Org test folders

Depends on: #7
What?
Join molecule tests into a single folder.
Why?
According to documentation each time then create a new scenario a new folder is created inside the molecule folder.
I thinks it's is good practice.
How?
Move all test folders to the molecule folder and make any necessary adjustments.

Perfect man!


修复兼容问题

#2760 #2763

Codecov Report

Merging #2766 into master will increase coverage by 0.32%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #2766      +/-   ##
============================================
+ Coverage     80.12%   80.45%   +0.32%
- Complexity     7084     7118      +34
============================================
  Files           145      145
  Lines         26728    26729       +1
  Branches       6383     6383
============================================
+ Hits          21417    21505      +88
+ Misses         3478     3387      -91
- Partials       1833     1837       +4

Impacted Files
Coverage Δ
Complexity Δ

...baba/fastjson/serializer/ASMSerializerFactory.java
96.05% <ø> (ø)
198 <0> (ø)
:arrow_down:

...ibaba/fastjson/serializer/SerializeFilterable.java
96.77% <100%> (+0.83%)
67 <1> (+2)
:arrow_up:

...com/alibaba/fastjson/serializer/SerialContext.java
72.91% <0%> (-4.17%)
19% <0%> (ø)

...om/alibaba/fastjson/serializer/ListSerializer.java
88.15% <0%> (-3.95%)
20% <0%> (-1%)

...com/alibaba/fastjson/parser/JSONReaderScanner.java
72.61% <0%> (-1.28%)
44% <0%> (-1%)

...libaba/fastjson/serializer/JavaBeanSerializer.java
83.14% <0%> (-0.23%)
189% <0%> (-1%)

...m/alibaba/fastjson/serializer/SerializeConfig.java
78.65% <0%> (+1.12%)
133% <0%> (+3%)
:arrow_up:

...om/alibaba/fastjson/serializer/JSONSerializer.java
86.89% <0%> (+1.94%)
80% <0%> (+8%)
:arrow_up:

.../main/java/com/alibaba/fastjson/util/ASMUtils.java
83.5% <0%> (+2.06%)
33% <0%> (ø)
:arrow_down:

... and 1 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 bdc0fe5...6281b76. Read the comment docs.


Cannot open /proc//mem on remarkable2, fw 3.3

I have just downloaded the latest release (0.6.4) and tried to run the client on the remarkable device, which exits with the following error:
2023/05/14 20:57:10 cannot open file: open /proc//mem: no such file or directory

I am running firmware version <IP_ADDRESS>6

... and the reason is, I was not running the binary with root provileges.


Adding "Akhil Rathipelly" in readme file

may i know who will merge the PR

may i know who will merge the PR

Hey, you need to have atleast 2 approvals from the maintainers & then your PR will be merged.


[Fix #767] Add header block support

Summary
This pull request fixes #767 by adding header block support to the slack.web.classes.blocks module as HeaderBlock.

⛑ Included a test that is based on the other block tests
🔍 Validated the text field as required with max length of 3000 characters
🔍 Validated the block_id field as optional
📐 Tried my best to match the ordering that the blocks were implemented (e.g. alphabetical or chronological)
📝 I did not find any documentation that needed to be updated, but please let me know if I missed a file!

Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Thanks for the review and help @seratch! Happy to make my first contribution to python-slackclient 🎉


Fuzz Test Failure in Counter.t.sol on zkSync with Foundry in Windows/WSL

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.0.2 (624cd93 2024-08-09T00:23:41.549447527Z)
What command(s) is the bug in?
forge test --zksync
Operating System
Windows
Describe the bug
When creating a new project and running the default test script on Counter.t.sol using the zkSync network with Foundry, the fuzz test fails due to an unexpected counterexample. This issue occurs specifically on Windows 11 using WSL (both Ubuntu 20.04 and 24.04). The same test script runs successfully on macOS.
Steps to Reproduce:

Create a new project in Foundry.

Use the default test script Counter.t.sol.

Run the fuzz test using the command: forge test --zksync -vvvv.

Observe the test failure with the following error:

test --zksync -vvvv
[⠊] Compiling...
No files changed, compilation skipped
[⠃] Using zksolc-1.5.1
[⠊] Compiling (zksync)
No files changed, compilation skipped
proptest: Aborting shrinking after the PROPTEST_MAX_SHRINK_ITERS environment variable or ProptestConfig.max_shrink_iters iterations (set 0 to a large(r) value to shrink more; current configuration: 0 iterations)

Ran 2 tests for test/Counter.t.sol:CounterTest
[FAIL. Reason: EvmError: Revert; counterexample: calldata=0x240f4157ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff args=[115792089237316195423570985008687907853269984665640564039457584007913129639935 [1.157e77]]] testFuzz_SetNumber(uint256) (runs: 0, μ: 0, ~: 0)
Traces:
  [37780] 0xbB19D84ecdC99Fe7C212B82f9B0B15EE6e852834::setUp()
    ├─ [0] → new <unknown>@0xc2E5d2d6D9d77E5C254DD4eE76b365143A188092
    │   └─ ← [Return] 32 bytes of code
    ├─ [0] 0xc2E5d2d6D9d77E5C254DD4eE76b365143A188092::setNumber(0)
    │   └─ ← [Return]
    └─ ← [Stop]

  [214] 0xbB19D84ecdC99Fe7C212B82f9B0B15EE6e852834::testFuzz_SetNumber(115792089237316195423570985008687907853269984665640564039457584007913129639935 [1.157e77])
    └─ ← [Revert] EvmError: Revert

[PASS] test_Increment() (gas: 8675)
Traces:
  [8675] 0xbB19D84ecdC99Fe7C212B82f9B0B15EE6e852834::test_Increment()
    ├─ [0] 0xc2E5d2d6D9d77E5C254DD4eE76b365143A188092::increment()
    │   └─ ← [Return]
    ├─ [0] 0xc2E5d2d6D9d77E5C254DD4eE76b365143A188092::number() [staticcall]
    │   └─ ← [Return] 0x0000000000000000000000000000000000000000000000000000000000000001
    ├─ [0] VM::assertEq(1, 1) [staticcall]
    │   └─ ← [Return]
    └─ ← [Stop]

Suite result: FAILED. 1 passed; 1 failed; 0 skipped; finished in 19.88ms (7.86ms CPU time)

Ran 1 test suite in 701.51ms (19.88ms CPU time): 1 tests passed, 1 failed, 0 skipped (2 total tests)

Failing tests:
Encountered 1 failing test in test/Counter.t.sol:CounterTest
[FAIL. Reason: EvmError: Revert; counterexample: calldata=0x240f4157ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff args=[115792089237316195423570985008687907853269984665640564039457584007913129639935 [1.157e77]]] testFuzz_SetNumber(uint256) (runs: 0, μ: 0, ~: 0)

Encountered a total of 1 failing tests, 1 tests succeeded

Expected Behavior:
The fuzz test should run without errors, as it does on macOS and regular Foundry without zkSync.
Actual Behavior:
The fuzz test fails due to an EvmError: Revert, identifying a counterexample that causes the test to abort.
Test Script:
function testFuzz_SetNumber(uint256 x) public {
    counter.setNumber(x);
    assertEq(counter.number(), x);
}

Additional Context:
This issue is specific to Windows 11 with WSL (Ubuntu 20.04 and 24.04).
The same command runs without issues on macOS.
The failure seems linked to the zkSync integration in Foundry.
System Information:
Operating System: Windows 11
WSL Versions: Ubuntu 20.04, Ubuntu 24.04
zkSync Version: zksolc-1.5.1

我也是这样

@cromewar could you try building from main or using one of the later releases: https://github.com/matter-labs/foundry-zksync/releases/tag/nightly-1cf88dc1e3118dadefdc823526b9f1966e5b98b5
We addressed an issue that was causing problems similar to yours so it might be related.


18573

Master list only says Russo staff and the Russo staff person's initials do not match the C.R listed in the RAPA.

Thanks for looking into this. I think it's Chrissy Rad, our aquatics coordinator.


is there any tutorial for making own scripts?

also slider for the brightness control would be nice

There is a wiki (see "Wiki" tab on the main page) documenting the Lua API. There are also example scripts already in the repository. I don't think there is a need for much more since it's all pretty basic. What are you struggling with?
As for brightness control, this isn't supported by any of the motherboards.

I'm closing this issue as the question has been answered. If you need any further help, please comment (unless it's a different problem, in which case, open a new issue or start a discussion - see 'Discussions' tab).


Examples should use current rule types

Takes the suggestion of Issue https://github.com/istio/istio/issues/5604 to use the new rule format in the istioctl usage examples.
This updates the CLI usage text but not https://istio.io/docs/reference/commands/istioctl.html .

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

Needs approval from an approver in each of these files:

istioctl/OWNERS [ayj]

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

@esnible: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
b59b03fdfe58092b5bf4dd1ab9e044c105ea1c60
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


fix: input type for uintN[], N > 51

Proposed Changes

Input types for large uintN[] are bigint | number[]. This PR fixes it so it's correctly bigint[] | number[]

Fixes #118

Is this something that would go to just bigint[] once the sdk is completely converted over?

Is this something that would go to just bigint[] once the sdk is completely converted over?

There's no plans to change this for the generated client. Newer features in algokit such as AlgokitComposer and the upcoming ARC56 app client will enforce usage of BigInt, but no breaking changes will be made to these ARC32-based generated clients.

Release in 3.0.6


Slow startup time running a Blazor app from the command line

I’m seeing exceptionally long startup times for 0.9.0 Blazor apps that I run from the command-line (~12sec).
SDK version: 3.0.100-preview3-010404
Blazor templates version: 0.9.0-preview3-19128-02
Repro steps:

dotnet new blazor
dotnet run

On my machine it takes ~10-12sec before the Blazor dev server starts up.
If I instead do  dotnet blazor serve bin\Debug\netstandard2.0\dist the app starts up in just a second or two.
I'm seeing similar slow startups for other project types, including console and empty web projects, on the order of 3-5sec, but Blazor stand-alone projects seem to be especially slow to start.

Is this really a bug?
It does take ~10s on my machine to do the first build-and-link. Subsequent builds of the same project only take a couple of seconds (on my machine). The subsequent faster builds rely on the Razor Compiler staying in memory and some parts of the build process not having to repeat.
AFAIK, this is no different from how it was in 0.8.0 or before. And is not really a problem because it's only the first build for a given project.

This was reproducing for me consistently on the first blazor project I created with the new bits, but after forcing a non incremental build (dotnet build --no-incremental) the problem went away. Subsequent runs only take about 4-5sec on my machine. The time delta does match up with the amount of time or takes to run the linker.   I can only repro this now on the first build of new projects. If we've always been this slow on first run then I think we can close this one as I can't reproduce the original issue anymore.

OK, let's close then!


Permission name for SSO should be hash

Defintion of done:

[ ] permission name used in loginwithapp() in id.tonomy contract should be hash(ecosystem namespace (e.g. id.tonomy + appp name + permission requested (e.g. "main" or "mobile) + parent?)

this is to ensure unique, determinant permission names across all apps and the way apps will use them

@theblockstalk Does this directly help with the Tonomy I.D SSO to MVP stage? How important is this?


Numpy backend implementation of rnn + cleanup of rnn tests

Summary
Update of Numpy backend to follow the actual Keras api for backend.rnn.
Related Issues
As per @gabrieldemarmiesse's request in https://github.com/keras-team/keras/pull/11499
PR Overview

[(y)] This PR requires new unit tests [y/n] (make sure tests are included)
[n] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[y] This PR is backwards compatible [y/n]
[n] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

Thanks a lot for the PR! We'll also be able to add your implementation in the documentation (see: #11507). I'll review tonight I think.
Could you add {{np_implementation}} at the end of the rnn docstring in the TF backend? This will display the numpy implementation of rnn in the docs. See #11507 if you don't see what I mean.

Also, we currently have a lot of flaky tests on travis. So I'll be able to review, but the merging might be delayed as only @fchollet can merge PRs which have a failing build.

I only had the time to check the numpy rnn and the check_rnn_operation. Both look good. I'll continue reviewing later on.

Great, I'll complete it shortly. (Note to self) just saw that constants are not used in the for loop! Will fix and improve test coverage (!?).

A test for that would be welcome indeed. Thanks!
On Tue, 20 Nov 2018, 23:34 Anders Huss<EMAIL_ADDRESS>wrote:

Great, I'll complete it shortly. (Note to self) just saw that constants
are not used in the for loop! Will fix and improve test coverage (!?).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keras-team/keras/pull/11622#issuecomment-440453408,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMS2K7nMxiTDZ4URl0mx2hYBU-xrRpmdks5uxIN6gaJpZM4YZhmx
.

@gabrieldemarmiesse Made remaining changes according to decisions, including a test for constants. Should be ready to go.

Thanks for the update, I'll review tonight.

Thanks, pushed simplification according to "final comment".

@gabrieldemarmiesse failing tests are not due to this PR, it should be good to go.

Sure, we have some issues with flaky tests on travis. See #11660 and #11521 . Github prevents me to merge PRs which have a failing build. Only @fchollet can do it. So either we wait for @fchollet to merge your PR, either we wait for the two PRs which are fixing the flaky tests to be merged.
Sorry about that, it's really slowing down progress on this repo for everyone.

Thank you for the PR! It's very helpful!


Added an example GaussianModel notebook and bunch of related fixes

Have added an example notebook. There seems to be some issue with denormalizing the values or order of the values. Will look into it

cool thanks... will take a look today.


add user-risk-profile commands

Add user risk profile commands, a couple of design choices in the comments

Do we want to include user_risk_profiles as their own command group? Or should risk_profiles but a subcommand of a broader users group (which would include all other user commands)?

Do we want to include user_risk_profiles as their own command group

I'm fine with keeping risk profile commands under the users subcommand like the code42cli. We can keep it a separate file though and just import them into incydr.cli.cmds.users.py

Cool, I'm writing the users commands right now but I'll plan to move these into there eventually.

Failing tests due to outdated output formatting in earlier command groups


New CDK version released: v1.89.0

A new version of CDK has been released! :tada:

Version: v1.89.0
Release: https://ift.tt/3rF4cXo

@mrgrain Please release a new version of @mrgrain/cdk-esbuild

released


Add post

Please add this post: (Thanks so much!)
Post URL: https://medium.com/@ly.lee/low-power-nb-iot-on-stm32-blue-pill-with-apache-mynewt-and-embedded-rust-cef5a3ecdd90?source=friends_link&sk=e232e68dc7c91dd4397e96d7dbde543a
Blog Homepage: Low Power NB-IoT on STM32 Blue Pill with Apache Mynewt and Embedded Rust
Author Name: Lup Yuen Lee
Categories: one or more of: Embedded

Published in 4c028c8


Add contact info items

Added map point link https://github.com/ticial/homepage/commit/38ef88331184fed9c4992a82ffea1b44628e0118

Added link to binary-studio on Linkedin - https://github.com/ticial/homepage/commit/effd540a961b8a2d1625c13979eab52e1bf3e3b0


No more position for HmIP-HDM2 (cover)

I agree to the following

[X] I have read the documentation
[X] I am aware of the latest release notes
[X] The Backend (CCU/Homegear/...) is working as expected and connected devices are controllable by its own UI.
[X] I am running the latest version of the custom_component (and Home Assistant)

The problem
Since the last update (unfortunately I updated homeassistant, hahomematic and raspberrymatic at the same time)
I can no longer the the current status from my blinds (HmIP-HDM2) in HomeAssistant.
However, the control from HomeAssistant still works.
In RaspberryMatic, values for the position of the blinds are still displayed (between 0.0 (closed) and 1.0 (open).
Current attributes from cover (Developer tools -> Entity -> Attributes:
interface_id: raspberrymatic-HmIP-RF
address: 0000C882BE01E3:1
model: HmIP-HDM2
entity_type: custom
value_state: restored
friendly_name: plissee_flur_rechts
supported_features: 11

State: unknown.
Do you have any idea what's going wrong here? I can't find anything related in the logs.
What version of HomematicIP (local) has the issue?
1.39.2
What was the last working version of HomematicIP (local)?
unknown
What type of installation are you running?
Home Assistant OS
What type of installation are you running for your homematic backend?
RaspberryMatic Standalone
Which version of your homematic backend are you running?
<IP_ADDRESS>30626
What hardware are you running for your system?
Proxmox
Which config details do you use

[X] Username and password
[ ] TLS
[ ] callback data (see)

Which interfaces do you use?

[X] Homematic IP
[ ] Homematic (Bidcos-RF)
[ ] Groups (Heating-Group)
[ ] BidCos-Wired (HM-Wired)

Diagnostics information
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response

value_state: restored  means that HA was not able to fetch data from CCU or has not received data since last restart.
I don't own a HmIP-HDM2 so i cannot test it by my self.
Enable debug logging for this integration, change values for your device in CCU.
Check the value_state of the cover entity again. Should be valid now.
If not, download the full log from HA and add it here as file.
Try to remember the last working version of integration. There has been no change for cover related code for 3 month!

Additionally search for more entities with value_state: restored.
In that case there is another root cause.

Thanks for your fast reply.
Issue was fixed with homeassistant 2023.7.3


Add extra cgroup mounts for bosh-lite environments

When deploying onto a bosh-lite environment using a persistent disk I am unable to execute:
docker run hello-world

However adding the extra code (my mish-mashed understanding of configuring cgroups - apologies) contained in the PR it executes successfully.

Hi @cagiti
The PR itself works. Is there a way to make it a bit more generic?
We have tried to do it in https://github.com/cloudfoundry-incubator/docker-boshrelease/commit/e24cc90990895784b9045307ff4c41ac207af202 but it didn't work

Hi @alex-slynko
I'll have a quick look and push another commit up. Thanks

@alex-slynko: I've refactored based off the commit you shared, which was successful when executing on bosh-lite. As a result, I was able to remove the extra cgroups I'd added in my PR.

Is anyone able to check this PR please?

hey @cagiti I'm testing out the PR and I can't get my worker to start. It fails with:
Failed to start ContainerManager open /sys/fs/cgroup/memory/name=/kubepods/cpuset.cpus: no such file or directory

Thanks @youreddy, are you able to give me some information on your environment. What stemcell and manifest are you using? Thanks

@cagiti We have deployed it with cfcr.
We used this script https://github.com/cloudfoundry-incubator/kubo-deployment/blob/master/bin/deploy_cfcr_lite but changed the docker bosh release to the latest.
This is what we saw in output.

@alex-slynko & @youreddy : I've made another change which should return the expected behaviour for non bosh-lite environments, but also should allow successful execution on bosh-lite.

Hi @cagiti
Could you please try to deploy CFCR with your changes.
To do that, clone kubo-deployment, upload your current docker release, go inside that repo and run ./bin/deploy_cfcr_lite -o ../docker-boshrelease/manifests/operators/dev.yml.
It should work on the local bosh-lite.

Hi @cagiti
It fails with the same issue you are trying to fix.
I'll check later the initial change and maybe we will go with it for now.

Hey @cagiti
I tried it locally. It fails when I do bosh -d deployment restart

@alex-slynko : I've pushed another couple of commits which I've verified locally and tested with a local deployment of CFCR which relies on https://github.com/cloudfoundry-incubator/kubo-deployment/pull/367. You can execute CFCR with the following command:
./bin/deploy_cfcr_lite -o ../docker-boshrelease/manifests/operators/dev.yml -o manifests/ops-files/dev.yml

@alex-slynko or @youreddy: are you able to revisit this change please? Thank you in advance 👍

Hi @cagiti
We tried deploying cfcr on bosh-lite using your PRs, and it successfully deployed.
We left a couple of comments on your PR for CFCR, but we'll merge this PR in the meantime.
Thanks,
Iain & @bu3


Set Gravity

How to set Gravity to MaterialSimpleListItem ?
and How to set size to icon?

Explicit gravity isn't supported. It will automatically go to RTL on devices which are using RTL languages (on API 16+).
The size is static and from the Material Design specs. "@dimen/md_simplelist_icon

I want to set gravity for MaterialSimpleListItem.there is no method to set gravity for this item:
adapter.add(new MaterialSimpleListItem.Builder(this)
<EMAIL_ADDRESS>.icon(R.drawable.ic_account_circle)
.backgroundColor(Color.WHITE)
.build());
if possible i need to set
.contentGravity(GravityEnum.CENTER)
to the above builder.
another thing to say, I have set android:supportsRtl="false" in manifest of my app and i need this case to be false.

any Help?
are you going to add this in next update or i should handle it?

@AlirezaGhanbarinia Do you find the workaround for setting gravity? I also need to change the gravity of the simple list from start to center


Fix: RAG not working

Issue #, if available:
#133
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closes #134


Portal: after user types in an existing label, he must select again, otherwise reverts to Empty

When user creates a new KV on Portal, after he/she types in an existing label, the user must select the label again with mouse, otherwise the label would revert to Empty by default, hence causing user miss-config potentially.

User types in an existing label, now he/she must select again with mouse:

Otherwise it would revert to Empty:

Imaging the user types in "L1" and click "Apply" immediately, we would create a new KV with empty label.

This is fixed in the portal update this week.


fix: add more social issues as to allow for fair representation

Description
We have a problem with code-as-activism that it frequently doesn't fairly represent minority and underprivileged populations. By focusing exclusively on one facet of the overwhelming struggle against the collective oppression of humanity, we risk losing perspectives which will ultimately help us all.
Motivation and Context
Code-as-activism can be so much more than one single issue. We should strive to enumerate as many social issues as we can to help bring their attention to AWS customers.
Breaking Changes
The only thing it breaks is code for fascists.
How Has This Been Tested?

[X] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[X] I have tested and validated these changes using one or more of the provided examples/* projects

[X] I have executed pre-commit run -a on my pull request

thank you for the PR, but at this time we won't be making any further changes related to cluster conditional creation


Fix display for context menu

This PR is to fix the wrong display for context menu. The reason this occurs is because display was overwitten by style of fomantic component, specifically the following rule
.ui.comments .comment .actions a {
    cursor: pointer;
    display: inline-block; // should be block
    margin: 0 0.75em 0 0;
    color: rgba(0, 0, 0, 0.4);
}

Before:

After:

I think the root problem is aria.js is too hacky, we can avoid using a here, I will propose new PR to avoid making the problem more complex.

See  Fix incorrect display for comment context menu #23343
Actually I had a TODO there  "in the future there could be a special CSS class for it". that TODO would help similar problems in the future.

Closed as #23343 fixed the root problem


python3Packages.pytikz-allefeld: init at unstable-2022-11-01

Description of changes
My thesis needs some nice figures, please help me making them reproducible.
I'm not using the name pytikz, since there already is a different package on pypi using that name.

Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Rebased on master
@ofborg build python310Packages.pytikz-allefeld python311Packages.pytikz-allefeld

@ofborg eval


Update with more models

https://app.endpoints.anyscale.com/explorer now lists:

I only have these currently:
https://github.com/simonw/llm-anyscale-endpoints/blob/86f395560530374da237092a500fa06b2022faeb/llm_anyscale_endpoints.py#L4-L10
Would be better if the plugin could retrieve the list from somewhere.

Full list of models: https://docs.endpoints.anyscale.com/category/supported-models

I tried Meta-Llama/Llama-Guard-7b but got this error:

endpoints llm -m Meta-Llama/Llama-Guard-7b hello
Error: rayllm.common.models.PromptFormatDisabledError: This model doesn't support chat completions. Please use the completions endpoint instead. (Request ID: TImvQaY61Ge0wkfMmPV56zDPFJh1_pUHjBJI9_0UYOU)

Mixtral really is very good:
llm -m mistralai/Mixtral-8x7B-Instruct-v0.1 \
  'Write a Python function that accepts a URL to a CSV file, downloads it and loads it into a SQLite database, creating a table with the correct columns'

Here's a Python function that accomplishes the task you described, using the requests, csv, sqlite3, and io libraries:
import requests
import csv
import sqlite3
from io import StringIO

def download_csv_to_sqlite(url):
    # Download the CSV file from the URL
    response = requests.get(url)
    response.raise_for_status()

    # Load the CSV data into a StringIO buffer
    csv_buffer = StringIO(response.text)

    # Connect to a new SQLite database in memory
    conn = sqlite3.connect(":memory:")

    # Create a new cursor for executing SQL commands
    cursor = conn.cursor()

    # Read the first row of the CSV file to determine the column names
    csv_reader = csv.reader(csv_buffer)
    columns = next(csv_reader)

    # Create a new table in the SQLite database with the correct columns
    column_defs = ", ".join([f"{col} TEXT" for col in columns])
    cursor.execute(f"CREATE TABLE csv_table ({column_defs});")

    # Insert the remaining rows of the CSV file into the table
    for row in csv_reader:
        value_defs = ", ".join(["?" for _ in row])
        cursor.execute(f"INSERT INTO csv_table VALUES ({value_defs});", row)

    # Commit the changes and close the connection
    conn.commit()
    conn.close()

# Example usage
url = "https://example.com/data.csv"
download_csv_to_sqlite(url)

This function downloads the CSV file from the given URL, loads it into a SQLite database in memory, creates a new table with the correct columns, and inserts all the rows from the CSV file into the table.
Note that this function uses an in-memory SQLite database for simplicity, but you can modify it to use a persistent database file if needed. Also, the function assumes that the CSV file contains text data, but you can modify it to handle other data types as necessary.


Add support for terraform 0.13

Fix terratests idempotency check by doing it manually and irgnoring output changes
Add support for terraform 13
Prepare 0.4.0 release
Try to reduce number of output changes detected by terraform 0.13
Add module_tags support

irgnore changes in outputs for now.. can't find the source..

[ch1106]


Implement shouldForwardProp for React Native/Primitives

Tested with react-figma (with styled-components/primitives). Should work with React Native, but would be great if someone could test it before merging 🙂.
I had to do npm i -D bundlesize jest in the package folder. Should I commit the package.json with them as local dependencies? I try to avoid global dependencies where possible (to avoid version mismatches between packages, and make sure people have up-to-date versions).
fixes #3093

I copied this test over from the web entrypoint tests, but it fails, not sure if it's because of the use of findByProps, or test renderer doesn't work for children in React Native? Bit strange, should be fine to leave it out though
    it('should inherit shouldForwardProp for wrapped styled components', () => {
      const View1 = styled.View.withConfig({
        shouldForwardProp: prop => prop !== 'color'
      })`
        background-color: ${({ color }) => color};
      `;
      const View2 = styled(View1)``;
      const wrapper = TestRenderer.create(
        <Fragment>
          <View1 color="red" id="test-1" />
          <View2 color="green" id="test-2" />
        </Fragment>
      );
      const view1 = wrapper.root.findByProps({ id: 'test-1' });
      const view2 = wrapper.root.findByProps({ id: 'test-2' });

      console.dir(view1.props);
      expect(view1.props.style).toEqual([{ color: 'red' }]);
      expect(view2.props.style).toEqual([{ color: 'green' }]);
      expect(wrapper.toJSON()).toMatchSnapshot();
    });

@macintoshhelper if you use yarn it should all work as expected because we use yarn "workspaces"

Thanks for your work on this!

Np. Thanks for merging 🙂. Should I open an issue for discussing changelog merge conflicts? Maybe worth documenting a process for submitting PRs first, then adjusting the changelog to link to the open PR?


Docker 1.8.2 : Windows platform

Hello ,
I got the very latest version of docker tookbox installed on my Windows OS.
I have set-up the right proxy as I am behind the corporate firewall.
But , when i run a simple command , I see message "Layer already being pulled by another client. Waiting" . Nothing progresses.
Many other users have also reported the same on stackoverflow.
http://stackoverflow.com/questions/32183390/error-on-docker-pull-layer-already-being-pulled-by-another-client
Kindly , provide the resolution for the same .

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

I'd take a peek at these search results: https://github.com/docker/docker/issues?q=is%3Aissue+"Layer+already+being+pulled+by+another+client"+is%3Aopen
This is unfortunately a rather common issue lately, and seems to have gotten more prevalent after 1.7 (in my own experience).
#12823 seems to be the main issue where this is tracked.

Closing since this is a dup of the aforementioned issues.
I believe most of these issues are fixed on master, but without wide-spread usage it is difficult to tell.


Add coordinate system to headers in camera defintion files

Add it for the files in describing the cameras coordinate systems which are currently located in the ctapipe-extra repository.

I think it is fine to require that camera definition files / tables are in CameraFrame. People need to convert.


Can't use multiple "--bag_file" to extract multiple bag files

I can use multiple "--bag_file" to extract multiple bag files (apollo r5.5)
What can I do for it to extract multiple bag file one time

I also noticed the difference, which version of apollo have the problem?

apollo r5.5.0

@mbing123 apollo r5.5.0 don't support multiple --bag_file. You can refer to other versions to implement it, of course I forget whether it is 5.0 or 6.0

Do you mean that I can refer to version 5.0 or 6.0 to modify the 5.5 related files? Or replace version 5.5 all?

ndt_mapping have error with apollo 6.0, you can just ref the cyber_record_parser code alone.

I'll try it now. Thanks

When I made a map of 43 files, it took me 80 hours to make an output.pcd. Is it normal to take such a long time?

No, normally 43 files will be fast in a few minutes.
When the outfile gets bigger, the speed will get slower. Pls check the output file size

I mean 43 recorded files, over 25,000 pcd files when unzipped. The resulting output.pcd file size is 759M

That seems normal, since there is no parallel processing at the moment.
Decreasing how the output point cloud is matched can reduce the time, but I haven't tried it yet. For example, only a portion of the output point cloud is captured for matching instead of all

I see. I really appreciate it

@mbing123 By comparing the previous 3 frames instead of the entire map, the speed has now been greatly improved. I created a map about 600 frames which cost 2600s (43min)


clangd vscode can't find corresponding header file from template implementation file

When I press Alt + O on my template implementation file, it can't find the corresponding header file. The error message is:
"Didn't find a corresponding file"
The implementation file extension is maybe a little bit unconventional in our codebase, we use name.i.h. But as I see it, you basically have two shots:

Template implementation file extension follows a convention (e.g. *.ipp, *.tcc, *.inl etc...) (on that note: what are the supported extensions?)
The template implementation file includes the header file (even though not needed but for context and consistency's sake)

We do number 2) in our codebase (not my decision) but it seems that clangd doesn't follow this hint in any case. So this could be added.
Operating system:
Ubuntu 20.04

what are the supported extensions?

The extensions currently supported by clangd's "switch source/header" command are these ones:
  llvm::StringRef SourceExtensions[] = {".cpp", ".c", ".cc", ".cxx",
                                        ".c++", ".m", ".mm"};
  llvm::StringRef HeaderExtensions[] = {".h", ".hh", ".hpp", ".hxx", ".inc"};

We could add additional extensions here (though in the case of .i.h we'd also have to modify the logic of how to compute the extension, since currently it only looks at what's after the last dot.)
One thing I wonder about template implementation files, though: might there be cases where a header defines a mixture of templates and non-templates (for example, a non-template class with some templated methods and some non-templated methods), and has both a template implementation file (for the implementations of the templates) and a regular implementation file (for the implementations of the non-templates), so that e.g. foo.h, foo.ipp, and foo.cpp all exist? I wonder what the behaviour should be in such cases.

Well there might be such cases, I can remember that I probably did that sometimes. I mean in theory you could also have multiple *.cpp implementation files for one header file. But I think we should opt for the most idiomatic case, which I suppose is to have either one *.cpp or one *.ipp file for non-templated / templated implementations respectively. In most cases I saw the implementation is actually for a class which is templated by itself, so certainly all methods must be templated on the class template parameters as well.
In other cases: What speaks about a three-way or four way toggle? Basically just "showing" all the "connected" files to the user in a row when pressing Alt + O instead of just switching between two files.


Fix issue java easy

Hi @nikohoffren, I wanted to let you know that I have resolved the Java easy #141 issue. Could you please review and merge my changes when you have a moment? Thank you!

Hi @nikohoffren, I wanted to let you know that I have resolved the Java easy #141 issue. Could you please review and merge my changes when you have a moment? Thank you!

Code looks good!

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Add projects page with basic mockup

Addresses #10

@sumedh123 @kvnamipara Please review

@ajayns Looking good, Add appropriate links in navbar. we'll update content later

Projects page navbar? Currently none of the pages have content in navbar yet. I've followed same layout as Meetups and Workshops page @kvnamipara

We can just give link to go to homepage in left side of nav bar

I'll add back buttons to all the navs when resolving #4
@kvnamipara


Date marker colors

Is there a way to give each date marker on the same day a separate color?

Not yet. Duplicated as #217.


[Device Support Request] Connecte 4500994 Thermostat

Problem description
Hello,
I recently bought and had a Connecte 4500994 thermostat installed at my house. The problem is that it seems like zha is picking it up, but there are no controls and it's not connecting. I think this means it's missing a quirk?
It seems like the company that supplies these has rebranded devices in the past, but I cannot figure out which device was rebranded in this case.
Solution description
Either figure out what device quirk can work with this, or write a new one. I'm happy to help with that if I can be pointed in the right direction.
Screenshots/Video
Screenshots/Video

Device signature
Device signature
[Paste the device signature here]

Diagnostic information
Diagnostic information
[Paste the diagnostic information here]

Logs
Logs
[Paste the logs here]

Custom quirk
Custom quirk
[Paste your custom quirk here]

Additional information
No response

Found a zigbee2mqtt thread about it here where they seem to link to the herdsman implementation
https://github.com/Koenkk/zigbee2mqtt/issues/19174

Unfortunately due to lack of support, with no one even pointing me in a direction to do this myself, I have migrated to Zigbee2Mqtt and I would recommend others to do the same.


[V2V] Enhance throttler logging

While trying to identify the reason for odd balancing on a migration plan execution, we realized that we didn't have enough information to nail the cause. This PR adds extra logging in debug mode, so that we can understand the current limits at the EMS and Conversion Host levels.
The PR also changes the configuration of the SSH connection in ConversionHost.verify_credentials, because it currently overrides the log level of the global throttler. We will need another PR to keep the SSH errors, but the current setting is counter productive.
RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1726186

@miq-bot add-label transformation, hammer/yes, enhancement
@miq-bot add-reviewer @djberg96
@miq-bot add-reviewer @agrare

Does this also address the race condition you mentioned?

@djberg96 nope, but it logs the job state, so we know it if it happens again.

Looks good to me, @djberg96 ?

:+1:

Hammer backport details:
$ git log -1
commit 99bbf47929122fdebc7fc77d53e52206fac11a54
Author: Adam Grare<EMAIL_ADDRESS>Date:   Tue Jul 2 12:46:57 2019 -0400

    Merge pull request #18929 from fdupont-redhat/v2v_enhance_throttler_logging

    [V2V] Enhance throttler logging

    (cherry picked from commit fd7042726763fa37450efd587a83dbad575d68ec)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1726394


replacing grunt-contrib-sass with grunt-sass

Replacing grunt-contrib-sass with grunt-sass means we can lower the requirements boundary and dismiss the dependency on ruby being installed/present.
Fixes #1237

Coverage remained the same at 69.68% when pulling 6aabeb69b104f9056b55df8d74390afdccb04289 on lirantal:feature/adding-grunt-css into 68529935cea7632548fd91e2e1f53000ba223e81 on meanjs:master.

Coverage remained the same at 69.68% when pulling ea7a3eb8e2de4d19a6571b2ba4136ce18e8fd171 on lirantal:feature/adding-grunt-css into 68529935cea7632548fd91e2e1f53000ba223e81 on meanjs:master.


fix(es/codegen): Implement codegen for static import assertions

swc_ecma_codegen:

Implement codegen for static import assertions.

swc_ecma_transforms_proposal:

Modify the existing import_assertions transform to support assertions in exports.
Add tests.

swc:

Add a keep_import_assertions option to JscExperimental that will keep import assertions in the compiled output.

node-swc:

Add a keepImportAssertions option to the typings for JscConfig.experimental.
Also fix a typo in the typings where JscConfig.experimental was spelled as "experimetal".

Description:

Currently import assertions are correctly parsed if the input is TypeScript, or EcmaScript with import_assertions: true, but the codegen step strips them no matter what. This PR adds a keep_import_assertions option to JscConfig to keep them.
BREAKING CHANGE:

None
Related issue (if exists):
Fixes #2802.

 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.

looks like this will fix #2802 too

Thank you!

Thank you for the review!

This configuration doesn't seem to apply through the .swcrc file correctly currently in the Node.js CLI run, instead only when set manually via -C jsc.experimental.keepImportAssertions=true. Perhaps something was overlooked in this PR?

@guybedford Ah, my bad. I think it's because there's no code to handle the field in https://github.com/swc-project/swc/blob/a4e93eb2dff0614e7a39c4301c84654412cf68dc/crates/swc/src/config/mod.rs#L985-L991


Add configuration to ignore some directories

In some projects autogenerated directories could add mess to the Clap windows. For example in node projects the node_modules directory is so big and it could be ignored.

Others directories that could be ignored: node_modules|target|dist|vendor|bin|obj|build and so on.
It could be a good idea to be able to indicate Clap which directories to ignore depending on the project.

I discovered that you are ignoring the files contained in the .gitignore file. Is that correct?
If so, we can close this issue.

The default command used by files https://github.com/liuchengxu/vim-clap/blob/2c34f53018/autoload/clap/provider/files.vim#L9, fd will ignore the files in .gitignore, etc. You can also pass any arguments, e.g., do not ignore these files, :Clap files ++finder=fd --type f --no-ignore.


Running execute during ssh disconnects the session?

I'm not sure this is an issue or the way that it's supposed to function. But I am trying to use NMSSH in a Swift project and when I try to run multiple session.channel.execute(_: error: timeout:) the first command runs successfully and I get a response back. But the second command gives me the following output from the console : "2016-10-06 14:07:19.319684 test2[54562:8031308] NMSSH: Unable to open a session"
Here are my functions that are handling the session.
func connectSSH(onHost host: String) {
        sshQueue.sync {
            session = NMSSHSession(host: host, andUsername: username)
            session.connect()

            if session.isConnected == true {
                session.authenticate(byPassword: password)
                print("Authentication was a success.")
            }
        }
    }

    func runCommands(_ commands: [String]) {
        sshQueue.sync {
            let error: NSErrorPointer = nil

            for command in commands {
                session.channel.execute(command, error: error, timeout: 10)
            }
        }
    }

    func disconnectSSH() {
        sshQueue.sync {
            session.disconnect()
        }
    }

I've done a test where I check the session.isConnected == true after running the first command and I notice that it is no longer true. Again this may be the functionality of the execute function, if so is the only way to execute multiple commands to establish a remote shell? I didn't have any luck with that either.

Did some further testing. When I log into my local machine over ssh using <IP_ADDRESS> I am able to execute multiple commands and get responses.
I've tried using vt100 for the pty to match the terminal I am sshing into when I receive the "Unable to open a session" error, but that didn't help. Any recommendations you may have will be great. I am going to look in the equipment further tomorrow to see if I can see anything that could be causing it to disconnect have one command.
I have used Python scripts on this equipment previously and ran multiple commands without any issues.

Hi i am facing issue with authentication could you help me to share this source file if its working on your system?

I am facing that Issue as well and would be glad to hear whether there has been a solution on that, thanks!

This also affects shortcuts on iOS. Shortcuts is not able to login, but a normal openssh client is.


update dataset config validation docs with poetry install requirements

Running dataset config validation requires scripts from the ingestion_tools and those scripts require their corresponding dependencies. A temporary workaround for properly setting up dataset config validation. A future goal could be to unify all potential pyproject.toml / poetry.lock files across the repo into one.

Not doing this, instead removing schema/ dependency on ingestion_tools/


withoutReduction: true - does not stop from downscaling images

What are the steps to reproduce?
An image of size 500x500 will get resized to 400 despite the withoutReduction: true flag.
sharp('large.png')
.resize(400, 400, {
    withoutReduction: true
  }).toFile('small.png');

What is the expected behaviour?
Only smaller images should be resized (upscaled) to 400px
Trying to resize a larger image than 400x400 should due to withoutReduction: true should result in an image with with the dimensions of the original image, effectively not performing any resizing.
version:
"sharp": "^0.31.3",

In this example, the image is not resized. The default fit is cover and the target dimensions are 400x400 so the image is cropped to cover these. Perhaps you meant to specify a fit of contain?
https://sharp.pixelplumbing.com/api-resize

cover: (default) Preserving aspect ratio, ensure the image covers both provided dimensions by cropping/clipping to fit.

contain: Preserving aspect ratio, contain within both provided dimensions

I guess the documentation for withoutEnlargement and withoutReduction could be updated to clarify that a crop might still occur even when resizing does not.

Well lets compare it to withoutEnlargement: true
Source Image size: 500x500
sharp('500x500.png').resize(1000, 1000, {
    withoutEnlargement: true
  }).toFile('small.png');

The dimensions of the output are NOT 1000x1000 they are the size of the original image dimensions - as we did not want to enlarge.
sharp('500x500.png').resize(200, 200, {
    withoutReduction: true
  }).toFile('small.png');

The dimensions of the output ARE  200x200 instead of the original image dimensions - even though we did not want to Reduce.
This is apart from the settings on how to fill the canvas with the image.

The words "reduction" and "enlargement" refer to scaling and not cropping.
The idea of fit=cover is to ensure there is "enough" image to cover the target dimensions. If both required to and allowed to it will scale an image; if required to it will crop an image. It will not embed or pad an image with a provided background colour.
In the first example you've provided, the use of withoutEnlargement: true prevents it from scaling up the image. When it comes to the cropping decision, the image is already smaller than both target dimensions, so nothing else occurs.
In the second example, the use of withoutReduction: true prevents it from scaling down the image. When it comes to the cropping decision, the image is larger than the target dimensions so a crop occurs. This image with this combination of options is almost equivalent to the CSS object-fit: none; directive.
Given the examples provided, I suspect a fit of either outside or contain might be what you're looking for.


[WIP] Save annotations as partial classifications, pick them up in transciption phase.

TODO: only fetch partial classifications for the current subject set
This is a basic proof of concept. Currently, annotations and classifications are submitted as separate classifications. This PR instead saves annotations as partial classifications which the transcription phase picks up from api/classifications/incomplete (see http://docs.panoptes.apiary.io/#reference/classification/classification-collection/list-all-classifications).
Currently I haven't figured out how we limit these to the current subject set (i.e. ship) - we can't do it using the API I don't think. We might be able to include subjects in the classification request though, and then filter client-side as the subjects will have a subject set id in. Would need a loop which requests classifications from the API until we have at least one for the current set (or until there are no more classifications, in which case we show the "nothing to transcribe" notice as occurs currently).
Eventually I think we can cut out the localStorageService layer for most things, as I believe panoptes-client caches non-query requests.

You could store a hash of partial classifications and ships in the user's project preferences...

Currently I haven't figured out how we limit these to the current subject set (i.e. ship) - we can't do it using the API I don't think

Nope - I'm not sure we want to do this either.
Note that a user can only fetch their own incomplete classifications, so no benefit of asking 1 set of users to do boxes and the other doing annotations.
Noting that for scenarios like this we have planned to have 2 distinct workflows. The first being bounding boxes the second an annotations workflow. We'd have a internal service (nero like) to listen to classifications / aggregation and upon thresholds then promote / create subjects from workflow 1 -> 2.

@camallen that sounds much more sensible - is this functionality planned for the near future?

We have some of the pieces in play but nothing tested and working. Pinging @marten on this one, thoughts re timing / nero refactor?

Question - I think i'm confusing old weather and old weather whaling (scribe). How does it currently work? Just local storage of you bounding boxes and then you annotate them yourself? If so then using incomplete classifications seems fine.

The bounding boxes are saved to local storage (and retrieved from there in the transcribe workflow). The bounding boxes are actually also saved as complete classifications as well, but the front end never retrieves them after creation.

I only noticed this mention of me just now. Did you still need anything from me?

Then the proposed workflow makes a lot more sense since it's just using the API for the storage layer. @itsravenous we have no firm timelines just the idea about using incoming classifications to allocate / create new subjects for subsequent worfklows.
@marten I don't think so unless we pursue the creation of subjects (ala the scribe tool) between workflows.

@camallen @marten thanks for the attention! I suppose we on OW need to decide whether we want users to be able to transcribe other users' annotations (as using incomplete classifications would preclude that, right?)

Partial classifications now work given the Panoptes fix https://github.com/zooniverse/Panoptes/pull/1883
Merging to master.


Error highlighting is unreadable within

Challenge Name

All challenges in Applied Visual Design
Issue Description

Type within the style section of code.
.cm-s-monokai span.cm-error {
background: #f92672;
color: #f8f8f0;
}  is not overriding .night .CodeMirror .cm-property, .night .CodeMirror .cm-string {
color: #B5753A;
}
Browser Information

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36.
Screenshot

Issue only happens when in NightMode.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain oss-india.net has exceeded the max emails per hour (100/100 (100%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mail-oi0-f42.google.com ([<IP_ADDRESS>]:34242)
by server14.hostingraja.in with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89)
(envelope-from<EMAIL_ADDRESS>id 1dnx3U-003jh0-4f
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 06:47:18 +0530
Received: by mail-oi0-f42.google.com with SMTP id w10so13893173oie.1
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 18:16:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:delivered-to:dkim-signature:dkim-signature:date
:from:reply-to:to:cc:message-id:in-reply-to:references:subject
:mime-version:content-transfer-encoding:precedence:list-id
:list-archive:list-post:list-unsubscribe;
bh=vMY2/oUl6oE8PUH0Of8v0NoAvFeZv92PlYKTb8gARPg=;
b=go+qASaxBV5bDPY1+49i7Q8x0nC/6WBA+il9HEzgl+J+Y2geUDPtFzBq8rXYI1Qhe0
0DSayqynEgbsYaHNjNdxt8t2kkI18APAaph0uspM6cusjype1BF5DrCynULL0Wysbw2J
ufZoUKSHn9gil4L3hEZl0teET9CGz4Cg26MC8N+l9HfUovMzpJUk5mi98PVqc30aPTyB
FIc1E/oN+Wl1983BPoERPjac6UjgHevqiGAapHOROPtTT/SqbDKyY7BFhOZWIm4uEqrD
KIbQOrq6WyetJDhSfxYpQB8MB0ttldJ/YSozeOYvBayZr8iX18vKM6dO/p9DE9c0XljZ
Kzvw==
X-Gm-Message-State: AHPjjUiKfeNPrl22ghy5UdYDD79bAM7WPlrXR2eMFJ62YDZnD5SLqNrt
sllcZj2O7q9H2mveJc3+kRCI0ZKAIJFOlI2BDd7q0g==
X-Received: by <IP_ADDRESS> with SMTP id 124mr4143239oie.246.1504314977562;
Fri, 01 Sep 2017 18:16:17 -0700 (PDT)
X-Forwarded-To<EMAIL_ADDRESS>X-Forwarded-For<EMAIL_ADDRESS><EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Received: by <IP_ADDRESS> with SMTP id q13csp1352617ofe;
Fri, 1 Sep 2017 18:16:16 -0700 (PDT)
X-Google-Smtp-Source: ADKCNb4+3HHEgiphuuJfMni18tGGmfQpD3J41Fpe6oY4LjfTu/m/KplFyDGCgntbg1RIQZXtgfUX
X-Received: by <IP_ADDRESS> with SMTP id t65mr1123451itb.173.1504314976657;
Fri, 01 Sep 2017 18:16:16 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1504314976; cv=none;
d=google.com; s=arc-20160816;
b=fVSFvT5S0CFvGY0y1AZCNFtAXYUjou7Cf1VSsKuqddiEipXXcW04sSpjuoMjmP0F/S
m6dz2U5+TTl/zmMmpEIg4BpfLgAI2/tr4b3nD+zoI6crYf+sAlmaj/vv+x0xekjHNU2Y
e6fJhzI2wNycqjM/VgN89/Q6h2ZC1a5BrKH9e3YOuZXSmVg7hJWsNfXqC/yX2glrvG8d
0YJBPHHcUsr1fngyyl1sJMvD0VZuAmH94NLCglM/8Zs5Jd5vna542WsNL3gY6ABSVFvc
hZd3B3O7tAAtd6ou+0kd51LGdRYr2mrOkB/cvRh9Bcqz3qBWP65+AgxNTGyWAms7DBh0
Z67A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-post:list-archive:list-id:precedence
:content-transfer-encoding:mime-version:subject:references
:in-reply-to:message-id:cc:to:reply-to:from:date:dkim-signature
:dkim-signature:arc-authentication-results;
bh=vMY2/oUl6oE8PUH0Of8v0NoAvFeZv92PlYKTb8gARPg=;
b=PvEKOEPFXlWjhlcF17Asj/GJGAxivuoJ+zdVixePCPjkPH+ioFnuPXX78TsHQxx83G
nd0dBkRpRTjfjNVSUvGE76H/Gm0j28SUZ3avv/jJY5FWOjrGQrL1QHOvvzoXES8k3sPD
GImpg0+lZSKr0ahbXvMlw6CNXlSuhZ87sTf53ioSzODshFaJi6r9+0UzdS5bGgs/On2x
QVrBvIUp2DXEBV7N+EdJYmRQUvf6MckbiXlLM1CGRTbGc/vbn1WvYISRjOmtOyEfVdPb
ivUFLwUGMyIG1R+nzVV2KaJFmfsGrPMHYd0SLd8IIMPO74EptHoOylRjLBW6sYkWrial
SmsA==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=sGcA8GNR;
dkim=pass<EMAIL_ADDRESS>header.s=smtpapi header.b=kAXvEUtC;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
Received: from o3.sgmail.github.com (o3.sgmail.github.com. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id z69si1271016ita.97.2<IP_ADDRESS>.16.15
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 01 Sep 2017 18:16:16 -0700 (PDT)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=sGcA8GNR;
dkim=pass<EMAIL_ADDRESS>header.s=smtpapi header.b=kAXvEUtC;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=bGNuibBBvbJw5wmFDUwivAsy9Fw=; b=sGcA8GNRI2BiMpeK
ZX4TwAjVtSa3qhaZZA7bzJs9mhzbKfBScGhFcw0UACRDn1/FcCyfXeyWJa+tiLYb
yJXUUR3MWJ5nkx2V6EIXaqY7zU2vwkcaN2EiSUz+uqjiwuGLQehEaqv5ns3qZnca
aZVqH39RrHVnhITKLe0zHZrgixw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=sendgrid.info;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe:x-feedback-id;
s=smtpapi; bh=bGNuibBBvbJw5wmFDUwivAsy9Fw=; b=kAXvEUtCMIF/mKkMVH
5W0SlmZpuns4cems7fPVtwFvnemOi1SjRm5ePALLBXVQI6EMi86lq141Ek1Ap0a3
iCNDy6JiHi8QD1YAp/GsRqytRERWXFJ8CAJ1g88s35b3pQ3Z6mhV6ERLYLOWo+4I
aKaEuV6oXu2+1pa3WDn9X1hNg=
Received: by filter0956p1mdw1.sendgrid.net with SMTP id filter0956p1mdw1-18561-59AA065F-2B
2017-09-02 01:16:15.902255009 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0037p1mdw1.sendgrid.net (SG) with ESMTP id A2qsIWiZTwONI6vgYjBntw
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:16:15.936 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:16:15 +0000 (UTC)
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Error highlighting is unreadable
within

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain funtasticlabs.com has exceeded the max emails per hour (118/100 (118%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
------ The body of the message is 44372 characters long; only the first
------ 5000 or so are included here.
Received: from mailin-01.elitehosts.com ([<IP_ADDRESS>]:60349 helo=offsite.elitehosts.com)
by neo.internetwebserver.net with esmtp (Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1dnx7C-0004eM-PN
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:20:51 -0400
Received: from o7.sgmail.github.com ([<IP_ADDRESS>]:15030)
by offsite.elitehosts.com with esmtp (Exim 4.69)
(envelope-from<EMAIL_ADDRESS>id 1dnx6m-00023l-Gs
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:20:25 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=IH/nAflat7PNyallIzjHvrgsk14=; b=t4FoGuxygnhKQlpr
d9iPajIeeiLEq6EmpfHoXZvZBLoOEZGZE7tBauht1QGujy2qjuq920B36i+HD/KP
mU5tuDfV6Nyvw5Da4rV3hLTJRYEiF56W8fqcRHZeRBpGtVKmacrFXhiXY63sRMCd
rCqq8xs47gWspO/3gbqwsrnPVXw=
Received: by filter0325p1las1.sendgrid.net with SMTP id filter0325p1las1-13026-59AA0752-20
2017-09-02 01:20:18.340039464 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id n9W1m5w-TqmQJEKABmKvYA
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:20:18.169 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:20:18 +0000 (UTC)
From: Pawan Mehta<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Error highlighting is unreadable
within


Redox OS support

Thanks for the contribution @ids1024
I'll release a new version in the next few days.


Rescue cardiovascular disease as TA in EFO slim

Based on recent discussion on ACE2 invalid evidence (#890) and an analysis on the impact of missing evidence for CVD, we decided it's sensible to rescue the cardiovascular disease term from EFO.
A ticket has been opened EBISPOT/efo#740 to action this task.
Once the new EFO OT profile is available, we need to double check it contains the right TAs and structure.
No further action is expected in the production pipeline.

These are the number of invalid evidence strings we have per data source because they are annotated with EFO_0000319:
 640 "chembl"
28504 "europepmc"
3888 "ot_genetics_portal"
 377 "phewas_catalog"
Total: 33,409

This change was implemented in EFO 3.16. It didn't cause any unindented issues in pipeline or FE (QA version). A reduction on the number of invalid strings has been confirmed.


munger: update location of WordSepNormalizeFunc

It moved from k8s.io/kubernetes/pkg/util to
k8s.io/kubernetes/pkg/util/flag

Never mind ... I should be using godeps

although feel free to update the godeps.  make help has all sorts of useful information so you don't have to remember things...


Consider checking the type of a bad row before parsing directly with the right decoder

At the moment we use .as[BadRow] to parse a Json to its bad row case class.
This is based on ADTs encoding and decoding.
Given the number of classes and fields in the bad rows it might be more performant to first check the schema of the bad row (in "schema" field) and then use directly the right Decoder, e.g.
schema match {
  case Schemas.EnrichmentFailures.toSchemaUri =>
    json.as[EnrichmentFailures]
  ...
}

Yup, that's a good idea. But I believe it is duplicated ticket: https://github.com/snowplow-incubator/snowplow-badrows/issues/28

At the same time, I think it would be better to leave Decoder[BadRow] like it is now, because .as[A] decoding implies that structure is compatible with A, while what we really can decode it SelfDescribingData[BadRow]


Nav bar title set async

There seems to be a problem when setting the title attribute of ion-view, if I set it after a promise is resolved the width is wrong. If it's a constant string there is no problem.

Removing view-title="" before using $ionicNavBarDelegate.title(title); does not work in v1.0.0-beta.14. However, using <ion-nav-title> directive as @adamdbradley suggested did fix the issue.
Summary:

There is a bug while using $ionicNavBarDelegate.title(title);
There is a bug while using view-title="{{title}}"
<ion-nav-title>{{title}}</ion-nav-title> seems to be working fine

Hi @OminStyle , you are quite right.

@OminStyle: only <ion-nav-title>{{title}}</ion-nav-title> worked for me too

When using <ion-nav-title>{{title}}</ion-nav-title> I have the same problem described here: https://github.com/driftyco/ionic/issues/2945

+1.  Same problem as @jbdemonte
ion-nav-title width is calculated incorrectly.  I actually see it display correctly for a flash, and then shrink and truncate the title

Context: I just jumped into a project w/ ionic + sass implemented. Not sure if this is a bug isolated to the SASS implementation or not.
There should probably be a SASS variable for $bar-title-width used in this class. If anyone is interested, I can make some PR's to update things.
Here's your problem:
  .bar .title {     position: absolute;     top: 0;     right: 0;     left: 0;     z-index: 0;     overflow: hidden; /* Problem if you have no width set */     margin: 0 10px;     min-width: 30px;      height: 43px;     text-align: center;     text-overflow: ellipsis;     white-space: nowrap;     font-size: 17px;     font-weight: 500;     line-height: 44px; }
Here's an updated version:
Here's your problem:
  .bar .title {     position: absolute;     top: 0;     right: 0;     left: 0;     z-index: 0;     margin: 0 10px;     min-width: 30px;     width: 80vw; /* Or whatever width you'd like */     height: 43px;     text-align: center;     /* text-overflow: ellipsis; */ /* this could be good if it's what you want. Use at your discretion */     white-space: nowrap;     font-size: 17px;     font-weight: 500;     line-height: 44px; }

Overwrite the .bar .title in your custom SASS components
Edit the ionic framework SASS. .bar .title. I haven't tested this thoroughly yet and it's implications it might have over the app.

Right now, option #1 is easiest for me, but I wouldn't think it's ideal


[AutoRelease] t2-authorization-2023-07-18-34193(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4263
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=970

issue link:https://github.com/Azure/sdk-release-request/issues/4263


Evgenyrahman/slide update

Pull Request from Evgeny for Slides
Background
This is to show how PRs work etc
Things I did

[x] Opened this PR
[x] Wrote some code

@evgenyrahman please add some more slides


Handle relative import path for contracts in test command

PR for context: https://github.com/SupunS/cadence-testing/pull/1

Codecov Report

Merging #985 (8395747) into master (bed89ec) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #985   +/-   ##
======================================
  Coverage    2.52%   2.52%
======================================
  Files           5       5
  Lines         435     435
======================================
  Hits           11      11
  Misses        423     423
  Partials        1       1

Flag
Coverage Δ

unittests
2.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

cc @SupunS @turbolent

Sure thing! I just wanted to see first, if anyone has a better implementation idea on how to handle this case.

@sideninja Added two test cases in https://github.com/onflow/flow-cli/pull/985/commits/1464fbec94253a45e4880a4f4e449891d725f992

@sideninja Is there any plan for a release this week? If yes, we would like to have this bug-fix included, as it is a blocker towards adoption of the code coverage feature :pray:

@m-Peter we can make a patch release today cc @chasefleming

If that's not too much trouble, it would be awesome :heart_eyes:


Getting timeouts on API requests

Package:
  "_from": "<EMAIL_ADDRESS>  "_id": "<EMAIL_ADDRESS>
code:
var cc = new computeManagementClient(gbl_azureCredsCache, azureConfig.subscriptionId);
computeClient.beginStart(vmName, vmName)

error:
 FetchError: request to https://management.azure.com/subscriptions/xxxxx/resourceGroups/xxxxx/providers/Microsoft.Compute/virtualMachines/xxxxx/start?api-version=2019-03-01 failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443

checking

Hi @sbutalia
Cloud you show your full code?  What does computeClient refer to in you sharing code?
Thanks

@dw511214992 Based on the error message, it looks like the code would be
var cc = new ComputeManagementClient(...);
cc.virtualMachines.beginStart(...)

Thank you @ramya-rao-a
Hi @sbutalia I tried in my side and don't see your issue. I think it may be casued by instability of network. Are you still encountering this issue?
Thank you

@sbutalia
Closing this issue as we havent heard back from you in a while.
Please feel free to log a new issue with code snippets if you see this again.


description field not written when adding/changing SLO

Hi,
when adding/changing an SLO the "description" field is not getting written to dynatrace

Provider Version 1.10.0
Resource Used: https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/resources/slo

Propably this is due to the a change in the API, as the description field is called "customDescription" on the API documentation (and it works, when doing a POST directly towards the API with customDescription

This issue has been fixed with Release v1.11.0.


feat: kyve spec, mainnet and testnet

Description
Added Spec for Kyve, mainnet and testnet

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[x] read the contribution guide

[x] included the correct type prefix in the PR title, you can find examples of the prefixes below:

[ ] confirmed ! in the type prefix if API or client breaking change

[x] targeted the main branch

[ ] provided a link to the relevant issue or specification

[x] reviewed "Files changed" and left comments if necessary

[ ] included the necessary unit and integration tests

[x] updated the relevant documentation or specification, including comments for documenting Go code

[x] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

New Features

Added new specifications for Kyve Mainnet, including block time, stake requirements, API endpoints, and verification details.
Added new specifications for Kyve Testnet, detailing provider types, block configurations, API collections, and verification parameters.

@RuslanGlaznyov we moved all the specs to the lava-config repo
can you open it there under testnet-1?
thanks


[Bug] : Contact Us cannot Proper approach

In this project contact Us content In the dark mode can be text can be black doesn't visible..
If i want to suggest for the proper text color in mode change.

Expected behaviour
Screencast from 2024-05-25 16-52-24.webm
Actual behaviour
Screencast from 2024-05-25 16-48-13.webm

please assign me..
I will ready for work it..

Go for it @sivaprasath2004

PLease assign me the issue , I am redy to work on it


Added checkPermissions function

A big downside to the plugin is asking user for permissions on initializing the application. As far as I know, there's no native app that would ask for extra permissions on app start but only on exact time where the plugin should be used.
That's why, I've updated the code, added the checkPermissions function and updated readme. Feel free to update/comment the PR.
For additional question, I'll be glad to help.

Please approve this pull request

This pull request needs to be approved

Seems a bit silly to force the end-user Javascript to check for permissions. I've done a pull request #25 which requires no javascript code changes for end-users and still implements this permission fix.

@ChrizC while I appreciate your PR, there's an logic issue in your PR:
If I DECLINE permission on purpose... in which-ever app... the app then doesn't always ask for permissions again but just show you permissions were declined. To fix this, you have to go to system settings and allow them again.
Why would you now take this away from developer, and why do all other Plugins include checkPermission() or depend on developer to handle permission issues itself is another story.

@lordgreg I'm confused as to what your point is - every app will keep asking for permissions after they've been declined, if you're still trying to do the thing that needs permissions. The Android OS will eventually offer the user a "never ask me again" option to the permission check, which will then make the permission check always return permission denied in the background. And it's up to the developer of the app to handle denied permissions.
Having used about 25+ Cordova plugins, this is the only one which has the legacy Android permission check. None of those other plugins require you to permission check in the Javascript, they all handle their own permission checks natively in the plugin.
If developers want to manually check permissions via Javascript, there are plugins which allow them to do this. This plugin should not presume that the developer will do the permission check.

Am closing this now as #25 has been merged in. @lordgreg Thanks for your original submission.


Target dummies

Ideally it pops up how much damage it took when hit.

It was resolved by the merging of #12317.


Translation to italian

hope it can help

Grazie! I will include it in following release.

Grazie! I will include it in following release.


changed cohere.py to update the default model of embedding

The cohere embedding model do not use large, small. It is deprecated. Changed the modules default model

Fixes # 4694
Before submitting

Who can review?
Community members can review the PR once tests pass. Tag maintainers/contributors who might be interested:

Created pull request for issue#4694

thanks @rajib76! closes #4694


Provide min / max value in slider headers and footer.

It would be nice to have in the documentation some examples of the header and footer using function instead of string.

Hi @hugo-ruivo-dw thanks for opening this issue.
Indeed this kind of information could be useful in the header / footer. However I'm not sure how feasible it is.

Do you mean adding the currently selected minimum and maximum, or the values that you set while initialising the widget. If you mean the initialised values, you should be able to put them in a variable before writing the widget code, and use the same value, or just copy and paste the values.

I mean the currently selected minimum and maximum.

Somebody know an answer?

@oscarhandsome This is currently not feasible with the current API. However, your feedback is greatly appreciated – we'll let you know if we make the bound values available.

@oscarhandsome This is currently not feasible with the current API. However, your feedback is greatly appreciated – we'll let you know if we make the bound values available.

Thank you for the answer, but, now I don't understand how can I move values to another tag? https://prnt.sc/l55g2s
might do you know a way?

Sorry for the late answer.
I'm not sure to understand the last question.
Assuming you're using InstantSearch.js v2, you can style the CSS class to move the price values:
.ais-range-slider--tooltip {
  margin-top: 50px;
}

You can change the margin-top value at your convenience.


Https warning  on site

Says cert expired 5 days ago

thank you! I had to reload nginx to get it to pick up the new certificate


issue with country flag after removing country code

Discussed in https://github.com/typesnippet/antd-phone-input/discussions/77

Originally posted by dmatysiak94 March 28, 2024
I aslo would like to report bug that input shows country ISO code and phone code instead of the flag if the user clears the Phone value after search using.
https://github.com/typesnippet/antd-phone-input/assets/37019712/02a9581a-315d-4420-ad33-f6ec7f5f5af4

@dmatysiak94, I was unable to reproduce the issue. Can you check the version of the antd-phone-input and react-input-hooks you're using?

@dmatysiak94, this must have been an old issue that was already fixed, which is why I could not reproduce it. Please upgrade the antd-phone-input and react-input-hooks dependency versions and try again. I am closing the issue, but you can reopen it if you face an issue after upgrading the dependencies.


vobject fails to parse this vcard

This code:
import vobject
el = """BEGIN:VCARD
VERSION:2.1
N;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:;=57=6F=6C=6C=6B=6E=C3=A4=75=65=6C=20=53=6F=63=6B=65=6E=62=61=72=74=20=
=45=50;;;
FN;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:=57=6F=6C=6C=6B=6E=C3=A4=75=65=6C=20=53=6F=63=6B=65=6E=62=61=72=74=20=
=45=50
TEL;CELL:+123456
TEL;CELL:+123456
END:VCARD"""
print(vobject.readOne(el))

fails with the message
Traceback (most recent call last):
  File "/path/to/script.py", line 32, in <module>
    print(vobject.readOne(el))
  File "/home/volker/.local/lib/python3.9/site-packages/vobject/base.py", line 1155, in readOne
    return next(readComponents(stream, validate, transform, ignoreUnreadable,
  File "/home/volker/.local/lib/python3.9/site-packages/vobject/base.py", line 1101, in readComponents
    vline = textLineToContentLine(line, n)
  File "/home/volker/.local/lib/python3.9/site-packages/vobject/base.py", line 925, in textLineToContentLine
    return ContentLine(*parseLine(text, n), **{'encoded': True,
  File "/home/volker/.local/lib/python3.9/site-packages/vobject/base.py", line 813, in parseLine
    raise ParseError("Failed to parse line: {0!s}".format(line), lineNumber)
vobject.base.ParseError: At line 7: Failed to parse line: =45=50;;;

instead of waiting for the library to be fixed...
Seems most/android phone exporters split long lines (>115) this way - ending on '=' then next line starts with '='. Most non-ascii names hit this limit easily.
newvcardtext = vcardtext.replace( '=\n=', '=')
works fine joining them back; use on single vcard or over whole vcf file/text, before parsing with vobject.

Thank you, this works.

You must allow QP decoding since the parser knows how to decode it:
print(vobject.readOne(el, allowQP=True))

print(vobject.readOne(el, allowQP=True))

This also works.


v0.60.0 app-group deploy suddenly also deletes after deploying

What steps did you take:
We updated kapp version in our deployment pipelines to v0.60.0
What happened:
kapp deployed as expected but it run a delete immediately and deletes the whole app
I can reproduce this in my test environment.
This is the command I am executing there:
kapp app-group deploy --group=platform.test-test --namespace=default --yes --diff-changes=true --apply-default-update-strategy=fallback-on-replace --directory=/src --dangerous-allow-empty-list-of-resources=true --dangerous-override-ownership-of-existing-resources=true --default-label-scoping-rules=false --logs=false --wait-timeout=20m0s --app-changes-max-to-keep=10 --delete-exit-early-on-apply-error=false --delete-exit-early-on-wait-error=false --exit-early-on-apply-error=false --exit-early-on-wait-error=false
This is the result with v0.59.2 to an existing and unchanged test deployment:
kapp-deploy  | --- deploying app 'platform.test-test-dockerfile-subdir' (namespace: default) from /src/dockerfile-subdir
kapp-deploy  | Changes
kapp-deploy  |
kapp-deploy  | Namespace  Name  Kind  Age  Op  Op st.  Wait to  Rs  Ri
kapp-deploy  |
kapp-deploy  | Op:      0 create, 0 delete, 0 update, 0 noop, 0 exists
kapp-deploy  | Wait to: 0 reconcile, 0 delete, 0 noop
kapp-deploy  |
kapp-deploy  | --- deploying app 'platform.test-test-subdir' (namespace: default) from /src/subdir
kapp-deploy  |
kapp-deploy  | Changes
kapp-deploy  |
kapp-deploy  | Namespace  Name  Kind  Age  Op  Op st.  Wait to  Rs  Ri
kapp-deploy  |
kapp-deploy  | Op:      0 create, 0 delete, 0 update, 0 noop, 0 exists
kapp-deploy  | Wait to: 0 reconcile, 0 delete, 0 noop
kapp-deploy  | time=2024-03-22T17:00:15Z | msg="🏁 finished"
kapp-deploy exited with code 0

This happens with v0.60.0:
kapp-deploy  | --- deploying app 'platform.test-test-dockerfile-subdir' (namespace: default) from /src/dockerfile-subdir
kapp-deploy  | Changes
kapp-deploy  |
kapp-deploy  | Namespace  Name  Kind  Age  Op  Op st.  Wait to  Rs  Ri
kapp-deploy  |
kapp-deploy  | Op:      0 create, 0 delete, 0 update, 0 noop, 0 exists
kapp-deploy  | Wait to: 0 reconcile, 0 delete, 0 noop
kapp-deploy  |
kapp-deploy  | --- deploying app 'platform.test-test-subdir' (namespace: default) from /src/subdir
kapp-deploy  |
kapp-deploy  | @@ update configmap/website (v1) namespace: default @@
kapp-deploy  |   ...
kapp-deploy  |   4,  4   metadata:
kapp-deploy  |   5     -   annotations: {}
kapp-deploy  |   6,  5     creationTimestamp: "2024-03-22T16:35:37Z"
kapp-deploy  |   7,  6     labels:
kapp-deploy  |
kapp-deploy  | Changes
kapp-deploy  |
kapp-deploy  | Namespace  Name     Kind       Age  Op      Op st.               Wait to    Rs  Ri
kapp-deploy  | default    website  ConfigMap  32m  update  fallback on replace  reconcile  ok  -
kapp-deploy  |
kapp-deploy  | Op:      0 create, 0 delete, 1 update, 0 noop, 0 exists
kapp-deploy  | Wait to: 1 reconcile, 0 delete, 0 noop
kapp-deploy  |
kapp-deploy  | 5:08:06PM: ---- applying 1 changes [0/1 done] ----
kapp-deploy  | 5:08:06PM: update configmap/website (v1) namespace: default
kapp-deploy  | 5:08:06PM: ---- waiting on 1 changes [0/1 done] ----
kapp-deploy  | 5:08:07PM: ok: reconcile configmap/website (v1) namespace: default
kapp-deploy  | 5:08:07PM: ---- applying complete [1/1 done] ----
kapp-deploy  | 5:08:07PM: ---- waiting complete [1/1 done] ----
kapp-deploy  |
kapp-deploy  | --- deleting app 'platform.test-test-dockerfile-subdir' (namespace: default)
kapp-deploy  |
kapp-deploy  | Changes
kapp-deploy  |
kapp-deploy  | Namespace  Name  Kind  Age  Op  Op st.  Wait to  Rs  Ri
kapp-deploy  |
kapp-deploy  | Op:      0 create, 0 delete, 0 update, 0 noop, 0 exists
kapp-deploy  | Wait to: 0 reconcile, 0 delete, 0 noop
kapp-deploy  |
kapp-deploy  | 5:08:18PM: ---- applying complete [0/0 done] ----
kapp-deploy  | 5:08:18PM: ---- waiting complete [0/0 done] ----
kapp-deploy  |
kapp-deploy  | --- deleting app 'platform.test-test-subdir' (namespace: default)
kapp-deploy  |
kapp-deploy  | @@ delete configmap/website (v1) namespace: default @@
kapp-deploy  |
kapp-deploy  | Changes
kapp-deploy  |
kapp-deploy  | Namespace  Name     Kind       Age  Op      Op st.  Wait to  Rs  Ri
kapp-deploy  | default    website  ConfigMap  33m  delete  -       delete   ok  -
kapp-deploy  |
kapp-deploy  | Op:      0 create, 1 delete, 0 update, 0 noop, 0 exists
kapp-deploy  | Wait to: 0 reconcile, 1 delete, 0 noop
kapp-deploy  |
kapp-deploy  | 5:08:39PM: ---- applying 1 changes [0/1 done] ----
kapp-deploy  | 5:08:39PM: delete configmap/website (v1) namespace: default
kapp-deploy  | 5:08:39PM: ---- waiting on 1 changes [0/1 done] ----
kapp-deploy  | 5:08:39PM: ok: delete configmap/website (v1) namespace: default
kapp-deploy  | 5:08:39PM: ---- applying complete [1/1 done] ----
kapp-deploy  | 5:08:39PM: ---- waiting complete [1/1 done] ----
kapp-deploy  | time=2024-03-22T17:08:50Z | msg="🏁 finished"
kapp-deploy exited with code 0

What did you expect:
kapp finishing successfully like it does with v0.59.2
Anything else you would like to add:
This here looks to me like the only change that could have caused that issue:
https://github.com/carvel-dev/kapp/pull/850
Any help appreciated!
Thanks!
Environment:

kapp version (use kapp --version): v0.60.0
We call kapp as golang library from our deployment tooling: https://github.com/carvel-dev/kapp/blob/79900e40a3f3f43b31470d21db4dbd67e5acd3fa/pkg/kapp/cmd/kapp.go#L48
Kubernetes version: v1.28.7-eks-b9c9ed7

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

Thank you for creating the issue @dhohengassner! Looks like it was a miss while fixing the ordering.


[BUG] Probably does not work with WSL2

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
npm repo pkg fails.
Expected Behavior
npm repo pkg should open a browser page with pkg repo.
Steps To Reproduce
$ npm repo axios
npm ERR! Cannot read properties of undefined (reading 'stdin')

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ai/.npm/_logs/2023-04-09T13_02_08_591Z-debug-0.log

Environment

npm: 9.5.0
Node: 18.15.0
OS: Ubuntu 20.04
platform: WSL2

Bumping as this means that npm login fails for this reason on Node 18 on WSL.


Store Airflow logs to EFS mount

Description
Right now, our Airflow logs are stored in ~/airflow/logs on our etl EC2 instances.  However, our etl instances have limited disk space available (~10 GB as of time of writing), which means we can only retain a few days of logs.  (The Airflow scheduler writes a lot of log messages.)
This task aims to move those logs to the EFS mount at /data, so that we can reduce disk usage on etl.
Acceptance Criteria

[x] update airflow.cfg to store logs to /data/log/etl, instead of ~/airflow/logs;
[x] verify that logs are being written to the new location;
[x] delete the old log folder at ~/airflow/logs;
[x] update the airflow_log_cleanup DAG to increase retention to 30 days.

Additional Notes
The airflow_log_cleanup DAG cleans up our Airflow logs daily, ensuring that we only retain a limited number of days.  This should automatically pick up any changes to the BASE_LOG_FOLDER setting in airflow.cfg.

Assigning to @peter-lyons - this is a good first task for poking around our Airflow configuration and ETL machines.

airflow component done and tested in dev


Bring back renamings in emitted d.ts files

Fixes #55654 (with the unfortunate solution)
This isn't ideal. I think the direction we want to go is to not emit renamings if we don't have to, but the current implementation uses isReferenced which unfortunately considers references other than those that affect the signatures of the functions. So if you ever actually use the parameter you've renamed, then it will be kept, even if that isn't required. In the real world, that'd of course be nearly all instances, because there's usually no reason to destructure a parameter and then not use it. Of course our tests have a lot of this because we typically don't care about what's inside a function, or we don't have a body at all!
This with #50779 effectively reverts all of #41044 except the new error. You'll notice that this PR's baseline changes don't contain any new errors, which is good. This is because the error only happens when the signature doesn't have an annotation, e.g.:
declare function foo({ a: string }): void; // Error
declare function bar({ a: string }: { a: string }): void; // Okay!

The former can't happen in emitted d.ts files; we're always going to fully annotate the output.
Maybe there's a solution that would instead attempt to figure out if the name is ever actually used elsewhere, but I'm not sure how to do that. I feel like we probably have that logic somewhere for other reasons? In which case, I'm happy to redo the PR.

I can’t see from the conversation in #55654 why we need to do anything here 🤔

No, you're right; we could "do nothing" and it would be fine; the existing code only removes things that are definitely unreferenced. If we want to do this right with usage tracking, that's #55683.


Things to fix

As I tried to test esssans workflow https://github.com/scipp/esssans/pull/134,
I found some bugs in the nexus helper and the random data generator.

[ ] dtype parsing from a message.

https://github.com/scipp/beamlime/blob/66c9efd9e1cc324b936452c75aff368f552c8ec3/src/beamlime/applications/_nexus_helpers.py#L8-L17
Numpy dtype doesn't match with the nexus dtype. So I suggest to update it to:

def _dtype_to_nexus_dtype(dtype: type):
    if dtype == str:
        return 'string'
    if dtype == int:
        return 'int'
    if dtype == float:
        return 'float'
    raise ValueError(f"Unsupported dtype: {dtype}")

def _dtype(value):
    """Return the dtype of a numpy array or the type of a scalar value."""
    if hasattr(value, 'dtype'):
        return _dtype_to_nexus_dtype(value.dtype)
    else:
        return _dtype_to_nexus_dtype(type(value))

[ ] numpy array wrapping missing

https://github.com/scipp/beamlime/blob/66c9efd9e1cc324b936452c75aff368f552c8ec3/src/beamlime/applications/_random_data_providers.py#L51-L52
In the production, the message de-serializer will convert them into numpy array so it doesn't matter.
reference_time=np.array([et_zero]),
reference_time_index=np.array([0]),

It's related to the dtype parsing above.

[ ] unit missing when we merge messages

When we initialize the dataset, we also need to insert units.
That's why I hard-coded the recipes per schema before.
The units are mentioned in the comment lines of the schemas but we can't get that information else where...
So we either get back the recipes, or we should insert some if-statements that handle the units.
Units are attributes in the nexus structure, that should be inserted like this:

Note that the attributes are a list of dictionaries(each attribute).

dataset['attributes'] = [dict(
                name='units',
                dtype='string',
                values='ns'
            )]

[ ] Merging decides to concatenate/stack/replace based on the field name

It was missing some fields to concatenate the values. I think it shouldn't depend on the names of the fields at all.
It should concatenate if it's possible, or replace it based on the values type.
https://github.com/scipp/beamlime/blob/66c9efd9e1cc324b936452c75aff368f552c8ec3/src/beamlime/applications/_nexus_helpers.py#L35-L43

[ ] Merging concatenate the initial data twice.

https://github.com/scipp/beamlime/blob/66c9efd9e1cc324b936452c75aff368f552c8ec3/src/beamlime/applications/_nexus_helpers.py#L39-L43
After we initialize the dataset, we don't know if we retrieved the existing dataset or we create the new dataset with the new value but here it concatenates the new value anyways.
We probably have to update how it initializes dataset. Also related to the previous point.

[ ] Field name mapping from schema to nexus.

https://github.com/scipp/beamlime/blob/66c9efd9e1cc324b936452c75aff368f552c8ec3/src/beamlime/applications/_nexus_helpers.py#L119-L120
Unfortunately, the name of the fields in the schema doesn't match with the nexus file...!
For example, reference_time should be event_time_zero.
It should be translated before we merge.
    if kind == 'ev44':
        content['event_time_zero'] = content.pop('reference_time')
        content['event_index'] = content.pop('reference_time_index')
        content.pop('source_name')
        content['event_time_offset'] = content.pop('time_of_flight')
        _merge_ev44(store[path], content)

[ ] Typo in the random generator and too small time offsets.

This is not really a bug, but for generating realistic dataset, we should fix these lines:
https://github.com/scipp/beamlime/blob/66c9efd9e1cc324b936452c75aff368f552c8ec3/src/beamlime/applications/_random_data_providers.py#L44
should be:
et_zero = ReferenceTimeZero(13620492*10**11)  # No reason

and
https://github.com/scipp/beamlime/blob/66c9efd9e1cc324b936452c75aff368f552c8ec3/src/beamlime/applications/_random_data_providers.py#L53
should be:
time_of_flight=rng.random((cur_event_number,)) * 48_000_000 + 4_000_000,  # No reason

I didn't fix them at once cuz some of them needs quite a few lines of changes across the modules...

reference_time=np.array([et_zero]),
reference_time_index=np.array([0]),

Prefer np.asarray in such cases, which can avoid a copy if it is and ndarray already.

Merging decides to concatenate/stack/replace based on the field name

It was missing some fields to concatenate the values. I think it shouldn't depend on the names of the fields at all.
It should concatenate if it's possible, or replace it based on the values type.

The issue is that "merging" messages is not an obviously well defined concept.
For example, the field message_id in ev44 messages.
What is the message_id of two merged ev44 messages? It's undefined.
Therefore I think what makes most sense here is to do the simplest thing possible and explicitly define the semantics for how fields are merged, and only for the fields we really need.

Field name mapping from schema to nexus.

It should be translated before we merge.

I don't see why we need to translate them before merging?
Let that be part of the merging logic in that case.

Merging concatenate the initial data twice.

Good catch!

Johanness also pointed out that we need to handle the concatenation of the reference_time_index, since we have to modify the value when we are extending it. We can't simply extend the lists.

Johanness also pointed out that we need to handle the concatenation of the reference_time_index, since we have to modify the value when we are extending it. We can't simply extend the lists.

Why do we have to modify the value?

Why do we have to modify the value? Has it been determined that we do not get a "global" index here via EV44?

I don't know. Good question. I'll ask ECDC.

I spoke with ECDC about it:

It's relative to the message, not a global index.
The n:th reference_time_index indicates the start index of the interval of the tof array associated with the n:th reference_time.
It always starts with 0 except if the number of events is 0, in that case it is -1.
Currently it is always a length 1 array, because they only have one reference time per message ;)

@jokasimr can you please write that down in our documentation?
Probably here:
https://git.esss.dk/docs/dmsc/-/blob/main/docs/groups/dram/data-reduction/data-streaming.md?ref_type=heads#data-format


FII-030 - Display the Inline files on the File inspector - UI implementation (LEAN-920)

In this PR: will get data of inline files from ModelMap and will update design figma

Can one of the admins verify this patch?

@mbartenev-atypon moved to lib

Approving with small notes.


@types/request unsupport<EMAIL_ADDRESS>

Summary
@types/request unsupport<EMAIL_ADDRESS>Simplest Example to Reproduce
Function start cwd: /builds/kemao-node-basis/metro-ui cli: tsc -p src
Function stdout node_modules/@types/request/index.d.ts(66,15): error TS2430: Interface 'DefaultUriUrlRequestApi<TRequest, TOptions, TUriUrlOptions>' incorrectly extends interface 'RequestAPI<TRequest, TOptions, TUriUrlOptions>'.
  Types of property 'defaults' are incompatible.
    Type '(options: TOptions) => DefaultUriUrlRequestApi<TRequest, TOptions, OptionalUriUrl>' is not assignable to type '{ (options: TOptions): RequestAPI<TRequest, TOptions, RequiredUriUrl>; (options: (UriOptions & TO...'.
      Type 'DefaultUriUrlRequestApi<TRequest, TOptions, OptionalUriUrl>' is not assignable to type 'RequestAPI<TRequest, TOptions, RequiredUriUrl>'.
        Types of property 'delete' are incompatible.
          Type '{ (uri: string, options?: TOptions, callback?: request.RequestCallback): TRequest; (uri: string, ...' is not assignable to type '{ (uri: string, options?: TOptions, callback?: request.RequestCallback): TRequest; (uri: string, ...'. Two different types with this name exist, but they are unrelated.
            Types of parameters 'options' and 'options' are incompatible.
              Type '(UriOptions & TOptions) | (UrlOptions & TOptions)' is not assignable to type 'OptionalUriUrl & TOptions'.
                Type 'UriOptions & TOptions' is not assignable to type 'OptionalUriUrl & TOptions'.
                  Type 'UriOptions & TOptions' is not assignable to type 'OptionalUriUrl'.
                    Types of property 'uri' are incompatible.
                      Type 'string | Url' is not assignable to type 'string'.
                        Type 'Url' is not assignable to type 'string'.

This isn't the repository for that package. Please refer your issue at https://github.com/DefinitelyTyped/DefinitelyTyped


Load firestore in the isolate

I think WidgetsFlutterBinding.ensureInitialized() needs to be called.
Basically, ensure that the isolate can read from Firestore.

@kevmo314 I think this should be completed https://github.com/muxable/rtchat/blob/main/lib/tts_isolate.dart#L51