libuv.org is empty

The current website is almost empty with a simple folder called dist in it.

Why can't someone add, at the very least, an HTTP redirect to the GitHub page? Slapping something together in GitHub Pages with a CNAME file would plug this hole if someone can alter the DNS for it.

We'll get there, we've just been busy with other things.


add natsnui

Details in Issue #47

Thanks for this! We would love to see this in our showcase channel in Discord! https://discord.gg/YsEQQX3Zaa


Display an info bar when the viewer receives a malformed JSON file.

This is part of #230: Developers should get confirmation that code analysis has run but no defects were found.
Also:

Collapse the ILoadSarifLogService<n> interfaces.
Simplify FileAndForget handling as we did in Sarifer.
Fix #264: FixSuggestedActionsSource throws NRE if there are no errors

// Copyright (c) Microsoft. All rights reserved.

Code obtained from Gabe.

Refers to: src/Sarif.Viewer.VisualStudio/Controls/InfoBar.cs:1 in 333c92d. [](commit_id = 333c92dadf2d92a84308c915b322ffa43a40a312, deletion_comment = False)


Don't report update available if steam unreachable

If the build number isn't returned, then report it as unknown, and don't report that an update is available.  This should resolve #220.

I will merge this and a few other pull requests into a single pull request.


Browse Featured returns 503 Service Unavailable

Description
Hi there, for a couple of days now, the Featured-page has been unavailable, maybe it's because of an API change?
Expected / Actual behavior
Expected: To see a list of the featured streams with their titles and thumbnails.
Actual:

Reproduction steps

Open Livestreamer Twitch GUI
Click on Featured under Browse

Environment details (operating system, etc.)

maybe it's because of an API change?

I doubt it as this is part of the public API. The "Service unavailable" error (no. 5xx) indicates that something else went wrong on their end.
I'm having issues as well these days, but not all of the time. Every so often the followed streams list is empty, so I think they're simply having some server/database issues. There's nothing I can do about.

I don't know if its coincidence, but this and other issues with LS seemed to coincide with the big twitch DDOS that went on a few days back


(thunderbird) Migrated to AU [AU thunderbird firefox]

when this is accepted, both this package and firefox can be pushed

Is it possible that both packages use the same helpers ? Perhaps thunderbird can use Firefox stuff or vice versa, its not really important.
That would make maintenance much easier.
My plan is to hae packages be as DRY as possible, for example https://github.com/majkinetor/au/issues/53 should accomplish similar stuff just on nuspec leel.

@AdmiringWorm you happy for me to merge, or are you planning on implementing above?

Seemed to me like they already were using same helper.

Seemed to me like they already were using same helper.

Not sourcing the same file. Any future modifications will have to be done on 2 places.

@majkinetor what are you talking about?
they are using the same helpers.

I must be insane. Sorry.

no worries, we all have moments of insanity 😉
anyways, if there are nothing else?
then I'm going to merge this


Use an object pool for ZopfliHash instances

This avoids a huge allocation (several until #27 is merged) every time the code needs a ZopfliHash instance.
If merging both this and #27, change the declaration of HASH_POOL to
#[cfg(feature = "std")]
pub static HASH_POOL: Lazy<LinearObjectPool<Box<ZopfliHash>>> = Lazy::new(|| LinearObjectPool::new(
    ZopfliHash::new, |hash| hash.reset()));
#[cfg(not(feature = "std"))]
pub static HASH_POOL: Lazy<LinearObjectPool<Box<ZopfliHash>>> = Lazy::new(|| LinearObjectPool::new(
    ZopfliHash::new, ZopfliHash::reset));

Thanks! #27 was recently merged, so would you mind rebasing this PR to the latest mainline commit? Also, could you show some benchmark results for comparison?

For what it's worth, I couldn't measure any performance improvement from either this PR or #27 😅.
(Not suggesting it's pointless, just the difference may be negligible)

Rebased.


[Spark] Adding Spark Connect Protobuf Messages to the Delta repository

Which Delta project/connector is this regarding?

[X] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description
Delta Connect is an extension for Spark Connect that adds support for the DeltaTable API. To be able to communicate back to Spark Connect we need to have access to Spark Connect's Protobufs.
Since Buf does not support local dependencies, while Delta and Apache Spark are two separate repositories, the only solution for Delta Connect to get access to Spark Connect's Protobuf messages is to have the copies of the messages in the Delta repository.
This may go out of sync, and we would need to update it manually from the Apache Spark repository, but this should be fine and would not break anything since Protobufs are backward compatible.

How was this patch tested?
N/A.

Does this PR introduce any user-facing changes?
No.

@andreaschat-db I don't think we have any plans right now, we are fine with having it to be out of sync momentarily with Spark Connect, do we have any plans on having the Spark Connect's protos to stay in sync with their copies in Delta Connect @tomvanbussel?

@longvu-db I am not sure if I have a good answer for now. We should figure this out together with the Apache Spark folks. For now we can just manually update these Protobuf files whenever there is a Spark release.


wasmtime: fix hash

Motivation for this change
Things done

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

[ ] 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 nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

No worries if it was a mistake, but just checking: why was this wrong, or why is it needing to change? :)

No worries if it was a mistake, but just checking: why was this wrong, or why is it needing to change? :)

Yeah I definitely had it working with that hash, but somehow no other machines are getting that. At first I thought it was a macOS vs linux thing, but now I can't get the old hash at all


Replace API Test Cases for privatized Contents

Overview
A large number of Subreddits have gone private and have thus, made their Posts/Comments unavailable for retrieval via API or direct links. As a result, any Post/Comment that has been targeted as part of the automated testing immediately fails after the initial API call.
Task
Identify these failing test cases and replace them with similar but public Posts/Comments of the same Content Types.

Within the ApiSyncTest::testSyncContentsByBatch test,  the following Contents are now failing due to going private.


Output model is not updated immediately

I had a dropdown list like this.

and in the loadMenttes function
$scope.loadMentees = function() {
console.log($scope.selectedPartnerSites);
};
but the selectedPartnerIds doesnot contain updated values, it has some delay.
if I change it to like this it works.
$timeout(function(
console.log($scope.selectedPartnerSites);
), 2000);
But I think this is not the right solution, any ideas?

Hi @georgi-kovachev ,
In AngularJs, scopes and DOMs are tightly attached one to another, and sometimes things don't always go in the sequence we expected. In this case, this is where $timeout can help, albeit in a hack-ish way.
The directive alone doesn't really follow the so-called "Angular way", and I do use some $timeouts in  it, so if you ask me, any solution is a solution, including yours.


Something wrong with WebGPU

https://floooh.github.io/sokol-html5/spine-inspector-sapp.html

https://floooh.github.io/sokol-webgpu/spine-inspector-sapp.html

WebGPU is darker

What device, platform and browser is this?

Wait! I can reproduce on Chrome macOS, why didn't I notice this before?

Might be some sort of SRGBA problem, the texcube sample which uses fully saturated colors looks identical.
I'll investigate. It must be a somewhat recent regression, otherwise I would have noticed it during development.

Ah silly me:
https://github.com/floooh/sokol/blob/08ae58e275decf36ca932ac8be3469556a46992f/sokol_gfx.h#L12787-L12788
I remember that I added the SRGB format sort of last minute before merging. I should be more careful. Fix incoming

Ok fixed, webpage will be updated when this CI job finishes: https://github.com/floooh/sokol-samples/actions/runs/6611073889
Thanks for the bug report!


[Blocker for OSL 1.33] Update operator managed persistence extensions to the RHB of Quarkus 3.8.4 and to the OSL version

Nothing here yet, but a reminder.

Description of the change:
Motivation for the change:
Checklist

[x] Add or Modify a unit test for your change
[x] Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@rgdoliveira @ricardozanini
A small clarification regarding the affected files in this PR:
The source of truth of the change is this file:  (here is where we change the versions)
config/manager/controllers_cfg.yaml
Then the following two files are automatically generated when we do
make generate-all. We must update them at the repository, and include in future version changes, but we don't change them manually.
bundle/manifests/sonataflow-operator-controllers-config_v1_configmap.yaml
operator.yaml
Finally, this other two files are changed only for making the number in the test consistent with current quarkus version, but really has no effect other than verifying that the yaml is parsed, etc.
controllers/cfg/controllers_cfg_test.go
controllers/cfg/testdata/controllers-cfg-test.yaml


Translated tags not showing up on Pixiv

Pixiv did some recent structural changes which probably changed all of the classes.

Nope, on pixiv, TPT is almost independent of classes.
It because pixiv has changed profile links and Danbooru doesn't understand them yet.
I did a temporal fix.


Locks up when moving/deleting/copying a few files

Fixed in repository, but not on a release yet due to not able to get the GitHub searching working again. The library I used died.


Support Cluster API provider AWS (CAPA) in the web UI

This is the issue tracking the implementation of support for Cluster API provider AWS (CAPA) in the web UI.
Details
As a first milestone, we aim to provide support for displaying all information our users are used to seeing from other providers.
Support for cluster and node pool management for CAPA will follow. Please see https://github.com/giantswarm/roadmap/issues/1181 as the tracking issue for the broader topic of supporting cluster creation for cluster apps.
References

Cluster app
CRDs

Tasks

[x] #1446
[x] #1447
[x] #1450

Display

[x] #1474
[x] #1507
[x] #1475

[x] Display instance type statistics for worker nodes
[x] #1526

[x] #1492

[x] Display instance type statistics for control planes

[x] #1501
[ ] #1575
[x] #1509
[x] #1508

There is a pr open that will close this issue.


Fix/improve function signatures and phpdoc for environments()

environment() supports multiple arguments and return types but that was not reflected in the phpdoc. (causing warnings in IDEs) This PR fixes that.
NB phpdoc format for variadic function arguments as suggested by https://stackoverflow.com/questions/14513356/phpdoc-documenting-a-function-with-a-variable-number-of-arguments
NB Also fixes what looks to be a no-op return statement in afterLoadingEnvironment()

Someone already did it in master, looks like..


Unified PyPI-Conda dependency resolution

While pixi can now avoid broken environments by figuring out what will be installed as a Conda package, then avoiding installing that package as a PyPI package. It doesn't solve the two ecosystems in one solve. Meaning it doesn't try to find new solutions when the Conda solve succeeded and then the PyPI one fails.
Simple Scenario

You depend on numpy = "*" as a conda dependency.
It solves for conda as numpy ==2.1.3
You depend on a pypi-dependency that requires numpy <2
Error:

  × failed to solve the pypi requirements of 'default' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ Because package_x==1.2.3 depends on numpy>=1.24.3,<2 and numpy==2.1.3, we can
      conclude that package_x==1.2.3 cannot be used.
      And because only package_x<=1.2.3 is available and you require
      package_x>=1.2.3, we can conclude that your requirements are unsatisfiable.

Idea for a Solution
This would be solved if our Conda(Rattler) and PyPI(uv) solver implementations could interact and share the information about the problems they run into. Like if the example error shows up, the Conda solver could retry with that information and see if it is possible to get numpy with a lower version.
Current workaround
You'll need to help the solvers to understand eachother needs. In the previous example you can tell the Conda dependencies to get numpy = "<2" it would have most likely solved your issues.
Disclaimer
This issue is for informational purpose. This is an extremely hard problem we're not planning to solve any time soon while we're working on other features. Feel free to discuss or share experiences to better map this issue.

@abkfenris To verify you mean having the pypi-dependencies versions injected as constraints in the conda solve?
For example, in this pixi.toml:
[pypi-dependencies]
numpy = "<2"

[dependencies]
package_that_depends_on_numpy = "*"

It should result in a numpy lower then 2 in the conda environment?

Yes, that as well, but I was thinking of something a bit smaller in scope like this:
[pypi-dependencies]
numpy = "<2"

[dependencies]
numpy = "inherit-pypi-constraint"

Then the conda solve would use the constraint from pypi-dependencies.
I'm thinking it might be a step on the way to broader unified dependency resolution.


resolving controller-interface type

Following the discussion in:
https://github.com/theganyo/swagger-node-runner/issues/58
This PR is NOT READY YET, I just wanted you to have an early look and get feedback from you and from the builder.
The code implementation is more or less there
However - I cannot guarantee it before I add tests for all the cases we discussed.
I'll get to it in a few days.

Peeweee. Haven't seen stack traces this long ever since the darker days of java... 😛

baaah. more missing opts. ok.

no. not missing opts. just a non-standard behavior.
I think i'got'cha now.
moment

Coverage decreased (-0.3%) to 96.104% when pulling f99c496c13a5ab1a375d29e130df839252b86eba on osher:patch-1 into a44711b21e04d0a989d58392ce076bd6cf9f96ca on theganyo:master.

Ok. Build passes
BUT
The PR is not ready, I still have to add more tests.
I just would appreciate if you take a look and say a word

Coverage increased (+0.07%) to 96.434% when pulling 94e3ef636e86815699982c8874f12185c4124bac on osher:patch-1 into a44711b21e04d0a989d58392ce076bd6cf9f96ca on theganyo:master.

Well, I'll be damned. I could not help myself...
I think we're there.
I would like to add one more thing:
~/fittings/swagger_cors
module.exports = require('./cors')

Can I please do it here?

Nice! I haven't had time to completely review, but this is looking super!
Re: cors... it's unrelated, should probably be a separate PR...

Then I suppose the context.output structure is also a different issue.
Will be glad to hear what you think though.
Anyway - I admire your response times.
I'm off to the weekend. Weekends here are Fri/Sat so I'll be back on Sunday.

Actually, on second thought, I'm ok with addressing them all in the same PR. As long as we can ensure all are backward compatible, I don't anticipate the need to accept piecemeal.

Oh, and enjoy your weekend! Yes, I'll try to review before then.

ok - fittings/swagger_cors - is done.
I wanted to update the docs, but I saw the README is rather empty...
How do you intend to manage docs?
Perhaps I should create a wiki page about x-controller-interface?

Yes, docs are horrible right now. This project was relying on the swagger project to maintain all the documentation, but that's no longer possible. So, yes, we should start a wiki. Many doc updates have been made only in the release notes until now, but it's not an acceptable way to continue.

Oops. Forgot to finalize this over the weekend. Thanks for all your work on this!

Scott - this is wonderful.
When should I expect it to be published on NPM?

Did you happen to go ahead and write up any release notes?

Where should I provide release notes?
I thought its some github feature only owners can...
Anyway - for my changes the release note may be in the spirit of:

This PR allows you to chose how you want to implement your controllers.
The default is like a middleware: operationMethod(req, res, next)
Alternatively, you can chose to write your controllers as a pipe: operationMethod(ctx, next)
In this case, the controller is passed with the pipeworks context, which have a reference to .request, to .response as seen in lib/connect_middleware,  line 55.
The idea in this case is not to use ctx.response, but leave your response body on the ctx.output, the status on ctx.statusCode, and the headers on ctx.headers.
The benefit is improved isolation from web-context. You don't have to run a web server to run your tests. You just pass it a ctx and see what you find on the ctx once the callback is called.
Lastly, you can ask bagpipes to deduct the interface from the controller's method signature.
If it names 2 parameters - it's a pipe, if it names 3 parameters - it's a middleware.
This directive may be provided in few levels that cascade each other.

The default for the entire server - provided at config/default.yaml as swagger.bagpipes._router.controllersInterface.
If its more comfortable to you to express it in the swagger - you may use in your swagger.yaml the following directive on the root: x-controller-interface.
You can cascade the default for an entire path, suggesting that all methods of the controller that manages this path are implemented this way, using x-controller-interface on the path level.
lastly - you can cascade the directive per operation, using x-controller-interface on the operation level.
The legal values are one of the values middleware, pipe, auto-detect, correspond to the behavior described above.

.
BTW - I think there's yet a small miss which I will be happy to fix before 0.7.1
We did not accomplished isolation from the web. Even if the user does not need to use ctx.response - he still needs ctx.request to access the ctx.request.swagger.params.
I think we should feature ctx.params
.
Oh, I also see you did not reference your release notes for v0.7.0: 😮
readme.md ends with
https://github.com/theganyo/swagger-node-runner/releases/tag/v0.6.4
https://github.com/theganyo/swagger-node-runner/releases/tag/v0.6.10
https://github.com/theganyo/swagger-node-runner/releases/tag/v0.6.11


Add support for vim-lsp

This is a copy-paste adaptation of the vim-ale extension for vim-lsp. I'm not sure this is the best way, but the other error/warning extensions follow the same pattern.

ping

pong

@fx-carton, will you apply the suggested changes?

Yes. I had a busy week, I'll do the changes in the week-end.

@fx-carton, thank you!

I left some minor comments, other than that, looks good.

I can't find your comments. Where did you leave them?

Please add this part as mentioned by @kazukazuinaina
if !get(g:, 'lsp_loaded', 0)
  finish
endif

and drop the l: prefix. Other than that it is okay I think

@fx-carton
Could you also update CHANGELOG.md?

thanks!

Sticking with NeoMake for diagnostics: LSPs aren't there yet.
Am I right in saying that this integration doesn't display current symbol, just diagnostics?


Add text render to render function example

In all examples expect this one, in button there is text from data

Thanks, @txantslusam 👍


different log file types

if within the logs folder we have other log files with other extensions (such as laravel.json)
the reponse returned to the front-end may become an Object as opposed to Array, and the log files
are no longer shown.

fixed


💅 Import used by decorator metadata reformatted as type import since Biome 1.6.0

Environment information
CLI:
  Version:                      1.6.0
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.11.1"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Linter:
  Recommended:                  true
  All:                          false
  Rules:                        complexity/noForEach = "warn"
                                complexity/noUselessSwitchCase = "off"
                                correctness/noUnnecessaryContinue = "off"
                                style/noInferrableTypes = "off"
                                style/noNonNullAssertion = "warn"
                                style/useNodejsImportProtocol = "error"
                                suspicious/noExplicitAny = "warn"

Rule name
lint/style/useImportType
Playground link
https://biomejs.dev/playground/?code=aQBtAHAAbwByAHQAIAB7ACAAQgBvAGQAeQAsACAAQwBvAG4AdAByAG8AbABsAGUAcgAsACAARwBlAHQALAAgAFAAYQByAGEAbQAsACAAUABvAHMAdAAsACAAVQBzAGUARwB1AGEAcgBkAHMAIAB9ACAAZgByAG8AbQAgACcAQABuAGUAcwB0AGoAcwAvAGMAbwBtAG0AbwBuACcAOwAKAGkAbQBwAG8AcgB0ACAAewAgAFIAbwBsAGUAcwAgAH0AIABmAHIAbwBtACAAJwAuAC4ALwBjAG8AbQBtAG8AbgAvAGQAZQBjAG8AcgBhAHQAbwByAHMALwByAG8AbABlAHMALgBkAGUAYwBvAHIAYQB0AG8AcgAnADsACgBpAG0AcABvAHIAdAAgAHsAIABSAG8AbABlAHMARwB1AGEAcgBkACAAfQAgAGYAcgBvAG0AIAAnAC4ALgAvAGMAbwBtAG0AbwBuAC8AZwB1AGEAcgBkAHMALwByAG8AbABlAHMALgBnAHUAYQByAGQAJwA7AAoAaQBtAHAAbwByAHQAIAB7ACAAUABhAHIAcwBlAEkAbgB0AFAAaQBwAGUAIAB9ACAAZgByAG8AbQAgACcALgAuAC8AYwBvAG0AbQBvAG4ALwBwAGkAcABlAHMALwBwAGEAcgBzAGUALQBpAG4AdAAuAHAAaQBwAGUAJwA7AAoAaQBtAHAAbwByAHQAIAB7ACAAQwBhAHQAcwBTAGUAcgB2AGkAYwBlACAAfQAgAGYAcgBvAG0AIAAnAC4ALwBjAGEAdABzAC4AcwBlAHIAdgBpAGMAZQAnADsACgBpAG0AcABvAHIAdAAgAHQAeQBwAGUAIAB7ACAAQwByAGUAYQB0AGUAQwBhAHQARAB0AG8AIAB9ACAAZgByAG8AbQAgACcALgAvAGQAdABvAC8AYwByAGUAYQB0AGUALQBjAGEAdAAuAGQAdABvACcAOwAKAGkAbQBwAG8AcgB0ACAAdAB5AHAAZQAgAHsAIABDAGEAdAAgAH0AIABmAHIAbwBtACAAJwAuAC8AaQBuAHQAZQByAGYAYQBjAGUAcwAvAGMAYQB0AC4AaQBuAHQAZQByAGYAYQBjAGUAJwA7AAoACgBAAFUAcwBlAEcAdQBhAHIAZABzACgAUgBvAGwAZQBzAEcAdQBhAHIAZAApAAoAQABDAG8AbgB0AHIAbwBsAGwAZQByACgAJwBjAGEAdABzACcAKQAKAGUAeABwAG8AcgB0ACAAYwBsAGEAcwBzACAAQwBhAHQAcwBDAG8AbgB0AHIAbwBsAGwAZQByACAAewAKACAAIABjAG8AbgBzAHQAcgB1AGMAdABvAHIAKABwAHIAaQB2AGEAdABlACAAcgBlAGEAZABvAG4AbAB5ACAAYwBhAHQAcwBTAGUAcgB2AGkAYwBlADoAIABDAGEAdABzAFMAZQByAHYAaQBjAGUAKQAgAHsAfQAKAAoAIAAgAEAAUABvAHMAdAAoACkACgAgACAAQABSAG8AbABlAHMAKABbACcAYQBkAG0AaQBuACcAXQApAAoAIAAgAGMAcgBlAGEAdABlACgAQABCAG8AZAB5ACgAKQAgAGMAcgBlAGEAdABlAEMAYQB0AEQAdABvADoAIABDAHIAZQBhAHQAZQBDAGEAdABEAHQAbwApACAAewAKACAAIAAgACAAdABoAGkAcwAuAGMAYQB0AHMAUwBlAHIAdgBpAGMAZQAuAGMAcgBlAGEAdABlACgAYwByAGUAYQB0AGUAQwBhAHQARAB0AG8AKQA7AAoAIAAgAH0ACgAKACAAIABAAEcAZQB0ACgAKQAKACAAIABmAGkAbgBkAEEAbABsACgAKQA6ACAAUAByAG8AbQBpAHMAZQA8AEMAYQB0AFsAXQA%2BACAAewAKACAAIAAgACAAcgBlAHQAdQByAG4AIAB0AGgAaQBzAC4AYwBhAHQAcwBTAGUAcgB2AGkAYwBlAC4AZgBpAG4AZABBAGwAbAAoACkAOwAKACAAIAB9AAoACgAgACAAQABHAGUAdAAoACcAOgBpAGQAJwApAAoAIAAgAGYAaQBuAGQATwBuAGUAKAAKACAAIAAgACAAQABQAGEAcgBhAG0AKAAnAGkAZAAnACwAIABuAGUAdwAgAFAAYQByAHMAZQBJAG4AdABQAGkAcABlACgAKQApAAoAIAAgACAAIABpAGQAOgAgAG4AdQBtAGIAZQByACwACgAgACAAKQAgAHsACgAgACAAIAAgAC8ALwAgAGcAZQB0ACAAYgB5ACAASQBEACAAbABvAGcAaQBjAAoAIAAgAH0ACgB9AA%3D%3D
Expected result
Be satisfied with the file as it is, like in Biome v1.5.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Biome is not able to analyze decorator implementations. I don't see how we could detect that CatsService is actually being used.

Biome is not able to analyze decorator implementations. I don't see how we could detect that CatsService is actually being used.
EDIT: We could ignore types used as a type annotation of a property parameter in a decorated class.

For a quick solution, I'm probably with your idea. I don't know the side effects yet.
For long term: Whats the state of the announced type system? Perhaps such a case can be covered by the type system in future?

For a quick solution, I'm probably with your idea. I don't know the side effects yet.

We could miss some cases where a type qualifier is actually needed according to the rule.
However, using both property parameters and decorator seems a common pattern for dependency injection.
Thus, I think it is a fair change.

For long term: Whats the state of the announced type system?

We have not started yet.

Perhaps such a case can be covered by the type system in future?

I am unsure if we will handle such complex analysis.

TIL that `@typescript-eslint/consistent-type-imports' does not work on NestJS files either, but it leaves the import as it is without displaying an error and without breaking the code after applying auto-fixes.
As a workaround, I disabled the useImportType' rule in biome.json'.

@bc-m  I couldn't get the useImportType to work what is the version of the schema that supports that rule ?

We recommend disabling the rule in angular/ nestjs projects: https://biomejs.dev/linter/rules/use-import-type/#caveat-with-typescript-experimental-decorators

It would be nice to somehow solve this problem, because decorators are an important part of Typescript.

How (typescript-)eslint does it, they simply skip this rule for files with decorators + experimentalDecorators: true + emitDecoratorMetadata: true. Biome could also do something alike.


Serviceworker should be unregistered from android webview chrome version 37.0.3770.67 ~ 37.0.3770.101

Related Issue: https://bugs.chromium.org/p/chromium/issues/detail?id=977784
In these chrome version webview, serviceworker blocked all network requests.
Could we handle this exceptional case in this library?

Sorry, I don't think this sort of "hot patch" makes sense for PWACompat. It's a very specific browser bug that we may not be able to detect or handle.


Project status ?

Dear all,
@devshawn, I just would like some information about the project status as we did not here from you since nearly 2 months now.
I think that you made a really good job and kafka-gitops seems to be interesting for many persons including me. I personally integrated it into my company processes to manage our Kafka clusters and I would really like to see some feature integrated like Schema management etc... Of course, I will collaborate as I already did for #52.
Wouldn't it be the good time to open the management to more than one person ? I can perfectly understand that this is really time consuming to maintain this kind of project alone but if a small group could be built I'm pretty sure that everything might be easier.
What do you think ?
Best,
Jerome

Hey @jrevillard,
Agreed, it can be hard and I'm happy the tool has helped you out. I apologize for not being around and letting your PR sit for so long.
I'd be open to adding some more maintainers in the future after discussing some code style + code structure that I'd like to follow since I can be a bit picky in my projects :)
I also booked time this weekend to get your PR reviewed and merged.

A new release will be pushed this weekend with the latest PRs incorporated. We will discuss the schema registry addition after that and possibly open up the project to a few more contributors. I was quite backlogged but I no longer have that backlog and will get new releases pushed regularly for kafka-gitops.
Expect a new release by the end of this weekend, hopefully sooner. 🚀

@devshawn Any updates? Should potentially think about getting additional maintainers for this project.

Hi all,
The next release will be pushed this week. I’ll look into more maintainers
in the future. Apologies for the wait.
On Tue, Nov 16, 2021 at 10:42 AM Alex @.***> wrote:

@devshawn https://github.com/devshawn Any updates? Should potentially
think about getting additional maintainers for this project.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/devshawn/kafka-gitops/issues/67#issuecomment-970456959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACEP3EUFDVOET3XVN2UUYG3UMKCX3ANCNFSM44VITQJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hello @devshawn ! Thank you for this awesome tool!
I experience the need of supporting in settings.topics.defaults.* more than just replication, and I'd be happy to contribute, but I'm not sure, whether this repo is actually maintained.
So I'm wondering, how big are the chances that a potential MR will be approved and merged "timely"?
Thank you!

So ?...

Hello all, is the project being abandoned?
That would be a pity! It can be a great donation to the open-source community!

Hi all, it's still maintained, I just haven't been working on it lately. I'll be making updates and making a new release soon.
I'm happy to review and accept PRs.

@devshawn Glad to hear this!
I have recently forked this project and made a release because I needed some bugs fixed and an additional feature: https://github.com/joschi/kafka-gitops/
Happy to contribute the changes back, although I had to revert one or two commits to make the tests work again.
This being said, what do you think about joining efforts with https://github.com/kafka-ops/julie, which seems to have the same focus and approach for managing Kafka clusters?
(CC: @purbon)

Looks like https://github.com/kafka-ops/julie is now also officially unmaintained.
Which leaves us with the newcomer https://github.com/streamthoughts/jikkou. 🥲
https://medium.com/@fhussonnois/why-is-managing-kafka-topics-still-such-a-pain-introducing-jikkou-4ee9d5df948


[Feature Request] Allow multiple Wifi's to be saved

It would be nice if i could save an arbritrary amount of Wifi's to the Tracker and it connects to the one with the highest signal. That would allow for multiple Wifi SSIDs being set up in a house/apartment and also make it easier if you either need to move between divorced parents or just visit friends often.

This could be nice indeed.
As a note so sidenote, if you only need 2 wifis, you can use hardcoded wifi and the server-set wifi. The tracker will try to connect to the wifi set by the server and then try to connect to the hardcoded one if it fails.

Thanks for the tip :)

As a not so sidenote, if you only need 2 wifis, you can use hardcoded wifi and the server-set wifi. The tracker will try to connect to the wifi set by the server and then try to connect to the hardcoded one if it fails.

That's coool.... I didn't know I could use it for that purpose!

Hmm I was referring to this: https://discord.com/channels/817184208525983775/817184209428021320/938940241648173158
altho, Eiren did say a few messages before that the wifi is stored as “hardcoded and last one used”, so I might have not understood something, my bad for the confusion.

I think hardcoded should always be a fallback on top of what was set via serial or wifi hotspot. The fact that hardcoded overrides storred is a problem. I think we may want to store wifi credentials in LiteFS when they are set via serial or other way, and retry them again. I am a bit worried about constantly trying two wifi credentials, this may wear out EEPROM. Is there a way to disable ESP writing credentials to EEPROM?

I mean, we can now basically store near unlimited SSID / password combinations, just needs someone to implement that (while that's happening the person might as well rewrite src/network/wifihandler.cpp)

Is there a way to disable ESP writing credentials to EEPROM?

yes


CU-21v8r8n_map_gitworkspath_host:container

map_gitworkspath_host:container

Task linked: CU-21v8r8n vscode  execute task pull laradock, space


fix: workaround drf-spectacular enum naming

https://github.com/tfranzel/drf-spectacular/issues/992


[Feature]: API Client can hit a minimal Space Manifest Diff endpoint (POST v3/spaces/<space-guid>/manifest_diff)

Blockers/Dependencies
No response
Background
Newer versions of the CF CLI (v8+) hit the POST v3/spaces/<space-guid>/manifest_diff endpoint when a space manifest is included with an app as part of cf push. We need to support a minimal version of this endpoint for the CLI to be able to continue with the push workflow.
As a client of the CF k8s API Shim
I want a minimal version of the POST v3/spaces/<space-guid>/manifest_diff endpoint to exist
So that I can use my existing client code to push apps
Acceptance Criteria
Scenario
Space Exists
GIVEN A CF Space exists and I have access to it
WHEN I I apply any space manifest
curl "https://api-shim.example.org/v3/spaces/<space-guid>/manifest_diff" \
  -X POST \
  -H "Content-Type: application/x-yaml" \
  -H "Authorization: bearer [token]" \
  -d @/path/to/manifest.yml

THEN I get back an empty diff
HTTP/1.1 202 OK
Content-Type: application/json

{
  "diff": []
}

Space Not Accessible
GIVEN A CF Space does not exist / I don't have access to it
WHEN I I apply any space manifest
curl "https://api-shim.example.org/v3/spaces/<fake-space-guid>/manifest_diff" \
  -X POST \
  -H "Content-Type: application/x-yaml" \
  -H "Authorization: bearer [token]" \
  -d @/path/to/manifest.yml

THEN I get back an empty diff
HTTP/1.1 404 Not Found
Content-Type: application/json

{
  "errors": [
    {
      "detail": "Space not found",
      "title": "CF-ResourceNotFound",
      "code": 10010
    }
  ]
}

Dev Notes

Docs: https://v3-apidocs.cloudfoundry.org/version/3.109.0/index.html#create-a-manifest-diff-for-a-space-experimental
Cloud Controller Code for how the diff works: https://github.com/cloudfoundry/cloud_controller_ng/blob/41036982a1d0ab82737c0f10f855bef650a7c5ef/app/actions/space_diff_manifest.rb

The CLI behavior for an empty diff is pretty good. It just goes ahead an reports what it's going to apply:
$ cf push dora -b ruby_buildpack -k 1.5GB -f manifest.yml
Pushing app dora to org org / space space as admin...
Applying manifest file manifest.yml...

Updating with these attributes...
  applications:
  - name: dora
    processes:
    - disk_quota: 1.5GB
      memory: 2GB
      type: web
    default-route: true
    buildpacks:
    - ruby_buildpack

Closing: This was addressed in https://github.com/cloudfoundry/cf-k8s-controllers/pull/214.


KeyError: 'cstring' when calling setDropdown

Hi! Not sure how much you're maintaining this, but I was playing around with the library for some tableau scraping of COVID data and came across an issue.
Everything worked fantastic until I tried to use setDropdown() on this dashboard. When I do that, I get:
    201
    202 def getWorksheetCmdResponse(selectedZone, dataFull):
--> 203     cstring = dataFull["cstring"]
    204     details = selectedZone["presModelHolder"]["visual"]["vizData"]
    205

KeyError: 'cstring'

I think this is happening because the data in question is integer data instead of strings, but I'm not entirely sure what's going on.
I have a testcase that demonstrates the issue at https://colab.research.google.com/drive/14nUWYCvJB1ERsROIwY-AL_ZkIE73GrMU

@zachlipton Hello, sorry for the late response, I've fixed the dropdown script example which should work on sample url provided. Unfortunately, you're link is not accessible anymore, can you upgrade to the latest version 0.0.7 and check if you still experience this issue ?

@zachlipton a similar bug #5 was also resolved in v0.0.8


Stomp out "player.txt"

The file is completely superceded by the new settings.ini
Issue Criteria:

All mentions of "player.txt" are expunged

Fixed on dev branch


Unable to override axios config for individual query

I am using the following arguments to build a client:
react-query-swagger /tanstack /input:swagger.yaml /template:Axios /serviceHost:. /use-recommended-configuration /output:lib/openapi.ts

And when using the generated client, I want to be able to override the axios behavarior for a specific useQuery usage:
import { Query } from './lib/openapi';

export function useMyQuery(axiosInstance: AxiosInstance) {
  return client.useMyQuery({
     onSuccess() {
       console.log("success");
     }
  }, {
    baseURL: "https://some-other-domain.com",
  });
}

When I look at the generated sources, the config is not being passed into the client method that runs the request. It therefore only uses the query configuration based on the setAxiosFactory or set...AxiosConfig call.
The generated client method looks like this:
function __getMyQuery() {
   return Client.getMyQuery();
}

The call stack indicates that the __getMyQuery function is being called with the attached meta/config passed into the original useQuery call. I suspect a fix here would require a slight modification because it's just adding an additional argument to an existing call flow.

Thanks for the report, plan to have this fixed today

@schwer the latest version should contain the fix. Could you please check if it's ok or not now? :)

I'm closing this one, feel free to reopen if something goes wrong


fix: allow after instructions for resumable uploads in a single chunk

Fixes #510

allow return-X-after-YK and x-goog-emulator-instructions:return-503-after-256K forced failures instructions for resumable uploads in both multiple chunks and a single chunk
add support to testbench for uploads to ignore request bytes already persisted, in align with GCS

[ASK]
Given that languages have different implementations on restarting an interrupted upload, verify language (conformance) tests are not adversely impacted by these new changes

[x] Testbench tests pass

This seems to break the C++ tests:
https://github.com/googleapis/google-cloud-cpp/pull/12069
Specifically these two tests:
https://github.com/googleapis/google-cloud-cpp/blob/576ea4680c54a9c3936481f43cc35072f9bd17f6/google/cloud/storage/tests/object_hash_integration_test.cc#L234-L257
https://github.com/googleapis/google-cloud-cpp/blob/576ea4680c54a9c3936481f43cc35072f9bd17f6/google/cloud/storage/tests/object_checksum_integration_test.cc#L238-L260
Both use x-goog-emulator-instructions: inject-upload-data-error, but fail with a fairly strange error.
2023-07-11T12:59:42.940753097Z [INFO] <140502397696384> UploadChunk() << UploadChunkRequest={upload_session_url=http://localhost:34887/upload/storage/v1/b/gcs-grpc-team-cloud-cpp-testing-bucket/o?uploadType=resumable&upload_id=4fb4efcfeb2deb52eb99f86617e5124336d7c2dfe2bc3a655a6eb3a4f0f8c5ad, range=<Content-Range: bytes 0-446/447>, known_object_hashes={}, x-goog-emulator-instructions: inject-upload-data-error, payload={{Lorem ipsum dolor sit amet, consectetur adipiscing.elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut e...<truncated>...}}} (/workspace/google/cloud/storage/internal/logging_client.cc:44)
2023-07-11T12:59:42.952790037Z [INFO] <140502397696384> UploadChunk() >> status={UNKNOWN: PerformWork() - CURL error [1]=Unsupported protocol} (/workspace/google/cloud/storage/internal/logging_client.cc:49)

We also see failed tests in Node.js with resumable upload request headers content-range set to'bytes 0-*/*'. This seems to be related to case handling in chunk_last_byte. Looking into this furthermore.
https://github.com/googleapis/storage-testbench/blob/a5a6592767799dc88122978bc5e3d04d0e6b2377/testbench/rest_server.py#L1007-L1009

Hi @ddelgrosso1 the node conformance tests now pass in my local dev environment. Could you help verify again when you have a chance, thanks!

Hi @coryan I believe the two failed tests are related. I've updated the PR to only inspect after-bytes instructions and added a unit test. Could you help run the C++ test suite again when you have a chance, thanks!

The C++ tests are now passing: https://github.com/googleapis/google-cloud-cpp/pull/12069 :shipit:

Update - confirmed that no language test is adversely impacted by this PR. Merging and cutting a new release tag shortly


Cell expression thresholds

Hello, many thanks for all your efforts in developing CellphoneDB!
I was hoping you could help me understand the situation below. From your publication (Efremova et al., 2020), it states that an interaction score between two cell-types is calculated by taking, for a certain cell-type, the percentage of cells expressing a gene and the mean gene expression. I have used the “threshold” argument in the method-2 (statistical analysis) to limit the minimum number of cells in a cell-type expressing a gene to be at least 10% (threshold = 0.1).
However, as you can see in the figure below, the interaction between endothelial cells and endocrine cells for LigandA and ReceptorA (not a complex) is scored as a very significant interaction, despite the endocrine cells only having 1 cell (out of 130 cells) expressing the ReceptorA gene, which would not meet the 10% threshold. I can only conclude that your threshold combines both cell-types (endothelial and endocrine) when calculating whether this threshold has been surpassed (combined cell threshold of endothelial cells expressing the ligand, or endocrine the receptor, is ~18%)? But this does not seem to match the wording in your documentation: “threshold percentage of the cells in the specific cluster”.
Many thanks in advance for any advice you can provide around this!
python 3.10.8
cellphonedb 4.0.0

Hi jamesl-g,
Thank you for using CellphoneDb and for your question. As far as I can see in the code the documentation is correct stating: “threshold percentage of the cells in the specific cluster” and we've never had this kind of feedback before. There must be something else at play here - it's as if the threshold has not been applied in the analysis. It's hard for me to guess what happened without having access to the data - if you like, you could send to<EMAIL_ADDRESS>access details to the data and the exact command you used to perform the analysis and I could try see what I could find out here? Btw, I'm going to be away for a few days but will get to it as soon as I get back.
Best,
Robert.


Dead light buoy and same dock placard symbols in scan-dock-deliver task

Whenever I launch the scan_dock_deliver.launch file, in the Gazebo world that is brought up (screenshot attached herewith), the light_buoy is dead (i.e. it is pitch black and does not display any color sequence) and all the dock placard symbols are exactly the same (blue_circles). It is worth mentioning however, that sometimes (extremely rare cases) the light buoy and the dock placard symbols work as expected. This is causing a lot of delay in testing our algorithms for the scan_dock_deliver task.
I am not sure if other teams or the developers and maintainers of this repository are experincing similar issue, although I did find https://github.com/osrf/vrx/issues/163 similar to what I am experiencing.

Another weird thing that I recently noticed regarding the aforementioned issue is that sometimes the WAM-V camera is able to view color sequence of the light buoy even though the light buoy appears to be dead in Gazebo window.
The dock placard symbols, on the other hand, are visible to the WAM-V camera exactly the same as they appear in the Gazebo window.

I think this should be fixed in https://github.com/osrf/vrx/pull/452. Could you confirm?

Yes @caguero, https://github.com/osrf/vrx/pull/452 does fix this issue.


Include MomentumOptimizer in API doc

Add missing MomentumOptimizer to typedoc

This change is

Thanks again for the PR!
So we're actually going to be migrating how this all works really soon. We also want to be the ones who control the API releases (we're going to make sure the docs get built with new versions when we release), and we're going to be moving off github pages. In the meantime, I'll push an update after the tsconfig-doc change goes through.
Can you abandon this change, except for the tsconfig-doc change?
Thank you for bearing with me :)

Review status: 0 of 4 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Thanks for review. I understand the current situation.
I updated.

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


R2: Fix JSONRPC Version() bug

Problem:
When following the example code described here:
https://rdkcentral.github.io/rdkservices/#/userguide/native?id=creating-native-clients
If I perform the "DeviceInfo.defaultresolution" request with callsign "DeviceInfo", I'm getting an error:
"Requested version is not supported".
But I also get this when trying other rdkservices APIs (for example: org.rdk.Bluetooth.getApiVersionNumber)
Root cause:
WPEFramework sends out the request like this:

As you can see, it added a versionnumber '0' to the method parameter.
Bug:
When the example scenario is triggered as described above, WPEFramework::Core::JSONRPC::Version() is called with "DeviceInfo." as designator.
At the if-statement with the atoi statement, index remains at pos - 1 and therefore points to the 'o' character. Because index < pos, result would be set to the result of the atoi() call.
But as described here: https://cplusplus.com/reference/cstdlib/atoi/#google_vignette
If the string starts with an invalid integral number, atoi() will return 0.
Because the result of WPEFramework::Core::JSONRPC::Version() is no longer 0xFF, the _versionstring field of JONRPCLink gets set to ".0". This in turn causes it to get appended to the method field of the jsonrpc request.
Fix:
Make sure to add an isdigit() check before trying the atoi() call. If !isdigit(), the atoi() call is now being avoided.
The WPEFramework::Core::JSONRPC::Version() code has been changed in the master branch. But for RDK 6.0.0, the R2 branch of Thunder is still being used by default.
I therefore think it's likely this fix will only be needed for R2-based versions.

By the way: here is a test application I wrote to test this scenario alongside a recipe.
You may have to edit the recipe to fit your personal folder path (externalsrc based). I have personally been building RDK using a docker container.
testapp.tar.gz
To use this test application from the terminal (over SSH on a raspberry pi):
rdkjsonrpc <IP_ADDRESS>:9998 DeviceInfo defaultresolution

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@risingPhil good catch!  Indeed on master the code is heavily changed but looks like there the check for IsDigit is done. Guess this is an R2 issue only!

Thanks! ;-)


IterationLimiter - Limit the size of iterations in a loop

This is in order to avoid situations where users create a long/infinite loop.
By setting the parserContext we can limit those iterations on while/do blocks.

I believe this feature doesn't make much sense. In any programming language if the developer implements an endless loop (intentionally or not) the result he obtains is an endless loop. I don't see why mvel should make any difference on this regards. Also this limit (provided that we want it and I don't think we do) isn't something that should be set at ParserContext because in the same expression you could have more loops and this isn't something you may want to configure for all those loops.

we allow our clients to write their own mvel.
since the iterations are context based (different inputs) we can't really validate if they have an infinite loop.
we are executing mvel multiple times in a data set, so we don't really want to open a thread for each evaluation (which will cause a serious performance bottleneck)
what we basically required was a time monitor (if eval takes more than X seconds, about it with exception)....
any ideas what would be a better way of approaching this?

we allow our clients to write their own mvel.
since the iterations are context based (different inputs) we can't really validate if they have an infinite loop.
we are executing mvel multiple times in a data set, so we don't really want to open a thread for each evaluation (which will cause a serious performance bottleneck)
what we basically required was a time monitor (if eval takes more than X seconds, about it with exception)....
any ideas what would be a better way of approaching this?

You can use the "run time cap". It will kill query if it runs more then
specified time period. You can set it on the resource pool level, or on the
user level.
http://my.vertica.com/docs/7.1.x/HTML/index.htm#Authoring/SQLReferenceManual/Statements/ALTERRESOURCEPOOL.htm
(SEARCH FOR RUNTIMECAP)
Please call me if you need more details.
On Sep 29, 2015 9:50 PM, "raananraz"<EMAIL_ADDRESS>wrote:

we allow our clients to write their own mvel.
since the iterations are context based (different inputs) we can't really
validate if they have an infinite loop.
we are executing mvel multiple times in a data set, so we don't really
want to open a thread for each evaluation (which will cause a serious
performance bottleneck)
what we basically required was a time monitor (if eval takes more than X
seconds, about it with exception)....
any ideas what would be a better way of approaching this?
—
Reply to this email directly or view it on GitHub
https://github.com/mvel/mvel/pull/71#issuecomment-144154224.

I understand your use case, but there isn't much you could do about this. mvel is a programming language, so like any another language you can develop an infinite loop and I don't think there should be any special guard to prevent this.
For you scenario I don't see any alternative than doing mvel evaluation in different threads (other than educate your customer). If you reuse threads through a thread pool I don't think it will be that expensive.


Create gamma1 environment

As discussed, creates a new environment for smoke testing any changes before they go out to prod.

[x] Set up .tfvars
[x] Added GitHub action
[ ] Added environment variables and secrets

I found a github action to merge branches. Requires adding a GITHUB_TOKEN to the environment, though, which seems cursed: https://github.com/marketplace/actions/merge-branch


Wrong description for DL Gridmaster

Describe the bug
When pressing the Diplom Info button on the DL Gridmaster page (awards/gridmaster/dl) in my wavelog instance (installed via Docker), I get a description for a different certificate (see screenshot below):
Version Information
We need some information about your versions. You can get all Information in the Admin > Debug Menu

OS: Apache/2.4.62 (Debian)
PHP:  8.3.11
MySQL/MariaDB: 11.3.2
Wavelog: 1.8.5

Steps to Reproduce

Go to awards/gridmaster/dl
Click on Diplom Info
Read the text and realize that it is not the one for DL Gridmaster

Expected Behavior
I expect the information for the DL Gridmaster certificate.
Screenshots

There is no official DL Gridmaster. So it has the description for the US Gridmaster in there.

Texts for non-US Gridmaster have been changed in https://github.com/wavelog/wavelog/pull/1019.


Display team projects in link command

Handle when there are no projects found
remove avatar and projects from user entity
display team projects in link command

It would be nice to eventually show which team the project is in when they are listed out. But for now, this PR just fixes the team projects not being selectable in the railway link project list.

It would be nice to eventually show which team the project is in when they are listed out

This wouldn't be too bad given we know scope of the thing right? I think, if there are teams, we should iter through and slap a "Team Name" as a *string onto the entity on this side, which we can display in color if it exists (and only add it if there's  team & user projects)
I can add this if you don't want to as part of this PR


Set site collection locale to English in tests

Q
A

Bug fix?
yes

What's in this Pull Request?
If the default site collection uses tenant language, for example Norwegian, then localization tests will fail as they assume 1033/English to be the default.
I also set the the initial quota for storage to 100mb and sandbox resources to 0, to play nice.

Thank, we'll process this one together with your other PR.


Fix CVE-2020-7720 (update node-forge)

Hello 👋
The library node-forge has a documented security vulnerability: https://github.com/advisories/GHSA-92xj-mqp7-vmcj
We should bump our version to ^0.10.0: https://github.com/node-apn/node-apn/blob/d257fc5ea00cab46289eed8a002561b74547af8e/package.json#L33
First breaking change in new version is that node v4 support was dropped: https://github.com/digitalbazaar/forge/blob/master/CHANGELOG.md#0100---2020-09-01
But we don't support that anyhow since: https://github.com/node-apn/node-apn/commit/e72259fae1a749ce0a7bc146d7ea89dcd9593fca

This package doesn't appear to be maintained anymore. I'd suggest using the Parse Community's fork: https://github.com/parse-community/node-apn

related https://github.com/node-apn/node-apn/pull/684


GenericIndexedWriter: Fix issue when writing large values to large columns.

Fixes https://github.com/apache/incubator-druid/issues/9027.

so , "anything that changes getSerializedSize(), should be immediately followed by a  if(getSerializedSize() > fileSizeLimit) { .. } block .

so , "anything that changes getSerializedSize(), should be immediately followed by a if(getSerializedSize() > fileSizeLimit) { .. } block" .

Or, at least that needs to be between anything that changes the serialized size and anything that depends on it being less than the fileSizeLimit.


Suggestions are displayed twice when using Bloodhound remote option

Either the configuration of my typeahead input is wrong or the plugin has serious issues with remote calls (Bloodhound remote option).
Here is the repo:

request the page
typing A in the input -> remote request is excuted
server receives the request and returns A, B, C (it does not filter for the query term on purpose)
the remote data is processed
suggestion popup is displayed with A
typing something in the input again -> remote request is excuted
server receives the request and returns A, B, C (same behavior as above)
the remote data is processed
suggestion data is simply appended to the popup without any additional checks or existing suggestion processing -> everything is displayed twice, in this case A, A

The cause of this is the following line in
typeahead.js:
that._append(query, suggestions.slice(0, idx));

I've tried to add some code that analyzes the existing suggestions in the popup but i could not find a way to get to the Menu instance. As a last resort solution i've added the following line
that._resetLastSuggestion();

before the append call and now the popup works again as expected.
Is this a valid approach? Should i provide a PR?

@ViRuSTriNiTy I haven't been able to reproduce this. I have multiple different typeahead instances running where the suggestions are replaced completely (without duplication) as the user types.
Could you create a JSFiddle demo that reproduces the problem?

Possibly related to #103. Are you using both prefetch and remote sources?

May also be a duplicate of #59

Issue resolved in connection with #140, the remote source was not providing the suggestions based on the query term.


Stress test with send_columns for Rust & C++, improve C++ TimeColumn api

What

Add send_column variant to plot stress tests for C++ and Rust.
Small addition to C++ TimeColumn: from_seconds
from_times_nanoseconds -> from_nanoseconds,

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

@teh-cmc good catch! Looking at it again I believe both what I had originally as well as main are wrong. And the same applies to Python.
If you check on the diff you'll find that they both counted logged scalars as:
total_num_scalars += num_series;

Whereas what I did was:
let num_series = args.num_plots * args.num_series_per_plot;
let mut scalars_per_tick = num_series * args.num_series_per_plot;
// ...
total_num_scalars += scalars_per_tick;

which in your example is factor 5 * 5 = 25 more which matches the numbers
So but the number of scalars per tick isn't exactly the number of series times the number of series per plots, it is just the number of series! Each series gets a scalar every tick (unless we do columns which we we do colum-batch-size times many)
Where did I have this code? Ofc from python.

??? wth just happened

Oo

where did stuff go. It first showed merged to me,then just closed now merged again

dunno i rebase on main and stuff just disappeared -- ive repushed the previous state


fixing broken link

Summary
Details and comments

If this PR gets approved, do we need a redundant tutorials link in the TOC of docs?

I agree. I would be ok removing the tutorials link either in the toc or in web. But then we need to remove from qiskit.org. Up to you and @nonhermitian and @derivation

But I don’t think we should have a broken link so I would approve and make an issue about how many

Lets remove the sidebar one.

Sounds good. Can you approve @SooluThomas Pr


Slash missing

It seems a final slash is missing on all the output:
filestat.yml:
exporter:
  #! Working directory of exporter
  working_directory: "/dir1/dir2/dir3/"

  #! Network parameters
  #listen_address: ':9943'
  #metrics_path: /metrics

  #! Uncomment one of the following to enable default config
  #enable_crc32_metric: true
  #enable_nb_line_metric: true

  # list of patterns to apply
  files:
    - patterns: ["*/*/.ERROR"]
    - patterns: ["*/*/*.ERROR"]
    - patterns: ["*/*/*/*.ERROR"]

Metric output:
file_glob_match_number{pattern="*/*/*.ERROR"} 294
file_glob_match_number{pattern="*/*/*/*.ERROR"} 36
file_glob_match_number{pattern="*/*/.ERROR"} 0
file_stat_size_bytes{path="dir/dir/dir20201208164827.xml.ERROR"} 171
file_stat_size_bytes{path="dir/dir/dir20201208165023.xml.ERROR"} 17

The files are actually located at:
/dir1/dir2/dir3/dir/dir/dir/20201208164827.xml.ERROR
/dir1/dir2/dir3/dir/dir/dir/20201208165023.xml.ERROR

Between the filename and the last directory a slash seems missing.
Is this expected, an issue with configuration, a bug or me not understanding something?
Thanks!

My bad... it's the actual filename...


Dataset shape

Hello,
Trying to use this to figure out the CSG of MNIST Fashion loaded from keras. No matter what pre-processing I try I keep getting a shape error. I figure it should be similar to whatever pre-processing was used on normal MNIST and was hoping you could help?
Here is the error I am getting:
boolean index did not match indexed array along dimension 1; dimension is 28 but corresponding boolean dimension is 10

Hello,
Do you have some code I could look at?
We expect an array with shape [N, num_features] so you need to flatten the images.

Hi this was my latest attempt, but I don't think I am flattening the images here...not entirely sure how haha
#from spectral_metric.estimator import CumulativeGradientEstimator
#from spectral_metric.visualize import make_graph
from keras.datasets import fashion_mnist,mnist
from keras.utils import to_categorical
import numpy as np
#(X_train, y_train), test_data = fashion_mnist.load_data()
(X_train, y_train), test_data = fashion_mnist.load_data()
Normalize the images.
X_train = (X_train / 255) - 0.5
reshape dataset to have a single channel
X_train = X_train.reshape((X.shape[0],28,28,1))
y_train = to_categorical(y_train)
estimator = CumulativeGradientEstimator()
estimator.fit(data=X_train, target=y_train)
csg = estimator.csg  # The actual complexity values.
estimator.evals, estimator.evecs  # The eigenvalues and vectors.

You can flatten the images with:
X_train = X_train.reshape((X.shape[0],-1))

then I get a similar error: boolean index did not match indexed array along dimension 1; dimension is 784 but corresponding boolean dimension is 10

Ah I see the issue, you must not call to_categorical here.
And we expect an array with a single dimension.
y_train = y_train.reshape([-1])

Thank you so much! That worked and MNIST Fashion has a CSG of 0.61860741 in case anyone else needs to know!

Awesome! So a bit easier than notMNIST

Yep! And that kinda makes sense doesn't it! :)

Hello again, just had a quick question about the metrics in your paper, did you take an average for CSGs at all over a certain number of calculations?

This is the average over 20 runs I think? But the standard deviation was very small as you can see in Figure 2.

That's amazing thank you so much! As you may have guessed I am using the CSG from your paper in my own work and I just want to make sure the MNIST Fashion CSG value is inline with the others1 I really appreciate your help!

WHen it is available, send me a link and I'll add it to the README :)

I will thank you!

On 21 Jan 2022, at 17:53, Frédéric Branchaud-Charron @.***> wrote:

WHen it is available, send me a link and I'll add it to the README :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

Hello again,
I have been trying to calculate the CSG of CIFAR-10 because I want the range to display on a chart. In your paper it is reported as being 1 but I am getting it as over 3 and I am not sure why, would you be so kind as to assist me again?

Yeah sure.
For the paper, we got CIFAR10 embeddings using an autoencoder and ran t-SNE on it. We used MultiCoreTSNE.
CNN encoder code: https://github.com/Dref360/spectral_metric/blob/master/experiments/embedding/cnn_autoencoder.py
t-SNE code: https://github.com/Dref360/spectral_metric/blob/master/experiments/embedding/tsne.py
To compare datasets, they need to be from similar embedding and in the paper, we only showed scores for CNN+t-SNE I think.


Form builder is not allowing the change state and browser stop rendering.

I am closing the issue as it was created too long ago and there are no new comments here. I hope it was resolved. If not, please reopen it. Thanks!


[UNR-5579] Re-fix too many spatial flow controllers

Re-revert for the original fix now that https://github.com/improbableio/UnrealEngine/commit/67b19471da6744c16ea8a3e9aba5ba3144637d89 (and the 4.25 version) are in.
Original: https://github.com/spatialos/UnrealGDK/pull/3175/

Nightly: https://buildkite.com/improbable/unrealgdkbuild-ci/builds/7797


⚠ Bofrost.de has degraded performance

In bd9f985, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1518 ms

Resolved: Bofrost.de performance has improved in db6d0ac after 18 minutes.


apply_dilaton_conv_to_image_classification_such_as_imagenet

hi，Thanks for your sharing!
The dilation is used for dense prediction,such as Semantic Segmentation. I have a naive idea, can we apply the dilation conv to the image classification task，such as imagenet?
Do you know the work about this? Do you think the dilation will work for image classification?Is it worthy trying?
Thanks for your kindly help and nice work!

I know of someone who have been working on this idea.


Feature-Request, (auto player unlink)

Loving this bot btw,
The Feature Request
This feature would remove linked players when they leave the discord chat and the game server in combination.
Or it would remove the linked player when leaving the game server.
I hope this type of feature can be added in the near future.
Much Love From Australia.

This should be addressed in the latest 2.2.4 release :)


[Storage][DataMovement] Fix transfers using root BlobStorageResourceContainer

Fixes transfers with BlobStorageResourceContainer (the root of the container) being used as the source by setting the Path to empty string rather than the container name. Also adds one test using the container root for each type of transfer.

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

/azp run net - storage - tests

should be good to merge, the mac os test failures are known and the checkpointersas one is flakey and I disabled the test for a known issue we were going to address later.


Please update 'Mock authentication' example

Code example in Mock authentication section does not work or at least works in some cases.
Here example that worked in my case, I think it can be added to the page.
	services.AddAuthentication(options => 						{ 							options.DefaultAuthenticateScheme = TestAuthHandler.DefaultScheme; 							options.DefaultScheme = TestAuthHandler.DefaultScheme; 						}) 						.AddScheme<AuthenticationSchemeOptions, TestAuthHandler>( 							TestAuthHandler.DefaultScheme, options => { });

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

ID: 77889d43-fedb-f8b4-8fea-379ec946555c
Version Independent ID: f499b131-8b14-7e10-1728-543fdd5a5656
Content: Integration tests in ASP.NET Core
Content Source: aspnetcore/test/integration-tests.md
Product: aspnet-core
Technology: aspnetcore-test
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Moved to #23543


Search issue [ Make arrow icons consistent ]

To maintain consistency, please either remove or add the arrows from all the filters

@MeghnaTewari @dev-rajneeshkumar
These arrows come from Coveo itself and are set dynamically when the entry is a leaf and contains another entry group inside.
Checking documentation and code, I don't find a way to change this behavior inside the Coveo facet / menu:
https://github.com/coveo/search-ui/blob/master/src/ui/DynamicHierarchicalFacet/DynamicHierarchicalFacetValues/DynamicHierarchicalFacetValueRenderer.ts#L64
Please correct me if I am wrong.
A possible implementation to hide all the arrows could be done via CSS.


Tests the StateDiff calculation

TestDiffs are calculated after each transaction to record what changed in the StarknetState
https://github.com/lambdaclass/starknet_in_rust/blob/89a458a1c4c93a6af90aa3698555ba7b3c51f683/src/business_logic/fact_state/state.rs#L250.
To do that it keeps track of the changes in the CachedState cache. We should test that logic.

Imma work on this one