Have you considered testing static pipelines as well in the perf tests?

To give a concrete example, consider the code here. You could probably see some serious perf differences if you replicated the tests for the ones that support cold observables, using static pipelines instead of dynamically created ones as much as possible. Of course, you can see below you can't do it always, but for cold subscription-only observables, I think the relative speeds might be closer together. (Plus, it's this part that RxJS focuses on in performance, not the creation part.)
mostPipeline = most.from(a).filter(even).map(add1)
rxPipeline = rx.Observable.fromArray(a).filter(even).map(add1)
rx5Pipeline = rxjs.Observable.from(a).filter(even).map(add1)
xstreamPipeline = xs.fromArray(a).filter(even).map(add1).fold(sum, 0)
kefirPipeline = kefirFromArray(a).filter(even).map(add1).scan(sum, 0)
baconPipeline = bacon.fromArray(a).filter(even).map(add1)
highlandPipeline = highland(a).filter(even).map(add1)

suite
  .add('most', function(deferred) {
    runners.runMost(deferred, mostPipeline.reduce(sum, 0));
  }, options)
  .add('rx 4', function(deferred) {
    runners.runRx(deferred, rxPipeline.reduce(sum, 0));
  }, options)
  .add('rx 5', function(deferred) {
    runners.runRx5(deferred, rx5Pipeline.reduce(sum, 0));
  }, options)
  .add('xstream', function(deferred) {
    runners.runXstream(deferred, xstreamPipeline.last());
  }, options)
  .add('kefir', function(deferred) {
    runners.runKefir(deferred, kefirPipeline.last());
  }, options)
  .add('bacon', function(deferred) {
    runners.runBacon(deferred, baconPipeline.reduce(0, sum));
  }, options)
  .add('highland', function(deferred) {
    runners.runHighland(deferred, highlandPipeline.reduce(0, sum));
  }, options);

One other suggestion: RxJS 6 could be a good addition, too. They've made some serious API changes, and I think perf has been substantially changed, too.

Hi @isiahmeadows.  I had tried it at one point and from what I remember, the creation time was completely dominated by the run time.  That said, I'd certainly welcome a PR that adds these kinds of tests, as well as one that adds rx 6.  It's good to see the progress the rx team has made since v4.

Closing because of inactivity.  Please feel free to reopen with an update.


Test erroring after tapping on an element

What happened?
Hi, I have been trying out Detox and my test is failing every time I try to tap on an element. It manages to tap on the desired button as I can see the bottom-sheet appearing on the Simulator but the test then fail to continue.
I tried adding a console.log after the tap() and it's not returned so there seems to be something wrong with this tapping action
Any idea why this could be occurring?
 FAIL  e2e/starter.test.js (24.981 s)
  Home screen
    ✕ "Sign in" button should be visible (18922 ms)

  ● Home screen › "Sign in" button should be visible

    The pending request #3 ("invoke") has been rejected due to the following error:

    The app has crashed, see the details below:

    Exception was thrown:
    NSInvalidArgumentException
    -[NSNull __detox_sync_untrackAnimation]: unrecognized selector sent to instance 0x1069b4590
    (
    	0   CoreFoundation                      0x00000001067257e0 __exceptionPreprocess + 160
    	1   libobjc.A.dylib                     0x0000000105e15144 objc_exception_throw + 56
    	2   CoreFoundation                      0x000000010673449c +[NSObject(NSObject) instanceMethodSignatureForSelector:] + 0
    	3   CoreFoundation                      0x00000001067296ec ___forwarding___ + 1308
    	4   CoreFoundation                      0x000000010672bb6c _CF_forwarding_prep_0 + 92
    	5   DetoxSync                           0x000000013f29ded0 -[_DTXCAAnimationDelegateHelper __detox_sync_animationDidStop:finished:] + 76
    	6   UIKitCore                           0x000000012145246c __63-[UIViewPropertyAnimator finalizeStoppedAnimationWithPosition:]_block_invoke_4 + 276
    	7   UIKitCore                           0x00000001214522b8 -[UIViewPropertyAnimator finalizeStoppedAnimationWithPosition:] + 644
    	8   UIKitCore                           0x000000012144e3a8 -[UIViewPropertyAnimator _runCompletions:finished:] + 28
    	9   CaregiverConnect                    0x000000010067ea58 ExpoBlur.BlurEffectView.__deallocating_deinit + 148
    	10  CaregiverConnect                    0x000000010067eaac @objc ExpoBlur.BlurEffectView.__deallocating_deinit + 28
    	11  libsystem_blocks.dylib              0x000000010d94ef60 bool HelperBase<GenericInline>::disposeCapture<(HelperBase<GenericInline>::BlockCaptureKind)3>(unsigned int, unsigned char*) + 64
    	12  libsystem_blocks.dylib              0x000000010d94d8e4 HelperBase<GenericInline>::destroyBlock(Block_layout*, bool, unsigned char*) + 168
    	13  libsystem_blocks.dylib              0x000000010d94d0ac _call_dispose_helpers_excp + 68
    	14  libsystem_blocks.dylib              0x000000010d94dfb8 _Block_release + 280
    	15  libsystem_blocks.dylib              0x000000010d94f05c bool HelperBase<GenericInline>::disposeCapture<(HelperBase<GenericInline>::BlockCaptureKind)4>(unsigned int, unsigned char*) + 64
    	16  libsystem_blocks.dylib              0x000000010d94d8f8 HelperBase<GenericInline>::destroyBlock(Block_layout*, bool, unsigned char*) + 188
    	17  libsystem_blocks.dylib              0x000000010d94d0ac _call_dispose_helpers_excp + 68
    	18  libsystem_blocks.dylib              0x000000010d94dfb8 _Block_release + 280
    	19  CoreFoundation                      0x00000001066166e0 __RELEASE_OBJECTS_IN_THE_ARRAY__ + 108
    	20  CoreFoundation                      0x0000000106616620 -[__NSArrayM dealloc] + 264
    	21  UIKitCore                           0x000000012144e1c8 -[UIViewPropertyAnimator _clearAnimationState] + 260
    	22  UIKitCore                           0x000000012144d59c __61-[UIViewPropertyAnimator _setupAssociatedViewAnimationState:]_block_invoke + 120
    	23  UIKitCore                           0x00000001222bd91c __UIVIEW_IS_EXECUTING_ANIMATION_COMPLETION_BLOCK__ + 28
    	24  UIKitCore                           0x00000001222bdb80 -[UIViewAnimationBlockDelegate _didEndBlockAnimation:finished:context:] + 604
    	25  UIKitCore                           0x00000001222991e8 -[UIViewAnimationState sendDelegateAnimationDidStop:finished:] + 212
    	26  UIKitCore                           0x0000000122299624 -[UIViewAnimationState animationDidStop:finished:] + 192
    	27  UIKit                               0x00000001455f4b80 -[UIViewAnimationStateAccessibility animationDidStop:finished:] + 168
    	28  DetoxSync                           0x000000013f29dec8 -[_DTXCAAnimationDelegateHelper __detox_sync_animationDidStop:finished:] + 68
    	29  QuartzCore                          0x000000010eb243a4 CA::Layer::run_animation_callbacks(void*) + 228
    	30  libdispatch.dylib                   0x000000010e2e7768 _dispatch_client_callout + 16
    	31  libdispatch.dylib                   0x000000010e2f7018 _dispatch_main_queue_drain + 1220
    	32  libdispatch.dylib                   0x000000010e2f6b44 _dispatch_main_queue_callback_4CF + 40
    	33  CoreFoundation                      0x0000000106689cf4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
    	34  CoreFoundation                      0x00000001066843b0 __CFRunLoopRun + 1956
    	35  CoreFoundation                      0x00000001066837f4 CFRunLoopRunSpecific + 584
    	36  GraphicsServices                    0x000000010fa23c98 GSEventRunModal + 160
    	37  UIKitCore                           0x0000000121e2ed1c -[UIApplication _run] + 868
    	38  DetoxSync                           0x000000013f29f4d0 __detox_sync_UIApplication_run + 376
    	39  UIKitCore                           0x0000000121e32d14 UIApplicationMain + 124
    	40  CaregiverConnect                    0x000000010051d61c main + 96
    	41  dyld                                0x0000000105499fa0 start_sim + 20
    	42  ???                                 0x0000000105585e50 0x0 +<PHONE_NUMBER>
    	43  ???                                 0xc31a800000000000 0x0 + -4388054149430771712
    )

      19 |     await expect(element(by.id('LoginButton'))).toBeVisible;
      20 |     console.log('tap the button');
    > 21 |     await element(by.id('LoginButton')).tap();
         |                                         ^
      22 |     console.log('bla bla');
      23 |     await waitFor(element(by.text('agree')))
      24 |       .toBeVisible()

      at Object.tap (e2e/starter.test.js:21:41)
      at asyncGeneratorStep (../../node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
      at _next (../../node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)

21:40:38.051 detox[56997] E Command failed with exit code = 1:
jest --config e2e/jest.config.js e2e
error Command failed with exit code 1.

What was the expected behaviour?
No response
Was it tested on latest Detox?

[ ] I have tested this issue on the latest Detox release and it still reproduces.

Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: 20.6.0
React Native version: 0.71.4
Has Fabric (React Native's new rendering system) enabled: no
Node version: 16.4
Test-runner (select one): jest
Detox logs
Detox logs
paste logs here!

Device logs
Device logs
paste logs here!

More data, please!
No response

Hey @guillaumemeunier, thanks for the report. Can I get more context and information that may help me investigate this issue?
Does this button have any unique properties? Does it trigger any animations?
It will be very useful if you'll provide me a minimal reproduction for this issue - the minimal code and dependencies required for this component that fails on tap.

Is the Reanimated library being utilized here?

I recommend on using https://github.com/wix-incubator/detoxtemplate for creating a minimal reproduction on a real RN project, this would be ideal for the investigation.

I am seeing this same error also. Would be great to get this fixed asap as this is a breaking change that is making me considering switching to Appium.
For me I am clicking a button that is a actually a textfield. Perhaps thats why its causing the error?

I am seeing this same error also. Would be great to get this fixed asap as this is a breaking change that is making me considering switching to Appium.
For me I am clicking a button that is a actually a textfield. Perhaps thats why its causing the error?

What issue are you having? Please share the error you're getting (better in a separated GH issue)
There's a lot of reasons for that, without more information it will be very hard to assist you

Hi @asafkorem,
Sorry. Yes I'm getting the exact same error that is shown in the original message.

@jennis-jaceparara I see.
As written before, since this error is coming from integration with 3rd party/parties it will be impossible to investigate this without a clean reproduction. If you can create a minimal project with reproduction for this error I can try to investigate this error.


Add logging of stdout to dbt graph run_command.

Description
Currently run_command functions put only stderr or stdout into logger. Which is misleading, because there are also important information in stdout even if something exists in stderr.
Related Issue(s)
closes #1356
Breaking Change?
NO
Checklist

[ ] I have made corresponding changes to the documentation (if required)
[x] I have added tests that prove my fix is effective or that my feature works

I wonder a little if it would be better to not split out the stderr and stdout in the first place, since it could be confusing. Still a substantial improvement.

Hi @KarolGongola, thank you very much for improving the logs
I'm happy with the improvement. Could you please fix the tests so they pass? It will also help us avoid any regressions in your log improvement.
Apparently, the following tests broke due to this change:
FAILED tests/dbt/test_graph.py::test_load_via_dbt_ls_with_non_zero_returncode - AssertionError: Regex pattern did not match.
 Regex: "Unable to run \\['.+dbt', 'deps', .*\\] due to the error:\\nSome stderr message"
 Input: "Unable to run ['/home/runner/.local/share/hatch/env/virtual/astronomer-cosmos/Za_bFbg4/tests.py3.11-2.9/bin/dbt', 'deps', '--project-dir', '/tmp/tmpivws28dg', '--profiles-dir', '/tmp/cosmos/profile/d426ea9bd2fe96408d8d2c4f150ab19011d7d7314fc17f613b902308e66fb2e7', '--profile', 'default', '--target', 'default'] due to the error:\nstderr: Some stderr message\nstdout: "
FAILED tests/dbt/test_graph.py::test_load_via_dbt_ls_with_runtime_error_in_stdout - AssertionError: Regex pattern did not match.
 Regex: "Unable to run \\['.+dbt', 'deps', .*\\] due to the error:\\nSome Runtime Error"
 Input: "Unable to run ['/home/runner/.local/share/hatch/env/virtual/astronomer-cosmos/Za_bFbg4/tests.py3.11-2.9/bin/dbt', 'deps', '--project-dir', '/tmp/tmp_jnwrslr', '--profiles-dir', '/tmp/cosmos/profile/d426ea9bd2fe96408d8d2c4f150ab19011d7d7314fc17f613b902308e66fb2e7', '--profile', 'default', '--target', 'default'] due to the error:\nstderr: \nstdout: Some Runtime Error"
= 2 failed, 66 passed, 5 skipped, 667 deselected, 2 warnings in 342.06s (0:05:42) =

sure, sorry for inconvenience,

I wonder a little if it would be better to not split out the stderr and stdout in the first place, since it could be confusing. Still a substantial improvement.

I think that just concatenating them without any info could be even more misleading because they wont be in chronological order.

@tatiana Is it fine now?

I meant keep them in chronological order by using the stderr=STDOUT param. https://docs.python.org/3/library/subprocess.html#subprocess.STDOUT

I meant keep them in chronological order by using the stderr=STDOUT param. https://docs.python.org/3/library/subprocess.html#subprocess.STDOUT

Ah, I see. It seems like good idea. Let me check how much changes it requires in the code.

It is much better. Thanks @fjmacagno

@tatiana Is this fine for you now? Or do you prefer concatenation without "stdout" and "stderr" keywords?


Added green tally color supported by FR7

I have added a color dropdown to the Tally On/Off action with options 'red' (default) and 'green'.
Having the green color added, we can now also send a green tally to our FR7's, when they are in preview for example.
Not sure what other Sony camera's support green Tally as well. Might be a FR7 only option...

Tested and verified to be working on a Sony FR7 running the 2.00 firmware.

@PerRoine could you verify and merge this into master? Let me know if you need any help.

Thanks for your contribution.


Quoted arguments including spaces parsed incorrectly on Windows (Nutika 2.4/2.4.1)

Nuitka Version:
2.4.1
Commercial: None
Python: 3.11.9 (tags/v3.11.9:de54cf5, Apr  2 2024, 10:12:12) [MSC v.1938 64 bit (AMD64)]
Flavor: CPython Official
Executable: C:\Users\campb\Documents\Code\Python\WiiPy\.venv\Scripts\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 11
Version C compiler: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\bin\Hostx64\x64\cl.exe (cl 14.3).

Installed normally from PyPI.
Description:
On Windows, when you pass arguments in quotes that include spaces, the spaces don't get included as part of the quoted string and the argument gets separated. Seems to be present in both 2.4 and 2.4.1. Also tested on Nuitka 2.4.1 on Linux, and this issue does not occur there. Reverting to Nuitka 2.3.11 on Windows shows that this was working before the 2.4 release.
Command: program.exe arg1 "arg 2"
Value of sys.argv:
Nuitka 2.3.11: ['\path\to\program.exe', 'arg1', 'arg 2']
Nuitka 2.4/2.4.1: ['\path\to\program.exe', 'arg1', 'arg', '2']

Thanks for the report, this is actually way more difficult than it should be, seems while Windows can partition arguments with APIs, it cannot re-assemble it easily, but I found code that I can emulate and handles escapes of "" and quotes correctly too.

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
Feedback on whether this is working is very welcome. Please do not share plans to do it; only confirm or deny that it is working.

This will be in the hotfix 2.4.2 shortly too.

Part of the 2.4.2 hotfix release I just made.

Seems to be working as expected in the hotfix!


Frame take whole stack of items but only return one

If you holde a whole stack, all of it is placed in the frame, but only one item is returned.
As a result all but one item is destroyed.

I am sad for this but as you can see in the repo, there is no event listener for itemframe item placing event. Probably it's causing because of a plugin in your server


feature: math and latex

Math and basic latex pads.

Work started here: https://github.com/ipfs-shipyard/peerpad/pull/93

@nicola now it should be ready to go. Remember to update local dependencies, since peerpad-core upgraded to version 0.6.2. for math support.


images deploy / private buckets

Issue #, if available:
Description of changes:

removed instructions for deploying from the public buckets
changed the way we deploy images (now uses a cloudfront distribution serving the image.tar.gz archive)
upgrade to python 3.12

Description of testing performed to validate your changes (required if pull request includes CloudFormation or source code changes):

stage.sh + deploy on my account (in eu-west-1 and in us-east-1)
basic testing of the demo itself

Known issues:

the internal pipeline is not fixed to accomodate for the buckets being private now
pandas is updated to 2.x, in some python versions this can cause a long build process (tested on 3.12.2 with no issues)
This a temporary hotfix to get the developper instructions (stage.sh) working
https://code.retaildemostore.retail.aws.dev/images.tar.gz is hardcoded for now

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Do we still need a script that updates the private bucket behind the CloudFront distribution? Minimally, this script would update and copy the images zip and copy the generated CSVs.

Do we still need a script that updates the private bucket behind the CloudFront distribution? Minimally, this script would update and copy the images zip and copy the generated CSVs.

I propose to keep the existing buildspec.yml and stage to the private bucket behind the code.retaildemostore.retail.aws.dev cloudfront distribution. So we have all the code available on this cloudfront distribution, lambda function, csv, etc.
Images are static and only updated if we modify them (not included in the github repo)


x/tools/cmd/digraph: allpaths non-deterministically misses cycles

$ cat x
A B
A C
A D
C E
D B
D F
E B
E F
F E
$ for i in $(seq 20); do echo $(digraph allpaths A B < x); done
A B C D E
A B C D E
A B C D E
A B C D E
A B C D E F
A B C D E F
A B C D E F
A B C D E F
A B C D E F
A B C D E
A B C D E
A B C D E F
A B C D E
A B C D E
A B C D E
A B C D E
A B C D E
A B C D E
A B C D E F
A B C D E
$

There is a path A -> C -> E -> F -> B (among others), so F should be included 100% of the time.

Fixed by https://go-review.googlesource.com/c/tools/+/184337, I think.
@jadekler


[bug] on_web_resource_request not working in dev mode

Describe the bug
In dev mode, i.e. when running npm run tauri dev the method on_web_resource_request of the WundowBuilder seems to be ignored.
Reproduction

Run sh <(curl https://create.tauri.app/sh) on linux.
Choose npm as the package manager and Vue-ts as the frontend framework.
Add the following setup hook to src-tauri/src/main.rs:

        .setup(|app| {
            use tauri::WindowBuilder;
            use tauri::WindowUrl;
            let _window = WindowBuilder::new(
                &app.handle(),
                String::from("some_label"),
                WindowUrl::App("index.html".into()),
            ).on_web_resource_request(move |request, response| {
              println!("Received request: {:?}", request);
            }).build();

            Ok(())
        })

Run npm run tauri dev and see that the print statement is not being triggered.
Build the app via npm run tauri build and see that the print statement is being triggered when running the AppImage.

Expected behavior
I expect .on_web_resource_request() to also work in dev mode.
Platform and versions
Environment
› OS: Ubuntu 22.04 X64
› Node.js: 16.11.1
› npm: 8.0.0
› pnpm: Not installed!
› yarn: 1.22.19
› rustup: 1.25.1
› rustc: 1.64.0
› cargo: 1.64.0
› Rust toolchain: stable-x86_64-unknown-linux-gnu
Packages
› @tauri-apps/cli [NPM]: 1.2.1
› @tauri-apps/api [NPM]: 1.2.0
› tauri [RUST]: 1.2.1,
› tauri-build [RUST]: 1.2.1,
› tao [RUST]: 0.15.6,
› wry [RUST]: 0.22.5,
App
› build-type: bundle
› CSP: unset
› distDir: ../dist
› devPath: http://localhost:1420/
› framework: Vue.js
App directory structure
├─ dist
├─ node_modules
├─ src-tauri
├─ src
├─ .vscode
└─ public
Stack trace
No response
Additional context
No response

This is expected and documented:

Thank you for your report.

Oh that's a big pitty. It was working before I updated to tauri 1.2.0 so I didn't really think about looking into the docs. I guess something changed under the hood when running npm run tauri dev.

The only change to tauri dev was that it now serves the frontend files, if your devPath is a file path and not a url, via an internal dev server to enable hot reloading.

No, i think it's hard coded. idk if that works but you could try setting tauri://localhost as the devPath.
If that doesn't work i'd suggest using tauri build --debug --b none, preferably in a script which can stops/start the app too (the script would need to take care of a potential beforeDevCommand too).
cargo run or cargo run --features custom-protocol  in your src-tauri dir should work too.
p.s. feel free to open a feature request asking for a built-in way to disable it.


[REQUEST] A setting to disable showing album artwork

First I would like to thank you for building this extension it is absolutely amazing! It's strange that Spotify doesn't have notification support built in and this is a perfect solution :-)
I am not sure if this is possible but if there could be a way to show the song name and album artwork when the popup notification is shown but not inside the notification center that would be great! The main issue is that it takes up too much space to show both in the notification center and I feel that it is a bit too cluttered.
Thanks!
Alex

@AlexAbraham1,
I just wanted to give you an update. Yesterday I signed and published binaries for versions 0.5.0 and 0.5.1, so if you didn't build the project yourself, feel free to download the latest version.
— @citruspi


Deletion of the kotlin files.

Is your feature request related to a problem? Please describe.
This is not a bug directly caused by walletconnectunity. The problem happens when trying to merge other plugins. The issue raises when you try to use the old unity version, kotlin files and Firebase SDK.
Working setup:
Unity 2021.3.17 - WalletConnectUnity(has CanOpenUrl.kt) - No Problem.
Unity 2021.3.17 - WalletConnectUnity(has CanOpenUrl.kt) - Firebase Unity SDK. No Jetifier.
Unity 2021.3.17 - WalletConnectUnity(has Linker.java) - Firebase Unity SDK. Use Jetifier.
Broken Setup:
Unity 2021.3.17 - WalletConnectUnity(has CanOpenUrl.kt) - Firebase Unity SDK. Use Jetifier.
Describe the solution you'd like
Delete CanOpenUrl.kt and turn it into Linker.java. This way, you are not going to need to include Kotlin Library. It will be more compatible. There are no additional changes required in the SDK.
Describe alternatives you've considered
I have tried to update
-Firebase version 11.3(down) - 11.4 current - 11.5(up) - 11.6(up) - 11.7(up)
-2022.3.19
-Disable Jetifier (cannot be done in the current project)
Additional context
After twenty hours of building files and trying different Unity, Firebase, and Gradle Versions, I have given up... Thanks to the Android platform, billions of dependencies make you hate Android...
Firebase Issue: https://github.com/firebase/firebase-unity-sdk/issues/847
The changing versions started to cause more problems (https://github.com/firebase/firebase-unity-sdk/issues/945), so I gave up and just fixed the reason that caused it in the first place. I would like to add error texts here, but Android got me so mad I want to be done 👹
Here is the solution that can save someone 20 Hours 🗿 (https://github.com/crawfordbowl/WalletConnectUnity/commit/2fa938fd9f191c0c42837eae65a0336b0884769a)

@crawfordbowl thanks!

Thanks @crawfordbowl, you saved me from stress, it took me 2 days for this issue.


Feature/meta params

Priority
I created a fork, but I think it is high priority because it is not complaint to the spec.
What Changed & Why
Create request was sending a meta parameter, and based on the spec, The request MUST include a single resource object as primary data.
I also added yarn, but I am new to the js community, so I am open to comments about that.
Testing
yarn test

I think this PR should NOT be implemented because although JSONAPI spec requires a single resource object as primary data, a document may have more top level members except from primary data such as meta.

Closing because this PR seems stale and not clear what the benefit is to losing the meta attribute.
@daniel-g You can reopen if you feel this still needs to be addressed.

I was using a ruby gem to consume a JSON API, one of its conditions to detect a create request was detecting a single resource. Since devour added a meta, it was rejecting the request. I guess the gemis the one that should change.


Improve the contentimporter by clearing the entitymanager regularly

We might want to consider doing this in each of the routines rather than forcing it as part of content import.
Using blackfire, this shows the installation going from 3:30s down to 1:48s!

The install command I'm using to profile is:
blackfire run ./concrete/bin/concrete5 c5:install --admin-password=password --db-database=concrete5 --db-server=localhost --db-username=root --timezone="america/los_angeles"

but you could just use time to test how long it takes:
time ./concrete/bin/concrete5 c5:install --admin-password=password --db-database=concrete5 --db-server=localhost --db-username=root --timezone="america/los_angeles"

Running on Ubuntu, PHP version 5.6.31-1
3 tests without changes from this commit
First test:
real	0m58.206s
user	0m22.636s
sys	0m14.096s
Second test:
real	1m1.371s
user	0m25.680s
sys	0m13.060s
Third test:
real	1m1.424s
user	0m25.768s
sys	0m13.620s
3 tests WITH changes from this commit
First test:
real	0m51.861s
user	0m14.080s
sys	0m15.136s
Second test:
real	0m48.194s
user	0m13.960s
sys	0m13.144s
Third test:
real	0m47.149s
user	0m13.560s
sys	0m12.964s
That means a fair 20% improvement (on PHP 5.6 though).  So now for PHP version 7.0.22-0
First test:
real	0m49.475s
user	0m17.284s
sys	0m10.496s
Second test:
real	0m48.151s
user	0m16.092s
sys	0m10.356s
Third test:
real	0m48.005s
user	0m16.440s
sys	0m10.716s
Now tests WITH changes from this commit
First test:
real	0m38.006s
user	0m8.376s
sys	0m10.212s
Second test:
real	0m40.453s
user	0m9.652s
sys	0m10.180s
Third test:
real	0m39.593s
user	0m8.752s
sys	0m10.368s
So on PHP 7.0, a 20% reduce in time too.
Did use the time command, not blackfire.

This breaks installation with sample content. I am reverting it. With this applied when  install via the command line I get the following error:
A new entity was found through the relationship 'Concrete\Core\Entity\Attribute\Set#category' that was not configured to cascade persist operations for entity: 1. To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or configure cascade persist  this association in the mapping for example @ManyToOne(..,cascade={"persist"}).


tBTC Media Kit page

sharing design and press assets for easy download and links.
related to Update tBTC VIS Doc and Media Assets #124

WIP:

@Shadowfiend i recommend implementing just this first row:

Figma

also, let's date the assets for whatever the publication date of the page is.

the following links are for the Media Kit section of tbtc website:
tbtc logo (SVG/PNG 1x—3x)
tbtc token icon (SVG/PNG 1x—3x)

let's remove EPS from the tbtc logo


[fvtt-11] Fix localization of document sub-types

Foundry 11 changed localization keys for document sub-types: https://github.com/foundryvtt/foundryvtt/issues/8568
e.g. ACTOR.TypeNpc -> TYPES.Actor.npc

This change can be addressed later, preferably after Zweihander compatibility with v10 is phased out (in order to not leave mess behind).


VSCode: keybindings.json

~/Library/Application\ Support/Code/User/keybindings.json

[
    {
        "key": "cmd+`",
        "command": "workbench.action.terminal.focus"
    }
]


[FEATURE REQUEST]

[ ] Custom colors

[ ] Custom background image for each break, or one for all

[ ] Custom times

[ ] Sound at the beginning, not at the end (or setting both?)

[ ] Background music or sound fx while the break lasts, for example some water flowing, beach waves, forest with animals sounds, rain, relaxing instrumental music.

[ ] Window Transparency

[ ] Custom Text/Messages

[ ] Insert at 1 image at the bottom, related to what the message says. If it says "Go, grab a glass of water" then image of a water bottle, a river or  waterfalls, or glass of water with ice. If it says "Go, grab a cup of coffee", the image can be coffee grains, coffee with heart, ora person drinking coffee.

[ ] Custom Pause times

[ ] Choose from an Analog clock animation or a  progress bar, and if progress bar, customizing the accent color.

[ ] "...nah, I'll just keep going" should be a material button, with customizable text, with a default of "Skip" or "Skip Break"

[ ] A "Pause" button at the side of the skip break button, clicking it will show the Pause times context menu.

[ ] Settings page needs improvement. Layout, and material animated toggle button instead of checkbox.

[ ] Why are the texts lower case!?

[ ] Any reason why the logo in the tray is monochrome by default?

[ ] Skip break with a keyboard shortcut

[ ] Language settings. The app's text can be modified in a JSON file.

I am developer, I can build my own app, but decided to try this one to support other developers' projects, but there are so many missing expected features.
Cheers

Hi and thanks for the ideas ;] A lot of things can be done via editing advanced settings file: https://github.com/hovancik/stretchly#advanced-settings. Basically every setting is in that file, thus can be changed there.
Custom colors - in settings file
Custom background image for each break, or one for all - I want the app to look very simple, thus I don't plan to have images for breaks
Custom times - what specifically do you mean? You can edit interval and how long the breaks are
Sound at the beginning, not at the end (or setting both?) in settings file
Background music or sound fx while the break lasts, for example some water flowing, beach waves, forest with animals sounds, rain, relaxing instrumental music. - I don't plan to do that in foreseeable future to keep app small
Window Transparency this could be done I guess, not sure how would that look.
Custom Text/Messages in settings file
Insert at 1 image at the bottom, related to what the message says. If it says "Go, grab a glass of water" then image of a water bottle, a river or waterfalls, or glass of water with ice. If it says "Go, grab a cup of coffee", the image can be coffee grains, coffee with heart, ora person drinking coffee. as I said previously, I don't plan to add pictures
Custom Pause times - this could be done, but I prefer to have little code as possible so I don't plan to add that
Choose from an Analog clock animation or a progress bar, and if progress bar, customizing the accent color.  - this could be done, but I prefer to have little code as possible so I don't plan to add that
`"...nah, I'll just keep going" should be a material button, with customizable text, with a default of "Skip" or "Skip Break"
A "Pause" button at the side of the skip break button, clicking it will show the Pause times context menu.
Settings page needs improvement. Layout, and material animated toggle button instead of checkbox.
Why are the texts lower case!?`  - there will be rework of the whole app soon, so all will change :D
Any reason why the logo in the tray is monochrome by default? because of macOS guidelines
Skip break with a keyboard shortcut - Cmd/Ctrl+X
Language settings. The app's text can be modified in a JSON file. do you mean translations? or break ideas?

Hello there!
Wow, didn't expect a detailed response. I appreciate your time and energy.
Thank your for all the information provided. By "Language settings" yes I mean translations.
Have a nice day!

Custom times - what specifically do you mean? You can edit interval and how long the breaks are

Not sure if it's the same idea but my suggestion would be a work hours interval. Typically, I only want the program to prompt me while I'm working.
Something like:

@kerwin15 hey, thanks for replying!
OMG! I can't believe I didn't notice the '+' sign to change the intervals!  I thought it was part of the text. Thank you for opening my eyes! So at least one of my suggestions is already possible.
About your idea, sounds great to me! Select timers according to weekdays.

guys, there is PR to make + more obvious, maybe comment thee? #488

@hovancik , @kerwin15 was just replying to one of my Feature Requests, so it makes sense discussing it here.

@kerwin15 I love this suggestion. It's like EXPECTED and OBVIOUS that was missed when designing this screen's GUI...
https://user-images.githubusercontent.com/9328196/67353909-9a5f6f80-f508-11e9-8cc3-166fa9bce51e.png


🐛 Metro crashing on every build with EPERM error

What were you trying to do?
When running npx react-native run-android, the build process starts normally and spawns Metro bundler into another window. The build processes normally, until the task :react-native-vision-camera:compileDebugKotlin is reached. The build continues, but at this point Metro crashes with the error message below:
C:\Users\myname\myapp\app\node_modules\metro-hermes-compiler\src\emhermesc.js:77
          throw ex;
          ^

Error: EPERM: operation not permitted, lstat 'C:\Users\myname\myapp\app\node_modules\react-native-vision-camera\android\build\intermediates\cxx\Debug\3e183j45\obj\armeabi-v7a\libVisionCamera.so.tmp22a6dbd'
Emitted 'error' event on NodeWatcher instance at:
    at C:\Users\myname\myapp\app\node_modules\metro\node_modules\jest-haste-map\build\watchers\NodeWatcher.js:275:14
    at FSReqCallback.oncomplete (node:fs:198:21) {
  errno: -4048,
  code: 'EPERM',
  syscall: 'lstat',
  path: 'C:\\Users\\tatuu\\jemma\\app\\node_modules\\react-native-vision-camera\\android\\build\\intermediates\\cxx\\Debug\\3e183j45\\obj\\armeabi-v7a\\libVisionCamera.so.tmp22a6dbd'
}

From what I understand, Metro is watching some temporary build files in the react-native-vision-camera build folder, and when these are cleaned up, Metro crashes with a "operation not permitted" error.
I didn't find any other issues regarding this problem, even though this is the third machine this happens in.
Is this a react-native-vision-camera problem or a Metro configuration issue? How can I run the build process in a way that doesn't trigger the EPERM error in Metro?
Reproduceable Code
No response
What happened instead?
Metro crashes.
Relevant log output
No response
Device
Android emulator
VisionCamera Version
2.13.2
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

I hit the same issue, but my problem is not related with the package react-native-vision-camera because I dont use. I dont know what's the root cause, please help!

any solution?

The only solution I found for now is to just relaunch Metro after this error happens. Pretty annoying but kinda works.

I am having this issue as well but the error mentions 'C:\Users\myname\myapp\app\node_modules\react-native-reanimated\...
I tried everything and I can't get metro not to crash.

I am facing this same issue, Not finding any proper solution!
Anyone found solution for this?

Solution that worked for me:
1  - Build first:
npx react-native run-android
This will crash with the same error but that's ok.
2 - Run metro separately:
npx react-native start or npm start
This works for me (live reload etc..)
I think the issue is metro starts watching files while the npx react-native run-android is still building/accessing files, and the two interfere with each other.

Best solution for now is to run:
adb reverse tcp:8081 tcp:8081 tcp:8081
So you can now build the app once and you don't need to run it again to connect to the metro. You can start metro later and app will connect to it.

I'm experiencing the same issue with vision camera version 2.15.4

1 - Solution
Main reason of this problem is your node version
You have to set the specific version of node which is used to create that project
This can fixed your issue
2 - Solution
Install the latest version of node

same error

RuntimeError: abort(Error: EPERM: operation not permitted, lstat 'E:\Workspace\xxx\example\android\app\build\intermediates\cxx\Debug\6n1z393a\obj\arm64-v8a\libappmodules.so.tmp05deaa0'). Build with -s ASSERTIONS=1 for more info.
    at process.abort (E:\xxx\rn_addtoapp_bridge\example\node_modules\metro-hermes-compiler\src\emhermesc.js:402:15)
    at process.emit (node:events:520:28)
    at processEmit [as emit] (E:\Workspace\xxx\example\node_modules\signal-exit\index.js:199:34)
    at emit (node:internal/process/promises:133:20)
    at processPromiseRejections (node:internal/process/promises:260:27)
    at processTicksAndRejections (node:internal/process/task_queues:97:32)
error Command failed with exit code 1.

same error

RuntimeError: abort(Error: EPERM: operation not permitted, lstat 'E:\Workspace\xxx\example\android\app\build\intermediates\cxx\Debug\6n1z393a\obj\arm64-v8a\libappmodules.so.tmp05deaa0'). Build with -s ASSERTIONS=1 for more info.
    at process.abort (E:\xxx\rn_addtoapp_bridge\example\node_modules\metro-hermes-compiler\src\emhermesc.js:402:15)
    at process.emit (node:events:520:28)
    at processEmit [as emit] (E:\Workspace\xxx\example\node_modules\signal-exit\index.js:199:34)
    at emit (node:internal/process/promises:133:20)
    at processPromiseRejections (node:internal/process/promises:260:27)
    at processTicksAndRejections (node:internal/process/task_queues:97:32)
error Command failed with exit code 1.

already fix the error

metro.config.js

// noinspection JSUnresolvedFunction,JSCheckFunctionSignatures,JSUnusedGlobalSymbols,NpmUsedModulesInstalled

const path = require('path');
const escape = require('escape-string-regexp');
const exclusionList = require('metro-config/src/defaults/exclusionList');
const pak = require('../package.json');
const root = path.resolve(__dirname, '..');
const modules = Object.keys({ ...pak.peerDependencies });

const originBlackListRE = exclusionList(modules.map((m) => new RegExp(`^${escape(path.join(root, 'node_modules', m))}\\/.*$`)));

//region for widows RuntimeError: abort(Error: EPERM: operation not permitted, lstat 'E:\Workspace\xxx\example\android\app\build\intermediates\cxx\Debug\6n1z393a\obj\arm64-v8a\libappmodules.so.tmp05deaa0'). Build with -s ASSERTIONS=1 for more info.
// https://stackoverflow.com/a/9213411/4348530
// https://github.com/mrousavy/react-native-vision-camera/issues/1047#issuecomment-1510030983
// https://github.com/expo/expo-cli/issues/2021#issuecomment-1239989633
const extraBlackListRE = new RegExp("(.*\\android\\.*|.*__fixtures__\\.*|node_modules\\\\react\\\\dist\\\\.*|website\\node_modules\\.*|heapCapture\\bundle\.js|.*__tests__\\.*)$");
const finalBlackListRE = new RegExp("(" + originBlackListRE.source + ")|(" + extraBlackListRE.source + ")")
console.log("metro.config.js originBlackListRE=", originBlackListRE)
console.log("metro.config.js extraBlackListRE=", extraBlackListRE)
console.log("metro.config.js finalBlackListRE=", finalBlackListRE)
// originBlackListRE /(^E:\\Workspace\\rn_addtoapp_bridge\\node_modules\\react\\.*$|^E:\\Workspace\\rn_addtoapp_bridge\\node_modules\\react-native\\.*$|\\__tests__\\.*)$/
// extraBlackListRE /(.*\android\.*|.*\__fixtures__\.*|node_modules[\\]react[\\]dist[\\].*|website\node_modules\.*|heapCapture\bundle.js|.*\__tests__\.*)$/
// finalBlackListRE /((^E:\\Workspace\\rn_addtoapp_bridge\\node_modules\\react\\.*$|^E:\\Workspace\\rn_addtoapp_bridge\\node_modules\\react-native\\.*$|\\__tests__\\.*)$)|((.*\android\.*|.*\__fixtures__\.*|node_modules[\\]react[\\]dist[\\].*|website\node_modules\.*|heapCapture\bundle.js|.*\__tests__\.*)$)/
// exit();
//endregion

const metroConfig = {
  projectRoot: __dirname,
  watchFolders: [root],

  // We need to make sure that only one version is loaded for peerDependencies
  // So we block them at the root, and alias them to the versions in example's node_modules
  resolver: {
    blacklistRE: finalBlackListRE,

Same Error have to start metro again after build

The issue remains on version 3.6.4


add rule name to default reporter

@clutchski any chance of getting this merged?
Would be happy to help maintain this project if you're no longer interested or too busy 🙂

cc @swang

This will be added to @coffeelint/cli in https://github.com/coffeelint/coffeelint/pull/11. Thanks!


Save condition backcollection between runs

Fixes https://github.com/aspnet/AspNetCore/issues/10768

I'm sad that this bug existed for so long though. There's just so many configuration options which makes it difficult to make sure everything is tested thoroughly.


Views

Highlights

[ ] Add Views to the project
[ ] Ensure all linters pass

@Munsa1 I don't see why you should request changes because of styling when the project requirement clearly states this in the image below:
Styling is nice to have but focus on making sure everything functions first. (Note: Ignore login logic, you would be using Devise in coming milestone)

Focus is the logic and since you have even attested to the fact that the logic works, why then request for change when clearly Microverse advice that focuses should be on the logic, please?

Focus is the logic and since you have even attested to the fact that the logic works, why then request for change when clearly Microverse advice that focuses should be on the logic, please?

As I see you could style the Users page as it requires you to match the given design, ignore the other two and ask for another review

@Munsa1 thank you

thank you @KayLemba


Suggesting prompt at unsaved exits

As title.
Better at asterisk at the window title, like vivado, when any change to the project happens.
Hello --> Hello*

v1.0.5版本已添加


Fixing setup to ignore user global configuration for "gpgsign = true"

Why
To have tests passing even if the ~/gitconfig contains
[commit]
gpgsign = true
Redefine the value for gpgsign to false in the repository used for test

@gastaldi I already fixed this with 497b96ed036870b9809823545a4fc363a9677453 , which I think is a better solution in our case.
@ehsavoie 's solution actually writes the value to the repo's config file, which in our case would mean it ends up in the user's repository potentially messing up any GPG setup they might be using locally.
Given the fact that this should only affect devs running the tests I thought it was better to fix this in the code where we push the commits. A better solution might be to have the code ignore any user config settings, but I wasn't able to find a way to do that.
Anyway, closing this PR. Thanks for your time @ehsavoie !

Ah completely missed that. That makes sense. Thanks @quintesse and @ehsavoie


Log buffer too small to dump verifier log 16777215 bytes (10 tries)!

The following error has been identified in net-next CI runs for PRs that introduce conditional branches deep in the datapath code:
Log buffer too small to dump verifier log 16777215 bytes (10 tries)!

This is not currently (as of writing) affecting any released versions of Cilium.
Endpoints go into either waiting-to-regenerate state constantly, or into not-ready state.
 subsys=datapath-loader
2020-03-09T02:54:00.24595512Z level=warning msg="Error fetching program/map!"
From Slack:

@pchaigno bisected to f7cf25b20 ("bpf: track spill/fill of constants") so it looks like verifier state pruning becomes ineffective to the point that we hit the 1mio walked insn limit. Potentially kernel bug.

Temporary mitigation: Bump the maximum number of tries to account for the non-pruned verifier paths:
https://github.com/cilium/iproute2/blob/50a9b6da3509e4caa90d27839dea707030b34347/lib/bpf.c#L1631

The actual complexity error from the BPF verifier can be reproduced on any kernel that contains commit f7cf25b20 ("bpf: track spill/fill of constants") (v5.3+) with the following e.g. steps. You need to bump the max. number of tries in tc as per @joestringer's comment to see the verifier logs):
ip link add cilium-probe type dummy
tc qdisc replace dev cilium-probe clsact
tc filter replace dev cilium-probe ingress bpf da obj ./bpf_lxc.o sec from-container

The object file bpf_lxc.o is attached to this comment.

The actual complexity error from the BPF verifier can be reproduced on any kernel that contains commit f7cf25b20 ("bpf: track spill/fill of constants") (v5.3+) with the following e.g. steps.

(Hit this CI issue already twice today with simple changes in Cilium's BPF data path on bpf-next kernel, where verifier then hits the 1 mio complexity limit.)

@borkmann Has this been improved or fixed with https://github.com/cilium/cilium/commit/06ea89304ec2723cd9f956a541cd77dd5df6a36b?

@borkmann Has this been improved or fixed with 06ea893?

Improved, I did measurements on our current complexity and we seem better than when the issue was more pressing few weeks ago, right now at max around 80k on new kernels + new clang (see slides from bpfconf).
That said, the features we'll merge soon would increase complexity again. Better mitigations need more analysis and fixing on kernel side which I'm investigating in parallel as well.
(Issue here could probably be closed for the time being if you were hinting to this question.)

Closing as this has been fixed with 1.8 and we haven't seen this in a while.

Hm, that's a new one 😓
@SimpCosm Could you open a new issue with a sysdump?

@pchaigno hi paul, I have open a new issue here #16144


TypeError: Cannot read property 'offset' of undefined (reopening issue #297)

I am seeing this exception as well. Here is some more detail, hoping it helps (I am using react-virtualized@9.10.1).
It all seems to start with this stack:
[0]    getSizeAndPositionOfCell           (CellSizeAndPositionManager.js:120)
[1]    getUpdatedOffsetForIndex           (CellSizeAndPositionManager.js:172)
[2]    getUpdatedOffsetForIndex           (ScalingCellSizeAndPositionManager.js:118)
[3]    _getCalculatedScrollLeft           (Grid.js:1034)
[4]    _updateScrollLeftForScrollToColumn (Grid.js:1049)
[5]    updateScrollIndexCallback          (Grid.js:497)
[6]    updateScrollIndexHelper            (updateScrollIndexHelper.js:42)
[7]    componentDidUpdate                 (Grid.js:484)
        .
        .
        .
--- stack bottom ---

The code executing in the top frame is:
return this._cellSizeAndPositionData[index]

index is the input parameter of getSizeAndPositionOfCell(index), and it gets here all the way from _getCalculatedScrollLeft() in frame [3], where it is called targetIndex and is calculated by:
var targetIndex = scrollToColumn < 0 ? finalColumn : Math.min(finalColumn, scrollToColumn);

This expression evaluates to NaN. It is NaN because scrollToColumn is NaN, which in turn is so because I do not pass it in as a prop to the Grid. If I do pass it in with, say, scrollToColumn={ 0 }, the exception disappears. However, if I do this and try to drag the Grid's scroll bar with the mouse, the Grid is continuously reset to position 0, which is no good. I need the scrollToColumn prop to stay undefined, but if I do that I get the error.
The actual exception is triggered when the NaN value returned above propagates into a variable called datum used at:
[0]    getUpdatedOffsetForIndex           (CellSizeAndPositionManager.js:173)
[1]    getUpdatedOffsetForIndex           (ScalingCellSizeAndPositionManager.js:118)
[2]    _getCalculatedScrollLeft           (Grid.js:1034)
[3]    _updateScrollLeftForScrollToColumn (Grid.js:1049)
[4]    updateScrollIndexCallback          (Grid.js:497)
[5]    updateScrollIndexHelper            (updateScrollIndexHelper.js:42)
[6]    componentDidUpdate                 (Grid.js:484)
        .
        .
        .
--- stack bottom ---

The offending line is:
var maxOffset = datum.offset

Since datum is NaN... boom.
All this also applies to scrollToRow, i.e., it must be defined to avoid the exception.
I am unfortunately unable to invest more time in properly understanding the code in order to submit a proper PR. (For instance, I haven't investigated why the exception doesn't occur in the demo at https://bvaughn.github.io/react-virtualized/#/components/Grid even when scrollToColumn is not defined.) I'm just hoping that somebody already versed in the implementation can use this info to fix it the right way.

I forgot to mention that the exception is thrown as soon as I drag-resize the container containing the Grid (which in turn resizes the Grid).

This seems to be fixed with the PR at https://github.com/bvaughn/react-virtualized/pull/820 (passing -1 as the value for scrollToColumn doesn't trigger the exception). This should probably be closed if/when that PR is merged. Leaving it here for reference only.

I am also having this issue on react@16 (probably related to the scrollbar repositioning when column count decreases. not sure if this is still the case on react@15).
I'm temporarily using error-guarding (componentDidCatch) feature to prevent the whole SPA from breaking.

I believe this should be fixed by PR #820 which was just merged and will be released with 9.11 in a few moments

We are bumping into this issue, even on 9.18.5

I'm not sure if the cause is going to turn out to be the same or not — we're currently doing some more detailed investigation and will update here. Hopefully we'll have some more conclusive info shortly!
Not sure if this is the best place for this, or if we should open a new issue

It turns out we reimplemented this bug all by ourselves in a wrapping component and passed NaN in for scrollToRow. smdh
I'd be very happy to PR a defence + warning to cover that scenario if that's something you think would be good or helpful.

Actually, on second though, a PR (+ test case 😁) to cancel the action if a falsey value is provided, rather than throwing an exception and breaking down, and then manually log an error is probably a better UX. I'd say open the PR and we can have a discussion about it there!

It turns out we reimplemented this bug all by ourselves in a wrapping component and passed NaN in for scrollToRow. smdh
I'd be very happy to PR a defence + warning to cover that scenario if that's something you think would be good or helpful.

thanks for pointing to the problem


Excel Export does not include row group headers

Summary of problem or feature request

Code snippet of problem

System details

Operating System
PHP Version
Laravel Version
Laravel-Datatables Version

If you need a custom row headers, you need to override the default print blade template and adjust it to your needs. Just print.blade.php to a new file and set the protected $print = 'path.to.print' on you DataTable class.

I'm using "yajra/laravel-datatables-oracle": "^8.8" and laravel 5.7 ... I couldn't locate print.blade.php


⚠ Jenkins Plugins Artifactory has degraded performance

In 4bd8a5c, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1164 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 2fb1333 after 12 minutes.


Relax targetSdkVersion dependency

Currently this requires SDK version 23, which is very restrictive when trying to support "older" builds of Android. Dropping this to at least 22 would allow use in Android 5 and below.

FWIW, I use the current RxLifecycle release with my app's minSDK set to 18,
target SDK set to 22 and compileSDK set to 23. No problems at all, runs
fine on all devices we test on down to sdk 18.
On Wed, Nov 18, 2015 at 1:26 PM cmathew<EMAIL_ADDRESS>wrote:

Currently this requires SDK version 23, which is very restrictive when
trying to support "older" builds of Android. Dropping this to at least 22
would allow use in Android 5 and below.
—
Reply to this email directly or view it on GitHub
https://github.com/trello/RxLifecycle/issues/55.

@tbsandee thanks for the suggestion. If I set compileSDK to 23, but targetSDK 22, the app will behave like a 22? I ask because I'm trying to avoid the API level 23 permissions model.

Yes I'm in the same situation. Not ready to update to the new permission
model but need a few other sdk23 features. It works great for me.
On Wed, Nov 18, 2015, 4:00 PM cmathew<EMAIL_ADDRESS>wrote:

@tbsandee https://github.com/tbsandee thanks for the suggestion. If I
set compileSDK to 23, but targetSDK 22, the app will behave like a 22? I
ask because I'm trying to avoid the API level 23 permissions model.
—
Reply to this email directly or view it on GitHub
https://github.com/trello/RxLifecycle/issues/55#issuecomment-157878374.

I just took a deeper look at the code and we don't actually use targetSdkVersion except for the sample.

Just a note, this library depends on RxBinding which assumes View.OnScrollChangeListener exists which requires api lvl 23.


travis: compute code coverage with tarpaulin

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@abd1aac). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #37   +/-   ##
=========================================
  Coverage          ?   93.85%
=========================================
  Files             ?        2
  Lines             ?      309
  Branches          ?        0
=========================================
  Hits              ?      290
  Misses            ?       19
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update abd1aac...0e3f8c4. Read the comment docs.


No Babel configuration?

From the README:

The Babel configuration lives inside package.json and will override an external .babelrc file, so if you want to use .babelrc remember to delete the babel property inside package.json.

However, that section was removed in 298da61c53ee731205556f19e302267dadddccaf.

Sounds like we can close this issue then as resolved during the update to Vite.


Bintray Forbidden

I tried compiling, but the Bintray artifact leads to 403 forbidden.

Looks like bintray is no longer continued, I added the gradle plugin directly to the project for the 1.12 branch so you should be able to build it now.


Specify build directory of Cython

This branch specifies the build directory to generate *.cpp files into python-primitiv/build/primitiv/

I tried this branch and observed that some files/directories are still generated in the top directory:

primitiv/*.so
primitiv.egg-info/
dist/

primitiv/*.so are generated by ./setup.py build_ext --inplace command that is hard coded in test command, so it is difficult to change behavior. egg-info too.

Okay.


Consider incorporating more variables with fallback values

Creating an issue to track our discussion in Slack. I will continue to update this issue as more ideas arise.
Pros

We can release new type scale addons that are a collection of variables
Adds more configurability without writing new CSS
Fallbacks keep things clean var(--some-var, 4rem);

Cons

Complexity
More difficult for beginners
Opinionated is sometimes good, configuration can snowball out of control easily
Other frameworks have had issues maintaining variables

Related Reading

http://jxnblk.com/writing/posts/rethinking-variables-in-css/

Thanks for kicking this off. I'm new to all this so bear with me if my questions are silly.

Why fallbacks, instead of variable defaults?
I don't see how this makes tachyons more difficult for beginners. If the variables have default, isn't the basic API the same?

@samselikoff I can't answer your first question - but I can answer your second question.
While variables may seem simple to you - they are often not for beginners. It's an added layer of abstraction. Say you are looking through source code and you see:
.bg-red {
  background-color: var(--red, red);
}

There are multiple things here you may or may not have seen. The syntax for declaring var, what does the double dash mean? Is that a requirement? Or was that an author choice to put a double dash there?
What is --red set to? Now you need to go find the definition of red. So you go find that (which can be non-trivial to do for some new people). Then you decide to change it, but you don't know what else uses --red and now you need to look that up to. Now again, this all might sound simple for an expert like yourself. But what value does the variable bring? And at what cost? To me variables in css are often just hacks to supplement peoples lack of ability to edit text efficiently - and are ripe for messiness in any system where multiple people are touching front-end code. Contrast this with the simple and clear
.bg-red {
  background-color: #ff0000;
}

As a beginner you might still have questions. What is this weird code? Do I have to have a pound sign?
But it's closer to the metal so to speak. css is just css. But memorizing various syntaxes and understanding how variables are utilized and tie together to other classes is an additional hurdle for some. And this makes me hesitate. In my 9 years of working with variables in css I have rarely if ever seen them solve more problems than they create. Tachyons is a personal framework for me - and one of my goals is to be able to collaborate with experts and beginners a like, in a system that suits both their needs. This is a lofty goal for sure, but much of tachyons is the result of user testing both groups and observing in real life how people consume css. And these are some of the best patterns I've found so far. In my user testing though, time and time again I've seen both experts and beginners struggle with pulling apart how the variables are used and what consumes them. And I haven't seen it speed up peoples workflows. I've often debated just ripping out variables all together. So this whole conversation is making me wonder if I should have a variables version and a non-variables version. Because if people want variables - i'd like to make it easy for them to get up and going and configure certain things for sure. But I have also witnessed the complexity that it introduces. You are correct in that the end API is basically the same. But I do think it adds a completely different layer of difficulty for beginners on how to quickly parse the class and understand what is going to happen.
Just my two cents on the matter. Please let me know if this doesn't answer your question.

Thanks for your thoughts. I think with a library like Tachyons one of the first things people will reach for is the ability to customize, e.g. the scales. I personally like the constraints of only being able to choose say 6 font sizes, and knowing I can alter them for my project, but only getting 6. I feel like that's Tachyons nudging me towards good architecture, but not boxing me in, since it's letting me customize.
The point is you should end up with a set of Tachyons suited specifically for your project. Variables seems the best and most natural way to me to achieve this. Of course, I don't have nearly as much experience as you, nor have I done any user testing ever. I just know that as a user of a new CSS library, one of my first instincts will be to try to customize it by seeing what variables the library uses, and changing them (especially when scales are involved).

Hey, not a problem, @samselikoff. @mrmrs and I have been discussing this topic for quite a while (months 😸 ).

Why fallbacks, instead of variable defaults?

The only reason I lean towards fallbacks in place of defaults as I think it will be more straightforward, as we want this to be as beginner friendly, though I could be entirely off base in this regard. If we incorporate variables I'm fine going with either implementation.

I don't see how this makes tachyons more difficult for beginners. If the variables have default, isn't the basic API the same?

Yeah. I agree with you on this point. Especially since variables are already used in the spacing and skin modules. Continuing in this fashion seems intuitive and consistent.

One of my favorite things about Tachyons is the ability for newcomers to get up and running with it. The CSS itself is simple and efficient. However, I do wonder if we are overemphasizing this when it comes to the source CSS. I'd anticipate that the beginner CSSer (please correct my if my assumption is wrong) would be using the built CSS rather than src, and when it comes down to it, the source is just that -- the source. We already use a version of variables for custom media.
I agree with your points, @mrmrs, that variables are often used for bad things and undoubtedly introduce another layer of complexity. I also think that the architecture of Tachyons limits this substantially as variable changes won't propagate to seemingly unrelated declarations (the Sass effect). If we point users to the built CSS, they won't have to know about the existence of variables in the source CSS. This is exceptionally viable for those that consume Tachyons via a git clone or directly editing in node_modules. Unfortunately, not all of us will consume Tachyons CSS in that manner.
Let's consider the following use case for a more advanced user and a build system
The key pieces to the implementation are:

installing via npm
importing from node_modules/ with PostCSS/webpack/build tool du jour
adding custom variables and extension CSS for matching to a given design (palette, shadows, other utils)
build pipeline that compiles css, minifies, fingerprints, etc.

With this, we're never editing the source CSS for Tachyons, and install via npm to help facilitate library updates (ends up being more efficient and elegant than copy pasta-ing as a consumer). Imagine a scenario where we're a given design has a slightly different type scale or measure widths. Without variables, one has a couple options:

Add extension classes like .my-f1 or .my-measure

Mutate the existing Tachyons classes

The first approach isn't desirable because this requires additional classes and their own documentation. The second approach isn't exactly "functional", and is an unfortunate way to handle the need for  2.2rem rather than 2rem. After all, we're using Tachyons so there's no need to write more CSS, I'm lazy af.
I definitely understand if my use case isn't the norm, and we can step around things if necessary. Creating a tachyons-vars library that contains more customizable variables would be a perfectly adequate approach.
Though, for consistency's sake, it seems like if we look to not include variables for certain things like typescale, we should also remove them from spacing (IMO). Otherwise the distinction between what modules have variables and which don't seem sort of arbitrary. As, anything with color or scale should be handled similarly.

Ultimately, @mrmrs, you're the BDFL of Tachyons CSS (I just do the JavaScripts : )), and your decisions have always been better for my stylesheets. It's like you know something I don't or something 🚀 📡 🌕 . So, I trust whatever your decision will be on this. I seek to provide a bit more context on my use case and why I lean towards using variables.
👯

I agree with your thoughts John. Adam's writings and the Tachyons library have been my introduction to functional css over the past few weeks. As I've showed the library to my colleagues, the first thing I explain is how functional css brings constraints, and why this is a good thing. We install Tachyons (by copying the built .css file), and start building out mockups. It's awesome that we can build custom designs using only css classes from a third-party library.
Then, we need a class that doesn't exist, or we need to modify a scale. We don't have PostCSS in any of our apps at the moment - most of our apps have the ability to work with Sass. They ask if we're supposed to customize things at all, or if we're supposed to stay within the boundaries and scales that Tachyons come with. I explain that no, the author explicitly says the library is meant to be customizable. But, the lesson is still important - you don't go making just any class you want, you stick to a scale and incorporate that into your design. More consistency, fewer decisions, etc.
At this point, if we were able to crack open a variables.scss file, or even look for variables at the top of a source, this would be really helpful. In our Ember apps using Bootstrap, we do it like this:
// app.scss
// Customize Bootstrap
$brand-primary: red;
@include 'bootstrap';

That gives us customized Bootstrap, and I think it's great. We still work within the constraints of the lib, but we're able to override defaults.
I think this is the convention over configuration argument. Ultimately, there are a lot of decisions made by Tachyons about class names, scale names and the like. These decisions don't affect things one way or another, and I'm glad Tachyons has made these decisions. I think it's good if other teams' projects can leverage them, to stay on board with the community, and to be more productive. But as with any conventional library there does need to be an escape hatch for when the defaults don't line up.

We use variables with fallbacks in production with several different customers. They've been useful for configurability from customer to customer allowing us to quickly change the branding to fit each customer's needs.
However, we take this to the extreme. This may be deemed as overkill and pointless, but after testing we ran into issues during the Bamboo's build and deploy leaving some things unstyled or broken. Since our client's assets/config don't live in the base project we have a set of default variables that live in base + client variables for each customer. This setup means that regardless of the client's config their site won't ever be broken or look too out of wack.
In short, we use variables as a fall backs as well. This only adds more complexity, but has been useful for theming, changing fonts, and even for different page layouts. Here's an example:
    --link-color : var(--client__link-color, var(--default__link-color));
    --text-color : var(--client__text-color, var(--default__text-color));
    --text-muted-color : var(--client__text-muted-color, var(--default__text-muted-color));

I'd like to add on to @johnotander's comments. The issue with overriding or defining your own classes after importing tachyons is that it breaks responsiveness. Say we want to change .f4 from font-size: 1.25rem to font-size: 1.125rem, we would do something like this:
/* from tachyons: */
.f3 { font-size: 1.5rem }
.f4 { font-size: 1.25rem }

@media (--breakpoint-not-small) {
  .f3-ns { font-size: 1.125rem }
  .f4-ns { font-size: 1.125rem }
}

/* my overrides: */
.f4 { font-size: 1.125rem }

If I have a

, the .f3-ns no longer overrides .f4 because .f4 now appears after .f3-ns.
Then we're left with editing the source directly which makes bringing updates from upstream more difficult.

Experiencing the same issue as @kentor ; my media queries don't do their thing with my mobile-first custom "f7" to default tachyons "f5-m". Has this been resolved elsehow/internally (w/o using node-css-mqpacker)?

We have several flavors of tachyons that use variables for those that desire them. Outside of colors going to refrain from using vars in the main repo.


More ores (diamond, iron etc.) in default biomes?

Hi there,
there are few ore blocks in default biomes. How can I scale it up a bit?

Tweak the Ore settings in the resource queue of each biome: check here and here

Also, please sign into our forum to get better/faster help from the existing community of TC users. There's only 1-2 people who respond to these issues on a regular basis :D


[Engineering] Lower time for botbuilder-ai tests

Addresses # 2338
Description
This PR optimizes the time for the botbuilder-ai tests having no impact in the code coverage numbers and reducing the execution time approximately from 1s to 872ms.
Specific Changes
Changes in luisRecognizer.test.js

Moved some LuisRecognizer instances to the top of the describe to be reused by some tests instead of creating new ones.
Fixed eslint warnings.

Testing

Promoted


BLE disconnection caused by channel map request or connection parameter update request

Describe the bug
I have a nRF52832 running Zephyr v1.13.0, which works as a BLE slave, connecting simultaneously to 4 mobile devices, including ios and android.
To have a good connection quality, I have put all devices very closed to each other. The distance between them should be less than 50cm, and no obstacle in the middle.
In this case, BLE connection drop on Zephyr is found much more often than single connection, and the sniffing result shows the disconnection always occurs following Channel Map Request or Connection Parameter Update Request.
I have attached the sniffing log file generated by V1 Nordic nRF Sniffer, as well as some screenshots. Details about the sniffer can be found here:
https://learn.adafruit.com/introducing-the-adafruit-bluefruit-le-sniffer/nordic-nrfsniffer
What have you tried to diagnose or workaround this issue?
To figure out what's happening, I put some log print to console, then I've captured the error returned in the code:
subsys\bluetooth\conroller\ll_sw\ctrl.c
static u8_t conn_update(struct connection *conn, struct pdu_data *pdu_data_rx)
{
if (((pdu_data_rx->llctrl.conn_update_ind.instant - conn->event_counter) & 0xFFFF) > 0x7FFF) {
return BT_HCI_ERR_INSTANT_PASSED;  // This causes connection drop
}

20190307-link_lost_channel_req.zip

Can you reproduce this with the latest master branch? Most people are busy stabilising it for the 1.14 release currently, so if this issue is applicable there it may get prioritised better.

@jeff-setec This is a limitation due to overlapping connection events in slave role. As the individual masters have no knowledge of other connection in the slave, they use the default instant offset of 6 events. If 4 connection events in the slave overlap, each connection listens to its master on the 4th connection event, if the event that the slave is listening fails to synchronize with the master, it has 2 more (forced) consecutive connection interval to listen, and if the packet from master is received beyond 6 intervals, then the slave will disconnect with reason instant passed.
I will analyze the logs later today, but could you let me know the zephyr board you are using (as 50 cm is too low a range you are observing), the reason for the missed instant could be due to poor radio conditions, like noisy 2.4GHz environment.

@jhedberg and @cvinayak
Thanks!
The Zephyr is running on a BLE module Laird BL652-SA-01, which is mounted on the board we designed, and is working as a slave connecting simultaneously to 4 mobile devices, 1 iPhone 7 Plus, 1 iPhone XR, 1 LG-X240YK, and 1 android tablet. All mobile devices are running an app we designed.
The disconnection occurs more between the Zephyr BLE module and the LG phone, and it seems all because of the same disconnection reason as I raised here.

Switching this to feature request because this is an inherent limitation on the Bluetooth spec. We will analyze a bit further but it looks like the timing is imposed by the centrals (mobile phones) over which we have no control.

@jeff-setec can you add traces for all 4 connections? you would need to use 4 sniffers in parallel. As long as you have 4 Nordic DKs you should be able to do that.

@jeff-setec I have looked at the sniffer logs you gave and there seems to be a bug here.
Could you log print the variables (instant in the packet, and conn->event_counter) used in calculating that the instant has passed with a sniffer capture for that connection?

@jeff-setec Also if possible could you check if the issue is reproducible on v1.14, and use the v2 of the nrf sniffer?

Setting to low due to the uncertainty about the root cause.

@jeff-setec could you please let us know if this is still an issue on the current master?

Closing due to inactivity from reporter


Program announcement on social media

depends of issue #7

Ready:
https://www.notion.so/galileos-paradox/Schedule-announcement-08678a78c1db492393d192fbdee8a4a6?pvs=4


Why commision failed (CON-720)

In the 30 matching process, commision failed twice, I want to know the reason and how to solve this problem

@maenkai Attach the log files for failed commissioning which would help in knowing the reason for failure and narrowing down on the problem. If you have commissioner logs that would help as well.

@maenkai Please upload the complete logs as requested

Close the issue temporarily and wait for the log to be provided after this replay


Criteria class not able to read downloaded bertqa.pt file

I used the code from https://github.com/deepjavalibrary/djl/blob/master/jupyter/pytorch/load_your_own_pytorch_bert.ipynb
The code downloaded https://djl-ai.s3.amazonaws.com/mlrepo/model/nlp/question_answer/ai/djl/pytorch/bertqa/0.0.1/trace_bertqa.pt.gz and unzipped the file to build/pytorch/bertqa/bertqa.pt.  I can see the file. However, the following error occurs:
Exception in thread "main" java.io.FileNotFoundException: Parameter file with prefix: bertqa not found in: /home/jtang/temp/dlj/build/pytorch/bertqa or not readable by the engine.
at ai.djl.mxnet.engine.MxModel.load(MxModel.java:109)
at ai.djl.repository.zoo.BaseModelLoader.loadModel(BaseModelLoader.java:161)
at ai.djl.repository.zoo.Criteria.loadModel(Criteria.java:168)
at org.dlj.example.Example.main(Example.java:70)
Process finished with exit code 1
The code causing the error is :
    Criteria<QAInput, String> criteria = Criteria.builder()
            .setTypes(QAInput.class, String.class)
            .optModelPath(Paths.get("build/pytorch/bertqa/")) // search in local folder
            .optTranslator(translator)
            .optProgress(new ProgressBar()).build();

The sample code is able to download the file. Why is it having issues reading it?

In your project, you included multiple engines in your classpath. DJL picked up MXNet in your case.
You can either set the default engine to PyTorch: -Dai.djl.default_engine=PyTorch
Or you can tell Criteria which engine you want to use:
    Criteria<QAInput, String> criteria = Criteria.builder()
            .setTypes(QAInput.class, String.class)
            .optModelPath(Paths.get("build/pytorch/bertqa/")) // search in local folder
            .optTranslator(translator)
            .optEngine("PyTorch")
            .optProgress(new ProgressBar()).build();

Another way to tell DJL which engine to use is adding a serving.properties file in your model directory, in this case build/pytorch/bertqa folder:
engine=PyTorch

Thank you Frank. I was following the code from https://github.com/deepjavalibrary/djl/blob/master/jupyter/pytorch/load_your_own_pytorch_bert.ipynb  verbatim. I didn't realize the .option("PyTorch") was needed. That fixed the problem. Thank you for the clarification.


Add basic version of package.json file

This change also adds a .gitignore file to allow us to ignore the node
modules which are downloaded

@dareid I have updated the PR


Update update-deps action to next release iteration

Update update-deps action to next release iteration

/cc @knative-extensions/knative-release-leads

/lgtm


Docs about tstl.transpileFiles config required

let result = await tstl.transpileFiles([filePath], {
    //conf is original from tsconfig.json
    ...conf, //not so easy...
    //mix ts and tstl
    ...conf.tstl,
    strict: conf.compilerOptions.strict,
    plugins: [...conf.compilerOptions.plugins],
    types: [...conf.compilerOptions.types],
    //if not . then put out to src
    rootDir: '.',
    //out path with same name from src
    luaBundle: `${conf.compilerOptions.outDir}/${path.basename(filePath).replace('.ts', '.lua')}`,
    //entry point
    luaBundleEntry: filePath,
})

We already have docs for configuration: https://typescripttolua.github.io/docs/configuration What are you missing?

@Perryvw About config in tstl.transpileFiles. Its working something wrong... Example: "strict", "plugins" and "types" from "compilerOptions" not working and must be defined at config root (thats actual only on using config in tstl.transpileFiles).

Also luaBundle from tstl  is too not working and must be defined at config root.
(i was try)
{
    tstl: {
        ...conf.tstl,
        luaBundle: `${conf.compilerOptions.outDir}/${path.basename(filePath).replace('.ts', '.lua')}`
    }
}


Patch github version into json creating vsix.

Codecov Report
Base: 92.75% // Head: 92.75% // No change to project coverage :thumbsup:

Coverage data is based on head (7dd8cfb) compared to base (5980121).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1680   +/-   ##
=======================================
  Coverage   92.75%   92.75%
=======================================
  Files         352      352
  Lines       25144    25144
=======================================
  Hits        23323    23323
  Misses       1821     1821

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Initial support of #[derive(Inspect)]

Closes #186
Example use
From tests/it/inspect.rs:
use rg3d::{
    // maybe add `prelude`?
    core::inspector::{Inspect, ProprertyInfo},
    scene::transform::Transform,
};

#[test]
fn inspect_attributes() {
    #[derive(Default, Inspect)]
    pub struct Data {
        #[inspect(skip)]
        skipped: u32,

        #[inspect(group = "Pos", name = "Super X")]
        x: f32,

        #[inspect(expand)]
        tfm: Transform,

        #[inspect(group = "Pos")]
        y: f32,
    }

    let data = Data::default();

    let expected = vec![
        PropertyInfo {
            name: "Super X",
            group: "Pos",
            value: &data.x,
        },
        PropertyInfo {
            name: "Y",
            group: "Pos",
            value: &data.y,
        },
    ];

    assert_eq!(data.properties()[0..2], expected);
    assert_eq!(data.properties().len(), 2 + data.tfm.properties().len());
}

PR contents
Preparation

[x] Restructuring tests/  for modulability and to reduce the number of test crates.
c.f. Delete Cargo Integration Tests
[x] Implement Debug and PartialEq for PropertyInfo (for assert_eq! in later tests)

Requested features in #186

[x] Support Struct { named_field: value }
[x] #[inspect(skip)]
[x] #[inspect(name = ..)]
[x] #[inspect(group = ..)]

More

[x] #[inspect(expand)]

TODOs

Supporting other kinds of structs and enums.
Improving the Inspect trait for performance (if necessary)
(Just some refactoring to #[derive(Visit)])

Ah, #[inspect(expand)] corresponds to this line:
        properties.extend(self.local_transform.properties().into_iter());

Better name to expand would exist 🤔

Omg, that's for sure very fast! Great job! I'll check the PR asap!


Update beginner-tutorial.rst

Added some additional text to better understand and help prevent too much demands for support.

Pull Request Test Coverage Report for Build 66

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 62:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

Pull Request Test Coverage Report for Build 66

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 62:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


Field error-message font-size looks too small

From @H3dz on July 12, 2017 21:11
The material error-message font-size looks smaller when compared with the paper-input-error font-size.
paper-input-error uses --paper-font-caption which is 12px and
material-text-field uses 0.7em instead of --material-caption-font-size
Copied from original issue: vaadin/vaadin-themes#27

Fixed in master. Now uses 0.75em which is 12px for the default 16px font size.


updating gotuf in godeps

That is all
Signed-off-by: David Lawrence<EMAIL_ADDRESS>(github: endophage)

Tests failing. Seem to be a real failure.

Failure was because downloadSigned obscured the raw data from the callers, which they required to populate cache. This mean the root never got cached (and it's the only thing that needs to be), so update was failing on the check of the snapshot hash for root vs the cache (the first time through, it fails and downloads the roots again, but when it fails on the update retry, it errors out of the update).

LGTM, but I've been wrong in the past.


Support dynamic scales for Qconv's and Dequantize

There is a fair amount of code duplication. Can you refactor existing functions in mkldnn_emitter and reuse them?


transformers version incompatible

when i try to pip install transformers==2.4.1,there are some problems:
ImportError: cannot import name 'AutoModelForMaskedLM' from 'transformers'
(C:**\Anaconda3\envs\py_light\lib\site-packages\transformers_init_.py)
so, i updated the transformers version（3.0.2)，but can't find ROBERTA_PRETRAINED_MODEL_ARCHIVE_MAP...
from transformers import BertPreTrainedModel, RobertaConfig, RobertaModel, ROBERTA_PRETRAINED_MODEL_ARCHIVE_MAP, RobertaForSequenceClassification
ROBERTA_PRETRAINED_MODEL_ARCHIVE_MAP
Does anyone know how to fix it? Thank you!

update to 2.8.0


Add "dsh reset" command

In some cases docker-compose provisioning may fail (e.g. IP or port conflict, etc.) and containers may get corrupted. Even if the underlying issue is then fixed and containers restarted with dsh up there may still be issue with volumes being corrupted.
The only way to fix corrupted volumes is by completely removing and recreating a container.
So dsh reset would be doing docker-compose stop && docker-compose rm --force && docker-compose up -d. It should also warn the user and explain the consequences of its actions.

Resolved in https://github.com/blinkreaction/drude/commit/d2dfd056b3870fb65c2a1d29f3d8614f2b76ef9d


Tone Analyzer service not parsing JSON for "tone_categories" properly

[tone-analyzer] rest kit not parsing returning json properly
Example used
`import ToneAnalyzer
let username = "your-username-here"
let password = "your-password-here"
let version = "YYYY-MM-DD" // use today's date for the most recent version
let toneAnalyzer = ToneAnalyzer(username: username, password: password, version: version)
let text = "I was asked to sign a third party contract a week out from stay. If it wasn't an 8 person group that took a lot of wrangling I would have cancelled the booking straight away. Bathrooms - there are no stand alone bathrooms. Please consider this - you have to clear out the main bedroom to use that bathroom. Other option is you walk through a different bedroom to get to its en-suite. Signs all over the apartment - there are signs everywhere - some helpful - some telling you rules. Perhaps some people like this but It negatively affected our enjoyment of the accommodation. Stairs - lots of them - some had slightly bending wood which caused a minor injury."
let failure = { (error: RestError) in print(error) }
toneAnalyzer.getTone(text, failure: failure) { tones in
// code here
}`
Expected result:
should have found keys
Actual Result
keyNotFound("tone_categories")
This is the latest version that i am using
target device is iPhone 8 IOS 11.1
After downloading the Rest Kit and stepping through the code I believe the issue is within the the Parsing for the JSON returned. the API call is returning the correct JSON but the Parsing is erroring out and returning no keys found. I believe it has to do with the nesting of the dictionary but I am unsure.

I'm afraid you ran into a bug with the Swift SDK! It looks like the 2017-09-25 release of the Tone Analyzer service removed the tone_categories key, which causes the SDK's JSON parsing to fail. Thanks for letting me know. I'll work on a fix soon.
In the meantime, a quick fix is to set the version date earlier. For example, you could set it to the previous release of 2017-07-06.
Here is a sample app for Tone Analyzer that I was able to test and run successfully.
Hope that helps!

I'm going to close this issue in favor of #695, which we'll use to track the update of the Tone Analyzer code for the 2017-09-25 release.
In the mean time, please use a version date prior to 2017-07-06 and let me know if you run into any more trouble!


Added Bitcoin Green

tested priv and pub key

Thanks for this.
The addition of BITG is great, thanks for that.
The change to -m SimpleHTTPServer is a python2 vs python3 thing. Python 3 on windows would also be -m http.server`. This is not a 'windows' difference, so the change to readme is not valid for merging.
The version is only changed when a release is made, and this PR is not a release, so the commit changing the version is not something I'd want to merge.
Please remove the changes to readme and the version, keeping just the BITG parameters.

You have clean BITG in same repo now.
Re: "This is not a 'windows' difference", the only reason I want to add it is because I don't have a module like you have in readme and I always have to research for "correct" module name

Do you want me to create a new pull request?

the only reason I want to add it is because I don't have a module like you have in readme and I always have to research for "correct" module name

Fair enough, I think it's a good idea, I can add a note about python2 using a different command for the server. Thanks for the feedback and pull request.


Adds RFC to reimplement npm start within the buildpack start command

Readable

Shouldn't we also call the postscript hook mentioned here[1]? My concern is when the start command is not a never-terminating-process like node server.js, but something like <cli-installed-via-npm-install> <args>. I think chalk-cli is probably an example.

https://github.com/npm/cli/blob/v6.14.8/docs/content/using-npm/scripts.md#npm-start

I've updated the RFC to include executing poststart scripts as part of the command.


[JavaFX-Part 4] Update FXML of DialogBox

Current:

Problem:
Text overrun may occur, and longer text will not be fully displayed but replaced with ellipsis instead.
Proposed:
Replace line with:
<Label fx:id="dialog" text="Label" wrapText="true" minHeight="-Infinity">

@flexibo any thoughts on this suggestion? I remember this aspect came up during the writing of part 5.

@JiaXinEu @damithc ah yes, IIRC the issue is also fixed by removing the prefHeight for VBox.

@flexibo Thanks for the inputs.
@JiaXinEu You can send a PR for this. It may be better to keep the original, point out the problem, and provide the two possible solutions.

Ok, submitted PR #37

@damithc @JiaXinEu Actually I was wondering if it is better to just replace that line altogether using either one of the solutions (can just use JiaXinEu's solution). It might be a lot clearer for the students this way and avoid any confusion.

It might be a lot clearer for the students this way and avoid any confusion.

I'm fine with that too.
Normally I prefer for students to learn about a problem and also how to solve it (rather than not encounter it at all) but this specific problem is not that important, so OK to avoid it entirely.

I have sent a PR based on this.

It may be better to keep the original, point out the problem, and provide the two possible solutions.

Perhaps I can create another PR for this so we can decide on which is more readable?

replace that line altogether using either one of the solutions

Perhaps I can create another PR for this so we can decide on which is better?

Sure @JiaXinEu


Device Model Pointer

It might be nice to integrate DeviceModel Pointer for each component that can represent a standard SPICE Model associated with it. This will be more helpful for running simulations with SPICE simulator of choice while generating the netlist.

https://github.com/FOSSEE/eSim/tree/master/library/deviceModelLibrary/Templates has some templates to create DeviceModels.  However, it doesn't have any description associated with it the parameters as well as no way of discerning what these parameters actually mean.

https://github.com/chezou/tabula-py is a project I found for extracting tables out of a pdf file. Currently, I have been doing manual conversion of tables in http://ngspice.sourceforge.net/docs/ngspice-34-manual.pdf, line by line which gets messy/complicated. I tried it with the manual and I could get nice dataframes:
>>> df = tabula.read_pdf("http://ngspice.sourceforge.net/docs/ngspice-34-manual.pdf", pages='124')
>>> df
[        Name                                 Parameter Units  Default  Example
0    IS (JS)                        Saturation current     A  1.0e-14  1.0e-16
1        JSW               Sidewall saturation current     A      0.0  1.0e-15
2          N                      Emission coefficient     -        1      1.5
3         RS                          Ohmic resistance     Ω      0.0      100
4         BV                 Reverse breakdown voltage     V        ∞       40
5        IBV              Current at breakdown voltage     A   1.0e-3   1.0e-4
6        NBV            Breakdown Emission Coefficient     -        N      1.2
7   IKF (IK)                      Forward knee current     A      0.0   1.0e-3
8        IKR                      Reverse knee current     A      0.0   1.0e-3
9       JTUN              Tunneling saturation current     A      0.0      NaN
10    JTUNSW     Tunneling sidewall saturation current     A      0.0      NaN
11      NTUN            Tunneling emission coefficient     -       30      NaN
12    XTITUN  Tunneling saturation current exponential     -        3      NaN
13       KEG        EG correction factor for tunneling     -      1.0      NaN
14       ISR          Recombination saturation current     A    1e-14      1pA]
>>> df = tabula.read_pdf("http://ngspice.sourceforge.net/docs/ngspice-34-manual.pdf", pages='125')
>>> df
[Empty DataFrame
Columns: [Name, Parameter, Units, Default, Example, Scalefactor]
Index: [],   CJP (CJSW)           Zero-bias junction sidewall\rcapacitance    F   0.0   .1pF  perimeter
0         FC  Coefficient for forward-bias\rdepletion bottom...    -  0.50      -        NaN
1        FCS  Coefficient for forward-bias\rdepletion sidewa...    -  0.50      -        NaN
2     M (MJ)                  Area junction grading coefficient    -  0.50    0.5        NaN
3       MJSW            Periphery junction grading\rcoefficient    -  0.33    0.5        NaN
4    VJ (PB)                                 Junction potential    V  1.00    0.6        NaN
5        PHP                       Periphery junction potential    V  1.00    0.6        NaN
6         TT                                       Transit-time  sec  0.00  0.1ns        NaN, Empty DataFrame
Columns: [Name, Parameter, Units, Default, Example]
Index: [],             TM1                      1st order tempco for MJ   1/◦C   0.0              -
0           TM2                      2nd order tempco for MJ  1/◦C2   0.0              -
1   TNOM (TREF)            Parameter measurement temperature     ◦C  27.0             50
2    TRS1 (TRS)                      1st order tempco for RS   1/◦C   0.0              -
3          TRS2                      2nd order tempco for RS  1/◦C2   0.0              -
4           TM1                      1st order tempco for MJ   1/◦C   0.0              -
5           TM2                      2nd order tempco for MJ  1/◦C2   0.0              -
6          TTT1                      1st order tempco for TT   1/◦C   0.0              -
7          TTT2                      2nd order tempco for TT  1/◦C2   0.0              -
8           XTI      Saturation current temperature exponent      -   3.0  3.0pn\r2.0Sbd
9          TLEV          Diode temperature equation selector      -   0.0            NaN
10        TLEVC    Diode capac.temperature equation selector      -   0.0            NaN
11    CTA (CTC)       Area junct.cap.temperature coefficient   1/◦C   0.0              -
12          CTP  Perimeter junct.cap.temperature coefficient   1/◦C   0.0              -]


Seems to be incompatible with ELK version "2.4.0"

The client socket is disconnected the moment it tries to talk with the server.

Well the latest driver has been build for elasticsearch version 2.3.5 so i guess it is not yet compatible with version 2.4.0. I will have to build it for the latest version in order for it to work. Ill update an close this issue once it is done.

Ok, i have updated the driver to es 2.4. Please download the latest release (<IP_ADDRESS>) and use that driver to connect with your cluster. Let me know if that works as intended.

Great! It works now. Thank you so much!


Can't write any integration test

integration test, I mean Ember integration test.
TypeError: Cannot read property 'get' of undefined
When launching the basic, generated integration test of Ember

Wrong issue, did not occur because of ember-routable-modal


ImportError: DLL load failed: The specified module could not be found.

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 Pro
TensorFlow installed from (source or binary): binary
TensorFlow version: 1.12.0
Python version: 3.6.7(also tried 3.7.1)
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source): Na
GCC/Compiler version (if compiling from source): Na
CUDA/cuDNN version: 9.0
GPU model and memory: GeForce GTX 1060 6GB

Describe the problem
I executed "pip install tensorflow" command and then wanted to test it by opening python on command prompt. I typed "python" and "import tensorflow" then I got this error message below:
Python 3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 13:35:33) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow
Traceback (most recent call last):
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\imp.py", line 343, in load_dynamic
return _load(spec)
ImportError: DLL load failed: The specified module could not be found.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow_init_.py", line 24, in
from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python_init_.py", line 49, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 74, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
File "C:\Users(User)\AppData\Local\Programs\Python\Python36\lib\imp.py", line 343, in load_dynamic
return _load(spec)
ImportError: DLL load failed: The specified module could not be found.
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

Can you try the solution provided here.

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


CLion not avalable in Github Spaces (avaliable via SSH)

CLion not avalable in Github Spaces, but avaliable via SSH
When conenct using SSH:

When using Github Spaces:

Additional context
OS: Linux
OS Version: 5.15.78-1-manjaro
OS Architecture: amd64
Java Version: 17.0.5
Java Runtime Version: 17.0.5+7-b469.67
Java Vendor: JetBrains s.r.o.
Available CPUs: 16
Max Memory: 536870912
Free Memory: 33242624
Total Memory: 161480704
IDE Version: 2022.2.4
IDE: JetBrains Gateway 2022.2.4
Plugin Version: <IP_ADDRESS>0
Plugin path: /home/winnie/.local/share/JetBrains/Toolbox/apps/Gateway/ch-0/222.4459.11.plugins/github-codespaces-gateway
Plugin ID: com.github.codespaces.jetbrains.gateway

And install Rust plugin by default, if possible :D
As it's bit tricky to install plugins into remote IDE now. And it is required for every new space.