iOS - allowEditing: true, trimming video not working

When choosing a video from the cameraroll, on the very top there is a section where I am supposed to trim a video. I trim it down in length, then select choose at the bottom - right, it says trimming video, and after that the video still appears as full length.
Any ideas?

React Native version: 0.43.3
Platform: iOS
Development Operating System: MacOs
Dev tools: Xcode

hello, did you find a solution for this?

This is still an issue. Confirmed with the latest version of this library on iOS 13. @Johan-dutoit


let(:node) not able to override $fqdn setting

This showed up for me when

using both rspec-puppet (v2.5.0) and rspec-puppet-facts (v1.7.1)
using let(:node) to specify a node name
some class in the catalogue being tested references the $::fqdn fact

I believe the issue is that line 146 of support.rb contains this:
facts_val.merge!(munge_facts(facts)) if self.respond_to?(:facts)
which means that if fqdn is already defined in the existing :facts hash, we're not going to be able to override it, and we get fqdn as foo.example.com, as defined by rspec-puppet-facts.
Am I missing something?

See PR#510, but I don't know what the intended behavior is, here, so not sure I got it right.

Resolved in #513


Focus change after enter press in form field (IE only)

I tested this behavior in latest Firefox (41.0.2) and Chrome (46.0.2490.80 m) and Internet Explorer 10.0.9200.17159
Used versions of the framework: SAPUI5 1.30.6 and OpenUI5 1.32.4
It can only be reproduced in IE. The other tested browsers don't show this behavior.
Please have a look at this example on jsbin
When the enter key is pressed while the cursor is in the input field of the detail view the focus caret will move to the button located at the bottom of the master view.
In my particular application this is really annyoing because the button is the logout button!

Thanks for reporting. I could reproduce this issue as described in IE10. I will forward to the responsible developer to have a look.
Internal reference:<PHONE_NUMBER>

The same happens in IE10 with the following plain HTML page:
<!DOCTYPE html><html><body><input><button>Button</button></html>
Apparently, IE10 handles inputs and buttons as being inside of a <form> element.
As it is already corrected in IE11, we take no further action.


Doesn't run on Apple Silicon

Hello, thanks for your amazing work. I'm struggling to get it to run on a M1 Mac environment - Running it on python 3.9 or 3.10 results in errors due to missing Mac modules - those seem to be all available on python 3.8 but then the code does not compile due to syntax errors:
(myCondaEnvironment) rafal@MacBook-M1 cbp_translate % python3.8 cbp_translate/cli.py --path-in ./assets/videos/keanu-reeves-interview.mp4 --path-out ./translated.mp4 --language PL

Traceback (most recent call last):
  File "cbp_translate/cli.py", line 4, in <module>
    from cbp_translate.pipeline import Config, run
  File "/Users/rafal/Crackground/cbp-translate/cbp_translate/pipeline.py", line 10, in <module>
    from cbp_translate.components.alignment import (
  File "/Users/rafal/Crackground/cbp-translate/cbp_translate/components/alignment.py", line 8, in <module>
    from cbp_translate.components.faces import FaceLocation, OnFrameRecognized
  File "/Users/rafal/Crackground/cbp-translate/cbp_translate/components/faces.py", line 13, in <module>
    from cbp_translate.components.loaders import frame_iterator, get_video_metadata
  File "/Users/rafal/Crackground/cbp-translate/cbp_translate/components/loaders.py", line 20, in <module>
    def get_video_metadata(path: str) -> tuple[int, int, tuple[int, int]]:
TypeError: 'type' object is not subscriptable

Any ideas are welcome :-)

Hi @fastmot1on , apologies for the issue! I don't have an M1 macbook available at the moment, but I'll see what I can do over the weekend


[Bugfix] Use correct length in beam search scoring

When argument seq_len to get_beam_search_score is None, the function ends up returning the wrong score for the beam. This was noted in https://github.com/vllm-project/vllm/issues/2606 and occurs because the the seq_len defaults to the length of the output and input (or prompt) tokens, when it should default to just the output tokens. The effect on the ranking of beams will be especially large when # of prompt tokens >> # of generated tokens. The fix is simply to swap get_len() --> get_output_len().
I was burned by this when I noticed the outputs from a HF model, with length_penalty=1.1 did not match the outputs when the same model was served with vLLM. I then noticed that length_penalty had almost no effect on the ranking of beams. This led me to https://github.com/vllm-project/vllm/issues/2606, so full credit to @physicsrob for first identifying the issue.
CC'ing my colleague @TheCodeWrangler who co-discovered this bug with me.
FIX https://github.com/vllm-project/vllm/issues/2606
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

I added a test to test_beam_search.py, let me know if it makes sense to place it in another location (maybe test_sequence.py?).
Also, I've realized that get_beam_search_score will run into a divide by 0 error in the case where get_output_len() is 0. I am not sure what the behavior of get_beam_search_score should be in this case. Detect when self.get_output_len() is 0 and return float('-inf')?

I added a test to test_beam_search.py, let me know if it makes sense to place it in another location (maybe test_sequence.py?).
Also, I've realized that get_beam_search_score will run into a divide by 0 error in the case where get_output_len() is 0. I am not sure what the behavior of get_beam_search_score should be in this case. Detect when self.get_output_len() is 0 and return float('-inf') maybe?

I think we will never evaluate a sequence with output length 0 so this should not be an issue?

I added a test to test_beam_search.py, let me know if it makes sense to place it in another location (maybe test_sequence.py?).
Also, I've realized that get_beam_search_score will run into a divide by 0 error in the case where get_output_len() is 0. I am not sure what the behavior of get_beam_search_score should be in this case. Detect when self.get_output_len() is 0 and return float('-inf') maybe?

I think we will never evaluate a sequence with output length 0 so this should not be an issue?

Hmm, an output length of 0 appears to happen in one of the failing tests though: https://buildkite.com/vllm/fastcheck/builds/1483#01910e64-aeec-49a0-8c5c-cd60e90318f4/193-495

Pinging @zhuohan123 @rkooo567. What is the desired behavior when self.get_output_len() == 0?


darlington day 37 and JSON solution submission

Apart from json.loads and json.dumps what else can we do with json

Do check this out More on Json


New Methods

Can you please update to include the latest methods or instruct me on how to do that?

I added the code for the REST client generator which I used to automatically generate the C# API methods & models.
An alternative would be that you manually add the methods & models for the new API operations here
Feel free to submit a pull request, I'm currently not able to provide an update.


Another "Error: Null check operator used on a null value" case

This error appears just same as #208. But the solution in that post didn't work for me. Here is my environment info, thx for the help.

Computer And OS: Mac Sonoma 14.2
Dart version: Dart SDK version: 3.3.0-27.0.dev
Prisma info:

Schema

Error Message

same

Here is another try, I defined two client, one for dart, and one for JS
just like this
generator clientDart {
  provider = "dart run orm"
  output = "./dart/client"
}
generator clientJS {
  // provider = "dart run orm"
  provider = "prisma-client-js"
  output = "./js/client"
}

the JS client generated successfully.

Here is another try, I defined two clients, one for dart, and one for JS just like this
generator clientDart {
  provider = "dart run orm"
  output = "./dart/client"
}
generator clientJS {
  // provider = "dart run orm"
  provider = "prisma-client-js"
  output = "./js/client"
}

the JS client generated successfully.

but dart client not generate.
In the example, I also don't see the dart folder being generated: https://github1s.com/medz/prisma-dart/blob/HEAD/prisma/schema.prisma

After downgrade Prisma and Prisma Client to version 4.16.2

the dart client and generated.

I tried a few history versions of prisma, and client, with my same code and environment, this issue can be reproduce start from 5.0.0.

Please fix the version to 4.x, I am developing a new client that is compatible with 5.x because Prisma 5.x has changed the protocol,

thx, I am using version 4.16.2.
fyi @ducphan1311

v3.4.5 version published, fixed the bug.

And v4.0.0-alpha.0 version published


Update FocusScope.mdx

Closes
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

I'm going to close this, FocusScope is imported in an example above, and in the usage section. We typically don't import the main component of the documentation page multiple times across any of our pages.


How import angular-ui-router.d.ts of latest version

My team have used typescript and we have used typings that declared tsd.json. Recently, we upgraded version of ui-router to 1.0.0-beta.1 but i cant find angular-ui-router.d.ts of this version in DefinitelyTyped
How import d.ts file in my project ?
I want to use the pattern like "private $transitions:TransitionService" in my local project.

We now publish the type definitions with every release, instead of separate publish to DefinitelyTyped.  This is the preferred method of publishing projects written in typescript (like Angular 2 project).
If you use npm to fetch angular-ui-router, and use "module_resolution": "node" in your tsconfig.js, then your IDE should use the typings files automatically.
https://www.typescriptlang.org/docs/handbook/module-resolution.html#how-typescript-resolves-modules
We use "typings": "commonjs/ng1.d.ts" in our package.json to let your typescript compiler know where to find the typing information.
In your typescript you then just use import {TransitionService} from "angular-ui-router";

the option 'moduleResolution' is awesome...
I resolve the problem
Thanks! @christopherthielen

Sorry, but what about when not using modules?
I have a project that still uses ambient declarations. Is there a .d.ts bundle somewhere or should I build it myself?

@nvivo there is not a .d.ts bundle.  I'm not even sure how to go about using the types in an ambient context.
All the types are currently exported from the .d.ts file in node_modules/angular-ui-router/commonjs/ng1.d.ts.  Everything I've read from the TypeScript folks is that this is the correct way to publish a TypeScript project.  I don't know how to enable your need for ambient declarations.  If it's possible, feel free to submit a PR.  I'll merge it if it doesn't break other users.

@nvivo I've managed to 'bundle' the code through the usage of typings install npm:angular-ui-router --save.
This will basically look into the node_modules/angular-ui-router/package.json, find the file specified in the typings attribute and somehow compiles it together. The output will be available in typings/modules/angular-ui-router/index.d.ts.
The problem is that the typings definition was built as a module (that's why it is in typings/modules/...) and not the ambient (a.k.a 'global') declaration. I tried to bundle it as a 'global' declaration using --global option like this: typings install npm:angular-ui-router --save --global, but I'm getting following error:
typings ERR! message Attempted to compile "angular-ui-router" as a global module, but it looks like an external module. You'll need to remove the global option to continue.

Maybe it's just a lack of my TS knowledge and I do not know what exactly I need to type in to get the correct suggestions. But it might be the case when there's actually something missing in the definitions.


Take cargo features into account through USE flags.

Almost fix #12
The main drawback, crate fetching : you still fetch all crates, even those depending on a feature you don't want (said otherwise, the CRATES variable of the ebuild is always the same). That being said, I don't know if we can do anything better, since crate dependencies are hardcoded in the ebuild when using the cargo eclass.
All use flags matching features in the default feature are activated by default (marked +)

Due to the changes in the cargo_metadata, this commit no longer works.
@cardoe, if you are interested, I can try to find a new way to fix #12 with the newer version of cargo_metada, but at first glance, it seems that it will be harder...


BUG: cmd and args are not parsed correctly

The bug appears during the execution of the hello world test from   _https://github.com/landerlini/vk-test-set/blob/main/vktestset/templates/000-hello-world.yaml_  .
It seems that args are not parsed correctly, in details, the test is requesting
command: ["/bin/bash", "-c"]  args: ["echo hello world"]
but the hello world is not printed, meaning that the arguments are not parsed correctly.
A possible solution to solve this problem would be to create a bash file with the contents of the command and the args and then send this bash file to the container.  So the content of the bash file for this example would be something like
#!/bin/bash

/bin/bash -c 'echo hello world'

Addressed in release 0.2.6
Closing for now, but it should probably be reviewed to check if it is properly done


Anchor Build not Working 0.21.0

Trying to run anchor build
But I get
Failed to obtain package metadata: 'cargo metadata' exited with an error:     Updating crates.io index error: failed to select a version for the requirement 'anchor-lang = "^0.21.0"' candidate versions found which didn't match: 0.24.2 location searched: crates.io index required by package 'programs v0.1.0 (/home/nomadicspark/Code/profile-solana/programs/programs/programs)'
anchor-cli 0.21.0
avm 0.24.2
cargo 1.61.0
rustc 1.61.0
solana-cli 1.10.27

Older versions of anchor crates are yanked from crates.io. If you need to use an older version than the latest semver, you can use git dependencies and target a certain repository tag or ref.

Can you provide the terminal commands I would use to accomplish that?

I made the change, but still having issues.
Failed to obtain package metadata: cargo metadataexited with an error:     Updating git repositoryhttps://github.com/coral-xyz/anchor`
error: failed to get anchor-lang as a dependency of package programs v0.1.0 (/home/nomadicspark/Code/profile-solana/programs/programs/programs)
Caused by:
failed to load source for dependency anchor-lang
Caused by:
Unable to update https://github.com/coral-xyz/anchor?tag=0.21.0
Caused by:
failed to find tag 0.21.0
Caused by:
reference 'refs/remotes/origin/tags/0.21.0' not found; class=Reference (4); code=NotFound (-3)`

Yes, thank you very much @callensm

I want to add that I also had to do
wget http://nz2.archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1l-1ubuntu1_amd64.deb sudo dpkg -i libssl1.1_1.1.1l-1ubuntu1_amd64.deb
because I still had issues with another error. Just adding this here in case anyone else gets a similar error
error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

wget http://nz2.archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2.16_amd64.deb
sudo dpkg -i libssl1.1_1.1.1f-1ubuntu2.16_amd64.deb

https://solana.stackexchange.com/questions/3029/anchor-test-error-while-loading-shared-libraries-libssl-so-1-1


[WFCORE-4867] Highlight the config name in start message

Issue: https://issues.redhat.com/browse/WFCORE-4867

Ok, thank you very much. :) I will look at it and create a new PR.


Guideline on Licensing

The following guideline is structured as follows:

Intro to open licensing and. why licenses are important.
Open-source licenses
Open access licenses

Creative Commons (CC) licenses

Most of the information were taken directly from the Review of Practices.

Suggest adding the following attribution to the review:
This material is derived from the [CCG review of good enough practices][1] which is released under a [CC-BY 4.0 license][2].

[1]: https://doi.org/10.5281/zenodo.5911546 "Usher, William, Beltramo, Agnese, Gardumi, Francesco, Martin, Viktoria, & Petrarulo, Luca. (2022). CCG Platform - Body of Knowledge: Review of Good Practice (1.3). Zenodo. https://doi.org/10.5281/zenodo.5911546"

[2]: https://creativecommons.org/licenses/by/4.0/legalcode


new feathering of surface model block diagonal prior covariances

Per Michael Turmon's method.  The associated surface model configuration file would have JSON definitions like:
 {
    "input_spectrum_files":
      [
        "filtered_veg"
      ],
    "n_components": 1,
    "windows": [
      {"interval":[300,350], "regularizer":10, "correlation":"decorrelated"},
      {"interval":[350,480], "regularizer":1e-4, "correlation":"EM", "name": "aerosol", "feather_forward":-2000},
      {"interval":[480,740], "regularizer":1e-4, "correlation":"decorrelated"},
      {"interval":[740,1250], "regularizer":1e-6, "correlation":"EM", "name": "shallow-water"},
      {"interval":[1250,1325], "regularizer":1e-8, "correlation":"EM", "name": "osf"},
      {"interval":[1325,1960], "regularizer":10, "correlation": "decorrelated"},
      {"interval":[1960,2070], "regularizer":1e-4, "correlation":"EM","name": "co2","feather_forward":-500 },
      {"interval":[2070,2470], "regularizer":1e-5, "correlation":"decorrelated"},
      {"interval":[2470,2500], "regularizer":1e-4, "correlation":"EM","isolated": 1, "name": "noise" }
    ]
  }

This works well on EMIT data where discontinuities were previously seen.

The preferred surface configuration is in
surface/surface_20240103.json

Looks awesome, thanks!


Bug: SPFx v1.13.0-beta.13 doesn't upgrade devDevependencies

While I'm at it: is it expected that devDependencies don't upgrade?

Originally posted by @PathToSharePoint in https://github.com/pnp/cli-microsoft365/issues/2610#issuecomment-886244839

@PathToSharePoint when I upgrade an SPFx v1.12.1 project to SPFx v1.13.0-beta.13, I'm getting suggestions to upgrade devDependencies as expected. Could you please provide us with more information so that we can reproduce what you're seeing?

I am getting them too. I re-ran the command on my 1.12.1 project and here is what happened:

Good catch! Local workbench has been deprecated in v1.13.0 which is why it fails during the installation. Will adjust!


Side menu ionOpen not triggered. It was working in beta.11

Bug Report
Ionic Info
Using it via CDN 4.0.0-beta.13
https://unpkg.com/<EMAIL_ADDRESS>
Describe the Bug
ionOpen event is not emitting.
Related Code
<ion-split-pane :when="expandWhen">
   <ion-menu type="reveal" @ionOpen="menuOpenHandle" @ionClose="menuCloseHandle">
</ion-menu>
</ion-split-pane>

Expected Behavior
menuOpenHandle function is not getting called. It should be called. It was working in beta.11

Hi @mhartington, Could you please check this out.

Thanks, @mhartington.


Fix default ov config

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Create UserAccount class

Create the UserAccount class and all the required methods as well as tests for all those methods

completed and merged


Subrouter per page

Awesome little bootstrap for a MVC project. I was wondering, wouldn't it be a bit nicer to have subrouters per /{page}/? So each controller gets a prefixed router?

you mean here https://github.com/ddo/go-mux-mvc/blob/master/controllers/controllers.go ?

Yes. There you define per route the exact method. Shouldn't it be 'prettier' to assign the /products to the ProductController via a prefix? And then define all the routes? Or is this an ugly idea?

yeah most of the other mvc frameworks supports like that i guess. but i think the currently way is more flexible

One downside: controllers.go now has an understanding of the routes of the other subcontrollers. I see the collection of routes with a prefix /products/ to be part of a products service.
To keep my project clean, I want all innercode to stay inside that service. Which means to keep all the route definitions in that specific controller folder.

good idea i just recently switch to chi since mux is lack of middleware. gonna push some changes to the template later then


Change npm install to npm ci for semantic/model validation

Npm install needs to be changed into npm ci as semantic/model validation relies on OAV and npm install might cause OAV to automatically download new yasway packages.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go


rewrite graph selection

resolves #4729

Description

Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change

Should I also remove the original tests in this PR? @gshank

Yes. Please remove the original test directory.


TST: Run each test in separate process

This works around the thread safety issues in upstream https://github.com/dmlc/xgboost/issues/2796

This makes local debugging annoying since you have to modify the setup.cfg to remove --boxed to use --pdb, but at least it passes.


"Beep" Sound and a nice card

Τhe dehumidifier itself makes a sound every time you press on buttons as a confirmation so I think it would make sense to also have it make the sound when you control if via HA. So you know when you change an option from HA that it actually happened
Also it would be nice if we can control the humidifier from a card that has all the control in it, toogle on/off, modes, fan speeds... all in one place.

Beep sound is hopefully coming in 0.5.0.

@PskNorz v0.5.0 is out, can you test if beep sound works (it is controlled by a switch which is disabled by default)

@PskNorz v0.5.0 is out, can you test if beep sound works (it is controlled by a switch which is disabled by default)

Perfect! If hymidifier goes unavaible and turn again avaible it will go off?

Probably, I have not tested, and I don't really have an option to check it simply in the code without some refactoring.

Ok then, what about the card idea?

I think that one will have either to wait someone else, or some other time, don't think I'll have time soon to look into that.

Nice much better support than the others, i did not know it could also report temperature.
About the Lovelace card :
Im currently in the process of modifying the default humidifier card to add support for all the options,
i've added the mode control with icons (Set, dry, smart, continuons)
it display the current humidity and i plan on adding support for controlling the fan, a tank full indicator, filter indicator....
I'll post a few screenshots if anyone is interested.

Nice much better support than the others, i did not know it could also report temperature.
About the Lovelace card : Im currently in the process of modifying the default humidifier card to add support for all the options, i've added the mode control with icons (Set, dry, smart, continuons) it display the current humidity and i plan on adding support for controlling the fan, a tank full indicator, filter indicator.... I'll post a few screenshots if anyone is interested.

Nice, i would be nice to control the humidifier from one place. I will wait for your card 😎

Update on the card, what's working so far and how does it looks :

All mode, fan mode + humidity settings + sensor values displayed (humidity and temperature)
TODO:

tank full icon/feedback
change air filter icon/feedback
defrosting icon/feedback

If you have any idea of something i may have missed feel free to tell me :)

This is what I am looking sooooo long it’s what I want!
can add power on/off option?

Done :

Waiting to share it 😎

I'll try releasing it in the next few days.

Just to share my lovelace card: https://github.com/MiguelCosta/Dehumidifier_Comfee_Card

I'm fixing the last bug i have then i'll release it, btw MiguelCosta your card is georgous, i'm not sure mine is gonne be used after seeing this but i'll release it anyway as soon as i've fixed that damn bug

Done :

Hi sicknesz, thanks for your work!! And thanks nbogojevic for this great integration!
Here below some possible improvements for the card:

Since you added the power button (nice idea!), maybe the "Set" mode (first switch on the top left) is not needed anymore. Indeed, in the official app there are toggles only for "Smart", "Continuous" and "Dry" modes.
The "Smart" mode icon could be something related to mdi: "idea" or "lightbulb", e.g., "mdi:head-lightbulb-outline"
The "Continous" mode icon could be related to mdi: "repeat" or "update" or "renew", e.g., "mdi:autorenew"
In the HA standard thermostat card, the actual temperature is shown big, and the target one is below it and smaller, I see that in your card the actual humidity is shown small and the target is shown bit. Maybe having them swapped would be more consistent in a lovelace dashboard.

Hello gsportelli,
i originally had the current and target swapped like the thermostat card but it felt a bit weird not to have the big value change when dragging the slider around, so i added an options to swap them so everyone can choose how the card will display stuff so

it is kinda needed cause unselecting all mode won't cause the applicance to fallback to "set" as the physical buttons  does
Totally agree with this, updated in the next commit
I've already changed the continuous to AutoRenew but havent posted the lastest screenshot yet
now swappable using a yaml option : swap_target_and_current_humidity: true

Lastly, i've fixed the NaN NaN rendering bug, i still have on some occasion when the appliance is off it misses the power status and fan mode on the first render but it's fixed as soon as any state change is trigger, not breaking anything.
I still have to test the installations instructions, and what will happens if one does not provide all the entities needed by the card, I'll do my best to release it before monday when i should get back to my daily job.
Latest screenshots :
Swapped current and target :

Thought I would share my card in case it's any inspiration for others. Modes on my Midea are 'set' (default), 'smart', 'continuous', 'boost' (fan high). Graphs are from mini-graph-card. Makes use of input_select and switch templates and a couple automations.

Just to share my lovelace card: https://github.com/MiguelCosta/Dehumidifier_Comfee_Card

Thanks for sharing this! I'd like to give it a try. I hate to ask but what do I do with the card code? I added all of the HACS entries but not sure where to paste your code. I am still using the default "here is everything" Overview card so haven't jumped into the Lovelace customization yet.

Hello guys, sorry for being late, here is the first release of the card : Midea humidifier card
Normally it should auto-configure itself properly when first added to lovelace but in case if fails the card editor is working properly and you should be able to configure it using the UI, if everything fails the yaml sample code and options are all explained in the repo's README.
I had not much time to test it lately but all fonctionnality has been tested and working on my Home assistant, i hope you don't encounter troubles using it.


Duplicate entries in train_names_all_lggx3.txt

Is there a reason why the LGG dataset have multiple entries in train_names_all_lggx3.txt.

This is because the number of LGG images is much smaller than that of HGG images.

Do I need to change the directory paths in the Job_test file to test the code with the dataset, even if i dont have a GPU?

A GPU is required for training. Otherwise the training process would be very slow.


Streamingcommunity server

Description
When i play any film on server streaming community, there is an error streaming community 403
I test the site on a normal browser and work correctly
Provider
StreamingCommunity
Reproduction steps
When i play any film on server streaming community, there is an error streaming community 403
I test the site on a normal browser and work correctly
Operating system
AndroidTV
Logs
No response
Please confirm the following

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] If related to a provider, I have checked the site and it works, but not the app.

any fix for streamingcommunity ?
does not work with any device
tablet, firestick
with o without von

@besidesa did a change on it on the new version 1.7.9, can you check it

it

still not working
vixcloud error 403

@besidesa did a change on it on the new version 1.7.9, can you check it

not working


Timer doesn't die when use is in a different channel

Need to resolve issues across channels or similar.
At this stage implement timer dying every time calendar can't be found in "thisChannel"?

whenever a command is used (or anything prefaced with !) in a different channel, looks for timer in that channel and enters error loop, ignoring previous channel.


Implement Context::set_deadline() and Actor::deadline_passed() callback

This is a result of an experimentation triggered by #52, and relates itself to #14.
Direction-wise this is an alternative to #52, but this PR does not implement a full-fledged timer, merely a building block on top of which one can be made. Simplified timer is presented as an example.
The main differentiating point is a focus on minimal additions to the core actor crate by allowing downstreams to implement their own in form of an Actor (though we can ship some ourselves). The design should allow implementing timers without any permanent "ticks", with resolution of thread::park_timeout() used by crossbeam-channel and ability to be interrupted by an incoming message.
From the API user PoV, the difference is that with this approach, the user has the burden of carrying some Recipient<TimerActor> around, while in #52, tonari-actor itself has to stick TimerRef somewhere.
The first 2 commits are preparatory ones (first extracted from Brian's PR), Implement Context::set_deadline() and Actor::deadline_passed() callback is the main one.

@strohel thanks for your research on this! I'll try integrating this branch into tonari along with @skywhale 's code suggestion above. If it works well we can try fixing up the API a bit more to include a convenience wrapping actor, and/or a more ergonomic API on top of it all.

I think (A) makes the most sense, if we can change the semantics of deadline_passed a bit, so it's not reset by incoming messages. Otherwise, I think the building block is a little too tricky to use. I like the flexibility of the original set_deadline and deadline_passed, assuming the changed semantics. Not to mention TickingWrapper, users can easily implement various types of timing logic.
(A) not as accurate as TickingWrapper, but something as simple as this can implement approximate ticks.
fn deadline_passed() {
  context.set_deadline(INTERVAL);
  do_recurring_stuff();
}

(B) if do_recurring_stuff() is an expensive call that take a few milliseconds, this pattern may be more appropriate.
fn deadline_passed() {
  do_recurring_stuff();
  context.set_deadline(INTERVAL);
}

@bschwind, @skywhale, thank you for your feedback. It made me understand that setting (rather than querying) the deadline could indeed be a more ergonomic API, and that we can preserve the deadline even when a message is received.
I've force-pushed a new version that incorporates both ideas and is rebased on main. The first 3 commits are preparatory and partially revert the previous implementation, the fourth one is the actual functionality. So the overall PR diff shows the difference between the 2 implementations and usage in the timer example, and the "pure additions" can be seen by looking at the last commit in isolation.

As the next step, it's helpful to land #54 and provide an actor wrapper that implements a similar API to @bschwind's send_recurring_* functions. Assuming it's a popular use case of the actor system, we can put it in a feature-gated util mod instead of an example.

Is the assumption right now that we'll add in some built-in convenience actors (perhaps under a feature flag as @skywhale mentioned) in a separate followup PR?

Right, I count with opening a follow-up PR to extend and promote DelayActor, possibly after landing #54 as Ryo suggested.
I've pushed new commit that should address most review points above (thanks for them). I've resolved relevant conversations. (do you have a preferred convention who resolves/when to resolve them?)


Reinstall AMI: stable relion-2.0 , enhanced networking

Start up AMI that is already running with relion2.0
-remove relion2
-install stable relion2
-install ENA (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking-ena.html#enhanced-networking-ena-ubuntu)
-add software for picking programs

Done -
Name: EM-Packages-in-the-Cloud-4.0.2-GPU-ENA
AMI: ami-7e088b1e


Passing negative numbers as arguments?

Is there a way to pass negative number and make cli to not to parse it?
Right now it gives me:
./cli command -1
Incorrect Usage: flag provided but not defined: -1
Where command is just a command with arguments, which are extracted using context.Args().Get()

This appears to be because the underlying flag used for flag parsing has this behavior:
package main

import (
	"flag"
	"fmt"
)

func main() {
	flag.Parse()
	fmt.Println(flag.Args())
}

go run /tmp/tmp.go -1
flag provided but not defined: -1
Usage of /tmp/go-build523638755/command-line-arguments/_obj/exe/tmp:
exit status 2

Unfortunately that means it won't be an easy fix, but I'll mark this to be considered if the flag library is removed in lieu of custom flag parsing (which a few other issues would also require).
You can separate the argument with -- to indicate that all following arguments shouldn't be parsed as flags, like:
go run /tmp/tmp.go -- -1
[-1]

Thank you, workaround with -- is just fine


[Bug]: Next image width and height error

Description
When i forked and cloned the website it was not showing on my local server due to the width and height error

To Reproduce

I tried running the project on my localhost
I saw an error

Anything else?
No response
Code of Conduct

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

Can this issue be assigned to me @tobySolutions

Sure thing @ololade2002!


feat(new): Added Azure.LogAnalytics.Replication

PR Summary
Fixes #2893
Added Azure.LogAnalytics.Replication.
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] Change is not breaking
[x] This PR is ready to merge and is not Work in Progress
Rule changes

[x] Unit tests created/ updated
[x] Rule documentation created/ updated
[x] Link to a filed issue
[x] Change log has been updated with change under unreleased section

Other code changes

[ ] Unit tests created/ updated
[ ] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

Hi @BernieWhite,
Could you please share your thoughts on this? Initially, I believed that Azure.Monitor.Workspace.Replication was the appropriate approach. However, upon further consideration, I am wondering if it would be better to separate each “sub-service.” Given the extensive nature of the Azure Monitor portfolio and its potential for further growth, this might provide better scalability and organization.

Check the latest changes @BernieWhite. Should be all good to merge.


There was a window ordering error when embed_subwindows was enabled.

Tested versions
4.3 Until now
System information
Windows 10 x64
Issue description
When embed_subwindows is enabled, a window with always_on_top will cover all PopMenus above it
The error may occur in the sort calculation of Viewport::_sub_window_update_order().
By the way, I found that changing the subwindow visibility triggers subwindow sorting. This means that window sorting is repeated multiple times in one frame. We should consider caching the value of gui.sub_windows and compare it with the current value at the end of each frame to determine whether subwindow sorting is needed.
Steps to reproduce

Create default project
Add Window  node and  enable always_on_top
Add any node with popup menu (e.g. TextEdit) to window node
Run
Open the popup menu

Minimal reproduction project (MRP)
window_order_mrp.zip

Can't replicate this from the steps provided, please upload an MRP to make testing this easier
I can confirm this with gui_embed_subwindows disabled, but that's a known bug:

https://github.com/godotengine/godot/issues/62382

Can't replicate this from the steps provided, please upload an MRP to make testing this easier无法从提供的步骤中复制此内容，请上传 MRP 以简化测试过程
I can confirm this with gui_embed_subwindows disabled, but that's a known bug:我可以在__禁用 gui_embed_subwindows 的情况下确认这一点，但这是一个已知的错误：

always_on_top breaks non-embedded popups #62382

I have updated the MRP

So testing this the case happens when gui_embed_subwindows is false, none of the code in the MRP uses this因此，当 gui_embed_subwindows 为 false 时，就会发生这种情况，MRP 中的任何代码都不会使用此
So probably a duplicate of:所以可能是以下的重复：

always_on_top breaks non-embedded popups #62382

So please see that for more details, closing this as a duplicate, but if you think this is not a duplicate please comment here and this can be reopened因此，请参阅有关更多详细信息，请将其作为重复项关闭，但如果您认为这不是重复项，请在此处发表评论，并且可以重新打开

The value of gui_embed_subwindows   is not critical.
This is essentially whether the window is native.
When the window is native, the window sorting is actually done by the operating system, and godot just calls the operating system's API.  https://github.com/godotengine/godot/issues/62382 is that the system API is not called correctly.
When the window is non-native, the window sorting is done by godot itself, which is implemented in the viewport.
Issue https://github.com/godotengine/godot/issues/62382 discusses the problem of native windows, and this issue discusses the problem of non-native windows. Therefore, the fix pr for https://github.com/godotengine/godot/issues/62382 cannot fix the problem of this issue.
Although they have the same external performance, I prefer to use different issues. This allows the fixer to only care about one code problem.

Then you need to update the issue because you wrote "embed_subwindows"
Reopening but the description needs to be updated to make the issue clear


NWP Contiguous Time doesn't overlap with any of the other datasets

Describe the bug
When trying to train MetNet in https://github.com/openclimatefix/metnet/pull/42 I have been able to train with Satellite, HRV, and PV, but not NWP. I even changed the config to only load NWP and GSP data, but the datapipe still complains that there is no overlap between the datasets. This is despite that the GSP data covers 2014-2022, and the NWP 2020-2021, and is the same NWP data used for training PVNet, and Power Perceiver.
To Reproduce
Run the metnet_training datapipe with a config that loads NWP data. The default train script in https://github.com/openclimatefix/metnet/pull/42 works on Donatello.
Expected behavior
There is an overlap and it should start returning examples
Additional context
Add any other context about the problem here.

Fixed the error, sample time has to be 3 hours, as init times are 3 hours apart


Support for creating Sections

This PR introduces the ability to split components into sections. Sections are configured in the styleguide.config.js file as a peer to the main components property. Sections can be nested if desired, since they are processed recursively. Sections can also include a reference to a content examples file that is used an introduction to the section.
Support for non-sectioned components is retained, so this PR should have no effect on existing guides that don't configure sections.

That’s very cool! Thank you very much. Just a few questions:

Can we also use HTML files as a content?

Is it renders everything on a single page? No routing?

No worries. Do you have any thoughts on how you're wire in using HTML files for content? I'm just forwarding them straight into the examples loader, so we're inheriting whatever capabilities it has there.
Everything is on a single page for now. I didn't want to make this PR too huge!

No worries. Do you have any thoughts on how you're wire in using HTML files for content? I'm just forwarding them straight into the examples loader, so we're inheriting whatever capabilities it has there.

We could figure it out later. But it could work as is for most of HTML files I think.

I didn't want to make this PR too huge!

Sure ;-)

I've merged master into this branch to remove the conflicts. Was there anything else you can see that needs changing at the moment?

Thank you very much!


Use nix::select directly to fix MacOS support

On MacOS, poll and kqueue are not supported for tty. So let's ditch mio completely and directly call select ourselves. It's not a lot of work anyway.
This fixes MacOS support.

I tested this to work on both Linux and Mac.

Using the old select function looks like a wrong solution.
I wonder if something like kqueue wouldn't work.

I'm trying to ponder the downsides of using the old select.
As I understand it, this would fail if the application using xterm-query has already opened many files, because of the file selector limit of select ?

wezterm's filedescriptor crate seems to have built a "poll" wrapper with compatibility for linux, mac, and windows: https://docs.rs/filedescriptor/latest/filedescriptor/index.html#polling

And maybe the Mac should use poll instead of select.

The whole issue is that Mac doesn't support poll or kqueue for tty (it's in the first line of the pr description 😉).
AFAIK the difference between poll and select is that the former is more efficient than the latter, for repeatedly calling. In here, we only need to call once and even if we didn't, we've only one FD so it wouldn't be so inefficient to re-initialising the fdset all the time.
I can't find any information about how they differ in terms of the number of open FDs in the process. Could you point me to some resource?
To summarise, I think only select usage keeps things simple here but if there are good reasons to avoid it for this very simple case, I can update the pr to use select only for Mac.

To summarise, I think only select usage keeps things simple here but if there are good reasons to avoid it for this very simple case, I can update the pr to use select only for Mac.

https://beesbuzz.biz/code/5739-The-problem-with-select-vs-poll
I'm not sure of the exact consequences of this problem.
Wezterm seems to have adopted the logic of using select only for mac: https://docs.rs/filedescriptor/latest/filedescriptor/index.html#polling

I can't find any information about how they differ in terms of the number of open FDs in the process. Could you point me to some resource?

NM, I found it. I'll update the pr accordingly.

Closing this in favor of #4, that uses select on MacOS but poll on other OSes.


fix: gock doesn't work with https

gock doesn't work with https, so instead of mocking, we were talking to the actual clusters.

gock doesn't work with https, so instead of mocking, we were talking to the actual clusters.

perfect timing for this PR! I was just wondering why I suddenly got this error ;)


PostgresDsn no longer has a 'build' attribute.

Initial Checks

[X] I confirm that I'm using Pydantic V2 installed directly from the main branch, or equivalent

Description
We are no longer able to build using PostresDSN
Example Code
@property
def uri(self) -> PostgresDsn:
    """Return uri for connection."""
    return PostgresDsn.build(
        scheme=self.scheme,
        user=self.user,
        password=self.password,
        host=self.host,
        port=str(self.port),
        path=f"/{self.dbname}",
        query=f"sslmode={self.sslmode}",
    )

However, we now get the following error:
`AttributeError: type object 'pydantic_core._pydantic_core.MultiHostUrl' has no attribute 'build'`

Python, Pydantic & OS Version
pydantic version: 2.0
        pydantic-core version: 2.0.1 release build profile
                 install path: /Users/oliver/Library/Caches/pypoetry/virtualenvs/sherlock-9z3yAd_C-py3.11/lib/python3.11/site-packages/pydantic
               python version: 3.11.4 (main, Jun 15 2023, 07:55:38) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)]
                     platform: macOS-13.4-arm64-arm-64bit
     optional deps. installed: ['typing-extensions']

Selected Assignee: @Kludex

I guess this is actually a pydantic core issue since this is now in core. https://github.com/pydantic/pydantic-core/blob/0d12efd1725ce190f13f9e51af3fd74b6cbab23e/src/url.rs#L158 would be my guess on where its located.

Yeah - It seems pydantic-core needs a 'Build' method on MultiHostUrl (or similar). Im not familiar with rust so would find this hard to fix, but happy to give it a go.

Can you template into a string and call PostgresDsn with that string?

I had the same error with the build but I replaced with a manual url
    # Database
    POSTGRES_HOSTNAME: str
    POSTGRES_PORT: str
    POSTGRES_USER: str
    POSTGRES_PASSWORD: str
    POSTGRES_DB: str

    SQLALCHEMY_DATABASE_URI: Optional[PostgresDsn] = None

    @validator("SQLALCHEMY_DATABASE_URI", pre=True)
    def assemble_db_connection(cls, v: Optional[str], values: Dict[str, Any]) -> Any:
        if isinstance(v, str):
            return v
        scheme = "postgresql"
        user = values.get("POSTGRES_USER")
        password = values.get("POSTGRES_PASSWORD")
        host = values.get("POSTGRES_HOSTNAME")
        port = values.get("POSTGRES_PORT")
        path = f'/{values.get("POSTGRES_DB", "")}'

        url = f"{scheme}://{user}:{password}@{host}:{port}{path}"
        return PostgresDsn(url)

Finally, I used with unicode_string() when I created the sqlalchemy engine
engine = create_engine(settings.SQLALCHEMY_DATABASE_URI.unicode_string())

I've created a PR https://github.com/pydantic/pydantic-core/pull/730 here in pydantic core. Im sure it needs some work, but seems to be good from what i can tell.

This has been implemented, closing


Hello-rails-Front-end

Instructions to run the project :
git checkout setup-react
npm install
npm start
This is Front-end of the application In which i have implemented the following things :
Create a new React app called 'hello-react-front-end'
Initialize your project with Git.
Create the App component with react-router.
Create the Greeting component that will display a greeting. Set it up as a route in your App component.
Create a store, an action and a reducer that will connect to you API endpont to get the random greeting.
Display the random greeting in your Greeting component.

Please Approve my Project as the deadline is near. I have only this activity pending in my dashboard for the final Capstone Project Module.

I have already installed the mentioned package (You can verify from paackage.json file) but the error still prisits therefore I have disabled linters for just this one line. I would Request the reviewer to please mention the solution before rejecting PR since I found the only way.

✅✅ The project is working fine. ✅✅

Hi @umair-rao 👍,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that ought to be done in a fresh PR; kindly open a new PR and ensure that all the project milestones are done. 🙏
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Using unocss in react + vite results in an error "hook is not a function"

UnoCSS version
^0.57.5
Describe the bug
Use unocss according to this document  unocss/vite

Reproduction
!
System Info
{
"name": "hello unocss",
"private": true,
"version": "0.0.0",
"type": "module",
"scripts": {
"dev": "vite",
"build": "tsc && vite build",
"preview": "vite preview"
},
"dependencies": {
"react": "^18.2.0",
"react-dom": "^18.2.0"
},
"devDependencies": {
"@types/node": "^20.9.1",
"@types/react": "^18.0.17",
"@types/react-dom": "^18.0.6",
"@vitejs/plugin-react": "^2.1.0",
"typescript": "^4.6.4",
"unocss": "^0.57.5",
"vite": "^3.1.0"
}
}
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Are you sure this is a Uno problem?

We temporarily close this due to the lack of enough information.
Please provide a minimal reproduction to reopen the issue.
Thanks.

Why reproduction is required


Update license in files to point to the root license

Fix #196.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3f4e59c). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #210   +/-   ##
=========================================
  Coverage          ?   97.43%
=========================================
  Files             ?       41
  Lines             ?     1947
  Branches          ?        0
=========================================
  Hits              ?     1897
  Misses            ?       50
  Partials          ?        0

Impacted Files
Coverage Δ

packages/Kokkos/src/details/DTK_PriorityQueue.hpp
100% <ø> (ø)

packages/Kokkos/src/DTK_InputAllocators_def.hpp
100% <ø> (ø)

packages/Kokkos/src/DTK_EvaluationSet.hpp
100% <ø> (ø)

packages/Kokkos/src/DTK_BVHQuery_def.hpp
100% <ø> (ø)

packages/Kokkos/src/DTK_Point.hpp
100% <ø> (ø)

packages/Kokkos/src/DTK_PolyhedronList.hpp
100% <ø> (ø)

packages/Utils/test/tstMpiTagConsistency.cpp
100% <ø> (ø)

packages/Kokkos/src/DTK_View.hpp
100% <ø> (ø)

packages/Utils/test/tstDBC.cpp
67.67% <ø> (ø)

packages/Kokkos/test/tstDetailsAlgorithms.cpp
100% <ø> (ø)

... and 31 more

Continue to review full report at Codecov.

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

Did we check anywhere to see if this was still a valid way to prescribe an open-source license?

No, we did not. And quick googling does not help.

I looked at root from the cern.  Here is an example https://github.com/root-project/root/blob/master/core/rint/src/TRint.cxx

I like the root example posted by @dalg24. Could we do something more like that instead?

So, something like this?
/*************************************************************************
 * Copyright (c) 2012, Stuart R. Slattery                                *
 * All rights reserved.                                                  *
 *                                                                       *
 * For the licensing terms see $DTK/LICENSE.                             *
 *************************************************************************/

Yeah I can't say I love having my name on it like that but that is what the license currently says. We can always change it if we update licenses

In deal, we use  the deal.II authors https://github.com/dealii/dealii/blob/master/source/dofs/dof_accessor.cc Also the copyright is range of year from creation to the file to when it was last touched (we use a script to do the update).

OK I like the @Rombur suggestion even better

So,
/*************************************************************************
 * Copyright (c) 2012-2017 by the DTK authors                                *
 * All rights reserved.                                                  *
 *                                                                       *
 * For the licensing terms see $DTK/LICENSE.                             *
 *************************************************************************/

@aprokop Looks good to me

Updated the PR.

Slightly tweaked version
/*************************************************************************
 * Copyright (c) 2012-2017 by the DataTransferKit authors
 * All rights reserved.
 *
 * This file is part of the DataTransferKit library. DataTransferKit has a
 * BSD 3-clause license. For the licensing terms see the LICENSE file in
 * the top-level directory.
 *************************************************************************/


Firmware not connected issue

Hi,
on a HassOS 3.5, with RaspBee, and 2.05.69 version of Phoscon,
I get a "firmware not connected" image on the Gateway tab.
Any ideas? I know that the security token is not set up as well, but I suspect that I first need to fix the firmware issue.
Logs:
starting version 232
[06:51:54] INFO: Starting the deCONZ gateway...
[06:51:54] INFO: Running the deCONZ OTA updater...
[06:51:54] INFO: Running the IKEA OTA updater...
[06:51:54] INFO: Running Hass.io discovery task...
{"uuid":"be1bfd9c00974ee397b9269d55577824"}
[06:51:54] INFO: Success send discovery information to Home Assistant
[06:51:54] INFO: deCONZ is set up and running!
libpng warning: iCCP: known incorrect sRGB profile
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
06:51:54:873 HTTP Server listen on address <IP_ADDRESS>, port: 40850, root: /usr/share/deCONZ/webapp/
06:51:54:898 CTRL. 3.16.206:51:54:969 dev /dev/ttyAMA0
06:51:54:969 COM: /dev/ttyAMA0 / serialno:
06:51:54:969 COM: --dev: /dev/ttyAMA0 (RaspBee)
06:51:54:969 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
06:51:55:080 parent process bash
06:51:55:080 gw run mode: docker/hassio
06:51:55:080 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
06:51:55:080 sd-card cid: 035344534e36344780ffffffff013500
06:51:55:081 DB sqlite version 3.16.2
06:51:55:082 DB PRAGMA page_count: 30
06:51:55:082 DB PRAGMA page_size: 4096
06:51:55:083 DB PRAGMA freelist_count: 0
06:51:55:083 DB file size 122880 bytes, free pages 0
06:51:55:083 DB PRAGMA user_version: 6
06:51:55:083 DB cleanup
06:51:55:083 DB create temporary views
06:51:55:088 don't close database yet, keep open for 900 seconds
06:51:55:089 started websocket server at port 40860
06:51:55:095 found node plugin: libde_rest_plugin.so - REST API Plugin
06:51:55:098 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
06:51:56:350 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
06:51:56:375 dev /dev/ttyAMA0
06:51:56:375 COM: /dev/ttyAMA0 / serialno:
06:51:56:375 COM: --dev: /dev/ttyAMA0 (RaspBee)
06:51:56:426 New websocket <IP_ADDRESS>:59184 (state: 3)
06:51:56:902 device state timeout ignored in state 2
06:51:57:852 device state timeout ignored in state 2
06:51:58:818 device state timeout ignored in state 2
06:51:59:490 New websocket <IP_ADDRESS>:59187 (state: 3)
06:51:59:818 device state timeout ignored in state 2
06:52:00:358 dev /dev/ttyAMA0
06:52:00:561 discovery network reply error: Error transferring http://dresden-light.appspot.com/discover - server replied: Service Unavailable
06:52:00:818 device state timeout ignored in state 2
06:52:01:817 device state timeout (handled)
06:52:02:215 New websocket <IP_ADDRESS>:59188 (state: 3)
06:52:02:317 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
06:52:02:317 device state timeout ignored in state 1
06:52:02:818 wait reconnect 15 seconds
06:52:03:355 New websocket <IP_ADDRESS>:57690 (state: 3)
06:52:03:818 wait reconnect 14 seconds
06:52:04:817 wait reconnect 13 seconds
06:52:05:818 wait reconnect 12 seconds
06:52:06:818 wait reconnect 11 seconds
06:52:07:818 wait reconnect 10 seconds
06:52:08:817 wait reconnect 9 seconds
06:52:09:818 wait reconnect 8 seconds

@youlib The Hass.io addon is a completely separate project from this Docker image and you will need to open an Issue on the repo for the Hass.io addons: https://github.com/home-assistant/hassio-addons.

Hi Mark,
I understand, I was under the wrong impression that the issue was within
the docker,
but, dah, that was stupid :D Thank you for your reply and for the nice
docker image!
youlib
On Mon, Oct 21, 2019 at 9:52 PM Mark Coombes<EMAIL_ADDRESS>wrote:

@youlib https://github.com/youlib The Hass.io addon is a completely
separate project from this Docker image and you will need to open an Issue
on the repo for the Hass.io addons:
https://github.com/home-assistant/hassio-addons.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/marthoc/docker-deconz/issues/170?email_source=notifications&email_token=AEAAAVHL4YCHAYLCNEOCG3LQPYB6DA5CNFSM4JCOGMIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB3SJUQ#issuecomment-544679122,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAAAVG2E52E5NA62SF63S3QPYB6DANCNFSM4JCOGMIA
.

im facing same issue any tip?


Update howto-create-a-storageclass.md to fix doc typos

Fix documentation typos to deploy a SC in ARO

@kevinpz : Thanks for your contribution! The author(s) have been notified to review your proposed change.

LGTM

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Adding endpoint for front end error reports.

@achen2401 will this work for sending in errors from front end code?

@achen2401 if the logger level is configured to send an email, it'll do so, as is the case on stg & production.
https://github.com/uwcirg/true_nth_usa_portal/blob/develop/portal/app.py#L210-L220


⚠ Cioos Pacific CKAN has degraded performance

In b6d4b4c, Cioos Pacific CKAN (https://catalogue.cioospacific.ca) experienced degraded performance:

HTTP code: 200
Response time: 12776 ms

Resolved: Cioos Pacific CKAN performance has improved in 107e913 after 22 minutes.


Hypothesis strategy for chunking arrays

Example of using this PR to create examples of arrays with a specific shape but arbitrary chunk structure:
In [9]: arr
Out[9]:
array([[1, 2, 3],
       [4, 5, 6]])

In [10]: from dask.array.strategies import chunks

In [11]: dask.array.from_array(arr, chunks=chunks(arr.shape).example())
Out[11]: dask.array<array, shape=(2, 3), dtype=int64, chunksize=(1, 3), chunktype=numpy.ndarray>

In [12]: dask.array.from_array(arr, chunks=chunks(arr.shape).example())
Out[12]: dask.array<array, shape=(2, 3), dtype=int64, chunksize=(2, 2), chunktype=numpy.ndarray>

[x] Closes #9373
[x] Tests added / passed
[ ] Passes pre-commit run --all-files

Can one of the admins verify this patch?
Admins can comment ok to test to allow this one PR to run or add to allowlist to allow all future PRs from the same author to run.

ok to test

Q: Should this utility expose max_chunk_lengths or be changed to expose max_num_chunks instead?

For some reason the new strategy is not showing up on the API docs page

mypy is failing with
dask/array/strategies.py:11: error: Untyped decorator makes function "block_lengths" untyped  [misc]
dask/array/strategies.py:45: error: Untyped decorator makes function "chunks" untyped  [misc]
Found 2 errors in 1 file (checked 244 source files)

which I would think is hypothesis' fault?

Thanks for opening this @TomNicholas! I have a few thoughts:

The mypy failure definitely feels like a hypothesis issue. It seems like it would not be too hard to pass the type though the decorator though (I'm looking at https://stackoverflow.com/questions/65621789/mypy-untyped-decorator-makes-function-my-method-untyped) so they would likely welcome that change upstream.
I am not convinced that this belongs in the dask/array part of the codebase. This is something the people would only use in  tests right so probably it should like in dask/array/tests/strategies.py
I don't have an opinion on whether to expose max_num_chunks or max_chunk_length. You could allow them both and error if they are both specified. Regardless of that choice these methods should be private at least to start.
Is this something that you are interested in maintaining? If so then great - I feel fine merging it into Dask if we can just ping you if something breaks :)

Thanks for your comments @jsignell !

The mypy failure definitely feels like a hypothesis issue.

I noticed there are recent changes to the code for that decorator in hypothesis so it might be that requiring a more recent version would fix this typing error? Looks like this PR was intended to make typing work with @st.composite.

I am not convinced that this belongs in the dask/array part of the codebase. This is something the people would only use in tests right so probably it should like in dask/array/tests/strategies.py

This depends on whether you think the tests namespace should be entirely a private library internal or not (I do). In xarray at least (and in numpy) we use tests to refer to internal checks checks that are run by pytest, and testing to refer to any test-related public API that someone else might want to import. So for example xarray.tests imports assert_equal from xarray.testing. (And yes we have an xarray/tests/test_testing.py file :grin:) However if dask has a different policy then I'm happy to defer, I just think this separation is neat.

I don't have an opinion on whether to expose max_num_chunks or max_chunk_length

This is really an intuition question for dask devs about which they think is more important for finding bugs. max_num_chunks would create uniform-length chunks by default (which we might want the strategy to arbitrarily deviate a bit from). max_chunk_length would create completely non-uniform chunks, but that might be overkill for finding bugs and/or mean an inefficient strategy.

You could allow them both and error if they are both specified.

I kind of don't really want to do that because they imply different strategies implementations under the hood, so allowing both is twice as much work :sweat_smile:

Regardless of that choice these methods should be private at least to start.
Is this something that you are interested in maintaining? If so then great - I feel fine merging it into Dask if we can just ping you if something breaks :)

I'm putting these here so that I can import them in xarray (/xGCM/xhistogram...)! So I am happy to maintain them, but I also want the chunks strategy to be public so that I'm not relying on private API.

I am not convinced that this belongs in the dask/array part of the codebase. This is something the people would only use in tests right so probably it should like in dask/array/tests/strategies.py

This depends on whether you think the tests namespace should be entirely a private library internal or not (I do). In xarray at least (and in numpy) we use tests to refer to internal checks checks that are run by pytest, and testing to refer to any test-related public API that someone else might want to import. So for example xarray.tests imports assert_equal from xarray.testing. (And yes we have an xarray/tests/test_testing.py file grin) However if dask has a different policy then I'm happy to defer, I just think this separation is neat.

Ah ok. Thanks for explaining. I took a look and realized that assert_eq is defined in dask/array/utils.py so I guess there is precedent. Given that, I am ok with the proposed placement and with it being public.

This is really an intuition question for dask devs about which they think is more important for finding bugs. max_num_chunks would create uniform-length chunks by default (which we might want the strategy to arbitrarily deviate a bit from). max_chunk_length would create completely non-uniform chunks, but that might be overkill for finding bugs and/or mean an inefficient strategy.

max_chunk_length feels slightly more dasky to me.

Coming back to this after a year :sweat_smile:
I've become interested in this problem again, and would like to merge this, but I'm just fighting with the CI to get everything to pass.


Group 82 : 2312517_2310886_2311614_2311548_2312365

Policy Overview
This pull request introduces two algorithms, Genetic Algorithm (GA) and Stock Filled Ratio Heuristic, designed to optimize material waste reduction and computational efficiency for the 2D Irregular Cutting Stock Problem.

####Team commitment:

Team Member
ID
Responsibility

Nguyễn Đăng Khoa
2311614
Implemented Stock filled_rate optimize heuristic

Nguyễn Lê Nguyên
2312365
Implemented Genetic Algorithm

Hồ Minh Nhiên
2312517
Revised code

Trịnh Vũ Đức Hải
2310886
Revised code

Lê Quang Khải
2311548
Revised code

Workflow of the Algorithms
Genetic Algorithm (GA):

Utilizes evolutionary techniques such as crossover and mutation to optimize material placement.
Scored solutions with a fitness function that balances maximizing filled ratio and minimizing trim loss.
While powerful, it suffers from premature convergence and high computational costs.

Stock Filled Ratio Heuristic:

Employs a deterministic approach to prioritize larger items and efficiently pack remaining space with smaller items.
Focuses on minimizing trim loss while ensuring faster execution for small to medium datasets.

Results
Based on the dataset of seed 42 used for testing, the following results were obtained in comparison with Greedy and Random policies:

Policy
Filled Ratio
Trim Loss
Runtime (s)

Genetic Algorithm
0.23
0.4141
~224.00

Stock Filled Heuristic
0.27
0.3036
45.19

Conclusion
The Stock Filled Ratio Heuristic demonstrates efficient and effective performance in reducing trim loss and improving material utilization, with reasonable computational cost. The Genetic Algorithm, while less efficient in runtime, provides insight into the potential of metaheuristic approaches but requires further refinement to overcome premature convergence and excessive runtime.
Kindly review and provide feedback!

@martinakaduc I made this new PR to correct my old #469 , which I have deleted.

Close PR as it does not comply with submission instructions.


use response filter directly

Using a post routing middleware was clunky.  The web server can define request handlers that process a queue of response filters.

Following the spirit of the PSR-15 Meta Document would allow for improved de-coupling and interoperability.
See https://www.php-fig.org/psr/psr-15/meta/#queue-based-request-handler and https://www.php-fig.org/psr/psr-15/meta/#queue-based-request-handler for implementation ideas.


[New Feature?] Translate to "default" language

I use this "custom templates" and it work fine.
I would be very interested in having this feature without the need to "explicitly" specify the translation language, instead use the "default" language of the GUI/HA.
So if i specify a language as a Parameter it will be translated to this specific language, but if i don't use this Language Parameter it will be translated to the "default" language of the system. This makes it possible to change the language by changing the default HA language.
Do you think this is possible?

"explicitly" specify the translation language, instead use the "default" language of the GUI/HA.

This is already done in HA 2024.3 - see state_translated function in Docs.
In 2024.3 some functionality of this custom plugin was added to the HA core.

Thank you for this information, i did not see this in the documentation of 2024.3
Am 19. März 2024 17:45:15 GMT+04:00 schrieb ildar170975 @.***>:

"explicitly" specify the translation language, instead use the "default" language of the GUI/HA.

This is already done in HA 2024.3 - see state_translated function in Docs.
In 2024.3 some functionality of this custom plugin was added to the HA core.
--
Reply to this email directly or view it on GitHub:
https://github.com/PiotrMachowski/Home-Assistant-custom-components-Custom-Templates/issues/23#issuecomment-2007220309
You are receiving this because you authored the thread.
Message ID: @.***>
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit Squeaky Mail gesendet.

Thanks for the link, I actually overlooked or ignored this point! That helps me at least partially. :+1:

@jkrasinger
I think the issue can be closed.

I'll keep it - I will add this feature to other functions

@ildar170975 and @PiotrMachowski : OK, I will leave this issue open for now.

Added in v1.4.0


[CPU] Remove special distribution tile size adjustment from generic ops.

We have a general fix in https://github.com/openxla/iree/commit/d99527b94d4f69f22982288625cec7c715cdca49. It reduces the number of workgroups in cases where we are dividing the work too much. We no longer need the specialization for elementwise generic ops.

@hanhanW still valid?


Made some Bug fix on piechart

When one of the slices is clicked on, it displays it's percentage at the centre

@tundealabi Pls help review, I just made a bug fix, I misplaced value before

@abiona01 reviewed


Update readme and check project against 23.10

First take on an unified readme format used accross every O3DE samples (and checked that the project still runs correctly on the release of 23.10.3)
The goal being to make the samples more accessible to the users. Both by updating the project's readme, adding a version check and linking them in O3DE showcase and doc pages. Task tracked via this issue : https://github.com/o3de/o3de.org/issues/2549

Change is visible here : https://github.com/guillaume-haerinck/buongiorno-sample/tree/unified_readme


"Modern" fake-timer implementation doesn't work with PromiseJS.

Awesome work on https://github.com/facebook/jest/pull/7776, thanks for that!!
🐛 Bug Report
I'm using Jest 26.1.0.
Testing async code with Promises, as described in this Jest doc, doesn't seem to work with jest.useFakeTimers('modern'); (from https://github.com/facebook/jest/pull/7776; documented here) if you're using the 'promise' library from NPM.
For a while (starting in https://github.com/facebook/react-native/commit/3ff39870ce776c653823e1733363be0401896294), React Native has used that library as part of their Jest setup (which you get if you use preset: 'react-native'), so I expect this will affect most people using React Native (this is how I encountered it).
Otherwise, I'm not sure how often people use that 'promise' library, but it's an official solution given in a Jest troubleshooting doc, and pops up as a workaround for some issues in this repo (e.g. here).
This is arguably a regression (or would be when 'modern' becomes the default), as this behavior isn't observed with jest.useFakeTimers('legacy'); or jest.useRealTimers().
To Reproduce
E.g.,
global.Promise = require('promise');

jest.useFakeTimers('modern');

test('1 equals 1', async () => {
  await Promise.resolve();
  expect(1).toEqual(1);
});

Expected behavior
I expect the test to pass. Instead, five seconds go by and I get this failure:
  ✕ 1 equals 1 (5006 ms)

  ● 1 equals 1

    : Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout.Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout.Error:

      3 | jest.useFakeTimers('modern');
      4 |
    > 5 | test('1 equals 1', async () => {
        | ^
      6 |   await Promise.resolve();
      7 |   expect(1).toEqual(1);
      8 | });

      at new Spec (node_modules/jest-jasmine2/build/jasmine/Spec.js:116:22)
      at Object.<anonymous> (fetchData.test.js:5:1)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        5.762 s, estimated 6 s
Ran all test suites.
error Command failed with exit code 1.

Link to repl or repo (highly encouraged)
In the repro linked below, I've closely imitated all the tests from the sections in the "Testing Asynchronous Code" doc that use Promises, to suggest that the failure happens in usual, well-documented ways of testing (provided you're using PromiseJS).
In its current state, you should observe these timeout errors on tests that use Promises (just run yarn and yarn test).
Try uncommenting global.Promise = require('promise'); at the top of fetchData.test.js; the tests should all pass.
Try doing something other than jest.useFakeTimers('modern');; the tests should all pass.
(Incidentally, note that accidentally calling jest.useFakeTimers multiple times with different arguments in the same file seems disruptive and might hamper your investigation. Also, be sure to comment out jest.runAllTimers() if you're using real timers.)
https://github.com/chrisbobbe/jest-async-modern-timers-repro
envinfo
  System:
    OS: macOS 10.15.5
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 10.20.1 - ~/.nvm/versions/node/v10.20.1/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v10.20.1/bin/npm
  npmPackages:
    jest: ^26.1.0 => 26.1.0

I have the same error with nock.
The test case
test('nock', async () => {
    jest.useFakeTimers('modern');
    nock('http://modern').get("/").reply(200);
    await fetch(`http://modern`, { method: "GET" });
});

Failing :
 : Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout.Timeout - Async callback was not invoked within the 5000 ms timeout specified by jest.setTimeout.Error:
  > 18 |         test('nock', async () => {
    |         ^
    19 |             jest.useFakeTimers('modern');
    20 |             nock('http://modern').get("/").reply(200);
    21 |             await fetch(`http://modern`, { method: "GET" });

It's working when I replace

'modern' by 'legacy'
or
fetch(...) by Promise.resolve() (nock is not actually used)

Hmm, I wonder if this is because we fake process.nextTick as well. As a test, can you modify your<EMAIL_ADDRESS>(or wherever it's located) from the line const toFake = Object.keys(this._fakeTimers.timers); to const toFake = Object.keys(this._fakeTimers.timers).filter(name => name !== 'nextTick');. That should exclude it. This is the default behavior of @sinonjs/fake-timers, which I've changed in Jest's implementation.

As an aside, one should never replace global.Promise - that suggestion is outdated. E.g. when using async-await you will always get the native Promise regardless of the value of global.Promise.

modify your<EMAIL_ADDRESS>(or wherever it's located) from the line const toFake = Object.keys(this._fakeTimers.timers); to const toFake = Object.keys(this._fakeTimers.timers).filter(name => name !== 'nextTick');.

The test with nock is working fine after doing it.
Since I tried 'modern' for _.debounce it's worth mentionning that a test I have with debounce is still working (It was not obvious to me).

As a test, can you modify your<EMAIL_ADDRESS>(or wherever it's located) from the line const toFake = Object.keys(this._fakeTimers.timers); to const toFake = Object.keys(this._fakeTimers.timers).filter(name => name !== 'nextTick');.

Yep—when I do this, it works!

As an aside, one should never replace global.Promise - that suggestion is outdated. E.g. when using async-await you will always get the native Promise regardless of the value of global.Promise.

Thanks for the heads-up! Yeah, a priori, I'm not really interested in replacing global.Promise. But I'm using React Native, with preset: 'react-native', so it's being done for me (RN has been doing this since https://github.com/facebook/react-native/commit/3ff39870ce776c653823e1733363be0401896294).

But I'm using React Native, with preset: 'react-native', so it's being done whether I like it or not

Opened https://github.com/facebook/react-native/issues/29303 to find out more about React Native's motives here. 🔍

Hmm, I wonder if this is because we fake process.nextTick as well. As a test, can you modify your<EMAIL_ADDRESS>(or wherever it's located) from the line const toFake = Object.keys(this._fakeTimers.timers); to const toFake = Object.keys(this._fakeTimers.timers).filter(name => name !== 'nextTick');. That should exclude it. This is the default behavior of @sinonjs/fake-timers, which I've changed in Jest's implementation.
As an aside, one should never replace global.Promise - that suggestion is outdated. E.g. when using async-await you will always get the native Promise regardless of the value of global.Promise.

After waisting a day troubleshooting why promises weren't working, this worked! Thank you.
I think Jest should resort back to the way Lolex was before. See https://github.com/sinonjs/fake-timers/issues/114 for more context as to why Lolex didn't fake nextTick. Most people will not want the current behavior. Maybe Jest can provide an option to fake nextTick, but not by default.

Filtering out 'nextTick' works for native promises and should really be the default behaviour. Is there any workaround in the meantime for this without tinkering in node_modules to make this usable in CI/CD until a fix is out?

Filtering out 'nextTick' works for native promises and should really be the default behaviour. Is there any workaround in the meantime for this without tinkering in node_modules to make this usable in CI/CD until a fix is out?

@squareloop1 I'd recommend using this nifty little tool. I just used it to patch Jest to the working fake-timers code. It's unfortunate, but I've also had to use it on several other packages that I'm using in my React Native app.

@tomdaniel0x01 thanks, I think I will use fake timers from sinon for now, as they seemed to work. But I'd would rather get rid of another dependency and use it in jest. Its the only thing really missing in jest.
I have to add to this issue for clarity: It does not only affect non-native global.promise replacements, it also makes native promises in Node.JS stop working.

Hey @chrisbobbe, great work with the triaging of this issue! Did you get any updates about it recently? I did not see any follow up or response in the issue that you created in the RN repo.
FYI, I've found a more friendly solution than forking the entire RN dependency: hijack the react-native jest preset instead. Here you can see an example of how it's done

Hey @chrisbobbe, great work with the triaging of this issue!

Thanks! 🙂

Did you get any updates about it recently? I did not see any follow up or response in the issue that you created in the RN repo.

No, unfortunately I haven't had any updates.

FYI, I've found a more friendly solution than forking the entire RN dependency: hijack the react-native jest preset instead. Here you can see an example of how it's done

Great, thanks for the tip!!

FYI, I've found a more friendly solution than forking the entire RN dependency: hijack the react-native jest preset instead. Here you can see an example of how it's done

@sbalay Thank you very much for the hint to this custom preset! It saved me more time to investigate why my tests did not work:
beforeAll(() => {
  jest.useFakeTimers("modern")
})

afterEach(cleanup)

afterAll(() => {
  jest.useRealTimers()
})

it("should report time updates every 30 minutes", () => {
    jest.setSystemTime(new Date("2020-11-19T10:00:00.000Z"))
    const { result } = renderHook(() => useDateTime("minute"))
    expect(result.current.toISOString()).toEqual("2020-11-19T10:00:00.000Z")
    act(() => {
      jest.advanceTimersByTime(1000 * 1 * 60)
    })
    expect(result.current.toISOString()).toEqual("2020-11-19T10:01:00.000Z")
  })

I did not use any async functions in my test, just setTimeout but even with an empty test, merely calling useFakeTimers made the empty test just time out.
Do you think we should report this bug to the jest react-native package?

@SimenB any progress on this? It seems like the problem and solution are both known. Is there any reason a change should not be made that would stop mocking nextTick? Is this just waiting on someone to make the change?

For most cases here I assume a strategically placed jest.runAllTicks() would solve the issue, but it's non-obvious

Is this just waiting on someone to make the change?

This, essentially 🙂 However, the change to make is not obvious. If we stop mocking nextTick by default we need to allow people to mock it if they want (right now we mock everything, which I think is ideal, but it sometimes breaks other modules).

Is there a recommended way to circumvent this for "productive" use?
Does it make sense to use the "legacy" implementation for cases where nock and fake timers are used?
I already spent a bit too much time on this and gave up for now 😕

@marikaner an acceptable workaround that we are using is to use the library https://github.com/sinonjs/fake-timers to fake the timers where we need to. Then you replace the jest APIs (jest.useFakeTimers(), jest.advanceTimersByTime(), etc) with the sinon fake-timers apis (let clock = FakeTimers.install(), clock.tick(), etc).

@SimenB

If we stop mocking nextTick by default we need to allow people to mock it if they want (right now we mock everything, which I think is ideal, but it sometimes breaks other modules).

So it would be acceptable to stop mocking nextTick by default, as long as there is a way to make sure it gets mocked? Would an API similar to sinon's for choosing what to mock work here?
The user's code would then look something like this:
it('does not mock nextTick', () => {
  jest.useFakeTimers('modern')
  // `nextTick` is not mocked by default
})

it('mocks nextTick', () => {
  jest.useFakeTimers('modern', { toFake: ['nextTick'] })
  // nextTick is mocked when requested
})

Or the other way : keep everything mocked by default, and a way to exclude some methods ?
it('does not mock nextTick', () => {
  jest.useFakeTimers('modern')
  // `nextTick` is mocked by default
})

it('mocks nextTick', () => {
  jest.useFakeTimers('modern', { toNotFake: ['nextTick'] })
  // nextTick is not mocked when requested
})

I created a pull request to add the options object with an ignore property (notToFake) 100% inspired by the comment above. Any feedback is welcome and greatly appreciated.
The added code is kept deliberately simple and pragmatic, it can still be changed easily to reflect any input.

@jschoubben Thank you! This would be so great if it got in

Is this moving along? As issue still persists.

facing same issue. Have we fixed this issue or it's still in progress?

Possible workaround for the time being is using https://github.com/sinonjs/fake-timers, as it was mention before. But here's the example for those who stumbles across this thread:
import FakeTimers, { InstalledClock } from "@sinonjs/fake-timers";

const now = new Date("2021-11-25 11:00:00");

let clock: InstalledClock;
beforeAll(() => {
  clock = FakeTimers.install({
    now: now,
    shouldAdvanceTime: true,
    toFake: ["Date"],
  });
});

afterAll(() => {
  clock.uninstall();
});

I tried using this but I keep getting jest warnings:
console.warn
A function to advance timers was called but the timers API is not mocked with fake timers. Call jest.useFakeTimers() in this test or enable fake timers globally by setting "timers": "fake" in the configuration file
Stack Trace:
at FakeTimers._checkFakeTimers (node_modules/@jest/fake-timers/build/modernFakeTimers.js:168:13)
at FakeTimers.advanceTimersByTime (node_modules/@jest/fake-timers/build/modernFakeTimers.js:100:14)
at node_modules/@testing-library/dom/dist/wait-for.js:90:18
at node_modules/@testing-library/dom/dist/wait-for.js:88:17
at unstable_advanceTimersWrapper (node_modules/@testing-library/dom/dist/config.js:26:40)
at node_modules/@testing-library/dom/dist/wait-for.js:87:15
at waitFor (node_modules/@testing-library/dom/dist/wait-for.js:39:10)

@dagadbm can you share more of your code? It's hard to see how your problem is related to this issue without more context

https://github.com/dagadbm/load-monitoring-challenge
This component is the one I wanted to do an integration test on: https://github.com/dagadbm/load-monitoring-challenge/blob/master/front-end/src/features/metrics/Metrics.tsx#L24
As you can see we have a useEffect that dispatches a fetch call and also a dispatch for a pooling mechanism using setInterval every POOLING_RATE
This is the fetch code:  https://github.com/dagadbm/load-monitoring-challenge/blob/master/front-end/src/features/metrics/metricsAPI.ts
I basically wanted to create a test that I mock the requests with MSW and then use jest fake timers (or sinon fake timers).
jest timers make the fetch to not even resolve.
Sinon fake timers are wildly inconsistent when I try to check the store state it is never what I expect it to be. (More details on the test below).
To have an idea of what I wanted to do you can check out this test I did where I manually do a "fake pooling" by dispatching actions manually on the store: https://github.com/dagadbm/load-monitoring-challenge/blob/master/front-end/src/features/metrics/Notification.test.tsx#L46
However, to really be integration, I would have loved for the setInterval to actually run so I dont have to manually dispatch all the actions to the store.
[...]

test('integration test', async () => {
  // this request should be for this line of code:
  // https://github.com/dagadbm/load-monitoring-challenge/blob/master/front-end/src/features/metrics/Metrics.tsx#L26

  jest.useFakeTimers(); // i am using latest CRA version.
  mockFetchCPUAverage(TIMESTAMP, DEFAULT_THRESHOLD);
  const { store } = render(<Metrics />);

  // wait until we have the first result of the API call on the store
  await waitFor( () => {
    expect(store.getState().metrics. cpuAverage.length).toBe(1);
  });

  // and from here on out I would expect, for each setInterval a different returned result from the API
  // similar to the notification test I showed before

  // second request
  mockFetchCPUAverage(TIMESTAMP, DEFAULT_THRESHOLD);
  jest.advanceTimersBy(POOLING_RATE);
  await waitFor( () => {
    expect(store.getState().metrics. cpuAverage.length).toBe(2);
  });

  // third request
  // ...

  // and so on and so forth until the UI changes so that I can assert the UI and not the store
});

I hope I wasnt too overwhelming. Let me know if I can be more explicit.

@dagadbm This issue is about the fact that jest fake timers do not work with promises, but in the example code you shared it looks like you are still using jest's fake timers (jest.useFakeTimers). The suggested solution from a comment above is to use sinon fake timers instead, because it does not mock the nextTick function by default.
However it seems that the issue you are seeing is more related to react-testing-library.  I'm assuming that the error you were seeing (A function to advance timers was called but the timers API is not mocked with fake timers) has something to do with React Testing Library, because it looks like they try to do something with fake timers here. According to that Pull Request, it looks like you can just do something like this.
jest.useFakeTimers()
await waitFor(() => // next message to appear)
jest.useRealTimers()

And here's an example.

Code similar to yours with working tests

import React, { useRef, useEffect, useState } from 'react'
import { render, screen, act } from '@testing-library/react'
import FakeTimers from '@sinonjs/fake-timers'
import useInterval from 'someUseIntervalLib'

export const messages = ['message 1', 'message 2', 'message 3', 'the end']

const POOLING_RATE = 10_000
let fetchCount = 0
function fetchNewMessage() {
	console.log('fetching!')

	return new Promise(res => res(messages[fetchCount++ % messages.length]))
}

function Test() {
	console.log('rendering')
	const [message, setMessage] = useState(null)
	useInterval(() => {
		console.log('intervalling')

		fetchNewMessage().then(message => {
			setMessage(message)
		})
	}, POOLING_RATE)

	return (

Your Message

{message}

	)
}

describe('Interval fetching', () => {
	it('fetches new stuff on an interval', async () => {
		jest.useFakeTimers()
		render(<Test />)
		expect(screen.getByRole('heading', { name: 'Your Message' })).toBeTruthy()

		for (let i = 0; i < messages.length; i++) {
			const message = messages[i]
			await waitFor(
				() => {
					expect(screen.getByRole('heading', { name: message })).toBeTruthy()
				},
				{ timeout: POOLING_RATE }
			)
		}

		jest.useRealTimers()
	})
})

So jest.useFakeTimers() doesn't work within async functions, right?
Is this gonna be fixed any time soon so that we don't need to rely on @sinonjs/fake-timers?

Finally fixed in #12572, available in https://github.com/facebook/jest/releases/tag/v28.0.0-alpha.8.


[Feature] Allow Computers to read block entity NBT values for data collection.

Describe your feature idea
When computers use the peripheral api on an unsupported block entity, it instead return a table that contains get methods for getting each value in that nbt table. These functions would not allow you to edit the nbt data. That way you can still collect data from mods that might not be supported.
Describe alternatives you've considered if you've any
There could also be a different api that wraps this behavior, but I believe that peripheral api would make the most sense.
Additional context
I think this was a feature in one of the many peripheral mods back it the day, because I distinctly remember using it with redpower 2 to get the energy levels in batteries.

I do not really understand what exactly do you want, it's already possible to get energy levels from every Energy Storage Block in 1.16. You can do wrap an Energy Container(e.g. Energy Cube From Mekanism, Battery Box from Silents mechanisms, ...) and get the stored energy.

I will close this for now to reduce the issues. I will reopen it if you respond to my question.

Sorry for the late response. I guess I should clarify the mechanic: Allow computers to read NBT Data from and block entities. Just like how a player can use the /data command to get nbt data from a block, so to could the computer using the peripheral api. The battery was just an example. Using this you could get the contents of a book in an adjacent lectern or the pattern of an adjacent banner. It would make getting information easier, because if the data is saved in the nbt, then you have access to it.
Hope that make sense!

Sorry, I did not see your response. I will reopen this issue!

Added in 0.7a


Importing tags

Hi, love the project. This was totally missing on the 3d printing scene.
One feature I would love to have is some way of importing tags. I have a large number of files that I have archived from a popular website for stls.
I have around 10 million folders, each has tags in an xml file (example attached as a txt file). It would be great to have some way of importing these tags. So far I have just been using a file indexer and searching for them that way. I was planning on importing them to an xml database at some point but this project is so far ahead of that its amazing.
Thank you!
example.txt

Oh, that;'s super interesting. I was strongly considering making a metadata file format to store everything on disk as well as in the db, so it can be transferred easily around and re-imported if the database is lost. Where does that XML format come from? Was it a standard part of the export from the site, or is that something you've created? If there's an existing standard, I'd be well up for adopting it.

Oh, that's super interesting. I was strongly considering making a metadata file format to store everything on disk as well as in the db, so it can be transferred easily around and re-imported if the database is lost. Where does that XML format come from? Was it a standard part of the export from the site, or is that something you've created? If there's an existing standard, I'd be well up for adopting it.

That is from an internet archive that someone made. And actually I just noticed that the one I gave you I had already snipped that out.
here is a link to the archive: https://archive.org/details/thingiverse?sort=-addeddate
here is a link to a complete XML from the archive: https://ia801505.us.archive.org/14/items/thingiverse-5487170/thingiverse-5487170_meta.xml
The archive has the most important data available on thingiverse parsed, so using that may be easiest. The file above is within a directory for each "thing". However, on the same internet archive he has also uploaded more data in a separate file.
https://archive.org/details/thingiverse_archive