Add IPv6 Host support to SSH.

Changes REGEX to allow for IPV6 entry
Alters Uri generation to support IPV6 hosts on create

I successfully tested this using an IPV6 IP Address and checked with backwards compatibility using IPV4 based hostnames. The one catch is the error when your device does not have an IPV6 address is a tad confusing. It simply says "connect failed: ENETUNREACH (Network is unreachable)" which is quite true if you do not have an IPV6 address or internet set up correctly, but may take a second to figure out.

Did you test this on older devices? I don't think IPv6 parsing in the Uri class works for pre-KitKat or something.

Not yet. I can do so in the next 24 hours. How far back do we hope to support?  If not, would adding a version check to determine the regex be acceptable?

We need to support back to API v8.

I started working on this a while ago, but didn't finish it. It might give you some hints as to what's wrong:
https://github.com/kruton/connectbot/tree/transportAddress

@jbcode42, will this solve #36?

@rhansby Yes, however I haven't checked backwards compatibility yet, but it will allow it to take IPV6 literals. I was able to successfully input the IPV6 address in #36 and attempt to connect. It failed because I was not on an IPV6 network at the time (And even then, I don't know if it is a valid host test), but it did recognize the full IPV6 address and correctly recognize it as a hostname and at least attempt to connect to it.

Tested fix on HTC Inc running CM 7.1 (Gingerbread 2.3.7 API Level 10) and it worked. Attempting to boot a emulator failed, so instead I elected to downgrade the HTC Inc again to CM 6.1 (Froyo 2.2.1 API Level 8). Confirmed working.
I think the reason this works is how the parseHost() call works in android.net.Uri. Normally it would split on the ":" symbol unless we encode the hostname. I looked at the source code from 2.3.2_r1 on GrepCode and it shows the following:
        private String parseHost() {
            String authority = getEncodedAuthority();
            if (authority == null) {
                return null;
            }

            // Parse out user info and then port.
            int userInfoSeparator = authority.indexOf('@');
            int portSeparator = authority.indexOf(':', userInfoSeparator);

            String encodedHost = portSeparator == NOT_FOUND
                    ? authority.substring(userInfoSeparator + 1)
                    : authority.substring(userInfoSeparator + 1, portSeparator);

            return decode(encodedHost);
        }

I do show that android version 2.0 does not bother with encoding/decoding the host string so my fix would not work on that version. GrepCode does not have an intermediate version available for reading and since it worked in my test, I have not tried to pull the relevant code from git.

Is there anything else needed on this?

I haven't had time to test this yet. Do shortcuts on the desktop still work?

Yes, tested on both the older device and the newer device previously
mentioned. Just checking in because I will likely be unable to code or test
anything further for the next couple days.
On Oct 8, 2015 5:41 PM, "Kenny Root"<EMAIL_ADDRESS>wrote:

I haven't had time to test this yet. Do shortcuts on the desktop still
work?
—
Reply to this email directly or view it on GitHub
https://github.com/connectbot/connectbot/pull/276#issuecomment-146708618
.

It should be good, then. I'll test it in the next day or so.

Cool. I hope sometime next week when I have more time to see about Telnet IPV6. Thanks!

Fixes #36


Write all tests and update readme

We need to write test for all providers and update README.md

@wikkiewikkie Are you interested?

@lk-geimfari  Is the idea here that someone can use Elizabeth as part of the test suite for their project?
For example, they have a function that should check that the user input a valid e-mail address.  In the test for that function, they could use Elizabeth to generate fake e-mail addresses as input?

from pytest-elizabeth import personal
from myproject import validate_email

def test_validate_email(personal):
    result = validate_email(personal.email())
    assert result

Something like that?

@wikkiewikkie Yeah. For case like in example above and for another cases. It's a plugin and we should not import nothing
def test_generic(personal, elizabeth_locale):
"""Test elizabeth fixture."""
    assert isinstance(generic, elizabeth.Personal)
    assert personal.name()
    assert elizabeth_locale == 'en'

@wikkiewikkie

@wikkiewikkie Now you're collaborator and we can work on it together. You can merge PRs without me.

@wikkiewikkie Also, if you interested in testing tool i have an experimental project that provider regex patterns. Here you can look at details

We also can do from expynent something useful.

@lk-geimfari I will check out expynent

@wikkiewikkie Okay. Thanks!


Better column population logic

Poor IF logic currently used, line 150 droid2sqlite.py onwards.

Well... this has all been rewritten...


Error compressing twitter widgets minified script

We use around 30 different js files with libraries and other stuff, and the nlsclientscript works well with them. But when I try to add twitter widgets library, the browser complains about missing parenthesis and other stuff.
You can test it adding the twitter widgets library to any example and enable compress:
https://platform.twitter.com/widgets.js

Hi,
i don't really want to:) On the demo page http://nlacsoft.net/nlsclientscript/merging-js, there's a section:

"The minification is done by the JShrink library. That's a 3rd party, so in case of js minification issues please turn to its developers."

I really mean it ;)
Alternatively you may set a regexp in the config file:
'mergeJsExcludePattern' => '/twitter\\.com/i'
so NLSClientScript won't merge and compress it but will link it separately instead.
Let me know if the workaround fixed the issue.

Has the workaround fixed the issue? Another chance is to link the uncompressed version (if any) of the file, the minification may work for that.


Add file comments for each source module

Each file contains only the copyright info. It would be good to have a 1-5 lines at the top of each file, describing the module.

[ ] antidote_app
[ ] antidote_error_monitor
[ ]  antidote_node_event_handler
[ ] antidote_pb_process
[ ] antidote_warning_monitor
[ ] binary_utilities
[ ] binary_utilities
[ ] clocksi_downstream
[ ] clocksi_materializer
[ ] clocksi_readitem_server
[ ] clocksi_vnode
[ ] cure
[ ] dc_meta_data_utilities
[ ] dc_utilities
[ ] inter_dc_manager
[ ] inter_dc_query_response
[ ] inter_dc_query_response_sup
[ ] inter_dc_txn
[ ] log_utilities
[ ] logging_vnode
[ ] materializer
[ ] materializer_vnode
[ ] zmq_utils

@deepthidevaki @albsch I have a made a small PR can you PTAL?


We are getting FlutterMethodChannel* _methodChannel; error while creating build for iOS

Here is my error console
/Users/ankitafirake/Documents/flutter/bin/flutter --no-color build ios --simulator
Building com.adamcompanies.technicianapp for simulator (ios)...
Running pod install... 9.6s
Running Xcode build...
Xcode build done. 12.4s
Failed to build iOS app
Error output from Xcode build:
↳

BUILD FAILED *

Xcode's output:
↳
/Users/ankitafirake/documents/flutter/.pub-cache/hosted/pub.dartlang.org/webview_flutter-0.3.24/ios/Classes/JavaScriptChannelHandler.m:8:3: error: unknown type name 'FlutterMethodChannel'
FlutterMethodChannel* _methodChannel;
^
/Users/ankitafirake/documents/flutter/.pub-cache/hosted/pub.dartlang.org/webview_flutter-0.3.24/ios/Classes/JavaScriptChannelHandler.m:12:40: error: expected a type

(instancetype)initWithMethodChannel:(FlutterMethodChannel*)methodChannel
^
/Users/ankitafirake/documents/flutter/.pub-cache/hosted/pub.dartlang.org/webview_flutter-0.3.24/ios/Classes/JavaScriptChannelHandler.m:29:17: warning: unused variable 'arguments' [-Wunused-variable]
NSDictionary* arguments = @{
^
1 warning and 3 errors generated.
note: Using new build system
note: Planning build
note: Constructing build description

Encountered error while building for simulator.
Process finished with exit code 1

Here is my flutter doctor console
flutter doctor
Downloading android-arm-profile/darwin-x64 tools... 2.3s
Downloading android-arm-release/darwin-x64 tools... 1.9s
Downloading android-arm64-profile/darwin-x64 tools... 2.2s
Downloading android-arm64-release/darwin-x64 tools... 1.9s
Downloading android-x64-profile/darwin-x64 tools... 2.2s
Downloading android-x64-release/darwin-x64 tools... 1.8s
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.6 19G2021 darwin-x64, locale en-IN)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[!] Android Studio (version 4.1)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[!] Connected device
! No devices available
! Doctor found issues in 3 categories.

Here is my flutter doctor console
flutter doctor
Downloading android-arm-profile/darwin-x64 tools... 2.3s
Downloading android-arm-release/darwin-x64 tools... 1.9s
Downloading android-arm64-profile/darwin-x64 tools... 2.2s
Downloading android-arm64-release/darwin-x64 tools... 1.9s
Downloading android-x64-profile/darwin-x64 tools... 2.2s
Downloading android-x64-release/darwin-x64 tools... 1.8s
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.6 19G2021 darwin-x64, locale en-IN)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[!] Android Studio (version 4.1)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[!] Connected device
! No devices available
! Doctor found issues in 3 categories.

Here is my pubspec file
environment:
sdk: ">=2.7.0 <3.0.0"
cupertino_icons: ^1.0.0
http: ^0.12.2
shared_preferences: ^0.5.12
fluttertoast: ^7.1.1
google_fonts: ^1.1.0
pin_code_fields: ^5.2.0
google_sign_in: ^4.5.4
flutter_facebook_login: ^3.0.0
device_preview: ^0.4.8
image_picker: ^0.6.7+11
firebase_messaging: ^7.0.3
provider: ^4.3.2+2
rect_getter: ^0.1.0
flutter_screenutil: ^3.2.0
dio: ^3.0.10
geolocator: ^6.1.13
google_maps_flutter: ^1.0.6
flutter_datetime_picker: ^1.4.0
intl: ^0.16.1
rflutter_alert: ^1.1.0
carousel_slider: ^2.3.1
badges: ^1.1.4
flutter_staggered_animations: ^0.1.2
location: ^3.1.0
flutter_html: ^1.0.2
flutter_inappwebview: ^4.0.0+4
searchable_dropdown: ^1.1.3
firebase_core: ^0.5.2
code_field: ^1.22.0
connectivity: ^2.0.1

Here is my pubspec file
environment:
sdk: ">=2.7.0 <3.0.0"
cupertino_icons: ^1.0.0
http: ^0.12.2
shared_preferences: ^0.5.12
fluttertoast: ^7.1.1
google_fonts: ^1.1.0
pin_code_fields: ^5.2.0
google_sign_in: ^4.5.4
flutter_facebook_login: ^3.0.0
device_preview: ^0.4.8
image_picker: ^0.6.7+11
firebase_messaging: ^7.0.3
provider: ^4.3.2+2
rect_getter: ^0.1.0
flutter_screenutil: ^3.2.0
dio: ^3.0.10
geolocator: ^6.1.13
google_maps_flutter: ^1.0.6
flutter_datetime_picker: ^1.4.0
intl: ^0.16.1
rflutter_alert: ^1.1.0
carousel_slider: ^2.3.1
badges: ^1.1.4
flutter_staggered_animations: ^0.1.2
location: ^3.1.0
flutter_html: ^1.0.2
flutter_inappwebview: ^4.0.0+4
searchable_dropdown: ^1.1.3
firebase_core: ^0.5.2
code_field: ^1.22.0
connectivity: ^2.0.1

Flutter doctor -v
flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.6 19G2021 darwin-x64, locale en-IN)
• Flutter version 1.22.5 at /Users/ankitafirake/documents/flutter
• Framework revision<PHONE_NUMBER> (5 weeks ago), 2020-12-10 11:54:40 -0800
• Engine revision ae90085a84
• Dart version 2.10.4
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/ankitafirake/Library/Android/sdk
• Platform android-30, build-tools 30.0.2
• ANDROID_HOME = /Users/ankitafirake/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
• Xcode at /Users/ankitafirake/Desktop/Xcode.app/Contents/Developer
• Xcode 11.3, Build version 11C29
• CocoaPods version 1.10.0.beta.2
[!] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[!] Connected device
! No devices available
! Doctor found issues in 3 categories.

Flutter doctor -v
flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.6 19G2021 darwin-x64, locale en-IN)
• Flutter version 1.22.5 at /Users/ankitafirake/documents/flutter
• Framework revision<PHONE_NUMBER> (5 weeks ago), 2020-12-10 11:54:40 -0800
• Engine revision ae90085a84
• Dart version 2.10.4
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/ankitafirake/Library/Android/sdk
• Platform android-30, build-tools 30.0.2
• ANDROID_HOME = /Users/ankitafirake/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
• Xcode at /Users/ankitafirake/Desktop/Xcode.app/Contents/Developer
• Xcode 11.3, Build version 11C29
• CocoaPods version 1.10.0.beta.2
[!] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[!] Connected device
! No devices available
! Doctor found issues in 3 categories.

Hello dear! i knew this problem is take your time so much, but i spent time an hour to solve it before i know the answer by doing some step in xcode:

Open ios project that create in flutter project and open it on xcode
Select " Pods"
Change on menu " Build Active Architecture Only" to true and depend on running mode.

*Sorry! for my english

Hello dear! i knew this problem is take your time so much, but i spent time an hour to solve it before i know the answer by doing some step in xcode:

Open ios project that create in flutter project and open it on xcode
Select " Pods"
Change on menu " Build Active Architecture Only" to true and depend on running mode.

*Sorry! for my english

Hi  @aTeamSolace
webview_flutter isn't included in your pubspec.yaml which might mean one of youyour packages is using it such as flutter_inappwebview  and it's an old version of the package based on the error pub.dartlang.org/webview_flutter-0.3.24/ios/.
Can you please try a possible solution provided above in https://github.com/flutter/flutter/issues/73948#issuecomment-760383624?
If the problem persists, Can you please provide flutter run --verbose logs, and a minimal complete reproducible code sample without using third-party packages such as flutter_inappwebview but using webview_flutter?
Thank you

Hi  @aTeamSolace
webview_flutter isn't included in your pubspec.yaml which might mean one of youyour packages is using it such as flutter_inappwebview  and it's an old version of the package based on the error pub.dartlang.org/webview_flutter-0.3.24/ios/.
Can you please try a possible solution provided above in https://github.com/flutter/flutter/issues/73948#issuecomment-760383624?
If the problem persists, Can you please provide flutter run --verbose logs, and a minimal complete reproducible code sample without using third-party packages such as flutter_inappwebview but using webview_flutter?
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


fix(material/datepicker): Return union of view component types

TypeScript inferred the return type of _getCurrentViewComponent as the type of the month view only. Tsickle propagates that to the JavaScript compiler which optimizes the code as monthView._init was the only method that could be called. This causes runtime errors.
 It needs to be prefixed with fix(material/datepicker) or squashed into the initial commit.

Thank you very much for the help, @crisbeto! It passed all the checks.


ARM Cortex-M: Fix booting in no-multithreading mode

This PR fixes the issues with Cortex-M when building without multi-threading support. In particular

it properly sets the PSP back to the main stack so main() uses the main stack and ISRs will use the _interrupt_stack. This has never worked, but needs to work, in order to use IRQs in the no multi-threading case.
configures FPU, MPU guards and PSPLIM accordingly, to mimic what is going on in the normal CONFIG_MULTITHREADING=y case. This allows to use FPU and HW stack overflow in main().
adds the required hook in the kernel z_cstart() to make the change less intrusive; only Cortex-M is affected - no other functional cases.

I am going to add a simple test to verify the feature.
Also this PR fixes a minor enhancement issue with the interrupt stack in reset.S.
Fixes #26796
Fixes #16210

Using #27136 on current master I've confirmed broken CONFIG_MULTITHREADING=n support on:

nucleo_l476rg (program dies after BOOT_BANNER)
nrf52840dk_nrf52840 (program runs, but once interrupt fires everything stops)
frdm_k64f (program dies after BOOT_BANNER)

Clearly CONFIG_MULTITHREADING=n is a poorly tested configuration, and the failure is not Nordic-specific.
With this patch using master button test (and default CONFIG_MULTITHREADING=y) all platforms pass.
With #27136 (CONFIG_MULTITHREADING=n) this PR on current master all platforms pass, so functional checks look good.  Review incoming.

With #27136 (CONFIG_MULTITHREADING=n) this PR on current master all platforms pass

however, if the explicit irq_unlock(0) added in that code is removed so interrupts are enabled in main the tests run but no button presses are detected.  All platforms.
So though this fixes #26796, it does not fix disabling multithreading.

@pabigot thanks for the review. Yeap, there are multiple typos and style fixes needed, I will revisit this PR and write also a test.

One style issue, and a couple typos in commit messages. This definitely improves things, though not enough to make single-threaded code work without extra help (#8393).

This patch is not meant to fix all issues with NO MULTITHREADING; i.e. it does not automatically enable IRQs; I still leave this to the user. But at least, it makes things work, if one wants run main() with IRQs and APIs that do not depend on kernel.
I am not against enabling IRQs automatically - we could do this in another RFC PR.

One style issue, and a couple typos in commit messages. This definitely improves things, though not enough to make single-threaded code work without extra help (#8393).

Patch 1: s/little intrucive/unintrusive/
Patch 3: s/Cortex-M ARCHictecture/Cortex-M architecture/

fixed now

I have built the mcuboot for nrf52840dk with the fix, with CONFIG_MULTITHREADING=n and serial recovery enabled.
I have been able to successfully upload and confirm test images via serial so the problem with serial not working in non-multithreading mode has gone.

@anangl I addressed your comments, particularly the ones suggesting functional changes.
Uploaded the test that verifies the single-thread operation in ARM Cortex-M

@anangl could you take another look please?

I have used the newest changes from this PR to compile mcuboot in non-multithreading mode and serial recovery enabled, repeating the previous tests https://github.com/zephyrproject-rtos/zephyr/pull/27343#issuecomment-668119695 and everything seems to work correctly.

I have used the newest changes from this PR to compile mcuboot in non-multithreading mode and serial recovery enabled, repeating the previous tests #27343 (comment) and everything seems to work correctly.

Thanks @de-nordic
I think maybe we have a chance also to enabled IRQs before jumping to main, and then solve #8393 as well, for Cortex-M.
Is this something we would like to do, @pabigot @andyross ?

Adding DNM, cause I want @anangl to look at the patch, before getting it in.

I do think interrupts should be enabled automatically: it's surprising when they aren't.

before jumping to main

To clarify, that's before jumping to bg_thread_main, not to main, right?  Because drivers that initialize post-kernel may be counting on having interrupts work.

I do think interrupts should be enabled automatically: it's surprising when they aren't.

before jumping to main

To clarify, that's before jumping to bg_thread_main, not to main, right? Because drivers that initialize post-kernel may be counting on having interrupts work.

Yes, correct.
Again, I would do this for Cortex-M only, if there is an interest for it, but not a wide consensus to do this for all ARCHes.

Again, I would do this for Cortex-M only, if there is an interest for it, but not a wide consensus to do this for all ARCHes.

I think it needs to be consistent across architectures.
Also a decision on whether to enable interrupts should not delay merge of this PR.

I think maybe we have a chance also to enabled IRQs before jumping to main, and then solve #8393 as well, for Cortex-M.

When you do a PR with that I can check the mcuboot for you.

@andyross thanks. There are some advantages of keeping the two stacks (but I agree with you that a single stack would work too). Zephyr ARM architecture code heavily depends on the fact that the ISRs use a different stack from the thread mode; if we want to use the same stack, lots of things need to be re-worked, and I wanted to avoid this.
A good example is the stack overflow case (and in general, the fault handling). Assessing faults is done by inspecting the stack frame which is on PSP; if we want to use MSP in the no-multithreading case, fault inspection needs a re-write.
Also, ARM reset code uses the interrupt stack with the Process stack pointer. We don't want to modify this common code and create confusion. Since IRQs will use the Main stack pointer, we need to switch back to using MSP in thread mode after initialization; this requires lots of #ifdef CONFIG_MULTITHREADING in the architecture code base.
Using a different stack pointer, depending on CONFIG_MULTITHREADING will also be a bit confusing for developers that need to debug Cortex-M code; they are used to see the main() running on PSP.
The interrupt stack gets defined in kernel code, same as the main stack, so we're reserving the area anyways, so not using it does not bring any benefit (unless we change kernel code for that, which i did not want to do). The point was to support this feature properly, with as few changes to the code base as possible.

Do not merge until the outcome of #27415 is decided.

Do not merge until the outcome of #27415 is decided.

Not sure I agree with this principle, @carlescufi. The discussion of whether to support single-threading or not is legitimate, however, this PR is a bug fix of an existing feature in zephyr, it is only a bug fix, and affects nothing outside the single-threading case. What is the timeline for the decision in #27415? In the mean time, why do you suggest having a broken feature in Zephyr instead of a feature working fine, even if it is candidate for removal?

Do not merge until the outcome of #27415 is decided.

Not sure I agree with this principle, @carlescufi.

I'm sure I do not agree.
The existing behavior is wrong on all ARM Cortex-M.  This fixes it.  Merging an acceptable low-risk fix seems appropriate even if the long-term presence of the feature is in doubt.  We're rapidly approaching feature freeze and need to start looking at stabilizing what we've got.  It would be bad to put this off for very long.

@ioannisg and @pabigot This introduces functionality that is strictly tied to CONFIG_MULTITHREADING, that was my reasoning for waiting to merge this. But since deciding on the future of that Kconfig variable might take time, I agree to merge this in the meantime.


BYOD export job (from D365 F&O to Azure SQL DB) failed due to special characters in the SQL account password

Hi there,
If this has not been raised before, I'd like to suggest a note to be included in the Microsoft Docs (around BYOD), suggesting not to use special characters (such as "~") as the password of the SQL account in the SQL DB.
Even though publishing entity to the SQL DB was successful, this the export job in D365 F&O and no information/logs were there to suggest what the cause of the problem, giving me so much headache.
Hopefully this suggestion is of any use.
Thanks.
RA
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 33f75161-0776-a6c1-dc10-dc20ea26973f
Version Independent ID: 55a81394-4606-745a-9fd2-59fb257d1086
Content: Bring your own database (BYOD) - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/analytics/export-entities-to-your-own-database.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @Sunil-Garg
Microsoft Alias: sunilg

Hello rizal-ang-- thanks for catching this and reporting to us. We will investigate as to why the jobs fail when this happens. Thanks.


Problem with cmdPressKey() function, can't press ENTER

There is a problem with source code, I think part with typing language, cmdPressKey function. Command "ENTER" (maybe more) is not execute in cmd.
That for example execute well.:
Keyboard.press(KEY_RETURN);
delay(50);
Keyboard.release(KEY_RETURN);
But Yours function cmdPressKey with  pressChar(convertLangChar(key)) not.
Configuration.:
Current mode: c
Current language: en
Current payload: demo1.txt

Sorry for not replying you earlier. Sometimes your target host can't accept characters at the speed that ducky is "typing" them. You can slower it down by increasing delays in printChar function. The other thing you can try is increasing delay between command execution by using DELAY or DEFAULTDELAY commands in your scripts.

This solution didn't help.


Revert "Revert "Fix remaining holes in stack trace demangling""

Reverts flutter/flutter#60916
Error is unrelated, will be fixed by https://github.com/flutter/flutter/pull/60668

LGTM.
I assumed it was caused by a bad merge up or something.  Thanks for fixing.

FYI @fkorotkov I cannot get these tasks to rerun :(
https://cirrus-ci.com/build/4837175218929664

@jonahwilliams there was a new build though: https://cirrus-ci.com/build/6311036733095936
Let me check why GH didn't update statuses.

Oh. It's the issue with different sets of tasks for branch builds vs PR builds. There is no way to delete a check run. I've reported it to GH and will implement a workaround on a Cirrus side.

@PixelToast @dnfield could you try and re-land the PR today? The revert-revert doesn't really seem to work


Put "Change connection(s) driver" button to "Connection configuration" interface near the "Driver settings" button

Reference https://github.com/dbeaver/dbeaver/issues/21710#issuecomment-1790638138

Users habitually go to the edit link interface to modify the driver of a single link

Thanks for the suggestion


CI: switch to Travis-CI container mode

Try switching to Travis new container-based infra. Disables sudo, but enables ccache, which might speed up our testing times.

Looks promising --- 'fast' test suite takes 10 min instead of the previous 20-25min when everything is in ccache.

Going to merge, about twice faster.

The speed improvement is impressive!


Adding 150-ai-rainbow

This is ready for review.  Please let me know if I need to change anything.
The json file is edited to include updated links to download page on RunwayML and Browse Models page.

Amazing!


Refreshing on AJAX pages

I can't seem to get ads refreshing every 30 seconds and working for ajax pages. I have the ads refreshing but it currently doesn't work once I change pages two or more times. This is what my code looks like right now.
$('.adunit:not(".display-block")').dfp({  dfpID: '52137663',  enableSingleRequest: false,  afterAllAdsLoaded: function() {  setInterval(function() {  jQuery.dfp(); }, '30000'); } });

I have also tried with this code:
`
function ads () {
    $('.adunit:not(".display-block")').dfp({
        dfpID: '52137663/top-ad-gh-music-web',
		enableSingleRequest: false,
		afterAllAdsLoaded: function() {
		setInterval(function() {
        jQuery.dfp();
    }, '30000');
}
    });
    }

$(document)
        .on('page:load', function () {
            ads();
        })
        .ready(function () {
            ads();
        });`

I am running a test on this page http://derekcoleman.me/pzzb6/

I have added this code to refresh the ad whenever the URL changes and it helps it work for the first 'page' change but then it doesn't refresh the ad once it's on the new URL.
function hrefHandler(){
    this.oldHref = window.location.href;
    this.Check;
    var that = this;
    var detect = function(){
        if(that.oldHref!=window.location.href){
            ads();
        }
    };
    this.Check = setInterval(function(){ detect() }, 100);
}
var hrefDetection = new hrefHandler();

Your example page seems to be stuck in some kind of loop... its calling it repeatedly over and over 10 times per second at least...

This jquery mobile test I put together a while back seems to have the same kind of idea... and the same issue with ads not showing up after a while... from what I can see though everything is loading correctly... it just appears to be google limiting the amount of times a creative will appear on a single page within a certain amount of time... if you have more creatives it will be fine I think.
http://coop182.github.io/jquery.dfp.js/dfptests/demo1.html

I removed the last bit of code that was checking if the URL has changed so now I have the same exact code as what is on the demo page but it's not working correctly. It is still having the same problem of not working once I navigated to a new 'page'.  Derek Riccardo Coleman
On Monday, February 22, 2016 3:59 AM, Matt Cooper<EMAIL_ADDRESS>wrote:

This jquery mobile test I put together a while back seems to have the same kind of idea... and the same issue with ads not showing up after a while... from what I can see though everything is loading correctly... it just appears to be google limiting the amount of times a creative will appear on a single page within a certain amount of time... if you have more creatives it will be fine I think.http://coop182.github.io/jquery.dfp.js/dfptests/demo1.html—
Reply to this email directly or view it on GitHub.

@derekcoleman i had the same problem and solved it by implementing it like this first example:
https://support.google.com/dfp_premium/answer/4578089
take notice of the googletag.pubads().refresh([slot]);

@samburgers could you please explain for someone who's not that code savvy how you did it? :)

@boooooooorbs You will need to use some of Google's native methods in jquery.dfp.js beforeEachAdLoaded callback like such:
beforeEachAdLoaded: function (adUnit) {
	var slots = googletag.pubads().getSlots(); // returns array of Slot objects
	var slot = slots[slots.length - 1];
	var slotName = adUnit.attr('id');

	googletag.display(slotName);
	googletag.pubads().refresh([slot]);
}


Support SSL to mce_cli.py

We are executing the step on https://github.com/linkedin/datahub/tree/master/metadata-ingestion, but the mce_cli.py (and other python apps) don't support SSL connection to Kafka.
A suggestion would be to use the same as kafka-topic.sh does:
kafka-topics --command-config kafka.config
Ex. kafka.config
ssl.truststore.location=./resources/keys/pt/pt.d2.aws.truststore.jks
ssl.truststore.password=XXXXXXXXXXXXX
ssl.keystore.location=./resources/keys/pt/pt.d2.aws.keystore.jks
ssl.keystore.password=XXXXXXXXXXXXXX
ssl.key.password=XXXXXXXXXXXXX
security.protocol=SSL
So the command could be:
python3 metadata-ingestion/mce-cli/mce_cli.py produce -l metadata-events/mxe-schemas/src/renamed/avro/com/linkedin/mxe/MetadataChangeEvent.avsc -d metadata-ingestion/mce-cli/bootstrap_mce.dat -b bootstrap.d2-pt.aws.com:9092 -s https://schemaregistry.d2-pt.aws.com:8443 -c kafka.config
Thank you.
Fabio

Makes sense. Would you be interested in creating a PR for this, @fabiofilz?

fyi this is moving to contrib soon anyway. I'll be sure to keep this in mind for the Java port :)

Hi @mars-lan,
Please find the PR with SSL feature.
Thank you.
Fabio


Inventory wording of "part number" and "part ID" inconsistency

Environment

Python version: 3.5.2

NetBox version: 2.5.13

Found Locations

https://NETBOXURL/dcim/devices/#/inventory/
https://NETBOXURL/dcim/inventory-items/#/edit/
https://NETBOXURL/dcim/inventory-items/

Expected Behavior
Having the same wording for the part number between different locations
Observed Behavior
At location 1, the word choice is "Part Number", were as location 2 and 3 use the wording of "Part ID".
Opinion
I personally would like to see "Part Number" used instead of "Part ID".

Changing the table header to "Part ID." "ID" was selected over "number" because many part IDs are alphanumeric.


FIX：When 28181 stream stopped，Stream API does not remove it

Codecov Report

Merging #1926 into feature/gb28181 will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@                 Coverage Diff                 @@
##           feature/gb28181    #1926      +/-   ##
===================================================
- Coverage            56.58%   56.58%   -0.01%
===================================================
  Files                  122      122
  Lines                51553    51553
===================================================
- Hits                 29171    29170       -1
- Misses               22382    22383       +1

Impacted Files
Coverage Δ

trunk/src/app/srs_app_gb28181.cpp
0.00% <0.00%> (ø)

trunk/src/protocol/srs_service_utility.cpp
72.43% <0.00%> (-0.55%)
:arrow_down:

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 a617d36...05151f4. Read the comment docs.


Update version: Microsoft.PowerBI version 2.123.742.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Update to metadata for latest version (2.123.742.0). Installer URL is intentionally the same.


Build tools error, cannot find symbol

cannot find symbol
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
^
symbol:   variable O
location: class VERSION_CODES
I guess the build tools version is old

👋 Have you changed your Android SDK versions at all? Can you post the contents of your android/build.gradle file?

@shubhang93 we set the versions in react-native-location/android/build.gradle to ours and the build error went away
def DEFAULT_COMPILE_SDK_VERSION          = 26
def DEFAULT_BUILD_TOOLS_VERSION          = "26.0.1"
def DEFAULT_TARGET_SDK_VERSION           = 26
def DEFAULT_GOOGLE_PLAY_SERVICES_VERSION = "16.+"

@matt-oakes if a PR can be made soon that'd be great, or else we can fork as well. Thank you!

Closing. See comment in #67.

I'm getting the same error as this.
compileSdkVersion 28
minSdkVersion 23
targetSdkVersion 28

Can you please advise how I can solve this issue? Thanks in advance!


[BUG] - Producing Each child in a list should have a unique “key” prop console warning

1. Describe the bug
I am using AnimatePresence and motion.div to create a dialog component. But it's producing Each child in a list should have a unique “key” prop console warning after opening the drawer component. If I remove the AnimatePresence and motion.div, the error is no longer produced.
2. Sceenshot

3. Environment details

React v18.3.1
Framer-motion: v11.15.0
Bundler: Webpack
Browser: Chrome 131.0

FAQs
Part of code that producing the error:
const animationVariants = {
	left: {
		open: {
			x: 0,
		},
		exit: {
			x: '-100%',
		},
	},
	right: {
		open: {
			x: 0,
		},
		exit: {
			x: '100%',
		},
	},
};

export interface DrawerPanelProps {
	/** Drawer content. */
	children: ReactNode | ( ( props: { close: () => void } ) => ReactNode );
	/** Additional class names. */
	className?: string;
}

const DrawerPanel = ( { children, className }: DrawerPanelProps ) => {
	const { open, position, handleClose, drawerRef, transitionDuration } =
		useDrawerState();

	return (
		<AnimatePresence>
			{ open && (
				<div className="fixed inset-0">
					<div
						className={ cn(
							'flex items-center justify-center h-full',
							{
								'justify-start': position === 'left',
								'justify-end': position === 'right',
							}
						) }
					>
						<motion.div
							ref={ drawerRef }
							className={ cn(
								'flex flex-col gap-5 w-120 h-full bg-background-primary shadow-2xl my-5 overflow-hidden',
								className
							) }
							initial="exit"
							animate="open"
							exit="exit"
							variants={ animationVariants[ position! ] }
							transition={ transitionDuration }
						>
							{ typeof children === 'function'
								? children( { close: handleClose! } )
								: children }
						</motion.div>
					</div>
				</div>
			) }
		</AnimatePresence>
	);
};

DrawerPanel.displayName = 'Drawer.Panel';

export default DrawerPanel;

What happens if you remove just where children is rendered?

What happens if you remove just where children is rendered?

@mattgperry, When there are no children the warning produces that time also. I forgot to mention the warning produced for production build only.


API for generic Sensors

This PR intends to add a generic API for creating and using sensors in robot_dart. This will also remove CameraOSR class, and adds a Magnum Camera class as a sensor. Things remaining:

Remove CameraOSR
Add python bindings
Add tests for sensors (only camera now) Tests for IMU and FT sensors added (no test for camera can be made at the moment)
Add a simple IMU sensor
Add force/torque sensor
Body Node name does not suffice. We need to have reference to the robot.

@jbmouret the first version of the sensor API should be completed. This PR fixes #79. I'll merge once the CI tests pass.

Merging.. I note that we should create a random generator (similar to limbo) and add some noise models to the sensors...


React Native Mapbox - MapboxNavigation was not found in the UIManager

So I've been trying to integrate @homee/react-native-mapbox-navigation I've followed the install instructions found here https://github.com/homeeondemand/react-native-mapbox-navigation to the letter 3 times now. I continue to get the following error, this is from the simulator:

This is from the console:
Invariant Violation: requireNativeComponent: "MapboxNavigation" was not found in the UIManager.

 This error is located at:
     in MapboxNavigation (at react-native-mapbox-navigation/index.js:6)
     in MapboxNavigation (at ManifestScreen.tsx:37)
     in RCTView (at View.js:34)
     in View (at Themed.tsx:40)
     in View (at ManifestScreen.tsx:36)
     in RCTView (at View.js:34)
     in View (at Themed.tsx:40)
     in View (at ManifestScreen.tsx:25)
     in ManifestScreen (at SceneView.tsx:122)
     in StaticContainer
     in StaticContainer (at SceneView.tsx:115)
     in EnsureSingleNavigator (at SceneView.tsx:114)
     in SceneView (at useDescriptors.tsx:153)
     in RCTView (at View.js:34)
     in View (at CardContainer.tsx:245)
     in RCTView (at View.js:34)
     in View (at CardContainer.tsx:244)
     in RCTView (at View.js:34)
     in View (at CardSheet.tsx:33)
     in ForwardRef(CardSheet) (at Card.tsx:573)
     in RCTView (at View.js:34)
     in View (at createAnimatedComponent.js:165)
     in AnimatedComponent (at createAnimatedComponent.js:215)
     in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:555)
     in PanGestureHandler (at GestureHandlerNative.tsx:13)
     in PanGestureHandler (at Card.tsx:549)
     in RCTView (at View.js:34)
     in View (at createAnimatedComponent.js:165)
     in AnimatedComponent (at createAnimatedComponent.js:215)
     in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:544)
     in RCTView (at View.js:34)
     in View (at Card.tsx:538)
     in Card (at CardContainer.tsx:206)
     in CardContainer (at CardStack.tsx:619)
     in RCTView (at View.js:34)
     in View (at Screens.tsx:84)
     in MaybeScreen (at CardStack.tsx:612)
     in RCTView (at View.js:34)
     in View (at Screens.tsx:54)
     in MaybeScreenContainer (at CardStack.tsx:494)
     in CardStack (at StackView.tsx:462)
     in KeyboardManager (at StackView.tsx:458)
     in SafeAreaProviderCompat (at StackView.tsx:455)
     in RCTView (at View.js:34)
     in View (at StackView.tsx:454)
     in StackView (at createStackNavigator.tsx:87)
     in StackNavigator (at ManifestTabNavigator.tsx:60)
     in DirectionsNavigator (at SceneView.tsx:122)
     in StaticContainer
     in StaticContainer (at SceneView.tsx:115)
     in EnsureSingleNavigator (at SceneView.tsx:114)
     in SceneView (at useDescriptors.tsx:153)
     in RCTView (at View.js:34)
     in View (at BottomTabView.tsx:55)
     in SceneContent (at BottomTabView.tsx:172)
     in RCTView (at View.js:34)
     in View (at ResourceSavingScene.tsx:58)
     in RCTView (at View.js:34)
     in View (at ResourceSavingScene.tsx:41)
     in ResourceSavingScene (at BottomTabView.tsx:166)
     in RCTView (at View.js:34)
     in View (at src/index.native.js:123)
     in ScreenContainer (at BottomTabView.tsx:146)
     in RCTView (at View.js:34)
     in View (at BottomTabView.tsx:145)
     in SafeAreaProviderCompat (at BottomTabView.tsx:144)
     in BottomTabView (at createBottomTabNavigator.tsx:45)
     in BottomTabNavigator (at ManifestTabNavigator.tsx:19)
     in ManifestTabNavigator (at SceneView.tsx:122)
     in StaticContainer
     in StaticContainer (at SceneView.tsx:115)
     in EnsureSingleNavigator (at SceneView.tsx:114)
     in SceneView (at useDescriptors.tsx:153)
     in RCTView (at View.js:34)
     in View (at CardContainer.tsx:245)
     in RCTView (at View.js:34)
     in View (at CardContainer.tsx:244)
     in RCTView (at View.js:34)
     in View (at CardSheet.tsx:33)
     in ForwardRef(CardSheet) (at Card.tsx:573)
     in RCTView (at View.js:34)
     in View (at createAnimatedComponent.js:165)
     in AnimatedComponent (at createAnimatedComponent.js:215)
     in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:555)
     in PanGestureHandler (at GestureHandlerNative.tsx:13)
     in PanGestureHandler (at Card.tsx:549)
     in RCTView (at View.js:34)
     in View (at createAnimatedComponent.js:165)
     in AnimatedComponent (at createAnimatedComponent.js:215)
     in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:544)
     in RCTView (at View.js:34)
     in View (at Card.tsx:538)
     in Card (at CardContainer.tsx:206)
     in CardContainer (at CardStack.tsx:619)
     in RCTView (at View.js:34)
     in View (at Screens.tsx:84)
     in MaybeScreen (at CardStack.tsx:612)
     in RCTView (at View.js:34)
     in View (at Screens.tsx:54)
     in MaybeScreenContainer (at CardStack.tsx:494)
     in CardStack (at StackView.tsx:462)
     in KeyboardManager (at StackView.tsx:458)
     in SafeAreaProviderCompat (at StackView.tsx:455)
     in RCTView (at View.js:34)
     in View (at StackView.tsx:454)
     in StackView (at createStackNavigator.tsx:87)
     in StackNavigator (at navigation/index.tsx:45)
     in RootNavigator (at navigation/index.tsx:29)
     in EnsureSingleNavigator (at BaseNavigationContainer.tsx:409)
     in ForwardRef(BaseNavigationContainer) (at NavigationContainer.tsx:91)
     in ThemeProvider (at NavigationContainer.tsx:90)
     in ForwardRef(NavigationContainer) (at navigation/index.tsx:26)
     in Navigation (at App.tsx:18)
     in RNCSafeAreaProvider (at SafeAreaContext.tsx:74)
     in SafeAreaProvider (at App.tsx:17)
     in App (created by ExpoRoot)
     in ExpoRoot (at renderApplication.js:45)
     in RCTView (at View.js:34)
     in View (at AppContainer.js:106)
     in DevAppContainer (at AppContainer.js:121)
     in RCTView (at View.js:34)
     in View (at AppContainer.js:132)
     in AppContainer (at renderApplication.js:39)
 - node_modules/react-native/Libraries/LogBox/LogBox.js:148:8 in registerError
 - node_modules/react-native/Libraries/LogBox/LogBox.js:59:8 in errorImpl
 - node_modules/react-native/Libraries/LogBox/LogBox.js:33:4 in console.error
 - node_modules/expo/build/environment/react-native-logs.fx.js:27:4 in error
 - node_modules/react-native/Libraries/Core/ExceptionsManager.js:104:6 in reportException
 - node_modules/react-native/Libraries/Core/ExceptionsManager.js:171:19 in handleException
 - node_modules/react-native/Libraries/Core/setUpErrorHandling.js:24:6 in handleError
 - node_modules/expo-error-recovery/build/ErrorRecovery.fx.js:9:32 in ErrorUtils.setGlobalHandler$argument_0
 - node_modules/regenerator-runtime/runtime.js:63:36 in tryCatch
 - node_modules/regenerator-runtime/runtime.js:293:29 in invoke
 - node_modules/regenerator-runtime/runtime.js:63:36 in tryCatch
 - node_modules/regenerator-runtime/runtime.js:154:27 in invoke
 - node_modules/regenerator-runtime/runtime.js:164:18 in PromiseImpl.resolve.then$argument_0
 - node_modules/react-native/node_modules/promise/setimmediate/core.js:37:13 in tryCallOne
 - node_modules/react-native/node_modules/promise/setimmediate/core.js:123:24 in setImmediate$argument_0
 - node_modules/react-native/Libraries/Core/Timers/JSTimers.js:130:14 in _callTimer
 - node_modules/react-native/Libraries/Core/Timers/JSTimers.js:181:14 in _callImmediatesPass
 - node_modules/react-native/Libraries/Core/Timers/JSTimers.js:441:30 in callImmediates
 - node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:387:6 in __callImmediates
 - node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:135:6 in __guard$argument_0
 - node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:364:10 in __guard
 - node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:134:4 in flushedQueue
 * [native code]:null in flushedQueue
 * [native code]:null in invokeCallbackAndReturnFlushedQueue

 Invariant Violation: requireNativeComponent: "MapboxNavigation" was not found in the UIManager.

 This error is located at:
     in MapboxNavigation (at react-native-mapbox-navigation/index.js:6)
     in MapboxNavigation (at ManifestScreen.tsx:37)
     in RCTView (at View.js:34)
     in View (at Themed.tsx:40)
     in View (at ManifestScreen.tsx:36)
     in RCTView (at View.js:34)
     in View (at Themed.tsx:40)
     in View (at ManifestScreen.tsx:25)
     in ManifestScreen (at SceneView.tsx:122)
     in StaticContainer
     in StaticContainer (at SceneView.tsx:115)
     in EnsureSingleNavigator (at SceneView.tsx:114)
     in SceneView (at useDescriptors.tsx:153)
     in RCTView (at View.js:34)
     in View (at CardContainer.tsx:245)
     in RCTView (at View.js:34)
     in View (at CardContainer.tsx:244)
     in RCTView (at View.js:34)
     in View (at CardSheet.tsx:33)
     in ForwardRef(CardSheet) (at Card.tsx:573)
     in RCTView (at View.js:34)
     in View (at createAnimatedComponent.js:165)
     in AnimatedComponent (at createAnimatedComponent.js:215)
     in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:555)
     in PanGestureHandler (at GestureHandlerNative.tsx:13)
     in PanGestureHandler (at Card.tsx:549)
     in RCTView (at View.js:34)
     in View (at createAnimatedComponent.js:165)
     in AnimatedComponent (at createAnimatedComponent.js:215)
     in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:544)
     in RCTView (at View.js:34)
     in View (at Card.tsx:538)
     in Card (at CardContainer.tsx:206)
     in CardContainer (at CardStack.tsx:619)
     in RCTView (at View.js:34)
     in View (at Screens.tsx:84)
     in MaybeScreen (at CardStack.tsx:612)
     in RCTView (at View.js:34)
     in View (at Screens.tsx:54)
     in MaybeScreenContainer (at CardStack.tsx:494)
     in CardStack (at StackView.tsx:462)
     in KeyboardManager (at StackView.tsx:458)
     in SafeAreaProviderCompat (at StackView.tsx:455)
     in RCTView (at View.js:34)
     in View (at StackView.tsx:454)
     in StackView (at createStackNavigator.tsx:87)
     in StackNavigator (at ManifestTabNavigator.tsx:60)
     in DirectionsNavigator (at SceneView.tsx:122)
     in StaticContainer
     in StaticContainer (at SceneView.tsx:115)
     in EnsureSingleNavigator (at SceneView.tsx:114)
     in SceneView (at useDescriptors.tsx:153)
     in RCTView (at View.js:34)
     in View (at BottomTabView.tsx:55)
     in SceneContent (at BottomTabView.tsx:172)
     in RCTView (at View.js:34)
     in View (at ResourceSavingScene.tsx:58)
     in RCTView (at View.js:34)
     in View (at ResourceSavingScene.tsx:41)
     in ResourceSavingScene (at BottomTabView.tsx:166)
     in RCTView (at View.js:34)
     in View (at src/index.native.js:123)
     in ScreenContainer (at BottomTabView.tsx:146)
     in RCTView (at View.js:34)
     in View (at BottomTabView.tsx:145)
     in SafeAreaProviderCompat (at BottomTabView.tsx:144)
     in BottomTabView (at createBottomTabNavigator.tsx:45)
     in BottomTabNavigator (at ManifestTabNavigator.tsx:19)
     in ManifestTabNavigator (at SceneView.tsx:122)
     in StaticContainer
     in StaticContainer (at SceneView.tsx:115)
     in EnsureSingleNavigator (at SceneView.tsx:114)
     in SceneView (at useDescriptors.tsx:153)
     in RCTView (at View.js:34)
     in View (at CardContainer.tsx:245)
     in RCTView (at View.js:34)
     in View (at CardContainer.tsx:244)
     in RCTView (at View.js:34)
     in View (at CardSheet.tsx:33)
     in ForwardRef(CardSheet) (at Card.tsx:573)
     in RCTView (at View.js:34)
     in View (at createAnimatedComponent.js:165)
     in AnimatedComponent (at createAnimatedComponent.js:215)
     in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:555)
     in PanGestureHandler (at GestureHandlerNative.tsx:13)
     in PanGestureHandler (at Card.tsx:549)
     in RCTView (at View.js:34)
     in View (at createAnimatedComponent.js:165)
     in AnimatedComponent (at createAnimatedComponent.js:215)
     in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:544)
     in RCTView (at View.js:34)
     in View (at Card.tsx:538)
     in Card (at CardContainer.tsx:206)
     in CardContainer (at CardStack.tsx:619)
     in RCTView (at View.js:34)
     in View (at Screens.tsx:84)
     in MaybeScreen (at CardStack.tsx:612)
     in RCTView (at View.js:34)
     in View (at Screens.tsx:54)
     in MaybeScreenContainer (at CardStack.tsx:494)
     in CardStack (at StackView.tsx:462)
     in KeyboardManager (at StackView.tsx:458)
     in SafeAreaProviderCompat (at StackView.tsx:455)
     in RCTView (at View.js:34)
     in View (at StackView.tsx:454)
     in StackView (at createStackNavigator.tsx:87)
     in StackNavigator (at navigation/index.tsx:45)
     in RootNavigator (at navigation/index.tsx:29)
     in EnsureSingleNavigator (at BaseNavigationContainer.tsx:409)
     in ForwardRef(BaseNavigationContainer) (at NavigationContainer.tsx:91)
     in ThemeProvider (at NavigationContainer.tsx:90)
     in ForwardRef(NavigationContainer) (at navigation/index.tsx:26)
     in Navigation (at App.tsx:18)
     in RNCSafeAreaProvider (at SafeAreaContext.tsx:74)
     in SafeAreaProvider (at App.tsx:17)
     in App (created by ExpoRoot)
     in ExpoRoot (at renderApplication.js:45)
     in RCTView (at View.js:34)
     in View (at AppContainer.js:106)
     in DevAppContainer (at AppContainer.js:121)
     in RCTView (at View.js:34)
     in View (at AppContainer.js:132)
     in AppContainer (at renderApplication.js:39)
 - node_modules/react-native/Libraries/LogBox/LogBox.js:148:8 in registerError
 - node_modules/react-native/Libraries/LogBox/LogBox.js:59:8 in errorImpl
 - node_modules/react-native/Libraries/LogBox/LogBox.js:33:4 in console.error
 - node_modules/expo/build/environment/react-native-logs.fx.js:27:4 in error
 - node_modules/react-native/Libraries/Core/ExceptionsManager.js:104:6 in reportException
 - node_modules/react-native/Libraries/Core/ExceptionsManager.js:171:19 in handleException
 - node_modules/react-native/Libraries/Core/ReactFiberErrorDialog.js:43:2 in showErrorDialog
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:15257:32 in logCapturedError
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:15361:20 in logError
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:16597:12 in update.callback
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:7106:2 in callCallback
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:7127:20 in commitUpdateQueue
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:15801:25 in commitLifeCycles
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:18744:22 in commitLayoutEffects
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:265:4 in invokeGuardedCallbackImpl
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:476:2 in invokeGuardedCallback
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:18483:29 in commitRootImpl
 * [native code]:null in commitRootImpl
 - node_modules/scheduler/cjs/scheduler.development.js:653:23 in unstable_runWithPriority
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:18317:17 in commitRoot
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:17697:12 in performSyncWorkOnRoot
 * [native code]:null in performSyncWorkOnRoot
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:5321:31 in runWithPriority$argument_1
 - node_modules/scheduler/cjs/scheduler.development.js:653:23 in unstable_runWithPriority
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:5316:21 in flushSyncCallbackQueueImpl
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:5304:28 in flushSyncCallbackQueue
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:17718:28 in batchedUpdates$1
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2492:29 in batchedUpdates
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2638:16 in _receiveRootNodeIDEvent
 - node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:2767:27 in receiveTouches
 - node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:416:4 in __callFunction
 - node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:109:6 in __guard$argument_0
 - node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:364:10 in __guard
 - node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:108:4 in callFunctionReturnFlushedQueue
 * [native code]:null in callFunctionReturnFlushedQueue

This is code for the file where I am trying to use the mapbox package:

 import * as React from 'react';

 import { Text, View } from '../components/Themed';
 import styles from '../components/styles';
 import {Ionicons} from '@expo/vector-icons';
 import {Image} from 'react-native';

 import MapboxNavigation from '@homee/react-native-mapbox-navigation';

 export default function ManifestScreen() {
   return (
     <View style={styles.padlessContainer}>
         <MapboxNavigation
           origin={[-97.760288, 30.273566]}
           destination={[-97.918842, 30.494466]}
           shouldSimulateRoute={true}
           onLocationChange={(event: any) => {
             const { latitude, longitude } = event.nativeEvent;
           }}
           onRouteProgressChange={(event: any) => {
             const {
               distanceTraveled,
               durationRemaining,
               fractionTraveled,
               distanceRemaining,
             } = event.nativeEvent;
           }}
           onError={(event: any) => {
             const { message } = event.nativeEvent;
           }}
           onCancelNavigation={() => {
             // User tapped the "X" cancel button in the nav UI
             // or canceled via the OS system tray on android.
             // Do whatever you need to here.
           }}
           onArrive={() => {
             // Called when you arrive at the destination.
           }}
         />
     </View>
   );
 }

I checked and made sure I had the correct native extensions installed in my /ios/pods directory:

I also made sure I had all the needed packages installed in the node_modules:

I also seen this issue, which seemed similar so I tried to autolink the missing package that was listed in the simulator errors:
https://stackoverflow.com/questions/60034686/react-native-rncsafeareaview-was-not-found-in-the-uimanager#answer-61329389
That didn't help either, I've been trouble shooting for 3-4 days trying to get this resolved, any help would be greatly appreciated!!!

@rossmartin Working on retrying with a completely clean install and only barebones code. Do you know are there any specific caveats to using your package with expo?

I've never used expo but I'm pretty sure most native modules will not work with it (including this one). It appears that "ejecting" might provide a way - https://docs.expo.io/expokit/eject/

Is there a way to pay for a few hours of direct support?
On Wed, Mar 3, 2021 at 6:42 PM Ross Martin<EMAIL_ADDRESS>wrote:

I've never used expo but I'm pretty sure most native modules will not work
with it (including this one). It appears that "ejecting" might provide a
way - https://docs.expo.io/expokit/eject/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/homeeondemand/react-native-mapbox-navigation/issues/16#issuecomment-790154818,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMP5CNQV7K32ZVHEZSQUH3TB3CP5ANCNFSM4YLKAT2A
.

--
Thomas Bird - Full Stack Developer
Perrysburg, OH
P:<PHONE_NUMBER>
E<EMAIL_ADDRESS><EMAIL_ADDRESS>Thomas.Bird5
W. http://ThomasKBird.com http://thomaskbird.com/

www.linkedin.com/in/thomasbird1/

@rossmartin I started the project with expo, but I saw the docs on ejecting and then auto-linking and tried that. I'm sure its a configuration issue. Is there a way to pay for a few hours of direct support like phone call support or webex?

Hey sorry I have been very busy after moving into a new house and with my day job. How far along are you in this expo project? I recommend creating a vanilla react native project and porting over any existing work. I apologize that I don't have time to help directly with this right now. This is my recommendation until I can see what it will take to get an expo project running with this (I have my doubts that it will though).

@rossmartin hey no worries I appreciate that, I’m kind of in the same boat just moved to. That’s what I did, I started from scratch a vanilla react native project left out everything except trying to get this package plugged in and working by itself and then I intended to add the other screens from my other app back into this vanilla project. I’m not getting this same error but now I’m getting other errors still relating to the same type of thing, mostly using native functionality.

try
npx react-native link @homee/react-native-mapbox-navigation
or
react-native link @homee/react-native-mapbox-navigation

Thanks @AKACC I will try that here shortly!

Thanks for opening this issue. I’m running into the same issue and was wondering if you were able to get past it? I’ve tried linking, ejecting, and modifying the Podfile as suggested but am still facing the error. Working within this repo and importing into the NavRoute component https://github.com/mpeglerg/NiteLite/blob/StartRoute/src/components/NavRoute.js

@mpeglerg I'm sorry I never figured it out we ended up hiring another developer who is handling and got past it. I would strongly suggest not using expo if you are, my guy said he never experienced this so I'm not sure what happened. Plus he started from scratch


Remove dist folder from version control

Small discussion here
https://github.com/rollup/rollup-starter-lib/issues/8

@avdeev what about installing package from github? Without this folder, the library will not work

@karambafe Yep, i asked about it in the linked discussion :)
Github (GIT) is the source store.
To distribute the code it's recommended to use NPM registry, CDNs (https://unpkg.com/match-media-breakpoint), etc.

ok, I deleted the folder dist in version 1.1.0


Add <HtmlPanel> component

This PR adds the <HtmlPanel> component.
I've also updated the example app to include an HTML panel so you can see it in action.

Hello there ! Thank you so much for your Pull Request, I'll move to your fork as I definitely need it :) Might be nice to merge it at some point

@eteeselink Arf actually I cannot manage to use this branch directly, no types etc... Could you release it on a canary version or whatsoever ? It would be of great help :)

The experimental <HtmlPanel> component is now available by installing the @talkjs/react library with the next tag:
npm install @talkjs/react@next


Move Purchase Button to Main Home Screen

The ticket purchase button is currently isolated within the exhibit page, which creates additional navigation steps for users and complicates the user journey.
Describe the solution you’d like
Move the ticket purchase button to the main home screen, integrating it directly into the main page for better visibility and smoother user flow.

proceeded with this but ran into a conflict between the wallet component as well as the main page being a client and not a server page so what I've done instead is consolidate the countdown and purchase screen


Clean up dead code

Clean up dead code

Everything looks good.
I assume we should unblock fields in "Currencies":

Since simple mistake well make as to Disable the currencies and make it dead wait but to update it and make it work. Also you will not be able to add "Wallet" if the "Currency id" id to long.

@pkucherenk0 you mean to disable these fields? @ysv what are your thought on this?
Also for long curreny_id issue, it's related to this https://github.com/rubykube/peatio/issues/1499

I want to be able to change the values in this fields.
The withdraw is in the forever conformation. I have reached block difference in 240+ block and my withdraw are not confirmed, required only 6 blocks.

@NQA1 This issue relates to https://github.com/rubykube/peatio/issues/1499


Does it support html tables?

It seems that i cant make it work with HTML tables (as i cant just a div outside tr). Could anyone suggest any solutions for it?

this is the same problem i just ran into ... not what i was expecting

this is the same problem i just ran into ... not what i was expecting

You can use the render function to determine what Draggable and or Container get rendered as. In this case if you were to have draggable table body rows
<Container
   render={(ref) => (

       <Draggable
         render={() => (

some data

         )}
       />

   )}
</Container>

Might contain types

Also dont forget when rendering  explicity through draggable change its display type to display: table-row as this will mess up your table UI as draggable overwrites it to display: block .
Dont forget to pass ref to the tbody and change display of
<Container    render={(ref) => (
        <Draggable          render={() => (
some data
          )}        />
    )} </Container>


Smith number | Python

Smith number -
what will change - This program finds out whether a number is smith or not.
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] Python

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

Can I work on this please?


Thanks to hanya for this patch

Originally posted by @Ghoai171 in https://github.com/libgdx/libgdx/issues/6948

Originally posted by @Ghoai171 in https://github.com/libgdx/libgdx/issues/6948


APK for download

Hi Emma, I was approached to please include your app with the IzzyOnDroid repo, so I came here to check. Unfortunately, you do not (yet) tag your releases and do not provide the APK there, so I cannot even check if it meets the IzzyOnDroid App Inclusion Policy.
I gladly give it a look and help out there, which also should meet your wish to get word out, as the mentioned repo has some popularity meanwhile. So if you agree, I'd guide you through the steps there and, if possible, get your app listed – at the IzzyOnDroid repo, and if you want to fulfill the "literal wish" as well, also give hints to apply at F-Droid.org itself.
Looking forward to your reply!

Hi, I will fix this next time I do a release for Google Play, which hopefully will be in a few weeks. I will ping you when it's done.

Wonderful, thanks! Looking forward to that :star_struck:

Downloading an APK (Android Package Kit) file can be a convenient way to access apps that might not be available through the official Google Play Store. APK files sportzfy latest version allow you to install apps directly on your Android device, often providing early access to new features or updates. However, it's important to exercise caution when downloading APK files.

@IzzySoft
Version 1.8.0 is now released and APK is available!

@IzzySoft I'll take a look at this tomorrow. I know my code inside and out, we do not use Google maps and I'm pretty sure we don't use Firebase either. Must be some sort of reference somewhere in that case. And all the data is stored on the device and nothing is sent anywhere.
We who are working on the app are new to android development so ofc we can make mistakes. But I'll get back to you when I have looked at this!

You're depending on com.google.android.libraries.places. Maybe that was unintended?

@obfusk Thanks for helping out! Im not sure why/when places was added as a lib but it was most definitely unintended. It was never used in the code...
@IzzySoft I cleaned the project and rebuild an APK and I cannot see these dependencies anymore. I don't understand where/why places was in there because I have never played around with any form of location data, not in any app... Firebase I think might have been left in there when I built the notification-stuff but I specifically wanted to avoid using it, I suspect the dependency didn't go away...
I do not take offense, I take this as a learning opportunity! So thank you for pointing this out. New APK will be uploaded now and new release too.

Thanks Emma! Probably "dependency hell", and Firebase was dragged in by e.g. Maps which was dragged in by Places or something (I didn't check the dependency tree, so please do not take this literally – but such "cascades" can be seen sometimes).
Confirming the new APK looking fine! :partying_face: Integrating it now at IzzyOnDroid… And Congrats, it's even a Reproducible Build :partying_face: (see e.g. Reproducible Builds, special client support and more in our repo for some background on this). So here's a preview from our staging area:

Your app should show up here with the next sync around 6 pm UTC. Be welcome to pick a badge to link there e.g. from your Readme. And if you wish, I can send you a PR with the metadata (app description, graphics) in Fastlane format, so you'd be in control how your app is presented (you can use the IzzyOnDroid Fastlane Documentation for guidance there; Fastlane would then be pulled along with each new release – and no binaries needed, just the metadata files). Just let me know and I send in the PR.
But now: Welcome aboard IzzyOnDroid! :partying_face: – and thanks a lot for your efforts! Will now notify the person who approached me with this wish, she will be very happy! :hugs:

I see you've opened an RFP with F-Droid – and the bot said you're missing … Fastlane :stuck_out_tongue_winking_eye: My above offer still stands, @EmmaTellblom :wink:

@IzzySoft Lol, I was so happy about being approved for IzzyOnDroid that I kind of skipped the last of your message. Sorry, I'll do better! And the funny part is that at the same time you wrote here I actually did include a fastlane because it wasn't so messy as I first thought it would be.

Thanks for helping out!

The IzzyOnDroid team is always happy to help :)

I actually did include a fastlane

Now, then let's turn my offer the other way round, and I update the YAML for Mensinator here to use it instead: with the next release, it will pull your Fastlane along :smiley: I'm pretty curious how your full description will render. IoD will convert it from Markdown to HTML, then replace all headings (h1…h6) with bold paragraphs (h1-h3 should also be made a little bigger) to not destroy page structure, sanitize it, and then import the result. Please take a look once the next release is out and let me know if you like it – or if we need…
…corrections. Which we will – not for IoD, but for F-Droid, which does not understand Markdown. So while above described results will look fine at IoD, F-Droid will simply replace each newline with a
, and ship it as such. You probably won't like that.
Two solutions for that, both described in the IzzyOnDroid Fastlane Documentation:

use fully-fledged HTML and "compress" it so it's all on one line (so nowhere to replace newlines)
use what the documentation describes as "Markdown Lite" – which renders fine at IoD, F-Droid and even Play.

@IzzySoft I did change to HTML now, but you say it needs to be all in one-line? That seems weird... Can you please look and see if current file is good enough for Fdroid? I really appreciate you helping out!

but you say it needs to be all in one-line?

It does not NEED to. For F-Droid, not having it in a single line means they replace each and every newline by
, which will simply look… err… not that well. At IzzyOnDroid that's taken care for when Fastlane is being pulled, we have extra configuration for that (as we have to configure the "entry point"). Here's what is set up for Mensinator currently:
  Fastlane: https://github.com/EmmaTellblom/Mensinator/blob/main/fastlane/metadata/android
  FastlaneFeatures: title,shortdesc,fulldescMD,icon,screenshots

First line is where the entry-point for your fastlane tree is to be found. Second line is what features are enabled and in which variant. You see e.g. fulldescMD there; that means "take the full_description.txt, then run it through the Markdown parser, then do the HTML sanitizing". That works with "full HTML" as well – but I could change it to fulldesc now to skip the Markdown part (which won't interfere as it allows for HTML, it's just not needed anymore if you have "full HTML") – but I guess I'll leave it in nevertheless so nothing breaks should you one day switch back). Sanitizing HTML also includes "compressing" it to a single line, so the fdroidserver software finds no newlines to replace.

Can you please look and see if current file is good enough for Fdroid?

(Looking) at the current HEAD here it's still Markdown. At F-Droid you'd see an additional empty line below your "headings" (
 and
) as those are block-level elements and thus already imply a line break themselves. All else would be handled as "plain text". I'm curious how the framework at IzzyOnDroid handles it: it uses "standard markdown" (so no flavors) and thus usually expects an empty line before and after bullet-point lists – except when they directly follow a "heading", so it should be fine. Btw, the sanitizer here will replace your
 and
 by something equivalent to
, so they don't break the structures of where the description is shown INLINED. h4-h6 would just be "bold" without increasing font size.
While here: your last release is RB again, but only after manual adjustment: you've built the APK before you committed your changes. Please always build the release APKs on a clean tree after all code is committed.
And speaking about builds: could you also include the gradle wrapper JAR next to the gradle/wrapper/gradle-wrapper.properties? Currently, the recipe for the verification builder(s) has to inject the gradle-bin indicated by the properties, but parsing that is not always safe. Better you have that set up fully here, then we can rely on your setup. Thanks in advance!

@IzzySoft Thank you so much! I have included the gradle wrapper JAR and have tried to follow your other recommendations too!

Thanks a lot, Emma! Will adjust the recipe at the verification builder with the next update then :star_struck:

@EmmaTellblom you forgot to attach the APK to the latest release. And @obfusk just tells me you seen to have used an older wrapper than gradle version. She says you might wish to take a look at https://github.com/marketplace/actions/gradle-version-wrapper-update

@IzzySoft Crap you are right.... I need to start making a checklist soon, lol. I will check out the github action tomorrow! I have corrected the new version at least.

Thanks! As we use to say: SHIFT happens (eh, sorry, just got my new SHIFTsound BNO and am excited about the sound quality – and "SHIFT happens" is their slogan. A really nice (family-) company with exciting products, I'm much convinced and highly recommend them. Also using 2 of their phones meanwhile)… oops, apologies for the fill-in :see_no_evil:
Yeah, we'll see then. Just attach the APK for the current version (Fay says the wrapper should still work, despite of not being the most recent). And the next release then will have it all completed. Thanks a lot for all your hard work there, Emma! :heart_eyes:

Oops, APK was already attached meanwhile… So the updater probably caught it. Hurry, Izzy! (bit action behind the scenes) OK, adjusted the commit again :see_no_evil: OK, it's RB :sweat_smile: (pushing the logs) and the green shield should be up again :smiley:

@EmmaTellblom please always build the app from a clean tree at the commit your tag points to. I had quite a bit to juggle getting your current release reproducible:
git checkout 7261bfb415937c99e113de949c5351837ce1afd6     # that is where your last changes ended up
git reset --soft 12579b4a4c35b8a72f47f9ab4324cf96c9daa7c5 # the embedded commit hash

Maybe I should simply have used sed to apply your changes :see_no_evil: However, this means the next release will need manual adjustments as well (removing those two lines again)…

@IzzySoft So sorry for the inconvenience, I really should create a checklist as I said I would in August... I will try and see if I can improve my releases so you do t have to fix them in the future!

Thanks Emma! And no worries, this was a rather easy one (you can bet I get "uglier ones" every week, which I cannot fix myself – like "commit – change something – build APK – change something else – commit, tag"; have fun if that were several lines in some code and not just the versionCode in the build.gradle :see_no_evil:). So I rather mentioned it as a reminder, before… well, no, not giving bad ideas here :rofl:


Update to add asset tag to source.extension.manifest

Update to add asset tag to source.extension.manifest

added


[SPARK-41954][CORE] Add isDecommissioned in ExecutorDeadException

What changes were proposed in this pull request?
When one executor is dead, we want to know whether this dead executor is caused by decommission.
Why are the changes needed?
When one executor is dead, we want to know whether this dead executor is caused by decommission.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added UT
Was this patch authored or co-authored using generative AI tooling?
No

@dongjoon-hyun @mridulm Help take a look?

Will let @dongjoon-hyun review this as he has more context.
One comment though, there is only addition to decommissionedExecutorIdSet, no removal - and so essentially will be a memory leak for long running apps.


Testing results are not as expected

@Xiefan-Guo Hey. Thanks for releasing the codebase.
I tested your pretrained model on celeba, however, the results are not as expected. Even the identity of the person belongs to the training set, still it does not generalize well. What could be the reason?

Hi, maybe it is caused by the preprocessing of the image. We follow the experimental settings of EdgeConnect. For CelebA, we cropped the center 178x178 of the images, then resized them to 256x256 using bilinear interpolation.

Hi, maybe it is caused by the preprocessing of the image. We follow the experimental settings of EdgeConnect. For CelebA, we cropped the center 178x178 of the images, then resized them to 256x256 using bilinear interpolation.
How to solve this problem please？

@SURABHI-GUPTA Hello, I also have this confusion, when I test on PSV and Places2, the result are not good, How can I solve it? could you help me?

H

Hi, maybe it is caused by the preprocessing of the image. We follow the experimental settings of EdgeConnect. For CelebA, we cropped the center 178x178 of the images, then resized them to 256x256 using bilinear interpolation.
How to solve this problem please？

Have you solve this problem?


Add video services to whitelist

Hello,
First of all, I want to thank you for this amazing service, which I recently discovered... It is a great pleasure to work with it ! I recently encountered a few problems with a project of mine, which makes some very light use of Youtube (occasional metadata downloading). Since this website is :

Completely free service
Used by a lot of people
Easily handle million hits

...I hereby suggest to add it to the Firewall whitelist. Please forgive me if this request seems dumb to you... I'm no professional, and I probably don't understand every implication of such a modification ! Especially I don't know if this modification would be compatible with the ToS preventing any Streaming usage of your servers.

Hi,
Thank you for the PR, but I think you've misunderstood the purpose of the whitelist.
The firewall whitelist is opt-in. By default, it won't be activated and can be turned off at will. I should clearly mention that in the docs: https://domcloud.co/docs/features/firewall#outbound-connection
Also, just adding youtube.com might not work. You have to list all possible subdomains to be used with YouTube API. This is because the firewall (iptables) blocks things by IP addresses, not a domain name.
You can host your web apps here without doing this PR.

Thank you for your answer ! I liked the idea of having a very restrictive firewall, which gave me some peace of mind regarding security... But I will follow your advice, thank you !


PHP 7.1 RC5

Release Candidate 5 is set to be public on the 27th. We have not yet updated to RC4, and I feel it would be pointless to update to it to be out of date in 36 hours.
This issue is for tracking purposes and I am working on a PR right now

This issue is for tracking purposes and I am working on a PR right now

Please do these on the homebrew/php repo instead.

@MikeMcQuaid I had just noticed that moved it over 👍


Discussion: What would be in an AnonCreds "presentation request" OCA Bundle consist?

We talked about what would be in an AnonCreds "presentation request" OCA Bundle such that the presentation request UX can be improved -- particularly in the areas of:

Multilingual support
An overall name/purpose for the presentation request
A summary of the purpose/justification for the presentation request
A label/information for the requested attributes, especially for predicates

This issue is written in the form of a spec (as if decisions have been made), but all aspects are open to discussion.
Context
A holder will receive a presentation request from a verifier.  Before any UI is presented to the user, the holder's wallet will look into the holder storage to find the credentials that could be used to satisfy the presentation request. Once that is done, the possible response to the presentation request is put on the screen for the user.  At that point the state of the flow could be:

The Holder has exactly one set of credentials that satisfy the all parts of the presentation request.
The Holder does not have a set of credentials that satisfy all parts of the presentation request.
The Holder has more than one credential that satisfies some or all of the parts of the presentation request.

Further, for each credential that the Holder has, assume that they also have access to the OCA Bundle associated with that credential. As such, the Holder will already have access to a lot of OCA for Aries Bundles and the data therein.  Of course, where there is no credential, or where there is no OCA Bundle, the holder would not have any extra information, other than perhaps the OCA Bundle from the presentation request.
OCA Presentation Request Data
We propose that the following OCA Overlays be included in the OCA Bundle for Presentation Requests.  To help in understanding these, please see this set of Presentation Request templates that are currently in the BC Wallet.

The ID of the presentation request should be used to find the associated OCA Bundle for the presentation request.
Capture Base:

The list of all attributes in "name" and "names", plus the list of the attribute needed for each attribute.

The same attribute may be requested in multiple name/names entries.
For now, we will ignore that possibility, but keep in mind that we may need to differentiate the attribute names by where they appear in the presentation request.

The list of predicates in the form "predicate."

This is the item that will NEVER be in the source credential OCA Bundles so it is very important.
Like the attributes, the same attribute name could be used in multiple predicates, so we might need to do something about that.

As with all Capture Bases, the list of PII elements should be tracked.

Meta Overlay (multilingual):

Name of Presentation Request
Description of Presentation Request
Justification for Request -- text about why the verifier is asking for the presentation request

Label Overlay
Information Overlay

There is no need for the other overlays that are used in OCA for Aries credentials because

They are needed only when the holder has credentials (with data) to satisfy the request, and at that time, the holder will have the OCA Bundles for the credentials.

The verifier may not be certain which credentials the holder will use to satisfy the request, so cannot know the data types anyway.

For predicates, the data is always either a True or False.

The branding is not needed, as the branding from the source credentials will be used.

This is the current suggestion, but should be considered further as we test using these OCA Bundles.

On Screen Display
The wallet will display for the user:

The name and possibly the description of the presentation request from the user, perhaps also with the Justification for request text inline or available via a popup.
For predicates, the label (and optional information popup) from the Presentation Request OCA Bundle
For any attributes that for which the holder does not have a credential, the Label (and optional information popup) from the Presentation Request bundle.
For all other attributes, the Label (and optional information popup) from the source credential to be used in satisfying the request.
For all attributes, a flag/indicator that the data element is sharing PII data, coming from OCA Presentation or OCA Source credential bundles.

@amanji -- does this look right from our discussion?  Please share with others that are interested.


Change Azure RKE size to Standard_D2_v2

Rancher versions: 2.1 rc9
Steps to Reproduce:

Go to Node Template
Add Template
Select Azure

Results:  Under Instance the size is Standard_A2.  Recommended for AKS is Standard_D2_v2 and that was changed from UI.  But the RKE template should stay consistent with that size and that has to be done in the API.

We changed this in our direct AKS integration, but not for the node template. Related: https://github.com/rancher/rancher/issues/15864

Scope is too big to get into v2.1. This is driven by the defaults in the docker-machine azure driver, which still has the default as A2

Seems the related issue is fixed. @tfiduccia can you re-test?

This is not fixed.  Size still says Standard_A2.  It was only fixed in AKS and not in the node template.

Propose moving out of 2.2.x and into 2.3

I merged the docker machine change, but need to release it

@alena1108 since you did a machine release for another fix, this will get pulled into the rc when you merge the update to rancher/rancher for the new machine version

Oh, i guess you didnt do the release, logan just opened PRs in anticipation of the machine release

waiting for machine to get release and pulled into rancher

Tested with master build from June 6th
Navigate to Add Azure Node template
The template shows  default size as Standard_D2_v2as expected.
After the template is created, the API shows the correct size
"privateIpAddress": "",
"resourceGroup": "docker-machine",
"size": "Standard_D2_v2",
"sshUser": "docker-user",
"staticPublicIp": false,
"storageType": "Standard_LRS",
"subnet": "docker-machine",

Created a cluster successfully using the above Azure node template and the cluster was functional


python310Packages.packageurl-python: 0.10.1 -> 0.10.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.packageurl-python is: "Python parser and builder for package URLs"
meta.homepage for python310Packages.packageurl-python is: "https://github.com/package-url/packageurl-python"
meta.changelog for python310Packages.packageurl-python is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.10.3 with grep in /nix/store/d3h574vxzgvhn6n75dkm1s7fw93fdmq5-python3.10-packageurl-python-0.10.3
found 0.10.3 in filename of file in /nix/store/d3h574vxzgvhn6n75dkm1s7fw93fdmq5-python3.10-packageurl-python-0.10.3

Rebuild report (if merged into master) (click to expand)

14 total rebuild path(s)

14 package rebuild(s)

First fifty rebuilds by attrpath
appthreat-depscan
checkov
cyclonedx-python
pip-audit
python310Packages.appthreat-vulnerability-db
python310Packages.cyclonedx-python-lib
python310Packages.packageurl-python
python310Packages.scancode-toolkit
python310Packages.tern
python39Packages.appthreat-vulnerability-db
python39Packages.cyclonedx-python-lib
python39Packages.packageurl-python
python39Packages.scancode-toolkit
python39Packages.tern

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d3h574vxzgvhn6n75dkm1s7fw93fdmq5-python3.10-packageurl-python-0.10.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.packageurl-python https://github.com/r-ryantm/nixpkgs/archive/9fc7dcea4f8cb85c75460588ca048b0e34f64ee6.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d3h574vxzgvhn6n75dkm1s7fw93fdmq5-python3.10-packageurl-python-0.10.3
ls -la /nix/store/d3h574vxzgvhn6n75dkm1s7fw93fdmq5-python3.10-packageurl-python-0.10.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

checkov

13 packages built:

appthreat-depscan
cyclonedx-python
pip-audit
python310Packages.appthreat-vulnerability-db
python310Packages.cyclonedx-python-lib
python310Packages.packageurl-python
python310Packages.scancode-toolkit
python310Packages.tern
python39Packages.appthreat-vulnerability-db
python39Packages.cyclonedx-python-lib
python39Packages.packageurl-python
python39Packages.scancode-toolkit
python39Packages.tern

Maintainer pings
cc @armijnhemel for testing.

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

1 package failed to build:

checkov

13 packages built:

appthreat-depscan
cyclonedx-python
pip-audit
python310Packages.appthreat-vulnerability-db
python310Packages.cyclonedx-python-lib
python310Packages.packageurl-python
python310Packages.scancode-toolkit
python310Packages.tern
python39Packages.appthreat-vulnerability-db
python39Packages.cyclonedx-python-lib
python39Packages.packageurl-python
python39Packages.scancode-toolkit
python39Packages.tern


ENH: prepare for transition to ITK 5

Use the latest release from 4.x branch (4.13.1+)
and disable legacy functionality.

Cc: @juanprietob

Thanks for integrating :+1:


/v2/_catalog throw 405 error (v2.2.0) ?

I try to debug why docker-registry get a 405 error after "/v2/_catalog". But I didn't find the reason:
core # curl -I http://<IP_ADDRESS>:5000/v2/
HTTP/1.1 200 OK
Content-Length: 2
Content-Type: application/json; charset=utf-8
Docker-Distribution-Api-Version: registry/2.0
X-Content-Type-Options: nosniff

core # curl -I http://<IP_ADDRESS>:5000/v2/_catalog
HTTP/1.1 405 Method Not Allowed
Allow: GET
Content-Type: text/plain; charset=utf-8
Docker-Distribution-Api-Version: registry/2.0
X-Content-Type-Options: nosniff
Content-Length: 19

log:
Nov 21 10:34:58 server docker[845]: time="2015-11-21T10:34:58.59033859Z" level=debug msg="authorizing request" go.version=go1.4.3 http.request.host="<IP_ADDRESS>:5000" http.request.id=c9d4abf2-8ee2-4e32-a4b2-7f3f23418a0e http.request.method=HEAD http.request.remoteaddr="<IP_ADDRESS>:45304" http.request.uri="/v2/_catalog" http.request.useragent="curl/7.42.1" instance.id=33ffd4a9-1bde-4bf2-a6d4-1ad7466d6241 service=registry version=v2.2.0
Nov 21 10:34:58 server docker[845]: <IP_ADDRESS> - - [21/Nov/2015:10:34:58 +0000] "HEAD /v2/_catalog HTTP/1.1" 405 19 "" "curl/7.42.1"

I run the registry as follow:
/usr/bin/docker run --rm --net host --privileged --name docker-registry \
          -v /data/registry:/var/lib/registry \
          -e REGISTRY_LOG_LEVEL=debug \
          -e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io \
          registry:2.2.0

> docker version
Client:
 Version:      1.8.3
 API version:  1.20
 Go version:   go1.4.3
 Git commit:   cedd534-dirty
 Built:        Thu Nov 19 23:12:57 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.3
 API version:  1.20
 Go version:   go1.4.3
 Git commit:   cedd534-dirty
 Built:        Thu Nov 19 23:12:57 UTC 2015
 OS/Arch:      linux/amd64

I don't find any help here: https://docs.docker.com/registry/spec/api/#get-catalog

I had the same error until I tried with -X GET instead of HEAD (-I).
(docker 1.9.1 and registry 2.2)

@remoe Which auth system are you using? From the error message, it looks like this is happening in the auth phase. There are specific privileges that are required to hit the catalog API.

@stevvooe I used the defaults of 2.2. But I haven't checked what these are.

I added SSL and this:
          -e REGISTRY_AUTH_SILLY_REALM=silly-realm \
          -e REGISTRY_AUTH_SILLY_SERVICE=silly-service \

But SSL is optional, right?
and then:
curl --header "Authorization: true" https://<IP_ADDRESS>:5000/v2/_catalog
{"repositories":["library/busybox","ubuntu"]}
curl --header "Authorization: true" https://<IP_ADDRESS>:5000/v2/
{}

It works :) @stevvooe thanks for this hint.

@remoe Silly auth isn't meant for real use. Now that I've read @RRAlex's hint, that is probably the real issue.

I added this, and it worked for me.
echo 'export KUBECONFIG=$HOME/admin.conf' >>$HOME/.bashrc


tzdata: 2020f -> 2021a; python3Packages.backports-zoneinfo: enable tests

Motivation for this change
Update tzdata to newest release.
Enable tests in python3Packages.backports-zoneinfo package by setting PYTHONTPATH and including python3Packages.tzdata (https://zoneinfo.readthedocs.io/en/latest/zoneinfo.html#envvar-PYTHONTZPATH)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

Near pkgs/data/misc/tzdata/default.nix:67:3:
   |
67 |   meta = with lib; {
   |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

If you feel like fixing the missing license attribute, noted by the bot, apparently this is public domain, with parts of the code under bsd 3: https://github.com/eggert/tz/blob/main/LICENSE

The python change is a net benefit, nothing to worry about. Added the two licenses with a comment that clarifies their application.


Tracking issues of storage backend integration tests

[x] aws s3: tested by minio now. We can add real s3 bucket in with sponsor.
[ ] aliyun oss: need an oss bucket (better to locate near us-east-1)
[ ] azure adlsv2: can be tested by Azurite. And I'm willing to provide test infra as Microsoft MVP.
[ ] gcp gcs: need a gcs bucket (better to locate near us-east-1)
[ ] hadoop hdfs: can setup in CI directly (thanks open source!)

I agree that we can label these features as experimental. Setting up the CI infrastructure requires time, more so than implementing those features.
Originally posted by @Xuanwo in https://github.com/apache/iceberg-rust/issues/408#issuecomment-2178730480

@Xuanwo I can take a shot at GCP GCS if nobody else is working on that at the moment 👍

How do you plan to do it? Is there any open source containers that could mock gcs?

@liurenjie1024
There is this mock which I found earlier: https://github.com/fsouza/fake-gcs-server
Failing this, my plan was to use an actual GCS bucket for testing the functionality - given this was mentioned at being potentially experimental for now. Granted, this isn't ideal for CI, but the mock from above looks relatively well-used at first glance 👍


CRC VM and Openshift Cluster can't been started automatically after Virtual Machine reboot

General information

OS: Linux
Hypervisor: KVM
Did you run crc setup before starting it (Yes/No): Yes
Running CRC on: VM

CRC version
# Put `crc version` output here
CRC version: 2.24.1+81aeeb
OpenShift version: 4.13.6
Podman version: 4.4.4

CRC status
# Put `crc status --log-level debug` output here
DEBU CRC version: 2.24.1+81aeeb
DEBU OpenShift version: 4.13.6
DEBU Podman version: 4.4.4
DEBU Running 'crc status'
CRC VM:          Stopped
OpenShift:       Stopped (v4.13.6)
RAM Usage:       0B of 0B
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     20.84GB

CRC config
# Put `crc config view` output here
[ryanlyy@localhost ~]$ crc config view
- consent-telemetry                     : no
- http-proxy                            : http://ip:port/
- https-proxy                           : http://ip:port/
- no-proxy                              : <IP_ADDRESS>,<IP_ADDRESS>/22,<IP_ADDRESS>/23,<IP_ADDRESS>/24,<IP_ADDRESS>/8,<IP_ADDRESS>/24,<IP_ADDRESS>/32,localhost,
- pull-secret-file                      : /home/ryanlyy/osl/pull-secret.txt
[ryanlyy@localhost ~]$

Host Operating System
Rocky Linux 9

Steps to reproduce

Install CRC in Linux VM
shutdown VM
start VM
CRC VM/Openshift: Stopped

Expected
CRC VM/Openshift can be started automatically after start VM
Actual
CRC VM/Openshfit is in Stopped status

If you mean that the cluster does not automagically start when the VM is restarted? This is by design, as we have to prepare the cluster environment before it gets started.
If this is an existing VM, you could suffice by logging in and starting the appropriate systemd service.