Wemo fails discovery

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.25.2
Python release (python3 --version):
Python 3.4.2
Component/platform:
Raspberry Pi / Raspbian
Description of problem:
No Wemo devices are discovered correctly and no information is presented.
Expected:
Discovery and Information from Wemo Devices
Problem-relevant configuration.yaml entries and steps to reproduce:
wemo:

Upgraded to latest homeassistant
Removed pywemo and wemo: from config. Re-added it and problem persist.

Traceback (if applicable):
Repeating:
16-08-11 15:36:49 pywemo.subscribe: Resubscribe for <WeMo Insight "Livingroom Camera">
16-08-11 15:36:49 pywemo.subscribe: Resubscribe error for <WeMo Insight "Livingroom Camera">, will retry in 60s
16-08-11 15:36:49 pywemo.ouimeaux_device: Reconnected to wemo at <IP_ADDRESS> on port 49153

Additional info:

I suspect the issue is that HA doesn't support the Wemo camera. Not sure the pywemo library does either.
Looks like some of the discovery and subscription code is working is finding the device - but the higher level code isn't.
Do you have other Wemo devices? Are they being found ok?

It's not a camera, that's just what I called my switch. All three of my switches give this message. It was working fine before upgrading to 25.2.

Can you post the pywemo discovery traces at the start of the run. The section you've posted is probably later when the pywemo code is trying to refresh the subscription to devices it has discovered. It doesn't look good - but the earlier traces might give more useful info.
What version did you upgrade from (ie what version was working)?
Did you upgrade Wemo devices, or change anything else?

The same thing is happening for me with static wemo devices.
INFO:pywemo.subscribe:Resubscribe for <WeMo Motion "Front Desk Staff Side">
WARNING:pywemo.subscribe:Resubscribe error for <WeMo Motion "Front Desk Staff Side">, will retry in 60s

0.24.0 was working, and I upgraded to 0.25.2, which is where the problems started.

That could just mean pywemo is having trouble talking to your Wemo device when trying to refresh it's subscription. I get those from time to time - and it doesn't matter as long as the retry works.
@bartonhodges are your devices working?
Don't think anything changed in the Wemo code, so may be something else changed in HA that's affecting pywemo.

I upgraded from 24.1 or 2 don't remember but I tried downgrading and it didn't help. Here the beginning of the discovery.
6-08-12 18:58:25 homeassistant.components.wemo: Scanning for WeMo devices.
16-08-12 18:58:27 pywemo.ssdp: Found malformed XML at http://<IP_ADDRESS>:40001: status=ok
16-08-12 18:58:31 homeassistant.components.wemo: Adding wemo at <IP_ADDRESS>:49153
16-08-12 18:58:31 homeassistant.core: Bus:Handling <Event platform_discovered[L]: service=belkin_wemo, discovered=('Ari Light', 'Socket', 'http://<IP_ADDRESS>:49153/setup.xml', 'EC1A59ECEFD0', '221334K0101B8A')>
16-08-12 18:58:32 homeassistant.components.wemo: Adding wemo at <IP_ADDRESS>:49153
16-08-12 18:58:32 homeassistant.core: Bus:Handling <Event platform_discovered[L]: service=belkin_wemo, discovered=('Bedroom Camera', 'Socket', 'http://<IP_ADDRESS>:49153/setup.xml', 'EC1A59ECF288', '221334K0101C38')>
16-08-12 18:58:32 homeassistant.components.wemo: Adding wemo at <IP_ADDRESS>:49153
16-08-12 18:58:32 homeassistant.core: Bus:Handling <Event platform_discovered[L]: service=belkin_wemo, discovered=('Livingroom Camera', 'Insight', 'http://<IP_ADDRESS>:49153/setup.xml', '14918224413E', '231615K1200DDE')>
16-08-12 18:58:32 homeassistant.core: Bus:Handling <Event component_loaded[L]: component=wemo>
16-08-12 18:58:32 homeassistant.core: Bus:Handling <Event platform_discovered[L]: platform=wemo, service=load_platform.switch, discovered=('Ari Light', 'Socket', 'http://<IP_ADDRESS>:49153/setup.xml', 'EC1A59ECEFD0', '221334K0101B8A')>
16-08-12 18:58:32 homeassistant.core: Bus:Handling <Event platform_discovered[L]: platform=wemo, service=load_platform.switch, discovered=('Bedroom Camera', 'Socket', 'http://<IP_ADDRESS>:49153/setup.xml', 'EC1A59ECF288', '221334K0101C38')>
16-08-12 18:58:32 homeassistant.core: Bus:Handling <Event platform_discovered[L]: platform=wemo, service=load_platform.switch, discovered=('Livingroom Camera', 'Insight', 'http://<IP_ADDRESS>:49153/setup.xml', '14918224413E', '231615K1200DDE')>
16-08-12 18:58:32 homeassistant.loader: Loaded switch.wemo from homeassistant.components.switch.wemo
16-08-12 18:58:32 homeassistant.loader: Loaded switch.wemo from homeassistant.components.switch.wemo
16-08-12 18:58:32 homeassistant.loader: Loaded switch.wemo from homeassistant.components.switch.wemo
16-08-12 18:58:33 pywemo.subscribe: Subscribing to events from <WeMo Switch "Bedroom Camera">
16-08-12 18:58:33 pywemo.subscribe: Resubscribe for <WeMo Switch "Bedroom Camera">
16-08-12 18:58:33 pywemo.subscribe: Resubscribe error for <WeMo Switch "Bedroom Camera">, will retry in 60s
16-08-12 18:58:34 pywemo.subscribe: Subscribing to events from <WeMo Switch "Ari Light">
16-08-12 18:58:34 pywemo.subscribe: Resubscribe for <WeMo Switch "Ari Light">
16-08-12 18:58:34 pywemo.subscribe: Resubscribe error for <WeMo Switch "Ari Light">, will retry in 60s
16-08-12 18:58:34 pywemo.subscribe: Subscribing to events from <WeMo Insight "Livingroom Camera">
16-08-12 18:58:34 pywemo.subscribe: Resubscribe for <WeMo Insight "Livingroom Camera">
16-08-12 18:58:34 pywemo.subscribe: Resubscribe error for <WeMo Insight "Livingroom Camera">, will retry in 60s

The retry never works.  It just continues to try to Resubscribe every 60s and gets an error.

Thanks that looks interesting. Won't be able to look until early next week - but will investigate

Thanks!  In the mean time, could you lead me to instructions on how to downgrade?

Downgrading didn't help but you can do: pip3 install homeassistant==24.0

Just checked I'm running 25.2 - and it's working (although I don't use discovery).
Also odd that downgrading doesn't fix it.
Are you both running on a Pi (just trying to think what else it could be).

I'm on a PI (fully updated) and all switches are on WeMo_WW_2.00.10626 firmware (if that matters).
I'm leaning towards a fresh install since I've been using hass for sometime now and not sure if something broke along the way.

I'm on CentOS 6 and CentOS 7, both fully updated.  And all WeMos have the latest firmware too.
My CentOS 7 was freshly installed today, and nothing has worked out of the box with the latest HA.  My CentOS 6 worked perfectly until I upgraded HASS.

It appears the problem may be requests-2.10.0
pip install requests==2.10.0 seems to fix it

I can confirm requests 2.10 fixes it. Thanks!

Great detective work - thanks. Sounds like pywemo doesn't work with the latest requests. Will take a look next week.

It appears that there's still something wrong.  I had to downgrade to these versions to get the WeMo motion sensor to work reliably:
homeassistant 0.24.1
pywemo 0.4.3
requests 2.10

+1 here.
I've downgraded to request == 2.10 and it fixed it.

Still getting this after updating requests, pywemo, and homeassistant to the latest versions.
16-08-14 13:55:42 pywemo.subscribe: Resubscribe error for <WeMo LightSwitch "Master Bathroom Light">, will retry in 60s

The latest pywemo traces the text of the requests exception - so please check you're running the latest version and post the full error.

Also are you running dev?

0.26.2 has been released with this fix included.


Add point update callback function

Add a callback function that can be called when the point value is updated. Add the following two attributes to the Point class:
update_func and update_func_arg. If the the update_func attribute is set, the update_func is called with the model and update_func_arg when the point value is updated.
update_func(model, update_func_arg)
The callback function should be used for an indication to be provided to another module and not be used for detailed processing.

Expanded to create a hook for read and a hook for writing a point with read_func() and write_func() routines. This is experimental functionality that may be updated in the future.


JAR path validation added

enhancement
minor

GAP runtime should be touched not tooling around / GAP build.

closing as discontinued


Add ttrt whls release to packages in tt-mlir

not allowed to publish this package yet. Need to wait for monorepo. Closing


Moving codecommit (3),codedeploy (3),codepipeline (2),codestarconnections (2),codestarnotifications (1) resources to v1beta1 version

Moving 3 resources in the codecommit group:

[ ] aws_codecommit_approval_rule_template_association
[ ] aws_codecommit_repository
[ ] aws_codecommit_trigger
[ ] aws_codecommit_approval_rule_template

Moving 3 resources in the codedeploy group:

[ ] aws_codedeploy_app
[ ] aws_codedeploy_deployment_config
[ ] aws_codedeploy_deployment_group

Moving 2 resources in the codepipeline group:

[ ] aws_codepipeline
[ ] aws_codepipeline_webhook

Moving 2 resources in the codestarconnections group:

[ ] aws_codestarconnections_connection
[ ] aws_codestarconnections_host

Moving 1 resources in the codestarnotifications group:

[ ] aws_codestarnotifications_notification_rule

PR by @turkenf, configuring codecommit group: https://github.com/upbound/provider-aws/pull/91

codedeploy and codepipeline: https://github.com/upbound/provider-aws/pull/102


Improved error messaging for index signature parameters

Fixes https://github.com/Microsoft/TypeScript/issues/18992
Implements this suggestion specifically: https://github.com/Microsoft/TypeScript/issues/18992#issuecomment-335458531

Looks good overall, just one comment


Windows install error: requirements file copy failed

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
10GB
What happened?
Installed using Window installer.
After it installs pip, I get the following error:
Successfully installed pip-22.3.1
***** Updated pip *****
The system cannot find the path specified.
----- requirements file copy failed -----
Press any key to continue . . .

Seems to be coming from this part of the install.bat file:
set err_msg=----- requirements file copy failed -----
copy installer\py3.10-windows-x86_64-cuda-reqs.txt requirements.txt
if %errorlevel% neq 0 goto err_exit

I don't have an "installer" folder, only "binary_installer" folder where that file resides.
I will change this in the bat file, or change the folder name from binary_installer to installer, run it again, and update this case.
Screenshots
No response
Additional context
No response
Contact Details
<EMAIL_ADDRESS>

UPDATE:
Installed, but little error at end:
***** Finished downloading models *****
***** Installing invoke.bat ******
The system cannot find the file specified.
All done! Execute the file invoke.bat in this directory to start InvokeAI
Press any key to continue . . .

Had to manually copy and rename invoke.bat to root folder.
The issue now is that it's showing me the HTML code instead of the GUI:

UPDATE:
I noticed that invoke.bat was referring to a "python scripts"folder that didn't exist:
.venv\Scripts\python scripts\invoke.py --web
But even after fixing that by changing it to:
.venv\Scripts\invoke.py --web
I still have the same issue.

I too have the requirement file copy failed error. The strange thing is that yesterday it was working (the installation), while today (I had to re-do it, long story) it doesn't work.. Edit: I "solved" using another installer: "invokeAi-src-installer-2.2.3-windows.zip" (you can find it here: https://invoke-ai.github.io/InvokeAI/installation/INSTALL_SOURCE/#walk-through and also under "assets" here at the main page https://github.com/invoke-ai/InvokeAI/releases/tag/v2.1.3p1)

Ok, so this installation went smooth with no errors. However, when running the invoke.bat, the http://<IP_ADDRESS>:9090/ page gives me the same HTML instead of the GUI.


remove old deprecated properties again

This is #72 again. It was reverted in #74 because CLI wanted to hold off, but it has been two months so probably enough time has passed.

Tracking back through the history here. I couldn't find our conversation about these dates... So here's a quick recap.
These types were deprecated in 18fc152, which was added to CLI in phylum-dev/cli@b317f34 and included in the CLI v4.8.0 release on 2023-04-04.


Add link to canonical_url in column actions for files

Hi! It's tiny enhachment for usability.

/cc @FinalAngel @lory87

@1vank1n would you provide a quick screenshot on what you want to achieve?

@1vank1n and/or @lory87 can you prepare this for merging?

@FinalAngel of course:

Advantage: get canonical url at file listing.

LGTM @mkoistinen

@1vank1n would you rebase this on current develop to fix conflicts?

@yakky no problem! Done!

@1vank1n thanks. There are still conflict markers in the patch. Could you check those?

@yakky hmm... i have not see conflict... "All checks have passed". Where's to find conflict?

@1vank1n have a look at the diff here on github. There are conflicts on directory_table.html and _navigator.scss

@yakky fixed. Now (in new version) there is icon download. Maybe in new version of django-filer my icon canonical url are unnecessary.

@1vank1n thanks!


Graceful Quit

Add in one additional trap to handle graceful quitting.

Thanks for the pull request.  The only challenge with this is that the backends are all blocking, so if there are no jobs in the queue, #work will never return and the worker will never shut down.
It was an intentional design decision to make qu abort immediately instead of finishing the current job. I'm not opposed to making that optional, but we'll have to think through how to make it work properly.


Move ZDNS to using ZFlags instead of Cobra

Description
ZFlags should give us more flexibility (we can now use short form flags (-t!)) and make ZDNS act more similar to ZGrab. Additionally, it should make having multiple modules as requested #234 possible, similar to how it's done in ZGrab.
New --help
$ ./zdns -h
Usage:
  zdns [options] <command>

ZDNS is a library and CLI tool for making very fast DNS requests. It's built upon
https://github.com/zmap/dns (and in turn https://github.com/miekg/dns) for constructing
and parsing raw DNS packets.
ZDNS also includes its own recursive resolution and a cache to further optimize performance.

Application Options:
      --4                      utilize IPv4 query transport only, incompatible with --6
      --6                      utilize IPv6 query transport only, incompatible with --4
      --alexa                  is input file from Alexa Top Million download
      --all-nameservers        Perform the lookup via all the nameservers for the domain.
      --blacklist-file=        blacklist file for servers to exclude from lookups
      --cache-size=            how many items can be stored in internal recursive cache (default: 10000)
      --checking-disabled      Sends DNS packets with the CD bit set
      --class=                 DNS class to query. Options: INET, CSNET, CHAOS, HESIOD, NONE, ANY. (default: INET)
      --client-subnet=         Client subnet in CIDR format for EDNS0.
      --conf-file=             config file for DNS servers (default: /etc/resolv.conf)
      --dnssec                 Requests DNSSEC records by setting the DNSSEC OK (DO) bit
      --go-processes=          number of OS processes (GOMAXPROCS by default) (default: 0)
      --include-fields=        Comma separated list of fields to additionally output beyond result verbosity. Options:
                               class, protocol, ttl, resolver, flags
  -f, --input-file=            names to read, defaults to stdin (default: -)
      --iteration-timeout=     timeout for a single iterative step in an iterative query, in seconds. Only applicable with
                               --iterative (default: 4)
      --iterative              Perform own iteration instead of relying on recursive resolver
      --local-addr=            comma-delimited list of local addresses to use, serve as the source IP for outbound queries
      --local-interface=       local interface to use
      --log-file=              where should JSON logs be saved, defaults to stderr (default: -)
      --max-depth=             how deep should we recurse when performing iterative lookups (default: 10)
      --metadata-file=         where should JSON metadata be saved, defaults to no metadata output. Use '-' for stderr.
      --metadata-passthrough   if input records have the form 'name,METADATA', METADATA will be propagated to the output
      --name-server-mode       Treats input as nameservers to query with a static query rather than queries to send to a
                               static name server
      --name-servers=          List of DNS servers to use. Can be passed as comma-delimited string or via @/path/to/file. If
                               no port is specified, defaults to 53.
      --nanoseconds            Use nanosecond resolution timestamps in output
      --no-recycle-sockets     do not create long-lived unbound UDP socket for each thread at launch and reuse for all (UDP)
                               queries
      --no-follow-cnames       do not follow CNAMEs/DNAMEs in the lookup process
      --nsid                   Request NSID.
      --override-name=         name overrides all passed in names. Commonly used with --name-server-mode.
      --prefer-ipv4-iteration  Prefer IPv4/A record lookups during iterative resolution. Ignored unless used with both IPv4
                               and IPv6 query transport
      --prefer-ipv6-iteration  Prefer IPv6/AAAA record lookups during iterative resolution. Ignored unless used with both
                               IPv4 and IPv6 query transport
      --prefix=                name to be prepended to what's passed in (e.g., www.)
  -o, --output-file=           where should JSON output be saved, defaults to stdout (default: -)
      --result-verbosity=      Sets verbosity of each output record.  Specifically, alookup acts similar to nslookup and will follow CNAME records.

Application Options:
      --4                      utilize IPv4 query transport only, incompatible with --6
      --6                      utilize IPv6 query transport only, incompatible with --4
      --alexa                  is input file from Alexa Top Million download
      --all-nameservers        Perform the lookup via all the nameservers for the domain.
      --blacklist-file=        blacklist file for servers to exclude from lookups
      --cache-size=            how many items can be stored in internal recursive cache (default: 10000)
      --checking-disabled      Sends DNS packets with the CD bit set
      --class=                 DNS class to query. Options: INET, CSNET, CHAOS, HESIOD, NONE, ANY. (default: INET)
      --client-subnet=         Client subnet in CIDR format for EDNS0.
      --conf-file=             config file for DNS servers (default: /etc/resolv.conf)
      --dnssec                 Requests DNSSEC records by setting the DNSSEC OK (DO) bit
      --go-processes=          number of OS processes (GOMAXPROCS by default) (default: 0)
      --include-fields=        Comma separated list of fields to additionally output beyond result verbosity. Options: class, protocol, ttl, resolver, flags
  -f, --input-file=            names to read, defaults to stdin (default: -)
      --iteration-timeout=     timeout for a single iterative step in an iterative query, in seconds. Only applicable with --iterative (default: 4)
      --iterative              Perform own iteration instead of relying on recursive resolver
      --local-addr=            comma-delimited list of local addresses to use, serve as the source IP for outbound queries
      --local-interface=       local interface to use
      --log-file=              where should JSON logs be saved, defaults to stderr (default: -)
      --max-depth=             how deep should we recurse when performing iterative lookups (default: 10)
      --metadata-file=         where should JSON metadata be saved, defaults to no metadata output. Use '-' for stderr.
      --metadata-passthrough   if input records have the form 'name,METADATA', METADATA will be propagated to the output
      --name-server-mode       Treats input as nameservers to query with a static query rather than queries to send to a static name server
      --name-servers=          List of DNS servers to use. Can be passed as comma-delimited string or via @/path/to/file. If no port is specified, defaults to 53.
      --nanoseconds            Use nanosecond resolution timestamps in output
      --no-recycle-sockets     do not create long-lived unbound UDP socket for each thread at launch and reuse for all (UDP) queries
      --no-follow-cnames       do not follow CNAMEs/DNAMEs in the lookup process
      --nsid                   Request NSID.
      --override-name=         name overrides all passed in names. Commonly used with --name-server-mode.
      --prefer-ipv4-iteration  Prefer IPv4/A record lookups during iterative resolution. Ignored unless used with both IPv4 and IPv6 query transport
      --prefer-ipv6-iteration  Prefer IPv6/AAAA record lookups during iterative resolution. Ignored unless used with both IPv4 and IPv6 query transport
      --prefix=                name to be prepended to what's passed in (e.g., www.)
  -o, --output-file=           where should JSON output be saved, defaults to stdout (default: -)
      --result-verbosity=      Sets verbosity of each output record. Options: short, normal, long, trace (default: normal)
      --retries=               how many times should zdns retry query if timeout or temporary failure (default: 1)
      --tcp-only               Only perform lookups over TCP
  -t, --threads=               number of lightweight go threads (default: 1000)
      --timeout=               timeout for resolving a individual name, in seconds (default: 15)
      --udp-only               Only perform lookups over UDP
      --verbosity=             log verbosity: 1 (lowest)--5 (highest) (default: 3)

Help Options:
  -h, --help                   Show this help message

[ALOOKUP command options]
          --ipv4-lookup        perform A lookups for each server
          --ipv6-lookup        perform AAAA lookups for each server

Testing
Normal Usage
$ echo "cloudflare.com" | ./zdns A
{"data":{"additionals":[{"flags":"","type":"EDNS0","udpsize":512,"version":0}],"answers":[{"answer":"<IP_ADDRESS>","class":"IN","name":"cloudflare.com","ttl":164,"type":"A"},{"answer":"<IP_ADDRESS>","class":"IN","name":"cloudflare.com","ttl":164,"type":"A"}],"protocol":"udp","resolver":"[2603:6013:9d00:3302::1]:53"},"duration":0.04202225,"name":"cloudflare.com","status":"NOERROR","timestamp":"2024-08-20T16:13:44-04:00"}

Using a flag
$ echo "cloudflare.com" | ./zdns A --verbosity=5
INFO[0000] No iteration IP preference specified, defaulting to IPv4 preferred. See --prefer-ipv4-iteration and --prefer-ipv6-iteration for more info
INFO[0000] using local addresses: [<IP_ADDRESS> 2603:6013:9d00:3302:c460:464e:f5c0:9930]
INFO[0000] for non-iterative lookups, using external nameservers: <IP_ADDRESS>:53, [2603:6013:9d00:3302::1]:53
INFO[0000] for iterative lookups, using nameservers: <IP_ADDRESS>:53, [2603:6013:9d00:3302::1]:53
INFO[0000] no name server provided for external lookup, using  random external name server: [2603:6013:9d00:3302::1]:53
DEBU[0000] DEPTH 00:[MIEKG-IN: starting a C/DNAME following lookup for  cloudflare.com  ( 1 )]
DEBU[0000] DEPTH 01:    [MIEKG-IN: following external lookup for  cloudflare.com  ( 1 )]
DEBU[0000] DEPTH 01:    [****WIRE LOOKUP***  A   cloudflare.com   [2603:6013:9d00:3302::1]:53]
DEBU[0000] DEPTH 01:    [MIEKG-OUT: following external lookup for  cloudflare.com  ( 1 ) with  1  attempts: status:  NOERROR  , err:  <nil>]
{"data":{"additionals":[{"flags":"","type":"EDNS0","udpsize":4096,"version":0}],"answers":[{"answer":"<IP_ADDRESS>","class":"IN","name":"cloudflare.com","ttl":153,"type":"A"},{"answer":"<IP_ADDRESS>","class":"IN","name":"cloudflare.com","ttl":153,"type":"A"}],"protocol":"udp","resolver":"[2603:6013:9d00:3302::1]:53"},"duration":0.019543083,"name":"cloudflare.com","status":"NOERROR","timestamp":"2024-08-20T16:13:55-04:00"}

Using a special module that adds extra flags
$ echo "cloudflare.com" | ./zdns nslookup --ipv4-lookup
{"data":{"servers":[{"ipv4_addresses":["<IP_ADDRESS>","<IP_ADDRESS>"],"name":"ns6.cloudflare.com","ttl":86400,"type":"NS"},{"ipv4_addresses":["<IP_ADDRESS>","<IP_ADDRESS>"],"name":"ns7.cloudflare.com","ttl":86400,"type":"NS"},{"ipv4_addresses":["<IP_ADDRESS>","<IP_ADDRESS>"],"name":"ns3.cloudflare.com","ttl":86400,"type":"NS"},{"ipv4_addresses":["<IP_ADDRESS>","<IP_ADDRESS>"],"name":"ns4.cloudflare.com","ttl":86400,"type":"NS"},{"ipv4_addresses":["<IP_ADDRESS>","<IP_ADDRESS>"],"name":"ns5.cloudflare.com","ttl":86400,"type":"NS"}]},"duration":0.231573292,"name":"cloudflare.com","status":"NOERROR","timestamp":"2024-08-20T16:15:29-04:00"}

~/zdns on  phillip/zflags-cli! ⌚ 16:15:29
$ echo "cloudflare.com" | ./zdns nslookup --ipv6-lookup
{"data":{"servers":[{"ipv6_addresses":["2400:cb00:2049:1::a29f:209","2400:cb00:2049:1::a29f:937"],"name":"ns5.cloudflare.com","ttl":86395,"type":"NS"},{"ipv6_addresses":["2400:cb00:2049:1::a29f:506","2400:cb00:2049:1::a29f:30b"],"name":"ns6.cloudflare.com","ttl":86395,"type":"NS"},{"ipv6_addresses":["2400:cb00:2049:1::a29f:408","2400:cb00:2049:1::a29f:606"],"name":"ns7.cloudflare.com","ttl":86395,"type":"NS"},{"ipv6_addresses":["2400:cb00:2049:1::a29f:7e2","2400:cb00:2049:1::a29f:21"],"name":"ns3.cloudflare.com","ttl":86395,"type":"NS"},{"ipv6_addresses":["2400:cb00:2049:1::a29f:837","2400:cb00:2049:1::a29f:121"],"name":"ns4.cloudflare.com","ttl":86395,"type":"NS"}]},"duration":0.331910166,"name":"cloudflare.com","status":"NOERROR","timestamp":"2024-08-20T16:15:34-04:00"}

Noticed I need to add -v, --version support. I'll do that and then open it for review.


Unable to find deleteById method

I'm applying the mongoose-delete-ts plugin globally. Any thoughts?
Error message:
Property 'deleteById' does not exist on type 'Model<SubmissionDocument, {}, {}, {}, Document<unknown, {}, SubmissionDocument> & Submission & Document<unknown, any, any> & Required<...>, any> & DeletedMethods'.ts(2339)
import { Model } from 'mongoose';
import { InjectModel } from '@nestjs/mongoose';
import { BadRequestException, Injectable } from '@nestjs/common';
import { DeletedMethods } from 'mongoose-delete-ts';
import { Submission, SubmissionDocument } from './schemas/submission.schema';
import { CreateSubmissionInput, DeleteSubmissionOutput, SubmissionOutput } from './dto';

@Injectable()
export class SubmissionsService {
  constructor(
    @InjectModel(Submission.name)
    private SubmissionModel: Model<SubmissionDocument> & DeletedMethods,
  ) { }

  async remove(id: string): Promise<DeleteSubmissionOutput> {
    try {
      const submission = (await this.SubmissionModel.deleteById(id));
      console.log(submission, id)
      return this.toDeleteSubmissionOutput(submission)
    } catch (err) {
      throw new BadRequestException(err.message);
    }
  }

  private toDeleteSubmissionOutput(submission: any): DeleteSubmissionOutput {
    return {
      ...submission
    };
  }
}

It looks like you are using the wrong type reference. DeletedMethods are the instance methods on the document (submission.delete()), not the static methods. To use the static methods you need to import DeletedStaticMethods. See example in the README
import { DeletedStaticMethods, DeletedMethods } from 'mongoose-delete-ts';
...
private SubmissionModel: Model<SubmissionDocument, {}, DeletedMethods> & DeletedStaticMethods,


EKF: Enable operation with arbitrary External Vision reference frame

This PR adds a parameter activated function that uses the navigation to body frame quaternion from the external vision system to estimate the rotation from the EKF to the EV reference frame. This is then used to rotate EV position measurements into the EKF NED navigation frame before they are used.
It has been created in response to requirements identified in https://github.com/PX4/Firmware/issues/7408.
This function is enabled by setting bit position 6 in EKF2_AID_MASK to true. If bit position 4 is also set to true (EKF is using the EV system's yaw angle) then the compensation is disabled because the EV system's navigation frame becomes the reference.
TESTING
Testing has been performed using SITL with the following branch to enable the EV data to be rotated into a different frame of reference.
https://github.com/priseborough/Firmware/tree/pr-ekfExtVisQuat
See the following log produced running make posix_sitl_default gazebo_iris.
https://review.px4.io/plot_app?log=b17ec2dd-f150-4b47-9534-e9ff96106561
Position innovations were small and the EV system alignment was correctly estimated as 1 radian of yaw.

The test was successfully repeated with EKF2_AID_MASK = 73 to enable GPS fusion:
https://review.px4.io/plot_app?log=ef6fac87-b038-49fe-bc9c-fe07a783473c
Position innovations were small and the EV system alignment was correctly estimated as 1 radian of yaw.

The position hold with GPS fusion (EKF2_AID_MASK = 73) was more as precise than with using EV data (EKF2_AID_MASK = 72). This may be due to the loss of velocity observations and/or the use of differential position to fuse EV data when it is not in a NED frame.

Forcing the EKF to use incremental position fusion solved the problem with the innovation divergence, but at the expense of additional drift.

Looks good to me, code-wise.

Investigate options enabling use of absolute position fusion when the EV frame is not NED.

Do you have any new ideas on this? I have been thinking about it as well, and I don't see a good way to do it without introducing drift of delta fusion (as opposed to absolute).

Sorry, I was on vacation... Not sure I quite get this:

Investigate options enabling use of absolute position fusion when the EV frame is not NED.

Isn't this what this PR is about? ->

This is a placeholder for development of a capability to operate the EKF with external navigation systems that use a different frame of reference to NED.

@priseborough Not sure how you tested this because the referenced log uses NED.

I hacked a rotation of the EV data in ekf2_main

I've rebased and updated the quaternion order. Testing to follow.

@ChristophTobler Is there a way I can reproduce you simulation test? The old log will no longer replay due to the number of uORB message changes..

@priseborough Yes. Just use the normal simulation make posix_sitl_default gazebo_iris and change the parameter EKF2_AID_MASK to use external vision.

I'm not happy with the drift performance when using the delta position observation model. Further tuning is required.

It looks like the overshoot and drift are caused by the observation variance being too high for what is essentially a relative measurement and the default value of EKF2_EV_DELAY of 175 msec being much larger than SITL is achieving. Reducing  EKF2_EV_DELAY to 10 and using a relative position observation error of 0.01m helped significantly.

Awesome upgrade! @priseborough
How do I test this (GPS+OF+EV fusion using delta position) in real flight?
I am thinking to upload https://github.com/priseborough/Firmware/tree/pr-ekfExtVisQuat to my pixracer and stream the vision pose through vision_pose/pose from mavros. Is this sensible?
Kind Regards,
Chang

@Changliu52 Enable use of OF and EV data via the EKF2_AID_MASK parameter. In theory using mavros should work, but there is work for you to do on the firmware side. Data received needs to be time stamped when received by the firmware and any delay relative to the time stamp compensated using the EKF2_EV_DELAY parameter.  Data needs to be published to the vehicle_vision_position and vehicle_vision_attitude topics.

I've rebased on ecl. This required resolving a number of conflicts due to changes to prior changes to the fusion control and reset logic, so I will need to repeat the SITL testing using https://github.com/priseborough/Firmware/tree/pr-ekfExtVisQuat

SITL test log here: https://logs.px4.io/plot_app?log=4e5ec8ed-8691-488e-a15a-12d8c49c7115

What is the status here?

@mhkabir  Your review status is still pending.

Looks good in general. I think we can merge this now, and then iterate further on the comment about absolute vision fusion I raised.
My idea would be to switch to absolute vision position fusion whenever we are not aiding with GPS even when the vision frame is not NED. This would also require tracking the position difference between the NED origin and the vision origin (in addition to the rotation this PR tracks.)

@priseborough I agree with @mhkabir. If you can verify that the redundant part can be removed (and actually remove it), this can go in.:+1:

@priseborough @mhkabir Can we not wait for the EV to NED frame (_ev_rot_mat) to converge and then fuse the absolute position?

@ChristophTobler Yes for operation without GPS, we could do that with a small modification.

Let's do that in the next iteration over the vision interface. I'm putting together a 250 racer with VIO and GPS, so it should be easy to get datasets and fly around to test new code.


[Latest] Docker container stays in "starting" state

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
[Latest] Docker container stays in "starting" state eventually changing to "unhealthy" state after recent update on Feb 13th 2023 - Container however is up and running and accessable via web gui

👟 Reproduction steps
Recreated / pulled image again and it replicates itself.
👀 Expected behavior
Recent update as of earlier this morning has caused the issue to occur.
😓 Actual Behavior
docker image update created issue at hand.
🐻 Uptime-Kuma Version
Version: 1.20.0
💻 Operating System and Arch
Ubuntu 22.04.1 LTS Server
🌐 Browser
Chrome Version 110.0.5481.97 (Official Build) (64-bit) & Firefox Version 109.0.1 (64-bit)
🐋 Docker Version
Docker version 20.10.14, build a224086
🟩 NodeJS Version
NodeJS Version 16
📝 Relevant log output
Container Logs:

==> Performing startup jobs and maintenance tasks
==> Starting application with user 0 group 0
Welcome to Uptime Kuma
Your Node.js version: 16
2023-02-13T23:31:46Z [SERVER] INFO: Welcome to Uptime Kuma
2023-02-13T23:31:46Z [SERVER] INFO: Node Env: production
2023-02-13T23:31:46Z [SERVER] INFO: Importing Node libraries
2023-02-13T23:31:46Z [SERVER] INFO: Importing 3rd-party libraries
2023-02-13T23:31:47Z [SERVER] INFO: Creating express and socket.io instance
2023-02-13T23:31:47Z [SERVER] INFO: Server Type: HTTP
2023-02-13T23:31:47Z [SERVER] INFO: Importing this project modules
2023-02-13T23:31:47Z [NOTIFICATION] INFO: Prepare Notification Providers
2023-02-13T23:31:47Z [SERVER] INFO: Version: 1.20.0
2023-02-13T23:31:48Z [DB] INFO: Data Dir: ./data/
2023-02-13T23:31:48Z [SERVER] INFO: Connecting to the Database
2023-02-13T23:31:48Z [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-02-13T23:31:48Z [DB] INFO: SQLite Version: 3.39.4
2023-02-13T23:31:48Z [SERVER] INFO: Connected
2023-02-13T23:31:48Z [DB] INFO: Your database version: 10
2023-02-13T23:31:48Z [DB] INFO: Latest database version: 10
2023-02-13T23:31:48Z [DB] INFO: Database patch not needed
2023-02-13T23:31:48Z [DB] INFO: Database Patch 2.0 Process
2023-02-13T23:31:48Z [SERVER] INFO: Load JWT secret from database.
2023-02-13T18:31:48-05:00 [SERVER] INFO: Adding route
2023-02-13T18:31:48-05:00 [SERVER] INFO: Adding socket handler
2023-02-13T18:31:48-05:00 [SERVER] INFO: Init the server
2023-02-13T18:31:48-05:00 [SERVER] INFO: Listening on 3001

Healthcheck Logs:

docker inspect --format "{{json .State.Health }}" uptime-kuma | jq
{
  "Status": "unhealthy",
  "FailingStreak": 130,
  "Log": [
    {
      "Start": "2023-02-13T20:44:35.345603713-05:00",
      "End": "2023-02-13T20:44:36.627348244-05:00",
      "ExitCode": 1,
      "Output": "Health Check ERROR\n"
    },
    {
      "Start": "2023-02-13T20:45:36.635919004-05:00",
      "End": "2023-02-13T20:45:37.90540917-05:00",
      "ExitCode": 1,
      "Output": "Health Check ERROR\n"
    },
    {
      "Start": "2023-02-13T20:46:37.915300586-05:00",
      "End": "2023-02-13T20:46:39.224146218-05:00",
      "ExitCode": 1,
      "Output": "Health Check ERROR\n"
    },
    {
      "Start": "2023-02-13T20:47:39.237531979-05:00",
      "End": "2023-02-13T20:47:40.599444254-05:00",
      "ExitCode": 1,
      "Output": "Health Check ERROR\n"
    },
    {
      "Start": "2023-02-13T20:48:40.607842167-05:00",
      "End": "2023-02-13T20:48:41.892513961-05:00",
      "ExitCode": 1,
      "Output": "Health Check ERROR\n"
    }
  ]
}

Is your server x86 or arm64?

Arm64

I suspected that it is a portainer bug, because it is still using the old healthcheck script, as ``Health Check ERROR` is coming from the old script.
But I will try to rebuild the debian image.

I just rebuilt the debian image too, you could try now.

It appears to be working properly again after recreating/puling the image again.
Do you still feel this is a Portainer glitch? If so i can log a ticket with them for the Portainer Business Edition.
If so - should i just reference the above statement of " it is still using the old healthcheck script, as ``Health Check ERROR` is coming from the old script. " Or is there something more specific i should refer to?

I think so. I can reproduce it.
If I directly create a container with louislam/uptime-kuma:1.20.0, the healthcheck script is correct. (extra/healthcheck) (no .js)

If I first create a container with louislam/uptime-kuma:1.18.0.

And then update to 1.20.0, it used the wrong healthcheck script (with .js)

You could also check your current healthcheck script by going into Inspect > Config > Healthcheck > Test.

Interesting it still reflects the healthcheck,js on my side with using the "latest" tag

Makes me wonder if it would be more prudent to just backup the monitors, prune the existing and redeploy from scratch entirely.

After pulling the image again, the container comes up.
However, the healthcheck is in my environment still the old, I guess... (healthcheck.js)

I just backed up my config from the interface, stopped the container, did a "docker system prune", redeployed in a different directory, and imported config . Upon double checking it now reports as just healthcheck. Took all of two mins.

@tweek11 - It was quicker for me :-) Just stopped & started the container and the healthcheck is now "extra/healthcheck".
I'm happy, that this issue was solved so quickly...

for me a simple repull and recreate of the image solved this too. thanks for all comments

Interesting it still reflects the healthcheck,js on my side with using the "latest" tag
Makes me wonder if it would be more prudent to just backup the monitors, prune the existing and redeploy from scratch entirely.

Yes, so that is why I think it is a Portainer bug.

If so i can log a ticket with them for the Portainer Business Edition.

I think you should do that, thanks.


[Important] The current website is about to enter maintenance mode to aid with v3 launch

TL;DR; At the end of Jan 2021, all tracks will enter v3 staging mode. Updates will no longer sync with the current live website, but instead sync with the staging website. The Io section of the v3 repo will be extracted and PR'd into this track (if appropriate). Further issues and information will follow over the coming weeks to prepare Io for the launch of v3.
Over the last 12 months, we've all been hard at work developing Exercism v3. Up until this point, all v3 tracks have been under development in a single repository - the v3 repository. As we get close to launch, it is time for us to explode that monorepo back into the normal track repos. Therefore, at the end of this month (January 2021), we will copy the v3 tracks contents from the v3 repository back to the corresponding track repositories.
As v3 tracks are structured differently than v2 tracks, the current (v2) website cannot work with v3 tracks. To prevent the v2 website from breaking, we'll disable syncing between track repositories and the website. This will effectively put v2 in maintenance mode, where any changes in the track repos won't show up on the website. This will then allow tracks to work on preparing for the Exercism v3 launch.
Where possible, we will script the changes needed to prepare tracks for v3. For any manual changes that need to be happening, we will create issues on the corresponding track repositories. We will be providing lots of extra information about this in the coming weeks.
We're really excited to enter the next phase of building Exercism v3, and to finally get it launched! 🙂

As of today, the website has entered maintenance mode.

As of today, the website has entered maintenance mode.

With Exercism v3 just being released, tracks are no longer in maintenance mode and are active again.
This means that changes made to this track will once again show on the website.
Thanks for being patient with us and enjoy Exercism v3!


Bump framework to 2.9.0 to get newer dependencies

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Fedora uki know issue, arm job network issue. I would say lets merge this!


fix(errors) better locations for errors involving operators

Improves some error messages for operators, adding location information. Addresses PR #622.

Coverage remained the same at 99.119% when pulling ba9357c34d5f8f6736f3412cd982e87a7f31d139 on jeromesimeon:js-release-0.8.6 into 1786e88e649c24aec81ec301d72f873b28d4e236 on accordproject:master.


Spring boot maven plugin build image error

I am trying to build spring boot build image with the builder as  builder-ubi-base and getting an error  "Failed to detect:detected order contains extensions that is not support by the creator", Execution failed with error code 22. Thanks

Hi, I am facing same error message when using this one in a kubernetes environment calling the creator manually.
We're based on this link.
This is working perfectly for the builders (builder-jammy-tiny, ...) but we see ERROR: failed to detect: detected order contains extensions which is not supported by the creator for this image.
Did you happen to find a solution?

Not yet , you are spot on  with the analysis   , the error is due to validation.  I do see  there  is a flag in  SB 3.4.x  milestone to handle that , hoping that would be resolve the issue , but I am not sure.
https://github.com/spring-projects/spring-boot/issues/41352


Running with Pytorch0.4

The current version of pretrainedmodels is supposed to work with pytorch 0.4.
Consider updating pretrainedmodels.


Output saucelabs test url if using wdio-sauce-service

Fix for https://github.com/webdriverio/wdio-sauce-service/issues/47
The error seems to occur because the check in reporter looks for config.host to be saucelabs.com, but wdio-sauce-service sets config.host to localhost at https://github.com/webdriverio/wdio-sauce-service/blob/master/lib/sauce-launch-service.js#L18
I can fix it there instead but I don't know the ramifications of that across all projects.

Done

Released as v0.1.4

@christian-bromann It seems after running npm update wdio-spec-reporter, I see this change in lib/reporter.js but not build/reporter.js.  Am I missing something?


proposal: flag: Add flag.File, flag.FileVar

It is very common to want to have a command line option that takes a file name, for example the name of a log file to create or an input to read (and this typically defaults to standard in). To achieve this in current versions of Go, one typically creates a flag.String and then checks whether the value is "" or "-" and if not opens *os.File.
I propose to add flag.File and flag.FileVar to the flag package. It will attempt to open the passed in file name at flag.Parse() time and on failure print an error message and exit.
If this proposal is accepted, I can create a CL.

It is unlikely that this proposal will be accepted, as the flag package isn't adding any more features (in Go1) (see #23013).

It should be possible to write such a flag in a third party package.  It shouldn't be necessary to add it to the flag package in the standard library.  So the first step might be to write that third party package and see how many places could use it.

If it typically defaults to standard input, why not assign the file to os.Stdin? I personally dont like the idea of opening files in the flags package because theres no elegant way I know of to close them with a defer.

One reason I see against adding this to the flag package is how subtle this type would be. All the existing types, such as String and Int, are immediately obvious.
However, when it comes to File, a number of questions come up. What should happen when it is given a directory? Would it always open files via os.Open? What if one needed other modes, such as opening a file for writing? And there's always the controlling of how and when Close is called, as @as mentioned.
Doing this via a string flag and controlling all these aspects in a few lines of code seems to me like an approach that already works now. Writing a library that would let you control all these aspects is possible, but its API would be much heavier than that of the existing package.


How to compile sqlpp11?  mingw32-make error: ld.exe cannot find lib Permission denid. collect2.exe error ld returned 1 exit status.

libsqlite3.a and libsqlite3.dll.a is installed to “D:\Qt\5.15.2\mingw81_32\lib”.
There's nothing I can do about it，please !

Good news:
You don´t need to compile sqlpp11, because it is a header only library.
What fails here is the compilation of a test. That's certainly not perfect, but does not have to stop you from using the library.
Thus, you could install the library without building tests and then start using the header files from the library and (most likely) header files you generate via scripts/ddl2cpp from your table definitions.
However:
You might still run into linker errors. Personally, I don't have any recent experience with mingw32 (I last used it about 20 years ago). So I won't be able to help you with that. But the log you show here, does not seem to have anything to do with sqlpp11 in particular. That seems to be a problem with your setup.
A quick search for mingw81_32 and permission denied turned up these links for instance.
https://stackoverflow.com/questions/59888370/mingw-compiler-denying-access-to-files
https://geekthis.net/post/mingw-fix-permission-denied-ld-and-error/
Maybe it will point you in the right direction? No promises, of course.
Hope that helps,
Roland

Thank you very much.


[Bug]:     return typeof possibleEnumValue === "undefined" ? Result.err(new UnknownEnumValueError(casted, this.enumKeys, this.enumMapping)) : Result.ok(possibleEnumValue);

Contact Details
No response
What happened?
A bug happened!

Version
newst
What engine are you seeing the problem on?
No response
Relevant log output
No response

Looks like you have multiple items with the same name in one of the collections.
Also it could be an issue with an object in your code. It is hard for me to say as I have never had this error

This issue is caused by #10 I'll do a pull request to solve this


Bump container base image to Debian 12 and Python 3.12

The latest latest build of Matter/CHIP wheels v2024.11.0 require a newer Debian version. This is required because the CHIP wheels build uses the Matter SDK build system, which recently got updated to Ubuntu 24.04. This meant that the native library got linked against a newer glibc version.
Technically, the Python 3.12 update is not related/strictly required. But it seems that the Matter v1.3 version of Matter/CHIP wheels v2024.9.0 runs fine with Python 3.12 already. So it is safe to upgrade the two at once.

After a restart yesterday I started having issues with zeroconf and mDNS I had to rollback to version 6.6.0. Have anyone experience this?
2024-12-02 14:40:23.716 (MainThread) WARNING [zeroconf] Error with socket 55 (('::1', 5353, 0, 0))): [Errno 101] Network is unreachable
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 1275, in sendto
self._sock.sendto(data, addr)
OSError: [Errno 101] Network is unreachable


New format of acme.json in Traefik 2.0

Classification

[x] Minor bug

Reproducibility

[X] Always

Description
After i tried to migrate to Traefik 2.0 i noticed that the Let's Encrypt certs could not be read correctly.
The new acme.json file has a new format.
I have found a little tool which can dump the cert like your scripts does. But it works with the new format already.
https://github.com/ldez/traefik-certs-dumper
I have configured it to dump the certs in the correct format to work with the mailserver.
Steps to reproduce

Configure the mailserver via docker-compose.yml
Configure Traefik 2.0 via docker-compose.yml
Start everything

Configuration (docker-compose.yml, traefik.toml...etc)
reverse-proxy:
    image: traefik:${TRAEFIK_VERSION}
    restart: always
    hostname: traefik.${FQDN}
    container_name: traefik
    command:
      - --providers.docker
      - --certificatesresolvers.default.acme.email=admin@${FQDN}
    ports:
      - 80:80     # The HTTP port
      - 443:443   # The HTTPS port
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # So that Traefik can listen to the Docker events
      - ./data/traefik/config/traefik.toml:/traefik.toml # The config file
      - ./data/traefik/config/acme.json:/acme.json # Let'd Encrypt's config file
      - ./data/traefik/logs:/logs # Logs
    networks:
      dev-server-network:

 traefik-certs-dumper:
    image: ldez/traefik-certs-dumper:${TRAEFIK_CERT_DUMPER_VERSION}
    restart: always
    hostname: traefik-certs-dumper.${FQDN}
    container_name: traefik-certs-dumper
    command: file --source ./source/acme.json --version v2 --clean --watch --domain-subdir --crt-name=fullchain --key-name=privkey --crt-ext=.pem --key-ext=.pem
    volumes:
      - ./data/traefik-certs-dumper/data:/dump
      - ./data/traefik/config:/source
    networks:
      dev-server-network:

  mailserver:
    image: hardware/mailserver:${MAILSERVER_VERSION}
    restart: always
    hostname: mail.${FQDN}
    container_name: mailserver
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.mail.rule=Host(`mail.${FQDN}`) || Host(`spam.${FQDN}`)"
      - "traefik.http.routers.mail.entrypoints=http,https"
      - "traefik.http.routers.mail.tls=true"
      - "traefik.http.routers.mail.tls.certresolver=default"
      - "traefik.http.services.mail.loadbalancer.server.port=11334"
    ports:
      - "25:25"       # SMTP                - Required
      - "110:110"     # POP3       STARTTLS - Optional - For webmails/desktop clients
      - "143:143"     # IMAP       STARTTLS - Optional - For webmails/desktop clients
      - "465:465"     # SMTPS      SSL/TLS  - Optional - Enabled for compatibility reason, otherwise disabled
      - "587:587"     # Submission STARTTLS - Optional - For webmails/desktop clients
      - "993:993"     # IMAPS      SSL/TLS  - Optional - For webmails/desktop clients
      - "995:995"     # POP3S      SSL/TLS  - Optional - For webmails/desktop clients
      - "4190:4190"   # SIEVE      STARTTLS - Optional - Recommended for mail filtering
    environment:
      - DBPASS=${MAILSERVER_DATABASE_USER_PASSWORD}       # MariaDB database password (required)
      - RSPAMD_PASSWORD=${MAILSERVER_RSPAMD_PASSWORD}     # Rspamd WebUI password (required)
    # - ENABLE_ENCRYPTION=false                # Disables encryption because it causes a bug with a memory leak in 1.1
    # - DISABLE_DNS_RESOLVER=true
    # - ADD_DOMAINS=aa.tld, www.bb.tld...      # Add additional domains separated by commas (needed for dkim keys etc.)
    # - DEBUG_MODE=true                        # Enable Postfix, Dovecot, Rspamd and Unbound verbose logging
    # - ENABLE_POP3=true                       # Enable POP3 protocol
    # - ENABLE_FETCHMAIL=true                  # Enable fetchmail forwarding
    # - DISABLE_RATELIMITING=false             # Enable ratelimiting policy
    # - DISABLE_CLAMAV=true                    # Disable virus scanning
    # - DISABLE_SIGNING=true                   # Disable DKIM/ARC signing
    # - DISABLE_GREYLISTING=true               # Disable greylisting policy
    #
    # Full list : https://github.com/hardware/mailserver#environment-variables
    #
    volumes:
      - ./data/mail/config:/var/mail
      - ./data/traefik-certs-dumper/data/mail.${FQDN}:/etc/letsencrypt/live/mail.${FQDN}
    depends_on:
      - reverse-proxy
      - mariadb
      - redis
      - traefik-certs-dumper
    networks:
      dev-server-network:

Forgot the parameter  --version v2 on the traefik-certs-dumper container.

I've already created a PR (#406) modifying the existing script, because I had the same problem. Apparently it hasn't been merged yet. :man_shrugging:

Should we combine this PR with yours @TheZenti ?

I'm slightly confused - as far as I can see, this is no PR (yet), just an issue. :see_no_evil:
With the changes in my PR, @iBrotNano's addition of traefik-certs-dumper should be obsolete.

Right! Sorry for the confusion. :( My bad. I wanted to refer to the traefik-certs-dumper container.  In this case we are good here. :)

@iBrotNano , @TheZenti I merged the PR.


"Show whole diff of working tree" does not work

Running the "Show whole diff of working tree" command does not work in my environment:

My workspace is a folder in a WSL remote session.

Confirmed; I always open it with the icon so I missed this.
Does it work for you if you click the book icon in Source Control by Changes?

Thanks for your feedback. Yes, the book icon works.

0.2.3 fixes this, thanks for reporting!

@carlfriedrich please confirm whether that's fixed it for you

@jacekkopecky Great, thanks for the quick fix! Works for me now!


Validation: Misc fixes

Docs Build status updates of commit 9db960d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/webapi/work-around-for-singleresult-create.md
:bulb:Suggestion
View
Details

Odata-docs/webapiauth/overview.md
:white_check_mark:Succeeded
View

Odata-docs/webapi/work-around-for-singleresult-create.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 53a5dad:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/webapi/work-around-for-singleresult-create.md
:bulb:Suggestion
View
Details

Odata-docs/webapiauth/overview.md
:white_check_mark:Succeeded
View

Odata-docs/webapi/work-around-for-singleresult-create.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e76c070:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/webapi/work-around-for-singleresult-create.md
:white_check_mark:Succeeded
View

Odata-docs/webapiauth/overview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Global effort to fix build validation errors
@xuzhg, @odero
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!


[Cleanup] Persist queue name as data

This allows us to safely use aliases for queue indices if we want.
Signed-off-by: lloydmeta<EMAIL_ADDRESS>

Codecov Report

Merging #27 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #27   +/-   ##
=======================================
  Coverage   83.97%   83.97%
=======================================
  Files          18       18
  Lines        1142     1142
=======================================
  Hits          959      959
  Misses        121      121
  Partials       62       62

Continue to review full report at Codecov.

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


Fixes 1249: Add sonarqube check

https://issues.redhat.com/browse/HMS-1249

/retest

Ah I did not notice it for our project, but we are analysing post npm i so we are analyzing all the node modules :face_exhaling:

/retest

/retest

/retest

/retest

/retest


use errors.Is to check for a specific error

Signed-off-by: Fish-pro<EMAIL_ADDRESS>What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Comparing with == will fail on wrapped errors. Use errors.Is to check for a specific error
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

/auto-cc

We can't modify the reflector.go alone, we need to keep it as consistent as possible with client-go's reflector.go, so if we need to modify it, we can create pr in client-go and then clusterpedia will synchronize it with client-go's dependencies

We can't modify the reflector.go alone, we need to keep it as consistent as possible with client-go's reflector.go, so if we need to modify it, we can create pr in client-go and then clusterpedia will synchronize it with client-go's dependencies

@Iceber Thanks for your reply, I got it


App Crash on Form Close

Hello!!!
I'm studying skia4delphi to use in my applications. But something is happening that I can't figure out why. When I close some form, my application closes unexpectedly. Alternatively, I created a blank project with two blank forms. The first form only contains a button to open the second form. However when I close the second form, the application freezes and crashes. Do I need any specific treatment in my project?

Hello @cleberDeveloper, thanks for the report!
What is the version that you are using?
The version 5 introduce some unexpected issues, like this. We strong recommend the adoption of the version 6.0.0-beta2 (it is still on beta, but it is extremally stable). The beta version is available only on our GitHub release pages (the GetIt will receive just release versions).

@cleberDeveloper Can you confirm if the issue was fixed on version 6.0.0-beta2?

Hi,
Yes. It fixes with 6.0.0 relaxe.
Thanks!!!


Expose non-interactive option to CLI help

That’s it :octocat:
Related to #1162
Having that option in the CLI help would have saved my a few minutes.

Was actually under the impression it's --non-interactive. I might be wrong but the changelog mentions it 🤔 What also should work is --config.interactive=false

Sorry. I double checked it a few minutes ago.
Both of these don’t prevent prompts:
bower install  --no-interactive
bower install  --non-interactive

But this do:
bower install --config.interactive=false

Going to force push this change in a minute.

Done. But I’m not sure if this feels right.
Should it be:
{
  "flag":        "--config",
  "description": "Set and override settings from .bowerrc  eg. `--config.interactive=false`"
}

instead of:
{
  "flag":        "--config.interactive=false",
  "description": "Disable prompts"
}

I’m totally confused cause according to 8f0a3d7 (PR: #1969) there should be a --non-interactive option 😕
I have currently no time to dig deeper in the sources.
Please let me now if you want any changes to this PR.

Is there anything I can do to help to get this merged?

I was just hoping for some more opinions, as I understand your feeling that it doesn't seem entirely "right" using --config. However I think it's an often needed/looked up feature, so I'm cool with merging this. Can you squash the commits (or somehow re-trigger the CI)?

We could wait for a few days if there are other opinions especially about that comment above: https://github.com/bower/bower/pull/2404#issuecomment-266440097

Any additional feedback? Will this get merged?
Going to close this otherwise 😗


Icon Based Housing on City Panel Overview

Icon Based Housing on City Panel Overview

Apparently this also includes the changes I made to Great People Popups now because I have no idea how Github works.

Can you share a screenshot, please?

Sure:
Housing Changes

Great Person Popup Changes

This looks awesome, and thanks for fixing the GP panel scroll bars being out of their tracks, it was really annoying. Hope this gets merged soon.

Made it so that turns left indicator always rounds up (was previously rounding to nearest whole number, but in game terms .3 turns is really 1 more turn), and fixed scroll bar to be better placed. Replaced tabs with spaces to better match style guide in code.
Screenshots:
Windowed mode better scroll bar placement

Slightly changed recruit button placement so that it fit better with my other changes. I had forgotten to test for this previously, but it should be good now!

Looks good, merging now!


Create SSH firewall exemption for VDH SFTP

Problem statement
We need to create an SSH firewall exemption for the VDH SFTP server, vdhsftp.vdh.virginia.gov, in coordination with CDC. This ticket is to track that work
What you need to know
As part of the PHDI project, we need a way for our ingest function to reach out and grab data from the Virginia Department of Health. To enable this, we need to work with the relevant parties within CDC to create the appropriate SSH firewall exemption to enable this connectivity from our VDH VNET.
Acceptance criteria

[ ] We are able to run a simple ingest function from within our PHDI VNET to see and list directory contents of the VDH server

This was approved and implemented by the firewall team on Jan 24


Can the video play when in viewport and how to have multiple videos?

Hi,
using your plugin and it works great, trying to achieve this:
Is there a way to play the video just when in viewport and pause it when out? Also resume it when completely out of viewport would be a plus
Any suggestion?
Thanks a lot

Yeah I could update this to do so. I'll add it to the feature list. When I get some time I'll do it. Alternatively if you want it before, please fork, do it yourself and put in a PR 👍

Hi!
Trying to figure out how to do it, If I achieve this I will post it for sure.
Thanks!

video play when in viewport
Very necessary


[Detections] Decode pixel_geometry to base64

See the below Disqus thread to have context on how to deal with the pixel_geometry attribute given by detections.

Closing. Duplicate of #32


[SPARK-14259] [SQL] Merging small files together based on the cost of opening

What changes were proposed in this pull request?
This PR basically re-do the things in #12068 but with a different model, which should work better in case of small files with different sizes.
How was this patch tested?
Updated existing tests.
Ran a query on thousands of partitioned small files locally, with all default settings (the cost to open a file should be over estimated), the durations of tasks become smaller and smaller, which is good (the last few tasks will be shortest).

ping @nongli

Test build #54661 has started for PR 12095 at commit 504a762.

Test build #54661 has finished for PR 12095 at commit 504a762.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54661/
Test PASSed.

cc @marmbrus

Lgtm, though I still think pipelined reading is the right thing to do long term.

Pipelined reading is a good idea to overlap opening and processing, will be done in another PR. After that, this PR is still useful, thinking of lots of tiny files (100ms to open, but 1ms to process), opening these files will be majority of the time, we should not add thousands of tiny files into one partition.

Merging this into master, thanks!


Error messages are confusing.

The error messages need adjustment. In this case, the AGB was too high, but the error message says it's a problem with "Age" and then it says biomass has to be between 0% and 100%. Basically it should say: Error message with the input value for AGB AND 111948 is not between 0 and 40,000, or whatever max you want to use.
2019-11-13 14:59:14,472 -    Loading initial communities from file "AK_IC_File-SW_111019.txt" ...
2019-11-13 14:59:14,494 - Error at line 7 of file "AK_IC_File-SW_111019.txt":
Error with the input value for Age:
"(111943" is not a valid aboveground biomass input:
111943 is not between 0% and 100%

I updated the error messages but it needs to be tested before posting to the Support repo.  Could you compile and test?

I don't see the code changes. When I look in this repo, there weren't any changes to the code in Nov, except for the project and ReadMe. What am I missing?

The changes are in a branch:  https://github.com/LANDIS-II-Foundation/Library-Initial-Community/tree/InputBiomass

But there weren't any changes in the the main or branch in Nov. I'm still confused.

Ah, yes, I see.  The code was not fully synced.  Should be ready for testing now.

So I couldn't get it run at all. Versioning issue?

I wouldn't think so.  Let's chat on the phone when you can.  Will you be in this morning?  I'm out after 11am eastern.

Runs now!  That fixed it.  Biomass in txt file matches csv.
Still a minor issue with the error message. Says it's an error with the "input value for Age", when it's an error in the biomass. I tried to fix it myself, but I couldn't find the error.

I made a couple of very minor tweaks to clean up the error messages.  Could you test again?  Thanks!


[SPARK-10871] include number of executor failures in error msg

Merged build triggered.

Merged build started.

Test build #43076 has started for   PR 8939 at commit 52ad7f3.

Test build #43076 has finished for   PR 8939 at commit 52ad7f3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43076/
Test PASSed.

LGTM merging into master 1.5.


bigloo: 4.4b -> 4.5b

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bigloo/versions.
meta.description for bigloo is: Efficient Scheme compiler
meta.homepage for bigloo is: http://www-sop.inria.fr/indes/fp/Bigloo/
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.5a-1 with grep in /nix/store/calwmm19b157nr5c4y3piq9yxgx6z77m-bigloo-4.5a-1
found 4.5a-1 in filename of file in /nix/store/calwmm19b157nr5c4y3piq9yxgx6z77m-bigloo-4.5a-1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
bigloo
hop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/calwmm19b157nr5c4y3piq9yxgx6z77m-bigloo-4.5a-1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bigloo https://github.com/r-ryantm/nixpkgs/archive/0c34a77503b918a8761f4a87c3dee4b682496cdc.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/calwmm19b157nr5c4y3piq9yxgx6z77m-bigloo-4.5a-1
ls -la /nix/store/calwmm19b157nr5c4y3piq9yxgx6z77m-bigloo-4.5a-1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

hop

1 package built:

bigloo

Maintainer pings
cc @thoughtpolice for testing.

@ofborg build hop

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/bigloo/versions.
meta.description for bigloo is: Efficient Scheme compiler
meta.homepage for bigloo is: http://www-sop.inria.fr/indes/fp/Bigloo/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.5b with grep in /nix/store/addcmhvpfg0l4s0b644rsji0w3sfz1h4-bigloo-4.5b
found 4.5b in filename of file in /nix/store/addcmhvpfg0l4s0b644rsji0w3sfz1h4-bigloo-4.5b

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
bigloo
hop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/addcmhvpfg0l4s0b644rsji0w3sfz1h4-bigloo-4.5b \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bigloo https://github.com/r-ryantm/nixpkgs/archive/8d2cfc31934b2163526b99224a08ffca5d3e2c6d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8d2cfc31934b2163526b99224a08ffca5d3e2c6d#bigloo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/addcmhvpfg0l4s0b644rsji0w3sfz1h4-bigloo-4.5b
ls -la /nix/store/addcmhvpfg0l4s0b644rsji0w3sfz1h4-bigloo-4.5b/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

hop

1 package built:

bigloo

Maintainer pings
cc @thoughtpolice for testing.


[BUG] Running import zeta immediately fails with "RuntimeError: mat1 and mat2 shapes cannot be multiplied (512x4 and 512x512)"

Hi,
I tried running vision mamba, which relies on zetascale. After following the error stack, I narrowed it down to zetascale causing the problem when trying to import it.
To Reproduce
Steps to reproduce the behavior:

Try running 'import zeta' in Python

Expected behavior
For zetascale to be imported and usable
Screenshots

Additional context
I am working on Ubuntu 22.04, running Python 3.10.13 (I have had the same error with Python 3.9 and 3.11). I have the latest PyTorch as of February 21, 2024. I am working in a Conda virtual environment where I installed vision mamba by running 'pip install vision-mamba' which ran without issues.
I would greatly appreciate any advice on how to zetascale to work!
Thanks,
Julian

@julian540 I'm closing for now, lmk if you have the issue


go-ethereum: 1.9.3 -> 1.9.5

Motivation for this change
Update go-ethereum to the latest release.

https://github.com/ethereum/go-ethereum/releases/tag/v1.9.5

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @adisbladis @asymmetric @lionello

@GrahamcOfBorg build go-ethereum


DL: Update madlib_keras_fit code to weight by images instead of buffers

JIRA: MADLIB-1310
Previously, while merging the weights, accuracy and loss, we
assume that all the buffers are of the same size. This may not be always
the case.  Ideally we should use the total no of images per segment to
average the weights, accuracy and loss.
This commit, updates the transition, merge and final function for
madlib_keras_fit() to use the number of images on a segment instead of
the buffer count for averaging weights, accuracy and loss.
Additionally, the function deserialize_weights() when deserializing
loss and accuracy from state, type-casted it to an int, which resulted
in computing lower loss and accuracy while training. This PR also
addresses this issue.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/853/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/854/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/855/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/860/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/861/


QR Code Card does not support templates

Hey @igor-panteleev, great card! Currently it doesn't seem to support setting templates for qr codes, e.g. assigning an input_text state to the password field or setting it to source type text and rendering a template entity there. Both times the QR code text contains the literal template and not the actual value, e.g. instead of
S:WIFINAME;T:WPA;P:WIFIPASSWORD;; it returns
{{ "S:WIFINAME;T:WPA;P:"~states('input_text.guest_wifi_password')~";;" }}
Could you entend the functionality by any chance?

I might add support to use entities in the WiFi config alongside string values.
For now, there is a workaround https://github.com/igor-panteleev/lovelace-qr-code-card/issues/4#issuecomment-1502135436


Non-dimensionalization of pre-defined power laws

This PR adds an option to directly non-dimensionalize power laws dfined in the database. It's enough to pass the characteristic lenghts when instantiating the rheology struct.
CharDims = GEO_units(; viscosity=1e19, length=1000km)
SetDiffusionCreep("Dry Anorthite | Rybacki et al. (2006)", CharDims)

Cool - can you add some tests?


Model.update not detecting datetime change in FastAPI

Bug
I'm trying to automatically update the modified_at field in my Server model from a FastAPI enpoint, but the Model.update method doesn't update the field.
Current Behavior
For this i have the base model to create a Server (simplified version):
class Server(Model):
    id: UUID = Field(primary_field=True)
    name: str
    created_at: datetime = Field(default_factory=datetime.now)
    modified_at: datetime = Field(default_factory=datetime.now)

and a model used to patch the Server that automatically updates the modified_at field  (simplified version):
class ServerUpdate(BaseModel):
    name: Optional[str]
    modified_at: Optional[datetime]

    class Config:
        validate_assignment = True

    @root_validator
    def number_validator(cls, values):
        values["modified_at"] = datetime.now()
        return values

In my FastAPI endpoint i have something like this:
@router.put("/{id}", response_model=Server)
async def update_server_by_id(id: UUID, patch: ServerUpdate):
    server = await engine.find_one(Server, Server.id == id)

    if server is None:
        raise HTTPException(404)

    server.update(patch)

    try:
        await engine.save(server)
        return server
    except Exception:
        raise HTTPException(500)

The modified_at field is never updated.
If I print(patch.dict()) it gives me:
{'name': None, 'modified_at': datetime.datetime(2022, 9, 11, 11, 4, 6, 319829)}
If I print(server.dict()) before the update it gives me:
{'id': UUID('c4dfa7ac-d25d-45cb-8bc3-f59e5938a58c'), 'name': 'Server 1', 'created_at': datetime.datetime(2022, 9, 11, 9, 46, 45, 234000), 'modified_at': datetime.datetime(2022, 9, 11, 9, 46, 45, 234000)}
so the patch instance has the current datetime.
The only way I found to make it work is to set patch.modified_at = patch.modified_at before server.update(patch)
Expected behavior
The Model.update method should update the datetime field.
Environment

ODMantic version: 0.8.0
MongoDB version: 5.0.12
Pydantic infos (output of python -c "import pydantic.utils; print(pydantic.utils.version_info())):

             pydantic version: 1.10.1
            pydantic compiled: True
                 install path: D:\Projects\Python\vendor-system-fastapi\.venv\Lib\site-packages\pydantic
               python version: 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
                     platform: Windows-10-10.0.19043-SP0
     optional deps. installed: ['dotenv', 'typing-extensions']

Version of additional modules (if relevant):

fastapi: 0.82.0

Additional context
Add any other context about the problem here.

common cases.  see:  https://pydantic-docs.helpmanual.io/usage/validators/#validate-always

@linpan I tried your suggestion but the result is the same. It must be something inside the engine save function.

common cases. see: https://pydantic-docs.helpmanual.io/usage/validators/#validate-always

The patch variable has the right  datetime value already, but it doesn't get saved by the engine.

common cases. see: https://pydantic-docs.helpmanual.io/usage/validators/#validate-always

class User(Model):
    username: str = Field(index=True)
    created: datetime = Field(default_factory=datetime.now)
    modified: datetime = Field(default_factory=datetime.now)

    @validator("modified", always=True, pre=True)
    def auto_now(cls, value):
        return datetime.now()

Same bug

This is ok
class User(Model):
    username: str = Field(index=True)
    created: datetime = Field(default=datetime.now)
    modified: datetime = Field(default=datetime.now)


password database files

I want to be able to share the password with the 1.7.10 login plugin. Is it possible to share the password database with the AuthME plugin?

Sharing is most likely not possible, due to the differences in how AuthMe and UserLogin structure their saved data.
Migrating, on the other hand, is most likely possible.
I see AuthMe has an option for bcrypt-hashed passwords. You'd have to turn it on first and foremost, as UserLogin also stores its passwords bycrpt-hashed.
I'm not sure how the structure for AuthMe's saved data works, but you'd probably have to restructure UserLogin's playerData.yml for it to be compatible with AuthMe afterwards.


Update Font Awesome and fix instagram/500px icons

Wanted to make 500px and instagram icons work correctly for SOCIAL links, this pull request should be able to fix that.

@iksaif If you are interested this feature has been merged into the laces3 theme https://github.com/lgiordani/laces3

@lgiordani I know I haven't been the quickest to respond to PRs lately (busy life, busy work), but you're now basically going over every PR in my project, trying to pull people to your project. That's not really nice form, don't you think?

I'm not a seasoned contributor to open source projects where the contributors aren't already organized through some other means, so I don't know the etiquette in a situation like this.
Could you join forces? As a user of the theme development has been a little slow (totally understandable, I'm busy too)... but I also I don't like the idea of it splitting the project or migrating to a different theme.

No no, sorry. As specified in the project I just wanted a bleeding edge version of the theme, and wanted only to notify people that, if they want, they have the feature there. Sorry. I don't really want to pull anyone

Could you join forces? As a user of the theme development has been a little slow (totally understandable, I'm busy too)... but I also I don't like the idea of it splitting the project or migrating to a different theme.

To me, this seems the best solution as well. I was actually planning to setup a Gitter chat room for pelican-bootstrap3. This way, we could actually discuss progress. I'm perfectly willing to give write access to this repo to @lgiordani, but only if we can align on the goals for this theme :)

I would encourage that with dev and master branches

@DandyDev you know that I'm here just to help (I already submitted and discussed PRs). I know that life is demanding and no one can do everything. Sorry again if what I did was perceived as an attempt to destroy something. If it helps you, I'm ready to give some time to the project. Obviously, given that this is your project, I'm not here to overturn it.

Hi!
First of all, thanks again for your pull request! I appreciate the contribution, but I cannot accept this PR at the moment. It's with heavy heart that I have decided that I can no longer maintain this theme due to lack of time and changing interests. To makes sure the theme lives on however and not goes to waste, I've donated it to the Pelican community. It can now be found in the official pelican-themes repository. I'd suggest you re-submit your pull request there.
Sorry for the inconvenience!


Decompiling more than one obfuscated class at a time

I am not sure this is an issue or not, but I can't find a manual anywhere.
When I decompile a single obfuscated class, it works just fine. However, when I drop a ZIP/JAR file containing multiple class (including the single one that was previously decompiled fine) nothing gets decompiled. The icon for files has changed, so it is like jadx is not detecting anything:

I can see the logs say:
WARN : No dex files found in ...
Not sure if this is related:
https://github.com/skylot/jadx/pull/455/files
How can I force decompilation of all classes inside a ZIP file?

@Rourke101 looks like conversion jar to dex failed and I can't tell exactly why without a sample.
You can try to convert it yourself using d8 from Android SDK.
Or use native java decompiler like cfr or gui took like Bytecode Viewer

mmm.. But this is not a DEX. Can't I decompile files in bulk like they do in single file decompilation?

@Rourke101 I think there is some misunderstanding. Jadx can load jar files, to do this jar files internally converted to dex, but now jadx uses for such conversion outdated dx library which has limited support for new versions of java classes (see #823). And looks like in your case some classes broke this conversion. So you need manually convert java classes to dex using a new d8 library or just use java native decompiler.
P.S. For me it is surprising that many people (according to open issues) using jadx to decompile native java bytecode, jadx is obviously bad at it: new java versions not supported, new instructions not supported, it is very slow because of internal conversion, etc... :(

Thanks for the clarifications. Can you suggest a native decompiler which is as good as jadx?
Perhaps I'm using the wrong tool, but it decompiled single classes so well I though I could use it for multiple of them.


Update Request/PR: Amazon PA API 5.0

PA API 4 will sunset on October 31st 2019.
Upgrade to PA API 5.0 is necessary in order for the package to function after said date.
Anyone working on this currently?

@jvv8 we are working on migration to Laminas and we have made decision that this library is not going to be supported and moved to Laminas. We are suggesting to use https://github.com/aws/aws-sdk-php instead, as it the official library.


Job service refactor

A job service should have following capabilities:

HA
Monitored
Controlled
Multiple trigger ways (immediate, schedule and hook etc.)
Statistical
Parallel/chain executing
Scaling
Distributed

Refactor direction

[Option1] Design and develop
[Option2] Investigate and integrate

All works are done, close this epic.


DWIs not found for dHCP data

Hi all,
I am aiming to use --recon-only to preform tractography on preprocessed neonatal data from dHCP. I am using version 0.15.3. I believe dHCP is correctly in bids for preprocessed data but I keep getting the error that no dwi files are found. I have also tried renaming the files to a simpler version of bids naming structure (e.g sub-NDARINV_ses-15102_dwi.nii.gz) since I am only preforming reconstruction and thus know the data is preprocessed but I continued to get the same error.
Here is my function call:
run bids_path,out_path,license_path /imaging/local/software/singularity_images/qsiprep/qsiprep-0.15.3.simg bids_path out_path participant --participant-label %s --recon-spec dsi_studio_gqi --recon-only --recon-input bids_path --infant --nthreads 16 --output-resolution 1 --fs-license-file license_path
Here is the .out file:
WARNING: Underlay of /etc/hosts required more than 50 (102) bind mounts
Matplotlib created a temporary config/cache directory at /tmp/matplotlib-hcp_a8lx because the default path (/home/qsiprep/.config/matplotlib) is not a writable directory; it is highly recommended to set the MPLCONFIGDIR environment variable to a writable directory, in particular to speed up the import of Matplotlib and to better support multiprocessing.
220404-13:04:46,593 nipype.workflow IMPORTANT:
Running qsirecon version 0.15.3:
  * BIDS dataset path: /imaging/astle/am11/dHCP/bids.
  * Participant list: ['NDARINV'].
  * Run identifier: 20220404-130446_35244ba7-450b-4881-b926-cb86fe41634e.

220404-13:04:46,781 nipype.workflow INFO:
found [] in /imaging/astle/am11/dHCP/bids
220404-13:04:46,781 nipype.workflow INFO:
No dwi files found for NDARINV
220404-13:04:47,43 nipype.workflow IMPORTANT:
Works derived from this qsiprep execution should include the following boilerplate:
Reconstruction was
performed using QSIprep 0.15.3,
which is based on Nipype 1.7.0
(@nipype1; @nipype2; RRID:SCR_002502).
Many internal operations of qsiprep use
Nilearn 0.9.0 [@nilearn, RRID:SCR_001362] and
Dipy 1.4.1[@dipy].
For more details of the pipeline, see the section corresponding
to workflows in qsiprep's documentation.
References
[WARNING] This document format requires a nonempty  element.
Please specify either 'title' or 'pagetitle' in the metadata.
Falling back to 'CITATION'
QSIPrep failed: Graph has no nodes or edges
Traceback (most recent call last):
File "/usr/local/miniconda/bin/qsiprep", line 8, in
sys.exit(main())
File "/usr/local/miniconda/lib/python3.8/site-packages/qsiprep/cli/run.py", line 659, in main
qsiprep_wf.run(**plugin_settings)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/engine/workflows.py", line 638, in run
runner.run(execgraph, updatehash=updatehash, config=self.config)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/base.py", line 121, in run
self._generate_dependency_list(graph)
File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/base.py", line 437, in _generate_dependency_list
self.depidx = nx.to_scipy_sparse_matrix(
File "/usr/local/miniconda/lib/python3.8/site-packages/networkx/convert_matrix.py", line 855, in to_scipy_sparse_matrix
raise nx.NetworkXError("Graph has no nodes or edges")
networkx.exception.NetworkXError: Graph has no nodes or edges
Sentry is attempting to send 4 pending error messages
Waiting up to 2 seconds
Press Ctrl-C to quit
The file structure looks as follows:
bids/
    dataset_description.json
    from-dwi_to-extdhcp40wk_mode-image.json
    from-dwi_to-T2w_mode-image.json
    from-T2w_to-dwi_mode-image.json
    from-template40wk_to-dwi_mode-image.json
    participants.tsv
    sub-NDARINV/
        sub-NDARINV_sessions.tsv
        .DS_Store
        ses-15102/
            .DS_Store
            dwi/
                sub-NDARINV_ses-15102_model-DKI_MK.nii.gz
                sub-NDARINV_ses-15102_model-DTI_MD.nii.gz
                sub-NDARINV_ses-15102_model-DTI_diffmodel.nii.gz
                sub-NDARINV_ses-15102_desc-preproc_dwi.nii.gz
                sub-NDARINV_ses-15102_desc-preproc_dwi.bval
                sub-NDARINV_ses-15102_model-DTI_EVECS.nii.gz
                sub-NDARINV_ses-15102_desc-preproc_dwi.bvec
                sub-NDARINV_ses-15102_model-DTI_FA.nii.gz
                sub-NDARINV_ses-15102_desc-brain_mask.nii.gz
                sub-NDARINV_ses-15102_desc-preproc_dwi.json
                sub-NDARINV_ses-15102_desc-brain_mask.json
            fmap/
                sub-NDARINV_ses-15102_fieldmap.json
                sub-NDARINV_ses-15102_fieldmap.nii.gz
            xfm/
                sub-NDARINV_ses-15102_from-extdhcp40wk_to-dwi_mode-image.nii.gz
                sub-NDARINV_ses-15102_from-dwi_to-T2w_mode-image.mat
                sub-NDARINV_ses-15102_from-dwi_to-extdhcp40wk_mode-image.nii.gz
                sub-NDARINV_ses-15102_from-T2w_to-dwi_mode-image.mat
            qc/
                sub-NDARINV_ses-15102_qc.json
                sub-NDARINV_ses-15102_qc.pdf

Any thoughts on why the dwis are not being found? Thanks!

This seems to be an issue specific to using --recon-only and/or --recon-input. I tested this with other data that I previously processed with QSIprep and it had the same issue of not finding the DWIs.

Did this turn out to be a singularity issue?

I believe this was happening because I was trying to user dHCP preprocessed data. So it was in bids but not in the exact same format as data preprocessed with qsiprep.


Save the preview stage colors

Minor issue, but anyway: Please store in the scmp file which colors were set for the preview stage. I have a skin with only white elements on a black background, and I have to set the color I really every time to see something.
Thanks and great work! :)

either that or an option to globally have a background color(or any of those preview options)  saved when you load the app regardless of what project is loaded

Good ideas guys. I'll probably have this in the next version. Thank you.

This has been resolved for the next version. Thank you.