kubernetes: 1.28.4 -> 1.29.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kubernetes/releases.
meta.description for kubernetes is: Production-Grade Container Scheduling and Management
meta.homepage for kubernetes is: https://kubernetes.io
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.29.0 with grep in /nix/store/sr3a1jy4wm7a47q291xswv2cvmfzkbzw-kubernetes-1.29.0
found 1.29.0 in filename of file in /nix/store/sr3a1jy4wm7a47q291xswv2cvmfzkbzw-kubernetes-1.29.0

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
chart-testing
gsctl
kns
kubectl
kubectl-convert
kubernetes
kubetail
tubekit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sr3a1jy4wm7a47q291xswv2cvmfzkbzw-kubernetes-1.29.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 kubernetes https://github.com/r-ryantm/nixpkgs/archive/5518253a51163c40903ee3eb33689afe448c66dd.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5518253a51163c40903ee3eb33689afe448c66dd#kubernetes

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sr3a1jy4wm7a47q291xswv2cvmfzkbzw-kubernetes-1.29.0
ls -la /nix/store/sr3a1jy4wm7a47q291xswv2cvmfzkbzw-kubernetes-1.29.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 run on x86_64-linux 1

8 packages built:

chart-testing
gsctl
kns
kubectl
kubectl-convert
kubernetes
kubetail
tubekit

Maintainer pings
cc @johanot @offlinehacker @saschagrunert @srhb for testing.

@GrahamcOfBorg test kubernetes

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kubernetes/releases.
meta.description for kubernetes is: Production-Grade Container Scheduling and Management
meta.homepage for kubernetes is: https://kubernetes.io
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.29.1 with grep in /nix/store/j0wfc1n8jahcdf1n5hp2cmzbh1y3gpdw-kubernetes-1.29.1
found 1.29.1 in filename of file in /nix/store/j0wfc1n8jahcdf1n5hp2cmzbh1y3gpdw-kubernetes-1.29.1

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
chart-testing
gsctl
kns
kubectl
kubectl-convert
kubernetes
kubetail
tubekit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j0wfc1n8jahcdf1n5hp2cmzbh1y3gpdw-kubernetes-1.29.1 \
  --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 kubernetes https://github.com/r-ryantm/nixpkgs/archive/c65cf13ad1190ce7cc32a59e1be815858c6894f8.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c65cf13ad1190ce7cc32a59e1be815858c6894f8#kubernetes

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j0wfc1n8jahcdf1n5hp2cmzbh1y3gpdw-kubernetes-1.29.1
ls -la /nix/store/j0wfc1n8jahcdf1n5hp2cmzbh1y3gpdw-kubernetes-1.29.1/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 run on x86_64-linux 1

8 packages built:

chart-testing
gsctl
kns
kubectl
kubectl-convert
kubernetes
kubetail
tubekit

Maintainer pings
cc @johanot @offlinehacker @saschagrunert @srhb for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kubernetes/releases.
meta.description for kubernetes is: Production-Grade Container Scheduling and Management
meta.homepage for kubernetes is: https://kubernetes.io
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.29.2 with grep in /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2
found 1.29.2 in filename of file in /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
chart-testing
gsctl
kns
kubectl
kubectl-convert
kubernetes
kubetail
tubekit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2 \
  --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 kubernetes https://github.com/r-ryantm/nixpkgs/archive/dffc7922ae07841bb8cff0fced1ceb30b3e12384.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/dffc7922ae07841bb8cff0fced1ceb30b3e12384#kubernetes

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2
ls -la /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2/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 run on x86_64-linux 1

8 packages built:

chart-testing
gsctl
kns
kubectl
kubectl-convert
kubernetes
kubetail
tubekit

Maintainer pings
cc @johanot @offlinehacker @saschagrunert @srhb for testing.

@wegank I marked this as ready again since tests are now passing in master. Let me know if that's a mistake. :)

I wonder why they still don't, according to ofborg, on x86_64-linux.

Because it needs rebase with master

Rebased.
@ofborg test kubernetes


Add Lua script debugging

Moonsharp supports debugging via VS Code. Need to add a way to support this.

This has been added but needs more testing.


Fix compiler options setting

quotes should not be used, they break multiple options support
cmake already using CMAKE_CXX_FLAGS, no need to add them again
CMAKE_CPP_FLAGS belong to options and not definitions

Thanks @isanych,
I'm not sure about this:

CMAKE_CPP_FLAGS belong to options and not definitions

CPPFLAGS are considered definitions. I may move it back later. I need to test on some older platforms.
Thanks for the patch.

@isanych,
This change just broke armel:
/usr/bin/c++   -O2 -g -DNDEBUG -fPIC -march=armv7-a -mfpu=neon -MD -MT CMakeFiles/cryptopp-object.dir/aria_simd.cpp.o -MF CMakeFiles/cryptopp-object.dir/aria_simd.cpp.o.d -o CMakeFiles/cryptopp-object.dir/aria_simd.cpp.o -c /cryptopp/aria_simd.cpp
In file included from /cryptopp/aria_simd.cpp:18:
/usr/lib/gcc/arm-linux-gnueabi/11/include/arm_neon.h:31:2: error: #error "NEON intrinsics not available with the soft-float ABI.  Please use -mfloat-abi=softfp or -mfloat-abi=hard"
   31 | #error "NEON intrinsics not available with the soft-float ABI.  Please use -mfloat-abi=softfp or -mfloat-abi=hard"
      |  ^~~~~
/cryptopp/aria_simd.cpp:63:34: error: ‘uint32x4_t’ does not name a type; did you mean ‘uint32_t’?
   63 | inline void ARIA_GSRK_NEON(const uint32x4_t X, const uint32x4_t Y, byte RK[16])
      |                                  ^~~~~~~~~~
      |                                  uint32_t
/cryptopp/aria_simd.cpp:63:54: error: ‘uint32x4_t’ does not name a type; did you mean ‘uint32_t’?
   63 | inline void ARIA_GSRK_NEON(const uint32x4_t X, const uint32x4_t Y, byte RK[16])
      |                                                      ^~~~~~~~~~
      |                                                      uint32_t
   ...

Cmake does not work like users expect. It is half-ass, poorly tested software. It is why we removed official support for it.


Add an auto-lock timer option

There should be an optional setting to set the extension to auto-lock after a certain amount of time. This will add additional security for those who want it.

Auto-lock after Unlock or after last action?
First one might be easy, if the latter, what do we consider an action?

Hey, do you think you can use this to determine if the browser is "idle": https://developer.chrome.com/apps/idle
It looks like that can determine if the browser is idle for a specified amount of time, or if the machine is "locked".

Is it really what the users want though?
If they keep using the browser (but not the extension), the wallet won t lock


beeline: get username from UnixSystem api

Since we haven't enabled hive server side authentication, user could impersonate anyone from beeline client. To prevent this, we do not allow user to pass the username, rather we query the UnixSystem api to get the actual username. We can revisit this once we have kerberos authentication enabled on the server side.

Shipit


Validation of BEL 2.0 expression (rxn) fails

Examples taken from BEL 2.0 specification
Valid term
rxn(reactants(a(CHEBI:superoxide)),products(a(CHEBI:"hydrogen peroxide"), a(CHEBI:"oxygen"))
delivers following validation object:
{
    "validation": {
        "expression": "rxn(reactants(a(CHEBI:superoxide)),products(a(CHEBI:\"hydrogen peroxide\"), a(CHEBI:\"oxygen\"))",
        "message": "Invalid syntax.",
        "term_signatures": [

        ],
        "valid_semantics": false,
        "valid_syntax": false,
        "warnings": [

        ]
    }
}

Tested with BEL 2.0 endpoint and API method "/api/expressions/{term}/validation".

This was a BEL syntax error in the specification. It was missing an closing parenthesis, after adding it the semantic validation was a success.


Raise error if end() is called with undefined argument instead of noop-ing

I expect Request.end() to raise an error if you pass it an undefined argument. Instead, it calls a no op.
If this change is acceptable, I can add a test for it.

Thanks for your involvement. However, sending a request (as request.end does) not subscribing to the response (that is, with no callback) seems like a legit use case.

@alex94puchades, ah, this seems obvious to me now but I wasn't thinking of that before. I just had an idea though.
What if you raised the error if ( arguments.length == 1 ) && ( typeof fn == 'undefined' )?
However, after typing this out, I guess I could see code where you pass end a callback that only is only defined sometimes and depend on it to noop? Feel free to close this if you're convinced that passing end() an undefined argument is a valid use case as well.
I'm probably too tired to be thinking about this right now, so sorry if this is a dumb idea for some obvious reason.

Not convinced this in an improvement. I recommend closing.


Exclude source artifacts from npm publish

Fixes #24, #25.
These files don't need to be included in the published package on npm, so they should be npmignored.  In particular, the extraneous .babelrc is causing problems with projects using Babel 6 (including all React Native projects with the latest version of react-native).
(This change allows you to leave your .babelrc in source, as opposed to #26.)

Thanks! Released in 0.6.1

Thanks for the quick merge! :tada:


jax.random.key tree comparison results in a ZeroDivision warning

See below:
import jax
import chex

chex.assert_trees_all_equal(jax.random.key(0), jax.random.key(0))
> RuntimeWarning: divide by zero encountered in equal val = comparison(x, y)

# Runs fine
chex.assert_trees_all_equal(jax.random.PRNGKey(0), jax.random.PRNGKey(0))

The problem is not jax per se, since key comparison works:
jax.random.key(0) == jax.random.key(1)
> Array(False, dtype=bool)

jax.random.key(0) == jax.random.key(0)
> Array(True, dtype=bool)

Wanted to mention that the problem isn't chex per se, the problem is the jax random key not converting to a proper numpy type in the numpy test function.
Meaning, the problem is located in np.testing.assert_allclose where the jax type is converted using:
np.asanyarray(jax.random.key(0))
> array(PRNGKeyArrayImpl[fry] { [0 0] }, dtype=object)

np.asanyarray(jax.random.PRNGKey(0))
> array([0, 0], dtype=uint32)

Hi! Thanks for reporting. I don't think this should be handled in Chex since, as you correctly noticed, the warning arises in the Numpy <-> JAX interactions.
Closing this issue for now.


Telemachus should have a leading 'v'.

Otherwise v<IP_ADDRESS> gets loaded, which is old

Merging with my thanks.


[docs] - Add a docs directory and clear the README.md

Hello, i really think the project will start to require a docs directory to have a real wiki sections.
Because the README with all the step can push people away from this project.

Thanks for the feedback!


Fix : null exception (subscription close)

What does this PR do?
Fix a null access exception
Test Plan
Random happening
Related PRs and Issues
Have you read the Contributing Guidelines on issues?
Yes but it was to complex for us to use PHP. We thus propose this PR and understand if you refuse it. Just pay attention that there is a simple error in the appwrite client code.

Unfortunately, this is a read-only repo as the code is generated by our SDK Generator, and changes made only here would be wiped in the next release.

Unfortunately, this is a read-only repo as the code is generated by our SDK Generator, and changes made only here would be wiped in the next release.


[AutoPR] managementpartner/resource-manager

Created to accumulate context: managementpartner/resource-manager

(message created by the CI based on PR content)

Codecov Report

Merging #2183 into master will increase coverage by 0.01%.
The diff coverage is 70.87%.

@@            Coverage Diff             @@
##           master    #2183      +/-   ##
==========================================
+ Coverage   52.06%   52.07%   +0.01%
==========================================
  Files        5567     5572       +5
  Lines      133508   133573      +65
==========================================
+ Hits        69510    69560      +50
- Misses      63998    64013      +15

Impacted Files
Coverage Δ

...managementpartner/operations/partner_operations.py
100% <100%> (ø)
:arrow_up:

.../mgmt/managementpartner/models/partner_response.py
100% <100%> (ø)
:arrow_up:

...er/azure/mgmt/managementpartner/models/__init__.py
100% <100%> (ø)
:arrow_up:

...t/managementpartner/models/partner_response_py3.py
100% <100%> (ø)

...mgmt/managementpartner/models/operation_display.py
44.44% <16.66%> (ø)
:arrow_up:

...gmt/managementpartner/models/operation_response.py
50% <20%> (ø)
:arrow_up:

...mt/managementpartner/models/extended_error_info.py
57.14% <25%> (ø)
:arrow_up:

...rtner/azure/mgmt/managementpartner/models/error.py
70% <33.33%> (ø)
:arrow_up:

.../managementpartner/models/operation_display_py3.py
44.44% <44.44%> (ø)

...nagementpartner/operations/operation_operations.py
41.93% <50%> (+1.93%)
:arrow_up:

... and 8 more

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 515bb1f...647634f. Read the comment docs.

@lmazuel this PR looks good, can you please merge it.


Change entity name to include model and serial number

Testing...

For an existing installation, the entity_id does not change from wf_SENSOR_NAME, but the Name changes. This must be because we don't change the unique_id. This not as severe a breaking change, as automations do not need to be edited.
I will try and delete my current installation, and see what happens when a new user installs.

For an existing installation, the entity_id does not change from wf_SENSOR_NAME, but the Name changes

That's what I was hoping would happen and kind of expected as I had been doing a number of other tests and iterations during the whole process. With a new install, it will show up with the new names. But this is good because those who have already renamed the device should see minimal changes.

It works as expected. You can merge this👍🏻


BasicExecutor keep threads in ConcurrentLinkedQueue,just add?

BasicExecutor just add threads in queue, will be too many object in this queue?

The number of threads used by the Disruptor doesn't change once set up, if it starts it will be okay.  The BasicExecutor is just a wrapper around a ThreadFactory to provide compatibility for old versions.


Implementation of the resistor-color exercise

This PR provides the resistor-color exercise for the Erlang track.
On a side note, the contribution guidelines are out of date.
So is the check-exercises escript, which looks for the exercises directly under exercises/, but they (now) live one level deeper. Accordingly, it will fail.

So is the check-exercises escript, which looks for the exercises directly under exercises/, but they (now) live one level deeper. Accordingly, it will fail.

Maybe you could submit a PR to fix this first and then rebase this PR once that is merged? That would make it easier to see if this PR works as intended.

Juhlig is right, the script is broken, but only meant to be used locally and not the reason for CI failing.
I can not even say why CI fails. It seems as if I have to take a closer look at that from master later today/this week.
On the other hand side, I had expected much newer OTP releases to be used for running the tests, something in the range from 22 to 25…
Something with the autodiscovery of available releases seems to have gone wrong and I need to check that anyway.


Fix v2-full lexer injecting pp. directives after ext. declarations

When using the v2-full lexer it is necessary to inject at least some preprocessor directives back to the AST so they appear in the transpiled GLSL.
The lexer supports this use case for preprocessor directives in external declaration position, but the tests that cover this injection functionality do not check that the results are correct when there are several external declarations in a translation unit.
As a result, when transpiling the following GLSL source back to GLSL:
#version 110
invariant x;
#pragma once
invariant y;

The output is unexpected:
invariant x;
#version 110
invariant y;
#pragma once

Given that the order of preprocessor directives is significant, this is an incorrect behavior. I pinned down the cause of this problem to a bad computation of the declaration start position in the injection code.
These changes improve the AST directive injection in this case and add a test for this problem.
(By the way, thank you for these wonderful GLSL parsing libraries, they are very much needed! :heart:)

I think you also need to change the signature for parse_pp when the lexer-v2-full feature is not available. This is the one that breaks when running the following tests:
cargo test -p glsl-lang --lib --features lexer-v1
cargo test -p glsl-lang --lib --features lexer-v2-min

The whole lexer-v1/v2-min/v2-full is rather unwieldy but I had to keep the (working) V1 lexer while getting the V2 (with full preprocessor support) ready. The V1 lexer will likely get dropped in the feature to simplify all this.

Other than that, very good catch and thanks for the fix!

Once https://github.com/vtavernier/glsl-lang/pull/18 gets merged you can rebase your PRs on the master branch, it'll have a pinned Rust toolchain version and all the clippy issues fixed


[WIP] Make NumericUpDown nullable

What does the pull request do?
Allows binding to nullable values. A default value can be set if the user don't want to allow null values
What is the current behavior?
null is not allowed, instead the property will be set to 0 if the user clears the TextBox part
What is the updated/expected behavior with this PR?
null is allowed
How was the solution implemented (if it's not obvious)?

Made Value nullable (decimal?)
Added a new property DefaultValue

Checklist

[ ] Added unit tests (if possible)? ► ToDo
[ ] Added XML documentation to any related classes? ► ToDo
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation ► ToDo

Breaking changes
Not sure if this is a breaking change as the functionality is just extended
Obsoletions / Deprecations

Fixed issues
Fixes #7725

You can test this PR using the following package version. 0.10.999-cibuild0019272-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0019273-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0019936-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Hey @avaloniaui-team may I ask for a first Feedback? A :+1: or :-1: would be enough for now. Then I can pick it up next week.
Thank you in advance ❤
Happy coding
Tim

You can test this PR using the following package version. 0.10.999-cibuild0020267-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


luci-app-mwan3: incorrect warnings with ipv6 wan interfaces

If you configure interface arises like wan6 and wanb6 per the standard convention (so we can run both udhcpc and odhcpc), we get warnings about duplicate interfaces and metrics.
@feckert

@feckert

config interface 'wan_cc'
        option ifname 'eth0.10'
        option proto 'dhcp'
        option metric '120'

config interface 'wan_cc6'
        option ifname '@wan_cc'
        option proto 'dhcpv6'
        option reqaddress 'try'
        option metric '120'
        option reqprefix '60'

config interface 'wan_mb'
        option ifname 'eth0.11'
        option proto 'dhcp'
        option metric '110'

config interface 'wan_mb6'
        option ifname '@wan_mb'
        option proto 'dhcpv6'
        option reqaddress 'try'
        option metric '110'
        option reqprefix 'auto'

@pleasantone
Yes i have not known that the ifname could also be related with the @ option. In the source i am iterating over the interfaces and if i found an equal metric luci-app-mwan3 shows the warning.
I have no hotfix for this now. I have to think about how to solve this problem.

Duplicate https://github.com/openwrt/luci/issues/4603


Midnight Commander Editor syntax highlighting appears to be broken

Describe the bug
A few months before today, mcedit's (pulled from nixpkgs-unstable) syntax highlighing just worked, but at least at nixpkgs commit b9982bcba7b0a54e004f73ece06743768c1781cd, syntax highlighing doesn't appear to work at all. Unluckily I don't have a system profile available anymore where it works...
Steps To Reproduce
Unknown.
Expected behavior
Syntax highlighting should work.
Screenshots

If applicable, add screenshots to help explain your problem.
Additional context
config repo: https://github.com/zseri/nixos-configs
Notify maintainers
@trofi @svanderburg
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.4, NixOS, 22.05 (Quokka)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.5pre20211202_3f3561f`
 - nixpkgs: `/etc/nix-flake-channels/nixpkgs`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
  - mc
# a list of nixos modules affected by the problem
module:

Syntax highlighting works for me on mc-4.8.27. When in editor if you click F9->Options->Syntax file does it show you the syntax file with rules and includes? That's where the list is supposed to come from.
It should be a ~/.config/mc/mcedit/Syntax. Make sure it's not empty by accident. It should be safe to move it away it if you want to check a default behaviour.

ok, nvm, I now ran rm -rf ~/.config/mc ~/.cache/mc ~/.local/share/mc and it works again. dunno how that could happen...

One of the scary and unlikely scenarios would be a machine crash right after that file was created for the first time (it's a frequent ext4 behaviour). More probable version is a bad migration from previous versions (I never encountered it myself) or explicit syntax file edit in the past that became incompatible.


Transaction-level vs Activity-level data

USAID have raised a challenge with the DS which was flagged to them, by an external stakeholder in the IATI community:
Where an organisation publishes data at transaction/activity level (where the Standard allows either), if the DS user uses the corresponding filter but does not use the same per-row option as the level that the data is held, data will not be returned.
For example, USAID designate recipient-country at the transaction level. Let's say a user wants to return all activities that USAID are reporting in Kenya. The following filters would probably be used:
Reporting-org = USAID
Recipient-country = Kenya
Row format = 1 activity per row
As USAID do not designate recipient-country at activity level, no data would be returned! Anyone who did not know the structure of IATI, or know USAID's data, would likely assume that USAID have not worked on any projects in Kenya, which is obviously incorrect.
Of course, the same goes for the majority of publishers, who designate recipient-country at activity level, if a user wanted to return one transaction per row.
Question: How can we deal with this? Is it sufficient to add this to the User Guide and text on the Query Builder front-end, or can a technical solution be implemented to mitigate the challenge that non-IATI experts may face? All suggestions welcome!

I'm keen for this issue to be worked on as a priority post launch.
The old datastore's QB allows you to add a country or sector filter and return all relevant transactions. I don't think it does anything clever, rather it selects the required activities (only looking at activity level reporting) and returns the transactions for those selected activities.
We'd need to go beyond this and include transaction level reporting (which I don't think the old datastore QB does at all)
The non-techy user can then do a v-lookup between the activity and transaction level output to combine the data as they need.

@amy-silcock an update in the UI could help, re-opening.

@stephanoshadjipetrou please check

Aligned filtering logic for:

Aligned filtering logic for:

recipient country: (recipient_country_code:<country_codes> OR transaction_recipient_country_code:<country_codes>)
recipient region: (recipient_region_code:<region_codes> OR transaction_recipient_region_code:<region_codes>)
sector: (sector_code:<sector_codes> OR transaction_sector_code:<sector_codes>)

Can be tested on https://test-datastore.iatistandard.org

[My simple test worked well](https://iatidatastore.iatistandard.org/search/activity?q=reporting_org_ref:(US-GOV-1) AND (recipient_country_code:(SO) OR transaction_recipient_country_code:(SO))&wt=json&rows=50) - thanks for this!

Pushed to production


Avoid retention of ChatMessageCollectionAdapter while updating models on background thread

Codecov Report

Merging #730 (9fe9090) into master (dabade2) will increase coverage by 11.93%.
The diff coverage is 91.89%.

@@             Coverage Diff             @@
##           master     #730       +/-   ##
===========================================
+ Coverage   57.33%   69.27%   +11.93%
===========================================
  Files         102       20       -82
  Lines        5635     1536     -4099
===========================================
- Hits         3231     1064     -2167
+ Misses       2404      472     -1932

Impacted Files
Coverage Δ

...er/ChatMessages/ChatMessageCollectionAdapter.swift
83.29% <91.89%> (+0.24%)
:arrow_up:

...toAdditions/sources/Common/UIImage+Additions.swift

...ssage/Content/DefaultMessageContentPresenter.swift

.../Input/Photos/Camera/LiveCameraCellPresenter.swift

...ttoAdditions/sources/Common/Comparable+Clamp.swift

.../Chat Items/BaseMessage/BaseMessagePresenter.swift

...hattoAdditions/sources/Input/ReusableXibView.swift

...dMessage/Content/MessageManualLayoutProvider.swift

...ompoundMessage/Views/CompoundBubbleViewStyle.swift

...Photos/Camera/LiveCameraCellPresenterFactory.swift

... and 73 more

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 dabade2...9fe9090. Read the comment docs.


[Jest] crash on Jest 25

Summary
I tried upgrading my own package to use Jest 25 in https://github.com/brodybits/create-react-native-module/pull/240, now the Jest runner crashes. Quick fix workaround for Jest 25 is to use default command runner, with testing time more than doubled for me.
I think this issue is caused by the way Jest 25 changed how it exports its CLI function.
I would personally favor that we make a new major release of the Stryker Jest runner that works with Jest 25 and drop support for any older versions of Jest that would not be compatible.
Here is my output if I try with latest update of Stryker, with HTML reporter removed:
% npx stryker run
12:14:18 (92133) INFO ConfigReader Using stryker.conf.js in the current working directory.
12:14:18 (92133) INFO InputFileResolver Found 10 of 104 file(s) to be mutated.
12:14:18 (92133) INFO InitialTestExecutor Starting initial test run. This may take a while.
12:14:22 (92133) ERROR InitialTestExecutor One or more tests resulted in an error:
	Test runner crashed. Tried twice to restart it without any luck. Last time the error message was: Error: TypeError: Cannot read property 'runCLI' of undefined
TypeError: Cannot read property 'runCLI' of undefined
    at JestPromiseTestAdapter.run (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/jest-runner/src/jestTestAdapters/JestPromiseTestAdapter.js:17:31)
    at JestTestRunner.run (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/jest-runner/src/JestTestRunner.js:43:56)
    at ChildProcessTestRunnerWorker.run (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/test-runner/ChildProcessTestRunnerWorker.js:24:56)
    at ChildProcessProxyWorker.doCall (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/child-proxy/ChildProcessProxyWorker.js:75:56)
    at Promise.then.send.correlationId (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/child-proxy/ChildProcessProxyWorker.js:46:53)
    at new Promise (<anonymous>)
    at ChildProcessProxyWorker.handleMessage (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/child-proxy/ChildProcessProxyWorker.js:46:17)
    at process.emit (events.js:223:5)
    at emit (internal/child_process.js:876:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
Error: TypeError: Cannot read property 'runCLI' of undefined
TypeError: Cannot read property 'runCLI' of undefined
    at JestPromiseTestAdapter.run (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/jest-runner/src/jestTestAdapters/JestPromiseTestAdapter.js:17:31)
    at JestTestRunner.run (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/jest-runner/src/JestTestRunner.js:43:56)
    at ChildProcessTestRunnerWorker.run (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/test-runner/ChildProcessTestRunnerWorker.js:24:56)
    at ChildProcessProxyWorker.doCall (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/child-proxy/ChildProcessProxyWorker.js:75:56)
    at Promise.then.send.correlationId (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/child-proxy/ChildProcessProxyWorker.js:46:53)
    at new Promise (<anonymous>)
    at ChildProcessProxyWorker.handleMessage (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/child-proxy/ChildProcessProxyWorker.js:46:17)
    at process.emit (events.js:223:5)
    at emit (internal/child_process.js:876:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
    at ChildProcess.<anonymous> (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/child-proxy/ChildProcessProxy.js:133:68)
    at ChildProcess.emit (events.js:223:5)
    at emit (internal/child_process.js:876:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
12:14:22 (92133) ERROR StrykerCli an error occurred Error: Something went wrong in the initial test run
    at InitialTestExecutor.validateResult (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/process/InitialTestExecutor.js:86:15)
    at InitialTestExecutor.run (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/process/InitialTestExecutor.js:41:14)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at async Stryker.runMutationTest (/Users/brodybits/dev/create-react-native-module/node_modules/@stryker-mutator/core/src/Stryker.js:54:38)
12:14:22 (92133) INFO StrykerCli Trouble figuring out what went wrong? Try `npx stryker run --fileLogLevel trace --logLevel debug` to get some more info.

Stryker config

With HTML reporter removed:
module.exports = config => {
  config.set({
    mutator: 'javascript',
    mutate: ['lib/**/*.js', 'templates/**/*.js'],
    packageManager: 'yarn',
    reporters: ['clear-text', 'progress'],
    testRunner: 'jest',
    transpilers: [],
    coverageAnalysis: 'off'
  });
};

Test runner config
none
Stryker environment

├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped

partial:
─┬<EMAIL_ADDRESS>[...]
├─┬<EMAIL_ADDRESS>[...]
│ ├─┬<EMAIL_ADDRESS>[...]
 └─┬<EMAIL_ADDRESS>[...]

Test runner environment

from package.json:
    "test": "npm run lint && npm run jest"

Your Environment

software
version(s)

node
v12.15.0

npm
6.13.7

Operating System
macOS version 10.15.2 (19C57)

Add stryker.log
stryker.log

Thanks for opening this issue! It seems like you have the same issue as #1983 so I'm closing this one for now.

Hi! Jest 25 support has been released with @stryker-mutator version 3! You can read all about it here: https://stryker-mutator.io/blog/2020-03-11/stryker-version-3


Load woff, woff2 font-face

I'm using this config:
WebFontConfig = {
      google: { families: [ 'Ubuntu:400:latin,cyrillic' ] }
    };

Which loads this css:
@font-face {
  font-family: 'Ubuntu';
  font-style: normal;
  font-weight: 400;
  src: local('Ubuntu'), url(http://fonts.gstatic.com/s/ubuntu/v8/Rbrel7WusHF7uMf4pVxmeOvvDin1pK8aKteLpeZ5c0A.ttf) format('truetype');
}

I want only woff and woff2 for speed loading for modern browsers, but WebFont gives only link to ttf font. How to config it to load woff, woff2?

The CSS is generated by Google Fonts, and not the Web Font Loader. Most likely they're serving TTF because they detected your browser as capable of only supporting TTF. If this is incorrect, please raise an issue in the Google Fonts forum.


Placeholder for deciding overall CI/CD approach

We have already implemented some CI/CD - see https://github.com/snowplow/snowplow/issues/2621 This ticket is about defining the overall approach across the whole repo.
Options:

Tag-driven build - Component-version tags drive releases, and also version numbers of components (i.e. e.g. BuildSettings.scala is dynamically populated with version number)
Double-entry build - Component-version tags drive releases, and the versions they dictate are validated against the versions in BuildSettings.scala etc
Semi-smart build - Component tags drive releases, but the versions are pulled from BuildSettings.scala
Smart build - Generic tags drive releases, but the component-versions to include are detected automatically by a smart build script

Currently the Kinesis CI/CD is a hybrid of approaches 1 and 2 - the Kinesis zipfile is driven from the tag; the constituent app versions are driven from the BuildSettings.scala files.

R81 is going to update:

Scala Common Enrich
Stream Enrich
Hadoop Event Recovery

Proposal:

We define a set of aliases for each unit of deployment (e.g. Scala Common Enrich, Stream Enrich, Hadoop Event Recovery)
We come up with a syntax to support Double-entry build with multiple components, like:

sce-0.24.0;se-0.9.0;her-0.2.0

where:

Components are published sequentially in left-to-right order
Component versions are validated against BuildSettings.scala etc

A big advantage of tag-driven builds: you can be selective about what you build. A given subproject may be changed in the development branch, but that doesn't necessarily mean that you want to spend time building and deploying it with every commit in that branch.

Proposal:
We have a self describing json in the root that tells the build what to run and what to release. This would change over time and would be updated manually by the person editing a specific component.
This would allow the person to select different items freehand and allow some complexity while enforcing a standard format.

What about the JSON-based approach, but then allow the tag to whitelist or blacklist specific components, so e.g.
+sce;+her

will only push SCE and HER.
or
-sce

will push all but SCE.

@BenFradet @chuwy - it feels like we have consensus on how CI/CD works/should work for this repo. Can I close?

Fine by me.


RFC Generate a prettyprinter for structs

This is a little off-the-walll, but in the Ruby thrift lib, enum values get printed out as their name, which can be pretty nice for debugging purposes.  We could theoretically generate a defimpl Inspect for structs and have it do this.  For the most part I think this would just hijack the normal struct implementation but it could replace the enum entries with something like user_status: 1 (UserStatus.active).
OTOH it could be not worth the complexity.  Something opt-in might be a compromise?  I.e., the generated module could include a prettyprint function or something and then we provide docs showing how you could roll your own defimpl around that.

I like this idea and spent a little time looking into a possible implementation. It unfortunately doesn't appear to be an easy thing to build, however. Because structs are just maps, the only want to determine which fields contain enums is based on matching against their names, and hooking into the Inspect protocol at that level appears to involve re-implementing the full struct/map Inspect.inspect/2 code path.
I think that could be done somewhat generically and reused for each of our generated structs, but it's still a good amount of complexity.
I think that work is roughly equivalent to rolling our own pretty printing function, so I'm not sure there's a benefit to not using Inspect here, unless the algebraic nature of Inspect gets in our way.


Datalog restrictions in blocks

Currently, blocks can be added to any non-sealed biscuit. A block can contain both caveats (like in macaroons), but also facts and rules. This requires careful thought from both the biscuit minter and the biscuit verifier: the goal is to avoid confusing facts from the biscuit minter and facts from blocks.
To that end, the special #authority atom is used.
It's special in two ways:

it's forbidden in blocks rules and facts
it's automatically added in authority facts (and rules? not sure)

All that makes the semantics rather complex (and way more complex than, say, macaroons). Another possibility would be to completely forbid rules and facts in blocks, and only allow caveats. This would bring the attenuation semantics closer to those of macaroons, which are arguably easier to reason about.
I still see the value in more complexity in blocks, but I think it should be optional (ideally, opt-in). In that case, i think the biscuit should carry this information when minted. This would avoid validating an restricted biscuit with a verifier that expects an unrestricted one.
All in all, while datalog brings huge improvements over macaroons (putting aside asymmetric crypto), the ability to add rules and facts in blocks make the complexity explode and make auditing biscuits properties way harder.
As an additional bonus, not allowing rules in biscuits completely remove an attack channel where a legitimate biscuit is attenuated with rules crafted to exploit the datalog engine.

as mentioned in #59, the authority block could be a special case for deserialization, containing configuration data that other blocks cannot hold, such as this option

If the version at https://play-with-biscuit.cleverapps.io/ is up-to-date, the #authority and #ambient restrictions can easily be bypassed by any party able to create a new block.
This in turn allows to bypass any checks already present on the previous blocks or in the authority section. Conversely, with knowledge of the verifier code, one could craft a block that always grants passage.

@svvac could you explain how it is easily bypassed? Wth the playground, you cannot create a token with authority or ambient facts in blocks other than block 0.
Sure, it is possible to manually create a token with the authority or ambient tag by tweaking the library, but verifier implementations are supposed to refuse them. There's even one of the samples that test for that: https://github.com/CleverCloud/biscuit/tree/master/samples/v1#invalid-block-fact-with-authority-tag-test7_invalid_block_fact_authoritybc
Though if you have specific concerns or vulnerabilities to demonstrate, I'm always interested, I'll make sure to fix them quickly

@Geal Given the Files example, without touching the authority and first block, adding the following block results in Success for all values of resource(#ambient, *) and operation(#ambient, *) in the verifier:
// Bypass `check if operation(#ambient, #read)` from authority block
operation($ambient, #read) <- operation($ambient, $any);

// Bypass `check if resource(#ambient, $file), $file.starts_with("/folder1/")` from block #1
resource($ambient, "/folder1/") <- resource($ambient, $any);

// Add missing rights
right($authority, $file, $right) <- right($authority, $any1, $any2), resource(#ambient, $file), operation(#ambient, $right);

Also different issue (I think), but with the same effect : there seems to be a bug where leftover variables in the rule pattern matches the #authority symbol:
// Bypass `check if operation(#ambient, #read)` from authority block
operation($unbound, #read) <- operation($any1, $any2);

// Bypass `check if resource(#ambient, $file), $file.starts_with("/folder1/")` from block #1
resource($unbound, "/folder1/") <- resource($any1, $any2);

// Add missing rights
right($unbound, $file, #read) <- resource($any1, $file);

Nice catch, thanks, I'll fix that and add a new sample to verify that behaviour

@svvac the bugs were identified and fixed in the Rust and Java implementation, soon in the Go one, and I have prepared test samples to test that for future implementations. The fixes should be pushed soon. I'll announce the vulnerabilities and make a changelog. Do you want to be credited in the announcement?

@Geal I don't mind, thanks for asking. Glad to hear it got fixed fast.

Special atoms are no longer needed to scope facts.


Typo

In the section entitled "Complete The Migration", step 1 tells you to click 'Stop Migration'. This should actually read 'Stop Replication'.
[Enter feedback here]

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

ID: 0f6cf488-07d3-1b2b-69f2-f04c7890bd55
Version Independent ID: fd658be4-17c5-19c7-b6c9-630090880c3c
Content: Migrate Hyper-V VMs to Azure with Azure Migrate Server Migration - Azure Migrate
Content Source: articles/migrate/tutorial-migrate-hyper-v.md
Service: azure-migrate
GitHub Login: @bsiva
Microsoft Alias: bsiva

@ianc911 Thanks again for bringing this to our notice and helping us improve our Azure documentation. I did raise a PR to update the document . Once the PR is reviewed and approved , changes would go live.
At this point it appears that there's no further edits or updates needed to the documentation, other than what has been listed above. We will go ahead and close this issue for now, however if you have any further feedback on the document please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you


Adds an interop test: oauth2_auth_token

test is similar to the existing auth tests: only on the cloud-to-prod path
uses an auth library to obtain the auth token OOB. This should be simplest, as many languages already use such an auth library in their existing auth tests.

@hsaliak: this is the draft I talked about yesterday.


How to add webpack.config.js for Vue plugin?

Description
I am trying to integrate Vuetify in my vue app. So i have to follow the webpack integration to make it work from the documention.
https://vuetifyjs.com/en/getting-started/quick-start/#webpack-install
i want to put some default webpack config in wwebpack.config.js file. So how can i add it?

I was able to integrate vuetify without having to manipulate the webpack config. Check out this repo demoing vuetify. I followed the documentation for installing vuetify in a vue-cli powered project and copied the changes over.

Thank you so much it worked perfectly. I just have few things i observed.

For some reasons, my onsave lint in vscode is not working at all. It is working for other apps. But not for vue.
The test files does not detect jest env in vscode but it is working on other apps too.
It seems like the environment.ts is not avaiable. When i try to create one manually and add "fileReplacements" key in workspace. It is giving me a error saying that i cant use that key. Is there a plan to support it?

Thanks.

Glad I could help!

I'm not too familiar with eslint onsave, but I downloaded the eslint extension, added "editor.codeActionsOnSave": { "source.fixAll.eslint": true } and it was working correctly. This was done with a fresh nx workspace mind you.
Could you create an issue regarding this with some more details? I can take a look but I'd need some more information.
We considered supporting fileReplacements but opted to stick with supporting what the vue-cli supports when it comes to environment variables.


mv30 encoder

hello please could you make a version which includes mv30 encoder? thank you

I don't see any support for mv30 encoding in FFmpeg? Or am I missing something?
This is not a tracker for issues and feature requests for FFmpeg.

oh I thought it was, is there any other way to encode mv30 then?
thanks


feat(bedrock): agent action groups

Fixes #169
Depends on #231 and #232
Adds an AgentActionGroup custom resource and construct.
Usage example:
  const agent = new bedrock.Agent(this, 'Agent', {
    foundationModel: bedrock.BedrockFoundationModel.ANTHROPIC_CLAUDE_INSTANT_V1_2,
    instruction: 'You are a helpful and friendly agent that answers questions about literature.',
    knowledgeBases: [kb],
  });

  const actionGroupFunction = new lambda_python.PythonFunction(this, 'ActionGroupFunction', {
    runtime: lambda.Runtime.PYTHON_3_12,
    entry: path.join(__dirname, '../lambda/action-group'),
    layers: [lambda.LayerVersion.fromLayerVersionArn(this, 'PowerToolsLayer', `arn:aws:lambda:${this.region}:017000801446:layer:AWSLambdaPowertoolsPythonV2:60`)],
  });

agent.addActionGroup({
  actionGroupName: 'query-library',
  description: 'Use these functions to get information about the books in the library.',
  actionGroupExecutor: actionGroupFunction,
  actionGroupState: "ENABLED",
  apiSchema: bedrock.ApiSchema.fromAsset(path.join(__dirname, 'action-group.yaml')),
});

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

Looks good to me. I would like to have  an ApiSchema construct , similar to the Code construct, with methods from_file() and from_inline(), instead of using fs.ReadFileSync() directly.
Expose also a method addActionGroup on the Agent construct.
Example on user experience:
const agent = new Agent(this, "weather-agent", {
      instruction:
        "You are a weather expert and answer user question about weather in different places. You answer the questions in the same language they have been asked.",
      description: "an agent to interact with a weather api",
    });

    agent.addActionGroup({
      lambda: weather,
      apiSchema: {
        payload: ApiSchema.fromPath(
          path.join(__dirname, "weather", "schema.json")
        ),
      },
      actionGroupState: "ENABLED",
    });

Here are some suggestion for UX improvements:
1. Add  an `ApiSchema` construct , similar to the `Code` construct, with methods `fromPath()` and `fromInline()`, instead of using `fs.ReadFileSync()` directly. This would also hide the language specific implementations for reading files.

2. Expose a method `addActionGroup()` on the `Agent` construct.

Thank you @massi-ang ! I like these ideas! I'll implement them.

Here are some suggestion for UX improvements:
1. Add  an `ApiSchema` construct , similar to the `Code` construct, with methods `fromPath()` and `fromInline()`, instead of using `fs.ReadFileSync()` directly. This would also hide the language specific implementations for reading files.

2. Expose a method `addActionGroup()` on the `Agent` construct.

@massi-ang fromPath() is fromAsset() to be consistent with Code.

The sample app in https://github.com/jstrunk/generative-ai-cdk-constructs-samples/tree/bedrock-agent-action-groups has been updated with a function that queries the most popular books in the library.


Add moderator notes to topic detail

Part of #3447
It adds the moderation notes to the topic detail view and tries to fix the styling.
It works in a context where mat-legacy-card and mat-card is used.

Waiting for #3487

In the moderation notes I notice a delay after pressing save and changing to the readonly view. It also happens in the main branch.

Could you please still update your PR to current main?

Updated to current main.


how to load tessdata from binary data stream

version： 4
linux Windows or Android

hey, i want load tessdata for vector or bytes,like binary data stream,from network or dynamic library.
what should i do?

You should start with respecting guidelines for posting issue: use tesseract user forum for asking questions/support.


Morgan documentation question

So, this is more of a question than an issues, but i don't know where else to post this, so here we go.
I'm using morgan on a nodejs project and I realized the Intellisense from VScode is showing me some attributes that were not on the index.js file.
After searching for them I realized they were on the README file.
Example: when calling morgan as a function 'morgan()', it shows 7 possibilities of formats.
So my question is: how is that done? What is it called? I found that so cool but I have no clue where starting searching.
Thanks in advance!

I'm not sure what you mean.

Okay, i'll add a link to an image to better exemplify it.
But that's basically it. I have doubts on how I'm able to see this documentation, which I first assumed would only be visible if that was on the file itself as a JSdoc.
So, after looking into the files, i suppose this come from the README file.

It's no problem! There really isn't anything here other than what you see in the GitHub repo, and I don't do anything special. It's possible that there is some kind of README scraping going on with that program, not sure.

I totally forgot about pasting the image link, sorry. Here is it:
https://ibb.co/i9MY6K
I tried making a test package copying morgan's structure but had no success with it. I get the default JSdoc (as expected) instead of the readme.
I'm clueless on this one haha

Okay, after a lot of rumbling around:
I tried to change what was written in the README and that didn't change what the Intellisense was showing.
So I started looking once again and I found at 'USER\AppData\Local\Microsoft\TypeScript\2.9\node_modules@types\morgan" a file index.d.ts which contained the same descriptions that were in the README. When changing it, the description intellisense gave changed!
So, what's that file? Apparently it's a file on (this repo)[https://github.com/DefinitelyTyped/DefinitelyTyped] used to document Typescript projects but seems like it can be used for JS projects too. Now, when it's that downloaded (I suppose NPM does it), why VScode uses it instead of the JSdoc is still a question to me.
Did you know about that or is it news for you? There is a readme there too which contains the github of the users that created this (@type/morgan)[https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/morgan] and it seems to me they didn't have anything to do with morgan's development.
I'll close this as I found the source, but I'd like to hear anything you have to say :)

It's news to me.


How to disable this tooltip in vscode

When long press cmd + s, this tooltip will show, this only happens in vscode(I tried in sublime and other editors, never happen this). Is that a feature?, And how to disable this tooltip in vscode?

VSCode Version: 1.34.0
OS Version: macOS 10.14.3

Steps to Reproduce:

Long press cmd + s

Does this issue occur when all extensions are disabled?: Yes/No
I did'nt disable all extensions as far now.

It's mac's feature, to disable it:
defaults write -g ApplePressAndHoldEnabled -bool false

Then restart vscode.


[Feature Request]: Configure file validation

Is there an existing issue for the same feature request?

[X] I have checked the existing issues.

Is your feature request related to a problem?
No response
Describe the feature you'd like
Now, infinity strictly requires that the version field of the config file needs to match the infinity version. The goal of this feature request is to remove version restrict matching requirement, but rather to indicate which parameters in the config file are unrecognized, outdated,  wrong type, or wrong value.
Describe implementation you've considered
No response
Documentation, adoption, use case
No response
Additional information
No response

Fixed by #1203


if you do Default before you do Alias, scons doesn't recognise it

This issue was originally created at: 2012-05-11 08:58:56.
This issue was reported by: thosrtanner.
thosrtanner said at 2012-05-11 08:58:56

For instance:

env = Environment()
o = env.Program('Hello.cc')
env.Default('all')
env.Alias('all', o)

then
> scons -Q
scons: *** Do not know how to make File target `all'
(/bbcm/ticker_plant/source/all).  Stop.

Swap the Default and Alias lines round, it works fine

How about a simple addition to the doc as a resolution?  Something like

Default will also accept a previously defined Alias as a target name.

Perhaps extend with something like

Any Alias defined after the Default statement will not be recognized, unlike a file or directory which will.

Added example file to: https://github.com/bdbaddog/scons-bugswork/tree/main/2839

Potentially related to #2581


Minor Dependency Updates

Description
Update all packages to their safest minor versions
https://docs.npmjs.com/cli/v8/commands/npm-update

I would expect that the main package.json contains the updated versions for each package too?
Which command did you run? Not npm update --save correct? https://docs.npmjs.com/cli/v8/commands/npm-update

You're right.. I was missing the save flag but ended up using ncu -u --workspaces --target minor this time around.
Should be updated now.


package command fails when using yarn workspaces with native dependency

Pre-flight checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project uses.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
7.5.0
Electron version
v32.1.2
Operating system
MacOS 14.7
Last known working Electron Forge version
No response
Expected behavior
Electron-forge should dereference symlinks (or provide an option to) when copying the package.
Actual behavior
It does not dereference the symlinked dependencies leading to error:
✔ Copying files

An unhandled rejection has occurred inside Forge:
Error: ENOENT: no such file or directory, stat '/private/var/folders/bb/j1658g0d50gfcvgq3cm6cj1c0000gn/T/electron-packager/tmp-usVZSn/Electron.app/Contents/Resources/app/node_modules/asr'

Steps to reproduce
I'm using yarn (4.5.0) workspaces and I have packages
- packages
  - application (electron app)
  - asr (a native dependency)

asr is a dependency of application.
When I run yarn package it fails with the following error:
✔ Copying files

An unhandled rejection has occurred inside Forge:
Error: ENOENT: no such file or directory, stat '/private/var/folders/bb/j1658g0d50gfcvgq3cm6cj1c0000gn/T/electron-packager/tmp-usVZSn/Electron.app/Contents/Resources/app/node_modules/asr'

I see the dir it is stat'ing is a symlink:
 ls -al /private/var/folders/bb/j1658g0d50gfcvgq3cm6cj1c0000gn/T/electron-packager/tmp-usVZSn/Electron.app/Contents/Resources/app/node_modules/asr
lrwxr-xr-x@ 1 matt  staff  9  9 Oct 00:19 /private/var/folders/bb/j1658g0d50gfcvgq3cm6cj1c0000gn/T/electron-packager/tmp-usVZSn/Electron.app/Contents/Resources/app/node_modules/asr -> ../../asr

A workaround is running:
rm -rf ./node_modules/asr && cp -L -r ../asr ./node_modules/asr

If I run this and then rerun yarn package. The application will build correctly.
Is there any way to make electron-force understand it should dereference this symlink when copying the package?

I see a similar issue at https://github.com/electron/forge/issues/3624 with a suggested fix to the vite plugin. Would you be happy to take a PR for this?
Additional information
No response

I managed to trace the issue and I believe it is indeed related to the vite plugin. If I add the following to my package.json:
"config": {
    "forge": {
      "packagerConfig": {
        "extraResource": [
          "./node_modules/asr"
        ],
        "derefSymlinks": true
      }
    }
  }

It works now as expected. I can even delete the entire forge.config.ts and it still works, so I guess this snippet replaces entirely the forge config, meaning no vite pugin is used.

Hey @mtharrison, thanks so much for your work on this! If it's no trouble, we'd definitely accept a PR to make this experience better or outline it more clearly in the docs. If you don't have time to do that, we can take a look at doing this 🙇♀

Sure, happy to. I'll take a look soon 😄


Input Feature Question

Hello,
I'm wondering what the input feature dimensions of the ECG and PPG data? Also,  how is the input_length is used in class ConvolutionalEncoder(nn.Module):?

The input dimensions are defined in the experiment config files here: https://github.com/webstah/self-supervised-bss-via-multi-encoder-ae/tree/main/config/experiment_config
The input length should be 12288 for the ECG and PPG experiments as described in our preprint. The input_length parameter was primarily used for earlier versions of the experiments that had a fully connected layer at the encoding space. This bit of vestigial code can be removed. If you run the model with our recommended configurations it has no effect but may be important in the decoder depending on the layer normalization method used.
I see that the ECG experiment config has the wrong input length set. While this has no impact on the experiment configuration we used, I will update this for clarity's sake.

Thanks, also following up in https://github.com/webstah/self-supervised-bss-via-multi-encoder-ae/blob/main/config/experiment_config/mesa_ecg_bss.yaml , I see there are 7 channels and num_encoders = 8, but in https://github.com/webstah/self-supervised-bss-via-multi-encoder-ae/blob/main/config/experiment_config/mesa_ppg_bss.yaml, there are 8 channels and 8 encoders, is there a reason for this difference or a typo?

Good catch, there is a typo or I accidentally deleted something when copying this file over from my private development repository. I have fixed it now.
Also the channels parameter defines the output channel dimension for each layer for all encoders. The number of layers in each encoder will match the length of this list, but the number of layers does not have to match the number of encoders as we can see with the toy dataset experiments.
Hope that helps! I appreciate your feedback.

One last note: page 10 of our preprint has a good visual overview of the model architecture specifications which should help with understanding the code and configurations we used.

Thanks Matthew, following up,  I was wondering how a ~12000 sized input feature is collapsed into a 64 sized vector? Asking this question because the first encoder has incoming channel size = 64. Shouldn't it be 12000? Why is input length is not used in the encoder section? Maybe I am misunderstood something, so clarity is appreciated

Also, the way we reduce the length dimension is with a max pooling layer for each convolutional block in the encoder. Each block divides the length by two according to our configuration for the max pooling layers.

Hi Matthew, thank you for your reply.  Mainly my questions relate to trying this method with hypothetically other types of mixed signals, I wanted to clarify inputs and outputs. From what I understand the inputs depend on the yaml file and data loader. I'm not sure where you would get the output for the encoder if you do not want images. There is some missing comments for this in the code.

For typical autoencoder architectures, the output dimensions will match the input dimensions and our work is no exception in this regard. We have two fully convolutional architectures available for the BSS task which are capable of taking inputs of variable size (the benefit of using a fully convolutional architecture), so you will not have to explicitly define the input and output dimensions, but you will need to be careful about their shape. Recall from the paper that we use a max pooling layer for each convolutional block with a kernel size of 2 and a stride of 2, effectively dividing the length (or height and width for images) by 2 for each block. This means your input/output features should be divisible by 2 to the power of the number of convolutional blocks in the encoder which is the same amount of blocks in the decoder where we reverse the max pooling with upsampling by a factor of two.


Large memory leak with game.debug.text in 2.4.4

I've verified this doesn't happen in 2.4.3. Very simple test case (excluded boilerplate HTML, if you need that let me know):
var game = new Phaser.Game(1400, 800, Phaser.AUTO, 'Hi', {create: create, render: render });
function create() {
    game.stage.backgroundColor = '#313131';
}
function render() {
    game.debug.text('Hello!', 5, 20);
}

If you watch the browser process, the memory usage in Chrome jumps around by 100's of megabytes (going from 200 -> 600 MB). In FF, it jumps around 100 MB.
Edit:
With 2.4.3 (OK): http://jsfiddle.net/bfgm8ed0/
With 2.4.4 (leak): http://jsfiddle.net/bfgm8ed0/1/

Holy crap, can confirm here.

I noticed the same the other day playing around with the rope, so it may not be just to do with game.debug.text
In my case it was to do with being in WebGL mode, and the heap being full of WebGL contexts.  Wasn't sure if it was my rope mods that were breaking it, but as I didn't need it fixed straight away I left it for a rainy day to look at again.
You could fix it to canvas mode and see iff the problem using Phaser2.4.4 goes away.  If it does go away then I would suspect a general WebGL mode problem.

Interesting. The problem is this line here: https://github.com/photonstorm/phaser/blob/master/src/gameobjects/BitmapData.js#L584
The change that caused this is that BitmapData.clear now calls BitmapData.update, which has the above line in it.
It only happens in WebGL of course, but still, very frustrating. I cannot see a way to fix it either. Even just calling context.getImageData is enough to trigger it. So I'll stop BitmapData.clear from calling update and reflect this in the docs.

Yup, that's fixed it.

Well not really, all it did is revert the earlier change, which was a quite important one. But it will have to do for now.

Dang, you are fast! :beers:


Just a question. what is the theme in readme?

could you tell me theme below in readme, if possible?

That's Agnoster.
fisher install omf/theme-agnoster

Let me know if that works for you.

Thank you for letting me know! I installed the theme but it seems to be different from the colors above. Did you customize it a little bit? I am sorry for raising the unrelated comment to the library itself here.

Good. Now, you need to set the colors you like in your terminal application.
I am using iTerm2 on OSX, so I press cmd+, which brings up the settings panel and I find my way from there. I am pretty sure whatever it is you are using there is something similar.

Cool! I downloaded the preset theme of Brogrammer from https://github.com/mbadolato/iTerm2-Color-Schemes and it is almost the same colors as yours.
Thanks a lot!

I'm glad we like the same colors :smile:


remove pull secret from int/prod

apply this after the az changes and documentation have been rolled out

closing for #328


Request: Investigate utilisation of versioned toolchains for improved hermeticity

In Bazel it's possible to force a specific compiler version with a custom toolchain that includes the download as part of the build process. For example, https://github.com/grailbio/bazel-toolchain.
I wonder if it's feasible to utilise something like this for this project, instead of requiring the host to have a specific clang version installed. Benefits could include more user friendly installation, seemless updating, and a tighter coupling between each commit and the required compiler version (the object files might even be built with the same toolchain to guarantee a match).
Not sure on the downsides, so that's why I'm making this issue a request to investigate.

I wasn't aware of this option, but it is a great suggestion! :)

With the new Lyra v0.0.2 the specific clang version isn't necessary anymore.


Error in documentation, code for Simple example

For some years I have a Magic Mirror and now I moved from FHEM to Home Assistant.
So I needed a way to get the data from Home Assistant instead of FHEM.
I found your module and I like it.
Unfortunately, I started trying the code of your simple example.
It didn't work at once and it took me some time to find out, there are two small errors in the example code:

after token: "..." a comma is missing
at the end of displayTemplate:  the closing backtick is missing.

Maybe this helps some other newbies like me

Fixed, thanks


Network Connectivity points

This article needs to provide more detail about how points are earned for the Network connectivity score.  There is not a clear explanation about what specific steps can be taken to improve it.

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

ID: 411cc9ec-3de2-9aaf-00b8-d923d2b02f37
Version Independent ID: c1a0daec-33a1-eb34-db3d-0b12b78a8aaf
Content: Microsoft Productivity score - Microsoft 365 admin
Content Source: microsoft-365/admin/productivity/productivity-score.md
Service: o365-administration
GitHub Login: @Sirkkuw
Microsoft Alias: sirkkuw

@lkuhn65 Thank you for your feedback. Microsoft productivity score is still in preview mode and Please share your thoughts about Productivity Score and your ideas about how to improve it. Use the Feedback sections within the product and/or reach out to the Productivity Score team at<EMAIL_ADDRESS>@yogkumgit We can close this as the document is still under preview mode and the feedback can be shared directly with the productivity score team at<EMAIL_ADDRESS>

@msbemba  Thank you very much for the contribution and sharing this explanation. @lkuhn65 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


add a mode_service for changing interaction_mode

Currently there is no std_srvs for sending a string. How do you want to structure non-standard srvs in grl? Thoughts on how to handle message_generation/message_runtime in CMake Basis?

sorry could you give additional context? Where is the string being sent from/to?
CMake basis just assists with compilation, are you discussing the generation of ROS messages?
In that case it is good to be aware of existing work to see if you could make use of that, specifically the messages available in iiwa_stack and in majorana.
I'm okay with adding new dependencies, I'd just like to keep them optional if it is sensible.
For generating messages or adding new cmake functions or importing external ones, that will typically go in grl/config/Settings.cmake, as you can see the flatbuffer config is there at the moment. Though perhaps for ros specific items the grl/src/ros/CMakeLists.txt may be appropriate.

In addition to publishing std_msgs::String to switch the interaction mode, I would like to have a service which has a request field of String. Since "ArmState" is a custom enum, not sure any of the "iiwa_stack" or "majorana" srvs are usable.

I see, alternately for the enum perhaps requesting an integer which is convertible to the enum would be sensible? Up to you.


pdf_parser: skip pdf2html outputs > 64MB

Description
Some PDF files have caused our airflow worker to OOM. Remediate this
by skipping these files (which, on inspection of one at least, didn't
contain any useable data):

Skip PDF files where pdf2html output is > 64MB
Update parse_pdf_document() so it returns parse errors
Include PDF parse errors in JSON output, so we can track how many
parses fail and of what kind
Use LXML instead of BeautifulSoup for parsing HTML (faster, may be
more memory efficient)

Issue: https://github.com/wellcometrust/policytool/issues/227
Type of change
Please delete options that are not relevant.

[x] :bug: Bug fix (Add Fix #(issue) to your PR)

How Has This Been Tested?
./docker_exec.sh airflow test policy ParsePdf.who_iris 2019-09-01

using a docker-compose.yml that pointed to s3://datalabs-staging/, and where the manifest was updated to only include files with hash prefix of 69.
make docker-test
Checklist:

[x] My code follows the style guidelines of this project (pep8 AND pyflakes)
[x] I have commented my code, particularly in hard-to-understand areas
[x] New and existing unit tests pass locally with my changes
[x] If my PR aims to fix an issue, I referenced it using #(issue)

(The LXML change actually breaks the unit tests...so what we have there isn't exactly the same. Defer that part for later)


Update to superset 4.0.0

Bug: T364022

Merging because this seems to be already deployed :)

This one wasn't done. There's more discussion in the ticket about the encountered error https://phabricator.wikimedia.org/T364022


Overlord - Iteration 2

• Edited according to suggestions/input.
• How deep/wide typically does one go when utilizing/testing with/for pO models?  Being that it is another level of abstraction is there also a point (in bigger applications, I suspect) where it creates efficiency in testing if/when code gets changed?  (Can discuss this more in person.)
• Aside from utilizing only "if's" is there a more elegant way to test for a double conditional?  I recognize I could have simply edited the instructions but thought it might be a good exercise for me in testing the sad path(s) for at least one scenario (though as a user I might like to have every double scenario covered as well despite that those were already tested, or more likely just have it all in the instructions upfront to begin with, unless it was my deliberate intent as a developer to have it otherwise).

Nice work! The code is clean and easy to follow and the test coverage is excellent. The only issue I have with the implementation is the disappearing bomb problem, although that is a UX/design issue and not necessarily within the scope of the exercise.
Read over the comments and let me know if you have any questions - I don't think you need to resubmit this one, though.


New version: SimilaritySearch v0.3.9

Registering package: SimilaritySearch
Repository: https://github.com/sadit/SimilaritySearch.jl
Created by: @sadit
Version: v0.3.9
Commit: ca32b4a867374403c7660304234202b91f50a19e
Reviewed by: @sadit
Reference: https://github.com/sadit/SimilaritySearch.jl/commit/ca32b4a867374403c7660304234202b91f50a19e#commitcomment-35550890

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

Does not meet sequential version number guideline

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

#4483


Monitor total number of users in _users plugin

Add to the nextcloud_users plugin graph the total number of users of the platform.

I will merge this PR now. I hoped that these small changes would have be corrected until now.
Thank you for your pull request I really like the idea, but please use tab characters and stop using normal spaces to align stuff.


Change background by double clicking it

As in subject.

Featured in https://github.com/jakke-korpelainen/newtab/commit/ba49a50fc1c403827b4c6cb01cfc170c120347d1


minimum view count

Hi all,
Your program is working really nice, thanks.
However, how do I get around this notification:
Skipped a song - The found song had less views than the minimum view count, (use the cli to increase this).
and this one:
[View count 5676 does not meet MIN_VIEW_COUNT value of 10000 [a-youtube-url-comes-her]]
Many thanks,
Jurgen

you need to specify the minimum in the command, example:
spotify2mp3.py -p https://open.spotify.com/playlist/17L6OQxf8zVMYc3XmDl9Ni?si=fa717d3f14d74188 --min-views 5


Capture shortcut keys in apps like VMWare

Regression?
No
System Info and Version
 System/Version info
Hyprland, built from branch main at commit b03f41efec14273cf25c42d4cef326acc36cb319  (xwayland: fix setting title prop (6809)).
Date: Mon Jul 8 21:16:42 2024
Tag: v0.41.2-27-gb03f41ef, commits: 4913

flags: (if any)

System Information:
System name: Linux
Node name: prayag-linux
Release: 6.9.8-zen1-1-zen
Version: #1 ZEN SMP PREEMPT_DYNAMIC Fri, 05 Jul 2024 22:11:01 +0000

GPU information:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) (prog-if 00 [VGA controller])
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev c9) (prog-if 00 [VGA controller])
NVRM version: NVIDIA UNIX x86_64 Kernel Module  555.58.02  Tue Jun 25 01:39:15 UTC 2024

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:

======Config-Start======

Config File: /home/prayag/.config/hypr/hyprland.conf: Read Succeeded
monitor=eDP-1,1920x1080@120.21,0x0,1.25
monitor=,preferred,auto,1,mirror,eDP-1
# See https://wiki.hyprland.org/Configuring/Keywords/ for more

# Execute your favorite apps at launch
exec-once = dbus-update-activation-environment --systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP
exec-once = systemctl --user import-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP
exec-once = waybar &
exec-once = swayosd-server &
exec-once = emacs --daemon &
exec-once = otd-daemon & # open tablet driver
exec-once = wal -R
exec-once = cliphist wipe && wl-paste --type text --watch cliphist store &
exec-once = wl-paste --type image --watch cliphist store &
exec-once = sleep 0 && swww init &
exec-once = dunst --daemon &
exec-once = hypridle &
exec-once = hyprpm reload -n &
exec-once = hyprctl setcursor Bibata-Original-Classic 20
exec-once = xsetroot -cursor_name left_ptr &
exec-once = "$HOME/.local/bin/update_keyboard_backlight.sh" &
exec-once = sleep 2 && xrdb -merge ~/.Xresources
exec-once = sleep 5 && ([[ $(cat /sys/class/power_supply/BAT*/status) = "Discharging" ]] && notify-send "Please connect a charger!" -i "battery-empty" -u critical)
exec-once = lxsession &

# Source a file (multi-file configs)
source = ~/.cache/wal/colors-hyprland.conf

# Some default env vars.
env = XCURSOR_SIZE,20
env = XDG_SESSION_TYPE,wayland
env = ELECTRON_OZONE_PLATFORM_HINT,wayland

# nvidia
#env = DRI_PRIME,pci-0000_01_00_0
#env = __VK_LAYER_NV_optimus,NVIDIA_only
#env = __GLX_VENDOR_LIBRARY_NAME,nvidia
#env = __NV_PRIME_RENDER_OFFLOAD,1
#env = LIBVA_DRIVER_NAME,nvidia
#env = VDPAU_DRIVER,nvidia
#env = WLR_NO_HARDWARE_CURSORS,1
# use integrated gpu: env = WLR_DRM_DEVICES,/home/prayag/.config/hypr/nvidia:/home/prayag/.config/hypr/amd

# For all categories, see https://wiki.hyprland.org/Configuring/Variables/
input {
    kb_layout = us
    kb_variant =
    kb_model =
    kb_options =
    kb_rules =

    follow_mouse = 1

    touchpad {
      natural_scroll = yes
      disable_while_typing = yes
      middle_button_emulation = yes
      tap-and-drag = yes
    }
    sensitivity = 0 # -1.0 - 1.0, 0 means no modification.
    numlock_by_default = true
}

plugin {
  hyprexpo {
      columns = 3
      gap_size = 5
      bg_col = rgb(111111)
      workspace_method = first 1 # [center/first] [workspace] e.g. first 1 or center m+1
      enable_gesture = true # laptop touchpad, 4 fingers
      gesture_distance = 300 # how far is the "max"
      gesture_positive = false # positive = swipe down. Negative = swipe up.
  }
}

xwayland {
  force_zero_scaling = true
}

misc {
    disable_hyprland_logo = true
    disable_splash_rendering = true

    enable_swallow = false
    swallow_regex = ^(Alacritty)$
    vfr = false
}

general {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more

    gaps_in = 3
    gaps_out = 6
    border_size = 2
    col.active_border = $color8
    col.inactive_border = $color8

    layout = dwindle
}

decoration {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more

    rounding = 0

    drop_shadow = yes
    shadow_range = 4
    shadow_render_power = 1
    col.shadow = rgba(1a1a1a80)

    active_opacity = 1
    inactive_opacity = 0.85
    fullscreen_opacity = 1

    blur {
        enabled = yes
        size = 4
        passes = 4
        new_optimizations = on
        ignore_opacity = true
        noise = 0.1

        blurls=waybar
        blurls=rofi
        blurls=notifications
    }
}

animations {
    enabled = yes

    # Some default animations, see https://wiki.hyprland.org/Configuring/Animations/ for more

    bezier = spring, 0.4, 0, 0.04, 1
    bezier = easeOut, 0.17, 0.84, 0.44, 1

    animation = windows, 1, 2, easeOut
    animation = windowsOut, 1, 2, easeOut
    animation = windowsMove, 1, 2, easeOut
    animation = border, 1, 10, default
    animation = borderangle, 1, 8, default
    animation = fade, 1, 7, default
    animation = workspaces, 1, 4, easeOut
}

dwindle {
    # See https://wiki.hyprland.org/Configuring/Dwindle-Layout/ for more
    pseudotile = yes # master switch for pseudotiling. Enabling is bound to mainMod + P in the keybinds section below
    preserve_split = yes # you probably want this
}

master {
    # See https://wiki.hyprland.org/Configuring/Master-Layout/ for more
    #new_is_master = true
}

gestures {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more
    workspace_swipe = on
    workspace_swipe_fingers = 3
    workspace_swipe_cancel_ratio = 0.25
}

# Example per-device config
# See https://wiki.hyprland.org/Configuring/Keywords/#executing for more
device {
  name = epic-mouse-v1
  sensitivity = -0.5
}

# Layer Rules
layerrule = ignorezero, notifications
layerrule = ignorezero, rofi

# Wallpaper
windowrulev2 = size 100% 100%, title:(^video-wallpaper-mpv-bg$)
windowrulev2 = move 0 0, title:(^video-wallpaper-mpv-bg$)
windowrulev2 = float, title:(^video-wallpaper-mpv-bg$)
windowrulev2 = pin, title:(^video-wallpaper-mpv-bg$)
windowrulev2 = noinitialfocus, title:(^video-wallpaper-mpv-bg$)
windowrulev2 = nofocus, title:(^video-wallpaper-mpv-bg$)

# See https://wiki.hyprland.org/Configuring/Window-Rules/ for more
windowrulev2 = suppressevent maximize, class:.* # You'll probably like this.
windowrulev2 = noborder, title:(.*is sharing your screen\.$)
windowrulev2 = noblur, title:(.*is sharing your screen\.$)
windowrulev2 = noshadow, title:(.*is sharing your screen\.$)
windowrulev2 = move 30% 100%-70, title:(.*is sharing your screen\.$)

# Window Rules
windowrule = float, ^(yad)$
windowrule = float, ^(MEGAsync)$
windowrule = float, ^(LibreWolf — Sharing Indicator)$
windowrule = noborder, ^(MEGAsync)$
windowrule = float, title:(Emulator)
windowrule = float, title:(KDE Connect Daemon)
windowrule = noblur, title:(KDE Connect Daemon)
windowrule = noblur, ^(MEGAsync)$
windowrule = noshadow, ^(MEGAsync)$

# Transparency
windowrule = opacity 0.85, ^(thunar)$
windowrulev2 = opacity 0.95, initialTitle:^(Visual Studio Code)$

# XWaylandVideoBridge
windowrulev2 = opacity 0.0 override 0.0 override,class:^(xwaylandvideobridge)$
windowrulev2 = noanim,class:^(xwaylandvideobridge)$
windowrulev2 = nofocus,class:^(xwaylandvideobridge)$
windowrulev2 = noinitialfocus,class:^(xwaylandvideobridge)$

# See https://wiki.hyprland.org/Configuring/Keywords/ for more
$mainMod = SUPER

# Other
bind = $mainMod CONTROL, F12, exec, $HOME/.local/bin/reload-hyprland.sh
bind = $mainMod SHIFT, P, exec, hyprpicker | wl-copy
bind = $mainMod, BackSpace, exec, hyprlock &

# Applications
bind = $mainMod, Return, exec, alacritty
bind = $mainMod, W, killactive,
bind = $mainMod, E, exec, thunar

# Rofi bindings
bind = $mainMod, R, exec, rofi -show drun
bind = $mainMod, Equal, exec, rofi -modi calc -show calc
bind = , XF86Calculator, exec, rofi -modi calc -show calc
bind = $mainMod, Period, exec, rofimoji --action copy
bind = $mainMod, B, exec, $HOME/.local/bin/bitwarden.sh
bind = $mainMod, N, exec, dunstctl action
bind = $mainMod, V, exec, cliphist list | rofi -dmenu -p  | cliphist decode | wl-copy
bind = $mainMod ALT, V, exec, wtype "$(wl-paste)"

# Screenshots
bind = ALT SHIFT, S, exec, $HOME/.local/bin/ss-wayland.sh taoc
bind = ALT, PRINT, exec, $HOME/.local/bin/ss-wayland.sh toc
bind = CONTROL, PRINT, exec, $HOME/.local/bin/ss-wayland.sh
bind = $mainMod SHIFT, S, exec, $HOME/.local/bin/ss-wayland.sh aoc
bind = $mainMod, PRINT, exec, $HOME/.local/bin/ss-wayland.sh oc

# Audio
bind = $mainMod, P, exec, playerctl play-pause
bind = $mainMod, M, exec, swayosd-client --input-volume mute-toggle
bind = , XF86AudioPlay, exec, playerctl play-pause
bind = , XF86AudioNext, exec, playerctl next
bind = , XF86AudioPrev, exec, playerctl prev
#binde = , XF86AudioRaiseVolume, exec, pamixer -i 5 && $HOME/.local/bin/volnotify.sh
binde = , XF86AudioRaiseVolume, exec, swayosd-client --output-volume raise
binde = , XF86AudioLowerVolume, exec, swayosd-client --output-volume lower
binde = SHIFT, XF86AudioRaiseVolume, exec, swayosd-client --input-volume raise
binde = SHIFT, XF86AudioLowerVolume, exec, swayosd-client --input-volume lower
bind = , XF86AudioMute, exec, swayosd-client --output-volume mute-toggle
bind = , XF86AudioMicMute, exec, swayosd-client --input-volume mute-toggle
bind = , XF86MonBrightnessDown, exec, swayosd-client --brightness -10
bind = , XF86MonBrightnessUp, exec, swayosd-client --brightness +10

# Tiling
bind = $mainMod, T, togglefloating,
bind = $mainMod, F, fullscreen,

# Move focus with mainMod + arrow keys
bind = $mainMod, H, movefocus, l
bind = $mainMod, L, movefocus, r
bind = $mainMod, K, movefocus, u
bind = $mainMod, J, movefocus, d

# Switch workspaces with mainMod + [0-9]
bind = $mainMod, 1, workspace, 1
bind = $mainMod, 2, workspace, 2
bind = $mainMod, 3, workspace, 3
bind = $mainMod, 4, workspace, 4
bind = $mainMod, 5, workspace, 5
bind = $mainMod, 6, workspace, 6
bind = $mainMod, 7, workspace, 7
bind = $mainMod, 8, workspace, 8
bind = $mainMod, 9, workspace, 9
bind = $mainMod, 0, workspace, 10
bind = $mainMod, bracketright, workspace, +1
bind = $mainMod, bracketleft, workspace, -1

# Resizing active window
bind = $mainMod ALT, L, resizeactive, 20 0
bind = $mainMod ALT, H, resizeactive, -20 0
bind = $mainMod ALT, K, resizeactive, 0 -20
bind = $mainMod ALT, J, resizeactive, 0 20

# Move active window to a workspace with mainMod + SHIFT + [0-9]
bind = $mainMod SHIFT, 1, movetoworkspace, 1
bind = $mainMod SHIFT, 2, movetoworkspace, 2
bind = $mainMod SHIFT, 3, movetoworkspace, 3
bind = $mainMod SHIFT, 4, movetoworkspace, 4
bind = $mainMod SHIFT, 5, movetoworkspace, 5
bind = $mainMod SHIFT, 6, movetoworkspace, 6
bind = $mainMod SHIFT, 7, movetoworkspace, 7
bind = $mainMod SHIFT, 8, movetoworkspace, 8
bind = $mainMod SHIFT, 9, movetoworkspace, 9
bind = $mainMod SHIFT, 0, movetoworkspace, 10
bind = $mainMod CONTROL, bracketright, movetoworkspace, +1
bind = $mainMod CONTROL, bracketleft, movetoworkspace, -1

# Scroll through existing workspaces with mainMod + scroll
bind = $mainMod, mouse_down, workspace, e+1
bind = $mainMod, mouse_up, workspace, e-1

# Move/resize windows with mainMod + LMB/RMB and dragging
bindm = $mainMod, mouse:272, movewindow
bindm = $mainMod, mouse:273, resizewindow

Config File: /home/prayag/.cache/wal/colors-hyprland.conf: Read Succeeded
$background = rgb(2E3440)

$color1 = rgb(88C0D0)
$color2 = rgb(BF616A)
$color3 = rgb(B48EAD)
$color4 = rgb(EBCB8B)
$color5 = rgb(A3BE8C)
$color6 = rgb(D08770)
$color7 = rgb(E5E9F0)
$color8 = rgb(4C566A)
$color9 = rgb(88C0D0)
$color10 = rgb(BF616A)
$color11 = rgb(B48EAD)
$color12 = rgb(EBCB8B)
$color13 = rgb(A3BE8C)
$color14 = rgb(D08770)
$color15 = rgb(8FBCBB)

======Config-End========

Description
In remote desktop apps or virtual machine apps like VMWare Horizon Client, shortcut keys like Win + R are not passed down to the application if their binding exists in the Hyprland config. Is there a way to tell Hyprland to pass down these shortcuts to the application if it's in focus?
I could use this app in an X11 environment like BSPWM but there are several reasons I don't want to switch; for example, the excellent multi-monitor support Hyprland has, gesture support and animations.
How to reproduce

Define a binding for Win + R in your Hyprland config:

# Just an example binding which launches Rofi
bind = $mainMod, R, exec, rofi -show drun

Launch a virtual machine (Windows 10/11)
Press Win + R in order to open the "Run" dialog in Windows.
Rofi launches instead of "Run" (which is undesirable)

Crash reports, logs, images, videos
No response

empty submap

vmware should inhibit shortcuts by itself but if it doesnt yea just make an empty submap


Change name to Markedsspillet (markedsspillet.dataekspeditioner.dk)

Fixes #77.

Seems to work. Merging.


Getting pghoard.rohmu.errors.InvalidConfigurationError

Following is my pghoard.json file:

{
    "backup_location": "./metadata",
    "backup_sites": {
        "main": {
            "nodes": [
                {
                    "host": "X.X.X.X",
                    "password": "blahblah",
                    "port": 5432,
                    "user": "backup"
                }
            ],
            "object_storage": {
                "storage_type": "google",
                "bucket_name": "abcdef",
                "project_id": "project-id",
                "credential_file": "/home/ubuntu/credentials.json"
            }
        }
    }
}

Following the traceback for the command:
ubuntu@localhost:~$ pghoard --config=pghoard.json
2017-01-11 03:24:36,531	pghoard	MainThread	DEBUG	Loading JSON config from: 'pghoard.json', signal: None
2017-01-11 03:24:36,585	pghoard	MainThread	ERROR	Invalid config file 'pghoard.json': InvalidConfigurationError: Site 'main' command 'pg_basebackup' not found
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/pghoard/pghoard.py", line 487, in load_config
    new_config = config.read_json_config_file(self.config_path)
  File "/usr/local/lib/python3.5/dist-packages/pghoard/config.py", line 152, in read_json_config_file
    return set_config_defaults(config, check_commands=check_commands)
  File "/usr/local/lib/python3.5/dist-packages/pghoard/config.py", line 126, in set_config_defaults
    raise InvalidConfigurationError("Site {!r} command {!r} not found".format(site_name, command))
pghoard.rohmu.errors.InvalidConfigurationError: Site 'main' command 'pg_basebackup' not found
pghoard: failed to load config pghoard.json: Site 'main' command 'pg_basebackup' not found

Not sure what exactly am I doing wrong here!

PGHoard does not find the "pg_basebackup" command. You either do not have the PostgreSQL package installed OR pghoard just needs to be pointed to the right directory. See pg_bin_directory in https://github.com/ohmu/pghoard/
Something like this should fix it:
    "backup_location": "./metadata",
    "backup_sites": {
        "main": {
            "pg_bin_directory": "/usr/pgsql-9.5/bin",

Ah my bad @melor! Thanks for the advice. It worked.


Conversion to TypeScript

Please see the discussion in #3
This is just a basic translation from JavaScript to TypeScript. To compile, run npm run build. Then the module should work just like it currently does.

Project is been moved to http-exceptions. Could you create the PR there again? Thank you again for your contribution!


[WIP] Updated ver of httpretty and requests

Expect fix to #40 and and #51 in the new httpretty version

Py3 fails with
httpretty == 0.8.14
requests== 2.9.1
Traceback (most recent call last):
  File "/opt/python/3.3.5/lib/python3.3/threading.py", line 901, in _bootstrap_inner
    self.run()
  File "/opt/python/3.3.5/lib/python3.3/threading.py", line 858, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/python/3.3.5/lib/python3.3/multiprocessing/pool.py", line 347, in _handle_tasks
    for i, task in enumerate(taskseq):
  File "/opt/python/3.3.5/lib/python3.3/multiprocessing/pool.py", line 274, in <genexpr>
    self._taskqueue.put((((result._job, i, func, (x,), {})
  File "/home/travis/build/piskvorky/smart_open/smart_open/smart_open_lib.py", line 636, in <genexpr>
    keys = (key for key in bucket.list(prefix=prefix) if accept_key(key.name))
  File "/home/travis/virtualenv/python3.3.5/lib/python3.3/site-packages/boto/s3/bucketlistresultset.py", line 34, in bucket_lister
    encoding_type=encoding_type)
  File "/home/travis/virtualenv/python3.3.5/lib/python3.3/site-packages/boto/s3/bucket.py", line 473, in get_all_keys
    '', headers, **params)
  File "/home/travis/virtualenv/python3.3.5/lib/python3.3/site-packages/boto/s3/bucket.py", line 399, in _get_all
    query_args=query_args)
  File "/home/travis/virtualenv/python3.3.5/lib/python3.3/site-packages/boto/s3/connection.py", line 665, in make_request
    retry_handler=retry_handler
  File "/home/travis/virtualenv/python3.3.5/lib/python3.3/site-packages/boto/connection.py", line 1071, in make_request
    retry_handler=retry_handler)
  File "/home/travis/virtualenv/python3.3.5/lib/python3.3/site-packages/boto/connection.py", line 1030, in _mexe
    raise ex
  File "/home/travis/virtualenv/python3.3.5/lib/python3.3/site-packages/boto/connection.py", line 944, in _mexe
    response = connection.getresponse()
  File "/opt/python/3.3.5/lib/python3.3/http/client.py", line 1147, in getresponse
    response.begin()
  File "/opt/python/3.3.5/lib/python3.3/http/client.py", line 382, in begin
    self.headers = self.msg = parse_headers(self.fp)
  File "/opt/python/3.3.5/lib/python3.3/http/client.py", line 264, in parse_headers
    raise LineTooLong("header line")
http.client.LineTooLong: got more than 65536 bytes when reading header line

Requests version updated in https://github.com/piskvorky/smart_open/pull/67
Httpretty version is still fixed. @nikicc Is there any need to bump it up?

@tmylk: the bump of httpretty to 0.8.12 or 0.8.14 should fix the issue #40, which is causing problems for us. Though, since test are failing with these versions, we probably need to wait for 0.8.15 and hope for the best :smile:

No longer pinned so this PR is not needed.


TagBot trigger issue

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

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

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

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

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

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

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