Feedback report from trying to use this with niche tools

I spent several hours today looking in to adopting xmake but the documentation to add custom targets appears to be the most minimum it could be. I am coming in from systems like Plan 9 Mk, PyDoIt and Ninja where it is easy to set up arbitrary rules for obscure tools.
Some of these will probably need to be split in to their own separate issues.

on_build examples looks like markdown but it just copies and renames a file, doesn't even show an example of os.exec and how one is intended to run say pandoc.
it took a bit to hunt down os.exec is what you call to actually get files built
pulling up the source code there are references to functions likes autogenfile which are never mentioned in the documentation
there is almost no docs for on_build_files but then a huge example for lex on buildcmd, which also brings in concepts like tracking the extra dependencies generated by the rule, but the on_build sections never told you how to do this at all
is on_build deprecated for on_buildcmd? it would appear to be since one is documented and the other is not, and the source code for things like protobuf, lex and capnproto use buildcmd
how does one deal with jobs where many files are specified as inputs but only one or two of those actually are part of the command line?

two examples of order only dependencies here:

in nim you compile similarly to pascal where you only specify the name of the application unit but you may still say its dependencies are required; so i say nim c foo but in mk or ninja i may say that this has order only dependencies to all of the other nim (or .pas) files.
in imatix GSL you have to specify some number of script files and model files to run; i managed to reverse engineer how to use an 'object' target and a custom rule to do this and generate an output, but xmake doesn't associate the inputs and outputs together and always rebuilds it. i also tried not using separate targets but this just merged all the .gsl and .xml files together via add_file and didn't do what it should.

for example i was able to dig out a way to get a target to actually run what it should:
# xmake.lua
rule('gsl')

on_build_files(function (target, sourcebatch, opt)
    local script = target:values('gsl.script')
    for _, sourcefile in ipairs(sourcebatch.sourcefiles) do
        if path.extension(sourcefile) == '.xml' then
            os.exec('gsl -script:%s %s', script, sourcefile)
        end
    end
    os.exec('touch potato.script')
end)

target('potato')
set_kind('object')
set_values('gsl.output', 'potato.script')
set_values('gsl.script', 'potato.gsl')
set_filename('potato.script')
add_files('potato.gsl', 'potato.xml', {rule='gsl'})

but since i used the objects kind i lose access to being able to set a filename which is also aggravating. so i have to use custom values to set that and xmake will always try to rebuild these.
i could fiddle around with writing some documentation but i have no idea how this is supposed to work (short of just copying the protobuf code and changing some strings)
for example in plan 9 mk the job is just
potato.script: potato.gsl potato.xml
    gsl -script:potato.gsl potato.xml > $target

in please.build there's just a simple seven lines to make a new rule for something like this
def word_count(name:str, file:str) -> str:
    return genrule(
        name = name,
        srcs = [file],
        outs = [f"{name}.wc"],
        cmd = "wc $SRC > $OUT",
    )

i'm not yet sure if xmake is just not suitable for jobs other than bog standard cmake like builds, or if it's :+1: but just needs someone to write docs.

some docs:
https://xmake.io/#/manual/custom_rule?id=ruleon_buildcmd_file
https://xmake.io/#/manual/custom_rule?id=ruleon_buildcmd_files
https://xmake.io/#/manual/project_target?id=targeton_build
https://xmake.io/#/manual/project_target?id=targeton_build_files

on_build examples looks like markdown but it just copies and renames a file, doesn't even show an example of os.exec and how one is intended to run say pandoc.

see https://xmake.io/#/manual/builtin_modules?id=osexecv

is on_build deprecated for on_buildcmd? it would appear to be since one is documented and the other is not, and the source code for things like protobuf, lex and capnproto use buildcmd

Both of these can be used and have not been discarded. But using on_buildcmd_file will be simpler, and it can handle dependency update issues more conveniently. If you use on_build_file, you can also use depend.on_changed to handle them, but it's a little more complicated.
https://github.com/xmake-io/xmake/blob/0b09f8fe41184b539e1bbf3aa0086794a77708a0/xmake/rules/utils/symbols/export_all/export_all.lua#L41
on_build_file is more flexible, but on_buildcmd_file is simpler. For novices, I recommend using on_buildcmd_file
related issue: https://github.com/xmake-io/xmake/issues/1246

for example i was able to dig out a way to get a target to actually run what it should:

rule('gsl')
    set_extensions(".xml")
    on_buildcmd_file(function (target, batchcmds, sourcefile, opt)
        local script = target:values('gsl.script')
        -- local outputfile = ? we need get output file path
        batchcmds:execv("gsl", {"-script:" .. script, sourcefile})

        batchcmds:add_depfiles(sourcefile)
        batchcmds:set_depmtime(os.mtime(outputfile))
        batchcmds:set_depcache(target:dependfile(outputfile))
    end
end)

or
rule('gsl')
    set_extensions(".xml")
    on_build_file(function (target, sourcefile, opt)
        import("core.project.depend")
        local script = target:values('gsl.script')
        -- local outputfile = ? we need get output file path
        depend.on_changed(function ()
             os.execv("gsl", {"-script:" .. script, sourcefile})
        end, {dependfile = target:dependfile(outputfile), files = sourcefile, lastmtime = os.mtime(outputfile)})    end
end)

more examples:
https://github.com/xmake-io/xmake/blob/master/xmake/rules/lex_yacc/lex/xmake.lua
https://github.com/PucklaMotzer09/VulkanKraft/blob/96a9dcfe9bc6d9ef3ba228c03488b7d040e9d3b4/xmake.lua#L6

I do agree that the documentation for rules is too simple. It lacks examples for many useful cases. For me I usually read the built-in rules under the folder https://github.com/xmake-io/xmake/tree/master/xmake/rules (but I can seldom find the exactly same case as what I need) and get help from github discussions. In my port of suitesparse https://github.com/xq114/SuiteSparse-xmake/blob/main/xmake.lua I felt that even with detailed help from @waruqi (much thanks!), writing rules is still not a easy thing to do, at least for now. I wish if there was a more detailed documentation about the target object, the option object, and more examples of rules explained in detail about the usage, design procedure and key points.

The examples in the document really cannot meet the needs of all users. I suggest you can directly read https://github.com/xmake-io/xmake/tree/master/xmake/rules or https://github.com/xmake -io/xmake/tree/master/tests/projects
Of course, if I have time, I will consider adding more examples to the document.
It takes a lot of time and work to complete the documentation, and my current fragmentation time can only barely satisfy the resolution of issues and the development of some new features.
I will update part of the documentation before each release, and I will also consider adding documentation for the option and target instance interface later.

About rules, I have used batchcmd to simplify them before. I think it should not be too complicated to implement a rule by referring to the existing rules with batchcmd.
Of course, I haven't used batchcmd to simplify some of the built-in rules of xmake, so it seems to be more complicated, and I will continue to update them later.


fixes #247

I think is @voorjaar prefer use that color, same as other colors like gray and green.

I think is @voorjaar preferred use that color, same as other colors like gray and green.

I didn't know there was a different palette, it kind of makes it harder to switch from tailwind to windi
Also since there is a violet color, why have two different color names with the same color?

Looks like tailwind is using the same color as we used.
https://github.com/tailwindlabs/tailwindcss/blob/master/stubs/defaultConfig.stub.js#L27

Not sure where that specific config is being used, but I've just moved my project from tailwind to windi and noticed that the colors don't match. When I use purple-100 in tailwind it corresponds to the color listed in their docs which is #F3E8FF. In windi purple-100 is #EDE9FE.


Where to find libBCrypt.so?

Where can a find libBCrypt.so? can i install it using the package manager (apt)?

I think it's not that easy, unfortunately. As stated in the list, I also came across a Windows game that needs bcrypt.dll and now the unity player looks for a bcrypt.so or libcrypt.so on Linux, but I'm not aware of an existing equivalent in use on Linux.
I searched for files with that name in all packages with the following:
$ apt-file search libbcrypt
libwine-dev: /usr/lib/x86_64-linux-gnu/wine/x86_64-unix/libbcrypt.a
libwine-dev: /usr/lib/x86_64-linux-gnu/wine/x86_64-windows/libbcrypt.a
mingw-w64-i686-dev: /usr/i686-w64-mingw32/lib/libbcrypt.a
mingw-w64-x86-64-dev: /usr/x86_64-w64-mingw32/lib/libbcrypt.a

The name appears in relation with wine and mingw, so I would guess it's more a Windows-specific library, but it could be possible to make of whats there.
Another possible option could be to determine why and which functions need the game to run. Most of the games I tested don't need that library, so I would assume it is not essential for a game to run and is only used for some checks or something when launching the game. In that cases, building a small stub library can sometimes help to pass the error.


There is no handler class defined for handler "%env(LOG_TYPE)%"

Might be overlooking something here, but seems MonologExtension is using type before Symfony has gotten around to evaluate env variables.
ref:
 [Symfony\Component\DependencyInjection\Exception\EnvParameterException]
  Incompatible use of dynamic environment variables "LOG_TYPE" found in parameters.

Exception trace:
 () at vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/Compiler.php:137
 Symfony\Component\DependencyInjection\Compiler\Compiler->compile() at vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/ContainerBuilder.php:565
 Symfony\Component\DependencyInjection\ContainerBuilder->compile() at vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php:484
 Symfony\Component\HttpKernel\Kernel->initializeContainer() at vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php:116
 Symfony\Component\HttpKernel\Kernel->boot() at vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php:68
 Symfony\Bundle\FrameworkBundle\Console\Application->doRun() at vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:120
 Symfony\Component\Console\Application->run() at bin/console:25

  [InvalidArgumentException]
  There is no handler class defined for handler "%env(LOG_TYPE)%".

Exception trace:
 () at vendor/symfony/monolog-bundle/DependencyInjection/MonologExtension.php:766
 Symfony\Bundle\MonologBundle\DependencyInjection\MonologExtension->getHandlerClassByType() at vendor/symfony/monolog-bundle/DependencyInjection/MonologExtension.php:140
 Symfony\Bundle\MonologBundle\DependencyInjection\MonologExtension->buildHandler() at vendor/symfony/monolog-bundle/DependencyInjection/MonologExtension.php:68
 Symfony\Bundle\MonologBundle\DependencyInjection\MonologExtension->load() at vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/MergeExtensionConfigurationPass.php:55
 Symfony\Component\DependencyInjection\Compiler\MergeExtensionConfigurationPass->process() at vendor/symfony/symfony/src/Symfony/Component/HttpKernel/DependencyInjection/MergeExtensionConfigurationPass.php:39
 Symfony\Component\HttpKernel\DependencyInjection\MergeExtensionConfigurationPass->process() at vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/Compiler.php:120
 Symfony\Component\DependencyInjection\Compiler\Compiler->compile() at vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/ContainerBuilder.php:565
 Symfony\Component\DependencyInjection\ContainerBuilder->compile() at vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php:484
 Symfony\Component\HttpKernel\Kernel->initializeContainer() at vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php:116
 Symfony\Component\HttpKernel\Kernel->boot() at vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php:68
 Symfony\Bundle\FrameworkBundle\Console\Application->doRun() at vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:120
 Symfony\Component\Console\Application->run() at bin/console:25

Relevant symfony issue: https://github.com/symfony/symfony/issues/21609

env variables cannot be used to configure aliases or service classes, because this would require reading them during the container compilation.
Supporting switching the handler type at runtime with an env variable would require moving all the logic configuring handlers to a factory method to do all the work at runtime rather than at build time. This would add overhead to all instantiations of the logger (as it would have to validate and resolve the config at that point), and would force to remove some features (handlers expecting other nested handlers would not be manageable at runtime, unless we move all the processing of the bundle config at runtime, which is a total no-go if you care about performance just a little)

I agree, we can close this and continue discussion on best practice for parameter injecting in symfony issue.


Fixed setting of NODE_ENV in package.json to be Windows compatible

What the title says. "SET ENV_VARIABLE" works on both windows & in linux/unix shells.

Current coverage is 83.98% (diff: 100%)

Merging #5 into master will not change coverage

@@             master         #5   diff @@
==========================================
  Files             5          5
  Lines           206        206
  Methods          37         37
  Messages          0          0
  Branches         42         42
==========================================
  Hits            173        173
  Misses           33         33
  Partials          0          0

Powered by Codecov. Last update 87555df...de5f753

Thanks for submitting this PR! Have you used the cross-env npm package before? I think I would prefer to use it instead but would happily merge a PR from you if you used it! The redux package itself uses it https://github.com/reactjs/redux/blob/master/package.json
Thanks again!

Hi,
No I have not. If you merge this PR, I can look into it and submit another request.

Ok, I'd like to publish a version to npm today with the cross-env implementation. So I'll merge this PR shortly along with a few other PRs, then merge a cross-env PR, then publish to npm. This way you'll still get contribution credit because I appreciate you making a PR, but no published npm version will have the code in this PR. Sound good?

Thanks.


Automatically closing expired positions is too inconspicuous

A user checking their position does not notice that their position is expired and therefore might close the app while the collaborative closure is happening.
Closing the app during this phase is still critical and may result into failures e.g. force closures (see also #874).
Automatically closing an expired position should be more visible to the user.

related to https://github.com/get10101/10101/issues/988

Closed in favor of https://github.com/get10101/10101/issues/1071


New Article : Various Activation Functions in Neural Networks

Blog is not being added due to absence of review.


{filters} Do not show filter options with 0 records for filters with variable use input

Story
Do not show filter options with 0 records for filters with variable input.
This is not a dynamic filter. We do not expect filters to disappear when an other filter is turned on and the results become 0.
Example: When you have a filter that has been used once (5 years ago for instance, or per accident), but it contains 0 records today it should not be shown, as it will never show results.
When there are 0 filters activated, we still see these filter options, while none of the visible/searchable records carry that metadata.

Success criteria

[ ] When, looking at the entire record base, there are no records in use for a variable, we do not retain it.

[ ] Year
[ ] Librarian tags
[ ] WoS type

Notes on informing better
[later] The level up from this for "year" could be:

a slider input that informs people in a better way while giving them control over the output.

giving people the option to show values in between that are hidden

@mietcls well like I said in that referenced issue, the facet value "0" does not always reflect the total amount of publications for that filter value. It can also mean that filters of another type are active. Only allowing values with more than 0, would hide too much.

I am still observing this case, it is in refinement.
But it is information that should not always be visible.
For example:
We could add a button that says "show filters with 0 records" (don't mind the copy) for example. But this is cognitive load that is not helpful, and the lack of the filter also gives information.

I will make a visualisation here

@mietcls what is the status of this ticket?

@nicolasfranck I need to refine it, see status "To refine"

Will close this as when refining it, it became clear we need to fix #872 first and then go from there. Useful information still to be found in here.


fix: fastify example

the fastify example did not work, also the link to codesandbox was wrong.

anyone home?

@rburgst its not really being maintained these days I am one of the maintainer of graphql-yoga and would recommend you try that out :)


gutenberg: 0.4.2 -> zola: 0.5.0

https://www.vincentprouillet.com/blog/releasing-zola-0-5-0/
Changelog
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build zola

Success on aarch64-linux (full log)
Attempted: zola
Partial log (click to expand)

installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/p9q8hcds04dxijjnpc5rkdydqpfv40y8-zola-0.5.0
shrinking /nix/store/p9q8hcds04dxijjnpc5rkdydqpfv40y8-zola-0.5.0/bin/zola
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/p9q8hcds04dxijjnpc5rkdydqpfv40y8-zola-0.5.0/bin
patching script interpreter paths in /nix/store/p9q8hcds04dxijjnpc5rkdydqpfv40y8-zola-0.5.0
checking for references to /build in /nix/store/p9q8hcds04dxijjnpc5rkdydqpfv40y8-zola-0.5.0...
/nix/store/p9q8hcds04dxijjnpc5rkdydqpfv40y8-zola-0.5.0

Success on x86_64-linux (full log)
Attempted: zola
Partial log (click to expand)

installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/sx3cwkfjxw8k79i1cm6ndfcmmk0h9c58-zola-0.5.0
shrinking /nix/store/sx3cwkfjxw8k79i1cm6ndfcmmk0h9c58-zola-0.5.0/bin/zola
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/sx3cwkfjxw8k79i1cm6ndfcmmk0h9c58-zola-0.5.0/bin
patching script interpreter paths in /nix/store/sx3cwkfjxw8k79i1cm6ndfcmmk0h9c58-zola-0.5.0
checking for references to /build in /nix/store/sx3cwkfjxw8k79i1cm6ndfcmmk0h9c58-zola-0.5.0...
/nix/store/sx3cwkfjxw8k79i1cm6ndfcmmk0h9c58-zola-0.5.0

Success on x86_64-darwin (full log)
Attempted: zola
Partial log (click to expand)
test cmd::serve::tests::relative_path ... ok

test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

installing
post-installation fixup
strip is /nix/store/g5r4apl0za012ffs6ladinwa5w0m1l3k-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/j4dc6hqy97i7w5lp8bim1hr0ha54bsxp-zola-0.5.0/bin
patching script interpreter paths in /nix/store/j4dc6hqy97i7w5lp8bim1hr0ha54bsxp-zola-0.5.0
/nix/store/j4dc6hqy97i7w5lp8bim1hr0ha54bsxp-zola-0.5.0


Disabled  elements doesn't get styled

I've included the button mixin but my <button> element doesn't get the button[disabled] style

I tried reproducing this bug using Foundation 6.0.5 but the button imports the correct styling.

Are you really sure that you get the styling from [disabled] and not .disabled?

I created a test class .testbutton and inside the rule I included the mixin @include button-disabled;
I then created a button element <button class="button testbutton">Test</button> which had the CSS properties of opacity: 0.25 cursor: not-allowed pointer-events: none.
If you are expecting the mixin to add a disabled attribute to the button, that is not what it does. This only adds the three CSS properties to the rule. From the docs Adds disabled styles to a button by fading the element, reseting the cursor, and disabling pointer events.

Okay. My main point is that I expected @include foundation-button; to include that styling for the disabled attribute as well. In my opinion it should because it seems like a very standard use case to add that

(I accidentally clicked close)

My mistake, I totally misunderstood what you meant. Looking in the _buttons.scss it is clear that there is no styling being given to the disabled attribute. I'm not sure how Zurb wants to approach this, but I have made a fix.

:) Thanks!

Merged this in @ocularrhythm . We'll close out this issue. Thanks!


[BUG] Aqara Wireless Remote Switch H1 (WRS-R02) loses trigger remote_button_short_press

Bug description
I have an Aqara Wireless Remote Switch H1 (WRS-R02) paired via ZHA using a Home Assistant Connect ZBT-1 (previously known as Skyconnect). When I pair it, it connects and seems to work reasonably well (albeit with somewhat limited functionality). So I created an automation to control my lights and it seems to work. A couple of hours later my automation fails saying that the device has no trigger remote_button_short_press. And indeed, there are no longer any triggers available for the device.
I've tried re-pairing 3 times with the same behavior.
I get an error message in the Repairs section of Home Assistant:

The automation "Bedroom wall switch" (automation.bedroom_wall_switch) is not active because its triggers could not be set up.
Error: device does not have trigger ('remote_button_short_press', 'left').

Steps to reproduce

Pair the device so it joins the Zigbee network.

Create an automation that uses the device's triggers, e.g. like this:
automation.yaml

id: '1718226515081'
alias: Bedroom wall switch
description: ''
trigger:
  - device_id: dad78deb552a65df0cf4e9e267deab62
    domain: zha
    platform: device
    type: remote_button_short_press
    subtype: left
    id: Left
condition: []
action:
  - service: light.toggle
    metadata: {}
    data: {}
    target:
      device_id:
        - 70d61452e48167554749325bc78021e5
        - 409a93a8de755e2855c32f1a403fdf13
mode: restart

Wait for a few hours, in my case it happened within 12 hours.

Click a button, notice it does not work. Check the automation, see errors.

Expected behavior
I expect all triggers to stay available if they are ever registered.
Screenshots/Video
Screenshots

Device signature
Device signature
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0105",
      "input_clusters": [],
      "output_clusters": []
    },
    "2": {
      "profile_id": "0x0104",
      "device_type": "0x0103",
      "input_clusters": [],
      "output_clusters": []
    },
    "3": {
      "profile_id": "0x0104",
      "device_type": "0x0103",
      "input_clusters": [],
      "output_clusters": []
    }
  },
  "manufacturer": "unk_manufacturer",
  "model": "unk_model",
  "class": "zigpy.device.Device"
}

Diagnostic information
Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant Container",
    "version": "2024.7.1",
    "dev": false,
    "hassio": false,
    "virtualenv": false,
    "python_version": "3.12.4",
    "docker": true,
    "arch": "x86_64",
    "timezone": "Europe/Stockholm",
    "os_name": "Linux",
    "os_version": "5.15.0-113-generic",
    "run_as_root": true
  },
  "custom_components": {
    "frigate": {
      "documentation": "https://github.com/blakeblackshear/frigate",
      "version": "5.2.0",
      "requirements": [
        "pytz"
      ]
    },
    "hacs": {
      "documentation": "https://hacs.xyz/docs/configuration/start",
      "version": "1.34.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    }
  },
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "after_dependencies": [
      "onboarding",
      "usb"
    ],
    "codeowners": [
      "dmulcahey",
      "adminiuga",
      "puddly",
      "TheJulianJES"
    ],
    "config_flow": true,
    "dependencies": [
      "file_upload"
    ],
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp",
      "universal_silabs_flasher"
    ],
    "requirements": [
      "bellows==0.39.1",
      "pyserial==3.5",
      "zha-quirks==0.0.117",
      "zigpy-deconz==0.23.2",
      "zigpy==0.64.1",
      "zigpy-xbee==0.20.1",
      "zigpy-zigate==0.12.1",
      "zigpy-znp==0.12.2",
      "universal-silabs-flasher==0.0.20",
      "pyserial-asyncio-fast==0.11"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*slzb-07*",
        "known_devices": [
          "smlight slzb-07"
        ]
      },
      {
        "vid": "1A86",
        "pid": "55D4",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus v2"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*conbee*",
        "known_devices": [
          "Conbee III"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate+"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      },
      {
        "type": "_zigate-zigbee-gateway._tcp.local.",
        "name": "*zigate*"
      },
      {
        "type": "_zigstar_gw._tcp.local.",
        "name": "*zigstar*"
      },
      {
        "type": "_uzg-01._tcp.local.",
        "name": "uzg-01*"
      },
      {
        "type": "_slzb-06._tcp.local.",
        "name": "slzb-06*"
      },
      {
        "type": "_xzg._tcp.local.",
        "name": "xzg*"
      },
      {
        "type": "_czc._tcp.local.",
        "name": "czc*"
      }
    ],
    "is_built_in": true
  },
  "setup_times": {
    "null": {
      "setup": 0.00011825800174847245
    },
    "7fc8d8d1267c81340eaf07abc5099621": {
      "wait_import_platforms": -0.0003713670012075454,
      "wait_base_component": -0.0007061039796099067,
      "config_entry_setup": 18.338653359998716
    }
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 23345,
    "manufacturer": "unk_manufacturer",
    "model": "unk_model",
    "name": "unk_manufacturer unk_model",
    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "quirk_id": null,
    "manufacturer_code": 4447,
    "power_source": "Battery or Unknown",
    "lqi": 208,
    "rssi": -48,
    "last_seen": "2024-07-07T11:06:27",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": "0x0104",
          "device_type": "0x0105",
          "input_clusters": [],
          "output_clusters": []
        },
        "2": {
          "profile_id": "0x0104",
          "device_type": "0x0103",
          "input_clusters": [],
          "output_clusters": []
        },
        "3": {
          "profile_id": "0x0104",
          "device_type": "0x0103",
          "input_clusters": [],
          "output_clusters": []
        }
      },
      "manufacturer": "unk_manufacturer",
      "model": "unk_model"
    },
    "active_coordinator": false,
    "entities": [],
    "neighbors": [],
    "routes": [],
    "endpoint_names": [
      {
        "name": "COLOR_DIMMER_SWITCH"
      },
      {
        "name": "ON_OFF_LIGHT_SWITCH"
      },
      {
        "name": "ON_OFF_LIGHT_SWITCH"
      }
    ],
    "user_given_name": "Bedroom wall switch",
    "device_reg_id": "dad78deb552a65df0cf4e9e267deab62",
    "area_id": "204201b2099211ebac0ac1e4746e0677",
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "COLOR_DIMMER_SWITCH",
          "id": 261
        },
        "profile_id": 260,
        "in_clusters": {},
        "out_clusters": {}
      },
      "2": {
        "device_type": {
          "name": "ON_OFF_LIGHT_SWITCH",
          "id": 259
        },
        "profile_id": 260,
        "in_clusters": {},
        "out_clusters": {}
      },
      "3": {
        "device_type": {
          "name": "ON_OFF_LIGHT_SWITCH",
          "id": 259
        },
        "profile_id": 260,
        "in_clusters": {},
        "out_clusters": {}
      }
    }
  }
}

Logs
I'll try to restart in fail-safe mode and enable debug logging. Until then, here's my current HA logs:
Logs
2024-07-07 10:53:19.753 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-07-07 10:53:19.755 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-07-07 10:53:24.946 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles/themes", "/config/themes", True)])`; This function will be removed in 2025.7 at custom_components/hacs/base.py, line 1182: self.hass.http.register_static_path(f"{URL_BASE}/themes", self.hass.config.path("themes")), please create a bug report at https://github.com/hacs/integration/issues
2024-07-07 10:53:24.955 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles/frontend", "/config/custom_components/hacs/hacs_frontend", False)])`; This function will be removed in 2025.7 at custom_components/hacs/frontend.py, line 54: hass.http.register_static_path(f"{URL_BASE}/frontend", locate_dir(), cache_headers=False), please create a bug report at https://github.com/hacs/integration/issues
2024-07-07 10:53:24.963 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles/iconset.js", "/config/custom_components/hacs/iconset.js", True)])`; This function will be removed in 2025.7 at custom_components/hacs/frontend.py, line 57: hass.http.register_static_path(, please create a bug report at https://github.com/hacs/integration/issues
2024-07-07 10:53:24.967 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-07-07 10:53:24.972 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call `await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles", "/config/www/community", True)])`; This function will be removed in 2025.7 at custom_components/hacs/base.py, line 1162: self.hass.http.register_static_path(, please create a bug report at https://github.com/hacs/integration/issues
2024-07-07 10:53:32.676 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.12/site-packages/vobject/base.py:736: SyntaxWarning: invalid escape sequence '\-'
  patterns['name'] = '[a-zA-Z0-9\-_]+'

2024-07-07 10:53:32.681 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.12/site-packages/vobject/base.py:1219: SyntaxWarning: invalid escape sequence '\;'
  s = s.replace("\\", "\\\\").replace(";", "\;").replace(",", "\,")

2024-07-07 10:53:32.681 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.12/site-packages/vobject/base.py:1219: SyntaxWarning: invalid escape sequence '\,'
  s = s.replace("\\", "\\\\").replace(";", "\;").replace(",", "\,")

2024-07-07 10:53:45.213 WARNING (MainThread) [zigpy.application] Zigbee channel 11 utilization is 95.12%!
2024-07-07 10:53:45.214 WARNING (MainThread) [zigpy.application] If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.
2024-07-07 10:53:46.664 ERROR (MainThread) [homeassistant.components.automation] Automation with alias 'Bedroom wall switch' failed to setup triggers and has been disabled: device does not have trigger ('remote_button_short_press', 'left')
2024-07-07 10:53:46.759 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues

Additional information
I'm running Home Assistant Container with core version 2024.7.1.

Hey, I randomly found this thread today. I had the same issue, what fixed it for me was to use a custom quirk: https://gist.github.com/xuxiaoqiao/6ed8dcb950f26337218d0507733970a0
May take a couple tries but eventually the device will be added using this custom quirk aqara_h1_remote.RemoteH1DoubleRocker3. Once mine started using the quirk it stopped dropping from the network.

Thank you for the tip! It started working for me too, actually. Just tried again after a recent update to Home Assistant, I'm guessing ZHA was updated. ¯\_(ツ)_/¯


highlight: 3.60 -> 4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/highlight/versions.
meta.description for highlight is: "Source code highlighting tool"
meta.homepage for highlight is: "http://www.andre-simon.de/doku/highlight/en/highlight.php"
meta.changelog for highlight is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/86kxdfr59wfmxpvz03rv37a6wvp6vwn6-highlight-4.0/bin/highlight passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 4.0 with grep in /nix/store/86kxdfr59wfmxpvz03rv37a6wvp6vwn6-highlight-4.0

found 4.0 in filename of file in /nix/store/86kxdfr59wfmxpvz03rv37a6wvp6vwn6-highlight-4.0

directory tree listing: https://gist.github.com/50aaa458803684459694cd75425c1dc9

du listing: https://gist.github.com/23ea7c3f3c76395449f355afa910b411

Rebuild report (if merged into master) (click to expand)

114 total rebuild path(s)

38 package rebuild(s)

38 x86_64-linux rebuild(s)
32 i686-linux rebuild(s)
12 x86_64-darwin rebuild(s)
32 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
adapta-gtk-theme
almanah
asciidoc-full
asciidoc-full-with-plugins
btrbk
ccache
ccacheStdenv
ccacheWrapper
chrome-gnome-shell
clevis
disorderfs
evolution
evolution-ews
evolutionWithPlugins
gnome3.gnome-session
gnome3.gnome-shell
gnome3.gnome-terminal
gnome3.gnome-tweak-tool
gnome3.gnome-tweaks
gnome3.gnome_session
gnome3.gnome_shell
gnome3.gnome_terminal
gnome3.pomodoro
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
highlight
ikiwiki
kakounePlugins.rep
luksmeta
pantheon.elementary-session-settings
public-inbox
ranger
rep
spring
springLobby
tang
udiskie

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/86kxdfr59wfmxpvz03rv37a6wvp6vwn6-highlight-4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A highlight https://github.com/r-ryantm/nixpkgs/archive/ee44c2a9d9720a2a3da8922b0c61256429ca5320.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/86kxdfr59wfmxpvz03rv37a6wvp6vwn6-highlight-4.0
ls -la /nix/store/86kxdfr59wfmxpvz03rv37a6wvp6vwn6-highlight-4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @willibutz for testing.

Result of nixpkgs-review pr 121052 at ee44c2a9 run on aarch64-linux 1

2 packages marked as broken and skipped:

spring
springLobby

1 package failed to build:

public-inbox

24 packages built successfully:

adapta-gtk-theme
almanah
asciidoc-full
asciidoc-full-with-plugins
btrbk
ccache
ccacheStdenv
chrome-gnome-shell
disorderfs
evolution
evolution-ews
gnome3.gnome-session (gnome3.gnome_session)
gnome3.gnome-shell (gnome3.gnome_shell)
gnome3.gnome-terminal (gnome3.gnome_terminal)
gnome3.gnome-tweaks (gnome3.gnome-tweak-tool)
gnome3.pomodoro
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
highlight
ikiwiki
rep (kakounePlugins.rep)
pantheon.elementary-session-settings
ranger
udiskie

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

Result of nixpkgs-review pr 121052 run on x86_64-linux 1

2 packages marked as broken and skipped:

spring
springLobby

1 package failed to build:

public-inbox

30 packages built:

adapta-gtk-theme
almanah
asciidoc-full
asciidoc-full-with-plugins
btrbk
ccache
ccacheStdenv
ccacheWrapper
chrome-gnome-shell
clevis
disorderfs
evolution
evolution-ews
evolutionWithPlugins
gnome3.gnome-session (gnome3.gnome_session)
gnome3.gnome-shell (gnome3.gnome_shell)
gnome3.gnome-terminal (gnome3.gnome_terminal)
gnome3.gnome-tweaks (gnome3.gnome-tweak-tool)
gnome3.pomodoro
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
highlight
ikiwiki
rep (kakounePlugins.rep)
luksmeta
pantheon.elementary-session-settings
ranger
tang
udiskie


TASK: Code cleanup (remove unused, simplify)

Ah, the included CLI controller could be removed as well, for now… what where the plans, if any? 😜

Thanks @kdambekalns


Edit for clarity in filters.txt

Keeping language consistent between MultipleChoiceFilter and ChoiceFilter: a user selects choices, the filter matches items. I found the explanation of 'conjoined=True' a little confusing so I broke that part into two sentences. I gave an example of a query string with multiple values even though that may be obvious to some.

👍


Fix default finch protocols documentation

Current code handling default protocols: https://github.com/wojtekmach/req/blob/10a3c969296de910811f77bf51af90024874634a/lib/req/steps.ex#L1065

There is a Finch bug when using H2 over H1 connections so unless that is resolved we default to using H1. Thanks for the PR though!


feature: add experimental features flag to be only accessible in core config

add facility to unlock experimental CLI options if a core config flag is set
Verification

[ ] run python -m garak --help, experimental features should not be enabled
[ ] change system.enable_experimental to true in garak/resources/garak.core.yaml
[ ] run python -m garak --help, there should be a message between the usage summary and options that experimental features are enabled

Question - would this feature be better off in a site config? I'm concerned about garak.core.yaml's value getting accidentally clobbered in a development commit

Alright. I think for now retaining the checks predicated on garak.core.yaml are more important than the odd mis-commit, so will proceed without a .gitignore. Site config is a great place for this flag but putting it there means changing the order of loading in a way that affects garak.cli processing, and I haven't taken a call on whether that's a good idea yet. So let's proceed as is


Empty 1D tensor output

As reported by @tdegeus , the following code
xt::xtensor<double,1> A = {};
std::cout << A << std::endl;

outputs {0.} instead of {}.

At the risk of restating the obvious, A in this case is actually non-empty: A.size() == 1 instead of 0.


Multi topic filter

Adds multi topic filter.  Pulls data fetching into a context.  Reorgs some things into utils.
Note: asking for PR review from a few people not because everyone actually needs to review this, but because I'm not sure who's busy/wants to know what's up/etc.

I'll try to take a closer look at the code sometime tomorrow if others don't get to it before me. Looking at the deploy preview, though, it seems pretty functional.
One thought -- since projects may match one or many tags, it might be nice to highlight the matching tags in the project records so it's easy to see how many of the selected tags match. Also might be nice to resort the projects so that ones matching more tags show up higher in the list.


Make identifier constraint optional

https://github.com/ER-FIZKarlsruhe/fiz-oai-backend/blob/8c29982f5f852ad423bf201779c4be05b68bb570/src/main/java/de/fiz/oai/backend/controller/ItemController.java#L151-L152
The line above checks if the identifier is contained in the content. Is this constraint standard-conforming? The check especially does not parse the XML file, so the check would pass even if the identifier is a part of a comment. I suggest either replacing the hard constraint with a warning or making the check configurable so that it can be disabled via config.

Is this constraint standard-conforming?

There is not standard for oai repositories. But this check helps us to avoid bad data in the backend.
You can opt-out this check via the new configuration "checkItemIdentifierInContent" in fiz-oai-backend.properties
boolean checkItemIdentifierInContent = Boolean.valueOf(config.getProperty("checkItemIdentifierInContent", "true"));

if (checkItemIdentifierInContent && !content.contains(item.getIdentifier())) {
  throw new WebApplicationException("Cannot find the identifier in the content!", Status.BAD_REQUEST);
}


[ATB-157] Implement Telemetry package - boilerplate

Pull request check list

[X] Proper tests/regressions included?
[ ] Documentation updated?

Affected functionality
Harvester run and Galadriel Server run functions were updated to also run the telemetry tasks, starting the Prometheus server.
Description of change
Add a new package related to telemetry with some boilerplate to be used with the fuctions we want to keep track of. Also added the Proemtheus configuration and runner to be used in the future.
Which issue this pull requests fixes
https://jira-pro.its.hpecorp.net:8443/browse/ATB-157

Closing this for now.


Workspace - Title with /Chats and /Settings is not aligned properly with minimum font size

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4-36.0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Kill the app if it is in the background
Change device font size to the minimum
Relaunch New Expensify app
Note that "/ Chats" is not on the same line as Expensify logo
Tap Settings from the bottom
Note that "/ Settings" is not on the same line as Expensify logo
Select a workspace
Note that "Workspace / Settings" is aligned to the top (higher than usual)

Expected Result:
In Step 4, 6 and 8, when device font size is the minimum, the Expensify title will align accordingly
Actual Result:
In Step 4 and 6, "/ Chats" and "/Settings" are not on the same line as Expensify logo when device font size is minimum
In Step 8, "Workspace / Settings" is aligned to the top (higher than usual)
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/88fc6cbe-56a4-4948-91bb-8d5dcce8c201
View all open jobs on GitHub

We think that this bug might be related to #wave8
CC @zanyrenney

Not a blocker, adding Design label to help us align on how this should behave as the system font sizes change.

oh boy, cc @Expensify/design on this one... I don't have a great answer, other than... what if we just made it so that this part of the app didn't change if system font settings changed?
Or in the very least, we should be making sure that everything maintains perfect vertical center alignment.

Hmmmm yeah this is tricky. Seems like everything works as expected for non-Expensify workspaces right? Everything just scales down together?
Is there any possible way we could also scale down the wordmark in the same way? (This might be an absolutely nutty idea, just tossing it out there.)

what if we just made it so that this part of the app didn't change if system font settings changed?

I don't love the idea of of specifically and directly not supporting a user's choice. There's got to be another way. I just don't know if I have any good ideas for it right now.

we should be making sure that everything maintains perfect vertical center alignment.

This might be our best bet unless we can get that wordmark to scale along with the text. The titles won't sit on the same baseline anymore but at least they'd be vertically centered?

This might be our best bet unless we can get that wordmark to scale along with the text. The titles won't sit on the same baseline anymore but at least they'd be vertically centered?

Yeah, in the very least, let's just make sure the non-filtered view has the vertically centered alignment? As you mentioned, seems like that's the only one that has the very obvious bug here.

Yeah, I agree that we need to scale it after user preference.
I wonder if we can scale like an image rather than text. So Expensify/Workspace name is treated as one element that we apply scale to rather than font-size?

Oh that's an interesting approach... Def would be curious to see a solution like that.

Sounds like we agree this should scale with the user preference but keep the correct alignment, making it external.

@dukenv0307 can you please raise a PR?

Not overdue, waiting for PR here.

Was merged

@mountiny since the PR has been merged, is it now waiting for the regression hold and payment or is this issue still in progress? Did automation skip the issue 🕵 If it's on the payment stage then I'll update the labels/title

Original upwork job expired so I created a new one and sent out offers
@Ollyws Reviewer $500 - offer sent - please complete the checklist
@dukenv0307 Contributor $500 - offer sent

Thanks Olly :)
Both payments made


Expect vscode 1.42

bors r+

Guess I'll need to update my VS Code :D
On Fri, 14 Feb 2020 at 18:05, Jeremy Kolb<EMAIL_ADDRESS>wrote:

bors r+
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-analyzer/rust-analyzer/pull/3139?email_source=notifications&email_token=AANB3M7BA2X2U52L4RX7PU3RC3FORA5CNFSM4KVMAAH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELZW3BI#issuecomment-586378629,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANB3MY4MKTPY4B2S6DGN43RC3FORANCNFSM4KVMAAHQ
.

I'm just keeping you on your toes :D


Refactor towards testability, step 6: make buffer edit operations more generic

Simple edit tests won't ever touch non-local buffers, so let's allow them to pass in no-op operations. Based on #208

Closed in favour of #350


Update buildpacks.md

Summary

Small proposed changes to the way the information is presented in this section
Use Cases

Checklist

[ ] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[ ] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

I'm looking into why check links fails.

Thanks, @fg-j
No worries!

Thank you @fg-j and @TisVictress
I'll make sure to add the ref wrapper next time :)


Facebook feed not pulling through videos or cards

I have implemented this socialfeed on a few sites now (love it by the way), but the one issue I have with it is that it doesn't pull through facebook videos or cards (i think thats what it is called, e.g. when you share your contact details link it creates a card/post).
Is there any work around or plans in the future to implement this?
Thanks

@bluelevel-media Did you ever find a workaround to this?

no ended up using Facebooks plugin for that client. Still think it would be good to have this though... I suppose theres not enough of a demand for it.


Query caching and whitelisting

hashing incoming queries and caching the document would improve parse times for large queries.
It would also serve as a great point to whitelist allowed queries.
Open question: how should the whitelist be specified?
Perhaps Persisted Queries?

I would be interested to see how hashing/caching the queries would work.
However, whitelisting queries (persisted queries) defeats the purpose of using GraphQL. On paper it seems like a great idea but it takes away the flexibility of GraphQL.

Hashing / caching would be pretty straight forward to implement, but would need to be measured before it lands. I wonder if there are any good graphql benchmark suites out there?
I think persisted queries offer a few big benefits:

locking down a graph to have a similar exposure footprint as REST.
protecting against malicious users: maybe something like https://github.com/ivome/graphql-query-complexity is probably better suited for public apis.
deleting deprecated fields: in a microservice environment knowing who is using what parts of the graph  lets you fail in CI if you remove something thats still in use.

Adding complexity somehow to the context object in the resolver would be very nice! We were thinking of implementing some kind of ACL layer that rate limits complexity per user...
I imagine this would tie in to https://github.com/vektah/gqlgen/issues/5 which gives us access to the query in the resolver?

@salmana1 But for security dont yo want 2 things:

Before a query is made to know what the user can and cant do. Hence you can restrict the Nav and also restrict the queries they could type in a query IDE.
After they make a query, and it hits the server, check each table they are hitting

??

first, i think cache is a field level or object level feature. its looks like
type Object @cache(10s) {
   id : Int @cache(10s)
   name: String @cache(20s)
   price: @cache(Never)
}

in the blow case, we can define a obejct level cache time and field level cache time.

Thats a different kind of caching. This issue is for the incoming query objects, not the resolver results

I've broken this out on the project board.

Were persisted queries implemented?
If so it'd be great to have the featured listed in the readme :)

Nope, just caching. Would be pretty easy to add the hooks required to lookup a query by I'd and let the user implement the store


Switch from file_picker package to first-party file_selector and/or image_picker

As described at https://github.com/zulip/zulip-flutter/issues/114#issuecomment-1619401171 ,

now we may be able to replace both uses of file_picker with first-party plugins

namely package:file_selector and package:image_picker.
We didn't use those initially because they didn't at the time have all the features we need. It looks like they now do.
Meanwhile the third-party package:file_picker seems to not be vigorously maintained. For example see:

#825

Hey, I would like to work on this project.


feat(hacbs-994): Change CI to use catalog dir

Signed-off-by: Jon Disnard<EMAIL_ADDRESS>

@davidmogar @theflockers @johnbieren
PTAL

The shell code looks good for me. I would suggest to the team to use the "ShellCheck" extension on VScode as it checks the code style with some standards. Some bash styling stuff is hard to see so using it makes it easier to standardize the way we write shell scripts.

Thanks, I installed "ShellCheck" extension, and fixed one of the findings, but ignored another finding which was false-positive. Namely ShellCheck is really pedantic about quoting variables, presumably to avoid word-splitting mistakes... but this script uses naked word-splitting as a feature... and so it goes.
I've seen other team use ShellCheck as part of their CI pipeline/workflow. Maybe someday we can do that too.
Also, while reviewing the script with ShellCheck, I noticed a mistake I hadn't caught before. So the latest commit has some minimal extra changes. If you care to take a look, I'd appreciate the extra set of eyes. Thanks!


[Bug]: 2台机器相同的 towhee 版本0.6.1, pipeline('towhee/image-embedding-resnet50') 下载不同的pth

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
2台机器相同的 towhee 版本0.6.1, pipeline('towhee/image-embedding-resnet50') 下载不同的pth.
一台下载日志：
2022-07-13 16:36:30,310 ｜ INFO ｜ helpers.py ｜ load_pretrained ｜ 188 ｜ Loading pretrained weights from url (https://github.com/rwightman/pytorch-image-models/releases/download/v0.1-rsb-weights/resnet50_a1_0-14fe96d1.pth)

另外一台下载日志：
2022-07-13 16:18:17,810 -<PHONE_NUMBER>82496 - helpers.py-helpers:183 - INFO: Loading pretrained weights from url (https://github.com/rwightman/pytorch-image-models/releases/download/v0.1-weights/resnet50_ram-a26f946b.pth)
Downloading: "https://github.com/rwightman/pytorch-image-models/releases/download/v0.1-weights/resnet50_ram-a26f946b.pth" to /root/.cache/torch/hub/checkpoints/resnet50_ram-a26f946b.pth

### Expected Behavior

下载相同的pth

### Steps To Reproduce

_No response_

### Environment

```markdown
- Towhee version(e.g. v0.1.3 or 8b23a93):0.6.1
- OS(Ubuntu or CentOS):CentOS
- CPU/Memory:
- GPU:  GeForce RTX 3090
- Others: (NVIDIA-SMI 460.73.01    Driver Version: 460.73.01    CUDA Version: 11.2)

Anything else?
No response

@angelapytao Can you check timm version on both machines? pip show timm

diff timm, maybe the reason？

@angelapytao
We suggest writing issues in English, so that more people in our community can read this. Thanks.


RMET-3602 ::: Updated libs for 16KB page alignment

Description
Update mlkit and camera libraries to latest version, that have their shared libraries (.so files) 16KB-aligned.
Note that libsqlc-ndk-native-driver.so is not 16KB-aligned, and any app that uses it crashes, that is because the SQL Cypher library needs to be updated - out of scope of this repo.
Context

https://outsystemsrd.atlassian.net/browse/RMET-3602
https://outsystemsrd.atlassian.net/wiki/spaces/RDME/pages/4426137659/iOS+18+Android+15+Assessment
https://developer.android.com/guide/practices/page-sizes

Type of changes

[X] Fix (non-breaking change which fixes an issue)
[ ] Feature (non-breaking change which adds functionality)
[ ] Refactor (cosmetic changes)
[ ] Breaking change (change that would cause existing functionality to not work as expected)

Platforms affected

[X] Android
[ ] iOS
[ ] JavaScript

Tests

Steps:

Generate a MABS11 build with barcode plugin pointing to the latest released version
Run check_elf_alignment.sh script: ./check_elf_alignment.sh <apk_file> | grep arm64-v8a

/var/folders/ln/4t6dd54d3c1b3wm92vv9pggc0000gn/T/barcode-MABS11-no16kb_out_XXXXX.23adACzP6z/lib/arm64-v8a/libsqlc-ndk-native-driver.so: \e[31mUNALIGNED\e[0m (2**12)
/var/folders/ln/4t6dd54d3c1b3wm92vv9pggc0000gn/T/barcode-MABS11-no16kb_out_XXXXX.23adACzP6z/lib/arm64-v8a/libbarhopper_v3.so: \e[31mUNALIGNED\e[0m (2**12)
/var/folders/ln/4t6dd54d3c1b3wm92vv9pggc0000gn/T/barcode-MABS11-no16kb_out_XXXXX.23adACzP6z/lib/arm64-v8a/libimage_processing_util_jni.so: \e[31mUNALIGNED\e[0m (2**12

Point the plugin version (in Extensibility Configuration) to this branch.
Run again ./check_elf_alignment.sh <apk_file> | grep arm64-v8a - ".so" files associated with mlkit and camera should be aligned

/var/folders/ln/4t6dd54d3c1b3wm92vv9pggc0000gn/T/barcode-MABS11-RMET-3602_out_XXXXX.rNDCwvBYgp/lib/arm64-v8a/libsqlc-ndk-native-driver.so: \e[31mUNALIGNED\e[0m (2**12)
/var/folders/ln/4t6dd54d3c1b3wm92vv9pggc0000gn/T/barcode-MABS11-RMET-3602_out_XXXXX.rNDCwvBYgp/lib/arm64-v8a/libbarhopper_v3.so: \e[32mALIGNED\e[0m (2**14)
/var/folders/ln/4t6dd54d3c1b3wm92vv9pggc0000gn/T/barcode-MABS11-RMET-3602_out_XXXXX.rNDCwvBYgp/lib/arm64-v8a/libimage_processing_util_jni.so: \e[32mALIGNED\e[0m (2**14)

Checklist

[ ] Pull request title follows the format RMET-XXXX <title>
[ ] Code follows code style of this project
[ ] CHANGELOG.md file is correctly updated
[ ] Changes require an update to the documentation

[ ] Documentation has been updated accordingly

@OS-pedrogustavobilro we should also update the gradle dependency to the OSBarcodeLib-Android library right?

Yeah @alexgerardojacinto  it was done in this PR - https://github.com/OutSystems/OSBarcodeLib-Android/pull/38 (already merged). Or do you mean some other dependency?


Upgrade api and img to mitigate CVE-2023-44487

What does this PR do?:

Mitigate CVE-2023-44487

Upgrade to gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0 and specify the flag --http2-disable=true, see
Upgrade k8s.io/api, k8s.io/client-go to v0.26.10
Upgrade k8s.io/apimachinery to v0.27.7
Disable http/2 on the webhook server by default, introduced Docker build arg ENABLE_WEBHOOK_HTTP2 to enable
Fetch the latest gitops generator library module
sigs.k8s.io/yaml has no new releases
sigs.k8s.io/controller-runtime v0.14.4 is left untouched because as of drafting this PR, they have not released yet. But they're updating the 0.14. branch and are undecided on what to do about release, refer to Slack thread and thanks to @kim-tsao for finding this out.

Which issue(s)/story(ies) does this PR fixes:

restricted DEVHAS-539
PR acceptance criteria:

[ ] Unit/Functional tests

[x] Documentation

[ ] Client Impact

How to test changes / Special notes to the reviewer:
Build an image and deploy it to HAS pod. Do a basic sniff test for Application and Component create. Remember to include the updated kube-rbac-proxy image in your test.

controller-runtime released 0.14.7 yesterday https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.14.7, so i will move up to this.


fix: multi publish still loading in the same profile

Description
fix multi publish still loading in the same profile.
Reason: publish with the same profile will used the same project name and profile name to save the history and status. if user click publish again, those value will be messed up.
Solution: disable publish button if already publishing with the same profile.
Task Item
#minor
Screenshots

Coverage decreased (-0.01%) to 55.75% when pulling fe3447efb79295b47057531d88a9846d8ac7c44e on wenyluo/fixPublish into dbbec318c896c0cd97e40661cb62d004cb8be950 on main.

@VanyLaw would you please address the comments?

@VanyLaw would you please address the comments?
Also please update the branch to resolve the conflicts.
@hatpick Thanks for the comment, I addressed it.

Due to publish page was change to a large extent, I need to confirm with @alanlong9278 how to disable those profiles which were used by current publish, make sure it can not select during current publish.
So I close it now. Will send another PR later.


PEP 8 Coding Style Adjustments

I know this is not exactly an urgent matter...however, cleaner code is usually easier to maintain (and often easy to understand).
 I can submit a huge PR fix that adjusts the entire code or separate PRs for each code. Here's my current list (considering the main branch)

[ ] base.py (102 PEP 8 coding style violations)
[ ] const.py (363 PEP 8 coding style violations)
[ ] context.py (10 PEP 8 coding style violations)
[ ] data.py (1 PEP 8 coding style violations)
[ ] fundamentals.py (3 PEP 8 coding style violations)
[ ] holders.py (1 PEP 8 coding style violations)
[ ] multi.py (5 PEP 8 coding style violations)
[ ] prices.py (64 PEP 8 coding style violations)
[ ] quote.py (29 PEP 8 coding style violations)
[ ] setup.py (1 PEP 8 coding style violations)
[ ] ticker.py (5 PEP 8 coding style violations)
[ ] tickers.py (1 PEP 8 coding style violations)
[ ] fundamentals.py (47 PEP 8 coding style violations)

After that, another suggestion would be to add a linter action that automatically scans the submitted code with each PR.

Generally this is a good idea, but just remember these are guidelines not strict rules, so be thoughtful. My personal preference is to exempt E702: multiple statements on one line - this is done rarely but for good reason. May also need to exempt some E501 line too long, or adjust the max length.

Yeah, we can filter some of those. However there are some more serious things such as imports in the middle of the code, bare excepts, and things like that.
I can send a sample PR for one of the files, just to have an idea of the kind of modifications I'm talking about.

Sure go ahead


snakemake: 5.16.0 -> 5.17.0

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/snakemake/versions.
meta.description for snakemake is: "Python-based execution environment for make-like workflows"
meta.homepage for snakemake is: "https://snakemake.readthedocs.io"
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 5.17.0 with grep in /nix/store/3iysy5wswia44l8d9cmkngj81w26g8j2-snakemake-5.17.0

directory tree listing: https://gist.github.com/5f17bb5e5e09f7ecc099516aa65b0ec2

du listing: https://gist.github.com/bbc0c8cc2d0d5dab7acd6e5d1e0c6778

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
snakemake

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3iysy5wswia44l8d9cmkngj81w26g8j2-snakemake-5.17.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A snakemake https://github.com/r-ryantm/nixpkgs/archive/158a628f51777304052a1dab32a106ed9cba773a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3iysy5wswia44l8d9cmkngj81w26g8j2-snakemake-5.17.0
ls -la /nix/store/3iysy5wswia44l8d9cmkngj81w26g8j2-snakemake-5.17.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:
- snakemake

Maintainer pings
cc @Helkafen @renatoGarcia @veprbl for testing.

@renatoGarcia Thank you!


FIX Ensure tests pass by reducing to PHPUnit 7.1.3

PHPUnit 7.1.4 and higher introduces a bug with float comparisons in strings. The fix until this is resolved is to use PHPUnit 7.1.3.
Reference: https://github.com/sebastianbergmann/phpunit/issues/3185
Also updates the phpunit config file to match the schema and imports a missing exception namespace.

Gosh, that's a painful regression that you'd think they'd fix a bit more quickly. :(


Optimize scripts using Plutarch.Extra.IsData

Accidentally deleted the base branch of #121 :(

Actually this is not done yet, I'm still trying to get ProductIsData work :D


Support files not found

I tried to use chai-datetime as additional plugin and placed it in spec/javascript/support and added the require in spec_helper.js. It seems that the browser loads the js file but all methods are undefined when running the specs.
Is there anything else which has to be configured?

Did you require it after requiring chai? I just set up a new app with chai-datetime, and it worked. I did nothing more than add the chai-datetime library to spec/javascripts/support, and put //=require support/chai-datetime in spec_helper.js, right below //=require support/chai-datetime.

Thanks for your effort. I tried again with a very basic setup and found out that window.expect = chai.expect; in spec_helper.js had to be commented in to make it work with chai-datetime. Regular chai specs were working already before.


Illegal domain attribute

Hi,
i'm testing prerender service for site www.weflymate.com but when i try for example this url i get the following warning message from server and 301 redirection to https://www.weflymate.com
04:34:01,928 WARN  [org.apache.http.client.protocol.ResponseProcessCookies] (default task-56) Cookie rejected [__cfduid="dc9e47295a5b370645719c1708c7358b81475483641", version:0, domain:weflymate.com, path:/, expiry:Tue Oct 03 04:34:01 EDT 2017] Illegal 'domain' attribute "weflymate.com". Domain of origin: "service.prerender.io"
What's the problem?
Thanks in advance

You can cancel this issue...the problem is cloudflare redirection

@paulux84 can we talk about your problem? I'm having the same problem and I cannot find a solution

@paulux84 , @joaohencke  I am facing same problem. please help me if you have any solution.


Similar codes migration for redis

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 8

Complexity increasing per file
==============================
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/socket/RedisSocketTestForQuarkus.java  1
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/MockErrorMsgPublisher.java  2
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/MockPublisher.java  2

Complexity decreasing per file
==============================
+ application/consumer-redis-quarkus/src/main/java/webapp/tier/service/RedisSubscribeService.java  -3

Clones added
============
- application/consumer-redis-quarkus/src/main/java/webapp/tier/healthcheck/ReadinessHealthCheck.java  1
- application/consumer-redis-quarkus/src/test/java/webapp/tier/healthcheck/ReadinessHealthCheckTest.java  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 5

Complexity increasing per file
==============================
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/MockPublisher.java  2
- application/webapp-service/src/test/java/webapp/tier/service/socket/ServiceSocketTest.java  2
- application/webapp-service/src/main/java/webapp/tier/service/socket/ServiceSocket.java  2
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/MockErrorMsgPublisher.java  2
- application/consumer-redis-quarkus/src/main/java/webapp/tier/service/RedisDeliverSubscriber.java  1
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/socket/RedisSocketTestForQuarkus.java  1

Complexity decreasing per file
==============================
+ application/consumer-redis-quarkus/src/main/java/webapp/tier/service/RedisSubscribeService.java  -3

Clones added
============
- application/consumer-redis-quarkus/src/main/java/webapp/tier/healthcheck/ReadinessHealthCheck.java  1
- application/webapp-service/src/test/java/webapp/tier/service/socket/ServiceSocketTest.java  1
- application/webapp-service/src/main/java/webapp/tier/service/socket/ServiceSocket.java  2
- application/consumer-redis-quarkus/src/test/java/webapp/tier/healthcheck/ReadinessHealthCheckTest.java  1

Clones removed
==============
+ application/jaxrs-redis-quarkus/src/main/java/webapp/tier/service/socket/RedisSocket.java  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/MockErrorMsgPublisher.java  2
- application/webapp-service/src/main/java/webapp/tier/service/socket/ServiceSocket.java  2
- application/webapp-service/src/test/java/webapp/tier/service/socket/ServiceSocketTest.java  2
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/MockPublisher.java  2
- application/consumer-redis-quarkus/src/main/java/webapp/tier/service/RedisDeliverSubscriber.java  1
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/socket/RedisSocketTestForQuarkus.java  1

Complexity decreasing per file
==============================
+ application/consumer-redis-quarkus/src/main/java/webapp/tier/service/RedisSubscribeService.java  -3

Clones added
============
- application/webapp-service/src/main/java/webapp/tier/service/socket/ServiceSocket.java  2
- application/webapp-service/src/test/java/webapp/tier/service/socket/ServiceSocketTest.java  1
- application/consumer-redis-quarkus/src/main/java/webapp/tier/healthcheck/ReadinessHealthCheck.java  1
- application/consumer-redis-quarkus/src/test/java/webapp/tier/healthcheck/ReadinessHealthCheckTest.java  1

Clones removed
==============
+ application/jaxrs-redis-quarkus/src/main/java/webapp/tier/service/socket/RedisSocket.java  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/MockErrorMsgPublisher.java  2
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/socket/RedisSocketTestForQuarkus.java  1
- application/webapp-service/src/test/java/webapp/tier/service/socket/ServiceSocketTest.java  2
- application/consumer-redis-quarkus/src/main/java/webapp/tier/service/RedisDeliverSubscriber.java  1
- application/webapp-service/src/main/java/webapp/tier/service/socket/ServiceSocket.java  2
- application/jaxrs-redis-quarkus/src/test/java/webapp/tier/service/MockPublisher.java  2

Complexity decreasing per file
==============================
+ application/consumer-redis-quarkus/src/main/java/webapp/tier/service/RedisSubscribeService.java  -3

Clones added
============
- application/consumer-redis-quarkus/src/test/java/webapp/tier/healthcheck/ReadinessHealthCheckTest.java  1
- application/webapp-service/src/test/java/webapp/tier/service/socket/ServiceSocketTest.java  1
- application/consumer-redis-quarkus/src/main/java/webapp/tier/healthcheck/ReadinessHealthCheck.java  1
- application/webapp-service/src/main/java/webapp/tier/service/socket/ServiceSocket.java  2

Clones removed
==============
+ application/jaxrs-redis-quarkus/src/main/java/webapp/tier/service/socket/RedisSocket.java  -2

See the complete overview on Codacy


make filename length hard limit

resolves #744

Codecov Report

Merging #752 into master will decrease coverage by <.01%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##           master     #752      +/-   ##
==========================================
- Coverage    73.5%   73.49%   -0.01%
==========================================
  Files          51       51
  Lines       16177    16177
==========================================
- Hits        11891    11890       -1
- Misses       4286     4287       +1

Impacted Files
Coverage Δ

androguard/misc.py
61% <100%> (-1%)
:arrow_down:

tests/test_misc.py
92.5% <50%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eef9735...d43194c. Read the comment docs.


Update Spec test protos

This pulls in firebase/firebase-js-sdk#2594

I presume it's okay that all versions are increased? I guess the generator code could check for zero explicitly.

Yes. It doesn't make much of a difference, as long as there is no zero version.


[Bug]:

Version
28.0.0.alpha-7
Steps to reproduce
jest.config.ts
const config: Config.InitialOptions = {
  preset: "ts-jest",
  testEnvironment: "node",
  clearMocks: true,
}

"jest": "^28.0.0-alpha.7",
"ts-jest": "^27.1.4"
All these settings were working as of 3 weeks ago. I cleared my package-lock file and with a clean install i now get an error when running tests. I think there is a mismatch between the pacakges that are being installed.
Expected behavior
Tests to run without errors.
Actual behavior
● Test suite failed to run
● Invalid return value:
  Code transformer's `process` method must return an object containing `code` key
  with processed string. If `processAsync` method is implemented it must return
  a Promise resolving to an object containing `code` key with processed string.
  Code Transformation Documentation:
  https://jestjs.io/docs/code-transformation

Additional context
No response
Environment
Macos 12.3.1
Node: v14.17.3
npm: 6.14.13

ts-jest isn't compatible with Jest 28. You should file the issue over there.


Add staticmethod to parse base64 encoded images

Summary of changes:

Add from_base64_image static method
Add sample base64 image as a text file

Test is not passing :(

Feel free to close this, but I actually had to write this up for my project, so I figured I'd open a PR here too.
Also could not quite figure out how to write the test with syrupy...

You need to run pytest --snapshot-update to save the snapshot to disk (and check it looks correct).
Then, every time that test runs in the future, it'll validate that the output doesn't change compared to that snapshot.

Ahhh yeah thanks!! That worked perfectly, and all tests passed 🚀

It should have generated a new snapshot image, which you'll also need to push up to this PR so that when other people run your test, it checks the output of the test against that snapshot :)

There you go! Thanks for the quick response! ⚡ ⚡


[VCM] add new option ToolbarHide After timeout and Startup action

Summary of the Pull Request

PR Checklist

[x] Closes: #14123
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Add new option ToolbarHide After timeout, allow always hide Toolbar no matter what state
Add new behavior option startup action, allow Unmute/Mute when startup for privacy
Fix Mute/Unmute logic, all controlled mic should be same state avoid manually change in Control Panel

Validation Steps Performed

Select behavior 'Mute' > Unmute all > Restart > All should muted
Have multiple Microphone devices > Change system sound > Change Default device level to unmute, Other mute > PowerToys Toggle shortcut > All devices should mute

@microsoft-github-policy-service agree

@yuyoyuppe Hi, could you review this?

I think you were hit with a bad upgrade of spellcheck. It's been reverted on main already. Please merge main in so CI passes? :)


Fix Invalid  Lifi Swap Fee

Fix https://github.com/vultisig/vultisig-android/issues/1476
The current swap fee for the Lifi provider is incorrect and lower than expected
https://playground.li.fi/?fromAmount=0.001&fromChain=10&fromToken=0x0000000000000000000000000000000000000000&toChain=1&toToken=0x0000000000000000000000000000000000000000
@enriquesouza  Please update your code; this issue also occurs on iOS
Uses https://github.com/vultisig/commondata/pull/23
Before

After

@yvebe
It relies on  https://github.com/vultisig/commondata/pull/23 which has not been merged yet . I believe this might causes issues when attemping to build the app


Form field unique selectors: align on using id where possible, backport QE-test-breaking changes to 2.1.2 (selector attributes only), follow up to help fix QE tests

Related to https://github.com/konveyor/tackle2-ui/issues/198. Ideally we can fix both together.
For rationale, see the "Accessibility and QE selectors" section at the bottom of the description in https://github.com/konveyor/tackle2-ui/pull/404. The main conclusions there are:

We need a unique id attribute on each form input in order to provide accessible labels without redundant aria-label attributes
We should NOT use aria-label as a selector for QE tests since it is user-facing copy that is subject to change (it is used by screen-readers for accessibility)
QE tests should use id selectors where possible, and work with dev on what selector to use when id cannot be provided on a case-by-case basis. When this comes up it is likely a bug in PatternFly and we can provide a real id once that bug is addressed.

https://github.com/konveyor/tackle2-ui/pull/404 included changes to support the above for the Proxy settings form and the Identity form (the Create/Edit Credential modal in the Admin view). That PR includes heavy refactoring that should not be backported to 2.1.x, but we should create a separate PR to backport matching id / aria-label changes to 2.1.2 once that release branch exists. We should then make sure we follow up to help transition relevant QE tests to use the new id selectors.
As more forms are refactored to use the new react-hook-form components, we will also be aligning their field attributes in a similar way, and any of those that are merged before 2.1.2 code freeze should also have their selector changes backported as part of this issue.

PRs containing changes that will break QE tests, which should have custom backport PRs to align the 2.1.2 branch to use their new field selectors:

https://github.com/konveyor/tackle2-ui/pull/404

Please edit this comment to add more if you identify them.

QE Requests (7 Sept 2023 - initially from https://github.com/konveyor/tackle2-ui/issues/1336) :

[x] Cancel button ID to be 'cancel' across the UI.
[x] Submit button ID to be 'submit' across the UI.
[ ] Top table level Kebab ID (for example id="toolbar-kebab") across the UI so it can be identified consistently (same ID) on every page where there is a top level dropdown (kebab).

[x] appliactions-table-assessment.tsx: Toolbar and row IDs
[ ] applications-table-analysis.tsx: Toolbar and row IDs
[ ] migration-waves.tsx : Toolbar ID
[ ] Pages with table rows having several actions component, such as edit (pencil icon) and actions (kebab with dropdown) must have a selector to distinct them from each others. Note there is no need to be uniquely named across rows.


Add custom pagination [button like pagination filled by some text]

I am trying to get some functionality where I can add custom tiles instead of pagination(Example slider is attached), I know there is an option of custom pagination but I am not able to add custom button tiles, I have to edit global scss file for that or it can not  be achieve

Hi @walifaizy , you can use 2 slides to achieve this behavior. Please refer demo page for implementation method (Thumbs Gallery With Two-way Control)

thanks @kidjp85 , solved my issue


collapsible filters (#287)

adds and tests a new toggleTab() function for adding/removing aria-selected attribute on the tabs. allows the tabs to be opened by clicking or pressing space/enter when they're focused.

Codecov Report

Merging #406 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #406      +/-   ##
===========================================
+ Coverage    98.37%   98.37%   +<.01%
===========================================
  Files          167      167
  Lines         7645     7650       +5
  Branches        26       26
===========================================
+ Hits          7521     7526       +5
  Misses         124      124


Allow typing RouteMeta

Does this mean /123 will be a real Number? If so, I also hope enums will be supported. So when there is /Sea/123 it should be possible to know its coming from
export enum Type {
    Road = 0,
    Sea = 1,
}

That’s another thing: Param matchers. Also planned thought!


CMake package should add the modules to CMAKE_MODULE_PATH

Issue: https://github.com/awslabs/aws-c-event-stream/issues/15
Right now aws-c-event-stream needs a lot of boilerplate code to determine the modules installation path while the aws-c-common package should provide it.
This would fix https://github.com/awslabs/aws-c-event-stream/issues/15 simply by moving find_package(aws-c-common REQUIRED) before the various module includes
Using configure_package_config_file makes it easier to have a relocatable package.
A pull request will be opened in aws-c-event-stream too.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Any news on this ?
I'm waiting for this PR and https://github.com/awslabs/aws-c-event-stream/pull/33 to be merged so that we can set our CI back to upstream and get the latest updates.

I think this is a great change, but we'd need to apply it evenly across all the repos (there's 8 more), so it will take time. It's also a lot of work when we get the cmake stuff wrong to get them upgraded. We're evaluating this and we'll apply it next time we touch our cmake.
As for the linked issue, it looks like your code is out of date. The actual bug was fixed a while ago.
Are you having problems with the latest commit?

As for the linked issue, it looks like your code is out of date. The actual bug was fixed a while ago.
Are you having problems with the latest commit?

Sorry I missed the question last time.
Yes I was having issues when building on amazon linux 2, using the latest commits at the time. That would be 60d5f8de6d4e237c7e7ac2014266d4948116f9e3.
Should I try with latest master ?


Changed 70 to 71

Hyperlink in version section

[x] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@pal3635, this link does not go anywhere. Marking as invalid.


[Enhancement] Enhance Vertical Split Visual Clarity with Distinct Active Window Borders

Description
When using the plugin with a vertical split layout containing only two windows, it becomes difficult to discern which window is currently active because there is only a single dividing line between them. This can lead to confusion and inefficiency, as users might type or perform actions in the wrong window.
Expected Behavior
I would like to propose a feature where there is a more distinct visual cue to indicate the active window when only two windows are present in a vertical split layout.
Current Behavior
At present, the plugin indicates the active window in a vertically split view by lighting up only half of the dividing line: the upper half if the right window is active, and the lower half if the left window is active. While this does provide an indication of which window is focused, the signal is quite subtle and can be easily overlooked.

Steps to Reproduce

Open the plugin and create a vertical split layout with two windows.
Click between windows to change the focus.
Observe that there is no clear indication of which window is active, other than the cursor location.

Additional Information
This enhancement would greatly improve the user experience by making it easier to identify the active window at a glance, especially for users who frequently switch between only two vertical split windows.
Thank you for considering this feature request. I believe it would benefit many users of your plugin.

I don't have any good ideas at the moment. Could you provide some guidance?

I don't really have a good method to recommend either. How to label two vertically split windows largely depends on personal aesthetics.
Perhaps, using "」" for the left and "「" for the right, utilizing a bit more horizontal extension to mark the current window.
I haven't actually tested this method, so it might not be truly suitable.

This sounds to be a very reasonable idea, just make the end piece of the separator line a corner that points towards the active pane.

https://github.com/nvim-zh/colorful-winsep.nvim/assets/57088952/7ee96394-af0a-46ce-b23c-ae2905075611

Edit the config.light_pollution callback function, which passes the current dividing line
	light_pollution = function(lines)
		local v_smooth = 0
		local s_smooth = 0
		for dir, line in pairs(lines) do
			local timer = vim.uv.new_timer()
			local height = line:height()
			timer:start(
				1,
				50,
				vim.schedule_wrap(function()
					local status = true
					if line:is_show() and (dir == "h" or dir == "l") then
						if v_smooth ~= line:height() then
							status = false
							local symbol = line.body_symbol
							if v_smooth == 0 then
								symbol = line.start_symbol
							end
							if v_smooth + 1 == height then
								symbol = line.end_symbol
							end
							line:pos_color(v_smooth, 0, "Error", symbol)
							v_smooth = v_smooth + 1
						end
					end
					if status and not timer:is_closing() then
						timer:stop()
						timer:close()
					end
				end)
			)
			local timer2 = vim.uv.new_timer()
			local width = line:width()
			timer2:start(
				1,
				4,
				vim.schedule_wrap(function()
					local status = true
					if line:is_show() and (dir == "j" or dir == "k") then
						if s_smooth ~= line:width() * 3 then
							status = false
							local symbol = line.body_symbol
							if s_smooth == 0 then
								symbol = line.start_symbol
							end
							if s_smooth + 1 == width then
								symbol = line.end_symbol
							end
							line:pos_color(0, s_smooth, "Error", symbol)
							s_smooth = s_smooth + 1
						end
					end
					if status and not timer2:is_closing() then
						timer2:stop()
						timer2:close()
					end
				end)
			)
		end
	end,

2024-05-20_23-03-33.mp4
@v-tibi @huangpufan

That is very cool but I don't see how it address this issue in particular.
I think you should be able to insert an indicator either on either end or the midpoint of the diving line. Idk how it would be implemented but imagine a config like:
indicator = {   position = 'center', // 'top', 'bot', 'topbot'   symbols = {     left = '',     right = '',     up = '',     down = '',   }, },

2024-05-20_23-03-33.mp4
@v-tibi @huangpufan

这非常酷，但我不知道它是如何特别解决这个问题的。
我认为您应该能够在潜水线的两端或中点插入一个指示器。 我不知道它是如何实现的，但想象一下这样的配置：
indicator = {
  position = 'center', -- 'top', 'bot', 'topbot', 'all',
  symbols = {
    left = '',
    right = '',
    up = '',
    down = '',
  },
},

	light_pollution = function(lines)
		for dir, line in pairs(lines) do
			if line:is_show() and (dir == "h" or dir == "l") then
				if dir == "h" then
					line:pos_color(line:height() / 2, 0, "Error", ">")
				elseif dir == "l" then
					line:pos_color(line:height() / 2, 0, "Error", "<")
				end
			end
		end


A better ICMP library

Hello,
I just notice that in #47 the lib/icmp and icmp_scan need to run as root to be working, I glad if someone can give us a better solution and contribute a new lib and replace the libraries.
let me know if anyone has any idea.
Best Regards.

Hey @Ali-Razmjoo,
I read about the issue of running icmp scan as root but I can't seem to find a possible solution. This is because we need to create a raw socket while sending a icmp packet and linux doesn't allow creation of raw sockets without root privileges. Alternatively we can use the ping command to run in the background using os.system('ping host'). But it won't serve the same purpose as that of a full fledged icmp library. So, I think we should implement it in the following way.

Check if the user logged in has root privileges
If it has root permissions, use the existing library to perform the task
Otherwise we can resort to os.system('ping host')

Regards.

I would like to know your views on the above implementation.

Hello,
Please let me research on this topic, I will get back to you soon, thank you for sharing your solution.
Regards.

Hello,
icmp_scannning is just a way to know if target is active, we can do this with simple ping like this
``
import os
hostname = "google.com" #example
response = os.system("ping -c 1 " + hostname)
if response == 0:
print hostname, 'is up!'
else:
print hostname, 'is down!'
``
am I missing something?

it gets extra time to do that, I think we are going to focus on docker image instead to avoid such issues.

@pallav12  the whole idea of Nettacker is to be 100% in python and not dependent on other tools installed in OS like nmap/ping etc-  calling an OS command is not scaleable in terms of pythons multi-threading. Most people run nettacker in Kali Linux as root anyway and can also use it in docker as @Ali-Razmjoo has already mentioned.

Ohh okay, makes sense

icmplib is a new library which provides a pure Python implementation of the ICMP protocol along with the option of running as non-root.

@abinpaul1 👍
yeah we will add this as dependecy https://pypi.org/project/icmplib/

@Ali-Razmjoo I would be happy to work on this. However the library is only compatible with python 3.6+.
So I think I could go about it in two ways

Keep the current implementation and use the new library if python version is more than 3.6
Replace the current implmentation
Do let me know, I would be happy to open a pull request for the same

done in #440

Hi
I could see a lot of changes made in the PR,
However it seems the ICMP implementation still requires root to run. Was the idea to use 'icmplib' (which provides an option to run ping as non root) dropped


AD/LDAP login integration

Have you considered adding some kind of AD/LDAP integration so that when this application is deployed in a secure internal environment can be accessed with already existing users database?
RBAC not needed in this phase, but it would be nice to have this kind of option instead of using Cognito.
Anyway, I wanted to say thanks for this app as it's really a nice option to have!

sounds good, will start working on it

SInce in my case I'm using a SAML 2.0 identity provider for logging to AWS services, and Cognito supports adding identity providers that could be easily re-used.
Not a React/javascript programmer so I'm not quite familiar with changing much in the code, but could this be used as-is to login using Cognito user pool + identity pool users?

yeah thats the path I would be heading down, simply changing cognito to use identity pools. I havn't done it before though so have to research and test it.

I found 2 guides that might be close to what you are looking for? I was hoping AWS SSO would support it out of the box but looks like not currently, Which provider are you going with so I can spin up a test one?
I found 2 guides for ADFS and Okta:
https://aws.amazon.com/premiumsupport/knowledge-center/cognito-okta-saml-identity-provider/
https://aws.amazon.com/blogs/mobile/building-adfs-federation-for-your-web-app-using-amazon-cognito-user-pools/
There's a code sample for Okta here as well:
https://github.com/aws-amplify/amplify-js/issues/2806
Or the offical doco has more details:
https://aws-amplify.github.io/docs/js/authentication#identity-pool-federation
Let me know which one and I'll test it out and see if I can get a sample

Hi, our use case is with DAG (DUO access gateway) https://duo.com/docs/dag
We use it as a SAML2.0 provider for logging in to AWS with 2FA
https://aws.amazon.com/quickstart/architecture/duo-mfa/
Not sure if you are familiar with it

Hey @gek0 I havn't been able to get this to work, I'll leave it open for another week and see if anyone else can help otherwise I'll have to close this request as its out of scope for the project sorry.
Hopefully we can find someone with experience in cognito with this before.
Thanks,

Hey @gek0
I'm closing this feature since its out of scope and I havn't been able to implement it. Happy to reopen if anyone finds a way to get it to work with any provider and I'll write the doco for it.
Thanks,