text:
Plugin upgrades

This is a micro-SIP for informing Spin users when there are new versions of their favourite plugins.  It is for discussion.
Principles:

Do not break the user's existing workflow (habits, scripts, etc.).
Do not block the user (make them wait on a prompt, make progress conditional on a download).
Do not surprise the user.
Do not badger the user.
Respect CI environments.

A specific consideration is that a GH action that installs an older plugin should continue to work.

Classification:

If the user is on a stable line of a plugin (>=1.x), and there is a higher version available within the same major version, that upgrade is eligible.
Upgrades within unstable lines (0.x) are questionable.
Upgrades across major versions (1.x -> 2.x) are questionable.
Upgrades with pre-release entries in their version (1.2.3-alpha.1) are ineligible.

We could refine this rule to make pre-releases eligible if the user is already on an earlier pre-release of that patch version, but pre-release text doesn't sort well and I'm not sure we have a sense of "earlier/later" other than the version.

When to notify:

When a user runs a plugin, we check for the availability of an upgrade.
If there is an eligible upgrade:.

Has the user already been notified about this version?  If so, do nothing.
Has the user been notified about any upgrade from their current version of the plugin within the last B days?  If so, do nothing.

The nuance here is for the following reason.  Suppose the user is on 1.3.  On Monday, the user runs the plugin, and we detect and offer an upgrade to 1.4.  They do the upgrade.  On Tuesday, 1.4.1 comes out.  On Wednesday, the user runs the plugin again.  We should probably mention 1.4.1 even though we prompted on Monday.  But if the user chose not to do the upgrade to 1.4, then we should not keep badgering them.  So we need a sense of "resetting" the badger clock when they do an upgrade.
There is still a risk of badger if a plugin has high churn.  The user keeps running to keep up but there's always a new upgrade to be pestered about.  We can probably cross this bridge if we come to it.

Otherwise, print a message informing the user that the upgrade is available and telling them how to get it.

If there is a questionable upgrade:

TBD.  We could notify them using the same rules as eligible upgrades but with the message warning about breaking changes, and possibly with a longer badger clock.  Or we could not notify them.  Or something else.

If there is an ineligible upgrade, do nothing.
This proposal doesn't define the badger timeout B, but that is easy to tweak during implementation and rollout.  My guess is we would start it at 7 or 14 days.

How to notify:

Spin could notify before handing off to the plugin.  This gets it out of the way.  But if the plugin produces non-trivial amounts of output, the message will disappear.  It also means we have to either make the user wait while we check for availability, or do a background check and notify the next time they run the plugin.
Spin could notify after the plugin exits.  This would allow Spin to do checks in the background while the plugin is running, avoiding any startup delay, ensures that the message is visible even if the plugin has produced a lot of output, and prints it at the moment the user/terminal comes free, so they can action the upgrade offer immediately.  I am not sure if this increases complexity though.
My preference is to notify after the plugin exits.
In either case, notifications should be "print to terminal" only.  Spin should not display a prompt that requires a response in order to proceed.
In either case, the upgrade check must be silent and errors must not be reported to the user.

Spin should skip the upgrade check If the environment is not a terminal, because there is no user to notify so it's a waste of bandwidth.

Privacy;

The user should be able to opt out of upgrade checks, via an environment variable or such like.

Perhaps the first time the user runs a plugin (any plugin), we should inform the user how to opt out.  That doesn't give them an opportunity to back out, though, unless we have the more complex rule of "the first time, we print the opt out notification; only the second time do we actually perform an upgrade check."  I am not sure how much of a concern this is.

The most information sent from the user's machine during the upgrade check should be the plugin name and version.  (I suspect we won't need to send that because we will look at the git repo, but then we get into repeated pulls, rate limiting, and similar "the whole reason why the update command exists" issues.  So I want to leave this much wiggle room.)

Future refinements:

It could be worth allowing authors to tag releases as urgent, e.g. security patches.  Urgent releases would change the rules a bit:

Urgent releases within the 0.x line would be eligible.  (Not sure about across stable major versions.  In principle a security patch would be backported.  In practice, that's not always the case.)
Urgent releases would be notified even if user had recently been badgered.  (Not sure if we would repeatedly notify for the same urgent release.  But if the user had recently declined an upgrade, and then there was an urgent release, that should be notified.)

I'm aligned with all of this. We will probably want to add this mini-SIP to the spin-plugins repository so authors know how their versioning scheme affects auto-upgrades

I feel like we could get away with slightly more badgeriness, like renotifying for eligible updates every badger timeout.

@kate-goldenring For checking upgrade availability, do you think it would be okay to effectively run spin update, or would you recommend something different?  I am thinking about:

Is it good or bad that they see an updated registry even though they never explicitly updated it themselves?
What is the potential impact on GitHub throttling - this was the original motive for not checking on every upgrade I think?  I don't know if pulling only the 'latest' file for a plugin would have a lower impact.

@itowlson, I don't see a downside to (1), since the local registry will still contain older versions of the manifests but now just also have the new ones. For (2), wouldn't updating one file with git require fetching all files? I am not sure in git how to just fetch one file but we could effectively curl the latest file at the expected path.
I do feel concern in running update every time a plugin is executed. I wonder if we want an update interval along with a badger interval. IE if it has been over 12 hours since the last update, we do a spin plugin update.

@kate-goldenring Yeah curling the latest file was what I prototyped.
The way I have prototyped it does things in a different order, so it would only check for updates if:

The user is now running a different plugin version from the last notification (i.e. they accepted the last badger); or
The badger interval has expired.

So that should keep the GH load down even without a separate update interval; plugins in the registry are unlikely to churn that fast enough for 1 to be a big issue (given that it's a PR and manual approval process to update the registry).

Hmm, the downside of curling only the latest is that if latest is incompatible with the user's version of Spin, but an intermediate version is compatible, we would not prompt to upgrade to the intermediate version.  So that might be a reason to do the full update.
(I forgot about Spin compatibility above... for completeness, upgrades where the Spin version requirement does not match are, naturally, ineligible.)
I am a bit concerned, though, that full update could be slow.  For plugins that normally complete quickly, this could result in a lot of cancelled updates (because we don't want to unduly delay exiting just for the sake of the badger).

I am a bit concerned, though, that full update could be slow. For plugins that normally complete quickly, this could result in a lot of cancelled updates (because we don't want to unduly delay exiting just for the sake of the badger).

Could fork a daemon to do the update, write the result to a file, and check the result file on plugin exit. If the update doesn't complete before the plugin exits this time you'll have the result ready for next time

I considered spinning off a background process, but was a bit intimidated by the additional moving parts (particularly for error cases, and edge cases like multiple instances running at once / user running update at the same time as the daemon is trying to / etc.).  It's definitely an option if we go the full update route though.  I'm not sure why a full daemon rather than a background process - would you see that as serialising updates or something?
It's probably worth aligning on perspective too.  I have been thinking about this as an advisory feature, that isn't worth making too involved and doesn't need to be perfect.  But if we regard it as a key servicing feature then it merits the extra level of robustness.

why a full daemon rather than a background process

Ah yeah I guess I mean "short-lived daemon". Sometimes "daemon" means "system service" and sometimes it just means "that one weird double-fork trick".

we would not prompt to upgrade to the intermediate version

This is a good point. I wonder if adding a subrepository to the plugins repository that just contains the manifests directory would reduce the fetch time.
I agree with the point on this not needing to be perfect on the first run. it may make sense to do full updates for now without a separate daemon process and then get feedback and potentially iterate to something more robust

I have an experimental branch using the "full update" strategy at https://github.com/itowlson/spin/tree/plugins-badger-full-update.
At the moment it looks like it needs about 750ms to complete an update when the working copy is already up to date.  For a fast-running plugin (which completes in say 10ms), that means a perceptible wait after the plugin exits.  The timeout I used in the curl branch was 250ms, which was barely noticeable (at least to me, though I am admittedly less sensitive to this stuff than many people).  So it depends on whether realistic plugins are likely to take 500ms+.

Yep, sorry, should have made that explicit.

The timeout I used in the curl branch was 250ms, which was barely noticeable (at least to me, though I am admittedly less sensitive to this stuff than many people)

Another option would be to add a versions.txt file to each plugin in the spin-plugins repo that contains all the existing versions of the plugin. Then on each update, we curl that file to check if an update is needed of it. Then if there are N latest updates to the plugin, it will then fetch the Nth. If its not compatible, it could then fetch each of the intermediate ones or do a full update at that point to not have too much of a curl train.

Okay there is a background processy branch at https://github.com/itowlson/spin/tree/plugins-badger-background-process-eek-eek-eek and it seems to work but I have no real idea how to evaluate it for correctness, especially in the face of errors or concurrency.
@lann I don't know if this is what you were thinking of when you mentioned a daemon approach or a "weird double fork trick" - all it does at the moment is spawn a background process - were you proposing more than that?

The "weird double fork trick" is about detaching the child process from the controlling terminal, but now that I think about I'm actually not sure whether you want the child to detach in this scenario... :thinking:

Uhhhhhhhhhhhhhhhhh... well... with what I've done the child can continue to run after the parent exits... I have not tested what happens if I close the terminal... do we care?  DON'T MAKE ME CARE LANN

How do we want to take this forward?

Okay it sounds like we had three options here:

Curl latest file (plugins-badger branch)

Concern: lack of intermediate version compat checking)
Consensus: do not choose

Full update: Run a spin plugins update at appropriate times (plugins-badger-full-update brance)

Concern: extends the time of the plugin process potentially substantially

Run full update as background process (...eek branch

Concern: Background say what?

Yes.  I don't love any of them.  The background process is probably the most robust in terms of getting updates in front of users, and I think avoids any UI speed bumps.  But correctness is going to be hard to confirm, especially since pulled updates will often not be displayed until the next time the plugin runs.  I am also not sure if there are any concurrency implications if two background checks kick off close together, or throttling implications since each plugin will trigger an update independently.  We can address those latter two points but it will make it more complicated (like serialising update requests and/or or recording a last update time and not re-updating within a timeout).  Which I guess is why large-scale servicing processes really do run as actual honest-to-goodness daemons...

cloud we do something where the upgrade background process grabs an flock() so it always checks if its locked and if so doesn't run.

Yeah that was the sort of thing I was thinking of for concurrency (and throttling isn't really an issue, nobody will run that many different plugins frequently enough or for long enough and I should get over myself).  We'd need some UI for "user tries to update while a background process is updating" but that's no biggie.  And of course now I am going into agonies about the background process getting stuck or failing to clean up the lock.
But correctness remains the big worry.

And of course now I am going into agonies about the background process getting stuck or failing to clean up the lock.

Good point. I think we will have some nice troubleshooting docs for this. I think its fair to proceed with the background process approach and we can iterate based on the behavior people experience.

The background process only needs to sync the repo right? Seems like that would use an "update state" file to track last update time for rate limiting, which it can flock during the update process (which will always unlock on process exit). Now you "just" have to worry about the background process hanging...

@lann

Don't you have to reboot windows every few hours anyway?

All right, Rust fs2 file locking uses LockFileEx on Windows, not the dreaded share mode APIs:

If a process terminates with a portion of a file locked or closes a file that has outstanding locks, the locks are unlocked by the operating system.

So we are gold--

However,

MUST WE MICROSOFT MUST WE
Anyway yep I can take a look at this.  I'll do it as a separate PR to spin plugins update as it is arguably a general safety feature (and to avoid piling more gunk into the branch).  Thanks all for the info, thought-sharing, and operating system banter.

authors: itowlson kate-goldenring lann

repo: fermyon/spin


text:
Show common trigger options on spin up --help

Fixes #1078, #815.
When the user runs spin up --help and there is no application (that is, the default application file doesn't exist), it now shows the common trigger CLI flags.
To maximise consistency with the standard help flow (where there is an application), this gets the trigger help options by handing off to a trigger command; however in the no-app case it is a hidden no-op trigger type that has only the base set of trigger CLI flags.
If an application manifest is present, its trigger type is invoked as usual (e.g. if there is a HTTP app present, the user still sees the --listen and TLS flags).
Signed-off-by: itowlson ivan.towlson@fermyon.com

Hi @itowlson please pardon me if I understood something incorrectly, but shouldn't this wait for https://github.com/fermyon/spin/pull/974 to complete?

@rajatjindal No, this is completely orthogonal.  The issue that this fixes is that if you are in a directory without a spin.toml file then spin up --help doesn't show the flags that are defined on spin_trigger::cli instead of directly on up.  Even if we later change or reshuffle, those options, the principle that "spin up --help should show all the options" remains true.
As an example of non-logging optioins, the Wasm cache, transient write, and runtime config flags are defined on the trigger and currently disappear if there is no spin.toml in the current directory.

source: gharchive/pull-request

authors: itowlson rajatjindal

license_type: permissive

license_source: github-api


text:
Tolerate component routes not starting with '/'

Fixes #1493.
An alternative solution would be to fail validation if any component route didn't start with '/'.  That would be safer in the sense of not committing us to supporting "wrong" manifests, but would risk a user experience of "stupid computer, you know what's wrong so why do you need me to fix it."  Happy to switch to that if people prefer.

@rylev awesome, thanks!


text:
Add initial implementation of turso integration

Marking this as WIP since it needs a bit of clean up, but it works in its current state. I was able to run the example todo app against a Turso backend.

Incorporated into #1545.

authors: itowlson rylev


text:
🛑 Ozono Odoo is down

In 161bfd6, Ozono Odoo (https://ozonotest.ddns.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ozono Odoo is back up in 91d2517 after 1 hour, 7 minutes.

source: gharchive/issue

license: MIT


text:
Fix Client.scrape returns no error on invalid URL

Fix #167.

Released as 8.0.8

repo: feross/bittorrent-tracker

license: mit

license_source: bigquery


text:
Python script to ease data collection for config files.

I have created a simple script to help with the all the data collection from RPA,
You can find it in a gist, here.
Assumptions
This script assumes the following initial file structure:
./
./data/
./data_parser.py

Operation

Choose an O/F ratio to work on.
Use RPA to generate data for each chamber pressure (Pe) you need in increasing order, saving the results in ./data/ with an individual and also increasing name (e.g. 1.txt, 2.txt, etc.).
Run the python script when you have all data you desire for the current O/F ratio.
A file results.txt will appear in ./, containing all the key values formatted for the config.
You must delete all files in ./data/ and ./results.txt before starting the next O/F ratio! I have not added any file handling other than reading the data files and writing the results.

I may update this with further improvements, but this saves so much time already. Just make sure to watch for any questionable data while doing this.

I've updated the script, here: https://gist.github.com/dgeastman/29a26dd8c08fb156660fefea1a8ffda8
It now has the Cpc and Cpe fields, and I also moved the results.txt file into the ./data directory, so that you can easily archive the input and results in case we need to go back again.

@ferram4 Do you foresee needing any data on propellant mixtures/mass ratios, nozzle inlet/throat, or anything else that RPA calculates?

@Tyaedalis I don't see any reason to keep the nozzle inlet data, since in this situation it's identical to the injector data.  I'm not using the throat data currently, but I can see that I might at some point so keep that.  Only other data I'd archive is the stoichiometric O/F somewhere (shouldn't change between O/Fs).  If you want to plan ahead for solid fuel, keep track of the mass fraction of condensed phases (liquid or solid) at the nozzle exit, since that'll be useful for handling solid rocket losses.

Hey, I just gotta say I've been busy with other work, and not only disappointed that I have to redo everything. BUT! I do have plans to redo my script and regenerate everything. I've only been quiet here because of other business. I really want to see this project reach finality.

Oh, don't worry too much.  I made some minor updates to the kerolox config since everything with an O/F lower than ~O/F 2.2 had the wrong area ratio set (to 1.5 rather than 1.3, understandable) so that's fixed except for 0.8 since that requires the averaging process and I've been putting off doing that one.
Also, interesting thing: it looks like the Cps for really stupidly rich mixtures are a little too high.  I don't think it requires changes in the data capturing procedure, I'll adjust it in code instead.

authors: Tyaedalis dgeastman ferram4


text:
Revert "Copy for promoting translations repo on language switcher page."

Reverts fetlife/translations#16

@reneklacan mind checking this with me? The diff here is not what I wanted it to be. The bad commit was this one: https://github.com/fetlife/translations/commit/6bd06866fad6940ed8114db359d374dae4a359ca
It was part of this PR, but it doesn't show up on the revert diff.

repo: fetlife/translations


text:
Password is still visible

Atom v0.175.0

Thank you for reporting this! I'll have a look tonight.
We had to emulate a password field as Atom didn't support input type="password" out of the box yet. Hopefully by now this works.


text:
Create contribution guide

Issue #7

Description

It was created the contribution guide for newcomers
Types of changes

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

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

it's ok

authors: RomuloSouza cjjcastro


text:
[DOC11] Documentar sprints

Descrição da mudança
Adição das sprints documentadas, com o planejamento e os resultados, dentro dos resultados estão o velocity e o burndown.
Tipo da mudança

[ ] Correção de bug.
[x] Adição de nova fucionalidade.

Issue relacionada
#34
Screenshots

Informações adicionais
Checklist

[x] O pull request possui nome significativo.
[x] O pull request possui descrição significativa.
[x] O pull request possui a marcação correspondente ao tipo da mudança.
[ ] O pull request possui screenshots quando necessário.
[x] O pull request possui labels.

Apesar das Sprints poluirem a sidebar se elas ficarem com links para os planejamentos e resultados, acredito melhorar a navegabilidade. Também acredito que seria melhor para o usuário se ele visse o nome do documento que ele está vendo no topo.

@cantuariavc concordo com vc, nós até tinhamos conversado sobre isso anteriormente e a gente estava tendo dificuldades para encontrar uma melhor posição. Eu creio que podemos definir melhor o layout em uma próxima issue, pois não é apenas o das sprints que estão nesse formato.

Corrigindo os erros que você apontou, eu percebi que havia uma de discrepância na pontuação do burndown e do planejamento. Percebi que o zenhub conta tanto os pontos das issues quanto os pontos dos pull requests, ou seja, não podemos pontuar as duas coisas. Só precisamos pontuar as issues. Eu já arrumei esse problema e atualizei as imagens do burndown e do velocity.


text:
Edit mail template.

How do I edit message template sent from kanboard?
Thanks!

Look into https://github.com/fguillot/kanboard/tree/master/app/Template/notification

authors: BlueTeck vsadriano

repo: fguillot/kanboard


text:
Recurring tasks concept (#340)

In this concept, essentially, when triggered, a task marked as recurring is duplicated to the first column of the same board in the same swim lane and the due date (if there is one specified) is adjusted accordingly.
There are 3 triggers that currently create a new recurring task; moving a task from the first column, moving a task to the last column, or closing the task (trigger is configurable per task).
Due dates, if set on the current task, can be recalculated by a given factor of days, months or years. The base date for the calculation of the new due date can be either the existing due date, or the trigger date (configurable per task).
Each task tracks the task id of the parent task that created it, and the child task that it creates.
Once a task has created a child task, the recurring settings cannot be changed in the UI (can be updated in the API).

@fguillot. Sorry, I meant to do the Vagrantfile change as a separate pull request. Hope this is OK.

Thanks for the pull-request, It's now merged in master! I improved some part of the code and added some unit tests...

Thanks @fguillot for accepting/merging it in (and adding the unit tests and other housekeeping tasks). Sorry for some of the troubles encountered. For an enhancement, I specifically didn't do it, because I personally feel it goes against Kanban methodology, but I did have the idea if people need the ability to create multiple tasks upfront, it would be possible to add a new trigger status (Manual), and manually call duplicateRecurringTask in a loop to create many tasks in advance. With proper checks and balances, the loop can be for a either a set iteration (create 5 duplicate tasks), or until a specific due date is reached. Another enhancement would be instead of triggering from the first or last column or closing of the task, would be to add another trigger type and process it when moved to a column that has an automatic action setup. There were lots of ideas, however I wanted to get a base concept in first to see if/how it was accepted. Great work on Kanboard. Love it.

authors: David-Norris fguillot


text:
Added vk.com to iframe whitelist

Example of video link: https://vk.com/video_ext.php?oid=-67429455&id=171494363&hash=6fdc6b4472acdaa7
Example of iframe: <iframe allowfullscreen="" width="607" height="360" src="https://vk.com/video_ext.php?oid=-67429455&id=171494363&hash=6fdc6b4472acdaa7" frameborder="0"></iframe>

@BernhardPosselt I did it

Needs https too :)

Basically check the previous iframe domains ;)

Ok, but why? It must be changed to https atomaticaly with this function https://github.com/rakshazi/picoFeed/blob/patch-1/lib/PicoFeed/Filter/Attribute.php#L370

:+1:

This whitelist is applied before it's moved to https, basically it just filters through all iframes and matches the URLs against this list, see:
https://github.com/rakshazi/picoFeed/blob/patch-1/lib/PicoFeed/Filter/Attribute.php#L222
which is executed before
https://github.com/rakshazi/picoFeed/blob/patch-1/lib/PicoFeed/Filter/Attribute.php#L226

If http or https were not defined in the iframe whitelist, they'd be discarded and never rewritten to https

oh, i understand now, thank you!

Btw, awesome job ;) thanks

authors: BernhardPosselt rakshazi

repo: fguillot/picoFeed


text:
adding the about section

Purpose/implementation Section
What changes are being implemented in this Pull Request?
Adding information to tell people what the course is about.
What was your approach?
Using the index file ... instead of the ch 1- so more like the structure that @avahoffman used for the cluster course instead of our ITN courses.
Tell potential reviewers what kind of feedback you are soliciting.
Let me know if you want anything different! :)

hmm spelling error report gives a 404


text:
Update manifest.json

Bump skodaconnect to 1.3.8
This Version is needed:
"Updated User-Agent in order to get code on par with recent Android and IOS apps.
Outdated User-Agent from older app version seems to be blocked now at token endpoints. This change is confirmed working with Enyaq owners."

please bump skodaconnect to 1.3.8

Thanks for reporting!

authors: fbuescher fhempy

repo: fhempy/fhempy


text:
Regex nya ke hapus  😂

@fiandev

Udah gw fix

Bug fixed

yatta 😊

authors: fiandev ryugenxd

repo: fiandev/jawa-language


text:
Add function, source and line number to log messages

Remove previous revisions - WIP

@sbernheim The tracing in and out of each function is not designed to replace stack traces, is designed to help with debugging
Would you prefer if I renamed the utility package, logutils and moved the file utility functions to a fileutils package?

The tracing in and out of functions allows a developers to follow the path taken when investigating issues and is only enabled at highest level of tracing

repo: fidelity/kraan


text:
Client Allocation Request for: Tung Vu

Client Allocation Questions
Core Information

Name: Tung Vu
Website / Social Media: https://github.com/vht210
DataCap Requested: 1TiB
Addresses to be Notarized: f3w6jw6moo7xqmy5v4acaljerlhqtwqef5yrwtf7x7orexco2k3vnhfhmjizhyd4uwu2tpqhskh2uh7rlzab2q
Notary Requested: s0nik42

No longer interest

No longer interest


text:
Add additional contributors

We want to add a few people for basic UI, docs, and description updates.
@eshon please list the GitHub accounts other than yourself that should be added.

eshon
smagdali
maciejwitowski

authors: bmann eshon

repo: filecoin-project/filsnap


text:
manual file sort

What feature or improvement do you think would benefit Files?
I wanted to suggest if you can to add a manual sort possibility (like to chose which file after which)
thank you for this amazing app, keep up the good work.
Requirements

This proposal will make it easier for sorting files
This proposal will also give the user the ability to customize more and more freely

Files Version
Version: 2.4.21.0 OS Version: 10.0.19045.2486
Windows Version
Windows 10
Comments
No response

This seem like it would be too hard to manager. Does the tag feature not work for you?

How would this work across sessions and what happens if you add more files to the folder?

repo: files-community/Files


text:
Bug: Unable to drag and drop any file onto .ahk files

Description
The drag-and-drop functionality seems to have a limitation, preventing the dragging and dropping of files with any file extension onto .ahk files.
I found a similar closed issue with .py files but that one has been fixed. Dragging and dropping doesn't seem to be an option.
Steps To Reproduce
Make an .ahk file
Try to drag any file onto it.
Requirements
It should allow me to drag and drop file onto .ahk files, but it currently does not. Essentially run that .ahk file with the filepath(s) as a parameter
Files Version
3.1.1.0
Windows Version
10.0.22631 Build 22631
Log File
debug.log

Thanks for the report

Fyi @antonioseet

can i solve this issue

what is knowledge required to solve the issue

; Enable drag-and-drop events
Gui +LastFound
Droplist := RegisterCallback("DropFiles")
DllCall("DragAcceptFiles", "Ptr", A_ScriptHwnd, "Int", 1)
; Create a simple GUI window
Gui, Margin, 10, 10
Gui, Add, Text, w300, Drag and Drop Files Here
Gui, Show, w320 h100, Drag-and-Drop Example
return
; Handle messages, including WM_DROPFILES
OnMessage(0x111, "WM_COMMAND")
; DropFiles subroutine
DropFiles(wParam, lParam) {
; Get the number of dropped files
FileCount := DllCall("DragQueryFile", "Ptr", wParam, "Int", 0xFFFFFFFF, "UInt", 0)
; Loop through each dropped file
Loop, %FileCount%
{
    ; Get the length of the file path
    FileLen := DllCall("DragQueryFile", "Ptr", wParam, "Int", A_Index - 1, "Ptr", 0, "Int", 0) + 1

    ; Get the file path
    VarSetCapacity(FilePath, FileLen)
    DllCall("DragQueryFile", "Ptr", wParam, "Int", A_Index - 1, "Str", FilePath, "Int", FileLen)

    ; Display the file path (you can modify this part as needed)
    MsgBox, Dropped File: %FilePath%
}

; Release resources
DllCall("DragFinish", "Ptr", wParam)

}
; GUI close event
GuiClose:
ExitApp
is it correct?

This is already being worked on

ok bro


text:
Request for Adding Details Column

What feature or improvement do you think would benefit Files?
When the layout is set to 'details,' please add columns to display the dimensions of images (width and height in pixels), the resolution, and the duration of videos and audio tracks.
I was searching for an app with a column layout feature for Windows and came across Files. I particularly love the design. However, since I frequently work with image and video data, it can be inconvenient when I can't switch to a detailed layout to view multiple files' information at once. I sincerely hope this can be addressed in a future update.
Requirements

This proposal will accomplish X
This proposal will accomplish Y
This proposal will accomplish Z

Files Version
3.6.0.0
Windows Version
10.0.19045.4780
Comments
No response

Thanks so much for your feedback! We’re keeping an eye on this in issue #8366. Feel free to subscribe to that issue for any updates.


text:
Right Click Animation Direction

If the mouse is on the upper half, the context menu is above the mouse cursor, but the animation is starting at the top instead of at the position, where the cursor is.
Is your feature request related to a problem? Please describe.
As far as i know, no
Describe the solution you'd like
It'd feel more natural if the animation would start from the cursors position upwards.
Describe alternatives you've considered
It'd also be possible to fade in the context menu without sliding it in, but it'd be less pleasant.
Additional context

This appears to be an issue with the WinUI control and there isn't anything we can do. The best option is to turn off the animation from the settings page.


text:
Uninstalled Files, now I can't use Explorer

Description
I just uninstalled Files into my Windows10 machine, I do rebooted the machine and I can't no longer use the Windows Explorer as it should. Instead I do get an error message: "Application not found".
How I can restore Windows Explorer back?
Steps To Reproduce
No response
Expected behavior
I expect to be able to use Windows Explorer againd after uninstalling Files.
Files Version
2.1.15
Windows Version
Windows10
Relevant Assets/Logs
No log file.

You'll need to run this script (make sure to save it as a ".reg" file):
https://raw.githubusercontent.com/files-community/Files/main/src/Files.Launcher/Assets/FilesOpenDialog/UnsetFilesAsDefault.reg
Please let us know if it solves the issue.

Thank you for the answer. The .reg file fixed the issue.

even after the script, win+e works, but it given an error Application not found

and i cant open any other folder... i ran the script BEFORE uninstalling, but still shows error.

I have the same issue. Just uninstalled it and now win+e gives me the Application not found error.
The link above isn't working either.

@bronze USE THE UPDATED SCRIPT.. thats old... @yaichenbaum replied and sent it
Here:
Windows Registry Editor Version 5.00
; Revert Default (new)
[HKEY_CLASSES_ROOT\Folder\shell\explore]
"LaunchExplorerFlags"=dword:00000018
"MultiSelectModel"="Document"
"ProgrammaticAccessOnly"=""
[HKEY_CLASSES_ROOT\Folder\shell\explore\command]
@=-
"DelegateExecute"="{11dbb47c-a525-400b-9e80-a54615a090c0}"
[HKEY_CLASSES_ROOT\Folder\shell\open]
"MultiSelectModel"="Document"
[HKEY_CLASSES_ROOT\Folder\shell\open\command]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,
00,5c,00,45,00,78,00,70,00,6c,00,6f,00,72,00,65,00,72,00,2e,00,65,00,78,00,
65,00,00,00
"DelegateExecute"="{11dbb47c-a525-400b-9e80-a54615a090c0}"
; Revert Default (old)
[HKEY_CURRENT_USER\SOFTWARE\Classes\Directory\shell]
@=-
[-HKEY_CURRENT_USER\SOFTWARE\Classes\Directory\shell\openinfiles]
; Revert Win+E
[-HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID{52205fd8-5dfb-447d-801a-d0b52f2e83e1}]
Copy paste above into a .reg file and execute, restart computer and done

authors: bronze gave92 rr-da-cat zohozer


text:
Code Quality: Move Resources dir to Assets

Summary
As the title.
PR Checklist

[ ] 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 #issue
[ ] 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?

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

[ ] Was this change approved?

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

Screenshots
None

Assets folder is mess and I’d like to get them have this simple structure:
Assets/
 Libraries/ (DLL and EXE files)
 Images/ (icon images)
 Resources/ (reg files and json files)

I usually view Assets as reserved for images and the like.

But those resources are already there except those json files.
the folder will look like after packaged:
Assets/
 AppTiles (app icons, no changes)
 Images (archive logos, fluent icons)
 Libraries (DLL,EXE)
 Resources (reg files, json files)

Current structure doesn’t provide identical folders for each purpose.
https://learn.microsoft.com/en-us/windows/uwp/app-resources/images-tailored-for-scale-theme-contrast#qualify-an-image-resource-for-scale-theme-and-contrast

In the future I want to put 7z DLL files in Libraries dir

For testing, we need to test the features that rely on the moved resources. This includes the details pane and properties window.

I tested these changes (added to the PR description) and I can confirm it's working as expected.


text:
🛑 Confluence is down

In e96e1a3, Confluence ($SECRET_SITE) was down:

HTTP code: 502
Response time: 640 ms

Resolved: Confluence is back up in d8efaa7.

repo: filii-lamberti/uptime


text:
Update shapeless to 2.3.6

Updates com.chuusai:shapeless from 2.3.3 to 2.3.6.
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.
Configure Scala Steward for your repository with a .scala-steward.conf file.
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 = "com.chuusai", artifactId = "shapeless" } ]

labels: library-update, semver-patch

Superseded by #179.

repo: finagle/finagle-mysql-shapes


text:
Move class definitions out of package objects

I mentioned this on Gitter but am creating an issue for more inclusive discussion.
I think it'd be a good idea to move all class (and trait and object) definitions that aren't implicit classes out of package objects, since having package$ prefixes on the JVM class names makes a number of things inconvenient (javap, Java interop, etc.).
This would be a breaking change but mostly (entirely?) source-compatible for Scala users. It'd be pretty straightforward to implement, and could even happen before 0.7.0 if people are on board.
Any thoughts?

+1

-Xlint says we're okay here after #292 and #295.

authors: BenWhitehead travisbrown

repo: finagle/finch


text:
关于无法显示实体的解决方案

首先感谢作者的付出，这几天试了一下感觉很实用。
只是高德地图功能升级后（仅限最近注册的KEY）无法显示标注点和行程了。对1.2.7版摸索了一番后，将第268-270行修改成：
if (result.info === 'ok') {           that._showMarker(result.locations[0],entity,color,type);         } else {           console.info("%c 地图加载异常:%o", "color: white; font-weight: bold; background: dimgray",result);         }
后得到高德地图返回“NVALID_USER_SCODE” 异常信息，通过查看高德API的“JSAPI key和安全密钥的使用”说明，我使用了第二个方法，在第4行追加下列代码后可以正常使用：
window._AMapSecurityConfig = {             securityJsCode:'您申请的安全密钥',         }

谢谢大佬！！！我最近也在搞这个，才发现作者好久没更新了，没啥编程基础，应该怎样快捷的修改这些代码啊？

修改了js代码，不生效，是什么情况

插眼，谢谢大佬付出

repo: fineemb/lovelace-cn-map-card


text:
07 Aug 2024 - Diversity Equity & Inclusion Special Interest Group Meeting

Date
20240807 - 12:00pm EST / 5pm GMT
Untracked attendees

Fullname, Affiliation, (optional) GitHub username
...

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes (including minutes from @eteridvalishvili and @Perelmuter )
[ ] #49 (Sergio) - call for additional GitHub task owners/maintainers
[ ] #52 (Rimma)
[ ] Grace Hopper Celebration updates (Paula): #56 #41 #53
[ ] #58 #60 (Paula)
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Meeting Info
Join Zoom Meeting
https://zoom.us/j/94969868675
Meeting ID: 949 6986 8675
Passcode: 184472

James McLeod / NatWest

Mimi Flynn / Morgan Stanley

authors: PaulaPaul mcleo-d mimiflynn

repo: finos/DEI-SIG


text:
Examples of feature disparities - Legend vs Rosetta for CDM?

Hi, has anyone used both Legend + Rosetta and faced problems with inconsistencies/feature disparities between the two DSLs? I am polling for prevalent issues to investigate.
This is part of a potential research project on the compatibility of using two DSLs to work with the CDM.
My current trajectory
Given I am new to FINOS, I'm very open to and actively seeking feedback!
TODO
Assess feature disparity between Pure and Rosetta:

[ ] 1. Explore "diff" approaches to compare transpiled Rosetta (from Pure) against the original Rosetta, and vice versa.

The purpose of this post is to gather input samples/test cases for this.

[ ] 2. Manually evaluate modeling capabilities of each DSL (via documentation review and domain-agnostic modeling tests). Unclear if this is helpful.
[ ] 3. Test Morphir as a target IR.

What I know so far + additional questions

The Legend/Pure -> Rosetta pipeline seems fleshed out.

I can transpile the Legend CDM back to Rosetta (using "New File Generation.."). This appears to solve #300 , as well as the code generator discussion in #311.

How do members typically deploy the rosettaTypes.txt output? Is this out of scope of the "Pure to Rosetta translation" problem?
What else might I be missing? (e.g., problems people face using the generated Rosetta?)

The Rosetta -> Legend/Pure pipeline looks less developed.

Per #650 (under "Other"), Rosetta CDM versions are not pushed regularly to Legend. The problem cited is "opaque expressions".

What are some examples of these "opaque expressions"?
Besides opaque expressions, are there other known bottlenecks (technical or otherwise) for regularly pushing Rosetta versions to Legend?

(Sidenote: I recently learned that the Legend CDM was updated last month to match the latest Rosetta CDM.)

ISDA review is required for all CDM changes (e.g., those made in Legend) pushed to the official Rosetta CDM.

From: #335

Is this review stage beyond the scope of DSL compatibility?
Is this review done at a purely logical level? Or are technical inconsistencies ironed out between DSLs?

I am looking into Morphir as a target IR and am just starting to explore how FpML fits into all this.

Hi @smsant - would recommend that you reach out to the FINOS Technical SteerCo to find out more. I think they engaged in a feature comparison analysis.

@beekemarie - sounds good, thanks for the guidance!

This issue 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 issue was closed because it has been inactive for 35 days. Please re-open if this issue is still relevant.

authors: beekemarie finos-admin smsant

repo: finos/legend


text:
Measurable Ratings: add a flattened hierarchy extractor

Description
Currently the extract just shows the immediate measurable.  Would be nice to use a dynamic 'n' wide, extract of all the parent measurable names.
Resourcing
We intend to contribute this feature

Waiting for #6870 to be merged first

repo: finos/waltz


text:
Can not sign in with Twitter

Hello
I follow all step on Firebase Auth document.
But when I sign in with Twitter, there is no action
When I try to call getCredetial method, this method does not response any event.
Please help me check this issue
Thank you so much

Please fill out the issue template.

repo: firebase/FirebaseUI-iOS


text:
io.grpc.Context and Firestore

Hi
I use Firestore and I just encountered the following: SEVERE [Catalina-utility-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@486b085d]) and a value of type [io.grpc.Context] (value [io.grpc.Context@5c653a4b]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
I read this thread https://github.com/firebase/firebase-admin-java/issues/237 and maybe I've missed something but I didn't see a solution to the above. Is there an update since 4 months ago?
Thanks

I see that @wilhuff has commented on #237. Closing this issue, since our position on this hasn't changed.

repo: firebase/firebase-admin-java


text:
Receiving invalid-argument error code instead of invalid-registration-token when sending push notification

Operating System version: Ubuntu 16.04
Firebase SDK version: firebase-admin 2.12.0 on Python 3.5.2
Firebase Product: messaging

Describe the problem
Hi there,
When I send a push notification using messaging.send with an invalid token I expect an invalid-registration-token error but and invalid-argument error is raised. The invalid token is generated adding an extra char at the end of the token. Is this the expected behavior? With the legacy HTTP API an invalid token error was returned.
Thanks
Relevant Code:
from firebase_admin import messaging
app = firebase_admin.get_app()
token = VALID_TOKEN+"a"

try:
    result = messaging.send(
        message=messaging.Message(
            notification=messaging.Notification(
                  title="Push",
                  body="message"
             ),
             token=push_id
         ),
         app=app)
except messaging.ApiCallError as error:
    assert error.code == "invalid-registration-token"

This is just the way the new FCM API reports errors. Here's the full response received from the server:
{
  "error": {
    "code": 400,
    "message": "Request contains an invalid argument.",
    "status": "INVALID_ARGUMENT",
    "details": [
      {
        "@type": "type.googleapis.com/google.firebase.fcm.v1.FcmError",
        "errorCode": "INVALID_ARGUMENT"
      },
      {
        "@type": "type.googleapis.com/google.rpc.BadRequest",
        "fieldViolations": [
          {
            "field": "message.token",
            "description": "Invalid registration token"
          }
        ]
      },
      {
        "@type": "type.googleapis.com/google.rpc.BadRequest",
        "fieldViolations": [
          {
            "field": "message.token",
            "description": "The registration token is not a valid FCM registration token"
          }
        ]
      },
      {
        "@type": "type.googleapis.com/google.rpc.DebugInfo",
        "detail": "[ORIGINAL ERROR] generic::invalid_argument: bad registration id data: foo-bar\ncom.google.apps.framework.request.StatusException: \u003ceye3 title='INVALID_ARGUMENT'/\u003e generic::INVALID_ARGUMENT: bad registration id data: foo-bar [google.rpc.error_details_ext] { details { type_url: \"type.googleapis.com/google.firebase.fcm.v1.FcmError\" value: \"\\010\\001\" } details { type_url: \"type.googleapis.com/google.rpc.BadRequest\" value: \"\\n+\\n\\rmessage.token\\022\\032Invalid registration token\" } details { type_url: \"type.googleapis.com/google.rpc.BadRequest\" value: \"\\nM\\n\\rmessage.token\\022\u003cThe registration token is not a valid FCM registration token\" } }"
      }
    ]
  }
}

If you want you can access this response, and parse it to get to the exact field violations:
try:
    messaging.send(msg)
except messaging.ApiCallError as ex:
    response = ex.detail.response # This is a requests.Response object
    response_data = response.text # Read the response as a string

repo: firebase/firebase-admin-python


text:
Firebase Version log message does not match SPM version

Description
Firebase 9.4.1 initializes and prints version 9.4.0 in both Crashlytics and Analytics. I assume the same is for other components but I don't use others.
I assume this is getting injected into the code based on the defines in the Package.swift
https://github.com/firebase/firebase-ios-sdk/blob/9.4.1/Package.swift#L22
Expected:
The version number printed to the system console should match the version of the swift package.
Actual:
The version number printed to the system console did NOT match the version of the swift package.
While I understand and acknowledge that the issue doesn't exist in the latest because 1.6.0 == 1.6.0, for future SPM tags, please please please, ensure the version printed in the logs reflects the actual version of the SDK.
Why does this matter? My QA team verifies our SPM integration versions (Firebase as an example) and when available, checks the SDK version logs with what we have documented as integrated. So as a dev lead I documented integration of 9.4.1, however, QA failed our SDK verification because the logs printed 9.4.0.
2022-09-14 09:53:54.692374-0500 ProcessName[3017:569038] [Firebase/Crashlytics] Version 9.4.0
2022-09-14 09:53:56.081405-0500 ProcessName[3017:569266] 9.4.0 - [FirebaseAnalytics][I-XXXXXXXXX] Analytics v.9.4.0 started
Reproducing the issue

Install Firebase SPM
Create a Firebase Config and setup the project per Firebase instructions
Initialize Firebase Crashlytics and Analytics in ApplicationDelegate
Read the log statements that get printed to Xcode outputs / console output

2022-09-14 09:53:54.692374-0500 ProcessName[3017:569038] [Firebase/Crashlytics] Version 9.4.0
2022-09-14 09:53:56.081405-0500 ProcessName[3017:569266] 9.4.0 - [FirebaseAnalytics][I-XXXXXXXXX] Analytics v.9.4.0 started
Firebase SDK Version
9.4.1
Xcode Version
Xcode 14.0 Public
Installation Method
Swift Package Manager
Firebase Product(s)
Analytics, Crashlytics
Targeted Platforms
iOS
Relevant Log Output
2022-09-14 09:53:54.692374-0500 ProcessName[3017:569038] [Firebase/Crashlytics] Version 9.4.0
2022-09-14 09:53:56.081405-0500 ProcessName[3017:569266] 9.4.0 - [FirebaseAnalytics][I-XXXXXXXXX] Analytics v.9.4.0 started

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

If using CocoaPods, the project's Podfile.lock
n/a

Thanks for raising this. We did not update https://github.com/firebase/firebase-ios-sdk/blob/master/Package.swift#L22 in 9.4.1. I'll leave this open to update our patch release process to do so.

updated the release process docs - internal cl/521942646

repo: firebase/firebase-ios-sdk


text:
Eliminate redundant gtest dependency.

googletest/CMakeLists.txt (which defines the gtest and gtest_main target
libraries) suggests that 'User tests should link with one of them'.

Sounds like we're happy with it as is. I'll abandon this PR.


text:
Generate JavaDocs

This project doesn't have any JavaDocs, which makes it very hard to navigate this project, and isn't in line with other Android/Google APIs.
JavaDocs should be generated and hosted on developer.google.com, firebase.google.com, or GitHub Pages.

In April 2019 we announced that Firebase Job Dispatcher would be deprecated today, April 7th 2020.  For this reason we are going to close all open issues and archive the repository.  We will also stop supporting FJD for new app installations (such as those targeting sdk versions greater than Android Q).  Existing apps that rely on FJD should continue to function as usual.
While we will no longer work on FJD, we encourage you to migrate to Work Manager which is a superior tool and fully supported by the Android team.
Thank you for taking the time to try the library and provide this feedback.  We sincerely appreciate your effort and we apologize for not addressing it in time.

authors: samtstern tjohns

repo: firebase/firebase-jobdispatcher-android


text:
[Bug] Problem with dependency resolution for Android and Unity 6000.0.1

Description
I have an incompatibility between Unity 6 Preview (6000.0.1f1) and Firebase auto dependency resolution.
The auto resolution just deletes all Firebase dependencies for Android from the gradle templates and deletes the generated maven package - so that the application builds without the Firebase binaries!
Reproducing the issue
I had a working projec t in 2023.2.nn.
Upgraded to 6000.0.1 in the usual way.
Build for Android and the auto-resolution deleted the dependencies
Firebase Unity SDK Version
11.9.0
Unity editor version
6000.0.1f1
Installation Method
Unity Package Manager
Problematic Firebase Component(s)
All
Other Firebase Component(s) in use
No response
Additional SDKs you are using
No response
Targeted Platform(s)
Android
Unity editor platform
Windows
Scripting Runtime
IL2CPP
Release Distribution Type
Pre-built SDK from https://firebase.google.com/download/unity
Relevant Log Output
No response
If using CocoaPods for Apple platforms, the project's Podfile.lock

Expand Podfile.lock snippet

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

Hi @runette, thanks for reaching out. I noticed a different behavior when I tried using one of our quickstarts in Unity with version 2022.3.24f1 and then opening it with version 6000.0.0f1. Initially, I've only encountered an issue with Namespace not specified, once I've added the namespace in the mainTemplate.gradle. The build was able to run successfully.
That said, could you specify the steps you took in order to reproduce this behavior?

Hi @runette, thanks for reaching out. I noticed a different behavior when I tried using one of our quickstarts in Unity with version 2022.3.24f1 and then opening it with version 6000.0.0f1. Initially, I've only encountered an issue with Namespace not specified, once I've added the namespace in the mainTemplate.gradle. The build was able to run successfully.
That said, could you specify the steps you took in order to reproduce this behavior?

as stated above :
I had a working projec t in 2023.2.nn.
Upgraded to 6000.0.1 in the usual way.
Build for Android and the auto-resolution deleted the dependencies
I do notice that I am using 6000.0.1 and not 6000.0.0 as you stated.
Also - I am not sure what you mean about putting the namespace in the mainTemplate.gradle. I have not edited the mainTemplate.gradle at all.

@argzdev So - I created a test project with the following steps :
1 Created a brand new totally standard 2023.2 URP 3D project - you can see it here https://github.com/runette/Firebase_Test
2 Added the Firebase SDK - just for your info the SDK is loaded as a Git Submodule from this git repo https://sync.virgis.co.uk/ViRGiS/Firebase_SDK and is 11.9.0
3 Added a small package of mine that provides login - see https://github.com/LiSe-Team/LiSe-Unity-Client
4 accepted all of the Firebase recommendations - including auto-resolution
This worked in 2023.2 as an Android application - as you see edm4u has loaded the maven package as expected.
4 Did a standard upgrade to Unity 6000.0.1f1.
5 The results are in the "6000" banch - see https://github.com/runette/Firebase_Test/tree/6000
6 Did an android build
As you can see edm4u has deleted the maven package and the dependencies in the gradle files. The build did not work because the dependencies were not loaded.
There is definitely a problem

Hey @runette, thanks for the extra details. Could you change the visibility of your repo to public so I can try it. So far, I've been unsuccessful testing with different versions 2022 and 2023 then changing to 6000 when trying to reproduce the behavior. By the way, have you tested using the Android Resolver > Delete Resolved Libraries, and then Android Resolver > Force Resolve if that makes any difference?

Hey @runette, thanks for the extra details. Could you change the visibility of your repo to public so I can try it.

Sorry about that - done now

By the way, have you tried using the Android Resolver > Delete Resolved Libraries, and then Android Resolver > Force Resolve if that makes any difference?

Tried that - no change

Okay, thanks for trying that. I'll try and investigate this further.

I'm able to reproduce the behavior now. After running a few tests, it looks like the issue might be due to the installation method. Adding the tgz file e.g. com.google.firebase.app-11.9.0.tgz is causing the EDM4U to malfunction. Using the .unitypackage works correctly. I'll go ahead and inform our engineering team to take a look into this. Thanks!

I noticed the 12.0.0 of the SDK had been released and I tried that but it seems to have the same behaviour.

hey @runette, maybe
[https://github.com/AppLovin/AppLovin-MAX-Unity-Plugin/issues/376#issuecomment-2121341734](this helps)

hey @runette, maybe this helps
https://github.com/AppLovin/AppLovin-MAX-Unity-Plugin/issues/376#issuecomment-2121341734

I think the problems are different, since this is a problem specifically with edm4u.
To be clear, I can build the project by turning edm4u off and using the old dependencies. The project also builds with edm4u turned on, it just does not run because the firebase binaries are not loaded.

authors: argzdev itkdo runette

repo: firebase/firebase-unity-sdk


text:
🐛 [firebase_auth] Crash on Motorola's phones

Bug report
Describe the bug
In our crashlytics report we can see sone early crashes that seems to be related with this library
Additional context
Logs:
Fatal Exception: java.lang.OutOfMemoryError: Failed to allocate a 75497480 byte allocation with 25165824 free bytes and 27MB until OOM, target footprint 264839928, growth limit 268435456
       at java.util.Arrays.copyOf(Arrays.java:3257)
       at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
       at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:649)
       at java.lang.StringBuilder.append(StringBuilder.java:203)
       at org.json.JSONStringer.string(JSONStringer.java:354)
       at org.json.JSONStringer.value(JSONStringer.java:261)
       at org.json.JSONArray.writeTo(JSONArray.java:616)
       at org.json.JSONStringer.value(JSONStringer.java:242)
       at org.json.JSONObject.writeTo(JSONObject.java:734)
       at org.json.JSONObject.toString(JSONObject.java:702)
       at com.google.firebase.auth.internal.zzbg.zzd(zzbg.java:180)
       at com.google.firebase.auth.FirebaseAuth.zzH(FirebaseAuth.java:116)
       at com.google.firebase.auth.zzo.zza(zzo.java:3)
       at com.google.android.gms.internal.firebase-auth-api.zzrv.zzb(zzrv.java:31)
       at com.google.android.gms.internal.firebase-auth-api.zzuh.zzj(zzuh.java)
       at com.google.android.gms.internal.firebase-auth-api.zzue.zzn(zzue.java:33)
       at com.google.android.gms.internal.firebase-auth-api.zztg.zzn(zztg.java:2)
       at com.google.android.gms.internal.firebase-auth-api.zzqe.zzb(zzqe.java:4)
       at com.google.android.gms.internal.firebase-auth-api.zzup.zza(zzup.java:140)
       at com.google.android.gms.internal.firebase-auth-api.zztv.zzf(zztv.java:20)
       at com.google.android.gms.internal.firebase-auth-api.zzrl.zzp(zzrl.java:18)
       at com.google.android.gms.internal.firebase-auth-api.zzth.zzj(zzth.java:26)
       at com.google.android.gms.internal.firebase-auth-api.zzrv.zzc(zzrv.java:11)
       at com.google.android.gms.internal.firebase-auth-api.zzui.run(zzui.java:8)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at java.lang.Thread.run(Thread.java:923)

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.3, on macOS 12.4 21F79 darwin-x64, locale en-IT)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2022.1.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2022.1.3)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.17.5
Flutter SDK 3.0.3
checkin 1.0.0+1

dependencies:
- badges 2.0.3 [flutter]
- bloc 8.0.3 [meta]
- cached_network_image 3.2.1 [flutter flutter_cache_manager octo_image cached_network_image_platform_interface cached_network_image_web]
- cloud_firestore 3.1.17 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cloud_functions 3.2.16 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- collection 1.16.0
- crypto 3.0.1 [collection typed_data]
- equatable 2.0.3 [collection meta]
- firebase_analytics 9.1.9 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 3.3.19 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.17.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 2.8.1 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_dynamic_links 4.2.5 [firebase_core firebase_core_platform_interface firebase_dynamic_links_platform_interface flutter meta plugin_platform_interface]
- firebase_messaging 11.4.1 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_storage 10.2.17 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- fluro 2.0.3 [flutter]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_bloc 8.0.1 [flutter bloc provider]
- flutter_form_builder 7.2.1 [flutter intl collection]
- flutter_image_compress 1.1.0 [flutter]
- flutter_linkify 5.0.2 [flutter linkify]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math]
- flutter_stripe 3.0.2 [flutter stripe_android stripe_ios stripe_platform_interface]
- flutter_svg 1.1.0 [flutter meta path_drawing vector_math xml]
- form_builder_validators 8.1.1 [flutter flutter_localizations intl collection]
- google_fonts 3.0.1 [flutter http path_provider crypto]
- google_sign_in 5.3.2 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- http 0.13.4 [async http_parser meta path]
- i18n_extension 5.0.0 [sprintf args analyzer gettext_parser equatable intl flutter]
- iban 1.0.1 [mod97]
- image_cropper 2.0.3 [flutter image_cropper_platform_interface image_cropper_for_web]
- image_picker 0.8.5+3 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_platform_interface]
- json_annotation 4.5.0 [meta]
- launch_review 3.0.1 [flutter]
- logger 1.1.0
- open_mail_app 0.4.5 [platform url_launcher flutter]
- package_info_plus 1.4.2 [flutter package_info_plus_platform_interface package_info_plus_linux package_info_plus_macos package_info_plus_windows package_info_plus_web]
- platform 3.1.0
- pub_semver 2.1.1 [collection meta]
- qr_flutter 4.0.0 [flutter qr]
- rx_shared_preferences 3.0.0 [flutter shared_preferences rx_storage rxdart_ext meta]
- share_plus 4.0.6 [meta mime flutter share_plus_platform_interface share_plus_linux share_plus_macos share_plus_windows share_plus_web]
- shared_preferences 2.0.15 [flutter shared_preferences_android shared_preferences_ios shared_preferences_linux shared_preferences_macos shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- shimmer 2.0.0 [flutter]
- sign_in_with_apple 3.3.0 [flutter meta sign_in_with_apple_platform_interface sign_in_with_apple_web]
- table_calendar 3.0.6 [flutter intl simple_gesture_detector]
- timeago 3.2.2
- url_launcher 6.1.2 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 3.0.6 [crypto]
- vector_math 2.1.2

dev dependencies:
- bloc_test 9.0.3 [bloc diff_match_patch meta mocktail test]
- build_runner 2.1.11 [args async analyzer build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_driver 0.0.0 [file flutter flutter_test fuchsia_remote_debug_protocol path meta vm_service webdriver archive async boolean_selector characters charcode clock collection crypto matcher material_color_utilities platform process source_span stack_trace stream_channel string_scanner sync_http term_glyph test_api typed_data vector_math]
- flutter_launcher_icons 0.9.2 [args image path yaml]
- flutter_native_splash 2.2.2 [args flutter flutter_web_plugins image js lint meta path universal_io xml yaml]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]
- freezed 2.0.3+1 [analyzer build build_config collection meta source_gen freezed_annotation json_annotation]
- integration_test 0.0.0 [flutter flutter_driver flutter_test path vm_service archive async boolean_selector characters charcode clock collection crypto fake_async file matcher material_color_utilities meta source_span stack_trace stream_channel string_scanner sync_http term_glyph test_api typed_data vector_math webdriver]
- json_serializable 6.2.0 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]
- mockito 5.2.0 [analyzer build code_builder collection dart_style matcher meta path source_gen test_api]
- mocktail 0.3.0 [collection matcher test]
- stack_trace 1.10.0 [path]

transitive dependencies:
- _fe_analyzer_shared 38.0.0 [meta]
- analyzer 3.4.1 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.1.11 [crypto path]
- args 2.3.1
- async 2.8.2 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 2.3.0 [analyzer async convert crypto glob logging meta path]
- build_config 1.0.0 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 3.1.0 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.0.9 [analyzer async build crypto graphs logging path package_config pool pub_semver stream_transform yaml]
- build_runner_core 7.2.3 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta path package_config pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.3.2 [built_collection collection fixnum meta]
- cached_network_image_platform_interface 1.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.0.1 [flutter flutter_cache_manager cached_network_image_platform_interface]
- characters 1.2.0
- charcode 1.3.1
- checked_yaml 2.0.1 [json_annotation source_span yaml]
- clock 1.1.0
- cloud_firestore_platform_interface 5.5.7 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 2.6.16 [cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- cloud_functions_platform_interface 5.1.7 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 4.2.15 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- code_builder 4.1.0 [built_collection built_value collection matcher meta]
- convert 3.0.2 [typed_data]
- coverage 1.2.0 [args logging package_config path source_maps stack_trace vm_service]
- cross_file 0.3.3+1 [js meta]
- dart_style 2.2.3 [analyzer args path pub_semver source_span]
- diff_match_patch 0.4.1
- disposebag 1.5.0 [meta collection]
- fake_async 1.3.0 [clock collection]
- ffi 1.2.1
- file 6.1.2 [meta path]
- firebase_analytics_platform_interface 3.1.7 [firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.4.0+14 [firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 6.2.7 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 3.3.16 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.4.0 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.6.4 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.2.7 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_dynamic_links_platform_interface 0.2.3+3 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 3.5.1 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 2.4.1 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_storage_platform_interface 4.1.7 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.2.16 [async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- fixnum 1.0.1
- flutter_blurhash 0.7.0 [flutter]
- flutter_cache_manager 3.3.0 [clock collection file flutter http path path_provider pedantic rxdart sqflite uuid]
- flutter_plugin_android_lifecycle 2.0.6 [flutter]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- freezed_annotation 2.0.3 [collection json_annotation meta]
- frontend_server_client 2.1.3 [async path]
- fuchsia_remote_debug_protocol 0.0.0 [process vm_service file meta path platform]
- gettext_parser 0.2.0
- glob 2.0.2 [async collection file path string_scanner]
- google_sign_in_android 5.2.8 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.3.1 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.1.3 [flutter quiver]
- google_sign_in_web 0.10.1+2 [flutter flutter_web_plugins google_sign_in_platform_interface js]
- graphs 2.1.0 [collection]
- http_multi_server 3.2.0 [async]
- http_parser 4.0.1 [collection source_span string_scanner typed_data]
- image 3.2.0 [archive meta xml]
- image_cropper_for_web 0.0.4 [flutter flutter_web_plugins image_cropper_platform_interface js]
- image_cropper_platform_interface 2.0.0 [flutter plugin_platform_interface http]
- image_picker_android 0.8.5 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- image_picker_for_web 2.1.8 [flutter flutter_web_plugins image_picker_platform_interface]
- image_picker_ios 0.8.5+5 [flutter image_picker_platform_interface]
- image_picker_platform_interface 2.5.0 [cross_file flutter http plugin_platform_interface]
- intl 0.17.0 [clock path]
- io 1.0.3 [meta path string_scanner]
- js 0.6.4
- linkify 4.1.0
- lint 1.8.2
- logging 1.0.2
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.4
- meta 1.7.0
- mime 1.0.2
- mod97 1.0.0
- nested 1.0.0 [flutter]
- node_preamble 2.0.1
- octo_image 1.0.2 [flutter flutter_blurhash]
- package_config 2.0.2 [path]
- package_info_plus_linux 1.0.5 [package_info_plus_platform_interface flutter path]
- package_info_plus_macos 1.3.0 [flutter]
- package_info_plus_platform_interface 1.0.2 [flutter meta plugin_platform_interface]
- package_info_plus_web 1.0.5 [flutter flutter_web_plugins http meta package_info_plus_platform_interface]
- package_info_plus_windows 1.0.5 [package_info_plus_platform_interface ffi flutter win32]
- path 1.8.1
- path_drawing 1.0.0 [vector_math meta path_parsing flutter]
- path_parsing 1.0.0 [vector_math meta]
- path_provider 2.0.10 [flutter path_provider_android path_provider_ios path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- path_provider_android 2.0.14 [flutter path_provider_platform_interface]
- path_provider_ios 2.0.9 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.7 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.6 [flutter path_provider_platform_interface]
- path_provider_platform_interface 2.0.4 [flutter platform plugin_platform_interface]
- path_provider_windows 2.0.7 [ffi flutter path path_provider_platform_interface win32]
- pedantic 1.11.1
- petitparser 5.0.0 [meta]
- plugin_platform_interface 2.1.2 [meta]
- pool 1.5.0 [async stack_trace]
- process 4.2.4 [file path platform]
- provider 6.0.3 [collection flutter nested]
- pubspec_parse 1.2.0 [checked_yaml collection json_annotation pub_semver yaml]
- qr 2.1.0 [meta]
- quiver 3.1.0 [matcher]
- rx_storage 2.0.0 [rxdart_ext disposebag meta stack_trace]
- rxdart 0.27.4
- rxdart_ext 0.2.2 [rxdart meta stack_trace path]
- share_plus_linux 3.0.0 [share_plus_platform_interface file flutter meta url_launcher]
- share_plus_macos 3.0.1 [share_plus_platform_interface flutter]
- share_plus_platform_interface 3.0.3 [flutter meta mime plugin_platform_interface]
- share_plus_web 3.0.1 [share_plus_platform_interface url_launcher flutter flutter_web_plugins meta]
- share_plus_windows 3.0.1 [share_plus_platform_interface flutter meta url_launcher]
- shared_preferences_android 2.0.12 [flutter shared_preferences_platform_interface]
- shared_preferences_ios 2.1.1 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.1.1 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_macos 2.0.4 [flutter shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.0.0 [flutter]
- shared_preferences_web 2.0.4 [flutter flutter_web_plugins shared_preferences_platform_interface]
- shared_preferences_windows 2.1.1 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- shelf 1.3.0 [async collection http_parser path stack_trace stream_channel]
- shelf_packages_handler 3.0.0 [path shelf shelf_static]
- shelf_static 1.1.0 [convert http_parser mime path shelf]
- shelf_web_socket 1.0.1 [shelf stream_channel web_socket_channel]
- sign_in_with_apple_platform_interface 1.0.0 [flutter plugin_platform_interface meta]
- sign_in_with_apple_web 1.0.1 [flutter flutter_web_plugins sign_in_with_apple_platform_interface js]
- simple_gesture_detector 0.2.0 [flutter]
- sky_engine 0.0.99
- source_gen 1.2.2 [analyzer async build dart_style glob meta path source_span yaml]
- source_helper 1.3.2 [analyzer collection source_gen]
- source_map_stack_trace 2.1.0 [path stack_trace source_maps]
- source_maps 0.10.10 [source_span]
- source_span 1.8.2 [collection path term_glyph]
- sprintf 6.0.0
- sqflite 2.0.2+1 [flutter sqflite_common path]
- sqflite_common 2.2.1+1 [synchronized path meta]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.0 [charcode source_span]
- stripe_android 3.0.0 [flutter]
- stripe_ios 3.0.0 [flutter]
- stripe_platform_interface 3.0.1 [flutter freezed_annotation json_annotation meta plugin_platform_interface]
- sync_http 0.3.0
- synchronized 3.0.0+2
- term_glyph 1.2.0
- test 1.21.1 [analyzer async boolean_selector collection coverage http_multi_server io js node_preamble package_config path pool shelf shelf_packages_handler shelf_static shelf_web_socket source_span stack_trace stream_channel typed_data web_socket_channel webkit_inspection_protocol yaml test_api test_core]
- test_api 0.4.9 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- test_core 0.4.13 [analyzer async args boolean_selector collection coverage frontend_server_client glob io meta package_config path pool source_map_stack_trace source_maps source_span stack_trace stream_channel vm_service yaml matcher test_api]
- timing 1.0.0 [json_annotation]
- typed_data 1.3.0 [collection]
- universal_io 2.0.4 [collection crypto meta typed_data]
- url_launcher_android 6.0.17 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.0.17 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.1 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.1 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.0.5 [flutter plugin_platform_interface]
- url_launcher_web 2.0.11 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.1 [flutter url_launcher_platform_interface]
- vm_service 8.2.2
- watcher 1.0.1 [async path]
- web_socket_channel 2.2.0 [async crypto stream_channel]
- webdriver 3.0.0 [archive matcher path stack_trace sync_http]
- webkit_inspection_protocol 1.1.0 [logging]
- win32 2.6.1 [ffi]
- xdg_directories 0.2.0+1 [meta path process]
- xml 6.1.0 [collection meta petitparser]
- yaml 3.1.1 [collection source_span string_scanner]

@nerder
This looks similar to https://github.com/firebase/flutterfire/issues/8444 for which the fix was made in native firebase android sdk. See https://github.com/firebase/flutterfire/issues/8444#issuecomment-1175754173 for more details.

authors: darshankawar nerder

repo: firebase/flutterfire


text:
Camera capture returns null.

If you pass EXTRA_OUTPUT with a URI to write to, it will return a null intent. Anyone else having this problem? Using a Samsung.

Cleaning up issue fixed in upcoming v2.

repo: firebase/friendlypix-android


text:
Auto-restrict commenting N days after issue close

We often get new comments on super-old issues with users encountering similar problems. They comment on the old thread and either someone happens to notice it or not, and it gets handled or not.
It would be nice as an option of oss-bot to have it automatically restrict comments N days after an issue is closed and post a message something like:

This issue has been marked as closed and is now closed for comments. If you are experiencing a similar issue, please file it as a new report with all relevant details.

@mbleigh this is already supported, if you look at the config internally this is the lock_days param and we're already using it on some of our SDKs.
For example:
https://github.com/firebase/firebase-ios-sdk/issues/7657#event-4549706960
Just let me know if you want this enabled on a repo you manage.

authors: mbleigh samtstern

repo: firebase/oss-bot


text:
Android notification icon when app background

Hi ,
How can I change notification icon and icon area's color when my app in background. Also, I open app and send push,Then onMessageReceived called and I create my custom notification.
Thanks

Hi @tekinarslan you cannot use FCM to set the notification icon at this time, but this is a know issue and the team is working on a fix.

Does this work by now? I only find sources on how to set the default notification icon but not on how to set individual icons.

@einicher You can set the notification icon to any resource in your application via the API (reference). The default notification icon is used when no icon is set in the notification message.

Any resource means, when i have a messages.png icon in my drawable folders and i set icon to messages.png it should work? Cause it does not.

@einicher for example in the sample app, if you remove the default notification metadata from the AndroidManifest.xml then send a notification message without specifying the icon eg:
{
	"message": {
		"topic": "news",
		"notification": {
			"title": "Breaking News",
			"body": "Catch up on breaking news stories."
		}
	}
}

The launcher icon is used.
However if you add the icon as a notification override specifying the resource ic_stat_ic_notification which represents ic_stat_ic_notification.png eg:
{
	"message": {
		"topic": "news",
		"notification": {
			"title": "Breaking News",
			"body": "Catch up on breaking news stories."
		},
		"android": {
			"notification": {
				"icon": "ic_stat_ic_notification"
			}
		}
	}
}

The resource image is used as the icon.

authors: einicher kroikie tekinarslan

repo: firebase/quickstart-android


text:
Get FCM token without using Firebase SDK

Is there a way having the firebase apiKey, to get the registering serviceworker IID_TOKEN? (without using firebase libraries I mean.. with a fetch)
From javascript in a webapp I use:
iid_token=await firebase.messaging().getToken()
Is there a way to do the same without the firebase libraries?
I am trying to code a very minmal app.
Thanks.

No answer???
Today it seems I can't even get the token using iid_token=await firebase.messaging().getToken()
The promise stays pending :(

You may be able to do this by following the Chrome docs: https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web#sending_a_push_message
@kroikie any tips?

/
Details

authors: Zibri backendaumenta jhuleatt

repo: firebase/quickstart-js


text:
App initializer installations not found, failed to enable.

[REQUIRED] Please fill in the following fields:

Unity editor version: 2019.4.27f1
Firebase Unity SDK version: 8.8.0
Source you installed the SDK: .unitypackage
Problematic Firebase Component: installations
Other Firebase Components in use: Analytics、Messaging、Crashlytics、RemoteConfig
Additional SDKs you are using:  No Others
Platform you are using the Unity editor on: Mac
Platform you are targeting: Android
Scripting Runtime: IL2CPP

[REQUIRED] Please describe the question here:
Hello!  Firebase components in use run correct, but when i use the installations, firebsae log print "Enable module 'installations' for 'Firebase.Installations.FirebaseInstallations, Firebase.Installations'" and "App initializer installations not found, failed to enable",  thanks for your reply.

In order to identify the cause of this behavior, could you provide a minimal, reproducible example along with the complete steps to replicate the issue?

Hi@paulinon,  in order to replicate the issue, i  just create a empty unity project and import the installations.unitypackage, could i need to call some initiate method?

Thanks for the additional information, @WikyWu. Did you remember to add the google-services.json file for your app in your Unity project? It's possible that this is the cause of your issue. After performing this step on my end, the initialization became successful.

Thanks for the additional information, @WikyWu. Did you remember to add the google-services.json file for your app in your Unity project? It's possible that this is the cause of your issue. After performing this step on my end, the initialization became successful

Thanks for the additional information, @WikyWu. Did you remember to add the google-services.json file for your app in your Unity project? It's possible that this is the cause of your issue. After performing this step on my end, the initialization became successful.

Thanks for your attention. The json file i have put in the unity project, also i have added the SHA1 certificate fingerprint, unfortunately, the same log has printed.

HI @WikyWu,
To be more specific, I was able to encounter logs saying that initialization was unsuccessful, but after a few seconds, new logs appeared saying that initialization was successful. Are you facing this similar behavior?

@paulinon, i print the all logs in the log.txt, hope it can be used. Thanks!
log.txt

Thanks for the additional information, @WikyWu. It's possible that one or more of your libraries were disabled or deleted from your project. Could you verify if your FirebaseCppInstallations.dll is present and has both Editor and Standalone selected? Additionally, are these logs the output of just having the Installations package in an empty Unity project?

Thanks for the additional information, @WikyWu. It's possible that one or more of your libraries were disabled or deleted from your project. Could you verify if your FirebaseCppInstallations.dll is present and has both Editor and Standalone selected? Additionally, are these logs the output of just having the Installations package in an empty Unity project?

Hi @paulinon, i just import the installations package in an empty unity project, both Editor and Standalone selected. . Thank you very much！

Hi @WikyWu,
Could you try if updating the Unity editor makes a difference (latest LTS Release is version 2020.3.32f1)? If it doesn't, please share the steps you've taken in retrieving your logs.

please share the steps you've taken in retrieving your logs.

Hi @paulinon, i use the 2019.4.27.f1 LTS Release Unity editor to program, updating will cause much problem. The steps i have taken:

Get the json file and put in unity asssets
Import the Installations.unitypackage
Android -> force resolve -> resolution succeed
Call method FirebaseApp.LogLevel = LogLevel.Verbose and FirebaseApp.CheckAndFixDependenciesAsync().ContinueWith
Run the unity project will get the logs
Import android project- > tag:firebase -> also get the logs

Thanks for the additional context, @WikyWu. I was able to replicate the issue you're facing using the steps you've listed. I'll let the team know about this, and you may refer to this thread for updates. For now, I'll be marking this as a bug.

Thanks for the additional context, @WikyWu. I was able to replicate the issue you're facing using the steps you've listed. I'll let the team know about this, and you may refer to this thread for updates. For now, I'll be marking this as a bug.

Thank you very much @paulinon , looking forward to your reply！

Hi @WikyWu, I'd like to check is there any functional affect to your app besides the log info?

I'd like to check is there any functional affect to your app besides the log info?

Hello @cynthiajoan , i can't get the installations token with the follow method:
public class Sample : MonoBehaviour
{
// Start is called before the first frame update
void Start()
{
// Initialize Firebase
FirebaseApp.LogLevel = LogLevel.Verbose;
FirebaseApp.CheckAndFixDependenciesAsync().ContinueWith(task => {
var dependencyStatus = task.Result;
if (dependencyStatus == DependencyStatus.Available)
{
// Create and hold a reference to your FirebaseApp,
// where app is a Firebase.FirebaseApp property of your application class.
FirebaseApp app = FirebaseApp.DefaultInstance;
Debug.Log("this ensures that Firebase is initialized");
// Set a flag here for indicating that your project is ready to use Firebase.
FirebaseInstallations.DefaultInstance.GetTokenAsync(true).ContinueWith(
task1 =>
{
if(task1.IsCompleted){
Debug.Log($"The token is {task1.Result}");
}
});
}
else
{
Debug.LogError(String.Format("Could not resolve all Firebase dependencies: {0}",dependencyStatus));
// Firebase Unity SDK is not safe to use here.
}
});
}
}
The Log print

Hello@cynthiajoan @paulinon, i just create an new firebase project and replace the json file and package name, surprised me that the project gets succeed result and i can get the installations token,  but the log "App initializer installations not found, failed to enable" also printed, i am confused and don't know why.

Thank you very much! @cynthiajoan @paulinon

authors: WikyWu cynthiajoan paulinon

repo: firebase/quickstart-unity


text:
Add More Info to Readme

Hello, I cannot find information explaining how to utilize this repo neither in the readme nor in the snippets.md.
I believe this repository would benefit from some elaboration. I wanted to offer a PR myself, but I can't even figure out how to implement this, or if this hosts to a VSC extension.
Thank you either way, I have added this potent repo to my watch list. 🙇🏼♂

Totally agree with you.

Totally agree with you.

I suppose further examination of the package.json and a few .js files reveals more about the dependencies, installation process and utilization though I'm not certain of the feasibility for implementations in it's current state which seems to be strapped to some ES5 rendering. Maybe a list of important tools and links to documentation of the use could also help brighten this project.
Either way, thank you @inglesuniversal for the encouragement on weighing in here.

I suppose further examination of the package.json and a few .js files reveals more about the dependencies, installation process and utilization though I'm not certain of the feasibility for implementations in it's current state which seems to be strapped to some ES5 rendering. Maybe a list of important tools and links to documentation of the use could also help brighten this project.
Either way, thank you @inglesuniversal for the encouragement on weighing in here.

I added some explanation in the README, does that help? Every code snippet in this repo is present in the Firebase documentation so there is no need to read or browse this repo directly.

authors: JasonHoku inglesuniversal samtstern

repo: firebase/snippets-web


text:
Integrate with Travis

As soon as we have tests (issue #34) we want to integrate with Travis https://travis-ci.org/
Honza

https://github.com/firebug/pixel-perfect/commit/f803658c440af15f9a544c9901dde39967f435c9
https://github.com/firebug/pixel-perfect/commit/44981564803a015fbb8c87abff340d816f420437
Honza

Travis builds are available:
https://travis-ci.org/firebug/pixel-perfect
Honza

repo: firebug/pixel-perfect


text:
Revert "Improve capa checkout in sync workflow"

Seems like something's off here
Reverts fireeye/capa-rules#40

it seems the token is needed. I'll send another one. It is the same problem as in https://github.com/fireeye/capa-testfiles.

repo: fireeye/capa-rules


text:
Keeping the scale and rotate state after rebuild

Hi,
I am using the PhotoView widget inside a container and drawing some line in my case and this change cause rebuilds.
Is there any way the keep the scale and rotate state after rebuilds?

Yah, use controllers.


text:
WG config download naming pattern..

When downloading device configuration files for use in the Wireguard client, they download in the name of firezone_fq_dn.conf and import into Wireguard as such.
I would like to suggest that if the device profile is firezone-rocks it should download as firezone-rocks.conf
This would allow the matching of device profiles to configuration files.
Possibly including the Updated date/timestamp in the configuration name as well?
firezone-rocks-022720221413.conf for example..
Thank you in advance.

Thanks for the suggestion! This makes sense -- we were actually considering this naming scheme off the bat. I'll queue this up into our backlog.

If you've never seen this.. https://github.com/StreisandEffect/streisand
You could learn a lot from them.. it was an amazing project..
This is where I initially exposed to the naming patterns..
https://github.com/StreisandEffect/streisand/blob/af5eb7dac157a2416ea64cba96cf32f7f505d9ff/playbooks/roles/common/files/english.txt
This random "naming-pattern.conf" was consistent throughout the openvpn, shadowsocks, wireguard, etc. services offered..
I cannot find Streisand screenshots to share..

Fixed in #495 and being released imminently with 0.3.0

authors: bcookatpcsd jamilbk

repo: firezone/firezone


text:
Delete ci file

test release drafter

oops wrong repo.


text:
Check if a snowflake column exists before altering its comment

Resolves #3039
Description

This PR modifies the "alter column comment" snowflake macro by breaking each column comment into a separate DDL statement, so that we can check that the column exists before attempting to  comment on it
This helps avoid the confusing scenario of getting a database error for a column that doesn't appear in your model's .sql file
I couldn't find an equivalent to comment if exists in BQ, redshift, or postgres so I did this PR for snowflake only
As mentioned in #3039, the downside of this PR is that breaking things up into multiple DDL statements causes dbt run to take longer. I hope this is okay since persist_docs defaults to off and users who are ultra-concerned with performance would most likely have it off anyways.

Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

I've just signed the CLA now

@cla-bot check

Hey @elikastelein, hope you're well! Just wanted to check in and see if you'd be able to add a test case for this change? More than happy to help with any pointers :)

Hey @jtcohen6, thanks for the ping. Sorry about leaving this hanging. I'll get started on adding tests soon and let you know if I need any pointers

@jtcohen6 thanks so much for the help, your comments were very helpful

Hi!
When running this, it runs one line per query. This slows down large tables with hundreds of columns, now taking minutes to run these instead of a few seconds.
This is because https://github.com/dbt-labs/dbt/commit/fffcd3b40423443a585a6ff1befaee74d47b6b30#diff-4e52d38c66fb471207fa26868ecc11715965558734704859a52b6bcfbc5c86cf now runs one query per line in sf, instead of putting it all in a single query.

authors: elikastelein joshuataylor jtcohen6 kwigley

repo: fishtown-analytics/dbt


text:
Link checker resolves to first matching suffix, not first matching path

Steps to reproduce:
If I create a link like this:
[run](run)

I expect it to go to the page named run:
https://docs.getdbt.com/reference/commands/run/

Instead, it goes to the first path that ends in run:
https://docs.getdbt.com/faqs/failed-prod-run

Live example
Source code:
https://github.com/fishtown-analytics/docs.getdbt.com/blame/current/website/docs/reference/dbt-commands.md#L18
Relevant page
Extra details
We could update all the links to be fully qualified, but I also think that my assumption about where the page will go is a pretty reasonable one.
In general, I'm a little blurry on the best way to write these hyperlinks in general! A heuristic would be useful to avoid future issues like this

closed by https://github.com/fishtown-analytics/docs.getdbt.com/pull/334

authors: clrcrl drewbanin


text:
Science Isn’t Broken

Hey!
I am curious if you have the data you used for the Science Isn't Broken article (https://fivethirtyeight.com/features/science-isnt-broken/). Particularly, the datasets you used for Hack Your Way To Scientific Glory figure. I know you mention where you got it, but do you have the "organized" form you used for it available?
It really is an excellent article.

You may be able to find the data you're looking for in this file.

authors: jayb mGalarnyk

repo: fivethirtyeight/data


text:
Feature/Label-Source-Addition

Are you a current Fivetran customer?

Fivetran created PR
What change(s) does this PR introduce?

This PR adds the label source table. This was necessary as the issue_label depreciated the label column. The respective label information will now be synced within the label table.
Additionally, a few minor updates were made to the issue_label table and some spelling updates were applied.
Does this PR introduce a breaking change?

[X] Yes (please provide breaking change details below.)
[ ] No  (please provide explanation how the change is non breaking below.)

Since this PR removes a field from the issue_label table and adds a new source table, this will be reflected as a breaking change.
Is this PR in response to a previously created Issue

[X] Yes, Issue #21
[ ] No

How did you test the PR changes?

[X] CircleCi
[ ] Other (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

[X] BigQuery
[X] Redshift
[X] Snowflake
[ ] Postgres
[ ] Databricks
[ ] Other (provide details below)

Provide an emoji that best describes your current mood

🏷
Feedback
We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

ah also remember to change the package version in the README installation instructions since it's breaking

authors: fivetran-jamie fivetran-joemarkiewicz