lxc: fix set memory swap

On LXC memory swap was only set to memory_limit*2 even if a value for
memory swap was provided. This patch fixes this behavior to be the same
as the native driver and set correct memory swap. Also add a test
specifically for LXC but w/o adding a new test requirement.
Haven't found anything about why the behavior shouldn't be the same as the native driver, meaning any value can be specified for memory swap and memory_limit*2 is just a convention.
Even if LXC is deprecated I think this should be fixed cause removal will be in 1.11, right?
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

ping @jfrazelle @ashahab-altiscale

testing on lxc :)

hopefully this fixes https://github.com/docker/docker/issues/15876

mm that tests is not failing on my host with lxc driver though :/

hmmmm

FAIL: docker_cli_run_unix_test.go:207: DockerSuite.TestRunWithKernelMemory :(

Fix for TestRunWithKernelMemory is in https://github.com/docker/docker/pull/16466 though

ah nice! LGTM

@runcom what about TestRunResolvconfUpdate ? probably unrelated to this PR too but just asking.

@tiborvass I'm trying to figure that out but it's tough

@runcom ok but I'm assuming it's unrelated to this PR, as in, LXC should already be failing with that error, right?

@runcom sorry needs rebase ;)

@tiborvass That one seems to be failing randomly on CI runs.

Needs a rebase

@tiborvass yes seems totally unrelated, @cpuguy83 rebased

Ping @tiborvass @cpuguy83 @jfrazelle this is green except on lxc for resolv.conf test

But it's also green on master
On Tuesday, September 22, 2015, Antonio Murdaca<EMAIL_ADDRESS>wrote:

Ping @tiborvass https://github.com/tiborvass @cpuguy83
https://github.com/cpuguy83 @jfrazelle https://github.com/jfrazelle
this is green except on lxc for resolv.conf test
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16418#issuecomment-142356893.

@runcom do we know why there are even more failures on lxc now? :S

the resolv one is always sketch the others...idk

I've opened https://github.com/docker/docker/issues/16520 for the other failing tests

can we get them all in one so its green hehe

just realized that was an issue not PR lol sorry carry on

OOM LXC failures.

@icecrime do we want this (which depends on #16547) in 1.9? these are bug fixes even if lxc is deprecated...

Briefly discussed with @tiborvass, and added it to the milestone

@runcom please rebase :)

rebased


Support hour minute second for non-UTC time zone

This PR supports hour minute and second for non-UTC time zone.
Closes #6834

Also closes #6842

build


Bug fix: when registry is unreachable during re-register process, ser…

when registry is unreachable during re-register process, serviceId may be set to empty and could never be revoverd

Pull Request Test Coverage Report for Build 1072

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
12 unchanged lines in 6 files lost coverage.
Overall coverage increased (+0.2%) to 63.131%

Files with Coverage Reduction
New Missed Lines
%

core/registry/bootstrap.go
1
69.72%

core/config/sd_config.go
1
0.0%

eventlistener/loadbalance_event_listener.go
2
66.67%

core/options.go
2
76.79%

core/handler/transport_handler.go
3
21.95%

core/registry/registrator.go
3
63.06%

Totals

Change from base Build 1069:
0.2%

Covered Lines:
5000

Relevant Lines:
7920

💛  - Coveralls


Mutable StarlarkValue?

Hi,
is there any documentation on how to implement mutable methods/attributes on a StarlarkValue?
The documentation suggests that if one wants a mutable value, one has to implement ComplexValue, however, that trait does not define mutable versions of the methods in StarklarkValue.
I could just use a RefCell in the struct and prevent modification that after freezing the value but that didn't seem right.
Raphael

A RefCell is exactly the right way to do it. For example, Dict is implemented using a RefCell here - https://github.com/facebook/starlark-rust/blob/d6cc74db4462428a2808693166118a10848bb605/starlark/src/values/types/dict/value.rs#L123. Note that Dict is quite complex because of how fundamental they are to the language, so a normal mutable type with RefCell shouldn't be as complex.

Added that as a comment in 68ce5bc8ac802c8f2f0c4d20b3d194a6a992a965.

Thanks, then my approach wasn't wrong.
I was confused by this comment: https://github.com/facebook/starlark-rust/blob/68ce5bc8ac802c8f2f0c4d20b3d194a6a992a965/starlark/src/values/traits.rs#L200.

Thanks - that used to be the case, but stopped being so a while ago. I've updated the docs to:
/// * A type is not [`Send`] and [`Sync`], typically because it contains
///   interior mutability such as a [`RefCell`](std::cell::RefCell).


Caused by: java.lang.IncompatibleClassChangeError: The method 'java.io.File android.support.v4.content.ContextCompat.getNoBackupFilesDir

Caused by: java.lang.IncompatibleClassChangeError: The method 'java.io.File android.support.v4.content.ContextCompat.getNoBackupFilesDir(android.content.Context)' was expected to be of type virtual but instead was found to be of type direct (declaration of 'com.google.firebase.iid.zzg' appears in /data/data/com.example.michaelokello.erp/files/instant-run/dex/slice-com.google.firebase-firebase-iid-9.0.0_e7a33b7a0993c47f35320c5f853852bbb21b5f39-classes.dex)

In the error you posted I see firebase-iid-9.0.0 which implies you are using at least one Firebase dependency at version 9.0.0.  This has known compatibility issues with some versions of the android support libraries.
Please update all of your com.google.android.gms:play-services-* and com.google.firebase:firebase-* dependencies to version 9.0.2 or higher.  Version 9.2.1 is preferred.
Also in the future please do not disregard the issue template, it's very helpful for us when troubleshooting.

@mykfrost it's been 14 days and I believe the solution offered will solve your problem so I am going to close this issue.  Please re-open it if updating your dependencies does not fix it.

thank u sam


Add a Fedora Copr

https://copr.fedorainfracloud.org/coprs/eclipseo/doas/
%global _hardened_build 1

Name:       doas
Version:    0.2.1
Release:    1%{?dist}
Summary:    Execute commands as another user
License:    MIT

URL:        https://github.com/odedlaz/doas/
Source0:    %{url}archive/v%{version}/%{name}-%{version}.tar.gz

Patch0:     doas-0.2.1-fix_dirs.patch

BuildRequires:  gcc-c++
BuildRequires:  cmake
BuildRequires:  pam-devel
BuildRequires:  pkgconfig(libdw)
BuildRequires:  rubygem-ronn

%description
doas is a utility that is aimed to replace sudo for most ordinary use cases.

Project Goals:

 - Secure.
 - Easy. The utility should be easy to audit, to maintain, to extend
   and to contribute to.
 - Friendly. Rule creation should be straight forward. Rule should be easy
   to understand and easy to debug.
 - Powerful. Rules should be short, concise and allow find-grained control.
 - Feature Parity. This project should have complete feature parity
   with the original utility.

%prep
%autosetup -p1 -n %{name}-%{version}

%build
mkdir build && pushd build
export LANG=C.UTF-8
%cmake -DCMAKE_BUILD_TYPE=Debug  -DCMAKE_POSITION_INDEPENDENT_CODE=ON ..
%make_build
popd

%install
pushd build
%make_install
popd

%files
%license LICENSE
%doc README.md
%{_bindir}/doas
%{_mandir}/man1/doas.1*
%{_mandir}/man5/doas.conf.5*

%changelog
* Sun Oct 22 2017 Robert-AndrÃ© Mauchin<EMAIL_ADDRESS>- 0.2.1-1
- First RPM release

Updated to reflect the name change:
https://copr.fedorainfracloud.org/coprs/eclipseo/suex/
The SPEC is available here: https://github.com/eclipseo/packaging/blob/master/suex.spec
If you want it included in Fedora proper, just ask.

@eclipseo , do you mind looking at the copr branch?

I've looked at it, everything should be fine for a future release, but if you want 0.2.2 to build, you need to add the patch from PR #8 .
If you need it to be included in Fedora, ask me anytime and I'll take care of it.


Fix test when using pytest

gemma/positional_embeddings_test.py rely on the default value of the config.
So we need to only change the config for that class Test. Not globally.

Error got fixed by this commit:
commit ebf259b7d47d42874de0b6fa51b476542e2b6689
Author: Michelle Casbon<EMAIL_ADDRESS>Date:   Wed Jul 24 05:55:57 2024 -0700

Thanks.


add support for cmake find_package

Why
Add support for cmake find_package. User can import async_simple easily.
Some package managers also use it. we can add async_simple to package manager later.
Example
find_package(async_simple REQUIRED)
target_link_libraries(<your-target-name> PRIVATE async_simple::async_simple) # dynamic_link
                                 # async_simple::async_simple_header_only
                                 # async_simple::async_simple_static

Windows CI is failing. Please take a look.

Windows CI is failing. Please take a look.

Fixed.


Stack querying needs to deal with SO term's descendants

@udp Has this been updated on your end?

I've added an issue to the SynBioHub tracker, but I just realized that you also do these searches in files.  How is this done?  For this, we cannot rely on SynBioHub, instead, we will need to use the SequenceOntology functionality in libSBOLj to filter.

SBOLUtils.getCDOfRole() returns all CDs whose role is or is a descendent of the query role.  This should handle local files correctly.  Is SynBioHub now doing this correctly as well?  If so, you can close this issue.

This is not in place yet, but Zach and James think it is doable within SynBioHub.  So, I guess this is now a synbiohub issue and can be closed here.

On May 29, 2017, at 6:49 PM, Michael Zhang<EMAIL_ADDRESS>wrote:
SBOLUtils.getCDOfRole() returns all CDs whose role is or is a descendent of the query role. This should handle local files correctly. Is SynBioHub now doing this correctly as well? If so, you can close this issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/SynBioDex/SBOLDesigner/issues/91#issuecomment-304749592, or mute the thread https://github.com/notifications/unsubscribe-auth/ADWD9zQB5K_59FcaIki0zoUC6UFg5VRyks5r-2eDgaJpZM4KinWA.


Do you know why it does that? When i scroll it disappear
Thank you for your help

Can you share your code of how you are creating custom cell ?


Testhound/fp16 comparison

This pull request adds support for the following 16-bit floating point operations to the CUDA target:
heq - (fp16 equal)
hne - (fp16 not equal)
hgt - (fp16 greater than)
hge - (fp16 greater than or equal to)
hlt - (fp16 less than)
hle - (fp16 less than or equal to)
hmax -(fp16 maximum)
hmin - (fp16 minimum)
This PR partly addresses the meta issue "add fp16 support": https://github.com/numba/numba/issues/4402.
 Can you confirm?

gpuci run tests

We can't use the current device's compute capability to control the lowering (as established when we were working through #7460) - we don't know that we're lowering for the current device, or that there even is a current device. This unfortunately means we don't have a way to use the PTX float16 min/max instructions when the compute capability is 8.0 - I'll open an issue for this.

Created #7954 for this.

We can't use the current device's compute capability to control the lowering (as established when we were working through #7460) - we don't know that we're lowering for the current device, or that there even is a current device. This unfortunately means we don't have a way to use the PTX float16 min/max instructions when the compute capability is 8.0 - I'll open an issue for this.

Created #7954 for this.

gpuci run tests

Thanks for the updates. I have verified  that https://github.com/numba/numba/pull/7556/commits/48b0c324cc5e2707e4b65bde7d65356722e9b7ba subsumes the changes in https://github.com/gmarkall/numba/tree/fp16-comparison. For future PRs if this situation arises where there are suggested commits, could you please merge / cherry-pick the suggested commits into your branch rather than re-committing the same changes as a new commit? This will make it easy to verify the changes are the same (or will highlight where there are additions / differences in subsequent commits) and also preserve authorship for the purpose of the review - because those changes come verbatim from my commits, I think they're significant enough that I should get someone else to review them too (as a review of my own code is limited compared to someone else's view on it).

Thanks for the updates. I have verified that 48b0c32 subsumes the changes in https://github.com/gmarkall/numba/tree/fp16-comparison. For future PRs if this situation arises where there are suggested commits, could you please merge / cherry-pick the suggested commits into your branch rather than re-committing the same changes as a new commit? This will make it easy to verify the changes are the same (or will highlight where there are additions / differences in subsequent commits) and also preserve authorship for the purpose of the review - because those changes come verbatim from my commits, I think they're significant enough that I should get someone else to review them too (as a review of my own code is limited compared to someone else's view on it).

@gmarkall input received and I will merge/cherry-pick in the future.

gpuci run tests

@esc could this have a CUDA buildfarm run please?

@esc could this have a CUDA buildfarm run please?

Build numba_smoketest_cuda_yaml_129 has started

@esc could this have a CUDA buildfarm run please?

Build numba_smoketest_cuda_yaml_129 has started

All green 🟢


Fix BoWTransformer test

Changed FakeVectorizer to return a matrix instead of vectors. Also learned that coo_matrix is a much more readable way to construct sparse matrices!

@all-contributors please add @mwilbz for test


Option to disable automatic updates

Great work with vtop, I’ve used it on loads of machines in a variety of places.
I’m currently trying to use it on a server’s mission-control style dashboard, however I’m having difficulty running it longterm because autoupdate keeps dropping to a sudo password prompt.
For now I’ve commented out part of the source to disable automatic updating, but it would be great if there was a flag to do this without me hacking around.  Maybe vtop --no-update or something?

I've also done the same, vtop keeps requesting an upgrade even after updating. Also, I install my global npm packages in ~/.npm so that they don't require sudo to update.

I second this. Automatic updates are crashing vtop despite of updating it through vtop and it is running the latest release.
Automatic updates should be turned off by default in my opinion.

I think subtly informing that there is an update is okay, anything else is limiting the users.


Allow installation on Android

Currently the packaged app can't be downloaded from the Marketplace on Android, but I'm not sure why. I'll look into it, but filing here for posterity.

Closing as we'll be fixing up the codebase and want to keep the issues here for the new version we're working on.
This should be fixed as the new version should be a hosted app.


Replace proc-macro-error with proc-macro-error2

As per https://github.com/rust-lang/docs.rs/issues/2595 :

proc-macro-error is unmaintained with creator being unreachable
syn 1.x being pulled in likely means duplication of syn

So if the conversion is easy, the affected utoipa-gen should be converted asap imo.

utoipa-gen does not use proc-macro-error but instead it is probably coming from some inner dependency: Duplicate for https://github.com/juhaku/utoipa/issues/1028

As added context, it did use it before but the latest releases does not use it. It is at least known to be used by the rust_decimal crate. But perhaps there are others as well.


add new tests for proofs of origin and multiple duties

Jira link

HOTT-2572
HOTT-2352

What?
I have added/removed/altered:

Enabled reintroducePsrRoO spec file
Added new tests for proofs of origin changes and multiple duties

Why?
I am doing this because:

To run new tests as part of the regression suite to ensure that all functionalities are working as expected

It looks good to me, I'm not sure if @jebw has managed to have a review, though?


Add support for different folder names

In a RoundhousE deployment I manage we use different names for the folders then those default specified. RoundhousE has support for these with these parameters "-up" "-sp" "-permissions". It would be nice if grate supported these, as we cannot update to grate without changing our internal workings with the tool.
The reason why we work like this is we have 3 folders

"1. OnlyOnce" (-up)
"2. OnChange" (-sp)
"3. Everytime" (-permissions)

We like this way of working as this keeps the folder clutter down, and we rarely need to fiddle with permissions (we use AD mostly).

Hey mate, good catch 👍
I missed this when building the docco for RH features we don't yet support, so a PR to add custom directory names, or tweak the docco highlighting the missing feature is very welcome.
I'm hoping to get a new release published in the next day or two with 6 months of fixes/enhancements included, but this would be great to see in vNext+1 :)

@wokket already on it :)
I would make it so we can add custom names for all folders if that is ok for you?

Yep. if we're going to do the work then full backwards compat with the options in RH is the goal.

Great initiative, @DjKillerMemeStar . I didn't quite see the need for this feature when initially porting RH to grate, and thought it to be gold-plating, but of course, backwards-compatibility, and, as you say, maybe simplifying the directory structure, could be an aim here.

@erikbra yes indeed! After my holiday i'll look into putting this in + including an option for the folder names roundhouse forgot/didn't want to include.

Perfect, thanks a lot!
And, if there are any questions I can help answering underway too, just give me a shout, of course.

Just a thought, maybe we should just make the whole folder structure(s) configurable, just make it possible to make an ordered list of folder names, with folder type (OneTime, AnyTime, Everytime), so that it could fit different ways of thinking about this?

Yes, this is a very good suggestion. But, I'm a bit sceptical to this example. Doesn't that mead that all folders of type "OneTimeScripts" would be bundled together?
https://docs.microsoft.com/en-us/dotnet/standard/commandline/syntax#multiple-arguments
So we cannot have an ordered list of folders, where different folder types are intertwined? We'd get all of one type, then the next, etc, wouldn't we?
I think, functionally, we need to support an ordered list of folders with no ordering of the type, e.g
setupstuff: Everytime
create-users: OneTime
upscripts: OneTime
storedprocs: AnyTime
test-data: OneTime
run-tests: Everytime
And expect them to be run in that order, with those type specifications.

Berko busy here so not a lot of thought gone into this, but assuming we can change the execution type of a file by filename (https://erikbra.github.io/grate/script-types/everytime/#everytime-scripts) then could we hit your "infinitely configurable folder options" by just allowing the original folder name suggestion, and combine that with custom file names?
In theory that would let you have a single folder (named what you like), running files in any order (via filename sorting) with any execution type (via filename content)??  If someone wants 2 or 3 or n folders after that they just need to override more folder paths via the original suggested change?

I'm not sure I exactly understand your suggestion, however, I would very much like to be able supporting existing folder structures (say, for someone coming from other tools), and not force any changes to folder structure or script naming upon people.
Looking at GrateMigrator, most of the folders can just be put in an ordered list, and it can probably still work:
https://github.com/erikbra/grate/blob/main/grate/Migration/GrateMigrator.cs#L26
There are a few folders which are a bit "special", namely:

AlterDatabase, which runs in a separate transactionscope/no transaction, and on the admin connection,
BeforeMigration, which runs in a separate transaction scope, on the default connection,
RunAfterCreateDatabase (which is only run if the database was actually created, and
Permissions and AfterMigration, which are run in a separate transactionscope/no transaction, on the default connection.

So, if we need to make this fully configurable, we need to at lease support the following:

The list of folders should be ordered, independently of script type
Per folder, we need the following:
a. Folder name
b. Script types (AnyTime, OneTime, EveryTime)
c. Whether to run within the transaction or not
d. Which connection to run on (Should default to ConnectionType.Default, as per now, all folders run on default, except the AlterDatabase folder).

I think that should be the puzzle pieces we need. And then we need to abstract KnownFolders to be a FolderConfiguration or something, which provides an ordered list of folders to run, with the above config per folder.

Sorry, as I said a little scatter brained here atm.
Your latest post also renders my previous one redundant due to the extra complexities in meeting the 'Fully Configurable' spec.
My point was that your 2b above (we need to know what type of file it is) can already be catered for via special casing the filename (.everytime. etc).  If we allowed folder name overrides (the original request, meets your 2a) then we've opened up an awful lot of flexibility in file/folder layout.

I've not had alot of time to think about this, but the best thing i can come up with is to have the ability to send over a json string in a parameter with all the info, this would make it pretty complex tho.
I'm also thinking my suggestion might work if we parse the parameters ourselfs instead of using the build in parameter parsers. But not sure how that works.

Sorry for the lack of feedback here, I've been on vacation (sorry, but not sorry 😉 ). I have started to look at this, in a branch, but I see that some of the logic about stuff that should be ran in a separate, autonomous transaction, is not run in all cases. So I have wrote som (now failing) tests for that, and are working on solving those issues in the existing code base before changing it. I'll create a PR when I have had a bit of more time to look into it.
Having stumbled upon another existing code base (at work) with a bit of different folder naming conventions, I lean more and more towards being able to support any folder structure, using a config (file, parameters, something), to be able to run on a collection of SQL scripts that have been run using another migration tool, with grate as a drop-in replacement, just configuring it to the code base/structure one is already using.


[CT-1194] [Bug] docker build returns error...

Is this a new bug in dbt-core?

[x] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
docker build returns "walk not a directory"
Expected Behavior
It should build the new image.
Steps To Reproduce
I've tried google (to see if is from Docker) but can't find anything usefull.
Took the Dockerfile, renamed it to Dockerfile.dbt and commented all other "FROM" except dbt-core & dbt-postgres.
When I try to build it returns me an error... I don't know if it from Dockerfile.
Runned in Windows 11, under PS, CMD, GitBash and WSL Ubuntu, all returns the same error:
Relevant log output
`
keos@KeosP14s:/mnt/c/Users/civan/Documents/work_dir/docker build --tag my_dbt ./Dockerfile.dbt
[+] Building 0.0s (1/2)
 => ERROR [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 40B                                                                                0.0s
------
 > [internal] load build definition from Dockerfile:
------
failed to solve with frontend dockerfile.v0: failed to read dockerfile: error from sender: walk Dockerfile.dbt: not a directory
`

Environment
- OS: Windows 11 or WSL 2 (Ubuntu)
- Docker: Docker version 20.10.17, build 100c701

Which database adapter are you using with dbt?
postgres
Additional Context
No response

sorry, wrong command
added -f for dockerfile & "PATH", now it returns:
failed to solve with frontend dockerfile.v0: failed to create LLB definition: no build stage in current context
I'll try to resolve this, I'll close this issue.


chore(starknet_integration_tests): add available ports to network config

Stack:

#2796
#2795 ⬅
#2794
#2789
#2788
#2787
#2786
#2781
#2780

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

✓ Commit merged in pull request #2796


Access to memory and other performance data

I am interested in incorporating tests, or any watching mechanism, for monitoring memory associated with the spectron client-> electron. I wonder your opinion if this a) can be interesting and b) how can I start working with any workaround solutions.
My first attempt was to do this:
        console.log('Memory: ' , app.mainProcess.getSystemMemoryInfo());
        console.log('Memory: ' , app.rendererProcess.getProcessMemoryInfo());

But these calls are generating the following outputs:
Memory:  { state: 'pending' }
Memory:  { state: 'pending' }

I also see other features in Electron, such as the following:
https://github.com/electron/electron/blob/master/docs/api/content-tracing.md
Therefore I wonder what would be the ideal set of functions for one that is not only interested in testing ins and outs but also performance.

@taboca All functions in Spectron return promises.  Try doing
app.rendererProcess.getProcessMemoryInfo().then((info)=> console.log(info))

Closing this out, using @MarshallOfSound's example should work for accessing those Electron APIs.


[HTTP] 如何压缩字体

when I use virtualenv --no-site-packages venv to set up a virtual environment for python, I got three folders: include; lib; local, SO differences??


feat(array): use discriminated union if all elements in the array have a "_type"

Closes #170
@miklschmidt

Hell yes this is beautiful! Awesome job, thank you, will update when i'm back at work :)


WIP: Migrate k8s middleware to client-go

do not merge

@miekg just in case I didn't forget this PR. I'm waiting for https://github.com/kubernetes/client-go/issues/27 and https://github.com/kubernetes/client-go/issues/24

I think I have this just about working with #379

You guys fight it out :) I'm out for diner
On 4 Nov 2016 8:27 pm, "John Belamaric"<EMAIL_ADDRESS>wrote:

I think I have this just about working with #379
https://github.com/miekg/coredns/pull/379
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/miekg/coredns/pull/374#issuecomment-258538829, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVkW4bqJlQusorhf_7br8VLMNQkoF2Vks5q65UVgaJpZM4KkZ5i
.

think this is now not needed anymore as I merged #379. (more fixes welcome of course)


Add built in policy definition/set definition paths

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@ravbhatnagar few apis added to existing api versions, some properties removed. Can you please review from ARM side? thanks!

@veronicagg Adding @cyl3392207, the PM for policy related ARM apis

@veronicagg The model validation results are because of missing example for 404 response, which I think is redundant here, and doesn't add any value. The linter result errors are also because of missing examples.

Approve from my side.

No modification for AutorestCI/azure-sdk-for-node

 https://github.com/Azure/azure-sdk-for-ruby/pull/1019

 https://github.com/Azure/azure-sdk-for-python/pull/1507

Approve


permission-backend: fix unauthenticated authorization

Hey, I just made a Pull Request!
The /authorize endpoint endpoint is supposed to be able to handle unauthenticated requests, as is evident here:
https://github.com/backstage/backstage/blob/9802004e10d4f97bdec40f49e50ea090498c5146/plugins/permission-backend/src/service/router.ts#L225-L227
This allows them through, ensuring that unauthenticated authorization isn't broken, which is particularly important when the default auth policy is disabled.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

On second though I don't see a way for the lack of this to actually lead to broken behavior at this point, so gonna hold off on the change but keep it around in case we find a way to reproduce an issue due to the lack of this. It shouldn't hurt to much to add this, but it's always nice to keep things locked down by default. The intended situation where the none path is reached right now is when the default auth policy is disabled, which ofc removes the need for this change.


[feature request] Better Qt5 support for Slots

Currently, all properties have a ctor which takes in slots as char*. However, since Qt5, there's an option to take slot as a member function or even a functor.
Links

Qt4 details
Qt5 details

Would a PR touching multiple property and derived class ctor be entertained?

A corresponding PR supporting the new scheme is highly welcome. The old scheme should be still supported of course.
I'm looking forward to this contribution :smile:


Restore Neovim 0.9.5 compatibility

It looks like some dependencies on Lua features only available on Neovim master have snuck in:

Having vim.uv as an alias for vim.loop

vim.fs.joinpath

Thanks.
Can you prepend the commit message with fix: .

Sure done


about kitti video

Hi, this is a wonderful work. I found in your readme.md you show Qualitative results of our IA-SSD on KITTI dataset. How you get kitti video? Is it kitti 360 dataset?

Hi, @mc171819, thanks for your interest in our work!
We deploy our model on the KITTI Tracking dataset for better visualization here. As for the KITTI dataset, we present a number of slideshows of challenging scenarios in our paper.

thank you for your reply. I also want to ask the differences between single-class and multi-class. In my understand, single-class means you trianed three models predicting car, ped,cyc respectively, multi-class means you trained one models predicting 3 classes in the same time?

Besides, i also wonder the difference between contextual instance centroid perception in your paper and the Candidate Generation Layer in 3d-ssd. You both use votenet to process instance center. About the speed comparision, which part of your model lead to the faster speed to 3d-ssd?
It's very kind of you to explain this to me, thank you!

Hi @mc171819, sorry for the late reply.
For Q1, your understanding is right. We believe using a single model to achieve multi-class object detection is more efficient (in terms of memory and computation) and more practical.
Regarding the contextual centroid perception, we use not only the instance points but also the surrounding background points to predict the centroid, which is achieved by expanded target assign in the training stage.
Regarding the speed improvement, the reasons are manifold:

The usage of effective and efficient instance-sampling strategy.
The design of light-weight backbone, including NSAMPLE and RADIUS setting in SA layer.
The high degree of parallelism benefited from the above.

And you can get more detailed information in our paper, hope these can help you!


Upgrade to Dotty 0.19.0-RC1

fixes #30
It compiles and passes the tests
Note: intent.formatters.FormatTest::'supports Try-Failure' failed to infer the implicit so I added an explicit type parameter of Try[Int]
Also I removed the ClassTag parameter from the given for TryFmt[TInner, T], which I assume was added just to keep them as anonymous

Very nice! I opened the code in my now restored editor and it works just fine. When I tried the upgrade before I had a christmas tree of errors...
I will take a look at the changes you did. If I remove ClassTag from TryFmt with 0.18.1, I get

with:
cannot merge
  method Formatter_T_given in trait FormatterGivens of type [TInner, T <: util.Try[TInner]]
   given (x$1: intent.core.Formatter[TInner]): intent.core.Formatter[T]  and
  method Formatter_T_given in trait FormatterGivens of type [TInner, T <: Option[TInner]]
   given (x$1: intent.core.Formatter[TInner]): intent.core.Formatter[T]
they are both defined in trait FormatterGivens but have matching signatures
  [TInner, T <: util.Try[TInner]]
   given (x$1: intent.core.Formatter[TInner]): intent.core.Formatter[T] and
  [TInner, T <: Option[TInner]]
   given (x$1: intent.core.Formatter[TInner]): intent.core.Formatter[T]
as members of trait FormatterGivens

So I suppose there are some improvements in 0.19.0 that make this error go away...
Thank you for your help!

The error still appears in 0.19, but really its masking the fact that the anonymous givens have the same generated name, so I gave them sensible names, but that may be against your style, so that can be reverted easily

Aha, I see. No, using sensible names is better than adding ClassTags, I think.
We're doing this project partly to explore/learn Dotty, so we don't really have a preferred style yet.

This is nice work, perhaps it could be added to the community build?

Thank you!
Yes, that'd be great. I suppose we just follow the instructions at https://github.com/lampepfl/dotty/tree/master/community-build/test/scala/dotty/communitybuild ?

Yes thats correct, and then the test runner just calls whatever sbt commands you need to compile all the sources and then optionally test the runtime behaviour of your project.

I still have problems with the editor, it seems. Out of curiosity, I removed the option -Yindent-colons which you added. A subseqent compilation resulted in 45 errors, the first in future.scala. I then opened the editor using launchIDE. No errors in future.scala. I removed the eol colon on line 19. Now the editor starts showing errors, the first on given inside of the parentheses on line 10. If I move given outside of the parentheses, the editor is happy.
So it seems my editor is severely out of sync. I will try reinstalling the Scala and Dotty plugins again to see if that helps.

Ok, -Yindent-colons appears to be required for consistency between compiler and editor.

I think i might know your problem, if you do not clean your project, and a compilation fails, but there already exist .dotty-ide-artifact and .dotty-ide.json files in the project root then the previously compiled code and settings are used in the editor.

Thanks, I'll add those files to the clean task for now.


Codeowners check should run on pull_request instead of pull_request_target

I broke CODEOWNERS in #9283, but CI still passed because the action was configured to run on pull_request_target. That makes it run in the base commit instead of the merge commit, so it doesn't test changes. Since we don't need write access, I just switched to pull_request. See the difference in the screenshot below.

@agarwal-navin FYI since you hit this.


How to increase loss scalar frequency while using Tensorboard callback?

Thank you for the amazing work.
I am using Tensorboard to visualize my training, and it works just fine.
But when I need to change the frequency of loss scalers, I can't find api to do this. I want to more scalers log, maybe log end of every batch. Now I can only get one log during an epoch. Thanks a lot.
tensorboard_callback = TensorBoard(log_dir = log_dir,
    histogram_freq = 1,
    write_graph = True,
    write_images = False,
    embeddings_freq = embeddings_freq,
    embeddings_layer_names = None,
    embeddings_metadata = "w2v_metadata.tsv")

[x ] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[x ] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[ ] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[ ] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

duplicated #6692


npm package warnings

There are a bunch of package warnings for dependencies of v1, some more dire than others:
$ npm install
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>The original electron project has been moved. Visit github.com/logicalparadox/electron for more details.
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade

This boils down to specifying dependence on 4yo versions of grunt, opener, and matcha.
They're just dev dependencies, so probably the only semi-urgent upgrade would be graceful-fs (via grunt), since those will break with the pending v7.0.0 release of node.

@valderra-jpl What version of npm and node are you running?
I am running npm 3.10.10 and node v7.3.0 - I don't see any of those warnings.


Replace 'BitBox Base' with  'BitBoxBase'

Because:

In the past, the project/product was called 'BitBox Base' and that is reflected accross documentation, scripts and code comments.
It's better to consistently change all occurrences now to the new naming of 'BitBoxBase' instead of doing it gradually.

This commit:

replaces case-sensitive 'BitBox Base' with 'BitBoxBase'
no working code is affected, only docs, code comments and one err msg

Readme logo is old as well. Could be addressed here.


Blob container rename fails

Storage Explorer Version: 1.10.0
Build Number: 20190912.8
Platform/OS: Windows 7
Architecture: x64
Regression From:  Unsure, but yes, many versions ago.
Bug Description
When attempting to rename a blob container I am getting multiple errors saying the file already exists. Since it's a simple rename and blob name must be unique it shouldn't be possible to have this error.
Steps to Reproduce
Create blob container
Add a reasonable number of blobs (tested with 100k)
Rename blob container to something else
Expected Experience
I would expect this process to take some time but complete without errors.
Actual Experience
Hundreds of conflicts complaining that a blob with the same name already exists (shouldn't be possible for a simple rename?)
Hundreds of errors complaining:

Could not delete the original item after copying.
Details:
The specified blob does not exist.

Again, shouldn't be possible if the blob was successfully copied?
Finally the rename operation fails due to too many errors occurring.
Additional Context
None

This is definitely a bug caused by us. It seems that we are incorrectly trying to paste/delete some of the blobs twice. However, it shouldn't block you from using the data in the new container because the data should have been transferred. If you really want the old container to be deleted, you can manually delete it for now.

The wider issue is that after multiple failures the whole process fails, then after additional retries it just stops retrying altogether leading to a partial copy.


test fix for kind_provisioner.sh to prevent modificationof kind confi…

…g files
Please provide a description of this PR:
just for testing, will PR against common-files once testing completes

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

/test all

@ilrudie: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
66a497c175794bef2abf2b284080cfd82e960039
link
true
/test release-notes

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

@ilrudie: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
66a497c175794bef2abf2b284080cfd82e960039
link
true
/test release-notes

unit-tests-arm64_istio
66a497c175794bef2abf2b284080cfd82e960039
link
true
/test unit-tests-arm64

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

/test integ-ambient-calico

/test integ-ambient-dual


keywords?

Hi, no matter how hard I look, I cannot find any keyword list?
I just want a simple stepper start & stepper stop, for continuous rotation.
I can find emergency stop in an example, but nothing else.
sorry to post here, cannot find any other on-line reference, tutorial for this library.
I like the idea of running it on core 0. Have tries continuous stepper library, but it somehow gets interfered with when the tft screen updates.

I guess you are looking for the jogging function.


Delete packetserver package

[ ] Delete packetserver package in modules
[ ] Delete packetserver package in modules
[ ] Delete custom routing in msg_server
[ ] Delete msg_server tests for packetserver

Blocked on #7456


fixed mobile view of home page

Title and Issue number
Title : Fixing Css in mobile view
Issue No. : #790
Code Stack :
Close #790

Description

Video/Screenshots (mandatory)

before:

after:

Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Checklist:

[X] I have performed a self-review of my code.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have gone through the  contributing.md file before contributing

Additional context:

##Are you contributing under any Open-source programme?

@apu52  please merge this PR

@apu52 Please check PR and merge it

@apu52 please merge the PR with gssoc label

Okay i will make

done @apu52 check it


[ADD ME TO THE ORGANIZATION]

SkyCaptainess:
United States:
Programing, Vocal Music:
AC:-
Why do you want to join?

I want to join because to make bigger and larger something with friends.

You can also join our Discord community here
Feel free to check out other cool repositories of the DevsInTech Community here.

SkyCaptainess:
United States:
Programing, Vocal Music:
AC#2873
Why do you want to join?
I want to join because to make bigger and larger something with friends.

Hey @SkyCaptainess What issue are you facing?


[RFC] extend the AdrPlugin to support gitlab too.

Status: Open for comments
Need
The ADR plugin as of right now does not support any other service other than GitHub.
this RFC target is to extend this plugin feature to also support GitLab.
Proposal
the plugin is using a custom hook name useOctokitRequest to get the repo content and file content from GitHub.
by using the Octokit library which only supports GitHub.
this hook takes the URL and returns the list of contents in the repo or file according to the URL.
according to my current plan.

create useAdrFilesList(url) -> [filepaths...]
create useAdrFileContent(filename) —> string (raw utf-8)
remove useOctokitRequest hook

these two hooks internally have to decide whether the request currently made is for Gitlab or GitHub.

the good thing is, this solution is expandable for other services also such as bitbucket etc.

right now my strategy is to trim the hostname from the URL and decide whether the current request is for GitLab or GitHub

useAdrFileList will be used in EntityAdrContent, where we will replace it with useOctokitRequest to get the ADR files list.
useAdrFileContent will be used in AdrReader, where we will replace it with useOctokitRequest to the content inside the file in UTF-8 format.

this solution will add the Gitlab support to the plugin-adr immediately, and create a smooth path for future extensions.

happy to pickup / contribute.

Another possible implementation is to build out the backend service to make use of the built in UrlReaders and have the frontend proxy all requests through the backend instead (similar to what the TODO plugin does). The search collator is already using UrlReaders so indexing ADRs already support all integrations and inspiration can be taken from there. This will also allow the plugin to be completely SCM agnostic and not just limited to Github/GitLab

I would be interested in support for Bitbucket Cloud.
I wonder a bit how to make these kind of things (support for all SCM providers) easier. 🤔

👍 to the idea of using the UrlReaders for this so that way it works with Azure DevOps Repos and Bitbucket Server which is what we are using

Can someone please re-open this

@freben @benjdlambert

It is recommended to open this issue. Please do not bind with github. Like techdocs, it can support multiple warehouses. After all, it is impossible to only support github in enterprise development, most of them use gitlab

Support for using UrlReaders in the ADR plugin was merged in on January 4, 2023 in this PR: https://github.com/backstage/backstage/pull/15348 and officially release with version 1.10.0 of Backstage
UrlReaders (https://backstage.io/docs/plugins/url-reader/) support pretty much all of the current integrations: https://backstage.io/docs/integrations/


Release v4.0.0, beta 13

This release will add the Mr. Bayes 'n' Beast (MB'n'B) pipeline that @hawkrives added in #103.

Do we want to wait to add in the new pruning outliers algorithm in the same release?

@OmarShehata, if you think you can have it ready tonight, sure, however, the tag has already been made and pushed… we can make yet another beta tonight.  I'll hold off on emailing the bio team until we know whether or not we want to do that, but for now this is in the process of deployment.

@rye it's already done and waiting to be merged.


provide template for consuming restful resources, refactor

hey uplift! awesome job so far!!! i got excited after working with you all, looked back at some angular, and made some suggestions. feel free to merge these changes and add to them or use them however you want. a couple things:
$resource:
since were consuming a restful api, we can can return a resource with functions like save and delete. that is located in the factories folder. the same thing can be done with your other models, like events. there is a problem right now saving, putting, and deleting, but I think part of that is the backend. Are these routes defined?
controllers as:
In the controllers, you will see something like var vm = this (vm is just a naming). "this" in the controller, is "organization" (or whatever we want to call it) in the view.

here are some other resources i think will help.
https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md
http://fdietz.github.io/recipes-with-angular-js//consuming-external-services/consuming-restful-apis.html
https://docs.angularjs.org/api/ngResource/service/$resource
https://www.sitepoint.com/creating-crud-app-minutes-angulars-resource/
feel free to email me<EMAIL_ADDRESS>if you have any questions. good luck and keep grindin!!!

@afayek1 Hey Amir, thank you for spending time on this and sending feedback on how we can improve. We are going to continue working on this so we'll definitely try and implement your code and get back to you with questions!! Thanks again!


I train ssd on a dataset which only has one class. When I run demo.py, there is an error.

I want to use ssd to detect text in images, so I train ssd on ICDAR dataset. I successfully train this model, and get the saved params and json on the folder 'Model'. Then I want see the performance of my model, so I run demo.py, but there is an error:
[15:02:26] /home/ubuntu/mxnet/dmlc-core/include/dmlc/logging.h:235: [15:02:26] src/ndarray/ndarray.cc:231: Check failed: from.shape() == to->shape() operands shape mismatch
Traceback (most recent call last):
File "demo.py", line 95, in
ctx, args.nms_thresh, args.force_nms)
File "demo.py", line 41, in get_detector
data_shape, mean_pixels, ctx=ctx)
File "/home/ubuntu/mxnet/example/ssd_LPR/detect/detector.py", line 39, in init
self.mod.set_params(args, auxs)
File "/home/ubuntu/mxnet/python/mxnet/module/base_module.py", line 503, in set_params
allow_missing=allow_missing, force_init=force_init)
File "/home/ubuntu/mxnet/python/mxnet/module/module.py", line 198, in init_params
_impl(name, arr, arg_params)
File "/home/ubuntu/mxnet/python/mxnet/module/module.py", line 188, in _impl
cache_arr.copyto(arr)
File "/home/ubuntu/mxnet/python/mxnet/ndarray.py", line 533, in copyto
return _internal._copyto(self, out=other)
File "/home/ubuntu/mxnet/python/mxnet/ndarray.py", line 1225, in unary_ndarray_function
c_array(ctypes.c_char_p, [c_str(str(i)) for i in kwargs.values()])))
File "/home/ubuntu/mxnet/python/mxnet/base.py", line 77, in check_call
raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: [15:02:26] src/ndarray/ndarray.cc:231: Check failed: from.shape() == to->shape() operands shape mismatch
I have changed the class in demo.py like this:
CLASSES = ('text')

I find I need to use two classes like 'text' and 'backgroud' in training or demo.py. In this way, I get no error. But I don't understand why only one class can not work.

Have you modified the class name in dataset class?

Yes, I have wrote a new data loading files in folder "dataset" which refers to "imdb.py", and I have modified "self.classes". I get no error when I set two classes like 'text' and 'backgroud' both in dataset class and "demo.py". However, if I use only one classes, I get such error.

Before
self.mod.set_params(args, auxs)

Can you print the shapes of params in args?

 Could you share your dataset.py? I also train a one class ssd on fddb but Train-ObjectAcc=0.026159.

@BunnyShan Thank you a lot!
@KeyKy It can converge. My 'dataset.py' just refers to the examples, and it is not very complex. I think the reason may not be "dataset.py" which is just the input file. I think you should check some mistake like that you mistake the x location as y.

@oyxhust Hi, I'm also using ssd to detect text on ICDAR2013 dataset, I changed the dataset to pascal-voc format , so I only need  change the data path of the imdb. But I find it's hard to get converged, this is the result after 100 epochs with learning rate 0.0005:

and 300 epochs seems not to make much difference.
Could you share your hyper-parameters or offer some help?
thanks you very much!

@xinghedyc
1、 I don't train my model directly on ICDAR, because it is not big enough. I suggest that you can train your model on SynthText, and then fine tune it on ICDAR. In this way, I believe you can gain a good performance.
2、 For the hyper-parameters setting, if you use this model for some application like license plate detection, I think the original SSD model is enough. If you want to get a better performance, you can refer to this paper (http://mc.eistar.net/UpLoadFiles/Papers/TextBoxes-AAAI17-draft.pdf) which is from my friend's lab in HUST. It can be very easy to realize, you just need to change some size of convolution kernel and default boxes to make them more suitable for text detection.

@oyxhust Thanks for your reply!

@oyxhust I got the same error as follows. How to solve this problem? Thanks.
Traceback (most recent call last):
File "demo.py", line 101, in
ctx, args.nms_thresh, args.force_nms)
File "demo.py", line 44, in get_detector
data_shape, mean_pixels, ctx=ctx)
File "/home/tx-eva-02/mxnet/example/ssd/detect/detector.py", line 38, in init
self.mod.set_params(args, auxs)
File "/home/tx-eva-02/mxnet/python/mxnet/module/base_module.py", line 557, in set_params
allow_missing=allow_missing, force_init=force_init)
File "/home/tx-eva-02/mxnet/python/mxnet/module/module.py", line 264, in init_params
_impl(desc, arr, arg_params)
File "/home/tx-eva-02/mxnet/python/mxnet/module/module.py", line 252, in _impl
cache_arr.copyto(arr)
File "/home/tx-eva-02/mxnet/python/mxnet/ndarray.py", line 556, in copyto
return _internal._copyto(self, out=other)
File "/home/tx-eva-02/mxnet/python/mxnet/_ctypes/ndarray.py", line 131, in generic_ndarray_function
c_array(ctypes.c_char_p, [c_str(str(i)) for i in kwargs.values()])))
File "/home/tx-eva-02/mxnet/python/mxnet/base.py", line 77, in check_call
raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: [12:21:15] src/ndarray/ndarray.cc:239: Check failed: from.shape() == to->shape() operands shape mismatchfrom.shape = (126,) to.shape=(12,)

could you share the ssd_model?，for example baidudisk .....
thank you so much。


settings: tasks: launch: Add the torizon_run_as

This is needed if exist the need to run the application with another user, root for example.
Signed-off-by: Matheus Castello<EMAIL_ADDRESS>Related-to: TIE-729

@andreriesco FYI


Better labeling

So I'm not quite sure what the solution to this is, but here's the problem:  A large portion of our spec code does map to assign a list of containers each their own individual label.  The issue is that, from the network perspective, If labels are connected, you can only really access them through a vip -- they aren't individually addressable.  A simple case this breaks is spark, where the worker nodes really should be dealt with as a single unit, but the master really needs the ability to talk to them individually.  This seems fairly important.

Migrated to Trello.
https://trello.com/c/v0IfSwXc


Create UML discribing BV structure

Documentation is good. Create a UML once we get things more stable

Documentation in general needs work

Lets wait on the UML itself until after the upcoming rewrite, but we should at least document the current workings of the FEAGI ecosystem overall


render as an image file [request]

I couldn't find a way to do this currently. I want to be able to render a pointcloud as a 2-d image. So like what I see when I call plot() but to save that as an image file. I couldn't figure out how to do that currently.

I'm going to add a "Screenshot" button to the 3D renderer. More info comming soon.

Screenshot button added in #128
On click, it will open a new window in your browser with a image ready to be downloaded:

From what I can tell this works on Firefox but not Chrome. Thanks!

how can i get the above mentioned output using pyntcloud plot()


Failed to create connection to server 'PicoTorrent' on topic 'ApplicationOptions': a client's attempt to establish a conversation has failed.

Updating to the latest version causes this error on startup and the application exits. It seems to be a wxWidgets issue.

I did uninstall/reinstall, clear the AppData folder and settings, but the same message appears.
The operating system is Windows 7.

Are you running through Sandboxie?

No, just normally.

+1 Same issue for me. The client just freezed while downloading, now I cannot do anything with it.

This has been resolved with #672 which will be released as v0.16.

This one returned. It's not persistent as the OP, just one time.
Win7


Upgrade Weld to 2.2.9.Final

Windows Build 916 is now running using a merge of ecf5d1472ae8913e65373f51753835795bc3cea3

Linux Build 5806 is now running using a merge of ecf5d1472ae8913e65373f51753835795bc3cea3

Linux with security manager Build 792 is now running using a merge of ecf5d1472ae8913e65373f51753835795bc3cea3

Linux with security manager Build 792 outcome was SUCCESS using a merge of ecf5d1472ae8913e65373f51753835795bc3cea3
Summary: Tests passed: 851, ignored: 316 Build time: 0:06:22

Windows Build 916 outcome was SUCCESS using a merge of ecf5d1472ae8913e65373f51753835795bc3cea3
Summary: Tests passed: 2934, ignored: 311 Build time: 0:50:19

Linux Build 5806 outcome was SUCCESS using a merge of ecf5d1472ae8913e65373f51753835795bc3cea3
Summary: Tests passed: 2933, ignored: 311, muted: 1 Build time: 0:51:56


Poor connections to Home Assistant Yellow (TZ-972)

Answers checklist.

[X] I have read the documentation ESP Zigbee SDK Programming Guide and tried the debugging tips, the issue is not addressed there.
[X] I have updated ESP Zigbee libs (esp-zboss-lib and esp-zigbee-lib) to the latest version, with corresponding IDF version, and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.4-dev-1205-ge7070e777a
esp-zigbee-lib version.
1.3.2
esp-zboss-lib version.
1.3.2
Espressif SoC revision.
ESP32C6 and ESP32H2
What is the expected behavior?
Be able to join a Zigbee network reliable
What is the actual behavior?
Lot of luck to join a Zigbee network. See usually only the following outout:
BESP-ROM:esp32c6-20220919
Build:Sep 19 2022
rst:0x1 (POWERON),boot:0xc (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:2
load:0x40875720,len:0x1804
load:0x4086c110,len:0xe74
load:0x4086e610,len:0x2e7c
entry 0x4086c11a
I (23) boot: ESP-IDF v5.4-dev-1205-ge7070e777a 2nd stage bootloader
I (24) boot: compile time Jun 27 2024 16:31:16
I (24) boot: chip revision: v0.0
I (28) boot.esp32c6: SPI Speed      : 80MHz
I (33) boot.esp32c6: SPI Mode       : DIO
I (38) boot.esp32c6: SPI Flash Size : 4MB
I (42) boot: Enabling RNG early entropy source...
I (48) boot: Partition Table:
I (51) boot: ## Label            Usage          Type ST Offset   Length
I (59) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (66) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (73) boot:  2 factory          factory app      00 00 00010000 000e1000
I (81) boot:  3 zb_storage       Unknown data     01 81 000f1000 00004000
I (88) boot:  4 zb_fct           Unknown data     01 81 000f5000 00000400
I (96) boot: End of partition table
I (100) esp_image: segment 0: paddr=00010020 vaddr=420a0020 size=32c64h (207972) map
I (152) esp_image: segment 1: paddr=00042c8c vaddr=40800000 size=0d38ch ( 54156) load
I (165) esp_image: segment 2: paddr=00050020 vaddr=42000020 size=99294h (627348) map
I (295) esp_image: segment 3: paddr=000e92bc vaddr=4080d38c size=0281ch ( 10268) load
I (298) esp_image: segment 4: paddr=000ebae0 vaddr=4080fbb0 size=02434h (  9268) load
I (307) boot: Loaded app from partition at offset 0x10000
I (307) boot: Disabling RNG early entropy source...
I (324) cpu_start: Unicore app
I (333) cpu_start: Pro cpu start user code
I (333) cpu_start: cpu freq: 160000000 Hz
I (334) app_init: Application information:
I (336) app_init: Project name:     on_off_light_bulb
I (342) app_init: App version:      6d288fb-dirty
I (347) app_init: Compile time:     Jun 27 2024 16:30:56
I (353) app_init: ELF file SHA256:  XXXXXXXXXX...
I (358) app_init: ESP-IDF:          v5.4-dev-1205-ge7070e777a
I (365) efuse_init: Min chip rev:     v0.0
I (370) efuse_init: Max chip rev:     v0.99
I (375) efuse_init: Chip rev:         v0.0
I (379) heap_init: Initializing. RAM available for dynamic allocation:
I (387) heap_init: At 408166E0 len 00065F30 (407 KiB): RAM
I (393) heap_init: At 4087C610 len 00002F54 (11 KiB): RAM
I (399) heap_init: At 50000000 len 00003FE8 (15 KiB): RTCRAM
I (406) spi_flash: detected chip: generic
I (410) spi_flash: flash io: dio
W (414) spi_flash: Detected size(8192k) larger than the size in the binary image header(4096k). Using the size in the binary image header.
I (427) sleep: Configure to isolate all GPIO pins in sleep state
I (434) sleep: Enable automatic switching of GPIO sleep configuration
I (441) coexist: coex firmware version: 66616e60c
I (455) coexist: coexist rom version 5b8dcfa
I (456) main_task: Started on CPU0
I (456) main_task: Calling app_main()
I (466) phy_init: phy_version 310,dde1ba9,Jun  4 2024,16:38:11
W (466) phy_init: failed to load RF calibration data (0x1102), falling back to full calibration
W (516) phy_init: saving new calibration data because of checksum failure, mode(2)
I (526) phy: libbtbb version: 04952fd, Jun  4 2024, 16:38:26
ZBOSS: common/zb_init_default.c:181   ED build
ZBOSS: common/zb_init_default.c:187   sizes: g_zb 7408 sched 224 bpool 16 nwk 912 aps 3040 addr 284 zdo 840
ZBOSS: common/zb_init_default.c:196   sec 2
ZBOSS: common/zb_init_default.c:198   zcl 600
ZBOSS: common/zb_init_default.c:201   zll 960
ZBOSS: common/zb_init_default.c:207   nvram 140
ZBOSS: common/zb_init_default.c:210   buttons 200
ZBOSS: common/zb_init_default.c:212   err_ind 4
ZBOSS: common/zb_init_default.c:218   scheduler q size 80
ZBOSS: common/zb_init_default.c:221   g_mac 816 g_imac 28
ZBOSS: common/zb_init_default.c:225   Configurable mem build, use ZBOSS lib defaults = 0
ZBOSS: common/zb_init_default.c:231   ZB_IOBUF_POOL_SIZE 80 ZB_NWK_IN_Q_SIZE 40 ZB_MAC_PENDING_QUEUE_SIZE 20 ZB_APS_DST_BINDING_TABLE_SIZE 16 ZB_APS_BIND_TRANS_TABLE_SIZE 20 ZB_N_APS_RETRANS_ENTRIES 27
ZBOSS: common/zb_init_default.c:261   ZB_N_APS_KEY_PAIR_ARR_MAX_SIZE 8 ZB_IEEE_ADDR_TABLE_SIZE 64 ZB_NEIGHBOR_TABLE_SIZE 64 ZB_NWK_ROUTING_TABLE_SIZE 0 ZB_APS_DUPS_TABLE_SIZE 32
ZBOSS: zdo/af_descriptor.c:357   ep_count 1
I (616) main_task: Returned from app_main()
ZBOSS: zdo/zdo_app_prod_conf.c:144   no production config block found
ZBOSS: zdo/zdo_app_prod_conf.c:781   no valid production configuration found, signaling to application
I (746) ESP_ZB_ON_OFF_LIGHT: ZDO signal: ZDO Config Ready (0x17), status: ESP_FAIL
I (756) ESP_ZB_ON_OFF_LIGHT: Initialize Zigbee stack
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:349   dev type 2, joined 0, ext_pan_id 0, authenticated 0, tclk_valid 1
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:549   COMMISSIONING_STOP: app signal 5 comm status 0
I (776) gpio: GPIO[8]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (776) ESP_ZB_ON_OFF_LIGHT: Deferred driver initialization successful
I (796) ESP_ZB_ON_OFF_LIGHT: Device started up in  factory-reset mode
I (806) ESP_ZB_ON_OFF_LIGHT: Start network steering
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:349   dev type 2, joined 0, ext_pan_id 0, authenticated 0, tclk_valid 1
ZBOSS: mac/mac.c:1039   Oops - error beacon payload is too small buf_sz 15 - drop it
ZBOSS: zdo/zdo_commissioning.c:210   Can't find PAN to join to! param 25
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:549   COMMISSIONING_STOP: app signal 10 comm status 3
I (3066) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: ESP_FAIL)
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:349   dev type 2, joined 0, ext_pan_id 0, authenticated 0, tclk_valid 1
ZBOSS: mac/mac.c:1039   Oops - error beacon payload is too small buf_sz 15 - drop it
ZBOSS: zdo/zdo_commissioning.c:210   Can't find PAN to join to! param 15
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:549   COMMISSIONING_STOP: app signal 10 comm status 3
I (6336) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: ESP_FAIL)
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:349   dev type 2, joined 0, ext_pan_id 0, authenticated 0, tclk_valid 1
ZBOSS: zdo/zdo_commissioning.c:210   Can't find PAN to join to! param 6
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:549   COMMISSIONING_STOP: app signal 10 comm status 3
I (9606) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: ESP_FAIL)
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:349   dev type 2, joined 0, ext_pan_id 0, authenticated 0, tclk_valid 1
ZBOSS: mac/mac.c:1039   Oops - error beacon payload is too small buf_sz 15 - drop it
ZBOSS: zdo/zdo_commissioning.c:210   Can't find PAN to join to! param 6
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:549   COMMISSIONING_STOP: app signal 10 comm status 3
I (12876) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: ESP_FAIL)
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:349   dev type 2, joined 0, ext_pan_id 0, authenticated 0, tclk_valid 1
ZBOSS: mac/mac.c:1039   Oops - error beacon payload is too small buf_sz 15 - drop it
ZBOSS: zdo/zdo_commissioning.c:210   Can't find PAN to join to! param 6
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:549   COMMISSIONING_STOP: app signal 10 comm status 3
I (16146) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: ESP_FAIL)
ZBOSS: commissioning/bdb/zdo_commissioning_bdb.c:349   dev type 2, joined 0, ext_pan_id 0, authenticated 0, tclk_valid 1
[..]

Steps to reproduce.

Have a ESP32C6 or ESP32H2

Was tested with the following hardware:

Waveshare ESP32-C6-Dev Kit N8
Waveshare ESP32 H2 Dev Kit N4
Seeed Studio XIAO ESP32C6 with internal and external antenna (See pin 14)

Have a Home Assistant Yellow in the regular configuration with Zigbee enabled. This also means NO multiprotocol support - Zigbee only.
Checkout esp-zigbee-sdk in revision #4383011.
Go to examples/esp_zigbee_HA_sample/HA_on_off_light.
Run:idf.py set-target esp32c6

Enable Zigbee debugging of ESP32 with:idf.py menuconfig

Start searching for new Zigbee devices in Home Assistant (Default: http://homeassistant.local:8123/config/zha/add).
Run:idf.py -p <PORT> erase-flash build flash monitor

More Information.

This was tested with several devices.
If the Home Assistant Yellow is in range of 50cm to 1m it always works.
If another Zigbee device (tested with Philips LOM007 Hue Smart Plug) is in mode Router is in range of 50cm to 1m it always works. Also if the distance between Home Assistant Yellow and the ESP32 is more than 10m.
If another Zigbee device (tested with Philips LOM007 Hue Smart Plug) is in mode Router is 5m away it does also not work.
Another Zigbee End Device (tested with Philips RWL021 Hue Dimmer Switch) which is in the same location as the ESP32 this device always works. Also if the ESP32C6 fails to work. Many other devices teste and all are working as expected.

Could you please provide the pcap file if you have a sniffer?
BTW, did all the three ESP boards fail to work?

@blaubaer ,

This was tested with several devices.
If the Home Assistant Yellow is in range of 50cm to 1m it always works.
If another Zigbee device (tested with Philips LOM007 Hue Smart Plug) >is in mode Router is in range of 50cm to 1m it always works. Also if the distance between Home Assistant Yellow and the ESP32 is more than 10m.
If another Zigbee device (tested with Philips LOM007 Hue Smart Plug) is in mode Router is 5m away it does also not work.
Another Zigbee End Device (tested with Philips RWL021 Hue Dimmer Switch) which is in the same location as the ESP32 this device always works. Also > if the ESP32C6 fails to work. Many other devices teste and all are working as expected.

According to the above description, the issue seems to be related to the energy of joining the network. The ESP device will determines whether to join the network based on the network's LQI. But the threshold value for joining LQI can be set using the esp_zb_secur_network_min_join_lqi_set() API. The default joining LQI threshold is 32. Could you set it to a smaller value and test it again?

Hi @xieqinan
In steps of ~5 I lowered it down to 10. There the connection works reliable, also in the same ranges as the Philips devices.
I would recommend to either change the default value or at least improve the documentation (for example the FAQ section).

@blaubaer ,

I would recommend to either change the default value or at least improve the documentation (for example the FAQ section).

No problem, I will consider adding the minimum joining LQI issue to the FAQ. Thanks for your testing and suggestion.


How does the 'prefix' work in a canvas renderer?

I am writing a canvas node renderer which displays more information than x, y, and size from a node. So my node looks like:
{
  x: 1,
  y: 1,
  size: 1,
  name: 'Physics',
  number: 101
}

And I want to display number inside the node, and name in the label.
I noticed in the def renderer x and y are not directly obtained but through a prefix. Regarding that the wiki states:

With the Canvas renderer, to keep all these steps independants from each other,
every of these routines takes a prefix as input and sets the coordinates with a new
output. This makes possible to have multiple cameras running at the same time in
the same sigma instance.

In the same spirit I tried to obtain number in a similar fashion by node[prefix + 'number'], but it returned undefined. Direct access by node.number is working, but why is prefix not?

I second this, a little bit confused about the 'prefix' thing.

Now that I come back to it, the purpose of the prefix is to separate cameras, and in such case only x and y, namely the position, changes. All other properties should not change, otherwise the nodes displayed in different cameras will not be referring to the same node in the graph.

Hello @21stcaveman and @louy2, indeed the prefix only applies to the "geographical" properties of the node such as x, y and size. They are the mapping of your node's properties within different referentials such as the actually rendered position and the virtual camera position. This is made so because you might need them and so you can bind several cameras and/or renderers to a single graph.

@Yomguithereal , @louy2 Thank you, this clears things up!


External component support PR

We'd like to support loading external components. @NoxNovus can summarize progress on this so far. (This might take a while to put through.)

@NoxNovus after summarizing the progress, let's close this PR for now to keep the PR list clean, we can re-open when it makes sense to work on this again.

I've also tagged this commit, so we can safely delete the branch.


Different symbols?

Hi,
have you considered using different symbols?
const bullet = "⬤";
const circle = " ⦁ ";

yields:

Hi,
I guess I can try to add config window where people can choose needed symbols for each (active and inactive workspaces).

I config file would also be alternative.


Run go fmt

I'm working on some other changes, but I figured I'd send through this commit.
@jwilder would you be in favor of changing the Travis build to fail if go fmt hasn't been run?

@md5 Yeah. Sounds good.

cf. #62


[Feature] How to show album name in chinese?

When i get album list use [getAssetPathList] method, then AssetPathEntity->name foreach, all is english.

Assuming this question is for IOS, you will need to follow the steps mentioned here
https://github.com/fluttercandies/flutter_photo_manager#localized-system-albums-name

Assuming this question is for IOS, you will need to follow the steps mentioned here
https://github.com/fluttercandies/flutter_photo_manager#localized-system-albums-name

it is run android.

@AlexV525 how to fix for android?


#136 document4j not working with WSH version 5.8

document4j not working with WSH version 5.8

Hello @raphw, @deepak-csols, this PR seems wrong and needed to be rolled back.
The MS official documentation of GetObject function reads:

Syntax
GetObject([ pathname ], [ class ])

If pathname is a zero-length string (""), GetObject returns a new object instance of the specified type. If the pathname argument is omitted, GetObject returns a currently active object of the specified type.

In three occurrences of GetObject function where this PR modifies, we all want to find an existing currently running MS Word instance. In fact, this PR causes word_shutdown.vbs not actually work because it would create a new instance and quit the new one then, however, we should quit the existing instance instead. As a result of failing cleanup, we may end up with many winword.exe zombie processes.


Update the inmanta export command for resourceSet (#4316)

Pull request opened by the merge tool on behalf of #4316

Merged into branches iso5 in bb293992c22a55845e6cfc3936384a7578af167c


Allow extra context for errors

Description
Currently faro.api.pushError() only accepts and Error argument, there is no way to add extra context data.
One significant use case would be capturing React error boundary errors, where in addition to the regular stack trace
there is the component stack trace. It would be great to be able to add is as extra information.
Proposed solution
Add optional context parameter, same as for faro.api.pushLog(). Will require changes for recevier too
Context

### Tasks
- [x] web-sdk update
- [x] agent update
- [ ] receiver update

PR Web-SDK update
PR Agent update
PR Receiver update


#45 Add --version option for helm install exec command

Added the --version option to generate flags and options for the helm install exec command, this patch covered #45 issue.

Thanks!


Connection timeout while trying to get images

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing 😞


example-cnf | Include reduced mode in testpmd

SUMMARY
In example-cnf's testpmd, if setting a flag in testpmd execution, reduced mode will be used, where only the 2nd core and its sibling is used, also rxd and txd parameters are doubled in that case.
ISSUE TYPE
Enhanced Feature
Tests

[x] Example-cnf execution with current parameters (not using reduced mode) - https://www.distributed-ci.io/jobs/d9f3a7ca-e7fa-425a-82f8-b7cd4fee3165/jobStates
[x] Example-cnf execution with modified parameters (using reduced mode) - https://www.distributed-ci.io/jobs/99437c94-a6e5-438e-aab8-b50d1bdf85d8/jobStates

Test-Hints: no-check
build-depends: https://github.com/openshift-kni/example-cnf/pull/109
Testing with:
dci-pipeline-check https://github.com/redhatci/ansible-collection-redhatci-ocp/pull/514 /home/dciteam/clusterconfigs-cluster4/kubeconfig example-cnf example-cnf:ansible_extravars=dci_teardown_on_success:true example-cnf:ansible_extravars=dci_teardown_on_failure:true example-cnf:ansible_extravars=check_workload_api:false example-cnf:ansible_extravars=do_certsuite:false example-cnf:ansible_extravars=certify_operators:false example-cnf:ansible_extravars=tests_to_verify:[]

Testing is finished, ready for review.


boot2docker init error

boot2docker-1.8.1
Booting Core 6.3
Running Linux Kernel 4.0.9-boot2docker.
Checking boot options... Done.
...
/etc/init.d/tc-config: line 615: /etc/init.d/dhcp.sh: not found
Running boot2docker init script...
net.ipv4.ip_forward = 1
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: setting key "cannot stat %s": No such file or directory
sysctl: "cannot stat %s" is an unknown key
sysctl: setting key "cannot stat %s": No such file or directory
Segmentation fault
automount ...
b2docker-181.png

@alanyih are you on Windows ?

I'm facing the same problem and I'm on Windows 7.

Same issue here. Ran docker many times on Oracle Virtualbox and created default machine many times successfully. After single try to recreate it with disk size of 30GB I've started to get that issue.
After machine startup, the 'docker' daemon is not working in such state (even in VM shell).
Tried different things with host-only adapter settings (with/without DHCP) but without success.
The machine only starts by manual docker-machine create command.
Running by Docker Quickstart when machine not exists causes:
Creating Machine default...
Running pre-create checks...
Creating machine...
Error creating machine: Error in driver during machine creation: Maximum number of retries (5) exceeded
Looks like something went wrong... Press any key to continue...

The Kitematic was able to create machine but end up in error (unfortunatelly I did not grabbed it), and clicking button to remove and set up machine again fixed the problem, But stil I need to create VM by myself (proxy setting in docker-machine create) so I cannot use machine created by Kitematic.
It looks like Kitematic creates Host-only adapter WITH DHCP enabled and this can be the fix.
But even when I create VM manually and select it to use Host-only adapter with DHCP enabled, the error still occurs and docker daemon don't start up.
To sum up:

cannot even start quickstart console, it cannot create VM
Kitematic can create boot2docker VM but I need proxy setting (I will try to add to /var/lib/boot2docker/profile maually)
manually invoking docker-machine create can create a machine but error still occurs at startup and docker daemon is not running

It looks like using Host-only adapter with DHCP enabled BREAKS starting docker daemon after second VM startup. Disabling DHCP solved the problem.

I have the same error in boot2docker.log when I tried to use docker-machine to create a new vm in vsphere. The created vm has no ipv4 address assigned on eth0 thus failed to ssh.
@communityportal I have no idea about the "disabling DHCP" thing, could you help elaborate it more?


Export-DbaLogin - Update for multiple instances

…ting

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[x] New feature (non-breaking change, adds functionality)
[X] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[X] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Update the Export-DbaLogin command to be able to properly handle multiple instances
Standardize the parameters to match with Export-DbaScript
Standardize handling of BatchSeparator as per #5514
Standardize date format used on output filenames to use a configuration
Approach
Added code to generate a Instance specific file when more than 1 instance is input
Added additional parameters like NoPrefix, Passthru and Encoding to align with Export-DbaScript
Commands to test
Export-DbaLogin

fantastic, ty! 🙇


[CI Problem] Flaky segfault test_ethosn/test_addition.py::test_addition

Happening quite frequently
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-9882/2/pipeline
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-9892/3
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-9892/1/pipeline
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-9832/1/pipeline
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-9896
@Leo-arm @leandron @Mousius

This one is also from ethosn but different kind of failure std: :bad_alloc
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-9892/2/pipeline/268

This could be due to https://github.com/apache/tvm/issues/9705

I looked through the latest patch, the update to a more recent version of the Ethos-N driver stack and I don't see anything that I would worry about. I also ran everything locally in image 80 and it is not failing for me, so for the moment I am thinking it is a disk space issue.

@masahi I think we can close this one as it does not seem to occur any more.

Yeah agreed, thanks @Leo-arm


A problem about the dataset

Hello, is the cptc data set in this experiment under this link? I wonder which of these files should I download? Just like the sample-input.json you gave. Thanks very much!
http://mirror.rit.edu/cptc/2018/t5/

Hello, the CPTC-2018 dataset in the link is correct, however this is only for team 5. In the experiments, we use all teams (which you can find in the parent directory) and we only use suricata alerts (suricata_alert.json). So, essentially, you will get six files: suricata_alert_t1.json, suricata_alert_t2.json, suricata_alert_t5.json, suricata_alert_t7.json, suricata_alert_t8.json, suricata_alert_t9.json.

Regarding your second question, which paper do you mean exactly? If you refer to the main paper "Alert-Driven Attack Graph Generation Using S-PDFA", then Figure 6 also has the 70#1 format (see below, showing only a fragment, so that the state names and transitions are also visible):

Note that the figure above shows the entire S-PDFA (i.e. red + blue + white states), while the image that you get does not include white sinks (since they are printed in a separate file, i.e. you have files expName.txt.ff.final.json and expName.txt.ff.finalsinks.json).
The reason that the states have 70#1 format is that this is the format used by FlexFringe.
So, I don't see any problem with your experiments. Does that answer your question? If not, feel free to send another comment.

Regarding your second question, which paper do you mean exactly? If you refer to the main paper "Alert-Driven Attack Graph Generation Using S-PDFA", then Figure 6 also has the 70#1 format (see below, showing only a fragment, so that the state names and transitions are also visible):
Note that the figure above shows the entire S-PDFA (i.e. red + blue + white states), while the image that you get does not include white sinks (since they are printed in a separate file, i.e. you have files expName.txt.ff.final.json and expName.txt.ff.finalsinks.json).
The reason that the states have 70#1 format is that this is the format used by FlexFringe.
So, I don't see any problem with your experiments. Does that answer your question? If not, feel free to send another comment.

Thank you very much for your answer. I have no further questions,currently. Thank you very much. It has been very useful to me

Hi @hexing2333, I will just add that the reason your model looks different is because FlexFringe is constantly getting updated, e.g., when we developed SAGE in 2021, the S-PDFA model never had any colored states (we add colors in SAGE to denote severity). Since the FlexFringe tool uses the red-blue state merging (you can read more about it in the flexfringe paper), now the core states in the model are colored red. I understand it makes it difficult to reproduce the paper's results. If that is indeed what you are after, I can share an older .exe file for FlexFringe that you can use to get the same model, though there are no guarantees that it would still work.

I see. Thank you very much for your reply. I will carefully read the relevant libraries and papers of FlexFringe again. And if quite convenient, I hope to get an old version .exe of FlexFringe. Here is my email address, @.*** Thank you very much for your reply!
---Original---
From: "Azqa @.>
Date: Fri, Sep 15, 2023 21:54 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [tudelft-cda-lab/SAGE] A problem about the dataset (Issue #45)
Hi @hexing2333, I will just add that the reason your model looks different is because FlexFringe is constantly getting updated, e.g., when we developed SAGE in 2021, the S-PDFA model never had any colored states (we add colors in SAGE to denote severity). Since the FlexFringe tool uses the red-blue state merging (you can read more about it in the flexfringe paper), now the core states in the model are colored red. I understand it makes it difficult to reproduce the paper's results. If that is indeed what you are after, I can share an older .exe file for FlexFringe that you can use to get the same model, though there are no guarantees that it would still work.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Problem with plants and Yellorite ore

I am on MC 1.12.1 and I have a strange issue when I try to harvest a plant. All plants are transformed to "blue orchid" after harvesting. I can reproduce it with Minecraft Plants and the latest plants mod (https://minecraft.curseforge.com/projects/plants?gameCategorySlug=mc-mods&projectID=257229)
Plants from biomes o plenty and Pams Harvestcraft don't seem to be affected.
I also discovered, that yellorite ore from extrem reactors is transformed if put in a furnace to uranium ingot from Immersive Engineering. If i throw yellorite ore in a pulverizer and get yellorium dust, i can smelt it to yellorium ingot as it is supposed to be.
https://imgur.com/a/PNw4y

the problem with flower is that the plants mod registers every flower in oredictionary. you can solve the problem by adding plant to the blacklist in config file.
the second one is not my fault. I don't change any furnace or pulverizer recipes.

Yeah the same thing happens with workbenches from tinkers and cyclic.
I think there should be a whitelist by default and not just swap everything that isn't on the blacklist...especially since you can't change the config in game.  Makes for finding problems with large mod packs a pain.

Can you tell me where exactly I have to put the "plants".
I edited the instantunify.cfg on my server and tried adding plant in the S:blacklist array for OreDict names that shouldn't be unified.
Or do you mean to blacklist the plants mod in row 5 ? How do I blacklist the minecraft plants? The show this behaviour, too.

do you use the new version? If so, you should delete the config file.
the new version uses a whitelist instead

I installed the newest version on my server, deleted the config file and restarted it.
The problem still persists, this is the .conf file, that was generated.
Configuration file
general {
# Blacklisted Mods [default: ]
S:blacklistMods <
>
# Preferred Mods [default: [thermalfoundation], [immersiveengineering], [embers]]
S:preferredMods <
    thermalfoundation
    immersiveengineering
    embers
 >

# Use UniDict's favorite ores to unify. [default: true]
B:useUnidict=true

}
list {
# OreDict names that shouldn't be unified. (supports regex) [default: [.Wood], [.Glass], [stair.], [fence.], [plank.], [slab.]]
S:blacklist <
.Wood
.Glass
stair.
fence.
plank.*
slab.*
>
# true - use whitelist
# false - use blacklist [default: true]
B:useWhitelist=true

# OreDict names that should be unified. (supports regex) [default: [block.*], [chunk.*], [dust.*], [dustSmall.*], [dustTiny.*], [gear.*], [gem.*], [ingot.*], [nugget.*], [ore.*], [plate.*], [rod.*]]
S:whitelist <
    block.*
    chunk.*
    dust.*
    dustSmall.*
    dustTiny.*
    gear.*
    gem.*
    ingot.*
    nugget.*
    ore.*
    plate.*
    rod.*
 >

}
unifyevent {
# Unify when items drop. [default: true]
B:drop=true
# Unify when GUI is opened/closed. [default: true]
B:gui=true

# Unify when blocks are harvested. [default: true]
B:harvest=true

# Unify every second items in player's inventory. [default: false]
B:second=false

}

Here it is in a pastebin:
https://pastebin.com/zCxLXcd9

so what's the problem? the whitelist is used by default (see B:useWhitelist=true).
therefore plants won't be unified anymore.
to add plants to the blacklist just add it like this.

wait, I'm an idiot

fixed in 1.0.4

I can confirm, it works! Thanks for your work!


Where is the abstractions about futures_sink like futures_util::SinkExt?

Sink was a mistake, so it's not included in this repo.

Yet another mistake. Removing legacy is definitely a good thing, but where is the alternative? How can I use async_tungstenite::WebSocketStream to send messages? If API need to redesign, then where is the more correct interface that can do similar thing?

Generally I hope that there will be a compatibility/adapting/legacy list, listing all of the APIs in futures series crate (maybe also all of Tokio API for the entire Smol project), explaining if there is a drop-in alternative, or an alternative with what differences, or this is a legacy API with trap or footgun and use another API or way to implement it, or the alternative API has not yet been implemented. Or people will get frustrated trying to transfer previous practices to the new system, preventing it from further evolving.

I agree with the idea of such a list.

Closing this as "not planned" now that it's official policy to not support Sink.


add rollout status in app api

What type of PR is this?
/kind api-change
What this PR does / why we need it:
add rollout status in application api

@hzxuzhonghu


HIVE-26434: Fix HMS thrift method recv_get_table_objects_by_name's exception list

What changes were proposed in this pull request?

Fix HMS thrift method recv_get_table_objects_by_name's exception list
Why are the changes needed?

HIVE-15062 accidentally removed the HMS thrift method recv_get_table_objects_by_name exception list, after HIVE-24608, some IT consistently failed because of that.
e.g. org.apache.hive.metastore.TestSetUGIOnOnlyClient#testSimpleTable
org.apache.thrift.TApplicationException: Internal error processing get_table_objects_by_name
 at org.apache.thrift.TApplicationException.read(TApplicationException.java:111)
 at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:79)
 at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Client.recv_get_table_objects_by_name(ThriftHiveMetastore.java:1544)
 at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Client.get_table_objects_by_name(ThriftHiveMetastore.java:1530)
 at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.getTableObjectsByName(HiveMetaStoreClient.java:1363)
 at org.apache.hadoop.hive.metastore.TestHiveMetaStore.testSimpleTable(TestHiveMetaStore.java:1478)

This PR should recover some ITs of branch-2.3
Does this PR introduce any user-facing change?

Yes, w/ this patch, the thrift exception can be propagated from hms to client correctly.
How was this patch tested?

Existing UT

cc @sunchao @wangyum
BTW, I checked the spark does not affect by this issue, because use catches all exceptions thrown by the recv_get_table_objects_by_name
https://github.com/apache/spark/blob/47f0303944abb11d3018186bc125113772eff8ef/sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala#L410-L419

The Jenkins report[1] shows this PR recovers ~60 tests compared to latest branch-2.3[2]
[1] http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-3483/1/tests
[2] http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/branch-2.3/26/tests/

Thanks, merged


"comparison of Float with NaN failed"...and GSL is Installed

While trying to fix an unrelated issue, I experimented with the code from #5, but using ZombieWriter::MachineLearning rather than ZombieWriter::Randomization.

zombie = ZombieWriter::MachineLearning.new

zombie.add_string(content: "This is filler text that I invented.This is also a paragraph that could be used")
zombie.add_string(content: "This post is amazing. Please take a look")
zombie.add_string(content: "For all sports fan, you must watch this video. Hey you have to check this out.")

array = zombie.generate_articles

p array

#/Users/tariqali/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/kmeans-clusterer-0.11.4/lib/kmeans-clusterer.rb:237:in `sort_by': comparison of Float with NaN failed (ArgumentError)

The culprit is the third string. Classifier-Reborn classified its lsi_norm as a vector of NaNs...
 "For all sports fan, you must watch this video. Hey you have to check this out.\n"=>
  #<ClassifierReborn::ContentNode:0x007fdec4b25ae8
   @categories=[],
   @lsi_norm=GSL::Vector
[   nan   nan   nan   nan   nan   nan   nan ... ],
   @lsi_vector=GSL::Vector
[ 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 ... ],
   @raw_norm=GSL::Vector
[ 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 ... ],
   @raw_vector=GSL::Vector
[ 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 ... ],
   @word_hash={:for=>1, :sport=>1, :fan=>1, :must=>1, :watch=>1, :video=>1, :hei=>1, :check=>1, :out=>1}>}

Changing the third string slightly resolves the issue.
zombie = ZombieWriter::MachineLearning.new

zombie.add_string(content: "This is filler text that I invented.This is also a paragraph that could be used")
zombie.add_string(content: "This post is amazing. Please take a look")
zombie.add_string(content: "For all sports fan, you must watch this video. Hey you have to check this out. Filler, filler, filler.")

array = zombie.generate_articles

p array

 "For all sports fan, you must watch this video. Hey you have to check this out. Filler, filler, filler.\n"=>
  #<ClassifierReborn::ContentNode:0x007fd931432fd0
   @categories=[],
   @lsi_norm=GSL::Vector
[ 6.205e-01 1.432e-01 1.432e-01 1.432e-01 1.432e-01 1.432e-01 0.000e+00 ... ],
   @lsi_vector=GSL::Vector
[ 6.593e-01 1.522e-01 1.522e-01 1.522e-01 1.522e-01 1.522e-01 0.000e+00 ... ],
   @raw_norm=GSL::Vector
[ 5.547e-01 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 ... ],
   @raw_vector=GSL::Vector
[ 6.272e-01 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 0.000e+00 ... ],
   @word_hash={:for=>1, :sport=>1, :fan=>1, :must=>1, :watch=>1, :video=>1, :hei=>1, :check=>1, :out=>1, :filler=>3}>}

But why? Both scenarios appeared to have a @word_hash, so it isn't quite clear why one string had a vector of NaNs and the other one doesn't. Is it because in the second scenario, the third string had words that were similar to that of the first string? I will have to research this issue more carefully and decide how to gracefully handle this potential error.
This problem is probably not likely to happen in the real-world...if you add long passages to ZombieWriter, there's bound to be a few overlaps of words that classifier-reborn can detect. But it could happen...which is why I need to figure out how to fix it.

same problem here. hope to see an answer


Feat: Add logging with reasons for not enriching a connection

Description

change me!
User-facing documentation

[ ] CHANGELOG is updated OR update is not needed
[ ] documentation PR is created and is linked above OR is not needed

Testing and quality

[ ] the change is production ready: the change is GA or otherwise the functionality is gated by a feature flag
[ ] CI results are inspected

Automated testing

[ ] added unit tests
[ ] added e2e tests
[ ] added regression tests
[ ] added compatibility tests
[ ] modified existing tests

How I validated my change

change me!

Sorry, messed up something during rebase - here a clean one https://github.com/stackrox/stackrox/pull/13463


Setting a Color's hue to 1.0 gives the wrong hue.

If you set the hue of a Color to 1.0, it results in the wrong hue: instead of a deep red, you get a purple. This occurs both when using the Color.h property, and when setting the hue via the color picker. 0.9999999 and 0 both appear to have correct results.

@MarianoGnu Want to have a look?


Implement OpenVDB support

Currently Cycles mainline doesn't support OpenVDB, however there was a Google Summer of Code in 2018 in which it has been implemented, however no one has merged it quite yet.
https://developer.blender.org/rB9f4e5581d18899d665d61e93ae7c6933c5a3e770
I have a test branch of this here:
https://github.com/boberfly/cycles/tree/vdbTest
There was some patching to do and I discarded the blender addon code as it was for 2.8 and Cycles standalone still targets 2.79, but this is not needed for the purposes of GafferCycles.

Progress

Still can't seem to make it actually render past the bounds here (I believe Cycles creates an outer geometry layer for optimisation, this is what is seen here afaik).

A few issues with the GSoC 2018 patch:

the built-in volume re-mesher for optimisation likes to run each time there's a simple change to the scene, hopefully we can fix this in Cycles code.
This is quarter res wdas_cloud.vdb and using the full res one the time to first pixel is crazy, maybe we can just get OpenVDB to generate the mesh instead.
Increasing density looks like the isovalue of the mesh needs to be increased with this adjustment, otherwise the outer optimisation mesh is apparent and the voxels can be seen...
Cuda/OpenCL devices aren't working yet

Closing this as VDB volumes have been implemented in Cycles mainline and render in GafferCycles.


Inconsistent pricing from homepage to product page

I have a product with two variants, each with a different price.
Product price: $12.34
Variant A price: $13.57
Variant B price: $12.34
The price shown on my homepage will be $12.34 but, when I click on the product, I will see a default of $13.57 on the product page, which is confusing for the buyer. There are a few different ways we could go with this.

Allow for arrangement of the variants so that the seller has control over the sorting when they're displayed. This isn't really the proper fix for the pricing confusion, but it has its own merits anyway.
Show a range of prices on the index page. This might end up producing messier UI.
Default to no selection on the product page. It would be clearer if the buyer was forced to make a selection.

Related to this, it's possible for the seller to inadvertently set variant prices that don't match the product price at all. Perhaps the "product price" should be disabled if the variant price fields are used or if variants exist at all.

Closing as duplicate of #409 .