lodash works perfectly at initial load, however when I refresh I get this error "_ is not defined"

lodash works perfectly at initial load, however when I refresh I get thiserror "_ is not defined"
I added loadash as a plugin to my project, and used the .debounce function which works perfectly when loading the page for the first time, but when i refresh the page  I get this error " is not defined"
submit:_.debounce(function(){
this.searchString = 'searching..................'
if (this.searchValue !== '' ) {
this.$router.push(${this.searchValue})
console.log(this.$nuxt.$route.path)
}
}, 3000)

Are you still having this problem?
Have you tried this?
https://nuxtjs.org/faq/webpack-plugins/

@husayt thanks for your concern. I decided not to use loadash for my application. But if I decide to use it in future I'll definitely try out your solution. Thanks again.


Remove the 'export's in .env.example in order to get your environment…

… variables to pull through when you run 'node .'.
When I run npm i and node . as per this documentation (https://www.twilio.com/docs/authy/quickstart/two-factor-authentication-nodejs) that points to this repo, I get an error telling me:
"Please set your ACCOUNT_SECURITY_API_KEY environment variable before proceeding."
Line 17 in index.js ^^
Removing the 'export's in .env.example (then changed to .env) fixes this issue.

I used exactly the code you provided on both a Windows and macOS machine and got the same error for both systems.
The tutorial on the Twilio website that uses this repository doesn't work withe the code as it's written, which can be a hurdle for people new to development.

I don't think just changing the readme is very responsible when this is attached to a tutorial on how to use one of your services.
The provided code should work as is.

I've updated the readme and added source .env is a pretty common first step when pulling a repo.
Thank you for your suggestion.

Right, but people who are new to programming won't always know to go through the readme to see if it's different than the official tutorial.
People might just see that it's not working, get frustrated, and give up on Twilio.

Yes, I've added a source .env step in the README.  Thanks again for your attention to detail.   We'll add it to the other instructions as well. Cheers!

If that's what you want to do, sure. I just think it's irresponsible to have your code not match your tutorial, but whatever.

As I stated above, we're updating those as well.   Perhaps clear your cache?  I'm not sure why supporting autoenv is irresponsible but thanks again for the heads up.   Cheers!


add Singapore

the docs mentioned all but the one in Singapore..

I need to add support for the relevant network location before you can create nodes in Singapore. I will try to add this to the next release if I can.


Missing sofort property from createSource types

Summary
As per the documentation for Sofort, we should be able to pass a sofort property with additional data when calling stripe.createSource. This seems to be missing in the type for SourceCreateParams.
There is already a Source.Sofort interface I think could be reused for this, e.g. on SourceCreateParams with:
sofort?: Source.Sofort;

Hi @oskarolsson-jimdo, thanks for the report and sorry for the delay acknowledging this issue.
We recommend that you accept Sofort using Payment Intents instead of the deprecated Sources API (we will make it clearer on the Sofort page you linked that this integration path is deprecated). That said, the types declared in this package should still accept these parameters and I've open #151 to fix.


Question about changing the favicon

To change the favicon,
should I just substitute it with a different one in the public  folder?
Thanks
C.

You can create a favicon.ico file in /static/ folder. Then, Hugo will generate it to the public folder.

Great, thank you! :)


cleanup

proper test setup (no more delegating to a cli)
test for configuration (inline vs non-inline source map)
update links package.json

@sebmck anything i can do to move this along?


⚠ Jenkins Plugins Artifactory has degraded performance

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

HTTP code: 200
Response time: 2564 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 6b57631 after 27 minutes.


feat: add http route interface

Which issue does this PR close?
Closes #
Rationale for this change
Add the http interface of route to facilitate troubleshooting and testing.
What changes are included in this PR?

Add http route interface.

Are there any user-facing changes?
None.
How does this change test
Local manual test.

The pr description information does not match the modified content.

The shardView is very important, can you expose http api to get the shard view.


CSS row highlighting

Hi,
I'm having a silly little issue with the look of my table. I included jQueryUI-1.11.4 and a few other extensions and all of them work just fine, but with the extensions or even without any extensions, all of my rows are plain white, there are no gray alternative rows, like in the example.
So, I have two questions: how can I get the alternative gray rows to show?
And, is it possible to define CSS styles for :hover and :selected?
Thanks!
p.s. also, how can i control the "Show entries" and the "Search", show/hide/remove?

I managed to get the styles working with:
'click tbody > tr': function (event) {
	$('.odd').removeClass('simpletableBodyTableFocus');
	$('.even').removeClass('simpletableBodyTableFocus');
	$(event.target.closest('tr')).addClass('simpletableBodyTableFocus');
}

and css:
table.dataTable tbody tr:nth-child(odd) {
  background: rgba(255, 255, 255, 0.85);
}
table.dataTable tbody tr:nth-child(even) {
  background: rgba(200, 200, 200, 0.85);
}
.simpletableBodyTableFocus {
  background: green !important;
}


[release-4.12] OCPBUGS-20749: CVE-2023-44487: bump golang.org/x/net to v0.17.0

cc @openshift/storage

/lgtm

/label backport-risk-assessed

/jira refresh

CI result is failed with known issue: "ERROR: (AuthenticationFailed) Authentication failed." Can be ignored.
Verified with golang.org/x/net v0.17.0 in go.mod file
/label cherry-pick-approved
/label qe-approved

/jira refresh

CI result is failed with known issue: "ERROR: (AuthenticationFailed) Authentication failed." Can be ignored.
Verified with golang.org/x/net v0.17.0 in go.mod file
/label cherry-pick-approved
/label qe-approved

/jira refresh


WIP: Add Node.js 6 runtime

PR for issue #17

@rabbah I see the following output in my logs for nodejs 6: "XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX"
It appears that the invoker is looking for this in the existing nodejs and is filtering this out.  Should I be updating the code to handle this for nodejs 6 as part of this PR or is thing something that will be handled separately?

@paulcastro
Hi Jason.  The invoker needs the sentinel markers to be coordinated with the language container and since this is node (which already has this feature), it should be enabled as part of this PR.  We are planning on doing this along with Swift and Python.  The relevant code is in lines 295 and 311 of Invoker.scala.
On line 295, augment with
private val nodejs6ImageName = WhiskAction.containerImageName(NodeJS6Exec("", None), config.dockerRegistry, config.dockerImageTag)

and change line 311 to
val isNodeJs = con.image == nodejsImageName || con.image == nodejs6ImageName

That should work but a better version would be to create a Set of all image names that will have the sentinel marker and change to checking con.image for membership in such a set.

I will update the nodejs 6 container to contain the two new packages being added as part of issue #523.   I assume docs will need to be updated as well to include the nodejs 6 list of packages.  The list is currently the same right now outside of package versions (which I don't know if we even list) and Jade being renamed to Pug.

pg #327

The changes look like they will work. I am a little uncomfortable though with the approach we are taking:
$ find nodejsAction/ -type f -exec wc -l {} + | tail -1
925 total
$ find nodejs6Action/ -type f -exec wc -l {} + | tail -1
916 total
$ diff -rw nodejsAction/ nodejs6Action/ | wc -l
104

We are copy-pasting a non-trivial set of functionalities (container definition, action wrapper, Whisk "SDK"), with basically no changes except pinning version numbers of the runtime and of the packages. I know we've recently had similar instances of clone-and-own, but never to that extent. Can we refactor this into core/nodejsCommon containing almost all the code, and core/nodejs[6]Action/ using a common base Dockerfile? I feel like this is doomed to diverge in unpleasant ways otherwise.
@sjfink @rabbah and others may want to comment and/or suggest better refactoring strategies.

Agreed we should not have multiple copies of all those js files.  It will be a maintenance nightmare.  Your strategy seems fine.  Since docker likes to build things under it, having a separate Dockerfile to build a base is necessary as that Dockerfile will have access to the shared stuff.  And of course, faster builds will be possible if we do it this way.

Seems like some of this will diverge very soon though with issues like #78 and #505.

Clone and own is bad. Extend and override is good.

@psuter - I pushed my refactoring changes and ran pg build # 335

Code looks good to me. Should we have at least one test that's specific to Node.js 6? Maybe throw in a let somewhere?

Can the packages be shared too? I see image magik in the base dockerhost why not all the other packages?
This is borderline nitpicking: the base could have just been the current nodejs action and then the specialization is node4 vs node6. To make the version more explicit (where node4's name is what the system current uses for its kind).

@psuter - I added a test for testing default function parameters, which is new to node 6.  I threw in the let you mentioned as well which not new to node 6, but isn't supported in the existing node we have (0.12.14).  My idea to throw in the Promises to test node 6 was to no avail since those are even supported in our existing node.  Found this nice link for viewing node features by version: http://node.green/

@jasonpet if we kept nodejsAction as is including its docker file, could the nodejs6 action Dockerfile simply upgrade the node version using whisk/nodejsaction as the image base?
the thinking is that we have only one list of packages to maintain instead of two (when we diverge, we'll diverge and make the lists explicit).

@rabbah - I haven't really been able to follow your last few comments regarding the docker file split.  The npm packages are different then the docker packages.  image magik is not an npm package.  The npm packages have different versions based on the node version and even different names in some cases.  Jade was renamed to Pug.

I'm thinking if there is a way to reduce the duplication between the two dockerfiles: primarily so we aren't maintaining two package lists. I did notice the versions are different, but it wasn't clear that we couldn't upgrade the packages in both runtimes. You are right that if we did this, then some packages will have breaking changes for existing node actions, so perhaps this is a reason not to consolidate further.

@psuter - I believe this should be ready now.  I had run pg build 338 after making those test updates.

It's in.

We should extend that split to all our actioncontainers maybe? Only having it in nodejs feels like adding a lot of maintainability and build-process overhead to just installing one package in the same image? Shouldn't stuff like "imagemagick" be in every actionContainer we have?


want to parameterize the threshhold "olderThan" for StoreCleaner.cleanup() method

at the 0.5.0, in https://github.com/kazurayam/inspectus/blob/0.5.0/core/src/main/java/com/kazurayam/inspectus/core/AbstractService.java
line#95
            cleaner.cleanup(jobName, JobTimestamp.now().minusHours(3));

This specifies the StoreCleaner should remove the artifacts older than 3 hours prior to the current JobTimestamp.
I want to parameterise this. I want my program to be able to specify "minus 10 minuts" or "minus 3 days".

done at 0.5.3-SNAPSHOT


SpatialSeries multiview does not show x-by-y

When viewing a spatial series the x-by-y plot is present when viewing the SpatialSeries on its own

but it cannot be viewed in a multi-view:

Maybe a solution could be to allow the user to select what views they want to bring up. You could offer a multi-select for all types that have multiple views and the user can decide which one(s) they want to display.
source: https://flatironinstitute.github.io/neurosift/?p=/nwb&url=https://dandiarchive.s3.amazonaws.com/blobs/f89/c91/f89c9160-056d-4edc-90c6-399dce74d407

This has been addressed by #78. As you suggested you now have a lot more flexibility in mixing and matching views, and more than one view plugin can be associated with the same neurodata type.


Reslate not found on npm registry

Bug Description
npm i reslate and npx reslate init both does not work. misleading install instructions on readme.md?
Screenshots
$ npm i reslate
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/reslate - Not found
npm ERR! 404
npm ERR! 404  'reslate@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:

$ npx reslate init
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/reslate - Not found
npm ERR! 404
npm ERR! 404  'reslate@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR!  The instructions have to be written first otherwise they won't be present on npm.

sounds good, i just wanted to bring this to attention just in case this was a bug or something unintentional.

Thanks! Will close this when published.

Now up to date and published.


[Blocking Issue]: Transformations JSON text area is limited to 2500 characters only

Hi,
I am using Magic Chunks in Azure Devops to update appsettings.json config for my ASP.NET Core project.
I tried to paste a JSON text of size > 2500 character but got the following message:

This input does not support more than 2,500 characters. The pasted content has been clipped.

Can you please increase the max length of this text area!
I tried to split my transformations into 2 tasks as follows:

but got the following error on the second task when running the build:

Did you ever find a work around for this?  I am running into the same issue.

@eeinworks8 just splitted them into 2 pipeline tasks and it worked fine.
(I was facing an issue due to some invalid json I inserted but worked after fixing it)


Warning: Class __PHP_Incomplete_Class has no unserializer

Getting this error when trying to install on php7 using symfony 3.2

I figured this to be a cache issue in symfony. I had to remove the cache directory using rm and will still leave this issue open in case you have some ideas.

how is this related to my library? how did you install it? also is there a stack trace for the error?


zalan-postgres-health-check container image: do we still need this?

During the Kubernetes v1.29 upgrade, I noticed that we build the zalan-postgres-heralth-check container image.  It doesn't look like we reference this anywhere.  I'm going to delete this now.
We should follow up to be sure.

CLOSING: It looks like later versions of this operator has probably integrated the health check and metrics because these settings are not longer in the Helm chart.

We might need this after all:
https://github.com/zalando/postgres-operator/issues/1703

...although it looks like we've disabled this functionality:


Improvement 2

Re-wrote the entirety of anime section

Let's just hope that this doesn't breaks anything.


Mobile nav redesign

Context
During design/dev sync yesterday we decided the current mobile design for navigation is problematic being in the header since the sidenav will always exist outside of it.
TO DO

[ ] We need to redesign an option where it's visually outside of the header

Redesigned the mobile trigger
https://www.figma.com/file/mh2maMG2NBtk41k1O1UGHV/Canadian-Digital-Service
---GC-Design-System?type=design&node-id=6381-17372&t=xlzmraTw5sdQPYwf-0


Plugins could avoid warnings by installing UIApplicationDelegate methods dynamically

Issue about warning message on console
https://github.com/flutter/engine/pull/8843
Right now iOS apps have the following in their logs:

You've implemented -[ application:didReceiveRemoteNotification:fetchCompletionHandler:], but you still need to add "remote-notification" to the list of your supported UIBackgroundModes in your Info.plist.

A possible improvement would be to avoid implementing that method directly, and instead only add an implementation using class_addMethod if we detect that it's needed for registered plugins. If no plugin implements application:didReceiveRemoteNotification:fetchCompletionHandler: then FlutterAppDelegate wouldn't implement it either, and thus would avoid the warning.
The same could be done for other UIApplicationDelegate methods as well.
/cc @mravn-google @szakarias @jakobr-google @mit-mit @Hixie @goderbauer

Edited by cyanglaz:
The original issue mentioned above has been fixed with https://github.com/flutter/engine/pull/8843. However, there is a related but different issue regarding receiving email warning from Apple when uploading builds. I have summarized the discussions and works related to it in below section for easier understanding the bug and where we are at:
Issue about warning email from Apple
When uploading a Flutter App to Apple, one might receive an warning Email like below:
Dear Developer,We identified one or more issues with a recent delivery for your app, "Flutter Gallery". Your delivery was successful, but you may wish to correct the following issues in your next delivery:Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the "aps-environment" entitlement. Xcode 8 does not automatically copy the aps-environment entitlement from provisioning profiles at build time. This behavior is intentional. To use this entitlement, either enable Push Notifications in the project editor's Capabilities pane, or manually add the entitlement to your entitlements file. For more information, see https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_ref/doc/uid/TP40008194-CH6-SW1.After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.Best regards,The App Store Team

Although this warning doesn't block releasing Apps, this warning is annoying and confusing for Flutter Apps that doesn't use push notifications.
Steps to reproduce

You need to have a valid Apple Distribution certs and private keys installed on your computer.
Create a new Flutter App. Build it for iOS with flutter build ios, or flutter build ios --local-engine=ios_release local engine build.
With the Apple Distribution account, upload the App to App Store Connect. You can follow the steps here: https://help.apple.com/xcode/mac/current/#/dev442d7f2ca
After a successful upload, you will see an email with a message similar to above.

Workaround
To not receiving this email anymore, you can workaround by enabling publish notification in your App. (You don't have to implement any publish notification features, just simply enable the feature and capability will suppress the warning.)
Cause
The root cause of this issue is the appearance of [application:didRegisterForRemoteNotificationsWithDeviceToken:] in the engine code base is the cause of the email warning in https://github.com/flutter/flutter/issues/9984#issuecomment-405380407.
Either directly implement this method, or dynamically implement this method with a similar solution in https://github.com/flutter/engine/pull/8843 (which only mentioning this method with a @selector syntax) triggers this warning email.

I assume from the above that it is possible and safe to add a new method after plugins are registered and before the method in question is called? I read somewhere that method swizzling tricks should be done in the +load method which may be too early.
Then there is the issue that people might implement the method in their own AppDelegate. Currently they should just call super to have the call forwarded to any interested plugins. If we use class_addMethod, we need another way of doing this. For instance, we could have a FlutterAppDelegate method that does plugin forwarding, but using a different selector like (forwardToPluginsApplication:didReceiveRemoteNotification:fetchCompletionHandler:). The method we add should call this one.

Urban Airship solves this problem with swizzling in application:didFinishLaunching: so I think it's safe for us to do so as well. It wouldn't make sense to do it in [FlutterAppDelegate load] because that would get called before [GeneratedPluginRegistrant registerWithRegistry:] so we wouldn't know what the plugins are yet.
My current thinking is that we should remove the plugin-related UIApplicationDelegate implementations from FlutterAppDelegate. Instead, let plugins swizzle the [UIApplication sharedApplication].delegate object directly in their registerWithRegistrar implementation (possibly providing an API for doing so, so that devs don't have to learn how to swizzle correctly and they can write plugins in Swift someday).
If AppDelegate provides a didReceiveRemoteNotification:fetchCompletionHandler: implementation, the call to [super didReceiveRemoteNotification:fetchCompletionHandler:] will do nothing because it's not implemented by FlutterAppDelegate. It'll work regardless of whether they call the super method or not.

Where's this at?

This bug causes developers to get this warning after uploading to the AppStore:
"""
Dear Developer,We identified one or more issues with a recent delivery for your app, "Flutter Gallery". Your delivery was successful, but you may wish to correct the following issues in your next delivery:Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the "aps-environment" entitlement. Xcode 8 does not automatically copy the aps-environment entitlement from provisioning profiles at build time. This behavior is intentional. To use this entitlement, either enable Push Notifications in the project editor's Capabilities pane, or manually add the entitlement to your entitlements file. For more information, see https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_ref/doc/uid/TP40008194-CH6-SW1.After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.Best regards,The App Store Team
"""
FYI @mjohnsullivan this might warrant a mention in https://flutter.io/ios-release/  or maybe it's already covered in stack overflow.

Is there documentation on how to workaround this issue while proposed solution is in progress, it'd be very helpful.

@pulyaevskiy
I'm pretty sure the "solution" is ignore the warnings.  They don't technically break anything.  Apple will still approve your app, as long as you're not actually using push notifications.

Instead of swizzling, would it be sufficient if FlutterAppDelegate instead used respondsToSelector: and forwardingTargetForSelector: and made them conditionally forward to the FlutterPluginAppLifeCycleDelegate?

This bug causes developers to get this warning after uploading to the AppStore:
"""
Dear Developer,We identified one or more issues with a recent delivery for your app, "Flutter Gallery". Your delivery was successful, but you may wish to correct the following issues in your next delivery:Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the "aps-environment" entitlement. Xcode 8 does not automatically copy the aps-environment entitlement from provisioning profiles at build time. This behavior is intentional. To use this entitlement, either enable Push Notifications in the project editor's Capabilities pane, or manually add the entitlement to your entitlements file. For more information, see https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_ref/doc/uid/TP40008194-CH6-SW1.After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.Best regards,The App Store Team
"""
FYI @mjohnsullivan this might warrant a mention in https://flutter.io/ios-release/ or maybe it's already covered in stack overflow.

Still getting this warning on every upload.

getting this warning too ! Ignoring is not the solution really.

We get the same thing,
Cordova app - build with adobe phonegap build
Plugin:
phonegap-plugin-push   	npm	~2.2.3	2.2.3	android,ios,winphone
On ad-hoc build, no problem. But on the release build:
Same mail as stated above "missing entitlement", but i get one more error/problem.
The push wont register and gives the error:
{"line":62,"column":50,"sourceURL":"http://localhost:8080/plugins/phonegap-plugin-push/www/push.js"}.
Tried:

Other versions of the plugin;
Cordova update;
New provisioning cert.

Im getting the same warning, would be good if we can remove this warning.

As a workaround for getting rid of the Apple warning mails after uploading (regarding missing push notifications entitlement) you can just activate push notifications under certificates in Xcode.
The iOS user won't even be asked for permissions for push notifications, nor will it show up in settings.

https://github.com/flutter/engine/pull/8843 is merged. Now the issue should be resolved. I am closing the issue. Please feel free to reopen if any related issues are found.

@eseidel As you pointed out the issue with the warning after uploading to AppStore, was this suppose to fix this? I still get the warning even after this was merged. Now this is closed, and the issue pointing directly to the warning issue is also closed. Everything closed but hopefully not forgotten as my CEO still believes something is wrong with our app (he gets the warning email too) :D

My understanding is this issue is not fixed, since I also still get an email warning every time we publish Flutter's own example apps. :/
@collinjackson, @amirh do you know?

Actually, it's very possible this is fixed on master, but not on stable or beta and it's possible that we're just currently releasing our example apps from one of those (and that @PerLycke your company is also releasing from a stable/beta branch and thus don't have the fix yet)?

Posted the above after I released from dev earlier today to see if it was fixed, but still got the warning email. So not fixed in dev where this is merged @eseidelGoogle

This fix should start at flutter v1.7.0

This fix should start at flutter v1.7.0 @PerLycke are you seeing the warning in the original post in the console as well?

I got the warning email using:

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v1.7.9, on Mac OS X 10.14.5 18F132, locale en-SE)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
[✓] iOS tools - develop for iOS devices
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.4)
[✓] IntelliJ IDEA Community Edition (version 2019.1.3)
[✓] Connected device (2 available)
• No issues found!

@cyanglaz Didn't see your edit before I posted. No, I don't see that in the console. Just this annoying email from Apple. If there is anything else I can try to help please let me know

@PerLycke Hmm. it seems like my fix only fixed the log. Apple would still send email even if the delegate methods are implemented dynamically.
One thing you can do to workaround it for now until we fix it is to enable the push notification capability for your iOS app.
You can follow here https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/pushing_background_updates_to_your_app?language=objc
specifically under Enable the Remote Notifications Capability
Remember the check both remote notification and background fetch. Please let me know if this helps.

I put some ideas for a potential solution into flutter/engine#9488
@PerLycke would you be willing to try patching your engine with this change and submit your app and let us know if you still get the warning?
https://github.com/flutter/flutter/wiki/Compiling-the-engine

@cyanglaz The workaround you proposed didn't work and I still got the warning email from Apple. I guess the last resort is to enable push notifications to avoid the warning email.
@collinjackson I'm sorry but I'm struggling building for ios using a custom built engine, and I don't know how to get around the error. So I can't confirm if your fix works or not :/ Getting the following error:

Failed to build iOS app
Error output from Xcode build:
↳
** BUILD FAILED **
Xcode's output:
↳
ld: warning: Could not find auto-linked framework 'Flutter'
Undefined symbols for architecture armv7:
"_FlutterMethodNotImplemented", referenced from:
-[FLTDeviceInfoPlugin handleMethodCall:result:] in DeviceInfoPlugin.o
"OBJC_CLASS$_FlutterMethodChannel", referenced from:
objc-class-ref in DeviceInfoPlugin.o
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
/Users/per/android/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_secure_storage-3.2.1+1/ios/Classes/FlutterSecureStoragePlugin.m:87:49: warning: values of type 'OSStatus' should not be used as format arguments; add an explicit cast to 'int' instead
[-Wformat]
NSLog(@"SecItemUpdate status = %d", status);
~~   ^~~~~~
%d   (int)
/Users/per/android/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_secure_storage-3.2.1+1/ios/Classes/FlutterSecureStoragePlugin.m:95:46: warning: values of type 'OSStatus' should not be used as format arguments; add an explicit cast to 'int' instead
[-Wformat]
NSLog(@"SecItemAdd status = %d", status);
~~   ^~~~~~
%d   (int)
2 warnings generated.
Encountered error while building for device.

Just submitted and ap and got this; and I do have the profile and everything setup correctly, so not sure whats is going on.

There are some helpful notes in firebase-ios-sdk explaining how the warning email is triggered and how to get around it.
https://github.com/firebase/firebase-ios-sdk/blob/7eb1747e4b9be195ea9908b9da28b1d0f818afe3/GoogleUtilities/AppDelegateSwizzler/GULAppDelegateSwizzler.m#L98
 *  We have to opt out of referencing APNS related App Delegate methods directly to prevent
 *  an Apple review warning email about missing Push Notification Entitlement
 *  (like here: https://github.com/firebase/firebase-ios-sdk/issues/2807). From our experience, the
 *  warning is triggered when any of the symbols is present in the application sent to review, even
 *  if the code is never executed. Because GULAppDelegateSwizzler may be used by applications that
 *  are not using APNS we have to refer to the methods indirectly using selector constructed from
 *  string.
 *
 *  NOTE: None of the methods is proxied unless it is explicitly requested by calling the method
 *  +[GULAppDelegateSwizzler proxyOriginalDelegateIncludingAPNSMethods]

I've updated flutter/engine#9488 with an approach based on this (waiting on @RedBrogdon to try submitting an app for me).
Relatedly, it seems that Firebase's swizzling got broken recently, see the discussion in https://github.com/flutter/flutter/issues/35267 and https://github.com/flutter/plugins/pull/1826

I am currently working on some other stuff and won't be able to actively work on this recently. I am going to un-assign myself from this issue.
cc @collinjackson

Any update on this?
I recently uploaded an application and received the above-mentioned warning as email.
There are no other issues, but the warning email itself is very annoying and giving a feel like something went wrong in the application.

Same here. I have received the same email this morning. Any update about this?

As a workaround for getting rid of the Apple warning mails after uploading (regarding missing push notifications entitlement) you can just activate push notifications under certificates in Xcode.
The iOS user won't even be asked for permissions for push notifications, nor will it show up in settings.

I can confirm with @nohli this seems to be the only way to get around this; unfortunatelly we still depend on having the macOS device for preparation purposes. This really needs to get looked at eventually, as it takes away options of using tools like codemagic to avoid the expenses associated with adquiring 2 computers to get the job done.

You can add a file "Runner.entitlements" under ios/Runner/Runner.entitlements
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>aps-environment</key>
	<string>development</string>
</dict>
</plist>

You have to enable "Push Notifications" under Capabilities. Xcode will generate the Runner.entitlements file for you.

You can add a file "Runner.entitlements" under ios/Runner/Runner.entitlements
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>aps-environment</key>
	<string>development</string>
</dict>
</plist>

You have to enable "Push Notifications" under Capabilities. Xcode will generate the "Runner.entitlements" file for you.

My configuration is exactly as you have shown but still getting the warming email.
Runner.entitlements
`

aps-environment
development

`

I too can't get rid of the warning email. I would consider this to be more than just an annoyance because it means it's now very difficult to get users to approve the app. With this error, TestFlight is rejecting the app. Even though the actual release may not be rejected, how do people approve if not via Test Flight?

@hagen00 in the comment above yours, the workaround is explained pretty well, did you try it?

@nohli I tried setting the two push notification permissions in Xcode, but didn't add the Runner.entitlements file. The app is live now, but next time I try get the app onto Testflight, I'll try add the Runner.entitlements file as well.

I can confirm that @rodruiz's solution worked for the Flutter stable channel! I do not get that warning message anymore when submitting a revision to App Store Connect.

Then the file named by @rodruiz (Runner.entitlements) should be generated alongside other Xcode files by flutter create, isn't it ?

I think this issue and it's proposed workaround is a severe security risk and I can't understand why it is proposed to enable the capability for push notifications and to create an entitlement for a functionality even when it is not used.
If any flutter app has to enable this and there happens to be a malicious pub who sends malicious push notifications to all apps which are using this pub you will have a great problem.
Please correct me if I'm wrong

So the safest solution is still to ignore the warning ?

So the safest solution is still to ignore the warning ?

Appears like that...looking for clarifications as well.

same issue.  3 years and still no solution?

Any update on the solution ? Faced this issue, when the build was pushed to Appstore.

i still receive this "ITMS-90078: Missing Push Notification Entitlement" email, so any solutions?

I have this problem, any update?

This seems to have been fixed.

@chinmaygarde When you say it's fixed, Is it fixed in master? I've just uploaded to App Store and still got this email: https://github.com/flutter/flutter/issues/9984#issuecomment-405380407
flutter doctor -v:
[✓] Flutter (Channel beta, 1.21.0-9.2.pre, on Mac OS X 10.15.6 19G2021, locale en-SE)
    • Flutter version 1.21.0-9.2.pre at /Users/per/dev/flutter
    • Framework revision 81a45ec2e5 (4 days ago), 2020-08-27 14:14:33 -0700
    • Engine revision 20a9531835
    • Dart version 2.10.0 (build 2.10.0-7.3.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/per/Library/Android/sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 48.1.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

This seems to have been fixed.

I check in stable channel still have problem

@chinmaygarde This is still an issue in stable today
Flutter 1.20.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 216dee60c0 (8 days ago) • 2020-09-01 12:24:47 -0700
Engine • revision d1bc06f032
Tools • Dart 2.9.2

Neither these solutions work for me, any way to override all the notifications handlers with a dummy class

We have this issue as well and it worries us. Is there any fix planned for this issue in the near future? Is there any risk of apps being rejected?

You can add a file "Runner.entitlements" under ios/Runner/Runner.entitlements

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

	<key>aps-environment</key>

	<string>development</string>

</dict>

</plist>

You have to enable "Push Notifications" under Capabilities. Xcode will generate the "Runner.entitlements" file for you.

This is the workaround.

Any fix yet? I'm still encountering this issue in flutter 1.22.2 build. I don't want to use the workaround since I would need to generate a new provisioning profile for that.

Any fix yet? I'm still encountering this issue in flutter 1.22.2 build. I don't want to use the workaround since I would need to generate a new provisioning profile for that.

@marcqtan actually, if you just enable it in Xcode (like in the screenshot above), there will be no provisioning profile under https://developer.apple.com/account/resources/profiles/list.

For this workaround, my question is will the user be asked to consent to Pushed Notification? Since we don't use it we don't want to send a conflicting message to the user.

@zenkog
No, the user will not be asked about anything related to push notifications... in fact the Notifications permission access will not be visible in the app settings from the OS settings.

Sorry, but does the @nohli 's workaround enable the push notifications capabilities on the app? If so, I think is a security threat

Sorry, but does the @nohli 's workaround enable the push notifications capabilities on the app? If so, I think is a security threat

Grumble.

We now have both this issue and https://github.com/flutter/flutter/issues/14182 closed. @chinmaygarde has not replied to requests for clarification on why they closed this issue.
The workaround comes after it was closed. But it seems to contradict itself, and now I feel the need to research why "enabling push notifications" does not really "enable push notifications" but actually just stops the email warnings about push notification.
In my opinion, the other issue should be reopened, as it is more aptly named. This issue is titled with a particular approach to solving it, if I understand correctly. The issue developers are facing is described more directly at https://github.com/flutter/flutter/issues/14182.
I am curious why @Hixie removed this from Milestones. I do see https://github.com/flutter/flutter/issues/61969 was spontaneously closed before then. I'm guessing because this issue's title is too specific in how this issue should be solved.

EDIT: the other issue was reopened, please disregard all but the second paragraph. You can even disregard that, to some extent. 😀

@bradyt I got ahead of myself, I think https://github.com/flutter/flutter/issues/14182 is properly a duplicate of this one.
I'm reopening this until we can get more clarification from either the plugin or engine team about why this was closed.  https://github.com/flutter/engine/pull/6259 and https://github.com/flutter/engine/pull/9488 were closed, not merged.
The last time this seems touched was https://github.com/flutter/engine/pull/8843

Can anyone clarify why the workaround makes sense? If my app does not use push notifications, why is the fix for this to add entitlement for push notifications? Can the clarification include a quote from official documentation?

Just to add clarification on why this is difficult to ignore, since I think some have suggested to ignore.
The subject line of the email is,

App Store Connect: Your app "" (Apple ID:  Version:  Build: ) has one or more issues

So we must be alarmed at email, check contents, verify that there is only one issue, and that it is the issue about push notifications.
Presumably it would be tricky to write an email filter for this.

Developing for Apple is already a pain. They are always complaining about something. It's a matter of time until they complain about setting push and not using it or not activating it at their console.

Apple is just trying to ignore the fact that so many people don't develop natively anymore. More support for Flutter = happy devs = more cool apps.

I have spent some time to explore different solutions. It seems like the appearance of [application:didRegisterForRemoteNotificationsWithDeviceToken:] in the engine code base is the cause of the email warning in https://github.com/flutter/flutter/issues/9984#issuecomment-405380407.
I have updated the issue description to make this Email warning issue clearer for easier future reference.

Over 4 years later now... is there any plan to fix this? 😟
It's not a great developer experience when apple says you have 1 or more issues on every single release...

Stuck on this problem too...

I've implemented a fix based on the information provided above: https://github.com/flutter/engine/pull/29996
Is there anyone in the position and willing to test this change quickly?  It will take me a minute to setup the conditions to reproduce it.

This issue is closed as a result of https://github.com/flutter/engine/pull/29996.  Since this is an old and much upvoted issue I just want to remind everyone that issues are closed when the fix lands on the master channel.  You can still run into this problem on stable until the PR is merged into the stable channel.    That commit will be tagged with the versions where the fix is present.
I'll also add that this issue involves a black box from Apple so we can't automate tests and Apple could change the algorithm they use for triggering the notification at anytime.  Testing it manually is awkward, but assuming the comments above and what Firebase implemented is correct, this should be fixed now as the remote notification symbols no longer show up in Flutter library.
Thanks!  Let me know if any issues arise.

Reopening, https://github.com/flutter/engine/pull/29996 was reverted in https://github.com/flutter/engine/pull/30330 due to b/210427076

Unfortunately it causes the [1P plugin] to not receive any APNS registration token and therefore not receive any push notifications. I'd guess it ends up breaking external push messaging plugins as well.

Aha there is a bad interaction here between the flutter delegate swizzling and the firebase SDK swizzling (not the firebase plugin but the native SDK itself). If I comment out firebase's swizzling for didRegister then the chime plugin does receive the callback.

The swizzling worked on its own, but unfortunately Firebase and Flutter swizzling the same methods stomped on each other.  Need to investigate something similar that doesn't interfere with Firebase's attempts to avoid the same warnings.

您好，您的邮件我已经收到，我会尽快给您回复，谢谢！
                                                       ——郝雅欣

您好，您的邮件我已经收到，我会尽快给您回复，谢谢！
                                                       ——郝雅欣

I talked @jklint-g and the swizzling that Firebase does when initialized isn't related to getting callbacks for Flutter plugins.  It happens regardless of Flutter.
https://github.com/flutter/engine/pull/29996 added the register methods for FlutterPluginAppLifeCycleDelegate at runtime and did not add them to the FlutterAppDelegate, instead relying on the forwarding target, which broke initialization of Firebase.  Firebase needs those present when its init is called.  If we also add those register methods at runtime to the FlutterAppDelegate everything should work.  The order of operations should be correct since I was editing the runtime at +load time, but Firebase's swizzling is happening when init is called for the Firebase API.

So now we still have to add Push Notification even though we don't use it?

您好，您的邮件我已经收到，我会尽快给您回复，谢谢！
                                                       ——郝雅欣

So now we still have to add Push Notification even though we don't use it?

No, you do not need the entitlement unless your app uses Push. This warning is safe to ignore.

Although this warning doesn't block releasing Apps, this warning is annoying and confusing for Flutter Apps that doesn't use push notifications.

No, you do not need the entitlement unless your app uses Push. This warning is safe to ignore.
That much was clear from the beginning.
Judging from the reactions on some comments, it looks like lots of people find this warning annoying and not a great user experience.
Is this issue going to be closed with the recommendation "please ignore the warning" ?

Is this issue going to be closed with the recommendation "please ignore the warning" ?

No, the intention is to fix it, which is why the issue is still open.  There have been several attempts to fix it but all have caused different, worse issues and have been reverted.

Can this be fixed? It's ridiculous.

@marianhlavac  Saying "it's ridiculous" wont help to fix the issue and is disrespectful to people putting efforts on working on flutter

您好，您的邮件我已经收到，我会尽快给您回复，谢谢！
                                                       ——郝雅欣

Just ran into this issue with Flutter 3.3.2. Looking forward to a resolution soon.

您好，您的邮件我已经收到，我会尽快给您回复，谢谢！
                                                       ——郝雅欣

Apple moved to restrict AdHoc to businesses with 100+ employees.
Smaller flutter developers now have to work inside their clients Apple-Business-Manager.
Now every time I upload a new app version to TestFlight,
not just me but the client gets this warning email about "Missing Push Notification Entitlement".
So now it's no longer an inconvenience that I can just ignore,
but I have to explain this issue to clients who thinks it's unprofessional and I can't even provide them an ETA when this will be resolved.

您好，您的邮件我已经收到，我会尽快给您回复，谢谢！
                                                       ——郝雅欣

Just wanted to report that this is still an issue, the Flutter counter app, when pushed to the App Store produces this email:
ITMS-90078: Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the 'aps-environment' entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the 'aps-environment' entitlement. Xcode does not automatically copy the aps-environment entitlement from provisioning profiles at build time. This behavior is intentional. To use this entitlement, either enable Push Notifications in the project editor's Capabilities pane, or manually add the entitlement to your entitlements file. For more information, see https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_ref/doc/uid/TP40008194-CH6-SW1.

After you’ve corrected the issues, you can upload a new binary to App Store Connect.

cc @leighajarett

It's been a couple of years so people might have missed some history on this issue.  In november 2021 I "fixed" this issue in https://github.com/flutter/engine/pull/29996.
The reason that these warnings happens is because Apple's submit process looks for the presence of certain symbols in the binary, and warns about entitlements if it sees them.  They are there for push notifications.  So, if your app isn't using push notifications, the warnings are irrelevant.
That PR removed those methods from the Flutter binary, adding them at runtime.  The problem is that there are plugins that are built on the assumption that those methods exist so that they can swizzle in their own behavior.  Breaking clients who are swizzling the engine is not defined as a Breaking Change.  However in this case, I'm not entirely sure why since I was absent, it was decided that it would be preferable to revert the fix to accommodate the the plugin that was swizzling and any hypothetical plugin that may be doing the same thing.
So, in summary it's a conflict of Apple warning if certain symbols are present in your binary and plugins that rely on those symbols being present to be used unorthodoxly.
Possible solutions:

Try to find some way to guarantee that our swizzling will happen before any other swizzling so the methods are present when they try to swizzle.
Find some way to more clearly break plugins who rely on those symbols being present.  (I'm guessing there was already an error that they just ignore when they tried to swizzle something that didn't exist.)
Relitigate the revert of the fix (and reach out to migrate plugins we know about or add in a hack to the engine to accommodate them somehow)

@pattobrien has a good point though: like you said, although the "warnings are irrelevant", it still does look really unprofessional if you need to explain stakeholders that this warning received from Apple, for every build you push, isn't really a problem. Plus it becomes annoying if you frequently push updates to TestFlight and this email is sent to everyone, for every. single. build.

@gaaclarke thanks for the insight into your prior fix attempt.

...it was decided that it would be preferable to revert the fix to accommodate the the plugin that was swizzling and any hypothetical plugin that may be doing the same thing.

I'm sure there's more to this than what I'm about to suggest, but perhaps we should consider evaluating the effects of this issue on 100% of iOS Flutter apps, versus the effects of the breaking change on a small subset of push notification apps. I myself have not shipped a single app (of 6 that I've worked on) that requires push notifications, since many use cases can simply be covered by one-off or scheduled notifications via a package like local_notifications. The firebase_messaging package is in the top 80 most liked packages on pub.dev, so breaking changes obviously need to be considered - but at what expense?

any news?

any update ?

Adding onto this thread - we've recently run into the same problem.
I agree with @pattobrien and @b055man - our stakeholders look at this askance. Heck, I only found out because I followed up with our developer to add the entitlement, not realizing this was a long standing annoyance.
It's crazy this has been open for 6+ years.

Let's keep conversation focused on how to fix the issue.  We know it's a problem, it's an open issue, and you can see several engineers have tackled it in the past.  "I agree" just adds noise.

I solved the problem by following the steps in the first two comments of the following link: https://stackoverflow.com/questions/32251123/missing-push-notification-entitlement

Hello guys, is there any solution for this issue? I don't use remote notifications, so I don't want to create an aps-environment.

A bit janky to ask people to enable push notifications for dev only, I'll stick with the warning.

disabling automatic signing and manually sign the app should resolve this issue.

disabling automatic signing and manually sign the app should resolve this issue.

Do you mean Xcode automatic signing? How would that solve it, technically? You are just proposing a solution without saying how exactly it would resolve the issue.
Also, I don't and I've never used automatic signing and I always had this issue. Also, this issue dates back 7 years and I'm sure many with me aren't using automatic signing and still have this issue. Which directly contradicts what you are proposing.

@PerLycke Honestly I'm just confused as you are right now, I tried with an old project and it worked. but now after your comment, I just tried it with our current project and sadly it didn't work. I guess I'll edit the other comment.

Replying to Aaron above: https://github.com/flutter/flutter/issues/9984#issuecomment-1664282440
There might also be a 4th way, which Apple uses itself for issues like this which is adding a runtime "quirk" to only add the symbol for certain plugins.  e.g. We should be able to find all Plugins this would break by scanning pub (running nm or strings on the ios binaries searching for this symbol).  And if so building a list of plugins that need this symbol, and then only registering it from the engine (at runtime) when those binaries/bundleids are present within the application.
Here are some examples from "quirks" in WebKit (there are a ton more in AppKit, depending on what app AppKit is loaded into to maintain old compatibility behavior, but AppKit isn't open source):
https://github.com/search?q=repo%3AWebKit%2FWebKit+quirk+language%3AObjective-C%2B%2B&type=code&l=Objective-C%2B%2B
(It looks like they don't have the list of sites or apps they quirk for checked into GitHub, but they do have the quirking infrastructure.)
But probably the easier solution is to just revert the revert and announce a breaking change.  Right now this bug results in millions of mails from Apple to Flutter devs every time they push to the store, which as others have commented, "makes flutter look bad".

I have this problem, any update?
flutter: 3.24.3
ITMS-90078: Missing potentially required entitlement - Your app, or a library that’s included in your app, uses Apple Push Notification service (APNs) registration APIs, but the APS Environment Entitlement isn’t included in the app signature’s entitlements. If your app uses APNs, make sure the App ID is enabled for push notifications in Certificates, Identifiers & Profiles, sign the app with a distribution provisioning profile that includes the APS Environment Entitlement, and upload a new build to ensure that push notifications function as intended. For details, visit: https://developer.apple.com/documentation/usernotifications/registering-your-app-with-apns.

I am getting the same warning as @kjxbyz
we are not using Push notifications at all in our app.
These are the dependencies our app uses:
cupertino_icons: ^1.0.8
package_info_plus: ^8.1.0
http: ^1.2.2
provider: ^6.1.2
font_awesome_flutter: ^10.7.0
intl: any
shared_preferences: ^2.3.2
icons_launcher: ^3.0.0

And this issue is still present and it is Dec 2024. I got the mail from App Store Connect while I pushed my build to test flight only.

Can confirm that we get this message from Apple as well in Dec 2024 however not using push notifications or related packages in our flutter app.

Same here. I just pushed my build to TestFlight and received the email from App Store Connect. My Flutter app does not use push notifications or related packages.
Here’s the email I received:
Hello,

We noticed one or more issues with a recent delivery for the following app:

- FooBar
- Version 1.0.0
- Build 1

This is for your information only and doesn't require any action:

ITMS-90078: Missing potentially required entitlement - Your app, or a library that’s included in your app, uses Apple Push Notification service (APNs) registration APIs, but the APS Environment Entitlement isn’t included in the app signature’s entitlements. If your app uses APNs, make sure the App ID is enabled for push notifications in Certificates, Identifiers & Profiles, sign the app with a distribution provisioning profile that includes the APS Environment Entitlement, and upload a new build to ensure that push notifications function as intended. For details, visit: https://developer.apple.com/documentation/usernotifications/registering-your-app-with-apns.

I have double-checked everything:

Verified the Apple Developer Portal settings (Certificates, Identifiers & Profiles) to ensure that the Push Notifications capability is correctly disabled.
Regenerated the provisioning profile to reflect the updated App ID configuration.
Confirmed that no references to push notifications exist in my app's code or dependencies.

Despite all this, the warning persists. Any insights would be greatly appreciated.

Same here. I just pushed my build to TestFlight and received the email from App Store Connect. My Flutter (version 3.27.1) app does not use push notifications or related packages.
Here’s the email I received:
Hello,

We noticed one or more issues with a recent delivery for the following app:

- FooBar
- Version 1.0.0
- Build 1

This is for your information only and doesn't require any action:

ITMS-90078: Missing potentially required entitlement - Your app, or a library that’s included in your app, uses Apple Push Notification service (APNs) registration APIs, but the APS Environment Entitlement isn’t included in the app signature’s entitlements. If your app uses APNs, make sure the App ID is enabled for push notifications in Certificates, Identifiers & Profiles, sign the app with a distribution provisioning profile that includes the APS Environment Entitlement, and upload a new build to ensure that push notifications function as intended. For details, visit: https://developer.apple.com/documentation/usernotifications/registering-your-app-with-apns.

I have double-checked everything:

Verified the Apple Developer Portal settings (Certificates, Identifiers & Profiles) to ensure that the Push Notifications capability is correctly disabled.
Regenerated the provisioning profile to reflect the updated App ID configuration.
Confirmed that no references to push notifications exist in my app's code or dependencies.

Despite all this, the warning persists. Any insights would be greatly appreciated.

Just add Push notifications capability in Xcode for your project even if you are not using it.


fix bug: sealos run automatically obtain system architecture information

sealos run automatically obtain system architecture information

There may be something wrong with this modification. You need to execute the arch in each node to get the arch corresponding node to assign values.

git commit -s --amend && git push
need signoff your PR

need support apply scale ,when  change node and master support it

@lixiaojun2914 you need to signoff this PR
git commit -s --amend && git push
need signoff your PR


SAVM: instruction decoding doesn't quite work

In SAVM, the instructions aren't decoded properly for some strange reason. The first 3 values of the instruction are zero on all of the instructions.

There is probably something broken in the SAVM_BITS_EXTRACT macro.


fix(ceph-grafana): make dashboard download work again

This fixes the dashboard download for pacific and later.
Since ceph switched to Prometheus Monitoring Mixins the path to the generated dashboards has changed. It is still working for octopus but it's broken from pacific onwards.
This change fixes the issue. Currently I only added the two latest releases to the check.
Also, this is only related to non containerized deployments.

@mitch000001 thanks!

@Mergifyio backport stable-6.0

@guits This change could potentially break deployments on stable-5.0 for octopus and earlier so I would not recommend to backport it there.

@guits This change could potentially break deployments on stable-5.0 for octopus and earlier so I would not recommend to backport it there.

yup, my bad, I misread your comment. I thought the changes in Ceph was as of Octopus.

@guits seems like the test failed due to a timeout related to alertmanager (ceph-prometheus role). How can I retrigger those tests?

I rebased on latest main

@guits what about newer versions like stable-7.0? Do we want to backport it there, too?


[doc][crypto] Document use of ZK api

How ZK api can be used in Move, with a simple example, recommendations on how to generate proofs (use fastcrypto for tooling)

Is this correct? We just use it in our project https://github.com/CubicGames/battleship/blob/master/sources/board_verifier.move#L14

@jonas-lj is working on the Sui/learn docs (mostly for devs to get familiar with functionality, no api change)
https://github.com/MystenLabs/sui/pull/11450

done in https://github.com/MystenLabs/sui/pull/11450


Sync events and timegraph states

Signed-off-by: muddana-satish<EMAIL_ADDRESS>

@muddana-satish I currently reviewing this patch. I'll get back to you soon.

@muddana-satish I currently reviewing this patch. I'll get back to you soon.

Should be linked to #111

Should be linked to #111

@bhufmann Modified as per your suggestions. Now the selection cursor moves based on the timestamp from the event row.

@bhufmann Modified as per your suggestions. Now the selection cursor moves based on the timestamp from the event row.

Please update and rebase this patch to latest in master.

Addressed all the review comments.

Please update and rebase this patch to latest in master.

Addressed all the review comments.


Comprehensive, Native Windows Support

Now, before you tell me this is a lot of work: I know, and am working on it (and almost done). Ideally, I would like to have my changes merged here, so I have a few questions and concerns for my current port.
Questions
Should I target a specific C++ standard?
Currently, my code depends on a few C++11 features, which can be easily removed with a few macros. This makes the code less readable, however, if C++03 support is desired, I will gladly change my implementation to conform to an older standard.
How to handle Unicode filesystem support?
Currently, LevelDB uses char-based (narrow) strings for for all filesystem operations, which does not translate well for Windows systems (since narrow strings use the ANSI, or OEM legacy codepages, and not UTF-8, for backwards compatibility). This means paths using international characters, or emojis, are therefore not supported with a simple port, something I consider to be an undesirable solution for a modern library. All the current forks of levelDB do not solve this fundamental issue, leading me to create my own implementation. Possible solutions include:

A narrow (UTF-8) API on *Nix, and a wide (UTF-16) API on Windows, using a typedef to determine the proper path type.
Converting all narrow strings from UTF-8 to UTF-16 before calling WinAPI functions.
Providing both a narrow (ANSI) and wide (UTF-16) API on Windows.

The 2nd option, although the least amount of work, is the least amenable for me since the expected encoding for paths from levelDB would then conflict with the entirety of the WinAPI. The 3rd option, however, duplicates code to support both the narrow and wide WinAPI, which would increase the amount of work required to maintain levelDB. The first option is a happy median: it minimizes redundancy and is consistent with expectations about *Nix and Windows paths. I am, however, amenable to any suggestions the levelDB authors may have.
Intellectual Property
To emulate the behavior of mmap on Windows, I used a very lightweight library (<250 lines of code) from Steven Lee, mman-win32. However, looking over your contributor license agreement, it seems that my port would not satisfy Google's CLA until I remove this code from my implementation. If this is the case, I could easily use the raw WinAPI functions rather than the emulated mmap in my Windows port. Please notify me if I should remove this code prior to submitting a pull request.
Other Changes
CMake Build System
I introduced a CMake build system, which retains most of the same logic as the existing Makefile. The existing Makefile has not been deprecated.
AppVeyor Continual Integration
To ensure builds do not break the Windows builds, I am planning to add an AppVeyor configuration, which allows continual integration on Windows using MSVC.
Summary
If there is still interest for native Windows support, and the proposed changes are amenable to the levelDB authors, I would gladly submit a pull request.

On Tue, Oct 17, 2017 at 1:09 PM, Alexander Huszagh<EMAIL_ADDRESS>
wrote:

Now, before you tell me this is a lot of work: I know, and am working on
it (and almost done). Ideally, I would like to have my changes merged here,
so I have a few questions and concerns for my current port.
Questions
Should I target a specific C++ standard?
Currently, my code depends on a few C++11 features, which can be easily
removed with a few macros. This makes the code less readable, however, if
C++03 support is desired, I will gladly change my implementation to conform
to an older standard.

We haven't made a decision w.r.t. this yet, so it will be easiest if it
does not rely on on c++03 only.  Would it be a big problem to do so?

How to handle Unicode filesystem support?
Currently, LevelDB uses char-based (narrow) strings for for all
filesystem operations, which does not translate well for Windows systems
(since narrow strings use the ANSI, or OEM legacy codepages, and not UTF-8,
for backwards compatibility). This means paths using international
characters, or emojis, are therefore not supported with a simple port,
something I consider to be an undesirable solution for a modern library.
All the current forks of levelDB do not solve this fundamental issue,
leading me to create my own implementation. Possible solutions include:

A narrow (UTF-8) API on *Nix, and a wide (UTF-16) API on Windows,
using a typedef to determine the proper path type.
Converting all narrow strings from UTF-8 to UTF-16 before calling
WinAPI functions.
Providing both a narrow (ANSI) and wide (UTF-16) API on Windows.

The 2nd option, although the least amount of work, is the least amenable
for me since the API would then seemingly lies to users of levelDB, since
strings would have to be UTF-8 encoded rather than using the local code
page, in contrast with the entirety of the WinAPI. The 3rd option, however,
duplicates code to support both the narrow and wide WinAPI, which would
increase the amount of work required to maintain levelDB. The first option
is a happy median: it minimizes redundancy and is consistent with
expectations about *Nix and Windows paths. I am, however, amenable to any
suggestions the levelDB authors may have.

Here is what I suggest: make a separate Env implementation for Windows
(instead of attempting to reuse env_posix.cc).  That Env implementation
(like all other Env implementations), accepts char-based (narrow) strings,
which are always utf8 encoded.  Inside this Env's implementation, it can
convert back and forth between the utf8 strings that the rest of leveldb
assumes, and whatever type is appropriate for windows APIs called in the
implementation.
If there is significant code in env_posix.cc you find yourself needing,
consider refactoring that out into a separate .h/.cc (which are private to
the leveldb implementation) so you can share the code in your Env
implementation.

Intellectual Property
To emulate the behavior of mmap on Windows, I used a very lightweight
library (<250 lines of code) from Steven Lee, mman-win32
https://github.com/witwall/mman-win32. However, looking over your
contributor license agreement, it seems that my port would not satisfy
Google's CLA until I remove this code from my implementation. If this is
the case, I could easily use the raw WinAPI functions rather than the
emulated mmap in my Windows port. Please notify me if I should remove
this code prior to submitting a pull request.

Yes, this should be removed.  In general, we have been throttling back mmap
usage anyway (it helps a bit with microbenchmarks, but causes a bunch of
portability problems).  So I suggest a good initial start will be to just
use raw WinAPI functions.

Other Changes
CMake Build System
I introduced a CMake build system, which retains most of the same logic as
the existing Makefile. The existing Makefile has not been deprecated.

AppVeyor Continual Integration

To ensure builds do not break the Windows builds, I am planning to add an
AppVeyor configuration, which allows continual integration on Windows using
MSVC.

This sounds very helpful.

Summary
If there is still interest for native Windows support, and the proposed
changes are amenable to the levelDB authors, I would gladly submit a pull
request.

This sounds very useful to me.  I would like it if the changes were limited
to the following:
(a) A windows Env implementation as I mentioned above.
(b) Build/portability changes.
Is that feasible, or you are seeing the need to make widespread changes?
—

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/leveldb/issues/519, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHuM0W8xE_w2Az-r6NfZqQwYWM9ZBrNVks5stQmLgaJpZM4P8vz1
.

Work on CMake support is already underway. Please use https://github.com/pwnall/leveldb/tree/cmake as a starting point, to avoid rework. Also, please use the Travis CI and AppVeyor configurations in https://github.com/google/snappy as a starting point for yours.
In general, I recommend following the approach taken by Chromium's LevelDB integration. Chromium builds (and runs) on Windows, and does not require modifications to the rest of the LevelDB.

Thank you for the feedback. This would be very feasible to do @ghemawat, especially if we use UTF-8 paths and just convert them in the Windows environment. As for CMake support, I will use that as a starting point (thank you). I will remove the mmap compatibility and use the raw WinAPI calls. Due to my other work, I should be able to finish this later this week.

@ghemawat and @pwnall, a quick question: When I asked the C++11 features and limiting myself to C++03, did you mean limit the codebase to C++98 or C++11? I have a few situations where std::chrono is dramatically more convenient than other code, however, I can remove this (it's only for NowMicros and SleepForMicroseconds). Other than that, the port should not require any new features.
Thank you and I am effectively done with my port, other than this minor question.

We've recently decided that the next release will require C++11, so it's OK to use C++11. Sorry for the code churn on your end... this decision was not taken lightly.

@pwnall No worries, I understand that such fundamental choices do not lend themselves to casual decisions. Thank you for all the help.

Hi @Alexhuszagh,
As a soon-to-be user of the leveldb Windows support (for Mesos), here are are my thoughts:

Should I target a specific C++ standard?

For us, C++11 is fine, we already target this.

How to handle Unicode filesystem support?

This is an annoying problem, I had to fix this for Mesos. I went with:

Converting all narrow strings from UTF-8 to UTF-16 before calling WinAPI functions.

It also leads into long path issues on Windows. I took an approach similar to the one CMake took for their Windows port, a longpath helper to translate all paths as they reach WinAPI functions from UTF-8 to UTF-16 with \\?\ prepended if necessary. My helper is here (note that the max path is not 255 despite documentation).
I need to stress: native long path support is probably a must for most Windows projects nowadays. It's not terribly difficult to do, it's just really annoying.
Also, for your comment:

is the least amenable for me since the expected encoding for paths from levelDB would then conflict with the entirety of the WinAPI

I'm not sure I entirely agree, there is no data loss going from UTF-8 to UTF-16. Both encodings are Unicode, it's just an implementation difference. Plus, you can do the conversion natively in C++11. Anyway, I've not had any problems on Windows having gone this route so far.
Thanks for your work! I personally know the trouble it is 😉

Also:

I introduced a CMake build system

Yay, a million times, yay! We'll pull it into Mesos with ExternalProject_Add.

Hi @pwnall and @ghemawat, I've had a few issues I cannot currently debug. I will attempt to use the Boost-based "windows" branch as a reference-point in short order.
Specifically, I've had 3 major issues:

issue178_test fails intermittently. ~10% of the time, it succeeds, without issue. 25% of the time, it produces a slightly lower number of keys than the 1.1m requires (almost always greater than 1.09m). The rest of the time, it produces the error Assertion Failed: r->options.comparator->Compare(key, Slice(r->last_key)) > 0, file level-db\table\table_builder.cc, line 97.

db_test fails intermittently (at about the same frequency) during the random_read_counter_ section (from env_->random_read_counter_.Reset(); to ASSERT_LE(reads, N + 2*N/100);

Most severely though, however, is the multi-threaded section seems to produce the bad block type error consistently, which would defeat the entire purpose of a multi-thread access.

Otherwise, all the test cases and benchmarks work. Just a heads up for the major delay.

No worries about delays. Honestly, I'm backed up with other work for the next two of weeks, and the odds that I'll be able to look at this are very low.

Everything has been patched, and I am adding extended file length support currently. @andschwa, for the extended file length support, since the "\\?\" prefix effectively removes all path parsing, do you know if there's anything else I need to consider other than:

Relative paths (which cannot use the extended file length prefix).
/, ., or .. in paths (somewhat tricky, see below).

For the . and .. operators, manually parsing them is somewhat tricky, since directory symbolic links may be in play. The only time-tested strategy for this is to iterate over all roots, parent directories, check to see if the item is a directory symbolic link or junction, get the real path of the directory if it is a symlink or junction, and then continue from there. This is because C:\leveldb\..\leveldb-1\README.md does not actually point to C:\leveldb-1\README.md if C:\leveldb is a symlink or junction.
This is very doable (and is relatively easy to implement), but it is fairly expensive since it requires filesystem calls. It requires a temporary vector to store each path component. Step-wise, the general approach is as follows:

Check if the path is absolute (skip remaining steps otherwise).
Replace all forward separators with backslashes.
Iterate over each parent component, from the root (drive letter, such as C:, or UNC root, such as \\host-name\share-name), excluding the file (we don't care if the file is a symlink, since relative path components cannot follow it).
If the directory basename is ., ignore the directory.
If the directory basename is .., remove the preceding directory component.
Otherwise, check if the directory is a symlink by calling CreateFile with the FILE_FLAG_OPEN_REPARSE_POINT and FILE_FLAG_BACKUP_SEMANTICS flags. If the handle is successfully created, it's a symlink, otherwise, it is not.
If the directory is a symlink, read the proper path using DeviceIoControl with the FSCTL_GET_REPARSE_POINT code, and reset the vector using the absolute new path.

I would be totally amenable to implementing this (as you can see, I've done this before), but this may add a lot of expense for a feature that application developer should have to be aware of themselves.
@pwnall, any thoughts? Should extended file length support be added, including with the caveats mentioned above?

@Alexhuszagh I don't believe you missed anything.
Re: bullet 6: I'm using this logic in Mesos:
  const DWORD access_flags = resolved_path_is_directory
    ? (FILE_FLAG_OPEN_REPARSE_POINT | FILE_FLAG_BACKUP_SEMANTICS)
    : FILE_FLAG_OPEN_REPARSE_POINT;

  const HANDLE handle = ::CreateFileW(
      longpath(absolute_path).data(),
      GENERIC_READ,     // Open the file for reading only.
      FILE_SHARE_READ,  // Just reading this file, allow others to do the same.
      nullptr,          // Ignored.
      OPEN_EXISTING,    // Open existing symlink.
      access_flags,     // Open symlink, not the file it points to.
      nullptr);         // Ignored.

adding the FILE_FLAG_BACKUP_SEMANTICS flag only if its a directory. I also specifically use OPEN_EXISTING, though you probably got that.
Re: point 7: I resolve the path using GetFinalPathNameByHandleW with the FILE_NAME_NORMALIZED flag, after using:
  const DWORD access_flags = resolved_path_is_directory
    ? FILE_FLAG_BACKUP_SEMANTICS
    : FILE_ATTRIBUTE_NORMAL;

  const HANDLE handle = ::CreateFileW(
      longpath(absolute_path).data(),
      GENERIC_READ,     // Open the file for reading only.
      FILE_SHARE_READ,  // Just reading this file, allow others to do the same.
      nullptr,          // Ignored.
      OPEN_EXISTING,    // Open existing file.
      access_flags,     // Open file, not the symlink itself.
      nullptr);         // Ignored.

to get a handle to the file/directory at the resolved path.
Re:

but this may add a lot of expense for a feature that application developer should have to be aware of themselves (that is, leveldb will already support an extended length path, if provided by the end-user)

I agree that just letting the end-user provide \\?\C:\long\paths without any extra handling from leveldb might be just fine, so long as all the Windows APIs used are the Unicode versions (and specifically listed as supporting long paths; though this is most of them).

@andschwa All the Window APIs are the Unicode versions. Currently, I use FILE_FLAG_BACKUP_SEMANTICS for files and directories, but that is easily changed. As for GetFinalPathNameByHandleW, unfortunately it somewhat raises a chicken/egg problem.

If FILE_FLAG_BACKUP_SEMANTICS is working for both, don't let me tell you it's wrong! I was using GetFinalPathNameByHandle specifically for resolution of symlinks; I see where it wouldn't quite work for you here.

All the Window APIs are the Unicode versions.

Perfecto.

Hi, I wanted to ask how your work is going? It's been about six months since your last messages, but I do not see any result. I need to build a library under Windows and I do not know how.

hi tôi bận quá và cũng chưa hiểu nội dung công việc tôi phải làm là gì ?
tôi biết rất ít về công nghệ ! nếu tôi có thể làm gì đó có ích cho bạn thì
bạn hãy hướng dẫn tôi !
2018-05-01 14:29 GMT+07:00 jenokizm<EMAIL_ADDRESS>
Hi, I wanted to ask how your work is going? It's been about six months
since your last messages, but I do not see any result. I need to build a
library under Windows and I do not know how.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/leveldb/issues/519#issuecomment-385616180, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ah4_VGZLcEwyQHyJXLEB6fv3yS1ZVObzks5tuA7WgaJpZM4P8vz1
.

@jenokizm Sorry, I got extremely busy with work and have submitted a few PRs to this extent but it still needs work. My Windows development PC just arrived after breaking in March, so I should be able to finish this soon.
If you would to use this branch, it currently works on Windows:
https://github.com/Alexhuszagh/leveldb

I think the ball is currently in our court. I need to find time to reconcile the various Windows PRs we've received with what we think this should look like.

We have no timeline for this, sorry.

@Alexhuszagh @pwnall can I take the code in the PR, rebase to fix the merge conflicts, then add commits with the suggestions from @ghemawat or that was already done by @cmumford in https://github.com/cmumford/leveldb/commit/a5888f680bea87cd14d665692cff223ea48c5f89 ?

@philix Thank you very much for the offer!
We have a change for the internal codebase, which will get published after lands. The code change is very far into the review process. At this point, I don't think there's anything that external contributors can help us with.

If there's anything I can do, or anything others could do with my code to make Windows support land earlier, I'd be glad to help. In the meantime, I'm just glad Windows support seems to be approaching soon. Thanks.

@pwnall Great news. Thanks.

Hi, it's me again. I really need a Windows port to start experimenting with LevelDB.
Is https://github.com/cmumford/leveldb/commit/a5888f680bea87cd14d665692cff223ea48c5f89 the best port so far?
I just need to hack something together before the official port lands.

At this point, I'm fairly convinced that this topic won't benefit from external input until we land the Windows port. Locking so googlers can focus their limited time on landing the code.
I expect that locked conversations are frustrating to external contributors, and I'm sorry for that. I'm doing this because the subtler request above hasn't been effective.


Completion of parameters not described in some animation resources

Add description to AnimationNodeAnimation.PlayMode
Add brief description to AnimationNodeStateMachineTransition
Fix #73014 docs error

Thanks!


Meteor Cordova - Blank Map on iOS 10+ version

I'm submitting a ...  (check one with "x")
[ ] question
[x] any problem or bug report
[ ] feature request
The plugin version:  (check one with "x")
[ ] 2.0-beta3 (github)
[x] 2.0 (npm)
If you choose 'problem or bug report', please select OS:  (check one with "x")
[ ] Android
[x] iOS
cordova information:  (run $> cordova plugin list)
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Screen capture or video record:

Related code, data or error log (please format your code or data):
017-09-14 15:52:33.369577+0800 myApp[30102:317844] THREAD WARNING: ['CordovaGoogleMaps'] took '12.288818' ms. Plugin should use a background thread.
CoreData: annotation:  Failed to load optimized model at path '/Users/user/Library/Developer/CoreSimulator/Devices/23AE1D06-AEC9-4566-AD70-43F6386BC555/data/Containers/Bundle/Application/448BBB3D-B98C-4263-8599-B845DD0D3B30/myApp.app/GoogleMaps.bundle/GMSCacheStorage.momd/Storage.omo'
CoreData: annotation:  Failed to load optimized model at path '/Users/user/Library/Developer/CoreSimulator/Devices/23AE1D06-AEC9-4566-AD70-43F6386BC555/data/Containers/Bundle/Application/448BBB3D-B98C-4263-8599-B845DD0D3B30/myApp.app/GoogleMaps.bundle/GMSCacheStorage.momd/Storage.omo'
CoreData: annotation:  Failed to load optimized model at path '/Users/user/Library/Developer/CoreSimulator/Devices/23AE1D06-AEC9-4566-AD70-43F6386BC555/data/Containers/Bundle/Application/448BBB3D-B98C-4263-8599-B845DD0D3B30/myApp.app/GoogleMaps.bundle/GMSCacheStorage.momd/Storage.omo'
2017-09-14 15:52:40.755483+0800 myApp[30102:317844] Google Maps SDK for iOS version: 2.4.30121.0
2017-09-14 15:52:40.758755+0800 myApp[30102:321218] TIC Read Status [5:0x0]: 1:57

Note:

Working on all android version and 9.3 iOS version

Thanks.

Please share the project files on github.

I noticed that you use kind of old version<EMAIL_ADDRESS>Please try to reinstall the plugin (I think the latest version resolved this issue).

in your repository the latest tag is v2.0.0?

No. The master branch.

I also update the npm repository.
https://www.npmjs.com/package/cordova-plugin-googlemaps

Im my Meteor Cordova POC Project the map works on IOS 10 - 11 version. but still not working on our actual project.
This is the repo of my POC Project for cordova google map:

https://github.com/junlouiegonzales/meteor-cordova-google-maps-poc

Thank you for preparing. By the way, could you tell me how to build the shared project?
Please tell me from what command I need to install, to run the app on the device.
I have never used the meteor.

First you need to install meteorjs

https://www.meteor.com/install

Go to the project directory

type meteor npm install
after that type meteor run ios-device

Ok, thanks. I will try that tomorrow

Thank you sir .

Ok, I found the reason. Since you use the maps plugin v2.0.0, that is the problem.
I already fixed this issue, and published it.
(Currently v2.0.8)
In this screen record, the map is not displayed in the red box, because you use the cordova-plugin-statusbar.
This plugin is shift down 20px mandatory.

I adjust the plugin code a little.
The plugin now follows the webview(browser) actual size when the map view position is updated.

Please reinstall the plugin from the multiple_maps branch.
$> cd .meteor/local/cordova-build

$> cordova plugin rm cordova-plugin-googlemaps

$> cordova plugin add https://github.com/mapsplugin/cordova-plugin-googlemaps#multiple_maps --variable API_KEY_FOR_ANDROID="..." --variable API_KEY_FOR_IOS="..."

I really appreciate it sir, Thanks and Godbless :)

one more thing sir, have you tried it on android? because there was an issue during build.
error: HTMLNodeRectFs hasprivate access in MyPluginLayout       mPluginLayout.HTMLNodeRectFs.put(domId, rectF);

Oh, sorry. I forgot to update the MyPluginLayout.java when I committed the code update for another update.
I just fixed it. Please reinstall the plugin.

Ok sir. Thank you very much :)
On Sep 18, 2017 2:23 PM, "Masashi Katsumata"<EMAIL_ADDRESS>wrote:

Oh, sorry. I forgot to update the MyPluginLayout.java when I committed the
code update for another update.
I just fixed it. Please reinstall the plugin.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1738#issuecomment-330136925,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATaFjsKhaSB2KMKiCxNcZYjYUCQqn8reks5sjgxNgaJpZM4PXMQ9
.


Include triton/language/libdevice.10.bc in package data

This should make https://github.com/openai/triton/pull/562 work with setup.py install / pip install rather than just setup.py develop.
Our CI was failing with:
>       name, asm, shared_mem = _triton.code_gen.compile_ttir(backend, generator.module, device, num_warps, num_stages, extern_libs)
E       RuntimeError: Failed to load extern lib libdevice at /home/circleci/project/env/lib/python3.8/site-packages/triton/language/libdevice.10.bc

env/lib/python3.8/site-packages/triton/code_gen.py:1320: RuntimeError

cc @Jokeren @ptillet

LGTM, Thanks for the hot fix. Waiting for Phil to approve.

Thanks!


Error in Consumer("xoai").end

Getting " ERROR org.dspace.event.BasicDispatcher @ Error in Consumer("xoai").end: java.lang.NullPointerException" in the logs:
cyp@fido /project/lindat-dspace/installation/log $ grep -c "ERROR.*Error in Consumer" dspace.log.2017-06*
dspace.log.2017-06-01:0
dspace.log.2017-06-02:0
dspace.log.2017-06-03:0
dspace.log.2017-06-04:0
dspace.log.2017-06-05:0
dspace.log.2017-06-06:0
dspace.log.2017-06-07:0
dspace.log.2017-06-08:0
dspace.log.2017-06-09:0
dspace.log.2017-06-10:0
dspace.log.2017-06-11:0
dspace.log.2017-06-12:0
dspace.log.2017-06-13:0
dspace.log.2017-06-14:0
dspace.log.2017-06-15:0
dspace.log.2017-06-16:132
dspace.log.2017-06-17:28
dspace.log.2017-06-18:0
dspace.log.2017-06-19:2
dspace.log.2017-06-20:70
dspace.log.2017-06-21:47
dspace.log.2017-06-22:0
dspace.log.2017-06-23:0

Not sure what this is about or how it affects the user.

Hmm, although I still don't think this really affects the user, we're actually getting more of these in the last week or so. If I recall correctly, Lindat is also getting some errors like this.

you see, the consumer reacts to all these (https://github.com/ufal/clarin-dspace/blob/clarin/dspace/config/dspace.cfg#L808) events. Some of them are fired when you start/save a submission, but the indexer was written to process already submitted items. So when you get to https://github.com/ufal/clarin-dspace/blob/clarin/dspace-oai/src/main/java/org/dspace/xoai/util/ItemUtils.java#L294 where it naively expects that every item has an owning collection...it fails.
There might be other triggers than that, but this one linked to submissions might be why you suddenly see more errors...
Indeed these shouldn't bother the users as they'll never see it


check if can be made better (obtain lvl xp)

feels like a slow method to obtain the data. method to obtain might already exist within RL
https://github.com/LowieN-1848537/SteelseriesGamesense/blob/master/src/main/java/com/example/GamesensePlugin.java#L195-L215

found an existing method in the api to find the same stats, replacement done


Implement parallel I/O

This will require either successfully installing netcdf-cxx4 over netcdf-c4 built for parallel I/O or removing all uses of netcdfcpp.

Notes:
netcdfcxx does not support parallel I/O.
pnetcdf provides parallel I/O through MPI for classic format files only.
netcdf-c <IP_ADDRESS> (current stable build) is missing an include needed for building with parallel I/O support. This is apparently fixed in their current master branch.

Resolved by merge commit SHA 8f2711ddf493bdacf4b0296939962e3093fa5f35


Look into TextEditor::scan

It might be possible to replace the current non-public usage with the TextEditor::scan method, or something related.

I believe the code this was referencing was removed in #35.


Report including not existent licenses

Here I got that license in the Apprendix, but that license doesn't exist.
I'm running using docker with the following flags
report -f PdfTemplate -i <input_file> -o <output_folder>
Also there are other no existent licenses with LicenceRef-* name
cc: @dgutson

Here I got that license in the Apprendix, but that license doesn't exist.

I guess that's supposed to say that no license text is displayed. The license / license name does exist.
Is ScanCode installed on the machine you run the report command on? Because ORT gets the ttexts for ScanCode-specific license names from the ScanCode installation directory.

I'm using docker builded from source code as the getting started guide says....

git clone <this_repo>
cd ort
docker build -t ort .

I don't know If I must do anything else in the docker image...

@Franco0700 does the problem persist? Can you provide an example project to scan that exposes the issue?

Closing this as a duplicate of https://github.com/oss-review-toolkit/ort/issues/8147.


Feature/224 sign transaction

need to build a workaround to this issue
https://github.com/Tonomy-Foundation/Tonomy-ID/issues/636
this is reported to leap here
https://github.com/AntelopeIO/leap/issues/1131


Integrated Terminal not opening

Issue Type: Bug
on pressing ctrl + `, the integrated terminal does not open while it opens the command powershell.
VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:35:15.005Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.85GB (9.07GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

composer-support-client
Hyp
0.19.12

python
ms-
2019.9.34911

remote-wsl
ms-
0.39.5

The PowerShell terminal must capture the keypress before VS Code receives it. Try to disable the shortcut in the PowerShell terminal settings or assign a different keybinding to it in VS Code.

Hi,
This does not seem to work. I changed it to another shortcut but still its opening powershell instead of integrated terminal.
I also deleted the shortcut in settings but it is still opening the powershell instead of integrated terminal.
Thanks,
Amit
From: Christof Marti<EMAIL_ADDRESS>Sent: Friday, September 27, 2019 3:45 AM
To: microsoft/vscode<EMAIL_ADDRESS>Cc: Amit Pandey<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/vscode] Integrated Terminal not opening (#81524)
The PowerShell terminal must capture the keypress before VS Code receives it. Try to disable the shortcut in the PowerShell terminal settings or assign a different keybinding to it in VS Code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/81524?email_source=notifications&email_token=AIQT2HFMPCDCU3LOD6WUNKLQLW2WZA5CNFSM4I3A3R2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7YB3NY#issuecomment-535829943 , or mute the thread https://github.com/notifications/unsubscribe-auth/AIQT2HBYQCPAIDPGSNC3S7LQLW2WZANCNFSM4I3A3R2A .  https://github.com/notifications/beacon/AIQT2HB32KZT4TNC6QRT45LQLW2WZA5CNFSM4I3A3R2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7YB3NY.gif

Open the keybindings editor and search for Toggle Integrated Terminall to check what the current assignment is:

Sometimes this is auto-reassigned to Ctrl + ' (tick ' instead of backtick `).

Hi Christof,
There is no shortcut assigned as of now:
From: Christof Marti<EMAIL_ADDRESS>Sent: Friday, September 27, 2019 8:47 AM
To: microsoft/vscode<EMAIL_ADDRESS>Cc: Amit Pandey<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/vscode] Integrated Terminal not opening (#81524)
Open the keybindings editor and search for Toggle Integrated Terminall to check what the current assignment is:
https://user-images.githubusercontent.com/9205389/65769934-3037f280-e135-11e9-91d2-22e91ed25f21.png
Sometimes this is auto-reassigned to Ctrl + ' (tick ' instead of backtick `).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/81524?email_source=notifications&email_token=AIQT2HBMRLGDHMLYT77HHBLQLX6FZA5CNFSM4I3A3R2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7YYY4A#issuecomment-535923824 , or mute the thread https://github.com/notifications/unsubscribe-auth/AIQT2HBO63YYFSJJBYL2EODQLX6FZANCNFSM4I3A3R2A .  https://github.com/notifications/beacon/AIQT2HBZFZSOC7P2465IJW3QLX6FZA5CNFSM4I3A3R2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7YYY4A.gif

@amit420102 Unfortunately images don't make it through email. Could you attach them directly on GitHub's website?
If there is none assigned, try assigning Ctrl + ' to it.

i have added keyboard shortcut of ctrl + `, but still on pressing the shortcut it opens powershell instead of integrated terminal. I have attached the images

Try adding the shortcut with a single quote (') instead of a backtick (`).

hi Christof,
I am getting same result, its opening the powershell.
Thanks,
Amit
On Sat, Sep 28, 2019 at 7:08 AM Christof Marti<EMAIL_ADDRESS>wrote:

Try adding the shortcut with a single quote (') instead of a backtick (`).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/81524?email_source=notifications&email_token=AIQT2HBHSCJFS4Y6NSCBS2LQL43JVA5CNFSM4I3A3R2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD72WVRI#issuecomment-536177349,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIQT2HCBZ32EZNPWMV5BWBDQL43JVANCNFSM4I3A3R2A
.

Hi Christof,
I found the solution, turning off ConPTY worked for me.
I can now have integrated terminal opening in the Visual studio code and not in a new window.
Thanks,
Amit
From: Christof Marti<EMAIL_ADDRESS>Sent: Saturday, September 28, 2019 7:08 AM
To: microsoft/vscode<EMAIL_ADDRESS>Cc: Amit Pandey<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/vscode] Integrated Terminal not opening (#81524)
Try adding the shortcut with a single quote (') instead of a backtick (`).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/81524?email_source=notifications&email_token=AIQT2HBHSCJFS4Y6NSCBS2LQL43JVA5CNFSM4I3A3R2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD72WVRI#issuecomment-536177349 , or mute the thread https://github.com/notifications/unsubscribe-auth/AIQT2HCBZ32EZNPWMV5BWBDQL43JVANCNFSM4I3A3R2A .  https://github.com/notifications/beacon/AIQT2HDC42HZFHATA4MSJJ3QL43JVA5CNFSM4I3A3R2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD72WVRI.gif

Closing as solved. Thanks.