catkin_make error

CMake Error at /opt/ros/indigo/share/soem/SoemTargets.cmake:34 (message):
  Some (but not all) targets in this export set were already defined.

  Targets Defined: simple_test;red_test;slaveinfo;eepromtool;ebox;firm_update

  Targets not yet defined: osal;oshw;soem

Call Stack (most recent call first):
  /opt/ros/indigo/share/soem/soem-config.cmake:12 (include)
  /opt/ros/indigo/share/catkin/cmake/catkinConfig.cmake:75 (find_package)
  robotiq/robotiq_ethercat/CMakeLists.txt:4 (find_package)

-- Configuring incomplete, errors occurred!
See also "/home/xsm/catkin_ws1/build/CMakeFiles/CMakeOutput.log".
See also "/home/xsm/catkin_ws1/build/CMakeFiles/CMakeError.log".
Invoking "cmake" failed

CMake Error at /opt/ros/indigo/share/soem/SoemTargets.cmake:

It would seem this is an error in soem, and not in this (robotiq) package.
Also: when reporting problems with build infrastructure, it's a good idea to include information on your OS, its version, how you installed it, version of ROS, how you installed that, etc, etc.

but before I put the robotiq package into workspace , catkin_make successed , when I put the robotiq package into workspace , it show error.Why?

Because nothing in your workspace was using the soem package?

nothing

No I meant: you did not get an error before, because no other package uses the soem package (which is the one with the error).

Which OS are you trying to build this on? Does it have CMake version > 3?

ubuntu14.10  cmake version <IP_ADDRESS>

Is this still an issue?  Can this be closed?

I'm not sure if this is the same error but it does involve soem
CMake Warning at /opt/ros/indigo/share/catkin/cmake/catkinConfig.cmake:76 (find_package):
  Could not find a package configuration file provided by "soem" with any of
  the following names:

    soemConfig.cmake
    soem-config.cmake

  Add the installation prefix of "soem" to CMAKE_PREFIX_PATH or set
  "soem_DIR" to a directory containing one of the above files.  If "soem"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  robotiq/robotiq_ethercat/CMakeLists.txt:4 (find_package)

-- Could not find the required component 'soem'. The following CMake error indicates that you either need to install the package with the same name or change your environment so that it can be found.
CMake Error at /opt/ros/indigo/share/catkin/cmake/catkinConfig.cmake:83 (find_package):
  Could not find a package configuration file provided by "soem" with any of
  the following names:

    soemConfig.cmake
    soem-config.cmake

  Add the installation prefix of "soem" to CMAKE_PREFIX_PATH or set
  "soem_DIR" to a directory containing one of the above files.  If "soem"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  robotiq/robotiq_ethercat/CMakeLists.txt:4 (find_package)

Closing this issue...if this is still an issue, please feel free to comment with more information and we will reopen it.


Faster env vars

Currently they're pulled in at runtime, but I'd like to consider utilizing the "native" encrypted Lambda env var support, baking them in at deploy time. The main wins are improved cold start time and fewer KMS requests, with the one caveat that rollbacks would now revert environment variables as well.
The downside is that since these variables display in the console as plain text since it decrypts them—they're encrypted at rest though.

[x] pull and bake into func
[ ] refactor to remove List() / Load(), somewhat redundant
[x] remove runtime loading
[ ] make current runtime implementation an option?
[ ] QA

[x] env listing
[x] NODE_ENV local and remote
[x] NODE_ENV overrides
[x] up start
[x] up start overrides
[x] build hooks
[x] stage fallbacks

[x] update docs

[x] rollback env vars not affected
[x] document remote precedence over up.json

Next release tonight or tomorrow will have this change, and everyone should see ~700ms shaved off cold starts.


TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined

Hi,
i have followed the usage section in the readme and receive the following issue.
gulp scaffold --project-dir="projects/example"

[21:03:51] Using gulpfile ~/Projects/PixelCombo/google-apps-scripts/gulpfile.js
[21:03:51] Starting 'scaffold'...
[21:03:51] 'scaffold' errored after 3.23 ms
[21:03:51] TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined
    at assertPath (path.js:39:11)
    at Object.relative (path.js:1167:5)
    at createNestedDir (/Users/steinbrueckri/Projects/PixelCombo/google-apps-scripts/gulp/tasks/scaffold/helpers.js:18:26)
    at resolve (/Users/steinbrueckri/Projects/PixelCombo/google-apps-scripts/gulp/tasks/scaffold/helpers.js:90:9)
    at new Promise (<anonymous>)
    at exports.makeProjectFolder (/Users/steinbrueckri/Projects/PixelCombo/google-apps-scripts/gulp/tasks/scaffold/helpers.js:88:12)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)

I have try to debug the issue and i think the problem is, createNestedDir() is called from makeProjectFolder with one argument insted of two.
It looks like it is working but now i struggling with
Error retrieving access token: TypeError: Cannot read property 'expiry_date' of undefined but this is a claps problem, i thing. ;)
regards Richard

@steinbrueckri
Thanks for pointing this out. I could reproduce and fix the error.


Hotfixes needed for 2.9.1

[x] Memory leaks on MainActivity #1996
[x] Crash on bookmarking an item from Explore #2041
[ ] After re-logging, notifications bell icon is empty #2014 @neslihanturan
[ ] App stuck at "receiving shared content" #2033 @ashishkumar468 / @maskaravivek
[x] 2.9.0: Unable to exit app after going to notifications activity #2044 @misaochan
[x] Blank Achievements activity for some users #2042
[x] Multiple uploads: If one description is empty, all pictures in batch will have no desc #2032 @misaochan / @maskaravivek
[x] When logging in after Skip Login, the usual main activity does not load #2030
[x] Attempt to invoke virtual method 'an droid.content.res.Resources android.view.View.getResources()' on a null object reference #2045
[ ] Nearby: My position does not move #2062 @neslihanturan
[ ] Upload failures after v2.8 #2013 @ashishkumar468

Thank you to our wonderful volunteers who have helped us with some of these issues while we were rushing for the 2.10 feature deadline!  :) Now that 2.10 is almost ready, we have decided that we will most likely skip 2.9.1 entirely and roll all of these fixes into 2.10. There are many bugfixes in master that we want to take advantage of, plus the automated releases via master will be very useful.
This does mean that Play Store production users will skip 2.9 entirely (as 2.9.0 has a few bugs that would not pass muster in production). However, given that we can output 2.10 in almost the same timeframe as 2.9.1, there would be minimal downside to this for them.

I have copied the remaining bugfixes needed over to #2171


How to add or remove password to NTAG213 and NTAG216

How to add or remove password to NTAG213 and NTAG216 by react-native-nfc-manager

It can be implemented by a sequence of nfcAHandler.transceive() commands.
You will need to read the datasheet from NXP first, but the whole idea looks like this:

[setup] use standard T2T write (0xa2) command to configure the tag, including

set password, and password-ack
set read or write protection
set the starting block index to protect

[access protected blocks] when you'd like to access the protected blocks, you will send an NXP proprietary command with your password. If correct, the tag will respond you with the password-ack. After this step, you will be able to access your tag's memory normally.

I have done this before, but I don't remember the detailed command and configuration block index, so you will need to consult the official datasheet from NXP.
Hope that helps.


Webview repeats some keyboard shortcut execution

Issue Type: Bug

Open a markdown preview editor
"ctrl+`" to toggle the terminal
The terminal will be opened and then dismissed immediately. Sometimes it's too fast then you can't see the terminal being opened

I'm not seeing this issue in Stable so it's a regression.
VS Code version: Code - Insiders 1.51.0-insider (2ee8b8c645ec8ab54304bacae7aa979c1d9c647a, 2020-10-29T06:00:13.428Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
32.00GB (1.08GB free)

Process Argv
--enable-proposed-api ms-vscode.vscode-notebook-history --enable-proposed-api vscode.notebook-editing --crash-reporter-id 1a907bbd-fa02-4595-81e0-63e1648afb31

Screen Reader
no

VM
0%

Extensions (41)

Extension
Author (truncated)
Version

comment-tagged-templates
bie
0.3.0

github-markdown-preview
bie
0.0.2

markdown-emoji
bie
0.0.9

markdown-preview-github-styles
bie
0.1.6

gitlens
eam
10.2.2

tsl-problem-matcher
eam
0.3.1

vscode-pull-request-github-insiders
Git
2020.10.41223

vscode-fluent-icons
mig
0.0.1

theme-monokai-pro-vscode
mon
1.1.17

vscode-docker
ms-
1.7.0

vscode-language-pack-zh-hans
MS-
1.51.1

dotnet-interactive-vscode
ms-
1.0.152203

vscode-dotnet-runtime
ms-
0.1.2

python
ms-
2020.10.332292344

remote-containers
ms-
0.147.0

remote-ssh-edit-nightly
ms-
2020.10.29700

remote-ssh-nightly
ms-
2020.10.29700

hexeditor
ms-
1.3.0

js-debug-nightly
ms-
2020.10.2817

powershell-preview
ms-
2020.9.0

vscode-github-issue-notebooks
ms-
0.0.57

vscode-markdown-notebook
ms-
0.0.13

vscode-notebook-history
ms-
0.0.1

vsliveshare
ms-
1.1.0-dev

vsonline
ms-
1.0.3073

debugger-for-chrome
msj
4.12.11

toggle
reb
0.0.1

java
red
0.69.0

kuskus-extensions-pack
ros
1.0.1

kuskus-kusto-language-server
ros
1.0.1

kuskus-kusto-syntax-highlighting
ros
1.1.8

rust
rus
0.7.8

sourcekit-lsp
unp
0.0.1

vscode-lldb
vad
1.6.0

vscodeintellicode
Vis
1.2.10

vscode-java-debug
vsc
0.29.0

vscode-java-dependency
vsc
0.14.0

vscode-java-pack
vsc
0.10.0

vscode-java-test
vsc
0.25.0

vscode-maven
vsc
0.25.0

notebook-editing
vsc
1.0.0

(5 theme extensions excluded)

Assign it to October milestone as it's a regression.

Doesn't happen for me on MacOS. Do you have any settings related to webviews, such as using iframe based webviews?

@mjbvz right I do have a legacy useIframe setting for webview. After removing that the issue is gone.

Thanks. I will take a look but am unassigning this for October then since that setting is still experimental

I found something more interesting:

Open a text editor, keep pressing ctrl+`, the terminal keeps toggling
Open markdown preview, keep pressing ctrl+`, the terminal toggles for a few times and then nothing happens anymore

This happens even without the experiment settings. I also toggled the keyboard shortcut troubleshooting and when ctrl+` went dead, the keybinding service doesn't get any keyboard events as well.

@mjbvz can you try if you can reproduce with steps listed in https://github.com/microsoft/vscode/issues/109702#issuecomment-719062237 ?

Fixed by ffb8c08
@rebornix I can reproduce the second issue too and have extracted it to #110276

To verify:

On MacOS
Set "webview.experimental.useIframes": true
Restart VS code
Open a markdown preview
Now try running some toggle commands such as ctrl + backtick while focused on the webview


Repository cache for GHES (beta)

Summary
Many GitHub Enterprise Server customers have teams and CI farms located all around the world. The GitHub repository cache will mirror repositories near these clients, reducing latency and bandwidth required to support geographically-distributed teams while also reducing load on the primary instance.
Intended Outcome
Massive read load from very large CI farms can affect performance on the customer's GitHub Enterprise Server. This degrades the developer experience - fetches, pushes, merges, and even non-Git features can be slowed down when load is high. Also, there's no reason to transmit the same Git data over and over again via a long-haul network link. The repository cache helps customers reduce bandwidth consumed on long, possibly intercontinental networks. It also helps customers serve their CI and automation needs from a dedicated host, reducing the load on the primary GHES and improving the experience for users of the primary.
How will it work?
The repository cache listens to the primary instance (whether that's a single GHES server, a geo-replicated set of instances, or a cluster configuration) for changes to Git data. CI farms and other read-heavy consumers clone and fetch from the cache server instead of the primary instance. Changes are propagated across the network once per cache instance rather than once per client.

https://github.blog/2021-12-07-github-enterprise-server-3-3-is-generally-available/


[#95] Update memo of SampleDataUtil.java

Fixes #95
Previous SampleDataUtil.java memos were empty.
Update the memos to contain miscellaneous data about the contact.

Codecov Report

Merging #96 (c702adc) into master (09e376b) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #96      +/-   ##
============================================
- Coverage     72.61%   72.59%   -0.02%
+ Complexity      459      458       -1
============================================
  Files            76       76
  Lines          1406     1405       -1
  Branches        148      148
============================================
- Hits           1021     1020       -1
  Misses          343      343
  Partials         42       42

Impacted Files
Coverage Δ

.../java/seedu/address/model/util/SampleDataUtil.java
20.00% <ø> (-5.00%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 09e376b...c702adc. Read the comment docs.


fix(deps): update gomod

This PR contains the following updates:

Package
Type
Update
Change

github.com/IBM/go-sdk-core/v5
require
patch
v5.16.3 -> v5.16.5

github.com/IBM/platform-services-go-sdk
require
patch
v0.62.2 -> v0.62.5

Release Notes

IBM/go-sdk-core (github.com/IBM/go-sdk-core/v5)
v5.16.5
Compare Source
Bug Fixes

bump golang.org/x/net to avoid  CVE-2023-45288 (#215) (b9287d2)

v5.16.4
Compare Source
Bug Fixes

errors: wrap errors from external authenticators to use new system (#214) (c74778e)

IBM/platform-services-go-sdk (github.com/IBM/platform-services-go-sdk)
v0.62.5
Compare Source
Bug Fixes

bump golang.org/x/net to avoid CVE-2023-45288 (#319) (17ac6ee)

v0.62.4
Compare Source
Bug Fixes

IAM Policy Management: S2S support for enterprise accounts (#317) (4d65f3d)

v0.62.3
Compare Source
Bug Fixes

ATracker: remove endpoint field from CloudlogsEndpoint (#318) (51b4afc)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.30.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[CP] Constrain _RenderScaledInlineWidget child size in computeDryLayout #131765

CP request: https://github.com/flutter/flutter/issues/132095
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@chtai can you review this CP request? If it looks good to you, add the "cp: approved" label.


Zuul Routing to Microservice in Liberty Container - SSL Issue

Hello,
We have a setup where Zuul is running on an JVM and Eureka is running on an JVM and a Simple Microservice is running on an JVM. All the 3 JVM are in Liberty Container. The service is able to register and can see it in Eureka. All these 3 are setup to run using https/ssl - tls v2.0 protocol.
The issue that we have is when a request is sent from browser to Zuul URL, which in turn supposed to forward to Microservice, it gives the SSL Handshake exception. On the other hand if you access the Microservice directly no issues and able to access it and get the response.
Any thoughts on what might be causing the SSL issue?

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


"wrap_attributes":"force" not working on Handlebars

Please provide repro steps and details.

Seeing this as well... using this in the Atom editor where html works a charm, but handlebars fails.

What details are needed? aside from creating a document and running the script?

  "atom-beautify":
    general:
      _analyticsUserId: "ccddff64-18a8-41db-a3b3-7d5ca10d9281"
    handlebars:
      indent_inner_html: true
      wrap_attributes: "force-aligned"
    html:
      indent_inner_html: true
      wrap_attributes: "force-aligned"

Pretty straight forward here,  no major tweaks. Comparing html and handlebars, handlebars pulls all attributes onto the same line.


[Nitpick] "popular" type names in "top-level" namespace

This is VERY nitpicky and the fix is easy, but I see this getting annoying quite fast:

I see there is an "Enums" namspace already, so maybe it belongs there, or a less "every project on earth will have the same type-name"-name:

Fixed in the latest version


Formatter

On top of that, would just using &format be nice? I get that it takes away from our branding - but it's much easier to type out.


Cannot create custom template from uploaded compose file

Bug description
When creating a custom template and choosing to upload a compose file, creation fails.
Expected behavior
Creation of the template should succeed.
Portainer Logs
2020/10/12 22:06:08 http error: Unable to create custom template (err=Invalid Compose file. Ensure that the Compose file is uploaded correctly) (code=500)
Steps to reproduce the issue:

Go to create custom template view
Upload a compose file
Click create button
See error Failure Unable to create custom template

Technical details:

Portainer version: CE
Docker version (managed by Portainer): 19.03.13
Platform (windows/linux): Linux
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): Docker run
Browser: FireFox, Chrome

I'm trying out portainer and just got this error too:
2021/01/12 21:20:22 http error: Unable to create custom template (err=Invalid Compose file. Ensure that the Compose file is uploaded correctly) (code=500)

I'm trying out portainer and just got this error too:
2021/01/12 21:20:22 http error: Unable to create custom template (err=Invalid Compose file. Ensure that the Compose file is uploaded correctly) (code=500)


Docker Compose : Instructions for Raspberry Pi [Raspbian GNU/Linux 9.9 (stretch)] installation.

The instructions in the file: compose/install.md can not be applied to Raspbian GNU/Linux 9.9 (stretch), because mention to execute the following command (in order to download the docker compose) :
sudo curl -L "https://github.com/docker/compose/releases/download/1.24.0/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

Where this will mean in the Raspberry Pi :
github.com/docker/compose/releases/download/1.24.0/docker-compose-Linux-armv7l

But I don't see any package for the Raspberry microprocessor architecture.
Docker Compose doesn't support this architectures or there is an alternative with which we can approach the issue ?
Thank you.

Thanks for the feedback, however this is not an issue with Docs.
Do you mind moving your conversation to the compose repo https://github.com/docker/compose. Additionally you may find this useful https://github.com/docker/compose/issues/6188#issuecomment-421185249.


[AngleWin32PlatformGraphics] code will never run

https://github.com/AvaloniaUI/Avalonia/blob/cd0020eb755b5867e1bf6d39d3472c857ece1c68/src/Windows/Avalonia.Win32/OpenGl/Angle/AngleWin32PlatformGraphics.cs#L92-L132
@kekekeks Can it be removed?

Whoops, the line before was supposed to be used only for debugging.


Mac Build dependencies (electron:package is invalid)

Hi Chris/Matt,
May be some more dependencies to list build. I've run:
npm install -g ember-cli
npm install -g electron
npm install -g electron-packager

but get this
$ ./scripts/electron/mac/package-dev.sh
(Presumably environment is already configured for development)
The specified command electron:package is invalid. For available options, see `ember help`.

Best,
Zach

$ npm -v
3.3.9

$ ember -v
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
ember-cli: 2.8.0
node: 5.0.0
os: darwin x64

$ electron -v
v1.4.2

Have you tried running the make install-tools make target (https://github.com/dotbc/dotbc-bundler/blob/master/Makefile#L24) to ensure all your tooling dependencies are installed?

Thanks, that fixed the watchman warning but still getting the original error running the script.
I also tried:
npm install -g ember-electron
ember g ember-electron
but that the later command returns
Unknown blueprint: ember-electron
The other install method:
ember install ember-electron
seems to fail with a  ES6 blocked scope syntax error.

No need to run $ ./scripts/electron/mac/package-dev.sh if you're developing locally.
make install-tools
make install-plugins
npm run electron

should do it. https://github.com/dotbc/dotbc-bundler#running-and-developing-locally


Remove unnecessary ExistingContactEntity interface

Problem
The ExistingContactEntity interface is unnecessary because we are not providing any implementations that are not "existing".
Solution
Delete the ExistingContactEntity interface and move its contents to ContactEntity.
🚨Breaking change 🚨
Users of this library must delete references to ExistingContactEntity and replace it with ContactEntity.

Perhaps I should not do this because there might be a "new" or "test" contacts in the future that do not "exist"...

I thought about it and decided that it best to keep the two interfaces; ContactEntity and ExistingContactEntity.
Even though ContactEntity does not CURRENTLY have any other inheritors besides ExistingContactEntity, it provides a standard structure that matches RawContactEntity and ExistingRawContactEntity. Furthermore, it gives us flexibility to create other entities such as NewContactEntity and MockContactEntity in the future if we ever need it. This may be violating YAGNI but it also does not hurt at all to have things that we way they are currently. It just gives us options and protects consumers from big refactors.
To close this ticket, I'll just leave some comments in code about this!


The isURL validator does not correctly validate http://www.

If I enter "http://www.uk" the validator says that it's a valid URL, however we can clearly see that it's not. The problem is that the trailing www after the protocol is not recognized as 'www' and is treated like the beginning of the url which can be something like 'abc.uk' or similar.

That is a valid URL. Checking whether the TLD allows registration of that domain, or checking whether the page actually exists, is outside the scope of the library.

Ok I didn't know that. Anyway for real life usage it is an invalid URL...


"Nonconforming Funders" notification displayed too frequently

@martinseul suggested that we show the "Nonconforming Funders" notification too frequently.
We show it for a few seconds on every load of resource landing page.
HS v 2.13.3

Making a note here that I discussed with @martinseul and decided that of three options:

Show Alert Only Once Per Session
Show Alert Only Once Per Resource Edit
Only Show Alert When Editing

We think the best might be to only show the alert when the owner/editor initiates editing a resource


Enable real walking code, add Sabre (first of enemy type) and minor enemy codebase improvements

Closes https://github.com/bharathcs/quantum-defence/issues/2
The enemies will not queue up like a hashtable's primary probe nightmare, but will move eventually around obstacles after colliding with something (not very intelligently though, so use this sparingly, e.g. with enemy - enemy collisions).
Instead of using the TileMaps, now I use a NavPoly with NavPoly Instance directly to manage the existing path. This is not required, and can be changed back to the original situation if required. I was trying out how to stop enemies from sticking to the wall so fiercely (not solved by new enemy implementation, only solved by the specially drawn nav polygon)

First three commits can be ignored (bhcs/reorg-src stuff).


Unit testing - simulate errors

When unit testing using in memory db, how do you simulate that an error occurred when accessing the db?

@Robelind You could look in to creating your own derived version of the InMemoryStore class and then using ReplaceService in OnConfiguring to have EF use your version. This would be using internal code, so do this at your own risk and with the understanding that it could break any time a new version of EF is shipped.


Implement spark run-operations

I've implemented two run-operations which can optimize all delta tables, or compute the column statistics of all tables. Similar to the vacuum operations of redshift.

@jtcohen6, @NielsZeilemaker : Can this PR be merge? I would like to use this macro.

@jtcohen6  and @NielsZeilemaker : once more: can we merge this macro in?

Closing in favor of #18


java.lang.NullPointerException: Cannot invoke "org.hibernate.engine.spi.EntityEntry.getEntityKey()" because "ownerEntry" is nullHHH-15453

https://hibernate.atlassian.net/browse/HHH-15453
The hql query in translated into
select u1_0.USER_ID, u1_0.AGENCY_ID, u1_0.USER_NAME
from
USER_TABLE u1_0
where
u1_0.USER_ID=2
with the following Initialized
    - EntitySelectFetchInitializer [User.agency]
    - SelectEagerCollectionInitializer [User.roles] << has no owner
    - EntityResultInitializer [User]

EntitySelectFetchInitializer#initializeInstance() triggers: internalLoad of Agency before the User.roles collection owner has been set, the following query is executed:
select a1_0.AGENCY_ID,  a1_0.AGENCY_NAME
from
AGENCY_TABLE a1_0
where
a1_0.AGENCY_ID=?
with the following Initialized:
    - SelectEagerCollectionInitializer [Agency.users]
    - EnityResultInitializer [Agency]

ListReusltsConsumers calls persistenceContext.initializeNonlazyCollections() that triggers
select u1_0.AGENCY_ID, u1_0.USER_ID, u1_0.USER_NAME
from
USER_TABLE u1_0
where
u1_0.AGENCY_ID=?
   with the following Initialized:

    - EntitySelectFetchInitializer [Agency.users.{element}.agency]
    - SelectEagerCollectionInitialzier [Agency.users.{element}.roles]  ---> the collection has no owner
    - EntityJoinedFetchInitializer [Agency.users.{element}]
    - SetInitializer [Agency.users]

select r1_0.USER_ID, r1_1.ROLE_ID,  r1_1.ROLE_NAME
from
USER_ROLE r1_0
join
ROLE_TABLE r1_1
on r1_1.ROLE_ID=r1_0.ROLE_ID
where
r1_0.USER_ID in(select
u1_0.USER_ID
from
USER_TABLE u1_0
where
u1_0.AGENCY_ID=?)
after initializeNonlazyCollections() the connection is closed causing the failures of the executions of the remaining initilizer initializeInstance() calls.

Yes, I am encountering this too! Huge pain. Thanks for fixing.


New Template for EATON ePDU

I added a template for Eaton ePDU . It was tested for the past 3 months. It was used with ePDU G3 Switched and Managed.
I couldn't find a compatible already existing template thus I decided to create a new one and to distribute it.
The template is of type SNMP_AGENT and depends on Template Module Generic SNMP.
I think it would greatly benefit this community giving the fact that Eaton ePDUs are widely used.

We wanted to thank you for your contribution to the development of the community, but we can't take your PR. Please add a directory with a version.
Example:
\_5.4
|   \_zbx_eaton-epdu_template.yaml.yaml
|   |_README.md
|_...


USHIFT-1390: Handle FDO scenario

/unhold
Unholding to allow to make progress with other dev tasks

/hold
Depends on https://github.com/openshift/microshift/pull/2037

/unhold


Add initial ARCore support for 4.x

As discussed in RocketChat this PR adds initial support for ARCore for Godot 4.x and upwards and builds a foundation to get it running. The android side of things isn't yet implemented but commented out to have compiling working.

Before merging please check if I did the rebase correctly as I had to do two rebases and I may have missed something. The fix-android branch is now obsolete since I incorporated the changes here.

Note, even though CI fails (because we haven't adjusted CI yet), we're merging this logic to create a base for our Godot 4 work.

Before merging please check if I did the rebase correctly as I had to do two rebases and I may have missed something. The fix-android branch is now obsolete since I incorporated the changes here.

As far as I could see everything seemed to be there.


Add support for PostgreSQL

I changed schema/sc_data.sql, src/scripts/data_loader.py, and src/update.py in order to support PostgreSQL.
A new command line argument '--db_type' was added to the update.py for selecting which database to be used (oracle or postgresql).
Please check them.
Your comments would be much appreciated.

@fujirock, your changes were merged to master branch.
Thank you for PR and sorry about delayed reaction.

@tadam, Thank you for your response!


[Feature Request] Cheating Mode Options

REI includes a few useful QoL features that I feel are sorely missed here:
"Cheating in Creative" allows cheating when in creative mode but not in survival mode, this saves a ton of time and energy in flipping back and forth for those who play both creative and survival.
"Cheating Style" allows a toggle between clicking on an item and 'picking it up' with the cursor similar to the creative mode vanilla menu, & simply clicking on the item to add it to the inventory, the ctrl+rmb is a bit of a chore and quite convoluted to do every time on a creative build.
Thanks for your consideration, if these are out of scope I'd love to know more about the intended scope of EMI and how that might differ from projects like REI or JEI so I can make a better informed decision about which I should be using.

"Cheating Style" exists as you'd like it to. You can rebind "cheat to cursor" (or any bind, really) to a mouse button without modifiers if you'd like, and it'll work as described, EMI is designed to layer binds like this prioritizing specialized actions over generic ones (like viewing a recipe).
When it comes to "Cheating in Creative", I'm not exactly sure what utility this serves. How would this save time switching gamemodes? EMI currently lets you cheat as long as you have permission to spawn in items, there is no need to switch to creative.

Okay sorry for the trouble, I dug through the config a little more and was able to find it

When it comes to "Cheating in Creative", I'm not exactly sure what utility this serves. How would this save time switching gamemodes? EMI currently lets you cheat as long as you have permission to spawn in items, there is no need to switch to creative.
I'd like a second consideration given to this proposal: I am often playing with cheats enabled (or with op status on multiplayer). However I would rather not cheat items in the game mistakenly, and having to switch to creative before using the cheat-item feature is a good way to unintentional summoning of items.

Also, when playing a singleplayer instance with multiple worlds (some being creative  worlds, some being survival), the option is enabled per-instance (that is, if I set cheats in a creative world where I certainly want to cheat, it is then set in my survival world as well, where I would rather not cheat).


GUIX Studio font heights above 240 pixels are not possible

Setting the font heights in GUIX studio to more than 240 pixels, e.g. 255 pixels, results in faulty behaviour. The font view doesn't show the font anymore. Moreover the font isn't shown when used in a prompt widget.
If the generated project is used with the actual hardware, the faulty behaviour stays. The font is not shown.
GUIX Studio <IP_ADDRESS>
Steps to reproduce the behavior:

Create a new GUIX studio project
Add a custom font to the project and set font heigth to 255 pixels.

@IvanThor GUIX keeps track of a metric within the GX_FONT structure called gx_font_line_height. This metric represents the sum of the maximum ascent and the maximum descent of the font glyphs. It's possible that the line height can exceed the font height, as explained in more detail at https://learn.microsoft.com/en-us/azure/rtos/guix/guix-studio-4#font-resources.  In your case, when the font height is set to a value greater than 240, the resulting line height may surpass the 255 limit of the line height. We'll add a note about this in the future.

@ting-ms Disabling ASCII as character range and just include character set defined by String Table fixed the issue indeed.

Thank you very much


Temporal types Validators are broken because of memoization os suppliers in TemporalConstraintBase

For example here: https://github.com/making/yavi/blob/0.11.0/src/main/java/am/ik/yavi/constraint/base/TemporalConstraintBase.java#L98
Value returned by a supplier gets memoized during the first method call and never changes again. If the supplier returns not a constant but dynamically changing value (for example now() timestamp) It breaks the entire concept of the supplier.

Right. Obviously it's a bug.
Memoize was introduced to print the same value in the message as the value to validate, but it's inappropriate here.

in 0.11.1, you can disable the memoization by e.g. after(() -> Instant.now(), false).
future and past no longer memoize the supplier.

Thanks a lot for quick resolution!!! I have already tested this update and everything is working as expected

Great to hear that!


fix import delay in docs

there are mistake in several docs with delay util importing
import { delay } from 'redux-saga/effects'

becouse redux-saga/effects does not exports delay, but redux-saga does itself.
So the right import line is:
import { delay } from 'redux-saga'

Implement this change for every doc where occurs

It's already importable from redux-saga/effects when using redux-saga@beta
Docs in the repository might be already updated to use it from redux-saga/effects. Published docs to https://redux-saga.js.org/ shouldnt yet have this change.


Create Repetitive element

Python3 program to find the only repeating element in an array where elements are from 1 to N-1.

great work amit beta


pin libvirt0 version on jenkins ci

Since its only needed for new installs, the 2nd conditional in the task ensures it will only run on Jenkins CI.

Build triggered. sha1 is merged.

Build started sha1 is merged.

Build finished.


[firebase_messaging]: FirebaseMessaging.onBackgroundMessage() method is never executed when notification arrives. Background message handler does not do any actions.

Is there an existing issue for this?

[X] I have searched the existing issues.

Are you aware of the differences between iOS and Android background message handling?

[X] I understand that iOS and Android background messages behave differently, and I've designed my application with that in mind.

Do you have an active Apple Developer account?

[X] I have an active Apple Developer account.

Are you using a physical iOS device to test background messages?

[X] I am using a physical iOS device to test background messages.

Have you enabled "Remote Notifications" & "Background Mode" (Checking options for "Background Processing" & "Remote Notifications") in your app's Xcode project?

Have you created an APNs key in your Apple Developer account & uploaded this APNs key to your Firebase console?

Have you disabled method swizzling for Firebase in your app?
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>CADisableMinimumFrameDurationOnPhone</key>
	<true/>
	<key>CFBundleDevelopmentRegion</key>
	<string>$(DEVELOPMENT_LANGUAGE)</string>
	<key>CFBundleExecutable</key>
	<string>$(EXECUTABLE_NAME)</string>
	<key>CFBundleIdentifier</key>
	<string>$(PRODUCT_BUNDLE_IDENTIFIER)</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>Cloud Messaging</string>
	<key>CFBundlePackageType</key>
	<string>APPL</string>
	<key>CFBundleShortVersionString</key>
	<string>$(FLUTTER_BUILD_NAME)</string>
	<key>CFBundleSignature</key>
	<string>????</string>
	<key>CFBundleVersion</key>
	<string>$(FLUTTER_BUILD_NUMBER)</string>
	<key>FirebaseAppDelegateProxyEnabled</key>
	<true/>
	<key>LSRequiresIPhoneOS</key>
	<true/>
	<key>NSBonjourServices</key>
	<array>
		<string>_dartobservatory._tcp</string>
	</array>
	<key>UIBackgroundModes</key>
	<array>
		<string>fetch</string>
		<string>processing</string>
		<string>remote-notification</string>
	</array>
	<key>UILaunchStoryboardName</key>
	<string>LaunchScreen</string>
	<key>UIMainStoryboardFile</key>
	<string>Main</string>
	<key>UISupportedInterfaceOrientations</key>
	<array>
		<string>UIInterfaceOrientationPortrait</string>
		<string>UIInterfaceOrientationLandscapeLeft</string>
		<string>UIInterfaceOrientationLandscapeRight</string>
	</array>
	<key>UISupportedInterfaceOrientations~ipad</key>
	<array>
		<string>UIInterfaceOrientationPortrait</string>
		<string>UIInterfaceOrientationPortraitUpsideDown</string>
		<string>UIInterfaceOrientationLandscapeLeft</string>
		<string>UIInterfaceOrientationLandscapeRight</string>
	</array>
	<key>UIViewControllerBasedStatusBarAppearance</key>
	<false/>
</dict>
</plist>

Are you sending messages to your app from the Firebase Admin SDK?
admin
  .messaging()
  .sendToDevice(
    [token],
    {
      data: {
        foo: 'bar',
      },
      notification: {
        title: 'A great title',
        body: 'Great content',
      },
    },
    {
      // Required for background/terminated app state messages on iOS
      contentAvailable: true,
      // Required for background/terminated app state messages on Android
      priority: 'high',
    }
  )
  .then((res) => {
    if (res.failureCount) {
      console.log('Failed', res.results[0].error);
    } else {
      console.log('Success');
    }
  })
  .catch((err) => {
    console.log('Error:', err);
  });

Have you requested permission from the user to receive notifications?

[X] I have the relevant permission to receive notifications.

Have you used the 'Console' application on your macOS device to check if the iOS device's system is throttling your background messages?
default	16:09:59.751194+0800	SpringBoard	Received incoming message on topic id.example.akd.fcm at priority 10
default	16:09:59.778287+0800	SpringBoard	[id.example.akd.fcm] Received remote notification request 625B-D052 [ waking: 0, hasAlertContent: 1, hasSound: 0 hasBadge: 0 hasContentAvailable: 1 hasMutableContent: 0 pushType: Alert]
default	16:09:59.778384+0800	SpringBoard	[id.example.akd.fcm] Process delivery of push notification 625B-D052
default	16:09:59.778441+0800	SpringBoard	[id.example.akd.fcm] Request DUET delivers content-available push notification to application
default	16:09:59.778637+0800	SpringBoard	SUBMITTING: com.apple.pushLaunch.id.example.akd.fcm:6FDDBA
default	16:09:59.780523+0800	dasd	Submitted Activity: com.apple.pushLaunch.id.example.akd.fcm:6FDDBA at priority 10 (Fri Dec  9 16:09:59 2022 - Sat Dec 10 16:09:59 2022)
default	16:09:59.781455+0800	SpringBoard	[id.example.akd.fcm] Badge can be set for notification 625B-D052: 0 [ canBadge: 1 badgeNumber: (null) ]
default	16:09:59.781611+0800	SpringBoard	Getting effectiveSectionInfo for section identifier: id.example.akd.fcm
default	16:09:59.781758+0800	SpringBoard	[id.example.akd.fcm] Getting effective section info
default	16:09:59.787216+0800	SpringBoard	[id.example.akd.fcm] Got effective section info [ hasResult: 1 ]
default	16:09:59.787502+0800	SpringBoard	Getting effectiveSectionInfo for section identifier: id.example.akd.fcm
default	16:09:59.787583+0800	SpringBoard	[id.example.akd.fcm] Getting effective section info
default	16:09:59.789712+0800	SpringBoard	[id.example.akd.fcm] Got effective section info [ hasResult: 1 ]
default	16:09:59.790007+0800	SpringBoard	[id.example.akd.fcm] Saving notification 625B-D052: YES [ hasAlertContent: YES, shouldPresentAlert: YES settingsShouldSave: YES]
default	16:09:59.791292+0800	dasd	com.apple.pushLaunch.id.example.akd.fcm:6FDDBA:[
	{name: ApplicationPolicy, policyWeight: 50.000, response: {Decision: Absolutely Must Proceed, Score: 1.00, Rationale: [{[appIsForeground]: Required:1.00, Observed:1.00},]}}
 ], FinalDecision: Absolutely Must Proceed}
default	16:09:59.793371+0800	dasd	[FBSSystemService][0x288a] Sending request to open "id.example.akd.fcm"
default	16:09:59.800018+0800	SpringBoard	[FBSystemService][0x288a] Received request to open "id.example.akd.fcm" from dasd:79.
default	16:09:59.800558+0800	SpringBoard	Received trusted open application request for "id.example.akd.fcm" from <FBProcess: 0xd6de22cd0; osservice<com.apple.dasd>:79(v125)>.
default	16:09:59.815499+0800	SpringBoard	[id.example.akd.fcm] Delivered user visible push notification 625B-D052
default	16:09:59.821661+0800	SpringBoard	[id.example.akd.fcm] Load 0 pending notification dictionaries
default	16:09:59.821954+0800	SpringBoard	[id.example.akd.fcm] Adding notification 625B-D052 [ hasAlertContent: 1, shouldPresentAlert: 1 hasSound: 0 shouldPlaySound: 1 ]; interruption-level: 1; destinations 398: (
    NotificationCenter,
    LockScreen,
    Alert,
    Spoken,
    Forwarding
)
default	16:09:59.823951+0800	SpringBoard	BBDataProviderProxy id.example.akd.fcm has enqueued a bulletin request
default	16:09:59.824007+0800	SpringBoard	BBDataProviderProxy id.example.akd.fcm is now sending enqueued bulletin request to BBServer
default	16:09:59.826529+0800	SpringBoard	Executing request: <SBMainWorkspaceTransitionRequest: 0x280950c60; eventLabel: OpenApplication(sceneID:id.example.akd.fcm-default)ForRequester(dasd.79); display: Main; source: FBSystemService>
default	16:09:59.827819+0800	SpringBoard	Publishing bulletin for section <id.example.akd.fcm>: subsectionIDs: (null), bulletinID = <A4CD7FFE-E409-41F6-96F6-832CD110CEAF>, expiration date = <Fri Dec 16 16:09:59 2022>, expiration events <0>
default	16:09:59.829241+0800	SpringBoard	Attempt gateway BBObserverGatewayLocalName for bulletin A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm
default	16:09:59.829293+0800	SpringBoard	Gateway BBObserverGatewayLocalName sending add bulletin lights and sirens YES for A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm with timeout 20.000000 WITH handler
default	16:09:59.829339+0800	SpringBoard	Gateway BBObserverGatewayLocalName add timer (Fri Dec  9 16:10:19 2022) for bulletin A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm
default	16:09:59.829387+0800	SpringBoard	Gateway BBObserverGatewayLocalName start timer (Fri Dec  9 16:10:19 2022) for out for bulletin A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm
default	16:09:59.837028+0800	SpringBoard	Executing suspended-activation immediately: OpenApplication(sceneID:id.example.akd.fcm-default)ForRequester(dasd.79)
default	16:09:59.837090+0800	SpringBoard	[FBWorkspaceEvent] Executing: <FBWorkspaceEvent: 0x287c83340; OpenApplication(sceneID:id.example.akd.fcm-default)ForRequester(dasd.79)>
default	16:09:59.837172+0800	SpringBoard	[FBWorkspaceEvent] Executing: <FBWorkspaceEvent: 0x287c814a0; OpenApplication(sceneID:id.example.akd.fcm-default)ForRequester(dasd.79)>
default	16:09:59.854507+0800	SpringBoard	[0x2801e5380:(FBSceneManager):sceneID:id.example.akd.fcm-default] Scene activity mode did change: support (transient).
default	16:09:59.854803+0800	SpringBoard	[0x2801e5380:(FBSceneManager):sceneID:id.example.akd.fcm-default] Scene assertion state did change: BackgroundActive.
default	16:09:59.855257+0800	SpringBoard	[application<id.example.akd.fcm>:5676] Workspace assertion state did change: BackgroundActive (acquireAssertion = YES).
default	16:09:59.858294+0800	runningboardd	Acquiring assertion targeting [application<id.example.akd.fcm>:5676] from originator [osservice<com.apple.dasd>:79] with description <RBSAssertionDescriptor| "com.apple.das.backgroundFetch" ID:31-79-77536 target:5676 attributes:[
	<RBSDomainAttribute| domain:"com.apple.dasd" name:"BackgroundDownload" sourceEnvironment:"(null)">
	]>
default	16:09:59.858630+0800	runningboardd	Assertion 31-79-77536 (target:[application<id.example.akd.fcm>:5676]) will be created as active
default	16:09:59.860173+0800	runningboardd	Deactivating delayed assertion 31-5676-77534 (target:[application<id.example.akd.fcm>:5676])
default	16:09:59.860440+0800	runningboardd	Acquiring assertion targeting [application<id.example.akd.fcm>:5676] from originator [osservice<com.apple.SpringBoard>:32] with description <RBSAssertionDescriptor| "FBWorkspace (BackgroundActive)" ID:31-32-77537 target:5676 attributes:[
	<RBSDomainAttribute| domain:"com.apple.frontboard" name:"Workspace-BackgroundActive" sourceEnvironment:"(null)">
	]>
default	16:09:59.860564+0800	runningboardd	Assertion 31-32-77537 (target:[application<id.example.akd.fcm>:5676]) will be created as active
default	16:09:59.860795+0800	runningboardd	Calculated state for application<id.example.akd.fcm>: running-active (role: Background)
default	16:09:59.861413+0800	powerd	Process runningboardd.31 Released SystemIsActive "application<id.example.akd.fcm>31-5676-77534:Shared Background Assertion 3 for id.example.akd.fcm(FinishTask)" age:00:00:23  id:51539646788 [System: SysAct]
default	16:09:59.861874+0800	SpringBoard	<private> adding bulletin 625B-D052 for feed 3115 in section id.example.akd.fcm playLightsAndSirens: YES
default	16:09:59.863055+0800	SpringBoard	Gateway BBObserverGatewayLocalName received DID play lights and sirens for bulletin A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm
default	16:09:59.863122+0800	runningboardd	[application<id.example.akd.fcm>:5676] set Memory Limits to Hard Inactive (1850)
default	16:09:59.863218+0800	SpringBoard	Gateway BBObserverGatewayLocalName invalidated timer (Fri Dec  9 16:10:19 2022) for out for bulletin A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm
default	16:09:59.863585+0800	runningboardd	Calculated state for application<id.example.akd.fcm>: running-active (role: NonUserInteractive)
default	16:09:59.864020+0800	runningboardd	[application<id.example.akd.fcm>:5676] Set darwin role to: NonUserInteractive
default	16:09:59.865155+0800	runningboardd	[application<id.example.akd.fcm>:5676] set Memory Limits to Hard Inactive (1850)
default	16:09:59.869329+0800	SpringBoard	Gateway enumerator received from BBObserverGatewayLocalName DID play lights and sirens for A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm currently NOT cancelled
default	16:09:59.869440+0800	SpringBoard	Attempt gateway GizmoGateway for bulletin A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm
default	16:09:59.869489+0800	SpringBoard	Gateway GizmoGateway sending add bulletin lights and sirens NO for A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm with NO timeout and NO handler
default	16:09:59.869601+0800	SpringBoard	Gateway enumerator received from GizmoGateway DID NOT play lights and sirens for A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm currently NOT cancelled
default	16:09:59.869647+0800	SpringBoard	Gateway enumerator was completed for bulletin A4CD7FFE-E409-41F6-96F6-832CD110CEAF in section id.example.akd.fcm
default	16:09:59.870429+0800	Firebase Cloud Messaging Example	sceneOfRecord: sceneID: sceneID:id.example.akd.fcm-default  persistentID: B13DD751-0724-4880-AC38-38C30938A8F1
default	16:09:59.881337+0800	SpringBoard	NCBulletinNotificationSource adding bulletin 625B-D052 for feed 3115 in section id.example.akd.fcm
default	16:09:59.888588+0800	SpringBoard	[0x2801e5380:(FBSceneManager):sceneID:id.example.akd.fcm-default] Scene activity mode did change: suspended.
default	16:09:59.888981+0800	SpringBoard	[0x2801e5380:(FBSceneManager):sceneID:id.example.akd.fcm-default] Scene assertion state did change: None.
default	16:09:59.889202+0800	SpringBoard	[application<id.example.akd.fcm>:5676] Workspace assertion state did change: None (acquireAssertion = NO).
default	16:09:59.890650+0800	runningboardd	Invalidating assertion 31-32-77537 (target:[application<id.example.akd.fcm>:5676]) from originator [osservice<com.apple.SpringBoard>:32]
default	16:09:59.898833+0800	backboardd	new deferring rules for pid:5676: [<environment: keyboardFocus; display: builtin; token: com.apple.frontboard.systemappservices::FBSceneManager:sceneID%3Aid.example.akd.fcm-default> -> <pid: 5676; token: 0x6AF09844> reason: "2-defer: UIWindowScene: 0x129f042c0: Begin event deferring in keyboardFocus for window: 0x129f2f370"]
default	16:09:59.938426+0800	BTLEServer	[com.apple.BTLEServer.ANCS:3955A5B0-D26C-4F77-953F-45266F323D20] Resolving behavior for event, details=<DNDMutableClientEventDetails: 0x588caec20; identifier: 'CE3A0D0E-8A84-436E-9681-4C0F32D64638'; bundleIdentifier:: id.example.akd.fcm; type: Default; urgency: Default; sender: (null); threadIdentifier: D3BA19072F4CB734; filterCritera: (null); notifyAnyway: 0; behavior: Default>
default	16:09:59.947818+0800	donotdisturbd	Event was resolved: resolution=<DNDSEventBehaviorResolution: 0x644d09fe0; UUID: D269A233-CB1A-4AA9-B83F-4C82C2A9CC68; date: 2022-12-09 08:09:59 +0000; eventBehavior: <DNDClientEventBehavior: 0x644e056e0; eventDetails: <DNDClientEventDetails: 0x644e057a0; identifier: 'CE3A0D0E-8A84-436E-9681-4C0F32D64638'; bundleIdentifier:: id.example.akd.fcm; type: Default; urgency: Default; sender: (null); threadIdentifier: D3BA19072F4CB734; filterCritera: (null); notifyAnyway: 0; behavior: Default>; interruptionSuppression: none; resolutionReason: disabled; activeModeUUID: (null)>; clientIdentifier: 'com.apple.BTLEServer.ANCS'; outcome: allowed; reason: disabled>
default	16:09:59.949011+0800	BTLEServer	[com.apple.BTLEServer.ANCS:3955A5B0-D26C-4F77-953F-45266F323D20] Resolved event, details=<DNDMutableClientEventDetails: 0x588caec20; identifier: 'CE3A0D0E-8A84-436E-9681-4C0F32D64638'; bundleIdentifier:: id.example.akd.fcm; type: Default; urgency: Default; sender: (null); threadIdentifier: D3BA19072F4CB734; filterCritera: (null); notifyAnyway: 0; behavior: Default> behavior=<DNDClientEventBehavior: 0x588fa8610; eventDetails: <DNDClientEventDetails: 0x588fc32a0; identifier: 'CE3A0D0E-8A84-436E-9681-4C0F32D64638'; bundleIdentifier:: id.example.akd.fcm; type: Default; urgency: Default; sender: (null); threadIdentifier: D3BA19072F4CB734; filterCritera: (null); notifyAnyway: 0; behavior: Default>; interruptionSuppression: none; resolutionReason: disabled; activeModeUUID: (null)>
default	16:09:59.991385+0800	SpringBoard	[com.apple.springboard.NCBulletinNotificationSource:349B73FF-E1DC-43C6-83DD-1753E5AA8E57] Resolving behavior for event, details=<DNDMutableClientEventDetails: 0x281b59770; identifier: 'CE3A0D0E-8A84-436E-9681-4C0F32D64638'; bundleIdentifier:: id.example.akd.fcm; type: Default; urgency: Default; sender: (null); threadIdentifier: D3BA19072F4CB734; filterCritera: (null); notifyAnyway: 0; behavior: Default>
default	16:09:59.992443+0800	SpringBoard	[id.example.akd.fcm] START liquidating the old, as snapshot generation succeeded
default	16:09:59.999003+0800	symptomsd	SymptomAnalytics ServiceImpl: FAE perform query for dasd (pid 79) on LiveUsage predicate hasProcess.bundleName == $targetname sort (null) actions {
    "hasProcess.procName" = copyRelationship;
    refreshUsage = refreshUsage;
    "hasProcess.firstTimeStamp" = copyRelationship;
    "hasProcess.bundleName" = copyRelationship;
    nameChain = "id.example.akd.fcm";
    "<null>" = "<null>";
} properties (null)
default	16:09:59.999285+0800	SpringBoard	<XBApplicationSnapshotManifestImpl: 0x2816ea300> [id.example.akd.fcm] Snapshot data for <XBApplicationSnapshot: 0xd6f13ae10; …B02BE9F565FD> [id.example.akd.fcm] written to file<EMAIL_ADDRESS>default	16:09:59.999378+0800	donotdisturbd	Event was resolved: resolution=<DNDSEventBehaviorResolution: 0x644a55960; UUID: 4D177CD2-68BD-4751-986A-D7EC25528D5B; date: 2022-12-09 08:09:59 +0000; eventBehavior: <DNDClientEventBehavior: 0x644a219b0; eventDetails: <DNDClientEventDetails: 0x644a346b0; identifier: 'CE3A0D0E-8A84-436E-9681-4C0F32D64638'; bundleIdentifier:: id.example.akd.fcm; type: Default; urgency: Default; sender: (null); threadIdentifier: D3BA19072F4CB734; filterCritera: (null); notifyAnyway: 0; behavior: Default>; interruptionSuppression: none; resolutionReason: disabled; activeModeUUID: (null)>; clientIdentifier: 'com.apple.springboard.NCBulletinNotificationSource'; outcome: allowed; reason: disabled>
default	16:10:00.000067+0800	SpringBoard	[com.apple.springboard.NCBulletinNotificationSource:349B73FF-E1DC-43C6-83DD-1753E5AA8E57] Resolved event, details=<DNDMutableClientEventDetails: 0x281b59770; identifier: 'CE3A0D0E-8A84-436E-9681-4C0F32D64638'; bundleIdentifier:: id.example.akd.fcm; type: Default; urgency: Default; sender: (null); threadIdentifier: D3BA19072F4CB734; filterCritera: (null); notifyAnyway: 0; behavior: Default> behavior=<DNDClientEventBehavior: 0x2834ae310; eventDetails: <DNDClientEventDetails: 0x281b93930; identifier: 'CE3A0D0E-8A84-436E-9681-4C0F32D64638'; bundleIdentifier:: id.example.akd.fcm; type: Default; urgency: Default; sender: (null); threadIdentifier: D3BA19072F4CB734; filterCritera: (null); notifyAnyway: 0; behavior: Default>; interruptionSuppression: none; resolutionReason: disabled; activeModeUUID: (null)>
default	16:10:00.000937+0800	SpringBoard	[id.example.akd.fcm] deleting old snapshots: (
    "<XBApplicationSnapshot: 0xd6ae40050; identifier: FF151F26-F9FD-4E00-A252-2B67C151D3A1; contentType: SceneContent; referenceSize: {375, 812}; interfaceOrientation: Portrait; userInterfaceStyle: Dark> {\n    creationDate = 9 December 2022 16.09.37 GMT+8;\n    keepsImageAccessUntilExpiration = NO;\n    hasGenerationContext = NO;\n    purge = high;\n    context = {\n        contentType = SceneContent;\n        fullScreen = YES;\n        referenceSize = {375, 812};\n        contentFrame = {{0, 0}, {375, 812}};\n        interfaceOrientation = Portrait;\n        userInterfaceStyle = Dark;\n        customSafeAreaInsets = <XBDisplayEdgeInsetsWrapper: 0x2836d70c0; topInset: 44.0; leftInset: 0.0; bottomInset: 34.0; rightInset: 0.0>;\n        additionalContext = {\n            statusBarSettings = <XBStatusBarSettings: 0x28386fc20; hidden: NO; style: UIStatusBarStyleLightContent; backgroundActivityEnabled: NO>;\n        }\n    }\n    imageContext = {\n        scale = 3.0;\n        opaque = YES;\n        fileRelativeLocation = default;\n        path = /private/var/mobile/Containers/Data/Application/5DC0706E-E933-4C00-8562-3694337478E9/Library/SplashBoard/Snapshots/sceneID:id.example.akd.fcm-default/FF151F26-F9FD-4E00-A252-2B67C151D3A1@3x.ktx;\n        fileFormat = ktx;\n    }\n    variants = {\n        downscaled = <XBApplicationSnapshot: 0xd6f231a60; identifier: AD461A4E-FB07-41B5-93A6-06C328BE8084; variantID: downscaled; contentType: SceneContent; referenceSize: {375, 812}; interfaceOrientation: Portrait; userInterfaceStyle: Dark> {\n            creationDate = 9 December 2022 16.09.37 GMT+8;\n            keepsImageAccessUntilExpiration = NO;\n            hasGenerationContext = NO;\n            purge = high;\n            context = {\n                contentType = SceneContent;\n                fullScreen = YES;\n                referenceSize = {375, 812};\n                contentFrame = {{0, 0}, {375, 812}};\n                interfaceOrientation = Portrait;\n                userInterfaceStyle = Dark;\n                customSafeAreaInsets = <XBDisplayEdgeInsetsWrapper: 0x2836d70c0; topInset: 44.0; leftInset: 0.0; bottomInset: 34.0; rightInset: 0.0>;\n                additionalContext = {\n                    statusBarSettings = <XBStatusBarSettings: 0x28386fc20; hidden: NO; style: UIStatusBarStyleLightContent; backgroundActivityEnabled: NO>;\n                }\n            }\n            imageContext = {\n                scale = 3.0;\n                opaque = YES;\n                fileRelativeLocation = default;\n                path = /private/var/mobile/Containers/Data/Application/5DC0706E-E933-4C00-8562-3694337478E9/Library/SplashBoard/Snapshots/sceneID:id.example.akd.fcm-default/downscaled/AD461A4E-FB07-41B5-93A6-06C328BE8084@3x.ktx;\n                fileFormat = ktx;\n            }\n        };\n    }\n}",
    "<XBApplicationSnapshot: 0xd6f231a60; identifier: AD461A4E-FB07-41B5-93A6-06C328BE8084; variantID: downscaled; contentType: SceneContent; referenceSize: {375, 812}; interfaceOrientation: Portrait; userInterfaceStyle: Dark> {\n    creationDate = 9 December 2022 16.09.37 GMT+8;\n    keepsImageAccessUntilExpiration = NO;\n    hasGenerationContext = NO;\n    purge = high;\n    context = {\n        contentType = SceneContent;\n        fullScreen = YES;\n        referenceSize = {375, 812};\n        contentFrame = {{0, 0}, {375, 812}};\n        interfaceOrientation = Portrait;\n        userInterfaceStyle = Dark;\n        customSafeAreaInsets = <XBDisplayEdgeInsetsWrapper: 0x2836d70c0; topInset: 44.0; leftInset: 0.0; bottomInset: 34.0; rightInset: 0.0>;\n        additionalContext = {\n            statusBarSettings = <XBStatusBarSettings: 0x28386fc20; hidden: NO; style: UIStatusBarStyleLightContent; backgroundActivityEnabled: NO>;\n        }\n    }\n    imageContext = {\n        scale = 3.0;\n        opaque = YES;\n        fileRelativeLocation = default;\n        path = /private/var/mobile/Containers/Data/Application/5DC0706E-E933-4C00-8562-3694337478E9/Library/SplashBoard/Snapshots/sceneID:id.example.akd.fcm-default/downscaled/AD461A4E-FB07-41B5-93A6-06C328BE8084@3x.ktx;\n        fileFormat = ktx;\n    }\n}"
)
default	16:10:00.001410+0800	SpringBoard	<XBApplicationSnapshotManifestImpl: 0x2816ea300> [id.example.akd.fcm] Deleting snapshots: (
    "<XBApplicationSnapshot: 0xd6ae40050; identifier: FF151F26-F9FD-4E00-A252-2B67C151D3A1; contentType: SceneContent; referenceSize: {375, 812}; interfaceOrientation: Portrait; userInterfaceStyle: Dark>",
    "<XBApplicationSnapshot: 0xd6f231a60; identifier: AD461A4E-FB07-41B5-93A6-06C328BE8084; variantID: downscaled; contentType: SceneContent; referenceSize: {375, 812}; interfaceOrientation: Portrait; userInterfaceStyle: Dark>"
)
default	16:10:00.001485+0800	SpringBoard	<XBApplicationSnapshotManifestImpl: 0x2816ea300> [id.example.akd.fcm] Deleting snapshot <XBApplicationSnapshot: 0xd6ae40050; …2B67C151D3A1> [id.example.akd.fcm] for reason: _contentType: SceneContent(0)
default	16:10:00.001718+0800	SpringBoard	<XBApplicationSnapshotManifestImpl: 0x2816ea300> [id.example.akd.fcm] Deleting snapshot <XBApplicationSnapshot: 0xd6f231a60; …06C328BE8084> [id.example.akd.fcm] for reason: _contentType: SceneContent(0)
default	16:10:00.002336+0800	SpringBoard	<XBApplicationSnapshotManifestImpl: 0x2816ea300> [id.example.akd.fcm] Deleting paths: <private>
default	16:10:00.002599+0800	SpringBoard	[id.example.akd.fcm] deleting old suspend snapshots using predicate: <XBApplicationSnapshotPredicate: 0x283806570> {
    name = SBSuspendSnapshot;
    contentTypeMask = SceneContent;
}
default	16:10:00.002753+0800	SpringBoard	[id.example.akd.fcm] STOP liquidating the old
default	16:10:00.012881+0800	SpringBoard	Posting notification id: 625B-D052; section: id.example.akd.fcm; thread: A274-68C2; category: ; timestamp: 2022-12-09 08:09:59 +0000; interruption-level: active; relevance-score: 0.00; filter-criteria: (null); actions: [ minimal: 0 (0 text), default: 0 (0 text) ]; destinations: [ {(
    BulletinDestinationCoverSheet,
    BulletinDestinationBanner,
    BulletinDestinationNotificationCenter,
    BulletinDestinationLockScreen
)} ]
default	16:10:00.013278+0800	runningboardd	[application<id.example.akd.fcm>:5676] Set darwin role to: Background
default	16:10:00.013345+0800	runningboardd	Calculated state for application<id.example.akd.fcm>: running-active (role: Background)
default	16:10:00.013634+0800	runningboardd	[application<id.example.akd.fcm>:5676] set Memory Limits to Hard Inactive (1850)
default	16:10:00.018155+0800	SpringBoard	Incoming Section [NCNotificationStructuredSectionList] inserting notification request 625B-D052 in existing group Group List [id.example.akd.fcm:A274-68C2] at index 0
default	16:10:00.018204+0800	SpringBoard	Group List [id.example.akd.fcm:A274-68C2] inserting notification request 625B-D052 at index 0
default	16:10:00.034286+0800	SpringBoard	<XBApplicationSnapshotManifestImpl: 0x2816ea300> [id.example.akd.fcm] Snapshot data for <XBApplicationSnapshot: 0xd6ae9c520; …B68A27424D8D> [id.example.akd.fcm] written to file<EMAIL_ADDRESS>default	16:10:00.143481+0800	symptomsd	entry: Wed Dec  7 16:58:15 2022                        id.example.akd.fcm (bundle)        208823       128154       213975        81851   0   1
default	16:10:00.145450+0800	runningboardd	Invalidating assertion 31-79-77536 (target:[application<id.example.akd.fcm>:5676]) from originator [osservice<com.apple.dasd>:79]
default	16:10:00.146584+0800	symptomsd	SymptomAnalytics ServiceImpl: FAE perform query for dasd (pid 79) on LiveUsage predicate hasProcess.bundleName == $targetname sort (null) actions {
    "hasProcess.procName" = copyRelationship;
    refreshUsage = refreshUsage;
    "hasProcess.firstTimeStamp" = copyRelationship;
    "hasProcess.bundleName" = copyRelationship;
    nameChain = "id.example.akd.fcm";
    "<null>" = "<null>";
} properties (null)
default	16:10:00.148015+0800	symptomsd	entry: Wed Dec  7 16:58:15 2022                        id.example.akd.fcm (bundle)        208823       128154       213975        81851   0   1
default	16:10:00.150633+0800	SpringBoard	STARTING: com.apple.pushLaunch.id.example.akd.fcm:6FDDBA
default	16:10:00.151402+0800	dasd	COMPLETED com.apple.pushLaunch.id.example.akd.fcm:6FDDBA at priority 10 <private>!
default	16:10:00.151460+0800	dasd	NO LONGER RUNNING com.apple.pushLaunch.id.example.akd.fcm:6FDDBA ...Tasks running in group [com.apple.dasd.defaultNetwork] are 1!
default	16:10:00.252993+0800	runningboardd	Removed last relative-start-date-defining assertion for process application<id.example.akd.fcm>
default	16:10:00.253062+0800	runningboardd	Activating delayed assertion 31-5676-77534 (target:[application<id.example.akd.fcm>:5676])
default	16:10:00.255131+0800	runningboardd	Calculated state for application<id.example.akd.fcm>: running-active (role: Background)
default	16:10:00.255562+0800	runningboardd	[application<id.example.akd.fcm>:5676] set Memory Limits to Hard Inactive (1850)
default	16:10:00.255906+0800	powerd	Process runningboardd.31 Created SystemIsActive "application<id.example.akd.fcm>31-5676-77534:Shared Background Assertion 3 for id.example.akd.fcm(FinishTask)" age:00:00:00  id:51539646789 [System: SysAct]
default	16:10:00.720715+0800	duetexpertd	Getting notification source id.example.akd.fcm (sync)
default	16:10:00.720794+0800	SpringBoard	UNSNotificationSettingsService [id.example.akd.fcm] Getting Notification Source For BundleIdentifier
default	16:10:00.720860+0800	SpringBoard	Getting effectiveSectionInfo for section identifier: id.example.akd.fcm
default	16:10:00.720942+0800	SpringBoard	[id.example.akd.fcm] Getting effective section info
default	16:10:00.721728+0800	SpringBoard	[id.example.akd.fcm] Got effective section info [ hasResult: 1 ]
default	16:10:00.721774+0800	SpringBoard	UNSNotificationSettingsService [id.example.akd.fcm] Returning Notification Source For BundleIdentifier <UNNotificationSource: 0x283470cf0; identifier: id.example.akd.fcm isHidden: NO, displayName: Cloud Messaging, icon: <UNNotificationIcon: 0x287aa2940; iconInfo: id.example.akd.fcm; iconInfoType: Application Identifier>, source settings: <UNNotificationSourceSettings: 0x287aa3740; notification settings: <UNNotificationSettings: 0x280940e10; authorizationStatus: Authorized, notificationCenterSetting: Enabled, soundSetting: Enabled, badgeSetting: Enabled, lockScreenSetting: Enabled, carPlaySetting: NotSupported, announcementSetting: Disabled, criticalAlertSetting: NotSupported, timeSensitiveSetting: NotSupported, alertSetting: Enabled, scheduledDeliverySetting: Disabled, directMessagesSetting: NotSupported, alertStyle: Banner, groupingSetting: Default providesAppNotificationSettings: No> topic settings: (
), isRestricted: NO>
default	16:10:00.721956+0800	duetexpertd	Got notification source <UNNotificationSource: 0xb6ae42170; identifier: id.example.akd.fcm isHidden: NO, displayName: Cloud Messaging, icon: <UNNotificationIcon: 0xb6ae2dbe0; iconInfo: id.example.akd.fcm; iconInfoType: Application Identifier>, source settings: <UNNotificationSourceSettings: 0xb6ae2c920; notification settings: <UNNotificationSettings: 0xb6ae41f90; authorizationStatus: Authorized, notificationCenterSetting: Enabled, soundSetting: Enabled, badgeSetting: Enabled, lockScreenSetting: Enabled, carPlaySetting: NotSupported, announcementSetting: Disabled, criticalAlertSetting: NotSupported, timeSensitiveSetting: NotSupported, alertSetting: Enabled, scheduledDeliverySetting: Disabled, directMessagesSetting: NotSupported, alertStyle: Banner, groupingSetting: Default providesAppNotificationSettings: No> topic settings: (
), isRestricted: NO>

Additional context and comments
The notifications show when the app is in the background but the background message handler doesn't handle it. This only affects iOS. I run the example project but still doesn't work. I have already seen this https://github.com/firebase/flutterfire/issues/9563 but still doesn't work.
Here's my flutter doctor -v :
[✓] Flutter (Channel stable, 3.3.9, on macOS 13.0 22A380 darwin-arm, locale en-ID)
    • Flutter version 3.3.9 on channel stable at /Users/mini16gboffice1/Documents/Flutter/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b8f7f1f986 (2 weeks ago), 2022-11-23 06:43:51 +0900
    • Engine revision 8f2221fbef
    • Dart version 2.18.5
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/mini16gboffice1/Library/Android/sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[✓] VS Code (version 1.74.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                            • android-arm64  • Android 12 (API 32) (emulator)
    • Adhitya's iPhone X (mobile) • 0d9a002477bfaf01631b4c5236349b2880716c62 • ios            • iOS 16.1.2 20B110
    • macOS (desktop)             • macos                                    • darwin-arm64   • macOS 13.0 22A380 darwin-arm
    • Chrome (web)                • chrome                                   • web-javascript • Google Chrome 108.0.5359.98

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Is there any solution or workaround for this issue? Thank you.

The notifications show when the app is in the background but the background message handler doesn't handle it.

@adhityapaf Can you please elaborate when you say the handler doesn't handle it ? When the app is in background and notification is triggered, it is being received properly and shows up in the tray, so what exactly is the issue you are facing ?

When user switched to different app and notification comes, the background message handler does not do any actions but notifications showed up in tray @darshankawar

FirebaseMessaging.onBackgroundMessage(firebaseMessagingBackgroundHandler);
Business methods cannot be called when iOS switches to the background. Is this the case with iOS mechanisms, or does FCM not support calling other methods when iOS switches to the background?

Please check if your use case is similar to https://github.com/firebase/flutterfire/issues/9625 and if https://github.com/firebase/flutterfire/issues/9625#issuecomment-1307095122 helps.

I have checked that comment @darshankawar, I try to add mutableContent: true below contentAvailable in my payload and it seems not to solve my issue.

I think this most probably is similar to https://github.com/firebase/flutterfire/issues/9563 but keeping this issue open for team's attention and insights.

Same issue on IOS, after flutter app minimized, FirebaseMessaging.onBackground never executed, push notification still showing but background handler never executed, and its not even silent notification

I think there is a problem in method onBackgroundMessage in ios, maybe in native native code problem, because i tried running function in background using just @pragma(vm-entrypoint) in flutter, and then minimized the app and the function successfully executed in background. but when you minimized your flutter app and send notification even after just one second after you minimize your app, this FirebaseMessaging.onBacgroundMessage is never called, notification still showing in apple notification center

Same Here. I cannot execute any function(I Save to db all notifications received) in flutter side, but the push still appear.
Is there a way to execute a function when receiving notification on Background?
@darshankawar maybe it is a bug

@atrope Hi, have you found any solution? I am also facing this problem.

@adhityapaf
Can you set the push type to be background and remove any alert / user interaction fields?
More details here (check the "Create a Background Notification") section -
https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/pushing_background_updates_to_your_app
Few things to check per the above link -

apns-push-type header field should be set to 'background' (required for watchOS)
apns-priority header must be set to 5
"... aps dictionary must not contain any keys that would trigger user interactions."

Hey @adhityapaf, I've just tested on the test app and I received the messages in the background handler. I'd like you to try the following. Run the app from Xcode. Put a break point here. Let me know if it gets to this point and log out the notificationDict in the Xcode console. Just call po notificationDict and it will log out the dictionary. If it doesn't get there, please remove the notification object where you send the message. Like so:
admin
  .messaging()
  .sendToDevice(
    [token],
    {
      data: {
        foo: 'bar',
      },
    },
    {
      // Required for background/terminated app state messages on iOS
      contentAvailable: true,
      // Required for background/terminated app state messages on Android
      priority: 'high',
    }
  )
  .then((res) => {
    if (res.failureCount) {
      console.log('Failed', res.results[0].error);
    } else {
      console.log('Success');
    }
  })
  .catch((err) => {
    console.log('Error:', err);
  });

Let me know if it gets to that break point. Thanks

Hi @russellwheatley, I tried your tips but it does not show any outputs of po notificationDict. I modified completionHandler in AppDelegate.m for showing notification outputs with this:
- (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo
fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler {
  // Handle the notification here
    NSLog(@"received notification called: %@", userInfo);
  // Call the completion handler with the appropriate result
  completionHandler(UIBackgroundFetchResultNewData);
}

Here are my terminal outputs:
// With notification field
2023-02-16 11:22:53.559850+0800 Firebase Cloud Messaging Example[24617:3824593] received notification called: {
    aps =     {
        alert =         {
            body = "Great content";
            title = "A great title";
        };
        "content-available" = 1;
    };
    foo = bar;
    "gcm.message_id" =<PHONE_NUMBER>305451;
    "google.c.a.e" = 1;
    "google.c.fid" = "c56vCMjH7Eklmw-0ke-Cwj";
    "google.c.sender.id" =<PHONE_NUMBER>514;
}

// Without notification field
2023-02-16 11:23:14.952554+0800 Firebase Cloud Messaging Example[24617:3824593] received notification called: {
    aps =     {
        "content-available" = 1;
    };
    foo = bar;
    "gcm.message_id" =<PHONE_NUMBER>567758;
    "google.c.fid" = "c56vCMjH7Eklmw-0ke-Cwj";
    "google.c.sender.id" =<PHONE_NUMBER>514;
}
(lldb) po notificationDict
error: expression failed to parse:
error: <user expression 4>:1:1: use of undeclared identifier 'notificationDict'
notificationDict
^

Also, it should print Handling a background message ${message.messageId} when the message comes and the app is in the background state.

Hi @aashishpatil-g, I tried your tips but still not receiving any background messages. Here's my function to send notifications from admin sdk:
var data ={
  "title": 'this is great title',
  "body" : 'this is body',
};
admin.messaging().send({
  data:{...data, notificationType: 'chat'},
  token: token,
  android: {
    priority: 'high',
    data,
  },
  apns: {
    payload: {
      aps: {
        contentAvailable: true,
        mutableContent: true,
      },
    },
    headers: {
      'apns-push-type': 'background',
      'apns-priority': '5',
      'apns-topic': 'id.example.akd.fcm',
    },
  },
}).then((res) => {
  if (res.failureCount) {
    console.log('failed', res.results[0].error);
  } else {
    console.log('Success. res:', res.results);
  }
}).catch((err) => {
  console.log('Error: ', err);
});

and here's the output from XCode terminal:
2023-02-16 11:33:15.721245+0800 Firebase Cloud Messaging Example[24617:3824593] received notification called: {
    aps =     {
        "content-available" = 1;
        "mutable-content" = 1;
    };
    body = "this is body";
    "gcm.message_id" =<PHONE_NUMBER>300932;
    "google.c.fid" = "c56vCMjH7Eklmw-0ke-Cwj";
    "google.c.sender.id" =<PHONE_NUMBER>514;
    notificationType = chat;
    title = "this is great title";
}

@adhityapaf please remove the didReceiveRemoteNotification handler in your app delegate, we're trying to debug the firebase_messaging plugin. Did you follow what I said and put a break point in Xcode and run app from Xcode?

@adhityapaf
Regarding the console output on the Xcode terminal -> where is this getting printed from? Is this within the app?

Before I delete didReceiveRemoteNotification, I already put a breakpoint but it does not pause the app. After I deleted it, it works. Here's the terminal output:
(lldb) po notificationDict
{
    contentAvailable = 1;
    data =     {
        foo = bar;
    };
    messageId =<PHONE_NUMBER>092765;
    notification =     {
        apple =         {
        };
        body = "Great content";
        title = "A great title";
    };
}

2023-02-17 10:49:27.577244+0800 Firebase Cloud Messaging Example[28842:4252832] flutter: background called!
2023-02-17 10:49:27.579695+0800 Firebase Cloud Messaging Example[28842:4252832] flutter: Handling a background message<PHONE_NUMBER>092765
2023-02-17 10:49:27.624896+0800 Firebase Cloud Messaging Example[28842:4252832] flutter: A new onMessage event was published!

Thank you @russellwheatley :pray:
@aashishpatil-g , It is from the didReceiveRemoteNotification function in AppDelegate.m (https://github.com/firebase/flutterfire/issues/10082#issuecomment-1432445218)

Apologies for the spam but I checked with the app being in the background and the following snipped added in AppDelegate.swift and it prints the notification content no matter if the app is In the background or foreground, but the backgroundHandler doesn't get ran:

@adhityapaf Do you mind sharing some code/what works for you?

Hi @thilojaeggi, I just removed the fetchCompletionHandler that I use to debug the notification handler in AppDelegate.m and it works as it should. To make sure it works or not, you can try to run the project in Xcode and add a breakpoint here. When debugger hits the breakpoint, you can run po notificationDict command in Xcode terminal to show the notification payload just like in my previous comment and continue the debugger to show if Flutter receive background message or not. Hope it helps 😄

Ok, I understand you left the function override for "didReceiveRemoteNotification" though?

Ok, so the breakpoint was reached when restarting the app from the background which kind of goes against the principle of background notifications?

Just found out how to fix it by adding FirebaseAppDelegateProxyEnabled: NO, to my Info.plist and FirebaseApp.configure()
in AppDelegate.swift


hover on disney card

What is the change?
When you hover on the Disney card it pops out and looks like a Disney plus website
Related issue?
closes: #135
How was it tested?
In chrome
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelineswhile contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Have you tested the code before submission?
[x] Have you formatted your code ? (You can use any html,css beautifier)
[x] My changes generates no new warnings.
[x] I'm Diversion contributor.
[x] I have commented my code, particularly in hard-to-understand areas.

GIF/video of the working of component you created:
https://user-images.githubusercontent.com/55155180/161413283-592258d1-6f3d-498e-ab8d-899906314cba.mp4

I can see only 1 file. Please follow the guidelines!


Identifiers validation failed for dataset Actualización e incremento del banco de datos de la colección de herbario del Jardín Etnobotánico de Oaxaca

Identifier validation failed for the dataset Actualización e incremento del banco de datos de la colección de herbario del Jardín Etnobotánico de Oaxaca:

Crawler attempt: 266
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 1592
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 73%, total records count 2189, absent records count 1592
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3073600/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Actualización e incremento del banco de datos de la colección de herbario del Jardín Etnobotánico de Oaxaca : https://doi.org/10.15468/jbeu2v.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Actualización e incremento del banco de datos de la colección de herbario del Jardín Etnobotánico de Oaxaca:

Crawler attempt: 269
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 1592
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 2189, absent records count 2189
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3094401/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Actualización e incremento del banco de datos de la colección de herbario del Jardín Etnobotánico de Oaxaca : https://doi.org/10.15468/jbeu2v.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


Provide deb/rpm and other packages for Gitea

Feature Description
I am aware that this was filed early on in issue #31, but it seems to still be an issue.
There is a trend among some large project developers currently to erroneously believe that using container images or 3rd party packages (or even distributing precompiled binaries unpackaged!) is somehow a sane or appropriate workaround for compiling rpm or deb, which is easy, or negotiating a package pipeline with an interfacing os distribution.
In truth it reintroduces solved problems to the user's systems and promotes generally unsafe practices (one of which is installing software by means other than the system package manager in a professional environment).  I realize that corporate contributors to major distros are curently advocating distribution models that rely on 3rd party package managers like snap, flatpak, appimage etc, or containers, or nothing at all, and these people are, in almost every case, incorrect for widely consumed projects that care about the maintenance of their product and those "worst practice" advocates' motives should be called into question.
Packaging is part of the SDLC.  Distributing container images is not a workaround for distributing packages (images are good to distribute but should also rely on packages to facilitate the package's lifecycle -- install, update, remove -- it still starts with a package).    Please don't make the mistake of thinking that containerization is a panacea as it is an architecture with specific use cases that this project really doesn't fit.
To not use native system packages is a regression, not an advancement, as neither 3rd party package managers nor container images can effectively manage system dependency trees or flexibly fit into all use cases for system administration, the most of obvious of which is that 3rd party package managers almost categorically do not interface with the default system package manager's database, which is almost gauranteed to create conflicts without careful tending.  Some popular 3rd party package managers actually harm the systems they are installed on.
This used to be well understood but a few poorly behaving corporate projects have stained the culture a bit while creating bad precedents that are frequently cited in recent years due to the corporate promotion of developers who are highly skilled at creating software but have never had to learn systems administration to any depth due to the OS layer generally being handled by another team, and the only way I know how to address it is occasionally filing notices like this on projects I enjoy using and would like to see managed on the target systems better.
To people that did not drink that koolaid, distribution of non-packaged pre-compiled artifacts has the smell of using a gmail account for a company email inbox.
That said, thank you for listening to my rant, I hope you listen, and thank you very much for creating and maintaining a wonderful product, I see a great deal of potential with Gitea and I think alot of other people see that potential as well.  I would also like to say that I'd be receptive to details on where I can donate to this project.
Screenshots
No response

Providing packages have been discussed before and I would not mind for us building them automatically but we need a way to easily integrate the process into our drone pipeline.
Donations can be made on https://opencollective.com/gitea

Since Gitea is totally an open source and free project, the development of Gitea is mostly done by volunteers.
If a volunteer has the motivation and the ability to implement a feature, then the feature may come. Otherwise, there are many good proposals are pending because no volunteer has time to implement them.

For the record, there is a effort already to package gitea in Debian:
https://wiki.debian.org/Gitea
And there is a up to date Copr package for Fedora:
https://copr.fedorainfracloud.org/coprs/elxreno/gitea/
And one for Opensuse:
https://build.opensuse.org/package/show/devel:tools:scm/gitea
I am sure there is lots of others groups doing the packaging work, so maybe it would be better to join them.
Debian for example is waiting on some js dependencies to be packaged so gitea can move to main.

Hey that's great news.  So what about incorporating these as official distribution channels in documentation?

It might be a good idea to use goreleaser to be able to automatically create packages based on release tags (or snapshots).
We are using goreleaser to build rpm and deb packages and it is as easy as adding a single .goreleaser.yml file in the repo.
Can be used for CI/CD too a few lines of code.
If this is of interest I can work on a pull request to add this.

It might be a good idea to use goreleaser to be able to automatically create packages based on release tags (or snapshots).

The concept of having packages generated and added to package repositories on the end of a CI/CD pipeline is a good idea, but there are some caveats:

Want to avoid treating "RPMs as RPMs":  For example, an RPM for Fedora is not interchangeable with an RPM from OpenSUSE or CentOS or derivatives of either.  This goes for Debian vs. Ubuntu for DEBs etc.

The build environment must emulate the target environment for dependency tree alignment in mass distribution.  For RPMs a best practice for building RPMs for mass distribution is to use a system like Mock to...well, "mock" the target environment.  It covers most popular RPM-based distributions.  I believe pbuilder is the DEB equivalent.  This is a critical piece of the build environment for quality assurance.  Alot of CI systems are built without this understanding baked into package generation features and generate a "local system compatible" package instead, which leads to frequent packaging issues .  I'm unsure as to whether goreleaser has that awareness or not.  What I've seen work well is a jenkins system for each target that watches the repo and in the case of an RPM,  will build with a spec file and the source code to an SRPM file, which can be consumed by community package mantainers for mainstreaming the package in the OS-default repos, but a self-hosted repo works too as the right CI tools can generate the RPM (mock!).  After package generation the CI system would need to place the rpm in a repo and update repo metadata if they opt to have "official package repositories".

A decision would need to be made by the Gitea project on whether they want to:
A. Host the packages on their own "official gitea" repos.  It's simple, it's easy to do, and saves alot of work.  Alot of projects use a COPR and equivelant to do this.  This has the great benefit of allowing all related products by the same project (as they come up) to be accessible after installing the "Official Gitea Repos".  It would require at minimum VirtualHost directives to host the repositories, though, it probably should get its own dedicated host as a packages repository.
B. Integrate into the target distributions' base repos or extended repos (such as EPEL or RPMFusion).  This would likely require package maintainers to maintain but provides much easier access by users of those distributions, and would be expected to increase popularity of the product a great deal.  To clarify this requires at least one person maintaining the packages for one or more distributions.
C. Jam the packages on a file download directory like savages.  Don't do this. It's always an option but it's a bad option and could attract time travelers showing up occasionally to try to stop you with matrix-esque kung fu moves and slow motion camera sweeps.  Agent Smith wants you to do this.  Don't do this.

Whatever decision is made in (3) needs appropriate infrastructure considerations and process, like repo hosting if they go with (A), or maintainers if someone volunteers for (B).

If a decision can be formalized around it, it should be integrated into the documentation.

I'm looking to migrate from Gitlab -> Gitea. Having RPMs would be super helpful in my case, especially for patching and keeping up-to-date with security.
@lafriks You mentioned donations. What would the donation amount need to be to get this feature implemented?


How do I stop my bot without repeating the last message, next time I start it up?

How can I stop this bot and flush/acknowledge the last message received, without having it repeated next time when I start the bot?
For instance it receive a "/quit" command and it run an exit(true) in my code. Next time when I start my bot it will stop right away as the last message/command is repeating...

Hi @protektwar, sounds interesting. I didn't mention that messages get duplicated after stop/start or restart though I didn't do it intentionally.
I think it is all about offset option in Client. It is getting updated before yielding message to a block specified.
I guess you can try to pass initial offset on Client initialization. You could store offset somehow while handling /quit command before exiting application.

  def saveLastMsgID(id)
    File.open(@lastMsgID_filename, "wb") { |file|
      file.write(id)
    }
  end

  def loadLastMsgID
    File.open(@lastMsgID_filename){ |file|
    @lastMsgID = file.gets
    }
  end

and inside bot.listen block
 bot.listen do |message|
        if ( bot.options[:offset].to_s == @lastMsgID.to_s )
         break
       end
 end

It is not what I meant but it is up to you. If the problem is solved please close the issue.