Update palm detection model from MediaPipe (2023feb)

This PR aims to change the palm detection model from tjfs model to mediapipe model. Model downloaded from https://google.github.io/mediapipe/solutions/models.html#hands

The accuracy of the int8 quantization model decreases more, but the speed improves a lot. The following video is a demo of the int8 model.
https://user-images.githubusercontent.com/49567307/217290047-56550fc3-51c6-4294-80c9-ecd0dc1ecc2f.mp4

What's the main difference between this one and the previous one?

What's the main difference between this one and the previous one?

Thanks for reminding! I've updated the description of this PR.

I tested the hand pose demo on Khadas VIM3. The FPS is the almost the same whatever I choose the TIMVX+NPU or Default+CPU. Could you check if everything is right?

The accuracy of the INT8 palm detector is obviously lower than that of the float model. Should we release the int8 model?

HandPose model still need to be updated after this PR.
New palm detection model on Vim3 do have the same spped no matter if we use npu. I'm not sure why this happen.
I think we can add more images to quantized this model so that the accuracy may be higher.
I will try to improve this model.

I think we can include @zihaomu for discussion on the speed.

New palm detection model on Vim3 do have the same spped no matter if we use npu. I'm not sure why this happen.

I have compared the new and old model. And the new model has lot of PRelu layer. Because PeRelu is float32, it will cause the model to be cut into many small graph when NPU is executed. Every switch from float to int8 will be very time consuming, that's why you won't get NPU acceleration.

I re-quantified the model with 3900+ images and got a better model. The accuracy is obviously better, but the inference time is longer on CPU.


Loblloly's Studio

When I talk to Loblloly in Nacrene City after Game Syncing, she doesn't give you the options to switch the furnitures. I've tested this on entralinked 1.0.0 and 1.1.0.

Did a bit of research, I assume this is what you mean?
As far as I know these only had a use in the Dream World, but it might be interesting to look into it anyway for the sake of completeness.

Feature has been implemented as of v1.2.0.
I say "implemented", but you can't really do anything with it. Still, it's pretty neat I'd say.

I just wanted to add that the decor options change every day/every time you do a game sync so could you change it so that the dummy decors do rotations or something?

It’s possible, I’m just not sure what the point would be.


[rbac]: skip create and edit roles e2e tests

Part of https://github.com/janus-idp/backstage-showcase/pull/1026
CI tests are failing

/hold

/hold
till the e2e tests pass

Feel free to remove the hold from this PR when the E2E test results pass

/hold


@With annotation not supported for Nullable fields or Optionals

Short description
I have recently upgraded my Lombok to version 1.18.10, in which the @Wither annotation is no longer experimental. So I changed all the uses of @Wither to @With, since this is the new name of this annotation.
Now the 'with' methods of Nullable fields and Optionals turn red, indicating that the method does not exist. The code however compiles and I am able to run my tests without errors.
Expected behavior
with-method is available for the nullable and optional fields as well.
Version information

IDEA Version: 2019.2.3
JDK Version: openjdk 11.0.2 2019-01-15
OS Type & Version: MacOS X 10.14.6 Mojave
Lombok Plugin Version: 0.26.2-2019.2
Lombok Dependency Version: 1.18.10

Steps to reproduce
Apply @With annotation to a Nullable field or an Optional

Duplicate of #673. New plugin version will be probably released this week.


Add Kraken Exchange to the indicator

Please add Kraken Exchange and their BTC/USD/EUR/ETH options.
Thanks and excellent work!

Hey,
Sure :) I've no internet at home currently but will add it soon!
Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: Miguel Morales<EMAIL_ADDRESS>Date: 09/07/2016 09:07 (GMT+00:00)
To: sdrelton/cryptocoin-indicator<EMAIL_ADDRESS>Subject: [sdrelton/cryptocoin-indicator] Add Kraken Exchange to the indicator (#3)
Please add Kraken Exchange and their BTC/USD/EUR/ETH options.
Thanks and excellent work!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/sdrelton/cryptocoin-indicator/issues/3, or mute the threadhttps://github.com/notifications/unsubscribe/AGGqhd6r41BdMArl8CbebWUixO1Hy1TXks5qT1atgaJpZM4JIkkz.


drivers: uart_ns16550: Remove CMake-based templating

With some additional macro-magic we can remove the CMake-based header file template feature, and instead take advantage of the usual DT_INST_FOREACH_STATUS_OKAY() macro.
This is the same kind of update that was recently done to the i2c_dw driver as part of #34437 . It's not quite as simple however, due to the ns16550 DTS binding having many optional properties which are reflected as build-time conditional members of the various configuration structs.

@evgeniy-paltsev it would be good if you could test this for any regressions on your ARC-based platforms, thanks. I build-tested it on some x86, arm and arc platforms, but only did runtime tests on an x86 platform.


Connect draft WildlifeHomes site to staging Open Humans

Then share some test accounts with Holly, Beau, Jason, and myself.

Successfully connects, detects deleted connection, and patches to the Open Humans 'data' field a dict containing data file links to S3. Next step is grabbing data via data processing.


dart2js: constant names not stable for type parameters, large strings

Both of these constants in dart:html are mapped to the same name, C.EventStreamProvider_load:
  static const EventStreamProvider<Event> loadEvent = const EventStreamProvider<Event>('load');
  static const EventStreamProvider<ProgressEvent> loadEvent = const EventStreamProvider<ProgressEvent>('load');

This leads to minified names
C.a0=new W.M("load")
C.a1=new W.M("load")

in one compilation and
C.a1=new W.M("load")
C.a0=new W.M("load")

in another. (From sdk/bin/dart2js samples-dev/swarm/swarm.dart --minify --out=m2.js)
The names a0 and a1 have been assigned in a way that seems to be stable (the references are unchanged). This means that the constants are emitted in a different order.
Since the constants are sorted by the (unminified) name C.EventStreamProvider_load, the order is not deterministic.
Repeated compiles flip the order of the constants, leading to differences in the output of compiling the same program twice with no changes.
There is no type parameter attached to the runtime constant object because it is unused, but the runtime type parameters could be included in the name.
Large strings have a different problem. We use a hash function to reduce the large string to an identifier. This can have collisions. There is a collision on JS_CONST constants containing strings in the js_runtime!
We can't embed the whole constant in the name. I think we need to develop a compareTo function for constants that always distinguishes non-identical constants. This can be used in place of the pretty-name / hash-name scheme, or as a fall-back for when the current scheme produces identical names.
(sorting by the hash-name first helps gzip.)
The above is one cause of https://github.com/dart-lang/sdk/issues/24721

CL investigating the compareTo approach: https://codereview.chromium.org/1491413008/ .

@rakudrama tagged this as "closed-obsolete", and I think the issue has been fixed, as we have deterministic builds internally.


cargo component add not producing runnable/usable binaries

Currently, cargo component add produces binaries using the unlocked-dep import syntax, which is not supported yet. Not runnable or parsable in today's tools. There are a number of things to figure out to get that feature supported, which I'd also like to move forward with.
I'm considering revising cargo component add behavior to produce binaries that can be used today.
Say you have a component package (an implementation not a pure wit package) that you'd like to use as a library in your component. cargo component add example:library would set you up with the bindings to use it. Then when you, cargo component build, the outputted binary includes the composed dependency and would be usable in current released tooling.

@macovedj Let's remove or comment out cargo component add until it is in a workable state.


Fix auto-dark mode

After the last update, Chrome on Mac converts all the websites into the dark mode automatically. It works fine for dvc.org/cml.dev, but with some small bugs:

(white areas that it was not able to convert, and some glitches with icons)
Also, on the landing page we need to review the main image.

I think that it got enabled with chrome://flags/ - enable dark mode somehow (I didn't do it manually)

Blog/Feed/Item components also have white area on overflow:

:dark_sunglasses: I didn't know the engine had a dark mode. Can we add a toggle button?

Can we add a toggle button?

I don't think so, since Google Chrome's dark mode can only be enabled in a user's browser settings.

I mean a cross-browser toggle button (perhaps for separate issue).

I mean a cross-browser toggle button (perhaps for separate issue) akin to https://squidfunk.github.io/mkdocs-material/ (next to search bar)

As far as I know, it's possible but I'm not sure how hard it would be to implement. We'd need to decide on a color scheme and update our site's styles accordingly.

Main image should be back to normal for iterative.ai and blog gradients are fixed as well!


[T5A3][W09-A1] Teo Tian Song

Reviewed in tutorial

Good job for doing all activities..
Accepting this PR without a review because, either

we already review this PR during tutorial.
another of your PRs for this tutorial was reviewed in detail.
minimally reviewed and found no important issue.


perf(resourcehandler): collect k8s resources in parallel

refactored and parallelized host sensor
Signed-off-by: Frédéric BIDON<EMAIL_ADDRESS>Overview

@matthyx I had closed this one since we agreed that taming the memory pressure was more important.
I believe that we had gone quite a long way on that path, hence I am reviving this one again.
I provide here a recap of the various performance drags on scans that we have discussed:

Memory pressure by "update results". I believe this should be much better now with #1054
Long-running OPA rule Compile. I don't have a smart solution for that time (yet...). Brute force is there: #1064
Report building (unique/trim stuff): you have worked on a solution (https://github.com/kubescape/opa-utils/pull/84) and so did I (https://github.com/kubescape/opa-utils/pull/81). Your approach really improves the code for the longer term, whereas I did focus on short-term pain relief. Maybe a side-by-side comparison would help decide what we do?
Eventually, this PR (#1066), with a focus on network API calls
We have also discussed the git history stuff, which eventually boiled down to a performance issue and causes us other (install & integration) impediments. I've investigated a bit, taking inspiration from your WIP branch, and comparing the different approaches taken by go-git and libgit2. Will keep you posted.

cc: @dwertent

@dwertent @matthyx
I don't think that the proposed parallelization endangers our objective of remaining low on resource usage.
You might opt for picking the refactoring and not the parallel execution part. Please let me know so I may split the changes in separate PRs.

@fredbi I get a panic:
matthiasbertschy@penguin:~/github.com/matthyx/kubescape$ go run . scan --enable-host-scan
[info] Kubescape scanner starting
[warning] unknown build number, this might affect your scan results. Please make sure you are updated to latest version
[info] Installing host scanner
[info] Downloading/Loading policy definitions
[success] Downloaded/Loaded policy
[info] Accessing Kubernetes objects
[success] Accessed to Kubernetes objects
[info] Requesting images vulnerabilities results
[success] Requested images vulnerabilities results
[info] Requesting Host scanner data
panic: send on closed channel

goroutine 310 [running]:
github.com/kubescape/kubescape/v2/core/pkg/hostsensorutils.(*workerPool).hostSensorApplyJobs.func1()
        /home/matthiasbertschy/github.com/matthyx/kubescape/core/pkg/hostsensorutils/hostsensorworkerpool.go:92 +0x145
created by github.com/kubescape/kubescape/v2/core/pkg/hostsensorutils.(*workerPool).hostSensorApplyJobs
        /home/matthiasbertschy/github.com/matthyx/kubescape/core/pkg/hostsensorutils/hostsensorworkerpool.go:84 +0xe5
exit status 2

@matthyx ok something has probably be regressing with the many merges this PR has been subject to. I am addressing the issue. Thanks for letting me know.

@matthyx  I realize there are absolutely no tests in this package. I am going to address that part first. We'll see how to refactor/improve only after I've raised the level of confidence in changes we put there.

@matthyx putting back this one in draft status. The newly added unit tests exhibit the panic. That's because the workerPool cannot be shared by several concurrent routine calling CollectResource.
I need to proceed with a deeper rework of this.
Anyhow, the current hostsenser exhibits some race conditions that need to be fixed.

This PR is scaffolded on top of   #1141 and #1154, to reduce the number of changes per PR.
As such, it remains in "draft" status until the fate of these PRs is determined.

copy that :)
I'll come back to your PRs as soon as we've finished outstanding tasks for the quarter, thanks for your patience.

The initial scope of this PR has been narrowed down to the host-sensor only.
The host-sensor client is now free from race conditions and fully asynchronous.
I hope this work improves the readability of the host-sensor logic.
I've noticed a strong sensitivity to the version of the host-scanner repository (paths, returned types). I'll possibly push later some improvements there (paths as enum, mock API...).
I've removed previous similar work on the more general k8s resources collection and deferred that piece to a forthcoming PR.

cc: @dwertent @matthyx  I believe this one is now ready to be subject to some integration tests.

@alegrey91 I would like to confirm/increase integration test coverage of this feature before we merge this one, this is a key feature of our commercial offering and I don't want to mess up.

@alegrey91 I would like to confirm/increase integration test coverage of this feature before we merge this one, this is a key feature of our commercial offering and I don't want to mess up.

Yes, agree

@alegrey91 Any update here?

This won't be merged for the following reasons:

The host-scanner is not longer supported from the CLI
We will change the way Kubescape collects the host scanner data, it will no longer request it directly from the running host-scanner microservice


Added the possibility to pass a custom each_serializer, page and limit

Summary
Added a way to pass custom serializers, page and limit to the render_paginate method

@icoluccio Can you rebase on development?


Changes to derived entity property values are not updating, only parent properties.

Hi,
We're experiencing an issue when trying to update a derived entity. Taking a look at the entity in the change tracker we can see the values we're expecting to see, but when SaveChanges is called, only the parent entity properties are in the generated update statement.
Our setup is;

Register EFDbContext in Startup
EFDbContext inherits IdentityDbContext
Consume it from a controller action
Try to update a derived entity

E.g. we have a parent class CustomPageContent:
public class CustomPageContent
{
        public int Id { get; set;}
        public int DisplayOrder { get; set; }
        public int Type { get; set; }
}

and a child class CustomPageContentText:
public class CustomPageContentText : CustomPageContent
{
        public string Content { get; set; }
}

Our code looks like (we do have a wrapper around EFDbContext, we're just using the raw context whilst we've been looking into this issue):
var textContent = _context.CustomPageContentTexts.FirstOrDefault(o => o.Id == 1);

textContent.DisplayOrder = 1;
textContent.Content = 'updated content';

_context.Update<CustomPageContentText>(textContent);
_context.SaveChanges();

When we call the update, we can see the following statement generated:
exec sp_executesql N'SET NOCOUNT OFF;
UPDATE [CustomPageContent] SET [DisplayOrder] = @p1, [Type] = @p2
WHERE [Id] = @p0;
SELECT @@ROWCOUNT;
',N'@p0 int,@p1 int,@p2 int',@p0=1,@p1=1,@p2=1

Adding a derived entitiy seems to work fine, however.

dupe of #4817 ?

Agreed that this is most likely a dupe of #4817 which was fixed yesterday.

Apologies fellas, seems I didn't look hard enough through the exisitng issues.


Not able to convert csv to xpt

Study Statistical Analysis (1).xlsx

That looks like XLSX, not CSV.


proposal: errors: Has function

Proposal
Add a tiny errors.Has function to make the errors.As mechanism ergonomically available in if statements.
errors.As is an essential function in the error-wrapping world we live in. But sometimes the caller is only interested in the type of the target, not its value. In that situation, errors.As is awkward to use in conditionals.
Implementation
Add a function errors.Has:
// Has returns true if err, or an error in its error tree, matches error type E.
// An error is considered a match by the rules of [errors.As].
func Has[E error](err error) bool {
  return errors.As(err, new(E))
}

A quick GH search  reveals many candidate usages. Here's one example:
  err = container.RunExec(ctx, s.dockerCli, target.ID, exec)
  var sterr cli.StatusError
  if errors.As(err, &sterr) {
    return sterr.StatusCode, nil
  }
  return 0, err

This could be rewritten to:
  err = container.RunExec(ctx, s.dockerCli, target.ID, exec)
  if errors.Has[*cli.StatusError](err) {
    return sterr.StatusCode, nil
  }
  return 0, err

For

It's a trivial addition, and makes it explicit that you're only interested in the type, not the value, so it adds to the clarity of the code.
The errors.As(err, new(E)) construct obviously isn't widely known; errors.Has is discoverable.

Against

We could instead just document the errors.As(err, new(E)) construct in the errors.As documentation.

Naming
Obviously errors.Has is similar to errors.As. Maybe that'll cause confusion? Although, it didn't stop errors.As and errors.Is.
That said, a name like errors.HasType is more explicit. But I absolutely hate it in comparison to errors.Has. I think the "typey" intent of the function is already made obvious by the type parameter. And when I see As, Is and Has together, is it not the missing triplet separated at birth?

see also #51945

your search only shows usages of errors.As, not specifically that the value of the error wasn't used
most seem to use !errors.As to early return from when they can't provide more detail.

@seankhliao: Ah, somehow I missed #51945. Obvious duplicate. Closing.

FWIW, I've just released jub0bs/errutil, a small utility package that exports the following function:
func Find[T error](err error) (T, bool)

It subsumes your Has function:
func Has[E error](err error) bool {
  _, ok := errutil.Find[E](err)
  return ok
}


add empty string test case in TestSwapCase in backend/commands/case_test...

Brings test coverage to 100% in case.go.
If not merged, please provide feedback.

Coverage remained the same at 62.56% when pulling 867c54777162855a863af689bbd71e3dfb996cbe on collinglass:case into ea73650cb8389a6964503619e35f802360f4c115 on limetext:master.

LGTM, thanks.


API Configuration

How did you obtain an API token and what is the API you are using? I can't seem to find any public API outside of the invite system. Have you reverse engineered an undocumented RESTful API or are you using something else altogether?

This isn't the HeckGuide source code.
To reverse the API you will need to get the APK, de-compile it, find the il2cpp files, de-compile and reconstruct them, repair the class names, reverse the .so and you will find every API call in the game.


Add get_meta_or_default()

Closes https://github.com/godotengine/godot-proposals/issues/2383

I'd prefer to add an optional third argument to get_meta(), which would be more similar to Dictionary.get().

get_meta_or_null()

I don't think having such method makes sense. We have get_node_or_null() because you can literally only return either node or null. In case of Dictionary or meta, the default value can be any Variant. And returning null in case of missing value means that you have to add more code if you want a different default.

Having a separate method is warranted for having get_meta_or_null() in the future (once we make get_meta() return an error when the value doesn't exist and no default is specified).

This basically means that we'd add get_meta_or_null() just to have a version of get_meta() with null default value that doesn't throw error. Instead of having two methods with default for such a weird reason, it's better to have one.

As mentioned in the PR review, that doesn't cover the use case that get_meta_or_default(meta, null) would, but we thought that this specific use case doesn't necessarily need to be supported (and can be handled with has_meta).

Tbh I think the _or_default method is useful and covers a lot of cases. Searching for has_meta( in the code base returns a number of results where this new method could be used to simplify the code. I think adding a param to get_meta (as described in quoted text above) but not having it work (without error) 100% of the time is a bit of a half measure.

adding the default value to get_meta itself

Done.

Does this need a rebase after #59452 or is it fine as is?

Tested, still works.

Thanks!

Cherry-picked for 3.5.


Add tutorial notebook for TIKE

I figured I would open a PR here first to get comments, and then we can move/copy the notebook to wherever TIKE needs it for review.

moved to https://github.com/spacetelescope/tike_content/pull/46


MDA8 and regulatory metrics

We need to add the regulatory metrics including MDA8 into the MELODIES-MONET tool. We have a start for how to do this from Patrick's old scripts and MONET itself. If someone can help with this that would be great, but otherwise I may eventually get to it.

The regulatory options have been included with this pull request:
https://github.com/NOAA-CSL/MELODIES-MONET/pull/84
Next step is to update the ReadTheDocs for these updates. @rschwant will work on this with help from @jianheRCM

This is complete and in the develop branch with this pull request:
https://github.com/NOAA-CSL/MELODIES-MONET/pull/142
And also we fixed some formatting for these updates in this pull request to clean up the plotting routine:
https://github.com/NOAA-CSL/MELODIES-MONET/pull/145


How to do deterministic sampling?

Hi! Thanks for the great work!
Though I have a question about how to do deterministic sampling.
I find the inference results are not the same when running a code multiple times (like I masked one portion of residues and redesign them). Even after I choose the max probability each node while doing autoregressive sampling, the results are not the same. I found that permutations are done when preprocessing the chains, this might be the reason.
For potts sampling, the results also differs in different run times.
How can I do deterministic sampling, to choose the one with maximum probability (or to say the most possible chain that I want)?

There seem to be two separate tasks here, making sampling deterministic and choosing the maximum probability residue during sequence design.
For the first, we've found that PyTorch 2 has deterministic versions of all the GPU operations we use. So, if you're willing to upgrade, you could try a snippet like this.
import os
import torch
import warnings
torch.use_deterministic_algorithms(True, warn_only=True)
os.environ["CUBLAS_WORKSPACE_CONFIG"] = ":4096:8"
chroma = Chroma() # should go before the warning filter
warnings.filterwarnings(action='default', message=r".*deterministic.*")

# set seed
seed = 0
torch.manual_seed(seed)
# sample from Chroma here
...

Independent of this, if you want to choose the most likely residue regardless, you could try lowering the temperature of the sequence sampling process via the temperature_S argument of Chroma.sample. Hope this helps!

Thanks for the quick response!
I think my question might be the latter case, that I want to generate the most likely results among probabilistic generations.
Sorry for the misunderstanding about previous description, when I was describing the question, I might be affected by autoregressive methods, in which case you choose tokens with maximum probability, and gets the most-likely residue chain, in that way it is both deterministic and most-wanted. This ''deterministic'' is not usually affected by random seed, but by how you sample from every node's predicted distribution.
So the question might become, how to choose the token with maximum probability at each node, to make sure that the autoregressive/potts produce best-likely results? I revised the code here to choose max prob at each sample, but the results are still not the same in multiple runs.
https://github.com/generatebio/chroma/blob/929407c605013613941803c6113adefdccaad679/chroma/models/graph_design.py#L1978
Could it due to the randomness by permutation?
I also tried to lower temperature to 1e-6 and 1e-9, results in multiple runs still differ (while I assume that the best results should stay the same?)
Or could it be other ways to sample the best result?
Thanks!!

Yes, the permutation to perform the autoregressive sequence sampling is generated randomly. You can fix the random seed for this generation by setting chroma.design_network.traversal.deterministic = True, or alternatively by calling torch.manual_seed before generation. In the code above that uses the latter, everything ends up being deterministic, not just the sequence design.
Just to clarify, even when performing autoregressive sampling, Chroma lets you sample at arbitrary temperature, rather than choosing the most likely residue given those that are already selected. Choosing a low temperature_S, in combination with fixing the permutation, should give you a deterministic sampling of the best residues in a set order.

Thanks again for your response! I've tried recently and find it is the permutation who causes randomness.
I mainly changed code here to maintain the sequence order of masked residues to stay the same using prioritized mask (while in original settings they were permutated randomly and placed last to be generated).
https://github.com/generatebio/chroma/blob/929407c605013613941803c6113adefdccaad679/chroma/models/graph_design.py#L2271


Feature/micro 38 convert to monorepo

Restructure the serverless template to allow us to create applications that contain multiple services (monorepo). To do this we are using serverless compose plugin which handles the deploy order and dependencies.
This PR also includes various other changes to allow the testing of deploys and dependencies on other services.
The way I have set it up allows for us to also define common yaml data in a central location meaning that you can update all of the services with this data without having to change each of yamls per service. I also added in a common lib which will be populated going forward however at this stage I have just added in a few simple actions for the purpose of testing. The remainder of this will be done in future tickets as specified in each of the files.

@SamMenzel @jswift do we want this to be part of the public-facing template? I was thinking of it as an internal project which used the template to build individual services within the monorepo.

Closed this PR as monorepo development has continued elsewhere.


/parquet-and-dataset-info is processing datasets bigger than 5GB

e.g. right now it's processing https://huggingface.co/datasets/madrylab/imagenet-star/tree/main

Though I checked and PARQUET_AND_DATASET_INFO_MAX_DATASET_SIZE is defined by
parquetAndDatasetInfo:
  maxDatasetSize: "5_000_000_000"

Same behavior with https://huggingface.co/datasets/CYHSM/asp/tree/main dataset.

we have to look at it

to be done

We have false positives, but it's not a big issue, I think. See https://huggingface.co/datasets/Muennighoff/multi_eurlex for example.


CSP eval error

Hi all
On the site I work on, we use a Content-Security-Policy to, among other things, forbid the use of eval, as it is a security vulnerability.
The HelloSign-embedded package trips this Policy to obtain the global object using the new Function("return this")() trick. If that returns an error, as it does on my site, then the code tries to get the window object. While this works, it causes CSP violation reports.
Can this check be done the other way around? Try to get the window object, and if that fails then use new Function("return this")()?
Alternativly, you could check globalThis:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis

Hey @Sora2455, thanks for the note. Looks like the UMD wrapper is injecting this code into the dist files. I'll see if there is a way to configure this with Webpack!

@iangcarroll for visibility

Looks like this is actually coming from one of the core-js dependencies (symbol to be exact). Will have to take a deeper look as to how to resolve

@Sora2455 this looks like it's out of my control since it's coming from a third-party package which we rely on for polyfilling :\ I'd recommend opening up an issue on core-js
Here are some related issues: https://github.com/zloirock/core-js/issues/274, https://github.com/zloirock/core-js/issues/11
If you have any other ideas, please don't hesitate to suggest them!

It looks like core-js fixed their fetching of the global object in May last year: https://github.com/zloirock/core-js/commits/5a66505301b64d13f7bcf96b1e9ab55e4ff35fe6/packages/core-js/internals/global.js.
Would it be possible to upgrade the core-js version?

Hmm, I upgraded to core-js@latest, and I'm still seeing new Function("return this")() in the built file, this time only inside web.dom-collections.iterator.js.

That's not web.dom-collections.iterator.js - that's a file that requires web.dom-collections.iterator.js, and searching for a file that does that in core-js turned up nothing.
I'll have a look through your other dependencies later today to see if I can find the offending file.

Okay, looks like this is a Webpack file (\node_modules\webpack\buildin\global.js), not a core-js one... I'll see if updating webpack removes it.

Bother. Webpack has fixed this problem, but for their 5.0.0 release (which is currently in beta).

Sorry! I'd love to resolve it as soon as it becomes possible on my end.


Timezone incorrect in boot2docker VM

By default, the VM is configured to sychronize time to the host, however the timezones are mismatched. The VM is set for UTC, while the host OS X is set for a local timezone (MDT here). As a result, when the VM is first started it sets both clocks to the same wall number (12:30pm MDT and 12:30pm UTC) which causes a mismatch.
The first indication of this failure is that the TLS certificate created by docker-machine for access to the Docker daemon will fail. Opening the certificate file with openssl shows the "not-valid before" time in UTC, and with the host on a different timezone, certificate checking fails until the VM time is corrected.

Yes, seems like we have a bug in "Time Sync" feature.
I'll temporary disable it by default, but it means that we have to release a new custom binary of docker-machine. I will do it in 1-2 days.
You can fix it manually for your VM in the moment:
docker-machine stop <vm_name>
prlctl set prl-test --time-sync off
docker-machine start <vm_name>

P.s. Boot2Docker guest OS has an internal way to sync the time (it runs ntp by cron job). So its time will be always correct even if "Time Sync" feature of Parallels Desktop will be disable.

Great, at least this workaround will allow me to run Make on my projects again (make does not like clock problems...)

Actually, not good. The internal NTD process is also fracked:
The following commands were run within the VM about every 8 seconds.

Fri Aug 21 23:32:47 UTC 2015
minion@0a87fa556f55:/build$ date
Fri Aug 21 23:32:54 UTC 2015
minion@0a87fa556f55:/build$ date
Sat Aug 22 00:34:11 UTC 2015

It seems that whenever the NTP cron is run, the time is advanced by 1 hour... at least it is not going backwards which is what happens if you try to manually correct the time by running ntpclient.

Fixed with ad586e86 and released as 0.4.0-1
$ curl -L https://github.com/Parallels/docker-machine/releases/download/parallels%2F0.4.0-1/docker-machine_darwin-amd64 > /usr/local/bin/docker-machine
$ chmod +x /usr/local/bin/docker-machine

@y3ddet Please, check that it works for you (you will need to re-create the machine from the scratch)

@legal90 Confirmed! Clock is now correctly showing actual UTC in the container, and the clock is stable over the last 4 hours.
The older container with the bug kept spinning forward, gaining about 48-hours for every real 24-hours, resulting in a clock that was more than 7+ days faster than wall clock after the weekend!


Check for command topics when determining the capabilities of an MQTT light.

Previous code used the state topic which is obviously wrong:

The state topic is already used to select optimistic mode.
A light with only the state topic but no command topic would still announce the capability.

Hi @herm,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Whoops, my bad :)
LGTM


linux or windows ?

can we run the train script on windows ?

The train script works on both Linux and Windows. If you are struggling, please describe it in the issue.

All good I think, I was trying to make it work on windows, but I didn't see that by default it was used in multiGPU
I changed parameters and it worked just fine.
thank you

All good I think, I was trying to make it work on windows, but I didn't see that by default it was used in multiGPU I changed parameters and it worked just fine. thank you

@trikiamine23 , can you please explain me what parameters did you change and how did you handle ""RuntimeError: Distributed package doesn't have NCCL built in" on Windows?

@cavidhabibov , you just need to comment out one line in train.py:
strategy="ddp",
ddp stands for "distributed data parallel" which depends on Nvidia NCCL.


Set up the link between EvoSuite and the plugin

Description
Create basic integration between EvoSuite and the plugin
Definition of Done

[ ]  Make it possible to generate tests for a (hardcoded) class from the plugin (i.e. execute the same functionality that a command such as java -jar evosuite-1.2.0.jar -projectCP target/classes/ -class delft.ArrayUtils would have)
[ ] Resolve any issues such as Java version or dependency incompatibilities that would prevent this integration from working

Moving this issue from Sprint 0 to Sprint 1 due to the issues that occurred while working on it.

Tracked in #18


Update messaging quickstart

This pull request solves the reported issues. The application is now working, and the tests are passing on CI.
Screenshoots

Changes Unknown when pulling 31d2e6ae6ab09d353b0ba3dfc90f5016fb0103b9 on update-messaging-quickstart into ** on master**.

Changes Unknown when pulling 31d2e6ae6ab09d353b0ba3dfc90f5016fb0103b9 on update-messaging-quickstart into ** on master**.


[FEA] Save data to databases

Right now Bumblebee can save data to files, It will be useful if the user can save data to databases. Optimus already have these features so we can implement them easily.

Implemented a few months ago


user_circles: Replace CSS-drawn circles with icons.

This PR replaces the former CSS-drawn user presence circles with new hand-drawn icons to match the former look almost exactly. (Eagle-eyed reviewers may note certain places, such as the typeaheads, where the CSS-drawn circles were sometimes egg shaped--even adjacent more perfectly circular counterparts; note that that effect also affects idle circles, whose egg-shaped before status may make it appear that the new icon has a different amount of filled space at bottom.)
CZO discussion
Along with the swapped icons, there are a few improvements to the existing design presented here:

Presence circles in the inbox view are now somewhat larger than previously, in response to feedback from @alya about circle-sizing generally.
The appearance of circles over top of avatars is greatly improved. First, as a matter of course, this PR corrects a regression in main where only the bottom half-moon portion of the idle circle appears as orange on user cards. Second, because the border property is no longer used to draw circles themselves, circles over avatars can be presented much more uniformly (and without a hacky outline-based hover effect). That includes better positioning the circles relative to the avatar images, especially in the right sidebar when showing avatars.
Offline circles on user cards are now presented more uniformly as other circles, giving them the same "bullseye" appearance.

There are a few quick but impactful follow-ups upon the successful merging of this PR:

[ ] Consolidate the user_profile_presence class, probably popover_user_presence too
[ ] Consolidate the user-circle and status-circle classes? The latter gets used as a class in popovers/Tippy (I think just on the navbar_personal_menu_popover.hbs template), but also as part of the --length-user-status-circle and --length-user-status-circle-recent-conversations variables, which presumably go away once the icons are introduced
[ ] Grid rewrite on Inbox lines so that “ghost” user circles aren’t holding the layout open on topic rows (a necessity owing to the current flexbox-based layout in the area)

Screenshots and screen captures:

Before
After

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Does this empty circle look a touch lower than the green one? Maybe it's not a big deal, but it felt a bit too low to me.

@alya those both look to be the product of subpixel shifts. I've yet to find a reliable way to control those. And they happen a lot more than we notice, even on the same screen across browsers. Here, for example, is the right sidebar in dev, Firefox vs. Chrome (Firefox has the heading text that appears slightly lower from the top than it does in Chrome):

Even in that little sample, the irritating thing is that the shifts aren't even uniform, line to line. Desdemona's name relative to the offline icon, for example, has a much more dramatic shift than does King Hamlet on the line below.

The left sidebar one seems potentially concerning. I can test-deploy, but holding off on merging to main for now.

Merged via force-push (we'd accidentally merged #32306 instead).


fix(time_offset): Row Limit

SUMMARY
When applying a time_offset in Advanced Analytics, if the row_limit is too small, data will not be present when the join occurs, so this PR prevent such behavior by not using limit nor offset in the inner query (the shifted one).
For example this query shown in the following video has all the records for a period of 10+ years:
https://github.com/apache/superset/assets/38889534/8dca8b16-5c05-4b2d-8fd6-67387c8708e7
We can see that the result of shifted queries not always include the same periods than the original query, so when the join gets applied, it won't match some records, thus giving you incorrect output.
Original query with limit and sorting:

1 year ago query with limit and sorting:

2 years ago query with limit and sorting:

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Error:
In the following image some datapoints are missing in the shifted columns because they are not part of the result dataframe after sorting and limiting it like the original query.

Fix:
Now we can see that the query is able to find the records that belong to those offsets regardless, because it's joining using the complete data.

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

/testenv up

@Antonio-RiveroMartnez are there any open issues we can link to this? I'm somewhat surprised that no one has reported an issue with this in the past.

Hey @john-bodley I just linked it in the PR description, thanks.


Putting unnecessary texts in the answer

Hello, the reply that comes from chat gpt contains unnecessary texts.
For example, when I want to write a test for the following method:
public static string FixLengthNumeric(string fieldName, dynamic lenghtNumber) => string.Format(Validations.FixLengthNumeric, fieldName, lenghtNumber.ToString());
He writes as follows:
```csharp
using Xunit;

public class ValidationTests
{
    [Fact]
    public void FixLengthNumeric_WithFieldNameAndLengthNumber_ShouldReturnFormattedString()
    {
        // Arrange
        string fieldName = "Field1";
        dynamic lengthNumber = 10;

        // Act
        string result = YourClassName.FixLengthNumeric(fieldName, lengthNumber);

        // Assert
        Assert.Equal("ExpectedFormattedString", result); // Update ExpectedFormattedString with the expected result
    }
}
 ` ``` `
In the test method `FixLengthNumeric_WithFieldNameAndLengthNumber_ShouldReturnFormattedString`, you can replace `YourClassName` with the actual class name where the `FixLengthNumeric` method is located. Update the `Assert.Equal` statement with the expected formatted string that should be returned by the `FixLengthNumeric` method.

The beginning of the return code is ```csharp and the end is ``` . and description text without // characters This is true for the rest of the commands as well.

Hi @Arman-Espiar,
about csharp and , I will implement a way to remove this from the OpenAI response.
But comments that don't start with comment characters are a bit tricky to do because it's difficult to identify what is code and what isn't. But I'll see what I can do.
I'll post the status of my progress here.

Hi @Arman-Espiar ,
I published a new version with the fix 🙂


[Bug]: No namespaces are detected in new version

Version
v2.1.0
What happened?
In UI no namespaces are detected:

Configured variables:
        env:
        - name: "KUBE_NS_SUSPENDER_UI_EMBEDDED"
          value: "true"
        - name: "KUBE_NS_SUSPENDER_CONTROLLER_NAME"
          value: "kube-ns-suspender"

❯ kubectl get ns --show-labels

NAME                STATUS   AGE     LABELS

kube-system         Active   77m     kubernetes.io/metadata.name=kube-system

default             Active   77m     kubernetes.io/metadata.name=default

kube-public         Active   77m     kubernetes.io/metadata.name=kube-public

kube-node-lease     Active   77m     kubernetes.io/metadata.name=kube-node-lease

kube-ns-suspender   Active   74m     kube-ns-suspender/controllerName=kube-ns-suspender,kubernetes.io/metadata.name=kube-ns-suspender

test                Active   5m42s   kube-ns-suspender/controllerName=kube-ns-suspender,kubernetes.io/metadata.name=test

Relevant log output
{"level":"info","time":"2022-06-14T11:54:55+02:00","message":"engine successfully created in 8.479µs"}
{"level":"info","time":"2022-06-14T11:54:55+02:00","message":"kube-ns-suspender version 'ghcr.io/govirtuo/kube-ns-suspender:v2.1.0' (built 2022-06-13_12:28:13TUTC)"}
{"level":"info","time":"2022-06-14T11:54:55+02:00","message":"web UI successfully created"}
{"level":"debug","time":"2022-06-14T11:54:55+02:00","message":"timezone: Europe/Paris"}
{"level":"debug","time":"2022-06-14T11:54:55+02:00","message":"watcher idle: 15s"}
{"level":"debug","time":"2022-06-14T11:54:55+02:00","message":"running duration: 4h0m0s"}
{"level":"debug","time":"2022-06-14T11:54:55+02:00","message":"log level: debug"}
{"level":"debug","time":"2022-06-14T11:54:55+02:00","message":"json logging: true"}
{"level":"debug","time":"2022-06-14T11:54:55+02:00","message":"controller name: kube-ns-suspender"}
{"level":"debug","time":"2022-06-14T11:54:55+02:00","message":"annotations prefix: kube-ns-suspender/"}
{"level":"info","time":"2022-06-14T11:54:55+02:00","message":"metrics server successfully created in 74.014µs"}
{"level":"info","time":"2022-06-14T11:54:55+02:00","message":"in-cluster configuration successfully created in 113.159µs"}
{"level":"info","time":"2022-06-14T11:54:55+02:00","message":"clientset successfully created in 1.209969ms"}
{"level":"info","time":"2022-06-14T11:54:55+02:00","message":"starting 'Watcher' and 'Suspender' routines"}
{"level":"info","routine":"suspender","time":"2022-06-14T11:54:55+02:00","message":"suspender started"}
{"level":"info","routine":"watcher","time":"2022-06-14T11:54:55+02:00","message":"watcher started"}
{"level":"debug","routine":"watcher","inventory_id":0,"time":"2022-06-14T11:54:55+02:00","message":"starting new namespaces inventory"}
{"level":"debug","routine":"watcher","inventory_id":0,"time":"2022-06-14T11:54:55+02:00","message":"parsing namespaces list"}
{"level":"debug","routine":"watcher","inventory_id":0,"time":"2022-06-14T11:54:55+02:00","message":"Metric - channel length: 0"}
{"level":"debug","routine":"watcher","inventory_id":0,"time":"2022-06-14T11:54:55+02:00","message":"Metric - running namespaces: 0"}
{"level":"debug","routine":"watcher","inventory_id":0,"time":"2022-06-14T11:54:55+02:00","message":"Metric - suspended namespaces: 0"}
{"level":"debug","routine":"watcher","inventory_id":0,"time":"2022-06-14T11:54:55+02:00","message":"Metric - unknown namespaces: 0"}
{"level":"debug","routine":"watcher","inventory_id":0,"time":"2022-06-14T11:54:55+02:00","message":"namespaces inventory ended"}

### Anything else?

_No response_

hi @krzwiatrzyk,
can you please share your namespaces annotations?

apiVersion: v1
kind: Namespace
metadata:
  creationTimestamp: "2022-06-14T09:56:28Z"
  labels:
    kube-ns-suspender/controllerName: kube-ns-suspender
    kubernetes.io/metadata.name: test
  name: test
  resourceVersion: "3833"
  uid: a169bfbe-9b79-48cf-babb-4b888af0fe34
spec:
  finalizers:
  - kubernetes
status:
  phase: Active

Oh, my fault. I labeled instaed of annotated :D

Yes, my fault. It looks great! Thanks for that feature in UI, very useful:) Closing the ticket.


Godot does not support alpha in EXR images

Godot version:
3.1-alpha4
OS/device including version:
Ubuntu 18.10, GTX 970 (410.78)
Issue description:
Godot does not load/support alpha channels in EXR images.
Steps to reproduce:
Just create a simple image with transparency in GIMP and save it as .exr.
Minimal reproduction project:
exr-alpha-test.zip

At least there is code to support the alpha channel in https://github.com/godotengine/godot/blob/master/modules/tinyexr/image_loader_tinyexr.cpp, but maybe something is broken.

I'll take a look at this.

I found the issue.

Well, thanks! :)


LibWeb: Serialize empty InputEventInit data as an empty string

The specification https://w3c.github.io/uievents/#idl-inputeventinit doesn't seem to define this, but the changes in this PR align with the behavior of other browsers and the expectations of WPT.

Our IDL generator is doing things right and according to the spec
https://webidl.spec.whatwg.org/#LegacyNullToEmptyString
Now I believe there the problem is one of those

UIEvents spec is wrong. It should include [LegacyNullToEmptyString] attribute
WPT and all other browsers are wrong. Ladybird is right.

This does not seem to actually fix the error, I don't know


Added comments for betterment of the reader

Added comments for the betterment of reader

Description

Code sample

I don't understand your contribution because your description does not match your change.
For now, I will close this PR. Feel free to reopen or open a new one.


TypeError [ERR_INVALID_ARG_TYPE]: The "file" argument must be of type string

I tried installing asciicast2gif via both Docker and npm, however I get this:
$ sudo asciicast2gif /tmp/tmphnl6gqdg-ascii.cast /home/alex/Desktop/hstr-rs.gif
[sudo] password for alex:
==> Loading /tmp/tmphnl6gqdg-ascii.cast...
==> Spawning PhantomJS renderer...
/usr/local/lib/node_modules/asciicast2gif/main.js:697
Qe)}function ep(a){try{var b=a[0];return b.h?b.h(a):b.call(null,a)}catch(c){if(c instanceof Object)throw b=c,Yo(a[6]),b;throw c;}}function fp(a,b,c){c=Zo(c,dp(function(c){a[2]=c;a[1]=b;return ep(a)}));return r(c)?(a[2]=Nb(c),a[1]=b,dj):null}function gp(a,b){a=a[6];null!=b&&a.Dc(null,b,dp(function(){return function(){return null}}(a)));Yo(a);return a}
                                                                                ^

TypeError [ERR_INVALID_ARG_TYPE]: The "file" argument must be of type string. Received type object
    at validateString (internal/validators.js:125:11)
    at normalizeSpawnArguments (child_process.js:411:3)
    at spawn (child_process.js:545:16)
    at Function.exports.exec (/usr/local/lib/node_modules/asciicast2gif/node_modules/phantomjs-prebuilt/lib/phantomjs.js:72:10)
    at Ke (/usr/local/lib/node_modules/asciicast2gif/main.js:262:219)
    at Je (/usr/local/lib/node_modules/asciicast2gif/main.js:261:410)
    at Ie (/usr/local/lib/node_modules/asciicast2gif/main.js:261:320)
    at He (/usr/local/lib/node_modules/asciicast2gif/main.js:261:238)
    at Le (/usr/local/lib/node_modules/asciicast2gif/main.js:266:230)
    at xp (/usr/local/lib/node_modules/asciicast2gif/main.js:705:224)

I'm on Xubuntu 20.04 LTS.

I'm also seeing this issue.

same error to me, ditto

same error to me, ditto

The project is obviously abandoned.

The project is obviously abandoned.

The project is obviously abandoned.

okay then, quite right :-(

The project is obviously abandoned.

okay then, quite right :-(

to get a gif image from a .cast file generated with asciinema you can use this tool i develooped to make this task easly : https://github.com/foubian/cast2gif

The project is obviously abandoned.

There were different priorities indeed. Also, given the amount of problems asciicast2gif has I decided to approach the problem of gif generation differently and start from scratch. The result is https://github.com/asciinema/agg which is a successor to asciicast2gif, feel free to try it out.


Broaden range of compatible servant versions

AFAICT everything should still work with Servant 0.7, the current release.

Thanks! I had actually already moved to servant-0.7 on the devel branch, which is now merged.
There I've gone for just servant >= 0.5. Do you think it should have the upper bound < 0.8? I'm not sure what the best practice is here, but given that servant is evolving rapidly it's probably not a bad idea.

Thanks! I had actually already moved to servant-0.7 on the devel branch, which is now merged.

Oh, great - didn't see that branch.

There I've gone for just servant >= 0.5. Do you think it should have the upper bound < 0.8? I'm not sure what the best practice is here, but given that servant is evolving rapidly it's probably not a bad idea.

I'm not sure what the best practice would be, either. I'd probably be inclined to leave it at >= 0.5 and see what happens. With < 0.8 this package is certain to stop working when 0.8 comes out, and without it, there's a good chance it will just stop compiling, in which case you can add the bound or update the code as necessary.

P.S. I'd suggest either making devel the default branch on github, or just develop on master. It's much more straightforward for contributors then -- you can always keep a somewhat-less-visible "stable" or "release" branch too.


Release azure-cli-iot 0.1.8

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[ ] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).

Command Guidelines

[ ] Each command and parameter has a meaningful description.
[ ] Each new command has a test.

(see Authoring Command Modules)

Reviewers, please verify the following for this PR:

[ ] The PR title has format Release <component-name> <version>.
[ ] setup.py has been modified with the same version as in the PR title.
[ ] HISTORY.rst has been modified with appropriate release notes.
[ ] If releasing azure-cli or azure-cli-core, __version__ defined in __init__.py should also be modified to match.

Started releasing azure-cli-iot 0.1.8...

Release of 'azure-cli-iot' with version '0.1.8' successful. View at https://pypi.python.org/pypi/azure-cli-iot/0.1.8.

GitHub release created. https://github.com/Azure/azure-cli/releases.


Upgrade Policy Add-on Gatekeeper image to v3.7.0

Verified the new image with E2E and manual tests.

@robbiezhang and @allenjzhang  - can you approve this PR when you get a chance?


Bug light card

Home Assistant release with the issue: 0.105.4
Last working Home Assistant release (if known): Probably 0.104 or 0.101
Operating environment (Hass.io)
After the last update, the light card stopped displaying correctly and there is no way to change the lighting effects. https://share-your-photo.com/7ce77f03dd

Please open only one issue and in the correct repo -> frontend https://github.com/home-assistant/home-assistant-polymer/issues/4883.


Release memory after deduping

Motivation

We call sortAndDedupe to shrink the nameHashes field of UsageHash.
(This structure is used to remember the names of symbols that a file might
use, so we know which downstream files might need to be retypechecked.)
This was causing all FileHash's in Stripe's codebase to take up about 6x
the space that it needed to. After shrinking, Sorbet uses about 1/6th the
memory to store all FileHash objects.
Note that this cost was only paid for cold-cache runs of LSP. Warm cache
runs of LSP would read file hashes from the cache, which would not have
serialized the unused capacity in these vectors.
So while this is definitely an improvement, it's not an improvement that
applies to 100% of LSP initializations. (But it does reduce the worst
case.)
Test plan

For correctness: existing tests
To check memory reduction: I have a WIP branch, based on top of #6827, which
adds a lot of writes to the trace file. It also adds another metric for
current_rss. This lets me see correlate the current RSS with given phases of
Sorbet. I can see that the current and max RSS values drop by the expected
amount for cold-cache LSP initialization requests.

Is it possible that we could be more clever and use less memory along the way, rather than just at the end?

Is it possible that we could be more clever and use less memory along the way, rather than just at the end?

I plan to check this in a future change. For now, I want to lock this in.


Victor VosMottor: Watch +27655652367

Victor VosMottor requests the watch of the watch_number +27655652367. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Spevacus in Charcoal HQ


Assistants API support

Support for the OpenAI submit tool outputs to run action is left unimplemented.
Some existing documentation examples' breaking styling was fixed. Yet, most of the examples still look unpolished and need attention.

When adding this functionality I was trying to keep the new code consistent with the existing one. Trying to do that I stumbled upon a number of issues which I'm outlining here for your consideration.

The naming of the functions is generally inconsistent. The are many fetch functions which submit a POST request, meaning they are not fetching but creating a resource, albeit a non-persistent one. Additionally, using fetch for what are list requests gets in the way, making it necessary to use awkward names such as fetch_by_id for separation. That is exacerbated by the fact sub-resources cannot be accessed by a single id in the first place, which makes the name even less fitting.

The above drives the external api inconsistency which has to use the same function name, e.g. files() and files(id) to perform a semantically different operation.

The existing naming issues lead to some new inconsistency in the naming of the added functions. Example: the assistants is a function returning either a list or a singular entity. The new assistants and threads resources have deeper hierarchy of sub-resources, meaning further compounding of the function names, e.g. assistant_file_create or thread_message_create. Using the assistants prefix along with the plural for the files sub-resource (assistants_files_create) is inconsistent with the syntax of the natural language. Because of that I'm using singular resource names for sub-resource CRUD functions while realizing it is not in line with the existing code.

The facade OpenAI module grew enormously while not bringing any benefit. Instead the individual endpoint adapters should be considered to be exposed and imported by the user directly. This could be similar to what ex_aws does, but might also be limited to splitting the facade to several smaller modules.

The crud operations are repetitive and contain no individual logic, therefore can be generalized. There are also some non-RESTful actions such as Create thread and run which may complicate the generalization.

Facade module tests should be implemented.

@mgallo thanks for all your help so far with the library
@nicnilov thanks for working on integrating the Assistants API
@mgallo are you still planning on working/maintaining this library?

@nicnilov also check out https://github.com/restlessronin/openai_ex

Thanks, wasn't aware of it.

Hi, thanks a lot for the PR and all the feedbacks.
These are somewhat complex days and I don't have much time to follow the library, but I will try to review/merge these PRs for new features and give support for blocking bugs.
Unfortunately I am involved in other projects I am prioritising, so a refactoring of the library will not be done anytime soon.
Thank you for your patience and support

No worries completely understand
thanks!


adds a user for running the docker image

in order to avoid conflicts and permission weirdness.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>05786ba214af1f7d8db26ef94dc2a0-PR-25

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 71.635%

Totals

Change from base Build 23bc42a852d06630e0297bb14df1946cb5a70497:
0.0%

Covered Lines:
149

Relevant Lines:
208

💛  - Coveralls

Hm, interesting. Can you describe what and why it happened? I'm curious now.

Essentially, whenever we run certain commands, we assume the user with id 1000 - the same user the image has builtin. If we don't do that, the _build folder will be owned by root after compilation, which is tricky when you want to use local tooling (e.g. LSP) from you editor, as your local user will get permissions denied from files belonging to root.
The user id 1000 is the default for a lot of Linux users, not sure if it's the same for MacOS. Currently trying to pass the current users id as a build arg to the image build through make, i.e. make setup should bake in your own local user id.


CSS

CSS
User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I see a dark blue header and footer, and four boxes with a shadow

Added a CSS style sheet (./assets/style.css) that adds a dark blue header and footer and four boxes with shadows.


Updated the real gateway name

I spent a lot of time finding the gateway name because using simply 'SecurePay' didn't work.
It returns 'Omnipay\SecurePay\Gateway' not found.
After spent hours of research the real gateway name is 'SecurePay_DirectPost'

Yep that readme is a bit misleading.
Looks like it actually needs the addition of 'SecurePay_SecureXML' as well as that is the other option this package provides.


Improvements for CLI

Using this as a placeholder for small improvements made to the command line, so it is easier to use the tool and minimize number of keystrokes needed for achieving common tasks.
force
Add -f alias for --force, quite common to force running a step, like prepare
scenario as argument
Transform scenario from being an option to be an argument, or allow both
# before
molecule prepare -s foo
# after
molecule prepare foo

This is possible be I do not yet see a use to have more than one action on a single call, which means that following argument can be used to mention scenario to apply to.
Mention force option when returning skipping
When running on interactive tty (opposed to CI), it could be useful to mention that user can use force option to enforce execution of a prepared host.

I would like to be able to specify multiple targets (might make the "scenario as argument" option less viable). E.g. I find myself doing this a lot:
molecule -c ../path/to/shared.yml destroy -s foo
molecule -c ../path/to/shared.yml lint -s foo
molecule -c ../path/to/shared.yml converge -s foo

It would be great if I could, like with "make", do this all at once
molecule -c ../path/to/shared.yml destroy lint converge -s foo

And have it execute them in the order specified.

This is what test sequence does mainly and btw, if you put config into REPOROOT/.config/molecule/config.yml you no longer need to specify it.
Basically you would have to only run molecule test -s foo

Sometimes "test" just does too much. Yes, I know there's the --destroy never option, but saving the resource isn't the only reason I'll iterate on converge. Sometimes I don't want verify/idempotence/side_effect to be running, and just want to iterate on converge until the process is running as expected.
And as for the global config, while that is good to know it's not applicable in my case. Each collection I work on (two of my personal and at least one for $DAY_JOB) has a different base configuration that's used in their CI pipeline. Since it's always stored at the same location across all of them I use a Bash alias, but the point still stands.
Less controversial and probably easier to tackle: "-h" as a shortcut for "--help" would also be nice.

I am going to close this ticket because it too broad and not directly actionable. Still, anyone is welcomed to raise PRs to improve the CLI and reference this ticket.


Update README.md

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

I'm not sure what you're trying to do here, but this isn't something we can merge, as it removes functionality.


How can I compute sum of a slice of matrix?

// S is a Matrix
sum(S[0..<1, 5..<10])? // doesn't work because MatrixSlice is not LinearType

Is there a workaround for it?
Ultimately, it would be easier to maintain I guess if there are less number of data types, e.g., everything is ndarray in numpy.. until then, hopefully more documents to come! ReadTheDocs would be perfect, but simple readme.mds would do the work pretty well, too, for APIs/inheritance/etc.  I'm up for contributing to it if there's anything I can.

It doesn't work because it is a 2D data structure (QuadraticType) but sum expects a 1D data structure (LinearType). You would need to flatten it first. I think it would be good to have a flatten method on TensorTypes to convert to an array.
I'll look into ReadTheDocs, it already has some docs in the code it's just a matter of running Jazzy on it. I do think it could use some simplification, but it's always a compromise between performance and convenience.

think it would be good to have a flatten method

Agreed!

ReadTheDocs

I think so, at the moment RTD could be a burden. I'll keep the hackmd document updated, could be useful later :)


Generators break between fusion-cli 1.9.0 and 1.11.4

to reproduce, add a generator somewhere in the current create-* scaffold and be sure to use it so it's not tree shaken.
yarn create fusion-app fusion-debug-app-2
cd fusion-debug-app-2

in ./src/pages/home.js
function* foo() {
  yield 1;
}

const fooSequence = foo();

//...

<FusionStyle>My app {fooSequence.next().value}</FusionStyle>

see that it compiles correctly using yarn build-production
update fusion deps: yarn add fusion-cli@latest fusion-core@latest fusion-tokens@latest
try to build-production again. yarn build-production
notice the following error:
error: (client) client-main-ae625f7157fa3294ebf9.js from UglifyJs
Unexpected token: operator (*) [./src/pages/home.js:49,0][client-main-ae625f7157fa3294ebf9.js:76,8]

If I comment out these changes to exclude generators, the project compiles: https://github.com/fusionjs/fusion-cli/blame/bd180b7ec79ed45cd475f4159d28421d668a2b01/build/get-babel-config.js#L98
the project compiles but doesn't run with the error:
home.js:49 Uncaught ReferenceError: regeneratorRuntime is not defined
    at Module../src/pages/home.js (home.js:49)
    at __webpack_require__ (bootstrap:782)
    at fn (bootstrap:150)
    at Module../src/root.js (pageNotFound.js:11)
    at __webpack_require__ (bootstrap:782)
    at fn (bootstrap:150)
    at Module../src/main.js (main.js:2)
    at __webpack_require__ (bootstrap:782)
    at fn (bootstrap:150)
    at reload (client-entry.js:16)
```

Thanks for the reproductions steps. This is fixed by https://github.com/fusionjs/fusion-cli/pull/557 and released in<EMAIL_ADDRESS>


significantly improve performance by asExternalTypedData

by using asExternalTypedData+setRange instead of Pointer.store

r? @shanehop @sjindel-google

Thanks for the contribution @truongsinh, this is awesome! :trophy:


Add no arch option

Adding a no arch option allow forcing the tcg accelerator. This
allows lima to run on AMD based hackintosh machines and other macos
machines that does not support hvf.

This is essentially like adding cpu.x86_64.qemu64 to the configuration. Thus closing this


Tagging the generated C# code as auto-generated

Could you please provide a description for this pull request? I can tell the effect is to add a comment to the top of generated files, "// ", as well as add this codegen attribute to many of the classes, but I am not sure why we should do this. What is the benefit?

Could you please provide a description for this pull request? I can tell the effect is to add a comment to the top of generated files, "// ", as well as add this codegen attribute to many of the classes, but I am not sure why we should do this. What is the benefit?

Sorry, forgot to add one. Will do.


Add cors rule in request/response for Cosmos DB

This change adds the existing "cors" property to most recent api versions. This change has been present in our service for a while, but was overlooked when originally adding the swagger. The two API versions being updated do not yet have wide usage.
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

@yungezz can you please take another look at this? As noted, this is fixing a swagger bug to match what is currently in production.

approve since this is Swagger bug fixing PR. hi @shurd is this PR ready to merge?

hi @yungezz this is ready to be merged


CompletionType items can come back null

I was trying to track down the source of a decoding error I've been seeing. It looks like textdocument/completion can return a result with the items property null. By my reading of the LSP spec, this could be an empty array, but never null.
I'm able to reproduce this by requesting completions from within a comment block:
{"id":5,"result":{"isIncomplete":false,"items":null},"jsonrpc":"2.0"}

Does this sound like an issue, or is it that I'm misunderstanding the spec?

Awesome -- thank you for looking at this!


SCB-405 support to disable the discovery client with configuration

Now user can disable the discovery client with below configuration:
servicecomb:
   discoveryClient:
      enabled: false

Coverage increased (+0.006%) to 87.214% when pulling dc5f973a992bc3065183dbb688ea6f48e290d99d on SCB-405 into e54338354e5547c3fbc1e80bc6d0c9cf98bf39b8 on master.


chore(typings): updated catch signature to allow T to flow through

Description:
This allows catch to flow it's types by default, but also allows for additional casting if needed.
Related issue (if exists):
#1672

Cool, this is reason I wasn't able to repro since I didn't try with catch? :/

Catch was causing Observable<any> to start flowing through, which isn't quiet correct :(

Merged with 56a12ba, appreciate for quick triaging @david-driscoll


2/04 PM Publish

Docs Build status updates of commit 39ac9ba:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azuredmps-0.9.0/AzureRM.DeploymentManager/Get-AzureRmDeploymentManagerService.md
:white_check_mark:Succeeded
View (azuredmps-0.9.0-preview)

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


WIP: Add an UPDATE with ORDER BY that fails.

This PR demonstrates a corner case that we use in our code, where UPDATE is used with ORDER BY. I'm not sure how to resolve it, so it's a WIP.
The root cause is that ORDER BY causes the row index to reset in this statement:
return new QueryResult(array_values($rows), $result->columns);

However, removing array_values causes errors in other tests!

Error caused:
/opt/homebrew/bin/php /Users/rguico/code/php-mysql-engine/vendor/phpunit/phpunit/phpunit --configuration /Users/rguico/code/php-mysql-engine/phpunit.xml.dist --filter "/(Vimeo\\MysqlEngine\\Tests\\EndToEndTest::testUpdateWithOrderAndPrimaryKey)( .*)?$/" --test-suffix EndToEndTest.php /Users/rguico/code/php-mysql-engine/tests --teamcity
Testing started at 10:38 AM ...
Cannot load Xdebug - it was already loaded
PHPUnit 9.6.17 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.3.1
Configuration: /Users/rguico/code/php-mysql-engine/phpunit.xml.dist
Random Seed:<PHONE_NUMBER>

Vimeo\MysqlEngine\Processor\SQLFakeUniqueKeyViolation : Duplicate entry '7' for key 'PRIMARY' in table 'video_game_characters'
 php-mysql-engine/src/Processor/Processor.php:226
 php-mysql-engine/src/Processor/UpdateProcessor.php:25
 php-mysql-engine/src/FakePdoStatementTrait.php:237
 php-mysql-engine/src/Php8/FakePdoStatement.php:16
php-mysql-engine/src/FakePdoTrait.php:185
php-mysql-engine/tests/EndToEndTest.php:1144


packer example in README should specify requirement for sql.nvim

Just as a note: the packer plugin spec in the README probably ought to add a requires = 'tami5/sql.nvim' key, for people who just copy-paste that example and miss that sql.nvim is required.

Thanks, I'll add that.
Telescope will soon have a :checkhealth that will also highlight the dependency.


fix: 🐛 chang the call order of scale and translate

Description
解决非scroller模式下滚轮滚动，graph的tranlate位置不正确问题
Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Enhancement (changes that improvement of current feature or performance)
[ ] Refactoring (changes that neither fixes a bug nor adds a feature)
[ ] Test Case (changes that add missing tests or correct existing tests)
[ ] Code style optimization (changes that do not affect the meaning of the code)
[ ] Docs (changes that only update documentation)
[ ] Chore (changes that don't modify src or test files)

Self Check before Merge

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Pull Request Test Coverage Report for Build 378531831

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 0.0%

Totals

Change from base Build 378235736:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls

/rebase


Test suite

This PR adds a test suite (using pytest).
It will also add a CI (Continuous Integration) webhook to automatically check new pull-requests to this repository to ensure that they do not break existing tests.

[x] Document
[ ] Detector, Flag, & Issue
[x] PersonalLifeDetector (Pending merge of #25)
[x] EffortDetector (Pending merge of #25)

Finally, it adds a code linter (pylint) to check for consistent code style. This enables us to keep the code readable in an objective, fewer-arguments sort of way :)

Good points — added!


After created bill and assign all user  it created bill but it also show haven't create menu

@RyukungG  can you explain more about this?

Cant replicated


Physical PCI Devices - qemu.conf always assigns bootIndex arg

Issue Description
When adding a physical PCI device to an instance, the corresponding block in qemu.conf will contain a bootIndex argument, but not all drivers will support this.
Steps to reproduce
lxc init images:ubuntu/22.04/cloud vm --vm
lxc config device add vm dev pci address=...
lxc start vm         # This fails.
Output of lxc info --show-log vm:
qemu-system-x86_64:/var/log/lxd/vm/qemu.conf:266: Property 'vfio-pci.bootIndex' not found
Information to attach
This seems to be connected to a3cf5ec0d, particularly here, with the following snippet:
type qemuPCIPhysicalOpts struct {
	dev         qemuDevOpts
	devName     string
	pciSlotName string
	bootIndex   int
}

func qemuPCIPhysicalSections(opts *qemuPCIPhysicalOpts) []cfgSection {
	deviceOpts := qemuDevEntriesOpts{
		dev:     opts.dev,
		pciName: "vfio-pci",
		ccwName: "vfio-ccw",
	}

	entries := append(qemuDeviceEntries(&deviceOpts), []cfgEntry{
		{key: "host", value: opts.pciSlotName},
		{key: "bootIndex", value: fmt.Sprintf("%d", opts.bootIndex)},
	}...)

@masnax thanks! Out of interest what sort of PCI device were you passing through to find this?

@tomponline Oh just the audio device for my GPU.


Device Network ID collision with another DTH

I struggled for days to find out why nothing was coming out of my SmartThings hub into the Bridge. Finally I noticed an error in the live logging that referred to a Device Network ID (DNID), hinting that it wasn't unique.
Turns out both cast-web-api and smartthings-mqtt-bridge both use the MAC address of where they run, as the DNID. As I had installed cast-web-api first, I suppose it got all the messages destined for smartthings-mqtt-bridge.
I hacked the DTH to prefix the MAC with "MQTT", to make it more likely to be unique. Immediately, I started getting MQTT messages through.
Now I just have to work out why I can't get any traffic going the other way...

Di you find a way to solve this ?
I have exactly the same problem and running both in Docker

Yes, I hacked the DTH code to prefix the MAC with "MQTT", to make it more likely to be unique.
But I gave up on trying to use MQTT.

MQTT working for me, let me know if I can help
Could you point me the exact places you had to modify DTH?
I thought it was the way ST hub was communicating, not related to code

I can do most of what I want without MQTT, so there isn't an urgent need. But it'd be nice - when I get a bit of time.
My diff looks like the below:
<     // Setting Network Device Id
<     def hex = "$settings.mac".toUpperCase().replaceAll(':', '')
<     if (device.deviceNetworkId != "$hex") {
<         device.deviceNetworkId = "$hex"
<         log.debug "Device Network Id set to ${device.deviceNetworkId}"
---
>     def hex = ""
>     if (device.deviceNetworkId == NULL || device.deviceNetworkId == "") {
>         // Setting Network Device Id
>         //hex = "MQTT"+$settings.mac.toUpperCase().replaceAll(':', '')
>         hex = ipToHex(settings.ip+":"+settings.port)
>         log.debug "debug:"+hex
>         if (device.deviceNetworkId != "$hex") {
>             device.deviceNetworkId = "$hex"
>             log.debug "Device Network Id set to $hex -> ${device.deviceNetworkId}"
>         }

I originally just prefixed the right-hand-side of the assignment to hex with the string "MQTT". This is now commented out and replaced - not because it didn't work but because it didn't make sense to me to use the MAC address at all.
The MAC address is unique to the device, but not to the services running on the device. Instead, it makes sense to use something that's unique to the service (and doesn't have to be unique to the site because it will always operate in the local network).
So the new code gets the IP address and port number of the listening socket, converts them to hex and joints them together with a colon. In this way, a different service listening on a different port will have a different device ID even when it's running on the same device (thus same MAC).
The call to ipToHex() refers to a function I added, but didn't include in the above diff, for clarity. It looks like this:
// accepts a IP:PORT string and converts it to a hex identifier
// for setting the SmartThings deviceNetworkId
// NOTE: does not handle octet less than 0x10 = 16!
private String ipToHex(String ip) {
  def parts   = ip.tokenize(':')
  def address = parts[0]
  def port            = parts[1]
  def octets  = address.tokenize('.')
  def hex             = ""

  log.debug "converting ipToHex"
  octets.each {
    hex = hex + Integer.toHexString(it as Integer).toUpperCase()
  }
  hex = hex + ":" + Integer.toHexString(port as Integer).toUpperCase().padLeft(4,'0')
  return hex
}

Great ! Thank you I will def try that !
@stjohnjohnson  could we integrate this kind of mod ? I think it would help many people


[authorization/role-assignment]:  Setting a scope

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Bug
Module Name
avm/ptn/authorization/role-assignment
(Optional) Module Version
0.1.0
Description
The Scope "resource group" and "subscription" are not valid for this module. Permitted scopes: "managementGroup"
While the metadata claims that all scopes are possible.
(Optional) Correlation Id
No response

@ppons1997 - Thanks for reaching out. I agree that the working in the metadata sounds a little confusing. We will look at what we can do to provide some clarification. The module is designed to make the role assignment at the management group, subscription or resource group level. The deployment scope for the Bicep code will be at the Management Group. The module looks for the addition of the subscription or the subscription and resource group parameters to determine where the role needs to be set at.
Here is a little code snippet that would make the role assignment at the resource group level.
module roleAssignment 'br/public:avm/ptn/authorization/role-assignment:0.1.0' = {   name: '${uniqueString(deployment().name)}-test-${serviceShort}'   params: {     principalId: nestedDependencies.outputs.managedIdentityPrincipalId     roleDefinitionIdOrName: '/providers/Microsoft.Authorization/roleDefinitions/c2f4ef07-c644-48eb-af81-4b1b4947fb11'     principalType: 'ServicePrincipal'     location: resourceLocation     subscriptionId: subscriptionId     resourceGroupName: resourceGroup.outputs.name   } }
If you remove the resourceGroupName parameter then the role assignment would take place at the subscription level. And subsequently if you remove the subscriptionID then the role assignment would take place at the management group level.


Binaries for newer versions of libgit2?

The latest version of libgit2sharp.nativebinaries NuGet package contains binaries for the version 0.28.0 of libgit2. However, there have been many releases since:

0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.99.0
1.0.0
1.0.1
1.1.0

They contain some useful fixes that would be nice to have. Are there any plans to publish binaries for these newer versions?
Thanks

I'm also wondering if there is a particular reason why it isn't updated to a newer version.
I've cloned both repositories libgit2sharp and this one, made a few changes to get it running with net5 and Visual Studio 2019.
Then I've updated/compiled/packaged this repo to use the source of libgit2 1.1.0 with the provided scripts.
Then I ran the tests in LibGit2Sharp.Tests (which uses the new binary package) and only 5 tests failed:

I think it would be nice to have an additional nuget alpha preview release of libgit2sharp with the 1.1.0 binaries, so more people are able to test it.

This now seems to be available at:

https://github.com/libgit2/libgit2sharp.nativebinaries/pull/114
https://github.com/libgit2/libgit2sharp.nativebinaries/pull/115

But it seems there is no one looking at this project anymore :-(

@DvdKhl  With the package produced by #114 I was able to run all tests successfully with only a few minor changes. "origin/HEAD" is now added when cloning (see https://github.com/libgit2/libgit2/pull/5651) and some tests are failing because they are counting the branches after clone.
I didn't have any issue with CanGetBlobAsTextWithVariousEncodings or NoPublicTypesUnderLibGit2SharpCoreNamespace.
I will create a PR but I need to reference the new package which is not on nuget.org for the CI to pass.

@jairbubbles #114 has been merged, and I've published 2.0.315-alpha.0.1 with the changes.

Looks awesome to me!

I create a draft PR here in libGit2Sharp => https://github.com/libgit2/libgit2sharp/pull/1905/

Since we now have packages up on nuget.org with newer versions, I'm going to go ahead and close this.


Specify minimal required Rust version

The pkg-config 0.3.10 update broke downstream crates on Rust 1.21...
error[E0599]: no method named `to_ascii_uppercase` found for type `char` in the current scope
   --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/pkg-config-0.3.10/src/lib.rs:538:28
    |
538 |     name.chars().map(|c| c.to_ascii_uppercase()).map(|c| {
    |                            ^^^^^^^^^^^^^^^^^^
    |
    = help: items from traits can only be used if the trait is in scope
    = note: the following trait is implemented but not in scope, perhaps add a `use` for it:
            candidate #1: `use std::ascii::AsciiExt;`

I run cargo-audit in CI for most of my crates, which depends on pkg-config (directly or indirectly). Unfortunately this means that I cannot use cargo-audit in CI for crates supporting Rust 1.21 without adding a separate build step that runs on a newer version.
Would it be possible to specify the minimal required Rust version, to add that version to CI and to consider changes to the minimal version a breaking change?

Oops sorry about that, PRs are of course welcome to tweak and fix this!


2-Sample Permutation test

Describe the new feature or enhancement
Please provide a clear and concise description of what you want to add or
change.
Hi, I would like to add a 2 sample permutation T-test to MNE. I was in a rush a while back and was unable to use the permutation_cluster_test because I could not get an adjacency matrix with the data I had. Other permutation tests were all one sample. I tried using other packages, but realized all the statistical packages for python that had a permutation test ran into one or more problems: couldn't handle nan values well, weren't invariant to the number of dimensions, or had very strict array requirements. Here is the test I threw together at the time: https://github.com/Winter-Bot/2sample_Permutation_ttest . It takes into account nan values in the ttest, it is able to take data arrays from 2D to 4D, and it can take pure arrays or a list of arrays, so long as the first dimension is the observations/participants.
Describe your proposed implementation
Describe how you think the feature or improvement should be implemented (e.g.,
as a new method on an existing class? as new capability added to an existing
method?) If you're not sure, please delete this section and the next section.
I was wondering if you wanted me to fork it. Or you could take it and modify it, adding it to other existing code. That is okay too.
https://github.com/Winter-Bot/2sample_Permutation_ttest
Describe possible alternatives
If you've suggested an implementation above, list here any alternative
implementations you can think of, and brief comments explaining why the chosen
implementation is better.
forked to mne.stats. or included into one of the other existing permutation test.
Additional comments
Add any other context or screenshots about the feature request here.
I tested my code against these:
(1)	nnstats.permtest_rel() (Network Neuroscience Lab at McGill University, 2018)
(2)	mlxtend.evaluate.permutation_test() function from Raschka, Sebastian (2018)
(3)	mne.stats.permutation_cluster_test() function (Gramfort et al., 2014)
(4)	permutation_test() functions from Python Software Foundation (2017)
with HCP-MEG eravg data and tfavg data. I did a short write up if you want to see it let me know.
I have it give several types of outputs, each one being more or less applicable depending on the type of data being input. If you want to take it and completely reformulate it that is fine too. If you have questions for me or need me to change anything on it, you can reach me at<EMAIL_ADDRESS>

can you provide a code snippet that fails with mne.stats and works with
your code? thx

It's not that the code fails, it's that the only 2 sample permutation test
is the cluster analysis (correct me if I am wrong). For me this didn't work
because I couldn't get an adjacency matrix due to the data constraints.
When I bypassed the adjacency matrix part the cluster analysis echoed nan
values throughout the data. So if participant 1 was missing electrode 1,
(due to not having an adjacency matrix I also couldn't interpolate bad
channels) then the out put would have nan values for electrode one. With 83
participants this left me with an output of mostly Nan values. But no
errors. So the cluster analysis is probably a better test to run, but some
constraints on data may make it harder to use. At least that was what I
observed, feel free to let me know if there was a better way I missed.
Best,
Matt
On Wed, Feb 3, 2021, 3:01 AM Alexandre Gramfort<EMAIL_ADDRESS>wrote:

can you provide a code snippet that fails with mne.stats and works with
your code? thx

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/8832#issuecomment-772314509,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJJHQ4FZ4LPPKPWLHL7ECVLS5D7GPANCNFSM4W72ZTKQ
.

when you run permutation_cluster_test you can pass a custom stat_fun (i.e., one that handles NaNs gracefully).  Some of the scipy.stats functions have a nan_policy='omit' option that might work for your use case; it might be enough to freeze that parameter using partial() --- or you may need to write a more complicated wrapper --- before passing it to stat_fun.

Thanks, I didn't try all the options with the cluster analysis. I'm a bit
new to MNE, so I was finding the cluster analysis I bit too much to work
with. The scipy.stats functions on the other hand were too inflexible. I
probably could make a better wrapper, but I wouldn't know where to begin
with that in all honesty. It was just easier for me at the time to write a
stripped down test that was better at handling the particular issues I was
running into, being nan values and varying array dimensions. If you can't
use it that's fine, just thought I'd share it incase.
On Wed, Feb 3, 2021, 1:51 PM Daniel McCloy<EMAIL_ADDRESS>wrote:

when you run permutation_cluster_test you can pass a custom stat_fun
(i.e., one that handles NaNs gracefully). Some of the scipy.stats
functions have a nan_policy='omit' option that might work for your use
case; it might be enough to freeze that parameter using partial() --- or
you may need to write a more complicated wrapper --- before passing it to
stat_fun.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/8832#issuecomment-772726758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJJHQ4HVGLY3RYKBNNXJ3MLS5GKKDANCNFSM4W72ZTKQ
.


Size can also be used with dot notation

Size can also be used with dot notation (for example, {{ my_string.size }})

Changes Unknown when pulling 2f66953d18522d8fb1d211783dc2f50d021be52f on chenos:master into ** on harttle:master**.

Changes Unknown when pulling 1754b3493a574f3502c608c9976fbf6b6d6bd57c on chenos:master into ** on harttle:master**.

In my understanding, it would be more clear to use .length to read the length property, rather than to read a .size property and do special calculations.
This will be rather confusing when there's already a size property exists there.

.size is designed for cross platform compatibility, ensure that syntax is the same as native liquid(ruby), javascript environment .size is .length alias.
https://shopify.github.io/liquid/filters/size

OK, sounds good. Published @1.7.5


AccordionView worked in android emulator, dont worked in Orion 4.2.2

Dont worked in ScrollView, i removed ScrollView and accordion started to work.

Forgive my ignorance, what's Orion? It should work inside a Scrollview, can you provide me some xaml so I can chek it?

Sorry for my eng. Orion is old operation system of android.

my company forces everyone to test on such an operating system

Sorry but I cant' support a SO if I can't test on it. If you find a fix, do a pull request and I will consider it.


[COOK-3155] Be able to install chef-client from omnibus packages

https://tickets.opscode.com/browse/COOK-3155

More on this, to quote someone knowledgeable on the history here, regarding why chef-client doesn't support updates:
First, the chef-client cookbook concerns itself with the configuration of the chef-client program. When building cookbooks it is generally advised to keep their focus narrowed to a specific component. This means that for chef-client we're mainly concerned with the configuration (/etc/chef/client.rb), and running it regularly, be that as a service or a cron job.
Second, the cookbook predated the creation of omnibus, and at one point attempted to handle upgrading the chef gem. [snip]. When omnibus came along, the upgrade process became more complex. We now have an API service that concerns itself with determining the right package file to retrieve for installation, but we (CHEF) never really wrote a client to handle that because we had the install.sh script do it.
Heavy Water created the omnibus-updater cookbook to cover this gap. It works very well. At this point in time there is probably enough adoption of that cookbook that converting people to use something else is like turning a barge in a river.
Migrating the functionality of the omnibus-updater cookbook to the chef-client cookbook would make the latter's codebase more complicated (it's already reasonably complex) and potentially difficult for users and contributors to follow. It would require more effort in testing and we simply don't have the bandwidth for that. Heavy Water is doing a good job of maintaining that cookbook and I'm inclined to keep it that way, rather than try to absorb that into our cookbook


Reproducibility of regress_out() results

Hi
I encountered a problem with regress_out function. The returned X matrix for the same input anndata varies for subsequent iterations. The function doesn't have any parameter such as "random_state" or "seed". Have you noticed this problem before? Is there a way to make this function more stable and return reproducibile results?
Thanks!

Thanks for the report! I believe the results should be the same for multiple runs.
Could you provide an example of this? I'm having a bit of trouble reproducing. Here's what I ran:
import scanpy as sc
import numpy as np

pbmc = sc.datasets.pbmc68k_reduced()
a = pbmc.copy()
b = pbmc.copy()

sc.pp.regress_out(a, "phase")
sc.pp.regress_out(b, "phase")

assert np.array_equal(a.X, b.X)
assert not np.array_equal(a.X, pbmc.X)

Is this what you meant?

As we haven't heard back after the question we will close the issue for now, hopefully you obtained the expected behaviour in the end :)
However, please don't hesitate to reopen this issue or create a new one if you have any more questions or run into any related problems in the future.
Thanks for being a part of our community! :)


Fix flaky test - AdminResourceSuite: delete engine - user share level

Why are the changes needed?

close #3751
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

UT passed one time, try again

retrying https://github.com/apache/incubator-kyuubi/actions/runs/3384044997

Passed again

try again

cc @cfmcgrady @wForget
I do not know why indeed.

I'm also confused about this, but this fix looks good.

cc @cfmcgrady @wForget
I do not know why indeed.

Is it possible that serviceNode: PersistentNode is automatically recreate after being deleted?

Is it possible that serviceNode: PersistentNode is automatically recreate after being deleted?

Not sure, but it did can be deleted finally.

- JpsApplicationOperation with jstat *** FAILED ***
  null equaled null (JpsApplicationOperationSuite.scala:56)
  S0     S1     E      O      M     CCS    YGC     YGCT    FGC    FGCT    CGC    CGCT     GCT
  0.00 100.00  92.04  78.54  96.79  87.17     45    0.786     0    0.000    22    0.470    1.255
  0.00 100.00  93.81  78.54  96.79  87.17     45    0.786     0    0.000    22    0.470    1.255

thanks, merging to master


wip: stream prototype

WIP: stream prototype
TODO:

prepare RFC on methods of working with streams
scale the current solution to all endpoints

Trying to re-implement it with another lib
const StreamArray = require('stream-json/streamers/StreamArray');
const {chain}  = require('stream-chain');
const {parser} = require('stream-json');

// Assume that keysStream is a stream returning key objects
let pipeline = chain([
  keysStream,
  parser(),
  new StreamArray(),
]);

// Create a function that yields a JSON string with meta information and keys
async function* generateJSON() {
  yield '{ "meta": ' + JSON.stringify(meta) + ', "keys": [';

  for await (const keysBatch of pipeline) {
    yield JSON.stringify(keysBatch.value) + ',';
  }

  yield ']}';
}

// Send the stream as a response
reply.type('application/json').send(generateJSON());

Since we need to collect json of complex shapes we have to write an additional function on generators, and the use of this library is reduced to the fact that we organize more beautiful chain
It is possible not to use libraries at all, but to write your own generator.