[Question] Filter performance on large data in datagrid

I'm really interested in using the dynamic data package, so I played around couple of days with it a bit...
However, I'm currently facing a performance problem, when I try to filter a large dataset (from 300.000 to 1.5 million rows) within the datagrid control.
I've also created a project here on github for testing purposes: https://github.com/PlotlyUser2/ReactiveDataGridTest
My setup for that is pretty simple: I've a search box and a DataGrid preloaded with a large dataset.
Snippet:
	// For binding to UI
	private readonly ReadOnlyObservableCollection<DataGridViewModel> _itemsBinding;

        public ReadOnlyObservableCollection<DataGridViewModel> TargetCollection => _itemsBinding;

        public MainViewModel(SourceList<DataGridViewModel> _dataList)
        {

            AddSomeRandomData(_dataList);

            var _observableSearchPhrase = this
                .WhenAnyValue(x => x.SearchPhrase)
                .Where(x => !string.IsNullOrEmpty(x) || !string.IsNullOrWhiteSpace(x))
                .DistinctUntilChanged()
                .Select(FilterOnId);

            _dataList.Connect()
                .ObserveOnDispatcher()
                .Filter(_observableSearchPhrase)
                .Bind(out _itemsBinding)
                .DisposeMany()
                .Subscribe();

        }

        private static void AddSomeRandomData(SourceList<DataGridViewModel> _dataList)
        {
            var random = new Random();
            for (int i = 0; i < 300_000; i++)
            {

                var buffer = new byte[random.Next(8, 100)];

                random.NextBytes(buffer);
                string hexData = BitConverter.ToString(buffer);

                var dataGridViewModel = new DataGridViewModel
                {
                    TimeStamp = DateTime.Now.ToString("HH:mm:ss.ffffff"),
                    Id = random.Next(1, 10).ToString(),
                    HexData = hexData
                };

                _dataList.Add(dataGridViewModel);
            }
        }

As it can be seen here (tested with 300k items)

it is pretty slow. Also the UI is unresponsible at this time too.
This arises the question, does the Filter operation is slow, especially on the first entry, or does the WPF DataGrid rendering takes so much time? In addition to that, how to write the Filter operation in an asynchronous manner to overcome the UI lag while the filtering task is ongoing. I haven't found any example to it.
Thanks.

You can choose what operations run on what thread using ReactiveUI's ObserveOn operator

_dataList.Connect()
                .ObserveOn(RxApp.TaskpoolScheduler) // to run on background thread
                .Filter(_observableSearchPhrase)
                .ObserveOn(RxApp.MainThreadScheduler) //this needed because UI updates need to run on the main thread
                .Bind(out _itemsBinding)
                .DisposeMany()
                .Subscribe();

This makes it so the filtering operation will run only on a background thread.
Another option is to use ReactiveUI's Throttle on your search field.
Currently for every character change, the whole filter operation is executed. This can be reduced to ignore rapid changes when the user is typing. this should ensure that the filter is only run once the user is done typing
var _observableSearchPhrase = this
                .WhenAnyValue(x => x.SearchPhrase)
                .Throttle(TimeSpan.FromMiliseconds(200)) // only propagates changes that occur more than 200 miliseconds apart
                .Where(x => !string.IsNullOrEmpty(x) || !string.IsNullOrWhiteSpace(x))
                .DistinctUntilChanged()
                .Select(FilterOnId);

Try a combination of the two to get a gauge of the performance of the library and also, a common problem encountered when making UIs. Hope this helps

That actually helped a lot, to keep the application responsive! Thanks.
But the performance is still slow, when I load over a million of rows in the DataGrid. In fact, the UI become laggy during the filtering operation. Do I have to go for something like data virtualization?
Also, is there a way to show a simple indeterminate progress bar while the filtering process is active?


/core-model-1-4:network-control-domain=cache/link={uuid}/link-port={local-id} - error response message for unknown NEs needs to be changed

If the cache doesn't contain data for the combination of uuid/local-id the service returns a 404 for both GET and DELETE, which is correct.
However the responseMessages need to be modified, as they currently both return "unable to fetch records for link >uuid<".
They should be changed as follows:

GET: "unable to fetch records for linkport >uuid</>local-id<"
DELETE: "unable to delete records for linkport >uuid</>local-id<"

Tested with latest package 1.1.2e, Issue still persist.
observing Null response when trying to GET a link port that doesnt exists.

http://xxx:xxx/core-model-1-4:network-control-domain=cache/link=513250008/link-port=3

{
  "core-model-1-4:link-port": [
    null
  ]
}

observing 204 RESPONSE when trying to DELETE a link port that doesnt exists.

http://xxx:xxx/core-model-1-4:network-control-domain=cache/link=513250008/link-port=4

Response:
access-control-allow-origin: *
 connection: keep-alive
 date: Wed, 19 Jun 2024 06:09:48 GMT
 keep-alive: timeout=5
 x-powered-by: Express

MWDI should return default messages for standard responseCodes. This will be aligned with 1.1.3, therefore closed


Laravel 5.2

Are there any plans in place for a version supporting Laravel 5.2, and an approximate timeframe thereof?

Hi CWood1,
I don't know if helps, but I have a small application using Laravel 5.2 and this package and it's working fine until now.
Are you having any issues?

I was mainly asking as, if not, I was going to take a look at starting the conversion, and wanted to avoid duplicate effort. If it tentitively works, I'll try on a larger application shortly, and report back here; if I find any issues, I'll start work on 5.2 support.
Thanks for reporting back!

Sounds Great ;)

The only issue I've had is with the Database Token Repository, which will throw an error anytime an Auth token is evaluated against it's expire date (e.g. when you click a change password email link).
The problem is how they changed the service provider for 5.2 vs. 5.1 (https://github.com/laravel/framework/commit/1aa9577caf43fbcd769050d4c49f4af880991ef2#diff-ae1e33c0c665facb622cf6ce6187d5f1). I've been trying to create a workaround for this but haven't had too much time to figure out.
If you want to upgrade to 5.2, then in the meantime for a quick-fix, try replacing the code in /vendor/laravel/framework/src/Illuminate/Auth/Passwords/DatabaseTokenRepository.php, line 126 from:
$expirationTime = strtotime($token['created_at']) + $this->expires;`

to
$expirationTime = strtotime($token['created_at']['date']) + $this->expires;

This will solve any password reset or token expires comparison issues, which are the only ones I've found so far and I've been using laravel-mongodb for both Eloquent and Query Builder on 5.2 quite a bit in the short time it's been released.

Thanks for mentioning the fix but I wouldn't be comfortable changing framework files as I need to sync this among different environments. Can we have a Laravel 5.2 release for this?

Hi, I have same the problem as well using Laravel 5.2. I' m also not comfortable changing the framework files. Any thought?

Did you guys register the included PasswordResetServiceProvider? This should register a custom db repository.

Can you guys test out my last commit to the service provider?

Thanks @jenssegers I'll try and let you know

@jenssegers Thank you for the fix. I just tested. The password reset worked perfectly now. Just that need to use Carbon to generate valid token's timestamp. Ref: https://github.com/zhaff/laravel-mongodb/commit/fb405cd92f3aadb31588410e91779cb47ae00980

@jenssegers The latest commit breaks compatibility with Laravel 5.1 LTS. Illuminate\Auth\PasswordBrokerManager is only available in 5.2.

@jenssegers worked for me too. Thanks!

@iceheat are you getting an error? Seems to be working fine for me in 5.1 tests.

@jenssegers yes, don't have the Class on my installation. Laravel api  shows its only available from 5.2. I only noticed the problem when I was attempting artisan route:list.

iceheat is right, it broke my Laravel 5.1.30 project as well. I will upgrade to 5.2, I hope it solves the problem. But anyway, thanks for the mongo development, Jens!

@Ravaelles a quick fix is to set your composer.json to require  "jenssegers/mongodb": "3.0.0-alpha" for now. Hope @jenssegers would figure a way around it soon

I have the same issue with 5.2


static routes lost after reboot

hi,
i have set some static route via luci.
the target is to route some ip's to a vpn tunnel on a new interface... all works as expected but after a reboot the routes are all lost.
in luci webinterface are the routes still persent but i cant activate it again. if i click on apply again the routes won't be set again. I have to delete the routes and set them again to bring it up to work.
the sames as described here
https://forum.lede-project.org/t/static-route-not-working/5993/8
here is my config
`config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '<IP_ADDRESS>'
option netmask '<IP_ADDRESS>'
config globals 'globals'
option ula_prefix 'fd7d:3b4e:f31c::/48'
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option netmask '<IP_ADDRESS>'
option ip6assign '60'
option ipaddr '<IP_ADDRESS>'
config interface 'wan'
option ifname 'eth0.2'
option proto 'dhcp'
option peerdns '0'
option hostname 'router'
config interface 'wan6'
option ifname 'eth0.2'
option proto 'dhcpv6'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0t 2 3 4 5'
option vid '1'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '0t 1'
option vid '2'
config interface 'dlhost'
option proto 'none'
option ifname 'tun0'
config route
option interface 'dlhost'
option target '<IP_ADDRESS>'
config route
option interface 'dlhost'
option target '<IP_ADDRESS>'
config route
option interface 'dlhost'
option target '<IP_ADDRESS>'
config route
option interface 'dlhost'
option target '<IP_ADDRESS>'
config route
option interface 'dlhost'
option target '<IP_ADDRESS>'`
how can i fix this?

I think on boot the VPN-Interface is not set up and so is not connected to the other Network.
Because of this the static routes in the system are not written to the routing table.
If you do a /etc/init.d/network restart the routings are setup.

Nope.. other internal static routes doesn't work too

CLosing as this is unrelated to LuCI.


Update Settings “general”

Automatically generated by Netlify CMS

👷 Deploy Preview for docbracing processing.

Name
Link

🔨 Latest commit
c132db2dc4c072350f2d4c74998af6036fc4a67f

🔍 Latest deploy log
https://app.netlify.com/sites/docbracing/deploys/6510d33e6b39eb0008cf3cfd


feat(docgen): Automatically add deprecated messages to removed errors

Description (required)
Astro developers keep not following my carefully crafted rules regarding removing errors. Which probably mean my rules are not so carefully crafted. This PR makes it so when an error is removed, a basic deprecated message is added automatically, so at least there's some indication that one could upgrade their Astro version to proceed further.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
reference/errors/actions-used-with-for-get-error.mdx
Source changed, localizations will be marked as outdated.

en
reference/errors/env-invalid-variable.mdx
Source changed, localizations will be marked as outdated.

en
reference/errors/invalid-rewrite404.mdx
Source changed, localizations will be marked as outdated.

en
reference/errors/locals-not-serializable.mdx
Source changed, localizations will be marked as outdated.

en
reference/errors/markdown-content-schema-validation-error.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


DL4JInvalidConfigException when trying to import Keras pretrained model

Issue Description
When trying to import a Keras model saved with the .save() method an exception is thrown.
Version Information
Please indicate relevant versions, including, if relevant:

Deeplearning4j 1.0.0-beta7
Windows 10
No CUDA
tesnorflow-gpu 1.14.0
Keras 2.3.1

Additional Information
Stacktrace: https://gist.github.com/marcoromelli/1ce708d929fd280b8c060353fbd996bc
Python code:
from keras.applications.resnet50 import ResNet50

model = ResNet50(weights='imagenet', include_top=False)
model.save('D:\\resnet50.hdf5')

Java code:
ComputationGraph model = KerasModelImport.
                importKerasModelAndWeights("D:\\resnet50.hdf5", false);

Confirmed. Let me look in to this, thanks!

@marcoromelli I fixed this here: https://github.com/KonduitAI/deeplearning4j/pull/521 Keep an eye out for an eclipse merge to master soon.


[BUG] Aggregate javadoc contains track 1 packages

Describe the bug
A clear and concise description of what the bug is.
API docs for Azure SDK contain track 1 packages and tabs - https://azuresdkartifacts.blob.core.windows.net/azure-sdk-for-java/staging/apidocs/index.html
This should only have packages and client library tabs that are part of track 2.
Exception or Stack Trace
N/A
To Reproduce
Steps to reproduce the behavior:
Go to the link below and look for package names starting with com.microsoft.azure.*
https://azuresdkartifacts.blob.core.windows.net/azure-sdk-for-java/staging/apidocs/index.html
Code Snippet
Add the code snippet that causes the issue.
N/A
Expected behavior
A clear and concise description of what you expected to happen.
Only track 2 packages should be shown in API docs.
Screenshots
If applicable, add screenshots to help explain your problem.
N/A
Setup (please complete the following information):

OS: Any
IDE : Any
Version of the Library used - N/A

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[] Setup information Added

Fixed - https://github.com/Azure/azure-sdk-for-java/pull/3893


[Slider] Major upgrade

This is a work in progress: 97% (44 hours): https://deploy-preview-15703--material-ui.netlify.com/components/slider/.

Closes #15803 - Change the DOM & CSS structure.
Closes #779 - Add support for range input.
Closes #11990 - Use the onChange(event, value) signature. It's not the first time we use it. It's also the one suggested in https://github.com/facebook/react/issues/9657.
Closes #12463 - I have done my best without making the implementation too complex.
Closes #12807 - We already support multi-touch.
Closes #13485 - The component doesn't have a name as it's not a native element, people have to account for it when using react-final-form or formik. However, I have added a hidden input for people who want to submit an HTML form.
Closes #13623 - I had to use a non-passive listener.
Closes #14469 - The thumb label was added for this use case.
Closes #14913 - This is an issue with react-swipeable-views. It could support a specific data- attribute for the problem. I don't think that the Slider should account for it.
Closes #15889 - Better handle the touch start event.
~- Closes #15802 - Expose a popperRef prop.~
Related to #14674 - I'm not sure about this one, hence it's the last one listed. I would like you feedback on it @eps1lon. I was thinking of: we keep onChange for consistency with the other components. We introduce an onAfterChange prop for the case described:

How I understand the use cases of the onDrag* events is to start validation or some other expensive operation only after the user has ended the drag.

Then, we wait for https://github.com/facebook/react/issues/9657 to migrate all our input components.

What's the use case [for multi-touch]?

An audio mixer or lighting controller with vertical sliders, where you wish to control multiple outputs at once?

Niche, but not beyond the bounds of possibility.

The component doesn't have a name as it's not a native element

<input type="range" /> ?

@mbrookes Ok, I will add the support back.

I wouldn't close #14674 at this point. As I understood React Fire onChange will be going away at which point this will make more sense. I would suggest onCommitChange however which is a more verbose name for how onChange actually works.

@oliviertassinari This looks great! I actually just found out today about a client request where they want a slider for something in our app.
Are you planning on providing any support for Value entry field in the initial version?

@ryancogswell It probably still need a day of work. I don't see anything specific with the value entry case. I have the following so far: https://deploy-preview-15703--material-ui.netlify.com/components/slider/.

I don't see anything specific with the value entry case.

@oliviertassinari Sorry, I'm not sure I understand what you're saying. Are you saying you aren't doing anything yet for the value entry case, or that you don't see anything in the spec about the value entry case (i.e. ability to do text entry of the value when the slider has focus), or that you don't think this case needs anything specific within Slider to support?

I don't think that it needs anything specific within the Slider support. What prevents you from implementing in it, today?

What prevents you from having this use case with the existing lab component?

@oliviertassinari I'm sure it's possible, but there are enough layout/styling concerns and potential complexities with tapping into the onKeyDown of the Slider and determining when to register a change to the Slider and honoring the step of the Slider, that it would be valuable for the component to take care of all of that for the user. We'll probably want the text entry option in our app, so I'll eventually find out how much is involved; though, at least initially, I'll probably avoid the complexity of trying to have text entry work when focus is on the thumb.

OK, I will add a demo. It should be about 1. Using the Grid component, 2. Using a debounce on the input changes. 3. Using the step prop for the input number type.

I have fixed all the problems I could stop. I believe it's good enough to move forward.

I have ignored it on purpose. I have yet to see it implemented on a Google product. I believe it's one of these cases where we can simplify things by giving up a few of the details. Anyway, I believe we can look into the problem later on. We can live without for now.

I have a problem with introducing regressions on purpose in an already bloated PR.

But, why? Should the thumb stays activated after click or not?

It's another regression from previous behavior and the spec

Let me know if you want me to split it,

Please do.

I have already spent so much time on this pull request

It's why smaller PRs are recommended or rather atomic commits in PRs. It would make splitting up trivial.

I have a problem with introducing regressions on purpose in an already bloated PR.

I haven't realized it was a regression, let me dive into it. We are probably not mentioning the same thing.

It's another regression from previous behavior and the spec

I'm gonna have a closer look at the specification.

Please do.

I'm on it. I'm gonna isolate what I can.

It's why smaller PRs are recommended or rather atomic commits in PRs. It would make splitting up trivial.

The problem here is that I need to get all the fundamental features to work to validate the integration of all the parts. We can't always reach an optimal solution with small incremental changes. Sometimes, it requires a large jump. Now, I agree, we have to avoid it, when we can!

This is not directly related, but it makes me think of Apple vs Google. Apple didn't come up with the Mac, iPod, and iPhone with small incremental changes. At some point, they have stopped looking at the data and optimizing them. Instead, they tried to use their taste and critical thinking to envision something better. In the 19 century, ask people what they want, they will tell you faster horses, not cars.

@oliviertassinari Nice job!
I'm focusing on functionality rather than code – I see @eps1lon has already given that a once-over, which he is far better qualified to do!
I agree with @eps1lon about the jump transition. It was one of the first things I noticed (back before you requested a formal review).
Disabled slider
For the disabled slider, in the spec there is a gap between the thumb and the track. It is there in the current implementation, but smaller than the gap in the v2 spec. The new implementation doesn't have it:
Spec:

Current MUI Slider

New MUI Slider

Discreet slider
Tick marks
In the spec, the discreet slider has steps at uniform intervals, optionally indicated by tick marks:
Spec:

While the new "discrete" demo has an interesting take, by allowing non-uniform tick-marks with additional labels, that's an advanced use-case:
New MUI Slider

Consider allowing marks={true} to enable tick marks for discrete sliders.
Value label
Referencing the images above, in the new implementation, the value label appears to be mandated for discrete sliders, whilst in the spec it is optional:

There seems to be an issue where the value label gets stuck open, even when the slider isn't focused:

(Top slider is focused, bottom one was previously focused. Not sure of the steps to reproduce though...)
Demo
The demo needs a description of what differentiates the three sliders, but first let's figure out what the demos should be, and how they should behave.  IMHO The discrete demo should match the spec: Slider with uniform discrete steps, and with or without tick marks and value label.
The custom tick marks spacing and tick mark labels should follow as and "advanced" demo.
Range slider
The range slider demo is a bit of an odd hybrid, by throwing in non-uniform discreet tick marks (and non-spec tick mark labels) on a non-discreet range slider. The interaction between the lick mark labels and the sliders is also hit-or-miss.
I suggest dropping the tick marks from this demo.
Customized sliders
Not the focus of this PR, but since the refactor enables it, the second demo can now have its track ends rounded.
With input field
Having a discrete slider combined with an input seems odd, since you can select values with the input that you can't with the slider.

For a discrete slider, input values should snap to the nearest discrete value.

Also:

If the Slider is at 0, the input can't be set to sane values.

The Input can be set to values outside the range of the slide.

Custom value reducer
What is the migration path?

@mbrookes Thanks for the review.

Disabled slider

Not implemented on purpose. I can't think of a way that would bloat the implementation.

Consider allowing marks={true} to enable tick marks for discrete sliders.

This is something considering worth implementing 👍. Uniform marks might be as valuable as the custom ones.

the value label appears to be mandated for discrete sliders, whilst in the spec it is optional:

It's optional

IMHO The discrete demo should match the spec: Slider with uniform discrete steps, and with or without tick marks and value label.
The custom tick marks spacing and tick mark labels should follow as and "advanced" demo.

I would advocate for the advanced demo to be a better default. But I'm happy to document a uniform version too.

I suggest dropping the tick marks from this demo.

Ok, we can simplify the demo to focus on the range. It was done this way to manually test the active tick style, but a unit test would be better.

the second demo can now have its track ends rounded.

Great idea.

With input field

I hope I can solve these problems with a blur cleaning logic on the input.

Custom value reducer

I have failed to see the use case of this feature. Can somebody explain the problem it uniquely solves?

I have failed to see the use case of this feature. Can somebody explain the problem it uniquely solves?

#12665
It was used for custom behavior when min/max/value and step didn't align perfectly. It was better to invert control here (for bundle size and because default behavior wasn't clear).

I believe we have only 3 points of concern left in order to merge:

It was used for custom behavior when min/max/value and step didn't align perfectly. It was better to invert control here (for bundle size and because default behavior wasn't clear).

@eps1lon Thanks for the context, do you think that I should reintroduce this prop? I believe the initial issue is handled right now: #12494, people can go from the min to the max value. Now, Ant went with the opposed default behavior: https://codepen.io/anon/pen/byybbL?editors=0010 (but I doubt it was done on purpose).

no more jump transition when clicking on the rail on discrete sliders

thumb stays activated after click

I have looked at the specification more closely, I believe these are two different sides of the same coin. Matt has raised the same concern, Ant does it this way too and the specification encourages this behavior. I was hoping I could get away with the browser :active state, it seems I can't.
I'm on it.

I have extracted some changes to minimize the size of this pull request, I will rebase on #16061 and #16069.

Bonus:

We can improve the demo documentation descriptions.

Just noticed that in the v3 spec, the track ends are rounded by default:

do you think that I should reintroduce this prop?

I'm ok with removing it and waiting for a reaction (it's in alpha for that purpose). I saw one package (react-slider?) that specifically warned against using values that don't align properly. But I never liked the old implementation anyway (too many ifs) so this is a good opportunity to get rid of some old code and see if we can improve later.

@mbrookes Correct, you have an 🧐 for the details. I will also try to round the mark's ticks.
@eps1lon This sounds like a great plan.

Just noticed that in the v2 spec, the track ends are rounded by default:

@mbrookes I hope that cd7236c solves it. Could you also have a look at the new discrete sliders? Any idea for the demo description?
I have tried to handle the point n°2. I have introduced an active custom pseudo-class and an open prop. It's much better like this. Thanks for pushing. However, I haven't handled the slider change animation, it's instant, I also haven't handled the pulsating keyboard effect. If you agree, we can come back to it later, once we have more component.
I would propose this strategy for the components we miss. We could seed the foundations while leaving the polishing ✨ for later. This way, we can enable small incremental contributions from the community.

Alright, I believe that we are good to go! 🛫 At least, for one trip.

Almost! 😉
Label clash, and demo descriptions? (what's the difference between them, and what prop makes the difference), per yesterday's discussion...

Label clash

I have added some spacing in b0ec4733f9d82edf7c629d6b0c0c25fe9e920bf1

demo descriptions

I'm on it.

I have added some spacing in b0ec473

That screenshot is from the latest build...

I have tried to optimize these two dimensions:

The smaller the spacing value is, the more conflict between the demos there is, the more overlapping that can create confusion
The smaller the spacing value is, the fewer distance the users need to travel to quickly interact with each demo, the less space the demo takes (higher density).

The current tradeoff is to increase the value at which point, there is no static conflict.

there is no static conflict.

Conflict is conflict.
If a user has difficulty moving a mouse ten pixels, they are probably a keyboard user anyway.

I have changed the default values and restructured the customizations:

Alright, it's ready for a new wave of review. There is one point I have just asked myself. Should we change the pathname from /components/slider/ to /components/sliders/? I believe that we do for consistency with the other components.

It isn't completely consistent, but the plural is in the majority for sure.

The Slider with input still has an issue. If the slider value is zero, you can't delete the zero when editing the input.

It isn't completely consistent

@mbrookes Oh boy, I have just looked at the problem in more detail, it's! 😞 I wish we handled it before changing all the pathnames (/demos -> /components). I won't change anything here. We need to agree on a global direction first.

The Slider with input still has an issue. If the slider value is zero, you can't delete the zero when editing the input.

Thanks, it's fixed.

Multi touch support would be a really good feature.

What does multi-touch support exactly mean? We have the following behavior.
People can slide two different sliders at the same time with two fingers.
People can't slide two thumbs of the same range slider with two fingers.

Slider is still in an active state after click.

Do you mean in the hover/focus state instead? It's not active. But I agree. We should add a focus-visible logic for the desktop & mobile and a media hover: none logic for mobile.

This is not required if the value matches the semantics of the label

Correct. We should reword this part of the accessibility guideline.

I would prefer controlled demos over uncontrolled ones so that users can see better how they can read/write the values.

Let's see what I can do about it.

Do you mean in the hover/focus state instead? It's not :active. But I agree. We should add a focus-visible logic for the desktop & mobile and a media hover: none logic for mobile.

The active state from the guidelines and still focused. It should not be focus-visible after a click.

@eps1lon What does multi-touch support exactly mean?

I didn't read the issue. I just see that this is an open issue that you close with this PR while saying you didn't address it. That can be misleading for people reading the issue.

@eps1lon I should have handled all your feedback.

After clicking it still responds to keyboard input. This is a regression from the previous version and doesn't follow wai-aria authoring practices.

After clicking it still responds to keyboard input. This is a regression from the previous version and doesn't follow wai-aria authoring practices.

@eps1lon I don't understand, can you clarify? In the following. The value starts around 0, I click around 80%. I press the up key command, then the down key command two times.
<input type="range />

<Slider />

Yeah you understood it. Native browser implementation is not following wai-aria as well. If there's a W3 spec for that behavior we can keep it (but need to display label again). So far browser implementations are most often not following specs or are different between vendors. They shouldn't be the most important reference.

After clicking it still responds to keyboard input.

@eps1lon Can you clarify what the desired behavior is and which wai-aria authoring practices you are referring to? The wai-aria example (https://www.w3.org/TR/wai-aria-practices/examples/slider/slider-2.html) seems to behave the same way unless I'm misunderstanding what aspect you are focusing on.

Can you clarify what the desired behavior

@eps1lon I just answered my own question with a little experimenting.
To clarify for others, in the wai-aria example, if you click on the Slider thumb then keyboard focus is placed on the Slider (same as in this branch), but if you click elsewhere on the Slider it just changes the Slider position without giving it focus.
When I was trying to understand your point, I was clicking on the thumb and dragging it to change the value and then using the keyboard to change it further. In that case keyboard focus behaves the same for the wai-aria example and this branch.

There's no visual indication that the thumb is focused (i.e. no focus-visible) until a key is pressed after clicking on the rail. You can see this in Oliviers video.
Basically clicking the rail should/did not focus the thumb. If that behavior is described in the W3C spec we should stick to it but make the focus-visible styling consistent. But so far this is a regression from previous behavior and wai-aria authoring practices.

There's no visual indication that the thumb is focused (i.e. no focus-visible) until a key is pressed after clicking on the rail.

@eps1lon I more fully understand what you're getting at now, but it is still unclear to me whether there is a problem with the new behavior.
There are two main questions to answer:

Should the focus-visible styling be in effect when receiving focus via a mouse click?
The answer to this for buttons has been "no". Clicking a button gives it keyboard focus, but does not give it focus-visible styling; whereas tabbing to a button gives it focus-visible styling. The current behavior in this branch is consistent with that approach and it makes sense to me that the focus-visible styling would then turn on when you do further interaction with the slider via the keyboard.

Should clicking the rail give focus to the slider?
The wai-aria example only gives focus to the slider when clicking on the thumb and not when clicking on the rail, but the design guidelines don't say anything about this aspect. Either behavior (giving focus only when clicking on the thumb vs. giving focus when clicking on the thumb or the rail) seems reasonable to me.

I support @ryancogswell points here. In the light of contradictions between different sources, I think that we should follow them in this order:

The wai-aria written recommendations
The browser behavior, what I have shown with macOS and Chrome can be reproduced with Windows 10 and Edge. Two very different environnements. What I haven't tried but would love to is: old school heavy Windows application. How does a Slider behave on Qt, something that have been around for decades?
Wai-aria examples behavior
Other libraries behavior

I propose that we discuss this in a separate issue. I would put the W3 spec above all the points listed above and move browser implementation to the bottom (again those have proven to be a bad reference for normalized behavior) but we can compare this at length later.

Should we raise the problem in https://github.com/w3c/aria-practices/issues?

This is one step further. We are not done yet!

@oliviertassinari @eps1lon where did jumped pseudoselector go?

@Astrantia This jumped custom pseudo-class was removed. This was an attempt to simplify the component. Could you describe your use case for using it?


RKE Cluster thats provisioned from Cluster Explorer and is in Provisioning state does not show up in Cluster Management --> Clusters page

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):
On master-head commit id: 8c014ef

Navigate to cluster explorer --> Home --> Cluster Management
Click on Create cluster --> choose RKE
User is presented with options - RKE vs RKE2
Select RKE
Create a cluster - Any, say GKE/Amazon EC2
provide details and click on Create.
Cluster is not seen in the list in Clusters page.
Though it will be seen disabled on the left pane under Cluster Explorer.

Expected:
When the cluster is deployed, it should be available in the list of clusters displayed in the Clusters page.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head commit id: 8c014ef
Installation option (single install/HA): Single

On master-head commit id: f90b36e

Navigate to cluster explorer --> Home --> Cluster Management
Click on Create cluster --> choose RKE
User is presented with options - RKE vs RKE2
Select RKE
Create a cluster - Any, DO
provide details and click on Create.
Cluster is seen listed in Clusters page.
Wait for the cluster to coome up Active, the Explorer button is enabled and user is able to Navigate to the explorer page of the cluster.


Fix csv_from_result if contain newline

If $item is a column with a newline inside, the old version create a newline in a result file, breaking the csv.
This fix replace any newline with a new parameter : $newline_delim

Sorry, but I don't see how the issue that you're describing could happen. Can you give an example?

This function take a sql query in parameter, read it and parse it in CSV.
If in a table there is a line (for example a varchar() or text()) containing a newline, this newline is printed into the result file and break the csv.
Example :
table db.item :
| id | name | description
| 1 | example | This is a description with a newline \n this is the second line
| 2 | another | another description
This is the result :
"id";"name";"description"
"1";"example";"This is a description with a newline
this is the second line";
"2";"another";"another description";
Please note there is 4 lines instead of 3 (2 + head)
The csv is break

That's perfectly valid CSV ... of course a newline character would be rendered as a new line by a text editor, that doesn't mean it's broken.


Consider refactoring code to save GAS

@mg6maciej suggested: https://github.com/0xcert/ethereum-erc721/pull/109#pullrequestreview-131429069
If we do this, we should do it everywhere where this is applicable.

I did a few tests around this to see what is the most gas optimal way to calculate. Here are the results:

Option tested
Gas cost of mint function

push tokens then get index with: tokens.length.sub(1)
158760

push tokens then get index with: tokens.length - 1
158665

get lenght as a result from push then calculate index as -1 from that lenght
158465

get lenght as a result from push then calculate index as .sub(1) from that lenght
158560

first get lenght then push token then just set the lenght
158672

As you can see the suggested way is indeed the most GAS efficient. The subtraction is done after push so there is no need to use safemath library for the subtraction.
As such we will do this change everywhere where it is applicable. PR coming soon.


[Bug] Strings missing for translate from English to other langs

Describe the bug
I found a few strings for translation that I couldn't find on crowdin.com. So far, I've noticed a few, and if there are any left lately, add directions to where they are.
This is for Serbian language.
How to reproduce
This strings are in backend.
Expected behavior

This is in service details: Renewal date in 365 day(s) = in 365 day(s) missing for translate
This is in user Services invoices: Pending Setup = Pending Setup missing for translate
This is in user Services invoices: Manage = Manage missing for translate
This is in user Invoice: Invoice #IDnumber = Invoice #IDnumber missing for translate
This is in Admin backend: Order Management = -- Select status --, Pending setup, Setup failed, Active, Suspended, Canceled missing for translate
This is in Admin backend: Order Management - Order status history = Order created, Order activated, Order could not be activated due to error: Only pending setup or failed orders can be activated missing for translate
This is in Admin backend: Recent clients activity tab = Checked out shopping cart missing for translate
This is in Admin backend: Recent clients activity tab = 13 minutes ago = 13 minutas pre (this is wrong translation) missing for translate
This is in Admin backend: Recent clients activity tab = Approved invoice "22" missing for translate
This is in Admin backend: Recent clients activity tab = Prepared new invoice "22" missing for translate
This is in Admin backend: Recent clients activity tab = Added "DNS Start" to shopping cart missing for translate
This is in Admin backend: Recent clients activity tab = Checked out shopping cart missing for translate
This is in Admin backend: Recent clients activity tab = Removed product from shopping cart missing for translate
This is in Admin backend: Recent clients activity tab = Removed product addon from shopping cart missing for translate
This is in Admin backend: Recent staff activity tab = Marked invoice "21" as paid missing for translate
This is in Admin backend: Recent staff activity tab = Activated order #28 missing for translate
This is in Admin backend: Recent staff activity tab = Updated invoice "21" missing for translate
This is in Admin backend: Recent staff activity tab = Updated payment gateway ClientBalance missing for translate
This is in Admin backend: Recent staff activity tab = Logged in as client #2 missing for translate
This is in Admin backend: Recent staff activity tab = Updated FOSSBilling from 0.6.2 to 0.6.3 missing for translate
This is in Admin backend: Recent staff activity tab = Updated system general settings missing for translate
System Settings all strings: Client, Scheduled Tasks, Currency, Email, Invoices, Orders, Staff, Support, System, Theme, Order Button, Form Builder, Redirect, Wysiwyg, Paid support module missing for translate

Screenshots
No response
FOSSBilling version
0.6.3
FOSSBilling instance ID
No response
Module version
No response
Device
Desktop
Information
No response
Additional context
No response

PDF invoice file also need translation for this strings:
Invoice number]: RH00020 - This is also bag number**]:**
Invoice date: 18.12.2023
Due date: 23.12.2023
Invoice status: Unpaid
Quantity & Price

We already have a roadmapped item to fix and fix all untranslatable strings and I've gone ahead and added a comment linking to this there.
So we can keep things centralized, I'd appreciate it if you could add any more items you discover to #1681 via a comment. I'm going to close this as a duplicate of the larger issue.

PDF invoice file also need translation for this strings:

I just need to sync the latest sources with Crowdin for the Invoice PDFs, which I'll do soon.

This is in Admin backend: Order Management

It might be easier to give the URI to where the source translation is rather than trying to describe it, but what you've done so far still works fine if you prefer to do that. ( Example: /admin/order/manage/9).

This is in Admin backend: Recent clients activity tab

There's also probably not any reason to list the activity strings as I don't believe a single one of those are translatable, which is known.

System Settings all strings: Client, Scheduled Tasks, Currency, Email, Invoices, Orders, Staff, Support, System, Theme, Order Button, Form Builder, Redirect, Wysiwyg, Paid support module missing for translate

These are module names which are untranslatable, which is known.
Thanks!


401 Remove top-level directory from extracted files if it has only single child

Description
Removes top-level directories from extracted files if its only child is a directory.
This top-level directory in the archive is unnecessary and creates longer file paths than needed.
Fixes issue #401
Implemented changes

[ ] Remove top-level directories by default in Dataset.extract(), dataset_download.extract_dataset() and utils.archives.extract_archive().

Type of change

[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

[ ] tests/utils/archives_test.test_extract_archive_destination_path_None()
[ ] test_extract_archive_destination_path_not_None()

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

@josephine-funken thank you for this great work! there seems to be a merge conflict which needs to be removed first -- if you have any questions how to resolve it feel free to reach out.

Added functionality to remove top-level directories to downloads.download_and_extract_archive() and added parameter to corresponding test.


Failed building wheel for grpcio

Env:
docker image: paddlepaddle/paddle:2.5.1-gpu-cuda12.0-cudnn8.9-trt8.6
python: python10
In this dokcer, pip3 install https://paddle-serving.bj.bcebos.com/test-dev/whl/paddle_serving_server-0.9.0-py3-none-any.whl will failed by grpcio<=1.33.2

i have same problem. are you solve this problem?

Google has resolve arm grpcio install error since 1.51.3
the requirements.txt SHOULD consider to update

we will update requirements.txt, you can try pip install --upgrade grpcio to fix this bug temperally


kedro-telemetry inserts apparently malformed project UUID in pyproject.toml

Description
As per title
Steps to Reproduce
$ mkdir kedro-telemetry-test && cd kedro-telemetry-test
$ uv init
$ git init && git add . && git commit -m 'First commit'
$ cat pyproject.toml
[project]
name = "kedro-telemetry-test"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
requires-python = ">=3.12"
dependencies = []

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"
$ uvx kedro-init .
$ uv add kedro
$ git diff
diff --git a/pyproject.toml b/pyproject.toml
index 137a622..f54fea7 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -4,8 +4,15 @@ version = "0.1.0"
 description = "Add your description here"
 readme = "README.md"
 requires-python = ">=3.12"
-dependencies = []
+dependencies = [
+    "kedro>=0.19.8",
+]

 [build-system]
 requires = ["hatchling"]
 build-backend = "hatchling.build"
+
+[tool.kedro]
+project_name = "kedro-telemetry-test"
+package_name = "kedro_telemetry_test"
+kedro_init_version = "0.19.8"
$ git commit -am 'Init Kedro project'
$ uv run kedro registry list
[08/23/24 09:09:01] INFO     Using                                 __init__.py:249
                             '/private/tmp/kedro-telemetry-test/.v
                             env/lib/python3.12/site-packages/kedr
                             o/framework/project/rich_logging.yml'
                              as logging configuration.
[08/23/24 09:09:03] ERROR    Failed to retrieve UUID: badly formed    plugin.py:81
                             hexadecimal UUID string
- __default__

                    INFO     Kedro is sending anonymous usage data   plugin.py:233
                             with the sole purpose of improving the
                             product. No personal data or IP
                             addresses are stored on our side. If
                             you want to opt out, set the
                             `KEDRO_DISABLE_TELEMETRY` or
                             `DO_NOT_TRACK` environment variables,
                             or create a `.telemetry` file in the
                             current working directory with the
                             contents `consent: false`. Read more at
                             https://docs.kedro.org/en/stable/config
                             uration/telemetry.html
[08/23/24 09:09:04] WARNING  Failed to send data to Heap. Response   plugin.py:336
                             code returned: 400, Response reason:
                             Bad Request
  /tmp/kedro-telemetry-test  main !1 ?4 ·························  9s 09:09:0
❯ git diff
diff --git a/pyproject.toml b/pyproject.toml
index f54fea7..34ee2a9 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -16,3 +16,6 @@ build-backend = "hatchling.build"
 project_name = "kedro-telemetry-test"
 package_name = "kedro_telemetry_test"
 kedro_init_version = "0.19.8"
+
+[tool.kedro_telemetry]
+project_id = "f720f1725912435fac4b08f43baac591"

Expected Result
With the project_id that kedro-telemetry itself inserted, the request should work.
Actual Result
It says "badly formed hexadecimal UUID string" but I didn't touch it...
(The HTTP 400 error shouldn't happen anyway and is reported at #815)

@astrojuanlu you're not using kedro new for project creation right? Can you explain what these steps do:
uvx kedro-init .
uv add kedro

I just created a project like this: kedro new --name=test-telemetry --tools=none --example=n
and replaced the created project id with the one here in the ticket project_id = "f720f1725912435fac4b08f43baac591" and it works fine.. 🤔

Uh interesting... let me dig a bit more.
For context

uvx kedro-init . applies my https://github.com/astrojuanlu/kedro-init to the existing project (a mostly empty pyproject.toml)
uv add kedro is roughly uv pip install kedro

Weird @merelcht , I did
kedro new --name=kedro-telemetry-test-starter --tools=none --example=n
cd kedro-telemetry-test-starter
kedro registry list

and I got the same error. The generated project_id in this case is 378344bf0a694d55bd24f99bca448bf6 🤔
I'll do some more debugging as soon as I have some time.

@astrojuanlu I tried it all again in a fresh conda environment and can still not reproduce your error... So strange! Could there be something going on with your "top-level" telemetry UUID?

OMG you're right, this is about the user UUID and not the project UUID...
cat '/Users/juan_cano/Library/Application Support/kedro'/telemetry.toml
[telemetry]
uuid = ""

Error was originating from
https://github.com/kedro-org/kedro-plugins/blob/f7dccf9ecc70448b2fe8679d5cd9ae5b7bf27332/kedro-telemetry/kedro_telemetry/plugin.py#L81
Sorry for the noise. Closing.


Update privacy policy

Update Privacy Policy for napari hub with language provided here: https://docs.google.com/document/d/1oRd_6o4HgsRJTIWnNccDYR3dSCCbJxhlvI2ScNr3A0k/edit#heading=h.n43g0ufvgqwz

Reference for one-liner blurb
https://github.com/chanzuckerberg/napari-hub/pull/690

Link to PR: https://github.com/chanzuckerberg/napari-hub/pull/904

Closing this out as it was deployed with today's release - FYI @EricMaxWang

Thanks all!


Course Dashboard - Scrolling gets disabled sometimes

Description
LEARNER-2873

Codecov Report

Merging #1021 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1021      +/-   ##
==========================================
+ Coverage    45.7%   45.71%   +<.01%
==========================================
  Files         409      409
  Lines       27139    27140       +1
==========================================
+ Hits        12405    12406       +1
  Misses      14734    14734

Impacted Files
Coverage Δ

Source/CourseDashboardViewController.swift
72.92% <100%> (+0.11%)
:arrow_up:

Continue to review full report at Codecov.

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


Added domain @fci.suezuni.edu.eg Suez University

University name: Suez University
City: Suez
Country: Egypt
Faculty: Computers and Information (Computer Science)
Website: https://suezuni.edu.eg/index.php/en
Proof with a screenshot is attached.

@AbdoMosa99 I am sorry for a delay with processing your request.
Pull request merged. Thank you!

Thanks so much.
On Fri, Dec 31, 2021, 1:23 PM Philip Torchinsky @.***>
wrote:

@AbdoMosa99 https://github.com/AbdoMosa99 I am sorry for a delay with
processing your request.
Pull request merged. Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/13193#issuecomment-1003350814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI2S6G454DF2UHJXKNMMIJTUTWHCPANCNFSM5KPZRNQA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


WAN over PPPOE - default Route is not set

Hi,
im using PPPOE for my WAN - if its the default gateway the IPv4 default is not set.
The Default IPv6 is set corect

Andreas, the problem with your reports is that they miss vitual informations. Please read the following and report back:
https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
It's simply not possible to help with no information about your setup, logs, etc.

I'll still need version info and additionally a dump of the following file(s), but careful with embedded credentials...
# ls /var/etc/mpd_*.conf

i will sent you an email

any news with the infos from my email?

Experimental patch at b349470, it looks like a missing Multi-WAN awareness issue.

This is on the 17.1 development track for now (opnsense-devel package under 16.7)

I haven't heard of further problems from @andreasvel and it's currently queued up for inclusion in 16.7.1. Thanks!

Its there again.. :-1:
on OPNsense 16.7.3-amd64

The bug is back now too in OPNsense 16.7.13-amd64
If I set:
route add -net default -interface pppoe0
everythings works but any change in config (such as in Web Proxy removes the IPv4 default route manually added previously.

It looks like "the" bug never went away completely, looking like a narrow race condition, which makes this hard to trace with the amount of additional info provided.
17.1 is almost out, featuring a new FreeBSD version. If anything we need to see how it performs there and think about what can be done?

I had this today. I couldn't figure out why it could not ping, traceroute, or connect to anything on the Internet. If i forced the use of WAN interface it would work fine.
Finally i found the routes screen. The default route is set to go the physical WAN port, rather than the PPPoE virtual port:

Now could i find anything in the UI to repair, reset, change, or fix it. So i had to yank the live USB stick and revert to pfSense.

I couldn't find anything in the UI to repair, reset, change, or fix it.

How about release/renew the PPP lease from the Interfaces: Overview page? Or saving/reapplying the WAN configuration? Or console option 11 or reboot... ;)

I did disconnect the PPPoE connection, so the WAN interface was down; and then connected it again
I did re-save the WAN configuration; thinking (hoping) that it simply would fix itself

Strictly speaking i did reboot; but without the Live USB stick in. I'll try again tonight. I had to get the Internet back up before people started complaining too much.

 The wizard ran on first use because it was, by definition, a fresh install.
Same thing. The default route is set to go out the physical WAN port:

Unpluged the USB stick to revert to pfSense in order to wait for a fix.

@JackTrapper, can you walk me through your setup sequence? You use the wizard to configure PPPoE?

(in the context of this older bug, we have found some caching files that were never cleared, so that might have something to do this this no default gateway behaviour previously reported for when this was referencing 16.7)

So i plugged in the USB stick and booted it up again.
OPNSense 17.1.4
Welcome to OPNSense! Starting wizard.

Next

General information.

Next

Time Server Information.

Timezone: America/Toronto
Next

Configure WAN Interface

Selected Type: PPPoE
PPPoE Username: [redacted]
PPPoE Password: [redacted]
Next

Configure LAN Interface

Next

Set Admin Web GUI Password

Admin Password: [redacted]
Admin Password AGAIN: [redacted]
Next

Reload Configuration

Reload

Finished initial configuration!

Congratulations! OPNsense is now configured.
Click to continue to the dashboard.

You are currently running in LiveCD mode. A reboot will reset the configuration. SSH remote login is disabled.

How are the routes
So now it is setup. Lets check the routes
System -> Routes -> Status

Proto
Destination
Gateway
Flags
Use
MTU
Netif
Netif (name)

ipv4
Default
link#2
U
5083
1500
re0

ipv4
[ISP gateway IP redacted]
link#7
UH
0
1492
pppoe
wan

So it's using the wrong gateway as the default route. Lets try pinging.
Interfaces -> Diagnostics -> Ping

Host: <IP_ADDRESS>

IP Protocol: IPv4

Source Address: Default

Count: 3
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes

 --- <IP_ADDRESS> ping statistics ---
 3 packets transmitted, 0 packets received, 100.0% packet loss
 ping: sendto: Host is down
 ping: sendto: Host is down
 ping: sendto: Host is down

Fails. Lets force use of the WAN (i.e. pppoe0) interface:

Host: <IP_ADDRESS>

IP Protocol: IPv4

Source Address: WAN

Count: 3
PING <IP_ADDRESS> (<IP_ADDRESS>) from <IP_ADDRESS>: 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=51 time=24.503 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=51 time=24.306 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=51 time=28.037 ms

--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 24.306/25.615/28.037/1.714 ms

So if i force the use of the interface, the packets will go. It just doesn't realize the default route.
 What about pinging again
Interface -> Diagnostics -> Ping

Host: <IP_ADDRESS>

IP Protocol: IPv4

Source Address: Default

Count: 3
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes

--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down

Nope, still cannot ping using the default gateway.
Disable and re-enable the WAN interface
Lets disable the interface:
Interfaces -> [WAN]

Enable: [x] Enable Interface
Uncheck
Save
Apply changes

And re-enable it:

Enable: [ ] Enable Interface
Check
Save
Apply changes

And check the routes again:
System -> Routes -> Status

Proto
Destination
Gateway
Flags
Use
MTU
Netif
Netif (name)

ipv4
Default
link#2
U
12152
1500
re0

ipv4
[ISP gateway IP redacted]
link#7
UH
0
1492
pppoe
wan

Still the wrong route. And ping still fails:
Interfaces -> Diagnostics -> Ping

Host: <IP_ADDRESS>

IP Protocol: IPv4

Source Address: Default

Count: 3
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes

--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down

And again if i force the use of PPPoE interface directly, it works:

Host: <IP_ADDRESS>

IP Protocol: IPv4

Source Address: WAN

Count: 3
PING <IP_ADDRESS> (<IP_ADDRESS>) from <IP_ADDRESS>: 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=51 time=24.503 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=51 time=24.306 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=51 time=28.037 ms

--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 24.306/25.615/28.037/1.714 ms

Now to go back downstairs, pull the USB stick, let pfSense boot up, and put my nicely formatted, long, verbose, findings into Github markdown. Should be posted in about an hour.

7:43pm EDT

Current time: 8:03pm EDT (quicker than i thought)

Lots of progress here in the backgrounds, eventually cleaning up the IP renewal facilities for 17.7. 17.7-RC1 is out soon, please retest then.

So i finally tried 17.7 and it still happens: Even though the PPPoE interface is up, the default interface is out the physical WAN port - with traffic going nowhere.
System -> Routes -> Status

Proto
Destination
Gateway
Flags
Use
MTU
Netif
Netif (name)
Expire

ipv4
default
link#2
U
81208
1500
re0

ipv4
<IP_ADDRESS>
link#7
UHS
0
16384
lo0

ipv4
<IP_ADDRESS>
link#7
UH
0
1492
pppoe0
wan

**System -> Gateways -> Status

Name
Gateway
Monitor
RTT
Loss
Status
Description

WAN_PPPOE
<IP_ADDRESS>
none
0.0 ms
0.0 %
Online
Interface WAN_PPPOE Gateway

So what's needed to help get this fixed?
By definition i'm starting a fresh install - Live USB stick.
Somebody on the planet must understand why the operating system refuses to use the correct default route. Is there a logfile that opnSense needs to log to?


Update minimum macOS version as needed in Swift package

If Swift Package Manager is enabled, the tool generates a Swift package at <ios/macos>/Flutter/ephemeral/Packages/FlutterGeneratedPluginSwiftPackage/. This Swift package is how the tool adds plugins to the Flutter project.
SwiftPM is strictly enforces platform versions: you cannot depend on a Swift package if its supported version is higher than your own.
On iOS, we use the project's minimum deployment version for the generated Swift package. If a plugin has a higher requirement, you'll need to update your project's minimum deployment version. The generated Swift package is automatically updated the next time you run the tool.
This updates macOS to do the same thing.
Fixes https://github.com/flutter/flutter/issues/146204
Pre-launch Checklist

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

If you need help, consider asking for advice on the #hackers-new channel on Discord.

I verified google_sign_in_ios builds on macOS using this change and SwiftPM enabled.


KOGITO-5664 - Rename KafkaClient package to avoid Sonar conflict

Assembly:

https://github.com/kiegroup/kogito-runtimes/pull/1544
https://github.com/kiegroup/kogito-apps/pull/992
https://github.com/kiegroup/kogito-examples/pull/854

The (build) Runtimes check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

Jenkins rerun apps tests

Jenkins rerun examples tests

The (build) Examples check has failed. Please check the logs.

Jenkins rerun examples tests

The (build) Examples check has failed. Please check the logs.

Jenkins rerun examples tests


the python version of gpufit should be named "pyGpufit"

bearing in mind that there is already a package called "PyGPU"

I don't think it should. Python library names are mostly lowercase, almost never camel case. The py prefix or sufix is rather seldomly used. Just see http://www.lfd.uci.edu/~gohlke/pythonlibs/ or https://pypi.python.org/pypi?%3Aaction=search&term=gpu&submit=search for examples.
Possible namings:

gpufit
pygpufit
gpufitpy
pyGPUfit
GPUfitpy

My vote goes either to pyGPUfit or to gpufit, because everything else doesn't look and the pyGpufit looks even worse and doesn't comply with the capitalization rules we defined in #55.

we should follow PEP 8

I think gpufit is the best choice

For the module I prefer gpufit and it is already like this. It's all underscore as requested by PEP 8 and it is without the py prefix because I don't feel it's necessary or adds anything about when coding it except length.
The name of the Python binding however, i.e. the package name on PyPi can be different. In the name of consistency within the project we might want to call it gpufit, GPUfit or even pyGPUfit or something different. Package and module names do not have to be the same.

great.  I support pyGPUfit.
On 09/02/2017 13:15, jkfindeisen wrote:

For the module I prefer gpufit and it is already like this. It's all
underscore as requested by PEP 8 and it is without the py prefix because
I don't feel it's necessary or adds anything about when coding it except
length.
The name of the Python binding however, i.e. the package name on PyPi
can be different. In the name of consistency within the project we might
want to call it gpufit, GPUfit or even pyGPUfit or something different.
Package and module names do not have to be the same.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gpufit/GPUfit/issues/72#issuecomment-278625274, or
mute the thread
https://github.com/notifications/unsubscribe-auth/ADb8MRDtTAa7366IxrVLFGsNmDfhdr6Dks5rawN3gaJpZM4L4Rhi.

fine, then gpufit it is for the module name and pyGPUfit for the package.


Connection to fulcrum fails.

I tried with both electrum and sparrow.
Electrum does nothing at all,
Sparrow shows : "Could not connect: Failed to parse server certificates"  Could be nothing.
Fulcrum logs show no connection attempt at all.
The fulcrum logs show it's listening? but to <IP_ADDRESS>
<Controller> Initial sync ended, flushing and deleting UTXO Cache ...
<Controller> Storage UTXO Cache: Flushing to DB ...
<Controller> Block height 792911, downloading new blocks ...
<Controller> Processed 372 new blocks with 1005712 txs (2422684 inputs, 2810080 outputs, 3521969 addresses), verified ok.
<Controller> Block height 792911, up-to-date
 SrvMgr: starting 1 service ...
 Starting listener service for SslSrv <IP_ADDRESS>:50002 ...
 Service started, listening for connections on <IP_ADDRESS>:50002

I deleted the config line
ssl=<IP_ADDRESS>:50002
And FINALLY got that thing to get connected to!

Given the sample config, Seems like this adding this one only risk having benefits.
# *RECOMMENDED* - TCP bind - 'tcp' - DEFAULT: <IP_ADDRESS>:50001, Specifies the IPv4
# or IPv6 interface:port to bind to.
tcp = <IP_ADDRESS>:50001

New electrum wallet in Parmanode.
It will connect to Fulcrum with SSL. You need to run Electrum from the Parmanode menu for it to work.

No matter what I did, Couldn't have electrum connect to either 50001 or 50002
Apparently we needed to append a :t at the end, GO FIGURE!
https://community.getumbrel.com/t/connecting-electrum-to-electrum-server-without-tor/1097

Yes, tor info here could be useful
https://armantheparman.com/tor/

Your chatgpt link doesn't work.
When using electrum, connection can be "assured" if you delete the certs and sockets from the hidden electrum directory. Parmanode takes care of it if you run Electrum from the menu.

public GPT link died when I deleted the chat,
260  openssl genrsa -out myprivatekey.key 2048
261  ls
262  openssl req -new -key myprivatekey.key -out myCSR.csr
263  ls
264  openssl x509 -req -days 3605 -in myCSR.csr -signkey myprivatekey.key -out mycertificate.pem

Somehow figured out I had to enter 50002:s at the end for it to connect to SSL.

Sparrow or electrum?

Sparrow or electrum?

The :t and :s are with Electrum. They're replacement for a SSL toggle.  :t is the only way to use it with 50001 port.
Apparently :s is assumed by default but it wasn't working for me until I added it manually, Then it just disappear but stay visible on mouse-over.

https://github.com/spesmilo/electrum/issues/8472
Apparently it's not recommended to use the oneserver=true, Seems like there's very little privacy leak, none related to addresses lookups.

Apparently it's not recommended to use the oneserver=true
I recommend the opposite. Don't trust.
On Tue, 6 June 2023, 3:37 am nostitos, @.***> wrote:

Sparrow or electrum?
The :t and :s are with Electrum. They're replacement for a SSL toggle.
:t is the only way to use it with 50001 port.
Apparently :s is assumed by default but it wasn't working for me until I
added it manually, Then it just disappear but stay visible on mouse-over.
[image: image]
https://user-images.githubusercontent.com/48504624/243430041-3fd2eb03-7806-4c18-be06-6001a8c65313.png
spesmilo/electrum#8472 https://github.com/spesmilo/electrum/issues/8472
Apparently it's not recommended to use the oneserver=true, Seems like
there's very little privacy leak, none related to addresses lookups.
—
Reply to this email directly, view it on GitHub
https://github.com/ArmanTheParman/Parmanode/issues/19#issuecomment-1577204860,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASQCCX6FN3FFFLSYB7STUF3XJYKMPANCNFSM6AAAAAAY2LY7XI
.
You are receiving this because you commented.Message ID:
@.***>


customer identified updates

There was an error while validating job 0569017d-959f-4939-aab3-baaedb51d0c9 Message:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
Details:Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase+ContextCommandException:
Result status: Failed
There was a problem accessing Github repository 'https://github.com/Microsoft/cordova-docs.git'.
---> System.AggregateException: One or more errors occurred. ---> System.ArgumentException: Error clonning repository ---> LibGit2Sharp.NotFoundException: Branch 241 not found. Available branches: origin/master
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetBranch(Repository repo, String name)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass30.<>c__DisplayClass34.b__29(KeyValuePair2 branch)    at System.Collections.Generic.List1.ForEach(Action1 action)    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass30.<CloneRepository>b__28()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.<>c__DisplayClass1.<ExecuteAction>b__0()    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction[TResult](Func1 func)
at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction(Action action)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)    --- End of inner exception stack trace ---    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository()
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetVersionAsync(String path)
at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)    --- End of inner exception stack trace ---    --- End of inner exception stack trace ---    at Microsoft.LightweightJobEngine.Core.Language.ContextCommandBase.ThrowIfErrorsLogged()    at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.CheckExternalServicesCommand.Do(IDictionary2 context)
at Microsoft.LightweightJobEngine.Core.Language.JobWorkflow1.RunCommands(Guid jobId, IDictionary2 context, CancellationTokenSource cancelSignal)


Repeat the process

Good afternoon, how are you? I would like to know how to make the bar repeat when reaching 100%?

asd

asd

askcnasc

salam

hi

how are you?

this is a test

asdasd

asd

lolo

aloooo

ada

in dge shod

holss

qweqwe

asd

asdacvvvvvvvvvvvvvvvvvv

asdasdaacascascascascasc

qwe

dddaaa

aloooooooooooooooo

khodayaaaaa

ahaayyyy

shod engarrrr

dddaaa


pkgs-lib.formats.xml: init

Description of changes
add XML export format. beneficial for https://github.com/NixOS/rfcs/blob/master/rfcs/0042-config-option.md
tested via: nix-build . -A tests.pkgs-lib.formats
sonarr can be improved to have settings e.g.: https://github.com/NixOS/nixpkgs/compare/master...Stunkymonkey:nixpkgs:exportarr-sonarr-test. which can be tested via nix-build . -A nixosTests.prometheus-exporters.exportarr-sonarr
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

not sure where to note the badgerfish-notation.

I'm wondering whether something could/should be done to ensure we can order attributes properly and still have control of the parent node? With the current implementation, it seems like you can either ensure the order of the child attributes by choosing to use a list, or you can use unordered attributes and be allowed to set "@asdf" and "#asdf" properties.

ping @infinisil ? Is this not wanted?

This seems like a fine addition, I'm just very behind on things to review and on holidays :)
After taking a look:

The logic in the two functions should be deduplicated
There should be a docs entry for the new functions in the NixOS manual (there's a sections on formats)


[CRX] Fix error that broke the Chrome extension

PR #9493 moved from appConfig.defaultUrl to AppOptions.get('defaultUrl').
However, it forgot to replace appConfig.defaultUrl in chromecom.js, and as a result the extension is not able to open any PDF file.
That is quite a serious bug, so I would merge this before releasing 2.0.
/cc @Snuffleupagus

Looks good to me. Could you resolve the failure on Travis?

Thank you for fixing this!


feat: adding GOT5.5 and GOT download program

refactor: renamed format for ATLAS to ATLAS-compact
refactor: renamed format for netcdf to ATLAS-netcdf
refactor: renamed format for FES to FES-netcdf and added FES-ascii
refactor: renamed format for GOT to GOT-ascii and added GOT-netcdf
feat: add JSON definition files for GOT5.5D and GOT5.6

I didn't realise there were new versions of GOT available! Have you come across any documentation for them? I can see the files here but not really any extra details...
https://earth.gsfc.nasa.gov/geo/data/ocean-tide-models

Great question. I don't have on hand any additional documentation as I think Richard is writing it up. I know they are higher resolution and with more solved constituents. They have better treatment of some confounding effects (like atmospheric tides), and in the case of GOT5.6 include degree-3 components.

Turns out there's a readme with a bit of extra info in the zip file - thanks @vnewey!
The ocean tide atlas available at this site, called GOT5.6, is
the latest solution in a series beginning with the work described in:

E J O Schrama and R Ray, Journal of Geophysical Research, v.99, p 24799, 1994.
and
R Ray, A global ocean tide model from Topex/Poseidon altimetry: GOT99.2,
   NASA Tech Memo 209478, 58 pages, Sept. 1999.
and
R Ray, Science Advances, 2020. DOI: 10.1126/sciadv.abd4744

GOT5.6 is a supplement to GOT5.5, which provides four additional
constituents, all generated by the third-degree terms of the astronomical
tide potential.  (It is considered a different "model" only because
some users have hard-coded the constituents of GOT5.5.)
You can combine the GOT5.5 and GOT5.6 files and call it GOT5.6.

The data for these four small constituents are defined only in the ±66°
latitude band covered by T/P and Jason altimetry (but tapered to
zero at higher latitudes).  Attempts to derive these tides from
non-T/P-J data have (so far) produced mostly noise.

The nomenclature here uses a prime(') to distinguish 3rd degree from
2nd degree tides. (The 2020 paper uses a leading "3" superscript.)
This isn't needed for M3, since there is no 2nd-deg M3 tide.

R D Ray, Goddard Space Flight Center                       July 2024
<EMAIL_ADDRESS>


Prepared statement caching is data dependent on numeric input parameters (incorrect binary data format in bind parameter x)

Bug description
When I run a raw query with a numeric parameter, the sequence of values for that parameter can cause error 22PO3 - incorrect binary data format.
Related issue: https://github.com/prisma/prisma/issues/16611
How to reproduce
Test code:
await prisma.$queryRaw(
    Prisma.sql`select * from version() where LENGTH("version") > ${1}`,
  );

  await prisma.$queryRaw(
    Prisma.sql`select * from version() where LENGTH("version") > ${1.1}`,
  );

Success cases:

Run query with decimal value (1.1) first, then query with integer value.

Failure cases:

Run query with integer value (1) first, then query with decimal value. Throws code 22PO3 - incorrect binary data format.

Workarounds:

Disabling Prisma's prepared statement cache (?statement_cache_size=0) prevents the issue from occurring.
Manually serializing the input value to a string and then casting to a Postgres decimal type separately prevents the issue from occurring ( ${n.toFixed(2)}::decimal )

Expected behavior
Prisma prepared statement caching should not prevent varying numeric types from being passed in as parameters.
Prisma information
See test code above.
Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v18.18.2

Prisma Version
5.7.1

Hi @lbebels, thank you for this issue. I was indeed able to reproduce it.
Internal note: this only happens when targeting "pure" PostgreSQL instances; this problem doesn't arise on Neon Cloud.

@jkomyno I am able to reproduce a similar issue by switching between arrays of null values and arrays of text values: https://github.com/benweissmann/prisma-22482-repro -- that produces the error Raw query failed. Code: 08P01. Message: ERROR: insufficient data left in message`.
As you'll see in that reproduction, the issue is related to the prepared statement cache: running just one query per client instance does not trigger the bug, and disabling the prepared statement cache works around the bug.

It looks like the issue is that the prepared statement cache uses prepare_typed but does not include those types in the cache key.
Out of curiosity -- why does Prisma prepare every query (necessitating the complexity of this cache layer)? Why not just pass the SQL and arguments directly to query?

@janpio @jkomyno Any updates on this? My team has been using the (undocumented) workaround of setting statement_cache_size=0 but it seems like this has been causing production issues for a lot of folks -- any timeline for a fix or anything we can do to help?

@janpio @jkomyno Any updates here? This seems to be a pretty severe issue; it was causing major production outages for us in unpredictable ways (because it's dependent on the order in which you issue similar-looking queries), and the only available workaround is the undocumented statement_cache_size=0. Are there any updates or a timeline for a fix?

If there is no response to your comment, then there is no update @benweissmann.

We also have exactly this issue in our production code, should I be checking the other issue for a solution?

+1
this is causing a lot of issues in production for us, we're close to migrating away from prisma solely due to this issue

+1

Here the same. This issue forces us to create workarounds in ugly way. Also performance is negatively effected by this.

Thank you for reporting the issue @lbebels!
If you are not using driver adapters for Postgres, can you please try this version and tell us if it fixes the issue? Note that this is a dev version and it is not suitable for production use.
npm i<EMAIL_ADDRESS>npm i<EMAIL_ADDRESS>

@laplab This didn't seem to fix it for me, but we are using vercel postgres - does that make a difference?

It should not @lbebels - this should apply to any PostgreSQL based database.
Can you confirm with prisma -v that you are using this version with both Prisma Client and CLI, and have used prisma generate to generate a new Client based on these? Thanks.

Thanks everyone!
The issue should be fixed and the fix will be shipped as a part of 5.15.0 release next week.
As my co-worker mentioned, you can try out the fix now by using 5.15.0-dev.47 snapshot. We do not recommend using snapshot versions in production, but it's enough to verify the fix.
Feel free to comment if that version does not fix the problem for you.


Cancel scheduled timeout work, if no longer needed

Fixes #2134
This ties the action subscription returned from a call to schedule() to the lifespan of the subscriber, so it handles error/complete. On reschedules it more explicitly cancels, if there's an existing.

I think this fixes it, but to be honest, I can't be sure. It's not immediately clear how to test it. At first glance, it doesn't appear we're testing this possible bug in the other operators which could have similar problems. e.g. debounceTime. So other operators could be hiding the fact that they don't clean up properly, because of guards in their work callback, or the subscriptions that protect against values continuing after error/complete.
I tried peeking into the internals of TestScheduler to see if maybe I could grab a reference to the VirtualAction and check action.pending, but because it's entirely virtual, the action comes and goes only inside a testScheduler.flush().
Perhaps @trxcllnt aka Mr. Scheduler can halp?

@jayphelps perhaps there's a test we can write for this?  I don't see anything here to that regard but should be.

@mattpodwysocki see my original post 😆

@jayphelps * sigh * reading is fundamental...

@jayphelps let's use lift! If the changes in my review pan out, something like this should do the trick:
it('should unsubscribe from the scheduled timeout action when timeout is unsubscribed early', () => {
  const e1 =   hot('--a--b--c---d--e--|');
  const e1subs =   '^         !        ';
  const expected = '--a--b--c--        ';
  const unsub =    '          !        ';

  const result = e1
    .lift(function(source) {
      const timeoutSubscriber = this;
      const { action } = timeoutSubscriber; // get a ref to the action here,
      timeoutSubscriber.add(() => {         // because it'll be null by the
        if (!action.canceled) {             // time we get into this function.
          throw new Error('TimeoutSubscriber scheduled action wasn\'t canceled');
        }
      });
      return source._subscribe(timeoutSubscriber);
    })
    .timeout(50, null, rxTestScheduler);

  expectObservable(result, unsub).toBe(expected);
  expectSubscriptions(e1.subscriptions).toBe(e1subs);
});

Coverage decreased (-0.1%) to 97.586% when pulling d34cb5792577746869cf1a38cebe79c3718432c7 on jayphelps:timeout into e0cf882feab1ec46cd611434e6411bd867abcbf2 on ReactiveX:master.

@jayphelps I'm preparing a PR for your PR, if that's ok :-)

@jayphelps I fixed the lint, rebased, tried and failed to push straight to this PR ref (GH doesn't like that), so I re-PR'd to your timeout branch.

Coverage decreased (-0.008%) to 97.678% when pulling 0de6ef5e43730f3ffeab0365c036af56218893f9 on jayphelps:timeout into f51b8f9391ca6d751517a72fdabb05ad8c1013d8 on ReactiveX:master.

@blesh alternatively, we should be able to define Operator as a hybrid type (so it's both an Object with a call method, and a Function with thisArg: Subscriber<T>), but my TypeScript-foo was not strong enough to defeat the compiler. maybe @david-driscoll @kwonoj could help?

@blesh what are the blockers to merging this? @jayphelps if possible, could you allow adding commits to this PR from other collaborators?

@trxcllnt the edit bit is already enabled:

We discussed this PR today, minor changes needed: https://github.com/ReactiveX/rxjs-core-notes/blob/master/2016-12/december-20.md#review-prsissues

Needs comments on why we're using lift this way, also remove npm script changes.

I won't be able to get to it for at least a couple days, but others with edit bit are welcome to modify.

ping @jayphelps https://github.com/jayphelps/rxjs/pull/3

lol wut

@trxcllnt it is expected, latest change now guards to have type definition import for test cases explicitly if test case has been modified (remaining test will be updated gradually, it's my task)
basically what you need is import type definitions for hot, cold like https://github.com/ReactiveX/rxjs/pull/2202/files#diff-4b0bd2db7bc00156389d58a6ee4d8e1cR6 . just copy-paste it and update PR would be sufficient. (if there's type error, it need to be fixed as well)

@kwonoj thanks for the heads up. @jayphelps I've made the fixes in https://github.com/jayphelps/rxjs/pull/4

Coverage decreased (-0.008%) to 97.681% when pulling 9e16f48fe24ec18ba9779d1f59e7adf95c2a9dab on jayphelps:timeout into 6ce4773e3894b3718dfc61edd6c38510b9a1e77b on ReactiveX:master.

I'm going to lower commit message checker to warning so ignore failure for now please.

LOL... why are there so many commits in this PR now?

@blesh lint/spec typings fixes and merge commits/conflicts le sigh

@trxcllnt sorry for inconvenience but rebase to master once again will resolve commit message checker failure (though you'll see warning still).

Ugh. I'm not sure what to do with this PR. It's older that dirt. It's a solid fix, but there's something crazy going on with the commits. Can we resubmit this one and/or clean it up?

I'm not following all of @trxcllnt's additions. If he's not available to fix, we can abandon this PR and I can try to fix the underlying problem from scratch again.

@jayphelps @blesh they're just merge commits from master to resolve the merge conflicts

Coverage decreased (-0.009%) to 97.679% when pulling c9994b0e4330765b1e271aec219683cb11e45766 on jayphelps:timeout into 023d436b3beead009bbbb24593775b51c9b97623 on ReactiveX:master.


Add support for updating ARM tags on AKS clusters

This PR adds support for updating RM tags on AKS clusters.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/seanmck/azure-cli-extensions.git@aks-update-tags#subdirectory=src/$EXT&egg=$EXT"

Are this PR still active?

@haroldrandom it doesn't seem so. I will dismiss my stale review.

There are some conflicts, could you please solve them first?
I don't know the context.

@seanmck

hi @seanmck  are you still on this PR? if yes, could you pls sync with master branch, and add test? thanks.

@seanmck  thanks for contribution, close the PR for now since no activity. pls feel free to create new PR when ready, thanks.


only lower presets working on P200 latest stable firmware

I'm using the latest stable P200 firmware, and have tried the latest stable & beta builds of companion, and only the lower presets are working, though my application uses 11-19 and "Recall Preset" does not work for these.
I saw that there was another closed Issue related to this, but it said it was resolved.  Perhaps they meant only for the latest BirdDog 5.0 firmware?  However, that is a beta firmware release, so I'd think this module would want to support the current/latest stable firmware too? It seems this module could detect that the P200 firmware isn't 5.0 so fallback on the old way of doing presets?
Companion Version: 2.2.2 and 2.3.0+4510-beta-b1f7c512
P200 firmware: BirdDog P200 A4_A5 4.5.3418-LTS
{"FirmwareVersion":"BirdDog P200 A4_A5 4.5.3418-LTS","Format":"CAM 1","HostName":"birddog2","IPAddress":"<IP_ADDRESS>","NetworkConfigMethod":"static","NetworkMask":"<IP_ADDRESS>","SerialNumber":"801f12f762ef","Status":"active"}

@schwtyl - Unfortunately using the v4 FW, the API only allows presets 1-9 to be saved & recalled. This is fixed in v5
The module was rewritten to use the API, rather than the old way of using VISCA commands.
Due to the future being the API, I'm not sure if we will look to add VISCA control of presets back into the module....will have a think


More than one file was found with OS independent path 'lib/arm64-v8a/libRSSupport.so'

I am getting this build error on version 3.3.0 with kotlin android project and glide version 4.7.1
More than one file was found with OS independent path 'lib/arm64-v8a/libRSSupport.so'.

me too

add below code in build.gradle
android {
......
packagingOptions {
        pickFirst 'lib/armeabi-v7a/libRSSupport.so'
        pickFirst 'lib/arm64-v8a/libRSSupport.so'
        pickFirst 'lib/x86_64/libRSSupport.so'
        pickFirst 'lib/x86/libRSSupport.so'
        pickFirst 'lib/mips/libRSSupport.so'
    }
}

add below code in build.gradle may help you
 packagingOptions {//加上这些代码
        pickFirst 'lib/armeabi-v7a/libRSSupport.so'
        pickFirst 'lib/arm64-v8a/libRSSupport.so'
        pickFirst 'lib/x86_64/libRSSupport.so'
        pickFirst 'lib/x86/libRSSupport.so'
        pickFirst 'lib/arm64-v8a/librsjni.so'
        pickFirst 'lib/x86/librsjni.so'
        pickFirst 'lib/x86_64/librsjni.so'
        pickFirst 'lib/armeabi-v7a/librsjni.so'
        pickFirst 'lib/x86_64/librsjni_androidx.so'
        pickFirst 'lib/armeabi-v7a/librsjni_androidx.so'
        pickFirst 'lib/x86/librsjni_androidx.so'
        pickFirst 'lib/arm64-v8a/librsjni_androidx.so'
    }


Add more logging when recording feedback

Apologies in advance, the commits are chaos as I was figuring things out. This pr should do the following:

Add a property and event on IClientSettings showing if feedback is being recording.
Up logging on LogHub and OutputWindowLogger if IsFeedbackBeingCollected is true
Add a specific in memory logger that keeps up to 5k messages in memory while feedback is being collected
Fix IClientSettings to have a ClientSettings as a property since it no longer allocates a new item.

I know I left a lot of comments, but they're all pretty opinionated and certainly nothing blocking. I definitely like where this is going though!

No this is great. I found myself floundering during a lot of the exploration in how to do this, and then couldn't quite figure out a clean way to make things fit. I appreciate the discussion

Going to close this for now. I think just doing a constant in memory log is the way to go, and can get rid of a lot of complexity in this pr. Will also make it easier to get into for 17.10 so we have those logs in dumps


What the size of the input image should be of CuMo?

the input image can be any size and the data loader will resize it to 336x336 and then send it to CLIP.

Thanks.

Hello， I noticed that in paper you implement the multi-resolution input. Does this implement have this feature? Thanks!

Yes, check the https://github.com/SHI-Labs/CuMo/blob/main/cumo/model/multimodal_encoder/clip_encoder.py for the implementation details.

Thanks!


Potentially resolve issue with os signals

os.Kill can never be caught by a process, unless i'm missing some very specific use case based on a specific OS.
I've updated upstart to also listen for SIGTERM. as far as i'm aware it's the default signal sent by upstart. This will be especially important when HasKillStanza is false
@publicarray, and @jedisct1 can you look to see if these signal changes resolve your issue with OpenBSD

If i'm right about this, #139 should be resolved by this

Coverage remained the same at 9.455% when pulling 12581512a0824a37850071f52c0f3c8ac6060b94 on SteelPhase:signal-ell into 45244176fc183034f15c4f1c2f801da5e25828b7 on kardianos:master.

I'll wait to see if the reporters can test and verify, but otherwise looks good.

Still no joy on OpenBSD :(

@jedisct1 can you provide the version of OpenBSD and go that you are using?

This is with OpenBSD-current and the current version of the Go package, which is 1.10.1.

I'm going to attempt to set up an OpenBSD vm and play around.

I don't believe this code will work at all with OpenBSD as it stands. I'm going to need to investigate further. This PR will not solve these issue, but should solve others.

I'll merge and leave the open bsd issues open.


Add Indonesian translation for container runtime class

This PR adds Indonesian translation for container runtime class, addresses #13929
/language id
/assign @irvifa

@irvifa comments are all addressed and italic format has been changed from single asterisk to underscore


python311Packages.mypy-boto3-ebs: 1.28.16 -> 1.28.36

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 252180 run on x86_64-linux 1

8 packages built:

python310Packages.dsnap
python310Packages.dsnap.dist
python310Packages.mypy-boto3-ebs
python310Packages.mypy-boto3-ebs.dist
python311Packages.dsnap
python311Packages.dsnap.dist
python311Packages.mypy-boto3-ebs
python311Packages.mypy-boto3-ebs.dist

Result of nixpkgs-review pr 252180 run on x86_64-linux 1

8 packages built:

python310Packages.dsnap
python310Packages.dsnap.dist
python310Packages.mypy-boto3-ebs
python310Packages.mypy-boto3-ebs.dist
python311Packages.dsnap
python311Packages.dsnap.dist
python311Packages.mypy-boto3-ebs
python311Packages.mypy-boto3-ebs.dist

Duplicate of https://github.com/NixOS/nixpkgs/pull/252179


fix: fixed the design inconsistency issue in finance cards

closes: #2574
Fixed the design inconsistency in finance cards for small screen devices. Changes can be observed through this video:
https://github.com/asyncapi/website/assets/129517558/6ca5dfd2-1b33-437a-a770-10c4f6ddd31a

Hi @akshatnema @derberg . I have implemented the required changes from scratch again. Please have a look. Waiting for a merge notification eagerly. Thanks!

looks good to me

/rtm

Thanks @anshgoyalevil . Please have a look on these too: #2575  #2563


More decryption modules such as BASE32 needed

Ciphey is in need of more decryption modules. Check out the README to learn how to add a decryption module.
In particular, we're looking to get more BASE encodings such as:

Decode from Base32
Decode from Base58
Decode from Base62
Decode from base85

But if you have any ideas for other decryptions / encodings, they will also be welcomed!
The bottom of the README details exactly how to contribute.
https://github.com/brandonskerritt/Ciphey/blob/master/README.MD
We currently have these decryptions (this might help you come up with more if you'd like!)

Vigenère cipher
Affine cipher
Transposition Cipher
Pig Latin
Morse Code
Ascii
Binary
Base64
Hexadecimal
Caesar Cipher
Reverse (palindrome)
Sha512
MD5
Sha1
Sha384
Sha256

These bases were implemented:
Base32
Base85
Base16


feat(core): export MemoryStore

I am not sure about this. because I don't think anyone will use the MemoryStore directly. That's why I didn't export it

It's fine, I ended up using a TTLCache. The bigger problem in Deno is this: https://github.com/denoland/deno/issues/24292


Apply security patch 0.11.x

Apply security patch to branch 0.11.x

#3094

Integration tests currently need to be ran manually on patch releases. I ran all the @GHA tag tests against a local von network and tails server and all 4 features passed.

Running AATH tests…so far so good.

Very weird. With these changes, all but a set of 7 peer-did tests fail. When I run with 0.11.x branch in ACA-Py a whole bunch more tests fail — coordinate mediation, oob, issue credential and one present proof.  Running again, in case it was a glitch, but local tests are usually pretty reliable…

Interesting. I've only run the integration tests for acapy for this patch. The AATH acapy runset all passed for me for the 0.12.x patch.

Most of the peer did work wasn't merged until 0.12.0, right? We should expect AATH peer did tests to fail, wouldn't we?

I think that aligns with what tests failed. I kind of expected some failing tests with this branch.

Ran the AATH acapy runset with this PR, 0.11.x/3.12 and 0.11.x/3.9.  All were consistent, with the same set of tests failing that would be expected — things added after 0.11.x.  However, as noted above, one of the two 0.11.x/3.12 tests had some additional failures — but worked the next time.
I think we’re good with this, and we can go ahead.
Next up will be a PR to publish the patch release.  Stay tuned!


(mostly) Implementation of NavigationPage

#65
This is only a partial fix to navigation.
This only works with non-modal navigation. i.e. a NavigationPage
This only works with one NavigationPage at a time as it will take over the browser's history.
This has not been tested with a shared page....probably doesn't work.
But, PushAsync, PopAsync, and PopToRootAsync work. Clicking on the forward and back buttons on the browser works. And typing in the url with a hash path also works...
I had to make a pretty big change to the javascript file in order to drill down properties and get access to methods like window.history.pushState. Now the Call method will parse the first parameter (methodName) and I can write this and have it work:
this.NativeView.Document.Window.Call("history.back")

Hey ! That feature sound great
But I have two questions :

It is working only with Ooui.Wasm and not Ooui.ASPNetCore ?
With Oui.Wasm, my SecondPage appear above the MainPage and doesn't replace it.  How can I fix this ?
Tx !

This is great thank you very much!

@praeclarum
So is it available in Nuget Package ?