Sound volume[FEAT]

Very cool! Works perfect!
One thing that would be nice, a possibility of adjusting the playback volume settings with props.
i.e playback sound 50%

:tada: This issue has been resolved in version 7.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix invalid table row formatting and default value

Fixes https://github.com/NuGet/docs.microsoft.com-nuget/issues/2721

Docs Build status updates of commit 22391ed:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/msbuild-targets.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add the ask() method to our Langchain::ActiveRecord::Hooks

Motivation
We'd like to expose the ask() method so that you can utilize the RAG (Retrieval Augmented Generation) flow when operating on the ActiveRecord model.
Steps
In the Langchain::ActiveRecord::Hooks class, similar to the similarity_search() method we should expose the ask() method.
This method should be just forwarding the ask() method along to the vectorsearch provider. You can see how the ask() method works by looking at any of the implementations inside of the vectorsearch/* classes.
Expected behavior:
Recipe.ask(question: "...")

# Top results are fetched from the vectorsearch DB and inserted as a context

# LLM produces a response

@yorzi Want to take a stab at this?

@andreibondarev Yeah, let me start from this one.


Remove Air Emission Data

As an ECMPS user, I want the ability to remove Air Emission Data so that I can update Relative Accuracy Data as needed
Acceptance Criteria:
Given I am in the Air Emission section
When I click on the 'Remove' option for Air Emission
Then I see that the relevant AET data record is deleted
Given I chose to remove Air Emission Data
When I click on the 'Remove' option
Then I see a message 'Are you sure you want to remove the selected data?'
And when I click Yes
Then the data is removed
And the update shall be reflected in the Air Emission section
When I select Cancel
Then I am returned to the landing screen for Air Emission Data
Invision Board:
https://projects.invisionapp.com/freehand/document/SrHrFhGQ3?zoomToItems=Y2w2YXc0OThtMDBqaDNiNnlnanNjaWF4Mg%3D%3D
Testing
Test Case: TC922
Tester:


OSX support added

Hi,
Your solution seems a great alternative for vagrant rsync-auto.
Revised the script to support OSX+fswatch for monitoring file changes.
Will gladly explain all the changes made.

This looks great, did it work okay?

wow, thanks for this great PR!
I added few remarks (see above), would be great if we could get this resolved and merged!


move attributes creation to applyStyle modifier

Right now the data attributes are added directly by the modifiers. I'd like to move them to applyStyle (and  maybe rename it to updateDOM for clarity).
In this way all the DOM write operations will be in a single modifier that can be replaced with an implementation with React or any other view library.

I'll try to pick this up too if you like. Not sure if we can move the actual DOM manipulations to one place, stuff like the x-out-of-boundaries would need to stay in hide.js right? We could do something similar to what we did for #105 though, checking if the applyStyles modifier is enabled (we'd need to find a way to pass that into the hide.js).
Alternatively, we could make a util function (probably not exposed) called setAttributeIfApplyStylesEnabled (or a not terrible name) and we could pass the attributes and the options to that.
Probably over-engineered, up to you.

i would prefer a kind of "virtual DOM" like approach, the modifier adds the attribute to an "attributes" array in the data and applyStyle reads and applies them. we did the same for the custom styles

To make it clear what I'm reffering to:
https://github.com/FezVrasta/popper.js/blob/v1-dev/src/popper/modifiers/applyStyle.js#L37-L43


Shaka Player canvas drawimage() is not working on webOS

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.2.0
Please ask your question
Shaka Player canvas drawimage() is not working on webOS.
mac used Chrome 94.0, WebOS 79.0, and Samsung Browser 69.0.
In mac, draw images are good with video elements, but Chrome 79.0 and 69.0 are black screen canvas.
Do you know how to draw an element of video on canvas?

        <textarea id="user_Agent" rows="1" cols="110" readonly>user agent</textarea>

        <video class="videosample2" id="videosample2" width="500px" height="300px" type="video/mp4" controls webkit-playsinline></video>
        <button id="button1" onclick="btn_click();" style="background: slategray; height: 50px; width: 200px;">버튼</button>

Clicks: 0

        <canvas id="main-canvas" width="500px" height="300px" style="float:left; border: 3px solid blue;"></canvas>

var video = document.getElementById("videosample2");
var canvas = document.getElementById("main-canvas"), context = canvas.getContext("2d");
const user_Agent = document.getElementById('user_Agent');

window.onload = function(){
  user_Agent.innerHTML = navigator.userAgent;
}

var clicks = 0;

function btn_click() {
  clicks += 1;
  document.getElementById("clicks").innerHTML = clicks;
  video.play();
  video.addEventListener('play', function() {
    (function loop2() {
        context.drawImage(video, 0, 0, canvas.offsetWidth, canvas.offsetHeight);
        window.requestAnimationFrame(loop2);
    })();
  }, 0);
}

Sounds like an issue with WebOS and Canvas rather than the player.  We don't do anything with Canvas, and anything you do to copy video to a canvas should be the same whether you're using Shaka and DASH or a plain mp4 in a <video> element with no player at all.
The only thing I can think of that may cause issues is DRM.  Are you trying to copy the frames of encrypted content?  If so, some browsers or DRM systems may have restrictions on that.


Enable TravisCI & Better Docker Builds

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@471117e). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage        ?   20.15%
=======================================
  Files           ?       15
  Lines           ?      794
  Branches        ?        0
=======================================
  Hits            ?      160
  Misses          ?      612
  Partials        ?       22

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 471117e...fbb374f. Read the comment docs.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@471117e). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage        ?   20.15%
=======================================
  Files           ?       15
  Lines           ?      794
  Branches        ?        0
=======================================
  Hits            ?      160
  Misses          ?      612
  Partials        ?       22

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 471117e...fbb374f. Read the comment docs.


support to laravel 5.2

Hi, dont work with laravel 5.2 =), dont install and update composer, showing error
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: remove laravel/framework v5.2.5
    - Conclusion: don't install laravel/framework v5.2.5
    - Conclusion: don't install laravel/framework v5.2.4
    - Conclusion: don't install laravel/framework v5.2.3
    - Conclusion: don't install laravel/framework v5.2.2
    - Conclusion: don't install laravel/framework v5.2.1
    - rcrowe/twigbridge v0.8.0 requires illuminate/view 5.0.*|5.1.* -> satisfiable by illuminate/view[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.6, v5.1.8].
    - rcrowe/twigbridge v0.8.1 requires illuminate/view 5.0.*|5.1.* -> satisfiable by illuminate/view[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.6, v5.1.8].
    - rcrowe/twigbridge v0.8.2 requires illuminate/view 5.0.*|5.1.* -> satisfiable by illuminate/view[v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.6, v5.1.8].
    - don't install illuminate/view v5.0.0|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.0.22|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.0.25|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.0.26|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.0.28|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.0.33|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.0.4|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.1.1|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.1.13|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.1.16|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.1.2|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.1.20|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.1.22|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.1.25|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.1.6|don't install laravel/framework v5.2.0
    - don't install illuminate/view v5.1.8|don't install laravel/framework v5.2.0
    - Installation request for laravel/framework 5.2.* -> satisfiable by laravel/framework[v5.2.0, v5.2.1, v5.2.2, v5.2.3, v5.2.4, v5.2.5].
    - Installation request for rcrowe/twigbridge 0.8.x -> satisfiable by rcrowe/twigbridge[v0.8.0, v0.8.1, v0.8.2].

Try 0.9

thx)


feat: first pass at adding a summary subcommand

to print out basic stats about a git repository

Codecov Report

Merging #237 (4135316) into main (7e64aa8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #237   +/-   ##
=======================================
  Coverage   70.52%   70.52%
=======================================
  Files          51       51
  Lines        2877     2877
=======================================
  Hits         2029     2029
  Misses        536      536
  Partials      312      312

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7e64aa8...4135316. Read the comment docs.


Consider use of prebuilt registry libraries

🚀 Feature Request
Fairseq should consider using prebuilt function/class registries internally
Motivation
The current iteration of fairseq's internal architecture registry is slightly confusing. It ties itself very tightly to argparse, has no mechanism for building with non-argparse.Namespace arguments, and encourages a lot of black magic with default arguments in the argument parser. It would be better if the registry logic could be punted to some separate library which is well-tested and more idiomatic.
Pitch
Ideally the general architecture wouldn't change: there would be registries for FairseqTask, Fairseq...Model, FairseqOptimizer, FairseqCriterion, etc. What would likely change is that there would be no bifurcation of registration and instantiation of these classes. For example, under the paradigm of class-registry, you'd have something like...
from class_registry import ClassRegistry

optimizer_registry = ClassRegistry()

@optimizer_registry.register("adafactor")
class FairseqAdafactor(FairseqOptimizer):
    def __init__(self, lr=1e-4, adafactor_eps=1e-3, clip_threshold=0.0, ...):
        ...

# Pass the non-defaults when looking up the class
opt = optimizer_registry.get("adafactor", lr=1e-5, clip_threshold=0.001)

This is highly desirable because it decouples completely from argument parsing, makes code more compositional by allowing setup_task to work strictly in terms of registries, and it requires less maintenance of code that isn't strictly "business logic" as far as fairseq is concerned.
Alternatives
There are two main options: leave the code as-is or explore registry libraries. The primary registry libraries that I know are class-registry and catalogue. There may be others, but I assume they'll all be approximately equivalent.
Additional Context
One question to explore before diving deeper is how this might interact with the --user-dir flag: can a user just import the appropriate registry from fairseq and register their own architectures?
Another question is about how to communicate defaults to a user -- in the above formulation, defaults get handled by the class rather than by the user-facing command-line arg mechanism, so how can those defaults percolate back to a user? Are there global defaults? Do defaults get presented to a user currently? Is it a matter of documentation? Will we need black magic? ⚡

Motivation makes sense, especially as you’re exploring decoupling from argparse.
I’d be reluctant to take an external dependency for something like this, since registry code is fairly small and easy to implement ourselves, once we decide what to implement :)
Regarding --user-dir, yes that’s exactly how it works. People can register their own tasks, models, etc. without needing direct access to the fairseq source (e.g., if using a pip installation). When a component is registered it injects the appropriate command-line arguments into fairseq-train so you can use your custom task/whatever. There are some docs about it at the bottom of this page: https://fairseq.readthedocs.io/en/latest/overview.html

Yep. 😄 I guess the question I was asking was more if we were to move the route of some external dependency - I am not sure how they would work with --user-dir.
I can play with some exploratory refactoring of the registry mechanism now to move to something closer to what's described above and we can discuss pros/cons as the code evolves. Does that seem reasonable?

I think some of this will be solved by Hydra. Also take a look at how tensor2tensor does it, since I believe they support a similar registry but without injection of command line options.

I've been reading about hydra and it seems very promising, but likely will require #1672 first because it has a similar mechanism to constructor argument population as described above.

Hi Folks, happy to see Hydra is on the radar of fairseq.
@myleott, we should meet and chat about what the integration can look like.
There are several non-obvious features of Hydra that are specifically designed with frameworks like fairseq in mind.

There's some context in another issue that basically equates to: hydra is going to allow for programatic hyperparameter sweeps -- currently I don't think there's a mechanism for this outside of using unix. 😆 Very excited for this!

See here.

I landed the Ax sweeper plugin to master today.
see this (docs in website needs some work)


Address already in use Error: failed to start Meshery

Current Behavior

I tried the following command:
curl -L https://meshery.io/install | PLATFORM=kubernetes bash -
Getting error:
Error response from daemon: driver failed programming external connectivity on endpoint meshery-meshery-nginx-sm-1 (4cf1b4b02f6e66ec2d545825370d33
7140f8c4057da39ff9d751ec0a637c4bf7): Error starting userland proxy: listen tcp4 <IP_ADDRESS>:10010: bind: address already in use
Error: failed to start Meshery
See https://docs.meshery.io/reference/mesheryctl/system for usage details
: failed to run meshery server
See https://docs.meshery.io/reference/mesheryctl/system for usage details
: exit status 1

How can we change the binding address?
Expected Behavior

Should start the server.
Environment

Host OS: Linux
Platform: Kubernetes
Meshery Server Version: stable-v
Meshery Client Version: stable-v

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Hi @prasadpatil25 how can I reproduce the same?


St/sdk 1090

This PR requires Sparkz as in Sparkz project PR st/SDK_987 (https://github.com/HorizenOfficial/Sparkz/pull/52) to be built

There are some compilation error in the CI, other than that LGTM!

@davehorizen Done


[Enhancement] Request version 1.20

CFM does not have a 1.20 version available for download.
Much appreciated.

There won't be a 1.20 veersion, use 1.20.1 instead


Add FlyBase anatomy terms in GOREL for annotating extensions in P2GO

[x] part_of FBbt:10000000 anatomical entity

[x] part_of FBdv:00007012 life stage

[x] part_of FBbt:00007002 cell

[x] occurs_in FBbt:10000000 anatomical entity

[x] occurs_in FBbt:00007002 cell

[x] happens_during FBdv:00007012 life stage

[x] existence_overlaps FBdv:00007012 life stage

[x] exists_during FBdv:00007012 life stage

[x] existence_starts_and_ends_during FBdv:00007012 life stage

[x] has_start_location FBbt:00007002 cell

[x] has_start_location FBbt:10000000 anatomical entity

[x] results_in_determination_of FBbt:00007002 cell

[x] results_in_commitment_to FBbt:00007002 cell

[x] results_in_movement_of FBbt:00007002 cell

[x] results_in_specification_of FBbt:00007002 cell

[x] results_in_morphogenesis_of FBbt:00007002 cell

[x] results_in_maturation_of FBbt:00007002 cell

[x] results_in_division_of FBbt:00007002 cell

[x] results_in_formation_of FBbt:00007002 cell

[x] results_in_development_of FBbt:00007002 cell

[x] results_in_development_of FBbt:10000000 anatomical entity

[x] results_in_morphogenesis_of FBbt:10000000 anatomical entity

[x] results_in_maturation_of FBbt:10000000 anatomical entity

[x] results_in_formation_of FBbt:10000000 anatomical entity

[x] results_in_acquisition_of_features_of FBbt:00007002 cell

[x] acts_on_population_of FBbt:00007002 cell

@hattrill @alexsign

@balhoff can you regenerate GORELs in the next release & snapshot ?
Thanks, Pascale

@pgaudet #27031.


Removes the quest modding stuff as we all know it is not coming back and is against the rules to do now. (Read description)

I think I got everything except the translated ones (I think don't take my word)
this took a good half an hour to do.
if theres more i need to remove please put it in the comments here.

Hold on the choose your platform is broken, give me a few days to finish it and if anyone could help that would be nice

i accidently broke a few things so dont pull this


[kernel 5.14] remove workaround for skb->mark scrub during veth traversal

Background:
The BPF datapath code currently contains a workaround for a kernel limitation. When traversing between a veth pair in the same netns, the skb->mark is scrubbed. So we need to use the skb->cb instead. This has been resolved in newer kernels (5.14+) and backported to older kernels, but we're still carrying the workaround.
Proposal:
Remove the workaround once we require a new-enough kernel. Until then we can implement a probe, but it's not a priority.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff70202b2d1 has been backported to Kernel 5.4.259 and 5.10.199 in October 2023.
RHEL8 still seems to be missing the patch, even in RHEL 8.10. Hoping that @tohojo might be able to help here.

Hmm, not sure I can be of much help here. You'll need a pretty compelling customer case to get anything into RHEL8 at this point...


[FIX] Removing some light grey background from Nav links and contact button.

New Mockup
Please check assets/css/global.css, design-assets folder images, and figma files for updated style guides. Any new pull request should use the updated color, spacing, and sizing variables.
No Bootstrap or jQuery
Please refrain from adding Bootstrap or jQuery to the site. These pr's will be closed. They overwrite global styles. Vanilla CSS and JS is way better now anyways 😊
New Task:

Removing this background as it's not present in the mockup.
What is the task
<Detail the problem/task>
Who is the task for?

[x] I created this task for me to complete, I will create a PR soon.
[x] I created this task for someone else to claim.
[x] I think this is a task that multiple people can do

Confirm all of the following:

[x] I have looked at all the issues currently available and this does not exist or overlap with another ticket

⚠ PLEASE ONLY SUBMIT A PR FOR THIS TASK IF THIS TASK WAS AVAILABLE FOR YOU TO CLAIM

This has already been solved in #526 .


TypeNameHandling works only when $type element is first element of JSON Object.

Source/destination types
Object with property that has multiple child types.
It has [JsonProperty(TypeNameHandling = TypeNameHandling.All)] annotation.
Source/destination JSON
Child type of C# in JSON with $type property.
Expected behavior
Newtonsoft.Json accepts $type porperty and deserializes to desired type.
Actual behavior
Newtonsoft.Json accepts $type only if it is the first property of deserialized object.
If $type property is not first, then object is treated as base class (as defined in C# class).
Steps to reproduce

Create some base and child classes. Use base as property of JsonObject.
Create new child class in JS and add $type of that child to JSON (but not on first place).
Serialize it and send to MVC controller.
Decoded child has base class type instead $type defined child.

PS, cant add actual code because NDA.

If $type is on first place it works OK. But its pain to add this in JS instead just write obj["$type"] = "Types.Child, Types"

MetadataPropertyHandling.ReadAhead?

Ok, didn't seen that. But Maybe ill try to make converter that choose the Type by Enum value of decoded object property (objects already have that enum).

It is already talked about quite clearly in the documentation  - https://www.newtonsoft.com/json/help/html/SerializationSettings.htm#TypeNameHandling

Written in doc and easy-to-spot is different things. I read this doc before posting my example but I didn't see the sentence about metadata. For example, this docs are very easy to spot that I have to know a newtype pattern. If it would be a plain text as it is I probably wouldn't see it or this docs, where note is actually a note, not a terse mentioning in the middle of the text.
Just as suggestion though. If you have people that creates such a issues then documentation is unclear even if you think the opposite.


Fix(snapshot) Fix the snapshot reverting message

https://github.com/longhorn/longhorn/issues/897
Signed-off-by: Siye Wang<EMAIL_ADDRESS>

[ ] There is no need for Cancel and OK when reverting is not allowed. Just put an OK there.
[ ] Attached Node is not shown for volume in maintenance mode.


How to return latents from MobileStyleGAN like those in StyleGAN2?

Hello @bes-dev,
How can I return latents from MobileStyleGAN just like StyleGAN2 does here as following:
if return_latents:
    return image, latent

How can I get the latent variable similar to this in StyleGAN2? Looks like there's some manipulation involved.

@RahulBhalley https://github.com/bes-dev/MobileStyleGAN.pytorch/blob/a9776ff8f05a868b2d3b637bda14eca4c074d2a3/core/distiller.py#L184

Hmm, I used these but the reconstruction results of ReStyle encoder started to become same for any face at around 12k iterations.
Could it have to do anything with the internal manipulation of latent before returning them as in StyleGAN2? Or I've misunderstood something?

No problem, I solved the problem. 🙂


AFL stuck "spinning up fork server"

Chapter 7, the snapshot is taken successfully but when opening it in AFL I'm timing out despite me increasing the limits.  Perhaps I'm missing a step?
Issue is discussed here, https://github.com/FirmWire/FirmWire/issues/26 & https://github.com/FirmWire/FirmWire/pull/28

Fixed by passing in
--restore-snapshop gsm_fuzz_base
to AFL.
Consider adding it to the final version of the book.

Thanks for the errata @icryo, what I wonder is how you get a copy of the book before the release, give that we don't even have it yet.


Bug issue2928: read sql table fails when reading empty table

[x] Tests added / passed
[x] Passes flake8 dask
[x] Fully documented, including docs/source/changelog.rst for all changes
and one of the docs/source/*-api.rst files for new API

This looks good to me.  Merging on passed tests.

Merged.  Thanks @avlahop !


Add toleration to helm chart with terraform

v10.0.1
Using terraform and following the docs I have been trying to add tolerations to Karpenter's helm chart.
This case isn't covered in the docs and I'm getting hard time implementing it.
From main.tf I am using set to inject vars to the chart values:
resource "helm_release" "karpenter" {
  name       = var.name
  repository = var.helm_repo
  chart      = var.helm_chart
  version    = var.helm_chart_version

  namespace        = var.name
  create_namespace = true
  timeout          = 300

  set {
    name  = "serviceAccount.annotations.eks\\.amazonaws\\.com/role-arn"
    value = aws_iam_role.main.arn
  }
  set {
    name  = "clusterName"
    value = var.cluster_id
  }
  set {
    name  = "clusterEndpoint"
    value = data.aws_eks_cluster.cluster.endpoint
  }
  set {
    name  = "aws.defaultInstanceProfile"
    value = "${var.default_instance_profile}"
  }
  set {
    name  = "webhook.hostNetwork"
    value = var.host_network
  .
  .
  .
  .
  .
  set {
    name  = "tolerations"
    value = var.tolerations
}

From file variables.tf I call tolerations var:
variable "tolerations" {
  type        = any
  description = "tolerations for karpenter"
  default = <???>
}

The default value should be the value of tolerations.
I tried many ways none of them worked.
My goal is that eventually the Helm chart's values file will look something like:
.
.
.
tolerations:
  - key: "tool"
    value: "karpenter"
.
.
.

Thanks!

Hi guys please advise I am pretty stuck right now. Thanks!

I tried many ways none of them worked.

In what way didn't it work?

@Izvi-digibank another simpler option is to use values and provide the tolerations key directly inside of a values.yaml file like:
values           = [templatefile("${path.module}/values.yaml", {})]

values.yaml:
tolerations:
  - key: tool
    operator: Exists

This will be merged with all the other set values by helm.

@Izvi-digibank you can try to wrap terraform with yaml
values = [yamlencode({
    clusterName      = module.eks.cluster_id
    clusterEndpoint = module.eks.cluster_endpoint
    serviceAccount = {
      annotations     = {
        "eks.amazonaws.com/role-arn" = module.iam_assumable_role_karpenter.iam_role_arn
      }
    }
    aws = {
      defaultInstanceProfile = aws_iam_instance_profile.karpenter.name
    }
    tolerations = [
      {
              key          = "tool"
              operator = "Exists"
              effect      = "NoExecute"
        },
        {
              key          = "tool"
              operator = "Equal"
              value       = "karpenter"
              effect      = "NoExecute"
        },
    ]
  })]

  set {
    name  = "tolerations[0].key"
    value = "dedicated"
  }

  set {
    name  = "tolerations[0].value"
    value = "karpenter"
  }

  set {
    name  = "tolerations[0].operator"
    value = "Equal"
  }

  set {
    name  = "tolerations[0].effect"
    value = "NoSchedule"
  }

No longer maintainer getting started for Terraform, please refer to https://github.com/terraform-aws-modules/terraform-aws-eks

@Izvi-digibank you can try to wrap terraform with yaml
values = [yamlencode({
    clusterName      = module.eks.cluster_id
    clusterEndpoint = module.eks.cluster_endpoint
    serviceAccount = {
      annotations     = {
        "eks.amazonaws.com/role-arn" = module.iam_assumable_role_karpenter.iam_role_arn
      }
    }
    aws = {
      defaultInstanceProfile = aws_iam_instance_profile.karpenter.name
    }
    tolerations = [
      {
              key          = "tool"
              operator = "Exists"
              effect      = "NoExecute"
        },
        {
              key          = "tool"
              operator = "Equal"
              value       = "karpenter"
              effect      = "NoExecute"
        },
    ]
  })]

Switch module.eks.cluster_id to module.eks.cluster_name


Cleanup Dockerfile

Thank you for making this tool available to everyone. This is just a tiny thing, the Dockerfile can be simplified by removing two packages that are installed anyways. The apt package texlive-full already includes texlive-latex-base and texlive-fonts-extra, so they don't have to installed separately.

If you want you can remove this line as well, since the entire Python3 directory is deleted later.
https://github.com/3b1b/manim/blob/8d66cfb75b2781e74f1de29d8e331f349aef03a8/Dockerfile#L21

@eulertour Good idea. I've also consolidated the apt install calls into one single one and sprinkled some comments into there. How does it look?

I think it's best not to consolidate the apt install commands because it obscures the logical flow of the installation (see here). For example, the dockerfile won't work after 4ba9f6b5a31188c53cf51da618de351863a43348 is applied because texlive is installed before the time zone is setup (you'll get this problem).

Welp, how's this?

The way it is now, requirements.txt will be left on the image since it gets copied in after the python 3 directory is deleted. Additionally, the time zone setup is still separated from the texlive install, which makes it unclear why it is necessary (although it was admittedly pretty unclear before as well).
I'd recommend moving the time zone setup to just before the texlive install, mentioning in the comment that the time zone setup is required by texlive, and getting rid of requirements.txt somehow, either by deleting it with the python 3 directory or adding another rm for it afterward.

Can you confirm that it now works as intended and that it makes sense?

This looks fine. The comment says textlive instead of texlive, but that's a nitpick.

It's best to have all the apt installing that van be done at once all be done in one RUN command.  That way it only creates one layer, saving the end user a bunch of disk space.
To make the list of dependencies clear, use backslashes:
RUN apt install -y \
  build-essential \
  something-else \
  yet-another-package

@Asday You're completely right, this dockerfile is ridiculous.

The good news is that the dockerfile is now much simpler. The bad news is that the image is actually larger now, up to 5.72 GB from 4.28 GB.


Support for Emoji 12.1

While this works fine, the multi-skin-tone emoji are not yet supported in colons-format. I need to define exactly what that syntax should look like, and then implement it.

Coverage decreased (-2.9%) to 86.643% when pulling 3f4583fd79a284d028c9091e10411fddf50d0b9d on v12 into 202a66471f507709ad658685283ddcac01d0c130 on master.

Replacing this work with #143, jumping us to the latest data version


Trail Data: Change trails to be based on Trail System instead of Trail System + Color

This was completed through updating the data on trailsyserver


Update SyncToDevice docs

Remove the limitation where we mentioned that files are not supported.

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


DDCE-3903 | Updates needed for Java 11.

Added .truncatedTo(ChronoUnit.MILLIS) to LocalDateTime.now to solve problems with precision, as mentioned in migration guide.
Run integration, acceptance, performance tests locally with J11. All passed.

test this please


[Breaking change]: Document MSBuild deprecation of custom derived BuildEventArgs

Description
The document should be very visibly linked from https://learn.microsoft.com/en-us/dotnet/api/microsoft.build.framework.custombuildeventargs (or it should be made part of that document).
https://github.com/dotnet/msbuild/pull/8917 introduces deprecation of custom derived build events of any subclass of BuildEventArgs by any build extensibility (mainly custom tasks).
From net8 - if any such event is used when building with NET8 version of msbuild (means from commandline) - a build error will be issued:
Usage of unsecure BinaryFormatter during serialization of custom event type 'MyCustomBuildEventArgs'. This will be deprecated soon. Please use Extended*EventArgs instead. More info: https://aka.ms/msbuild/eventargs

The behavior can be opted out via explicitly setting env. var MSBUILDCUSTOMBUILDEVENTWARNING to something else then 1.
The warning might be given a MSB code - then another way of suppressing would be usage of MSBuildWarningsAsMessages
When building on Full Framework version of MSBuild (Visual Studio case), then this behavior is not on by default. It'll be introduced in VS17.8 and will be explicit opt-in by setting MSBUILDCUSTOMBUILDEVENTWARNING to 1. When opted in, it will introduce a build warning (as opposed to build error in NET8+) with the same wording as above.
Version
.NET 8 RC 1
Previous behavior
It was allowed to derive from any subclass of BuildEventArgs and use those freely in custom Tasks and other build extensibility points
New behavior
A build error or a build warning will be issued
| Building your MSBuild extensibility | Build leveraging the MSBuild extensibility with custom   build events (regardless how that one was built) | Previous scenario with MSBUILDCUSTOMBUILDEVENTWARNING=1   in environment | Previous scenario with MSBUILDCUSTOMBUILDEVENTWARNING=0   in environment
-- | -- | -- | -- | --
.NET 8+ | No change | Build error,    Custom event dropped | Build error,    Custom event dropped | Build crashes    (unless EnableUnsafeBinaryFormatterSerialization explicitly enabled in MSBuild   runtimeconfig)
.NET Framework 17.8+ | No change | No change | Build warning,    Custom event transferred | No change
Type of breaking change

[ ] Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load or execute, and if so, require recompilation.
[ ] Source incompatible: When recompiled using the new SDK or component or to target the new runtime, existing source code may require source changes to compile successfully.
[ ] Behavioral change: Existing binaries may behave differently at run time.

Reason for change
Unsecure BinaryFormatter is going to be deprected (https://aka.ms/binaryformatter). From NET8 - usages of BinaryFormatter will lead to runtime errors (unless user explicitly opts-in with EnableUnsafeBinaryFormatterSerialization) - and custom derived build events rely on BinaryFormatter - so such a build would fail anyways. Current build error/warning gives more grace information.
The runtime errors do not apply to Full Framework yet - hence the build warning is opt-in for Full Framework. However this will change very soon (current deadline for BinaryFormatter removal is 2023-12-31 - https://liquid.microsoft.com/Web/Object/Read/MS.Security/Requirements/Microsoft.Security.SystemsADM.10010#Zguide), so opting-in and refactoring is strongly recommended.
Recommended action
Proper approach is to move to any of the offered alternative build-in events for extensibility (code links will be provided once PR is merged. Those types should be probably documented with generated documentations similarly as CustomBuildEventArgs as part of this documenting effort):

ExtendedCustomBuildEventArgs
ExtendedBuildErrorEventArgs
ExtendedBuildMessageEventArgs
ExtendedBuildWarningEventArgs

Alternatively users can temporarily disable the check by explicitly setting env. var MSBUILDCUSTOMBUILDEVENTWARNING to something else then 1.
The warning might be given a MSB code - then another way of suppressing would be usage of MSBuildWarningsAsMessages
Feature area
Other (please put exact area in description textbox)
Affected APIs
https://learn.microsoft.com/en-us/dotnet/api/microsoft.build.framework.custombuildeventargs

Tagging @ghogen to update the API docs as necessary.


Submit PR to json-schema.org updating our description with draft-2019-09 support

As far as I can tell, we're the first go implementation of the new spec, we should PR that info into json-schema.org

https://github.com/json-schema-org/json-schema-org.github.io/blob/master/_data/validator-libraries-modern.yml


Zephyr layout coords fix

A bug in zephyr_layout in the file dwave-networkx/drawing/zephyr_layout.py is fixed so that if scale = scale, all positions fit within [0, scale] on the x-axis and [-scale, 0] on the y-axis.
A couple of tests are added to tests/test_zephyr_layout.py that would fail before fixing the bug. These test the range of x value and y-value produced by zephyr_layout for the default scale=1 and scale=10.
Similarly, for pegasus_layout and test_pegasus_layout.py

@randomir - can you assign myself and @AndyZzzZzzZzz as reviewers?

@randomir Is this ready to be merged?

You're correct that the plots don't look different before and after this PR. However the document says scale=1 gives values in [0,1], and this is a feature that was relied on in the layout algorithm (in dnx_layout in layout.py) and the bug in this code caused the layout algorithm to give poor results.

@randomir
Could you advise on numpy import?


Add oauth2 as valid auth method for creating and updating users

Add oauth2 as valid auth method for creating and updating users

Great spot, I intended it to allow for not setting a password at all, as opposed to setting an empty string. I must have dropped the line when separating the changes into proper feature branches. I added it back now.


Preparations for the upcoming 3.13 release and its upload to Debian.

As a pragmatic choice, I only develop and test against released versions of Python, in particular those where Circle CI has released images I can use for testing.
I'm pretty allergic to linux distro packagers: if you're going to make a submission like this, I expect a PR with the fixes not a bug report, otherwise you're just wasting my time.


'Update code model for cpptools Error' after disable cpptools's IntelliSense

Brief Issue Summary
After update cpptools to 1.7.0(IntelliSense has been disable), Update code model for cpptools Error log will show when configure.
Debug Log
[main] Safe constructing new CMakeTools instance
[variant] Constructing VariantManager
[main] Constructing new CMakeTools instance
[main] Starting CMakeTools second-phase init
[variant] Loaded new set of variants
[main] CMakeTools instance initialization complete.
[kit] Reading kits file xxxxxx\cmake-tools-kits.json
[kit] Successfully loaded 8 kits from xxxxxx\cmake-tools-kits.json
[kit] Not reading non-existent kits file: xxxxxx\cmake-kits.json
[main] Injecting new Kit into CMake driver
[extension] Using cache to configure workspace on open file:///xxxxxx
[main] Starting new CMake driver
[main] Starting CMake driver
[main] Using generator from user configuration: Ninja
[cmakefileapi-driver] Creating instance of CMakeFileApiDriver
[driver] Initializating base driver using kit
[driver] CMakeDriver Kit set to Visual Studio Community 2019 Release - amd64
[kit] OK running xxxxxx\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat x64, env vars:xxxxxx
[driver] Run _refreshExpansions
[driver] Run _refreshExpansions cb
[cache] Reading CMake cache file xxxxxx/build/Debug/CMakeCache.txt
[cache] Parsing CMake cache string
[cache] Reading CMake cache file xxxxxx/CMakeCache.txt
[cache] Parsing CMake cache string
[cmakefileapi-parser] Read reply folder: xxxxxx\build\Debug\.cmake\api\v1\reply
[cmakefileapi-parser] Found index files: ["cache-v2-d94fb1ac8145deee2684.json","codemodel-v2-19b47e44f6078814bb45.json","index-2021-09-18T11-56-26-0823.json","target-Utils-Debug-ae79c13cc81fa1e0ac66.json","target-UtilsTest-Debug-025563727d3d9d72a9cc.json"]
[cmakefileapi-driver] This version of CMake does not support the "toolchains" object kind. Compiler paths will be determined by reading CMakeCache.txt.
[driver] Setting new variant Debug
[driver] Run _refreshExpansions
[driver] Run _refreshExpansions cb
[driver] Run _refreshExpansions
[driver] Run _refreshExpansions cb
[driver] Use cached configuration
[driver] Runnnig pre-configure checks and steps
[driver] Run _refreshExpansions
[driver] Run _refreshExpansions cb
[cmakefileapi-parser] Read reply folder: xxxxxx\build\Debug\.cmake\api\v1\reply
[cmakefileapi-parser] Found index files: ["cache-v2-d94fb1ac8145deee2684.json","codemodel-v2-19b47e44f6078814bb45.json","index-2021-09-18T11-56-26-0823.json","target-Utils-Debug-ae79c13cc81fa1e0ac66.json","target-UtilsTest-Debug-025563727d3d9d72a9cc.json"]
[cache] Reading CMake cache file xxxxxx/build/Debug/CMakeCache.txt
[cache] Parsing CMake cache string
[cache] Reading CMake cache file xxxxxx/build/Debug/CMakeCache.txt
[cache] Parsing CMake cache string
[rollbar] Unhandled exception: Unhandled Promise rejection: Update code model for cpptools Error: Do not activate the extension when IntelliSense is disabled. {}
[rollbar] Unhandled exception: Unhandled Promise rejection: Update code model for cpptools Error: Do not activate the extension when IntelliSense is disabled. {}
[cache] Reading CMake cache file xxxxxx/build/Debug/CMakeCache.txt
[cache] Parsing CMake cache string
[rollbar] Unhandled exception: Unhandled Promise rejection: Update code model for cpptools Error: Do not activate the extension when IntelliSense is disabled. {}

I believe this is a bug for cpptools.  Configuration Providers should not be required to check when IntelliSense is disabled or not.  cpptools should just silently ignore the provider callbacks.


Testing AerTV Compatability

Great, however it sense there is conflics, I think because I made changes since you have made changes but I could add the new AerTV function in and give the user a username and password entry in the settings

o.o o shit just realized something 1 sec

go on

It had something in it that shouldnt be in it at all lol


Using Generics in an interface, get error TS2322: Type 'string' is not assignable to type 'T'.

I get the above error using react and mobx in the code below.   It may be related to #10589, but could also be a separate cause.  The code below compiles successfully with version 1.8.10.
TypeScript Version:  2.0.2 & 2.1.0-dev.20160907
Code
// A *self-contained* demonstration of the problem follows...

//input.tsx
interface Props<T> extends React.HTMLProps<Input<T>>
{
    val: IObservableValue<T>;
    onChange?: React.FormEventHandler;
}

interface State
{
}

@observer
export class Input<T> extends React.Component<Props<T>, State> {

    private onChange(e: any): void
    {
        // ....
    }

    render(): JSX.Element {
        // ....
    }
}

// testComponent.tsx
import * as React from "react";
import {observable} from "mobx";
import {observer} from "mobx-react";

import {Input} from "./input";

interface IProps {
}

interface IState {
}

@observer
export class TestComponent extends React.Component<IProps, IState> {
    private _data = observable("");

    constructor(props: IProps, context: any) {
        super(props, context);
    }

    render(): JSX.Element {
        return (

                Enter Data: <Input val={this._data} type="text"/>
       // <-- Receive TS2322 error on this line when trying to set val={this._data}

        );
    }
}

**Expected behavior:**
To Compile

**Actual behavior:**
Compile Error TS2322

where is the definition of IObservableValue coming from?

It's from MobX type definition:
interface IObservableValue<T> {
    get(): T;
    set(value: T): void;
    intercept(handler: IInterceptor<IValueWillChange<T>>): Lambda;
    observe(listener: (newValue: T, oldValue: T) => void, fireImmediately?: boolean): Lambda;
}

i can not get this to repro. can you provide a self contained sample i could try?

I created a sample project that repros the issue.  MobX not required, only using react.  For some reason it wouldn't let me attach the zip to this issue, so I uploaded it here:
https://dl.dropboxusercontent.com/u/29165199/Test.zip
After extracting the files simply run "npm install" to set up.
Then to build with TypeScript 1.8.10 run:  "npm run build-1.8"
Then to build with TypeScript rc (currently 2.0.2) run: "npm run build-rc"
The 1.8.10 build compiles fine, the rc (2.0.2 ) build fails with TS2322.

Just wondering if you had a chance to try and pull down the sample project zip file and if you were able to reproduce the issue?
Let me know if you have any other questions.  Thanks.

@yak77 sorry for the delay, looking now

This is just a duplicate of #6395 -- it's currently not possible to use a generic class as a JSX element class. A workaround is
  render(): JSX.Element
  {
    // Might want to have a generic type alias for this
    const StringInput: new() => Input<string> = Input;
    return (

          <StringInput val={this._data}/>

    );
  }

@RyanCavanaugh Thanks for looking into this and posting the workaround.
Is this a regression in the 2.0 compiler?  Because the code I posted compiles with 1.8.10.


Is there a way to add a marker for every 1 km/ mile?

I would like to use Leafletjs and your plugin for our running club, and I have both leafletjs and your plugin running - I would like however to be able to display a numbered marker for every 1 km along the track.
Is this possible with Leafletjs and (or) your plugin?

It's not possible out of the box right now, but I'd be interested in having such a feature too if you feel like implementing it. The easiest way would be, as you go through the datapoints, to place a marker on each point after the accumulated distance so far goes over the next km/mi.

This seems relevant https://github.com/adoroszlai/leaflet-distance-markers

That was the solution I ended up with.


Get Handel training step

Might make more sense here to get the handle to the previous training run step in order to compare metrics stored.

Looks like I can't create a comment there, but please review line 33, it needs to be changed as well.

Side comment: notice this will not be the run corresponding to the train step, as you said, but the parent run of both training & evaluation steps (the run corresponding to the pipeline itself). When training happens, metrics are logged both in the child "train" run and in the parent "pipeline" run (here).


Cell navigation is not working properly, if hidden column is available

Hi,
While navigating to cell using arrow keys, cell selection is getting set for the hidden columns also. Kindly set cell selection only for the visible columns.

How would you approach this, something like detect when you're in a hidden cell and repeat the last keyboard action (such as arrow-right)?

Thank you so much for your response. As you said while navigation we need to identify the previous/next visible elements. We can use the jQuery methods to get the previous/next visible elements. I have modified few changes in the “keyDownControls” method to make it work. Please check attached screen shot. We need to do similar changes for Home and End key also.

Thank you so much for your response. As you said while navigation we need to identify previous/next visible elements. We can use the jQuery methods to get the previous/next visible elements. I have modified few changes in the “keyDownControls” method to make it work. Please check attached screen shot. We need to do similar changes for Home and End key also.

Thanks for adjusting the code, could you provide a text version as an attachment?  (I'd like to try it out)

Could you kindly send a pull request, I am happy to merge it to the master.

Thank you. I have attached the modified jquery.jexcel.js file. The changes are done in the keyDownControls method.
jquery.jexcel.zip


Define a function that steps and triggers all callbacks

We should define a function that calls all of the callbacks so that we can run step!(integrator) and call_all_callbacks!(integrator), so that we can pre-compile all (or most) code paths  ahead of time for profiling.
One wrinkle in this is that some functions are called depending on the data. For example, saturation adjustment (iterations using RootSolvers) is only called if the specific humidity is above some threshold. Aside from developing a fuzzer, we probably can't guarantee that we'll compile all functions ahead of time when profiling.

This wasn’t actually closed by #1850, but it was a step to fixing.


Update Gradle to 7.5.1

Signed-off-by: Andriy Redko<EMAIL_ADDRESS>Description
Update Gradle to 7.5.1
Issues Resolved
N/A
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #4211 (d3d7473) into main (5f2e66b) will decrease coverage by 0.21%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #4211      +/-   ##
============================================
- Coverage     70.78%   70.56%   -0.22%
+ Complexity    57218    57119      -99
============================================
  Files          4605     4605
  Lines        274695   274695
  Branches      40228    40228
============================================
- Hits         194441   193844     -597
- Misses        63955    64534     +579
- Partials      16299    16317      +18

Impacted Files
Coverage Δ

...adonly/AddIndexBlockClusterStateUpdateRequest.java
0.00% <0.00%> (-75.00%)
:arrow_down:

...readonly/TransportVerifyShardIndexBlockAction.java
9.75% <0.00%> (-73.18%)
:arrow_down:

...n/admin/indices/readonly/AddIndexBlockRequest.java
17.85% <0.00%> (-53.58%)
:arrow_down:

...ava/org/opensearch/action/NoSuchNodeException.java
0.00% <0.00%> (-50.00%)
:arrow_down:

...opensearch/persistent/PersistentTasksExecutor.java
22.22% <0.00%> (-44.45%)
:arrow_down:

...adcast/BroadcastShardOperationFailedException.java
55.55% <0.00%> (-44.45%)
:arrow_down:

...indices/readonly/TransportAddIndexBlockAction.java
20.68% <0.00%> (-41.38%)
:arrow_down:

...h/action/ingest/SimulateDocumentVerboseResult.java
60.71% <0.00%> (-39.29%)
:arrow_down:

...opensearch/index/reindex/BulkByScrollResponse.java
48.38% <0.00%> (-38.71%)
:arrow_down:

...regations/metrics/AbstractHyperLogLogPlusPlus.java
51.72% <0.00%> (-37.94%)
:arrow_down:

... and 470 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Unity 2022 LTS

Upgrade to 2022 LTS (again).
Noting I had to change the tracking origin from Floor to Unspecified in the main scene, as it wants to set this itself and you end up in the floor if you don't. This may break other platforms though, so we'll need a good test. This was compared to the official VR template that also seemed to have this "bug".
Test Platforms:

[x] Quest 1
[x] Quest 2
[x] PCVR
[x] Oculus PCVR
[x] Pico
[x] Monoscopic Windows
[x] Monoscopic Mac
[ ] Monoscopic Linux
[x] Zapbox

Yes and yes, that color space thing has been pending forever now! The other was a half hearted attempt to fix the input sensitivity, but I'm going to need to dive deeper.

Upgrade to 2022 LTS (again). Noting I had to change the tracking origin from Floor to Unspecified in the main scene, as it wants to set this itself and you end up in the floor if you don't. This may break other platforms though, so we'll need a good test. This was compared to the official VR template that also seemed to have this "bug".

How does this affect the "locked to world" mode we use with passthrough?

It doesn't, just the runtime picks if its device or floor instead of us setting directly, or in quest's case overrides to stage.

First results on Q1 seem reasonable. No major improvements or degradations seen, but a few small observations:

Language works correctly on Q1 (see the discord bug where it didn't before)!
The initial splash screen background changed from black to a sort of pale dark brownish color.

I couldn't get the profiling tool to work properly (see discord again), so I'm not sure how the performance is.

This is weird. I merged this into a different branch just to test if it fixed an issue on that branch and I found I couldn't build.
The error was:

Shader error in 'TiltBrush/Standard (Specular setup)': 'vertShadowCaster': no matching 2 parameter function at line 189 (on d3d11)

Which relates to Assets/ThirdParty/UnityODS/TiltBrushStandardSpecular.shader
This is basically a copy of Unity's built-in Standard Specular, with various hooks added to support ODS rendering.
The file has never been modified (going right back to the first open source code dump) and it's drifted a long way from the current built-in Unity code. I think it's failing because of this:
    vertShadowCaster(v, opos
#ifdef UNITY_STANDARD_USE_SHADOW_OUTPUT_STRUCT
                                    ,o
#endif
#ifdef UNITY_STANDARD_USE_STEREO_SHADOW_OUTPUT_STRUCT
                                    ,os
#endif
    );

I presume neither of those compiler flags exists any more so the result is an invalid function call.
But the mystery is - how comes it builds for you @mikeskydev  ?

Here's a clue as to the way to fix it:
https://github.com/KhronosGroup/UnityGLTF/blob/99c96d9029d4ce02e5f729a5e069a44aef6faa99/Runtime/Shaders/UnityStandardShadow.cginc#L26
Still doesn't explain why it works ok for the CI build on this PR.

This commit might be in the right ballpark: https://github.com/icosa-foundation/open-brush/commit/df36787e5a01fbdd3c4f51675fa0ffc90318b911

This is weird. I merged this into a different branch just to test if it fixed an issue on that branch and I found I couldn't build.
The error was:

Shader error in 'TiltBrush/Standard (Specular setup)': 'vertShadowCaster': no matching 2 parameter function at line 189 (on d3d11)

Which relates to Assets/ThirdParty/UnityODS/TiltBrushStandardSpecular.shader
This is basically a copy of Unity's built-in Standard Specular, with various hooks added to support ODS rendering.
The file has never been modified (going right back to the first open source code dump) and it's drifted a long way from the current built-in Unity code. I think it's failing because of this:
    vertShadowCaster(v, opos
#ifdef UNITY_STANDARD_USE_SHADOW_OUTPUT_STRUCT
                                    ,o
#endif
#ifdef UNITY_STANDARD_USE_STEREO_SHADOW_OUTPUT_STRUCT
                                    ,os
#endif
    );

I presume neither of those compiler flags exists any more so the result is an invalid function call.
But the mystery is - how comes it builds for you @mikeskydev ?

I didn't notice this error in 2022, but I did when i played around with unity 6? 🤔 Not sure why it was giving only you issues - but did your borrowed code from UnityGLTF fix it?

Can anyone confirm if the development builds work for them?

I'll add a list in the first post we can tick off to check

Thanks. It's probably important on its own, but more than that, I wanted to use it for benchmarking

head offset issues in both pico and quest versions

Quest 1 and Android OpenXR builds aren't working on a Quest 3 either, when theoretically they should.

Quest 1 and Android OpenXR builds aren't working on a Quest 3 either, when theoretically they should.

This might have been Meta that broke this, theoretically the newest SDK version should fix it.

Reminder that when merging this, the existing caches should be deleted (and once it builds, open PRs should rebase/merge with it)

Followup PRs: #732 #733


Increase minimum supported version to 1.46.0

CI pipelines are failing because an indirect dependency has
increased its minimum supported Rust version, due to using if
inside const fn. Cargo currently has no way to make crate version
selections dependent on compiler version, so we are forced to raise
the minimum required version for com-rs.

Committing this to unblock CI pipelines. No code changes.


how to pass a URL to index.html

I want to call med3web page (index.html) from another webpage with a URL link; so when med3web page is onloaded, it is automatically going to load dicom files pointed by URL.
How to achieve that?

In the built main.js file, I modified init function at line 125xx to the following:
    key: "init",
    value: function() {
        if ((new c.default).checkValidBrowser() || console.log("Found non valid browser"), this._initScene2d(), !this._initScene3d()) return !1;
        var t = !0;

        this.m_options.loadUrlFile = "http://serverip/3d_dicom/data/files_1";

         return this.m_options && this.m_options.loadUrlFile
                && this.m_options.loadUrlFile.length > 1 ?
                (t = this.loadScene(this.m_options.loadUrlFile, this.m_options.loadType))
                 || (0, o.default)({
                 title: "Error load",
                 text: "Cant read scene",
                 icon: "error",
                 button: "continue"
         }) : console.log("Med3Web.init without load scene"), this._run(), t

It didn't work; the URL is not passed to loading function.

There are 2 ways to load some volume on application startup:

Load volume, placed in local application folder structure
Load volume, referenced by URL from some remote location in Web.

You need to write reference to loaded on stratup file in project/tools/config.js.
Both ways with more details:

You can place some file in ProjectFolder/app./data folder. For example, 'lungs.ktx' is already placed here to illustrate loading posibilities. In this case you need to setup config.data.onloadsrc: 'data/lungs.ktx',
Implementing this way, you can place some not-very-large files directly inside web app build and this file will be acessed locally by application. Pros: loading can be quick. Cons: Application build will contains this file inside.

You can place some files (single *.ktx file or folder with a lot of *dcm files) somewhere on your web site and Med3Web application will load this file(s) from specified URL on startup stage.
If you need to load KTX file on startup, please put your somevolume.ktx file to your location and specify URL like:
config.data.onloadsrc: 'http://yoursite.com/folder1/folder2/somevolume.ktx'

If you need to load folder with *.dcm files, you need to put all your dcm files in seperate folder (containing only these dcm files) and create special file 'file_list.txt' with just list of all files. You can create file_list.txt by running command:
dir *.dcm /w /b > file_list.txt
After that yo need to specify URL in tools/config.js like:
config.data.onloadsrc: 'http://yoursite.com/folder1/folder2/folder3',
where folder3 is final folder, contained all dcm files.
Also, you can read a lot of comments in tools/config.js : data description


Sdk v0.46.* and ibc-go v5.1.0

Closes: #347
Context and purpose of the change
This PR updates cosmos-sdk to v0.46.*.  It shouldn't be considered ready for production until the release of v0.46.7, which deprecates all prior sdk releases.
Brief Changelog

update cosmos-sdk
update ibc-go

Author's Checklist
I have...

[ ] Run and PASSED locally all GAIA integration tests
[ ] If the change is contentful, I either:

[ ] Added a new unit test OR
[ ] Added test cases to existing unit tests

[ ] OR this change is a trivial rework / code cleanup without any test coverage

If skipped any of the tests above, explain.

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] manually tested (if applicable)
[ ] confirmed the author wrote unit tests for new logic
[ ] reviewed documentation exists and is accurate

Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md?
[ ] This pull request updates existing proto field values (and require a backend and frontend migration)?
[ ] Does this pull request change existing proto field names (and require a frontend migration)?
How is the feature or change documented?

[ ] not applicable
[ ] jira ticket XXX
[ ] specification (x/<module>/spec/)
[ ] README.md
[ ] not documented

Is upgrade code also required here?

open

@hieuvubk can you fix the linting errors here please?

@hieuvubk can you fix the linting errors here please?

Yes sure, but this will change all sdk.Int to math.Int so many changes. Are you sure you want to do it?

@asalzmann lint passed

Thanks!

Also, do we need to add this upgrade handler for ibc denoms?

One more important comment, we'll have to update how we handle acks (example here)

Also, do we need to add this upgrade handler for ibc denoms?

As far as I know none of our base denoms contain slashes, so we should be ok
stuatom
stujuno
stustars
stuosmo
strd

One more important comment, we'll have to update how we handle acks (example here)

Yes I did it in below commit

Hi @sampocs @asalzmann I addressed all your upper comments, could u guys take a look again? Also thank for leaving them

Taking a look now

@asalzmann

As far as I know none of our base denoms contain slashes, so we should be ok

I think you're conflating base denom's with native denoms. Base denom's are the underlying denom after you remove the stride channel/port prefix. But just checked and doesn't look like we have any with slashes.
>>> stridedm q ibc-transfer denom-traces | grep base_denom
- base_denom: stuatom
- base_denom: uatom
- base_denom: uatom
- base_denom: ustars
- base_denom: uatom
- base_denom: uscrt
- base_denom: ujuno
- base_denom: uluna
- base_denom: uatolo
- base_denom: uxki
- base_denom: aevmos
- base_denom: uregen
- base_denom: ukuji
- base_denom: ustars
- base_denom: ujuno
- base_denom: uatom
- base_denom: uumee
- base_denom: utori
- base_denom: ucmdx
- base_denom: uscrt
- base_denom: utori
- base_denom: swth
- base_denom: ucmdx
- base_denom: stuatom
- base_denom: uatom
- base_denom: ustrd
- base_denom: stuosmo
- base_denom: ujuno
- base_denom: basecro
- base_denom: ustars
- base_denom: uosmo
- base_denom: orai
- base_denom: ucre
- base_denom: ustrd
- base_denom: aevmos

@hieuvubk I think we'll need branching logic which is not addressed in 198f5ac1b4c36e8c2dd9168dedf045cf6a05b8fe. Specifically, like so
var ack channeltypes.Acknowledgement
if err := channeltypes.SubModuleCdc.UnmarshalJSON(acknowledgement, &ack); err != nil {
   return err
}

var txMsgData sdk.TxMsgData
if err := proto.Unmarshal(ack.GetResult(), txMsgData); err != nil {
   return err
}

switch len(txMsgData.Data) {
case 0: // for SDK 0.46 and above
   for _, msgResponse := range txMsgData.MsgResponses {
      // unmarshall msgResponse and execute logic based on the response
   }
   return nil
default: // for SDK 0.45 and below
   for _, msgData := range txMsgData.Data {
      // unmarshall msgData and execute logic based on the response
   }
}

I'll do this now

Thanks for the updates Hieu! As far as the ack's I think you need to update module_ibc.go in icacallbacks/records to this:
var ack channeltypes.Acknowledgement
if err := channeltypes.SubModuleCdc.UnmarshalJSON(acknowledgement, &ack); err != nil {
   return err
}

var txMsgData sdk.TxMsgData
if err := proto.Unmarshal(ack.GetResult(), txMsgData); err != nil {
   return err
}

switch len(txMsgData.Data) {
case 0: // for SDK 0.46 and above
   for _, msgResponse := range txMsgData.MsgResponses {
      // unmarshall msgResponse and execute logic based on the response
   }
   return nil
default: // for SDK 0.45 and below
   for _, msgData := range txMsgData.Data {
      // unmarshall msgData and execute logic based on the response
   }
}

@hieuvubk I think we'll need branching logic which is not addressed in 198f5ac1b4c36e8c2dd9168dedf045cf6a05b8fe. Specifically, like so
var ack channeltypes.Acknowledgement
if err := channeltypes.SubModuleCdc.UnmarshalJSON(acknowledgement, &ack); err != nil {
   return err
}

var txMsgData sdk.TxMsgData
if err := proto.Unmarshal(ack.GetResult(), txMsgData); err != nil {
   return err
}

switch len(txMsgData.Data) {
case 0: // for SDK 0.46 and above
   for _, msgResponse := range txMsgData.MsgResponses {
      // unmarshall msgResponse and execute logic based on the response
   }
   return nil
default: // for SDK 0.45 and below
   for _, msgData := range txMsgData.Data {
      // unmarshall msgData and execute logic based on the response
   }
}

I'll do this now

Hey I addressed them in all callback files

Hey I addressed them in all callback files
I believe you need to update the OnAcknowledgementPacket in module_ibc.go - but looks like Aidan's taking care of it

And then also bumping this

In the sdk/ibc-go/evmos, I've seen them import "cosmossdk.io/math" as sdkmath so it might be good to follow their lead and keep it consistent. Also, do we need to update the protos since they have an sdk.Int annotation?

Wdyt @asalzmann and @hieuvubk  ?

https://github.com/Stride-Labs/stride/pull/349#discussion_r1063476869
@sampocs about this one, I'm not sure about your idea cause its not a test file here. appVersion should depend on msg.ConnectionId that user pass through msg

No need to update proto, I see evmos they still use github.com/cosmos/cosmos-sdk/types.Int in their proto

And then also bumping this

In the sdk/ibc-go/evmos, I've seen them import "cosmossdk.io/math" as sdkmath so it might be good to follow their lead and keep it consistent. Also, do we need to update the protos since they have an sdk.Int annotation?

Wdyt @asalzmann and @hieuvubk ?

No need to update proto, I see evmos they still use github.com/cosmos/cosmos-sdk/types.Int in their proto

renamed all

No need to update proto, I see evmos they still use github.com/cosmos/cosmos-sdk/types.Int in their proto

Sounds good. And what about cosmosmath → sdkmath?

renamed all

Awesome. Can you also update the relayer to a new commit that uses ibc-v5?

Update submodule

cd deps/relayer
git checkout 7f78a4d608329b2ae07a6512381bbadffee66be6
cd ../..
git add deps/relayer

Update .gitmodules

[submodule "deps/relayer"]
	# Commit: 7f78a4d608329b2ae07a6512381bbadffee66be6
	# Branch: andrew/client_icq
	path = deps/relayer
	url = https://github.com/cosmos/relayer.git

Update the relayer dockerfile

ENV COMMIT_HASH=7f78a4d608329b2ae07a6512381bbadffee66be6

RUN apk add --update git make gcc linux-headers libc-dev eudev-dev
RUN git clone https://github.com/cosmos/relayer.git \

Awesome. Can you also update the relayer to a new commit that uses ibc-v5?

Update submodule

cd deps/relayer
git checkout 7f78a4d608329b2ae07a6512381bbadffee66be6
cd ../..
git add deps/relayer

Update .gitmodules

[submodule "deps/relayer"]
	# Commit: 7f78a4d608329b2ae07a6512381bbadffee66be6
	# Branch: andrew/client_icq
	path = deps/relayer
	url = https://github.com/cosmos/relayer.git

Update the relayer dockerfile

ENV COMMIT_HASH=7f78a4d608329b2ae07a6512381bbadffee66be6

RUN apk add --update git make gcc linux-headers libc-dev eudev-dev
RUN git clone https://github.com/cosmos/relayer.git \

Where u get the commit hash 7f78a4d608329b2ae07a6512381bbadffee66be6 ?

Where u get the commit hash 7f78a4d608329b2ae07a6512381bbadffee66be6 ?

I'm in contact with the Strangelove team who maintains the relayer. They just pushed the v5 update and I grabbed the commit from that.
Branch: https://github.com/cosmos/relayer/tree/andrew/client_icq
Last Commit: https://github.com/cosmos/relayer/commit/7f78a4d608329b2ae07a6512381bbadffee66be6

For testing, we can add logging at each step in the Unpack function.
And then we can test the following cases:

Transfer success
Transfer failure (hard code wrong delegation address in transfer deposit records step)
ICA sucess
ICA failure (hard code wrong validator address)
ICA timeout (hard code TTL that's 1 second after current block time)

@asalzmann  What am I forgetting? I think there's another failure case - maybe from a tx that's rejected in validate basic? Maybe we send a Msg type that doesn't actually exist on the host or send a message with missing args?

The above test plan makes sense - thoughts on doing this in a separate PR? This one is getting a bit hairy

The above test plan makes sense - thoughts on doing this in a separate PR? This one is getting a bit hairy

Agreed, I don't think we should push any changes related to those tests, I think we can just do it locally. But I think we should avoid merging this to main until the integration tests pass. Maybe we get the acks working for the current v3 hosts, merge, then test a v5 host (evmos) and make relevant changes in another PR?

I think we should probably write integration tests for these, wdyt?

I think as far as the individual success/failure test cases, we should just determine the Ack packet format and then make unit tests. And then wrt integration tests, I think adding a v5 host is adequate.

@asalzmann Integration tests are working. I'm trying to test restoring the channel but looks like there's some bugs in the relayer we might have to solve first.
If the new changes look good, I think we should merge this.

LGTM


Update Blog “time-of-a-square”

Automatically generated by Netlify CMS

👷 Deploy Preview for famous-kulfi-ae21db processing.

Name
Link

🔨 Latest commit
fffee9d70683e1940082144a89991a0eaa90b52d

🔍 Latest deploy log
https://app.netlify.com/sites/famous-kulfi-ae21db/deploys/65b13063dc2e7f00088a694e


[bug] Discrepancies in SUM and MEAN query results

After a random number of iterations executing the same SUM or MEAN query, different results are returned at the lower floating point digits with v0.11 master branch.
E.g.
Using sample dataset NOAA (https://s3-us-west-1.amazonaws.com/noaa.water.database.0.9/NOAA_data.txt)
SUM value calculated with Python is: 67777.66900000008
select sum(water_level) from h2o_feet
First 4 iterations match with the pre-calculated value. 5th iteration:
ValueError: Iteration 5: Sum(water_level) = 67777.66900000024 did not match 67777.66900000008
15 digit accuracy MEAN value calculated with Python is: 4.442107025822525
select mean(water_level) from h2o_feet
First 3 iterations match with the pre-calculated value. 4th iteration:
ValueError: Iteration 4: Mean(water_level) = 4.442107025822535 did not match 4.442107025822525
We have integration test cases that we can run to reproduce the issue easily.
@jsternberg @e-dard @joelegasse thoughts?

I'll start with the short version of my thoughts: don't use floating point numbers if you need precision. Store the value as thousandths or millionths in an integer value.
The slightly longer version of my thoughts can be found here (Go playground has a limit on snippet size, or I would have shared it from there): https://gist.github.com/joelegasse/76c04cb83a2e9558b69b
I created two slices of the water_level values as they appear in the data file you provided, once as []float64 to be interpreted by the Go compiler, and another as []string to be parsed with exact, decimal precision.
unsorted   67777.66900000021
ascending  67777.66900000024
descending 67777.66900000008
exact      67777669/1000
converted: 67777.669 false

Only 130 of 15258 values were able to be exactly represented as floating point numbers

From the first three lines, where each value was interpreted as a float64, you can see that the order of operations on those values matters. The reason it matters can be seen at the bottom of the output: only 130 of the 15258 values could be represented exactly. That means that over 15000 values are potentially off by the least significant bit at several orders of magnitude below where the final sum ends up, which is important. As soon as the sum increases in order of magnitude, those least significant bits of the value with the lesser magnitude disappear, and aren't included in the sum, making those values potentially even less precise when added in to the total. This magnitude shift happens several times, compounding the error rate to the point where it becomes noticeable in the final result.
I used the word "noticeable", but the error as a percentage of the exact answer is on the order of 10^-13. Even the exact answer, which is being printed "correctly" isn't represented as a float64 exactly.
"Fixing" this so that the order becomes predictable and repeatable would involve not performing any calculations until we are sure we have the values sorted (or will be accessing them in a sorted manner). This would most likely increase query response time, all in the name of providing a less-imprecise value, which, if used to calculate the sum of the mass of every living human, would be off by less than 2 grams.
Back to the short version: I don't think this is an issue worth solving, if it can even be considered an issue at all. If precision is needed, you should use precise values.

What @joelegasse says is fully possible. We don't sort the points before doing any of the call iterators except by the window which they're in. This is currently done for efficiency. I think we should just remind people in the documentation that a floating point value comes with the normal caveats of floating point. Maybe we want to add support for a high-precision floating point to InfluxDB at some point as an extra feature for those who need the precision?

That is totally understandable and is actually a logical implication of summing the same set of floats with random order. Returning slightly different results for the same query against the same data set could be misleading though.
We could consider providing an additional "precise" version of those queries which will have more computational cost. Otherwise if almost no real use case is ever affected by this, we can just mention it as a known issue in the docs.

I don't understand how it is misleading. I think @jsternberg has the right idea in that we should just educate people that the value 0.1 can never be stored exactly as a floating point value, and that InfluxDB makes no guarantees about the order of operations for aggregate functions. All of the aggregate values calculated (other than when using math/big) in the above example are technically incorrect.
I don't think adding a more precise floating point or decimal value type will have a significant benefit, but that's a larger discussion, and not really related to aggregate functions currently returning slightly different values.

Thanks @joelegasse @jsternberg
The next best thing we can do is document this behavior of variable results in the lower digits of floats when fields are aggregated. We want to make sure that this is justified to end users who might get slightly different results for the same query on a particular dataset.

@kostasb I think the knowledge that the points are floating point are enough. In the part of the documentation where we discuss floating point, a link to the inaccuracies of floating point could be enough. Telling people that their results are going to be slightly different each time they make a query is going to make people think that the calculation is wrong because we're doing something wrong rather than being a natural limitation.
An alternative is we can always try returning a slightly rounded value in the emitter rather than just printing all 15 digits every time.

@jsternberg I will open an issue under our docs repo to add some clarifications about the inaccuracies of floating point, noting that points are not sorted before they are aggregated by mathematical functions - which may result in such minor discrepancies in the outputs.


Automatic render of Data Quality Tests form

The same way that we generate the service connection form based on JSON Schema definitions, the tests UI should do the same. Pick up properties with titles and descriptions and generate the form dynamically.

This is no more relevant, As we are rendering the form as per the test definition!


Change from Factory Girl to fixtures

Feature
Why is this feature being added?

Factory girl is very slow. While we don't have too many features I'd like to switch over to fixtures
What should your feature do?
Replace all factories with features, make all tests pass.

If nobody else is looking at this, I'll start digging in to see the best way to make this conversion happen.

@ianroberts131 all yours!

@hollomancer - FactoryGirl is much more beginner friendly, more flexible, and much more well known to Rails developers.
Our test suite runs plenty fast.  Fixtures would not give us any significant improvements in speed.  Especially when you weigh all the constraints it puts in place, when compared to the flexible nature of FactoryGirl.
We have quite a few tests depending heavily on FactoryGirl today. I recommend that we stay with FactoryGirl, and remove this issue.

@hpjaj, concur. I do not think that test speed is a significant limitation to our development on the backend right now - we can reopen if it is.


Couldn't build using dfx 0.6.18

Hi,
I am trying to compile linkedup for learning purpose. I got the error bellow using dfx build
Note: I modify dfx.json version from 0.6.6 to 0.6.18
Stderr: /var/opt/dev/linkedup/src/connectd/main.mo:6.1-19.2: type error, an actor or actor class must be the only non-imported declaration in a program   (This is a limitation of the current version.)
My problem is my experience with Motoko isn't good enough to find a work around.
Thanks

Hi @rbolog
Types need to be inside the actor (see screenshot)

A PR already addresses this issue, but still needs to be merged to master.

Hi @rbolog
Types need to be inside the actor (see screenshot)

A PR already addresses this issue, but still needs to be merged to master.


Revisit cosmo->status_message.

The original purpose of definding status as an int and keeping error context (status_message) in cosmo object was to avoid tedious manipulation of the error status in numerical code. However, so far all places where cosmo->status_message is used, it is assoicated with *status=.
(see this via. grep -A 1 status_message)
Thus it appears we still propagate status all the way down anyways.
I thus propose moving status_message and merge it with *status into a ccl_error struct. This can be done in a few steps.

typedef int ccl_error; replace all int *status with ccl_error * status.
add method `ccl_error_set_message(cosmology * ...), and deprecate the inconsistent use of sprintf/strcpy.
typedef struct {ccl_error_code * status; char * message} ccl_error; find all ccl_error_set_message, replace with ccl_error_raise(ccl_error_code * status, char * message);

Closing this issue as "won't fix" for now. We could possibly revisit this later, but the current setup is working OK, and subsequent changes to master have fixed some consistency issues.


Converted Notebook to seperate scripts + speed improvements

Hey! Thank you for the notebook!
In the readme I saw that you wanted to convert the script to a python file. I have created two files:

ticker_counts.py -> Contains the first part of the script with the counts for each mentioned ticker.
This scripts saves the created DataFrame to a csv file in the ./data folder. Some speedupgrades have been made and the script could still be further improved. I have also added a TQDM loading bar to see how long you have left to wait.
yfinance_analysis.py -> Contains the analysis and second part of the notebook. The resulting DataFrame will be saved in the same ./data folder

Some remarks:

Please remove your secret Reddit key
Consider changing the yfinance lookup to check if tickers exist with, for instance, a local file with all legal tickers. This should be significantly faster

Please feel free to change the filenames and the code.
Greetings,
Thijs

Very high quality PR @Denbergvanthijs! This is amazing
I agree 100% that having a local file with all static ticker data is the best option for ticker verification, Even I noticed that it takes a long time. Also, Yes. The Reddit secrets slipped through last time. In the next commit I will make them private. Thanks!


IndexOutOfBoundExeption when notifyDataSetChanged() is called

Stack trace:
07-10 15:11:53.936 E/AndroidRuntime: FATAL EXCEPTION: main
                                     Process: com.nejctomsic.registerzdravil.debug, PID: 18830
                                     java.lang.IndexOutOfBoundsException: Index: 3, Size: 1
                                         at java.util.ArrayList.get(ArrayList.java:411)
                                         at com.github.nitrico.lastadapter.LastAdapter.getType(LastAdapter.kt:178)
                                         at com.github.nitrico.lastadapter.LastAdapter.onViewRecycled(LastAdapter.kt:132)
                                         at com.github.nitrico.lastadapter.LastAdapter.onViewRecycled(LastAdapter.kt:27)
                                         at android.support.v7.widget.RecyclerView$Recycler.dispatchViewRecycled(RecyclerView.java:6064)

The issue was not present until version 2.2.2. It was added in this commit.  The problem is when notifyDataSetChanged() is called on the adapter, with a new backing list that has fewer elements than the old one. To fix this, the line that compares the position should be reverted to this one.

Hi @alenjularic
I've never seen this problem and no one else reported it. Can you please make sure you are using it correctly? I'll check it as well. Can you please let me know if you're using an ObservableList or just a regular List?
Thanks.

Same problem here, it happens only if I filter the data (less data in list) and call notifyDataSetChanged()
Caused by: java.lang.IndexOutOfBoundsException: Index: 2, Size: 1    at java.util.ArrayList.get(ArrayList.java:411)    at com.github.nitrico.lastadapter.LastAdapter.getType(LastAdapter.kt:178)    at com.github.nitrico.lastadapter.LastAdapter.onViewRecycled(LastAdapter.kt:132)    at com.github.nitrico.lastadapter.LastAdapter.onViewRecycled(LastAdapter.kt:27)    at android.support.v7.widget.RecyclerView$Recycler.dispatchViewRecycled(RecyclerView.java:6182)

Same problem here. When the list is filtered with the less data than the previous one.
java.lang.IndexOutOfBoundsException: Inconsistency detected. Invalid item position 10(offset:10).state:50 android.support.v7.widget.RecyclerView{a6d485 VFED..... ........ 0,0-1080,1548 #7f0900c4 app:id/rcv_news_latest}, adapter:com.github.nitrico.lastadapter.LastAdapter@fa732da, layout:android.support.v7.widget.LinearLayoutManager@a4b430b, context:com.fintech.assetvantage.main.views.MainActivity@1101dba
                                                                            at android.support.v7.widget.RecyclerView$Recycler.tryGetViewHolderForPositionByDeadline(RecyclerView.java:5628)
                                                                            at android.support.v7.widget.GapWorker.prefetchPositionWithDeadline(GapWorker.java:285)
                                                                            at android.support.v7.widget.GapWorker.flushTaskWithDeadline(GapWorker.java:342)
                                                                            at android.support.v7.widget.GapWorker.flushTasksWithDeadline(GapWorker.java:358)
                                                                            at android.support.v7.widget.GapWorker.prefetch(GapWorker.java:365)
                                                                            at android.support.v7.widget.GapWorker.run(GapWorker.java:396)
                                                                            at android.os.Handler.handleCallback(Handler.java:751)
                                                                            at android.os.Handler.dispatchMessage(Handler.java:95)

Same problem. Removing item from list and causes IndexOfBound.

I still don't understand why this exception occurred but when i change my list to observable list my problem is solve.
@nitrico Please check this issue it's really a major issue.

I'm sorry it took so long... Can you guys please check if the problem is solved in version 2.3.0?

No problem @nitrico. Yes it's fixed for me in 2.3.0. Thank you so much!


jax.numpy.round not working when the result is printed

When printed under brackets, jax.numpy.round is not behaving as expected:
import jax

key = jax.random.PRNGKey(0)
a = jax.random.uniform(key)
print(a)
# 0.41845703
print(jnp.round(a, 2))
# 0.42
print(f"{jnp.round(a, 2)}")
# 0.41999998688697815

The same goes for jax.numpy.around.
I am using jax version 0.3.13.

Great thank you @jakevdp!


Missing DLC

When I began, I had many broken mods and collections on a Next Gen version install, all DLC, no HD Texture update.
In Vortex, I removed and deleted all mods and collections, then ran a file verify in Steam for the Fallout install and all DLC.
I then renamed my Fallout 4 install folder for backup reasons, and made a new empty folder named Fallout 4.
From that blank slate, I followed the instructions for manaul downgrade. All depots were fully downloaded and the contents dumped into the empty Fallout 4 folder. Removed all creation club files and set the app manifest to read only.
When the game is launched via F4SE, I get a perfectly vanilla game lanuch... but Add-ons shows Nuka World is missing. Grayed out and says "coming soon." In Vortex, the nuka plugin .esm files are missing. It shows Fallout4.esm, robot.esm, workshop 1, 2, and 3, and the ccoast.esm. No nuka.
What might have gone wrong? Did I miss something?

The downgrader needs a clean install of fallout 4, it does not download enough files to itself have a full fallout 4 game

Please report back if just installing fallout 4 on steam and then running the downgrader helped.

Will do. This WAS a full and complete install, if not exactly fresh or clean. As clean as I could make it. Was hoping to avoid a full nuke and pave. Nuking and paving now, will report back after

I'm repeating the steps found here using a pristine new install. But there is a conflict:
"The downgrader needs a clean install of fallout 4, it does not download enough files to itself have a full fallout 4 game"
If I understand, I need a proper install, then drop all the depot files into it, overwriting as needed.
The guide by Gopher on youtube states the collected Depot files comprise a full and complete install by themselves. The old folder can be archived or deleted. Before I go pointing fingers, is this a genuine conflict? Or am I not comprehending again.
https://www.youtube.com/watch?v=B-s1C3B2qjY&t=45s with notes/instructions in the description. If he got it wrong, he might listen to you more than me.

This seems to be working. Rebuilding my modlist now. Might be good to drop Gopher a friendly note. Will re-open and add comment if something goes wrong, but otherwise this can probably be closed.

There are issues with Gophers video and we'd have to offer support for that so that's not going to happen.


Support non numeric values for histogram

I am test-driving hyperdx and IMHO the best thing on observability tools is to slice and dice data into several segments to understand and inspect things.
I realized that I have many events being sent from various nodes. The data looks something like:
{
  "Duration": 345,
  "Node": "A"
}

Another would be
{
  "Duration": 25555,
  "Node": "B"
}

I now want to see a histogram binned by Node Name and their durations.
While I can create a histogram about Duration and filter to Node:"B", I would rather be able to create the following histogram:
"Show me the (pick one: average|min|max) duration for Service X, grouped by 'Node'".
I assumed this would be a very common use case. But I might be wrong 😅
As far as I can see, HyperDX does not support it right now. If so, then this is a feature request, otherwise this is a request to help me to find the docs for it 😊
Edit: The line chart actually has an ok-ish visualization for that (if there is more than one data point), but maybe a histogram feature set similar to the line chart would be useful?

Hi @Seikilos I'm wondering if you'd be looking for a table in this case if you want a single data point?

if not, could you share maybe an example image of the kind of visualization you'd be looking for?

Hi @MikeShi42
the table is ok for that, but for visually detecting patterns, tables usually fails.
Here is an excel example:

I can visually spot, that B is off much easier form a chart. Additionally I can instantly see that C is also probably something to look at.

Ahh got it, sorry the word histogram is so overloaded in our app that it took me a minute to get aligned with what you're saying 😅
Totally makes sense - functionally it'll be like our table chart, but being able to visualize the values as bars as well (which is now clicking with me that's what you meant the whole time). This shouldn't be too hard to pull off.
I'm curious what do you think of a combined histogram/table display if it'd help? (crude mockup)

@MikeShi42 how do you overload this word? For what did you guys use it as well?
The table+chart looks great. 👍 Would be very useful. One caveat: The histogram page would need some kind of hint that the functionality that others would 'naturally' search in the histogram tab (as I did) is actually in the table. 😊

Yeah discoverability would definitely be an issue... will need to chew on that a bit more to figure out what we can do there.
For overloading, I guess the two "histograms" we have today are either binned by timestamp (bar chart on the search page), or binned by numeric bucket (histogram chart type, which can bin by number values like 5ms - 15ms, etc.). I'm going to need to do some digging to figure out how to straighten when/how we should talk about histograms in the app.


Don't depend directly on React/ReactDOM

Having these as dependents makes it impossible to upgrade to React 0.15 and beyond until this library does.
Also it's just not necessary. A React library can safely assume that React is around :) If you do rely on specific React apis that were introduced only recently, you can add peerDependencies for them.

Should they be peer deps then?

Yeah exactly.

Want to add them as peer deps? Then I will merge this in.

Done.

Thanks good sir :+1:


Register v0.1.7

@JuliaRegistrator register
Release notes:

include_columns and exclude_columns keyword arguments to fillter columns

Registration pull request created: JuliaRegistries/General/101674
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.7 -m "<description of version>" 5aab44df5eeca8d4df602857482a07d92adf7533
git push origin v0.1.7


Problem running in ESM module

It seems that this package doesn't like to be run under ESM
import graphql from "github-openapi-graphql-query";

const QUERY = `
  query($version: String) {
    endpoints(version: $version, ghecCompatibilityMode: true) {
      url
      triggersNotification
    }
  }
`;

const {
  data: { endpoints },
} = await graphql(QUERY, {
  version,
});

Results in TypeError: Cannot read properties of null (reading 'endpoints')

if you are up to turning the whole module to ESM, I'm down


Unbuffered output

I'm running some codon generated executables in batch mode and I realized it sends to stdout just as Python (kind of expected), that is a buffered output. I know in Python I can run a script using the -u switch to have unbuffered stdout, is there something similar for codon?

Not yet—we can add this in the later versions (wasn't even aware of -u until now). For now, you'll have to flush the stdout manually (stdout.flush() should work) or use stderr.


terraform-docs broken in 1.11.0 ?

Hi, trying to use pre-commit hooks for terraform-docs but every-time the hook is passed no readme.md file is created. It works well for terraform-fmt though and modify the files accordingly. Thanks for your support!
System Information:

MacOS : 10.14.4 (18E226)
Terraform-docs : 0.6.0
Bash version : GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin18)
Terraform v0.11.13
Python 3.7.3

Files:
├── main.tf
├── output.tf
└── variable.tf

.pre-commit-hook.yaml:
  rev: v1.11.0
  hooks:
    - id: terraform_fmt
    - id: terraform_docs

Issue:
% pre-commit run -c .pre-commit-config.yaml --all-files --verbose
[terraform_fmt] Terraform fmt............................................Passed
[terraform_docs] Terraform docs..........................................Passed

Yah, it's not working for me either.  I'm on MacOS 10.14.4 as well.
I keep getting a"Failed", no matter what, and won't allow me to commit.

I can't get this to work on my MacOS 10.14.4 either.

It does not work for me either.

pre-commit run -a
Terraform fmt............................................................Passed
Terraform docs...........................................................Failed
hookid: terraform_docs

/home/mdorner/.cache/pre-commit/repoq21wt094/terraform_docs.sh: line 65: terraform-docs: command not found

Terraform validate with variables........................................Passed

The problem seems to be that it tries to call a binary called 'terraform-docs' in line 65 which is not in $PATH.
terraform-docs $args md ./ > "$tmp_file"

@moxli You need to install the dependencies and make sure they are on your path. This is not an issue with the hooks. But if you are on a Mac, my fork has a hook to install the dependencies with homebrew

Sad to say, but terraform-docs won't work with 0.12. Of course if you upgrade your code properly to that version. Tested by running manually, it's failing with error: 2019/06/07 14:25:53 At 2:12: Unknown token: 2:12 IDENT var.region - as in top scope we don't need to use "${var.region} anymore, just can and should use var.region.
Looking on that project, it seems to be abandon - last changes nearly half year ago, before there was something happening every month.

terraform-docs and Terraform 0.12 support has been released in v1.13.0.


🔧 MAINTAIN: Improve repository format

This commit does not fundamentally change any of the code, except for formatting.
It updates the package inline with EBP latest best practices

move the setup configuration to the static setup.cfg (and add pre-commit formatter)
Add pyproject.toml, for build configuration
Update versions in pre-commit and adds  check-manifest, isort (import ordering) and mypy (type checking)

thanks @chrisjsewell.

move the setup configuration to the static setup.cfg

This is pretty tidy way to specify the requirements. Nice. Is this the new standard for executablebooks?

This is pretty tidy way to specify the requirements. Nice. Is this the new standard for executablebooks?

Yeh currently, eventually all the configuration will be moved to pyproject.toml and setup.cfg can be removed (it's an approved python pep)


Create Audit Log FSM state

Description
Changes proposed in this pull request:

a new state in state machine that is responsible for configuring Audit Logs on Shoot

Related issue(s)
#286

/cla-recheck


[3.0] [CPI] Add option to ignore OpenStack Cinder availability zone, bsc#1095572

This was merged into master (with review from @vitoravelino & @MaximilianMeister) back in July, and was previously approved here before Kiall left.  What happened to prevent merge into the release?


Error running onnx inference with multiple images: "onnxruntime.capi.onnxruntime_pybind11_state.InvalidArgument: [ONNXRuntimeError] : 2 : INVALID_ARGUMENT : Non-zero status code returned while running GatherElements node. Name:'/model/decoder/GatherElements' Status Message: GatherElements op: 'indices' shape should have values within bounds of 'data' shape. Invalid value in indices shape is: 2""

If I try to run onnx inference for multiple images at the same type I've got the error:
onnxruntime.capi.onnxruntime_pybind11_state.InvalidArgument: [ONNXRuntimeError] : 2 : INVALID_ARGUMENT : Non-zero status code returned while running GatherElements node. Name:'/model/decoder/GatherElements' Status Message: GatherElements op: 'indices' shape should have values within bounds of 'data' shape. Invalid value in indices shape is: 2
The inputs shape are the following:

images (im_data): (4, 3, 640, 640)
orig_target_sizes (orig_shape): (4, 2)

The python code is as follows:
output = dfine_session.run(
            output_names=None,
            input_feed={'images': im_data, "orig_target_sizes": orig_shape}
        )

Is there a way to run inference on múltiple images as one batch?

I think that I found the problem @Peterande . In the export onnx script you should change:
data = torch.rand(1, 3, 640, 640)
size = torch.tensor([[640, 640]])
for:
data = torch.rand(2, 3, 640, 640)
size = torch.tensor([[640, 640], [640, 640]])
Otherwise the exported model doesn't support batching. If I'm right I would like to make the PR myself to be a contributor if possible.

https://github.com/Peterande/D-FINE/pull/35
👀