Doubt how to launch the library

Hello 👋🏻 ,
First of all congratulations on your work and your contribution to the community.
I have a doubt in order to launch the library
We use yarn and our command to launch the tests is determined by different parameters example:
npx @perf-profiler/e2e measure --bundleId xxx --testCommand "yarn e2e:android:local:fr" --duration 100000 --resultsFilePath results.json
The test runs but the process continues and does nothing.
Any suggestion?
Thanks!

Hi @juannavalonribas, thanks for the congratulations! 😊
A few questions on my side:

what e2e framework are you using? what does yarn e2e:android:local:fr run?
can you share a copy of the logs you see in the terminal when running npx @perf-profiler/e2e measure ...?
what OS are you running on?

Hello @Almouro,
I am using appium@next (appium 2) with webdriverIO all in javascript. The command I am launching is "e2e:android:local:fr": "TEST_COUNTRY='FR' TEST_ENV=E2E yarn e2e:android:local --suite login",
Where e2e:android:local =  "e2e:android:local": "TEST_ENV=E2E wdio ./e2e/config/wdio.android.local.conf.js",
Logs:
[16:59:28] ℹ  Installing C++ profiler for arm64-v8a architecture [16:59:28] ✅  C++ Profiler installed in /data/local/tmp/BAMPerfProfiler [16:59:29] ℹ  Running iteration 1/10
And then the test is executed properly and ends showing:
Spec Files:      1 passed, 1 total (100% completed) in 00:00:33  ✨  Done in 36.05s.
But the "process" is still running with no more iterations
Running the command locally in a macbook m1 macOs Ventura 13.0.1 through webstorm terminal

ohh It was a missunderstanding.. true is working properly. But I have another question currently the json results.json report appears empty regarding the current json https://gist.github.com/juannavalonribas/35d53300e408d9d482876348443ab314
Any idea?

Oh that's not normal indeed
I've tried quickly with a small wdio example and cannot reproduce this.
Would you be able to reproduce this with a very simple test on your app? Something like:
describe("Very simple test", () => {
  it("finds the text", async () => {
    const text = "random text";
    const element = await $(
      `//*[contains(@text,'${text}')] |`
    );
    await element.waitForDisplayed({ timeout: 30000 });
    // Just wait for 5s to make sure we have performance measures before the app stops
    await new Promise((resolve) => setTimeout(resolve, 5000));
  });
});

Also is the app stopping and starting during the e2e test? We expect the test to start the app and never stop it (except at the end potentially)

It works with this simple example
describe(`Performance in ${country.countryCode}`, () => {
  beforeEach(async () => {
    await checkAppStatus();
  });
  it('Just Click in login button', async () => {
    await HomeScreen.goToLogin();
    await new Promise(resolve => setTimeout(resolve, 5000));
  });
});

appium capabilities:
        'appium:noReset': false,
        'appium:fullReset': false,

I am going to investigate what might be happening. The previous case I had tried it with a suite that only contains 1 test.

Hello!
I have tried using my real device connected in local env and it works perfect. Now im facing the challenge launching the test against browserstack.
I close this "doubt" cause has been resolved.
Thank

@juannavalonribas Up to my knowledge, Browserstack sadly doesn't allow adb access so this lib won't work (https://github.com/bamlab/android-performance-profiler#running-in-ci for more details)


plant - create group for plant+sensors, check history for min_brightness

Description:
This change consists of two parts:

I would like to have all data for a plant in a single group in the UI. So this extension of the plant component will allow to create a group of the plant itself will all the sensors that are related to it. You can choose the name of the group
This is based on the proposal in https://github.com/ChristianKuehnel/plantgateway/issues/14

You probably want to know if the place, where your plant is located at the moment is bright enough for the plant. Checking the min_brightness of a plant only makes sense when looking at the history. At night it's obviously dark, so it does not make sense to check min_brightness. Thus the new check looks at states in the database and checks if the maximum brightness over the last X days (where X can be configured) was above min_brightness.

Related issue (if applicable):
fixes https://github.com/ChristianKuehnel/plantgateway/issues/14
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#3417
Example entry for configuration.yaml (if applicable):
 plant:
   simulated_plant:
       sensors:
         moisture: sensor.mqtt_plant_moisture
         battery: sensor.mqtt_plant_battery
         temperature: sensor.mqtt_plant_temperature
         conductivity: sensor.mqtt_plant_conductivity
         brightness: sensor.mqtt_plant_brightness
       min_moisture: 20
       max_moisture: 60
       min_battery: 17
       group_name: sim_plant_group
       check_days : 3

The new fields are  "group_name" and "check_days".
Feel free to use the simulator for testing this change: https://github.com/ChristianKuehnel/hass_simulated_plant
Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

@ChristianKuehnel, this may be a stupid question but could you use a plant state-card to achieve part 1 and avoid all of the group creation stuff? Given that the plant entity already has all of the sensor states stored in its own attributes, you could just expose that via a plant state-card. @pvizeli Is that an allowed design approach ?
Reason, I'm asking is that I've done exactly this for my 12 miflora's. I now "hide" the 60-odd sensors and just have the 12 plant entities showing in the UI but with all of the problem identification information visible. A state-card does this without needing any modification to your current code. I've attached code/screenshot so you get the jist.
Anyway, feel free to file in the "thanks but ..."
The part 2 stuff looks great and look forward to trying it out. Thanks for all the efforts on this.

state-card-plant.zip

@PeteBa
I really like your solution! That looks really cool. Honestly I'm not sure how to proceed with the groups...
(in case anyone wants to use the state card : here are the instructions to install it: https://home-assistant.io/developers/frontend_creating_custom_ui/)

@PeteBa
After using it for a while, I have to admit that  the state cards look much nicer than the groups. The only downside that I found so far is that I cannot click e.g. on the moisture and then see the history of the value. But that's a minor issue.
Are you planning to merge the state card?

@ChristianKuehnel , thanks for the feedback! I've done a second iteration that I think looks better and brings in the battery level icons as well. I would love to get this merged in if you are supportive. I would want to do a small modification to plant.py (i.e. expose Icon and Units names) so I dont have to hard-code in the state-card. I assume this can be done, I just have to figure out how 8). I'll get a new PR going for this.

@pvizeli
The tests are now passing again, please merge or let me know what you want changed.

@pvizeli I haven't heard from you in a while. How do you want to proceed here?

I like the idea from @PeteBa a lot. It is the same thing that we do for weather: it too contains a lot of data points and it is shown in the UI as 1 card. I think that we should pursue that.

Hey @balloob ,
just to be sure: So you want me to remove the group feature from this PR? And only leave the brightness history feature in?

Do you think that we need the brightness feature or, when we add a new card for plants, we can just query the database for the history? (so it is also ok between restarts)

I'm not sure if I fully understand your proposal.
Functionality:
The history feature collects the maximum brightness over the last n days for every day. This will help you to decide if the plant gets enough light and if you need to move them. I need the history as it does not make any sense to look at the brightness at night. So the min_brightness check was quite useless so far.
Solution:
Initially I implemented this by querying the database when I wanted to update the value. After the comments from @pvizeli I changed the behavior: The database is only read on startup, after that I'm keeping the history in memory (one value per day). So this should be quite efficient.
So all in all, I would say the history still makes sense.
My question is: Do we want to keep the grouping feature in or shall I remove it?

@ChristianKuehnel , I have translated the state-card from above into the new ha-card format based on feedback from @balloob  above and submitted as work-in-progress here (https://github.com/home-assistant/home-assistant-polymer/pull/583). I am still showing the original brightness attribute as per the current Plant component but can change as needed.

Unless I've missed something, the new ha-card approach doesn't let you consolidate a group of plants into a single card like the custom state-card from the earlier post. Instead, you get one card per plant regardless of whether grouped or not.
So pros and cons here as some users may prefer the current group view (i.e. list of plant entities with just state shown), some may want the details always visible as per this ha-card and yet others may want something in between, such as, the default state-card with the above showing as the more-info when tapped.
I would very much appreciate your thoughts.

So what's the end goal?
If each attribute (c % lx ... ) is not a separate sensor you don't get a separate history (unless a hack on the UI side is done to pull it from attributes)

@andrey-git
My goal was to have all the values that belong to one plant together in one element in the UI. So that you immediately get an overview of how the plant is doing. This can either be done with groups (this PR) or via the UI (https://github.com/home-assistant/home-assistant-polymer/pull/583).
My 2 cents:

The group solution has the advantages that you still get the history for each sensor and the state badges disappear from the long list at the top of the UI. But they do not look so nice.
The UI solution has the advantage that it looks nicer and you get the color-coding of the values that are out of range. But you do not get the history and you have to hide the sensors manually.

So both options have their advantages and disadvantages...

@ChristianKuehnel , that is a great summary of the design choice here. Note that history works in the UI solution just haven't submitted as it requires changes to the plant component. Specifically, adding the sensor entity_ids to the plant state attributes so they are available on the polymer side.
A "con" for the ha-card is that it doesn't combine into a single card when grouping multiple plants together. You still end up with one card per plant entity. So no way to "hide" the detail from the user that just wants to see the headline ok/problem indicator.
The middle-ground might be to make this the "more-info" card that comes up when when you tap on a plant. The user would still need to manually hide all of the underlying sensors but they would have a consolidated view and access to history from more-info. If someone (like you and me !) wants the full detail on their view then the custom-state-card from above is an option.

you should make the sensors optional
sensors:
  - entity: sensor.mqtt_plant_moisture
    type: moisture

@c727
This would be a breaking change as existing users would have to migrate their existing configuration.
It's no problem to export the entity ids of the sensors as additional attribute like. As soon as we have a decision on the path we want to take here I can easily add a new attribute to the component:
```sensors : {"moisture":"sensor.mqtt_plant_moisture", ... }````

Hey @ChristianKuehnel , just wanted to check how you got on with the frontend build ? For info, I have pushed an update that has the "history" working if you click on one of the sensor icons. I used your suggestion of attrib.sensors : {"moisture":"sensor.mqtt_plant_moisture", ... } as a plant.py "patch" to test this. I am curious of your thoughts.

@PeteBa Just tried to set up the frontend development environment but I failed following the instructions: https://github.com/home-assistant/home-assistant/issues/10546
Anyway I just removed the group feature from this PR and added a new attribute "sensors" to it. This attribute will list all the sensors from which we're getting the data. This should allow you to display their history.
Please let me know if this is what you wanted to have.

@ChristianKuehnel , just tried your latest commit and I have access to the sensors which is great. Given that all of these options can work, I guess the main question really is which do you think best meets the goal ? I am happy to refine the existing card or to change it to a more-info card if you think that is better?
If we do go forward with the card then we would need to agree where things like icons/uom should get mastered (i.e. the sensor, the plant component or the front-end) as there is some duplication at the moment.

@ChristianKuehnel , sorry I think I was out-of-sync with your comments. If you have the front-end built via script/build_frontend and you can confirm that the three files ( src/components/ha-cards.html, src/cards/ha-card-chooser.html and src/cards/ha-plant-card.html) have all been updated as per the front-end PR then you should be seeing the plant-card. You may need to "clear cache" in Developer Tools (or with Chrome you can also go through a new Incognito tab which can also work). Let me know if it isn't coming up.

@PeteBa thx for the hint, now I got your new plant card working.
I like the plant-card the way it is now: You get a nice compact overview of the current values in the UI. And you even getting the history by clicking on the icons. I'm not sure what to show in a "more info" card...
Concerning architecture:

I would say the unit of measurement the plan component should read it from the sensors and forward it to the UI. The sensors are defining the units and so this should be the source.
The icons are "only" used for the visualisation and are not related to the sensors or the logic. So I would decide on these in the plant-card.

That being said, I just added 2 patches: one is adding the units as attributes, the other is removing the icon-related logic.

This can be merged when the one comment has been addressed.

@ChristianKuehnel , follow-on from above, does it make sense to publish both versions of brightness? It might be simpler, and cover off review comment, to just make brightness attribute the historic version or maybe rename max_brightness if you want it more explicit. I would then only display that rather than both in the front-end. (if people want the real-time version then they could refer to the underlying sensor history).
I saw that your _load_history_from_db function assumes that a brightness sensor has been configured but the schema has it as optional so this might cause an error if undefined. Worth checking.
My front-end PR was inadvertently merged before we had finalised things so I have raised a new PR here to continue. It supports the mastering of uom/icons as you suggest above. But needs the decision on brightness attribute name to finalise. Let me know your thoughts or any feedback.
Looks like we have a shot at getting this into the next release so let me know if you think we can finalise before Saturday.

Don't use unit_of_measurement as a dict. It is a standard attribute. If you want to pass a dict of units use another name - units_of_measurement for example

I just fixed all of the issues addressed in the comments of the last two days, except:
I did not remove the brightness value. I can't give you a real reason, it's just my gut feeling that it should stay there.
@PeteBa Thx for pointing out the issue with _load_history_from_db. I really missed that case.

@ChristianKuehnel , I'm trying to get max_brightness to trigger a " low problem" but having difficulty. Doc suggest that if max_brightness < CONF_MIN_BRIGHTNESS then "low  problem" but CONF_MIN_BRIGHTNESS isn't stored in READINGS array so isn't picked up in _check_min(). Chances are its just me missing something here.
I think the historical view really add value for brightness and wonder if it would be better than the real-time check for max as well. The thing I dont like about real-time checks for brightness and temperature is that they assume that the problem has gone away just because it is approaching night. I would want to know if either metric was outside limits during the CHECK_DAYS period as plant was under stress and probably still recuperating. I would be up for discussing but probably for a future PR ?

@PeteBa Thank you for finding yet another bug :sunglasses: I also fixed this one...
Concerning the question on checking the history for other values as well:
I have an email notification set up to tell me, if one of my plants is currently unhappy, so I do not really care about the history of the values:
- id: plantstatus
  trigger:
    platform: state
    entity_id: <entity ids of my plants>
    to: problem
  action:
    - service: notify.my_email
      data_template:
        message: >
          the plant {{trigger.entity_id}} has a problem:
          {{trigger.to_state.attributes.problem}}

          current values:
            Moisture: {{trigger.to_state.attributes.moisture}}
            Conductivity: {{trigger.to_state.attributes.conductivity}}
            Brightness: {{trigger.to_state.attributes.brightness}}
            Temperature: {{trigger.to_state.attributes.temperature}}
            Battery: {{trigger.to_state.attributes.battery}}
            Brightness: {{trigger.to_state.attributes.brightness}}

Would that also work for your use case?
The exception here is the minimum brightness, as there it does not really make any sense to check it against a minimal value, as it's supposed to be dark at night. But checking against a maximum value again makes sense: right now it's too bright and the plant should be moved. In that case I would get an email.
I also was thinking of a smarter way to model the requirements of the plants, e.g. if the moisture (or conductivity) was above A in the last B days, the plant should still be fine. Or if the integral over the light absorbed by the plant is above C its still fine. But that adds a lot of assumptions about the requirements of the plants. As I do not really have a good idea what plants really need, I'm not able to create such a model. (And that's also the reason, why I'm using these sensors in the first place :wink: )

@balloob I'm fine with the current solution, from my point of view this can be merged.

@ChristianKuehnel seems the tests for the db failed.

These kind of entities with a lot of separate relative data points could profit from the more-info-panel tabs approach we've discussed here.
Pointing back to that thread to gather some possible use-cases to explore and take into account.
https://github.com/home-assistant/home-assistant-polymer/issues/627

@MartinHjelmare thx for the hint, I did not check for the test results as all tests passed in my TravisCI instance.
It was a nasty sporadic failure of the test case, caused by the wrong "block_till_done" statement in the test case. I rand the test a several times now and the problem seems to be gone now.

Hmpf. The tests are still failing sporadically. So I guess this is some sort of concurrency issue between my component, hass and the database. The tests always work on my machine.
Does anyone have some hints one how to debug this problem?

@ChristianKuehnel , hey, for what it is worth I can confirm that the tests are also passing on my dev machine and in travis-ci on my github.
I wonder if there is a mix of things going on here, a few things to check:

Travis is highlighting a problem with the sqlalchemy query syntax. Not an expert on this but can you try changing the filter parameter to comma separated rather than using "and" as you might be picking up the python keyword. Default behaviour for filter is sqlalchemy and_:

query = session.query(States).filter(States.entity_id == entity_id.lower(), States.last_updated > start_date)).order_by(States.last_updated.asc())

If that doesn't fix thigs then the Recorder may not have recorded the three state changes and the query not returning anything.  Only thing I could suggest here comes from the recorder test suite (tests/components/recorder/test_purge.py) where a small pause, sleep(0.1), is used to give the recorder thread time to complete. Worth a try.

If you want to see if it is an intermittent problem then you can close/open the PR to trigger a travis build.

Hey @balloob , can you give some directions on how to debug/fix this sporadically failing build?

Hey @balloob , @pvizeli
can anyone of you point me in the right direction in debugging this randomly failing tests? There seems to be a concurrency issue when running the tests against the recorder. The failure only occures during tests on Travis, but never in production use or when testing on my machine...

Sorry for the confusion, I had messed up my branches...

@MartinHjelmare do you have any idea what to do with the flaky test here? Any idea on how to debug the issue?
The easy way would be: just  @unittest.skip the test case...


What will happen if a singleton service depends on a scoped service?

I am faced with a memory lead problem in my web api project,when i review the code,i find some singleton services depend on non-singleton service.Is it the key for the problem?

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


Unit_06 fix mentimeter question

There are still mentimeter questions in Unit 6. They need to be removed/embedded as images.

Done


CSO2 | Counter-Strike Online 2 shader issues artifacts and strange color

Remix 0.2.0
GF | RTX 3060 Ti
Game | Counter-Strike Online 2
CSO2 and Remix | logs files
cso2_report_log.txt refers to the game or launcher
cso2_report_log_1.txt refers to the game or launcher
launcher_d3d9.log refers to remix
NvRemixBridge.log refers to remix
CSO2_DocLog.txt CSO2 main game log

ORIGINAL

I don’t know why this happens in older versions, it didn’t let me start the game at all
For those who also want to do this, I will leave a link to the game here

Hello! Will you please test this on the latest release and let us know if the issue persists? Thank you!


flink: init at 1.3.2

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Please review my changes.

Looks good as far as I can tell.


Maze generator

Another generator that could be nice, a maze with a start and an end.

@BenjaTK  I have an old C++ project with maze generation, I can try to add this in my free time, I still need to figure out the git commands :D

@BenjaTK  I have an old C++ project with maze generation, I can try to add this in my free time, I still need to figure out the git commands :D

That'd be great!


Bug: PCWSTR argument gets turned into PWSTR

Which crate is this about?
windows
Crate version
0.43.0
Summary
In IDXCCompiler3::Compile, the parguments parameter in c++ looks like: _In_opt_count_(argCount) LPCWSTR *pArguments,, but gets turned into Option<&[PWSTR]> in the Rust. I would expect it to be mapped to Option<&[PCWSTR]> instead.
Ideally the use would look something like
let compiler: Dxc::IDxcCompiler3 = ...
let args = [w!("arg1"), w!("arg2")];
compiler.Compile(..., Some(&args), ...);

Instead, something like this is required:
let compiler: Dxc::IDxcCompiler3 = ...
let args = [w!("arg1"), w!("arg2")];
let args = args.map(|s| PWSTR::from_raw(s.0 as *mut _));
compiler.Compile(..., Some(&args), ...);

which feels very unsafe, though I think it's fine as long as the strings are all constants.
Toolchain version/configuration
Default host: x86_64-pc-windows-msvc
rustup home:  C:\Users\rkevi.rustup
installed targets for active toolchain
wasm32-unknown-unknown
x86_64-pc-windows-msvc
active toolchain
stable-x86_64-pc-windows-msvc (default)
rustc 1.65.0 (897e37553 2022-11-02)
Reproducible example
No response
Crate manifest
No response
Expected behavior
No response
Actual behavior
No response
Additional comments
No response

Good catch. Unfortunately the Win32 metadata drops the const-ness of the parameter, but I should be able to infer that from the fact that it is an input parameter.

Thanks for reporting. This has now been fixed (#2227) - here's an example:
https://github.com/microsoft/windows-rs/blob/3370b0d885975597b3f128ef263a03cac11f6426/crates/tests/const_ptrs/tests/test.rs#L17-L19


Duplicated errors when that() is reused for multiple should()

Bug Report

Q
A

BC Break
no?

Library Version
0.2.32

PHP version
7.4.32

Summary
Consider such configuration:
return static function (Config $config): void {
    $srcClassSet = ClassSet::fromDir(__DIR__ . '/src');
    $rules = [];

    $rectors = Rule::allClasses()->that(new ResideInOneOfTheseNamespaces('Codito\Rector\Money\Rule'));
    $rules[] = $rectors->should(new HaveNameMatching('*Rector'))->because('this is Rector convention');
    $rules[] = $rectors
        ->should(new Extend(AbstractRector::class))
        ->because('we need satisfy Rector\'s contract for rules');

    $config->add($srcClassSet, ...$rules);
};

Since result of the should() is a BecauseParser it does not allow multiple expectations for the same selection, I wanted to reuse result of that() to make 2 separate rules. Unfortunately, it does not behave as I expected.
Current behavior
For class that does not satisfy both rules (empty Codito\Rector\Money\Rule\Foo class) I get:
Codito\Rector\Money\Rule\Foo has 4 violations
  should have a name that matches *Rector because this is Rector convention
  should extend Rector\Core\Rector\AbstractRector because this is Rector convention
  should have a name that matches *Rector because we need satisfy Rector's contract for rules
  should extend Rector\Core\Rector\AbstractRector because we need satisfy Rector's contract for rules

How to reproduce

Fork codito/rector-money
Create empty class in src/Rule directory
Run make arkitect

Expected behavior
I would expect only 2 errors for such scenario:
Codito\Rector\Money\Rule\Foo has 2 violations
  should have a name that matches *Rector because this is Rector convention
  should extend Rector\Core\Rector\AbstractRector because we need satisfy Rector's contract for rules

Ideally, it would be great to be able to define rule like this:
return static function (Config $config): void {
    $srcClassSet = ClassSet::fromDir(__DIR__ . '/src');
    $rules = [];

    $rules[] = Rule::allClasses()
        ->that(new ResideInOneOfTheseNamespaces('Codito\Rector\Money\Rule'))
        ->should(new HaveNameMatching('*Rector'))
        ->andShould(new Extend(AbstractRector::class))
        ->because('we need to satisfy Rector\'s contract for rules and keep Rector naming convention');

    $config->add($srcClassSet, ...$rules);
};

and set multiple expectations for single rule.

Hi @Wirone thanks for this interesting issue, I have a little question.
If you write multiple expectations and a class violates them, Do you expect an error or more errors for that class?
Because if you expect only one error the message could be not useful for the user if we show only one single violation.
It's better to return multiple errors for the class with all the violations to understand well, what do you think?

@AlessandroMinoccheri it depends 😅 I believe there are scenarios when you would like to have multiple expectations but only one error if any of the expectations is not met (but print only those failed). For that "ideal" example, when there is no Rector suffix it could be something like:
Codito\Rector\Money\Rule\Foo has 1 violation
  should have a name that matches *Rector because we need to satisfy Rector's contract for rules and keep Rector naming convention

But when both expectation are not met, it could be:
Codito\Rector\Money\Rule\Foo has 1 violation
  should have a name that matches *Rector AND should extend AbstractRector because we need to satisfy Rector's contract for rules and keep Rector naming convention

Probably because should be defined better (shorter, like "it's a convention for rules"), but you get the point 😉
In general, I would like to avoid duplicating Rule::allClasses()->that(new ResideInOneOfTheseNamespaces('Codito\Rector\Money\Rule')). Since it's the same selector, IMHO it should be ready for reusing for different expectations. But currently the analysis result is invalid (2 out of 4 errors does not make sense because they mix expectations and explanations from different concerns).

We could make the class return from the that immutable, so that can be reused in different "shoulds".


Update rust to 1.72

I tried building this on my Macbook (aarch64-apple-darwin) and ran into some build issues
...
   Compiling utf8parse v0.2.1
   Compiling colorchoice v1.0.0
error[E0658]: use of unstable library feature 'stdsimd'
   --> /Users/edavis/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ahash-0.8.7/src/operations.rs:124:24
    |
124 |     let res = unsafe { vaesmcq_u8(vaeseq_u8(transmute!(value), transmute!(0u128))) };
    |                        ^^^^^^^^^^
    |
    = note: see issue #48556 <https://github.com/rust-lang/rust/issues/48556> for more information

error[E0658]: use of unstable library feature 'stdsimd'
   --> /Users/edavis/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ahash-0.8.7/src/operations.rs:124:35
    |
124 |     let res = unsafe { vaesmcq_u8(vaeseq_u8(transmute!(value), transmute!(0u128))) };
    |                                   ^^^^^^^^^
    |
    = note: see issue #48556 <https://github.com/rust-lang/rust/issues/48556> for more information

error[E0658]: use of unstable library feature 'stdsimd'
   --> /Users/edavis/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ahash-0.8.7/src/operations.rs:154:24
    |
154 |     let res = unsafe { vaesimcq_u8(vaesdq_u8(transmute!(value), transmute!(0u128))) };
    |                        ^^^^^^^^^^^
    |
    = note: see issue #48556 <https://github.com/rust-lang/rust/issues/48556> for more information

error[E0658]: use of unstable library feature 'stdsimd'
   --> /Users/edavis/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ahash-0.8.7/src/operations.rs:154:36
    |
154 |     let res = unsafe { vaesimcq_u8(vaesdq_u8(transmute!(value), transmute!(0u128))) };
    |                                    ^^^^^^^^^
    |
    = note: see issue #48556 <https://github.com/rust-lang/rust/issues/48556> for more information

For more information about this error, try `rustc --explain E0658`.
error: could not compile `ahash` (lib) due to 4 previous errors
warning: build failed, waiting for other jobs to finish...

It appears this unstable feature is stable as of 1.72 (cf. this discussion). This PR just bumps to that.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Qiskit just bumped the MSRV to 1.70. Qiskit supports some users whose security requirements limit the software they install. For this reason they won't bump the rust version again for several months. Because these crates need to be buildable with Qiskit, we need to follow Qiskit's MSRV.
I see that this error only occurs on some macs. (There are at least three people building this successfully on linux.) I suppose we can find another way to solve this. There are some Qiskit devs who had recent experience that might be relevant.

The direct dependency bringing in ahash is hashbrown. Maybe we can cap the hashbrown version.

The MSRV of rustworkx is currently less than 1.70. And it depends on hashbrown and ahash.
Can you build with rustc 1.70 using the versions of dependencies here:
https://github.com/Qiskit/rustworkx/blob/main/Cargo.toml
?

I'll add a small update that I think this is an issue for the 1.70.0-aarch64-apple-darwin target but not 1.70.0-x86_64-apple-darwin. By using the other toolchain I can successfully build and run (using x86_64 and Rosetta) on my Macbook.


Fix SQL injection in example 7

See https://github.com/goldcaddy77/warthog/blob/master/examples/07-feature-flags/src/feature-flag/feature-flag.service.ts#L28-L48

Closing, done.


Cannot mock json data

Cannot send json data in mock module

Due to the problem of transferring characters, fix this problem in the next version.


Additive refinement test fix

Small update to #5778 that fixes a problem revealed by a test failure.

@lilleyse, thanks for the pull request! Maintainers, we have a signed CLA from @lilleyse, so you can review this at any time.
I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.
I am a bot who helps you make Cesium awesome! Thanks again.


Universe.XYZ skin & domain added

Hi! What is your PR about?

[x] Add or edit a skin
[x] Add custom domain for your space
[ ] Add alias for migrate your space
~Add images for your space~ (deprecated) Add the image URL on the space settings directly
~Edit your space with GitHub?~ (deprecated) Please migrate your space to ENS https://docs.snapshot.page/spaces/migrate
~Create your space with GitHub~ (deprecated) Create your space with ENS instead https://docs.snapshot.page/spaces/create

@pabless Can you remove the logo? You can add the logo from the settings page directly, we don't use GitHub anymore for adding logo

Done


Updating core-amqp-  reactor connection scheduler

This PR is to test performance impact on Srikanta's change for Reactor Connection to use new scheduler. Hoping to improve performance.
DO NOT MERGE

/azp run java - servicebus - tests

/azp run java - servicebus - tests

/azp run java - servicebus - tests


Exposes class definition

Part of EPIC #222
As a developer, I want to access the class definition to gather information about it
Acceptance criteria:

The class definition is accessed from an instance or from the constructor
If the class was not created with gpf.define, null is returned
The class definition does not expose any methods / properties (for now)

Actually, this is not required to start with. It should remain internal and accessed on demand through dedicated APIs (such as getAttributes)


Create l10n_it.xml

Creation translation on italian

@Rudolfet Follow-up - all the UI settings are now in game, which require quite a few more translated strings!
see https://github.com/GMNGjoy/FS25_ContractBoost/issues/26 for more information.
Any help is appreciated!

Hi @GMNGjoy, i translate all in Italian's language, so you can add them on your mod in official's way 👍🏻 Please check up and verify syntax for avoid eventually errors. Also because my game (in ITA language) it's all missing l10n etc...
l10n_it.txt

Sorry for the delay. Thanks a lot @FirenzeIT for the help.


Suggest rule of thumb for what to do in practices vs. product teams

Tiny start to a "playbook" for practices.
As discussed, some other things this could document include:

example agenda and list of candidate topics
steps to create a practice Jira "board" via labels and saved filters

ah thanks for starting this!

I wonder if we can be even more explicit here, for instance we're converging on a few areas where we expect the practices to be more involved in:

Architecture / technical plan reviews
Important technology choices
Quality
Performance
Trying to think of what else we usually expect the practices to cover.


Feature | Support cmake and multiple files

Finished by:

https://github.com/16bit-ykiko/vscode-compiler-explorer/commit/2f27c36b0cc8fa883382e1c6292e3af989d78e9a
https://github.com/16bit-ykiko/vscode-compiler-explorer/commit/0ccaa96fc53e7db5a095fbd9a2da6d4ac9a4932d

Now, you can use cmake easily!


Testing Azure DevOPS Build Pipeline Changes

TBD

Codecov Report

Merging #114 into Dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              Dev     #114   +/-   ##
=======================================
  Coverage   87.51%   87.51%
=======================================
  Files          37       37
  Lines        3116     3116
  Branches       11       11
=======================================
  Hits         2727     2727
  Misses        378      378
  Partials       11       11

Impacted Files
Coverage Δ

...MSFT_EXOAcceptedDomain/MSFT_EXOAcceptedDomain.psm1
47.82% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


... not key value coding-compliant for the key ...

I am getting a bunch of warnings of the following type:
Ignoring user defined runtime attribute for key path [variable name] of instance of UIView. Hit an exception when attempting to set its value ...setValue:forUndefinedKey:  this class is not key value coding compliant for the key [variable name]
I see this for editable, emptyImage, floatRatings, fullImage, halfRatings and so on.
I have inserted a view controller to storyboard which has a view with custom class FloatRatingView.
I believe that I started to see it after changing the deployment target to iOS7. I have already searched the web, but I did not find a fast solution. I am happy to help if I understand the issue.

감사합니다


Do you take requests for your gallery ?

It would be great if Freemind works on this.

Have you worked with the Freemind code?
At first glance it looks like it has been adapted to work with different front-ends, so there is hope to make it work on TeaVM.  Given the highly graphical nature a Canvas is probably the best bet for rendering.
It would still be a substantial project.  If you or someone else from the Freemind team wants to start, be sure to read the TeaVM docs and post here for help.
You could also consider porting it to SnapKit, which would let it target desktop and web (via TeaVM) from one codebase: https://github.com/reportmill/SnapKit   The SnapKit author is a frequent poster on the TeaVM forums.

I haven't worked with FreeMind, I guess I misunderstood and assumed the frontend code would mostly work with TeaVM.
I always assumed the default UI is in Swing, there is also an Applet.


arrays.findLastIndex

Find the index of the last item that matches or -1 if there is no match.
Checklist

[x] implementation
[x] tests
[x] jsdoc

Details

References

_.findLastIndex()

Added in 0.27


Fix deadlocked engine in RPC

There's an issue where if you're busy handling an incoming rpc request, additional engine events will not be processed. this causes a deadlock essentially if you have nested RPC, since the incoming acks won't be processed, but also probably gums up plenty of other features of livekit...
this solution is probably not correct, but it works and i included an example. need help @typester !

Interesting. Will take a look!

The change you made (d7c8cdacf84b77e3711afe89254cf8cb7816f39b) seems like a good fix to me :+1:

What caught my attention in a different context is the await here: https://github.com/livekit/rust-sdks/blob/fea75571cfd021296525598a37752cc2f1fe55eb/livekit/src/room/mod.rs#L649
If we await at this point, engine_events will be processed one by one. To me, it seems more natural not to await here, but what was the intention behind this design?


Encrypt with expiry date and passphrase

Hi,
Is there any way to create a key with an expiry date and passphrase?
Many thanks!

Hi @alistairdyer this repo only has basic functionality and does not support expire date or passphrase. I recommend looking into using the openpgp package directly: https://golang.org/x/crypto/openpgp


Refactor install.sh to also write setup.csh

A the end of a successful installation, install.sh writes a setup.sh file in the installation path and directs users to source that file in order to define environment variables required for proper execution of caf and cafrun.
For users of C shell, install.sh should also create an alternative setup.csh with the C-shell translations of the bash shell statements in setup.sh.  Attached is a sample setup.csh provided by Bob Numrich.
setup.csh.txt

I would also like to examine ways to make sourcing setup scripts unnecessary. Part of this will inevitably depend on whether or not the user has root privileges, and where they select to install OpenCoarrays. Is this something you want to have done for the next release?


Move pinot-filesystem into pinot-common

We would like to start adding annotations to classes that are expected to be extended by the users. See https://github.com/apache/incubator-pinot/issues/4031.
#4063 added the annotations to pinot-common. However it turns out that we currently have pinot-filesystem as the base module (pinot-common depends on it). To be able to annotate filesystem related classes (which forms a big part of extensibility for Pinot) one option is to merge filesystem into common. (Other option is to move the annotations to filesystem or perhaps another module below filesystem, but both seem to be far from ideal.)
Compatibility considerations:

This change is backwards incompatible. Users explicitly extending pinot-filesystem will encounter compile-time failures. The fix would be to exclude pinot-filesystem dependency in the corresponding pom file. We could add this to next release's release notes (and/or bump up the version number so its more explicit).

Codecov Report

Merging #4155 into master will increase coverage by 0.12%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #4155      +/-   ##
============================================
+ Coverage      67.2%   67.32%   +0.12%
  Complexity       20       20
============================================
  Files          1037     1037
  Lines         51427    51427
  Branches       7198     7198
============================================
+ Hits          34559    34622      +63
+ Misses        14500    14424      -76
- Partials       2368     2381      +13

Impacted Files
Coverage Δ
Complexity Δ

...main/java/org/apache/pinot/filesystem/PinotFS.java
78.57% <ø> (ø)
0 <0> (?)

...va/org/apache/pinot/filesystem/PinotFSFactory.java
84.37% <ø> (ø)
0 <0> (?)

...java/org/apache/pinot/filesystem/LocalPinotFS.java
87.09% <ø> (ø)
0 <0> (?)

...a/manager/realtime/RealtimeSegmentDataManager.java
50% <0%> (-50%)
0% <0%> (ø)

...he/pinot/core/query/pruner/ValidSegmentPruner.java
57.14% <0%> (-28.58%)
0% <0%> (ø)

...er/validation/BrokerResourceValidationManager.java
25% <0%> (-25%)
0% <0%> (ø)

...pinot/core/operator/docidsets/OrBlockDocIdSet.java
84.9% <0%> (-13.21%)
0% <0%> (ø)

.../impl/dictionary/LongOffHeapMutableDictionary.java
81.81% <0%> (-10.91%)
0% <0%> (ø)

...mpl/dictionary/DoubleOffHeapMutableDictionary.java
72.72% <0%> (-10.91%)
0% <0%> (ø)

...n/java/org/apache/pinot/core/transport/Server.java
59.25% <0%> (-7.41%)
0% <0%> (ø)

... and 24 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 0328662...ebe33f0. Read the comment docs.


“Lightbulb” volume slider not working, but Apple remote volume works normally

Everything has been working great now that the new version of the plug-in has been released, except for my lightbulb volume slider in Home.app. Volume works fine with the Apple remote but not from the “brightness” slider. I can mute the TV from the slider, and when I adjust volume with the slider the TV will display the current volume, almost as if the slider is simply querying the TV and saying “display the current volume”. I’m working on an XBR-65X850D (2016). Physical setup is a soundbar connected via ARC to the appropriate HDMI 4 port, and TV configured to control the soundbar using CEC. I seem to remember reading somewhere that when using various HB tv plugins such as some of the LG ones, that these lightbulb volume sliders in the home app don’t work with sound output over ARC, so I was curious if this is just a limitation?

Figuring you'd probably ask, here is what the log looks like when I try to change volume with the slider:
[10/3/2021, 12:43:16 PM] [BraviaTVOS] Living Room TV Speaker: Volume: 31 (speaker)
[10/3/2021, 12:43:16 PM] [BraviaTVOS] Living Room TV Speaker: Mute OFF
[10/3/2021, 12:43:17 PM] [BraviaTVOS] Living Room TV Speaker: Volume: 35 (speaker)
[10/3/2021, 12:43:17 PM] [BraviaTVOS] Living Room TV Speaker: Mute OFF
[10/3/2021, 12:43:17 PM] [BraviaTVOS] Living Room TV Speaker: Volume: 37 (speaker)
[10/3/2021, 12:43:20 PM] [BraviaTVOS] [DEBUG] Living Room TV: Polling API...
[10/3/2021, 12:43:20 PM] [BraviaTVOS] [DEBUG] Living Room TV: {"id":1,"turnedOff":null,"result":[{"uri":false,"source":"application","title":"Application"}]}
[10/3/2021, 12:43:20 PM] [BraviaTVOS] [DEBUG] Living Room TV Speaker: {"result":[[{"target":"speaker","volume":37,"mute":false,"maxVolume":100,"minVolume":0},{"target":"headphone","volume":15,"mute":false,"maxVolume":100,"minVolume":0}]],"id":1,"turnedOff":null}
[10/3/2021, 12:43:30 PM] [BraviaTVOS] [DEBUG] Living Room TV: Polling API...
[10/3/2021, 12:43:30 PM] [BraviaTVOS] [DEBUG] Living Room TV: {"id":1,"turnedOff":null,"result":[{"uri":false,"source":"application","title":"Application"}]}

I did not understand exactly what the problem is. Can't you change the volume properly? Or is the display wrong?
Log shows nothing out of the ordinary

While using the Home app, I can’t adjust the TV volume using the volume slider (lightbulb).
While using the Apple Remote in control center, volume control works properly.
When I try to increase or decrease through the Home app, the on-screen volume of the TV pops up, almost as if I a command was sent to the TV that instructed the TV to display the current volume. If I took a video and posted it here would that help you?

Ah i understand. Can u post your config pls

{
"name": "BraviaTVOS",
"platform": "BraviaOSPlatform",
"debug": true,
"warn": true,
"error": true,
"extendedError": true,
"tvs": [
{
"active": true,
"name": "Living Room TV",
"ip": "<IP_ADDRESS>",
"port": 80,
"appName": "@seydx/bravia",
"manufacturer": "Sony",
"model": "Bravia",
"serialNumber": "00000000",
"refreshInputs": false,
"wol": false,
"oldModel": false,
"polling": 10,
"sheduledRefresh": 12,
"inputs": [
{
"name": "Xbox",
"identifier": "HDMI 2",
"source": "hdmi"
}
],
"apps": [
{
"name": "Netflix",
"identifier": "Netflix"
},
{
"name": "Disney+",
"identifier": "Disney+"
},
{
"name": "HBO Max",
"identifier": "HBO Max"
},
{
"name": "Prime Video",
"identifier": "Prime Video"
},
{
"name": "SlingTV",
"identifier": "Sling TV"
}
],
"displayOrder": [
"apps",
"inputs",
"channels"
],
"speaker": {
"active": true,
"output": "speaker",
"increaseBy": 1,
"reduceBy": 1,
"accType": "lightbulb"
},
"channels": [],
"commands": [],
"macros": [],
"remote": []
}
]
}

{
"name": "BraviaTVOS",
"platform": "BraviaOSPlatform",
"debug": true,
"warn": true,
"error": true,
"extendedError": true,
"tvs": [
{
"active": true,
"name": "Living Room TV",
"ip": "192.168.1.xxx",
"port": 80,
"appName": "@seydx/bravia",
"manufacturer": "Sony",
"model": "Bravia",
"serialNumber": "00000000",
"refreshInputs": false,
"wol": false,
"oldModel": false,
"polling": 10,
"sheduledRefresh": 12,
"inputs": [
{
"name": "Xbox",
"identifier": "HDMI 2",
"source": "hdmi"
}
],
"apps": [
{
"name": "Netflix",
"identifier": "Netflix"
},
{
"name": "Disney+",
"identifier": "Disney+"
},
{
"name": "HBO Max",
"identifier": "HBO Max"
},
{
"name": "Prime Video",
"identifier": "Prime Video"
},
{
"name": "SlingTV",
"identifier": "Sling TV"
}
],
"displayOrder": [
"apps",
"inputs",
"channels"
],
"speaker": {
"active": true,
"output": "speaker",
"increaseBy": 1,
"reduceBy": 1,
"accType": "lightbulb"
},
"channels": [],
"commands": [],
"macros": [],
"remote": []
}
]
}

Can u change speaker output to "headphone" pls and try again

So if I change to the audio setting for "Speakers" to 'TV Speakers', the lightbulb volume slider works fine!  But the minute I change it back to "Audio System', the volume slider doesn't work.
Again my setup is a soundbar connected to HDMI 4 which is my ARC port.

The Apple TV Remote widget does not use the TV API. Instead, it uses the IRCC command to increase (by +1) or decrease (by +1) the volume. The speaker in HomeKit uses the API to increase/decrease the volume to the target value
It seems that your TV can't handle it because it's connected via HDMI/ARC, which is strange because my sound system, which is also connected via HDMI/ARC, works without any problems. I think it must be related to the settings of your TV

I have the same problem

I never found a solution.  I see the comments by the other two users above me with the exact same issue.  Every few months when I had some free time, I tried a few things to see if I could get it to work.  I can't tell you how many times I deleted and re-added the TV trying to get it to work over the last year!  I gave up and ended up just turning off the "speaker" in the config.  Volume control still works properly using the Apple TV Remote in Control Center.  My best guess at this point is that the root of the issue is the age of my TV, which is an XBR-65X850D (2016 model).  I also have a brand new Sony OLED and both volume controls work properly, so my best guess is my older 2016 model just doesn't play nice with the light bulb slider in the Home app.  I'm hoping that eventually Apple will update the Home app to include TV controls within the Home app itself, instead of having to navigate to Control Center to use the Apple TV Remote.


Conventional middleware class requirements.

Fixes #11443.
I made a few changes here:

Changed the delegate example to use async/await to match the approach used in the middleware class.
Switched the example URL to use https and the template-generated default 5001 port for that.
Added an explanation of the requirements for a middleware class. All of these requirements are enforced by the hosting startup process, where exceptions are thrown if the requirements aren't met.
Moved the dependencies section up to below the requirements explanation I added. I think this follows on naturally.
Made the per-request dependencies section a child of the higher-level dependencies section.

TODO:
I don't know how to test the moniker ranges locally, so I couldn't update the note about InvokeAsync being available in ASP.NET Core 2.0+. Ideally, I'd like to know how to test this locally but alternatively, please make the relevant change. I imagine this being a different version of the relevant bullet for < 2.0, e.g.:

A public method named Invoke. In ASP.NET Core 2.0 or later, the name can also be InvokeAsync. This method must:

I don't know how to test the moniker ranges locally

Version the whole topic for 2.1+ (1.1 is about to go away, and 2.0 has already left the scene).
In the metadata above ms.author, place this line ...
monikerRange: '>= aspnetcore-2.1'

@guardrex Thanks for such prompt feedback. :rocket:
I've (hopefully) made the relevant changes, as requested.

Let's go ahead and not disturb cats OOF. 🏖


Add Cherish Sachdeva in Hacktoberfest Community

Thanks, EddieHub for guiding me through Open Source.

#644
This is the new pr.
Please can you close this pull request.
@csachdeva83 you don't need to create a new pull request, you could just add your changes, and commit them and it will show here. Thank you.


[GSSOC'23] Adding animations to the cards

Title: Implement Card Elevation for Enhanced Visuals
Description: The current cards lack visual depth and appear flat. To improve the user interface, add card elevation or shadow effects to create a lifted and 3D appearance. Apply appropriate CSS styles, such as box-shadow or gradients, to achieve the desired effect.

Hi @avinashkranjan  ,
I am a contributor at GSSOC'23 and would love to work on this issue. Please assign the issue to me

I want to work on this issue as a contributor.
Pleasure Assign so that I can show my skills under GSSoC'23.

Hello, I have already worked on this type of animation, so I'm good to handle this issue. please assign me this issue.
I'm GSSOC'23 contributor.

Go Ahead @mkswagger


fix: Copy scripts to lite and ultra-lite images

From 0.17.0, lite and ultra-lite images fail to start due to missing entrypoint script.
TODO:

[x] Test images

[x] lite
Container starts successfully, no further tests done.
[ ] ultra-lite
Fails to start. note: /scripts/init.sh has a bash shebang. alpine does not ship with bash ootb so fails to start.
possible fix: install bash during image build.
possible fix: change script to run with /bin/sh

fixes #531
License Agreement for Contributions
By submitting this pull request, I acknowledge and agree that my contributions will be included in Stirling-PDF and that they can be relicensed in the future under MPL 2.0 (Mozilla Public License Version 2.0) license.
(This does not change the general open-source nature of Stirling-PDF, simply moving from one license to another license)

Tried to bypass entrypoint and run init.sh manually
ultra-lite
Copying original files without overwriting existing files
cp: can't stat '/usr/share/tesseract-ocr-original/*': No such file or directory
Running Stirling PDF with DOCKER_ENABLE_SECURITY=false and VERSION_TAG=

lite
Copying original files without overwriting existing files
cp: cannot stat '/usr/share/tesseract-ocr-original/*': No such file or directory
Running Stirling PDF with DOCKER_ENABLE_SECURITY=false and VERSION_TAG=
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
External configuration file 'configs/settings.yml' does not exist. Using default configuration and environment configuration instead.

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v3.1.2)

10:51:09.793 [main] INFO  s.software.SPDF.SPdfApplication - Starting SPdfApplication v0.17.1 using Java 17.0.9 with PID 1 (/app.jar started by root in /)
10:51:09.797 [main] INFO  s.software.SPDF.SPdfApplication - No active profile set, falling back to 1 default profile: "default"
10:51:11.648 [main] INFO  o.s.b.w.e.tomcat.TomcatWebServer - Tomcat initialized with port(s): 8080 (http)
10:51:11.656 [main] INFO  o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-8080"]
10:51:11.659 [main] INFO  o.a.catalina.core.StandardService - Starting service [Tomcat]
10:51:11.659 [main] INFO  o.a.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/10.1.11]
10:51:11.758 [main] INFO  o.a.c.c.C.[Tomcat].[localhost].[/] - Initializing Spring embedded WebApplicationContext
10:51:11.761 [main] INFO  o.s.b.w.s.c.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 1900 ms
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
10:51:11.995 [main] INFO  s.s.S.config.EndpointConfiguration - Disabling remove-blanks
10:51:11.996 [main] INFO  s.s.S.config.EndpointConfiguration - Disabling url-to-pdf
10:51:11.997 [main] INFO  s.s.S.config.EndpointConfiguration - Disabling html-to-pdf
10:51:11.997 [main] INFO  s.s.S.config.EndpointConfiguration - Disabling extract-image-scans
10:51:11.997 [main] INFO  s.s.S.config.EndpointConfiguration - Disabling compress-pdf
10:51:11.997 [main] INFO  s.s.S.config.EndpointConfiguration - Disabling ocr-pdf
10:51:11.997 [main] INFO  s.s.S.config.EndpointConfiguration - Disabling pdf-to-pdfa
rateLimit=null
10:51:12.959 [main] INFO  o.s.b.a.e.web.EndpointLinksResolver - Exposing 1 endpoint(s) beneath base path '/actuator'
10:51:13.011 [main] INFO  o.a.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-8080"]
10:51:13.034 [main] INFO  o.s.b.w.e.tomcat.TomcatWebServer - Tomcat started on port(s): 8080 (http) with context path ''
10:51:13.059 [main] INFO  s.software.SPDF.SPdfApplication - Started SPdfApplication in 3.739 seconds (process running for 4.688)
Stirling-PDF Started.
Navigate to http://localhost:8080

May n

Done changes as part of a different commit sorry about the double up
appreciate the fix regardles!


Add aiosonic and onecache dependency

Description of changes

Added myself as maintainer
init aiosonic, A very fast Python asyncio http client, see: https://github.com/sonic182/aiosonic
init onecache, Python LRU and TTL cache for sync and async code, see: https://github.com/sonic182/onecache

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[X] sandbox = true

[ ] Tested, as applicable:

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

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage

8 packages built:
python311Packages.aiosonic python311Packages.aiosonic.dist python311Packages.onecache python311Packages.onecache.dist python312Packages.aiosonic python312Packages.aiosonic.dist python312Packages.onecache python312Packages.onecache.dist

[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[X] Fits CONTRIBUTING.md.

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

Hello, this is my first time contribution. I could use some guidance on correctly activating pytest and also some help on fixing formatting. I actually use aiosonic and I worked before with the maintainer with fixing bugs. I'm capable of helping maintain this package.

Hello @gador and thank you for your extensive and caring review!
I disagree on disabling tests that require network however. They only require local networking and disabling them is pretty much equal to no tests at all.

Hello @gador and thank you for your extensive and caring review!
I disagree on disabling tests that require network however. They only require local networking and disabling them is pretty much equal to no tests at all.

Not all tests are disabled. There is still a good number of tests which aren't skipped. You can check by applying those changes and watching the build log. I very much prefer some tests to no tests at all. This at least gives us a better chance to catch regressions caused by other packages (which get checked by nixpkgs-review)

I tried your suggestion with enabling __darwinAllowLocalNetworking = true;. This works and allows to more test to run on darwin. So I'm fine adding this again 👍

Great to hear. I'm on Linux by the way and I don't think the tests that require local networking need to be disabled for Linux either - I'd guess local networking is enabled by default on Linux, it's just Darwin that needs that line to permit local networking.

I tried your suggestion with enabling __darwinAllowLocalNetworking = true;. This works and allows to more test to run on darwin. So I'm fine adding this again 👍

Great to hear. I'm on Linux by the way and I don't think the tests that require local networking need to be disabled for Linux either - I'd guess local networking is enabled by default on Linux, it's just Darwin that needs that line to permit local networking.

Mmh, the tests had to be disabled on my system to not fail on NixOS (x86_64-linux)

I tried your suggestion with enabling __darwinAllowLocalNetworking = true;. This works and allows to more test to run on darwin. So I'm fine adding this again 👍

Great to hear. I'm on Linux by the way and I don't think the tests that require local networking need to be disabled for Linux either - I'd guess local networking is enabled by default on Linux, it's just Darwin that needs that line to permit local networking.

Mmh, the tests had to be disabled on my system to not fail on NixOS (x86_64-linux)

Hmm, thank you for the information and for the guidance so far.

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

8 packages built:

python311Packages.aiosonic
python311Packages.aiosonic.dist
python311Packages.onecache
python311Packages.onecache.dist
python312Packages.aiosonic
python312Packages.aiosonic.dist
python312Packages.onecache
python312Packages.onecache.dist

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 332808 run on aarch64-darwin 1

8 packages built:

python311Packages.aiosonic
python311Packages.aiosonic.dist
python311Packages.onecache
python311Packages.onecache.dist
python312Packages.aiosonic
python312Packages.aiosonic.dist
python312Packages.onecache
python312Packages.onecache.dist

Package looks good to me. Thank you for applying all those recommendations and your work!

Thank you @gador !


[Question] When will .net 7 preview images become available

When will .net 7 preview images become available for devcontainers?
Is there a work around?

As a follow-up, this will get you both versions currently.
  "features": {
    "dotnet": {
      "version": "7.0",
      "installUsingApt": false,
      "additionalVersions": "latest"
    },
}


Slip fix

Discovered this with real world data.  A "null" attribute was causing
Type check failed in assignment to $!name; expected Str but got Slip

Returning a Str type object in this case fixes this.

Looks good to me, thanks! :)


Fix debug flag

The debug flag is now fixed.
The following all work now:
 python -m safety --debug scan
 python -m safety --debug 1 scan
 python -m safety --debug true scan

Because of the way the click group works, we need to preprocess the args and call preprocess_args() directly before the click decorators for the cli() function.
Added 3 new tests which are passing.
https://linear.app/pyup/issue/SFTY-915/-debug-flag-is-broken

moved to https://github.com/pyupio/safety/pull/546

moved to https://github.com/pyupio/safety/pull/546


create scram users thru kafka-storage command

Description
Creates scram users thru kafka-storage command when target is KRaft and not Zookeeper
Fixes #1495
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Checked on a new installation, with dédicated KRaft nodes
Checklist:

[X] Any variable/code changes have been validated to be backwards compatible (doesn't break upgrade)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If required, I have ensured the changes can be discovered by cp-ansible discovery codebase
[ ] My code follows the style guidelines of this project
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] Any dependent changes have been merged and published in downstream modules

I just understood that I completly missed the point...
kafka-storage must be used only for a first admin user creation, when initializing kraft
Then, kafka-config must be used to create other users.
I put back this PR in draft mode and I'll work on a new version,


Segfault on MacOS in pdal::plang::Invocation::prepareData

I've built with python 3.10.4 and pdal 2.4.3 and when running a pipeline that opens a single COPC file and runs the following filter:
def filter(ins,outs):
    print('schema: ', schema)
    print('srs: ', spatialreference)
    print('metadata: ', metadata)
    outs = ins
    return True

if fails with a segfault that looks like it happens at https://github.com/PDAL/python-plugins/blob/9d4f9370c77f7eba9335b095b82e02299415e135/pdal/plang/Invocation.cpp#L180
I've put a std::out before that line and after the call returns:
PyObject * Invocation::addArray(std::string const& name, uint8_t* data,
...
    std::cout << "call PyArray_New" << "\n";
    return PyArray_New(&PyArray_Type, nd, dims, pyDataType, strides, data,
        0, flags, NULL);
}

PyObject *Invocation::prepareData(PointViewPtr& view)
...
        PyObject *array = addArray(name, (uint8_t *)data, dd->type(),
            view->size());
        std::cout << "addArray done" << "\n";

And I get this output:
call PyArray_New
zsh: segmentation fault  PDAL_DRIVER_PATH=`pwd`/venv/lib/python3.10/site-packages/pdal pdal pipeline

The segfault log is:
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000002e8
Exception Codes:       0x0000000000000001, 0x00000000000002e8

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [39379]

VM Region Info: 0x2e8 is not in any region.  Bytes before following region:<PHONE_NUMBER>25912
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->
      shared memory            7fffffff9000-7fffffffa000 [    4K] r-x/r-x SM=SHM

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libpdal_plugin_filter_python.dylib	       0x10f81534b pdal::plang::Invocation::prepareData(std::__1::shared_ptr<pdal::PointView>&) + 363
1   libpdal_plugin_filter_python.dylib	       0x10f814c2c pdal::plang::Invocation::execute(std::__1::shared_ptr<pdal::PointView>&, pdal::MetadataNode) + 44
2   libpdal_plugin_filter_python.dylib	       0x10f80049b pdal::PythonFilter::run(std::__1::shared_ptr<pdal::PointView>) + 331
3   libpdal_plugin_filter_python.dylib	       0x10f8005b8 virtual thunk to pdal::PythonFilter::run(std::__1::shared_ptr<pdal::PointView>) + 24
4   libpdalcpp.14.3.0.dylib       	       0x10c6e8ed6 pdal::StageRunner::run() + 70
5   libpdalcpp.14.3.0.dylib       	       0x10c6804b5 pdal::Stage::execute(pdal::BasePointTable&, std::__1::set<std::__1::shared_ptr<pdal::PointView>, pdal::PointViewLess, std::__1::allocator<std::__1::shared_ptr<pdal::PointView> > >&) + 1247
6   libpdalcpp.14.3.0.dylib       	       0x10c67f7f5 pdal::Stage::execute(pdal::BasePointTable&) + 655
7   libpdalcpp.14.3.0.dylib       	       0x10c65ee9a pdal::PipelineManager::execute(pdal::ExecMode) + 156
8   libpdalcpp.14.3.0.dylib       	       0x10c62356a pdal::PipelineKernel::execute() + 596
9   libpdalcpp.14.3.0.dylib       	       0x10c64f11c pdal::Kernel::doExecution(pdal::ProgramArgs&) + 34
10  libpdalcpp.14.3.0.dylib       	       0x10c64f005 pdal::Kernel::run(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > > const&, std::__1::shared_ptr<pdal::Log>&) + 177
11  pdal                          	       0x10bdccb2d App::execute(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > >&, std::__1::shared_ptr<pdal::Log>&) + 761
12  pdal                          	       0x10bdcc5e1 main + 207
13  dyld                          	    0x7ff80d312310 start + 2432

This happens regardless of a las or COPC reader being used.
Is there anything else that I can capture that might be helpful?

Is there any chance the Numpy that you are building the PDAL plugins against isn't the same one as you are running against? When I've had trouble on OSX with this stuff, that was ultimately the root cause of it.

I’ll check it out and let you know.

I wonder if this isn't fixed by #3. I was having some threading interaction issues with readers.copc and readers.ept and I sanitized the GIL responsibilities of these plugins in 1.3.0


metrics_5m lost one data

Hi :
In metric_full,there is one data at Tue Jul 18 19:39:00 GMT+08:00 2017,but metrics_5m lost one data at 7:35PM.  blueflood'log is following:
[2017-07-18 19:44:59,521 +0800] [INFO ] [BasicRollup conductor] [com.rackspacecloud.blueflood.service.RollupService:run 270] Scheduling slotKey metrics_5m,1579,48 @<PHONE_NUMBER>516 last collection time:<PHONE_NUMBER>686 last rollup time:<PHONE_NUMBER>456 isReroll: false
.....
....
[2017-07-18 19:44:59,743  +0800] [INFO ] [locator-fetcher-23] [com.rackspacecloud.blueflood.service.LocatorFetchRunnable:run 116] Number of locators getting rolled up for slotkey: [metrics_5m,1579,48] are 4611; isReroll: false
.....
....
[2017-07-18 19:44:59,743 +0800] [INFO ] [locator-fetcher-23] [com.rackspacecloud.blueflood.service.LocatorFetchRunnable:finishExecution 213] Successful completion of rollups for (gran,slot,shard) metrics_5m,1579,48 in 16890 ms
I query cassandra with cql
select * from "DATA".metric_state where key=48 allow filtering;
the result is that:
key  | column1                     |value
48    |metrics_5m,1579,A   |1500377949678
48    |metrics_5m,1579,X   |1500377949678
How can I find the root cause of this problem？
Thanks

hello

@42701618 , what version of blueflood are you using? Also, do you see any Write or Read timeout in the blueflood log from rollups?

hi

the version of blueflood is blueflood-2.0.0.

NO Write or Read timeout in the blueflood log from rollups

select column1,writetime(value)  from metrics_full  where key='*****************' order by column1  ;
1500379620000<PHONE_NUMBER>725000  Tue Jul 18 20:07:00 GMT+08:00 2017          Tue Jul 18 20:08:17 GMT+08:00 2017
1500379380000<PHONE_NUMBER>720000  Tue Jul 18 20:03:00 GMT+08:00 2017          Tue Jul 18 20:04:16 GMT+08:00 2017
1500379140000<PHONE_NUMBER>879000  Tue Jul 18 19:59:00 GMT+08:00 2017         Tue Jul 18 20:00:16 GMT+08:00 2017
1500378900000<PHONE_NUMBER>709000  Tue Jul 18 19:55:00 GMT+08:00 2017         Tue Jul 18 19:56:16 GMT+08:00 2017
1500378660000<PHONE_NUMBER>594000  Tue Jul 18 19:51:00 GMT+08:00 2017         Tue Jul 18 19:52:37 GMT+08:00 2017
1500378420000<PHONE_NUMBER>452000  Tue Jul 18 19:47:00 GMT+08:00 2017         Tue Jul 18 19:48:16 GMT+08:00 2017
1500378180000<PHONE_NUMBER>624000  Tue Jul 18 19:43:00 GMT+08:00 2017         Tue Jul 18 19:44:16 GMT+08:00 2017
1500377940000<PHONE_NUMBER>212000  Tue Jul 18 19:39:00 GMT+08:00 2017         Tue Jul 18 19:40:17 GMT+08:00 2017
1500377700000<PHONE_NUMBER>450000  Tue Jul 18 19:35:00 GMT+08:00 2017        Tue Jul 18 19:36:16 GMT+08:00 2017
1500377460000<PHONE_NUMBER>653000  Tue Jul 18 19:31:00 GMT+08:00 2017        Tue Jul 18 19:32:16 GMT+08:00 2017

select column1,writetime(value)  from metrics_5m  where key='*****************' order by column1;
1500378300000<PHONE_NUMBER>341001 ->> Tue Jul 18 19:45:00 GMT+08:00 2017        Tue Jul 18 19:55:10 GMT+08:00 2017
1500378000000<PHONE_NUMBER>325002 ->> Tue Jul 18 19:40:00 GMT+08:00 2017        Tue Jul 18 19:50:00 GMT+08:00 2017
1500377400000<PHONE_NUMBER>306000 ->>	Tue Jul 18 19:30:00 GMT+08:00 2017       Tue Jul 18 19:40:00 GMT+08:00 2017

hi @shintasmith


Node.js SDK - Ref docs needs to be improved

Our current ref docs need to be reviewed. Some outputs are not displayed in the good place.
For instance Type aliases FileID is displayed here :https://docs.dagger.io/current/sdk/nodejs/reference/modules/api_client_gen
A better place to display it could here:
https://docs.dagger.io/current/sdk/nodejs/reference/classes/api_client_gen.default/#file
The Client class is also renamed to default which doesn't make sens.
https://docs.dagger.io/current/sdk/nodejs/reference/classes/api_client_gen.default

From #4147

NodeJS reference name for the default client should be more explicit
Right now, the name of it is: default.
When I was doing some demo, I couldn't find the API for the client, because it was not shown, except under default which was not clear at all.
maybe defaultClient at least?

Our reference TS doc is way better than before: https://docs.dagger.io/reference/typescript/modules/api_client_gen
I think we can close this issue since it's a pretty old one and we can reopen a new one if we catch anything new.


How to get ref of the ScrollArea component?

I want to get a reference to the ScrollArea component, in order to obtain various information about the scroll position. I cannot use the supplied onScroll function. So how do I get a ref, as when I do this...
ref={scrollArea => this.scrollArea = scrollArea}

and try and get the I get scrollTop...
const scrollTop = this.scrollArea.scrollTop;

I get an error:

Uncaught TypeError: Cannot read property 'scrollTop' of null

I'm also wondering how to do exactly this. Thanks!

Get ref:
const scrollRef = useRef(null);  // or the pre-hook way
<ScrollArea ref={scrollRef}>

then scroll:
scrollRef.current.scrollArea.scrollBottom();


Feature-request: Use bootstrap alerts for alert blocks

In case bootstrap is used, alert-blocks should utilize the corresponding CSS classes.
 I'll be happy to help.

There is an existing and rudimentary extension for Boostrap that can be extended.


Autoprefix for all user agent

I'm working on the server-side rendering, my renderToString() is taking too much time (100 ms +).
So I have added some memoization. This memoization is taking the user-agent as a parameter.
Is it possible making radium apply the prefixes for a large number of browsers?
I would be able to remove the user-agent as a parameter of the memoization. This would increase my index.html size, but reduce the memory usage of my server. That's a trade-off I'm willing to take.

Yes, this is possible, as inline-style-prefixer does support it. inline-style-prefixer added a special API for this, prefixAll, and Radium could call that API if, say, you pass all as the userAgent.

Alright, so I'm not mistaking, that's something that's currently not supported by radium but you would accept a pull request to address it. I also have to address it at the material-ui level.
I will probably submit a PR.

Yes, I'd take a PR for this.

@oliviertassinari have you seen radium-plugin-prefix-all? This is what I use to solve this use-case.

The plugin, while nice for basic cases, is not quite ideal, because the prefixer isn't fully pluggable. It is used directly by keyframes, style, and media queries, so none of those would be affected by swapping the plugin.


Terraform CDK google Provider: API Reference not accessible

Hello,
I can't access the @cdktf/provider-google TypeScript docs and I hope you can help me
Thanks in advance
Niels
Test case

open https://constructs.dev/packages/@cdktf/provider-google/v/5.0.3?lang=typescript
Try to click "API Reference" in the sidebar
It is not clickable because it is rendered as paragraph:

API Reference

Testing environment:

Safari 16.2 on macOS 13.1
Google Chrome 109.0.5414.119 on macOS 13.1

(also tested in incognito mode without add-ons)

This looks like a rendering issue to me.


"WebGL is not supported" after switching from Electron Forge React

Describe the bug
I'm currently in the process of transitioning from the template from Electron Forge, React with Typescript, to using Electron Vite, as I've grown to like Vite better than Webpack.
A lot of config has been changed, but now it works - with one notable exception:
In my project, we use plotly.js (and therefore also react-plotly.js), which uses webgl under the hood. That worked perfectly before I made the switch, but for some reason, it now just shows me the blue message WebGL is not supported by your browser - visit https://get.webgl.org for mor info above the empty plot.

I have opened the url in the electron application, using location = 'https://get.webgl.org', and it works there, so I know the warning isn't shown because the webgl-api is unavailable.
I've also tested the following in the console, which seems to show that the webgl api exists and works as expected.

The message is created by plotly.js (source), but I can't seem to see what has changed, causing it to show this message.
Electron-Vite Version
1.0.25
Electron Version
24.6.2
Vite Version
4.4.2
Plotly Versions
// package.json
<EMAIL_ADDRESS>"^2.12.24",
<EMAIL_ADDRESS>"^2.6.0",
"plotly.js": "^2.24.3",
"react-plotly.js": "^2.6.0",

Validations

[X] Follow the Code of Conduct.
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Turns out, electron-vite wasn't the issue. My CSP was changed from "allow anything" to an explicit whitelisting, and for some reason plotly.js (the default version) used unsafe evals to initialize, so without a CSP containing script-src 'self' 'unsafe-eval';, it wasn't possible to run it. I remedied the problem by instead using plotly.js-strict-dist-min, as recommended here
This is the post that got me on the right track, btw.


Allow using partial words to match syntaxes. Fixes #340

This is compatible with the current configurations, but also supports using partial words for syntaxes.
Ex., to match any syntax with "JSON" in it:
"syntaxes": ["json"]

Pull Request Test Coverage Report for Build 752

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.006%) to 16.715%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

plugin/core/configurations.py
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

plugin/core/configurations.py
1
0.0%

Totals

Change from base Build 750:
-0.006%

Covered Lines:
459

Relevant Lines:
2746

💛  - Coveralls

Looks good, we can ignore the test coverage for now.
Forgive my inexperience, but why the '\b' surrounding each escaped string?

It means word boundary, so that if for instance I add [“c”] that won’t match Coffescript, only “C”

@tomv564, could you please merge this one in?
I'd like to start working in #349 now so I can get json/jsonc, c/c++/objective-c, css/scss/sass/less plugins ready. 😁

Thanks, sorry for the slow response!


[OpenAI] Added Missing Transcription WithResponse APIs

Added Missing Transcription WithResponse APIs
Refactored source code by adding a Utility class in the implementation folder for clean code.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-openai

I think that we should maybe do the split I mentioned to you, like

moving getRequestOpetionsForMultipartFormData to the MultipartDataHelper
As an idea: moving the AudioTranscription  and AudioTranslation static methods to their own AudioTranscriptionValidator and AudioTranslationValidator classes under the `implementation package.

WDYT?

I think it is a good idea. will update it soon.


Allow govukButton to be decorated

button elements can take id, name and value attributes, too.

Have you needed to do this?

Yup, shortly before I added this issue. I often use button values to change the status of a thing from draft to published, for example. Saves either creating a separate hidden input or updating the data in the POST route.


Added new fields to DataPoint

Looks like the API has 2 new fields that aren't accounted for.  I added them.

Thanks!


Please add support for Roborock S5

Device model
roborock.vacuum.s5
Device name
Roborock S5
Does the device require a MiCloud connection?
Do not know (But possibly yes)
Anything special about the device?
It doesn't work with the plugin as of now. However, I see that Roborock S5 MAX is already supported by the plugin so I guess we can safely use all the functions of Roborock S5 Max with this Roborock S5.
Thank you in advance and looking forward to your reply.

Roborock S5 support is already there. What is not working for you?

My Roborock S5 isn't working as well. When i tap on the robot in apples home app it just shows "no response". Restarted Homebridge several times but didn't worked for me yet. Do you have any idea what else I could try?

In order for me to have an idea what the issue might be you need to post your config.json entry and a homebridge debug log.

The Debug just shows a handshake error, see attached screenshot.
Config:
{
"bridge": {
"name": "Homebridge 2345",
"username": "",
"port": ,
"pin": ""
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 8581,
"auth": "none",
"theme": "amber",
"tempUnits": "c",
"lang": "de",
"loginWallpaper": "/homebridge/ui-wallpaper.jpg",
"platform": "config"
},
{
"platform": "TadoPlatform",
"name": "TadoPlatform",
"homes": [
{
"id": ,
"name": "Zuhause",
"username": "",
"password": "",
"polling": 30,
"temperatureUnit": "CELSIUS",
"geolocation": {
"longitude": "",
"latitude": ""
},
"presence": {
"anyone": false,
"accTypeAnyone": "OCCUPANCY",
"user": [
{
"active": false,
"name": "iPad",
"accType": "OCCUPANCY"
},
{
"active": false,
"name": "iPhone",
"accType": "OCCUPANCY"
}
]
},
"weather": {
"temperatureSensor": false,
"solarIntensity": false,
"accTypeSolarIntensity": "LIGHTBULB",
"airQuality": true
},
"extras": {
"centralSwitch": false,
"runningInformation": false,
"presenceLock": false,
"accTypePresenceLock": "ALARM",
"boostSwitch": false,
"sheduleSwitch": false,
"turnoffSwitch": false,
"childLockSwitches": [
{
"active": false,
"name": "Wohnzimmer ",
"serialNumber": ""
},
{
"active": false,
"name": "Wohnzimmer ",
"serialNumber": ""
},
{
"active": false,
"name": "Badezimmer ",
"serialNumber": ""
},
{
"active": false,
"name": "Küche ",
"serialNumber": ""
},
{
"active": false,
"name": "Schlafzimmer ",
"serialNumber": ""
}
]
},
"zones": [
{
"active": true,
"id": 3,
"name": "Wohnzimmer",
"delaySwitch": false,
"autoOffDelay": false,
"openWindowSensor": false,
"openWindowSwitch": false,
"airQuality": false,
"separateTemperature": false,
"separateHumidity": false,
"minStep": 0.5,
"minValue": 5,
"maxValue": 25,
"mode": "MANUAL",
"modeTimer": 30,
"easyMode": false,
"noBattery": false,
"type": "HEATING",
"boilerTempSupport": false,
"accTypeBoiler": "SWITCH"
},
{
"active": true,
"id": 1,
"name": "Badezimmer",
"delaySwitch": false,
"autoOffDelay": false,
"openWindowSensor": false,
"openWindowSwitch": false,
"airQuality": false,
"separateTemperature": false,
"separateHumidity": false,
"minStep": 0.5,
"minValue": 5,
"maxValue": 25,
"mode": "MANUAL",
"modeTimer": 30,
"easyMode": false,
"noBattery": false,
"type": "HEATING",
"boilerTempSupport": false,
"accTypeBoiler": "SWITCH"
},
{
"active": true,
"id": 2,
"name": "Küche",
"delaySwitch": false,
"autoOffDelay": false,
"openWindowSensor": false,
"openWindowSwitch": false,
"airQuality": false,
"separateTemperature": false,
"separateHumidity": false,
"minStep": 0.5,
"minValue": 5,
"maxValue": 25,
"mode": "MANUAL",
"modeTimer": 30,
"easyMode": false,
"noBattery": false,
"type": "HEATING",
"boilerTempSupport": false,
"accTypeBoiler": "SWITCH"
},
{
"active": true,
"id": 4,
"name": "Schlafzimmer",
"delaySwitch": false,
"autoOffDelay": false,
"openWindowSensor": false,
"openWindowSwitch": false,
"airQuality": false,
"separateTemperature": false,
"separateHumidity": false,
"minStep": 0.5,
"minValue": 5,
"maxValue": 25,
"mode": "MANUAL",
"modeTimer": 30,
"easyMode": false,
"noBattery": false,
"type": "HEATING",
"boilerTempSupport": false,
"accTypeBoiler": "SWITCH"
}
],
"telegram": {
"active": false
}
}
]
},
{
"platform": "Calendar",
"calendars": [
{
"name": "Müllabfuhr",
"url": "",
"pollingInterval": 5,
"offset": "-10h",
"sensors": [
"Gelber Sack",
"Restmüll"
]
}
]
},
{
"devices": [
{
"name": "LG OLED",
"host": "",
"mac": "",
"disableLogInfo": false,
"disableLogDeviceInfo": false,
"enableDebugMode": false,
"turnScreenOnOff": false,
"volumeControl": 1,
"switchInfoMenu": false,
"getInputsFromDevice": false,
"filterSystemApps": true,
"inputs": [
{
"name": "SAT TV",
"reference": "com.webos.app.hdmi1",
"type": "HDMI",
"mode": 0
},
{
"name": "Apple TV",
"reference": "com.webos.app.hdmi2",
"type": "HDMI",
"mode": 0
},
{
"name": "Xbox",
"reference": "com.webos.app.hdmi3",
"type": "HDMI",
"mode": 0
}
],
"pictureModeControl": false,
"brightnessControl": false,
"backlightControl": false,
"contrastControl": false,
"colorControl": false
}
],
"platform": "LgWebOsTv"
},
{
"name": "Govee",
"username": "",
"password": "",
"apiKey": "",
"lightDevices": [
{
"label": "Lightstrip",
"deviceId": "",
"enableBT": true,
"customAddress": "",
"brightnessStep": 1
}
],
"platform": "Govee"
},
{
"name": "Levoit Humidifiers",
"email": "",
"password": "",
"platform": "LevoitHumidifiers"
},
{
"name": "Yeelighter",
"timeout": 5000,
"interval": 60000,
"ctforcolor": false,
"blocking": false,
"split": false,
"override": [
{
"id": "0x00000000182b44e6",
"log": true,
"color": false,
"backgroundLight": false,
"separateAmbient": false,
"offOnDisconnect": true,
"colorTemperature": {
"min": 5000,
"max": 5000
}
}
],
"manual": [
{
"ignorePower": false
}
],
"platform": "Yeelighter"
},
{
"devices": [
{
"name": "Roboter-Staubsauger",
"ip": "<IP_ADDRESS>",
"token": "5172374f573771444649656a686e6666",
"deviceId": "118041519",
"model": "roborock.vacuum.s5",
"pollingInterval": 10,
"deepDebugLog": false,
"micloud": {
"username": "",
"password": "*",
"country": "de",
"forceMiCloud": false
},
"buzzerControl": false,
"ledControl": false,
"childLockControl": false,
"modeControl": false
},
{
"name": "Yeelight Deckenleuchte",
"ip": "<IP_ADDRESS>",
"token": "ab07b010991199abd1fee4e7acc193da",
"deviceId": "405488870",
"model": "yeelink.light.ceilc",
"pollingInterval": 10,
"deepDebugLog": false,
"buzzerControl": false,
"ledControl": false,
"childLockControl": false,
"modeControl": false
}
],
"platform": "miot"
}
],
"disabledPlugins": [
"homebridge-sonos",
"homebridge-pihole",
"homebridge-dummy",
"homebridge-apple-tv-remote",
"homebridge-ws",
"homebridge-harmony",
"homebridge-mqttthing",
"homebridge-webos-tv",
"homebridge-yeelight-wifi",
"homebridge-xiaomi-roborock-vacuum",
"homebridge-yeelighter"
]
}

A handshake timeout indicates that either your ip or token is incorrect.

Me personally the log said the device is not yet supported by the plugin.
I will try adding it once again this evening and let you know the result.

A handshake timeout indicates that either your ip or token is incorrect.

Alright, then I'll delete the robot and add it again. I got the Information via micloud.

@dweiden
The information in the cloud is not always up to date, so yeah re adding would be a good idea.
@Aekung probably you then have a different device?

@dweiden
The information in the cloud is not always up to date, so yeah re adding would be a good idea.

Tried but still the same issue. Cleared the cache already but will give it a try later again. Otherwise I'll extract the token by myself and try it again. Thanks for your help!

It might not necessarily be the token. Make sure also that the ip is correct and that you can ping the vacuum from your homebridge device.


[Submission]: PostgresSQL for Docker Desktop

Docker Hub repository name
agorinenko/docker-extension-postgres
Terms of services

[X] I accept the term of services

/validate

Hi @agorinenko, Docker Extensions are using SemVer convention for versioning, see docs here.
You should push a specific version, for example, "1.1.0" instead of "latest."
Thanks,
Ivan

Hello @ivan-curkovic ! I fixed the error and loaded the new version.
Thanks.

/validate

Hi @agorinenko, please validate the extension locally using the following command:
docker extension validate agorinenko/docker-extension-postgres:1.1.0
Here are the error messages:

level=error msg="(required) image label "com.docker.extension.categories" is set to empty string in the Dockerfile: https://docs.docker.com/desktop/extensions-sdk/extensions/labels/\n"
level=error msg="(required) image label "com.docker.extension.changelog" is set to empty string in the Dockerfile: https://docs.docker.com/desktop/extensions-sdk/extensions/labels/\n"
level=error msg="(required) image label "com.docker.extension.screenshots" is not a valid JSON array of objects: https://docs.docker.com/desktop/extensions-sdk/extensions/labels/\n"
level=warning msg="(optional) maybe image label "com.docker.extension.categories" should define at least 1 category"
level=error msg="the image for platform "linux/arm64" is not pushed to DockerHub: https://docs.docker.com/desktop/extensions-sdk/extensions/multi-arch/"
level=error msg="The extension "agorinenko/docker-extension-postgres:1.1.0" hasn't passed the checks to be published."

/validate

Closing as there's no activity. Feel free to reopen if this is active again


Archive this feedstock

Hey @SylvainCorlay (as the sole listed maintainer), are you still interested in this feedstock? It seems unmaintained and pops up as blocking in quite some migrations. Can we archive it until someone has the time to fix it again?

I pushed things forward quite a bit @xhochy. Is this still blocking things anywhere?

If all is running fine: no. scilab just appeared so often as a missing piece in migrations. Seems like all have been solved, thus closing this.


RAFD-3090: remove the directives

Please ensure all the directives which are getting removed and not tracked are tracked somewhere


Transfer from one exchange is not showing up on destiny exchange

Hi,
I made a transfer from an exchange, but I don't know if the transaction has completed or not. In the source exchange is showing a message that tokens were transfered, they are not in P2PB2B wallet, could you check where it is?

I can see the only transaction with such memo: https://stellar.expert/explorer/public/tx/128530375256698880#128530375256698881
Hope this helps.


add vendor

Will close it for now - it is outdated. If later decide to include vendor folder will create a new PR.


Timer Fix

Asana Task
Updates the countdown timer to be its own component. Previously, the timer was created by a series of recursive function calls that updated the timeLeft state variable. However, when the reset button was pushed, the recursion was not stopped. So, when a new code was generated on the same page, there were two recursive chains running, each updating timeLeft on top of each other. This is shown below with the interval between updates changed from one minute to one second.

Now that the countdown timer is its own component, on reset the component is unmounted so the timer disappears. Also lets the time updates be triggered by the useEffect hook, which avoids the recursion.
Now, with one second updates we get:

Just tested locally including hitting the time when the code expires and the message changes.  Looks good, merging to staging for further testing.


python312Packages.holidays: 0.57 -> 0.58

Diff: https://github.com/vacanza/python-holidays/compare/refs/tags/v0.57...v0.58
Changelog: https://github.com/vacanza/python-holidays/releases/tag/v0.58

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

10 packages built:

home-assistant-component-tests.holiday
home-assistant-component-tests.workday
python311Packages.holidays
python311Packages.holidays.dist
python311Packages.prophet
python311Packages.prophet.dist
python312Packages.holidays
python312Packages.holidays.dist
python312Packages.prophet
python312Packages.prophet.dist


Add Alt+w to copy current command to clipboard

Fixes #130

I'd love to get this merged - once the build error is fixed I'm happy to approve!

Hey @yuvipanda — any progress?

Hey @yuvipanda! This one has been open for quite some time now, so I'm going to close it. Happy to reopen if anything changes!

Sorry I haven't been able to follow up, @ellie! Closing it is the right thing to do for now


Migrate kdm, chart, system chart branch values to the new build system

One other change we need to check is the removal of ENV CATTLE_KDM_BRANCH=dev-v2.8 from Dockerfile.dapper.
This line is continually updated - the KDM branch.
https://github.com/rancher/rancher/blob/79bf51eb1ce0570915b18669a14044c2378dbfa3/Dockerfile.dapper#L16C31-L16C31
But looks like we later update it elsewhere - in package/Dockerfile and some of the scripts. It appears we may not need to set the value in Dockerfile.dapper.
We're trying to integrate the KDM branch with the new build system, so that it's not specified inline, but taken from outside as an ARG. Where do we explicitly run docker build with this dapper file?

As the changes in the build system will also affect the releasing of rancher-prime, we would like to have the release team review this PR as well.  cc @briandowns

@snasovich, thanks for the note, I didn't know about that, will check it out!

@briandowns, I updated the check-chart-kdm-source-values script for 2.9 and the new build system.
One thing to note is that the create-components-file.sh script creates the listing of chart/KDM sources with the variable names as they are written in the build.yaml file itself. It doesn't convert them to ENV_VAR case. Please let me know if that's OK. The output currently looks like this:
...
# Chart/KDM sources
* systemChartDefaultBranch: dev-v2.9 (`build.yaml`)
* chartDefaultBranch: dev-v2.9 (`build.yaml`)
* kdmBranch: dev-v2.9 (`build.yaml`)


React Router v4 Switch, getting 'Cannot read property 'classList' of null'

Hey, I'm trying to implement this with React Router v4 Switch, yet the app immediately fails with an error that says 'Cannot read property 'classList' of null'.
From doing a bit of debugging I saw that it fails on PageTransition.componentDidMount where it tries to load the DOM element for the Switch, which is null.
I am passing the location prop to the Switch.
Any idea?
Thanks!

Hm.. can you help me out by create an minimal example to reproduce the bug on https://codesandbox.io/? It would help me a lot to investigate the bug.
Also, what is your exact version of react router 4?


Apparel is not showing up in the movement type stats.

Extension was missing from Biomes! Islands.


[test] code coverage

RegistryLayoutRenderer .view should not be marked as covered by unit tests

Current coverage is 71.94%

Merging #1026 into master will increase coverage by +0.01% as of bd344d3

@@            master   #1026   diff @@
======================================
  Files          263     263
  Stmts        14830   14864    +34
  Branches      1611    1616     +5
  Methods          0       0
======================================
+ Hit          10668   10694    +26
  Partial        418     418
- Missed        3744    3752     +8

Review entire Coverage Diff as of bd344d3

Uncovered Suggestions

+0.09% via ...argets/FileTarget.cs#1918...1930
+0.09% via ...argets/FileTarget.cs#1555...1567
+0.08% via ...c/NLog/LogFactory.cs#180...191
See 7 more...

Powered by Codecov. Updated on successful CI builds.


⚠ Bofrost.fr has degraded performance

In 5761867, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1448 ms

Resolved: Bofrost.fr performance has improved in 2b47b17 after 1 hour, 1 minute.