removed dependencies

Buffer where just used for one thing to base64 encode usr/psw
this removes the hole buffer module
closes #176
thought about using btoa but node don't have it...
didn't see moment being used anywhere either?

Thanks for putting this together!

This will be fixed by: https://github.com/dropbox/dropbox-sdk-js/pull/288


Revert "[SPARK-41369][CONNECT][BUILD] Split connect project into comm…

What changes were proposed in this pull request?
revert https://github.com/apache/spark/pull/38889
Why are the changes needed?
https://github.com/apache/spark/pull/38889 make all tests skipped
Does this PR introduce any user-facing change?
no
How was this patch tested?
existing tests

https://github.com/apache/spark/pull/38925 was merged after https://github.com/apache/spark/pull/38889, let's wait for the CI to see whether https://github.com/apache/spark/pull/38925 is ok

Oh, just saw this. I reverted it for now.

@HyukjinKwon  no problem


Store the default shaders

I did as you suggested: I added a LoadShaderPartial function and changed the LoadShaderProgram function to take already compiled shaders. Which means we only have to compile the default shaders once now !
Fix #381

Great! Thanks for the update @nounoursheureux!
I'll probably rename that function to CompileShader(), it's more descriptive.


Version 3.0.0

Implemented Sub-second KSUID.
A small part of the payload is used for sub-second bits. The number of sub-second bits depends on Instant.now() resolution. In JDK-8, the  usual resolution is millisecond. In JDK-9+, microsecond.
Three sub-second precisions are supported: millisecond, microsecond, and nanosecond. The precision is detected at runtime.
Added:

KsuidCreator.getSubsecondKsuid()
KsuidCreator.getSubsecondKsuid(instant)

Removed:

KsuidCreator.getKsuidMs()
KsuidCreator.getKsuidUs()
KsuidCreator.getKsuidNs()
KsuidCreator.getKsuidMs(instant)
KsuidCreator.getKsuidUs(instant)
KsuidCreator.getKsuidNs(instant)

Updated:

README.md
benchmarks
javadoc
test cases

Test coverage: 96.0%

Released version v3.0.0.


Autoaim issue

When more that one enemy around me autoaim locks on one enemy and I have no chance to aim on another enemy

You can always move the mouse cursor towards the person you want to shoot and it locks on that person. You have to at least move the cursor autoaim is helpful but you yourself have to try to aim the cursor towards the person you want to shoot

If you have auto aim restriction disabled, it will always aim to the closest person to you. Turn it on, and it will aim closest to your cursor position


itest: neutrino anchor output flake fix

Fixes #5015.
Fixes #5492 (though indirectly, that never caused the tests to fail in the first place).
Fixes two of our most elusive neutrino itest flakes, both in context of anchor output channels.
I'm not 100% sure I can explain properly why this seems to only happen with Neutrino, but this is what I got so far:

for anchor outputs, we always try to sweep our anchor of our local commit TX and our anchor in the remote commit TX (since we possibly don't know who force closed)
so if we force close from our end, we always create 1 valid sweep TX (our anchor in the local commitment) and an orphaned one (our anchor in the remote commitment)
normally the first sweep succeeds and the second sweep fails because we don't have a spare UTXO to anchor it down. so we never actually publish the orphaned TX
sometimes (hence the flake), the orphaned sweep (remote commitment anchor) is published first and the UTXO is marked as used (even if it's in an orphaned TX) and then the actual "good" sweep TX can't go through because we don't have a spare UTXO

The easy solution to fix the flakes in the itest is to just add another UTXO. That actually makes all those anchor tests quite stable. But I'm pretty sure this just gets rid of the symptoms of a possible underlying problem.

sometimes (hence the flake), the orphaned sweep (remote commitment anchor) is published first and the UTXO is marked as used (even if it's in an orphaned TX) and then the actual "good" sweep TX can't go through because we don't have a spare UTXO

This is very interesting. Did you get it from observation (the logs?) or from inference? If that's the case then I think we should (not in this PR, just a thought) give each node enough number of UTXO to start with, and add a following test to check that the above case and assert our expectations.

Did you get it from observation (the logs?) or from inference?

I studied the logs for a (way too long) time to find this. It only seems to happen in the case where the sweeper publishes a sweep TX for the remote anchor first. The UTXO is then used/locked up even if the commitment TX confirms and it is now clear which anchor would be the correct one. Apparently Neutrino can't detect that the orphaned TX will never confirm and keeps seeing the UTXO as being locked/used. Just giving the node a second UTXO solves this for the itest at least.

And it needs a rebase, sorry bro...

No problem! I'm very happy your itest split PR got in first, that huge lnd_test.go file was always a bit painful to handle.


feat: added some tags to latest posts

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind translation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
These tags are limited to blogs and allow to look for other related blog posts.
@Issif

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vjjmiras
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [vjjmiras]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Editor doesn't get updated from TreeView SelectItem

I have treevieww from uranium UI on the left of my screen and  I want to display the contents of the selected folder from the treeview on the right side of the screen (this is the requirement, can't change it). So for displaying the contents of each folder on the space on the right, I added an editor element there and binded it to the FS viewmodel. So technically whenever an item is selected it should display something in the editor. I defined a function for updating the editor that I call both from a button click event and in item selection. I also added a display alert to the called function to verify that it's being invoked. Now when I click on the button, the editor is updated and the display alert is also displayed. But when I select an item from the treeview, display alert is invoked so obviously the function is being called but the editor doesn't get updated. I've tried it with other text elements as well and nothing works.

Hi, there is no problem seen in the TreeView

Here some tips that you can check:

Check If your property invokes PropertyChanged event in the setter.

Make sure you bind correct property

<!-- Use string property of SelectedItem instead complex type itself -->
<Editor Text="{Binding SelectedItem.Name}" />

I've checked the binding, it is fine and the property is being invoked as well. Can you share your code for this with me so I can see what am I missing? Or if you want I can share my code with you so that you can check.


Activity doesn't execute

The workflow's execute() function is called, but not its first activity's execute() function.
The workflow class method starts with:
    public function execute($email_address = '')
    {
        dump(__CLASS__ . '::execute()', $email_address);

        yield ActivityStub::make(SendEmailAddressVerificationEmailActivity::class, $email_address);

and prints:
"App\Workflows\Tests\VerifyEmailAddress\VerifyEmailAddressWorkflow::execute()"
<EMAIL_ADDRESS>
But the activity class method doesn't print or log anything:
    public function execute($email_address)
    {
        dump(__CLASS__ . '::execute()', $email_address);

        Log::info('Sending to: ' . $email_address);

In the workflows database table all started workflows have status waiting.
I'm using Laravel 10.

@wq9578 I'm sorry to hear that you're having an issue. I'm wondering, did you make sure to run the queue worker? Check that first and let me know if that wasn't the issue. Thanks!

Laravel Workflow uses Laravel's queued jobs to run workflows and activities in the background. You will need to either run the queue:work Artisan command or use Horizon to run your queue workers. This will process the queued workflows and activities and execute them in the background. Without a running queue worker, workflows and activities will not be executed.

(Source: https://laravel-workflow.com/docs/installation#running-workers)

Of course I had started the queue (and I have tested it again now).
The exact instructions were:

Starting the server: php artisan serve
Starting the queue: php artisan queue:work

I also tried starting the queue first, and starting the queue only (without starting the server).
So what is the next step in debugging?
The library as well as the website are nicely done, as far as I can see, so I would like to use it.
Thanks!

@wq9578 Just wanted to cover the basics and also was wishful thinking on my part! 😂
What do you see in the output of php artisan queue:work? Anything? Also can you try using Log::info in both places? I think dump might not work in all cases.
Can you provide the entire workflow and activity classes? You can use https://gist.github.com/ or paste it here.
Also can you tell me what version of the library you are using? What queue driver? What database driver?
How are you starting the workflow and checking the output? Thanks in advance!

See the files at https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71, and for the versions the log file there.
The queue doesn't report anything, even with maximum verbosity: php artisan queue:work -vvv.
Console:
php artisan test tests/Feature/EmailVerificationWorkflowTest.php
"App\Workflows\Tests\VerifyEmailAddress\VerifyEmailAddressWorkflow::execute(test@example.com)" // app/Workflows/Tests/VerifyEmailAddress/VerifyEmailAddressWorkflow.php:24

   PASS  Tests\Feature\EmailVerificationWorkflowTest
  ✓ it logs the PHP and composer version                                                                                0.11s
  ✓ it logs the composer package versions with ('laravel/framework')                                                                             0.01s
  ✓ it logs the composer package versions with ('doctrine/dbal')                                                                                0.01s
  ✓ it logs the composer package versions with ('pestphp/pest')                                                                                0.01s
  ✓ it logs the composer package versions with ('pestphp/pest-plugin-laravel')
  ✓ it logs the composer package versions with ('laravel-workflow/laravel-workflow')
  ✓ it test the email address verification workflow                                                                                0.03s

  Tests:    7 passed (7 assertions)
  Duration: 0.20s

@wq9578 Thanks for the additional details! It looks like you are executing this via a Pest test? Have you tried also making an artisan command to start the workflow that way? I'm going to try all of this myself but I want to narrow down if it's an issue running via Pest. All the tests I have just use vanilla PHPUnit btw. Also can you confirm which queue driver you are using? Is it redis or database or something else?

I made a PHPUnit test to make sure that it isn't a Pest issue: https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71#file-emailverificationworkflowphpunittest-php
The result is still the same.
See the updated log here for the database engine version: https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71#file-laravel-log

@wq9578 That doesn't make sense because this library is tested with PHPUnit. All the tests run automatically in the GitHub pipeline. If this library didn't work with PHPUnit then the pipeline wouldn't work.
https://github.com/laravel-workflow/laravel-workflow/blob/master/tests/Feature/WorkflowTest.php
Try making a simple artisan command to start your workflow. There's something we're still missing here.

@wq9578 This is what I am using:
https://gist.github.com/rmcdaniel/e343a84954481eb069fb243bc078e956

Artisan command: https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71#file-workflowtest-php
Nothing changed, as expected.
Both the MySQL database and Pest always worked fine and seamlessly with all other features of my current Laravel project.

@wq9578 I tested your workflow locally and it works for me. 😞

Tried it with your console command (with minor modifications), didn't work either: https://gist.github.com/wq9578/5e52bfc9e0e5178aa4eb99aca0ebcd71#file-workflow-php
$ php artisan workflow:run
"App\Workflows\Tests\VerifyEmailAddress\VerifyEmailAddressWorkflow::execute(test@example.com)" // app/Workflows/Tests/VerifyEmailAddress/VerifyEmailAddressWorkflow.php:24
^C

@wq9578 Do you have some time for a video chat so we can screen share? That would be the fastest way to make progress on this point. The major issue right now is that we aren't getting any error message. So we need to figure out when/where/how it's silently dying in the middle of the workflow.

@rmcdaniel Thanks for your kind offer.
For arranging a video chat appointment, is there any way on GitHub you could tell me your email address privately?
I don't want to share contact details here.

Here's my public email address https://github.com/laravel-workflow/laravel-workflow/blob/master/composer.json#L27

I have updated the documentation. I would recommend database or redis queue driver for testing workflows. The sync driver won't work. If you want to hack it yourself @florisbosch has graciously provided some code for that. But you won't be able to use timers if you go that route. I'm going to close this ticket, assuming changing the driver fixes the issue. If not, please feel free to reopen it. Thanks!

After migrating the database and updating the QUEUE_CONNECTION as described at https://laravel.com/docs/10.x/queues#driver-prerequisites it seems to work.
Thanks a lot!


feature: create a subdirectory per mode in debug/

What ❔
Merging this PR requires merging https://github.com/matter-labs/era-compiler-llvm-context/pull/24 first.
Support creating subfolders in debug/.
Why ❔
Compiler tester overrides IR dumps if they were produced by launching a test repeatedly with different modes.
This change should not break behavior expected from era-compiler-llvm-context.
Initially I wanted to just encode modes in the filenames but it turned out to be very intrusive to the code base (for one, dumping .yul files is done by a very different code than dumping everything else). Therefore we are creating a subdirectory per mode.

Note: run CI after merging https://github.com/matter-labs/era-compiler-llvm-context/pull/24 and before merging this PR.

@sayon thanks!
Please note that you have to do cargo update for zksolc and zkvyper as well, so they depend on the correct commit of era-compiler-llvm-context, and then do cargo update here in the tester so it depends on everything up-to-date.

Address the 2nd comment as well please.

@sayon have you checked locally before commiting? There are compile errors.

I see the problem! It worked indeed on my machine, but I was using a patch in Cargo.toml to override the dependency on llvm context.
 Or do cargo update and commit it?
As for CI: Maybe CI does "cargo update" before launching tests? Therefore it has Cargo.lock with a newer dependency, not an obsolete reference to a previous commit.

I see the problem! It worked indeed on my machine, but I was using a patch in Cargo.toml to override the dependency on llvm context.
 Or do cargo update and commit it?
As for CI: Maybe CI does "cargo update" before launching tests? Therefore it has Cargo.lock with a newer dependency, not an obsolete reference to a previous commit.

No, CI shouldn't do it. Please do cargo update and push Cargo.lock!


Add release workflows

Signed-off-by: Sayali Gaikawad<EMAIL_ADDRESS>Description
This change adds the release workflow which includes a release-drafter that drafters a release with all artifacts that needs to be published attached to it. It also contains a jenkins workflow that is responsible for signing and publishing the artifacts to maven central.
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/2692
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I'll add the jenkins workflow and set up webhooks. Please watch https://github.com/opensearch-project/opensearch-build/issues/2692 for updates. I'll give a go ahead on that.
Thanks!


Errors in calculating drawdowns?

Is it possible the max drawdown periods are giving the wrong dates as an output? For example see this:
Here I'm finding the max drawdown for the dot-com and great recession crashes for QQQ.

!pip install quantstats

# need to install arial font with matplotlib
import matplotlib.font_manager as fm
import matplotlib.pyplot as plt
# arial_path = '/content/drive/MyDrive/arial.ttf'
# fm.fontManager.addfont(arial_path)  # Register the Arial font with Matplotlib
# plt.rcParams['font.family'] = 'Arial'

import yfinance as yf
df = yf.download('QQQ', start='2000-01-01', end='2020-01-01')

import quantstats as qs
qs.extend_pandas()
returns = df.Close.pct_change()
qs.reports.full(returns, "QQQ")

OUTPUT:
_[Worst 5 Drawdowns]
Start Valley End Days Max Drawdown 99% Max Drawdown
1 2000-03-28 2002-10-09 2016-09-02 6003 -82.96 -80.06
2 2018-08-30 2018-12-24 2019-04-16 230 -23.16 -19.77
3 2019-05-06 2019-06-03 2019-07-02 58 -10.98 -8.98
4 2018-03-13 2018-04-02 2018-06-01 81 -10.67 -10.02
5 2000-01-24 2000-01-28 2000-02-02 10 -10.65 -7.27_

# start of drawdown period
start_draw_down = df[df.index == '2000-03-28']

# end of drawdown period
end_draw_down = df[df.index == '2016-09-02']

# double checking a date before end of drawdown period where close has already broken out of drawdown period
earlier_date_in_drawdown_period = df[df.index == '2016-08-30']

print(start_draw_down.Close)
print(end_draw_down.Close)
print(earlier_date_in_drawdown_period.Close)

OUTPUT:
Date
2000-03-28 114.75
Name: Close, dtype: float64
Date
2016-09-02 117.120003
Name: Close, dtype: float64
Date
2016-08-30 116.559998
Name: Close, dtype: float64
Note, the 2016-08-30 has already surpassed the close from the previous high water mark. Therefore the drawdown end date that quant stats is calculating appears erroneous.Thoughts? Maybe I'm missing something.

Check out https://github.com/Lumiwealth/quantstats_lumi, which is being updated regularly. We are a fork of this library that is being maintained by Lumiwealth


FeatureFormView - Refresh attachment display on add

Related: Apollo 408

Provides a callback to AttachmentImportMenu to use when a new attachment has been added.
AttachmentsFeatureElementView uses the callback to update its list of attachment models.

Know issues:

Attachment naming isn't correct yet
Thumbnails don't seem to be rendering with correct display scale - appear blurry

Thumbnails don't seem to be rendering with correct display scale - appear blurry

This is because for the .preview list type, the thumbnail size is 120 x 120, but the default thumbnail size argument for AttachmentModel.load is 40 x 40. I'll fix this in a separate PR.


GEODE-9209: Complete test in DistributionConfigJUnitTest

testCheckerChecksValidAttribute in DistributionConfigJUnitTest has a "TODO" comment about a missing check in the test.
I have also changed JUnit asserts by AssertJ asserts, which are more descriptives in case of error.

PR checks in this PR are now a week old (and don't include DistributedTestOpenJDK8).  If possible @alb3rtobr could you please push an empty commit?

Kind reminder, review by code owners still pending

Thanks for the review @kirklund , I have implemented the requested changes


Add 3xpl.com to blockchain explorer list

This PR adds 3xpl.com to the blockchain explorer list.
close #1

ready for review. thank you!

Just checked, It seem great. Thank you 👍

Thank you for welcoming this PR. Have a nice day!


Update spo folder move endpoint

While working on #4968 I noticed that it's not possible to use special characters # and % in the URL of the source or destination path of the command spo folder move. Just like we did with spo file copy we should look for another API endpoint that does support it. This will likely cause breaking changes.

Amazing job with this research @milanholemans. It's a bit annoying that we have to drop an option but let's just make sure to note in the docs why we did this change. I'm keener on a faster command and make it so certain chars are allowed.
For the option bypassSharedLock, I don't have any experience with that one so not quite sure how it works.

@Jwaegebaert I think the option that we have to drop is not that useful. It's the default behaviour with the new API.
We also moved to the same endpoint for spo file copy. Over there we had to drop the same option.


feat: don't upgrade configs with a filepath in $schema

Instead of using a NoVersion Handler analize function should throw an error.

@ivan-tymoshenko Do we still need this? What do we need to land it?


Error when insert timestamps containing T delimiter

I'm trying to import a table that contains a series of timestamps that contain a 'T' delimiter (e.g. 2009-11-11T15:21:19) as per the ISO 8601 standard but I'm getting an error from duckdb. As a short example (using the python interface):
con = duckdb.connect(database=':memory:', read_only=False)
con.execute(f"CREATE TABLE tmp(testdate TIMESTAMP);")
con.execute(f"INSERT INTO tmp VALUES ('2009-11-11 15:21:19'), ('2009-11-11T15:21:19');")

results in the following error
RuntimeError: Conversion: time field value out of range: "T15:21:19", expected format is ([YYY-MM-DD ]HH:MM:SS[.MS])

It seemed odd to me that only the second part of the data format was returned as an error. I did some digging and FromString(string str) in 'src/common/types/timestamp.cpp' seems to indicate that the 'T' should be accepted, at least based on the comments and my quick read of the code.
// string format is YYYY-MM-DDThh:mm:ssZ
// T may be a space

Am I doing something incorrect in my insertion in the above example or is there some sort of quotes/escaping I can use to make this work?

Thanks for the bug report! This seems to be an issue in the timestamp parsing, the comment seems to not indicate exactly what is actually going on in the code. The code parses the DATE and TIME separately. The space works because the TIME parsing skips any leading or trailing spaces, but the "T" is not accepted by the parser here. I will fix it next week.

Should be fixed in the "strftime" branch now, I will close this issue when I merge it.


feat: #1343 - "world" queries and faster cached result display

Deleted file:

group_query_filter_view.dart: old code never used and never changed

Impacted files:

app_en.arb: added 2 labels for "world results"
app_fr.arb: added 2 labels for "world results"
category_product_query.dart: implemented world query
keywords_product_query.dart: implemented world query
paged_product_query.dart: introduced word query parameter and methods
paged_search_product_query.dart: implemented world query
paged_to_be_completed_product_query.dart: implemented world query
product_list_supplier.dart: refactored
product_model.dart: loosely related safer "notifyListeners" method
product_query.dart: now storing here the country, which makes "world" queries possible
product_query_model.dart: removed all the "category filter" code; better management of the "what if the refresh download fails?" case
product_query_page.dart: added "world" queries; removed the "category filter" code; now displays a MaterialBanner (more flexibility than a SnackBar)
smooth_theme.dart: added a banner theme for MaterialBanner

What

As in the web version, there's the possibility to run search queries not only on the current country, but in the world.
This is specifically useful for country with few products, or queries with few results in general.
As an optimization, the category filter has been removed. As a result, the cached results are displayed instantly.

Screenshot

country page
world page

Fixes bug(s)

Closes: #2715
Closes: #2339
Closes: #1343

Thank you @VaiTon for your review!


Link to online documentation is broken

I know. The docs are pushed as part of release, and this hasn't been released yet. :smirk_cat:
Thanks for reporting!


Update HikariCP to 4.0.0

Updates com.zaxxer:HikariCP from 3.4.5 to 4.0.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (3.4.5).
You might want to review and update them manually.
CHANGELOG.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.zaxxer", artifactId = "HikariCP" } ]

labels: library-update, semver-major, old-version-remains

Superseded by #2069.

Superseded by #2069.


FEAT: Add configuration option to allow parsing of html only blocks for Jupyter notebooks

This PR adds the option to include html only blocks in jupyter notebooks.

[ ] check test

Closing as this is replaced by #92


[develop < T0070-GA] Add more clauses for base classes

Description
Added load_csv and return to base classes list.
Discuss:
REMOVE, DELETE and SET  are also supported per cypher grammar to be at the start of a query, but I have not included them as in agreement with Ivan they do not make much sense to be used like that, without some variable defined with MATCH in front of them.
Note:
FOREACH will also be in the base classes, but I decided to add it to the FOREACH clause PR, so this PR doesn't have to wait for that one.
Pull request type

[x] Bugfix
[x] Feature

Related issues
Closes #138
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] 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

######################################
Reviewer checklist (the reviewer checks this part)

[ ] Core feature implementation
[ ] Tests
[ ] Code documentation
[ ] Documentation on memgraph/docs

######################################

And discussion-wise, I think we should follow Cypher grammar as much as we can, especially because of the next version of the query builder. I vote for implementing all clauses that can be first in the query to be base classes.

I already reviewed this and you made the necessary changes, so I think that's it! Besides failing tests, this is fine 😄

I see status:discuss. Is there anything else that we need to discuss here? @brunos252


MudTextField attribute Pattern dont works

Bug type
Component
Component name
MudTextField
What happened?
<MudTextField T="string" Required="true"
@bind-Value="bannerAd.MaxDeposit" Label="Maximum Deposit"
RequiredError="is required!" Pattern="[0-9]"/>
can write all letters
Expected behavior
cant input all letters
Reproduction link
https://try.mudblazor.com/snippet/QOQmOFwbpOvnciBs
Reproduction steps

do some letters in field

Relevant log output
No response
Version (bug)
latest
Version (working)
No response
What browsers are you seeing the problem on?
Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Try this: https://try.mudblazor.com/snippet/QaQcklQFqXeYmFFz
It is not a bug. As far as I know only Safari will prevent input of characters not matching 0-9 and probably only if input type is numbers. I don't know exactly. But if you try the snippet I linked you will see that Pattern does not prevent input in html. So this is not a bug in mudblazor. If you can prove otherwise you can reopen. Look at our PR #3480 where we are working on a solution for this. Also look at MudNumericInput where we prevent letters.

I just want to note that in the future with masking merged you should be able to do this instead <MudTextField Mask="@(new RegexMask("[0-9]"))" />

As @henon said, and a little addition, https://www.w3schools.com/tags/att_input_pattern.asp, pattern is used more for validation and within form component. Masking will solve all this problems.


Update association_test.R

This change has already been incorporated in a merge that had some bigger changes, but thanks for flagging it


Free Threaded CPython 3.14 Plan

graph LR

    subgraph Legend
        ORANGE(Orange - In-progress)
        GREEN(Green - Done)
    end

    TAG(Stack references)
    TAG --> DEBUG(Debug information)
    TAG --> HEAPREF(Heap references)
    HEAPREF --> UNBOX
    TAG --> UNBOX(Unboxed integers
 With Faster CPython @ Microsoft)
    TAG --> DRCGC(Deferred refcounting GC changes)
    DRCGC --> DRC(Finish deferred refcounting)
    DRC --> LEAK(Remove memory leaking immortalization)
    COW(Copy-on-Write Bytecode)
    COW --> INCA(Make method inline caches safe)
    COW --> SPEC(Incremental re-enabling of specializations
 With Matt Page)
    COW --> COL(Make dict, tuple, list specializations safe
 With Matt Page)
    DRC --> INCA
    INCA --> ATTR(Full attribute specialization
 With Matt Page)

    classDef green fill:#9f6,stroke:#333,stroke-width:2px;
    classDef orange fill:#f96,stroke:#333,stroke-width:4px;

    class ORANGE,DEBUG,DRC orange
    class GREEN,TAG,DRCGC,LEAK,COW green

Order of priority:

Deferred RC
Specialization
Unboxing

Closing this, it's been taken over by Matt Page!