Win-Arm64 not packaged correctly in Nuspec

Describe the bug
The nupkg from Nuget installs the x64 binary on arm64, using latest 2.12.3363.
To Reproduce
Steps to reproduce the behavior:

dotnet new console
dotnet add package uplink.NET.Win
dotnet add package uplink.NET.Linux
dotnet build -r win-arm64
dotnet build -r linux-x64
In the publish folder, the Windows x64 storj_uplink.dll is installed for both win-arm64 and linux-x64.

Expected behavior
The package should only install the relevant files.
The same problem occurs when including the Windows+Linux package and targeting Linux.
Additional context
Looking inside the nupkg, it has the correct files, but the build process appears to be picking up the wrong version for some reason.
Console session showing the included files:
> shasum uplink.net.win.2.12.3363.nupkg/runtimes/win-x64/native/storj_uplink.dll
8c9f069cc657f16787347d1f916a67f756aedbd9  uplink.net.win.2.12.3363.nupkg/runtimes/win-x64/native/storj_uplink.dll

> shasum uplink.net.win.2.12.3363.nupkg/runtimes/win-x86/native/storj_uplink.dll
ba10f3492ea1e5c838a08a129fc951e3d5060716  uplink.net.win.2.12.3363.nupkg/runtimes/win-x86/native/storj_uplink.dll

> shasum uplink.net.win.2.12.3363.nupkg/runtimes/win-arm64/native/storj_uplink.dll
6ff71d75099f12ebf98c8ff5383f1af5fd0e5e13  uplink.net.win.2.12.3363.nupkg/runtimes/win-arm64/native/storj_uplink.dll

> shasum test-project/publish/linux-arm64-gui/storj_uplink.dll
8c9f069cc657f16787347d1f916a67f756aedbd9  test-project/linux-arm64-gui/storj_uplink.dll

> shasum test-project/publish/linux-x64-gui/storj_uplink.dll
8c9f069cc657f16787347d1f916a67f756aedbd9  test-project/linux-x64-gui/storj_uplink.dll

> shasum test-project/publish/linux-x64-gui/storj_uplink.so
3998df8c86149d31d249728d85f3a26b4d118fac  test-project/linux-x64-gui/storj_uplink.so

> shasum test-project/publish/win-arm64-gui/storj_uplink.dll
8c9f069cc657f16787347d1f916a67f756aedbd9  test-project/win-arm64-gui/storj_uplink.dll

> file test-project/publish/win-arm64-gui/storj_uplink.dll
test-project/win-arm64-gui/storj_uplink.dll: PE32+ executable (DLL) (console) x86-64 (stripped to external PDB), for MS Windows

> file test-project/publish/win-x64-gui/storj_uplink.dll
test-project/win-arm64-gui/storj_uplink.dll: PE32+ executable (DLL) (console) x86-64 (stripped to external PDB), for MS Windows

> file uplink.net.win.2.12.3363.nupkg/runtimes/win-arm64/native/storj_uplink.dll
uplink.net.win.2.12.3363.nupkg/runtimes/win-arm64/native/storj_uplink.dll: PE32+ executable (DLL) (GUI) Aarch64, for MS Windows

> ls test-project/linux-x64-gui/storj_uplink.*
test-project/linux-x64-gui/storj_uplink.dll
test-project/linux-x64-gui/storj_uplink.so

> file test-project/publish/win-x64-gui/storj_uplink.dll
test-project/win-arm64-gui/storj_uplink.dll: PE32+ executable (DLL) (console) x86-64 (stripped to external PDB), for MS Windows

> file test-project/publish/win-x64-gui/storj_uplink.so
test-project/win-arm64-gui/storj_uplink.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=551f4f30f0fe83233ff6da071cfa448ef246ae6e, with debug_info, not stripped

My project file:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net8.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="uplink.NET.Linux" Version="2.12.3365" />
    <PackageReference Include="uplink.NET.Win" Version="2.12.3363" />
  </ItemGroup>

</Project>

I see a warning during build:
/Users/kenneth/Downloads/test-storj/test-storj.csproj : warning NU1701: Package 'uplink.NET.Win 2.12.3363' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net8.0'. This package may not be fully compatible with your project.

I am guessing that it somehow triggers the target file which overrides the normal target selection.

Thanks @kenkendk for this issue and your feedback! I'm in a personal war against nuspec and target-file. 🤣🙈 I do not really know what I could/would have to change here. The whole nuget/nuspec-thing feels so unnecessary complex.
I'll try to find a more stable way for the packages. If you have any idea how to do it better, let me know! Basically it is just "place the {platform-binary} in the output dir" for all supported platforms.

@TopperDEL Ha! I am not well versed in the MSBuild scripts either, but I think at least part of the problem is that the conditions look at the operating system running MSBuild, not the target:

The System.OperatingSystem property functions return information about the operating system on which MSBuild is running. For example, if your project targets Linux and you build it on macOS, the property functions will return information about macOS.

So it would work for developing, except the lack of the Win-Arm64 condition.
But when building for another operating system, it will fail.
The best answer I can find is this SO thread that mentions using: Condition="'$(RuntimeIdentifier)' == 'linux-arm'".
In my own packages with multi-arch binaries, I do not have the target file at all, and then it appears to work as expected, just placing the targets in the correct runtime folders.
I think that for .NET5+ you no longer need the build targets.

A related note, on Mac, I can see that the library is built with both x64 + arm64, but somehow it does not get installed on Arm64.
csproj:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net8.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="uplink.NET.Linux" Version="2.12.3365" />
    <PackageReference Include="uplink.NET.Win" Version="2.12.3363" />
    <PackageReference Include="uplink.NET.Mac" Version="2.12.3363" />
  </ItemGroup>

</Project>

Running:
dotnet publish -r osx-x64
dotnet publish -r osx-arm64

Places the libstorj_uplink.dylib only in the x64 output.
That does not seem to have anything to do with the target file, but follow the copy conventions where the file is only copied to x64.
An additional note: I do not get warnings about the package target version when building, except when I include the uplink.NET.Win package.

So, I'm a little step further.
There should now be ARM and ARM64-builds for Linux which should fix this issue. Haven't tried it yet, though.
Also the package should now deploy x64 and arm64 on MacOs correctly. We're still not done yet as Windows still might deploy the wrong binary for arm64.

So now the prerelease-version of the packages should support:

Win-x86, Win-x64, Win-arm64
Linux-x64, Linux-arm, Linux-arm64
osx-x64, osx-arm64

Finally it seems I got them all! :)
The warnings about the package target version are gone now, too. I think that uplink.NET does not really support .NetFramework anymore - but I think this is neglectable.

Issue should be resolved with the version 2.13.* Closing it.

@TopperDEL I have tested it, and it almost works, but I think you have packaged the wrong binaries in the nupkg:
> shasum uplink.net.linux.2.13.3448/runtimes/linux-*/native/storj_uplink.so
5a56a5bf5ca48156bee579b706c7a4e0ef7c8353  uplink.net.linux.2.13.3448/runtimes/linux-arm/native/storj_uplink.so
5a56a5bf5ca48156bee579b706c7a4e0ef7c8353  uplink.net.linux.2.13.3448/runtimes/linux-arm64/native/storj_uplink.so
5a56a5bf5ca48156bee579b706c7a4e0ef7c8353  uplink.net.linux.2.13.3448/runtimes/linux-x64/native/storj_uplink.so

All 3 variants have the same binary, and it looks like the x64 variant:
> file uplink.net.linux.2.13.3448/runtimes/linux-*/native/storj_uplink.so
uplink.net.linux.2.13.3448/runtimes/linux-arm/native/storj_uplink.so:   ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=b242b27943bce2a7cb5e3462a840bc34efd46009, with debug_info, not stripped
uplink.net.linux.2.13.3448/runtimes/linux-arm64/native/storj_uplink.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=b242b27943bce2a7cb5e3462a840bc34efd46009, with debug_info, not stripped
uplink.net.linux.2.13.3448/runtimes/linux-x64/native/storj_uplink.so:   ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=b242b27943bce2a7cb5e3462a840bc34efd46009, with debug_info, not stripped

All the versions in .Win and .Mac seems to be correct, so I think it is just the packaging that has picked up the wrong binaries.

Thanks for the finding, @kenkendk!
I was concentrated on the correct pathing but did not realize, that the build itself was not respecting the target-architecture. I fixed this with some trial and error. Version 2.13.3484 should be fine now!


Shallow needs a facelift.

Getting complaints about his looks.

Here's the prompt I used in midjourney:
/imagine character avatar portrait, expressive cat robot, wearing headphones and techwear, blue and white colour scheme, illustration --s 750 --v 5.1
Here's a short bio:
Shappie // Grumpy Cyberpunk Discord Catbot
Shappie is an annoyed cyber cat living in the discord server attic. They'll begrudgingly give you what you need, adding a healthy serving of snark on the side. While reluctant to say so on a whim, they're hoping for your success and will put in the work to see things through.


Automatic lifting of distributions

The following definition for normal:
normal(μ, σ, ωid::Id, ω::Omega) = quantile(Normal(μ, σ), ω[ωid])
normal(μ::T, σ::T, ωid::Int=ωnew()) where T = RandVar{T, true}(normal, (μ, σ, ωid))
normal(μ::AbstractRandVar{T}, σ::T, ωid::Int=ωnew()) where T = RandVar{T, true}(normal, (μ, σ, ωid))
normal(μ::T, σ::AbstractRandVar{T}, ωid::Int=ωnew()) where T = RandVar{T, true}(normal, (μ, σ, ωid))
normal(μ::AbstractRandVar{T}, σ::AbstractRandVar{T}, ωid::Int=ωnew()) where T = RandVar{T, true}(normal, (μ, σ, ωid))

Is problematic because
(i) lots of repetition
(ii) the types might be incorrect, e.g. you could do normal(1, 1) and it would give you a Randvar{Int}

Fixed alot of duplication with  MaybeRV{T} = Union{T, AbstractRandVar{T}} where T.
Would be nice to be able to do just
normal(ω::Omega, μ, σ) = rand(ω, Normal(μ, σ))
liftrv(normal)

But:

normal is method, which one are we talking about.  Look at all methods with omega as first arg?
return type could depend on mu or sigma

Done! iid


chore: add more logging to SM notifier

Rebasing to include https://github.com/fedimint/fedimint/pull/4005 should fix CI


Check for July Updates

The Windows July updates appear to be causing more issues and we should add a check into the script to address this ASAP.
https://blogs.technet.microsoft.com/exchange/2018/07/16/issue-with-july-updates-for-windows-on-an-exchange-server/
Based off what i am reading, i should be able to check to see if the OS is on a particular build number then flag it.

Commit bce37167cee5e58eab02a724e9bf8e6b9866563e is what is going to be merged into the master branch. The logic in the other commit wouldn't have worked.


Unrecognized option "form"  under "twig"

Hi,
I installed the bundle, but I am not able to install assets and fetch vendor. I get "Unrecognized option "form"  under "twig"".
When I try to run website I've got same error.
InvalidConfigurationException in ArrayNode.php line 314:
Unrecognized option "form" under "twig"
Using Symfony 3, can it be the problem?

Same issue for me with Symfony3

That's due to some changes in the twig bundle. An Update to 1.3.4 should resolve this issue.

Confirmed, 1.3.4 fixed this for me. Thanks @avanzu

Hi,
I'm getting the following error because using Symfony 2.3 :
  [Symfony\Component\Config\Definition\Exception\InvalidConfigurationException]
  Unrecognized options "form_theme" under "twig"

Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache handling the post-update-cmd event terminated with an exception

  [RuntimeException]
  An error occurred when executing the "'cache:clear --no-warmup'" command.

How am I supposed to manage this ? I forced avanzu/admin-theme-bundle:1.3.3 but this won't do for long...
Im' planning to upgrade to Symfony 2.8 soon but in the meantime, I still need to make my back office work ;)

@avanzu I'm enable to update to the specified version due to a conflict with nelmio doc bundle, here is my composer command output :

php composer.phar require twig/twig:1.3.*@dev
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- twig/twig 1.3.0 conflicts with nelmio/api-doc-bundle[2.11.2].
- nelmio/api-doc-bundle 2.11.2 conflicts with twig/twig[1.3.0].
- twig/twig 1.3.0 conflicts with nelmio/api-doc-bundle[2.11.2].
- Installation request for twig/twig 1.3.*@dev -> satisfiable by twig/twig[1.3.0].
- Installation request for nelmio/api-doc-bundle == <IP_ADDRESS> -> satisfiable by nelmio/api-doc-bundle[2.11.2].
Installation failed, reverting ./composer.json to its original content.

any help to avoid the error "Unrecognized option "form" under "twig" " ?
thank you.
NB: this is my composer info details:

php composer.phar info
cocur/slugify                            v1.4.1                                Converts a string into a slug.
doctrine/annotations                     v1.2.7                                Docblock Annotations Parser
doctrine/cache                           v1.6.0                                Caching library offering an object-oriented API for many cache backends
doctrine/collections                     v1.3.0                                Collections Abstraction library
doctrine/common                          v2.6.1                                Common Library for Doctrine projects
doctrine/dbal                            v2.5.4                                Database Abstraction Layer
doctrine/doctrine-bundle                 1.6.2                                 Symfony DoctrineBundle
doctrine/doctrine-cache-bundle           1.3.0                                 Symfony Bundle for Doctrine Cache
doctrine/inflector                       v1.1.0                                Common String Manipulations with regard to casing and singular/plural rules.
doctrine/instantiator                    1.0.5                                 A small, lightweight utility to instantiate objects in PHP without invoking their constructors
doctrine/lexer                           v1.0.1                                Base library for a lexer that can be used in Top-Down, Recursive Descent Parsers.
doctrine/orm                             v2.5.4                                Object-Relational-Mapper for PHP
friendsofsymfony/rest-bundle             1.7.7                                 This Bundle provides various tools to rapidly develop RESTful API's with Symfony
friendsofsymfony/user-bundle             dev-master 88f84f6                    Symfony FOSUserBundle
incenteev/composer-parameter-handler     v2.1.2                                Composer script handling your ignored parameter file
jdorn/sql-formatter                      v1.2.17                               a PHP SQL highlighting library
jms/metadata                             1.5.1                                 Class/method/property metadata management in PHP
jms/parser-lib                           1.0.0                                 A library for easily creating recursive-descent parsers.
jms/serializer                           1.1.0                                 Library for (de-)serializing data of any complexity; supports XML, JSON, and YAML.
jms/serializer-bundle                    1.1.0                                 Allows you to easily serialize, and deserialize data of any complexity
knplabs/knp-menu                         v2.1.1                                An object oriented menu library
knplabs/knp-menu-bundle                  v2.1.1                                This bundle provides an integration of the KnpMenu library
michelf/php-markdown                     1.6.0                                 PHP Markdown
monolog/monolog                          1.18.0                                Sends your logs to files, sockets, inboxes, databases and various web services
nelmio/api-doc-bundle                    2.11.2                                Generates documentation for your REST API from annotations
paragonie/random_compat                  v1.2.1                                PHP 5.x polyfill for random_bytes() and random_int() from PHP 7
phpcollection/phpcollection              0.4.0                                 General-Purpose Collection Library for PHP
phpoption/phpoption                      1.5.0                                 Option Type for PHP
psr/log                                  1.0.0                                 Common interface for logging libraries
sensio/distribution-bundle               v5.0.4                                Base bundle for Symfony Distributions
sensio/framework-extra-bundle            v3.0.14                               This bundle provides a way to configure your controllers with annotations
sensio/generator-bundle                  v3.0.6                                This bundle generates code for you
sensiolabs/security-checker              v3.0.2                                A security checker for your composer.lock
sonata-project/admin-bundle              dev-master 04c1e81                    Symfony SonataAdminBundle
sonata-project/block-bundle              2.3.9                                 Symfony SonataBlockBundle
sonata-project/cache                     1.0.7                                 Cache library
sonata-project/core-bundle               2.3.10                                Symfony SonataCoreBundle
sonata-project/datagrid-bundle           2.2                                   Symfony SonataDatagridBundle
sonata-project/doctrine-extensions       1.0.2                                 Doctrine2 behavioral extensions
sonata-project/doctrine-orm-admin-bundle dev-master e8eb83f                    Symfony Sonata / Integrate Doctrine ORM into the SonataAdminBundle
sonata-project/easy-extends-bundle       2.1.10                                Symfony SonataEasyExtendsBundle
sonata-project/exporter                  1.4.1                                 Lightweight Exporter library
sonata-project/google-authenticator      1.0.2                                 Library to integrate Google Authenticator into a PHP project
sonata-project/user-bundle               dev-add_support_for_fos_user2 e119e8e Symfony SonataUserBundle
swiftmailer/swiftmailer                  v5.4.1                                Swiftmailer, free feature-rich PHP mailer
symfony/monolog-bundle                   v2.9.0                                Symfony MonologBundle
symfony/phpunit-bridge                   v3.0.3                                Symfony PHPUnit Bridge
symfony/polyfill-intl-icu                v1.1.0                                Symfony polyfill for intl's ICU-related data and classes
symfony/polyfill-mbstring                v1.1.0                                Symfony polyfill for the Mbstring extension
symfony/polyfill-php56                   v1.1.0                                Symfony polyfill backporting some PHP 5.6+ features to lower PHP versions
symfony/polyfill-php70                   v1.1.0                                Symfony polyfill backporting some PHP 7.0+ features to lower PHP versions
symfony/polyfill-util                    v1.1.0                                Symfony utilities for portability of PHP codes
symfony/security-acl                     v3.0.0                                Symfony Security Component - ACL (Access Control List)
symfony/swiftmailer-bundle               v2.3.11                               Symfony SwiftmailerBundle
symfony/symfony                          v3.0.3                                The Symfony PHP framework
twig/extensions                          v1.3.0                                Common additional features for Twig that do not directly belong in core
twig/twig                                v1.24.0                               Twig, the flexible, fast, and secure template language for PHP
willdurand/jsonp-callback-validator      v1.1.0                                JSONP callback validator.
willdurand/negotiation                   1.5.0                                 Content Negotiation tools for PHP provided as a standalone library.

I'm using sonata-project/admin-bundle 3.1.0 and I update to 3.3.0 but it does not solve the issue any help please

Did you Target the right Project?
Am Dienstag, 14. Juni 2016 schrieb MAPOUKA :

I'm using sonata-project/admin-bundle 3.1.0 and I update to 3.3.0 but it
does not solve the issue any help please
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/avanzu/AdminThemeBundle/issues/85#issuecomment-225937999,
or mute the thread
https://github.com/notifications/unsubscribe/AA8xexnhy2PknZ9D1P-HG9_bvDvUs1Qcks5qLtbVgaJpZM4G6DVn
.

@Mangetsu being unable to update to 1.3.4 and using Symfony >= 2.6,  one could try applying the AvanzuAdminThemeExtension.php patch in: 174fd34fba2eaf85344b5dec6a107fca6b135478.
@Saint-Cyr use this in config.yml for Symfony >= 2.6
twig:
  form_themes:
    - something.html.twig

instead of this:
twig:
  form:
    resources:
      - something.html.twig

Docs for the current TwigBundle configuration structure (old structure).

Sorry I'wase confuse a bit it suppose to be Sonata - project sorry !


fix: retain main activity state on rotation

used publish subject instead of behavior subject for bus
shifted initial page load logic on main activity start to main activity's onCreate
bus is not used to show header title any more

fixes #375

@iamareebjamal
have replaced behavior subject to publish subject. please test on a device. we may restore it with behavior subject again with #376. please review.

@mejariamol There's no point in changing something temporarily. What issue will it fix if it is PublishSubject?

Behavior subject is causing issue for rotation by re-emitting the last item to load dashboard forcefully, right?

I am just saying if we are using behavior subject then it should be used correctly.

Yes, that's why we should fix the behavior rather than changing it to PublishSubject. If we want to use PublishSubject, then fine. But then we must implement a solution to the problem we are facing in #364 if BehaviorSubject is not used. It will break on merging on this PR

But then we must implement a solution to the problem we are facing in #364 if BehaviorSubject is not used

will have to use stored event id and get the event from the repository to set to ticket.

Then what'd be the point of a bus?

For event click on events page.

That's not the use of bus. For that, we could even use action listeners. This is a workaround TBH, not a solution, so we should either complete the solution or else there'd be no point of the bus. I'll be thinking about the solution, meanwhile could you take up #353
These bugs can be solved later, as the app is working fine without them. Probably when the feature set s stable, we can take these up.

Handled in #389


JRD-95 Implement "string contains" approach for jaqket_v2 and jsquad

LLMs can sometimes provide correct answers but that may not be an exact match to the ground truth.
In order to account for this, in addition to the existing "exact match" approach, this PR adds a new "string contains" approach. For example, this is done by LINE corporation (https://logmi.jp/tech/articles/325454):

正解かどうかの判定は、出力結果の一部に正解が内包されているかどうかで判定しています。

Closing this for now as we decided that using the existing F1 instead of string contains is better, in order to penalize very long/redundant answers even if it's correct


Suggestion: add Scoop installation methods in Wiki

I added lua-language-server to Scoop (a package manager for Windows 10 & Windows 11), https://scoop.sh/#/apps?q=lua-language-server&s=2&d=1&o=true.
Here are the installation instructions:
scoop install lua-language-server

Added! Thanks! ❤


Permission interference in SSPP app log tool

Reported by Wendy: SSPP Program Manager role disables some permissions granted by the SSPP Unit Manager role.

https://github.com/gaepdit/iaip/blob/567c2531298b4def24e730a9d9bb5b667b923980/IAIP/SSPP/SSPPApplicationTrackingLog.vb#L1810-L1814
select *
from LOOKUPIAIPACCOUNTS
where Active = 1
  and (STRFORMACCESS like '%(3-_,1,_,0)%'
    or STRFORMACCESS like '%(48-_,1,0,0)%')

NUMACCOUNTCODE
STRACCOUNTDESC

112
RMP Specialist

113
SSCP Engineer

122
SSPP Engineer

Should also add these:

NUMACCOUNTCODE
STRACCOUNTDESC

28
SSPP Program Manager

121
SSPP Unit Manager


Upgrade to truffle 3.2.2 and solidity 0.4.11

Keep in mind there's been a change to the exception raised by explicit throws (ethereum/solidity#2260) so we'll have to change a few things in the tests.

@frangio Thanks a lot for pointing this out! It helped a lot.

I'm glad! :-)


fix(#6,#5): types and approach to specify utxos

Apologies for not splitting the merge, can do so if requested.
Fixes #5 by taking a different approach with specifying a transaction id list that you would like to allow.
Fixes #6 by restructuring and updating the build system.
Also adds an automated publish system to assist with #6.

Closing due to making too many non-merge ready changes to specify this as a caldera-network publish.


CPU Cores

Hi there,
Crashplan only uses 1 CPU core, although 8 CPU cores are available in the NAS.
One CPU core is mostly used at 120% (according to Portainer Info).
The "--cpus=" option is specified on this website, which can be used to regulate the maximum available CPU cores. This option doesn't work:
docker: Error response from daemon: NanoCPUs can not be set, as your kernel does not support CPU CFS scheduler or the cgroup is not mounted.
Does anyone know of another method to make more CPU cores available?
== German ==
Hallo,
Crashplan verwendet nur 1 CPU Core, obwohl im NAS 8 CPU Cores zur Verfügung stehen.
Die eine CPU Core wird meistens zu 120%  ausgelastet (Angabe laut Portainer Info).
 Diese Option funktioniert nicht:
docker: Error response from daemon: NanoCPUs can not be set, as your kernel does not support CPU CFS scheduler or the cgroup is not mounted.
Kennt jemand eine andere Methode, um mehr CPU Cores zur Verfügung zu stellen?

By default, unless you add restrictions, Docker will allow the container to use all cores.
However, it's not because all cores are available the CrashPlan will use all them.
If you want to confirm wether or not usage of cores is restricted for the container, you can try to run stress-ng from the container.  For this, you need to login to the container:
docker exec -ti <container name> sh

Then install stress-ng:
add-pkg stress-ng

Finally run the tool.  Example to run on 4 cores:
stress-ng -c 4

Closing this issue.  Please re-open if needed.

@jlesage,
I seem to be having the same behaviour as this ticket, where CrashPlan only seems to use 1 core at max and that 1 core usage seems to cycle to other cores to but it only ever maxes out at using 1 core.
I used the stress-ng utility to make sure that all cores can work via docker and it certainly can, but do you happen to know if CrashPlan has a way to increase its multi-threading to speed up processing for the CPU intensive tasks?  Ideally would like for it to use all of my CPU resources to finish deduplication and encryption faster.


ERR! code ELIFECYCLE

Hello,
I'm trying to install this on Centos V7. when I run npm install I get the error bellow:
ffi_bindings.target.mk:104: recipe for target 'Release/obj.target/ffi_bindings/src/ffi.o' failed make: *** [Release/obj.target/ffi_bindings/src/ffi.o] Error 1 make: Leaving directory '/home/iota-database-tutorial-master/node_modules/ffi/build' gyp ERR! build error gyp ERR! stack Error: make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Linux 4.4.0-127-generic
gyp ERR! command "/usr/local/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/iota-database-tutorial-master/node_modules/ffi
gyp ERR! node -v v10.4.1
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-06-13T14_31_32_639Z-debug.log
root@vmi187578:/home/iota-database-tutorial-master# n latestgyp ERR! node -v v10.4.1
Error: invalid version latestgyp
`
Any guide?

To perform the proof of work we use ccurl.lib.js. This is a native c library that is accessed using the node ffi module.
Node ffi as part of its install has to build an interop library that is native to the platform you are running on.
This looks like the step that is failing, I would suggest looking at the npm package for ffi to see if they have any suggestions for your specific platform.


Fatal error: Class 'Guzzle\Http\Message\RequestFactory' not found

I'm using the SendGrid library, I've put all in my scripts folder but when I execute my script I get this error:
Fatal error: Class 'Guzzle\Http\Message\RequestFactory' not found in /membri/poisson/scripts/sendgrid-php/vendor/guzzle/guzzle/src/Guzzle/Http/Client.php on line 79
in the row 79 of the Client.php file there is:
$this->setRequestFactory(RequestFactory::getInstance());
But I don't understand what is wrong, because I follow the documentation correct. Someone have the same issue? What I doing wrong?

The SendGrid PHP lib has a dependency on Guzzle, more exactly on a very old version of Guzzle available here. https://github.com/guzzle/guzzle3
Pretty lazy.

@JackIlPAZZO @pomle is correct, Guzzle is required for this library.
@pomle If you would like to have more recent Guzzle support, please see https://github.com/taz77/sendgrid-php. For now, we must maintain backwards support for Guzzle 3 due to the amount of users still using older version of PHP.


Added file downloader script

Description
Added file downloader script
Fixes #1700

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] I have added the project meta data in the PR template.
[x] I have created the requirements.txt file if needed.

Project Metadata
If there is no-file/nothing to fill the below fields with, then type: none
Example: If no requirements.txt needed/present, then type none in Requirments.
Category:

[ ] Calculators
[ ] AI/ML
[x] Scrappers
[ ] Social_Media
[ ] PDF
[ ] Image_Processing
[ ] Video_Processing
[ ] Games
[ ] Networking
[ ] OS_Utilities
[ ] Automation
[ ] Cryptography
[ ] Computer_Vision
[ ] Fun
[ ] Others

Title:  File downloader script
Folder: File downloader script
Requirements: pip install requests
Script: python file_downloader.py
Contributor: Abhinavcode13
Description: A file downloader script is a program or script that automates the process of downloading files from a given URL. It enables users to retrieve files from the internet without manual intervention.
File downloader scripts typically use the HTTP or FTP protocols to establish a connection with a server hosting the desired file. They send a request to the server and retrieve the file's content, which is then saved to a local destination on the user's machine.

Please check this PR!! @avinashkranjan


[JENKINS-63761] Certificate upload correction

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your master branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[n/a] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Jira tickets: JENKINS-63761 and JENKINS-64542 (at least)
⁉ There are multiple things corrected here. The main one is the bug introduced since 2.254 in https://github.com/jenkinsci/jenkins/pull/4910. Due to the COOP header, the new window approach to upload certificate is no longer working. The second problem was about the warning/error message when you are uploading the certificate.
The second part about the validation was filed as a bug in the tracker: JENKINS-65616.
✔ Both are resolved by putting the file input field "inline" inside the form instead of using a window. Then, by adding some magic from Jelly/hudson-behavior.js, we are able to trigger the validation at the correct moment.
Tested with:

2.253 (before the COOP header)
2.254 (just after the COOP header)
2.277.4 (current LTS)
2.292 (current weekly)

Gifs of the behavior
2.253 Create

2.253 Update

2.292 Create

2.292 Update

I think we have typo in the bug number here in the subject - it is also wrong in the release notes https://github.com/jenkinsci/credentials-plugin/releases/tag/credentials-2.4

@saper thanks! (and thanks Daniel for the quick adjustment)

Lol I spent far too long trying to integrate / fix a bug with certs in one of my plugins and gave up as I couldn’t figure out how to upload the cert...
Good to know it wasn’t me being dumb, can’t remember where it was though


docs(api): enhanced the visibility

The API page was littered with rpcMethods and is now fixed by having a horizontal scroll view if the text is too long.
Also fixed a tooltip when hovering over an item in the list

Is this tested?

Tested and it works fine in Firefox 66.0.2 (64-bit).

:tada: This PR is included in version 8.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


LCD Screen Pin Flip

Please list which pin needs to be flipped on the LCD screen.

The board expects VCC-GND-SCL-SDA, looking at it from the front with the display over the cube line meeting point.  I don't have the OLED in front of me to check, but it was two adjacent pins on one end that needed to swap, my guess is VCC-GND otherwise we could have fixed it in software.


⚠ Bofrost.at has degraded performance

In 3570f04, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 953 ms

Resolved: Bofrost.at performance has improved in 840dc26 after 14 minutes.


Wrong serialization of error messages.

It looks like the error messages are not being serialized correctly.
From the conformance server I can see the following error message as the response for a bad formatted request (in hex format):
a56a6572726f725f636f646518647570726576696f75735f6d6573736167655f74797065146c6572726f725f737472696e67784553657269616c697a6174696f6e206572726f723a20696e76616c696420747970653a20696e7465676572206030602c206578706563746564207374727563742048656c6c6f6f6572726f725f74696d657374616d70f66a6572726f725f757569641b55413d158cba1b93

The conformance server fails parsing the above data with:
cbor: cannot unmarshal map into Go value of type fdoshared.FdoError (cannot decode CBOR map to struct with toarray option)

Using the playground site (http://cbor.me ) to decode the content by pasting it in the Bytes text box (on the right side) and clicking on the green arrow above that text box (convert to diagnostic notation), the following is shown:

In the Diagnostic text box, the deserialized data is:

{"error_code": 100, "previous_message_type": 20, "error_string": "Serialization error: invalid type: integer `0`, expected struct Hello", "error_timestamp": null, "error_uuid":<PHONE_NUMBER>474681747}

In the Bytes text box the pasted content is formatted in the following way:

A5                                      # map(5)
   6A                                   # text(10)
      6572726F725F636F6465              # "error_code"
   18 64                                # unsigned(100)
   75                                   # text(21)
<PHONE_NUMBER>6F75735F6D6573736167655F74797065 # "previous_message_type"
   14                                   # unsigned(20)
   6C                                   # text(12)
      6572726F725F737472696E67          # "error_string"
   78 45                                # text(69)
<PHONE_NUMBER>6C697A6174696F6E206572726F723A20696E76616C696420747970653A20696E7465676572206030602C206578706563746564207374727563742048656C6C6F # "Serialization error: invalid type: integer `0`, expected struct Hello"
   6F                                   # text(15)
      6572726F725F74696D657374616D70    # "error_timestamp"
   F6                                   # primitive(22)
   6A                                   # text(10)
      6572726F725F75756964              # "error_uuid"
   1B 55413D158CBA1B93                  # unsigned(6143258529474681747)

According to the FIDO specification the error message definition seems to be an array of elements:
ErrorMessage = [
    EMErrorCode: uint16,   ;; Error code
    EMPrevMsgID: uint8,    ;; Message ID of the previous message
    EMErrorStr:  tstr,     ;; Error string
    EMErrorTs:   timestamp,;; UTC timestamp
    EMErrorCID: correlationId ;; Unique id associated with this request
]
timestamp = null / UTCStr / UTCInt / TIME_T
UTCStr = #6.0(tstr)
UTCInt = #6.1(uint)
TIMET  = #6.1(uint)
correlationId = uint

Therefore, the conformance server error would make sense as we are formatting the Error as a CBOR map instead of an CBOR array.

It would be worth while looking at git history here, I seem to remember there was previous back and forth around cbor serialisation, could also be a bug/change in rust dependencies.


Please move "AMD ROCm Version History" out of the Installation Instruction guide

https://rocmdocs.amd.com/en/latest/Installation_Guide/Installation-Guide.html
has this enormous "AMD ROCm Version History" section which shouldn't be there.
Similarly "Uninstall instructions", "AMD ROCm MultiVersion" and "Getting the ROCm Source Code" should be moved out of this document.

We have moved the version history section into the per-version release notes, but I believe the other sections make sense to leave in the installation guide. Thanks for the feedback!


Garbage Collection - Timeline is disappeared

I dont see it. Where timeline tab is?
https://cl.ly/3x420x2y3Z2M

May be it is preformance tab ? Because it looks very similar


library not found for -lglfw3

Required Info

Camera Model
SR300

Firmware Version

Operating System & Version
macOS 10.12.2

Kernel Version (Linux Only)

Build System
XCode

Continued from #152. Since then, I changed some setting on Xcode and now I'm getting a build error as follows (e.g. when I ran cpp-pointcloud):
ld: warning: directory not found for option '-L/Users/username/Projects/librealsense/librealsense.xc/../librealsense/build/Debug'
ld: warning: directory not found for option '-L/Users/username/Projects/librealsense/librealsense.xc/../bin'
ld: warning: directory not found for option '-L/Users/username/Library/Developer/Xcode/DerivedData/bin/Debug'
ld: warning: directory not found for option '-L/Users/username/Projects/librealsense/librealsense.xc/build/Debug'
ld: library not found for -lglfw3
clang: error: linker command failed with exit code 1 (use -v to see invocation)

As @martinthomas suggested, this error might be because of the deprecated glfw3 from brew, but
when I ran brew install homebrew/versions/glfw3, the output said the followings.
Warning: Use glfw instead of deprecated homebrew/versions/glfw3
Warning: glfw-3.2.1 already installed

I don't have libglfw3.dylib, but I have libglfw.3.2.dylib, libglfw.3.dylib and libglfw.dylib under /usr/local/lib/.

See pull request #408

This is because glfw3 is deprecated.  If you read the result of the brew install command, it says it installed glfw-3.2.1 - which is not glfw3.  The ld command fails to find "-lglfw3" because brew did not install it.
You can try changing the library target in the Xcode project from glfw3 to glfw and that will fix it or you can use the pull request that I submitted to fix the dependency.

Thank you very much. Now everything works fine.

Close?

Yes, thanks.


Adds mina-pr-gating to required status in mergify.yml

This makes the test officially required

!approved-for-mainnet

!approved-for-mainnet


Checksession is not sending the cookies to the identity server,

Hi,
tried multiple times, check session is not able to send the cookies after logged in and the application is logged out.
checked multiple sites to change the cookie samesite attribute to none, Cookiesecurepolicy to always(secure) but still no luck.
Identity server4 2.2.0 and aspnetcore 2.0.3

Well - this looks like a SameSeit cookie issue. Also keep in mind that we can only support the latest IdentityServer/ASP.NET Core versions.
Generally speaking - check session will not work reliably anymore.
https://leastprivilege.com/2020/03/31/spas-are-dead/

@leastprivilege  Thanks for the response, if I upgrade to latest identity server 3.1.2 and aspnet core to 3.1 will it work or do i need to do any changes to make it work?

@leastprivilege Thanks for the response, if I upgrade to latest identity server 3.1.2 and aspnet core to 3.1 will it work or do i need to do any changes to make it work?

I'm not sure if we're talking about the same issue, but in order to get the Quickstart projects to work  today in 3.1, all I had to do to get it working was make everything HTTPS. I was really pissed off at first because the MVC to IdP Quickstart solution didn't work from the latest code in github, but then I realized it might have something to do with SameSite cookies and switched to HTTPS.  I would suggest the team retest and update those projects accordingly.
Note that you can turn on and off those "SameSite" features in chrome (for testing purposes) here: chrome://flags/

https://github.com/IdentityServer/IdentityServer4/blob/master/src/IdentityServer4/host/Extensions/SameSiteHandlingExtensions.cs

After set right SameSite value, you may need check browser settings.

Chrome
settings -> privacy and security -> Site Settings -> Cookies and site data

If Block third-party cookies is checked, please add you OP domain into Allow list

If Block third-party cookies is checked, please add you OP domain into Allow list

this setting will sooner or later become the default value for all browsers. The check session mechanism will not work reliably anymore if client and OP are cross-site.
https://leastprivilege.com/2020/03/31/spas-are-dead/


Add uintSlice and boolSlice to name prettifier

I might have missed some. These are the ones I came across.

But #148 actually makes sense to not use word "slice" for flag arguments.

An option could be to instead of replacing them in the switch, just replace
Slice in the type name with .... This would make the types string...,
uint... etc.
On 6 Nov 2017 15:39, "Albert Nigmatzianov"<EMAIL_ADDRESS>wrote:

But #148 https://github.com/spf13/pflag/issues/148 actually makes sense
to not use word "slice" for flag arguments.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spf13/pflag/pull/150#issuecomment-342167979, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA0F3DvO0y4i_WDkSPpk7UcjkjCV7cQ7ks5szxo7gaJpZM4QTJKA
.


Adding Conda packages to conda-forge

It would be great to have packages for Conda. While there are packages maintained by Anaconda, it would be great to have some community maintained packages in conda-forge. This would allow us to update things more directly and provide us the option to publish RCs to get the latest changes out there. Not to mention Anaconda reuses recipes from conda-forge in their own builds. In this effort it would be great to have your help maintaining the package. Thoughts?
cc @pentschev

Have added PR ( https://github.com/conda-forge/staged-recipes/pull/8638 ) to get this started. It is still WIP.

Thanks for the discussion on this topic today during the PFN-NVIDIA call.
Just to summarize it here, PFN is going to discuss this but are mostly willing to maintain CuPy's conda-forge package. For now, @jakirkham has sent an initial package recipe in https://github.com/conda-forge/staged-recipes/pull/8638 that may be used as an introductory recipe and CuPy could continue to maintain it afterwards. Also, @jakirkham and I will help PFN if they encounter any issues with the package in the future.
Among the advantages of having this package are the capabilities of having nightly/development builds of CuPy, as well as allowing packages for different version of dependencies. As an example, we have an immediate need of a CuPy package with NCCL 2.4, and the package on conda's main repository only supports NCCL 1.x, but this scenario could be extended to the various dependencies of CuPy.
Feel free to expand on this if I missed something.

@pentschev Thank you for summarizing the discussion!
@jakirkham

Does conda-forge provides automated build infrastructure like DockerHub, or should we build and upload packages by ourselves for each release?
Anaconda's main repo already hosts cupy package. Are there anything that we should take care of (e.g. conflicts between Anaconda's main repo and conda-forge repo)?

Thank @pentschev for discussing this with PFN. Also thanks for the thoughtful questions, @kmaehashi. Have added some info below.

Does conda-forge provides automated build infrastructure like DockerHub, or should we build and upload packages by ourselves for each release?

conda-forge provides infrastructure for each feedstock to manage the build and upload of packages from a clean, reproducible environment. This infrastructure is maintained by the core group in conda-forge and a few service providers (like Anaconda and Azure), which we work with. In fact update PRs are largely automated as well. So this comes down to reviewing, possibly modifying, and merging a PR like this one. For manual changes, there is a rough overview in the docs.

Anaconda's main repo already hosts cupy package. Are there anything that we should take care of (e.g. conflicts between Anaconda's main repo and conda-forge repo)?

Users of conda-forge are recommended to make the conda-forge channel higher priority as noted here. Additionally Anaconda's recipes are all downstream from conda-forge. Once the conda-forge feedstock is made, they will fork it and apply any changes they need on top of it. More generally conda-forge and Anaconda work together to keep their recipes in sync as much as possible. It's possible Anaconda will submit changes they recommend to the recipe, which may need review.

@kmaehashi, does that help answer your questions? Are there any other questions you have?

@jakirkham Sorry for the late reply and thank you for the answer! We discussed in the team and agreed to publish cupy package on conda-forge (I'm assuming nvcc and nccl packages in the PR will be maintained by NVIDIA). Could you proceed to merge https://github.com/conda-forge/staged-recipes/pull/8638?

Thanks @kmaehashi! Sorry for being quiet here.
We've recently added the infrastructure to build GPU packages. This includes the necessary logic for conda-build to perform builds with nvcc and add the cudatoolkit libraries as a dependency. Added nccl recently. So cupy's dependencies are in place.
Have replaced the aforementioned PR with this updated one ( https://github.com/conda-forge/staged-recipes/pull/9959 ). Would be great to hear from more CuPy developers on this PR. Please let us know if this looks reasonable. 😄

Just a brief comment from our NVIDIA-PFN meeting today, the PFN team would like to maintain the package as a team. @jakirkham is it possible to add a group of people to be maintainers of conda-forge packages? If not, I think the primary maintainer would be @kmaehashi, could you confirm?

Yes, I will be a primary maintainer.

is it possible to add a group of people to be maintainers of conda-forge packages?

I think so. Give me a list of github ids. I can add them as the maintainers

For the discussion on the maintainers, please go to conda-forge/cupy-feedstock#7.

Thanks all! Going to close this as complete. 😄
We can follow up on anything else either as issues here on the feedstock as appropriate.

Great to hear, thanks @jakirkham for the enormous effort on this!


feat(config): add volumeConfigs field for VolumeConfig manifest

Fixes: https://github.com/budimanjojo/talhelper/issues/781

Hmm, looking at extensionServices that I use for list of ExtensionServiceConfig, it seems like this shouldn't be volumeConfigs but volumes instead.


Remove docutils work-around

Docutils 0.20 has finally been released, hooray!
Sadly, Sphinx doesn't seem to support it yet: https://github.com/sphinx-doc/sphinx/issues/11414

I've released Sphinx 7.0.1 with support for DU 0.20.
A

Thanks @AA-Turner!


Segmentation Fault with C++ API on Tizen

Hello,
I am trying to run a simple program on a Tizen 6.5 platform with armv7l arch.
#include <iostream>
#include <memory>

#include <nntrainer_cpp/model.h>

int main(int argc, char** argv) {
    using namespace ml::train;

    auto model=createModel(ModelType::NEURAL_NET);
    auto res=model->addLayer(layer::Input({"input_shape=1:1:10", "normalization=true"}));
    std::cout<<res<<'\n';
    return 0;
}

The program crashes on the destructor of a model object.
This only happens when the layer/optimizer is added to a model.
A result of model->addLayer() is 0.
The gdb stacktrace I get:
Program received signal SIGSEGV, Segmentation fault.
0xb69fa69c in nntrainer::NeuralNetwork::~NeuralNetwork() () from target:/lib/libnntrainer.so
(gdb) bt
#0  0xb69fa69c in nntrainer::NeuralNetwork::~NeuralNetwork() () from target:/lib/libnntrainer.so
#1  0xb69fac28 in nntrainer::NeuralNetwork::~NeuralNetwork() () from target:/lib/libnntrainer.so
#2  0x00013788 in std::default_delete<ml::train::Model>::operator() (this=0xbefffc94, __ptr=0x44788) at /usr/arm-linux-gnueabi/include/c++/10/bits/unique_ptr.h:85
#3  0x00012e94 in std::unique_ptr<ml::train::Model, std::default_delete<ml::train::Model> >::~unique_ptr (this=0xbefffc94, __in_chrg=<optimized out>) at /usr/arm-linux-gnueabi/include/c++/10/bits/unique_ptr.h:361
#4  0x000124f4 in main (argc=1, argv=0xbefffe54) at /home/user/IoML/src/src/main.cpp:9

Program is being compiled with a following command
arm-linux-gnueabi-g++  -I/home/user/IoML/src/include -I/home/user/IoML/deps/include -I/home/user/IoML/deps/include/nntrainer_cpp -I/home/user/tizen-studio/platforms/tizen-6.5/wearable/rootstraps/wearable-6.5-device.core/usr/include -I/home/user/tizen-studio/platforms/tizen-6.5/wearable/rootstraps/wearable-6.5-device.core/usr/include/network -I/home/user/tizen-studio/platforms/tizen-6.5/wearable/rootstraps/wearable-6.5-device.core/usr/include/nnstreamer -I/home/user/tizen-studio/platforms/tizen-6.5/wearable/rootstraps/wearable-6.5-device.core/usr/include/nntrainer -I/home/user/tizen-studio/platforms/tizen-6.5/wearable/rootstraps/wearable-6.5-device.core/usr/include/dlog -I/home/user/tizen-studio/platforms/tizen-6.5/wearable/rootstraps/wearable-6.5-device.core/usr/include/appfw -I/home/user/tizen-studio/platforms/tizen-6.5/wearable/rootstraps/wearable-6.5-device.core/usr/include/appcore-agent  -Ipch -g3 -Wall -O0 -fmessage-length=0 -march=armv7-a -fPIC -mfloat-abi=softfp -std=gnu++2a -o CMakeFiles/Main.dir/src/src/main.cpp.o -c /home/user/IoML/src/src/main.cpp

arm-linux-gnueabi-g++ --version returns
arm-linux-gnueabi-g++ (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
I am using Tizen headed build from 17 March 2022, C++ API version 0.3.0-43.11

:octocat: cibot: Thank you for posting issue #1860. The person in charge will reply soon.

Ok, I managed to fix it. For some reason it complied successfully although the dependencies were not linked correctly.


[Concurrent Segment Search] Enable Search ITs with Concurrent Segment Search

Currently Search ITs do not run with Concurrent Search feature.  We need to identify and enable the suite of existing IT that needs to run with this feature.

@yigithub These look like sub-tasks with no description.  Could you please link these back to a meta along with #7439, #7438, #7437 ?

@yigithub Please make sure to add the details for this issues

Adding some more details --
As of #7356 there are now 3 ways to control Concurrent Segment Search: 1.) Feature Flag (Not Dynamic) 2.) Dynamic Cluster Setting 3.) Dynamic Index Setting
Currently, the Feature Flag is disabled for (almost) all java ITs so we do not have automated test coverage for concurrent search. The goal of this task is to come up with a way to automatically run the java ITs with concurrent segment search enabled.
Off the top of my head one solution is to enable the Concurrent Segment Search Feature Flag and then parameterize the tests using the dynamic cluster setting. However we would like to avoid adding the parameterization code to every single test if possible, so it would be good to come up with a solution where all of the controls are in one place.

I will be working on this.

Created an [issue] (https://github.com/opensearch-project/opensearch-build/issues/3729) with EE team to ask about a custom jenkins job to run the following command that run the entire test suite with concurrent search enabled:
./gradlew :server:internalClusterTest --tests "org.opensearch.search.*" -Dopensearch.experimental.feature.concurrent_segment_search.enabled=true


[FEAT] Incorrect Password Reset Link

Description
Users who attempt to reset their passwords receive a reset link via email, but when they click the link, they are redirected to an incorrect or unintended page. This issue prevents users from successfully resetting their passwords and impacts their ability to access their accounts.
Acceptance Criteria
Users will be correctly redirected to the password reset page upon clicking the reset link.
The password reset process will function properly, allowing users to successfully reset their passwords.
Any issues with incorrect redirections will be resolved, improving the overall user experience.
Purpose
To be able to generate and managing the reset link for users that want to reset password
Requirements
Check the backend logic responsible for generating and handling password reset links.
Ensure that the link parameters are processed correctly and that users are directed to the intended page for password reset.
Expected Outcome
Users will be correctly redirected to the password reset page upon clicking the reset link.
The password reset process will function properly, allowing users to successfully reset their passwords.
Any issues with incorrect redirections will be resolved, improving the overall user experience.
Uploading Incorrect reset link.mov…

@Promachi
Kindly include the team for this fix.

@Promachi
Kindly include the team for this fix.

It's been updated. C#


Add autoload composer

Add autoload composer
Add namespace class
Fix issue #2

It is done

Merged! Thank you for your contribute. :-)


e2e logs do not have timestamp

The logs downloaded from stackdriver do not have timestamp.
Plus we need the proxy (side car) logs in order to understand the issues.

Make sure the content of the logs is to @kyessenov satisfaction.


[Enhancement Request]: Porting for JS/TS ?

Any chance to have a porting for JS/TS ?

Yes, hoping to have this done by EOD :)


Add writing guidelines to Style Guide

Add writing guidelines to Style Guide for:

general principles of writing
error messages
capitalization (JSON or json)
verb tense
addressing audience
length
commas (Oxford)
spacing
...and more!

Perhaps this should be a wiki page rather than on the style guide?

Here is the wiki: https://github.com/DataBiosphere/saturn-ui/wiki/Writing-Guidelines
Take a look and comment with your thoughts and items for discussion.
If anyone has more than a handful of quick thoughts and opinions, I can create a Google Doc for collaborating/bickering/convincing.

Well done, Kate! Nice concise guidance. (Not sure if I need commas there ;)  I especially like the "Objective then action" guideline and leading with the most important information. Another rule I would love to standardize on is to omit commas after labels. If the information design is done right, they should not be needed.
Fwiw, Google's writing guidelines in the Material spec are a nice reference that I generally agree with -- with the possible exception of their preference for using numbers in sentences. They might spark other topic ideas.

@katevoss Thanks for doing this and I agree with your guidance.

I added a section for Labels and a link to Material.io. I'll leave this PR open for another day in case anyone has additional requests or suggestions.


Add "increment" parameter to ProgressBar to define how much increase the value at every input change

Sir, sorry to bother you again. Could you kindly elaborate the feature a little bit? What do you mean by at every input change specifically? Is it just an invocation of the setValue(value) method? Do we need to add new incrementValue()/decrementValue() method?
IMHO, despite good documentation, the constructor signature already seems complex enough with multiple optional parameters. Why don't  we just use a single object as the argument. For example:
// with a single object parameter
new Progress({
	x: 3,
	y: 23,
	length: 20,
	id: "prog1",
	thickness: 1,
	style: pStyle,
	theme: "htop",
	orientation: "horizontal",
});

// with multiple parameters
new Progress("prog1", 20, 1, 3, 23, pStyle, "htop", "horizontal")

The previous one is much more clean and scalable than the current implementation. But if you don't want to change the API then should I just add the increment parameter at the end as an optional one?
Thank you.

Yes, the change of every widget constructor with only one props configuration object is in my plans and it should increment the version to a new major release because of the incompatibility that it will cause.
I'm considerin go do it in the next weeks.
For now, you can ad the increment value as a class property with setter and getter methods.
So if you want to change the default increment you have to use theese methods.

And, just to be clear what function will the increment property serve? For example, if I create a new ProgressBar and set the *increment value to 10. So, calling some kind of incrementValue method would change the progress percentage by 10 and render it to the screen?

It will be usefull for interactions with the mouse wheel
if (event.name === "MOUSE_WHEEL_DOWN") {
  if (this.value > this.min + 1) {
      this.value -= 1 // this is the hardcoded increment
  } else {
      this.value = this.min
  }
  this.emit("valueChanged", this.value)
  this.update()
}
if (event.name === "MOUSE_WHEEL_UP") {
  if (this.value < this.max - 1) {
      this.value += 1 // this is the hardcoded increment
  } else {
      this.value = this.max
  }
  this.emit("valueChanged", this.value)
  this.update()
}

This also when will be developed the arrows, on the key listeners.
Thanks man

Thanks to @h-sifat 🙏

@h-sifat feel Thank you for your help! Feel free to propose changes for other things as well.
I saw that you use nice and correct syntax, if you feel like, you can for example check for flaws or errors in my code and propose stylistic changes.
Thank you, best regards


How to read video file from sftp location

Hi
I am facing issue in reading file from sftp location using opencv lib. Can you tell me how to read file from sftp location or sftp file object. If can you tell me read large file directly to opencv lib then it's good things.

This is not a QA forum. Usage questions belong to http://answers.opencv.org/questions/ or to https://stackoverflow.com/.


[Question]: What is the reason for the user defined literals?

In the following example:
"args"_test =
   [](const auto& arg) {
      expect(arg >= 1_i);
    }
  | std::vector{1, 2, 3};

You use a custom integer literal. Why? I noticed there is afair amount of code in the library to support this so I was just curious what its purpose is as it works fine without the literals.

Mainly, in order to nicely print error messages with expanded expressions :+1:
  expect(add(1, 2) == 4_i); // with UDL -> will nicely print the expression
  expect(add(1, 2) == 4); // without UDL -> will use bool

  <source>:8:FAILED [3 == 4]
  <source>:9:FAILED [false]

Example -> https://godbolt.org/z/4bauN2

:+1:


Unable to log in to CodeCrunch

Summary
When I tried to log in to my account, I have been receiving this message since yesterday.
Screenshots (if any):

Please let SOC-RT know about this.

Try leaving it for awhile and log in again later?


'importlib._bootstrap' has no attribute 'SourceLoader'

Hi,
I'm trying to build an app. It was working before (ok, maybe some months ago. Since then, python 3.5 went out).
I have the following exception:
File "/usr/lib/python3.5/site-packages/esky/util.py", line 578, in compile_to_bytecode
    loader = importlib._bootstrap.SourceLoader()
AttributeError: module 'importlib._bootstrap' has no attribute 'SourceLoader'

I'm using:
Python 3.5.0
Esky 0.9.9 (latest) from pypi
cx_freeze 4.3.4-2
And I'm on Manjaro (Linux). It seems to be related to #67 somehow, but I'm not really sure. Could you give me a hand please ?

Ok, I spent the day on this issue, with the help of others.
I first monkey-patched esky:
http://stackoverflow.com/questions/33365471/importlib-bootstrap-has-no-attribute-sourceloader#
Some little changes:
loader = importlib._bootstrap_external.SourceLoader()
We assumed that esky is not compatible yet with python 3.5.
Once this corrected, the build completed, but I got another error when trying to run the exe:
ImportError: No module named '_frozen_importlib_external'
Fatal Python error: Py_Initialize: importlib install failed

This one is because cx_Freeze "can not see an import":
https://bitbucket.org/anthony_tuininga/cx_freeze/issues/156/running-frozen-app-with-python-35-no
By applying the patch here:
https://bitbucket.org/anthony_tuininga/cx_freeze/pull-requests/83/python-35-compatibility-for-cx_freeze-4x/diff
I could solve the issue. But as I use scipy in my program, I got one last error:
Error importing scipy: you cannot import scipy while
being in scipy source directory; please exit the scipy source
tree first, and relaunch your python intepreter.

I found the solution here:
http://stackoverflow.com/questions/32432887/cx-freeze-importerror-no-module-named-scipy
By patching cx_Freeze again, I finally got my program running.
I let this here for posterity, or in case someone runs into the same problems.

Thanks for your work, see this post for more info on our plans https://github.com/cloudmatrix/esky/issues/95,

I can probably make a PR. Would it help ?

that would be awesome

Ok, I will try. Do I also have to write some tests ?

We are using travis ci to run the tests when pull requests are pushed. I don't think you need to write more tests, as long as the tests that we have pass on 2.7 +

Ok, I'm still not confortable with the PR process, but I think it's ok now. I just made one. It solved my issue (at least for the Esky part).

Cool, at the moment the tests on the server are only being run on python 3.4, ill update it for 3.5 and see what we get.
Here are my favorite resources on git
https://www.youtube.com/watch?v=4EOZvow1mk4
https://www.youtube.com/watch?v=KDUtjZHIx44

@JPFrancoia Thanks


Fixing Social Media Icons Section

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!

Sumarise what this PR fixes:
I have Modified index.html and Styles.css to implement the Fix. It includes Deleting one of the Social Media icons row and Commented out lines 323 to 325 in Styles.css
Fixes #: 219
Checklist:
(Add an x between the brackets to check the items)

[x ] I have sumarised what this PR fixes above
[ x] I have provided the issue ID/URL above
[x ] This PR fixes only the issue mentioned above (create seperate PRs for seperate issues)
[ x] I was the first one to claim the issue or I created the issue

Hey, looks like this is an empty PR (meaning, it introduces no changes to the existing codebase).
Thanks for putting efforts on making this PR anyways :)

But i made the changes
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
10/02/20,
11:21:32 PM
On Fri, Oct 2, 2020 at 9:51 PM Abdus<EMAIL_ADDRESS>wrote:

Closed #225 https://github.com/zero-to-mastery/Keiko-Corp/pull/225.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zero-to-mastery/Keiko-Corp/pull/225#event-3834716770,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHKVVHEWNJFEMRM7MQWLBRLSIX42PANCNFSM4SB2X42Q
.

the changes you've made are probably already merged into this repository. so, it's empty

okay,thank you.
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
10/03/20,
09:17:12 AM
On Sat, Oct 3, 2020 at 3:03 AM Abdus<EMAIL_ADDRESS>wrote:

the changes you've made are probably already merged into this repository.
so, it's empty
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zero-to-mastery/Keiko-Corp/pull/225#issuecomment-702967781,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHKVVHEDWZR74A4BK2XWYLTSIZBJ3ANCNFSM4SB2X42Q
.


Install Sui failed on M1 Mac

Command
cargo install --locked --git https://github.com/MystenLabs/sui.git --branch devnet sui
Error
error: linking with cc failed: exit status: 1
······
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: could not compile sui-framework due to previous error
System Information

rustup: stable-aarch64-apple-darwin unchanged - rustc 1.70.0 (90c541806 2023-05-31)
cmake: cmake version 3.26.4
OS: macOS Ventura 13.4, Apple M1 Pro

So how can I fix this and install Sui?

Command
cargo install --locked --git https://github.com/MystenLabs/sui.git --branch devnet sui
Error
error: linking with cc failed: exit status: 1 ······ ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) error: could not compile sui-framework due to previous error
System Information

rustup: stable-aarch64-apple-darwin unchanged - rustc 1.70.0 (90c541806 2023-05-31)
cmake: cmake version 3.26.4
OS: macOS Ventura 13.4, Apple M1 Pro

So how can I fix this and install Sui?

It looks like a rust environment issue, not a sui issue.
Try to add the following sections to your ~/.cargo/config (if you don't have this file feel free to create):

[target.x86_64-apple-darwin]
rustflags = [
  "-C", "link-arg=-undefined",
  "-C", "link-arg=dynamic_lookup",
]

[target.aarch64-apple-darwin]
rustflags = [
  "-C", "link-arg=-undefined",
  "-C", "link-arg=dynamic_lookup",
]

Works for me! I'll let you know if I have any other issues.

@alphafitz11 Feel free to create a new issue if it still does not work for you.


\n and \r escaping on text asset dump importing

Hello,
I'm having some trouble when trying to escape the new line sequence (\n) using the "Import dump" tool, and I suspect that it might a be bug or a limitation of the program.
When I export the text asset of the AmongUs videogame, the resulting dump looks like this:
\r\nHowToPlayText42       Firstly, determine who you want to play with!\\n\\nIf you want to play with friends online

As the text shows, the different translation string records are separated with \r\n. That works nicely, but the problem comes when some strings include \\n (like in the example above). According to what I tried (but I might we wrong), there is no way to export those espaced line breaks \\n back to the asset file. The program converts them into regular non escaped line breaks, and the game is not able to correctly parse them (actually only the first line of the strings is shown in-game).
I think the following flow also confirms the unexpected behaviour:

Export the asset using "Export dump".
The resulting string has the escaped line breaks \\n.
Without making any change import the dump back to the asset.
Export the asset using "Export dump" again.
The resulting string has the line breaks unescaped \n.

Could this be a bug? Or is there any way to workaround the problem?
Thank you for your work.

Fixed in latest commit.


Misc Deuce TODOs

X button in pop-up windows (deuce, right-click, config panel).

Restore Deuce selection state on Undo.

Issue with text-selection. Hold Shift and press an arrow key to perform an Ace text selection. A Deuce polygon appears.

(let p e1 e2) target positions: The whitespace between p and e1 is treated specially, with all characters up to the first newline (if any) dedicated to after-p, and the rest to before-e1. Instead, each polygon should be mapped to a set of code objects (specifically, white space objects in this case), and selection sets should be interpreted as the Cartesian product of the selected code object sets.

Moved to individual issues in project board.


Devops - build fails on tests due to disk limits

Following on from issue #160, I am now building with gradle 5.6.4, but the build fails the following tests:
org.webcurator.core.visualization.networkmap.NetworkMapUtilTest > testGetNextTitle FAILED
    com.sleepycat.je.DiskLimitException at NetworkMapUtilTest.java:43

org.webcurator.core.visualization.networkmap.NetworkMapUtilTest > testClassifyTreeViewByPathName2 FAILED
    com.sleepycat.je.DiskLimitException at NetworkMapUtilTest.java:43

org.webcurator.core.visualization.networkmap.NetworkMapUtilTest > testClassifyTreeViewByPathName FAILED
    com.sleepycat.je.DiskLimitException at NetworkMapUtilTest.java:43

org.webcurator.core.visualization.networkmap.NetworkMapClientLocalTest > test FAILED
    com.sleepycat.je.DiskLimitException

org.webcurator.core.visualization.networkmap.NetworkMapClientLocalTest > testInitialIndex FAILED
    com.sleepycat.je.DiskLimitException

org.webcurator.core.visualization.networkmap.IndexProcessorTest > testInitialIndex FAILED
    com.sleepycat.je.DiskLimitException at IndexProcessorTest.java:48

org.webcurator.core.visualization.networkmap.BDBNetworkMapTest > testBDB FAILED
    com.sleepycat.je.DiskLimitException at BDBNetworkMapTest.java:27

348 tests completed, 7 failed, 29 skipped

> Task :test FAILED

FAILURE: Build failed with an exception.

The specific exception in all these cases is
com.sleepycat.je.DiskLimitException: (JE 18.3.12) Disk usage is not within je.maxDisk or je.freeDisk limits and write operations are prohibited: maxDiskLimit=0 freeDiskLimit=5,368,709,120 adjustedMaxDiskLimit=0 maxDiskOverage=0 freeDiskShortage=1,511,313,408 diskFreeSpace=3,857,395,712 availableLogSize=-1,511,313,408 totalLogSize=1,427 activeLogSize=1,427 reservedLogSize=0 protectedLogSize=0 protectedLogSizeMap={}

I have about 80GB of free space on my laptop, so pretty sure that's not the issue. I can see this has come up in Heratrix before, with a solution to increase the FREE_DISK variable.

I was able to get past this by adding
environmentConfig.setConfigParam(EnvironmentConfig.FREE_DISK, "0");

to the BDBRepoHolder.java file as suggested in this comment.
I don't know a better way to raise the disk limit, anyway this works for now.

Setting the disk limit to zero just removes the free space limit, in the meantime I've set my limit to<PHONE_NUMBER> (10GB), which also passes the test.


Span vs Context

Span vs Context
The context propagation changes from OTEP 66 have lead to a few wrinkles in our APIs that need be addressed. Tracer#start_span returns a span. Often times this is what you want, but sometimes you really want that span in a Context object. On the other hand, sometimes you have a Context object and you want the current span from it.
What should Tracer#start_span return?
We could return a context instead a span, but I'm not sure that would improve things. It's worth considering though. Go has take the approach of returning both a context and span from start_span. Multiple return values would be possible, but not idiomatic in Ruby, and sadly would cost an additional array allocation. I suppose we can still consider that as an option.
Current issues
I have a span, but I want it in a context
An option is:
Tracer#in_span(span) { ctx = Context.current }

Is this good enough or should we add more convienence methods around this?
I have a context, but I want a span
Currently you have to do this:
Context.current[OpenTelemetry::Trace::Propagation::ContextKeys.current_span_key]

Proposal ContextUtils
While the above options work I think we can improve this situation. The OpenTelemetry::Context object is meant to be a general purpose context that could possibly be extracted out from OpenTelemetry and standalone as its own package. As such, adding a convenience methods to the Context directly should be avoided, but we can introduce a OpenTelemetry::ContextUtils class. Here's how I would see that working.
# read the current span from a given context
ContextUtils.span_from(context)

# read the span context from a given context
ContextUtils.span_context_from(context)

# return a new context with a given span and parent context
ContextUtils.set_span(span, parent: Context.current)

# return a new context with a given span context and parent context
ContextUtils.set_span(span, parent: Context.current)

While something like https://github.com/open-telemetry/oteps/issues/68 could be a better long term solution, this will improve some difficulties that we're running into with the current API.

I think this sort of thing should be the responsibility of objects in the Trace API rather than sticking them in a separate utils module. Having seen example uses in #202, the code doesn't seem any cleaner to me.

Related: https://github.com/open-telemetry/opentelemetry-specification/issues/455

If you are interested in this still, please take a look at https://github.com/open-telemetry/opentelemetry-specification/pull/875

I think this issue can be closed @mwear.

I think this issue can be closed @mwear.


The entrypoint runs as root, should run as graylog

Multi-tenant Kubernetes services such as OpenShift do not allow containers to run as root, and as such, the Graylog image fails to run on OpenShift.
It looks like you already create the greylog user, and change the file ownership to graylog.  All that would be left to do is a USER graylog entry in the Dockerfile.

all images are now updated.


1.20 Update?

Hello sir, Thank u for making this mod <3
I really miss this mod in my game.. do u have any plans on updating the mod to 1.20 in the near future?

At some point

on curseforge

Yooo thank u so much, I will go back to minecraft today for this... <3


fix: make autoware_cmake Clang-friendly

Description
Currently, many packages in Autoware cannot be built with Clang (for the purposes of this PR, Clang = Clang-15, the newest version packaged on Ubuntu 22.04).
This PR demotes a number of additional compiler warnings only output by Clang from error to warning, in order to make a large number of Autoware packages buildable while staying minimally invasive. The main aim of this PR is to facilitate a timely introduction of Clang-Tidy across all Autoware packages.
Why Clang?
Clang provides the foundation for most modern state-of-the-art static analysis tools, such as Clang-Tidy and FB-Infer. Static analysis is of utmost importance to catch bugs before they hit production, especially in autonomous driving. Not having Clang support prevents us from fully introducing this common industry practice. Also see the Clang-Tidy discussion.
Further, Clang detects many more problems in the source code, thus giving developers better input on how to improve their code. Clang-specific features might also be a reason for some developers, see this discussion.
The current situation
Currently, out of 347 packages, 17 (5%) fail on Clang due to compiler errors, preventing 172 (50%) dependent packages from being built. Note that even with fixes in those 17 packages, other packages do have compiler errors as well.
Root cause
As Clang detects more code problems than GCC, and since -Werror is set for both compilers, the additional warnings flagged by Clang are promoted to error and cause many packages' builds to fail.
These errors (taken from the fixed log retroactively) are preventing Autoware from being built*:
208 -Wdeprecated-copy
66 -Wdelete-non-abstract-non-virtual-dtor
27 -Wunused-private-field
26 -Wc11-extensions
20 -Wsign-conversion
19 -Wformat-security
17 -Wunused-parameter
17 -Winconsistent-missing-override
10 -Wunused-lambda-capture
10 -Wunused-const-variable
8 -Wimplicit-const-int-float-conversion
6 -Wunused-but-set-variable
6 -Wdelete-abstract-non-virtual-dtor
5 -Wdefaulted-function-deleted
3 -Woverloaded-virtual
1 -Wunused-function
1 -Wpessimizing-move
1 -Winfinite-recursion
1 -Wdeprecated-builtins

Detailed warnings here:
warnings.txt
Full log (before):
build-old.log
Full log (after):
build-new.log
Possible fixes

Fix all errors in all modules (quite many people involved, hard to manage)
Temporarily demote affected Clang-specific warnings to warn

The first option is best handled by architects or teams such as the Autoware engineering team, as this is a coordinated effort involving many contributors.
This PR implements the second option, and since all these warnings are in addition to warnings similar to GCC's ones, I think it is fine to not treat them as error temporarily. Build quality will still not be lower than that produced by GCC.
Effects of this PR
Out of 347 packages, 3 (<1%) fail on Clang, preventing 6 (2%) dependent packages from being built.
This is an :point_right: :point_right: improvement of 114% :point_left: :point_left: in the number of successfully buildable packages!
To get a list of all warnings that were promoted to error and caused a build failure, run:
colcon build 2>&1 | tee build.log
cat build.log | grep -oP '\[-Werror,\K[^]]*' | sort | uniq -c

*: Build command:
colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_EXPORT_COMPILE_COMMANDS=1 -DCMAKE_C_COMPILER=clang-15 -DCMAKE_CXX_COMPILER=clang++-15

Tests performed

Not applicable.
Effects on system behavior

No effects when building with GCC (default).
More packages buildable when building with Clang

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

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

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

[ ] The PR follows the pull request guidelines.

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

[ ] There are no open discussions or they are tracked via tickets.

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

To Do
Limit the list of disabled warnings only to the most impactful ones. Impact, as in, the number of code fixes saved by disabling the warning here.
For some warnings, it will be better to fix them in the respective packages, as they might either be real bugs or they might only affect a single package.


Consider preferring preferred quote style if both styles require backslashes

Given:
"json enter input={'a': 2} kwargs={\"strict\": None, \"context\": {\"c\": 2}}"

Black will reformat as:
'json enter input={\'a\': 2} kwargs={"strict": None, "context": {"c": 2}}'

Ruff does the same thing, so it's not a compatibility issue. But I'm wondering if it makes more sense to bias towards the preferred quote style if you need backslashes regardless (even if the non-preferred style results in fewer backslashes).
This came up in the Pydantic migration: https://github.com/pydantic/pydantic/pull/7930/files#r1373829517

I'm leaning toward Black compatibility. It doesn't seem we have strong reasoning to diverge. E.g. for the above example, I find Black's formatting easier to read and it results in a shorter string overall.
"json enter input={'a': 2} kwargs={\"strict\": None, \"context\": {\"c\": 2}}'

It doesn't seem to have come up again. We can improve our documentation if this comes up more often. @charliermarsh feel free to re-open if you disagree with my decision.


bug: Sierra function declarations generated for loops are lacking namespacing

Bug Report
Cairo version:
1.1.0
Current behavior:
Compiling with cairo-compile -r gives declared functions proper namespacing but the namespaces lack for auxiliary Sierra functions generated for loops.
Expected behavior:
Generate better names for the auxiliary Sierra functions which  cannot clash with functions in other modules of the same name.
Steps to reproduce:
Take for example a snippet feltloop.cairo:
fn foo() -> felt252 {
    let mut x : felt252 = 0;
    loop {
        if (x == 12) {
            break();
        };
        x += 3;
    };
    return x;
}

cairo-compile -r feltloop.cairo produces a Sierra file containing the following declarations:
feltloop::feltloop::foo@0([0]: RangeCheck, [1]: GasBuiltin) -> (RangeCheck, GasBuiltin, core::PanicResult::<(core::felt252,)>);
foo[expr10]@22([0]: RangeCheck, [1]: GasBuiltin, [2]: felt252) -> (RangeCheck, GasBuiltin, core::PanicResult::<(core::felt252, ())>);

The second function should be called feltloop::feltloop::foo[expr10] instead.

Was fixed a while back - sorry for the late update.


Adding await support

For what thing this feature?
Adding possibility for using await in send messages
Ideal solution
@bot.event
async def test(ctx):
    await ctx.send("Test!")

Not ideal but cool colution
None

Feature tasks:

[ ] Add using aiohttp
[ ] async and await replace
[ ] Add gets and posts for aiohttp

It is made :)


Add support for pure Python Poetry packages

This allows Poetry packages to be installed by Colcon even if they aren't also ROS packages. This was an artificial limitation in the first place whose only purpose was to add some additional correctness checks for ROS packages.
Fixes #29

Thanks. Generally, this seems to work. I only noticed that dependencies are not tracked.
When I call colcon graph --dot > deps.dot and look at the dependency graph via xdot deps.dot then all my packages are independent (there are no arrows connecting packages), although the section [tool.poetry.dependencies] lists one of the packages on the same workspace as a dependency.

Scripts under [tool.poetry.scripts] are installed to lib and not bin. This is different from pip, where those are installed to $HOME/.local/bin/.

@christian-rauch Thanks for testing colcon graph, I'll try to take a look at that this week. The lib behavior is not new and is, as far as I'm aware, necessary for ROS to see the binaries. It's done here.

The lib behavior is not new and is, as far as I'm aware, necessary for ROS to see the binaries. It's done here.

At least with CMake packages, there is a differentiation between regular executables from plain CMake packages and nodes from ament packages. For example, https://github.com/AprilRobotics/apriltag is a plain CMake package, that will install the demo executables apriltag_demo and opencv_demo in the folder install/apriltag/bin/, such that they can be called just by sourcing the environment.
For ROS-specific binaries or nodes, I think it would make sense to rely on a dedicated section in pyproject.toml that lists the ROS nodes. Otherwise, the installed scripts should be handled just like standard python scripts and executables.

With the usual python/ROS workflow, they have you set up scripts in the setup.py as normal scripts, and those are just assumed to be ROS executables. I think mirroring that workflow with poetry might be more clear for the users of the tool.

With the usual python/ROS workflow, they have you set up scripts in the setup.py as normal scripts, and those are just assumed to be ROS executables.

I experimented a bit with the setup.py and colcon-python-setup-py before and was able to install standard python packages including its executable. My plan with colcon-poetry-ros was to mirror this and poetry's behaviour by installing plain python packages alongside other colcon packages in the same way their native tools (cmake, poetry) would do.

I think mirroring that workflow with poetry might be more clear for the users of the tool.

It's a good question of what the expected behaviour should be :-) I thought that there actually should be a colcon-poetry and a colcon-poetry-ros extension for plain and ROS Python packages. My expectation on a "poetry" extension is that it behaves like normal poetry, just in a colcon workspace. I haven't looked too deep into this, but I assume that for creating a Python ROS node/package, you will have to add additional steps, such as message generation or launch file installation, anyway. So it would make sense to support standard poetry behaviour as a baseline with colcon-poetry and extend this by anything specifically required by ROS nodes with colcon-poetry-ros.

@velovix @apockill Are you interested in replicating the poetry behaviour where scripts and executables are installed in the bin folder?

Sorry for the delay on this Christian. You raise good points that require some thinking.

I thought that there actually should be a colcon-poetry and a colcon-poetry-ros extension for plain and ROS Python packages

I agree with this on principle and it would allow the project to better mirror the way Colcon's official extensions are developed. In practice it has some unfortunate knock-on effects where we would need to maintain two separate packages and perhaps two repositories, although I suppose we could maintain them in the same repository. Maybe that's the future of this project, but it seems a bit heavy for now.
One reason why it feels "heavy" to me is because there's actually very little ROS stuff we need to do in this extension. We don't need to worry about message generation, because that needs to be done with CMake, and we don't need to worry about launch file installation because that's handled elsewhere in the build process.

For ROS-specific binaries or nodes, I think it would make sense to rely on a dedicated section in pyproject.toml that lists the ROS nodes. Otherwise, the installed scripts should be handled just like standard python scripts and executables.

I tend to agree with @apockill that I would prefer to treat Poetry scripts and ROS nodes as equivalent to mirror Colcon's setup.py behavior and also because I think it's more intuitive. You have probably already noticed this, but the executables actually end up in both places. That seems to me like a good compromise, as it simultaneously fits Poetry's and ROS's expectations on where they should go.

A gentle ping :-) Do you think this is ready?

Thank you for the reminder! I got sidetracked on this while trying to fix the dependency issue you identified. Unfortunately, it's still a problem, but I'll leave that for another PR since that's not a regression from these changes. I'm happy where this one is.


⚠ Elibs has degraded performance

In acd1331, Elibs (https://elibs.unmer.ac.id) experienced degraded performance:

HTTP code: 200
Response time: 6341 ms

Resolved: Elibs performance has improved in 274408d.


Make public repository

Changes Unknown when pulling 6fd06761146e29e3269208c23d3bb8debecd23bf on make-public into ** on master**.

:rabbit2: :+1:


Add coding standards from SWA to Wiki

@Lariiii can this be closed?

Not yet, I will do that today.


currency filter, bug upon pressing tab key

using:

everytime i click tab key , the value changes in my input text. hope someone could help me on this. thanks in advance.

Vue.js version
2.0.2
Reproduction Link

Steps to reproduce
What is Expected?
What is actually happening?

Hi, please make sure to follow the Issue Reporting Guidelines before opening an issue. Thanks!


W1D3 Coding exercise 2. Wrong argument documentation

hidden_unit_nums should be a list of int, not int per function documentation

Hey @dungscout96 ! In which tutorial does this issue refer? Tutorial 1 or tutorial 2?

Our latest branch fixes this. Thanks for pointing out this issue @dungscout96. Much appreciated :)


Added glide dependency handling

Setup glide and modified the makefile

Looks good. Thank you for the update. And sorry it took so long to review... was totally focused on another project the last two weeks.


How do I update Files?

I couldn't find the feature to update it.
Do I have to delete current one and install latest?

If you installed it from Store or https://files.community/ it autoupdates. Latest stable version is <IP_ADDRESS>.


MM-47108 : Migrate "components/markdown_image/markdown_image.jsx" to Typescript

Summary
Migration of markdown_image fie from jsx to tsx
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/21062
Fixes  https://mattermost.atlassian.net/browse/MM-47108
Related Pull Requests
None
Screenshots
None
Release Note
NONE

Hello @babinderrathi,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

@babinderrathi hey gentle ping on this one :)

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

Heads up that as part of our efforts to move to a monorepo, we're closing out a number of older pull requests like this one to help streamline the effort.
If you'd like to preserve these changes -- even if you're not the original author! -- feel free to resubmit the pull request against the monorepo once it's ready. You can subscribe to mattermost-server-issue-22420 for status updates on this effort.


Cross-Origin Fetch Requests Failing Due to Missing Credentials Leading to 401 Unauthorized Errors

Expected Behaviour
When making a cross-origin fetch request, credentials (such as cookies) should be sent along with the request to ensure proper user authentication and session maintenance.
Actual Behaviour
Cross-origin fetch requests fail to include credentials, causing authentication to fail and leading to 401 Unauthorized errors.
Reproduce Scenario
Steps to Reproduce

Open the application in a browser.
Ensure the user is logged in on a different tab to establish an authenticated session.
Trigger a fetch request to a cross-origin domain that requires credentials.
Observe the request and response in the browser’s developer tools (Network tab).

Logs taken while reproducing problem

Closing as it worked with helix sidekick login.


Add javascript-v output

This generates a new pattern optimized for use with the upcoming v flag in JavaScript regular expressions. The pattern has the following format:
\p{RGI_Emoji}|other|emoji|here

Since we no longer have to directly embed any RGI_Emoji into the pattern, the overall pattern becomes much more compact:
 12909 dist/latest/javascript-u.txt
 11631 dist/latest/javascript.txt
  3146 dist/latest/javascript-v.txt

To be on the safe side, we look at the oldest possible Emoji standard supported across all browsers that support the v flag, and use the set of RGI_Emoji strings that corresponds to it. Since there are no v flag implementations yet, this version is currently assumed to be Emoji 14. This means that, in the future, the generated pattern might start to contain hardcoded strings that are technically redundant for that given version of the Emoji standard — but this is done intentionally so that the pattern still behaves equivalently on older browsers where \p{RGI_Emoji} resolves to an older Emoji version.
More info on the RegExp v flag proposal: https://github.com/tc39/proposal-regexp-set-notation
Issue: #15

8e73efecdf88113a22a6914e5d33663e51269d07 lowered the LCD version to Emoji 13 (i.e. the oldest version supported by this project), since it’s required to ensure the older patterns behave correctly.


AdaptivePoolingAllocator EventLoop Magazine's affinity

Motivation:
AdaptivePoolingAllocator uses some shared Magazines hoping thread's id distribution to improve contended behaviour, but event loops threads can just uses their own Magazine(s) and save 2 atomic operations (write lock/unlock) in the hot path, further improving performance.
Modification:
Implements dedicated event loop Magazines
Result:
Better allocation performance for event loop threads

@chrisvest @normanmaurer Similarly to what I've done for https://github.com/quarkusio/quarkus/blob/ca27e0c29d9ae048227da8118c61ef3215fe6266/independent-projects/resteasy-reactive/server/vertx/src/main/java/org/jboss/resteasy/reactive/server/vertx/AppendBuffer.java#L21 we can use a JDK 8 MethodHandle::invokeExact and explicitly save ThreadLocal(s) for virtual thread(s) too, but I didn't pushed this here.

Thanks @chrisvest and sorry for arriving late

I'm sending an additional commit to further improve performance @chrisvest, but i didn't yet added specific tests or benchmarks on this, yet.

Perf wise, I've profiled ByteBufAllocatorBenchmark and given that is an uncontended case, I see that the dominant costs are instead the many others atomic ops to increase/decrease the ref cnt shared on the chunk buffer; due to this the uncontended case with 256 bytes and direct buffer have just a small improvement i.e. 23 M ops/sec ->  25 M ops/sec
Where instead I think it would very beneficial, is with the concurrent scenario in the real world, because there won't be any retry due to contention or expansion going on for event loop magazines, given that are not shreable, but I don't have any performance test around such yet.

@franz1981 please fix

@normanmaurer hope to have addressed the comments
I still believe, for the hot path vs event loops we could do much better, but I need to better understand how this work: the ChunkByteBuf uses a costy retain method to bump the allocation out of it, but in theory this should be fully uncontended, because it is either protected by a lock or not shared: maybe there is something we can do there to split the ref cnt for ChunkByteBuf into 2 parts, making the retain much less costy, using something which doesn't imply strong memory barriers, but I need to better understand the allocator, I think

The ChunkByteBuf.retain() call coordinates with the deallocations of allocated ByteBuf instances, which can happen in any thread because buffers are not confined.

Yep @chrisvest that's why I proposed 2 separate counters (up and down): so they can be updated with different ordering mode. We usually decide for the subsequent deallocation of the chunk when its capacity is exhausting (on the last adaptive buffer we slice out of it - which is still in the allocation path), and maybe this can be used at our advantage. I have to better think if I am saying something just not possible, but I will give it a shot in the next days or in another pr.
This one, as it is already deliver a decent improvement, which can likely get better under magazine sharing (which cannot happen anymore  between event loops).

@chrisvest this is what I meant (@normanmaurer too):
https://github.com/franz1981/netty/commit/724d7540d3d2b955e47b48ddad8dbe0ba9c6a9db
as you can see it is relaxing the ref cnt behaviour, but it shouldn't be more unsafe than what we have right now, given the constrains of the algorithm and it would enable super fast-path event loops allocations.
wdyt?
If it looks good I can port it on this branch as well...

@franz1981 I think that looks interesting. I'd like to think it through independently and see what the build says, so I still prefer it being a separate PR.

ready to go @normanmaurer too?
I'll send the ref cnt changes in a separate PR, which speedup quite a lot the event loops allocation ;)

@chrisvest I can send some more test or a better benchmark for this or it is ready to go?

I think this is ready. Was just waiting to see if Norman had anything, but I think we can merge it

Cherry-picked into 4.2 ... @franz1981 do you mind opening a PR against main ?

Will take tomorrow folks, dealing with some other things these days..and will send the ref cnt proposal @chrisvest which clearly relax something but for a very real positive performance impact, but I can make it opt-in (I believe)


Model loading prior to starting the app

WWW
As a developer running the app, the speech recognition model now is loaded in multiple places. It would be good to load the model once into memory prior to the start of the application before inference is run and not load it every time inference needs to be run. This makes things really slow.
AC
A pull-request with code changes where the model is loaded just once and used in multiple places wherever inference needs to be run.

I am deleting some of the speech recognition code to make it all a bit lighter


ISPN-9320 Hot Rod protocol client / server handshake

https://issues.jboss.org/browse/ISPN-9320
WARNING: this was a quick rebase. Since @gustavonalle made changes to the PING response in protocol 2.9, I need to adapt my code to that.

Is this being target for final? It seems we should postpone to 10.0.0 as this is a change in the protocol with potential side effects for clients

Yes, this is for 10

And we should probably bump the protocol to 3.0

This is now ready. I've greatly simplified the original proposal by folding the changes into the PING operation. The bug I uncovered wrt topology changes closing the channel before processing the whole operation will be resolved in https://issues.jboss.org/browse/ISPN-9827