Implement __setitem__ slice for DataProxy (moons 89.17s -> 12.79s, xor 24.42s -> 4.83s)

Implements slice set grad https://github.com/yrmo/cudagrad/issues/59 to speed up SGD https://github.com/yrmo/cudagrad/issues/25

Test CMakeLists don't have pybind11 https://github.com/yrmo/cudagrad/issues/11


[Meta-issue] Increase test coverage

Problem Description
We currently only have a pretty low coverage which makes it hard to refactor certain parts of the code base. We would like to increase the coverage to make it safe for everyone to create PRs and increase the level of safety reviewers feel when accepting PRs.
Our latest code coverage can be seen on CodeCov.io.

File
statements
missing
excluded
coverage

shap/explainers/pytree.py
186
186
0
0%

shap/utils/_keras.py
41
41
0
0%

shap/utils/image.py
81
81
0
0%

shap/plots/_waterfall.py
316
306
0
3%

shap/plots/_benchmark.py
125
119
0
5%

shap/plots/_partial_dependence.py
151
143
0
5%

shap/plots/_decision.py
243
228
0
6%

shap/plots/_violin.py
197
186
0
6%

shap/plots/_force_matplotlib.py
210
195
0
7%

shap/explainers/_kernel.py
426
390
0
8%

shap/plots/_group_difference.py
46
42
0
9%

shap/maskers/_composite.py
99
89
0
10%

shap/explainers/_sampling.py
115
102
0
11%

shap/plots/_heatmap.py
70
62
0
11%

shap/explainers/_linear.py
209
182
3
13%

shap/explainers/other/_maple.py
166
145
0
13%

shap/plots/_utils.py
150
130
0
13%

shap/maskers/_image.py
139
119
0
14%

shap/plots/_image.py
115
99
0
14%

shap/actions/_optimizer.py
55
47
0
15%

shap/plots/_monitoring.py
44
36
0
18%

shap/plots/_embedding.py
31
25
0
19%

shap/explainers/_permutation.py
91
73
0
20%

shap/plots/_scatter.py
445
350
0
21%

shap/explainers/other/_lime.py
45
35
0
22%

shap/plots/_beeswarm.py
521
401
0
23%

shap/explainers/other/_treegain.py
21
16
0
24%

shap/models/_teacher_forcing.py
178
134
0
25%

shap/models/_text_generation.py
100
75
0
25%

shap/explainers/_additive.py
38
27
0
29%

shap/explainers/other/_random.py
28
20
0
29%

shap/models/_topk_lm.py
110
76
0
31%

shap/utils/_clustering.py
120
83
0
31%

shap/datasets.py
154
105
0
32%

shap/utils/_legacy.py
172
103
0
40%

shap/plots/_text.py
619
355
0
43%

shap/plots/colors/_colorconv.py
230
130
0
43%

shap/maskers/_output_composite.py
32
18
0
44%

shap/maskers/_fixed_composite.py
31
17
0
45%

shap/explainers/_partition.py
247
132
0
47%

shap/explainers/_tree.py
1120
543
4
52%

shap/_explanation.py
501
231
0
54%

shap/maskers/_masker.py
13
6
0
54%

shap/plots/_bar.py
221
98
0
56%

shap/utils/_general.py
194
86
0
56%

shap/utils/_masked_model.py
267
115
0
57%

shap/plots/_force.py
240
101
0
58%

shap/explainers/_gradient.py
334
137
0
59%

shap/utils/transformers.py
37
15
0
59%

shap/actions/_action.py
5
2
0
60%

shap/maskers/_fixed.py
10
4
0
60%

shap/explainers/other/_coefficient.py
8
3
0
62%

shap/maskers/_tabular.py
130
49
0
62%

shap/init.py
71
25
0
65%

shap/maskers/_text.py
285
97
0
66%

shap/explainers/_deep/deep_tf.py
486
145
0
70%

shap/explainers/_exact.py
181
51
0
72%

shap/explainers/_explainer.py
240
62
0
74%

shap/links.py
16
4
0
75%

shap/explainers/tf_utils.py
40
9
0
78%

shap/_version.py
11
2
0
82%

shap/utils/_show_progress.py
29
4
0
86%

shap/_serializable.py
127
16
0
87%

shap/plots/init.py
20
2
0
90%

shap/explainers/_deep/deep_pytorch.py
256
23
0
91%

shap/explainers/_gpu_tree.py
30
2
0
93%

shap/explainers/other/_ubjson.py
121
7
0
94%

shap/models/_transformers_pipeline.py
22
1
0
95%

shap/models/_model.py
27
1
0
96%

shap/plots/colors/_colors.py
88
2
0
98%

shap/actions/init.py
2
0
0
100%

shap/explainers/init.py
23
0
0
100%

shap/explainers/_deep/init.py
32
0
0
100%

shap/explainers/_deep/deep_utils.py
12
0
0
100%

shap/explainers/other/init.py
6
0
0
100%

shap/maskers/init.py
9
0
0
100%

shap/models/init.py
6
0
0
100%

shap/plots/_labels.py
1
0
0
100%

shap/plots/colors/init.py
2
0
0
100%

shap/utils/init.py
5
0
0
100%

shap/utils/_exceptions.py
18
0
0
100%

I suggest that we gradually start making PRs that increase the coverage especially of the less well covered files.

@CloseChoice FYI I noticed that several CodeCov uploads have failed recently due to throttling:

['error'] There was an error running the uploader: Error uploading to https://codecov.io: Error: There was an error fetching the storage URL during POST: 429 - {'detail': ErrorDetail(string='Rate limit reached. Please upload with the Codecov repository upload token to resolve issue. Expected time to availability: 1834s.', code='throttled')}

This can be fixed by adding the CodeCov token as a repo secret, which I've asked Scott to do. I send a reminder email a few days ago. Once that's sorted we should get the PR comments again, and we can also update the deprecated CodeCov action.

Hi,
I recently  created a PR #3748 regarding the test coverage for pytree.py but I do realize I should have asked here first whether it was needed, I enjoyed working on the same and if it is okay I would like to work on other tests  too, also this was my first ever PR solving an issue, so I would appreciate any feedback on how to improve, I enjoy working on shap repository and hopefully  could help with more issues in the future.
Sincerely
Siddharth


Quick Idea/Request - Resiliency for the provider

I regularly get proxmox errors such as this during terraform apply:
trying to acquire lock...
trying to acquire lock...
 OK
TASK ERROR: clone failed: can't lock file '/var/lock/pve-manager/pve-storage-local' - got timeout

I believe if terraform just did a quick retry then it would be fine. I've made changes here before, but I think this one is a little over my head. Can anyone help?
https://www.terraform.io/docs/extend/resources/retries-and-customizable-timeouts.html

I have a similar issue, when cloning a bunch of vm's (more than 2) I get this issue:
create full clone of drive ide2 (local:9003/vm-9003-cloudinit.qcow2) trying to acquire lock... TASK ERROR: clone failed: can't lock file '/var/lock/pve-manager/pve-storage-ZFS_Main1' - got timeout
Seems like there is a need to for a wait/retry after receiving a timeout


Updating FirebaseAuth Plugin issue on IOS build

I have a FirebaseAuth plugin within my project coming from Git. I already pulled recent updates as of today for FirebaseAuth plugin and I am encountering some issues.
Steps to Reproduce

Updated Firebase Auth plugin coming from Git repo
Run flutter build ios

Logs
build	29-Jun-2018 03:15:44	â†³
build	29-Jun-2018 03:15:44	    ** BUILD FAILED **
build	29-Jun-2018 03:15:44
build	29-Jun-2018 03:15:44	Xcode's output:
build	29-Jun-2018 03:15:44	â†³
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:80:42: warning: 'UIUserNotificationSettings' is only available on iOS 8.0 or newer [-Wunguarded-availability]
build	29-Jun-2018 03:15:44	        didRegisterUserNotificationSettings:(UIUserNotificationSettings*)notificationSettings;
build	29-Jun-2018 03:15:44	                                             ^
build	29-Jun-2018 03:15:44	    In module 'UIKit' imported from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
build	29-Jun-2018 03:15:44	    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIUserNotificationSettings.h:43:12: note: 'UIUserNotificationSettings' has been explicitly marked partial here
build	29-Jun-2018 03:15:44	    @interface UIUserNotificationSettings : NSObject
build	29-Jun-2018 03:15:44	               ^
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:79:1: note: annotate 'application:didRegisterUserNotificationSettings:' with an availability attribute to silence this warning
build	29-Jun-2018 03:15:44	    - (void)application:(UIApplication*)application
build	29-Jun-2018 03:15:44	    ^
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:95:44: warning: 'UIBackgroundFetchResult' is only available on iOS 7.0 or newer [-Wunguarded-availability]
build	29-Jun-2018 03:15:44	              fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
build	29-Jun-2018 03:15:44	                                               ^
build	29-Jun-2018 03:15:44	    In module 'UIKit' imported from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
build	29-Jun-2018 03:15:44	    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
build	29-Jun-2018 03:15:44	    typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
build	29-Jun-2018 03:15:44	                                ^
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:93:1: note: annotate 'application:didReceiveRemoteNotification:fetchCompletionHandler:' with an availability attribute to silence this warning
build	29-Jun-2018 03:15:44	    - (BOOL)application:(UIApplication*)application
build	29-Jun-2018 03:15:44	    ^
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:140:58: warning: this block declaration is not a prototype [-Wstrict-prototypes]
build	29-Jun-2018 03:15:44	                          completionHandler:(nonnull void (^)())completionHandler;
build	29-Jun-2018 03:15:44	                                                             ^
build	29-Jun-2018 03:15:44	                                                              void
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:148:49: warning: 'UIBackgroundFetchResult' is only available on iOS 7.0 or newer [-Wunguarded-availability]
build	29-Jun-2018 03:15:44	        performFetchWithCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
build	29-Jun-2018 03:15:44	                                                    ^
build	29-Jun-2018 03:15:44	    In module 'UIKit' imported from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
build	29-Jun-2018 03:15:44	    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
build	29-Jun-2018 03:15:44	    typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
build	29-Jun-2018 03:15:44	                                ^
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:147:1: note: annotate 'application:performFetchWithCompletionHandler:' with an availability attribute to silence this warning
build	29-Jun-2018 03:15:44	    - (BOOL)application:(UIApplication*)application
build	29-Jun-2018 03:15:44	    ^
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:53:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseStorage/FirebaseStorage/FirebaseStorage.h:8:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseStorage/FirebaseStorage/FIRStorageTaskSnapshot.h:53:50: warning: 'NSProgress' is only available on iOS 7.0 or newer [-Wunguarded-availability]
build	29-Jun-2018 03:15:44	    @property(readonly, strong, nonatomic, nullable) NSProgress *progress;
build	29-Jun-2018 03:15:44	                                                     ^
build	29-Jun-2018 03:15:44	    In module 'Foundation' imported from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterBinaryMessenger.h:8:
build	29-Jun-2018 03:15:44	    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.3.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSProgress.h:37:12: note: 'NSProgress' has been explicitly marked partial here
build	29-Jun-2018 03:15:44	    @interface NSProgress : NSObject {
build	29-Jun-2018 03:15:44	               ^
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:53:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseStorage/FirebaseStorage/FirebaseStorage.h:8:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseStorage/FirebaseStorage/FIRStorageTaskSnapshot.h:33:12: note: annotate 'FIRStorageTaskSnapshot' with an availability attribute to silence this warning
build	29-Jun-2018 03:15:44	    @interface FIRStorageTaskSnapshot : NSObject
build	29-Jun-2018 03:15:44	               ^
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:70:41: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
build	29-Jun-2018 03:15:44	            signInAnonymouslyWithCompletion:^(FIRAuthDataResult *dataResult, NSError *error) {
build	29-Jun-2018 03:15:44	                                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:441:73: note: passing argument to parameter 'completion' here
build	29-Jun-2018 03:15:44	    - (void)signInAnonymouslyWithCompletion:(nullable FIRAuthResultCallback)completion;
build	29-Jun-2018 03:15:44	                                                                            ^
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:103:41: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
build	29-Jun-2018 03:15:44	                                 completion:^(FIRAuthDataResult *dataResult, NSError *error) {
build	29-Jun-2018 03:15:44	                                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:543:61: note: passing argument to parameter 'completion' here
build	29-Jun-2018 03:15:44	                     completion:(nullable FIRAuthResultCallback)completion;
build	29-Jun-2018 03:15:44	                                                                ^
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:131:37: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
build	29-Jun-2018 03:15:44	                             completion:^(FIRAuthDataResult *dataResult, NSError *error) {
build	29-Jun-2018 03:15:44	                                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:329:57: note: passing argument to parameter 'completion' here
build	29-Jun-2018 03:15:44	                 completion:(nullable FIRAuthResultCallback)completion;
build	29-Jun-2018 03:15:44	                                                            ^
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:188:43: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
build	29-Jun-2018 03:15:44	                                   completion:^(FIRAuthDataResult *dataResult, NSError *error) {
build	29-Jun-2018 03:15:44	                                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
build	29-Jun-2018 03:15:44	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
build	29-Jun-2018 03:15:44	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:486:63: note: passing argument to parameter 'completion' here
build	29-Jun-2018 03:15:44	                       completion:(nullable FIRAuthResultCallback)completion;
build	29-Jun-2018 03:15:44	                                                                  ^
build	29-Jun-2018 03:15:44	    5 warnings and 4 errors generated.
error	29-Jun-2018 03:15:44	Encountered error while building for device.
simple	29-Jun-2018 03:15:44	Failing task since return code of [/Users/nbonita/SOFTWARES/bamboo-home/temp/MDS-UP-JOB1-297-ScriptBuildTask-5830017953596687174.sh] was 1 while expected 0
simple	29-Jun-2018 03:15:44	Finished task 'Build IOS' with result: Failed

Flutter Doctor
[✓] Flutter (Channel dev, v0.4.4, on Mac OS X 10.13.4 17E199, locale en-PH)
    • Flutter version 0.4.4 at /Users/macbook/Documents/flutter
    • Framework revision f9bb4289e9 (7 weeks ago), 2018-05-11 21:44:54 -0700
    • Engine revision 06afdfe54e
    • Dart version 2.0.0-dev.54.0.flutter-46ab040e58

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.0-rc1)
    • Android SDK at /Users/macbook/Library/Android/sdk
    • Android NDK at /Users/macbook/Library/Android/sdk/ndk-bundle
    • Platform android-27, build-tools 28.0.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.3, Build version 9E145
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.2

[✓] Android Studio (version 2.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] IntelliJ IDEA Community Edition (version 2017.2.5)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 19.1
    • Dart plugin version 172.4343.25

[!] VS Code (version 1.17.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Dart Code extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.dart-code

[!] Connected devices
    ! No devices available

Pod version
1.5.2

Have you tried pod update in ios/?

Already did pod update
but i think the number of errors and warnings didn't change
build	29-Jun-2018 19:21:00	    === BUILD TARGET firebase_auth OF PROJECT Pods WITH CONFIGURATION Release ===
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/FB-Signin-Plugin/ios/Classes/FacebookSignInPlugin.m:1:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/FB-Signin-Plugin/ios/Classes/FacebookSignInPlugin.h:1:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:140:58: warning: this block declaration is not a prototype [-Wstrict-prototypes]
build	29-Jun-2018 19:21:00	                          completionHandler:(nonnull void (^)())completionHandler;
build	29-Jun-2018 19:21:00	                                                             ^
build	29-Jun-2018 19:21:00	                                                              void
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/FB-Signin-Plugin/ios/Classes/FacebookSignInPlugin.m:23:34: warning: incompatible pointer types sending 'FacebookSignInPlugin *' to parameter of type 'UIViewController *' [-Wincompatible-pointer-types]
build	29-Jun-2018 19:21:00	                  fromViewController:self
build	29-Jun-2018 19:21:00	                                     ^~~~
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/FB-Signin-Plugin/ios/Classes/FacebookSignInPlugin.m:3:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/FBSDKLoginKit/FBSDKLoginKit.h:21:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/FBSDKLoginKit/FBSDKLoginButton.h:23:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/FBSDKLoginKit/FBSDKLoginManager.h:158:54: note: passing argument to parameter 'fromViewController' here
build	29-Jun-2018 19:21:00	                  fromViewController:(UIViewController *)fromViewController
build	29-Jun-2018 19:21:00	                                                         ^
build	29-Jun-2018 19:21:00	    2 warnings generated.
build	29-Jun-2018 19:21:00	    === BUILD TARGET firebase_core OF PROJECT Pods WITH CONFIGURATION Release ===
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:80:42: warning: 'UIUserNotificationSettings' is only available on iOS 8.0 or newer [-Wunguarded-availability]
build	29-Jun-2018 19:21:00	        didRegisterUserNotificationSettings:(UIUserNotificationSettings*)notificationSettings;
build	29-Jun-2018 19:21:00	                                             ^
build	29-Jun-2018 19:21:00	    In module 'UIKit' imported from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
build	29-Jun-2018 19:21:00	    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIUserNotificationSettings.h:43:12: note: 'UIUserNotificationSettings' has been explicitly marked partial here
build	29-Jun-2018 19:21:00	    @interface UIUserNotificationSettings : NSObject
build	29-Jun-2018 19:21:00	               ^
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:79:1: note: annotate 'application:didRegisterUserNotificationSettings:' with an availability attribute to silence this warning
build	29-Jun-2018 19:21:00	    - (void)application:(UIApplication*)application
build	29-Jun-2018 19:21:00	    ^
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:95:44: warning: 'UIBackgroundFetchResult' is only available on iOS 7.0 or newer [-Wunguarded-availability]
build	29-Jun-2018 19:21:00	              fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
build	29-Jun-2018 19:21:00	                                               ^
build	29-Jun-2018 19:21:00	    In module 'UIKit' imported from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
build	29-Jun-2018 19:21:00	    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
build	29-Jun-2018 19:21:00	    typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
build	29-Jun-2018 19:21:00	                                ^
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:93:1: note: annotate 'application:didReceiveRemoteNotification:fetchCompletionHandler:' with an availability attribute to silence this warning
build	29-Jun-2018 19:21:00	    - (BOOL)application:(UIApplication*)application
build	29-Jun-2018 19:21:00	    ^
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:140:58: warning: this block declaration is not a prototype [-Wstrict-prototypes]
build	29-Jun-2018 19:21:00	                          completionHandler:(nonnull void (^)())completionHandler;
build	29-Jun-2018 19:21:00	                                                             ^
build	29-Jun-2018 19:21:00	                                                              void
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:148:49: warning: 'UIBackgroundFetchResult' is only available on iOS 7.0 or newer [-Wunguarded-availability]
build	29-Jun-2018 19:21:00	        performFetchWithCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;
build	29-Jun-2018 19:21:00	                                                    ^
build	29-Jun-2018 19:21:00	    In module 'UIKit' imported from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Target Support Files/firebase_auth/firebase_auth-prefix.pch:2:
build	29-Jun-2018 19:21:00	    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:76:29: note: 'UIBackgroundFetchResult' has been explicitly marked partial here
build	29-Jun-2018 19:21:00	    typedef NS_ENUM(NSUInteger, UIBackgroundFetchResult) {
build	29-Jun-2018 19:21:00	                                ^
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/Flutter.h:37:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterAppDelegate.h:11:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterPlugin.h:147:1: note: annotate 'application:performFetchWithCompletionHandler:' with an availability attribute to silence this warning
build	29-Jun-2018 19:21:00	    - (BOOL)application:(UIApplication*)application
build	29-Jun-2018 19:21:00	    ^
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:53:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseStorage/FirebaseStorage/FirebaseStorage.h:8:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseStorage/FirebaseStorage/FIRStorageTaskSnapshot.h:53:50: warning: 'NSProgress' is only available on iOS 7.0 or newer [-Wunguarded-availability]
build	29-Jun-2018 19:21:00	    @property(readonly, strong, nonatomic, nullable) NSProgress *progress;
build	29-Jun-2018 19:21:00	                                                     ^
build	29-Jun-2018 19:21:00	    In module 'Foundation' imported from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/Flutter/Flutter/FlutterBinaryMessenger.h:8:
build	29-Jun-2018 19:21:00	    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.3.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSProgress.h:37:12: note: 'NSProgress' has been explicitly marked partial here
build	29-Jun-2018 19:21:00	    @interface NSProgress : NSObject {
build	29-Jun-2018 19:21:00	               ^
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:53:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseStorage/FirebaseStorage/FirebaseStorage.h:8:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseStorage/FirebaseStorage/FIRStorageTaskSnapshot.h:33:12: note: annotate 'FIRStorageTaskSnapshot' with an availability attribute to silence this warning
build	29-Jun-2018 19:21:00	    @interface FIRStorageTaskSnapshot : NSObject
build	29-Jun-2018 19:21:00	               ^
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:70:41: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
build	29-Jun-2018 19:21:00	            signInAnonymouslyWithCompletion:^(FIRAuthDataResult *dataResult, NSError *error) {
build	29-Jun-2018 19:21:00	                                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:441:73: note: passing argument to parameter 'completion' here
build	29-Jun-2018 19:21:00	    - (void)signInAnonymouslyWithCompletion:(nullable FIRAuthResultCallback)completion;
build	29-Jun-2018 19:21:00	                                                                            ^
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:103:41: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
build	29-Jun-2018 19:21:00	                                 completion:^(FIRAuthDataResult *dataResult, NSError *error) {
build	29-Jun-2018 19:21:00	                                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:543:61: note: passing argument to parameter 'completion' here
build	29-Jun-2018 19:21:00	                     completion:(nullable FIRAuthResultCallback)completion;
build	29-Jun-2018 19:21:00	                                                                ^
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:131:37: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
build	29-Jun-2018 19:21:00	                             completion:^(FIRAuthDataResult *dataResult, NSError *error) {
build	29-Jun-2018 19:21:00	                                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:329:57: note: passing argument to parameter 'completion' here
build	29-Jun-2018 19:21:00	                 completion:(nullable FIRAuthResultCallback)completion;
build	29-Jun-2018 19:21:00	                                                            ^
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:188:43: error: incompatible block pointer types sending 'void (^)(FIRAuthDataResult *__strong, NSError *__strong)' to parameter of type 'FIRAuthResultCallback _Nullable' (aka 'void (^)(FIRUser * _Nullable __strong, NSError * _Nullable __strong)')
build	29-Jun-2018 19:21:00	                                   completion:^(FIRAuthDataResult *dataResult, NSError *error) {
build	29-Jun-2018 19:21:00	                                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.m:5:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/firebase_plugins/firebase_auth/ios/Classes/FirebaseAuthPlugin.h:7:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Private/Firebase/Firebase.h:13:
build	29-Jun-2018 19:21:00	    In file included from /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FirebaseAuth.h:4:
build	29-Jun-2018 19:21:00	    /Users/nbonita/SOFTWARES/bamboo-home/xml-data/build-dir/MDS-UP-JOB1/ios/Pods/Headers/Public/FirebaseAuth/FirebaseAuth/FIRAuth.h:486:63: note: passing argument to parameter 'completion' here
build	29-Jun-2018 19:21:00	                       completion:(nullable FIRAuthResultCallback)completion;
build	29-Jun-2018 19:21:00	                                                                  ^
build	29-Jun-2018 19:21:00	    5 warnings and 4 errors generated.
error	29-Jun-2018 19:21:00	Encountered error while building for device.
simple	29-Jun-2018 19:21:00	Failing task since return code of [/Users/nbonita/SOFTWARES/bamboo-home/temp/MDS-UP-JOB1-300-ScriptBuildTask-4595063734247350563.sh] was 1 while expected 0
simple	29-Jun-2018 19:21:00	Finished task 'Build IOS' with result: Failed

I believe one of the suggestions should fix the issue
https://github.com/flutter/flutter/issues/18340#issuecomment-396457808
https://github.com/flutter/flutter/issues/17457#issuecomment-405117816
https://github.com/flutter/flutter/issues/17469#issuecomment-391976660
https://github.com/flutter/flutter/issues/17721#issuecomment-390259983

how to fix it

I've got the same issue and no one comment helped me
This is the issue

@artAst
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/775. Any further collaboration will be done there.


Testing the bot

Description:
Describe in a couple of sentences what this PR adds
JIRA: (Optional)
XXX-XXXX
Merge checklist:

[ ] All reviewers approved
[ ] CI build is green
[ ] If adding new checks, followed how_tos/0001-adding-new-checks.rst
[ ] Changelog record added (if needed)
[ ] Documentation updated (not only docstrings) (if needed)
[ ] Commits are squashed

Thanks for the pull request, @nedbat-test-external! I've created OSPR-6363 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.
:warning: We can't start reviewing your pull request until you've submitted a     signed contributor agreement     or indicated your institutional affiliation. Please see the CONTRIBUTING     file for more information.     If you've signed an agreement in the past, you may need to re-sign.  See     The New Home of the Open edX Codebase     for details.

@nedbat-test-external Even though your pull request wasn’t merged, please take a moment  to answer a two question survey so we can improve your experience in the future.


Bundler warning

This message appears when integrating OpenID token proxy in a Rails application and running the server or console:

Bundler is using a binstub that was created for a different gem.
This is deprecated, in future versions you may need to bundle binstub openid-token-proxy to work around a system/bundle conflict.

Any ideas?

As explained here it seems to be related to the binstubs in this repo in combination with the following gemspec line:
spec.executables = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }

Covered by 3fcf731370309b212912782e173ca34e075cbb16.


Could not find module 'SDWebImageSwiftUI' for target 'arm64-apple-ios-simulator'; found: x86_64-apple-ios-simulator, x86_64

Any context？I even don't knwo what's your installation way, SwiftPM ? Carthage ? CococaPods ?
And, SDWebImageSwiftUI do not promise any Binary API compatible. If you face any issue related to binary framework, try recompile and check

Duplicated for #149


Browser use

Hi there,
watched your GrCon presentation online, great work! In your presentation you mention

Rendered frame can be attached to any window (Qt, Cocoa, MTKView, etc)
TL;DR: It’s easy to use on iOS, Android, macOS, or even a browser

What is the recommended way for visualizing on a browser? websockets? wasm? any examples show casing how to use?

Hey, thanks for creating this issue! The current branch can't be run on the browse. This is because I added some new features that WebGL wouldn't be able to support. To solve this, I'm planning to write a new WebGPU backend for browsers. The problem is that WebGPU isn't available for Chrome and Firefox as of now. I'm hoping they will make it available by January 2023.
Regarding the architectural question, CyberBrowser worked using WebAssembly with multi-threading enabled. The communication with the SDR was made by a LibUSB to WebUSB wrapper that I wrote some time ago. That repository also has some examples, but it requires a patched version of Emscripten to work (due to some synchronization requirements imposed by WebUSB limitations).

@luigifcruz Hey Luigi, had a chance to revisit this repo after seeing your recent tweet about running CyberEther on ios. (great stuff btw!) In your previous reply you mention CyberBrowser. Is this the radio-blast stuff here or is it a completely separate project?

Hey, @karatemir! It's a different project. I wrote it as a proof of concept for my WebUSB to libusb translation layer. It did work well but there are limitations. I'm planning to start the WebGPU backend for CyberEther as soon as the technology is widely available and the limitations (multi-thread) are solved.


How can I generate SBOM for a docker image?

I want to generate SBOM for a docker image, but the command line requires multiple parameters according to this sample,  which looks complicated. Is there a simple way to generate SBOM for a docker image like Docker Sbom?

The easiest way I've found is ./sbom-tool generate -di <imageref> -b ./foo -pn bar -pv 0.1 -bc ./foo where foo is an empty directory, and pn=bar is a namespace for the generated SBOM.

@bureado has the right answer, that is the way to generate SBOMs using our tool.
Although, baz is not a valid URI, we need a valid URI as a parameter for the -nsb parameter.


remove extra query in non-revision updates

Partially fixes #737
The remaining updates (Deployment, Spec) have to maintain revisions and will require different and more complex logic to handle in a similar manner, so I'll submit that in a separate PR so we can evaluate that approach separately.

The test timeout seems unrelated to this PR. Needs investigation, but possibly db lock contention?


feat(shwap): Add axis roots to Accessor

Add axis roots to all Accessor implementations. It will allow server side to handle namespace requests without the need to know exact rowIdxes beforehand.

Codecov Report
Attention: Patch coverage is 76.72414% with 27 lines in your changes missing coverage. Please review.

Please upload report for BASE (shwap@d807843). Learn more about missing BASE report.

Files
Patch %
Lines

store/file/ods.go
80.39%
6 Missing and 4 partials :warning:

share/new_eds/close_once.go
0.00%
4 Missing :warning:

share/new_eds/proofs_cache.go
69.23%
2 Missing and 2 partials :warning:

store/cache/noop.go
0.00%
3 Missing :warning:

share/new_eds/nd.go
50.00%
1 Missing and 1 partial :warning:

share/new_eds/rsmt2d.go
60.00%
1 Missing and 1 partial :warning:

share/root.go
0.00%
1 Missing :warning:

store/store.go
83.33%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff            @@
##             shwap    #3586   +/-   ##
========================================
  Coverage         ?   47.80%
========================================
  Files            ?      316
  Lines            ?    18651
  Branches         ?        0
========================================
  Hits             ?     8917
  Misses           ?     8598
  Partials         ?     1136

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


Create a ESP32 focused options file that lives on top of the Arduino …

…template
This removes the wire->end() function
Fixes #62
Fixes #183

Cannot reproduce failing unit test. Merging.


Disable Wiki

Please disable Wiki on this repo, you're wasting a lot of internet because we have to transfer the text Wiki and the icon next to it.
<a href="/neonichu/xcode-install/wiki" class="js-selected-navigation-item reponav-item" data-hotkey="g w" data-selected-links="repo_wiki /neonichu/xcode-install/wiki">
      <svg aria-hidden="true" class="octicon octicon-book" height="16" role="img" version="1.1" viewBox="0 0 16 16" width="16"><path d="M2 5h4v1H2v-1z m0 3h4v-1H2v1z m0 2h4v-1H2v1z m11-5H9v1h4v-1z m0 2H9v1h4v-1z m0 2H9v1h4v-1z m2-6v9c0 0.55-0.45 1-1 1H8.5l-1 1-1-1H1c-0.55 0-1-0.45-1-1V3c0-0.55 0.45-1 1-1h5.5l1 1 1-1h5.5c0.55 0 1 0.45 1 1z m-8 0.5l-0.5-0.5H1v9h6V3.5z m7-0.5H8.5l-0.5 0.5v8.5h6V3z"></path></svg>
      Wiki
</a>

This not only wastes Internet itself, but also energy on the user's mac to render it, and also GitHub's servers.

Can confirm that all three Internet tubes are clogged due to this excess resource usage.

Yes this is for sure showing up as a spike in a ops team graph :chart_with_upwards_trend:

The wiki contains loads of important information.

Buuuh!!! :cry:


lb_3

Closes #135

Looks good! The only thing I might change is making the line widths of the land borders/contours thinner so they are less distracting, but that is up to you.

I decided to make the coastlines a bit transparent to make them less distracting. I think making them thinner would have reduced legibility too much. What do you think? @clairefio


How to disable the Farcaster middleware?

Hi, it seems that the farcaster middleware runs even tho I am only using the xmtp one. Is there a way to disable the farcaster middleware totally?
I can see in my server logs:
farcaster middleware: could not decode farcaster message from payload, calling next.
and my code is:
import { createFrames } from "frames.js/next";
import { openframes } from "frames.js/middleware";
import { getXmtpFrameMessage, isXmtpFrameActionPayload } from "frames.js/xmtp";

export const frames = createFrames({
  basePath: "/frames",
  initialState: {},
  middleware: [
    openframes({
      clientProtocol: {
        id: "xmtp",
        version: "2024-02-09",
      },
      handler: {
        isValidPayload: (body) => isXmtpFrameActionPayload(body),
        getFrameMessage: async (body) => {
          if (!isXmtpFrameActionPayload(body)) {
            return undefined;
          }
          const result = await getXmtpFrameMessage(body);

          return { ...result };
        },
      },
    }),
  ],
});

Hi, this is expected as the farcaster middleware is built-in at this stage - your xmtp middleware should work as expected


#1634 - Attach Condition to Optional Output

Checklist

[x] manage.py test passes
[x] tests are included

Affected app(s)

job
recipe

Description of change
Actually copy the input interface of a condition and update the copy so we're not modifying the original input interface and making everything required.  Also fixed a bug in setting the json output for a job in the post steps

Decided I should add a test for getting json outputs


fix missing closing brackets in release

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3381

Relevant Lines:
5253

💛  - Coveralls


Programmatically open picture-in-picture PIP mode

Hi. I am currently using MuxPlayer and noticed that there is a Picture-in-Picture button that when clicked puts the video in a smaller contained window. This is great. I'd like to programmatically put into picture-in-picture mode when they click a button. I have not been able to find PIP captured in documentation.

@sharpsteelsoftware1 did that work for you? I'm going to go ahead and close this because I tested it out and it worked for me


Gradle multi-project detection doesn't work if script needs a property

The multi-project detection doesn't work if the gradle script needs a porperty e.g. the password of a repository.
Problem in case of the gradle.ps1 - TFS 2015 Update 3
Line 104 doesn't use the $options property, therefore execution of "gradlew properties" throws an exception and the build fails with:
2016-11-07T10:58:57.7644413Z ##[debug]Running batch script.
2016-11-07T10:58:57.7800682Z ##[debug]   Path: D:\Agents\2_work\1\s\Desktop\gradlew
2016-11-07T10:58:57.7800682Z ##[debug]   Arguments: properties
2016-11-07T10:58:57.7800682Z ##[debug]   WorkingFolder: D:\Agents\2_work\1\s\Desktop
2016-11-07T10:59:02.1863281Z ##[error]System.Exception: Unexpected exit code received from batch file: 1
2016-11-07T10:59:02.1863281Z ##[error]   at Microsoft.TeamFoundation.DistributedTask.Task.Internal.PowerShell.InvokeBatchScriptCmdlet.ProcessRecord()
2016-11-07T10:59:02.1863281Z ##[error]   at System.Management.Automation.CommandProcessor.ProcessRecord()
Output of the "gradlew properties" script without the options
FAILURE: Build failed with an exception.

Where:
Build file 'D:\Agents\2_work\1\s\Desktop\build.gradle' line: 11

What went wrong:
A problem occurred evaluating root project 'enterprise'.

No such property: deploymentPassword for class: org.gradle.api.internal.initia
lization.DefaultScriptHandler

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.

BUILD FAILED
Total time: 21.094 secs
My multi-project script looks like the following:
buildscript {
repositories {
maven{
url "http://.../nexus/repository/maven-public/"
credentials {
username System.getenv('DEPLOYMENT_USERNAME') ?: deploymentUsername
password deploymentPassword
}
}
}
dependencies { classpath 'com.google.protobuf:protobuf-gradle-plugin:0.7.6' }
}
...
options are -PdeploymentPassword myPassword

@shruda I guess we need to pass the options while calling gradlew properties?
Correct me on that. If that's the case, will help in fixing it internally for you and make the appropriate fix in the task too.

Hi nigurr,
yes that's right. The options must be added to the gradlew properties call.
Best Regards,
Steve

@shruda do you have any open source project to try it out. It will be helpful to test it out.

@nigurr  I've created a multimodule for you which helps you to reproduce the issue.
https://github.com/shruda/bugreports/tree/master/vsts-tasks/3037/multimodule
Gradle wrapper: vsts-tasks/3037/multimodule/gradlew
Options: -PmyProperty=MyValue
Tasks: build
Working directory: vsts-tasks/3037/multimodule
If it works, then you will see the following output at the log:
2016-11-17T09:49:57.0981760Z multimodule: The value of myProperty is 'test'
2016-11-17T09:49:57.2231789Z module-one: The value of myProperty is 'test'
2016-11-17T09:49:57.2231789Z module-two: The value of myProperty is 'test'
if not ...
2016-11-17T09:49:11.5043084Z ##[error]Unexpected exit code received from batch file: 1
2016-11-17T09:49:17.9261287Z ##[error]> multimodule: myProperty isn't available!
The second error is only visible because of my hasProperty check in the build.gradle file.

Thanks for the contribution. I will def take this to fix this issue.

@shruda I just looked at code. indeed we are passing options to properties.
You need to pass properties -PmyPassword=abcxyz -PmyUsername=123456 in gradle task options field.
Correct me If I am missing something

I see - vbossica added it.
https://github.com/Microsoft/vsts-tasks/commit/1b3dbf42de2fcb933cb8d46518b56da2b70916a2
Which version will include this fix? At the moment I'm using TFS 2015 Update 3.

@shruda It should be available in Dev15 TFS

OK perfect thanks!


Restructure Animation Component/System

In the ECS paradigm components are designed to only store data, systems are supposed to manipulate this data. The current animation implementation has logic spread between the component and its related system.

Ok, having spend even more time with animation.go I can see what you were trying to achieve there.
The main issue is with increment() method which obviously processes data.
However, I am slowly coming to some conclusions how I would like this to look like:
For me

We should delete an actual Sprite type (legacy like you said)
We should seriously consider renaming Bounds to Sprite as bounds is form of a sprite. I am also fine to keep this Bounds if this is more natural for you. I am torn myself, as plain texture is also a kinda sprite.
We should provide Render method for Bounds (Sprite) and in future Draw if the code base is refactored to use Draw everywhere. I already have it working locally - but without camera
AnimationComponent apart from data it has (with some tweaks) should take as part of construction process - simply an array of Bounds. Array is already indexed. Later through methods or constructors we can pick which indexes are part of which frames. This gives us enormous flexibility, Spriteheet is today a very specific and concrete implementation. I can imagine other implementation based on some ripped sprite sheets from the internet, which do not conform to the contract (like Hero.png example). Since AnimationComponent does not have to know much about actual concrete Spritesheet type and implementation (which assumes too many things) we can simply provide other implementations of Sprite collections, like Spritemap.

To understand me better you can have a look at spritesheet I found on the internet:
http://www.spriters-resource.com/game_boy_advance/namcomuseum/sheet/22731/
This one is far from predictable patterns despite what it seems and Spritesheet freaks out on this even with my various tweaks. With such a spritemap the only option may be to manually define bounds and then form a number of array bounds from them that can be animated.
Thoughts?
PS.
I miss what is this dt, which is passed in update method and also what u,v mean in Region. Help appreciated.

@matiwinnetou IMO Region != Sprite. A Region represents part of a Texture.
Yes. Regions should be Renderable, so we can stop this kind of situation.

Sure. Structure the AnimationComponent however you want. As long as no logic is performed on it. Logic should be performed on the AnimationSystem.

dt is delta time, the change in time since the last frame was rendered... Useful for computing movement and stuff :)

Close please.


Can not run on Apple M1 silicon

We've been using this library for a while now and it works very well.  I just got a new Macbook Pro 2021 and getting an issue using this library.
Just wondering if you know any issues using this library on an M1 Macbook?
This is the error I get
Docker Chromium: Setting Ubuntu to use default mirror for packages...
Docker Chromium: Setting Chromium download host to https://storage.googleapis.com...
Docker Chromium: Setting Chromium flags to –ignore-certificate-errors...
Docker Chromium: Setting Chromium version to rev-901912...
Docker Chromium: Building Docker image...
Error: Jest: Got error running globalSetup - /monorepo/node_modules/jest-puppeteer-docker/src/setup.js, reason: Docker Chromium: Failed to build Docker image

Internal Error:

Error: Command failed: docker-compose -f "/monorepo/node_modules/docker-chromium/docker/docker-compose.yml" build --build-arg CHROMIUM_ADDITIONAL_ARGS="–ignore-certificate-errors" --build-arg CHROMIUM_DOWNLOAD_HOST=https://storage.googleapis.com --build-arg CHROMIUM_REVISION=901912 --build-arg USE_CLOSEST_UBUNTU_MIRROR=false --pull chromium
Building chromium
#1 [internal] load build definition from Dockerfile
#1 sha256:803b5310a114036fdf92f0a543e55e2b83c8178d3b8d958bc1e3a6efb5a3b5af
#1 transferring dockerfile: 37B done
#1 DONE 0.0s

Hey @cuongluu8, you could try with the latest Chromium revision by setting this env var: PUPPETEER_CHROMIUM_REVISION=938248

That didn't work.  I think the issue is actually in https://github.com/gidztech/docker-chromium as this image is can not be built on M1 silicon.

We were having the same issue and ended up using  jest-puppeteer directly using this image https://hub.docker.com/r/browserless/chrome
Our jest-puppeteer.config.js looked like this
const { config } = require('./package.json');
module.exports = {
  launch: {
    dumpio: true,
    headless: process.env.HEADLESS !== 'false',
    product: 'chrome',
  },
  browserContext: 'default',
  connect: { browserWSEndpoint: `ws://localhost:${config.dockerChromePort}` },
  server: {
    command: `http-server -p ${config.visualTestPort} ./storybook-static`,
  },
};

Hope it helps someone.


Additional field for bonus points validity + link to association rules

Grüezi!
It would be great to have the following in the summit pop-up / info page:

An extra field or hoover tip with the bonus point validity period,

A direct link to the association's rules page.

Vielen Dank!

Hello,
I've had a look and found the following:

Bonus validity period: It seems that the only way to get this is from the database API (https://api-db.sota.org.uk/admin/summit_history?summitID=xxx), but then one needs to look up the summit ID first. The regular API (https://api2.sota.org.uk/api/summits/3Y/BV-001) that SOTLAS uses does not return it. I assume if the bonus validity period was shown on https://summits.sota.org.uk/ (currently it's not), then they would make the API return it as well :wink:
Association rules: The PDF filenames can be obtained from https://api2.sota.org.uk/api/associations/XX, but many are hopelessly outdated or missing altogether, and it seems that the MT wants to move away from PDF-based ARMs to something generated from the database anyway.

Manuel HB9DQM


Added elevation option

The elevation option allows setting the elevator style on android and emulates this setting on ios.
This is inline with the material design guidelines.
It can be hard to notice the difference on the examples but if the list is moved down a bit, you can see the effect.

Hi, thanks!
Could you add a screenshot? That would be helpful :)

Here are 4 screenshots showing varying values of elevation

Thanks again, and sorry for the late response.
I'll review it this weekend. 🏄🏻♂

Looks very good! Thanks a lot 👍

Included in v5.6.2.


Add more runtimes and tools

In the bustling world of cloud-native computing, container technologies have emerged as a powerhouse for building, shipping, and running applications in a highly portable and scalable manner. As developers continue to work with containers, having the right set of tools can make all the difference. Here's a reference for some helpful container tools that have been shaping the DevOps and cloud ecosystems.
While this list is far from complete, these tools form a strong foundation for container management, deployment, and orchestration.

Add a lot of tools, container specs and a list of kubernetes distributions.


crypto/cipher: easy optimisations to xorBytes

The function crypto/cipher.xorBytes implements the XOR operations between slices of bytes, and is heavily used by encryption in CTR mode.  The version in the stdlib has seen a significant amount of optimisation, but some easy optimisations are missing:

The variable supportUnaligned in xor_generic.go should be set for GOARCH equal to arm64.
Said variable sohould be set for GOARCH equal to ARM and GOARM equal to 6 or 7 (but not 5).
When supportsUnaligned is not set, the fast version should still be called when both src and dst are multiples of wordSize (this actually happens fairly often, e.g. when encrypting a freshly allocated slice);
When supportsUnaligned is not set, and src and dst are equal modulo wordSize, then the initial bytes should be xored and then the fast version called on the rest of the array;
Ideally, there should be a NEON implementation for ARMv7.

Points 1 through 3 are fairly trivial, and would bring a significant part of the benefit.  This is related to #53021.

@jech - point 1 is unnecessary because arm64 is excluded via the go:build line in xor_generic.go (due to the presence of the arm64 neon assembly implementation).
But an emphatic yes to the other points. Especially point 2 where we are currently leaving significant gains on the table on a performance critical function on ARMv6/7 where unaligned access is OK.
There are frequent posts regarding golang’s slow crypto performance on arm32 and this would be a low hanging fruit change with big gains.

cc @bradfitz

See also  #35381.

@bcmills / @bradfitz / @jech - I have written both NEON and non-NEON versions of xorBytes for 32-bit ARM. The performance increase over the 'slow' version in xor_generic.go is significant, between 4X and 20X.
Given that 32-bit ARM remains one of the most popular IoT device platforms, it's a shame that 32-bit ARM is the sole unoptimised platform for 32-bit ARM in the crypto library for xorBytes, which can be a bottleneck function for crypto.
So, I would be very happy to create a PR here to contribute optimised 32-bit NEON and non-NEON ARM implementations of xorBytes. This could be a significant deal for crypto performance in general on 32-bit ARM. But I would appreciate a signal first that there is the appetite to accept such a PR, so it does not end up in /dev/null.


NaN variance with a or b as infinity

Hi,
It seems that when a or b are defined as math.inf, the variance becomes undefined.
Unless I am missing something, the variance should still be well defined for these cases
For example, comparing to the equivalent scipy function scipy.stats.truncnorm:

scipy.stats.truncnorm(a=-0.5, b=math.inf, loc=7500, scale=15000) gives variance 1.1E+08
TruncatedNormal(a=-0.5, b=math.inf, loc=7500, scale=15000) gives variance NaN

I believe it comes down to the line
self._lpbb_m_lpaa_d_Z = (self._little_phi_b * self.b - self._little_phi_a * self.a) / self._Z

Little phi is correctly calculated as zero for the infinite limit, but 0 * math.inf results in a NaN.
As a quick fix, I replaced infinities with zeros in the line above, for example:
self._lpbb_m_lpaa_d_Z = (self._little_phi_b * (self.b if self.b != math.inf else 0) - self._little_phi_a * (self.a if self.a != math.inf else 0)) / self._Z

Hi, thanks for spotting this,
Is it handled similarly in scipy? If yes, could you perhaps file a pull request?
Thanks,
Anton

I'm not familiar enough with scipy to be sure how it internally handles cases like this, but this fix yields the same behaviour as far as I've tested. I'll submit a pull request.

Fixed in #5


Support block grid as well as block list

So far this project has only worked with the block list editor in Umbraco. This PR adds support for the block grid editor, opening up more layout possibilities for future projects.
It is at parity with block list support. Filtering and overriding blocks is fully supported.

Add a new demo page for the block grid in the example app, and block grids on some other pages (these will be further revised as documentation is updated in following PRs). Renames the existing BlockList example page to FilterAndOverrideBlocks which applies to both block editors.

Filters now use an interface that is common to block list items and block grid items. Views for each component also use the interface.

Some namespaces and classes change from BlockList to Blocks

Backoffice views are configured so that the backoffice interface is somewhat WYSIWIG. More can be done on this, but a good level of support is there for v1. govuk-umbraco-rich-text-editor.css becomes govuk-umbraco-backoffice.css and now supports this additional functionality. This shows part of the backoffice view of the example page:

There is a lot more unit testing of FindBlock and FindBlocks extension methods. However the number of overloads is reduced to only support overridable blocks. These extension methods now run on interfaces that are common to both block list and block grid, but supporting both the base types and the overridable types meant having to use a long syntax to specify the overridable type with every call to avoid ambiguity. With ModelsBuilder now building overridable types by default it's very rare to encounter the base types (I couldn't find an example in our current applications) so I removed the base type support.

Task list summary logic moves out of the BlockList.cshtml view and into an ActionFilter that can handle block lists or block grids

RemoveSettingsErrorsActionFilter deals with spurious validation errors that are thrown up by the block grid. This used to happen for the block list but got fixed, so I have revived the old code.

There is a new 'Image' block in the TPR-specific project which is copied from the Umbraco example code for block grid, and allows adding images to the page.

Block grid support is added to the testing project.

Closing PR to create smaller PRs instead with the same content.


SVG Elements causing a (signal: 9, SIGKILL: kill) at compile time

Hello,
While building a rust UI through markup a code signal 9 appears at compile time. This is due to an over usage of the ram during compilation. Is there any way to fix it? It seems to happen when too many elements are present, but works fine on its nodejs based server.
Any idea or solution to counter this issue, and if so would it be possible to improve it?
Thank you very much.

Hi @LucasStill. Can you post a complete sample template that uses too much memory for you? Are you able to compile other Rust crates fine on the same machine?


ghost: update to the latest jwt library RC

A number of the APIs have been refactored, correct these and bump the
dep.

Thanks for the solution, it's extremally usefull and I hope author will merge it, anyway friendly reminder for others: You can use "replace" in your go.mod in order to use this lib with Phillips breanch

Thanks for submitting this @philips, and sorry for missing it before! This looks great -- merging now.


Added support for aoc-session and improved the docs

See DavidAnson.vscode-markdownlint VS Code extension.
See shieldify crate.

Thanks for submitting a PR! I didn't expect this project to get any attention.
I assume you would like to use it this year but want it to be compatible with aoc-session? I've allowed the .session file to contain the session= header, so they should be compatible now. I've also added badges, but I didn't deem the remainder of the changes you made in this PR necessary at the moment. Thanks regardless!


Segfault when accessing signature of a function with optional fusedtype memoryview argument

foo.pyx:
#cython: binding=True
cimport cython

def foo(cython.floating[:] x=None):
    return x

$ cythonize -b foo.pyx && PYTHONFAULTHANDLER=1 pydoc foo
running build_ext
Fatal Python error: Segmentation fault

Current thread 0x00007f8776e03700 (most recent call first):
  File "/usr/lib/python3.5/inspect.py", line 1803 in _signature_is_functionlike
  File "/usr/lib/python3.5/inspect.py", line 2223 in _signature_from_callable
  File "/usr/lib/python3.5/inspect.py", line 2737 in from_callable
  File "/usr/lib/python3.5/inspect.py", line 2987 in signature
  File "/usr/lib/python3.5/pydoc.py", line 1345 in docroutine
  File "/usr/lib/python3.5/pydoc.py", line 372 in document
  File "/usr/lib/python3.5/pydoc.py", line 1160 in docmodule
  File "/usr/lib/python3.5/pydoc.py", line 370 in document
  File "/usr/lib/python3.5/pydoc.py", line 1625 in render_doc
  File "/usr/lib/python3.5/pydoc.py", line 1632 in doc
  File "/usr/lib/python3.5/pydoc.py", line 1895 in help
  File "/usr/lib/python3.5/pydoc.py", line 2615 in cli
  File "/usr/bin/pydoc", line 5 in <module>
[1]    15338 segmentation fault (core dumped)  pydoc foo

(and similarly when trying foo.foo? in IPython)
Arch Linux
Python 3.5.2
Cython version 0.24.1

Fixed in the most recent master - pydoc gives the correct signature.
I suspect this was fixed with https://github.com/cython/cython/issues/1470 (but haven't confirmed this)


Class that extended Subsampling library, opening images in zoomed state

I tried  to extend your class and reset image scale onSizeChanged. It helped me to reset the image on rotation, but now I got another problem. On first open my images opens in zoomed state. What I did wrong?
import android.content.Context;
import android.util.AttributeSet;

import com.davemorrissey.labs.subscaleview.SubsamplingScaleImageView;

public class CustomSubsamplingScaleImageView extends SubsamplingScaleImageView {

    public CustomSubsamplingScaleImageView(Context context, AttributeSet attr) {
        super(context, attr);
    }

    public CustomSubsamplingScaleImageView(Context context) {
        super(context, null);
    }

    @Override
    protected void onSizeChanged(int w, int h, int oldw, int oldh) {
        //reset image scale to original on image rotation
        resetScaleAndCenter();
    }
}

The original checks the view is ready before doing anything, like this:
PointF sCenter = getCenter();
if (readySent && sCenter != null) {
    // Do stuff
}

I think you need to do the same.


[AVM Module Issue]: PSQL Deployment often fails when enabling EntraID Auth

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Bug
Module Name
avm/res/db-for-postgre-sql/flexible-server
(Optional) Module Version
0.3.0
Description
For us, the Bicep deployment often fails when enabling Password Auth and EntraID Auth on our PSQL Server.
4 out of 5 times it will fail with The server '<<server_name>>' is not in an accessible state to perform Azure AD Principal operation. Please make sure the server is accessible before executing Azure AD Principal operations. (Code: AadAuthOperationCannotBePerformedWhenServerIsNotAccessible).
I tried playing around with the deployment order locally but couldn't find a reliable order that resolves this issue...
Code Snippet:
module flexiServer 'br/public:avm/res/db-for-postgre-sql/flexible-server:0.3.0' = {
  name: 'psql-flexi-${deploymentNameVar}'
  scope: resourceGroup
  params: {
    name: names.outputs.psqlName
    location:'westeurope'
    administratorLogin: names.outputs.psqlAdminUserName
    administratorLoginPassword: psqlAdminPassword
    administrators: [
      {
        objectId: managedIdentityContainerInstance.outputs.principalId
        principalName: managedIdentityContainerInstance.outputs.name
        principalType: 'ServicePrincipal'
      }
      {
        objectId: adminGroupPrincipalId
        principalName: 'sg-pace-resource-access-smc-admin'
        principalType: 'Group'
      }
    ]
    tier: psqlTier
    skuName:'Standard_D2s_v3'
    availabilityZone: '2'
    backupRetentionDays: 7
    geoRedundantBackup: 'Disabled'
    createMode: 'Create'
    highAvailability: 'Disabled'
    passwordAuth: 'Enabled'
    activeDirectoryAuth: 'Enabled'
    delegatedSubnetResourceId: psqlSubnetId
    privateDnsZoneArmResourceId: getPrivateDnsZoneResourceId(
      connectivityHubSubscriptionId,
      connectivityHubResourceGroupName,
      postgresPrivateDnsZoneName
    )
    storageSizeGB: 512
    version: '14'
    configurations: [
      {
        name: 'lock_timeout'
        value: '1500'
        source: 'user-override'
      }
      {
        name: 'shared_preload_libraries'
        value: 'pg_stat_statements'
        source: 'user-override'
      }
      {
        name: 'temp_tablespaces'
        value: 'temptblspace'
        source: 'user-override'
      }
      {
        name: 'log_line_prefix'
        value: '%t-%c %d'
        source: 'user-override'
      }
      {
        name: 'max_wal_size'
        value: '32768'
        source: 'user-override'
      }
    ]
    diagnosticSettings: [
      {
        storageAccountResourceId: dseStorageAccountResourceId
        logCategoriesAndGroups: [
          {
            categoryGroup: 'audit'
            enabled: true
          }
          {
            categoryGroup: 'allLogs'
            enabled: true
          }
        ]
        metricCategories: [
          {
            category: 'AllMetrics'
            enabled: false
          }
        ]
      }
    ]
    enableTelemetry: true
  }
}

(Optional) Correlation Id
80fb0d4c-d51d-4803-9be3-d79be922e709

Thanks @GregorLauritz for submitting the issue. Let me take a look to see if I can identify an issue.

Contacted product group concerning issue and they were able to recreate in their environment.


fix social cards

fixed social cards code and Updated this branch. Please accept this PR.

The Social Share Preview screenshots are attached.

Works!


Lazily generate video thumbnails for all uploaded videos.

Feature Description
Posters are generated on-the-fly when new videos are uploaded, but that doesn’t really help existing videos. The first time a author opens the story editor, the editor needs to lazily start requesting poster generation for all existing videos (it’s expected, and OK that images would slowly trickle in, since poster generation takes time).

Acceptance Criteria
QA Instructions

closing and merging with $470


Message - TORCH CUDA version not installed/working even though running on CPU

Im running cell pose locally on my Mac laptop (CPU) and I've followed the instructions listed on the Github page (i.e. installed Anaconda, created the python 3.8 environment, installed cell pose and the GUI on the zsh server, upgraded cell pose and then started the GUI by running  python -m cellpose. I can load my image, and can run it through (albeit slowly). However, after analyzing one image or so, I start getting the message in the terminal window - TORCH CUDA version not installed/working. Since I'm running this on the CPU, why am I getting this message? Does it matter or can I ignore it? I am unsure if this message is causing Cellpose to not work on subsequent images as the processing of the image by the software seems to no longer work/finish? Any help or insight would be great.
thanks,
Dabn

That message is displayed on all systems and indicates if GPU acceleration is enabled. Since your Mac doesn't have it, the message says it's not enabled.
Cellpose will operate as normally in CPU only mode. You can ignore it.


Tiny doc error

Page: https://docs.microsoft.com/en-us/office/vba/word/concepts/miscellaneous/storing-values-when-a-macro-ends
Under Document properties, third paragraph:
"Use the CustomDocumentPropertiesproperty (…)", should be: "(…) CustomDocumentProperties property (…)"

@PeterVanLoosbroek Fixed. Changes will be live Monday night.


The snapshot tests are failing due to different font rendering

The following tests are failing for me:
    widget::align::tests::centered
    widget::align::tests::left
    widget::align::tests::right
    widget::button::tests::simple_button
    widget::checkbox::tests::simple_checkbox
    widget::flex::tests::flex_col_cross_axis_snapshots
    widget::flex::tests::flex_col_main_axis_snapshots
    widget::flex::tests::flex_row_cross_axis_snapshots
    widget::flex::tests::flex_row_main_axis_snapshots
    widget::label::tests::line_break_modes
    widget::label::tests::simple_label
    widget::label::tests::styled_label
    widget::portal::tests::button_list
    widget::sized_box::tests::label_box_no_size
    widget::sized_box::tests::label_box_with_size
    widget::split::tests::columns
    widget::split::tests::rows
    widget::textbox::tests::simple_textbox

And the .diff.png files all only show the text, e.g:

(I'm on Debian.)

Is this still relevent @PoignardAzur ? I think we now use a bundled font (Roboto) for text rendering tests.

Yeah, we haven't had any complaints, including from people using MacOS and windows. I'll assume it's fixed until proven otherwise.


[FEATURE] Support for Multiple Languages

I think a good starting point would be to add:

English
Russian
French

(as a minimum)
This will be a very large task, and will require a lot of re-writing and translating.
I have a bit of knowledge regarding both Russian and French, but my translations likely will not be 100% accurate.

First of all, I think we should create a basic structure for translations and choose the default language (Eng). Then we can translate to other languages :) And I can help with Russian.

This was the plan, I just created a branch not too long ago.
I think a macro to print strings would be ideal, and that macro checks the locale of the host computer and looks up the translation. If it's not added, default to English.
We'd probably need to refactor the printing of things, such as moving file names+additional info to the end of the text - there's probably too many factors throughout languages otherwise.

I think it's better to do without a macro. :man_shrugging:  The macro will add chunks of code every time we place it. And there is not always a rational side to it) I prefer to avoid it if possible

But a macro can help to assemble our beautiful structure into a small call

Going to close this for now. Dexios doesn't have too many command-line outputs (as of #208), so I think most of the work would be on clap definitions (and maybe the docs/readmes).


Need to write test for workflows

Describe the issue:
Need to write test cases to capture the issue mentioned in [1]
[1] https://github.com/wso2/product-is/issues/11155

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


feat(ci): add e2e delete test for kafka sink

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
After #9855 and #9833, it's necessary to test Kafka sink for delete in e2e test.

Checklist For Contributors

[x] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[x] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

could you please elaborate more on the test details?


浏览器提示性能优化

Canvas2D: Multiple readback operations using getImageData are faster with the willReadFrequently attribute set to true.https://html.spec.whatwg.org/multipage/canvas.html#concept-canvas-will-read-frequently

fixed in 1.12.2


Symbol color interactivity not working properly

When the color of a symbol is not set and the color is changed in an interactivity event it produces weird results.
const DURATION = 10;
interactivity.on('featureEnter', (event) => {
  event.features.forEach((feature) => {
    feature.color.blendTo('yellow', DURATION);
  });
});
interactivity.on('featureLeave', (event) => {
  event.features.forEach((feature) => {
    feature.color.reset(DURATION);
  });
});

Color: red

Color: default

Just merged into master (not in v0.8 though, but next release)


Bug: game window resizing

@andrewchangshs : The bot inconsistently resizes the game window both using window decoration height option and automatic resizing. This does not affect farming, however, it does cause the pod bar percentage to be inaccurate.
I am wondering if this is because the bot resizes to the middle of the screen and my laptop resolution is not large enough (the bottom of the bot is slightly hidden)

I'm thinking to make the bot use the full width and height of the screen, this would also be better if you wanna use the bot the same time you're playing without having to resize the window each time you wanna take the control of the game.


.evaluate does not return anything good

I cannot understand why result of .evaluate equals null in my example.
whatever.queryForLink = function(url) {
    var self = this;
    return new Promise((resolve, reject) => {
        var ev = self.page.evaluate(() => {
            return "YABADABADOO";
        }).then( answer => {
            console.log("Answer", answer); // expecting here YABADABADOO, but got null instead.
        }).catch(error => {
            console.log("ERRR", error);
        });
        console.log("ev:", ev); // here I get lib$es6$promise$promise$$Promise object.. Oo
    });
};

I have stripped page creation and other processes and left only a problematic function. Also I tried to add onError for page object hoping that any clues will come up by this, but no such events were raised.
What really confuses me that I get null in console. Why null? If for some reason nothing is returned from evaluation, I would expect at least to get undefined..
Using phantomjs-node version 2.1.14

It looks like evaluate doesn't work with arrow functions for some reason.

Yea. => doesn't work because phantomjs doesn't understand the arrow. I am not sure if it is a bug but perhaps we can convert => to function(){}?

Yea, I guess it's working as intended, but it'd be nice to be able to to use arrow functions consistently. Do you think we should convert '() => {}' to 'function() {}' here?

@elias-winberg that is where it would be. I never thought it was a bug because if you use babel then it would work without making any changes. But now this is the fourth time someone has added this as a bug. We have two options:

Fix it so that => works
Throw a big huge error saying you can't use =>

I can do either one later next week or you can give it a try to. Happy to review whatever.

I didn't really fix the problem but I did add the error and warning log.

@kaytrance what's your status on this issue? Did you try using function and does it work now?

Sorry for delay. I have tried to change arrow function syntax to normal funciton() and it worked, so the issue can be closed.


Release version 0.0.2

Codecov Report
Patch and project coverage have no change.

Comparison is base (097df41) 100.00% compared to head (9816beb) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #108   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           62        62
  Lines         2137      2137
  Branches       145       145
=========================================
  Hits          2137      2137

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


Broken outbound links from index pages for older TF API

URL(s) with the issue:
Numerous links of the older TF APIs, listing only a few index pages as examples here:

Links under "Classes" and "Functions" within https://github.com/tensorflow/docs/blob/r1.11/site/en/api_docs/python/tf.md
Links under "Classes" and "Functions" within https://github.com/tensorflow/docs/blob/r1.11/site/en/api_docs/python/tfdbg.md
Links within https://github.com/tensorflow/docs/blob/r1.5/site/en/api_docs/python/index.md
"JAVA" link within https://github.com/tensorflow/docs/blob/r1.7/site/en/api_docs/index.md

Description of issue (what needs changing):
A large amount of links on index pages (e.g. for functions and classes) are currently broken (404). This appears to affect only the older TF versions (multiple versions affected), whose index pages are Markdown files within Github repositories.
Clear description
Outbound links from these indexing pages are currently broken. Some might be fixed by adding a .md after the current URL to point to the correct Markdown available in the repositories, but not all of them can be fixed through this way.
Correct links
Is the link to the source code correct?

Incorrect.

Submit a pull request?
Are you planning to also submit a pull request to fix the issue?

Currently no plan.

This issue persists in latest TF versions as well.Please, find below links as well.Thanks!
https://github.com/tensorflow/docs/blob/r1.15/site/en/api_docs/python/tf.md
https://github.com/tensorflow/docs/blob/r2.0/site/en/api_docs/python/tf.md
https://github.com/tensorflow/docs/blob/r1.15/site/en/api_docs/python/tfdbg.md
https://github.com/tensorflow/docs/blob/r2.0/site/en/api_docs/python/tfdbg.md
https://github.com/tensorflow/docs/blob/r1.15/site/en/api_docs/python/index.md
https://github.com/tensorflow/docs/blob/r2.0/site/en/api_docs/python/index.md

Acknowledged.
This is my fault. I'll make sure it doesn't happen going forward, but IDK how many of the old snap-shots I can fix.

Hey, @MarkDaoust  I'll happy to work in this issue.

Hi @lichili233 ! 1.x version are not supported any more. For the 2.x version , You can find working links here.
python/index.md  (Updated till 2.0 )
api_docs/index.md  (Updated till 2.3)
python/tf.md (updated till 2.4)
Could not find tfbdg.md in 2.x version. Thanks!


Update shadow-dom-selector and use the new dot notation syntax

coverage: 100.0%. remained the same
when pulling 3bc7401ac949b1af9b833a820f16752c1e0b60cf on update_shadow-dom-selector
into c5068747b737bf32743ab918a79f141b8886d1fb on master.


Can't find JS config files in the current directory

If you create a JavaScript configuration file in the current directory, then run jsdoc -c conf.js, you get the following error message:
Cannot parse the config file conf.js: Error: Cannot find module 'conf.js'

If you specify ./conf.js instead, it works.
We should fix this before 3.5.0 ships.

Fixed on master. The fix will be included in JSDoc 3.5.0.


Update Enum.chunk_by in translated guides

PR #528 updated the Enum.chunk_by/2 section of the basics/enum lesson to be a bit more clear.
You can see the exact changes in English here.
Update
This has since been included to show the arity, see here.
Translation
Translation progress:

[x] en
[x] ru /cc @brain-geek / @nscyclone
[x] ko /cc @devleoper
[x] jp /cc @3100
[ ] no /cc @therobinsj
[x] pl /cc @Koziolek
[ ] sk /cc @michalvalasek
[ ] fr /cc @julienXX
[ ] cn /cc @cizixs
[x] es /cc @aleandros / @jonahoffline / @edwinallenz
[ ] pt /cc @pragmaticivan
[ ] vi /cc @joneslee85
[ ] it /cc @lucidstack  / @sformisano
[ ] my /cc @alkaha
[ ] id /cc @rezaprima

It seems like it is mentioned twice in the task list.

@nscyclone woops! Fixing

@nscyclone fixed

I wonder whether we should mention the functions' arities in the references and headers? They are used in the Strings lesson and sometimes in this one.
What do you think, @ybur-yug, @doomspork?

@nscyclone since its core to the nature of the language itself I think this was an oversight by me. I will update.

@nscyclone fixed here and opening a PR

@nscyclone PR opened https://github.com/doomspork/elixir-school/pull/537

The issue was closed automatically but I suppose it's too early since not all the translations are ready yet.

Good catch @nscyclone!  I didn't notice the magic phrase in that PR that auto-closed this.

This issue seems to be closed by accident once again.

I suck, sorry @nscyclone!  I need to keep an eye out for those triggers in Github commit messages

Sorry it's because I included the fix #... keyword in the commit message I'll use relates to for feature messages

Thank you @edwinallenz, I'll do my part to be more vigilant with those messages!