[Usage] RuntimeError: cuDNN error: CUDNN_STATUS_NOT_INITIALIZED

Describe the issue
Issue: RuntimeError: cuDNN error: CUDNN_STATUS_NOT_INITIALIZED
Command:
python -m llava.serve.cli \
    --model-path "/home/LLaVA-main/pretrained/LLaVA-Lightning-MPT-7B-preview" \
    --image-file "/home/LLaVA-main/view.jpg" \
    --load-4bit

Log:
[2023-10-10 12:31:07,178] [INFO] [real_accelerator.py:110:get_accelerator] Setting ds_accelerator to cuda (auto detect)
You are using config.init_device='cpu', but you can also use config.init_device="meta" with Composer + FSDP for fast initialization.
The model weights are not tied. Please use the `tie_weights` method before using the `infer_auto_device` function.
Loading checkpoint shards: 100%|████████████████████████████████| 2/2 [00:27<00:00, 13.77s/it]
user: please describe the view
Traceback (most recent call last):
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/home/jovyan/LLaVA-main/llava/serve/cli.py", line 119, in <module>
    main(args)
  File "/home/jovyan/LLaVA-main/llava/serve/cli.py", line 89, in main
    output_ids = model.generate(
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/transformers/generation/utils.py", line 1588, in generate
    return self.sample(
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/transformers/generation/utils.py", line 2642, in sample
    outputs = self(
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/jovyan/LLaVA-main/llava/model/language_model/llava_mpt.py", line 76, in forward
    input_ids, attention_mask, past_key_values, inputs_embeds, labels = self.prepare_inputs_labels_for_multimodal(input_ids, attention_mask, past_key_values, labels, images)
  File "/home/jovyan/LLaVA-main/llava/model/llava_arch.py", line 103, in prepare_inputs_labels_for_multimodal
    image_features = self.encode_images(images)
  File "/home/jovyan/LLaVA-main/llava/model/llava_arch.py", line 83, in encode_images
    image_features = self.get_model().get_vision_tower()(images)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/jovyan/LLaVA-main/llava/model/multimodal_encoder/clip_encoder.py", line 48, in forward
    image_forward_outs = self.vision_tower(images.to(device=self.device, dtype=self.dtype), output_hidden_states=True)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/transformers/models/clip/modeling_clip.py", line 941, in forward
    return self.vision_model(
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/transformers/models/clip/modeling_clip.py", line 866, in forward
    hidden_states = self.embeddings(pixel_values)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/transformers/models/clip/modeling_clip.py", line 195, in forward
    patch_embeds = self.patch_embedding(pixel_values)  # shape = [*, width, grid, grid]
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/nn/modules/conv.py", line 463, in forward
    return self._conv_forward(input, self.weight, self.bias)
  File "/home/jovyan/.local/share/conda/envs/llava/lib/python3.10/site-packages/torch/nn/modules/conv.py", line 459, in _conv_forward
    return F.conv2d(input, weight, bias, self.stride,
RuntimeError: cuDNN error: CUDNN_STATUS_NOT_INITIALIZED

I have torch 2.0.0+cu117, and 4 A100 80Gb gpus.

this is how I changed LLaVA-Lightning-MPT-7B-preview model's config
{
  "_name_or_path": "llava-mpt-7b-pretrain_blip_558k_new_template_1e-instruct_conv_reason_nooverlap_80k-1epoch",
  "architectures": [
    "LlavaMPTForCausalLM"
  ],
  "attn_config": {
    "alibi": true,
    "alibi_bias_max": 8,
    "attn_impl": "torch",
    "attn_pdrop": 0,
    "attn_type": "multihead_attention",
    "attn_uses_sequence_id": false,
    "clip_qkv": null,
    "prefix_lm": false,
    "qk_ln": false,
    "softmax_scale": null
  },
  "d_model": 4096,
  "emb_pdrop": 0,
  "embedding_fraction": 1.0,
  "expansion_ratio": 4,
  "freeze_mm_mlp_adapter": false,
  "init_config": {
    "emb_init_std": null,
    "emb_init_uniform_lim": null,
    "fan_mode": "fan_in",
    "init_div_is_residual": true,
    "init_gain": 0,
    "init_nonlinearity": "relu",
    "init_std": 0.02,
    "name": "kaiming_normal_",
    "verbose": 0
  },
  "init_device": "cpu",
  "learned_pos_emb": true,
  "logit_scale": null,
  "max_seq_len": 2048,
  "mm_hidden_size": 1024,
  "mm_use_im_start_end": true,
  "mm_vision_select_layer": -2,
  "mm_vision_tower": "/home/jovyan/data-vol-1/model/llava/clip-vit-large-patch14-336",
  "model_type": "llava_mpt",
  "n_heads": 32,
  "n_layers": 32,
  "no_bias": true,
  "norm_type": "low_precision_layernorm",
  "resid_pdrop": 0,
  "sep_image_conv_front": false,
  "tokenizer_name": "/home/jovyan/LLaVA-main/pretrained/gpt-neox-20b-chatml",
  "torch_dtype": "float16",
  "transformers_version": "4.28.0.dev0",
  "tune_mm_mlp_adapter": false,
  "use_cache": true,
  "use_mm_proj": true,
  "verbose": 0,
  "vocab_size": 50282
}

I just changed mm_vision_tower and tokenizer_name to my local directories

also same error when I tried with "llava-v1.5-7b" model

Hello! I want to know how you solved this problem.

Same here. I want to know how you solved this problem.

I solve this use load_checkpoint to 4 bit like that:
tokenizer, model, image_processor, context_len = load_pretrained_model(
                                                                    model_path=args.model,
                                                                    model_base=None,
                                                                    model_name=model_name,
                                                                    load_4bit=True)

I think that error when VRAM GPU not enough to load checkpoint (This is case I debug when I catch this bug)


Use a spec field on WEPs for ServiceAccount name

Description

A third option for fixing https://github.com/projectcalico/calico/issues/4529
Fixes https://github.com/projectcalico/calico/issues/4529
Idea is:

Stop setting serviceaccount as a label on the WEP
Instead include it as a spec field. Convert to a label on Syncer API
to Felix so selection still works the same.

In kdd mode, this alone will be enough. The CNI plugin will stop sending
the label through, and since Felix reads directly from the Pod API will
keep receiving the same info over the Syncer.
For etcd mode, we need to make an additional change so that
kube-controllers properly updates old WEPs in the data store to include
the new spec field.
Alternatively, for etcd mode we could have kube-controllers add the
projectcalico.org/serviceaccount label itself. Any existing clusters
will not have any labels > 63 characters, and any new workloads that do
have such a long serviceaccount will be handled by the new CNI plugin
populating the spec field.
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

Fix issue with serviceaccount names larger than 63 characters.

I deployed the patch release with this in it and I am getting the following message:
Message:      OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/install-cni.sh": stat /install-cni.sh: no such file or directory: unknown
I was using v3.15.1 prior to this so this may be due to the large version change.


Specify less greedy flags when connecting to named pipes

Whilst working with named pipes on Node, I came across an issue where I wouldn't be able to connect to a pipe which had it's access permissions set to GENERIC_READ | FILE_WRITE_DATA. If the pipe had it's permissions set to GENERIC_READ | GENERIC_WRITE, any process that would be able to connect to the pipe would also be capable of spawning new server ends of the pipe. Or at least that's my interpretation of the docs on this.
Maybe this is would be best handled the same way read-only and write-only pipes are handled, i.e. try for GENERIC_READ | GENERIC_WRITE first and then attempt GENERIC_READ | GENERIC_WRITE ?

Will do! :+1:

I'll happily add a test specifically for testing the behaviour that I've changed here, but I'll only have time to do this sometime next week, is that still OK?

@pinkisemils: that is ok, we will wait.
In the mean time - CI to test if (and how) this change affects Node: https://ci.nodejs.org/view/libuv/job/libuv-in-node/56/

Before the CI results are lost to history...
The libuv CI fails on all Windows machines with:
not ok 147 - pipe_connect_to_file
# exit code 3
# Output from process `pipe_connect_to_file`:
# Assertion failed in test-pipe-connect-error.c on line 53: status == UV_ENOTSOCK || status == UV_ECONNREFUSED

The Node CI fails on Windows:
02:30:20 not ok 333 parallel/test-net-pipe-connect-errors
02:30:20   ---
02:30:20   duration_ms: 0.203
02:30:20   severity: fail
02:30:20   exitcode: 1
02:30:20   stack: |-
02:30:20     assert.js:338
02:30:20         throw err;
02:30:20         ^
02:30:20
02:30:20     AssertionError [ERR_ASSERTION]: received EINVAL instead of ENOTSOCK or ECONNREFUSED
02:30:20         at Socket.<anonymous> (c:\workspace\node-test-binary-windows\test\parallel\test-net-pipe-connect-errors.js:64:3)
02:30:20         at Socket.<anonymous> (c:\workspace\node-test-binary-windows\test\common\index.js:435:15)
02:30:20         at Socket.emit (events.js:182:13)
02:30:20         at emitErrorNT (internal/streams/destroy.js:82:8)
02:30:20         at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
02:30:20         at process._tickCallback (internal/process/next_tick.js:63:19)
02:30:20   ...

I'll look at it later on today, sorry for the lack of progress. I think I know the root cause of this. Speaking of testing, is there a reliable way of running these tests with the vc2017 toolchain instead of vc2015?

I believe the issue here is that libuv relies on the extra privileges to try and get more info about the pipe in case opening it as a pipe fails. Is this extra information really required? Could it not fail with a plain old - ENOTAPIPE or something simple?

@bzoz @libuv/windows feel free to reopen if you think we should still do this.

We've done something a bit similar in ebafb90acd6de8f2bf766ac58dc1091ddfacfad4, so there's perhaps some precedent for this. However, we couldn't land this as-is (as shown in the CI failures), since parts of libuv work better if we can get these permissions and plus it'd be inconsistent with the permissions requested on the fall-through branches.


System.Configuration and il-repack

for example, I have the following App.config
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <configSections>

  </configSections>
  <MyConfig NAS_IDENTIFIER="OpenVpn">
    <servers>
      <server name="radius1.kontur" authport="1818" wait="77" sharedsecret="secret1" />
      <server name="radius2.kontur" retries="7" sharedsecret="secret2" />
    </servers>
  </MyConfig>
</configuration>

(main assembly is auth.exe),
after I merge some DLL into it like
<Target Name="AfterBuild">
  <ItemGroup>
    <MergeAssemblies Include="$(OutputPath)\$(AssemblyName).exe" />
    <MergeAssemblies Include="$(OutputPath)\Radius.dll" />
  </ItemGroup>
  <PropertyGroup>
    <OutputAssembly>$(OutputPath)\$(AssemblyName).standalone.exe</OutputAssembly>
    <Merger Condition="('$(OS)' == 'Windows_NT')">"$(SolutionDir)\packages\ILRepack.1.26.0\tools\ILRepack.exe"</Merger>
    <Merger Condition="('$(OS)' != 'Windows_NT')">mono --runtime=v4.0.30319 "$(SolutionDir)\packages\ILRepack.1.26.0\tools\ILRepack.exe"</Merger>
  </PropertyGroup>
  <Message Text="MERGING: @(MergeAssemblies->'%(Filename)') into $(OutputAssembly)" Importance="High" />
  <Exec Command="$(Merger) /out:"$(OutputAssembly)" @(MergeAssemblies->'"%(FullPath)"', ' ')" />
</Target>

I'm getting the following error when I start auth.standalone.exe:
Unhandled Exception:
System.TypeInitializationException: An exception was thrown by the type initializer for auth.Config ---> System.Configuration.ConfigurationErrorsException: Type 'auth.Config,  auth' not found.
at System.Configuration.InternalConfigurationHost.GetConfigType (System.String typeName, Boolean throwOnError) [0x00000] in :0
at System.Configuration.ConfigInfo.CreateInstance () [0x00000] in :0
at System.Configuration.SectionInfo.CreateInstance () [0x00000] in :0
at System.Configuration.Configuration.GetSectionInstance (System.Configuration.SectionInfo config, Boolean createDefaultInstance) [0x00000] in :0
at System.Configuration.ConfigurationSectionCollection.get_Item (System.String name) [0x00000] in :0
at System.Configuration.Configuration.GetSection (System.String path) [0x00000] in :0
at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection (System.String configKey) [0x00000] in :0
at System.Configuration.ConfigurationManager.GetSection (System.String sectionName) [0x00000] in :0
at auth.Config..cctor () [0x00000] in :0
--- End of inner exception stack trace ---
at auth.Program.Main (System.String[] args) [0x00000] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An exception was thrown by the type initializer for auth.Config ---> System.Configuration.ConfigurationErrorsException: Type 'auth.Config,  auth' not found.
at System.Configuration.InternalConfigurationHost.GetConfigType (System.String typeName, Boolean throwOnError) [0x00000] in :0
at System.Configuration.ConfigInfo.CreateInstance () [0x00000] in :0
at System.Configuration.SectionInfo.CreateInstance () [0x00000] in :0
at System.Configuration.Configuration.GetSectionInstance (System.Configuration.SectionInfo config, Boolean createDefaultInstance) [0x00000] in :0
at System.Configuration.ConfigurationSectionCollection.get_Item (System.String name) [0x00000] in :0
at System.Configuration.Configuration.GetSection (System.String path) [0x00000] in :0
at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection (System.String configKey) [0x00000] in :0
at System.Configuration.ConfigurationManager.GetSection (System.String sectionName) [0x00000] in :0
at auth.Config..cctor () [0x00000] in :0
--- End of inner exception stack trace ---
at auth.Program.Main (System.String[] args) [0x00000] in :0
the fix is obvious, I have to rename

to

can il-repack do such magic ?

ILRepack can do magic, definitely :crystal_ball:
ConfigMerger already takes care of those config files (simply concat'ing their content).
If serialized type names can be easily identified in those configs, it should remap them.
Open for a contribution there if you feel like doing it.


Nice Work!

Hey @SabreValkyrn ,
Nice work on this!
Only request... if you use any project with an MIT License, it's important to keep the same MIT License.
Long chat on that here.
https://github.com/Gogo1951/GogoWatch/commit/686aa1c68493654616a69c374aa04d1dadf3258b#comments
Feel free to take any idea around features I had posted and run with them. https://github.com/Gogo1951/GogoWatch/projects/1
Glad someone is making this work!
Oh, and I'd love to see it work for SoM too if you get a chance. (=

Not to air too much dirty laundry, but I didn't know I could get kicked off my own Discord.
Here's the post I made there before Tex deleted it.
--
Hey everyone, I don't really want to be involved with this any more...
Just wanted to say that I am happy to have anyone take anything I've done and run with it.
I hated that this project stagnated.
Few points...
1 - I'm not a fan of Overwolf. Changing the license to promote Overwolf was not something I was across.

Update LICENSE · Gogo1951/GogoWatch@686aa1c | https://github.com/Gogo1951/GogoWatch/commit/686aa1c68493654616a69c374aa04d1dadf3258b#comments

2 - I think open-source is great, and anyone who wants to run with this has my blessing. It wasn't my idea, just an add-on that I thought was missing from Classic.

RankWatch - Addons - World of Warcraft - CurseForge | https://www.curseforge.com/wow/addons/rankwatch

Nice Work! · Issue #5 · valkyrnstudios/SpellSentinel | https://github.com/valkyrnstudios/SpellSentinel/issues/5

3 - The Original Files have been removed from GitHub at Tex's request.

Also Relevant!

Love Is Something (The Magic Penny) - YouTube || https://www.youtube.com/watch?v=4zqvcmsxCcI

Thanks for this! #6?
I tried to cover history, credits, and legality in #6. Would you mind reviewing and commenting on it for posterity?

Worked with @Gogo1951 via Discord to rebuild ability tables and discuss his roadmap ambitions for passing the torch.


scannetv2_raw_categories.json and cat2glove42b.json missing?

Hi, when trying to finetune on ScanQA it looks for  scannetv2_raw_categories.json and cat2glove42b.json which I couldn't find. Could you please add these files?

These files are Scannet configuration files, which is provided in our Readme. The link is here https://github.com/cshizhe/vil3dref


[proto] Draft for Transforms API v2

A draft for Transforms API v2

Closed in favor of https://github.com/pytorch/vision/pull/6305


Add an example for integration with an existing Qt app.

Description
Our Qt examples so far fall into two categories:

Integration with specific complex Qt apps (napari, PyFAI)
Integration with IPython for interactive use

This example demonstrates integration with a dead-simple minimal Qt application, as a jumping off point for integration with Qt applications in general.
Motivation and Context
For @JulReinhardt
How Has This Been Tested?
Run interactively.
python -m bluesky_widgets.examples.qt_app_integration

Screenshots (if appropriate):

Hi Dan, thanks for the example. I got a basic version running. Now I am trying to get it running using the queueserver. Where is the right place to define the figure model? Seems like I cannot do it in the qserver startup scripts. But it feels likes mixing realms when putting it into the GUI classes.

Hi Dan, thanks for the example. I got a basic version running. Now I am trying to get it running using the queueserver. Where is the right place to define the figure model? Seems like I cannot do it in the qserver startup scripts. But it feels likes mixing realms when putting it into the GUI classes.

I agree. I'd suggest placing the code that configures/instantiates models in a module by itself, e.g.
# plot_models.py

auto_lines = AutoLines(...)
# and probably additional, custom models as this grows...

and then importing those into wherever you are instantiating your GUI classes (which may or may not be the same place that you define them).
I'm sure we'll be wrestling with the best way to organize this too, and I'll let you know if we learn anything useful in the process.

I agree. I'd suggest placing the code that configures/instantiates models in a module by itself, e.g.
# plot_models.py

auto_lines = AutoLines(...)
# and probably additional, custom models as this grows...

and then importing those into wherever you are instantiating your GUI classes (which may or may not be the same place that you define them).
I'm sure we'll be wrestling with the best way to organize this too, and I'll let you know if we learn anything useful in the process.


Is it possible to pass query parameters in a SQL query?

Is your feature request related to a problem or challenge?
I would like to do smth like: execute("SELECT * FROM table WHERE id = ?", &[435]), is it possible?
Describe the solution you'd like
It would be nice to be able to pass the parameters as an array or something similar (instead of hardcoding them into the query-string)
Describe alternatives you've considered
No response
Additional context
No response

hi @shner-elmo  -- yes you can do this with PREPARE statements:
Here are some examples:
https://github.com/apache/arrow-datafusion/blob/b6f87edbbaaaedd696b2e448fcd7df7ad3cd2c93/datafusion/sqllogictest/test_files/prepare.slt#L18-L20
You can do it via a DataFrame like this:
https://docs.rs/datafusion/latest/datafusion/dataframe/struct.DataFrame.html#method.with_param_values
Something like
let ctx: SessionContext = ...;
ctx.sql(""SELECT * FROM table WHERE id = ?")
  .await?
  .with_param_values(vec![lit(435)])?
  .collect()

This is something that should be documented. I will try and do so

PR with documentation: https://github.com/apache/arrow-datafusion/pull/7785

(there are some rough edges around the usability that I fixed in https://github.com/apache/arrow-datafusion/pull/7785)


What to do next after creating a virtual env. & installing packages from requirement.txt?

I am pretty new to the python world & I have been able to successfully create virtual environment & installing packages from requirement.txt. But I can't figure out what to do next to run your code. Please help me out with the situation. I couldn't understand from the "Example".

Just create a python file, say example.py.
Inside it, paste the example code:
from copy_move_detection import detect
detect.detect('assets/', 'dataset_example_blur.png', 'output/', block_size=32)

And then make sure you have assets and output folder at the same hierarchy with the example.py.
Then insert your image (to be detected) inside assets folder.
Simply change the parameter of the code, say change the dataset_example_blur.png to your_image.png.
Finally, run the python script inside your venv :
python3 example.py


2024-04-12 17:00:03.691 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Searching for (['scheduled for delivery TODAY', 'zostanie dziś do Państwa doręczona', 'wird Ihnen heute', ' - Shipment is out with courier for delivery - ', 'Shipment is scheduled for delivery', 'voraussichtlich innerhalb']) in (1) emails
2024-04-12 17:00:03.691 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for (['scheduled for delivery TODAY', 'zostanie dziś do Państwa doręczona', 'wird Ihnen heute', ' - Shipment is out with courier for delivery - ', 'Shipment is scheduled for delivery', 'voraussichtlich innerhalb']) count results: 0
2024-04-12 17:00:03.691 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Paket kommt heute) results: b'' count: 0
2024-04-12 17:00:03.691 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Paket wird gleich zugestellt)
2024-04-12 17:00:03.691 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Paket wird gleich zugestellt
2024-04-12 17:00:03.692 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR OR OR OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "Paket wird gleich zugestellt" SINCE 12-Apr-2024)
2024-04-12 17:00:03.905 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:03.906 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Searching for (['scheduled for delivery TODAY', 'zostanie dziś do Państwa doręczona', 'wird Ihnen heute', ' - Shipment is out with courier for delivery - ', 'Shipment is scheduled for delivery', 'voraussichtlich innerhalb']) in (1) emails
2024-04-12 17:00:03.906 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for (['scheduled for delivery TODAY', 'zostanie dziś do Państwa doręczona', 'wird Ihnen heute', ' - Shipment is out with courier for delivery - ', 'Shipment is scheduled for delivery', 'voraussichtlich innerhalb']) count results: 0
2024-04-12 17:00:03.906 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Paket wird gleich zugestellt) results: b'' count: 0
2024-04-12 17:00:03.906 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Powiadomienie o przesyłce)
2024-04-12 17:00:03.907 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Powiadomienie o przesyłce
2024-04-12 17:00:03.907 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: OR OR OR OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SINCE 12-Apr-2024 SUBJECT
2024-04-12 17:00:04.348 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:04.348 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Searching for (['scheduled for delivery TODAY', 'zostanie dziś do Państwa doręczona', 'wird Ihnen heute', ' - Shipment is out with courier for delivery - ', 'Shipment is scheduled for delivery', 'voraussichtlich innerhalb']) in (1) emails
2024-04-12 17:00:04.348 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for (['scheduled for delivery TODAY', 'zostanie dziś do Państwa doręczona', 'wird Ihnen heute', ' - Shipment is out with courier for delivery - ', 'Shipment is scheduled for delivery', 'voraussichtlich innerhalb']) count results: 0
2024-04-12 17:00:04.349 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Powiadomienie o przesyłce) results: b'' count: 0
2024-04-12 17:00:04.349 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (DHL Shipment Notification)
2024-04-12 17:00:04.349 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: DHL Shipment Notification
2024-04-12 17:00:04.349 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR OR OR OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "DHL Shipment Notification" SINCE 12-Apr-2024)
2024-04-12 17:00:04.382 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:00:04.383 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None
2024-04-12 17:00:04.385 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: amazon_camera
2024-04-12 17:00:04.385 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None
2024-04-12 17:00:04.582 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:04.582 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Searching for (['scheduled for delivery TODAY', 'zostanie dziś do Państwa doręczona', 'wird Ihnen heute', ' - Shipment is out with courier for delivery - ', 'Shipment is scheduled for delivery', 'voraussichtlich innerhalb']) in (1) emails
2024-04-12 17:00:04.582 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for (['scheduled for delivery TODAY', 'zostanie dziś do Państwa doręczona', 'wird Ihnen heute', ' - Shipment is out with courier for delivery - ', 'Shipment is scheduled for delivery', 'voraussichtlich innerhalb']) count results: 0
2024-04-12 17:00:04.582 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (DHL Shipment Notification) results: b'' count: 0
2024-04-12 17:00:04.582 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: dhl_delivering Count: 0
2024-04-12 17:00:04.582 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: dhl_packages Count: 0
2024-04-12 17:00:04.583 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Your package has been delivered)
2024-04-12 17:00:04.583 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your package has been delivered
2024-04-12 17:00:04.583 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "Your package has been delivered" SINCE 12-Apr-2024)
2024-04-12 17:00:04.805 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:04.805 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Your package has been delivered) results: b'' count: 0
2024-04-12 17:00:04.805 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Your packages have been delivered)
2024-04-12 17:00:04.805 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your packages have been delivered
2024-04-12 17:00:04.805 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "Your packages have been delivered" SINCE 12-Apr-2024)
2024-04-12 17:00:05.083 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:05.084 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Your packages have been delivered) results: b'' count: 0
2024-04-12 17:00:05.084 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: fedex_delivered Count: 0
2024-04-12 17:00:05.084 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Delivery scheduled for today)
2024-04-12 17:00:05.084 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Delivery scheduled for today
2024-04-12 17:00:05.084 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "Delivery scheduled for today" SINCE 12-Apr-2024)
2024-04-12 17:00:05.306 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:05.307 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Delivery scheduled for today) results: b'' count: 0
2024-04-12 17:00:05.307 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Your package is scheduled for delivery today)
2024-04-12 17:00:05.307 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your package is scheduled for delivery today
2024-04-12 17:00:05.307 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "Your package is scheduled for delivery today" SINCE 12-Apr-2024)
2024-04-12 17:00:05.547 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:05.547 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Your package is scheduled for delivery today) results: b'' count: 0
2024-04-12 17:00:05.547 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Your package is now out for delivery)
2024-04-12 17:00:05.547 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your package is now out for delivery
2024-04-12 17:00:05.547 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "Your package is now out for delivery" SINCE 12-Apr-2024)
2024-04-12 17:00:05.782 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:05.783 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (Your package is now out for delivery) results: b'' count: 0
2024-04-12 17:00:05.783 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (out for delivery today)
2024-04-12 17:00:05.783 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: out for delivery today
2024-04-12 17:00:05.783 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>SUBJECT "out for delivery today" SINCE 12-Apr-2024)
2024-04-12 17:00:05.997 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:05.997 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS><EMAIL_ADDRESS>with subject (out for delivery today) results: b'' count: 0
2024-04-12 17:00:05.997 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: fedex_delivering Count: 0
2024-04-12 17:00:05.997 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: fedex_packages Count: 0
2024-04-12 17:00:05.998 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: mail_updated Count: 2024-04-13 00:00:05.998027+00:00
2024-04-12 17:00:05.998 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Your UPS Package was delivered)
2024-04-12 17:00:05.998 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your UPS Package was delivered
2024-04-12 17:00:05.998 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Your UPS Package was delivered" SINCE 12-Apr-2024)
2024-04-12 17:00:06.207 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:06.208 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Your UPS Package was delivered) results: b'' count: 0
2024-04-12 17:00:06.208 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Your UPS Packages were delivered)
2024-04-12 17:00:06.208 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your UPS Packages were delivered
2024-04-12 17:00:06.208 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Your UPS Packages were delivered" SINCE 12-Apr-2024)
2024-04-12 17:00:06.420 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:06.420 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Your UPS Packages were delivered) results: b'' count: 0
2024-04-12 17:00:06.421 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Your UPS Parcel was delivered)
2024-04-12 17:00:06.421 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your UPS Parcel was delivered
2024-04-12 17:00:06.421 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Your UPS Parcel was delivered" SINCE 12-Apr-2024)
2024-04-12 17:00:06.676 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:06.676 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Your UPS Parcel was delivered) results: b'' count: 0
2024-04-12 17:00:06.676 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Your UPS Parcels were delivered)
2024-04-12 17:00:06.676 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your UPS Parcels were delivered
2024-04-12 17:00:06.676 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Your UPS Parcels were delivered" SINCE 12-Apr-2024)
2024-04-12 17:00:06.897 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:06.897 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Your UPS Parcels were delivered) results: b'' count: 0
2024-04-12 17:00:06.897 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: ups_delivered Count: 0
2024-04-12 17:00:06.898 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (UPS Update: Package Scheduled for Delivery Today)
2024-04-12 17:00:06.898 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: UPS Update: Package Scheduled for Delivery Today
2024-04-12 17:00:06.898 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "UPS Update: Package Scheduled for Delivery Today" SINCE 12-Apr-2024)
2024-04-12 17:00:07.111 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:07.111 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (UPS Update: Package Scheduled for Delivery Today) results: b'' count: 0
2024-04-12 17:00:07.111 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (UPS Update: Follow Your Delivery on a Live Map)
2024-04-12 17:00:07.111 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: UPS Update: Follow Your Delivery on a Live Map
2024-04-12 17:00:07.112 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "UPS Update: Follow Your Delivery on a Live Map" SINCE 12-Apr-2024)
2024-04-12 17:00:07.322 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:07.323 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (UPS Update: Follow Your Delivery on a Live Map) results: b'' count: 0
2024-04-12 17:00:07.323 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (UPS Pre-Arrival: Your Driver is Arriving Soon! Follow on a Live Map)
2024-04-12 17:00:07.323 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: UPS Pre-Arrival: Your Driver is Arriving Soon! Follow on a Live Map
2024-04-12 17:00:07.323 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "UPS Pre-Arrival: Your Driver is Arriving Soon! Follow on a Live Map" SINCE 12-Apr-2024)
2024-04-12 17:00:07.576 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:07.576 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (UPS Pre-Arrival: Your Driver is Arriving Soon! Follow on a Live Map) results: b'' count: 0
2024-04-12 17:00:07.576 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (UPS Update: Parcel Scheduled for Delivery Today)
2024-04-12 17:00:07.576 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: UPS Update: Parcel Scheduled for Delivery Today
2024-04-12 17:00:07.576 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "UPS Update: Parcel Scheduled for Delivery Today" SINCE 12-Apr-2024)
2024-04-12 17:00:07.789 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:07.789 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (UPS Update: Parcel Scheduled for Delivery Today) results: b'' count: 0
2024-04-12 17:00:07.789 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: ups_delivering Count: 0
2024-04-12 17:00:07.789 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (UPS Update: New Scheduled Delivery Date)
2024-04-12 17:00:07.790 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: UPS Update: New Scheduled Delivery Date
2024-04-12 17:00:07.790 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "UPS Update: New Scheduled Delivery Date" SINCE 12-Apr-2024)
2024-04-12 17:00:07.999 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:07.999 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (UPS Update: New Scheduled Delivery Date) results: b'' count: 0
2024-04-12 17:00:07.999 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: ups_exception Count: 0
2024-04-12 17:00:08.000 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: ups_packages Count: 0
2024-04-12 17:00:08.000 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Item Delivered)
2024-04-12 17:00:08.000 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Item Delivered
2024-04-12 17:00:08.000 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Item Delivered" SINCE 12-Apr-2024)
2024-04-12 17:00:08.210 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b'136359'])
2024-04-12 17:00:08.210 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Item Delivered) results: b'136359' count: 1
2024-04-12 17:00:08.210 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: usps_delivered Count: 1
2024-04-12 17:00:08.211 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Expected Delivery on)
2024-04-12 17:00:08.211 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Expected Delivery on
2024-04-12 17:00:08.211 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Expected Delivery on" SINCE 12-Apr-2024)
2024-04-12 17:00:08.434 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b'136273<PHONE_NUMBER>76<PHONE_NUMBER>85<PHONE_NUMBER>07<PHONE_NUMBER>80'])
2024-04-12 17:00:08.435 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Searching for (['Your item is out for delivery']) in (1) emails
2024-04-12 17:00:08.838 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: multipart/mixed
2024-04-12 17:00:08.839 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: text/html
2024-04-12 17:00:09.116 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: multipart/mixed
2024-04-12 17:00:09.116 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: text/html
2024-04-12 17:00:09.371 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: multipart/mixed
2024-04-12 17:00:09.372 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: text/html
2024-04-12 17:00:09.720 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: multipart/mixed
2024-04-12 17:00:09.720 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: text/html
2024-04-12 17:00:10.006 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: multipart/mixed
2024-04-12 17:00:10.007 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: text/html
2024-04-12 17:00:10.278 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: multipart/mixed
2024-04-12 17:00:10.278 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: text/html
2024-04-12 17:00:10.278 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found (Your item is out for delivery) in email 1 times.
2024-04-12 17:00:10.518 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: multipart/mixed
2024-04-12 17:00:10.518 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: text/html
2024-04-12 17:00:10.519 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found (Your item is out for delivery) in email 1 times.
2024-04-12 17:00:10.763 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: multipart/mixed
2024-04-12 17:00:10.764 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: text/html
2024-04-12 17:00:11.021 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: multipart/mixed
2024-04-12 17:00:11.021 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Content type: text/html
2024-04-12 17:00:11.021 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for (['Your item is out for delivery']) count results: 2
2024-04-12 17:00:11.022 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Expected Delivery on) results: b'136273<PHONE_NUMBER>76<PHONE_NUMBER>85<PHONE_NUMBER>07<PHONE_NUMBER>80' count: 2
2024-04-12 17:00:11.022 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Out for Delivery)
2024-04-12 17:00:11.022 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Out for Delivery
2024-04-12 17:00:11.022 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Out for Delivery" SINCE 12-Apr-2024)
2024-04-12 17:00:11.257 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:11.257 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Searching for (['Your item is out for delivery']) in (1) emails
2024-04-12 17:00:11.257 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for (['Your item is out for delivery']) count results: 0
2024-04-12 17:00:11.257 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Out for Delivery) results: b'' count: 2
2024-04-12 17:00:11.257 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Searching for tracking numbers in 9 messages...
2024-04-12 17:00:11.538 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking message subject...
2024-04-12 17:00:11.539 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found tracking number in email subject:<PHONE_NUMBER>464013116432)
2024-04-12 17:00:11.783 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking message subject...
2024-04-12 17:00:11.785 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found tracking number in email subject:<PHONE_NUMBER>464013116432)
2024-04-12 17:00:12.024 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking message subject...
2024-04-12 17:00:12.025 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found tracking number in email subject:<PHONE_NUMBER>464013116432)
2024-04-12 17:00:12.278 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking message subject...
2024-04-12 17:00:12.278 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found tracking number in email subject:<PHONE_NUMBER>464013116432)
2024-04-12 17:00:12.517 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking message subject...
2024-04-12 17:00:12.517 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found tracking number in email subject:<PHONE_NUMBER>464013116432)
2024-04-12 17:00:12.754 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking message subject...
2024-04-12 17:00:12.754 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found tracking number in email subject:<PHONE_NUMBER>464013116432)
2024-04-12 17:00:12.996 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking message subject...
2024-04-12 17:00:12.996 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found tracking number in email subject:<PHONE_NUMBER>464013116432)
2024-04-12 17:00:13.234 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking message subject...
2024-04-12 17:00:13.234 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found tracking number in email subject:<PHONE_NUMBER>644808544524)
2024-04-12 17:00:13.474 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking message subject...
2024-04-12 17:00:13.474 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found tracking number in email subject:<PHONE_NUMBER>644808544524)
2024-04-12 17:00:13.475 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Searching for tracking numbers in 0 messages...
2024-04-12 17:00:13.475 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] No tracking numbers found
2024-04-12 17:00:13.475 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: usps_delivering Count: 1
2024-04-12 17:00:13.475 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Delivery Exception)
2024-04-12 17:00:13.475 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Delivery Exception
2024-04-12 17:00:13.475 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Delivery Exception" SINCE 12-Apr-2024)
2024-04-12 17:00:13.696 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:13.696 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Delivery Exception) results: b'' count: 0
2024-04-12 17:00:13.696 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: usps_exception Count: 0
2024-04-12 17:00:13.697 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find Informed Delivery mail
2024-04-12 17:00:13.697 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Informed delivery search date: 12-Apr-2024
2024-04-12 17:00:13.697 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your Daily Digest
2024-04-12 17:00:13.697 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR OR OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM "USPS Informed Delivery" SUBJECT "Your Daily Digest" SINCE 12-Apr-2024)
2024-04-12 17:00:13.911 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b'136296'])
2024-04-12 17:00:13.912 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Cleaning up image directory: /config/custom_components/mail_and_packages/images/
2024-04-12 17:00:14.327 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Checking for overlay files in: /config/custom_components/mail_and_packages/images/
2024-04-12 17:00:14.327 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Copying file to: /config/custom_components/mail_and_packages/images/overlay.png
2024-04-12 17:00:14.397 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Copying file to: /config/custom_components/mail_and_packages/images/vignette.png
2024-04-12 17:00:14.401 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Copying file to: /config/custom_components/mail_and_packages/images/white.png
2024-04-12 17:00:14.454 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Informed Delivery email found processing...
2024-04-12 17:00:15.171 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] msg: Delivered-To<EMAIL_ADDRESS>2024-04-12 17:00:15.206 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Found html email processing...
2024-04-12 17:00:15.306 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Unexpected html format found.
2024-04-12 17:00:15.306 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Extracting image from email
2024-04-12 17:00:15.306 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Discarding junk mail.
2024-04-12 17:00:15.307 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Extracting image from email
2024-04-12 17:00:15.307 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Discarding junk mail.
2024-04-12 17:00:15.307 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Extracting image from email
2024-04-12 17:00:15.311 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Extracting image from email
2024-04-12 17:00:15.315 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Removing duplicate images.
2024-04-12 17:00:15.369 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Removing USPS announcement images.
2024-04-12 17:00:15.369 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Image Count: 2
2024-04-12 17:00:15.369 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Resizing images to 724x320...
2024-04-12 17:00:15.594 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Creating array of image files...
2024-04-12 17:00:15.596 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Generating animated GIF
2024-04-12 17:00:15.658 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Mail image generated.
2024-04-12 17:00:15.661 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: usps_mail Count: 2
2024-04-12 17:00:15.662 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: usps_packages Count: 2
2024-04-12 17:00:15.662 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Your order was delivered)
2024-04-12 17:00:15.662 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Your order was delivered
2024-04-12 17:00:15.662 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Your order was delivered" SINCE 12-Apr-2024)
2024-04-12 17:00:15.874 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:15.874 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Your order was delivered) results: b'' count: 0
2024-04-12 17:00:15.874 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Some of your items were delivered)
2024-04-12 17:00:15.874 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Some of your items were delivered
2024-04-12 17:00:15.875 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Some of your items were delivered" SINCE 12-Apr-2024)
2024-04-12 17:00:16.084 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:16.084 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Some of your items were delivered) results: b'' count: 0
2024-04-12 17:00:16.085 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Delivered:)
2024-04-12 17:00:16.085 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Delivered:
2024-04-12 17:00:16.085 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Delivered:" SINCE 12-Apr-2024)
2024-04-12 17:00:16.302 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:16.302 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Delivered:) results: b'' count: 0
2024-04-12 17:00:16.302 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: walmart_delivered Count: 0
2024-04-12 17:00:16.302 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Out for delivery)
2024-04-12 17:00:16.302 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG subject: Out for delivery
2024-04-12 17:00:16.302 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Out for delivery" SINCE 12-Apr-2024)
2024-04-12 17:00:16.509 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] email_search value: ('OK', [b''])
2024-04-12 17:00:16.509 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Out for delivery) results: b'' count: 0
2024-04-12 17:00:16.509 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: walmart_delivering Count: 0
2024-04-12 17:00:16.509 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: zpackages_delivered Count: 1
2024-04-12 17:00:16.509 DEBUG (SyncWorker_32) [custom_components.mail_and_packages.helpers] Sensor: zpackages_transit Count: 1
2024-04-12 17:00:16.581 DEBUG (MainThread) [custom_components.mail_and_packages] Finished fetching Mail and Packages (imap.gmail.com) data in 42.553 seconds (success: True)
2024-04-12 17:00:16.582 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] USPS Check: True
2024-04-12 17:00:16.587 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] USPS Image hash: 4b4378ea18fd47383886b88f060f4f31aae0d081
2024-04-12 17:00:16.587 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] USPS None hash: a0f0065114d47d9e9e24b938f6461ecdb5166368
2024-04-12 17:00:16.588 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] Amazon Check: True
2024-04-12 17:00:16.637 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] Amazon Image hash: 0e7c4b3558ab5b356a6aca738ebc0c973846701d
2024-04-12 17:00:16.638 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] Amazon None hash: 0e7c4b3558ab5b356a6aca738ebc0c973846701d
2024-04-12 17:00:16.640 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Updating system image path to: custom_components/mail_and_packages/images/
2024-04-12 17:00:34.383 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:00:34.383 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None
2024-04-12 17:00:34.385 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: amazon_camera
2024-04-12 17:00:34.385 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None
2024-04-12 17:01:04.392 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:01:04.392 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None
2024-04-12 17:01:04.393 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: amazon_camera
2024-04-12 17:01:04.393 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None
2024-04-12 17:01:34.393 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:01:34.393 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None
2024-04-12 17:01:34.395 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: amazon_camera
2024-04-12 17:01:34.395 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Custom No Mail: None

Perhaps the issue is the todays address in the email itself?
Hello ,
Your item departed our USPS facility in SPOKANE WA DISTRIBUTION CENTER on April 12, 2024 at 2:14 pm. The item is currently in transit to the destination.
Tracking Number:<PHONE_NUMBER>644808549876
Expected Delivery On
13
Apr
By 9:00pm
By 9:00pm
Tracking & Delivery Options

Here is a log I took after re configuring that:
2024-04-12 17:21:34.684 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.helpers] Removing USPS announcement images.
2024-04-12 17:21:34.970 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.helpers] Sensor: usps_mail Count: 2
2024-04-12 17:21:34.970 DEBUG (SyncWorker_1) [custom_components.mail_and_packages.helpers] Sensor: usps_packages Count: 2
2024-04-12 17:21:35.062 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:21:35.772 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] USPS Check: True
2024-04-12 17:21:35.862 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] USPS Image hash: 4b4378ea18fd47383886b88f060f4f31aae0d081
2024-04-12 17:21:35.862 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] USPS None hash: a0f0065114d47d9e9e24b938f6461ecdb5166368
2024-04-12 17:22:05.063 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:22:35.064 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:23:05.065 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:23:35.065 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:24:05.066 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:24:35.067 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:25:05.069 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:25:35.219 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:26:05.222 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:26:35.222 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:27:05.224 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:27:35.225 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:28:27.448 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Item Delivered)
2024-04-12 17:28:27.448 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Item Delivered" SINCE 12-Apr-2024)
2024-04-12 17:28:27.662 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Item Delivered) results: b'136359' count: 1
2024-04-12 17:28:27.662 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Sensor: usps_delivered Count: 1
2024-04-12 17:28:27.662 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Expected Delivery on)
2024-04-12 17:28:27.662 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Expected Delivery on" SINCE 12-Apr-2024)
2024-04-12 17:28:30.104 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Expected Delivery on) results: b'136273<PHONE_NUMBER>76<PHONE_NUMBER>85<PHONE_NUMBER>07<PHONE_NUMBER>80' count: 2
2024-04-12 17:28:30.105 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Out for Delivery)
2024-04-12 17:28:30.105 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Out for Delivery" SINCE 12-Apr-2024)
2024-04-12 17:28:30.302 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Out for Delivery) results: b'' count: 2
2024-04-12 17:28:32.438 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Sensor: usps_delivering Count: 1
2024-04-12 17:28:32.439 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Attempting to find mail from<EMAIL_ADDRESS>with subject (Delivery Exception)
2024-04-12 17:28:32.439 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (FROM<EMAIL_ADDRESS>SUBJECT "Delivery Exception" SINCE 12-Apr-2024)
2024-04-12 17:28:32.639 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Search for<EMAIL_ADDRESS>with subject (Delivery Exception) results: b'' count: 0
2024-04-12 17:28:32.639 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Sensor: usps_exception Count: 0
2024-04-12 17:28:32.640 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] DEBUG imap_search: (OR OR OR FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM<EMAIL_ADDRESS>FROM "USPS Informed Delivery" SUBJECT "Your Daily Digest" SINCE 12-Apr-2024)
dkim=pass<EMAIL_ADDRESS>header.s=krs header.b=naS81TXf;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=email.informeddelivery.usps.com
Return-Path<EMAIL_ADDRESS>Received: from mg196.informeddelivery.usps.com (mg196.informeddelivery.usps.com. [<IP_ADDRESS>])
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
dkim=pass<EMAIL_ADDRESS>header.s=krs header.b=naS81TXf;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=email.informeddelivery.usps.com
DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=email.informeddelivery.usps.com; q=dns/txt; s=krs; t=1712931466; x=1712938666;
X-Feedback-Id: USPSInformeddelivery@email.informeddelivery.usps.com::628d49d589e2a96a9951e974:mailgun
Sender<EMAIL_ADDRESS>From: USPS Informed Delivery<EMAIL_ADDRESS>Message-Id<EMAIL_ADDRESS>https://informeddelivery.usps.com/box/pages/secure/DashboardAction_input?ke=
You subscribed to this service with USPS(R) New Products & Innovation, PO B=
https://informeddelivery.usps.com/box/pages/unsubscribe/confirm?id=3D231682=
ormed Delivery(TM) and the trade dress of USPS(R) Packaging are among the m=
ng-bottom: 10px;text-align:left"><a href=3D"https://www.usps.com/" st=
" tabindex=3D"1"><img src=3D"https://www.usps.com/real-mail/images/logo_mob=
ile.png" width=3D"64" height=3D"36" style=3D"border: none;" alt=3D"USPS.com=
" data-responsive=3D"true" src=3D"https://www.usps.com/email/id/IDdailyDmai=
k" href=3D"https://informeddelivery.usps.com/box/pages/secure/DashboardActi=
ng-image-href-id" target=3D"_blank" href=3D"https://informeddelivery.usps.c=
href=3D"https://informeddelivery.usps.com/tracking/ClickTrack?token=3D09d81=
17f83&source=3Dimage&origin=3DcloudDigest"><img src=3D"https://www.usps.com=
lank" href=3D"https://informeddelivery.usps.com/tracking/ClickTrack?token=
=3D"_blank" href=3D"https://informeddelivery.usps.com/box/pages/reminderImb=
ivery.usps.com/box/pages/reminderImb/confirm?campId=3D1200451061&deliveryDa=
08294110"><img src=3D"https://www.usps.com/email/id/Icon-Calendar.png" alt=
href-id-secondary" target=3D"_blank" href=3D"https://informeddelivery.usps.=
ef=3D"https://informeddelivery.usps.com/box/pages/reminderImb/confirm?deliv=
6899208294110" src=3D"https://informeddelivery.usps.com/box/pages/reminderI=
27010650215386346899208294110"><img src=3D"https://www.usps.com/email/id/Ic=
=3D"_blank" href=3D"https://informeddelivery.usps.com/box/pages/reminderImb=
ef=3D"https://informeddelivery.usps.com/box/pages/reminderImb/confirm?deliv=
4699208294110" src=3D"https://informeddelivery.usps.com/box/pages/reminderI=
27120054400139294699208294110"><img src=3D"https://www.usps.com/email/id/Ic=
=3D"_blank" href=3D"https://informeddelivery.usps.com/box/pages/reminderImb=
://informeddelivery.usps.com/box/pages/secure/DashboardAction_input?keyword=
ttps://informeddelivery.usps.com/box/pages/secure/packageDashboardAction?se=
"tools.usps.com/go/TrackConfirmAction?tRef=3Dfullpage&tLc=3D2&text28777=3D&=
h=3D"800" height=3D"200" src=3D"https://www.usps.com/email/id/desktop-refer=
"https://www.usps.com/email/id/mobile-refer-friend.jpg" style=3D"display:no=
href=3D"https://informeddelivery.usps.com/tracking/Referral?a=3Df3J9B15-xZF=
ref=3D"https://informeddelivery.usps.com/tracking/Referral?a=3DqPFqp0WFYkph=
y.usps.com/box/pages/secure/DashboardAction_input?keyword=3Dmail" class=3D"=
ng-mailpiece-href-id" href=3D"https://informeddelivery.usps.com/box/pages/m=
se images represent mail pieces that are sorted on USPS=C2=AE au=
legal">You subscribed to this service with USPS=C2=AE Innovative=
d=3D"unsubscribe-url-link" href=3D"https://informeddelivery.usps.com/box/pa=
<a href=3D"https://usps.force.com/emailus/s/?path=3D003010070" target=3D"_b=
=3D"https://faq.usps.com/s/" tabindex=3D"7" class=3D"inline-link" style=3D"=
de dress of USPS=C2=AE Packaging are among the many trademarks o=
informeddelivery.usps.com/tracking/emailRead?emailToken=3D09d81f82-9994-4ba=
2024-04-12 17:28:33.982 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Removing USPS announcement images.
2024-04-12 17:28:34.253 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Sensor: usps_mail Count: 2
2024-04-12 17:28:34.253 DEBUG (SyncWorker_25) [custom_components.mail_and_packages.helpers] Sensor: usps_packages Count: 2
2024-04-12 17:28:35.252 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] USPS Check: True
2024-04-12 17:28:35.258 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] USPS Image hash: 4b4378ea18fd47383886b88f060f4f31aae0d081
2024-04-12 17:28:35.258 DEBUG (MainThread) [custom_components.mail_and_packages.binary_sensor] USPS None hash: a0f0065114d47d9e9e24b938f6461ecdb5166368
2024-04-12 17:29:05.271 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera
2024-04-12 17:29:35.272 DEBUG (MainThread) [custom_components.mail_and_packages.camera] Camera Update: usps_camera

Thank you, this is very helpful.
Looks like the issue is here:
https://github.com/moralmunky/Home-Assistant-Mail-And-Packages/blob/00aeb76e0bb1bccd0ac0ba0e5acf58c3175cec54/custom_components/mail_and_packages/const.py#L177
Likely we'll need to adjust the subject search here to clear this up.

The one that was counted correctly also has a similar subject: "USPS® Expected Delivery on Friday, April 12, 2024 arriving by 2:45pm<PHONE_NUMBER>464013116765"
That's the good delivery, the one I expected to be counted.
Is there a way to use the date in the subject to determine if it should be counted?

Can you verify the phrase: "Your item is out for delivery" isn't in the email for the 13th?

Thats correct.
On Fri, Apr 12, 2024, 6:49 PM Chris @.***> wrote:

Can you verify the phrase: "Your item is out for delivery" isn't in the
email for the 13th?
—
Reply to this email directly, view it on GitHub
https://github.com/moralmunky/Home-Assistant-Mail-And-Packages/issues/883#issuecomment-2052943264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARQFDKFZOVKE7Z3TPDOOFYTY5CFKTAVCNFSM6AAAAABFKDDQBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSHE2DGMRWGQ
.
You are receiving this because you were assigned.Message ID:
@.***
com>

So any thoughts on what can be done to fix the bug? It just happened again. As you can see today is Saturday the 20th but it's picked up this email for Monday the 22nd.
.

It's weird it shouldn't be picking up these as the subject doesn't match the pattern.

This is the only other one that mentions this tracking number.

It's weird it shouldn't be picking up these as the subject doesn't match the pattern.

It is weird, but it seems it must be picking them up somehow. It's happened again today. You can see the time chart when it changes is when I received this first email about expected delivery for the next day. [

I wonder if your timezone in Home Assistant may be incorrect or something.

Yes, it is incorrect. Docker -v /etc/timezone and also TZ don't work,
neither does setting time_zone in config yaml.
So yes, it's off by one hour according to home assistant settings. But this
got picked up over 6 hours early, which the one hour time difference
doesn't explain.
I've manually changed the timezone in the home assistant settings to the
correct time. I'll let you know if the it changes anything.
On Tue, May 14, 2024, 6:32 AM Chris @.***> wrote:

I wonder if your timezone in Home Assistant may be incorrect or something.
—
Reply to this email directly, view it on GitHub
https://github.com/moralmunky/Home-Assistant-Mail-And-Packages/issues/883#issuecomment-2110258184,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARQFDKDYPD54XJRWXIS3QETZCIG7VAVCNFSM6AAAAABFKDDQBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJQGI2TQMJYGQ
.
You are receiving this because you were assigned.Message ID:
@.***
com>

If you run date inside the container is it reporting the date/time UTC?

If it shows UTC as the timezone try adding the volume like below:
    volumes:
      - /etc/localtime:/etc/localtime:ro

This is how I have my container localtime mapped in.

Yes, thats what I meant. Apparently I was wrong, the time is and was
correct before I messed with it. Sever time and HA time are correct. So
still not sure why next day deliveries are sometime picked up.
On Tue, May 14, 2024, 10:24 AM Chris @.***> wrote:

If it shows UTC as the timezone try adding the volume like below:
volumes:
  - /etc/localtime:/etc/localtime:ro

This is how I have my container localtime mapped in.
—
Reply to this email directly, view it on GitHub
https://github.com/moralmunky/Home-Assistant-Mail-And-Packages/issues/883#issuecomment-2110757726,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARQFDKDKFT3GEM5KPGAAO4TZCJCFPAVCNFSM6AAAAABFKDDQBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJQG42TONZSGY
.
You are receiving this because you were assigned.Message ID:
@.***
com>


[WIP] [Compaction] Stagger the start of full compaction between multiple replicas on a disk.

This is needed to ensure that all the stores on a disk do not start full compaction at the same time.

Codecov Report
Patch coverage: 100.00% and project coverage change: -58.92 :warning:

Comparison is base (302456e) 72.80% compared to head (fd0dbe7) 13.88%.

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2508       +/-   ##
=============================================
- Coverage     72.80%   13.88%   -58.92%
+ Complexity    11157     2366     -8791
=============================================
  Files           790      790
  Lines         63084    63121       +37
  Branches       7710     7716        +6
=============================================
- Hits          45928     8766    -37162
- Misses        14650    53845    +39195
+ Partials       2506      510     -1996

Impacted Files
Coverage Δ

...main/java/com/github/ambry/config/StoreConfig.java
98.33% <100.00%> (-1.67%)
:arrow_down:

...com/github/ambry/store/HybridCompactionPolicy.java
74.62% <100.00%> (+0.38%)
:arrow_up:

... and 627 files with indirect coverage changes

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


Update README file

Several new users have been confused by the readme file for 1.5 Even though it is unsupported, I think we should remove the readme that instructs people to create a config file. At the very least, remove the readme altogether, or add a short note about using the web ui.

I updated the readme for the "database-and-api" branch.
I also updated the text below release 1.5 on the releases page, in case anybody reads that.


Relax Publishing API schema for specialist documents

Context
When creating or editing Specialist Documents, we need to make some changes in Publishing API and regenerate the schemas. The schemas, and the underlying files that help generate the schemas, where the manual changes are made, are quite verbose when it comes to specifying facets and document types.
To reduce effort in creating and maintaining specialist document configuration, we can reduce the specificity of the schemas. We believe validating that facets and document type are simple strings, rather than maintaining a full list of options to validate against, is valuable enough. This is what these commits achieve.
Changes

remove enums from _specialist_document shared definitions, so that facets are only validated as strings
remove document_type enums from specialist_document schemas, so that it's now only validated as a string
remove specialist document types from allowed_document_types list
add custom logic for specialist documents, so that the schema generators behave differently when dealing with them
add test to cover new exception logic

Note - alternative path we've looked into
We also considered maintaining the document_type enum and validation, instead reducing maintenance cost by removing the allowed_document_types list. The list is used as an additional "whitelisting" check, and as a fallback when a document type is not provided. There is no actual schema in publishing_api that does not have a document_type specified, meaning we could raise an error if the document type is not provided, instead of defaulting to allow list logic here.
Nonetheless, there are some generic and generic_with_external_related_links schemas that do make use of the allowed types as they do not provide a document type. We could provide any random string as a type, but it seems other publishing apps use these generic schemas to run tests, making this change rather costly as it involves fixing many failures across several repos.
Links
Trello

Argh - this has broken our build on GOV.UK Chat. As we validate that the document types we care about are actually valid document types
It's a bit weird that we now have a method GovukSchemas::DocumentTypes.valid_document_types that now returns an incomplete list - could we consider reverting this until we can either deprecate or have alternative means to resolve the API issues this causes on GovukSchemas?

Also expect this will break the dev docs: https://github.com/search?q=repo%3Aalphagov%2Fgovuk-developer-docs+allowed_document_types&type=code

Understanding this a bit more it looks like this would remove what is our only list definitive list of document types for GOV.UK so would strongly suggest rethinking this as we'll lose that resource.
It feels like you could save a maintenance overhead by only updating one list.
Also seems an unlikely situation to have to add a new specialist document type and not make any schema changes - given it's a new type of content, something in the schemas should know about that.

Linking #2917 for reference on what we reverted.

Understanding this a bit more it looks like this would remove what is our only list definitive list of document types for GOV.UK so would strongly suggest rethinking this as we'll lose that resource.
It feels like you could save a maintenance overhead by only updating one list.
Also seems an unlikely situation to have to add a new specialist document type and not make any schema changes - given it's a new type of content, something in the schemas should know about that.

We were not aware that the allowed list is used as a reference definitive list. We even looked into removing the allowed list completely (broke many tests that use the generic schemas). It's these generic (and generic with links) schemas that use the entire list of allowed documents. Otherwise all other ("real") schemas get their own document_type field which is used by the schema generators. You can see in #2917 that the generic schemas were the only ones to change upon reintroducing the specialist document types in the allowed list.
This unlikely situation is the "relaxation" we've introduced. Upon adding a new specialist document type, none of the specialist document schemas will change.


decouple circuit breaker

Coverage increased (+0.3%) to 64.882% when pulling 7e69b8f52bc4e504d179f8fc919bc79d3c4c3adc on tianxiaoliang:master into fab00e1f56fe17bc035d8b98006d3cb88af2dcbf on go-chassis:master.


Added 'once' to the exposed api

Main changes are here and the test here. The rest was my editor doing some formatting on save.


import segmentation without @type

When I open existing PAGE-XML files with standalone LAREX – yes, I have managed to get around #160 and #162 in a Docker build (so when I have time, we'll get to the bottom of this) – then the UI keeps showing an hourglass and I see these exceptions on the console:
	at org.primaresearch.dla.page.layout.physical.text.impl.TextRegion.getTextType(TextRegion.java:149)
	at de.uniwue.web.io.PageXMLReader.getPageAnnotations(PageXMLReader.java:99)
	at de.uniwue.web.io.PageXMLReader.loadPageAnnotationsFromDisc(PageXMLReader.java:208)
	at de.uniwue.web.controller.DataController.getAnnotations(DataController.java:94)

(This is with the prima-core-libs 1.4.02 repackaged in current master.)
The error goes away when I add @type annotations for the regions.
Again, this strikes me as overly restrictive.

Allowing regions without a specified type and just displaying them as "undefined region" or something similar sounds like a good idea.
Thanks for the suggestion.

Added in d6cd3daf4d365aed58ea612eabc4bac7c06d620d and should now work for both import and export.
Imported TextRegions without a subtype will be shown as TextRegions in LAREX (which is now available for choosing in the sidebar) and assigning this tag to any segment will export it as a TextRegion without a subtype as well


Support for sdk 21

Please provide support for minsdk 21 except its absolutely needed to update to 24

i will make this change.

Any progress on this ?
@imranbaig1977
@imranbaigshortcut

Please let me what changes you want to do.
I will try to help 🙂

From: Hazhan Jalal @.>
Sent: 21 December 2023 11:44
To: imranbaigshortcut/android-qibla-finder @.>
Cc: Imran Baig @.>; Mention @.>
Subject: Re: [imranbaigshortcut/android-qibla-finder] Support for sdk 21 (Issue #1)
Any progress on this ?
@imranbaig1977https://github.com/imranbaig1977
@imranbaigshortcuthttps://github.com/imranbaigshortcut
—
Reply to this email directly, view it on GitHubhttps://github.com/imranbaigshortcut/android-qibla-finder/issues/1#issuecomment-1866035744, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACSF3MQXRVVR6SQVN2O3IEDYKQHIFAVCNFSM6AAAAAAQMQ5E22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRWGAZTKNZUGQ.
You are receiving this because you were mentioned.

Thanks a bunch kind sir.
Preferably supporting all the way down to sdk 21 (minSdk 21).
Didn't want to fork/add to my project on my on since it's a small change.

Also one addition question,
Is it possible to grab/get the calculated degree for qibla from provided Lon/Lat ? It's quite small and I wanted to grab the value and show it somewhere myself, couldn't see any function on how to do it.
There was getDegree() but it returns the current direction I am looking, not calculated degree for Qibla.


Getting 'PayPal API Error: 'Version error''

When trying to register transaction I get:
Paypal::Exception::APIError - PayPal API Error: 'Version error'

Full message says that version is not supported. I tried setting Paypal.api_version to latest and different values and it doesn't help.
This started happening suddenly yesterday. It was working fine few days ago.
full code of method
order = @order
    if(APP_CONFIG["paypal"]["sandbox"])
      Paypal.sandbox!
    end

    express_request = Paypal::Express::Request.new(
      :username   => APP_CONFIG["paypal"]["api_username"],
      :password   => APP_CONFIG["paypal"]["api_password"],
      :signature  => APP_CONFIG["paypal"]["api_signature"]
    )

    logger.info "==PPP Express::Request: #{express_request}"

    paypal_options = {
      no_shipping: true, # if you want to disable shipping information
      allow_note: false, # if you want to disable notes
      pay_on_paypal: true # if you don't plan on showing your own confirmation step
    }

    logger.info "==PPP paypal_options: #{paypal_options}"

    payment_request = Paypal::Payment::Request.new(
      :currency_code => "PLN",              # if nil, PayPal use USD as default
      :description   => order.pack.name,    # item description
      :quantity      => 1,                  # item quantity
      :amount        => order.total.round(2).to_f,
      :invoice_number => (order.id + 100000),
      :notify_url => APP_CONFIG["paypal"]["ipn_notify_url"]
    )

    response = express_request.setup(
      payment_request,
      "http://bookrage.org/paypal/success/#{order.return_token}",
      "http://bookrage.org/paypal/cancel/#{order.return_token}",
      paypal_options  # Optional
    )

    logger.info "==PPP response.redirect_uri: #{response.redirect_uri}"

    return response.redirect_uri

Still, example curl from paypal page works on sandbox event with my credentials
curl https://api-3t.sandbox.paypal.com/nvp \
>   -s \
>   --insecure \
>   -d USER=platfo_1255077030_biz_api1.gmail.com \
>   -d PWD=1255077037 \
>   -d SIGNATURE=Abg0gYcQyxQvnf2HDJkKtA-p6pqhA1k-KTYE0Gcy1diujFio4io5Vqjf \
>   -d METHOD=SetExpressCheckout \
>   -d VERSION=78 \
>   -d PAYMENTREQUEST_0_PAYMENTACTION=SALE \
>   -d PAYMENTREQUEST_0_AMT=19 \
>   -d PAYMENTREQUEST_0_CURRENCYCODE=USD \
>   -d cancelUrl=http://www.example.com/cancel.html \
>   -d returnUrl=http://www.example.com/success.html
TOKEN=EC%2d6VH883273N101092R&TIMESTAMP=2016%2d07%2d14T21%3a04%3a57Z&CORRELATIONID=c34496e55ed38&ACK=Success&VERSION=78&BUILD=000000%

Same problem here.

I think @meal or @ianfleeton seemed to fix it here:
https://github.com/ianfleeton/paypal-express/commit/cebd62f02966f74a8aa3ece5d1793be9327048a0
Maybe we can merge that back into the canonical version? @nov are you still maintaining this or is there a new canonical fork?

This was @meal's work - my fork contains two improvements, neither by me. A merge from @meal's would be better.

I can create PR for this but I'm not sure if @nov still maintains this repository.

There already are pending PR with this change...Looks like this got abandoned

That's a pity because this gem is very useful and i used it in three projects already!

What fork are you currently using guys?

I've started using my own fork as I need the changes I've pulled in so far, which include changes from more than one other fork.
I am working on a project that depends on this library for the next year. I'm happy to become a maintainer for the next year or so if it helps others, focusing on bug fixes / minor improvements rather than new features. I've not maintained a project before but first time for everything. Unless there are any other takers? @nov?

awesome @ianfleeton do that! we need somebody to take over. A quick paypal integration gem is quite useful and we can't let it die.
I tried to contact @nov multiple times on email, twitter and github, but no answer. Let's move on!

@nov what about creating an organization for the gem? Time for this useful child to fly away?
If @nov doesn't reply, we may well create the org and move on. @ianfleeton if you need some help, I may find some time here and there.

Excellent, I'll wait to see if anything happens by Sunday and if no news I'll start reviewing the current open issues and pull requests with a view to moving things forward. Any and all help welcome :)

@ianfleeton @dgilperez shall we? 👍

I've made a few commits and pulled in some others' changes into https://github.com/ianfleeton/paypal-express by making pull requests from their forks and merging them.
Fixed:

PayPal API version, including with refunds (thanks @meal @netjungle)
Travis build with ActiveSupport 5.x (thanks @ursm)
Phone number included (thanks @fny)

The next two items to look at:

Gem releases
Organization

Is it time to move the discussion over to ianfleeton/paypal-express?
Cheers!

if you guys want help and support from an organisation - AgileVentures is a charity that could help - we were just thinking about integrating paypal
Happy to provide a home for the project at https://github.com/AgileVentures/ if that's any help

I see that Paypal also has their own ruby gem https://github.com/paypal/PayPal-Ruby-SDK - is that any relation?

PayPal Express uses the NVP / SOAP APIs instead of the REST APIs provided by that library. I don't think they overlap, but I'm not 100%.

I encountered this same problem and it turns out that the issue was that, although the paypal-express gem hadn't changed, I had upgraded the rest-client gem from 1.8.2 to 2.0.0. The slight change between the versions is that they serialize querystring parameters slightly differently. Where 1.8.2 would emit:
&SUBJECT=&VERSION=0.88
2.0.0 emits:
&SUBJECT&VERSION=0.88
Although many servers understand this, seemingly Paypal's doesn't. (I'm guessing it sees one parameter named "SUBJECT&VERSION" with value "0.88" - and then complains that there's no VERSION in the request).
I have implemented a horrible workaround for now (evilly monkey-patching RestClient::Utils#encode_query_string). Although fixing to 1.8.2 of the rest-client gem works, too.

@ktopping have you tried using a later API version -- e.g., 204.0 to see if that helps? The fork over at  https://github.com/ianfleeton/paypal-express uses that. If you find the same problem with that fork I'd be interested to know. Also, this fork includes the required version parameter in many more places.
I have that running with rest-client 2.0.0 no problems, though I haven't dug in to see whether the SUBJECT param is or isn't set in my usage.

Quick solution: using the fork from Ian Fleeton
gem 'paypal-express', github: 'ianfleeton/paypal-express'

I've pulled into the above PR #98 from @ursm (thanks!) which hopefully addresses this problem by explicitly setting a blank string for the subject parameter if it's nil.

Thanks for the replies. I have it working at the moment but will try upgrading to ianfleeton's fork next time I rebundle.

Following @pastullo's suggestion worked for me. Thank you. Too bad that this repo doesn't seem to be receiving any attention from the creator anymore.

We just upgraded rest-client from 1.8.0 to 2.0.2 and started getting this "Version error". Changing to ianfleeton's fork as mentioned by @pastullo above fixed it. Thank you!

Hi! If you want not change of repository you can use monkey patching. This is the code:
File: config/initializers/paypal.rb
....

Paypal::NVP::Request.class_eval do
  def common_params
    {
      USER: self.username,
      PWD: self.password,
      SIGNATURE: self.signature,
      SUBJECT: self.subject,
      VERSION: self.version,
      version: self.version # This is necessary
    }
  end
end

A little bit late, but I hoppe help some one.
This solution was taking from ianfleeton/paypal-express repository, so thanks a lot ianfleeton


Restyle registration pages.

The registration pages — both the landing page and the follow through
page after receiving an email have been restyled to be more linear in
nature and centered using flex box.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

Looks like this fails the frontend test because you renamed some of the things they check for.

Thanks for working on this @brockwhittaker!  Aside from the test issue mentioned above, it'd be good to make the refactoring on the registration page more readable using more than 1 commit -- it's pretty hard to tell what you changed in the actual body of the page by reading it.  Thanks!
Otherwise, this looks great!

I pushed a few updates that separated commits and fixed the issues with
casper that were provoked by the last commits.
On Tue, Aug 23, 2016 at 11:15 PM, Tim Abbott<EMAIL_ADDRESS>wrote:

Thanks for working on this @brockwhittaker
https://github.com/brockwhittaker! Aside from the test issue mentioned
above, it'd be good to make the refactoring on the registration page more
readable using more than 1 commit -- it's pretty hard to tell what you
changed in the actual body of the page by reading it. Thanks!
Otherwise, this looks great!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/1693#issuecomment-241967531, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJ199-DeyQaCYRvn6rqMZf225Y2CLZICks5qi-FngaJpZM4Jri8M
.

Looks like it's failing the linter?

Linting error fixed. All linting & front-end tests passed.

@brockwhittaker thanks for working on this!    Check out the Zulip coding style guidelines here for more details on this model: https://zulip.readthedocs.org/en/latest/code-style.html#version-control
I merged this as d8aed0227a7d795e9ee1070adfaf06ae7f4f3447 (and the 3 commits before it).


Upgrade of refine attenuation to have better reports and work with UHF

This is the upgrade of Refine attenuation for L & UHF bands done by Mpendulo Sibiya
The Refine attenuation code measures the standard deviation of the ADC samples is measured for both the UHF and L-band and a threshold of 12 is used. This is done to ensure there is enough timing information to maintain the receiver sampling rate. The voltage and voltage range thresholds are are measured from the ADC samples and a suitable range is 190 and 190+ 20 for L-band, and √2 x 𝐿𝑏𝑎𝑛𝑑 and x for the UHF-band. Given (𝑣𝑜𝑙𝑡𝑎𝑔𝑒) √2 𝐿𝑏𝑎𝑛𝑑(𝑣𝑜𝑙𝑡𝑎𝑔𝑒 𝑟𝑎𝑛𝑔𝑒) the threshold, if the antenna’s standard deviation and voltage are not within the acceptable range, the algorithm changes or updates the attenuation levels until the values lie within the appropriate range. The end of the refine attenuation process is two results emails sent to the operators. The first email is titled “Summary: Changing attenuation”, this email summarizes the entire observation and is important to be seen by the operators as it highlights the antennas that have changed, and should be updated in the config. The second email is titled “Details: Changing attenuation”, this email contains all the debug information, it highlights all the detailed changes or updates made during the observation and is useful for a deeper understanding of what happened during the observation.
Refine-attenuation:Upgrade-Documentation.pdf

There is typo in the documentation (pdf) under "Attenuation change update conditions"
"If the voltage is too low we reduce the attenuation by 1dB and too high it is reduced by 1dB."
This should read
"If the voltage is too low we reduce the attenuation by 1dB and too high it is increased by 1dB."

Please could you add<EMAIL_ADDRESS>to the emails.
The new report looks good and it it is great that this works under UHF.


Fix over-writing fmin race in fem/tmop/tmop_pa_da3.cpp [tmop-da3-race-fix]

Fixes a race in the fmin reduction, avoiding y & z threads to overwrite the result.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Merged in next for testing...