text selection reacts only to SelectableText bounds

on web you can start/remove selection from any place of the page
in flutter you have to put the cursor directly into the bounds of SelectableText to start selection
and you can't tap outside it to cancel the selection as well - you have to click to another Selectable Text

code sample
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      home: Scaffold(
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: [
            SelectableText('''
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  '''       ),
              Text("you can't deselect by tapping me"),
              ElevatedButton(onPressed: () {}, child: Text('or me')),
              Text("or any other on page except SelectableText\n"),
              SelectableText('''
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  loooooooooooooooooooooooooooooong selectable text
  '''       ),
            ],
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[√] Flutter (Channel nt4f04und, 2.1.0-13.0.pre.192, on Microsoft Windows [Version 10.0.19041.867], locale ru-RU)
    • Flutter version 2.1.0-13.0.pre.192 at c:\dev\src\flutter
    • Framework revision c0bcb4fc16 (4 days ago), 2021-03-19 16:34:57 -0700
    • Engine revision e6db3a275e
    • Dart version 2.13.0 (build 2.13.0-149.0.dev)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\danya\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.7.7)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.7.30621.155
    • Windows 10 SDK version 10.0.18362.0

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 50.0.1
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.54.3)
    • VS Code at C:\Users\danya\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.20.0

[√] Connected device (4 available)
    • Redmi Note 5 (mobile) • 40c9f14 • android-arm64  • Android 9 (API 28)
    • Windows (desktop)     • windows • windows-x64    • Microsoft Windows [Version 10.0.19041.867]
    • Chrome (web)          • chrome  • web-javascript • Google Chrome 89.0.4389.90
    • Edge (web)            • edge    • web-javascript • Microsoft Edge 89.0.774.57

• No issues found!

https://user-images.githubusercontent.com/39104740/112228509-75fa4c00-8c42-11eb-92ae-5deb8d72fdaa.mp4
https://user-images.githubusercontent.com/39104740/112228615-a215cd00-8c42-11eb-9ec4-6eb89e639e2e.mp4

I'd like to also add that using a MacBook, I'm quite used to  "tripple clicking" a paragraph and have it the entire paragraph be fully selected.
This does not currently work in Flutter web.
Thanks!

https://user-images.githubusercontent.com/67046386/112278654-12efd000-8ca9-11eb-813c-77bbb20cb6c4.mov

flutter doctor -v

[✓] Flutter (Channel stable, 2.0.3, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.0.3 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 4d7946a68d (5 days ago), 2021-03-18 17:24:33 -0700
    • Engine revision 3459eb2436
    • Dart version 2.12.2

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.54.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.20.0

[✓] Connected device (3 available)
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                               •
      web-javascript • Google Chrome 89.0.4389.90

! Doctor found issues in 1 category.

@marwan-at-work what you are talking about is tracked in https://github.com/flutter/flutter/issues/63576

This is not web-specific, so removing the label.

the behavior of where selection an be started differs on different platforms, for example i don't think fully web-like selection would be appropriate for desktops
cancellation behavior appears to be the same on all platforms

cc @gspencergoog

@HansMuller who is working on selectable text these days?

CC @chunhtai

How is this proposal progressing?

Duplicate of https://github.com/flutter/flutter/issues/72029

@nt4f04uNd is this really a duplicate of #72029? The issue description focuses on mobile and I agree that the issues should be very similar, but as we know the text selection on web vs. mobile on Flutter is implemented entirely differently.

They are both about web (the other issue is more about mobile behavior), but yeah, let's keep this one open to be sure both are properly fixed.


fix: base32 for ipfs:// urls and cidv1 everywhere

make POST return a base32 encoded cidv1. (it was returning bsae36 which is valid, but surprising)
default to using cidv1 everywhere.
update to use the new ipfs-core module.

base36 is the right thing to use to respect the max authority length for ipns:// scheme urls.
The assumption is folks should use base32 for CIDs in ipfs:// scheme urls, and it's the default output for cidv1.
The new ipfs-core modules has the same api as the ipfs module but doesn't include the cli and http-server code with it.
At time of writing the tests pass apart from the last one, which hangs. I think it's due to an unrelated bug https://github.com/ipfs/js-ipfs/issues/3692
License: MIT
Signed-off-by: Oli Evans<EMAIL_ADDRESS>

I'll chase down https://github.com/ipfs/js-ipfs/issues/3692 when i get time and see if I can get that unrelated test hang fixed.

Thanks for the clarifications, @lidel!

Published in 2.0.0 since this changes how URLs work. Thanks again for the PR and thanks @lidel for the clarification.

🎉 what a nice thread to wake up to! Thanks @lidel and lovely work on this module @RangerMauve !


kubectl proxy --accept-hosts appears to filter destination, not source.

Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT
Kubernetes version:

Client: v1.8.3
Server: v1.7.8-gke.0

Environment:

Cloud provider: Google [GKE]
OS:

Client: CentOS 6/7 [client]
Server: cos-stable-61-9765-66-0

Install tools: gcloud

What happened:
In my development VM [<IP_ADDRESS>] I started kubectl proxy to provide full access to the Dashboard UI to my workstation [<IP_ADDRESS>], but not everyone else in the office. The command used was:
kubectl proxy --port=8080 --address=<IP_ADDRESS> --accept-hosts='^10\.0\.2\.200$'

as well as many variants of the regular expression with/without \., ^, and $
Which yielded the following for all endpoints:

Unauthorized

It was suggested in the #kubernetes-users Slack channel that it may be running the regex against a hostname, but I've double-checked and we do not have reverse lookups enabled for our network, and I don't think that kubectl would be looking up NetBIOS info.
It can be made to work with --accept-hosts='^.*$' as you would expect, however I also decided to try --accept-hosts='^10\.0\.1\.100$' on a hunch, which ended up working the same as the wildcard, allowing anyone on the network access to the proxy.
What you expected to happen:

--accept-hosts='^10\.0\.2\.200$' should allow only the stated IP access to the proxy.

actual: universal inaccessibility

--accept-hosts='^10\.0\.1\.100$' should allow only local requests, similar to the <IP_ADDRESS> defaults.

actual: open access to all

How to reproduce it:
With two hosts attached to the same network:

Host A: kubectl proxy --port=8080 --address=HOST_A_IP --accept-hosts='^HOST_B_IP$'
Host B: curl http://HOST_A_IP:8080/

Anything else we need to know:
This has wider implications than me simply being paranoid about my local network. In searching for solutions to this problem I found pages upon pages of people stating --accept-hosts='^.*$' and --disable-filter=true as general solutions, even in the face of machines with public-facing interfaces. The supposed workarounds for this issue are causing people to unwittingly expose very sensitive information and APIs to potentially the entire world unless they take additional action to prevent it, eg: firewall rules.
eg: See the discussion in https://github.com/kubernetes/dashboard/issues/692

I don't know who knows about proxy. @liggitt ?

/remove-lifecycle rotten

/remove-lifecycle stale

/remove-lifecycle stale


Sound issues

What happened?
For some reason, I can't hear attack sounds from melee weapons and fists. Even the horse galloping is very wonky and can only be heard once every 8 seconds. I'm not sure if it's a faulty install or if some mod is overwriting the sounds incorrectly. Is it because I'm playing a male character? I noticed that everyone that has uploaded gameplay of this modpack only plays female characters.
Modlist version
Latest one.

unlikely anything to do with the modlist, plenty of people play male characters without reporting this issue. This may help:
https://www.nexusmods.com/skyrimspecialedition/mods/71567/

You're a genius. Thank you so much. I never would have solved this issue in a thousand years.


[Feature] allow configure date_range popup open direction

Fixes #3776

A new inspection was created.

The inspection completed: No new issues

If that's a problem, I can submit a new PR to still default to down, but passing the configuration on to the field config?

@olipayne that would be the best of both worlds I think. So you can have one picker up and the other down if desired.
Thanks for the contribution :)
Best,
Pedro

Hey guys - sounds good, I totally agree to making auto the default. I have no idea why that isn't the default in the JS plugin itself, sounds like a no-brainer. But I may have an issue with the implementation. Please let me know if I understand this correctly.
Wouldn't this be better done in the PHP part, so that it's overridable?
To rephrase:

if we merge this PR as-is, where we do $configuration.drops = 'auto'; in JavaScript, even if the developer specifies in his addField() statement the date_range_options, and inside them drops would be up, it'll still be auto because it's basically ignored by the javascript;
if we define the drops option in the PHP at the top of the file, where the rest of the defaults are, the developer would be able to override this however he pleases;

    // make sure the datepicker configuration has at least these defaults
    $field['date_range_options'] = array_replace_recursive([
        'autoApply' => true,
        'startDate' => $start_default,
        'endDate' => $end_default,
+       'drops' => 'auto',
        'locale' => [
            'firstDay' => 0,
            'format' => config('backpack.base.default_date_format'),
            'applyLabel'=> trans('backpack::crud.apply'),
            'cancelLabel'=> trans('backpack::crud.cancel'),
        ],
    ], $field['date_range_options'] ?? []);

What do you guys think? Better in PHP or JS?
Cheers!

100% PHP, I think that's what @olipayne mean when he said passing the configuration on the field config!
@olipayne if you don't have time to do it, just let me know and I do it 👍
Best,
Pedro

Sorry if I wasn't clear, yes I'll be doing it exactly as you guys have described, happy to throw a PR your way later this week.

Excellent. Thank you @olipayne , much appreciated 🙏 Right now we're putting the finishing touches on a shiny new thing, so if you don't get to it... we'll probably get it done in the next bug fixing cycle in Backpack (a few weeks).
Cheers!

A new inspection was created.

opening a new one with everything in one

The inspection completed: No new issues


Inclusion of a Patient Dashboard

I would like to propose the idea for a dashboard for patients which is presently absent in the app. There are dashboards for the admin, doctors, labs etc but the inclusion of this feature would make the app more accessible from the patient side.The features would include:

Book an appointment from the list of available doctors.
Manage appointments, i.e., if there would be a change in the schedule of the doctor, it would be notified to the patients and a new appointment would be fixed.
Check-up reminders for patients.
Reminders for the refill of medicines.
Reports of checkups and imaging lab reports.

These are the basic features that would make the experience for the patients more convenient, however, more ideas and features would be appreciated to be worked upon.

Great ideas! What do you think about Signup feature for Patients? Currently patients are added only through dashboard. But if he/she has to book an appointment for the very first time, he/she must be able to Signup!

I think currently the core team is focused on Release 1.0 since the release date (April 1st) is approaching. These features might get included in next versions of the software.

I'm currently working on this issue. I approached it by creating a new route called patientrole.index.


Proxy WWW-Authenticate and Authorization

Graphity Client should work as a proxy and:

tunnel WWW-Authenticate sent by Linked Data server to the end-user's web browser
tunnel Authorization sent by the end-user's web browser to the Linked Data server

Also related to #49


Don't use bare except

Bare excepts are bad because they can catch BareExceptions, which you usually don't want to catch. Catching Exception is enough to fix this, but a more specific one would be better.

🙏


Restoring database in mac m1 Azure data studio for MSSql

Azure Data Studio Version: 1.48.0
OS Version: sonoma 14.5 (Mac m1)

Steps to Reproduce:

Restore button is disabled while restoring the AdventureWorks2022.bak database file in Azure database studio in macbook m1 chip.

Does this issue occur when all extensions are disabled?: Yes/No

same error


Make popup menus avoid display features

This PR makes popup menus avoid overlapping display features.
Here is an example of showing a popup menu on one of the screens, instead of the middle of the screen (where the example device has a display feature):

This is split from a larger PR for foldable support in order to make it easier to review (https://github.com/flutter/flutter/pull/77156).
Issues that will be fixed by this PR:

https://github.com/flutter/flutter/issues/49411

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

This was split from https://github.com/flutter/flutter/pull/92909 as popup menus have less in common with modal routes than I initially considered. @Piinks @goderbauer

cc @goderbauer for secondary review, please and thanks. :)

@andreidiaconu can you rebase this PR? It looks like the G testing shard is stuck here, and the un-sticking tool is not fixing it.

@andreidiaconu can you rebase this PR? It looks like the G testing shard is stuck here, and the un-sticking tool is not fixing it.

Rebased


Add user and password to mqtt input output

Adds user and password fields to config and uses them if present in setting up mqtt client, both for input and output.

Looks great, thanks @woosteln.


Refactor plugin manager to support well defined interfaces

Overview
TBD
References and additional details
const MyPluginOpportunities = RegisterDefiOpportunities({
  pluginId: plugin.id,
  groupId: plugin.groups.jar.id,
  category: CategoryType.TokenStaking,
  getPositions: () => DefiPositionType[],
  getBalances: () => DefiBalanceType[]
})

const MyPluginDepositScreen = RegisterDefiDepositView({
  pluginId: plugin.id,
  groupId: plugin.groups.jar.id,
  component: PluginDepositView,
})

const MyPluginDefiApi = RegisterDefiApi({
  pluginId: plugin.id,
  groupId: plugin.groups.jar.id,
  estimateApproveGas: () => {},
  estimateDepositGas: () => {},
  estimateWithdrawGas: () => {},
  allowance: () => {},
  getGasPrice: () => {},
  getTxReceipt: () => {},
  approve: () => {},
  deposit: () => {},
  withdraw: () => {}
})

registerPlugin({
  pluginId: plugin.id,
  providers: [
    MyPluginRoutes,
    MyPluginOpportunities,
    MyPluginDepositScreen,
    MyPluginDefiApi
  ]
})

pluginManager.renderDefiDeposit({ pluginId, groupId, category })

pluginManager.getOpportunities({ network })

Acceptance Criteria
TBD
Need By Date
Soon...
Screenshots/Mockups
No response
Estimated effort
Couple days

as per @reallybeard closing as stale


Proposal: Add StandardUICommand

Proposal: Add StandardUICommand
Summary
The StandardUICommand class is very useful. But it is impossible to add this to apps targeting older Windows versions. Using StandardUICommands for newer Windows versions plus manual commands for older versions would cause lots of extra code. It could also lead to inconsistent UI between old an new, because manual translations, shortcuts, etc might be different from the ones in StandardUICommand.
To be really useful, we need this class (along with XamlUICommand) in Microsoft.UI.Xaml. Only then it will be useful for a large number of apps.
Functional Requirements
Mandatory:

Support all values from StandardUICommandKind

Optionally include more commands:
Not sure how MS selects which commands are available. These are just some ideas. Some of those items could only provide a common translation, maybe an icon, which IMHO is still helpful. Devs would have to fill missing properties (description, icon, shortcut), so it matches their app. Docs would have to mention which properties are filled for each value.
This must be aligned with MS internal strategy/roadmap for the class.
General:

Search
Select (multi select button, e.g. in photos app)
Add
Remove
Export
Import
Edit
Start
Cancel
OpenFile
OpenFolder
Enable
Disable
Activate
Deactivate
Clear

Note: Sometimes, having a button to enable/activate a function is appropriate, e.g. if that function triggers long running actions. For those cases, I'd prefer a button over a checkbox/switch.
Media:

Cast To Device
Shuffle
Repeat
Skip forward
Skip backward
Fast forward
Fast backward
Fullscreen
Resize
Equalizer

@lukasf, I completely agree with your sentiment and this request is already in plan for WinUI 3. I'll close this issue because we don't need to keep track of this class separately, this is simply a part of lifted Xaml that's already on our roadmap.


typo: Span events: even > event

Typo on https://agardnerit.github.io/tracepusher/reference/span-events/ even should be `event
https://github.com/agardnerIT/tracepusher/blob/73025fc92cb6040d28550a945df6ac9965ec5d9a/docs/reference/span-events.md?plain=1#L23

Thanks for taking this on @viktoriussuwandi . Closing as the PR is merged.


mkpr

Applied mkpr on package.json
sed s/"@kronos-integration\/endpoint": "^.*"/"@kronos-integration\/endpoint": "^9.2.8"/

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1094   +/-   ##
=======================================
  Coverage   89.18%   89.18%
=======================================
  Files           7        7
  Lines         712      712
  Branches       77       77
=======================================
  Hits          635      635
  Misses         77       77

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 a12ded2...e52d52d. Read the comment docs.


Initializing Pre-Trained roadtracer

Hello!
Thank you so much for releasing RoadTracer it’s awesome! I’m really curious to try road tracer in new areas. I’ve been trying to work with the pre-trained mode, but I keep running into this error:
import tensorflow as tf

sess=tf.Session()
saver = tf.train.import_meta_graph('/home/ubuntu/roadtracer/roadtracer/model/model.meta')
saver.restore(sess,tf.train.latest_checkpoint('/home/ubuntu/roadtracer/roadtracer/model/'))`

NotFoundErrorTraceback (most recent call last)
<ipython-input-33-66ada43313aa> in <module>()
      2 #First let's load meta graph and restore weights
      3 saver = tf.train.import_meta_graph('/home/ubuntu/roadtracer/roadtracer/model/model.meta')
----> 4 saver.restore(sess,tf.train.latest_checkpoint('/home/ubuntu/roadtracer/roadtracer/model/'))

/home/ubuntu/anaconda/lib/python2.7/site-packages/tensorflow/python/training/saver.pyc in latest_checkpoint(checkpoint_dir, latest_filename)
   1855     v1_path = _prefix_to_checkpoint_path(ckpt.model_checkpoint_path,
   1856                                          saver_pb2.SaverDef.V1)
-> 1857     if file_io.get_matching_files(v2_path) or file_io.get_matching_files(
   1858         v1_path):
   1859       return ckpt.model_checkpoint_path

/home/ubuntu/anaconda/lib/python2.7/site-packages/tensorflow/python/lib/io/file_io.pyc in get_matching_files(filename)
    337           for single_filename in filename
    338           for matching_filename in pywrap_tensorflow.GetMatchingFiles(
--> 339               compat.as_bytes(single_filename), status)
    340       ]
    341

/home/ubuntu/anaconda/lib/python2.7/site-packages/tensorflow/python/framework/errors_impl.pyc in __exit__(self, type_arg, value_arg, traceback_arg)
    517             None, None,
    518             compat.as_text(c_api.TF_Message(self.status.status)),
--> 519             c_api.TF_GetCode(self.status.status))
    520     # Delete the underlying status object from memory otherwise it stays alive
    521     # as there is a reference to status from this from the traceback due to

NotFoundError: /data/discover-models/2018mar12-m4d-newreconnect//model_latest; No such file or directory

What version of tensorflow do you use? Do you know what I should do to initialize the pre-trained road tracer to avoid this error? Thanks you for your help.

@martham93  Hi Martha!
I ran into the same issue while trying to use the pre-trained model. I see you have closed the issue. Might you have any leads on how to fix it?
Thanks
Arpit

@arpitsri3 the checkpoint file has absolute paths that likely don't match the path where you put the model.
Can you try setting the path directly?
saver.restore(sess, '/home/ubuntu/roadtracer/roadtracer/model/model')


build all sub-projects within traffic_control

NOT ready for pulling in,  but I'd like feedback..   still requires more testing.  Top script is ./build/build.sh which invokes build/build_rpm.sh in each of the sub-projects.
traffic_monitor and traffic_router don't inherit version number (VERSION.txt) and build number isn't consistent, yet.

yes on functions.sh -- as I said,  I know that part was incomplete, but good enough to have you all have a look.     and --count isn't available on git installed by yum on Centos 6.[56] -- that's why I used that method instead.

Ah, that makes sense RE the git versions on CentOS.

really good feedback..   thanx..

Overall this looks very good. Definitely moving in the right direction.

will open new pull request after updating..


docs: add python code sample to multiple timeseries forecasting

BEGIN_COMMIT_OVERRIDE
docs: Add python code sample for multiple forecasting time series (#531)
END_COMMIT_OVERRIDE
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Corrected region tags, will be updated on next PR!

e2e tests failed with
FAILED tests/system/large/ml/test_core.py::test_bqml_e2e - AssertionError: Da...
FAILED tests/system/large/ml/test_ensemble.py::test_xgbregressor_default_params
FAILED tests/system/large/ml/test_pipeline.py::test_pipeline_random_forest_classifier_fit_score_predict
FAILED tests/system/large/ml/test_pipeline.py::test_pipeline_xgbregressor_fit_score_predict

which appear to be unrelated.


feat: add ability to log benchq params to mlflow

Description
Include description of feature this PR introduces or a bug that it fixes. Include the following information:

Context: Users often want to track and share information about and resulting from benchq resource estimates. mlflow is a good tool for that.
In order to make it easier for users to log the values they care about to mlflow, new helper functions are added for logging input objects (AlgorithmImplementation, BasicArchitectureModel, and DecoderModel) to mlflow, as well as logging info from the output ResourceInfo object)
mlflow is added as a dependency. This is needed in order to be able to call mlflow logging functions

Please verify that you have completed the following steps

[x] I have self-reviewed my code.
[x] I have included test cases validating introduced feature/fix.
[x] I have updated documentation. (new example added showing use of the functions)

Looks good! I was able to run the example and see the experiments in mlflow.
Left a few minor comments. Also since there is already is an example 6, we should rename this to example 7.

Oh that example must have gotten added recently! Changed to 7 in 0cb9d646fb82f9c4f5add0f7ad8411a7f40b9a3c


HDFS-16721.Improve the check code of the important configuration item “dfs.client.socket-timeout”.

Description of PR
"dfs.client.socket-timeout" as the default timeout value for all sockets is applied in multiple places, it is a configuration item with significant impact, but the value of this configuration item is not checked in the source code and cannot be corrected in time when it is set to an abnormal value, which affects the normal use of the program.
[HDFS-16721](https://issues.apache.org/jira/browse/HDFS-16721)
How was this patch tested?
This patch uses Precondition.checkArgument() to refine the code for checking this configuration item.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 46s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 27s

trunk passed

+1 :green_heart:
compile
6m 15s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
6m  2s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
1m 36s

trunk passed

+1 :green_heart:
mvnsite
3m  3s

trunk passed

+1 :green_heart:
javadoc
2m 25s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
2m 49s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
6m 27s

trunk passed

+1 :green_heart:
shadedclient
22m 52s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 19s

the patch passed

+1 :green_heart:
compile
5m 57s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
5m 57s

the patch passed

+1 :green_heart:
compile
5m 44s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
5m 44s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 15s
/results-checkstyle-hadoop-hdfs-project.txt
hadoop-hdfs-project: The patch generated 1 new + 9 unchanged - 0 fixed = 10 total (was 9)

+1 :green_heart:
mvnsite
2m 30s

the patch passed

+1 :green_heart:
javadoc
1m 49s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
2m 15s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
6m  7s

the patch passed

+1 :green_heart:
shadedclient
23m 28s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 45s

hadoop-hdfs-client in the patch passed.

+1 :green_heart:
unit
240m 41s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m 16s

The patch does not generate ASF License warnings.

388m 46s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4713/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4713

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 12268940e515 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9280c3814a633d2b813be3799669689881d444cf

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4713/1/testReport/

Max. process+thread count
3524 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4713/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Increase CPU limit for upgrade test job

/kind enhancement
What this PR does / why we need it:
This PR increases the CPU limit for the upgrade test job from 6 CPUs to 12 CPUs(similar to the single/multi-zone job).
This change is expected to reduce CPU throttling and decrease the flakiness of the upgrade test job.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
cc: @rfranzke

Thanks 😄
/lgtm
/approve


Readme outdated

The readme says that the File parser is still available, but the source says it has been removed in v0.2.0.
What is the 'official' status?
Maybe there is a small example as well that can be used to update the readme.
Cheers (Üdv),
Tibor

At the moment README is highly outdated. I will try to find some time and update it during the weekend.
Üdv:
Márk

Thanks, ping me if I can provide some assistance.
-Tibor

Do you have code snippet at hand that shows how to parse and write a config file to the fs without having to reverse engineer the code? :smile:


Error : "esp_matter_core: Node does not exist or esp_matter does not start" (CON-1264)

After flashing the matter controller example to my ESP32-WROVER-E and monitoring, the following error appears
E (2723) esp_matter_core: Node does not exist or esp_matter does not start
I (2733) chip[DL]: E (2733) app_main: Failed to start Matter, err:259
Done driving station state, nothing else to do...
I (2753) chip[DL]: HandlePlatformSpecificBLEEvent 49152
I (2763) chip[DL]: HandlePlatformSpecificBLEEvent 49152
I (2763) chip[DL]: WIFI_EVENT_STA_CONNECTED
I (2773) chip[DL]: WiFi station state change: Connecting -> Connecting_Succeeded
E (2783) chip[DMG]: Endpoint 0, Cluster 0x0000_0031 not found in IncreaseClusterDataVersion!
I (2783) wifi:E (2793) chip[DMG]: idx:0 (ifx:0, 9c:a2:f4:5c:a3:e7), tid:0, ssn:3, winSize:64Endpoint 0, Cluster 0x0000_0031 not found in IncreaseClusterDataVersion!
Environment

ESP-Matter Commit Id: latest

ESP-IDF Commit Id: Latest

SoC (eg: ESP32 or ESP32-C3): ESP32

Device Logs (Please attach the log file):
idf_py_stdout_output.pdf

Host Machine OS: Ubuntu

Commissioner app and versions if present: Alexa 2.2.575865.0

Can you please give a try by setting CONFIG_ESP_MATTER_ENABLE_MATTER_SERVER=n set using idf.py menuconfig.

I tried the above solution with the latest IDF version and it generated some build error.  On changing to v5.3, this issue is resolved.


Use Lazy class instead of raw function

ref: #1
Users can deserialize GraphQL custom scalar types to their favorite application types. Thus, the type of an application-level field can be any type.
For example, a custom scalar type can be deserialized into a function. However, graphql-fabbrica did not support it. graphql-fabbrica incorrectly interpreted a field deserialized into a function as a lazily evaluated field.
This PR introduces a lazy class so that graphql-fabbrica can distinguish between lazily evaluated fields and fields deserialized into functions.
References

https://graphql.org/learn/schema/#scalar-types
https://www.apollographql.com/docs/apollo-server/schema/custom-scalars/

Frankly, I was not sure if I should support this edge case. However, the ability to eliminate the cast to any type was very appealing.


remove useNativeDriver for backgroundColor animation

this PR try to resolve the Redbox: Style property 'backgroundColor' is not supported by native animated module when running rntester app.
Test Plan:

[x] All flow tests
[x] RNTester app on iOS

Release Notes:
[RNTester] [BUGFIX] [RNTester/js/AnimatedGratuitousApp/AnExSet] - rm useNativeDriver in backgroundColor animation

Thanks for the PR, sorry we didn't merge it earlier and had two people make the same change :(


Unix domain socket

Note, this is based off of the formatted PR.

I can confirm that we have this working happily in production.

Great work @benwilson512.
The formatted PR is merged, could you rebase on master?

Did the format branch get force pushed? I'm having a lot of trouble reconciling the git history

@benwilson512 there were 2 extra commits: 63a8d8f5a594c323a136b5f96d6ce58492fe7d8e and c7110a60bba5306f297230dda04ebd66bacf1057.


Destructuring

TODO:

[x] object destructuring
[ ] tuple destructuring

Destructuring tuples is import for React support since many of the hooks use this pattern.


ISC DHCPv4 need  restart on vlan interface

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

Describe the bug
DHCP server is not responding to "Request":
root@opnSense:~ # tcpdump -t -n -i em2_vlan832
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on em2_vlan832, link-type EN10MB (Ethernet), snapshot length 262144 bytes
IP <IP_ADDRESS>.68 > <IP_ADDRESS>.67: BOOTP/DHCP, Request from a4:3e:51:78:96:d6, length 398
IP6 fe80::a63e:51ff:fe78:96d6.546 > ff02::1:2.547: dhcp6 solicit
IP <IP_ADDRESS>.68 > <IP_ADDRESS>.67: BOOTP/DHCP, Request from a4:3e:51:78:96:d6, length 398
IP6 fe80::a63e:51ff:fe78:96d6.546 > ff02::1:2.547: dhcp6 solicit
IP <IP_ADDRESS>.68 > <IP_ADDRESS>.67: BOOTP/DHCP, Request from a4:3e:51:78:96:d6, length 398

To Reproduce
Apparently, this is related to when opnSense retrieve the WAN interface or maybe when any interface reappears.
not easy to spot the event and link it to the deconnection of ICS Dhcp server (even with a 10minutes lease time).
OpnSense interfaces:
GPon_nic (vtnet0) -> (diectly to the fiber optic gpon)
 LAN_nic (vtnet1) -> v4: <IP_ADDRESS>/16    v6/t6: 2a01:xxxxxfe/64
 LB_nic (em2_vlan832) -> v4: <IP_ADDRESS>/24
 WAN_nic (em0_vlan832) -> v4/DHCP4: 82.125.xxx.xxx/23  v6/DHCP6: fe80::5054:ff:fe93:6c4c%em0_vlan832/64

Relevant log files

2024-09-19T09:30:39
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-18T09:54:50
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-17T23:04:38
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-16T22:37:44
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-13T17:49:51
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-12T18:14:03
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-12T18:07:11
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-11T21:26:58
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-10T18:14:03
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-08T18:53:41
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-06T01:29:35
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

2024-09-06T01:14:39
Error
dhcpd
receive_packet failed on em2_vlan832: Device not configured

If applicable, information from log files supporting your claim.
As soon as ICS DHCPv4 is restarted by OpnSense web interface, the livebox gets the lease and everything is ok until some hours:
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on em2_vlan832, link-type EN10MB (Ethernet), snapshot length 262144 bytes
IP <IP_ADDRESS>.68 > <IP_ADDRESS>.67: BOOTP/DHCP, Request from a4:3e:51:78:96:d6, length 398
ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
IP6 fe80::a63e:51ff:fe78:96d6.546 > ff02::1:2.547: dhcp6 solicit
IP <IP_ADDRESS>.67 > <IP_ADDRESS>.68: BOOTP/DHCP, Reply, length 417
IP <IP_ADDRESS>.68 > <IP_ADDRESS>.67: BOOTP/DHCP, Request from a4:3e:51:78:96:d6, length 404
IP <IP_ADDRESS>.67 > <IP_ADDRESS>.68: BOOTP/DHCP, Reply, length 417
ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 46
IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 11012, seq 0, length 28
ARP, Reply <IP_ADDRESS> is-at 52:54:00:cd:5f:42, length 28
ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 46
ARP, Reply <IP_ADDRESS> is-at 52:54:00:cd:5f:42, length 28
IP <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply, id 11012, seq 0, length 28

Environment
OPNsense 24.7.4_1-amd64
FreeBSD 14.1-RELEASE-p4
OpenSSL 3.0.15
OpnSense runs as a VM on Ubuntu server.
The livebox is provided by the ISP Orange. To have the phone working (SIP) the livebox must be online. The trick is connecting
the WAN interface of the livebox on a local network port.  The port is attributed to a virtual bridge.
Then OpnSense is presented thoses virtual interfaces .
The difference between the regular LAN interface and the Livebox interface is mainly the VLAN 832 aspect of the setup.
As if when OpnSense recovers from 'some event' at low level interfaces, ICS DCHP is not 'seeing' the new em2_vlan832 interface.
This log is just when I noticed lost of internet connection and yep, the livebox was down just after this (9h30):
2024-09-19T09:31:39 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip_map (execute task : vxlan_configure_do()) |   |   |
-- | -- | -- | -- |  -- | -- | -- |
2024-09-19T09:31:38 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip_map (execute task : openssh_configure_do( | opt1 | lan)) |   |
2024-09-19T09:31:38 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip_map (execute task : dhcrelay_configure_map( | opt1 | lan | inet6)) |
2024-09-19T09:31:38 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip_map ( | opt1 | lan | inet6) |
2024-09-19T09:31:38 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync( | lan)) |   |   |
2024-09-19T09:31:34 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do( | lan)) |   |   |
2024-09-19T09:31:34 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do( | lan)) |   |   |
2024-09-19T09:31:34 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do()) |   |   |   |
2024-09-19T09:31:34 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do()) |   |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do()) |   |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip ( | lan) |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do( | lan)) |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface LAN_nic. |   |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do( | lan)) |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do( | lan)) |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn ( | lan) |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync( | opt1)) |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do( | opt1)) |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do( | opt1)) |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do()) |   |   |   |
2024-09-19T09:31:33 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do()) |   |   |   |
2024-09-19T09:31:31 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do()) |   |   |   |
2024-09-19T09:31:31 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip ( | opt1) |   |   |
2024-09-19T09:31:31 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do( | opt1)) |   |   |
2024-09-19T09:31:31 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface WAN_nic. |   |   |   |
2024-09-19T09:31:31 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do( | opt1)) |   |   |
2024-09-19T09:31:31 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do( | opt1)) |   |   |
2024-09-19T09:31:31 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn ( | opt1) |   |   |
2024-09-19T09:31:31 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn_map ( | opt1 | lan | inet6) |
2024-09-19T09:31:28 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'lan' |   |   |   |
2024-09-19T09:31:27 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'opt1' |   |   |   |
2024-09-19T09:31:27 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure dhcp (execute task : dhcpd_dhcp_configure( | inet6)) |   |   |
2024-09-19T09:31:27 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure dhcp ( | inet6) |   |   |
2024-09-19T09:31:27 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: IP renewal starting (address: fe80::5054:ff:fe93:6c4c%em0_vlan832 | interface: opt1 | device: em0_vlan832) |   |
2024-09-19T09:31:24 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip_map (execute task : vxlan_configure_do()) |   |   |   |
2024-09-19T09:31:23 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip_map (execute task : openssh_configure_do( | opt1 | lan)) |   |
2024-09-19T09:31:23 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip_map (execute task : dhcrelay_configure_map( | opt1 | lan | inet6)) |
2024-09-19T09:31:23 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip_map ( | opt1 | lan | inet6) |
2024-09-19T09:31:23 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync( | lan)) |   |   |
2024-09-19T09:31:22 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do( | lan)) |   |   |
2024-09-19T09:31:22 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do( | lan)) |   |   |
2024-09-19T09:31:22 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do()) |   |   |   |
2024-09-19T09:31:22 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do()) |   |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do()) |   |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip ( | lan) |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do( | lan)) |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface LAN_nic. |   |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do( | lan)) |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do( | lan)) |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn ( | lan) |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync( | opt1)) |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do( | opt1)) |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do( | opt1)) |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do()) |   |   |   |
2024-09-19T09:31:20 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do()) |   |   |   |
2024-09-19T09:31:19 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : vxlan_configure_do()) |   |   |   |
2024-09-19T09:31:19 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : openssh_configure_do( | opt1)) |   |   |
2024-09-19T09:31:19 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip_map (execute task : dhcrelay_configure_map( | opt1 | inet)) |   |
2024-09-19T09:31:19 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip_map ( | opt1 | inet) |   |
2024-09-19T09:31:19 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : wireguard_sync( | opt1)) |   |   |
2024-09-19T09:31:19 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : webgui_configure_do( | opt1)) |   |   |
2024-09-19T09:31:19 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do( | opt1)) |   |   |
2024-09-19T09:31:19 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : opendns_configure_do()) |   |   |   |
2024-09-19T09:31:18 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do()) |   |   |   |
2024-09-19T09:31:18 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure newwanip ( | opt1) |   |   |
2024-09-19T09:31:18 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do( | opt1)) |   |   |
2024-09-19T09:31:18 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface WAN_nic. |   |   |   |
2024-09-19T09:31:18 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do( | opt1)) |   |   |
2024-09-19T09:31:18 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do( | opt1)) |   |   |
2024-09-19T09:31:18 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn ( | opt1) |   |   |
2024-09-19T09:31:18 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure vpn_map ( | opt1 | lan | inet6) |
2024-09-19T09:31:18 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : ntpd_configure_do()) |   |   |   |
2024-09-19T09:31:16 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'lan' |   |   |   |
2024-09-19T09:31:16 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dnsmasq_configure_do()) |   |   |   |
2024-09-19T09:31:16 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure newwanip ( | opt1) |   |   |
2024-09-19T09:31:16 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : wireguard_configure_do( | opt1)) |   |   |
2024-09-19T09:31:16 | Notice | opnsense | /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface WAN_nic. |   |   |   |
2024-09-19T09:31:16 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do( | opt1)) |   |   |
2024-09-19T09:31:16 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do( | opt1)) |   |   |
2024-09-19T09:31:16 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure vpn ( | opt1) |   |   |
2024-09-19T09:31:16 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure vpn_map ( | opt1 | inet) |   |
2024-09-19T09:31:15 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'opt1' |   |   |   |
2024-09-19T09:31:15 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure dhcp (execute task : dhcpd_dhcp_configure( | inet6)) |   |   |
2024-09-19T09:31:15 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: plugins_configure dhcp ( | inet6) |   |   |
2024-09-19T09:31:15 | Notice | opnsense | /usr/local/etc/rc.newwanipv6: IP renewal starting (address: fe80::5054:ff:fe93:6c4c%em0_vlan832 | interface: opt1 | device: em0_vlan832) |   |
2024-09-19T09:31:14 | Notice | dhcp6c | dhcp6c_script: REQUEST on em0_vlan832 renewal |   |   |   |
2024-09-19T09:31:14 | Notice | dhcp6c | dhcp6c_script: REQUEST on em0_vlan832 executing |   |   |   |
2024-09-19T09:31:12 | Notice | dhcp6c | RTSOLD script - Sending SIGHUP to dhcp6c |   |   |   |
2024-09-19T09:31:11 | Notice | dhcp6c | dhcp6c_script: REQUEST on em0_vlan832 renewal |   |   |   |
2024-09-19T09:31:11 | Notice | dhcp6c | dhcp6c_script: REQUEST on em0_vlan832 executing |   |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do( | WAN_INTERNET_DHCP)) |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.newwanip: plugins_configure monitor ( | WAN_INTERNET_DHCP) |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.newwanip: ROUTING: keeping inet default route to <IP_ADDRESS> |   |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.newwanip: ROUTING: configuring inet default gateway on opt1 |   |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.all: plugins_configure monitor (execute task : dpinger_configure_do(1)) |   |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.all: plugins_configure monitor (1) |   |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.all: ROUTING: setting inet default route to <IP_ADDRESS> |   |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.all: ROUTING: configuring inet default gateway on opt1 |   |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'opt1' |   |   |   |
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.newwanip: IP renewal starting (new: <IP_ADDRESS> | old: <IP_ADDRESS> | interface: opt1 | device: em0_vlan832 | force: yes)
2024-09-19T09:31:10 | Notice | opnsense | /usr/local/etc/rc.all: ROUTING: entering configure using defaults |   |   |   |
2024-09-19T09:31:10 | Notice | dhcp6c | RTSOLD script - Sending SIGHUP to dhcp6c |   |   |   |
2024-09-19T09:31:09 | Notice | dhclient | dhclient-script: Creating resolv.conf |   |   |   |
2024-09-19T09:31:09 | Notice | dhclient | dhclient-script: New Routers (em0_vlan832): <IP_ADDRESS> |   |   |   |
2024-09-19T09:31:09 | Notice | dhclient | dhclient-script: New Broadcast Address (em0_vlan832): <IP_ADDRESS> |   |   |   |
2024-09-19T09:31:09 | Notice | dhclient | dhclient-script: New Subnet Mask (em0_vlan832): <IP_ADDRESS> |   |   |   |
2024-09-19T09:31:09 | Notice | dhclient | dhclient-script: New IP Address (em0_vlan832): <IP_ADDRESS> |   |   |   |
2024-09-19T09:31:09 | Notice | dhclient | dhclient-script: New Hostname (em0_vlan832): opnSense |   |   |   |
2024-09-19T09:31:09 | Notice | dhclient | dhclient-script: Reason BOUND on em0_vlan832 executing |   |   |   |
2024-09-19T09:31:09 | Error | dhclient | unknown dhcp option value 0x7d |   |   |   |
2024-09-19T09:31:09 | Error | dhclient | unknown dhcp option value 0x5a |   |   |   |
2024-09-19T09:31:09 | Notice | dhclient | dhclient-script: Reason ARPCHECK on em0_vlan832 executing |   |   |   |
2024-09-19T09:31:07 | Notice | dhclient | dhclient-script: Reason ARPSEND on em0_vlan832 executing |   |   |   |
2024-09-19T09:31:07 | Error | dhclient | unknown dhcp option value 0x7d |   |   |   |
2024-09-19T09:31:07 | Error | dhclient | unknown dhcp option value 0x5a |   |   |   |
2024-09-19T09:30:40 | Notice | dhclient | dhclient-script: Reason PREINIT on em0_vlan832 executing |   |   |   |
2024-09-19T09:30:40 | Error | dhclient | ^ |   |   |   |
2024-09-19T09:30:40 | Error | dhclient |   | vlan-id |   |   |
2024-09-19T09:30:40 | Error | dhclient | /var/etc/dhclient_opt1.conf line 13: expecting a statement. |   |   |   |
2024-09-19T09:30:40 | Error | dhclient | ^ |   |   |   |
2024-09-19T09:30:40 | Error | dhclient |   | vlan-parent |   |   |
2024-09-19T09:30:40 | Error | dhclient | /var/etc/dhclient_opt1.conf line 11: expecting a statement. |   |   |   |
2024-09-19T09:30:39 | Notice | kernel | <6>vlan1: changing name to 'em2_vlan832' |   |   |   |
2024-09-19T09:30:39 | Warning | rtsold | <rtsock_input_ifannounce> interface vlan1 removed |   |   |   |
2024-09-19T09:30:39 | Notice | kernel | <6>vtnet2: promiscuous mode disabled |   |   |   |
2024-09-19T09:30:39 | Notice | kernel | <6>vlan0: changing name to 'em0_vlan832' |   |   |   |
2024-09-19T09:30:39 | Warning | rtsold | <rtsock_input_ifannounce> interface em2_vlan832 removed |   |   |   |
2024-09-19T09:30:39 | Warning | rtsold | <rtsock_input_ifannounce> interface vlan0 removed |   |   |   |
2024-09-19T09:30:39 | Warning | rtsold | <rtsock_input_ifannounce> interface em0_vlan832 removed |   |   |   |
2024-09-19T09:30:39 | Critical | dhclient | exiting. |   |   |   |
2024-09-19T09:30:39 | Error | dhclient | connection closed |   |   |   |
2024-09-19T09:30:39 | Critical | dhclient | exiting. |   |   |   |
2024-09-19T09:30:39 | Error | dhclient | No live interfaces to poll on - exiting. |   |   |   |
2024-09-19T09:30:39 | Error | dhclient | Interface em0_vlan832 no longer appears valid. |   |   |   |
2024-09-19T09:30:39 | Error | dhclient | ioctl(SIOCGIFFLAGS) on em0_vlan832: Operation not permitted |   |   |   |
2024-09-19T09:30:39 | Error | dhclient | receive_packet failed on em0_vlan832: Device not configured |   |   |   |
2024-09-19T06:12:18 | Notice | kernel | <6>em2_vlan832: promiscuous mode enabled |   |   |   |
2024-09-19T06:12:18 | Notice | kernel | <6>vtnet2: promiscuous mode enabled |   |   |   |

Cut this morning (11h57).
Wan interface em0_vlan832 was briefly lost causing the 'newwanip' thing to activate.
This time I clearly saw the em2_vlan832 (livebox) disconnected :
2024-09-20T11:57:55 | Error | dhclient | unknown dhcp option value 0x7d |
-- | -- | -- | -- | --
2024-09-20T11:57:55 | Error | dhclient | unknown dhcp option value 0x5a |
2024-09-20T11:57:54 | Notice | dhclient | dhclient-script: Reason ARPCHECK on em0_vlan832 executing |
2024-09-20T11:57:52 | Notice | dhclient | dhclient-script: Reason ARPSEND on em0_vlan832 executing |
2024-09-20T11:57:52 | Error | dhclient | unknown dhcp option value 0x7d |
2024-09-20T11:57:52 | Error | dhclient | unknown dhcp option value 0x5a |
2024-09-20T11:57:37 | Notice | dhclient | dhclient-script: Reason PREINIT on em0_vlan832 executing |
2024-09-20T11:57:37 | Error | dhclient | ^ |
2024-09-20T11:57:37 | Error | dhclient |   | vlan-id
2024-09-20T11:57:37 | Error | dhclient | /var/etc/dhclient_opt1.conf line 13: expecting a statement. |
2024-09-20T11:57:37 | Error | dhclient | ^ |
2024-09-20T11:57:37 | Error | dhclient |   | vlan-parent
2024-09-20T11:57:37 | Error | dhclient | /var/etc/dhclient_opt1.conf line 11: expecting a statement. |
2024-09-20T11:57:37 | Notice | kernel | <6>vlan1: changing name to 'em2_vlan832' |
2024-09-20T11:57:37 | Notice | kernel | <6>vtnet2: promiscuous mode disabled |
2024-09-20T11:57:36 | Warning | rtsold | <rtsock_input_ifannounce> interface vlan1 removed |
2024-09-20T11:57:36 | Warning | rtsold | <rtsock_input_ifannounce> interface em2_vlan832 removed |
2024-09-20T11:57:36 | Notice | kernel | <6>vlan0: changing name to 'em0_vlan832' |
2024-09-20T11:57:36 | Warning | rtsold | <rtsock_input_ifannounce> interface vlan0 removed |
2024-09-20T11:57:36 | Warning | rtsold | <rtsock_input_ifannounce> interface em0_vlan832 removed |
2024-09-20T11:57:36 | Critical | dhclient | exiting. |
2024-09-20T11:57:36 | Error | dhclient | connection closed |
2024-09-20T11:57:36 | Critical | dhclient | exiting. |
2024-09-20T11:57:36 | Error | dhclient | No live interfaces to poll on - exiting. |
2024-09-20T11:57:36 | Error | dhclient | Interface em0_vlan832 no longer appears valid. |
2024-09-20T11:57:36 | Error | dhclient | ioctl(SIOCGIFFLAGS) on em0_vlan832: Operation not permitted |
2024-09-20T11:57:36 | Error | dhclient | receive_packet failed on em0_vlan832: Device not configured |
(tcpdump started early)
2024-09-20T08:37:27 | Notice | kernel | <6>em2_vlan832: promiscuous mode enabled |
The problem started at 11h56, the livebox receive no answsers. Then at 11:56:26, the interface disappeared.
11:55:43.883182 IP <IP_ADDRESS>.68 > <IP_ADDRESS>.67: BOOTP/DHCP, Request from a4:3e:51:78:96:d6, length 392
11:55:43.898044 IP <IP_ADDRESS>.67 > <IP_ADDRESS>.68: BOOTP/DHCP, Reply, length 417
11:55:49.850427 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 46
11:55:49.850455 ARP, Reply <IP_ADDRESS> is-at 52:54:00:cd:5f:42, length 28
11:56:01.195833 IP6 fe80::a63e:51ff:fe78:96d6.546 > ff02::1:2.547: dhcp6 solicit
11:56:05.531394 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:06.532677 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:07.533941 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:08.535733 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:09.536008 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:10.538910 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:11.539980 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:12.542119 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:23.651065 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:24.652450 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:25.655207 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:26.656810 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:31.662599 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:32.664134 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:33.668751 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:34.670232 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:47.675791 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:48.677327 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:49.679138 IP <IP_ADDRESS>.42250 > <IP_ADDRESS>.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:50.679676 IP <IP_ADDRESS>.36973 > <IP_ADDRESS>.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:11.552660 IP <IP_ADDRESS>.43666 > <IP_ADDRESS>.53: 48034+ A? audiphone-lb4-fr.odmtrack.orange.com. (54)
11:57:11.552805 IP <IP_ADDRESS>.53183 > <IP_ADDRESS>.53: 49808+ AAAA? audiphone-lb4-fr.odmtrack.orange.com. (54)
11:57:16.561011 IP <IP_ADDRESS>.43666 > <IP_ADDRESS>.53: 48034+ A? audiphone-lb4-fr.odmtrack.orange.com. (54)
11:57:16.561157 IP <IP_ADDRESS>.53183 > <IP_ADDRESS>.53: 49808+ AAAA? audiphone-lb4-fr.odmtrack.orange.com. (54)
11:57:19.689983 IP <IP_ADDRESS>.39822 > <IP_ADDRESS>.53: 14340+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:20.691570 IP <IP_ADDRESS>.44640 > <IP_ADDRESS>.53: 20472+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:21.568506 IP <IP_ADDRESS>.39211 > <IP_ADDRESS>.53: 46544+ A? audiphone-lb4-fr.odmtrack.orange.com.VEL.access.orange-multimedia.net. (87)
11:57:21.568650 IP <IP_ADDRESS>.41755 > <IP_ADDRESS>.53: 41337+ AAAA? audiphone-lb4-fr.odmtrack.orange.com.VEL.access.orange-multimedia.net. (87)
11:57:21.693923 IP <IP_ADDRESS>.39822 > <IP_ADDRESS>.53: 14340+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:22.695914 IP <IP_ADDRESS>.44640 > <IP_ADDRESS>.53: 20472+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:26.574665 IP <IP_ADDRESS>.39211 > <IP_ADDRESS>.53: 46544+ A? audiphone-lb4-fr.odmtrack.orange.com.VEL.access.orange-multimedia.net. (87)
11:57:26.574757 IP <IP_ADDRESS>.41755 > <IP_ADDRESS>.53: 41337+ AAAA? audiphone-lb4-fr.odmtrack.orange.com.VEL.access.orange-multimedia.net. (87)
tcpdump: pcap_loop: The interface disappeared

From now, the ICSDHCPv4 will never honor em2_vlan832 until restart of dhcp service.
root@opnSense:~ # tcpdump -n -i em2_vlan832
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on em2_vlan832, link-type EN10MB (Ethernet), snapshot length 262144 bytes
12:37:26.208689 IP <IP_ADDRESS>.68 > <IP_ADDRESS>.67: BOOTP/DHCP, Request from a4:3e:51:78:96:d6, length 398
12:37:56.550380 IP6 fe80::a63e:51ff:fe78:96d6.546 > ff02::1:2.547: dhcp6 solicit

nothing particular at line 11 & 13, dhclient 'error' in the log
root@opnSense:~ # cat /var/etc/dhclient_opt1.conf
interface "em0_vlan832" {
        # DHCP Protocol Timing Values
        timeout 8;
        retry 3;

        # DHCP Protocol Options
        send dhcp-class-identifier "sagem";
        send user-class "+FSVDSL_livebox.Internet.softathome.Livebox4";
        send option-90    f3:3b:ac:b9:a5;
        request subnet-mask, routers, domain-name-servers,  broadcast-address,   dhcp-lease-time,  dhcp-renewal-time, dhcp-rebinding-time,  domain-search, option-90, option-120, option-125;
        vlan-parent "em0";
        vlan-pcp 6;
        vlan-id 832;

        script "/usr/local/opnsense/scripts/interfaces/dhclient-script";
        supersede interface-mtu 0;
}
root@opnSense:~ # ls -l  /var/etc/dhclient_opt1.conf
-rw-r--r--  1 root wheel 761 Sep 20 11:57 /var/etc/dhclient_opt1.conf

Hmm some of the custom options in dhclient are no longer supported. Is this an old box that was just recently upgraded?

Hi fichtner
The physical Livebox is not so old but is not the problem. If you want the geographic phone number, the livebox is mandatory because Orange doesn't share its SIP specification.
So, opnSense simulates correctly a 'virtual' Livebox to connect on em0_vlan832 to Orange.
Maybe some Orange modified the 'protocol' for allowing a livebox to connect, ok. But until opnSense stops connecting as a livebox, no need to search anything here for now.
When Orange will block voluntarily or not opnSense, this topic (in french) will wake up:
https://lafibre.info/remplacer-livebox/cacking-nouveau-systeme-de-generation-de-loption-90-dhcp/456/
For me, I'm quite sure I found the cause of my problem. Can you check that the newwanip thing also restarts dhcpserver on VLAN interfaces ?
em2_vlan832 is invisible to the dhcp server !

@Franck78 the answer to your question is simple: DHCP doesn't restart for the simple fact that it binds to all interfaces at the same time anyway. Couple the fact that VLANs are online before DHCP even starts and never changed thereafter (unless manually modified) the situation you run into is rather strange.
What I do refer to regarding Orange is the fact that vlan-parent, vlan-pcp and vlan-id are obsolete and you only have to use the: 'Use VLAN priority' setting with value 'Internetwork Control (6)' now.
https://github.com/opnsense/docs/commit/cc565a2ca5d

ok,
I know why your are confused. I forgot an important piece of info.
I started with 19.1.7 and Orange livebox, ok zero problem on Ubuntu server 2018
At some point I upgraded to Ubuntu 2020 and to opnSense 20.7
Since then, the Wan (FFTH) became unreliable. Add to do numerous manual reboot.
Then I installed monit to detect the bad condition, no exchange on the wan link.
The action of monit was lauch "/usr/local/etc/rc.reload_all"
I also made a short version to minimize the reload:
/* core service reload */
system_resolver_configure(true);
interfaces_configure(true);
system_routing_configure(true);
filter_configure_sync(true);

All this was more or less OK until opnSense 24.7
With 24.7 and this monit fix, restarting the DHCP server is mandatory.
But now

I reviewed the wan setup between OpnSense and the Orange infra
removed the Monit check

My 'new' expectation is that opnSense reconnects alone to Orange. This new config changes everything.
I need some days to see what is happening now.

The change of the mode of connection between opnSense and Orange (eg livebox v6) made it very stable. No disconnection.
That's a good news.
With the old way, opnSense was unable to restore itself the WAN. My "solution" was detecting the loss, after 3 minutes, launch a partial 'rc.restartall'
Maybe that 'rc.restartll' was messing (is) with DHCPv4 preventing it from responding to the em2_vlan832.
I will close this if I don't see loss of the real livebox behind her em2_vlan832 ;)
One month.
thank you

Did this eventually go back to working as intended?

can't tell it's working well. I checked the phone (SIP) provided by the LBox and it was 'off'. One day, one week, can't tell.
Can't tell who is the culprit in this setup. Too many variables (the LBox, the virtualization system, opnSense, something else).
Turning on/off the LB fixes everything but not for long. Probably in relation, while I'm calling/answering sometimes the data stream (SIP) is 'cut'. I ear something like a normal noisy phone line but no voice.


Nested loop printout

Below is my simplified example with nested loops. I need to know their execution times via pb because the inner loop randomly change size and need to know if it's stuck or the problem got too big. How to make the below example  with nested loops to print out nicely.
package main

import (
	"math/rand"
	"time"

	"github.com/cheggaaa/pb"
)

func main() {
	Example_my()

}

func Example_my() {
	second := pb.New(20).Prefix("Second ").Start()
	for i := 0; i < 20; i++ {
		first := pb.New(200).Prefix("First ").Start()
		for n := 0; n < 200; n++ {
			time.Sleep(time.Millisecond * time.Duration(rand.Intn(250)))
			first.Increment()
		}
		second.Increment()
		first.FinishPrint("first") //.Finish()
	}
	second.Finish()
	second.FinishPrint("2nd fisnished")
}

If I understood you right, just use the pool.
Example:
package main

import (
	"math/rand"
	"time"

	"github.com/cheggaaa/pb/v3"
)

func main() {
	first := pb.New(200).Set("prefix", "First")
	second := pb.New(20).Set("prefix", "Second")

	pool := pb.NewPool(first, second)

	_ = pool.Start()

	for i := 0; i < 20; i++ {
		first.SetTotal(200).SetCurrent(0)
		for n := 0; n < 200; n++ {
			time.Sleep(time.Millisecond * time.Duration(rand.Intn(250)))
			first.Increment()
		}
		second.Increment()
	}

	_ = pool.Stop()
}


Middle Mouse clicking in inventory screen of Mob Crusher results in items deleted including upgrade modules

Industrial Foregoing
1.18.2-<IP_ADDRESS>-9
Titanium
1.18.2-3.5.6-38
Problem Statement:
When in the inventory screen of the Mob Crusher; middle-mouse clicking in the loot inventory area results in all items being deleted including any installed range modules. Essence container doesn't appear to be impacted as any accrued Essence remains in the inventory.
Steps to Duplicate
Deploy an IF 'Mob Crusher' and provide sufficient power.
Install any combination of upgrade modules.
Spawn mobs and allow them to be killed/harvested.
Verify loot drops have been generated in the inventory of the Mob Crusher.
Move your mouse cursor into the 3x6 orange inventory area
Click Middle-Mouse || 'Middle Button' in keybinds menu.
Watch your loot and upgrades vanish into the nether.

Possibly related to the Inventory Sorter mod, which by default uses the Middle (mouse) Button for sorting inventory, which is why those of us who experience this bug are clicking the middle mouse button in the inventory.

Not IF issue

Update: For what it's worth, my son and I are now playing FTB Skies, and this behavior is also present on this pack.
I am opening a new issue on that pack, but just for anyone who may find this post in FTB Skies 1.0.3 and 1.0.4, opening the Flower pouch (botania) WITH flowers inside it, and middle-mouse-clicking inside the flower pouch will void ALL flowers in the inventory of the pouch.


Resubmission one

Added css comments, restored site appearance and original content, added screenshot to the README, moved application code out of the subfolder and into the root directory

Biggest item of concern is moving the subfolders and files into the root directory.


GoPro Hero 13 Black GPS

It seems the GPS is back on Hero 13 Black? (https://gopro.com/en/ro/shop/cameras/learn/hero13black/CHDHX-131-master.html)
If the GPS is indeed in there, can we assume that it's GPS9 only from now on? I recall something about GPS5 being deprecated with the Hero 11 Black which logged both.
If so, great to hear! It's not in the tech specs as far as I can see, but it's mentioned in the intro video, the on the main page together with new overlay, and also in the footnote regarding battery life ("GPS off"). @dnewman-gpsw Perhaps you could check with your colleagues if this can be added to the tech specs, since I suspect many of us frequenting this repo are looking exactly for this.

try this
https://gofile.io/d/yMHabA
select the desired compiler in the installer

GPS is back with a GPS9 track in the GPMF track.  I just updated the repo's readmes.

That's great, thank you!


Introduce component-level Design Page template

Create a markdown template for authoring Design Guidelines (usage guidelines) pages for pf-next components. Follow the format outlined here: https://docs.google.com/document/d/1L0YnKwJimjpO81mwDpigkOq81qX97LikwlR9Edq1JN0/edit?usp=sharing

Closed by PR #324


Changing AspectRatioContainer to anything other than 'fit' crashes Godot Editor 4.0 RC1

Godot version
4.0 RC1
System information
Intel Mac OS
Issue description
When using an aspect ratio container, with a texture rect as a child. Setting the aspect ratio container to anything other than 'fit' is crashing the editor
Steps to reproduce

change the aspect ratio container mode from 'fit' to 'cover'
crashes editor

Minimal reproduction project
aspectratiobug.zip

GDB Backtrace
Thread 1 "godot.linuxbsd." received signal SIGSEGV, Segmentation fault.
0x0000555569bb727d in Callable::get_object (this=0x7fffed958810) at core/variant/callable.cpp:132
132                     return ObjectDB::get_instance(custom->get_object());
(gdb) bt
#0  0x0000555569bb727d in Callable::get_object (this=0x7fffed958810) at core/variant/callable.cpp:132
#1  0x000055556a3bde92 in MessageQueue::statistics (this=0x6070000f47e0) at core/object/message_queue.cpp:154
#2  0x000055556a3bd5f7 in MessageQueue::push_callablep (this=0x6070000f47e0, p_callable=..., p_args=0x0, p_argcount=0, p_show_error=false) at core/object/message_queue.cpp:121
#3  0x0000555562d0a0d7 in MessageQueue::push_callable<>(Callable const&) (this=0x6070000f47e0, p_callable=...) at ./core/object/message_queue.h:101
#4  0x0000555564fb08d3 in CanvasItem::queue_redraw (this=0x61f00055b290) at scene/main/canvas_item.cpp:358
#5  0x0000555565357cd3 in Button::set_text (this=0x61f00055b290, p_text=...) at scene/gui/button.cpp:451
#6  0x0000555562ed5c58 in EditorLog::LogFilter::set_message_count (this=0x604005f7ff60, p_count=2) at editor/editor_log.h:112
#7  0x0000555562ecd591 in EditorLog::_process_message (this=0x61e000d47090, p_msg=..., p_type=EditorLog::MSG_TYPE_STD) at editor/editor_log.cpp:223
#8  0x0000555562ecd7d4 in EditorLog::add_message (this=0x61e000d47090, p_msg=..., p_type=EditorLog::MSG_TYPE_STD) at editor/editor_log.cpp:235
#9  0x0000555562f7e18d in EditorNode::_print_handler (p_this=0x61f000064a90, p_string=..., p_error=false, p_rich=false) at editor/editor_node.cpp:6503
#10 0x000055556a49d45e in __print_line (p_string=...) at core/string/print_string.cpp:81
#11 0x000055555d8497a4 in print_line (v=...) at ./core/string/print_string.h:65
#12 0x000055556a3bd585 in MessageQueue::push_callablep (this=0x6070000f47e0, p_callable=..., p_args=0x0, p_argcount=0, p_show_error=false) at core/object/message_queue.cpp:120
#13 0x0000555562d0a0d7 in MessageQueue::push_callable<>(Callable const&) (this=0x6070000f47e0, p_callable=...) at ./core/object/message_queue.h:101
#14 0x0000555564fb08d3 in CanvasItem::queue_redraw (this=0x61f000556c90) at scene/main/canvas_item.cpp:358
#15 0x0000555565812266 in RichTextLabel::_add_item (this=0x61f000556c90, p_item=0x607001f7e040, p_enter=false, p_ensure_newline=false) at scene/gui/rich_text_label.cpp:2979
#16 0x0000555565811658 in RichTextLabel::add_text (this=0x61f000556c90, p_text=...) at scene/gui/rich_text_label.cpp:2924
#17 0x0000555562ece827 in EditorLog::_add_log_line (this=0x61e000d47090, p_message=..., p_replace_previous=false) at editor/editor_log.cpp:327
#18 0x0000555562ecd476 in EditorLog::_process_message (this=0x61e000d47090, p_msg=..., p_type=EditorLog::MSG_TYPE_STD) at editor/editor_log.cpp:219
#19 0x0000555562ecd7d4 in EditorLog::add_message (this=0x61e000d47090, p_msg=..., p_type=EditorLog::MSG_TYPE_STD) at editor/editor_log.cpp:235
#20 0x0000555562f7e18d in EditorNode::_print_handler (p_this=0x61f000064a90, p_string=..., p_error=false, p_rich=false) at editor/editor_node.cpp:6503
#21 0x000055556a49d45e in __print_line (p_string=...) at core/string/print_string.cpp:81
#22 0x000055555d8497a4 in print_line (v=...) at ./core/string/print_string.h:65
#23 0x000055556a3bd585 in MessageQueue::push_callablep (this=0x6070000f47e0, p_callable=..., p_args=0x0, p_argcount=0, p_show_error=false) at core/object/message_queue.cpp:120
#24 0x0000555562d0a0d7 in MessageQueue::push_callable<>(Callable const&) (this=0x6070000f47e0, p_callable=...) at ./core/object/message_queue.h:101
#25 0x000055556545c14a in Container::queue_sort (this=0x61e0002eb090) at scene/gui/container.cpp:143
#26 0x000055556545a586 in Container::_child_minsize_changed (this=0x61e0002eb090) at scene/gui/container.cpp:40
#27 0x00005555654633ec in call_with_variant_args_helper<Container>(Container*, void (Container::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (p_instance=0x61e0002eb090, p_method=NULL, p_args=0x0, r_error=...)
    at ./core/variant/binder_common.h:293
#28 0x0000555565462b29 in call_with_variant_args<Container> (p_instance=0x61e0002eb090, p_method=(void (Container::*)(Container * const)) 0x55556545a562 <Container::_child_minsize_changed()>, p_args=0x0, p_argcount=0, r_error=...)
    at ./core/variant/binder_common.h:407
#29 0x0000555565461dfa in CallableCustomMethodPointer<Container>::call (this=0x608001864bb0, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/object/callable_method_pointer.h:104
#30 0x0000555569bb5cd0 in Callable::callp (this=0x60d003e9d968, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at core/variant/callable.cpp:50
#31 0x000055556a3d4e2f in Object::emit_signalp (this=0x61e0002ebc90, p_name=..., p_args=0x0, p_argcount=0) at core/object/object.cpp:1046
#32 0x000055555e92a5fb in Object::emit_signal<>(StringName const&) (this=0x61e0002ebc90, p_name=...) at ./core/object/object.h:869
#33 0x000055556547868b in Control::_update_minimum_size (this=0x61e0002ebc90) at scene/gui/control.cpp:1539
#34 0x000055555ea65bdc in call_with_variant_args_helper<__UnexistingClass>(__UnexistingClass*, void (__UnexistingClass::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (p_instance=0x61e0002ebc90, p_method=NULL,
    p_args=0x7fffffffd0f0, r_error=...) at ./core/variant/binder_common.h:293
#35 0x000055555ea61adb in call_with_variant_args_dv<__UnexistingClass> (p_instance=0x61e0002ebc90, p_method=(void (__UnexistingClass::*)(__UnexistingClass * const)) 0x555565478414 <Control::_update_minimum_size()>, p_args=0x0,
    p_argcount=0, r_error=..., default_values=...) at ./core/variant/binder_common.h:440
--Type <RET> for more, q to quit, c to continue without paging--
#36 0x000055555ea584c4 in MethodBindT<>::call(Object*, Variant const**, int, Callable::CallError&) const (this=0x60c0000d69d0, p_object=0x61e0002ebc90, p_args=0x0, p_arg_count=0, r_error=...) at ./core/object/method_bind.h:320
#37 0x000055556a3d000c in Object::callp (this=0x61e0002ebc90, p_method=..., p_args=0x0, p_argcount=0, r_error=...) at core/object/object.cpp:733
#38 0x0000555569bb635f in Callable::callp (this=0x7fffedd587a0, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at core/variant/callable.cpp:62
#39 0x000055556a3c0054 in MessageQueue::_call_function (this=0x6070000f47e0, p_callable=..., p_args=0x7fffedd587b8, p_argcount=0, p_show_error=false) at core/object/message_queue.cpp:229
#40 0x000055556a3c08be in MessageQueue::flush (this=0x6070000f47e0) at core/object/message_queue.cpp:275
#41 0x000055556514b8da in SceneTree::process (this=0x619000301190, p_time=0.0069444444444444449) at scene/main/scene_tree.cpp:461
#42 0x000055555d9911eb in Main::iteration () at main/main.cpp:3131
#43 0x000055555d8432ea in OS_LinuxBSD::run (this=0x7fffffffdf30) at platform/linuxbsd/os_linuxbsd.cpp:880
#44 0x000055555d82ebd2 in main (argc=4, argv=0x7fffffffe538) at platform/linuxbsd/godot_linuxbsd.cpp:73

To add: this only happens if the TextureRect's expand mode is "Fit Width Proportional"

I spent some time researching this bug, and it appears to be caused in part due to container sorting logic (specifically the AspectRatioContainer, but I haven't investigated other containers yet). Essentially, after changing the mode to Cover, the children are sorted / resized. This causes the container's minimum size to change, which causes the sorting to happen again, except this time the children are sized larger than before, which affects the container's minimum size (infinite loop), and this continues until the MessageQueue buffer is full, explaining the stack trace above. This leads me to believe the issue is with a signal/notification, because the message queue doesn't appear to be fully processing messages (and freeing up queue space).
There may be a separate bug with the message queue causing an access violation, which may only manifest when the queue is full. I am investigating that too.

The MessageQueue crash is likely https://github.com/godotengine/godot/issues/63298
But the infinite loop in container logic should be fixed independently of that one.

Printing the child_size gives interesting results 🙃
https://user-images.githubusercontent.com/2223172/219110360-c16395b8-4d76-43c7-ac2f-f54e614a702d.mp4

If the issue is caused by the TextureRect, then from the discussion on RC it seems that TextureRect is wrongly using its current size to compute its min size. This shouldn't be done.

Then what should it use? The whole point of expand modes was to have the TextureRect fit the texture properly based on size.

@KoBeWi It should use the current size to compute the size of the texture. But it should not use it to compute the min size of the control, otherwise it can lead to infinite growth and recalculation, as is observed. The texture size should be used for the min size.

Okay, so after looking into the feature, I think that the original problem should've been solved differently. This implementation tries to trick the container into keeping a ratio by manipulating the min size, but that leads to other issues, as min size has to be deterministic and it isn't. This feature doesn't work with all containers because of that, and it also glitches when the control is used standalone, with anchors.
The solution to the problem should've been to introduce a new sizing flags for containers, or a probably modifier, like Expand, so that we tell the container the desired behavior instead of trying to trick it with what is in essence a hack. That new flag would tell the container to take the min size of the child and use it as a ratio when filling the space, so if the container needs to make the height bigger, it also has to make the width bigger. Then on the TextureRect's side you need to give it a min size with a correct ratio matching your texture, which is a bit of a setup, but will work reliably.
That's the proper solution, IMO. As for the current one, I'm not sure how to salvage it, because it relies on an unstable logic. The safest option would probably be to remove the newly added expand options and only keep the first two, keep size and ignore size. Then we can work on a better solution, in 4.1 I guess.

Anyway, something needs to be done fast because a crash/infinite loop isn't a good thing to have in 4.0 stable :/

he safest option would probably be to remove the newly added expand options and only keep the first two, keep size and ignore size.

If we are going for a temporary fix for the crash, I have a better solution: #73396
No reason to remove a functionality if it works fine in every case except one.

No reason to remove a functionality if it works fine in every case except one.

It's not just one case, and the fact that it works at all is incidental. The implementation is simply incorrect, and we will not be able to remove it after 4.0.

I don't have a permanent solution for now. We could even go with your sizing flag solution (but it can't require setting minimum size), in worst case we will end up with a few legacy enum values for expand_mode and some compatibility code.
Expand flags are too important for TextureRect to remove them after they finally got implemented and made the class usable in containers.

but it can't require setting minimum size

Why is that a limitations? Setting up min sizes is a normal practice for containers. You would need to supply the ratio somehow, without relying on the current size to avoid cascading issues.

Expand flags are too important for TextureRect to remove them after they finally got implemented and made the class usable in containers.

A size flag would be easy to implement. I don't think committing to a problematic implementation just to preserve our current status quo is valid. I understand that you need this, but we should make it waterproof. I'm sorry that the PR hasn't been reviewed properly in the first place, so we could avoid it.

Why is that a limitations?

Because it makes the TextureRect too rigid. If I use any expand mode other than "Keep Size", I don't care about texture size and just want the TextureRect to fit in whatever I put it into. Before Expand Modes I had to resort to all sorts of hacks to make it stretch properly in BoxContainers.
Implementing a ratio that depends on custom minimum size is totally pointless, because that's exactly how TextureRect was before - you had to use custom minimum size. And the container may change size or the size can sometimes be arbitrary, which makes it very cumbersome to work with.
As an example, you might want to have a HBoxContainer with text and icon. The icon is bigger than font, so you enable the "Expand" (as it was in 3.x) and set a minimum size, so the icon fits. But then you decide to change the font size, or whatever detail that affects the icon size. Suddenly it doesn't fit anymore and you have to manually set a new minimum size that will make the icon stretch properly. After doing it 10+ times, it becomes kind of annoying. It's even worse if the icon isn't square, because you need to calculate the minimum size that will make the icon keep aspect ratio.

But what I propose doesn't require you to do any of that. You give it a small minimum size and leave the rest to the container. If you really want to remove this step, we could add a flag to TextureRect to have a min size be a small ratio based on the texture size (say, values between 0 and 1). That would still be deterministic and work with any container.

I am interested in implementing the approach from @YuriSizov, including any compatibility shims / fixups. I'm a new contributor, but I think I can manage this implementation (including docs, compatibility/migration tooling, etc.). I think I will give it a try. :)

@chutchinson Hey, thanks for offering! It depends on the timeline right now. If we only remove the current options right now, and work on the solution later, I'd be happy to help you with this. But if we want to have the implementation replaced in the next few days (or even today), it's probably better if one of the maintainers (well, me, I guess) works on it. I'll let you know the plan.

The crash is fixed by #73396, so repurposing this issue for the underlying bug (feel free to edit the title if I didn't infer it correctly).

@chutchinson If you want to work on a PR for the updated implementation, feel free. If you drop by the contributors chat, I can help you to figure out the necessary steps.

In the end it might be impossible to implement proportional sizing for controls without the min size hackery, similar to how it's done in TextureRect. The main problem is that there is no mechanism to enforce any size restrictions aside from through the min size. So if we need to somehow tell the owning container that hey, if I grow horizontally I also must grow vertically, we just can't do that.
The container sizing option that I proposed here only moves the hack from the child node, like TextureRect, to the parent container. But then, if that container is also a child of another container, then we can only communicate this new limit via the min size. So we end up in the same place we are currently, with unstable logic that just kind of works.
Say we have a BoxContainer. It uses children min sizes to allocate itself a min size. If it's anchored and you resize it to be bigger, or if it's a child of another container that resizes it to be bigger, then it can use the remaining size to expand the children that want that. So in HBox we are free to expand horizontally to take as much space as there is. But if these children are configured to resize proportionally, then they will demand more vertical space as well. Something that our HBox doesn't necessarily have.
Which is not a problem in an anchored control, we can just grow in any direction. But if our HBox is a child of another container, say VBox, it needs to request more space from that VBox, and the only mechanism that Godot has for that is min size. (And then VBox might need to request space from its parent, and so on.)

Long story short, I'm putting a pin in this one. Feel free to come up with alternative ideas.
So far I can imagine some path with introducing an extra concept, besides the min size, that containers can use for their sizing logic. That could allow us to divorce the container logic and general min size limitations a node might have. So a control node can have some "requested size" which the container will use for allocating some space (all the way up the chain), and min size would be only used to actually limit the minimal size.

The crash is fixed by #73396, so repurposing this issue for the underlying bug (feel free to edit the title if I didn't infer it correctly).

The crash doesn't seem to be fully fixed, it still crashes if there are other container nodes (e.g. BoxContainer) between the AspectRatioContainer and the TextureRect.
These two functions are in conflict with each other.

The container tries to rely on the minimum size of the child control to determine the display space of the child control;
And the size of the child control depends on the size of the display space, which affects its own minimum size.

The condition of the infinite loop is met. Similar to #75713 at this point.


feat: implement Async Profiling widget

Implement a new widget in dashboards to visualize async profiling.
Video
https://github.com/user-attachments/assets/87d08369-2252-4bdc-ac15-93f2aa0e6a6f
Signed-off-by: Qiuxia Fan<EMAIL_ADDRESS>

We need to put the parameter explanation table in the UI as tips.


Error when install h3 in Jenkins

Does anyone know this kind of error in Jenkins?
Some answer said install cmake but Jenkins environment cannot get sudo priority.
Running setup.py install for h3: started
    Running setup.py install for h3: finished with status 'error'
    ERROR: Command errored out with exit status 1:
     command: /mnt/jenkins/workspace/test-sim-learn/env/bin/python2.7 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-sx5ESs/h3/setup.py'"'"'; __file__='"'"'/tmp/pip-install-sx5ESs/h3/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-OyoolU/install-record.txt --single-version-externally-managed --compile --install-headers /mnt/jenkins/workspace/test-sim-learn/env/include/site/python2.7/h3
         cwd: /tmp/pip-install-sx5ESs/h3/
    Complete output (120 lines):
    running install
    running build
    running build_py
    creating build
    creating build/lib.linux-x86_64-2.7
    creating build/lib.linux-x86_64-2.7/h3
    copying h3/__init__.py -> build/lib.linux-x86_64-2.7/h3
    copying h3/h3.py -> build/lib.linux-x86_64-2.7/h3
    running build_ext
    + VERSION=v3.4.2
    + IS_64BITS=True
    + '[' '' == v3.4.2 ']'
    + command -v cmake
    + mkdir -p h3/out
    + rm -rf h3c
    + git clone https://github.com/uber/h3.git h3c
    Cloning into 'h3c'...
    + pushd h3c
    /tmp/pip-install-sx5ESs/h3/h3c /tmp/pip-install-sx5ESs/h3
    + git pull origin master --tags
    From https://github.com/uber/h3
     * branch            master     -> FETCH_HEAD
    Already up to date.
    + git checkout v3.4.2
    Note: checking out 'v3.4.2'.

    You are in 'detached HEAD' state. You can look around, make experimental
    changes and commit them, and you can discard any commits you make in this
    state without impacting any branches by performing another checkout.

    If you want to create a new branch to retain commits you create, you may
    do so (now or later) by using -b with the checkout command again. Example:

      git checkout -b <new-branch-name>

I think this is addressed in uber/h3-py#59


get_digital_currency_daily() market = USD

One small issue using "get_digital_currency_daily()". The result is returned in two currencies, market and USD, OK. But if I set the market to USD I get duplicate Pandas labels.
So indexing a row ( row['. close (USD)'] ) results in a two element series for USD, and a scalar for other markets.
The duplicate data comes from AV, but is not really an issue for them as they present data as a structured list and parsing would normally take the first match. However inserting all this data into a table (Pandas) results in duplicate keys. Indexing the table gets two matches and returns a list of two values rather than the single USD value we get from other markets.
Test case:
usd.zip
This prints:
For GBP price returns <class 'numpy.float64'>
For USD price returns <class 'pandas.core.series.Series'>

Hi @Ham-Merhead, I have been super busy and yesterday I just had time for some other important fixes. I will try to have a look over it and fix it over the weekend.
Best Regards Romel.

Got it. Great, thank you.
In my code I changed the column keys to the full AV labels (e.g. '4b. close (USD)' or '4. close'), removed my workaround, and everything just worked :)   Always a nice experience.
I think your choice of solution is the sustainable one, but I would suggest a clear statement someplace. As newbies will assume for example 'close', and existing users will expect no change. Also I notice the index changed from a string (the date) to an int64 - no problem just different.
I tried:
get_digital_currency_daily()    with BTC and two markets USD and GBP
get_daily_adjusted()      with SPY


fixing az cli script for aks

fixing az cli script for aks as per #25244

@ghostinthewires : Thanks for your contribution! The author, @iainfoulds, has been notified to review your proposed change.

Thanks, @ghostinthewires. Not sure why this causes problems on WSL. Works fine natively on MacOS and Cloud Shell. Given you're proposed approach, the read is actually unnecessary. I'll remove in additional PR.
#sign-off