Fix missing allocations in memray stats histogram

Signed-off-by: Jingkai Tan<EMAIL_ADDRESS>Fixes #84.
Describe your changes
Cap the known valid range to ensure that anything greater than the second to last bucket will appear in the last bucket.
Testing performed
Ensured that output is as expected (missing mmap allocation shows up)
🕙12:30:27 ❯ memray stats output.bin
📏 Total allocations:
	9

📦 Total memory allocated:
	9.313GB

📊 Histogram of allocation size:
	min: 536.000B
	----------------------------------------
	< 2.792KB  : 4 ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
	< 14.895KB : 1 ▇▇▇▇▇▇▇
	< 79.453KB : 0
	< 423.837KB: 0
	< 2.208MB  : 0
	< 11.778MB : 0
	< 62.827MB : 0
	< 335.145MB: 0
	< 1.746GB  : 0
	<=9.313GB  : 1 ▇▇▇▇▇▇▇
	----------------------------------------
	max: 9.313GB

📂 Allocator type distribution:
	 MALLOC: 5
	 MMAP: 1

🥇 Top 5 largest allocating locations (by size):
	- <module>:../test.py:3 -> 9.313GB
	- _call_with_frames_removed:<frozen importlib._bootstrap>:219 -> 4.381KB
	- _run_tracker:/home/jingkai/Documents/github/memray/memray/src/memray/commands/run.py:60 -> 592.000B
	- _run_code:/usr/lib/python3.8/runpy.py:80 -> 576.000B
	- run_path:/usr/lib/python3.8/runpy.py:265 -> 536.000B

🥇 Top 5 largest allocating locations (by number of allocations):
	- _call_with_frames_removed:<frozen importlib._bootstrap>:219 -> 4
	- <module>:../test.py:3 -> 1
	- run_path:/usr/lib/python3.8/runpy.py:265 -> 1
	- _run_module_code:/usr/lib/python3.8/runpy.py:97 -> 1
	- _run_tracker:/home/jingkai/Documents/github/memray/memray/src/memray/commands/run.py:60 -> 1

Could I get an approval to rerun CI on this please?

I've made a few minor tweaks - rebased this, ran Black, added a changelog entry, and squashed it down to one commit. Looks good to me!
Thanks @xlanor, especially for the new test to try to make sure we don't regress on this again in the future.

Thank you Matt and Pablo for your guidance on this PR. I hope to contribute more to this project in the future during my free time!

I've made a few minor tweaks - rebased this, ran Black, added a changelog entry, and squashed it down to one commit. Looks good to me!
Thanks @xlanor, especially for the new test to try to make sure we don't regress on this again in the future.

Thank you Matt and Pablo for your guidance on this PR. I hope to contribute more to this project in the future during my free time!

Thanks a lot for your great work and patience ❤

I've made a few minor tweaks - rebased this, ran Black, added a changelog entry, and squashed it down to one commit. Looks good to me!

Thanks @xlanor, especially for the new test to try to make sure we don't regress on this again in the future.

Thank you Matt and Pablo for your guidance on this PR. I hope to contribute more to this project in the future during my free time!

Thanks a lot for your great work and patience ❤

No problem! Please feel free to let me know if you're in the London office and want to grab a drink.


Unable to pull image from integrated Harbor via VCH.

This is found on .ova environment, when enabled project level content trust the Harbor keeps returning 412 to VCH.

Found root cause in vic engine, opened issue: https://github.com/vmware/vic/issues/5950

close it as fixed.


fireside:1.0.0

I am submitting

[x] a new package
[ ] an update for a package

Description: This template looks a bit friendlier than a pure black-and-white letter, when the context allows it. I've used it successfully as a cover letter on multiple occasions previously. It has a modern look with a warm white background.

I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Thanks :)


Build oauth2 proxy with go ver 1.19

Description
Changes proposed in this pull request:

To fix golang CVEs we want to build with latest

Related issue(s)

/test all


Adjust curl call

Coverage remained the same at 100.0% when pulling 80aa14dbbf36134323ac85bc7b8f3837ddfec325 on adjust-curl-call into 83f2c5720769174afb4433a2fed7b6dc4934ee3b on main.

Coverage remained the same at 100.0% when pulling 80aa14dbbf36134323ac85bc7b8f3837ddfec325 on adjust-curl-call into 83f2c5720769174afb4433a2fed7b6dc4934ee3b on main.

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/42940

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/49367


explorerExtensibility is not visible if embedMode flag is set to true

Bug
When using the explorerExtensibility API, the extended interface is not shown if the embedMode flag set to true.
var extensibility = [
        {
            predicate: (entity) => { return true; },
            entries: [
                {
                    label: "Say hello",
                    action: (entity) => alert("hello " + entity.name)
                }
            ]
        }
    ];
scene.debugLayer.show({ embedMode: true, explorerExtensibility: extensibility });

https://www.babylonjs-playground.com/#F47J2M

Expected result:

Current result:

Resizing the Inspector window or popping it out does not fix.  Only the embedMode flag and I can't seem to find documentation that would indicate this is the expected behavior.

Thanks!!!


BUG - Transactions table design not implemented completely

As implemented:

As designed:

Missing:

Colored memo
Colored action

I deeply dislike the expand functionality you guys added. It looks weird and works weird. It also feels unnecessary.

@ramijames can you confirm this issue has been addressed?

@donnyquixotic this is done.

@ramijames can you please verify so we can close this issue?


SourceLocation.Equals() can return false for locations with identical hash codes

SourceLocation.GetHashCode() and SourceLocation.Equals() use different properties, a fairly basic no-no.  problems are unlikely unless one of the source locations is corrupt.  nonetheless this quirk should be removed.
in particular GetHashCode() ignores LineIndex and CharacterIndex while Equals() includes them in its comparison.  Equals() is the odd one out because CompareTo() also ignores LineIndex and CharacterIndex.
e.g. the following test succeeds
// Arrange
var sourceLocationA = new SourceLocation(10, 3, 4);
var sourceLocationB = new SourceLocation(10, 45, 8754);

// Act
var compare = sourceLocationA.CompareTo(sourceLocationB);
var equals = sourceLocationA.Equals(sourceLocationB);
var hashCodeA = sourceLocationA.GetHashCode();
var hashCodeB = sourceLocationB.GetHashCode();

// Assert
Assert.Equal(0, compare);
Assert.False(equals);    // !!!
Assert.Equal(hashCodeA, hashCodeB);

original discussion at https://github.com/aspnet/Razor/pull/357#discussion_r28467249

That doesn't seem like a real bug, does it? It's perfectly fine to implement GetHashCode() to return 0 and then to implement Equals() to do a proper comparison. Nothing will break. The only contract is that if two instances are compared and have Equals() be true that their GetHashCode() returns the same value.

I haven't seen anything except Equals() consistency with GetHashCode() but it's possible nothing will break due to that inconsistency here.  now a bit more concerned about Equals() returning false in scenarios where CompareTo() returns 0.

@dougbu Do the Right Thing

Updated subject since SourceLocation.GetHashCode() was fine and SourceLocation.Equals() versus SourceLocation.CompareTo() is only one example of Equals() or GetHashCode() issues.

6384977


Day229

Resolves #472.

Pull Request Test Coverage Report for Build 932

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

Totals

Change from base Build 921:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


OSError: Unable to open file (truncated file: eof = 186683120, sblock->base_addr = 0, stored_eof = 246969744)

While following this tutorial, https://medium.com/deepquestai/train-object-detection-ai-with-6-lines-of-code-6d087063f6ff everything worked fine using their materials however when I trained my own object detector thing using their steps it gave me the above error when I tried using it instead. The full logs I got are in this pastebin: https://pastebin.com/D1MYrSi6
It's probably something dumb I did wrong but any help would be greatly appreciated, thanks.

Hello, there is a chance the pretrained_yolov3.h5 model file partially downloaded. Try to download it again and run your training code.

Hello, there is a chance the pretrained_yolov3.h5 model file partially downloaded. Try to download it again and run your training code.

thanks, that worked!


onvif protocol

I am aware that it is not a bug but it did not make me open a request.
I'm sorry for my english.
have you foreseen the enabling of the onvif protocol?
thanks
Maurizio

No. This is not supported.


add support for updating policy

The IAM Policy resource does not support direct updates. If you want to
modify the policy's Document, you need to call the CreatePolicyVersion
API call and set the new policy version as the policy's
DefaultVersionID. Fairly straightforward, as far as non-updateable
resources go.
The trick with IAM Policies is that you cannot have more than 5 policy
versions associated with a user-managed Policy. This means that if you
attempt to make more than 4 calls to CreatePolicyVersion, you will get
errors back from IAM. So, instead, you must call DeletePolicyVersion
and delete one of the previous policy versions (not the one set as the
default, though).
Similarly, when attempting to delete a Policy, if there is more than a
single PolicyVersion associated with the Policy, you must first delete
all policy versions except the one that is the policy's DefaultVersion
before calling DeletePolicy, which is the only way to delete the
policy version that is the default for a policy.
This patch adds support for the above update and delete code paths,
combining all of the various calls to ListPolicyVersions,
GetPolicyVersion (to get the policy's Document),
CreatePolicyVersion, and DeletePolicyVersion APIs to make an IAM
Policy resource behave in a "normal Kubernetes way" -- in other words,
the Kubernetes user simply changes the desired state of the Policy
(including the Policy's Spec.PolicyDocument field) and the controller
takes care of actuating those changes.
Closes Issue: aws-controllers-k8s/community#1124
Signed-off-by: Jay Pipes<EMAIL_ADDRESS>By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

/approve
LGTM

/lgtm


General-purpose default error type

Most users would probably want to switch between BoxedError and Failure in debug and release respectively. Providing a default error type that has the behavior and cost of BoxedError in debug but Failure in release would help achieve this. There are a few tradeoffs to consider:

Would most users want a release-mode error to immediately print out the error and context, instead of discarding it entirely?

If users really want the error in release mode, they should explicitly ask for it by passing BoxedError instead of the default error type.

Why shouldn't release-mode errors default to panicking?

That would provide better codegen, but at the cost of a behavior change. The default error type should not cause a behavior change.

Why not allow users to switch the default error type using a crate feature?

Mutually-exclusive crate features are terribly badly supported by tooling. They should not be! But it's not a fight worth fighting right now. If the tooling for mutually-exclusive crate features improves then maybe next version.

Fixed by 7a88f17c0b02ce01450d5fe383bc95d01789c5d3


Fixing pytest crash

Pytest made breaking change to drop support for pytest_namespace and only supporting pytest_configure as shown by pytest-dev/pytest#4421.
This is the first step to get CI running again. @TimKam

Thanks! Will you add more to this PR?

@TimKam What is the best style? Create a large PR that gets the tests running completely or several PRs that each fix one problem?

I think one PR to fix all tests would be good. The project is not super-complex so I think it shouldn't be too hard to review such a PR :-) Without the tests passing, it feels a bit like merging in the dark, anyway.

@TimKam Got the Travis CI tests passing. I don't run Windows so I don't think I can fix the appveyor tests.

@TimKam Got all the tests working!!! :smile:


2:4 sparsity + PTQ(int8) model's inference

Are there any runnable demos of using Sparse-QAT/PTQ (2:4) to accelerate inference, such as applying PTQ to a 2:4 sparse LLaMA for inference acceleration? I am curious about the potential speedup ratio this could achieve.
The overall pipeline might be: compressing the Weight matrix using 2:4 sparsity and quantizing it to INT8 format through PTQ/QAT. The Activation matrix should also be quantized to INT8 format through PTQ/QAT. After such processing, the main type of computation would be INT8*INT8.
I would like to know if there is a tutorial document available, as I am a beginner in the field of quantization.
Thx！

Hi @RanchiZhao yes, please see #36, which has a benchmark script and the subclasses. It would be a good idea to add a beginner tutorial as well.

Hi @jcaip Thanks, I saw this before but didn't get a chance to look it over carefully, i'll do it know

oh, another thing, is this in LLM like LLaMA available?
And I wanna do this with Hugging Face's transformers, maybe tough to do.

It should work for LLMs but the speedup characteristics depend on the matmul shapes and depending on what you are trying to do you will see more / less speedups. You will also need the model to be torch.compile traceable, as we use the torchao quantization workflow.

thanks a lot, another interesting thing is that, i want do PEFT(like LoRA) on the sparse&quant model.
once we get the trained LoRA modules, we can add them into original models(bf16 one), and do sparse&quant on it again.
now we get a "sparse&quant aware training" model, we can use it to do inference.
Is this possible?
we should make sure:

we can put LoRA on the sparse&quant model
merging LoRA modules into the bf16 one(instead of int8 one because of the dtype conflict) works

Do you have some reference papers for PEFT + sparsity? I am also interested in that space as well, but have not been following actively.
It's impossible to say for sure without knowing the exact approach, but theoretically I believe some version of this should be possible, although accuracy is likely prohibitive. In terms of implementation though, this is not something directly supported by our APIs. You may be able to hack something together but we do not plan to add this functionality ATM. We may consider it down the line, so for anyone reading who's interested please react / +1 this comment.

no, AFAIK no, I' ll keep finding


Background and panel positions are not updated when tabbing to off-screen node

Describe the Bug
Hi all, big fan of ReactFlow here. I noticed this bug this morning when working on some accessibility features and thought I should flag:
When navigating the graph with the tab button, if the focus shifts to a node that is off screen, the background and panels are not re-rendered in the correct new position. This can be seen on the website examples.
Thank you!
Steps to Reproduce the Bug or Issue

Open https://reactflow.dev/docs/examples/overview/
Zoom in enough for some nodes to be off-screen
Click a node to provide focus
Tab until a node that is off-screen becomes focused
The background and panels will be in the wrong position

Expected behavior
Background and panels should remain stationary throughout.
Screenshots or Videos
https://github.com/wbkd/react-flow/assets/2594635/3535ae30-2943-43b9-971c-d4ee1a1c71cc
Platform

OS: macOS
Browser: Chrome
Version: 117.0.5938.92
reactflow: 11.9.2

Additional context
No response

It's not easy to fix, because it's a native browser behaviour but we will have a look for v12.

A solution could be to set .react-flow__pane to position: fixed. We will investigate.

Also happens when input fields extend off-screen #3598 #3354


[WFLY-13605] fix licenses in full-feature-pack-licenses.xml

Jira: https://issues.redhat.com/browse/WFLY-13605

@jamezp @bstansberry can you please review this one too?


DataGrid: Change default values of TemplateColumn

Description
The TemplateColumn is generally used to add "Action" columns like editing, select and hierarchy.
Currently, the defaults are just the same as for the normal column, which is suboptimal.
In the most common use cases most features are not used or need to be setup first anyway, like with SortBy.
Some of these features like drag and drop add spacing to the column, which is particularly noticeable for select and hierarchy columns.
Furthermore, some features could not been turned off per column, like drag and drop for the hierarchy and select columns.
I also changed the default for 'ShowInFooter' for the SelectColumn since I have seen multiple people complain about the hole row just for the one checkbox.
I would remove that completely to be honest, no other columns support this, and you could always make the header sticky with 'FixedHeader' and have a better experience.
Examples of space savings:

How Has This Been Tested?
visually
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

If this PR gets merged the following default values have changed to false and need to be added to the migration guide:
Template Column

ShowColumnOptions
Resizable
DragAndDropEnabled
Sortable
Filterable

Select Column

DragAndDropEnabled (change inherited from Template column)
ShowInFooter

Hierarchy Column (changes inherited from Template column)

DragAndDropEnabled

@tjscience last year we talked about this change here: https://github.com/MudBlazor/MudBlazor/pull/6049#issuecomment-1452741566
I hope we had the same thing in mind by setting sensible defaults.

@henon @danielchalmers @ScarletKuro ready for review ✌

I will let @tjscience to decide, I'm unsure about the ShowInFooter="false" default as it leaves awkward space in footer, also it's been default for a very long time. I only pretty much agree with Fiterable as TemplateColumn is not attached to any data and filtering is not possible as result confusing people

@ScarletKuro the "awkward space in footer" was there already and is not even dependent on the ShowInFooter setting, as it is introduced though the spacing of the checkboxes.
I wanted to open a separate pr for that.

@dennisrahmen can you write down all breaking change of that PR for the https://github.com/MudBlazor/MudBlazor/issues/8447
in similar format so we could just copy paste it? Thanks.

@ScarletKuro @henon I took the hole block so you can just copy paste.
## MudDataGrid

- Removed `FilterDefinition.GenerateFilterExpression()` replace with `FilterExpressionGenerator.GenerateExpression`
- Removed other old APIs from `FilterDefinition` that was replaced by `IFilterDefinition` API.
- `FilterContext.FilterActions` all properties are marked as required.
- `FooterContext.FooterActions` all properties are marked as required.
- `HeaderContext.SetSelectAllAsync` all properties are marked as required.
- `HeaderContext.IsAllSelected` changed type from `bool` to `bool?`.
- **Column**: replace `IsEditable` with `Editable`
- **TemplateColumn**
  - `ShowColumnOptions` changed default to false
  - `Resizable` changed default to false
  - `DragAndDropEnabled` changed default to false
  - `Sortable` changed default to false
  - `Filterable` changed default to false
- **SelectColumn**
  - `DragAndDropEnabled` changed default to false
  - `ShowInFooter` changed default to false
- **HierarchyColumn**
  - `DragAndDropEnabled` changed default to false

For more details see https://github.com/MudBlazor/MudBlazor/pull/8548, https://github.com/MudBlazor/MudBlazor/pull/8317, https://github.com/MudBlazor/MudBlazor/pull/8892, https://github.com/MudBlazor/MudBlazor/pull/9142

Thanks Dennis


*: remove backend

ref: https://github.com/coreos/etcd-operator/issues/1626

cc/ @hongchaodeng @hasbro17

LGTM


fix(featureflags): return empty object regardless when setting up feature flags

The type of this PR is: Bugfix
Description
If you don't have Unleash set up locally or if there's an error, anything using a feature flag is going to error:

🙏


Add cache in build actions to speed up dependency resolve

Add git cache to speed up the whole build... 80% of the time the action spends time downloading the dependencies for running the test...

This repository hopefully won't build that often. It is not that important to add cache here.


⚠ Multimedia BRN has degraded performance

In 91bbdcb, Multimedia BRN (https://mbrn.in) experienced degraded performance:

HTTP code: 200
Response time: 5077 ms

Resolved: Multimedia BRN performance has improved in cc3a1ea after 15 minutes.


AWS ec2 role credentials

route53-kubernetes had support for ec2rolecreds and would use IAM roles based on metadata.
i.e.
	creds := credentials.NewChainCredentials( 		[]credentials.Provider{ 			&credentials.EnvProvider{}, 			&credentials.SharedCredentialsProvider{}, 			&ec2rolecreds.EC2RoleProvider{Client: metadata}, 		})
Can we do the same thing inside the aws provider?

external-dns already supports the IAM metadata service.

Yes, exactly, external-dns works seemlessly with AWS EC2 Instance Profiles. We use external-dns with kube2iam. Example:

AWS IAM Role: https://github.com/zalando-incubator/kubernetes-on-aws/blob/dev/cluster/senza-definition.yaml#L196
Kubernetes deployment with kube2iam annotation to assign AWS IAM Role to external-dns pods: https://github.com/zalando-incubator/kubernetes-on-aws/blob/dev/cluster/manifests/external-dns/deployment.yaml

Thanks guys


minimize personal debug information in sbmitted debug logs

Preflight Checklist
want to proceed  (y)
Issue Details
After going through a few submitted debug logs by users seeking help, I needed to open this issue.
For debugging purposes it's needed to have relevant debug information.
It would be helpful to protect the users privacy but at the same time get enough information from the application to do debugging.

Is it really needed to expose so much user data for debugging logs?

Can you please minimize the exposure of personal data in debug logs?

Actual Behavior
# getting api credentials
file: 068ebfb138ac0a31e5ef62f23c00a27e35bf71208ddbbfb47a730a4572bd7ccf  applogs.log
"http://XXXXX:ac41b8fc46b8XXXXXXXXXXXXXXXXb17874840c20f87348e1d0145149a@<IP_ADDRESS>:8555"
usernames
# get to know the user
112cb46bc0ff83bfd7bb65e0ac2852461cc4946895d652d1cdf0d30d32fff666  binary_log.log
"app_log.log:[20XXXXXXX] [IPC-RENDERER-info] New version 2.1.13 has been downloaded to /Users/$CLEAR_USERNAME/Library/Application Support/Caches/defi-app-updater/pending/defi-app-2.1.13-mac.zip"
AddToWallet TX_IDs
28b26d7651223491271fb04949219de89203390d25fae74da997a7efc2cca747  binary-log.log
"binary-log.log:202XXXXXXXX [default wallet] AddToWallet d6f9feb84e84a3aeab2177cf2cab8889bd78a1b1add131c8433fb1d065a10867  update"
handleAddPoolLiquidity
# personal preferences in investing?
068ebfb138ac0a31e5ef62f23c00a27e35bf71208ddbbfb47a730a4572bd7ccf  applogs.log
"applogs.log:[2021-XXXXXXXXX] [IPC-RENDERER-info] [handleAddPoolLiquidity] 1. Address dbnQMqPTvpxoEAtDGFZ34DYuCm9TqptJ2scv Amount 0.213"
additional possible needed debug information:
068ebfb138ac0a31e5ef62f23c00a27e35bf71208ddbbfb47a730a4572bd7ccf  applogs.log
"applogs.log:[2XXXXXXX] [IPC-MAIN-info] [Starting Electron App] OS Windows 8.1 - 6.XXXXX"
I did try to anonymize the user data here, in order to protect users privacy.
Expected Behavior
no user data should be included in the debug information log's.
Users should have the possibility to choose with or without personal information.
App log / binary log / app config
(not needed)

Hi @AltCoiFish , thanks for your feedback, will forward it to the team!


Dynamic piping

Is it possible to resolve the problem below with highland.js?
Consider a problem:

split file by lines
write lines to a result file
if a result file exceeds some size create a new result file

For example, if I have a file which weights 4gb and split size is equal 1gb. The result is four files weights 1gb.

Without any additional information, this a little tricky, but there are reasonable ways to do it using only core highland functions if you either bend the rules a little bit or if you know a little more about the input. Assuming neither of those is the case, your best bet would be to handle the file rotation using either a consume handler or custom writable stream.

Hi, I believe I found a solution http://stackoverflow.com/questions/30591188/dynamic-piping-with-frp without any additional libraries

Here's a general corecursive implementation using consume that doesn't require you to create a new fs stream for every buffer. It relies on the guarantee that calling next inside the consume handler never causes a reentry of the handler.
function splitStream(maxSize) {
    return function (s) {
        var i = 0;
        var size = 0;

        var err = null;
        var buf = null;
        var yieldToChild = null;
        var yieldToParent = null;

        return s.consume(function (_err, _buf, push, next) {
            yieldToParent = null;

            if (_buf === _.nil) {
                push(null, _.nil);
            } else {
                yieldToParent = next;
            }

            err = _err;
            buf = _buf;

            if (yieldToChild) {
                yieldToChild();
            } else if (_buf !== _.nil) {
                size = 0;
                push(null, newChild());
            }
        });

        function newChild() {
            return _(function (push, next) {
                yieldToChild = null;

                push(err, buf);

                if (err) {
                    yieldToChild = next;
                } else if (buf !== _.nil) {
                    size += buf.length;
                    if (size >= maxSize) {
                        push(null, _.nil);
                    } else {
                        yieldToChild = next;
                    }
                }

                err = null;
                buf = null;

                if (yieldToParent) {
                    yieldToParent();
                }
            });
        }
    };
}

To use it
_(fs.createReadStream('large.txt'))
    .through(splitStream(1024*1024))
    .scan({i: -1, stream: null}, function (acc, stream) {
        return {
            i: acc.i + 1,
            stream: stream,
        };
    })
    .drop(1)
    .each(function (s) {
        s.stream.pipe(fs.createWriteStream('small_' + s.i + '.txt'));
    });

You should get a bunch of files numbered from 0 that are 1MB each.

I was scribbling up a consume-based solution, but I wasn't managing to use .pipe and was thus having to roll my own back pressure handling, which is always annoying. I like @vqvu's solution, so I'll just leave a couple comments:
@kharandziuk while that works, I personally think it's a bit craftier than it needs to be, and with all the extra state being passed around, there's probably a measurable amount of overhead. Also, by using wrapCallback with fs.WriteStream.write, you're ignoring the destination's highWaterMark and just waiting for each chunk to be flushed before you read any further. I'm not sure if that causes a measurable slowdown, but it certainly doesn't help.
@vqvu at first glance I also suspected that @kharandziuk's solution was creating a new fs stream for every buffer, but it isn't; nextStream() is only invoked when acc.size > MAX_SIZE.
Finally, just for contrast, doing this with logrotate-stream is two lines, avoids reinventing the wheel, performs roughly the same as far as I can surmise, and doesn't even need Highland:
var fs = require('fs');
var logrotate = require('logrotate-stream');

// would use fs.stat to do math to compute 650 instead of hardcoding but you get the idea
var rotator = logrotate({ file: './out.txt', size: '10m', keep: 650 });

fs.createReadStream('walmart.dump').pipe(rotator);

@LewisJEllis Oh, you're right. Oops.
@kharandziuk I pretty much agree with @LewisJEllis. Just use logrotate unless what you want to do isn't write to a bunch of files. Also, now that I look at it more closely, I don't think your solution actually works most of the time.
You overwrite acc.stream and acc.buffer in the scan handler and use parallel(4). Unless the fs write stream is really fast, you're probably writing four copies of every fourth buffer and dropping the rest on the floor. Not to mention if your buffers are really large (> .25 * MAX_SIZE), you'll end up skipping whole files. You really should be creating new objects every time in scan. You can also skip the parallel and just use flatMap, but that's no better than a synchronous write to disk if you're waiting for the writes to complete before doing more work.
Finally, I assume the following is a typo? In your code, parallel and flatMap both consume from the same stream, s, which is not allowed.
s.parallel 4
s.flatMap((x) ->
  debug('flatMap')(x)
  x.stream(x.buffer)
)
.done -> debug('profile')('finish')

@vqvu No, it isn't a typo. It works and it looks like there is no other way to make it works. Consider two samples below
H= require('highland')

readS = H([1...10])

s = readS.map(
  H.add(2)
)
s.parallel(2) # It works
s.each((el)->
  console.log(el)
)

and
H = require('highland')

readS = H([1...10*3])

s = readS.map(
  H.add(2)
)
s.parallel(2).each((el)-> # it doesn't works
  console.log(el)
)

An error in second case TypeError: undefined is not a function

parallel only works on streams of streams, so the second case not working is the correct behavior (though we should probably throw a more descriptive error in this case). The following code will not work as expected.
var s = H([1, 2, 3, 4]).map(H);
s.parallel(2);
s.each(H.log);
// => A bunch of streams instead of [1, 2, 3, 4].

The first case "works" because Highland is lazy and parallel will not consume from s until you want data from it, which you never do because you immediately throw it away. So the parallel ends up doing nothing. This won't work and will throw an error.
var s = H([1, 2, 3, 4]);
s.map(H.add(2));
s.each(H.log);

It is undefined behavior to consume from a stream multiple times without choosing a back-pressure strategy (fork or observe).


Paypal post return on payment success not being received

fixed :) FINALLY!
Commits:
ea71fc8d94e3e3de6a3f9f9caf9202c173f7a527
f355ffdb8d5bdb2b9498811feb611f4c3d14a9a9
05f0be6b4c2ec7f76b33e6f8df8f10c8069e0d05
5a79b3866dc7f32dcc9ce57f82b81c51e5076739
b240a7d9f68cef8f720227b9ef719ef24b84b6fc
d2c963020ea022651e0eed3e629fae10bf0050db


Add and update tests for midstream exception policy bug 5825 - v5

Previous PR: https://github.com/OISF/suricata-verify/pull/1230
Changes:

rebase

Suricata PR: https://github.com/OISF/suricata/pull/9011

There is a PR to fix this, so the label should be requires suricata PR right ?

Fair point XD

Replaced by: https://github.com/OISF/suricata-verify/pull/1247


Update cd2dbrush-class.md

Replaced 'render target' with 'brush' in the CD2DBrush::SetTransform function description

@TylerMSFT
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

@ocucu - Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, we can move forward with your pull request. Thanks!

Hey @ocucu , we weren't making progress on the CLA, so I ported your changes to the private repo and will publish from there.
I'm closing this since the work is done, and thank you for taking the time to do it.
PR#5110 in the private repo is where I'll publish the updates from.
Thank you.


Ability to change window size programmatically

We should be able to change the size of a window programmatically, after it is created. This is useful if the window size is intended to correlate with the size of its current content, or if the window is not fully resizable but can instead be toggled between a developer-defined set of sizes (e.g. for pixel-art games).

It feels to me that doing this 'correctly' requires us to be able to set the frame of the window, that is both its position and its size. Doing this should also require us to query the active displays, so that we can check how much space is available; this would tie in to #1037.


Lack of documentation to reproduce examples from README.md

Still searching for solution for this. I saw this example in README file, but can't find it in documentation and examples.
https://github.com/apexcharts/apexcharts.js#interactivity
Originally posted by @wsjscss in https://github.com/apexcharts/apexcharts.js/issues/1563#issuecomment-626840234

It's a pity


include+ and include- properties

Description
I propose the addition of include+ and include- properties in the configuration options, which respectively add and remove items from the include list. At the moment, only the entire list can be replaced/redefined, which is quite unergonomic and does not compose well with presets, etc.
Bonus
It would be very useful to be able to specify a function to the option that takes an HTML node object as a parameter, and returns a boolean value to specify whether the element should be beautified (or conversely, whether it should be considered inline). Returning "undefined" would fall back to the static include/include+/include- properties in options. This feature would allow you to only inline for example ul.classA > li elements (to use CSS notation). Adding support for such CSS/jQuery notation to the existing include family of properties is an alternative solution.
Input
With this new feature, I expect this configuration:
"inline+": [ "li" ]

to be equivalent to:
"inline": [ "a", "abbr", "area", "audio", "b", "bdi", "bdo", "br", "button", "canvas", "cite", "code", "data", "datalist", "del", "dfn", "em", "embed", "i", "iframe", "img", "input", "ins", "kbd", "keygen", "label", "map", "mark", "math", "meter", "noscript", "object", "output", "progress", "q", "ruby", "s", "samp", "select", "small", "span", "strong", "sub", "sup", "svg", "template", "textarea", "time", "u", "var", "video", "wbr", "text", "acronym", "big", "strike", "tt", "li" ] }

Likewise, I expect this configuration:
"inline-": [ "a" ]

to be equivalent to:
"inline": [ "abbr", "area", "audio", "b", "bdi", "bdo", "br", "button", "canvas", "cite", "code", "data", "datalist", "del", "dfn", "em", "embed", "i", "iframe", "img", "input", "ins", "kbd", "keygen", "label", "map", "mark", "math", "meter", "noscript", "object", "output", "progress", "q", "ruby", "s", "samp", "select", "small", "span", "strong", "sub", "sup", "svg", "template", "textarea", "time", "u", "var", "video", "wbr", "text", "acronym", "big", "strike", "tt" ] }

Thanks @alexreg.  Due to the way CLI options are parsed, this might need to be implemented as:
"inline": [ "+", "li" ]

And
"inline": [ "-", "a" ]

@bitwiseman Sure. I mean, that's slightly less intuitive, but if it makes the implementation a lot easier, then sounds fair. Does the bonus feature (in either form) sound doable to you too?

@alexreg
Re Bonus feature:
It isn't possible, but it definitely won't be implemented as part if this feature.
Also, to be clear, it is unlikely I'll have time to implement it - it would need someone else to take ownership of it.
Please open a new issue and we can discuss it there.

Implementation would probably go in these two methods:

https://github.com/beautify-web/js-beautify/blob/98594300ce7f012f0f0f0e232b111292cdffa7f7/js/src/core/options.js#L76-L87
https://github.com/beautify-web/js-beautify/blob/98594300ce7f012f0f0f0e232b111292cdffa7f7/python/jsbeautifier/core/options.py#L88-L96

In
If we went with the "inline": [ "+", "li" ] syntax, those methods would need to look at the first element in the array to determine if it was an add or subtract case instead of the default set case.
As an alternative, those methods could look for option named <optionName> and if not found take the default. Then look for   <optionName>-add followed by  <optionName>-rm and process those on top of the current value.  Then return.


test-01-failed and RP wip

@dezhizhang1985 please spid_cie_oidc/relying_party/static and add it in gitignore


mpatibility with SD.Next from VLAD

This is great extension and working very well with A1111, sadly I am getting error when using it with SD.Next Vlads fork from A1111.
20:40:48-409139 ERROR    gradio call: AttributeError
╭────────────────────────────────────────────────────────── Traceback (most recent call last) ───────────────────────────────────────────────────────────╮
│ F:\!AI\StableDiffusion\automatic\modules\call_queue.py:34 in f                                                                                │
│                                                                                │
│    33 │   │   │   try:                                                                                │
│ ❱  34 │   │   │   │   res = func(*args, **kwargs)                                                                                │
│    35 │   │   │   │   progress.record_results(id_task, res)                                                                                │
│                                                                                │
│ F:\!AI\StableDiffusion\automatic\modules\txt2img.py:56 in txt2img                                                                                │
│                                                                                │
│   55 │   if processed is None:                                                                                │
│ ❱ 56 │   │   processed = processing.process_images(p)                                                                                │
│   57 │   p.close()                                                                                │
│                                                                                │
│ F:\!AI\StableDiffusion\automatic\extensions\sd-webui-prompt-history\lib_history\image_process_hijacker.py:25 in process_images                         │
│                                                                                │
│   24 │   # add result to history                                                                                │
│ ❱ 25 │   global_state.add_config( uuid.uuid4().hex, res.prompt[:64], shared.opts.sd_model_che                                                          │
│   26 │   return res                                                                                │
│                                                                                │
│ F:\!AI\StableDiffusion\automatic\extensions\sd-webui-prompt-history\scripts\prompt_history_script.py:76 in add_config                                  │
│                                                                                │
│    75 │   │   img = img.resize((new_width, new_height), Image.LANCZOS)                                                                                │
│ ❱  76 │   │   images.save_image_with_geninfo(img, None, os.path.join(global_state.history_path                                                         │
│    77 │   else:                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
AttributeError: module 'modules.images' has no attribute 'save_image_with_geninfo'

please add support for vlads SD.Next: https://github.com/vladmandic/automatic

As of here: vladmantic automatic_SD.NEW issue and comment about this

you have not posted actual trace of the error, only noted it in a headline.
function modules.images.save_image_with_geninfo was obsoleted a long time ago and its not referenced anywhere.
which means you have an extension that is trying to use it. well, that function was always internal-only and no extension should use it. if extension wants to use a correct method, it should rely on modules.images.save_image.
i suggest to find which extension is doing this (you'll see it in console log showing actual error) and report to extension owner.

Where all extension references are pointing to sd-webui-prompt-history
...if that is of any help (:

@GraspGG  thanks for the information

the fix is in this commit: https://github.com/namkazt/sd-webui-prompt-history/commit/b980c5c522abe891aea911aa5c6bab963f5a0c91
please update and test again as i;m not using vlad version.

feel free to open an issue if it still persist

@GraspGG thanks for the information

@namkazt you're welcome
Thanks for the fix!! (:

the fix is in this commit: b980c5c
please update and test again as i;m not using vlad version.

Updated - Enabled - Tested:

No more errors after image generation - check
Prompt has been saved and is shown/listed on the "Prompt History" tab afterwards- check
On SD.NEXT/A1111-"Prompt History" tab there are tiny little graphic issues - but well, i couldn't care less - that whole project frontend is kinda new/different. So i guess noone can even say what is the reason for those little misalignments (:

If you would like a screenshot showing the "Prompt History" tab, let me know - i would have placed it right here, hidden below a "spoiler" but couldn't find one. Placing a screenshot here, big and omnipresent, would make that topic multiple times bigger than it is ^^)
Thanks again,
for the extension itself and for the quick fix!
Take care


Added clang-tidy for C, too.

A limited number of clang-tidy checks can be used with C, too. I pretty much
copied and refactored the C++ clang-tidy linter, and added some documentation
about C-compatible checks.

Cool, now you can add some Vader tests.

I added a Vader test for this by copying the C++ one, and I linked the C++ documentation for the build directory options to the C file.


Test and support Python 3

During development, we ran against Python 2.7 only. I am fairly certain we are cross-version compatible but we should enable Python 3.3 in Travis just to be certain.

Doesn't work on python 3.4
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-f137ea1814a5> in <module>()
----> 1 import sublime_info

sublime-info/sublime_info/__init__.py in <module>()
      1 # Load in local modules for extension
----> 2 from sublime_info import SublimeInfo
      3 from errors import *
      4
      5 # Define sugar methods

ImportError: cannot import name 'SublimeInfo'

after resolving the above error by using absolute imports, I am getting:
sublime-info/sublime_info/SublimeInfo.py in <module>()
      3 import re
      4 import subprocess
----> 5 from shutilwhich import which
      6 from errors import STNotResolvedError, STBadLocationError
      7

ImportError: cannot import name 'which'

Probably ought to wrap the imports with a try/except for backwards compatibility
try:
  from shutil import which
except ImportError:
  from shutilwhich import which

Would you be interested in opening a PR to fix up the one-offs?

This has been resolved via @adambullmer's work in #5 and released in 0.2.0 :tada:

I think your sublime_harness needs an update to to it's requirements.txt to bump the version of it's dependency of this repo

Ah, yea. There's probably a cascade of changes to be done in the Sublime Text tests framework. I'm not sure how much time I want to invest in that since it's mostly dusty and I wasn't too satisfied with the workflow =/
Are you looking at using that?

Yeah, That's how I landed on this bug. Fortunately, at my package level I can override dependency versions. I'm testing now to see if there are any other issues with it. Might join you on jumping ship if this proves too difficult.

Yea, if it is actually working, then I will be surprised. I remember it being rage inducing by the time I finished my work.
randy3k wrote another package and took notes on the alternatives:
https://github.com/randy3k/UnitTesting
In any case, let me know what happens =). If it's effed, then I should be responsible and put up deprecation notices.

So as far as I can tell, the harness works. However, I'm trying to run this through tox and it seems like a file isn't being written where we expect it to, so the test never completes. This is happening on the harness.run() command. If you've got any lead given this issue, I'd be more than happy to dive a little deeper. Otherwise I think I've explored all I can on this project.

Yea, I am not looking forward to debugging that mess -- it was choc full of race conditions and debugging visual components in a non-visual environment. Prob going to deprecate it =(

Sorry for the slow follow up on this. Before I deprecate sublime-plugin-tests, I want to explore to rest of the landscape (still not too familiar with randy3k's version). I will take a look at everything by the end of next weekend.

Finally got around to exploring UnitTesting. I think it has enough overlap with sublime-plugin-tests and is much further along (e.g. OS X and Windows support) that we can deprecate:
https://github.com/twolfson/sublime-plugin-tests
https://github.com/twolfson/sublime-plugin-tests-base
https://github.com/twolfson/sublime-harness

Alright, I have posted a deprecation notice on each of the repos. Thanks for the push to close out this issue on this repo though =)


Getting seq2seq to operate reproducibly

Hi,
I'm trying to use this patch with Tensorflow 2.0, but the learning is still non-deterministic. I guess it is due to XLA optimization. How can I disable XLA?
Bests,

Hi @duncanriach,
Any update on this issue? could you confirm the non-deterministim?

Hey @atebbifakhr, Sorry, I have not gotten to this yet. Will do as soon as I can and get back to you.

Hi @atebbifakhr, I looked into this more deeply. Removing tf.nn.sparse_softmax_cross_entropy_with_logits from the loss function only makes the gradients reproducible for the first step. They still go non-deterministic on the second step. The trainable variables actually go non-deterministic on the first step (somehow) regardless of whether tf.nn.sparse_softmax_cross_entropy_with_logits is in the loss function.
The fact that the gradients are deterministic for the first step but the trainable variables are not suggests that non-determinism is being introduced in the gradient update step. I hope to continue investigating soon.

Hi @atebbifakhr,
After further investigation, there seems to be at least three sources of non-determinism in this system.

Confirmed that back-prop of tf.nn.sparse_softmax_cross_entropy_with_logits does inject non-determinism.
Discovered that tf.keras.optimizers.Optimizer::apply_gradients seems to inject non-determinism when it reduces gradients across the batch.
Discovered that the “inputters”, which do some kind of mapping through a (trainable?) word embedding, are injecting non-determinism by making the samples applied to the model non-reproducible after the first step.

There is a lot more work to do on this issue, but I wanted to give you an interim update.
I've also added your name to the credits section of this repo in recognition of your effort in enabling me to reproduce the problems you've been seeing.

I updated the previous comment based on some more discoveries.


Add Icon to Change Token Network & Add Signing of Messages

Currently its not evident on how to change network ( mainnet / devnet or any other custom networks) + testnet should be deleted by default (since it was replaced with devnet).
Solution : Add icon in the right upper menu, when clicked it shows all networks you have saved (reads from manage networks)

Adding signing of messages within Ark Desktop - currently its only possible through ARK CLI ( https://github.com/ArkEcosystem/ark-client/blob/master/index.js#L628 )

true that, can you put into 2 separate issues, to better track them down

@fix not needed because both issues are solved already :laughing:

@fix the ninjas are taking over :)

@zillionn but that ninjas are awesome ninjas :D

🥋


Storing and applying last known vertical scroll

Change request for the issue specified in https://github.com/phuoc-ng/html-dom/issues/137
Ability to store vertical scroll position in a variable on every location change.
Then applying for that scroll position whenever User returns to index route from a post route.

That looks good. Thanks @surajhell88

@surajhell88 The PR is merged and deployed. But the live site doesn't work as expectation.
Will need to revisit it.

live site

@surajhell88 The PR is merged and deployed. But the live site doesn't work as expectation.
Will need to revisit it.

@phuoc-ng Hey I am so sorry, I just sort of tested it on chrome and brave, it works fine on them. There is some issue with firefox I sort of tested it now. I will work towards solving that and push in another PR. Also if you found the issue on Chrome/Brave too, do let me know.

Thank @surajhell88.
My expected behavior is that:

Access the home page, scroll to given post
Click on post, and then click on the header to go to the home page
It should scroll to the last post position

Is this correct?

Oops, I just checked it on the back button given in the browser. Never checked it when on click of the header. I will work on this now as well as the firefox issue as well.


Adding support for Wordpress Coding Standards

Is there a way to add support for https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards in this current implementation. I tried installing and adding a custom route to the XML file, but CodeSniffer fails. "WordPress-Core" coding standard is not installed. The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz and Zend is the error I get.

Hi! I'll try to check it tonight. Thank you for feedback!

Hello
Could you please try the following?

Add phpcs and wpcs to your composer.json

composer require squizlabs/php_codesniffer
composer require wp-coding-standards/wpcs

Modify the phpcs section in your .php-censor.yml:

test:
    php_code_sniffer:
	....
        standard: "WordPress-Core"
	....

It should work. The path to ruleset will be automaticaly set by composer after install/update (see composer.json).

Update:

The path to ruleset will be automaticaly set by composer after install/update (see composer.json).

It doesn't work if you use wpcs as dependency so:
3. Update composer.json with the following:
"scripts": {     "post-install-cmd": "\"vendor/bin/phpcs\" --config-set installed_paths ../../../vendor/wp-coding-standards/wpcs",     "post-update-cmd" : "\"vendor/bin/phpcs\" --config-set installed_paths ../../../vendor/wp-coding-standards/wpcs" }

@ValerioOnGithub Thx!

@ValerioOnGithub @corpsee Thanks for the quick replies. I'll give this a tweak and see if it works.

This works great! Thanks for the help


VM list with blank IDs in Sunstone

Description
When I return to the list of VMs from a Virtual Network, it appears without IDs.
To Reproduce

Login to Sunstone.
Go to "Virtual Networks" from Dashboard.
Select one of the virtual network and click.
Click on "VMs" in Instances.
VM list with blank IDs will be displayed.
Click the VM on this state, the information of ID:0 will be displayed.

Expected behavior
Habitual behavior.
Details

Affected Component: Sunstone
Version: 5.12 and development

Additional context

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

PRs to merge:

one: https://github.com/OpenNebula/one-ee/pull/1810
doc: https://github.com/OpenNebula/docs/pull/2172


Add storage account example and virtual network example

Storage Account example is a command line tool going through the various actions.
The virtual network example was created by Nava Levy, but included here since she didn't have time to generate the pull request.

Can one of the admins verify this patch?

Hi @jmspring, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

@azuresdkci add to whitelist

Note - this patch is part of the CRP Java SDK hackfest that took place the
last three days.
On Thu, Aug 20, 2015 at 4:38 PM, Jianghao Lu<EMAIL_ADDRESS>wrote:

@azuresdkci https://github.com/azuresdkci add to whitelist
—
Reply to this email directly or view it on GitHub
https://github.com/Azure/azure-sdk-for-java/pull/502#issuecomment-133211715
.

@azuresdkci retest this please

I'll reissue a PR with the broken tests (that this PR adds) fixed.


Automated testing

As can be seen in the commits the automated testing was broken in 2,5 places.

The pipe operator for the union of dictionaries was only added in Python 3.9 which is why the test failed for Python 3.8
Not as initially assumed the Geometry3D but the transformations package has an outdated install method which is why it broke the setup to run tox on the macOS os. Since it says in the Notes that transformations is no longer developed I decided to switch this package to Transforms3D but we might simply want to use something with more features like blender.mathutils or scipy.spatial.transforms in the future.
In addition to those two changes, I reduced the tox definitions and cleaned up some environment descriptions to make them easier to change and follow in the future.

So cool to see that green tick 🎉🚀

The pipe operator for the union of dictionaries was only added in Python 3.9 which is why the test failed for Python 3.8

Nice catch!

Not as initially assumed the Geometry3D but the transformations package has an outdated install method which is why it broke the setup to run tox on the macOS os. Since it says in the Notes that transformations is no longer developed I decided to switch this package to Transforms3D but we might simply want to use something with more features like blender.mathutils or scipy.spatial.transforms in the future.

Ah interesting, so it was the installation of transformations that was failing in a super cryptic way. Nice!
Transforms3D seems to be a good alternative for composing and decomposing affine transforms. Actually, I found a way to get rid of it completely for now 🙈. Can push here or as a follow up, as you prefer.
One thing to consider is that transformations is used also in the multi-view notebook, where it's use however can easily be replaced. This didn't show up in the tests because the notebooks are not being tested currently. As you might have seen, we already have a small test dataset in the repository, however I remember there were some problems when testing with tox, namely that the filepath wasn't found (it's currently a relative path from sample_data.py.

In addition to those two changes, I reduced the tox definitions and cleaned up some environment descriptions to make them easier to change and follow in the future.

Does this mean we wouldn't be testing different python versions and OSes? Given the problems we had it might be useful to have these, what do you think?

Does this mean we wouldn't be testing different python versions and OSes? Given the problems we had it might be useful to have these, what do you think?

My understanding is that we are testing all versions and OSes because we spawn 9 different containers in the workflow (where we define the matrix) and start tox and run the tests in all of them as we did before. There might be some features in tox that require us to define the matrix in the tox.ini as well but currently, it just doubles the configuration, I think.

Transforms3D seems to be a good alternative for composing and decomposing affine transforms. Actually, I found a way to get rid of it completely for now 🙈. Can push here or as a follow up, as you prefer.

You can push however you prefer. But I think the immediate solution here is not as important as thinking about a long term solution. If we don't want to write all functions for geometric manipulations (which I believe we will need quite extensively) ourselves we should find a well-maintained package to use everywhere.

One thing to consider is that transformations is used also in the multi-view notebook, where it's use however can easily be replaced. This didn't show up in the tests because the notebooks are not being tested currently. As you might have seen, we already have a small test dataset in the repository, however I remember there were some problems when testing with tox, namely that the filepath wasn't found (it's currently a relative path from sample_data.py.

Yes, I saw the dataset and I think it's a good temporary solution (or maybe base solution; We might also want to be able to run some tests offline without caching data first.) since I want to focus on other things for now. For the notebook we should also replace the transformations with the replacement yes.

My understanding is that we are testing all versions and OSes because we spawn 9 different containers in the workflow (where we define the matrix) and start tox and run the tests in all of them as we did before. There might be some features in tox that require us to define the matrix in the tox.ini as well but currently, it just doubles the configuration, I think.

Yes you're right, perfect.

You can push however you prefer. But I think the immediate solution here is not as important as thinking about a long term solution. If we don't want to write all functions for geometric manipulations (which I believe we will need quite extensively) ourselves we should find a well-maintained package to use everywhere.

Removed the dependencies and replaced the usage in the notebook for now. We might get away by simply concatenating affine transforms for quite a bit, but I agree that probably we'll need a library for further functionality at some point (which like this we can decide about then).

Yes, I saw the dataset and I think it's a good temporary solution (or maybe base solution; We might also want to be able to run some tests offline without caching data first.) since I want to focus on other things for now. For the notebook we should also replace the transformations with the replacement yes.

I added testing for the notebook using the tiny dataset.


Superset with Athena connection

Hi,
Facing issue in connection with Athena
using PyAthena
created the connection string
awsathena+rest://{aws_access_key_id}:{aws_secret_access_key}@athena.{region_name}.amazonaws.com/{schema_name}?s3_staging_dir={s3_staging_dir}
Now the problem is {schema_name} parameter is not working
Ii am not able to connect to a particular DB or scheme it's always connected to a default data source from my Athena
Kindly suggest

Hi kapilgarg83  - can you please explain how you made the connection work? I tried, but I always face an error. I used PyAthena as well.

Hi, I can confirm somehow similar behavior. There are multiple datasources configured in our AWS Athena, up on configuring database in superset in a form of:
awsathena+rest://key:secret@athena.us-east-1.amazonaws.com:443/schema?s3_staging_dir=bucket&work_group=some_group
I can successfully establish (test) connection, however when I'm trying to create dataset - Superset showing schemas only from first Athena datasource (AWS Glue) so far I wasn't able to make it choose somehow other Athena datasource

@kapilgarg83, are you able to solve the problem? facing the same issue here :(

@eschutho @betodealmeida I can't remember the details, but I know there were some changes/ideas around the Athena connector after this was open. Is this still an issue in your minds?
Curious also if anyone else on the thread is able to repro this in 2.0.1 or on master?

Same issue here!

@arnoroos-dataroots what version are you running?
Anyone able to verify this issue on Superset 3.x?

Same Issue:
When test the connection it show "Connection looks good!". When click Connect Button it through error: "An error occurred while creating databases: Database could not be created."

@irfanmajeed on what version of Superset?

@irfanmajeed on what version of Superset?

Version: 4.0.0


f5-tts_finetune-gradio: Segmentation fault when starting 42h audio "Transcribe Data"

Checks

[X] This template is only for bug reports, usage problems go with 'Help Wanted'.
[X] I have thoroughly reviewed the project documentation but couldn't find information to solve my problem.
[X] I have searched for existing issues, including closed ones, and couldn't find a solution.
[X] I confirm that I am using English to submit this report in order to facilitate communication.

Environment Details
Ubuntu 22.04.4 LTS (Docker pytorch/pytorch:2.4.0-cuda12.4-cudnn9-devel), RTX 4090, Python 3.10.15, torch 2.3.0+cu121
Note: I tried with cu121 because of https://github.com/SWivid/F5-TTS/issues/209, but torch==2.3.0+cu118 produces the same error.
Steps to Reproduce

Create conda env
Start f5-tts_finetune-gradio
Upload 42h mp3 file (16.0 kHz, mono, 439M)
"Click Transcribe Data"

✔ Expected Behavior
Audio transcribed
❌ Actual Behavior
Fatal Python error: Segmentation fault
With PYTHONFAULTHANDLER=1 f5-tts_finetune-gradio:
Thread 0x00007c561d4fa640 (most recent call first):
  File "/opt/conda/envs/f5-tts/lib/python3.10/threading.py", line 320 in wait
  File "/opt/conda/envs/f5-tts/lib/python3.10/queue.py", line 171 in get
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 932 in run
  File "/opt/conda/envs/f5-tts/lib/python3.10/threading.py", line 1016 in _bootstrap_inner
  File "/opt/conda/envs/f5-tts/lib/python3.10/threading.py", line 973 in _bootstrap

  Current thread 0x00007c561ccf9640 (most recent call first):
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/soxr/__init__.py", line 206 in resample
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/numpy/lib/shape_base.py", line 379 in apply_along_axis
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/librosa/core/audio.py", line 669 in resample
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/librosa/core/audio.py", line 193 in load
  File "/root/F5-TTS/src/f5_tts/train/finetune_gradio.py", line 689 in transcribe_all
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/gradio/utils.py", line 865 in wrapper
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 943 in run
  File "/opt/conda/envs/f5-tts/lib/python3.10/threading.py", line 1016 in _bootstrap_inner
  File "/opt/conda/envs/f5-tts/lib/python3.10/threading.py", line 973 in _bootstrap

Thread 0x00007c561f7fe640 (most recent call first):
  File "/opt/conda/envs/f5-tts/lib/python3.10/selectors.py", line 469 in select
  File "/opt/conda/envs/f5-tts/lib/python3.10/asyncio/base_events.py", line 1871 in _run_once
  File "/opt/conda/envs/f5-tts/lib/python3.10/asyncio/base_events.py", line 603 in run_forever
  File "/opt/conda/envs/f5-tts/lib/python3.10/asyncio/base_events.py", line 636 in run_until_complete
  File "/opt/conda/envs/f5-tts/lib/python3.10/asyncio/runners.py", line 44 in run
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/uvicorn/server.py", line 65 in run
  File "/opt/conda/envs/f5-tts/lib/python3.10/threading.py", line 953 in run
  File "/opt/conda/envs/f5-tts/lib/python3.10/threading.py", line 1016 in _bootstrap_inner
  File "/opt/conda/envs/f5-tts/lib/python3.10/threading.py", line 973 in _bootstrap

Thread 0x00007c5853fb4740 (most recent call first):
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/gradio/blocks.py", line 2832 in block_thread
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/gradio/blocks.py", line 2737 in launch
  File "/root/F5-TTS/src/f5_tts/train/finetune_gradio.py", line 1842 in main
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/click/core.py", line 783 in invoke
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/click/core.py", line 1434 in invoke
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/click/core.py", line 1078 in main
  File "/opt/conda/envs/f5-tts/lib/python3.10/site-packages/click/core.py", line 1157 in __call__
  File "/opt/conda/envs/f5-tts/bin/f5-tts_finetune-gradio", line 8 in <module>

It looks like the error comes from the following line in finetune_gradio.py:
audio, _ = librosa.load(file_audio, sr=24000, mono=True)

So I will try with the audio in 24kHz instead of 16).

It didn't crash anymore, but used too much memory. I will use split audio instead.


Suitcase Reset App Server should have confirmation

Software and hardware versions
Suitcase 2.0.3
Problem description
If a user is unfamiliar with the "Reset" button in Suitcase, or pushes it by mistake, there isn't a warning that it is about to delete all your data on the server. There should be an "Are you sure" dialog that briefly explains what is about to happen.

Closed by: https://github.com/odk-x/suitcase/pull/47


UNet Example

I'd love to contribute an example of using UNet for image segmentation - would this be useful?

Sure thing!

This is what I've got so far: https://gist.github.com/tanmayb123/c3106c64ee8b9e07b729465b0744477b
But I get this error:
Stack dump:
0.	Program arguments: /root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift -frontend -interpret DeepUNet.swift -disable-objc-interop -color-diagnostics -module-name DeepUNet
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x44d21cf]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x44d0320]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x44d24d2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f166318d390]
[0x7f16405d5553]
[0x7f16405cf04d]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0xcb369e]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0xcb7542]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x51b50f]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x4efe14]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x4eb366]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x49229e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f164edbd830]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x4900d9]
Segmentation fault

Did I do something wrong?

#tfop are not differentiable and will lead to undefined behavior. You can define your differentiable version of Tensor.concatenated(...) locally in your file using the differentiableFunction(from:) operator or the @differentiable(vjp: ...) attribute. I'll add the derivative for you in stdlib tomorrow.

Ah I see. I'll try again tomorrow.

In the meantime, I've created a PR for the UpSampling2D layer to be added to your DeepLearning repo: https://github.com/rxwei/DeepLearning/pull/6

Excellent!

@rxwei There's one more issue I just came across.
This code: https://gist.github.com/tanmayb123/4c140c011fe1c262d22968172a3475ad crashes with this stack dump:
Stack dump:
0.	Program arguments: /root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift -frontend -interpret abc.swift -disable-objc-interop -color-diagnostics -module-name abc
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x44cf04f]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x44cd1a0]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x44cf352]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f298b8ab390]
[0x7f2968cf9483]
[0x7f2968cf504b]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0xcb3bbe]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0xcb7a62]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x51b50f]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x4efe14]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x4eb366]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x49229e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f29774db830]
/root/ss/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/bin/swift[0x4900d9]
Segmentation fault

Notice that in the code I linked, in the applied(to:) function, I don't use the up1_c2 layer. However, if I comment lines 63 and 54 (where I declare and initialize the up1_c2 layer), the code works just fine.
This stumped me for some time yesterday, any idea where this may be coming from?

Could you help file a bug on bugs.swift.org with the reproducer?

We'd love for someone to open a PR with a working UNet example! :-)

Can I take this PR up ?

@saeta @dan-zheng I've finished the UNet model, but I'm unable to find an appropriate dataset for the implementation, for example the dataset used in the paper i.e website has images in tiff format and I'm having some issues loading it, which I'll be putting up on the Google groups, but I'd love your suggestions for the dataset.

@saeta @dan-zheng I've finished the UNet model, but I'm unable to find an appropriate dataset for the implementation, for example the dataset used in the paper i.e website has images in tiff format and I'm having some issues loading it, which I'll be putting up on the Google groups, but I'd love your suggestions for alternate datasets.

oxford pets dataset has segmentation masks:  https://www.robots.ox.ac.uk/~vgg/data/pets/

I've got a U-Net based generator for my pix2pix implementation. I would be happy to contribute it to this project in case you think that implementation is good
https://github.com/s1ddok/pix2pix-s4tf

I'm almost done with the UNet example code with the EM Segmentation dataset as implemented in the paper. Sorry about the delay, I was in the midst of my exams and couldn't devote much time. Should be sending a PR in day.

I'm sorry again about the delay again. Will pe posting the link to my code soon for comments before I officially open a PR.


WebAR on Samsung S24+ Exynos. Black Screen but AR works

Description
Same problem as with the issue #3495 but with the new Samsung S24.
When I start a WebAR session features like hit testing still work, but there is no camera view.
Live Demo
Screenshot:
Link: https://immersive-web.github.io/webxr-samples/hit-test.html
Version

model-viewer: v3.4.0

Browser Affected

[ ] Chrome, version: 120.0.6099.231
[ ] Chrome Canary, version: 123.0.6263.0
[ ] Samsung Internet, version: <IP_ADDRESS>

OS

[ ] Android

AR

[ ] WebXR

Thanks, but does Samsung have someplace you can file bugs or feedback? There's nothing we can do about their browser bugs. Also, you're not even referencing anything to do with model-viewer. At least we can fall back to scene viewer.


Distance and Direction WAB widget: Range rings drawn interactivley get drawn to the graphics layer incorrect

Widget
Distance and Direction WAB widget
Version of widget
2.1 & 2.2
Bug or Enhancement
When you draw a range ring interactively it creates a geodesic circle, it then looks like this circle gets the geodesic function applied again when added to the graphics layer
Repo Steps or Enhancement details
Use the interactive option on the Rings tab to draw a circle that is high or low in latitude (near a pole). Looks ok when drawn but when double clicked and drawn to the map it looks like the geodesic circle gets corrupted.

@kgonzago
When drawing the circles from the clicked locations the radius of the circle was being determined using the geometry engine distance function which returns a planar distance instead of a geodesic length. I changed the function to use geodesicLength instead which seems to have fixed the issue.
Please can you do an independent check

@adgiles will do.

verified.


ADD failed proxy error handler

I'm trying to integrate this into a small service within a cluster I run and I've found that a failed proxy requests by default result in an empty server response with no error message server side. I've found that this comes from one somewhat unsafe ? unwrap in the internal proxy.
I've slightly modified this so that there is now a handle_error on the HttpHandler trait that takes the error from hyper and returns a response. By default I have it returning a 502 Bad Gateway.

Thanks for the PR! I have requested a few small changes.

No problem, have responded to them. Appologies for the bad rust, I only learned it yesterday.


Add sensu_event type

Pull Request Checklist

Description

Related Issue

Part of #901  .
Motivation and Context

Allow sensu-go events to be resolved and deleted.
How Has This Been Tested?

Beaker acceptance tests and vagrant instance.  Travis-ci tests will fail until #916 is merged.
General

[ ] Tests pass - bundle exec rake validate lint spec

@treydock still getting errors after #916 was merged

Having issues with acceptance tests

I thought that would be fixed by latest commit but it wasn't, will investigate.  Thus far I haven't been able to reproduce locally using beaker and centos-7 set.  The testing of events is rather tricky since events can't be created for the purpose of testing, at least not without first creating some checks and having them run and then forcing one to fail, but I fear all that effort would add a lot of time to the acceptance tests which some are already timing out.

Agreed that we should not do that extra effort which will lead to the tests timing out.

Issue resolved by forcing agent node to have specific entity ID and not relying on local hostname lookup as seems some containers kept getting localhost.localdomain and this collided with backend container.


tower-abci: bump<EMAIL_ADDRESS>

Looks good to me, can you bump the cargo version as well please

Thanks!


bump cf_exporter from v1.0.0 to v1.0.1

This PR bump cf_exporter from v1.0.0 to v1.0.1, which includes:

concurrent requests are handled correctly

(bosh-prometheus/cf_exporter#82)

connexions to api are correctly closed

(bosh-prometheus/cf_exporter#81)

Note: new blob has been uploaded

I planned to do this after merge. I feared that the blob would be actually delete on S3, maybe I was overthinking
I can delete it right now if you tell me that it's ok

ah okay, yeah you are maybe right.


Enhancement: Allow selectable number of channels

Looks like the context always has two channels.
It would be nice to be able to select the number of channels.  I guess this also means making the waveform display include a display for each channel.

I will work on this issue along with #15. The current modular structure of waveform renderer makes this easy to do.

Closing with a57b9c52c2730cc17b2b9cac83a8fb92c28c326f.


CopyToOutput deleted when adding a new file

Describe the bug
If I have a fsproj like so:
  <ItemGroup>
    <Content Include="customers.json" CopyToOutputDirectory="Always" />
    <Compile Include="DataStore.fs" />
    <Compile Include="RestrictionOperators.fs" />
    <Compile Include="ProjectionOperators.fs" />
    <Compile Include="PartitioningOperators.fs" />
    <Compile Include="OrderingOperators.fs" />
    <Compile Include="Program.fs" />
  </ItemGroup>

If I choose Add File Above, and add a new file I get:
  <ItemGroup>
    <Content Include="customers.json" />
    <Compile Include="DataStore.fs" />
    <Compile Include="RestrictionOperators.fs" />
    <Compile Include="ProjectionOperators.fs" />
    <Compile Include="PartitioningOperators.fs" />
    <Compile Include="OrderingOperators.fs" />
    <Compile Include="NewFile.fs" />
    <Compile Include="Program.fs" />
  </ItemGroup>

To Reproduce
Steps to reproduce the behaviour:

Go to Solution Explorer
Click on a file
Click add new file above
View fsproj
See error

Expected behaviour
For it to add an entry of the new file and not to delete other attributes
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: Mac OS
Ionide version: 4.12.0
VSCode version: 1.46.0
dotnet SDK version: 3.100.0
mono / .Net Framework version: N/A

There are more things which get deleted. The following screenshot shows what gets deleted from my function app fsproj:

Should be fixed with 5.0


Type param in SelectProps is not used

Provide a general summary of the issue here
The type param T is used in CollectionBase<T> to define the children and items props.
However they are both omitted by SelectProp.
https://github.com/adobe/react-spectrum/blob/main/packages/react-aria-components/src/Select.tsx#L65
So the type param is just noise and doing nothing.
🤔 Expected Behavior?
remove it or use it
😯 Current Behavior
doing nothing
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
n/a
Version
rac 1.3.1
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
macOS
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Looks like we don't require it in TagGroup https://github.com/adobe/react-spectrum/blob/32574f874fd8a8b667a409938457819ac33f8e84/packages/react-aria-components/src/TagGroup.tsx#L26
thanks for the issue

@snowystinger
May I work on this issue?

Note that this can considered as a breaking change if we remove the type param

that's a great point, we may need to make a default in order to deprecate it instead

@snowystinger
I understand the concern about removing the type parameter T being a breaking change. Instead of removing the type parameter T, I'm thinking of providing a default value for it.
Would the following change be acceptable?
export interface SelectProps<T extends object = {}> extends Omit<AriaSelectProps<T>, 'children' | 'label' | 'description' | 'errorMessage' | 'validationState' | 'validationBehavior' | 'items'>, RACValidation, RenderProps<SelectRenderProps>, SlotProps {}

function Select<T extends object = {}>(props: SelectProps<T>, ref: ForwardedRef<HTMLDivElement>) {
  // ...
}

I believe that will work, we'll discuss more in review. Thanks!


Version withour json-smart

Hello,
I would like to try my luck, with a new post. Are you planning a version without json-smart? Since the library is abandoned by it's user, one of it's dependencies is really outdated and is causing conflicts in my project.

agree, I think Jackson would be more appropriate.

Hello,
same as @nikolakoco89 , this way one could completely exclude json-smart dependency from pom.
and then we could also think making 'net.minidev.json.*;resolution:=optional' in the build gradle so we are able to choose the Jackson implementation of JsonProvider and MappingProvider?

+1

Hi everyone,
due to unresponsiveness regarding this manner, I've switched to using JSON Pointer.
Cheers

Hello,
same as @nikolakoco89 , this way one could completely exclude json-smart dependency from pom.
and then we could also think making 'net.minidev.json.*;resolution:=optional' in the build gradle so we are able to choose the Jackson implementation of JsonProvider and MappingProvider?

+1 for this solution, it would make easier to use json-path without forcing to depends of json-smart which seems dead and even worst can lead to the jvm to be killed with jdk11

Hello guys,
Not only json-smart is abandoned but it have a critical vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2021-27568.


add redirections

Docs Build status updates of commit c0e806f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Table Showing Field Description by Default in Manager

Describe the bug
Any solution that uses the Manager app or Table widget are showing the field descriptions in the column header by default.

Expected Behavior
Column headers should only show field name by default.
Reproduction Steps & Sample
In QAext or DEVext, deploy the Community Risk Reduction Solution.

Navigate to the Community Risk Manager web experience item page and click View.
In the Requests tab (embedded Manager Instant App), notice the field descriptions are visible by default.
Click the Inventory tab in the top right.
Notice the field descriptions are visible by default in the table widget.

Alternatively try this test app to see the behavior https://solutions.mapsdevext.arcgis.com/apps/instant/manager/index.html?appid=a1188165b1b24090b9d69191c93466ff
Other Relevant Info
No response

@azizaparveen

We have not made any changes related to this.
looks like some enhancements with the JS API FeatureTable widget.

@jmhauck - Could you please check and let us know if any updates to the JS API or in the documentation related to this?

@sumitzarkar it is recently being added to FeatureTable. Now FeatureTable supports showing field description in column headers when descriptions are available, which is enabled by default. they said they also have added a property to visibleElements to control the display of descriptions in the header cell.
We would like to hide the description from header cells.

I am good with hiding it for now, but we should also consider if we want a configurable property in the future as this could be a helpful feature.

cc @sarahmcdonald7

@azizaparveen I noticed last week that the table started picking up the new table configurations from Map Viewer. I think hiding the descriptions makes sense too.
We should honor the other configurations though, like field order and field visibility.

@azizaparveen @jmhauck
We will hide the column description and deliver the code in next code drop


Bug: Parallel transitions always exit on transition in v5.0.0-beta.7

Description
Hi there! I was trying out the latest v5 beta with Reflame's VSCode extension and came cross an issue where parallel states seem to always exit no matter how I specify the transition to try to prevent it. Here's a sandbox reproducing the issue: https://codesandbox.io/s/cranky-dhawan-b16zyc?file=/src/index.js
In my extension, it causes infinite loops due to invoked actors existing prematurely and re-entering and executing side effects.
Expected result
Parallel states should not exit when transitioning within the same state unless reenter is true.
Actual result
Both parallel states end up exiting.
Reproduction
https://codesandbox.io/s/cranky-dhawan-b16zyc?file=/src/index.js
Additional context
No response

Does this behavior differ from v4? We are still hashing out how reenter+parallel should work together

Thanks for the reproduction!
This may be confusing but it's actually expected behavior. The reenter: false flag is only for the state where the transition is specified. Since no transitions are found in the child states for that event, the algorithm exits those states since it now needs to check the parent.
Here is an illustration:

The workaround is to specify the transition on each state, which will give the expected behavior:
const machine = createMachine({
  id: "machine",
  type: "parallel",
  // on: {
  //   transition: {
  //     reenter: false,
  //     // all of these cause both states to exit
  //     // target: ".right.transitioned"
  //     // target: "#machine.right.transitioned"
  //     // target: ["#machine.right.transitioned", "#machine.left"]
  //     target: [".right.transitioned", ".left"]
  //   }
  // },
  states: {
    left: {
      exit: ({ event }) => console.log("exited left due to event", event),
      on: {
        transition: {}
      }
    },
    right: {
      initial: "initial",
      exit: ({ event }) => console.log("exited right due to event", event),
      states: {
        initial: {},
        transitioned: {}
      },
      on: {
        transition: ".transitioned",
        reenter: false
      }
    }
  }
});

https://codesandbox.io/s/mystifying-hugle-jozqgt

@davidkpiano @Andarist appreciate the follow up! The reason I thought this was a bug was because it's a breaking change from how internal transitioned worked in v4.
Take a look at this sandbox: https://codesandbox.io/s/elated-stallman-4liby6?file=/src/index.js
Note that neither of the states exit when specifying a target within the state for a transition specified at a parent.
I'm glad this can be worked around by specifying tighter scoped transitions, but I would much prefer the previous behavior to be preserved if possible.
Part of it is that it'd force me to refactor a ton of transitions to upgrade, but the other part is (as you alluded to) it just doesn't feel intuitive that a transition to the same state should cause it to exit, regardless of where it's specified.
One of things that prompted me to attempt the upgrade was the move to make all transitions internal by default (whereas previously it defaulted to external), which sounded like an awesome improvement to ergonomics since I had to manually specify internal: true in so many transitions before, but this new behavior feels like a step backwards since it's no longer even possible to transition a parallel child state from the parent without causing it to exit.

@davidkpiano @Andarist I gave the beta another shot earlier today and this particular breaking change has caused me the most pain by far.
It's forcing me to rewrite every state node that looks like this in v4:
    status: {
      initial: "initial",
      on: {
        "config.none": {
          actions: assign({
            config: undefined
          }),
          target: "#config.status.none",
          internal: true
        },
        "config.invalid": {
          actions: assign({
            config: undefined
          }),
          target: "#config.status.invalid",
          internal: true
        },
        "config.valid": {
          actions: assign({
            config: (context, event) => event.config
          }),
          target: "#config.status.valid",
          internal: true
        }
      },
      states: {
        initial: {},
        none: {},
        invalid: {},
        valid: {
          initial: "inner",
          states: {
            inner: {
              exit: (context, event) => console.log("exited inner", event)
            }
          }
        }
      }
    }

(sandbox here, note that there's no exited log)
... into monstrosities like this in v5 in order to preserve the previous behavior:
    status: {
      initial: "initial",
      states: {
        initial: {
          on: {
            "config.none": {
              actions: assign({
                config: undefined
              }),
              target: "#config.status.none"
            },
            "config.invalid": {
              actions: assign({
                config: undefined
              }),
              target: "#config.status.invalid"
            },
            "config.valid": {
              actions: assign({
                config: ({ context, event }) => event.config
              }),
              target: "#config.status.valid"
            }
          }
        },
        none: {
          on: {
            "config.none": {
              actions: assign({
                config: undefined
              }),
              target: "#config.status.none"
            },
            "config.invalid": {
              actions: assign({
                config: undefined
              }),
              target: "#config.status.invalid"
            },
            "config.valid": {
              actions: assign({
                config: ({ context, event }) => event.config
              }),
              target: "#config.status.valid"
            }
          }
        },
        invalid: {
          on: {
            "config.none": {
              actions: assign({
                config: undefined
              }),
              target: "#config.status.none"
            },
            "config.invalid": {
              actions: assign({
                config: undefined
              }),
              target: "#config.status.invalid"
            },
            "config.valid": {
              actions: assign({
                config: ({ context, event }) => event.config
              }),
              target: "#config.status.valid"
            }
          }
        },
        valid: {
          on: {
            "config.none": {
              actions: assign({
                config: undefined
              }),
              target: "#config.status.none"
            },
            "config.invalid": {
              actions: assign({
                config: undefined
              }),
              target: "#config.status.invalid"
            }
          },
          initial: "inner",
          states: {
            inner: {
              exit: ({ event }) => console.log("exited inner", event)
            }
          }
        }
      }
    }

(sandbox here. If we use the same structure as v4, inner ends up exiting as can be seen in this sandbox.)
 Maybe I'm missing something?
Putting this migration on pause for now since refactoring every node like this isn't really workable. Keeping my fingers crossed that either there's a workaround or this behavior ends up getting changed before v5 reaches stable. 🙏


Usage error should show there is a --help option

For instance
$ ./scancode
Usage: scancode [OPTIONS] <input> <output_file>

Error: Missing argument "input".None

It would be better if we had something such as:
$ ./scancode
Usage: scancode [OPTIONS] <input> <output_file>
Try 'scancode --help' for help on options and arguments.

Error: Missing argument "input".None

@untitaker I can provide a pull request for this.
Is Try 'scancode --help' for help. a good wording?
Should this be fixed or configurable as a click.help option with a default?

Thanks for volunteering, I think it's fine as default.
On 12 August 2015 19:22:04 CEST, Philippe Ombredanne<EMAIL_ADDRESS>wrote:

@untitaker I can provide a pull request for this.
Is Try 'scancode --help' for help. a good wording?
Should this be fixed or configurable as a click.help option with a
default?

Reply to this email directly or view it on GitHub:
https://github.com/mitsuhiko/click/issues/393#issuecomment-130381456

--
Sent from my phone. Please excuse my brevity.

Fixed by #557

Thanks ++ for fixing this! I am updating to 7.x now.


Fix IPAccessList resource configuration

Description of your changes

Fixes IPAccessList resource and adds an example manifest for it.
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Manually tested using the example manifest provided.

can we please merge this one? I really need to use it @ulucinar

Hi folks,
I checked whether we should make the databaseName of User a reference to Cluster as my interpretation is that you can refer to an existing cluster's name in that parameter but then, why not make it a reference to an AdvancedCluster? Currently, we have no support for generic cross-resource references, thus I chose not to implement cross-resource referencing for the field.
@bitgandtter, is my interpretation correct? Can it be a reference to a Cluster or to an AdvancedCluster?


DWURecyclingAlert Red alert while rendering images and cells...

FeedTableView in sample app with the following FeedItemLayout causes red boxes around images as well as high latency alert from DWURecyclingAlert. Any thoughts on how I can optimize image loading and layout?
https://github.com/diwu/DWURecyclingAlert/blob/master/RecyclingAlert/DWURecyclingAlert/DWURecyclingAlert.m
`        let actorCommentLayout = StackLayout(axis: .horizontal, sublayouts: [
SizeLayout(width: 50, height: 50, config: { imageView in
            imageView.image = UIImage(named: "Avatar\(imageIndex.instance.value)")
        }),
        LabelLayout(text: actorComment, alignment: .centerLeading)
    ])`

Thanks for reporting!
I am not familiar with DWURecyclingAlert but based on the README it triggers for two reasons:

Displays non-recycled UIView, CALayer and UIImage objects with bold red bolders.
Displays the time it takes to complete each time sensitive API calls, in milliseconds.

LayoutKit does not reuse views by default so my guess is that is causing the alert (and not necessarily that it is slow). 8ms doesn't seem that bad since the README also says this:

Your code usually has less than ten milliseconds to run before it causes a frame drop.

What hardware did you test on?
LayoutKit will reuse views if a layout has a viewReuseId. For the feed example, you can try adding viewReuseId parameters to all of the LabelLayouts and SizeLayout<UIImageView>s in ProfileCardLayout, FeedItemLayout, and ContentLayout to see (1) if that gets rid of the warning and more importantly (2) if it actually improves performance.
If it does improve performance, feel free to submit a PR to make those changes to the example layouts (they were created before viewReuseId existed).
Collecting this data would also help inform how beneficial #58 would be.

I experimented with viewReuseId and it does noticeably improve performance.
#63 updates the example layouts.

Excellent, Thank you Nick.
Cheers,
Nader Rahimizad

For clarification, if/when #58 is resolved it may not be necessary to specify viewReuseIds everywhere to get better performance (it would only be necessary for animations).


upgrade: ios sdk 0.0.16 -> 0.0.17

https://github.com/pagecall/pagecall-ios-sdk/releases/tag/0.0.17

trivial하여 바로 머지하겠습니다.


Add MusicClient

Is your feature request related to a problem? Please describe.
Music client (used on music.youtube.com) seems to have different search algorithm compared to youtube.com, and can be more suitable if you need to search for a music specifically, and not a video. It also has slightly faster search response compared to youtube.com (around 200-300ms faster)
Describe the solution you'd like
Create a MusicClient with basic functionality like .search and .getMusic
import {Client, MusicClient} from "youtubei";

const client = new Client(); // YouTube Normal Client
const musicClient = new MusicClient(); // YouTube Music Client

Added on https://github.com/SuspiciousLookingOwl/youtubei/commit/9b62e305e144ddba4dc10ddfd8dae7d07e937fec
With 2 API:

.search(keyword)
.getLyrics(id)


{"detail":"Not Found"} error message

{"detail":"Not Found"} receive this clicking this link https://jobseeker-analytics.onrender.com/get-jobs
Can't get beyond this point.

ack, thank you @JasonPopko! looks like the URL gets changed when you click on the hyperlink. can you try copy/pasting https://jobseeker-analytics.onrender.com/get-jobs instead directly into the URL field?

Thx. Getting same error even when I copy the link address

@JasonPopko can you try one more time? it seems to be working for me now


Support Laravel 11

hi @ryangjchandler
is it in your list to check this PR? 🙂
(which is 6+ months old)
it would be awesome to have also Laravel 11.x supported for this package 👍


Trying to set connection_method for SFTP connector causes Terraform failure

Hi,
I'm trying to create a SFTP-connector using Terraform. I have the following TF-config:
resource "fivetran_connector" "sftp_connector" {
  group_id          = data.fivetran_destination.destination.group_id
  service           = "sftp"
  sync_frequency    = var.sync_frequency_min
  run_setup_tests   = "true"
  paused            = var.paused
  pause_after_trial = false

  destination_schema {
    name  = var.destination_schema
    table = var.destination_table
  }

  config {
    connection_method   = var.connection_method
    is_keypair         = var.is_keypair
    password           = var.password
    user               = var.user
    host               = var.host
    port               = var.port
    prefix             = var.folder_path_to_sync
    pattern            = var.pattern
    file_type          = var.file_type
    on_error           = var.on_error
    append_file_option = var.append_file_option
    archive_pattern    = var.archive_pattern
    null_sequence      = var.null_sequence
    delimiter          = var.delimeter
    escape_char        = var.escape_char
    skip_before        = var.skip_before
    skip_after         = var.skip_after
  }
}

Running "terraform plan" I get the error below stating the a connection_method is not expected where I have placed it in my config. I have also tried placing the connection_method key inside destination_schema object but that did not work either.

If I simply remove the connection_method from the config object then everything works, but then I guess Fivetran just is defaulting to the "direct" connection method. It seems like I can't use the expected parameter "connection_method" to control the connection method. According to the docs I think I'm doing things correctly but not getting it to work.

Hi @anderskotsalaineneqt, can you update Fivetran terraform provider to latest version, "connection_method" was added in 0.6.14 version release.

Yep this solve the issue. Only thing worth mentioning is that version 0.6.14 does not exist any more so I had to chose 0.6.15