Simple example does not do column/row layout under WidgetKit

This one is pretty odd. This simple WidgetKit example:
import SwiftUI
import ExyteGrid
import WidgetKit

struct GridIssue2View: View {
    var body: some View {
        Grid(tracks: [
            .fit, // label
            .fit, // value
        ], spacing: 3)
        {
            Text("A")
            Text("B")
            Text("C")
            Text("D")
        }
    }
}

struct GridIssue2View_Previews: PreviewProvider {
    static var previews: some View
    {
        GridIssue2View()
            .previewContext(WidgetPreviewContext(family: .systemSmall))
    }
}

Does not do column/row layout in preview mode:

But when placed in view for real widget, it renders OK in preview. Also I could place within ZStack to fix:
struct GridIssue2View: View {
    var body: some View {
        ZStack
        {
            Grid(tracks: [
                .fit, // label
                .fit, // value
            ], spacing: 3)
            {
                Text("A")
                Text("B")
                Text("C")
                Text("D")
            }
        }
    }
}

Similar preview example under iOS is fine. Perhaps related to ScrollView change?
iOS:
import SwiftUI
import ExyteGrid

struct GridIssue2View: View {
    var body: some View {
        Grid(tracks: [
            .fit, // label
            .fit, // value
        ], spacing: 3)
        {
            Text("A")
            Text("B")
            Text("C")
            Text("D")
        }
    }
}

struct GridIssue2View_Previews: PreviewProvider {
    static var previews: some View {
        GridIssue2View()
    }
}

To support a preview for Grid I had to apply some kind of hack (ForEach+GridViewsContaining.swift:46-68 and GridGroup.swift:20-30).
Looks like it doesn't work for widgets.


Clarify laws of NonDet

NonDet satisfies the "left-catch" law for MonadPlus but not the "left-distribution" law. This is a little surprising, since that makes it more "maybe-like" than "list-like" (Maybe satisfies "left-catch" but not "left-distribution", and vice versa for lists), which isn't quite what I'd expect for a non-determinism monad.
return x `mplus` m = return x -- left catch
(m `mplus` n) >>= k  =  (m >>= k) `mplus` (n >>= k) -- left distribution

In practice this means that:
do
   v <- a <|> b
   f v

is not the same as
(f a <|> f b)

so you can't guard after you <|>, etc.
I don't think it's possible to satisfy "left-distribution" with NonDet as it's currently implemented, since it's implemented with exceptions. So I just think we should say something in the documentation, to save future people some time!

Interesting! I think that's the opposite. I don't know what "algebraic" means in this context, but it sounds like their Choice effect satisfies left-distribution ,which is what I want.
I'll make you a PR :)


Explore CoCo

Explore Confidential Containers and see how we can utilize them.
Write down the report to the comment of this issue.

Split between #337 and #338. Closing this one.


stream info: add attempt count for HTTP requests and TCP proxy

Commit Message: stream info - add attempt count for HTTP requests and TCP proxy
Risk Level: low
Testing: UT

cc @goaway

Thanks @junr03!

@ggreenway fair point, update to include in tcp proxy.

/retest

/retest


flake8 should ignore generated test script files

in precommit config file

Fixed:
- repo: https://github.com/PyCQA/flake8
  rev: 6.0.0
  hooks:
  - id: flake8
    exclude: ^tests/generated_scripts/

https://github.com/sgbaird/honegumi/pull/4


[feature] Use schema store to get json schema

https://github.com/kkiyama117/coc-toml/blob/main/src/index.ts#L64
Why not use schemastore to get json schema?
Related issue: https://github.com/neoclide/coc-json/issues/75

https://taplo.tamasfe.dev/configuration/developing-schemas.html#publishing:

Submitting schemas directly to Taplo is not possible anymore, and all JSON schemas should be submitted to the JSON Schema Store.

Yes, https://github.com/tamasfe/taplo/tree/master/editors/vscode use schemastore.

I think it is a very good suggestion, as are the other issues you have put up. I will work on it later if I can find the time, but I am currently a university student and I don't think I will have time to work on it for another month or so due to my graduation thesis, remaining credits and graduate exams.
This coc-toml is based on the alpha version of taplo's plugin for vscode, modified to fit the configuration of other coc plugins. If I remember correctly, taplo is now in a different major version from that time, and I think there are discrepancies in some functions and links such as schema, etc. because the internal structure is different. If you want these features immediately and can use Node.js, I hope you can make the changes and create a PR.

Also, I now use a plugin structure in vim based on the denops ecosystem and do not use coc in main. That, and the private reasons mentioned above, have slowed down the updating of coc-toml. If you use coc regularly and you or someone you know is familiar with coc, nodejs or vim, and you are interested, please let me know in a separate issue as I will transfer this repository.

someone you know is familiar with coc, nodejs or vim

How about https://github.com/coc-extensions?

Sure. I'll discuss it there when I can take the time to reply properly.


Fix zipalign command name on Windows machines

Fixes https://github.com/godotengine/godot/issues/43650

Thanks!

Cherry-picked for 3.2.4.


 There are so many confusing things... Even docs.  Because that tone is unacceptable here.

As a beginner (to anything), a person should be quite humble about what might be right or wrong, because no one will get acceptance to suggested changes or their opinions with the kind of tone or attitude you are demonstrating here.
And please - always only speak for yourself. You are irritated by the docs. You shouldn't assume everyone else is too.
Scott

Listen, people complain about many bugs.

Why are you so fixated on the "stupidity" of these bugs? Do you not understand how distracting that language is, and how little it makes anyone want to help you?

Unfortunately, my questions are ignored. The only way to get attention is to open such issues. Pardon. So, who can me explain why do you use cache variable two times? It's not even ESLint-friendly. This code just killng me.


Update ingress-controller-install-existing.md

Title: Clarification of Permission Requirements for AGIC and Application Gateway Deployment Summary
This pull request updates the documentation regarding the deployment of Application Gateway in a different resource group from Azure Kubernetes Service (AKS) nodes. The intention is to enhance clarity and comprehension for users setting up Application Gateway Ingress Controller (AGIC).
Justification
Enhanced Clarity: The original phrasing was somewhat technical and could be challenging to understand for users not deeply familiar with Azure role-based access control. The rephrasing aims to make the instructions more accessible to a broader audience.
Emphasizing the Importance of Correct Permissions: The updated text underscores the necessity of having the Microsoft.Network/virtualNetworks/subnets/join/action permission for AGIC. This is crucial for successful deployment and operation.
Guidance on Role Assignment: The revision explicitly suggests using the "Network Contributor" role if a custom role isn't available. This direct recommendation can aid users in quicker decision-making.
Preventing Potential Configuration Issues: By making the requirements clearer, the update seeks to reduce the likelihood of misconfigurations that could arise from misunderstandings about permission and role requirements.
Conclusion
The proposed changes aim to improve the usability of our documentation, ensuring that users have a smoother experience with Azure's networking and Kubernetes services. This clarity is essential for effective setup and minimizes potential support queries related to misconfiguration.

@greg-lindsay
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@greg-lindsay
Can you review this old PR and determine whether it needs to be closed or merged?
If the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

Since the PR is old and now has conflicts, I will create a private PR to incorporate this edit. Thanks for the contribution. #please-close


Detect new wasm features

The way the wasm collection is currently set up will not detect new wasm features. This PR gets the list of wasm features from the wasm-feature-detect package so the collector can find new wasm features from there.
Not sure why it was decided to not use the same keys from the wasm-feature-detect package in BCD. That would have been cleaner... I'm mapping the existing ones now.

Ah, thanks for the context! I don't see mdn_urls for these features. Anyway, I don't think we have to change this. The mapping works. The important part was to get to know about entirely new wasm features.


feat(reporting): add reporting to page and account sheet

Describe your changes

added account reporting dialog to the page and account-sheet component
initialized pocketbase

Issue link

https://github.com/palladians/minaverse/issues/25

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] I have added necessary test automation or not applicable.

After pulling changes, run pnpm install and set NEXT_PUBLIC_POCKETBASE_URL env variable.
There's also need to add Turkish 🇹🇷 translations 👇
accounts.warning
accounts.accountSuspicious
accountReport.trigger
accountReport.title
accountReport.reason
accountReport.reasonDescription
accountReport.evidence
accountReport.submit
accountReport.toast


Cleanup: deleted file BenchmarkMetricRouter.js and its related usage

#190

Deleted file BenchmarkMetricRouter.js and its related usage in back end and front end.

Signed-off-by: sophiaxu0424<EMAIL_ADDRESS>

Having some concerns about Dong's PR here: https://github.com/AdoptOpenJDK/openjdk-test-tools/pull/207/
since his adding is still using the old design, not sure if I should combine it together into this PR or Dong could add it later after mine's merged.

Thanks @sophiaxu0424
I commented on #207 https://github.com/AdoptOpenJDK/openjdk-test-tools/pull/207#issuecomment-595238610

Please make sure this PR will not break the test with TKG and without TKG. Thanks.

Need to apologize, I double checked TKG and non-TKG test builds, and found that I missed the updating for the Utils's functions in BenchmarkPaser. Have updated it together in this push.


Credential permissions

What type of permissions (role) are required to use the Connect cmdlet?

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

ID: 1ee082c9-735d-3f8a-7bc4-b2d4f175c784
Version Independent ID: 50e0366c-46b0-71da-b6f6-f422adaad785
Content: Connect-MicrosoftTeams (teams)
Content Source: teams/teams-ps/teams/Connect-MicrosoftTeams.md
Service: teams-powershell
GitHub Login: @kenwith
Microsoft Alias: kenwith

Hi @DeanGross , thank you for your feedback.
You can connect if you are admin or have a teams license.
If you are admin you can manage any Team, if you have a license assigned you can manage Teams you are the owner and create new Teams.

@dariomws306  Thank you very much for the contribution and sharing this explanation. @DeanGross
Hope this comment is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Didn't anyone find the official website's plug-in store inaccessible?

See #57851

Duplicate of #57851


router.push() doesn't update query when providing name route doesn't change

from #1182 @kvdmolen

Version
2.7.0
Reproduction link
http://jsfiddle.net/ub9e33fm/12
Steps to reproduce

Click first link (?q=foo)
Click second link (?=foo,bar)

What is expected?
$route.query should update
What is actually happening?
It only updates after another navigation

I can confirm this issue. Is there any hack to fix this issue?

Same here, it is annoying because I would want to use query to filter an array.

Same issue, can't update query dynamically for the same route. Query object is getting updated, but it's not showing up in the route.

Quick workaround: Use a fresh array (this.arr.slice()) when using .push()
http://jsfiddle.net/ydwmmum6/

@fnlctrl Here is the example issue.
Version
"vue": "^2.4.2",
"vue-router": "^2.7.0"
Reproduction link
https://jsfiddle.net/ydwmmum6/2/
Steps to reproduce

type random text in input field and hit search

What is expected?
$route.query should update
What is actually happening?
input field gets the value from the previous $route.query

Actually, I don't know why I marked this as a bug... If the array is the same, it's normal for the router not being able to tell it's a different location. To fix it we could compare the JSON representation (which could be very slow) or copy the arrays in queries which can also be slow.


background-image and background-position classes are being removed wrongly

Describe the bug
When supplying multiple "similar" classes, some are removed wrongly.
To Reproduce
https://codesandbox.io/s/magical-sound-6sfws8?file=/src/index.ts
Expected behavior
Background size, and image should be included.
Environment

tailwind-merge version: 1.13.2

Additional context
N/A

Hi @iduuck! 👋
That's a bug indeed, thanks for reporting! I'll fix that.
I'll include this in a v2 release I'm working on, so I won't be able to ship the fix immediately.
As a temporary workaround you can use the tag url: at the beginning of the arbitrary value for background-images (even if they aren't actually URLs) like this:
bg-[url:linear-gradient(-45deg,#fff_0%,#f9fafb_100%)]

Tailwind CSS accepts that value and tailwind-merge will detect it as a background-image class.

Note to myself:

I should use the image CSS data type instead (url is not really a data type since it can be used for different data types like images and fonts): https://developer.mozilla.org/en-US/docs/Web/CSS/image
images can be startsWith url(, element(, image(, image-set(, cross-fade(

can also be a CSS data type gradient which startsWith linear-gradient(, radial-gradient(, repeating-radial-gradient(, repeating-linear-gradient(, conic-gradient(
The Regex for that could be a bit long, maybe I could add support only with CSS data types
Interestingly Tailwind CSS only supports image: or url: as tags but not gradient:

@iduuck I just realized that arbitrary values in background-position and background-size classes are currently only supported by using tags position: and size:, otherwise they'll get classified as background colors and merged with other background colors. So if you're using arbitrary values in those, you need to keep that in mind.
I'll either fix this as well or make this clear in the documentation.

@dcastil Having similar issue here, when applying classNames like text-red-500 and text-lg, one of them will be removed because having the same prefix

Hey @locbqvmo! 👋 Could you open a separate issue for that and provide a reproduction example? I just played around on https://codesandbox.io/s/tailwind-merge-playground-cssr35?file=/src/index.ts with
const mergeData: MergeData[] = [
    {
        args: ['text-red-500 text-lg'],
    },
]

and it outputs text-red-500 text-lg which seems correct.

Hi @dcastil. Try with a custom tailwind config. I define new fontSize: "40px".
//tailwind.config.js
module.exports = {
  ...
  theme: {
    extend: {
      fontSize: {
        "40px": ["40px", "56px"],
      },
    },
  },
  ...
};

My component pass props
className={twMerge("mb-10 text-center text-40px font-semibold text-bbc-brand-800 ")}

and I got result:

The "text-40px" is in conflict with "text-bbc-brand-800" so"text-40px" class are being removed wrongly.
But, if I try with name is "text-40xl":
//tailwind.config.js
module.exports = {
  ...
  theme: {
    extend: {
      fontSize: {
        "40xl": ["40px", "56px"],
      },
    },
  },
  ...
};

className={twMerge("mb-10 text-center text-40xl font-semibold text-bbc-brand-800 ")}

I got true result:

The "text-40xl" isn't in conflict with "text-bbc-brand-800".
The same issue if I try "text-40size", "text-40abc",... Only "text-40xl" same suffix "xl" with "text-xl","text-2xl",.. of tailwind default return true.

Hey @ankhoa18599! 👋
tailwind-merge doesn't have access to the tailwind.config.js file and you need to configure it separately. The default out-of-the-box config of tailwind-merge assumes all unknown classes which could be a color are a color, this is why it de-duplicated text-40px when you use text-bbc-brand-800 afterwards.
Here is an example on how to configure tailwind-merge: https://github.com/dcastil/tailwind-merge/blob/v1.14.0/docs/recipes.md#adding-custom-scale-from-tailwind-config-to-tailwind-merge-config.
And here is the documentation on how the tailwind-merge configuration works: https://github.com/dcastil/tailwind-merge/blob/v1.14.0/docs/configuration.md#usage-with-custom-tailwind-config.

Hi. I have the same issue as @ankhoa18599.
@dcastil could you expand on how one can configure extendTailwindMerge? There is no fontSize config inside theme (considering https://github.com/dcastil/tailwind-merge/blob/v1.14.0/docs/configuration.md#theme).
Even though I added all my custom color names inside theme.colors, merge doesn't work properly.

Hey @Senneer! 👋
When the group isn't in the theme, then you need to check the default config and find the class group ID. For fontSize it's here: https://github.com/dcastil/tailwind-merge/blob/v1.14.0/src/lib/default-config.ts#L619
So your config should look like this:
const twMerge = extendTailwindMerge({
    classGroups: {
        'font-size': ['text-custom-1', …]
    }
})

https://github.com/dcastil/tailwind-merge/blob/v1.14.0/docs/recipes.md#adding-custom-scale-from-tailwind-config-to-tailwind-merge-config

Literally having the same issue when trying to add this for my error messaging. With text-red and text-extrasmall it applies the font in this case but it won't take the color.
Also, I am using class-variance-authority
`
import { cva, VariantProps } from 'class-variance-authority';
import { FC } from 'react';
import { twMerge } from 'tailwind-merge';
const paragraphClasses = cva(
['font-normal', 'font-display', 'text-base', 'text-center'],
{
variants: {
intent: {
h2: ['font-light', 'text-black'],
errorMessage: ['text-left', 'text-red', 'font-light', 'text-small'],
},
},
},
);
`

I had to add an extra extend in the call to extendTailwindMerge to get it to work:
export const twm = extendTailwindMerge({
  extend: {
    classGroups: {
      'font-size': [
        'text-h1',
        ...
      ],
    },
  },
});

@noorvir Yes, that is due to the change from v1 to v2 → https://github.com/dcastil/tailwind-merge/blob/v2.2.0/docs/changelog/v1-to-v2-migration.md#extendtailwindmerge-object-shape-changed

I was wondering why bg-white bg-[url(somefile)] was overwritten.
Changing for bg-white bg-[url:url(somefile)]. I wonder if for "URL" the prefix is really necessarry ?
Can't it be determined with heuristic ?

Hey @mrleblanc101! 👋
Just tested it and I get the result twMerge('bg-stone-100 bg-[url(somefile)]') === 'bg-stone-100 bg-[url(somefile)]' in v2.2.1. tailwind-merge indeed uses url(…) to detect bg-images (code) and you shouldn't need to use the url: tag for them. Could you try to create a reproducible example and open a new issue with it?

@dcastil Might be a tailwind issue then.
Without the url:url() prefix, it would generate a background instead of a background-image, so the background-color longhand was overwritten by the background shorthand.
I'll look into it and provide a repro if needed or open a new issue on the tailwind repo.

@dcastil
Here is the repro: https://codesandbox.io/p/sandbox/tailwind-merge-playground-cssr35?file=%2Fsrc%2Findex.ts%3A23%2C1-26%2C7
It looks like tailwind-merge thinks that bg-[center_right_0.75rem] will overwrite my bg-stone-100.
But this seems incorrect, as tailwindcss properly infer that bg-[center_right_0.75rem] will results in background-position
I don't know if tailwindcss updated/improved they heuristic, but bg-[center_right_0.75rem] did not need the position: label like so bg-[position:center_right_0.75rem].
So it's partially improper use from my part, but seems also like a bug in tailwind-merge because the same thing works without tailwind-merge.
I can create a seperate issue if needed.

@mrleblanc101 background-position and background-image classes always need a label for tailwind-merge to know what to do because the values for both of them look very similar and sometimes even identical. You can read more on that in the docs: https://github.com/dcastil/tailwind-merge/blob/v2.2.2/docs/limitations.md#you-need-to-use-label-in-arbitrary-background-position-and-background-size-classes

@dcastil But why and how does Tailwindcss infer it correctly ? Should tailwind-merge have the same inference ?

Yes, I try to be close to Tailwind's implementation. It's not always possible to use the exact same approach because tailwind-merge has much bigger constraints when it comes to how fast it needs to process data and how much code it can ship since it's typically within the frontend bundle. But the biggest obstacle is usually how much time I have to research and build.
In case you really want to have this feature, feel free to research how Tailwind detects which of the two it is and post a new issue with the info. I could pick it up from there or you could continue and submit a PR.
A good starting point is Tailwind's definition of the backgroundPosition plugin: https://github.com/tailwindlabs/tailwindcss/blob/d86fd0bb5b69c9aa5c75d4e78f8fe78969d6ff50/src/corePlugins.js#L1965-L1967

@dcastil Thanks for you explaination.
I did not know tailwind-merge was not an official Tailwindcss plugin since it's heavily featured in most YouTube tutorials, so thank you for your plugin.
I am not an avid Tailwindcss user, so I'll look this up later if I have time or let someone more interested look into it as this is a pretty minor annoyance, I just found it off after understanding the problem completely.

Spent some time figuring this out, might help someone. Pay attention to the custom class you need to extend in the config. You need to type the whole class, while on tailwind.config you can forgo the prefix.
Tailwind config
const tailwindConfig = {
  theme: {
    extend: {
      fontSize: {
        'xs': ...,
        'sm': ...
      }
      ...

twMerge config
const twMergeConfig = extendTailwindMerge({
  extend: {
    classGroups: {
      'font-size': [
        'text-xs', <-- include 'text'
        'text-sm',
        ...


🌐 Add Japanese translation for FastAPI People

This PR translates the fastapi-people.md to Japanese.

Thank you for your review!
Top contributors/reviewers with translation  must need cooperations between translators. I'm always really grateful. 🙇 🙇 🙇

@delhi09 Thank you for reviewing!
I committed some changes for your suggestions. Please check it again.

Amazing @tokusumi ! :bow: :tada:
Thanks for the reviews as always @komtaki and @delhi09 ! :cake:

Amazing @tokusumi ! :bow: :tada:
Thanks for the reviews as always @komtaki and @delhi09 ! :cake:


Test hxcpp gc moving objects

You can define HXCPP_GC_MOVING and call cpp.vm.Gc.compact() from haxe code
See: https://github.com/HaxeFoundation/hxcpp/blob/0d0dd2a2797ffa7196a889679ba059aa67d380da/src/hx/gc/Immix.cpp#L2305-L2314

More of the conversation:
Hugh Sanderson [10:13 PM]
If you are tracking creation count, you don't need to do anything in the collection
If you are tracking lifetimes, then you need to do something
I think the fastest way is to iterate over your live object list immediately after marking and check to see if it is still marked.
This should be a simple byte offset an lookup per pointer.
If you only wanted to track the creation of Double/Int/StringData and assume they are not live after next next collect, you probably would not be too far wrong, and you could save some time.
Jeff Ward [5:27 PM]
Thanks, @hugh - so iterating over my live object list would look something like this?
https://github.com/HaxeFoundation/hxcpp/blob/master/src/hx/gc/Immix.cpp#L3214-L3226 (edited)
Hugh Sanderson [10:28 PM]
Yes, you would be basically doing exactly what this finalizers do - except you already have your list of pointers.
 unsigned char mark = ((unsigned char *)obj)[ENDIAN_MARK_ID_BYTE];
      if ( mark!=gByteMarkID ) // Old

Hugh Sanderson [10:39 PM]
Yes - I've added defragging and compacting (for 'memory low' messages), but this is currently not enabled by default because you need the HXCPP_GC_MOVING define.
I'm wondering if the telemetry code is ready for moving blocks.  The "movespecial" code handles this
One possibility is to not allow moving with telemetry on
Jeff Ward [10:44 PM]
Hmm, I vaguely recall doing something wrt moving or reallocation, not sure if that's the same thing. Not sure how well it's tested.
Hugh Sanderson [10:48 PM]
Probably not tested because this code has not been active for a while.  Although, it appears to mostly follow the pattern, so could be ok.
Jeff Ward [10:50 PM]
Yeah, it looks like it handles the finalizer, but it looks like it doesn't inform the Debug.cpp of the changed pointer, there's a todo here:
https://github.com/HaxeFoundation/hxcpp/blob/0d0dd2a2797ffa7196a889679ba059aa67d380da/src/hx/gc/Immix.cpp#L2305-L2314 (edited)
I can do some testing -- is there any way to force this to happen more often?
smaller memory parameters or some trigger?
Hugh Sanderson [10:53 PM]
You can define HXCPP_GC_MOVING and call cpp.vm.Gc.compact() from haxe code
Jeff Ward [10:54 PM]
ok, great, I'll look into it, then. I might expect perhaps to see those printf's with HXCPP_GC_MOVING  and HXCPP_TELEMETRY both defined
Hugh Sanderson [10:56 PM]
There are some other possibilities depending on how things are done.
One woud be to attach the telemetry data pointer to the allocation directly by using some space at the end of the buffer
Then this would be moved when the allocation is moved
You would then need to walk over all the objects that were active since the last collect to find out what has been collected
Jeff Ward [10:58 PM]
Oh, and another topic -- if I change the interface of telemetry in Debug.cpp and need to detect that in hxtelemetry.hx, since I didn't put a version in to start with -- can I do something like:
Debug.cpp:
#define TELEMETRY_VERSION=2
Hxtelemetry.hx (@header or something):
#ifndef  TELEMETRY_VERSION
#define TELEMETRY_VERSION=1
Would this work with older (undefined) and newer (ver=2) hxcpp?
Jeff Ward [10:58 PM]
Or is there a different/better way to detect hxcpp version?
Hugh Sanderson [11:00 PM]
You can change toolchain/common-defines.xml to define HXCPP_TELEMETRY=2 if you like - this will be visible in the generated .cpp code
But not the .hx code
Jeff Ward [11:01 PM]
Can my HxTelemetry library be compatible with both versions?
Hugh Sanderson [11:02 PM]
It depends on if you need to change the haxe code
You could do something like inject "version=2" FROM the haxe code (via build.xml) and then check in Debug.cpp and do some kind of wrapepr for the old code
Jeff Ward [11:04 PM]
Ok, thanks for the info!
James Gray [11:08 PM]
is the plan to define HXCPP_GC_MOVING by default?
Hugh Sanderson [7:23 AM]
I think so - it only really adds overhead if its needed (which is fair enough I think) but also adds a bit to "get object id" and objecthash on 32 bit systems, since we can no longer use the raw pointer.
It also allows for memory compaction which can be useful on mobile

While moving support was added here (https://github.com/HaxeFoundation/hxcpp/issues/332) there is still a crash being investigated here (come back to this when time allows): https://github.com/HaxeFoundation/hxcpp/issues/333


JavaScript Error

BEFORE MAKING A BUG REPORT, PLEASE READ THE
CONTRIBUTING GUIDE.
BUG REPORTS ARE NOT FOR SUPPORT REQUESTS. IF YOU JUST NEED HELP,
ASK IN THE DISCORD SERVER.
BUG REPORTS THAT DO NOT PROPERLY FILL
IN THE TEMPLATE MAY BE IGNORED OR REJECTED.

What is happening?
Javascript error in the attached image
What should be happening?
Notion should run , but has the error
Screenshots (if applicable):

Operating system/browser name & version:
windows 10 latest
notion-enhancer and/or notion-repackaged version:
notion-enhancer
notion-enhancer configuration (enabled/disabled mods and their settings):
I do not know

After updating notion-enhancer by commandline, the Same Isuue I met, I follow the Exception and change separator \ to / at two files which shown in MsgBox.
Then Notion launchs with launching cirlcle circling forever. Not sovled.
Windows 11 21H2 22000.376

dup of https://github.com/notion-enhancer/desktop/issues/684#issuecomment-1004797099


Subtotal spec with grand total and ordering

Description
Currently, when applying ordering on a dimension to a query that has a total subtotal spec applied (or any subtotal spec that does not contain the dimension) will return an error.
{
    "queryType": "groupBy",
    "dataSource": "some_awesome_table",
    "granularity": "all",
    "dimensions": [
        "country"
    ],
    "aggregations": [
        {
            "type": "count",
            "name": "count"
        }
    ],
    "subtotalsSpec": [["country"], []],
	  "limitSpec": {
		    "type": "default",
		    "limit": 100,
		    "columns": [
					  {
                "dimension": "country",
                "direction": "descending"
            }
				]
	  },
    "intervals": [
        "2019-06-30T00:00:00Z/2019-06-31T00:00:00Z"
    ],
     "context": {
        "useCache": false,
        "populateCache": false,
        "useResultLevelCache": false,
        "populateResultLevelCache": false
     }
}

returns
{
  "error": "Unknown exception",
  "errorMessage": "Unknown column in order clause[OrderByColumnSpec{dimension='country', direction='descending', dimensionComparator='lexicographic'}]",
  "errorClass": "org.apache.druid.java.util.common.ISE",
  "host": null
}

This is obviously technically correct as the total subtotal does not contain the dimension. It would be more useful to allow the ordering in this case, as a total will only ever produce 1 record, and therefore can never actually be ordered.
Motivation
It is fairly common to want to order results and provide totals. In the above example, it is not unreasonable to want to provided alphabetical country ordering and a total at the same time.
The argument could be made to reduce ordering columns to the subset of columns in the the subtotal spec, as long as all ordering columns exists in at least 1 subtotal spec or is a metric.

due to various changes in subtotals processing , I expect this to work in 0.16.0 release for which RC will come out very soon. Please give that a try.

Awesome, thanks for getting back to me so quickly.
I will give that a try.


Patch/updates 202305

Codecov Report
Patch coverage: 30.76% and project coverage change: -1.77 :warning:

Comparison is base (c2d6f6b) 18.19% compared to head (7441d0e) 16.42%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #164      +/-   ##
============================================
- Coverage     18.19%   16.42%   -1.77%
- Complexity      213      215       +2
============================================
  Files            40       41       +1
  Lines           918      962      +44
============================================
- Hits            167      158       -9
- Misses          751      804      +53

Impacted Files
Coverage Δ

app/Console/Kernel.php
60.00% <ø> (ø)

app/Http/Middleware/RedirectIfAuthenticated.php
0.00% <ø> (ø)

app/Services/ExchangeRateService.php
0.00% <0.00%> (ø)

app/Kata/Challenges/KataChallengeMySQL.php
38.70% <50.00%> (+1.67%)
:arrow_up:

app/Kata/Challenges/KataChallengeEloquent.php
90.47% <100.00%> (-0.44%)
:arrow_down:

...pp/Kata/Challenges/KataChallengeEloquentRecord.php
100.00% <100.00%> (ø)

... and 7 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Import history

https://trello.com/c/7LsjNZM2/802-add-endpoints-for-importing-content-in-to-the-publishing-api-3
I'm looking at this as part of the work on importing Needs in to the Publishing API.

Seems like work is still ongoing on this. It might be best to close the PR until it's actually ready for review.

This is now at a point where we have importing needs in to the Publishing API working locally, so it would be good to get more review so this can be merged.

What more needs doing on this now? I think I've addressed the feedback given, so let me know if I've missed something.

What more needs doing on this now? I think I've addressed the feedback given, so let me know if I've missed something.

Bump again. @kevindew, @dougdroper could you take another look, as I think I've made changes since you last commented on this.

Sorry @cbaines I started a review the other day but didn't get a chance to finish it. We're just working out who'll have some time to go review it properly.

Sorry @cbaines I started a review the other day but didn't get a chance to finish it. We're just working out who'll have some time to go review it properly.

Any news yet? Ideally this would be merged in and deployed to production before we get Maslow to a state where it can use the Publishing API, so that deploying Maslow using the Publishing API is just blocking on getting Maslow working, and not the Publishing API. We (@binaryberry @issyl0 and I) now have Maslow rendering content from the Publishing API in a rudimentary way, so I'm hopeful that getting Maslow working fully with the Publishing API is not too far off now.

@cbaines sorry nothing to report, are you free this morning? I can pop over and chat through some bits with you - if so let me know when your stand up finishes.

What is the progress on getting this merged? I'd like to start testing Maslow using the Publishing API on integration and staging over the next few days, and that will be easiest to do if this is merged.
From what I remember of our conversation last week @kevindew , we discussed some things about simplifying the way states are specified. I may have forgotten the details, but looking at the current implementation, I don't see any opportunities to simplify it.

@cbaines I've just added some documentation. If you can just check that over for me that'd be great then I'll approve.

@cbaines I've just added some documentation. If you can just check that over for me that'd be great then I'll approve.

All fine by me.

:fireworks: :fireworks: :fireworks: :fireworks:


Reacting to Caching api review changes

@Tratcher

Hi @kichalla, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:shipit:


Screengrab improperly handles the adb server being out of date.

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
Screengrab thinks "adb" is a valid device name if the adb server is out of date and must be restarted upon running the adb devices -l command because it isn't in the array used for devices.reject.
Complete output when running fastlane, including the stack trace and command used
Command run:
screengrab

Output:
....lots of unrelated stuff.....

$ adb devices -l
▸ List of devices attached
▸ adb server is out of date.  killing...
▸ * daemon started successfully *
▸ emulator-5554          device product:sdk_phone_x86_64 model:Android_SDK_built_for_x86_64 device:generic_x86_64
Multiple connected devices, selecting the first one
To specify which connected device to use, use the -s (specific_device) config option
$ adb -s adb shell echo \$EXTERNAL_STORAGE
▸ error: device 'adb' not found

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Not relevant to this issue.
Environment
fastlane version (run fastlane -v):
fastlane 1.104.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
No
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
No

@EricKuck Thanks for the commit. Can you create a PR around this so we can fix this? Thanks!

There is a PR already - #6286

#6286 has shipped as part of screengrab v0.5.3


Use mio v0.8 in examples

This PR updates the version of mio used in the examples from v0.6 to v0.8 (latest minor version).
After this change, I've confirmed that the http3-server and http3-client examples work as before:
$ cd quiche/
$ mkdir examples/root/
$ echo 'Hello World!' > examples/root/hello

// Server
$ cargo run --example http3-server

// Client (another shell)
$ cargo run --example http3-client https://<IP_ADDRESS>:4433/hello
Hello World!

Closes https://github.com/cloudflare/quiche/issues/1196

Merged, thanks @sile! By the way, the apps crate (https://github.com/cloudflare/quiche/tree/master/apps) also needs to be updated to mio v0.8 if you'd like to look at that as well.

Thank you for the quick merge!
I'm going to try updating the apps create as well when I have time.


Issue #3007: Fix search clone array corruption

Method-chaining in gorm is predicated on search's clone method
returning a copy of the search instance such that no change that
is made to the copy affects the original.
However, the original implementation copied the slices of the various
slice properties (such as whereConditions), with the incorrect
understanding that append would create a new slice each time that
it was called.  In some cases, this is true.  Practically, go
doubles the size of the slice once it gets full, so the following
slice append calls would result in a new slice:

0 -> 1
1 -> 2
2 -> 4
4 -> 8
and so on.

So, when the number of "where" conditions (or any other slice
property) was 0, 1, 2, or 4, method-chaining would work as expected.
However, when it was 3, 5, 6, or 7, modifying the copy would modify
the original.
The solution is simply to create new slices in clone.
Make sure these boxes checked before submitting your pull request.

[] Do only one thing
[] No API-breaking changes
[] New code/logic commented & tested

For significant changes like big bug fixes, new features, please open an issue to make an agreement on an implementation design/plan first before starting it.
What did this pull request do?

Anyone have any idea why wercker/build failed on mysql but it works fine if I run it locally?
$ GORM_DIALECT=mysql go test ./...
ok      github.com/jinzhu/gorm  47.597s
?       github.com/jinzhu/gorm/dialects/mssql   [no test files]
?       github.com/jinzhu/gorm/dialects/mysql   [no test files]
?       github.com/jinzhu/gorm/dialects/postgres        [no test files]
?       github.com/jinzhu/gorm/dialects/sqlite  [no test files]


Potential bug in run_mcmc of the 2.2.x branch

General information:

emcee version: 2.2.x

Problem description:
Reading the code for the Sampler class of version 2.2.x, I think I found a mistake at line 167 in sampler.py:
Shouldn't rstate0 be replaced with lnprob0 ?

Yes! You're absolutely right.


Host address configurable

Hard-coding the host address was a bit messy. I'm thinking of turning this into a list and cameras will be allocated to the available addresses in a rolling fashion. This way we can have N number of connections and distribute the load.

From what I understand it would actually be a list of server IPs right? To reduce future changes to the data structures and function definitions maybe we can already set it as a vector of length 1?

I'm going to leave this PR here for sake of size. I think the next step is adjusting the Ethernet Client to spawn threads for each socket and then allocate sockets on a rolling basis to send off messages. This starts entering scheduler territory so I think we should start with the simplest solution and improve from there. My first idea is to just block until a socket is available to send the message. The second is to establish a queue. My main concern with the queue is that we should replace the previous request if it is not served by the time that the primary thread rolls around again. This is highly unlikely but still quite possible if bandwidth is less than the flood gates.

I'm going to leave this PR here for sake of size. I think the next step is adjusting the Ethernet Client to spawn threads for each socket and then allocate sockets on a rolling basis to send off messages. This starts entering scheduler territory so I think we should start with the simplest solution and improve from there. My first idea is to just block until a socket is available to send the message. The second is to establish a queue. My main concern with the queue is that we should replace the previous request if it is not served by the time that the primary thread rolls around again. This is highly unlikely but still quite possible if bandwidth is less than the flood gates.

Would this mean that a camera could send an image to a socket in one iteration and another one in the following? I guess the server would use the header to know what to do with them?
My original idea was estimating the bandwidth needed by any camera through the camera parameters (width * height * bytes_per_pixel * fps) and using it to calculate how busy every socket is and assign probed cameras to the least busy socket. However, if this works it sounds like it might make a more efficient use of bandwidth.
I think it could still be interesting in the future to do the bandwidth estimation though, just to make sure there is no saturation of the links and to either warn the user or throttle the imagers if there is (for example if, in an extreme case, the imagers run at 60 fps but we only have bandwidth to send 15 fps and we have 4 framebuffers, we might end up sending half a new and half an old frame, so it might be good to warn the user and throttle the imager).
Anyway apart from the derailing this looks good to me.


trestle task should allow list without a valid trestle directory.

Describe the bug
trestle task -l requires you to be in a valid directory.
To Reproduce
Run trestle task -l and see an error for the fact it's not inside a trestle project.
Expected behavior
As a help function I would expect this to operate without a check for a trestle project setup.
Screenshots / Logs.
N.A.
Environment

trestle 3.3.0

A trestle command either requires a trestle root to be initialized (inheriting from CommandPlusDocs or not (CommandBase). The current task command inherits from CommandPlusDocs and requires root to be available for various tasks to be executed. I don't think just for one option "-l" the root can be avoided, unless we assume the task command itself does not require trestle root at all.


bat files

is it possible to run bat files??

At this time no but it has been mentioned before I think and it is on the to do list. I can run py files and they go to terminal, so I think a batch file could be similar.


Issue 10 Added map

This PR will close #10
Please, go through these steps before you submit a PR.

[X] My Pod Leader knows I'm working on this Pull Request
[X] I've explained what the Pull Request is adding.
[X] I've explained why this is important.
This PR is adding a map to the website portfolio and location of the fellows.

https://deploy-preview-31--mlh-prep-22-nov-prep-2-portfolio.netlify.app/

Yes, it is. We are still adding fellow info and making changes which Namita is going to raise a PR for tomorrow. This is just a PR for what we did so far.

Implemented feedback

There seems to be an existing PR for this issue. Please sync with @namitaarya and close one of the PRs/

You can ignore this one, and look into the other PR. This would be closed by Nora :)

There is another PR for this

Please, fix merge conflicts


Change in order

I've noticed that in my setup this code:
const addShopping = useMutation(gql(createProject), {
    variables: { input: {
      title: 'Shopping',
      color: '#607d8b',
      children: [],
      order: data.listProjects.items.length,
    }}
  });

Leads to error:
index.js:1446 Warning: React has detected a change in the order of Hooks called by ProjectList. This will lead to bugs and errors if not fixed. For more information, read the Rules of Hooks: https://fb.me/rules-of-hooks

   Previous render            Next render
   ------------------------------------------------------
1. useState                   useState
2. useContext                 useContext
3. useContext                 useContext
4. useMemo                    useMemo
5. useMemo                    useMemo
6. useState                   useState
7. useMemo                    useMemo
8. useEffect                  useEffect
9. useContext                 useContext
10. useRef                    useRef
11. useState                  useState
12. useEffect                 useEffect
13. undefined                 useContext
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

My bad, I didn't notice early return before the useMutation


Unit vector data from camera

The o3d3xx PCIC interface can return unit vector matrices related to camera calibration data, and depending the used IR frequency.
Those vector already includes intrinsic and extrinsic transformations that can be applied on distance image to obtain calibrated and eventually customized  cartesian 3D coordinates.
It would be important to access this vector matrix for some processing done on distance data only and to be able to compute totally or partially their 3D coordinates.

Unit Vector description
The unit vector matrix contains 3 values [ex, ey, ez] for each pixel, the data layout is [ex_1,ey_1,ez_1, ... ex_N, ey_N, ez_N], where N is the number of pixels. Multiplying a distance measurement by the appropriate component leads to the corresponding cartesian coordinate: [X_i, Y_i, Z_i] = D_i * [ex_i, ey_i ez_i]. The rotational component of the extrinsic calibration, specified by the user, is already applied to the unit vectors.
Data type: 32 bit float
Chunk Type
The chunk type used for the unit vector matrix is: 223
Chunk Header
The Unit Vector data is prefixed with a header. This header is called chunk header.

Offset
Name
Description
Size in bytes

0x0000
CHUNK_TYPE
Defines the type of the chunk. For each distinct chunk type a own type is defined.
4

0x0004
CHUNK_SIZE
Size of the whole image chunck in bytes.
4

0x0008
HEADER_SIZE
Number of bytes starting from 0x0000 until PIXEL_DATA
4

0x000C
HEADER_VERSION
Version number of the header
4

0x0010
IMAGE_WIDTH
Image width in pixel
4

0x0014
IMAGE_HEIGTH
Image height in pixel
4

0x0018
PIXEL_FORMAT
Pixel-Format
4

0x001C
TIME_STAMP
Timestamp in uS
4

0x0020
FRAME_COUNT
Frame count according to algorithm output
4

0x0024
PIXEL_DATA
The pixel data in the given type and dimension of the image.
-

Example Code
This is how the data is assembled on the camera
Currently supported Chunk Types
typedef enum ChunkType {
	CT_RADIAL_DISTANCE_IMAGE  = 100,
	CT_NORM_AMPLITUDE_IMAGE   = 101,
	CT_AMPLITUDE_IMAGE        = 103,
	CT_CARTESIAN_X_COMPONENT  = 200,
	CT_CARTESIAN_Y_COMPONENT  = 201,
	CT_CARTESIAN_Z_COMPONENT  = 202,
	CT_CARTESIAN_ALL          = 203,
	CT_UNIT_VECTOR_ALL        = 223,
	CT_CONFIDENCE_IMAGE       = 300,
	CT_DIAGNOSTIC             = 302,
	CT_EXTRINSIC_CALIBRATION  = 400,
	CT_JSON_MODEL             = 500,
	CT_SNAPSHOT_IMAGE         = 600,
	CT_MAX
} ChunkType_t;

Available pixel formats
typedef enum PixelFormat {
	PF_FORMAT_8U   =  0,
	PF_FORMAT_8S   =  1,
	PF_FORMAT_16U  =  2,
	PF_FORMAT_16S  =  3,
	PF_FORMAT_32U  =  4,
	PF_FORMAT_32S  =  5,
	PF_FORMAT_32F  =  6,
	PF_FORMAT_64U  =  7,
	PF_FORMAT_64F  =  8,
	PF_FORMAT_16U2 =  9,
	PF_FORMAT_32F3 = 10,
	PF_MAX
} PixelFormat_t;

chunkHeader.chunkType = ifm::CT_UNIT_VECTOR_ALL;
chunkHeader.chunkSize = sizeof(ifm::ChunkHeader) + result->width * result->height * 3 * sizeof(float);
chunkHeader.headerSize = sizeof(chunkHeader);
chunkHeader.headerVersion = 1;
chunkHeader.imageWidth = result->width;
chunkHeader.imageHeight = result->height;
chunkHeader.pixelFormat = ifm::PF_FORMAT_32F3; // [eX,eY,eZ] triple
chunkHeader.timestamp = result->timestamp;
chunkHeader.frameCount = getFrameCounter();

The unit vector provided by the latest official ifm firmware has a bug which makes them useless. This will be fixed in the firmware version 1.2.x

Great info. Thanks @graugans I think we need to think about the best way to deal with this in the library. While I completely appreciate the concerns of @semsitivity  there is certainly a whole host of use cases that will continue to want to have the Cartesian data constructed as a PCL point cloud as it is done now (i.e., not manually converting the depth image when needed). That said, I could imagine a few scenarios:

We provision for pluggable frame grabber implementations that would allow for flexibility in what we ask the camera to return to us.

The current frame grabber could be changed to let the JSON schema drive its parsing rather than exploiting a priori information as it does today. It follows then that we will allow for a mutator to be called so that the user can specify its desired JSON schema.

We allow for the caller to provide some kind of bitmask (or similar) denoting what images the frame grabber should populate in the ImageBuffer object.

Regardless of what we do, I think we should grab some performance metrics to ensure it is worth the effort. Given that the FrameGrabber is running in a separate thread from the user's algo code, the speed-ups (if any) may not be meaningful. I'm speculating and could only speak definitively to this once we capture some performance data. We should probably let the O3D303's on-board iMX6 be the ground truth architecture for which we grab this performance data as it seems there is consensus among many of us that, ideally, our algo code runs on the camera.
Related to this, I am currently planning (unless there are serious objections), of moving the xyzi_image that is currently being constructed in the o3d3xx-ros code into this library as well. It is basically a 4 channel OpenCV image encoding of the point cloud where the first three channels are spatial planes (x, y, z) and the fourth is the amplitude data. You can see that implementation here NOTE: the notion of numpy_cloud has been changed to a more general xyzi_image.  But the code is effectively the same. I think having this also addresses a concern of @semsitivity where (for example) an ROI can be defined in depth or amplitude space and similarly masked directly to the point cloud (i.e., the xyzi_image) since they are now all cv::Mat. I should also note that this will be in addition to the PCL point cloud that is also constructed. Again, I expect the overhead to be minimal as the construction of all the images happen concurrently (i.e., O(n) where n is the number of pixels on the active imager array).
@graugans Quick question since you mention the extrinsics in your note above... Does the O3D303 apply a rotation and translation to the image data based on the extrinsics configured via the JSON interface? I could figure this out empirically, but since you are here, I thought I'd be lazy and just ask :) FWIW, I like having the ability to store the extrinsics on the camera however, it would be nice to have a flag or switch to tell the camera whether or not you actually want it to perform the transform. For example, we have a current use case where we want to do all algo processing in the camera frame and then once we localize our object of interest we will simply transform the object pose based on the extrinsic calibration.

@tpanzarella  You can change the extrinsic calibration by a xml-rpc call to the following object:
http://<sensor-ip>/api/rpc/v1/com.ifm.efector/session_<session-id>/edit/device/
The following parameters are available:

ExtrinsicCalibRotX
ExtrinsicCalibRotY
ExtrinsicCalibRotZ
ExtrinsicCalibTransX
ExtrinsicCalibTransY
ExtrinsicCalibTransZ

There is no flag as far as I know, but you can store multiple configurations on the camera and switch between them. We call it application.

@graugans Right. I guess the question is, does this simply store the data or does the O3D303 firmware apply this transformation prior to returning the data over the socket interface?

@tpanzarella The extrinsic calibration is applied during calculation of x,y,z data.
BTW this plugabble framegrabber approach sounds interesting.

@graugans Thanks for the clarification of the extrinsics. As you note in an earlier comment, the effect I am looking for (i.e., storing the extrinsics on the camera while operating in the camera frame) can be achieved by having multiple applications loaded on the camera with different extrinsic calibration values (i.e., one with the real extrinsics and one with all zeros for the rot and trans).
Many thanks again Christian! This is good information to know.
I'll keep thinking about the FrameGrabber solution we have been discussing above. Do you have a current target date for the 1.2.x firmware? It sounds like we have until (at least) then to come up with a direction we'd like to go in to support the use case of @semsitivity

@tpanzarella Last week we did a feature freeze for the 1.2.x branch, but there is still some testing needed.
Frankly I am not involved in the official release process. My team and myself provide release candidates when those go online is the decision by the sales team. I guess by the end of October 1.2.x is released. Maybe I can provide the next test candidate for a beta test.

@tpanzarella, just a comment about the xyzi_image.
I read in the o3d3xx-ros code that you use a '''CV_32FC4''' opencv matrix. I guess that you consider the unit in meter here.
My feeling , and say me if you disagree, is that if we keep the unit in millimeter a '''CV_16UC4''' would be more suitable. For the reasons:

currently, soft-float is used on the board...so it's always some cpu saved by this.
the best camera accuracy is arround 4mm if I remember well, and of course more depending the range and the configuration.
maximum precision is of course better, but I'm not sure that it's really pertinent to use this format using twice the memory size and probably a bit time consuming for the cpu for so few real information in the data.
Concerning the point cloud format, keeping it in meter with double seems to be a good choice, but in opencv world, I think that unsigned short is closer to reality, even if unit vector are given as float or double.
What do you think?

@semsitivity Your point on keeping the xyzi_image in mm is well taken and works for me too (especially if we keep the point cloud in meters). I don't think we have too many users of the xyzi_image in the ROS code yet, so, I am not concerned with backward compatibility. I'll just be sure to clearly note this change in the documentation and changelog.
I will work this change into the next release of the code. Tentatively, I'm shooting for next week. I am bogged down with lots of other stuff this week and early next week, but I'll have time to update both libo3d3xx and o3d3xx-ros to reflect this (and other) changes.
Thanks for the comment and technical rationale for this request.

@semsitivity The camera is using hardware floating point. But we do use the softfp ABI. We are planning to switch to hardfp  by the end of the year. The main purpose for using unsigned int 16 for the data is to save Ethernet bandwidth. Internally everything is calculated in float precision. We started with  softfp because there was hardfp GPU userland.

@tpanzarella After digging deeper into the whole extrinsic and unit vector business I realized that I made a big mistake and claimed the extrinsic calibration is a application specific parameter. It is not!
http://<sensor-ip>/api/rpc/v1/com.ifm.efector/session_<session-id>/edit/device/ <-- device !!!

The whole idea of extrinsic calibration was for a fixed mounting of the Camera.
Anyway I started some internal discussion if it make sense to have such an flag. If there is more benefit for such an flag let me know.
Sorry for my misleading assumption about the extrinsic calibration.

No worries Christian. In fact, I am a bit embarrassed that I did not catch that. It is clear that the extrinsics are configured at the device level as indicated by the JSON serialization. For example this. Thanks for the explicit clarification anyway.
In terms of the flag to either apply or not apply the extrinsic transformation, my request is motivated by three concrete concerns:

As you know, the libo3d3xx coordinate frame is not consistent with the O3D303 returned coordinate frame. That said, inspecting the stored extrinsics on the camera would be highly unintuitive to someone using libo3d3xx as they would have to mentally remap the coordinate system in their head while debugging, etc. I believe this would lead to a lot of unnecessarily wasted engineering cycles by many (very smart) people simply due to a misunderstanding. That said, if there were a flag that determined if the transformation were applied or not, those using libo3d3xx could store the extrinsics according to the libo3d3xx coord frame and simply apply the transform manually once getting the point cloud returned to them in the camera frame. Conversely, for those using the built-in O3D303 coord frame, they could set the flag to apply the extrinsics as is if it makes sense for their application. Effectively this decouples the stored parameters from the coordinate system that is in place for the application.

I think it is really useful to be able to store the extrinsics close to the camera and there isn't much closer than directly on the camera. This gets even more valuable for multi-camera systems where you are managing a fleet of n-cameras each with their own unique extrinsic calibration. Now, just because you have an extrinsic calibration in place does not necessarily mean you want to run your vision algorithm in that coord frame. For example, we have a concrete object recognition use case where we want to do all processing in the camera frame, then once we segment out our object of interest, we need to return its pose transformed via the extrinsics. So, we want the camera data in the camera frame, then to be able to query the camera for the extrinsic calibration, and manually transform the final pose to the parent frame.

From a practical engineering perspective, many of our applications involve embedded linux systems where we highly prefer to configure the system to run with a read-only file system to avoid any corruption -- we typically provide a very small read/write filesystem for logging or whatever (sometimes just a block of volatile memory -- e.g., tmpfs or similar). That said, it would be super convenient to be able to store in persistent memory the extrinsics of the camera and since the O3D303 already provides a facility for doing so, we would just exploit that. Again, I realize that this is sort of minutia but it is a real practical concern and of high value to have this option.

In summary, I hope the above three examples help further motivate real-world concerns for: 1) keeping the ability to store the extrinsics on the camera, but, 2) provide a boolean flag to indicate whether or not you actually want the transformation applied by the O3D firmware.
Let me know if anything is unclear.

This is not an anwser, but just a remark for @graugans and the information he gave about the extrinsic.
The extrinsic are at the device level, yes, and they are not in deg, but in rad.
The translations unit is in meter.
Thanks to o3d3xx-config, @tpanzarella 's help on how to use it, I finally figured it out.

@semsitivity , @tpanzarella Yes, at the moment the values are in m and rad. But this is more a bug than an intended feature. We are discussing this internally, because the general camera interface is mm and degrees we may fix this in a next release. And we are preparing some sort of application note how to deal with the extrinsic calibration and the unit vectors. There are some points to pay attention off. I hope you can wait a couple of days until we can provide a pre release of the application note to you.

@tpanzarella , my target was to be able to adapt my algorithm to the device for the end of the month.
The first step is obviously the image capture which is was blocking problem, and even if it will change really soon, I'm happy to be able to go on on my next development steps.
So don't hesitate to be clear on next release changed, and I'll adapt my code.
Today, I have this sequence working great:

Set up camera application settings for a good quality/precision image
capture a single image
detect floor normal vector and needed transformation to align points with the floor
set other camera settings for a long run at 10fps with less precision to take care about temperature
set extrinsic values to camera with those needed transformation
start image capture loop and all my detection stuff, starting from floor oriented cartesian coordinates

I'm happy because, previously, I was applying my self all the transformation. Now I obtain what I was expecting: less CPU consumption + a simplified algorithm, and that's great.

@graugans Thanks. Take the time you need to sort this out. Speaking for LPR, we can wait until you are ready.


HBASE-26567 Remove IndexType from ChunkCreator

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  8s
Docker mode activated.

Please resolve the conflicts? And also fix the javadoc issue?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  3s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 18s
the patch passed

+1 :green_heart:
compile
3m 25s
the patch passed

-0 :warning:
javac
3m 25s
hbase-server generated 1 new + 192 unchanged - 1 fixed = 193 total (was 193)

+1 :green_heart:
checkstyle
1m 12s
hbase-server: The patch generated 0 new + 10 unchanged - 2 fixed = 10 total (was 12)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
21m 34s
Patch does not cause any errors with Hadoop 3.1.2 3.2.2 3.3.1.

+1 :green_heart:
spotbugs
2m 24s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

54m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3947

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 8e49d2aba873 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e96df8bf40

Default Java
AdoptOpenJDK-1.8.0_282-b08

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/artifact/yetus-general-check/output/diff-compile-javac-hbase-server.txt

Max. process+thread count
86 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@Apache9 , thank you for view, fixed the conflict and the javadoc issue

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 33s
master passed

+1 :green_heart:
compile
1m 16s
master passed

+1 :green_heart:
shadedjars
8m 30s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
master passed

-0 :warning:
patch
9m 25s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 31s
the patch passed

+1 :green_heart:
compile
1m 14s
the patch passed

+1 :green_heart:
javac
1m 14s
the patch passed

+1 :green_heart:
shadedjars
8m 15s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

-1 :x:
unit
138m 40s
hbase-server in the patch failed.

171m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3947

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux c6bed785e487 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e96df8bf40

Default Java
AdoptOpenJDK-11.0.10+9

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/testReport/

Max. process+thread count
3559 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 51s
master passed

+1 :green_heart:
compile
1m  5s
master passed

+1 :green_heart:
shadedjars
8m 19s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
master passed

-0 :warning:
patch
9m 10s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 57s
the patch passed

+1 :green_heart:
compile
1m  5s
the patch passed

+1 :green_heart:
javac
1m  5s
the patch passed

+1 :green_heart:
shadedjars
8m 10s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 38s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
151m 53s
hbase-server in the patch passed.

182m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3947

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 895800bf92a1 4.15.0-161-generic #169-Ubuntu SMP Fri Oct 15 13:41:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e96df8bf40

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/testReport/

Max. process+thread count
3704 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3947/6/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Now detecting DC/OS version using on-disk file

Each DC/OS node has a file at location: /opt/mesosphere/active/dcos-metadata/etc/dcos-version.json. Use this file to determine DC/OS version, and do so in best-effort fashion.

@nickbp It doesn't fall back to HTTP. In fact the HTTP endpoint in context, basically just serves the contents of this file from disk. This file is basically present on all DC/OS nodes.
Are you saying that this file did not exist on all hosts pre 1.8 ?
Also, if this file is not found then the library gives up all hopes on determining DC/OS version and any version based capability detection logic return false.

@mesosphere-ci retest this please.

I didn't know either way, just wanted to check that the new system would work for all 1.7+. From offline discussion it sounds like we're good.

Closing this in favor of https://github.com/mesosphere/dcos-commons/pull/238. Once the certificate is installed in the JRE, the existing version detection logic works just fine.


Footer content must be in center

The copyright content must be in the centre of the page.
It makes it more good looking.

Is it still open or solved?


Added support for Wada Energy Q8 EV charger

Preliminary support for Wada Energy Q8 EV charger.

Start/stop charge, set charge current are working
Actual charging power sensor is working
Missing phase current and voltage data
Missing support for time based charge

Your product id looks like a device id. These are separate things, the product id is common to all devices of that product, your device id is unique to your device.

thanks. It should be the right one now. Marked the pull request as draft as I have to make some tests.


Update Invoke-CMApplyDriverPackage.ps1

Hi,
I did some modifications:

If using demo mode you can also use get-credentials
Fallback to a different OS Name when no Windows 11 driver exists
Fallback to a lower OS version
Save downloaded and applied driver package in the registry to skip it in case the powershell runs again
Added error handling like recommended: https://github.com/MSEndpointMgr/ModernDriverManagement/issues/156

Hi, I did some modifications:

If using demo mode you can also use get-credentials
Fallback to a different OS Name when no Windows 11 driver exists
Fallback to a lower OS version
Save downloaded and applied driver package in the registry to skip it in case the powershell runs again
Added error handling like recommended: v4.2 Bad error reporting #156

Hi,
How did you setup the OS Name fallback? Didn't work "out of the box" for me, so was wondering if I had to add a parameter when invoking the script or such?
Br
Samuel

Just added 23H2:
https://github.com/stephannn/ModernDriverManagement/blob/master/Invoke-CMApplyDriverPackage_4.2.1_woOSVersion_4.ps1
I call the fallback like that:
Invoke-CMApplyDriverPackage_4.2.1_woOSVersion_4.ps1
-DriverUpdate -Endpoint "Server.FQDN" -RegistryValueDriverInstalled $true -PerformReboot $false -TargetOSName 'Windows 11' -TargetOSVersion "23H2" -OSVersionFallback -TargetOSNameIgnore $true -TargetOSVersionLatest $true

This is phenomenal. Nice work on this!


Added CMORizer for JMA-TRANSCOM

Added CMORizer for JMA-TRANSCOM for the variables nbp and fgco2.

[x] Create an issue to discuss what you are going to do, if you haven't done so already (and add the link at the bottom)
[x] Give this pull request a descriptive title that can be used as a one line summary in a changelog
[x] Make sure your code is composed of functions of no more than 50 lines and uses meaningful names for variables
[x] Circle/CI tests pass. Status can be seen below your pull request. If the tests are failing, click the link to find out why.
[x] Preferably Codacy code quality checks pass, however a few remaining hard to solve Codacy issues are still acceptable. Status can be seen below your pull request. If there is an error, click the link to find out why. If you suspect Codacy may be wrong, please ask by commenting.
[x] Please use yamllint to check that your YAML files do not contain mistakes
[x] (Only if really necessary) Add any additional dependencies needed for the diagnostic script to setup.py, esmvaltool/install/R/r_requirements.txt or esmvaltool/install/Julia/julia_requirements.txt (depending on the language of your script) and also to meta.yaml for conda dependencies (includes Python and others, but not R/Julia)
[x] If new dependencies are introduced, check that the license is compatible with Apache2.0

New data reformatting script

[x] Test the CMORized data using recipes/example/recipe_check_obs.yml, to make sure the CMOR checks pass without errors
[x] Add the new dataset to the table in the documentation
[x] Tag @mattiarighi in this pull request, so that the new dataset can be added to the OBS data pool at DKRZ and synchronized with CEDA-Jasmin

Task of #473.

Is the codacy issue solvable?

I don't think so, I'm not even sure why it is complaining at all.


No need to explicitly return None value

Description
No need to explicitly return None value which is more idiomatic in this code.
Python implicitly assumes return None if an explicit return value is
omitted. Therefore, explicitly returning None is redundant and should be
avoided when it is the only possible return value across all code paths
in a given function.
Type of change

[x] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (bd4265b) 96.09% compared to head (7bc527b) 70.82%.
Report is 28 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #437       +/-   ##
===========================================
- Coverage   96.09%   70.82%   -25.27%
===========================================
  Files          32       32
  Lines        1075     1090       +15
===========================================
- Hits         1033      772      -261
- Misses         42      318      +276

Files
Coverage Δ

ols/app/endpoints/health.py
100.00% <100.00%> (ø)

... and 14 files with indirect coverage changes

/retest

/lgtm

/approve


[Bug?] serviceCollection.AddMapster(); is missing -- v. 7.3.0

Hello all!
I am unsure if this is a bug, or a caching issue.. As you can see, I have installed:

Mapster: 7.3.0
Mapster.DependencyInjection: 1.0.0

I try and perform services.AddMapster(); and it is 'not found.  Please look at my using statements and set-up.

I have restarted Rider a few times in attempt to clear the package cache, incase it is a cache issue, and the issue persists.
Strangely - I can add the dependency manually like: services.AddTransient<IMapper, Mapper>(); and it works fine.
See here:

Here is my .csproj file:

Note: Riok.Mapperly and MapTo are other mapping libraries I was testing out.
I then proceeded to debug by installing the 'pre-release' versions of Mapster, the issue still persisted:

Is this a bug? How can I help you debug this.
Thanks all

AddMapster() is scheduled for the upcoming v7.4.0. I think it should be available in the latest prerelease package though.

Sounds good thanks!

I might be missing something, but v.7.4.0 doesn't seem to have it either now. :\

I might be missing something, but v.7.4.0 doesn't seem to have it either now. :\

I can't use it too


Change is triggered when a palette color is clicked

The docs say change is triggered when the user clicks Choose, but change is triggered on click of every palette color. This would be fine if it triggered change to the reverted color when the user clicks Cancel.
http://jsfiddle.net/ctkY3/3915/

This is fixed in master by #405.  Please let me know if it isn't working as you expect.


Colab Version of GPT-SoVits2

i want to know if you had plan for GPT-SoVITS2 webui will also available on Google Colab when released. also will it support Indonesian Language? and how to train the voice model with this GPT-SoVITS2? Thanks

I'm not a developer, but I'll try to help you out:
1- I'm not sure if it will be available on Google Colab, but most likely.
2- If you carefully read README.md, you will find this line: Native support for multiple languages: Not limited to Chinese, Japanese, and English, but supports any language in the world.
3- GPT-SoVITS2 has not been released yet, but I believe the training method will be similar to that of the original GPT-SoVITS repository.


Can't deploy your project

Hey,
First of all, thanks for the template,
It really helped me understand things out with IdentityServer and ASPNetCORE + Angular.
I'm facing an issue when trying to deploy to Azure Web App,
I'm getting error 500, and in the Web App logs I see that it cannot find the index.htm, and therefore it throws the error 500.
Did anyone else faced the same issue?
Maybe you've got a solution?

@yakeer Try to verify these settings to serving static files in production:

https://github.com/robisim74/AngularSPAWebAPI/blob/master/ClientApp/angular.json#L20-L21
https://github.com/robisim74/AngularSPAWebAPI/blob/master/Startup.cs#L110-L120
https://github.com/robisim74/AngularSPAWebAPI/blob/master/Startup.cs#L141-L150

@yakeer Did you solve your problem? This project is currently deployed on Azure without any error.


this solution pass all the text but it is wrong. Add the case [1,2,3,1] [4,5,6]. Since there are 2 item with value 1, this solution will not add 1 in the final array. It should to be correct!

Challenge Diff Two Arrays has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
function diff(arr1, arr2) {
  var newArr = [];

  newArr = arr1.concat(arr2);
  console.log("arr total is: ",newArr);

  //count occurence of item in array
  //return number of occurrence > 0
  var count = function(item, array){
    var count = 0;
    var i=0;
    for (i ; i<array.length; i++){

      if (array[i] == item){
        count++;
      }
    }

    console.log("This item: "+item+" appears: "+ count+" times!");
    return count;
  };

 arr = [];

 var  y=0;
  var restOfArr = newArr.slice(0);

  for (y; y<newArr.length;  y++){
     if (restOfArr.length == 0){
     console.log("EMPTY. RES IS: ", arr);
     return arr;
   }
    //console.log("index is: ", y);
    var item = restOfArr[0];
    console.log("item is: ", item);
    restOfArr = restOfArr.slice(1);

    var counter = count(item, restOfArr);

    if (counter == 0){
      arr.push(item);
      restOfArr = restOfArr.filter(function(el){
        return el !== item;

     // console.log("after delete item restOfArr is: ", restOfArr);
    });
    }
    if (counter > 0){
      //ce ne sono 2 non addo
      restOfArr = restOfArr.filter(function(el){
        return el !== item;

    });
    }
    console.log("rest of arr: ", restOfArr);

   // console.log("FOR: arr is: "+arr+" newArr is: "+newArr);

  }

  return arr;
}

diff([1, 2, 3, 5], [1, 2, 3, 4, 5]);

I am also having an issue with this - my code is passing the challenges but they are not becoming green.
Code below:
`function diff(arr1, arr2) {
var newArr = [];
// Same, same; but different.
newArr = arr1.concat(arr2);
newArr.sort();
var ans = [];
var i = 1;
for (i=1; i<newArr.length; i++) {
if (newArr[i] !== newArr[i+1] && newArr[i] !== newArr[i-1] ) {
ans.push(newArr[i]);
}
}
return ans.sort();
}
diff(["diorite", "andesite", "grass", "dirt", "pink wool", "dead shrub"], ["diorite", "andesite", "grass", "dirt", "dead shrub"]);`

@ninjasun thanks for the issue but I don't think it is necessary to add a test with duplicate elements in one array. This challenge IMO is on testing you to implement symmetric differences, which is actually a method on (mathematical) sets, which don't have duplicates. @SaintPeter thoughts?
@vaspv your code isn't working because we have been updating function names recently. Change your function diff to diffArray and then you should start seeing some checkmarks.

Thanks Eric, working now.

I tried to pass different values in the array and it is working, but I am not able to clear this challenge.
If I am doing something wrong, any help would be appreciated.
I know there may be better ways of solving this particular challenge but right now I'm interested in what am I missing? or is it some kind of a bug?
function diff(arr1, arr2) {
  var newArr = [];
  // Same, same; but different.
 for (var i = 0;i<arr1.length;i++) {
   if(arr2.indexOf(arr1[i]) === -1) {
     newArr.push(arr1[i]);
   }
 }
  for(var j=0;j<arr2.length;j++) {
    if(arr1.indexOf(arr2[j]) === -1) {
      newArr.push(arr2[j]);
    }
  }
  return newArr;
}

diff(["diorite", "andesite", "grass", "dirt", "pink wool", "dead shrub"], ["diorite", "andesite", "grass", "dirt", "dead shrub"]);

Hi as per Eric above  - Change your function diff to diffArray and then you should start seeing some checkmarks.

Ok it worked, although it din't make any sense.

@erictleung For this earlier bonfire I don't know that we need to have corner cases like duplicate elements in one array.

@erictleung I think duplicates would be good, it would allow a user to discover that these are to be treated like sets. Also, it doesn't really make sense to think of them as sets, since arrays impose ordering, and I thought the ordering was significant, which is where the difficulty came in. If a user thinks ordering matters, it seems like it will follow a levenshtein style of solution, which makes it unnecessarily complicated. Another option would be to describe it in more accessible language like "Return the elements in only the first array followed by the elements in only the second"

I'd advocate these tests:
// the element in array 2 fulfills every element in array 1
diffArray([1, 1], [1]); // => []

// order doesn't matter, like a set
diffArray([1, 2], [2, 1]); // => []

// comparison does not get confused by types (eg I put them in as object keys to cache lookup, but that casts them to strings, so my solution was wrong)
diffArray([1], ['1']); // => [1, '1']


enhanceuse version instead of timestamp

Proposed changes
Issue Number: close #xxx
MTMV records snapshot information for each refresh of data, used to compare whether partitions need to be updated
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


Fatal bug: mods conflicts

In version 0.1.0, there is a known bug: it conflicts with architectury.
We'll fix this bug in next version, 0.2.0.

Is 0.2.0 going to be put up on curseforge? architectury is pretty hard to avoid in a big fabric modpack.

Is 0.2.0 going to be put up on curseforge? architectury is pretty hard to avoid in a big fabric modpack.

OK, 0.2.0 has been published.


docs(main): add steps for static deployment to Edgio

Thanks for the PR @rishi-raj-jain, but we are trying to minimize the services we have instructions for in these docs in favor of letting each platform document how to deploy Vite projects. It is a lot easier to maintain if you are the one in charge of these docs.
Thanks for understanding, and we hope to see a Vite section on your side.

@patak-dev Thanks for the quick response, would it be possible to add a single line of reference to our docs?

We don't yet have a resolution regarding this between the team. We'll discuss it when we get a chance, but it may also have a maintenance cost (in case you change your docs for example) without much gain because everyone should be able to find the section by searching "vite edgio"


Option --file or -f to include additional files

Add option --file or -f to include additional files from command line

Option changed to --include/-I


Fix accessibility issue #9165 on color contrast ratio

References

https://github.com/github/accessibility-audits/issues/9165

What
This pull request includes change to the src/theme.js file to fix an accessibility issue related to color contrast ratio between npm link text #cb0000 and surrounding text #1f2328
Why
If the link has no distinct style (such as underline) and luminosity contrast of the link has insufficient contrast ratio with the surrounding text. As a result, users with low vision who experience low contrast cannot detect visually that the text is intended to function as a link.
Accessibility improvements:

src/theme.js: Changed the color text of npm link from #cb0000 to #cf2b2b to meet the minimum contrast 3:1 suggested by color contrast checker

Please use #cb3837 instead. This one can be used for the logo as well.

spot check and links are now color: rgb(203, 56, 55);


Fix Azure App Configuration subscribePollInterval to be Go Time format and not nanoseconds

This issue was raised in the docs repo https://github.com/dapr/docs/pull/3595 to provide polling interval in nanoseconds. However everywhere else we have used Go Time format which is what the docs currently have.

Closing as a duplicate of https://github.com/dapr/components-contrib/issues/2976


[BUG] exclusiveMinimum not handled correctly

Example
Here's a self-contained, minimal, reproducible, example with my use case:

from fastapi import FastAPI, Query

app = FastAPI()

@app.get('/')
def root(number: int = Query(..., gt=0)):
    return {"Hello": "World"}

Description
Setting gt=0 (docs) produces a openapi schema with "exclusiveMinimum": 0.0 for that parameter.
According to openapi  (see "Minimum and Maximum") this field has to be a boolean and present together with the minimum field.
Setting both, gt and ge, doesn't work although that should be the correct way. gt should also be a boolean instead of float.
(Most likely same for lt/le)
Environment

OS: Windows 10
FastAPI Version 0.60.1
Python version: 3.8

Refer to #240

Thanks for the help here @rkbeatss ! :clap: :bow:
Thanks for reporting back and closing the issue :+1:


Problem with the DataSourceSelector and the FieldSelector

I'm trying to use the DataSourceSelector and the FieldSelector for a widget and it doesn't seem to work correctly for multiple data sources and fields. Here are the initial settings in the "setting.tsx" file :

              <DataSourceSelector

                disableAddData={true}
                types={this.supportedTypes}
                useDataSources={this.props.useDataSources}
                useDataSourcesEnabled={this.props.useDataSourcesEnabled}
                onToggleUseDataEnabled={this.onToggleUseDataEnabled}
                onChange={this.onDataSourceChange}
                mustUseDataSource={true}
                widgetId={this.props.id}
                isMultiple={true}

              />
              {
                this.props.useDataSources && this.props.useDataSources.length > 0 &&

                    <FieldSelector
                      placeHolder={'Sélectionner les champs'}
                      useDropdown={false}
                      useDataSources={this.props.useDataSources}
                      onChange={this.onFieldChange}
                      isMultiple={true}
                      selectedFields={this.getSelectedFields() || Immutable([])}
                    />

              }

Here are some of the functions that interact with the DataSource and the FieldSelector:
  onFieldChange = (allSelectedFields: IMFieldSchema[], ds: DataSource) => {
    let newDS: UseDataSource[] = [];
    let useDS = this.props.useDataSources;
    useDS.forEach((item) => {
      let estDataSourceCourant = item.dataSourceId === ds.id;
      let fields: string[];
      if (estDataSourceCourant) {
        fields = allSelectedFields.map(f => f.jimuName);
      }
      else {
        fields = [];
        item.fields?.forEach(f => {
          fields.push(f);
        });
      }
      let newItem: UseDataSource = { dataSourceId: item.dataSourceId, dataViewId: item.dataViewId, fields: fields, mainDataSourceId: item.mainDataSourceId, rootDataSourceId: item.rootDataSourceId };

      newDS.push(newItem);
    })
    const newDSSort: UseDataSource[] = [];
    const firstDS = newDS.find(d => d.dataSourceId === ds.id);
    if (firstDS) {
      newDSSort.push(firstDS);
    }

    newDS.sort((a, b) => a.dataSourceId.localeCompare(b.dataSourceId)).filter(d => d.dataSourceId !== ds.id).forEach(ds => {
      newDSSort.push(ds);
    });

    this.props.onSettingChange({
      id: this.props.id,
      useDataSources: newDSSort
    })
  }

 getSelectedFields = () => {
    let selectedFields: { [dataSourceId: string]: string[] } = {};
    this.props.useDataSources.forEach((item) => {
      let fields: string[] = [];
      item.fields?.forEach(f => {
        fields.push(f);
      })
      selectedFields[item.dataSourceId] = fields;
    })

    return Immutable(selectedFields);
  }

What I'm trying to do is a widget where I can choose multiple DataSources and for each DataSource, I want to select some fields. The problem that I have is when I select some fields for a DataSource and then I select another DataSource to change the fields, the fields for the first DataSource are reset. Here's an example:
Here I selected some field for a DataSource and then I switch to another DataSource by using the dropdown.

Then I select a field in the other DataSource and I switch back to the first DataSource.

Now all the fields that I selected are unselected except for the ObjectId. The problem is that when I use the dropdown to change the DataSource, the onFieldChange function is executed at the same time but with the wrong fields passed in parameter. I tried to find why and I found that the problem was in the "data-source-selector.js" file. In the " n.onSelectedUseDsChange" function, the value of selectedDs is changed by calling setState. However, when the function calls "n.getSelectedFields", the value of "n.state.selectedDs" is used as a parameter but it still has the old value assigned to it. The function then returns the wrong fields and they are passed to the "n.props.onChange" function. That's why the wrong fields are passed in parameters in my  "onFieldChange" function.

I did a pretty-print of the file in "client/dist/jimu-ui/advanced/data-source-selector.js"and I tried to fix the problem by modifying it by changing the first parameter in the call to "getSelectedFields" in the "n.onSelectedUseDsChange" function. I then replaced the file with the new version that I created. After doing that, it started to work correctly.

Hi, do you have a specific issue or question with one of the sample widgets that are in this repository (https://github.com/Esri/arcgis-experience-builder-sdk-resources/tree/master/samples/widgets)? If not, the best place to ask more general Experience Builder questions in GeoNet: https://community.esri.com/t5/arcgis-experience-builder/ct-p/arcgis-experience-builder

No sorry, my issueis related to the DataSourceSelector. I will try to ask my question in the esri community.


Hidden Component

THe Hidden component was removed or missing?
Attempted import error: 'Hidden' is not exported from '@material-ui/core'.

Hidden supports certain usecases in a cleaner fashion than the sx property
https://github.com/mui-org/material-ui/issues/26408


FreeBSD docker image has headers and libs in wrong place

Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
headers are installed in $SYSROOT/include, when the compiler wants then in $SYSROOT/usr/include (and the same happens for lib).
If we passthrough BINDGEN_EXTRA_CLANG_ARGS_x86_64_unknown_freebsd="--sysroot=/usr/local/x86_64-unknown-freebsd12 -v" we can see things like:
  --- stderr
  clang version 10.0.0-4ubuntu1
  Target: x86_64-unknown-freebsd
  Thread model: posix
  InstalledDir:
  #include "..." search starts here:
  #include <...> search starts here:
   /usr/lib/llvm-10/lib/clang/10.0.0/include
   /usr/local/x86_64-unknown-freebsd12/usr/include
  End of search list.
  /usr/local/x86_64-unknown-freebsd12/usr/include/xenstore_lib.h:25:10: fatal error: 'errno.h' file not found

Workaround: start the pre-build hook with
mkdir -p /usr/local/x86_64-unknown-freebsd12/usr &&
ln -s ../include /usr/local/x86_64-unknown-freebsd12/usr/include &&
ln -s ../lib /usr/local/x86_64-unknown-freebsd12/usr/lib &&

What target(s) are you cross-compiling for?
x86_64-unknown-freebsd
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[ ] Windows
[X] Linux / BSD
[ ] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[X] docker
[ ] podman
[ ] other container engine (specify in description)

cross version
cross 0.2.5 (44011c8 2023-10-23)   [note: that's master not 0.2.5]
Example
No response
Additional information / notes
No response

there is also a problem with the BINDGEN_EXTRA_CLANG_ARGS_* for other targets, will have to identify those.
Specifically, I think targets returned by grep -L "ENV CROSS_SYSROOT=/usr/local/" --include='Dockerfile.*' -r ./docker need to be checked

fixed with #1403


induction-induction and induction-recursion

@mikeshulman would like to have induction-recursion and induction-induction in Lean.

This will not be supported in the near future.


feat: add ypm_debug script

Related issue # (if applicable): adds in the ypm debugger script to utils and a make file to use it, set env BAD and optionally BLOCK .
What I did:
How I did it:
How to verify it:
Checklist:

[ ] I have tested it locally and it works
[ ] I have included any relevant documentation for the repo maintainers
[ ] (If fixing a bug) I have added a test to the test suite to test for this particular bug

Adding a Network
If the purpose of your PR is to add support for a new network, please copy the checklist from here into this PR conversation, and use it to track your changes.

lgtm


Improve output of failed tests

Fixes codewars/runner#235.
Changed two types of output events:

Failing assertions
Errors outside of it block

With new reporter:

Original reporter:

No reporter:

Added support for newlines in titles:


Error creating S3 bucket: TooManyBuckets

Hello,
I'm receiving an error when using your module,
Error: Error creating S3 bucket: TooManyBuckets: You have attempted to create more buckets than allowed
	status code: 400, request id: 89C5F67086889131, host id: wPdV165nEmLi92mhhOCI9nHNt+jUk+zjIFTMbv/Se08jx9y/YJa9S1VRigzKN/0h81bgiCXr8M4=

Error: Error creating S3 bucket: TooManyBuckets: You have attempted to create more buckets than allowed
	status code: 400, request id: 4B5FF648E1B79D5F, host id: lbtIJiUVxVAspB1El4JxvFOz4IXHc4hmnxVUy4OCFmibrrjkjnlEoqIS0DQJmsggJD+9wUOw3DE=

Error: Error creating S3 bucket: TooManyBuckets: You have attempted to create more buckets than allowed
	status code: 400, request id: 1DC100A1565DABF8, host id: dH5aVMqbDQE9MnVMXpK9RzMjGTuJPF7CJXoduXUVrgKDQjq3O8RN5zotxCWISlhLdQSzYAgRx/A=

My TF file is the following,
provider "aws" {
  version = "~> 3.0"
  region = "us-east-1"
}

module "lambdas" {
  source  = "dealmore/next-js/aws"

  deployment_name = "test-app-sandbox"
  create_domain_name_records = false
}

I've followed the following steps,

terraform init
yarn tf-next
terraform plan
terraform apply

Not sure if I'm doing something wrong and any help is appreciated!  Thank you in advance!

Hi,
your configuration seems fine.
I would say that the message comes from the underlying AWS SDK that you cannot create any more S3 buckets because that would exceed the limit of 100 per account.
This module creates 3 new S3 buckets in your account so you should have a maximum of 97 buckets already in your account.
(You can always ask the AWS support for an increase to 1000 buckets per account).
Can you confirm that you have 97 or less buckets already in your account (So that creating 3 more buckets would not exceed the 100 limit)?
Anyway, we'll give the readme an update soon to list the number of each resource the module is creating.

Hey @ofhouse - thanks for the quick response!
Yeah, wow our account is over 100 buckets - I've requested an increase.  Thanks for the help!