image fails to run on Mac OSX 10.9

I was trying to use the image library, but this happens:
➜  ~  th -limage
> image.lena()
Wrong JPEG library version: library is 80, caller expects 62
/usr/local/share/lua/5.1/image/init.lua:115: attempt to index local 'a' (a nil value)
stack traceback:
    /usr/local/share/lua/5.1/image/init.lua:115: in function 'loader'
    /usr/local/share/lua/5.1/image/init.lua:247: in function 'load'
    /usr/local/share/lua/5.1/image/init.lua:1007: in function 'f'
    [string "local f = function() return image.lena() end ..."]:1: in main chunk
    [C]: in function 'xpcall'
    /usr/local/share/lua/5.1/trepl/init.lua:510: in function </usr/local/share/lua/5.1/trepl/init.lua:452>
>

I have no idea how to fix that.

I had a similar problem. Upgrading lua to 5.2.3 solved it for me.

issue still there on MacOS Yosemite
th -limage -e "image.lena()"
Wrong JPEG library version: library is 80, caller expects 62

I had same problem in 10.10.2, and I try to upgrade the lua to Lua 5.3.0 to solve it, but the torch still run version 5.1.

I have the latest version of everything (brew, libjpg and image) and everything works just fine.
I guess we can close this issue.

After trying many things, I solved this in torch only using PNG files

-- Found JPEG: /Users/bakercp/anaconda/lib/libjpeg.dylib
-- Found ZLIB: /Users/bakercp/anaconda/lib/libz.dylib (found version "1.2.8")
-- Found PNG: /Users/bakercp/anaconda/lib/libpng.dylib (found version "1.5.18")
Pretty much what happened to me except it was getting built with my Postgres' libjpef.dylib. I just went into my bash profile and took that off my path where I was exporting it, then rebuilt with luarocks install image, and it worked after that! Check the logs when you run luarocks install image because thats where I was it was using a possibly out of date version of libjpeg. Strangely, my anaconda's libjpeg.dylib (which it linked too after I changed my PATH) works fine and built image without any problems.

The solution of @JohnZed worked for me. This JPEG library was installed with GDAL and caused a conflict. Simply deleting it fixed the issue.

On my mac system the following solved the issue.
brew unlink jpeg
brew link homebrew/versions/jpeg6b
luarocks install image

after this the following command runs without issue
th -limage -e "image.lena()"

hi guys, i am sure this is so redundant but I have no other choice but bringing up the issue and asking for help as of how to deal with it.
So, when I try image.lena(), I get this typical error:
Wrong JPEG library version: library is 80, caller expects 90
Now, as far as i understood from this and so many other posts, there is some sort of conflict, I used JohnZed's feedback above and found that I have so many versions of lipjpeg, here is what I have:
find /usr/ /Library/ /opt/ /lib/ -iname "libjpeg*.dylib" 2>/dev/null
the above gives the following output:
/usr//local/Cellar/jpeg/8d/lib/libjpeg.8.dylib
/usr//local/Cellar/jpeg/8d/lib/libjpeg.dylib
/usr//local/Cellar/jpeg9/lib/libjpeg.9.dylib
/usr//local/Cellar/jpeg9/lib/libjpeg.dylib
/usr//local/mac-dev-env/libjpeg-9b/lib/libjpeg.9.dylib
/usr//local/mac-dev-env/libjpeg-9b/lib/libjpeg.dylib
/usr//local/octave/3.8.0/lib/libjpeg.9.dylib
/usr//local/octave/3.8.0/lib/libjpeg.dylib
/Library//Frameworks/GTK+.framework/Versions/2.24.X11/Resources/lib/libjpeg.9.dylib
/Library//Frameworks/GTK+.framework/Versions/2.24.X11/Resources/lib/libjpeg.dylib
/Library//Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/lib/libjpeg.dylib
/Library//Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libjpeg.dylib
Before I go ahead and delete or modify any of the above versions, what would be the best approach to solve this problem?
Thanks a lot

For me, I ran into similar problems with
luajit -limage -e "image.test()"
seed:<PHONE_NUMBER>
Running 41 tests
 1/41 CompressAndDecompress ............................................. [PASS]
 2/41 test_transformation_largeByteImage_vflip .......................... [PASS]
 3/41 CompressAndDecompressPNG .......................................... [WAIT]libpng warning: Application built with libpng-1.4.12 but running with 1.6.29
 3/41 CompressAndDecompressPNG .......................................... [ERROR]

...

CompressAndDecompressPNG
 Function call failed
/Users/david/src/torch/install/share/lua/5.1/image/init.lua:215: [write_png_file] png_create_write_struct failed
stack traceback:
	[C]: in function 'save'
	/Users/david/src/torch/install/share/lua/5.1/image/init.lua:215: in function 'compressPNG'
	/Users/david/src/torch/install/share/lua/5.1/image/test.lua:419: in function </Users/david/src/torch/install/share/lua/5.1/image/test.lua:416>
	[C]: in function 'xpcall'
	...s/david/src/torch/install/share/lua/5.1/torch/Tester.lua:477: in function '_pcall'
	...s/david/src/torch/install/share/lua/5.1/torch/Tester.lua:436: in function '_run'
	...s/david/src/torch/install/share/lua/5.1/torch/Tester.lua:355: in function 'run'
	/Users/david/src/torch/install/share/lua/5.1/image/test.lua:708: in function 'test'
	(command line):1: in main chunk
	[C]: at 0x010d8e6a00

which was finally resolved by following @JohnZed suggestion: search for stray libjpg files, and re-build luarocks install image.  In my case, I had an unused old Mono.Framework on the system.

Mono.framework causes CMake to produce an incorrect build due to libpng and libjpeg.
CMake has this funny parameter called CMAKE_FIND_FRAMEWORK which is set by default to FIRST. This means that CMake will first look for files first in all framework directories, and only then in regular include directories. Funnily enough Mono.framework contains the headers for libjpeg and libpng. So, CMake finds the headers in Mono, but the library in the regular install location, e.g. /usr/local/lib and therefore a version mismatch happens.
Mono is a known menace (for some time brew doctor warned if Mono is installed that builds may fail). You can see this behavior if you create a CMakeLists.txt file with the single line find_package(JPEG), run cmake . and take a look at the paths in the generated CMakeCache.txt file.
The fix that definitively worked for me was to check out the project manually, add set(CMAKE_FIND_FRAMEWORK LAST) to CMakeLists.txt before the find_package calls and then run luarocks make. This way CMake found the headers in the right folder.


Simplify deploy script

Remove a useless job
Clean up the script a bit

Coverage increased (+0.01%) to 82.593% when pulling ea69b4578b31ecd31fe6a0a7acc1273c8436317a on Luni-4:simplify-deploy into 03a11a268874a9b7adf23a519027cbe34a0f5e9c on xiph:master.

Thanks!


Closes: #1

fixed the check
Fixes #1

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Local source scaling

This fixes issue #170

Would this help/solve: https://github.com/EricssonResearch/openwebrtc/issues/150

No, this is unrelated to #150


TextView does not expose .foregroundColor(_:)

This is a result of a limitation in the public SwiftUI API. There is a radar open for this at FB7154926.


Version 3 of the architecture specific layers are not shared consistently across regions.

Versions

Lambda runtime: python 3.8
Lambda extension: honeycomb-lambda-extension

Steps to reproduce

Create a function using the us-east-1, x86_64 layer shown in this table
You should get a failure!

Additional context
While testing out moving our Lambda functions to arm64, I updated the current honeycomb extension layers with the new architecture specific layers. However, when I did this in us-east-1, I was unable to access the layer! I wrote a quick script to help debug this, but it looks like there are two of the new architecture-specific layers that do not have the correct permissions on them to be used.
Script
#!/bin/bash

regions=("ap-northeast-1" "ap-south-1" "ap-southeast-1" "ap-southeast-2" "eu-central-1" "eu-west-1" "eu-west-2" "us-east-1" "us-east-2" "us-west-2")
architectures=("x86_64" "arm64")

for region in "${regions[@]}";do
    for arch in "${architectures[@]}";do
        layer_arn="arn:aws:lambda:$region:702835727665:layer:honeycomb-lambda-extension-$arch"

        result=$(aws lambda get-layer-version --layer-name "$layer_arn" --version-number 3 --region "$region" --profile <some-profile> 2>&1)

        if [[ $result == *"not authorized"* ]]; then
            echo "$region - $arch | No Permissions | $layer_arn"
        else
            echo "$region - $arch | OK | $layer_arn"
        fi
    done

    sleep 1s
done

Results
ap-northeast-1 - x86_64 | OK | arn:aws:lambda:ap-northeast-1:702835727665:layer:honeycomb-lambda-extension-x86_64
ap-northeast-1 - arm64 | OK | arn:aws:lambda:ap-northeast-1:702835727665:layer:honeycomb-lambda-extension-arm64
ap-south-1 - x86_64 | OK | arn:aws:lambda:ap-south-1:702835727665:layer:honeycomb-lambda-extension-x86_64
ap-south-1 - arm64 | OK | arn:aws:lambda:ap-south-1:702835727665:layer:honeycomb-lambda-extension-arm64
ap-southeast-1 - x86_64 | OK | arn:aws:lambda:ap-southeast-1:702835727665:layer:honeycomb-lambda-extension-x86_64
ap-southeast-1 - arm64 | OK | arn:aws:lambda:ap-southeast-1:702835727665:layer:honeycomb-lambda-extension-arm64
ap-southeast-2 - x86_64 | OK | arn:aws:lambda:ap-southeast-2:702835727665:layer:honeycomb-lambda-extension-x86_64
ap-southeast-2 - arm64 | OK | arn:aws:lambda:ap-southeast-2:702835727665:layer:honeycomb-lambda-extension-arm64
eu-central-1 - x86_64 | OK | arn:aws:lambda:eu-central-1:702835727665:layer:honeycomb-lambda-extension-x86_64
eu-central-1 - arm64 | OK | arn:aws:lambda:eu-central-1:702835727665:layer:honeycomb-lambda-extension-arm64
eu-west-1 - x86_64 | OK | arn:aws:lambda:eu-west-1:702835727665:layer:honeycomb-lambda-extension-x86_64
eu-west-1 - arm64 | OK | arn:aws:lambda:eu-west-1:702835727665:layer:honeycomb-lambda-extension-arm64
eu-west-2 - x86_64 | No Permissions | arn:aws:lambda:eu-west-2:702835727665:layer:honeycomb-lambda-extension-x86_64
eu-west-2 - arm64 | OK | arn:aws:lambda:eu-west-2:702835727665:layer:honeycomb-lambda-extension-arm64
us-east-1 - x86_64 | No Permissions | arn:aws:lambda:us-east-1:702835727665:layer:honeycomb-lambda-extension-x86_64
us-east-1 - arm64 | OK | arn:aws:lambda:us-east-1:702835727665:layer:honeycomb-lambda-extension-arm64
us-east-2 - x86_64 | OK | arn:aws:lambda:us-east-2:702835727665:layer:honeycomb-lambda-extension-x86_64
us-east-2 - arm64 | OK | arn:aws:lambda:us-east-2:702835727665:layer:honeycomb-lambda-extension-arm64
us-west-2 - x86_64 | OK | arn:aws:lambda:us-west-2:702835727665:layer:honeycomb-lambda-extension-x86_64
us-west-2 - arm64 | OK | arn:aws:lambda:us-west-2:702835727665:layer:honeycomb-lambda-extension-arm64

@roryj-vendia thanks for letting us know! we had a few issues with the last release 😬
can you try again with layer version 5? here's what we get:
ap-northeast-1 - x86_64 | OK | arn:aws:lambda:ap-northeast-1:702835727665:layer:honeycomb-lambda-extension-x86_64
ap-northeast-1 - arm64 | OK | arn:aws:lambda:ap-northeast-1:702835727665:layer:honeycomb-lambda-extension-arm64
ap-south-1 - x86_64 | OK | arn:aws:lambda:ap-south-1:702835727665:layer:honeycomb-lambda-extension-x86_64
ap-south-1 - arm64 | OK | arn:aws:lambda:ap-south-1:702835727665:layer:honeycomb-lambda-extension-arm64
ap-southeast-1 - x86_64 | OK | arn:aws:lambda:ap-southeast-1:702835727665:layer:honeycomb-lambda-extension-x86_64
ap-southeast-1 - arm64 | OK | arn:aws:lambda:ap-southeast-1:702835727665:layer:honeycomb-lambda-extension-arm64
ap-southeast-2 - x86_64 | OK | arn:aws:lambda:ap-southeast-2:702835727665:layer:honeycomb-lambda-extension-x86_64
ap-southeast-2 - arm64 | OK | arn:aws:lambda:ap-southeast-2:702835727665:layer:honeycomb-lambda-extension-arm64
eu-central-1 - x86_64 | OK | arn:aws:lambda:eu-central-1:702835727665:layer:honeycomb-lambda-extension-x86_64
eu-central-1 - arm64 | OK | arn:aws:lambda:eu-central-1:702835727665:layer:honeycomb-lambda-extension-arm64
eu-west-1 - x86_64 | OK | arn:aws:lambda:eu-west-1:702835727665:layer:honeycomb-lambda-extension-x86_64
eu-west-1 - arm64 | OK | arn:aws:lambda:eu-west-1:702835727665:layer:honeycomb-lambda-extension-arm64
eu-west-2 - x86_64 | OK | arn:aws:lambda:eu-west-2:702835727665:layer:honeycomb-lambda-extension-x86_64
eu-west-2 - arm64 | OK | arn:aws:lambda:eu-west-2:702835727665:layer:honeycomb-lambda-extension-arm64
us-east-1 - x86_64 | OK | arn:aws:lambda:us-east-1:702835727665:layer:honeycomb-lambda-extension-x86_64
us-east-1 - arm64 | OK | arn:aws:lambda:us-east-1:702835727665:layer:honeycomb-lambda-extension-arm64
us-east-2 - x86_64 | OK | arn:aws:lambda:us-east-2:702835727665:layer:honeycomb-lambda-extension-x86_64
us-east-2 - arm64 | OK | arn:aws:lambda:us-east-2:702835727665:layer:honeycomb-lambda-extension-arm64
us-west-2 - x86_64 | OK | arn:aws:lambda:us-west-2:702835727665:layer:honeycomb-lambda-extension-x86_64
us-west-2 - arm64 | OK | arn:aws:lambda:us-west-2:702835727665:layer:honeycomb-lambda-extension-arm64

Just tested it out, and looks like v5 is working. I am going to try deploying this new layer now, thanks for the speedy response!

We're also eating our own dogfood and confirm this is now working as another lambda extension consumer!


Are there any excellent github projects on action recognition implemented by TF2?

I have been searching for official or non-official awesome code projects of action recognition written by TF2 for a long time, but unfortunately fail. I'd like to integrate video classification with other TF2 elements more conviniently. The most majority of video-relevant resources are under the community of Pytorch, though only a few projects were done by TF1, which seem fairly passe and only attract very few stars. Since the TF 2.X version has been released for over 2 years, why does its current ecosystem yet appear to be frustrated? Does anybody else cope with similar questions?

Did you see action recognition with tf hub using i3d tutorial?

Did you see action recognition with tf hub using i3d tutorial?

Did you see action recognition with tf hub using i3d tutorial?

Thanks. Looking forward to more elaborate official tutorials and demos by TF2

Did you see action recognition with tf hub using i3d tutorial?

Thanks. Looking forward to more elaborate official tutorials and demos by TF2


List type is not converted to integer[] DBType when used in parameter

Within statement as below,
VALUES (@p1174, @p1175, @p1176, @p1177, @p1178, @p1179, @p1180, @p1181, @p1182, @p1183, @p1184, @p1185);       INSERT INTO "Segments" ("ZoneX", "ZoneZ", "SiteIndex", "SegmentIndex", "BusinessKey", "CenterFromZoneCount", "CenterFromZoneX", "CenterFromZoneZ", "Chunks", "OwnerId", "ShopId", "StoreyLimit")
@p1194='System.Collections.Generic.List1[System.Int32]' (DbType = Object)`
List type is converted to Object DBType, not array type.
dotnet ef migrations generates ddl correctly as column of integer[],
but on insert statement parameter type is not converted correctly showing error as below
Npgsql.PostgresException (0x80004005): 0A000: unsupported result type: int
Installed versions are as below.
Npgsql.EntityFrameworkCore.PostgreSQL
Installed versions : 2.0.1
Npgsql.EntityFrameworkCore.PostgreSQL.Design
Installed versions : 2.0.0-preview1
Microsoft.EntityFrameworkCore
Installed versions : 2.0.1
Microsoft.EntityFrameworkCore.Design
Installed versions : 2.0.1
Database: cockroachDB v2.0-alpha.20180212

Sorry for the time it took me to look into this.
First, you should remove Npgsql.EntityFrameworkCore.PostgreSQL.Design - that package is no longer necessary (no 2.0.0 was ever published).
The following works fine for me:
public class Blog
{
    public int Id { get; set; }
    public string Name { get; set; }
    public int[] Tags { get; set; }
}

using (var ctx = new MyDbContext())
{
    ctx.Database.EnsureDeleted();
    ctx.Database.EnsureCreated();

    ctx.Blogs.Add(new Blog { Name = "foo", Tags = new[] { 5, 6, 7 } });
    ctx.SaveChanges();
}

Please submit a small repro showing what exactly isn't working.

Thanks for reply! My Repro case are as below.
Entity and test code.
public class Chunks
{
    public int Id { get; set; }
    public int[] ChunkList { get; set; }

     public Chunks() {}
}

protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    modelBuilder.Entity<Chunks>().HasKey(c => c.Id);
}

using (var context = new MarsContext())
{
    var chunk = new Chunks();

    chunk.Id = 1;
    chunk.ChunkList = new int[] {1, 2, 3};

    context.Chunks.Add(chunk);

    context.SaveChanges();
}

DDL Generated with dotnet ef migrations / database update (worked as intended)
CREATE TABLE "Chunks" (
	"Id" INT NOT NULL DEFAULT unique_rowid(),
	"ChunkList" INTEGER[] NULL,
	CONSTRAINT "PK_Chunks" PRIMARY KEY ("Id" ASC),
	FAMILY "primary" ("Id", "ChunkList")
)

Result Log
dbug: Microsoft.EntityFrameworkCore.Database.Command[20100]
      Executing DbCommand [Parameters=[@p0='1', @p1='System.Int32[]' (DbType = Object)], CommandType='Text', CommandTimeout='30']
      INSERT INTO "Chunks" ("Id", "ChunkList")
      VALUES (@p0, @p1);
fail: Microsoft.EntityFrameworkCore.Database.Command[20102]
      Failed executing DbCommand (35ms) [Parameters=[@p0='1', @p1='System.Int32[]' (DbType = Object)], CommandType='Text', CommandTimeout='30']
      INSERT INTO "Chunks" ("Id", "ChunkList")
      VALUES (@p0, @p1);
Npgsql.PostgresException (0x80004005): 0A000: unsupported result type: int

The test code is not much different from your example. Because I use CockroachDB, not Postgres, The problem is may be CockroachDB specific case.

As expected, I tried running your exact code on PostgreSQL and it worked fine.
I'd suggest looping in someone from Cockroach to look at this issue...

https://github.com/cockroachdb/cockroach/issues/24055 seems to be closed, so there's a chance this works now, hopefully someone can test. Will close for now, and reopen if there's still an Npgsql-side issue.


Avoid Installating dependencies while creating the project

Hi there! new-web-app's so I suppose it mustnt install the dependencies , it needs to just set the project dir and put the package.json like vite's cli tool does. I use pnpm instead of yarn and its much faster! Also it comes with tsx template by default , how do I use js? :c

Hi @siduck
Thank you for filing an issue. I could support pnpm along with yarn but I don't want to support JS template.

Hi @siduck
Thank you for filing an issue. I could support pnpm along with yarn but I don't want to support JS template.

oh . Idk tsx so asked about it :(

I see. If so, could you open a pull request about it? Thanks

I see. If so, could you open a pull request about it? Thanks

hmm nvm , too dumb of me to assume that this supports ts only lol so I thought i wouldnt be able to do js in it but later realized we can :laughing:


Add some tests to safer-ffi-gen-macro

Basic testing to ensure that the output actually is valid

I think this can be closed as resolved by #33 and other PRs that introduced tests.


Task unification: reuse serializer

Coverage increased (+0.04%) to 93.815% when pulling a4dfe25ef337838562d2b5200e54d053ba4e4739 on task-unification-todo-viewset-reuse-serializer into 44eb6705d765a2ebe68f97f270ce68a3bb65eb60 on main.


Refactor io.Reader/Writer and []byte methods to delegate to each other

Can MaxSize() just be Size()? No. The only point of MaxSize() is so the user can preallocate a buffer to use for Put(buf, value).
Can RequiresTerminator() simply be size < 0? Exceptions:

empty: req term, size = 0
*fixed-size-type: NOT req term, size = 1 or 1 + size(referent)
*big.Int, *big.Rat: NOT req term, size ???

wrt the general task, whichever way makes more sense or is more performant (benchmark!).

[ ] Read/WritePrefix
[ ] empty
[ ] bool
[ ] uint*
[ ] int*
[ ] float*
[ ] complex*
[ ] string
[ ] time
[ ] duration
[ ] big.*
[ ] bytes
[ ] pointer
[ ] slice
[ ] map
[ ] negate
[ ] terminate
[ ] add helper methods to allow users to go in either direction
[ ] example_*.go
[ ] package docs
[ ] README

If it turns out that the I/O methods almost always delegate to []byte ones, then consider removing them entirely and provide some helper functions for that use case.
Big Issue to Resolve
If the user is actually working with an I/O stream, nillable Codecs and those requiring a terminator are impossible without some additional code on the user's part.
Unless those are additional methods on those specific Codecs? For fixed-length Codecs, using Size() would be sufficient for a (non-member) helper function.

empty
string
bytes
pointer
slice
map
big.*

I think lexy is going to abandon the io.Reader/Writer API entirely. There will be a couple adapter functions, but that's it.
If I decide to not do this, this issue can be reopened.


Home file variables - envrionment variable issue

Minimal .gitlab-ci.yml illustrating the issue
Here is my local variable config (/home/$USER/.gitlab-ci-local/variables.yml):
project:
  gitlab.fr/exemple:
    MY_EXEMPLE_VAR:
      type: variable
      values:
        '*': not_production_value
        'prod': production_value

Here is an exemple CI job:
---
job:
  environment:
    name: preproduction
  script:
    -  echo "${MY_EXEMPLE_VAR}"

This will output:
job       $ echo "${MY_EXEMPLE_VAR}"
job       > production_value

The variable MY_EXEMPLE_VAR take the prod value while I was expecting it to take the * value.
Expected behavior
I would expect:
job       $ echo "${MY_EXEMPLE_VAR}"
job       > not_production_value

Host information
Debian 11
gitlab-ci-local 4.41.2
Additional context
My assumption is that the check on the environment is valid if the variable file environment value is a substring of the job environment value.
In my exemple above: prod is a substring of preproduction.
For exemple, I tested to updated the value of the home file variable environment:
project:
  gitlab.fr/exemple:
    MY_EXEMPLE_VAR:
      type: variable
      values:
        '*': not_production_value
        '__prod__': production_value

And now my variable is set to the rigth value.

This is definently a bug


publisherUserId isn't optional

The docs say publisherUserId is optional, but it isn't (it must be set in code)

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

ID: 13f85bf6-849d-020a-7c1b-fc949e102eee
Version Independent ID: 26ce2d38-6da1-59f2-88dd-f386ba61f2e1
Content: StoreContext.GetCustomerPurchaseIdAsync(String, String) Method (Windows.Services.Store) - UWP app developer
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.services.store.storecontext.yml&version=GBlive&_a=contents
Product: windows
Git Login: wdg-dev-content
Microsoft Alias: wdg-dev-content

Thanks for your feedback. I have revised the description for this parameter to clarify that it is not optional.


update secret command

When I use the new feather secret, I find the secret commands and secret docs don't match well,   especially toward secret inspect command , the docs shows users can inspect one or more secrets while the command shows users can only inspect a secret. so I refine the incorrect part to make docs and commands match well.
- What I did
- How I did it
- How to verify it
- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: erxian<EMAIL_ADDRESS>

I am afraid this pr did not trigger the CI. @thaJeztah

Issue here is, the commans should be doing what the doc says, which is consistent with the other subcommands.

@cpuguy83  Hi, the modified commands just match the docs description. Here are the secret docs details:
secret_creat.md
# secret create

Usage:  docker secret create [OPTIONS] SECRET

secret_inspect.md
# secret inspect

Usage:  docker secret inspect [OPTIONS] SECRET [SECRET...]

Display detailed information on one or more secrets

secret_ls.md
# secret ls

Usage:	docker secret ls [OPTIONS]

secret_rm.md
# secret rm

Usage:	docker secret rm SECRET [SECRET...]

Remove one or more secrets

BTW,  towards the secret inspect commands, the modified part has passed the binary make, and could works normally when inspect multiple secrets : )

ping @ehazlett

Inspect should support multiple secrets as the other inspect commands do.  I'll take a look.

@ehazlett  That's great, thanks for your time.  And here is my docker environment.
docker version:
Client:
 Version:      1.13.0-rc1
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   75fd88b
 Built:        Fri Nov 11 19:41:05 2016
 OS/Arch:      linux/amd64

Server:
 Version:             1.13.0-rc1
 API version:         1.25
 Minimum API version: 1.12
 Go version:          go1.7.3
 Git commit:          75fd88b
 Built:               Fri Nov 11 19:41:05 2016
 OS/Arch:             linux/amd64
 Experimental:        false

docker info:
Containers: 25
 Running: 0
 Paused: 0
 Stopped: 25
Images: 111
Server Version: 1.13.0-rc1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 141
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: active
 NodeID: k3sj8v8mm49cw998wthwpzqz3
 Is Manager: true
 ClusterID: lw36g9p3yneoqqxrvf0tlifjv
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8517738ba4b82aff5662c97ca4627e7e4d03b531
runc version: ac031b5bf1cc92239461125f4c1ffb760522bbf2
init version: N/A (expected: v0.13.0)
Security Options:
 apparmor
Kernel Version: 3.13.0-100-generic
Operating System: Ubuntu 14.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.861 GiB
Name: 10-11-11-54
ID: LJ7Q:CII3:2HUV:5EJK:GEEO:5MD3:36NZ:RLIJ:L3DG:IMI2:NFHC:C7ME
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

@ehazlett Hi, ehazlett     I've  seen the new PR "Update secret inspect to support IDs",   and your consideration is much more adequate 👍 .   However the secret commands still not match it's docs description, could you please check this PR (#28576) again ?

Sure. I'll carry this one. Thanks!
On Nov 22, 2016 11:10 PM, "Evelyn.Xu"<EMAIL_ADDRESS>wrote:

@ehazlett https://github.com/ehazlett Hi, ehazlett I've seen the new PR
"Update secret inspect to support IDs", and your consideration is much more
adequate 👍 . However the secret commands still not match it's docs
description, could you please check this PR (#28576
https://github.com/docker/docker/pull/28576) again ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/pull/28576#issuecomment-262431219, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAP6IoNkSVgiB4kjr8qETKrYB1QZjJhAks5rA7yogaJpZM4K2Nf7
.


Code that typechecks normally from the command line can crash fstar-mode

The following code (put in a file called Foo.fst) can be typechecked normally with the
fstar.exe Foo.fst

command, but when the last line is typechecked in fstar-mode, it crashes and the subprocess must be killed.
module Foo

open FStar.Buffer

let wat buff =assert( buff.(0ul) % 2 = 0)

Also, the following error message appears in emacs : "error in process filter : Not enough arguments for format string".

Thanks for the report!


Improve header hierarchy for utils documentation

Groups functions into sections

This provides better structure for users rather than being a flat list. Each section header corresponds to a specific module.
Using these h2 headers also improves the accessibility of the docs with IQP. In qiskit/documentation, functions have an h3 generated for them like this:

We generate this h3 so that
a) it shows up in the right page table of contents, and
b) the app automatically generates an anchor link buton

But accessibility guidelines say that you should avoid jumping from an h1 to h3 because it makes screen readers work worse.
Fixes Optional Dependency Checkers to be h2
It was being set as an h3 because of using === as the header rather than ---. Note that Sphinx doesn't have any predetermined heading value for === vs ---. It determines what it corresponds to based on what shows up first in the document. Here, --- shows up first, so it was an h2, whereas === was an h3.
This issue was causing all subheaders to be one heading level lower than they should be.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.02%) to 89.31%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
4
91.69%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
59125

Relevant Lines:
66202

💛  - Coveralls

Oh dear, that test error is #11676, except it just happened on Python 3.8 / Numpy 1.24.4, which we thought couldn't happen.

Thanks, Jake. FYI I opened up https://github.com/Qiskit/documentation/issues/942 to track auditing all the other module pages.


Support running with TrustedTypes enforced.

Description of the Change
Trusted Types is a new Content Security Policy specification,
currently implemented in browsers based on Chromium 83 or higher, which
requires that data passed to APIs which may result in arbitrary code
execution must go through an explicit policy. This helps to catch
unintended use of dangerous APIs, and reduces the surface area for
some security reviews.
I'm not sure if test infrastructure like mocha is a likely target
for attack – seems like in most cases an attacker could only access test
data, and it is rare for tests to handle untrusted data. However,
there's value for infrastructure to be compatible with running with
Trusted Types enabled, as it will allow users to write tests to ensure
that the code under test can run with Trusted Types.
This change creates and applies policies for the two places in mocha
that call innerHTML, and adds a temporary patch to the rollup build.
With those changes in place, we can run mocha's karma tests with
Trusted Types enabled (save for the one test that runs with requirejs,
which relies on eval).
Alternate Designs
It would be possible to integrate dompurify into the HTML reporter, which would make it more secure. Alternatively, it may be possible to do a larger refactoring to construct the HTML output in a more structured way, rather than using string concatenation of HTML.
Why should this be in core?
This must be in core in order for these parts of core to be trusted types compatible.
Benefits
Users will be able to test their code with mocha in a browser with native Trusted Types enforcement enabled.
Possible Drawbacks
This change adds additional code, which adds weight to the mocha package for users, and maintenance burden on the mocha core devs.
Our own dependencies may inadvertently break us by doing otherwise safe operations (e.g. eval(str), Function(str), setting innerHTML, etc).
This is an enhancement (minor release).
More info and related work

Spec: https://w3c.github.io/webappsec-trusted-types/dist/spec/#introduction
Related PR adding support to karma: https://github.com/karma-runner/karma/pull/3360

Coverage increased (+0.007%) to 93.966% when pulling 614e23d83934736e84d26756bc00484dde369c96 on rictic:trustedTypes into 738a57574f3eb82ba2844c8a512cafec974ed5ab on mochajs:master.

Further, I think it'd be good to see a test which asserts the behavior works as intended.

My main question is: if a test is written using eval(), and we ship this change, will the test now fail when run in a Trusted-Types-supporting browser? If so, this behavior must be opt-in. And if it needs to be opt-in, does this defeat the purpose?

Trusted type enforcement is opt in. Like other CSP features, you enable it with either an HTTP header or with a <meta> tag in the page's <head>.
The change should have no effect on existing tests, which won't have opted into enforcing Trusted Types.
Shipping this change will make mocha compatible with trusted types, so it will enable testing with mocha with TT enforced. See e.g. https://github.com/Polymer/lit-html/pull/1323

Further, I think it'd be good to see a test which asserts the behavior works as intended.

See the changes to karma.conf.js, which adds headers to enable Trusted Type enforcement for mocha's existing browser tests (in supporting browsers, which is currently browsers based on a recent Chromium like Brave, Chrome, and Edge).

Further, I think it'd be good to see a test which asserts the behavior works as intended.
See the changes to karma.conf.js, which adds headers to enable Trusted Type enforcement for mocha's existing browser tests (in supporting browsers, which is currently browsers based on a recent Chromium like Brave, Chrome, and Edge).

sorry, what I meant was that the existing tests assert compatibility, but we do not have:

a test asserting some sort of exception is thrown when unsafe code is run
a test asserting no such exception is thrown when unsafe code is run

(AppVeyor is no longer building our PRs; I've removed it from the list of checks)

I'm not 100% sure I follow. You'd like to see a test of native Trusted Types functionality? A test that only runs in Chromium browsers and would fail if the trusted types headers in karma.conf.js didn't result in TT being enforced?

I'm not 100% sure I follow. You'd like to see a test of native Trusted Types functionality? A test that only runs in Chromium browsers and would fail if the trusted types headers in karma.conf.js didn't result in TT being enforced?

Yes, essentially:

a test that runs in Chromium that asserts "unsafe" code will break
a test that runs either in Chromium w/ the headers disabled, or somewhere else that lacks support, and asserts "unsafe" code does not break

The point is not to test the browser feature--I'm sure Chromium has plenty of tests--but rather to establish a baseline of behavior which Mocha will exhibit when encountering these configurations.  We need to make sure that future changes in Mocha do not violate the assumptions of its behavior established here.

I need to run TrustedTypes.

@rictic are you able to continue on this PR?

👋 coming back to this @rictic, are you still interested in working on this PR? As of https://github.com/mochajs/mocha/issues/5027 there are again maintainers who can review it now. No worries if you no longer have time - but if you do that'd be great!

I would still like to see this resolved, especially as Webkit has decided to support the standard as of two weeks ago: https://github.com/WebKit/standards-positions/issues/186#issuecomment-2172422968 and Mozilla as of Dec 2023: https://github.com/mozilla/standards-positions/issues/20#issuecomment-1853427823


chore: release main

:robot: I have created a release beep boop
accesskit_c: 0.1.1
Dependencies

The following workspace dependencies were updated

dependencies

accesskit_windows bumped from 0.13.3 to 0.14.0
accesskit_macos bumped from 0.6.3 to 0.7.0
accesskit_unix bumped from 0.3.3 to 0.4.0

accesskit_consumer: 0.15.0
0.15.0 (2023-03-30)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)

Bug Fixes

Force a semver-breaking version bump in downstream crates (#234) (773389b)

accesskit_macos: 0.7.0
0.7.0 (2023-03-30)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)

Bug Fixes

Force a semver-breaking version bump in downstream crates (#234) (773389b)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit_consumer bumped from 0.14.2 to 0.15.0

accesskit_unix: 0.4.0
0.4.0 (2023-03-30)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)

Bug Fixes

Force a semver-breaking version bump in downstream crates (#234) (773389b)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit_consumer bumped from 0.14.2 to 0.15.0

accesskit_windows: 0.14.0
0.14.0 (2023-03-30)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)

Bug Fixes

Force a semver-breaking version bump in downstream crates (#234) (773389b)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit_consumer bumped from 0.14.2 to 0.15.0

accesskit_winit: 0.13.0
0.13.0 (2023-03-30)
⚠ BREAKING CHANGES

Force a semver-breaking version bump in downstream crates (#234)

Bug Fixes

Force a semver-breaking version bump in downstream crates (#234) (773389b)

Dependencies

The following workspace dependencies were updated

dependencies

accesskit_windows bumped from 0.13.3 to 0.14.0
accesskit_macos bumped from 0.6.3 to 0.7.0
accesskit_unix bumped from 0.3.3 to 0.4.0

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/AccessKit/accesskit/releases/tag/accesskit_consumer-v0.15.0 :sunflower:

:robot: Release is at https://github.com/AccessKit/accesskit/releases/tag/accesskit_macos-v0.7.0 :sunflower:

:robot: Release is at https://github.com/AccessKit/accesskit/releases/tag/accesskit_unix-v0.4.0 :sunflower:

:robot: Release is at https://github.com/AccessKit/accesskit/releases/tag/accesskit_windows-v0.14.0 :sunflower:


cleanup unwanted kwargs for transport

API change check
API changes are not detected in this pull request.

/azp run python - keyvault - tests


Add support for lombok @Builder.Default Annotation

What's changed?
Added support for lombok Annotation @Builder.Default
What's your motivation?
Issues
The JavaParser fails to parse source files containing the @Builder.Default annotation.

The Lombok handler for @Builder sets the init expression to null for fields annotated with @Builder.Default. As a result, the AST-to-LST converter never see this init expression, since it was removed from the original code.
The Lombok handler uses a hack to convert @Builder.Default into a fully qualified name, which disrupts the AST positions.

Fix

Added logic to Remove the @Builder.Default annotation before invoking the Lombok @Builder handler and restored the original value after processing.
Updated the @Builder.Default annotation handler to NoOp, as it doesn't produce any output necessary for type attribution.

Checklist

[x] I've added unit tests to cover both positive and negative cases
[ ] I've read and applied the recipe conventions and best practices
[x] I've used the IntelliJ IDEA auto-formatter on affected files

I was reading a reddit thread, found claim of lombok creator that lombok does't modify existing ones.
https://www.reddit.com/r/java/comments/170gdha/comment/k3lq6p4/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
In this case, this issue is a design bug for Builder.Default annotation.


Use real emoji in the Git log

on the terminal, all I see is things like :tada: instead of 🎉.
0/10 will not use this CSS.

Too many people already rely on this repository, amending commit names and force-pushing would potentially break thousands of websites...
We'll keep your suggestion in mind for a V2.


Allow run time variable for useHash in RouterModule

Bug Report or Feature Request (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request

Area
- [ ] devkit
- [ ] schematics

Versions
Node v8.11.1.
NPM 5.6.0.
Windows 10.
Angular CLI: 1.6.5
OS: win32 x64
Angular: 5.2.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
@angular/cli: 1.6.5
@angular-devkit/build-optimizer: 0.0.41
@angular-devkit/core: 0.0.28
@angular-devkit/schematics: 0.0.51
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.5
@schematics/angular: 0.1.16
typescript: 2.6.2
webpack-bundle-analyzer: 2.9.2
webpack: 3.10.0
Repro steps
Given the following:
        // Workaround for IE 9 - have to use # location strategy
        RouterModule.forRoot(appRoutes, { useHash: !history.pushState })

when compiled using
ng build --prod

And loading on a modern Chrome browser I find I am using the hash location strategy.
The log given by the failure
No console or error logs.
Desired functionality
When I use a variable in the root AppModule.ts for the hash location strategy it seems to be ignored and is compiled to true. It should be variable and available at run time.
Mention any other details that might be useful
To support IE 9 with Angular we have to always use hash location strategy which is annoying. We should only have to punish IE 9 users with an inferior URL, not everyone.

The AOT compiler processes and compiles the Angular metadata at build time.  This is not something the CLI can control.  Disabling AOT is an option but this will result in a less optimized final build.  Asking for help on a site such as stackoverflow may be a prudent option.

@NgModule
({
  ...
  imports:
  [
   ...,
   AppRouterModule, //  RouterModule.forRoot( ROUTES...
  ],
  providers:
  [
    {
      provide: LocationStrategy,
      useFactory: ( inj: Injector ) => !history.pushState
        ? new HashLocationStrategy( inj.get(PlatformLocation), inj.get(APP_BASE_HREF) )
        : new PathLocationStrategy( inj.get(PlatformLocation), inj.get(APP_BASE_HREF) ),
      deps: [ Injector ]
    },
  ]
})
export class AppModule {}


Simplify configuration - get rid of "releasing.build.branch" (#101) (#106)

solves #101
sadly, no unit test because GitStatus is hardly unit testable.
We could add tests for testing the extension.
Should we also bump the version?

@szczepiq thx!
ad pushing directly to my branch: sure, that's ok.


trpc-chrome

// TODO: Implement trpc-chrome

Should be pretty simple, but give me a ping if you need any help setting up trpc-chrome!
💙

@jlalmes there are a couple of things that I'd need to wrap my head around and that's essentially the reason why haven't gotten to it so far.
E.g. how woule trpc-chrome's procedure listen to messaging from external web pages (e.g. apps/nextjs)?
// next/pages/some-page.tsx
  chrome.runtime.sendMessage(
      clientEnv.NEXT_PUBLIC_EXTENSION_ID,
      { data },
      (res) => {
        setIsLoadingExtension(false);
        if (res.success) {
          setIsSuccess(true);
          setTimeout(() => {
            close();
          }, 2000);
        } else {
          setIsError(true);
        }
      },
    );

Could I create the chromeLink also from the nexjs app? Not sure how the trpcClient can be initiated from there (that's our primary use case rn). Here's the chrome api reference.
Btw, we're currently catching all of those messages in our background  script with
chrome.runtime.onMessageExternal.addListener(
  async (request, sender, sendResponse) => {
    console.log("INCOMING MESSAGE...", { sender }, { request });
    if (!sender.url) return;
    // ... "procedures"...

trpc-chrome uses the connect protocol instead of message for message passing. (https://developer.chrome.com/docs/extensions/mv3/messaging/#connect)
Just open a port and add it in your chomeLink e.g.
// next/pages/some-page.tsx
const port = chrome.runtime.connect(process.env.PLASMO_PUBLIC_EXTENSION_ID);
const client = createTRPCClient<AppRouter>({
  links: [chromeLink({ port })],
});


Call for maintainers

Hey all
As some of you might know, I published this code because of this thread on our.umbraco.com which was started after an open space discussion at Codegarden (which I unfortunately didn't attend) and I wanted to share what I had been playing around with for some time so we didn't had to start from scratch implementing GraphQL for Umbraco.
I've tried to run the project but I really don't have the motivation to do so and as I never used the project myself in a real project (I only did it as a learning experience), I really don't think I'm the right person to continue this project, so if anyone want to take over and make it a success, please let me know.
In the coming weeks I'll transfer the project to the Umbraco Community GitHub account or the GraphQL for Umbraco organization (depending of the responses I get).

Hi @rasmusjp!
We've discussed it today with the Devteam at Cogworks and we'd like to help.
We're going to build some of the functionalities using GraphQL and Umbraco in the upcoming months, so we can use this as a base and/or extend it with our experience for that community usage - as it was meant to be from the beginning.
Let me know if it's still open and you haven't made any decision / agreement / assignment yet and we're happy to try to maintain it and dedicate enough amount of time to keep it alive and evolving!
Cheers and #h5yr for this amazing work! 🙌

Hi Rasmus,
We have been using it lately on some ProWorks projects and would also love to help.  I know @benjaminc has made a few Pull Requests to get Examine and Forms working with project and we will likely have more as we continue to use it.
Let us know how we can help and if you would like to setup a meeting sometime.
Thanks and #h5yr for the package!
-Jason

Hi @mzajkowski and @protherj
Awesome to see some interests in helping out with this package :)
I think it would be great if we could have meeting to talk about how we can move forward, if you can send me an email with some time suggestions I'll get a meeting setup.

Had a great chat with @mzajkowski, @protherj and @benjaminc about the future of this project.
Here's a summary of what we talked about:

The repository will be moved to the Umbraco Community Org, I will still be the owner
@mzajkowski, @protherj, @benjaminc and othrer relevant peaple will get commit rights to avoid me being the bottleneck in merging things
We're closing all existing issues, this doesn't mean that the issues are not relevant but we want to start with a clean board
We created a #graphql channel on the Community Slack
We'll talk again in January about where we want the project to go

Thanks again y'all


Question: How can I match multiple import functions with ELF module?

Yara version: 4.2.3
Elf file has structure like this:
elf
  symtab
    [54]
			name =<EMAIL_ADDRESS>			value = 0
			size = 0
			type = 2
			bind = 1
			shndx = 0
    [55]
			name =<EMAIL_ADDRESS>			value = 0
			size = 0
			type = 2
			bind = 1
			shndx = 0

From all resources I can find, I can search 1 import function
for any i in (0 .. elf.symtab_entries):
  (elf.symtab[i].name ==<EMAIL_ADDRESS>and elf.symtab[i].type == elf.STT_FUNC)

Problem comes when I want to check multiple values. The only solution I can think is
for any i in (0 .. elf.symtab_entries):
 (elf.symtab[i].name ==<EMAIL_ADDRESS>and elf.symtab[i].type == elf.STT_FUNC)
and for any i in (0 .. elf.symtab_entries):
 (elf.symtab[i].name ==<EMAIL_ADDRESS>and elf.symtab[i].type == elf.STT_FUNC)

It seems works, but it doesn't very good because I have to call multiple for loops.
There's an other way could be a solution but I don't really like it (obfuscated section names)
strings:
  $ = "htons" fullword
  $ = "dup2" fullword
for any i in (0 .. elf.number_of_sections):
  (elf.sections[i].name == ".strtab" and all of them)

So is there any better method to check multiple imported functions in ELF file?

There's an other case that it seems too complicated with only for loop check: If i want to check if either execv or execve imported in ELF file and htons was imported
(
  for any i in (0 .. elf.symtab_entries):
   (elf.symtab[i].name == "execv" and elf.symtab[i].type == elf.STT_FUNC)
  or for any i in (0 .. elf.symtab_entries):
   (elf.symtab[i].name == "execve" and elf.symtab[i].type == elf.STT_FUNC)
) and
for any i in (0 .. elf.symtab_entries):
   (elf.symtab[i].name == "htons" and elf.symtab[i].type == elf.STT_FUNC)

Well this could also work...
for 2 i in (0 .. elf.symtab_entries): (
   elf.symtab[i].type == elf.STT_FUNC and
   (
       elf.symtab[i].name ==<EMAIL_ADDRESS>or
       elf.symtab[i].name ==<EMAIL_ADDRESS>   )
)

Notice that in this case it's for 2 i in ..., which means that at least two of the entries must match the condition inside the for. But of course this assumes that you can't have two entries in  elf.symtab with the same name. If that's the case the rule above would work, if not, the only solution is the one you found.

Notice that in this case it's for 2 i in ..., which means that at least two of the entries must match the condition inside the for

Thanks a lot for that. I think i missed it in documentation. But if the condition is more complicated, I think the only solution is multiple for loops (which could be much slower?). Let say that I want to match

any of ("execv", "execve")
any of ("dup", "dup2")
any of ("htons", "htonl")
The condition can look like this

for 3 i in (0 .. elf.symtab_entries):
elf.symtab[i].type == elf.STT_FUNC and
   (
      ( elf.symtab[i].name == "htons" or elf.symtab[i].name == "htonl") or
       (elf.symtab[i].name == "exec" or elf.symtab[i].name == "execve") or
     // continue for dup, dup2 check
   )

It looks like the condition is similar to 3 of them instead of any of ($hton) and any of ($exec) and any of ($dup)
Btw, i think dynsym is undocumented in ELF module?

I think my last syntax can solve this problem (it's ugly because it requires too many for loops, but it's the only thing can do for now) so i'm closing this issue.
I hope Yara provides sort of syntax to do comparison like this in the future


Feat: Create food-adding drawer (UI)

Overview

This PR creates the food-adding button [ + ] and drawer and applies the design.
Changes

Adjusted the mobile layout paddings.
Indexed all the feature-specific components
Added the ring style to the SelectTrigger button when the select popover is open

Review points

When you review, please focus on the UI and components structure.
May refactor when creating a food-editing drawer to share similar components.

Screen Captures

Added the [ + ] button and the drawer.
https://github.com/genesis-tech-tribe/nishiki-frontend/assets/99148565/5d2a5bcf-d311-4a0a-9138-61fd96c07132
Note

Assignee Checklist:

[x] The base branch is correct (See: Types of Branches)
[x] The branch name follows the Branch Naming Conventions
[x] The correct assignees and reviewers have been designated for this PR
[x] The coding style follows the Coding Style Guide
[x] All the related issues are associated with this PR
[x] All criteria in the associated issues are met (please tick the checkboxes)
[x] My changes do not generate new warnings or errors (especially in the console)

Reviewer Checklist:

[ ] The code follows the generic best practices and our Coding Style Guide
[ ] Code is well-commented and easy to understand
[ ] UI changes accurately reflect the provided design

@kotaaaa
Thank you for your review and approval!
@kanta1207

You named directory name AddEditForm, so this os gonna be the directory to contain EditButton and EditDrawerBody, EditDrawerContent? If my understanding is correct. I like the approach, but at the same time, I feel like separating AddForm and EditForm directory could be also an option. In that case, we're gonna also create new directory to put all the add/edit form related components?

I understand your point. I will rearrange the directory structure that you pointed out in the next PR of implementing the food-editing modal because I have already commenced it.


Allow duplication of a channel in different groups.

Is your feature request related to a problem? Please describe.
I have created several groups to organize all my channels.
For different reasons, I would like to have the same channel in different groups. (ex: Disney Cinema in "Cinema" but also in "Kids" group. This is not possible so far. Only one group is authorized.
Describe the solution you'd like
Maybe we can have a way to duplicate a channel in several groups ?
Ex: Having a channel calle "Disney Cinema" in channel 40 in group "CINEMA", but also a channel "Disney Cinema" on channel 140 in group "KIDS". Of course, both these two channels refering to the same flow.
This could be feasible for example by clicking a "duplicate" button in mapping, on a given channel.  This would then duplicate all the characteristics, but with another channel number.

I guess you don't use Plex or Emby. Duplicate channels behave very strange in Plex, especially when recording. xTeVe is not an M3U editor. The M3U export function was only created to debug xTeVe with VLC. If you need an M3U editor, there are other alternatives, e.g. M3U4U

Right, I am using Kodi with M3U lists.
I must admit that I am not a big fan of putting my playlists into a web server. No one knows what they do with it. And I don't want my username/password to be given to someone else.
That's why xTeVe was really helpful for me. It ticks all the boxes of a playlist manager I was looking for.  It runs on Linux locally, has a web interface, a filters playlist, generates M3U, is compatible with multiple EPG... So very nice.
Then, if you don't want to consider the channel duplication feature, never mind. I think I can accommodate with it. But please, please, keep the M3U generation in place !

Don't worry, the M3U export function will remain.


ARM64 support?

Can this run on Arm64 Ubuntu?
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows 11 22H2]
Graphics hardware: [e.g. NVIDIA GeForce RTX 2060 Super, AMD Ryzen R4000 Integrated Graphics]
Graphics driver: [e.g., 531.18]
Memory usage: [e.g., 32 GB, 44% used]
Network speed and latency: [see speedtest.net]
Version: [e.g. 0.1.0]

Debug Log (if applicable):
[Paste debug log here]

Additional context
Add any other context about the problem here.

Only amd64 Ubuntu for now. This is a duplicate of #128.


2020 choice of fireproof safe

Ref. nytimes https://www.nytimes.com/wirecutter/reviews/best-fireproof-document-safe/
Req: TBD

Tired a bit so went with SentrySafe SFW123GDC, the 1st pick in the review 2021 safe.


default path to save video - current dir

> cd /tmp
> pyutube --help
...
│      path      [PATH]  Path to save video [default: /tmp]
...
> cd /
> pyutube --help
...
│      path      [PATH]  Path to save video [default: /]
...

Different and confusing output.
A user might mistake the dir they are current in for a dir downloads always go to.
It should not print the value of current dir, but say "current directory" or maybe ..
│      path      [PATH]  Path to save video [default: <current directory>]

│      path      [PATH]  Path to save video [default: .]

Hello again,
Thank you for bringing this to our attention. This change will provide a consistent and clear indication of the default path, regardless of the user's current location in the filesystem.
Your feedback is valuable to us, and we appreciate you taking the time to bring this to our notice. If you have any other suggestions or concerns, please don't hesitate to let us know.
Have a great day 😊

default twice - confusing:
│      path      [PATH]  Path to save video [default: <current directory>] [default: /tmp]

│      path      [PATH]  Path to save video [default: <current directory>] [default: /]

Ah, I understand now. The presence of [default: /tmp] or [default: /] is likely a feature of the Typer library, which I use in the pyutube CLI. It seems to be part of the library's functionality. I'll temporarily remove the [default: <current directory>] indicator and investigate if there's a way to adjust or modify the defaults for [default: /tmp] or [default: /].
Thank you.

Hey there,
I just wanted to express my gratitude for your understanding and patience. I've taken the time to address the issue that was causing some confusion about the default path display in the pyutube CLI.
Enhanced Output Representation:
url       TEXT    YouTube URL [required]
path      [PATH]  Path to save video [default: current directory>]

I truly appreciate your feedback, Cheers!


run in docker image node:14.14.0-buster-slim error

all the package is installed.
command 'npm run build '
Server: Compiled successfully
but log a error:
error building locale=en
Error: /app/node_modules/nodejieba/build/Release/nodejieba.node: invalid ELF header
at Object.Module._extensions..node (internal/modules/cjs/loader.js:1122:18)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object. (/app/node_modules/nodejieba/index.js:4:17)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object. (/app/node_modules/@easyops-cn/docusaurus-search-local/dist/server/server/utils/tokenizer.js:6:45)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: docusaurus build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build 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/2021-01-18T08_00_32_870Z-debug.log

For invalid ELF header, according to https://stackoverflow.com/a/29994851/14148700:

This happens when you build on one architecture and then attempt to use the same built addon on a different architecture (or platform in some cases).

This is probably a problem of nodejieba when using it on the docker image you used. I suggest you report a bug or a question to nodejieba instead.

For invalid ELF header, according to https://stackoverflow.com/a/29994851/14148700:

This happens when you build on one architecture and then attempt to use the same built addon on a different architecture (or platform in some cases).

This is probably a problem of nodejieba when using it on the docker image you used. I suggest you report a bug or a question to nodejieba instead.

And can you provide more information such as host system and arch (x86 or x86_64 or arm, etc,.)?
I just tried this image on my Mac x86_64, it works fine.

And can you provide more information such as host system and arch (x86 or x86_64 or arm, etc,.)?
I just tried this image on my Mac x86_64, it works fine.


stateless pods count Inconsistency between hkube jobs display and  stateless pods reported at grafana

HKube micro-service
version 2.6.20, UI
Describe the bug
while grafana HKUBE streaming dashboard displays that 15 stateless pods were up at the same time, in jobs UI stateless displays only 5 pod names
Expected behavior
jobs UI stateless should display all pods during the job
To Reproduce
Steps to reproduce the behavior:
streaming pipeline
stateful and stateless blocks (including min stateless pods definition)
start a pipeline, stream data in the way that 15 stateless will be created, monitor via jobs dashboard

Pods that were scaled (Not the minimum stateless pods)  were removed once completed. Fixed for 2.7 Release.


Release/3.0.5

[3.0.5] 2023-05-10
Fixed

Download API will not override a response status that is different than New. 2052
Language Toggle
Button styling across the product
Error message when a user tries to login and the service is unavailable
Unsupported browser page / Java Script not enable page

LGTM also :)
Did some basic browser testing - some future thoughts:

I would occasionally see a console error but it was hard to reproduce so it's probably related to my local setup "assertion failed: input argument is not an HTMLInput Element". If anyone else sees this in staging, might be worth looking into
meta charset is not first item in head, it probably should be
I saw a warning about using x-frames-options in the response headers and using CSP instead. I would think x-frames-options is more supported by browsers. I double checked with OWASP (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html) and I suspect a pen tester would have said something but noting encase anyone comes across this

In terms of x-frames-options we actually do allow our forms to be added as Iframes on external sites.

@thiessenp-cds in terms of x-frames-options we actually do allow our forms to be added as Iframes on external sites. This was to meet a specific use case early on in the GCForms project however may need to remove in the future.

Oh I had no idea, good to know, thanks! :)


FIX: GGshield should not install its tests

Related issue
https://github.com/GitGuardian/ggshield/issues/383
About this MR
This MR introduces two small changes:

Now; ggshield does not install its tests folders and subfolders
We have a new CI step that ensures such behavior (installing non-desired chunks of ggshield) does not occur again.

Codecov Report

Merging #452 (2eeb52a) into main (77a6401) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #452   +/-   ##
=======================================
  Coverage   93.54%   93.54%
=======================================
  Files          78       78
  Lines        3581     3581
=======================================
  Hits         3350     3350
  Misses        231      231

Flag
Coverage Δ

unittests
93.54% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Having issues with typescript 2.1.5

My project is based on typescript 2.1.5 and while importing postcss-middleware (tested even as a seperate ts file) I'm getting many errors from tsc regarding duplicate identifiers and interface Server ,ServerResponse, etc.
with errors as:

file: '.../node_modules/%40types/node/index.d.ts'
severity: 'Error'
message: 'Interface 'ServerResponse' cannot simultaneously extend types 'Writable' and 'EventEmitter'.
  Named property 'emit' of types 'Writable' and 'EventEmitter' are not identical.'
at: '640,22'
source: 'ts'

my tsconfig file is:
{
  "compilerOptions": {
    "target": "es2017",
    "module": "commonjs",
    "noImplicitAny": false,
    "removeComments": true,
    "preserveConstEnums": true,
    "noUnusedLocals": true,
    "outDir": "build",
    "sourceMap": true,
    "watch": false,
    "pretty": true
  },
  "compileOnSave": true,
  "include": [
    "src/**/*"
  ],
  "exclude": [
    "node_modules",
    "**/*.spec.ts",
    "build/**/*"
  ]
}

Yeah this code hasn't been updated to the newest version of TS. Are you requiring a ts file from this project directly? You shouldn't need to compile files in this project w/ your setup, I think.

Maybe I'm doing something wrong, but pretty straight forward from my ts file I'm writing the following:
import * as autoprefixer from 'autoprefixer';
import * as postcssMiddleware from 'postcss-middleware';

    this.app.use(postcssMiddleware({
      plugins: [
        // Plugins

        autoprefixer({
          browsers: [
            '>1%',
            'last 4 versions',
            'Firefox ESR',
            'not ie < 9', // React doesn't support IE8 anyway
          ],
        }),
      ],
      src: (req) => {
        return path.join(postcssDir, req.url);
      },
    }));

BTW, what makes you think the error you posted above has anything to do with this package? Perhaps you need to isolate the problem down to only the part that's failing. Try not using autoprefixer, for example. Eliminate anything else that might be a point of failure.

I did. I left only postcssMiddleware in the import.
Even more, I actually created a separate ts file just to test this - as at first I thought it had something to do with the other middlewares.

I can create a sample project to show the issue.

How did you install postcss-middleware and can you dive into your node_modules folder and tell me the extension name of the files that are installed? Are there ts files in there or js files?

Also, are you using webpack by chance?

no webpack.
it's a Typescript 2.x ExpressJS scaffolding I did on my own to cleanup stuff.
Then a friend asked me to add postcss to it (for his use) - and that's when I got this error.
I've installed postcss-middleware using yarn (yarn add postcss-middleware). nothing out of the ordinary.
The actual folder in node_modules list the files as:
CHANGELOG.md	LICENSE		README.md	dist		fixtures	gulpfile.ts	package.json	typings

and dist/lib/
middleware.d.ts	middleware.js

Thanks, that's very helpful. I think the d.ts file has to be recompiled with TypeScript latest to resolve this issue. Let me see how trivial that is.

@ShaharHD let me know if version 1.1.3 doesn't solve your issue.

No errors now 👍
Thank you!
I'll post here if after testing there are additional issues.


Fixes the Hermes' dock icon resolution

Fixes the Hermes' dock icon when disabling the "Hide Dock icon and menus" preference. If this preference is disabled the Hermes' dock icon becomes blurry. Diving deeper, it seems that the size of the dock icon was keeping the status bar icon '18' pixel size. This fix sets both the album art and Hermes' icon to both be 1024x1024, the Apple recommended dock icon size. The status bar icon is still set to the '18' size.

I can't reproduce this — can you give me some specific instructions to reproduce?  Thanks!

Here are the steps to reproduce:
Hermes Versions tested: 1.3.0 & 1.3.1
MacBook Air (13-inch, Early 2015)
macOS Sierra 10.12.3
Steps to reproduce:

Preferences…
General
Uncheck ‘Hide Dock icon and menus’
Uncheck ‘Use album art with play/pause as Dock icon’
The Hermes’ Dock icon is now blurry (attaching screenshots)

With the steps above:

With the 'Hide Dock icon and menus' checked:

Thanks, I am now seeing a pixelated icon; it was less noticeable because I was testing on a Retina display but I can definitely see it in the app switcher if not in the Dock.
It turns out #304/#299 also fixes this and is a bit shorter so I'm closing this pull request.  If for whatever reason the bug is still there for you, feel free to post a new patch.


⚠ Bofrost.at has degraded performance

In 58fa696, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1269 ms

Resolved: Bofrost.at performance has improved in 404fe48 after 6 minutes.


Correct path of the config.serve.concurrent configuration

The config prefix of the path serve.concurrent used on the serve task is missing.
Without it, there is no way of overriding the tasks that run concurrently when serving the site with grunt.
This commit correct the path to config.serve.concurrent, so it will be able to override it.

There's no test coverage on this either way, and it seems a very unused feature, so going with a merge.


Function DownloadFile crashes on the second file of an iteration

When using the function DownloadFile in a loop with multiple PortableDeviceFile:

It works fine on the first file
It throws an exception on the second file

The exception:
An unhandled exception of type 'System.Runtime.InteropServices.COMException' occurred in PortableDevices.dll

Additional information: The requested resource is in use. (Exception from HRESULT: 0x800700AA)

I thought that maybe sourceStream needed to be closed, but that does not seem feasible with the current. Here is the line of the exception, marked with // !!! EXCEPTION:
    public void DownloadFile(PortableDeviceFile file, string saveToPath)
    {
        IPortableDeviceContent content;
        this._device.Content(out content);

        IPortableDeviceResources resources;
        content.Transfer(out resources);

        PortableDeviceApiLib.IStream wpdStream;
        uint optimalTransferSize = 0;

        var property = new _tagpropertykey();
        property.fmtid = new Guid(0xE81E79BE, 0x34F0, 0x41BF, 0xB5, 0x3F, 0xF1, 0xA0, 0x6A, 0xE8, 0x78, 0x42);
        property.pid = 0;

        // !!! EXCEPTION (on the second file)
        resources.GetStream(file.Id, ref property, 0, ref optimalTransferSize, out wpdStream);

        var sourceStream = (System.Runtime.InteropServices.ComTypes.IStream)wpdStream;

        var filename = Path.GetFileName(file.Name);
        FileStream targetStream = new FileStream(Path.Combine(saveToPath, filename), FileMode.Create, FileAccess.Write);

        unsafe
        {
            var buffer = new byte[1024];
            int bytesRead;
            do
            {
                sourceStream.Read(buffer, 1024, new IntPtr(&bytesRead));
                targetStream.Write(buffer, 0, 1024);
            } while (bytesRead > 0);
            targetStream.Close();
        }
    }

I have figured out a way to make it work:
Connecting and disconnecting for every DownloadFile, like so:
_device.Connect();
_device.DownloadFile(file, destinationWindowsFolderPath);
_device.Disconnect();

Hi Xavier!
Sorry for the late reply. I'm glad to hear you have figured it out :)
Lasha
On Sun, Oct 2, 2016 at 9:10 PM, Xavier Peña<EMAIL_ADDRESS>wrote:

I have figured out a way to make it work:
Connecting and disconnecting for every DownloadFile, like so:
_device.Connect();
_device.DownloadFile(file, destinationWindowsFolderPath);
_device.Disconnect();
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Duke-fleed/WPDApi/issues/1#issuecomment-250985665,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGb-qHXX1s3NMS_5DhRqRld_jqUTGoz4ks5qv_OJgaJpZM4KMEiB
.


Add dist/ to the repository for Bower usage

Installation using "bower install --save google/wicked-good-xpath" still ignores the dist directory,
even after the following commit to close issue #44

I guess that this change would be unnecessary after the next release.


Emoji support

Codecov Report

Merging #3 (72969d9) into master (9f0a84c) will decrease coverage by 1.68%.
The diff coverage is 83.09%.

@@            Coverage Diff             @@
##           master       #3      +/-   ##
==========================================
- Coverage   95.34%   93.66%   -1.69%
==========================================
  Files           8        8
  Lines         516      568      +52
==========================================
+ Hits          492      532      +40
- Misses         24       36      +12

Impacted Files
Coverage Δ

lib/src/text.dart
100.00% <ø> (ø)

lib/src/text_layout.dart
89.89% <79.16%> (-10.11%)
:arrow_down:

lib/src/text_border.dart
92.85% <91.30%> (-7.15%)
:arrow_down:

emoji support + custom border improvements


ORC-167: Missing SchemaEvolution API breaks hive compatibility

Closing this as this issue is fixed in HIVE-15841


Make sample code for string substitution syntax

https://github.com/m-mujica/steal-conditional-interpolation-example


Errors in windowed and fullscreen

I have single display (laptop).
In fullscreen bot thinks that something is overlapping game window.
In windowed bot finds game window, but struggles to find "pallette headers".
Opus.log

Interesting - I'll probably have to add some more logging to help figure out what's going on.

Fixed errors by disabling FPS counter in Steam settings, got new ones.
Opus - Copy.log

I've added some extra logging when it searches for overlapping windows. (It tries to check there are no overlapping windows before starting, because otherwise the keyboard/mouse input might go to a different application on your computer and do bad things!)
For your new errors, it looks like it's still having problems analyzing the sidebar. If you edit Opus/App.Config and set ScreenCapture.LoggingEnabled to true, then try running it again, it will save screenshots as it analyzes the screen. You could then attach them to this issue (with a new log file). That should hopefully let us see why it's having problems!

Here

Opus.log

Turns out cropping problems were caused by interface scaling in Windows. It was at 125%, I totally forgot that I'm using it.
This time bot placed some elements, but something else went wrong again.
A lot of screenshots, using Dropbox.
https://www.dropbox.com/s/cqxwb6aimgjwgym/screenshots__2.zip?dl=0
Opus.log

Nice catch! I think I can probably make it more tolerant of interface scaling in the future...
In the meantime it looks like it's sometimes failing to right-drag with the mouse. This could be because it's doing it too quickly. I could probably try to make this a lot more robust, but for now I've added another setting that might help. Can you please:

Pull from master (or download the latest version)
Edit App.config and set MouseUtils.GlobalDragDelay to 50, and ScreenCapture.LoggingEnabled to true again.
Build and run.

If that doesn't help, try increasing the delay to 200. If that works, then we'll know the problem was a timing issue!

Works perfectly at 30! Thanks a lot! Watching how bot solves levels is completely mesmerizing!

Glad to hear it's working now! :)
I've just added a change which I think will make it work properly with interface scaling in Windows.
If the timing issue is a problem for a lot of people I could the drag delay setting it to the UI or (ideally) make the solver try to calibrate automatically. But for now I'll take the easy approach of just documenting it in the readme :)


included citation file for github

I've created a citation file that can be used in github to automatically populate a reference option on the left side bar of the main repo page.
I used information from github resource, information from issues #230, and used this tool

Thanks for your contribution @mkutu !


How to run musikcube in terminal (Windows).

How can I launch musikcube.exe in a terminal in Windows? It's not about musikcube-cmd.exe, since it is devoid of custom theme selection settings and in addition, it loads the processor very much in terminals other than the standard one (cmd.exe). If you just run musikcube.exe, then the application opens in a separate window... But who nowadays uses standart host? ConEmu, alacritty, and Windows Terminal have long been in use.

I run musikcube-cmd.exe in an MSYS2 shell in Windows Terminal—it works perfectly and uses the shell's theme.

I run musikcube-cmd.exe in an MSYS2 shell in Windows Terminal

I don't quite understand why I need MSYS2, when on one laptop Linux, and on the other Windows. The problem is that in Windows Terminal it is impossible to start musikcube.exe, and only musikcube-cmd.exe. But musikcube-cmd.exe in wt, heavily loads the cpu and in addition, there is no custom style selection setting. Therefore, we have to adjust the design of the terminal to the design of the player, which in my opinion is like pulling pants over head.

I don't quite understand why I need MSYS2
You don't, I was just sharing how I happen to use it.

But musikcube-cmd.exe in wt, heavily loads the cpu
That isn't the case on my machine, but I use a remote library running on my home server. Maybe it is taking that amount of CPU because it's indexing your library? See below:

Therefore, we have to adjust the design of the terminal to the design of the player, which in my opinion is like pulling pants over head.
Yeah, it might seem crazy to setup a shell config just for musikcube, but how often are you going to be opening and closing musikcube within another shell? For me, it's easier to have the settings for it in one place.

As far as I know, standard Windows cmd.exe/conhost stuff does not support extended palettes, and does not provide an ability to change defined colors on the fly. I may have to play around with this some more, but that was my experience a while back when I was playing with it. Because of this, themes are currently unsupported in this use case.
The more concerning issue is the high CPU usage using Windows Terminal. I'll try to find some time this weekend to see if I can reproduce that particular issue.

This should fix the high CPU usage bug: https://github.com/clangen/musikcube/commit/95420b83590a7a4c4f44b6e34270b4f4664228fa

This is still an issue, why was it closed?
I don't see any reason why musikcube should launch it's own term here
OS: Windows 10
Shell: pwsh 7.3.0-preview.8
Term: alacritty 0.10.1 (2844606)

@brian6932 run the included musikcube-cmd.exe instead of musikcube.exe in your command shell, it'll open in-place.

Ok so this must be an issue with the scoop package, as that wasn't shimmed, I'll fix it then


Throwing error

when write this script in common main implementation("io.github.pablichjenkov:component-toolkit:0.5.1")
:shared:iosX64Test: Could not resolve io.github.pablichjenkov:component-toolkit:0.5.1.
Required by:
project :shared
Possible solution:

The target x64 for iOS is not supported to gain speed in compilation times.  There aren't many iPhones with Intel chip out there if any, that's why I took that decision.
If you are planning to use/contribute to the library I can add the x64 target.
PR welcome 🙂 too

Issue should be fixed in version 0.5.4
implementation("io.github.pablichjenkov:component-toolkit:0.5.4")


fix: use base config when no remote is declared

What kind of change does this PR introduce?
Bug fix
What is the new behavior?
Overrides local project id when no remote is declared.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 6 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 59.627%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/config/push/push.go
0
6
0.0%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.02%

Covered Lines:
6386

Relevant Lines:
10710

💛  - Coveralls


adds an option to print the current context/namespace

I needed an option to see the current namespace, and just leveraged what was already present in the tools. Did the effort for context too, for uniformity.

See #28 and #14. 😊


:ambulance: Length validator would fail on non-string values.

Called toString() on value to ensure that we can use the default tokenizer.

thanks!


Running a single test type? ie --lib, --test, etc

I'm attempting to get coverage for what would normally be cargo test --lib. Most notably I'm doing this to avoid some integration tests, and not having success with the flag --exclude-files "*integration*".
Am I missing a way to just run lib tests?
(edit: I realized I am pre-assuming what the Tests runtype does, so I'm trying that now. To see if it excludes /tests)
(edit2: nope, seems the Tests runtype still executes /tests, as expected.)

There's not yet an analogue for --lib it is on my todo list as part of #247

I've currently got a feature branch for this and it seems to be working pretty good. I'll look at adding some tests and tidying it up as I'm also adding things like named tests at the same time i.e. --bench <NAME>

This is now in the develop branch, so you can try it out there otherwise it'll be around next release :+1:


Inconsistent use of 'colour'

wxWidgets consistently uses 'Colour'. wxGlade mixes 'Colour' and 'Color' inconsistently.

While this doesn't really matter for internal code (hint: use 'colr' ☺) at UX level it should be consistent.
(Note that I consitently typed 'consitent' and had to manually edit all occurrences.)

Well, wxWidgets is also not 100% consistent: there is a stock item wxID_SELECT_COLOR.
Unfortunately wxGlade uses widget property names like grid's line_color which can't be changed easily.
But you're right, it should be changed where possible.

I hope I did not introduce a bug...


Public sign up option

Does Postal have this option, for a public sign up page, where any one can register and create an organization/account?
The user would have access to his/her organization, but not have admin rights, just regular user rights.
At the moment I create this manually, but would love to know if there's an option already for this.

I don't believe this is a feature and presume atech handled registration in a separate system before releasing Postal as open source.

I'm afraid Postal does not support this. There is no simple solution other than creating the accounts manually, or you would need to build in your own signup flow.


Could not connect to Azure SQL Database on version <IP_ADDRESS>

I started facing this issue when I brew updated my system.
When I try to connect to sql server:
cnxn = pyodbc.connect('DRIVER='+driver+';SERVER=<IP_ADDRESS>,1433;DATABASE='+database+';UID='+username+';PWD='+ password)
I get the following error:
pyodbc.OperationalError: ('08001', '[08001] [Microsoft][ODBC Driver 17 for SQL Server]Client unable to establish connection (0) (SQLDriverConnect)')
When I run : isql -v -k "{ODBC Driver 17 for SQL Server};SERVER=<IP_ADDRESS>,1433;DATABASE=test;UID=sa;PWD=" I get
[IM002][unixODBC][Driver Manager]Data source name not found and no default driver specified
[ISQL]ERROR: Could not SQLDriverConnect
odbcinst -j
unixODBC 2.3.9
DRIVERS............: /usr/local/etc/odbcinst.ini
SYSTEM DATA SOURCES: /usr/local/etc/odbc.ini
FILE DATA SOURCES..: /usr/local/etc/ODBCDataSources
USER DATA SOURCES..: /Users/r0m086g/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8
Please help. Trying to resolve this issue for past two weeks but unable to

That definitely doesn't look like Azure. Is it a Linux  SQL Server? Your connection string with isql is incorrect, it is missing DSN or Driver specification. What are ALL the errors? "Client unable to establish connection" does not say anything useful for determining the cause.


Fix issue with PyObject drop and allow_threads

While writing tests for #908 I realised unfortunately there is a bad interaction between the optimization I wrote in #851 and allow_threads.
With the GIL_COUNT method for gil_is_acquired, it's not possible to know if we are inside an allow_threads call without the GIL. The way #851 is currently written, in this situation we end up decreasing a reference count without the GIL held, which could cause all kind of bad stuff.
I propose to fix this situation by introducing a linked-list of GIL states, which is updated by both GILPool and allow_threads.
This fix is still broken if someone wishes to use the PyEval_SaveThread APIs themselves manually. If you think we need to worry about the case of users using PyEval_SaveThread themselves, then I think the only sensible solution is to revert #851.
I think the implementation here can still be cleaned up a lot. I wanted to open this PR to discuss the problem before I bothered to make the solution particularly tidy.
(I have also checked benchmarks and it does not noticeably affect performance.)
Let me know if you think I should finish this fix, or revert #851.

I'm sorry I don't completely understand the problem yet, but how about just setting it to zero?
E.g.,
        unsafe {
            let save = ffi::PyEval_SaveThread();
            let count = GIL_COUNT.with(|c| c.get());
            GIL_COUNT.with(|c| c.set(0));
            let result = f();
            GIL_COUNT.with(|c| c.set(count));
            ffi::PyEval_RestoreThread(save);
            result
        }

Haha nice yes that will also solve the problem in a much simpler way! 😆

Cool @kngwyu the simpler solution is much nicer 👍 👍 👍

Thank you!


stackexchange.com/questions/2411/what-are-the-most-common-algorithms-for-adaptive-thresholding

https://dsp.stackexchange.com/questions/2411/what-are-the-most-common-algorithms-for-adaptive-thresholding

Added in 283c496


KAFKA-15942: Implement ConsumerInterceptor

When invoking ConsumerInterceptor#onCommit method in ConsumerCoordinator, there're some redundant if-nonNull branches.
private final ConsumerInterceptors<?, ?> interceptors is a non-null field because it'll be instantiate in the constructor, and this field is non-null when delivering from LegacyKafkaConsumer.
Some proofs:
There're 2 constructors in LegacyKafkaConsumer, both of them will instantiate interceptors field:

constructor1 in LegacyKafkaConsumer：this.interceptors = new ConsumerInterceptors<>(interceptorList);
constructor2 in LegacyKafkaConsumer:  this.interceptors = new ConsumerInterceptors<>(Collections.emptyList());

And this field can not set to null because it's private and no method to modify it.
Committer Checklist (excluded from commit message)

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

@vamossagar12 Thanks for reviewing the PR!
At the beginning I misunderstood this ticket, now I understood and the code has already updated.
When commit request returns successfully from the broker in AsyncKafkaConsumer on both sync and async methods, I added the ConsumerInterceptor#onCommit.
Would you have time to take a look at this PR?

hmm, the JDK21 build failed with this error =>
> Task :examples:spotbugsMain

Cannot contact jenkins-shared-ubuntu-3: java.lang.InterruptedException

> Task :core:compileScala

> Task :group-coordinator:classes

> Task :metadata:classes

> Task :examples:spotbugsTest SKIPPED

> Task :examples:check

> Task :group-coordinator:checkstyleMain

> Task :clients:testClasses

> Task :clients:checkstyleTest

> Task :clients:spotbugsMain

The message received from the daemon indicates that the daemon has disappeared.

Build request sent: Build{id=f24da9a8-313c-42d5-bc18-9f578f44c4a3, currentDir=/home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-14963}

Attempting to read last messages from the daemon log...

Daemon pid: 2004981

  log file: /home/jenkins/.gradle/daemon/8.5/daemon-2004981.out.log

----- Last  20 lines from daemon log file - daemon-2004981.out.log -----

2023-12-11T15:25:02.911+0000 [DEBUG] [org.gradle.launcher.daemon.server.SynchronizedDispatchConnection] thread 25: received class org.gradle.launcher.daemon.protocol.CloseInput

2023-12-11T15:25:02.911+0000 [DEBUG] [org.gradle.launcher.daemon.server.DefaultDaemonConnection] thread 25: Received IO message from client: org.gradle.launcher.daemon.protocol.CloseInput@41f596f2

2023-12-11T15:25:02.945+0000 [DEBUG] [org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon] Requesting daemon stop after processing Build{id=f24da9a8-313c-42d5-bc18-9f578f44c4a3, currentDir=/home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-14963}

2023-12-11T15:25:02.965+0000 [LIFECYCLE] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] Daemon will be stopped at the end of the build

2023-12-11T15:25:02.968+0000 [DEBUG] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] Stop as soon as idle requested. The daemon is busy: true

2023-12-11T15:25:02.969+0000 [DEBUG] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] daemon stop has been requested. Sleeping until state changes.

2023-12-11T15:25:02.970+0000 [DEBUG] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] The daemon has started executing the build.

2023-12-11T15:25:02.971+0000 [DEBUG] [org.gradle.launcher.daemon.server.exec.ExecuteBuild] Executing build with daemon context: DefaultDaemonContext[uid=c8e3ee8e-33ef-46b7-a5a1-3d91a0e54ca4,javaHome=/usr/local/asfpackages/java/adoptium-jdk-21.0.1+12,daemonRegistryDir=/home/jenkins/.gradle/daemon,pid=2004981,idleTimeout=120000,priority=NORMAL,applyInstrumentationAgent=true,daemonOpts=-Xss4m,-XX:+UseParallelGC,--add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-Xmx2g,-Dfile.encoding=UTF-8,-Duser.country,-Duser.language=en,-Duser.variant]

2023-12-11T15:25:02.972+0000 [INFO] [org.gradle.launcher.daemon.server.exec.ForwardClientInput] Closing daemon's stdin at end of input.

2023-12-11T15:25:02.973+0000 [INFO] [org.gradle.launcher.daemon.server.exec.ForwardClientInput] The daemon will no longer process any standard input.

Starting build with version 3.7.0-SNAPSHOT (commit id 22d2b462) using Gradle 8.5, Java 21 and Scala 2.13.12

Build properties: maxParallelForks=4, maxScalacThreads=4, maxTestRetries=0

@Joker-5 , I see another PR created for this here. You might want to check with Lucas about this

Hey @Joker-5, I took the ticket since your original PR seemed to only change the legacy consumer, so I thought it was just linked to the wrong ticket.
I think there are some things missing here

enable unit / integration tests
the way you implemented it, I think the interceptors will run as part of the background thread, but I think they should not interfere with the background thread and run as part of the application thread instead.

How about we merge my PR which has the two changes and I add you in a Co-authored-by tag? Sorry again for the confusion.

Hey @Joker-5, I took the ticket since your original PR seemed to only change the legacy consumer, so I thought it was just linked to the wrong ticket.
I think there are some things missing here

enable unit / integration tests
the way you implemented it, I think the interceptors will run as part of the background thread, but I think they should not interfere with the background thread and run as part of the application thread instead.

How about we merge my PR which has the two changes and I add you in a Co-authored-by tag? Sorry again for the confusion.

I understand, this is the second PR which i committed to Kafka. And I had learned a lot from your PR, so just do it.

@Joker-5 , thanks for the update. There are some missing pieces in this PR from what I can tell. Having said that, I see another PR created for this here. You might want to check with @lucasbru about this.

Thanks so much for the review!
I had checked with @lucasbru. We will merge @lucasbru's PR which has the two changes and @lucasbru will add me in a Co-authored-by tag.

@Joker-5 , makes sense and thanks for letting me know. We can close this PR then?

@Joker-5 , makes sense and thanks for letting me know. We can close this PR then?

Sure, I'll close this PR soon.

Hey, @lucasbru, I saw this PR is ready to merge, but I don't see the Co-authord-by tag in the commits log.
I'm a bit worried that you forgot or maybe there's some reason for it. I would be extremely grateful if you would tell me about it if you have time.
So sorry to trouble you.

@Joker-5 I can add it in the PR description so that I don't forget. But the tag needs to added to the final commit, once we merge it, so we cannot really add it yet

@Joker-5 I can add it in the PR description so that I don't forget. But the tag needs to added to the final commit, once we merge it, so we cannot really add it yet

Got it, many thanks.

Hey, @lucasbru, I saw this pr had been merged, but it seems there's no Co-authord-by tag in the final commit. So there may something wrong in it?
I would be extremely grateful if you would tell me about it if you have time.
Feel so sorry to trouble you again.

There is one here: https://github.com/apache/kafka/commit/1a54c25fdfff351fd1b35d60dbc95232c550f3a1

There is one here: 1a54c25

Got it, feel so sorry to trouble you again.
Have a nice day!


Suggested practices for running parallel tagged specs?

Hey Artur!
I've read the README section on running specs with tags but I'm not 100% sure this fully describes our use case. Let me tell you how we roll 😄
Before configuring Knapsack we were already using rspec tags to parallelize our build. We have 4 different tags:

ordered - for legacy test that need to run in a predefined order 💀
random - for good tests
hive - for tests that integrate with hive
jruby - for a subset of tests that also has to run on JRuby

What I did when configuring Knapsack was I generated a separate report file for each tagged subset of specs. So we have 4 different files: knapsack_ordered.json, knapsack_hive.json, etc. Based on them we further parallelize each tagged rake task.
Is this a good setup for Knapsack or would you suggest something else? One of my concerns is that such a setup creates a lot of leftover specs and I'm not sure how Knapsack deals with them in mix with tags.

@madejejej Could you tell me more how you run those tests?

Do you run each tag on each CI node?

Could you tell me how long is each tagged test suite?

How many CI nodes do you have?

What CI provider?

Do ordered tests depends only on its inside of test files, right?

Do ordered depend on the order in which test files are executed? For instance b_spec.rb must be executed after a_spec.rb.

I designed knapsack_pro gem for larger and more complex test suites. You can learn more watching video on https://knapsackpro.com and I can help you configure your project.
You could run your tests in this order to get optimal test suite split.
# run only tests with tag ordered
KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC=api_key_for_tag_ordered bundle exec rake "knapsack_pro:rspec[--tag ordered]"

# run only tests with tag hive
KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC=api_key_for_tag_hive bundle exec rake "knapsack_pro:rspec[--tag hive]"

# run only tests with tag jruby
KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC=api_key_for_tag_jruby bundle exec rake "knapsack_pro:rspec[--tag jruby]"

# run only tests with tag random using knapsack_pro Queue Mode
# that will auto balance your timing differences between CI nodes
# so your CI build will have optimal timing split.
KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC=api_key_for_tag_random bundle exec rake "knapsack_pro:queue:rspec[--tag random]"

You will need to generate 4 API tokens for each command after sign in.
Please read more about:

What is the optimal order of test commands? https://github.com/KnapsackPro/knapsack_pro-ruby#what-is-optimal-order-of-test-commands

If your test are in different directories than you can use KNAPSACK_PRO_TEST_FILE_PATTERN="{spec,engines/*/spec}/**/*_spec.rb" to control which tests should be executed instead of using tags.
https://github.com/KnapsackPro/knapsack_pro-ruby#how-can-i-run-tests-from-multiple-directories

Let me know if I can help or email me :)

Each tag is run on a separate node

Hive is ~24 minutes, ordered around 20 minutes, random around 15 minutes and JRuby ~7 minutes

we self-host Jenkins so it's all configurable and we're still looking for the optimal configuration :). Currently we use an auto-scaling group with a limit of 40 v-CPUs and 40 workers

/ 6. Unfortunately there are dependencies between files but we're pretty close to fixing these issues and running them all in random order

We'll definitely consider using the pro version but for now we want to see how well our build will work with the regular version.

If you will look for Jenkins configuration, here is an example from one of my users:
https://github.com/KnapsackPro/knapsack_pro-ruby#info-for-jenkins-users
You can still run order depended tests with regular knapsack for the time being and use knapsack_pro Queue Mode to auto balance CI nodes timing to get optimal time execution. No need to reinvent the wheel and you can focus on delivering features to your customers which should please stakeholders more :)

Pretty old issue, I guess no action here for now. I'm closing it. Feel free to reopen or add more information if you need help.


feat: settings bitcoin unit

This PR wires up bitcoin unit in the display settings flow.

@markmhendrickson need your feedback here on Monday bc the team talked abt reducing offered bitcoin units to just BTC and sats to start. We weren't sure why the others were being prioritized?

I tested this but when I try and reach Display - Settings it's crashing with:
 ERROR  TypeError: Cannot read property 'symbol' of undefined

This error is located at:
    in SettingsDisplayScreen

https://github.com/user-attachments/assets/40099822-56b3-4fcb-9137-1bc32a112d35
Maybe I'm missing a step where I need to regenerate lingui files?

need your feedback here on Monday bc the team talked abt reducing offered bitcoin units to just BTC and sats to start, we weren't sure why the others were being prioritized?

The idea here is that users may want a wider range of options, given just how much BTC they're dealing with in the app. bitcoin and sats are indeed the most common units these days; however, the other ones may help users with more mid-sized or smaller holdings.
My presumption is that the work involved would be relatively the same regardless (between two or five options) in that we need to support an array of options, and whichever is chosen, we'll apply that to a formatting function throughout the app? However, I'm happy to release with just two to start if there is indeed a significant work difference.
Reference: https://bitcoin.design/guide/designing-products/units-and-symbols/

I tested this but when I try and reach Display - Settings it's crashing with:
 ERROR  TypeError: Cannot read property 'symbol' of undefined

This was happening to me until I purged the persisted redux store. This is likely exposing a prob with our store setup, bc we shouldn't haven't to do that, right?

I tested this but when I try and reach Display - Settings it's crashing with:
 ERROR  TypeError: Cannot read property 'symbol' of undefined

This was happening to me until I purged the persisted redux store. This is likely exposing a prob with our store setup, bc we shouldn't haven't to do that, right?

OK let me check it out. Yes I don't think we should need to purge the store but maybe it's something we have to deal with


add quote for affinity values.

merge: https://github.com/istio/istio/pull/16689

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

Test name
Commit
Details
Rerun command

noauth_installer
55f1e5227465c29582f655596df4f8a84a0099aa
link
/test noauth_installer

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

/test noauth_installer