Problem with ESM module imports

I'm trying to include https://github.com/JoshK2/react-spinners-css to my razzle build.
React-spinners-css doesn't use/support commonJS modules at all.
I get following error when I run npm start:

/node_modules/react-spinners-css/dist/index.js:1
import Circle from './Circle';
^^^^^^
SyntaxError: Cannot use import statement outside a module

I tried to use my own .babelrc:
{
  "presets": [
    "razzle/babel"
   ],
   "plugins": [
     "@babel/plugin-transform-modules-commonjs"
   ]
}

But that didn't help...
Can anyone please advise on how to get those ESM modules imported?

@jutunen I responded to you in my project repo, otherwise, you can try to install just the component you need using my bit.dev collection: https://bit.dev/joshk/react-spinners-css
Tell me if it's worked for you.

You need to change config.externals to make razzle allow the esm module to be bundled.

So, use cjs or modify config.externals. Or write a esm plugin to add modifications automatically for listed packages.

Hi, I fixed this in the last version.
And also wrote details about it here: https://github.com/JoshK2/react-spinners-css#how-to-use-with-ssr

fixed in dev


"Flash the fast bootloader": Stray paren in code block

In "Develop "Hello LEDs" App on Brillo Edison" part "3. Flash the Edison", section "Flash the Fast Bootloader", there is a parenthetic comment appended to the code block:
sudo dpkg -i Downloads/phoneflashtoollite_<IP_ADDRESS>_linux_x86_64.deb(This will say there was a dep missing. The next step fixes it).
The open paren is actually within the "code" style, so you might think the command you were required to type actually ended with "(".
(You'd have to be naive to make that mistake, but it still looks sloppy.)

Hmm, I couldn't even run the lines after that.  What I ended up having to do was:
cd ~
mkdir Downloads   # assuming it doesn't already exist
cd Downloads
wget https://download.01.org/android-ia/tools/phoneflashtool-lite/<IP_ADDRESS>/phoneflashtoollite_<IP_ADDRESS>_linux_x86_64.deb   # as found by Google, I assume this is the right one
cd ~
sudo dpkg -i Downloads/phoneflashtoollite_<IP_ADDRESS>_linux_x86_64.deb  # fails for lack of gdebi etc.
sudo apt-get install p7zip-full gdebi-core gdebi   # line on page appears to be corrupted version of this
sudo dpkg -i Downloads/phoneflashtoollite_<IP_ADDRESS>_linux_x86_64.deb


Present mode doesn't fullscreen when pdf is embedded

First of all, note that I don't think this behaviour is bad currently, I'm just making you aware. I actually rely on this behaviour, so please don't change it before the below mentioned alternative is implemented.
Configuration:

Web browser and its version: firefox 96.0.2
Operating system and its version: Arch linux, sway (wayland)
PDF.js version: Whatever came with the browser
Is a browser extension: no

Steps to reproduce the problem:

Open a web page with an embedded PDF
Press the present button on the PDF

What is the expected behavior? (add screenshot)
The more correct and consistent behaviour would be to present the PDF in full screen.
What went wrong? (add screenshot)
It expands the pdf to fill the window (just the way it shows in the demo). Pressing the button again will still not present the pdf in full screen. For now this is to me better than presenting, since I more often want to view the PDF expanded to the whole window. But ideally, when the pdf is embedded, there would be a separate button that would allow you to expand the pdf
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
I cannot link the website, since you have to log in. You'll need to find a website that embeds PDF's, I suppose using an iframe.

I cannot link the website, since you have to log in. You'll need to find a website that embeds PDF's, I suppose using an iframe.

Unfortunately that makes it somewhat difficult to follow the provided STR, since using e.g. https://pdfobject.com/static/ I cannot actually reproduce any of this (on Windows).
Please note that e.g. an  can use the allowfullscreen attribute to control whether or not the FullScreen API (which is what the PDF.js viewer uses for PresentationMode) is actually allowed to be used. Hence this issue, to me at least, certainly sounds like it might actually work as expected!?

But ideally, when the pdf is embedded, there would be a separate button that would allow you to expand the pdf

Actually, there already is: Please note the "Current view..." button on the right-hand side of the toolbar, which you can either middle-click or right-click (and then choose e.g. open in new tab) in order to get a full-sized viewer.

Hmm, this view is different than any of the views on the website you linked. There's no download or current view button. There's only a download button separate from pdf.js on the page itself. I guess I'm allowed to share the code they use to show the pdf:

...

...

I tried copying the relevant parts.

Thank you for the screen-shot, and the excerpt from the HTML code!
Based on your initial description and this additional information, it actually confirms my suspicion that what you're seeing is a custom PDF.js viewer with (some) modified/removed functionality. Unfortunately, this is not something we can help with and you'll need to contact that web-page directly for support; sorry about that.
Slightly off-topic, but: This sort of confusion is exactly why we ask those who use the PDF.js viewer, in custom implementations, to change its appearance to not unnecessarily mislead users into thinking it's the Firefox built-in PDF Viewer that they're seeing.

Thank you for your patience and explanation. There seem to be some other buttons missing as well. I have no idea why they would make a custom version just to remove some functionality.

Slightly off-topic, but: This sort of confusion is exactly why we ask those who embed the PDF.js viewer, in custom implementations, to change its appearance to not unnecessarily mislead users into thinking it's the Firefox built-in PDF Viewer that they're seeing.

Yes I agree. What could also help on your side is adding some version info in the dropdown below document properties and make sure firefox sets their version to something different.

Note that Firefox will always print the PDF.js version number in the console, when the built-in PDF Viewer is being invoked. For example, in Firefox Nightly 98, when opening http://mirrors.ctan.org/info/lshort/english/lshort.pdf the following line is printed (with the version number last):
PDF 458436452feb268d340a4b6564fe9133 [1.5 xdvipdfmx (20190824) / LaTeX with hyperref] (PDF.js: 2.13.24)

What could also help on your side is adding some version info in the dropdown below document properties and make sure firefox sets their version to something different.

Unfortunately it'd be impossible to prevent a custom viewer from accidentally, or even deliberately, displaying the same exact version information. Hence this probably wouldn't help all that much, see also issue #5884.

Note that Firefox will always print the PDF.js version number in the console, when the built-in PDF Viewer is being invoked. For example, in Firefox Nightly 98, when opening http://mirrors.ctan.org/info/lshort/english/lshort.pdf the following line is printed (with the version number last):

Interesting. When opening that pdf,  I get the string
PDF 458436452feb268d340a4b6564fe9133 [1.5 xdvipdfmx (20190824) / LaTeX with hyperref] (PDF.js: 2.12.248)

But when opening the page this issue is about I also get a string, namely:
PDF 284c6bc89fcf4626d4dd4a60d14d9f90 [1.5 MiKTeX pdfTeX-1.40.20 / LaTeX with hyperref] (PDF.js: 2.9.0)

It seems that non built-in versions of pdf.js also print their version string to console.

Unfortunately it'd be impossible to prevent a custom viewer from accidentally, or even deliberately, displaying the same exact version information. Hence this probably wouldn't help all that much, see also issue #5884.

True, but it not being the default would probably prevent most cases of that happening. I don't think many vendors will set their string the same on purpose. It seems from the linked issue that it's mostly a case of not thinking it's neccesary.

When opening that pdf, I get the string
PDF 458436452feb268d340a4b6564fe9133 [1.5 xdvipdfmx (20190824) / LaTeX with hyperref] (PDF.js: 2.12.248)

That's because you're using Firefox 96, which given that it's older (than the current Nightly) simply contains an older PDF.js version as well.

PDF 284c6bc89fcf4626d4dd4a60d14d9f90 [1.5 MiKTeX pdfTeX-1.40.20 / LaTeX with hyperref] (PDF.js: 2.9.0)

It seems that non built-in versions of pdf.js also print their version string to console.

Please note that a non-built version doesn't actually have a version number, and in that case ... (PDF.js: -) would've been printed instead.
Hence the conclusion is that they've somehow incorrectly built the library/viewer, since a version number such as the quoted one has never existed.

It seems from the linked issue that it's mostly a case of not thinking it's neccesary.

There's also the fact that all code needs to be both implemented and then maintained going forward, and it's somewhat questionable if this feature (another dialog box) wouldn't be enough of a special-case to not really be worth it here.


Adding new ingredients

When in a formular and trying to add an ingredient and its not available, I'll create one... But having to create multiple, where the first one was 50% in DPG then adding the next, and its not dilluted, DPG is still selected and I have to change to dilution percent and change 100 to 10 and back to 100 for the field with dilutant is reset.. would be a nice fix if automatically set.

Please provide context, version, environment, screenshots etc

Docker
Latest version 5.4
Docker on my QNAP
Attached are photos
. xblomx
On Feb 4, 2023, 15:37 +0100, John B @.***>, wrote:

Please provide context, version, environment, screenshots etc
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Here images are, dont know of you got them before.

Seems like a broken update between versions.
Try to login to the database and apply the db schema update manually
db/updates/update_5.3-5.4.sql

Okay, how to login to the database?
I'm running on container station on QNAP and also have portainer installed
I can login via console but executing this command from there gives no such file or directory
. xblomx
On Feb 5, 2023, 14:50 +0100, John B @.***>, wrote:

Seems like a broken update between versions.
Try to login to the database and apply the db schema update manually
db/updates/update_5.3-5.4.sql
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

You have to patch that file against the database.
Try this command:
mysql -upvault -ppvault pvault < /var/www/html/db/updates/update_5.3-5.4.sql

Sweet, that did it ;) there were already 4 created edc, edt, edp, and perfume, so all sweet ;)
Thanks a million
. xblomx
On 5 Feb 2023 at 14.50 +0100, John B @.***>, wrote:

Seems like a broken update between versions.
Try to login to the database and apply the db schema update manually
db/updates/update_5.3-5.4.sql
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

John,
I managed to recover from a backup some time ago, lost 14 days..
Installed 5.4 again due to the backup I had, and have updated to 5.5
But I'm getting the same issue with the missing perfume types, and tried the previous reccomended, with no success.
It gives me this error like last, see attached.
How to recreate that table when it's missing from fresh install in 5.4 and 5.5?
That would be really nice to know.
. xblomx
On Feb 4, 2023, 15:40 +0100, . xblomx @.***>, wrote:

Docker
Latest version 5.4
Docker on my QNAP
Attached are photos
. xblomx
On Feb 4, 2023, 15:37 +0100, John B @.***>, wrote:

Please provide context, version, environment, screenshots etc
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Updating to ember 2.7 causes problems with item/optionComponent usage

I recently updated a project to ember 2.7, and found that this broke my usage of the ember-selectize component.  I've been supplying the itemComponent and optionComponent properties to specify which component should provide the content for the selectize control.  After updating, I get ember-selectize.js:819 Uncaught TypeError: componentLookup.lookupFactory is not a function when trying to render the selectize component.
Further error detail:

I created the simplest repro case I could come up with to help narrow down the problem: https://github.com/timmorey/selectize-regression.  The app just tries to display a selectize component with custom content.  All tests pass and everything works fine at ember 2.6 (https://github.com/timmorey/selectize-regression/commit/73427761ea8c6f5c5f4bee3fbc8eded00176ae37), but the selectize stops working and tests fail after updating to 2.7 (https://github.com/timmorey/selectize-regression/commit/ce653d0558b399448991d92ff8af18c164c42962)
Any idea what is going wrong here?

@timmorey can you test with my fork?
 "ember-cli-selectize": "safeforge/ember-cli-selectize",

@safeforge I tried that branch, and it fixes my test case.  Also tried it in my real app, and it seems to work.

Works only in 2.7 but not in 2.8.
component.createElement() is not a function

Can someone try with 0.5.6 and close if it works?

It would not work with 0.5.12, since it has that _lookupFactory call.
On development the error would state:
DEPRECATION: Using "_lookupFactory" is deprecated. Please use container.factoryFor instead. [deprecation id: container-lookupFactory] See http://emberjs.com/deprecations/v2.x/#toc_migrating-from-_lookupfactory-to-factoryfor for more details.


drivers: uart: nrf_uarte: Fix power management transitions

Deadlock may occur when uart device was put to low power state
while uart_poll_out was in progress. Poll out pends until uarte
is ready to send new byte and it is detected by endtx and txstopped
events being set. When uarte was disabled while poll_out was pending
events were never set and that lead to deadlock. Added a step
in going to low power state in which CPU waits for txstopped event
and only after that uarte peripheral is disabled.
Additionally fixed uart_callback_set not returning error code when device did not support async api.
Added test for uart power management. Test is putting uart device into low power state and back to active and validates that it is restored correctly.

@anangl i've applied your comments.


typo locale fix and todo: move toast messages to locales

@mistikk we need to check all toast messages as well...


First pass buffer optimization

Initial timings (posted below) indicate that buffer optimization is a good idea, benefits outweigh the penalty when the allocated buffer was insufficient.
Main question now is how/whether we let the user specify a desired size for the buffer.  Also do we want to enable different policies (eg. throw an error if buffer was not big enough)?

cuda (P100)
buffer_size=50
buffer_size=5
w/o buffer optimization

construction
0.315553
0.310011
0.315535

kNN
0.38308
0.382824
0.383394

radius
0.251215
0.37983
0.3486

openmp (16 threads)
buffer_size=50
buffer_size=5
w/o buffer optimization

construction
0.348378
0.350198
0.354455

kNN
0.587793
0.589182
0.587693

radius
0.450977
0.873691
0.867394

serial
buffer_size=50
buffer_size=5
w/o buffer optimization

construction
3.50672
3.52719
3.52879

kNN
6.67414
6.6447
6.58063

radius
4.7042
9.30572
9.1137

Codecov Report

Merging #411 into master will increase coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #411      +/-   ##
==========================================
+ Coverage   96.68%   96.74%   +0.06%
==========================================
  Files         102      102
  Lines        7324     7311      -13
==========================================
- Hits         7081     7073       -8
+ Misses        243      238       -5

Impacted Files
Coverage Δ

packages/Search/test/tstDetailsUtils.cpp
100% <100%> (ø)
:arrow_up:

packages/Search/src/DTK_LinearBVH_decl.hpp
100% <100%> (ø)
:arrow_up:

packages/Search/src/details/DTK_DetailsUtils.hpp
100% <100%> (ø)
:arrow_up:

packages/Discretization/test/MeshGenerator.hpp
99.61% <0%> (ø)
:arrow_up:

packages/Discretization/test/tstMeshGenerator.cpp
100% <0%> (ø)
:arrow_up:

...ackages/Discretization/src/DTK_PointSearch_def.hpp
100% <0%> (+1.26%)
:arrow_up:

Continue to review full report at Codecov.

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

I have updated the PR.  The user is now able to pass the desired size for the buffer optimization as an extra parameter when calling query().  The last thing to consider now is the policy.

From a user's perspective, it's probably better to call it an estimate (for the number of results per query), and not buffer size. Buffer seems to be an internal implementation.

Ready for review

Not sure what to think about these timings from my dev container but here it is:

cuda (K40)
--buffer=-50
--buffer=5
--buffer=0
w/o buffer optimization

construction
0.444047
0.443188
0.448707
0.443805

kNN
1.60538
1.61959
1.62235
1.59602

radius
0.467582
0.808872
0.830499
0.82421

These seem to indicate the attempt to reduce the cost when buffer_size == 0 is not working so great.  I might try on Condo to compare.

After talking with Bruno, decided to disable the buffer optimization by default.

Can't buffer_size = 2*sizeof(Stack) = 128? You will unapologetically throw anyway if you exceed stack capacity. And as nodes in stack are internal, each one has at most 2 leaves.
Also, one could use allocated memory for buffer for stack itself, so that instead of 364 it would just be 264.

Can't buffer_size = 2*sizeof(Stack) = 128?

It can be whatever you like.

You will unapologetically throw anyway if you exceed stack capacity. And as nodes in stack are internal, each one has at most 2 leaves.

I think you misunderstand how the tree is traversed.  The stack will not necessarily exceed capacity if you find say over 100 collisions.


Use lazy load hooks to hook on ActionController::Base

👋
Use lazy load hooks to hook on ActionController::Base

Calling directly ActionController::Base affects the initialization process (one of them being one that controls ActionController configuration)
As a result setting configuration inside an initializer (such as the asset_host), doesn't have any effect

cc/ @rafaelfranca @haani

Hi @Edouard-chin! Thank you for taking the time to put together this PR. We're accepting it and it will be included in our upcoming version 4.7 release. We really appreciate your help making the agent better for everyone!

Thanks !


Abstract step over proof systems

This PR changes the step prover to handle proofs from multiple proof systems.
This builds upon #8101.
Checklist:

[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

This work will be redone as part of customisable pickles. Closing as stale.


Help required for changing the icon for current location.

Hi guys,
I'm trying to use a custom image for the user's current location on the map. But the default pins are what shows for current location.
On the image attached, I have the blue pin showing me the current location.
I need to set a custom image instead of the blue pin.
Any help or suggestions are appreciated.
Thanks.

Suggestion:

Disable IsShowingUser.
Track User-Position. (https://github.com/jamesmontemagno/GeolocatorPlugin)
Add a Pin with an image at the current user-position.

Thanks man.
I have applied an image on the location, but the image size remains constant at all zoom levels.
The image should resize itself as and when the user zooms right?
And IsShowingUser doesnt remove the blue dot on the current location. How do I remove the (blue)location dot entirely?

No, pins never scale with the zoom level. If you want it to scale with the zoom level, you need to define an overlay. Currently images are not supported as overlay though. You can draw a TKCircle.
IsShowingUser = false should remove the dot. This a a XF.Maps default property. https://developer.xamarin.com/api/property/Xamarin.Forms.Maps.Map.IsShowingUser/

Thanks Torben. This fixed my problem.


Where can I find the tracker id ?

As the title says, where can I get the Tracker Id? Im a little bit confused on this part. I've connected Firebase with my PlayStore App so I can get analytics but I can't find that tracker id.

Hi. This library does not work with Firebase. You'll have to use Google Analytics.


bug(mat-slider): thumb label affected by parent word-break

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Upgraded to mdc based components and the sliders thumb label started looking like this:

found out the culprit to be a word-break: break-word; on one of the parent divs, not sure if this is intended
Reproduction
StackBlitz link: https://stackblitz.com/edit/components-issue-okzuyh?file=src%2Fapp%2Fexample-component.html
Steps to reproduce:

move slider thumb

Expected Behavior
slider thumb label shouldn't break on any parent having word-break
Actual Behavior
slider thumb label inherits word-break
Environment

Angular: 15.2.4
CDK/Material: 15.2.5
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

hey @gpaimla  I am happy to have a look at it and try to resolve it


Merge prTesting_202004141935 branch to master branch

Docs Build status updates of commit 52576b8:
:clock10: Pending: waiting for processors (9 builds ahead of you)
:warning: Docs Build is busy, currently there are 9 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 52576b8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestRef.md
:warning:Warning

Details

split/updateTestRef.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.
Line 1: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Gateway monitoring says link is down whereas link actually works (probably not OPNsense related)

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

The following bug has been noticed and experienced from OPNSense 24.1.6 to 24.1.10_3 (current).
I have a multi-WAN setup with two links.
As of today, I tend to use <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS> and <IP_ADDRESS> as monitor IP for gateway monitoring.
So far so good, my seconary WAN link seems down according to gateway monitoring:

Still, I can use the link, and can also ping via OPNSense interface/diagnostic page:

I have checked that the monitor IP <IP_ADDRESS> is not bound to any interface in DNS page:

Nor bound to in interface in the routing table:

Updating OPNSense and rebooting doesn't help.
Gateway monitor settings are pretty basic:

My ISP blocks ICMP pings to the gateway, hence the reason I use <IP_ADDRESS> as IP for gateway monitoring.
Is there any reason that the gateway is marked offline, whereas it can ping <IP_ADDRESS> ? Perhaps dpinger works like traceroute and doesn't like the fact that the first hop isn't pingable ?
[EDIT]
I can confirm that the gateway that is marked offline works, since a test from VM behind the OPNsense shows that the offline gateway is used (I'm using a rule with that explicit gateway):
curl 'http://api.ipify.org?format=json'
{"ip":"172.25.XX.XX"}

To Reproduce
Sorry, there's no reproducer that I can suggest here.
Expected behavior
Since OPNSense can ping <IP_ADDRESS> through the gateway which uses that IP as monitoring IP, I would expect the gateway to be online intead of offline.
Software version used and hardware type if relevant, e.g.:
OPNsense 24.1.10_3 (amd64) on KVM with virtio NICs

I realized that my above diagnostic is a bit botched.
So I added a rule forcing ICMP to use the offline marked gateway for one of my machines behind OPNSense.
From that machine, pinging <IP_ADDRESS> with that rule still works, so I can confirm that something isn't right with the way dpinger thinks my gateway is offline, when monitor IP is <IP_ADDRESS>.
I've also tried the following from the OPNsense console
Ping works
ping -S 172.25.XX.XX <IP_ADDRESS>

PING <IP_ADDRESS> (<IP_ADDRESS>) from <IP_ADDRESS>: 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=53 time=21.643 ms

Dpinger fails from my second WAN which is marked offline
dpinger -f -B 172.25.X.X -s 1s -l 4s -t 60s -d 1 <IP_ADDRESS>

send_interval 500ms  loss_interval 2000ms  time_period 60000ms  report_interval 1000ms  data_len 0  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr <IP_ADDRESS>  bind_addr 172.25.XX.XX identifier ""
0 0 0
0 0 100

But dpinger works from my primary WAN
dpinger -f -B 194.87.XX.XX  -s 1s -l 4s -t 60s -d <IP_ADDRESS>
send_interval 1000ms  loss_interval 4000ms  time_period 60000ms  report_interval 1000ms  data_len 1  alert_interval 1000ms  latency_alarm 0ms  loss_alarm 0%  alarm_hold 10000ms  dest_addr <IP_ADDRESS>  bind_addr 194.87.XX.XX  identifier ""
26746 0 0
26672 179 0
26722 92 0

Investigating further, it seems that when dpinger's payload is set to 1, it fails. If I set the payload to 4 or higher, it works.
I could confirm this by using ping:
The following works:
ping -S 172.25.XX.XX -s 4 <IP_ADDRESS>

The following doesn't;
ping -S 172.25.XX.XX -s 1 <IP_ADDRESS>

Playing with the packet size, I realized that every packet size between 4 and 172 bytes works, and others don't.
This only happens on the secondary link, the primary link accepts usual packet sizes.
So end of diagnostic: It seems that there's something fishy with the link itself, and not OPNSense.
Sorry for the noise.
I have yet to find what the problem is at my datacenter.
If anyone has a clue, I will gladly take it ;)

Please let me know if you found anything - I'm having the exact same problem but only since 24.7 came along.

@dwkirw I've pushed the diagnostics. Whenever I use values for ping -s n where 4 <= n <= 172, I get to ping.
My datacenter guys told me that they have no filter whatsoever, but on the second link they provide I don't have that problem, so to be honest I doubt that this is an OPNSense problem.
Btw, I'm running OPNsense 24.1.10_3-amd64 on this unit, so I had this problem prior to 24.7.
What exactly is your problem ? Did you try adding a payload to the gateway monitor ? Does it work ?

Thank you - I've had a better read of what you wrote and tried some of the stuff.   Also, disregard the only on 24.7 thing - I've only had a backup WAN about 6 weeks and likely havent noticed this
I have not played around with dpinger before.
From the primary wan (which is currently marked as down) i get stuff such as this.
dpinger -f -B 139.5.x.x -s 1s -l 4s -t 60s -d 1 <IP_ADDRESS>
7650 0 0
7288 371 0
7370 316 0
7289 324 0
From backup (currently showing Online) i get this
dpinger -f -B <IP_ADDRESS> -s 1s -l 4s -t 60s -d 1 <IP_ADDRESS>
36686 0 0
33661 3030 0
35521 3611 0
34479 3608 0
My primary is PPPoE, its IP changes fairly often.  Heres its settings. The IP has been left blank for this reason.
.
While the primary wan is appearing to be down but still working if i go to System>Configuration>Gateways and hit the Apply button it goes to Online again.    While its marked Offline my port forwards are flakey though sometimes working/not...
If you can see any dumb things I've missed or should try I'd appreciate knowing about them, ta!

It looks like the patch from issue #7027 is not included yet in 24.7.1? @fichtner ? I'm having a very similar issue, both with 24.1, as well as 24.7. Can reproduce like clockwork if needed.
It's happening with <IP_ADDRESS> as monitor host as well as the PPPOE connection's gateway. The IP given to dpinger -S is the correct one.

Here's some debug output:
root@OPNsense:~ # pluginctl -r return_gateways_status
{
    "dpinger": {
        "WAN_DHCP6": {
            "status": "none",
            "monitor": "~",
            "name": "WAN_DHCP6",
            "stddev": "~",
            "delay": "~",
            "loss": "~"
        },
        "WAN_PPPOE": {
            "status": "down",
            "monitor": "<IP_ADDRESS>",
            "name": "WAN_PPPOE",
            "stddev": "0.0 ms",
            "delay": "0.0 ms",
            "loss": "100.0 %"
        },
        "WAN_LTE_DHCP": {
            "status": "none",
            "monitor": "<IP_ADDRESS>",
            "name": "WAN_LTE_DHCP",
            "stddev": "5.8 ms",
            "delay": "1.4 ms",
            "loss": "0.0 %"
        }
    }
}

root@OPNsense:~ # ps auxf | grep dping
root    84723   0.0  0.1   17572  2780  -  Is   04:15      0:04.21 /usr/local/bin/dpinger -f -S -r 0 -i WAN_PPPOE -B 95.117.229.XXX -p /var/run/dpinger_WAN_PPPOE.pid -u /var/run/dpinger_WAN_PPPOE.sock -s 1s -l 4s -t 60s -d 1 <IP_ADDRESS>
root    90835   0.0  0.1   17572  2792  -  Is   19:57      0:14.78 /usr/local/bin/dpinger -f -S -r 0 -i WAN_LTE_DHCP -B <IP_ADDRESS> -p /var/run/dpinger_WAN_LTE_DHCP.pid -u /var/run/dpinger_WAN_LTE_DHCP.sock -s 1s -l 4s -t 60s -d 1 192

root@OPNsense:~ # pluginctl -c monitor
Setting up gateway monitors...done.

root@OPNsense:~ # ps auxf | grep dping
root    67987  10.6  0.1   13344  2716  -  Ss   06:59      0:00.01 /usr/local/bin/dpinger -f -S -r 0 -i WAN_LTE_DHCP -B <IP_ADDRESS> -p /var/run/dpinger_WAN_LTE_DHCP.pid -u /var/run/dpinger_WAN_LTE_DHCP.sock -s 1s -l 4s -t 60s -d 1 192
root    67240  10.4  0.1   13344  2716  -  Ss   06:59      0:00.01 /usr/local/bin/dpinger -f -S -r 0 -i WAN_PPPOE -B 95.117.229.XXX -p /var/run/dpinger_WAN_PPPOE.pid -u /var/run/dpinger_WAN_PPPOE.sock -s 1s -l 4s -t 60s -d 1 <IP_ADDRESS>

root@OPNsense:~ # pluginctl -r return_gateways_status
{
    "dpinger": {
        "WAN_DHCP6": {
            "status": "none",
            "monitor": "~",
            "name": "WAN_DHCP6",
            "stddev": "~",
            "delay": "~",
            "loss": "~"
        },
        "WAN_PPPOE": {
            "status": "none",
            "monitor": "<IP_ADDRESS>",
            "name": "WAN_PPPOE",
            "stddev": "119.4 ms",
            "delay": "49.2 ms",
            "loss": "0.0 %"
        },
        "WAN_LTE_DHCP": {
            "status": "none",
            "monitor": "<IP_ADDRESS>",
            "name": "WAN_LTE_DHCP",
            "stddev": "125.7 ms",
            "delay": "42.6 ms",
            "loss": "0.0 %"
        }
    }
}

And the general log:

2024-09-26T04:19:32	Error	dhclient	send_packet: Host is down
2024-09-26T04:18:23	Error	dhclient	send_packet: Host is down
2024-09-26T04:17:31	Error	dhclient	send_packet: Host is down
2024-09-26T04:16:09	Error	opnsense	/usr/local/etc/rc.newwanipv6: The command '/usr/sbin/daemon -f -p '/var/run/updaterrd.pid' '/var/db/rrd/updaterrd.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 10158'
2024-09-26T04:16:09	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync(,opt2))
2024-09-26T04:16:09	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do(,opt2))
2024-09-26T04:16:09	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : vxlan_configure_do())
2024-09-26T04:16:09	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do(,opt2))
2024-09-26T04:16:09	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : openssh_configure_do(,opt2))
2024-09-26T04:16:09	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do())
2024-09-26T04:16:09	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do())
2024-09-26T04:16:09	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : reset_failover_states(,opt2))
2024-09-26T04:16:08	Warning	igmpproxy	select() failure; Errno(4): Interrupted system call
2024-09-26T04:16:08	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : igmpproxy_configure_do())
2024-09-26T04:16:08	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2024-09-26T04:16:08	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (,opt2)
2024-09-26T04:16:08	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do(,opt2))
2024-09-26T04:16:08	Notice	opnsense	/usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface LAN_WLAN.
2024-09-26T04:16:08	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do(,opt2))
2024-09-26T04:16:08	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do(,opt2))
2024-09-26T04:16:08	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (,opt2)
2024-09-26T04:16:08	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync(,lan))
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do(,lan))
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : vxlan_configure_do())
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do(,lan))
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : openssh_configure_do(,lan))
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do())
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do())
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : reset_failover_states(,lan))
2024-09-26T04:16:06	Warning	igmpproxy	select() failure; Errno(4): Interrupted system call
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : igmpproxy_configure_do())
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2024-09-26T04:16:06	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (,lan)
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do(,lan))
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface LAN_SERVER.
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do(,lan))
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do(,lan))
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (,lan)
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync(,wan))
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do(,wan))
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : vxlan_configure_do())
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do(,wan))
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : openssh_configure_do(,wan))
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do())
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do())
2024-09-26T04:16:05	Error	opnsense	/usr/local/etc/rc.newwanipv6: Primary WAN pppoe0 change detected, killing states of failover WAN igb2_vlan22 / <IP_ADDRESS>
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : reset_failover_states(,wan))
2024-09-26T04:16:05	Warning	igmpproxy	select() failure; Errno(4): Interrupted system call
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : igmpproxy_configure_do())
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2024-09-26T04:16:05	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (,wan)
2024-09-26T04:16:04	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do(,wan))
2024-09-26T04:15:59	Warning	opnsense	/usr/local/etc/rc.newwanip: Interface '' (ovpns1) is disabled or empty, nothing to do.
2024-09-26T04:15:58	Notice	opnsense	/usr/local/etc/rc.newwanipv6: OpenVPN client 2 instance started on PID 37591.
2024-09-26T04:15:58	Notice	kernel	<6>ovpns1: link state changed to UP
2024-09-26T04:15:58	Notice	opnsense	/usr/local/etc/rc.newwanipv6: OpenVPN server 1 instance started on PID 33027.
2024-09-26T04:15:58	Notice	kernel	<6>ovpns1: link state changed to DOWN
2024-09-26T04:15:58	Notice	opnsense	/usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface WAN.
2024-09-26T04:15:58	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do(,wan))
2024-09-26T04:15:58	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure route_reload (execute task : core_routing_batch(,[]))
2024-09-26T04:15:58	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure route_reload (,[])
2024-09-26T04:15:55	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do(,wan))
2024-09-26T04:15:55	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (,wan)
2024-09-26T04:15:51	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: keeping inet6 default route to fe80::f6e4:51ff:fed3:bc97%pppoe0
2024-09-26T04:15:51	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: configuring inet6 default gateway on wan
2024-09-26T04:15:51	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: ignoring down gateways: WAN_PPPOE, WAN_LTE_DHCP, WARP_GWv6, WARP_GWv4
2024-09-26T04:15:51	Error	dhclient	send_packet: Host is down
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'opt2'
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: keeping inet6 default route to fe80::f6e4:51ff:fed3:bc97%pppoe0
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: configuring inet6 default gateway on wan
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: ignoring down gateways: WAN_PPPOE, WAN_LTE_DHCP, WARP_GWv6, WARP_GWv4
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'lan'
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_DHCP6))
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure monitor (,WAN_DHCP6)
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: keeping inet6 default route to fe80::f6e4:51ff:fed3:bc97%pppoe0
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: configuring inet6 default gateway on wan
2024-09-26T04:15:50	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: ignoring down gateways: WAN_PPPOE, WAN_LTE_DHCP, WARP_GWv6, WARP_GWv4
2024-09-26T04:15:49	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'wan'
2024-09-26T04:15:49	Warning	radvd	exiting, 1 sigterm(s) received
2024-09-26T04:15:48	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(,inet6))
2024-09-26T04:15:48	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure dhcp (,inet6)
2024-09-26T04:15:48	Notice	opnsense	/usr/local/etc/rc.newwanipv6: IP renewal starting (address: fe80::20d:b9ff:fe48:9070%pppoe0, interface: wan, device: pppoe0)
2024-09-26T04:15:45	Error	opnsense	/usr/local/etc/rc.newwanipv6: The command '/usr/sbin/daemon -f -p '/var/run/updaterrd.pid' '/var/db/rrd/updaterrd.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 32728'
2024-09-26T04:15:44	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync(,opt2))
2024-09-26T04:15:44	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do(,opt2))
2024-09-26T04:15:44	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : vxlan_configure_do())
2024-09-26T04:15:44	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do(,opt2))
2024-09-26T04:15:44	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : openssh_configure_do(,opt2))
2024-09-26T04:15:44	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do())
2024-09-26T04:15:44	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do())
2024-09-26T04:15:44	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : reset_failover_states(,opt2))
2024-09-26T04:15:43	Warning	igmpproxy	select() failure; Errno(4): Interrupted system call
2024-09-26T04:15:43	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : igmpproxy_configure_do())
2024-09-26T04:15:43	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2024-09-26T04:15:43	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (,opt2)
2024-09-26T04:15:42	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do(,opt2))
2024-09-26T04:15:42	Notice	opnsense	/usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface LAN_WLAN.
2024-09-26T04:15:42	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do(,opt2))
2024-09-26T04:15:42	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do(,opt2))
2024-09-26T04:15:42	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (,opt2)
2024-09-26T04:15:42	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync(,lan))
2024-09-26T04:15:41	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do(,lan))
2024-09-26T04:15:41	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : vxlan_configure_do())
2024-09-26T04:15:41	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do(,lan))
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : openssh_configure_do(,lan))
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do())
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do())
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : reset_failover_states(,lan))
2024-09-26T04:15:40	Warning	igmpproxy	select() failure; Errno(4): Interrupted system call
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : igmpproxy_configure_do())
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (,lan)
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do(,lan))
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface LAN_SERVER.
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do(,lan))
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do(,lan))
2024-09-26T04:15:40	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (,lan)
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync(,wan))
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do(,wan))
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: keeping inet6 default route to fe80::f6e4:51ff:fed3:bc97%pppoe0
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: configuring inet6 default gateway on wan
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: ignoring down gateways: WAN_PPPOE, WAN_LTE_DHCP, WARP_GWv6, WARP_GWv4
2024-09-26T04:15:39	Error	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: not a valid opt4 interface gateway address: 'missing'
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : vxlan_configure_do())
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: treating '<IP_ADDRESS>' as far gateway for '95.117.229.XXX/32'
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do(,wan))
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : openssh_configure_do(,wan))
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do())
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do())
2024-09-26T04:15:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: Primary WAN pppoe0 change detected, killing states of failover WAN igb2_vlan22 / <IP_ADDRESS>
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : reset_failover_states(,wan))
2024-09-26T04:15:39	Warning	igmpproxy	select() failure; Errno(4): Interrupted system call
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : igmpproxy_configure_do())
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure newwanip (,wan)
2024-09-26T04:15:39	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: entering configure using defaults
2024-09-26T04:15:38	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do(,wan))
2024-09-26T04:15:34	Error	opnsense	/usr/local/etc/rc.newwanip: The command '/usr/sbin/daemon -f -p '/var/run/updaterrd.pid' '/var/db/rrd/updaterrd.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 57282'
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : wireguard_sync(,wan))
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : webgui_configure_do(,wan))
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : vxlan_configure_do())
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,wan))
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : openssh_configure_do(,wan))
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : opendns_configure_do())
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : ntpd_configure_do())
2024-09-26T04:15:34	Error	opnsense	/usr/local/etc/rc.newwanip: Primary WAN pppoe0 change detected, killing states of failover WAN igb2_vlan22 / <IP_ADDRESS>
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : reset_failover_states(,wan))
2024-09-26T04:15:34	Warning	igmpproxy	select() failure; Errno(4): Interrupted system call
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : igmpproxy_configure_do())
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dnsmasq_configure_do())
2024-09-26T04:15:34	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure newwanip (,wan)
2024-09-26T04:15:33	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : wireguard_configure_do(,wan))
2024-09-26T04:15:29	Warning	opnsense	/usr/local/etc/rc.newwanip: Interface '' (ovpns1) is disabled or empty, nothing to do.
2024-09-26T04:15:29	Notice	opnsense	/usr/local/etc/rc.newwanipv6: OpenVPN client 2 instance started on PID 40848.
2024-09-26T04:15:28	Notice	kernel	<6>ovpns1: link state changed to UP
2024-09-26T04:15:27	Notice	opnsense	/usr/local/etc/rc.newwanipv6: OpenVPN server 1 instance started on PID 28432.
2024-09-26T04:15:27	Notice	kernel	<6>ovpns1: link state changed to DOWN
2024-09-26T04:15:27	Notice	opnsense	/usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface WAN.
2024-09-26T04:15:27	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do(,wan))
2024-09-26T04:15:27	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure route_reload (execute task : core_routing_batch(,[]))
2024-09-26T04:15:27	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure route_reload (,[])
2024-09-26T04:15:24	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do(,wan))
2024-09-26T04:15:24	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure vpn (,wan)
2024-09-26T04:15:22	Warning	opnsense	/usr/local/etc/rc.newwanip: Interface '' (ovpns1) is disabled or empty, nothing to do.
2024-09-26T04:15:22	Notice	opnsense	/usr/local/etc/rc.newwanip: OpenVPN client 2 instance started on PID 94442.
2024-09-26T04:15:21	Notice	kernel	<6>ovpnc2: link state changed to DOWN
2024-09-26T04:15:21	Notice	kernel	<6>ovpns1: link state changed to UP
2024-09-26T04:15:21	Notice	opnsense	/usr/local/etc/rc.newwanip: OpenVPN server 1 instance started on PID 84548.
2024-09-26T04:15:21	Notice	kernel	<7>cannot forward src fe80:2::81bc:8d60:3c1b:248b, dst 2a02:3100:a106:ea23:20d:b9ff:YYYY:XXXX, nxt 58, rcvif igb1, outif pppoe0
2024-09-26T04:15:21	Notice	kernel	<6>ovpns1: link state changed to DOWN
2024-09-26T04:15:20	Notice	opnsense	/usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
2024-09-26T04:15:20	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do(,wan))
2024-09-26T04:15:20	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure route_reload (execute task : core_routing_batch(,[]))
2024-09-26T04:15:20	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure route_reload (,[])
2024-09-26T04:15:20	Notice	kernel	<7>cannot forward src fe80:2::81bc:8d60:3c1b:248b, dst 2a02:3100:a106:ea23:20d:b9ff:YYYY:XXXX, nxt 58, rcvif igb1, outif pppoe0
2024-09-26T04:15:19	Notice	kernel	<7>cannot forward src fe80:2::81bc:8d60:3c1b:248b, dst 2a02:3100:a106:ea23:20d:b9ff:YYYY:XXXX, nxt 58, rcvif igb1, outif pppoe0
2024-09-26T04:15:17	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: keeping inet6 default route to fe80::f6e4:51ff:fed3:bc97%pppoe0
2024-09-26T04:15:17	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: configuring inet6 default gateway on wan
2024-09-26T04:15:17	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: ignoring down gateways: WAN_PPPOE, WAN_LTE_DHCP, WARP_GWv6, WARP_GWv4
2024-09-26T04:15:17	Error	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: not a valid opt4 interface gateway address: 'missing'
2024-09-26T04:15:17	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: treating '<IP_ADDRESS>' as far gateway for '95.117.229.XXX/32'
2024-09-26T04:15:17	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do(,wan))
2024-09-26T04:15:17	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure vpn (,wan)
2024-09-26T04:15:17	Notice	opnsense	/usr/local/etc/rc.newwanip: IP address change detected, killing states of old ip <IP_ADDRESS>
2024-09-26T04:15:16	Notice	opnsense	/usr/local/etc/rc.routing_configure: ROUTING: entering configure using defaults
2024-09-26T04:15:16	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: keeping inet6 default route to fe80::f6e4:51ff:fed3:bc97%pppoe0
2024-09-26T04:15:16	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: configuring inet6 default gateway on wan
2024-09-26T04:15:16	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: ignoring down gateways: WAN_PPPOE, WAN_LTE_DHCP
2024-09-26T04:15:15	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'opt2'
2024-09-26T04:15:15	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: keeping inet6 default route to fe80::f6e4:51ff:fed3:bc97%pppoe0
2024-09-26T04:15:15	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: configuring inet6 default gateway on wan
2024-09-26T04:15:15	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: ignoring down gateways: WAN_PPPOE, WAN_LTE_DHCP
2024-09-26T04:15:14	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'lan'
2024-09-26T04:15:14	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_DHCP6))
2024-09-26T04:15:14	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure monitor (,WAN_DHCP6)
2024-09-26T04:15:14	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: keeping inet6 default route to fe80::f6e4:51ff:fed3:bc97%pppoe0
2024-09-26T04:15:14	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: configuring inet6 default gateway on wan
2024-09-26T04:15:14	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: ignoring down gateways: WAN_PPPOE, WAN_LTE_DHCP
2024-09-26T04:15:14	Notice	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'wan'
2024-09-26T04:15:14	Warning	radvd	exiting, 1 sigterm(s) received
2024-09-26T04:15:13	Warning	opnsense	/usr/local/etc/rc.newwanipv6: dhcpd_radvd_configure(manual) found no suitable IPv6 address on opt2(igb2_vlan59)
2024-09-26T04:15:13	Notice	dhcp6c	dhcp6c_script: REQUEST on pppoe0 renewal
2024-09-26T04:15:13	Warning	opnsense	/usr/local/etc/rc.newwanipv6: dhcpd_radvd_configure(manual) found no suitable IPv6 address on lan(igb1)
2024-09-26T04:15:13	Notice	dhcp6c	dhcp6c_script: REQUEST on pppoe0 executing
2024-09-26T04:15:13	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(,inet6))
2024-09-26T04:15:13	Notice	opnsense	/usr/local/etc/rc.newwanipv6: plugins_configure dhcp (,inet6)
2024-09-26T04:15:13	Notice	opnsense	/usr/local/etc/rc.newwanipv6: IP renewal starting (address: fe80::20d:b9ff:fe48:9070%pppoe0, interface: wan, device: pppoe0)
2024-09-26T04:15:11	Notice	dhcp6c	RTSOLD script - Sending SIGHUP to dhcp6c
2024-09-26T04:15:11	Notice	opnsense	/usr/local/etc/rc.newwanip: Chose to bind WAN_PPPOE on 95.117.229.XXX since we could not find a proper match.
2024-09-26T04:15:11	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_PPPOE))
2024-09-26T04:15:11	Notice	opnsense	/usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_PPPOE)
2024-09-26T04:15:11	Notice	opnsense	/usr/local/etc/rc.newwanip: ROUTING: ignoring down gateways: WAN_PPPOE, WAN_LTE_DHCP
2024-09-26T04:15:11	Notice	opnsense	/usr/local/etc/rc.newwanip: ROUTING: treating '<IP_ADDRESS>' as far gateway for '95.117.229.XXX/32'
2024-09-26T04:15:10	Notice	opnsense	/usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
2024-09-26T04:15:10	Notice	dhcp6c	RTSOLD script - Sending SIGHUP to dhcp6c
2024-09-26T04:15:10	Notice	opnsense	/usr/local/etc/rc.newwanip: IP renewal starting (new: 95.117.229.XXX, old: 77.7.62.X, interface: wan, device: pppoe0, force: yes)
2024-09-26T04:15:09	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure dns (execute task : unbound_configure_do(1))
2024-09-26T04:15:09	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure dns (execute task : dnsmasq_configure_do(1))
2024-09-26T04:15:09	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure dns (1)
2024-09-26T04:15:08	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(1))
2024-09-26T04:15:08	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure dhcp (1)
2024-09-26T04:15:08	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure route_reload (execute task : core_routing_batch(1,[]))
2024-09-26T04:15:08	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure route_reload (1,[])
2024-09-26T04:15:05	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure ipsec (execute task : ipsec_configure_do(1,wan))
2024-09-26T04:15:05	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure ipsec (1,wan)
2024-09-26T04:15:05	Warning	opnsense	/usr/local/etc/rc.configure_interface: The required WAN_PPPOE IPv4 interface address could not be found, skipping.
2024-09-26T04:15:05	Warning	opnsense	/usr/local/etc/rc.configure_interface: Skipping gateway WAN_PPPOE due to empty 'gateway' property.
2024-09-26T04:15:05	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure monitor (execute task : dpinger_configure_do(1,WAN_PPPOE))
2024-09-26T04:15:05	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure monitor (1,WAN_PPPOE)
2024-09-26T04:15:05	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure monitor (execute task : dpinger_configure_do(1,WAN_DHCP6))
2024-09-26T04:15:05	Notice	opnsense	/usr/local/etc/rc.configure_interface: plugins_configure monitor (1,WAN_DHCP6)
2024-09-26T04:15:05	Notice	opnsense	/usr/local/etc/rc.configure_interface: ROUTING: ignoring down gateways: WAN_LTE_DHCP
2024-09-26T04:15:05	Warning	opnsense	/usr/local/etc/rc.configure_interface: ROUTING: refusing to set interface route on addressless wan(pppoe0)
2024-09-26T04:15:05	Notice	opnsense	/usr/local/etc/rc.configure_interface: ROUTING: entering configure using 'wan'
2024-09-26T04:15:04	Notice	kernel	<6>ng0: changing name to 'pppoe0'
2024-09-26T04:15:04	Warning	rtsold	<rtsock_input_ifannounce> interface ng0 removed
2024-09-26T04:15:04	Warning	rtsold	<rtsock_input_ifannounce> interface pppoe0 removed
2024-09-26T04:15:03	Notice	opnsense	/usr/local/etc/rc.newwanip: Failed to detect IP for interface wan

Looking at https://github.com/dennypage/dpinger/blob/master/dpinger.c#L366 I wonder if this shouldn't be fixed directly in dpinger? As long as dpinger is running as root, it should be possible to either re-bind() or re-create the socket.

@KiNgMaR the patch is included and the cron job can fix the issue as it happens. However, we've been unable to find a good fix in the core for dpinger being stuck. A SIGHUP to rebind would be nice there, but the trigger for it is elusive. We're suspecting pf states may play a role here, because normally dpinger is able to recover (except maybe in the pppoe case but then it should also restart by default which it does). It's all entirely unclear in the grand scheme of things.

@fichtner I ran reproduce with nearly 100% "success" rate, let me know if you want to debug together.

@KiNgMaR Good, can you look up the states for the stuck gateway monitor and try to clear them o see if that helps it to recover on its own?

@fichtner not sure if this response is better in her or in #7027 but you are mentioning states here :)
For context I've just set up a Mikrotik LTE router in passthrough mode for Multi WAN failover and see this issue every time the 4g Connection drops and reconnects, at which time the interface in OPNSense gets a new IP.  Restarting the gateway monitoring fixes it.  I looked at the state table and this is what I found.
Just after reconnection while the monitor is showing 100% packet loss :
root@opnsense:~ # pfctl -s states -vv | grep <IP_ADDRESS> -A3
No ALTQ support in kernel
ALTQ related functions disabled
all icmp [<IP_ADDRESS>:12671](http://<IP_ADDRESS>:12671/) -> [<IP_ADDRESS>:12671](http://<IP_ADDRESS>:12671/)       0:0
   age 00:01:44, expires in 00:00:09, 104:0 pkts, 3016:0 bytes, rule 104, allow-opts
   id: f1bd926800000000 creatorid: 829fe43d route-to: <IP_ADDRESS>@vlan04
   origif: vlan04

if I then remove this state the monitor starts working without needing restarted and the entry in the state table gets recreated as :
root@opnsense:~ # pfctl -s states -vv | grep <IP_ADDRESS> -A3
No ALTQ support in kernel
ALTQ related functions disabled
all icmp [<IP_ADDRESS>:12671](http://<IP_ADDRESS>:12671/) -> [<IP_ADDRESS>:12671](http://<IP_ADDRESS>:12671/)       0:0
   age 00:00:06, expires in 00:00:09, 6:6 pkts, 174:174 bytes, rule 104, allow-opts
   id: e6c5926800000000 creatorid: 829fe43d route-to: <IP_ADDRESS>@vlan04
   origif: vlan04

note the route-to has changed ... in the first one it is the old gateway ip and in the 2nd one it is the new gateway ip.
Hope that gives you something to work with.

@LucidityCrash Looks related to my other issue in https://github.com/opnsense/core/issues/7637

@LucidityCrash best fit seems #7027 indeed.  Looks like route-to sends to the old gateway which makes this fail permanently until the state is flushed. Thanks a lot for this piece of the puzzle. Let me see if that state can be targeted.

@LucidityCrash is rule 104 one of your rules? Or at least a route where you added the gateway (route-to) yourself? Does it point to a gateway group or a single gateway?

@LucidityCrash can you try this patch? 73e837d7d3
# opnsense-patch 73e837d7d3

@LucidityCrash is rule 104 one of your rules? Or at least a route where you added the gateway (route-to) yourself? Does it point to a gateway group or a single gateway?

Not an expert but :
the rule is :
@104 pass out route-to (vlan04 <IP_ADDRESS>) inet from (vlan04:1) to ! (vlan04:network:1) flags S/SA keep state allow-opts label "dca43ea815d5974296ad34b7b77d1f97"
  [ Evaluations: 84200     Packets: 4906      Bytes: 142274      States: 1     ]
  [ Inserted: uid 0 pid 72809 State Creations: 1     ]
  [ Last Active Time: Thu Nov  7 12:28:12 2024 ]

If I click on the link to the rule in the UI it takes me to the Firewall -> Settings -> Advanced -> Disable Forced Gateway option (which is unticked) so I believe is it an auto generated rule.

@LucidityCrash can you try this patch? 73e837d
# opnsense-patch 73e837d7d3

Not done that before, I'm currently running 24.7.5 and not on site, so a) can I apply this to a "not the latest" release, and b) will it require a reboot ?
I feel I should have updated to the latest before I added my comments but I found this bug while researching why the monitor didn't recover after a link reconnect and collected info and added it here without thinking straight :)
I should be able to update and test the patch properly tonight or tomorrow it that's OK.

"Firewall -> Settings -> Advanced -> Disable Forced Gateway" makes sense as the origin. So disabling this (all strings attached) would be a workaround.
Take your time. I believe this will require FreeBSD 14 / OPNsense 24.7 anyway. The change to pfctl is not that old.

Sorry for the possibly stupid question but can I double check my understanding of that option is ? Ticking this will result in it not adding the 3 rules (one for each of my WAN interfaces - ipv4 and ipv6 on the main one an just ipv4 on the backup) that say "if the source is the WAN interface and the destination is not the WAN network then send the traffic to the WAN Gateway".  This means that it will just use the system routing table only, other than not forcing all packets from the Backup_WAN interface to go via the Backup_WAN gateway are there any other downsides ?

In multi-WAN you want this behaviour in general so it's harder to switch the rules off although it only pertains to outgoing connections (and maybe outbound NAT). It really depends on your setup/requirements. For gateway monitoring you have a route ensuring that the right interface will be used on top of that either way.
What version are you on?
Cheers,
Franco

24.7.5

Hmm, I think 24.7.5 should patch just fine :)

Applied the patch ... as you say a 1 line difference ... didn't appear to help in my case

During the problematic WAN switch? The modem should reconnect and cause rc.newwanip logs to appear in the system log.

Log entries for a reconnect situation
<13>1 2024-11-07T15:04:25+00:00 opnsense.telinformix.com dhclient 95917 - [meta sequenceId="4267"] dhclient-script: Creating resolv.conf
<13>1 2024-11-07T15:04:41+00:00 opnsense.telinformix.com opnsense 99280 - [meta sequenceId="4268"] /usr/local/etc/rc.routing_configure: ROUTING: entering configure using defaults
<13>1 2024-11-07T15:04:41+00:00 opnsense.telinformix.com opnsense 99280 - [meta sequenceId="4269"] /usr/local/etc/rc.routing_configure: ROUTING: configuring inet default gateway on wan
<13>1 2024-11-07T15:04:41+00:00 opnsense.telinformix.com opnsense 99280 - [meta sequenceId="4270"] /usr/local/etc/rc.routing_configure: ROUTING: keeping inet default route to <IP_ADDRESS>
<13>1 2024-11-07T15:04:41+00:00 opnsense.telinformix.com opnsense 99280 - [meta sequenceId="4271"] /usr/local/etc/rc.routing_configure: ROUTING: configuring inet6 default gateway on wan
<13>1 2024-11-07T15:04:41+00:00 opnsense.telinformix.com opnsense 99280 - [meta sequenceId="4272"] /usr/local/etc/rc.routing_configure: ROUTING: keeping inet6 default route to fe80::aa7:41ff:feff:480c%igc0
<13>1 2024-11-07T15:04:41+00:00 opnsense.telinformix.com opnsense 99280 - [meta sequenceId="4273"] /usr/local/etc/rc.routing_configure: plugins_configure monitor (1,[])
<13>1 2024-11-07T15:04:41+00:00 opnsense.telinformix.com opnsense 99280 - [meta sequenceId="4274"] /usr/local/etc/rc.routing_configure: plugins_configure monitor (execute task : dpinger_configure_do(1,[]))
<13>1 2024-11-07T15:04:52+00:00 opnsense.telinformix.com opnsense 10667 - [meta sequenceId="4275"] /usr/local/etc/rc.routing_configure: ROUTING: entering configure using defaults
<13>1 2024-11-07T15:04:52+00:00 opnsense.telinformix.com opnsense 10667 - [meta sequenceId="4276"] /usr/local/etc/rc.routing_configure: ROUTING: ignoring down gateways: 4G
<13>1 2024-11-07T15:04:52+00:00 opnsense.telinformix.com opnsense 10667 - [meta sequenceId="4277"] /usr/local/etc/rc.routing_configure: ROUTING: configuring inet default gateway on wan
<13>1 2024-11-07T15:04:52+00:00 opnsense.telinformix.com opnsense 10667 - [meta sequenceId="4278"] /usr/local/etc/rc.routing_configure: ROUTING: keeping inet default route to <IP_ADDRESS>
<13>1 2024-11-07T15:04:52+00:00 opnsense.telinformix.com opnsense 10667 - [meta sequenceId="4279"] /usr/local/etc/rc.routing_configure: ROUTING: configuring inet6 default gateway on wan
<13>1 2024-11-07T15:04:52+00:00 opnsense.telinformix.com opnsense 10667 - [meta sequenceId="4280"] /usr/local/etc/rc.routing_configure: ROUTING: keeping inet6 default route to fe80::aa7:41ff:feff:480c%igc0
<13>1 2024-11-07T15:04:52+00:00 opnsense.telinformix.com opnsense 10667 - [meta sequenceId="4281"] /usr/local/etc/rc.routing_configure: plugins_configure monitor (1,[4G])
<13>1 2024-11-07T15:04:52+00:00 opnsense.telinformix.com opnsense 10667 - [meta sequenceId="4282"] /usr/local/etc/rc.routing_configure: plugins_configure monitor (execute task : dpinger_configure_do(1,[4G]))
<13>1 2024-11-07T15:05:26+00:00 opnsense.telinformix.com dhclient 5613 - [meta sequenceId="4283"] dhclient-script: Reason EXPIRE on vlan04 executing
<13>1 2024-11-07T15:05:26+00:00 opnsense.telinformix.com dhclient 10195 - [meta sequenceId="4284"] dhclient-script: Reason PREINIT on vlan04 executing
<13>1 2024-11-07T15:05:27+00:00 opnsense.telinformix.com kernel - - [meta sequenceId="4285"] <7>arpresolve: can't allocate llinfo for <IP_ADDRESS> on vlan04
<13>1 2024-11-07T15:05:27+00:00 opnsense.telinformix.com dhclient 12474 - [meta sequenceId="4286"] dhclient-script: Reason ARPSEND on vlan04 executing
<13>1 2024-11-07T15:05:27+00:00 opnsense.telinformix.com kernel - - [meta sequenceId="4287"] <7>arpresolve: can't allocate llinfo for <IP_ADDRESS> on vlan04
<13>1 2024-11-07T15:05:28+00:00 opnsense.telinformix.com kernel - - [meta sequenceId="4288"] <7>arpresolve: can't allocate llinfo for <IP_ADDRESS> on vlan04
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com dhclient 14022 - [meta sequenceId="4289"] dhclient-script: Reason ARPCHECK on vlan04 executing
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com dhclient 15391 - [meta sequenceId="4290"] dhclient-script: Reason BOUND on vlan04 executing
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com dhclient 19312 - [meta sequenceId="4291"] dhclient-script: New IP Address (vlan04): <IP_ADDRESS>
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com dhclient 20864 - [meta sequenceId="4292"] dhclient-script: New Subnet Mask (vlan04): <IP_ADDRESS>
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com dhclient 22572 - [meta sequenceId="4293"] dhclient-script: New Broadcast Address (vlan04): <IP_ADDRESS>
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com dhclient 24329 - [meta sequenceId="4294"] dhclient-script: New Routers (vlan04): <IP_ADDRESS>
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com dhclient 27032 - [meta sequenceId="4295"] dhclient-script: Creating resolv.conf
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4296"] /usr/local/etc/rc.newwanip: IP renewal starting (new: <IP_ADDRESS>, old: <IP_ADDRESS>, interface: opt3, device:
 vlan04, force: yes)
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4297"] /usr/local/etc/rc.newwanip: ROUTING: entering configure using opt3
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4298"] /usr/local/etc/rc.newwanip: ROUTING: ignoring down gateways: 4G
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4299"] /usr/local/etc/rc.newwanip: ROUTING: configuring inet default gateway on wan
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4300"] /usr/local/etc/rc.newwanip: ROUTING: keeping inet default route to <IP_ADDRESS>
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4301"] /usr/local/etc/rc.newwanip: plugins_configure monitor (,[4G])
<13>1 2024-11-07T15:05:29+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4302"] /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,[4G]))
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4303"] /usr/local/etc/rc.newwanip: IP address change detected, killing states of old ip <IP_ADDRESS>
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4304"] /usr/local/etc/rc.newwanip: plugins_configure vpn_map (,opt3,inet)
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4305"] /usr/local/etc/rc.newwanip: plugins_configure vpn_map (execute task : ipsec_configure_do(,opt3))
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4306"] /usr/local/etc/rc.newwanip: plugins_configure vpn_map (execute task : openvpn_configure_do(,opt3))
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4307"] /usr/local/etc/rc.newwanip: plugins_configure vpn_map (execute task : wireguard_configure_do())
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4308"] /usr/local/etc/rc.newwanip: plugins_configure vpn (,opt3)
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4309"] /usr/local/etc/rc.newwanip: plugins_configure newwanip (,opt3)
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4310"] /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,opt3))
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4311"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (,opt3,inet)
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4312"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : dhcrelay_configure_map(,opt3,inet))
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4313"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : dnsmasq_configure_do())
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4314"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : miniupnpd_configure_do())
<13>1 2024-11-07T15:05:30+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4315"] /usr/local/etc/rc.newwanip: miniupnpd: Starting service on interface: lan
<13>1 2024-11-07T15:05:31+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4316"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : ntpd_configure_do())
<13>1 2024-11-07T15:05:31+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4317"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : opendns_configure_do())
<13>1 2024-11-07T15:05:31+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4318"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : openssh_configure_do(,opt3))
<13>1 2024-11-07T15:05:31+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4319"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : vxlan_configure_do())
<13>1 2024-11-07T15:05:31+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4320"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : webgui_configure_do(,opt3))
<13>1 2024-11-07T15:05:31+00:00 opnsense.telinformix.com opnsense 28656 - [meta sequenceId="4321"] /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : wireguard_sync())
<13>1 2024-11-07T15:05:59+00:00 opnsense.telinformix.com dhclient 81000 - [meta sequenceId="4322"] dhclient-script: Reason RENEW on vlan04 executing
<13>1 2024-11-07T15:05:59+00:00 opnsense.telinformix.com dhclient 81884 - [meta sequenceId="4323"] dhclient-script: Creating resolv.conf
<13>1 2024-11-07T15:06:29+00:00 opnsense.telinformix.com dhclient 65497 - [meta sequenceId="4324"] dhclient-script: Reason RENEW on vlan04 executing
<13>1 2024-11-07T15:06:29+00:00 opnsense.telinformix.com dhclient 67181 - [meta sequenceId="4325"] dhclient-script: Creating resolv.conf
<13>1 2024-11-07T15:06:59+00:00 opnsense.telinformix.com dhclient 69806 - [meta sequenceId="4326"] dhclient-script: Reason RENEW on vlan04 executing
<13>1 2024-11-07T15:06:59+00:00 opnsense.telinformix.com dhclient 71790 - [meta sequenceId="4327"] dhclient-script: Creating resolv.conf
<13>1 2024-11-07T15:07:29+00:00 opnsense.telinformix.com dhclient 57041 - [meta sequenceId="4328"] dhclient-script: Reason RENEW on vlan04 executing
<13>1 2024-11-07T15:07:29+00:00 opnsense.telinformix.com dhclient 58240 - [meta sequenceId="4329"] dhclient-script: Creating resolv.conf
<13>1 2024-11-07T15:07:59+00:00 opnsense.telinformix.com dhclient 69402 - [meta sequenceId="4330"] dhclient-script: Reason RENEW on vlan04 executing
<13>1 2024-11-07T15:07:59+00:00 opnsense.telinformix.com dhclient 69994 - [meta sequenceId="4331"] dhclient-script: Creating resolv.conf
<13>1 2024-11-07T15:08:29+00:00 opnsense.telinformix.com dhclient 50529 - [meta sequenceId="4332"] dhclient-script: Reason RENEW on vlan04 executing

Ok, good. Make sure the change is still applied to the file and see what happens on the next reconnect. It looks like this will start working eventually :)

define eventually :) ... File is still the same (ie has the extra line in) ... forced a reconnect and the bad state entry is still there ... this kinda looks like a race condition.  It is almost as if the interface gets a new IP, the newwanip script runs removes any existing states then a new state entry is added (I'm assuming because dpinger is restarted and starts trying to ping the monitor address) with the new wan ip as the source but the old gateway ip as the route-to.

routes, monitors and filters are reloaded before the cache IP purge. Can you add a sleep before the 3 pfctl invokes? just a simple sleep(2);

fraid not ... I bumped that to 10 Seconds and still no luck though it did allow me to capture this from the states table :
root@opnsense:/var/log/system # pfctl -s states -vv | grep 8\.8\.4\.4 -A3
No ALTQ support in kernel
ALTQ related functions disabled
all icmp <IP_ADDRESS>:27599 -> <IP_ADDRESS>:27599       0:0
   age 00:00:27, expires in 00:00:07, 25:0 pkts, 725:0 bytes, rule 104, allow-opts
   id: f337966800000000 creatorid: 829fe43d route-to: <IP_ADDRESS>@vlan04
   origif: vlan04
--
all icmp <IP_ADDRESS>:46510 -> <IP_ADDRESS>:46510       0:0
   age 00:00:03, expires in 00:00:10, 3:0 pkts, 87:0 bytes, rule 104, allow-opts
   id: af38966800000000 creatorid: 829fe43d route-to: <IP_ADDRESS>@vlan04
   origif: vlan04

Just wanna add, sorry for the back and forth and thank you for your amazing support in trying to resolve this problem

Ah sorry we need to kill the old gateway not the old local IP (:

Sorry ... What does this mean with regards to how it is fixed ?

I’ll propose a patch in a bit. Needs more shuffling as the gateway is not cached yet.

Cool ... was just worried you expected me to understand what needed to be done ... I'm not that smart 😀

Neither am I, but anyway: 270aac573d9 applies on top of the other one
# opnsense-patch 270aac573d9

Cheers,
Franco

I updated to 24.7.8 this morining and applied those 2 patches.  The first time I forced a reconnection it didn't seem to work, and I removed the state entry manually.  I have since forced a reconnect multiple times and it has worked each time.
Thank you so much.

The first time not working is normal because it didn't cache the gateway IP yet :) This sounds great, thanks a lot for your debugging help!

I'll keep an eye out for it in a release ... looking at some of the threads in the forums there may be some happy users ... seemed to have hit a number of Starlink users in particular.

Starlink users always have issues from past experiences. ;)

Apparently #7027 isn't the same, but the overall patch looks ok to be introduced in 24.7.9 anyway. @deajan can you confirm as well?

Just to confirm I had an un forced reconnection last night and the new code handled it perfectly.  ( you never know there may have been a slight difference in the failure state comparec to the manually forced reconnect)

Applied those two patches eight days ago. And while I didn't have a maintenance window to properly do some exploration, the nightly re-connect of one of the WANs has been handled perfectly since - which didn't work before, dpinger would always get stuck. Thank you @fichtner! 💪

@KiNgMaR happy to hear, the change will hit 24.7.9 early this week :)

Just gave this a go and the gateway switched back once it came back up!! After months and months of frustration!!
Will continue to monitor but major improvement

thanks, going to close this then... already shipped


False positives

Deliberately using the wrong password and getting a false positive with it:
[+] Testing websites with one form (14)!
 -[   Vimeo   ] Login successful !  #<- No
 -[  Ask.fm   ] Login unsuccessful!
 -  Dropbox  form data is invalid! please report to us!
 -[  Github   ] Login successful ! #< Yes
 -[  Reddit   ] Login unsuccessful!
 -[  StackOF  ] Login unsuccessful!
 -[  Twitter  ] Login successful ! #<- No
 -[ Bitbucket ] Login successful !
 -[ Ebay.com  ] Login unsuccessful!
 -[ Facebook  ] Login unsuccessful!
 -[ FourSquare ] Login unsuccessful!
 -[ Linkedin  ] Login unsuccessful!
 -[ Mediafire ] Login successful ! #<- No
 -[ Wikipedia ] Login unsuccessful!

[+] Testing websites with two forms (2)!
 -[ Google ] Login unsuccessful!
 -[ Yahoo  ] Email not registered!

Second attempt:
[+] Testing websites with one form (14)!
 -[   Vimeo   ] Login successful !
 -[  Ask.fm   ] Login unsuccessful!
 -  Dropbox  form data is invalid! please report to us!
 -[  Github   ] Login unsuccessful!
 -[  Reddit   ] Login unsuccessful!
 -[  StackOF  ] Login unsuccessful!
 -[  Twitter  ] Login unsuccessful!
 -[ Bitbucket ] Login successful !
 -[ Ebay.com  ] Login unsuccessful!
 -[ Facebook  ] Login unsuccessful!
 -[ FourSquare ] Login unsuccessful!
 -[ Linkedin  ] Login unsuccessful!
 -[ Mediafire ] Login successful !
 -[ Wikipedia ] Login unsuccessful!

[+] Testing websites with two forms (2)!
 -[ Google ] Login unsuccessful!
 -[ Yahoo  ] Email not registered!

Same problem

Ok I will fix it ASAP

@D4Vinci thanks

In addition to the false positive that I came here to report, if you don't enter any password (because no breach results were found) then it not only reports a false positive for login to Vimeo but it also returns this error:
[+] Testing websites with one form (14)!
-[   Vimeo   ] Login successful !
-[  Ask.fm   ] Login unsuccessful!
Traceback (most recent call last):
File "./Cr3d0v3r.py", line 123, in
main()
File "./Cr3d0v3r.py", line 115, in main
print( login( wd ,dic ,email ,pwd ) )
File "./Cr3d0v3r.py", line 53, in login
browser.select_form(form)
File "/usr/local/lib/python3.6/dist-packages/mechanicalsoup/stateful_browser.py", line 170, in select_form
found_forms = self.__current_page.select(selector, limit=nr + 1)
AttributeError: 'NoneType' object has no attribute 'select'
Let me know if I should report this as a separate issue. The application should be able to fail gracefully if no password is entered.

updated to version 0.1.1 released yesterday and it won't crash

I used a random password and here are the results!
[+] Checking email in public leaks...

Results found : 1
---------------------------------------
      Name of leak => Dropbox
      Date of leakage => 2012-07-14T00:00:00+00:00
      Details => https://hacked-emails.com/leak/anon-dropbox68m2012txt

Please enter the password=>

[+] Testing websites with one form (14)!
 -[   Vimeo   ] Login successful !
 -[  Ask.fm   ] Login unsuccessful!
 -[  Dropbox  ] Login successful !
 -[  Github   ] Login unsuccessful!
 -[  Reddit   ] Login unsuccessful!
 -[  StackOF  ] Login unsuccessful!
 -[  Twitter  ] Login unsuccessful!
 -[ Bitbucket ] Login successful !
 -[ Ebay.com  ] Login unsuccessful!
 -[ Facebook  ] Login unsuccessful!
 -[ FourSquare ] Login unsuccessful!
 -[ Linkedin  ] Login unsuccessful!
 -[ Mediafire ] Login successful !
 -[ Wikipedia ] Login unsuccessful!

[+] Testing websites with two forms (2)!
 -[ Google ] Login unsuccessful!
Traceback (most recent call last):
  File "Cr3d0v3r.py", line 123, in <module>
    main()
  File "Cr3d0v3r.py", line 120, in main
    print( custom_login( wd ,dic ,email ,pwd ) )
  File "Cr3d0v3r.py", line 69, in custom_login
    browser.select_form(form2)
  File "/usr/local/lib/python3.5/dist-packages/mechanicalsoup/stateful_browser.py", line 170, in select_form
    found_forms = self.__current_page.select(selector, limit=nr + 1)
  File "/usr/lib/python3/dist-packages/bs4/element.py", line 1426, in select
    'Unsupported or invalid CSS selector: "%s"' % token)
ValueError: Unsupported or invalid CSS selector: "form[class="pure-form"

Yeah its just false positives I usually get them more at Mediafire, Linkedin BItbucket and Vimeo
but everything else is fine I dont get those errors that are commented in here I was trying to add new websites but can seem to add them correctly

Released Version 0.2 check it out and please reopen the issue if the problem continues 😄


Ensemble Square Root Updater

Here is my implementation of the Ensemble Square Root filter Updater which I presented at last year's Fusion Conference.
A full writeup of the algorithm itself, as well as design philosophy can be found in my paper titled "Implementation of Ensemble Kalman Filters in Stone Soup". The contribution here (in this particular pull request) is specifically a new updater. The predictor of the EnKF and EnSRF are shared, but the EnSRF assimilates measurements without adding noise which typically results in lower sampling error and thus higher accuracy.
One other thing to note. Is that this pull request also fixes issue #668 which caused both the EnsemblePredictor and the predict_measurement method in the EnKF (the latter of which is inherited by the EnSRF).

It should be noted that this pull request now includes the changes outlined in the discussion of Issue #668.
This include changes to numerous model classes, as well as the Partifle filter. Currently these changes only affect the Ensemble and Particle filters respectivley.


typescript(vx-legend): re-write package in TypeScript

:rocket: Enhancements
This PR builds off #488 which introduces Typescript build config, and re-writes the @vx/legend package in TypeScript.
This one was a bit gnarly vs some. Closes #546.
💥 Breaking Changes

This PR introduces React.Fragments, which requires bumping the peerDep for react to ^16.3.0-0
The following changes were made to the package directory structure which will affect deep import paths of components (importing from the index is unchanged):

src/legends/* => src/*

Tests

[x] CI
[x] functional /legend demo
[x] generates .d.ts files

Screen shots
Prod

Local

@hshoff  @kristw

woot! finally 😅


TypeScript conversion

What this PR does

Sets up basic package.json
Sets up ESLint for TypeScript
Sets up tsconfig.json
Converts all existing code into TypeScript

Notes
I'm hoping it was worthwhile to convert the entire SimpleAnnotationServerV2Adapter file to TS. It would also have been possible to leave it as JS and simply declare its import as an any type, and use it in our own TS that way. However, I do think it benefits from strong typing, to ensure it conforms to the respective annotation models.
The interfaces I defined for each model aren't exhaustive, of course—and I'm wondering if someone has already done the work of writing type declarations that actually conform exactly the standard. For now, they're implemented to the minimal possible extent to work with the existing code (while avoiding any types).
This did lead to some pretty big changes to SimpleAnnotationServerV2Adapter, so I think it may be worth reviewing. Since the diff isn't working on GitHub, you might need to pull it into your own diff checker.
While you look at this, I'll work on webpack so you can actually use this code!

I've set up a preliminary webpack config, built and successfully pulled in locally to geniza. However, I'm running into a curious problem. (Only realized this when I was setting id to an empty string at times.)
The original V2 adapter seems to do the following to convert v3 id into v2 @id:
https://github.com/Princeton-CDH/annotorious-sas-storage/blob/196dbd280be9552a04ca3b0410350c0943789aad/src/SimpleAnnotationServerV2Adapter.js#L98-L101
Otherwise, the v2 annotation's @id remains undefined. Therefore, I left @id as an optional property for v2 annotations.
But then, the original adapter can convert v2 to v3 as well. It does it in the following way, which implies that id could be undefined in a v3 annotation:
https://github.com/Princeton-CDH/annotorious-sas-storage/blob/196dbd280be9552a04ca3b0410350c0943789aad/src/SimpleAnnotationServerV2Adapter.js#L186-L193
Finally, in your code, we have:
    // delete an annotation
    anno.on("deleteAnnotation", (annotation: Annotation) => {
        adapter.delete(annotation.id);
    });

Which suggests id is a required property for a v3 annotation.
The question I have is, how should we define these ID properties? Should we insist that they are required for one or both of v3 and v2? In that case, how should we adjust the adapter code to ensure that they are never unset?

As a quick patch, if I do adapter.delete(annotation.id || ""); to make the typescript compiler happy (ensuring delete() is passed a string), the plugin works completely in geniza 😄

Which suggests id is a required property for a v3 annotation.
The question I have is, how should we define these ID properties? Should we insist that they are required for one or both of v3 and v2? In that case, how should we adjust the adapter code to ensure that they are never unset?

An annotation doesn't get an id until it is saved. So a new annotation wouldn't have one yet — but you could never delete one that doesn't have an id set.
I'm not sure if that answers how to resolve this; there must be patterns we can follow, though.


Wildcard Config Support

Relay from Twitter:
Please allow defining all blocks from a mod with mod:* in the config files :)

Hey, sorry i didnt see this when you posted it.  Probably too late for your pack but its in the latest update.  I just copied the formatter that cyclic uses so you can use either mod:* or even cyclicmagic:*_ore
https://minecraft.curseforge.com/projects/anger-management/files/2688252

Sweet, thanks!


Issue Age is Calculated incorrectly when a repository has 0 (Zero) issuse

Describe the bug
When there are no issues on a repo, the average age is calculated, which should not be the case. I think its simply a boundary condition.
At https://metrix.chaoss.io

This looks like the offending code:
        select
            avg(now() - i.created_at) as difference
        from
            augur_data.issues i,
            augur_data.repo r
        where
            r.repo_id in ({str(repolist)[1:-1]})
            and i.repo_id = r.repo_id
            and i.closed_at is not null

The average should be from the individual open date, and individual close date for each issue, and then those should be averaged.
Here's the file: 8Knot/pages/home/visualizations
/issue_metrics.py


Modify TermGPT to use .env file instead of .txt file.

Hmm, needs more work on the .env part I think. Might be willing to take this better approach with:
from dotenv import load_dotenv
load_dotenv()
In the main file, but I also like the ease of just using the text file heh.
If you can re-submit as 2 separate PRs as well, that'd be ideal.

requirements file + gitignore  (I can just accept this one)
the .env suggestion.  (I want to think more on how I really want this done).

I am not entirely certain how much longer I will be using GPT-4 or anything needing API keys, so I am not positive I want this change, but also I don't think it's really working with this PR.

Actually, a different PR did the .env the way I wanted and came with a requirements.txt and gitignore as well, so I've merged that one.


Replace db_handler to db_ctx_handler

Currently, main module uses the db_handler.
But db_handler is not designed for context switching...
Need to be changed to db_ctx_handler.

Done. :)


Create default role assignments for automatic sku

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
Create three default role assignments for automatic sku clusters.
az aks create -g -n --sku automatic
General Guidelines

[ X ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ X ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ X ] My extension version conforms to the Extension version schema

For new extensions:

[ X ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.


:memo: Document electron label in Contributing guide

This PR documents a new label, electron, which should make it clearer when Atom bugs / enhancement requests require changes in Electron to happen. :zap:
/cc @atom/issue-triage

:+1: Thanks for adding this


Minor tweaks + iOS compatibility

location is now an empty string if undefined.
Added METHOD:PUBLISH to iCal/Outlook.
Open iCal/Outlook download in same tab in mobile. The new tab was causing the "Add to Calendar" dialog to close immediately in iOS (always in 11.3 for me, sometimes in 11.4 for other people I had testing). Tested across a few different iPhones, iPads, and Android phones at my company and it seems to be working properly now.

Just made a tweak that adds support for IE11. Not sure if it worked before I made the iOS tweak but regardless, now it should work.
I'm having trouble running the tests locally as well as getting them to pass so I haven't committed any updates to the tests. :/

Whoops, sorry I forgot about the auto formatter 😅
Thanks for reviewing this; I'll run through this and make changes in the near future!


MINIBALL: Supplement the Miniball introductory doc

Supplement the Miniball introductory documentation, including design, architecture, steps to start the guest, getting started, and supported platforms.
ASOC: https://github.com/openanolis/dragonball-sandbox/issues/155
Signed-off-by: yaoyinnan<EMAIL_ADDRESS>

Thanks for your doc:)
I'll read that tomorrow~

I refer to vmm-reference to sort out the code of the guest startup process. As the project progresses, I will use the crates of dragonball-sandbox to replace the crates of rust-vmm mentioned in the document.


Warning about EF Core using shared IMemoryCache instance without specifying size is outdated

The warning at https://docs.microsoft.com/en-us/aspnet/core/performance/caching/memory?view=aspnetcore-5.0#use-imemorycache is very prominent in this page and uses EF Core as an example of a memory caching usage that can lead to problems, but the statements about EF Core are actually outdated.
See See https://docs.microsoft.com/en-us/ef/core/what-is-new/ef-core-3.x/breaking-changes#adddbc for the changes in EF Core 3.
Also, the paragraph seems to contain a bit of repetition.
cc @ajcvickers in case you want to follow up on what exactly changed and cannot find the answer in the previous link.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 13f5f8f9-18dd-9c12-9ed1-fcc6b44ba7fd
Version Independent ID: 640b4f36-5886-7b69-1c95-cfc8574a02fd
Content: Cache in-memory in ASP.NET Core
Content Source: aspnetcore/performance/caching/memory.md
Product: aspnet-core
Technology: aspnetcore-performance
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

See comment on PR: https://github.com/dotnet/AspNetCore.Docs/pull/22145#pullrequestreview-646248512


Create an account with this api

How can create an account with the api?

Any answer to this question yet?

I updated to new version. it is keep getting challenge_required error. any solution?

I added
ZSTD encode, sn_nonce, sn_result, still I am getting
Challenge required error.
I think it can be solved in real app, but it should not get with API


Is this project dead or alive?

Ever wonder why not one person has installed it since you uploaded it to the Chrome Store over 6 months ago?
Well the lack of a screenshot might not be the only reason,  but it may be the main reason.
And the fact that it no longer seems to be under development is another.
If it's dead, it should be removed from the C.S.

Hello there! You're right, this project isn't under active development. It could definitely be a more feature-rich extension. But I think that while the functionality is extremely simple, it still does one job well and I personally use it everyday. It seems that there're at least 46 other users (at the time of writing this) using it too.
Thanks for reminding me about the lack of marketing on the chrome web store. I'm actually a little stuck on this - do you have any suggestions on how I could capture the idea of shifting tabs via a screenshot?
Cheers mate! :beer:

I don't use the app so I can't help - I've never even seen it since there are no screenshots.
Yesterday I was browsing for extensions to rearrange/organize tabs when your listing came up.


Template generation writes to start location, not output dir

Since makita's render_jobs_basic is directory agnostic, setting an output dir has no influence on where files are written to.

Solved in v0.2