Added support for custom command line arguments

d2R.exe -mod skinName
-mod skinName
Mode is not applied
How do I create a command line for mod application?

command line arguments
-Mode SkinName
Mode not applied
What do I need to do?


Added documentation for Dark theme functionality

Signed-off-by: Shivam-AfA<EMAIL_ADDRESS>Notes for Reviewers
This PR fixes #51
I have updated the contributing.md file with documentation on the working of light and dark theme.
Signed commits

[ ] Yes, I signed my commits.

@leecalcote Reviews needed.


wis2downloader to use from image built by wis2downloader repository

wis2downloader to use image built by wis2downloader repository

2024-08-20:

implemented, being tested/docs (@david-i-berry)

Dave implemented this in this PR:
https://github.com/wmo-im/wis2box/pull/742
Note that users migrating from existing installation will need migration steps to cover the additional steps added in wis2box-create-config.py in order to use wis2downloader
The download-functionality will no longer work for users running wis2box on Windows.

@david-i-berry to verify install on Windows.

Completed and merged as part of https://github.com/wmo-im/wis2box/pull/742


Not clear how to "clean" my flutter project, and remove all generated/built artifacts

I tried to run flutter clean but that didn't work. I looked at flutter --help and I didn't see anything with the semantics of "clean up all the generated/built artifacts". Maybe I missed it?

For now, the workaround seems to be rm -rf build in your Flutter project.

There is flutter build clean -- not very discoverable, though.

Ah, thanks!
Consider this a request for "flutter clean" :)

Just ran into this again. flutter -h doesn't tell me an obvious answer for how to clean out my project.

cc @mit-mit

Thanks @goderbauer & @sethladd, always good when we can make things more discoverable!

There is flutter build clean -- not very discoverable, though.

It works for this error:
ion -Xlinker -dependency_info -Xlinker /Users/ies/Library/Developer/Xcode/DerivedData/Runner-apffkuoylfsqdqazxdmhgktnzyay/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/Runner.build/Release-iphoneos/OneSignalNotificationServiceExtension.build/Objects-normal/armv7/OneSignalNotificationServiceExtension_dependency_info.dat -o /Users/ies/Library/Developer/Xcode/DerivedData/Runner-apffkuoylfsqdqazxdmhgktnzyay/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/Runner.build/Release-iphoneos/OneSignalNotificationServiceExtension.build/Objects-normal/armv7/OneSignalNotificationServiceExtension

ld: library not found for -lvideo_player
clang: error: linker command failed with exit code 1 (use -v to see invocation)

?

Had the same issue on windows using VS Code. Once I closed the IDE and ran the clean from the command line it clean and I was able to relaunch the ide to get a successful build.

Run Flutter Clean but same issue still there
every time get the same data even I change the sign in ID


compsize: init at 2018-04-07

Motivation for this change
Adds compsize, a tool for checking the compression type/ratio on a file or a set of files on Btrfs.
Things done

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

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

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

Fixed.
Thanks for the review and explanation, I won't make that mistake again :)

@GrahamcOfBorg build compsize

Success on x86_64-linux (full log)
Attempted: compsize
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/18dv8bdjdi00nq7g4lzd16mcj6xanxvf-compsize-2018-04-07
shrinking /nix/store/18dv8bdjdi00nq7g4lzd16mcj6xanxvf-compsize-2018-04-07/bin/compsize
gzipping man pages under /nix/store/18dv8bdjdi00nq7g4lzd16mcj6xanxvf-compsize-2018-04-07/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/18dv8bdjdi00nq7g4lzd16mcj6xanxvf-compsize-2018-04-07/bin
patching script interpreter paths in /nix/store/18dv8bdjdi00nq7g4lzd16mcj6xanxvf-compsize-2018-04-07
checking for references to /build in /nix/store/18dv8bdjdi00nq7g4lzd16mcj6xanxvf-compsize-2018-04-07...
/nix/store/18dv8bdjdi00nq7g4lzd16mcj6xanxvf-compsize-2018-04-07

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: compsize
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: compsize
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/9038pr2kiawp09ij8z6f8gpq1zhw6w4z-compsize-2018-04-07
shrinking /nix/store/9038pr2kiawp09ij8z6f8gpq1zhw6w4z-compsize-2018-04-07/bin/compsize
gzipping man pages under /nix/store/9038pr2kiawp09ij8z6f8gpq1zhw6w4z-compsize-2018-04-07/share/man/
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/9038pr2kiawp09ij8z6f8gpq1zhw6w4z-compsize-2018-04-07/bin
patching script interpreter paths in /nix/store/9038pr2kiawp09ij8z6f8gpq1zhw6w4z-compsize-2018-04-07
checking for references to /build in /nix/store/9038pr2kiawp09ij8z6f8gpq1zhw6w4z-compsize-2018-04-07...
/nix/store/9038pr2kiawp09ij8z6f8gpq1zhw6w4z-compsize-2018-04-07


Adding support for internal pull up / pull down resistors and tri state

@sokarovski I assume that you have tried this code on a Raspberry Pi? I haven't had a need for these modes yet.

I have and i am testing it right now in my house. But now i start to think internal pull-up pull-down are not good idea since interference from relays is causing them to detect false edges probably because they are too week :D

@gavinhungry fixed the typo and i tested and it works perfectly 👍

Thanks @sokarovski!


Improve calldata decoder

Related Issue
mask when decoding
Description of changes

Think we can close this given it gets truncated on return & is unused within the assembly block


fix: compute getPkgName only when used

Description

Fixes #4698.
This computes getPkgName only when used within the OR operation, allowing for no package name if a libOptions.fileName is provided due to short circuiting. The check for libOptions isn't included anymore, because it's already present as the condition for when resolveLibFilename is called.
I'm unsure how to include tests as I'm unfamiliar with such a big project.
EDIT: Oh, I saw #4726 too late! Feel free to close this then.
Additional context

What is the purpose of this pull request?

[X] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the Commit Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[X] Ideally, include relevant tests that fail without this PR but pass with it.

The other solution throws an error https://github.com/vitejs/vite/pull/4726/files#diff-aa53520bfd53e6c24220c44494457cc66370fd2bee513c15f9be7eb537a363e7R644
I personally like your solution therefore more, cause it does not throw an error, but do stuff silently 🚀/🤔

Now it also throws an error 😢 So it is kinda the same as the other PR, and I don't prefer this PR instead of the other PR 🤷
So I'm for the solution that is just working (the other PR tests are green 👀 )

@Shinigami92 Thanks, I think I know why the CI failed. It's because it uses the old resolveLibFilename where I changed the third argument. Give me a few moments more to fix this. Then I'll push another commit.
It's difficult to test locally, because I see multiple other failures that I think are unrelated to this change.

[...] many unrelated failures that I don't see on the CI

I know you pain 😢


Only execute the close once the already added write operations completes

@normanmaurer
Motivation:
We need to be careful that we only execute the close(...) once the write
operation completes as otherwise we may close the underlying socket too
fast and also the writes
Modifications:
Keep track of if we need to delay the close or not and if so execute it
once the write completes
Result:
No more test failures

/cc @1Jo1

Also note that the CI is currently not working for this branch as we do not run a recent enough kernel I will figure out something for this

@njhill PTAL again


GitOps Resources Don't Work.....

I'm unable to get any of the harness_gitops_ prefixed resources to work. It appears either the underlying Go SDK API's don't permit the use of PAT/SAT keys and require a bearer token, or that the keys aren't being passed around internally.
I've tried a few options here in different directions, but ultimately we just want to have a terraform script create some Harness resources and trigger them. It seems this is potentially a trick too much though for the current state of play?

Yeah, I've confirmed this with the Go SDK locally. The fix is in addition to these lines....
	ctx = context.WithValue(ctx, nextgen.ContextAccessToken, hh.EnvVars.BearerToken.Get())

You need to follow them with:
	ctx = context.WithValue(ctx, nextgen.ContextAPIKey, nextgen.APIKey{
		Key: apiKey,
	})

(Where apiKey is from the terraform provider properties). Ideally you should remove any access of environment variables from these resource definitions and do that kind of defaulting in the Terraform provider function itself, not inside the individual resource stoo.

Hi @steve-gray , this has been fixed. Now GitOps resources support the pat token.

I can confirm this is working, and was able to deploy a Gitops agent.
@manavjot-harness  - is there a resource to configure the association between an agent and environment anywhere?

@steve-gray No we don't have a resource for the association for agent and environment. But you can configure environments to use certain clusters from an agent.
Can you please elaborate on the use case?


failed test : tests/test_examples/test_xls_examples.py::TestXlsExamples::test_basic_after_merge

labels corresponding to solar collector have changed from 'solarCollector' to 'solarCollectorSH' in the new version of the code. As a result, the dataframe columns like '(('electricityInBus__Building1', 'solarCollectorSH__Building1'), 'flow')' do not match with the expected results of basic_example.
The expected .xls results file needs to be updated.
Detailed report:
https://github.com/SPF-OST/optihood/actions/runs/11235281517/job/31232896202?pr=92

An additional issue arose with this test in the following:
https://github.com/SPF-OST/optihood/actions/runs/11361952168/job/31602758770
In constraints.py:
A case is encountered where the sh capacity exists and the dhw capacity is an empty list.
I added a check for the dhw capacity for this constraints in #95.

I am quickly checking this to get my pull request to pass.
One of the changes to the file does not make sense to me:
(('solarCollector__Building1', 'dhwStorageBus__Building1'), 'flow')
is changed to
(('solarCollectorSH__Building1', 'dhwStorageBus__Building1'), 'flow')
Should this be solarCollectorDHW?

Affected sheets:

electricityInBus 1x
domesticHotWaterBus 1x
solarConnectBus all named columns

This makes it seem like the change is in the wrong bus.
I would have expected it to show up in the space heating bus.
Is it possible that the solar collector is only connected with DHW for this case, and thus the name should include DHW and not SH?

@nehadimri1991
This tests now passes in #95 and you will need to check whether or not SH is a correct addition to the name in this case.


Option to use traditional time label suffixes

I prefer to use regular m and s suffixes over the current use of ' and " for minutes and seconds representation. Maybe others do too?
Depends on #125.

Thanks for all the PRs. I'm excited to see another dev adding to the project! 🎉
Could you make each PR self-containing without the requirement of another PR. That way we can review the PR on the changes (what it fixes or what new features it implements) without having to merge another PR. I understand there will be repeat code.

Hey @karbassi, thanks for the warm welcome. Glad I can contribute to this project!
Screenshots
Screenshots below for time label suffix change.
Current look

This PR

Its an optional setting, and defaults to the current behaviour, so shouldn't affect other people if they don't like it.
PR dependency

Could you make each PR self-containing without the requirement of another PR. That way we can review the PR on the changes (what it fixes or what new features it implements) without having to merge another PR. I understand there will be repeat code.

The first 2 commits of all the PRs I've submitted are actually all the same (adds the View menu option and saves/loads preferences from UserDefaults) – in other words, the PRs are already self-contained and can be merged without needing #125. I only split it up like that to make it easier for code review. But happy to close that PR if you prefer.
Let me know if this is ok. I'll then fix up the lint issues that have been flagged.


List of accepted file types

Is it possible to allow multiple file types, separated in a list, with separate descriptions for each?
Of course, I can allow as many file types as I want, however I would like to follow what desktop programs do, and separate them out like this:

Not a deal breaker obviously, just wondering if it's even possible on the web

This is certainly possible with the File System Access API:
await showOpenFilePicker({
  types: [
    {
      description: 'Text Files',
      accept: {
        'text/plain': ['.txt', '.text'],
        'text/html': ['.html', '.htm']
      }
    },
    {
      description: 'Images',
      accept: {
        'image/*': ['.png', '.gif', '.jpeg', '.jpg']
      }
    }
  ],
});

I'm looking to add a way to make this happen in browser-fs-access.

This is now supported as of v0.20.0, which will go out in a moment.


Add support for pane titles

Each pane in a window can have its own title pane_border_status and pane_border_format control its location and display format. Perhaps this theme can support coloring and easy formatting of it as well.

Added in #114


test(single): add test against breaking unsubscription chain

Relates to #875.

Hey! A new face! Thank you, @figueredo for the quality PR!
Merged with a484510... thanks again.

You're welcome, @blesh, I'll try to be here for a while :)


Rename ListStoreExtManual to GtkListStoreExtManual

Part of https://github.com/gtk-rs/gio/pull/131
cc @EPashkin @sdroege

@GuillaumeGomez Please remove ListStoreExt too (like https://github.com/gtk-rs/gtk/blob/master/Gir.toml#L417)

*rename (not remove)

Oh nice! I didn't know we had this option. Makes things much more easy!

Thanks.


Removed redundant if statement part

Before this pull request can be accepted you must first sign a CLA as described at https://www.pfsense.org/about-pfsense/#cla. Please read for more details.

That's not redundant. It prevents use of a gateway with synproxy state rules because it isn't functional in that circumstance (or at least didn't used to be, have you seen otherwise?). This is wrong regardless though as it would make it impossible to save any firewall rule that specified a gateway, which breaks tons of things.

Of course this is redundant, please take a look here:
https://github.com/pfsense/pfsense/pull/2876/commits/d19ad3c23a4461cde5dc74ddc9e4dcf20b010655#diff-34254bd85b68c71eddb8fc0eed510e66L455
You have the exact same if statement in line 455.

I didn't notice the check above it, looked like you just made a change without having any idea of why. I'll remove it. Thanks

Fixed in 34515250ca726f096071b139fcebd5d18601162a, thanks @Fusl


[libarchive] build failure

Host Environment

OS: Linux (Ubuntu 16.04)
Compiler: GCC-7

To Reproduce
Steps to reproduce the behavior:
./vcpkg install libarchive
Failure logs
error: no such remote ref 75a94bea3918e612b879d6a11ca64b8689526147

I found an answer https://github.com/microsoft/vcpkg/issues/14424


Typescript: Build errors when using TS workaround

glamorous version: 4.3.1, 4.6.0
glamor version: 2.20.40
react version: 15.6.1

Relevant code.
// Per https://glamorous.rocks/api/ "Known Issues" section
// Underlying issue: Microsoft/TypeScript/issues/5938
import glamorous, { ExtraGlamorousProps, WithComponent  } from 'glamorous'
export { ExtraGlamorousProps, WithComponent }

What you did:
Builds just started failing this morning. I tried updating Glamorous and it didn't resolve the issue.
What happened:
ERROR in ./src/NumericInput/index.tsx
(7,31): error TS2305: Module '"/Users/echen/Code/nuna-ui-components/node_modules/glamorous/typings/glamorous"' has no exported member 'WithComponent'.

ERROR in ./src/NumericInput/index.tsx
(7,46): error TS2305: Module '"/Users/echen/Code/nuna-ui-components/node_modules/glamorous/typings/glamorous"' has no exported member 'WithProps'.

ERROR in ./src/NumericInput/index.tsx
(13,7): error TS4023: Exported variable 'NumericInput' has or is using name 'GlamorousComponent' from external module "/Users/echen/Code/nuna-ui-components/node_modules/glamorous/typings/glamorous-component" but cannot be named.

ERROR in ./src/index.tsx
(3,42): error TS2305: Module '"/Users/echen/Code/nuna-ui-components/node_modules/glamorous/typings/glamorous"' has no exported member 'WithComponent'.
Reproduction:

Problem description:
One of our devs implemented this code to fix a type definition issue per the Readme. Today when we tried to build we started getting the errors above. These exports previously existed and I'm not sure why they were removed. Not sure if workaround is no longer needed, or if Readme is out of date, or if the change to typings files is the problem.
Suggested solution:

appears workaround no longer needed

Hey @tenshiemi, apologies I forgot to update the documentation for re exporting when creating definition files.
There's getting to be a backlog of outdated and missing typescript documentation unfortunately,  I'll try and get some updated over the coming weekend.
Glad to hear you got it working.


Wallet native logic

Closes #7
Todo:

Improve error handling on sendTokens result, but sendTokens seems to throw no error.

Improve error handling on sendTokens result, but sendTokens seems to throw no error.

Check if the result has a code. Code 0 or undefined is success. Other code is an error (use log)
  public async postTx(tx: StdTx): Promise<PostTxResult> {
    const result = await this.lcdClient.postTx(tx);
    if (!result.txhash.match(/^([0-9A-F][0-9A-F])+$/)) {
      throw new Error("Received ill-formatted txhash. Must be non-empty upper-case hex");
    }

    return result.code !== undefined
      ? {
          height: Uint53.fromString(result.height).toNumber(),
          transactionHash: result.txhash,
          code: result.code,
          rawLog: result.raw_log || "",
        }
      : {
          logs: result.logs ? parseLogs(result.logs) : [],
          rawLog: result.raw_log || "",
          transactionHash: result.txhash,
          data: result.data ? fromHex(result.data) : undefined,
        };
  }

Example how to check for errors:
try {
  const res = await client.sendTokens(rcpt, [{denom: "ushell", amount: "123456"}]);
  if (res.code) {
    throw new Error(`sendToken error: ${res.log}`);
  }
  // handle success case
} catch (e) {
  // handle error case
}

Reviewed the UI by clicking around. And actually had a hard time to get send to error... validation logic and all.
Places to improve:

Rather than 79000 ushell, please show 0.079SHELL. For the mapping, just define some mapping in the config. Please look at BankMeta in faucet for an example of this metadata. Here is how they build a Decimal using the balance and the metadata

On the Send page, it is very helpful to show the current balance, so I can remember what I have available to send.

I do actually get a "nice" error message now: "Send transaction failed:insufficient funds: insufficient account funds; 72994ushell < 74000ushell: failed to execute message"
I will take a look at the code, but the flow is working pretty well. Mainly changing ushell to SHELL

Also, tried search. It doesn't change anything. I tried the following accounts (which both exist on coralnet):

coral1r4tnas9cyfjvsq5yuusrlmvzxr6h7wu9srjxfd
coral17qgdxytgygz54etpq4nkmptfl5c3rl8z3sfxxa

Please check the search field

Please just fix the logic changes and do not worry about the UI stuff I mentioned above. I made another issue to rethink those flows: https://github.com/CosmWasm/dApps/issues/28
I think the Native Token and the CW20 Token designs are more different than I thought. And you made some good points when we talked.


Decide on best way to connect to SQL server

Considerations:

security best practice (don't want connection string to be public!)
ease of use

DSN, plus option to use connection string instead


Split value prop

Fixes #187 by making the current user-facing Var be a wrapper around a helper class VarInfo, where Var is a pair (VarInfo, PropValue).
The idea is to have VarInfo be the object that is passed around inside of all functions and be pointed to by all Node-s, so concrete propagated values can be garbage collected correctly.
Checklist for implementation

[X] Provide better typing around input_prop_values dictionary
[X] Fix adapt_node
[X] Fix documentation
[X] Add a CHANGELOG.rst entry
[X] Fix Var-s passed to manual inference
[X] Make tests passing

Breaking changes checklist

[X] Examine the performance implications?
[X] Examine downstream repos, does the change brake anything we rely on?

 It feels like a significant change.
I wonder if your standpoint on value propagation changed, Christian @cbourjau - it was mostly intended as an experimental side-feature to improve experimentation back when I added it, not something that should be relied on in live systems. So I’m not sure a large change is worth it to improve the GC behaviour.
I’m afraid I won’t be able to help review this as I’m pretty starved on time.

I'm afraid running this PR against this branch in ndonnx (which makes extensive use of Spox's value propagation) gives rise to a lot of warnings of the type:
spox._exceptions.InferenceWarning:
 Output type for variable expanded of ai.onnx@21::Unsqueeze was not concrete - ValueError: Tensor int32[...] does not specify the shape -- in ?.

These warnings do not appear when running on spox from the main branch.
You can make pytest fail on these warnings in the ndonnx test suite by running it as follows:
pytest tests -W="error:Output type for variable"

Do you think you can take a look into what is going on here?

This is caused by the fact that validate_types is being called before actually performing the value propagation.
Currently this type-validation is "optional", however AFAIK this is not really optional as validate is not exposed publicly. Should we remove this option. If we do, then we can safely move the validation after the value-propagation.


Placeholder Images

Picking up the discussion from #99 and #207, I'd like to track all the images on the site that are still placeholder.

[x] Site maintenance guide
[x] Passenger Showcase guide
[x] Getting Started Guide
[x] Workflow Track
[x] Algorithmic Botany Track
[x] p5 tips and tricks track

Tagging @jasontheillustrator I have some thoughts about these let's discuss on Discord!

Assigning myself as a reminder to create a selection of possible "backgrounds" for these thumbnails.

This can be closed now! @jasontheillustrator had the idea of a whiteboard shot for "getting started guide" maybe I'll get around to that at some point!


Add singlecell-barcodes installation.

Some of the common barcode schemes have a large amount of possible cellular barcodes, so I moved these out of the bcbio-nextgen repo and into its own standalone one to reduce clutter. @chapmanb my spidey sense is going off that this wasn't how you wanted stuff added, so pinging you to let me know if there is another way of doing it that works better. ggd-recipes didn't seem like a great solution since it isn't genome specific.

Moved this over to a bioconda recipe instead. Thanks @chapmanb for the good suggestion.


rw_pass_cell: remove WritePass custom Drop

If both drop and consume decrease parent.remaining_children by one,
then after calling consume, the final result would be a decrease of two
in parent.remaining_children

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#173  👈
#171 : 1 other dependent PR (#172 )
#166
#165
#164
#161
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gabriele-0201 and the rest of your teammates on  Graphite


set h264 encode default fps to 30

if input frame rate is unreasonable, fix it to a feasible value (30).
Signed-off-by: Fuwei Tang<EMAIL_ADDRESS>

I saw 30 is set as the default fps if fps info is missed in sample_encode and sample_multi_transcode, so how about setting this default value in MediaSDK?

Stanislav Efremov is OOO until Aug, 26


Signing releases

Would it be feasible for you to begin signing new release tarballs? Like for every .tar.gz if we could get a .tar.gz.asc? It makes verification significantly easier and it is the "proper" way to verify packages for rpms at least. I think it would be worth the extra effort since this is such a security sensitive application, given the fact that it's entire purpose is to act a middleman for keystrokes.

All Git commits are already signed.
All Git tags are already signed.

I don't understand the necessity for tarballs, which are disconnected from Git. This disconnection has led to issues, such as the case with the xz backdoor. In that instance, the Git source code was clean, but the tarball was compromised. There was no mechanism enforcing that the tarball matched the version control system, effectively undermining many advantages of being Open Source.
If source code is managed within a version control system, as it should be, the use of tarballs becomes unnecessary.

All Git commits are already signed.

All Git tags are already signed.

I'm aware. Signing tarballs is just a suggestion to make end user verification a little less convoluted.

I don't understand the necessity for tarballs, which are disconnected from Git.

You already distribute compressed tarballs. Right here: https://github.com/Whonix/kloak/archive/refs/tags/0.3.7-1.tar.gz. My suggestion is to sign them and distribute the asc file so that people who use the tarballs can verify them relatively easily.

This disconnection has led to issues, such as the case with the xz backdoor. In that instance, the Git source code was clean, but the tarball was compromised.

The xz incident is completely unrelated, the target was always ssh keys not compressed tarball archives. Nonetheless, there are mechanisms in place that prevented compromised versions from making their way into stable distributions such as Bookworm and Fedora stable. If it had made its way into bookworm(or trixie once it becomes stable), then Whonix and Kicksecure would have been compromised and people who store their ssh keys in a Kicksecure/Whonix vm would've been screwed, compressed tarballs would still be clean though.

There was no mechanism enforcing that the tarball matched the version control system, effectively undermining many advantages of being Open Source.

Just about every oss project on earth distributes via compressed tarball and git. I can't name a single project that doesn't at least distribute via tarball, can you? Even your projects get tarballs every time you tag a release. And once uncompressed you can still verify hashes and src code. With that in mind, can you really say that compression undermines open source?

If source code is managed within a version control system, as it should be, the use of tarballs becomes unnecessary.

Even when I use VCS I still end up just compressing the folder into a tarball using bzip2, I think most people do(with various different algorithms).
If you can't or won't sign tarball releases then fine, I understand you don't have to do this and you must already have a lot on your plate, but your reasoning here doesn't make much sense to me.

https://deb.whonix.org/pool/main/k/kloak/ has kloak_*.dsc (signed source dsc file that contains a hash) and kloak_*.orig.tar.xz (upstream tarball). Signed tarballs are provided indirectly.

Context of this ticket for users:
Simplified summary...
This feature request is not something users of Debian, Qubes, Kicksecure or Whonix need to worry about.
That ticket is  a feature request related to RPMs (Fedora package format), which are unrelated to Debian and derivatives.
For users, the supported  way to get kloak (or any package provided by Kicksecure or Whonix) to receive signed software is:

A) source code (signed git tags + signed git commits); or
B) signed APT repository -> https://www.whonix.org/wiki/Packages_for_Debian_Hosts

There is no security issue. There is no missing digital software signatures verification gap.


Unable to compare images locally

Describe the bug
When I run npx reg-suit run I get the following output:
npx reg-suit run
[reg-suit] info version: 0.12.2
[reg-suit] info Detected the previous snapshot key: 'b34f71b71df63026decb66bdaae226b1ba8d1df9'
[reg-suit] info Skipped to fetch the expected data because publisher plugin is not set up.
[reg-suit] info Comparison Complete
[reg-suit] info    Changed items: 0
[reg-suit] info    New items: 177
[reg-suit] info    Deleted items: 0
[reg-suit] info    Passed items: 0

It seems that reg-suit is unable not compare the images that are already located in my workingDir and actualDir, but instead expects me to install the publisher plugin, which I don't need. It skips the comparison with a message Skipped to fetch the expected data because publisher plugin is not set up.
Reproduced step
Install reg-suit without the publisher plugin and do the comparison.
Expected behavior
Images are compared without the publisher plugin.
Actual behavior
Skips comparison.

are you still reproducing this? Happens to me as well

My understanding is that this tool does not work without the publisher so I gave up.

@Jarzka
below is your our best bet on running locally. Same functionality as reg-suit
https://github.com/reg-viz/reg-cli


[json] JSON language server not localized

VSCode Version: VSCode 1.48.2
Steps to Reproduce:
1.Install VSCode
2.Install Language Extension Chinese(Simplified) and C++ extension
3.Open file “c_cpp_properties.json”
4. Delete the value or update value to an invalid one for property "cStandard"
5. Check the warning info in tooltip window
Expected:
Warning info in tooltip window
Actual:
Warning string “Value expected” and “Value is not accepted. Valid values" in file “c_cpp_properties.json” is not localized in tooltip window
(Repro on Windows, Linux and Mac)

@weinand Sorry for mislead you when create this issue, this issue actually not related C++ Extension, as when we delete a value or update value to invalid one for VSCode property without C++ extension installed, issue still repro (Updated screenshot as below), could you help to double check this issue? Thanks.
Warning string “Value expected” in file “settings.json” is not localized in tooltip window

Warning string “Value is not accepted. Valid values" in file “settings.json” is not localized in tooltip window

"Trailing comma" in file “c_cpp_properties.json” is not localized:


option parsing: don't consider argparse defaults over config file values

This was accidentally making prefix specified in an INI config ignored over the argparse default of ''. Oops.

Make sure to document that the INI config is intended to be overridable by the command-line options (or decide to throw up an error for dual definitions).


Gitc 2514 reproject updates

Pulled in changes up to https://github.com/lucianpls/mod_retile/commits/66c88728e0666443e87b6fc4f3f7e7365295ed72.
Added updates for memory issues

@dtchou802, was this a mistake?

@lucianpls yep


License?

The README says

© 2018 Plotly, Inc. MIT License.

but this is not the same as actually having the text of the MIT license explicit and included, either in the README or as a top-level LICENSE file.
Can you please clarify whether this software has an open-source license and, if so, what it is exactly?
Thanks!

Yikes! That is an oversight. Yes, this is MIT-licensed and I'll merge the license in as soon as CI passes :)
Thanks for the nudge!


⚠ Samsung has degraded performance

In 36245d5, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2709 ms

Resolved: Samsung performance has improved in 35797ec.


Contribution Tracking Spike

Pre-requisites

[x] I looked through both open and closed issues and did not find an existing bug.

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

We need to find a effective solution to keep track of user contributions.
Methods to investigate:

Database Schema for storing contrabution data
Contribution tracking utilities, endpoints, filters, queries, files.

Describe alternatives you've considered

Additional context

Utilities needed for MVP

GET API endpoint that returns current user pull request contributions

Needs filter logic to only show a select list of repositories (list pulled from database)
returns

title
url (for a link to the PR)
time merged (mergedAt)

Point scoring system (probably calculated in page after filtering)

add total points field to the user table, and editable user fields
might be easier to do achievements and milestones instead and tie points to those

Additional Utilities (non-MVP)

cache the get api results, and add a button the page to force a fetch

add a lockout to the button to throttle user requests?

add more precise point scoring parameters
create new endpoint or modify the old one to include issue contributions as well

Pages for MVP

Contribution page

Displays these properties,

total points or earned achievements
latest contributions in a table (5? all?)

add basic filtering to the returned data

only show merged PRs

if not 'all' add button to show all
each contribution has a link to the initial object/page
How many points its worth (if using this method)

Non-MVP Page improvements

show issues as well
add refresh button (with lockout?)
show point calculation method (unless we want to keep it a mystery)
improve filtering within the page

add other options

Likely MVP Stories (in order)

Basic api get endpoint returning all pull request contributions for the current user
Build acievement display component (if using this method)
Build PR display component
Contribution page (filter: show only merged)

Non-MVP Stories (no particular order)

Add filter options to contribution page
Cache contribution fetches
Fetch issue contributions
display issues on page

So for the request, it would be a GET request to get the data from our database right? So there would be a table for contributions that would have nodeId, description, type, score, and contributedAt.
Getting the data from github into that table is another issue, but that could be done with a CRON job that scans the user table for users that need their contributions updated. For this, there would be a new column on the user table, something like contributionsLastCheckedAt, and every time the CRON job runs it'll grab the users who haven't been updated in X seconds (some amount of time) and go fetch their contributions from GitHub and update that table.


Revert "[factory]: Add new maksimoos ZK Badge "

Reverts sismo-core/sismo-hub#1190

The created group is too huge for now

Here the refund tx https://etherscan.io/tx/0xd5f7dc376e60dedfc70644c57aa9144acf9021a3e1200b54f08e90a99f074a29

Hey @Latines, here are some information about your badge. Feel free to create a new one with less heavy computation involved please :)


[0.10 branch] SIGABRT statusline.c:260: stl_fill_click_defs: Assertion `len <= width' failed

Hi! I'm getting this error with statuscol on neovim 0.10 (main)
/home/runner/work/neovim/neovim/src/nvim/statusline.c:260: stl_fill_click_defs: Assertion len <= width' failed`
This issue seems to have been introduced by this commit from yesterday but I'm not 100% sure.
Steps to replicate
Just copy the following snippet into a file, let's say repro.lua. Then open vim with this command: nvim --clean +'so repro.lua'
It will first install the necessary dependencies.
Close vim and open it again with nvim --clean +'so repro.lua' to see the error.
You don't need to do anything else.
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

--------------------------------------------------------------------------------

vim.opt.signcolumn = "yes:1"

--------------------------------------------------------------------------------

local plugins = {
  {
    -- Remove ugly numbers in the foldcolumn
    -- Thanks: https://github.com/kevinhwang91/nvim-ufo/issues/4#issuecomment-1512772530
    "luukvbaal/statuscol.nvim",
    lazy = false,
    branch = "0.10", -- https://github.com/luukvbaal/statuscol.nvim/commit/ec939ac7d5e8560d0305b6d54f41bc8a3f7be0c7
    config = function()
      local builtin = require("statuscol.builtin")
      require("statuscol").setup({
        relculright = true,
        segments = {
          { text = { "%s" }, click = "v:lua.ScSa" },
          { text = { builtin.lnumfunc }, click = "v:lua.ScLa" },
          {
            text = { " ", builtin.foldfunc, " " },
            condition = { builtin.not_empty, true, builtin.not_empty },
            click = "v:lua.ScFa",
          },
        },
      })
    end,
  },
}

--------------------------------------------------------------------------------

local lazypath = root .. "/plugins/lazy.nvim"
---@diagnostic disable-next-line: undefined-field
if not (vim.uv or vim.loop).fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    "--branch=stable",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

This issue seems to have been introduced by this commit from yesterday but I'm not 100% sure.

Hey. That commit should have fixed the issue, are you sure you are on a build that includes that commit?

This issue seems to have been introduced by this commit from yesterday but I'm not 100% sure.

Hey. That commit should have fixed the issue, are you sure you are on a build that includes that commit (nightly builds don't yet, it was merged a few hours ago)?

That is correct. I though the neovim-nightly-bin from AUR was the same as main. I now built neovim manually and the issue is resolved! Thanks!


How to prove that MobileSAM's performance is comparable to the original SAM?

Thanks a lot for your work! When you mention that MobileSAM and SAM have comparable performance, do you mean with SAM (ViT-H)? I tried to find evidence for this idea from the paper, but only found a few visualization results. I'm really looking forward to know the quantitative comparison between MobileSAM and SAM on some tasks (such as the multiple experiments mentioned in the original SAM paper).

Thanks for your kind advice. We will conduct those experiments soon. Stay tuned!


Drag the table rows and the row goes to the bottom of the table.

Refer to the gif, i drag the row of "a".  While i was dragging it, this row appears at the bottom of the table until finish the dragging process.
Besides, the width of the table cell also expands while i was dragging.  Can i ask if you have any idea?
Thank you!

Hi while, dragging an item the CSS of its parent cell is applied the Drag element. that is causing you this issue.
I was not sure for some reason we are adding the class of the sortable element also in to the drag element.
dragElement.addClass(scope.sortableScope.element.attr('class')).addClass(sortableConfig.dragClass);
You could override any CSS of sortable element via setting the dragClass.
Let me also see whether I can remove applying the sortable class to the drag element.

You need to see any of your  CSS of sortable class is causing this?
also we apply the height and width of the element in itemScope to the drag element.
Should be a CSS issue.

support for table drag is added as part of #237 hence closing this.


Winamp current and update versions are the same

Brief description of your issue
winget shows Winamp as not up to date but the versions shown are the same:
Name   ID               Version Verfügbar Quelle
------------------------------------------------
Winamp Radionomy.Winamp 5.8     5.8       winget

Steps to reproduce
install Winamp 5.8 (3660) http://www.winamp.com/ and execute winget upgrade
Expected behavior
Winamp should not be shown in the winget upgrade list any more, because the versions are the same.
Actual behavior
Winamp is shown in the winget upgrade list, but the versions are the same.
Environment
Windows Package Manager v1.1.12653
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

Windows: Windows.Desktop v10.0.19043.1288
Paket: Microsoft.DesktopAppInstaller v1.16.12653.0

Protokolle: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
-----------------------------------------------------------------------------------------
Datenschutzerklärung              https://aka.ms/winget-privacy
Lizenzvereinbarung                https://aka.ms/winget-license
Hinweise von Drittanbietern       https://aka.ms/winget-3rdPartyNotice
Startseite                        https://aka.ms/winget
Windows Store Nutzungsbedingungen https://www.microsoft.com/en-us/storedocs/terms-of-sale

Thank you very much, this works.


Run tests without internet fails if AWS is configured

As part of the https://www.codequalitychallenge.com/ you should be able to run the test suite without internet connection. However if I have configured AWS to be used in development, the factory for Documents do not work.

Fixed with ActiveStorage!


Minor Fixes for Environment Visualizer

Description
This PR fixes some issues introduced by the previous PR #1689 and adds some minor code quality improvements, including:

Refactored Arrow class
Fixed issue with scrolling on mobile
Fixed issues caused by mutating the runtime context passed in
Other minor changes

Type of change

[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 not work as expected)
[ ] This change requires a documentation update
[x] Code quality improvements

How to test
Tested against previous snapshots.
Checklist

[x] I have tested this code
[x] I have updated the documentation

Pull Request Test Coverage Report for Build 744450266

10 of 81 (12.35%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 29.133%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/features/envVisualizer/EnvVisualizerLayout.tsx
7
8
87.5%

src/features/envVisualizer/components/arrows/ArrowFromText.tsx
0
4
0.0%

src/features/envVisualizer/EnvVisualizerUtils.ts
2
7
28.57%

src/features/envVisualizer/components/arrows/Arrow.tsx
0
5
0.0%

src/features/envVisualizer/components/arrows/ArrowFromFn.tsx
0
6
0.0%

src/features/envVisualizer/components/arrows/ArrowFromFrame.tsx
0
6
0.0%

src/features/envVisualizer/components/ArrayUnit.tsx
0
8
0.0%

src/features/envVisualizer/components/arrows/ArrowFromArrayUnit.tsx
0
17
0.0%

src/features/envVisualizer/components/arrows/GenericArrow.tsx
0
19
0.0%

Totals

Change from base Build 743783473:
-0.06%

Covered Lines:
2639

Relevant Lines:
8282

💛  - Coveralls


Create getinvite.js

If you don't want it to show up in your help command, I'd suggest you remove the category and modify the permissions.
Also, would it be possible for you to add me in discord? I have a few questions, If yes my discord is yohan#0002. Thanks!

Ive send a request.


Without the The biometrics

Could someone mod this to make it do what it does randomly without the biometrics and be able to change settings with the wifi.

Would love this!

The firmware has two fallback behaviors that kick in if five seconds pass between heartbeats! You can have it fire random rainbow ripples or simulate biometric behavior.
Unfortunately, I'm not a great Web coder... I'm not sure how to even write that!

Planning on implementing an audio visualizer with this. Will submit a PR when I have it!

Planning on implementing an audio visualizer with this. Will submit a PR when I have it!

I would love this

The firmware has two fallback behaviors that kick in if five seconds pass between heartbeats! You can have it fire random rainbow ripples or simulate biometric behavior.
Unfortunately, I'm not a great Web coder... I'm not sure how to even write that!
Would it be possible to make it just random ripples without the hear sensors.

This is already implemented. Please read the readme.


Keep duplicated filterable list params when paginating

Closes #2199 from over 4 years ago!
The problem here stemmed from the use of request.GET.items(), which returns only the last value when multiple params have the same key, by design.
See https://docs.djangoproject.com/en/3.1/ref/request-response/#django.http.QueryDict.items
Changing to .lists() and updating the logic a bit to handle the resulting lists stops params from being dropped.
Also, filtering out the 'page' param prevents the other bug here which was repeated page params in the querystring.

@wpears
Do me a favor…

pull this branch and run it
go to http://localhost:8000/blog
expand the filter and check "At the CFPB" and "Director's notebook"
click "Apply filters'
scroll to the bottom of the results and enter "3" in the pagination component.
click "Go"

Do you get this error?

@anselmbradford I did encounter this (once) but I don't think it's related to this PR. I'm looking into the source of the error.

Almost certainly related to https://github.com/cfpb/consumerfinance.gov/pull/5984

Yeah confirmed, will merge this and PR a different fix (the error is local only)


Make sure V0 and V1 can coexist in the same Unity project

This may require removing all .meta files from AAC and its extensions

TODO:

[] Check if https://github.com/PiMaker/av3-animator-as-code can coexist in the same project as AnimatorAsCode V1
[] Check if https://github.com/suzuryg/face-emo can coexist in the same project as AnimatorAsCode V1

There does not appear to be conflicts, following CGE V3 push


Nitrokevin/building blocks

3 column footer block

Sorry If I've done this wrong, first building block and first time GitHub user !

Hey congrats for your first PR... Will take a look soon!

Hi @nitrokevin Before i review your PR you first need to correct the indentation of your code (2 spaces)
For your reference => https://github.com/zurb/building-blocks/pull/188/files

Thanks! I hadn't even realised my editor was putting 4 spaces until you mentioned it, on it now

I made the updates - merged!
Well done @nitrokevin!
Good feedback @IamManchanda !


Update e2e_federation with specific sig prefix

 Issue by guangxuli
Wednesday Aug 16, 2017 at 06:11 GMT
Originally opened as https://github.com/kubernetes/kubernetes/issues/50735

Is this a BUG REPORT or FEATURE REQUEST?:
Ref to https://github.com/kubernetes/kubernetes/issues/49161, e2e_federation still test use k8s.io prefix. Not sure if we could use sig-federation instead of k8s.io  just as https://github.com/kubernetes/kubernetes/issues/49161 described.
i would be happy to send a PR to update it if we indeed need.
/cc @quinton-hoole @csbell

 Comment by guangxuli
Wednesday Aug 16, 2017 at 06:12 GMT

/sig federation

 Comment by quinton-hoole
Saturday Sep 02, 2017 at 00:22 GMT

@guangxuli Yes, it would be great if you could send a PR.  Please use sig-multicluster, our new sig name.

 Comment by guangxuli
Monday Sep 04, 2017 at 00:48 GMT

@quinton-hoole ok, i will do that.

 Comment by guangxuli
Wednesday Sep 06, 2017 at 02:10 GMT

@quinton-hoole I had send a PR to fix this issue, In this PR i just move the ubernetes_lite.go to the new created directory named multicluster, I created it under e2e directory. I found that there is a another specific directory named e2e_federation. A little confusing,  there are three cases:

move ubernetes_lite.go to e2e, just like PR #51898
move ubernetes_lite.go to e2e_federation
move all e2e_federation to e2e

I am not sure which case is fit to sig-multicluster, what do you think? ;)

 Comment by guangxuli
Thursday Sep 07, 2017 at 07:17 GMT

@nikhiljindal Could you see this issue and the relevant PR. Thanks.

cc @guangxuli


When plotting categorical interactions, ensure we don't request more bounds than available color buckets

Due to automatic detection of categorical interactions, certain datasets (specifically, those with extreme outlier values) can cause us to generate a bounds array with more elements than the number of color buckets available to us. This leads to an error from matplotlib saying "ncolors must equal or exceed the number of bins".
This PR caps the number of bounds generated to be at most the number of bins available in the colormap.

looks good. Thanks!


added volume_mode attribute to ask for Block mode PVC

Signed-off-by: Franck davalo<EMAIL_ADDRESS>

will retry


@GREAT-OFFER@^**Amazon Gift Card Codes Generator 2023 Free All Time

5 second ago. you would argue that you re not getting the card for free but with some of the options you are trading things you don t even own for the applicable amazon gift card code that you can use to purchase anything from the online mega store.
Free amazon gift card code generator 2023 08 20 new update twitch gift card code generator google gift card code generator etsy gift card code generator shein gift card code generator feedback list of unused amazon gift card codes 2023 amazon gift card generator no human verification.
🔴✅𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄✅🅶🅴🆃🅵🆁🅴🅴
🔴✅𝐂𝐋𝐈𝐂𝐊 𝐇𝐄𝐑𝐄✅🅶🅴🆃🅵🆁🅴🅴
all we know is that amazon is the number one website to buy goods and services aside from that it offers cash coupons in the form of vouchers and gift cards amazon gift cards can be exchanged for products or services to send to their loved ones
you would argue that you re not getting the card for free but with some of the options you are trading things you don t even own for the applicable amazon gift card code that you can use to purchase anything from the online mega store.
free gift~Card codes 2023 free amazon gift~Card codes list free $500 amazon gift~Card~Generator $100 amazon gift~Card~Generator 2023 list of unused amazon gift~Card codes 2023 free $200 amazon gift~Card code.Amazon Gift~Card Tricks, Amazon Gift~Card Free Codes – Amazon Gift~Cards are plastic with a built-in microchip loaded with an amount of money that is normally not very high to make purchases or payments defined by the National Commission for the Protection and Defence of Users.
Amazon Gift Card~Code~Generator 2023-08-21 New Update Twitch Gift~Card
code~Generator Google gift~Card code~Generator Etsy gift~Card code~Generator Shein gift~Card code~Generator Feedback list of unused amazon gift~Card codes 2023 amazon gift~Card~Generator no human verification. If you also want to get free Amazon gift~Cards online then this information will show you all the platforms that use personally and where you can have managed to accumulate hundreds of dollars or rupees for freehand without any risk.
When you win a gift~Card for Amazon, they usually send you a code to your email. Copy the code and enter the Amazon page where the gift vouchers are redeemed ( amazon.com/gc/redeem ). log in to Amazon with our username and password, paste the code in the box that appears, and give it to redeem. The five dollars or rupees will be stored in your Amazon balance and valid for ten years from the date of issue.

🔴✅CLICK HERE TO GET FREE Amazon Gift Card Codes Generate NOW
🔴✅CLICK HERE TO GET FREE Amazon Gift Card Codes Generate NOW
🔴✅CLICK HERE TO GET FREE Amazon Gift Card Codes Generate NOW
5 second ago. you would argue that you re not getting the card for free but with some of the options you are trading things you don t even own for the applicable amazon gift card code that you can use to purchase anything from the online mega store. Free amazon gift card code generator 2023 08 20 new update twitch gift card code generator google gift card code generator etsy gift card code generator shein gift card code generator feedback list of unused amazon gift card codes 2023 amazon gift card generator no human verification.

FREE Amazon Gift Cards Generator 2023
54 seconds ago- ke with Cash Flipping, if someone is promising you free money in return for sending them a payment, it is likely a scam. Moreover, Cash App will never request funds from a customer for any reason.8.12 version

<< CLICK HERE TO GENERATE >>
Amazon gift card codes 2023 free amazon gift card codes list free $600 amazon gift card generator $100 amazon gift card generator 2023 list of unused amazon gift card codes 2023 free $200 amazon gift card code.Amazon Gift Card Tricks, Amazon Gift Card Free Codes Amazon Gift cards are plastic with a built-in microchip loaded with an amount of money that is normally not very high to make purchases or payments defined by the National Commission for the Protection and Defence of Users.
Amazon Gift Card Codes Generator [February 2023] No-Verification Amazon Gift Card Codes Generator Google gift card code generator Etsy gift card code generator Shein gift card code generator Feedback list of unused amazon gift card codes 2023 amazon gift card generator no human verification.
Free Amazon Gift Card Codes Generator 2023 [title ar gusti chudi]
Amazon Gift Card Code Signup or Login to your amazon account. Now Goto the Gift Card Redeem page. Or directly visit on this link – amazon.com/gc/redeem If you have an valid code, paste the code you have just copied in the box. To check your gift card, Hit the “Apply to Balance” button. Cheers! You’ve successfully claimed your amazon gift card balance. 5 Ways to Get Free Gift Card Code 2023.


Implement support for Tor Hidden Services and outbound connection establishment

Currently, lnd isn't able to connect to other peers over Tor, nor able to set up a hidden service and use that address as its publicly accessible address. As not all users will want to, or be able to advetise a publicly routed IP address, support for Tor hidden services should be integrated into the daemon. In addition to solving a slew of NAT issues, Tor hidden services also hide the location of the advertising lnd node, and make the system much more private when in us.
The Tor control port should be used to detect a local Tor daemon, and automatically set up an hidden service which lnd will use as its sole listening interface (if specified by a command line option). These two libraries may be of interest (or we implement our own interface to the Tor control port):

https://github.com/postfix/goControlTor
https://github.com/subgraph/roflcoptor

Steps To Completion

[ ] Add support for automatically setting up a hidden service over the Tor control port if a Tor daemon is detected locally.
[ ] Add support for connecting to advertised onion addresses on the network via a SOCKS5 proxy. Care must be taken to ensure that we don't leak any IP information or somehow incorrectly attempt o resolve DNS over clear net.
[ ] Add a new address type to the NodeAnnouncement p2p message. Both the current generation onion addresses, and the next generation (prop224 whenever they figure out what the encoding is) should be added.
[ ] A special mode should be added to lnd which ensures that it only connects to other peers over Tor and solely listens on a created hidden service address.

I was working on a project that does this as a library, I can take care of this feature possibly.

Hey @lostinblue ! Great to see that someone is willing to contribute in the project. The additional information which might be helpful for you.

Oops 😁

@lostinblue sounds like a plan, very excited to see this implemented! The networking/connection handling of lnd is similar to btcd which has already implemented this feature. As a result, you may want to take a look at their implementation (doesn't have auto hidden service though), as an initial point of reference.

I will read over the above and get in contact if I have more questions.

What I have previously worked on is an onion hash table (https://github.com/onionNet/oht). It connected peers similar to ricochet, using hidden services generated.
I have had on my list of things to do, to make a simple library for onion routing using hidden services without the pub/sub.
I will look over the btcd implmenetation, and implement it with whatever improvements I can think of. This may be able to solve your nat punching issue too btw.

I would like to work on this.
I am not sure if @lostinblue is still working on this or not.

I've looked for a couple of hours, and though Tor now uses Ed25519, it does not yet use it for hidden services.  No sources online that I could find indicated or showed how to generate a hidden service with a Ed25519 secret key.  I used both the ControlPort's "ADD_ONION NEW: Port=" command with an Ed25519 key and received a 513 Invalid Key error.  I also tried creating a hidden service via HiddenServiceDir & HiddenServicePort in my .torrc but to no avail.  I also looked in Tor's documentation about the config file (https://www.torproject.org/docs/tor-manual.html.en) and found nothing about the next-gen hidden services.  However, Ed25519 is mentioned quite a bit.

I have several questions:

When creating the HS, do we need to store the private key?  This would allow the same HS to be re-run at a later time.  I know Bitcoin Core does this (https://github.com/bitcoin/bitcoin/blob/master/src/torcontrol.cpp#L507).
What sorts of authentication to Tor's ControlPort should be supported?  Cookie authentication AND Password authentication?
Where would this code fit into the lnd codebase?  Say we have a HS, will custom code need to be written that handles the connections to the HS and reads the wire protocol?  Or is this code essentially already written and we can simply "plug it in"?

Since v3 addresses were released, I'll resume my work on this. Should also make it so that people don't need to port forward anymore when running lightning-app


[aws] iam instance profile, kubelet extra arguments #request

Howdy,
this beautiful module is kept clean and tidy thus it's quite limited to a certain extent. I'm curious if the bellow features could be of any interest and can be considered merge candidates into the upstream:

Worker node instance profile IAM role?
Extra arguments for the kubelet container?

No cloud account credentials are bound to nodes. Its by design to focus on cloud-agnostic Kubernetes usage cases and to keep a strict security profile.
For applications that need access to account credentials, first, some cloud providers offer credentials that can be given directly to workloads via Kubernetes secrets (e.g. a GCP service accounts as a Kubernetes Secret), rather than bound to VMs. AWS is more limited. Otherwise, you'll want to explore customization options.
For Kubelet arguments, if you find settings that are applicable to general clusters and useful, they can be added. But its not a goal to provide support for a free-form argument list.

I see. Regarding the first - worker instance profile iam role is not a subject to for inclusion into typhoon.
For the second --node-labels, --register-with-taints seem totally applicable @dghubble please correct me if I'm wrong.

I think node labels can be set with the API, so maybe we don't need a static conf flag.

@JordanP yes obviously they can. But generally how do you suggest to set the labels of the newly created instances by of an AutoScaling group?

Good point.

Also guys would you please envision the usage scenarios or maybe how this module should be properly extended (maybe anyone makes one's own fork).
Without IAM roles use in cloud platforms is very limited or I'm missing the proper usage approaches:

no master profiles - no ability to use EBS volumes etc...
no worker profiles - no ability to use KMS...
lots more possible limitations

At least roles might be empty but could be allowed for user's customizations.
What am I missing?

@dennybaa I understand your use case but as @dghubble said, how would you suggest we implement this in a cross-cloud compatible manner ? Cross-compatibility is a major "selling" point of Typhoon.

Yup. right. Totally agree with this one if you suppose to stick to the cross-compatibility. Let's leave alone IAM profiles I do not offer to introduce them anymore. However
extra arguments is a must imo.
How are people supposed to use this module? Out-of-the box a number of strict assumptions is taken, so that for me it seems difficult to customize typhoon. Personally I've admitted that typhoon could be a great starting point for a customizable cluster :+1:, typhoon is honestly awesome:+1:.
Though I run into many problems, probably due to a lack of experience or practical ideas how to bind these all together, I realized:

--cloud-provider is still not customizable, not provided (I guess this is on the list).
Different arguments for customizing manifests for various services such as kubelet, api-server etc should be introduced.

So this is my view, like potential users might be interested in doing their specific tuning such as enabling --cloud-provider, enabling feature gates etc. This obviously won't influence the default configuration "cross cloud compatibility".
When denying customization users are simply stuck without possibility to enable any features. Like it won't be even possible to enable specific feature gates to install a custom CSI plugin for example (https://github.com/digitalocean/csi-digitalocean).
Would you please clarify how users are supposed to use the module? Since there are no volumes, no ability to enable CSI (though it's told CSI ready), etc...
Please correct me if I'm missing anything, also please use cases for typhoon are welcome. For me it's difficult to envision how I can use it without volumes. PS. I can be really missing the "right" usage scenarios.

Choices in Typhoon are rooted in years of experience designing bare-metal Kubernetes, building and leading Tectonic at CoreOS, and daily operating a network of clusters daily. Whole problem domains have risen and fallen, the space evolved, colonized by corporations. Time has provided ample lessons in how scope decisions echo across Kubernetes landscapes, architectures, and the community.
Typhoon strikes the balance among pragmatism, security, sustainability, and correctness I desire in clusters and you may too. I understand if some find it strict, but that's ok.
These may be feature checkboxes, but they're nuanced decisions. I'll try to be succint.
Machine Roles
GCP, DO, and Azure (kinda) provide portable service account / token abstractions to interact with their services (e.g. access datastore from bare-metal). AWS does as well, but their IAM roles bound to VMs are pushed heavily (probably nothing to do with the long-term lock-in effect it creates in organizations). but here a high bar is upheld, that doesn't change on account of AWS.
In Typhoon, nodes do not get inherent account permissions. Design so that workloads needing to interact with cloud services receive credentials directly. When using cloud services (e.g. bigtable), don't assume the workload is anchored to the same cloud platform.
--cloud-provider
--cloud-provider is not a simple set it and done kind of option. In early Kubernetes, some providers used their clout to add code paths in-tree. There is broad consensus this was a bad idea and CCM and CSI are slowly replacing the need. The in-tree flow has specific assumptions about how hosts are configured with IAM roles and AWS tags. Allowing the flag to be set is akin to having to support the whole jumble.
Custom arguments
Arguments that are uniformly right and proper will just be set outright and are suitable for a PR. But additional variables and especially free-form lists of extra arguments are different. As nice as they sound, these become a support burden, can create reliance on alpha features/behaviors that get canned, and can cause instability that lowers the quality bar.
If you imagine a grid, options multiply the size of the matrix of correctness. This was/is a factor in commercial distributions needing large teams to drive their ship every bell and whistle feature expansion. Typhoon has to keep this complexity low.
CSI
I've used DigitalOcean's CSI, around v1.11, but I don't currently. It did not require custom feature gates, but their new v1.x releases now appear to rely on flags that are still alpha. That's between the authors (the features they choose to rely on) and upstream. But CSI as a principle shouldn't require modifications.
If you need an alpha feature now, kubectl edit ds apiserver -n kube-system to add the flags at your own risk or do it in a private fork.
Storage
There are a lot of Kubernetes storage providers. With various tradeoffs and stipulations.
Storage is a weak area, but I think most distros are as well. Putting data somewhere is the bare minimum consideration - there's also resilience, snapshots, backups, and how migrate it between platforms (yes). GKE/AKS/EKS enabling their disk storage also marries us to them. But we won't solve these problems today.
In my case, some applications are stateless and others are stateful. My stateful applications tend to either interact with cloud provider databases or run on-premise (several options). Not great (many similar lock-in problems) but it doesn't intrude on cluster architecture.
Conclusion
All that said, its not "denying customization". The source is freely available. The "just-a-module" design is specifically made to preserve your freedom to add tweaks in a private fork and carry them. There are helpful docs on customization.
The idea is that someone who is able to weigh the pros/cons of a non-standard alteration (e.g. some new alpha feature, doing the work to use aws cloud provider, etc), should also be responsible for making those tweaks and carrying them on their own. If it proves to be a wise investment and the feature becomes mature and ready, Typhoon will later have it and the need for carrying a patch gone. No harm. If not, its clear what transpired. It provides a bit of a cue when something goes off the edge of the map. And keeps this project sustainable.
I hope that explains some of the reasoning.
Its the subtle cue that someone is going  the map a bit.

This issue is getting into support / advice kinds of topics so I'm going to close.
But node labels and taints are in-scope for platforms that have heterogeneous nodes - platforms with worker pools that can differ and bare-metal where hardware differs. Its been in back of mind for a while, but low on the list. This can be tracked with #429

@dghubble Thank for a such detail answer!


fixing-loganalytics-bug

Purpose
This update addresses an error caused by using Log Analytics Classic in unsupported regions. The solution involves transitioning to the Log Analytics Workspace.
Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?
Instead of using Log Analytics Classic, the Log Analytics Workspace is utilized.

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test
Try deploying in regions where Log Analytics Classic is unsupported, such as Sweden Central, using the one-click deployment.

These comments are clearer and more structured, improving readability and understanding.

@microsoft-github-policy-service agree company="Microsoft"


Migrate from Travis to Papr (formerly redhat-ci)

It's extremely difficult to maintain a CI testing envornment when
it's base is an ancient Ubuntu-based distro that doesn't keep
pace with upstream kernel features and fixes.  Switch to Papr,
which allows testing based off of very-modern Fedora releases.
Signed-off-by: Chris Evich<EMAIL_ADDRESS>

N/B: Proof-of-concept / Work-in-progress.  Papr won't start running against this until https://github.com/projectatomic/papr/pull/56 is merged.

Okay @k8s-ci-robot I've signed the dagumn papers, now hand over the keys.

I think as still want to keep Travis if Papr doesn't cover Ubuntu yet

Yep, no reason we can't have both if you want 'em.  But @nalind left me with the idea this was a straight replacement though.  In all cases, nothing changes until papr is setup to monitor this, and the YAML is completed.
On that note, I'll need some help with what's needed to get the various "go" versions built/installed ( in .papr_first.sh ).  Also, if y'all have ideas for better names than 'first', 'second', 'third', I'm all ears 😀

Can we use papr to test on Ubuntu, so we can get rid of travis?

@rhatdan I'll ask.  Which releases would you like?  Latest and recent LTS maybe?

Latest and recent LTS maybe?

Yup if possible

Either latest or lts, both if they can run in parallel.

@rhatdan @runcom or others...could use help justifying up-front cost of adding Ubuntu support to papr

@cevich currently we are struggling with travis for support of latest Ubuntu.  This is causing people like @nalind to jump through hoops to keep it working.   Therefore we would like to get rid of travis, and keeping two CI/CD systems running would be complicated.
Support for Ubuntu in travis, will keep us honest and make sure that cri-o will always compile on it.  Otherwise we will be only testing on Fedora based operating systems.

Closing this, plan is to move Ubuntu integration/e2e testing into origin-ci and just keep travis for git/lint checking.


Fix bottom panel visibility behaviour in the theme editor

Fixes #29034, fixes #29056

Thanks!

Cherry-picked for 3.1.2.


Cannot connect remote host

Tried to connect multiple device through remote host  but the devices are unable to find it. Only the Host can find it through localhost

Hi, Can you please explain more on your issue? For what are you trying to connect? Is is a ballerina service or a ballerina composer. Please provide us more concrete information to proceed on this issue.
Thanks a lot for reporting.

When we were trying to connect two pc's using http1 protocol, only the
server created device can see the server. The other device cannot find it
On Tue, 14 Aug 2018, 9:18 am Vinod Kavinda<EMAIL_ADDRESS>wrote:

Hi, Can you please explain more on your issue? For what are you trying to
connect? Is is a ballerina service or a ballerina composer. Please provide
us more concrete information to proceed on this issue.
Thanks a lot for reporting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ballerina-platform/ballerina-lang/issues/10027#issuecomment-412746153,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnVOrT3JPn6rQcAxzFMXiIQHQcN_BBxsks5uQkipgaJpZM4V5fq6
.

@Chalithya
Can you provide the sample code you used?
Were you able to ping from one (client) machine, to the other machine?

I am closing this issue since this duplicate with #10025. Please check issue #10025 for update.


Kafka limits for eval instances are not properly handled in the CLI 4a1bcff

Verification
rhoas kafka create --name on account that has already one eval instance.
Fix for bug logged by @DuncanDoyle

@wtrocki I've added 0ff83ee76c3b90381b551aedcaf28d8365ca73e1 to workaround this issue for the time being. Please check.

@craicoverflow This is unblocked. Api returns 403 now.
Can you adjust changes for us. Thank you


Airbnb-maps issue

Team,
I have got below error, when install below commands and run my app, Can you please help me on this..
$ ignite add maps
$ ignite add vector-icons
$ ignite generate screen PizzaLocationList
$ ignite generate component PizzaLocation
$ ignite generate map StoreLocator
Issue description below,
PizzaApp\node_modules\react-native-maps\android\src\main\java\com\airbnb\android\react\maps\MapsPackage.java:2
7: error: method does not override or implement a method from a supertype
@Override
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
:react-native-maps:compileReleaseJavaWithJavac FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':react-native-maps:compileReleaseJavaWithJavac'.

Compilation failed; see the compiler error output for details.

O maps!  always fun.
Looks like the bug that got introduced in 0.47 for all android plugins.
Perhaps we need to update:  https://github.com/infinitered/ignite-maps
Does it work on iOS?
Thanks for reporting this!

O btw!  This is fixed.  Can you verify and close the issue?  Sorry for not reporting back faster, we fixed it a while ago.


Fix instrumentation link in README

Maybe the link to instrumentation best practices should be
https://prometheus.io/docs/practices/instrumentation/#counter-vs-gauge-summary-vs-histogram

Thanks!


Don't send keys to clients when they match a keybinding in rootston

This will be annoying but we'll have to figure it out anyway for sway.

Use a keyboard grab?

I don't think that makes sense.

Can't all keyboard events go through rootston just like the mouse events?

That's likely to be the correct solution, yes.


ocamlPackages.tyxml: 4.4.0 → 4.5.0

Motivation for this change
Things done

[ ] 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/)
[ ] Added a release notes entry if the change is major or breaking
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 124457 at 3fcd7a46 run on aarch64-linux 1

6 packages failed to build:

ocamlformat_0_11_0
ocamlformat_0_12
ocamlformat_0_13_0
ocamlformat_0_14_0
ocamlformat_0_14_1
ocamlformat_0_14_2

7 packages built successfully:

dune-release
ocamlformat
ocamlformat_0_14_3
ocamlformat_0_15_0
ocamlformat_0_15_1
ocamlformat_0_16_0
ocamlformat_0_17_0

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


switch qa-frankfurt to qa-dublin

its happening... soon.

👍

Once we fix the merge conflict, that is


full-text search, AlgoliaSearchNetworkError

Hi, I followed the readme on full-text search for cloud functions. Adding,modifying or deleting the blog-posts will trigger an error. Same for adding,modifying and deleteing for search/query/{queryid}.
I created an account on algolia then get the ApplicationID, and Admin API Key.
firebase functions:config:set algolia.key="<ApplicationID"> algolia.secret="<Admin API Key">

You need to upgrade to the Blaze plan (paid).

Oh , so it is not for free :( I'm still a student though. May I ask if I can do elasticsearch without paying or having crefit card?  By the way thanks.

Yes the issue is hapening because you need to enable billing on your account. For abuse protection reasons we had to disable external request for billingless accounts for now. After enabling billing there is still a large free tier so you likely won't get billed right away for Functions usage although the Realtime Database does not have a free tier so you'll get billed on that.
And yes you'll need a credit card to enable billing :/


SQL error when two rules refer to the :read action with hash parameters

Hello,
When you have the following:
# Models
class Item
  has_many :permissions, as: :subject
end
class Permission
  belongs_to :user
  belongs_to :subject, polymorphic: true
  # db field 'action'
end

# Ability
alias_action :read, :update, :destroy, to: :modify
can :read,   Item, permissions: { action: 'read',   user_id: user.id }
can :modify, Item, permissions: { action: 'modify', user_id: user.id }

Trying to do Item.accessible_by(current_ability) fails with the following error:
Mysql2::Error: Unknown column 'permissions.action' in 'where clause': SELECT `items`.* FROM `items`  WHERE ((`permissions`.`action` = 'modify' AND `permissions`.`user_id` = 14) OR (`permissions`.`action` = 'read' AND `permissions`.`user_id` = 14))

To fix it, you can do one of the following:

Remove the :read action from the :modify alias
Remove the can :read, ... rule
Use can [:read, :update, :destroy], ... instead of can :modify

This only seem to happen with :read, I couldn't reproduce with :update.
See #74 for more informations.

Seems to me this issue can be closed. Feel free to reopen in case.


rebrand: Update greenhouse URLs

Checklist

[ ] I have read the contribution guidelines
[ ] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

Forgot Joe is out today, @knolleary can you review?


Support kubeflow.org/xgboostjob

What type of PR is this?
/kind feature
What this PR does / why we need it:
Support kubeflow.org/xgboostjob.
Which issue(s) this PR fixes:

Part-of https://github.com/kubernetes-sigs/kueue/issues/297
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Support kubeflow.org/xgboostjob

/hold for review

LGTM, have you tested this on a running cluster? /assign @alculquicondor

Yes, I verified this feature on a real cluster using the following XGBoostJob:
apiVersion: kubeflow.org/v1
kind: XGBoostJob
metadata:
  name: xgboost-dist-iris-test-train
  namespace: default
  labels:
    kueue.x-k8s.io/queue-name: user-queue
spec:
  xgbReplicaSpecs:
    Master:
      replicas: 1
      restartPolicy: Never
      template:
        spec:
          containers:
          - name: xgboost
            image: docker.io/merlintang/xgboost-dist-iris:1.1
            resources:
              requests:
                cpu: 0.5
                memory: 256Mi
            ports:
            - containerPort: 9991
              name: xgboostjob-port
            imagePullPolicy: Always
            args:
              - --job_type=Train
              - --xgboost_parameter=objective:multi:softprob,num_class:3
              - --n_estimators=10
              - --learning_rate=0.1
              - --model_path=/tmp/xgboost-model
              - --model_storage_type=local
    Worker:
      replicas: 2
      restartPolicy: ExitCode
      template:
        spec:
          containers:
          - name: xgboost
            image: docker.io/merlintang/xgboost-dist-iris:1.1
            resources:
              requests:
                cpu: 0.5
                memory: 256Mi
            ports:
            - containerPort: 9991
              name: xgboostjob-port
            imagePullPolicy: Always
            args:
              - --job_type=Train
              - --xgboost_parameter="objective:multi:softprob,num_class:3"
              - --n_estimators=10
              - --learning_rate=0.1

I will create a PR for the document once https://github.com/kubernetes-sigs/kueue/pull/1109#issuecomment-1716958772 is resolved.

/remove-kind documentation
/kind feature

/retest
Due to https://github.com/kubernetes-sigs/kueue/issues/1090

#1090 happened again :(
/test pull-kueue-test-e2e-main-1-24

/lgtm
/assign @trasc
in case @trasc  would like to give a review pass as he reviewed the previous kubeflow integrations


defer assigning to video.currentTime Fixes #101

Tested in FF (Nightly), Opera (Beta), and Safari

ready for rereview @joeyparrish

rereview? @joeyparrish

rereview? @joeyparrish , double check the annotations, I've never written them before.  Guessing they're used for closure compiler.

Thanks for the revisions.  I really appreciate you working on this patch.

made use of EventManager.  rereview? @joeyparrish

Looks good to me.  Would you please give a quick read through CONTRIBUTING?  You'll need to sign the license agreement, and add yourself to AUTHORS & CONTRIBUTORS.

@joeyparrish , done.  rereview?

Excellent.  Thanks for your contribution!

Hi Nick, sorry to have to say, but this patch breaks live streaming.  You can see this by running this subset of the integration tests: spec_runner.html?spec=Player%20live
The symptom is that these live streams simply do not start at all, at least on Chrome.  Unfortunately, I have to revert your patch.  I really do appreciate you getting Shaka Player working nicely on Firefox, and I hope you're still willing to try again when you have the time.

No problema, about to hop a plane for a company work week, but I'd like to see this project working in FF, even if I have to write the patches.  Will take a look later.

Thanks, Nick.  We want to see this working well on Firefox, too, but haven't been able to make it a priority yet to figure out why Firefox's HTML5/MSE implementation seems to behave a little bit differently from Chrome's.  So your efforts are much appreciated.


Roadmap (0.4 and beyond)

(This supersedes the roadmap in #501.)
Goals for 0.4.0

[x] Axum extract function (#1093)
[x] Improvements to <For/> algorithm (#533, #1146)
[x] Remove need to explicitly call ::register() on server functions (#613, #1154)
[ ] Consider using anyhow in <ErrorBoundary/> and friends
[x] Support generics in multiple positions in components (#949, #1023, #1109)
[ ] Breaking: Reorganize features so that nightly is an opt-in feature and stable is default (#567, #1007, #591)
[ ] Breaking Changing reactive ownership model to avoid manual use of Scope and cx everywhere (#802, #918)
[ ] (?) Breaking: Use new bind: syntax for typed children on <For/> and possibly other control-flow components, when useful (#1140)

Non-breaking improvements

[ ] Reduce number of hydration keys and component comment markers  (#972, #903)

Goals for Future

[ ] Exploring partial hydration/server components/islands architectures that would allow us to reduce the amount of WASM shipped to the client and increase the ergonomics of loading server-only async data
[ ] Send/Sync reactive system to improve ergonomics (and possibly performance) of Axum integration (#832)

Ongoing work with no breaking changes

[x] Website.
[ ] Completing the guide/book.
[ ] Adding end-to-end testing for examples as part of our CI (#210). There has been much work by @agilarity on improving CI on the examples, including testing.

I have to say I really like this project, and this issues is well structure, I like the delineation of breaking changes.
I just want to introduce a sideways perspective -- "Reasons to walk away from 0.3"
So here is a consumer's story
When I follow the template step and produce a new  project from leptos version "0.3" and check the projection into github repository employing dependabot
I get security warnings  Ouroboros is Unsound
Here is my analysis or the situation
when I ask
cargo why ouroboros
I see "leptos_reative" is the only thing pulling in ouroboros
Also this issue was resolved a few says ago with thie PR
Replace ouroboros with self_cell
I appreciate managing the pace of releases is not straight forward
To argue against my point -- Some consumers will be put off by the frequent publication of releases with breaking changes,  seeing that incorrectly as sign of instability.
So I am just adding a single factor into a complex decision
At some point we must get off 0.3

output of cargo why
photo_indexer -> leptos -> leptos_dom -> leptos_reactive -> ouroboros
photo_indexer -> leptos -> leptos_reactive -> ouroboros
photo_indexer -> leptos -> leptos_server -> leptos_reactive -> ouroboros
photo_indexer -> leptos_meta -> leptos -> leptos_dom -> leptos_reactive -> ouroboros
photo_indexer -> leptos_meta -> leptos -> leptos_reactive -> ouroboros
photo_indexer -> leptos_meta -> leptos -> leptos_server -> leptos_reactive -> ouroboros
photo_indexer -> leptos_router -> leptos -> leptos_dom -> leptos_reactive -> ouroboros
photo_indexer -> leptos_router -> leptos -> leptos_reactive -> ouroboros
photo_indexer -> leptos_router -> leptos -> leptos_server -> leptos_reactive -> ouroboros

Adding end-to-end testing for examples as part of our CI (

I saw that some of the examples still doesn't have the end-to-end testing, can I write e2e test for them?

Adding end-to-end testing for examples as part of our CI (

I saw that some of the examples still doesn't have the end-to-end testing, can I write e2e test for them?

That would be really, really great.

Adding end-to-end testing for examples as part of our CI (

I saw that some of the examples still doesn't have the end-to-end testing, can I write e2e test for them?

That would be really, really great.

I am adding e2e tests for the counters_stable example. The PR will include more cargo make tasks to support trunk and playwright.

Exploring partial hydration/server components/islands architectures that would allow us to reduce the amount of WASM shipped to the client and increase the ergonomics of loading server-only async data
this would be very cool +1 for anything along this theme, especially isolated islands.

this would be very cool. +1 for anything along this theme, especially isolated islands.

@dezren39 This is very much a WIP demo but you can see the fruits of #1422 at https://leptos-hackernews-islands.fly.dev/
(This does not work on Safari or iOS at the moment; I didn't realize Safari doesn't have requestIdleCallback.)

Some HTMX-like features would be very cool tbh

Some HTMX-like features would be very cool tbh

Which HTMX-like features are you looking for, how have you tried to use Leptos to achieve the same things, and what's gone wrong?


in let_value(sndr, fun) use sndr's completion scheduler as current scheduler for sender returned from fun

 Issue by ericniebler
Wednesday Sep 13, 2023 at 16:28 GMT
Originally opened as https://github.com/brycelelbach/wg21_p2300_execution/issues/47

None

I think this change has since been applied to the wording that was merged into the WD with P2300R10, so this issue could probably now be closed.
See [exec.let] p2 (https://eel.is/c++draft/exec.let#2) which defines SCHED-ENV(sch) helper, which produces an environment that has a get_scheduler query that returns the completion scheduler of the predecessor sender. This is then stored in the op-state and moved into receiver2 constructed in p11 / p12.
However, I'm not sure if this is the right design.
If I write on(thread_pool, let_value(some_io_read, [](auto& buf) { return process(buf); })) then it would be surprising to me if the process operation ended up seeing a get_scheduler of the io-scheduler that is the completion scheduler of some_io_read instead of the scheduler that I injected into the context from above.
I think the rules around get_scheduler and get_completion_scheduler are still unclear in terms of exactly what the query represents. e.g. is get_scheduler just referring to an ambient scheduler that should be used for scheduling new work? Or does it represent the scheduler that the operation will be started on? While in many cases these two things will be the same, we are not really clear what the semantic requirements and guarantees of get_scheduler are and thus it's unclear whether behaviour like the one suggested in this issue is desired behaviour or not.
Unfortunately, this issue does not have any justification/rationale behind why this semantic was desired. @ericniebler do you recall what the motivation/use-case was behind making this change?

get_scheduler tries to return the scheduler that the work is started on. We don't say that anywhere and we probably should. And it's imperfect because we don't propagate the environment through set_* or start.


Fix to broken link for "Create the SSIS Catalog"

Link was this (which now gives 404 error):
https://docs.microsoft.com/en-us/sql/integration-services/create-the-ssis-catalog
Updated to this.
https://docs.microsoft.com/en-us/sql/integration-services/catalog/ssis-catalog?view=sql-server-ver15#create-the-ssis-catalog

Docs Build status updates of commit aa26e3d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/install-and-config-guides/set-up-and-install-prerequisites-for-biztalk-server-2020.md
:warning:Warning
View
Details

biztalk/install-and-config-guides/set-up-and-install-prerequisites-for-biztalk-server-2020.md

Line 269, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/sql/integration-services/catalog/ssis-catalog?view=sql-server-ver15#create-the-ssis-catalog' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 95, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-server-ver15
Line 205, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/visualstudio/install/install-visual-studio?view=vs-2019
Line 232, Column 5: [Suggestion-alt-text-bad-value] Alt text 'sqlasconfiguration' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 269, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/en-us/sql/integration-services/catalog/ssis-catalog?view=sql-server-ver15#create-the-ssis-catalog

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

This is a fix for issue #567
https://github.com/MicrosoftDocs/biztalk-docs/issues/567

@MandiOhlinger - Would you be available to review this PR?

Docs Build status updates of commit b59cae4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/install-and-config-guides/set-up-and-install-prerequisites-for-biztalk-server-2020.md
:bulb:Suggestion
View
Details

biztalk/install-and-config-guides/set-up-and-install-prerequisites-for-biztalk-server-2020.md

Line 95, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-server-ver15
Line 205, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/visualstudio/install/install-visual-studio?view=vs-2019
Line 232, Column 5: [Suggestion-alt-text-bad-value] Alt text 'sqlasconfiguration' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@CarloGarcia Thank you very much! I removed the language identifiers from the URL. So, we're good to merge.

Thank you Mandi!


Self-hosted gitlab always return HTTP 411 when pushing

Hey, guys.
I want to cherry-pick a commit and push it to my gitlab server. But it always return Error: Unexpected HTTP status code: 411
I have no idea what's wrong with my code... please give me a help
environment:
macOS 10.12.1
node.js 7.1.0 (--harmony-async-await)
nodegit 0.16.0
Here is my code:
const repo = await Git.Repository.open(process.cwd())
const remote = await repo.getRemote('origin')
const current = await repo.getCurrentBranch()
await remote.push(
  [`${current.name()}:${current.name()}`],
  {
    callbacks: {
      certificateCheck: () => 1,
      credentials: (url) => {
        if (url.indexOf('http') === -1) {
          return Git.Cred.sshKeyFromAgent(USERNAME)
        } else {
          return Git.Cred.userpassPlaintextNew(USERNAME, PASSWORD)
        }
      }
    }
  }
)

Thanks!

I guess that I found the problem.
I use http protocol and nodegit reject me and return 411 error code.
Does anyone has any idea? :(

How many changes do you need to push?

Can you check if this is https://github.com/libgit2/libgit2/issues/3981#issuecomment-257518324 (libgit2 requires chunked encoding to push changes)?

@saper I only had one change to push and my git push works fine.
Is this problem related to http protocol?

Yes, 411 is an HTTP error code, in this case related to the size limit. SSH will be fine in this situation.


[BUG] Hubble Stats sidebar not remain consistent when refresh

The sidebar expands and then collapses when users refresh the page:
Expected behavior: The sidebar should remain consistent when user refresh
https://github.com/webb-tools/webb-dapp/assets/69841784/38503214-7851-40d9-91da-a1eb81631602

Current best approach: Utilizing cookies and NextJS Server Action.
However, Server Action is only available in Next 13.4 and we are still using 13.3.
=> Postpone this task for now!


MIPS64: Using the macro MTC rather than MTC1

Fixed #3761

Thank you very much, this does indeed fix the problem. (Not sure how this slipped through, perhaps I should add a qemu-based CI job so that we do not have to rely on my manual testing)