Fixed parsing closing tags of unsized containers

The closing tag was peeked in the loop, but wasn't popped from the stream once found. This caused the rest of the message to be corrupted.
Note that the code has poor handling of stream errors. In my case this bug caused an infinite recursion which resulted in a stack overflow crash. This should be considered a security vulnerability: an attacker could insert a stray } in a UBJSON document and cause a denial-of-service or worse. This problem is not fixed by this PR.

Note that the code has poor handling of stream errors. In my case this bug caused an infinite recursion which resulted in a stack overflow crash. This should be considered a security vulnerability: an attacker could insert a stray } in a UBJSON document and cause a denial-of-service or worse. This problem is not fixed by this PR.

If you have suggestions or patches I would appreciate it.  When I wrote this initially I was quickly trying to get a compliant,fast, and simple implementation.  Security wasn't one of my concerns (although you're right that it should be).  If you can help now I can work on it.

Actually the reason I was looking into ubj was because I'm putting together a benchmarking suite to comparing the performance of libraries for various schemaless serialization formats (JSON, MessagePack, BSON, UBJSON, etc.) I ran into these bugs setting up ubj.
There are a few other bugs as well that I didn't try to fix since I can work around them externally. For example ubjr_open_memory() allocates a struct mem_r_fd but never frees it. The call to free it in memclose() is commented out, but even if it wasn't, ubjr_close_context() doesn't actually call the close_cb so it's leaked either way.
Obviously this PR is the wrong place to discuss other bugs and I should just open an issue for them. But I don't actually intend to use ubj so I didn't really want to spend too long trying to report or fix bugs in it. With these fixes the library works fine in the benchmarking suite (and can correctly read and write both unoptimized UBJSON as well as type- and size-optimized UBJSON in my tests) so that's all I needed. But since ubj it's not production-ready I can leave it out of the benchmark if you're not comfortable with it.
As for the security issues, I believe the main problem is that calls to the read_cb don't actually check the return value to see if the data was truncated, so they tend to use uninitialized memory (such as in priv_ubjr_context_getc().) This is what can lead to crashes or infinite loops. If the library were checking for data truncation this would probably solve most of your problems.

Nah keep it in the benchmark, but I want it to be "production-ready".
What makes you think that it's not? If it's not, I'd like to fix it.  I've
been using it in "production"
for some time and want it to be used.
On Wed, Jan 6, 2016 at 4:47 PM, Nicholas Fraser<EMAIL_ADDRESS>wrote:

Actually the reason I was looking into ubj was because I'm putting
together a benchmarking suite to comparing the performance of libraries for
various schemaless serialization formats (JSON, MessagePack, BSON, UBJSON,
etc.) I ran into these bugs setting up ubj.
There are a few other bugs as well that I didn't try to fix since I can
work around them externally. For example ubjr_open_memory() allocates a struct
mem_r_fd but never frees it. The call to free it in memclose() is
commented out, but even if it wasn't, ubjr_close_context() doesn't
actually call the close_cb so it's leaked either way.
Obviously this PR is the wrong place to discuss other bugs and I should
just open an issue for them. But I don't actually intend to use ubj so I
didn't really want to spend too long trying to report or fix bugs in it.
With these fixes the library works fine in the benchmarking suite (and can
correctly read and write both unoptimized UBJSON as well as type- and
size-optimized UBJSON in my tests) so that's all I needed. But since ubj
it's not production-ready I can leave it out of the benchmark if you're not
comfortable with it.
As for the security issues, I believe the main problem is that calls to
the read_cb don't actually check the return value to see if the data was
truncated, so they tend to use uninitialized memory (such as in
priv_ubjr_context_getc().) This is what can lead to crashes or infinite
loops. If the library were checking for data truncation this would probably
solve most of your problems.
—
Reply to this email directly or view it on GitHub
https://github.com/Steve132/ubj/pull/3#issuecomment-169473059.

Ah sorry, I didn't mean to imply that it shouldn't be used. It was just that the bugs I encountered led me to believe that it wasn't being widely used yet since the UBJSON data that was throwing the parser into an infinite recursion was actually encoded by ubj itself. In any case I'm glad it's working well for you, and hopefully these fixes will allow it to be used in more situations.


[feature] #2040: Add integration test with transaction execution limit

Description of the Change

Added new permission validator that checks for Transfer execution count and sets some limit per time period. I.e. it's possible to limit someone to 10 Transfer transactions per day
Added test which demostrates it. Also there are additional comments so that someone from Orillion project could read this, cause this test is needed for their use-cases

Issue
Closes #2040

Benefits
One more permission validator and one more integration test

Possible Drawbacks

I'm not sure if I used permission validators system on the right way
Should this new validator participate in default_permissions()?

Re: should this be part of default permissions
I think no.

I'v just updated it to new iroha2-dev


StoryChunk merging enhancements

implement StoryChunk merging logic , audit and adjust related functions parameters as needed

closing this issue as the work was done under issue 125


How we used this with Row & column

as we used in our project and insert the text into a row and then column then put this AutoSizeText
nothing will happen and yellow lines still show

The AutoSizetext widget needs bounded constraints to work. So, if you want to use it as a child of the Column, you can wrap the AutoSizeText widget inside a Flexible widget.


Workflow Context

We should chat about and decide how we are going to define the context for client calls. At this moment, the context is Background, with no timeout and no cancelation.

Maybe we should define special contexts in the ProxyMessage. For example, during a ConnectRequest, this is the operation that takes the longest because we have to wait to establish a connection to the server. This operation should have a longer timeout than say a domain describe call to the client. And I think that this can be done using context.

I'm leaning towards having ProxyRequest include a Timeout parameter that you'd use if that makes sense for the specific operation (or you'd just ignore when it doesn't make sense).
We haven't talked about cancellation yet.  The current design is that I'll send you a CancellationRequest to cancel a specific operation identified by RequestId.  This means that all operations I submit to you need to be cancel-able.  This means that you'll need to maintain a table mapping request IDs to requests and have this mapping also have a copy of the cancellation function you'll create for all operations and then you'd simply call the cancellation function for the pending request when you receive a CancellationRequest.  If the operation has already completed, the CancellationReply should indicate this via the CancellationReply.WasCancelled property.

@johncburns1: The ConnectRequest now includes the ClientTimeout property (which defaults to 30 seconds).  You should use this as the timeout and then close this issue.

@johncburns1: It looks like you've coded this, so I'm closing this issue.

My bad. Forgot to close. Thanks for doing that.
On Mon, Jun 3, 2019 at 22:25 Jeff Lill<EMAIL_ADDRESS>wrote:

@johncburns1 https://github.com/johncburns1: It looks like you've coded
this, so I'm closing this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nforgeio/neonKUBE/issues/526?email_source=notifications&email_token=ACIDPTHKG4QQ2SJEECBGJALPYXHB5A5CNFSM4HM3XZIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW3GXWQ#issuecomment-498494426,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACIDPTC3ZQZGUZVIWY6RBBLPYXHB5ANCNFSM4HM3XZIA
.


Filter getCompletions results based on location

See below image.  Intellisense for the type name shows all identifiers.  Only types should be shown.

Just looking at old bugs; this one was fixed in #16206. Only types appear in the completion list in this code.
(A three digit issue; not many of those left...)


Term change suggestion SDG14,15 - [rehabitilitat]

SDG:14, 15
Target & phrase: 14.4 ++
Suggested term/change: rehabilit as a synonym for habitat/fish stock restoration
Reason:

Present in 15.1


buylimit returns null

Hi guys, I'm trying to make a standard buy trade and getting null in response.
getbalances and getticker calls work great.
API permissions all enabled.
Tried also v2 tradebuy with the same result.
Thanks in advance.
`
const bittrex = require('node.bittrex.api');
bittrex.buylimit({
market : 'BTC-LTC',
quantity: 1.2,
rate: 1.3
}, (data) => {
console.log(data); // Output: null
});
`

Have you checked the second parameter for an error?
const bittrex = require('node.bittrex.api');

bittrex.buylimit({
market : 'BTC-LTC',
quantity: 1.2,
rate: 1.3
}, (data, error) => {
    if(!error)
        console.log(data);
    else
        console.log(error);
});

You are right, I went out lame))
I just thought, that the first parameter might be anything, but null anyway.
Sorry for this.

No problem. Can you close the issue?

Sorry, couldn't find the button.


Error message entrypoint stage 'main'

I have this error message
The game crashed whilst initializing game
Error: java.lang.RuntimeException: Could not execute entrypoint stage 'main' due to errors, provided by 'customizableelytra'!
crash-2023-01-04_12.34.46-client.txt

Fixed. You need to have the correct version of trinkets for your minecraft version. You can't use any newer ones.


Trigger for Date Picker React component should be text input instead of button

The Momentum spec shows that the trigger input for Date Pickers should be a text box with ability to manually type in the date. But the examples show the trigger elements being a button

Issue Type

[ ]  Bug Report
[ ]  Feature Request
[x]  Support Request

Component or Pattern Affected
Date Picker
Expected Behavior
On clicking the calendar icon inside the text box, the Date Picker control should show up. It should also validate user manually typing in the date.

Current Behavior
The docs show the usage of a button instead of the proposed text box as the trigger element.

Context
Trying to implement Date Pickers where users should be able to manually type in dates
Your Environment

Library: @momentum-ui/react
Version used: 16.0.1
Browser Name and version: All
Operating System and version: All

@bharath063 other than the misinformation on the site that has been fixed.  Do you have a current design link you can share that requires this type of input change?


support af-south-1 region

Please help keep the CHANGELOG up to date by providing a one sentence summary of your change:
Adds support for new region in Africa

@iliana mind reviewing this?

aws.amazon.com/blogs/aws/new-query-for-aws-regions-endpoints-and-more-using-aws-systems-manager-parameter-store

@softprops  that's good idea. Certainly worth exploring. 👍


Release v0.1.0

This is the first release of Microsoft Authentication Library for Java, currently in preview. This release contains -

Feature parity with ADAL Java
Updated public API to builder pattern
Added telemetry callback
Added support for caching tokens
Added acquire token with silent parameters API

@henrik-me - Pull requests into dev and master trigger the E2E test build, which can be found here: https://identitydivision.visualstudio.com/IDDP/_apps/hub/ms.vss-ciworkflow.build-ci-hub?_a=edit-build-definition&id=785&view=Tab_Triggers.  Unit tests are run as part of CI and Release builds - look at the Maven build task and unit test results can be found about halfway down the page.


Fails to run when segment_size is set to anything except 256 in mdx_params of Separator

Trying to run the library similarly to how I use UVR5; I wanted to run a model with a larger segment size, but I can't seem to get anything other than the default 256 to work at all on either of the two MDX models I've tried (Voc FT and Inst HQ 4).
Running the below code works normally:
from audio_separator.separator import Separator

sep = Separator(model_file_dir="./models", invert_using_spec=True)

# sep.load_model("UVR-MDX-NET-Inst_HQ_4.onnx")

# prim, _ = sep.separate("test.wav")

sep.load_model("UVR-MDX-NET-Voc_FT.onnx")

voc, _ = sep.separate("test.wav")

...outputs two stems as wav files in the parent directory, as expected.
But changing this line:
...
sep = Separator(model_file_dir="models", invert_using_spec=True, mdx_params={"segment_size": 1024})
...

gives the following output:
2024-03-14 15:57:19,547 - INFO - separator - Separator version 0.15.3 instantiating with output_dir: None, output_format: WAV
2024-03-14 15:57:19,547 - DEBUG - separator - Secondary step will be inverted using spectogram rather than waveform. This may improve quality, but is slightly slower.
2024-03-14 15:57:19,548 - INFO - separator - Operating System: Windows 10.0.19045
2024-03-14 15:57:19,548 - INFO - separator - System: Windows Node: realbox Release: 10 Machine: AMD64 Proc: AMD64 Family 25 Model 33 Stepping 2, AuthenticAMD
2024-03-14 15:57:19,548 - INFO - separator - Python Version: 3.11.7
2024-03-14 15:57:19,548 - INFO - separator - PyTorch Version: 2.1.2+cu121
2024-03-14 15:57:19,566 - INFO - separator - FFmpeg installed: ffmpeg version 2024-02-04-git-7375a6ca7b-essentials_build-www.gyan.dev Copyright (c) 2000-2024 the FFmpeg developers
2024-03-14 15:57:19,568 - DEBUG - separator - Python package: onnxruntime-silicon not installed
2024-03-14 15:57:19,570 - INFO - separator - ONNX Runtime GPU package installed with version: 1.17.1
2024-03-14 15:57:19,570 - INFO - separator - ONNX Runtime CPU package installed with version: 1.16.3
2024-03-14 15:57:19,589 - INFO - separator - CUDA is available in Torch, setting Torch device to CUDA
2024-03-14 15:57:19,589 - INFO - separator - ONNXruntime has CUDAExecutionProvider available, enabling acceleration
2024-03-14 15:57:19,589 - INFO - separator - Loading model UVR-MDX-NET-Voc_FT.onnx...
2024-03-14 15:57:19,589 - DEBUG - separator - File already exists at ./models\download_checks.json, skipping download
2024-03-14 15:57:19,590 - DEBUG - separator - Model download list loaded
2024-03-14 15:57:19,590 - DEBUG - separator - Searching for model_filename UVR-MDX-NET-Voc_FT.onnx in supported_model_files_grouped
2024-03-14 15:57:19,590 - DEBUG - separator - Single file model identified: MDX-Net Model: UVR-MDX-NET Voc FT
2024-03-14 15:57:19,590 - DEBUG - separator - File already exists at ./models\UVR-MDX-NET-Voc_FT.onnx, skipping download
2024-03-14 15:57:19,591 - DEBUG - separator - Returning path for single model file: ./models\UVR-MDX-NET-Voc_FT.onnx
2024-03-14 15:57:19,591 - DEBUG - separator - Model downloaded, friendly name: MDX-Net Model: UVR-MDX-NET Voc FT
2024-03-14 15:57:19,591 - DEBUG - separator - Calculating MD5 hash for model file to identify model parameters from UVR data...
2024-03-14 15:57:19,591 - DEBUG - separator - Calculating hash of model file ./models\UVR-MDX-NET-Voc_FT.onnx
2024-03-14 15:57:19,605 - DEBUG - separator - Model ./models\UVR-MDX-NET-Voc_FT.onnx has hash 77d07b2667ddf05b9e3175941b4454a0
2024-03-14 15:57:19,606 - DEBUG - separator - VR model data path set to ./models\vr_model_data.json
2024-03-14 15:57:19,606 - DEBUG - separator - File already exists at ./models\vr_model_data.json, skipping download
2024-03-14 15:57:19,606 - DEBUG - separator - MDX model data path set to ./models\mdx_model_data.json
2024-03-14 15:57:19,606 - DEBUG - separator - File already exists at ./models\mdx_model_data.json, skipping download
2024-03-14 15:57:19,607 - DEBUG - separator - Loading MDX and VR model parameters from UVR model data files...
2024-03-14 15:57:19,607 - DEBUG - separator - Model data loaded from UVR JSON using hash 77d07b2667ddf05b9e3175941b4454a0: {'compensate': 1.021, 'mdx_dim_f_set': 3072, 'mdx_dim_t_set': 8, 'mdx_n_fft_scale_set': 7680, 'primary_stem': 'Vocals'}
2024-03-14 15:57:20,238 - DEBUG - common_separator - Common params: model_name=UVR-MDX-NET-Voc_FT, model_path=./models\UVR-MDX-NET-Voc_FT.onnx
2024-03-14 15:57:20,238 - DEBUG - common_separator - Common params: primary_stem_output_path=None, secondary_stem_output_path=None
2024-03-14 15:57:20,238 - DEBUG - common_separator - Common params: output_dir=None, output_format=WAV
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: normalization_threshold=0.9
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: enable_denoise=None, output_single_stem=None
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: invert_using_spec=True, sample_rate=44100
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: primary_stem_name=Vocals, secondary_stem_name=Instrumental
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: is_karaoke=False, is_bv_model=False, bv_model_rebalance=0
2024-03-14 15:57:20,239 - DEBUG - mdx_separator - MDX arch params: batch_size=1, segment_size=1024
2024-03-14 15:57:20,240 - DEBUG - mdx_separator - MDX arch params: overlap=None, hop_length=None, enable_denoise=None
2024-03-14 15:57:20,240 - DEBUG - mdx_separator - MDX arch params: compensate=1.021, dim_f=3072, dim_t=256, n_fft=7680
2024-03-14 15:57:20,240 - DEBUG - mdx_separator - MDX arch params: config_yaml=None
2024-03-14 15:57:20,240 - DEBUG - mdx_separator - Loading ONNX model for inference...
Traceback (most recent call last):
  File "t:\python-audio-separator-test\Untitled-1.py", line 10, in <module>
    sep.load_model("UVR-MDX-NET-Voc_FT.onnx")
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\audio_separator\separator\separator.py", line 605, in load_model
    self.model_instance = separator_class(common_config=common_params, arch_config=self.arch_specific_params[model_type])
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\audio_separator\separator\architectures\mdx_separator.py", line 106, in __init__
    self.model_run = onnx2torch.convert(self.model_path)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx2torch\converter.py", line 72, in convert
    onnx_model = safe_shape_inference(onnx_model_or_path)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx2torch\utils\safe_shape_inference.py", line 46, in safe_shape_inference
    return _shape_inference_by_model_path(onnx_model_or_path, output_path=tmp_model_file.name, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx2torch\utils\safe_shape_inference.py", line 24, in _shape_inference_by_model_path
    return onnx.load(output_path)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx\__init__.py", line 208, in load_model
    model = _get_serializer(format, f).deserialize_proto(_load_bytes(f), ModelProto())
                                                         ^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx\__init__.py", line 145, in _load_bytes
    with open(f, "rb") as readable:
         ^^^^^^^^^^^^^
PermissionError: [Errno 13] Permission denied: 'T:\\python-audio-separator-test\\models\\tmptftn7wrq'

Tried the same code on M1 Mac, but the issue doesn't reproduce.

That's really strange, since the error message you saw in your first debug log output seems to be a permissions issue with a temporary folder, which I wouldn't expect to have anything to do with that parameter...
However, honestly I haven't tested on Windows at all, I don't have a Windows machine to hand and don't really know how to use that operating system these days so I'm not very well equipped to help.
I develop on a Mac and test on Linux (in a docker container).
Are you able to run Docker on your Windows machine? If so, that's probably the easiest way to get things to "just work", as the docker container will run within a Linux VM which will likely resolve any file path and/or permission issues.
I do note that there is a (subtle, but relevant) difference between your two example code lines though - in one you're setting model_file_dir to "./models" and the other, "models".
Technically those should both be relative paths to the same directory you're in, but windows file paths are weird (backslash instead of forward slash) so you might want to try experimenting with that!
If you want to try and debug it more thoroughly with support from me I'm happy to jump on a screen share call some time to investigate properly, just let me know a good date/time/timezone for you! I just don't have a Windows machine to do that myself :)

Ah, sorry, that's just from me testing to make sure the paths weren't a problem. I removed all the spaces from the path, and I put the dot slash to make sure that it was getting the correct models folder, but the result was the same.
I'm sure it would work in the docker container, now seeing that it worked fine on my own Mac. I'll experiment more later and come back with any updates, if I find anything else or if I get something working. I'll close the issue for now.

Thanks for the pointer @helloimmatt !
I don't have a Windows machine to test on but I've opened this PR with what I think you're suggesting the fix is?
If you're able to reproduce the error, please could you test that branch (name: attempt-to-test-windows-mdx-fix) on your machine to see if it fixes it? 🙇
Cheers,
Andrew

Thanks for testing and confirming @helloimmatt !
FYI @CarpetBook and anyone else who sees this - this issue on Windows should be fixed from v0.16.5 onwards 🙏


Translate to Brazilian Portuguese

Hey Carbon team!
I was hoping I could translate your docs to Brazilian Portuguese if that's something you guys would like.
Thanks, Izabela.

@izabelacborges absolutely! Go for it


Developer Tools Theme

It is possible to style the Developer Tools too. Would be great to have both (Atom and Dev Tools) in the same (dark) theme.
For inspiration: https://atom.io/packages/dev-tools-themes

I'm not sure about this. It'd be nice to have, sure, but I really don't think there will be many people going through the hassle of enabling it. If I end up doing it, I would probably make a separate package for it.

...but I really don't think there will be many people going through the hassle of enabling it.

Only package authors I guess, whom should be familiar with Dev Tools.

I would probably make a separate package for it

That's perfect too. Then there's Material UI, Material Syntax and Material Dev Tools Theme :+1:

In an attempt to clean up my created issues that have not been processed or updated over a year, I'm closing this issue. If this issue is still relevant, please reopen another issue.


feat: add task to periodically delete expired events

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

-3 of 15 (80.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 92.903%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/app.module.ts
0
1
0.0%

src/nostr/nostr.module.ts
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
507

Relevant Lines:
561

💛  - Coveralls


Consider constraints when sorting columns

The ordering of columns is a great option that we use for a while now. The current implementation however does not take table CONSTRAINTs into account. This results in all CONSTRAINTs to be placed in front of the columns definitions, which is not the PostgreSQL default. And it does not actually sort the CONSTRAINTs since it only sorts based on the first word of the statement.
This PR fixes both issues.
PS: most whitespace correction tools enforce files to end with a single end-of-line character by default. The dump always ends with 2. It is a small issue I also fixed here, but if you like I can place it in a separate PR.
Let me know what you think.

Hi Lukas,
Do you have time to look at this PR? It changes the output structure from:
CREATE TABLE(
  CONTRAINT c,
  CONTRAINT a,
  CONTRAINT b,
  column_a,
  column_b,
  column_c
)

to:
CREATE TABLE(
  column_a,
  column_b,
  column_c,
  CONTRAINT a,
  CONTRAINT b,
  CONTRAINT c
)

@nvanoorschot It's been a long time. Is this still something you're looking to get in? If so, please confirm and rebase on latest master. If you could address the comment from @RKushnir as well, that would help.
Can you confirm that this change would re-order all the existing constraint positions in the existing db/structure.sql files, out in the wild? If so, we should probably put that in the Changelog notes at a minimum.
Did you get a chance to verify all constraint types are treated the same, even if they aren't in your schema? PK, FK, Unique, Not null, check, Exclusion etc.? https://www.postgresql.org/docs/current/ddl-constraints.html

If you could address the comment from @RKushnir as well, that would help.

Oh, thanks for the hat tip :) But I no longer know what I meant with that comment and I would probably not suggest that today. So I'm just going to withdraw my comment, pretend it's not there :)


cpp-library plugin needs suport for cross-compiling for Arm

The older c and cpp plugins could be configured with custom tool chains to support building for linux-arm on linux x86_64.  The new preferred cpp-library needs this ability.
Expected Behavior
I should be able to add target machines such as:
  library {
    targetMachines = [
      machines.linux.x86, machines.linux.x86_64,  // Linux Intel 32/64-bit
      machines.linux.arm, machines.linux.aarch64  // Linux Arm 32/64-bit
    ]
  }

A new mechanism is needed to define a new machine type or specify the tool chain for a type.
Current Behavior
We can't cross-compile for Arm currently
Context

I want to avoid the old c and cpp plugins (which are very complicated to configure) and adopt the new cpp-library plugin, but I have existing code and future needs to build the same project on Linux, Windows and macOS, both 32- and 64-bit for Linux and windows in addition to 32 and 64-bit Arm for Linux.
I am building for an application framework that uses the same source code for desktops and embedded devices.
Your Environment
Windows 10 64-bit Intel
Linux (Ubuntu/CentOS) 64-bit Intel, targeting both Intel and Arm
macOS

+1

+1 Also need this.  All our current builds use the component model and cross compile for arm.  We'd like to start migrating to the new plugins.
For anyone who is interested, I was able to compile a hello world program for arm using the new Gradle cpp-application plugin and clang.  I'm not suggesting this is a good solution, but it did compile an arm binary.
Dockerfile:

FROM ubuntu:bionic
Setup useful environment variables
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install -qq -y
clang
openjdk-11-jdk
g++-aarch64-linux-gnu
gcc-aarch64-linux-gnu
g++-7-aarch64-linux-gnu
gcc-7-aarch64-linux-gnu
gcc-7-multilib
g++-7-multilib
lld-6.0
&& rm -rf /var/lib/apt/lists/*

build.gradle

plugins {
id 'cpp-application'
}
application {
binaries.configureEach {
def compileTask = compileTask.get()
def linkTask = linkTask.get()
if (toolChain instanceof Clang) {
  compileTask.compilerArgs = ["-fuse-ld=lld", "--sysroot", "/usr/aarch64-linux-gnu", "-I/usr/aarch64-linux-gnu/include/c++/7/aarch64-linux-gnu", "-march=armv8-a", "-static", "-target", "aarch64-linux-gnueab\

i"]
linkTask.linkerArgs = ["-fuse-ld=lld", "--sysroot", "/usr/aarch64-linux-gnu", "-I/usr/aarch64-linux-gnu/include/c++/7/aarch64-linux-gnu", "-march=armv8-a", "-static", "-target", "aarch64-linux-gnuea
bi"]
}
}
}

Does anyone have a workaround?

My workaround is to use the old "cpp" plugin from Gradle 4 instead of "cpp-library". It's routine to define new platforms in the "cpp" plugin, whereas "cpp-library" seems to be limited to 6 hardcoded ones.
Also note that the Android plugins handle ARM architectures, so it's surprising that "cpp-library" can't!

This is how I do it based on many helpful hints from @lacasseio and others:
https://github.com/pedrolamarao/psys/blob/master/buildSrc/src/main/groovy/toolchain.groovy

@pedrolamarao It looks like that is using a different plugin 'dev.nokee.cpp-library' not 'cpp-library'


Dependabot + Dependabot Fixer

Dependabot won't work with flit until it upgrades pip: https://github.com/dependabot/dependabot-core/pull/4345

Blocked by https://github.com/dependabot/dependabot-core/issues/3290 and/or https://github.com/dependabot/dependabot-core/issues/4483


cmake, doc: Amend Windows build notes

Tested on Windows 11 +  WSL + Ubuntu 24.04.
Cleaned up old workaronds (https://github.com/bitcoin/bitcoin/pull/11437 and https://github.com/bitcoin/bitcoin/pull/19408) which no longer seem required.

Friendly ping @sipsorcery @fanquake @pablomartin4btc @m3dwards :)

Rebased.

ACK 87b4c0843f78e4c3351bd9746884103e6ca7f318
Using instructions I was able to build, test and create windows installer using WSL (Ubuntu 24.04 based)


Use ChemSpaX for subfunctionalisations

For a project I needed to explore chemical space with substituents that could have some substitutions (called subsubstitutions) as well. I added code to ChemSpaX to perform these subsubstitutions. This code is especially useful for high-throughput situations.

Amazing work Mark!
In terms of compatibility, I see that this branch continued from a point in time after your bachelor's project, but it still has a lot of old/redundant files that were removed. To get it fixed it's probably easiest to clone the latest version of the main branch, make your own branch and then implement your changes. You could also work with the current high-throughput branch and try to make it completely similar to the current version of main, but that is a tedious task prone to errors. Additionally I would ask you to add .DS_Store and .xtboptok files to the gitignore so they are not pushed

[ ] Fix branch such that it is similar to current version of main
[ ] Add DS_Store and xTB related files to gitignore
[ ] Add an example of running subfunctionalizations in run_example.py

I will do a final test run after these things are done and then we should be ready to merge!

Pull request changed to new branch that can be found here: https://github.com/EPiCs-group/chemspax/pull/24.


Incorrect fluent terminology

The Fluent docs refer to units of translated text as messages, as opposed to keys.

Thank you for your issue! Would you be able to link examples of where this is present? It's a bit hard to tell what to do otherwise.

The Zola function calls it key.

Ah I see what you mean. I'm a bit torn on which is preferable as key is more general terminology that more people will know and is less characters to type.


feat!: unify the importModule behavior of cjs and esm

Description
When I migrated this library to unbuild, I found that the behavior of importModule was inconsistent under cjs and esm, so can the two be unified?
This PR also adds the dependency of mlly and migrates tsup to unbuild.

Linked Issues
Additional context

Seems good. Let's try it.


1.4 assignment

the import from uio import StringIO does not work. Replacing uio with io solves the issue
the import ussl does not work. Replacing it with ssl solves the issue. Same for the use of ussl.CERT_REQUIRED in line 63 of microcontroller_client.py
the my-secrets.py from previous toutorials/assigments did not contain COURSE_ID. This variable is added withing assignment 1.4 and can cause confusion when the user tries to keep working with his old version of my-secrets.py
Maybe irrelevant: DeprecationWarning: Callback API version 1 is deprecated, update to latest version

Regarding the structure of this assignment, I must admit until now I did not get it, even though I really tried. What I don't understand is, why there are dummy functions used withing the tests even though I must be connected with the microcontroller and have the code running there. I would have expected to either have a tests environment in codespace which can run without the microcontroller at all, or having everything be running on the physical hardware.

Alright, I get it, Thanks for the clarification.  Just a hint, that the tests will run with both, dummy and "real world" functions. That way the user can focus on the code and will hopefully not spend his time thinking about something, which is actually irrelevant for him in that moment.

Aside, hopefully should address first point for future learners


"Animated Node with tag2 does not exist"  - Error Message while running App in Emulator

Hi,
While trying to run the app in an emulator, I am getting the below error.
Could you please check.

Thanks,
Rohit

Try reinstalling it with: expo install
Or try to downgrade react-native and expo sdk package to older version. @RohitSreekumar1994

Hi Earl,
Its resolved after downgrading the react-native version
Thanks,
Rohit


Add domain of Haute École Robert Schuman hers.be

the university official website URL, if it is different from the domain you are submitting: https://hers.be
a URL of a page on the official website where a long-term (>1 year) IT related course is offered by the university: http://progcours.hers.be/cocoon/en/programmes/E1INFO01_C.html
a URL of a page or some other proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the enrolled students.: https://hers.be/vie-etudiante/organisation/office-365-pour-tous

@vincent-spies Pull request merged. Thank you!


test:thanos querier e2e test - wait for deployment to be ready

This should fix the test failing with:
E0322 09:17:13.829822   42915 portforward.go:409] an error occurred forwarding 10902 -> 10902: error forwarding port 10902 to pod b607bb8a7641f1f305367d46323a9525283056d28cb3d86ac85cc8d0b5bc59e5, uid : sandbox b607bb8a7641f1f305367d46323a9525283056d28cb3d86ac85cc8d0b5bc59e5 is not running
panic: lost connection to pod

/lgtm

/test observability-operator-e2e


[Bug] Playing an exist torrent isn't working

When trying to play a torrent that exists in torrents list (From Trakt lists or directly from the torrents list), it opens the dialog but doesn't play it, even when the init buffer already reached to 100%
Expected Behavior
Pressing on an exist torrent in the torrents list, or play it from the Trakt menus should play it (When the init buffer reached to 100%)
Current Behavior
Instead, now it's only shows the dialog without playing it.
Steps to Reproduce (for bugs)

Add a new torrent for downloading.
While it's dowloading and the init buffer reached to 100% check this:
a. Playing it from the torrent list.
b. Playing it from the Trakt Collection list
(a & b should be act the same)

Also a strange issue with the percentage value, before restart kodi it shows 100%, now after restarting kodi it shows -1.00%.

I think the problem starts in 0.1.14 (But I'm not sure)

Your Environment
Kodi Log 1 (Playback issue): https://paste.ubuntu.com/p/r5YgSgmvqt
Kodi Log 2 (Percentage issue): https://paste.ubuntu.com/p/SWmkFN9Qxc
Elenetum: 0.1.14
Kodi: 17.6
OS: Windows 10, 64bit

Please, try v0.1.16.

Thanks, It seems that it's ok now with 0.1.16


Why doesn't aws_ec2_instance_type table support the account_id (and region) column?

It's hard to query instance types as a single list because this table does not allow you to filter to a single account. As a result you get many duplicates.
Also - do instance types vary by region? If so, should this table be querying by region?

In addition to the above, would be also useful to be able to filter by instance family m5a, m5, t3, etc - This would drastically increase performance.

@e-gineer / @graza-io, I've submitted a PR to address this issue. Here are the changes implemented:

We can now obtain results for each region.
It's possible to filter by instance type as demonstrated (select instance_type, region from aws_ec2_instance_type where instance_type = 'r6g.large').
The API does not support filtering by instance family. While specific instances like m6g.metal can be filtered, broader family filters like m6g are not supported. Reference: AWS API Documentation

Also - do instance types vary by region? If so, should this table be querying by region?

Yes, it varies from region to region.
> select count(*) from aws_ec2_instance_type where region = 'us-east-1'
+-------+
| count |
+-------+
| 776   |
+-------+

> select count(*) from aws_ec2_instance_type where region = 'ap-south-1'
+-------+
| count |
+-------+
| 518   |
+-------+

Please let me know if I have missed any other implementations.
Thank you!


pager + freehand don't work

Not enough information provided. Please always include a detailed description, your code, any errors, expected and actual behaviour, and screenshots where possible.


After bot registration: Object reference not set to an instance of an object

After registering the bot successfully, which also already works in Azure Bot Service view, the bot can no longer accessed in https://dev.botframework.com/bots: When clicking the bot, the following error is raised from backend: https://dev.botframework.com/api/BotManager/Bots?id=wai-clone

I've successfully registered the same bot earlier (same code, another instance), but seems that something has gotten broken since.

Hi juhamust,
Thank you for your submission.
I've seen this many times also.  Closing other dev.botframework tabs, and signing out/back has refreshed the session and allowed me to proceed whenever I've encountered it.  Inconvenient, but does get passed the "Object reference" issue.  It is somehow tied to session.  The developers working on the portal are aware of it.
I'm closing this because the issue is with the dev.botframework portal, and this is the Microsoft BotBuilder repository.  If, after cycling your login, the issue persists, please re-open and/or comment.

Thanks for the quick response! Indeed, the bot started to working after re-login.
As for the tickets, you might want to add a separate address for site -related issue (if they can be recognised as such): https://docs.botframework.com/en-us/support/


Error on First Use of a Facet

version: OpenRefine 3.0
OS: Windows 7E
Browser: Chrome
Java: jre1.8.0_66

I'm seeing the terminal post an error with v3.0. It happens whenever I start a new project -- I can edit cells, move columns, etc, but the first time I try to create a facet, I get the above error and the "Working" screen keeps turning over. If I reload the browser page and try the facet again, it works. It seems to affect all facet types, but only the first time one is created.
Checked on Linux version 3.0, and not seeing the same behavior.

This looks like its an issue in the DERI RDF extension version you are using.
This might be easily fixed if you use the newest version under here ? https://github.com/stkenny/grefine-rdf-extension/releases
Correct @stkenny ?

Ah! I had no idea there was a new version. I was under the impression that the RDF extension had been abandoned?

You can see the semi-complete list of extensions on our Downloads page and scroll down (notice we have both versions of RDF extension) http://openrefine.org/download.html#list-of-extensions

I am wondering if there is a good practice to maintain the interface between the core and plugin in a way that can allow the core part change without breaking plugin. Or Openrefine's plugin mechanism is too rigid to extend.

@jackyq2015 I don't see why not...that was the whole idea of the command/operations partitioning that David did...I further recall that plugins would be able to use and extend operations... that would be done through the AbstractOperations ?? and the idea was simple in practical terms... core + op  https://github.com/OpenRefine/OpenRefine/blob/master/main/src/com/google/refine/operations/OperationRegistry.java#L74
Question is:  if it is abstracted enough, and can even create/use custom metadata during a plugin's abstracted operations ?

In another piece of s/w I’ve written extensions for the extension was required to state a version compatibility which would be used by the main s/w to decide whether to load the extension or not.
Would this be an approach we could take with OR?

@ostephens sure, that would make sense, but that would probably require tweaking Butterfly, I think.
Rather than trying to fix this obsolete and unmaintained library I would prefer migrating to something standard like Spring.


Failure when Explicit VR contains Implicit VR

So this is another one with an invalid dicom, which is a case I think should be handled.
This is one where a dicom comes in with ExplicitVRLittleEndian TS and some elements don't actually have VRs.  The way the explicit VR decoder is doing that is by setting the VR to UN here which then causes it to read the two extra reserved bytes which may or may not be there depending on what the actual VR is supposed to be.
I've reproduced this by taking a basic pydicom test file, adding a private tag and manually deleting the VR bytes, so the section of the file looks like this:
00000316: 11 00 10 00 4c 4f 04 00                (0011, 0010) LO Length: 4
0000031e: 54 65 73 74                            b'Test'
00000322: 11 00 01 10 02 00 00 00                (0011, 1001) None Length: 2
0000032a: 31 32                                  b'12'

so this section of the file looks like this, which gives an error when I dicom-dump
➜  ~ $ dicom-dump ~/Downloads/mr_broken.dcm
/home/naterichman/Downloads/mr_broken.dcm:
Could not read data set token

Caused by these errors (recent errors listed first):
  1: Could not read 1585713 value bytes for element tagged (0011,1001)
  2: Could not read value from source at position 480
  3: failed to fill whole buffer

Part of the reason I think this should be supported is because pydicom supports it :wink:  The way its done in pydicom is here where they first try to read explicit and then if the resulting VR is not alphabetical, they fall back to implicit.
I'm not sure how that would work with the design here and I fully understand that this library cannot be as dynamic as python, but I think at least the error should be clearer, i.e. if the VR is not present when reading when reading an explicit DS make that the warning instead of trying to parse the length from the next bytes.
Link to documents, I uploaded both the original and the one I edited to be broken: onedrive

Thank you for reporting. Can you validate that this is a duplicate of https://github.com/Enet4/dicom-rs/issues/169?
It's a rare scenario, but it's true that the parser currently misbehaves when entering nested sequences with the VR UN.

Yep, it seems to be the same thing from what I can tell without having the original file of the issue author, except this is just an invalid element, not the small exception within sequences.   I'm happy to take a crack at this one, except I don't think your proposed solution would work for this particular case

From the moment it enters a sequence of VR UN, it would remember to always use implicit VR little endian until it reaches the end of that sequence

since this isn't in a sequence. LMK your thoughts

So I see. This is something else all right!
It should be fine to introduce some simple logic there if it helps read that file to completion.


Basic: guard against nullptr for env

env is a default'ed parameter.  In some cases it may be passed a nullptr,
which is not a valid parameter to llvm::toStringRefArray.  Guard against this
case.  This allows the swift compiler to work again on Windows!

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test and merge


Update automatically-merging-a-pull-request.md

Why:
The sentence was grammatically incorrect.

What's being changed:
Added missing 'with' to create a correct sentence.

Check off the following:

[x] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[ ] For content changes, I have reviewed the localization checklist
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

@KnapSac Thanks so much for opening a PR! I'll get this triaged for review ⚡

@KnapSac Thanks so much for opening a PR! I'll get this triaged for review ⚡

سلام به خوبا

سلام به خوبا

با سلام بی صبرانه منتظر چنین روزی بودم
در تاریخ سه‌شنبه ۲۶ ژانویهٔ ۲۰۲۱، ۱۲:۵۸ ب.ظ Casper Verhaar <
<EMAIL_ADDRESS>نوشت:

Why:
The sentence was grammatically incorrect.
What's being changed:
Added missing 'with' to create a correct sentence.
Check off the following:

I have reviewed my changes in staging. (look for the
deploy-to-heroku link in your pull request, then click View
deployment)
For content changes, I have reviewed the localization checklist
https://github.com/github/docs/blob/main/contributing/localization-checklist.md
For content changes, I have reviewed the Content style guide for
GitHub Docs
https://github.com/github/docs/blob/main/contributing/content-style-guide.md
.

You can view, comment on, or merge this pull request online at:
https://github.com/github/docs/pull/3184
Commit Summary

Update automatically-merging-a-pull-request.md

File Changes

M
content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
https://github.com/github/docs/pull/3184/files#diff-254330945d06dc5741831f0a5e811348785cf0a422d424f83c09c59367d21a78
(2)

Patch Links:

https://github.com/github/docs/pull/3184.patch
https://github.com/github/docs/pull/3184.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/3184, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ART63TR65XAVMXEFLPX64E3S32DMRANCNFSM4WTEFXIQ
.

با سلام بی صبرانه منتظر چنین روزی بودم
در تاریخ سه‌شنبه ۲۶ ژانویهٔ ۲۰۲۱، ۱۲:۵۸ ب.ظ Casper Verhaar <
<EMAIL_ADDRESS>نوشت:

Why:
The sentence was grammatically incorrect.
What's being changed:
Added missing 'with' to create a correct sentence.
Check off the following:

I have reviewed my changes in staging. (look for the
deploy-to-heroku link in your pull request, then click View
deployment)
For content changes, I have reviewed the localization checklist
https://github.com/github/docs/blob/main/contributing/localization-checklist.md
For content changes, I have reviewed the Content style guide for
GitHub Docs
https://github.com/github/docs/blob/main/contributing/content-style-guide.md
.

You can view, comment on, or merge this pull request online at:
https://github.com/github/docs/pull/3184
Commit Summary

Update automatically-merging-a-pull-request.md

File Changes

M
content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
https://github.com/github/docs/pull/3184/files#diff-254330945d06dc5741831f0a5e811348785cf0a422d424f83c09c59367d21a78
(2)

Patch Links:

https://github.com/github/docs/pull/3184.patch
https://github.com/github/docs/pull/3184.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/3184, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ART63TR65XAVMXEFLPX64E3S32DMRANCNFSM4WTEFXIQ
.

Komakam konid khasteh shodam  khodaro shokr mikonam ye hamzabon peyda
kardam
در تاریخ پنجشنبه ۲۸ ژانویهٔ ۲۰۲۱، ۳:۳۵ ق.ظ Afsaneh Heydari <
<EMAIL_ADDRESS>نوشت:

با سلام بی صبرانه منتظر چنین روزی بودم
در تاریخ سه‌شنبه ۲۶ ژانویهٔ ۲۰۲۱، ۱۲:۵۸ ب.ظ Casper Verhaar <
<EMAIL_ADDRESS>نوشت:

Why:
The sentence was grammatically incorrect.
What's being changed:
Added missing 'with' to create a correct sentence.
Check off the following:

I have reviewed my changes in staging. (look for the
deploy-to-heroku link in your pull request, then click View
deployment)
For content changes, I have reviewed the localization checklist
https://github.com/github/docs/blob/main/contributing/localization-checklist.md
For content changes, I have reviewed the Content style guide for
GitHub Docs
https://github.com/github/docs/blob/main/contributing/content-style-guide.md
.

You can view, comment on, or merge this pull request online at:
https://github.com/github/docs/pull/3184
Commit Summary

Update automatically-merging-a-pull-request.md

File Changes

M
content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
https://github.com/github/docs/pull/3184/files#diff-254330945d06dc5741831f0a5e811348785cf0a422d424f83c09c59367d21a78
(2)

Patch Links:

https://github.com/github/docs/pull/3184.patch
https://github.com/github/docs/pull/3184.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/3184, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ART63TR65XAVMXEFLPX64E3S32DMRANCNFSM4WTEFXIQ
.

Komakam konid khasteh shodam  khodaro shokr mikonam ye hamzabon peyda
kardam
در تاریخ پنجشنبه ۲۸ ژانویهٔ ۲۰۲۱، ۳:۳۵ ق.ظ Afsaneh Heydari <
<EMAIL_ADDRESS>نوشت:

با سلام بی صبرانه منتظر چنین روزی بودم
در تاریخ سه‌شنبه ۲۶ ژانویهٔ ۲۰۲۱، ۱۲:۵۸ ب.ظ Casper Verhaar <
<EMAIL_ADDRESS>نوشت:

Why:
The sentence was grammatically incorrect.
What's being changed:
Added missing 'with' to create a correct sentence.
Check off the following:

I have reviewed my changes in staging. (look for the
deploy-to-heroku link in your pull request, then click View
deployment)
For content changes, I have reviewed the localization checklist
https://github.com/github/docs/blob/main/contributing/localization-checklist.md
For content changes, I have reviewed the Content style guide for
GitHub Docs
https://github.com/github/docs/blob/main/contributing/content-style-guide.md
.

You can view, comment on, or merge this pull request online at:
https://github.com/github/docs/pull/3184
Commit Summary

Update automatically-merging-a-pull-request.md

File Changes

M
content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md
https://github.com/github/docs/pull/3184/files#diff-254330945d06dc5741831f0a5e811348785cf0a422d424f83c09c59367d21a78
(2)

Patch Links:

https://github.com/github/docs/pull/3184.patch
https://github.com/github/docs/pull/3184.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/3184, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ART63TR65XAVMXEFLPX64E3S32DMRANCNFSM4WTEFXIQ
.

👋  Thanks for opening a PR. This doc is accurate as its currently written, so I'm closing this.
You can check out issues with the help wanted label if you want to see other issues ready for PRs. :sparkles:


KAFKA-10894; Ensure PartitionInfo replicas are not null in client quota callback

Previously offline replicas were included as null in the array of replicas in PartitionInfo when populated by the MetadataCache for the purpose of the client quota callback. This patch instead initializes empty non-null nodes, which is consistent with how PartitionInfo is constructed by the clients in MetadataResponse.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@chia7712 Good question about leader(). I looked into usage and it seems we do not have consistent isEmpty checks, so I'm a little concerned about compatibility if we change that. To be honest, I do not like the use of the empty sentinel. It seems like a dangerous practice and I'm not too eager to expand its usage. However, given the choice between returning a list of replica nodes which contains null values (what is done today for this callback) and making use of the empty sentinel in the same way  that it is already used in the client logic, the latter seems preferable. Does that make sense?

@chia7712 Good question about leader(). I looked into usage and it seems we do not have consistent isEmpty checks, so I'm a little concerned about compatibility if we change that. To be honest, I do not like the use of the empty sentinel. It seems like a dangerous practice and I'm not too eager to expand its usage. However, given the choice between returning a list of replica nodes which contains null values (what is done today for this callback) and making use of the empty sentinel in the same way  that it is already used in the client logic, the latter seems preferable. Does that make sense?


Steam Trade Safe

Im just curios: Given that i have Trding bot with now Items worth tons of $$$ how do i keep them safe from getting hacked? is there a way apart from a strong random password ?

Yes, a strong password.
#427

Mobile auth maybe?


Add depends-ciphers.pl

Description
Add a new test script depends-ciphers.pl - this is a step towards https://github.com/ARMmbed/mbedtls/issues/1892
Status
READY
Requires Backporting
YES

This PR can be merged both in development and 2.16
Backport to 2.7: #2316

Migrations
NO
Todos

[x] Tests
[x] Documentation
[x] Changelog updated
[x] Backported

@sbutcher-arm @gilles-peskine-arm Thanks for your review! I believe I've addressed your comments, please review again.

retest

@sbutcher-arm @RonEld @gilles-peskine-arm I believed I addressed your feedback. As the review history wasn't too significant, I've taken the liberty of rewriting the history in order to resolve conflicts (in particular with #930) by rebasing on current development and more cleanly separate fixes to test cases from changes in the script (in the direction suggest by Simon).
The main change is the script now starts from a full configuration as suggested by all of you. As a result, I've found and fixed errors in the CMAC test suite. I've been tempted to do the same in other depends-xxx.pl scripts but the first attempt found non-trivial issues, so I think it would better be handled in a separate PR in order to keep PRs nice and small.
Please (at least two of you) review again.

This PR cannot run CI due to it being based on a branch that doesn't contain a Jenkinsfile. Will run CI manually as part of gatekeeping.

I've just rebased on current development in order to resolve conflicts (and as a welcome side-effect, enable Jenkins testing). @Patater @gilles-peskine-arm please review again. @RonEld @sbutcher-arm you previously requested changes and I think I did all of them, please check and update your review status.

This PR would require significant rework, and a consolidated dependency checking script is in the pipeline, so it's probably best to focus our efforts on the more general solution rather than on this PR.


Blob table  backups

CrateDB version: 1.1.4
JVM version: 1.8.0_102
OS version : RedHat 7.3
Problem description: How is the blob table backed up and restored?

hi @jyyun, at the moment we don't support doing backups for blobs. i will investigate why this is listed in concrete_indices. this should not appear there.

Blobs should no longer appear in concrete_indices (see https://github.com/crate/crate/pull/5968)


[Feature] Complete helm unit tests

Describe the solution you'd like
@gprossliner  introduced helm unit testing in the following PR: https://github.com/mariadb-operator/mariadb-operator/pull/766
We should complete the unit tests to ensure that our manifests render correctly. So far, we only lint and attempt to install our helm chart with the default values in a KIND cluster, something that doesn't test the rendering logic.
Describe alternatives you've considered
None, currently we only do integration test, which complements but does not replace helm unit tests.
helm-unittest seems to be an alternative for unit tests, but the ability to write tests in Go is superior.

I think you need both. Golang unit tests to validate your golang code before and independent from the usage in the Helm chart. Helm unit tests are very helpful to validate your templating logic. We use the unittest plugin in that way...

@businessbean  Absolutely, I'm totally conviced that we need both.

We use the unittest plugin in that way...

Thanks for sharing your use case. How is your experience with helm-unittest? I've used it a long time ago but you probably have more experience with it, right now I believe doing tests in Go the same way we do for the operator currently would be better for us, but I'm happy to hear your thoughts.

helm-unittest is doing a good job. You just need to define rules in Yaml without Helm template or golang knowledge required. Our mariadb-galera Helm chart relies heavily on Helm templating and the unittests help us to keep the complexity under control.
The Helm unittests do not help for the Bash code that runs inside the containers. To improve that area a move to golang (with the related unit tests) would help.
To make it short: helm-unittest will be a help for the mariadb-operator, but the golang unit tests will have a much bigger impact because you have the majority of the functionality in the operator binary.


feature: consider using selene instead of luacheck for linting

Did you check the docs?

[X] I have read all the docs

Is your feature request related to a problem? Please describe.
Someone pointed out luacheck might be falling out of date to me here https://github.com/gsuuon/tshjkl.nvim/pull/10#pullrequestreview-1833965956
I was able to add the selene lua linter in its place very easily. I think this might be a good alternative to consider, as a sort of recommendation for the community.
Describe the solution you'd like

Add a selene command in the Makefile along with minimal configuration for vim apis and testing. These can be found in the PR above as examples.
Add selene as a github action. This is also done in the PR above.

Describe alternatives you've considered

Additional context
There is a detailed comparison between the two linters available here https://kampfkarren.github.io/selene/luacheck.html

In 1.0.0 I opted for using just lua language server. For linting, typechecking and formatting.


Errors when creating a GoogleCloudStorage source with tmctl

It seems like it is impossible today to create a GCS source with tmctl without hitting some errors.
How to reproduce:

Create a service account called triggermesh in GCP IAM that has PubSub Admin and Storage Admin roles
Create a key for the service account and save it as JSON
Create a bucket called triggermesh-bucket

Then run
tmctl create source googlecloudstorage --bucket triggermesh-bucket --pubsub.project <project-name> --serviceAccountKey $(cat serviceaccountkey.json)

Error:
2023/04/06 16:49:52 source initialization: Error obtaining notification configuration for bucket "triggermesh-bucket": adding notification configuration: googleapi: Error 403: The service account<EMAIL_ADDRESS>does not have permission to publish messages to to the Cloud Pub/Sub topic '//pubsub.googleapis.com/projects/object-notifications/topics/local.triggermesh-googlecloudstoragesource~googlecloudstoragesources.sources.triggermesh.io', or that topic does not exist., forbidden

It looks like the bucket's service account service-549199081752... was not given permission to publish notifications to the pub/sub topic created by the triggermesh GCS source. Because this topic was created dynamically by the source, I cannot as a user have provisioned this permission beforehand. Based on a test @FranBarrera did, it sounds like the equivalent command in K8s by creating a GCS source CRD does work and is able to configure these permissions, so maybe there is an issue with the reconciliation logic?
If I manually add the missing permission stated above, then everything works. But it is expected that this should happen automatically.

@jmcx can you check if the same configuration works in K8s for you? I don't see any difference in the CLI and tm/tm reconcilers.

Indeed, same issue on K8s:
{                         "lastTransitionTime": "2023-04-07T14:20:48Z",                         "message": "Access denied to Cloud Storage API: adding notification configuration: googleapi: Error 403: The service account<EMAIL_ADDRESS>does not have permission to publish messages to to the Cloud Pub/Sub topic '//pubsub.googleapis.com/projects/object-notifications/topics/default.gcssource~googlecloudstoragesources.sources.triggermesh.io', or that topic does not exist., forbidden",                         "reason": "APIError",                         "status": "False",                         "type": "Subscribed"                     }

shall we move this ticket to tm/tm ?

shall we move this ticket to tm/tm ?

I think that it may end up as a documentation issue, but right now tm/tm would be a better fit

Indeed: you had to give the Google Cloud Storage service account for the current project the Pub/Sub publisher role on the project to avoid the aforementioned error.
I'll update the docs: https://github.com/triggermesh/docs/issues/365


run question

I have set up the entire environment, including the project, according to the README. The demo.py file in the omniglue folder can output the correct answers. However, if I place the demo.py file in a directory at the same level as the omniglue folder and execute the file, it gives an error. Here is the error screenshot.WHY？

I’ve got a same problem


Check limits in sidecars container for Cloud Composer

@mik-laj can you provide more information and decide if this issue should be closed? Autoscaling is not on our roadmap and KEDA is done.

The latest version of Airflow requires a different configuration of cluster rules, i.e. if the cluster has a minimum resource limit set, the side container may not start. I don't know what policy Cloud Composer has. I suspect it won't be a problem, but I think it's worth checking it out.


Add skip-O0 plugin option

Background: I was trying to use inspection to check unboxing in this file, which yields about 7000 lines of core with -O2, most of which is to be inspected.
I've found that loading in ghci becomes unacceptably slow with inspection, goes from around 2 seconds to something which I don't have the patience to wait for. In contrast, compilation with -O and -O2 is only about 10% slower with inspection.
A possible solution to my problem would be to put inspections in a different module than my definitions. However, I've found that inspection-testing can only follow referenced core definitions in the current module, so this doesn't work for me.
While this slowdown in interactive mode is probably worth to investigate, I think a very simple solution, which seems useful anyway, is to add a plugin option which disables inspection in the case of -O0. So that's what I did.

Do you need a release of this or are you find with this slipping into the next release (whenever that is)?

Thanks for the quick response here! I'm fine with the next release.


chore: remove compiler.build and compiler.rebuild

Summary

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

maybe this should not be called "chore:xxx"


[Question]: How to resolve this error?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
Parsing documents into nodes: 100%|████████████████████████████████████████████████████| 11/11 [00:00<00:00, 64.00it/s]
Generating embeddings: 100%|█████████████████████████████████████████████████████████| 181/181 [02:13<00:00,  1.36it/s]
Internal Server Error: /api/chat-with-custommodel/
Traceback (most recent call last):
File "D:\djangosass\sass_env\Lib\site-packages\django\core\handlers\exception.py", line 55, in inner
response = get_response(request)
^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\django\core\handlers\base.py", line 197, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\django\views\decorators\csrf.py", line 56, in wrapper_view
return view_func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\django\views\generic\base.py", line 104, in view
return self.dispatch(request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\rest_framework\views.py", line 509, in dispatch
response = self.handle_exception(exc)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\rest_framework\views.py", line 469, in handle_exception
self.raise_uncaught_exception(exc)
File "D:\djangosass\sass_env\Lib\site-packages\rest_framework\views.py", line 480, in raise_uncaught_exception
raise exc
File "D:\djangosass\sass_env\Lib\site-packages\rest_framework\views.py", line 506, in dispatch
response = handler(request, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\hr_management\views.py", line 82, in post
response = query_engine.query(input_text)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\llama_index\indices\query\base.py", line 23, in query
response = self._query(str_or_query_bundle)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\llama_index\query_engine\retriever_query_engine.py", line 170, in _query
nodes = self.retrieve(query_bundle)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\llama_index\query_engine\retriever_query_engine.py", line 118, in retrieve
nodes = self._retriever.retrieve(query_bundle)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\llama_index\indices\base_retriever.py", line 22, in retrieve
return self._retrieve(str_or_query_bundle)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\llama_index\indices\vector_store\retrievers\retriever.py", line 87, in _retrieve
return self._get_nodes_with_embeddings(query_bundle)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\llama_index\indices\vector_store\retrievers\retriever.py", line 164, in _get_nodes_with_embeddings
query_result = self._vector_store.query(query, **self._kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\llama_index\vector_stores\simple.py", line 168, in query
top_similarities, top_ids = get_top_k_embeddings(
^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\llama_index\indices\query\embedding_utils.py", line 30, in get_top_k_embeddings
similarity = similarity_fn(query_embedding_np, emb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\djangosass\sass_env\Lib\site-packages\llama_index\embeddings\base.py", line 48, in similarity
product = np.dot(embedding1, embedding2)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: shapes (1536,) and (768,) not aligned: 1536 (dim 0) != 768 (dim 0)

LlamaIndex  0.8.22

@qxpf666 what embedding model did you use to create the index?
The embedding model used to create the index has to be the same as the one that is used to query

🤖
The error you're encountering is due to a mismatch in the dimensions of the embeddings. The error message ValueError: shapes (1536,) and (768,) not aligned: 1536 (dim 0) != 768 (dim 0) indicates that the system is trying to compare or operate on two vectors of different dimensions, one of dimension 1536 and the other of dimension 768.
This issue has been encountered before in the LlamaIndex repository. Here are some solutions that have been suggested:

The Llama-Index does not support existing collections created outside of it. You need to modify the Chroma implementation to support existing collections. This can be achieved by creating a method to inform Llama-Index where to find key fields such as text, id, etc. This solution was suggested in a similar context for Pinecone and can be applied here as well. You can refer to this issue for more details: Embedding dimension 1536 does not match collection dimensionality 768
You need to start fresh when switching embedding models so that the vector sizes line up. This was suggested in this issue: About customized embedding model
The error could be due to a conflict between the lengths of the huggingface embeddings and the OpenAI embeddings. You are advised to recreate the index using huggingface. This was suggested in this issue: ValueError: shapes (768,) and (1536,) not aligned: 768 (dim 0) != 1536 (dim 0)

The expected dimension of the embeddings in the LlamaIndex framework is determined by the embed_dim parameter in the MockEmbedding class. This parameter is an integer that specifies the dimension of the embedding vector. You can refer to the MockEmbedding class in the llama_index/token_counter/mock_embed_model.py file for more details.
The default embedding dimension used in the LlamaIndex framework is 1536. This is indicated in the constants.py file with the line of code: DEFAULT_EMBEDDING_DIM = 1536. You can refer to the llama_index/constants.py file for more details.
Please try the suggested solutions and let me know if you need further assistance.
Sources

[Question]: Embedding dimension 1536 does not match collection dimensionality 768
About customized embedding model
ValueError: shapes (768,) and (1536,) not aligned: 768 (dim 0) != 1536 (dim 0)
llama_index/token_counter/mock_embed_model.py
llama_index/constants.py

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.

I found the reason for the error. I attempted to use two different storage methods, but it worked when I made them consistent. Thank you very much for your patient responses. Thank you.
"
service_context = ServiceContext.from_defaults(
llm=llm, embed_model=embed_model, chunk_size=1024, chunk_overlap=20)
storage_context = StorageContext.from_defaults(
persist_dir="D:/index/index_json")
index = load_index_from_storage(storage_context)
"


Add new architectures from libseccomp 2.3.2

Signed-off-by: zhouhao<EMAIL_ADDRESS>

LGTM

LGTM


Added ChatUI Screenshot to Docs

cc @osanseviero

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


App Service - Web Site Netframeworkversion property inaccurately reported

Hi,
One issue and one question:
Issue: When running the following the netFrameworkVersion property is being reported as v4.0 (also appears inaccurate when browsing via Resource Explorer so assuming Powershell is relying on the same) even though it is set properly to a higher version on the Azure Portal (Powershell script and output below where the version on Azure Portal has been set via App Service - Application Settings - to v4.7)
$websiteProps = (Get-AzureRmResource -ResourceGroupName 01resgrp -ResourceType Microsoft.Web/sites/config -ResourceName $website.Name -ApiVersion 2018-02-01)
$websiteProps.Properties.NetFrameworkVersion
netFrameworkVersion              : v4.0
Question: Where and how can one set the netFrameworkVersion property for Azure Functions via the Azure Portal? The menu option does not appear under Application Settings.

@jrgithub - This sounds like you're experiencing several issues which aren't related to the documentation. If you have a problem with the Azure PowerShell tool itself, please file an issue with the engineering team: https://github.com/azure/azure-powershell/issues
If you're experiencing problems with Functions or the Portal, you will need to report an issue to that team. Portal issues can be reported through the "Report a Bug" button on the Portal. Functions has a README describing how to get help or file a report: https://github.com/Azure/Azure-Functions


Is it possible to search for information on a specific offer with the offer id?

Is it possible to search for information on a specific offer with the offer id?

Thanks


Bump aws-ecr orb 4.0.1 --> 6.15.2

What
Bump circleci orb used to build and push docker images
to ECR.
see aws-ecr-orb
Testing
I have tested the circleci build and push works on another branch
Why
We are pretty out of date on this orb and am thinking to use it
to set some docker build args.
relates to
Checklist
Before you ask people to review this PR:

[X] Tests and linters should be passing
[X] Github should not be reporting conflicts; you should have recently run git rebase master.
[X] Avoid mixing whitespace changes with code changes in the same commit. These make diffs harder to read and conflicts more likely.
[X] You should have looked at the diff against master and ensured that nothing unexpected is included in your changes.
[X] You should have checked that the commit messages say why the change was made.


During tuning, Connection handles frame-max=0 incorrectly.

Describe the bug
When an AMQP::Connection connects to a server, during the tune step, if the server proposes a frame-max value of 0, the client will be unable to finish connecting, failing silently and potentially blocking forever.
Expected behavior and actual behavior
According to the AMQP Reference Guide (emphasis mine):

The largest frame size that the server proposes for the connection, including frame header and end-byte. The client can negotiate a lower value. Zero means that the server does not impose any specific limit but may reject very large frames if it cannot allocate resources for them.
Until the frame-max has been negotiated, both peers MUST accept frames of up to frame-min-size octets large, and the minimum negotiated value for frame-max is also frame-min-size.

Instead of the above behavior, the client takes the value of 0 as-is, and in the following step when it attempts to respond with tune-ok, it finds that its frame is larger than 0 and does not send the frame. The connection then essentially halts, as neither the client nor the server attempt to take further action.
Sample code
On the server side, the python package amqp-mock (as of version 0.4.0) sends a tune with a frame-max of 0. A simple demo program for the server is as follows:
import asyncio
import logging

from amqp_mock import AmqpServer, HttpServer, Storage, create_amqp_mock

async def main() -> None:
    storage = Storage()
    await storage.bind_queue_to_exchange('demo-queue', 'demo-exchange')

    http_server = HttpServer(storage, port=8080)
    amqp_server = AmqpServer(storage, port=5672)
    async with create_amqp_mock(http_server, amqp_server) as mock:
        messages = storage.get_next_message('demo-queue')
        async for msg in messages:
            print(f"new message : {msg}")
            print('Properties: ', msg.properties)

if __name__ == "__main__":
    logging.basicConfig(level="DEBUG")
    asyncio.run(main())

For the client, any simple program should work. Here's the one I used, based on the libboostasio example, though the behavior should be event-loop-agnostic.
#include <boost/asio/io_service.hpp>
#include <boost/asio/strand.hpp>
#include <boost/asio/deadline_timer.hpp>

#include <amqpcpp.h>
#include <amqpcpp/libboostasio.h>

#include <iostream>

class MyHandler : public AMQP::LibBoostAsioHandler {
public:
    using AMQP::LibBoostAsioHandler::LibBoostAsioHandler;

    void onError(AMQP::TcpConnection *connection, const char *message) override
    {
        std::cerr << message << std::endl;
    }
};

int main(int argc, char** argv)
{
    boost::asio::io_service service(2);
    MyHandler handler(service);

    AMQP::TcpConnection connection(&handler, AMQP::Address("amqp://guest:guest@localhost/"));
    AMQP::TcpChannel channel(&connection);

    channel.onReady([&channel]{
        std::cout << "Connected, publishing message\n";
        channel.publish("demo-exchange", "", "Hello, world!");
    });

    return service.run();
}

Here is the logged output from the server, showing that it sent a tune but never received a tune-ok:

Additionally, after debugging and investigating the AMQP-CPP source code, the fix could be done in one of two places, depending on the preferred approach.

This sets the connection's _maxFrame member to the value received from the tune, i.e. 0: https://github.com/CopernicaMarketingSoftware/AMQP-CPP/blob/c273d936253ed08ff15642d6874406a564b8f9b5/src/connectiontuneframe.h#L135
This compares the frame's size to _maxFrame, and this check will always fail once _maxFrame has been set to 0: https://github.com/CopernicaMarketingSoftware/AMQP-CPP/blob/c273d936253ed08ff15642d6874406a564b8f9b5/src/connectionimpl.cpp#L392

In either of these places, a special case could me made for the special value 0.

Thanks, you are right this was indeed wrong.


adding react-sidebar (missing dependency) and make checkout more dependable

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   87.19%   87.19%
=======================================
  Files          10       10
  Lines         203      203
  Branches       30       30
=======================================
  Hits          177      177
  Misses         26       26

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 0b620df...4e10cea. Read the comment docs.


Code style issue: too long functions

Python google styleguide

Prefer small and focused functions. If a function exceeds about 40 lines, think about whether it can be broken up without harming the structure of the program.

Example
https://github.com/spcl/dace/blob/6e91853c0f4fa06ebdd8672e52b478f9b7219873/dace/transformation/dataflow/map_fusion.py#L194
Pros

More opportunities to reuse
Easier to see what function does by reading called function names, without looking into the implementation of these functions

Possible solution
Split long functions into small functions across the boundaries defined by comments between chunks of block.
Before
def foo():
  # do action X
  some code
  # do action Y
  some code

After
def do_action_X(...):
   some code
def do_action_Y(...):
   some code
def foo():
  do_action_X(...)
  do_action_Y(...)

Agree, we did something like this for unparse_tasklet, for example. I would like to specifically mention memlet_copy_to_absolute_strides (in fact, after using it many times, I still don't really understand what this function does).

I agree. This is a matter of identifying what methods would be suitable for replacing the original one. We can make a list of candidate methods and work on them when there is time.

The difficulty is that this is hard to figure out in advance, and finding time is always a nightmare. Even though we all agree I suspect that unless we have some dedicated slot to do this stuff - something like a once every X months we spend 1-2 evenings on this, I am afraid this will always be pushed back by urgent stuff.


Fix background color on login page

The login page that appears when logging in with eventyay-tickets has a blue background. Result is that only the white part of the logo appears properly. Show the background color in the default color same as the other backgrounds.

HI, i would like to start contributing , how do i start?

Download the project and implement the changes. Then make a PR. Thanks


Design visualizations of audio.

It may be useful to visualize audio entering the numeric input channel of each AudioNode. First, we should research and justify what type of visualization(s) would be most useful - a waveform/oscilloscope? A histogram of the frequency domain?
For starters, a user may want to know whether any audio is going into an input at all. Beyond that, I wonder what information is most useful to visualize.
After making that design call, we use native AnalyserNodes to collect the data needed for visualization. That logic will reside in js/entry-points/tracing.js.

I wrote both a frequency analyser and an oscilloscope with a stabilization feature for waveforms (like on real oscilloscopes). They are both ES6 classes that inherit from the AnalyserNode (and that do not work when your extension is enabled -> I just posted an issue about that). I'm still working on them (removing external dependencies, adding some optional dat-gui widgets, etc.).
Both are fully resizable with labels and fonts adjusted automatically.
You can give a look at current versions in case they can help:

Frequency analyser: https://codepen.io/w3devcampus/pen/GWGdjK?editors=0010
Oscilloscope: http://jsbin.com/cawenaj/edit?js,output, I also started made it an ES6 class that inherits from the AnalyserNode, but I haven't added the sensibility slider yet.

You can see both of them in action with my tube guitar amp simulation (does not work when your extension is enabled): https://wasabi.i3s.unice.fr/AmpSimFA

That might be exactly we need. Both visualizations seem well thought-out.
I think I need authorization to see https://wasabi.i3s.unice.fr/AmpSimFA
Awesome, awesome work. We have to fix #73.

While we're wishing for things, include a spectrogram. :-)
I think this needs some careful thought.  To support visualization, you have to insert an AnalyserNode from this app into the applications audio graph.  This is intrusive.  You have to add some kind of timer to get the data.  That impacts CPU usage on the main thread.  In addition, because audion doesn't know about GCed objects, the point where you want to add visualization may no longer exist.  Or by adding it, the object may not be GCed anymore, breaking how the app might work.
There's also the issue of where this gets displayed. My dev console window is usually at the bottom of the tab so space is limited. I can pop it out when necessary, but then it covers up even more precious screen space.
While I'd love to have a built-in visualizer that I can just attach when needed (my graphs are almost always static), general usage seems complicated.  Actually, for my usage, canopy works perfectly except that you can't visualize arbitrary nodes.  But that can be fixed by sending the node output as another channel to the destination.  Kind of painful, but doable.

https://wasabi.i3s.unice.fr/AmpSimFA/ is public now. It's a recreation of a
Marshall JCM800 tube amp with measure tools (freq analyzer, oscilloscope,
the ones I shared on codepen/jsbin).
You don't need a guitar in order to try it. You can just use the audio
player on the left (try to turn the amp on/off using the switch on the top
tight), or send a sin wave (menu below the audio player) and adjust the
freq/gain. You will see the frequency analyzers in action at different
stages of the amp. You'll also see the waveform in the oscilloscopes at
input and output. Sliders are for stabilizing the waveform. It's
interesting for looking at harmonics that are generated depending on the
different transfer functions I use for the tubes.
If you're on a mac + soundcard + guitar, it plays in real time, and sound
and latency are comparable (well, assuming you've got the same audio buffer
size) with native references such as the JCM800 from Guitar Rig.
Lots of things are missing from these freq analyzer + oscilloscope, I'm
working on them: select freqs to zoom, freeze, display curves instead of
histograms, etc.
I'm also trying to break all external dependencies (global vars in freq
analyzer I was testing things). I'll post updated versions in case you'll
find that interesting.
Le jeu. 6 avr. 2017 à 17:12, rtoy<EMAIL_ADDRESS>a écrit :

While we're wishing for things, include a spectrogram. :-)
I think this needs some careful thought. To support visualization, you
have to insert an AnalyserNode from this app into the applications audio
graph. This is intrusive. You have to add some kind of timer to get the
data. That impacts CPU usage on the main thread. In addition, because
audion doesn't know about GCed objects, the point where you want to add
visualization may no longer exist. Or by adding it, the object may not be
GCed anymore, breaking how the app might work.
There's also the issue of where this gets displayed. My dev console window
is usually at the bottom of the tab so space is limited. I can pop it out
when necessary, but then it covers up even more precious screen space.
While I'd love to have a built-in visualizer that I can just attach when
needed (my graphs are almost always static), general usage seems
complicated. Actually, for my usage, canopy works perfectly except that you
can't visualize arbitrary nodes. But that can be fixed by sending the node
output as another channel to the destination. Kind of painful, but doable.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/audion/issues/72#issuecomment-292205704, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAnl2FS4tyoJdTrJLzM_y_3vMmzp_IQ_ks5rtQDdgaJpZM4Mzxz8
.

Just in case: new version of the frequency analyser with embedded dat-gui + resizeable + just one ES6 class, no more external dependencies. I'm adding some zoom by selecting an area with the mouse + scale the Db vertical axis. You can already try the selection with mouse + drag.
Simple use:
let fa = new FrequencyAnalyzer(audioCtx, parentElem, label);
...
anyWebAudioNode.connect(fa);
fa.connect(audioCtx.destination);
fa.start(); // if you want the freq analyser to run its own requestAnimationFrame
// or if you have your own animation loop with raf, just call fa.update().


Dataset MolHIV

Hi, thanks for sharing the code. However, I wonder whether you miss out on one of the four datasets used in your paper: the MolHIV dataset. Can you please provide some information regarding how you use it and the relevant code?

Hi, thanks. The relevant file is still under revision as some parts are redundent. I included it in  train/molhiv_dir.py and will update it later. I think you can refer to this file for now about using the dataset etc.

thx


added the mentioned AC4 algorithm for constraint propagation

AC3 algorithm has non-optimal worst-case time-complexity O(cd^3 ), while AC4 algorithm runs in O(cd^2) worst-case time. Here the original paper by Mohr and Henderson.

Is it possible to add the code of algorithms whose pseudocode is not present in the book but is only mentioned?


cannot disable packages in settings page in safe mode

I can't load atom in anything but safe mode presumably because of a bad package.  Unfortunately I can't use package-cop because it doesn't work in safe mode.
I went to the settings page to disable packages.  There were two problems ...

When I scroll down, go into settings for a package, I can't go back, can I?.  I have to click on packages again and start at the top.  This is a serious problem when you have 100 packages.

All enabled packages show the Install button which makes no sense.  And since there  is no Settings button I can't disable anything.

I'll use the command-line but that is a lot of typing. The above problems need fixing.
windows 8.1
atom 187

Weird.  I don't see any disable command in apm --help.
I guess I'll move packages out of the folder but this skit is getting silly.

@mark-hahn I agree that some of those things could be improved, thanks for pointing them out. In the meantime, you should be able to disable packages by editing your config.cson file, even in safe mode.
https://atom.io/docs/latest/using-atom-basic-customization#configuration-key-reference
Example from my own config.cson file:
"*":
  core:
    disabledPackages: [
      "the-closer"
    ]

Does that help? Also, I think this issue should be opened on the settings view package, would you mind moving it over there? (Minus the apm-related things -- I believe that's working as expected since enabling/disabling packages isn't an apm concept, it's an Atom concept.)

I had this same issue where my config file got wiped out when my disk got full (runaway log file, related to #3158 ).

FWIW, apm's missing disable command is being tracked in https://github.com/atom/apm/issues/358.

Addressed by https://github.com/atom/apm/pull/400


chore: bump epel

Pull Request (PR) description
This PR bumps the dependency on stahnma/epel.
This Pull Request (PR) fixes the following issues
This PR is a step towards CentOS 8 support.

Does this take into account that stahnma/epel is deprecated and replaced by puppet-epel?
"This module has been deprecated by its author since February 20, 2020.
The reason given was:
Transferred to Vox Pupuli
The author has suggested puppet-epel as its replacement."

No. The PR was made on the 15th of February. At the time there was no indication that it would be archived and replaced.

Replaced by #542


Fixes 'jvm.options' (prerequisite, required file) is unmanaged by module #1093

Pull request acceptance prerequisites:

[x] Signed the CLA (if not already signed)
[x] Rebased/up-to-date with base branch
[x] Tests pass
[x] Updated CHANGELOG.md with patch notes (if necessary)
[x] Updated CONTRIBUTORS (if attribution is requested)

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Need to fix File_line jvm_option test.