Bump up worker start timeout

What changes are proposed in this pull request?
The previous value can be too short for worker registration in some use cases, bump up the default timeout to 10 minutes for worker start.
Why are the changes needed?
Without this change, the worker registration will reach the time out by registering a large number of blocks.
Does this PR introduce any user facing changes?
No.

@jiacheliu3 FYI

Codecov Report

Merging #13646 (d14e8b7) into master (0203366) will decrease coverage by 26.24%.
The diff coverage is 41.93%.

@@              Coverage Diff              @@
##             master   #13646       +/-   ##
=============================================
- Coverage     43.86%   17.62%   -26.25%
+ Complexity     8930     2672     -6258
=============================================
  Files          1359     1380       +21
  Lines         78109    80103     +1994
  Branches       9496     9730      +234
=============================================
- Hits          34260    14115    -20145
- Misses        40960    64746    +23786
+ Partials       2889     1242     -1647

Impacted Files
Coverage Δ

...n/java/alluxio/client/block/AlluxioBlockStore.java
5.93% <0.00%> (-69.91%)
:arrow_down:

...o/client/block/policy/DeterministicHashPolicy.java
0.00% <ø> (-68.43%)
:arrow_down:

...nt/block/policy/LocalFirstAvoidEvictionPolicy.java
0.00% <ø> (-94.29%)
:arrow_down:

.../alluxio/client/block/policy/LocalFirstPolicy.java
0.00% <ø> (-93.94%)
:arrow_down:

.../client/block/policy/MostAvailableFirstPolicy.java
0.00% <ø> (-91.67%)
:arrow_down:

.../alluxio/client/block/policy/RoundRobinPolicy.java
0.00% <ø> (-97.92%)
:arrow_down:

...lluxio/client/block/policy/SpecificHostPolicy.java
0.00% <ø> (-40.00%)
:arrow_down:

...ava/alluxio/client/block/stream/BlockInStream.java
0.00% <0.00%> (-58.20%)
:arrow_down:

...xio/client/block/stream/BlockWorkerDataReader.java
0.00% <0.00%> (ø)

...ient/block/stream/BufferCachingGrpcDataReader.java
0.00% <0.00%> (-41.67%)
:arrow_down:

... and 855 more

Continue to review full report at Codecov.

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

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.6 please

alluxio-bot, cherry-pick this to branch-2.5 please

alluxio-bot, cherry-pick this to branch-2.4 please


Translated the Documentation to EN . Added a link to the EN README

Please check if the translation is okey !

nice


cleanup(falco): clarify that --print variants only affect syscalls

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind documentation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area engine

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

cleanup(falco): clarify that --print variants only affect syscalls

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 17358eb68cfe7500010a0a060c713bb52b4a824f

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra,incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, incertum, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,LucaGuerra,incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Resolve #49 [Assert] Create string "matches" matchers

RegexpMatcher implemented
UberMatchers.matches(String) and UberMatchers.matches(Pattern) implemented
=====
Blocked by: #57

createMatcher(...) seems more obvious than matching(...).

Renamed into #create


[Site] https://gamehag.com

Example: https://gamehag.com/giveaway/161

Ad removal implemented since https://github.com/gekkedev/giveawayHelperEnhancer/commit/4dc37b9c2adfa3689aacc2b324c7518b6985229e, and autologin afaik wasn't possible via steam. There's still a lot of auto-solving potential to be worked on another day! 😉 Keeping the issue open as reminder.

You May get Free CSGO skins at https://gamersnab.com/


⚠ Turnos 24x7 has degraded performance

In c4e1dc2, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 819 ms

Resolved: Turnos 24x7 performance has improved in cce9b54.


Improve Expressen extractor to work with more URLs

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Updated the Expressen extractor so support more urls, mostly by extracting the info from their embedded player page instead of the main page.

@dstftw thanks for the review - I've correct the issues now so please take another look at it.

@ dstftw please review again, I updated the code to fallback to the original url if embed url fails or if no formats were found. Thanks 😊

Hey @dstftw , is this ready for merge after the last version?


add id to

e.g.
 [...] Acme::Meow
That would allow linking from a README.md to the module in the ecosystem if that module is a dependency or for general propaganda.

Why not link to a search query? Like http://modules.perl6.org/#q=Adventure::Engine. And if you wish to link to a README, just link to the repo with http://modules.perl6.org/repo/Adventure::Engine

A definite :-1: from me due to it not being effective means for the wished purpose and due to it adding more markup to an already heavy page.
For example, here's what accessing a link to Adventure::Engine would look like.

And here's what a link to Zef would look like (note, it's not at the top).

You could style :target pseudo-class, but even then it would not be effective, since the user clicking a link isn't expecting a wall of modules.


which branch for version 8.1?

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ -] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
I will compile the source code for 8.1, but i dose not know which batch is matching with version 8.1

Bug

Which version of SkyWalking, OS, and JRE?

Which company or project?

What happened?
If possible, provide a way to reproduce the error. e.g. demo application, component version.

Requirement or improvement

Please describe your requirements or improvement suggestions.

All releases are tagged.

All releases are tagged.

All releases are tagged.

git  it, thanks .

All releases are tagged.

git  it, thanks .


Evaluate Jasmine 2.0

Jasmine 2.0 was just released.  We should take a closer look to see how hard upgrading is given all our custom changes.  If it is a ton of work, we can hold off until we decide on Intern, #735

@kring any ETA on this?  No rush, I just want to avoid a big merge conflict with #2056 (no action there yet).

I hope to get back to it really soon, especially since the merge gets more painful every day even in the absence of big changes like #2056.

Upgraded in #2495


Invoke-DbaQuery / Invoke-DbaAsync - Let PSObject handle more than one table

Type of Change

[ ] Bug fix (non-breaking change, fixes # )
[x] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
I want to get the output of sp_BlitzFirst @ExpertMode = 1 as PSObject, but the procedure returns 7 tables and -As PSObject only returns the content of the first table.
Approach
If there are more than one table, return an array of rows.
Commands to test
Install-DbaFirstResponderKit -SqlInstance SRV1\SQL2017
$BlitzFirst = Invoke-DbaQuery -SqlInstance SRV1\SQL2017 -Query 'sp_BlitzFirst @ExpertMode = 1' -As PSObject
$BlitzFirst | ForEach-Object -Process { $_ | Format-Table }
$BlitzFirst | ConvertTo-Json | Set-Content -Path C:\BlitzFirst.txt

There are maybe better approaches, so feedback is highly welcome.

Sorry for the indention change - my VSCode is not configured well...

did not forget this, sorry, had a busy few days. will review in a few hours

Thank you, @andreasjordan and @niphlod ! Will wait for approval 🙇

give it a whirl, I added tests . I believe the ones failing are due to other pending changes in development

Let's forget sp_blitz for the sake of "keeping it simple".
assuming this query

Keeping convertto-json as the "formatter", the original version, which does an array of rows (which are arrays themselves), ends up with
[
    {
        "value":  [
                      {
                          "a":  1
                      },
                      {
                          "a":  2
                      }
                  ],
        "Count":  2
    },
    {
        "value":  [
                      {
                          "b":  2,
                          "c":  3
                      },
                      {
                          "b":  4,
                          "c":  5
                      }
                  ],
        "Count":  2
    }
]

I feel the flexibility of PSObject is hurting here, because what you can have (basically the fix I put in) is this instead
[
    {
        "a":  1
    },
    {
        "a":  2
    },
    {
        "b":  2,
        "c":  3
    },
    {
        "b":  4,
        "c":  5
    }
]

which is more akin of what you get with a single resultset, or invoking the two queries separated.
Basically the problem here is .... with a Dataset, or Datatable, the "rich" object given back has distinct tables that you can "loop" separately, each one with a fixed set of columns and one or multiple rows.
What should we make the PSObject look like for results which are not consistent (i.e. two rows have only the property "a" and the next two ones have properties "b" and "c" ) ?
Powershell likes to spit out PSObjects as they come, irregardless of the type.
Spitting arrays of arrays has the added bonus of "delimiting" what is a single resultset from another one, i.e. we can identify where one starts and ends.
But the added con of being different from the result you'd get from a single resultset.
If the "columns" between resultsets do change, you can still identify where a resultset starts and ends.
Maybe @potatoqualitee, @wsmelton  and @FriedrichWeinmann have a type in mind that fits the bill ?
tl;dr: I'm fine either way (but this behaviour is new and should be fixed in stone by a regression test when we agree). I feel there are both pros and cons to each one and both implementations are coming from a solid background.... it's just that PSObject is too damn flexible that can accomodate both :D

I have thought about it again and hereby propose the new type PSObjectTable. What do you say, @niphlod ?

yeah, I don't think anything is going to cut it without an additional -As type. I'd go for PSObjectArray.

yeah, I don't think anything is going to cut it without an additional -As type. I'd go for PSObjectArray.

Yes, as it is an Array - let's call it an Array. I had the analogy with DataSet, DataTable and DataRow in mind. But I fully agree with Array.
I can change the code probably later today.

OK, updated the code, @niphlod please have a look.

the array part looks good, but -As PSObject needs to still spits out results from the two resultsets combined (as the version I posted before we embarked on a "let's make the array output optional").
Fix that, add a test with the behaviour of PSObject with multiple resultsets (this is a "new" feature and I'd like to fix the behaviour in stone with tests) and it's all perfect for me.

Like this?

@niphlod so sorry to bother but it's giving issues with formatting. help?

was looking but @andreasjordan  beat me to it. if it does fila again hail me.
BTW: @potatoqualitee after the last version of invoke-dbaformatter which checks that a correct version of PSSA is available I can't see why yours generates a different output

Ok, all green now...

sweet as heck, merging! thanks everyone 🙇


Cant setup smatir. Please help

Hi, I followed the instructions on how to set up the components but not having any luck. As soon as I check my config I am getting this error ):

Can you please paste in the contents of your configuration.yaml?

Can you also update to the latest version of home-assistant (and include the version number in the next update on the issue)?


Add Scrapfly website scrape tool

Adds Scrapfly support, a web scraping API enabling:

Extracting web page as HTML, Text, and Markdown (LLM accessible).
Executing headless browsers for dynamic websites.
Anti-bot bypass.
Built-in proxies.

Nice!


Request for making several elements valid in mei-neume dev-5.0.0 schema

As shown in the figure below, the underlined elements are not valid in the mei-neume dev-5.0.0 schema. The details and examples are as follows. All the examples are from Einsiedeln (CH-E_611).

<accid> is not valid both inside and outside a syllable, but it happens both inside and outside.

inside:

outside:

<divLine> is only valid inside a syllable, but it is mostly outside.

<clef>is only valid outside a syllable, but sometimes it is inside.

Compared to mei-all dev-5.0.0 schema, all the elements mentioned above but <accid> (also needs to be fixed) are valid both inside and outside a syllable.

Thanks to @martha-thomae for testing the schema, and thanks to @JoyfulGen for providing the examples.

Many thanks for bringing this up. As I'm no expert in encoding neumes I would like to bring this issue to the attention of the @music-encoding/ig-neumes with a kind request of reviewing and discussing the issues mentioned.

Just for the record: The clef and custos elements have been disabled within syllable in this commit: 78784fa92208ad7683d0c456840ca45ce326efd8 (maybe @kepper remembers about the intention behind that change?)
accid seems never to have been allowed, not even in v4?
Just out of curiosity: Is there a semantic difference between a clef or accid outside a syllable vs. inside a syllable? If they appear at the beginning of a syllable (that is "outside", right?), would they not be taken to belong to that syllable?

Thank you for finding that @musicEnfanthen. They were disallowed within a syllable because we asked for that. We have found new cases where clef changes do occur within a syllable as shown above in the examples.
As for for the semantic difference, if clef (or accid) was only allowed outside, it would apply to the entire syllable and not be able to change the pitch of the neumes within a syllable.

After discussing this issue with some members of the @music-encoding/ig-neumes (if I post this on the mailing list, most people would have no idea what I am talking about) and in view of finding new notational practices (as shown above), I believe what we would like is the following elements to be allowed inside or outside of syllable:  accid, divLine, and clef.
As for custos, they should not be allowed inside a syllable and only outside.

A current problem I see is that model.syllablePart is member of model.eventLike, allowing as syllable children:

barLine
chord
clef
clefGrp
custos
note
pad
rest
space

The only thing of this whole list that should go in there is clef, correct?

A current problem I see is that model.syllablePart is member of model.eventLike, allowing as syllable children:

barLine
chord
clef
clefGrp
custos
note
pad
rest
space

The only thing of this whole list that should go in there is clef, correct?

Yes, from the list the only thing we would like to be included within syllable is clefin the Neume module. I guess you can remove the others from model.syllablePart because the model class is only used in the Neume module.
But we would also like to have accid and divLine to be allowed inside syllable.

You want to treat an accidental like a free floating glyph, but it is always connected to a pitch event, so from my point of view it should be (always and only) a child of nc.

There was a reason why <accid> is not allowed as a child of <nc>, see https://github.com/music-encoding/music-encoding/issues/816#issuecomment-861793579. But it seems to have been allowed within syllable at some point, as indicated in https://github.com/music-encoding/music-encoding/issues/665#issue-620153531.

You want to treat an accidental like a free floating glyph, but it is always connected to a pitch event, so from my point of view it should be (always and only) a child of nc.

I see two reasons why the <accid> should be free-floating:

Because it's spacial (horizontal) position must be encodable. It is in general not written immediately before the <nc> but before a <ncGrp> (or <neume>) which the <nc> is part of.  Tthat's what @pe-ro's comment what @martha-thomae links to above says.
I remember cases where the Corpus monodicum editors found an accidental that was written before a <uneume> (as it was encoded back then) that did not fit any of the <note>s (as they were encoded back then) from that <uneume>.  We didn't have a way of encoding it properly and used an annotation instead that my typesetting engine would recognize and output the proper accidental in the PDF. I would have to work through old backups to see if I find any traces of that, though.
I also remember vaguely cases where editors were not sure if the accidentals they looked at were intended as something like a key signature or if they were just free-floating accidentals.  It would be nice if they could just encode what they find instead of enforcing an interpretation.

@yinanazhou can you create an MEI file that has an accid, a divLine, and a clef inside a syllable and also an accid, a divLine, and a clef outside a syllable and place that file in one of our DDMAL GitHub repo? This file will be used to test the changes we will be making here.

@yinanazhou can you create an MEI file that has an accid, a divLine, and a clef inside a syllable and also an accid, a divLine, and a clef outside a syllable and place that file in one of our DDMAL GitHub repo? This file will be used to test the changes we will be making here.

Hi @fujinaga, I've uploaded the test file here. The corresponding image file can be found in the same folder.

@yinanazhou @fujinaga could you please test your file against the latest changes in PR #983 and see if it solves your problem?

Hi @ahankinson, I just tested an example file against this schema. I'm sorry that it doesn't solve all the problems as the elements below should be valid:

accid is not allowed either inside or outside of a syllable in this schema (accid should be allowed both inside and outside of a syllable)

divLine is not allowed outside of a syllable in this schema (divLine should be allowed inside and outside of a syllable)

Just an observation, and not really related to the validity, but your accid should have a ploc attribute; otherwise you don't know which pitch on the staff your accidental affects.

So, Klaus's PR #983 does solve the issues with clef and custos. Thank you, @rettinghaus!
I am providing here a very minimalistic MEI file to test any of the other desired changes mentioned in this comment:

...I believe what we would like is the following elements to be allowed inside or outside of syllable: accid, divLine, and clef.
As for custos, they should not be allowed inside a syllable and only outside.

File: testing_changes_to_neumes_module.xml.zip
<?xml version="1.0" encoding="UTF-8"?>
<!-- <?xml-model href="https://music-encoding.org/schema/dev/mei-Neumes.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="https://music-encoding.org/schema/dev/mei-Neumes.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?> -->
<?xml-model href="mei-Neumes.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="mei-Neumes.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<mei xmlns="http://www.music-encoding.org/ns/mei">
    <meiHead>
        <fileDesc>
            <titleStmt>
                <title>Testing Changes to Neumes Module</title>
            </titleStmt>
            <pubStmt/>
        </fileDesc>
    </meiHead>
    <music>
        <body>
            <mdiv>
                <score>
                    <scoreDef>
                        <staffGrp>
                            <staffDef n="1" lines="4" notationtype="neume"></staffDef>
                        </staffGrp>
                    </scoreDef>
                    <section>
                        <staff>
                            <layer>
                                <custos/>
                                <sb/>
                                <clef/>
                                <accid/>
                                <syllable>
                                    <custos/>
                                    <sb/>
                                    <clef/>
                                    <accid/>
                                    <neume><nc/></neume>
                                    <divLine/>
                                </syllable>
                                <divLine/>
                            </layer>
                        </staff>
                    </section>
                </score>
            </mdiv>
        </body>
    </music>
</mei>

Reopened, since #983 only addressed parts of the issue.

I believe the fixes in PR #1019 resolve this issue.
However, it's SUPER important to make a distinction between what's allowed by MEI-all, which exists to accommodate documents that mix notational repertoires, and what's allowed by the neumes customization, which can extend or restrict MEI-all. For example, @fujinaga's  comments above -- "the only thing we would like to be included within syllable is clef in the Neume module." -- should be implemented in the neumes customization, not MEI-all; that is, not within the neumes module.


ClipQKV

This PR

enables qk_ln in triton attn variant
enables clipping qkv before attn is applied

On its own, Alibi does not fully solve the stability issue; when clipping is added to qkv, training becomes more stable.

Without Alibi, clipping qkv is still very stable (it just doesn't do as well)

I tried clipping values of {0.1, 1, 2, 10}; {0.1, 1} were too aggressive; {2, 10} are shown. We can see that when the clipping value is higher (10) the network is slightly less stable and gets psuedo-loss spikes from which it recovers gracefully.
ClipQKV+Alibi outperforms QKLN

ClipQKV+Alibi has the exact same performance as QKLN+Alibi

adding some unit tests to check equality between the torch/causal/triton attention blocks?
https://mosaicml.atlassian.net/browse/RESEARCH-468

Looks like the tests got OOM killed. Try turning down some of the params (e.g. model size, sequence length) on the test that got killed (https://github.com/mosaicml/examples/blob/d1a855f4ac0bc4bc6ec218b6748f35fa008eafbf/examples/llm/tests/test_model.py#L179)

https://github.com/mosaicml/examples/pull/197#issuecomment-1449479110
yeah they're gpu tests. I need to xfail them on cpu. Forgot to do that...


Revert "Remove unnecessary NuGet package references (#5242)"

This reverts commit 1ae86d63c271f20985f8d327132628c105fae0ae which has been blocking our builds since it was merged in.
https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=3623419&view=results is the failing build and https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=3624117&view=results is the build that succeeded after reverting the commit.

This change wasn't at fault; https://github.com/dotnet/arcade/pull/5239 should resolve this permanently.


JEP 471 warning: "sun.misc.Unsafe::objectFieldOffset has been called by scala.runtime.LazyVals$"

Compiler version
3.x
Minimized example
lazy val x = "X"

Output
When running on the latest JDK-24-dev (or on JDK-23+ with --sun-misc-unsafe-memory-access=deny)
WARNING: Please consider reporting this to the maintainers of class scala.runtime.LazyVals$
WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by scala.runtime.LazyVals$

Expectation
No warnings

I propose that because of the weird appropriation of X by the billionaire platforms, we abjure 3.x, val x and similar valorizations of x that derive principally from mathematical notation and secondarily from the branding marketplace.
I use v for a value and A for a type parameter, although many still use T for "type". I still prefer T for trait T.

@som-snytt Thanks for your feedback!
I have updated of list of Scala versions were I reproduced this issue.
Also, it looks that any code can reproduce the issue, even val v = "".


sw-check-in and lamda functions are timing out

Something weird is up. My alarms were triggered.
sw-schedule-check-in and sw-check-in are timing out. Logs are not currently helpful but here they are.
sw-schedule-check-in
[INFO]	2019-03-01T02:19:41.318Z	ce8d9421-b32c-4ec2-9099-bfe517b8d1ed	Looking up reservation ABC123 for John Doe
02:19:51
END RequestId: ce8d9421-b32c-4ec2-9099-bfe517b8d1ed
02:19:51
REPORT RequestId: ce8d9421-b32c-4ec2-9099-bfe517b8d1ed	Duration: 10010.31 ms	Billed Duration: 10000 ms Memory Size: 128 MB	Max Memory Used: 37 MB
02:19:51
2019-03-01T02:19:51.328Z ce8d9421-b32c-4ec2-9099-bfe517b8d1ed Task timed out after 10.01 seconds

sw-check-in
START RequestId: da00d186-fe0f-4f85-9537-0d7b25c500cd Version: $LATEST
02:10:06
[INFO]	2019-03-01T02:10:06.937Z	da00d186-fe0f-4f85-9537-0d7b25c500cd	Checking in [{'firstName': 'John', 'lastName': 'Doe'}] (ABC123)
02:10:21
END RequestId: da00d186-fe0f-4f85-9537-0d7b25c500cd
02:10:21
REPORT RequestId: da00d186-fe0f-4f85-9537-0d7b25c500cd	Duration: 15013.39 ms	Billed Duration: 15000 ms Memory Size: 128 MB	Max Memory Used: 39 MB
02:10:21
2019-03-01T02:10:21.946Z da00d186-fe0f-4f85-9537-0d7b25c500cd Task timed out after 15.01 seconds

Raising timeout doesn't help.

Appears the base url has changed from
BASE_URL = "https://api-extensions.southwest.com/v1/mobile"
to
BASE_URL = "https://mobile.southwest.com/api/extensions/v1/mobile"
sucessfully looked up a reservation after making this change
[INFO]	2019-03-01T03:09:03.254Z	55c29032-b4c7-40d5-8434-203e31c3f9d8	Looking up reservation ABC123 for John Doe
03:09:07
[DEBUG]	2019-03-01T03:09:07.194Z	55c29032-b4c7-40d5-8434-203e31c3f9d8	Reservation: <Reservation ABC123>
03:09:07
[INFO]	2019-03-01T03:09:07.691Z	55c29032-b4c7-40d5-8434-203e31c3f9d8	Sending email to<EMAIL_ADDRESS>

Yikes. Does it work from non-AWS address space?
On Thu, Feb 28, 2019, 8:56 PM Scott Bishop<EMAIL_ADDRESS>wrote:

Raising timeout doesn't help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DavidWittman/serverless-southwest-check-in/issues/55#issuecomment-468523394,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AArmLxn23qCjtVuq7JRUWi00HSFHUyX1ks5vSJbkgaJpZM4bYKzo
.

Thanks Scott... PRs welcome!
On Thu, Feb 28, 2019, 9:27 PM Scott Bishop<EMAIL_ADDRESS>wrote:

Appears the base url has changed from
BASE_URL = "https://api-extensions.southwest.com/v1/mobile"
to
BASE_URL = "https://mobile.southwest.com/api/extensions/v1/mobile"
sucessfully looked up a reservation after making this change
[INFO]	2019-03-01T03:09:03.254Z	55c29032-b4c7-40d5-8434-203e31c3f9d8	Looking up reservation ABC123 for John Doe
03:09:07
[DEBUG]	2019-03-01T03:09:07.194Z	55c29032-b4c7-40d5-8434-203e31c3f9d8	Reservation:
03:09:07
[INFO]	2019-03-01T03:09:07.691Z	55c29032-b4c7-40d5-8434-203e31c3f9d8	Sending email to<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DavidWittman/serverless-southwest-check-in/issues/55#issuecomment-468529043,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AArmL6pg35kfLuy-YM4Eqwz_jXHigRtdks5vSJ46gaJpZM4bYKzo
.

Thanks Scott... PRs welcome!

https://github.com/DavidWittman/serverless-southwest-check-in/pull/56


Swift Compiler Error (Xcode): Type 'Logger' has no member 'e', 'd' or 'i' when update to 0.7.7

Rules

To report a bug and help us to provide the solution as fast as possible, please follow the instructions below:
1 - Describe the bug
A clear and concise description of what the bug is.
OBS: avoid to use the expression "its not working" or "is working" or any other variation. These expressions can mean anything and at same time doesn´t bring any useful information. As soon you rewrite these expressions, you naturally going to be more precise and clear.
2 - Provide us as much information as possible
To help us to understand your issue, provide with your bug report all the relevant informations, such as:

Your plugins list inside the file pubspec.yaml (at least all notification plugins)
What platform did you found the issue
What devices did you found the issue
How are you initializing the plugin
How are you creating the notification
The output of flutter doctor command

OBS: To post a source code in your issue, please use the markdown below:
print('Your source code goes here');

3 - How To Reproduce the Error
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

...or if you prefer, you can provide us a simple example app on GitHub with the issue already reproduced instead of the steps 2 and 3.
4 - Expected behavior
A clear and concise description of what you expected to happen.
5 - Screenshots
If applicable, add screenshots to help explain your problem.
6 - Additional context
Add any other context about the problem here.

Getting the same issue with pubspec:
awesome_notifications_core: ^0.7.6   awesome_notifications: any   awesome_notifications_fcm: any

try awesome_notifications: 0.7.4+1

You gonna need to clean your project to ensure to use the most updated version. This is happening yet because your core libraries at iOS native still the same, but the rest was updated.

Any solution to resolve this?

@rafaelsetragni
I got the same issue, after making sure pods and packages were updated and the project build was clean.
to be precise DartBackgroundExecutor all the loggers in that class are complaining

When you run pub get what versions of awesome are being printed?

When you run pub get what versions of awesome are being printed?

awesome_notifications 0.7.7
awesome_notifications_core 0.7.6
awesome_notifications_fcm 0.7.6

Try to run pod update inside ios folder

Try to run pod update inside ios folder

still not working

I update to:
awesome_notifications: ^0.7.4+1
awesome_notifications_core: ^0.7.4+1
and this problem still shows:
Could not build the precompiled application for the device.
Swift Compiler Error (Xcode): Type 'Logger' has no member 'e'
/Users/pedrocovarrubias/.pub-cache/hosted/pub.dev/awesome_notifications-0.7.7/ios/Classes/lib/DartBackgroundExecutor.swift:97:19
someone can help?

I solved with deleting podfile.lock and pubspec.lock. And doing flutter pub get and pod install

Same here. Tried everything from cleaning project to running pub get time and again. Nothing is working.
Anyone have any idea last working version ? Or any temp work around?

I solved it with deleting podfile.lock and pubspec.lock. After that using old awesome notification version and doing flutter pub get and pod install

Didnt work for me. I am stuck in
awesome_notifications 0.7.7
awesome_notifications_core 0.7.6
awesome_notifications_fcm 0.7.6

It is, i just compile it right now.
Here is the result of my pod update:
rafaelsetragni@Rafaels-Mac-mini ios % pod update
Ignoring ffi-1.15.5 because its extensions are not built. Try: gem pristine ffi --version 1.15.5
Update all pods
Updating local specs repositories
Analyzing dependencies
cloud_firestore: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
firebase_auth: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
firebase_core: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
Ignoring ffi-1.15.5 because its extensions are not built. Try: gem pristine ffi --version 1.15.5
Warning: firebase_app_id_file.json file does not exist. This may cause issues in upload-symbols. If this error is unexpected, try running flutterfire configure again.
firebase_crashlytics: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
firebase_storage: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
Downloading dependencies
Installing BoringSSL-GRPC (0.0.24)
Installing DKImagePickerController (4.3.4)
Installing DKPhotoGallery (0.0.17)
Installing FMDB (2.7.5)
Installing Firebase (10.15.0)
Installing FirebaseAppCheckInterop (10.15.0)
Installing FirebaseAuth (10.15.0)
Installing FirebaseAuthInterop (10.15.0)
Installing FirebaseCore (10.15.0)
Installing FirebaseCoreExtension (10.15.0)
Installing FirebaseCoreInternal (10.15.0)
Installing FirebaseCrashlytics (10.15.0)
Installing FirebaseFirestore (10.15.0)
Installing FirebaseInstallations (10.15.0)
Installing FirebaseMessaging (10.15.0)
Installing FirebaseSessions (10.15.0)
Installing FirebaseStorage (10.15.0)
Installing Flutter (1.0.0)
Installing GTMSessionFetcher (3.1.1)
Installing GoogleDataTransport (9.2.5)
Installing GoogleUtilities (7.11.5)
Installing IosAwnCore (0.7.7)
Installing IosAwnFcmDist (0.7.6)
Installing Mantle (2.2.0)
Installing PromisesObjC (2.3.1)
Installing PromisesSwift (2.3.1)
Installing ReachabilitySwift (5.0.0)
Installing RecaptchaInterop (100.0.0)
Installing SDWebImage (5.18.2)
Installing SDWebImageWebPCoder (0.13.0)
Installing SwiftyGif (5.4.4)
Installing Toast (4.0.0)
Installing abseil (1.20220623.0)
Installing awesome_notifications (0.7.6)
Installing awesome_notifications_core (0.0.1)
Installing awesome_notifications_fcm (0.7.5)
Installing cloud_firestore (4.9.2)
Installing connectivity_plus (0.0.1)
Installing device_info_plus (0.0.1)
Installing file_picker (0.0.1)
Installing firebase_auth (4.10.0)
Installing firebase_core (2.16.0)
Installing firebase_crashlytics (3.3.6)
Installing firebase_storage (11.2.7)
Installing flutter_image_compress_common (1.0.0)
Installing flutter_native_image (0.0.1)
Installing flutter_secure_storage (6.0.0)
Installing fluttertoast (0.0.2)
Installing gRPC-C++ (1.50.1)
Installing gRPC-Core (1.50.1)
Installing image_picker_ios (0.0.1)
Installing leveldb-library (1.22.2)
Installing libwebp (1.3.2)
Installing nanopb (2.30909.0)
Installing package_info_plus (0.4.5)
Installing path_provider_foundation (0.0.1)
Installing permission_handler_apple (9.1.1)
Installing photo_manager (2.0.0)
Installing share_plus (0.0.1)
Installing shared_preferences_foundation (0.0.1)
Installing sqflite (0.0.3)
Installing url_launcher_ios (0.0.1)
Installing webview_flutter_wkwebview (0.0.1)
Generating Pods project
Integrating client project
Pod installation complete! There are 26 dependencies from the Podfile and 63 total pods installed.

The most important part is to certify that you are using the lastest core libraries:
Installing IosAwnCore (0.7.7)
Installing IosAwnFcmDist (0.7.6)

Analyzing dependencies
firebase_core: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
Run script to upload symbols already exists.
firebase_crashlytics: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
firebase_dynamic_links: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
Downloading dependencies
Installing FMDB (2.7.5)
Installing Firebase (10.15.0)
Installing FirebaseCore (10.15.0)
Installing FirebaseCoreExtension (10.15.0)
Installing FirebaseCoreInternal (10.15.0)
Installing FirebaseCrashlytics (10.15.0)
Installing FirebaseDynamicLinks (10.15.0)
Installing FirebaseInstallations (10.15.0)
Installing FirebaseMessaging (10.15.0)
Installing FirebaseSessions (10.15.0)
Installing Flutter (1.0.0)
Installing GTMSessionFetcher (2.3.0)
Installing GoogleDataTransport (9.2.5)
Installing GoogleMLKit (4.0.0)
Installing GoogleMaps (7.4.0)
Installing GoogleToolboxForMac (2.3.2)
Installing GoogleUtilities (7.11.5)
Installing GoogleUtilitiesComponents (1.1.0)
Installing IosAwnCore (0.7.7)
Installing IosAwnFcmDist (0.7.6)
Installing MLImage (1.0.0-beta4)
Installing MLKitBarcodeScanning (3.0.0)
Installing MLKitCommon (9.0.0)
Installing MLKitTextRecognition (2.0.0)
Installing MLKitTextRecognitionCommon (1.0.0)
Installing MLKitVision (5.0.0)
Installing Mantle (2.2.0)
Installing OrderedSet (5.0.0)
Installing PromisesObjC (2.3.1)
Installing PromisesSwift (2.3.1)
Installing ReachabilitySwift (5.0.0)
Installing SDWebImage (5.18.2)
Installing SDWebImageWebPCoder (0.13.0)
Installing Stripe (23.12.0)
Installing StripeApplePay (23.12.0)
Installing StripeCore (23.12.0)
Installing StripeFinancialConnections (23.12.0)
Installing StripePaymentSheet (23.12.0)
Installing StripePayments (23.12.0)
Installing StripePaymentsUI (23.12.0)
Installing StripeUICore (23.12.0)
Installing WeScan (1.7.0)
Installing awesome_notifications (0.7.6)
Installing awesome_notifications_core (0.0.1)
Installing awesome_notifications_fcm (0.7.5)
Installing connectivity_plus (0.0.1)
Installing device_info_plus (0.0.1)
Installing edge_detection (1.1.2)
Installing firebase_core (2.16.0)
Installing firebase_crashlytics (3.3.6)
Installing firebase_dynamic_links (5.3.6)
Installing flutter_blue_plus (0.0.1)
Installing flutter_fgbg (0.0.1)
Installing flutter_image_compress_common (1.0.0)
Installing flutter_inappwebview (0.0.1)
Installing flutter_native_splash (0.0.1)
Installing flutter_secure_storage (6.0.0)
Installing geocoding_ios (1.0.5)
Installing geolocator_apple (1.2.0)
Installing google_maps_flutter_ios (0.0.1)
Installing google_mlkit_commons (0.5.0)
Installing google_mlkit_text_recognition (0.10.0)
Installing image_picker_ios (0.0.1)
Installing libwebp (1.3.2)
Installing local_auth_ios (0.0.1)
Installing mobile_scanner (3.2.0)
Installing nanopb (2.30909.0)
Installing package_info_plus (0.4.5)
Installing path_provider_foundation (0.0.1)
Installing pay_ios (0.0.1)
Installing permission_handler_apple (9.1.1)
Installing share_plus (0.0.1)
Installing shared_preferences_foundation (0.0.1)
Installing sign_in_with_apple (0.0.1)
Installing sqflite (0.0.3)
Installing stripe_ios (0.0.1)
Installing url_launcher_ios (0.0.1)
Installing vibration (1.7.5)
Installing webview_flutter_wkwebview (0.0.1)
Generating Pods project
Integrating client project
Pod installation complete! There are 36 dependencies from the Podfile and 79 total pods installed.

Analyzing dependencies
firebase_core: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
Run script to upload symbols already exists.
firebase_crashlytics: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
firebase_dynamic_links: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
Downloading dependencies
Installing FMDB (2.7.5)
Installing Firebase (10.15.0)
Installing FirebaseCore (10.15.0)
Installing FirebaseCoreExtension (10.15.0)
Installing FirebaseCoreInternal (10.15.0)
Installing FirebaseCrashlytics (10.15.0)
Installing FirebaseDynamicLinks (10.15.0)
Installing FirebaseInstallations (10.15.0)
Installing FirebaseMessaging (10.15.0)
Installing FirebaseSessions (10.15.0)
Installing Flutter (1.0.0)
Installing GTMSessionFetcher (2.3.0)
Installing GoogleDataTransport (9.2.5)
Installing GoogleMLKit (4.0.0)
Installing GoogleMaps (7.4.0)
Installing GoogleToolboxForMac (2.3.2)
Installing GoogleUtilities (7.11.5)
Installing GoogleUtilitiesComponents (1.1.0)
Installing IosAwnCore (0.7.7)
Installing IosAwnFcmDist (0.7.6)
Installing MLImage (1.0.0-beta4)
Installing MLKitBarcodeScanning (3.0.0)
Installing MLKitCommon (9.0.0)
Installing MLKitTextRecognition (2.0.0)
Installing MLKitTextRecognitionCommon (1.0.0)
Installing MLKitVision (5.0.0)
Installing Mantle (2.2.0)
Installing OrderedSet (5.0.0)
Installing PromisesObjC (2.3.1)
Installing PromisesSwift (2.3.1)
Installing ReachabilitySwift (5.0.0)
Installing SDWebImage (5.18.2)
Installing SDWebImageWebPCoder (0.13.0)
Installing Stripe (23.12.0)
Installing StripeApplePay (23.12.0)
Installing StripeCore (23.12.0)
Installing StripeFinancialConnections (23.12.0)
Installing StripePaymentSheet (23.12.0)
Installing StripePayments (23.12.0)
Installing StripePaymentsUI (23.12.0)
Installing StripeUICore (23.12.0)
Installing WeScan (1.7.0)
Installing awesome_notifications (0.7.6)
Installing awesome_notifications_fcm (0.7.5)
Installing connectivity_plus (0.0.1)
Installing device_info_plus (0.0.1)
Installing edge_detection (1.1.2)
Installing firebase_core (2.16.0)
Installing firebase_crashlytics (3.3.6)
Installing firebase_dynamic_links (5.3.6)
Installing flutter_blue_plus (0.0.1)
Installing flutter_fgbg (0.0.1)
Installing flutter_image_compress_common (1.0.0)
Installing flutter_inappwebview (0.0.1)
Installing flutter_native_splash (0.0.1)
Installing flutter_secure_storage (6.0.0)
Installing geocoding_ios (1.0.5)
Installing geolocator_apple (1.2.0)
Installing google_maps_flutter_ios (0.0.1)
Installing google_mlkit_commons (0.5.0)
Installing google_mlkit_text_recognition (0.10.0)
Installing image_picker_ios (0.0.1)
Installing libwebp (1.3.2)
Installing local_auth_ios (0.0.1)
Installing mobile_scanner (3.2.0)
Installing nanopb (2.30909.0)
Installing package_info_plus (0.4.5)
Installing path_provider_foundation (0.0.1)
Installing pay_ios (0.0.1)
Installing permission_handler_apple (9.1.1)
Installing share_plus (0.0.1)
Installing shared_preferences_foundation (0.0.1)
Installing sign_in_with_apple (0.0.1)
Installing sqflite (0.0.3)
Installing stripe_ios (0.0.1)
Installing url_launcher_ios (0.0.1)
Installing vibration (1.7.5)
Installing webview_flutter_wkwebview (0.0.1)
Generating Pods project
Integrating client project
Pod installation complete! There are 35 dependencies from the Podfile and 78 total pods installed.

Guys, once again, you need to update your libraries with flutter pub upgrade. This error is because your libraries are outdated. This logger class was changed to use interfaces and singletons on the last version, and the old version uses static methods.

Analyzing dependencies
firebase_core: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
Run script to upload symbols already exists.
firebase_crashlytics: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
firebase_dynamic_links: Using Firebase SDK version '10.15.0' defined in 'firebase_core'
Downloading dependencies
Installing FMDB (2.7.5)
Installing Firebase (10.15.0)
Installing FirebaseCore (10.15.0)
Installing FirebaseCoreExtension (10.15.0)
Installing FirebaseCoreInternal (10.15.0)
Installing FirebaseCrashlytics (10.15.0)
Installing FirebaseDynamicLinks (10.15.0)
Installing FirebaseInstallations (10.15.0)
Installing FirebaseMessaging (10.15.0)
Installing FirebaseSessions (10.15.0)
Installing Flutter (1.0.0)
Installing GTMSessionFetcher (2.3.0)
Installing GoogleDataTransport (9.2.5)
Installing GoogleMLKit (4.0.0)
Installing GoogleMaps (7.4.0)
Installing GoogleToolboxForMac (2.3.2)
Installing GoogleUtilities (7.11.5)
Installing GoogleUtilitiesComponents (1.1.0)
Installing IosAwnCore (0.7.7)
Installing IosAwnFcmDist (0.7.6)
Installing MLImage (1.0.0-beta4)
Installing MLKitBarcodeScanning (3.0.0)
Installing MLKitCommon (9.0.0)
Installing MLKitTextRecognition (2.0.0)
Installing MLKitTextRecognitionCommon (1.0.0)
Installing MLKitVision (5.0.0)
Installing Mantle (2.2.0)
Installing OrderedSet (5.0.0)
Installing PromisesObjC (2.3.1)
Installing PromisesSwift (2.3.1)
Installing ReachabilitySwift (5.0.0)
Installing SDWebImage (5.18.2)
Installing SDWebImageWebPCoder (0.13.0)
Installing Stripe (23.12.0)
Installing StripeApplePay (23.12.0)
Installing StripeCore (23.12.0)
Installing StripeFinancialConnections (23.12.0)
Installing StripePaymentSheet (23.12.0)
Installing StripePayments (23.12.0)
Installing StripePaymentsUI (23.12.0)
Installing StripeUICore (23.12.0)
Installing WeScan (1.7.0)
Installing awesome_notifications (0.7.6)
Installing awesome_notifications_core (0.0.1)
Installing awesome_notifications_fcm (0.7.5)
Installing connectivity_plus (0.0.1)
Installing device_info_plus (0.0.1)
Installing edge_detection (1.1.2)
Installing firebase_core (2.16.0)
Installing firebase_crashlytics (3.3.6)
Installing firebase_dynamic_links (5.3.6)
Installing flutter_blue_plus (0.0.1)
Installing flutter_fgbg (0.0.1)
Installing flutter_image_compress_common (1.0.0)
Installing flutter_inappwebview (0.0.1)
Installing flutter_native_splash (0.0.1)
Installing flutter_secure_storage (6.0.0)
Installing geocoding_ios (1.0.5)
Installing geolocator_apple (1.2.0)
Installing google_maps_flutter_ios (0.0.1)
Installing google_mlkit_commons (0.5.0)
Installing google_mlkit_text_recognition (0.10.0)
Installing image_picker_ios (0.0.1)
Installing libwebp (1.3.2)
Installing local_auth_ios (0.0.1)
Installing mobile_scanner (3.2.0)
Installing nanopb (2.30909.0)
Installing package_info_plus (0.4.5)
Installing path_provider_foundation (0.0.1)
Installing pay_ios (0.0.1)
Installing permission_handler_apple (9.1.1)
Installing share_plus (0.0.1)
Installing shared_preferences_foundation (0.0.1)
Installing sign_in_with_apple (0.0.1)
Installing sqflite (0.0.3)
Installing stripe_ios (0.0.1)
Installing url_launcher_ios (0.0.1)
Installing vibration (1.7.5)
Installing webview_flutter_wkwebview (0.0.1)
Generating Pods project
Integrating client project
Pod installation complete! There are 36 dependencies from the Podfile and 79 total pods installed.
Agreed... but it is already updated.

And the error:

@rafaelsetragni What is your Xcode version?

Running on MacOS 14 Sonoma
and cocoapods:
1.13.0

@rafaelsetragni What is your Xcode version?
To Logger Class and Protocol. Is it the right one?

Yes, it is. I need to use this approach to integrate with Firebase Crashlytics in the next versions.

Mine is 14.3.1

Could this be the problem?

Even with the suggestions posted in the discord I have the exact same problem.
pub get:
  awesome_notifications 0.7.7
  awesome_notifications_core 0.7.6
  awesome_notifications_fcm 0.7.6

pod install/ pod update:
Installing IosAwnCore (0.7.7)
Installing IosAwnFcmDist (0.7.6)
...

I am on Xcode 15.0

Same problems here. Right now I can't even go back to 0.7.4+1 because the same error persists, it seems like it keeps using 0.7.7 even though I cleaned pub cache, not sure what to do?

Same Issue using Xcode 15 and awesome_notifications 0.7.7. I can't go back to 0.7.5 either , even after cleanning cache deleting Pod folder and podfile.lock

I have tried all of the above steps, as well as the following (multiple times, multiple orders):

Upgrade Flutter to 3.16.3
Upgrade cocoapods (brew upgrade cocoapods)
Do a Hail Mary (dev tools folder, clean script)
delete podfile.lock
delete Pods folder
flutter clean
flutter pub cache repair
flutter pub get
flutter pub upgrade
delete pods folder
cd into ios

pod install —repo-update
pod update

I am still getting errors, like many of the comments above.

(I hope this is not relevant for long!)
Needing a fix for this now, I forked and commented out references to the Logger. So, if you need a "works now," you can use my fork by updating your pubspec.yaml's awesome_notifications to:
    awesome_notifications:
        git:
            url: https://github.com/charlesRmajor/awesome_notifications

No promises on this working, but it is building for me. I forked from the latest 0.8.0 version.

Same issue for me, was running ok on 0.7.4+1 but upgrading to 0.8.0 the Logger issue appeared and not able to go back to 0.7.4+1. Removing Pod, podfile.lock, pubspec.lock, etc ... nothing works. Running Flutter 3.13.6, Xcode 15, IOS Simulator 15. I just upgraded Flutter from version 3.7.12 and awesome_notifications: ^0.8.0 ( no core no fcm).

I uploaded all libraries with major version 0.8.0. Update it and try again:
dependencies:
  awesome_notifications_core: ^0.8.0
  awesome_notifications: any
  awesome_notifications_fcm: any // <- The other plugins are optional

Hope this helps, unfortunately since I had limited time, I was only able to get this to run by. Running this via deployment 13 from my original 12. (17 also worked, but ran into issues with connectivity_plus plugin).
I backed up my iOS directory and then deleted it. I ran: flutter create .
flutter pub cache clean
flutter clean
flutter pub get
Added back my plist, entitlement etc. to iOS and added platform: 13.0 to my Podfile then set the deployment version to 13-17

@rafaelsetragni You're amazing. Our app is able to compile.
Not sure if it is relevant, but I'll add it just in case anyone else needs things to try. I also updated my XCode Project Format to Xcode 15.0. I had it on 14 before.

I'm in shock how .lock files are so insistent to keeping old versions, even updating the major version to 8.
To ensure that everything is updated, use the yaml below:
dependencies:
  awesome_notifications_core: ^0.8.1
  awesome_notifications: ^0.8.2
  awesome_notifications_fcm: ^0.8.0

Later I'll figure out a better way to make sure all the libraries are up to date and match each other.

@rafaelsetragni it's quite annoying to say the least.
I appreciate you getting on this so quickly! Today is our company's go-live for push notifications using your package-- so your fix came just in time 😄

@rafaelsetragni Thank you. It compiles now!

@rafaelsetragni  awesome thanks a million !

xcode 15, macos 14 sonoma, cocoapods last version, emulator and phone ios 17
Using
dependencies:
  awesome_notifications_core: ^0.8.1
  awesome_notifications: ^0.8.2
  awesome_notifications_fcm: ^0.8.0

On real phone getting this error
Could not build the precompiled application for the device.
Error (Xcode): Sandbox: rsync.samba(30335) deny(1) file-write-create /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Flutter.framework

Error (Xcode): Sandbox: dart(30315) deny(1) file-write-create /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/.last_build_id

Error (Xcode): Flutter failed to write to a file at "/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/.last_build_id".

Error launching application on Shahar's IPhone.

Solved with this
https://github.com/flutter/flutter/issues/128739
disabled ENABLE_USER_SCRIPT_SANDBOXING is working for me.
1.	Open the Xcode project.
2.	Click on the project name in the left sidebar to open the project settings.
3.	Select the target you want to check in the "Targets" section.
4.	Click on the "Build Settings" tab.
5.	In the search bar, type "ENABLE_USER_SCRIPT_SANDBOXING".
6.	If the value of ENABLE_USER_SCRIPT_SANDBOXING is set to "No", then it is disabled. If it is set to "Yes", then it is enabled.

Now getting a different error
Launching lib/main.dart on Shahar's IPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: 9ZU62NBH4Z
Running pod install...
Running Xcode build...
Xcode build done.                                           39.7s
Failed to build iOS app
Could not build the precompiled application for the device.
Error (Xcode): Cycle inside Runner; building could produce unreliable results.
Cycle details:
→ Target 'Runner': ExtractAppIntentsMetadata
○ Target 'Runner' has copy command from '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/AwesomeServiceExtension.appex' to '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex'
○ That command depends on command in Target 'Runner': script phase "Thin Binary"
○ Target 'Runner' has process command with output '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist'
○ Target 'Runner' has copy command from '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/AwesomeServiceExtension.appex' to '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex'

Raw dependency cycle trace:

target:  ->

node: <all> ->

command: <all> ->

node: /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/Objects-normal/arm64/ExtractedAppShortcutsMetadata.stringsdata ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:ExtractAppIntentsMetadata ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase7--firebase-crashlytics--crashlytics-upload-symbols> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase7--firebase-crashlytics--crashlytics-upload-symbols ->

node: /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/Script-BC11CAE13E2DC45C0B5D946E.sh ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:WriteAuxiliaryFile /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/Script-BC11CAE13E2DC45C0B5D946E.sh ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase6-copy-files> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase6-copy-files ->

node: <Copy /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex> ->

CYCLE POINT ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:Copy /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/AwesomeServiceExtension.appex ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase5--cp--embed-pods-frameworks> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase5--cp--embed-pods-frameworks ->

node: /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/InputFileList-1C3A44BFFC5025545F5E8B2C-Pods-Runner-frameworks-Debug-input-files-d88ddd2ecbce107c5ee125cb56f6064b-resolved.xcfilelist ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:WriteAuxiliaryFile /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/InputFileList-1C3A44BFFC5025545F5E8B2C-Pods-Runner-frameworks-Debug-input-files-d88ddd2ecbce107c5ee125cb56f6064b-resolved.xcfilelist ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase4-thin-binary> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase4-thin-binary ->

node: <execute-shell-script-18c1723432283e0cc55f10a6dcfd9e02f1eee2015e8ff5ebcd27678f788c2826-target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-> ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:PhaseScriptExecution Thin Binary /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/Script-3B06AD1E1E4923F5004D2608.sh ->

node: /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist/ ->

directoryTreeSignature: c ->

directoryContents: /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist ->

node: /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:ProcessInfoPlistFile /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist /Users/shahar/StudioProjects/frontend/apps/users_app/ios/Runner/Info.plist ->

node: /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:Copy /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/AwesomeServiceExtension.appex

Error launching application on Shahar's IPhone.

Any idea?

xcode 15, macos 14 sonoma, cocoapods last version, emulator and phone ios 17
Flutter 3.13.6 • channel stable • https://github.com/flutter/flutter.git Framework • revision ead455963c (6 days ago) • 2023-09-26 18:28:17 -0700 Engine • revision a794cf2681 Tools • Dart 3.1.3 • DevTools 2.25.0
Using
dependencies:
  awesome_notifications_core: ^0.8.1
  awesome_notifications: ^0.8.2
  awesome_notifications_fcm: ^0.8.0

On real phone getting this error
Could not build the precompiled application for the device.
Error (Xcode): Sandbox: rsync.samba(30335) deny(1) file-write-create /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Flutter.framework

Error (Xcode): Sandbox: dart(30315) deny(1) file-write-create /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/.last_build_id

Error (Xcode): Flutter failed to write to a file at "/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/.last_build_id".

Error launching application on Shahar's IPhone.

Solved with this flutter/flutter#128739
disabled ENABLE_USER_SCRIPT_SANDBOXING is working for me.
1.	Open the Xcode project.
2.	Click on the project name in the left sidebar to open the project settings.
3.	Select the target you want to check in the "Targets" section.
4.	Click on the "Build Settings" tab.
5.	In the search bar, type "ENABLE_USER_SCRIPT_SANDBOXING".
6.	If the value of ENABLE_USER_SCRIPT_SANDBOXING is set to "No", then it is disabled. If it is set to "Yes", then it is enabled.

Now getting a different error
Launching lib/main.dart on Shahar's IPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: 9ZU62NBH4Z
Running pod install...
Running Xcode build...
Xcode build done.                                           39.7s
Failed to build iOS app
Could not build the precompiled application for the device.
Error (Xcode): Cycle inside Runner; building could produce unreliable results.
Cycle details:
→ Target 'Runner': ExtractAppIntentsMetadata
○ Target 'Runner' has copy command from '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/AwesomeServiceExtension.appex' to '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex'
○ That command depends on command in Target 'Runner': script phase "Thin Binary"
○ Target 'Runner' has process command with output '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist'
○ Target 'Runner' has copy command from '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/AwesomeServiceExtension.appex' to '/Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex'

Raw dependency cycle trace:

target:  ->

node: <all> ->

command: <all> ->

node: /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/Objects-normal/arm64/ExtractedAppShortcutsMetadata.stringsdata ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:ExtractAppIntentsMetadata ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase7--firebase-crashlytics--crashlytics-upload-symbols> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase7--firebase-crashlytics--crashlytics-upload-symbols ->

node: /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/Script-BC11CAE13E2DC45C0B5D946E.sh ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:WriteAuxiliaryFile /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/Script-BC11CAE13E2DC45C0B5D946E.sh ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase6-copy-files> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase6-copy-files ->

node: <Copy /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex> ->

CYCLE POINT ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:Copy /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/AwesomeServiceExtension.appex ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase5--cp--embed-pods-frameworks> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase5--cp--embed-pods-frameworks ->

node: /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/InputFileList-1C3A44BFFC5025545F5E8B2C-Pods-Runner-frameworks-Debug-input-files-d88ddd2ecbce107c5ee125cb56f6064b-resolved.xcfilelist ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:WriteAuxiliaryFile /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/InputFileList-1C3A44BFFC5025545F5E8B2C-Pods-Runner-frameworks-Debug-input-files-d88ddd2ecbce107c5ee125cb56f6064b-resolved.xcfilelist ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase4-thin-binary> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase4-thin-binary ->

node: <execute-shell-script-18c1723432283e0cc55f10a6dcfd9e02f1eee2015e8ff5ebcd27678f788c2826-target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-> ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:PhaseScriptExecution Thin Binary /Users/shahar/Library/Developer/Xcode/DerivedData/Runner-fnugzdxlcopubvahlxgeodnkykmz/Build/Intermediates.noindex/Runner.build/Debug-iphoneos/Runner.build/Script-3B06AD1E1E4923F5004D2608.sh ->

node: /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist/ ->

directoryTreeSignature: c ->

directoryContents: /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist ->

node: /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:ProcessInfoPlistFile /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/Info.plist /Users/shahar/StudioProjects/frontend/apps/users_app/ios/Runner/Info.plist ->

node: /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug:Copy /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/Runner.app/PlugIns/AwesomeServiceExtension.appex /Users/shahar/StudioProjects/frontend/apps/users_app/build/ios/Debug-iphoneos/AwesomeServiceExtension.appex

Error launching application on Shahar's IPhone.

Any idea?

Having the same issue here on Sonoma and the latest iOS, even with the proposed solution:


a problem with php7

My website is magento1.9.2,after i upgrade php to 7.0.0,the lazyload not work fine,the images not show up.

Lazy Load is a JavaScript plugin. It has nothing to do with PHP. Probably something change on Magento side.


fix: expose ability to set logger level

Summary
The current logger is unable to change the logging level
The class structure did not seem to be set up correctly. Tracing the logic from the existing require('neotest.logging'):set_level('WARN'):

require('neotest.logging') resolves to the result of Logger:new()
Logger:new() effectively returns setmetatable(logger, Logger)
There is no __index field on the Logger metatable, so looking up set_level will return nil

The fix is to setmetatable(logger, { __index = Logger }), and to also set the _level onto the logger object instead of the Logger class. It kind of doesn't matter because they're both effectively singletons, but it's technically more correct? ¯\(ツ)/¯
I also slipped in a call to set the default log location to stdpath('log') if available (upcoming in nightly, see https://github.com/neovim/neovim/pull/15583).
Would potentially be nice to set this from a config option, but I think that's outside the scope of this PR.
Test plan
In init.lua added:
require("neotest.logging"):set_level("WARN")
require("neotest").setup({})

Ran tests
Observed no output in ~/.cache/nvim/neotest.log
Tested again without the set_level line, and confirmed that the debug logs appear in the logfile.

Thanks for the PR! Logging was completely thrown in without much thought, need to tidy it up a bit anyway


SIP: Opentelemetry integration proposal

Rendered.
Signed-off-by: Bogdan Vlad<EMAIL_ADDRESS>

Going to go ahead and close this SIP as this work is now being tracked in #2293, #2303 and #2316.


-1 entries in neighbor_graph

I get some -1 entries in the kNN graph when I build it on a sparse matrix with cosine distance. Is this intentional? Does -1 mean X.shape[0]-1? When I run query(X), I don't get any negative elements. E.g.:
X = scipy.sparse.csr_matrix(np.random.randn(10000,1247)>3)
nn = pynndescent.NNDescent(X, metric='cosine', n_neighbors=15)

Now nn.neighbor_graph[0] has some values equal to -1 but nn.query(X, k=15)[0] does not.
Update: Forgot to say that I do get a warning "UserWarning: Failed to correctly find n_neighbors for some samples.Results may be less than ideal. Try re-running withdifferent parameters." from NNDescent. Maybe that's what -1 indicate? But then query() does not return any negative elements and does not complain. How should one approach this?

So looking into it a bit more, it seems what whenever a row in neighbor_graph contains -1 values, the corresponding query(X) row is meaningless and contains one element (always the same) repeated 15 times. And whenever a row in neighbor_graph does not contain -1 values, the corresponding query(X) row looks fine.
So I assume that -1 means that NNDescent failed as per UserWarning and subsequent query returns meaningless results for these points.
This happens with my real (non-simulated) data, but at the same time I can run UMAP on it (same metric, same number of neighbors) and it outputs something that appears sensible. So what does UMAP do with the points that NNDescent fails to identify neighbors of?

Any -1's are ignored by UMAP, so we just end up with fewer than expected neighbors in those cases. Generally this means those points end up being outliers.

Oh I see. Thanks. The warning text is

UserWarning: Failed to correctly find n_neighbors for some samples.Results may be less than ideal. Try re-running withdifferent parameters.

Is there a specific advice on which parameters one could try to adjust?
I get some points (using n_neighbors=15) with all 15 values equal to -1, so no neighbors of these points could be found. It feels like it is a bit dangerous to continue with UMAP/tSNE based on such a kNN graph.

For your information, I've been looking at this dataset: https://johnhw.github.io/umap_primes/index.md.html. Turns out, this (all neighbors -1) happens for around 10% of points. It seems these are mostly prime numbers and UMAP mostly keeps them where they were at initialization.

I see. This makes sense. Okay, I guess this is not an issue with Pynndescent, so I'm closing it.

Hey Leland, has anything changed in the recent version of pynndescent' regarding this behaviour? I updated to the last version and noticed that I do not get any -1' values in the index anymore, using the same data and code as before.

I don't believe anything changed in terms of how missing entries are handled. There were some changes in how cosine gets computed that makes it less likely to fail to find neighbors.

I see, thanks. It works very effectively: e.g. in the prime factorization dataset I don't get any single -1 anymore out of N=100,000.

Indeed; they may not be the best neighbors, but they are what can be found.


Ticketit with places

Updated and uploaded files for the "places" table

i have a litle issue for editing tickets:
it do not retrieve place's color to show the colorful place name, that's what i am working around.
After that, i tried to insert places to dashboard, but i was not able at this moment. But it will be necessary once we have place's tickets to meassure.

Still too many files included, but never mind, I'll try to handle it manually. But not now, as i'm leaving for holiday. I'll get back to this in 7-10 days.

Do i have to do some coding to solve the files conflict at this branch, if yes, let me know.

That would be great! Sorry, for having this open for this long, besides my studies I have very limited time to maintain this project.

Hi there, i´ve made some updates in dashboard viewing for places pizza counter. just waiting for the integration merge, to add the features. Regards!

I think this is an installation of Laravel, this can't be merged to ticketit package.


feat: add GH action to scan files in repo on PR basis

Description
Add new GitHub Action to do vulnerability scanning on static file in the repo on any PR
Result stored as artifacts in json format can be downloaded from Action runs' Artifacts zip file.
Only record if vuln in high or critical level
How Has This Been Tested?
Create a PR in forked repo https://github.com/zdtsw/odh-dashboard/actions/runs/4799075808
Action was run and result can be download as artifacts
Test Impact
N.A
Request review criteria:

[x] The commits have meaningful messages (squashes happen on merge by the bot).
[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work
[ ] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

Idia itself is very good, however, would this not be better-placed in odh-manifests? Dashboard image-reference is part of the recipes there, too.

Idia itself is very good, however, would this not be better-placed in odh-manifests? Dashboard image-reference is part of the recipes there, too.

The reason I picked up dashboard than any other ODH repo is mostly based the language it uses.
And I would like to see how community feel about enable such tool.
My idea is to have it in as many repo as possible.
But on the other side, I am not sure it is better on the image level or on the source code level.
So the PR itself is more to open a conversation and discuss from here.

@zdtsw can you rebase main please? and before mergin, can we take a look, it seems that everything is ok but i would love to have more context

@zdtsw can you rebase main please? and before mergin, can we take a look, it seems that everything is ok but i would love to have more context

@zdtsw can you rebase main please? and before mergin, can we take a look, it seems that everything is ok but i would love to have more context

I did a rebase and now think it need approve to run Action https://github.com/opendatahub-io/odh-dashboard/actions/runs/5175998579
Also I added more context in the commit message. Let me know if anything not clear.

@zdtsw Running now, let's see!

Ok it seems to be working fine!

@andrewballantyne everything seems ok here, should we merge it?


dotnet ARM64 support

Current dotnet containers are only supporting x86. Based on some work done, dotnet images can be build to support arm64, but still there some dependency on Omnisharp Extension in order to have a complete user experience.
This issue was opened to track the OmniSharp dependency.

Testing with Omnisharp 1.24.0-beta1 with various images, it was possible to debug inside the dotnet arm64 container.
Starting OmniSharp server at 1/4/2022, 9:17:03 PM
    Target: /root

OmniSharp server started with .NET 6.0.101
.
    Path: /root/.vscode-server/extensions/ms-dotnettools.csharp-1.24.0/.omnisharp/1.38.0-net6.0/OmniSharp.dll
    PID: 5473

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on Unknown 0.0 (Unknown)
[info]: OmniSharp.Services.DotNetCliService
        Checking the 'DOTNET_ROOT' environment variable to find a .NET SDK
....

Images:

6.0-bullseye-slim-arm64v8
5.0-bullseye-slim-arm64v8
3.1-bullseye-arm64v8

In case of dotnet 6.0, changes need to be added to the container's vscode settings to use 6.0 features.
.vscode-server/data/Machine/settings.json

{
	"omnisharp.useModernNet": true
}

Relates to: <Codespaces | Remote - Containers | Both>

Reference: https://github.com/microsoft/vscode-dev-containers/issues/558

Since OmniSharp 1.24 is now released - do we expect the dotnet vscode images to be released for ARM as well?

@juzuluag I know you hit some problems with 1.24 and arm64 Linux here (which is what the container would run), correct?  Or has that been resolved since the beta?

@juzuluag I know you hit some problems with 1.24 and arm64 Linux here (which is what the container would run), correct? Or has that been resolved since the beta?

Hi @Chuxel. I faced issues using 1.23.18-beta2 and not with 1.24.0-beta1. I haven't try the latest (1.24.0)


[rstream-log] Fix "similar-code" issue in packages/rstream-log/src/logger.ts

Similar blocks of code found in 5 locations. Consider refactoring.
https://codeclimate.com/github/thi-ng/umbrella/packages/rstream-log/src/logger.ts#issue_5d5c680a5ef8cd0001000a60

Do this on the feature/rstream-opts branch...


remove 'test' prefix snapshots names

Summary
More information in this issue: https://github.com/facebook/jest/issues/2839

@rubenmoya @cpojer so I've had a moment to take a look at that and it turns out that everything's fine with snapshots making obsolete tests. What's not right, is that -u flag is not passed to examples and some of our integration_tests.
This is something that we should fix, but it's not relevant to this PR.
As a workaround run jest -u in these dirs:
examples/react-native
integration_tests/transform/multiple-transformers

Ohhh yes, I get what you are saying, you are right. Thanks so much for digging in, phew, no bugs in Jest then, just our set up.

Thanks @rubenmoya for working on this!

@cpojer Thank you for the help! :)


cached base layers can be stale

if a layer is from: type:docker, the base layer is cached, and nothing currently checks if it is stale wrt. to the contents of the url.
that'd be handy

I believe this is fixed now; we do a query every time.


KeyVault secrets are passed to module w/o secure() decorator.

This app creates secrets in bulk, but passes those secrets from main.bicep w/o using the secure decorator.  Those secrets with therefore be in plaintext in the Azure deployment.
Add secure() here.
https://github.com/Azure-Samples/azure-search-openai-demo-csharp/blob/fb1ca3248e693ea7acb04740c97526c5a49c82eb/infra/core/security/keyvault-secrets.bicep#L3
If that isn't possible, then remove the keyvault-secrets.bicep file and create them with individual module references and a secure decorator on the key.

@jongio Can you share an example on adding secure decorator to individual module?

I'd go this route:

If that isn't possible, then remove the keyvault-secrets.bicep file and create them with individual module references and a secure decorator on the key.

I'd go this route:

If that isn't possible, then remove the keyvault-secrets.bicep file and create them with individual module references and a secure decorator on the key.

@jongio do we have a sample of this?

@LittleLittleCloud are we okay to close this one?

I'd remove "secrets" file and set each one individually so they are passed securely.


Providing support for gollvm

What is the problem you're trying to solve
Providing extensive support for gollvm , which offers LLVM back-end - while the same front-end is used, for Golang.
Main repo, sub-projects.
Describe the solution you'd like
Regular building experiments, bug reports.
Additional context
@thanm @cherrymui could speak for gollvm project.
Ivan

Can you elaborate why is this needed?

@mxpv , people might be interested in another compiler (not GCC).
Also there are some common package dependencies, between containerd and other CNCF/LF projects (including cri-o, k8s, docker) - so I am opening this issue to cross-reference against bugs, which are related to those packages/projects.
If you have are skeptic  - please explain yourself. And if you do not believe in that diversifying compiler usage would bring benefit to containerd project - share your arguments.

@haircommander , please join the review process

@advancedwebdeveloper as a community project, we rely on contributions from the community to add support for other tools and projects needed by the community. This sort of change would need to be broken down into the changes which are needed to get it supported. We cannot make a judgement as to whether those changes would be accepted without knowing what they are. I suggest when opening an issue like this you break it down into individual issues which cause gollvm not to work today. Otherwise, at least provide a strong reason for supporting it such that someone else in the community will be motivated to take on the effort. Asking why is not about being skeptical here, it is about having open issues which can be tracked and progressed.


adopt ulimits on TravisCI to reflect important system settings

according to ES 5.0 upgrade it is necessary to increase the limits of
open file descriptors and adapt the number of threads.
https://www.elastic.co/guide/en/elasticsearch/reference/5.4/system-config.html

Could this have introduced the errors here: https://travis-ci.org/crate/crate/builds/235764426#L1788 ?

@mfussenegger yes, I have reverted the nr of processes limit already https://github.com/crate/crate/pull/5629


Improve performance of aromaticity detection for large molecules

For very large molecules, the repeated counting of total number
of ring atoms is a bottleneck in aromaticity detection! This
pulls that total count out of the function that is checking
aromaticity of a particular ring set.
For an example molecule (PDB ID: 3EOH), this basically
removes aromaticity detection from a performance profile
of sanitization. (on my laptop, makes sanitization about
1.5s faster for 3EOH).
My only hesitation with this commit is that the check
that requires knowledge of the total number of ring
atoms may not be needed at all?

I can reproduce the test failures, and agree that for the molecule that you mention this makes sense. Let me read through the test to understand what I can, and I'll post and update (and change the title and description of this PR).

I can reproduce the test failures, and agree that for the molecule that you mention this makes sense. Let me read through the test to understand what I can, and I'll post and update (and change the title and description of this PR).

I'm not sure the title should change. I do think it's worth adding an explicit test for #3256. If it helps, I can do a PR for that (and the fix to the MQN tests)

@d-b-w how do you want to proceed with this?

I'm happy to address this - I just had a couple of other things on my plate last week.
I understand why the old code was problematic now - it was a check for done atoms, rather than done bonds.

I've updated the commit to completely remove the "done atoms" check in Aromaticity.cpp. This addresses the performance and accuracy issues discussed in this case. I also updated the tests, and added a new test in catch_graphmol.cpp to explicitly actively check these systems for correct envelope aromaticity.
I did notice one odd thing... For the test that I had to update - the line in aromat_regress.txt says:
 N12C(N3N=C(C)C=C(N4C1=CC(C)=N4)3)=C(C=O)C(=N2)C	Cc1cc2n(n1)c1cc(C)nn1c1c(C=O)c(C)nn21	15	[0, 1, 2, 3, 4, 6, 7, 8, 9, 10, 11, 13, 14, 17, 18]

But before this change, if I render this mol back as SMILES I get:
Cc1cc2n(n1)-c1cc(C)nn1-c1c(C=O)c(C)nn1-2

(note the explicit single bonds between aromatic atoms). Was adding single bonds between aromatic atoms a new fix?

Hi @d-b-w : the CI failures are real ones this time.

ugh! I originally wrote the test in Python and then got sloppy when translating. Sorry about that.
The current failure is in a java test. The same test passes on Mac. It looks like this is the assertion that fails:

https://github.com/rdkit/rdkit/blob/master/Code/JavaWrappers/gmwrapper/src-test/org/RDKit/DiversityPickerTests.java#L163

Does that seem related to this?

oooook. I had to kill this after a minute or two runtime on a nanotube system. Looks like we need some sort of kill switch.
When I next have a chance, I'll play with using bonds that are complete rather than atoms.

ugh! I originally wrote the test in Python and then got sloppy when translating. Sorry about that.
The current failure is in a java test. The same test passes on Mac. It looks like this is the assertion that fails:

Failures in that test are generally not real. The test has a random component to it (intentionally) and that occasionally results in a failure. I restarted that failed build on Azure DevOps

I think it would be good to hold off on the merge until I figure out whether this causes a hang in a system that ran in finite time before.

@d-b-w : any news here?

I think that the test failures are all in doctest and are unrelated:
Exception occurred:
  File "/usr/share/miniconda/envs/rdkit_build/lib/python3.7/typing.py", line 969, in get_type_hints
    base_globals = sys.modules[base.__module__].__dict__
KeyError: 'Boost.Python'

I'll merge master, because I think that there were some changes to the docs, and try again.

I've done the testing that I need to on this to feel good about it.

I think that the test failures are all in doctest and are unrelated:
Exception occurred:
  File "/usr/share/miniconda/envs/rdkit_build/lib/python3.7/typing.py", line 969, in get_type_hints
    base_globals = sys.modules[base.__module__].__dict__
KeyError: 'Boost.Python'

I'll merge master, because I think that there were some changes to the docs, and try again.

yeah, those failures were due to a problem with sphinx 3.2. The changes to master cleared them up

Thanks @d-b-w !


Update pyslds pip install code

Last updated last summer!

Good point! Just updated pyslds (last updated last summer) and added pyslds (this repo) to pypi.


LPAL-1100 Hide sensitive arguments from log

Purpose
LPAL-1100
Approach
See ticket.
Learning
Psalm plugin authoring.
Checklist

[X] I have performed a self-review of my own code
[X] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[X] I have added tests to prove my work
[X] I have added mandatory tags to terraformed resources, where possible
[X] If I have a new OPG component dependency, I have updated the metadata.json with the repo location.
[X] If I added a package.json or composer.json, I also made sure this is included in the script in .github/workflows/dependabot-update.yml
[ ] The product team have tested these changes

As this depends on LPAL-1078, do not merge until that branch has been.


Filter styling updates

Styled the UI a little bit and added dark & light themes.
Also made it so that it doesn't try to load a new filter until the previous one has finished rendering. Otherwise you can fire off like 10 requests and some of them seem to take quite a while so it really bogged the machine down.
Here's how it should look...

Please don't merge this in! I will open up a new PR with these changes as well as fixes for the issues mentioned in the original PR.

@gideonthomas okay, got it

Feel free to close this as your commit has been merged (with these fixes) into mozilla/brackets


Add a view that shows a short one line height band with text for messages

Large retail sites use these often to talk about free shipping and other promotions without using too much space.

Should be full width of page.


Issue/110 - Add search functionality to my lists page

Description
This pull request introduces a search feature to the Lists page, enabling users to filter and find lists by name as the number of lists increases.
Resolves issue #110
Result
https://github.com/user-attachments/assets/7ac9bbfb-1020-4515-81af-f85520a2a41e

@AshuKr22
Are the changes fine, or should I make some changes

@daccotta If my pr is fine, please label it with gssoc-ext and level


Bug: The login button is not blocked when the password or login field is empty

Fixed by b6bb05f commit


Propose hosting on HuggingFace/source.coop

Hi
Currently using this package - note it is scraping a website which is probably not ideal in the long term as urls can change etc.
Suggest instead/as well as hosting on HuggingFace/source.coop
Cheers

The script hung at 59%, and restarts at 0 - another reason to put as a direct download :-)


Exception with avio_alloc_context_read_packet::Invoke

Managed Debugging Assistant 'CallbackOnCollectedDelegate'
  Message=Managed Debugging Assistant 'CallbackOnCollectedDelegate' : 'A callback was made on a garbage collected delegate of type 'FFmpeg.AutoGen!FFmpeg.AutoGen.avio_alloc_context_read_packet::Invoke'. This may cause application crashes, corruption and data loss. When passing delegates to unmanaged code, they must be kept alive by the managed application until it is guaranteed that they will never be called.'

I am unsure why but after a sound is done playing I guess the delegate is being called by avio. It doesn't happen all the time. I have seen it twice today.
I added lock around the code in the fixed statement. This should prevent any dispose from being called before the code is done executing.
The system will not let me ffmpeg.avio_context_free(&Decoder._format->pb); It causes a CTD when ever I try.
I hope the lock helps. The error is so rare.
The only reason I am using avio_read_content. Is that it is the only way I found to read ADPCM sounds out of memory.

I was thinking it could be related to the Task I added. It's possible the Delegate It's complaining about is something internal to ffmpeg.autogen. He uses delegates to reference various ffmpeg calls. Though I only use avio explicitly in one place. But unsure if it gets called automatically or not.

I think i fixed this. I had a delegate defined in a method. And sometimes the delegate would get collected before we were done with it. Though sometimes this would never happen. So now the delegate is a field of the class so it should last as long as the class does. Oh and I upgraded ffmpeg.autogen to latest version incase that had something fixed in it. I plan to test linux before my next pull request.


upgrade python version in dockerimage

can we change to 3.8  without minor version to get newer base?
https://github.com/apache/superset/blob/master/Dockerfile#L21

Converting this to a Q&A Discussion since it's not a bug, per se.


Consolidate sort and external_sort, consolidate N-way merge sort

Which issue does this PR close?

Closes #1571 and #1572.
Rationale for this change

in_mem_sort and SortPreservingMergeStream share similar goal.
We should have only a single sort operator that does in-memory sorting if it has enough memory budget but then spills to disk if needed.

What changes are included in this PR?

Remove in_mem_sort, use heap_sort in SortPreservingMergeStream
Duplicate tests SortExec into ExternalSort, retain spill-related tests in ExternalSort.

TODO

[ ] Benchmark external sort, guarantee no performance regression.
[x] Remove SortExec and rename ExternalSortExec, keep only one sort at last.

Are there any user-facing changes?

No

Thank you @yjshen  -- this looks awesome -- I will try and review this carefully, but likely won't have time until tomorrow

I first run bench sort_limit_query_sql
cargo criterion --bench sort_limit_query_sql

and witness no noticeable difference between this branch with which it originates:
With this PR:
sort_and_limit_by_int   time:   [3.3633 ms 3.4736 ms 3.6268 ms]

sort_and_limit_by_float time:   [3.3644 ms 3.4726 ms 3.6342 ms]

sort_and_limit_lex_by_int
                        time:   [3.7431 ms 4.1084 ms 4.6626 ms]

sort_and_limit_lex_by_string
                        time:   [3.4665 ms 3.6071 ms 3.7919 ms]

Without this PR:
sort_and_limit_by_int   time:   [3.3156 ms 3.3392 ms 3.3626 ms]

sort_and_limit_by_float time:   [3.2272 ms 3.6257 ms 4.3373 ms]

sort_and_limit_lex_by_int
                        time:   [3.4235 ms 3.4393 ms 3.4558 ms]

sort_and_limit_lex_by_string
                        time:   [3.3962 ms 3.4127 ms 3.4298 ms]

Flamegraph with this PR:

After a quick investigation with flamegraph, nearly 70% of the time is spent on SortKeyCursor::compare, which deteriorate to item wise comparison, compared to arrow sort kernel which is compared on Array.
only nearly 40% of the time is sort related:

The logic for ExternalSort:

get batch from input, sort it, and buffer it in memory
when memory threshold meet, do in-mem-sort to do "N-way merge" and spill it to file
repeat 1 and 2 until input is exhausted.
another "N-way merge": merge current in-mem buffered batches as well as all spills, to get the total order.

Currently, I've unified all "N-way merge" into SortPreservingMergeStream. Inside SPMS, I construct a min-heap size of "N" to minimize merging memory consumption. However, the performance deterioration of item-wise heap compare seems to overweight its benefits of memory saving.
I think it is probably worth porting https://github.com/jorgecarleitao/arrow2/blob/main/src/compute/merge_sort/mod.rs to avoid too much memory consumption during combine_batches in the original sort implementation.
cc @alamb @jorgecarleitao @houqp @tustvold.

Starting to check this out @yjshen -- thank you for the detailed analysis so far

more than 70% of the time is spent on SortKeyCursor::compare, which deteriorates to item-wise comparison, compared to Arrow sort kernel which is compared on Array.

There is a bunch of other overhead in that column I suspect we could avoid with some additional engineering (follow on PRs) such as the use of an RWLock to defer the comparator initialization, for example

TPC-H sf=1 sort_extendedprice_discount.    [combine_and_sort method]
No differences for the external_sort compared to the previous sort.
./target/release/tpch benchmark datafusion --path ./data --format tbl --query 1 --batch-size 10240 --partitions 1

I changed q1 locally to run directly from tpch program to:
select
    l_returnflag,
    l_linestatus,
    l_quantity,
    l_extendedprice,
    l_discount,
    l_tax
from
    lineitem
order by
    l_extendedprice,
    l_discount;

query plan:
SortExec: [l_extendedprice@3 ASC NULLS LAST,l_discount@4 ASC NULLS LAST]
  ProjectionExec: expr=[l_returnflag@4 as l_returnflag, l_linestatus@5 as l_linestatus, l_quantity@0 as l_quantity, l_extendedprice@1 as l_extendedprice, l_discount@2 as l_discount, l_tax@3 as l_tax]
    CsvExec: files=[./data/lineitem.tbl], has_header=false, limit=None

W/ this PR:
Running benchmarks with the following options: DataFusionBenchmarkOpt { query: 1, debug: false, iterations: 3, partitions: 1, batch_size: 10240, path: "./data", file_format: "tbl", mem_table: false }
Query 1 iteration 0 took 7239.6 ms
Query 1 iteration 1 took 7357.7 ms
Query 1 iteration 2 took 6668.1 ms
Query 1 avg time: 7088.46 ms

W/o this PR:
Running benchmarks with the following options: DataFusionBenchmarkOpt { query: 1, debug: false, iterations: 3, partitions: 1, batch_size: 10240, path: "./data", file_format: "tbl", mem_table: false }
Query 1 iteration 0 took 7135.3 ms
Query 1 iteration 1 took 7462.2 ms
Query 1 iteration 2 took 7484.8 ms
Query 1 avg time: 7360.79 ms

Thanks @tustvold for the detailed review. I've first quick fix the async and documentation-related comments. For deadlock / mutex / hangup parts, let me think it over again.

@yjshen  is this PR ready for another review, or are you planning more changes to it?

@alamb I find some of my messages for you are lost, maybe because of the network.
Yes, I think the PR is ready for another round of review now.

for SortKeyCursor:

AtomicUsize is introduced for sharing the SortKeyCursors in a BinaryHeap as well as in a Vec of cursors. I can think of deduplicating its usage and only keeping it in heap, but let me do in a follow-up PR.
batch_comparators: RwLock it's required to make SortKeyCursor impl PartialOrd and Ord, since the original cmp in SortKeyCursor has the mut signature, but Ord needs it to be immutable.  Do you have any suggestions on simplifying this?

for AggregatedMetricsSet:

I don't really understand this code -- it appears to be merging in new (zero'd) metrics to sef.all_metrics`? Why not just return self.all_metrics ?

This means to aggregates all metrics during a complex operation, which is composed of multiple stages and each stage reports its statistics separately. For the sort case here: when the dataset is more significant than available memory, it will report multiple in-mem sort metrics and final merge-sort metrics from SortPreservingMergeStream.
Therefore, We need a separation of metrics for which are final metrics (for output_rows accumulation), and which are intermediate metrics that we only account for elapsed_compute time.  So I create a zero'd metrics here and gather elapse_time and output_rows separately.

Thanks @yjshen  -- I'll put this on my review queue for first thing tomorrow

FYI @houqp  @Dandandan @liukun4515  @andygrove  -- while @yjshen has done performance analysis and this change should not affect the performance of queries that stay all in memory, there is some possibility of regression. Let us know if you see some and we'll investigate.

Epic work @yjshen  -- thanks again for all the work and thank you @tustvold  for the help reviewing


WIP readme explanation of env vars

#43 . I'm actually not sure myself what the last 2 env vars are, but I think this is a good starting point. I tried to be as brief, while still providing some info, based on what I was confused about personally when trying to set up a dev environment. Feedback is much appreciated

If this PR already touches the README, maybe also fix that it's supposed to be env $(cat .env) instead of only env $(.env).

If this PR already touches the README, maybe also fix that it's supposed to be env $(cat .env) instead of only env $(.env).

Added

RE attachment cache stuff:
To log message attachments (images, etc) we have to locally cache them, as discord doesn't let us download them after a message has been deleted. thus, there is a cache directory and max-size for that. if the max-size is exceeded, it'll start deleting old attachments

Thanks!


Suggestion: map syndicate

include the syndicate image with the best choices

You can bind a site with this image to keyboard shortcut using 'bookmarks' tab in the settings.

ok, i will try, thank you very much

You can bind a site with this image to keyboard shortcut using 'bookmarks' tab in the settings.

Thanks! Closed.