Burst animation happens twice on ios

I am struggling with an issue with Burst.
On every desktop browser, and android phones, the burst is played normally. However, on ios something strange happens:
The animation is ran twice, and the total duration is the duration I sat as a property on children. So, on android there is one burst with a duration of five seconds and on ios the is two bursts with a total duration of five seconds.
The code for the mojs.Burst
const mojs = require('mo-js');
        this.burst = new mojs.Burst({
            parent: '#label-' + this.props.id,
            radius: 40,
            degree: 300,
            angle: 120,
            count: 11,
            children: {
                shape: 'line',
                radius: 6,
                scale: 1,
                stroke: this.props.color,
                strokeDasharray: '100%',
                strokeDashoffset: { '-100%': '100%' },
                duration: 5000,
                easing: 'quad.out',
            }

The triggering:
this.burst.replay();

To make things a bit easier for people to help you:

What iOS version the problem happens?
can you post a reduced case on codepen or similar service?
does it happen in a specific scenario?
does it happens only with burst?

I'll add the codepen later.
So far we've tested it with iPhone X and iPhone 8. Both running ios 11.
I have only used Burst.
The scenario is an onClick event on an image. This is a react-app.
I can send you an url in an email or something if you're interested.

Also happens on iPad with ios 11.2.5

The bug is present here: https://codepen.io/rkhayat/pen/aBpMRr?editors=1010

The bug is also at Chrome on IOS

@eltonmesquita Have you had a chance to look at the codepen?

Nope. Unfortunately this is a pretty messy week for me and my Xcode is broken :(
I'll try it next week, alright?

Hi @olemartin!
I can't test on iOS for now, sorry, but, can you try to change this:
strokeDashoffset: { '-100%' : '100%' }
...into this:
strokeDashoffset: { 0 : '100%' }
Thanks for your feedback :wink:

Tested and working fine on an iPad Pro with iOS 11.2.6: can't reproduce this issue.

Thanks!
Seems like strokeDashoffset: { 0 : '100%' } did the trick. At least on https://codepen.io/rkhayat/pen/aBpMRr?editors=1010

Very nice! I suspected there was a problem with configuring this property this way. That's cool, thanks for the reply and have a nice day :+1:


sgx-sdk: 2.21 -> 2.23

Description of changes

Updates the sgx-* package family to the latest 2.23 release. These packages are used (1) by devs to build Intel SGX enclaves and (2) by operators running the NixOS aesmd service to easily run enclaves on servers. Intel SGX is a Confidential Computing technology for running enclaves and confidential VMs (Intel TDX) on Intel server CPUs alongside an untrusted hypervisor/Linux/userspace software stack.
These changes were tested on an Azure gen2 VM (DCSv3) running NixOS.

sgx-sdk/ipp-crypto: 2021.9.0 -> 2021.10.0

gcc 13 still failing to compile w/o warnings...
Diff: https://github.com/intel/ipp-crypto/compare/ippcp_2021.9.0...ippcp_2021.10.0
Changelog: https://github.com/intel/ipp-crypto/blob/ippcp_2021.10.0/CHANGELOG.md

sgx-sdk: 2.21 -> 2.23

make preparation step keeps changing; use a more maintainable .patch
approach instead of copying over steps from Makefile.
Remove stale patch.
Add build reproducibility patch for binary-bundled zip files, courtesy of @haraldh <3
Diff: https://github.com/intel/linux-sgx/compare/sgx_2.21...sgx_2.23
Changelog (2.22): https://github.com/intel/linux-sgx/releases/tag/sgx_2.22
Changelog (2.23): https://github.com/intel/linux-sgx/releases/tag/sgx_2.23

sgx-psw: 2.21 -> 2.23
sgx-azure-dcap-client: 1.12.1 -> 1.12.3

Diff: https://github.com/microsoft/Azure-DCAP-Client/compare/1.12.1...1.12.3

sgx-ssl: 1.1.1u -> 3.0.12

Extract tests into separate build-only derivation, since SIM mode tests don't work on non-Intel hardware.
Diff: https://github.com/intel/intel-sgx-ssl/compare/lin_2.21_1.1.1u...3.0_Rev2

sgx-sdk: add 'phlip9' as maintainer of sgx packages

For additional context, see also my previous update PR (2.16 -> 2.21): https://github.com/NixOS/nixpkgs/pull/254845
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Nice! Looks a lot like https://github.com/NixOS/nixpkgs/pull/243098

Seems like this runs also into https://github.com/NixOS/nixpkgs/pull/243098#issuecomment-1910248447

On a related note, I don't actually use this sgx-ssl package and I'm wondering how people are using this.

Currently I use sgx-ssl to build
https://github.com/intel/SGXDataCenterAttestationPrimitives
here:
https://github.com/haraldh/nixsgx/tree/main/packages/sgx-dcap
As soon, as I cleaned it up, I will upstream sgx-dcap

Added a commit that (1) pulls out the tests from sgx-ssl into a separate derivation, (2) we only build but not run the tests, since only real Intel HW can run (both SIM and HW!), and (3) added a Intel SGX HW test variant like the others.
You can run the tests (only on real Intel hardware) with:
$ nix run .#sgx-ssl.tests.HW
$ nix run .#sgx-ssl.tests.SIM

OfBorg is now finally green on x86_64-linux : ) https://github.com/NixOS/nixpkgs/pull/283405/checks?check_run_id=21114692010

$ nix run .#sgx-ssl.tests.SIM

Tests passed on my machine.

Output of nix run .#sgx-ssl.tests.SIM
$ nix run .#sgx-ssl.tests.SIM                                                                                [179/207]
[1/3/12 built, 1/163/165 copied (1224.4/1434.1 MiB), 281.4/327.4 MiB DL] building ipp-crypto-2021.10.0 (configurePhase): -- ASM object forma
token_path: /home/sylvain/enclave.token
Start tests
{"public":"3082020a0282020100bdaf4e5f1a49323c373442ed2d6c834944901809a16cec2cfa7bef01e7dc85a563af7566966011ae20964c0be83275fe0916905d50022d29dd32ea887e867f9eeb6519eee88ccedd983de985a8c5480c12034abcdd0bc796d56bd4cae6b2e9b42c74a3a9d3d2396ee3e16d3920a5a816
9f5b67e4da618b58f44fb59eae83478506d40e6960c5505ed042c002cca810ad67e3e65e9fbe5243073ac8b0cbeed4c550258c31403ee892520121a62087a9958c17116aee8b6bca18a64afbdb3042133bc65d4421d762a46973096bb882592efac57517ca1c702896d9e24cedbd322893de7236192680f4033168e5a2f3f
612efcc5b51332d918ea94e704bb7cfe2e147e24613475c9a1b38a2fc901d9036bf9fc3b78f8adcc4089f1c20c7e97232e86ccfeb52c9ab3689307ab9d814825ad4f44da38d0011e08d1cca8ea7fa5e72812821fb99f3cb414523af72e6a22c23f8f39bafa0f095e64278cb4f25f53e186f9e4d4c8cff3c1b602cff9f2f57
858226c5abfd018e05fb6c3fb89ea305b5047fec62d8b8d42d29ed2ae76e0fde7ade20845fa4d735da89233e6cd05c53b9b48a9d17dea74b14e1317d27195f69d9ecd7e9e9d306a3293ffdd43229f947a29c6625af98cb71c34d5b2d7dc32b679a40df0a4bbc14984a0d13dffd8f830b78b71fdd6bd4ec0bdfa005c0863ab
8bbe2a292a7acf20871525b6fa55a85122790e4130203010001"}
{"private":"308209280201000282020100bdaf4e5f1a49323c373442ed2d6c834944901809a16cec2cfa7bef01e7dc85a563af7566966011ae20964c0be83275fe0916905d50022d29dd32ea887e867f9eeb6519eee88ccedd983de985a8c5480c12034abcdd0bc796d56bd4cae6b2e9b42c74a3a9d3d2396ee3e16d392
[encoded data, 4301 characters]
fac7e9998c76826bb88c5562a7cef1bf516dafce949ccb6709c0ca2067f1a5eab21e43418dd46b1b33c64e1f98c82d1546ccff97915cc1b9435c0af2c6ea466f7d72b25de7e22f019fddb05659"}
test rsa_key_gen completed
{"public":"046a598e18717b8a4892e0aa98d7a3cab7eea6c013df97f534e98df4c6f24738c0d982336179f159c8328e98d277a25e67e264c5804699c5d3cfe4efd4b449f9a7e9e064e197cddae8c2d9671aaade0d4932a5850f8ca5f3e77423ef6a83f7757c"}
{"private":"3081a40201010430712bd422ae9f865a282d556245f03299397f3369ab874b6c3c1ae69f479ca741037869ab562a67833ab7e1cd60d52500a00706052b81040022a164036200046a598e18717b8a4892e0aa98d7a3cab7eea6c013df97f534e98df4c6f24738c0d982336179f159c8328e98d277a25e67e26
4c5804699c5d3cfe4efd4b449f9a7e9e064e197cddae8c2d9671aaade0d4932a5850f8ca5f3e77423ef6a83f7757c"}
test ec_key_gen completed
test rsa_test completed
     y^2 = x^3 + a*x + b (mod p)
A cyclic subgroup:
     point at infinity
combined multiplication ...
 ok

NIST curve P-224 (optimised implementation):
NIST test vectors ...
NIST curve P-256 (optimised implementation):
NIST test vectors ...
NIST curve P-521 (optimised implementation):
NIST test vectors ...

Testing SHA-224 ... passed.
test sha256_test completed
test 1 ok
test 2 ok
test 3 ok
test sha1_test completed
test hmac_test completed
original thread, id:<PHONE_NUMBER>41536
in new thread, id:<PHONE_NUMBER>62304
in new thread, id:<PHONE_NUMBER>83072
PASS
test threads_test completed
test evp_sm2_sign_verify completed
test evp_sm2_encrypt_decrypt completed
test evp_sm3 completed
test evp_sm4_cbc completed
test evp_sm4_ctr completed

$ nix run .#sgx-ssl.tests.HW

What is required to run the sgx-ssl hardware tests? I have the out-of-tree sgx driver installed, on an SGX -cacpable machine, and get the following error:
$ nix run .#sgx-ssl.tests.HW
token_path: /home/sylvain/enclave.token
Error: Unexpected error occurred.

What is required to run the sgx-ssl hardware tests? I have the out-of-tree sgx driver installed, on an SGX -cacpable machine (...)

Unfortunate that it gives such a useless error message. My understanding is that the out-of-tree driver is deprecated and not-guaranteed-compatible (?) now that SGX support is upstreamed to Linux proper, so I'd recommend trying on a recent kernel with the in-tree driver.
Assuming your kernel is setup properly, you should see some evidence like:
$ journalctl --dmesg --grep=sgx
Jan 24 03:18:51 kernel: sgx: EPC section 0x2c0000000-0x3bfffffff

$ ls -l /dev | grep sgx
drwxr-xr-x  2 root root          80 Jan 24 03:18 sgx
crw-rw----  1 root sgx      10, 125 Jan 24 03:18 sgx_enclave
crw-rw----  1 root sgx_prv  10, 126 Jan 24 03:18 sgx_provision

You'll also want the user running tests to be a member of the sgx group (or just run as root).
If this still doesn't work, you could try our nix-packaged sgx-detect for more detailed debugging:
$ nix run github:lexe-app/lexe-public#packages.x86_64-linux.sgx-detect

Detecting SGX, this may take a minute...
✔  SGX instruction set
  ✔  CPU support
  ✔  CPU configuration
  ✔  Enclave attributes
  ✔  Enclave Page Cache
  SGX features
    ✔  SGX2  ✔  EXINFO  ✘  ENCLV  ✘  OVERSUB  ✔  KSS
    Total EPC size: 4.0GiB
✔  Flexible launch control
  ✔  CPU support
  ✔  CPU configuration
  ✔  Able to launch production mode enclave
✔  SGX system software
  ✔  SGX kernel device (/dev/sgx_enclave)
  ✘  libsgx_enclave_common
  ✔  AESM service
  ✔  Able to launch enclaves
    ✔  Debug mode
    ✔  Production mode
    ✔  Production mode (Intel whitelisted)

You're all set to start running SGX programs!

Rebased on latest nixos-unstable

@pbsds
LGTM, but there seems to some missing dynamic linking.
...
I assume this is fine?

Right, the aesm_service binary wrapper sets the LD_LIBRARY_PATH to include these libs.
makeWrapper $out/aesm/aesm_service $out/bin/aesm_service \
  --suffix LD_LIBRARY_PATH : ${lib.makeLibraryPath [ protobuf ]}:$out/aesm \
  --chdir "$out/aesm"


[Bug] dbt-snowflake opens a new connection per each model

Is this a new bug in dbt-snowflake?

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

Current Behavior
The way I am currently using dbt-snowflake locally is that, I have a dbt profile as follows:
my-snowflake:
  target: dev
  outputs:
    dev:
        type: snowflake
        account: some-account
        authenticator: externalbrowser

        database: xyz
        user: xyz
        role: xyz
        warehouse: xyz
        schema: ""

        threads: 4

However, running dbt test creates a snowflake connection per each model. This fires a huge amount of connection request on my browser, and I barely have time to click on Duo for 2FA requests. After a few try, because I wasn't responding enough on Duo, the 2FA would lock me out.
I am wondering what is the connection management practices in this repo looks like? Has the connection pool been properly managed? https://docs.snowflake.com/en/developer-guide/node-js/nodejs-driver-connect#creating-a-connection-pool
Expected Behavior
Each dbt run should create a proper connection, ideally one per each thread, and whatever dbt jobs running should pick up connections from the pool, instead of firing auth request like it is free candy.
Steps To Reproduce

Create a dbt profile in ~/.dbt/profile.yml
set authenticator: externalbrowser
Use an example dbt project with a lot of models and run dbt deps && dbt test.

Relevant log output
No response
Environment
- OS: MacOs
- Python: 3.12
- dbt-core: 1.8.8
- dbt-snowflake: 1.8.4

Additional Context
No response

@TiansuYu Have you enabled token caching? We have some links in our docs here https://docs.getdbt.com/docs/cloud/connect-data-platform/connect-snowflake#snowflake-mfa


LDAP minor fixes

Hi!
based on https://forum.opnsense.org/index.php?topic=21605.0

baseDN igonred in search function if ldapauthcontainers is set. help text for "Authentication containers" input fixed
https://github.com/opnsense/core/blob/25959a45a918000c36d092403ac3e3c223c4671a/src/opnsense/mvc/app/library/OPNsense/Auth/LDAP.php#L160-L163

In select "Authentication containers" modal Close button is actually a Save button (writes changes to the "Authentication containers" input)

Some debug info added to System: Access: Tester page for LDAP servers

thanks!

@kulikov-a maybe we better add a method getLastErrors() for the  error feedback and move this into a separate array, it makes it more explicit that this is error feedback and not something returned by the authenticator. Other than that it's definitely an improvement to make sure errors are returned to the user here.

@AdSchellevis
thanks! more correct of course
I will try to do so. for now I'm converting it to a draft

@AdSchellevis it's kind of done.
moved errors to a separate array.

slightly tweaked the logLdapError function: it turned out that a LDAP_OPT_ERROR_STRING can contain not only commas but also new lines and even tabs special characters.
added Cancel button to "Authentication containers" modal.
added some debug (and the message for this case in modal window) for "Authentication containers" empty search results
(https://forum.opnsense.org/index.php?topic=21605.msg103543#msg103543)

please take a look when you have time

@kulikov-a looks good, thanks, I'll pull it in to master, haven't tried it myself yet, but don't see any reason why it shouldn't.

Wow! thanks!!!

@kulikov-a made a small adjustment after testing (https://github.com/opnsense/core/commit/3277c0beb6f3ecb957fef0e95ae0562cea43eb99), when you can't connect, there's an ldap connect error but no LDAP_OPT_ERROR_STRING, so it's better to omit it in that case.

@AdSchellevis thanks! it is always better to add existing ones )
I should have noticed it. thank!


Fix path to Velocity's docs

Curious. I wonder if this is a permanent change or a webhost mixup. At any rate, we can revert later if necessary.


Better tests for Cloudkeeper core and plugins

Currently the core has some test coverage and the plugins essentially none. Each plugin has a stub that tests some cli args essentially as a starting point for adding more tests. All the infrastructure is already there and tox configured for each plugin.

Test coverage has improved significantly. Since this is an ongoing effort - let's close this ticket.


bootstrap.sh/test.sh failing for me - No module named boto

docker run -ti -v $PWD:/repo centos bash

Inside the container:
cd /repo
chmod +x bootstrap.sh
./bootstrap.sh # note - I had to remove 'set -e' since it was quietly failing early
./test/test.sh

Output:
HOME=/tmp/tmp.4n7WIFREAf
Traceback (most recent call last):
  File "/repo/bin/rpm-s3", line 14, in <module>
    import boto
ImportError: No module named boto

You probably need to install python-boto from epel in the container.

@drnic we ran into several issues when trying to run in a container, so we just built our own as follows:
Dockerfile:
FROM centos:7

RUN yum update -y
RUN yum install -y deltarpm python-deltarpm
RUN yum install -y rpm-sign

RUN curl "https://bootstrap.pypa.io/get-pip.py" | python

ADD . /rpm-s3
WORKDIR /rpm-s3

RUN pip install boto

build/tag the image, then run.

Worked for us.


@capacitor/core": "4.0.1" support

Describe the bug
Looks like there is no support for @capacitor/core 4.0.x?
To Reproduce
Steps to reproduce the behavior:
npm install @capacitor-community/bluetooth-le
Expected behavior
it to install
Plugin version:
1.8.3
Desktop (please complete the following information):
macOS Monterey 12.5
Additional context
When you create a new ionic project (angular) it utilizes angular 14 and @capacitor/core version 4.0.1
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@capacitor/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@capacitor-community/bluetooth-le
npm ERR!   @capacitor-community/bluetooth-le@"*" from the root project

You can use the prerelease of the plugin V2:
npm i @capacitor-community/bluetooth-le@next

Will be closed by https://github.com/capacitor-community/bluetooth-le/pull/374


[WIP] remove components submodule

This removes the components submodule and compiled css files, instead relying on bower to fetch the dependencies and less to build css.
Running the notebook from master will from now on require npm.
It works already, the only pieces I want to get in before merging are distutils hooks for triggering the npm, bower, and less calls, which I will mostly copy from JupyterHub where this same pattern is already working well.

Continuing in #8.


fontconfig_210: remove package

This removes the fontconfig_210 package, as well as the only remaining usage, the rendering of 2.10.x config and cache.
I switched my system to this, and didn't spot any breakages.
Motivation for this change
Closes https://github.com/NixOS/nixpkgs/issues/88289
Things done

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

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

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

There's a lot more of (now possibly unused) code - there's make-fonts-conf.xsl used to post-massage fontconfigs /etc/fonts/font.conf file to include fontDirectories - and to load files from the versioned subdir.
This is also exposed as makeFontsConf (which seems to be used in various places)
For now I decide to keep this, to not change too much at once, but I assume we might want to remove the configVersion parts in there, too.

Yeah, the XSL stylesheet does two things at once. The reason why it is used in the fontconfig derivation is precisely to introduce the versioned include so we cannot remove the fontconfigConfigVersion variable or fontconfig would no longer load its global configuration.

@jtojnar has there been any breakage reported already, or do you mean you just want to await one staging cycle?

Yeah, the XSL stylesheet does two things at once. The reason why it is used in the fontconfig derivation is precisely to introduce the versioned include so we cannot remove the fontconfigConfigVersion variable or fontconfig would no longer load its global configuration.

I'd propose removing the fontconfigConfigVersion parts from the xslt stylesheet, if the support fontconfig was the only (remaining?) consumer of it. (But in a followup PR after this one)

@jtojnar has there been any breakage reported already, or do you mean you just want to await one staging cycle?

Yeah, I would like to wait one staging cycle, or maybe slightly more since the channels lag a bit behind.

I'd propose removing the fontconfigConfigVersion parts from the xslt stylesheet, if the support fontconfig was the only (remaining?) consumer of it. (But in a followup PR after this one)

The current fontconfig needs it too, since it is the mechanism that makes it load the global config.

We had enough some staging rounds since https://github.com/NixOS/nixpkgs/pull/93562#pullrequestreview-452120074.
Rebased to latest master.

@aszlig You mean, chromium bundles its own version of fontconfig 2.10, which  is still used inside chromium, and it stumbles over our fontconfig version? Wow.
In that case, could we provide a fontconfig 2.10-compatible config (and not build the optional fc caches), so we can keep fontconfig_210 removed?

NixOS module fonts.fontconfig.penultimate still relies on fontconfig_210 and will trip the assertion. I suppose that the code which generates the fontconfig 2.10 caches in that module can be deleted.


Checking/error reporting for undefined or missing subdoc schemas

I've experienced that defining a schema such that:
SchemaBefore = new Schema{"schemaafter": [SchemaAfter]};
SchemaAfter = new Schema{"anyproperty": ...};
brings all to work without errors, but the embedded schema dosn't work as expected.
Obviously this happens because SchemaAfter is not already defined, so it behaves as a ["undefined"]. This leads to wast a big amount of time the first times it happens expecially when combined with code like validators, getters/setters, defaults, and so on.
Is there any reason you do not throw an excpetion for a not defined/undefined subschema property? If someone models their own ODM architecture, then it's really difficult to immagine that he specifies definitions just as a writing exercices. Do you agree? And it could still remain the difference by letting the "anysubdoc": [], still allowed with any futher advice: in this case the intent is maybe clear to the creator.

This is fixed in 3.9.x.


APIs - Technical documentation update

Please revise chapter and subchapters. Divide it to Functionality (description of what is delivered in 1st prototype) and Future work (everything else). Provide links to currently available APIs.

I updated the intro to APIs and added a link to the SPARQL endpoint. Please revise. I believe that other APIs will not be part of the first prototype. Maybe something from Hale?

@Somakanthan are there any APIs that can be added from the Hale Connect/Studio?


ABQM - worker information

Added a node for each worker connected to the Site Composite Node in ABQM; include capacities and capacity_allocations
Added a component node for each component/model pair including capacities and capacity_allocations
Indicate site as Active when a specific worker is in Maintenance including the workers' maintenance state as well

#313

@ibaldin - This also requires changes in user interfacing FIM object CompositeNode to return nodes associated with a Site thus enabling the user to be able to check per worker information.

Currently they are doubled up at the site level and worker level, but we can remove them at site level to avoid duplicacy.


Use healtcheck middleware for Glance

This provides a lighter way to see if glance is up and running.

👍


Data structure in c by great learning

This course contains 2 hours of video lecture focusing on Implementation of Data Structures using C programming language.
https://www.greatlearning.in/academy/learn-for-free/courses/data-structures-in-c

will assign this one later :)
2 pr is already accepted

@avinash201199 PR for this is already accepted. #14

okay then closing the issue


More options for settings

Nice plugin, very promising and useful.
However, would it be possible to add more parameters to the Sublime settings globally, instead of relying on pyproject.toml file being present in the root of the project?
It would be nice to be able to configure it once, and not necessarily as per repository where the toml is located?
It would make sense giving the priority for the pyproject.toml first, then settings.
Many thanks

Have you tried to create a black global configuration file?
https://black.readthedocs.io/en/stable/usage_and_configuration/the_basics.html#where-black-looks-for-the-file

🤦♂
Great tip, many thanks!


Allow onSelectionChanged Callback To Be Aware Of Where Data Came From In a SelectableRegion

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Use case
For selecting Text widgets, often one may need to not only know what text was selected, but where that text came from. Example, a text widget may be backed by data that is intended to change on selection, such as selecting "highlight" from a context menu. Adding this functionality will allow selection changes to be mapped to the correct data.
This is functionality that exists in SelectableText but not with Text widgets inside a SelectableRegion or SelectionArea. SelectableRegion has a callback, but it only provides the text, not where the text came from.
Proposal
A few possible solutions:

It looks like this functionality could be easily added by modifying SelectedContent to also contain a list of widget keys, starts, and end indexes. See SelectableRegion._updateSelectedContentIfNeeded() and _SelectableFrament.getSelectedContent()

This may not be the desired solution since not all Selectables could be Text

A onSelectionCallback could be added to the Text widget and called in the _SelectableFrament.dispatchSelectionEvent() or _SelectableFrament.getSelectedContent()

Having this handler would allow the use of a closure with the widget id (or some other identifier) that is associated with the backing data in order to update the backing data as such.

I already implemented 2 and it works as expected. Happy to create a PR if this is the desired solution.

Went ahead and created a PR for this feature


first stab at android webview support

@Jonahss @imurchie I cleaned this up, reorganized it, fixed a few bugs, and added more comments. Please re-review!

Looks good to me.


[NextJS] Add .gitattributes to Next.js sample app with CRLF line endings

Description / Motivation
The OOTB Next.js sample fails to build on Vercel due to Prettier errors (note this previously worked - Vercel must have changed their build agent OS).

Testing Details

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

@illiakovalenko Could you clarify what's the reason using CRLF in the first place?

@thezaff the problem here was that Next.js app couldn't build in Vercel. build on Vercel due to Prettier errors (Vercel must have changed their build agent OS, when I added this change).


Support lists and tuples as well as dicts.

Lists and tuples will be converted into dicts using enumerate().
This means that a dict such as:
d = {'list': ['a', 'b', 'c',]}
Will be flattened as follows:
flat = {'list:0': 'a', 'list:1': 'b', 'list:2': 'c'}
I also made some indentation changes for consistency.
Resolves #3

Looks good, thanks :)

I just released 1.2.0 to pypi, thanks again!

Thanks Gavin!
On 26 June 2015 at 13:02, Gavin M. Roy<EMAIL_ADDRESS>wrote:

I just released 1.2.0 to pypi, thanks again!
—
Reply to this email directly or view it on GitHub
https://github.com/gmr/flatdict/pull/4#issuecomment-115481796.


Rename server extensions to addons

In hindsight, using the name server extensions was not a good choice as it leads to confusion with VS Code extensions. There's no easy way to refer to them without saying "Ruby LSP server extensions".
Plugin may also lead to confusion given that, in editors other than VS Code, that's often the term used to describe their "extensions". Like Vim plugins.
Let's rename server extensions to addons. The name is descriptive enough and not overloaded with other meanings that could lead to confusion.
This will be a breaking change, but it's better we do this now than after there's a larger ecosystem of gems adding Ruby LSP functionality.

addon or add-on 😁


Fature request: add a warning on clients that don't support knocking, when the room has join_rules knock or knock_restricted

Describe the bug
Matrix.to has ability to know the join_rules of a room (since https://github.com/matrix-org/matrix-spec-proposals/pull/3266), but it doesn't actually warn when a client doesn't support the feature.
To Reproduce
Steps to reproduce the behavior:

Go to a matrix.to URI link which requires knocking e.g. https://matrix.to/#/%23space.piraatit.fi:matrix.org
Open in Element (top option)
In Element attempt to join room
Get error: you are not invited to room

Expected behavior
Matrix.to sees join_rules being knock or restricted_knock and adds a warning to clients that don't support knocking. Knocking is a part of Matrix specification since 1.1 and restricted_knock I hope to soon pass the MSC process.
Screenshots

Desktop (please complete the following information):

OS: Fedora 36
Browser Firefox
Version 101.0b6 (64-bittinen)

Additional context

https://spec.matrix.org/latest/client-server-api/#knocking-on-rooms

(This issue has been heavily edited since the original version)


HDDS-5160. Remove some Freon integration tests

What changes were proposed in this pull request?
Remove some unnecessary integration tests, which exercise Freon generators already widely used in acceptance tests:
https://github.com/apache/ozone/blob/66a411be58843eac7cbc7b32860b494707c9dbd6/hadoop-ozone/dist/src/main/smoketest/freon/generate.robot#L26
https://github.com/apache/ozone/blob/66a411be58843eac7cbc7b32860b494707c9dbd6/hadoop-ozone/dist/src/main/smoketest/admincli/container.robot#L30
https://github.com/apache/ozone/blob/66a411be58843eac7cbc7b32860b494707c9dbd6/hadoop-ozone/dist/src/main/compose/xcompat/test.sh#L58
https://github.com/apache/ozone/blob/66a411be58843eac7cbc7b32860b494707c9dbd6/hadoop-ozone/dist/src/main/smoketest/basic/basic.robot#L35
https://github.com/apache/ozone/blob/66a411be58843eac7cbc7b32860b494707c9dbd6/hadoop-ozone/dist/src/main/smoketest/recon/recon-api.robot#L40
https://github.com/apache/ozone/blob/66a411be58843eac7cbc7b32860b494707c9dbd6/hadoop-ozone/dist/src/main/smoketest/spnego/web.robot#L55
https://issues.apache.org/jira/browse/HDDS-5160
How was this patch tested?
https://github.com/adoroszlai/hadoop-ozone/runs/2460045744

Thanks @elek for reviewing and committing it.


Responsiveness issue - Project page

Bug Description
Go to the project page
Reduce the width to 320px

Steps to Reproduce
Reduce the width to 320px

i want to work on this

All yours @ManishBisht777!! 🚀🚀

Are you still working on this @ManishBisht777?

yes @tobySolutions

yes @tobySolutions, but i am facing some issue while running it on my local

Are you still facing the issues?

yes @tobySolutions, but i am facing some issue while running it on my local

Are you still facing the issues?

yes the site just shows a black screen

yes @tobySolutions, but i am facing some issue while running it on my local

Are you still facing the issues?

yes the site just shows a black screen

Let me check it out on my local machine. GIve me a moment to check it out.

Hey @ManishBisht777, the build is taking so long because of some things that are in the works. I'm so sorry about this, but the server eventually starts, It just takes an unusually long time. You could open this issue while you're at it, that'll really help. Yoy could also use Gitpod for the meantime. If you can't bear it on your local machine.

Are you still on this @ManishBisht777??

Are you still on this @ManishBisht777??

its still showing a black screen even i gitpod

Are you still on this @ManishBisht777??

its still showing a black screen even i gitpod

it did run think I didn't waited enough on the first time

In the development server, things look ok
But on the live site, it seems broken
Live

Dev

Hey @ManishBisht777 ! It seems okay from my end though. Can you check again?

It's still showing like this in my browser

@tobySolutions Can you check your end ?

@tobySolutions Can you check your end ?

Hey @Yagazie-davidson!! It looks good from my end.

This looks fine for me, my browser:  Google Chrome Version 108.0.5359.125.
@ManishBisht777  please could you tell me what browser are you using?

I am using chrome Version 108.0.5359.124 (Official Build) (64-bit)  and firefox version 108

mmmm now its getting weird

now its

Thanks @ManishBisht777  I was able to replicate this, and I think I know what is the issue I will try to work on that now and will open PR if successful

OK an update from me - basically this issue is caused by width set to the projects  which is set to 30ch. If this width property will be removed, it will cause text wrap for longer titles and the cards heights will be different

That's it from me for now on that issue, It would be great if someone could test this wit actual mobile devices as i suspect that this issue may be only occurring in developer tools, not on actual devices.

Hey @KarolSongin, yes I did test it and the issue only occurs on the developer tools, not on actual devices. I've tested it on quite a few devices and I don't seem to be getting the issue on my end.
Do you think this issue should be closed?

Hey @KarolSongin, yes I did test it and the issue only occurs on the developer tools, not on actual devices. I've tested it on quite a few devices and I don't seem to be getting the issue on my end.
Do you think this issue should be closed?

same for me. I tested it on mobiles and it works fine I think you can close this issue

Hey @KarolSongin, yes I did test it and the issue only occurs on the developer tools, not on actual devices. I've tested it on quite a few devices and I don't seem to be getting the issue on my end.
Do you think this issue should be closed?

Yes i think in that case if this was tested on actual devices this can be closed.


GetSaveFileNameInput projects dialog focuses Create External File and not Save

Version and Platform (required):

Binary Ninja Version: 3.6.4812
OS: Windows
OS Version: 10
CPU Architecture: x64

Bug Description:
When I tried to save a file via GetSaveFileNameInput, the Create External File button is focused instead of Save, so typing the file name and pressing enter starts trying to create an external file instead of accepting my input.
Steps To Reproduce:

Call function
Type text
Press enter
Confusion

Expected Behavior:
I expected pressing enter to accept my changes and close the dialog

Fixed in 3.6.4813-dev


islands adapt  deno workspace

If deno workspace is used, islands will not function.
For example, the following error is shown.
Error: Build failed with 1 error:
components/Button.tsx:2:27: ERROR: [plugin: deno-resolver] specifier was a bare specifier, but was not remapped to anything by importMap.
    at failureErrorWithLog (https://deno.land/x/esbuild@v0.20.2/mod.js:1626:15)
    at https://deno.land/x/esbuild@v0.20.2/mod.js:1034:25
    at runOnEndCallbacks (https://deno.land/x/esbuild@v0.20.2/mod.js:1461:45)
    at buildResponseToResult (https://deno.land/x/esbuild@v0.20.2/mod.js:1032:7)
    at https://deno.land/x/esbuild@v0.20.2/mod.js:1061:16
    at responseCallbacks.<computed> (https://deno.land/x/esbuild@v0.20.2/mod.js:679:9)
    at handleIncomingPacket (https://deno.land/x/esbuild@v0.20.2/mod.js:739:9)
    at readFromStdout (https://deno.land/x/esbuild@v0.20.2/mod.js:655:7)
    at https://deno.land/x/esbuild@v0.20.2/mod.js:1974:11
    at eventLoopTick (ext:core/01_core.js:168:7) {
  errors: [Getter/Setter],
  warnings: [Getter/Setter]
}

In the case of building multiple fresh applications in a single repository, the availability of this feature should be very useful.
We would like to be able to use it.

Hello @Octo8080X :)
fix: #2615

Please follow this step.

Update importMap.json with correct mappings.

Add importMap to deno.json.

Verify imports in your files.

Use importMap in Deno commands.

Update Deno to the latest version.

is there actually a way to fix this? those steps do not work.

I'm also getting the same issue:
The manifest has been generated for 2 routes and 0 islands.
X [ERROR] specifier was a bare specifier, but was not remapped to anything by importMap. [plugin deno-resolver]

    https://deno.land/x/fresh@1.6.8/src/runtime/entrypoints/signals.ts:1:23:
      1 │ export { signal } from "@preact/signals";
        ╵                        ~~~~~~~~~~~~~~~~~

X [ERROR] specifier was a bare specifier, but was not remapped to anything by importMap. [plugin deno-resolver]

    https://deno.land/x/fresh@1.6.8/src/runtime/entrypoints/main.ts:13:7:
      13 │ } from "preact";
         ╵        ~~~~~~~~

error: Uncaught (in promise) Error: Build failed with 2 errors:
https://deno.land/x/fresh@1.6.8/src/runtime/entrypoints/main.ts:13:7: ERROR: [plugin: deno-resolver] specifier was a bare specifier, but was not remapped to anything by importMap.
https://deno.land/x/fresh@1.6.8/src/runtime/entrypoints/signals.ts:1:23: ERROR: [plugin: deno-resolver] specifier was a bare specifier, but was not remapped to anything by importMap.
  let error = new Error(text);
              ^
    at failureErrorWithLog (https://deno.land/x/esbuild@v0.20.2/mod.js:1626:15)
    at https://deno.land/x/esbuild@v0.20.2/mod.js:1034:25
    at runOnEndCallbacks (https://deno.land/x/esbuild@v0.20.2/mod.js:1461:45)
    at buildResponseToResult (https://deno.land/x/esbuild@v0.20.2/mod.js:1032:7)
    at https://deno.land/x/esbuild@v0.20.2/mod.js:1061:16
    at responseCallbacks.<computed> (https://deno.land/x/esbuild@v0.20.2/mod.js:679:9)
    at handleIncomingPacket (https://deno.land/x/esbuild@v0.20.2/mod.js:739:9)
    at readFromStdout (https://deno.land/x/esbuild@v0.20.2/mod.js:655:7)
    at https://deno.land/x/esbuild@v0.20.2/mod.js:1974:11
    at eventLoopTick (ext:core/01_core.js:175:7)

Getting same error with Deno 2.0

This is likely caused by a bug in Deno. See https://github.com/denoland/deno/issues/26138


auto_route implementation

#43

Is this how I link this to the Issue ?

I'm new to flutter, how do I fix the tests ?

Looks like the failing tests come from the two conflicting error members in the view model

Also looks like auto_route broke on flutter version 1.20.0, which makes me think the dependency might not be worth while, if it breaks on every new flutter version.

I closed the other PRs. I had to fix the github action test. So i just went ahead and updated the dependencies and fixed the errors. Feel free to rebase and continue working on adding auto_route.


Proxy can now use QUIC for upstream connections

1. What does this change do, exactly?
Adds QUIC proxy support for upstream connections.
2. Please link to the relevant issues.
#999
3. Which documentation changes (if any) need to be made because of this PR?
Yes, updating the proxy command in Caddyfile to include a QUIC scheme: quic://. This is identical to https:// but using QUIC.
Using this feature does not require the proxy to use the -quic flag, but the server still has to!
4. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I am willing to help maintain this change if there are issues with it later

I will write tests at a later point (September maybe).
Note: when updating go-quic, h2quic.QuicRoundTripper should change to
h2quic.RoundTripper

Fyi: this does not work (yet) when the upstream server pushes something to the proxy.

Thanks for your work on this, @twdkeule ! Also on the upstream quic-go library, we all really appreciate it. I'll be looking at this soon!

Just a quick update that receiving server pushes will probably not be supported in the near future as even the HTTP/2 implementation of the Go standard lib does not support it yet.

Tests would prove really helpful here, especially as I prepare to rewrite the proxy middleware; I would hate to see my rewrite break this change. Do you want someone to help you write the test for it?

I really don't have the time to write tests until the end of August. But anybody is free to write them :wink:

I added a test to check if a QUIC RoundTripper was created.
Does the repo have an integration test suite? Because it would be good to run a test where 2 Caddy servers use QUIC to communicate.

@twdkeule Thanks for working on it! I don't have a suite of integration tests set up quite yet, but it's not that hard to add one already; we do this for other kinds of proxying if you look at the other Test functions. Just spin up a server on some port (that's configured to use QUIC) and then proxy a request to it through ServeHTTP. You don't have to spin up a whole Caddy instance, per-se, just a QUIC server.
Checking for the RoundTripper is a good start. Would you want to try the other test that actually makes sure proxying QUIC works? ;) (I would highly, strongly recommend it!)
By the way:

Note: when updating go-quic, h2quic.QuicRoundTripper should change to h2quic.RoundTripper

What do you mean by this? Should we just update go-quic in our vendor folder with this PR?

Yes, I'll definitely add that test. Maybe next week.
You can ignore that comment. You already updated quic-go sufficiently I'm the last vendor update :-)

Gotcha. Cool. An "integration" test should just be a few lines of code, I think. Looks like this is all you need to set up the QUIC server (taken from quic-go's readme):
h2quic.ListenAndServeQUIC("localhost:4242", "/path/to/cert/chain.pem", "/path/to/privkey.pem", nil)

I vendored in the certificate from quic-go to run the quic server

@twdkeule Cool, almost there! The tests are failing because "cannot bind requested address" - likely because a test server is not being shut down or we are re-using the same address? Do the tests pass locally for you?
Anyway, if I understand this properly, once the tests pass, we can merge this PR and deploy this in 0.10.7. Is that right?

The tests run successful locally.
I don't stop the goroutine running the QUIC server, but that should stop after the test.go file is finished, no?
I changed the port number just in case.

OK, the tests are a succes.
@mholt this is ready to merge

Thanks @twdkeule for tackling the tests. Sorry about the quic-go tests having troubles. This is a recent thing that changed upstream. I'd rather not add test dependencies to the vendor folder if we can avoid it. Do you have any idea what caused the problem? We're discussing it in https://github.com/lucas-clemente/quic-go/issues/797 in case it can be fixed there, rather than adding test baggage to the vendor folder.

Okay, updating the CI to Go 1.9 fixed the issue. @twdkeule if you could undo your changes to the vendored folders and only include the changes for your PR, then we can merge this. If it happens early enough today, it's likely to go out on the release I'm planning.

@mholt The Travis tests are succesful now, but Appveyor cannot find the file.
I don't have a Windows machine for Go development, so I'm not sure what the problem is.
Go should handle / correctly as path separator, right?

Oh. Then I was wrong. 😅 Maybe moving the certs I to a local folder is
still a good way to do it...
On Fri, Aug 25, 2017, 10:58 AM Christine Dodrill<EMAIL_ADDRESS>wrote:

@Xe commented on this pull request.
In caddyhttp/proxy/proxy_test.go
https://github.com/mholt/caddy/pull/1782#discussion_r135305652:

if err != nil {

t.Errorf("Expected no error. Got: %s", err.Error())

}
p := &Proxy{

Next:      httpserver.EmptyNext, // prevents panic in some cases when test fails

Upstreams: upstreams,

}

// start QUIC server
go func() {

dir, err := os.Getwd()

if err != nil {

	t.Errorf("Expected no error. Got: %s", err.Error())

	return

}

certDir := path.Join(dir, "../../vendor/github.com/lucas-clemente/quic-go/example/")

The windows API's take both forward and backslashes
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mholt/caddy/pull/1782#discussion_r135305652, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABE5kWgtpIwjxnUrFmYPKztZuFgUqzcXks5sbv0jgaJpZM4OjsDC
.

@twdkeule The vendor folder does not include test dependencies (this is intentional).

Maybe it's easier to use a public website we know uses QUIC

@twdkeule Maybe, but then we'd have external network dependencies for the tests. I bet we can just move the certificates into a local test folder for proxy and get them to work. :)

Wow, this is looking better. Thank you for the changes! I will do another review this week!

Sorry, I've gotten a little delayed...

Looking forward to the release. Awesome.

@twdkeule I just realized after running the tests locally that the certificate chain is a real one (I didn't bother to decode it in the code review, oops) that expires on October 17, and that the hosts file must direct quic.clemente.io to localhost. For now, I've disabled that test outside of CI environments, and later, we'll have to update it every 3 months or just disable it entirely after October 17. Is there a more permanent or low-maintenance way of testing connections to QUIC upstreams? (pinging @marten-seemann in case you have any ideas as well!)

As far as I am aware, the QUIC server needs a certificate to start.
We could use a self-signed certificate with a 5 year validity, but also only on a  CI environment as we need to add it to the trusted certificates. Unless insecure-skip-verify works with quic-go

tls.Config.InsecureSkipVerify works with QUIC.
Alternatively, you could generate a CA certificate, sign the server public key with that and use it in the tls.Config.ClientCAs cert pool.

Thanks, I fixed the tests easily enough in cccfe3b4efb45b443dcbef9ab26a4ec4ffb46eab by your suggestion.


attribute full_name on resource harbor_robot_account

How to access attribute "full_name" on resource harbor_robot_account as described in the documentation : https://registry.terraform.io/providers/BESTSELLER/harbor/latest/docs/resources/robot_account
harbor_robot_account.myrobot.full_name does not work.

Hi,
with latest provider harbor_robot_account.myrobot.full_name works
for eg :
resource "harbor_robot_account" "system" {
  name        = "toto"
  level       = "system"
  secret      = "Test123181erb"
  permissions {
    access {
      action   = "create"
      resource = "labels"
    }
    kind      = "system"
    namespace = "/"
  }
}

output "test" {
  value = harbor_robot_account.system.full_name
}

harbor_robot_account.system: Modifying... [id=/robots/3]
harbor_robot_account.system: Modifications complete after 0s [id=/robots/3]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

Outputs:

test = "robot$toto"

I close the issue feel free to re-open it if needed


Feature: swipe ui

Description of changes:
Attempt to integrate feature/swipe-support into new fullscreen layout
Related issues (if any):

Consider adding touch support (#15)
Swipe with transition (#99)

Checks:

[ ] Please confirm npm run lint ran successfully
[ ] Please confirm that only /src and /examples/src are committed
[ ] [if new feature] Please confirm that documentation was added to the README.md

@jkettmann we've both made pretty dramatic changes to the codebase. I tried to merge the two branches by hand but was unsuccessful. Is there any chance you could help?

Hi @jossmac, of course. I'll have some time the next days. I'll keep you posted

@jkettmann that's terrific, thank you!
I'm struggling a bit with the new <SwipeContainer /> component. I haven't implemented anything using react-motion, so it's unfamiliar territory. There's also some decisions that I don't understand, like providing 'data:' to the <img /> when it's NOT visible?
I'm likely just missing something obvious; perhaps some code comments would help.

I made my changes now and pushed to my forked feature/swipe-ui branch. I'm not sure how the workflow is continuing now. Should I just create a pull request from my forked branch to feature/swipe-ui?
Anyways:
LightBox now only uses SwipeContainer, so we also have horizontal animation on non-mobile devices. The name SwipeContainer seems a bit confusing in this way.
I'm not totally sure why setting source to something for non-visible images was important, but '''data:''' seems to be wrong. As far as I remember I did that because of performance issues: SwipeContainer is a wrapper around all images, so it's '''windowWidth * imageCount''' wide. If all image sources would be set, this would cause memory problems when there are a lot of and/or large images. So we need to unset sources of non-visible images. One way of doing that is like in this answer.
On mobile devices there is a small issue now, because the user cannot close the LightBox if he is not active anymore.

Thank you @jkettmann, I appreciate you diving back into this

Yes, please create a new pull request from your branch to feature/swipe-ui
In my manual merge attempt I had intentionally forked the behaviour on touch vs desktop devices, I feel that having the image replaced in situ (with the loading indicator when applicable) feels more responsive on desktop. Are you cool with that?
The solution on StackOverflow seems fine, though perhaps I'm missing the problem. Can't we request the image (or two) ahead of the direction the user is headed rather than load them all at once?
I'll look into the userIsActive issue when this is merged; should be fine with the forked behaviour mentioned above

Hi @jossmac

done
that's fine by me. I just like to have an animation on desktop too. Otherwise it looks kind of static to me. I removed Desktop behaviour in the second commit I guess
Yes, actually I remember seeing that. I'm not sure, if there is any reason to use my implementation as well. I'll look into that.

when will this be added to master? thanks

if @jkettmann could fix the conflicts i can look at merging it, otherwise i'll look at it when i can.

@neptunian I'll probably have some time at the weekend

Hi, just a small update: I didn't find enough time on the weekend. I'll let you know soon

@jkettmann is this merge for two different features?  full screen and swipe?

@neptunian It's been quite some time, but as far as I remember it was something @jossmac was working on and we merged the two behaviors into this branch. But I'm not really sure

@jkettmann do you recall the reason for that?  otherwise it seems like it'd be easier to separate these features out for simplicity's sake.

@neptunian No I don't remember a reason. You're right, it would be easier to separate them.

@neptunian I resolved the conflicts. Should I create a pull request to feature/swipe-ui or somewhere else?

@jkettmann i think we should probably keep it on this branch instead of starting over and separating things.  perhaps @jossmac will be able to pick up where he left off again.  Did you ever look into #3 that you mentioned above with loading of the images one or two ahead instead of loading them all?

@neptunian Sorry it took me so long. I created a new (pull request)[https://github.com/jossmac/react-images/pull/158], because this branch is already quite messed up. You would have to resolve the conflicts yourself. If you would like me to change something just tell me.

Would love to use this component as soon as touch support is added!

I would like to use swipe function in current version ... is it gonna be possible?

addressed in https://github.com/jossmac/react-images/issues/199


Close out post-mortem for 502 incident

We hypothesize that what happened on 2021-03-05 will happen again, and soon. When it does, we need to be sure our site is resilient.
Potential work to do. Discuss with team how much of it we can take on:

[x] Obtain support from AWS for more details on IPs involved (time limit effort here if they're not helpful)
[ ] Share details on incident with GSA-IR and US-CERT
[ ] Follow up with one detailed report to abuse@cloudproviders (make sure we're using the right channel/email)
[x] Prepare selection of "Protect" technical measures, the relative effort and impact
[x] Prepare selection of "Detect & Respond" technical measures
[x] Hold another meeting to review and decide on measures.
[ ] Post a public incident post-mortem with steps we're taking
[ ] Ship an incident post-mortem to JAB TRs, with POA&Ms for the steps we're taking

This ticket needs grooming by the Engineering Huddle....
Incident notes:
Incident PM meeting

We met on 2021-04-09, with our notes in the same document as before.
@bengerman13 and @mheadd are working on the full writeup.
A redacted write-up willl go on Statuspage once the mitigation work is complete. The full write-up will go to the JAB, GSA-IR (and thence to CERT).
We can close this once:

[ ] the full write up is shipped to the JAB
[ ] Peter has checked on the current CloudFront status with the JAB
[ ] The engineering team has tickets in the backlog for the next steps.
[ ] We have a POA&M created for that same work.

Draft incident post-mortem statements are here.

Action item tickets and PRs:
cloud-gov/logsearch-for-cloudfoundry#86
cloud-gov/cg-deploy-cf#541
cloud-gov/cg-provision#821


NameError: uninitialized constant IssueOpenWorker

Redmine 3.4.6.stable
Invoking from cron:
rake issue_open_date:switch --silent RAILS_ENV="production" --trace
got this stacktrace

** Invoke issue_open_date:switch (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute issue_open_date:switch
rake aborted!
NameError: uninitialized constant IssueOpenWorker
/home/redmine/plugins/redmine_issue_open_date/lib/tasks/issue_open_date.rake:3:in block (2 levels) in <top (required)>' /var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/task.rb:271:in call'
/var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/task.rb:271:in block in execute' /var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/task.rb:271:in each'
/var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/task.rb:271:in execute' /var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/task.rb:213:in block in invoke_with_call_chain'
/usr/lib/ruby/2.1.0/monitor.rb:211:in mon_synchronize' /var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/task.rb:193:in invoke_with_call_chain'
/var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/task.rb:182:in invoke' /var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/application.rb:160:in invoke_task'
/var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/application.rb:116:in block (2 levels) in top_level' /var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/application.rb:116:in each'
/var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/application.rb:116:in block in top_level' /var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/application.rb:125:in run_with_threads'
/var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/application.rb:110:in top_level' /var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/application.rb:83:in block in run'
/var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/application.rb:186:in standard_exception_handling' /var/lib/gems/2.1.0/gems/rake-12.3.1/lib/rake/application.rb:80:in run'
/var/lib/gems/2.1.0/gems/rake-12.3.1/exe/rake:27:in <top (required)>' /usr/local/bin/rake:23:in load'
/usr/local/bin/rake:23:in `'
Tasks: TOP => issue_open_date:switch

tried develop branch but no luck

Hello!
Please, try fix-worker-autoload branch


[WIP] PAGE-ANN: annual timesteps in the model.

Several, but not all, modules of PAGE have been annualised, by creating a new Index(), with new variables based on this.
Open standing points to resolve, before considering if we would want to merge this in (feel free to work on this if you would like @jrising @P-Wlich ):

[ ] Update test-suite to include all tests for annual variables as well
[ ] Make a decision on what interpolation to do; (a) choose one and remove the options, or (b) move the options into the getpage() call
[ ] Make a decision on whether or not to annualise more modules than just the ones following ClimateTemperature. Especially consider if combining growth effects would impact this decision.
[ ] ... add more points as you see fit ...

Thanks for sharing this. I like that you've set this up so that it keeps the timestepped variables unchanged.
Ultimately, the right way to set this up the annual code would be to create your annual changes as separate components, which would take any necessary timestep variables as inputs. That way, one could get the timestep results by just including those components, and with both sets of components get the annual model. It would also make clearer where there are real dependencies between the timestep variables and the annual ones, vs. that the two are just computed in parallel.

That would also make it so that your unit tests wouldn't fail. You currently have an error because you haven't defined y_year_ann in some of them.

This PR is outdated, work has continued in #46


Node disappears in network multiplayer on physics collision and game crashes

Godot version:
3.0.6.stable.official.8214054
OS/device including version:
Ubuntu 18.04 64bit
Issue description:
If I run my game on two PCs across my WiFi, if two units cause a physics collision with each other, one of the units just disappears from both clients (I have not coded any such behavior). Most of the time, the client will become disconnected from the server soon after that.
The trigger is: setting the scale of a RigidBody with rset_unreliable("slave_scale", self.scale) and self.scale = self.slave_scale.
If I run two instances of my game on the same PC and test multiplayer that way, this does NOT happen. Happens only on a real network, cable or wireless.
I am aware that Godot doesn't want RigidBodies to be scaled, or just resets the scale to (1, 1, 1). That's okay if there is a good reason for that. But it should not behave in such an erratic way, without a specific error.
Steps to reproduce:

Run the game on two PCs
Host. Join on IP. Start.
Move the starting unit of each player towards each other until they collide. Select with left click, move with right click.
Disable slave setting of scale on the following lines and see that the error doesn't happen anymore:
4.1 https://gitlab.com/ScyDev/Critically-Entangled/blob/debugging/physics-collision-with-slave-scale-crashes/godot-project/Unit.gd#L57
4.2 https://gitlab.com/ScyDev/Critically-Entangled/blob/debugging/physics-collision-with-slave-scale-crashes/godot-project/Unit.gd#L102
4.3 https://gitlab.com/ScyDev/Critically-Entangled/blob/debugging/physics-collision-with-slave-scale-crashes/godot-project/Unit.gd#L106

Minimal reproduction project:
Use this tag of my project: https://gitlab.com/ScyDev/Critically-Entangled/tree/debugging/physics-collision-with-slave-scale-crashes

@ScyDev you have slave var slave_scale = Vector3() (i.e. 0 scale by default).
This gets assigned to the objects scale at some point, which seems to make physics angry (causing the ERROR: move: Condition ' Math::is_nan(p_aabb.size.x) ' is true. spam).
Change that to slave var slave_scale = Vector3(1,1,1) (i.e. scale 1 by default) and the error goes away.
Not sure if this is an actual bug (are 0 scaled elements allowed in physics?) but in case my guess is that it's more a physics bug then a network one.

@AndreaCatania ?

There was no follow up, but yes, using a scale of 0 is definitely going to lead to issues with physics and rendering. The editor should now prevent it to some extent / raise warnings.

@Faless Thanks a lot!


Cant Pass event inventory click event to crazyenchantments

I recently added a new gkit to the gkits file and there are no errors when starting my server. The gkit is called Viking and i can right click it to view what is in the gkit though when i try and left click the gkit i get an error in the console. This only happens with the new Viking gkit i added.   This is the error
https://pastebin.com/PQAUPRmT

https://pastebin.com/5Hvz2023 Also this is my gkits file

So if you know why i am getting the error and can not get the gkit please let me know

I still have no idea why i am getting this error i even tried remaking the gkit incase i did something wrong and im still getting the error when trying to use the gkit

It seems one of the enchantments you put was not named right. Can you pastebin the enchantments.yml and customenchantments.yml.

https://pastebin.com/6NNbr1tk
And
https://pastebin.com/vrYXY60c

Try this for the gkit file.
https://pastebin.com/4dvcDRs1

It works what did you change?

Lol, changed Honeyhearts to HoneyHearts


Sources folder

Allow the sources folder to be controlled with a command line argument when starting the kernel.
Add in a setup phase that ensures that all services source directories are created on boot.

Done in commit 33b94a1487237f3189324840d04566e211fd1737


Docs - add an example to the i18n custom labels section

Description
- What does this PR change? Give us a brief description.
This PR adds some more detail to the "Extend translation schema" section of the i18n guide by adding an example of how to use the new custom label inside a component. indeed, as i was going through this process on my project, it took me a while to understand that I needed to use the labels props. I thought it could be a useful addition to the Starlight docs.
- Did you change something visual? A before/after screenshot can be helpful.
Yes. I added a <Steps> components and a code block. See screenshots.
Before

After

I hope it's helpful.
Thank you,
Geoffrey
P.S. Sorry, I don't know why there are updates to settings.json and 'package.json`.

Hello! Thank you for opening your first PR to Starlight! ✨
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any issues you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Netlify 🤩

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

en
guides/i18n.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Thanks for this @BuckyBuck135! Going to check with @HiDeoo but we are planning to change how this works in #1923, so it might not make sense to add this information at this point (although it is very useful!)

Indeed, as part of #1923, the documentation will now contain a brand new "Accessing UI strings" section (still a work in progress) that will explain how to access UI strings using the new approach and all the helper functions that will be available.

Considering the current progress, I agree with Chris that we can potentially skip documenting and translating the old approach at this point.
I'll close this PR but thanks for the contribution nonetheless and also spotting an area that definitely needed improvement! :raised_hands:
I hope the new approach and its documentation will be more helpful when it's ready, and feel free to take a look at the link I shared above to let us know if you have any feedback or suggestions.

That new doc looks very promising and perfectly conveys the example I was trying to give.
Thank you both for your technical and communication skills. Keep up the great work.
I'll find another way to get my first contributor alert :)


Add a domain name if not present in a vm's name

Tested and works for me...
Purpose explained in #355
Two new params. Intended to handle these types of things:

shortname -> shortname.example.com (add domain)
foo.site1 -> foo.site1.example.com (add domain)
foo.site2.example.com -> foo.site2.example.com (no change)
foobar.example.net -> foobar.example.net

For when names in vCenter have an implied domain if not included.

Hi,
This would be a great addition. I'm afraid that it would not cover the case where one would only assign a missing domain to certain VMs. Could you change it to work the same way as existing relations?

You mean something like this?
vm_domain_name_relation = ^[a-z]\.foo$ = example.net, ^[a-z]-bar$ = example.com

Replacing simple add_vm_domain_name with:
vm_domain_name_relation = .* = example.net

Should that still have the keep_vm_domain_name_filter regex param to skip things that already have a domain name on them?

Sorry @eric-eisenhart I missed your comment.
the first example looks good to me. Would need to craft your config precisely. And if the relation matches but the correct domain name is already part of the VM name then it would not add the domain name again.
What do you think?


adds docker-compose for postgres database

there is also this duplication https://github.com/lnbits/lnbits-legend/pull/355


layernorm_forward kernel#1 with copy compute overlap is 3x faster than kernel#5

I added a layernorm_forward kernel, #6, which just applies the copy compute overlap to kernel#1. It turns out that these kernels were heavily memory bound & dominated by the host to device & device to host memory copies. I modified the benchmarking code to include memory copy operations. Applying the copy compute overlap to any of the other kernels is as easy as modifying kernel#6, just change the kernel number in the kernel launch line. Here is the script that generated the data used in the writeup.
for b in {8,32,128,512}
do
     ./layernorm_forward 5 $b
     ./layernorm_forward 6 $b
done

I've prepared a little overview of the work with profiles, graphs, & the raw data.

Working on making a clang format file that makes the diff less dramatic. I couldn't find any standards when I search the repo, but I'll at least match the indents & use snake case (if that's what's generally used).

There was this PR: https://github.com/karpathy/llm.c/pull/270

Thanks Ross!

unfortunately, the diff is currently not really readably, so I might have just misunderstood something, but this seems to optimize for a non-existent use-case?
For any actual computations, all the kernels inputs and outputs will be buffers in GPU memory; no memcpy operation will be involved. As such, it is deliberate that the benchmarking code excludes any memcopies.
Btw, even with all the data in GPu memory, the kernels are still heavily memory bound regarding GPU-RAM to SM memory transfers ;)

Hah, that makes sense, I wondered if that might be the case. Do you have anything similar to point me at? If not similar anything in general you want help with?


The content in the text_unit_ids column of create_final_communities.parquet doesn’t seem quite right.

Do you need to file an issue?

[X] I have searched the existing issues and this bug is not already filed.
[ ] My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
[ ] I believe this is a legitimate bug, not just a question. If this is a question, please use the Discussions area.

Describe the issue
While reviewing the contents of create_final_communities.parquet, I noticed that for each community, the text_unit_ids is a list. Upon further inspection, I found that each element in the list is not a single UUID string but a string made up of multiple UUIDs separated by commas. Is this the expected behavior?

Steps to reproduce
No response
GraphRAG Config Used
# Paste your config here

Logs and screenshots
No response
Additional Information

GraphRAG Version:
Operating System:
Python Version:
Related Issues:

This is correct. Communities are made up of the entities from many text units, so we store the list as "metadata" for possible backreferencing. It is not directly used, so we packed it into a single delimited string rather than a more complex normalized structure.


Finished Issue 106

The tests should be working and the components are all there.

If you want to this is a good opportunity to figure out how to merge these in. Kayla or I can walk you through it.


Wrong return type inference with the Union of Literal types

TypeScript Version:  2.2.0
Code
type T = 'a' | 'b'

const f1 = () => true ? 'a' : 'b'
const f2 = () => true ? 'a' : 'a'

const v1: T = f1()
const v2: T = f2()

Expected behavior:
Both will be ok.
Actual behavior:
Only the former is ok.
index.ts(7,7): error TS2322: Type 'string' is not assignable to type 'T'.

Minimal repro
const f = () => 'a' // inferred type f: () => string
const v: 'a' = f()  // Type 'string' is not assignable to type '"a"'

This is working as intended. See discussion here for the rationale.


Handling imported files

[x]  Try out the .import folder at root of mod folder approach

That would save use from rewriting the .import files

Works fine 👌

Now do we want to add the mods import files right into the games .import folder.
Or keep it separated and close to the mod folder?
I think it’s fine to copy them in the base .import folder

It’s the default spot for imported files
The files are hashed so there should be no overwrite issues?
Whit that we just need to copy the files into the mods .import and don’t have to mess with rewriting the .import file of each import.

Just for reference here is the first / current approach

Check if there is a _import folder in the root of the mod folder

Copy everything inside the import folder into res://.import

I forgot about this part 😅

This file system is read-write only when running the project locally from the editor. When exported or when running on different devices (such as phones or consoles, or running from DVD), the file system will become read-only and writing will no longer be permitted.
[*https://docs.godotengine.org/en/stable/tutorials/scripting/filesystem.html#resource-path*](https://docs.godotengine.org/en/stable/tutorials/scripting/filesystem.html#resource-path)

So the only option then is to rewrite the .import files?

Rewriting the .import files
[remap]

importer="texture"
type="StreamTexture"
path="res://.import/CheckedBox.png-2de33354470b091a4ff1e85a8aa8163f.stex"
metadata={
"vram_texture": false
}

[x]  Search mod directory for .import files
[x]  Open File
[x]  Replace path with “res://modFolderName/_import/filename.something”
[x]  Save File
[x]  ez

Closed by https://github.com/GodotModding/mod-loader/pull/10


fix exclusion of gson

amends #456 to fix the exclusion  as noted by @basil
Testing done

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

https://issues.jenkins.io/browse/JENKINS-72857?

That would have been https://github.com/jenkinsci/google-compute-engine-plugin/pull/456  (as the dependency is closer to the api plugin the exclusion is more for clarity and to prevent accidental promotion in the future should it be changed in the libraries we are pulling in).


New version: HDF5_jll v1.12.1+0

Autogenerated JLL package registration

Registering JLL package HDF5_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/HDF5_jll.jl
Version: v1.12.1+0
Commit: b668f05a34947a64b3fefc160a19b288c2ad3d15
Revision on Yggdrasil: https://github.com/JuliaPackaging/Yggdrasil/commit/0b200463f814a4b432bcc119f68ad45ab5c3bff6
Created by: @giordano

Pause, I want to do some tests before merging


When using the Tabs component, there is no line break on the mobile phone

Description
When using the Tabs component, there is no line break on the mobile phone

Can you elaborate? Your screenshot hasn't been uploaded. Would you mind providing a reproduction?

Can you elaborate? Your screenshot hasn't been uploaded. Would you mind providing a reproduction?

So you're talking about the prose component Tabs from Nuxt UI Pro?

So you're talking about the prose component Tabs from Nuxt UI Pro?

Yes

Are you in a fork of the @nuxt/ui documentation? If so, it's not related to the Tabs component but instead our custom ComponentExample component that misses an overflow-x-auto.

overflow-x-auto

When I use the ContentRenderer component, how do I customize overflow-x-auto to the Tabs component?
`{"type":"root","children":[
{"type":"element","tag":"tabs","props":{},"children":[
{"type":"element","tag": "div","props": {"label": "One"},"children":[{"type":"text","value":"One"}],
{"type":"element","tag": "div","props": {"label": "Two"},"children":[{"type":"text","value":"Two"}],
{"type":"element","tag": "div","props": {"label": "Three"},"children":[{"type":"text","value":"Three"}],
{"type":"element","tag": "div","props": {"label": "Four"},"children":[{"type":"text","value":"Four"}],
{"type":"element","tag": "div","props": {"label": "Five"},"children":[{"type":"text","value":"Five"}],
{"type":"element","tag": "div","props": {"label": "Six"},"children":[{"type":"text","value":"Six"}],
{"type":"element","tag": "div","props": {"label": "Seven"},"children":[{"type":"text","value":"Seven"}],
]}
],"toc":{}}`

Are you in a fork of the @nuxt/ui documentation? If so, it's not related to the Tabs component but instead our custom ComponentExample component that misses an overflow-x-auto.

When I use the ContentRenderer component, how do I customize overflow-x-auto to the Tabs component?
{"type":"root","children":[

{"type":"element","tag":"tabs","props":{},"children":[

{"type":"element","tag": "div","props": {"label": "One"},"children":[{"type":"text","value":"One"}],
{"type":"element","tag": "div","props": {"label": "Two"},"children":[{"type":"text","value":"Two"}],
{"type":"element","tag": "div","props": {"label": "Three"},"children":[{"type":"text","value":"Three"}],
{"type":"element","tag": "div","props": {"label": "Four"},"children":[{"type":"text","value":"Four"}],
{"type":"element","tag": "div","props": {"label": "Five"},"children":[{"type":"text","value":"Five"}],
{"type":"element","tag": "div","props": {"label": "Six"},"children":[{"type":"text","value":"Six"}],
{"type":"element","tag": "div","props": {"label": "Seven"},"children":[{"type":"text","value":"Seven"}],

]}

],"toc":{}}


Use correct language code for Dutch Informal

nl_di is not an actual language code. It just needed to be different on
Crowdin. You will either require this package for an informal way or the
"normal" Dutch language pack
(https://github.com/mageplaza/magento-2-dutch-informal-language-pack)

we're not using this package anymore.


Fix flaky TestDNS case

DNS resolve error could happen in UDP protocol with error:
=== RUN   TestDNS/udp-success:_non_k8s_host_not_in_local_cache
dns_test.go:221: Failed to resolve query for www.bing.com.: dns: overflowing header size
This change increases the UDP receive buffer size.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[X] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @l8huang. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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

Hi @l8huang. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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

/ok-to-test

/ok-to-test

@l8huang: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
597d72191b4c9e118b66736287d4cf0efb48dc18
link
/test release-notes_istio

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

@l8huang: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
597d72191b4c9e118b66736287d4cf0efb48dc18
link
/test release-notes_istio

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

/test release-notes_istio

/test release-notes_istio


update strings sorting and readme

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


Add support for Windows clipboard history (Win+V) in bash

Add support for Windows clipboard history activated by Win+V in bash.

When running PowerShell, paste from clipboard history works ok.
When running bash in its own window (i.e. not using Window Terminal, from MSYS2 project or Git), paste from clipboard history works ok.
When running bash in Windows Terminal window (in any way - C:\Windows\System32\bash.exe, from Windows Subsystem for Linux, executable from Msys2, ssh connection to a Linux machine) and paste from clipboard history is activated, it does nothing for the first time and it prints ^V for the second time.

Version
Windows Terminal Preview, Version: 1.16.2642.0

Do you have ctrl+v bound to paste in your settings/? Clipboard History works by just sending a literal ctrl+v key to the window, so if that's not bound to paste, then it won't work for pasting.

@zadjii-msft It is annoying to bind ctrl+v to paste while using vim. Vim default bind ctrl+v to toggle visual block mode which is very useful. Is there any workaround to make clipboard history work without editing the default key binding in vim?

This is just a quick thought, but you might be able to bind ctrl+v to multipleActions([paste, sendInput('^V')]), so that when Terminal recieves a Ctrl+V, it both pastes, and sends a literal ^V to the client application (that vim can read).

Thank you for your advice.
It seems that everything is fine if I bind ctrl+v to send \u0016 (which is the corresponding Unicode of ^V). Vim and clipboard history work well under Windows terminal.
But still don't know why I have to do such binging.


Add closing div tag to fix alignment

[x] Fix alignment issue on the home tab.

Thanks @Olipa776
ill merge this now


Remove API keys from autocomplete prompt

Description
Currently, if you edit the config.json in an editor with autocomplete enabled, apiKeys may be included in the prompt to the autocomplete provider. Since it is fairly common to edit the config.json in editor, this PR replaces configured API keys with the string "SECRET".
Example
Before:
{
  "models": [
    {
      "title": "Claude 3.5 Sonnet",
      "provider": "anthropic",
      "model": "claude-3-5-sonnet-20240620",
      "apiKey": "[ANTHROPIC_API_KEY]"
    }
  ],
  "tabAutocompleteModel": {
    "title": "Codestral",
    "provider": "mistral",
    "model": "codestral-latest",
    "apiKey": "[CODESTRAL_API_KEY]"
  },
  "embeddingsProvider": {
    "provider": "openai",
    "model": "voyage-code-2",
    "apiBase": "https://api.voyageai.com/v1/",
    "apiKey": "[VOYAGE_AI_API_KEY]"
  },
  "reranker": {
    "name": "voyage",
    "params": {
      "apiKey": "[VOYAGE_AI_API_KEY]"
    }
  }
}

After:
{
  "models": [
    {
      "title": "Claude 3.5 Sonnet",
      "provider": "anthropic",
      "model": "claude-3-5-sonnet-20240620",
      "apiKey": "SECRET"
    }
  ],
  "tabAutocompleteModel": {
    "title": "Codestral",
    "provider": "mistral",
    "model": "codestral-latest",
    "apiKey": "SECRET"
  },
  "embeddingsProvider": {
    "provider": "openai",
    "model": "voyage-code-2",
    "apiBase": "https://api.voyageai.com/v1/",
    "apiKey": "SECRET"
  },
  "reranker": {
    "name": "voyage",
    "params": {
      "apiKey": "SECRET"
    }
  }
}

As this is my first contribution, feel free to let me know if any improvements could be made. For example, is this the correct place for the replacement to be made? Is the ConfigHandler the correct file for the apiKeys() function? Do we need to traverse like this or could we just get them from the known typed values? Could we just work on the serialised config instead?
I'm also happy to add any tests if needed.
Checklist

[x] The base branch of this PR is dev, rather than main
[x] The relevant docs, if any, have been updated or created

@FozzieHi I like the idea here, it's definitely pretty important to avoid API keys. I think it's going to be really difficult to handle all possible cases because sometimes there could also be an API key in a context provider's params. Maybe we ought to just ignore config.json for autocomplete altogether. Would you be interested in making this change?

@sestinj There's been a few messages on the Discord on this. I can see the pros and cons of both approaches.
By searching for the API keys directly, you might not necessarily catch every single case but you'll catch the majority of them. You'll also catch cases where the keys are stored outside of the config.json, for example in a variable in the config.ts. By disabling autocomplete in the config.json, you'll catch all cases of API keys in the JSON, but then you'll lose the usefulness of the autocomplete in that file. You also won't catch the API keys in other files like the config.ts, unless you disable autocomplete in all files in the .continue directory, and then you're reducing the usefulness of autocomplete even more.
So instead of force disabling it in the .configure directory,  should we make disabling it in the .continue directory a config option which is disabled by default, and document the risk of enabling it in the docs? We could either set a default value for disableInFiles, or create a new config option. The risk with setting a default value in disableInFiles is that users may inadvertently turn it back on again by configuring their own files and not including the continue directory in the array. Although we could document that as well.

Hi @FozzieHi , thanks for taking the initiative on this!
You made some good points on the pros/cons of both approaches but I would probably lean towards @sestinj 's solution as well - just disabling autocomplete in the Continue folder.
The more robust/long-term solution here is likely to identify any API key in any prompt and strip it out.
In the short run, I lean towards just disabling in the Continue folder for a few reasons:

Not much value in autocomplete in a config file
Easy to implement/maintain

@Patrick-Erichsen Great, that's what I was leaning to as well. Have you thought about what I said above about how we'd want to implement this? Either by putting it in as a default entry in the disableInFiles option, or creating a new boolean option like disableInContinueDirectory?

I think completions should be forcefully turned for config.json, but not for config.ts or other files in the .continue directory. While there's a chance that a few people might want to alter this behavior, I think the urgency wouldn't rise to the level where it would be worth the additional config complexity + docs + risk of reverting the change like you said

@sestinj Done, I couldn't find any tests for the disableInFiles functionality, so do you think we need one for this?

no need to test, this is perfect. Thanks for your contribution!


Incorrect this when passing a method from 1 class to another

class A {

    private key = "I am key from A";

    private action: () => boolean;

    public constructor(action: () => boolean) {
        this.action = action;
    }

    run(): boolean {
        return this.action();
    }
}

class B {
    protected key = "I am key from B";

    public constructor() {
    }

    test(): boolean {
        alert(this.key);
        return true;
    }
}

var b = new B();
b.test();

var a = new A(b.test);
a.run();

This will give 2 alerts, the first one, "I am key from B", obviously, considering I call it directly
However the second alert returns "I am key from A", while the B::test() method is called from a method from A.
The intellisense provided by the compiler in the test() from B is seeing "this" as the B class, which is not always true.
You can verify the code above on the typescript playground.
--
I can work around this issue by wrapping the b.test argument as
var a = new A(() =>  b.test());

This is the ECMAScript behavior of this.
See http://stackoverflow.com/a/20627988/1704166 for other solutions.


Added Xenoblade 3 to be prepared to the release

ok i put it in alphabetical order

alright looks good now, i'm just going to wait until July 29th to merge this because that's when the game comes out

ok


Creating new about get into teaching events page with subject page design

Trello card
Context
Changes proposed in this pull request
Guidance to review

Closing this as it is now superseded by https://github.com/DFE-Digital/get-into-teaching-app/pull/2805


Spawn cards

Spawn new cards for the player - at the start of the game and after each card action; at random and according to rules from previous cards.

Done except for drawing cards based on previous ones - prerequisites and sequences of events. Those have been moved to #15 and #17 respectively.


Glow to please support line numbers when using fence blocks

Currently if you want line numbers on your embedded glow code snippets, you have to use markdown as follows
this works;
[code numbered]
    var x = 10
    -var y = ••20••
    var z = 30
    for(i<10;i++) {
        // do •something with• all the ••numbers••
    }

renders as expected as follows;

However, if you use default fenced blocks triple tick to indicate a code block, everything works except line numbers dont render.
```js
    var x = 10
    -var y = ••20••
    var z = 30
    for(i<10;i++) {
        // do •something with• all the ••numbers••
    }
```

renders without the line numbers

For larger code blocks it's helpful to have the fenced code block in your markdown use the native markdown code formatting. Otherwise it's got no formatting in the IDE and only has formatting in the rendered view.
Not sure if this is a bug, or a feature. i.e. whether it was intended for Glow to support line numbering of normal fenced blocks or only via custom markdown tags?

If you want line numbers, you can set numbered: true in your site.yaml for global (or in your dir.yaml for sub-dirs) or in the front-matter, for a specific page.
:warning: But I think this is more of an accidental feature, than a planned one...
I don't think, that there currently is a feature to do this natively (without the global / page hack) so I think this would be a great addition.

Should be fixed with https://github.com/nuejs/nue/commit/91feb6d4b6a53cebeb81318ef2064c53669d6cbf on dev


Add "resume" functionality

Sometimes coqui-tts crashes. It would be nice to check to see if the intermediate wave files exist, and start back up from where we left off.

Resolved with https://github.com/aedocw/epub2tts/pull/42


Improve plugin documentation

This is an epic that involves:

Introductory information ("what are plugins and why do they exist")
Information for developing, testing, and releasing plugins
In-code documentation for plugin APIs.

See #330, #392.

Writing plugins was of complete ease. I will say, however, that the error messages it prints out should be more clear.
For instance, I was stuck on why I got a KotlinNullPointerException. It turned out it was due to adding an item name that didn't exist. After some debugging by modifying the DSL, the item at fault was "Kharidian headpiece" (despite copying from the wiki), only to find it is actually spelled "Karadian headpiece" in the source. If the error was more clear to that it being a spelling error (perhaps InvalidItemException or something?), it would have saved a lot of time. I had the same thing happen to waterskins and had to rinse and repeat the process.
Albeit this can be resolved by putting IDs for all items, that was not the intention behind the DSL.


Scrollbar causes fixed header to shift horizontally on page load in Chrome

The bug is found on any page using a fixed header, for example: http://www.getmdl.io/templates/android-dot-com/index.html
When the page is loading, the scrollbar covers the header. Then when the content is loaded the scrollbar pops down below the header, causing the header content to shift to the right.
This happens on Chrome only, and on all platforms (Linux, Mac, Windows).

This is a side-effect of how Layout is handled with lots of JS. The 2.x layout refactor should clear it up.

Great! Do you have an ETA on when we can start testing 2.x?

No.


gengine_quickstart mygengine

i read doc step by step to install https://gamification-engine.readthedocs.io/en/latest/installing/index.html#installation-from-pypi
after run command  this is result
bash: gengine_quickstart: command not found

did you find a solution?


Convert module roles to mutable

Converts ownerHat and arbitratorHat from immutable "constants" to mutable storage values.
The reason to do this is that this module is stateful, which adds friction to migrating to a new instance in order to update owner or arbitrator roles.
There are two primary benefits of immutable config on modules

simple to understand when/how they can be updated, ie by an admin of the hat as long as the hat is mutable
some gas savings by using immutable values instead of storage reads

We can get the benefits of (1) in a mutable scenario by constraining changes to when the hat is mutable.

lgtm