Can't send mails from clients like Thunderbird

I had a mailserver running for like a year without any issue. Recently i moved the project from one host to another (copied the whole configuration and mail files). After the DNS was updated everything worked like expected on the new host. Except one thing:
I can't send Mails from a client using a tool like Thunderbird
Every time when i write and send an email within thunderbird i immediately receive an email like this:
A message from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>
was considered unsolicited bulk e-mail (UBE).

Our internal reference code for your message is 04499-12/ZLlB5XaNH1eJ

The message carried your return address, so it was either a genuine mail
from you, or a sender address was faked and your e-mail address abused
by third party, in which case we apologize for undesired notification.

We do try to minimize backscatter for more prominent cases of UBE and
for infected mail, but for less obvious cases some balance between
losing genuine mail and sending undesired backscatter is sought,
and there can be some collateral damage on either side.

First upstream SMTP client IP address: [XXX.211.186.169]
  p4fd3bxx9.dip0.t-ipconnect.de
According to a 'Received:' trace, the message apparently originated at:
  [XXX.211.186.169],

Return-Path<EMAIL_ADDRESS>From: Frederic<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>Subject: Test

Delivery of the email was stopped!

Where IP address: [XXX.211.186.169] was the IP i got assigned that day from my ISP (Telekom) I put that IP in a blacklist checker and it was listed in some of the lists.
Everything else works like expected. I can receive mails like as previously. And all the filters and rules work like a charm.
I noticed a strange behavior that i can't completely explain why:
I am able to send mails if i am using a webmailer or my phone to send the mails. Only when sending Mails from a local Mail Client (Thunderbird/Outlook) it fails with the message above.
Context
Here is the corresponding log output when i try to send a mail from a local mail client:
mail    | Feb  7 21:50:19 mail postfix/submission/smtpd[28737]: F2B847D53E: client=p4fd3bxx9.dip0.t-ipconnect.de[XXX.211.186.169], sasl_method=PLAIN<EMAIL_ADDRESS>mail    | Feb  7 21:50:20 mail postfix/sender-cleanup/cleanup[28741]: F2B847D53E<EMAIL_ADDRESS>mail    | Feb  7 21:50:20 mail postfix/sender-cleanup/cleanup[28741]: F2B847D53E: replace: header MIME-Version: 1.0 from p4fd3bxx9.dip0.t-ipconnect.de[XXX.211.186.169]<EMAIL_ADDRESS><EMAIL_ADDRESS>proto=ESMTP helo=<[<IP_ADDRESS>]>: Mime-Version: 1.0
mail    | Feb  7 21:50:20 mail opendkim[287]: F2B847D53E: DKIM-Signature field added (s=mail, d=mydomain.de)
mail    | Feb  7 21:50:20 mail postfix/qmgr[1089]: F2B847D53E<EMAIL_ADDRESS>size=341, nrcpt=1 (queue active)
mail    | Feb  7 21:50:20 mail postfix/submission/smtpd[28737]: disconnect from p4fd3bxx9.dip0.t-ipconnect.de[XXX.211.186.169] ehlo=2 starttls=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=8
mail    | Feb  7 21:50:20 mail dovecot: imap(myuser@mydomain.de)<27502><XtmYdgKeKdFP07qp>: Logged out in=1768 out=3094 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
mail    | Feb  7 21:50:20 mail postfix/smtpd[28752]: connect from localhost[<IP_ADDRESS>]
mail    | Feb  7 21:50:20 mail postfix/smtpd[28752]: DFFB37D9C7: client=localhost[<IP_ADDRESS>]
mail    | Feb  7 21:50:20 mail postfix/cleanup[28753]: DFFB37D9C7<EMAIL_ADDRESS>mail    | Feb  7 21:50:20 mail postfix/qmgr[1089]: DFFB37D9C7: from=<>, size=3809, nrcpt=1 (queue active)
mail    | Feb  7 21:50:20 mail postfix/smtpd[28752]: disconnect from localhost[<IP_ADDRESS>] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
mail    | Feb  7 21:50:20 mail amavis[4499]: (04499-12) Blocked SPAM {BouncedOpenRelay,Quarantined}, [XXX.211.186.169]:53930 [XXX.211.186.169]<EMAIL_ADDRESS>-><EMAIL_ADDRESS>quarantine: Z/spam-ZLlB5XaNH1eJ.gz, Queue-ID: F2B847D53E, Message-ID<EMAIL_ADDRESS>mail_id: ZLlB5XaNH1eJ, Hits: 7.358, size: 840, 798 ms
mail    | Feb  7 21:50:20 mail postfix/smtp[28743]: F2B847D53E<EMAIL_ADDRESS>relay=<IP_ADDRESS>[<IP_ADDRESS>]:10024, delay=0.98, delays=0.16/0.02/0.01/0.79, dsn=2.5.0, status=sent (250 2.5.0 Ok, id=04499-12, BOUNCE)
mail    | Feb  7 21:50:20 mail postfix/qmgr[1089]: F2B847D53E: removed

Here is the log output when using my phone with the outlook app installed (phone using wlan from the same network the thunderbird client is located in). Keep an eye on the connect from unknown[XXX.125.138.24]. So somehow the outlook app changes the IP address which in the end talks to my mailserver (because it is obviously not my dynamic assigned one like in the previous log output). Therefore the mail is accepted and delivered as the used IP is not listed anywhere:
mail    | Feb  8 22:34:40 mail postfix/submission/smtpd[17652]: connect from unknown[XXX.125.138.24]
mail    | Feb  8 22:34:40 mail postfix/submission/smtpd[17652]: Anonymous TLS connection established from unknown[XXX.125.138.24]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
mail    | Feb  8 22:34:40 mail postfix/submission/smtpd[17652]: DE0A27D9E5: client=unknown[XXX.125.138.24], sasl_method=LOGIN<EMAIL_ADDRESS>mail    | Feb  8 22:34:40 mail postfix/sender-cleanup/cleanup[17653]: DE0A27D9E5<EMAIL_ADDRESS>mail    | Feb  8 22:34:40 mail postfix/sender-cleanup/cleanup[17653]: DE0A27D9E5: replace: header MIME-Version: 1.0 from unknown[XXX.125.138.24]<EMAIL_ADDRESS><EMAIL_ADDRESS>proto=ESMTP helo=<mail.outlook.com>: Mime-Version: 1.0
mail    | Feb  8 22:34:40 mail opendkim[287]: DE0A27D9E5: DKIM-Signature field added (s=mail, d=mydomain.de)
mail    | Feb  8 22:34:41 mail postfix/qmgr[1088]: DE0A27D9E5<EMAIL_ADDRESS>size=919, nrcpt=1 (queue active)
mail    | Feb  8 22:34:41 mail postfix/smtpd[17324]: connect from localhost[<IP_ADDRESS>]
mail    | Feb  8 22:34:41 mail postfix/smtpd[17324]: C30B47D9E6: client=localhost[<IP_ADDRESS>]
mail    | Feb  8 22:34:41 mail postfix/cleanup[17317]: C30B47D9E6<EMAIL_ADDRESS>mail    | Feb  8 22:34:41 mail postfix/qmgr[1088]: C30B47D9E6<EMAIL_ADDRESS>size=1637, nrcpt=1 (queue active)
mail    | Feb  8 22:34:41 mail postfix/smtpd[17324]: disconnect from localhost[<IP_ADDRESS>] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
mail    | Feb  8 22:34:41 mail amavis[1089]: (01089-05) Passed CLEAN {RelayedOpenRelay}, [XXX.125.138.24]:58058 [XXX.125.138.24]<EMAIL_ADDRESS>-><EMAIL_ADDRESS>Queue-ID: DE0A27D9E5, Message-ID<EMAIL_ADDRESS>mail_id: Y3l3071d2Plc, Hits: 2.923, size: 1417, queued_as: C30B47D9E6, 774 ms
mail    | Feb  8 22:34:41 mail postfix/smtp[17318]: DE0A27D9E5<EMAIL_ADDRESS>relay=<IP_ADDRESS>[<IP_ADDRESS>]:10024, delay=0.95, delays=0.16/0/0.02/0.77, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[<IP_ADDRESS>]:10025): 250 2.0.0 Ok: queued as C30B47D9E6)
mail    | Feb  8 22:34:41 mail postfix/qmgr[1088]: DE0A27D9E5: removed
mail    | Feb  8 22:34:41 mail dovecot: imap-login: Login<EMAIL_ADDRESS>method=LOGIN, rip=XXX.125.138.24, lip=<IP_ADDRESS>, mpid=17661, TLS, session=<FWAkRhee/qU0fYoY>
mail    | Feb  8 22:34:42 mail dovecot: imap(myuser@mydomain.de)<16631><5CJeNheeRuk0fYoY>: Logged out in=1583 out=14968 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=395 body_count=1 body_bytes=213
mail    | Feb  8 22:34:49 mail postfix/smtp[17660]: connect to mail.otherdomain.de[IP6:4f8:d0a:6403::2]:25: Cannot assign requested address
mail    | Feb  8 22:34:52 mail postfix/smtp[17660]: Trusted TLS connection established to mail.otherdomain,de[IP<IP_ADDRESS>]:25: TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)
mail    | Feb  8 22:34:59 mail postfix/smtp[17660]: C30B47D9E6<EMAIL_ADDRESS>relay=mail.otherdomain.de[IP<IP_ADDRESS>]:25, delay=18, delays=0/0.02/11/6.8, dsn=2.0.0, status=sent (250 OK id=1j0Xkf-0001Dj-If)
mail    | Feb  8 22:34:59 mail postfix/qmgr[1088]: C30B47D9E6: removed
mail    | Feb

So it seems like amavis blocks Mails which are sent from a client at home (from a dynamic IP) as SPAM and therefore i receive the mail above. This would explain why it works if i use a webmail tool to send mails because then its a static IP that is not reported or listed anywhere.
Can anyone help me to identify what the problem is and why all mails i want to send from a mail client are marked as SPAM and not delivered?
Did i miss something important? Is this the expected behavior? If I can understand why this happens i can continue finding a solution how to fix it for me.
Expected Behavior
I should be able to send a mail regardless of the tool/client i use
Actual Behavior
I can only send mails using a webmailer or my phone with mail app (outlook)
Steps to Reproduce

Pull docker container and configure it like listed in my environment
Write an email from a local mail client that uses the dynamic ip from the ISP

Environment

Amount of RAM available: 2GB
Mailserver version used: 2.6.1 (stable)
Docker version used: Docker version 19.03.4, build 9013bf583a
Environment settings relevant to the config:
I have pretty every setting on the default value except for these:

ONEDIR=1
ENABLE_CLAMAV=0
ENABLE_MANAGESIEVE=1

Obviously i have also set the hostname variables etc.
Do you need any further information? Thanks in advance!

You should probably try to get your IP off the spam list(s). Otherwise your messages are likely to get rejected by other servers. However, apart from that I wonder if you really need to send from the public IP? If your mail client uses the internal network inside the firewall instead you can mark that network as trusted and bypass the tests. Finally I think it should be possible to make authenticated messages bypass the tests (which would be ideal here), but I don't remember how to do it. Perhaps someone else can help?

I think you missunderstood something.
I tried to visualize it:
+--------------------+
| VPS in Cloud       |    Blocked SPAM {BouncedOpenRelay,Quarantined},
| Running mailserver +--->[XXX.211.186.169]:53930 [XXX.211.186.169]
| Static IP          |<EMAIL_ADDRESS>-><EMAIL_ADDRESS>+----+---------------+
     ^
     |
     | F2B847D53E: client=p4fd3bxx9.dip0.t-ipconnect.de[XXX.211.186.169]
     |
     |
+----+-------------------------+
| Home PC                      |
| Thunderbird                  |
| Dynamic assigned IP from ISP |
+------------------------------+

So i guess this is the "normal" setup. One rents a VPS in the Cloud with a public static IP and runs its mailserver on it.
So if i try to write an email from the PC at home with thunderbird, thunderbird connects to the mailserver which is seen in the logs (p4fd3bxx9.dip0.t-ipconnect.de is the dynamic public ip my router got assigned that day). It is normal up to this point. But then amavis comes into play and blocks this mail as SPAM before it can be processed further.

 Next to that it is the same condition as with every mail provider regardless of hosting by its own or not

Otherwise your messages are likely to get rejected by other servers.
That is not true in my opinion, bc other mail servers see the ip of my mail server (which is clean) only my mailserver sees the clients dynamic ip and blocks it.

Fair enough. What port are you connecting to? Could it be 25?

I configured the mailserver with certificates and Thunderbird with the STARTTLS option. So Thunderbird is using 587 for smtp and 143 for imap

Right. You should not use 143 (plain text), but that is not the problem here. As you copied the configuration perhaps something is different from how it was? You could perhaps enable DMS_DEBUG and run the two tests again to get more verbose logs? It would also be interesting to see your other options. You can of course obfuscate sensitive ones.

So i should use 993 for IMAP and 465 for SMTP? (Thanks for the hint!)
I will set DMS_DEBUG=1 and run the test again when i am back home and then provide the output here.
For the meantime here is the content of my docker-compose.yaml:
# Ansible managed: File is managed by Ansible. Manual changes will be overwritten!
version: '2'
services:
  mail:
    image: tvial/docker-mailserver:stable
    restart: always
    ports:
      - "25:25"
      - "143:143"
      - "587:587"
      - "4190:4190"
    volumes:
      - ./data/maildata:/var/mail
      - ./data/mailstate:/var/mail-state
      - ./data/config:/tmp/docker-mailserver/
      - /etc/letsencrypt:/tmp/ssl:ro
      - /etc/localtime:/etc/localtime:ro
    environment:
      - SSL_CERT_PATH=/tmp/ssl/live/mail.****/fullchain.pem
      - SSL_KEY_PATH=/tmp/ssl/live/mail.****/privkey.pem
      - DMS_DEBUG=0
      - ENABLE_CLAMAV=0
      - ONE_DIR=1
      - ENABLE_FAIL2BAN=1
      - ENABLE_MANAGESIEVE=1
      - POSTMASTER_ADDRESS=****@****
      - REPORT_RECIPIENT=1
      - REPORT_INTERVAL=daily
      - SSL_TYPE=manual
      - SPOOF_PROTECTION=1
      - POSTFIX_MAILBOX_SIZE_LIMIT=2147482548
      - POSTFIX_MESSAGE_SIZE_LIMIT=52428800
      - ENABLE_SPAMASSASSIN=1
      - SA_TAG=2.0
      - SA_TAG2=6.31
      - SA_KILL=6.31
      - SA_SPAM_SUBJECT=****SPAM****
      - ENABLE_POSTGREY=1
      - POSTGREY_DELAY=240
      - POSTGREY_MAX_AGE=35
      - POSTGREY_AUTO_WHITELIST_CLIENTS=2
      - POSTGREY_TEXT=Delayed by postgrey
    hostname: mail
    domainname: ****
    container_name: mail
    dns: <IP_ADDRESS>
    cap_add:
      - NET_ADMIN
      - SYS_PTRACE

Thanks!

Sorry for late response. As mentioned above i migrated the project from one host to another. It seems like i copied some host specific configuration files (or my previous configuration just had issues i never faced before) that were causing the error.
I refactored the configuration (basically started from zero again) and cleaned out the old file.
Since then the issue disappeared and i was not able to reproduce it again.
Thanks for the help in the meantime. I will close the issue for now (hoping to never need to open it again).


Incorporate test data that uses tags on the add action

Description
Right now there are no test datasets in the golden set or our own which use the tags field on the add action. It's not really clear to me what kind of data should go into there or how it's used "in real life"
Use Case
Related Issue(s)

They are now covered in these tables:
crates/test/tests/data/table_with_column_mapping
crates/test/tests/data/table_with_deletion_logs
and these tests (since we read the add actions there):

test_with_deletion_vector
async fn test_with_column_mapping() {


[SPARK-49739][SQL] Throw Custom error condition for invalid options in SaveIntoDataSourceCommand class

What changes were proposed in this pull request?
NullPointerException was thrown when invalid options were provided in the run function of SaveIntoDataSourceCommand up to now. That is because this map is propagated here, and java.util.Properties throws NPE if key/value is null. In map, a key cannot be null, but a value can, so that is why this NPE is possible to produce.
I propose we send the client an appropriate error condition. I've created a new error condition INVALID_OPTIONS.NULL_VALUE. Options are checked, and the error is thrown if there exists an entry in options map where the value is null.
Why are the changes needed?
To send the client an appropriate error.
Does this PR introduce any user-facing change?
Yes, in case invalid options are sent, we throw INVALID_OPTIONS.NULL_VALUE instead of NullPointerException.
How was this patch tested?
Wrote a unit test.
Was this patch authored or co-authored using generative AI tooling?
No.

@cloud-fan

Master branch is guarded from the NullPointerException cause by SPARK-49739. We should consider backporting the fix from https://github.com/apache/spark/pull/46955.

Closing the pr because #46955 solves it.


What's the proper way to make the AppBar fixed?

That is, fixed to the top while only the content is scrollable.

Hi, and thanks for your question. As explained in the admin-on-rest contributing guide, the right place to ask a "How To" question, get usage advice, or troubleshoot your own code, is StackOverFlow.
This makes your question easy to find by the core team, and the developer community. Unlike Github, StackOverFlow has great SEO, gamification, voting, and reputation. That's why we chose it, and decided to keep GitHub issues only for bugs and feature requests.
So I'm closing this issue, and inviting you to ask your question at:
http://stackoverflow.com/questions/tagged/admin-on-rest
And once you get a response, please continue to hang out on the admin-on-rest channel in StackOverflow. That way, you can help newcomers and share your expertise!


Add traits used by the flash driver: Client and HwInterface.

Client contains callbacks executed when the driver finishes an operation. HwInterface is the interface between the flash driver and the underlying hardware; it is abstracted into a trait so that we can fake the flash hardware out during unit testing.
Commits new to this PR:

Add traits used by the flash driver: Client and HwInterface.

----------------------
`make prtest` summary:
----------------------
git rev-parse HEAD
24c7b5625638bed4c1e50f2a826ba9b0c4b57435
git status
On branch driver-traits
nothing to commit, working tree clean

Updated.
----------------------
`make prtest` summary:
----------------------
git rev-parse HEAD
d7b3ee4a0caf6f053e4e9b660db117ba9526f4ab
git status
On branch driver-traits
Your branch is up to date with 'origin/driver-traits'.

nothing to commit, working tree clean


Peer dashboard feedback

A few feedback comments on the dashboard:
For the first tab:

The title in misspelt
Add headings for radio-buttons / dropdowns
Radio buttons on first tab are probably overkill, since I can already see the first world vs non first world airlines with the first view
Title on viz in first tab should be re-worded

For the second tab:

Switch order of x-axis labels, and give labels more descriptive names
Add description of dropdown options (definitions of terms)

Great dashboard!

issues have been created as per feedback given.


Prod: Users are earning VTX even when they don't have a signature set

Describe the bug
Users who previously had a Volentix signature but no longer have this signature set are still earning VTX.
To Reproduce
Steps to reproduce the behavior:

Clear the campaign data
Wait a few days
Look at the dashboard and see that users have some VTX
Look at their posts and notice that none of these users have a Volentix signature displayed

Expected behavior
Since none of these users have signatures displayed, they should still have 0 VTX
Screenshots
After I cleared the data everyone has 0; now they have some points:

I see two problems here:

Forum posts exist that are dated before the clearing of the data. That doesn't seem correct.
The only two fairly new posts are both credited=false; why then do users have VTX credited on the leaderboard?

Additional context
I cleared the campaign data on or around 25 September, so there should be no data from before then.

@shawnlauzon This happens because, if I understood the context correctly, you are recycling users from the old db. The system will just think these users have already confirmed their signatures and that they have been scraped before. So, whatever they post from the timestamp of the last scrape or the date they verified their profile are re-scraped and re-credited.
One approach in solving this problem is defining a campaign start. So we create a Campaign model that has a campaign_start field. (Anyway, we will have to create this model later for the support for multiple campaigns.)
With a campaign with a definite start date, the scraping of posts can be designed so that posts older than the campaign start date will not be scraped.

The system will just think these users have already confirmed their signatures and that they have been scraped before. So, whatever they posted that is newer than the timestamp of the last scrape or the date they verified their profile are re-scraped and re-credited.

It sounds to me like when these old posts are were re-scraped (and that is perhaps a problem), they should have been re-credited based on the status of their current signature. However, an incorrect assumption was made that their signature was good when it wasn't, and that's where the problem occurred.
It's possible that adding a new Campaign model as suggested will solve the problem, but it is a bigger change than what I want to include right now. Furthermore, it would not solve the current problem, which is that posts were credited when they shouldn't have been.
So my solution is just to brute force set these re-scraped posts as not credited:
UPDATE public.venue_forumpost SET credited = false WHERE timestamp < '2018-08-25';

(note that the timestamp was just so that I could rollback if it was a bad change; in fact we could have removed the WHERE clause completely.)
After doing that, all the users again have 0 points, which is all that is needed for this specific problem.

I'm keeping the PR around for the moment, but closing this issue as resolved


update packages

:white_check_mark: Build TheIdServer 1.1.2-maintain-1-0-01-0018 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/526b80b13f by @)


Webex Teams now "Webex"

Found out that the Webex Teams app is now just called "Webex".
I was able to update the installomator script with the following to allow the installation to work with the new name.
By changing name to "Webex" from "Webex Teams" the install is now running successfully again.
webexteams)
# credit: Erik Stam (@erikstam)
name="Webex"
type="dmg"
downloadURL="https://binaries.webex.com/WebexTeamsDesktop-MACOS-Gold/WebexTeams.dmg"
expectedTeamID="DE8Y96K9QP"
;;

thank you!


[MINOR] Fix the flag for bootstrap

Change Logs
Fix the flag.
Impact
Low.
Risk level (write none, low medium or high below)
Low.

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Tests pass based on #10055.


Unexpected new line feed in vuex

As shown：

Please tell me how to solve it.

@webees I'm sorry, I do not understand what the issue is. Can you perhaps explain it more ?


New OM: ActionSelector

Codecov Report
Patch coverage: 37.19% and project coverage change: -0.28 :warning:

Comparison is base (6911837) 87.32% compared to head (12b8e7b) 87.05%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #353      +/-   ##
==========================================
- Coverage   87.32%   87.05%   -0.28%
==========================================
  Files         172      176       +4
  Lines       21790    21905     +115
==========================================
+ Hits        19029    19070      +41
- Misses       2761     2835      +74

Impacted Files
Coverage Δ

unified_planning/model/action.py
93.50% <ø> (+7.92%)
:arrow_up:

...ed_planning/model/contingent/contingent_problem.py
37.27% <0.00%> (ø)

unified_planning/model/contingent/environment.py
22.22% <22.22%> (ø)

...nified_planning/model/contingent/sensing_action.py
40.42% <40.42%> (ø)

unified_planning/engines/mixins/action_selector.py
46.15% <46.15%> (ø)

unified_planning/shortcuts.py
92.52% <50.00%> (-0.81%)
:arrow_down:

unified_planning/engines/mixins/plan_repairer.py
36.36% <66.66%> (+3.03%)
:arrow_up:

unified_planning/engines/factory.py
82.58% <80.00%> (-0.13%)
:arrow_down:

unified_planning/engines/engine.py
95.00% <100.00%> (+0.08%)
:arrow_up:

unified_planning/model/__init__.py
100.00% <100.00%> (ø)

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@shanigu @hilaBGU In this PR I implemented the interfaces we discussed on.
Let me know if you have any comment or feedback.


Introduce renderWeekHeaderDay prop

This is not ready to be merged as there are still missing tests. I can add those if the suggestion is approved.
This is an alternative solution to an existing open PR: https://github.com/airbnb/react-dates/pull/650 - That PR introduces just a dayFormat prop that is passed on to formatting the week day headers. However, I thought it's more consistent to have a render() function as the same option is already provided to renderDay() and renderMonth().
The renderWeekHeaderDay() function takes in the day of the week as a prop (0-6). Users can then use this to format it how they want, and additionally apply any styles as they would like.
I'm not sure about the function name either... perhaps there's something better 😄

Coverage increased (+0.01%) to 86.481% when pulling 494117bd86e0c0ad3812eea1d3a09afa4ae0d001 on jseminck:render-week-header into 4de27332defa94bf6c02a6e04db08aa87d530b72 on airbnb:master.

Coverage increased (+0.01%) to 86.5% when pulling 783751aab2c8f6913709e68760963cff304ff497 on jseminck:render-week-header into bea3c2c2fd4dd20c1964bab01e0e007e837c82f6 on airbnb:master.

Hi! Any chance to get this or https://github.com/airbnb/react-dates/pull/650 merged? I know this implementation is still missing tests, but I'll definitely add them if this solution is approved.

Nothing additional. Just consistency with other renderXXX functions. It could be used to apply some different styling if someone wanted to.
But on the other hand, I understand that the simplicity of https://github.com/airbnb/react-dates/pull/650 is much nicer to have, especially when no one has a specific use-case to render something completely different.
At least my case would be solved with https://github.com/airbnb/react-dates/pull/650 as well 😄

In that case, let's go with #650 for now and if we come up with a usecase that needs additional formatting we can expand it then. :) Thank you for your contribution. I'll review the other PR now so we can get that in!


Electron Camera permission not enabled

Environment
Running 0.0.5 AppImage on NixOS 24.05-stable with KDE Wayland
Reproduction steps:

Create a new patch, add a WebcamTexture node connected to a MainLoop
Save the patch and reload

cant reproduce this in 0.0.8 anymore, is this still the case?

Duplicate of https://github.com/cables-gl/cables_electron/issues/88
Works with 0.0.8 under MacOS 14.13.1

Confirmed on Linux AppImage as well


Please add instruction to change the default StorageClass optionally

Especially for those who are not familiar with system side yaml configs, like app developers or infra people who prefer managed k8s clusters, this CSI driver is one of the components they do not really care even though it is necessary.
So the cluster operation people may have to execute kubectl patch storageclass default -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"false"}}}' when they don't want developers use the default StorageClass and let them use the HPE storage for PV.
I think this would be very important to mention about this in the document.
Ref. https://kubernetes.io/docs/tasks/administer-cluster/change-default-storage-class/

@inductor thanks for filing this issue. Both the Helm chart and Operator is clearly documented if you want to mark the StorageClass default. We talk about in storage classes in a lot of places and explaining how to patch the storageclass everywhere we do that wouldn't make much sense since this is a generic Kubernetes things. Do you have any idea where it would make sense to you where we should've mentioned it?

@inductor closing this due to inactivity and last response by @datamattsson. Please re-open if you still feel this needs to be addressed.


Use 7zip instead of bsdtar

Use 7zip instead of bsdtar on Windows machines
Switching to 7zip instead of bsdtar version 2.4.0 because it is not supporting xz archives on windows.
Please only merge this PR if this https://github.com/mesosphere/teamcity-agent/pull/51 is merged.
Corresponding DC/OS tickets (required)

DCOS_OSS-5499 Fix Teamcity CI/CD build.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot changelog-not-required Fixing windows build doesn't need a changelog entry.

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot request-review cgawron1


Update container-insights-troubleshoot.md

Updated troubleshooting to add a check for Log Analytics Workspace daily cap in the scenario where there is no data in Log Analytics.

@bwren - can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Performance tests

We need some way to determine the impact on performance of new PRs. Since that requires quite a bit of computation, this can probably not run through GitHub Actions.
A nice alternative might be to have a separate workflow that kicks off an evaluation on one of our computer clusters, and then reports back in the PR once that evaluation completes. This is some work to set-up, however.

Closed by #140.


If you want padding those should be negative

@julien-c thank you!

No problem! Looks like there's a glitch on the generated page though

Oof, looks like Github Pages having some issues with Swift syntax, I'll just remove the highlights for now.

Fixed for now…


[RFC] Deferred compute in imperative interface to unify imperative and symbolic interface

A new deferred computation (DC) argument to the imperative MXNet APIs is
proposed. If enabled, memory allocation and computation is deferred as long as
possible. Users can export the computational graph recorded during deferred
computation, which enables hybridization support.
Arrays for which DC is enabled are called lazy. Other arrays are called
normal.
Storage allocation and computation for lazy arrays is deferred until their
results are required by conversion to numpy or use as input to an operator
creating a normal array. Accessing attributes such as shape can also trigger
computation if the attribute can't be inferred.
C API
Deferred Compute (DC) Mode
An “alias” to MXImperativeInvokeEx, MXImperativeDeferredInvokeEx is
introduced which creates lazy arrays based on (normal or lazy) input arrays and
the operator
/*!
 * \brief invoke a nnvm op and imperative function creating lazy ndarray
 * \param creator the op
 * \param num_inputs number of input NDArrays
 * \param inputs input NDArrays
 * \param num_outputs number of output NDArrays
 * \param outputs output NDArrays
 * \param num_params number of keyword parameters
 * \param param_keys keys for keyword parameters
 * \param param_vals values for keyword parameters
 * \param out_stypes output ndarrays' stypes
 * \return 0 when success, -1 when failure happens
 */
MXNET_DLL int MXImperativeDeferredInvokeEx(AtomicSymbolCreator creator,
                                           int num_inputs,
                                           NDArrayHandle *inputs,
                                           int *num_outputs,
                                           NDArrayHandle **outputs,
                                           int num_params,
                                           const char **param_keys,
                                           const char **param_vals,
                                           const int **out_stypes);

Checks and explicit trigger
/*!
 * \brief Check if array's computation is deferred.
 * \param handles ndarray handles to be checked
 * \param num_handles nmuber of ndarray handles to be checked
 * \param status pointer to array of num_handles integers to hold the result.
 */
MXNET_DLL int MXNDArrayGetIsDeferredCompute(NDArrayHandle *handles,
                                             int num_handles,
                                             int *status);
/*!
 * \brief Trigger deferred computation.
 * \param handles ndarray handles to trigger comuptation of.
 * \param num_handles nmuber of ndarray handles to be checked
 *
 * Deferred computation of input arrays for specified handles is triggered if
 * required. Arrays that are already computed are ignored.
 */
 MXNET_DLL int MXNDArrayTriggerDeferredCompute(NDArrayHandle *handles,
                                              int num_handles);

Exporting to symbol
The computational graph recorded in deferred computation mode can be exported to
symbol. Users must specify all inputs and outputs, to define the part of the
graph they are interested in exporting.
It is an error, if any of the output depends on an input is not or cannot be
computed from the specified inputs. Equally, providing an input that is not
connected to any output is an error.
/*!
 * \brief Extract the graph constructed during deferred computation mode as a
 * Symbol.
 * \param input_handles ndarray handles of inputs
 * \param output_handles ndarray handles of outputs
 * \param input_names names associated with the inputs of the returned Symbol
 * \param output_names names associated with the outputs of the returned Symbol
 * \param out grouped output symbol handle
 *
 * Construct a Symbol for the subgraph of the deferred computation graph
 * spanning from the input_handles to the output_handles. Requires that
 * input_handles and output_handles are connected in the tracked computational
 * graph. The input_handles are required to have been used as arguments to an
 * operator that is part of the tracked subgraph. All inputs of the
 * computational graph must be specified.
 */
MXNET_DLL int MXNDArrayGetDeferredComputeSymbol(NDArrayHandle *input_handles,
                                                NDArrayHandle *output_handles,
                                                const char** input_names,
                                                const char** output_names,
                                                int num_inputs,
                                                int num_outputs,
                                                SymbolHandle *out);

Basic Python usage example
Example without Gluon.
x = mx.np.arange(shape=(8, 10))
with deferred_compute():
    y = (x + 5) * (x + 5)
    z = x**2
s = export(inputs={'x': x}, outputs={'y': y, 'z': z})
assert s.list_inputs() == ['x']
assert s.list_outputs() == ['y', 'z']

Implementation (C++)
NDArray
class NDArray {
 public:

   [...]

  /*!
   * \brief constructs a new dynamic NDArray
   * \param shape the shape of array
   * \param ctx context of NDArray
   * \param `delay_alloc whether delay the allocation (True for DC mode)`
   * \param dtype data type of this ndarray
   */
  NDArray(const mxnet::TShape &shape, Context ctx,
          bool delay_alloc = false, int dtype = mshadow::default_type_flag)
      : ptr_(std::make_shared<Chunk>(shape, ctx, delay_alloc, dtype)),
        shape_(shape),
        dtype_(dtype),
        storage_type_(kDefaultStorage),
        autograd_entry_(nullptr) {
  }

   [...]

  /*!
   * \brief Block until all the pending write operations with respect
   *    to current NDArray are finished, and read can be performed.
   *
   * If this is a array with deferred computation, computation is triggered.
   */
  inline void WaitToRead() const;
  /*!
   * \brief Block until all the pending read/write operations with respect
   *    to current NDArray are finished, and write can be performed.
   *
   * If this is a array with deferred computation, computation is triggered.
   */
  inline void WaitToWrite() const;

   [...]

 private:

   [...]

  /*! \brief node entry for autograd */
  nnvm::NodeEntry autograd_entry_;  // renamed from entry_
  /*! \brief node entry for deferred computation tracking */
  nnvm::NodeEntry deferredcompute_entry_;

  /*!
   * \brief Perform deferred computation.
   *
   * Applicable if current array is associated with deferredcompute_entry_ and
   * DCInfo. If so, compute this and all dependent NDArrays.
   *
   * Triggered automatically if needed by WaitToRead
   */
  void DeferredCompute() const;

   [...]

};

DCInfo
  /*! \brief DCInfo stores NDArays required to perform the deferred computation
   *  of it's owning NDArray.
   *
   *  Once deferred computation is completed, DCInfo::Clear should be executed
   *  to release references to input data.
   */
  class DCInfo {
  public:
    DCInfo(std::vector<NDArray> inputs) inputs_(inputs);

    static DCInfo& Get(const nnvm::NodePtr& node) {
      return dmlc::get<DCInfo>(node->info);
    }

    static void Clear(const nnvm::NodePtr& node) {
      if (node == nullptr || node->info.empty()) return;
      DCInfo& info = Get(node);
      node->info.clear();
    }

    static DCInfo& Create(const nnvm::NodePtr& node) {
      node->info.construct<DCInfo>();
      return Get(node);
    }

  private:
    std::vector<NDArray> inputs_;

  };

Execution
Trigger execution from within NDArray
NDArray::WaitToRead and NDArray::WaitToWrite are extended to trigger
execution, calling NDArray::TriggerDeferredCompute. TriggerDeferredCompute
is a no-op if no DCInfo is associated with the current array, ie. if it is
already computed.
Explicit C API to trigger execution
Users can also manually trigger the computation of specified arrays.
MXNET_DLL int MXNDArrayTriggerDeferredComputation(NDArrayHandle *handles)

Implementation
Operations on the graph are pushed to the engine for asynchronous execution via RunGraph.
FAQ
How about Autograd, NDArray.autograd_entry_ and AGInfo?
Autograd inside deferred computation (DC) mode can be supported.
Relation of Autograd and DC: While autograd’s RecordOp provides a similar
recording functionality to the deferred computation, the autograd graph is not
the same as a computational graph: NDArray::Detach() serves to detach a node
from the autograd graph by deleting NDArray.entry_, though the NodeEntry is
still required for reconstructing the computational history of how this NDArray
came to be.
Are reqs like kInPlace supported?
No. For now only kWriteTo is supported in DC mode.
The plan is to replace inplace operations with kWriteTo operations, writing to
a new (lazy) array. The framework should be smart enough to decide when to reuse
memory and when not. It shouldn’t be required for users to specify that they
want an inplace operation.
How is context attribute handled, specifically context changes?
Cross-device copy must be represented as operator (CrossDeviceCopyOp) which
requires special handling in the graph executor.
How is incomplete shape information handled?
shape property triggers computation if shape is accessed and can't be inferred completely.
Users can access static_shape if they wan't to avoid triggering computation.
Python (Gluon)
Based on DC, hybridization in Gluon is simplified:
Instead of implementing def hybrid_forward(self, F, x, ...) in HybridBlock,
users can opt to implement def forward(self, x, ...) in HybridBlock.
Hybridization based on DC works by the HybridBlock performing the following
steps (if it is not called by a parent block being hybridized)

keeping a reference to the input arrays and a reference to the parameter
arrays to pass them to MXNDArrayGetDeferredComputeSymbol;
enabling deferred compute mode
running forward
exporting to symbol and create CachedOp; Run CachedOp

A (internal) global context variable tracks if hybridization is ongoing. If set
to False and a Block is called that is to be hybridized, the global context
variable is set to True and the Block goes through all 4 steps outlined above;
finally the context variable is set back to False after the export to Symbol
step is finished.
Usage example
class Net(nn.HybridBlock):
    def forward(self, x, ...):
        ...

Hybridizing gluon.Blocks?
DC could be used to support hybridzing Block if all logic can be traced. A
separate effort may add logic to detect these cases and add hybridization
support based on DC. For now we rely on user to signify hybridization support by
subclassing HybridBlock.
Parameter Shape Inference
For HybridBlock making use of DC for hybridization, we request users to
implement HybridBlock.infer_shape to infer the parameters shape given the
inputs.
Currently, if HybridBlock.infer_shape is not implemented, backward shape
inference is used to infer the shape of parameters. However backward shape
inference is not supported in all cases (cf #14253,
https://github.com/apache/incubator-mxnet/issues/14983#issuecomment-493729329)
and relying on it for parameter shape inference is brittle. Thus for consistency
and simplicity we require infer_shape method implementation when using
hybridization based on DC.

Closing as issue was not picked up by the mailing list bridge.


Update guava to 31.1-jre

Updates com.google.guava:guava from 16.0.1 to 31.1-jre.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

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

labels: library-update, commit-count:1

Why this project retired, and I think it 's a wonderful and excited topic of stream processing.

@GithubZhitao Thanks for your interest! The project was developed by several engineers from a hardware company and we never had adoption and real customers in and outside the company. Then most of us left the company and moved on with our life.


Rename and define 'receptor cell'

currently no text def or logical def
I think the intent is such that this should be called 'sensory receptor cell'
TBD:

make part of uberon sensory system (thus inheriting TCs)
link to GO sensory perception / detection of stiumlus (capable of part of?) (@dosumis ?)

Also: many subclasses should follow a DP, neuronal receptor cell and involves in GO detection of X stimulus involved in perception of Y

I took a pass at this, not sure if it is correct, see PR: #729


update(plugins): change hyphens plugin

Name
Link

Hyphens Plugin
Link to plugin's repo

The current hyphens plugin hasn't been updated since 2019 and it's outdated (uses the old syntax for making plugins). I created a new one for a project and I think others could benefit from using it.

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

Thanks!


Remove language selection feature from K-9

Per comments on #2246 we plan to remove the language selection feature as it was originally designed to solve a problem in Android (lack of support for certain languages).
Right now it's an underused and fairly obscure feature which just makes the app more complex.

I realize this is not a vote, but please reconsider removing features from project. Apart from that, it's not unused - I'm sure I'm not the only one using it, and it's actually first setting on the list (so not obscure).

I find it difficult to think of a use case that isn't "Work around this bad translation"
Ignore that one, why would you want your email client in a different language to the rest of your device (and all other apps).

The other question is, is this a lot of complexity? Does this cause us headaches anywhere, or require maintenance?

well actually I can't tell why my phone isn't set to english globally, but I can't stand my native language in apps. from bad translations (not the case in k9mail), to 'too long texts', to just 'simply sounds stupid'.
anyway, this is kind of like kde-gnome debate, I always thought iphone was more remove-options-we-know-better, while android was the tinker-away approach.
On February 22, 2017 3:07:01 PM GMT+01:00, Philip<EMAIL_ADDRESS>wrote:

I find it difficult to think of a use case that isn't "Work around this
bad translation"
Ignore that one, why would you want your email client in a different
language to the rest of your device (and all other

There is a maintenance cost. When adding a new language it has to be added to the supported_languages string array (which I'm sure I forgot the last time I added a new translation) so users can select it in K-9 Mail's settings.
To properly override the system language we'd have to ignore all locale change events. I'm fairly certain we don't do this a) everywhere and b) properly (we don't want to ignore those events when we don't override the system language).
Also, the notification thing has probably been broken since forever. The fact that nobody reported this as a bug until now is a strong indication that language selection is not a heavily used feature.

I have to admit, I personally never noticed notification bug (although, come to think of it, it affects me too), so.. well.. I see your point. Shame, but maybe this will finally make me change the language globally.

@cketti Ho ne, kial vi volas forigi tiun ĉi eblon? Mi antaŭnelonge finigis traduki K-9 al Internacia Lingvo Esperanto kaj mi eĉ ne povas ĝin uzi! Bonvolu rekonsideri vian decidon kaj realdoni tiun ĉi eblon al la programo!

@verdulo This won't stop K-9 from being translated by your device. It'll mean K-9 is (like every single other application on your device) the same language as every other application.

2-signaj kodoj estas preferataj, la problemo estas, ke Esperanto NE estas elektebla en Android, do tial mi petas programistoj pri aldoni eblon por ŝanĝi aplikaĵan lingvon...

Message deleted. Please speak english if you want to communicate on our issue tracker, we don't want to use google translate to find out what you are talking about.

Why should I speak English, instead of Esperanto? Esperanto is easy international language, unlike English which is almost impossible to learn and not-international.
The problem is, that Esperanto is not selectable on Android, that is why I ask developers to add option to change interface language.

Hi,
Well, for me, the reason to select a different language to K-9 is because in spanish strings translations are to long and when I got a new e-mail "DELETE" button is not shown because "MARK AS READ" is to long in spanish, before the update to select a language in K-9 I had to put my device in english to avoid that, but that means that all speak apps do in english, like google maps finding places, streats with spanish name making a english pronunciation, gps and all, it sounds funny but it's a problem, and when select language came I inmediatly put my device in spanish and set english to K-9, I thought "this is great", but surprice!, some times notifications are in english and other times in device language (spanish for me).
I think a situations like this are same for others who do the same for same issue, what I suggest, if you want to remove language selection (at least for me), you can remove all text from buttons, nowadays every body knows whats each button for, trash container to delete, arrow to reply, double arrow to reply to all, open envelop to mark as read, folder to archive or move to folder, etc, so, if you remove text at least from notifications you will have an extra space to set other buttons there and make more usefull this app.
I've been saying this in other posts, maybe is to difficult for you to do it or you just don't want it to do, how ever is your call...
Regards.

As a "new" user, I, from time to time, switch to English just to compare "what did they mean when they phrased that in my (system default) language (German)?" Like e.g. "Empfangsbestätigung" ... here we usually either say "Lesebestätigung" (Read Receipt) or "Übermittlungsbestätigung" (DSN) ... by checking the terminus used in the english localisation, I found out what the feature actually is about (Read Receipt).


'LastItemData': is not a member of 'ImGuiContext'

Hi, i get this error when i try to build the imgui_animated.cpp file

Anyone knows how can i solve?

You are using too old version of ImGui for which we cannot provide compatibility.


[Feature Request] Add Amazon.nl

The integration is great, and working very nice with other delivery providers, so I would like to ask if it would be possible to include Amazon.nl among the providers.
If I understood how the integration works correctly, the integration needs the sender and subject for each one of the messages below, but if I'm missing any information let me knwo.
Package is shipped
Sender<EMAIL_ADDRESS>Subject: "Your Amazon.nl order (#XXXX) has been dispatched!" or "Je Amazon.nl-bestelling van "XXXX" is verzonden!"
Package arrives today
Sender<EMAIL_ADDRESS>Subject: "Arriving today: Your Amazon package will be delivered today." or "Wordt vandaag bezorgd: XXXX..."
Package is delivered
Sender<EMAIL_ADDRESS>Subject: "Delivered: Your Amazon package has been delivered." or "Bezorgd: Je Amazon-pakket is bezorgd."
I do get the messages on either English or Dutch (I'm not sure why), so I've added both subjects above.
Thank you very much for your great work on this integration.

Also need the "will arrive" portion from the email they send, examples:
    "will arrive:"
    "estimated delivery date is:"
    "guaranteed delivery date is:"
    "Arriving:"

and the bit of text after that, examples:
    "Previously expected:"
    "This contains"
    "Track your"

On both the 'order dispatched' and 'order confirmation' emails (not sure if the later is relevant) there is an  "Arriving:   " (in English) or "Verwachte bezorgdatum:   ".
For the second part, it was not clear to me which part is needed. So I've copied below the text from the "order has been dispatched" email, with the any identifying parts removed. If you can indicate for me which text on it you need, I can go look at the email in Dutch to find the equivalent.
`Hello,
We thought you'd like to know that we dispatched your order. Your order is =
on the way, and can no longer be changed.
Arriving:
Saturday 22 June
Track your item(s):https://www.amazon.nl/gp/css/shiptrack/view.html/ref
Your order was sent to:

Order Total: EUR XX,XX
Note: Order contains items marked as gift.
Your item(s) is (are) being sent by Amazon Logistics. Your tracking number =
is: .
Depending on the delivery method you chose, it's possible that the tracking=
information might not be visible immediately.Learn more about tracking shi=
pments.        https://www.amazon.nl/gp/help/customer/display.html
Visit our help pages for carrier contact information:
https://www.amazon.nl//help/en/carriers/ref=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
Order summary
1 x
Sold by: =09=09=09=09
EUR XX,XX`

The part where it says Track your is what I need, thanks!

Clear.
On the dispatched email, it shows as Volg je pakket. On the arriving today one, it shows as Je pakket volgen.

This should be working in the latest release. Let me know your results.

Thanks for the quick implementation. I have it running, but did not have anything coming from Amazon before today.
Right now I have Amazon's 'order has been dispatched' email in my inbox, with a delivery date of tomorrow. I can see from the log that it has been found, but none of the sensors have changed value. All amazon exception, amazon hub packages, amazon packages, and amazon delivered all remain at 0, while they all show the order number as atribute.
Is this the intended behavior, since delivery is only scheduled for tomorrow? I expected either amazon hub packages or amazon packages sensors (I'm not sure what is the difference between the two) to change to 1 to indicate that there is a package in route.
I will report back tomorrow as well with the arriving today and delivered emails.

Is this the intended behavior, since delivery is only scheduled for tomorrow?

Yes, it'll only increase on the day of delivery. Since Amazon doesn't send an "out for delivery" email.

Clear, thanks. Indeeed, as expected, today the amazon_packages counted turned into 1.
What seems to have been missed is the delivered message (from<EMAIL_ADDRESS>with subject Delivered: Your Amazon package has been delivered..
  has been dispatched!
2024-07-06 20:13:17.918 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: will arrive:
2024-07-06 20:13:17.918 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: estimated delivery date is:
2024-07-06 20:13:17.918 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: guaranteed delivery date is:
2024-07-06 20:13:17.918 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Arriving:
2024-07-06 20:13:17.919 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] First pass: Saturday 6 July
2024-07-06 20:13:17.935 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Arriverà:
2024-07-06 20:13:17.935 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: arriving:
2024-07-06 20:13:17.936 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Dostawa:
2024-07-06 20:13:17.936 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Zustellung:
2024-07-06 20:13:17.936 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Entrega:
2024-07-06 20:13:17.936 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: A chegar:
2024-07-06 20:13:17.936 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Arrivée :
2024-07-06 20:13:17.936 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Verwachte bezorgdatum:
2024-07-06 20:13:18.073 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Email Multipart: True
2024-07-06 20:13:18.074 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Content Type: multipart/alternative
2024-07-06 20:13:18.074 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Amazon Subject: Arriving today: 1MORE...
2024-07-06 20:13:18.075 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: will arrive:
2024-07-06 20:13:18.075 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: estimated delivery date is:
2024-07-06 20:13:18.075 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: guaranteed delivery date is:
2024-07-06 20:13:18.075 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Arriving:
2024-07-06 20:13:18.075 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Arriverà:
2024-07-06 20:13:18.076 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: arriving:
2024-07-06 20:13:18.076 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Dostawa:
2024-07-06 20:13:18.076 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Zustellung:
2024-07-06 20:13:18.076 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Entrega:
2024-07-06 20:13:18.076 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: A chegar:
2024-07-06 20:13:18.076 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Arrivée :
2024-07-06 20:13:18.077 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Verwachte bezorgdatum:
2024-07-06 20:13:18.216 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Email Multipart: True
2024-07-06 20:13:18.216 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Content Type: multipart/alternative
2024-07-06 20:13:18.216 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Amazon Subject: Delivered: Your Amazon package has been delivered.
2024-07-06 20:13:18.217 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: will arrive:
2024-07-06 20:13:18.217 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: estimated delivery date is:
2024-07-06 20:13:18.218 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: guaranteed delivery date is:
2024-07-06 20:13:18.218 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Arriving:
2024-07-06 20:13:18.218 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Arriverà:
2024-07-06 20:13:18.218 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: arriving:
2024-07-06 20:13:18.218 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Dostawa:
2024-07-06 20:13:18.218 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Zustellung:
2024-07-06 20:13:18.218 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Entrega:
2024-07-06 20:13:18.219 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: A chegar:
2024-07-06 20:13:18.219 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Arrivée :
2024-07-06 20:13:18.219 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Looking for: Verwachte bezorgdatum:
2024-07-06 20:13:18.219 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Amazon order: ['402-9023507-0006751']
2024-07-06 20:13:18.219 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: amazon_packages Count: 1
2024-07-06 20:13:18.220 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Je pakket is bezorgd)
2024-07-06 20:13:18.220 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG subject: Je pakket is bezorgd
2024-07-06 20:13:18.220 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Je pakket is bezorgd" SINCE 06-Jul-2024)
2024-07-06 20:13:18.350 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-07-06 20:13:18.350 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Je pakket is bezorgd) results: b'' count: 0
2024-07-06 20:13:18.351 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: dhl_parcel_nl_delivered Count: 0
2024-07-06 20:13:18.351 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (We staan vandaag)
2024-07-06 20:13:18.351 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG subject: We staan vandaag
2024-07-06 20:13:18.351 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "We staan vandaag" SINCE 06-Jul-2024)
2024-07-06 20:13:18.474 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-07-06 20:13:18.474 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (We staan vandaag) results: b'' count: 0
2024-07-06 20:13:18.474 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (We staan vanavond)
2024-07-06 20:13:18.475 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG subject: We staan vanavond
2024-07-06 20:13:18.475 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "We staan vanavond" SINCE 06-Jul-2024)
2024-07-06 20:13:18.595 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-07-06 20:13:18.596 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (We staan vanavond) results: b'' count: 0
2024-07-06 20:13:18.596 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: dhl_parcel_nl_delivering Count: 0
2024-07-06 20:13:18.596 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: dhl_parcel_nl_packages Count: 0
2024-07-06 20:13:18.596 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Ihr Paket ist da!)
2024-07-06 20:13:18.597 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG subject: Ihr Paket ist da!
2024-07-06 20:13:18.597 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Ihr Paket ist da!" SINCE 06-Jul-2024)
2024-07-06 20:13:18.717 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-07-06 20:13:18.717 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Ihr Paket ist da!) results: b'' count: 0
2024-07-06 20:13:18.717 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: dpd_delivered Count: 0
2024-07-06 20:13:18.718 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Bald ist ihr DPD Paket da)
2024-07-06 20:13:18.718 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG subject: Bald ist ihr DPD Paket da
2024-07-06 20:13:18.718 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Bald ist ihr DPD Paket da" SINCE 06-Jul-2024)
2024-07-06 20:13:18.848 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-07-06 20:13:18.848 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Searching for (['Paketnummer']) in (1) emails
2024-07-06 20:13:18.848 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for (['Paketnummer']) count results: 0
2024-07-06 20:13:18.849 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Bald ist ihr DPD Paket da) results: b'' count: 0
2024-07-06 20:13:18.849 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: dpd_delivering Count: 0
2024-07-06 20:13:18.849 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: dpd_packages Count: 0
2024-07-06 20:13:18.849 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (informacja o dostawie)
2024-07-06 20:13:18.850 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG subject: informacja o dostawie
2024-07-06 20:13:18.850 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "informacja o dostawie" SINCE 06-Jul-2024)
2024-07-06 20:13:18.970 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-07-06 20:13:18.970 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Searching for (['została dzisiaj dostarczona', 'Adresse erfolgreich zugestellt']) in (1) emails
2024-07-06 20:13:18.970 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for (['została dzisiaj dostarczona', 'Adresse erfolgreich zugestellt']) count results: 0
2024-07-06 20:13:18.970 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (informacja o dostawie) results: b'' count: 0
2024-07-06 20:13:18.970 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (wurde durch GLS zugestellt)
2024-07-06 20:13:18.971 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG subject: wurde durch GLS zugestellt
2024-07-06 20:13:18.971 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "wurde durch GLS zugestellt" SINCE 06-Jul-2024)
2024-07-06 20:13:19.092 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-07-06 20:13:19.093 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Searching for (['została dzisiaj dostarczona', 'Adresse erfolgreich zugestellt']) in (1) emails
2024-07-06 20:13:19.093 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for (['została dzisiaj dostarczona', 'Adresse erfolgreich zugestellt']) count results: 0
2024-07-06 20:13:19.093 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (wurde durch GLS zugestellt) results: b'' count: 0
2024-07-06 20:13:19.093 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: gls_delivered Count: 0
2024-07-06 20:13:19.093 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (paczka w drodze)
2024-07-06 20:13:19.094 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG subject: paczka w drodze
2024-07-06 20:13:19.094 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "paczka w drodze" SINCE 06-Jul-2024)
2024-07-06 20:13:19.216 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-07-06 20:13:19.216 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Searching for (['Zespół GLS', 'GLS-Team']) in (1) emails
2024-07-06 20:13:19.216 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for (['Zespół GLS', 'GLS-Team']) count results: 0
2024-07-06 20:13:19.216 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (paczka w drodze) results: b'' count: 0
2024-07-06 20:13:19.217 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (ist unterwegs)
2024-07-06 20:13:19.217 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG subject: ist unterwegs
2024-07-06 20:13:19.217 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "ist unterwegs" SINCE 06-Jul-2024)
2024-07-06 20:13:19.338 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-07-06 20:13:19.339 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Searching for (['Zespół GLS', 'GLS-Team']) in (1) emails
2024-07-06 20:13:19.339 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for (['Zespół GLS', 'GLS-Team']) count results: 0
2024-07-06 20:13:19.339 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (ist unterwegs) results: b'' count: 0
2024-07-06 20:13:19.339 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: gls_delivering Count: 0
2024-07-06 20:13:19.340 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Sensor: gls_packages Count: 0
2024-07-06 20:13:19.345 DEBUG (MainThread) [custom_components.mail_and_packages] Finished fetching Mail and Packages (imap.gmail.com) data in 19.905 seconds (success: True)
2024-07-06 20:13:19.346 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up mail_and_packages.binary_sensor
2024-07-06 20:13:19.348 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] Amazon Check: True
2024-07-06 20:13:19.349 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] Amazon Image hash: None
2024-07-06 20:13:19.349 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] Amazon None hash: None
2024-07-06 20:13:19.351 INFO (MainThread) [homeassistant.components.camera] Setting up mail_and_packages.camera
2024-07-06 20:13:19.354 INFO (MainThread) [homeassistant.components.sensor] Setting up mail_and_packages.sensor
2024-07-06 20:13:19.384 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Updating system image path to: custom_components/mail_and_packages/images/
2024-07-06 20:13:49.355 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: amazon_camera
2024-07-06 20:13:49.355 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None
2024-07-06 20:14:00.326 INFO (MainThread) [homeassistant.components.automation.monitor_healthcheck_io_heartbeat] Monitor: Healthcheck.io heartbeat: Running automation actions
2024-07-06 20:14:00.327 INFO (MainThread) [homeassistant.components.automation.monitor_healthcheck_io_heartbeat] Monitor: Healthcheck.io heartbeat: Executing step call service
2024-07-06 20:14:19.356 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: amazon_camera
2024-07-06 20:14:19.356 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None

2024-07-06 20:13:16.293 DEBUG (SyncWorker_45) [custom_components.mail_and_packages.helpers] Amazon Subject: Delivered: Your Amazon package has been delivered.

It was found. Did the amazon camera update with the photo of your delivered package?
I'm not sure if they do that in NL or if it's a US only thing.

Amazon doesn't take photos of the delivered package in NL, but the camera seems to have updated with the image below (at least I don't recall it before).

My question was more whether the sensor.mail_amazon_packages_delivered sensor should have changed to 1 once the delivered message was identified. Because it has remained at 0.

It should have, I see the issue, let me see what I can do.
Thanks.

Please try the 0.4.0b0 release, note that you'll need to add your amazon domain into the config. Please use the reconfigure menu to do this.

I have the 0.4.0b0 installed and configured and will report back once I get new packages. I have a couple of them comming on the next few days, but unfortunatelly they seem to be coming via DHL.
I've noticed a couple of things this morning as well that I wanted to check whether it is intended behavior.:

The amazon_packages sensor seems to have turned to 1 due to a Amazon order being delivered by DHL.
The order number from the order delivered on July 6th still appears in the amazon_packages sensor attributes.

The behaviour above seems to be already present in  0.0.31 (the dip on the sensor to 0 around 8am is when I've updated to 0.4.0b0).

Log is attached. To help make sense of it, it contains 3 orders:
Order; 402-XXXXXXX-XXXXXX1
Item: "1MORE..."
Status: Delivered by Amazon in July 6th.
Order; 171-XXXXXXX-XXXXXX6
Item: "Tzstz 3+2 Stuks Gehard Glas..."
Status: To be delivered by DHL on July 8th. DHL's email confirming today's delivered already received.
Order; 171-XXXXXXX-XXXXXX5
Item: "Amazon Basics Handbagage..."
Status: To be delivered by DHL on July 10th. No email from DHL received so far (the tracking number is from DHL, confirmed via their website).
error_log-4.txt

So I've finally had the chance to test the 0.4.0b0 with an amazon delivered package. Once the Delivered: email was received, sensor.mail_amazon_packages_delivered turned to 1.
The sensor.mail_amazon_packages remains at 1 despite the delivery. Again, I'm not sure if this is as intended, but if it is not I'm attaching the log.
debug.txt

Again, I'm not sure if this is as intended

It's intended, because Amazon is a special case.


vite5.0.10版本使用defineConfig返回async方法提示类型不兼容

Describe the bug
问题：使用 vite5.0.10 时，defineConfig 返回 async function 提示类型不兼容

Reproduction
none
Steps to reproduce
typescript: 5.2.2
vue-tsc: 1.8.8
vite: 5.0.10
System Info
`macOS: 14.1.2 (23B2091)`

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

The information you provided is limited. Can you provide a minimal reproducible repository?

这边使用 codesandbox 复现了一下。
感谢您的回复。
请查看。

You can workaround it with localsConvention: 'camelCaseOnly' as const or return { plugins... } satisfies UserConfig, but I'm not really why TypeScript isn't detecting this right. I don't this there's much we can do here so I think the workaround are the solution for now.

在实际项目中，我将 async 标识取消时，ts 也能正确的运行，没有相关的类型错误报错。是一个很奇怪的问题。这个示例其实并没有完全的复现问题。但我觉得你的观点是正确的，这应该是 ts 的问题。感谢你的解答😄。


Add glossary page

Proposed changes:

Fix https://github.com/RasaHQ/roadmap/issues/635

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog
[ ] reformat files using black (please check Readme for instructions)

thanks, @msamogh ! I think we need to make these definitions crystal clear, otherwise this page will hurt more than it helps. Happy to do an iteration in a google doc if that's quicker. Would be good to get @JustinaPetr input as well

i'm also halfway through a review of this btw

@amn41 We could collaborate on the definitions here (https://docs.google.com/spreadsheets/d/1v7xUaTYbhdIoR2q7hjYXqXzieB4z2zyqbjIzBleaBd8/edit#gid=0). I had copy-pasted several of them straight from the product team guide and simply added a few more onto that. I'll fix them in the sheet first and let's collaborate there before pushing things here?


Dockerize kismatic

What's happening with this PR? Also we need to merge the Makefile changes(and all other upstream changes) into ket-server first and then finish this up.

This PR includes the makefile changes - including those to publish to dockerhub and build a docker-compatible package.

Please try to keep the commit names meaningful,  Requested dashboard changes won't mean anything when looking back at the history, Fix running kismatic dashboard command inside a docker container by not opening the browser is much more representative of what is actually going on

I figured it would end up in a squash anyway. The commit history is only really going to reflect this PR, unless you dig into the commit details.

The scope of this PR has been cut down drastically and relevant sections moved to other PRs.

LGTM!


JTQ backend by sakshi & sai neel

Jump the Queue Backend by Sakshi & Sai Neel.

We have merged our frontend and backend code in one branch.


[Vue3] RouterView doesn't populate correctly on page loads

Problem
When using Vue3 and the example provided at examples/vue3/basic.py, the RouterView does not display the route that should be active on the page load. Additionally, you can see in the browser console a warning that says:
[Vue Router warn]: No match found for location with path "/"

It is worth noting that after page load if you click the list items in the nav draw, the routes seem to display correctly. The issue is only on page load/reload. This does not appear to be an issue when using Vue2.
Steps to Reproduce

pip install trame trame-vuetify trame-router
cd examples/vue3
python basic.py --port 8988
Open a browser at http://localhost:8988
Observe the fact that no content is rendered in the RouterView
Open the browser console and observe the Vue Router warning
Click on one of the nav buttons and observe the router view correctly populate itself without creating any warnings in the browser console
Reload the page (keeping the route in the URL path), observe the content failing to load in the RouterView and another warning in the browser console

Environment Setup
I am using the following package versions:
trame==3.5.2
trame-client==2.15.0
trame-router==2.1.0
trame-server==2.15.0
trame-vuetify==2.4.2

Possible Solution
Not sure yet... however I think it could be related to the fact the router object is initialized with no routes on the following line:
https://github.com/Kitware/trame-router/blob/69fe15df8cedbed1f585b65d5cc2889af160e31b/vue3/src/use.js#L7

Thanks for pointing out the issue!


git checkout doesn't work in local area

I tried the command  git checkout $TAG
I notice it displayed taht  it'is done. Hovewer, when I verified with command line "git describe --tags"
It show me, not the commit with tag, but the last commit pushed

Hi @smola ,
With go-git, I made a git clone of one of my gitlab repositories, then I tried to check out a tag release. it seems to be a "sucess" (there is a ''nil' error). So I stop my app.  And in the local git repository that I just clone, I did a 'git describe --tags' for checking if it is really checking out.
As a result, the HEAD is on master branch's last commit. like the go-git checkout command is never performed.
Unfortunately, I didn't make a backup of this block of code... It is very similar to the example provided here  indeed I copy paste

I tried the command git checkout $TAG
I notice it displayed taht it'is done. Hovewer, when I verified with command line "git describe --tags"
It show me, not the commit with tag, but the last commit pushed

sorry for my bad english... :)

@akdj Thank you, we'll look into it.

@akdj You must checkout by commit hash. If you want to checkout a tag, you will have to get the commit that tag points to first. See https://github.com/src-d/go-git/pull/985


[Question] Sentinel-2 Cloud Masking with s2cloudless code tutorial

@jdbcode
I tried the code tutorial, and it seems the output s2_sr_median has crs EPSG:4326, which corresponds to WGS84 (World Geodetic System 1984, used in GPS).
My question:
Shouldn't the cloud mask preserve the original projection provided by GEE? If I'm not mistaken, it is in UTM/WGS84, with EPSG varying according to the location on the globe.

@marlonfs, the EPSG:4326 output projection for s2_sr_median is expected because it is generated by a call to .median(). Functions that do composting use EPSG:4326 with 1-degree scale as a default because the inputs can be in multiple projections. See the projections guide page for more info. If you want the output in a specific projection, you can chain .setDefaultProjection onto the call to .median() (in this case). Also, for any downstream functions like reduceRegion or Export.* you can use the crs and scale (or crsTransform) parameters to set the desired projection. Hope this helps!


Custom alert dispatcher script

Would it be possible to add a custom alert dispatcher script to the ambari configuration as described here ?
Using Slack SDK, it would look like this:
import os
import sys
from slack import WebClient

client = WebClient(token=os.environ['SLACK_API_TOKEN'])
warning_level = {
    "OK": "ok",
    "WARNING": "warning",
    "CRITICAL": "red_circle",
    "UNKNOWN": "question"
}

def send_alert(alert_id, alert_label, service, status, message):
    icon = warning_level[status]
    alert = """
        :{icon}: {service} Alert ! {mention}
        *ID*: `{id}`
        *Label*: {label}
        *Status*: {status}
        *Details*: {text}
    """.format(
        icon=icon,
        id=alert_id,
        label=alert_label,
        service=service,
        status=status,
        text=message,
        mention='@username'
    )
    response = client.chat_postMessage(
        channel='#ambari',
        text=alert)
    assert response["ok"]

def main():                                     # main method which is called when invoked on the command line
    definition_name = sys.argv[1]               # :param definitionName: the alert definition unique ID
    definition_label = sys.argv[2]              # :param definitionLabel: the human readable alert definition label
    service_name = sys.argv[3]                  # :param serviceName: the service that the alert definition belongs to
    alert_state = sys.argv[4]                   # :param alertState: the state of the alert (OK, WARNING, etc)
    alert_text = sys.argv[5]                    # :param alertText: the text of the alert
    send_alert(definition_name, definition_label, service_name, alert_state, alert_text)

Sorry @belgacea never personally used the custom dispatcher.
But if it's supported by the Ambari API as I can see in your link then it should be possible to add it in these playbooks.
Feel free to add it in the post-install role and submit a PR!


Int8_kv_cache run error for whisper

System Info

intel i5 13500
nvidia 4060ti 16G
Tensorrt-LLM commitID b57221b764bc579cbb2490154916a871f620e2c4
container nvidia-docker run --entrypoint /bin/bash -it nvidia/cuda:12.1.0-devel-ubuntu22.04

Who can help?
No response
Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)

Hi @Eddie-Wang1120  would u please try our latest code base to see if the issue still exists?
And do u still have further issue or question now? If not, we'll close it soon.


 Three parts:

pass jshint - add some semis, put if bodies on separate lines, etc. Hope that's OK, I use jshint a lot and it's nice to keep quiet so that when it complains you know it's important
when pasting, treat all individual values with the same steps - blank handling, duplicate handling, etc - that we were ding on individual inputs earlier
when pasting, make the tags immediately - before we had to add a single trailing , to build the tags.

Hope that's OK. I've bumped the ver in both files to 0.8.1.

Good spot re: the bad event, was a typo from the rename. Have adjusted accordingly.

Manually merged ideas/chunks of this as part of #11. README update still needed though.


ESM is unsupported

Describe the bug
I am trying to use flat configs through the use of #156; my problem right now is that I cannot use it in my configuration, as my eslint configuration is in an ESM library.
The problem that I am facing is that all files in configs/ aren't transpiled and make use of require, which is not supported in ESM. Tools like tsup can shim these (kind of), but it makes the bundling a lot harder, as now multiple other - not directly referenced - files need to be included during bundling.
Expected behavior
Use of eslint-config-storybook in ESM packages.
Screenshots
ESLint: 8.57.0

TypeError: __require.resolve is not a function
    at ../../../node_modules/eslint-plugin-storybook/dist/configs/csf-strict.js

Additional context
Add any other context about the problem here.

+1 for this 👀


[WIP] Slack Error Handling

Closes CORE-90

@CalumTowers can you check that this is the kind of thing you are after?

@atoff Yeah this is where we need to go. I want to try and eliminate the "its Slack's fault" from our BugSnag to...
a) tidy it up
b) stop using our quota
I mean, we do need to optimise our calls to Slack's API to prevent us being blocked/timed out but if its a temporary error with no real impact to the user, I don't want BugSnag (and my phone...) going crazy


Error - ... provided an invalid property of "default" - with 1.0.0 and babel 6

Uncaught Exception:
Error: Plugin 0 specified in "/home/mike/slack-wrapped-2/.babelrc" provided an invalid property of "default"
    at Plugin.init (/home/mike/slack-wrapped-2/node_modules/babel-core/lib/transformation/plugin.js:124:13)
    at Function.normalisePlugin (/home/mike/slack-wrapped-2/node_modules/babel-core/lib/transformation/file/options/option-manager.js:155:12)
    at /home/mike/slack-wrapped-2/node_modules/babel-core/lib/transformation/file/options/option-manager.js:183:30
    at Array.map (native)
    ...

{
  ...
  "plugins": [
    ["babel-plugin-module-alias", [
      { "src": "./src/main", "expose": "main" },
      { "src": "./src/web", "expose": "web" }
    ]]
  ]
}

I wonder if this is this related to https://github.com/babel/babel/pull/2697?

It seems that it probably was. The fix https://github.com/babel/babel/commit/b5b7e346a04c99da8793e2c65cc3b3c7c720253d is included in babel 6.0.15, and this problem does not occur with 6.0.15.


Double-clicking highlights the word and the space after

see superhuman/superhuman#8158

@rahulgs12 this looks good to me, :gem:.
Can you please publish a new version of @superhuman/Squire and send a PR to update the package.json in the app.


Revert "Updated master startup."

This reverts commit 16fb2574c4088f74d954ea636233142b40e2513d.

Keep unrelated to master startup changes.

Codecov Report

Merging #168 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #168      +/-   ##
==========================================
- Coverage   53.27%   53.26%   -0.02%
==========================================
  Files         340      340
  Lines       26131    26136       +5
  Branches     3392     3394       +2
==========================================
  Hits        13921    13921
- Misses      11522    11527       +5
  Partials      688      688

Impacted Files
Coverage Δ

lib/python/treadmill/bootstrap/master/__init__.py
0% <ø> (ø)
:arrow_up:

lib/python/treadmill/cli/admin/install/master.py
0% <0%> (ø)
:arrow_up:

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 69c3583...0e40175. Read the comment docs.


How to un-ignore the ignored rubocop cops?

haml-lint ignores some rubocop cops (https://github.com/brigade/haml-lint/blob/master/config/default.yml#L56-L70)
Let's say I didn't want it to...
I tried figuring out how to configure haml-lint to enable those cops but couldn't quite figure it out. Is it possible?
Thanks!

Hey @maxjacobson,
Those cops are ignored for a good reason: haml-lint takes some shortcuts when extracting Ruby code from a HAML template, which necessarily results in noise from those cops.
Can you give a specific example of a copy you want to disable?
If you still REALLY want to do this, you just need to redefine the entire list in your local .haml-lint.yml:
linters:
  RuboCop:
    ignored_cops: [] # NOT RECOMMENDED!

Hey @sds thanks for getting back to me!
there are a few nitpicky things I was hoping haml-lint would catch:

the newline character at end of file thing
tabs instead of spaces for indentation
4 spaces instead of 2 spaces for indentation

are you saying it doesn't analyze the file as it is, but first transforms it into some other ruby file, so it wouldn't catch those things necessarily anyway?
thanks!

Yes, as part of its preprocessing, haml-lint will convert HAML like this:
- if signed_in?(viewer)
  %span Stuff
  = link_to 'Sign Out', sign_out_path
- else
  .some-class{ class: my_method }= my_method
  = link_to 'Sign In', sign_in_path

...into Ruby like this:
if signed_in?(viewer)
  link_to 'Sign Out', sign_out_path
else
  { class: my_method }
  my_method
  link_to 'Sign In', sign_in_path
end

Notice that the Ruby is somewhat nonsensical. All haml-lint tries to do is preserve the ordering of declarations and uses of variables, as well as the order Ruby that code appears in the template. This means you probably won't have a translation that makes perfect sense.
For things like indentation, it may be possible to munge things into shape but I haven't looked too deeply into that. Right now if you have HAML like the following:
%tag{ some: 'hash',
      attributes: 'here' }

...it will get extracted as:
{ some: 'hash', attributes: 'here' }

...losing some of the whitespace in the process. This makes it difficult to have it generate correct indentation.
For your request about final newlines, I think it's reasonable for haml-lint to support that first hand via a FinalNewline linter, since RuboCop won't have any idea whether your HAML template ends with a newline or not.

Makes total sense, thanks for explaining.
Adding a newline check would be super helpful! What do you think about checking for the presence of a tab character? I think most Rubyists are using spaces, not tabs, so checking for the presence of a tab file in the source haml file might be useful as well :smile:

Added a final newline check in 1635c078c2. Enforcing spaces instead of tabs in indentation was added in  #81.

Awesome! Thanks a lot @sds


Server issue after install

Helo, I'm trying to install on aws ec2 instance.
after yarn start... my instace doesnt connect anymore and i need to restart.

My instance
Edit:

I run those commands:
$ git clone https://github.com/LANIF-UI/dva-boot-admin.git
$ cd dva-boot-admin
$ yarn
$ yarn start

I used customize-cra not eject to use CRA, currently  customize-cra does not support the latest CRA, I am also looking at this https://github.com/arackaf/customize-cra/issues/134

ok thanks!

okay, thanks!


Remove dependency on screenfull - fix issue#107

In some scenarios (e.g. commonjs environments) there exist problems with the dependency on the screenfull package. This package is a second export of the leaflet.fullscreen package, but this seems not to work in some configurations.
As screenfull is only a thin wrapper around the fullscreen api available in all modern browsers, this pr integrates the required calls to the fullscreen api into the leaflet.fullscreen package as internal methods.
As all major browsers support the fullscreen api since more than 4 years and since IE is no longer supported by microsoft, I dropped the support of older browsers / IE (but this could be changed easily).
The only exception is the safari browser on apple devices that only support the complete api since march 2023. Here older versions are supported too.
I tested this pr in the demo page included in the package and in the commonjs demo (using hugo) from @taviowong.
To enable more tests, I set the version in the package.json file to v 3.0.0-rc.0, so that this pr could be published as a prerelease (using npm publish --tag next).
Perhaps some of the other users (@barbalex or @ricfio) could test this release candidate too (with npm i leaflet.fullscreen@next) and give some feedback. I would appreciate this very much.

Perhaps some of the other users (@barbalex or @ricfio) could test this release candidate too (with npm i leaflet.fullscreen@next) and give some feedback. I would appreciate this very much.

Hi @BePo65,
I tried to do this on my project:
npm r screenfull
npm i github:BePo65/leaflet.fullscreen#b1e18f7c
4814cae8a857c8288b8ec56763fb57c9

but the result was:
vite
✘ [ERROR] Could not resolve "screenfull"

    node_modules/react-leaflet-fullscreen/node_modules/leaflet.fullscreen/Control.FullScreen.js:196:55:
      196 │     module.exports = factory(require('leaflet'), require('screenfull'));
          ╵                                                          ~~~~~~~~~~~~

  You can mark the path "screenfull" as external to exclude it from the bundle, which will remove
  this error. You can also surround this "require" call with a try/catch block to handle this
  failure at run-time instead of bundle-time.

/home/ricfio/cedat85/projects/d4d/portal-NEW/node_modules/esbuild/lib/main.js:1649
  let error = new Error(`${text}${summary}`);
              ^

Error: Build failed with 1 error:
node_modules/react-leaflet-fullscreen/node_modules/leaflet.fullscreen/Control.FullScreen.js:196:55: ERROR: Could not resolve "screenfull"
    at failureErrorWithLog (/home/ricfio/cedat85/projects/d4d/portal-NEW/node_modules/esbuild/lib/main.js:1649:15)
    at /home/ricfio/cedat85/projects/d4d/portal-NEW/node_modules/esbuild/lib/main.js:1058:25
    at /home/ricfio/cedat85/projects/d4d/portal-NEW/node_modules/esbuild/lib/main.js:1525:9
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  errors: [
    {
      detail: undefined,
      id: '',
      location: {
        column: 55,
        file: 'node_modules/react-leaflet-fullscreen/node_modules/leaflet.fullscreen/Control.FullScreen.js',
        length: 12,
        line: 196,
        lineText: "\t\tmodule.exports = factory(require('leaflet'), require('screenfull'));",
        namespace: '',
        suggestion: ''
      },
      notes: [
        {
          location: null,
          text: 'You can mark the path "screenfull" as external to exclude it from the bundle, which will remove this error. You can also surround this "require" call with a try/catch block to handle this failure at run-time instead of bundle-time.'
        }
      ],
      pluginName: '',
      text: 'Could not resolve "screenfull"'
    }
  ],
  warnings: []
}

Node.js v18.17.1

so, i have solved in this way:
npm i screenfull

then I'm come back to official leaflet:
npm r leaflet.fullscreen # to remove the pr version
npm i leaflet.fullscreen # to re-install the official 2.4.0 version

I hope this can help you.

@ricfio  I see that you are using react-leaflet-fullscreen that is a wrapper around leaflet.fullscreen. As react-leaflet-fullscreen connot yet be updated to the updated leaflet.fullscreen you have to do some more steps to test the updated functionality (all used directories must already exist after step 2):

npm r screenfull
npm i github:BePo65/leaflet.fullscreen#b1e18f7c4814cae8a857c8288b8ec56763fb57c9
copy the file Control.FullScreen.js containing the new version from 'node_modules/leaflet.fullscreen' to the node_modules used by 'react-leaflet-fullscreen' in the directory 'node_modules/react-leaflet-fullscreen/node_modules/leaflet.fullscreen'

now running vite should use the updated version.
To undo this change you have to reinstall 'react-leaflet-fullscreen' and 'screenfull'..
I know this is a lot of work, but it would help me a lot, to make sure that the modifications run in your environment.

@BePo65
I have replaced node_modules/react-leaflet-fullscreen/node_modules/leaflet.fullscreen/Control.FullScreen.js with node_modules/leaflet.fullscreen/Control.FullScreen.js (from github:BePo65/leaflet.fullscreen#b1e18f7c4814cae8a857c8288b8ec56763fb57c9)
It's works !
... but at this point, after the pr closing, will be need to update react-leaflet-fullscreen:
https://github.com/krvital/react-leaflet-fullscreen

I will create an issue in 'react-leaflet-fullscreen' as soon, as this pr is accepted and published.

As the changes in this pr seems to solve the problem, I think that we can skip the release of a prerelease version; therefore the version info in the packag.json must be changed before publishing a version containing thhis pr.

Version 3.0.0 published, thx again @BePo65
Since you are now the main contributor of this package i would like to suggest to transfer the ownership of this repo to @Leaflet org. This could allow more people to collaborate on this, and i could help to handle issue and request on this (since i'm not really coding on it since a long time). Any thoughts ?

Perhaps it would help the leaflet guys to accept such a transfer, if we added some development "helpers":

add 'uglify-js' to create a minified version to the repository (or how does the minified version come to the cdn?)
add eslint using the configuration from the leaflet project to ensure consistent coding styles
perhaps add a script to add the version number to the head of the javascript file

If you agree, I would create a pr for this.

1. add 'uglify-js' to create a minified version to the repository (or how does the minified version come to the cdn?)

why not this could be done like https://github.com/Leaflet/Leaflet.heat/blob/gh-pages/package.json#L26 but minified version on https://cdnjs.com/libraries/leaflet.fullscreen seems to be automatically generated

2. add eslint using the configuration from the leaflet project to ensure consistent coding styles

I can't find any guideline way on this side, maybe we should do like this https://github.com/Leaflet/Leaflet.draw/blob/develop/package.json#L7 & https://github.com/Leaflet/Leaflet.draw/blob/develop/package.json#L67

3. perhaps add a script to add the version number to the head of the javascript file

Not sure bout that, but if you think it's use full, gogogo :)

If you agree, I would create a pr for this.

Nice !

PS : do you think this mention to screenfull in the readme is still revelant ? https://github.com/brunob/leaflet.fullscreen/blob/master/README.md?plain=1#L23

Regarding the 'ps': looks like I missed that point. Will fix it in a mini pr.
Regarding the other points:
if I understand your answer, you do not have to publish your package ti cdnjs - somehow they fetch it from github (I did not find an answer to this question on the web), The idea behind point 3 was to make sure that I can find out, what version I'm using, But cdnjs adds the version to the path; therefore I think we don't need neither point 1 nor point 3.
And regarding point 2: the idea was to take (some) rules from the .eslintrc,js of the leaflet repository.

One more question: in the first line of 'Control.FullScreen.js' there is a !_map after the start of the comment.
As I didn't find any information about that "token" on the web: can you tell me,what that is about? Eslint complains about that sequence, when I use the settings from the leaflet repository.

And regarding point 2: the idea was to take (some) rules from the .eslintrc,js of the leaflet repository.

Perfect.

One more question: in the first line of 'Control.FullScreen.js' there is a !_map after the start of the comment.

This was introdiced with 768329bc287dd3a976e56d48e816176de5ffb749 ^^ Is it a typo ? Or did you get it from another leaflet plugin ?

Dammed, git never forgets anything 😃