using bert with unused/discarded data

Hi, I have a multiclass data of song lyrics(lets say 20 classes with total of 36000 text pieces of avg length 250 words ). The dataset contains some of the overlapping classes while some are not appropriate for my work. So i decided to merge or get somehow reasonable final set of lets say 8 classes made using lets say 14 classes. But data corresponds to 20 - 14 = 6 classes were discarded as it was not suitable for my work. So by BERT pre-trained models i can fine-tune on data consists of 8 classes (14 but some were condensed ). But how would i make use of remaining data of 6 classes. I read some where that it is good to fine-tune with model trained on data which is close to your domain but since BERT trained on wikipedia and some other which is very different from song lyrics. So does using pre-trained BERT model and then fine-tuning on my data gives me benefit or should I train the BERT from scratch on discarded data and then fine-tune it on my selected data.
Hope someone reply.
TIA

Hello @Priyansh2 according to BERT, you might want to do fine tuning for your downstream tasks.
However, how good will it be or how much you can benefit from BERT is hard to tell. It would be a good idea if you can do experiments and share what you find.

btw @imgarylai  can you tell me how to leverage BERT on transliterated data (for example, hindi text trasliterated into english language). In that case I can't use english pre-trained model of BERT and do fine tune over my data as my data contain lots of noise due to improper word structure, ambiguities etc. Should i train BERT from scratch on it or pre-train on some other data close to my domain and then fine-tune over my data to generate rich embeddings.

@Priyansh2 it depends on your task. Actually, Bert has multilingual models, and Hindi is included.
Please check this: https://github.com/google-research/bert/blob/master/multilingual.md
You should be able to build your task top on it.


fix: adapt to rcases fix

a proof was relying on buggy behavior that is fixed in https://github.com/leanprover/lean4/pull/4422

This is a PR to a lean-pr-testing-NNNN branch. I'm merging now.


Remove the need for HostRef<Module>

This commit continues previous work and also #708 by removing the need
to use HostRef<Module> in the API of the wasmtime crate. The API
changes performed here are:

The Module type is now itself internally reference counted.
The Module::store function now returns the Store that was used to
create a Module
Documentation for Module and its methods have been expanded.

Er I botched the merge here by accident and included https://github.com/bytecodealliance/wasmtime/pull/780 by accident. I pushed a revert and will re-push this PR as originally reviewed


supporting constexpr values/types in variant

Added support for handling reads of constexpr struct values in variants.
Introduced type handling of const types for glaze value, and split the const types from the non const types during the parse of variant types.

very unofficial compilation time benchmarking
before
jonb@jonb-desktop ~/P/glaze (support-direct-constexpr-read)> time cmake --build build --target json_test
[0/2] Re-checking globbed directories...
[2/2] Linking CXX executable tests/json_test/json_test

________________________________________________________
Executed in   43.86 secs    fish           external
   usr time   40.95 secs  246.00 micros   40.95 secs
   sys time    2.76 secs  351.00 micros    2.76 secs

after
jonb@jonb-desktop ~/P/glaze (support-direct-constexpr-read) [1]> time cmake --build build --target json_test
[0/2] Re-checking globbed directories...
[2/2] Linking CXX executable tests/json_test/json_test

________________________________________________________
Executed in   42.71 secs    fish           external
   usr time   40.01 secs  233.00 micros   40.01 secs
   sys time    2.58 secs  345.00 micros    2.58 secs

Does not show any major difference but it's a bit better

Thanks for the benchmark and making those changes. I guess there's not a significant difference in this context, but I've seen in make a big difference elsewhere.

I think this can be merged, if you think it's ready.


F# Type Provider for .proto Files

Create an F# Type Provider which reads .proto Files and produces classes for serializing and deserializing to protobuf wireformat.
This is being iterated on in branch type-provider.
Non-goals

Generation of service wrapper classes.
Importing from binary (compiled .proto) FileDescriptorSet.

@jhugard Feel free to tag a 0.4.0 if @takemyoxygen is ready to release the type provider. I'm on vacation for a week, but there is strong interest from my employer in looking at grpc and it could get me back more involved in this.

@jhugard @ctaggart I think it's ready for the initial release. I'll also have a closer look at grpc to see if type provider can be of any help there.

Publishing 0.4.0 today. Working on it right now.


progress

Hurray!! this is the 1000 commit to this repository. Thank you @Nejilee For being a part of it.


Revert the Discord taskbar icon

I was wondering if we could change the discord icon in the taskbar from this:

To this (not my image):

We would not be able to do this with CSS but a plugin could maybe do it? This plugin is able to change the icon, but I think it just tells discord "there are no notifications, show the no notification icon".
I guess the only thing I can do now is change the .ico in AppData\Local\Discord to the original, but I do not have the original. Does anyone, has it?

Found the old logo in a subfolder
app.zip

Not interested in making a plugin myself but others can, not related to / possible by theme so closing issue.

Found the old logo in a subfolder
app.zip

Thank you for this!


remove unmaintained projects [WIP]. Issue#123

hi @lk-geimfari , I have created a simple python script to automate the #123.
I have pushed the changes in javascript.md, for you to review. Will push others after getting a green flag.

@makkoncept Hi! I really like this script!  Do you interested?

@makkoncept If you don't want to work on it, can i use your script?

@lk-geimfari I should point out that while the script reduces human labour significantly, it is not full proof.
for example, it only checks the master branch for the last commit date. If you want to check for all the branches, you may run out of the request limit, as some projects have many branches present. Therefore a small minority of projects are left out, which may be doing development in a different branch say dev and have not pushed code to the master branch for over 9 months.

@lk-geimfari  i am naive to Travis Cl, so you can use the script. It would be great if it can help make this project better.
So would I continue pushing to this PR?

@makkoncept Sure! Let me know when you finish with this PR.

@lk-geimfari  I have pushed the changes, you can review them.
Also the RUBY.md file of the repository had the same content over and over. maybe someone committed it by mistake. It was also resolved in the PR

@lk-geimfari  a gentle ping

@makkoncept I missed your message in notifications. I'll merge this PR.
Do you interested to be of our maintainer?

Hi @lk-geimfari , I am very excited by your offer. I have dropped you a mail regarding this

@makkoncept Great! Thank you! Check your email too, please.


Figure out how to combine efforts with xpartition

@spencerkclark and @nbren12's xpartition looks like it solves some very similar problems.
It would be great to figure out how to work together, e.g., to share helper functions for working with dataset "blocks" without using dask: https://github.com/spencerkclark/xpartition/issues/13

I agree that could be a good collaboration point. How do you see this going? I could see xarray-beam depending on xpartition, the shared functionality being up-streamed to xarray, or combining xpartition and xarray-beam into one package. One strength of xpartition is that it can easily be used with anything that supports iterating over a sequence (e.g. beam, slurm array jobs, k8s indexed jobs, etc).
I’d be interested to here @spencerc’s thoughts.
From: Stephan Hoyer @.>
Reply-To: google/xarray-beam @.>
Date: Wednesday, May 26, 2021 at 10:41 PM
To: google/xarray-beam @.>
Cc: Noah Brenowitz @.>, Mention @.***>
Subject: [google/xarray-beam] Figure out how to combine efforts with xpartition (#15)
@spencerkclarkhttps://urldefense.com/v3/__https:/github.com/spencerkclark__;!!CjdShnub!nCf_w7cKLSvQuWFJK61KrY-DqlbNMYBFlmHDF0pwTRwqvOalItMKTcuI_d6n$ and @nbren12https://urldefense.com/v3/__https:/github.com/nbren12__;!!CjdShnub!nCf_w7cKLSvQuWFJK61KrY-DqlbNMYBFlmHDF0pwTRwqvOalItMKTcD30yqy$'s xpartitionhttps://urldefense.com/v3/__https:/github.com/spencerkclark/xpartition/__;!!CjdShnub!nCf_w7cKLSvQuWFJK61KrY-DqlbNMYBFlmHDF0pwTRwqvOalItMKTbajT9eE$ looks like it solves some very similar problems.
It would be great to figure out how to work together, e.g., to share helper functions for working with dataset "blocks" without using dask: spencerkclark/xpartition#13https://urldefense.com/v3/__https:/github.com/spencerkclark/xpartition/issues/13__;!!CjdShnub!nCf_w7cKLSvQuWFJK61KrY-DqlbNMYBFlmHDF0pwTRwqvOalItMKTc5yS18e$
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/google/xarray-beam/issues/15__;!!CjdShnub!nCf_w7cKLSvQuWFJK61KrY-DqlbNMYBFlmHDF0pwTRwqvOalItMKTUCMKayF$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AAKSREXFI6LJFFQR2EE5KSLTPXLQZANCNFSM45TPFWVA__;!!CjdShnub!nCf_w7cKLSvQuWFJK61KrY-DqlbNMYBFlmHDF0pwTRwqvOalItMKTWELSeKA$.

I’d be interested to here @SpencerC’s thoughts.

I'd personally like to see a more modularized approach where xpartition and xarray-beam remain independent and shared functionality is up-streamed. I see distinct use cases for each (although I'm partial to beam workflows myself).

I'm not opposed to either pushing components upstream or even adding xpartition as an xarray-beam dependency, but it's easier to develop in a single repository until we know what the right reusable abstractions are :)
For now I've tried to keep the abstractions pretty light-weight, but even one of the few abstractions we have already (ChunkKey) needs an overhaul: https://github.com/google/xarray-beam/issues/9. So maybe this is worth coming back to in a few months.
The logic around partitioning xarray Datasets into smaller chunks does feel very generic, so in the long term I do like the idea of trying to split it out, assuming that there are actual concrete non-Beam use-cases. Xarray-Beam could just be a thin layer with beam.PTransform objects wrapping upstream helper functions (e.g., from xpartition).

it's easier to develop in a single repository until we know what the right reusable abstractions are :)

Makes sense. I'd suggest working out of the xpartition repo since it has a more permissive license and a code coverage step in the CI, and add it as submodule here; unless you've got a google3/copybara workflow this would overcomplicate and slow you down along other project paths?

I do like the idea of trying to split it out, assuming that there are actual concrete non-Beam use-cases

As amazing as beam is, I've encountered at least one instance in geodata processing where the right call was to break out of beam and roll our own distributed workflow system for one step. If you can get it upstreamed, there are also definitely benefits to maintaining functionality in a heavily used, actively managed project with lots of contributors (assuming it's well administrated).

Makes sense. I'd suggest working out of the xpartition repo since it has a more permissive license and a code coverage step in the CI, and add it as submodule here; unless you've got a google3/copybara workflow this would overcomplicate and slow you down along other project paths?

Hah, @SpencerC are you are (ex-)Googler or are we just notorious? :)
I do have a convenient sync setup for xarray-beam/google3 -- and we have a handful of internal uses that serve as integration tests -- but that's not really a good reason not to do open development, if others want to get involved! It is easy enough for me to mirror other external projects.
It does seem more plausible that xpartition could/should be the shared foundation rather than xarray-beam, which will require a Beam dependency. I would rather not push this all the way to xarray (yet), until we really figure out what we're doing.
(IMO the differences between MIT/Apache licenses and a code-coverage step in CI are not really material factors)

As amazing as beam is, I've encountered at least one instance in geodata processing where the right call was to break out of beam and roll our own distributed workflow system for one step

I agree, there are for sure cases where Beam does not make sense. One obvious one is saving outputs from a numerical model. ML inference on specialized hardware might be another.
That said -- what is the specific shared functionality? Some possibilities:

a shared way to build/represent a "dataset schema with chunks" that doesn't require using dask
utilities for reading/writing/splitting/combining partitioned "chunks" of larger datasets
shared data structures for keeping track of said chunks (e.g., xarray_beam.ChunkKey) and perhaps chunking schemes

If you can get it upstreamed, there are also definitely benefits to maintaining functionality in a heavily used, actively managed project with lots of contributors (assuming it's well administrated).

sure, but who do you think is going to be on hook for maintaining said upstream project? ;)

I think we probably have enough experience that we could make a decent design, so I wouldn't be too worried about needing to track xpartition too closely as a dependency. In this case, the abstraction is basically set theory (e.g. union, intersection, partitions of sets, and ways to map between partitions). I always find designs work pretty well when the code abstractions line up with math abstractions.

I'm also not convinced this simple functionality would be more maintainable in xarray, although it could replace the map_blocks function, which I assume is not particularly easy to maintain...


Added timer API

This implements the new timer API so that the following is possible:
from kybra import Duration, ic, TimerId, update

@update
def set_timers(delay: Duration) -> list[TimerId]:
    global_function_timer_id = ic.set_timer(delay, global_function)

    lambda_timer_id = ic.set_timer(
        delay,
        lambda: ic.print("inline lambda called"),
    )

    def inner_function():
        ic.print(f"inner function called")

    inner_function_timer_id = ic.set_timer(delay, inner_function)

    return [global_function_timer_id, lambda_timer_id, inner_function_timer_id]

def global_function():
    ic.print("global function called")

@update
def clear_timer(timer_id: TimerId):
    ic.clear_timer(timer_id)
    ic.print(f"timer {timer_id} cancelled")

Note
Callbacks are not required to be exported externally as canister methods.

Also in the README if you could link to the internetcomputer.org timers documentation (or wherever the best documentation is, maybe the interface spec) just like in the Azle documentation (from my review of the pull request).


fix: timestamp comparison in from_json function

Summary
Fixes issue with updated date with loading items from_json by casting as int or setting it as None
Changes these areas

[x] Bugfixes
[ ] Feature behavior
[ ] Command line interface
[ ] Configuration options
[ ] Internal architecture
[ ] Archived data layout on disk

lol definitely a hack but I'll accept it


performance of must

(quick-bench
 (let [m {:a "some-val"}]
   (if (contains? m :a)
     (assoc m :a "$")
     m))
 )

(quick-bench
 (let [m {:a "some-val"}]
   (setval [(must :a)]
           "$"
           m))
 )

;; clojure
Evaluation count : 19747476 in 6 samples of 3291246 calls.
             Execution time mean : 28.269609 ns
    Execution time std-deviation : 0.386183 ns
   Execution time lower quantile : 27.600519 ns ( 2.5%)
   Execution time upper quantile : 28.637442 ns (97.5%)
                   Overhead used : 1.743376 ns

;; specter
Evaluation count : 4257258 in 6 samples of 709543 calls.
             Execution time mean : 134.752354 ns
    Execution time std-deviation : 11.815950 ns
   Execution time lower quantile : 118.779726 ns ( 2.5%)
   Execution time upper quantile : 147.331239 ns (97.5%)
                   Overhead used : 1.743376 ns

As benchmark above show, Specter is much slower than pure Clojure.
For me, Specter is faster than pure Clojure in most situation, but I wonder what's Specter not good at?

The Clojure code you wrote is identical to what the must navigator does. Executing a path via Specter adds some overhead, namely a couple more layers of function calls to get to the transformation logic. It's these situations of a single simple navigator like must or keypath that Specter will benchmark as slower. As soon as you compose multiple navigators together, or use a more involved navigator like ALL or MAP-VALS, Specter will crush the performance of reasonable vanilla Clojure.


Invalid tests skipped with h5py 2.10

Comes down to comparing strings not ints ...
def _h5_py_version_older_than(version):
    v_majeur, v_mineur, v_micro = h5py.version.version.split('.')[:3]
    r_majeur, r_mineur, r_micro = version.split('.')
    return v_majeur >= r_majeur and v_mineur >= r_mineur

This test is still not correct as 3.1 !> 2.9 !

h5py also provides versions as tuple
In [4]: import h5py.version

In [5]: h5py.version.api_version_tuple
Out[5]: (1, 8)

In [6]: h5py.version.hdf5_version_tuple
Out[6]: (1, 10, 4)

In [7]: h5py.version.version_tuple
Out[7]: _H5PY_VERSION_CLS(major=2, minor=10, bugfix=0, pre=None, post=None, dev=None)

In [8]: type(h5py.version.version_tuple)
Out[8]: h5py.version._H5PY_VERSION_CLS

Could it make your life easier?

Handled by #3325


Switch lazy_static over to mutable statics instead of UnsafeCell on nightly

https://github.com/rust-lang/rfcs/pull/1440 got merged, so we can now get rid of the UnsafeCell in favor of directly having a drop type in a mutable static.
However, since the current UnsafeCell impl got also legitimized by the RFC, the current plan is to not merge this PR until either the drop_types_in_const feature gets stabilized, or is at least old enough to not require the most current version of the compiler.

Alright, I'm giving this another spin. If anyone has any comments to this PR feel free to post them. :)

Alright, thanks!


Warnings for centertab: centertab:custcentertab40 Failed: That record does not exist.

Your environment
OS : iOS Catalina 10.15.4
Node.js version : 14.14.4
suitecloud-cli version : 1.0.2
Terminal/CMD tool : iTerm2
Describe the bug
When importing objects in ACCOUNTCUSTOMIZATION project I receive a lot of warnings for centertab:custcentertab40 Failed: That record does not exist.
To Reproduce

Run suitecloud project:create -i (use ACCOUNTCUSTOMIZATION type)
Run suitecloud account:setup
run suitecloud object:import with ALL types

@omrilit This seems like a problem with server side, but we will look in to this to know the exact problem.

This issue is not with the tool itself, The issues with server side issues/validations etc have to be reported to Netsuite support.
This is not a problem with the CLI itself. Its the response coming from Netsuite SDF.
Please open a ticket with NS Support.


Multiple containers with same selector

With these changes the containment option accepts a CSS style selector, and starts looking for the container from the parent of the element all the way up to the body. This allows us to have two lists, each one of them inside a container with class ".whatever" and we won't have any problems with it, each one will find the correct one. In the version in the master branch the directive makes a querySelectorAll and choose the first element that matches the selector, what is not the best behavior IMHO.
I added a little helper function for traversing the DOM upwards and also a 'kind-of' polyfill for Element.matches so the browser compatibility is the same as before.
I hope you like it and think it is useful, we can talk about it if you want!
Thanks a lot!

@JPorry thanks for the PR and I appreciate, I would prefer to add this helper method in the sortable-helper.js, But also would like to know more in detail, how this patch is necessary and how better it is when compared to the older code. may be a real time example would help in understand the problem it solves.

Hello there!
yeah, i think you are absolutely right and that function makes much more sense in sortable-helper.js
As per the need of this patch, let me share two codepens to illustrate the issue in a much clearer way:
Current Master Version:
http://codepen.io/JPorry/pen/MwvLgO
Version with my patch applied:
http://codepen.io/JPorry/pen/WvELzr
As you can see, there are two sortable lists and both have a div wrapping them with the same class (.dragContainer) In the first example, due to the fact that the plugin is looking for the containment selector provided using document.querySelectorAll and getting the first match, the first list is working fine, but the second one is also finding the same element as a container, and that doesn't make any sense.
In the second version, I am traversing the DOM from the element and upwards until I find an element that matches the selector, returning the body if there is none. So, both lists work as expected.
I know you can probable fix this adding ids to the containers, but you will also have to create more configuration objects in the controller and it can get quite verbose IMHO.
So, that is it, let me know if you want me to move the helper function and create a new PR or if you just merge this one and move it afterwards, whatever suits you best!
Thanks a lot man!

@JPorry I had merged and moved the function to the helper., thanks for the PR.


Provide implementations for Mutex

Hi, is it possible to provide implementations for std::sync::Mutex and std::sync::RwLock?

I don't think we can provide a structure that gives the same functionality in an archive (since it must be cross-platform), but if you just want a passthrough then that would be a sensible thing to do. A passthrough would essentially just serialize the contained value inline and only provide read access.

Seems good for me, I will deserialize anyway before using it. I found it useful to be able to use the derive macros in types with Mutex or RwLock directly.

Linking #122. Once that issue is closed, I'll add a wrapper like LockMutex so you can do:
#[derive(Archive)]
pub struct Example {
    #[with(LockMutex)]
    foo: Mutex<i32>,
}

and hopefully it will just work.

Fixed by bd5ad7fa241c5a1f16e61d275b40ab9c3289933d. This will ship in 0.7.0, but you can use it now by using the 0.7 branch as a git dependency. The syntax for this is:
use rkyv::with::Lock;

#[derive(Archive)]
pub struct Example {
    #[with(Lock)]
    foo: Mutex<i32>,
}

The field will be archived as an Immutable which makes it unable to be mutated.


images flipped 180 degrees

I just started using the ghost:alpine2 docker image and it works fine except when I add animage to a post it is rotated 180 degrees in the preview from when you actually publish it. So I have to add my images upside down in order for them to be right side up in the production post.

I experienced something similar: adding images to a gallery showed them rotated in preview mode, but after publishing the post, they appeared properly.

@jedidja would you mind providing a sample of the image that was flipped?

Sorry for the delay @gargol  ... what's weird is that when I first drag it into the editor, it's rotated, but after saving the post and editing afterwards, it appears the correct way.

Also - Github is displaying it rotated, but the preview in Finder shows it as normal and you can see that the resolution means it should be vertical (3024x4032)

@jedidja thanks for the image. Have been able to replicate it on the local environment as well. Also confirming the image itself is displayed correctly when it's published with a post. Additionally, it is displayed correctly when you re-enter the post editor/refresh the editor page. So, it's only the initial image preview after uploading that is broken.

The image shown as a preview whilst uploading and once initially uploaded is how the browser itself handles the raw image file. There's not much we can do about that other than not showing image previews whilst uploading but that makes the experience worse for the vast majority of images which don't have odd exif rotation data.

@kevinansfield think the main issue is the confusion that is left after the image is uploaded and stays in the flipped state in the editor. Think reloading showed image with uploaded one would solve this?

@gargol we can but it produces a lot of UI jank with images disappearing/re-appearing, this was especially noticeable with the gallery card. It would need deeper investigation to resolve it fully I think and so far we've had very few complaints (the rotation based on exif can be browser dependent, @jedidja I'd be interested to hear which browser you are using).
This issue also appears to have been split now? The wrong rotation during upload problem is not the same as the symptoms of the original issue.

@kevinansfield understood.
For future reference, was able to reproduce this incorrectly flipped behavior after initial upload on Chrome 74 running Ubuntu 18.04.

This issue also appears to have been split now?

It's unclear what if the original issue was something else :thinking: @chovy would be great if you could provide more information about your scenario with some examples

@gargol we can but it produces a lot of UI jank with images disappearing/re-appearing, this was especially noticeable with the gallery card. It would need deeper investigation to resolve it fully I think and so far we've had very few complaints (the rotation based on exif can be browser dependent, @jedidja I'd be interested to hear which browser you are using).
This issue also appears to have been split now? The wrong rotation during upload problem is not the same as the symptoms of the original issue.

@kevinansfield Chrome on macOS (whatever was the released version a couple weeks ago). That's unfortunate it's a browser issue :( Maybe there's a place to subtly warn users this might happen?
@gargol Agree that the only problem only exists with initial upload, and after that it's fine.


Viewing Logs is broken in Firefox

Get an error in the browser page about getLogs not being defined.
Off of requireify branch.

:+1:

Closing, fixed in dev-requireify


[Hold for #49539][$250] Android - Workspace - User is redirected to previous page when deleting current workspace

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.57-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5180087&group_by=cases:section_id&group_order=asc&group_id=296775
Issue reported by: Applause - Internal Team
Action Performed:

Open the Expensify app
Tap on the workspace selector on the top left corner
Select any workspace
Tap on settings on the bottom of the page
Tap on "Workspaces"
Tap on the three dots icon of the currently selected workspace and delete it
Verify the app remains on the workspaces list page after the workspaces was deleted

Expected Result:
After deleting current workspace, user should remain on the workspaces list tab
Actual Result:
User is redirected to previous page instead of staying on workspaces list tab, after deleting currently selected workspace
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Standalone
[x] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/7a619fbe-72c9-443a-ac5f-68336bf2243e
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021853673909103643294
Upwork Job ID:<PHONE_NUMBER>103643294
Last Price Increase: 2024-11-05

Issue OwnerCurrent Issue Owner: @ntdiary

this can be reproduced outside of the Hybrid app so adding External

Proposal
Please re-state the problem that we are trying to solve in this issue.
User is redirected to previous page instead of staying on workspaces list tab, after deleting currently selected workspace
What is the root cause of that problem?
We call navigateWithSwitchPolicyID without route param after we delete the active policy then it goes back to the previous page.
https://github.com/Expensify/App/blob/af2d2c6fae67be99b97ccd619c9aa71821b5082f/src/pages/workspace/WorkspacesListPage.tsx#L136-L142
What changes do you think we should make in order to solve the problem?
I don't think we need to navigate to another page because we've already been on the workspace list page. We can simply remove Navigation.navigateWithSwitchPolicyID({policyID: undefined}).
https://github.com/Expensify/App/blob/af2d2c6fae67be99b97ccd619c9aa71821b5082f/src/pages/workspace/WorkspacesListPage.tsx#L136-L142
What alternative solutions did you explore? (Optional)

@ntdiary can you take a peek at these proposals when you have a moment? Thank you!

Oh yes, that sounds good - let's hold for 49539 and retest again

Hold for https://github.com/Expensify/App/pull/49539

Hold for https://github.com/Expensify/App/pull/49539

Hold for https://github.com/Expensify/App/pull/49539

Hold for https://github.com/Expensify/App/pull/49539

Hold for https://github.com/Expensify/App/pull/49539

Hold for https://github.com/Expensify/App/pull/49539


Baking: Update baker stake

Task description
If an account is already registered as a baker, the user will have the option to press the "Update baker settings" button, on the baker status page. This will give the user a drop down, which in turn will let the user choose the option "Update baker stake".
This option will start a flow very similar to the one for registering a baker, except it will not contain any of the parameters related to the pool of the baker. Instead, what can be changed is the following:

Baker stake
Restake status

Each of the parameters are technically optional, but if the user ends up in a situation where they are about to submit a transaction with no changes, they will be stopped by a notification (this can be seen in Scenario 4 in the Update baker stake flows box in Figma.)
In Figma three scenarios can be found (besides Scenario 4 mentioned above)  Update baker stake flows. Common for all the scenarios is that they are started in the same way from the baker status page, and that they begin with a skippable version of the carousel explaining baking.
Scenario 1:
Scenario one displays all the steps of the Update baker stake flow. In this scenario the stake is increased and the restake status is left unchanged.

The amounts page is the same as seen in the Register baker flow, including error messages.
The presubmission transaction overview is also similar, but now showing only the affected parameters.
The overview after submission is also similar, but again just showing the affected parameters.
Before being led to the baker status page, the user is presented with a notification telling them that the update will take effect from the next pay day.

Scenario 2:

Scenario 2 is similar to scenario 1, except this time the amount is decreased. This will change the notification shown before the user is led back to the baker status page, which will now also say that there will be a cool down for the decreased amount.

Scenario 3:

Scenario three is also similar, with the exception of the amount input field being locked. This is because the amount cannot be changed in a scenario, where the amount is in a cool down due to being decreased, or if the baker is in shut down cool down.

@jens-concordium
I don't know if this is intended.
But no matter which option I choose ('Update baker stake', 'Update pool settings', 'Update baker keys') I end up in the generic guide for 'updating baker settings' which covers all the above.
Maybe the guide should be split up into three individual parts? Such that when I click 'Update pool settings' I don't land on a guide that explains all three possibilities starting with 'Update baker stake'.
Also the full guide is shown even if I already did carry out a 'Update baker stake'.

The baker stake is functional. I can update the baker stake.

Yeah, that was intentional. Ideally it would be split out, but we decided to go with a single guide, to cut some development time.

3.0.0 (48)


ClientId - Seems to not be getting set

First off thanks for publishing this repo - nicely written.
I'm on a blazor wasm myself project and really like the way you've componentized the various aspects of rendering PBI in Blazor.
First off I'm simply running this project with any updates of modification to get it going before adapting slightly for wasm.
Unfortunately I'm seeing this exception the app.Run(); call is made:

ArgumentNullException: IDW10106: The 'ClientId' option must be provided.
Microsoft.Identity.Web.MergedOptionsValidation.Validate(MergedOptions options)

My initial thoughts were I've not set the Azure App Registration up correctly of I 've messed up the appsettings.
I've turned off secrets while I try to work through it doubled checked everything in terms of guids being set correctly.
I'd be interested firstly if you have a success in the 'ClientId' being set?
My appsettings.json:

Hi and thanks for trying out the repo in addition to leaving a comment.
So the ClientId is still being set by the Microsoft Identity layer here
AstroPanda.Blazor.PowerBI.Demo/Program.cs#L8-L9
If you're trying to set the Azure AD configuration you'll need to make sure you're grabbing the right configuration section.
However, I'm noticing now that the Demo app is targeting an AzureAd section. I think I just forgot to change it before pushing last time. I'm willing to bet that if you're trying to run the Demo app it's failing because of lines 8 and 9 in Program.cs

One other thing I'd like to point out is that this project is originally set up to run in Blazor Server mostly because the configuration uses Client secrets and you're access your Power BI workspace as a Service Principal. It's not really recommended to keep those service principal secrets on the client.
However,  we do have plans to break this a part a bit and provide some Web API middleware though so that the components can still run other Blazor WASM and have a quick wire-up with an API that contains the secrets but serves out the embedding tokens needed to show the report.
Please let me know if what I've mentioned is helpful! Good luck!

By the way, we've been working on a getting started wiki in case you've not seen it yet.
Getting Started
If you find it helpful, I'd appreciate any feedback you've got!


C# Snippet updates

Fixes #836 (Async snippets not using CreateAsync)

Current coverage is 82.04% (diff: 100%)

Merging #837 into master will not change coverage

@@             master       #837   diff @@
==========================================
  Files           321        321
  Lines         12393      12393
  Methods           0          0
  Messages          0          0
  Branches       1625       1625
==========================================
  Hits          10168      10168
  Misses         1801       1801
  Partials        424        424

Powered by Codecov. Last update 196b6a0...80542b0

PTAL


testing/crypto: change crypto module testcase into cmocka

Unified crypto testcases using cmocka testing

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.makejian seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Prevent standard build jobs from building type=Release

Release builds should only be built using the release pipeline build jobs

is this still an open issue?

No this is fine, thanks


Spell 24 - s_wall_of_stone

The Duration in spelldef doesnt work, you can set 10000 or 0, the wall will always last for around 10s.
Other field spells seems to work well.
probably bugged?

I set it to 1 and it lasted one second

With X-PACK? even tho there is this?
[ITEMDEF 080] //This is the hardcoded ITEMDEF used by Wall of Stone spell //It has been excluded from the i_wall_hugebrick DUPELIST on purpose on @create if <serv.spell.<morex>.flags>&SPELLFLAG_FIELD timerf 1,timer = <R10,15> endif

Oh looks like setting one second in the duration field of the SPELLDEF makes the stone wall disappears before the timerf sets the 10,15 seconds timer. Anyway you should comment it

It's a scriptack x bug btw

Oh looks like setting one second in the duration field of the SPELLDEF makes the stone wall disappears before the timerf sets the 10,15 seconds timer. Anyway you should comment it

of course i did comment it, but still the timer is always 10s 😁

Change the timer on spelldef duration


Automated Package Upgrade

:tada: This PR is included in version 5.0.482 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unable to update via pip3 due to error.

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version): 0.35.3 (Issue is with the upgrade process)
Python release (python3 --version): Python 3.4.2
Component/platform:
Updater (pip3 install homeassistant --upgrade)
Description of problem:
Pip seems to be throwing exceptions when trying to upgrade to 0.36
Expected:
No errors
Problem-relevant configuration.yaml entries and steps to reproduce:

sudo su -s /bin/bash homeassistant
source /srv/homeassistant/homeassistant_venv/bin/activate
pip3 install --upgrade homeassistant

Traceback (if applicable):
Using cached voluptuous-0.9.3.tar.gz
Exception:
Traceback (most recent call last):
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/basecommand.py", line 215, in main
status = self.run(options, args)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/commands/install.py", line 335, in run
wb.build(autobuilding=True)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/wheel.py", line 749, in build
self.requirement_set.prepare_files(self.finder)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/req/req_set.py", line 380, in prepare_files
ignore_dependencies=self.ignore_dependencies))
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/req/req_set.py", line 487, in _prepare_file
req_to_install, finder)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/req/req_set.py", line 428, in _check_skip_installed
req_to_install, upgrade_allowed)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/index.py", line 465, in find_requirement
all_candidates = self.find_all_candidates(req.name)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/index.py", line 423, in find_all_candidates
for page in self._get_pages(url_locations, project_name):
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/index.py", line 568, in _get_pages
page = self._get_page(location)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/index.py", line 683, in _get_page
return HTMLPage.get_page(link, session=self.session)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/index.py", line 792, in get_page
"Cache-Control": "max-age=600",
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/_vendor/requests/sessions.py", line 488, in get
return self.request('GET', url, **kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/download.py", line 386, in request
return super(PipSession, self).request(method, url, *args, **kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/_vendor/requests/sessions.py", line 475, in request
resp = self.send(prep, **send_kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/_vendor/requests/sessions.py", line 596, in send
r = adapter.send(request, **kwargs)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/_vendor/cachecontrol/adapter.py", line 37, in send
cached_response = self.controller.cached_request(request)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/_vendor/cachecontrol/controller.py", line 111, in cached_request
resp = self.serializer.loads(request, cache_data)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/_vendor/cachecontrol/serialize.py", line 114, in loads
return getattr(self, "_loads_v{0}".format(ver))(request, data)
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/pip/_vendor/cachecontrol/serialize.py", line 176, in _loads_v2
cached = json.loads(zlib.decompress(data).decode("utf8"))
zlib.error: Error -3 while decompressing data: incorrect data check
Additional info:

if you need any more details, holler.

Looks like pip's cache may be corrupted. Try this:
pip3 install --upgrade homeassistant --no-cache-dir

That seems to have fixed it.  issue closed.


[Done] Allow linearrings with 3 coordinates in GEOS 3.10

See also my comments at https://github.com/pygeos/pygeos/issues/233#issuecomment-849483828. I don't know how much I looked at it in detail at that point, but if such linearrings are invalid, it might be nice to continue raise an error for it in the linearrings constructor

continue raise an error for it in the linearrings constructor

I agree.  Since linearrings is invoked within the user's control to provide better coordinates, invalid rings should be caught.
In contrast, we should allow invalid linear rings that come in from WKB / WKT so that they can at least be deserialized and then repaired.
So as a general rule I'm thinking (outside scope of this PR, but just adding here for context):

create invalid geometry manually => exception
create invalid geometry from serialized form => warning

The relevant issue is this one: https://github.com/libgeos/geos/issues/406
The amount of coordinates allowed in a linearring was deliberately reduced to 3. I think it is best to not build different logic in pygeos and allow construction of 3-coordinate rings.

I was reading up on the issue and I actually think @brendan-ward 's idea is a good general guideline, which I also like to implement for NaN-valued coordinates which lead to invalid geometries also:

create invalid geometry manually => exception
create invalid geometry from serialized form => warning

This could be done in this PR.

Done, I made it a ValueError. The NaN stuff can be addressed another time.

Regarding the general rule of

create invalid geometry manually => exception
create invalid geometry from serialized form => warning

I agree with it for the default behaviour, but just want to point out that also the "manual" creation functions can be used in a deserialization context (if the format is storing raw coordinates arrays instead of some custom binary/text format). So I think ideally even for those manual creation functions there would be an option to have it only raise a warning and not error.

Now, for linearrings of 3 coordinates that's maybe less of an issue (I think for NaNs it might be more important to have an escape hatch)


Best way to call a controller action method programatically and return IActionResult

I'm following up with issue opened on home repository: https://github.com/aspnet/Home/issues/1543
I guess that was a wrong place to ask the question.
How to call a controller action method in C# and get IActionResult back from the executed controller?

Is your question still about use of methods in Internal namespaces, specifically whether using ControllerActionExecutor is the right thing to do for your CMS scenario?
If yes, the answer is "it depends". Classes in Internal namespaces are subject to change and not intended for primary scenarios. But of course, your scenario may need ControllerActionExecutor and you might be fine with future breaking changes.
@sebastienros may have some ideas on alternate approaches for your scenario. Or you could start with Orchard 2 instead of "just" MVC.
One thought: Would creating an alternate IViewComponentInvoker which delegates to DefaultViewComponentInvoker and does extra stuff in InvokeAsync() work for you?

Thanks @dougbu for replying.
I have tried ViewComponents, however, it doesn't support other verbs such as POST, PUT and DELETE. I guess ViewComponents are ideal for rendering trivial components such as navigation and language switcher.
Area is appropriate to build modular components such as Login/Registration, because it supports all verbs and return IActionResults. These components could be rendered anywhere in the website.
In future, it would be highly appreciated when the method "ControllerActionExecutor.Execute()" is available for primary scenarios.

My apologies for the confusing mention of view components; they are not controllers. I was looking at the wrong use of ControllerActionExecutor and should have mentioned IActionInvoker and ControllerActionInvoker. But that wouldn't have been useful since even the ControllerActionInvokerProvider is in an Internal namespace. Just ignore that last paragraph...

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


Implement VitsSVC resume training / finetune feature

✨ Description:
This PR addresses bugs in VitsSVC module, mainly related to:

implement resume training / finetune feature
fix bug for multiple acoustic content training

🚧 Related Issues:
#91
👨💻 Changes Proposed:

[x] Fix bug in models/svc/vits/vits.py, removed useless content_vec feature dependency.
[x] Refractor VitsSVCTrainer to detach from TTSTrainer

🧑🤝🧑 Who can review?
@RMSnow @lmxue
🛠 TODO

[x] Further clean up config
[x] Refractor VitsSVCTrainer to detach from TTSTrainer

✅ Checklist:

[ ]  Code has been reviewed
[x]  Code complies with the project's code standards and best practices
[x]  Code has passed all tests
[x]  Code does not affect the normal use of existing features
[x]  Code has been commented properly
[ ]  Documentation has been updated (if applicable)

Just fixed problem 1, now this PR doesn't affect tasks other than SVC.

Now the default training data config is the same across DiffWaveNet and VitsSVC. The exp_config.json is now user-friendly with fewer exposed options. I'll refractor SVC preprocess to svc.json in another PR soon.


[BUG] Cannot install the package due to react-native-reanimated version conflict

Describe the bug
I cannot install the package in the first place due to react-native-reanimated version conflict. My project uses npm and not yarn.
To Reproduce
Steps to reproduce the behavior:

Have a React Native project with versions:

"react-native": "0.72.5",
"react-native-reanimated": "^3.5.4",

npm i react-native-notificated
Error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react-native-reanimated
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-native-notificated
npm ERR!   react-native-notificated@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Expected behavior
To be install the package
Possible Solution
To use the version from the root project if detected.

Hi @hpelitebook745G2, thanks for bringing it up, we will address this issue and let you know. For now, please try installing the package with --legacy-peer-deps  or downgrade the root version to 2.x.x. The library is working with reanimated 3.x.x (I was using it with Expo recently).

Hi @hpelitebook745G2, this has been fixed with v0.1.4, please let me know if you have other issues :)


cyclonev.h needs a pos_t to BEL lookup function

To match nextpnr's Arch::getTileBelDimZ

Added fa687fa52eddd5c0e6cb2dd92448a3040a550c43

Added fa687fa52eddd5c0e6cb2dd92448a3040a550c43


Compilation error with vue-cli

ERROR in ./~/babel-loader/lib!./~/vue-loader/lib/selector.js?type=script&index=0!./~/vue2-timepicker/src/vue-timepicker.vue
Module build failed: ReferenceError: Unknown plugin "transform-runtime" specified in "/Users/kmaxat/Development/vue-test/node_modules/vue2-timepicker/.babelrc" at 0, attempted to resolve relative to "/Users/kmaxat/Development/vue-test/node_modules/vue2-timepicker"
at /Users/kmaxat/Development/vue-test/node_modules/babel-core/lib/transformation/file/options/option-manager.js:176:17
at Array.map (native)
at Function.normalisePlugins (/Users/kmaxat/Development/vue-test/node_modules/babel-core/lib/transformation/file/options/option-manager.js:154:20)
at OptionManager.mergeOptions (/Users/kmaxat/Development/vue-test/node_modules/babel-core/lib/transformation/file/options/option-manager.js:229:36)
at OptionManager.init (/Users/kmaxat/Development/vue-test/node_modules/babel-core/lib/transformation/file/options/option-manager.js:374:12)
at File.initOptions (/Users/kmaxat/Development/vue-test/node_modules/babel-core/lib/transformation/file/index.js:216:65)
at new File (/Users/kmaxat/Development/vue-test/node_modules/babel-core/lib/transformation/file/index.js:139:24)
at Pipeline.transform (/Users/kmaxat/Development/vue-test/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
at transpile (/Users/kmaxat/Development/vue-test/node_modules/babel-loader/lib/index.js:38:20)
at Object.module.exports (/Users/kmaxat/Development/vue-test/node_modules/babel-loader/lib/index.js:133:12)
@ ./~/vue2-timepicker/src/vue-timepicker.vue 8:18-108
@ ./~/vue2-timepicker/index.js
@ ./src/main.js

Sorry for the long wait. The latest release v0.2.0 has upgraded to support vue-cli now.

Related to #15


Spotlight prediction market

General
Closes UI part of #120
Implemented all stated UI for tables with prediction markets overview and market details (opinions related to market).
Implemented fetching of markets and opinions from blockchain.
Implemented modals for PM creation, Opinion adding, PM resolution.
Implemented filter features for markets and opinions tables.
Left to do / clarify:

[ ] Use action to create prediction market
[ ] Use action to buy/sell PM assets (submit opinion)
[ ] Use action to resolve PM
[ ] Use action to cancel owned opinions
[ ] Fix unstable issues with opinions fetching from MarketsStore
[ ] Improve filter features

UX issues to discuss:

[ ] yes/no buttons seems like does no effect from UX point of view
[ ] resolution date (expiry) is not present in most prediction markets and not reflected in UI
[ ] It is not clear what does opinions table contain
[ ] Opinions table is out of screen, when there are PMs with long description
[ ] Resolved PMs are positionaly displayed in overview table

General
Please make sure the following is done:

Pull request is onto develop
If you haven't already, have a look at

https://github.com/bitshares/bitshares-ui/blob/develop/CODE_OF_CONDUCT.md
https://github.com/bitshares/bitshares-ui/blob/develop/CONTRIBUTING.md

Code Preparation
Please review all your changes one last time before committing

[ ] Check for unused code
[ ] No unrelated changes are included
[ ] None of the changed files are reformatting only
[ ] Code is self explanatory or documented
[ ] All written text is properly translated (english language)

Testing
The branch has been tested on the following browsers (desktop and mobile view)

[ ] Chrome
[ ] Opera
[ ] Firefox
[ ] Safari

User interface changes
Delete this section if there weren't any UI changes. Please make sure you tested your changes in all themes

[ ] Dark
[ ] Light
[ ] Midnight

Please provide screenshots/licecap of your changes below

Forwarding this for testing


Support configuration of overscroll effects in commonMain

Android has LocalOverscrollConfiguration that configures Android-style overscroll, and has the overscrollEffect argument in Modifier.scrollable
Desktop/web don't have overscroll at the moment
iOS has a custom overscroll effect via CupertinoOverscrollEffect, and the current LocalOverscrollConfiguration isn't applicable for it (it doesn't have glowColor or drawPadding). But sometimes it needs to be configured. For example, we need to configure should we always apply overscroll, or configure the spring effect stiffness. Possible solutions:

make LocalOverscrollConfiguration expect/actual
deprecate LocalOverscrollConfiguration and provide LocalOverscrollEffect instead
deprecate LocalOverscrollConfiguration and provide LocalScrollableConfiguration instead
deprecate LocalOverscrollConfiguration, allow configuration only per-widget basis (LazyList, scrollable)

It would be amazing if ComposeMP had a custom overscroll effect (like in IOS but in other platforms too) and let us customize it. Android overscroll effect is very limited and if you have a lower Android version, the "Stretch overscroll" is not there. In my humble opinion, stretch overscroll should be implemented in all android versions! (i dont know if that possible or not)

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


feat(split): added skeleton component

Added a skeleton component to display when the Split test is still not ready.

Closing this PR and I'll open a new one.


VSTS task "Update Service Fabric Manifests" removes   tag from ApplicationManifest.xml

Hi,
After executing the "Update Service Fabric Manifests" task in Azure Pipelines, the <ManagedIdentities> tag is removed from the enclosing <Principals> tag. I use the task to update the manifest versions.
Regards,
Wouter

So, it turns out that the issue is actually caused by SF's MSBuild tooling 'cleaning' the manifest. I suspect that the sdk/tooling version in Azure Pipelines is not yet updated with a version that supports these tags so they are removed. Running the same MSBuild command on a machine that does have the latest sdk/tooling does not remove the tags.
As a workaround you can update the .sfproj files with the <UpdateServiceFabricApplicationManifestEnabled>false</UpdateServiceFabricApplicationManifestEnabled> property to prevent the cleanup tool from running.


MudMessageBox: Completely broken on published app - System.MissingMethodException: Arg_NoDefCTor

Bug type
Component
Component name
MudMessageBox
What happened?
Using the ShowMessageBox method exactly as in the docs:
await DialogService.ShowMessageBox("Warning", new MarkupString("Are you sure you want to delete this?"))
when triggered on a published app gives this error:

blazor.webassembly.js:1 crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: Arg_NoDefCTor, MudBlazor.MudMessageBox
System.MissingMethodException: Arg_NoDefCTor, MudBlazor.MudMessageBox
at System.RuntimeType.CreateInstanceMono(Boolean , Boolean )
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean , Boolean )
at System.Activator.CreateInstance(Type , Boolean , Boolean )
at System.Activator.CreateInstance(Type , Boolean )
at System.Activator.CreateInstance(Type )
at Microsoft.AspNetCore.Components.DefaultComponentActivator.CreateInstance(Type )
at Microsoft.AspNetCore.Components.ComponentFactory.InstantiateComponent(IServiceProvider , Type )
at Microsoft.AspNetCore.Components.RenderTree.Renderer.InstantiateComponent(Type )
at Microsoft.AspNetCore.Components.RenderTree.Renderer.InstantiateChildComponentOnFrame(RenderTreeFrame& , Int32 )
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewComponentFrame(DiffContext& , Int32 )
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewSubtree(DiffContext& , Int32 )
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InsertNewFrame(DiffContext& , Int32 )
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InsertNewFrame(DiffContext& , Int32 )
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InsertNewFrame(DiffContext& , Int32 )
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& , Int32 , Int32 , Int32 , Int32 )
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.ComputeDiff(Renderer , RenderBatchBuilder , Int32 , ArrayRange1 , ArrayRange1 )
at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder , RenderFragment , Exception& )
at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry )
at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()

Expected behavior
Should work like in the docs
(reproduction link is missing because it can be reproduces only after publishing the app)
Reproduction link
https://try.mudblazor.com/
Reproduction steps

Use the show messagebox like in the docs
Publish the app
Trigger the action that shows the messagebox
The error occures

Relevant log output
No response
Version (bug)
6.0.14
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Mac OSX
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

Hi, I'd just like to confirm we are experiencing the exact same issue - all the MudMessageBox components are broken in our test build with 6.0.14 - we'll be reverting until it's fixed

Hi
I have the same issue when I try to use ShowMessageBox

Duplicate of https://github.com/MudBlazor/MudBlazor/issues/4822
There is also a work-around posted in this issue to resolve the issue.

This issue is now closed due to duplicate. If you have further thoughts, please comment or open a new issue.


ValueError: Variable types cannot be inferred from Dask DataFrames, use variable_types to provide type metadata for entity

Hi There
I was using dask dataframes with featuretools because I wanted to see if it can help me ovecome the memory problems I'm having when using pandas df.
I took my dataframe and converted it to a dask dataframe:
df[cats] = converterdDF[cats].astype('category')
df[NumericColumns] = converterdDF[NumericColumns].astype('float64')
dask_df = dd.from_pandas(df, npartitions=2)
then pass it to featuretools :
es = ft.EntitySet(id="dask_es")
es = es.entity_from_dataframe(entity_id="dask_entity", dataframe=dask_df, index="ticker" )
but I get this error:
ValueError: Variable types cannot be inferred from Dask DataFrames, use variable_types to provide type metadata for entity
I am not sure what to do and manually adding the columns is a bit difficult since it's over 100 columns.
Has anyone experienced a similar issue? or provide any advice?

I think I figured it out
dt.update(dict.fromkeys(cat, ft.variable_types.Categorical))
dt.update(dict.fromkeys(NumericColumns, ft.variable_types.Numeric))
then updating this line seemed to have fixed it
es = es.entity_from_dataframe(entity_id="dask_entity", dataframe=dask_df, index="ticker", variable_types = dt)

@gautambak Thank you for reaching out with this issue, and glad to hear you were able to resolve the issue successfully.
As you discovered the current implementation in Featuretools does not perform type inference if a Dask DataFrame is used when creating an Entity. This is because performing type inference requires pulling the data into memory to access the column values. As a result, users are currently required to manually specify variable types for all columns in the Entity.
For reference, this guide provides some additional information on using Dask DataFrames with Featuretools: https://featuretools.alteryx.com/en/stable/guides/using_dask_entitysets.html
Please let us know if you find any additional issues.


Example in az container create -h uses incorrect registry-login-server parameter

When issuing a call to az container create -h, the first Image Registry argument is listed as --registry-login-server, but the last example uses --registry-server.
I tested the --registry-server argument to see if it was an alias for the correct argument, but it yielded the error message:
az: error: unrecognized arguments: --registry-server test.com

https://github.com/Azure/azure-cli/pull/4208

Fixed.


try and install master sunpy on travis

Didn't work...Hmmm.  I wonder what is the answer?

ah that looks like a packaging bug in cube. I will have to investigate when I have more time.

At least you have an idea of what it might be now :)


Do not log the app key/secret

Not sure if this falls under the umbrella of issue #38 or not, but I thought it deserves its own issue.  This is obviously a security issue and should not be logged

👍

may i suggest partial blackout to validate the expected key is there
app_secret=Xg5*****Fed


fix: Local resource error in some entrypoint

Purpose of the pull request

Fix createResource, queryResourceListPaging, onlineCreateResource resource error in local resource, otherwise will raise error  in those entry point
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #14826 (d809991) into dev (3148dba) will decrease coverage by 0.06%.
The diff coverage is 16.66%.

:exclamation: Current head d809991 differs from pull request most recent head b274846. Consider uploading reports for the commit b274846 to get more accurate results

@@             Coverage Diff              @@
##                dev   #14826      +/-   ##
============================================
- Coverage     38.90%   38.85%   -0.06%
+ Complexity     4595     4587       -8
============================================
  Files          1232     1232
  Lines         43243    43192      -51
  Branches       4785     4772      -13
============================================
- Hits          16825    16783      -42
+ Misses        24556    24543      -13
- Partials       1862     1866       +4

Files Changed
Coverage Δ

...heduler/api/service/impl/ResourcesServiceImpl.java
44.11% <16.66%> (-0.37%)
:arrow_down:

... and 47 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix capitalization in title

This was noticed by UX after we merged the previous PR to update the title.
Developer
Accessibility

[ ] ANDI or WAVE has been run in accordance to our guide.
[ ] This PR contains no changes to the view layer.
[ ] New issues flagged by ANDI or WAVE have been resolved.
[ ] New issues flagged by ANDI or WAVE have been ticketed (link in the Pull Request details above).
[ ] No new accessibility issues have been flagged.

New ENV

[ ] All new ENV is documented in README.
[ ] All new ENV has been added to Heroku Pipeline, Staging and Prod.
[ ] ENV has not changed.

Approval beyond code review

[ ] UXWS/stakeholder approval has been confirmed.
[ ] UXWS/stakeholder review will be completed retroactively.
[ ] UXWS/stakeholder review is not needed.

Additional context needed to review
E.g., if the PR includes updated dependencies and/or data
migration, or how to confirm the feature is working.
Code Reviewer
Code

[ ] I have confirmed that the code works as intended.
[ ] Any CodeClimate issues have been fixed or confirmed as
added technical debt.

Documentation

[ ] The commit message is clear and follows our guidelines
(not just this pull request message).
[ ] The documentation has been updated or is unnecessary.
[ ] New dependencies are appropriate or there were no changes.

Testing

[ ] There are appropriate tests covering any new functionality.
[ ] No additional test coverage is required.

Merging without review as it's changing one letter in the copy.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 99.274%

Files with Coverage Reduction
New Missed Lines
%

app/controllers/search_controller.rb
1
98.1%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
547

Relevant Lines:
551

💛  - Coveralls


Add details about building with logs to project setup

What
Add details about building with logs to project setup.
Why

Something went wrong with PR preview build please check


Information on AMM and Clawback collaboration

It is not clearly stated that AMM pools cannot be created with tokens that have Clawback enabled.

It's listed here: https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0039d-clawback#7-compatibility-with-automated-market-maker-xls-30

This statement gives the perception that it is possible to create an AMM pool with Clawbackable tokens, but it is not possible to Clawback from the AMM pool.
A statement regarding AMMCreate transactions is needed.

Thanks for catching this!  We can update the Clawback spec to explicitly state this.  I believe this Clawback spec was derived before the AMMCreate behavior was fully finalized, and now we can update the spec to define the behavior clearer

https://github.com/XRPLF/xrpl-dev-portal/pull/2245 fixes this on the dev portal


Huffman Bug Fix

I noticed one cleanup & one bugfix while looking into the huffman algorithm:

the cleanup: we can use a u128 to guarantee no overflows, and saturating_add to guarantee reasonable behavior in any case
the bug: the binary heap is a max heap so the behavior ends up merging the nodes of the most likely entries repeatedly. a huffman encoder requires merging the least likely elements, so it should be reversed.

a currently failing test https://github.com/rust-bitcoin/rust-bitcoin/pull/700
that passes if rebased on this branch.

I think u128 is supported on all platforms, either with a native type or a wrapper. We could also do the same trick with u32 and u64 and it wouldn't be an issue either (u32 is plenty IMO).


Enable sourcemaps for the runtime builds

Improve debugging experience of the runtime

@Janpot

perhaps, it's a problem with the .next folder in the toolpad-app.
Despite the fact that I can develop, it’s not efficient.
and I can't clearly see what the React component name is.
I'm sorry to bother you.

I have tried to directly run the toolpad-app
But it relied on a lot of other stuff.
if you can do, please sharing your idea.

To work on Toolpad you'll have to do the following

Run yarn dev. This will buid all the packages in watch mode
Launch toolpad in dev modeyarn toolpad dev test/integration/backend-basic/fixture --dev

It's important to note the difference between yarn toolpad dev and the --dev parameter. The first instruction runs Toolpad in dev mode. The --dev parameter is one for contributors only and runs the underlying next.js app that powers the editor in dev mode.

I'm updating the contributing guide in https://github.com/mui/mui-toolpad/pull/2149


Hello, can i add the Admins / Server from Sourceban?

Hallo,
is there a opinion that i can import Settings from SB 1.8? Admins, Servers?
Many thanks for u

Hallo,
is there a opinion that i can import Settings from SB 1.8? Admins, Servers?
Many thanks for u

Hi, this would be a somewhat complex feature to do, because the DB structures of SourceBans and SourceAdmin are completely different, but it is something to consider in the future.


Switch to kctfork for Kotlin compilation testing

The original project doesn't seem to be actively maintained. It's safe to assume that Zac will continue to maintain this fork for the foreseeable future.
The fork is already updated for 1.9.20. Sticking with the original project will block us for 1.9.20 due to https://github.com/tschuchortdev/kotlin-compile-testing/issues/390.

Warnings

:warning:
This PR is approved with no milestone set. If merged, it won't appear in the detekt release notes.

  Generated by :no_entry_sign: dangerJS against 5dca2a85c4ffe8b92169a81d4ac0d7a042837f9a


Documentation for working of the project

An md file to be created to add the workflow and how the project works generally.
This should be a beginner friendly document so that they should know how things are working behind the scenes
Make it interactive with emojis, images and memes
For ex: Suppose in a DisplayCard.js we have used Github apis so you should write in a layman's language in the document about their working and how they function. Then move on to the technical aspects like the API calling and parameters.
Naming convention: WORKFLOW.md

can I work on this issue @garimasingh128

Thanks @garimasingh128


updated footer , added try app

Please pull first when you are developing further because I have made some changes like adding links to our pages and styling.


Feat/multi test case handling

Optional parameter added to function createTestRun: Reduces run to only tests in parameter array (fix for all testcases staying 'InProgress')
Added continuiation token in testCasesPoints: with old function maximum 200 testcases were extracted
Added testcase comment for failed results
Set failed result to dominant result (needed for: 2 automated testcases linked to one manual testcase)

maybe you can also have a look if the package runs well. i am not able to run it properly because husky is throwing an error. maybe updating packages?
terminal: npm i gianlucamangiapelo/azuredevops-test-reporter#pull/1/head
npm ERR! command failed
npm ERR! command sh -c -- husky install
npm ERR! .git can't be found (see https://git.io/Jc3F9)


Calculation of DASH Live Edge with large propagation delays whilst using SegmentTemplate

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
4.7.2
What browser and OS are you using?
Latest Chrome, various OSes.
Please ask your question
We have a live encoded DASH dynamic manifest being produced by a 3rd party and we are using Shaka to play it. In between the writing of the DASH files and the ability to read it are various layers of network latency and cloud storage mirroring etc. This results in the manifest and media files which are seen by the player being about 90s behind wall clock time. :-(
From looking at network activity and reading "Live Edge" here I can see the player is doing what is documented i.e. it calculates the live edge as:
video.currentTime = now - ast - maxSegmentSize;
Unfortunately that calculation is about 90s ahead of what is actually available in terms of media segments to read (hence we hit 404 errors reading segments).
I understand there is the possibility of specifying MPD@suggestedPresentationDelay as 90 seconds and this could potentially solve the issue. However unless I am mistaken, for other players which are sited closer to the encoder and using non-mirrored storage, this delay would be excessive and unnecessary i.e. we would need to request manifest output incorporating the worst case propagation delay.
In the manifest we have the segment template as follows which has no indication of the current last segment number:
<SegmentTemplate timescale="60000" initialization="test065_ICh24._V_0.proxy.mp4" media="test065_ICh24._V_$Number$.proxy.mp4" duration="480480" startNumber="0"/>
but we also have `mediaPresentationDuration="PT296.296000S" in the manifest which is updated periodically.
What we are effectively seeing is that the edge time is being calculated as about 90s greater than the currently published  mediaPresentationDuration. So my questions are:

What are we missing which could just make this work?
Could/should the player edge time be calculated as: video.currentTime = Min(now - ast - maxSegmentSize, mediaPresentationDuration);

As an update to this, I can see in the Shaka Player code that the manifest mediaPresentationDuration attribute is only ever examined when the playlist is type = static. So it seems quite hard to even prototype this approach.
I have checked in the MPEG standard and there are examples of manifests with type=dynamic and which have a  mediaPresentationDuration.
I should also say that part of the problem we are having is because we are dealing with a manifest which only has a segment template and does not provide a segment timeline.
But maybe I am still missing something...

A further update...
I realise with a <SegmentTimeline> element included the problem disappears. e.g. with the following, there is no knowledge of the currently available segments and hence the player tries to play up to the current wall clock time and gets 404s:
<SegmentTemplate timescale="60000" initialization="test065_ICh24._V_0.proxy.mp4" media="test065_ICh24._V_$Number$.proxy.mp4" duration="480480" startNumber="0"/>

But with the following, the player knows the currently available segments and the problem disappears:
<SegmentTemplate timescale="60000" initialization="test065_ICh24._V_0.proxy.mp4" media="test065_ICh24._V_$Number$.proxy.mp4" duration="480480" startNumber="0">
    <SegmentTimeline>
        <S t="0" d="480480" r="14" />
    </SegmentTimeline>
</SegmentTemplate>

I do think taking account of mediaPresentationDuration if it exists for a dynamic manifest would also work, however I realise the likelihood of this being implemented is minimal. I am hoping I have a chance of getting the 3rd party vendor to change their MPD generation to include the <SegmentTimeline> element and hence will close this issue.


Incompatible with lua versions >=5.2

Issue in markdown.lua line 124:
setfenv(1, M)

The function is not available in following versions.
Did not manage to have a more detailed look yet. Maybe I find some time to provide a PR in the following weeks.

I have no relation to this repo, just randomly saw this bug but you can provide your own ‘setfenv’ implementation in newer Lua versions.
local function setfenv(fn, env)
  local i = 1
  while true do
    local name = debug.getupvalue(fn, i)
    if name == "_ENV" then
      debug.upvaluejoin(fn, i, (function()
        return env
      end), 1)
      break
    elseif not name then
      break
    end

    i = i + 1
  end

  return fn
end

See this post for more info!

I tried to give the library a spin but just implementing the setfenv function as described in the post is not enough, the code is still broken in 5.2 and up.


Fix a long lasting "pip install" issue which will loss files in asset

What changes do you make in this PR?

Please describe why you create this PR

close #234
Checklist

[ ] I have merged the latest main branch into current branch.
[ ] I have run bash scripts/format.sh before merging.
Please use "squash and merge" mode.

I test it in Windows 11. It works and everything work well by using
 pip install git+https://github.com/metadriverse/metadrive.git@fix-asset-copy

Therefore, merge this PR when all tests pass!


Drop zone component ?

Would it be possible to add a drop zone component ? Thanks for the amazing work!! :D

https://github.com/shadcn-ui/ui/issues/163

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

I created a simple version of the drop-zone component, published as shadcn-dropzone. ✨
yarn add shadcn-dropzone

Here is an example of how you would use it:
<Dropzone
  onDrop={(acceptedFiles: File) => {
    // Do something with the files
  }}
>
  {(dropzone: DropzoneState) => (
    <>
      {
        dropzone.isDragAccept ? (

Drop your files here!

        ) : (

              Upload files

        )
      }

        { dropzone.acceptedFiles.length } files uploaded so far.

    </>
  )}
</Dropzone>

Demo: https://diragb.github.io/shadcn-dropzone

@diragb the demo site is down

@diragb the demo site is down

Thanks for this, it's up now.

is there any chance this might become part of the official shadcn repo ? @shadcn ? :)

Filepond also looks good.
Currently I am using this with modifies CSS with shadcn/ui

Hey everyone! 👋
I was also looking for a shadcn-ui drag and drop component. I was here earlier in the day and read up on the discussion. Even though great suggestions were made, none could fit my needs so I took out time to build something flexible that might help.
I've created a customizable file upload component that integrates seamlessly with shadcn/ui projects. It offers drag-and-drop functionality, multiple layout options, and more.
Key features include:

Drag and drop file upload
Vertical and horizontal layout modes
Single and multiple file upload modes
Customizable text and icons
File type and size limit options
Built with shadcn/ui for consistent styling

Feel free to check it out, use it, or contribute:
https://github.com/kwesinavilot/shadcn-file-upload
I hope this helps! Let me know if you have any questions or feedback. 😊

I created a simple version of the drop-zone component, published as shadcn-dropzone. ✨
yarn add shadcn-dropzone

Here is an example of how you would use it:
<Dropzone
  onDrop={(acceptedFiles: File) => {
    // Do something with the files
  }}
>
  {(dropzone: DropzoneState) => (
    <>
      {
        dropzone.isDragAccept ? (

Drop your files here!

        ) : (

              Upload files

        )
      }

        { dropzone.acceptedFiles.length } files uploaded so far.

    </>
  )}
</Dropzone>

Demo: https://diragb.github.io/shadcn-dropzone

isn't the point of using shadcn is NOT to install ui components in the node_modules?

I also encountered this same scenario, ever since I used shadcn I am addicted how elegant they implement components, so I wasted my time for it.
`"use client";
import * as React from "react";
import { cn } from "@/lib/utils";
import {
Accept,
DropzoneOptions,
DropzoneState,
ErrorCode,
useDropzone,
} from "react-dropzone";
import { Input } from "@/components/ui/input";
import { UploadIcon } from "lucide-react";
interface DropzoneConfig {
multiple?: boolean;
accept?: Accept;
maxFiles?: number;
minSize?: number;
maxSize?: number;
}
interface DropzoneContentValue extends DropzoneState {
config: DropzoneConfig;
}
const DropzoneContext = React.createContext<DropzoneContentValue | null>(null);
interface DropzoneProps extends DropzoneOptions {
children?: React.ReactNode;
}
const Dropzone: React.FC = ({ children, ...opts }) => {
const dropzone = useDropzone({ ...opts });
const { multiple, accept, maxFiles, maxSize, minSize } = opts;
return (
<DropzoneContext.Provider
value={{
...dropzone,
config: { multiple, accept, maxFiles, maxSize, minSize },
}}
>
{children}
</DropzoneContext.Provider>
);
};
Dropzone.displayName = "Dropzone";
function useDropzoneValue() {
const context = React.useContext(DropzoneContext);
if (!context) {
throw new Error("useDropzoneValue must be used within Dropzone");
}
return context;
}
const DropzoneContent = React.forwardRef<
HTMLDivElement,
React.HTMLAttributes

(({ className, children, ...props }, ref) => {
const { getRootProps, isDragAccept, isDragReject } = useDropzoneValue();
const rootProps = getRootProps({ ...props });

return (

{children}

);
});
DropzoneContent.displayName = "DropzoneContent";
const DropzoneTitle = React.forwardRef<
HTMLHeadingElement,
React.HTMLAttributes

(({ className, children, ...props }, ref) => {
return (
<h2
className={cn("text-xl font-semibold tracking-tight", className)}
ref={ref}
{...props}

  {children}

);
});
DropzoneTitle.displayName = "DropzoneTitle";
const DropzoneInput = React.forwardRef<
HTMLInputElement,
React.InputHTMLAttributes

(({ className, ...props }, ref) => {
const { getInputProps } = useDropzoneValue();
const inputProps = getInputProps({ ...props });

return <Input className={cn(className)} ref={ref} {...inputProps} />;
});
DropzoneInput.displayName = "DropzoneInput";
const DropzoneDescription = React.forwardRef<
HTMLParagraphElement,
React.HTMLAttributes

(({ className, children, ...props }, ref) => {
return (
<p
className={cn("text-sm text-muted-foreground", className)}
ref={ref}
{...props}

  {children}

);
});
DropzoneDescription.displayName = "DropzoneDescription";
function readableFileSize(bytes: number, decimals = 2) {
if (bytes === 0) return "0B";
const kilobyte = 1024;
const sizes = ["B", "KB", "MB", "GB", "TB", "PB", "EB", "ZB", "YB"];
const sizeIndex = Math.floor(Math.log(bytes) / Math.log(kilobyte));
return (
parseFloat(
(bytes / Math.pow(kilobyte, sizeIndex)).toLocaleString("en", {
maximumFractionDigits: decimals < 0 ? 0 : decimals,
}),
) + sizes[sizeIndex]
);
}
const DropzoneMessage = React.forwardRef<
HTMLParagraphElement,
React.HTMLAttributes

(({ className, children, ...props }, ref) => {
const { fileRejections, config } = useDropzoneValue();

const errors = React.useMemo(
() =>
fileRejections.flatMap((fileRejection) =>
fileRejection.errors.map((error) => {
switch (error.code) {
case ErrorCode.FileInvalidType:
if (!config.accept) {
return "";
}
          const accepts = Object.keys(config.accept).map((accept) =>
            accept.replace(/[^a-zA-Z ]/g, ""),
          );

          const fileExtension = fileRejection.file.name.split(".").pop();

          return `Accepts ${accepts.join(", ")} received ${fileExtension}.`;

        case ErrorCode.FileTooLarge:
          if (!config.maxSize) {
            return "";
          }

          const fileSizeLarge = readableFileSize(fileRejection.file.size);
          const maxSize = readableFileSize(config.maxSize);

          return `File is too large, weighing ${fileSizeLarge}. Max size is ${maxSize}.`;
        case ErrorCode.FileTooSmall:
          if (!config.minSize) {
            return "";
          }

          const fileSizeSmall = readableFileSize(fileRejection.file.size);
          const minSize = readableFileSize(config.minSize);

          return `File is too small, weighing ${fileSizeSmall}. Min size is ${minSize}.`;
        case ErrorCode.TooManyFiles:
          if (!config.maxFiles) {
            return "";
          }

          const { length: fileLength } = fileRejections;
          const { maxFiles } = config;

          return `Too many files, maximum files is ${maxFiles} recevies ${fileLength}.`;
        default:
          return "Something went wrong upon reading the file.";
      }
    }),
  ),
[fileRejections, config],

);
const body = errors.length ? String(errors[0]) : children;
if (!body) {
return null;
}
return (

{body}

);
});
DropzoneMessage.displayName = "DropzoneMessage";
export {
Dropzone,
DropzoneContent,
DropzoneTitle,
DropzoneInput,
DropzoneDescription,
DropzoneMessage,
};
`
It uses react-dropzone for implementation, and yeah, I know react-dropzone has their own component, but I wanted mine to follow shadcn compounding the components.


fixed CupertinoNavigationBar leading issue

Description
Fixed CupertinoNavigationBar leading issue
Related Issues
#18536
Tests
I added the following tests:
Leading positon of the text in CupertinoNavigationBar should be centered vertically
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

Hello @parkwonhui
Are you working on it?
Thanks


fuzzycollect internal error lalloc

Steps to reproduce

vim -Nu NONE
set completeopt=menuone,popup,fuzzy,fuzzycollect,noselect completepopup=highlight:Pmenu
hi PmenuMatch guifg=#ffaf5f guibg=#3a3a3a gui=NONE cterm=NONE
hi PmenuMatchSel guifg=#af5f00 guibg=#afaf87 gui=NONE cterm=NONE
:h fuzzy
switch to previous window
type omp and c-p c-p

Expected behaviour
There should be no errors.

Version of Vim
9.1.505
Environment
debian 12, bash
Logs and stack traces
No response

@glepnir fyi

can be close because fuzzycollect is removed


Windows support

Hello! Awesome library (or framework, idk) and thanks for your hard work!
What's the status of windows implementation?

Thank you for your interest in my repository.
The schedule for Windows support has not yet been determined, but it is low priority and will be a few years later. If there is a clear and specific demand, the support schedule may be accelerated.
The technical implementation method for Windows support has been studied and will be about 3 months for 200 commits.

Does it already support Windows?


Update chef-client in one more location.

Description
We missed one reference to chef-client during our last update of the chef-client version. Fix that, and add document with checklist of places to fix to help prevent future oopsies.
Issues Resolved
Closes #1622 (this and prior merges supersede those changes)
Check List

[x] New functionality includes tests
[x] All tests pass
[x] Full CI Run passes
[x] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Signed-off-by: Mark Anderson<EMAIL_ADDRESS>

Closes #1594


Change multipathServiceType to none

I tried out this SDK for the first time today but spent hours trying to determine why I wasn't getting a response. Drilling down I came across configuration.multipathServiceType = .handover. I was curious what that is since I have not used it before and reading the docs I saw that it Requires the com.apple.developer.networking.multipath entitlement.
Using these service types requires the appropriate entitlement.  Any connection attempt will fail if the process does not have the required entitlement.
This explained all of my problems and confirmed as such with the change of this PR.
My suggestion, given this SDK will likely be most used by developers working on hobby projects, is to switch this to .none so that the entitlement is not required. However, if this setting is a hard requirement for the SDK I can change this PR to instead emphasize the need for the entitlement in the README.

Thanks for spotting this @chickdan. Haven't come across this issue myself.

I am hoping this is a fix for #125. thank you @chickdan !


feat: also check content-type with @sgtpooki/file-type

This PR adds an additional check for content-type via a fork of the file-type library, similar to how it's used in helia-http-gateway.
I forked https://github.com/sindresorhus/file-type because it doesn't currently support browsers due to direct or dependency consumption of node:stream, node:buffer, node:fs, or node:process.
The fork could still use some updates to support streams and confirm that memory usage is reasonable, but it's a start and confirmed working in helia-service-worker-gateway.
Using this fork, we would be able to remove the file-type dependency from helia-http-gateway and de-dupe the content-type checking code.
Related issues in the original repo:

https://github.com/sindresorhus/file-type/issues/578
https://github.com/sindresorhus/file-type/issues/617

file-type really looks like it needs a new module that strips out all the old node stuff.
How much does the fork add to the bundle size?

how much do these add to the bundle size?

You can find this out with npm run build -- -b in packages/verified-fetch
Somewhat eye-opening:

Do we really need to be able to detect all of these mime types?

removing mime-type reduces bundle size by 147kb (707.2kb to 560.2kb)

Closing this in favor of #422


Milestones toward generalized representation of timeouts

PR #17155 proposed a proof-of-concept for an opaque timeout representation that would allow the flexibility required by #19282. Over time the changes grew to include:

A complete family of functions to convert between time-based, tick-based, and cycle-based durations including control of rounding (now separately submitted in #19591);
A representation of timeout values as an opaque struct that encoded timeout features;
New API like K_TIMEOUT_MS(x) to replace K_MSEC(x) by storing the count in system ticks rather than milliseconds.
Conversion of existing code to the new API.

Although the initial steps were promising the PR grew to include a conversion of the entire Zephyr tree to support the new API, and making the new API the default.  This exposed the following problems:

The PR became unreviewable as it modified almost 600 files.
It revealed many cases where kernel (threads), driver, and subsystem code stored delay values in other structures, used them as values in expressions, and passed them through internal functions.
Global changes to the API were made without giving codeowners an opportunity to consider how new capabilities should be used (i.e. where the transition between integral durations and timeouts should be done)
The new representation of timeouts as a count of ticks required duration calculations that had been done at compile-time to be performed at runtime as the time-to-ticks conversion depends on sys_clock_hw_cycles_per_sec() which may not be a compile-time constant.  This impacts use of K_THREAD_DEFINE() which requires a compile-time delay while k_thread_create() can accept a runtime-specified delay.

This issue is intended to address the request for more details on what would make the changes in PR #17155 acceptable.  It does that by breaking the task down into discrete, focused stages (i.e. Pull Requests) that can be reviewed and merged without building up massive changes (with one exception that's unavoidable):

[x] Unify the existing kernel APIs
[ ] Replace the integer timeout representation with an opaque structure
[ ] Transition to representing relative timeouts as unsigned values
[ ] Support using 64-bit timeouts
[ ] Support for high resolution timeouts

It does not extend to cover all features of #17155, which may be revisited after the initial stages of supporting a flexible representation have been completed.
Unify the existing kernel APIs
Ensure that all places where literal integers are passed to kernel API that will in the future take a k_timeout_t are converted to use the timeout macros K_NO_WAIT, K_FOREVER, and K_MSEC(x).
This is currently being done using Coccinelle, with #19650 being the most recent step.
Replace the integer timeout representation with an opaque structure
We need a one-time global change for public API involving timeouts to convert from s32_t to the opaque k_timeout_t type.  This change will likely affect hundreds of files.  To keep it reviewable and trusted it must not include any behavioral changes beyond the structural type change.
To accomplish this the PR should change all kernel API where a timeout is represented as an s32_t to instead be represented by:
typedef struct k_timeout_t {
    s32_t ms;
} k_timeout_t;

It should change the generating macros something like this:
#define K_NO_WAIT_VALUE 0
#define K_FOREVER_VALUE -1
#define K_NO_WAIT ((k_timeout_t){.ms = K_NO_WAIT_VALUE})
#define K_FOREVER ((k_timeout_t){.ms = K_FOREVER_VALUE})
#define K_MSEC(x) ((k_timeout_t){.ms = x})

It should add functionality something like this:
#define K_TIMEOUT_GET_VALUE(t) (t).ms
#define K_TIMEOUT_IS_NO_WAIT(t) (K_TIMEOUT_GET_VALUE(t) == K_NO_WAIT_VALUE)
#define K_TIMEOUT_IS_FOREVER(t) (K_TIMEOUT_GET_VALUE(t) == K_FOREVER_VALUE)

Any use of timeout values that requires knowing the duration value or comparing the duration to the marked K_NO_WAIT or K_FOREVER should convert to the new helper macros.
The purpose of this is to identify, by the resulting compilation errors, all places where code converts between an integer representation and a k_timeout_t representation, and determine which representation is appropriate for each case.  There are likely to be many of them.
It would be possible to use Coccinelle to convert existing uses, but ideally this step should involve the maintainers of code that must be changed, to determine at what point the integral duration should be converted to a timeout.
Transition to representing timeouts as unsigned values
Zephyr does not currently support a relative timeout that is in the past: all such timeouts are treated as equivalent to K_NO_WAIT.  The use of signed values for delays cuts the maximum representable delay in half.  It also impacts expression evaluation as any overflow will invoke undefined behavior.
Replace the k_timeout_t structure with:
#define K_FOREVER_VALUE (u32_t)-1
typedef struct k_timeout_t {
  u32_t ms;
} k_timeout_t;

Identify places where this causes a behavioral change and rework the logic to be correct.
Support using 64-bit timeouts
Add a Kconfig option such as CONFIG_SYS_TIMEOUT_64BIT that would change k_timeout_t to:
#ifdef CONFIG_SYS_TIMEOUT_64BIT
typedef u64_t k_timeout_value_t;
#else
typedef u32_t k_timeout_value_t;
#endif
#define K_FOREVER_VALUE (k_timeout_value_t)-1
typedef struct k_timeout_t {
  k_timeout_value_t value;
} k_timeout_t;

#define K_TIMEOUT_GET_VALUE(t) (t).value

Support for high resolution timeouts
At this point, with 64-bit timeout support, we can move to using higher resolution (sub-millisecond) timeout values as proposed in #19656.
Support for additional enhancements
Other desires described in #19282 can be designed and implemented after we've reached the stages described above.

@andyross please review.  I'd like to work with you towards our goal.

@nashif @andyross I think this is a great description of a suggested sequence of discrete steps to achieve the goal of moving to the opaque structures and 64-bit timeout support.

cleaning out old cruft, the relevant treaty was signed long ago and peace has reigned since


How to prevent unknown options

Ideally, I'd like any command line option that is not listed on the usage screen to generate an error.  I don't see any kind of preventUnknownOptions() type API after browsing.
Is there a way I could do this today?  I imagine there might be some way to look through the options and find the ones of UnknownType, but I don't know how I could do that in a way that would apply globally to all my commands and subcommands.
(As an aside, and a nice-to-have: if this doesn't exist and it's added in the future, it might also be nice to have configurable control over the behavior if the error is triggered, so that I could hook into it and do a git-style "Unknown option --nmae, did you mean --name?" error message.)

@elliot-nelson Thanks for the suggestion!
Sywac doesn't currently have an "easy" way to do this, but I'm beginning to think we should add something to the api. (You're not the first person to ask for this functionality.)
To workaround, you can define a custom check handler that sniffs out any unknown args and short-circuits when they're found. See #17, especially my comment here.

Released PR #51 as v1.3.0 on npm.
We haven't yet addressed the nice-to-have feature you mentioned in the issue description, but we at least now have .strict() mode available.
Give it a spin and let me know what you think. Thanks for all your help so far!


Add ignore keyword to FeatureSelector Transformer

This PR

Adds ignore keyword to FeatureSelector Transformer similar to ignore keyword used in Standardizer.
allow features keyword to accept a function similar to features keyword used in Standardizer

might want to add NaiveBayes test back before merging

Looks great. Any chance of adding a test?

@OkonSamuel Assuming this passes CI, you ready for merge?

@OkonSamuel Assuming this passes CI, you ready for merge?

Yeah