Vite migration

This PR migrate from create-react-app to Vite. Using vite improves the build time in dev and prod mode a lot. This originates from my attempt at upgrading to CRA v5 which was a failure because of the decision the CRA team made to not give any option to include basic polyfills for NodeJS modules the deps in this project are using.

I appreciate these PRs. @bobnik is going to look into this one for me. It looks fine, but I am not a javascript expert.
BTW, we aren't very fast, especially me. But we will get to these PRs.

@geekuillaume I've looked over this PR, and I'm OK with moving to Vite. It's a step in the right direction. Your current PR breaks some out of the box CRA functionality, like eslint and jest specs. I've locally made (I think) all of the changes needed to get these features back. If it's alright with you, I'll push some fixes to your PR and we'll iterate until we're all happy.
@jeffeb3 When the PR is ready, you'll have to try out the new build to be sure nothing is broken.

@geekuillaume I've looked over this PR, and I'm OK with moving to Vite. It's a step in the right direction. Your current PR breaks some out of the box CRA functionality, like eslint and jest specs. I've locally made (I think) all of the changes needed to get these features back. If it's alright with you, I'll push some fixes to your PR and we'll iterate until we're all happy.
@jeffeb3 When the PR is ready, you'll have to try out the new build to be sure nothing is broken.

You can push on this PR! Happy to see this merged :)

@geekuillaume @jeffeb3 I've pushed my changes. Please review. As mentioned previously, most of my changes were made to (1) completely remove CRA, and (2) manually add eslint and jest along with approximate copies of CRA's configuration for each.
Jeff, per Vite's instructions, I moved favicon.svg and CNAME files to the root folder. I wasn't sure how to test the CNAME change.

Awesome! Thanks for this! :)

Jeff, per Vite's instructions, I moved favicon.svg and CNAME files to the root folder. I wasn't sure how to test the CNAME change.

That stuff is all on the edge of my ability. I think we will probably have to pay close attention when we make the next release. But I am sure we can figure it out.

Oh, one last thing - lint no longer runs inside the node process. You will need to run it manually (since we don't have it integrated into CI, presumably just remember to run it before you push your changes).

I didn't know we had eslint :). How do I run it?

When the PR is ready, you'll have to try out the new build to be sure nothing is broken.

I have gotten around to trying this. I am running npm in a docker container to avoid changing the versions on my host OS. That all seems to work, although I am sure I could make it a bit smoother. I will put the dockerfiles up later, in a different PR.


[BUG] "Invalid Request. Dumping the Response" error when running command on slack

Hi - I am currently testing and playing around with this. Everytime I run "@botkube get pods" on slack, it does not give any response. I looked at the logs and I get below error:
INFO[2019-06-13T18:46:11Z] Invalid request. Dumping the response
INFO[2019-06-13T18:51:43Z] Invalid request. Dumping the response
INFO[2019-06-13T18:51:52Z] Invalid request. Dumping the response
INFO[2019-06-13T18:53:53Z] Invalid request. Dumping the response
INFO[2019-06-13T18:55:20Z] Invalid request. Dumping the response
INFO[2019-06-13T18:55:31Z] Invalid request. Dumping the response

I ran both helm and deploy all yaml file kubernetes manifests and both gave the same error. Am I missing anything? I setup the slack channel, the token, cluster name, and "allowkubectl: true" so I assume everything is setup?
If I enable events, I can see it populating in slack but slack can't seem to communicate correctly to the kubernetes cluster. Am I missing something?

ahhh found the fix! the problem was the slack channel. I was adding "#" on slack name when its not really needed.
  communications:
    # Settings for Slack
    slack:
      enabled: true
      channel: '#kubernetes'
      token: '<secret token>'

when it should be:
  communications:
    # Settings for Slack
    slack:
      enabled: true
      channel: 'kubernetes'
      token: '<secret token>'

Not an obvious error, maybe docs should reflect that.


Publish bosh release into bosh.io or s3 or github release

Can you please upload final release tgz into bosh.io or s3 or github releases?

Full release is there no ? https://logsearch-for-cloudfoundry-boshrelease.s3.amazonaws.com/boshrelease-logsearch-for-cloudfoundry-2.tgz

Thanks for linking URL to v4 release notes


How to respond with multiple Set-Cookie header?

according to https://tools.ietf.org/html/rfc6265#section-3

An origin server can include multiple Set-Cookie header fields in a single response

I can use raw to set headers, but header dictionary override old Set-Cookie key

Any updates on this?
Shouldn't the type for the response header be [(String, String)]? instead of  [String : String]? ?


How to invalidate the cache for a post method

I want to invalidate the cache if user call POST method to update data into database, so that th GET method can return the latest data to user.

You need to delete a key by yourself. Of course, you should use a custom key builder to get the key or delete it by using namespace.
Here's the later example.
e.g.
from redis import Redis
from fastapi import FastAPI
from fastapi_cache.decorator import cache

app = FastAPI()
redis = Redis()

@app.get("/")
@cache(namespace="some_namespace")
def get_some_data():
    return {"data": "some data from database"}

@app.post("/")
def update_some_data():
    for key in redis.keys("some_namespace:*"):
        redis.delete(key)
    return {"data": "updated data"}

If the namespace is too large, use scan_iter rather than keys function.

thanks

Thanks. But it looks we can not find key by redis.keys("some_namespace:*") without custom key builder because the key is finally hashed.

You are right. That's why I told you, "You should use a custom key builder". FastAPI-Cache hash keys using MD5 default, so you cannot identify resources. In general, if you don't have to invalidate immediately, set the TTL value properly.

This is a very common case where we need to invalidate the cache for related GET methods when updating data via POST/PUT/PATCH.
Maybe add some high-level API to invalidate the cache in such cases? Without having to specify a custom key builder. Since in essence the proposed method reveals internal implementation details and violates the encapsulation principle.

@espdev Would you be willing to submit a PR for this?

@vicchi First, I need to look at the code. I think I may if I have some time on my hands.

It seems this PR already adds such functionality. The TagProvider approach looks flexible, but somewhat complicated. Duplicate argument names in items_provider can cause problems during refactoring. But I didn't look too deeply into the architecture of this solution.


MIOpenSoftmax.cl kernel bug

Hi, the softmax backward with mode SOFTMAX_LOG is wrong, please double check the formula.
My cuda implementation for this mode is as belows;  can use this as a formula reference.
__global__ void SoftmaxBwdPerInstance(const float* top_diff, const float* top_dat, float* bot_diff, const int channel, const int height, const int width,
                                      const int spatial_dim)
{
    __shared__ float mid_result[256];
	int batch_id = blockIdx.x;
	int tid = threadIdx.x;
	//in one loop each threadblock will work on one channel

	float channel_dot = 0.f;
	   for(int i = tid; i < channel; i+= blockDim.x)
	   {
	   	for(int h = 0; h < height; h++)
		{
		   for(int w = 0; w < width; w++)
		   {
	           float value = top_diff[(batch_id * channel + i) * spatial_dim + h * width + w];
		   channel_dot = float_sum(channel_dot, value);
		   }
		}
	   }

	   mid_result[tid] = channel_dot;

	   __syncthreads();
	   for(int i = (blockDim.x >> 1); i > 0; i >>= 1)
	   {
	      if(tid < i)
          {
	   	      mid_result[tid] += mid_result[tid + i];
	      }
		   __syncthreads();
	   }
	   channel_dot = mid_result[0];

	   for(int i = tid; i < channel; i+= blockDim.x)
	   {
	   	for(int h = 0; h < height; h++)
		{
		   for(int w = 0; w < width; w++)
		   {
		   int s = h * width + w;
	       bot_diff[(batch_id * channel + i) * spatial_dim + s] = top_diff[(batch_id * channel + i) * spatial_dim + s]  - channel_dot * expf(top_dat[(batch_id * channel + i) * spatial_dim + h * width + w]);
	      }
		}
	   }

Thank you for your feedback! We will address it in next release.

Resolved in 2.1.0


arch/riscv: force using encoding macro for CSR access

Using CSR name depends on compiler support heavily, but CSR encoding does not have this problem. It also make it easy to add new CSR support even if the compiler does not support.
Unify CSR access by using the CSR encoding macro.

Using CSR name depends on compiler support heavily, but CSR encoding does not have this problem. It also make it easy to add new CSR support even if the compiler does not support.

@inochisa Thanks for unifying the CSR access, could you give an example of a CSR Name that differs by Compiler? So we can watch out for similar problems in future. I will test your PR on Ox64 BL808 SBC. Thanks!

Using CSR name depends on compiler support heavily, but CSR encoding does not have this problem. It also make it easy to add new CSR support even if the compiler does not support.

@inochisa Thanks for unifying the CSR access, could you give an example of a CSR Name that differs by Compiler? So we can watch out for similar problems in future. I will test your PR on Ox64 BL808 SBC. Thanks!

@lupyuen see c906_head.S, mxstatus is a important CSR for bare programming. But if we don not use the T-HEAD toolchain, it can not be touched, However, it can be accessed directly from the CSR id. (This patch does not include this change, as it need to write a T-HEAD CSR mapping like this, I will prepare this patch once this get accepted).
Another scenario is for AIA  (This is what I am working now), which need at least gcc version 12 IIRC. This may cause problem when using old gccs.

That's an excellent example. Thanks!


Remove obsolete E2E GHA inputs

Now that we have using and all projects are using that, remove these
inputs
Signed-off-by: Mike Kolesnik<EMAIL_ADDRESS>

I think we missed removing these in the consuming projects tests:
        uses: ./gh-actions/e2e
        with:
          cabledriver: ${{ matrix.cabledriver }}
          deploytool: ${{ matrix.deploytool }}
          working-directory: ./${{ matrix.project }}

https://github.com/submariner-io/shipyard/blob/3f413912e9a6f897e8d832049d954165d2d001ca/.github/workflows/consuming.yml#L53

I think we missed removing these in the consuming projects tests:
        uses: ./gh-actions/e2e
        with:
          cabledriver: ${{ matrix.cabledriver }}
          deploytool: ${{ matrix.deploytool }}
          working-directory: ./${{ matrix.project }}

https://github.com/submariner-io/shipyard/blob/3f413912e9a6f897e8d832049d954165d2d001ca/.github/workflows/consuming.yml#L53

Sent a fix here: https://github.com/submariner-io/shipyard/pull/486


Rename ExampleDeviceAttestationVerifier

Change overview

Rename ExampleDeviceAttestationVerifier to DefaultDeviceAttestationVerifier
since it is now used commonly and becoming fully spec-compliant.

Fixes #11919
Testing

Unit tests pass
Certification integration tests pass

fast track: rename. Pr made by domain owner.


Add list and delete task commands

User guide has been updated. Only dev guide has not been updated yet.

Coverage decreased (-0.7%) to 80.974% when pulling 2b6c3502a7c6cf286fac3c106b2aa9540d78986f on lancehaoh:master into 6a3887da8628068c2de77cc802164957957898bd on CS2103AUG2017-W11-B1:master.

Coverage increased (+1.2%) to 82.864% when pulling ffd3441119ba67cf9b0aeca8a2ad8debdfcc14ae on lancehaoh:master into 6a3887da8628068c2de77cc802164957957898bd on CS2103AUG2017-W11-B1:master.

Coverage increased (+1.2%) to 82.864% when pulling 2bc4487b869c9955b7548f7aa58036b0bd58bd16 on lancehaoh:master into 6a3887da8628068c2de77cc802164957957898bd on CS2103AUG2017-W11-B1:master.

Just help you to resolve some conflicts, but it failed travis before i resolve.

Argh! I did not change any code from my previous commit which pased all the checks. Also, if I remove that import that was mentioned in codacy, the project cannot compile.


change portal url to production

The ms.portal.azure.com is preview UI portal. NOT production.
I would like to change portal url to production url.

Hi @buchizo, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@buchizo : Thanks for your contribution to the Azure documentation! The author, @sethmanheim, has been notified to review your proposed change.

@tysonn Need to find the correct author.

@buchizo - Thanks for the fix!


Patch TS typings for graph methods (Fixes #724)

Update TypeScript typings for QueryBuilder#insertGraph and QueryBuilder#upsertGraph methods to support nested eager relation properties.

Coverage remained the same at 97.175% when pulling f0aefe5a79701dd9a27d2c1bcef6cad13211cc65 on yenbekbay:fix/patch-typings into d2b675746f989054fe466973ed49205757e2a504 on Vincit:master.

Coverage remained the same at 97.175% when pulling f0aefe5a79701dd9a27d2c1bcef6cad13211cc65 on yenbekbay:fix/patch-typings into d2b675746f989054fe466973ed49205757e2a504 on Vincit:master.


Interacting with Horizon's observables is an enormous pain.

The single biggest usability problem I've had getting up and running is working with Horizon's observables.  I had three major problems:

It isn't obvious what's defined and what isn't.

This was extremely frustrating.  We just link to outside documentation on observables, which is reasonable, but has the unfortunate side-effect that I couldn't actually run most examples because we happened not to include some of the operations.

It isn't obvious how to add new operations.

We have no documentation on our site about how to do this.
I still don't know how to do it in the case where you're just writing a script instead of using a build system.
It ended up being easier to just download and rebuild Horizon so I could get a client with the commands I needed pre-included.

It isn't obvious how to access Horizon's Observer class.

You need this because some observer commands check that their arguments are from the same class, so you can't e.g. write hz.currentUser().watch().takeUntil(Rx.Observable.timer(5000)).
I literally ended up writing Observable = hz.currentUser().watch().constructor in my code.

I think we can fix the first one by just providing all of rx-lite out of the box.  I think the gains in terms of convenience far outweigh the costs in terms of code size.
@Tryneus suggested that we could maybe fix (2) and (3) at the same time by letting users pass us the Observable class they want to use, but I don't know if that's reasonable or not.  (We could also just fix (3) by exporting our Observable class somewhere and documenting it.)

Could you describe how to add operators when using a build system? Would be nice with a workaround until this issue is fixed.

Right now, the easiest way if you have webpack or browserify is to import the rxjs/add/* modules, which will monkeypatch Observable. So, for example, to add reduce, you'd do:
import { Observable } from 'rxjs/Observable'
import 'rxjs/add/operator/reduce'
// or in es5:
var Observable = require('rxjs/Observable')
require('rxjs/add/operator/reduce')

// use it like:
myObservable.reduce(...)

Alternately, you can grab the bare operators and use them with .call or the function-bind syntax.
import { Observable } from 'rxjs/Observable'
import { reduce } from 'rxjs/operators/reduce'

// use it like:
reduce.call(myObservable, other, args, go, here)
// or with the :: operator from babel:
myObservable::reduce(other, args, go, here)

I couldn't get monkeypatching to work. It didn't seem to affect the observables created by horizon. I'll give it another go.

It's possible we'll need to export our Observable class. Since we webpack stuff, we're probably using a different Observable than if you also require rxjs. We discuss fixing this by making rxjs a peer dependency in #306 . We also discuss different build options in #611 of which some would have more Observable methods for convenience, and others would be more trimmed down. I think the function-bind syntax is the holy grail solution, but it isn't standards track so it's not worth considering at the moment

I think we should do two things which would be quick and actually can be done for 2.0:

Make rxjs a peer dependency per #306 , so users must bring their own. This will fix the instanceof checks and monkeypatch issues we've seen since the user has full access to the Observable, we aren't compiling it into our library.
Export the Observable class in utensils to solve number 3 above (I'm assuming @mlucy meant Observable, not Observer. the latter is only an interface, not a class that would be getting instanceof checks)

@alf I think I've discovered the main issue for you with Observable not being the same. We don't define it as a peer dependency, but we also have several builds that don't inline it (leaving it to a global called Rx or a commonjs module named rxjs). You can try out the version of horizon from dist/horizon-core.js, which does not have Observables inlined.

@deontologician this is mostly semantic, but I think for (2) we should just export the entire Rx namespace. That way you just have two options:
import Rx from 'rxjs/Rx';
import Horizon from '@horizon/client';
// or
import { Horizon, Rx } from '@horizon/client';

If you only export the Observable class I think you're likely to still run into issues with instanceof checks since people might still try to grab stuff off the "other" Rx instance.
If you're using a build of Horizon that doesn't include rxjs then horizon.Rx === window.Rx. Otherwise horizon.Rx will be whatever was bundled (which could either be the full rxjs or some subset depending on which Horizon build you're using).

I'm poking at this now. I am leaning towards not doing 2 from above. The idea would be to only use the Rx global object, which the user would provide, and we'd have no builds which compile in a version of RxJs.
The problem with exposing our Rx directly is that even that doesn't allow you to reach everything you can get to through require. For examples, require('rxjs/observable/dom/webSocket') isn't reachable from the Rx object exported by @reactivex/rxjs. So it gets us some things but not all still. Alternately we could explicitly expose everything we use internally, but that sounds kinda gnarly.

Ok, nevermind on that. I had a beta.7 version which didn't export dom, but beta 10 does. I think that is a good idea then, we'll re-export Horizon.Rx, and remove deep imports from 'rxjs', just using the kitchen sink version available through global Rx

@deontologician right because when you import 'rxjs/add/observable/dom/webSocket' it now defines Rx.Observable.webSocket, correct?

import 'rxjs/add/observable/dom/webSocket' will add it to rxjs/Observable, whether or not there is a global Rx. The entrypoint for the umd version of Rx automatically calls all of the rxjs/add/* imports, effectively making Rx.Observable a kitchen sink kind of thing (see https://github.com/ReactiveX/rxjs/blob/master/src/Rx.ts)

To clarify my current proposal:

Make rxjs a peerDependency in package.json
Change all deep imports of rxjs modules to just use the global Rx (equivalently, do import 'rxjs/Rx' and tell webpack to fetch that module from the global or from commonjs/amd as appropriate)
Have the default build of horizon bundle the kitchen sink RxJS
Have the horizon-core build get rxjs as an external

@deontologician I think the deep imports are still a good idea. Static analysis tools like rollup allow you to only bundle what you use, but it still requires that you use explicit imports. If the user has rxjs as a dependency and uses a tool like rollup, they should be able to import Horizon without suddenly including all of rxjs in their bundle.

To clarify, I think our own client/src/Rx.js should look a lot like rxjs/src/Rx.ts, exporting all the things we use. Internally, we would import from ./Rx instead of rxjs/Rx. We would still have the default build of horizon bundle kitchen sink RxJS for convenience, but this way horizon-core users still benefit from static analysis because the dependencies are explict.

Ok, so long discussion with @marshall007 on slack, we sorted out the various use cases that are happening here:
target | how to use | es6 polyfills | node polyfills | includes rxjs
---|---|---|---|---|---
dist/horizon-core.js | script tag | no | no | no
dist/horizon.js | script tag | yes | no | yes
lib/* | webpack 1.0 | no | no | no
src/* | rollup/webpack 2.0 | no | no | no
This table doesn't include node.js for the moment. How it'll probably work is that the user will need to provide their own browser api polyfills (like WebSocket) when they are running on node.js
Tasks:

[ ] add jsnext:main for rollup
[ ] ensure rxjs/add/* are no-ops in the horizon-core.js build
[ ] ensure rxjs/Observable returns Rx for horizon.js
[ ] ensure the kitchen sink is bundled with horizon.js
[ ] make rxjs a peerDependency (#306)

@deontologician I guess relevant information is that I'm using horizon as a linked npm module (I need to build it from source until #507 has landed).

@deontologician the more I think about this, the less having a kitchen-sink bundle of rxjs makes sense. I think you can really boil it down to two use-cases:

Application code only references Horizon public API, no Rx references.
Application code also references all or some subset of the Rx API directly.

To meet these use-cases I think we just need:

dist/horizon.js - I want core and a minimal subset of Rx bundled for it to "just work" (browser).
dist/horizon.core.js - I just want core - universal/CommonJS module (browser/Node).
src/* - SystemJS, rollup and/or webpack (ES6)

So far we've seen a fair amount of confusion resulting from operators missing. I'd rather not have to second guess which operators we think will be most useful in order to only get a slight benefit in file size. We can include a subset of operators that cover 95% of use cases, but any individual user is likely to need at least one operator outside that set.
As it is, if you just need one extra operator and you're not using a bundler, it's a pain to extend Observable. The RxJS UMD is not built with operator patching in mind. The nice modular extensibility designed into the library expects you to be using the import system. I'd like to accommodate our <script> tag brothers and sisters without causing them a ton of pain. (If you're using a bundler, then you're ignoring horizon.*.js, so how many operators we bundle doesn't matter to you.)
If a user is sensitive to size, they can move to Horizon core and hand pick their operators. If you're past the point of prototyping and are looking to streamline your app size, I think that's a reasonable stage to pay the complexity cost of rolling your own Observable.
As an aside, if the function bind :: operator were standards track, I'd say it would be worth it to have a minimal/rx-lite build in addition to kitchen-sink and bring-your-own-Rx builds, since :: makes it trivial to extend whatever Observable you happen to be presented with. But, unfortunately, it seems :: is not picking up steam.

@deontologician what I'm saying is that <script> tag users don't really benefit from having RxJS bundled with Horizon. If their application depends on Rx, they should already have another script tag in place referencing rx.js.
In my view, the kitchen sink Rx build doesn't fulfill any use cases. If you don't think the "core and a minimal subset of Rx bundled for it to 'just work'" is a valid use-case then I say we just drop that one too so none of the builds bundle anything from rxjs.

I think we shouldn't continue providing a version which has an essentially random subset of the operators defined.  (Or, at least, I found that decision annoying when using it.)  We should either provide no operators and force people to include Rx before Horizon, or we should provide basically everything.
Assuming there's a way to get at the Observable class inside Horizon, I think bundling it with Horizon makes the first-touch experience much nicer because you don't have to go download anything else to use it.  So, +1 for the original proposal where we provide horizon.js with everything and horizon-core.js with nothing.

just to add a use-case to this:
I've got a navigation of about 20 items, which contain sub-items like:
Football
 - NCAAF
 - NFL
Soccer
 - Euro 2016

I've got an admin interface to change the order of the sports items, to do this I'm altering the array order, adding an order property and then doing this.service.sports.replace(items), which is running on about 20 sports items.
Because we can't do joins, inside the sports-navigation component, I've nested a query inside the subscribe like so:
// sports-nav.component.ts
this.sportsbookService.sports.order('order').watch().subscribe((sports) => {
  this.sports = sports;
  // TODO: Remove when horizon supports JOINs
  // Fetch leagues and nest them inside of sports
  this.sportsbookService.leagues.fetch().subscribe((leagues) => {
      this.sports.forEach((sport) => {
          sport.leagues = [];
      });
      leagues.forEach((league) => {
        this.sports.forEach((sport) => {
          if (league.sport_id === sport.id) {
            sport.leagues.push(league);
          }
        });
      });
    });
});

Because I'm replacing 20 items, the subscribe is triggered 20 times, which is running the inner query 20 times as well.
I'd like to add .debounceTime(50) to the watch() so lots of updates are batched into one reaction in my component :)
Unless it's possible to do a replaceAll() which triggers only one change-feed?

@intellix check out #105 for discussion on aggregating multiple queries like that. In the mean time, something like this should work:
this.sportsbookService.sports.order('order').watch()
  .combineLatest(this.sportsbookService.leagues.watch())
  .map(pair => {
    let [ sports, leagues ] = pair;
    sports.forEach(s => s.leagues = leagues.filter(l => l.sport_id === s.sport_id))
    return sports
  })
  .subscribe(sports => this.sports = sports)

Fixed in #640

Fixed in #638 I suspect.

You're right, I'm a chronic issue mis-numberer

FYI RxJS has let operator which basically serves as a way to add new functionality
without monkeypatching.
https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/operators/let.md
I'd prefer :: but the current proposal is dead AFAK.


Long press variations

Hi Cem,
Thanks for wonderful project. I am a non IOS person. Want to make a keyboard for my language.
is it possible to do following using your project?

Can you show an example if it is possible.
Once again many many thanks.

Hi Al, thanks. Actually yes, I am supporting this behaviour with KeyMenu class, check out KeyMenuType in KeyMenu class, there is and .Horizontal option which gives you extra buttons like behaviour in the system keyboard.


Combination of Required/Optional Query Parameters

I am having some trouble defining a combination of required/optional parameters for a state.
Assume I have a state 'myPage' with three params - param1, param2, param3.
To navigate to the state I would like to require that param1 be defined in the url, while param2 and param3 can be optionally defined. If a user hits '/myPage' I want to handle the case using $urlRouterProvider.otherwise.
$stateProvider
   ...
   .state('myPage', {
      url: '/myPage?param1&param2&param3',
      templateUrl: 'app/myPage.view.html',
   });

$urlRouterProvider.otherwise(function($injector, $location) {
   // handle routing for accessing unknown route
});

I've seen people talk about using a params object with squashing and setting a default value, but I have been unsuccessful in getting that to work.
I believe I could accomplish this using a regex, but this seems error prone.
I also have a requirement that my urls must use query parameters

This is a better question to ask on stackoverflow as its an implementation detail and not a ui-router bug.


Migrate from maven-bundle-plugin to bnd-maven-plugin for finer OSGi meta…

…data
fixes #3842
Signed-off-by: Raymond Augé<EMAIL_ADDRESS>

fix unfortunate commit text...

Hi @frantuma thanks for reviewing :)

The main one: if I am not mistaken the generated JARs manifests do not include anymore an Automatic-Module-Name entry, even if this seems to be configured in the new plugin. This would need to be fixed to consistently provide automatic module name to JDK 9+ modules based envs.

If you perform a binary comparison of the resulting jars before and after (which I have done for all jars) you will note that the Automatic-Module-Name is correctly preserved.

There are differences in the outcome related to Export-Package, Import-Package and possibly Require-Capability for all modules; This is probably ok, and even "better" than what previously provided but I cannot at the moment do thorough tests in OSGi env for all modules to verify their correct behaviour. I guess you are more familiar and up to date with OSGi internals, and actively using swagger-core in OSGi, I would therefore ask you to confirm that all packages have been tested in OSGi env and that they correctly define imports and exports.

This is expected and desired :) I've tested the result in OSGi using the Apache JAX-RS Whiteboard project for which I wish to update the version of swagger if/when this change gets merged/released.
I'm also prepared to keep the metadata up to date and address issues (as time permits) if someone pings me.
Thanks for you time and effort on swagger.

Hi @frantuma thanks for reviewing :)

The main one: if I am not mistaken the generated JARs manifests do not include anymore an Automatic-Module-Name entry, even if this seems to be configured in the new plugin. This would need to be fixed to consistently provide automatic module name to JDK 9+ modules based envs.

If you perform a binary comparison of the resulting jars before and after (which I have done for all jars) you will note that the Automatic-Module-Name is correctly preserved.

There are differences in the outcome related to Export-Package, Import-Package and possibly Require-Capability for all modules; This is probably ok, and even "better" than what previously provided but I cannot at the moment do thorough tests in OSGi env for all modules to verify their correct behaviour. I guess you are more familiar and up to date with OSGi internals, and actively using swagger-core in OSGi, I would therefore ask you to confirm that all packages have been tested in OSGi env and that they correctly define imports and exports.

This is expected and desired :) I've tested the result in OSGi using the Apache JAX-RS Whiteboard project for which I wish to update the version of swagger if/when this change gets merged/released.
I'm also prepared to keep the metadata up to date and address issues (as time permits) if someone pings me.
Thanks for you time and effort on swagger.


Implemented API HTTP requests for Lobby list (GET/POST) and detail view (GET/PATCH/DELETE)

Implemented the list view for Lobby objects, as well as the detail view under the endpoints /api/lobbies and /api/lobbies/<int:pk> respectively.
ENDPOINTS:
/api/lobbies/: This supports both GET and POST requests. GET will return a list of all the lobby objects in the database using Django REST Framework. POST allows users to create new lobbies
/api/lobbies/<int:LobbyID>: This supports GET/PATCH/DELETE requests through Django REST framework. GET returns a detail view for a specific lobby, which PATCH allows a user to edit the contents of the lobby, and DELETE allows user to delete a certain lobby.
TASK COMPLETED:
When the endpoints are finished being implemented -- meaning all the functionality described above is complete.

Created the Lobby list and detail URL endpoints and views, along with a LobbySerializer class for the API app within Chigame.

Closing statement: Added two endpoints /api/lobbies and api/lobbies/<int:pk>. The former gets a list view of Lobbies and support GET and POST requests. The latter gets the detail view of a specific lobby using the lobby's id and supports GET, PATCH, and DELETE requests.

Issue Score: Excellent
Comments:
Great job!
I genuinely really appreciate the format you use when describing what endpoint were made. Directly listing endpoint : available requests : details... is a simple and straightforward way to clearly communicate the most important information for work like this.
Small note, your title is a little off, because you say you implemented the HTTP requests, when what you implemented were the Django Rest Framework Endpoints which support the requests that you later put in parenthesis ie: (GET/POST)
Great work, keep moving forward! We're almost done with the quarter.


Update default CORS Anywhere proxy

I'm not sure how you want to handle the CORS Anywhere proxy in the visualizer this season, but I'd be happy to run it again. I like to separate my CORS Anywhere instances by project, and have origin whitelists on all of them to prevent abuse, so last season's proxy will no longer work. This PR changes the default CORS Anywhere proxy URL to https://lux-eye-s3-cors-anywhere.jmerle.dev/, which has http://localhost:5173, https://lux-eye-s3.netlify.app, and https://s3vis.lux-ai.org as whitelisted origins.
Please close this PR without merging in case me hosting the CORS Anywhere proxy for this season makes me ineligible for this season's prizes.

won't make you ineligible. It was done this way last year, ty.


Fix broken links

Fix broken links
Fix broken redirects to github.com/dotnet/csharplang repo (follow up to https://github.com/dotnet/docs/pull/33305)

Contributes to #35597

Internal previews

📄 File
🔗 Preview link

docs/core/deploying/native-aot/index.md
Native AOT deployment

docs/csharp/tour-of-csharp/index.md
A tour of C# - Overview

docs/fsharp/using-fsharp-on-azure/queue-storage.md
Get started with Azure Queue Storage using F#

docs/orleans/streaming/index.md
docs/orleans/streaming/index

docs/standard/serialization/system-text-json/migrate-from-newtonsoft.md
Compare Newtonsoft.Json to System.Text.Json, and migrate to System.Text.Json

docs/standard/serialization/system-text-json/preserve-references.md
How to preserve references and handle or ignore circular references in System.Text.Json

docs/standard/serialization/system-text-json/supported-collection-types.md
"Supported collection types in System.Text.Json"

docs/standard/serialization/system-text-json/use-utf8jsonreader.md
How to use Utf8JsonReader in System.Text.Json

@BillWagner I'm assuming the redirection warnings will only appear in this PR and once we merge this, they're gone forever. Because this PR actually fixes those redirects.


GA: Pass Zonal failure test

we should run a test of shutting down an entire AZ of a management cluster running hypershift components and see if it passes failure testing. Any gaps should be closed before GA.

We'll track this as QE for multi-zonal spread (https://issues.redhat.com/browse/HOSTEDCP-195)

Note: IBM will still need to perform and pass it's zonal failure test suite.


Remove constructor and instead explicitly called one-time method

Issue
Deploying evm bytecode that requires initialization via a constructor to a specific address is a very unnatural operation and hard to specify across clients. On the other hand, deploying evm runtime bytecode to a specific address is easy, but lacks any initialization you might want from the bytecode.
To get the ease of the deploy of runtime bytecode along with the initialization we require from the constructor, we plan to move the code from __init__ to an explicitly called method init. The method signature will be the same and the body will be almost 100% the same except that there will be a flag that prevents it from running more than once (assert not self.initialized).
The EIP will be updated to say move CASPER_CODE to CASPER_ADDR and then execute a call init with the list of params.
Proposed Implementation

move contents of __init__ to init
create initialized var/flag that is asserted False and then set to True in init
Migrate testing setup to call init explicitly and make sure all tests pass
Test explicitly that init can only be called once. Simple but very important.

addressed in #137


use Java 11 in github actions

Fixes failing builds due to incompatible class files in xtend generation

If we use Java 11, will it be still possible to use bsp4 and bsp4j with Java 8?

If we use Java 11, will it still be possible to use bsp4 and bsp4j with Java 8?

I think we wouldn't be able to use Java 8, so I would hesitate to merge this :thinking:  We could instead add a separate verify job for JDK 11?

I'm trying to figure out how these even broke. #176 would be a good candidate, but reverting to before that commit doesn't fix it. Not even to old 2020 commits. So what is actually going on here?
Meanwhile, we could use JDK11 only for the verify job but not release?

I'm trying to figure out how these even broke. #176 would be a good candidate, but reverting to before that commit doesn't fix it. Not even to old 2020 commits. So what is actually going on here?
Meanwhile, we could use JDK11 only for the verify job but not release?

Probably both jdk 11 and 8 are needed just in case, otherwise the release might fail even if check runs ok.

obsoleted by #185


Fixes 'loaded' class being added multiple times to lazy-loaded images

Noticed this when using the component with dynamic images that allow browsing through multiple ImageGalleries. The images will end up with a class like "loadedloadedloadedloaded", depending on how many times the individual image was viewed, which can cause issues with the .loaded css class and prevent the image from being displayed.

@heldinz Thanks for the pr.


[FEATURE]: allow listening to voices snippets before generating audio.

In bark, when you open the tab, you can select the language and the voice, I find myself generating audio just to test the voices, I think there should be a little checkbox thing that let you hear the selected voice before generation.

It was not possible before, but could be now, good idea!
On Sun, Oct 29, 2023, 2:51 AM AIhasArrived @.***> wrote:

In bark, when you open the tab, you can select the language and the voice,
I find myself generating audio just to test the voices, I think there
should be a little checkbox thing that let you hear the selected voice
before generation.
—
Reply to this email directly, view it on GitHub
https://github.com/rsxdalv/tts-generation-webui/issues/208, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTRXIYYZC6NSQ3X66CZHOTYBWLBZAVCNFSM6AAAAAA6UNCTGWVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DMNZXGQ2TEMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Implemented this in the React UI.


Attest Actions uploaded artifacts

Hello!
What is expected
It would be great if we could attest directly artifacts uploaded by actions/upload-artifact by passing, for instance, the artifact-id output to this action.
Why is this needed?
Although this action now supports wildcards as subjects, which is good for software that outputs multiple artifacts (for instance, a pipeline building ffmpeg usually outputs ffprobe, ffplay and ffmpeg), sometimes the build artifact is a single piece but with multiple file dependencies (software with dlls or web applications with chunk splitting and multiple .js bundles), so you want to sign it all "as a whole", not as individual files.
Current workaround
Right now, a good workaround for this would be to zip or tar all the files and sign the compressed output, and then upload it as an artifact, so consumers of the software get the same file that was signed. However, that creates a double compressed file, which is not always convenient and annoying, but there's no way to avoid GitHub Actions Artifacts API to upload artifacts as zip.
Hence, it would be awesome to directly attest those zips/artifact ids that GitHub Actions Artifacts provides.

The release of v2.0.0 improves this in some way, since now a single attestation could be created of a group of files. However, still not 100% the original request.

@ferferga is your goal to create an attestation which references the archive created by actions/upload-artifact, or one which references each of the constituent files contained in the upload archive?

@bdehamer The former

@ferferga I updated the upload-artifact action so that it will output the digest of the archive that is created. This means that you can now string together the upload-artifact and attest-build-provenance actions with something like this:
- name: Upload build artifact
  id: upload
  uses<EMAIL_ADDRESS>  with:
    path: "dist/*"

- uses: actions/attest-build-provenance@v2
  with:
    subject-name: artifact.zip
    subject-digest: sha256:${{ steps.upload.outputs.artifact-digest }}

@bdehamer This is awesome, thank you very much! Eagerly waiting for the release!

The upload-artifact release with this feature just went out so I wanted to come update this issue. Will work to get an example added to the README.

I'll leave this open then, feel free to close when you have ticked all the checks internally.
Thank you very much again for the quick implementation and updates!


feat: add --resource option to update subcommand

Signed-off-by: Jian Zeng<EMAIL_ADDRESS>ref #147

Codecov Report

Merging #546 (21eaf4e) into main (7d63d2a) will increase coverage by 0.57%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #546      +/-   ##
==========================================
+ Coverage   60.56%   61.13%   +0.57%
==========================================
  Files          99       85      -14
  Lines       12673    12563     -110
==========================================
+ Hits         7676     7681       +5
+ Misses       4997     4882     -115

@knight42 Looks good. However, integration tests about the update subcommand may be necessary.

Okay! I will file another PR to add the integration tests.


Palettes cannot be generated with no images

When trying to create a palette with no images, convimg gives the error [error] No images to convert for palette 'night'. It would be useful if you could generate a palette from only fixed index colors. I use this for dynamic palettes so that I don't need multiple copies of sprites in different colors, and currently, I have to include a "dummy" image to get the palette to generate.

Completed on the feature/features branch. Feel free to build and test if you want.


Delete all responders and related configuration

The ADR triad is not meant to be implemented in an agnostic way, but
rather implemented exactly as necessary for each use case. This makes
general purpose responders pointless, since the responder attached to
each action (or possibly groups of actions) will generate an exact
response based on the requirements of the use case.

I'm not certain this should be immediately merged down to the simplified branch. In particular, I would like to find a reasonable way to preserve the content negotiation that is available in FormattedResponder.
Anyone have suggestions on how we can create content negotiation within the context of formatters instead of responders?

@shadowhand Maybe shift them to middlewares placed into the pipeline after ActionHandler ?

@elazar no, the responder attached to the action should do the formatting. ActionHandler should always produce a full populated response.

@shadowhand Fair enough. In that case, I guess we can look at either composing supporting classes or using traits in responder classes.

@shadowhand It seems to me that content negotiation belongs in the responders because it's effectively choosing what format to use, which implies things like Content-Type headers, etc. in the response.

@shadowhand And besides, format($content) just returns a string, and the type() method doesn't take any arguments, so without some major changed to FormatterInterface, I don't see how you could implement content negotiation there at all.

@elazar will do responder doc updates here before merging.

@bvisness I believe your concerns were addressed in #78

@elazar docs have been updated in #79

👍


Add HoverLight script settings in MRTK profile for each cursor

Describe the problem
Hello everyone, maybe I missed it (if yes documentation is not clear), but I would like to change the settings of the hoverlight scripts of the cursors.
Describe the solution you'd like
Would it be possible to have the possibility to change these settings in the input profiles?
Additional context
Specifically I want to disable it for eye tracking and set radius for hand ray. The only I found to change that is to create a script that will find the script at run time, it's quite dirty.
Thank you

@cre8ivepark @Cameron-Micka is this something you guys could help answer?

Hi @benjamincoven, the HoverLight (and ProximityLight) settings are driven from a HoverLight (or ProximityLight) component that lives in the cursor prefab that each pointer instantiates. I would recommend making a prefab variant of the cursor you wish to modify, and a prefab variant of the pointer you wish to modify, then connect the new cursor variant to the new pointer variant and specify that new pointer variant in your input profile.
Typing also those steps out it sounds laborious, but should be auto-update safe if you take future MRTK updates. We could push overrides to HoverLight/ProximityLight settings somewhere in a profile, but that could cause extra settings clutter. But, I could be convinced either way.
Note, you can also specify HoverLight and Proximity light setting overrides on a per material basis in the material inspector.

If I change the HoverLight and Proximity Light, it would whange it for all pointers isn't it (hands and eye)?
The first solution is what I was looking for. Thank you.

Yes, it should! I haven’t taken a look at how many cursors are used among all the HoloLens pointers recently (last I checked it was 2 or 3), but changing the HoverLight & ProximityLight settings in those cursor should apply the change globally.


Add support for simplest debayer algorythm (Superpixel)

The superpixel algorithm is required.
I can do it manual, from .raw_image, but other postprocess steps is problematic.
This not for speed, but for the processing oversampling image.
Add it support, please.

rawpy does not implement debayer algorithms. Please ask the authors of the underlying libraw library for that.


systemd --system flag simpler?

I noticed that nowadays, systemd has the --system flag to force it to work as the system instance even if the PID is not 1. Would that work here?

Thank you for your interest in NixOS-WSL! I could swear I looked into the --system flag and there was some reason against it, but I honestly cannot remember if that is the case or whether I just overlooked that option.
Meanwhile, I left my short detour into Windows lands - hence (as you already might have guessed by the late response), my interest in investing energy into this project is fairly limited. I'm happy to accept contributions thought.

Hah, same here ;) And I also found out that the --system thing is just for testing and it's not actually useful for running systemd. So nothing to be done about it, although there is a light-weight alternative to genie now: https://github.com/sr229/wsl-systemd
Anyway, I also did a short detour in Windows and am now trying to make NixOS my laptop home - not easy!


Invalid Date

We need to deal with this "Invalid Date" situation in some kifu.

http://gokibitz.com/kifu/m15BCc7S

It looks like this is caused by games that span multiple days.
Property:	DT
Propvalue:	simpletext
Propertytype:	game-info
Function:	Provides the date when the game was played.
		It is MANDATORY to use the ISO-standard format for DT.
		Note: ISO format implies usage of the Gregorian calendar.
		Syntax:
		"YYYY-MM-DD" year (4 digits), month (2 digits), day (2 digits)
		Do not use other separators such as "/", " ", "," or ".".
		Partial dates are allowed:
		"YYYY" - game was played in YYYY
		"YYYY-MM" - game was played in YYYY, month MM
		For games that last more than one day: separate other dates
		by a comma (no spaces!); following shortcuts may be used:
		"MM-DD" - if preceded by YYYY-MM-DD, YYYY-MM, MM-DD, MM or DD
		"MM" - if preceded by YYYY-MM or MM
		"DD" - if preceded by YYYY-MM-DD, MM-DD or DD
		Shortcuts acquire the last preceding YYYY and MM (if
		necessary).
		Note: interpretation is done from left to right.
		Examples:
			1996-05,06 = played in May,June 1996
			1996-05-06,07,08 = played on 6th,7th,8th May 1996
			1996,1997 = played in 1996 and 1997
			1996-12-27,28,1997-01-03,04 = played on 27th,28th
			of December 1996 and on 3rd,4th January 1997
		Note: it's recommended to use shortcuts whenever possible,
		e.g. 1997-05-05,06 instead of 1997-05-05,1997-05-06

http://www.red-bean.com/sgf/properties.html
Not exactly sure how I'm going to handle this.


drectangle with the size < 1

I was trying to use drectangle with some normalized coordinate system, where x/y are in range 0..1. This allows me to make processing independent from image resolution, because modern CCTV cameras have multiple output video streams of different resolution
Current drectangle contract says that its size can't be less than 1:
 drectangle centered_drect (
        const vector<double,2>& p,
        double width,
        double height
    );
    /*!
        ensures
            - returns a rectangle R such that:
                - center(R) == p
                - if (width < 1 || height < 1)
                    - R.width() == 0
                    - R.height() == 0
                    - R.is_empty() == true
                - else
                    - R.width() == width
                    - R.height() == height
    !*/

Is there any way to change this? It would be nice to have rectangle primitive without such strong restriction and inventing the wheel with some new rectangle class does not look interesting
The main problem I see are right() and bottom() values. Now they are pointing to a positions inside rectangle. OpenCV's implementation makes simple : right = left + width, while dlib's: right = left + width - 1
I can imagine some other situations where this can be usefull:

DNN can produce drectangles (YOLO, SSD for example are working this way)
some affine-transform of drectangle

Yeah, the drectangle is weird in that way.  But it's because the rectangle, that has integer coordinates, works this way.  And this makes them behave in the same way.  For example, a rectangle(1,1,1,1) is the rectangle that contains exactly the pixel point(1,1).  If it were defined the opencv way the integer rectangle object would have an odd API.  Since the dlib::rectangle has been around forever we can't change this even if we wanted to anyway.
The first version of the drectangle I made behaved as you suggest, which is how you would expect something with continuous coordinates to work.  But then when it's converted to or from dlib::rectangle objects it gets all weird and wrong, giving bad and surprising behavior in a number of cases.  So I changed it to work the way it does now to make dlib::rectangle and dlib::drectangle compatible.
Although, the general use case for dlib::rectangle and dlib::drectangle is to represent boxes in images, where the coordinates are always integer valued and never in the range 0..1.   For that it's convenient.  But yeah, as a general rectangle the drectangle is weird.

Looks like the only solution is to have a new class copied from drectangle with minor changes.
Do you think it will be useful in dlib now?

Maybe.  It might just be more confusing if you add another.  You would have to remove any conversions between a new class and rectangle and drectangle.  I can see that being a source of confusion.  There are also probably some of the utility functions for drectangle that don't make any sense for a general rectangle.
Anyway, I'm not sure.  If you want to propose something I'll take a look :).

What if we will change drectangle's interface this way?
        template<bool inside=true>
        double right()  const { return inside ? r : r + 1;}

This will make it's default implementation work the same way as original and leave it 100% compatible with rectangle, but will also allow having size < 1

How does someone use that though?  They call all the regular utility
functions and get the old behavior.  width() still uses the old behavior,
etc.

i am thinking, if we can change drectangle's internals to make it work with size < 1 and keep it 100% compatible with rectangle.
drectangle can be constructed from dlib::centered_drect
drectangle r = centered_drect(dpoint(1,1), 0.5, 0.5);

this will not produce any error messages and will make l=1.25, r=0.75, t=1.25, b=0.75, is_empty = true, width()=0, height()=0
now width = r - l + 1. what if we will change drectangle's behaviour to have width = r - l, and right()=r-1; ?
this way we will  keep it compatible with rectangle and all other functions
yes, this way we should also change some other interface functions (is_empty, width, height, right, left ...), but their result will be identical to current implementation except the situation when size < 1

That seems even more weird than the current behavior though.  Say you make a drectangle by giving it two points.  Then you go ask it what the right boundary is and it subtracts 1 from the right boundary value you supplied in the constructor.  That's way worse :/

I mean, fundamentally, right now a drectangle is just a set of 4 numbers.  It doesn't modify them or do anything funny to them.  It's just that the width() and height() member functions have this odd behavior because of compatibility requirements with the discrete coordinate system used by rectangle.

But you can still put whatever values you want in the drectangle.

Thank you for the explanation. Looks like there is no simple and compatible way to modify the drectangle for this goal

No problem.  I already when through all this trying to make the drectangle like you would expect but it just makes all these compatibility problems with the rectangle :(
You would be better of using an entirely different object to do this kind of stuff.


Resolved rotation issue in TwoHandManipulatable script

Overview
Issue:
If we change the rotation axis constraint at run time, it does not make any difference in the behaviour.
Fix: Reinitialize the rotate logic with the new rotation axis constraint every time the rotation constraint property is set.
Sample:
I have duplicated the TwoHandManipulationTest scene as TwoHandManipulationTest_Fix scene and have added the following game object into the scene content:

Model_Bucky_Rotation_Constraints_Test: This has a test script(TestRotationConstraints) attached to it and is intended to depict the solution to the issue.

Changes
Changed TwoHandManipultable.cs
Added TestRotationConstraints.cs
Added TwoHandManipulationTest_Fix.unity

 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.:x: shubhamarora28 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

You can either rename it as an example and remove the fix suffix, or remove the test scene all together. Up to you.

I'm good with not adding a new test scene.

@davidkline-ms The test scene I had created has a game object(Model_Bucky_Rotation_Constraints_Test) that depicts the capability of TwoHandManipulatable to modify the rotation constraint at run time.
Instead of adding this as a new scene just for this fix, I was thinking if I can replace the original TwoHandManipulationTest scene with the one that I have added. Will that be okay?

Does this fix also need applying to vNext ? @davidkline-ms @StephenHodgson

We haven't ported it yet.

@shubhamarora28, as long as we don't lose functionality in the existing example scene, I think that sounds fine.
Thanks!

Does this fix also need applying to vNext ? @davidkline-ms @StephenHodgson

We haven't ported it yet.

It should definitely be added to #2465 for tracking.

@StephenHodgson @davidkline-ms Pushed a commit with all the changes.


Questions about train/test split

Hello, thank you very much for your excellent work. I noticed that you used pre-trained models like CasMVSNet in your code. I was wondering if these models were trained by yourself or if they are officially released ones. Additionally, on which scenes of the DTU dataset were they pre-trained?

Hi, for pre-trained MVS models, we use the officially released models.
I remember they use same train-test split to train their models, here is what I found for TransMVSNet: train.txt, test.txt.


feat: insert expect

[x] get at least a couple of non-matching rows in test output
summarize,
[x] diff in matching : explain why a particular part of the rule is not matching
[x] integrated schema matching as a header (to allow for projection for the following rules, if position based)
[ ] introduce a blocking key to avoid rule collision (a specific set of field are in priority for matching, which reduce the candidate rules)
[ ] add expectAtLeast

validity:

[x] a row is valid, if it matches only one rule, or if the rules can be distributed between more rows.

case class Person(name, age)

val ds:Dataset = // Person("toto", 13), Person("tata", 13)

ds.expectAll(row(__, 13), row("toto", __)) // should not fail
ds.expectAll(row(__, 13)) // should fail

ds.expectAll(row(__, 13).allowMultipleMatches) // should not fail

summarize :
Due to the potential large volume of data, and low volume of rows, the idea is to keep certain rows to explain the failing test :

a set row that are valid are keeped, scored with closeness to rules that were not matching
a set row that didn't match any rules, scored with closeness to rules that were not matching
The purge works per rules, keeping at least N values in the two sets, depending on closeness

@ahoy-jon key value implicit conversion is hard to create, the value conversion take the lead if I have both :
@SuppressWarnings(Array("scalafix:DisableSyntax.implicitConversion"))
implicit def valueConversion[T](t: T): PositionalValueMatcher.Value[T] = PositionalValueMatcher.Value(t)

@SuppressWarnings(Array("scalafix:DisableSyntax.implicitConversion"))
implicit def keyValueConversion(kv: (String, PositionalValueMatcher)): GlobalValueMatcher.KeyValue =
  GlobalValueMatcher.KeyValue(kv._1, kv._2)

Even if I put the valueConversion in a LowPriorityImplicits trait.

@ahoy-jon I would like a review on the current state of this PR. I think we can improve error handling, but I don't know exactly how. I would also need more insight about blocking keys based on the current state.


feat(Card): unify padding to 16px for all breakpoints

This way it's aligned with the behaviour of Tile and looks better when only text is in sections (in Desktop viewport)
Before (actual https://www.kiwi.com/en/help) 😿

Now 😃

@vepor @williamkolmacka Instead of downsizing the Card to 16px, could we instead adapt the Tile to be also 24px on desktop viewports?


Speaking Rate

While running voiceOver tests using guidepup - we have observed that speaking rate is very low because of which our tests are taking too long. Could you please let us know if there is a way increase speaking rate in guidepup.

Hi @KPrerana4 👋
Sorry for the slow reply. Afaik Guidepup currently configures VoiceOver (while it is being automated) to be set to the max speaking rate, see https://github.com/guidepup/guidepup/blob/main/src/macOS/VoiceOver/configureSettings.ts#L62 but open to suggestions!
One reason it can be quite slow is waiting for the full spoken text, if all you care about is the initial spoken text and not the "next page" of additional command information / description then you can use the capture option when using the start method to only capture initial text:
voiceOver.start({ capture: "initial" });

This is typically a fair bit faster.
In the meantime will have a look to see if there are any other options that could be used to speed it up - PRs welcome if have any ideas!

Ok, I've found that we can eliminate the delay between the main announcement and the subsequent hint speech which saves ~400ms per interaction.
I've had a play whether different voices are faster etc. and if can abuse the speach rate to be over 100%, but there doesn't seem to be much can do here. There might be some extra ms savings if reduce verbosity, or start disabling things like punctuation verbosity, but think it is minimal unfortunately.


Version conflicts

As reported here: https://x.com/fucha_co/status/1736882391317352859?s=20
Needs testing and fix

Same error here, i can't continue deploying


OIDC_id_token_{payload,serialized} header keys should be configurable or avoid '_'

when using OIDCPassIDTokenAs "claims" or "serialized", the header key seems to be non-configurable.
This causes issues in the python uwsgi world (which for security reasons doesn't honor "_" in header keys.) (see also https://github.com/zmartzone/mod_auth_openidc/issues/71).
It would be nice if these headers were configurable, or avoided problematic "_".
Thanks!

Even if this configurable prefix is implemented, you'd still have to deal with the underscores in <PREFIX>id_token and <PREFIX>access_token. Perhaps it is better to rewrite the headers using mod_headers, converting the underscores to dashes?

Does using mod_headers work for you?

Indeed, I did a mod_headers rewrite and it worked fine.   Thanks for the suggestion, and the good work!


Returns a RunArtifact from UploadModelAsync

Resolves
Fixes #292
Description
Returns a RunArtifact from UploadModelAsync

This is ready for a review.

I'm going to merge this PR given that it contains migrations and changes that will cause merge conflicts for other contributions. I don't want to cause any conflicts on current or new PR's. Let me know if you have any comments or suggestions to this PR and I would be happy to open a new PR to address any of them :)


List RPM content without in-image rpm util for FROM scratch

CLOUDBLD-4095

Signed-off-by: Robert Cerven<EMAIL_ADDRESS>Maintainers will complete the following section

[x] Commit messages are descriptive enough
[x] Code coverage from testing does not decrease and new code is covered
[x] JSON/YAML configuration changes are updated in the relevant schema
[n/a] Changes to metadata also update the documentation for the metadata
[n/a] Pull request has a link to an osbs-docs PR for user documentation updates
[x] New feature can be disabled from a configuration file

rn updated: List RPM content without in-image rpm util for FROM scratch

rn updated: List RPM content without in-image rpm util for FROM scratch


repeat via attributes

Discussed in https://github.com/Jinntec/Fore/discussions/38

Originally posted by JoernT June  4, 2021
repeat attributes
fx-repeat element is fine but does not work out in some use cases.
Consider this:

Using fx-repeat as is would force:

    <fx-repeat ref="items">
        <template>

{.}

        </template>
    </fx-repeat>

Not at all want you want - breaks content-model of
 and may even break styling or require workarounds.
So in consequence what we'll need is:

    <template>

{.}

    </template>

Possible implementation
At initial refresh the fx-form:

querySelectorAll('[data-ref]')
create fx-repeat for each of them like so:

<fx-repeat ref="items">
::shadowDOM <template>...</template

1

2

3

</fx-repeat>

fx-repeat would become an invisible wrapper around the actual repeated element and:

move data-ref to fx-repeat/@ref
move <template> to shadowDOM of repeat
unroll items

Same principle should work for tables or other similar structures.

A working solution has been pushed to dev branch. A new demo illustrates usage with different tables and lists.
However there's a limitation: repeats via attributes cannot be nested at this point in time. As the implementation gets significantly more complex when nesting tables i've decided to wait for user feedback and defer this step until a use case comes up. This limitations does NOT apply to usual repeats - those can be nested within a table created via attributes.
A second reason to defer implementation of nested tables is their rather bad performance in browsers - it takes significantly more time for a browser to paint tables than e.g. nested div structures. This mostly occurs when tables have no fixed dimentions and need several paint runs to get calculated dynamically expecially when they contain other dynamically layed out elements like select elements.
implementation notes
Instead of merging the functionality now a new fx-repeat-attributes is used. This share significant portions of the implemenation with fx-repeat and might be merged at a later stage again. This road was mainly taken to not interfere with the current fx-repeat element implementation.

Here is the user feedback on "repeats via attributes cannot be nested". I have a sequence of <subject>s, each containing a sequence of <ref>s. I want to make a table for each <ref>, like this:
	<fx-repeat ref="instance('article-categories')/subject">
	  <template>

{@title}

			 <template>

<EMAIL_ADDRESS>

			  </template>

	  </template>
	</fx-repeat>

It would be nice if at least an error message is generated in this case. It took me a few hours before I found this issue.

I'm sorry you had trouble. I'll add a clear message on the demo to say that data-ref attributes can only be used as outermost repeated structure.
Btw, usually there's no hard need for tables nowadays as it's always possible to use a structure of 'div' elements and use CSS Grid on them. The only real exception is when you want table headers - these can be difficult to achieve with above method.
Anyway - i apologize for your trouble and try to be more clear on that.

Thank you, Joern. I did end up using display: table etcetera on nested divs.
I noticed there is a 'header' slot on fx-repeat. This is nice, but it is always shown. Is there a way to not show the header slot if the fx-repeat/@ref is empty?
(And is there a way to render an HTML fragment conditionally, something like fx-if?)


Add a Security Considerations section in the Periodic Background Sync spec

See also https://github.com/WICG/BackgroundSync/issues/169


command decorations in the overview ruler don't update when command color is changed

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

change the workbench color customizations for terminal commands
🐛  the decorations in the overview ruler don't update

https://github.com/xtermjs/xterm.js/issues/3729


feat: add pavius/impi

pavius/impi: Verify proper golang import directives, beyond the capability of gofmt and goimports
$ aqua g -i pavius/impi

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
$ impi --help
usage: impi-v0.0.3-darwin-amd64 PACKAGE [PACKAGE ...]
  -ignore-generated
        ignore files generated by 'go generate'
  -local string
        prefix of the local repository
  -scheme string
        verification scheme to enforce. one of stdLocalThirdParty/stdThirdPartyLocal
  -skip value
        paths to skip (regex)

Reference

README

https://github.com/pavius/impi/blob/master/README.md

Thank you!

v4.31.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.31.0


Added Rsa solver

🛠 Issue (Number)

Closes #825
Description
Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] 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

Checklist:

[x] I have made this from my own
[ ] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@TusharKesarwani please review my PR

@harshit-paneri pls review my PR


Allow http proxy on bootstrap

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Hi @feltra, thanks for the PR. Can you please rebase against our latest master branch? There are a bunch of commits here that should not appear.

can you please have a look at the failing travis jobs and rebase against our latest master branch and squash the commits?

@bastelfreak Looks like tests are passing, and you can squash commits when merging.
Is anything else preventing this PR from being merged?

Hi. This branch doesn't cleanly rebase on our current master. A squash via the web UI triggers a merge, even if CI would then fail. Please do a rebase on the command line and forcepush to this branch / resubmit it as a new PR.

@bastelfreak I cannot push to this branch but I submitted #488 which is a merged version.


Logging feature issue #246

Description of changes
Created a new logging instance for future logg messages.
Technical details
Heavily adapted from Cellrank and Scanpy.
Additional context
Will add logg.info() messages in every method where it is needed in the next days/weeks.

About the rich module: it is not that trivial as I thought, so I reverted the changes that I introduced by replacing print() with logg.warning(). I'll open a new issue for this: introduce coloured messages into our logging instance.

Do the messages appear red? I modified the LogFormatter and added some colours for different message types but it does not seem to work on my laptop. Also there is a safety issue: Vulnerability found in ipywidgets version 7.6.6. Any ideas?


Sharing weights for CBNet

Hello, regarding the comparative experimental design of shared parameters, I would like to ask how to implement parameter sharing in the code?

in caffe2，the parameter is consistent with the name of the network in the code, so just keep the name of two backbones the same发自我的iPhone------------------ Original ------------------From: 邱锋  @.>Date: Mon, Sep 13, 2021 10:27 PMTo: PKUbahuangliuhe/CBNet @.>Cc: Subscribed @.***>Subject: Re: [PKUbahuangliuhe/CBNet] Sharing weights for CBNet (#23)
Hello, regarding the comparative experimental design of shared parameters, I would like to ask how to implement parameter sharing in the code?
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
[
{
@.": "http://schema.org",
@.": "EmailMessage",
"potentialAction": {
@.": "ViewAction",
"target": "https://github.com/PKUbahuangliuhe/CBNet/issues/23",
"url": "https://github.com/PKUbahuangliuhe/CBNet/issues/23",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
@.": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]


Metrics Endpoint slow with large number of Workflows

What happened:
With a large number of workflows, the /metrics endpoint is slow to respond. This with legacy metrics disabled and no custom metrics.
$ time curl http://<IP_ADDRESS>:8080/metrics
# HELP argo_workflows_count Number of Workflows currently accessible by the controller by status
# TYPE argo_workflows_count gauge
argo_workflows_count{status="Error"} 0
argo_workflows_count{status="Failed"} 5
argo_workflows_count{status="Pending"} 0
argo_workflows_count{status="Running"} 1
argo_workflows_count{status="Skipped"} 0
argo_workflows_count{status="Succeeded"} 12349

0.01s user 0.01s system 0% cpu 7.173 total

The workflow-controller is running unbounded on a latest generation AMD Epyc CPU, much faster than you'd find in your typical AWS or GCP instance, however I assume that much of the delay is due to querying Kubernetes objects. A response time of less than 10s is often expected for a Prometheus metric, which means that this will top out at a couple of thousand more workflows.
What you expected to happen:
This is not necessarily a bug, but it is a scalability concern, and should be noted in scalability documentation.
How to reproduce it (as minimally and precisely as possible):
Create a lot of workflows. Query /metrics.
Environment:
On prem.
argo: v2.7.3
  BuildDate: 2020-04-15T22:52:59Z
  GitCommit: 66bd0425280c801c06f21cf9a4bed46ee6f1e660
  GitTreeState: clean
  GitTag: v2.7.3
  GoVersion: go1.13.4
  Compiler: gc
  Platform: darwin/amd64

Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Thanks for this @salanki, I have a fair idea of what the issue is here

@simster7 I have a solution to this I'd like to discus than would design-on scalability problems.

Sure, let's discuss

ping me whenever

@simster7 do you want to own this?


Update from jquery 1.* to jquery 3.*; fixes #1012

Update jquery from its current unsupported 1.* branch
to the current 3.* branch.
We use the gem 'jquery-rails' to bring in the JavaScript library jquery,
and keep us up-to-date. However, jquery-rails does not update between
major branches of jquery. The jquery version brought in is determined by
"app/assets/javascripts/application.js", and it previously said:
//= require jquery

This means we're bringing in the no-longer supported 1.* branch, not the
current 3.* branch.  The jquery 3 branch was released on June 9, 2016,
so jquery 3 has had time for people to get ready for it.
This commit changes the require statement from "jquery" to "jquery3",
which is how you request the newer 3.* branch. This does create
incompatibilities with extremely old web browsers.
However, the jquery 3.* branch is designed to support the
following web browsers, and that seems to be "good enough"
for most users of this application:

Internet Explorer: 9+
Chrome, Edge, Firefox, Safari: Current and Current - 1
Opera: Current
Safari Mobile iOS: 7+
Android 4.0+

Jquery 3.* has a number of interface changes, but as far as I can
tell we aren't affected by any of them.  We've generally tried to
follow the jquery documentation recommendations, and by doing so
I think we've avoided many of the potential breaking problems.
My thanks to Guy Podjarny from Snyk for alerting us to our use of
jquery 1., and recommending that we switch to the 3. supported
branch instead.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

Our suite for testing our javascript is not as good as it should be so a pass of the tests does not mean it is working flawlessly.  If you can attest that you have tested this locally and had no issues.  I am happy with merging.  I will also try to test when I get time.


Wipe out source code for easier review on next bigger updates

Agreed to wipe out code base first, but keeping history at the stand-up meeting ;)


failed to ping localhost:25565 : read tcp <IP_ADDRESS>:56970-><IP_ADDRESS>:25565: read: connection reset by peer

Describe the problem
I just repeatedly get this error

Nov 06, 2023 9:56:05 PM io.netty.channel.DefaultChannelPipeline$TailContext exceptionCaught

WARNING: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.

java.lang.RuntimeException: Unable to access address of buffer

	at io.netty.channel.epoll.Native.read(Native Method)

	at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.doReadBytes(EpollSocketChannel.java:678)

	at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.epollInReady(EpollSocketChannel.java:714)

	at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe$3.run(EpollSocketChannel.java:755)

	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:380)

	at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:268)

	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)

	at java.base/java.lang.Thread.run(Unknown Source)

Container definition
version: "3.8"

services:
  mc:
    image: itzg/minecraft-server
    tty: true
    stdin_open: true
    ports:
      - "25565:25565"
    environment:
      EULA: "TRUE"

      VERSION: "1.8.8"

    volumes:
      - /root/storage/minecraft/testv3:/data

Container logs
_minecraft-mc-1_logs.txt

my bad for not thinking before sending this turns out i just needed to add the java8-jdk tag and everything got fixed 🤦♂

Hey @Colon101
I get the same error but don't understand how you fixed it. Would you mind explaining where you added the "java8-jdk tag" and what code is involved? Cheers


rename wbb to p4rtutils and move to internal/

Find a better place for the p4rtutils

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 69.405%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1656

Relevant Lines:
2386

💛  - Coveralls


info-beamer-nodes-seamless pi only?

Trying to run the open source version out on ubuntu, but when trying out the seamless sample you have(which works on the pi) gives me the following:
info-beamer pi version required
Is there a version of this for the non-pi info-beamer?
Thanks

The open source version uses software decoding for all videos. You'd have to open the first video, step through it frame by frame. You can use the util.videoplayer helper function for that, see here. Once video:draw(...) returns false (= video ended), open the next video and switch to it.


WANT TO SEE HOT PICS WITH ME? 💋 💋 💋

WANT TO SEE HOT PICS WITH ME? 💋 💋 💋
👇 👇 👇
https://is.gd/ms4xm3

@beaucarnes Can you please ban this user?


Basic: Add minimum availability version for visionOS

This fixes an issue where diagnostics were not emitted for missing availability attributes when compiling for visionOS.
Resolves rdar://127073463

@swift-ci please test


add support for URL-sharing

As in the previous version of \Blue, in the options page, we can add an option
"Share by URL" Yes/No
So that a paper can be edited with a URL only (no login required)

I started integrating it on my branch https://github.com/satabin/bluelatex/tree/feature/better-roles


Add additional monitor data / data-frames

Add addtional monitor data to the dl1 file format following the approach:

3 data frames, 1 for camera items, 1 for per TM items, 1 for per pix items
Add at least the following:
-- SB temps, currents, voltages, fan speeds (cam)
-- Chiller temps and status (cam)
-- DACQ temps (cam)
-- BP trigger rate (cam)
-- BP TM Voltages and Currents (tm)
-- TM temps (tm)
-- SiPM V and I (pix)

I did this didn't I? This can be closed now?

Functionality added by #48 and #51


Extension: Ask for parameter for profile

Description of the new feature/enhancement
I often have the need for multiple, but similar tabs. For example, an SSH terminal to various servers. Currently, afaik, I must create a new profile for each that specifies the specific server I want to connect to. This is not generally practical, as I have a large number of servers and may need to connect to any of them at any time. Currently I have to edit the profile entry in the config file with the new server name--thankfully that is read immediately so I can then use that profile, but this is still cumbersome.
Proposed technical implementation details (optional)
I would like to be able to specify a variable name in a profile that would request the value when I open that profile. For example, current a static entry for an ssh profile would be:
"commandline": "ssh user@servername"
It would be useful to be able to have a parameter so the value were requested from the user:
"commandline": "ssh user@%Server name%"
or multiple parameters:
"commandline": "ssh %user%@%Server name%"
When this profile is activated wt would ask the user for each parameter. This way I could have one profile that could handle whatever machine I want to connect to. Every time I open a new tab using this profile it would ask for the parameters to use in that tab. In my first example it would raise a dialog requesting Server name where I would enter the name of the server I want to connect to. In the second example it would also ask for the user. Of course this could be used for any purpose or other value.
I further suggest that if the same parameter name is used more than once it would only ask once, but use that for each reference. This would allow, for example, to use that parameter in the tab name:
"name": "SSS (%Server name%)",
"commandline": "ssh user@%Server name%"
In this example wt would ask for the value of "Server name" once, then use it in the tab title as well as the connection.

Hey, this is a cool idea! Thanks!
It's not something we're likely to do on our own, but I'm going to mark it up as a possible future extension. We're collecting these in #4000 to gauge what our plugin plan should encompass.

As an intermediary, you might have success with the commandline mode of the command palette. With that, you could type something like nt ssh user@serverName, and that'll open a new tab in the current window running ssh user@serverName.

Thanks, good idea! I thought of done something like that but hadn't looked into it enough. Good workaround for now.

I must be missing something...I don't see a way to start an arbitrary executable that way. If I don't specify a specific profile it just says "No matching commands."

Sorry, that's my bad. To get to commandline mode, you have to delete the leading > (on 1.5), or type a leading > (on 1.4). I know that's confusing, we just recently changed that to align with VsCode. See #7935

Got it, thanks, that was it! Keeps the current tab label, which is a little wierd. I know I can change that in the command.


mysql source operator with basic search ability

Besides the regular files that need to be changed when adding a new operator, this PR also introduces changes in

DateTimeField.java: introduced a new constructor that takes a DateTimeFormatter besides that value string, the string is formatted using the formatter provided. This is necessary because Java DateTime and mysql DateTime have different format.

AttributeType.java: introduced a new type BOOLEAN because mysql boolean type values are "1" and "0" and need to be converted to "true" and "false" at the creation of a StringField.

Should I create an issue for this BooleanField?


Dependency Versions

Hi,
We are trying to use TrustKit 1.1.3 and since this Open source and there 2 dependencies(fishhook and domain_registery).
Could I get the versions of the dependencies?(fishhook and domain_registery).
Thanks in advance

Hi,
Both dependencies don't seem to have version numbers:

Fishhook: https://github.com/facebook/fishhook
Domain registry provider: https://github.com/nabla-c0d3/domain-registry-provider

Also, for iOS 9 support, we will most likely start using RSSwizzle 0.1.0 as well (https://github.com/rabovik/RSSwizzle).


Test fixes

Fixes a couple of tests.
Only product impact is defaulting to PYTHONPATH when no variable name is set. This should only affect tests, as we already default to PYTHONPATH elsewhere in the actual product.

👍


Evaluation returns all zeros

All the evaluation results return all zeros. Evaluation logs show 'CHATGPT api is not working'

got the same problem

Same here, @kennymckormick could you please take a look? I checked the evaluation log, it said chatgpt api is not working which I assume is the problem here ?

Hey guys @simplelifetime @nicedoctor @nbasyl , this issue has been solved now. Now the platform can successfully complete the evaluation.

从除夕夜到目前为止，我一直试图提交测试，然而返回的结果都是“ChatGPT API is not working”，请问是出了什么问题吗 @kennymckormick

从除夕夜到目前为止，我一直试图提交测试，然而返回的结果都是“ChatGPT API is not working”，请问是出了什么问题吗 @kennymckormick

Hi, Tianwei,
Our API service is experiencing failure and we may not be able to fix it during the new year holiday. As a temporary solution, you can send your prediction results to<EMAIL_ADDRESS>and we will help you with the evaluation.

@kennymckormick I have sent my submissions to the email box and I sincerely request for your help. Thank you so so much!


Links: table refactor as class component

Reformat details links fetch
Add translations to javascript
closes: https://github.com/inveniosoftware/invenio-rdm-records/issues/1087

why was the old PR closed?

@Pineirin we should be careful when we close a PR as it is wiping out other people contributions! Make sure in this PR to have the proper co-authors! Out of curiosity, why was it needed to close this?

@Pineirin we should be careful when we close a PR as it is wiping out other people contributions! Make sure in this PR to set the proper author e.g git commit --author="John Doe<EMAIL_ADDRESS>and add yourself as co-author! Out of curiosity, why was it needed to close this?

I'm not sure if it was needed but I struggled a lot with the permissions for committing the changes so I thought that for simplicity it was best for me to create a clean PR, as I was going to squash the commits anyway.


Raspberry Pi 3B+ Mac Spoofing stops IPV4 lease from router

MAC spoofing is working properly on RPi 3B but the same process fails on RPi 3B+.
The device goes offline and isn't getting an IPV4 lease from the router any more.
The minimal nmcli command that demonstrates the different behavior on the 3B and 3B+ is:
export DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket

nmcli --nocheck con mod "Wired connection 1" 802-3-ethernet.cloned-mac-address "B8:27:EB:00:00:00"
nmcli --nocheck con up "Wired connection 1"
Supervisor: 9.0.1
Host OS: balenaOS 2.29.2+rev2
VM OS: Debian Stretch

Dockerfile:
FROM resin/%%RESIN_MACHINE_NAME%%-debian:latest

RUN apt-get update &&
apt-get install network-manager &&
systemctl mask NetworkManager

ENV INITSYSTEM on

 Front conversations

This will be fixed in balenaOS 2.29.2+rev8 or newer


On Date Of birth Text-box ,not able to open calendar once click on cancel button on Calendar

Describe the bug
On Date Of birth Text-box ,not able to open calendar once click on cancel button on Calendar
Component
reference app
To Reproduce
Steps to reproduce the behavior:

Go to 'Reference App'
Click on '+' icon
Tap On Date of birth
On calendar, click on Cancel button
Again Tap on Date Of Birth
Observe behavior

Expected behavior
User should be able to open and close calendar anytime
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. Lenovo Tab
Android version:10

Additional context
On click back button and again come on add patient, user is able to open calendar.

https://user-images.githubusercontent.com/64417713/142632731-eadd3961-f757-4e78-a024-b679f9940e22.mp4

Hii @anita-vadverao  can i work on this issue

@msubham193 please feel free to send a pr

i think we've seen similar issues before - the pop-up only gets opened when the text box gains focus, but if you cancel the pop-up the text box maintains in focus, therefore clicking it again doesn't open the popup.
so we need to maybe use a different listener.


add clone point, and turn off update after clone.

A proposal, to extend MercurialRepository/GitRepository to have clone point we clone at, and also disable default update to workingcopy after clone, i think it's waste of diskspace, and make the whole operation longer. I know that You can specify clone_point, and update option to mercurials api. Also i seen that clone_point is possible for git, and also --no-checkout  options is an equivalent of no update in mercurial.
One option is to make
{{{
#!python
def init(self, repo_path, create=False, baseui=None,   clone_url=None,
clone_point=None):
}}}
and another
{{{
#!python
def init(self, repo_path, create=False, baseui=None,
{'clone_url':None,'clone_point':None,'update':False}):
}}}
What do You think Lukasz ?

Reference: https://bitbucket.org/marcinkuzminski/vcs/issues/29/

@marcinkuzminski: I suppose we've already done that ;-) Please verify and close.
Also, just added bare repositories support for git during #94.

we made only update_after_clone, wich infact is a bad name, when now i think about it, it should be rather no_update,no_checkout to be more like command line option. But clone points are something not implemented i like it, and i think it's good value option. btw i'm more into keyworded arguments than dict


Fix ColorPicker's RAW mode colors and values

Fixes: https://github.com/godotengine/godot/issues/62894 Fixes: https://github.com/godotengine/godot/issues/88073
Changes:

Makes RAW sliders colored same as RGB mode.
Fix RAW mode maximum values, from 100 to 1.0.
Changes RAW step value to 1.0 / 255.0, to match the RGB mode values when changed.
Fix pressing the sample left side changes the color to black when old color is not displayed.
Remove an empty VBoxContainer called vbl.
Remove an extra VBoxContainer used as child of real_vbox, and adding it's children to the real_vbox directly.
Prevent OKHSL mode from changing the picker shape. The color mode is for sliders only, no need to override the shape.

Please add the bug label too, since it fixes three annoying issues.

Please open a bug report first :)

Remember you need to add "fixes" before each issue number

Thanks ^^

See also:

https://github.com/godotengine/godot/pull/62913

See also:

fix switching RAW mode to RGB mode issue #62913

We share the same fix
from float slider_max[4] = { 100, 100, 100, 1 }; to float slider_max[4] = { 1, 1, 1, 1 };

Being able to set values greater than 1.0 in raw mode is a feature, not a bug. #62894 is about not restoring the maximum value of the slider when going back to RGB mode, not changing the max value in raw mode.

Being able to set values greater than 1.0 in raw mode is a feature, not a bug. #62894 is about not restoring the maximum value of the slider when going back to RGB mode, not changing the max value in raw mode.

we can still allow this feature by making the spin box able to set values higher than 1.0 by enabling allow_greater, but I still don't understand the use of it, since they will not be visualized correctly, is it for glow/emission strength to make some colors more brighter that others? maybe because the glow the strength is a global variable for each environment.

Yes, it is for colors that are overbright in cases such as emissive colors with glow effects, or using modulate to brighten something.
I wouldn't suggest using allow_greater on the RAW mode sliders and limiting them to 1, because afaik the main reason raw mode is used at all is for overbright colors. RGB mode uses code specifically (see get_maximum_value) to set different slider max values in the case where you switched from raw and still want to edit the overbright color I guess but I'm not sure that that part is usefull, and you could just as easily switch to HSV instead (which would be more helpful to edit an overbright color) now that raw is a separate tab from RGB, but HSV does clamp the overbright color so that's pointless currently.
A proper way to deal with overbright colors on all color modes (probably a separate intensity slider) is the only elegant fix I think, but I think making RGB mode use allow_greater or just making it clamp is the way to go for this bug. HSV could use allow_greater theoretically, but I don't think the internal conversion supports that properly, okhsl will definitely not work with unclamped lightness so don't bother with that one.

ok, after allowing both RGB and RAW modes to have greater values, we are back again to this issue https://github.com/godotengine/godot/issues/62894, for some reason the slider maximum value changes after converting from RAW to RGB.
https://github.com/godotengine/godot/assets/53877170/17354eb9-b5f0-4355-a0fb-feb4b2cff1b7

Hi there, I was going to ask, while we're at it, is it difficult to make it possible to accept negative values as well? I know the most common use case is overbright colors, but negative colors are also used in many graphics tricks, and being able to export one would be great. The thing is that each component in Color can, in code, represent any float. But when exported in the inspector, the values are artificially being constrained by the UX of the ColorPicker. I think that's quite a shame, and it would be great if we could get over that hurdle with this PR. But if it's too difficult, I think getting over the limit of 100 is already a pretty big win.

Hi there, I was going to ask, while we're at it, is it difficult to make it possible to accept negative values as well? I know the most common use case is overbright colors, but negative colors are also used in many graphics tricks, and being able to export one would be great. The thing is that each component in Color can, in code, represent any float. But when exported in the inspector, the values are artificially being constrained by the UX of the ColorPicker. I think that's quite a shame, and it would be great if we could get over that hurdle with this PR. But if it's too difficult, I think getting over the limit of 100 is already a pretty big win.

The issue is that many properties can't handle negative colors by design (or it'll result in unintended effects). We'd need additional property hints to denote that specific properties can't use negative colors, similar to the existing PROPERTY_HINT_COLOR_NO_ALPHA.


Modify the param “format” of the function "setupSender"  to "DXGI_FORMAT_B8G8R8A8_UNORM",cann't receive the i

Modify code:
//const auto format = DXGI_FORMAT_R8G8B8A8_UNORM;
const auto format = DXGI_FORMAT_B8G8R8A8_UNORM;
result:
cann't receive Image.

I think you also have to modify C# code.

I'm closing this issue now. Please feel free to reopen it for further issues.


Create development branch

Not sure how you work with git but it would be nice to have a development branch and lock the master. What do you think?

Can you set this up? Would like to setup the travis jobs

Done


"% of people who used editor X" would be interesting not only for StreetComplete

for StreetComplete there is the first graph on https://piebro.github.io/openstreetmap-statistics/#465b (BTW, is it feasible to have some human readable links? not this random anchors?)

I thought about it too and wanted it to look like this https://piebro.github.io/openstreetmap-statistics/#a008 , but I wasn't sure how to implement it, because adding up all percentages is more then 100% (people use more then one editing software) and I wasn't sure how to phrase it's not misleading. Maybe this can be a normal multi line plot.
It was like this before and I changed it to these random 4 digit hex numbers. The advantage is: smaller links, disadvantage: not human readable. Before it was #general__how_man_people_are_contributing_each_month (automatically generated from the topic and question). In the end I decided for the smaller links as a more elegant solution. It's pretty easy to change. Maybe something human generate tag that summarizes the data  is best of both worlds like #general_contributors_per_month for https://piebro.github.io/openstreetmap-statistics/#63f6

I thought about it too and wanted it to look like this https://piebro.github.io/openstreetmap-statistics/#a008 , but I wasn't sure how to implement it, because adding up all percentages is more then 100% (people use more then one editing software)

Like on https://piebro.github.io/openstreetmap-statistics/#c229 ? With Y scale in %?
It would not sum to 100% obviously (in extreme theory all users could use all editors every single month) but that is not a problem.


[pivot table] Totals for pivot table not correct, not showing the sum of the rows/columns

Totals for pivot table not correct, not showing the sum of the rows/columns

Expected results
Totals will show sum of all columns and sum of all rows
Actual results
Totals show sum of one columns and sum of one rows
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug

Create a pivot table
Select 'Totals'
See error

Environment
(please complete the following information):

superset version: master
python version: python --version
node.js version: node -v

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Thanks for filing! We will NOT fix this issue but to accelerate the process of migrating Pivot table to Pivot table v2.
assigning to @zhaoyongjie
Task: Write a migration script and make sure the existing pivot table is showing properly in the v2. no need to address this pivot table issue specifically. 🙏


merge from template-sync/template-arlac77-github

package.json

chore(scripts): add documentation readme --section=API ./src//*.mjs && documentation readme --section=API ./src/.mjs (scripts.docs)
chore(scripts): add documentation lint ./src**/.mjs (scripts.lint:docs)

LICENSE

chore(license): update from template

README.md

docs(README): update from template

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.185%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
298

Relevant Lines:
348

💛  - Coveralls