Component not filling in properly using Chrome autofill and on paste

When using the pattern<PHONE_NUMBER>, this component wasn't filling in the phone number using the chrome auto-fill. Also ran into problem trying to paste using this mask as well.

@insin would it be possible to take a look at this sometime this week?

+1

+1

PRs welcome!

Was there a problem with #22? It looks like no one gave any feedback. I could rebase the patch if the approach is okay.

I haven't had a chance to take a look but its probably fine if it works, feel free to rebase. We'll get some more eyes on it promptly

@jquense tested and rebased and it works for me (added a test case as part of the description of the PR). Thought about adding it to the demo but decided not to.
Seemed cleanest to not include /dist changes in the commit

It's been over a year and this is still open?  Is this ever going to get in?

This is pretty essential. Any update on this issue?

Bump

Up 👍

I ran into the same issue, but I discovered that if you add prop type="tel" it seems to work


shrink gives errors #2

After run at Ubuntu 18.04 i see this
user@user-pc:~$ sudo ./pishrink.sh /media/sf_raspy/relay_proj_200119.img
tune2fs: Input/output error while trying to open /dev/loop7
Couldn't find valid filesystem superblock.
mount: /tmp/tmp.pDOb40n21z: can't read superblock on /dev/loop7.
md5sum: /tmp/tmp.pDOb40n21z/etc/rc.local: No such file or directory
./pishrink.sh: line 78: [: !=: unary operator expected
umount: /tmp/tmp.pDOb40n21z: not mounted.
e2fsck: Operation not permitted while trying to open /dev/loop7
You must have r/w access to the filesystem or be root
resize2fs 1.44.1 (24-Mar-2018)
resize2fs: Operation not permitted while trying to open /dev/loop7
./pishrink.sh: line 151: [[: Couldn'tfindvalidfilesystemsuperblock.: syntax error: invalid arithmetic operator (error token is "'tfindvalidfilesystemsuperblock.")
./pishrink.sh: line 157: - Couldn'tfindvalidfilesystemsuperblock.: syntax error: invalid arithmetic operator (error token is "'tfindvalidfilesystemsuperblock.")
resize2fs 1.44.1 (24-Mar-2018)
resize2fs: Operation not permitted while trying to open /dev/loop7
Couldn't find valid filesystem superblock.
ERROR: resize2fs failed...
mount: /tmp/tmp.pDOb40n21z: can't read superblock on /dev/loop7.
mv: cannot stat '/tmp/tmp.pDOb40n21z/etc/rc.local.bak': No such file or directory
umount: /tmp/tmp.pDOb40n21z: not mounted.
losetup: /dev/loop7: detach failed: No such device or address

the given image for program is taken by dd command, the source of image is most fresh Raspbian lite

Did you ever figure this?

@unclehowell
as i remember right this error happens when we try to shrink image from being virtual machine and joined hdd volume.
solution is:
copy image into virtual machine then shrink.

Can confirm, was able to do basically this in my VM of Ubuntu 18.04:
cp /media/sf_Shared/some.img /tmp/some.img
sudo ./pishrink.sh /tmp/some.img
mv /tmp/some.img /media/sf_Shared/some.img

The only problem is the additional time is making sure you have a big enough VM drive and then waiting for the copy and move on multi-gigabyte files.

Unfortunately VirtualBox does not work as well as it should. I added a warning about this to the README


Remove Lint steps from CI as we have pre-commit-ci?

Shall we remove
https://github.com/pymc-labs/pymc-marketing/blob/bc71f159490a75660e563a6ae4bd7214ca2b18d1/.github/workflows/ci.yml#L13-L26
as we have https://pre-commit.ci/ ?
We would lose checking this against a grid of Python versions and old and new PyMc versions, but I do not think this is super necessary. Any thoughts?

I think that's fine, we are still running the tests against the old PyMC, no? That's the one that matters

Indeed!


Error on documentation?

Dear all,
there is probably an error or unclarity concerning the orleans server configuration.
In the section below in comments 4 and 5. Please see my thought about what should be there.
Kind regards
Emeric
.Configure<EndpointOptions>(options =>
{
    // 1 Port to use for Silo-to-Silo
    options.SiloPort = 11111;
    // 2 Port to use for the gateway
    options.GatewayPort = 30000;
    // 3 IP Address to advertise in the cluster
    options.AdvertisedIPAddress = IPAddress.Parse("<IP_ADDRESS>");
    // 4 The socket used for silo-to-silo will bind to this endpoint --> here it should be client to silo, not silo-to-silo?
    options.GatewayListeningEndpoint = new IPEndPoint(IPAddress.Any, 40000);
    // 5 The socket used by the gateway will bind to this endpoint --> here it should be silo-to-silo?
    options.SiloListeningEndpoint = new IPEndPoint(IPAddress.Any, 50000);
})

okay

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 2c693bc1-0e57-d0cc-e635-a5b39650ff76
Version Independent ID: c4efa180-e101-f723-2a36-73906469635f
Content: Server configuration
Content Source: docs/orleans/host/configuration-guide/server-configuration.md
Product: dotnet-orleans
GitHub Login: @IEvangelist
Microsoft Alias: dapine

Associated WorkItem - 46075

Related to dotnet/orleans#8209


python310Packages.asdf-standard: 1.0.2 -> 1.0.3

Description of changes
https://github.com/asdf-format/asdf-standard/releases/tag/1.0.3

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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 185787 run on x86_64-darwin 1

2 packages failed to build:

python310Packages.asdf
python39Packages.asdf

4 packages built:

python310Packages.asdf-standard
python310Packages.asdf-transform-schemas
python39Packages.asdf-standard
python39Packages.asdf-transform-schemas

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

8 packages built:

python310Packages.asdf
python310Packages.asdf-standard
python310Packages.asdf-transform-schemas
python310Packages.sunpy
python39Packages.asdf
python39Packages.asdf-standard
python39Packages.asdf-transform-schemas
python39Packages.sunpy


Trying to import Request from ullib breaks lib for Python 2

Using python 2, I get this for version 1.3.2. Version 1.3.1 works just fine.

pi@basiliscus:~ $ python /opt/tboplayer/tboplayer.py
Traceback (most recent call last):
File "/opt/tboplayer/tboplayer.py", line 75, in
from youtubesearchpython import SearchVideos
File "/home/pi/.local/lib/python2.7/site-packages/youtubesearchpython/init.py", line 1, in
from youtubesearchpython.videos__search import SearchVideos
File "/home/pi/.local/lib/python2.7/site-packages/youtubesearchpython/videos__search.py", line 3, in
from youtubesearchpython.__requesthandler import RequestHandler
File "/home/pi/.local/lib/python2.7/site-packages/youtubesearchpython/__requesthandler.py", line 4, in
from urllib import urlencode, urlopen, Request
ImportError: cannot import name Request

Sorry for inconvenience.

Hi there!
alexmercerind@10e301f6f2dc16d9f08da00bb09d8d12569936eb
Now after this commit module will use urllib2 on Python 2 for adding headers.
Please let me know if everything works fine now. After that, I'll update the version on PyPI.
Thankyou 🍀.
Also, I'll consider myself fortunate if you tell me if you are able to reproduce this issue on the latest version.

Hi, @alexmercerind ,
Now I am getting this:

Traceback (most recent call last):
File "tboplayer.py", line 75, in
from youtubesearchpython import SearchVideos
File "/home/pi/.local/lib/python2.7/site-packages/youtubesearchpython/init.py", line 1, in
from youtubesearchpython.videos__search import SearchVideos
File "/home/pi/.local/lib/python2.7/site-packages/youtubesearchpython/videos__search.py", line 3, in
from youtubesearchpython.__requesthandler import RequestHandler
File "/home/pi/.local/lib/python2.7/site-packages/youtubesearchpython/__requesthandler.py", line 22
headers = {"Accept-Language": f"{self.language},en;q=0.9"}

@heniotierra
I see you haven't made all the changes I made.
Please change your following line in your cloned code:
headers = {"Accept-Language": f"{self.language},en;q=0.9"}

with this:
headers = {"Accept-Language": self.language + ",en;q=0.9"}

I think you probably missed this change. Since, this kind of string formatting does not work in Python 2.


feat(rh-badge): add

What I did

Extended 'pfe-badge' and applied styling from the final rh-badge design

Testing Instructions

Notes to Reviewers

https://www.npmjs.com/package/@patternfly/pfe-spinner
apparently spinner next-6 got published under the latest dist tag :facepalm:
oh well, soon it'll all be /elements and there will be slightly fewer headaches

a potential fix for those failing tests: https://github.com/RedHat-UX/red-hat-design-system/pull/622

Looking at the code everything looks good to me, we might want to add some spec tests just to check on the padding and the border radius but since it's not really interactive (no buttons or moving pieces) it might not be too important.  Ran it locally and checked it out at https://deploy-preview-599--red-hat-design-system.netlify.app/components/badge/demo/ and it matches the specs in both places.  Looks great @marionnegp !


Upgrading Puppeteer from 1.1.1 to 1.3.0

Thanks @rashiagarwal!

1.3.0 has been tagged and built on Docker Hub too. Thanks again!

Thanks, @toolmantim!


Game ID

Hi,
Some games listed in https://www.xbox.com/en-US/games/all-games doesn't have game ID in the end of the game url. For example Madden NFL 22 Xbox One, Grant Theft Auto V: Premium Edition and so on.
How can I get the game ID for those games?

Good question. I have no idea. This is the first time I've seen a game without an ID.


chore: Add missing Dependabot schedule key

Noticed that the schema validation was flagging the missing key in VScode

Looks like there is a failure for missing secrets https://github.com/github/vscode-github-actions/actions/runs/4533514040/jobs/7986429046
Not sure if it actually needs to use the internal package repo or if it should be updated to the public NPM registry


Performance question, related to multiple effects

Hi all,
I'm having 1 FMsynth, 1 Membrane Synth, 6 Sampler tracks.
Using scheduled Transport.
Tried setting own context to 22000 rate.
Converted WAV to MP3
Each of my instruments have their own Effects, Reverb, distortion and a low pass filter.
Q: am I being stupid? I have thought it would be fine to have one reverb and distortion and just 'send' from each instrument, but I didn't so far see any example of using send. Would this have a positive impact on performance or not?
I sometimes get crackling and popping, I'm using a limiter so I'm wondering if it's my connections which are maybe unwisely configured.
Thank you

Short answer: it's probably the reverb which is one of the most expensive effects. Which type of reverb are you using? What kind of device are you getting glitching on?
It would definitely help to use single shared effects nodes where possible (as in, 1 reverb node that all source nodes are connected to). You can use individual gain nodes as reverb sends so you can vary the send amount from each source while only using a single reverb node.


yabai: refactor new sdk pattern; switch to apple-sdk_15; build from source; 7.1.4 -> 7.1.5

Things done
Using the new sdk pattern and cleaning up derivation. Also changing yabai on arm to build from source, finally, by using the llvm 19 stdenv.

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352621

x86_64-linux

aarch64-linux

x86_64-darwin

:white_check_mark: 1 package built:

yabai

aarch64-darwin

Had a hash issue hiding a build issue from source I need to find out. It looks like it's trying to do 2 builds at once and second xxd fails.

Arm64 builds, just need to see if x86 builds with llvm 19.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352621

x86_64-linux

aarch64-linux

x86_64-darwin

:x: 1 package failed to build:

yabai

aarch64-darwin

:white_check_mark: 1 package built:

yabai

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352621

x86_64-linux

aarch64-linux

x86_64-darwin

:white_check_mark: 1 package built:

yabai

aarch64-darwin

:white_check_mark: 1 package built:

yabai

Double checking the patch strategy...

@emilazy So, I updated to use the patch file strategy to make it clearer what the end file looks like. What i'm trying to double check though, is something I see in the build logs for the patching we're doing to get the SA to build and load.

ld: warning: object file built with an incompatible arm64e ABI: '/private/tmp/nix-build-yabai-7.1.5.drv-0/loader-49f623.o'
error: derivation '/nix/store/jp2954fyn57nfk7qk5zgc4frl4x9gq76-yabai-7.1.5.drv' may not be deterministic: output '/nix/store/3njvk50dqnhkj3hfl709iz97ksa4jlza-yabai-7.1.5' differs

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352621

x86_64-linux

aarch64-linux

x86_64-darwin

:white_check_mark: 1 package built:

yabai

aarch64-darwin

:white_check_mark: 1 package built:

yabai

I can confirm based on my azuwis@2725afe and upgrade to 7.1.5, the scripting addition works.

Speak too soon, after replaced system yabai with this build, SA crashed.

Interesting, I'm still running it on my laptop fine.

Try:
sudo yabai --uninstall-sa
sudo yabai --load-sa

and reboot.
You may be running a cached version? Check /Library/ScriptingAdditions/yabai.osax/Contents/MacOS/loader.

Ah yeah, looks like the ./result/bin/yabai --uninstall-sa wasn't actually removing it... running the old version --uninstall-sa worked to remove it and then running ./result/bin/yabai --load-sa loads that different version of it that doesn't work..

Might need you @azuwis to double check me... but simply building scripting additions against arm64 instead of arm64e got rid of the linker warning and seems to work for me...

I think the Mach-O universal binary with 2 architectures is a sign that the SA is a cached version, since the current nix patched makefile does not try to build multiple archs at all.

The problem is that sudo ./result/bin/yabai --load-sa just asks the yabai daemon to load SA, the SA is from your running yabai daemon, not ./result/bin/yabai.
The properly test this, your need something like:
  services.yabai.package =
    (import
      (builtins.fetchTarball {
        url = "https://github.com/NixOS/nixpkgs/archive/03bffabd6b96e7b260e1136af03b95e2dcb1ea72.tar.gz";
        sha256 = "";
      })
      {
        system = "aarch64-darwin";
      }
    ).yabai;

I run the command while running ./result/yabai

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352621

x86_64-linux

aarch64-linux

x86_64-darwin

:white_check_mark: 1 package built:

yabai

aarch64-darwin

:white_check_mark: 1 package built:

yabai

@emilazy This should be good now too. Moved building from source to a separate PR until we can figure out the arm64e scripting additions.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352621

x86_64-linux

aarch64-linux

x86_64-darwin

:white_check_mark: 1 package built:

yabai

aarch64-darwin

:white_check_mark: 1 package built:

yabai


Structuring solar meteorology terms

Description of the issue
We want to introduce a number of new terms regarding solar meteorology into the OEO. The first question we should discuss is, how to structure them into the ontology. The is a number issues associated with it:
"Type" of solar radiation

irradiation is an energy measured within a certain period of time (e.g. aggregated over an hour)
irradiance is a power at an instant. Irradiance integrated over time is an irradiation.
illuminace ist spectrally weighted irradiance focused on daylighting applications.

The "spatial distribution of radiation"

direct radiation directly comes from the sun
diffuse radiation is reflected and scattered e.g. by air molecules or clouds
global radiation is the sum of direct and diffuse

The way of measurement:

horizontal is meased on a horizontal plane which is parallel to the earth surface
direct is measured on a plane which is always directed towards the sun, e.g. the plane is perpendicular to the incomming direct light rays, a tracking surface
titlted is an arbitrary tilted plane (e.g. a tilted roof-top).

These properties can be combined, e.g. we have

"direct normal irradiance" which is a power of solar radiation measured on a surface oriented towards the sun and only considers the radiation which comes directly from the sun.
"global horizontal irradiation" is an energy which is collected on a flat horizontal surface from all directions.

The main questions is:
Do we need to define all permutations of the three groups as separate terms

direct normal irradiance
direct normal irradiation
direct normal illuminance
direct horizontal irradiance
direct horizontal irradiation
direct horizontal illuminance
.....

or can we define just the single words and can use combinations of the terms to annotate the data.
One further question:
We have

solar energy in in continuant->specifically dependent continuant -> quality -> energy -> radiative energy
solar radiation in occurrent -> process -> radiation -> solar radiation

Should we place energy related terms as irradiation in the first group and power related terms as irradiance in the second group? Or should we restructure this?
Ideas of solution
Option 1)

We just define the single words an can use combinations of it
Optoin 2)
We need to have definitions for all permutations.

Workflow checklist

[x] I discussed the issue with someone else than me before working on a solution
[x] I already read the latest version of the workflow for this repository
[x] The goal of this ontology is clear to me

I am aware that

[x ] every entry in the ontology should have a definition
[x ] classes should arise from concepts rather than from words

"Type" of solar radiation
* irradiation is an energy measured within a certain period of time (e.g. aggregated over an hour)

* irradiance is a power at an instant. Irradiance integrated over time is an irradiation.

* illuminace ist spectrally weighted irradiance focused on daylighting applications.

Things that you measure are neither energies nor processes but quantity values of some energies or processes, so these would be all in continuant -> generically dependent continuant -> information content entity -> quantity value. There we already have areal solar power density (alternative term: irradiance) and areal solar energy density (alternative term: irradiation). Concepts like direct normal irradiance will probably be subclasses of these. Illuminance however is a completely new concept, at least I did not find this word in the OEO.

The "spatial distribution of radiation"
* direct radiation directly comes from the sun

* diffuse radiation is reflected and scattered e.g. by air molecules or clouds

* global radiation is the sum of direct and diffuse

These sound to me as different ways, the light travels from the sun through the atmosphere, so I assume, these processes are subprocesses of our more general solar radiation class (Definition: Solar radiation is radiation that is emitted by the sun.).

Things that you measure are neither energies nor processes but quantity values of some energies or processes, so these would be all in continuant -> generically dependent continuant -> information content entity -> quantity value.

Usually, all quantity values should be related to their "entity in reality", which in the case of irradiation seems to be solar radiation.
With for energy transformation processes we introduced power as process attribute. We could think about having irradiance as its subclass, or directly link it to solar irradiation as well.
By the way: I think radiation should be classified as subclass of energy transformation/ energy tranfser.

By the way: I think radiation should be classified as subclass of energy transformation/ energy tranfser.

I agree, but then it should be redefined to: Radiation is an energy transfer by emitting or transmitting energy in the form of waves or particles through a spatial region or a material entity.

I just discovered that we have a whole set of light units imported from the Units Ontology:

I just had a look on this issue. Not everything is solved, but at least I see an consensus to make radiation as subclass of energy transfer. To move forward, I will implement this part.

For UO imports see also #1690

Is there update on the state of this issue?

hopefully soon...


chore(module): install deps before semantic-release

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement batch-contract (1.0 equivalent of canonical-transaction-chain contract)

Closing this, we will not use a contract, we can submit data in plain form to some configured address instead


User component

[ ] Login

[ ] Logout

[ ] Detect if user is logged in

[ ] Display username and avatar

[ ] User service as client-side endpoint of REST API

:dart: 1d


TC-DM-2.1 , 2.3 Chip tool testing: Few mandatory fields were missing

As per the test steps, the below mentioned fields are mandatory to check. Few of them were missing in the Chip Tool

Currently, only these mandatory fields are present in chip-tool.

@Garik098
Please re-test on master branch, I think we have supported all commands defined in the xml. Please note, you should only see request command from the controller side(chip-tool)
yufengw@yufengw-SEi:~/connectedhomeip/out/debug/standalone$ ./chip-tool operationalcredentials ?
[1644875979.535107][332165:332165] CHIP:TOO: Unknown command: ?
Usage:
./chip-tool operationalcredentials command_name [param1 param2 ...]
+-------------------------------------------------------------------------------------+
| Commands:                                                                           |
+-------------------------------------------------------------------------------------+
| * command-by-id                                                                     |
| * add-noc                                                                           |
| * add-trusted-root-certificate                                                      |
| * attestation-request                                                               |
| * csrrequest                                                                        |
| * certificate-chain-request                                                         |
| * remove-fabric                                                                     |
| * remove-trusted-root-certificate                                                   |
| * update-fabric-label                                                               |
| * update-noc                                                                        |
| * read-by-id                                                                        |
| * read                                                                              |
| * write-by-id                                                                       |
| * subscribe-by-id                                                                   |
| * subscribe                                                                         |
| * read-event-by-id                                                                  |
| * subscribe-event-by-id                                                             |
+-------------------------------------------------------------------------------------+

Closing this ticket as it was raised long back and the attributes were provided in the recent chip-tool.


Extract parquet statistics from Time32 and Time64 columns

Which issue does this PR close?

Closes #10751
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

BTW I am slowly merging these PRs after resolving conflicts -- I expect to be done by tomorrow

Thanks again @comphead  and @Lordworms


Increase price for garbage + recycling

Increase the price for garbage + recycling to $5.

@brandon-lind  Can I work on the issue?

@96RadhikaJadhav - thank you for the offer, but @graystripe208 has got this one.


[5.4] Clear the Carbon mock during tear down

I found that the Carbon\Carbon mock was not being clear after each test execution, causing some random tests failures.
This is fixed in https://github.com/laravel/framework/pull/19934 but i think that 5.4 users can also benefit from this.

It could break tests to do it on 5.4.


transaction.duration.sum.us, transaction.duration.count and transaction.breakdown.count should no longer be recorded (#2192)

What does this PR do?
Fixes #2192
Checklist

[x] This is something else

[x] I have updated CHANGELOG.asciidoc

@elasticmachine run elasticsearch-ci/docs


Added react version of the web app

Created a react version of the web explainer. Please let me know if there is anything that needs to be changed
https://user-images.githubusercontent.com/36244069/149459967-3eb5e168-f3f6-49c9-9700-6eb804c2f31c.mov

Amazing work @ahmed-adly-khalil! Love the UI improvements. I am worried about some of the dependencies we are going to take on though.

npm and node isn't available/installed everywhere. Some companies have a list of languages and tools, and this would block them.
react and tailwind means this won't be integrated as much. If a project is already using angular or vue they are going to disregard this project.

I am not against any of the libraries chosen. If we absolutely need them/can't ship without them it makes sense to use them. If they are just nice to have I think we should avoid using them. My hope is that we can keep this project is simple/easy to integrate as possible and grow from there.

Hello @Sean-Der
Sounds good, I will keep the same UI with pure JavaScript and remove deps. For css tailwind can be included as a script tag so I guess that would be ok?

Codecov Report

Merging #7 (fbee3d1) into master (78b1418) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##           master       #7   +/-   ##
=======================================
  Coverage   68.79%   68.79%
=======================================
  Files           7        7
  Lines         266      266
=======================================
  Hits          183      183
  Misses         79       79
  Partials        4        4

Flag
Coverage Δ

go
68.79% <ø> (ø)

wasm
36.81% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out 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 78b1418...e04825c. Read the comment docs.

@Sean-Der Done, I have converted to vanilla javascript + only tailwind CSS for styling and kept the exact same UI as the react version. Please let me know if further changes are needed


Allow usage of an existing db server

Instead of always deploying the postgresql subchart,
allow the usage of an existing database server.
This feature can be enabled via the helm variable
postgresql.external
and should be used in conjunction with
postgresql.enabled: false
Provide postgresql.postgresqlHost
in order to build a valid connection string.
closes #282

Hello and thank you very much for the contribution! ❤
I ask for a little patience, as I first need to clarify internally how to proceed.

Hello and thank you very much for the contribution! ❤
I ask for a little patience, as I first need to clarify internally how to proceed.


Support generating prop doc from Cesium's type

Extract prop type info from such as type EntityCesiumProps = HogeHoge & {};

close with #411


Also print gemspecs in bundle env

This change has the nice side-effect that bundle env will throw an error for Gemfiles with invalid DSLs.
Closes https://trello.com/c/QOX9jyYN.

Sample output: https://gist.github.com/agis-/2e753ebd4d89fc81d644.

👍🏻 if we can add a simple test for this

@segiddins Added test.
P.S. In the future I will add some more tests about Env.

Awesome!
@homu r+

:pushpin: Commit fb0de08 has been approved by segiddins

:hourglass: Testing commit fb0de08 with merge d79615a...

:sunny: Test successful - status


Update resolve-model-database-corruption-sqllocaldb.md

Adding important note to highlight that the described workaround/mitigation steps should only be applied if all conditions are true.

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


abrupt switch to Queues and DS in JavaScript Course

The JavaScript Course which is dealing with the basics of functions suddenly has a problem with Queues.

Then, the display code is too complex for the beginners, this lesson/challenge must be shifted somewhere below on the curriculum list. Here, is a screenshot of the challenge:

Then, the display code is too complex for the beginners,

Can you specify which part of the code you were referring to?
IMO, the Stand In Line challenge is introduced after several challenges on functions, arrays, array manipulations, returning values from functions, etc have been already presented. So, by this point, the challenge tasks - adding an item to the end of an array, and returning and removing the first array element should be pretty straightforward, even for beginners.
If you were referring to the terminology about the Queue at the beginning of the challenge being distracting/confusing for beginners, we could do something about that, since a knowledge of Queues is really not necessary for this challenge. Maybe it could be moved to the end of the challenge description, as a side note, mentioning this is how Queues work.

I was referring to the following code :

This challenge can be introduced in the Basic Data Structures part wherein the arrays are further expanded. This is just a kind suggestion as this seems a bit abrupt to start dealing with queues without even having the proper knowledge of arrays beforehand.
Please mention the appropriate file name so that I can make a PR and change the sequence appropriately. Hope you get my point. Thanks!!!

This is just a kind suggestion as this seems a bit abrupt to start dealing with queues without even having the proper knowledge of arrays beforehand.

@PragatiVerma18 I am not sure what you are talking about.  There are 9 challenges before this one on various aspects of arrays.  Everything the camper needs to understand has already been presented.


made a new contribution to networkx

improved test coverage for algorithms in richclub.py

Thanks @chimaobi-okite!


Fix issue 142, saving wrong number of coeff maps if NaN in input cubes

Fixes #142 , now without additonal commits

Fix already deployed on dev branch, so I'm going to close this PR and merge in the dev branch today. (Sorry Erik, I made you recreate the PR only to close it again!)


[CI] set up Java explicitly and use the built-in cache mechanism

The failures were so strange that I am even not sure whether this fixes the problem or not. Here are my observations:

https://github.com/apache/skywalking/runs/5966401737?check_suite_focus=true#step:6:25 in the failure case, I list the files under ~/.m2/repository and there indeed is no 9.1.0-SNAPSHOT versions.
Also in the same case 👆 when I manually upload the ~/.m2/repository folder and download it to my local machine, those 9.1.0-SNAPSHOT files are there. https://github.com/apache/skywalking/actions/runs/2146307624 see the artifacts maven-cache

This PR is just an attempt after I've run out of all my ideas 🤦🏻♂


PWM lidar ll40ls not working anymore

@kd0aij @julianoes ll40ls pwm does not work anymore after this https://github.com/PX4/Firmware/commit/aa9fbbedd54a7a0e346ea03f439dcdf4f90c6113
Any ideas why?

I think I know why. It is potentially similar to why camera trigger got broken. @davids5

@mhkabir Could you please add this to your list?

@ChristophTobler - did you test after https://github.com/PX4/Firmware/commit/8e217b028718fb6f0196e8a42ccff026a82c3215 came in?
@mhkabir here is more STM32 code in the wrong place perhaps you can remove all the timer code and refactor the PWMIn into the io_timer_driver - the stubs and resource allocation is there - just not the guts for PWMIn. Another possibility is the io_timer_driver Capture API. Things like "px4_arch_gpioxxxx" can live outside of /drivers/stm32 ut direct HW manipulations of Timer IP block can not.
Also see https://github.com/PX4/Firmware/pull/6993 and please test the PX4IO is running on V3 HW if after any changes you make add RAM usage to the common shared io timer code.

@davids5 this setup is on the Pixracer without PX4IO by the way.

@julianoes io_timer is just a nice API which David wrote to allow shared
access to the timer hardware on the STM32. e.g camera trigger running on
AUX (FMU) pins uses it.
It is not specific to the px4io, or something like that :)
On 08-Apr-2017 7:27 AM, "Julian Oes"<EMAIL_ADDRESS>wrote:

@davids5 https://github.com/davids5 this setup is on the Pixracer
without PX4IO by the way.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/issues/6994#issuecomment-292696319, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFTNrDA6YS6woqpbP9Z8EtUO0qQy9w5qks5rtxqogaJpZM4M2h4j
.

@julianoes Good to know, for testing. The comment about testing on PX4IO is because the io_timer code is a shared stm32 driver. Changes to that code effect the highly RAM constrained PX4IO and can trigger the out of memory "police lights" which most people do not notice, and then the future bug report is RC calibration is not working.

@davids5 It doesn't work with latest master

The lidar to pwm not fixed yet?

Is there a known version/commit where the PWM input works?

Yes it doesn't work after commit https://github.com/PX4/Firmware/commit/aa9fbbedd54a7a0e346ea03f439dcdf4f90c6113 as can be seen in the first comment

@ChristophTobler can you try on master again? If it still doesn't work, try changing the "pwm4" to "none" here : https://github.com/PX4/Firmware/blob/master/ROMFS/px4fmu_common/init.d/rcS#L468-L469

@mhkabir I'm currently on holidays and therefore cannot test it. But maybe @julianoes can give it a quick try on tuesday? Otherwise, I'll do it of course once I'm back.

@mhkabir I have tested it with latest master and it works. Thanks!

:D

What is this command suppose to show "nsh> pwm_input test"?

You should see samples of the measured pulse width e.g. 1500 us.

Should I see the pulses only if the Lidar is powered or I should see pulses regardless of that?

Only if it's powered.

Ok. Thanks! I will connect power to the servo rail.


Remove specific locales from links

Overview
Removes the en-us locale from links. This will allow a user's chosen locale to take over when a link is clicked, instead of defaulting to en-us.

/azp run mrtk_docs


Feature request: add wind speed in m/s for Weather Overlay similarly to ℃/℉ selector

Feature request
Please consider adding selectable m/s (meters per second) wind speed indicator similarly to ℃/℉ selector in Weatter Overlay.
Quoting Wikipedia:
Meters per second (m/s) is the SI unit for velocity and the unit recommended by the World Meteorological Organization for reporting wind speeds, and is amongst others used in weather forecasts in the Nordic countries.
Thanks!

Hey @shpokas
I went back and forth on the wind unit that went with celsius, early builds even had m/s but I can't remember why I went to km/h. In any case, since it's used in nordic countries, I'll try to fix that for next build.
Thanks !

Umm, just noticed that when forecast had been configured instead of current weather, then "m/s" in current weather is displayed along with km/h in the forecast.

Can confirm, from a quick look it's just the unit that is wrong, the values are I believe correct. Reopening and will fix for next version, thanks for the heads up!

Really appreciate that super quick fix! Tested with 3.2.6 and all is fine.
Thank you!


metrics(ticdc): fix slowest table metrics in scheduler

What problem does this PR solve?

Issue Number: close #10482
What is changed and how it works?

Record the correct progress in slowestTablePullerResolvedTs
For tables with equal checkpoints, set the table with the smallest resovedTs to the slowest table

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`.

/check-issue-triage-complete

/retest

/retest


exploitdb: 2023-06-01 -> 2023-06-03

Description of changes
update to 2023-06-03
commit tagged as 2023-06-03: https://gitlab.com/exploit-database/exploitdb/-/commit/5f38b443479a9d8af79f0937846e30d777719c1e

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

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

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

[X] Fits CONTRIBUTING.md.

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

1 package built:

exploitdb


[Feature]: help information for preview command

Expected behavior
I'm asking for this feature because I'm not 100% sure what this help message should actually be. Is it this?
→ bash-it help preview
Previews a theme (you will still need to modify your bash-it settings to choose this theme)

Current behavior
There currently is no help text for preview
→ bash-it help preview
oops! preview is not a valid option!
bash-it             Bash-it help and maintenance
parameters:
                    1: verb [one of: help | show | enable | disable | migrate | update | search | preview | version | reload | restart | doctor ]
                    2: component type [one of: alias(es) | completion(s) | plugin(s) ] or search term(s)
                    3: specific component [optional]
examples:

Possible solution
function _help-preview() {
        _about 'help message for preview command'
        _group 'lib'

        # I'm not certain what this message should be
        echo "Previews a theme (you will still need to modify your bash-it settings to choose this theme)"
}

Context
This is a curiosity-level problem. If you really stretch, it's a usability problem that there's no help message here.
Notes
No response

@jakebman, Can I Take This Issue ?


Leverage TypeScript 4.7 upgrade for deep type imports

Describe the problem
Right now we have to do ambient module hacks to define a public API through hand-written d.ts files for deep imports like @svelte/kit/hooks .
Describe the proposed solution
TypeScript 4.5 will support the exports field of a package.json along with a special import for types: https://github.com/microsoft/TypeScript/issues/33079#issuecomment-926946976
This means we could do
"exports": {
  "hooks": {
    "import": "./hooks.index.js",
    "types": "./types/hooks.d.ts"
  }
}

If we do this we require people to use a compatible version of TypeScript which would be breaking change, so it would need to happen before 1.0 ideally.
Alternatives considered

Keep the hack as-is for now and change it in v2
Add a post-build-script which copies handwritten types to a location like hooks/index.d.ts where TS should pick it up

Importance
would make my life easier
Additional Information
No response

TS 4.5 is out. We need to wait on Vite and ESBuild to update accordingly first and then do this and #2654 in one sweep.

Removed this from the 1.0 milestone, a backwards-compatible solution should be preferred for now. TS 4.6 at the earliest might contain stable support (which is more than 2 months from now) and even then it's not set in stone that everything will work reliably.

TS 4.7 will probably have the new resolution but we will likely not enforce it on the user (yet?). I don't know if export maps and type resolution will work for non-nodenext, too. If not, we won't be changing this.

We're on TypeScript 4.7 and have added a types field here: https://github.com/sveltejs/kit/pull/2896
I don't know if we want to add types for each sub-export? I'm changing this to 1.0 milestone since it sounds like it'd be a breaking change and there's no other blockers. Feel free to close it if it's already done

Not sure if we should do this in the near future. TypeScript ignores the package exports map if you don't opt in to the new module/moduleresolution (Node16 or NodeNext) - but if you do opt in to these, you are also required to adhere to the "always add explicit file endings" rules, so you need to write imports like import { foo } from './bar/index.js instead of import { foo } from './bar';

Does this work with bundler? If so, then I think we could start doing this

This is obsoleted by the the dts-buddy approach of having one big ambient module file, therefore closing right away - but yes, bundler would also enable this.


Fixes issue while closing many tabs.

Fixes #22399.

Fixing the build issues now

Could you squash the commits together? See PR workflow.

Done, I think.

Moving to 3.2 milestone as we're about to enter the beta stage and release freeze for Godot 3.1. Only bug fixes against issues of the 3.1 milestone (or enhancements to core features of the 3.1 roadmap) will be considered until 3.1-stable is released.
Note: If it's merged after 3.1-stable is released, this change may be considered for cherry-picking into a later 3.1.x release.

Closing as there are issues which are not being addressed, so it can't be merged.


[FeatureRequest] Include the type of request in the ShareIntent?

First of all, thanks for the plugin, it was crucial for an app that I'm building!
I have a feature request. It seems that when the intent either contains a WebURL or a text, both end up in the ShareIntent in the text field. Can we maybe add a type union field in the share intent that contains the original intent type? Thanks!

👋
That's sounds like a good idea !
You mean something like this :
type ShareIntent = {
  files: ...;
  text: string | null;
  type: "text" | "url" | null;
};

what about this :
type ShareIntent = {
  files: ...;
  text: string | null;
  link: string | null;
};

under the hood i only have this information on iOS, it's always a text on android. so for compatibility reason i have to do a manual check with something like that
    const link: string | undefined = first(
      text?.match(/[(http(s)?)://(www.)?-a-zA-Z0-9@:%._+~#=]{2,256}\.[a-z]{2,6}\b([-a-zA-Z0-9@:%_+.~#?&//=]*)/gi),
    );
    if (!link || !link?.startsWith('http')) {
      console.log('wrong link:', link, text);
    } else {
      console.log('text contain a link', link)
    }

for example when you share a link from the amazon app it comes with some text before the real url, so we need to isolate the information.
The better way to add this feature is to have text (with raw data) and link return by the hook :
const { shareIntent } = useShareIntent();
console.log(shareIntent.text); // "Hello, click on my link http://example.com"
console.log(shareIntent.link); // "http://example.com"

Alright, it's on my TODO :)

@MohamedBassem available in v1.2.0! see README for more details.
I also add some informations about type and filename.


feat: update Proposal layout

Summary
Closes: https://github.com/snapshot-labs/sx-ui/issues/557
Depends on: https://github.com/snapshot-labs/sx-ui/pull/570
Currently no separate results/quorum section, pending some questions being answered.
Everything that was not included on the design was kept in main section (actions, execution etc.)
Screenshot

The font-size for the content of the proposal should be 22px
Font-size for title should be 36px
Right sidebar should have a left border
"Your voting power", "Cast your vote" and "Results" title should use same style than others labels with eyebrow class


pin pv-site-prediction to 0.1.16

pin pv-site-prediction to 0.1.16
and pin other ones too

@peterdudfield Do you mean on the requirements.txt file, the version of pv-site-prediction should be 0.1.16? And the rest of the libraries should be fixed to whatever their latest versions are?

Yea, that would be great

This is linked to #14

Hello @peterdudfield , do we need to work on this issue?  I think it is already addressed by #61


Documentation says nothing about Test object and where it came from.

Need more documentation for Test object. Otherwise unclear what it is and how it should be defined.
const value = new Test(

{ x: 255, y: 20, z: '123', q: [1, 2, 3] }

);

What is Test? What is its definition?

Read the top of this test file https://github.com/near/borsh-js/blob/master/borsh-ts/test/serialize.test.js

I agree that the Test object should be defined in the docs... or at least that serialize.test.js should be linked.

should be fixed now, please open again if not


Frame technical plans as a way to make decisions

@dleve123 and I have been working for some time on defining a process for making technology decisions at Artsy. While the solution we landed on seems straightforward, I want to describe our process so that it's clear how we ended up here.
First, the rationale. Not all engineers at Artsy are familiar with how we make decisions (we saw this in recent Culture Amp surveys). There is a desire to know how we make decisions, and having a documented process is really important to make sure we build+maintain a culture where every engineer feels like they have a voice.
Daniel and I worked through a few different models, but none of them really suited our team. They were good frameworks, but introduced more and more process. This ran contrary to our Engineering Guiding Principle of Minimum Viable Process. We realized that any process for making decisions will have significant overlap with our existing technical plans (see #245) so we decided to lean into that overlap. Rather than use two processes for technical planning and technical decision-making, we should use the existing technical planning process for decision-making.
This is quite a shift, and will take time to socialize it. Daniel is going to run this through the paces on the Auctions team and, in the new year, I'm going to lead a Lunch & Learn discussion so we can retrospectively write a technical plan for decisions that we've already made. This is an ongoing process, and everyone's feedback is super-valuable.
To get us moving in the right direction, I've amended the (already-improved, thanks @joeyAghion!) technical choices doc to emphasize the usefulness of technical plans for making decisions. The documentation has a little extra pep so as to encourage engineers to write plans. I'll make a larger announcement on Slack and in Monday's standup.
I'm assigning this to @dleve123 because we worked on it together, and have requested a review from @xtina-starr because her input through the Peer Learning Working Group was super-valuable, ultimately pointing us in this direction.

I think it would be good in some form to differentiate between when to use technical plan vs when to use an RFC.

@zephraph makes sense! I think that might fit well within the FAQ section.

@zephraph I've added a clarifying section here, and am curious what you think: https://github.com/artsy/README/pull/277/commits/a898bf596cd9f582648a2d9a8da09f182267736a


Update blog: Kubernetes v1.26: Retroactive Default StorageClass

The version notation for Kubernetes  should be consistent.

Change the command line kc to kubectl.

kc is an alias of "kubectl", which has the same usage as kubectl. However, in some cases, there may be command conflict issues with kc.

According to the Documentation Style Guide, adjust the article content to comply with the guidelines of Don't include the command prompt and Separate commands from output.

Thanks
BTW, blog articles don't have to follow all the docs style guidelines (but following them is still helpful).
@RomanBednar are you happy to see these changes made?

/approve


Something went wrong -> addwstr() returned ERR

I've already updated the dependencies, setup my config as usual but it fails to start

Turns out I need to run it on full screen mode, else it will reproduce the same error


Variable flat file configuration

Hello yay.sh parsing:
Previous to commit e042818e69f030d61965501a7b624713547afc74 top level variables were present in both rhel-labs and rhel-labs-functions.cfg. This created a situation where it would be difficult to maintain down the road. Using a previously written parser from: https://github.com/HumanNeuroscienceLab/gunther/blob/master/include/yay.sh allows a flat yaml file to be parsed for variables and shell commands allowing nesting of variables.
Special thanks to Red Hatters Kambiz Aghaiepour and Will Foster who relayed they use this parser for quads internally for maintaining shell scripts: https://github.com/redhat-performance/quads/blob/master/bin/yay.sh. With a little bit of research on my end I was able to with in minutes adapt this to RHEL-LABS, however the rewrite of rhel-labs and rhel-labs-functions.cfg to facilitate this parsing has taken roughly a week.
File changes implementing the parser:
https://github.com/vidurous/rhel-labs/blob/master/yay.cfg
https://github.com/vidurous/rhel-labs/blob/master/load.cfg
https://github.com/vidurous/rhel-labs/blob/master/conf/var.yml

Fixed #19 in commit e042818e69f030d61965501a7b624713547afc74

Correction parses to Yamlesque not YAML
Yamlesque has a structured syntax that is a small subset of YAML. Valid Yamlesque is also valid YAML but the reverse isn't necessarily true due to Yamlesque only supporting a basic subset of the YAML syntax. The name Yay is a reminder that Yaml ain't Yamlesque!
Valid Yamlesque will pass a YAML validity check: http://www.yamllint.com. The full YAML specification is at http://yaml.org. Yamlesque meets the following format specification:
   <indent><key>:[<value>]


In some cases Naviganto can't go back

Create a test that recreates a first level route, that can reproduce this bug

8eb64ac closes this issue


Bug: Milestone Due column in project table can display erroneous information when the project has non-milestone reporting requirements[7]

Describe the Bug:
Probability (how likely the bug is to happen, scored from 1-5): 4
Effect (how bad the bug is when it does happen, scored from 1-5): 3
Steps to reproduce the behaviour:
Unclear - Project 144 in our prod data is impacted
This is likely due to our project_next_milestone_due_date also taking into account in deleted reports

I see project_next_milestone_due_date only takes care of milestone reports while Lindsey mentioned Summary Reports in the team's channel post which is a different report type. should we change the logic of this function and consider summary reports too?!

For the "milestone" column of the projects table, I think we only need to take milestones into account, so I'd say no

The title was misleading, it's not happening only when the project has non-milestone reporting requirements

@Sepehr-Sobhani  it's unclear what I need to test here - is it something you can confirm is in dev?

In this ticket, we excluded archived reports from project_next_milestone_due_date so we can have an accurate due date. This is now in PROD.


Add tools icon/improve metadata

Alternatives (including possible alterations to pencil…)

Maybe a bit big and maybe a bit hard to point out what the icon is supposed to convey.

Maybe a bit big

It’s using exactly the proportions of ruler and pen[cil]…

a bit hard to point out what the icon is supposed to convey.

Meant to represent tools/utilities/design/illustration/technical drawing/sketch etc…

Not sure about the name: tools, I think we can better name it as ruler-pencil or pencil-ruler.

@ericfennis I think pencil-ruler, since the pencil is the front/overlapping element… A similar approach to the naming in #1156.

What about naming it stationery?

What about naming it stationery?

I think pencil-ruler is more in line with the general approach to naming. But that should definitely be added to tags…

IMO pencil-eraser should become the new pencil and have an alias as edit-2.
pencil-eraser and edit-2 could then be removed.

pencil-line should also have the eraser IMO.

I think we can have both pencil and pencil-eraser

Surely it should be pen and pencil then…?

pencil-line should also have the eraser IMO.

Yes, I wholeheartedly agree, without the eraser, it looks a bit too much like an airplane.

I think @jguddas was referring to what is currently named edit-3…?

@karsa-mistmere @jguddas @ericfennis See latest changes…

Nice work, @danielbayley!


Added Release Drafter to Repository

Signed-off-by: Anthony Oyakhilome Justice<EMAIL_ADDRESS>

Hello @oyakhilomee there’s no content in the commit file, kindly push. And also do well to edit your PR message and mention the issue fixed.
“This PR fixes #issuenumber 😊


Add support for CameraSerialNumber

Camera Serial Number is part of the SMPTE 2065-4 spec, and does exist in Arri (as CameraSerialNumber) and Red (Camera_PIN), and I suspect for Sony Venice, its mxf/camera Attributes.
This is super useful for uniquely identifying the camera body, and its common to do lens charts recording both the camera body SN and the Lens SN, so we map cases where the camera body is producing an off center lens axis.

See https://smpte.slack.com/archives/C04E88H4FNJ/p1674757096673189 re: Sony Venice

I would recommend we add additional fields for camera manufacturer, model, serial number, and firmware version. These are all fields that exists in ANSI E1.59, a standard with which we should aim to be compatible.

Agreed to call out those four fields as individual records to make filtering and switching easier, and hope that the vendors use semantic versioning for their firmware version info.

Below are the camera and lens identification fields:

lens_make
lens_model
lens_serial_number
lens_firmware
camera_make
camera_model
camera_serial_number
camera_firmware

@repentsinner @makkbe @richardssam Please review #62

LGTM.
RED exposes user-editable SLATE_CAMERA_ID and SLATE_CAMERA_POS fields that are useful for identification, but not sure if they have parity fields from the other vendors.


test.sh would be much nicer if it supported --test_filter

Repeatedly running all 150+ tests + integration tests is frustrating when I just want my 0.01s test to run.

https://github.com/tensorflow/minigo/pull/507


Missing feature:  Hide columns from...

Missing feature to hide all columns from a certain column to the rest of the worksheet.
This way the worksheet will look like a real sheet which ends (has a boundary) at the right side
Need to adjust:
ZIF_EXCEL_SHEET_PROPERTIES:  Add attribute to hold column from where to hide all columns,
ZCL_EXCEL_WRITER_2007 to make use of new attribute
ZCL_EXCEL_READER_2007 to allow templates with this feature

Added with revision 444


[SPARK-34000][CORE] Fix stageAttemptToNumSpeculativeTasks java.util.NoSuchElementException

What changes were proposed in this pull request?
From below log, Stage 600 could be removed from stageAttemptToNumSpeculativeTasks by onStageCompleted(), but the speculative task 306.1 in stage 600 threw NoSuchElementException when it entered into onTaskEnd().
21/01/04 03:00:32,259 WARN [task-result-getter-2] scheduler.TaskSetManager:69 : Lost task 306.1 in stage 600.0 (TID 283610, hdc49-mcc10-01-0510-4108-039-tess0097.stratus.rno.ebay.com, executor 27): TaskKilled (another attempt succeeded)
21/01/04 03:00:32,259 INFO [task-result-getter-2] scheduler.TaskSetManager:57 : Task 306.1 in stage 600.0 (TID 283610) failed, but the task will not be re-executed (either because the task failed with a shuffle data fetch failure, so the
previous stage needs to be re-run, or because a different copy of the task has already succeeded).
21/01/04 03:00:32,259 INFO [task-result-getter-2] cluster.YarnClusterScheduler:57 : Removed TaskSet 600.0, whose tasks have all completed, from pool default
21/01/04 03:00:32,259 INFO [HiveServer2-Handler-Pool: Thread-5853] thriftserver.SparkExecuteStatementOperation:190 : Returning result set with 50 rows from offsets [5378600, 5378650) with 1fe245f8-a7f9-4ec0-bcb5-8cf324cbbb47
21/01/04 03:00:32,260 ERROR [spark-listener-group-executorManagement] scheduler.AsyncEventQueue:94 : Listener ExecutorAllocationListener threw an exception
java.util.NoSuchElementException: key not found: Stage 600 (Attempt 0)
        at scala.collection.MapLike.default(MapLike.scala:235)
        at scala.collection.MapLike.default$(MapLike.scala:234)
        at scala.collection.AbstractMap.default(Map.scala:63)
        at scala.collection.mutable.HashMap.apply(HashMap.scala:69)
        at org.apache.spark.ExecutorAllocationManager$ExecutorAllocationListener.onTaskEnd(ExecutorAllocationManager.scala:621)
        at org.apache.spark.scheduler.SparkListenerBus.doPostEvent(SparkListenerBus.scala:45)
        at org.apache.spark.scheduler.SparkListenerBus.doPostEvent$(SparkListenerBus.scala:28)
        at org.apache.spark.scheduler.AsyncEventQueue.doPostEvent(AsyncEventQueue.scala:38)
        at org.apache.spark.scheduler.AsyncEventQueue.doPostEvent(AsyncEventQueue.scala:38)
        at org.apache.spark.util.ListenerBus.postToAll(ListenerBus.scala:115)
        at org.apache.spark.util.ListenerBus.postToAll$(ListenerBus.scala:99)
        at org.apache.spark.scheduler.AsyncEventQueue.super$postToAll(AsyncEventQueue.scala:116)
        at org.apache.spark.scheduler.AsyncEventQueue.$anonfun$dispatch$1(AsyncEventQueue.scala:116)
        at scala.util.DynamicVariable.withValue(DynamicVariable.scala:62)
        at org.apache.spark.scheduler.AsyncEventQueue.org$apache$spark$scheduler$AsyncEventQueue$$dispatch(AsyncEventQueue.scala:102)
        at org.apache.spark.scheduler.AsyncEventQueue$$anon$2.$anonfun$run$1(AsyncEventQueue.scala:97)
        at org.apache.spark.util.Utils$.tryOrStopSparkContext(Utils.scala:1320)
        at org.apache.spark.scheduler.AsyncEventQueue$$anon$2.run(AsyncEventQueue.scala:97)

Why are the changes needed?
To avoid throwing the java.util.NoSuchElementException
Does this PR introduce any user-facing change?
No
How was this patch tested?
This is a protective patch and it's not easy to reproduce in UT due to the event order is not fixed in a async queue.

Test build #133643 has started for PR 31025 at commit 7d0245e.

Test build #133643 has started for PR 31025 at commit 7d0245e.

Hi, @LantaoJin . Does this affect only Apache Spark 3.x?

Yes. Only branch-3.1 and master. branch-3.0 is fine.

Hi, @LantaoJin . Does this affect only Apache Spark 3.x?

Yes. Only branch-3.1 and master. branch-3.0 is fine.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38232/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38232/

Test build #133643 has finished for PR 31025 at commit 7d0245e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #133643 has finished for PR 31025 at commit 7d0245e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133643/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133643/


module is not compatible with puppet 4

Currently module assumes variables set in the class are available in called 'defined' types,
for instance, class newrelic::agent::php calls newrelic::php::newrelic_ini  and all it's variables are out of scope, so newrelic.ini.erb is not evaluated properly

I believe this is fixed in this commit from #44: https://github.com/fsalum/puppet-newrelic/pull/44/commits/80944948293768a00d9acffc09a6b55bb0f79c1a

To be honest I am not sure I understand, why this is a defined resource.
How one would create another instance of newrelic::php::newrelic_ini ?


Leads to task fix

Show "leads to" tasks when they are made available when a task is activated.

.deploy


[ja] add doc for cgroup

Add desrtiption of cgroup.
https://kubernetes.io/docs/concepts/architecture/cgroups/
close #38922

The target page on preview site:
https://deploy-preview-39085--kubernetes-io-main-staging.netlify.app/ja/docs/concepts/architecture/cgroups/

/lgtm
It looks perfect for me :smile:

/lgtm

/assign @nasa9084
Please check them when you have the time.


Pi 4 Compile error! fontinfo.h : No such file or directory

when I compile this project ON MY PI 4 as wiki said:
git clone https://github.com/seeul8er/DroneBridge.git
cd DroneBridge
git submodule init
git submodule update
cmake .
make
I got a error on the screen:
Building C object splash/CMakeFiles/db_splash.dir/main.c.o
/DroneBridge/splash/main.c:26:10: fatal error: fontinfo.h : No such file or directory
#include "fontinfo.h"
compilation terminated.
Does anybody occurred this error ??? PLS help!
Did this project lack of some code or Pi 4 lack of some library?
But this head file as I know, is just a font usage file, maybe used in OSD module.

As far as I know the Pi4 does not support OpenVG. However, the OSD & the splash screen require that dependency. You can compile and run the other modules by commenting lines 32 & 33 the the CMakeLists.txt.

As far as I know the Pi4 does not support OpenVG. However, the OSD & the splash screen require that dependency. You can compile and run the other modules by commenting lines 32 & 33 the the CMakeLists.txt.

but when execute the start_db, failed again..
seems that the code has deep relate to the osd module...
/etc/init.d/start_db: line 33: ./osd: No such file or directory


initSelection not set id but set  text

i use select2
when try use initSelection
it work and set text to dropdown list
but with out id or value

Can you expand upon the issue you are facing by adding a few more pieces of information to your bug report?

What steps can be used to reproduce the issue?
What is the bug and what is the expected outcome?
What browser(s) and Operating System have you tested with?
Does the bug happen consistently across all tested browsers?
What version of jQuery are you using? And what version of Select2?
Are you using Select2 with other plugins?

The contributing guide contains a useful section with a few questions which can help us track down the bug and speed up the process of finding a fix for it.  The creation of an isolated test case would also be useful.

I have same problem.
When i use initSelection on loading select2
initSelection: function (element, callback) {                                 var data = {                                     id: "1",                                     text: "Anything"                                 };                                 callback(data);                             }
visually its ok, in Select2 layout is shown, but the DOM element select behind, still empty. if i submit my form it will go blank.

This issue does not appear to conform to our contributing guidelines.
At any rate, this issue is extremely old, and initSelection is deprecated in v4, so I don't think we need to worry about it any more.


Build issues on Windows

Should address the issue: https://github.com/Islandora-Devops/isle-buildkit/issues/21
Address two issues:

Previously Windows EOL characters were used in some files not covered by .gitattributes.
Previously download files that did not download successfully would pollute the build cache.

Solutions:

Change .gitattributes so the appropriate files have the appropriate line endings.
For all download files check against a known checksum, if check fails remove the file from the build cache so it can be downloaded again.

@marksandford Mind giving this a test to confirm if it solves your issues?


remove redundant checks?

The consensus layer performs some checks on the block header which are also checked in the ledger layer. Should we remove this redundancy or keep it?

@edsko @nc6 any thoughts on this? It seems to me avoiding redundant checks would be preferable. If so, how can we do this?

This is mostly a question for @nc6 I think.

I’d be inclined to keep them in unless there’s a known performance issue?
Sent from my iPhone

On 18 Sep 2019, at 12:57, Edsko de Vries<EMAIL_ADDRESS>wrote:
This is mostly a question for @nc6 I think.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I’d be inclined to keep them in unless there’s a known performance issue?

Any reason for doing this?
Alternatively the ledger layer, thought the executable spec, could expose the validation functions to the consensus layer. But I don't know how easy it is to do this.

Sent from my iPhone

On 18 Sep 2019, at 16:37, Damian Nadales<EMAIL_ADDRESS>wrote:
I’d be inclined to keep them in unless there’s a known performance issue?
Any reason for doing this?

Not on the critical path. You may accidentally remove a check that is needed. Takes some human time.
Might be possible to automate. Might be possible to combine at a coarser granularity. Might even be more efficient to repeat the check. :)

the consensus layer does not call the CHAIN rule directly, so in fact we are not doing the header checks twice.


Responsiveness issue

When the ToC is too long, it overlaps the footer. It's not scrollable.
Live: https://www.ohidur.com/posts/free-developer-resources/

fixed in 621c83a


security clarifications

This PR clarifies security information for edge meshes.

@jhadobe can we add a note to the features section https://developer.adobe.com/graphql-mesh-gateway/mesh/ about WAF and DDoS? This is a great enhancement and worth calling out at high level.
I'm thinking something like

Advanced Security: WAF and DDoS protection for all your APIs

@jhadobe can we add a note to the features section https://developer.adobe.com/graphql-mesh-gateway/mesh/ about WAF and DDoS? This is a great enhancement and worth calling out at high level and then link to security page.
I'm thinking something like

Advanced Security: WAF and DDoS protection for all your APIs

Thanks @naomirobichaud! I've added the suggested bullet to #282


:robot: Add nanodump.vm

Automated PR from https://github.com/mandiant/VM-Packages/issues/378 :rocket:

@nos3curity this category would be Password Attacks

@day1player category updated. Ready to merge if you are good with that.


WIP) policy: add a decapod app for policies

https://github.com/openinfradev/tks-flow/pull/256
https://github.com/openinfradev/decapod-flow/pull/130
https://github.com/openinfradev/decapod-base-yaml/pull/265
https://github.com/openinfradev/decapod-site/pull/178
https://github.com/openinfradev/helm-charts/pull/206

다른 파일 수정없이 policy 앱을 추가한 내역입니다,

다른 것들과 충돌이 없으므로 임의 merge 하겠습니다.


DT accessors with defaults + default flags to 0

Fixes https://github.com/zephyrproject-rtos/zephyr/issues/25827
Add generic accessors for devicetree property values which accept defaults, and then use them to make all DT_FOO_FLAGS() APIs just return 0 if there are no flags set in the DT.
CC @NZSmartie

BK errors look unrelated. I will wait for the infra issues to get fixed then re-run.


Batch log requests

It would be nice to batch log messages that happen in quick succession. This would cut down on the number of network requests for errors that happen in tight loops, or anything else where multiple log messages are sent in quick succession. I'm not sure how to do this without potentially cutting off the last log messages if the user closes the page quickly after causing the log messages to be sent.
logger.batchLogDelay(1000) could make the logger wait 1000ms after receiving a log to send the original log and any logs that have been sent since the original one.

@jaketodaro This is something on my scratchpad for 1.0.  I'll make this the official story for it :-)  Thanks!


Warning Failling to release lock

Greetings, I know it's an old code, but using it I get this warning:
*Severity	Code	Description	Project	File	Line	Suppression State
Warning	C26115	Failing to release lock 'allotemp.1' in function 'ThreadPoolExecutor::on_worker_exit'.	 C:\Users\XXX\Documents\Visual Studio 2019\Projects\Test\thread_pool_executor.hpp	147
std::notify_all_at_thread_exit(workers_map_cv, std::move(lock));
I found there was a bug in VS 2019 but a fix was release with 16.10, right now I'm using 16.11.13, it should be fixed, do you get the same warning?
Thank you in advance (Y)

@AnDumu Hi. Sorry, I don't have VS compiler on my laptop so I can't check if this warning is reproducible on my side.
I have clang++ 13.1.6 only. It doesn't emit any warnings.


Move content from Blue Sky Demo notebook into docs

Most of this has already been salvaged, but at least one thing -- Tom's awesome fly scan plot -- has not. Once we get it all, we should nuke the notebook, which is way behind the current API and not as good a teaching tool as a the docs.

The fly scan plot has been superceded by LiveRaster, and everything in that "Blue Sky Demo" notebook is wildly behind the current API. Reopen if you want to give into the git history to revive some part of this.

everything in that "Blue Sky Demo" notebook is wildly behind the current API

Isn't that true of most of the stuff in the bluesky_git_repo/examples folder?

(because if so, should we do something about this examples folder?)

Based on a quick look, the examples scripts still look useful and working to me. Most are months more recent that the notebook, which IIRC has not been significantly changed since Day 3 of bluesky development.

Ah ok. Any objections to removing the outdated notebook?


17.17-beta2 broke Macro OtFs in the character sheet

The Fireball Quick Notes entry there is using /m instead of /:
* ["Fireball"/m Fireball] works, but
* ["Lightning"/:Lightning] does not work

This is also an issue in the new Quick Rolls feature #2028:


feat(theme-classic): store selected tab in query string.

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Implementation description

Selection stored according to this comment - serialized JSON with group ids as keys and __noGroup__ constant key for tabs that do not belong to any group. Downsides:

Ugly links - http://localhost:3000/docs/markdown-features/tabs?tabs={"__noGroup__"%3A"banana"%2C"operating-systems"%3A"win"}
In case of multiple tabs that do not belong to any group and have different tab item keys, this solution would only work for the last selected tab.

Selected key priority: search query > local storage > defaultValue prop > 1st tab with default specified > 1st tab.
@slorber can you please provide further explanation for this comment ? I identified the file that needs the changes as this, but it's not clear to me what is actually needed to be done. From my understanding, when you hydrate React components and build static HTML off it, you cannot know the search URL query params as they are only available during the actual request or am I missing something?

Let's use this PR as starting point for further discussion around UX/implementation.
Motivation
Allows for sharing tabs selection via URL - better UX.
Test Plan
Manual
Test links

https://deploy-preview-8225--docusaurus-2.netlify.app/docs/markdown-features/tabs#query-string
https://deploy-preview-8225--docusaurus-2.netlify.app/docs/markdown-features/tabs?current-os=ios#query-string
https://deploy-preview-8225--docusaurus-2.netlify.app/docs/markdown-features/tabs?current-os=android#query-string

Related issues/PRs
Closes #7008

For the hydration problem, I don't know exactly how we can solve it, but if would be really preferably if we didn't have that "hydration tab change" when React loads:

This can be particularly disturbing in case tabs have different heights. If an anchor is provided in addition to qs tabs, it can also mess-up with the scroll position.
Now this is likely not easy to solve so I won't block the PR if it can't be fixed, it can be handled later.

preferably if we didn't have that "hydration tab change" when React loads

Yes, the desired outcome is clear. The implementation is the question here since docusaurus uses SSG, not SSR. Curious about the solution though.
@slorber I have added the desired react router APIs, but unfortunately these break unit tests as they are not renderable on the server. I wasn't able to find similar scenario (react router APIs within unit tests) throughout the codebase. Could you please give me some pointers? Thanks!

Yes, the desired outcome is clear. The implementation is the question here since docusaurus uses SSG, not SSR. Curious about the solution though.

Unfortunately that's exactly why it's not easy. There are tricks to work around this in SSG (see dark mode or ThemedImage). Don't worry, we'll eventually figure out later in another PR.

looks better but not yet good enough 🤪

No worries, it's expected to be an iterative process so that we are on the same page as for the required implementation direction :)

I don't see how a function call is overkill here.

Yea, I see we are from different camps. Clean code is very subjective and although I don't agree with your opinions, I fully respect them and since you are the maintainer here, you have the upper hand ofc :D Refactored into more abstractions as requested. Let me know if that's enough or you would like me to split the custom hook into a separate file as well.

Hey! We are keen to use this feature for our documentation. Could you please confirm the release date?

Did some refactoring, fixes and docs improvements => should be ready to review.
Some things to review more carefully:

clicking a tab should not lead to scroll position changes (it did due to core scrollAfterNavigation())
how groupId and queryString work together => it makes sense to me the url qs choice overrides the localStorage choice

Please test the preview and let me know if you see anything weird

Looks like it works as I want it to 👍

May be a silly question - how can one access this feature update before v2.3 becomes live?


Perception warnings in State.init

Description
For example, we have ParentFeature and ChildFeature and if we have array of ChileFeature.State in ParentFeature.State it throws runtime perception warning
Code:
@Reducer
public struct ParentFeature {
   @ObservableState
   public struct State {
   	public var items: IdentifiedArrayOf<ChildFeature.State> = [ .init() ]

   	//...
   }

   //.......
}

Checklist

[ ] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
No perception warnings
Actual behavior
Have perception warnings
Reproducing project
No response
The Composable Architecture version information
1.15.0
Destination operating system
iOS 18.0
Xcode version information
Xcode 16.0
Swift Compiler version information
swift-driver version: 1.115 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.10 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0

@KirillZholnerovich I don't think this is a bug in the library and you have not provided a full reproduction for us to evaluate the problem.
It does sound like maybe there could be an observation issue in your application requiring a WithPerceptionTracking view, but we'll need more info to help. Please follow up in the discussion with some compiling sample code!


my code is not showing the variables in color

Type: Bug
I am unable to see the color for my variables and it is not letting me select my variables in tab options either

VS Code version: Code 1.84.0 (d037ac076cee195194f93ce6fe2bdfe2969cc82d, 2023-11-01T11:29:04.398Z)
OS version: Windows_NT x64 10.0.22635
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.88GB (8.31GB free)

Process Argv
--crash-reporter-id 0317c924-b542-43ed-a34b-192414d0c9d6

Screen Reader
no

VM
0%

Extensions (20)

Extension
Author (truncated)
Version

vscode-django
bat
1.14.0

vscode-tailwindcss
bra
0.10.3

python-environment-manager
don
1.2.4

python-extension-pack
don
1.7.0

vscode-html-css
ecm
1.13.1

copilot-chat
Git
0.10.0

vsc-python-indent
Kev
1.18.0

python
ms-
2023.20.0

vscode-pylance
ms-
2023.11.10

jupyter
ms-
2023.10.1003070148

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

vsliveshare
ms-
1.0.5892

autodocstring
njp
0.6.1

vscode-css-peek
pra
4.4.1

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.2.30

jinja
who
0.0.8

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263cf:30856253
vscaat:30438848
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
f6dab269:30613381
showlangstatbar:30737416
a2ce3375:30757347
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30869155
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30871694
pythonregdiag2:30871582
pyreplss1:30865275
pythonmypyd1:30879173
pythoncet0:30874138
pythontbext0:30879054

Sorry, I don't know what color you are talking about

My problem seems to have fixed itself but what was happening was that when I was writing code in python, when I was creating variables they were not turning blue as they should have and that made it become an issue as I could not call them with the tab option and it looked like plain text when it was notXavierSent from my iPhoneOn Nov 6, 2023, at 20:13, Rob Lourens @.***> wrote:
Sorry, I don't know what color you are talking about
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Support for styled components

Do we need some special treatment for styled components? At least I'm getting an unexpected error Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components for styled components like AnotherReactContainer in this example:
import styled from "styled-components";

export const SomeReactComponent = () => (
Test
);

export const AnotherReactContainer = styled.div`
  padding-bottom: 6px;
`;

Fixed in 0.4.5!


how to validate this feilds

when some elements is rendered after user input a value , the validation doesn't work.
this is a reproduction
http://codepen.io/jackpan/pen/yJpzPG
in this demo, the input that rendered after user input does'n work

@Nandiin

similar #249
The use-case is mostly identical, so you can refer to that.
The point is you are rendering a list of inputs using v-for directive but assigning a static validation field name ( in your demo, 'amount'), so the last item of the list overrides the former ones.  Dynamic field names are needed in this case.

This issue can be closed I think @kazupon

@Nandiin thank you  i closed it


Use actions/tool-cache to download and cache the buildevents binary

actions/toolkit provides utility functions to download, move and cache binaries in a cross-platform way.
https://github.com/actions/toolkit/tree/master/packages/tool-cache#download

Caching isn't that useful: https://github.com/kvrhdn/gha-buildevents/pull/7#issuecomment-662053395
But we do use @actions/tool-cache now: e81318b87fa99f03b17ccd0d9af6e7ac4ab248e1


Adding support for sending request headers in azure core rest request API

This feature is added to support sending additional headers in all azure rest requests. It will be used by migration extension to send the session id in all the requests we are making for SQL migration resources.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 3 (33.33%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.001%) to 42.476%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/azurecore/src/azureResource/utils.ts
1
2
50.0%

extensions/azurecore/src/extension.ts
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/azurecore/src/azureResource/utils.ts
2
6.42%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
26757

Relevant Lines:
57065

💛  - Coveralls


Add Find-PSResource parameter to only return highest result for version range

Summary of the new feature / enhancement
I would like Find-PSResource to have a switch parameter to only return the highest version for a given version range.
Proposed technical implementation details (optional)
No response

Thanks @ThomasNieto this is an interesting feature request, the work around today would be to filter the results...would like to see more feedback on this issue

@SydneyhSmith while I do have that workaround it is more complicated when trying to use wildcards or when multiple resources are returned as they would first need to be grouped then sorted (sorting does not work very well as outlined in previous issues due to Version and Prerelease and not having a semantic version property).


[BUG] Azure.Storage.Blobs cannot connect to azure blob storage on AzureIoTEdge when using Azure IoTEdge API proxy and HTTPS

Library name and version
Azure.Storage.Blobs v>= 12.15.1
Describe the bug
Dear Azure team,
currently we are using Azure IoT Edge v.1.4 on Ubuntu Server 20.04 with Azure Blob Storage container service (v.1.4.4-linux-amd64).
We have IoT devices that connects to Azure IoT Edge and also uses Azure Blob Storage on IoT Edge for uploading files.
When we use HTTP protocol with connections strings like:
"DefaultEndpointsProtocol=http;BlobEndpoint=http://<IP_ADDRESS>:11002/edgeblob;AccountName=edgeblob;AccountKey=<64 bit key>;"
everything is working fine.
Also connections from inside other containers with connection string like:
"DefaultEndpointsProtocol=http;BlobEndpoint=http://azureblobstorageoniotedge:11002/edgeblob;AccountName=edgeblob;AccountKey=<64 bit key>;"
is working fine.
Since we want to use secure protocol like HTTPS, we decided to use Azure IoT Edge API Proxy module: https://learn.microsoft.com/en-us/azure/iot-edge/how-to-configure-api-proxy-module?view=iotedge-1.4
We have successfully configured the latest version available of the proxy and configured the environment variable of the proxy: BLOB_UPLOAD_ROUTE_ADDRESS with the value azureblobstorageoniotedge:11002 since the communication between the proxy and the blob container is limited inside docker on the edge device.
We used this connection string for TLS connection on the IoT devices:
DefaultEndpointsProtocol=https;BlobEndpoint=https://iotedge/edgeblob;AccountName=edgeblob;AccountKey=<64-bit-key>;"
The endpoint is correctly resolved since the DNS is fine and also certificate are correctly configured on Edge device (EdgeCA is ok). Also the proxy is configured fine and at TLS level we have no errors.
The problem we encountered is this one form the APIs related to interaction with blob storage:
RESPONSE Status: 403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. Connection: [keep-alive] Content-Length: [0] Date: [Fri, 22 Mar 2024 08:15:35 GMT] Server: [nginx/1.22.1] X-Ms-Error-Code: [AuthenticationFailed] X-Ms-Request-Id: [459adac6-fbb8-43a4-8cbf-93671a39023b]
I've noticed that when using https connection string, the SDK does not compute well the signature for authorization.
We checked the time and machines are correctly synced. We are using volumes mount for Blob storage persistance on the edge so no errors related on file system permissions are present.
The problem I think it is related to the misunderstanding of the account name:

The problem is that the SDK, when parsing https connection strings, accepts only endpoint in the form https://blob-account-name.blob.ms-cloud-sub-domain. Delving into the SDK code, it seems that the parsing function does not take into account https urls in different forms.
In our case we have a blob endpoint like: https://iotedge/edgeblob, where iotedge is the FQDN name of the edge machine and the edgeblob is the container name.
When using http connection string with IP address it is fine:

Since in this case the parsing in the SDK takes into account the fact that an IP address is explicitly present.
I've tried to update to Azure.Storage.Blobs 12.19.0, but I'm getting a different error related to x-ms-version not being compatible with the blob storage on edge device.
How can I solve both problems?
Expected behavior
When using connection string behing Azure IoTEdge API Proxy from IoT Device
DefaultEndpointsProtocol=https;BlobEndpoint=https://iotedge/edgeblob;AccountName=edgeblob;AccountKey=<64-bit-key>;"
The connection from Azure.Storage.Blobs v >= 12.15.1 is fine and the IoT Application can upload and download blobs passing through the proxy.
Actual behavior
When using connection string behing Azure IoTEdge API Proxy from IoT Device
DefaultEndpointsProtocol=https;BlobEndpoint=https://iotedge/edgeblob;AccountName=edgeblob;AccountKey=<64-bit-key>;"
The connection from Azure.Storage.Blobs v >= 12.15.1 we face 2 errors:
With Azure.Storage.Blobs v 12.15.1 we have the error:
RESPONSE Status: 403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. Connection: [keep-alive] Content-Length: [0] Date: [Fri, 22 Mar 2024 08:15:35 GMT] Server: [nginx/1.22.1] X-Ms-Error-Code: [AuthenticationFailed] X-Ms-Request-Id: [459adac6-fbb8-43a4-8cbf-93671a39023b]
I've noticed that when using https connection string, the SDK does not compute well the signature for authorization.
We checked the time and machines are correctly synced. We are using volumes mount for Blob storage persistance on the edge so no errors related on file system permissions are present.
The problem I think it is related to the misunderstanding of the account name:

The problem is that the SDK, when parsing https connection strings, accepts only endpoint in the form https://blob-account-name.blob.ms-cloud-sub-domain. Delving into the SDK code, it seems that the parsing function does not take into account https urls in different forms.
In our case we have a blob endpoint like: https://iotedge/edgeblob, where iotedge is the FQDN name of the edge machine and the edgeblob is the container name.
When using http connection string with IP address it is fine:

Since in this case the parsing in the SDK takes into account the fact that an IP address is explicitly present.
With Azure.Storage.Blobs v >= 12.16.0 we have the error:
x-ms-version not supported. We suppose that with version 12.16.0 and higer the blob storage on iotedge is not supported with C# sdk
Reproduction Steps
We have successfully configured the latest version available of the proxy and configured the environment variable of the proxy: BLOB_UPLOAD_ROUTE_ADDRESS with the value azureblobstorageoniotedge:11002 since the communication between the proxy and the blob container is limited inside docker on the edge device.
We used this connection string for TLS connection on the IoT devices:
DefaultEndpointsProtocol=https;BlobEndpoint=https://iotedge/edgeblob;AccountName=edgeblob;AccountKey=<64-bit-key>;"
we face
RESPONSE Status: 403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. Connection: [keep-alive] Content-Length: [0] Date: [Fri, 22 Mar 2024 08:15:35 GMT] Server: [nginx/1.22.1] X-Ms-Error-Code: [AuthenticationFailed] X-Ms-Request-Id: [459adac6-fbb8-43a4-8cbf-93671a39023b]
Clocks are ok.
Environment
dotnet 8 applications
Azure.Storage.Blobs v >= 12.15.1

Dear Azure Team,
any update on this topic?
Thank you!

Update:
Using Azure.Storage.Blob v 12.8.4 and overriding class BlobContainerClient like shown in the below picture:

The connection is fine, but the library version is vulnerable so we cannot use it.

Hello!
Is there any news on this topic?
Thanks and kind regards.


Initial commit of invocation chunking support

Signed-off-by: Kevin Hoffman<EMAIL_ADDRESS>

Especially interested in your thoughts @stevelr as this has direct impact on wasmbus_rpc

Only real request is that I'd love to see a test with this working, is there a somewhat simple scenario that we could use to test this?

Yeah the tick is finding an actor I can use that has a contract that allows for a payload big enough to chunk


Specification for Versioning of CRDs

Initial draft for review and iteration.
2020-06-05 - Complete rewrite for new approach
2020-06-25 - Major update, including two case studies and diagrams

Pull Request Test Coverage Report for Build 127940478

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 32.44%

Totals

Change from base Build 125270582:
0.0%

Covered Lines:
1706

Relevant Lines:
5259

💛  - Coveralls

Abandoning thjs PR in favour of starting a fresh conversation with a wider audience.


Object move speed

Is there a requirement for object moving speed? I have a robot moving around 10-15 mph, can I use T265 to track the robot position?

How well this works will depend very much on the characteristics of the movement (not just speed, but also rotational velocity and accelerations) and the environment the robot is in. The only way to be sure of the tracking quality is to test T265 in your use case. We have seen T265 used successfully in robotics and drone applications with speeds similar to or higher than you suggest.
Also keep in mind that for robotics applications we strongly recommend wheel odometry input to achieve maximum quality.

I race in the DIY Robocars meetup in Oakland. https://www.meetup.com/DIYRobocars/ Currently, my car uses a Lidar and particle filter to locate itself. I am wondering if I can use T265 tracking to replace Lidar.

Thanks. I think I can at least use it to improve my odom, but Lidar and particle filters are still needed.

Hi @ArtlyStyles,
I am interested if you have any test result with T265?

Yes, please see my twitter https://twitter.com/SmallpixelCar/status/1152765212409229312 In summary, I think the device did a good job and was better than my wheel odom, but was not good enough to replace Lidar and my localization algorithm for my robocar.

Hi...thanks for providing the feedback. Will you be needing anything else on this particular topic or can we close this?
Also a few updates have been released since August which should improve performance even more if you have not given it a try yet.

Closed due to lack of further responses after 2 months.


Workspace Virtual Env not detected in Windows

Open integrated terminal in VSC on Windows
Create a new venv python3 -m venv venv
Wait & wait & wait... the folder venv does not appear in VSC
Similarly the extension does not detect this new venv folder.

I.e. file change detection doesn't seem to work on windows, VSC too might have similar issues, why else isn't the venv folder displayed in VSC.

Todo:

[ ] Note, if VSC does not raise the event, then no need to solve at our end, just file an issue on VS Code

TODO: File issue upstream on VSC


Dont insert empty reverts in state

Noticed here: https://github.com/bluealloy/revm/pull/626#discussion_r1301347468
We should check if revert is empty and not insert it.

Hi! Sorry for the naive question: I tried to give a look at it to become more familiar with this part of the codebase; is it possible this is the solution to the issue? Or am I skipping some storage related operations to do depending on AccountStatus?
--- a/crates/revm/src/db/states/bundle_account.rs
+++ b/crates/revm/src/db/states/bundle_account.rs
@@ -151,7 +151,7 @@ impl BundleAccount {
         let info_revert = if self.info != updated_info {
             AccountInfoRevert::RevertTo(self.info.clone().unwrap_or_default())
         } else {
-            AccountInfoRevert::DoNothing
+            return None;
         };

         match updated_status {

Hi! Sorry for the naive question: I tried to give a look at it to become more familiar with this part of the codebase; is it possible this is the solution to the issue? Or am I skipping some storage related operations to do depending on AccountStatus?
--- a/crates/revm/src/db/states/bundle_account.rs
+++ b/crates/revm/src/db/states/bundle_account.rs
@@ -151,7 +151,7 @@ impl BundleAccount {
         let info_revert = if self.info != updated_info {
             AccountInfoRevert::RevertTo(self.info.clone().unwrap_or_default())
         } else {
-            AccountInfoRevert::DoNothing
+            return None;
         };

         match updated_status {

Ah not exactly, maybe account info is not changed, but storage values could be, so revert for that should still be present.
It is a simple change to check but we need to check that both AccountInfoRevert is DoNothing and if storage.is_empty(). You probably need to refactor a few small things inside that fn and add is_empty() for AccountRevert.

Thanks a lot for the suggestion! Let me know if now is ok

Left comments there, but that is the right direction!


chore: bump std4 to change instances for Div Int and Mod Int

bors merge

bors merge

bors r+

So the notation / is fdiv right?

No, it's ediv now.


Set column format > Epoche time: Remember last used unit

I have lots of databases with lots of tables, which contain integer fields with unix epoche values.
One of the features of dbeaver I really like is its ability to display such integer fields as human readable  timestamp.
However, dbeaver assumes the unix epoche is given in milliseconds, and I have to switch to seconds every time.
It would be great if dbeaver would remember the last used unit and use it as default for the next time.

thanks for the suggestion

Done.

verified


pad_sentences

Hi,
I'm wondering where i can find an explanation of why we need to apply pad_sentences to text for the embedding layer and why the 2D transformation ? Thanks!

The input to an Embedding layer is a 2D tensor of integers. The first dimension is the batch size, the second dimension is the sequence length. So that's why all your sequences have to have the same size, and the simplest way to achieve same-length sequences is to pad the shorter ones with zeros.

Thanks for this straightforward explanation !


Microsoft.Build.Traversal: propogate well known global properties

See issue #207 for discussion on the change.

@jeffkl, do I need to update the version in version.json as well?

do I need to update the version in version.json as well?

Yeah I suppose it changes enough behavior, might as well bump the minor version.  Thanks for suggesting that