NSInternalInconsistencyException: bundleURL must be non-nil when not implementing loadSourceForBridge

I am using react-native 0.31.0-rc.1. I am observing the error in iOS on Mac.
I recently update react-native on my app to the latest and started to get this error (detailed error below). This only happens when I try to run the app on the phone by using Option 2 which is to load using a static bundle. I have tried:

Clean and rebuild in Xcode
Reset cache and run react packager
Uninstall the app on the phone
Coming from Windows background, I have also tried to reboot my machine

Error in Xcode
2016-08-04 09:34:37.611 GalarmApp[367:165469] *** Assertion failure in
-[RCTBatchedBridge loadSource:](), /Users/abc/Projects/GalarmApp/node_modules/react-native/React/Base/RCTBatchedBridge.m:180 2016-08-04 09:34:37.613 GalarmApp[367:165469] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'bundleURL must be non-nil when not implementing loadSourceForBridge'
*** First throw call stack: (0x182b32db0 0x182197f80 0x182b32c80 0x1834b81c0 0x1000af788 0x1000adefc 0x1000adca4 0x1000e73d8 0x1000e7368 0x1000e6700 0x1000e643c 0x10005a254 0x10003cebc 0x10003c214 0x10003966c 0x100039b18 0x187d069c0 0x187f36184 0x187f3a5f0 0x187f37764 0x1844d37ac 0x1844d3618 0x1844d39c8 0x182ae909c 0x182ae8b30 0x182ae6830 0x182a10c50 0x187cff94c 0x187cfa088 0x10003bee0 0x1825ae8b8) libc++abi.dylib: terminating with uncaught exception of type NSException (lldb)

I can see that this problem is printed here in the code but I am a beginner at best in native iOS development and don't know how to fix this problem.
Please help me in fixing this problem. Thanks!
Code in AppDelegate.swift file
/**
 * Loading JavaScript code - uncomment the one you want.
 *
 * OPTION 1
 * Load from development server. Start the server from the repository root:
 *
 * $ npm start
 *
 * To run on device, change `localhost` to the IP address of your computer
 * (you can get this by typing `ifconfig` into the terminal and selecting the
 * `inet` value under `en0:`) and make sure your computer and iOS device are
 * on the same Wi-Fi network.
 */
// let jsCodeLocation = NSURL(string: "http://localhost:8081/index.ios.bundle?platform=ios&dev=true")

 /**
 * OPTION 2
 * Load from pre-bundled file on disk. The static bundle is automatically
 * generated by "Bundle React Native code and images" build step.
 */
let jsCodeLocation = NSBundle.mainBundle().URLForResource("main", withExtension: "jsbundle")

print (jsCodeLocation)

let rootView = RCTRootView(bundleURL:jsCodeLocation, moduleName: "galarm", initialProperties: nil, launchOptions:launchOptions)

As you can see, I have commented out Option 1 and uncommented out 'Option 2. The jsCodeLocation is printed as nil. I have run the same app this way on the device like 100 times when I was usingreact-native 0.24.0`. I have not made any changes to the code and I started to see this error after the upgrade.
I have also asked this question on stackoverflow but since I was not getting any responses, I thought I will raise an issue here as well

I have the same problem ~

Please refer to the accepted answer for this question on stackoverflow. Looks like the IP detection for the ios bundle has been automated due to which the two options were removed and there is just one now.

@varungupta85 Thank you,I have resolved the problem follow your advice.
This url:
http://stackoverflow.com/questions/38780325/running-react-native-app-on-ios-device-using-offline-bundle

If you change to a release scheme while building your app, that will compile your app with the offline bundle.
Product > Scheme > Edit Scheme > set build configuration to Release

I sometimes get this error when using the development bundle (served by the packager).
Restarting the packager fixes it.

I solved by turning off WiFi in my mac and turning it on. Same on the iPhone.

just using
jsCodeLocation = [NSURL URLWithString:@"http://localhost:8081/index.ios.bundle?platform=ios&dev=true"]; to instead of jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
this solved my problem.

None of these solutions worked for me.
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  NSURL *jsCodeLocation;

  // Comment-out, cannot get past error: bundleURL must be non-nil when not implementing loadSourceForBridge
  //jsCodeLocation = [[RCTBundleURLProvider sharedSettings]<EMAIL_ADDRESS>fallbackResource:nil];

#if DEBUG
  NSLog(@"AppDelegate:DEBUG");

#if TARGET_IPHONE_SIMULATOR
  NSLog(@"AppDelegate:DEBUG:TARGET_IPHONE_SIMULATOR");
  jsCodeLocation = [NSURL URLWithString:@"http://localhost:8081/index.ios.bundle"];
#else
  NSLog(@"AppDelegate:DEBUG:!TARGET_IPHONE_SIMULATOR");
  NSLog(@"To device debug, open RCTWebSocketExecutor.m & replace localhost with MacBook IP.");
  // Get dev host IP Address:
  //    ifconfig | grep inet\ | tail -1 | cut -d " " -f 2
  jsCodeLocation = [NSURL URLWithString:@"http://<IP_ADDRESS>:8081/index.ios.bundle"];
#endif

#else
  NSLog(@"AppDelegate:RELEASE jsbundle");
  jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif

  NSLog(@"jsCodeLocation = %@",jsCodeLocation);

  RCTRootView *rootView = [[RCTRootView alloc] initWithBundleURL:jsCodeLocation
                                                      moduleName:@"BluetoothConnect"
                                               initialProperties:nil
                                                   launchOptions:launchOptions];
  rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];
  return YES;
}

We were able to fix this without changing the jsCodeLocation code. It turns out that rn looks up the localhost ip either in the hosts file or because of the hosts file, I'm not good enough to read the Obj C to figure out exactly what its doing. I don't explicitly set localhost in our hosts files, as DNS will resolve it anyways, but because it isn't explicitly stated as <IP_ADDRESS> localhost, rn isnt able to grab the url of the device to store for offline bundle creation or interacting with the packager.
So the solution was to add the localhost line to the hosts file, and the error went away, without changing the scheme to release and without hardcoding the old jsCodeLocation code. I will say that it is also possible some people who do have the localhost line explicitly set in the hosts file may be having issues because the hosts file has been corrupted or is encoded incorrectly. I've read a bunch of places while hunting for the solution to this problem that osx fails to read the hosts file if it has those issues.
I've updated the so question here as well with what I've found http://stackoverflow.com/questions/38780325/running-react-native-app-on-ios-device-using-offline-bundle/40730709#40730709.

thanks for the tip @aleclarson 🎉

Still getting the same error. Tried all of it. Can someone help?
Dec 12 18:34:41 tw-mbp-stelang logd[6406] : metadata shared cached uuid is null (using logd's shared cache info) AwesomeProject (11002)
Dec 12 18:34:41 tw-mbp-stelang logd[6406] : Failed to harvest strings for pathless uuid '00000000-0000-0000-0000-000000000000'
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : assertion failed: 15G1108 14B72: libxpc.dylib + 62597 [17F6B510-0FB1-30D3-B29C-D74A5D63719E]: 0x7d
Dec 12 18:34:41 tw-mbp-stelang Unknown[11002] :
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : [] nw_host_stats_add_src recv too small, received 24, expected 28
--- last message repeated 2 times ---
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : [] ____nwlog_simulate_crash_inner_block_invoke dlopen CrashReporterSupport failed
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : [] __nwlog_err_simulate_crash simulate crash failed "nw_socket_set_common_sockopts setsockopt SO_NOAPNFALLBK failed: [42] Protocol not available"
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : [] nw_socket_set_common_sockopts setsockopt SO_NOAPNFALLBK failed: [42] Protocol not available, dumping backtrace:
[x86_64] libnetcore-856.20.4
0   libsystem_network.dylib             0x000000010987d682 __nw_create_backtrace_string + 123
1   libnetwork.dylib                    0x000000010a0ec932 nw_socket_add_input_handler + 3100
2   libnetwork.dylib                    0x000000010a0ca4f4 nw_endpoint_flow_attach_protocols + 3768
3   libnetwork.dylib                    0x000000010a0c9511 nw_endpoint_flow_setup_socket + 563
4   libnetwork.dylib                    0x000000010a0c8270 -[NWConcrete_nw_endpoint_flow startWithHandler:] + 2612
5   libnetwork.dylib                    0x000000010a0e344d nw_endpoint_handler_path_change + 1261
6   libnetwork.dylib                    0x000000010a0e2e7c nw_endpoint_handler_start + 570
7   libnetwork.dylib                    0x000000010a0faae5 nw_endpoint_resolver_start_next_child + 2240
8   libdispatch.dylib                   0x00000
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : [] nw_host_stats_add_src recv too small, received 24, expected 28
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : [] __nwlog_err_simulate_crash simulate crash already simulated "nw_socket_set_common_sockopts setsockopt SO_NOAPNFALLBK failed: [42] Protocol not available"
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : [] nw_socket_set_common_sockopts setsockopt SO_NOAPNFALLBK failed: [42] Protocol not available, dumping backtrace:
[x86_64] libnetcore-856.20.4
0   libsystem_network.dylib             0x000000010987d682 __nw_create_backtrace_string + 123
1   libnetwork.dylib                    0x000000010a0ec932 nw_socket_add_input_handler + 3100
2   libnetwork.dylib                    0x000000010a0ca4f4 nw_endpoint_flow_attach_protocols + 3768
3   libnetwork.dylib                    0x000000010a0c9511 nw_endpoint_flow_setup_socket + 563
4   libnetwork.dylib                    0x000000010a0c8270 -[NWConcrete_nw_endpoint_flow startWithHandler:] + 2612
5   libnetwork.dylib                    0x000000010a0e344d nw_endpoint_handler_path_change + 1261
6   libnetwork.dylib                    0x000000010a0e2e7c nw_endpoint_handler_start + 570
7   libnetwork.dylib                    0x000000010a0faae5 nw_endpoint_resolver_start_next_child + 2240
8   libdispatch.dylib                   0x00000
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : jsCodeLocation = (null)
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : Initializing <RCTBatchedBridge: 0x6180001998b0> (parent: <RCTBridge: 0x6180000bd640>, executor: RCTJSCExecutor)
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : *** Assertion failure in -RCTBatchedBridge loadSource:onProgress:, /Users/stelang/dev/AwesomeProject/node_modules/react-native/React/Base/RCTBatchedBridge.m:196
Dec 12 18:34:41 tw-mbp-stelang AwesomeProject[11002] : *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'bundleURL must be non-nil when not implementing loadSourceForBridge'
*** First throw call stack:
(
0   CoreFoundation                      0x000000010572834b __exceptionPreprocess + 171
1   libobjc.A.dylib                     0x000000010463621e objc_exception_throw + 48
2   CoreFoundation                      0x000000010572c442 +[NSException raise:format:arguments:] + 98
3   Foundation                          0x0000000104202d79 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
4   AwesomeProject                      0x0000000103d4f355 -[RCTBatchedBridge loadSource:onProgress:] + 997
5   AwesomeProject                      0x0000000103d4d4c3 -[RCTBatchedBridge start] + 883
6   AwesomeProject                      0x0000000103d8f60c -[RCTBridge setUp] + 684
7   AwesomeProject                      0x0000000103d8e663 -[RCTBridge initWithDelegate:bundleURL:moduleProvider:launchOptions:] + 387
8   AwesomeProject                      0x0000000103d8e472 -[RCTBridge initWithBundleURL:moduleProvider:launchOptions:] + 146
9   AwesomeProject                      0x0000000103cebc27 -[RCTRootView initWithBundleURL:moduleName:initialProperties:launchOptions:] + 183
10  AwesomeProject                      0x0000000103cc937a -[AppDelegate application:didFinishLaunchingWithOptions:] + 266
11  UIKit                               0x0000000107c9a0be -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 290
12  UIKit                               0x0000000107c9ba43 -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 4236
13  UIKit                               0x0000000107ca1de9 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1731
14  UIKit                               0x0000000107c9ef69 -[UIApplication workspaceDidEndTransaction:] + 188
15  FrontBoardServices                  0x000000010b127723 FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK + 24
16  FrontBoardServices                  0x000000010b12759c -[FBSSerialQueue _performNext] + 189
17  FrontBoardServices                  0x000000010b127925 -[FBSSerialQueue _performNextFromRunLoopSource] + 45
18  CoreFoundation                      0x00000001056cd311 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
19  CoreFoundation                      0x00000001056b259c __CFRunLoopDoSources0 + 556
20  CoreFoundation                      0x00000001056b1a86 __CFRunLoopRun + 918
21  CoreFoundation                      0x00000001056b1494 CFRunLoopRunSpecific + 420
22  UIKit                               0x0000000107c9d7e6 -[UIApplication _run] + 434
23  UIKit                               0x0000000107ca3964 UIApplicationMain + 159
24  AwesomeProject                      0x0000000103cc974f main + 111
25  libdyld.dylib                       0x000000010967068d start + 1
26  ???                                 0x0000000000000001 0x0 + 1
)
Dec 12 18:34:41 tw-mbp-stelang SpringBoard[6412] : [KeyboardArbiter] HW kbd: Failed to set (null) as keyboard focus
Dec 12 18:34:41 tw-mbp-stelang com.apple.CoreSimulator.SimDevice.BFAC201D-7386-4604-844F-35B0E8A23E1F.launchd_sim[6395] (UIKitApplication:org.reactjs.native.example.AwesomeProject[0x6f37][11002]) : Service exited due to Abort trap: 6
Dec 12 18:34:41 tw-mbp-stelang assertiond[6416] : notify_suspend_pid() failed with error 7

I got this when migrating a native project over to react native: check that the following is in your info.plist (right click it and edit as source).
<key>NSAppTransportSecurity</key>
	<dict>
		<key>NSExceptionDomains</key>
		<dict>
			<key>localhost</key>
			<dict>
				<key>NSIncludesSubdomains</key>
				<true/>
				<key>NSTemporaryExceptionAllowsInsecureHTTPLoads</key>
				<true/>
			</dict>
		</dict>
	</dict>

can you speak chinese?


fix: Fix type checking

Signed-off-by: Manuel Schönlaub<EMAIL_ADDRESS>This PR
This PR fixes typing errors in the client code:

The Liskov Substitution Principle should also apply to providers. This relates to the signature of the methods to retrieve flags.

Incorrect usage of type instead of flagType. Most probably a typo.

Ensure that the callables in create_provider_evaluation are annotated in a mypy-friendly way.

Fix type annotations for FlagEvaluationDetails

Fix type annotations around optional parameters all over the place

Related Issues
Fixes #17

Codecov Report

Merging #25 (7102813) into main (04a4323) will increase coverage by 0.08%.
The diff coverage is 78.26%.

@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
+ Coverage   92.83%   92.92%   +0.08%
==========================================
  Files          18       18
  Lines         321      325       +4
==========================================
+ Hits          298      302       +4
  Misses         23       23

Flag
Coverage Δ

unittests
92.92% <78.26%> (+0.08%)
:arrow_up:

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

Impacted Files
Coverage Δ

open_feature/hooks/hook_support.py
95.00% <ø> (ø)

open_feature/provider/no_op_provider.py
100.00% <ø> (ø)

open_feature/exception/exceptions.py
79.16% <37.50%> (ø)

...n_feature/evaluation_context/evaluation_context.py
90.90% <100.00%> (+0.90%)
:arrow_up:

...feature/flag_evaluation/flag_evaluation_details.py
100.00% <100.00%> (ø)

open_feature/hooks/hook_context.py
100.00% <100.00%> (ø)

open_feature/open_feature_api.py
100.00% <100.00%> (ø)

open_feature/open_feature_client.py
96.29% <100.00%> (+0.04%)
:arrow_up:

open_feature/provider/provider.py
75.00% <100.00%> (+0.92%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@mschoenlaub I've invited you to the python maintainers group. Feel free to accept or not. Soon we will be formalizing the responsibility of that role (you can leave it anytime you want, of course) but it will allow you to merge for now if you'd like.

We could also instead just merge this as typing enhancements and resolve the optional provider issue separately. In the name of progress 🚀


Add postgres' PDO driver

As someone who uses postgres, I noticed this image doesn't actually have a PDO driver in it 😭
It's pretty simple to add this ✨

Would love to see this landed because nextcloud requires pdo_pgsql :smile: Unfortunately, @ameliawylie you forgot to update the Dockerfile-no-stats file in your PR.

@ameliawylie just update the other file as mentioned above and I'll merge it in.
Thanks.

This has been added for 1.0.2 release.


Gcs support temp

test gcs support - checking latest changes

@Yuhta I believe this is a temp PR as the title suggests. The main PR is here https://github.com/facebookincubator/velox/pull/1565 and I plan to review it later today.


Harshad number in C++

💥 Proposal
Program to check if a number is harshad number
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


Pyinstaller traceback error eel

 I tried to build (package) eel program using pyinstaller.
Pyinstaller workes fine and build the app successfully.
But when i tried to run the exe in dist folder i got following error:-
`Traceback (most recent call last):
  File "C:\Users\Administrator\Desktop\PythonEel\oslister.py", line 1, in
    import eel, os, random
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36-32\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 631, in exec_module
    exec(bytecode, module.__dict__)
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36-32\lib\site-packages\eel\__init__.py", line 2, in
    import gevent as gvt
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36-32\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 631, in exec_module
    exec(bytecode, module.__dict__)
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36-32\lib\site-packages\gevent\__init__.py", line 87, in
    from gevent._hub_local import get_hub
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36-32\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 631, in exec_module
    exec(bytecode, module.__dict__)
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36-32\lib\site-packages\gevent\_hub_local.py", line 101, in
    import_c_accel(globals(), 'gevent.__hub_local')
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36-32\lib\site-packages\gevent\_util.py", line 105, in import_c_accel
    mod = importlib.import_module(cname)
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36-32\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named 'gevent.__hub_local'
[1240] Failed to execute script oslister`

Help Needed

I also experienced the same problem.
I do not know whether it is correct, but I generated an exe file in the following way.

Copy pyinstaller execution command
Add the following to the copied command　＆ run
 --add-data C:\Users\Administrator\AppData\Local\Programs\Python\Python36-32\lib\site-packages\gevent";"gevent"

Hi. I'm closing this issue due to inactivity and the belief that it has been fixed in a more recent release of Eel.
If you continue to have this problem, please leave a message here or open a new issue.
Thanks.


Switch from HIVSeqinR to HIVIntact

Try using HIVIntact to determine which samples are intact.
HIVIntact is apparently designed for improved integration into analysis pipelines, and is more “customizable” than current tools (such as SeqinR).
One additional possible advantage of this program is that it appears to be able to handle HIV sequences belonging to different subtypes (as opposed to SeqinR which may not be appropriate for use on many (all?) non-B subtypes.

There's a paper related to the project.


relay/meta(dm): fix potential data races after saving GTID

What problem does this PR solve?

Issue Number: close #4166
What is changed and how it works?
When a GTID set is saved into LocalMeta, clone this GTID set first and then do the updating.
Otherwise, after a GTID set is saved into LocalMeta, the input GTID set and the one inside LocalMeta are referencing the same object.  It'll cause potential data race when modifying the input GTID set object and reading the GTID set inside LocalMeta happen simultaneously.
Check List
Tests

Unit test

Code changes
N/A
Side effects
N/A
Related changes
N/A
Release note
None

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

/cc @glorv @lance6716

/run-verify

Codecov Report

Merging #4455 (9607554) into master (e469fb3) will decrease coverage by 0.1675%.
The diff coverage is 54.3026%.

Flag
Coverage Δ

cdc
59.9222% <60.5381%> (-0.2652%)
:arrow_down:

dm
52.0288% <42.1052%> (-0.0747%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #4455        +/-   ##
================================================
- Coverage   55.8077%   55.6402%   -0.1675%
================================================
  Files           495        494         -1
  Lines         61246      61283        +37
================================================
- Hits          34180      34098        -82
- Misses        23614      23750       +136
+ Partials       3452       3435        -17

don't forget to sign cla https://github.com/pingcap/tiflow/pull/4455#issuecomment-1019792900

/merge


[Bitwarden]: Add forms to create a bitwarden records

Description
Add ability to crate a Bitwarden recors
Type of change

Bug fix / improvement for somebody else's extension. Extension author: @pomdtr

Screencast
https://www.loom.com/share/ad4862be7af341f58bdb63f18a8ea849
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast

This is a big one! Give me a few days for the review 😅

Hey @guga4ka – any updates here? Btw, the CI seems to be failing with prettier errors...

@fe9lix sorry, feel free to close this pr, it's on hold due to war in my country.

@guga4ka You can re-open it any time, of course. Maybe @pomdtr could help out meanwhile? (Unfortunately I'm not familiar with Bitwarden myself.) The prettier errors should be easy to fix by just running npm run fix-lint (which basically runs npx prettier src/** --write)

sorry, feel free to close this pr, it's on hold due to war in my country.

Sorry to hear that, take care of yourself and your loved ones.


justifies controls at bottom of survey page

Signed-off-by: Kevin N. Murphy<EMAIL_ADDRESS>Description
Justifies the survey control buttons

[ x] For visual changes, I've attached before and after screenshots

Nice!


Team XP gain limit

These modes are great, but in order to avoid high-level players with low-level upgrades, can you add a configuration setting so that low-level characters with a level difference of more than 10 cannot get XP

Yes, I can add that as a config option.

how's the progress xD

@ZhengPeiRu21 Continue？

@ZhengPeiRu21 Continue？

Sorry, I had forgotten about this. I will look into it soon!


Selecting generic families

This lib includes fn set_serif_family etc. but has no default assignments, which may be useful in lieu of a full fontconfig implementation.
Font-kit does do this, here.
P.S. close as "out of scope" if you like; this isn't clear from the README.

Yes, this is a good idea. Not sure why I've didn't do this initially.


Enhancement: Add Final total number of reads basecalled at end

Progress shows a snapshot of chunked basecalled reads
It would be good I it showed the full total at the ned as well

The final number of reads is now printed at the end


Add event initiator

Pull Request Test Coverage Report for Build 84

18 of 24 (75.0%) changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 73.646%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

common/src/main/java/com/mercateo/eventstore/domain/Reference.java
1
2
50.0%

common/src/main/java/com/mercateo/eventstore/domain/EventInitiator.java
2
7
28.57%

Totals

Change from base Build 80:
-0.09%

Covered Lines:
408

Relevant Lines:
554

💛  - Coveralls


Add classifier: Topic :: Scientific/Engineering :: Hydrology

Suggest to use this classifier in an effort to centrally start documenting Python packages for use in hydrological studies. (pypa/warehouse#5728)

Codecov Report

Merging #32 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #32   +/-   ##
=======================================
  Coverage   84.77%   84.77%
=======================================
  Files           7        7
  Lines        1189     1189
=======================================
  Hits         1008     1008
  Misses        181      181

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 32992bd...cbc0fb2. Read the comment docs.

Thanks for creating this classifier and including this!


INFRA-85 – less revealing headers

And possibly also footer of certain default pages, although Apache default changes may already have got rid of those.

Retire old PHPs
INFRA-85 – make Apache reveal its existence and no more detail
INFRA-85 – don't expose PHP in headers

Tested against MatchBot locally, seems about right so far:

We can temporarily run on push, as with previous updates, if this passes review and reaches main tomorrow. Or alternatively wait until next week before actually getting apps using the patched image.


arabic product in home page Not lined up in one format

Bug report
Title
arabic product in home page Not lined up in one format

The product appears in small cards, and larger card.
width and height  are not consistent

Issue Description
When presenting Arabic content, it appeared untidy on the main page of the site in Velocity Theme
Preconditions
Please provide as detailed information about your environment as possible.
1. framework Version. last version v1.1.2
2. Commit id.

Steps to reproduce
It is important to provide a set of clear steps to reproduce this bug.If relevant please include code samples.
1. step1
2. step2

Expected result
Tell us what should happen.

[Screenshots, logs or description]

Actual result

Tell us what happens instead.

[points....]

any update ..?

Hello there,
Basically I suggest you need to add images of same size, that will make your site look better.

i try did that.
But the problem still exists.
In addition to a demo site, it carries the same problem when converting to Arabic

Have you tried setting up the height fix of product images displaying in card ?

Hi @Tayeb-Ali
We aren't getting any response from the last 20 days, so we're closing this.
Feel free to reopen it anytime.
Thanks


404 on the RSS Feed

Showing 404 error on the RSS Feed

I can't reproduce. Can you try again? https://microsoft.github.io/AzureTipsAndTricks/rss.xml

RSS feed is confirmed working properly.


Add a "Member of" column in the Persons list

Add a "Member of" column in the Persons list. It should show a comma-separated list of organisations this person is a member of. Every organisation should be a link to the organisation page.

Implemented in PR: https://github.com/StarcounterSamples/People/pull/35

Fixed in #35, closing


New Feature

This is not an issue but a request.
Can you create a script that can save/export the Gelbooru Favorites as CSV (Only the Post ID) and can later import it back to Gelbooru (Same or Different Account).

Hi,
I've had a look at the API documentation but it appears that it does not currently support functionality to favourite posts.
The most we could do at the moment is save the post IDs of a user's favourite posts to a JSON file.
If the API is updated in the future to support favouriting then it should be relatively simply to create a script which takes post IDs from a JSON and favourites them.


Repo sync for protected CLA branch

The pull request is created from master637695902316455171 to master to fix git push error for protected CLA branch

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change. @evanwindom


10330: Toggle password fields on render

Fixes a long-standing bug where password fields were hidden if the page refreshed, e.g. when submitting a form that has errors. Previously they were only shown on a change in status of the select dropdown.

Cool!

Cool!


Fix Checkbox component

FIx checkbox value prop and add label.

Not sure what is going on this travis...
Anyway. I like the idea behind this PR. The point of this library (which is missing from the Read Me). is Convenience. I got tired of re-writing the basic (and error prone) mappers from Formik to Material ui.
So there are 2 ways we can go forward: Merge as is or Create a CheckboxWithLabel component that does what this does. If we go with option 2 is there really any value in the plain checkbox component?
I played around with using the api and I think this should go in as is.

I agree, I prefer this API rather than the original from Material-UI. Thanks.

Hey friends, I have been playing with your repo all weekend :)
So far loving it.
I don't want to but in with my ideas and suggest you change what you are doing - obviously you should build what you need first and foremost. I just wanted to share what I have been doing.
Regarding the question of CheckboxWithLabel (i think i even called it this) @cliedeman I went just went down the path of creating variants for all form component with and without a label. I ended up deciding it was a silly difference and collapsed them.
For the checkbox I just wrapped it in a material-ui label - easy as pie.
Also if you are looking through my code, this is very much an experimental approach and full of work in progress experiments - but the gist of it is to use Brad Frost's Atomic Design principles with react components and later redux. The consequence of this is that it is very easy to later change small parts of the application :) and hopefully ends up being accessible to juniors (please let it be so!!!)
In anycase I only say this to provide some context of why I am making small reusable components.
In regards to whether formik-material-ui should depart from the material-ui api. As someone using the repo already (and loving it) I'm in two minds, on the one hand material-ui's documentation is pretty good and if the library just wraps this and formikifies it then I can safely just rely on that. On the other hand there is the opportunity to fix things like the adding a label to checkbox (I was surprised they didn't)
Then there is also the opportunity to add other common form components like SimpleFileUpload which I think is super cool
I much appreciate the work so far and am keen to support the project going forward :)
ps Im from New Zealand - though currently I'm in Cape Town visiting family - small world :)

Hello :), small world indeed.
Sorry I have taken so long to reply.
I am happy keeping the API as simple as possible. Small changes can have really unexpected behavior. For example, a while back I added so that fields are disabled during submission but inadvertently removed the ability to allow the user to disable Text Fields. (This was added later)
but there is no way to override the disabled behavior during submission. I sometimes using formik for search fields with a debounced auto submit but with this code there will be a disabled flicker during each submission.
Is this something that should work out of the box or for that special use case should I just fall back to creating a custom text field?
In general, I expect this library to get you going quickly but as the forms evolve and become more complicated these basic components will just be replaced by custom ones. I like the current trade off of convenience for flexibility.

Great answer

Is this something that should work out of the box or for that special use case should I just fall back to creating a custom text field?

I think this should be either another atom in the library or expect the user to make their own.
I don’t think it is very important to have DRY code in a niche component library. Ie material-ui being a big and super general component library. This library is far more specific and the most important thing is it works for you in your business :)
So if you feel it having a search field in here would save you time - id just add it, even if 90% of the code is the same as another field.

I have given this some more thought and realized the mappings from field to Checkbox/Textfield etc. should actually be part of the public api. (Seeing as that is the bulk of the library anyway).
I have created #32 to test this theory out. please have a look. Especially this.
@stalmok I also added a CheckboxWithLabel component because it's just too useful a use case to pass up on, but on the other hand I like the idea of atoms and want to keep the Checkbox too.

I am closing this now that #32 is merged. Please let me know if this covers all your use cases


sensu Invertebrata

We were trying to work out what to do with the sensu
terms that were sensu Invertebrata. Michael has worked
out how to deal with the problem:
I have looked at all of the terms with 'sensu Invertebrata'
I think the equivalent term from the NCBI_taxonomy is
Protostomia id: 33317
This includes annelids ("true" worms), molluscs, and
arthropods but NOT nematodes.
Most of the Invertebrata terms are for defence mechanisms.
Are any of these use by C elegans ? If not then change
all to Protostomia.
I think this subgraph must simply be an error:
process.ontology:      %odontogenesis (sensu
Invertebrata) ; GO:0042477 ; synonym:tooth development
(sensu Invertebrata)
no invertebrate as teeth in the accepted meaning of the
word ! (as far as i know)
The only terms which cause problems are those to do
with cuticle.  My recollection here is the
distinction between animal (worm, insect) and plant
cuticles.
As there is - in Taxman - no grouping term for the
Protostomia and Nematodes I suggest we
do what a formal taxonomist would do and label these:
sensu Nematoda+Protostomia.
Michael
Reported by: jenclark
Original Ticket: "geneontology/ontology-requests/1505":https://sourceforge.net/p/geneontology/ontology-requests/1505

thanks www.movied.org


mo.lazy preview code shown in documentation running incorrectly

Documentation is

[ ] Missing
[ ] Outdated
[ ] Confusing
[X] Not sure?

Explain in Detail
The example code provided for the LazyComponent in the docs/api/layouts section is not functioning correctly due to a missing library - random import. This is causing the following issue error popup:

[!CAUTION]
Function call (name: load, args: {}) failed with exception name 'random' is not defined

I plan to submit a Pull Request (PR) with the following changes:
Your Suggestion for Changes
To resolve this issue, I plan to:

Import the random function.
Ensure the updated example code runs as expected.

This PR will ensure that the documentation previews its demo in the right way, running without any errors/issues.

Thank you for the issue report and the PR!


Autofill for TextField is not firing onChange in all browsers

This may not be a Stripe Apps issue, but it's an issue we've had to deal with in our application.  When a user inputs their origin address for shipping, depending on their browser, the onChange event does not get fired when auto-filling their address via their browser.  And in some browsers, the autofill attribute is not respected.  We would like them to be able to auto-fill their address, and we would like the onChange event to get respected, regardless of the browser.  For reference see this issue: https://stackoverflow.com/questions/55244590/autofill-does-not-trigger-onchange
I've created a test component that should work similarly across browsers, but it does not behave as expected in cross-browser experiments:

import {
  Box,
  Button,
  ContextView,
  Switch,
  TextField,
} from "@stripe/ui-extension-sdk/ui";
import type { ExtensionContextValue } from "@stripe/ui-extension-sdk/context";
import { useCallback, useEffect, useRef, useState } from "react";

type Address = {
  name?: string;
  city?: string;
  state?: string;
  line1?: string;
}

const App = () => {
  const [address, setAddress] = useState<Address>({})
  const [autofill, setAutofill] = useState<boolean>(false)
  const [displayAddress, setDisplayAddress] = useState<Address>()

  const currentAddress = useRef<Address>({})

  const showAddressResult = useCallback(() => {
    setDisplayAddress(currentAddress.current)
  }, [])

  useEffect(() => {
    currentAddress.current = address
  }, [address])

  const handleChange = (key: keyof Address, value: string) => {
    setAddress(prev => ({ ...prev, [key]: value }));

  };

  return (
    <ContextView title="Autofill address browser test">
      <Box css={{  stack: "y", gap: "small" }}>
        This applications tests if auto-filled forms trigger an on-change event, also reveals if the autofill attribute is respected by the browser.

      <Switch label="Set auto fill attribute to on" defaultChecked={autofill} onChange={(e) => setAutofill(e.target.checked)} />
      <TextField
        label="Name" autoComplete={autofill ? "on" : "off"} placeholder="Name" name="name"
        onChange={(e) => handleChange("name", e.target.value)}
      />

<TextField
        label="Address Line 1" autoComplete={autofill ? "on" : "off"} placeholder="Address line 1" name="line1"
        onChange={(e) => handleChange("line1", e.target.value)}
      />

      <TextField
        label="City" autoComplete={autofill ? "on" : "off"} placeholder="City" name="city"
        onChange={(e) => handleChange("city", e.target.value)}
      />
            <TextField
        label="State" autoComplete={autofill ? "on" : "off"} placeholder="State" name="state"
        onChange={(e) => handleChange("state", e.target.value)}
      />

      <Button type="primary" onPress={() => showAddressResult()}>
        Show result
      </Button>

      {displayAddress && <Box>
        <Box>
          Name: {displayAddress.name}
        </Box>
        <Box>
          Address Line 1: {displayAddress.line1}
        </Box>
        <Box>
          City: {displayAddress.city}
        </Box>
        <Box>
          State: {displayAddress.state}
        </Box>
      </Box>}

      </Box>

    </ContextView>
  );
};

export default App;

Thanks for the report, @bensontrent!
We have tested this functionality according to https://docs.stripe.com/dashboard/basics#browser-compatibility. We couldn't reproduce this on any of our supported browsers, the onChange was triggered in all supported browsers on autocomplete. Seeing as this issue isn't browser behavior, the Apps platform does not plan to solve this issue.


Scalafix the string contexts to org.http4s.implicits

We couldn't do #2661 through our normal deprecation cycle.  This would be very nice to have a scalafix for, but I'm not sure how to conditionally add an import.  Rewriting old references to call the string contexts explicitly would keep code compiling, but be horribly ugly.
This is beyond my scalafix skills.

This seems old and unlikely to happen.


[release-23.05] github-runner: 2.310.2 -> 2.311.0

Description of changes

Cherry picked the hash/version update from #263101 since this is still on node 16.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

it isn't said enough... but @newAM and @veehaitch thank you for your constant work on this :heart:


Feature request: support for IPv6

IPv4 addresses are supported at ping hosts (e.g., <IP_ADDRESS>), but IPv6 (e.g., 2001:4860:4860::8888) isn't on Linux as it requires the use of ping6 instead of ping.
It would be nice to support both.

Thanks for the request, @hugoh
Should be able to use the -6 flag with the ping command in many circumstances

@hugoh this was implemented by #61

Awesome, thank you!

On Feb 6, 2022, at 5:00 PM, highvolt-dev @.***> wrote:

@hugoh this was implemented by #61
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Reopened based on feedback from @hugoh in #61

Thanks. It's working except for 1 aspect: I could not figure out how to enable it via .env. I tried to set tmo_6, tmo_ping6, tmo_ping_6, tmo_ping-6 to True without success. Am I missing something?

It's intended to be set via tmo_ping_6=True
Can you verify the rest of your .env file is being parsed?
After restructuring the repo into modules and to use setup.py, it looks like the .env doesn't get picked up because it installs a copy of the program rather than using your cloned repo.
Try reinstalling with pip3 install -e . so it installs with a symlink to the repo directory or installing into a virtualenv that is a subdirectory of the repo directory so it can traverse up to get to the .env file

It doesn't pick up the tmo_ping_6 option.
The following .env:
tmo_ping_host=github.com
tmo_ping_6=True
tmo_skip_reboot=True
tmo_print_config=True

gives the following config:
Script configuration:
[..]
  Ping configuration:
    Host: github.com
    Count: 1
    Interval: 10
    Protocol: IPv4

It picks up tmo_ping_host but not tmo_ping_6.

Thanks for the sanity check, @hugoh - just committed what should be the necessary fix


Manually upload WSIMOD docker image and model/data files to DAFNI

To test if the integration with the environment work as expected and fix any possible issues.

Model deployed to DAFNI alongside the example settings and data files.


Need a help to save the output file

In Example: Hansen–Law xenon i want to save the  output_text
i ran the code and i seems to be working properly and i was able to save the output plot
is there way to save this dat file

Hi there! Are you basically trying to save a text file of the transformed image?
You can try adding something like:
np.savetxt('abel_transform.txt', recon)

towards the end of the example script.
Here is a modified example script that saves the Abel transformed image as a text file using the line above:
https://gist.github.com/DanHickstein/1a63ac94621027784603ec59ce636854

I think that this issue has been addressed, so closing this issue.

I think that this issue has been addressed, so closing this issue.


Replace secp256k1 with coincurve

i think we should just migrate to coincurve - it is well maintained (last secp256k1 release was in 2021) - and even CLN uses coincurve and not secp256k1 for their python plugins
related issues:

https://github.com/lnbits/bolt11/issues/45
https://github.com/lnbits/lnurlp/issues/57
https://github.com/lnbits/nostrclient/issues/29
https://github.com/lnbits/nostrmarket/issues/103
https://github.com/lnbits/nostrrelay/issues/26

Thomas from Electrum released recently electrum-ecc with zero dependencies making it a great candidate too. Coincurve pulls in CFFI and other deps.


Multiple enhancements

Hello everyone,
This PR has for purpose to add the following enhancements:

Added iOS 9 support
Fixed picker toolbar wrong positioning on iOS 11
Added animation to picker appearance/disappearance
Updated gitignore

Notes:

README.md does not reflect the proper minimum supported iOS version
SmartcarAuth project has multiple times the example app, once as a subproject, once as a target. I'd recommend keeping only the target and remove the project file altogether

Thanks for considering

@zz60 I have updated the tests to take animation and new hiding technique into account

Looks good! Thank you for the changes!


Update analytics overview page with some links

Add links for various subpages of Analytics to the core Analytics page

🚀 Deployed on https://659dc73589a0866746d9ab4e--cozy-fox-0defec.netlify.app


Stream timesync error to RPC clients and add API to notify that the clock is correct

Per discussion in https://github.com/spacemeshos/SMIPS/issues/55.
We want to provide users of the smapp with timely notifications that the time is not sync, before node will be shutdown.
On such error user will have to fix the clock and notify the go-sm with another API call.
Once API call is received we assume that the system clock is adjusted and previous errors can be ignored. In future we can also drop peers that have invalid clock.

Q: are we still going to check on startup drift related to average time from several NTP servers and crash the node if drift is too big and only notify via api if there's a drift while the node is running? Need to better understand how node behavior's going to change to think through the UI/UX implications.
@antonlerner @moshababo

I think that as per our discussion in the SMIP in case of a large time drift we will pause all miner operations and put out an error that miner cannot continue running until time drift is fixed. the implementation of halting all miner operations can be via killing it, but can be done in other ways

Streaming errors will be fixed as a part of https://github.com/spacemeshos/go-spacemesh/pull/2603

I will remove it from the current sprint. We are not going to add this API for now to keep things simple. Later we will keep things as they are or act based on feedback (if any).


Various warnings in React 16.13.1

React version 16.13.1
Concurrent mode no
Describe the bug
React throws warnings when useResource is used anywhere:
Warning: Cannot update a component (`CacheProvider`) while rendering a different component (`PartnerRewards`). To locate the bad setState() call inside `PartnerRewards`, follow the stack trace as described in https://fb.me/setstate-in-render

Thanks for the report!
"To locate the bad setState() call inside PartnerRewards, "
React seems to be suggesting the error is in PartnerRewards. I might be able to assist if the code is shared, but it most certainly is an interaction so hard to say what this is without being able to repro.

Here is a barebones PartnerRewards that triggers the warning:
class PartnerRewardResource extends CMSResource {
  static urlRoot = `landing-page-partner-rewards/${SORT_BY_RANK}`;

  readonly id!: number;
  readonly company!: string;
  readonly blurb!: string;
  readonly website!: string;
  readonly logo!: Logo;
  readonly rank!: number;

  pk() {
    return this.id.toString();
  }
}

const PartnerRewards: React.FC<{}> = () => {
  const isDesktop = useBreakpoints({ minWidth: "desktop" });

  const rewardsData = useResource(PartnerRewardResource.listShape(), {});

  return (
    <Box bg="gray4">{JSON.stringify(rewardsData)}</Box>
  );
};

CMSResource is just an extended copy of SimpleResource with a custom fetch - it doesn't touch React.

Thanks, was able to repro, looking into it!

Appreciate it!

Seems to be the call to fetch, but it seems odd that this would be a problem. I left a comment to get clarity in the react github: https://github.com/facebook/react/issues/18178#issuecomment-601992546

Appears to be fixed in 4.5.9


dsaasddsa

test
test
test
test
test

Hi, I have some suggestions to help solving this issue!
Here is a list of similar issues:

1. [dsaasddsa](https://github.com/fjsj/python-social-auth/issues/38)

2. [dsaasddsa](https://github.com/fjsj/python-social-auth/issues/38)

3. [dsaasddsa](https://github.com/fjsj/python-social-auth/issues/38)

4. [dsaasddsa](https://github.com/fjsj/python-social-auth/issues/38)

5. [dsaasddsa](https://github.com/fjsj/python-social-auth/issues/38)

Hope this is useful!
Cheers,
Cinnabot.


Make certificate subject adjustable with indentifiable information

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
We use Istio with AWS ACM PCA.
AWS ACM PCA has a limitation where it doesn't log the SAN Attributes of a certificate, only the subject and some other metadata.
Istio certificate subjects are empty (O=) , meaning that the created certificates are unidentifiable when the CA would be audited.
It would be very nice to have an option that sets the subject of the certificates, preferably with a value comparable to the SPIFFE uri, so that it is clear  where the  certificate came from.
I do understand this is an ACM PCA limitation, and we have submitted a feature request.
Describe alternatives you've considered
There is an alternative where you'd modify cert requests with Open Policy Agent, which would be a very ugly workaround.
Affected product area (please put an X in all that apply)
[X] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context
source https://github.com/cert-manager/istio-csr/issues/168

I guess you are saying the selfsigned CA,  by default the subject is not empty, it is cluster.local

I guess you are saying the selfsigned CA, by default the subject is not empty, it is cluster.local

We use AWS Private CA, with istio-csr , cert-manager and the AWS issuer.

IC

Any progress?

Hello, we are integrating istio with Venafi TPP using certmanager and certmanager-istio-csr; and we are facing the same issue. The policies on Venafi TPP dont allow for the Subject name to be empty. So, it would be great if this enhancement can be accepted.

Related to https://github.com/istio/istio/issues/42114 and https://github.com/istio/istio/issues/7153

Lets consolidate this in https://github.com/istio/istio/issues/42114, lots of discussion there already


特别容易崩溃

升级之后，很容易崩溃
<IP_ADDRESS>6

Hi,
I don't understand. Can you elaborate on this?

I'm closing this issue due of inactivity. Reopen if needed.


Add the CI tests for subpackages

Currently Travis and Appveyor only run tests for the top-level gfx_app package. Subpackages, such as gfx_core and gfx_window_* are not tested - only built. Travis and Appveyor scripts need to be changed to test all the packages in gfx repository. Cargo has the ability to run tests for a package given its spec: something like cargo test -p gfx_core will test the gfx_core package. Adding additional test commands to the scripts should be pretty simple.

Is there any reason to test gfx on rust with gnu toolchain as well as on rust with msvc toolchain? Seems redundant, since all of gfx is written in rust. I can delete the gnu target from appveyor while I'm working on this issue.

@retep998 do you see any use of testing the GNU toolchain?

It's nice to test the GNU toolchain as it has somewhat different import libraries that can sometimes have issues (such as when the libd3dcompiler.a turned out to be for a severely outdated DLL). While I do wish MinGW would just go away, if you can test GNU for free, I don't see why you wouldn't want to keep testing it just in case.

That said, do we really need to install mingw through chocolatey? It spams up the build logs like crazy. If the only way to remove the dependency on that is to remove CI for the gnu toolchain, then I'd be okay with that.

Wouldn't the same kind of testing be done by winapi-rs? It tests both stable and nightly on gnu and msvc.

As for chocolatey, it seems appveyor only has mingw32 installed, so the only other way to do it would be to manually download and unpack mingw64.

winapi doesn't cover integration tests at all. It has no idea whether things actually function correctly. At best I can test whether things link and whether the size/alignment of a type is correct. The d3dcompiler issue for example I wouldn't be able to catch with testing in winapi.
What does gfx depend on that has to compile C/C++ code and so need mingw? If the entire dependency tree is pure Rust then the mingw that is bundled with Rust is good enough and no separate installation is needed.

The bindings for the miniz library require gcc to build. Though, I'm not sure what requires the miniz library.

Piston-image, IIRC

On Jun 4, 2016, at 11:44, Eugene Gorodinsky<EMAIL_ADDRESS>wrote:
The bindings for the miniz library require gcc to build. Though, I'm not sure what requires the miniz library.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

No, it doesn't look like anything depends on piston-image. It seems that png depends on it, image depends on png and gfx_app in turn depends on image for some of the examples.

Yes, that's what I meant.

On Jun 4, 2016, at 12:09, Eugene Gorodinsky<EMAIL_ADDRESS>wrote:
No, it doesn't look like anything depends on piston-image. It seems that png depends on it, image depends on png and gfx_app in turn depends on image for some of the examples.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


8184.10 DEV Add GET /db

Shippable/pm#8184
Add GET /db
- return the db information in the same format as vault right now
- the values should be parsed from the env variables already set in the application

verified with a new DO install


Reportback function updates

Fixes #6054
Refs #5991
What's this PR do?
There are a series of function related to Reportback saving etc, that needed to be accounted for with updates regarding the campaign run_nid data. This PR updates all the functions involved.
Where should the reviewer start?
Might be best to review it in order of commits.
How should this be manually tested?
You can pull down the branch, clear cache and try submitting a few reportbacks. Check that the database is correctly updated with the appropriate run_nid on the dosomething_reportbacks table.
What are the relevant tickets?
#6054
#5991

@angaither
CC: @deadlybutter  @DFurnes

Is it worth waiting to merge this to go alongside https://github.com/DoSomething/phoenix/pull/6080 ?

Ok to merge? I've checked locally and things seem to be working ok...

if you're sure it works :+1:

@angaither ominous thumbs up, haha


[Advanced Search] substring vs full word search

We want to allow users the ability to use advanced search features in the search box inputs (in facet panel and above the recordset table). The following is a list of features to include:

[ ] substring vs full word search

append the regex with the beginning/end of word characters

[ ] select which columns for advanced search

customize the columns available through the model
allow pseudocolumn paths to be defined via annotation to show pseudocolumn as an option for user other than just base columns and FK relationships

To support this in chaise, we could have an advanced search option next to the search box.. (not sure what the design would be like after this).

do we want a popup dialog with all advanced search options?
should the space under the search box expand down to show more available options instead?

Something simple like the "Cc W" options in this IDE's test search control. You can see it also has a regex option ".*" but we don't have to go that far with it.
I'm not sure this is really "Advanced Search" its a (relatively simple?) qualifier for the search mode. I think both of which are supported.
My primary usability concern is really the term picker where a curator is picking from a large set of terms and many terms may overlap in ways.


Chapter for Test Environment Setup

https://github.com/elixir-ecto/ecto/issues/2465

@josevalim I've added the chapter

Should the aliases function for the test command also be included? I am not sure about that.

Thanks @philippneugebauer! I have done some changes that expand a bit more the point of using the sandbox. Can you please review my changes?
I think we should also mention the aliases in mix.exs because it makes running tests more convenient, could you please add that too?
Thanks!

I have also added the aliases. Should be good to merge now

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


Status Widget

please find a new status widget in this pull request :)

any idea why the unit test fails? it runs flawlessly on my machine 😕

damn different editor settings ;) thanks for the review! gonna fix it up.

hey @plouc, did you find time to look into again?
is there anything i can add or are you fine with the PR? :)

@swissmanu sorry for the delay, didn't took the time to review it, thanks for your contribution !

dont worry at all... i was just curious :) cool it made it into the repo :+1:


empty array on line 12

Hey,
when take the example code, change the product ID and run the code, I get the error
"[__NSArrayI objectAtIndex:]: index 0 beyond bounds for empty array" on the line of the declaration of product.
Why?
Many thanks in advance

Hi @easybay , can you share your code ? How did you allocated the array ?  It look like array is not allocated.

It's the example code. Copied and paste, same error.

@ClickedApps
Look like error at
SKProduct* product =[[IAPShare sharedHelper].iap.products objectAtIndex:0];
Did you register your product identifier at iTunes Connect ?

I checked it and this error occur because you didn't register any products. So, SKProductsResponse didn't response any product.
However, example code is trying to get index 0. So, this error occur. Please register your in app purchases first.


Merge refs/heads/issue/aggregations-behavior into alpha

Merge refs/heads/issue/aggregations-behavior into alpha

This PR has been merged into alpha and tagged as 2.0.0-alpha-202308181233. Thanks for your contribution!


Titles with no results should be displayed on UI

Currently if any search term doesn't get any results from API, it just logs the "No results found" in browser console. Need to display it in UI.

Done.
Check updated app at App Website
And it's a lot faster now.  💃 💃 💃


Incident Analysis - Incident Density - Remove Optional Raster Output Layer and replace with Kernel Density Tool

After speaking with the spatial statistics team, I learned that the option to have a Raster Output Layer from the Optimized Hot Spot Analysis has gone away as part of ArcGIS Pro due to issues with setting the extent of the output raster layer. While we haven't noticed major issues with it in our our Incident Density model yet, but best practice would be to remove it as an output parameter from our Incident Density model.
For reference, in ArcMap the Optional Density Surface exists:

But in Pro, there is no Optional Density Surface:

Possible Solution

Incorporate the Kernel Density tool into the Incident Density model so that we can get a raster output that will be supported in future versions of ArcGIS Pro.

@Dbarnes1 is this something that will take time and we will need to change the templates in order to complete? Looking at marking this as Version - After Next.

@mfunk definitely a Version - After Next enhancement


Fee for "Unstaking" not paid to corresponding Node Owner

On testnet i did a test of unstaking during the stake period. I was correctly charged 0.8% fee (16000)
https://nebulatestnet.lyra.live/showblock/LEodNAzdRTTrVzVmRxmFZTq2muU3fqV9mdXgNcMusSt8Ms34TRQDkaX5kwLskZ9JEdSxJtNPEr7AsfapusqFDKVgE7mMk1
But surely that fee should have been paid to the node owner as compensation for breaking contract. It appears not. That 16000 fee seems to have disappeared. Node owner address:-
https://nebulatestnet.lyra.live/showblock/LYSRCV7J6QKEZdYVJSxbJCGhW45Yf3DLL8CZssQZuPxJKxibxKTbvtS3mec4qkDYkDrVXLfQxp9tzmPqXEhUm9nxyxxoaE
Node profiting address:-
https://nebulatestnet.lyra.live/showblock/LW6FcY4uPqSqWnhvDJyTtmo31hxaaNhMb2baEcXdcaLnEyHyAMxtuxp2QLRGpFSVRtbNDscYem9jsJEFYT2wJ552uix1Eg
So bug is if user unstakes during stake period fee is charged to the users wallet but that fee is lost in the network and not paid to anyone- it should have gone to the node owner

The fee is redistributed to all nodes as a service reword:
https://nebulatestnet.lyra.live/showblock/Consolidation/6346


Faster torchdata import

🚀 The feature, motivation and pitch
I'm using torchdata for data preprocessing without using GPU and pytorch.
But when I import torchdata, it costs about 6.22s.
I used cProfile to inspect what makes the light-weight torchdata use 6.22s to import.
And I found that torch/__init__.py costs 6.06s, since torchdata import its implementation from torch.
Moreover, most of time is consumed by torch._C._cuda_getDeviceCount() (in torch.cuda.is_available()).
I would like to importing torchdata within 0.5s to be possible.
A possible solution is that make torchdata don't depend on torch.
Alternatives
Add an environment variable(or use CUDA_VISIBLE_DEVICES) to make torch don't check torch.cuda.is_available() during initialization(or make it return False without calling torch._C._cuda_getDeviceCount()).
e.g.
def is_available() -> bool:
    r"""Returns a bool indicating if CUDA is currently available."""
    if not hasattr(torch._C, '_cuda_getDeviceCount'):
        return False
    if os.getenv('CUDA_VISIBLE_DEVICES') == '':
        return False
    # This function never throws and returns 0 if driver is missing or can't
    # be initialized
    return torch._C._cuda_getDeviceCount() > 0

With this, import torchdata still spend about 1s. And this alternative need user set environment variable, which is not convenient.
Additional context
No response

importing torch isn't supposed to initialize the cuda context, which it sounds like is what you're complaining about here. Do you have the stack trace for the is_available call?

I don't have stack trace, but torch._C._cuda_getDeviceCount() seems time consuming.


Ticuare mobile keyboard desactived

When I run the demo of ticuare on mobile when I come back on terminal the keyboard is desactived, I think its because the input It is mouse.
Thanks

Yeah I'd consider this a pretty major issue with Android at least. I have an issue for it open here:
https://github.com/nesbox/tic.computer/issues/66
Closing to avoid duplicate.


Refactored the assets pallet

Made a remove_if_dead function, so that the transfer_and_die function looks a bit cleaner. The function is pretty self-explanatory. The functionality is the same.

Please fix the CI before we can take a look at this.
Currently it reports a conflict and it needs a cargo +nightly fmt.


(Minor) Add a missing period.

Docs Build status updates of commit cc7140d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/Word.WdBuiltinStyle.md
:bulb:Suggestion
View
Details

api/Word.WdBuiltinStyle.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Thanks for the catch @italicize. You have a good eye! We appreciate it.


add swerve steer tuning routine

I'm personally tempted to just consider the swerve steering isomorphic to a flywheel for the purposes of sysid.

Closing since we have #13 now. Note that the last gain update from #10 was obtained using this pr and not what now exists in main. It may be worth tuning the steer gains again once the full mass of the robot is mounted


[EN] Feedback for: /web/fundamentals/performance/rendering/?hl=en

Hi there! This is more of an edit for the callout text regarding a link-out to csstriggers.com.
Instead of:
If you want to know which of the three versions above changing any given CSS property will trigger head to CSS Triggers. And if you want the fast track to high performance animations, read the section on changing compositor-only properties.
Perhaps the phrasing could be written as:
If you want to know if a given CSS property will trigger a change in one of the above cases, head to CSS Triggers. And if you want the fast track to high performance animations, read the section on changing compositor-only properties.

cc @paullewis


Fixed https://github.com/javascript-obfuscator/javascript-obfuscator/…

…issues/195

Coverage increased (+0.004%) to 98.259% when pulling 71f5d43b79b87164a207f64c0378747fa706b050 on dead-code-injection-improvements-2 into 345a1f7dc9b10e5eac95bf13d48c0e37ce61023b on master.

Coverage increased (+0.004%) to 98.259% when pulling 71f5d43b79b87164a207f64c0378747fa706b050 on dead-code-injection-improvements-2 into 345a1f7dc9b10e5eac95bf13d48c0e37ce61023b on master.

Coverage increased (+0.004%) to 98.259% when pulling 71f5d43b79b87164a207f64c0378747fa706b050 on dead-code-injection-improvements-2 into 345a1f7dc9b10e5eac95bf13d48c0e37ce61023b on master.


List All APIs of Set, Hash, and Array that I want to implement for version 1.0.0

I want SortedArray, SortedHash, and SortedSet to be drop in replacements for Array, Hash, and Set. To do that I need to implement the entire API of the relevant classes.
Create a checklist of the methods that we want to implement from the relevant classes.
Secondarily, I also need a list of every additional method that needs to be implemented to support the concept that they are sorted. That should be a separate list because I don't want to mix up my API design with the already set-in-stone API of Array, Hash and Set.

Array Methods

[ ] # &
[ ] # *
[ ] # +
[ ] # -
[ ] # <<
[ ] # <=>
[ ] # ==
[ ] # []
[ ] # []=
[ ] # abbrev
[ ] # all?
[ ] # any?
[ ] # append
[ ] # assoc
[ ] # at
[ ] # bsearch
[ ] # bsearch_index
[ ] # clear
[ ] # collect
[ ] # collect!
[ ] # combination
[ ] # compact
[ ] # compact!
[ ] # concat
[ ] # count
[ ] # cycle
[ ] # delete
[ ] # delete_at
[ ] # delete_if
[ ] # difference
[ ] # dig
[ ] # drop
[ ] # drop_while
[ ] # each
[ ] # each_index
[ ] # empty?
[ ] # eql?
[ ] # fetch
[ ] # fill
[ ] # filter
[ ] # filter!
[ ] # find_index
[ ] # first
[ ] # flatten
[ ] # flatten!
[ ] # hash
[ ] # include?
[ ] # index
[ ] # initialize_copy
[ ] # insert
[ ] # inspect
[ ] # intersect?
[ ] # intersection
[ ] # join
[ ] # keep_if
[ ] # last
[ ] # length
[ ] # map
[ ] # map!
[ ] # max
[ ] # min
[ ] # minmax
[ ] # none?
[ ] # one?
[ ] # pack
[ ] # permutation
[ ] # pop
[ ] # prepend
[ ] # product
[ ] # push
[ ] # rassoc
[ ] # reject
[ ] # reject!
[ ] # repeated_combination
[ ] # repeated_permutation
[ ] # replace
[ ] # reverse
[ ] # reverse!
[ ] # reverse_each
[ ] # rindex
[ ] # rotate
[ ] # rotate!
[ ] # sample
[ ] # select
[ ] # select!
[ ] # shelljoin
[ ] # shift
[ ] # shuffle
[ ] # shuffle!
[ ] # size
[ ] # slice
[ ] # slice!
[ ] # sort
[ ] # sort!
[ ] # sort_by!
[ ] # sum
[ ] # take
[ ] # take_while
[ ] # to_a
[ ] # to_ary
[ ] # to_h
[ ] # to_s
[ ] # transpose
[ ] # union
[ ] # uniq
[ ] # uniq!
[ ] # unshift
[ ] # values_at
[ ] # zip
[ ] # |

Created the relevant issues


Update to use latest node and PureScript

This updates the Dockerfile to the latest available node container and uses yarn to install instead of npm, for faster installation. This also updates the version of PureScript to the latest version, 0.11.7.

Thanks for the PR


apps sc: Bootstrap fluentd namespace if fluentd.audit.enabled=true

[!warning]
This is public repository, ensure not to disclose:

[x] personal data beyond what is necessary for interacting with this pull request
[x] business confidential information, such as customer names

What kind of PR is this?
Required: Mark one of the following that is applicable:

[ ] kind/feature
[ ] kind/improvement
[ ] kind/deprecation
[ ] kind/documentation
[ ] kind/clean-up
[x] kind/bug
[ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important]
Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

[ ] kind/admin-change
[ ] kind/dev-change
[ ] kind/security
[ ] kind/adr

What does this PR do / why do we need this PR?

Previously, if fluentd.enabled = false and fluentd.audit.enabled = true the fluentd-system namespace was never created during bootstrap even though Helmfile is configured to install the log-manager chart in this situation.
This is probably an odd config setup but it happened because the dev flavor defaults to fluentd.enabled = false but fluentd.audit.enabled was set to true separately.

Fixes #

Additional information to reviewers
Screenshots
Checklist

[x] Proper commit message prefix on all commits

Change checks:

[x] The change is transparent
[ ] The change is disruptive
[x] The change requires no migration steps
[ ] The change requires migration steps

Metrics checks:

[ ] The metrics are still exposed and present in Grafana after the change
[ ] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
[ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)

Logs checks:

[ ] The logs do not show any errors after the change

Network Policy checks:

[ ] Any changed pod is covered by Network Policies
[ ] The change does not cause any dropped packages in the NetworkPolicy Dashboard

Pod Security Policy checks:

[ ] Any changed pod is covered by Pod Security Admission
[ ] Any changed pod is covered by Gatekeeper Pod Security Policies
[ ] The change does not cause any pods to be blocked by Pod Security Admission or Policies

Falco checks:

[ ] The change does not cause any alerts to be generated by Falco

Audit checks:

[ ] The change does not cause any unnecessary Kubernetes audit events
[ ] The change requires changes to Kubernetes audit policy

Shouldn't log-manager just respond to .fluentd.enabled as well? :thinking:
But I guess that then there would be an edge case that isn't covered then if you have fluentd with audit on wc, but not on sc. :sweat_smile:

Shouldn't log-manager just respond to .fluentd.enabled as well? 🤔 But I guess that then there would be an edge case that isn't covered then if you have fluentd with audit on wc, but not on sc. 😅

Haven't dug into it more than getting an error during apply to be completely honest. 😅 Does it make sense to install log-manager without installing fluentd? Looks like the configuration option was introduced here: 4b1c689 You might be more apt to answer the question than me. 😄

Yeah, I'm leaning more towards that it should be fully disabled if .fluentd.enabled is false to let it be the main flag for log collection. Because if one wants to have audit logs on wc but not on sc, then one would be missing out on the bulk of the audit logs of ck8s-apps.

Shouldn't log-manager just respond to .fluentd.enabled as well? 🤔 But I guess that then there would be an edge case that isn't covered then if you have fluentd with audit on wc, but not on sc. 😅

Haven't dug into it more than getting an error during apply to be completely honest. 😅 Does it make sense to install log-manager without installing fluentd? Looks like the configuration option was introduced here: 4b1c689 You might be more apt to answer the question than me. 😄

Yeah, I'm leaning more towards that it should be fully disabled if .fluentd.enabled is false to let it be the main flag for log collection. Because if one wants to have audit logs on wc but not on sc, then one would be missing out on the bulk of the audit logs of ck8s-apps.

Like this? https://github.com/elastisys/compliantkubernetes-apps/pull/1770/commits/5856c686021708dc0536929d55024a6365a78a3c or should it also require fluentd.audit.enabled to be true?


Deploy the service to Kubernetes cluster using kubectl

As a DevOps Engineer
I need to use the Kubernetes CLI kubectl command to deploy my service to my Kubernetes cluster
So that my containerized application is running and accessible on the cluster
Details and Assumptions

A Kubernetes cluster is set up on IBM Cloud
Necessary Kubernetes metadata files for deployment are created (e.g., deployment.yaml, service.yaml)

Acceptance Criteria
Given a Kubernetes cluster
When I use the kubectl command to deploy my service to the Kubernetes cluster
Then my service is successfully deployed, running, and accessible on the cluster


Prototypenet visualisation on custom data

@dbolya The idea of protoypnet is really amazing great work , is there any process by which we can visualise the masks in the protonet so as to understand hwo the network is performing on the custom data

There is, just it's not polished.
To get it to work change the tuple in this line:
https://github.com/dbolya/yolact/blob/f46dc4385a41ed1f2df6716ecf6084081afcbec6/layers/output_utils.py#L180
to (4, 8) and then run with the arguments --display --display_lincomb=True (don't use --video or --image).
You can check out that function for more ways to view the prototypes.

@dbolya thanks for this i am able to see the feature map , and i can i look into a particular image how is it learnt because the default which i am able to see the map i am not sure which image has it taken by default

I'm not sure what you mean by that. Could you clarify what you mean by "i am not sure which image has it taken by default"?

when i run the command which you have shared i just get the feature maps , generally saliency maps / activation maps is dependent on the images given as an input to the model right , for eg : as mentioned in ur paper i want to visualize the tennis playing image visualisation

Yeah, and it's using the current dataset's validation set by default (which is what --display does).
And I checked the code again and --display_lincomb=True totally works with --image, I don't know why I said you couldn't use it--I'll edit the original comment. You can choose which image to use using that then.
The tennis player example is image<PHONE_NUMBER>52.jpg in COCO val btw if you want to use it:
--image=./data/coco/images/000000000552.jpg --display_lincomb=True

@dbolya  as usual thanks for ur quick response and wonderful code set ...

This is actually just the output of protonet, i.e., the prototypes that are being combined into the masks. You can't configure it to output other layers sadly because it's in a very different spot in the code.
This is the function that's doing it:
https://github.com/dbolya/yolact/blob/f46dc4385a41ed1f2df6716ecf6084081afcbec6/layers/output_utils.py#L167
Maybe that can help you create a version for the backbone features?

@dbolya wokay i shall try to tune this segment to obtain the feature viz for the all the layers of the network

@dbolya i was able to get the final 32 mask and observe the visualization on the custom data , how can i get the mask coefficients  , since few detection of objects are missing so

The mask coefficients are in the parameter called masks passed into display_lincomb. (Yeah I should have named that better...)

@dbolya is there any way i can modify my model based on the masks generated , since i see that a particular object is not getting highlighted in the feature mask due to which detections are not happening

Did you have anything in mind? Other than tuning the training parameters so that class is more important, I'm not sure how else you could fix that.

@dbolya Hi i was looking into the visualisation and have following queries
1.In the feature map i am able to see the object highlighted but in the output their is no detection unless i decrease the threshold
2. There is mis classification of teh detected object
3. if there are two objects only one object get detected

@abhigoku10 By in the feature map, do you mean the prototypes? It doesn't matter if the object appears in the prototypes--if the backbone detector doesn't detect it, then there's no detection. The masks are only generated after the detector has made all its detections.
Misclassification again happens in the detector without regard to the mask branch. Our classification branch is quite shallow for speed reasons and thus we can't use something like focal loss to improve it. For future versions, this is something we want to fix.
On that note, the detector is also pretty shallow which might cause your 3rd point. 30 fps is a hard target to hit (33 ms / frame), so we walk a fine line here.

@dbolya  yup feature map according to me is prototype
I want to solve misclassification for my dataset so seeing is there any other method which will give me the hack
yup you have done a great work thoughtfull appreciate in achieving 33ms

You can try increasing the number of layers allocated to each branch. Change this setting in your config:
https://github.com/dbolya/yolact/blob/f46dc4385a41ed1f2df6716ecf6084081afcbec6/data/config.py#L505
The order of extra layers is (bbox, conf, mask). So (0, 1, 0) would give just one extra layer to the class prediction branch (these layers aren't shared).
Btw I forgot to mention that since the detection score comes from the class branch, actually all the errors you mention are from the same branch (conf). So maybe you want to give that a lot of extra layers (let's say, (0, 2, 0)).


reindex_like with tolerance changes the type of returned DataArray

I am really excited about all of the new changes to xarray! reindexing with tolerance has great potential to clean up some sort of nasty stuff that I use a lot but have tucked away into a corner of my code. I am not sure I am 100% comfortable with it at the moment, however, because it seems to be changing the types of my data in unexpected ways.
Bei:
test = xr.DataArray([1,2,3], coords=[[0.1, 0.2, 0.3]])
test_i = xr.DataArray([5,6,7,8], coords=[[0.21, 0.31, 0.41, 0.51]])

test.dtype
test.reindex_like(test_i, method='pad', tolerance=0.2).dtype

the reindexed output has changed from int64 to float64!
Even more concerning is the complex example:
test = xr.DataArray(np.array([1,2,3], dtype=np.complex), coords=[[0.1, 0.2, 0.3]])

test.dtype
test.reindex_like(test_i, method='pad', tolerance=0.2).dtype

Conversion from complex to object? Oh no.
Hope this isn't anything too big, let me know if I can help.
Thank

Unfortunately, NumPy has no integer type that can support missing values. This leaves us in a difficult situation for integer types. So, we've copied the approach from pandas of upcasting integers to floats when we need to add NaNs:
http://pandas.pydata.org/pandas-docs/stable/gotchas.html#nan-integer-na-values-and-na-type-promotions
http://xarray.pydata.org/en/stable/computation.html#missing-values (this could use a reference to the aforementioned pandas docs)
Conversion from complex to object is certainly not what we want, though, because NaN is a perfectly valid complex number. A fix to _maybe_promote should take care of that:
https://github.com/pydata/xarray/blob/v0.7.0/xarray/core/common.py#L412
A contribution here would definitely be appreciated! We have made some improvements to complex number support recently but it definitely gets less use.


Use serde_test for unit test instead of serde_json.

Hello again!
These PRs have no new functionality, but may be implementing a more idiomatic way to test serde::{Serialize, Deserialize} by serde_test crate.
But because ArcSwapAny doesn't have  Eq, PartialEq traits implementation, in this case I'm using some wrapper around it.
What do you think about this ?

Codecov Report

Merging #67 (9edcb62) into master (7e16ca3) will decrease coverage by 0.58%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #67      +/-   ##
==========================================
- Coverage   86.34%   85.75%   -0.59%
==========================================
  Files          18       18
  Lines        1091     1081      -10
==========================================
- Hits          942      927      -15
- Misses        149      154       +5

Impacted Files
Coverage Δ

src/serde.rs
91.83% <100.00%> (-8.17%)
:arrow_down:

src/lib.rs
94.81% <0.00%> (-0.31%)
:arrow_down:

What's the advantage of using serde_test over serde_json? I know it has test in its name, so it should be somehow more appropriate, but I feel like we are not using any of the features it provides so we don't benefit from it.

Hypoteticaly, can exist some formats which supported by serde but can't serialize / deserialize into Json.
Also, IMHO, serde_test tokens thing much more undertandable than to_string / from_string comming from serde_json.

I don't think the part with formats unsupported by JSON applies here in any way ‒ the test doesn't use such and we only test that the ArcSwap is „transparent“. But :shrug: whatever, let's have this.
But please have a look at the simplification as noted above.

Hello
Ooops, I must have missed this somehow, my apologies. I've merged it now, when cleaning things up.


Old dumpsters now phase into existing nodes

Since the new nodebox  for the dumpster juts out in a different direction than the old one, dumpsters that were placed before the new nodebox will phase into any adjacent blocks.

It may not be possible to identify old dumpster nodes now, since there is no way knowing whether they were placed before or after the updated nodebox.


defaults fix

I have mixed feelings about this. The problem is clearly with how _nick functions and the docs that surround it. But rather than fix that, which is hard, I just fixed the usage of it in the returners that use it.
In particular: we want to make sure if sourcetype_nebula is undefined that it gets the intended default.

This will need to be backported.


Can't Hit Apply Button On a Laptop With the Addition Apply With LinkedIn Feature

When applying to a job on the career portal from a laptop, you cannot see the apply button.  Normally you could, but with the apply from LinkedIn addition, you cannot.  It cuts off the bottom of box that is used to fill out name and attachment.  The only way around this is to hit the tab key.  But even then, it does not look right.
Current behavior

You cannot hit the apply button on the career portal if you are on a laptop and the career portal supports the apply with LinkedIn Integration.

Expected behavior

You should be able to scroll down to the apply button.

Steps to replicate behavior

Go to http://www.coyotecrk.com/careerportal/#/jobs on a laptop.
Go to any job and hit apply.
The applicants information box displays but is cut off half way though the attach resume portion.

Screenshots

Current

Expected

Took a look at this, on a couple of computers.  It appears to be exclusive to devices with 1366x768 monitors.

@bulbajackel Thank you for reporting this. We will investigate the matter and come up with the best course of action to resolve this. In the meantime, if have an idea and want to submit a pull request I will gladly help in any way I can.
If this is your first time contributing to an open source project you can refer to How to Submit a PR and ping me for any help!
Thanks again!

This is a problem for us as well.
http://www.fastswitch.com/careerportal/#/jobs/
Any idea on a fix timeframe?

To alleviate this pain immediately, you can adjust the margins to push up the box to the top of the screen its being viewed on within the 'styles/app-XXXXXXXXXX.css' file
Edit this -
.modal-container>div.modal {
	max-width: 500px;
	margin: 80px auto;
	height: auto
}

To this:
.modal-container>div.modal {
	max-width: 500px;
	/*margin: 80px auto;*/
	height: auto
}

Thanks to @bulbajackel we have moved the Apply Via LinkedIn experience to the apply details page instead of in the modal. This frees up screen real estate and allows users on smaller screens to see the apply button. Our minimum screen resolution is now 1280x800.


[Chore] Fix the issue that the click version is locked at 7.x

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Fix the issue that the click version is locked at 7.x, fixes #123
In addition, add .vscode into .gitignore make vscode user happy.
Modification

.gitignore
setup.py
requirements/install.txt
mim/click/__init__.py
mim/click/compat.py
mim/click/option.py
mim/commands/download.py
mim/commands/install.py
mim/commands/search.py
mim/commands/uninstall.py

BC-breaking (Optional)
No
Use cases (Optional)
No
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMCls.
The documentation has been modified accordingly, like docstring or example tutorials.

#128 has been merged and please update your branch to fix the CI.
In addition, it would be better to test click < 8.0 in CI.

Suggest renaming mim/click/compat.py to mim/click/compatibility .py

The name compat.py are much more commonly used than compatibility.py.
For examples:

requests/compat.py
pytest/compat.py
tensorflow/compat/compat.py

#128 has been merged and please update your branch to fix the CI.
In addition, it would be better to test click < 8.0 in CI.
      - name: Test click==7.1.2
        run: python -m pip install click==7.1.2
        if: ${{matrix.python-version == '3.8'}}

Add a step in CI： Run unittests with click < 8.0.0
- name: Run unittests with click < 8.0.0
   run: |
       python -m pip install click==7.1.2
       pytest tests/


Version 0.11.6

After #888 and nearly a year since 0.11.5, I think it is time for 0.11.6 to get out ...
What do you think @stephencelis (or other contributors) ?

Yep. Because we need to push 10.2 changes. I think we will need even 0.12 soon, with Swift 5 support.

Is there anything we can do to make this module swift 5 compatible? Like take current master version?
We are using carthage.

I think we should start from 0.11.6 version. We need PR for this. Update README, versions everywhere. Swift 5 - next step

@ypopovych I've added you as a collaborator after your recent contribution. Would you be willing to shepherd the release? I handed contributor duties off awhile ago but it looks like those contributors have also mostly stepped away from the project.

@stephencelis I will work on this. Will try to get help from other active contributors too. Because right now I'm working on the publishing of 6 our own libraries + PRs to 3 libs :) Will do what I can.
I hope someone can start with PR. If not - will do this tomorrow by myself

Yes please

@christopheblin do you want to start PR with fixes for the new version?

@ypopovych I'm in france and this is nearly the end of the workday for me so I can not start this until tomorrow (at best). Plus, I've never contributed to an iOS Pod so you'll need to explain me what I need to do (I've catched that I must change documentation but I have no clue what else should be done)

@christopheblin in general - version update everywhere (podspec, docs, etc.). Also, we should check Package.swift file (and all files with . in the beginning). Then I will publish a new release (and tag).  We will need @stephencelis only for the push of the new podspec.

@ypopovych  Looking forward. Thanks.

@ypopovych I've created #902 which updates the project to swift 5, and bumps the version to 0.11.6. Please let me know if I missed anything in here!

I will need to move to CoreData and abandon the library. Swift 5 it is a big milestone because for first time is ABI stable.

#902 was merged last week and updated to version 0.11.6. #913 is awaiting review, and will introduce Swift 5 with version 0.12.

Sorry for the delay! I've pushed 0.11.6 to CocoaPods. @ypopovych please shoot me an email with your CocoaPods email address if you'd like access to unblock things in the future.

@christopheblin I pushed 0.12.0 too. With Swift 5.


Media Library

The media library UI is feature complete. Here are the remaining steps:

[x] remove temporary "media" widget and convert image/field widgets to use media library
[x] implement support for asset provider integrations
[x] add support for in-memory test backend
[x] ensure asset filenames are lowercased
[x] add media library support for markdown editor
[x] migrate netlify-auth support to git-gateway (rebase to 0.5.0-beta branch)

Note that the media library will be in place for the editorial workflow, but will not be subject to the editorial workflow process.
Closes #350.
Closes #494.
Closes #229.
Closes #247.

I've got a rebased version of this at https://github.com/dopry/netlify-cms/tree/media-library-ui, you can grab it or cherry pick from there as you need.  I'd send a PR, but my branch is based on master and won't merge.

There is a bug with uploads, see https://github.com/dopry/netlify-cms/commit/37456b12f09ef4c0b086de1d7dd0ce037fd08c3e

The workflow for inserting images is a little convoluted, not sure if there is a good way to streamline, but figured I'd write up some of my notes. some of it we may want to hoist up into #350, unless its something easily fixed in the PR.

Redundant steps when adding an existing image to an entry

click +
click image (Insert Image dialog pops up)
click in dialog to open media library (media library dialog pops up)
select image in media library
click insert (media library dialog closes)
click insert (Insert Image dialog closes)

Note that steps 2,3 and 5,6 are redundant.

You have to specifically check the box to insert media. Its a small hit target, it might be better if clicking the row selected the checkbox.

it would be really cool if just dropping an image on the text editor would upload a piece of content, and insert an image box.

@dopry just saw your feedback, great stuff! I'll look into the upload bug and selection by clicking rows, the rest is probably going to happen under the UI refresh as the redundancies are bigger than just the media library.

Here is a quick dependency/lockfile sync for this PR: https://github.com/netlify/netlify-cms/pull/622.

@Benaiah @tech4him1 @talves this is ready to rock. I went ahead and squashed, too many commits to be super useful anyway. I left the temporary live backend in the example config for review purposes, we'll need to revert that before merging.

@erquhart :raised_hands: awesome! I'll get to reviewing.

I have one thing on the UX that was different than I expected:
If I'm inserting an image, and I upload a new one, I think the checkbox for it should be automatically checked, as it is pretty obvious that that is the one I want.

@erquhart Is there a reason why new assets on an editorial workflow draft get uploaded to the master branch, instead of the one for that new post?

@tech4him1 thanks for the review!

If I'm inserting an image, and I upload a new one, I think the checkbox for it should be automatically checked, as it is pretty obvious that that is the one I want.

I think this makes sense. We could handle it as an improvement post-release, would you be good with that?

Is there a reason why new assets on an editorial workflow draft get uploaded to the master branch, instead of the one for that new post?

Hmm images wouldn't show until the entry published, good point. Need to dig into EW more than I expected for that, good catch.

A post-release improvement sounds fine for that, seeing we are working on UI anyway.

Currently implementing a solution for a gap in the editorial workflow, where deploy previews would not have the latest uploaded assets, by rebasing editorial workflow entries when necessary. This is the last expected fix before the media library is ready to go.

@Benaiah @talves @tech4him1 this is ready again.

Looks like there's still an issue with tree handling, back to WIP.

ALRIGHT ITS REALLY READY FOR REAL NOW GUYS

Note: ignore code style issues unless they're catastrophic. Didn't have the luxury of doing it clean, but improvements will probably come with the UI work prior to 1.0.

This might be for a second-level (after merge) fix, but I wish there was a way so that we didn't have to download the entire full-resolution images when viewing the media library, or at least download them async. If you had a large media library, this could really bog down your computer.

@tech4him1 I've been thinking of, at some point, creating and uploading thumbnails to the metadata branch for this purpose, definitely agree.

@tech4him1 the media library can show all assets, or just images. The image control uses this to ensure non-images aren't available for selection in the image widget, and the messaging is tweaked accordingly.

@erquhart Awesome, that's what I was hoping, just wanted to check.

@erquhart I was testing out the local api against this code to make the necessary method calls, when I saw the above. So, I tested on the preview deploy against the pr-554-backend and saw the same happen.

@talves good catch - we're faking it to reduce API calls, but we need a way to check for this. Can you open a separate issue for it?

https://github.com/netlify/netlify-cms/issues/783

Yarn is having issues, going to hold off on merging until their resolved.

Talking about the naming inconsistencies you were discussing earlier, if this PR title is "Media Library" (and most instances in the code use that same term) why not go with Click here to select an image from the media library and Click here to select an asset from the media library instead of repeating the filtered keyword.
I think even something like Click here to select an image from the library would be better since "select an image" already implies you're allowing the user to only pick image files from the media library.

@hacknug yeah, we need to have more considered verbiage around this, agreed. I'm about to merge this (finally!!), but if you open a separate issue we can discuss from there.


Async support missing for ITelemetryInitializer and ITelemetryProcessor

Async support is missing in ITelemetryInitializer and ITelemetryProcessor.
I want to add some information from the AuthenticationState in my Blazor WebApp.
The AuthenticationStateProvider class has 1 method called GetAuthenticationStateAsync. See Docs.
I would like to do something similar to:
public class TelemetryInitializerEnrichment : ITelemetryInitializer
{
    private readonly AuthenticationStateProvider authenticationStateProvider;

    public TelemetryInitializerEnrichment(AuthenticationStateProvider authenticationStateProvider)
    {
        this.authenticationStateProvider = authenticationStateProvider;
    }

    public async Task InitializeAsync(ITelemetry telemetry)
    {
        if (telemetry is ISupportProperties telemetryWithProperties)
        {
            AuthenticationState authState = await authenticationStateProvider.GetAuthenticationStateAsync();
            bool isAuthenticated = authState.User?.Identity?.IsAuthenticated == true;
            telemetryWithProperties.Properties.Add("IsAuthenticated", isAuthenticated.ToString());
        }
    }
}

@adamashton
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

Hi,
I'm not following an specific documentation but using these as references,
https://learn.microsoft.com/en-us/azure/azure-monitor/app/api-filtering-sampling#addmodify-properties-itelemetryinitializer
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/?view=aspnetcore-7.0#authenticationstateprovider-service
Thanks

@adamashton
Thanks for your feedback! We will investigate and update as appropriate.

@adamashton Thanks for your feedback.
Assigning to content author @AaronMaxwell   for review.


Recommend to install open driver by default for meta packages

Add this to meta packages nvidia-drivers-G06 and nvidia-drivers-minimal-G06
Recommends:  nvidia-open-driver-G06-signed-kmp = %{version}

Also PR #30

done with PR #30