Move setting of segment size into DataAccess constructors

Have not really looked into this, but it seems many Storable implementations have this method anyway (I guess because most of them use some DataAccess underneath), for example:

CHGraphImpl
LocationIndex
TurnCostExtension
GraphStorage
NameIndex
all DataAccesses

Yes, would make sense. What is the reason you stumbled over this?

I was checking where we are using CHGraphImpl instead of CHGraph and one of the reasons we do this e.g. in GraphHopperStorage was because of setSegmentSize(). It was similar when we discussed about using an interface for TurnCostExtension.

Does it make sense to call setSegmentSize after a DataAccess has been used (written to) ? Or can this even be a wrong thing to do ? If it must never be called after writing to the DataAccess I wonder if we should rather remove it from the DataAccess interface and add a segmentSize parameter to the constructors of the objects that need it ?

So if setSegmentSize may not be called after the first writes to the DataAccess its probably a bad idea to even expose it in Storable and I think it should rather be more hidden than exposed ?

Or can this even be a wrong thing to do ?

Yes, this can be even wrong (stumbled over this ugliness for the StringIndex again).

I think it should rather be more hidden than exposed ?

Yes. The only current use case is to reduce the storage size for small data. E.g. for tests (small graph data) but also for they DataAccess keys in StringIndex or StorableProperties.
In early days I was experimenting with this setting and was hoping that there is a sweet spot regarding performance. But it wasn't and so I picked a size of ~1MB so that the smallest possible graph is not too big and a very big graph has not too many segments (although it still can be X-thousand)

So something like dir.find("nodes", daType, segmentSize) ? This would mean that if the segmentSize parameter is given and the .find() call creates a new DataAccess it uses this segmentSize to do so. If .find() finds something it would just ignore the parameter. And then we have four overloads for Directory.find (with/without DAType and with/without segmentSize).

Yes, sounds good. Probably we should rename to findOrNew? Otherwise ignoring the segmentSize is a bit ugly... or doing a similar comparison like we do for daType?
https://github.com/graphhopper/graphhopper/blob/master/core/src/main/java/com/graphhopper/storage/GHDirectory.java#L83-L84

Ok I think I would rename it (anyway) and do this comparison ?

Yes

I tried briefly but its not so straight-forward because of copyTo etc. For now I'm happy with #1794, but at some point we should do this.

Interestingly, we always use Directory#find only to create something, never to return something that exists. GHDirectory keeps references to created objects and find would return the already created object, but we never use this feature. Ok, we use it once in LineIntIndex, but I think this is just an accident and can be fixed. So actually instead of adding segmentSize to dir.find("nodes", daType, segmentSize) I would rather remove the map of created DataAccess in GHDirectory entirely and rename find to create. Code that creates a DataAccess in Directory will use a reference to the created DataAccess anyway, so why should there be a Directory that keeps references to all the DataAccesses?
Ok this was still a bit simplified :) GHDirectory uses the map also for getAll, but, ..., this is never used. It also uses the map for close and clear, and they are even used in production, but, ... only once for elevation providers. And these elevation providers just temporarily create a directory to 'abuse' the map instead of simply using their own map.
Honestly, I feel like we do not need Directory at all.


Added optional parameters to stack.save()

stack.save(..., dataset=False, describe=False)
This PR resolves #426.

This PR resolves #426.


feat(linter): implement useImportExtensions

Summary
Closes https://github.com/biomejs/biome/issues/2674
Implements import/extensions requirement for relative extensions.
Rule suggests unsafe fix based on current file and import path, given the limitations of not being able to access file system.
Test Plan
Added snapshots

Should we disable this rule for typescript files? For a typical typescript projects, adding files extensions is usually handled by the bundler, and typescript doesn't even allow imported files to end with .ts or .tsx

@vohoanglong0107 As of typescript 5.0 you can use .ts extensions, this rule would not have much use otherwise. I don't see case where user would want to enable .js extensions, but not .ts

Once the conflicts resolved, I think we can merge this PR.

@Conaclos what about windows tests? Right now they fail, because on windows os paths us different slash. Should I replace pathBuf with vector or something like that?

@Conaclos what about windows tests? Right now they fail, because on windows os paths us different slash. Should I replace pathBuf with vector or something like that?

We shouldn't rely on PathBuf to compose the new imports. Instead, we should do that manually.

Ah, I've also run into that at some point. Maybe we should add it to the contributing guide somewhere. Path is usually better for inspecting path-like strings, but plain String is better for building paths if you don't want to run into surprises on Windows.

I replaced path_buf with string concatenation, windows test now pass.


Pin nbconvert

Pull Request Checklist:

[ ] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #xyz

[ ] Tests for the changes have been added (for bug fixes / features)

[ ] (If applicable) Documentation has been added / updated (for bug fixes / features)

[x] CHANGES.rst has been updated (with summary of main changes)

[x] Link to issue (:issue:number) and pull request (:pull:number) has been added

What kind of change does this PR introduce?

Pins nbconvert to prevent the documentation from failing on build.

Does this PR introduce a breaking change?
No.
Other information:
Example: https://readthedocs.org/projects/xclim/builds/23494704/
https://github.com/jupyter/nbconvert/issues/2092

coverage: 90.18%. remained the same
when pulling 91d4622d1c2ef32d840c7084ca1a95554992c739 on pin-nbconvert
into b7694af587cf029c38a794cb1c1ec7537dd69252 on master.


"cannot call non-const fn kani::assert in constant functions"

Having a poke at building top-100 crates with Kani. Found this one frequently.
Cause is typically an assert! or panic! etc in a constant function. Probably we just need to make kani::assert and friends const?

Do you have an example?

Good point. I believe this was the time crate?

Hello, I'm trying kani and ran into the same issue. The codebase I want to analyze uses panic! in constant functions and this causes cargo kani to fail with "cannot call non-const fn kani::panic in constant functions".
Simple example:
const fn my_const_fn() {
    panic!()
}
#[cfg(kani)]
#[kani::proof]
pub fn check_something() {
    my_const_fn();
}

Thanks for the example @nano-o! This is due to how Kani defines the panic function: https://github.com/model-checking/kani/blob/22316d16eb508e2a7f45d918ba4e5ab5a27332a1/library/kani/src/lib.rs#L137
Adding const to the function seems to fix the issue. I'm running the regressions and will submit a PR if everything looks good.

Hmm. This is possibly not yet completely solved. It did fix most of the issues I saw but I ran into this:
error: `std::fmt::Arguments::<'a>::new_v1` is not yet stable as a const fn
   --> /home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/time-0.3.14/src/format_description/well_known/iso8601/adt_hack.rs:148:13
    |
148 |             assert!(bytes[idx] == 0, "invalid configuration");
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = help: add `#![feature(const_fmt_arguments_new)]` to the crate attributes to enable
    = note: this error originates in the macro `format_args` which comes from the expansion of the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)

Which slightly confuses me. I think it might be triggerable just by building with the time crate.

Reproduction steps:
$ cargo new time-test
     Created binary (application) `time-test` package
$ cd time-test/
$ cargo add time --features formatting
[..SNIP..]
$ cargo kani
   Compiling itoa v1.0.3
   Compiling time v0.3.14
error: `std::fmt::Arguments::<'a>::new_v1` is not yet stable as a const fn
   --> /home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/time-0.3.14/src/format_description/well_known/iso8601/adt_hack.rs:148:13
    |
148 |             assert!(bytes[idx] == 0, "invalid configuration");
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = help: add `#![feature(const_fmt_arguments_new)]` to the crate attributes to enable
    = note: this error originates in the macro `format_args` which comes from the expansion of the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)

Error: "Failed to compile crate."
error: could not compile `time` due to previous error; 2 warnings emitted
Error: cargo exited with status exit status: 101

The non-const format_args was mentioned in an issue related to the const panic RFC: https://github.com/rust-lang/rust/pull/86998. It seems they implemented a special solution for that, which is currently unstable. I'll dig into this.

Currently, the format_args! cannot be used in const contexts unless the const_fmt_arguments_new language feature is enabled. So, while this Rust program is accepted by rustc:
const fn const_fn() {
    assert!(1 + 1 == 2, "A message");
}

fn main() {
    const_fn();
}

$ rustc assert.rs && ./assert
$

This one isn't:
const fn const_fn() {
    format_args!("A message");
}

fn main() {
    const_fn();
}

$ rustc assert.rs && ./assert
error: `Arguments::<'a>::new_v1` is not yet stable as a const fn
 --> assert.rs:2:5
  |
2 |     format_args!("A message");
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: add `#![feature(const_fmt_arguments_new)]` to the crate attributes to enable
  = note: this error originates in the macro `format_args` (in Nightly builds, run with -Z macro-backtrace for more info)

error: erroneous constant used
 --> assert.rs:2:18
  |
2 |     format_args!("A message");
  |                  ^^^^^^^^^^^ referenced constant has errors
  |
  = note: `#[deny(const_err)]` on by default
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #71800 <https://github.com/rust-lang/rust/issues/71800>

error: erroneous constant used
 --> assert.rs:2:5
  |
2 |     format_args!("A message");
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ referenced constant has errors
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #71800 <https://github.com/rust-lang/rust/issues/71800>
  = note: this error originates in the macro `format_args` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 3 previous errors

A workaround is to add:
![feature(const_fmt_arguments_new)]

to the root of the crate in which the assert is used (which may be difficult/impossible to do for dependent crates).
This issue should be resolved if/when const_fmt_arguments_new is stabilized .

I think we need to redefine the assert macro
macro_rules! assert {
    ($cond:expr $(,)?) => {
        kani::assert($cond, concat!("assertion failed: ", stringify!($cond)));
    };
    ($cond:expr, $fmt:literal $(,)?) => {{
        kani::assert($cond, concat!(stringify!($fmt)));
        if false {
            let _ = $fmt;
        }
    }};
    ($cond:expr, $fmt:literal, $($arg:tt)+) => {{
        kani::assert($cond, concat!(stringify!($fmt, $($arg)+)));
        if false {
            let _ = format_args!($fmt, $($arg)+);
        }
    }};
}

Thanks @camshaft for the great suggestion! The only downside is that Kani would fail to report errors/warnings in the format literal, e.g.
#[cfg(kani)]
macro_rules! assert {
    ($cond:expr $(,)?) => {
        kani::assert($cond, concat!("assertion failed: ", stringify!($cond)));
    };
    ($cond:expr, $fmt:literal $(,)?) => {{
        kani::assert($cond, concat!(stringify!($fmt)));
        if false {
            let _ = $fmt;
        }
    }};
    ($cond:expr, $fmt:literal, $($arg:tt)+) => {{
        kani::assert($cond, concat!(stringify!($fmt, $($arg)+)));
        if false {
            let _ = format_args!($fmt, $($arg)+);
        }
    }};
}

#[cfg_attr(kani, kani::proof)]
fn main() {
    assert!(1 + 1 == 2, "Hello world {}");
}

rustc:
$ rustc test_const.rs
warning: panic message contains an unused formatting placeholder
  --> test_const.rs:22:38
   |
22 |     assert!(1 + 1 == 2, "Hello world {}");
   |                                      ^^
   |
   = note: this message is not used as a format string when given without arguments, but will be in Rust 2021
   = note: `#[warn(non_fmt_panics)]` on by default
help: add the missing argument
   |
22 |     assert!(1 + 1 == 2, "Hello world {}", ...);
   |                                         +++++
help: or add a "{}" format string to use the message literally
   |
22 |     assert!(1 + 1 == 2, "{}", "Hello world {}");
   |                         +++++

warning: 1 warning emitted

rustc 2021:
$ rustc --edition 2021 test_const.rs
error: 1 positional argument in format string, but no arguments were given
  --> test_const.rs:22:38
   |
22 |     assert!(1 + 1 == 2, "Hello world {}");
   |                                      ^^

error: aborting due to previous error

Kani
$ kani test_const.rs
Checking harness main...
CBMC 5.67.0 (cbmc-5.67.0)
CBMC version 5.67.0 (cbmc-5.67.0) 64-bit x86_64 linux
Reading GOTO program from file test_const.out.for-main
Generating GOTO Program
Adding CPROVER library (x86_64)
Removal of function pointers and virtual functions
Generic Property Instrumentation
Running with 16 object bits, 48 offset bits (user-specified)
Starting Bounded Model Checking
Runtime Symex: 0.000678171s
size of program expression: 45 steps
slicing removed 27 assignments
Generated 2 VCC(s), 1 remaining after simplification
Runtime Postprocess Equation: 1.6311e-05s
Passing problem to propositional reduction
converting SSA
Runtime Convert SSA: 2.8521e-05s
Running propositional reduction
Post-processing
Runtime Post-process: 1.072e-05s
Solving with MiniSAT 2.2.1 with simplifier
0 variables, 0 clauses
SAT checker: instance is SATISFIABLE
Runtime Solver: 3.8802e-05s
Runtime decision procedure: 0.000100895s

RESULTS:
Check 1: main.assertion.1
         - Status: SUCCESS
         - Description: ""Hello world {a}""
         - Location: test_const.rs:22:5 in function main

SUMMARY:
 ** 0 of 1 failed

VERIFICATION:- SUCCESSFUL

Verification Time: 0.015771724s

but perhaps this is OK until format_args is allowed in const contexts?

Yeah that's a good point. Could you forward the string on to panic instead?
if false {
    ::std::panic!($($arg)+);
}

That's a great idea! This works if I use core::panic (since Kani overrides std::panic). Will submit a PR shortly.

D'oh, this still doesn't work with cf017e84e2e for const panics, e.g.:
const fn my_const_fn(msg: &str) -> ! {
    panic!("{}", msg)
}

#[cfg_attr(kani, kani::proof)]
fn main() {
    my_const_fn("failed");
}

$ rustc const_panic.rs
$ ./const_panic
thread 'main' panicked at 'failed', const_panic.rs:2:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
$ kani const_panic.rs
error[E0015]: cannot call non-const formatting macro in constant functions
 --> const_panic.rs:2:18
  |
2 |     panic!("{}", msg)
  |                  ^^^
  |
  = note: calls in constant functions are limited to constant functions, tuple structs and tuple variants
  = note: this error originates in the macro `format_args` which comes from the expansion of the macro `panic` (in Nightly builds, run with -Z macro-backtrace for more info)

error: `std::fmt::Arguments::<'a>::new_v1` is not yet stable as a const fn
 --> const_panic.rs:2:5
  |
2 |     panic!("{}", msg)
  |     ^^^^^^^^^^^^^^^^^
  |
  = help: add `#![feature(const_fmt_arguments_new)]` to the crate attributes to enable
  = note: this error originates in the macro `format_args` which comes from the expansion of the macro `panic` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0080]: erroneous constant used
 --> const_panic.rs:2:12
  |
2 |     panic!("{}", msg)
  |            ^^^^ referenced constant has errors

error: aborting due to 3 previous errors

Some errors have detailed explanations: E0015, E0080.
For more information about an error, try `rustc --explain E0015`.
Error: "Failed to compile crate."
Error: /home/ubuntu/git/kani/target/kani/bin/kani-compiler exited with status exit status: 1

Re-opening.


fix module not found

require('videojs-background') returned module not found with previous config

hmm, looks like the package I downloaded didnt yet have the dist folder
feel free to ignore

Which version did you install? 1.0.2 should have https://github.com/matthojo/videojs-Background/blob/master/dist/videojs-background.js in it

version 1.0.2, reinstalled three times, still no dist.. will try again tomorrow let u know

I've just fixed this in v1.0.3 :)

nice, that did it


Possible Uint8Array fixes

After doing a bunch of research, I think these are correct, but I want to figure out some tests for them before we land this.

Let me know if you want some help figuring anything out!


Slim 1148 make daylight savings deviation not writable

retest this please

retest this please

retest this please

Looks like there are some merging issues, as in the PR some files seem to have been deleted, while they should not have been...

Retest this please


fix: #157 Simulator isn't visible on booting it from Control Room

This PR fixes issue #157 - simulator isn't visible after booting it from Control Room when Simulator app is not running already.

Thank you!


fix potential flake8 miss checking

What is the problem that this fixes or functionality that this introduces? Does it fix any open issues?
During the code checking by flask8, the existing problem inside the original code will block the correct code modification suggested by the LLM.

Give a summary of what the PR does, explaining any non-trivial design decisions

Lint the original file before the code modification and record the error.

Select the errors caused by the modification after the code modification.

Other references
See detail description in the slack general channel  the following message:
OK, It seems that this is really a potential problem, I performed a check before the code modification (in /OpenDevin/opendevin/runtime/plugins/agent_skills/agentskills.py def _edit_or_append_file) , and find that this problem happened before it.  During the later code checking by flask8, the same problem will block the correct code modification suggested by the llm.  My suggestion is that, it is probably necessary to compare the error before and after the code checking to avoid this situation, otherwise, some correct code modification suggestion provided by llm will not be applied.  I can submit a pull request if you think my suggestion is correct. Thanks!

Do you have an actual code/file example of what is wrong, please?

I'm not sure how the problem is occuring in the first place.
The file - before editing - already has linting errors in it? Added by OpenDevin?

@xingyaoww I think it's all good now. In the previous version, I did not set first_error_line to None , which cause a problem with CURRENT_LINE. It is fixed now. Thanks

I'm not sure how the problem is occuring in the first place. The file - before editing - already has linting errors in it? Added by OpenDevin?

@tobitege It a problem happened in the command running stage.  The file - before editing - already has linting errors will block some correct modification suggest by OpenDevin.

I'm not sure how the problem is occuring in the first place. The file - before editing - already has linting errors in it? Added by OpenDevin?

@tobitege It a problem happened in the command running stage. The file - before editing - already has linting errors will block some correct modification suggest by OpenDevin.

Ok, understood.
As @xingyaoww mentioned, it'd be great if you could add a test case to the above mentioned unit test file.
The example from your Slack thread would probably suffice to illustrate the use case for this PR.
Thank you!

I'm not sure how the problem is occuring in the first place. The file - before editing - already has linting errors in it? Added by OpenDevin?

@tobitege It a problem happened in the command running stage. The file - before editing - already has linting errors will block some correct modification suggest by OpenDevin.

Ok, understood. As @xingyaoww mentioned, it'd be great if you could add a test case to the above mentioned unit test file. The example from your Slack thread would probably suffice to illustrate the use case for this PR.
Thank you!

Thanks, I added the test case here, https://github.com/OpenDevin/OpenDevin/pull/3124/commits/29edba0f841014babe8ffb64b927fc603551b42a. The example from the Slack thread contains about 3000 lines in total.  I used a simple example with the same type of error.

I'm not sure how the problem is occuring in the first place. The file - before editing - already has linting errors in it? Added by OpenDevin?

My understanding is flake8 could give false positives for existing files before OpenDevin's edits. If it's a "false positive", there's no point for OpenDevin to fix.
The added unit test doesn't seem to reproduce a "false positive".

I'm not sure how the problem is occuring in the first place. The file - before editing - already has linting errors in it? Added by OpenDevin?

My understanding is flake8 could give false positives for existing files before OpenDevin's edits. If it's a "false positive", there's no point for OpenDevin to fix.
The added unit test doesn't seem to reproduce a "false positive".

Yeh, agreed, I just ran the test locally to see how it works.
The test case as is doesn't seem to test what the original PR idea was about.
@bin123apple I was expecting it to have like just a single line at the top of the test content saying something like:
problematic-file-test.py:6:17 F821 undefined name 'ANOTHER_CONSTANT'

The real messages would look quite differently if linted for real with that missing variable.

Rewritten test method:
def test_edit_file_by_replace_with_problematic_file2(tmp_path, monkeypatch):
    # Set environment variable via monkeypatch does NOT work!
    monkeypatch.setattr(
        'opendevin.runtime.plugins.agent_skills.agentskills.ENABLE_AUTO_LINT', False
    )

    content = """problematic-file-test.py:6:18: F821 undefined name 'ANOTHER_CONSTANT'
def Sum(a,b):
    try:
        answer = a + b
        return answer
    except Exception:
        answer = ANOTHER_CONSTANT
        return answer
Sum(1,1)
"""

    temp_file_path = tmp_path / 'problematic-file-test.py'
    temp_file_path.write_text(content)

    open_file(str(temp_file_path))

    with io.StringIO() as buf:
        with contextlib.redirect_stdout(buf):
            edit_file_by_replace(
                str(temp_file_path),
                to_replace='        answer = ANOTHER_CONSTANT',
                new_content='        answer = \'test\'',
            )
        result = buf.getvalue()
        expected = (
            f'[File: {temp_file_path} (8 lines total after edit)]\n'
            '(this is the beginning of the file)\n'
            '1|def Sum(a,b):\n'
            '2|    try:\n'
            '3|        answer = a + b\n'
            '4|        return answer\n'
            '5|    except Exception:\n'
            '6|        answer = \'test\'\n'
            '7|        return answer\n'
            '8|Sum(1,1)\n'
            '(this is the end of the file)\n'
            + MSG_FILE_UPDATED.format(line_number=6)
            + '\n'
        )
        assert result.split('\n') == expected.split('\n')

@li-boxuan what do you think? good to go?

@li-boxuan what do you think? good to go?

I am mostly concerned with the proposed approach.
The test is fine, although I would suggest renaming the test and adding more comments to the code.

Hey @bin123apple , thanks again for the contribution! What do you think about @li-boxuan 's comments above. Do you understand what would need to be done, or would you like some help?

Hey @neubig, thanks for asking, I read @li-boxuan's comment before and the example he gave.

Say you have L1,2,3,4, and you replace L3 with 2 new lines, and then you have L1,2,3,4,5, with L3 & L4 being new. We should only retain linting errors for L3-5 (inclusive).

One thing I am not very sure is that if we replace L3 with 2 new lines, will it cause new issues in other places inside of only these two lines? For example, if we delete a function defination, I think there will probably be some issues in other places if we use this function elsewhere.
I still suggest to check the lint_error before and after the new modification and probably use my commit https://github.com/OpenDevin/OpenDevin/pull/3124/commits/02dab77e5f2e039f128452acb5cf28d6cc4ca30d ? Thanks!

Say you have L1,2,3,4, and you replace L3 with 2 new lines, and then you have L1,2,3,4,5, with L3 & L4 being new. We should only retain linting errors for L3-5 (inclusive).

One thing I am not very sure is that if we replace L3 with 2 new lines, will it cause new issues in other places inside of only these two lines? For example, if we delete a function defination, I think there will probably be some issues in other places if we use this function elsewhere.

That's a good point, so we DO need to run linter twice. I still think my original comment holds, though. I am worried about current approach causing regressions. Comparing errors using error message doesn't convince me. Taking  F821 | undefined name [name] for example. Let's say the original script is:
def unused_bogus_func():
     undefined_func()

def func_to_modify():
     print('this function works')

Linter would report test.py:2:5 F821 undefined name undefined_func
and OpenDevin modifies it into:
def unused_bogus_func():
     undefined_func()

def func_to_modify():
     undefined_func()

Linter would report test.py:2:5 F821 undefined name undefined_func and test.py:5:5 F821 undefined name undefined_func
Using the current approach in this PR (comparing error messages), this wrong edit by OpenDevin would be overlooked.

Thanks for pointing out the potential bug.

Linter would report test.py:2:5 F821 undefined name undefined_func and test.py:5:5 F821 undefined name undefined_func

Yes, this case will indeed be ignored by the current commit.
It seems difficult to find a perfect solution. I’ve come up with two methods, but both have some potential edge cases.
1. Also compare the line number before & after the lint.
However, if some new lines are added. The test.py:2:5 will change to test.py:3:5, which is not the same as the original lint_error.
2. Also compare the number of the different types of errors.
However, if the original error is fixed, and new error is imported. The new error will be ignored.
I haven't thought of a better solution for now either.

However, if some new lines are added. The test.py:2:5 will change to test.py:3:5, which is not the same as the original lint_error.

OpenDevin only makes one edit (consecutive lines) at a time, so you could figure out the mapping.

OpenDevin only makes one edit (consecutive lines) at a time, so you could figure out the mapping.

Oh, I think this is a feasible method!
And I just check the current main branch code for the detail, It not only contains the edit_file(), but also contains some other modification functions such as replace()
Could some one help with the line number mapping function 🤦? I think if I do that on my own, it would take me a long time to figure out the details of these modification functions and to keep everything correct for the line mapping lol...

OpenDevin only makes one edit (consecutive lines) at a time, so you could figure out the mapping.

Oh, I think this is a feasible method!
And I just check the current main branch code for the detail, It not only contains the edit_file(), but also contains some other modification functions such as replace()
Could some one help with the line number mapping function 🤦? I think if I do that on my own, it would take me a long time to figure out the details of these modification functions and to keep everything correct for the line mapping lol...

I can take a look and directly push to your PR, if you agree

OpenDevin only makes one edit (consecutive lines) at a time, so you could figure out the mapping.

Oh, I think this is a feasible method!
And I just check the current main branch code for the detail, It not only contains the edit_file(), but also contains some other modification functions such as replace()
Could some one help with the line number mapping function 🤦? I think if I do that on my own, it would take me a long time to figure out the details of these modification functions and to keep everything correct for the line mapping lol...

I can take a look and directly push to your PR, if you agree

Sure! Really appreciate!


Is it possible to use a location other than /Users

Is it possible to mount an additional location say /opt/docker in addition to /Users?

Hello @JoyceBabu ,
It's possible but you will have to modify the script manually :/


Is it possible to set "step" property on number inputs?

Is it possible to set "step" property on number inputs?

yes possible:
{
  type: 'input',
  templateOptions: {
    type: 'number',
+   step: 10,
  },
},


chore: add android cache

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add the option to force include client-only from Modrinth modpacks

Mentioned in Discord

Inclusion wasn't working, as reported in Discord


Fix issues identified by Dorota in #81

[x] Include suicidality_score in  activity
[x] Include suicidality_score in dsm_5_parent_guardian_rated_level_1_crosscutting_s_schema_20_to_25
[x] Include suicidality_score in DSM5_crosscutting_youth_schema
[x] Fix missing  item for activities/RCADS-25-C/items/RCADS25_25
[x] Fix non-existent activities/RCADS-25-Y/items/RCADS-25_total_score
[x] Remove unused addProperties elements e.g. here

"suicidality_score is not included in addProperties in the activity
the same issue in dsm_5_parent_guardian_rated_level_1_crosscutting_s_schema_20_to_25 and DSM5_crosscutting_youth_schema"
"items activities/RCADS-25-C/items/RCADS25_25 and activities/RCADS-25-Y/items/RCADS-25_total_score don't exist but used in the schemas"
"some schema has in addProperties elements that are not used, e.g. here"
https://github.com/ReproNim/reproschema-library/issues/81

@djarecka did I address all your feedback?

@djarecka hi, can you double check whether everything we needed is done and if so, we can merge this?


Adds code coverage workflow and badge.

@ralexstokes to finish this PR the ssz-rs repo would need the CodeCov app to be added.

I've added the code cov app for this repo. And generally thumbs up on this approach
it looks like this PR uses tarpaulin, which I haven't used before but don't see any issues yet -- ill go do some more research but if you want to send over any resources that would be appreciated!

@ralexstokes thanks for reviewing! I applied the changes. 😄


KFLUXINFRA-777: Config to Configure Worker Nodes with NVMe Disks

This Pull Request will do the following -

Create Namespace
ServiceAccount
ClusterRoleBinding
ConfigMap
DaemonSet

This DaemonSet will make use of shell scripts coming from the ConfigMap to configure NVMe Disks.

/retest

/test appstudio-e2e-tests

@gbenhaim could you please take a look at this whenever your schedule allows you?
Thanks :)

/approve

/lgtm

/retest

/lgtm


Question: How to play MIDI files?

From the project description:

A User-friendly Arduino/Teensy/ESP8266 Library to play MIDI files

Sorry if I missed this, but how does one play MIDI files with this library? I saw the How to Write Music section, but didn't see anything about playing an existing MIDI file. Do the MIDI files need to be converted to this "RTTL" format or something?
Awesome project, BTW!

In the MIDI example listed here, you must use a MIDI serial that sends data to the RX pin of the Arduino(If you want to use it with a computer, you must use Hairless-MIDI). Or you can use a Teensy as a USB-MIDI device shown at PJRC's site.  Then simply plug the Arduino/Teensy to a computer and play the MIDI stream. I prefer teensy because it uses fewer wires :)
Here is a video of me playing my piano and using the USB host shield to convert USB MIDI to regular MIDI and then feeding them into the RX pin of the microcontroller. You can also use Anvil Studio to play many popular midi files to the Teensy. Here is a video of that too.
I intentionally had the idea to make a library that would play a MIDI char array, but I never got around to that :sweat:.  I don't how to interpret MIDI rests and notes.  But it is definitely possible to implement this feature.
So that's why I've been using a separate Arduino to stream the MIDI and using my Noodle synth to play it.

Thanks for the info! I don't know a very much about MIDI... Do you know of any other projects that can play MIDI files on an Arduino specifically? Also, could your library play MIDI files if first converted to RTTL format? Looks like there are various converters online.


Fixed issue 96: moins de 21s parsing

Fixes issue #96

[Current coverage][cc-pull] is 94.32%

Merging [#192][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #192   diff @@
==========================================
  Files            29         29
  Lines          2554       2554
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2409       2409
  Misses          145        145
  Partials          0          0

Powered by Codecov. Last updated by [004ec7d...ab984e8][cc-compare]
[cc-base-branch]: https://codecov.io/gh/scrapinghub/dateparser/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/scrapinghub/dateparser/compare/004ec7d15ff10524d6d328910cb58da34b04fc69...ab984e8f2de24c37b97a47feb7101711c69ccac4
[cc-pull]: https://codecov.io/gh/scrapinghub/dateparser/pull/192?src=pr


Datastreams UI improvements

Description

In this PR I have added a few Datastreams UI improvements to the Extension Configuration View:

added copy datastream ID to clipboard button - PDCL-8306
added delete datastream ID button - PDCL-8308
changed the alert box for not required environments to informative rather than error - PDCL-8309

Related Issue

Motivation and Context

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (non-breaking change which does not add functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA or I'm an Adobe employee.
[ ] I have made any necessary test changes and all tests pass.
[ ] I have run the Sandbox successfully.
[ ] I've updated the schema in extension.json or no changes are necessary.
[ ] My change requires a change to the documentation.

I've investigated the test failures they are here: #232.
Thanks for going through these tickets. What do you think of graying out the copy and delete buttons when there is no data stream selected?

Thank you Jon! If there is no datastream selected the buttons will be disabled


🐛 Fix support for prefix on APIRouter WebSockets

Related to #2639

Any chance on getting this PR merged?

Is there any reason why this PR is still not merged?

Hi! Will this PR get merged any time soon? It's been more than a year
@tiangolo

@tiangolo Please merge this!

Why is this not merged yet ? Are you guys afraid it will deprecate existing code ?

Awesome, thanks @Kludex as always! :bow: :cake:
Thanks everyone for your input. :cookie:
This will be available in FastAPI version 0.75.2 in a couple of hours.

Try this solved


Able to start the oobabot twice

          I noticed an issue - i dont know if it relates.

But if you refresh the webui while the bot is running - it will default to be displayed as the bot if off. And you can press the "start oobabot" button again while its running, (whitch would be typically grayed out)
If you do indeed press that button then the bot would end up replying twice over to every message untill ooba is fully restarted

as you can see in the picture above. The bot is already running , and "stop" button is grayed out. But the "start" button is clickable.
Originally posted by @obi-o-n-e in https://github.com/chrisrude/oobabot-plugin/issues/18#issuecomment-1621232435

Thanks for the report!  I've landed a fix for this in https://github.com/chrisrude/oobabot-plugin/commit/bb81073decf0fc9d302680fb884100334e5e7039
It should be included in the next release.

This should be fixed with the 0.2.0 release.  Please let me know if it still occurs after that.
To upgrade, just go into your textgen directory / conda environment and run pip install oobabot-plugin --upgrade.
Thanks for the report!


[azservicebus] Stress test updates (mostly)

Quite a few updates, mostly just trying to make the stress tests test more areas around reliablity, and be easier to write. We now have:

infinite_send_and_receive: 5 days of constant sending and receiving, with 4 receivers on separate connections.
constant_detachment: makes sure our links properly recover. There is still a bug that needs to be fixed for it to be 100% reliable (where amqp-common was eating and retrying on obviously fatal errors)
finite_send_and_receive: sends 50000 messages, and receives them, making sure nothing is dropped
long_running_renew_lock: receives a message and does nothing but renew the lock, every 5 seconds, and then complete it after 3 hours.
Adding in a test case I saw in an issue: https://github.com/Azure/azure-service-bus-go/issues/126

Also, adding in some extra tools:

StreamingBatch, similar to an idea we're kicking around for simplifying batch sending.
A series of useful development CLI commands:

delete queues/topics by regex
constant update a queue to force detach logic
creating an auto-expiring test queue

Part of #15758

/azp run go - azservicebus


Link not working

looks like the link module is not working with the current version.

Hello,
Thanks for reporting the issue.
A fix is imminent.
:+1:


[0.19][ios]Error 'babelHelpers.typeof is not a function'  running examples UIExplorer

The project I inited before run normally. But the example cloned from react-native of github could not works. I followed the steps in README, and I find out one module require<EMAIL_ADDRESS>when I run 'npm install'.
I assume that the error occurs because of the version of babel. But I can not solve the problem by install latest version of babel.

@asd123freedom I also got this upon upgrading. I tried clearing babel cache and the react native packager cache. It wasn't until I literally rebooted that it was resolved.
Not the most concrete solution I understand, but this is eventually what solved it for me. I suspect there was something being cached somewhere in $TMP but couldn't track it down.

@gijoehosaphat Thanks a lot. I will try it as soon as possible

@asd123freedom @gijoehosaphat the best way to make sure the packager cache is cleared is by doing:
watchman watch-del-all
[packager command] --reset-cache

For me, the fix was getting rid of es-2015 as a preset in my .babelrc file, thanks @skevy

@gijoehosaphat was the problem solved?

I ended up not having to change any code in the project, and continue to use stage-0, es2015 and react babel presets. I believe it was just cache causing a conflict.

cc @asd123freedom good to close?

@bestander Because of Chinese new year I am in a vacation not having my mac aside. I  will  try the solution @gijoehosaphat  suggested when I come back from vacation. So it's good to close. Thanks a lot.

:+1: reopen if it is still an issue

I'm now running into this issue with v0.19.0, so I tried upgrading to v0.20.0 but I still run into the issue.
Newly init'd projects work fine, but a project I started about a week ago is broken. I've tried all of the above suggestions with no luck.
This morning I've done the following:
rm -rf node_modules/
watchman watch-del-all
npm cache clean
I then removed all dev and regular dependencies from package.json except for<EMAIL_ADDRESS>npm install
react-native run-ios
And it still comes up with the undefined babelHelpers.typeof exception.
I was able to take my application specific code and basically dump that into a newly init'd project and it runs fine. I'd still like to know why my original repo is hosed though, and fix if possible.

what does your package.json look like?

I took it down to its bare minimum, trying to replicate a fresh react-native init.
{
  "name": "testApp",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
  },
  "dependencies": {
    "react-native": "0.20.0"
  }
}

Previously there was more (See below), but I spent several hours adding and removing package dependencies to try and figure out if one of them was the problem. One step I did take last night was to react-native init a new app, and then one by one add the dependencies seen below and after each one I ran the simulator. I was able to get my app running in the simulator this way, so I'm at a loss for what might be the root cause in my original repo folder.
{
  "name": "testApp",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "remotedev": "remotedev --hostname=localhost --port=8000",
    "test": "mocha --compilers js:babel-register --require  ./test/test_helper.js --require babel-polyfill --recursive || true"
  },
  "dependencies": {
    "firebase": "2.4.0",
    "geofire": "3.2.4",
    "history": "2.0.0",
    "immutable": "3.7.6",
    "ramda": "0.19.1",
    "react-addons-pure-render-mixin": "0.14.7",
    "react-native": "0.20.0",
    "react-native-drawer": "1.15.0",
    "react-native-geocoder": "0.3.1",
    "react-native-maps": "0.3.0",
    "react-native-router-flux": "2.2.0",
    "react-redux": "4.4.0",
    "redux": "3.3.1",
    "redux-saga": "0.7.0",
    "redux-thunk": "1.0.3",
    "reselect": "2.0.3"
  },
  "jscsConfig": {
    "maximumLineLength": null
  },
  "devDependencies": {
    "babel-cli": "6.5.1",
    "babel-plugin-transform-regenerator": "6.5.2",
    "babel-polyfill": "6.5.0",
    "babel-preset-es2015": "6.5.0",
    "babel-register": "6.5.2",
    "chai": "3.5.0",
    "chai-immutable": "1.5.3",
    "mocha": "2.4.5",
    "remote-redux-devtools": "0.1.2",
    "remotedev-server": "0.0.3"
  }
}

@mikepugh
$ npm cache clean

is something different from
[packager command] --reset-cache

Try to run
$ ./node_modules/react-native/packager/packager.sh start --resetCache

from your application folder first.

@Kureev - ok thanks for the tip, I'll try that out once I'm back on that machine this afternoon.
I don't have a .babelrc file, I did have a "babel" section within package.json which loaded the es2015 preset, but it's missing at the moment due to all of the recent meddling.

@Kureev awesome - the --reset-cache fixed it.

@mikepugh I'm glad it helped you.

I have the same problem for a fresh clean project created the project using
react-native init

I've tried all the above suggestions and am still running into this problem. Uncaught TypeError: babelHelpers.typeof is not a function
Node v4.3.1
NPM v3.7.3
I've been running
npm run reset
node node_modules/react-native/local-cli/cli.js run-ios --reset-cache
{
  "name": "mobile_moderation",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "remotedev": "remotedev --hostname=localhost --port=8000",
    "reset": "rm -rf node_modules/ && npm cache clear && watchman watch-del-all && rm -rf $TMPDIR/react-* && npm i",
    "start": "node node_modules/react-native/local-cli/cli.js start --reset-cache",
    "test": "mocha --compilers js:babel-core/register --require ./test/test-helper.js --recursive",
    "test:watch": "npm run test -- --watch --watch-extensions jsx"
  },
  "babel": {
    "presets": [
      "es2015",
      "stage-2"
    ],
    "plugins": [
      "transform-regenerator",
      "transform-flow-strip-types"
    ]
  },
  "dependencies": {
    "immutable": "^3.7.6",
    "ramda": "^0.19.1",
    "react": "^0.14.7",
    "react-native": "^0.20.0",
    "react-redux": "^4.4.0",
    "redux": "^3.3.1",
    "redux-saga": "^0.8.2",
    "reselect": "^2.0.3"
  },
  "devDependencies": {
    "babel-cli": "^6.5.1",
    "babel-core": "^6.5.2",
    "babel-plugin-transform-flow-strip-types": "^6.5.0",
    "babel-plugin-transform-regenerator": "^6.5.2",
    "babel-polyfill": "^6.5.0",
    "babel-preset-es2015": "^6.5.0",
    "babel-preset-stage-2": "^6.5.0",
    "chai": "^3.5.0",
    "chai-immutable": "^1.5.3",
    "mocha": "^2.4.5",
    "remotedev-server": "0.0.3"
  }
}

@prasanthu @lifehackett
I was just having the same problem.
What I did were:
$npm uninstall -g react-native-cli
$brew update && brew upgrade
$npm uninstall -g react-native-cli

I'm at
$ node -v
v5.6.0
$ react-native -v
react-native-cli: 0.1.10
react-native: 0.20.0

Did what @xuezhma told but it didn't fixed for me, any other solution? Thanks!

@lifehackett @sambarboza Can you please share your .babelrc configs? (if you already tried to run a packager with --reset-cache option)

@Kureev are theses .babelrc configs global or per project? On the project folder I don't have this file. I've tried to run the packager command with --reset-cache.

@Kureev I wasn't using a .babelrc config in my original post.  The babel transforms were applied in my package.json https://github.com/facebook/react-native/issues/5747#issuecomment-187765275
I have tried this setup as well and gotten the same results.
.babelrc
{
    "extends": "react-native/packager/react-packager/.babelrc"
}

package.json
{
  "name": "TestProject",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "remotedev": "remotedev --hostname=localhost --port=8000",
    "reset": "rm -rf node_modules/ && npm cache clear && watchman watch-del-all && rm -rf $TMPDIR/react-* && npm i",
    "start": "node node_modules/react-native/local-cli/cli.js start --reset-cache & sudo dtruss -fn node",
    "test": "mocha --compilers js:babel-core/register --require ./test/test-helper.js --recursive",
    "test:watch": "npm run test -- --watch --watch-extensions jsx"
  },
  "dependencies": {
    "immutable": "^3.7.6",
    "ramda": "^0.19.1",
    "react": "^0.14.7",
    "react-native": "^0.20.0",
    "react-redux": "^4.4.0",
    "redux": "^3.3.1",
    "redux-saga": "^0.8.2",
    "reselect": "^2.0.3"
  },
  "devDependencies": {
    "babel-cli": "^6.5.1",
    "babel-plugin-transform-flow-strip-types": "^6.5.0",
    "babel-plugin-transform-regenerator": "^6.5.2",
    "babel-preset-es2015": "^6.5.0",
    "babel-preset-stage-2": "^6.5.0",
    "chai": "^3.5.0",
    "chai-immutable": "^1.5.3",
    "mocha": "^2.4.5",
    "remote-redux-devtools": "^0.1.2",
    "remotedev-server": "0.0.3"
  }
}

@lifehackett you shouldn't extend react-native's babelrc file. Try using this https://github.com/facebook/react-native/tree/master/babel-preset instead of es2015 and stage-2.

@Kureev Same result

@lifehackett @Kureev same thing here.

I had been running into this issue for the last few days, just solved this by switching the es2015 preset from my .babelrc with react-native and then running react-native start --reset-cache. My .babelrc file looks like this now:
{
  "presets": ["stage-1", "stage-2", "stage-3", "react-native"],
  "plugins": ["transform-decorators-legacy"],
}

and my package.json looks like this:
{
  "private": true,
  "name": "[REDACTED]",
  "version": "0.0.0",
  "scripts": {
    "authenticate": "scripts/authenticate",
    "bundle": "scripts/bundle:js",
    "bundle:js": "scripts/bundle:js",
    "clean": "scripts/clean:cache && scripts/clean:deps",
    "clean:cache": "scripts/clean:cache",
    "clean:deps": "scripts/clean:deps",
    "postinstall": "scripts/postinstall",
    "provision": "scripts/provision",
    "publish": "scripts/publish",
    "publish:all": "scripts/publish demo && scripts/publish production",
    "publish:sourcemap": "scripts/publish:sourcemap",
    "publish:codepush": "scripts/publish:codepush",
    "shrinkwrap": "npm-shrinkwrap",
    "start": "scripts/start",
    "start:ios": "scripts/start:ios",
    "test": "mocha --require babel/register"
  },
  "dependencies": {
    "google-libphonenumber": "1.0.7",
    "js-quantities": "1.6.0",
    "lodash": "3.10.1",
    "moment-timezone": "0.4.1",
    "numeral": "1.5.3",
    "pluralize": "1.2.1",
    "raven-js": "1.3.0",
    "react-addons-shallow-compare": "0.14.0",
    "react-addons-update": "0.14.0",
    "react-mixin": "3.0.0",
    "react-native": "0.20.0",
    "react-native-audioplayer": "0.2.0",
    "react-native-background-geolocation": "0.3.3",
    "react-native-code-push": "1.7.3-beta",
    "react-native-file-upload": "1.0.4",
    "react-native-image-picker": "marcshilling/react-native-image-picker#5720a18",
    "react-native-mixpanel": "0.0.7",
    "react-native-orientation": "JAStanton/react-native-orientation#340a0ba",
    "react-native-scrollable-tab-view": "0.3.7",
    "react-native-side-menu": "0.18.0",
    "react-native-vector-icons": "1.2.1",
    "react-timer-mixin": "0.13.3",
    "redux": "3.3.1",
    "redux-thunk": "1.0.3",
    "shallowequal": "0.2.2",
    "url": "0.11.0"
  },
  "devDependencies": {
    "babel-plugin-transform-decorators-legacy": "1.3.4",
    "babel-preset-react-native": "1.4.0",
    "babel-preset-stage-1": "6.5.0",
    "babel-preset-stage-2": "6.5.0",
    "babel-preset-stage-3": "6.5.0",
    "code-push-cli": "1.5.0-beta",
    "ios-sim": "5.0.6",
    "mocha": "2.3.3",
    "react-native-cli": "0.1.10",
    "sinon": "1.17.1"
  }
}

I am on node-version: v4.1.0
I am on npm version: 2.14.3
I installed all my dependencies with npm3 install.

@JAStanton I already recommended @lifehackett and @sambarboza to replace es2015 by react-native preset and clear the cache, but seems they have the same problem still.
P.S. You can remove stage-2 and stage-3 from your config, stage-1 includes 2nd and 3rd stages by default

@Kureev oh! Thanks :)
Could it be that another one of their presets includes es2015? Correct me if I'm wrong but the babel.typeof source code is coming from whatever code es2015 includes. Remove that and that code isn't even in your source. IMO they still have the old cache sticking around somehow. Anyways thats my $0.02 if it helps any.

Thanks guys! With @JAStanton and @Kureev tip's to use stage-1, was already using react-native preset, added stage-1 and it worked.

huzzah! Glad to hear it!
On Thu, Feb 25, 2016 at 12:32 PM Samuel Barbosa<EMAIL_ADDRESS>wrote:

Thanks guys! With @JAStanton https://github.com/JAStanton and @Kureev
https://github.com/Kureev tip's to use stage-1, was already using
react-native preset, added stage-1 and it worked.
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/issues/5747#issuecomment-188969256
.

Hey, glad that it helped! :+1:

There's something unsettling about the number of different 'solutions' to this issue, and how they don't seem to work reliably for everybody.

Following this thread as well as I'm getting the same babelHelpers.typeof  error mentioned above and haven't had success with any suggestions.
I tried adding stage-1 to my .babelrc presets, cleared cache, etc. with no luck running:
node v4.3.1
npm v3.7.5
App is running react-native v0.20.0.

I have some more data points.

Created a new repo. Ran without errors
Added some dependencies (none babel related). Ran without errors
I used a destructuring import statement import { actionTypes } from ../constants. Got an error that actionTypes is undefined

Conclusion: Doesn't know how to handle destructuring.

Shutdown server and emulator
rm -rf node_modules/
npm clear cache
npm i
npm i --save-dev babel-preset-react-native
Added "babel": { "presets": ["react-native"] } to package.json
watchman watch-del-all
node node_modules/react-native/local-cli/cli.js run-ios --reset-cache
Still get error about actionTypes being undefined

I looked at babel-preset-react-native and it depends on babel-plugin-transform-es2015-destructuring which would seem like it would handle my scenario.  The conclusion I am therefore drawing is that my preset definition is not getting picked up/recognized.  This seems to jive with the "fixes" people have been identifying and the idea that there is some sort of caching issue, but none of the methods I used above fixed the problem.  It seems like the cache issue could be internal to react-native.
For completeness
node- 4.3.1
npm- 3.7.5
{
  "name": "fresh",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start"
  },
  "babel": {
    "presets": ["react-native"]
  },
  "dependencies": {
    "immutable": "^3.7.6",
    "ramda": "^0.19.1",
    "react": "^0.14.7",
    "react-native": "^0.20.0",
    "react-redux": "^4.4.0",
    "redux": "^3.3.1",
    "redux-saga": "^0.9.1",
    "reselect": "^2.0.3"
  },
  "devDependencies": {
    "babel-preset-react-native": "^1.4.0"
  }
}

1

Also getting this error with 0.20 (node 5.7 & npm 3.6), tried both with es2015 and react-native presets with a clear-cache didn't fix the issue on my side (axios package).

Same problems here. Initializing a brand new project then adding Babel with es2015 and stage-2 results in the error. I've cleared npm cache, uninstalled (local and global) node_modules, the entire node installation, and used the --reset-cache option. I've also tried using dropping 'es2015' in favor of 'react-native' as suggested earlier.

Same here, tried everything as well and I still have the error, latest versions everywhere.

Same problems here. Initializing a brand new project then adding Babel with es2015 and stage-2 results in the error.

It's a fun windy path, but I think I have an explanation:

The es2015 preset includes transform-es2015-typeof-symbol
transform-es2015-typeof-symbol transforms all typeof comparisons into a call to babelHelpers.typeof
The react packager bundles its own implementation of babelHelpers, which does not include an implementation of typeof (and several other helpers defined in Babel's implementation)
From what I can tell, you can't hook into the load process early enough to monkey patch the packager's implementation w/ missing methods from the official implementation

Having the same problem here. Tried the fix other people suggested but when i put react-native in .babelrc instead of es2005, i got error:
/Users/shangyeshen/Sites/cairn/node_modules/react-native/Libraries/react-native/react-native.js:114
  ...require('React'),
  ^^^

SyntaxError: Unexpected token ...

and when added stage-1 to .babelrc, got error:
Error: Couldn't find preset "stage-1" relative to directory "/path/to/project"

.babelrc
{
  "presets": [
    "stage-1",
    "react-native"
  ]
}

this is my package.json:
{
  "name": "app",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "server": "nodemon index.server.js",
    "test": "PORT=3001 mocha --compilers js:babel-core/register server/tests"
  },
  "dependencies": {
    "body-parser": "^1.15.0",
    "express": "^4.13.4",
    "express-session": "^1.13.0",
    "jsonwebtoken": "^5.7.0",
    "mocha": "^2.4.5",
    "mongoose": "^4.4.3",
    "morgan": "^1.7.0",
    "react-native": "^0.19.0",
    "react-native-fbsdkcore": "0.0.8",
    "react-native-fbsdklogin": "0.0.8",
    "react-redux": "^4.4.0",
    "redux": "^3.3.1",
    "redux-logger": "^2.5.0",
    "redux-thunk": "^1.0.3",
    "supertest": "^1.2.0"
  },
  "devDependencies": {
    "babel-core": "^6.5.2",
    "babel-preset-es2015": "^6.5.0",
    "nodemon": "^1.8.1",
    "supertest": "^1.2.0"
  }
}

@shangsunset Please leave this issue clean, the error message should be obvious about what your problem really is.

I just upgraded to the newly released<EMAIL_ADDRESS>and am no longer experiencing the issue.  I'll hold off on declaring the issue resolved as some of the "fixes" listed in this thread have provided temporary relief only to have the error resurface.  I suggest other try upgrading.  I'll update in a few days.  These commits stood out as potential fixes
https://github.com/facebook/react-native/commit/a72c295
https://github.com/facebook/react-native/commit/727a2a9

I just upgraded version 0.21.0 but also appeared the problem....

After upgrading to 0.21.0 I also still have the problem.

@gobadiah You said you are using "Latest versions everywhere". Does that mean 5.x? I'm using 4.3.1.
@gavin1990 What node version are you using?

@lifehackett Yes node 5.7.0, I'm trying to find out now what's going on. If I don't succeed I'll reverse to 4.3.1 to see what happens.

There are other issues regarding babelHelpers. I followed this comment by @justinr1234 .
It simply suggests ... to edit the babelHelper file and add the code needed. In our case, edit the file
vim node_modules/react-native/packager/react-packager/src/Resolver/polyfills/babelHelpers.js

add these lines :
babelHelpers.typeof = typeof Symbol === "function" && typeof Symbol.iterator === "symbol" ? function (obj) {
  return typeof obj;
} : function (obj) {
  return obj && typeof Symbol === "function" && obj.constructor === Symbol ? "symbol" : typeof obj;
};

After babelHelpers definition ( var babelHelpers = global.babelHelpers = {};)
Hopefully this will be integrated in future versions.

@lifehackett node  v5.6.0

same here, having the issue on my end as well. probably worth re-opening the issue since it seems to affect people still. I tried to update babelHelpers.js with this:
babelHelpers.typeof = typeof Symbol === "function" && typeof Symbol.iterator === "symbol" ? function (obj) {
  return typeof obj;
} : function (obj) {
  return obj && typeof Symbol === "function" && obj.constructor === Symbol ? "symbol" : typeof obj;
};

no luck...
cleared my npm cache, nuked my node_modules dir, re-cloned my repo, no luck. help will be greatly appreciated.

@emroot did you try my comment on this page: https://github.com/facebook/react-native/issues/4844#issuecomment-191282653

Although upgrading to<EMAIL_ADDRESS>initially resolved the issue for me, it has returned.  I'll try @justinr1234 hack, but I think this needs to be addressed at the core.

@justinr1234 yeah it's already in my .babelrc
I tried doing this too, just in case if any other .babelrc file would screw things up.
find node_modules -type f -name .babelrc | grep -v /react-native/ | xargs rm
Everything was working fine until I installed https://www.npmjs.com/package/react-native-push-notification, that when I started getting the error. I then removed the packages and the issue sticked. I tried deleting node_modules, clear npm cache, run with --reset-cache, downgrade react-native to 0.20 (I am running on `0.21). No luck. I'm debating in reinstalling npm from scratch.
here's a backtrace of the error if this helps:

@lifehackett any luck?
@emroot did you specifically try modifying the babelHelpers.js file in your node_modules here:  https://github.com/facebook/react-native/blob/master/packager/react-packager/src/Resolver/polyfills/babelHelpers.js
And replace it with your own generated by following directions here:  http://stackoverflow.com/a/34943779/3096547
I'm confused by what you said, because it sounds like you followed a different (probably equivalent) method. I'm no expert on the situation, but the steps I outlined are the only way I was able to fix my errors.

@justinr1234 yeah I did it last, see my previous comment here.

This error has been holding up my team for the last 2 days. My local repo currently works as expected, but several of my teammates have had this issue arise (seemingly out of nowhere). When I push my repo up to github, pull down a fresh copy, and try to run the project from there, I get the error as well. But my local repo still works fine.
Would really appreciate any help!

@gm758 Have you tried archiving your working install and sending to someone on your team?

@justinr1234 I did, but with no luck. Even when I copy the repo into a new directory on my computer, this error pops up.

@justinr1234 applying your fix did NOT resolve the error in my case.

The work around I have been doing and seems to consistently work is to react-native init a new project and then copy over my files from the broken project into the new one.  This is certainly not ideal especially from a VC perspective.

@lifehackett what other debugging steps did you take from this thread? That sounds like it could be a cache issue maybe...

@justinr1234 I've tried every single one mentioned in this and any other threads I can find.  Some of my earlier posts on this issue detail them.

After cleaning my build folder and restarting my computer due to an unrelated issue, I am now getting this error like the rest of my team. Apparently whatever was keeping my safe from this bug is gone now. We've pretty much had to revert to not using babel at all, which precludes doing any testing in ES6+ or defining our own presets.
I know of at least 2 other teams working with react native who've been hamstrung by this error. I think this issue should reopened.

I was having the same issue. I tried most of the techniques on this page without luck.
I was finally able to fix it, but I had to remove all babel dependencies. Here are the steps I took:
npm uninstall everything with the word 'babel' (not sure if this is strictly necessary, but I was fed up)
npm install (to re-include the babel dependencies required by react-native)
/node_modules/react-native/packager/packager.sh start --reset-cache
--to get this to work, i actually had to run 'lsof -i :8081' and kill the PID using that port before

I was running into this issue last night. Some combination of --reset-cache and removing stage-1 and es2015 presets from my .babelrc seems to have resolved it. My .babelrc only has the react-native preset now, which is fine for my use case but I imagine that might not fly for everyone.

Hey everyone -
Please see this comment on how to possibly fix this issue (if you're trying to use babel-preset-react-native along with stage-0, stage-1, stage-2, or stage-3 presets).
https://github.com/facebook/react-native/issues/4844#issuecomment-204035720
Thanks,
-Adam

I'm with @balanceiskey. On RN 0.22.2 I removed es2015 and stage-0 presets and now only have the react-native presets. If I add either of the ones I removed I get the same error. Doesn't matter if you use --reset-cache, npm cache clean or not. I mean their may be lingering modules if you don't use those but the root is somewhere in using the es2015 or stage-0/stage1 presets I think.

@ekryski you're correct. Please see the comment I linked to above.

I run into this problem, and after several hours of research and trial and error, the solution that worked for me was using @skevy's package. Massive thanks to you sir

still facing this issue

Re-opening the issue. FYI I've only seen it happen when you've a dependency which is compiled using another preset other than react-native. It also happens if you've a .babelrc with a different preset under a subdirectory.

@satya164 I experienced the same thing just now. I have a dependency that is compiled using different presets. I was able to get it working by (a) installing the presets that the dependency needs npm install --save dev <whatever babel preset the error message says i'm missing> and (b) DO NOT add that preset to your .babelrc. I was able to add whatever other babel transforms I needed by adding the specific transforms to my .babelrc, but it seems if you add any other presets you end up with this or a similar error.

I had same problem with react-native 0.27.2 and react-native start --reset-cache works for me

I have the same problem with latest react-native and nothing works for me. Live Reloading works, but Bundling doesn't.
I tried

removing ALL .babelrcs that I use
deleting the caches (watchman and packager)
removing all node_modules and reinstalling them

Ok, I got to another bottom of this: https://github.com/facebook/react-native/issues/7850#issuecomment-227398161
(right now the react package also picks up .babelrc of unrelated dependencies in node_modules and breaks things)

+1 Is there any resolution on this?
The strange thing is that our Android app does work when on "DEBUG" mode but not when in "RELEASE" mode. I assume because the "iterator" works due to chrome dev tools being loaded?

The cause /solution in my case seems like it might be esoteric, but for the sake of completeness :
I was using a node_module (that I had myself created), and that node_module did not have an .npm_ignore file, thus the src as well as the .babelrc file were being unnecessarily included in the module as it was downloaded.
I added the appropriate .npm_ignore file to that module, included src and .babelrc in that file, republished the module, re-installed the module in my react-native app, and the problem was solved.

RN 0.33.0, same issue, ./node_modules/react-native/packager/packager.sh start --reset-cache does not seem to help.

I believe @marcellosachs solution is correct. A dependency that has a .babelrc in it will cause that .babelrc to get picked up by the react native packager. @ivanakimov I would try to figure out which npm module is the one that has a .babelrc in it (maybe like find ./node_modules -name .babelrc) and see if that can be removed or fixed.

Um pouco de Like
Em 05/10/2016 21:23, jeffgran<EMAIL_ADDRESS>escreveu:
I believe @marcellosachshttps://github.com/marcellosachs solution is correct. A dependency that has a .babelrc in it will cause that .babelrc to get picked up by the react native packager. @ivanakimovhttps://github.com/ivanakimov I would try to figure out which npm module is the one that has a .babelrc in it (maybe like find ./node_modules -name .babelrc) and see if that can be removed or fixed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/react-native/issues/5747#issuecomment-251836397, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ARNFs2seqIiJsL33fc9lE7TB_yRd9hMiks5qxD9rgaJpZM4HTHAv.

@jeffgran this is what I get when searching for .babelrc:
./node_modules/babel-preset-react-native/node_modules/babel-plugin-react-transform/.babelrc

(everything else is either in "test" or "lint" folders, I'm guessing those don't count?)

Huh. I don't know. My issue definitely seemed to be resolved when I figured out that multiple (incompatible) .babelrc files were being picked up. Maybe there are multiple causes of this issue.

Interestingly, I came here because I started getting this error after installing my npm dependencies with yarn. Using npm works fine. Installing with yarn, and then running my React Native project results in this error.

@hellogerard same. Tested yarn, it didn't install everything properly, went back to npm. Too new.

When this will be fixed or fix will be shipped/merged?

At this point this thread appears to be a number of unrelated issues globbed together with the original one fixed. I am going to close this issue and encourage people who still have something similar to open a new issue with repro steps that are specific to their app. Thanks folks!

@lacker I am having this exact issue.
Log
babelHelpers.typeof is not a function. (In 'babelHelpers.typeof(target)', 'babelHelpers.typeof' is undefined)
.babelrc
{
"presets": ["env","react-native"],
"plugins": [],
"sourceMaps": true
}

Deps
    "react": "~15.4.0-rc.4",
    "react-native": "0.40.0",
    "react-native-checkbox": "^1.1.0",
    "react-native-elements": "^0.9.2",
    "react-native-vector-icons": "^4.0.0"
  },
  "devDependencies": {
    "babel-cli": "^6.22.2",
    "babel-eslint": "^7.1.1",
    "babel-jest": "18.0.0",
    "babel-preset-env": "^1.1.8",
    "babel-preset-react-native": "1.9.1",
    "eslint": "^3.14.0",
    "eslint-config-react-native": "^1.6.0",
    "eslint-plugin-flowtype": "^2.30.0",
    "flow-bin": "^0.36.0",
    "jest": "18.1.0",
    "react-test-renderer": "~15.4.0-rc.4"
  }

In my case, i forget to set presets in .babelrc, add "react-native" as preset in .babelrc works

I just encountered this problem when adding the a dependency called redux-query.
Changing the redux-query .babelrc from:
{
    "presets": ["react", "es2015", "stage-2"]
}

To:
{
    "presets": ["react", "react-native", "stage-2"]
}

Made problem go away.


Fix issues with dict parameters of GET methods on python 3.8

Description
Some tests failed on python 3.8 because of the typing differences, this PR provides a fix.
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] ~Attached issue to pull request~
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] ~End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )~

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master in 409d2d852d7acecdde30f94a9afd2d23afa49d39

Processing #2800.


Implement Dynamic Exchange Fee

Description
Implement and calculate dynamic exchange fees on Kwenta. Two deliverables:

Calculate dynamic fee and show it if in effect next to the current base fee
Add a tooltip if the dynamic fee is in effect

Related issue
#300
Motivation and Context
SIP-184 introduces dynamic exchange fees which kick in during turbulent market periods in order to avoid front-running opportunities. The feature is currently in the testing phase.
How Has This Been Tested?

I tested it manually by choosing different currencies on the exchange page.
I also set the different totalFeeRate as input to see how it shows on the exchange page.
This change also affects the shorting page because TradeSummaryCard is shared by the exchange and shorting page.

Screenshots (if appropriate):

@JChiaramonte7 All the changes have been made as requested.
I am not able to update the new screenshot with the correct color of + because no asset is in dynamic fee mode now.

@JChiaramonte7 The baseFeeRate is optional now.


Small updates to the documentation

There are some issues building NumPy git on CI. I believe the NumPy 1.20 release is imminent, after which we won't need to build the git version on CI, so we can just wait for that.

Sounds like a good plan!


Replenish pool when release_conn=False and error occurred

Replaces #646
Fixes #644

@jlatherfold @Lukasa Please review.
Also need some more tests, I think socket-level. @Lukasa up for helping? <3 <3 <3

Alright, I snuck in some extra assertions into existing tests, good enough! Please review, then merging.

Some notes, but otherwise :+1:


Collision (and/or Signals) not working in Linux with Godot 4.1.x

Godot version
4.1.1 and 4.1.2
System information
Godot v4.1.2.stable - Ubuntu 22.04.3 LTS 22.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 SUPER (nvidia; 530.30.02) - AMD Ryzen 9 3900X 12-Core Processor (24 Threads)
Issue description
When signals are setup to be sent on enter or leaving a collision area (only testing in 2D so far), the code that should be run by the signal does not run.
The code involved is as follows:
extends Node2D

func _ready():
	pass # Replace with function body.

func _process(delta):
	pass

func _on_maze_area_exited(area):
	print("Area Exited")
	get_tree().reload_current_scene()

func _on_maze_area_shape_exited(area_rid, area, area_shape_index, local_shape_index):
	print("Area Exited")
	get_tree().reload_current_scene()

func _on_area_2d_area_entered(area):
	print("Telepad Entered")

func _on_area_2d_area_exited(area):
	print("Telepad Exited")

This is all I know to say.  I really don't know why its not work, but its very simple code and I can't imagine a non-bug-related reason it would not run.  This has been tried with both version 4.1.1 (initially) and then 4.1.2, in case the bug had been reported and fixed.

Thanks you.
Steps to reproduce
Create a node that can move with a collision shape 2d  (and  sprite render for visualization), I used a circle.  Then create another node with either a collision polygon 2d or another collision shape 2d.  Put a script to receive the signals on the root node of a scene acting as the level.  Add signals to the collision polygon and/or second collision shape to be sent to the script on the root node, and add some debug code to print when entered or exited.
Be sure there is a movement control script on the node containing the first collision shape, run the game, and move the object represented by that node into and out of the other collision shape(s).  Watch as nothing happens.
Minimal reproduction project
The full project  is here, in case someone needs it.  There are actually two versions, one using GD script and one using C#, though I doubt that matters; it is very minimal.

Please provide a proper MRP, a minimal project:

A small Godot project which reproduces the issue, with no unnecessary files included. Be sure to not include the .godot folder in the archive (but keep project.godot).
Drag and drop a ZIP archive to upload it. Do not select another field until the project is done uploading.
Note for C# users: If your issue is not Mono-specific, please upload a minimal reproduction project written in GDScript or VisualScript. This will make it easier for contributors to reproduce the issue locally as not everyone has a Mono setup available.

It looks like you are trying to detect if the player (a RigidBody2D) is entering the area, this is wrong, you need to use on_body_entered, see the documentation

Please see my comment, this isn't a bug, try changing to the correct signal

No trouble! But in the future, for support questions and help please first turn to the other community channels. Please use other channels first to see if this is a bug or user error.


Add a copy-resource to maven build

Description
ciDict.json has to be copied from the root folder to the java project. Refs. #13
Motivation & context
Refs. #14
Type of change

Refactoring/debt (improvement to code design or tooling without changing behaviour)

Looked good. Might want to delete this too:
https://github.com/cucumber/create-meta/tree/main/java/src/main/resources/io/cucumber/createmeta


Remove warning about missing SegmentKey in json mode

The Problem/Issue/Bug:
The warning about the missing SegmentKey generates a second obejct on output which causes it to be invalid for parsers.
How this PR Solves The Problem:
In json output mode the warning is no longer triggert.
Manual Testing Instructions:
Execute ddev describe -j on a self build ddev binary. The following warning must not appear:
{
  "level": "warning",
  "msg": "Instrumentation is opted in, but SegmentKey is not available.",
  "time": "2022-02-05T16:52:26+01:00"
}

Automated Testing Overview:
N/A
Related Issue Link(s):
N/A
Release/Deployment notes:
N/A

The warning is still shown in the human readable output of the commands:

Can be tested in gitpod

run ddev poweroff
edit .ddev/config.yml
set instrumentation_opt_in: true
run ddev start
run ddev describe
run dddev describe --json-output

Awesome. Let me know when you're happy with it and I'll pull (after tests run)

Awesome. Let me know when you're happy with it and I'll pull (after tests run)

Ready when you are

The weird thing here is that output.UserOut.Warning() should already have been outputting json and not breaking the json output. Maybe it's not properly initialized at this point.

I'm sure you already know that your code can set DDEV_NO_INSTRUMENTATION=true before interacting with ddev and also solve all this.


Ikea E1524/E1810 remote (ON/OFF) switch not working after rPi restart

Issue description
When I shutdown/start or restart my Raspberry Pi, the "E1524/E1810" remote (ON/OFF switch) in Domoticz does not respond anymore when I hit the on/off button of the physical remote. But when I restart the Zigbee2mqtt and Domoticz service in this order from the console the Switch is back to normal behaviour.
It looks like that is has something to do with the order of starting the mosquitto (zigbee2mqtt) and domoticz services because when I add a startup delay:
"DAEMON_ARGS="$DAEMON_ARGS -startupdelay 20"
to "sudo nano /etc/init.d/domoticz.sh", the behaviour after a Pi restart is also back to normal behaviour. (10 seconds are to short)
I have bound the remote to a group of bulbs in zigbee2mqtt, and only use the on/off switch to sync it with the group switch created in Domoticz.
All other zigbee2mqtt devices created with the plug-in have no issues
What could be the problem here?
Additional information
Zigbee2MQTT version: 1.14.3
Python version: 3.7.3
Domoticz version: 2020.2 (build 12230)
Plugin version: 0.2.0
Logs
Attach any additional logs here which might be useful: mqtt, domoticz, plugin logs

Looks like the same issue as #161

Looks like the same issue as #161


Support for uWsgi?

Hello, I want to use Dumper for backup but I have uWsgi as application server.
It's a bit strange but it's a good server and it's fast.
http://uwsgi-docs.readthedocs.org/en

I haven't seen any Rubyists using uWSGI. I'll keep this issue open to see if there's more demand than I thought, but a short answer is no support in the short term.
It does seem to support master = true in config/uwsgi.ini, which makes it possible to start the agent thread in the master process, so you might want to monkey patch these lines to see if it works. Start the agent before the fork and don't disconnect AR connection on the master.
https://github.com/kenn/dumper/blob/master/lib/dumper/stack.rb#L45-L47


Disconnect new nav from oss nav hooks and export it

Refs #3432
What's happening in here?
This is modifying and adding some components to OSS so they can be reused in Enterprise.
Why?
Engineers have been doing double the work divided between two frontends for a while, and although sometimes they do need to be different, we should aim to reuse when we can. Duplicating styles not only adds more code to sift through, but has the potential to introduce a ton of hard to track bugs when a component works one way in OSS, and another in Enterprise.
Summary of changes:

Icons that are added as separate components are done this way so that the svg can be modified with a class (other svgs that have been imported into the Icon component as static images can not be modified). They have to be added to the IconType enum to be used, which means they must be added in OSS if they are to be used in a component that is expecting an IconType.
State (collapsed, route) has been moved out of Nav and Logo and into Layout, allowing Enterprise to pass down it's own separate values to the components.
the disabled prop in Nav allows for Enterprise to show/hide nav items based on feature flags.
a lot of additions to index.ts, and it's been alphabetized automatically by my linter which is why there are a lot of changes...I didn't choose these settings so...not pointing any fingers...but someone doesn't have their linter configured.
I ordered theme.spacing since it's been bothering me for a looooong time.

❓  Testing this PR. Noticed that in OSS only the icon part of the logo is clickable (but not the "weavegitops" text image), while in enteprise the whole logo (icon + text image) is clickable. What is the desired behavior which should be supported by the shared Logo component?

💡 Would it be possible to make both the Collapse icon and "Collapse" text clickable to collapse the sidebar? Because not only the icon can be clicked for this, and it's small and hard to target.


chore: use regular env for docs publishing

Motivation
Make it easier for forks to test doc changes
Description
Do not depend on buildjet for docs deployment. This makes it a bit easier for forks to experiment and deploy docs changes.

:tada: This PR is included in v1.18.0 :tada:


Feature Popover is displayed on top of the Modal overlay

Describe the bug
When you click on the button to open the Modal window, the Feature Popover will be displayed above the overlay.
Code example
Open codesandbox
To Reproduce

Click on Open modal button
See error

Expected behavior
Feature Popover is displayed under the Modal overlay.
Additional context
z-index values:

z-index: var(--intergalactic-z-index-popper, 700);
z-index: var(--intergalactic-z-index-modal, 600);

Hi, basically it's an intended behavior that ensures that feature popover may be displayed over the modals.
You need to close all possible feature popovers while opening new modals.


[nghttp2] Work around two possible crashes.

Context: Our services received (invalid) HTTP2 streams with a disallowed connection header. This caused a nghttp2 error: Invalid HTTP header field was received: frame type: 1, stream: 23, name: [connection], value: [keep-alive] to be logged, but also caused our serving process to crash subsequently in onStreamCloseCallback. After that was worked around, doOneWrite was called with a negative length.
This patch does not fix the underlying issue, it only prevents a hard crash of the process until we can migrate to the non-nghttp2 implementation.

@swift-nio-bot test this please


TFlite shape

hello，
Computer environment:window 10 ;tensorflow 1.13.0; python3.6 ; tflite-runtime  2.1.0.post1;
save tflite code
def save(self):
converter = tf.lite.TFLiteConverter.from_session(self.session, [self.ts.x, self.ts.x_peak], [self.ts.logits])
tflite_model = converter.convert()
with open("model/" + cfg.name + '/model.tflite', "wb") as f:
f.write(tflite_model)
print('model is in {}'.format(self.save_path))
when I set the  the x ( input model) shape is [10, 1801, 2], it product tflite is right ,and   in the tflite input_details is [10, 1801, 2],however, I need the shape is [1, 1801, 2];So, when I set the x shape is [None, 1801, 2] ; but when I train the model, it is error that as follows
_Traceback (most recent call last):
File "C:/Users/Administrator/Desktop/mix/train.py", line 400, in
app.train(train_data, val_data)
File "C:/Users/Administrator/Desktop/mix/train.py", line 265, in train
ts.train_summary, ts.loss_summary], feed)
File "D:\Users\Administrator\anaconda3\envs\python36\lib\site-packages\tensorflow\python\client\session.py", line 929, in run
run_metadata_ptr)
File "D:\Users\Administrator\anaconda3\envs\python36\lib\site-packages\tensorflow\python\client\session.py", line 1128, in run
str(subfeed_t.get_shape())))
ValueError: Cannot feed value of shape (10, 1801, 2) for Tensor 'self.x:0', which has shape '(1, 1801, 2)'
I know the reason is that producting tflite cause x that change it's shape ；but I don't know how to solve it ;I sincerely hope you can understand my poor English！Thanks！！！

@xzy-666 ,
Can you please, fill issue template.Also, We see that you are using tf version 1.x which is not actively supported, please update to 2.x and in order to expedite the trouble-shooting process, could you please provide the complete code and dataset to reproduce the issue reported here.

+1 to the idea of upgrading to TensorFlow 2.x. TensorFlow Lite in TensorFlow 2.x should have good support of dynamic shape.
On the other hand, it seems you're running to some shape issues in your training script, which is not directly relevant to TensorFlow Lite. It's hard to help you without knowing what's the actually code you're running.

+1 to the idea of upgrading to TensorFlow 2.x. TensorFlow Lite in TensorFlow 2.x should have good support of dynamic shape.
On the other hand, it seems you're running to some shape issues in your training script, which is not directly relevant to TensorFlow Lite. It's hard to help you without knowing what's the actually code you're running.

hello, miaout17, thanks！！！
The problem is that the tflite-runtime does not adapt well to tensorflow1.x .So, I've converted offline and saved it as tflite model . however, I want to know why TensorFlow 1.x not  good support of dynamic shape.

@xzy-666 ,
As mentioned above tf v1.x is not actively supported, can you please try to execute the code in tf v2.x and let us know if you are facing same issue.Thanks!

@xzy-666 ,
As mentioned above tf v1.x is not actively supported, can you please try to execute the code in tf v2.x and let us know if you are facing same issue.Thanks!

@tilakrayal, hello
Shame to say, I'm not familiar with tensorflow 2.x. Can you provide some materials for learning tensorflow 2.0? I will master it as soon as possible.thanks!!!

@xzy-666 ,
Please refer this tensorflow website which provides the information on tensorflow latest versions.Link.
Please free free to move the issue to closed status as the issue has resolved.Thanks!


[crash] Something went wrong

Describe the bug
Steps to reproduce
Stacktrace
Cannot set properties of undefined (setting 'cluster')
The error may be correlated with this previous error:
TypeError: Cannot set properties of undefined (setting 'cluster')
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:331671:21
   at Array.forEach (<anonymous>)
   at Function.unflatten (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:331640:23)
   at mergeConfigs (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:59051:237)
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:58666:4928
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644675:25
   at memoized (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644583:20)
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644689:40
   at Object.memoized [as current] (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644583:20)
   at Object.checkForUpdates [as onStateChange] (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:634742:48)

TypeError: Cannot set properties of undefined (setting 'cluster')
The error may be correlated with this previous error:
TypeError: Cannot set properties of undefined (setting 'cluster')
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:331671:21
   at Array.forEach (<anonymous>)
   at Function.unflatten (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:331640:23)
   at mergeConfigs (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:59051:237)
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:58666:4928
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644675:25
   at memoized (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644583:20)
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644689:40
   at Object.memoized [as current] (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644583:20)
   at Object.checkForUpdates [as onStateChange] (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:634742:48)

   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:331671:21
   at Array.forEach (<anonymous>)
   at Function.unflatten (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:331640:23)
   at mergeConfigs (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:59051:237)
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:58666:4928
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644675:25
   at memoized (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644583:20)
   at file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644689:40
   at memoized (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:644583:20)
   at useSelectorWithStoreAndSubscription (file:///C:/Program%20Files/Kubeshop/Monokle/resources/app.asar/build/bundle.main.js:634709:30)

Hello @HarshS1611 , thank you for reporting this crash!
If possible, could you please help us with some more details of how this happened and how it can be reproduced?

The application got crashed when I was providing a new path for the minikube cluster kubeconfig file . After I selected the folder after few seconds the application got crashed .

Thank you @HarshS1611 , we are investigating the problem.

Hi @HarshS1611, we released the 1.7.5 version of Monokle which includes a fix for this error.
You can download it here: https://github.com/kubeshop/monokle/releases/tag/v1.7.5
I'm closing this issue but please let us know if the problem persists after 1.7.5.
Thank you!


Disable card authentication

Is your feature request related to a problem? Please describe.
We would like to disable card authentication for users. it looks as though this can be disabled when confirming a payment through the api for confirm payment.
It looks like we can enable error_on_requires_action and to disable card auth. This however isn't available in the react native sdk
Describe the solution you'd like
Can the error_on_requires_action be made available through the sdk
Describe alternatives you've considered
Allow params that are not listed in the sdk to be passed to the endpoint

Hi there! You should pass this on the server-side when you create the payment intent. See these docs for an example: https://stripe.com/docs/payments/without-card-authentication


Cm4370 write script to move a visualization from one host to another

This closes CartoDB/cartodb-management#4370.

@javisantana @jgoizueta CR this, please.

@javisantana , @jgoizueta , ping ^

I only miss the documenttion in operations -> https://github.com/CartoDB/cartodb/tree/master/doc/manual/source/operations

Sure, I'll document it as soon as it's merged :+1:

So when you want to import an exported visualization (json), you have to change the vis. id.
The owner id is replaced by the import process, but I see there are also uuids for layer ids and stat_tag. Do they need to be manually changed too?

@jgoizueta I should've given you some context.
This is not meant to be a 100% generic solution for all export/import use cases (although it's quite close) but a first step that covers this: CartoDB/cartodb-management#4370. I've just documented it as well, you'll find some additional explanation here: CartoDB/cartodb#6353.
Being a "visualization mover" is the reason why the user id is requested: we want to move a visualization among users, so the user must be changed. You don't need to change any id (including visualization one) if servers are different. In case of export/import inside the same server you must change all ids. I've documented it in the operations manual.

:+1: OK everything seems fine to me


Don’t build SourceKitLSPPackageTests in build-script-helper’s build action

Building SourceKitLSPPackageTests with cross-compilation enabled fails with
error: Could not find target named 'SourceKitLSPPackageTests_586B622B321A3B86_PackageProduct'
error: fatalError

For testing, we work around this by disabling cross-compilation. This is not possible for building, so we need to explicitly build all products.
This fixes a current toolchain build failure.

@swift-ci Please test

Merging this now to unblock the Swift package bot.


[feat] add default user-agent

Modelled it after curl. Should a resources/BABASHKA_HTTP_CLIENT_VERSION be used?

The version is stored in deps.edn but I guess that's not part of the deployed stuff.
Perhaps we can add babashka.http-client.impl.version.clj with (ns ..) (def version ...) and make a script to refresh this by reading the deps.edn?

I'll take care of that version.clj thing.

Added the version.clj now

incorporating it now

Can you maybe not use force push? :)

Can you maybe not use force push?

Yeah that was the main rebase. Will merge next time.

I added a PR template now. Can you update the changelog?

🙏


Cannot import name autheticate

I try to using mg connector with neo4j
File "/Users/signorini/Jobs/www/maestro/mongo-connector/lib/python3.6/site-packages/mongo_connector/doc_managers/neo4j_doc_manager.py", line 16, in
from py2neo import Graph, authenticate
ImportError: cannot import name 'authenticate'
py2neo == 4.0.0
mongo-connector==2.5.1
more-itertools==4.2.0
neo4j-doc-manager==1.0.0.dev11
neo4j-driver==1.6.0
Made some searchs, i find some anwsers, but this is new version, with same problems..

Same error. Any solution?

Same Error Any Solution

I found the solution
This is problem of py2neo version4
Uninstall current version
pip uninstall py2neo
Install versipn 2.0.8
pip install py2neo==2.0.8
I worked for me!!!
Hope it work for you!!!

I was running into same error with py2neo 4.1.0 ... uninstalled then installed v2.0.8 as @HelloDivyani mentioned and worked ... seems to be a bug in v4

In v4, instead of using auth, I connect using the following:
graph = Graph(host=HOST, auth=(USER, PASS))


Add strigazi to reviewers

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

/ok-to-test

/approve

/lgtm

Merged in #39.
Please close.

Thanks


fix: preload query error

Fix: #760
Description
Upon deploying to Cloudfare workers, we are occasionally getting this error:

On further investigation, this happens when we try to preload an expired Cache item from Cloudfare.

Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance.

The fix for this is to make sure we delete the attempted query with the error response and let React render cycle retry on its own.
How to test this
This error is easily reproducible with a Cloudfare worker.

Create your own personal Cloudfare account
Follow the deploy to Cloudfare instructions
Setup local debugging with wrangler https://blog.cloudflare.com/profiling-your-workers-with-wrangler/

Before submitting the PR, please make sure you do the following:

[x] Run yarn changeset add to update the changelog, if needed
[ ] Read the Contributing Guidelines
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[ ] Update docs in this repository for your change, if needed

@wizardlyhel in your profiling/testing, did you observe at least some of the preloads succeeding? Or were they all broken?

@jplhomer All preloading was working if the request is within the max-age time.
Currently, our project is set to preload all useShopQuery calls with different cache control headers. All the ones with long max-age time works just fine. All the ones with 1 second max-age fails in the next load.


Window Blinds ( up down ) via rf

I have all house motorised blinds via rf remote controllers
But they are just two buttons: up and down
Also you do not need to keep the button pressed
You just press down briefly once and the blind will go down till either has all gone down or you press up to stop it at the position has arrived/you desire
Similarly for up
I have tried putting the up and down codes in both the garage door open close and blind open close samples of the config-sample.json
But for both garage and blind buttons it doesn't work properly
When I start homebridge , the blind goes down as it reports last state was down ( it physically send the down command ) but when I try pull it up it doesn't send the rf command
So I pull it up with the real original blind remote and goes fully up. Now that it is up I try to send it down with the HomeKit but does' t go down , it isn't the hex code because when I start homebridge it managed to pull it down ( to be in sync with last known state )
I cannot understand what's wrong
I couldn't program with a code the stop , because my system has two different stop commands:
When blind is going up the stop command is a down command , and when is going down the stop is au up command , it could be an idea to define two stops one for up and one for down and users that have just one stop put the same code in both , or if it is omitted the stop it means that a reverse direction command must be sent out.
To solve without changing your coding is there a way to define a "pulse RF" type button that just sends an rf command ( stateless ) e.g. Blinds up
Thanks

I'm getting mad, I have copied the rf codes of my blinds up down into the TV channel up down of the sample-config json file and the two buttons channel up down work so I can control the blind as on the original blind remote , tested it and every time I press the buttons instantly the blind reacts.
I then tried via Siri voice commands ,  on the raspberrypi terminal I see the command accepted and the send rf code but the blind doesn't react
Can you pls help...

Hello, I have the same problem..

Hey, can you post your config please and I'll take a look.

Closing, if you'd still like help please re-open