text:
Use docker .env file

Юзаем env_file в докер компосе, чтобы не дублировать параметры настроек, сейчас все кучей навалены в environment отдельно для каждого сервиса
Автор: Артемий

connected with PR https://github.com/fidals/shopelectro/pull/280

already done and payed for astro hours

repo: fidals/refarm-site


text:
Take view full-screen into account

One use-case I see missing from the summary so far is the use case of a video being played within the layout of a webpage - perhaps only taking up 1/4 of the available screen - and the user the clicking to go full-screen (at some point before or during play). I would like to see a way to initially present a small video file and then fetch the large version when the user requests full screen.
Loading a 1080p or 4k video in case the user wants to go full screen is not a good experience for a mobile user or someone on a small laptop screen, or just someone who doens't want to bother leaving the webpage context.
I don't think this changes any scope or attributes proposed thus far, just an implementation use-case for the browser.

It's actually a rather complicated case, as are all resize > change media situations while playing or having loaded media. This is only really solved by DASH or HLS and authoring the media according to the specifications. I haven't looked up the discussions from when the W3C changed the  spec but I wouldn't be surprised if these cases were the primary reason to abandon sizes support.

It's actually a rather complicated case, as are all resize > change media situations while playing or having loaded media. This is only really solved by DASH or HLS and authoring the media according to the specifications. I haven't looked up the discussions from when the W3C changed the  spec but I wouldn't be surprised if these cases were the primary reason to abandon sizes support.

@phillipseamore Is there a difference between the <video> element resizing within the page and the video going fullscreen?
With the caveat that I don't know what I don't know and therefore it's much more complicated than I envision, is it not straight foward to capture the timestamp at the event to go fullscreen and start the larger video size at that spot?

@phillipseamore Is there a difference between the <video> element resizing within the page and the video going fullscreen?
With the caveat that I don't know what I don't know and therefore it's much more complicated than I envision, is it not straight foward to capture the timestamp at the event to go fullscreen and start the larger video size at that spot?

No there isn't any difference between changing sources based on resizing the window or going fullscreen. The issue is how to handle flushing the media that is already in the buffer, retrieving new media (higher or lower res file), seeking to right frame and audio sample and starting playback again. If the media isn't all authored correctly changing between files might completely stall. How the media is served would be an issue also (e.g. if the server doesn't support byte-range requests the whole file would be retrieved etc). There are a tonne of technical and UX issues.  This is all solved with HLS and DASH and authoring the media files according to those specs. None of this is an issue if the media hasn't been loaded and isn't playing - but that would be uncommon.

No there isn't any difference between changing sources based on resizing the window or going fullscreen. The issue is how to handle flushing the media that is already in the buffer, retrieving new media (higher or lower res file), seeking to right frame and audio sample and starting playback again. If the media isn't all authored correctly changing between files might completely stall. How the media is served would be an issue also (e.g. if the server doesn't support byte-range requests the whole file would be retrieved etc). There are a tonne of technical and UX issues.  This is all solved with HLS and DASH and authoring the media files according to those specs. None of this is an issue if the media hasn't been loaded and isn't playing - but that would be uncommon.

source: gharchive/issue

authors: philiprenich phillipseamore

repo: filamentgroup/html-video-responsive

license: MIT

license_type: permissive

license_source: github-api


text:
Please Help me out with this last question, I want to display my table record based on a condition, apart of using filter, i can't find it in the documentation. For example, i want to display employee records where status = 1, i don't want to use filter, and tab to do that, how can i achieved it?

Please Help me out with this I want to display my table record based on a condition, apart of using filter, i can't find it in the documentation. For example, i want to display employee records where status = 1, i don't want to use filter, and tab to do that, how can i achieved it?
Originally posted by @aldids01 in https://github.com/filamentphp/filament/discussions/13673#discussioncomment-10147663

Donate 💰 to fund this issue

You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
100% of the funding will be distributed between the Filament core team to run all aspects of the project.
Thank you in advance for helping us make maintenance sustainable!

You could modifiy the table base query.
    public static function table(Table $table): Table
    {
        return $table
            ->modifyQueryUsing(fn ($query) => $query->where('status', 1))

Please do not open bug reports for questions that already exist in Discussions. Again and we will block you from posting on the repo.

Please do not open bug reports for questions that already exist in Discussions. Again and we will block you from posting on the repo.

Okay Sir

authors: Jonas-johansen aldids01 danharrin

repo: filamentphp/filament


text:
Add CSS classes to sidebar based on label

Description
I was looking for a way to apply some custom CSS to a certain item in the navigation to make it stand out more (an onboarding page). I noticed there wasn't really a good way to target a specific navigation item using CSS classes.
This PR automatically sluggifies the navigation item label and adds that as a class. It will generate classes like this:
fi-sidebar-item-onboarding
fi-sidebar-item-tasks
...

Thanks!

I don't think we should merge this. The classes would then be changing based on the current locale, in translated apps.

That's true indeed, would you be open to adding an extraAttributes() method?

Sure

source: gharchive/pull-request

authors: danharrin ralphjsmit


text:
CronJob to periodically list objects in S3

Useful for debugging the s3 object expiration, the job runs every 15
minutes and you can see the list of objects in the pod's log.

@avishayt  whouldn't it be better to have a tool to do that?

maybe a single shot job?

I guess I could wrap it in a bash script that takes environment variables, writes the yaml to /tmp, and then applies it. Seems like a bit of overkill. Also one-shot job isn't very helpful I think. Basically I wanted to monitor which objects were in S3 over time so that I could see how the GC was working, so getting the list of objects every 15 minutes was what I needed, not just once.

You can wrap with a python script.
As long as it's for debug and we don't need it as part of a full deployment i think it's fine.

authors: avishayt filanov ronniel1

repo: filanov/bm-inventory


text:
Remove all logging information during test runs and/or devstack

ETA: 2022Q4
When running locally, the logs are virtually unusable. Just a wall of meaningless text. Need to improve.
Further, we do a lot of OpenTelemetry stuff - we should detect and turn that off (with no errors) when running DevStack.

I don't find the logging too hard to interpret, can you give some specific examples of things that we should change please?

@aronchick What would improve this for you? The logging seems to be useful in debugging situations, but I agree there is a lot of it. Would you prefer logs to only be shown if tests fail?

I'm closing this as I don't think we've reached a consensus on whether a change is required. Please re-open with more details if necessary!

authors: aronchick lukemarsden simonwo

repo: filecoin-project/bacalhau


text:
i have a problem!!

;C

Hi,
Set the php error reporting to default value so it doesn't scream like that, see:
https://www.php.net/manual/en/function.error-reporting.php
https://www.php.net/manual/en/errorfunc.configuration.php#ini.error-reporting
Or just add this line to the top of your index.php file:
<?php

// Turn off all error reporting
error_reporting(0);

repo: filegator/filegator


text:
bug: Trying to open properties from blank area of a folder doesn't open window

Description
Read steps to reproduce for a clearer understanding.
Side note when right clicking a folder and opening properties it will open two windows of the same folder just clicked on.
Steps To Reproduce

Go to a folder
Right click empty space
Click properties
See window doesn't open

Steps to fix
?
Files Version
2.3.51.0
Windows Version
10.0.22621.675
Relevant Assets/Logs
Haven't been generated.

@yaichenbaum I identified the line of code to fix for this bug. However, it would be nice if the Show Properties command in the context menu corresponded to that in the action bar. It should be possible to open the properties from the quick actions when no element is selected. Is this the expected behavior?

Not currently but I don't see why it shouldn't be supported.

authors: Josh-65 cinqmilleans yaichenbaum

repo: files-community/Files


text:
Working With Images

Description
Most of the time when I'm using Files, it crashes when I'm working with images.
Steps To Reproduce

Open any folder with multiple images.

Requirements

e.g. Fix crash that occurs when...
You load a folder that has more images than can be displayed on screen without scrolling. I have one panel open and the display properties panel.

Files Version
2.5.1.0
Windows Version
10.0.22621.1848
Log File
debug.log

Thanks for the report.

Yes, and since I posted the report I have viewed a folder with as few as 6 images (but all fairly large files, 7MB>) so maybe that's a part of it. I'd be more than happy to submit more information if needed. Just let me know if I can help. Files is awesome.


text:
Bug: Toolbar extract text not shown correctly with a small window width

Description
The extract option is labled "E" when you resize your window down and the menu bar is reduced in size causing the "..." button to appear

Steps To Reproduce

Resize window down that the menu bar has a "..." option
Select a zip folder
Click the "..."

Notice extract is labled "E"
Requirements
Fix Extract label on context menu
Files Version
3.5.0.0
Windows Version
1000.22700.1020.0
Log File
debug.log

Thanks for the report, I've added this to the project board.

Isnt this the same as https://github.com/files-community/Files/issues/10291?

Yes, we can continue tracking there.


text:
Preview pane doesnt keep size if navigated to different folder

Describe the bug
If you adjusted the size of the preview pane and navigate to a different folder or close and open it, the size resets to default.
To Reproduce
Steps to reproduce the behavior:

Enable preview pane
Resize preview pane
Navigate to different folder or close and open preview pane
Preview pane has default size again

Expected behavior
Preview Pane keeping same size after navigating to different folder or closing and opening preview pane.
Screenshots
Before:

After reopening or navigating to different folder:

Desktop (please complete the following information):

OS Version: Windows 10 19042
App version: 1.2.0.0

Additional context
Also happens when you restart
Log file
This doesnt really make sense as it doesnt crash but here you go anyway
debug.txt
debug_fulltrust.txt

This bug was fixed with #3349#3282

authors: benschlegel winston-de


text:
creating new folders & files doesn't work

Explain the bug
creating folders & files doesn't work
To reproduce

right-click -> new -> folder
type a name
click set name
folder won't be created

Expected behavior
a folder with the name I choose should be created
Logfile
debug_fulltrust.log
debug.log
Screenshots
https://user-images.githubusercontent.com/37732484/127262505-96ed9fd9-293f-4a6f-aa1f-ae67d1cfc61d.mp4
System Information

OS Version: Windows 11 21H2 22000.100
App version: 1.9.15.0

Additional comment
this problem happens again after restarting the app
& creating folders from windows explorer works fine so it's not the drive's fault

This issue should be resolved in main.

This issue should be resolved in main.


text:
Drag and drop gets stuck until transfer is finished

Description
When i drag a file from desktop to my SMB server it got stuck until the transfer is finished.

Steps To Reproduce
drag a file into a network drive
Expected behavior
drag icon not stuck
Files Version
2.0.13.0
Windows Version
Edition	Windows 11 Pro Version	21H2 Installed on	06/10/2021 OS build	22000.194 Experience	Windows Feature Experience Pack 1000.22000.194.0
Relevant Assets
No response

Is this still an issue in the preview build? https://files.community/download/preview

authors: ivanjx yaichenbaum


text:
File in use dialog should show the file name and extention

What's the Problem?
Currently it just says "The file" which isnt helpful
Solution/Idea

Alternatives

Priorities
No response
Files Version
No response
Windows Version
No response
Comments
No response

Something like this maybe?

looks good

This issue should be resolved with #8925


text:
Files creating empty zip files unprompted

Description
I have a bunch of torrents from a private tracker with the names:
{EHT PERSONALIZED TORRENT - DO NOT REDISTRIBUTE} [x] x [x].zip.torrent
Replace x with the actual name/info of the individual torrent.
Files(the program) creates an empty zip file with the same name as the torrent minus the .torrent for every one of these torrents that is VIEWED in the program. Just viewed. Imagine my surprise when I open my downloads folder and a bunch of zip files start spawning.
Steps To Reproduce
No response
Expected behavior
Expected behavior is that it doesn't do this.
Files Version
Version: 2.1.24.0 OS Version: 10.0.22000.493
Windows Version
Windows 11 21H2 22000.493
Relevant Assets/Logs
debug_fulltrust.log
debug.log

This issue should be resolved with #9273

authors: octopushugger yaichenbaum


text:
Fix: Fixed layout doesn't update on open tabs when the default layout changes

Resolved / Related Issues

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #14580

Notes
The if at line 432 is not easily readable. Should I add a comment/split it, or is it fine?
Validation
How did you test these changes?

[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[x] Did you implement any design changes to an existing feature?

[x] Was this change approved?

[x] Are there any other steps that were used to validate these changes?

Make sure Files settings > Folders > Sync layout and sorting preferences across directories is enabled
Open two tab
Change the layout in one tab
Switch to the other

Does this also work if the default layout is changed in Settings?

The if at line 432 is not easily readable. Should I add a comment/split it, or is it fine?

Can you split it?

Does this also work if the default layout is changed in Settings?

Not yet but I'll work on that and on dual pane mode


text:
NavBar improvements step 1

Moved the navigation buttons to the left of the path bar
Fixed spacing of the toolbar buttons

Could you share a screenshot?

@d2dyno1 This PR is part of a larger effort to redesign the navbar area, but this is what it looks like so far.

LGTM (actually it looks horrible but it's part of the plan right? 🤣)

LGTM (actually it looks horrible but it's part of the plan right? )

tbh I like this one more

LGTM (actually it looks horrible but it's part of the plan right? 🤣)

Exactly 😆

LGTM (actually it looks horrible but it's part of the plan right? rofl)

Exactly

Hmm. How will the final version of this redesign look alike?

@d2dyno1 There are several parts to this design change including #3184, there are also plans to add some shadows around the app. It's hard to describe how it will look, but this concept should give you the basic idea.

Ooof every time I see one of this mockups I cry for the lost sidebar extending all the way to the top 😂. Aware of the reason behind the change my gut says otherwise.

@gave92 What don't you like about the sidebar extending to top?

I meant I don't like too much the current design where the sidebar is not extented to the top. When the sidebar is made acrylic I miss the "old" design.

@gave92 Oh good, then I am sure you will like the new design when #3184 is merged 😄

I see that little progress circle in the bottom right. Will this replace this progress bar which indicates that the folder is being loaded? I'd appreciate that.

@R3voA3 The progress circle is just a concept, don't read much into it.

@R3voA3 The progress ring is just a concept, there isn't anything planned to change there.

Too bad =(

@d2dyno1 There are several parts to this design change including #3184, there are also plans to add some shadows around the app. It's hard to describe how it will look, but this concept should give you the basic idea.

That has... everything I wanted 😲Even the W10X quick actions below the navbar

@yaichenbaum one thing I noticed is that with the navigation buttons on the same row as the address bar on my screen the address bar becomes very cramped(in dual pane even more so and almost unusable). Just saying that this change would adapt with the window width.

@gave92 It's something to look into, I am curious if this is really an issue or not because the dual screen feature is mainly used on larger screens. Regardless, I plan on reducing the size of the text in the nav bar, so that should help with this issue.

Thanks, it's simply that currently I can use the dual pane feature with no issue, but with this change it gets a little awkward. Thinking that the search button and the others are going to also be moved into the same row.. :)

@gave92 The only other button that's going to be moved is the search button, it's something we should start discussing to find possible solutions. Thank you for bringing it up.

Wondering if you have considered adding the title of the app (and logo) to the top left of the NavBar. Probably good from a branding point of view, but also would be consistent with a lot of the other 'modern' apps. At the moment it sort of looks like the app is called 'favourites'. :) Screenshot below for example.

Not really sure where the title and logo would fit since the Tabs are taking the space and soon the nav bar.
Also, they should not try to be consistent with Microsoft apps since that's impossible :D

The Win32 Explorer doesn't use a logo or a title anyway, so as it is now Files is consistent with the legacy file browser

@yaichenbaum Any chance to see a screenshot? I need to see where
          <target state="new">Browse</target>         </trans-unit>         <trans-unit id="RecentLocations" translate="yes" xml:space="preserve">           <source>Recent locations</source>           <target state="new">Recent locations</target>
Is used so I can properly translate it.

Here is two good examples I think. Adding a title to the top of the navbar doesn't get in the way of tabs, or the navbar items.

Also here: https://www.behance.net/gallery/74300939/Windows-10-File-Explorer

@R3voA3

Wondering if you have considered adding the title of the app (and logo) to the top left of the NavBar. Probably good from a branding point of view, but also would be consistent with a lot of the other 'modern' apps. At the moment it sort of looks like the app is called 'favourites'. :) Screenshot below for example.

Thanks for bringing this up, it seems like Microsoft is moving back towards this trend, but as mentioned above, it wouldn't fit into our design right now.


text:
Small typo fix

Changed bellow (to yell loudly) to below (underneath). ;)

Thanks @hughfdjackson!

authors: hughfdjackson vkostyukov

license_source: bigquery


text:
Update circe-fs2 to 0.13.0

Updates io.circe:circe-fs2 from 0.13.0-M1 to 0.13.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe", artifactId = "circe-fs2" } ]

labels: library-update, semver-pre-release

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@195fc1a). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1208   +/-   ##
=========================================
  Coverage          ?   81.16%
=========================================
  Files             ?       55
  Lines             ?     1009
  Branches          ?       42
=========================================
  Hits              ?      819
  Misses            ?      190
  Partials          ?        0

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 195fc1a...9d19cee. Read the comment docs.

authors: codecov-io scala-steward

repo: finagle/finch


text:
Added methods for detecting changed fields in domain layer

Will need tests before merge... wanted to clarify structure first.  See issue #52 by @dhoechst

Thanks for this, a few comments and hopefully some food for thought...

Wondering if these can be made instance methods then you can leverage Records property.
I also think the methods should be bulkified like other methods on this class, take a list of old records.
I know QueryFactory has a lot of overloads for String vs SObjectField usage, but i'm less sure here, for example Selector doesn't offer this and i feel the domain layer is more concrete in nature.
Can we validate these with @dhoechst use cases perhaps?

Hmm. So could you we have an instance method with a signature something like this? That might be pretty cool as then if you want to work with records that have changed, just make a call to this method. No need to loop through the records.
public List<SObject> getChangeRecords(Set<Schema.SObjectField> fieldTokens)

Like! :+1:
@MayTheSForceBeWithYou thoughts?

@afawcett @dhoechst I'm on it!

Excellent thanks. I'd let it throw the runtime exception, its a developer error / bug and should be caught in testing asap.

@MayTheSForceBeWithYou I'm happy to add these, your PR looks to be in conflict currently though?

@MayTheSForceBeWithYou let me know if you still plan to work on this?

I will finish it up!  I miss fflib so much. :-(
#SOQLinControllers
On Sat, Feb 18, 2017 at 11:26 AM Andrew Fawcett notifications@github.com
wrote:

@MayTheSForceBeWithYou https://github.com/MayTheSForceBeWithYou let me
know if you still plan to work on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/financialforcedev/fflib-apex-common/pull/87#issuecomment-280868883,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA5kc9z0vjcEiQUADjW5lZ2oDs4FzcStks5rd0YCgaJpZM4GF8x2
.

--
May The SForce Be With You!
Nathan Pepper, Salesforce Developer
MayTheSForceBeWithYou@gmail.com
www.youtube.com/MayTheSForceBWithYou
Twitter: @SForceBeWithYou

@dhoechst @afawcett How should this perform on insert, delete, and undelete?
Since this will be an instance method that cycles through this.Records, should I access Trigger.oldMap directly and ignore records that (for some reason) wouldn't be in oldMap?
https://github.com/financialforcedev/fflib-apex-common/pull/87/files

I would make the methods agnostic of being in a trigger context. In cases where the old map is available it is passed to the outer method e.g onValidate. So the developer can pass this onto your helper methods. It feels a bit onerous to do this i know, but its clearer whats going on and makes for some flexibility. What do you think?

Is this still being worked on/looked into?  I am currently trying to implement something that this would be a help with.

@MayTheSForceBeWithYou any updates?

@ejwill I would love a code use case... not justification, just, "Here's how I'd want to use it in code".
I've implemented most of the functionality, just really lacking code for a use case, and then I'll finish the unit tests. @afawcett It's been ages since I rolled up my sleeves using the domain layer :-(

Has this effort fizzled out?  Would be great functionality but just adding a method to my own SObject_Domain for now.

Hey @dfruddffdc , how can I get the authenitcation failure resolved for the TravisCI job?

@MayTheSForceBeWithYou just ignore that its a known issue with PR's and Travis integration. Meanwhile this looks like a good utility feature addition to the class to me. cc @stephenwillcock @agarciaodeian

Excellent contribution!

authors: MayTheSForceBeWithYou afawcett broughtonsoftware dhoechst ejwill resample-admin

repo: financialforcedev/fflib-apex-common


text:
Add a setting to not launch the keyboard when opening the app drawer

I just started using this launcher and love it the only thing I have an issue with is that the keyboard opens up with the app drawer. While I'm sure this is intended behavior could you add a setting that allows you to disable that behavior.

It indeed was intended functionality as I disliked having to click the search bar all the time...
You'll see that it is disabled in the "choose app" app drawer / dialog.
Smart idea though, we'll do that!
I feel like this can be implemented by adding another switch to the Launcher tab of settings.
Don't worry, I'll get to it, likely on the weekend - I am just very busy studying physics during the week : )

repo: finnmglas/Launcher


text:
Fix/fast appmenu

Closes #7
Finally!

I made the menus faster
Improved the layout

From now on I will squash commits in order to keep it easier understandable. I made too many single commits lately...


text:
Feedback

Hey again!
Thanks for taking the first step of implementing a vim colorscheme!
I came with feedback..

I normally use a modified version of spaceduck and
Let me know if you want me to provide any more information! Or I can also stop being lazy and contribute... but that's gotta wait until weekend I think.

Please provide more information. Is the issue the tab background color?

Ah sorry for the late return, I missed this one.
I think the issue is the whole thing, the first image is nothing close to the actual colors that i see on search-lights. I linked the spaceduck as an example since while it includes things like common plugin colors that you might not know, it also correctly represents the intended colors. I figured maybe you are doing something wrong? I'm just trying to help sorry.
I can also modify something like spaceduck myself with your colors and publish it myself, or I don't know actually learn how theming works on vim and do it. but I figured you wouldn't be okay with that?

Ahhhh I get what you're saying. That's actually a pretty big issue to solve because vscode and vim do not use the same tokenization scheme. I just used an existing vim theme template and moved the colors over. It would be super helpful if you would submit a pull request making the token colors match a little closer to the original vscode theme! I will see what I can do to fix this but I am not sure when I will get the chance.

authors: finnsjames qualious


text:
GitHub Action - Meetings - Not Working

Bug Report
Steps to Reproduce:

https://github.com/finos/architecture-as-code/actions/workflows/meetings.yml
Look at job history - I can't find an instance of it actually passing.

Expected Result:
From reading the GH action this is meant to actually capture who is attending the meetings and send this information to FINOS for their metrics.
Actual Result:
It appears to fail when checking out the metrics from Finos.
@karlmoll - is this something that we should have working ASAP? Do we have any capability to manually upload these metrics to FINOS in the interim?

@TheJuanAndOnly99 @maoo ^^

Hi @Thels @karlmoll this action is deprecated and can be removed. We moved from a push to a pull approach. The meeting information is being processed and published on GitLab.

Fantastic - I'll remove the action as a part of this issue and then will close it out.

authors: TheJuanAndOnly99 Thels karlmoll

repo: finos/architecture-as-code


text:
Benchmark compiler

Sample code to benchmark the compiler, and compare performance base on parallelism and PMCD size.
For the PMCD, the benchmark duplicates a sample PMCD.  The assumption is that an average PMCD have similar distribution of elements as it gets bigger.  There are scenarios this does not account or cover, and all this try to show that under some use cases, the parallelism will have a positive effect on the compiler.
Benchmark Results

-1 is for the code before the refactoring.  Given the number of synchronize blocks added, the performance impact is noticeable.  We need to reduce these contention points.

Raw Data

(parallelism)
log(parallelism, 2)
(pmcdCount)
log(pmcdCount, 2)
Mode
Cnt
Score

Error
Units

-1
-1
1
0
avgt
25
0.202
±
0.066
s/op

-1
-1
2
1
avgt
25
0.2
±
0.016
s/op

-1
-1
4
2
avgt
25
0.214
±
0.002
s/op

-1
-1
8
3
avgt
25
0.251
±
0.002
s/op

-1
-1
16
4
avgt
25
0.385
±
0.098
s/op

-1
-1
32
5
avgt
25
0.466
±
0.022
s/op

-1
-1
64
6
avgt
25
0.773
±
0.017
s/op

-1
-1
128
7
avgt
25
1.356
±
0.011
s/op

1
0
1
0
avgt
10
0.517
±
0.023
s/op

1
0
2
1
avgt
10
0.765
±
0.064
s/op

1
0
4
2
avgt
10
0.855
±
0.006
s/op

1
0
8
3
avgt
10
1.093
±
0.006
s/op

1
0
16
4
avgt
10
1.533
±
0.014
s/op

1
0
32
5
avgt
10
2.449
±
0.148
s/op

1
0
64
6
avgt
10
4.147
±
0.028
s/op

1
0
128
7
avgt
10
7.605
±
0.054
s/op

2
1
1
0
avgt
10
0.529
±
0.031
s/op

2
1
2
1
avgt
10
0.523
±
0.009
s/op

2
1
4
2
avgt
10
0.71
±
0.006
s/op

2
1
8
3
avgt
10
0.913
±
0.015
s/op

2
1
16
4
avgt
10
1.223
±
0.051
s/op

2
1
32
5
avgt
10
2.083
±
0.109
s/op

2
1
64
6
avgt
10
3.78
±
0.065
s/op

2
1
128
7
avgt
10
7.207
±
0.097
s/op

4
2
1
0
avgt
10
0.506
±
0.005
s/op

4
2
2
1
avgt
10
0.573
±
0.034
s/op

4
2
4
2
avgt
10
0.541
±
0.004
s/op

4
2
8
3
avgt
10
0.744
±
0.005
s/op

4
2
16
4
avgt
10
1.126
±
0.05
s/op

4
2
32
5
avgt
10
1.793
±
0.116
s/op

4
2
64
6
avgt
10
3.451
±
0.401
s/op

4
2
128
7
avgt
10
6.441
±
0.713
s/op

8
3
1
0
avgt
10
0.514
±
0.005
s/op

8
3
2
1
avgt
10
0.542
±
0.028
s/op

8
3
4
2
avgt
10
0.541
±
0.004
s/op

8
3
8
3
avgt
10
0.717
±
0.034
s/op

8
3
16
4
avgt
10
1.008
±
0.019
s/op

8
3
32
5
avgt
10
1.585
±
0.079
s/op

8
3
64
6
avgt
10
2.919
±
0.07
s/op

8
3
128
7
avgt
10
5.586
±
0.221
s/op

16
4
1
0
avgt
10
0.535
±
0.034
s/op

16
4
2
1
avgt
10
0.543
±
0.006
s/op

16
4
4
2
avgt
10
0.556
±
0.027
s/op

16
4
8
3
avgt
10
0.619
±
0.005
s/op

16
4
16
4
avgt
10
0.863
±
0.037
s/op

16
4
32
5
avgt
10
1.306
±
0.038
s/op

16
4
64
6
avgt
10
2.237
±
0.1
s/op

16
4
128
7
avgt
10
4.267
±
0.115
s/op

32
5
1
0
avgt
10
0.518
±
0.019
s/op

32
5
2
1
avgt
10
0.519
±
0.009
s/op

32
5
4
2
avgt
10
0.546
±
0.008
s/op

32
5
8
3
avgt
10
0.622
±
0.005
s/op

32
5
16
4
avgt
10
0.752
±
0.011
s/op

32
5
32
5
avgt
10
1.196
±
0.077
s/op

32
5
64
6
avgt
10
1.963
±
0.105
s/op

32
5
128
7
avgt
10
3.655
±
0.193
s/op

64
6
1
0
avgt
10
0.548
±
0.035
s/op

64
6
2
1
avgt
10
0.54
±
0.027
s/op

64
6
4
2
avgt
10
0.556
±
0.013
s/op

64
6
8
3
avgt
10
0.631
±
0.007
s/op

64
6
16
4
avgt
10
0.759
±
0.007
s/op

64
6
32
5
avgt
10
1.172
±
0.055
s/op

64
6
64
6
avgt
10
1.992
±
0.109
s/op

64
6
128
7
avgt
10
3.601
±
0.21
s/op

128
7
1
0
avgt
10
0.502
±
0.013
s/op

128
7
2
1
avgt
10
0.545
±
0.006
s/op

128
7
4
2
avgt
10
0.551
±
0.023
s/op

128
7
8
3
avgt
10
0.608
±
0.013
s/op

128
7
16
4
avgt
10
0.743
±
0.014
s/op

128
7
32
5
avgt
10
1.097
±
0.042
s/op

128
7
64
6
avgt
10
1.988
±
0.092
s/op

128
7
128
7
avgt
10
3.657
±
0.185
s/op

Pivot
-- | log(parallelism, 2) |   |   |   |   |   |   |   |
-- | -- | -- | -- | -- | -- | -- | -- | -- | --
log(pmcdCount, 2) | -1 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7
0 | 0.202 | 0.517 | 0.529 | 0.506 | 0.514 | 0.535 | 0.518 | 0.548 | 0.502
1 | 0.2 | 0.765 | 0.523 | 0.573 | 0.542 | 0.543 | 0.519 | 0.54 | 0.545
2 | 0.214 | 0.855 | 0.71 | 0.541 | 0.541 | 0.556 | 0.546 | 0.556 | 0.551
3 | 0.251 | 1.093 | 0.913 | 0.744 | 0.717 | 0.619 | 0.622 | 0.631 | 0.608
4 | 0.385 | 1.533 | 1.223 | 1.126 | 1.008 | 0.863 | 0.752 | 0.759 | 0.743
5 | 0.466 | 2.449 | 2.083 | 1.793 | 1.585 | 1.306 | 1.196 | 1.172 | 1.097
6 | 0.773 | 4.147 | 3.78 | 3.451 | 2.919 | 2.237 | 1.963 | 1.992 | 1.988
7 | 1.356 | 7.605 | 7.207 | 6.441 | 5.586 | 4.267 | 3.655 | 3.601 | 3.657
Graph

System Information

Laptop Legion 5 Pro 16IAH7H
12th Gen Intel(R) Core(TM) i7-12700H   2.30 GHz
32GB DDR5
64-bit operating system, x64-based processor
Windows 11 Home - 22H2

This PR is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days.

This PR was closed because it has been inactive for 35 days. Please re-open if this PR is still relevant.

authors: finos-admin rafaelbey

repo: finos/legend-engine


text:
Add warning for users changing project's group ID or artifact ID

Summary
Before, users could just directly click and edit the inputs for group id or artifact id on the project config page. Now, users must click the edit icon to edit, and if they do a caution dialog will appear to make the potential consequences of their actions clearer for them:

GIF of flow:

How did you test this change?

[ ] Test(s) added
[x] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

@xannem by the way, for the input warning, should we add an exclamation point on the right inside the input box, wdyt?

@xannem by the way, for the input warning, should we add an exclamation point on the right inside the input box, wdyt?

I feel like it might be a bit busy if there is exclamation point in input warning since we already have documentation icon that pops up to the right of the input box so then there would be two icon-like items here if that's what you meant

I could switch the question icon to use exclamation icon instead though?

@xannem by the way, for the input warning, should we add an exclamation point on the right inside the input box, wdyt?

I feel like it might be a bit busy if there is exclamation point in input warning since we already have documentation icon that pops up to the right of the input box so then there would be two icon-like items here if that's what you meant

I could switch the question icon to use exclamation icon instead though?

Yep agree, looks too cluttered

authors: akphi xannem

repo: finos/legend-studio


text:
make creation of exchange, queue & binding configurable

added default config for backwards compatibility

Good job. I will go through it and test later. Did you fully test this feature?

Yes, it has been tested. Please keep me updated if there are any issues.

Hi, any issues or change requests on your side?

Merged and released in 5.1

repo: fintech-fab/laravel-queue-rabbitmq


text:
ConnectionError for deferreds waiting for connection

Call errback with ConnectionError of deferreds waiting for connection
in ConnectionHandler's wrapper when all attempts for connecting fail.

Haven't tested this code but I'm not too sure about it. The concern is about a reconnection attempt calling errback more than once, and failing.

I thing calling errback more than once won't happen because RedisFactory.deferred is set to None after errback and is called only when there is no connection in pool. Because there is 1:1 relation between RedisFactory and ConnectionHandler (I haven't found another case) there is no other way to call factory's errback when connection fail. On the other hand deferred is put to waiting set only when factory's deferred has called == False.

Good, will let this sit for another day to see if anyone else has concerns, otherwise will merge in.

Here is example script that explain (I hope) what I expect from this patch.
#!/usr/bin/env python

import sys

from twisted.internet import defer, reactor, task
from twisted.python import log

from txredisapi import lazyConnectionPool

pool = None

def newPool():
    global pool
    pool = lazyConnectionPool('localhost', 6379, connectTimeout=1, poolsize=2)
    log.msg('New pool: %s' % pool)
    pool._factory.maxRetries = 5

def reconnectPool(res, delay):
    global pool

    log.msg('Connection failed after %s attempts: %s' % (pool._factory.retries - 1, res.getErrorMessage()))
    log.msg('Will create new pool after %s seconds' % delay)

    reactor.callLater(delay, newPool)

def doWork(batch_id):
    global pool

    @defer.inlineCallbacks
    def ping(task_id):
        try:
            yield pool.ping()
        except Exception as e:
            log.msg('Ping #%s.%s: %s %s' % (batch_id, task_id, type(e), str(e)))

    log.msg('Running doWork batch #%s' % batch_id)

    defers = []
    for i in range(10):
        d = ping(i)
        defers.append(d)

    return defer.DeferredList(defers)

@defer.inlineCallbacks
def test():
    global pool

    reconnectDelay = 10

    try:
        newPool()

        pool._connected.addErrback(reconnectPool, reconnectDelay)

        yield doWork(0)
        yield doWork(1)

        yield task.deferLater(reactor, reconnectDelay + 1, lambda: None)

        yield doWork(2)
        yield doWork(3)

    except Exception as e:
        print type(e), str(e)
    finally:
        reactor.stop()

log.startLogging(sys.stdout)

reactor.suggestThreadPoolSize(1)
reactor.callWhenRunning(test)
reactor.run()

And its result:
2015-09-21 16:14:04+0200 [-] Log opened.
2015-09-21 16:14:04+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:04+0200 [-] New pool: <Redis Connection: Not connected>
2015-09-21 16:14:04+0200 [-] Running doWork batch #0
2015-09-21 16:14:04+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80de23db48> will retry in 2 seconds
2015-09-21 16:14:04+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80de23de60> will retry in 7 seconds
2015-09-21 16:14:04+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:07+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:07+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80de23db48> will retry in 10 seconds
2015-09-21 16:14:07+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:12+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:12+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80de23de60> will retry in 9 seconds
2015-09-21 16:14:12+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:18+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:18+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80de23db48> will retry in 11 seconds
2015-09-21 16:14:18+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:22+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:22+0200 [Uninitialized] Abandoning <twisted.internet.tcp.Connector instance at 0x7f80de23de60> after 6 retries.
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.6: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.3: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.0: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.7: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.4: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.9: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.8: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.1: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.5: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #0.2: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Running doWork batch #1
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.0: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.1: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.2: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.3: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.4: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.5: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.6: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.7: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.8: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Ping #1.9: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:22+0200 [Uninitialized] Connection failed after 5 attempts: Connection was refused by other side: 111: Connection refused.
2015-09-21 16:14:22+0200 [Uninitialized] Will create new pool after 10 seconds
2015-09-21 16:14:22+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:29+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:29+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d950>
2015-09-21 16:14:32+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d6c8>
2015-09-21 16:14:32+0200 [-] New pool: <Redis Connection: Not connected>
2015-09-21 16:14:32+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80de23d710> will retry in 2 seconds
2015-09-21 16:14:32+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80dddc4ea8> will retry in 5 seconds
2015-09-21 16:14:32+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d6c8>
2015-09-21 16:14:33+0200 [-] Running doWork batch #2
2015-09-21 16:14:35+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d6c8>
2015-09-21 16:14:35+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80de23d710> will retry in 12 seconds
2015-09-21 16:14:35+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d6c8>
2015-09-21 16:14:37+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d6c8>
2015-09-21 16:14:37+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80dddc4ea8> will retry in 10 seconds
2015-09-21 16:14:37+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d6c8>
2015-09-21 16:14:47+0200 [-] Starting factory <txredisapi.RedisFactory instance at 0x7f80de23d6c8>
2015-09-21 16:14:47+0200 [Uninitialized] <twisted.internet.tcp.Connector instance at 0x7f80de23d710> will retry in 10 seconds
2015-09-21 16:14:47+0200 [Uninitialized] Abandoning <twisted.internet.tcp.Connector instance at 0x7f80dddc4ea8> after 6 retries.
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.2: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.0: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.8: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.5: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.9: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.7: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.3: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.4: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.1: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #2.6: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Running doWork batch #3
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.0: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.1: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.2: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.3: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.4: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.5: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.6: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.7: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.8: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Ping #3.9: <class 'txredisapi.ConnectionError'> Not connected
2015-09-21 16:14:47+0200 [Uninitialized] Stopping factory <txredisapi.RedisFactory instance at 0x7f80de23d6c8>
2015-09-21 16:14:47+0200 [-] Main loop terminated.

Batch 0 failed because of new code and batch 1 because pool is not connected (and don't try connect). Then I create new pool and run batchs 2 and 3, their behaviour is same as 0 and 1.
I've fixed cancelWaiting because it discarded the failure.

authors: fiorix jakm

repo: fiorix/txredisapi


text:
Add filtering by tag to SimProject.format_record()

Imported from Bitbucket issue 7,  created by apdavison on 06-26-2010 at 20:44, last modified: 06-30-2010 at 13:52

Done in r124:6435bbd54a48 (actually not implemented for HttpRecordStore yet)
Trac comment by apdavison on 06-29-2010 at 10:32

As of r128:4945a1d3a9aa it is also implemented for HttpRecordStore
Trac comment by apdavison on 06-30-2010 at 13:52

repo: fipymigrate/sumatra


text:
Excessive build warnings

Step 1: Are you in the right place?
Yes
Step 2: Describe your environment

Objective C or Swift: Swift
iOS version: iOS 10
Firebase SDK version: 3.10.0
FirebaseUI version: 1.0.0
CocoaPods Version: 1.1.1

Step 3: Describe the problem:
Steps to reproduce:

Compile a project that depends on firebase

Observed Results:

Lots of warnings about nullability specifiers, for example "FIREmailPasswordAuthProvider.h:35:1: Conflicting nullability specifier on return types, 'nullable' conflicts with existing specifier 'nonnull'"

Expected Results:

No Warnings

This is an issue with upstream Firebase Auth, and will be fixed in the next Firebase release. This issue will remain open until then.
Thanks for reporting!

This is fixed with the Firebase 3.11 release. Running pod update should resolve the issue.

repo: firebase/FirebaseUI-iOS


text:
"unknown error" download extension to stream firestore collection to bq

Same error as seen here:

Interestingly, I am able to install the same extension for another project to an identical collection.

Hi @ipcleary.
This an issue that the Firebase team is currently investigating.
You can use the firebase  cli in the meantime to get around this problem.

@dackers86 good to know, thank you!

repo: firebase/extensions


text:
ImportError: No module named cachetools

Operating System version: Ubuntu 16.04.6 LTS
Firebase SDK version: 3.2.1 or 2.17.0 (tried both)
Firebase Product: messaging
Python Version: 2.7.12

whenever I try to import firebase-admin I'm getting the following error
Traceback (most recent call last):
File "Integrations/firebase.py", line 5, in
import firebase_admin
File "/usr/local/lib/python2.7/dist-packages/firebase_admin/init.py", line 23, in
from firebase_admin import credentials
File "/usr/local/lib/python2.7/dist-packages/firebase_admin/credentials.py", line 22, in
from google.oauth2 import credentials
File "/usr/local/lib/python2.7/dist-packages/google/oauth2/credentials.py", line 42, in
from google.oauth2 import _client
File "/usr/local/lib/python2.7/dist-packages/google/oauth2/_client.py", line 35, in
from google.auth import jwt
File "/usr/local/lib/python2.7/dist-packages/google/auth/jwt.py", line 48, in
import cachetools
ImportError: No module named cachetools
It seems like cachetools has stopped their support with Python2.7 and that's causing the import issue. Any suggestions on what I can try to do to resolve this issue?

Doesn't reproduce in my development environment:
$ virtualenv env -p python

$ source env/bin/activate
(env) $ python
Python 2.7.12 (default, Oct  8 2019, 14:14:10)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import firebase_admin
>>> firebase_admin.__version__
'3.2.1'
>>> import cachetools
>>> cachetools.__version__
'3.1.1'
>>> cachetools.__file__
'/home/hiranya/Projects/scratch/env/local/lib/python2.7/site-packages/cachetools/__init__.pyc'

As you can see cachetools 3.1.1 was installed along with firebase_admin. This was on Ubuntu 16.
Do you have an installation log, or a sequence of steps I can follow to reproduce this?

Here's one possible explanation:

google-auth declares the following dependency: "cachetools>=2.0.0,<5.0"
In some environments, this allows the installation to pull in the latest version of cachetools (v4).
This version seems to have dropped Python 2 support.

If this is the case, it needs to be resolved at https://github.com/googleapis/google-auth-library-python by updating their dependency to be <4.0.0. But in the meantime you have 2 workarounds:

Manually install 3.x version of cachetools.
Upgrade to Python 3.

I'd recommend the 2nd option, since Python 2 support is deprecated, and we will also stop supporting is very soon.

You can continue to track this at https://github.com/googleapis/google-auth-library-python/issues/414

repo: firebase/firebase-admin-python


text:
Crash GDTCORWriteDataToFile (GoogleDataTransport) on 295 line ([data writeToFile: ...)

Description
Firebase console shows that apps crashed on GDTCORPlatform.m line 295 (GDTCORWriteDataToFile).
Reproducing the issue
No response
Firebase SDK Version
10.6.0
Xcode Version
14.2
Installation Method
CocoaPods
Firebase Product(s)
Analytics, Crashlytics
Targeted Platforms
iOS
Relevant Log Output
Crashed: com.google.GDTCORFlatFileStorage
0  CoreFoundation                 0x7cbd8 CFDictionaryGetValue + 92
1  CoreFoundation                 0x18ca1c _CFBundleGetStringsSources + 1976
2  CoreFoundation                 0x73658 CFBundleGetLocalInfoDictionary + 196
3  CoreFoundation                 0x5d334 CFBundleGetValueForInfoDictionaryKey + 44
4  Foundation                     0x5e888 -[NSFileManager _URLForReplacingItemAtURL:error:] + 648
5  Foundation                     0x5e398 _NSCreateTemporaryFile_Protected + 168
6  Foundation                     0x6cf24 _NSWriteDataToFileWithExtendedAttributes + 436
7  GoogleDataTransport            0x14ed8 GDTCORWriteDataToFile + 295 (GDTCORPlatform.m:295)
8  GoogleDataTransport            0x111c8 __68-[GDTCORFlatFileStorage(Promises) fetchAndUpdateMetricsWithHandler:]_block_invoke + 130 (GDTCORFlatFileStorage+Promises.m:130)
9  FBLPromises                    0x9518 __38+[FBLPromise(DoAdditions) onQueue:do:]_block_invoke + 33 (FBLPromise+Do.m:33)
10 libdispatch.dylib              0x24b4 _dispatch_call_block_and_release + 32
11 libdispatch.dylib              0x3fdc _dispatch_client_callout + 20
12 libdispatch.dylib              0xb774 _dispatch_lane_serial_drain + 896
13 libdispatch.dylib              0xc1e0 _dispatch_lane_invoke + 384
14 libdispatch.dylib              0x16e10 _dispatch_workloop_worker_thread + 652
15 libsystem_pthread.dylib        0xdf8 _pthread_wqthread + 288
16 libsystem_pthread.dylib        0xb98 start_wqthread + 8

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Thanks for reporting, @MaxiJunkie. It seems like your issue is related to #10471. Are you using Performance SDK as well?

Seems like its trigger from FIRCrashlytics.initWithApp -> FIRCLSReportUploader.uploadPackagedReportAtPath -GoogleDataTrasnsport -> ... -> .GDTCORWriteDataToFile

authors: MaxiJunkie rizafran

repo: firebase/firebase-ios-sdk


text:
Codesigning failure on MacOS

Description
I have an app with the Firebase SDKs that compiles and works fine for an iOS destination. However, I now have a new MacOS destination and the build fails for it with the following error message:
....../...app: code object is not signed at all
In subcomponent: ....../Build/Products/Beta/..../Contents/Frameworks/GoogleAppMeasurement.framework
Command CodeSign failed with a nonzero exit code
When I filter the MacOS build log for signing,  I see the attached

:  the frameworks are not getting signed.
When I similarly filter for the iOS build, I see that they are getting signed.
Reproducing the issue
No response
Firebase SDK Version
10.23.1
Xcode Version
15.3
Installation Method
Swift Package Manager
Firebase Product(s)
Analytics
Targeted Platforms
macOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Thanks for the report. Is this issue occurring on 10.23**.0** as well?

Thanks for the report. Is this issue occurring on 10.23**.0** as well?

No, this does not occur on 10.23.0. Please note that I am using the new Xcode multiplatform target feature.

We are seeing a similar issue with Mac Catalyst after updating to version 10.23.1 from 10.23.0. An iOS destination seems to work fine.

This is also happening to my team for 10.23.1.
Noteworthy, it can also happen for another third party dependency that we use that is also a swift package .binaryTarget.

Thanks, everyone. I suspect this issue will be fixed by the 10.24.0 release next week. The next release will contain signed SDKs and SDKs with a fixed structure for macOS/macCatalyst. I will keep this issue open until then.

10.24.0 is now released and all XCFrameworks have code signatures.


text:
InAppMessaging is displayed even if specified app's version changes after auto-update

InAppMessaging is displayed after the iOS app is auto updated.
The trigger conditions are based on the previous version of the app.
Expected result is that the in-app message cannot be displayed.
[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your environment
Xcode version: 10.1
Firebase SDK version: 5.14
Firebase Component: InAppMessagingDisplay
Component version: 0.12.2
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:

login to web console (https://console.firebase.google.com/)

Grow > In-App Messaging, select

Target > App(iOS), and "Version" (https://console.firebase.google.com/project/${PROJCET ID}/inappmessaging/compose)
ex) this settings "include" version. 3.3.6

Scheduling : "Now" and "No end date"

Trigger : "app_lunch"

Publish, campain

the app's (version. 3.3.6) install and show In-App Messaging

the app's new version (version. 4.0.0) release / TestFlight release.

my iPhone "Settings" appli, iTunes Store & App Store > Updates "ON"

the app's updated (version. 4.0.0)

the app's lunch, show In-App Messaging

@christibbs can you update this issue?

Couldn't actually reproduce this.


text:
CoreData: warning: Property 'parameters' on Entity 'GAIHit' is using nil or an insecure NSValueTransformer

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.6
Firebase SDK version: 6.29.0
Firebase Component: Analytics
Component version: 6.29.0
Installation method: CocoaPodse

[REQUIRED] Step 2: Describe the problem
CoreData: fault: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.
CoreData: warning: Property 'parameters' on Entity 'GAIHit' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
Steps to reproduce:
Call Analytics.logEvent("", parameters: nil)
Relevant Code:

The root of this issue lies in GoogleAnalytics, which is a separate framework from Firebase Analytics and is not tied to the Firebase release cycle.
The fix should be pretty simple--GAIHit needs to conform to NSSecureUnarchiveFromData.

On further inspection, it looks like something is going on in your project. Google Analytics doesn't use CoreData to store hit events, it instead stores them in sqlite like Firebase Analytics does. Can you share your full Podfile.lock or a project that reproduces this issue?

After further investigation, it seems that the warning is coming from GoogleTagManager which seems that it's a dependency of Firebase Analytics? If I remove it from the project the warning goes away.
`PODS:

abseil/algorithm (0.20200225.0):

abseil/algorithm/algorithm (= 0.20200225.0)
abseil/algorithm/container (= 0.20200225.0)

abseil/algorithm/algorithm (0.20200225.0):

abseil/base/config

abseil/algorithm/container (0.20200225.0):

abseil/algorithm/algorithm
abseil/base/core_headers
abseil/meta/type_traits

abseil/base (0.20200225.0):

abseil/base/atomic_hook (= 0.20200225.0)
abseil/base/base (= 0.20200225.0)
abseil/base/base_internal (= 0.20200225.0)
abseil/base/bits (= 0.20200225.0)
abseil/base/config (= 0.20200225.0)
abseil/base/core_headers (= 0.20200225.0)
abseil/base/dynamic_annotations (= 0.20200225.0)
abseil/base/endian (= 0.20200225.0)
abseil/base/errno_saver (= 0.20200225.0)
abseil/base/exponential_biased (= 0.20200225.0)
abseil/base/log_severity (= 0.20200225.0)
abseil/base/malloc_internal (= 0.20200225.0)
abseil/base/periodic_sampler (= 0.20200225.0)
abseil/base/pretty_function (= 0.20200225.0)
abseil/base/raw_logging_internal (= 0.20200225.0)
abseil/base/spinlock_wait (= 0.20200225.0)
abseil/base/throw_delegate (= 0.20200225.0)

abseil/base/atomic_hook (0.20200225.0):

abseil/base/config
abseil/base/core_headers

abseil/base/base (0.20200225.0):

abseil/base/atomic_hook
abseil/base/base_internal
abseil/base/config
abseil/base/core_headers
abseil/base/dynamic_annotations
abseil/base/log_severity
abseil/base/raw_logging_internal
abseil/base/spinlock_wait
abseil/meta/type_traits

abseil/base/base_internal (0.20200225.0):

abseil/base/config
abseil/meta/type_traits

abseil/base/bits (0.20200225.0):

abseil/base/config
abseil/base/core_headers

abseil/base/config (0.20200225.0)
abseil/base/core_headers (0.20200225.0):

abseil/base/config

abseil/base/dynamic_annotations (0.20200225.0)
abseil/base/endian (0.20200225.0):

abseil/base/config
abseil/base/core_headers

abseil/base/errno_saver (0.20200225.0):

abseil/base/config

abseil/base/exponential_biased (0.20200225.0):

abseil/base/config
abseil/base/core_headers

abseil/base/log_severity (0.20200225.0):

abseil/base/config
abseil/base/core_headers

abseil/base/malloc_internal (0.20200225.0):

abseil/base/base
abseil/base/base_internal
abseil/base/config
abseil/base/core_headers
abseil/base/dynamic_annotations
abseil/base/raw_logging_internal

abseil/base/periodic_sampler (0.20200225.0):

abseil/base/core_headers
abseil/base/exponential_biased

abseil/base/pretty_function (0.20200225.0)
abseil/base/raw_logging_internal (0.20200225.0):

abseil/base/atomic_hook
abseil/base/config
abseil/base/core_headers
abseil/base/log_severity

abseil/base/spinlock_wait (0.20200225.0):

abseil/base/base_internal
abseil/base/core_headers
abseil/base/errno_saver

abseil/base/throw_delegate (0.20200225.0):

abseil/base/config
abseil/base/raw_logging_internal

abseil/container/compressed_tuple (0.20200225.0):

abseil/utility/utility

abseil/container/inlined_vector (0.20200225.0):

abseil/algorithm/algorithm
abseil/base/core_headers
abseil/base/throw_delegate
abseil/container/inlined_vector_internal
abseil/memory/memory

abseil/container/inlined_vector_internal (0.20200225.0):

abseil/base/core_headers
abseil/container/compressed_tuple
abseil/memory/memory
abseil/meta/type_traits
abseil/types/span

abseil/memory (0.20200225.0):

abseil/memory/memory (= 0.20200225.0)

abseil/memory/memory (0.20200225.0):

abseil/base/core_headers
abseil/meta/type_traits

abseil/meta (0.20200225.0):

abseil/meta/type_traits (= 0.20200225.0)

abseil/meta/type_traits (0.20200225.0):

abseil/base/config

abseil/numeric/int128 (0.20200225.0):

abseil/base/config
abseil/base/core_headers

abseil/strings/internal (0.20200225.0):

abseil/base/config
abseil/base/core_headers
abseil/base/endian
abseil/base/raw_logging_internal
abseil/meta/type_traits

abseil/strings/str_format (0.20200225.0):

abseil/strings/str_format_internal

abseil/strings/str_format_internal (0.20200225.0):

abseil/base/config
abseil/base/core_headers
abseil/meta/type_traits
abseil/numeric/int128
abseil/strings/strings
abseil/types/span

abseil/strings/strings (0.20200225.0):

abseil/base/base
abseil/base/bits
abseil/base/config
abseil/base/core_headers
abseil/base/endian
abseil/base/raw_logging_internal
abseil/base/throw_delegate
abseil/memory/memory
abseil/meta/type_traits
abseil/numeric/int128
abseil/strings/internal

abseil/time (0.20200225.0):

abseil/time/internal (= 0.20200225.0)
abseil/time/time (= 0.20200225.0)

abseil/time/internal (0.20200225.0):

abseil/time/internal/cctz (= 0.20200225.0)

abseil/time/internal/cctz (0.20200225.0):

abseil/time/internal/cctz/civil_time (= 0.20200225.0)
abseil/time/internal/cctz/time_zone (= 0.20200225.0)

abseil/time/internal/cctz/civil_time (0.20200225.0):

abseil/base/config

abseil/time/internal/cctz/time_zone (0.20200225.0):

abseil/base/config
abseil/time/internal/cctz/civil_time

abseil/time/time (0.20200225.0):

abseil/base/base
abseil/base/core_headers
abseil/base/raw_logging_internal
abseil/numeric/int128
abseil/strings/strings
abseil/time/internal/cctz/civil_time
abseil/time/internal/cctz/time_zone

abseil/types (0.20200225.0):

abseil/types/any (= 0.20200225.0)
abseil/types/bad_any_cast (= 0.20200225.0)
abseil/types/bad_any_cast_impl (= 0.20200225.0)
abseil/types/bad_optional_access (= 0.20200225.0)
abseil/types/bad_variant_access (= 0.20200225.0)
abseil/types/compare (= 0.20200225.0)
abseil/types/optional (= 0.20200225.0)
abseil/types/span (= 0.20200225.0)
abseil/types/variant (= 0.20200225.0)

abseil/types/any (0.20200225.0):

abseil/base/config
abseil/base/core_headers
abseil/meta/type_traits
abseil/types/bad_any_cast
abseil/utility/utility

abseil/types/bad_any_cast (0.20200225.0):

abseil/base/config
abseil/types/bad_any_cast_impl

abseil/types/bad_any_cast_impl (0.20200225.0):

abseil/base/config
abseil/base/raw_logging_internal

abseil/types/bad_optional_access (0.20200225.0):

abseil/base/config
abseil/base/raw_logging_internal

abseil/types/bad_variant_access (0.20200225.0):

abseil/base/config
abseil/base/raw_logging_internal

abseil/types/compare (0.20200225.0):

abseil/base/core_headers
abseil/meta/type_traits

abseil/types/optional (0.20200225.0):

abseil/base/base_internal
abseil/base/config
abseil/base/core_headers
abseil/memory/memory
abseil/meta/type_traits
abseil/types/bad_optional_access
abseil/utility/utility

abseil/types/span (0.20200225.0):

abseil/algorithm/algorithm
abseil/base/core_headers
abseil/base/throw_delegate
abseil/meta/type_traits

abseil/types/variant (0.20200225.0):

abseil/base/base_internal
abseil/base/config
abseil/base/core_headers
abseil/meta/type_traits
abseil/types/bad_variant_access
abseil/utility/utility

abseil/utility/utility (0.20200225.0):

abseil/base/base_internal
abseil/base/config
abseil/meta/type_traits

Alamofire (5.2.2)
apptentive-ios (5.2.14)
BluedotPointSDK (15.3.0)
BoringSSL-GRPC (0.0.7):

BoringSSL-GRPC/Implementation (= 0.0.7)
BoringSSL-GRPC/Interface (= 0.0.7)

BoringSSL-GRPC/Implementation (0.0.7):

BoringSSL-GRPC/Interface (= 0.0.7)

BoringSSL-GRPC/Interface (0.0.7)
CocoaAsyncSocket (7.6.4)
CryptoSwift (1.3.1)
FBSDKCoreKit (7.1.1):

FBSDKCoreKit/Basics (= 7.1.1)
FBSDKCoreKit/Core (= 7.1.1)

FBSDKCoreKit/Basics (7.1.1)
FBSDKCoreKit/Core (7.1.1):

FBSDKCoreKit/Basics

Firebase/Analytics (6.29.0):

Firebase/Core

Firebase/Auth (6.29.0):

Firebase/CoreOnly
FirebaseAuth (~> 6.7.1)

Firebase/Core (6.29.0):

Firebase/CoreOnly
FirebaseAnalytics (= 6.7.0)

Firebase/CoreOnly (6.29.0):

FirebaseCore (= 6.9.2)

Firebase/Crashlytics (6.29.0):

Firebase/CoreOnly
FirebaseCrashlytics (~> 4.3.1)

Firebase/Firestore (6.29.0):

Firebase/CoreOnly
FirebaseFirestore (~> 1.16.3)

Firebase/Messaging (6.29.0):

Firebase/CoreOnly
FirebaseMessaging (~> 4.6.1)

Firebase/RemoteConfig (6.29.0):

Firebase/CoreOnly
FirebaseRemoteConfig (~> 4.8.0)

FirebaseABTesting (4.1.0):

FirebaseCore (~> 6.8)

FirebaseAnalytics (6.7.0):

FirebaseCore (~> 6.8)
FirebaseInstallations (~> 1.4)
GoogleAppMeasurement (= 6.7.0)
GoogleUtilities/AppDelegateSwizzler (~> 6.7)
GoogleUtilities/MethodSwizzler (~> 6.7)
GoogleUtilities/Network (~> 6.7)
"GoogleUtilities/NSData+zlib (~> 6.7)"
nanopb (~> 1.30905.0)

FirebaseAuth (6.7.1):

FirebaseCore (~> 6.8)
GoogleUtilities/AppDelegateSwizzler (~> 6.7)
GoogleUtilities/Environment (~> 6.7)
GTMSessionFetcher/Core (~> 1.1)

FirebaseCore (6.9.2):

FirebaseCoreDiagnostics (~> 1.3)
GoogleUtilities/Environment (~> 6.7)
GoogleUtilities/Logger (~> 6.7)

FirebaseCoreDiagnostics (1.5.0):

GoogleDataTransport (~> 7.0)
GoogleUtilities/Environment (~> 6.7)
GoogleUtilities/Logger (~> 6.7)
nanopb (~> 1.30905.0)

FirebaseCrashlytics (4.3.1):

FirebaseCore (~> 6.8)
FirebaseInstallations (~> 1.1)
GoogleDataTransport (~> 7.0)
nanopb (~> 1.30905.0)
PromisesObjC (~> 1.2)

FirebaseFirestore (1.16.3):

abseil/algorithm (= 0.20200225.0)
abseil/base (= 0.20200225.0)
abseil/memory (= 0.20200225.0)
abseil/meta (= 0.20200225.0)
abseil/strings/strings (= 0.20200225.0)
abseil/time (= 0.20200225.0)
abseil/types (= 0.20200225.0)
FirebaseCore (~> 6.8)
"gRPC-C++ (~> 1.28.0)"
leveldb-library (~> 1.22)
nanopb (~> 1.30905.0)

FirebaseInstallations (1.5.0):

FirebaseCore (~> 6.8)
GoogleUtilities/Environment (~> 6.7)
GoogleUtilities/UserDefaults (~> 6.7)
PromisesObjC (~> 1.2)

FirebaseInstanceID (4.5.1):

FirebaseCore (~> 6.8)
FirebaseInstallations (~> 1.0)
GoogleUtilities/Environment (~> 6.7)
GoogleUtilities/UserDefaults (~> 6.7)

FirebaseMessaging (4.6.1):

FirebaseCore (~> 6.8)
FirebaseInstanceID (~> 4.3)
GoogleUtilities/AppDelegateSwizzler (~> 6.7)
GoogleUtilities/Environment (~> 6.7)
GoogleUtilities/Reachability (~> 6.7)
GoogleUtilities/UserDefaults (~> 6.7)
Protobuf (>= 3.9.2, ~> 3.9)

FirebaseRemoteConfig (4.8.0):

FirebaseABTesting (~> 4.1)
FirebaseCore (~> 6.8)
FirebaseInstallations (~> 1.1)
GoogleUtilities/Environment (~> 6.7)
"GoogleUtilities/NSData+zlib (~> 6.7)"

GoogleAnalytics (3.17.0)
GoogleAppMeasurement (6.7.0):

GoogleUtilities/AppDelegateSwizzler (~> 6.7)
GoogleUtilities/MethodSwizzler (~> 6.7)
GoogleUtilities/Network (~> 6.7)
"GoogleUtilities/NSData+zlib (~> 6.7)"
nanopb (~> 1.30905.0)

GoogleDataTransport (7.1.0):

nanopb (~> 1.30905.0)

GoogleSymbolUtilities (1.1.2)
GoogleTagManager (7.1.3):

FirebaseAnalytics (~> 6.3)
GoogleAnalytics (~> 3.17)
GoogleUtilitiesLegacy (~> 1.3)

GoogleUtilities/AppDelegateSwizzler (6.7.1):

GoogleUtilities/Environment
GoogleUtilities/Logger
GoogleUtilities/Network

GoogleUtilities/Environment (6.7.1):

PromisesObjC (~> 1.2)

GoogleUtilities/Logger (6.7.1):

GoogleUtilities/Environment

GoogleUtilities/MethodSwizzler (6.7.1):

GoogleUtilities/Logger

GoogleUtilities/Network (6.7.1):

GoogleUtilities/Logger
"GoogleUtilities/NSData+zlib"
GoogleUtilities/Reachability

"GoogleUtilities/NSData+zlib (6.7.1)"
GoogleUtilities/Reachability (6.7.1):

GoogleUtilities/Logger

GoogleUtilities/UserDefaults (6.7.1):

GoogleUtilities/Logger

GoogleUtilitiesLegacy (1.3.2):

GoogleSymbolUtilities (~> 1.1)

"gRPC-C++ (1.28.2)":

"gRPC-C++/Implementation (= 1.28.2)"
"gRPC-C++/Interface (= 1.28.2)"

"gRPC-C++/Implementation (1.28.2)":

abseil/container/inlined_vector (= 0.20200225.0)
abseil/memory/memory (= 0.20200225.0)
abseil/strings/str_format (= 0.20200225.0)
abseil/strings/strings (= 0.20200225.0)
abseil/types/optional (= 0.20200225.0)
"gRPC-C++/Interface (= 1.28.2)"
gRPC-Core (= 1.28.2)

"gRPC-C++/Interface (1.28.2)"
gRPC-Core (1.28.2):

gRPC-Core/Implementation (= 1.28.2)
gRPC-Core/Interface (= 1.28.2)

gRPC-Core/Implementation (1.28.2):

abseil/container/inlined_vector (= 0.20200225.0)
abseil/memory/memory (= 0.20200225.0)
abseil/strings/str_format (= 0.20200225.0)
abseil/strings/strings (= 0.20200225.0)
abseil/types/optional (= 0.20200225.0)
BoringSSL-GRPC (= 0.0.7)
gRPC-Core/Interface (= 1.28.2)

gRPC-Core/Interface (1.28.2)
GTMSessionFetcher/Core (1.4.0)
JustLog (3.0.5):

CocoaAsyncSocket (~> 7.6.3)
SwiftyBeaver (~> 1.8.3)

KochavaCoreiOS (3.17.0)
KochavaTrackeriOS (3.17.0):

KochavaCoreiOS (~> 3.16)

leveldb-library (1.22)
MarketingCloudSDK (7.2.1)
nanopb (1.30905.0):

nanopb/decode (= 1.30905.0)
nanopb/encode (= 1.30905.0)

nanopb/decode (1.30905.0)
nanopb/encode (1.30905.0)
PromiseKit (6.13.1):

PromiseKit/CorePromise (= 6.13.1)
PromiseKit/Foundation (= 6.13.1)
PromiseKit/UIKit (= 6.13.1)

PromiseKit/CorePromise (6.13.1)
PromiseKit/Foundation (6.13.1):

PromiseKit/CorePromise

PromiseKit/UIKit (6.13.1):

PromiseKit/CorePromise

PromisesObjC (1.2.9)
Protobuf (3.12.0)
SpinnerView (0.1.1)
SwiftValidator (4.0.0)
SwiftyBeaver (1.8.4)
Typist (1.4.2)
WebViewJavascriptBridge (6.0.3)

DEPENDENCIES:

Alamofire
apptentive-ios (~> 5.2)
BluedotPointSDK
CryptoSwift
FBSDKCoreKit
Firebase/Analytics
Firebase/Auth
Firebase/Core
Firebase/Crashlytics
Firebase/Firestore
Firebase/Messaging
Firebase/RemoteConfig
GoogleTagManager
JustLog
KochavaTrackeriOS
MarketingCloudSDK
PromiseKit
Typist
WebViewJavascriptBridge

SPEC REPOS:
trunk:
- abseil
- Alamofire
- apptentive-ios
- BluedotPointSDK
- BoringSSL-GRPC
- CocoaAsyncSocket
- CryptoSwift
- FBSDKCoreKit
- Firebase
- FirebaseABTesting
- FirebaseAnalytics
- FirebaseAuth
- FirebaseCore
- FirebaseCoreDiagnostics
- FirebaseCrashlytics
- FirebaseFirestore
- FirebaseInstallations
- FirebaseInstanceID
- FirebaseMessaging
- FirebaseRemoteConfig
- GoogleAnalytics
- GoogleAppMeasurement
- GoogleDataTransport
- GoogleSymbolUtilities
- GoogleTagManager
- GoogleUtilities
- GoogleUtilitiesLegacy
- "gRPC-C++"
- gRPC-Core
- GTMSessionFetcher
- JustLog
- KochavaCoreiOS
- KochavaTrackeriOS
- leveldb-library
- MarketingCloudSDK
- nanopb
- PromiseKit
- PromisesObjC
- Protobuf
- SwiftyBeaver
- Typist
- WebViewJavascriptBridge
EXTERNAL SOURCES:
CHECKOUT OPTIONS:
SPEC CHECKSUMS:
abseil: 6c8eb7892aefa08d929b39f9bb108e5367e3228f
Alamofire: 814429acc853c6c54ff123fc3d2ef66803823ce0
apptentive-ios: 16951b1f9546bbae9165792679f865dc53bbe82f
BluedotPointSDK: 729d468235468ed1737a0aa61106fbf3ac7b366a
BoringSSL-GRPC: 8edf627ee524575e2f8d19d56f068b448eea3879
CocoaAsyncSocket: 694058e7c0ed05a9e217d1b3c7ded962f4180845
CryptoSwift: f12f037f6d0fcd6d48c96db0071b653de64e6c4d
FBSDKCoreKit: b46507dc8b8cefed31d644e74d7cc30e2a715ef8
Firebase: 57957c8d6eb3d8b80a560b1dc58be24724b89ff2
FirebaseABTesting: 9e368b88c2f1c5d7a433828d9d224779b53207b6
FirebaseAnalytics: aa522dce9fd93002ba1554467d23ce7092323000
FirebaseAuth: a818d73466d51db897d3bf3c0f3baa3dae7fd4c0
FirebaseCore: 7930a1946517d94256d857f97371ed993b55f7bd
FirebaseCoreDiagnostics: 7535fe695737f8c5b350584292a70b7f8ff0357b
FirebaseCrashlytics: 863c851b034baeb3116cd2c91743e37de2dcedfc
FirebaseFirestore: 5ea7b0878363f9ec66bdcee0c29ad875d1b511ac
FirebaseInstallations: 3c520c951305cbf9ca54eb891ff9e6d1fd384881
FirebaseInstanceID: c4ad474b87787afd27d09541800620993b457d6f
FirebaseMessaging: 942cfe05b4f53c95ab8959395ca35c200398b2f0
FirebaseRemoteConfig: 521ff38593bed36fcb6f466fb6fffa99a753d783
GoogleAnalytics: f42cc53a87a51fe94334821868d9c8481ff47a7b
GoogleAppMeasurement: 345d365fd105e6682bf5084783a5352a3db26820
GoogleDataTransport: af0c79193dc59acd37630b4833d0dc6912ae6bd5
GoogleSymbolUtilities: 631ee17048aa5e9ab133470d768ea997a5ef9b96
GoogleTagManager: a5b872a9aae225c83587cc526d816b0323961845
GoogleUtilities: e121a3867449ce16b0e35ddf1797ea7a389ffdf2
GoogleUtilitiesLegacy: 5501bedec1646bd284286eb5fc9453f7e23a12f4
"gRPC-C++": 13d8ccef97d5c3c441b7e3c529ef28ebee86fad2
gRPC-Core: 4afa11bfbedf7cdecd04de535a9e046893404ed5
GTMSessionFetcher: 6f5c8abbab8a9bce4bb3f057e317728ec6182b10
JustLog: d583795da0ed7da3c4adcd76c28031d4043a3258
KochavaCoreiOS: 0dc05fb86adb2bd27f01e8b06e48e621ea789df3
KochavaTrackeriOS: 3bc2417dd6b9e7bbe99b8acfee0f83e1447d7469
leveldb-library: 55d93ee664b4007aac644a782d11da33fba316f7
MarketingCloudSDK: 14cbb3e77f50c69aea078c6c70368ca29041eaee
nanopb: c43f40fadfe79e8b8db116583945847910cbabc9
PromiseKit: 28fda91c973cc377875d8c0ea4f973013c05b6db
PromisesObjC: b48e0338dbbac2207e611750777895f7a5811b75
Protobuf: 2793fcd0622a00b546c60e7cbbcc493e043e9bb9
SpinnerView: 411d0af71d49975aab0e71764eb95f1b780bbb90
SwiftValidator: 249b6b3ae3b294266c5b9de134d94f18f2d5aa47
SwiftyBeaver: f9a9aba96a6a6166e21682377804d728b0d20b95
Typist: 06465ab9867782aa6c81e38f073dfc01dab73deb
WebViewJavascriptBridge: 7f5bc4d3581e672e8f32bd0f812d54bc69bb8e29
PODFILE CHECKSUM: c098f349c3e8e3bf0a4ba96fa9e07b421d3b8ef6
COCOAPODS: 1.9.3
`

Thanks. TagManager uses CoreData to persist events and is definitely what's responsible for triggering this warning. I'll make a fix for it.
In the meantime, if you want to avoid this warning and don't need GoogleAnalytics in your project, you can simply remove GoogleAnalytics and log all of your app's events through FirebaseAnalytics instead.

Googlers see internal change number cl/325478723

The fix has been submitted to TagManager. TagManager operates on a different release schedule than Firebase, so you will not see the fix in the Firebase release notes.

@morganchen12 how can I apply the fix for GA for Unity? Which is obviously abandoned?

authors: akcelotechnology enquel morganchen12