Error on last version of sails.js

When i tried $ sails generate scaffold services //for example..
i obtain this error:
node_modules/sails-generate-scaffold/Generator.js:102
var modelAttributeNames = _.pluck(scope.modelAttributes, 'name');
TypeError: _.pluck is not a function
at Object.module.exports.before (/.../node_modules/sails-generate-scaffold/Generator.js:102:33)
at generate (/usr/lib/node_modules/sails/node_modules/sails-generate/lib/generate.js:73:13)
at module.exports (/usr/lib/node_modules/sails/node_modules/sails-generate/lib/index.js:112:3)
at Command.module.exports (/usr/lib/node_modules/sails/bin/sails-generate.js:107:10)
at Command.listener (/usr/lib/node_modules/sails/node_modules/commander/index.js:301:8)
at emitTwo (events.js:87:13)
at Command.emit (events.js:172:7)
at Command.parseArgs (/usr/lib/node_modules/sails/node_modules/commander/index.js:615:12)
at Command.parse (/usr/lib/node_modules/sails/node_modules/commander/index.js:458:21)
at Object. (/usr/lib/node_modules/sails/bin/sails.js:145:9)

I had the same problem. Any advice?

I resolve this error TypeError: _.pluck is not a function by this:
1 - path_to_my_server/sailsTest/node_modules/sails-generate-scaffold/
npm install underscore
2 - add in the top of Generator.js
_.pluck = require('underscore');
but then comes another in this lines:
compiledNewFlash = compiledNewFlash.replace(/ERBstart/g, '<%')
compiledNewFlash = compiledNewFlash.replace(/ERBend/g, '%>')
it said that replace is not a function.
I also resolve that by:
1 - path_to_my_server/sailsTest/node_modules/sails-generate-scaffold/
npm install replace
2 - add in the top of Generator.js
var replace = require("replace");
3 - add this between var NEW_FLASH_TEMPLATE = path.resolve(__dirname, './templates/any template in the file generator.js')
and this NEW_FLASH_TEMPLATE = fs.readFileSync(NEW_FLASH_TEMPLATE, 'utf8').
note: you can also change ERBstart and ERBend directly in the temlates files and don't have to do this.
replaceInFile({
    regex: "ERBstart",
    replacement: "<%",
    paths: [NEW_FLASH_TEMPLATE],
    recursive: true,
    silent: true,
});

replaceInFile({
    regex: "ERBend",
    replacement: "%>",
    paths: [NEW_FLASH_TEMPLATE],
    recursive: true,
    silent: true,
});

4 - coment this 2 lines in all the Generation.js file
compiledNewFlash = compiledNewFlash.replace(/ERBstart/g, '<%')
compiledNewFlash = compiledNewFlash.replace(/ERBend/g, '%>')
but then I get this error with the lodash.js package.
I don't know what to do and I need a CRUD generator for a sails project. I'm thinking in create my own generator from the scratch.

Solution:
npm install underscore
Insert following code in node_modules/sails-generate-scaffold/Generator.js line 12:
_.pluck = require('underscore');
my_template = _.template;
_.template = function(arg1, arg2) {
  return my_template(arg1)(arg2);
}

Solution:
Change this line
var modelAttributeNames = _.pluck(scope.modelAttributes, 'name');
by this line
var modelAttributeNames = _.map(scope.modelAttributes, 'name');

yes facing the same problem as well but @marlonscalabrin solution fixed the problem

nearly 3 years and this problem is still not fixed, sails is dead.


Add Intel-specific development instructions

@alexbaden  is this work still onging ?

@etiotto this PR is needed, not a first priority for July though. For more details see linked issue:

#1393

I have made the requested updates - I suggest we merge and refine as needed.

What about using wiki (https://github.com/intel/intel-xpu-backend-for-triton/wiki) for documents like this? The editing process is simpler (no CI runs, reviews) and more user-friendly (UI editor in the browser).


Virtual hard disk files must be uncompressed

Please fill out the below information:

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.18917.1000]

What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

The error message as below
PS E:\temp> wsl --set-version kali-linux 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The requested operation could not be completed due to a virtual disk system limitation.  Virtual hard disk files must be uncompressed and unencrypted and must not be sparse.

What's wrong / what should be happening instead:

Set a distro to be backed by WSL 2 using the command line

Duplicate of #4103.


About Consuming Native Views.

Recommendations Concerning this line :
xmlns:androidLocal="clr-namespace:SimpleColorPicker.Droid;assembly=SimpleColorPicker.Droid;targetPlatform=Android"
clr-namespace : You'll Find it in MainActivity.cs (Android Project)
assembly : You'll find it in AssemblyInfo.cs ( Android Project) .
Copy them carefully instead of wasting an hour wondering what went wrong.
Your Intellisense will not Help  , because this Xaml is not Compiled. Don't get suspicious.
Remeber to Add the Instance Property to your MainActivity.cs . Check the github sample.

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

ID: a781e5d5-c0c4-4bc0-2049-97442139bee3
Version Independent ID: 94e2df3f-c624-98d8-2edb-ef98134835b9
Content: Native Views in XAML - Xamarin
Content Source: docs/xamarin-forms/platform/native-views/xaml.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @davidbritch
Good advice!


Adds Numeric#finite? / Numeric#infinite? and Complex impl

Part of #473
Feature #12039, Numeric#finite? and Numeric#infinite?
This covers both the base class Numeric and subclass Complex with finite? and infinite? as the methods were implemented in both classes as part of #12039.
There are some oddities with mspec's == matcher when comparing against Complex negative infinity, which is why Complex#infinite? and Complex#finite?  have different test structures.  I kept the structure consistent within the tests of each file, however.

Added two specs for Complex#infinite? and Complex#finite? and clarified real vs imaginary parts of the Complex.

There are some oddities with mspec's == matcher when comparing against Complex negative infinity, which is why Complex#infinite? and Complex#finite? have different test structures. I kept the structure consistent within the tests of each file, however.

What oddities did you notice? #infinite? returns -1/nil/1 and not true/false like #finite?.

This is nice and complete specs, thank you @cadwallion!

The oddity I found was this:
irb(main):004:0> value = -Complex(Float::INFINITY, 42).infinite?
=> -1
irb(main):005:0> value = -Complex(Float::INFINITY, 42) ; value.infinite?
=> 1

Ah, right, because the unary minus applies to the whole expression, not just the Complex() method.

:+1:

My only question is that we should verify that NaN.{in}finite? makes sense. It should probably raise.

Bah, that behavior has been there for years apparently, so I'd let it slide.

Sorry for the noise. Looks like Complex & Float give opposite results for NaN.finite? which means there should probably be a fix in Ruby. I opened https://bugs.ruby-lang.org/issues/14014


Fix #199

Root cause is not properly following section 2.e of the cp spec. The bug itself is encountered if the file system lists D/D before D/a.

Here is the failure after testing this issue199 branch:

     Running tests/tree-tests.rs (target/release/deps/tree_tests-48a52f9cf418fb37)

running 111 tests
test cp::test_cp_dir_slash ... ok
test cp::test_cp_deref ... ok
test cp::test_cp_dir_vs_file ... ok
test cp::test_cp_childproof ... ok
test cp::test_cp_fail_perm ... FAILED
test cp::test_cp_into_self ... ok
test cp::test_cp_hl ... ok
test cp::test_cp_special_bits ... ignored
test cp::test_cp_i_2 ... ok
test cp::test_cp_i ... ok
test cp::test_cp_thru_dangling ... ok
test cp::test_cp_special_f ... ok
test cp::test_cp_r_vs_symlink ... ok
test link::link_already_exists ... ok
test link::link_create ... ok
test cp::test_cp_trailing_slash ... ok
test cp::test_cp_part_symlink ... ok
test ls::test_ls_empty_directory ... ok
test ls::test_ls_infloop ... ok
test ls::test_ls_file_type ... ok
test ls::test_ls_no_arg ... ok
test ls::test_ls_dangle ... ok
test ls::test_ls_recursive ... ok
test ls::test_ls_rt_1 ... ok
test ls::test_ls_m_option ... ok
test mkdir::test_create_single_directory ... ok
test ls::test_ls_inode ... ok
test mkdir::test_directory_already_exists ... ok
test mkdir::test_invalid_mode ... ok
test ls::test_ls_size_align ... ok
test mkdir::test_set_directory_mode ... ok
test cp::test_cp_proc_short_read ... ok
test mv::test_mv_atomic2 ... ok
test mv::test_mv_atomic ... ok
test cp::test_cp_same_file ... ok
test mv::test_mv_dir2dir ... ok
test mv::test_mv_dir_file ... ok
test mv::test_mv_hard_4 ... ok
test mv::test_mv_hardlink_case ... ignored
test mv::test_mv_hard_2 ... ok
test mv::test_mv_childproof ... ok
test mv::test_mv_force ... ok
test mv::test_mv_i_1 ... ok
test mv::test_mv_i_link_no ... ignored
test mv::test_mv_dup_source ... ok
test mv::test_mv_i_5 ... ok
test mv::test_mv_hard_link_1 ... ok
test mv::test_mv_i_2 ... ok
test mv::test_mv_into_self ... ok
test mv::test_mv_i_4 ... ok
test mv::test_mv_into_self_3 ... ok
test mv::test_mv_into_self_4 ... ok
test mv::test_mv_part_fail ... ok
test mv::test_mv_into_self_2 ... ok
test mv::test_mv_perm_1 ... ok
test mv::test_mv_part_hardlink ... ok
test mv::test_mv_partition_perm ... ok
test mv::test_mv_sticky_to_xpart ... ignored
test mv::test_mv_symlink_onto_hardlink_to_self ... ok
test mv::test_mv_special ... ok
test mv::test_mv_symlink_onto_hardlink ... ok
test mv::test_mv_to_symlink ... ok
test mv::test_mv_part_symlink ... ok
test readlink::test_readlink_non_existent_file ... ok
test mv::test_mv_part_rename ... ok
test readlink::test_readlink_not_a_symlink ... ok
test mv::test_mv_trailing_slash ... ok
test readlink::test_readlink_valid_symlink ... ok
test readlink::test_readlink_valid_symlink_no_newline ... ok
test rm::test_rm_cycle ... ok
test rm::test_rm_dir_no_w ... ok
test rm::test_rm_dir_nonrecur ... ok
test rm::test_rm_dot_rel ... ok
test rm::test_rm_empty_inacc ... ok
test rm::test_rm_f_1 ... ok
test rm::test_rm_fail_2eperm ... ignored
test rm::test_rm_empty_name ... ok
test rm::test_rm_i_1 ... ok
test rm::test_rm_fail_eacces ... ok
test rm::test_rm_i_no_r ... ok
test rm::test_rm_ignorable ... ok
test rm::test_rm_ir_1 ... ok
test rm::test_rm_inaccessible ... ok
test rm::test_rm_no_give_up ... ignored
test rm::test_rm_dangling_symlink ... ok
test rm::test_rm_r_4 ... ok
test rm::test_rm_r_3 ... ok
test rm::test_rm_r_root ... ok
test rm::test_rm_rm1 ... ok
test rm::test_rm_rm2 ... ok
test rm::test_rm_rm3 ... ok
test rm::test_rm_rm4 ... ok
test rm::test_rm_rm5 ... ok
test rm::test_rm_sunos_1 ... ok
test rm::test_rm_unread2 ... ok
test rm::test_rm_readdir_bug ... ok
test rm::test_rm_unread3 ... ok
test rmdir::rmdir_remove_directory_with_parents ... ok
test rmdir::rmdir_remove_existing_directory ... ok
test rm::test_rm_unreadable ... ok
test rmdir::rmdir_remove_non_empty_directory ... ok
test rmdir::rmdir_remove_non_existent_directory ... ok
test unlink::unlink_remove_directory ... ok
test unlink::unlink_remove_existing_file ... ok
test unlink::unlink_remove_non_existing_file ... ok
test rm::test_rm_deep_2 ... ok
test mv::test_mv_leak_fd ... ok
test rm::test_rm_hash ... ok
test ls::test_ls_time ... ok
test cp::test_cp_preserve_slink_time ... ok
test rm::test_rm_isatty ... ok

failures:

---- cp::test_cp_fail_perm stdout ----
thread 'cp::test_cp_fail_perm' panicked at plib/src/testing.rs:68:5:
assertion `left == right` failed
  left: "cp: Permission denied\n"
 right: "cp: cannot open '/home/jgarzik/repo/posixutils-rs/target/tmp/test_cp_fail_perm/D/a' for reading: Permission denied\n"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    cp::test_cp_fail_perm

test result: FAILED. 104 passed; 1 failed; 6 ignored; 0 measured; 0 filtered out; finished in 3.08s

error: test failed, to rerun pass `-p posixutils-tree --test tree-tests`

This fails on Linux in a new way:

---- cp::test_cp_fail_perm stdout ----
thread 'cp::test_cp_fail_perm' panicked at tree/tests/cp/mod.rs:348:34:
called `Result::unwrap()` on an `Err` value: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    cp::test_cp_fail_perm

test result: FAILED. 105 passed; 1 failed; 6 ignored; 0 measured; 0 filtered out; finished in 3.09s

Also tested on MacOS.  All tests pass.  No regressions.

Forgot to reset the permissions for DD like in test_cp_issue199. Latest commit is the same as the previous plus the said modification:
@@ -342,7 +342,7 @@ fn test_cp_fail_perm() {
         1,
     );

-    for f in [test_dir, d, d_a] {
+    for f in [test_dir, d, d_a, dd] {
         fs::set_permissions(f, fs::Permissions::from_mode(0o777)).unwrap();
     }
     fs::remove_dir_all(test_dir).unwrap();

Testing successful, well done.
Fixed #199


Minitest exit value

To incorporate this gem as part of a CI process, the tests suite should return a non-success exit code when coverage failed.
For minitest, ignoring thresholds (considering anything bellow 100% a failure), this block inside the minitest.rb could be enough:
  if $covered.policy.each.flat_map(&:counts).detect { _1&.zero? }
    Kernel.exit(1)
  end

A similar behavior is found in simplecov: https://github.com/simplecov-ruby/simplecov/blob/b6c2d4208a5fa395ce09d7e1d3b074f680ee29b0/lib/simplecov.rb#L239

Do you want to make a PR?

Sure, I will try!

You should check out the coverage tasks that I use for this purpose too:
Basically, 0 or more tasks which generate coverage, and a final task which merges it all together and validates it according to some required percentage: https://github.com/socketry/async/actions/runs/11737730374/job/32699033302

@ioquatix, thanks for the reference sir, I just added the PR #33 using the Covered::Statistics class as you are using in the bake tasks.
I chose to not set the Kernel.exit directly because the #validate! already raises and error and this is enough.


Unable to connect to TX SFTP location

Email sent to TX asking for help troubleshooting.
"Good Afternoon,
As of the last few hours we have been unable to connect to the the SFTP location to send ReportStream reports for TX. We are getting a socket closed exception. Are there any known issues or configuration changes that may be impacting our ability to deliver reports? Please let us know if this is a known outage or if further investigation is needed.
Thanks,
James Gilmore"

[1;31m19:26:43.210 [pool-2-thread-216][1355] FATAL-ALERT gov.cdc.prime.router.azure.SendFunction - FAILED Sftp upload of inputReportId bab428da-bd32-47f4-bd22-2bc1f296ecbc to SFTPTransportType(host=sftp-edts.hhs.texas.gov, port=22, filePath=./, credentialName=null) (orgService = tx-doh.elr), Exception: Socket closed, All retries failed.  Manual Intervention Required.  Send Error report for: bab428da-bd32-47f4-bd22-2bc1f296ecbc to tx-doh.elr[m


add job and pod wellknownStatusRules

Signed-off-by: Zhiwei Yin<EMAIL_ADDRESS>

/assign @qiujian16


Remove compiler warning

Overview
Fix compiler warning about unused variable.
Testing recommendations
successful compilation would be sufficient
Related Issues or Pull Requests
N/A
Checklist

[x] Code is written and works correctly
[ ] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

+1


All Inline-Table-Rolls results are null.

As of the latest Foundry update (V11 Stable Build 308) Inline Table Rolls has stopped working and only returns null for the result.

Came to report the same.


TypeError: Cannot read property textContent of null when you expect a property on a missing element queried by data-testid

react-testing-library version: 1.0.1
node version: n/a
npm (or yarn) version: n/a

Relevant code or config
expect(queryByTestId('greeting-text').textContent).toBe('hello there')

What you did:
Did not render the element with 'greeting-text' identifier.
What happened:
TypeError: Cannot read property textContent of null
Reproduction repository:
https://codesandbox.io/s/4q3zol71y9
Problem description:
The error does not describe what has gone wrong.
Suggested solution:
Throw a user-friendly error.

Thanks for filing this @sompylasar!
For more context, here's what the error looks like when I make a typo in a similar test:

TypeError: Cannot read property 'textContent' of null

  18 | test('calling render with the same component on the same container does not remount', () => {
  19 |   const {container, queryByTestId} = render(<NumberDisplay number={1} />)
> 20 |   expect(queryByTestId('number-displays').textContent).toBe('1')
  21 |
  22 |   // re-render the same component with different props
  23 |   // but pass the same container in the options argument.

  at Object.<anonymous>.test (src/__tests__/number-display.js:20:10)

The fact that Jest will call out the line number where the error happened makes the problem less concerning for me. I think that people will understand what went wrong.
And just to be clear for everyone, we're not throwing any errors, this is a regular JavaScript error (trying to read textContent on null). I think the error output makes it clear where that's happening. As to answering why that's happening, I think that could be improved.
For the benefit of everyone else, I talked with @sompylasar about this already. He asked if we could throw an error in queryByTestId when the element wasn't found and I explained that would break this use case:
expect(queryByTestId('foo')).not.toBeTruthy()

Where you're trying to assert that something does not exist.
So one thing's for sure: We will not be changing the current behavior.
However, it would be nice to improve the error message. One suggestion @sompylasar made is we could create a new function called queryByTestIdRequired, but first off I doubt many people will use it so we lose the benefits there, and secondly I'd prefer to avoid expanding the API unless it's absolutely necessary.
Another idea I had is to create custom expect matchers that people can use in their apps that could throw more helpful error messages:
expect(queryByTestId('foo')).not.toBeInTheDOM()
expect(queryByTestId('number-display')).toHaveTextContent('1')

I don't think I'll work on these myself, but I would be happy to accept a contribution that adds this capability with a simple API :)

@kentcdodds: I give it a shot, the implementation looks like the following:
expect.extend({
    toBeInTheDOM(received) {
        if (received) {
            return {
                message: () =>
                    'expected the dom to be present',
                pass: true,
            };
        } else {
            return {
                message: () => 'expected the dom not to be present',
                pass: false,
            };
        }
    },
})

expect.extend({
    toHaveTextContent(htmlElement,checkWith) {
        console.log(htmlElement.textContent)
        let pass = htmlElement.textContent === checkWith;
        if (pass) {
            return {
                message: () =>
                    `expected ${htmlElement.textContent} not equals to ${checkWith}`,
                pass: true,
            };
        } else {
            return {
                message: () => `expected ${htmlElement.textContent} equals to ${checkWith}`,
                pass: false,
            };
        }
    },
})

And I used in fetch.js test cases like:
expect(queryByTestId('foo')).not.toBeInTheDOM()
expect(queryByTestId('greeting-text')).toBeInTheDOM()
expect(queryByTestId('greeting-text')).toHaveTextContent('hello there')

Everything was green! If you find this good enough, then I can export these functions as a simple API. By the way thanks for a neat small library. The flushPromises is simple & intelligent away to wait for fetch calls.

@antoaravinth
        console.log(htmlElement.textContent)
        let pass = htmlElement.textContent === checkWith;
        if (pass) {
            return {
                message: () =>
                    `expected ${htmlElement.textContent} not equals to ${checkWith}`,
                pass: true,
            };
        } else {
            return {
                message: () => `expected ${htmlElement.textContent} equals to ${checkWith}`,
                pass: false,
            };
        }

I'd suggest retrieving htmlElement.textContent once at the first line and storing in a variable. It's not syntactically guaranteed to not change by the time the message function is called.

@sompylasar Agreed and it was a quick implementation for you guys to review. Will take care when I raise a PR.

Another suggestion: a generic matcher
.toMatchDOM(el => el.textContent === 'hello')

where el is guaranteed to exist or it fails; for safety and clarity, the exceptions from within the matching function can also be caught and enhanced with "the DOM element did not match" hint.

@sompylasar I like this idea, as we are allowing the user to pass their own assert function to execute in the current assertion context.

I'd rather it be called: .toSatisfyDOM
There's a toSatisfy in jest-extend, so it would make sense to follow the naming convention there.

Another related issue with the queryByTestId is with the TypeScript definition. It's declared that it can return HTMLElement | null which is true, but prevents me from being able to write the kind of simple code documented for this library. Just like this issue mentions the runtime error if the queried-for element is null, with TypeScript projects, these lines all become compile-time errors because of this possible scenario.
The rejected proposal of throwing an error would resolve this issue as well since it would no longer return null. Alternately, changing the type declaration in an incorrect way to specify that it doesn't return null might also be a reasonable solution to this problem. I'm not worried about these runtime errors being thrown as this library should only be used in a testing environment where errors thrown are likely to result, correctly, in test failures.
What are your thoughts on this problem? I lean towards fudging the type declaration as the developer experience is really bad when null can be returned.

What if you just write a small wrapper around the render method inside your test/project that throws an error if it's null?

What if you just write a small wrapper around the render method inside your test/project that throws an error if it's null?

For the same reason I would use a 29-lines react-testing-library instead of having the small wrappers it provides inside my test/project.

Yeah, I don't love that idea as it creates a reasonable amount of friction for devs. I think it's very similar to how you imported and re-exported react-dom APIs in this library to ease the friction. Having teams learn and use this library, but getting them to not use the render function in favor of some other wrapper we have is probably a deal breaker in terms of making things easy for them.
Also, how do you feel about the code exhibited in this library not being possible for the many teams that are writing typed JavaScript, either via Flow or TypeScript? I realize those teams are probably still in the minority, but likely not an insignificant percentage. As such a consumer, I'd prefer to see the type definitions relaxed (made incorrect) to ease the development at the cost of type-safety in error scenarios for our tests.
One other option I will explore, that you might prefer, is to overwrite the type definitions for this library in my project. I still feel like this is a hack and that it's not better than changing the definitions in this library itself, but at least would offer up another alternative.

Ok, here are a few ideas:
Add options to queryByTestId:
const queryByTestId = render(<MyThing />)
expect(queryByTestId('foo', {throwIfMissing: true})).toBeTruthy()

Add getByTestId:
const queryByTestId = render(<MyThing />)
expect(getByTestId('foo')).toBeTruthy()

I'm not huge on the idea of expanding the API for something like this, but I appreciate the usefulness to some teams. And honestly, if we did this, I'd probably recommend people use this. Most of the time you wont want the return value to be null. I just appreciate the minimal abstraction that queryByTestId is on top of querySelector.
Anyway, I think I'd accept a PR that:

Adds docs for getByTestId
Updates existing examples and tests to getByTestId
Adds at least one test for queryByTestId that can assert expect(queryByTestId('foo')).toBeFalsy()
Implements getByTestId as a minimal abstraction over queryByTestId that throws a useful error message (tested with toThrowErrorMatchingSnapshot()) when the returned element is null.

I think this will make everyone happier :)

Thanks @kentcdodds, that sounds reasonable to me. I'll start throwing together a PR.

@kentcdodds Well, do you want to me to raise a PR for these methods:
toBeInTheDOM
toHaveTextContent
toSatisfyDOM

Where do you want me to place these extensions? index.js should be fine?

How about you do this:

Create a jest-extensions.js file in src where you put the source for those. This should not make calls to expect.extend but instead just be the extension objects themselves.
Create an extend-expect.js file in the root of the repository. This file will not be transpiled and should use Node 8 compatible functions (basically that means just use CommonJS instead of ESM). That file should actually do the expect.extend calls. It should also require files from the dist directory (you'll probably need to disable some ESLint rules (import/*) in the file for this to work when the dist directory doesn't exist, like on a fresh clone).
Add ./extend-expect.js to the files list in the package.json so it's included when publishing.
Add some tests :) I think I'd prefer just regular tests against actual rendered DOM nodes. You could probably update some existing tests.

What do you think?

If I understand things correctly, it should be the following approach:

Only the extension objects, like:

{
    toBeInTheDOM(received) {
        if (received) {
            return {
                message: () =>
                    'expected the dom to be present',
                pass: true,
            };
        } else {
            return {
                message: () => 'expected the dom not to be present',
                pass: false,
            };
        }
    },
}

Call expect.extend from jest-extensions.js to actually extend the jest stuff. require the jest-extensions.js (commonjs system) from dist to make this happen.

3 & 4 seems to be fine. I'm wondering why there is a split up on logic in these two files? Why can't be in a single shot and have a test cases for the same? Any benefit we get with the split up?

The reason to split it up is so people can just do this in their test files:
import 'react-testing-library/extend-expect'

It's explicit, but it's really easy. And it means that if someone wanted to use them differently, or only use one of them, they could:
import {toBeInTheDOM} from 'react-testing-library/dist/jest-extensions'

expect.extend({toBeInTheDOM})

Gives a bit more flexibility without sacrificing usability.

@kentcdodds Ahh, that make sense to me. Will do the same and raise a PR. Thanks!

Ok, @pbomb's PR was merged. A release should be out soon and you'll be able to use getByTestId :+1:

For the record, the link to PR: https://github.com/kentcdodds/react-testing-library/pull/10

I think we've dealt with this :+1:

@sompylasar, if you'd like to make a pr to add yourself to the contributor table you're more than welcome. You can follow the instructions in the CONTRIBUTING.md :+1:

@kentcdodds Thanks!

👉 https://github.com/kentcdodds/react-testing-library/pull/29


Added tbTextSearch tests -> NOT WORKING

Check tubular API to make tbTextSearch e2e to work...

Coverage remained the same at 97.753% when pulling aebfb9ab4ea01848bf0bd094185a9272a77938b8 on roberttapia:master into 9bec4746cab2fdad9ae9e4e6342c79b43419fc25 on unosquare:master.


[NBS] NonreplicatedPartitionRdmaActor implementation lacks volume mode and checkpoint checks

When processing read/write request the NonreplicatedPartitionActor checks for volume mode (is read only/ has broken device) and whether checkpoint support is needed.
https://github.com/ydb-platform/nbs/blob/f0bfcb041e1d1c01ced1edd994832656d0974aa8/cloud/blockstore/libs/storage/partition_nonrepl/part_nonrepl_actor.cpp#L140
This functionality is missing from NonreplicatedPartitionRdmaActor

checkpoint checks are implemented at the volume level: https://github.com/ydb-platform/nbs/blob/4320a453409b4d97922839017b91a969fa1baebe/cloud/blockstore/libs/storage/volume/volume_actor_forward.cpp#L682
seems that we need to fix only the volume mode check

@budevg do we need to do anything else regarding this issue?

No everything was done in #559 ... closing the issue


"Too many lines in translated script" error

Hi..
I get "Too many lines in translated script" error during insertlocal command after I'm done translating script.xlsx
What's wrong and what should I do?

sometimes I also get ""Not enough lines in translated script" error
Can someone tell me what this errors mean and what should I do to fix them?

It means your .xlsx file contains either more or less lines (or character names) than are in the original scenario file.

It means your .xlsx file contains either more or less lines (or character names) than are in the original scenario file.

Hi.. so I actually found the real culprit.. we can't translate "／" to "/".. I replace all the "/" back to "／" then everything back to normal

Right - VNTextPatch treats half-width slashes in character names as a separator. This is to handle cases where one line has two names attached: a real one and a displayed one (e.g. "Kirino/???"). If you replace a full-width slash in a name by a half-width one, VNTextPatch will think there are now two names and raise an error.
If needed, you can change this separator in ExcelScript.cs.

@arcusmaximus I'm getting this error even though I edited one (1) line. (YU-RIS engine)

@kokoiro Please create a new ticket and attach the scripts of the game where you get the error.


Add PropertyValueType attribute to help models builder #49

Guess this means single item mode won't work properly then as our resolver can resolve multiple value types.

@zpqrtbnk Can you offer any advice on how we could handle multiple value types?
e.g. our ValueConverter could return either an IEnumerable<IPublishedContent> or a single IPublishedContent

I imagine two property value converters would be needed. However the "IsConverter" method has no context of value so it could not be done at run time.
I suppose it opens the discussion into if a single property editor should be returning two different types though. Its easy in code to .FirstOrDefault() if you know there is only going to be one. but that's a breaking change now.

Yea. Guess it just sucks as these are new rules that weren't a requirement
previously.
Yes we could just return enumerable, but would make the code a bit uglier.
Don't think it'll be possible to have converters for the same PE though.

@mattbrailsford it may be possible just looking at the converter actually.
the single return works on min/max item pre-values so splitting the converter in two should be possible. I have 30 mins if you want me to look at another pull request?

Who am I to stop you :)

@cwjackso By all means, please do :sunglasses:

Ok, that works nicely! I've pulled some logic out into static extensions but thought that would be cleaner than extending the converter?
Thanks

Have you tested it in non-models builder manner? ie, from within a normal view can you still do Model.GetPropertyValue< IEnumerable< IPublishedContent>>("alias") and Model.GetPropertyValue< IPublishedContent>("alias")

@mattbrailsford I think they should be okay, as GetPropertyValue extension method is a wrapper for GetProperty("alias").Value.TryConvertTo<T> (obviously that's "in a nutshell" :wink:) ... so the PVC returns the appropriate object-type and TryConvertTo<T> attempts to cast/convert it accordingly.

It's cool, I'm just throwing things out there as they come to mind, not really with any backing :)

Nice work @cwjackso though on such a fast fix

Like a fool I only tested the model building and hadn't tested the retrieval at all. I wasn't returning the converted value in either converter!
The last commit is now tested for retrieval via both strong typed model and .GetPrpertyValue(). As @leekelleher says they are essentially the same thing though.
Thanks

Never hurts to double check :) Nice work fella :clap:


Ignore alpha materials in baked light ray-tracer.

I made this PR a while back but there was a syntax error on certain GCC compiler setups, and I ended up forgetting about it. Either way, the issue should be resolved now, and this small update simply allows the light baker rays to ignore transluscent surfaces like windows, ect.

Assigning to @reduz for review.

Needs rebasing it seems. And of course stills has to be reviewed.. :)

light baker no longer exists in 3.0 (was replaced by GIProbe), so closing this


Unable to expand all nodes on init

export class ConversationBuilderComponent implements OnInit {
nodes = [];
@ViewChild('tree') tree: TreeComponent;
@Component {
nodes = [...];
@ViewChild('tree') tree;
ngAfterViewInit() {
this.tree.treeModel.expandAll();
}
}
}

Hi @Chaitanya009,
You can use initialized option
<tree-root
      #tree
      [nodes]="nodes"
      [options]="customTemplateStringOptions"
      [focused]="true"
      (event)="onEvent($event)"
      (initialized)="onInitialized(tree)">

onInitialized(tree) {
    setTimeout(() => {
           tree.treeModel.expandAll();
        });
  }

Note -  Expand All on init can be expensive for big tree,
Please specify your exact requirement to help you out.
Thanks
Abhi

<tree-root #tree [nodes]="nodes" [focused]="true" (initialized)="onInitialized(tree)">
  onInitialized(tree) {     setTimeout(() => {        tree.treeModel.expandAll();     });   }
I have tried this it didin't work

For me it's working, can you try to expandAll event on button click? and see whether its working or not.
I assume you are loading child asynchronous

I want to expand tree on loading of component

thanks, it did work after setting delay


[BEAM-5355] Add GroupByKeyLoadTest

This commit adds the test with all neecssary setup required to run itmanually.
The following GroupByKey load test can be run on all runners using the following command (example is for flink):
./gradlew run -p sdks/java/load-tests -PloadTest.args='--fanout=5 --iterations=1 --sourceOptions={"numRecords":1000,"splitPointFrequencyRecords":1,"keySizeBytes":10,"valueSizeBytes":20,"numHotKeys":3,"hotKeyFraction":0.3,"seed":123456,"bundleSizeDistribution":{"type":"const","const":42},"forceNumInitialBundles":100,"progressShape":"LINEAR","initializeDelayDistribution":{"type":"const","const":42}} --stepOptions={"outputRecordsPerInputRecord":2,"preservesInputKeyDistribution":2,"keySizeBytes":10,"valueSizeBytes":20,"numHotKeys":3,"hotKeyFraction":0.3,"seed":123456}} --runner=FlinkRunner' -Prunner=":beam-runners-flink_2.11" -PloadTest.mainClass="org.apache.beam.sdk.loadtests.GroupByKeyLoadTest"

Runner can be changed by altering the runner-related properties. We can also add --flinkMaster=localhost:8081 to run this on a separate flink cluster (not in memory).
You can skip the syntieticStep pipeline option. Example for dataflow runner:
./gradlew run -p sdks/java/load-tests -PloadTest.args='--fanout=5 --iterations=1 --sourceOptions={"numRecords":1000,"splitPointFrequencyRecords":1,"keySizeBytes":10,"valueSizeBytes":20,"numHotKeys":3,"hotKeyFraction":0.3,"seed":123456,"bundleSizeDistribution":{"type":"const","const":42},"forceNumInitialBundles":100,"progressShape":"LINEAR","initializeDelayDistribution":{"type":"const","const":42}} --runner=DataflowRunner' -Prunner=":beam-runners-google-cloud-dataflow-java" -PloadTest.mainClass="org.apache.beam.loadtests.GroupByKeyLoadTest"

@pabloem could you take a look? I know there is a separate PR for this but it was easier to completely rebuild the pr due to the fact that now it does not require Perfkit and runs from the main code. I didn't develop any method of publishing the metrics to BigQuery - this needs a follow up pull request (is it ok?).
CC: @echauchot

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

So that it's not forgotten, quoting from the other pr:

I'd just add one or a couple distribution metrics to count time spent blocked, waiting to load the iterable with the values (e.g. time of first iteration, time of all iterations). WDYT?

This should be done after we have a way to connect to BigQuery on which I'm working on right now. WDYT?

Your proposal to have a follow up PR sounds good. I'll take a look at the code now.

This change looks good to me. We had already reviewed many parts of it. Please go ahead an self merge.


DRILL-6652: PartitionLimit changes for Lateral and Unnest

This PR includes some commits which are not part of PartitionLimit fix. Please ignore those commits. Here are the list of commits to be ignored.
DRILL-6616: Batch Processing for Lateral/Unnest
DRILL-6619: Lateral changes for implicit column  …
DRILL-6618: Unnest changes for implicit column  …
DRILL-6617: Planner Side changed to propagate $drill_implicit_field$ … …
The commits which pertain to ParitionLimit build upon the above commits, hence these are included in this PR. While merging this PR please cherry-pick only the below relevant commits and then merge them accordingly.
As regards to other commits which are related to execution changes for PartitionLimit, @parthchandra  can you please review the changes.
@amansinha100 Please review the planner side changes for handling PartitionLimit.
i.e DRILL-6636: Planner side changes to use PartitionLimitBatch in place …
The expectation is that this PR should have two +1's before merging to master branch.

+1 for the DRILL-6636 (commit 9351cc6b6d593fedefc4411d0cd9a95dc89eb152).  cc @HanumathRao .

@amansinha100  Thank you for the review. I have corrected the name in LimitPrel.

@HanumathRao can you correct the PR's title to carry the JIRA number as the leading text??

@sohami - Once PR-1401 is merged in master, we should rebase this PR on top of it and remove the commits from that PR. Also make sure to add a commit to remove all ignores from TestE2EUnnestAndLateral.

Rebased on latest master.
Removed Ignores from TestE2EUnnestAndLateral
Squashed 2 commits related to DRILL-6636 since it's approved


AppCompactDependancy Issue

I think you used compile 'com.android.support:appcompat-v7:25.1.0'
please come back to compile 'com.android.support:appcompat-v7:25.0.1'
becz, in appcompat : 25.1.0  fragment getSupportFragmentManager().popBackStack(); have a bug and it's not working perfectly...

Can't you just use a different version in your code? I don't think the version is enforced by a library (or is it?). You can always exclude it if that helps https://discuss.gradle.org/t/excluding-dependencies-from-dependent-projects/4506.

Had similar problem, conflict with the support lib, fixed with:
compile ('com.futuremind.recyclerfastscroll:fastscroll:0.2.5') {
        exclude module: 'appcompat-v7'
        exclude group: 'com.android.support'
    }

Hope it helps,
cheers


Added a small change to increase readability

ℹ Repository information
The repository has:

[ ] At least three issues with the good first issue label.
[ ] At least 10 contributors.
[ ] Detailed setup instructions for the project.
[ ] CONTRIBUTING.md
[ ] Actively maintained.

@mxnuchim I guess the current statement is clear and doesn't need to change. Thus, closed the PR. Thanks!


Improve the ERPL environment to use fgetc() instead of fgets()

Reading a string at once could be dangerous as there is no way to validate the input stream of data if it comes as a block of string.
With the use of fgetc(), we have a means to validate all incoming characters one at a time which gives us the means to do more checks to the string that is being read via the STDIN.

The line could be longer than 1024, (or smaller) and if the first byte fgets  read is a null \0 it'll returns an uninitialized buffer which will causes UB.
The idea is to read each char into a ByteBuffer that'll dynamically resize till we reach a new line or EOF, this will prevent any potential vulnerability. (See: https://stackoverflow.com/a/314422/10846399 for a reference).
But thanks for the PR.
And I've just opened a "good first issue" with a walkthrough on how to add tokens to the pocketlang parser here #70, if you're interested.

@ThakeeNathees, thanks for the context given. As for reading of the line using fgetc(), that has been done.
I'm only worried a little bit about the realloc()'ing every time once the size is greater than 1024. I can go ahead and implement that but I wanted to be sure that the current PR is an improvement from fgets() with the use of fgetc().
Once you confirm and merge this, I'll make another PR with the resizing of the mem buffer :)

I'm only worried a little bit about the realloc()'ing every time once the size is greater than 1024

That's why we have to use the 'ByteBuffer' which will only be double its size, once it's filled. You can use this PR to implement it  I'll open an issue on how to do it (and how the byte buffer works), by tomorrow.

Will close this and open a new PR with the agreed solution.


Version 1.6.5 is not available at https://pypi.org/project/keras2onnx/#history

I am trying to install version 1.6.5 of this library but it is not available at https://pypi.org/project/keras2onnx/#history.
Should I add another package manager in my system?

Sorry, due to some process issue, the package publish in pypi.org has been postponed for couple weeks.
You can try it from https://github.com/onnx/keras-onnx/releases or install it from the code with a version tag like pip install<EMAIL_ADDRESS>

@wenbingl thanks for the information.
In order to work I had to execute also "pip install<EMAIL_ADDRESS>

keras2onnx 1.7.0 is released now.


[0.9.2] Graphite plugin not closing connection and running out of file descriptors

I wrote a script to import data from influxdb-0.8.8 to influxdb-0.9.2 and it was running out of file descriptors I increased open files limit, but I am afraid it won't be enough:
[root@TIAGO-TEST1 test]# while true; do echo $(date) - $(lsof -nP  | grep influx | wc -l);sleep 60; done
Tue Aug 25 14:55:19 UTC 2015 - 482
Tue Aug 25 14:56:19 UTC 2015 - 557
Tue Aug 25 14:57:19 UTC 2015 - 633
Tue Aug 25 14:58:19 UTC 2015 - 708
Tue Aug 25 14:59:19 UTC 2015 - 784
...
Tue Aug 25 15:18:24 UTC 2015 - 2212
Tue Aug 25 15:19:24 UTC 2015 - 2288
Tue Aug 25 15:20:24 UTC 2015 - 2364
Tue Aug 25 15:21:25 UTC 2015 - 2439
Tue Aug 25 15:22:25 UTC 2015 - 2515

All connections are hanging on CLOSE-WAIT state:
[root@TIAGO-TEST1 ~]# ss -ntp | grep influx | awk '{print $1}' | sort | uniq -c
   2613 CLOSE-WAIT

To import the data I am sending several 1K lines file to netcat on port 2003, data is being imported well so far.
Version:
[root@TIAGO-TEST1 ~]# rpm -qa | grep influx
influxdb-0.9.2-1.x86_64

You can't either re-use the connection or close out the connections? We can have timeouts on the TCP listener, but if the client is behaving badly (like in this case) then even then it's going to run out of fds.

@pauldix  I am not sure the client is to blame, connections do not hang if I use netcat as dummy server:
nc -l 2003 -k > /dev/null

@tlopo, could you please share PCAP dumps of your two scenarios? Just TCP
handshakes and resets / closes will do. Thanks!
On 26 Aug 2015 8:15 am, "tlopo"<EMAIL_ADDRESS>wrote:

@pauldix https://github.com/pauldix I am not sure the client is to
blame, connections do not hang if I use netcat as dummy server:
nc -l 2003 -k > /dev/null
—
Reply to this email directly or view it on GitHub
https://github.com/influxdb/influxdb/issues/3830#issuecomment-134757717.

Ok the pcap follows this pattern for both scenarios:
11:37:48.815296 IP <IP_ADDRESS>.59894 > <IP_ADDRESS>.2003: Flags [S], seq<PHONE_NUMBER>, win 43690, options [mss 65495,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 7], length 0
11:37:48.815316 IP <IP_ADDRESS>.2003 > <IP_ADDRESS>.59894: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 43690, options [mss 65495,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 7], length 0
11:37:48.824248 IP <IP_ADDRESS>.59894 > <IP_ADDRESS>.2003: Flags [FP.], seq 24577:66190, ack 1, win 342, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 41613
11:37:48.835674 IP <IP_ADDRESS>.59894 > <IP_ADDRESS>.2003: Flags [FP.], seq 24577:66190, ack 1, win 342, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 41613

But I found the culprit, in one of my testes I have set idle timeout to 0, so although the client was sending the FIN packet it was not waiting for the FIN-ACK before creating a new connection, The dummy server worked fine because there was no idle timeout as it was not processing data.
I will re-use the connection as Paul suggested. Thanks for your help!


Problem running code for Tapo P110

The following code works on my ubuntu machine, but does not work on my Macbook pro laptop:
from PyP100 import PyP110

p110 = PyP110.P110("192.168.X.X", "<email address>", "<password>") #Creates a P110 plug object

p110.handshake() #Creates the cookies required for further methods
p110.login() #Sends credentials to the plug and creates AES Key and IV for further methods

print(p110.getDeviceInfo()) #Returns dict with all the device info of the connected plug
print(p110.getDeviceName()) #Returns the name of the connected plug set in the app

When I run this code on the Macbook I get the following error:
/Users/robafett/PycharmProjects/BatterySaver/venv/bin/python /Users/robafett/PycharmProjects/BatterySaver/smart_plug_test2.py
Traceback (most recent call last):
  File "/Users/robafett/PycharmProjects/BatterySaver/venv/lib/python3.9/site-packages/requests/models.py", line 910, in json
    return complexjson.loads(self.text, **kwargs)
  File ["/usr/local/Cellar/python@3.9/3.9.6/Frameworks/Python.framework/Versions/3.9/lib/python3.9/json/__init__.py"](mailto:/usr/local/Cellar/python@3.9/3.9.6/Frameworks/Python.framework/Versions/3.9/lib/python3.9/json/__init__.py), line 346, in loads
    return _default_decoder.decode(s)
  File ["/usr/local/Cellar/python@3.9/3.9.6/Frameworks/Python.framework/Versions/3.9/lib/python3.9/json/decoder.py"](mailto:/usr/local/Cellar/python@3.9/3.9.6/Frameworks/Python.framework/Versions/3.9/lib/python3.9/json/decoder.py), line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File ["/usr/local/Cellar/python@3.9/3.9.6/Frameworks/Python.framework/Versions/3.9/lib/python3.9/json/decoder.py"](mailto:/usr/local/Cellar/python@3.9/3.9.6/Frameworks/Python.framework/Versions/3.9/lib/python3.9/json/decoder.py), line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/robafett/PycharmProjects/BatterySaver/smart_plug_test2.py", line 8, in <module>
    print(p110.getDeviceInfo()) #Returns dict with all the device info of the connected plug
  File "/Users/robafett/PycharmProjects/BatterySaver/venv/lib/python3.9/site-packages/PyP100/PyP100.py", line 256, in getDeviceInfo
    decryptedResponse = self.tpLinkCipher.decrypt(r.json()["result"]["response"])
  File "/Users/robafett/PycharmProjects/BatterySaver/venv/lib/python3.9/site-packages/requests/models.py", line 917, in json
    raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: [Errno Expecting value] 200 OK: 0

I am a Java programmer and am not familiar enough with Python to interpret this stacktrace to solvefind the issue. I use the same version of the library (newly installed on the ubuntu machine and updated to the newest on the Macbook, where it has worked before) and also identical credentials on both machines.

I found out that the versions were not entirely the same, even after I updated the library on the Macbook using the suggested command. Removed the library and added it again and it works now. So closing this issue.


Add consistent classes to all overlays.

This adds a consistent class hierarchy to all overlays on the site with
a top level class of .overlay, and a content wrapper of
.overlay-content (optional).
Fixes: #4036.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

This seems to throw an exception when flipping to/from the administration tab.

Not sure I ever saw the bug but it isn't present in the current build anymore at least.

Updated!

The latest push fails the casper tests.

Yep, it's fixed.

Merged, thanks @brockwhittaker!!


websocket compress

Hello.
Do you plan to support websocket extension - "permessage-deflate"  ?

Sorry. There is no plan at present.


Standardize error handling for dataset API

I went looking for a related info fidesops but couldn't pin down what you meant. Maybe create an issue to document or implement this.
Originally posted by @ssangervasi in https://github.com/ethyca/fides/pull/782#discussion_r903174350

Oh right, more context here: https://github.com/ethyca/fides/pull/772#discussion_r900690619
Basically I believe we want to marshal our error responses through type predicates in order for the code to know what type of error we received and how to display it. I did this on the fidesops side (really I was just trying to fix linting, but typescript was unhappy about the error parsing, so I went down this rabbit hole) https://github.com/ethyca/fidesops/blob/main/clients/admin-ui/src/features/common/helpers.ts

Closed by https://github.com/ethyca/fides/pull/896


Handle exception in span wrappers

Proposed changes
If the LLM throws an error, the return value could be null.
The code was throwing exception. This PR prevents the exception.
Types of changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added the necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

no longer required as changes incorporated in https://github.com/monocle2ai/monocle/pull/51


Add hooks for valid memory accesses

For the most part, just create a Z3 predicate Valid(n) that takes a memory access, and asserts that it is a valid access.
The tough part is adding Valid(k) assertions, which typically result either from being at some reasonable offset from SP, or being part of an allocation, which would look something like

if malloc(n) was called, then either the result is 0 or forall k <= n, Valid(res + k)

This is also important for the gdb output. Currently it does produce values out of memory, but it ignores the default value and uses invalid memory locations for actual x86

Closed with #260.


Add HTTP Request and Response Logging

This PR introduces a new logging feature for HTTP requests and responses. It adds a new abstract logger interface in the abstractions package, implements it in the HTTP package, and integrates it with the HttpxRequestAdapter.
Changes:

Add new abstract RequestResponseLogger class
Implement HttpxRequestResponseLogger in HTTP package
Integrate logger in HttpxRequestAdapter
Add JSON formatting support for log messages
Update relevant tests

Files changed:

/packages/abstractions/kiota_abstractions/request_response_logger.py (new file)
/packages/http/httpx/kiota_http/httpx_request_response_logger.py (new file)
/packages/http/httpx/kiota_http/httpx_request_adapter.py
/packages/serialization/json/kiota_serialization_json/json_serialization_writer.py
/packages/http/httpx/tests/test_httpx_request_adapter.py

I will take a look


Can't use online.visualstudio.com (Version mismatch)

Suddenly out of nowhere, VS Code Online stopped working.
Existing tickets did not help me to solve the issue.
This is the error code:

Failed to connect to the remote extension host server (Error: Connection error: Version mismatch, client refused.)

Any suggestions? Thanks in advance.

Please file this issue against VS online: https://github.com/MicrosoftDocs/vsonline/issues/new


Ability to Hide Entities - "Sending Single Client Data"

Major SpongeAPI version
8
Is this likely to be a breaking change?
I don't know
What are you requesting?
Back in API 7 there was talk of implementing functionality that was in Bukkit's API to Sponge.
https://github.com/SpongePowered/SpongeAPI/issues/1614
I feel that continuing to neglect this functionality is severely limiting the capabilities that Sponge servers have in comparison to their Spigot counterparts. It would be fantastic if this issue could be brought back up for the current API as the ability to hide entities would allow for more Wynncraft MMO-type servers that utilize Sponge/SpongeForge.
Again referencing the previous issue, "Sponge does have Player only Block support with Player.sendBlockChange(Vector3i, BlockState);" and I would hope that implementing the aforementioned capability with that in mind should easily allow for
[ ] Player only Time
[ ] Player only Weather
[ ] Player only Entity

Closing as it's a duplicate of #1614... Why would you open a new issue to just reiterate what was requested and linked......


React-helmet crashes with the hook useEffect

Hi.
I was just trying out hooks for the first time and I noticed that when I use Helmet on a component that has the hook useEffect, it crashes with maximum call stack size exceeded error:
Uncaught RangeError: Maximum call stack size exceeded
    at isUndefinedOrNull (index.js:27)
    at objEquiv (index.js:44)
    at push../node_modules/deep-equal/index.js.module.exports (index.js:23)
    at objEquiv (index.js:96)
    at push../node_modules/deep-equal/index.js.module.exports (index.js:23)
    at objEquiv (index.js:96)
    at push../node_modules/deep-equal/index.js.module.exports (index.js:23)
    ...

I fixed the issue by using props on the Helmet component, instead of using children.
Before:
<Helmet>
    <title>test</title>
</Helmet>

After:
<Helmet
    title="test"
/>

Any ideas why this is happening? Seems to be related to #373
Thanks.

Have you tried this on the 6.0.0-beta release? I would suspect it's related to #373 instead of hooks.

Have you tried this on the 6.0.0-beta release? I would suspect it's related to #373 instead of hooks.

No not yet. I just ended up using the title prop.

Check my comment https://github.com/nfl/react-helmet/issues/373#issuecomment-447561484

the issue seems to be solved with v6.0.0-beta. tested with react 16.8

In fact, I am experiencing this with just using useState in my component (useEffect is not present)
Changing my title from a children component to a title prop fixed it without having to upgrade my Helmet package.

This happened to me today. Solved it by upgrading to v6.0.0-beta.

HI guys, I'm facing the same issue with useEffect and react-helmet. I've updated to v6.0.0-beta but is still failing.

Same issue here, upgraded to 6.0.0-beta but using a hook with Helmet fails with a Maximum call stack size exceeded

I had to use defaultTitle and description props to avoid the problem.

Fixed in 6.0.0-beta 👌

This appears to also be solved in the v5 branch with v5.2.1. That release also switched from the deep-equal package to react-fast-compare. Upgrading from v5.2.0 to v5.2.1 solved this issue for me.
yarn upgrade -L react-helmet

Neither 5.2.1 nor 6.0.0-beta fixed it for me. Still getting the following error:
Uncaught RangeError: Maximum call stack size exceeded
    at Array.sort (native)
    at objEquiv (http://localhost:3001/static/js/6.chunk.js:92895:6)
    at push../node_modules/deep-equal/index.js.module.exports (http://localhost:3001/static/js/6.chunk.js:92833:12)
    at objEquiv (http://localhost:3001/static/js/6.chunk.js:92906:10)
    at push../node_modules/deep-equal/index.js.module.exports (http://localhost:3001/static/js/6.chunk.js:92833:12)
    [..]
    at objEquiv (http://localhost:3001/static/js/6.chunk.js:92906:10)
    at push../node_modules/deep-equal/index.js.module.exports (http://localhost:3001/static/js/6.chunk.js:92833:12)
    at objEquiv (http://localhost:3001/static/js/6.chunk.js:92906:10)
static/js/6.chunk.js:222713 The above error occurred in the <HelmetWrapper> component:
    in HelmetWrapper (at LauncherWindow.tsx:139)
    in AppWindow (created by ConnectFunction)
    in ConnectFunction (at MyWindow.tsx:138)
    in MyWindow (created by ConnectFunction)
    in ConnectFunction (at Route.tsx:28)
    in Route (at Route.tsx:37)
    in Route (at routes.tsx:18)
    in Switch (at App.tsx:20)
    in Suspense (at App.tsx:18)
    in Router (at Router.tsx:16)
    in Router (created by ConnectFunction)
    in ConnectFunction (at App.tsx:17)
    in App (at src/index.tsx:38)
    in ThemeProvider (at src/index.tsx:37)
    in Provider (at src/index.tsx:36)

Upgrading from v5.2.0 to v5.2.1 solved this issue for me.

A tag/release for 5.2.1 isn't on GitHub, but the version is on npm. What's the difference between 5.2.0 and 5.2.1?

@OliverJAsh version 5.2.1 wasn't tagged, but you can see the diff here, assuming the commit is the same thing that was published on NPM. The only real difference appears to be replacing deepEqual with isEqual.
https://github.com/nfl/react-helmet/compare/4d28f7045bc75724b904d2b63a06b7c0a81fe387...release/5.2.0


Training deep SNNs with DECOLLE

Objective of issue:
Implementation of the training algorithm DECOLLE (Kaiser et al. 2020)
Lava DL version:

[ ] 0.3.0 (feature release)
[ ] 0.2.1 (bug fixes)
[x] 0.2.0 (current version)
[ ] 0.1.2

I'm submitting a ...

[ ] bug report
[x ] feature request
[ ] documentation request

Current behavior:
Currently, only training with SLAYER is implemented and documented.
Expected behavior:
As per the desire of the developers to provide a general framework for neuromorphic computing, I believe that it would be great if Lava implemented training of deep SNNs via a variety of algorithms. In that sense, the naming of the training library (lava.lib.dl.slayer) would also benefit from evolving in future iterations, e.g. as lava.lib.dl.training. In the PR linked to this issue, I have implemented training of SNNs via DECOLLE.
Other information:
A PR is linked to this issue.

@nskat closing this issue for now as we have not much progress on licensing situation.


dnSpy-x86 points to 64bit binary instead of 32 bit.

actual location of dnSpy-x86 binary (32bit) is C:\Program Files (x86)\dnspy-x86. Bit it points to "C:\Program Files (x86)\dnspy\dnSpy.exe" which loads 64bit binary. Attaching screenshot

Updated, pleased reinstall the package via:

choco upgrade dnspy.flare


glTF 2.0 specification coverage of Rhodonite

It may be useful to have a list of supported glTF 2.0 on the top page.
The following is a checklist of items that I believe are currently supported. If there are any errors, please point them out.
glTF 2.0

Encodings

[x] Embeded
[x] Binary

Primitive Types

[ ] Points
[x] Lines
[ ] Line Loop
[ ] Line Strip
[x] Triangles
[ ] Triangle Strip
[x] Triangle Fan

Animation

[x] Transform animation
[x] Linear interpolation
[x] Morph animation

[x] Sparse accessor

[x] Skin animation
[x] Joint animation

Extensions

[x] KHR_draco_mesh_compression
[ ] KHR_lights_punctual
[ ] KHR_materials_clearcoat
[x] KHR_materials_pbrSpecularGlossiness
[ ] KHR_materials_sheen
[ ] KHR_materials_transmission
[x] KHR_materials_unlit
[x] KHR_mesh_quantization
[x] KHR_texture_transform

For reference, I have listed the current support status. I think Rhodonite can support glTF display except for some extensions.
Format Tests

Format and Sample Model
RhodoniteTS v0.3.8

glTF 2.0Duck/glTF
:white_check_mark: Sample

glTF 2.0 (Embedded resources)Duck/glTF-Embedded
:white_check_mark: Sample

glTF 2.0 (Binary container) Duck/glTF-Binary
:white_check_mark: Sample

KHR_draco_mesh_compression Duck/glTF-Draco
:white_check_mark: Sample

KHR_mesh_quantization Duck/glTF-Quantized
:white_check_mark: Sample

KHR_texture_basisu FlightHelmet/glTF-BasisU
:x: Sample

Simple models for testing individual features

Model
Screenshot
RhodoniteTS v0.3.8

Triangle Without Indices

:white_check_mark: Sample

Triangle

:white_check_mark: Sample

Animated Triangle

:white_check_mark: Sample

Simple Morph

:white_check_mark: Sample

Simple Sparse Accessor

:white_check_mark: Sample

Animated Morph Cube

:white_check_mark: Sample

Animated Morph Sphere

:white_check_mark: Sample

Simple Material

:white_check_mark: Sample

Simple Meshes

:white_check_mark: Sample

Simple Texture

:white_check_mark: Sample

Cameras

:white_check_mark: Sample

Simple Skin

:white_check_mark: Sample

InterpolationTest

:white_check_mark: Sample

More complex models

Model
Screenshot
RhodoniteTS v0.3.8

Box

:white_check_mark: Sample

Box Interleaved

:white_check_mark: Sample

Box Textured

:white_check_mark: Sample

Box Textured Non Power Of Two

:white_check_mark: Sample

Box Vertex Colors

:white_check_mark: Sample

Duck

:white_check_mark: Sample

2 Cylinder Engine

:white_check_mark: Sample

Reciprocating Saw

:white_check_mark: Sample

Gearbox Assy

:white_check_mark: Sample

Buggy

:white_check_mark: Sample

Box Animated

:white_check_mark: Sample

Cesium Milk Truck

:white_check_mark: Sample

Rigged Simple

:white_check_mark: Sample

Rigged Figure

:white_check_mark: Sample

Cesium Man

:white_check_mark: Sample

Fox

:white_check_mark: Sample

BrainStem

:white_check_mark: Sample

Virtual City

:white_check_mark: Sample

PBR Models

Model
Screenshot
RhodoniteTS v0.3.8

Avocado

:white_check_mark: Sample

Barramundi Fish

:white_check_mark: Sample

Boom Box

:white_check_mark: Sample

Corset

:white_check_mark: Sample

Damaged Helmet

:white_check_mark: Sample

Flight Helmet

:white_check_mark: Sample

Lantern

:white_check_mark: Sample

Water Bottle

:white_check_mark: Sample

Sponza

:white_check_mark: Sample

Further PBR Models

Model
Screenshot
RhodoniteTS v0.3.8

Two Sided Plane

:white_check_mark: Sample

Cube

:white_check_mark: Sample

Animated Cube

:white_check_mark: Sample

Suzanne

:white_check_mark: Sample

Sci Fi Helmet

:white_check_mark: Sample

Antique Camera

:white_check_mark: Sample

Feature Test Models

Model
Screenshot
RhodoniteTS v0.3.8

Alpha Blend Mode Test :warning:glTF-Sample-Models#221

:white_check_mark: Sample

Boom Box With Axes

:white_check_mark: Sample

Metal Rough Spheres

:white_check_mark: Sample

Metal Rough Spheres(Textureless)

:white_check_mark: Sample

Morph Primitives Test

:white_check_mark: Sample

Multi UV Test

:white_check_mark: Sample

Normal Tangent Test

:white_check_mark: Sample

Normal Tangent Mirror Test

:white_check_mark: Sample

Orientation Test

:white_check_mark: Sample

Texture Coordinate Test

:white_check_mark: Sample

Texture Settings Test

:white_check_mark: Sample

Vertex Color Test

:white_check_mark: Sample

Extension Test Models

Model
Screenshot
RhodoniteTS v0.3.8

KHR_materials_clearcoat Clear Coat Test

:x: Sample

EXT_lights_image_based Environment Test

:x: Sample

KHR_lights_punctual Lights :warning:glTF-Sample-Models#210

:x: Sample

KHR_materials_variants Materials Variants Chair

:x: Sample

KHR_materials_variants Materials Variants Shoe

:x: Sample

KHR_materials_pbr SpecularGlossiness SpecGloss vs MetalRough

:x: Sample

KHR_texture_transform Texture Transform Test

:white_check_mark: Sample

KHR_texture_transform Texture Transform Multi Test

:x: Sample

KHR_materials_transmission Transmission Test

:x: Sample

KHR_materials_unlit Unlit Test

:white_check_mark: Sample

KHR_materials_sheen KHR_materials_variants Sheen Chair

:x: Sample

KHR_materials_sheen Sheen Cloth

:x: Sample

KHR_materials_sheen  KHR_materials_transmission KHR_materials_clearcoat Toy Car

:x: Sample

KHR_materials_specular (Experimental) KHR_materials_ior (Experimental)Toy Car Specular

:x: Sample

Thank you @cx20 . This is very helpful!


Bm homepage drawer update

Changelog:

Change defaultActiveKey and activeKey settings to get different tiers to stay open once selected

 Elizabeth's Feedback - be able to open all drawers on homepage


Usage guide (connect to FPS device)

Hello,
Are there any guide to initialise the device and connect to it?
I tried import the sample flow but it doesn't connect to the FPS device.
Please advice, thanks.
Regards,
Les

Is your fingerprint supported by libfprint?
https://www.freedesktop.org/wiki/Software/fprint/libfprint/Supported_devices/
Please try to use the nodejs nodes without node-red.

Hello Ephraim,
I have the same issue (or I'm simply not experienced enough to use your code).
My fingerprint reader is 08ff:5731 | AuthenTec AES3500, I installed node red, the fprint library and device as well as your nodes, but get the debug message:
17.8.2019, 10:35:10node: Enroll Message
msg.payload : Object
object
payload: object
state: 98
message: "device-open-fail"
May you help me please?
Thanks a lot in advance!
best regards

@ltw001: "Device open fail" is mostly a rights problem.
Have your tried the test scripts from nodejs node-fprint?
Please try it as normal user and if that fails as root. If root works, then your user (or the node-red user) doesn't has the right to use the fprint device.
In that case you might want to find out which usb device your fprint device is and find the Vendor and Product ids. Then I would recommend, you write a udev rule which assigns appropriate rights to the device on plugin in.

Thanks a lot for the reply! I'm new to linux. I can't find any node-fprint test scripts. Where do I get those?
The fingerprint reader also shows up in the node red nodes under "Autoselect first reader".
What does the udev rule look like?

The node-red fprint nodes depend on nodejs node-fprint node which is another git repository.
https://github.com/ephraim/node-fprint
There you will find test scripts to test node-fprint in the console ... without node-red. You can use these test scripts as user or as root to test the rights.
About Udev rules, you might want to use Google for this there are plenty examples available.


Add RESERVED_SELECT and ASTERISK tokens

These are needed to finish the final bit of functionality (distinguishing * in SELECT * from other uses of * operator) that Nearley parser currently lacks compared to our current parser.
It also eliminates the hack for detecting SELECT token using a regex.
Using the name ASTERISK as that's what SQL standard uses.

I merge this in to move forward with Nearley integration. Feel free to still review it and express your thoughts.


Fix debug console is cleared on style changed

Close #200369
It seems when viewPanel body visibility changed the height was changed from 0 to the previous render height.
The listView.ts#L1439 will probe dynamic height when executing this.tree?.rerender.
After the calculation it removeItemFromDOM but not insertItemInDOM them back which result in looks like was cleared.
The fix was to insert the previous dom back into its container.

@roblourens ping in case you miss that.


web part not loading

I´ve been creating pages with this web part for a couple of weeks. At the beginning it worked great but now it's not loading. In every page I'm using  it it's stuck on " Loading Promoted Links... "
Any Idea?

If I Edit the page, it loads. I've tried removing the web part from the page and adding it again. I publish the page and then when I refresh the page it get stuck again.
Thank you in advance

I'm unable to replicate this issue. In chrome, if you press F12 and reload the page, do you get any errors in the console log?
Thanks,
Tony


Provide a TOC for README.md file

At present, there is no table of contents for the README file.
TOC can provide easier navigation through the README file.

@sharmaaditya570191 I would like to work on this issue

@jamesjose03 @sharmaaditya570191 I would like to work on this, I haven't been assigned any issues,
pls assign me this issue

@Basilleaf24 Sorry, I am already working on this issue.

@jamesjose03 what exactly do you plan to add in the README. Please keep in mind that we should keep the instructions in the README short and clear so that people tend to read the file.

@sharmaaditya570191 To add a table of contents in the readme just like how standard README files are maintained. It provides an easier navigation through the README and people can understand what are the main topics that are included in the README file.
For example,

Thanks for your suggestion @jamesjose03 . Here we don't have a long README.md so their is no need for TOC. We may open this at a later stage. Closing it for now.


Improve error message when make_time_index is invalid

For normalize_entity function, the argument make_time_index is a string.
There are two cases where make_time_index might not be valid:

Specifying an existing column for make_time_index but not adding that column to additional_variables or copy_variables.
Setting make_time_index to a column that doesn't exist in the base frame.

See https://github.com/Featuretools/featuretools/pull/535#discussion_r282472988

The assertion check should be added in the normalize_entity function


Fix wrong merge workflow

Issue

N/A

Overview (Required)

Fix Github Actions workflow when merged
Click the README badge to show the workflow

Links

N/A

Screenshot

Before
After

👀


Implement the script as a CLI which can be easily downloaded from PIP distribution

Implemented the CLI as a pip distribution which can be downloaded from the PIP


Fix LossKLD

This was running into NaNs pretty instantly because KL Divergence expects non-zero probabilities.
This changes the score calculation to be exactly the same as it is in Keras (https://github.com/fchollet/keras/blob/master/keras/objectives.py#L51).
I'm not quite sure if the computeGradient method is correct, as is as well. But introducing this change at least results in not NaN scores.

Good fix. Will merge in after resolve aeron compilation error on master.


Use json schema datatype instead of string

Title says it all.
This affects existing parsers for WFS and GeoJSON.

See also https://github.com/terrestris/geostyler-wfs-parser/pull/27

https://github.com/terrestris/geostyler-geojson-parser/pull/33

thx for review @KaiVolland
I'll release a new version after merge.


gradle multimodule war webapp src directory missing in ear.xml fixed

Can you add an image of what the generated xml file looks like before/after this fix?

before changes

after changes


Update the local node impl to deal with different kinds of UpdateDatas

After completion of #167 the API now supports passing of related contracts data etc. but we are not currently supporting this at the node layer so we can track the requested updates or have different subscription modes for updates.
In practice only UpdateData::Delta is supported (as is equivalent to the previous API version).
After completing this issue we should be be able to handle different subscription modes and keep track/ask for the related contracts.

Blocked by #410

Done


pagmo2: 2.18.0 -> 2.19.0

https://github.com/esa/pagmo2/blob/master/doc/sphinx/changelog.rst#2190-2023-01-21
https://github.com/esa/pagmo2/compare/v2.18.0...v2.19.0
Fixes python3.pkgs.pygmo
ZHF: #230712
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 233128 run on x86_64-linux 1

5 packages built:

openturns
pagmo2
python310Packages.openturns
python310Packages.pygmo
python311Packages.openturns


Add support for System.register

As noted at es6-module-loader wiki:

System.register can be considered as a new module format...

How about extending the UMD pattern to also use System.register?
Something like:
if (System && typeof System.register === "function") {
    System.register(['b'], factory);
} else if (typeof define === 'function' && define.amd) {
    // AMD. Register as an anonymous module.
    define(['exports', 'b'], factory);
} else if (typeof exports === 'object') {
    // CommonJS
    factory(exports, require('b'));
} else {
    // Browser globals
    factory((root.commonJsStrict = {}), root.b);
}

A similar discussion also takes place at mozilla/localForage#158.

For me, System.register is still speculative, and its format could change depending on how the loader API for the ES module loader shakes out. The use of System in general is trying to mimic or guess at the ES API, and it is just not close to done. I also expect the loaders that do implement System.register would know how to load commonjs or amd modules.

Does anything support System.register?
$ node --version
v5.0.0

node --harmony_modules
> System.register()
ReferenceError: System is not defined
    at repl:1:1
    at REPLServer.defaultEval (repl.js:248:27)
    at bound (domain.js:280:14)
    at REPLServer.runBound [as eval] (domain.js:293:12)
    at REPLServer.<anonymous> (repl.js:412:12)
    at emitOne (events.js:82:20)
    at REPLServer.emit (events.js:169:7)
    at REPLServer.Interface._onLine (readline.js:210:10)
    at REPLServer.Interface._line (readline.js:549:8)
    at REPLServer.Interface._ttyWrite (readline.js:826:14)


Focus move up one line after press enter key

I have this bug, when press enter key once, then press it again, the cursor will first move down, then move up to the line before. and this is only affecting Chrome, anybody help?

@htmlboy comment works perfectly.
thanks @htmlboy

@htmlboy & @kurtfunai thanks so much! This works great.

@nathanhamilton I actually ended up having issues with the fix mentioned in @htmlboy's comments. After adding it to our app, newlines were not being correctly added via the wyshtml project.
I actually ended up migrating to a new/active fork of this project: https://github.com/Voog/wysihtml
It is pretty similar, but has some nice improvements (no longer uses iFrames, resizes text area by default, and does not have this bug)
Best of luck!

@kurtfunai Thank you so much for letting me know you had issues. I will check out that project!


KV - widget properties not available during custom property creation

Kivy: ce9206c + stable

Description
Basically this SO question looks like a bug in our code, most likely in the kv parser. I think it's not the init ↔ post-init issue and here's why: notice the on_custom_size event, which prints __dict__, size and custom_size. Now if I set a property with a default value, then make an event that prints the property, the source of the property and change the property later, I expect the event to print the correct values - which it does and tells something more about the canvas presence (I think).
Let's draw a Rectangle using the value of the custom property.
Code and Logs
KV only
from kivy.app import runTouchApp
from kivy.lang import Builder

runTouchApp(Builder.load_string('''
<Test@BoxLayout>:
    custom_size: [0, 0]
    on_custom_size: print((vars(self), self.size, self.custom_size))
    # print __dict__, 800, 600 (= Window size); 1600, 1200
    custom_size: [s*2 for s in self.size]
    canvas:
        Color:
            rgba: (1, 0, 0, 1)
        Rectangle:
            # 100x100 default, uncommented = [x for x in None]
            # size: self.custom_size

Test:
'''))

Python only
from kivy.app import runTouchApp
from kivy.uix.boxlayout import BoxLayout
from kivy.properties import ListProperty
from kivy.graphics import Color, Rectangle

class Test(BoxLayout):
    custom_size = ListProperty([0, 0])

    def on_custom_size(self, *_):
        print((vars(self), self.size, self.custom_size))

    def __init__(self, **kwargs):
        super(Test, self).__init__(**kwargs)
        # print __dict__, 100, 100(= Widget default); 200, 200
        self.custom_size = [s*2 for s in self.size]
        with self.canvas:
            Color(rgb=(1, 0, 0))
            Rectangle(size=self.custom_size)

runTouchApp(Test())

As you can see there are two different behaviors, I think it's like that because in one of the snippets the canvas was already constructed, which obviously means size available with the default value, etc etc (the Python one), but I'm not sure because size doesn't seem to be available in __dict__ of the object (why? where is the first place the size/pos/... are created?).
On the other hand, kv code behaves like some kind of snake catching its own tail i.e. canvas isn't built, there's no size, yet the properties "work" or at least look like they work in the "functional" manner (kv executed line-by-line like PHP or C), but they are executed after the canvas is created unless they are used in the canvas and if they actually are used, then the Python code is executed inplace/directly(???) with that call, thus leading to issues with None.
Or am I missing something?

I suspect this is another illustration of the same or similar problem
from kivy.lang import Builder
from kivy.factory import Factory

Builder.load_string('''
<Dummy@Widget>:
    ninja: 100
''')

# Uncomment and it will work because property exists
#x = Factory.Dummy()
x = Factory.Dummy(ninja=0)

 Traceback (most recent call last):
   File "prop3.py", line 11, in <module>
     x = Factory.Dummy(ninja=0)
   File "c:\python36\lib\site-packages\kivy\uix\widget.py", line 337, in __init__
     super(Widget, self).__init__(**kwargs)
   File "kivy\_event.pyx", line 254, in kivy._event.EventDispatcher.__init__ (kivy\_event.c:5332)
 TypeError: object.__init__() takes no parameters

Possible kvlang solution:
<Test@BoxLayout>:
    custom_size: [0, 0]
<Test>:
    custom_size: [s*0.5 for s in self.size]

from kivy.app import runTouchApp
from kivy.lang import Builder

runTouchApp(Builder.load_string('''
<Test@BoxLayout>:
    custom_size: [s*.5 for s in self.size]
<Test>
    canvas:
        Color:
            rgba: (1, 0, 0, 1)
        Rectangle:
            size: self.custom_size
Test:
'''))

As speculated this works, my understanding is that the property is created during the evaluation of the <Test@BoxLayout> rule and exists in the class by the time the canvas rule is evaluated
from kivy.app import runTouchApp
from kivy.lang import Builder
from kivy.factory import Factory

class Dummy(Factory.BoxLayout):
    custom_size = Factory.ListProperty([0, 0])

runTouchApp(Builder.load_string('''
<Dummy>:
    custom_size: [s*.5 for s in self.size]
    canvas:
        Color:
            rgba: (1, 0, 0, 1)
        Rectangle:
            size: self.custom_size
Dummy:
'''))

#x = Factory.Dummy()
x = Factory.Dummy(ninja=0)

Nope, this is a completely different problem and that's about a missing Kivy Property that pops the ninja from kwargs before passing it further down to the object instance initialization itself. See the part about __init__.
I've already met this behavior and then I just switched to the Python classes instead as I don't think a dynamic class allows you to manipulate its __init__, or better said, it's not defined anywhere else (correct me if I'm wrong), therefore it just waits for the first instance because together with that the class property (ninja in this case) is created and otherwise it's just a plain Widget or even object class. Or maybe it's just in some dictionary somewhere, waiting. @matham or @tito will know more about this, I think.

<Test@BoxLayout>:
    custom_size: [s*.5 for s in self.size]
<Test>
    canvas:

About this piece, well this part just appends to the previous rule, therefore the property is there, but nothing was done with the canvas instructions from the user's side. At the second rule the property is properly created after the canvas is ready(in your case the default canvas instructions). In other words, see this:
<Test@BoxLayout>:
    custom_size: [s*.5 for s in self.size]
    # justa copypasta
    canvas:
        Color:
            rgba: (1, 0, 0, 1)
        Rectangle:
            size: self.custom_size  # crash boom
<Test>
    canvas:
        Color:
            rgba: (1, 0, 0, 1)
        Rectangle:
            size: self.custom_size
Test:

For more details see this answer although I think I've already explained it in the first post. My point is that there's a big inconsistency between the Python and Kv part which will introduce more troubles later if we tell users (and we already did) to use KV for designing the widgets.
A solution to this should preferably be evaluating every property in the whole rule (e.g. collect all rule lines first, filter by category - properties, canvas, etc and eval properties first, canvas later) where the line-by-line behavior is preserved. For example:
from kivy.app import runTouchApp
from kivy.lang import Builder

runTouchApp(Builder.load_string('''
# probe the rule
<Test@BoxLayout>:
    # collect to queue
    custom_size: [0, 0]

    # collect to the same queue as properties and on evaluation of the event
    # check if the property exists. If no, raise an error. If yes, don't care,
    # it can break at runtime (user's fault)
    on_custom_size: print((vars(self), self.size, self.custom_size))

    # collect to the queue; on evaluation the property already exists, so the
    # value would be just overwritten like in Python, so the event would be
    # triggered
    custom_size: [s*2 for s in self.size]

    # ignore until all properties and events are resolved
    canvas:
        Color:
            rgba: (1, 0, 0, 1)
        Rectangle:
            # ---> after evaluating properties first, canvas later this
            # ---> should work correctly as the value would be available
            # 100x100 default, uncommented = [x for x in None]
            # size: self.custom_size

    # collect to the queue
    random_property: 'blob'

    # end of rule, properties are evaluated here, canvas instructions'
    # evaluation should begin right after them

Test:
'''))

And that's probably even expected behavior and something just broke along those lines. 😢

The kv compiler is supposed to make these things more sane.


[FEATURE] Re-implement support for Roslyn-based mods

Feature Information
Feature description
Prior to transitioning to BepInEx, we had a feature where mods could be written in uncompiled .cs files and run using the .NET Compiler Platform SDK (Roslyn). We should try looking into the possibility of implementing this again, there have been a couple of questions about this in the Discord server and I think it will be useful for fast iteration of some smaller mods.

Added in #226


unable to use non-standard ports

Activation URLS in email messages are built using:
{ protocol }}://{{ site.domain }}{% url userena_activate user.username activation_key %}

But site.domain is only a domain name, not a domain name plus port number. This means that any ports other than 80 and 443 are not supported.
Thanks.
-Tom

This is something that will only confuse people when I add it in. I would override the template if you have a port that is neither 80 or 443.

Then I would need two templates. One for development, the other for production. How about we move the call to send the email outside of form.save()? That way we'll have access to the request object and can use build_absolute_url somehow. We'll just add one more template variable, and people will be none the wiser.


Add webcam qr code scanning on Faucet UI

During the session @chevdor did today on wallet setup for non technical people, it would have been nice to be able to fund mobile wallet accounts by scanning your account qrcode with the camera.

A good implementation of this is in the subwallet web app under "attach an account". It is very easy to add an account from nova wallet or similar mobile apps.
https://web.subwallet.app/
https://web.subwallet.app/accounts/attach-read-only


Get answers from ICLR chairs

We need to know the answers to the following questions from the ICLR 2020 chairs

[x] Did they use a completely static website? If so, did they just use GitHub pages?
We ran a server ourselves for auth, although we just hosted images etc on github pages. Probably we could have put them anywhere
[x] If you used a server to host the ICLR website, which server did you use?
I think it was NGinx. It just had auth and static pages.
[x] How did they integrate login/validation into GitHub Pages?
We didn't. Guessing you can't do that, but it would have been nice.
[x] Did they have any issues with a lot of traffic slowing down the website on busy days or times?
No, it was actually very stable. I think modern web servers are really good at static things. Our chat server and sponsor on the other hand both went down. We had to up the size of the server.
[x] Do you mind sharing the specs of the server you used? Was it an AWS instance?
No it was just the https://neurips.cc/ server.

@raosudha89 can you please add Sasha's answers from the email here so we have them documented a single place?

@raosudha89 can you please add Sasha's answers from the email here so we have them documented a single place?

I updated the comment with his answers

Based on his answers, I think we can just get a basic DO droplet for $5/mo, set up nginx on it and then just deploy the static website there. However, I want to hear what specs the NIPS server had before suggesting a final solution.

The server they ended up piggybacking on was a pretty beefy NeurIPS server with dozes of cores and 128G of RAM. We have asked if more moderate specs (e.g., Digital Ocean droplets with 4CPUs and 16G of RAM) would suffice for serving static content via nginx. Waiting for a reply.


expand shortcode not applying formatting inside expand div

Since Hugo 0.55.0 I have noticed that when using the expand shortcode, any formatting applied within the expand is not displayed correctly. For example, if you use ``` to format code, or notices to bring important information to the user's attention, this is not displayed correctly, and Markdown is simply displayed instead.
So for example, a simple expand like this will work fine:
{{< expand "Expand me" >}}
I'm hidden until expanded.
{{< /expand >}}

But an expand with additional formatting inside it will break:
{{< expand "Expand me" >}}
I'm hidden until expanded.
$ hello world

Bullet points like this:

will
not
display
correctly

{{< /expand >}}

REALLY strangely (particularly because of issue #316), a notice within an expand displays just fine, even on 0.55.0 and newer, e.g.
{{< expand "Expand me" >}}
{{% notice info %}}
This will work just fine, even though it won't display correctly outside the expand
{{% /notice %}}
{{< /expand >}}
{{% notice info %}}
See?
{{% /notice %}}

It seems I had an old version of the theme embedded in my Hugo site, so it hadn't taken the necessary updates. All working well now after updating the theme.


NIFI-2536 Update User Guide Template section

Updating the User Guide text on Templates to reflect changes in the 1.0 UI.

Templates uploaded from the Operate Palette
No upload from the Templates dialog
Permissions related to Process Group context

Reviewing...

Looks good @jvwing. This has been merged into master. Thanks!


Add command output comparisons

Tidy README
is cli output "tmux -V" like tmux

Codecov Report
Patch coverage is 12.50% of modified lines.

Files Changed
Coverage

cli.go
0.00%

parser/parser.go
54.54%

compare/compare.go
100.00%

:loudspeaker: Thoughts on this report? Let us know!.


Update a2q-apm-ruby base image

Description
Need to update base Docker image used for a2q-apm-ruby (Agent2Query) end-to-end test service.
Acceptance Criteria
Rescan is done and comes up clean.
Design Consideration/Limitations
N/A
Dependencies
N/A
Additional context
Same issue identified for all language agents. Should be able to coordinate next steps needed.
Original ref - NR-269099

Closing. Team originally setting up the framework will update this image.


An small intellisense Issue in Case of ConfigMethod(Action<T1,T2>) with overload ConfigMethod(Action)

Issue Description
When there is an overload for a method likeConfigMethod(Action<T1,T2>)which accept one arguments as ConfigMethod(Action<T2>), intellisense show methods of T2 in T1 in addition to T1 methods and properties. Fortunately it show an error just after selecting the wrong method but it is not very easy to find its own properties and methods.
Steps to Reproduce
Simply create a Host using Host.CreateDefaultBuilder(args).ConfigureAppConfiguration((ctx,configBuilder)=>{}) and try to use ctx methods and properties

This is happens in all methods of HostBuilder here and you can check it. I do not test it in normal program.cs file with main method and I only test it in High level statement procedure programming of .Net template for program.cs (without main or program class directly!)
Expected Behavior
Only show methods and properties of T1 here.
Actual Behavior
Shows methods and properties of both T1 and T2 for T1 in intellisense
Logs
OmniSharp log
Post the output from Output-->OmniSharp log here
C# log
Post the output from Output-->C# here
Environment information
VSCode version: 1.67.0
C# Extension: 1.24.4
Mono Information
        OmniSharp using built-in mono
Dotnet Information
.NET SDK (reflecting any global.json):
 Version:   6.0.202
 Commit:    f8a55617d2
Runtime Environment:
OS Name:     ubuntu
OS Version:  20.04
OS Platform: Linux
RID:         ubuntu.20.04-x64
Base Path:   /usr/share/dotnet/sdk/6.0.202/
Host (useful for support):
Version: 6.0.4
Commit:  be98e88c76
.NET SDKs installed:
6.0.202 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.4 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.4 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

csharp
ms-dotnettools
1.24.4

csharpextensions
kreativ-software
1.7.0

I close this issue since it does not seem very serious.


Need Row Value in filterFunction. (As of Now only Cell value)

How to get entire row value inside a filterFunction (Similar to valuePrepareFunction(cell,row)).
             valuePrepareFunction : (cell,row) => {
                return this.timeDifference.transform(row.reserveTime, row.releaseAt);
            },
            filterFunction : (cell, search, **row**) => {
                let temp = new Date(cell).toDateString() + ' - ' + new Date(cell).toLocaleTimeString();
                if (String(this.timeDifference.transform(**row.reserveTime**, **row.releaseAt**)).toLowerCase().includes(search.toLowerCase()) || search === '') {
                    return true;
                  } else {
                    return false;
                  }
            }

Here i am finding the difference of two date using valuePrepare function and displaying them as duration. On filter i need to filter based on the same value.To calculate i need entire row data instead of cell value.

I would upvote this feature!  I also think the proposed method signature is perfect.

I have added this feature and updated the documentation on a fork of this project.  I just submitted a pull request #971 and hopefully @nnixaa will release a new npm update that includes it.


Add ProtonVPN 1.15.0

Microsoft Reviewers: Open in CodeFlow

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: kutoswiss sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@kutoswiss I got Installer failed with exit code:<PHONE_NUMBER>. Did you install this on your local machine with winget install -m 1.15.0.yaml? Does this require elevated terminal?

@denelon I installed it on my machine using winget install -m 1.15.0.yaml and works well without any elevated privileges.
However I can reproduce the issue when I try to install it with an elevated terminal as you probably did. Do we need to satisfy this condition ? I also go an error window with the message "Invalid command line".

@denelon I found the issue. I added wrong silent switches to the yaml file. Should be fine now.


fix issues

Description:
fix filterMetadatas
fix DNSResolveDB

Testing done:
Done

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[ ]

Upgrade
[ ]

Other
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Is this a breaking change? no

Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)? no

Codecov Report
Attention: Patch coverage is 0% with 18 lines in your changes are missing coverage. Please review.

Project coverage is 14.47%. Comparing base (cf56380) to head (b9bca01).
Report is 89 commits behind head on release/v1.3.

Files
Patch %
Lines

pkg/sidecar/providers/pipy/repo/jobs.go
0.00%
6 Missing :warning:

pkg/connector/provider/eureka.go
0.00%
4 Missing :warning:

pkg/connector/provider/nacos.go
0.00%
4 Missing :warning:

pkg/sidecar/providers/pipy/repo/policy.go
0.00%
4 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                Coverage Diff                @@
##           release/v1.3     #280       +/-   ##
=================================================
- Coverage         46.81%   14.47%   -32.34%
=================================================
  Files               199      760      +561
  Lines             15239    51032    +35793
=================================================
+ Hits               7134     7388      +254
- Misses             8059    43475    +35416
- Partials             46      169      +123

Flag
Coverage Δ

unittests
14.47% <0.00%> (-32.34%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Result of Object.create(null) may be passed to template literal

TypeScript Version:  3.5.1
Search Terms: template string, template literal, Object.create(null)
Code
`${Object.create(null)}`

Expected behavior: TypeError, as the object passed to the template string has no toString method in the prototype chain (as it has no prototype chain at all).
Actual behavior: Everything goes well in the compiler, but JavaScript reports runtime error (ex. TypeError: Cannot convert object to primitive value in Chrome).
Playground Link: https://www.typescriptlang.org/play/index.html#code/AYEg3g8gRgVgpgYwC4DoECc4EMlwBQB2ArgDYkCUAvsEA
Related Issues:
https://github.com/microsoft/TypeScript/issues/30239
https://github.com/microsoft/TypeScript/issues/1108

It should be possible, however, to pass that weird object-no-object thingy to tagged template literal, as tag function may be able to deal with that.
interface OptionalToString {
    toString?: () => string
}

function tag(_: TemplateStringsArray, value: OptionalToString) {
  if (typeof value.toString !== 'function') {
    return Object.prototype.toString.call(value);
  }

  return value.toString();
}

tag`${Object.create(null)}`;

See this in playground

Object.create(null) has bitten me in the past. I hate it. I don't like it when developers and libraries use it.
It's because of them, I need to do stuff like Object.prototype.hasOwnProperty.call(obj, k)
Because obj.hasOwnProperty fails for Object.create(null)
You just have to use libraries that actually support it and remember to support it, yourself.
It's not a TS problem

Because obj.hasOwnProperty fails for Object.create(null)

Actually this is usually why you would use it: because you’re using an object as a dictionary and don’t want anything from Object.prototype interfering.  Admittedly it’s less useful now that we have Map but it did serve a useful purpose when it was introduced.
If you ever wondered why we have a bunch of a static methods on Object now, e.g., Object.keys, rather than them being direct instance methods—this is why.


 Please provide some details so that someone can contribute.

Thanks for the feedback. I'm currently using these issues to keep track of tasks for myself, but let me know if you (or anyone else) would be interested in contributing, and I can prioritize adding more documentation.