Problem with .wav files following the build_your_own_voice recipe

Hi Merlin Community
I have been trying to train a model using my own data following the recipe found in build_your_own_voice. Unfortunately, I have become stuck on step 3 "prepare_acoustic_features".
It seems like WORLD does not accept the format of the .wav files I am using - even though they are the same format as .wav files found in the VCTK speech corpus, which I have trained a model succesfull using.
When I run the script "copy_synthesis.sh" I get the following trace:
001
fmt (2) error.
error: The file is not .wav format.
Cannot open file /home/lbl/Desktop/features/f0/001.f0!
Cannot open file /home/lbl/Desktop/features/sp/001.sp!
Cannot open file /home/lbl/Desktop/features/bap/001.bapd!
terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
copy_synthesis.sh: line 52: 24517 Aborted                 (core dumped) $world/synth $nFFTHalf $fs ${resyn_dir}/$file_id.resyn.f0 ${resyn_dir}/$file_id.resyn.sp ${resyn_dir}/$file_id.resyn.bapd ${out_dir}/$file_id.resyn.wav
002
fmt (2) error.
error: The file is not .wav format.
Cannot open file /home/lbl/Desktop/features/f0/002.f0!
Cannot open file /home/lbl/Desktop/features/sp/002.sp!
Cannot open file /home/lbl/Desktop/features/bap/002.bapd!
terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
copy_synthesis.sh: line 52: 24534 Aborted                 (core dumped) $world/synth $nFFTHalf $fs ${resyn_dir}/$file_id.resyn.f0 ${resyn_dir}/$file_id.resyn.sp ${resyn_dir}/$file_id.resyn.bapd ${out_dir}/$file_id.resyn.wav
003
...
The .wav files I am using are not corrupt and play successfully.
To see whether there were some minor differences in the format of my .wav file compared to ones from the VCTK corpus I inspected the headers of the .wav files:
HEADER OF WAV FROM VCTK CORPUS:
Input #0, wav, from 'p347_002.wav':
Duration: 00:00:04.27, bitrate: 768 kb/s
Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 1 channels, s16, 768 kb/s
HEADER OF MY WAV FILE:
Input #0, wav, from 'C_002.wav':
Metadata:
comment         : To Audio Converter Lite (amvidia.com)
Duration: 00:00:04.46, bitrate: 771 kb/s
Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 1 channels, s16, 768 kb/s
Have anyone encountered the same issue? And if so, how did you fix them?
All help is appreciated!
Best regards,
Lauritz

I have fixed the issue by removing all metadata from the .wav files - it seems like the files are unable to be analyzed if they contain any form of metadata.


error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

I got this error when installing
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

@sonnv174 I cannot debug it with such little information, it may be caused by many reasons. But I suggest you to do more check on your installation of gcc and spconv, usually, the bug could be fixed by reinstallation of these modles. Please refer to Det3D for  the installation guidance.

I got this error when installing
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

I have had the same error using google colab, these setups managed to solve it ,you can modify it to match your env .
% cd /content/
% cd /content/CIA_SSD/cia/
!pip install -r requirements.txt
!pip install gdown
!apt-get install python3.6
!apt-get install python3.6-dev
% cd /content/CIA_SSD/cia/det3d/core/iou3d
! python setup.py install
%cd /content/
!git clone https://github.com/poodarchu/Det3D.git
%cd Det3D
!pip install -r requirements.txt
%cd /content/CIA_SSD/cia/
!pip install nuscenes-devkit
!python setup.py build develop
! pip install cmake==3.13.0
! sudo apt-get install libboost-all-dev
%cd /content/
! git clone https://github.com/poodarchu/spconv --recursive
! cd spconv && python setup.py bdist_wheel
! cd /content/spconv/dist && pip install *
!pip install torchvision==0.9.0
%cd /content/
!git clone https://www.github.com/nvidia/apex
%cd apex
!python setup.py install
% cd /content/CIA_SSD/cia/det3d/core/iou3d
! python setup.py develop

For me the origin of this error was "AT_CHECK". After I added following lines into the respective src files, the error was solved:
#ifndef AT_CHECK
#define AT_CHECK TORCH_CHECK
#endif
ref: https://github.com/mrlooi/rotated_maskrcnn/issues/31


Resolve 42: hdf5 exception in msvc debug builds

Changes
Switch to HDF5 C API to avoid incompatible binaries in debug builds.
Merge Request - GuideLine Checklist
Guideline to check code before resolve WIP and approval, respectively.
As many checkboxes as possible should be ticked.
Checks by code author:

[x] There is at least one issue associated with the pull request.
[x] The branch follows the naming conventions as defined in the git workflow.
[x] New code adheres with the coding guidelines
[ ] Tests for new functionality has been added
[x] A local test was succesful
[x] There is appropriate documentation of your work. (use doxygen style comments)
[ ] If new third party software is used, did you pay attention to its license? Please remember to add it to the wiki after successful merging.
[ ] If new mathematical methods or epidemiological terms are used, has the glossary been updated ? Did you provide further documentation ?
is present or referenced. Please provide your references.
[ ] The following questions are addressed in the documentation*:  Developers (what did you do?, how can it be maintained?), For users (how to use your work?), For admins (how to install and configure your work?)
For documentation: Please write or update the Readme in the current working directory!

Checks by code reviewer(s):

[ ] Is the code clean of development artifacts e.g., unnecessary comments, prints, ...
[ ] The ticket goals for each associated issue are reached or problems are clearly addressed (i.e., a new issue was introduced).
[ ] There are appropriate unit tests and they pass.
[ ] The git history is clean and linearized for the merge request.
[ ] Coverage report for new code is acceptable.

closes #42

Codecov Report

Merging #57 (424022b) into main (a45672f) will increase coverage by 0.03%.
The diff coverage is 35.23%.

@@            Coverage Diff             @@
##             main      #57      +/-   ##
==========================================
+ Coverage   62.40%   62.43%   +0.03%
==========================================
  Files          88       89       +1
  Lines        5881     5894      +13
  Branches     2063     2068       +5
==========================================
+ Hits         3670     3680      +10
+ Misses        536      528       -8
- Partials     1675     1686      +11

Impacted Files
Coverage Δ

cpp/epidemiology/secir/secir_params.h
32.21% <0.00%> (ø)

cpp/epidemiology_io/secir_result_io.cpp
29.03% <23.80%> (-4.66%)
:arrow_down:

cpp/epidemiology_io/hdf5_cpp.h
100.00% <100.00%> (ø)

pycode/epidemiology/epidata/getRKIData.py
93.46% <100.00%> (-0.03%)
:arrow_down:

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 40f25e3...424022b. Read the comment docs.


CIP-???? | On-chain Transaction Chaining

Once in a while, I see people raising issues that could be solved with transaction chaining if there where the possibility to have some additional guarantees on it.
There is no strict need for this proposal at the current state but I think it might prevent something more complex in the future.
(see rendered proposal in branch)

Seems like this is basically batched transactions as described in https://github.com/input-output-hk/cardano-ledger/issues/768

The goal/problem they try to solve is the same; however, I would say this is a different implementation if compared to do the description of the cited issue

Doesn't this imply that the chain of transactions must all be within one block? I can't see how to enforce the guarantee otherwise. And if so, doesn't this end up being much the same as batched transactions?

Doesn't this imply that the chain of transactions must all be within one block? I can't see how to enforce the guarantee otherwise. And if so, doesn't this end up being much the same as batched transactions?

Not necessarily; transactions can still be included in multiple blocks; the only thing needed for a chain of transactions is the existence of an output of a previous one

It seems to me that the main difference between this and batch transactions is that this lets scripts "see" that other transactions will happen, which is a major power increase and I'm not sure what I think about it.

That is the main idea of the proposal. The main use case (that I will add as soon as I edit the proposal) is the composability of transactions; keeping every transaction atomic on its own but under all aspects provides a way to be sure some other action took place (based on the output of the current).
In general this would give scripts the possibility to act like active entities.
This, as an example, allows for datum validation when creating a brand new UTxO in a script; where the first transaction creates the UTxO and the second spends that UTxO only to be sure that the datum is valid; if the second fails the first fails too, so the UTxO is never created.
Another use case, also based on the "acting like active entities" thing, is smart contract interaction; where a smart contract first performs an action (even expansive ones) and then forwards the validation to a script in a successive transaction that checks for the result of the previous and the presence of the target (external) contract; under all aspects emulating a contract call.

Not necessarily; transactions can still be included in multiple blocks; the only thing needed for a chain of transactions is the existence of an output of a previous one

So this doesn't ensure that the following transaction is ever made? It's much less clear what the point is, then. I thought this would allow scripts to ensure that another transaction happens, but in this case it wouldn't.

In order to be included in a block all the chained transactions have to be submitted an all have to be validated; if any of the transactions fails none is included; if all succeed then can be included as a normal transaction.
If the above doesn't make sense then is likely I'm missing something so please let me know how can improve there.

@KtorZ: ... proof-reading on the document as there are many little typos 🤓

@michele-nuzzi after you've given this your best effort let us know & I'll give it a good editing review. 😇

@michele-nuzzi marking Waiting for Author as per https://github.com/cardano-foundation/CIPs/pull/518.

@michele-nuzzi Why can't you just use minting policies for this? That is what I have been using for my applications.

The main use case (that I will add as soon as I edit the proposal) is the composability of transactions; keeping every transaction atomic on its own but under all aspects provides a way to be sure some other action took place (based on the output of the current).

This, as an example, allows for datum validation when creating a brand new UTxO in a script; where the first transaction creates the UTxO and the second spends that UTxO only to be sure that the datum is valid; if the second fails the first fails too, so the UTxO is never created.

This is literally how I use the minting policy. For example, when a borrower creates a UTxO to ask for a loan, they must mint an Ask token and store it in the UTxO. This Ask token can only be minted if the datum in the UTxO is valid (among other things). A lender who then wants to offer a loan must create a UTxO with an Offer token. The Offer token can only be minted if the offer is valid (datum, value, etc must all be valid). To accept a loan, the borrower must match up an ask UTxO with an offer UTxO with the added requirement that they contain an Ask token and Offer token, respectively. The very fact that the tokens exist means the UTxOs are valid. To use the terminology here, the presence of the tokens is proof that a previous transaction occured. I have successfully been able to compose my applications using this approach. For example, you can safely compose my dex, options trading protocol, and secondary market in a single transaction. They either all succeed or the transaction fails.

In order to be included in a block all the chained transactions have to be submitted an all have to be validated; if any of the transactions fails none is included; if all succeed then can be included as a normal transaction.

The approach I mention above has this property already. Why is this approach not sufficient?

yes that particular scenario is already possible without chaining transactions; as an example, I used a similar technique in this yield contract;
however, the contract tends to be more complicated because
in that particular case, I had a mutual dependency between the minting policy and the validator (policy checks for the asset to be sent to the validator and the validator checks for the policy to assert the validity of an utxo)
that implies "unsafe" type coercion and ad-hoc data design.
while the CIP won't remove the pattern (mutual dependencies are more common than I wish they were) it definitely makes the process much smoother and requires less mental gymnastic to achieve something like datum validation.
There are also many advantages in chaining transactions and having the guarantee that there is some transaction happening after yours.
In particular "batching" (but without third parties signing transactions)
where a bunch of different users would send a single witness transaction to some contract and then that contract would be a single witness to a chained transaction.
The above is also possible without third parties but that would imply having multiple users from all around the world having to sign the same exact transaction.
If that was easy we wouldn't have batchers at all today, but of course, that is not the case.
chaining transactions and having a guarantee of that on-chain allows contracts to act like active entities; without requiring an indefinite amount of users to sign the same exact transaction (they would sign theirs and then leave the contract to do its things)

@michele-nuzzi we are trying to trim the abandoned proposals from the CIP PR queue but it looks like this one is still relevant... despite being in Waiting for Author state for about a year... due to the mention in #880 (cc @fallen-icarus), so could you please look this over and let us know what we're waiting for here?
If you're standing by your proposal, and intend to carry it forward, please update the header & format according to the new CIP-0001 (I believe you are familiar with those specifics but please post if not).  Then based on your posting whatever's happened in the last year, we can change the status to something other than (potentially) Abandoned... until then, this tag marks it for closure if there are no further updates.


Draft import key error: 0

New key error when importing draft using v1.1.0 in this leagueId=373956 Let me know what other information can be provided. I see 1 empty draft slot, but I thought this was resolved with https://github.com/cwendt94/ff-espn-api/issues/21
`2019-09-11T02:06:15.710208+00:00 app[worker.1]:     bot_main("init")
2019-09-11T02:06:15.710211+00:00 app[worker.1]:   File "ff_bot/ff_bot.py", line 284, in bot_main
2019-09-11T02:06:15.710388+00:00 app[worker.1]:     league = League(league_id, year)
2019-09-11T02:06:15.710391+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.6/site-packages/ff_espn_api/league.py", line 54, in __init__
2019-09-11T02:06:15.710576+00:00 app[worker.1]:     self._fetch_league()
2019-09-11T02:06:15.710579+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.6/site-packages/ff_espn_api/league.py", line 77, in _fetch_league
2019-09-11T02:06:15.710716+00:00 app[worker.1]:     self._fetch_draft()
2019-09-11T02:06:15.710723+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.6/site-packages/ff_espn_api/league.py", line 195, in _fetch_draft
2019-09-11T02:06:15.710911+00:00 app[worker.1]:     playerName = self.player_map[playerId]
2019-09-11T02:06:15.710946+00:00 app[worker.1]: KeyError: 0
`

Interesting, for the other error I was seeing -1 as not player. This one is 0. I will create a quick fix for this and update

version 1.1.1 should have this fix.


[Metal Direct] Testing

We want a testing harness in python, we want to be able to write:
import torch
from ttmlir.dialects import ttir

# What the test harness could look like

class Add:
    def golden(self, a, b):
        return a + b

    def build(self, a, b):
        return ttir.add(a, b)

class TTIRBuilder:
    def create_ttir_tensor(...):
    def create_ttir_add(...):

# What a test definition could look like
def test_add(builder):
    torch.seed(0)
    in0 = torch.randn(64, 128)
    torch.seed(1)
    in1 = torch.randn(64, 128)
    golden = in0 + in1
    ttir_tensor0 = builder.create_ttir_tensor(in0)
    ttir_tensor1 = builder.create_ttir_tensor(in1)
    out = builder.create_ttir_add(ttir_tensor0, ttir_tensor1)
    builder.finish(input_seeds=[0, 1], golden_outputs=[golden])

This would build an MLIR graph in TTIR, then lower it to ttmetal dialect and then serialize to flatbuffer.  It will also embed the golden information directly in the flatbuffer.
TTRT will then be able to pop open the embedded golden info, regen the same inputs using the same seed, and compare the embedded golden output with the run from the device.  Sync with Taps regarding this golden support in TTRT which doesn't exist yet.
Reference:

test/python/tensor_layout.py this test already demonstrates creating MLIR from python
test/python/simple_kernel.py super prototype of writing a kernel in python and translating it to mlir, this test is fairly deprecated at this point and we'll almost certainly want to remove/change it.  But it does serve as a good reference building an MLIR graph in python

In the short term we should just bake all golden information directly into the flatbuffer in the debug_info.fbs area.  We can have a contract with ttrt that knows to look for golden info in that area and automatically does golden comparison / populates input data from there if exists.
debug_info.fbs:
table GoldenTensorDataBytes {
  data: [uint8];
};

table GoldenTensorDataSeed {
  seed: uint64;
};

table GoldenTensorDataURL {
  url: string; // local path or URL
};

union GoldenTensorData {
  GoldenTensorDataBytes,
  GoldenTensorDataSeed, // placeholder for future, we can store just the seed for random generated inputs instead of storing the full tensor data inline
  GoldenTensorDataURL, // placeholder for future, where we want to point to real weights / inputs
};

table GoldenTensor {
  ref: TensorRef; // Reference to tensor in the program that this golden corresponds to, shape info can be inferred from here too
  data: GoldenTensorData;
};

table GoldenInfo {
   golden_tensors: [GoldenTensor];
};

table DebugInfo {
  ...
  golden_info: GoldenInfo;
}

Assigning this umbrella issue to @tapspatel since he continued this effort.


lightbox_view: Fix media title update on change in title.

Presently in a session when an image or video title is updated, the same change is not reflected in the lightbox view of them, until a new session is made.
This is because the metadata of the media is stored in Map for the session with the preview_src as keys, and hence, when title is changed the preview_src being same, the title change is not reflected inside lightbox view.
This is fixed by modifing the asset_map (cache map) keys from preview_src to an array of preview_src, and the media title. Hence, when title is modified now, the keys won't map to the existing value, and hence new metadata would be shown.
Fixes: #21311

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Works for me in manual testing!

Merged, thanks @roanster007!

It looks like this caused us to trigger an exception if a lightbox is opened and left/right is pressed:
https://zulip.sentry.io/share/issue/49764529ea674b3999941513dea0311c/


How to save the raw images from .bag files using python?

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ R200 / F200 / SR300 / ZR300 / D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>

I hope that the Pyrealsense2 script in the link below for extracting the depth images from a bag and saving them to a directory will be helpful to you.
https://github.com/IntelRealSense/librealsense/issues/1887#issuecomment-397529590
The comments in the rest of the discussion below the script discuss its programming.

Case closed due to no further comments received.


FR: preview() action

1st, Thank you!
- [X] Etc.
- [X] Linux
- [X] zsh
Describe your problem or suggestion from here ...
Would it be possible to have a preview() action, like execute().

If you mean a way to change the --preview flag, I would also like to see this implemented :)

Added in 0.22.0.
https://github.com/junegunn/fzf/blob/master/CHANGELOG.md#0220

Thank you!


chore(main): release 1.0.7

:robot: I have created a release beep boop
1.0.7 (2024-12-03)
Bug Fixes

deps: update dependency @faker-js/faker to v9.3.0 (#286) (a6813e3)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

1.0.7
:sunflower:


Updating glog version to latest(0.3.5) which is the version RN is usi…

Please select one of the following

[X] I am removing an existing difference between facebook/react-native and Microsoft/react-native :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into Microsoft/react-native :thumbsup:
[ ] I am making a fix / change for the macOS implementation of react-native
[ ] I am making a change required for Microsoft usage of react-native

Description of changes
Updating glog version to latest(0.3.5) which is the version RN is using now
Focus areas to test
Verified that glog logging is working
Microsoft Reviewers: Open in CodeFlow

/azp run


Spesification Validation Error: Practitioner SDSUserId is populated with value which is not SDSUserId

**Bugs **
Practitioner SDSUserId is populated with value which is not SDSUserId

** Step to reproduce **

check 'multi_pathology_msg1.fhir.json'
Check practitioner identifier with system 'https://fhir.nhs.uk/Id/sds-user-id'
check that the identifier value is not an SDSUserId (seems something else, probably GMC code ??)

** Expected behavior **
The value should reflect the 'system' value, otherwise, it will be misleading.

We have no SDS User ID information in EDIFACT

NHS suggestion:

as we don’t know which system the identifier comes from, just leave the system out

RETEST 1
TEST STEPS TO REPRODUCE ISSUE
I re-ran request multi_pathology_msg and inspected the FHIR payload.
ACTUAL RESULT
multi_pathology_1_payload.txt

The System value no longer appears for Practitioner resource.
Retest 1 PASSED
Defect 122 Closed


Cannot import route 53 records that contain underscores

Steps to reproduce

create a record name with an underscore on route53
try to import the record using the [zone id]_[name]_[type]

Expected: import successful
Actual:
Preview failed: refreshing urn:pulumi:production::xxxx::aws:route53/record:Record::CNAME-xxxxx.dkim.amazonses.com: 1 error occurred:
    	* InvalidInput: 1 validation error detected: Value 'domainkey.xxxxx.com.' at 'startRecordType' failed to satisfy constraint: Member must satisfy enum value set: [AAAA, A, CAA, NS, SOA, SPF, MX, PTR, CNAME, DS, TXT, SRV, NAPTR]
    	status code: 400, request id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx

Contex:
I am trying to import dkim records that I made on terraform into pulumi. AWS makes dkims with an underscored in a [dkim]._domainkey.[domain] structure and pulumi identifies it as a split in the record ID.
Not sure if this is a bug or if I am not importing these records correctly. I have tried escaping the underscore to no avail.

Could you share an example of the command you're invoking to get that output?
Have you tried importing using the Import Resource Operation rather than the import command? Does the resource approach have the same issue?


Specimen details: preferably not in the basic viewer; is better in an extended protocol (no use for the physician)

This is solved in the visualiser: you can hide / show specimen details.


http connect exception occurs during region dropdown population

We get http connect exception during region dropdown population. This is intermittent but it would be good if we handle this exception gracefully. Refer screenshot for the error.

This issue doesn't occur anymore with the latest fix.


Fix a few manager tests that need polling

These tests were expecting something to happen instantly or after a fixed sleep. This isn't reliable.
Fixes #2088

Rebased now that #2092 was merged.

I think there may have been a rebase issue with https://github.com/docker/swarmkit/pull/2092 - looks like cautils is still the thing imported as testutils

Indeed the rebase went wrong. Fixed.

LGTM


Fix or improve client build docs

I am trying to build my own client talking to its own sync server.
I have built the sync server using docker build -t prompta . and run it using docker run --name=prompta -p 8080:8080 prompta.
To use  it, I understand I have to serve the client over http to allow it to access the server on http://<IP_ADDRESS>:8080/.

If I try to build the client as per https://github.com/iansinnott/prompta?tab=readme-ov-file#developing I get the following errors:

$ docker run --rm -it -v ~/Downloads/prompta/:/prompta --entrypoint=/bin/bash -w /prompta node:20

root@430ead86902b:/prompta# npm install
npm notice
npm notice New minor version of npm available! 10.2.4 -> 10.3.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.3.0
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/svelte
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/svelte-check
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!   3 more (svelte-preprocess, svelte-preprocess, @sveltejs/kit)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/svelte
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/bits-ui
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /root/.npm/_logs/2024-01-18T22_47_16_576Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-01-18T22_47_16_576Z-debug-0.log

root@430ead86902b:/prompta# npm run build

><EMAIL_ADDRESS>build
> tauri build

       Error failed to get cargo metadata: No such file or directory (os error 2)

Alternatively if I try using pnpm as per the Dockerfile I get this error:

root@430ead86902b:/prompta# apt-get update; apt install -y curl python-is-python3 pkg-config build-essential
Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:2 http://deb.debian.org/debian bookworm-updates InRelease [52.1 kB]
Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:4 http://deb.debian.org/debian bookworm/main arm64 Packages [8685 kB]
Get:5 http://deb.debian.org/debian bookworm-updates/main arm64 Packages [12.5 kB]
Get:6 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages [132 kB]
Fetched 9080 kB in 2s (4275 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
curl is already the newest version (7.88.1-10+deb12u5).
pkg-config is already the newest version (1.8.1-1).
pkg-config set to manually installed.
The following NEW packages will be installed:
  build-essential python-is-python3
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.7 kB of archives.
After this operation, 35.8 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main arm64 build-essential arm64 12.9 [7704 B]
Get:2 http://deb.debian.org/debian bookworm/main arm64 python-is-python3 all 3.11.1-3 [3000 B]
Fetched 10.7 kB in 0s (41.2 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package build-essential.
(Reading database ... 23282 files and directories currently installed.)
Preparing to unpack .../build-essential_12.9_arm64.deb ...
Unpacking build-essential (12.9) ...
Selecting previously unselected package python-is-python3.
Preparing to unpack .../python-is-python3_3.11.1-3_all.deb ...
Unpacking python-is-python3 (3.11.1-3) ...
Setting up build-essential (12.9) ...
Setting up python-is-python3 (3.11.1-3) ...
root@430ead86902b:/prompta# npm install -g pnpm

added 1 package in 1s

1 package is looking for funding
  run `npm fund` for details
root@430ead86902b:/prompta# pnpm install
Lockfile is up to date, resolution step is skipped
Packages: +411
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 ERR_PNPM_LINKING_FAILED  Error: ENOENT: no such file or directory, copyfile '/prompta/.pnpm-store/v3/files/4e/e1c88f8c3f4e4cd34cb6c00339bf9d6d036ff4ade3af49e871cc8966b84c729d8b75492acc6413c9a664ac00a57958223ac13c4229da8c62ebe6a53e4f783f' -> '/prompta/node_modules/.pnpm/bits-ui<EMAIL_ADDRESS>Progress: resolved 411, reused 0, downloaded 105, added 89

The server build should be relatively simple since it only requires typescript compilation (no bundling, and no Rust dependencies). Try building the server directly first:
pnpm i
pnpm tsc -p ./tsconfig.server.json

At that point it's a standard node.js server which you can run via:
node ./dist-server/server.js

Thanks for this. These commands do (now) work, and it turns out at least part of my problem was that I was trying to build inside a repo directory that was bind-mounted from my Mac. This led to the ERR_PNPM_LINKING_FAILED error. Additionally, I found that building from source on an overlay filesystem (e.g. inside a plain docker container) can cause node-gyp build to fail.
Building inside a fresh copy of the repo in a Docker volume inside a container, or using docker build seems to work (and I don't really know why the docker build failed before when I raised this issue).
I've also managed to launch my sync server behind https and resync my local chat.prompta.dev storage to it. So far so good!
I also managed to build and load the client, but had to add NODE_OPTIONS="--max-old-space-size=2048" before pnpm build ui:build and pnpm build ui:build-static.
I think you can close this issue, but I suggest modifying Dockerfile and docs to add NODE_OPTIONS="--max-old-space-size=2048" to the client build instructions.
It would be neat if the sync server could also serve the static client, so that everything can be built and run off one IP and port. In the meantime here is a Dockerfile that builds and (hackily) serves both client and sync server.
FROM node:20 as builder

RUN apt-get update; apt install -y curl python-is-python3 pkg-config build-essential
RUN mkdir /app
WORKDIR /app

COPY . .

RUN npm install -g pnpm
RUN pnpm install
RUN pnpm run build:server

RUN NODE_OPTIONS="--max-old-space-size=2048" pnpm run ui:build

EXPOSE 8080
EXPOSE 8081

CMD [ "bash", "-c", "PORT=8081 node ./dist-server/server.js & pnpm run preview --host <IP_ADDRESS> --port 8080" ]


Clarify fetch handler in the api-analytics recipe

This PR helps to clarify the fetch handler of the api-analytics recipe (see #184).

Thanks for the enhancements.


Feature request: separate between interrupt handlers callback and interrupt handlers which can have several implementations

The latest Mouse Driver PR showed that the ICallback and the Spice86.Core.Emulator.Callback namespace don't distinguish betwwen:

Interrupt handler callbacks
Interrupt handlers with several implementations

This can cause things to be a bit confusing.

Done by @kevinferrare


Fix 117, 148, 149

117: edit should be editTask
148: standardized spacing
149: unclear instruction on how to mark task as done/ not done

Codecov Report
Base: 56.45% // Head: 56.45% // No change to project coverage :thumbsup:

Coverage data is based on head (c39dd71) compared to base (6f20c8d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #164   +/-   ##
=========================================
  Coverage     56.45%   56.45%
  Complexity      544      544
=========================================
  Files           112      112
  Lines          2285     2285
  Branches        280      280
=========================================
  Hits           1290     1290
  Misses          897      897
  Partials         98       98

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix native component loading

Close  #4066
When just one component is loaded, the command data_vals=list(data_vals) keeps just the keys of the dictionary. We need instead data_vals=[data_vals].

Just to double check @lorenzovecchietti . I am guessing that the example one_native_component.aedt was created from scratch and does not contain any IP.

It's just one lonely heatsink :)

Just to double check @lorenzovecchietti . I am guessing that the example one_native_component.aedt was created from scratch and does not contain any IP.

It's just one lonely heatsink :)

Perfect @lorenzovecchietti


[Jetbrains] Error vectordb::voyage-code-2 index - failed to load native library (JetBrains Plugin)

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: MacOS Ventura
- Continue: 0.0.49
- IDE: PHPStorm

Description
'm encountering an error while updating the vectordb::voyage-code-2 index within a JetBrains plugin. The error message suggests that the native library failed to load.
To reproduce
Run IDE
Log output
2024-06-01T08:26:52] Error updating the vectordb::voyage-code-2 index: Error: vectordb: failed to load native library.
  You may need to run `npm install @lancedb/vectordb-darwin-arm64`.

  If that does not work, please file a bug report at https://github.com/lancedb/lancedb/issues

  Source error: Error: Cannot find module '@lancedb/vectordb-darwin-arm64'
Require stack:
- /snapshot/continue-deploy/binary/out/index.js
1) If you want to compile the package/file into executable, please pay attention to compilation warnings and specify a literal in 'require' call. 2) If you don't want to compile the package/file into executable and want to 'require' it from filesystem (likely plugin), specify an absolute path in 'require' call using process.cwd() or process.execPath.

During my troubleshooting, I discovered that running npm run build on the binary and installing @lancedb/vectordb-xxx leads to an overwrite issue.
For instance, there's a requirement to bundle the following dependencies into the plugin. However, in practice, only the last one is actually bundled, resulting in a missing dependency issue:
  "darwin-arm64": "@lancedb/vectordb-darwin-arm64",
  "darwin-x64": "@lancedb/vectordb-darwin-x64",
  "linux-arm64": "@lancedb/vectordb-linux-arm64-gnu",
  "linux-x64": "@lancedb/vectordb-linux-x64-gnu",
  "win32-x64": "@lancedb/vectordb-win32-x64-msvc",
  "win32-arm64": "@lancedb/vectordb-win32-x64-msvc",

I resolved this issue by modifying binary/build.js:
.....

async function installNodeModuleInTempDirAndCopyToCurrent(packageName, toCopy) {
  console.log(`Copying ${packageName} to ${toCopy}`);
  // This is a way to install only one package without npm trying to install all the dependencies
  // Create a temporary directory for installing the package
  const adjustedName = toCopy.replace(/^@/, "").replace("/", "-");
  const tempDir = path.join(
    __dirname,
    "tmp",
    `continue-node_modules-${adjustedName}`,
    packageName,
  );

........

By including the packageName in tempDir, I successfully addressed the dependency overwrite issue.
Hope it helps you.


Update select-over-clause-transact-sql.md

The listed restriction is incorrect. CHECKSUM is not an aggregate function at all. If CHECKSUM_AGG was meant, then it was still incorrect, because CHECKSUM_AGG can be used with OVER without errors. Example (AdventureWorks): SELECT p.ProductID,
p.Name,
p.ListPrice,
p.ProductLine,
CHECKSUM_AGG (p.DaysToManufacture) OVER (PARTITION BY p.ProductLine
ORDER BY p.ListPrice
ROWS BETWEEN 4 PRECEDING AND 2 FOLLOWING) AS MovingAverage
FROM   Production.Product AS p;
This only fails when you change it to CHECKSUM_AGG(DISTINCT p.DaysToManufacture). But the error you get in that case is the same that you also get for COUNT(DISTINCT p.DaysToManufacture) or even MAX(DISTINCT p.DaysToManufacture). So it is a restriction on DISTINCT, not on CHECKSUM_AGG (or on CHECKSUM)

@VanMSFT
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks, @HugoKornelis! Looks good to me.
#sign-off


Added Alt + P shortcut to toggle preview for message editing solved #30851

This PR is same as https://github.com/zulip/zulip/pull/30860 , but with clean commit history
Fixes: #30851

Screenshots and screen captures:
Screencast from 2024-07-13 04-01-11.webm

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.
Individual commits are ready for review (see commit discipline).

[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

This still is very far from matching the style guidelines I shared. I'm closing this PR as not being on track towards being mergeable. Thanks for giving it a try, @shubhiscoding !

@alya
Hii! can you please tell me what could have been a good commit message or what could have been done better?

Contributing successfully to this project requires being able to follow documentation.


Use github url in Readme when referencing folders

These snippets from the Readme will not work outside of Github:
"the cities example"
"unit tests"
"examples directory"
So these should use absolute urls pointing to Github instead of relative ones.

I just made these changes in PR #41. Hope this helps.


Change quorum from 3/4ths to 2/3rds

Fixes #1122

Codecov Report

Merging #1123 (6f45385) into master (047c891) will decrease coverage by 10.24%.
The diff coverage is 50.99%.

@@             Coverage Diff             @@
##           master    #1123       +/-   ##
===========================================
- Coverage   59.57%   49.33%   -10.25%
===========================================
  Files         108      147       +39
  Lines        5803     8765     +2962
===========================================
+ Hits         3457     4324      +867
- Misses       1823     3821     +1998
- Partials      523      620       +97

Impacted Files
Coverage Δ

pkg/config/consts.go
0.00% <0.00%> (ø)

pkg/config/genesis/config.go
0.00% <0.00%> (ø)

pkg/core/chain/legacy.go
0.00% <0.00%> (ø)

...kg/core/consensus/blockgenerator/candidate/mock.go
0.00% <0.00%> (ø)

pkg/core/consensus/comms.go
0.00% <0.00%> (ø)

pkg/core/consensus/fixtures.go
0.00% <0.00%> (ø)

pkg/core/chain/mock.go
9.09% <9.09%> (ø)

pkg/core/chain/loader.go
17.59% <18.42%> (-37.10%)
:arrow_down:

pkg/core/chain/chain.go
48.93% <49.30%> (-6.55%)
:arrow_down:

pkg/core/consensus/agreement/handler.go
54.11% <51.61%> (-11.27%)
:arrow_down:

... and 201 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 8104794...6f45385. Read the comment docs.


8241 Update email address in Terms of Service

This PR ...
Updates the email address in Terms of Service
Test Steps:

Go to RS
Click on Terms of Service in the footer
Verify the email address is<EMAIL_ADDRESS>
Changes

changed from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>
Checklist
Testing

[x] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[x] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

As as aside, I think minor copy changes like this (and minor style/markup changes) only really need one approval.  Let's just use our best judgment going forward, and it doesn't hurt to get more eyes on changes regardless!


Fix STRERROR_R_CHAR_P cxx check (remove unused variable warning->error)

Client: cpp

If '-Werror=unused-variable' set for compiler, check for STRERROR_R_CHAR_P always fail because of 'a' is unused in test code fragment.

[ ] Did you create an Apache Jira ticket?  (not required for trivial changes)
[ ] If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
[x] Did you squash your changes to a single commit?  (not required, but preferred)
[x] Did you do your best to avoid breaking changes?  If one was needed, did you label the Jira ticket with "Breaking-Change"?
[ ] If your change does not involve any code, add  [skip ci] at the end of your pull request to free up build resources.

how to restart appveyor for this task?
Failures

winflexbison3 (exited 404) - Error while running 'C:\ProgramData\chocolatey\lib\winflexbison3\tools\chocolateyInstall.ps1'.
See log for details.
Command exited with code 404
seem like network error

how to restart appveyor for this task?
Rebase and force-push


Add documentation, homepage or repository to manifest

cargo publish --dry-run:
warning: manifest has no documentation, homepage or repository.
See https://doc.rust-lang.org/cargo/reference/manifest.html#package-metadata for more info.

Already done


fix: typescript v5 deprecations

Hello,
I tried to upgrade one of my Vue3 projects using @vue/tsconfig to typescript v5. Unfortunately they introduced deprecations regarding --importsNotUsedAsValues and --preserveValueImports in favour of the newly introduced --verbatimModuleSyntax flag.
Of course there is a temporary workaround to just ignore those deprecations:
{
  "compilerOptions": {
    "ignoreDeprecations": "5.0"
  }
}

This PR probably will result in a breaking change, since the new flag is only available in typescript v5.
Fixes #6

When merging these changes then #3 is obsolete and can be closed

Hi! Will the next package version with this changes has major version update?
looks like developers that use 4+ version of ts will not be able to use this config?

Hi @chemparparokke,
as already mentioned this changes will result in a breaking change, and therefore a major version bump as well ;)
Developers using 4+ can stick to the current version and upgrade once they are ready for Typescript v5.


Can't build a project derived from this on DockerHub

First of all, thanks a lot for your work.
I'm sure there is something I don't get and that the source of my problems is not on your side, but... maybe you can help.
I have a project which aims to build a minimal image for ARMV7 (OrangePi Zero/Raspberry PI3B+) on DockerHub.
It builds when based on resin/qemux86-alpine:latest (but then can't execute on the Zero standard_init_linux.go:190: exec user process caused "exec format error").
It does not build when based on schmich/armv7hf-alpine-qemu:3.5:
Step 2/6 : RUN [ “cross-build-start” ] ---> Running in 895fcf627619 standard_init_linux.go:187: exec user process caused "exec format error"  Removing intermediate container 895fcf627619

I forked your project, and it does build.
Do you have any idea on what I am doing wrong, or if something has changed on DockerHub side, or yours?

Forget it, I had used a bad set of quotes.


only round width/height when resizing

Problem
When resizing, the top or left prop might have changed as a result of the edit
Fix
Remove the rounding call that rounded all of top/left/width/height of the new frame, and only round width and height

Does this work as well when resizing the top left corner?

Does this work as well when resizing the top left corner?

extending on this, don't forget the case when an element has width, height, right, bottom props, and you are resizing the bottom right corner.


Removing databroker

As migration is finished no need to keep it here.
Version 0.4.3 tagged and docker containers created, verified that they give warnings

Anything more you want that we shall do before removing it @SebastianSchildt .
I suggest that after you approve it that we ping (or add as reviewer) John, Mike, SvenErik, Lukas, so they are aware that it will be deleted, and can complain before we do it

We have used that policy in the past, to remove the code in the old location. Reduces the risk for PRs and Issues in the old repo.

couldn't we keep a branch open like deprecated_databrokeror something like this? Then documenting clearly that it is there and you should not use it. But at least we then keep the state for I do not know end of the year?

@lukasmittag - I added a branch https://github.com/eclipse/kuksa.val/tree/deprecated_databroker from previous commit, and references that branch from the README now. So if someone by some reason do not want to use the partially refactored databroker in kuksa-databroker and they want to check out code by branch rather than tag they can use the deprecated_databroker branch.


Centralize mapping of operators parsed from symbols

TNT allows some built-in operators to be represented with symbols and then translates them at parsing (i.e. + to iadd, { key: value } to rec(key, value)). These operator names are mostly internal, and they are referenced to in many different parts of the code base (parsing, default definitions for name resolution, effect signatures, type signatures, simulator compiling) which is a problem since we can change the name in some of these places but not others. Also, I keep switching them up (i.e. rec vs record) so that's annoying.
We should have a single module defining all of those names so we can:

Have a single place to update when we want to change them
Have static guarantees that we are not referencing an unexisting operator

This should also be true for built-in operators in general, not just the ones with symbol representation

I think the impact of this is not so low anymore. We've hit problems related to this at least thrice this week:

#815 (missnaming of operator in docs)
https://github.com/informalsystems/apalache/issues/2530 (no central place for ops, so i overlooked the record ops, which aren't in the builtin sigs.)
#814 (REPL doesn't handle operator)

@bugarela I could take this on, if you're not eager for it or don't have the bandwidth :)

Sounds good! I don't think I'll have bandwidth for it this quarter.


Di on application

Breaking change

Proposed change

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the [development checklist][dev-checklist]
[ ] The code compiles without warnings (code quality chek)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

Codecov Report

Merging #421 (656dc6a) into dev (d3eaf1c) will increase coverage by 0.00%.
The diff coverage is 41.89%.

@@           Coverage Diff           @@
##              dev     #421   +/-   ##
=======================================
  Coverage   54.45%   54.45%
=======================================
  Files          82       83    +1
  Lines        4598     4609   +11
  Branches      712      717    +5
=======================================
+ Hits         2504     2510    +6
- Misses       1867     1869    +2
- Partials      227      230    +3

Flag
Coverage Δ

unittests
54.45% <41.89%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/App/NetDaemon.App/Common/INetDaemonApp.cs
0.00% <0.00%> (ø)

src/App/NetDaemon.App/Common/NetDaemonAppBase.cs
70.86% <ø> (-0.79%)
:arrow_down:

...c/App/NetDaemon.App/Common/Reactive/Observables.cs
100.00% <ø> (ø)

...n/NetDaemon.Daemon/Daemon/Config/YamlExtensions.cs
78.00% <ø> (ø)

...mon/NetDaemon.Daemon/Daemon/DaemonAppExtensions.cs
61.40% <ø> (ø)

...er/Infrastructure/Extensions/AssemblyExtensions.cs
75.00% <0.00%> (ø)

...nner/DaemonRunner/Service/App/DaemonAppCompiler.cs
0.00% <0.00%> (ø)

...DaemonRunner/Service/App/LocalDaemonAppCompiler.cs
0.00% <0.00%> (ø)

...rc/Daemon/NetDaemon.Daemon/Daemon/NetDaemonHost.cs
52.56% <30.18%> (-1.20%)
:arrow_down:

src/Fakes/NetDaemon.Fakes/DaemonHostTestBase.cs
73.80% <80.00%> (-0.60%)
:arrow_down:

... and 10 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 d3eaf1c...656dc6a. Read the comment docs.


Fixing link to training survey

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/6142f49e3c79a20191dd1286d04a836757e5408e/


Using literally suppresses info in compilation failure traceback

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

Hi,
This is regarding numba.literally which is working normally itself, but has a shortcoming of masking the real compilation error when it is applied before compilation reaches some non-supported code, i.e. the compilation failure traceback only references to 'Repeated literal typing request', but not to the root cause of compilation failure, which complicates the debugging. Here's the example that demonstrates the problem:
import numba
from numba import njit, literally
from numba.core import types
from numba.extending import overload
from numba.core.errors import TypingError

def foo(x):
    pass

def bar(y):
    pass

@overload(bar)
def bar_ovld(y):

    # consider this is the only impl that is currently provided, and reject others with TypingError
    if not isinstance(y, types.NoneType):
        raise TypingError("bar only supported arg is None")

    return lambda y: 43

@overload(foo)
def foo_ovld(x):
    if not isinstance(x, types.Literal):
        return lambda x: literally(x)

    x_literal_val = x.literal_value
    def foo_impl(x):
        if x_literal_val == 1:
            return 42
        else:
            return bar(x)

    return foo_impl

@njit
def test_impl(x):
    return foo(x)

val = 'sdf'
print(test_impl(val))

This prints the following huge traceback, that has no references to bar's TypingError message (in case of some LoweringError from the bar_impl it would be suppressed too, so it becomes difficult to understand what went wrong):

(NUMBA_MASTER_4) C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba>python test_literally_err.py
Traceback (most recent call last):
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 979, in compile
cres = self._compiler.compile(args, return_type)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 141, in compile
status, retval = self._compile_cached(args, return_type)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 155, in _compile_cached
retval = self._compile_core(args, return_type)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 173, in _compile_core
pipeline_class=self.pipeline_class)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 686, in compile_extra
return pipeline.compile_extra(func)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 428, in compile_extra
return self._compile_bytecode()
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 492, in _compile_bytecode
return self._compile_core()
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 471, in _compile_core
raise e
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 462, in _compile_core
pm.run(self.state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 343, in run
raise patched_exception
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 334, in run
self._runPass(idx, pass_inst, state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
return func(*args, **kwargs)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 289, in _runPass
mutated |= check(pss.run_pass, internal_state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 262, in check
mangled = func(compiler_state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\untyped_passes.py", line 430, in run_pass
find_literally_calls(state.func_ir, state.args)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\analysis.py", line 620, in find_literally_calls
raise errors.ForceLiteralArg(marked_args, loc=loc)
numba.core.errors.ForceLiteralArg: Failed in nopython mode pipeline (step: find literally calls)
Pseudo-exception to force literal arguments in the dispatcher
File "test_literally_err.py", line 28:
def foo_ovld(x):

if not isinstance(x, types.Literal):
return lambda x: literally(x)
^
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 589, in resolve
sig = typeinfer.resolve_call(fnty, pos_args, kw_args)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 1541, in resolve_call
return self.context.resolve_function_type(fnty, pos_args, kw_args)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typing\context.py", line 195, in resolve_function_type
res = self._resolve_user_function_type(func, args, kws)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typing\context.py", line 247, in _resolve_user_function_type
return func.get_call_type(self, args, kws)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\types\functions.py", line 348, in get_call_type
failures.raise_error()
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\types\functions.py", line 226, in raise_error
raise fail.error
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\types\functions.py", line 329, in get_call_type
sig = temp.apply(nolitargs, nolitkws)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typing\templates.py", line 351, in apply
sig = generic(args, kws)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typing\templates.py", line 605, in generic
disp, new_args = self._get_impl(args, kws)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typing\templates.py", line 704, in _get_impl
impl, args = self._build_impl(cache_key, args, kws)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typing\templates.py", line 805, in _build_impl
disp_type.get_call_type(self.context, args, kws)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\types\functions.py", line 555, in get_call_type
self.dispatcher.get_call_template(args, kws)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 377, in get_call_template
self.compile(tuple(args))
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 984, in compile
raise e.bind_fold_arguments(folded)
numba.core.errors.ForceLiteralArg: Pseudo-exception to force literal arguments in the dispatcher
File "test_literally_err.py", line 28:
def foo_ovld(x):

if not isinstance(x, types.Literal):
return lambda x: literally(x)
^
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 979, in compile
cres = self._compiler.compile(args, return_type)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 141, in compile
status, retval = self._compile_cached(args, return_type)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 155, in _compile_cached
retval = self._compile_core(args, return_type)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 173, in _compile_core
pipeline_class=self.pipeline_class)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 686, in compile_extra
return pipeline.compile_extra(func)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 428, in compile_extra
return self._compile_bytecode()
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 492, in _compile_bytecode
return self._compile_core()
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 471, in _compile_core
raise e
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 462, in _compile_core
pm.run(self.state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 343, in run
raise patched_exception
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 334, in run
self._runPass(idx, pass_inst, state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
return func(*args, **kwargs)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 289, in _runPass
mutated |= check(pss.run_pass, internal_state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 262, in check
mangled = func(compiler_state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typed_passes.py", line 112, in run_pass
raise_errors=self.raise_errors)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typed_passes.py", line 83, in type_inference_stage
errs = infer.propagate(raise_errors=raise_errors)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 1076, in propagate
raise reduce(operator.or, force_lit_args)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 154, in propagate
constraint(typeinfer)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 566, in call
self.resolve(typeinfer, typevars, fnty)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 607, in resolve
raise ForceLiteralArg(requested, loc=self.loc)
numba.core.errors.ForceLiteralArg: Failed in nopython mode pipeline (step: nopython frontend)
Pseudo-exception to force literal arguments in the dispatcher
File "test_literally_err.py", line 43:
def test_impl(x):
return foo(x)
^
During: resolving callee type: Function(<function foo at 0x000001AAD5AACA68>)
During: typing of call at test_literally_err.py (43)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 434, in _compile_for_args
return_val = self.compile(tuple(argtypes))
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 984, in compile
raise e.bind_fold_arguments(folded)
numba.core.errors.ForceLiteralArg: Pseudo-exception to force literal arguments in the dispatcher
File "test_literally_err.py", line 43:
def test_impl(x):
return foo(x)
^
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 979, in compile
cres = self._compiler.compile(args, return_type)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 141, in compile
status, retval = self._compile_cached(args, return_type)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 155, in _compile_cached
retval = self._compile_core(args, return_type)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 173, in _compile_core
pipeline_class=self.pipeline_class)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 686, in compile_extra
return pipeline.compile_extra(func)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 428, in compile_extra
return self._compile_bytecode()
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 492, in _compile_bytecode
return self._compile_core()
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 471, in _compile_core
raise e
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler.py", line 462, in _compile_core
pm.run(self.state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 343, in run
raise patched_exception
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 334, in run
self._runPass(idx, pass_inst, state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
return func(*args, **kwargs)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 289, in _runPass
mutated |= check(pss.run_pass, internal_state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\compiler_machinery.py", line 262, in check
mangled = func(compiler_state)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typed_passes.py", line 112, in run_pass
raise_errors=self.raise_errors)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typed_passes.py", line 83, in type_inference_stage
errs = infer.propagate(raise_errors=raise_errors)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 1076, in propagate
raise reduce(operator.or, force_lit_args)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 154, in propagate
constraint(typeinfer)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 566, in call
self.resolve(typeinfer, typevars, fnty)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\typeinfer.py", line 607, in resolve
raise ForceLiteralArg(requested, loc=self.loc)
numba.core.errors.ForceLiteralArg: Failed in nopython mode pipeline (step: nopython frontend)
Pseudo-exception to force literal arguments in the dispatcher
File "test_literally_err.py", line 43:
def test_impl(x):
return foo(x)
^
During: resolving callee type: Function(<function foo at 0x000001AAD5AACA68>)
During: typing of call at test_literally_err.py (43)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 434, in _compile_for_args
return_val = self.compile(tuple(argtypes))
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 984, in compile
raise e.bind_fold_arguments(folded)
numba.core.errors.ForceLiteralArg: Pseudo-exception to force literal arguments in the dispatcher
File "test_literally_err.py", line 43:
def test_impl(x):
return foo(x)
^
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "test_literally_err.py", line 47, in
print(test_impl(val))
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 457, in _compile_for_args
return_val = self._compile_for_args(*args)
File "C:\Users\akozlov\AppData\Local\Continuum\anaconda3\numba_master\numba\numba\core\dispatcher.py", line 450, in _compile_for_args
raise errors.CompilerError(m.format(info))
numba.core.errors.CompilerError: Repeated literal typing request.
Arg #0 is Literalstr.
This is likely caused by an error in typing. Please see nested and suppressed exceptions.

Best Regards,
Alexey.

@kozlov-alexey Thanks for the report. If you switch on logging the exception is in there.
$ head -n 10 issue7568.py
import numba
from numba import njit, literally
from numba.core import types
from numba.extending import overload
from numba.core.errors import TypingError

import logging
logging.basicConfig(level=logging.DEBUG)

def foo(x):

running with that also gives a large backtrace but it does contain:
numba.core.errors.TypingError: No implementation of function Function(<function bar at 0x7ff72eafee50>) found for signature:

 >>> bar(Literal[str](sdf))

There are 2 candidate implementations:
    - Of which 2 did not match due to:
    Overload in function 'bar_ovld': File: issue7568.py: Line 16.
      With argument(s): '(unicode_type)':
     Rejected as the implementation raised a specific error:
       TypingError: bar only supported arg is None


Probable typo in default-containers.json

The total-liquid-volume for location A1 in a container of type e-gelgol is defined as 20; the other locations have the same values of depth and diameter, but a total-liquid-volume 10 times smaller (2, rather than 20).

This has been fixed in v3 with #518 but we need to figure out if/how we are going to backport the fix to v2


by adding some padding at left its look more proper than its look now.

[##]() Problem

photos are not aligned at proper form.
Description

so we can solve this issue by adding some padding on both side so it can look good.
Alternatives

Additional context

Implementation

[ ] I would be interested in implementing this feature.

if we add some padding both side its look more attractive

@mohitparmar1 Thank you for pointing this out!  ❤
You're right, and it's a good suggestion, but this design is in the process of being replaced so it's not something we'll be addressing directly.


README features are out of date

Aliases are done
Banned is a thing, too
privacy mode management maybe?

how do youse @cryptix @staltz feel about adding some kinda image to the readme? and show off how pretty the dashboard is 💖
we can hack the image embed by pasting an image into an issue (or a github wiki page) and then using the generated link on the readme (and get away with not having to add an image to the repo proper :)

i wouldn't mind having docs/screenshots/dashboard{1..n}.png either.


[bug][.net analyzer] ignore property bag class with suffix Options

Problem
In AZC0030, we will report a warning if a model class name ends with Options. However, our property bag class will have an Options suffix. That causes false alerts, like https://github.com/Azure/azure-sdk-for-net/pull/39653/checks?check_run_id=18337868902

sdk/integrationspaces/Azure.ResourceManager.IntegrationSpaces/src/Generated/Models/BusinessProcessCollectionGetAllOptions.cs(14,26): Error AZC0030: Model name 'BusinessProcessCollectionGetAllOptions' ends with 'Options'. Suggest to rename it to 'BusinessProcessCollectionGetAllConfig' or any other appropriate name.

BusinessProcessCollectionGetAllOptions is a property bag. We should ignore such cases in AZC0030

Hi, I am facing the same issue with my model class name ending in "Parameter" ending in the error AZC0030. What can I do?

Hi, I am facing the same issue with my model class name ending in "Parameter" ending in the error AZC0030. What can I do?

@shrutijha041100 Ordinary models should avoid Parameter suffix. You can rename the model, see here for details: https://github.com/Azure/autorest.csharp#rename-a-model-class


Implement camera-orbit attribute

Configurable camera-orbit attribute
This change proposes the addition of a camera-orbit attribute to enable users to control the starting and subsequent positions of the camera long a spherical orbit centered on the model.

Highlights

camera-orbit attribute allows CSS-like configuration of starting and subsequent camera positions

Accepts values in the form of $theta $phi $radius
Example accepted values include: 0deg 75deg 1m, 1 2 3, 1rad 2deg 100cm
Default units are radians for angles, meters for radius
Special radius value auto: refers to the "ideal" camera distance as determined by scene framing
Camera interpolates from its current position to subsequent values of camera-orbit (see also #454)

getCameraOrbit method for real-time querying of current orbital position

Realtime position may not align to attribute on account of interpolation or user interaction

interaction-prompt-threshold attribute controls the time that must have passed before an interaction prompt is presented to the user
🚨 BREAKING CHANGE: The controls attribute has been renamed to camera-controls

Rationale: disambiguates from controls attribute in the <video> element

New modules for parsing and converting complex attribute values have been introduced
Lots of new tests for all of above have been added
Controls feature has been converted to TypeScript
A new documentation section for "Staging & Camera Control" has been added
A new model has been contributed to help document the align-model attribute introduced in #441

Name rationale
I waffled a bit when deciding what name to propose for the attribute. Initially, I thought that camera-position was a good name. But, position is already used by Three.js (and other libraries) to refer to the cartesian coordinates of things in 3D space. This attribute, by contrast, represents the spherical coordinates of the camera relative to a separately defined target origin.
As far as API shape is concerned, the spherical position can be queried by the user, and is represented by a plain-object version of Three.js's Spherical data structure e.g., { theta, phi, radius }. However, it might make sense to name this object's properties more explicitly, e.g., { azimuth, inclination, radius }. Feedback here is requested.
Future work

Camera panning support #447
Establish concrete definition of 1m in world space #450
Attribute to configure the camera target #453
Opt-out of interpolation when changing camera orbit #454

Fixes #98
Additional fixes have been rolled in from #457 :
Fixes #435
Fixes #437
Fixes #446
Fixes #456

FYI @svinkle this change will pull in the fix for screen reader SVG discoverability.


Import proxy with experimental wasm/mixerv2 support.

Update istio/proxy which contains @jplevyak's experimental support for running MixerV2 in WASM.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

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

Test name
Commit
Details
Rerun command

racetest_istio_release-1.3
8f06e061cd1f28a2aa982739226d14728480876f
link
/test racetest

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

/test racetest

@duderino: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.3
8f06e061cd1f28a2aa982739226d14728480876f
link
/test integ-mixer-k8s-tests

unit-tests_istio_release-1.3
8f06e061cd1f28a2aa982739226d14728480876f
link
/test unit-tests

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


feat(glue): enable profiling

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues (if applicable)
[x] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[x] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@BoyuanZhangDE thanks for the contribution. I left some comments.

@BoyuanZhangDE looks good now, but it seems there are some linter errors.
Please, can you run black formatting on the code?


feat(pose_initializer): add a method type to the /localization/initialize service.

Description
I have added the capability to directly initialize by the input pose of the /localization/initialize service.
To facilitate this, a new service message is being defined https://github.com/tier4/tier4_autoware_msgs/pull/121, and I have changed service message type of /localization/initialize
autoware_adapi_v1_msgs::srv::InitializeLocalization -> tier4_localization_msgs::srv::InitializeLocalization.
Along with that I have modified following packages

pose_initilizer
component_interface_specs
default_ad_api

Related links

Tests performed

test case1

ros2 service call /localization/initialize tier4_localization_msgs/srv/InitializeLocalization

The initial position is automatically estimated using the GNSS pose.

test case2

ros2 service call /localization/initialize tier4_localization_msgs/srv/InitializeLocalization "
method: 0
"

The initial position is automatically estimated using the GNSS pose.

test case3

ros2 service call /localization/initialize tier4_localization_msgs/srv/InitializeLocalization "
pose_with_covariance:
  - header:
      frame_id: map
    pose:
      pose:
        position:
          x: 89571.1640625
          y: 42301.1875
          z: -3.1565165519714355
        orientation:
          x: 0.0
          y: 0.0
          z: 0.28072773940524687
          w: 0.9597874433062874
      covariance: [0.25, 0, 0, 0, 0, 0, 0, 0.25, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.06853891909122467]
method: 0
"

The initial position is automatically estimated using the input pose.

test case4

ros2 service call /localization/initialize tier4_localization_msgs/srv/InitializeLocalization "
pose_with_covariance:
  - header:
      frame_id: map
    pose:
      pose:
        position:
          x: 89571.1640625
          y: 42301.1875
          z: -3.1565165519714355
        orientation:
          x: 0.0
          y: 0.0
          z: 0.28072773940524687
          w: 0.9597874433062874
      covariance: [0.25, 0, 0, 0, 0, 0, 0, 0.25, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0.06853891909122467]
method: 1
"

The initial position is set directly by the input pose.

Notes for reviewers
This PR should merge after https://github.com/tier4/tier4_autoware_msgs/pull/121.
Otherwise, the build will fail, and the GitHub CI will not pass.

Interface changes

ROS Topic Changes

ROS Parameter Changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

Thank you.
In the explanation, it looked like it would be fine to just merge the PRs in autoware.universe and tier4_autoware_msgs, but I got a build error.
Is it correct that the PR that Takagi-san linked to also needs to be merged at the same time?

@SakodaShintaro

Is it correct that https://github.com/tier4/tier4_ad_api_adaptor/pull/112 also needs to be merged at the same time?
Yes, I'm sorry.

@KYabuuchi I added some descriptions to initialize pose the via CLI


x/tools/gopls: does not conform to Go documentation on non-scalar GOPATH

What version of Go are you using (go version)?

$ go version
go version go1.13.4 darwin/amd64

Does this issue reproduce with the latest release?
I am currently one patch level behind. But based on the source code on current master shown below, I believe it will reproduce with the latest release.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env | sed s/$USER/user/g
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/user/Library/Caches/go-build"
GOENV="/Users/user/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/user/go:/Users/user/go-work"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/local/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/local/lib/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="/usr/bin/clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/q_/jc67mj41687gcm21gq1z853m0000gn/T/go-build770602489=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

VSCode installed gopls for me, and it shows an error message when I get to a go file that is (i) in my GOPATH but (ii) imports an unsatisfied dependency. For example, try:
package main

import "missingpackagehere"

The error message is:

You are neither in a module nor in your GOPATH. Please see https://github.com/golang/go/wiki/Modules for information on how to set up your Go project.

I believe this is because my GOPATH is a colon-separated string:

GOPATH="/Users/user/go:/Users/user/go-work"

This type of non-scalar GOPATHs is supported in Go 1 according to the current Go documentation https://golang.org/cmd/go/#hdr-GOPATH_environment_variable:

The GOPATH environment variable lists places to look for Go code. On Unix, the value is a colon-separated string. On Windows, the value is a semicolon-separated string. On Plan 9, the value is a list.

However, this line of code at current master does not appear to support such non-scalar GOPATHs. https://github.com/golang/tools/blob/0f69de236bb709847e215a792a40aaee1cba60d9/internal/lsp/source/errors.go#L50:
inGopath := strings.HasPrefix(uri.Filename(), filepath.Join(gopath, "src"))

What did you expect to see?
I expect gopls to support GOPATHs allowed by the Go documentation and therefore not return the error message shown above.
What did you see instead?
I saw the error message shown above.

The filepath.SplitList function should be useful for resolving this issue.


x/vuln: incorrect fix version reporting GO-2023-1987

What version of Go are you using (go version)?

$ go version
go version go1.20.6 darwin/amd64

Does this issue reproduce at the latest version of golang.org/x/vuln?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOOS="darwin"
GOARCH="amd64"

What did you do?

when checking a package using crypto/tls (in my case go-redis but anything will do), using go1.20.6, govulncheck reports vuln GO-2023-1987. which is valid. except that it reports it fixed in go1.21rc4.
What did you expect to see?
the vuln is fixed in an earlier version, go1.20.7. i expected govulncheck to report that version. i often see govulncheck report the earliest version where a vuln is fixed, so i expected that here as well.
What did you see instead?

Vulnerability #1: GO-2023-1987
    Large RSA keys can cause high CPU usage in crypto/tls
  More info: https://pkg.go.dev/vuln/GO-2023-1987
  Standard library
    Found in<EMAIL_ADDRESS>    Fixed in<EMAIL_ADDRESS>

cc @golang/vulndb

@tatianab

Also for the recent GO-2023-2041:
Vulnerability #2: GO-2023-2041
    Improper handling of HTML-like comments in script contexts in html/template
  More info: https://pkg.go.dev/vuln/GO-2023-2041
  Standard library
    Found in<EMAIL_ADDRESS>    Fixed in<EMAIL_ADDRESS>
This is actually fixed earlier, in go1.20.8.

govulncheck's current approach is to always report the latest fix available (after which the issue is not re-introduced).
I think that often the earliest and the latest fix coincide, so that is why you sometimes see what you described.
In your case, is there a particular reason why you would prefer the earliest instead of the latest fix?

govulncheck's current approach is to always report the latest fix available.

huh. then the language should perhaps be changed. "found in / fixed in" implies first known occurrence and first known fix. At least to this reader.
In this case, it's because it is implying a need to update the minor version (1.21.x) instead of just a patch version (1.20.x). In go, even "minor" version updates can introduce breaking behavior that needs to be fully tested/qualified, eg in go1.21 the initialization order is better defined and may be different. (compatbility promise aside).
Besides resistance to upgrading minor version "just" to address a vuln, the latest version tends to have more churn.
The "fixed in" version for the original report, GO-2023-1987, is an rc version! govunlcheck is suggesting me to update my codebase to an rc version? I think that would be ok if that were the only fixed version, but this was fixed earlier, in a go1.20 release version.


Target .NET Standard 2.0

:watch: blocked on httpsys conversion to ns2.0 cc @Tratcher
Also updated samples that used obsolete logging API.

Unblocked


Fix extra behaviour for multiple inheritance/mix-ins

Change Summary
New Config.extra supports both Enum and str values. And set_extra method always tries to convert the value to make sure it is an Enum.
But this leads to extra being re-constructed/re-assigned each time BaseModel is inherited from (even it it was not set in child classes Config) thus breaking extra inheritance when using mix-ins/multiple inheritance.
So Config.extra conversion/re-assignment was limited only to cases when extra is not an instance of Extra enum.
Rationale:

If extra is an Extra enum value, then it was either:

inherited from one of the base Configs (BaseConfig has extra = Extra.ignore), and does not need to be re-assigned to the topmost MRO class.
was set directly in the topmost MRO class, and does not need to be re-assigned either.

if extra in not an Extra enum value, than it was certainly set in the topmost MRO class (all base classes have already done the conversion), and is safe to be converted and re-assigned without messing MRO.

Related issue number
https://github.com/samuelcolvin/pydantic/issues/392
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] HISTORY.rst has been updated

if this is the first change since a release, please add a new section
include the issue number or this pull request number #<number>
include your github username @<whomever>

@samuelcolvin  Do we need a new version in HISTORY.rst?

looks good to me. Good catch, thank you very much.
I try and merge PRs in the order they were created to make conflicts as fair as possible, so I'll try and get other PRs merged before this.

I'll try and get other PRs merged before this.

:+1:


request processing time - too high

First of all this issue is for now.sh cloud itself, not for cli, but I didn't found any other repository for such an issue, that's why I've created it here, If its not in correct place sorry and please give me some direction where should I create it.
I was comparing request processing time in now.sh vs heroku. I've created simple graphql server with tracing and here are the results:
Now.sh

Heroku

This is the time after request sent successfully and server is processing, based on that region is not necessary here but for information both (now.sh & heroku) servers are in US.
Also I'm using free tier in now.sh and can it be the reason ?
P.S. I do some researches right now, for future infrastructure and I really liked now.sh with its pricing & cli, but that factor is really important and will be happy if you will give me more information about that.
P.P.S. the results are not for first run, first run needs more time, this is results after multiple run same query, in both cases
query that I ran in graphql is simple:
type Query {
   hello: String
}

const resolvers = {
    Query: {
        hello: () => null
    },
}

Hi - are you using HTTPS when connecting to Heroku?

Yes it's https in both cases, I've created repo: https://github.com/playerx/paas-performance-test
So my questions are:

If I'll have another kind of subscription (not free one) will I have the same picture?
Am I doing something wrong, should I meter the performance with another way?

one more screen, processing time with browser waiting time:

Could you show ping times to each server?

If I'll have another kind of subscription (not free one) will I have the same picture?

Potentially; the open source plan has lower resources allotted to deployments and lower bandwidth guarantees.

Am I doing something wrong, should I meter the performance with another way?

The network panel in your last screenshot is a bit more telling than lumping all of the time under request. Connection time is a large portion of requests and SSL handshaking can incur some cost, too.
The waiting is a little troublesome - upon trying the Now version I see the reporting isn't very accurate:

309ms waiting time is indeed a bit high but not at all close to the 1847ms the tool is reporting.
As well, I'm seeing similar times to Heroku:

As with the Now example, it appears the tool's timing mechanism is off here, too.

PING https://paas-performance-test-dfqsnqkmox.now.sh (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=43 time=78.624 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=43 time=80.317 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=43 time=106.854 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=43 time=78.409 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=43 time=78.278 ms

I'm not in US, but ping is good.
Its strange that tracing doesn't work for you, can you try chrome ? maybe apollo tracing has some issue. Also can you try to run same query multiple times.
Can you show the picture for Now.sh? in both pictures there are heroku in url.

Apologies, not sure how that happened. Updated the screenshot in https://github.com/zeit/now-cli/issues/1039#issuecomment-351486202.

Here it is on Chrome:

Heroku seems a bit volatile:

Whereas now is a little more consistent:

Our TTFB times are going to decrease in the coming months as we make improvements to our internal networking design.

Now I really don't understand, same resource, same server and 2 different clients:

your request was processed in 183ms
my request was processed in 773ms

Do you have any idea?
I'm located in another part of the world, in Georgia, can it matter?
P.S. thanks for helping me

300-400 ms is okey for me, but for me its 700-1000 every time I try at Now.sh

Yes, it definitely can. Your route to Heroku's datacenters could be drastically different than the route to Now's datacenters, especially since you're quite far away. Route topology makes a huge difference in response times.
Just out of curiosity, what is the difference between https://sfo.now.sh and https://bru.now.sh? Our Belgium datacenter is being rolled out and will become generally available in the coming months, which I would imagine will be a much better connection.

It's also worth mentioning I'm connecting from San Francisco, California.

https://bru.now.sh - 3225 km   80-100 ms
So this request processing time by server + routing time. I thought it was just request processing, thanks.
One more question, is there any way to select server(s) where I want to host, I've found it in now.json configuration but didn't found available values, server list.

https://sfo.now.sh - 11105 km  300-340 ms

Yeah those ping times sound about right.
Right now, no - we only have one datacenter location here in San Francisco. In the coming months we'll be rolling out functionality to scale up deployments in our Belgium datacenter, which is probably what you're after. :)

Great thank you so much !

No problem :) 👋

@dohomi no, I'm getting 50-100 ms on bru1 now. The exact same performance than in Google Cloud.


Creating joinRoom and handling the Joinroom functionalities

Creating and Handlingchanges of room names and handling errors of it .
Placeholder logic for joining or creating a room.
It Clear any existing error messages.
The handleRoomNameChange function updates the roomName state based on user input.
The component renders:
A heading and input field for entering a room name.
Buttons for joining or creating a room.
An error message if necessary.

Please attach some screenshot @tusharyadav11

Please raise this pull request to branch feature/InitialUIDesign for this Sprint 1

@thecuriousteam

Please check the the figma design @tusharyadav11

any updates @tusharyadav11

yes

any updates @tusharyadav11

any updates @tusharyadav11

yes providing you soon

@thecuriousteam  earlier I pushed into main branch then you asked me to in different branch irrespective of main branch

Please any updates @tusharyadav11

Providing you soon
On Thu, 16 May, 2024, 8:12 pm Curious Team, @.***>
wrote:

Please any updates @tusharyadav11 https://github.com/tusharyadav11
—
Reply to this email directly, view it on GitHub
https://github.com/Curious-Ecosystem/Curious-Connect/pull/26#issuecomment-2115440595,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCVZ36FK3QAWQ6KTPV6P53LZCTAUDAVCNFSM6AAAAABHRWNVU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJVGQ2DANJZGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

any updates?


RLS

RLS does work at least for report subscriptions.  The data is filtered accordingly.

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

ID: 830da8e8-8526-0e6a-d83f-0c804226e006
Version Independent ID: 3e7b9d31-133d-1b2f-fded-d9218284155b
Content: Subscribe yourself and others to reports and dashboards in the Power BI service - Power BI
Content Source: powerbi-docs/service-report-subscribe.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @asocorro -- me again! OK, I checked with the product team. Here's their response:
IF the report subscription is only for yourself, it does work – you simply can’t subscribe others to a report with RLS in Power BI right now.
Paginated Reports allows you to subscribe other users to reports with RLS turned on, however, the attachment data is based on the initial subscriber only.
Hope that clears things up. I'll look at the article and see if I need to clarify.
Thanks for asking!

Hi!  Thanks for the quick response, as usual.
IF the report subscription is only for yourself, it does work – you simply can’t subscribe others to a report with RLS in Power BI right now.
Yes, my comment was that the article says it doesn’t.
By the way, it would be nice if subscriptions remembered the filter state of the report (if one so chooses).
Have a nice weekend,
Adolfo
From: Maggie Sparkman<EMAIL_ADDRESS>Sent: Friday, May 17, 2019 3:05 PM
To: MicrosoftDocs/powerbi-docs<EMAIL_ADDRESS>Cc: Adolfo J. Socorro, Ph.D<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerbi-docs] RLS (#1046)
Hi, @asocorrohttps://github.com/asocorro -- me again! OK, I checked with the product team. Here's their response:
IF the report subscription is only for yourself, it does work – you simply can’t subscribe others to a report with RLS in Power BI right now.
Paginated Reports allows you to subscribe other users to reports with RLS turned on, however, the attachment data is based on the initial subscriber only.
Hope that clears things up. I'll look at the article and see if I need to clarify.
Thanks for asking!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/powerbi-docs/issues/1046?email_source=notifications&email_token=ADAAVNGDFKY57X7PB4PNAY3PV36XRA5CNFSM4HNRDZ22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVVTKBQ#issuecomment-493565190, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADAAVNDLJKRUJIIR5HNYZATPV36XRANCNFSM4HNRDZ2Q.

@asocorro -- got it, thanks. Yes, I'll update the article.

OK, article updated. Thanks, @asocorro !


Example with bare tls magic

Sample using AkkaTlsMagicSSLEngineProvider without any refactor.
This is to compare the original ConfigSSLEngineProdicer wth AkkaTlsMagicSSLEngineProvider. Here's a few details:

differences in settings (enable/disable hostname verification, enable/disable mTLS)
duplicate code

@raboof I've simplified the code:

removed the new ConfigSSLEngineProvider
undeprecate the old ConfigSSLEngineProvider
remove the SSLFactory class introduced in https://github.com/akka/akka/pull/29061
removed some no-longer-necessary abstractions (e.g. ManagersProviders)

Then, I've extracted a few bits and pieces from AkkaTLSMagicSSLEngineProvider to separate classes.
Finally, I've introduced SSLEngineConfig (related to the discussion in https://github.com/raboof/akka/pull/2#discussion_r431873610) and used it in both AkkaTLSMagicSSLEngineProvider and the old ConfigSSLEngineProvider.
The most important detail on this last commit is that now there are only two EngineProvider implementations and only one of them support key rotation.