Clearing schema entries after run()

An issue came up while I was working on #965 that I think points at a larger conceptual issue. The problem comes when we perform multiple run() calls in succession on the same chip object.
With my new scheduler changes, a second run() call would fail because the 'flowstatus', ..., 'status' bit indicates the import step is "complete" (from the first run), causing the next task to launch too soon. I don't think there's a clean way to ignore this while also handling a partial steplist. In the meantime, I added a hack to that PR to clear these 'status' values after run.
Beyond this functional problem however, I think there's also a subtle issue here with regards to provenance. When you perform a second run(), new metrics and records will get stored side-by-side with the old ones. In most cases, old values will be totally overwritten, or the step lists of each run() will be totally orthogonal, so there's no real issue. However, if there is some step/index overlap things will get muddled in terms of what comes from where.
I think it would be worthwhile to fix this up. I have a few ideas:

We already have the 'history' config, so we could just clear everything that is set during the run ('metrics, 'record', 'flowstatus') and force all future lookups to read from history based on job name. I wonder if we can even have chip.get(...) transparently read from history based on the current job name, although that seems potentially dangerous.
Go back to having 'metric', 'record', and 'flowstatus' have per-job keys. Makes it a little less typing to access old values, but I think this is a little redundant with the 'history' dict.

Good points. Not sure I see the larger conceptual issue here. What is the test case where this came up?

The scope field is controls copying parameters to history, so no information should get lost.
There should nothing left in the current state when starting a run(). I like the idea of clearing out the record/metrics/flowstatus at the beginning of a run. (the "reentrant" use of run() on remote might affect implementation?)
The history reflects previous jobs, anything non history reflects the current state, so having the job key mixxed into some parameters and not others feels like a partial solution. The "scope" filed gives us per parameter granularity on controlling the history of the parameter.
The use of case of running through partial step lists on the same job run (one step at a time or "resume") would require the flowstatus to be retained between runs for the same job. What is the use case here?
How are new metrics recorded "side by side", wouldn't they be overwritten the old values on a per step/index basis?

One of the test cases that broke with the new "flowstatus" scheme is: https://github.com/siliconcompiler/siliconcompiler/blob/main/examples/gcd/gcd_skywater.py. "Larger conceptual issue" might have been a bit extreme, what I meant by that is that while the "flowstatus" issue is functional, the broader issue with metrics/record is conceptual (and hasn't been a problem yet).

The scope field is controls copying parameters to history, so no information should get lost.

Agreed, not worried about info getting lost, just confusion about where info comes from.

I like the idea of clearing out the record/metrics/flowstatus at the beginning of a run.

I'm not sure if we can do this, since that makes it impossible to continue a run by reading in a previous manifest, or making a second run() call with a partial steplist.

The history reflects previous jobs, anything non history reflects the current state, so having the job key mixxed into some parameters and not others feels like a partial solution. The "scope" filed gives us per parameter granularity on controlling the history of the parameter.

Agreed!

The use of case of running through partial step lists on the same job run (one step at a time or "resume") would require the flowstatus to be retained between runs for the same job. What is the use case here?

That's a good point, my hack would break that use case. The one I'm trying to fix (shown in the example linked above) is running a totally different flow on the same chip object.

How are new metrics recorded "side by side", wouldn't they be overwritten the old values on a per step/index basis?

Yeah, but I'm not sure the step/index would be enough to disambiguate. For example, suppose we added some basic metrics to our Surelog based import, and a user runs asicflow on their design. Then they run another flow with a built-in"nop" for import. The "import" metrics would include the minimal runtime for nop, but also the metrics from Surelog. Probably not a huge deal in this case since someone could figure out what's going on, but illustrates the point that you might have step/index overlap between different flows, and different tools report different metrics so not everything might get overridden.
Those are good points overall, I've realized now that naively clearing things before OR after run() is problematic since it breaks re-running something with a partial steplist using the same chip object. I'll do some brainstorming to come up with a better solution, it will probably have to involve some sort of job name check, to determine if we're still working on an existing run or something fresh.

I'm not sure if we can do this, since that makes it impossible to continue a run by reading in a previous manifest, or making a second run() call with a partial steplist.

If we can figure out the last step of the graph executed in the last run() (which should be possible by checking the existence of output .json files), then we "should" be able to safely decide if the run() state should be cleared or continued. The alternative would be to possible make it user controlled with something like a -resume flag.  Still, we should be mindful of the steplist and the use cases supported. There are plenty of built in limitations with the steplist. For example,  trying to run a step before all the previous dependencies have executed correctly.

Then they run another flow with a built-in"nop" for import.

I think we still have some work to do with the modular flowgraphs, but each step within a named flow is unique, so there is no rerunning of import steps.

I'd say this is fixed by #979.


Fixed issue with "StudyingForYears" application status

Some of the changes are not connected to my issue I've found them during my investigation and I decided to fix them. In InstitutionHierarchyServiceTest there was unused mock and in ChildControllerTests there were extra tabs


[OpenAI] Modes required to be public in Java SDK

These classes are already in the public /model folder, we should keep them out in Java at least.

I am updating typespec-java to 0.11.0 (which include Union as BinaryData) https://github.com/Azure/azure-sdk-for-java/pull/37629
I will try to see if I need some change to client.tsp, built upon this PR.

@lmazuel Can I merge this PR? @joseharriaga opened a PR  in .NET side to fix the failure in .net.


chore: upgrade cross-fetch to prevent Denial of Service vulnerability

Running yarn audit in my project, I got this vulnerability:

(low) Denial of Service
Module: node-fetch
Installed version: 2.6.0
Published: 2020-09-10, 10:55:53 a.m.
Reported by: Unknown
CWE-400
CVE-2020-15168
Vulnerable: < 2.6.1 || >= 3.0.0-beta.1 < 3.0.0-beta.9
Patched: >=2.6.1 <3.0.0-beta.1|| >= 3.0.0-beta.9
CVSS: 3
Overview
Node Fetch did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure.
For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.
Remediation
Upgrade to version 2.6.1 or 3.0.0-beta.9
References
https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r
Reasons this module exists
link-preview-js>cross-fetch>node-fetch

To fix, I just had to bump cross-fetch to 3.0.6 which has the correct version of node-fetch: "2.6.1"

Cheers, I will release an upgraded package later

Thanks @andresouza! new package version is released 2.1.0

Awesome! Thank you! 💪


add vote doc

Signed-off-by: liwen-tj<EMAIL_ADDRESS>
What is the purpose of the change

Related to #133

Closes #

Brief change log

No changes.

Checklist

Are tests written for added code?

[ ] Yes
[x] No because: only add doc

Did you introduce any new dependencies?

[x] No
[ ] Yes

Dependency:
Reason: only add doc

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

Please move vote component to Component directory, files that need to be modified include:

/docs/component/index.md
/docs/component/vote.md
/docs/_sidebar.md
/docs/zh-cn/_sidebar.md
/docs/zh-cn/component/vote.md
/docs/zh-cn/component/index.md


Omnisharp updates without permission

Issue Description
the C# extension ignores extension update rules set elsewhere and updates automatically.  For those globally who lack access to broadband, this is an impediment to work as the server is shut down during the long download process.
Steps to Reproduce

Open VS Code
Watch the slow progression of dots in the C# output window

Expected Behavior
Obey global settings for VS Code extension updates
Actual Behavior
Non-compliance
Logs
Getting latest OmniSharp version information
Downloading package 'Latest OmniSharp Version Information' (1 KB).................... Done!
Installing OmniSharp Version = 1.34.6-beta.17...
Platform: linux, x86_64, name=ubuntu, version=19.04

Downloading package 'OmniSharp for Linux (x64), Version = 1.34.6-beta.17' (42216 KB)..................

OmniSharp log
[empty]
C# log
Getting latest OmniSharp version information
Downloading package 'Latest OmniSharp Version Information' (1 KB).................... Done!
Installing OmniSharp Version = 1.34.6-beta.17...
Platform: linux, x86_64, name=ubuntu, version=19.04

Downloading package 'OmniSharp for Linux (x64), Version = 1.34.6-beta.17' (42216 KB)..................

Environment information
VSCode version: 1.39.1
C# Extension: 1.21.4
Mono Information
        OmniSharp using built-in mono
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100
 Commit:    04339c3a26
Runtime Environment:
OS Name:     ubuntu
OS Version:  19.04
OS Platform: Linux
RID:         ubuntu.19.04-x64
Base Path:   /usr/share/dotnet/sdk/3.0.100/
Host (useful for support):
Version: 3.0.0
Commit:  95a0a61858
.NET Core SDKs installed:
3.0.100 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

auto-using
Fudge
0.7.9

clang-format
xaver
1.9.0

cmake
twxs
0.0.17

cmake-tools
vector-of-bool
1.1.3

cmake-tools-helper
maddouri
0.2.1

cpptools
ms-vscode
0.25.1

csharp
ms-vscode
1.21.4

dark-plus-material
vangware
2.1.1

EditorConfig
EditorConfig
0.14.1

python
ms-python
2019.10.41019

rainbow-csv
mechatroner
1.3.1

restructuredtext
lextudio
114.0.0

vscode-icons
vscode-icons-team
9.4.0

vscode-postgresql
ms-ossdata
0.2.0

It's not the extension that updates, but the OmniSharp server bundled with it. I presume you have "omnisharp.path": "latest" in your settings which means you have explicitly opted into pulling the latest OmniSharp prerelease build from master branch.
You should remove that, then the OmniSharp version will stay pinned to that which ships with the extension (and extension will obey the update settings as you mentioned).

I rolled back to using 1.21.4 and then 1.21.3.
No change, same issue.


Typo "Postgre SQL"→"PostgreSQL"

https://learn.microsoft.com/en-us/azure/synapse-analytics/spark/apache-spark-secure-credentials-with-tokenlibrary?pivots=programming-language-python
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/synapse-analytics/spark/apache-spark-secure-credentials-with-tokenlibrary.md
#PingMSFTDocs

Thanks, @hyoshioka0128 !


Handle blocktests

Issue Link
Added a generic blocktests support for blocklist and quarantined tests
Description
Added a generic blocktests support for blocklist and quarantined tests
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Test With runners and postman
[ ] Test B

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Trusting the 2 reviewers. Merging.


add compress in fluentbit output es

Is your feature request related to a problem? Please describe.
fluentbit support compress payload in es output
(https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch)[https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch].
Will it be supported in operator in the future?
Describe the solution you'd like
like configuration below
----
apiVersion: fluentbit.fluent.io/v1alpha2
kind: ClusterOutput
metadata:
  labels:
    fluentbit.fluent.io/enabled: "true"
    fluentbit.fluent.io/mode: "fluentbit-only"
  name: es
spec:
  es:
     compress: gzip

Additional context
No response

Hi,
I interested to work on this, Could you please assign to me?

Hi, I interested to work on this, Could you please assign to me?

sure，thanks

Hi @wenchajun,
Could you please advise and review above changes?


ionic - build failed on IOS when using https://github.com/phonegap-build/PushPlugin.git plugin

ionic build failed with IOS if using PushPlugin but on android work perfectly.
Here is the error message after build failed:
** BUILD FAILED **
The following build commands failed:
CompileC build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/PushPlugin.o Book\ Football\ Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
Error: Error code 65 for command: xcodebuild with args: -xcconfig,/Users/ceeb/desktop/ionic/fbob/platforms/ios/cordova/build-debug.xcconfig,-project,Book Football Field.xcodeproj,ARCHS=i386,-target,Book Football Field,-configuration,Debug,-sdk,iphonesimulator,build,VALID_ARCHS=i386,CONFIGURATION_BUILD_DIR=/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator,SHARED_PRECOMPS_DIR=/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/sharedpch
Please help because I stuck on this issue for a week
Thanks

@aceeblaj the actual cause of your build failure is above that ** BUILD FAILED ** line. Seeing that would help in answering your question.

Below log is what you need.
CeebLajs-MacBook-Pro:fbob ceeb$ ionic emulate ios
Running command: /Users/ceeb/desktop/ionic/fbob/hooks/after_prepare/010_add_platform_class.js /Users/ceeb/desktop/ionic/fbob
add to body class: platform-ios
Building project  : /Users/ceeb/desktop/ionic/fbob/platforms/ios/Book Football Field.xcodeproj
Configuration : Debug
Platform      : emulator
Build settings from command line:
ARCHS = i386
CONFIGURATION_BUILD_DIR = /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator
SDKROOT = iphonesimulator9.2
SHARED_PRECOMPS_DIR = /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/sharedpch
VALID_ARCHS = i386
Build settings from configuration file '/Users/ceeb/desktop/ionic/fbob/platforms/ios/cordova/build-debug.xcconfig':
CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES = YES
CODE_SIGN_IDENTITY = iPhone Developer
ENABLE_BITCODE = NO
GCC_PREPROCESSOR_DEFINITIONS = DEBUG=1
HEADER_SEARCH_PATHS = "$(TARGET_BUILD_DIR)/usr/local/lib/include" "$(OBJROOT)/UninstalledProducts/include" "$(OBJROOT)/UninstalledProducts/$(PLATFORM_NAME)/include" "$(BUILT_PRODUCTS_DIR)"
IPHONEOS_DEPLOYMENT_TARGET = 8.0
OTHER_LDFLAGS = -ObjC
SWIFT_OBJC_BRIDGING_HEADER = $(PROJECT_DIR)/$(PROJECT_NAME)/Bridging-Header.h
TARGETED_DEVICE_FAMILY = 1,2
=== BUILD TARGET CordovaLib OF PROJECT CordovaLib WITH CONFIGURATION Debug ===
Check dependencies
=== BUILD TARGET Book Football Field OF PROJECT Book Football Field WITH CONFIGURATION Debug ===
Check dependencies
PhaseScriptExecution Copy\ www\ directory build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Script-304B58A110DAC018002A0835.sh
cd /Users/ceeb/Desktop/ionic/fbob/platforms/ios
/bin/sh -c "/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Script-304B58A110DAC018002A0835.sh"
CompileAssetCatalog /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book\ Football\ Field.app Book\ Football\ Field/Images.xcassets
cd /Users/ceeb/Desktop/ionic/fbob/platforms/ios
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/mysql/bin:~/.composer/vendor/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/Users/ceeb/Desktop/android::~/.composer/vendor/bin"
/Applications/Xcode.app/Contents/Developer/usr/bin/actool --output-format human-readable-text --notices --warnings --export-dependency-info /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/assetcatalog_dependencies --output-partial-info-plist /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/assetcatalog_generated_info.plist --app-icon AppIcon --launch-image LaunchImage --compress-pngs --enable-on-demand-resources YES --target-device iphone --target-device ipad --minimum-deployment-target 8.0 --platform iphonesimulator --compile /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book\ Football\ Field.app /Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book\ Football\ Field/Images.xcassets
/* com.apple.actool.document.warnings /
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./AppIcon.appiconset: warning: A 83.5x83.5@2x app icon is required for iPad apps targeting iOS 9.0 and later
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./AppIcon.appiconset/(null)[2d][icon-60.png]: warning: The app icon set "AppIcon" has an unassigned child.
/ com.apple.actool.document.notices /
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./AppIcon.appiconset/[iphone][57x57][][][1x]: notice: 57x57 app icons only apply to iPhone apps targeting releases of iOS prior to 7.0
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./AppIcon.appiconset/[iphone][57x57][][][2x]: notice: 57x57@2x app icons only apply to iPhone apps targeting releases of iOS prior to 7.0
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./AppIcon.appiconset/[ipad][50x50][][][1x]: notice: 50x50 iPad spotlight icons only apply to iPad apps targeting releases of iOS prior to 7.0
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./AppIcon.appiconset/[ipad][50x50][][][2x]: notice: 50x50 iPad spotlight icons only apply to iPad apps targeting releases of iOS prior to 7.0
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./AppIcon.appiconset/[ipad][72x72][][][1x]: notice: 72x72 app icons only apply to iPad apps targeting releases of iOS prior to 7.0
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./AppIcon.appiconset/[ipad][72x72][][][2x]: notice: 72x72@2x app icons only apply to iPad apps targeting releases of iOS prior to 7.0
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./LaunchImage.launchimage/[iphone][736h][3x][portrait][full-screen][8.0]: notice: This launch image only applies to iOS 6.x and prior but the minimum deployment is 7.0 or later.
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./LaunchImage.launchimage/[iphone][736h][3x][landscape][full-screen][8.0]: notice: This launch image only applies to iOS 6.x and prior but the minimum deployment is 7.0 or later.
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./LaunchImage.launchimage/[iphone][667h][2x][portrait][full-screen][8.0]: notice: This launch image only applies to iOS 6.x and prior but the minimum deployment is 7.0 or later.
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./LaunchImage.launchimage/[iphone][][1x][portrait][full-screen][]: notice: This launch image only applies to iOS 6.x and prior but the minimum deployment is 7.0 or later.
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./LaunchImage.launchimage/[iphone][][2x][portrait][full-screen][]: notice: This launch image only applies to iOS 6.x and prior but the minimum deployment is 7.0 or later.
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./LaunchImage.launchimage/[iphone][retina4][2x][portrait][full-screen][]: notice: This launch image only applies to iOS 6.x and prior but the minimum deployment is 7.0 or later.
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./LaunchImage.launchimage/[ipad][][1x][portrait][full-screen][]: notice: This launch image only applies to iOS 6.x and prior but the minimum deployment is 7.0 or later.
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Images.xcassets:./LaunchImage.launchimage/[ipad][][2x][portrait][full-screen][]: notice: This launch image only applies to iOS 6.x and prior but the minimum deployment is 7.0 or later.
/ com.apple.actool.compilation-results */
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/AppIcon29x29.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/AppIcon57x57.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/AppIcon29x29~ipad.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/AppIcon40x40~ipad.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/AppIcon50x50~ipad.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/AppIcon72x72~ipad.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/AppIcon76x76~ipad.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/LaunchImage-700-Portrait~ipad.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/LaunchImage-700-Landscape~ipad.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/LaunchImage.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football Field.app/LaunchImage-Portrait~ipad.png
/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book Football<EMAIL_ADDRESS>/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book Football Field.build/Debug-iphonesimulator/Book Football Field.build/assetcatalog_generated_info.plist
ProcessInfoPlistFile /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book\ Football\ Field.app/Info.plist Book\ Football\ Field/Book\ Football\ Field-Info.plist
cd /Users/ceeb/Desktop/ionic/fbob/platforms/ios
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/mysql/bin:~/.composer/vendor/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/Users/ceeb/Desktop/android::~/.composer/vendor/bin"
builtin-infoPlistUtility /Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book\ Football\ Field/Book\ Football\ Field-Info.plist -genpkginfo /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book\ Football\ Field.app/PkgInfo -expandbuildsettings -format binary -platform iphonesimulator -additionalcontentfile /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/MainViewController-PartialInfo.plist -additionalcontentfile /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/DatePicker-PartialInfo.plist -additionalcontentfile /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/assetcatalog_generated_info.plist -o /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/Book\ Football\ Field.app/Info.plist
CompileC build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/CDVLocation.o Book\ Football\ Field/Plugins/cordova-plugin-geolocation/CDVLocation.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
cd /Users/ceeb/Desktop/ionic/fbob/platforms/ios
export LANG=en_US.US-ASCII
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/mysql/bin:~/.composer/vendor/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/Users/ceeb/Desktop/android::~/.composer/vendor/bin"
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch i386 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=c99 -fobjc-arc -fmodules -gmodules -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session-file=/var/folders/wg/_wz53njd5jb9txstfctwh88m0000gp/C/org.llvm.clang/ModuleCache/Session.modulevalidation -fmodules-validate-once-per-build-session -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-implicit-atomic-properties -Wno-arc-repeated-use-of-weak -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-shorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wno-deprecated-implementations -DDEBUG=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -mios-simulator-version-min=8.0 -g -fvisibility=hidden -Wno-sign-conversion -fobjc-abi-version=2 -fobjc-legacy-dispatch -iquote /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-generated-files.hmap -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-own-target-headers.hmap -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-all-target-headers.hmap -iquote /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-project-headers.hmap -I/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include -I/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/usr/local/lib/include -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/UninstalledProducts/include -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/UninstalledProducts/iphonesimulator/include -I/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/DerivedSources/i386 -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/DerivedSources -F/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator -FBook\ Football\ Field/Plugins/cordova-plugin-webserver -include /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/sharedpch/Book\ Football\ Field-Prefix-dsjxmyucneteuccvniebevbfqntr/Book\ Football\ Field-Prefix.pch -MMD -MT dependencies -MF /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/CDVLocation.d --serialize-diagnostics /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/CDVLocation.dia -c /Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book\ Football\ Field/Plugins/cordova-plugin-geolocation/CDVLocation.m -o /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/CDVLocation.o
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/cordova-plugin-geolocation/CDVLocation.m:76:31: warning: 'kCLAuthorizationStatusAuthorized' is deprecated: first deprecated in iOS 8.0 - Use kCLAuthorizationStatusAuthorizedAlways [-Wdeprecated-declarations]
return (authStatus == kCLAuthorizationStatusAuthorized) || (authStatus == kCLAuthorizationStatusNotDetermined);
^
In module 'CoreLocation' imported from /Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/cordova-plugin-geolocation/CDVLocation.h:21:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/CoreLocation.framework/Headers/CLLocationManager.h:65:2: note: 'kCLAuthorizationStatusAuthorized' has been explicitly marked deprecated here
kCLAuthorizationStatusAuthorized NS_ENUM_DEPRECATED(10_6, NA, 2_0, 8_0, "Use kCLAuthorizationStatusAuthorizedAlways") __TVOS_PROHIBITED __WATCHOS_PROHIBITED = kCLAuthorizationStatusAuthorizedAlways
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/cordova-plugin-geolocation/CDVLocation.m:91:42: warning: 'locationServicesEnabled' is deprecated: first deprecated in iOS 4.0 [-Wdeprecated-declarations]
return [(id)self.locationManager locationServicesEnabled];
^
In module 'CoreLocation' imported from /Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/cordova-plugin-geolocation/CDVLocation.h:21:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/CoreLocation.framework/Headers/CLLocationManager.h:177:37: note: property 'locationServicesEnabled' is declared deprecated here
@property(readonly, nonatomic) BOOL locationServicesEnabled __OSX_AVAILABLE_BUT_DEPRECATED(__MAC_NA,__MAC_NA,__IPHONE_2_0,__IPHONE_4_0) __TVOS_PROHIBITED __WATCHOS_PROHIBITED;
^
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/CoreLocation.framework/Headers/CLLocationManager.h:177:37: note: 'locationServicesEnabled' has been explicitly marked deprecated here
CompileC build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/AppDelegate+notification.o Book\ Football\ Field/Plugins/com.phonegap.plugins.PushPlugin/AppDelegate+notification.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
cd /Users/ceeb/Desktop/ionic/fbob/platforms/ios
export LANG=en_US.US-ASCII
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/mysql/bin:~/.composer/vendor/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/Users/ceeb/Desktop/android::~/.composer/vendor/bin"
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch i386 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=c99 -fobjc-arc -fmodules -gmodules -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session-file=/var/folders/wg/_wz53njd5jb9txstfctwh88m0000gp/C/org.llvm.clang/ModuleCache/Session.modulevalidation -fmodules-validate-once-per-build-session -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-implicit-atomic-properties -Wno-arc-repeated-use-of-weak -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-shorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wno-deprecated-implementations -DDEBUG=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -mios-simulator-version-min=8.0 -g -fvisibility=hidden -Wno-sign-conversion -fobjc-abi-version=2 -fobjc-legacy-dispatch -iquote /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-generated-files.hmap -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-own-target-headers.hmap -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-all-target-headers.hmap -iquote /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-project-headers.hmap -I/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include -I/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/usr/local/lib/include -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/UninstalledProducts/include -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/UninstalledProducts/iphonesimulator/include -I/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/DerivedSources/i386 -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/DerivedSources -F/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator -FBook\ Football\ Field/Plugins/cordova-plugin-webserver -include /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/sharedpch/Book\ Football\ Field-Prefix-dsjxmyucneteuccvniebevbfqntr/Book\ Football\ Field-Prefix.pch -MMD -MT dependencies -MF /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/AppDelegate+notification.d --serialize-diagnostics /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/AppDelegate+notification.dia -c /Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book\ Football\ Field/Plugins/com.phonegap.plugins.PushPlugin/AppDelegate+notification.m -o /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/AppDelegate+notification.o
CompileC build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/PushPlugin.o Book\ Football\ Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
cd /Users/ceeb/Desktop/ionic/fbob/platforms/ios
export LANG=en_US.US-ASCII
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/mysql/bin:~/.composer/vendor/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/Users/ceeb/Desktop/android::~/.composer/vendor/bin"
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch i386 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=c99 -fobjc-arc -fmodules -gmodules -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session-file=/var/folders/wg/_wz53njd5jb9txstfctwh88m0000gp/C/org.llvm.clang/ModuleCache/Session.modulevalidation -fmodules-validate-once-per-build-session -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-implicit-atomic-properties -Wno-arc-repeated-use-of-weak -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-shorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wno-deprecated-implementations -DDEBUG=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -mios-simulator-version-min=8.0 -g -fvisibility=hidden -Wno-sign-conversion -fobjc-abi-version=2 -fobjc-legacy-dispatch -iquote /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-generated-files.hmap -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-own-target-headers.hmap -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-all-target-headers.hmap -iquote /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Book\ Football\ Field-project-headers.hmap -I/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include -I/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/usr/local/lib/include -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/UninstalledProducts/include -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/UninstalledProducts/iphonesimulator/include -I/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/DerivedSources/i386 -I/Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/DerivedSources -F/Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator -FBook\ Football\ Field/Plugins/cordova-plugin-webserver -include /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/sharedpch/Book\ Football\ Field-Prefix-dsjxmyucneteuccvniebevbfqntr/Book\ Football\ Field-Prefix.pch -MMD -MT dependencies -MF /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/PushPlugin.d --serialize-diagnostics /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/PushPlugin.dia -c /Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book\ Football\ Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m -o /Users/ceeb/Desktop/ionic/fbob/platforms/ios/build/Book\ Football\ Field.build/Debug-iphonesimulator/Book\ Football\ Field.build/Objects-normal/i386/PushPlugin.o
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:55:5: warning: 'UIRemoteNotificationType' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
UIRemoteNotificationType notificationTypes = UIRemoteNotificationTypeNone;
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:67:32: note: 'UIRemoteNotificationType' has been explicitly marked deprecated here
typedef NS_OPTIONS(NSUInteger, UIRemoteNotificationType) {
^
In module 'Foundation' imported from /Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.h:26:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:281:52: note: expanded from macro 'NS_OPTIONS'
#define NS_OPTIONS(_type, _name) CF_OPTIONS(_type, _name)
^
In module 'Foundation' imported from /Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.h:26:
In module 'CoreFoundation' imported from /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFAvailability.h:107:65: note: expanded from macro 'CF_OPTIONS'
#define CF_OPTIONS(_type, _name) enum _name : _type _name; enum _name : _type
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:55:50: warning: 'UIRemoteNotificationTypeNone' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
UIRemoteNotificationType notificationTypes = UIRemoteNotificationTypeNone;
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:68:5: note: 'UIRemoteNotificationTypeNone' has been explicitly marked deprecated here
UIRemoteNotificationTypeNone    = 0,
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:64:34: warning: 'UIRemoteNotificationTypeBadge' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
notificationTypes |= UIRemoteNotificationTypeBadge;
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:69:5: note: 'UIRemoteNotificationTypeBadge' has been explicitly marked deprecated here
UIRemoteNotificationTypeBadge   = 1 << 0,
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:71:30: warning: 'UIRemoteNotificationTypeBadge' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
notificationTypes |= UIRemoteNotificationTypeBadge;
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:69:5: note: 'UIRemoteNotificationTypeBadge' has been explicitly marked deprecated here
UIRemoteNotificationTypeBadge   = 1 << 0,
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:80:34: warning: 'UIRemoteNotificationTypeSound' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
notificationTypes |= UIRemoteNotificationTypeSound;
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:70:5: note: 'UIRemoteNotificationTypeSound' has been explicitly marked deprecated here
UIRemoteNotificationTypeSound   = 1 << 1,
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:87:30: warning: 'UIRemoteNotificationTypeSound' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
notificationTypes |= UIRemoteNotificationTypeSound;
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:70:5: note: 'UIRemoteNotificationTypeSound' has been explicitly marked deprecated here
UIRemoteNotificationTypeSound   = 1 << 1,
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:96:34: warning: 'UIRemoteNotificationTypeAlert' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
notificationTypes |= UIRemoteNotificationTypeAlert;
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:71:5: note: 'UIRemoteNotificationTypeAlert' has been explicitly marked deprecated here
UIRemoteNotificationTypeAlert   = 1 << 2,
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:103:30: warning: 'UIRemoteNotificationTypeAlert' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
notificationTypes |= UIRemoteNotificationTypeAlert;
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:71:5: note: 'UIRemoteNotificationTypeAlert' has been explicitly marked deprecated here
UIRemoteNotificationTypeAlert   = 1 << 2,
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:109:26: warning: 'UIRemoteNotificationTypeNewsstandContentAvailability' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
notificationTypes |= UIRemoteNotificationTypeNewsstandContentAvailability;
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:72:5: note: 'UIRemoteNotificationTypeNewsstandContentAvailability' has been explicitly marked deprecated here
UIRemoteNotificationTypeNewsstandContentAvailability = 1 << 3,
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:116:30: warning: 'UIRemoteNotificationTypeNone' is deprecated: first deprecated in iOS 8.0 - Use UIUserNotificationType for user notifications and registerForRemoteNotifications for receiving remote notifications instead. [-Wdeprecated-declarations]
if (notificationTypes == UIRemoteNotificationTypeNone)
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:68:5: note: 'UIRemoteNotificationTypeNone' has been explicitly marked deprecated here
UIRemoteNotificationTypeNone    = 0,
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:127:42: warning: 'registerForRemoteNotificationTypes:' is deprecated: first deprecated in iOS 8.0 - Please use registerForRemoteNotifications and registerUserNotificationSettings: instead [-Wdeprecated-declarations]
[[UIApplication sharedApplication] registerForRemoteNotificationTypes:notificationTypes];
^
In module 'UIKit' imported from /Users/ceeb/desktop/ionic/fbob/platforms/ios/build/emulator/include/Cordova/CDVAvailabilityDeprecated.h:20:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:190:1: note: 'registerForRemoteNotificationTypes:' has been explicitly marked deprecated here

(void)registerForRemoteNotificationTypes:(UIRemoteNotificationType)types NS_DEPRECATED_IOS(3_0, 8_0, "Please use registerForRemoteNotifications and registerUserNotificationSettings: instead") __TVOS_PROHIBITED;
^
/Users/ceeb/Desktop/ionic/fbob/platforms/ios/Book Football Field/Plugins/com.phonegap.plugins.PushPlugin/PushPlugin.m:221:23: error: no visible @interface for 'UIView' declares the selector 'stringByEvaluatingJavaScriptFromString:'
[self.webView stringByEvaluatingJavaScriptFromString:jsCallBack];
~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11 warnings and 1 error generated.

 What i did in terminal type "cordova plugin ls" you will see list of plugins then remove PushPlugin by typing "cordova plugin rm com.pluginname.version" i can't remember the full name. It is because ionic is using the old pushplugin which cause conflict with the new one. Hope it helps.

@uno2xx my issue is not to remove the plugin I want to use if for push notification but it always error like this so that's why on my IOS app no notification at all until now.

@aceeblaj actually Ionic have PushPlugin installed already if you are going to use the new which is the PushNotification it will cause an issue. try to run 'cordova plugin ls' and you will see.

@uno2xx I have completely removed the push plugin in order to build IOS version, here are plugin lists after run "cordova plugin ls" but no push plugin as you mentioned

How come you don't have a PushPlugin ? if that is the case you need to install it. check mine.

@uno2xx I think the one you're using is not the same as mine! because I used to try that one too. Here is the link for the one I'm facing problem https://github.com/phonegap-build/PushPlugin.git plugin
Is the one you're using work on both Android and IOS for notification?
Here is my code for the above plugin for Push Notification:
// Push notification

            var config;
            if (ionic.Platform.isAndroid()) {
                config = {
                "senderID": "xxxxxxxx" // project ID
                };
            }
            else if (ionic.Platform.isIOS()) {
                config = {
                    "badge": "true",
                    "sound": "true",
                    "alert": "true"
                };
            }

            $cordovaPush.register(config).then(function(result) {
              // Success -- send deviceToken to server, and store for future use
              console.log('result: ' + result)
              //$http.post('http://server.co/', {user: 'Bob', phoneID: result.deviceToken})
            }, function(err) {
              alert('Registration error: ' + err)
            });

            if (ionic.Platform.isAndroid()) {
              $rootScope.$on('$cordovaPush:notificationReceived', function(event, notification) {
                switch(notification.event) {
                  case 'registered':
                    if (notification.regid.length > 0 ) {
                      $rootScope.deviceToken = notification.regid;
                      store.set('deviceToken', notification.regid);
                      //alert('registration ID = ' + notification.regid);
                    }
                    break;

                  case 'message':
                    // this is the actual push notification. its format depends on the data model from the push server
                    alert(notification.message );
                    break;

                  case 'error':
                    alert('GCM error = ' + notification.msg);
                    break;

                  default:
                    alert('An unknown GCM event has occurred');
                    break;
                }
              });
            } else if (ionic.Platform.isIOS()) {
              $rootScope.$on('$cordovaPush:notificationReceived', function(event, notification) {
                if (notification.alert) {
                  navigator.notification.alert(notification.alert);
                }

                if (notification.sound) {
                  var snd = new Media(event.sound);
                  snd.play();
                }

                if (notification.badge) {
                  $cordovaPush.setBadgeNumber(notification.badge).then(function(result) {
                    // Success!
                  }, function(err) {
                    // An error occurred. Show a message to the user
                  });
                }
              });
            }

            // WARNING: dangerous to unregister (results in loss of phoneID)
            $cordovaPush.unregister(options).then(function(result) {
              // Success!
            }, function(err) {
              // Error
            });

For android it works very well, but on IOS can't build the project at all, if the one you're using work on both without any build error please help to provide a sample like the above for me.

You are using the old push notification and it is outdated. Install first PushNotification. Below is my code and I have the same code on iOS.
`var push = PushNotification.init({
android: {
senderID: GCM_SENDER_ID,
// iconColor: '#009ee0',
sound: true,
vibrate: true,
}
});
		push.on('registration', function(data) {
			window.localStorage.setItem('registration_id',data.registrationId);
			window.localStorage.setItem('device_type','android');

			$http({
			  method: 'POST',
			  url: 'http://<IP_ADDRESS>/api/update/registration-id',
			  dataType: 'json',
			  data: {token:data.registrationId,device:'android'}
			}).then(function successCallback(response) {
				console.log(response);
			}, function errorCallback(response) {
				console.log(response);
			});

			// console.log('Loading Data Above');
		});

		push.on('notification',function(data){
			// query notifications total;
			$http({
				method: 'GET',
				url: 'http://<IP_ADDRESS>/api/count-notification'
			}).then(function successCallback(response){
				console.log(response);
				$rootScope.notification = response.data.count;
			}, function errorCallback(response){
				reject(response);
			});

			BadgeCounter.counter();

			console.log('coldstart :'+data.additionalData.coldstart);
		});`

@uno2xx Thank you for your help, do I need to inject anything in controller or in .run() ?

@aceeblaj no need you can use directly the PushNotification

I don't understand, Ionic.Push is the one right in the documentation, is that already outdated? what is the exact plugin that should be used to build for iOS then?

@alexfradiani that's more of an Ionic question but I believe you are looking for $cordovaPushV5 in the code.


fix #1481, improve storm over gearpump perf

+1

Changes include

set TupleImpl.messageId to null to avoid map initialization
avoid converting java collections to scala
turn foldLeft into `tailrec

Now storm over gearpump reaches 5 million/s on 3-node(72 tasks) cluster


Python 3 Bindings

Any plans for Python 3 support? What would be necessary to generate the proper python bindings for this library?

I think this is a great idea, and I believe it should be a relatively straightforward improvement to make to MaterialX.
The core library on which the PyMaterialX module is based (PyBind11) already natively supports Python 3.x, so the main work would be resolving the two changes we've made to PyBind11 for MaterialX, which are listed below:

We've extended PyBind11 to support Python 2.6 (natively it only supports Python 2.7 and above).
We've added a compile-time flag (PYBIND11_PREFER_PYINT) which allows the developer to choose whether Python methods using integers should prefer objects of Python type 'int' or 'long'.

So far, these two extensions have only been built and unit tested with Python 2.x, so a developer would need to build PyMaterialX with Python 3.x and resolve any issues that come up.
Additionally, the handful of pure-Python wrappers in python/MaterialX would need to be updated for compatibility with Python 3 syntax.

I've tried building this for Python 3.5.2 using the provided "Quick Start Guide" for developers. However, running setup.py results in a "package not found" error. Is there more specific documentation for how to get this library setup and working properly?

Python 3 is now supported, but let us know if you encounter any issues with MaterialX in this environment, since the majority of our testing at Lucasfilm is with Python 2.x.


Possible improvements for Random

We could provide an asynchronous alternative to Random.Finite which automatically replenishes entropy by calling Random.blob(), since this would drastically reduce the complexity of random number generation for common use cases. That being said, it seems reasonable to also keep the current functionality due to the extra overhead from async calls.

I think @ggreif deliberately didn't do that so people don't re-use stale entropy in subsequent rounds, which can be unsafe for some applications that rely on unpredictable randomness. Not sure that applies here, but might.

Though it would be nice if Random.Finite took a byte iterator, not a finite, blob, so you could give it an infinite supply of bits generated on demand using a PRNG, say.

Though it would be nice if Random.Finite took a byte iterator, not a finite, blob, so you could give it an infinite supply of bits generated on demand using a PRNG, say.

The it should be named Random.Stream.


Bicep extension settings (settable through settings.json) are not documented

Describe the bug
Bicep VSCode extension contributes its own settings. We should follow the best practices and recommendations specified in https://code.visualstudio.com/api/references/contribution-points#contributes.configuration
Most Importantly, making sure that we add a description on each one of the fields that are configurable that is sufficiently informative so that people know and understand how to use the extension settings
Additional context
Related to the discussion in https://github.com/Azure/bicep/issues/9902

PR created - https://github.com/MicrosoftDocs/azure-docs-pr/pull/238025

PR merged.


stop using the browserproxy now that we have the window openers conne…

also fixes https://github.com/brave/browser-laptop/issues/143

@bbondy

sweet!


Fix: Background report changes to Tags page after clicking Custom tag name in RHP

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/49883
PROPOSAL: https://github.com/Expensify/App/issues/49883#issuecomment-2391275044
Tests

Precondition:

User is logged in to two devices
Workspace has tags

Open App
[Device A] Go to workspace chat
[Device A] Click + > Submit expense > Manual
[Device A] Proceed to confirmation page and click Tag
[Device B] Go to workspace settings > Tags
[Device B] Disable all tags
[Device A] Click Edit tags
[Device A] Click Settings > Custom tag name

Verify that The report in the background will remain after clicking Custom tag name

[x] Verify that no errors appear in the JS console

Offline tests

N/A can't test offline
QA Steps

Precondition:

User is logged in to two devices
Workspace has tags

Open App
[Device A] Go to workspace chat
[Device A] Click + > Submit expense > Manual
[Device A] Proceed to confirmation page and click Tag
[Device B] Go to workspace settings > Tags
[Device B] Disable all tags
[Device A] Click Edit tags
[Device A] Click Settings > Custom tag name

Verify that The report in the background will remain after clicking Custom tag name

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/dc61e1de-af39-4833-8ffe-e07f82afc22a

Android: mWeb Chrome
https://github.com/user-attachments/assets/ae40d71c-9936-4b08-aaa1-7a2d585eb688

iOS: Native
https://github.com/user-attachments/assets/deb57a5f-c7e8-4915-a691-2637e8b77e38

iOS: mWeb Safari
https://github.com/user-attachments/assets/8d9da5e2-8e12-4182-999e-a53d6da88c5a

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/7433e0b5-9687-49a2-9b3f-d757b3cd13d2

MacOS: Desktop
https://github.com/user-attachments/assets/51759477-b99b-414a-bd84-78750d8cdb15

@paultsimura yeah, I agree it's a bit bulky. But if it's already implemented this way for categories, I cannot argue with this approach. Same for Expensify Card - I wonder if we should also implement it this way.

Yep @paultsimura let's double it to $500 and get those fixed! CC @Christinadobrzyn

I have been OOO but am working my way through this. Lots of changes!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


PushNotificationIOS Podfile example is incorrect

At one time, the file showed the correct information. However, it was overwritten by PR #1214 and is now incorrect.
A PR is coming shortly that reverts the change and adds syntax highlighting to the example.

yes the example is wrong and confusing. thanks for pointing this out @blakek


Rename Transaction.{input, output} to plural?

Using singular sounds weird for naming repeated data. Plural is used in these situations pretty much everywhere I've seen, including this crate (e.g. in PSBT). This API-breaking that would affect multiple dependents but it's trivial to fix and I think it's worth it.

I prefer the current "input[i] refers to the 'i'th input" situation, but googling for this particular holy war shows I am in the minority, and I have no strong feelings about this.

Interesting view. I found things like tx.input.iter()... quite common which is not that appealing to me.

Yeah, that's fair. My view comes from C, and in Rust it's much more common to treat vectors as containers instead of constantly indexing into them.

If we are going to do this should we do it after we move Transaction to primitives?

I think it doesn't matter but I want it done before any primitives release.

I think we should leave the existing names alone. This is a case of #3166.
We could add accessors with plural names and try to encourage people to use those. (If primitives 2.0 gets rid of the public fields that might even make the transition easier.)

Oh, maybe we can do the same trick as cargo_toml did! Because of the Cargo.toml format change they had to change the type of a public field. So to make transition easier they added a method returning the real value in an older version and deprecated the field, then they broke it in the next version keeping the method. The result being one can use ranged version specification. However using it from libraries may be brittle if they expose the type in the API too. But in that case we should be able to trivially semver-trick the leaf types and implement a likely-zero-cost conversions by just moving fields around (if the layouts end up being the same the conversion is zero cost and this is likely to happen).

I think we should leave the existing names alone. This is a case of #3166.

I really, really, really don't like this. for input in self.input looks totally like a bug or bad variable naming unless you are familiar with rust-bitcoin.

We should add self.inputs() then. We could even deprecate the field if you want to discourage direct accesses. But I think we should keep the field (deprecation and all) around even for primitives 1.0 to minimize gratuitous code breaking.

One reason to rename the field is to avoid annoying difference between inputs() and inputs_mut().
So here's the suggestion: add the accessors and deprecate the field ASAP with a message, in addition to suggestion, asking for feedback in a specially prepared GH issue. Then we can decide if we should rename them or not based on the feedback. We will need to give it enough time though. We could also have primitives 2.0 one day but I hope we will not.

Sounds good.

I just had the second attempt at this I've made, it opens such a can of worms. No clue what to do about this.

I think we should add inputs() and inputs_mut() accessors and call it a day.
If you are feeling really ambitious you can try deprecating the fields, but I think that just won't work for people (due to borrowck limitations discussed above) and as a result we'll have to un-deprecate them.


Add CircleCI config

This CircleCI config is copied from eth-json-rpc-filters, which was recently updated to test on all Node.js LTS versions. Aside from the test matrix, it follows the typical conventions present in all of our library CircleCI configs (deps-install.sh script and HAR logs, separate test and lint jobs, a final all-tests-pass job to use as the required status check, etc.).

This depends upon #36

we likely don't need the har records, I just wanted them for the extension, in case we needed them as part of a post mortem for a ci build. Fine to have them tho


Improved Oracle System

Get price data from the following sources with a x% deviation tolerance. If any of the below deviate their reporting by x%, transaction reverts

BAND
pull oracle data from other chains using xCall (e.g. chainlink on avalanche)
Whitelisted oracle data providers approved by Balanced governance (e.g. icon runs oracle, LL runs oracle, etc.)


Add SetValue method in context to set context.values outside contex…

In my project, I want to pass data from middleware to a handle function.  I read the context.go.  In context struct, there is a attribute named values can implement it. But in Content interface(content
struct have implemented Content interface), There is no way to set values or modify values outside
context package. So, I want to add a method to do it.
And In "func (ctx *context) Value(key interface{}) interface{}", "ctx.values.GetString(k)" can only get
value of string type and in fact it may be other type.

@fpagyu Thanks for your interest but you're wrong here, you can set values outside of the context package. You have to call ctx.Values().Set... . values is not exported but Context has the Values() function which is exported.

@hiveminded You are right. Thank you.


Flannel to Calico migration not working

Expected Behavior

Flannel to Calico migration should succeed.
Current Behavior

The migration controller stopped with the following error:
[ERROR][1] ipam_migrator.go 348: Failed to validate existing default IPv4 IP pool (cidr/blocksize/nat/vxlanMode) {CIDR:<IP_ADDRESS>/16 VXLANMode:Always IPIPMode:Never NATOutgoing:true Disabled:false BlockSize:26 NodeSelector:all() IPIP: NATOutgoingV1:false}
[ERROR][1] migration_controller.go 171: Error initialising default ipool and Felix configuration. error=Failed to create default ippool
[FATAL][1] migration_controller.go 138: Migration controller stopped
Possible Solution

Steps to Reproduce (for bugs)

Install calico controller yaml
Install the calico migration job

Context

Your Environment

Calico version : v3.15.0
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes v1.18.1
Operating System and version: Centos 7
Link to your project (optional):

Have you tried installing canal first then running migration code?
I have not use it with your setup. however, I remember a similar error when I was working with the script.
Since this is experimental please try this in a lab environment first.
`

Install Canal from https://docs.projectcalico.org/getting-started/kubernetes/flannel/flannel
Install calico controller yaml
Install the calico migration job
`

remember to change CIDR in https://docs.projectcalico.org/manifests/canal.yaml @ net-conf.json section

@ragunathan23 Can you paste logs before [ERROR] ipam_migrator.go 348: Failed to validate existing default IPv4 IP pool ? Especially I am looking for this line  https://github.com/projectcalico/kube-controllers/blob/master/pkg/controllers/flannelmigration/ipam_migrator.go#L289


make instantiated models picklable

Especially, make the result of the following methods picklable:

[x] LabeledSpanExtractionByTokenClassificationTaskModule.configure_model_metric()
[x] TextToTextTaskModule.configure_model_metric()
[x] RETextClassificationWithIndicesTaskModule.configure_model_metric()
[ ] PointerNetworkTaskModuleForEnd2EndRE.configure_model_metric()

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (e44eb44) 95.80% compared to head (908d347) 95.78%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #46      +/-   ##
==========================================
- Coverage   95.80%   95.78%   -0.02%
==========================================
  Files          47       47
  Lines        3508     3539      +31
==========================================
+ Hits         3361     3390      +29
- Misses        147      149       +2

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


Merge updates for Weather Anti-UAV dataset into main

Change dependency source from conda to pypi
Add a download script for checkpoint
Ignore results folder
Refactor inference script
Add missing pip dependency to environment.yml
Change loading style to avoid OOM while loading backgrounds
Fix printing bug in demo.py
Improve image loading and pre-processing step with a general way
Add a option for visualizing details
Add an inference script for Weather Anti-UAV dataset
Change to use torch.inference_mode() instead of torch.no_grad()
Add an inference shell script for Weather Anti-UAV dataset
Update the source of pretrained weight

Sorry, my bad.
This PR is not for the upstream repo.


getMaximum2DCurvature wrong curvature calculation

Describe the bug
CatmullRomSpline member function getMaximum2DCurvature calculates the wrong value.
The member function finds the greatest max 2D curvature value from all curves that are included in the spline. This is done in the line below.
https://github.com/tier4/scenario_simulator_v2/blob/173a8c1d5e16b6e594de58d78cdb81a1d518ad82/common/math/geometry/src/spline/catmull_rom_spline.cpp#L570
However the max 2D curvature can be a positive as well as a negative value. The curvature magnitude is determined by the absolute value of the curvature value, which is considered in the function below.
https://github.com/tier4/scenario_simulator_v2/blob/173a8c1d5e16b6e594de58d78cdb81a1d518ad82/common/math/geometry/src/spline/hermite_curve.cpp#L303-L310
This means that the CatmullRomSpline member function getMaximum2DCurvature having two values: -10 and 2 will choose 2, however the value -10 corresponds to a much greater curvature, just in the other direction. For a spline having all component curves bending in one way (when all component max 2D curvatures are negative) this member function actually does the opposite of what is should - it selects the smallest curvature.
The logic present in HermiteCurve member function should be applied to a CatmullRomSpline member function as well.
Context:
I am adding unit tests for the geometry package and wanted to add tests for the getMaximum2DCurvature function, but it generates the wrong result in a case similar to the example above.
To Reproduce
Steps to reproduce the behavior:

Edit any existing source code file or create a new one
Create a CatmullRomSpline passing through points (0, 0), (0.5, 0.5), (1, 0), (2, -1) and (3, 0)
Call the getMaximum2DCurvature member function
Print and see the incorrect result

Expected behavior
Greatest absolute value should be selected instead of the greatest one.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]: Ubuntu
Browser [e.g. chrome, safari]: Firefox
Version [e.g. 22]: 22
ROS 2 version: Humble
DDS: CycloneDDS

Thanks, it is a bug.

#1139 was merged


v1.7: Provide option to avoid DROP_INVALID_IDENTITY during upgrade from v1.6 to later Cilium versions

Allow tunnel traffic "from host" with remote-node-identity=false
According to the documentation:
 One can set enable-remote-node-identity=false in the ConfigMap to
 retain the Cilium 1.6.x behavior.

The above is true when evaluating policy, but not true from the
DROP_INVALID_IDENTITY perspective as during an upgrade from v1.6 to
v1.7, v1.6 nodes may send traffic to v1.7 nodes with the "host" identity
and the v1.7 nodes will drop such traffic with this error code. Mitigate
this by also covering this datapath case with the
EnableRemoteNodeIdentity flag check.

Add hidden allow-remote-src flag
This flag allows to override the default setting for whether to accept
traffic into a node if the source node reports the source identity as
"host". Default is "auto" - to allow if enableRemoteNodeIdentity is
disabled; deny if enableRemoteNodeIdentity is enabled. If specified
directly, it will take on the configured behaviour (allow such traffic
if true, otherwise drop it).

Backported for bpf.sha rebase, daemon arg changes.
~Related: #12998~
Fix packet loss issues when running Cilium v1.6 and v1.7 in the same cluster concurrently with --enable-remote-node-identity=false

test-backport-1.7

test-backport-1.7

test-backport-1.7

Shouldn't we document this flag in the upgrade guide though (and/or set it via the Helm chart for upgrade path)?

Shouldn't we document this flag in the upgrade guide though (and/or set it via the Helm chart for upgrade path)?

The primary goal here is to make the code conform with the documentation: That is, with --enable-remote-node-identity=false, there is no behavioural difference from v1.6.
The hidden flag is provided as an override in case we really need a knob. Users should not need to know about this unless there is some special condition in which we can let them know to configure in a configmap.

Regular ginkgo tests hit known flakes #12777 , #12994

Only Istio 1.5.9 failure in k8s tests, github infrastructure issue. Given the changes are unrelated and the only failures are known flakes, this is good to merge.
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/3461/testReport/junit/Suite-k8s-1/16/K8sIstioTest_Istio_Bookinfo_Demo_Tests_bookinfo_inter_service_connectivity/


simplify overview & push rest of content into sections

simplify overview & push rest of content into sections

Closing this out in favor of working in the docusaurus structure


Old School Essentials - adding missing translation items

adding missing translation items

Character Sheet Info Roll20 Internal Use only.


[ANNOUNCEMENT] - RevoGain - an alternative that actually works!

Revolut statements are very hard to parse, and that's not all. There are actually many more issues, like:

stocks undergo splits and reverse splits so you need to take that into consideration when calculating the base cost
you can buy crypto with USD, GBP, and EUR, but gains have to be converted to a base currency when doing the report
the crypto Excel/CSV statement does not even contain the buying/selling price so you need the historical price for that
you need the historical price for Gold and Silver if you trade those as well
you can buy BTC with EUR, then sell it to ETH, and then buy USD. All those operations are taxable.
you need to calculate the dividend cost
as a Revolut customer, you might want to generate your report in your local currency (e.g., 'EUR', 'GBP', 'CHF', 'USD', 'DKK', 'SEK', 'NOK', 'PLN', 'CZK', 'HRK', 'HUF', 'BGN', 'RON)

Trying to make a sense out of all that could take you days or just a minute if you use RevoGain.

All types of splits are supported.

Crypto calculations are not supported.

The new Revolut CSV statements will be supported before the next tax season.

Commodities are not supported.

Dividend costs are fully supported.

Currently the calculator works with BGN, according to Bulgarian tax lows.

RevoGain doesn't seem to work with any EU tax jurisdiction.

My calculator is free and always remains free.


Update fbjs from v6.x to v7.x

npm v3 tries to dedupe the dependencies by default, and keeping dependencies up-to-date helps better deduplication.
Though it seems that this repository is not tested on any CIs, I ran npm test on my PC and it passed all the tests.
$ node --version
v5.5.0

$ npm t

><EMAIL_ADDRESS>test /Users/shinnn/github/emitter
> NODE_ENV=test jest

Using Jest CLI v0.8.2, jasmine1
 PASS  src/__tests__/EventSubscriptionVendor-test.js (0.572s)
 PASS  src/__tests__/BaseEventEmitter-test.js (0.686s)
20 tests passed (20 total in 2 test suites, run time 1.457s)

Seems fine to me, @ide and @zpao were playing around with dependencies in here related to react native, if this seems okay with them I'm happy to merge this.

LGTM

I have no skin in this game so feel free to ignore me, but could it be a range instead? ^0.6.0 || ^0.7.1 perhaps (assuming it's intentional to exclude 0.7.0)

The range would work too.

I'll make it a range and publish 2.0.2.


merge from template-arlac77-github

package.json

chore(deps): add ^6.0.1 remove ^6.0.0 (devDependencies.ava)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
167

Relevant Lines:
174

💛  - Coveralls


User Page Templating

Administrative Info
#4
Changes
What changes did you make?

Implemented user page for desktop and mobile views
Created modals (visually) for change password and delete account

Testing
How did you confirm your changes worked?

Viewed website at different page sizes and at mobile

Confirmation of Change
https://user-images.githubusercontent.com/29768212/148857330-aa303fba-7056-4151-9bd3-343f6b57dfb6.mov

I only noticed that the modals look a bit cramped with the Galaxy Fold dimensions.

Other than that, lgtm.


[data-poll-sender] always honor the default child timeout based poll interval

This PR contains three related changes/commits.
It addresses an issue with child timing out on parent (kicked out of child table) if the data poll period is set (by user) to a value larger than the child's timeout.
[network-diagnostics] use the child timeout directly

This commit changes the `NetworkDiagnostic::FillRequestedTlvs()` to
directly use the child timeout value in appended `TimeoutTlv`. This
addresses an issue where a user-specified long data poll interval
could cause the timeout TLV in diags response to be set higher than
actual child's timeout value.

[data-poll-sender] always honor the default child timeout based poll interval

This commit changes the `DataPollSender` to ensure that a child device
will always send a data poll within its timeout interval. This
addresses an issue where a large user-specified poll period could
cause the device to adopt a poll period longer than the default child
timeout (causing parent to kick the child out of its child table).

This commit also simplifies the selection code for a new poll period
by adding a helper `UpdateIfLarger()` method to update the period only
if it's larger than a given new value.

[toranj] add test to verify child sending data poll within its timeout

This commit adds a `toranj` test-case. This test covers the situation
where the data poll interval is set to a value larger than child's
timeout interval. The test verifies that the sleepy child would send a
data poll within its timeout interval (ensuring that child stays in
parent's child table).

The new test does indeed fail without the change/fix from the second commit.

In  the new pushed commits, added PR number (#4136) to commit message title.

@abtink , sorry for late response.
For the first commit, I am afraid it might be conflict with the Specification.

1.1 Spec 10.11.3
Timeout For SEDs, indicates the maximum polling time period.

For the issue the first commit to resolve, I don't think it is valid to allow user to set a poll period larger than child's timeout.

Spec 1.1 Section 4.7.5
If a Child does not receive a response to a keep-alive message from their Parent, the Child
should retry three times before attempting to reattach to a new Parent. All four attempts
MUST be completed within the child's timeout period.

How about adding the check when setting the poll period?

Thanks @librasungirl for helping review the PR. Addressed the typos from your comment in new pushed commit.
On first point, @jwhui  and I both read the spec before the change. The interpretation is that the value in this TLV should be the maximum polling interval device will always honor (i.e. we always have at least one poll within this interval). The child timeout is indeed the maximum poll interval that we always guarantee (independent of user's specified poll interval). The user may request different poll intervals and may change the value often, so it's not always ensured to remain the same.
On second point, I think we should allow user to set the external poll interval to any value (even larger than child timeout):

Changing the API to return an error on value larger than timeout would directly impact how we use it in some of our internal projects:

The next layers (on some internal projects) do set the poll interval (user-specified poll interval) to some large value and instead the next layer directly controls when/how to send polls using otLinkSendDataRequest() API.
This is what exposed this issue being addressed here, i.e., if the next layer does not send polls frequently enough, OT core should still ensure that it honors the child timeout interval (send at least one poll within the child timeout).

The fact that we need to poll at minimum within a child timeout's intevral, is a Thread requirement (which we ensure in core code implementation). The goal is for user to determine its poll interval from app layer requirements and would be easier to not have user be aware of child timeout.

Thoughts?

@abtink Thanks for the explanation. Agree that it would not be a good idea to reject the larger value in the context. I vote for 'honor' solution here. Basically I am fine with this PR.  Here are some thoughts just for discussion:
Section 4.7.5 should indicate that in worst case four keep-alive messages(i.e. data poll for SED) should happen before ChildTimeout - that is, maximum poll interval should be the value of existing DataPollSender::GetDefaultPollPeriod, not ChildTimeout.
And Network Diagnostics should be designed to retrieve the state of the device or the network. The Timeout TLV in Network Diagnostic (maximum of poll interval, for SED) should be used to check the possible waiting time to deliver a message to a SED. I think it may make better sense to still fill TimeoutTLV with the real maximum poll period?
Thoughts?

Section 10.11.3 also states:
Same format and semantics as Timeout TLV (MLE TLV Type 2, Section 4.5.3).

Section 4.5.3 states:
The Timeout TLV (TLV Type 2) has a Value containing a 32-bit unsigned integer. The value
is the expected maximum interval between transmissions by the sender, in seconds. This
allows the receiver to more accurately time out a link to a neighbor that polls for its
incoming messages.

What is communicated in the MLE Timeout TLV is the child timeout value. So I think it makes sense that we use the child timeout value for the Network Diagnostics TLV as well.
Thoughts?


Changed GovernmentConstants.ToChannelFromBotLoginUrl

Fixes #2133
Description
Per @willportnoy, this is the only changed needed for now since, unlike the Dotnet repo, JS doesn't:

use GovernmentAppCredentials
write its own AdalAuthenticator

Changes
Changes GovernmentConstants.ToChannelFromBotLoginUrl to https://login.microsoftonline.us/MicrosoftServices.onmicrosoft.us

Pull Request Test Coverage Report for Build 126426

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.87%

Totals

Change from base Build 126375:
0.0%

Covered Lines:
12357

Relevant Lines:
14762

💛  - Coveralls


Add logical string type

addresses #85
This PR implements a logical String type that just pipes through every string to the physical layer without doing any sophisticated parsing. In contrast, the Any type now does exactly that, i.e. parses its input string as RDF term, which is in turn mapped appropriately to the physical layer.
If no type declarations are specified, all columns from CSV inputs are treated as String. (Every Datasource variant has its own default type; for RDF files this would be Any.)
Note that the String "A" and Constants the constant A look the same in CSV: A
Further note that the physical representation of the logical String "A" (or "A"^^<http://www.w3.org/2001/XMLSchema#string> or "A"@cz) and the logical Any constant A are also the same: A.
String literals "A" or ("A"^^<http://www.w3.org/2001/XMLSchema#string> or "A"@cz) in columns with a logical type of Any are represented as "A", both in the physical layer and when written to CSV.
The normalization of rdf terms like "A"^^<http://www.w3.org/2001/XMLSchema#string> for the String type only applies to terms from the rule file. "A"^^<http://www.w3.org/2001/XMLSchema#string> in a String column of a CSV is treated as the String "\"A\"^^<http://www.w3.org/2001/XMLSchema#string>".
I think the confusion has now been completed :rocket:

!!! NOTE: I did not check if any of our usual benchmarks break here !!!

Alright, I think all comments should be addressed now :)
(Hope I did not overlook something.)
Some things like output handling need more love but I think we can leave this for later. (Possibly in the scope of #245)