Attempting to spread InputLabelProps on InputLabel with component set to legend give TS error

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
https://codesandbox.io/s/intelligent-payne-uh9i76?file=/src/App.tsx
Steps:

Open the example and see the Typescript error

Current behavior 😯
When I add the component="legend" onto an InputLabel and then try to spread InputLabelProps onto the component I get a typescript error related to differences in properties of HTMLLabelElement vs HTMLLegendElement
Expected behavior 🤔
I should not get a typescript error. Or maybe I can add a generic for HTMLLegendElement to the InputLabelProps somehow make typescript happy.
Although honestly, it seems like the type should be built to switch the underlying element based on component.
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
  System:
    OS: macOS 13.2.1
  Binaries:
    Node: 18.14.2 - ~/.nvm/versions/node/v18.14.2/bin/node
    Yarn: Not Found
    npm: 9.5.0 - ~/.nvm/versions/node/v18.14.2/bin/npm
  Browsers:
    Chrome: 111.0.5563.110
    Edge: Not Found
    Firefox: 111.0.1
    Safari: 16.3
  npmPackages:
    @emotion/react: ^11.10.6 => 11.10.6
    @emotion/styled: ^11.10.6 => 11.10.6
    @mui/base:  5.0.0-alpha.122
    @mui/core-downloads-tracker:  5.11.14
    @mui/icons-material: ^5.11.11 => 5.11.11
    @mui/material: ^5.11.14 => 5.11.14
    @mui/private-theming:  5.11.13
    @mui/styled-engine:  5.11.11
    @mui/system:  5.11.14
    @mui/types:  7.2.3
    @mui/utils: ^5.11.13 => 5.11.13
    @mui/x-date-pickers: ^6.0.3 => 6.0.3
    @types/react: 17.0.53 => 17.0.53
    react: 17.0.2 => 17.0.2
    react-dom: 17.0.2 => 17.0.2
    typescript: 4.9.5 => 4.9.5

Also, would you like me to fix and make a pull request for this issue? Thanks.

Correct your default assignment on line 14 to:
function Component(InputLabelProps:ComponentProps = {}) {

Put the type annotation before the assignment, not after.
Remove the curly braces surrounding the parameter.

Thanks for the corrections. Those are little details and my example is a bare bones one. And it overall doesn't affect the issue I'm having.

Also, would you like me to fix and make a pull request for this issue? Thanks.

If you are willing to fix it, I'd love to have the issue resolved. Thank you

Correct your default assignment on line 14 to:
function Component(InputLabelProps:ComponentProps = {}) {

Put the type annotation before the assignment, not after.
Remove the curly braces surrounding the parameter.

Thanks for the corrections. Those are little details and my example is a bare bones one. And it overall doesn't affect the issue I'm having.

You're welcome. A union type of the InputLabelProps and native HTMLLegendElement types may be what you are looking for on line 11, to make cases that use either type valid.
interface ComponentProps {
  InputLabelProps?: InputLabelProps | HTMLLegendElement;
}

You're welcome. A union type of the InputLabelProps and native HTMLLegendElement types may be what you are looking for on line 11, to make cases that use either type valid.
interface ComponentProps {
  InputLabelProps?: InputLabelProps | HTMLLegendElement;
}

This intersection seems to work better than union
InputLabelProps & HTMLLegendElement

You're welcome. A union type of the InputLabelProps and native HTMLLegendElement types may be what you are looking for on line 11, to make cases that use either type valid.
interface ComponentProps {
  InputLabelProps?: InputLabelProps | HTMLLegendElement;
}

Thanks for the suggestion, but that didn't help

You're welcome. A union type of the InputLabelProps and native HTMLLegendElement types may be what you are looking for on line 11, to make cases that use either type valid.
interface ComponentProps {
  InputLabelProps?: InputLabelProps | HTMLLegendElement;
}

Thanks for the suggestion, but that didn't help

Happy to help. Okay, perhaps a more experienced contributor can look into making the type switch the underlying element based on component as you requested earlier.

@heath-freenome

Or maybe I can add a generic for HTMLLegendElement to the InputLabelProps to somehow make typescript happy.

Yes, this is what you will have to do. See https://codesandbox.io/s/vigilant-wiles-pe0ie2?file=/src/App.tsx.

Although honestly, it seems like the type should be built to switch the underlying element based on component.

The types are built to switch to the underlying element based on the component prop when the props are provided directly to the InputLabel component. But since you have a custom component (named Component) that you are explicitly typing with the InputLabelProps type, you will have to provide a parameter type to the InputLabelProps generic. By default, it uses the label component.


Update Webinars Pages “armory-continuous-delivery-for-infrastructure/index”

Automatically generated by Netlify CMS

Just for testing cms will close

Oh I am sorry, I thought it was the one I created


add tolerance to netlist extraction

Hi Joaquin!
I propose this simple patch during netlist extraction.
Basically I've changed two things:

There now is a tolerance (in nm) for netlist extraction.
Store internal x,y,w coordinates as ints in the dictionary as comparing floats might yield problems due to eps differences.

What do you think?

Looks good,
Thank you Floris

I released 3.5.12, with your patch. See CHANGELOG.md

add tolerance to netlist extraction. Snap to any nm grid for detecting connectivity (defaults to 1nm).


launch/sev: Remove lifetime requirement

Instead of a sev::Launcher taking references to AsRawFd implementers, allow then to take ownership if they see fit. If a caller does not want a sev::Launcher to take ownership, they can use as_raw_fd().

cc @slp

LGTM.


Missing bevy_ecs 0.10.0 documentation

How can Bevy's documentation be improved?
The bevy_ecs documentation seems to not have been updated for the last release
https://docs.rs/bevy_ecs/0.10.0 is not available

https://docs.rs/releases/queue
Ah, I see


Rename UNeXt2

Rename the 'Unet22d' architecture to 'UNeXt2'.

@Soorya19Pradeep just FYI we are changing names for what used to be 2.2D Unet

Thanks for the update @edyoshikun !


Declaration of supported PHP versions

Submitted solutions often show deprecated usage of the language. While they still work, they do not make usage of newer (meaning better) syntax or functionality. Additionally they have become uncommon practice in modern PHP frameworks and libraries.
In order to provide a good experience for students, to learn modern (current) aspects of the language, I recommend defining supported PHP versions. It would clarify supported syntax, especially in regards to type declarations etc.
I am not sure, what the best place for this is, but could imagine the installation guide as a start. This might be overlooked by those who have PHP already up and running. Maybe you have a better suggestion?
Personally I would prefer the support of currently maintained releases like 7.2 and 7.3. The tests lack some maintenance and could benefit from a dust-off.
For the repository itself and development of it, initializing composer and adding a version constraint for PHP could benefit the process.
Questions:

Are there any reasons not to limit supported versions (I might not be aware of)?
What is the best place to specify supported versions?

I am curious about the responses and willing to contribute, if changes will be necessary.

I agree it would be wise to encourage learners to update to/use at least a supported (and maintained) version of the language. This will always be in flux, but the repo is probably overdue an update to support 7.2+.
The installation guide seems a sensible place for this (see source code here).
We also need to update travis.yml too (if we're to officially drop support for PHP 7.1.


Implement fairseq

I'd love to see the core parts of this type of sequence model available in Chainer.
https://github.com/facebookresearch/fairseq

Fortunately, I implemented a convolutional seq2seq model using gated linear units (GLU) this week.
https://github.com/soskek/convolutional_seq2seq
I am not planning to make PR of parts of them (e.g. GLU) currently, but you can refer to this. For example, GLU is on https://github.com/soskek/convolutional_seq2seq/blob/master/net.py#L62-L82.
Note that this does not aim for complete reproduction of a model used in experiments in the paper. There are some architecture-level or optimization-level differences of which I am aware or not for.

I'm extremely happy about this!  Thank you!


Change the state text field to a prepopulated dropdown

In order to keep people using a standard state code definition (which is used for reliability querying), Id like to be able to predefine the state / province drop down in the admin console to a list of values.  This could be in the auto-config.inc.php and just be an array.

Would you have a default list of states/provinces that you'd like the wizard to write to auto-config.inc.php, or would you just make this a hidden feature initially?

wizard?

Yes, when you first install the root server there is a wizard that walks you through configuration and auto-generation of auto-config.inc.php.

Would not have to be on the wizard IMO.  The issue that this would be solving is that people are entering all kinds of weird values for states “NC” or “North Carolina” and misspellings.  This throws of our querying by string capability.
What I imagine is that you can just configure the field to be a dropdown instead of freeform text field.  Those values are pre-populated in the config.inc.php file.  Again not sure the wizard needs to be modified for this.

On Oct 3, 2018, at 12:08 AM, jbraswell<EMAIL_ADDRESS>wrote:
Yes, when you first install the root server there is a wizard that walks you through configuration and auto-generation of auto-config.inc.php.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/LittleGreenViper/BMLT-Root-Server/issues/26#issuecomment-426505595, or mute the thread https://github.com/notifications/unsubscribe-auth/ABw9uw2DOxihGCnRa-p4DXNE6jUyoRbsks5uhDhOgaJpZM4XAliu.

I originally planned this, but be aware that the BMLT is not a US-only utility.
It becomes a VERY big deal to change the contents of the popup for different nations.

We can't forget that a huge "selling point" of the BMLT, is its extreme flexibility in working forn non-US Service bodies.
Whenever I do work, I always keep one word in mind:
"Iran".

I actually see this as extremely flexible.  It's an option that is in the configuration.  This feature should not affect anyone that doesn't want to use it.

this feature would be nice for the county, and country fields too.

One of the things that you need to be VERY careful of, here, is that the "solutions" to these problems often becomes "bring in a dependency!"
Some of these dependencies are a VERY BAD THING. One of the ways that the "big kids on the block" have achieved supremacy is to write libraries and frameworks that make it easy to do stuff.
I am immediately suspicious of anything provided by Facebook. Google is a bit better, but mostly because they don't really get into the data stream (they don't really need to).
Something like GraphQL is smack-dab in the middle of your data stream. Facebook gets a peek at every bit of data that goes through your site, and they will use it. Don't believe them for a second when they say they won't use it. They are proven sociopaths. Google is just as bad, but you can sequester the service they provide (for now -note what has already happened with the Maps API). I am extremely suspicious of OAuth2 SSO solutions.
A big part of what has been going on the last few years, is that an entire generation of programmers has been raised in an environment where they -quite literally- cannot write dependency-free software. It's really depressing.
I was at a GraphQL demo a month or so ago, and the kid giving the demo had half a dozen dependencies in the software he was using for the demo. It was ostensibly about GraphQL, but what he was really demonstrating was GraphQL Yoga, and he barely mentioned that. It was just assumed that the baseline was Yoga. What he was demonstrating would ONLY work in Yoga. It was not GraphQL.
That's crazy, but it's par for the course, these days.

This looks good to me.  This will really help data quality.

this could be problematic for people using the BMLT Administrator iOS app, server admins should still  watch data for variations from set array if using this.

There was a discussion on Slack about modifying the iOS app.

This is done in 2.12.0

Still need to validate that this doesn’t break the iOS app. Might be worth implementing the drop down in the iOS app.

It shouldn't, as it becomes a text string, but I don't have the bandwidth to do it quite yet (I will, though; just not for a while -I need to reinvent myself again, and that takes time).


Build script cleanups

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hopefully brings in much of the excellent work done in #9

@conda-forge-admin please rerender


Pulseaudio crackling sound

Godot version:
happens in godot tag  2.1.4
and 2.1 at 0b55481ceaf3dc90c03bf19e0cf9db9d72dd8893
OS/device including version:
Linux guidesk 4.15.3-2-ARCH #1 SMP PREEMPT Thu Feb 15 00:13:49 UTC 2018 x86_64 GNU/Linux
Issue description:
Building with pulseaudio=yes enabled, results with the pulseaudio server craclking audio issues, immediately noticeable right after opening the editor.
Steps to reproduce:
Just compiling with PA yes/no
Notes:
Possible correlation with issues #15266 and #14866. I personally suspect it being related to the forced latency (which is also present with cpu usage), or that "silent" issue that could have solved it on 3.0.
I can run diagnostics commands with pacmd, but I haven't seen anything out of the ordinary yet, feel free to ask me anything I can do. Running godot -v:
 AudioServerSW Params:
 -mix chans: 2
 -mix rate: 44100
 -latency: 10
 -fx: 1
 -interp: 1

CC @marcelofg55
I can't reproduce it by just running the compiled binary, but I did experience such random crackling issues playing Deep Sixed which uses Godot 2.1.4. (Also confirmed by another Linux player).

more info:

pulseaudio ver: 11.1
card name: "HDA ATI SB"
card driver: "snd_hda_intel"

One thing I've noticed is a huge drop in latency as soon as godot starts:
pacmd list-sinks | grep current\ latency
current latency: 355,03 ms
current latency: 1,38 ms
current latency: 2,82 ms

First was before opening godot, second is with pulse enable and third with it disabled. No issues with it disabled, so it may be completely irrelevant.

Did you try this also with latest Godot master (aka 3.x)?
Also could you run godot with -verbose flag? And paste here the console output, thanks!

no I did not, yet at least, and I mentioned above that one possible closed issue may be the answer, the verbose output is plain and simple, without errors with crackling right from the get go
./godot.x11.opt.tools.64.llvm.pulse.180321 -v
No touch devices found
AudioServerSW Params:
 -mix chans: 2
 -mix rate: 44100
 -latency: 10
 -fx: 1
 -interp: 1
Using GLES2 video driver
GLES2: Using GLEW 1.13.0
remap failed: /home/guiu/.godot/editor_settings.tres
load resource: /home/guiu/.godot/editor_settings.tres
EditorSettings: Load OK!
EditorSettings Save OK!
FPS: 1
FPS: 53
FPS: 59
FPS: 60

@Gfurst Can you (or anyone else) still reproduce this bug in Godot 3.2.1 or 3.2.2beta4?
Also, note that there's an OS-independent bug report about clipping/static noises in rapid intervals of sound: https://github.com/godotengine/godot/issues/22016

Closing due to lack of response. Please comment if you can still reproduce this bug.
PS: If no minimal reproduction project was included in the original bug report, please upload one as well to ease troubleshooting.

Hello @Calinou, I haven't checked with this for a while, and this was an issue back when using Godot2 (which had to do because of my project backward compatibility), I can try a newer release to check this out, but I presume it isn't the default packaged released, but a custom build with pulseaudio option?

@Gfurst The official releases use PulseAudio by default. You need to explicitly opt-in to use ALSA by specifying --audio-driver ALSA on the Godot command line.

Well the original issue was rather old, so at some point in time, things must've changed. Anyway, I can still try that out, but if it was the default for everyone, I doubt I would be the only one having issues.

There were some issues in 2.1 but they have long since been fixed.

Sorry, but this issues does not seem to be resolved yet.
I am experiencing the same behaviour with the recent godot-mono build (3.2.3-1) found in the AUR repository of Arch. This build is using the PA driver by default and apparently it is impossible to switch to ALSA using the command line parameter.
I just tested with various projects and regardless of which one it is I always end up with a very annoying crackling and stuttering on the whole system. I also tried to use Jack and bridge to PA using a sink device which ended up in a lot of Xruns while Godot was running.
That being said, I think this issue needs to be reopened.

Please open a new issue, similar symptoms don't necessarily mean a same bug, and both Godot and PulseAudio have changed a ton since 2018.


Ag grid floating filter column chooser list item doesn't have hover effect

Area
UI Components
The problem
Use below site example, click floating filter of "Capital" column, observe no list item hover effect on the column chooser.
https://www.saltdesignsystem.com/salt/components/ag-grid-theme/examples#floating-filter
In v1.3.7 of the theme, there were hover effect on the list items.
The solution
Add hover style to ag-virtual-list-item

background color
cursor: pointer?
Adjust spacing between checkbox and text (very tight in HD)
[Optional] Expand the clickable area of the set filter item (e.g. use padding instead of margin)

Alternatives and examples

Are you a JPMorgan Chase & Co. employee?

[X] I am an employee of JPMorgan Chase & Co.

Going out in next release


feature flag the coupon label that appears in summary

Stan requests: Adding the little label in the order summary html is technically a breaking change.
Add *cxFeatureLevel='1.3' directive to that label to be on a safe side

Will be done in related issue #5191

QA steps:

Change features level to 1.2

Expected result:
Coupons labels shouldn't appear.

Tested on dev10.
With feature flag set to 1.2, we see the coupon input field, and can apply coupons. We do not see the 'applied coupon' label as intended.
Proceeding through checkout removes the coupon, and there's no more coupon related label.
And confirmed that on the order review page, the 'applied coupon' label is not displayed.

With feature flag=1.3, we can see the 'applied coupon' label on the cart page, and all the checkout pages, and the coupons are applied.


Fix ListFeaturesStream return type on RouteGuide Tutorial

Motivation
I followed routeguide-tutorial.md but there's a problem with ListFeaturesStream at compile time.

Solution
Luckily I found a solution in one of the issues.
This PR is to adopt what is suggested in the comment above both in routeguide-tutorial.md and server.rs.

Thanks for fixing this!


20000 works limit (1000 page limit)

Pixiv seems to have a limit set on exactly 20.000 works. Still searching for a workaround for this issue.
The fix most likely has something to do with dates. (limiting search somehow to continue where it left off)

Will most likely solve it using the ECD parameter to get posts per given day.


Take a look at release 1.3.0

Hi dear developers, thank you for your previous collaboration to Vetlog, please take a look at these cool functionality we want to deliver to our users.
Milestone
https://github.com/josdem/playwright-vetlog/milestone/2
Issues
https://github.com/josdem/playwright-vetlog/issues
I hope you find something interesting to work with.
Thanks again! 🐕🐱❤

Release 1.3.0 created: https://github.com/josdem/playwright-vetlog/releases/tag/1.3.0 🎉


Can't Install Template 10 in  Microsoft Visual Studio Community 2015

I tried to search for template 10 in Microsoft Visual Studio Community 2015, but couldn't find it, then I downloaded .vsix file from website and tried to install it manually, and I got error with it stating " VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products."
I have attached log file here, can you please help with this.
VSIXInstaller_f15052e5-4682-4f32-a52b-8648769e0fdc.txt

Support was dropped for 2015 a while ago, time to install Visual Studio 2017.

True. I am sorry.


Assignment 2 - Data Flow Map Ziqing Yuan

Assignment 2 - Data Flow Map Ziqing Yuan.pptx
Hi everyone, Here I share my Data flow map with you. Feel free to leave any comments on it. Thank you!

Hi @ZQYZQYZQ!
Thanks for sharing assignment 2!
Could you please still complete assignment 1  and open up an overview issue so that we can share your assignment there? You can see the other issues in the repository as an example.
Please let me know if you have issues completing this: happy to help!

I'll place the feedback on assignment 2 here for now: It looks very clear and comprehensive, well done @ZQYZQYZQ !
Some feedback and questions that I have:

Why do you need to check the usage rights of the raw optical data? Will you not generate this yourself?
I like how you included your literature database as a dataset! That is indeed also a form of data. Another form could be the images that you use in publications, or the article/chapter texts themselves!
I do not see file sizes and formats in your assignments, so I hope you don't run into any storage space issues. OneDrive stores data up to 1 TB, but the Project Drive should be able to handle more :). File formats will play a more important role in assignment 3.
Do you have any notes or other form of documentation that could be its own separate dataset?


Fix for compatible with Octotree extension

Fix for compatible with Octotree extension https://github.com/buunguyen/octotree
Without fix, page width keep 100% of window and after shift have horisontal scrolling.

I see the issue and the PR fixes it.
another opinion is needed.

Do you have someone?

Do you have someone?

I think @mdo will have a look when he got the tome

I think @mdo will have a look when he got the time

@dj-raphael maybe you could add a fix to prevent the overflow of the octotree button over the gh icon

I'm sorry I took you by the owner.
Yes I can try, but it does not interfere.

Doesn't interfere but would look better.

Wow, PR updated automaticaly. I do not planing this, it's ok?
And it also for compatible with Octotree.

GitHub is great like that :imp:

Your Addition will change the look for all users of this styling.
Can we limit it to users of octotree?

No, I can't. Should I remove this commit, and recreate PR?

You can revert and force push to change the PR to the first commit only.
Then you can send another PR for the other fix so we can talk about limiting it somehow

Should be closed - relates to an issue with a chrome extension of the same name as this style project @mdo

Thanks for the context!


Pinephone support

This has taken a ton of time, compared to how long I wanted it to. Around a week ago I discovered we were booting in EL2, not EL1, that's why writing to the EL1 registers didn't do anything... I also recently discovered that u-boot doesn't have identity mapping set up for some reason, so we have to patch its page tables before reading our data to ram. Both of these factors have cost me many weeks of horrible debugging, but we should finally have walkarounds for all of these issues.


Compare-Object: -ExcludeDifferent should imply -IncludeEqual

Compare-Object only reports differences by default, requiring explicit opt-in for inclusion of equal objects via -IncludeEqual.
Therefore, the only meaningful behavior when you use -ExcludeDifferent is to default to -IncludeEqual.
Without that, as is currently the case, nothing is ever output, so it is currently effectively pointless to pass -ExcludeDifferent without also passing -IncludeEqual.
Steps to reproduce
Compare-Object 1,2 3, 1 -ExcludeDifferent -PassThru -IncludeEqual  | Should -Be 1
# Currently produces NO output, because -IncludeEqual isn't implied.
Compare-Object 1,2 3, 1 -ExcludeDifferent -PassThru | Should -Be 1

Expected behavior
Both tests should pass.
Actual behavior
The 2nd test fails, because -IncludeEqual is not implied.
Environment data
PowerShell Core 7.0.0-rc.2

It appears that it is already supposed to do that, but clearly isn't. See Compare-Object.cs
/// <summary>
/// If the parameter 'ExcludeDifferent' is present, then we need to turn on the
/// 'IncludeEqual' switch unless it's turned off by the user specifically.
/// </summary>
protected override void BeginProcessing()
{
    if (ExcludeDifferent)
    {
        if (_isIncludeEqualSpecified == false)
        {
            return;
        }

        if (_isIncludeEqualSpecified && !_includeEqual)
        {
            return;
        }

        _includeEqual = true;
    }
}


Avoid subscribing static components

I'm not sure if this breaks anything, but if it doesn't it might prevent some unnecessary re-renders?

This makes sense in theory. Breaks a ton of tests though...

I think it can change in SSR scenarios from first construction to final emit?

Should probably also do on native btw?

We don't have a concept of "staticness" in native at the moment. I looked 😛


Rewired modules showing up in Coverage reports

When I run mix test --cover, I'm seeing rewired modules in the coverage report:
Generating cover results ...

Percentage | Module
-----------|--------------------------
    78.57% | Foo.Bar.Baz.R5115

Is this expected behavior?  I'm thinking they should be excluded, but I'm hesitant to start adding generated modules to my coverage_exclusions.

For anyone else that encounters this, you can add the following to your coverage_exclusions to ignore any coverage reports for rewired modules: ~r"\.R\d+$"


Add KUTTL test --start-index and --end-index

When building out a kuttl test, there could be a failure after a number of steps and there may be issues with re-running those steps.  It should be great to "skip" a set of steps and start where you left off.
After having that thought, --end-index made sense... where you may want to run the apply and asserts for a given step.  It likely is meaningful to say  --start-index=2 --end-index=2 means to run step 2 with it's asserts and stop.
things to think about:

this works great if 1) namespace is provided or 2) --skip-delete was used.  It likely isn't useful otherwise
if skip-delete is used, then it might be nice to be able to start with the same namespace... but it seems the user will need to type that.

this thought may not make sense... it seems useful when creating tests, and working with 1 test... but under normal circumstances, what does index mean for a series of tests?

questionable... this


Having problem when applying filter on child collection

I have a class Project that contains a collection of ProjectResourceMembers.
My filter is defined like this:
//Security
                modelBuilder.Filter("ProjectFilter",
                    (Project p, string resourceCode) => (p.ProjectResourceMembers.Any(x => x.ResourceCode.ToLower() == GetResourceCodeFromPrincipal(Thread.CurrentPrincipal))
                    && p.IsConfidential == true) || p.IsConfidential == false,
                    () => GetResourceCodeFromPrincipal(Thread.CurrentPrincipal));

                modelBuilder.EnableFilter("ProjectFilter", () => !string.IsNullOrEmpty(GetResourceCodeFromPrincipal(Thread.CurrentPrincipal)));

However, when I query the context (via OData), I get this exception:
variable 'x' of type 'DataHub.Provider.Models.Atomic.ProjectResourceMember' referenced from scope '', but it is not defined
The error seems to be related to x.ResourceCode.ToLower()... Any idea what the error might be?

Hello @elferone ,
I'm not exactly sure yet what's the error but something for sure doesn't work in this expression.
The filter modifies the SQL queries that will be sent to the database.
However, this part: x => x.ResourceCode.ToLower() == GetResourceCodeFromPrincipal(Thread.CurrentPrincipal)
Cannot be translated to a SQL query because of the method GetResourceCodeFromPrincipal
I believe you can already use the variable resourceCode instead.
Can you try to fix the filter expression and tell us if you still have the same issue?
Best Regards,
Jonathan

I have fixed the expression to:
//Security
                modelBuilder.Filter("ProjectFilter",
                    (Project p, string resourceCode) => (p.ProjectResourceMembers.Any(x => x.ResourceCode.ToLower() == resourceCode)
                    && p.IsConfidential == true) || p.IsConfidential == false,
                    () => Thread.CurrentPrincipal.Identity.Name.ToLower());

The error still happens when I use the ToLower() function on x.ResourceCode:

x => x.ResourceCode.ToLower()

Hello @elferone ,
Thank you, I will try to create a similar filter on my side and see if something is missing for the ToLower method.
Best Regards,
Jonathan

.ToLower() is not supported.  And I don't see an obvious way to map that C# function to the database function.  It does not seem to be exposed in DbExpressionBuilder (we are limited in this library to what EF has decided to expose to us).
There are some other custom functions being handled in LambdaToDbExpressionVisitor.VisitMethodCall() - that would probably be the right place to add support if it's possible to map it.

Thank you @jcachat for letting me know.
I believe there is certainly a way since a DbExpression must be returned but I'm not sure either how doing it yet.
Best Regards,
Jonathan

Hello @elferone ,
The v3.0.0 has been released.
The support for ToLower and ToUpper for basic scenario should now work.
Let me know if you run into another issue.
@jcachat , using your code made this request pretty easy ;) I'm not sure if that handle all scenarios but that will at least handle some basic scenario,
Here is the code added
case "ToLower":
	expression = MapSimpleExpression(node, EdmFunctions.ToLower);
	break;

private Expression MapSimpleExpression(MethodCallExpression node, Func<DbExpression, DbFunctionExpression> dbExpressionFactory)
{
	var expression = base.VisitMethodCall(node) as MethodCallExpression;

	DbExpression srcExpression = GetDbExpressionForExpression(expression.Object);
	var dbExpression = dbExpressionFactory(srcExpression);
	MapExpressionToDbExpression(expression, dbExpression);
	return expression;
}

Best Regards,
Jonathan

Works like a charm. Good job and thanks again!


Breakpoints are skipped while debugging PHP application with Sublime Text 3

Hi,
I have been trying to debug a PHP application on LAMPP stack from Sublime Text 3, but the browser loads the page completely without hitting any of the breakpoints I have set in them. I am running the LAMPP stack on Ubuntu 18.04 with PHP version 7.3.8 and Xdebug version 2.7.2 (installed based on the instructions from the wizard.).
Since the same Xdebug setup happen to work perfectly with VS Code, I tried comparing the Xdebug logs generated for both.
As can be seen from the log for Sublime Text run at the bottom, Xdebug recognizes the breakpoints correctly, but there is an error while communicating with the client using IPv6 address of localhost (::1). On the other hand, in the case of VS Code, the IPv6 address seems to be handled without error and the debugger works correctly.
I tried swapping the host address between 'localhost', '<IP_ADDRESS>' and '<IP_ADDRESS>' (private IP of the machine in LAN) in php.ini, .sublime_project, and Xdebug.sublime-settings files, but there was no change. The debugger in VS Code works perfectly with Xdebug regardless of these changes, so I'm guessing the issue lies on the side of Sublime Text (when it tries to communicate with Xdebug) instead of any problem with the Xdebug installation.
For the past couple of days I have been experimenting with various fixes suggested in different forums, but I'm no closer to a solution yet.
Can you please shed some light on this? I have pasted the contents of the configuration files and the logs below.
Environment
Sublime Text
Operating system:
Ubuntu 18.04
Installed version/build:
Sublime Text 3 v3.2.1
Python version:
3.3.6
Server
LAMPP stack running on Ubuntu 18.04
PHP/Xdebug version:
PHP 7.3.8 / Xdebug 2.7.2
Configuration
php.ini/xdebug.ini
zend_extension=/opt/lampp/lib/php/extensions/no-debug-non-zts-20180731/xdebug.so
[XDebug]
xdebug.remote_enable=1
xdebug.remote_autostart=true
xdebug.remote_host=<IP_ADDRESS>
xdebug.remote_connect_back=1 ; Not safe for production servers
xdebug.remote_port=9000
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_log=/tmp/xdebug.log
xdebug.idekey=sublime.xdebug
Packages/User/Xdebug.sublime-settings
{
"path_mapping": {

"/opt/lampp/htdocs/" : "/opt/lampp/htdocs/"

},

"url": "http://<IP_ADDRESS>/index.php",

"ide_key": "sublime.xdebug",

"host": "<IP_ADDRESS>",

"port": 9000,

"max_children": 32,

"max_data": 1024,

"max_depth": 1,

"break_on_start": false,

"break_on_exception": [
    "Fatal error",
    "Catchable fatal error",
    "Warning",
    "Parse error",
    "Notice",
    "Strict standards",
    "Deprecated",
    "Xdebug",
    "Unknown error"
],

"close_on_stop": false,

"super_globals": true,

"fullname_property": true,

"hide_password": false,

"pretty_output": false,

"launch_browser": false,

"browser_no_execute": false,

"disable_layout": false,

"debug_layout" : {
    "cols": [0.0, 0.5, 1.0],
    "rows": [0.0, 0.7, 1.0],
    "cells": [[0, 0, 2, 1], [0, 1, 1, 2], [1, 1, 2, 2]]
},

"breakpoint_group": 2,
"breakpoint_index": 1,
"context_group": 1,
"context_index": 0,
"stack_group": 2,
"stack_index": 0,
"watch_group": 1,
"watch_index": 1,

"breakpoint_enabled": "circle",
"breakpoint_disabled": "dot",
"breakpoint_current": "",
"current_line": "bookmark",

"python_path" : "",

"debug": true

}
*.sublime-project
{
"folders":

[

    {

        "follow_symlinks": true,

        "path": "."

    }

],

"settings": {

    "xdebug": {

         "url": "http://<IP_ADDRESS>/fastusvisa/",

         "path_mapping": {

            "/opt/lampp/htdocs/<application>" : "/opt/lampp/htdocs/<application>",

            "super_globals": true,

            "close_on_stop": true

        },

    }

}

}
Logs
Console output:
Packages/User/Xdebug.log:
Xdebug.log (successful) from VS Code
[3156] Log opened at 2019-09-23 09:15:01
[3156] I: Checking remote connect back address.
[3156] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[3156] I: Checking header 'REMOTE_ADDR'.
[3156] I: Remote address found, connecting to <IP_ADDRESS>:9000.
[3156] I: Connected to client. :-)
[3156] -> XdebugDerick Rethanshttps://xdebug.orgCopyright (c) 2002-2019 by Derick Rethans
[3156] <- breakpoint_list -i 1
[3156] ->
[3156] <- breakpoint_list -i 2
[3156] ->
[3156] <- breakpoint_set -i 3 -t line -f file:///opt/lampp/htdocs/fastusvisa/wp-content/themes/di-business/footer.php -n 16
[3156] ->
[3156] <- breakpoint_set -i 4 -t line -f file:///opt/lampp/htdocs/fastusvisa/wp-content/themes/di-business/header.php -n 15
[3156] ->
[3156] <- breakpoint_list -i 5
[3156] ->
[3156] <- breakpoint_list -i 6
[3156] ->
[3156] <- breakpoint_set -i 7 -t exception -x *
[3156] ->
[3156] <- run -i 8
[3156] ->
[3156] <- stop -i 9
[3156] ->
[3156] Log closed at 2019-09-23 09:15:02
[3955] Log opened at 2019-09-23 09:15:02
[3955] I: Checking remote connect back address.
[3955] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[3955] I: Checking header 'REMOTE_ADDR'.
[3955] I: Remote address found, connecting to ::1:9000.
[3955] I: Connected to client. :-)
[3955] -> XdebugDerick Rethanshttps://xdebug.orgCopyright (c) 2002-2019 by Derick Rethans
[3955] <- breakpoint_list -i 1
[3955] ->
[3955] <- breakpoint_list -i 2
[3955] ->
[3955] <- breakpoint_set -i 3 -t line -f file:///opt/lampp/htdocs/fastusvisa/wp-content/themes/di-business/footer.php -n 16
[3955] ->
[3955]
[3955] <- breakpoint_set -i 4 -t line -f file:///opt/lampp/htdocs/fastusvisa/wp-content/themes/di-business/header.php -n 15
[3955] ->
[3955]
[3955] <- breakpoint_list -i 5
[3955] ->
[3955]
[3955] <- breakpoint_list -i 6
[3955] ->
[3955]
[3955] <- breakpoint_set -i 7 -t exception -x *
[3955] ->
[3955]
[3955] <- run -i 8
.
.
.
.
[3955] <- step_over -i 32
[3955] -> <xdebug:message filename="file:///opt/lampp/htdocs/fastusvisa/wp-content/themes/di-business/header.php" lineno="123"></xdebug:message>
[3955] <- stack_get -i 33
[3955] ->
[3955] <- run -i 34
[3955] ->
[3955] <- stop -i 35
[3955] ->
[3955] Log closed at 2019-09-23 09:15:24
[3955]
`
Xdebug.log (failure) from Sublime Text 3
[3152] Log opened at 2019-09-23 09:07:08
[3152] I: Checking remote connect back address.
[3152] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[3152] I: Checking header 'REMOTE_ADDR'.
[3152] I: Remote address found, connecting to <IP_ADDRESS>:9000.
[3152] I: Connected to client. :-)
[3152] -> XdebugDerick Rethanshttps://xdebug.orgCopyright (c) 2002-2019 by Derick Rethans
[3152] <- feature_set -i 1 -n show_hidden -v 1
[3152] ->
[3152] <- feature_set -i 2 -n max_children -v 32
[3152] ->
[3152] <- feature_set -i 3 -n max_data -v 1024
[3152] ->
[3152] <- feature_set -i 4 -n max_depth -v 1
[3152] ->
[3152] <- breakpoint_set -i 5 -f file%3A///opt/lampp/htdocs/fastusvisa/wp-content/themes/di-business/header.php -t line -n 15
[3152] ->
[3152] <- breakpoint_set -i 6 -f file%3A///opt/lampp/htdocs/fastusvisa/wp-content/themes/di-business/header.php -t line -n 32
[3152] ->
[3152] <- breakpoint_set -i 7 -f file%3A///opt/lampp/htdocs/fastusvisa/wp-content/themes/di-business/header.php -t line -n 5
[3152] ->
[3152] <- breakpoint_set -i 8 -f file%3A///opt/lampp/htdocs/fastusvisa/wp-content/themes/di-business/header.php -t line -n 23
[3152] ->
[3152] <- breakpoint_set -i 9 -t exception -x "Fatal error"
[3152] ->
[3152] <- breakpoint_set -i 10 -t exception -x "Catchable fatal error"
[3152] ->
[3152] <- breakpoint_set -i 11 -t exception -x "Warning"
[3152] ->
[3152] <- breakpoint_set -i 12 -t exception -x "Parse error"
[3152] ->
[3152] <- breakpoint_set -i 13 -t exception -x "Notice"
[3152] ->
[3152] <- breakpoint_set -i 14 -t exception -x "Strict standards"
[3152] ->
[3152] <- breakpoint_set -i 15 -t exception -x "Deprecated"
[3152] ->
[3152] <- breakpoint_set -i 16 -t exception -x "Xdebug"
[3152] ->
[3152] <- breakpoint_set -i 17 -t exception -x "Unknown error"
[3152] ->
[3152] <- run -i 18
[3152] ->
[3152] Log closed at 2019-09-23 09:07:15
[3153] Log opened at 2019-09-23 09:07:15
[3153] I: Checking remote connect back address.
[3153] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[3153] I: Checking header 'REMOTE_ADDR'.
[3153] I: Remote address found, connecting to ::1:9000.
[3153] W: Creating socket for '::1:9000', poll success, but error: Operation now in progress (29).
[3153] E: Could not connect to client. :-(
[3153] Log closed at 2019-09-23 09:07:15
[3153] Log opened at 2019-09-23 09:07:17
[3153] I: Checking remote connect back address.
[3153] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[3153] I: Checking header 'REMOTE_ADDR'.
[3153] I: Remote address found, connecting to ::1:9000.
[3153] W: Creating socket for '::1:9000', poll success, but error: Operation now in progress (29).
[3153] E: Could not connect to client. :-(
[3153] Log closed at 2019-09-23 09:07:17
[3153] Log opened at 2019-09-23 09:07:17
[3153] I: Checking remote connect back address.
[3153] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[3153] I: Checking header 'REMOTE_ADDR'.
[3153] I: Remote address found, connecting to ::1:9000.
[3153] W: Creating socket for '::1:9000', poll success, but error: Operation now in progress (29).
[3153] E: Could not connect to client. :-(
[3153] Log closed at 2019-09-23 09:07:17
[3153] Log opened at 2019-09-23 09:07:17
[3153] I: Checking remote connect back address.
[3153] I: Checking header 'HTTP_X_FORWARDED_FOR'.
[3153] I: Checking header 'REMOTE_ADDR'.
[3153] I: Remote address found, connecting to ::1:9000.
[3153] W: Creating socket for '::1:9000', poll success, but error: Operation now in progress (29).
[3153] E: Could not connect to client. :-(
[3153] Log closed at 2019-09-23 09:07:17
[3153]

I am experiencing the exact same issue. Everything works in Visual Studio Code, but error after error when using Sublime Text 3 and this plugin. I've tried everything, no dice.

@lewsid, I switched from this Package to the Debugger Package. If you have experience in using VS Code  and Xdebug the Debugger Package is – in my opinion – easy to handle.

Thanks @meengit!

@vineethgk Did you find a solution? I have the same issue as well


PMID:25417108

abnormal RNA polymerase II release at rDNA
abnormal RNA polymerase II release at tDNA
abnormal RNA polymerase II release at highly transcribed protein-coding gene
decreased antisense transcription-derived small RNA level at tDNA
decreased antisense transcription-derived small RNA level at rDNA
increased antisense small RNA at rDNA
increased number of Rad52 foci at rDNA replication origins
increased number of Rad52 foci at rDNA replication pause sites
decreased number of Rad52 foci at highly transcribed protein coding genes
increased level of DNA:RNA hybrids at rDNA
stable shortened rDNA during veg growth
progressively shortening rDNA through meiotic generations
normal rDNA copy number

a few questions:
Is "RNA polymerase II release" distinct from "termination of RNA polymerase II transcription" (a la GO:0006369)?
"Antisense transcription-derived small RNA" sounds the same as "antisense small RNA", only wordier. OK if I use the "antisense small RNA" wording in the names for 4-6?
Does "shortened rDNA" mean "decreased rDNA copy number"?

Is "RNA polymerase II release" distinct from "termination of RNA polymerase II transcription" (a la GO:0006369)?
-I was unsure to be honest. In the paper they say:
"Canonical termination involves two steps, the first being Pol II pausing, and the second being Pol II release"
I think "pausing" is (similar to...) this:
https://en.wikipedia.org/wiki/Intrinsic_termination
Is this a distinct step from "release"? If not then I guess "termination of RNA polymerase II transcription" is fine....I was unsure..
"Antisense transcription-derived small RNA" sounds the same as "antisense small RNA", only wordier. OK if I use the "antisense small RNA" wording in the names for 4-6?
-yes
Does "shortened rDNA" mean "decreased rDNA copy number"?
-yes

re 1-3 - Okey doke, I'll put them in as "termination" because that lets me use GO:0006369 in xps. If the authors don't like it, maybe they can help us define more specific GO terms to request and use. (I certainly don't have much relevant specialist knowledge!)

abnormal termination of RNA polymerase II transcription FYPO:0004811
abnormal termination of RNA polymerase II transcription at rDNA FYPO:0004812
abnormal termination of RNA polymerase II transcription at tDNA FYPO:0004813
abnormal termination of RNA polymerase II transcription at highly transcribed protein-coding genes FYPO:0004814
increased rDNA antisense small RNA level FYPO:0004815
decreased antisense RNA level FYPO:0004816
decreased rDNA antisense small RNA level FYPO:0004817
decreased tDNA antisense small RNA level FYPO:0004818
increased number of Rad52 foci at rDNA replication origins FYPO:0004819
increased number of Rad52 foci at rDNA replication pause sites FYPO:0004820
decreased number of Rad52 foci at highly transcribed protein-coding genes FYPO:0004821
increased level of RNA-DNA hybrids at rDNA FYPO:0004822
abnormal rDNA copy number FYPO:0004 FYPO:0004823
normal rDNA copy number FYPO:0004824
stably decreased rDNA copy number during vegetative growth FYPO:0004825
progressively decreasing rDNA copy number during successive meiotic generations FYPO:0004826

edit file: b8675d2457640a785c45d391b00ed8b8f33fae71
release: f734d0cb6a1e4ed84a8e2fcacaade03fe1d655b4


Fix raster statistics

The property stats must be statistics.
That also fixes the default rendering for e.g. the DSM in OL STAC (but not yet in STAC Browser).

@tschaub Although the nodata value is not explicitly set in the COGs, I've also added NaN as nodata value.


Seperate GUI into a separate artifact and reorganize it to use the new modules.

Depends on #35, #36, #37, #38.

Module has been separated to own project at JavaTorrent-gui


should i use  supersonic.bind($scope, function)?

I have a requirement in which i want javascript function to continuously run in background regardless or view .how can i achieve that?
deviceready is fired on each view. But i want to call function ones in initial view and  keep it running in background.
should i use supersonic.bind($scope, function) to acehive my goal?

You can use supersonic.bind() for this. You can also use $rootScope, though most developers I have talked with on this issue are using Superscope.

Function will check for network and if network is available it will send all data from indexeddb to server. Function will continue to run on specific time interval.
So what will be perfect one supersonic.bind() or superscope? @justincolangelo

Here is an example of a service that has a setInterval() call in the $rootScope. Self Updating Data Service
I haven't tested something like this on an Appgyver application, yet. I use $rootScope for a few things in my Appgyver application, but not for this at the moment.

will this work on multipage appgyver application ? Because for each view new instance of webview with all script reference is created. So on each view angular service or controller will be reinitialized.

Is it all part of one module? I am relying on SO posts because this type of question has been answered many times on there. Here is one example that can share a service across modules/apps: Share Service


Identifying and Documenting Unique Client Metadata Parameters in the WSO2 DCR Implementation

Description:
for the DCR endpoint, apart from the client metadata defined in the spec (RFC 7591), only the ones listed http://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#client-metadata should be added according to https://datatracker.ietf.org/doc/html/rfc7591#section-4.1.
But in our implementation, we have added custom client metadata parameters that are not defined in either of these places.
A summary of the parameters that are shared with the RFC and the metadata registry and the and the ones that are unique to us.

Shared with RFC
Shared with Metadata Registry
Unique to WSO2-IS DCR

redirect_uris
redirect_uris
url

client_name
client_name
ext_param_client_id

client_id
client_id
ext_param_client_secret

client_secret
client_secret
ext_param_sp_template

grant_types
grant_types
-

jwks_uri
jwks_uri
-

contacts
contacts
-

response_types
response_types
-

-
application_type
-

-
post_logout_redirect_uris
-

-
request_uris
-

-
backchannel_logout_uri
-

-
backchannel_logout_session_required
-

Based on the above comparison, there are 4 unique parameters found in WSO2-IS DCR implementation that are not present in either the RFC or the Metadata Registry:
url
ext_param_client_id
ext_param_client_secret
ext_param_sp_template

It's also worth noting that the WSO2-IS DCR implementation does not include several parameters from both the RFC and the Metadata Registry, including but not limited to:
token_endpoint_auth_method
client_uri
logo_uri
scope
tos_uri
policy_uri
software_id
software_version
client_id_issued_at
client_secret_expires_at

As for the parameters present in the Metadata Registry but not in WSO2-IS DCR, there are several of them, such as:
registration_access_token
registration_client_uri
sector_identifier_uri
subject_type
id_token_signed_response_alg
id_token_encrypted_response_alg
id_token_encrypted_response_enc
userinfo_signed_response_alg
userinfo_encrypted_response_alg
userinfo_encrypted_response_enc
request_object_signing_alg
request_object_encryption_alg
request_object_encryption_enc
token_endpoint_auth_signing_alg
default_max_age
require_auth_time
default_acr_values
initiate_login_uri
claims_redirect_uris
nfv_token_signed_response_alg
nfv_token_encrypted_response_alg
nfv_token_encrypted_response_enc
tls_client_certificate_bound_access_tokens
tls_client_auth_subject_dn
tls_client_auth_san_dns
tls_client_auth_san_uri
tls_client_auth_san_ip
tls_client_auth_san_email
require_signed_request_object
require_pushed_authorization_requests
introspection_signed_response_alg
introspection_encrypted_response_alg
introspection_encrypted_response_enc
frontchannel_logout_uri
frontchannel_logout_session_required
authorization_details_types
dpop_bound_access_tokens

However, in the OIDC DCR implementation that is now deprecated, we have used parameters from the metadata registry which are now not supported in our default implementation.
The following is a comparison of the WSO2-IS OAUTH DCR parameters, WSO2-IS OIDC DCR parameters, RFC parameters, and Metadata Registry parameters.

Parameter
RFC
Metadata Registry
WSO2-IS OAUTH DCR
WSO2-IS OIDC DCR

sector_identifier_uri
-
Yes
-
Yes

subject_type
-
Yes
-
Yes

id_token_signed_response_alg
-
Yes
-
Yes

id_token_encrypted_response_alg
-
Yes
-
Yes

id_token_encrypted_response_enc
-
Yes
-
Yes

userinfo_signed_response_alg
-
Yes
-
Yes

userinfo_encrypted_response_alg
-
Yes
-
Yes

userinfo_encrypted_response_enc
-
Yes
-
Yes

request_object_signing_alg
-
Yes
-
Yes

request_object_encryption_alg
-
Yes
-
Yes

request_object_encryption_enc
-
Yes
-
Yes

token_endpoint_auth_signing_alg
-
Yes
-
Yes

default_max_age
-
Yes
-
Yes

require_auth_time
-
Yes
-
Yes

default_acr_values
-
Yes
-
Yes

initiate_login_uri
-
Yes
-
Yes

request_uris
-
Yes
Yes
Yes

redirect_uris
Yes
Yes
Yes
-

client_name
Yes
Yes
Yes
-

client_id
Yes
Yes
Yes
-

client_secret
Yes
Yes
Yes
-

grant_types
Yes
Yes
Yes
-

application_type
-
Yes
Yes
-

jwks_uri
Yes
Yes
Yes
-

url
-
-
Yes
-

ext_param_client_id
-
-
Yes
-

ext_param_client_secret
-
-
Yes
-

contacts
Yes
Yes
Yes
-

post_logout_redirect_uris
-
Yes
Yes
-

response_types
Yes
Yes
Yes
-

ext_param_sp_template
-
-
Yes
-

backchannel_logout_uri
-
Yes
Yes
-

backchannel_logout_session_required
-
Yes
Yes
-

From the table, we can see that the parameters used in WSO2-IS DCR and WSO2-IS OIDC DCR implementations are quite different. Only the 'request_uris' parameter is shared between the two WSO2 implementations, while the rest of the parameters are exclusive to each.
related: https://github.com/wso2/product-is/issues/14959

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


feat: Add .contextignore support and normalize linter output

Changes
This PR introduces support for .contextignore files and normalizes the linter output across the project. The main changes include:

Added ContextignoreLinter class to handle .contextignore file linting and file ignoring functionality.
Implemented validation for .contextignore file patterns, including checks for:

Invalid patterns
Patterns that might ignore critical files (.context.md, .context.yaml, .context.json, .contextdocs.md, .contextignore)
Conflicting patterns (a pattern and its negation)

Added caching mechanism for ignore patterns to improve performance.
Implemented recursive file checking to support .contextignore files at different directory levels.
Normalized linter output for consistency across different linter types.

Key Features

Support for .contextignore files to exclude specific files or directories from context consideration.
Improved error reporting and validation for .contextignore files.
Performance optimization through caching of ignore patterns.
Consistent linter output format across the project.

Testing

Added tests for .contextignore file functionality.
Ensured existing tests pass with the new changes.

Documentation

Updated relevant documentation to reflect the new .contextignore support.
Added inline comments to explain complex logic in the ContextignoreLinter class.

This PR enhances the project's flexibility by allowing users to exclude specific files or directories from context consideration, while maintaining the integrity of critical context files. The normalized linter output will improve the consistency of the tool's feedback across different file types.

:tada: This PR is included in version 1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Can we pass the prop on headless toast for title and description?

@maheshbhattaraifundo
Yes with the new release, you can


mgmt, update test on mediaservice

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - mediaservices - mgmt - tests

/azp run java - mediaservices - mgmt - tests

/azp run java - mediaservices - mgmt - tests


@skip, @include respect avoidOptionals

Related: https://github.com/dotansimha/graphql-code-generator/issues/5099

@gilgardosh ready for a review? (btw, changeset is missing)

@dotansimha Ready now


(:query-params request) not keywordized?

The title says it all. the result map I get from (:query-params request) is not keywordized. Should this be keywordized by default?

The wrap-keywords middleware only keywordizes :params. This is so that you can access the parameters conveniently via :params, but access them more exactly via :query-params (and :form-params).

Just curious, what is the reason why (:query-params) is not keywordized by default?


support: Add new EVMs to Support NFTs

✅ Checklist

[x] npx changeset was attached.
[ ] Covered by automatic tests.
[ ] Impact of the changes:

...

📝 Description

Add new EVMs in NFTs support (https://github.com/LedgerHQ/nft-metadata-service/pull/1448)

arbitrum, avalanche_c_chain, base, blast, bsc, celo, ethereum, fantom, linea, moonbeam, optimism, polygon, scroll
LLD

LLM
https://github.com/user-attachments/assets/aff94d50-4661-400e-9644-b6343350dd9a
https://github.com/user-attachments/assets/79f7d3ed-fcb2-4181-9b01-c1d1bcd3b6dc

Update SimpleHash tool in LLD to support more Spam report/check

❓ Context

JIRA or GitHub link: LIVE-14272

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

Tested and it works well. Looks like we don't receive rarible/opensea links from backend so all good


Make Python topology adapt to #1421

In https://github.com/twitter/heron/pull/1421, changes of instance involve only Java part. We need to change Python part accordingly.

close via #1468


[main] Update BC Artifact version

Fixes AB#420000

Test Results Summary
Workflow run: https://github.com/aholstrup1/BCApps/actions/runs/8151717026
Last updated: 2024-03-05 05:58:59


[Event Request] Report 13630/13631 "OIOUBL-Create Elec. Invoices"/"OIOUBL-Create Elec. Cr. Memos"  skip Succesfully Messsage

Describe the request
We would like an event to be able to skip this Message upon OnPostDataItem  for both Report 13630 "OIOUBL-Create Elec. Invoices"  and 13631 "OIOUBL-Create Elec. Cr. Memos"  The Event should be added in both report.
Suggestion:
report 13630 "OIOUBL-Create Elec. Invoices"
{

            trigger OnPostDataItem();
            begin
           OnAfterCreateElectronicInvoice(SkipMessage);
          if not SkipMessage then
                MESSAGE(SuccessMsg, Counter);
            end;

      SuccessMsg: Label 'Successfully created %1 electronic invoice(s).', Comment = '%1 = amount of electronic invoices created';

report 13631 "OIOUBL-Create Elec. Cr. Memos"
{
            trigger OnPostDataItem();
            begin
            OnAfterCreateElectronicCrMemo(SkipMessage);
            if not SkipMessage then
                MESSAGE(SuccessMsg, Counter);
            end;
      SuccessMsg: Label 'Successfully created %1 electronic cr. Memo(s).', Comment = '%1 = amount of electronic cr. Memos created';

Additional context
We have an extension that can send electronic Invoice Directly to Sproom API and it is tedious to press okey for each document that are sent if the customer are using batch posting, A boolean field is already updated on the document that an electronic invoice has been created which should be enough info.
Internal work item: AB#496985

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 17376.


Refactor issues

This ticket is for minor issues we spot for the code refactor.

The spacing for the back button on the preview page looks a little uneven. Any way to move the text a bit more to the left? It looks close to being cut off on the right or add some buffer room on the right.

One small change we mentioned on slack. Sort all stream by "name" on all the applicable pages. We can ignore "display_title"

Deployed fixes for the above two issues.

Found one small one with the creation form. If I try to create a stream and pick an item from the dropdown, sometimes the url wont clear when I switch streaming protocol.
See video below, I pick a UDP url but when I swap to other protocls it stays present. Eventually the form goes back to blank
https://github.com/user-attachments/assets/9e8f59e6-89c7-4eba-8fce-052d46844b38

Some other small things on the creation form
Typo for "Select Encryption" in the placeholder text, it showsd "Selet" instead of "Select"

For Retention it is showing as blank on initial load (even though it uses 1 day)

On Prod we pre select 1 day

Deployed fixes for the typo and retention default.

Deployed a fix for the bug where selected url doesn't clear when switching protocols.

I noticed on the refactor the creation form is more narrow in terms of width when compared to prod. Below is a screenshot, of demo (top) vs prod. I made sure the browser size settings  are set 100% to get an apples to apples comparison

I get an error when I try the probe step from the stream creation step.

I see the console complains with this but in the creation form I had a library specified.
Error: Library ID not specified
    at t.ValidateLibrary (851.bundle.js:2:246151)
    at e.<anonymous> (851.bundle.js:2:440804)
    at d (851.bundle.js:2:423693)
...

When I try to create a stream with no library specified the UI is no longer informing me of my error. Instead a console error get thrown with no error feedback to the user
https://github.com/user-attachments/assets/3dcce60c-faba-48e0-b56e-db65aae17169

On the creation form, for advanced values where we have defaults set for Retention, DRM, Ladder. I noticed that sometimes when I change the value for one of the dropdowns the UI clears my selection or ignored my choice and shows the default value.  I sometimes have to select a non default value twice for it to proper show as selected for me.
Below is a video that shows the issue, I see no console errors getting thrown
https://github.com/user-attachments/assets/6f2e8ddb-10c3-4921-9d4e-5f9b8e0afae8

Deployed fixes for:

the creation form is more narrow in terms of width when compared to prod
 I get an error when I try the probe step from the stream creation step.

Deployed a fix for:

advanced values not getting set properly on the Create page

Deployed a fix for:

When I try to create a stream with no library specified the UI is no longer informing me of my error
PLUS general validation for the Create form items

I pulled the latest changes an noticed in the advanced settings the default ladder is preselected (as expected) but the drop down is blank.  When I click on it you can see "default" is selected and when I click off the drop down it gets populated.
https://github.com/user-attachments/assets/cbaf40d9-591b-4eb3-aada-bbe3819b6827

On demo for stream creation default value for permissions is editable but not auto selected but on prod it is
This is what the option shows on initial load
demo

prod

When creating a new stream. If I go through the whole probe process I noticed 2 issues

My custom language and setting a track to default do not get applied after the stream is saved
/probe gets called again when I click save (this already after I already probed the first time)

Below is an example of the 2 things above. You can see the browser console that probe gets called again when I click save, I ended up sending the stream again so the probe get fulfilled.
You can also see after the save is done my custom language and setting the audio track as default are not present.
https://github.com/user-attachments/assets/f725b21f-e35b-48e8-97f8-8e63b1e02ef3

Deployed fixes for:

in the advanced settings the default ladder is preselected (as expected) but the drop down is blank
default value for permissions is editable but not auto selected
For Create -> Probe, do not re-probe when saving
For Create -> Probe, save custom language and default track
Fix audio_index meta when disabling Record on a middle audio track

Deployed a change to the Preview page to not use a "live" player profile by default. You'll notice that the value of HLS Player Profile in the right sidebar will now be Default.

On the creation page for advanced I cannot change the ladder profile anymore. It stays stuck on the "default" ladder
https://github.com/user-attachments/assets/f2263626-c195-4900-b1a3-18719ffd2e8b

Deployed a fix for the ladder profile being stuck on "default"

Deployed a fix for the ladder profile being stuck on "default"

Interesting, Its fixed but now the issue where the dropdown is blank is back.

Deployed a fix for the playout ladder being blank again


Porch PackageVariant deletion when not in the same namespace

Problem description:
When porch-server is deployed in a namesapce that's not 'porch-system', then at PackageRevision deletion time it fails with the following message:
deployment-dccd4002bfbc41716067a01b073a56078fddec7a failed (Internal error occurred: failed calling webhook "packagerevdeletion.google.com": failed to call webhook: Post "[https://api.porch-system.svc:8443/validate-deletion?timeout=10s":](https://api.porch-system.svc:8443/validate-deletion?timeout=10s%22:) dial tcp: lookup api.porch-system.svc on <IP_ADDRESS>:53: no such host) Error: errors:   Internal error occurred: failed calling webhook "packagerevdeletion.google.com": failed to call webhook: Post "[https://api.porch-system.svc:8443/validate-deletion?timeout=10s":](https://api.porch-system.svc:8443/validate-deletion?timeout=10s%22:) dial tcp: lookup api.porch-system.svc on <IP_ADDRESS>:53: no such host
Preliminary analysis:
It seems that this is because at startup time, porch creates a ValidatingWebhook that hardcodes the porch-system namespace.
See: https://github.com/nephio-project/porch/blob/b0ca16df80a43274bd8726ce45916edb26e42a77/pkg/apiserver/webhooks.go#L178

/label bug

/kind bug

Maybe one solution could be that the ValidatingWebhookConfiguration resource itself is created with the other k8s yaml files, and then there is a reference (name) passed to porch-server at startup time, for which resource to patch with the certificate. This also allows renaming the porch-server ClusterIP service to something other than 'api', which is a problematic name in case multiple services are deployed in the same namespace.

See https://github.com/nephio-project/porch/pull/26

@nagygergo is it OK to close this issue now that the namespace PR has been merged?

Yes, it's ok to be closed.


The published version of the 0.10.4 contains a dist folder in addon/

Hi there !
I was trying to use embroider on our ember applications: http://github.com/1024pix/pix
When using the 0.10.4 version of your addon, I had issues when building the application related to some typescript files:
ERROR in ../../../code/orga/node_modules/dayjs/plugin/advancedFormat.d.ts
Module build failed (from ../../../code/orga/node_modules/thread-loader/dist/cjs.js):
Thread Loader (Worker 1)
/code/orga/node_modules/dayjs/plugin/advancedFormat.d.ts: Missing semicolon. (3:7)

  1 | import { PluginFunc } from 'dayjs'
  2 |
> 3 | declare const plugin: PluginFunc
    |        ^
  4 | export = plugin
  5 |
    at instantiate (/code/orga/node_modules/@babel/parser/lib/index.js:64:32)
    at constructor (/code/orga/node_modules/@babel/parser/lib/index.js:361:12)
    at Parser.raise (/code/orga/node_modules/@babel/parser/lib/index.js:3251:19)
    at Parser.semicolon (/code/orga/node_modules/@babel/parser/lib/index.js:3622:10)
    at Parser.parseExpressionStatement (/code/orga/node_modules/@babel/parser/lib/index.js:13075:10)
    at Parser.parseStatementContent (/code/orga/node_modules/@babel/parser/lib/index.js:12679:19)
    at Parser.parseStatementLike (/code/orga/node_modules/@babel/parser/lib/index.js:12535:17)
    at Parser.parseModuleItem (/code/orga/node_modules/@babel/parser/lib/index.js:12519:17)
    at Parser.parseBlockOrModuleBlockBody (/code/orga/node_modules/@babel/parser/lib/index.js:13106:36)
    at Parser.parseBlockBody (/code/orga/node_modules/@babel/parser/lib/index.js:13099:10)
    at Parser.parseProgram (/code/orga/node_modules/@babel/parser/lib/index.js:12433:10)
    at Parser.parseTopLevel (/code/orga/node_modules/@babel/parser/lib/index.js:12423:25)
    at Parser.parse (/code/orga/node_modules/@babel/parser/lib/index.js:14226:10)
    at parse (/code/orga/node_modules/@babel/parser/lib/index.js:14268:38)
    at parser (/code/orga/node_modules/@babel/core/lib/parser/index.js:41:34)
    at parser.next (<anonymous>)
    at normalizeFile (/code/orga/node_modules/@babel/core/lib/transformation/normalize-file.js:65:38)
    at normalizeFile.next (<anonymous>)
    at run (/code/orga/node_modules/@babel/core/lib/transformation/index.js:21:50)
    at run.next (<anonymous>)
    at transform (/code/orga/node_modules/@babel/core/lib/transform.js:22:41)
    at transform.next (<anonymous>)
    at step (/code/orga/node_modules/gensync/index.js:261:32)
    at /code/orga/node_modules/gensync/index.js:273:13
    at async.call.result.err.err (/code/orga/node_modules/gensync/index.js:223:11)
 @ ./node_modules/ember-dayjs/node_modules/dayjs/plugin/ lazy ^\.\/.*$ namespace object ./advancedFormat.d.ts ./advancedFormat.d
 @ ./node_modules/ember-dayjs/dist/services/dayjs.js 43:35-67
 @ ./assets/pix-orga.js 2891:13-71

As typescript is not javascript this make senses. However the dist/services/dayjs.js was different than the original services/dayjs.js file. It seems to use dynamic import, await import(\dayjs/plugin/${plugin}`);` and webpack try to bundle all files in the plugin dir, so it includes the typescript files.
I guess the addon/dist folder was pushed on npm by mistake. Could you publish a new version to fix that?
Btw, I'm looking forward to use the new version with dynamic imports!

Whoopsy. I was trying to migrate this addon to v2. I guess there were some leftover folders. I'm handling now. Sorry.

I've just released v0.10.6. Should be ok now. Could you please check @francois2metz ? Sorry for inconvenience.

It worked, thanks for the quick fix. Looking forward for the v2 addon.


Running a Simulation with an Invalid Circuit

I haven't fully worked my way through Circuit construction, Circuit validation and Circuit simulation, but I am not clear on why a Circuit does not have an IsValid property. The Circuit class does have a Validate() method, but all it does is return a CircuitException if a validation rule fails ( #96 ).
Perhaps the Circuit class could contain an IsValid property that calls the Validate() method when the circuit entity items have changed ( a needs validation flag ). This could then be used by the Simulation.Run( entities ) method to check if a circuit is valid before running simulations.

The original validation was quite naive and straight-forward. I also chose the form of a method (Validate()) to make you feel that it was not a very cheap operation. But I do believe that making it throw exceptions for any rule violation was perhaps not the best option because it obscures validation rules further down the line.
The new validation framework (for v3.0) should allow you to run through all the validation rules and list them.

So, I've been thinking about this...
The question stuck in my head is "what is a valid circuit"? And the answer is actually a little bit more awkward than I assumed before. For the standard simulations included in Spice#, some rules apply and some don't. For example, floating nodes are invalid for biasing analyses, but may not be for a transient analysis that has initial conditions. For custom simulations, I could conceive types of simulations that don't even require a ground node or independent source.
So a valid circuit would depend on the context and an IsValid flag would need a lot of assumptions (which is currently the case by the way). I'm considering to remove the Validate() method altogether.

This has been dealt with using circuit validators.


Add way to set language using Context

Is your feature request related to a problem? Please describe.
In Next.js 13, you can't push a state object and should only push the href, so that we can push like router.push('/home/en') but this seems a bit weird.
Also we have a context that providing current locale, so we probably could make a setter for context to set current language.
Describe the solution you'd like
^Above is all
Describe alternatives you've considered
We can do as like I've said above, that we can use router.push('/home/en') or whatever root (/) will fallback to defaultLocale.

Hello @rikusen0335, I think you're looking for this: https://next-intl-docs.vercel.app/docs/next-13/server-components#routing
Does this help?

Thank you for your response!
Well no, it's not. It's considered alternative for me, and I thought if there was a way to get current lang from context (meant provider)

Okay I changed issue title, this could be more particular

I thought if there was a way to get current lang from context

You can get the current locale via useLocale. It might be from context in case of Client Components, but could also be a URL segment in Server Components.

Add way to set language using Context

In Next.js 13, with Server Components, there is no context—the URL is the source of truth for the current locale. Therefore changing the locale really means changing the URL, which is what the routing APIs I've mentioned above are for.
Does that help?

You can get the current locale via useLocale. It might be from context in case of Client Components, but could also be a URL segment in Server Components.

Okay, wait, my brain is really dying today. I meant to say if there's way to set lang through context.

In Next.js 13, with Server Components, there is no context—the URL is the source of truth for the current locale. Therefore changing the locale really means changing the URL, which is what the routing APIs I've mentioned above are for.

Oh that's too bad...
So as I understand, is that we can't set language without using router? Something like state can't be used, because of server components (rendered in node.js server actually)

Yep, that's correct!
Can the routing APIs be used for your use case? I'd close this issue then.

Yes, thank you for the help!

@amannn the only problem with routing API is the state is become reseted. Any solution for this kind of problem?


chromium versions that match puppeteer release versions.

Project description
Puppeteer (https://github.com/GoogleChrome/puppeteer) is a nodejs package that lets you control (headless) Chromium/Chrome instances. It is the state of the art to do so.
As stated, a given puppeteer version should go along with a specific Chromium version. The versions can be found on the Puppeteer release page (https://github.com/GoogleChrome/puppeteer/releases)
While one can package puppeteer, or more specifically puppeteer-core (latter doesn't try to automatically download the right Chromium version, which wouldn't work as-is on NixOS anyway) using node2nix, but the Chromium already packaged in nixpkgs is of course a different version.
At the most basic, would be nice to supply chromium derivations for the versions listed on above release page. As a bonus step, puppeteer could be packaged, pointing to those versions.
Thank you!

Packaging puppeteer would also enable packaging https://github.com/sportradar/aws-azure-login

It's hard to imagine even one puppeteer-specific revision being built on hydra. (See current discussion of adding a second chromium version: #82443.) Is there a reasonable way to maintain packages in nixpkgs and build/cache them elsewhere? If not, would this be better maintained outside the tree?

Mermaid has since been merged which appears to use an arbitrary chromium version with puppeteer. Mermaid probably doesn't make very extensive use of puppeteer but it's notable that there's now an instance of using puppeteer with an unsupported chromium version in nixpkgs.
From pkgs/development/node-packages/default.nix:
    mermaid-cli =<EMAIL_ADDRESS>(
    if stdenv.isDarwin
    then {}
    else {
      nativeBuildInputs = [ pkgs.makeWrapper ];
      prePatch = ''
        export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1
      '';
      postInstall = ''
        wrapProgram $out/bin/mmdc \
        --set PUPPETEER_EXECUTABLE_PATH ${pkgs.chromium.outPath}/bin/chromium
      '';
    });

@ryneeverett As of mermaid-cli v0.3.0, mermaid-cli has been merged into mermaid core. Nixpkgs should replace nodePackages.mermaid with nodePackages.mermaid-cli. I don't know if its usage of puppeteer has changed, but it's possible.

I have added an issue regarding mermaid-cli's deprecation here: https://github.com/NixOS/nixpkgs/issues/116951


building STIR C++ programs needs libitk-devel and libboost-headers

Currently, libitk-devel is not in our run section. This means that ITK include files etc might not be present unless it is installed manually. See https://github.com/conda-forge/stir-feedstock/issues/101#issuecomment-2294811024_
We could add libitk-devel to run, but a longer term solution is to have a libstir-devel package. To do this properly, it'd be best to have CMake COMPONENTS in STIR. Then it seems straightforward (!) to follow the libitk recipe, e.g. https://github.com/conda-forge/libitk-feedstock/blob/1374e15747412aee18c34db2273abc89a9262c70/recipe/meta.yaml#L57-L62 and https://github.com/conda-forge/libitk-feedstock/blob/1374e15747412aee18c34db2273abc89a9262c70/recipe/libitk-devel_install.sh#L2-L3

A similar problem is that libboost-headers is not exported as a run dependency.


rmz urlrewriter: fixed bug ...

.. that may lose links if another plugin adds links to the urls field of an entry before the urlrewriter is executed.
So far this only occurred to me on another site (rlsbb) where the rss plugin already finds urls in enclosures. So this bug does not currently affect users but it might in the future, if rmz adds enclosures.
Motivation for changes:
bugfix
Detailed changes:

the plugin now checks whether there is already an urls field in the entry and adds the contained links to its list of urls to process.

Thanks :)


avatar：修复IE兼容性问题

Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

偶现图片错位问题。

Please break up two PR.
And  there is also another includes issue https://github.com/ElemeFE/element/blob/dev/packages/cascader/src/cascader.vue#L537.


Conscription

I think there should be a reform table for conscription because multiple countries that have abandoned conscription such as Lithuania have reintroduced it in recent years. If conscription was added to the mod it would be a significant factor in determining the number of units is gained by mobilisation for example perhaps fitting into the fall of america issue #1026  a progressive government would be in favour of reducing the years of service a conscript has to serve until conscription is abolished entirely paving a transition to an all volunteer military while a militaristic government would gradually increase the number of years a conscript has to serve. This system would be very similar to the conscription used in the PDM mod.

Likewise Sweden has also reintroduced conscription. I suggest taking it as part of #1026 and not as a separate issue.

Ok


Add Adon AI

Adding Adon smart recruiter to the list Adon AI

Awesome, You can also add it on Altern


Add artic v4 primers

add these
https://github.com/artic-network/artic-ncov2019/tree/master/primer_schemes/nCoV-2019/V4

Added in commit https://github.com/Psy-Fer/interARTIC/commit/ad4a2624c275954781c740a786485f9f97d4a281

tries to download the primers, which we want to give manually. need to block that method.

Ahh, the issue is the name changed from nCoV-2019 to SARS-CoV-2. This then fails the check to see if the reference.fasta and the scheme.bed files exist.
For now, I'll duplicate the files with the name change, and patch this in the future.


Additional class for column

Hi,
I think it would be useful to be able to add additional classes to form column. By example to add some offset class or similar.
Plus, some components (checkboxes by example) are not aligning properly so sometime I add to column:  d-flex align-items-center

I just seen now the row-attributes. So this can be closed.


Best Practices on Setting TimeOut between PowerBI and Kusto

I've been struggling with the best way to increase Kusto's 4 minute default timeout and so far I have not been successful.
I've tried a few different ways...so I thought I'd ask for "Best practices of increasing the Kusto default timeout"  to be included in "Best Practices"
I have successfully increased the timeout in Kusto Explorer to 59 minutes and received data from a query that ran for 30 minutes.  I followed these instructions:
https://docs.microsoft.com/en-us/azure/data-explorer/kusto/concepts/querylimits
I use this "Query to PowerBI" button to move query from Kusto to PowerBI
https://docs.microsoft.com/en-us/azure/data-explorer/power-bi-imported-query
After pasting in PowerBI,  I see this in the Advanced Query window (note the two(2) instances of 59 representing 59 minutes)
",#"x-ms-app"="PowerQuery",#"properties"="{""Options"":{""servertimeout"":""00:59:00"",""query_language"":""csl""},""Parameters"":{},""ClientRequestId"":null,""Application"":null,""User"":null,""PrincipalIdentity"":null,""SecurityToken"":null,""AuthorizationScheme"":null,""RequestHostName"":null,""LocalClusterName"":null,""OriginClusterName"":null}"], Timeout=#duration(0,0,59,0)])),
TypeMap = #table(

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

ID: 082142f3-9558-d472-c85b-459b956480a1
Version Independent ID: 3beb35b6-5885-9367-9fc0-2c4fe6b7b824
Content: Query limits - Azure Data Explorer
Content Source: data-explorer/kusto/concepts/querylimits.md
Service: data-explorer
GitHub Login: @orspod
Microsoft Alias: orspodek

@orspod Can you please review this ask?

@MRBreen thanks for your feedback.
@Gabilehner and @saguiitay can you assist with this question.

@Gabilehner and @saguiitay can you assist with this question.

Hi MRBreen,
First I would recommend you move to Azure Data Explorer native connector to Power BI - https://docs.microsoft.com/en-us/azure/data-explorer/power-bi-connector
The native connector provides more flexibility as it allows also creating DirectQuery datasets and not just import datasets.
In addition, it is the main way to connect which means it is constantly updated and maintained.
The query you've pasted above should work, so we would like to take a closer look at it.
Please contact me directly with more details -<EMAIL_ADDRESS>Thanks,
Gabi

@MRBreen - thanks for your feedback. I hope this resolves your issue.

@orspod Thanks.  I followed up with an email to @Gabilehner.

@MRBreen  We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

@MRBreen - were you able to resolve the issue ? and how ?


hubble: Username Proofs http API no longer returns Proofs with the type "USERNAME_TYPE_FNAME"

What is the bug?
Previously, it was possible to obtain Proofs of type "USERNAME_TYPE_FNAME" from the Username Proofs http API to acquire custody addresses. However, it now only returns Proofs of type "USERNAME_TYPE_ENS_L1," which is inconsistent with the documentation's description of this http API.
{
    "proofs": [
        {
            "timestamp":<PHONE_NUMBER>,
            "name": "varunsrin.eth",
            "owner": "0x182327170fc284caaa5b1bc3e3878233f529d741",
            "signature": "zCEszPtiesKv6mAEKq796dR/HMoO7yobmbtpAb+7AmAlnG5+cyilF3f6bmTUAF1iU+h4XpaV23n7nzqxTiFqVBs=",
            "fid": 2,
            "type": "USERNAME_TYPE_ENS_L1"
        }
    ]
}

Documentation Description
userNameProofsByFid
Get a list of proofs provided by an FID
Query Parameters

Parameter
Description
Example

fid
The FID being requested
fid=2

Example
curl http://<IP_ADDRESS>:2281/v1/userNameProofsByFid?fid=2

Response
{
  "proofs": [
    {
      "timestamp":<PHONE_NUMBER>,
      "name": "v",
      "owner": "0x4114e33eb831858649ea3702e1c9a2db3f626446",
      "signature": "bANBae+Ub...kr3Bik4xs=",
      "fid": 2,
      "type": "USERNAME_TYPE_FNAME"
    },
    {
      "timestamp":<PHONE_NUMBER>,
      "name": "varunsrin.eth",
      "owner": "0x182327170fc284caaa5b1bc3e3878233f529d741",
      "signature": "zCEszPt...zqxTiFqVBs=",
      "fid": 2,
      "type": "USERNAME_TYPE_ENS_L1"
    }
  ]
}

How can it be reproduced? (optional)
Include steps, code samples, replits, screenshots and anything else that would be helpful to reproduce the problem.
https://nemes.farcaster.xyz:2281/v1/userNameProofsByFid?fid=2
https://github.com/farcasterxyz/hub-monorepo/blob/6ef0638492ea2aada241f5b0c55696737e152f37/apps/hubble/www/docs/docs/httpapi/usernameproof.md#usernameproofsbyfid
Additional context (optional)
Ideally, Proofs of both types（USERNAME_TYPE_FNAME and USERNAME_TYPE_ENS_L1） would be returned.

related to https://github.com/farcasterxyz/hub-monorepo/issues/1584


Add integration test package

Including a simple robot does not drift test
To run the test start the simulation, and then run:
$ ros2 run noah_integration_tests noah_integration_tests_odometry_drift_test

You should see an output like this:
root@4baecc5911cd:/colcon_ws# ros2 run noah_integration_tests noah_integration_tests_odometry_drift_test
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from OdometryDriftTest
[ RUN      ] OdometryDriftTest.IsDriftAccetable
[INFO] [1673268422.869056054] [odometry_drift_test]: First odom message received!.
[INFO] [1673268422.918131082] [odometry_drift_test]: Currently accumulated drift: 0.000001
[INFO] [1673268422.965896321] [odometry_drift_test]: Currently accumulated drift: 0.000002
[INFO] [1673268423.016283535] [odometry_drift_test]: Currently accumulated drift: 0.000002
[INFO] [1673268423.353383486] [odometry_drift_test]: Currently accumulated drift: 0.000003
[INFO] [1673268423.353466533] [odometry_drift_test]: Currently accumulated drift: 0.000004
[INFO] [1673268423.353511458] [odometry_drift_test]: Currently accumulated drift: 0.000005
[INFO] [1673268423.353546554] [odometry_drift_test]: Currently accumulated drift: 0.000006
[INFO] [1673268423.353698260] [odometry_drift_test]: Currently accumulated drift: 0.000006
[INFO] [1673268423.353740149] [odometry_drift_test]: Currently accumulated drift: 0.000007
[INFO] [1673268423.366899479] [odometry_drift_test]: Currently accumulated drift: 0.000008
[INFO] [1673268423.420928907] [odometry_drift_test]: Currently accumulated drift: 0.000009
[INFO] [1673268423.471269894] [odometry_drift_test]: Currently accumulated drift: 0.000010
[INFO] [1673268423.522373472] [odometry_drift_test]: Currently accumulated drift: 0.000010
[INFO] [1673268423.569856206] [odometry_drift_test]: Currently accumulated drift: 0.000011
[INFO] [1673268423.619760290] [odometry_drift_test]: Currently accumulated drift: 0.000012
[INFO] [1673268423.671839748] [odometry_drift_test]: Currently accumulated drift: 0.000013
[INFO] [1673268423.718960189] [odometry_drift_test]: Currently accumulated drift: 0.000013
[INFO] [1673268423.770886849] [odometry_drift_test]: Currently accumulated drift: 0.000014
[       OK ] OdometryDriftTest.IsDriftAccetable (1012 ms)
[----------] 1 test from OdometryDriftTest (1012 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (1024 ms total)
[  PASSED  ] 1 test.

If the simulation is not running, the test will fail as there are no odometry messages, and the drift is infinity:
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from OdometryDriftTest
[ RUN      ] OdometryDriftTest.IsDriftAccetable
/colcon_ws/src/noah_integration_tests/test/odometry_drift_test.cpp:87: Failure
Expected: (accumulated_drift_) <= (1e-3), actual: inf vs 0.001
Accumulated drift too high.
[  FAILED  ] OdometryDriftTest.IsDriftAccetable (1015 ms)
[----------] 1 test from OdometryDriftTest (1015 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (1015 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] OdometryDriftTest.IsDriftAccetable

 1 FAILED TEST

You can also run the test using colcon test:
root@Eskarina:/colcon_ws# colcon test --event-handlers console_direct+
Starting >>> noah_description
Finished <<< noah_description [0.04s]
Starting >>> noah_gazebo
Finished <<< noah_gazebo [0.06s]
Starting >>> noah_integration_tests
UpdateCTestConfiguration  from :/colcon_ws/build/noah_integration_tests/CTestConfiguration.ini
Parse Config file:/colcon_ws/build/noah_integration_tests/CTestConfiguration.ini
   Site: buildkitsandbox
   Build name: (empty)
 Add coverage exclude regular expressions.
SetCTestConfiguration:CMakeCommand:/usr/bin/cmake
Create new tag: 20230110-0946 - Experimental
UpdateCTestConfiguration  from :/colcon_ws/build/noah_integration_tests/CTestConfiguration.ini
Parse Config file:/colcon_ws/build/noah_integration_tests/CTestConfiguration.ini
Test project /colcon_ws/build/noah_integration_tests
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
    Start 1: noah_integration_tests_odometry_drift_test

1: Test command: /usr/bin/python3 "-u" "/opt/ros/foxy/share/ament_cmake_test/cmake/run_test.py" "/colcon_ws/build/noah_integration_tests/test_results/noah_integration_tests/noah_integration_tests_odometry_drift_test.gtest.xml" "--package-name" "noah_integration_tests" "--output-file" "/colcon_ws/build/noah_integration_tests/ament_cmake_gtest/noah_integration_tests_odometry_drift_test.txt" "--command" "/colcon_ws/build/noah_integration_tests/noah_integration_tests_odometry_drift_test" "--gtest_output=xml:/colcon_ws/build/noah_integration_tests/test_results/noah_integration_tests/noah_integration_tests_odometry_drift_test.gtest.xml"
1: Test timeout computed to be: 60
1: -- run_test.py: invoking following command in '/colcon_ws/build/noah_integration_tests':
1:  - /colcon_ws/build/noah_integration_tests/noah_integration_tests_odometry_drift_test --gtest_output=xml:/colcon_ws/build/noah_integration_tests/test_results/noah_integration_tests/noah_integration_tests_odometry_drift_test.gtest.xml
1: [==========] Running 1 test from 1 test case.
1: [----------] Global test environment set-up.
1: [----------] 1 test from OdometryDriftTest
1: [ RUN      ] OdometryDriftTest.IsDriftAccetable
1: [INFO] [1673343960.820459652] [odometry_drift_test]: First odom message received!.
1: [INFO] [1673343960.879023392] [odometry_drift_test]: Currently accumulated drift: 0.000001
1: [INFO] [1673343960.927109838] [odometry_drift_test]: Currently accumulated drift: 0.000002
1: [INFO] [1673343960.979029327] [odometry_drift_test]: Currently accumulated drift: 0.000002
1: [INFO] [1673343961.024011861] [odometry_drift_test]: Currently accumulated drift: 0.000003
1: [INFO] [1673343961.073021826] [odometry_drift_test]: Currently accumulated drift: 0.000004
1: [INFO] [1673343961.124044380] [odometry_drift_test]: Currently accumulated drift: 0.000005
1: [INFO] [1673343961.177766612] [odometry_drift_test]: Currently accumulated drift: 0.000005
1: [INFO] [1673343961.228301524] [odometry_drift_test]: Currently accumulated drift: 0.000006
1: [INFO] [1673343961.276068266] [odometry_drift_test]: Currently accumulated drift: 0.000007
1: [INFO] [1673343961.323874034] [odometry_drift_test]: Currently accumulated drift: 0.000008
1: [INFO] [1673343961.374286623] [odometry_drift_test]: Currently accumulated drift: 0.000009
1: [INFO] [1673343961.422902574] [odometry_drift_test]: Currently accumulated drift: 0.000009
1: [INFO] [1673343961.476271266] [odometry_drift_test]: Currently accumulated drift: 0.000010
1: [INFO] [1673343961.526372386] [odometry_drift_test]: Currently accumulated drift: 0.000011
1: [INFO] [1673343961.588337566] [odometry_drift_test]: Currently accumulated drift: 0.000012
1: [INFO] [1673343961.633424678] [odometry_drift_test]: Currently accumulated drift: 0.000012
1: [INFO] [1673343961.677475621] [odometry_drift_test]: Currently accumulated drift: 0.000013
1: [INFO] [1673343961.723505207] [odometry_drift_test]: Currently accumulated drift: 0.000014
1: [INFO] [1673343961.773711326] [odometry_drift_test]: Currently accumulated drift: 0.000015
1: [       OK ] OdometryDriftTest.IsDriftAccetable (1024 ms)
1: [----------] 1 test from OdometryDriftTest (1024 ms total)
1:
1: [----------] Global test environment tear-down
1: [==========] 1 test from 1 test case ran. (1024 ms total)
1: [  PASSED  ] 1 test.
1: -- run_test.py: return code 0
1: -- run_test.py: inject classname prefix into gtest result file '/colcon_ws/build/noah_integration_tests/test_results/noah_integration_tests/noah_integration_tests_odometry_drift_test.gtest.xml'
1: -- run_test.py: verify result file '/colcon_ws/build/noah_integration_tests/test_results/noah_integration_tests/noah_integration_tests_odometry_drift_test.gtest.xml'
1/1 Test #1: noah_integration_tests_odometry_drift_test ...   Passed    1.16 sec

100% tests passed, 0 tests failed out of 1

Label Time Summary:
gtest    =   1.16 sec*proc (1 test)

Total Test time (real) =   1.16 sec
Finished <<< noah_integration_tests [1.22s]

Summary: 3 packages finished [1.57s]

(but you also need to run the simulation first)
Closes #9

Regarding starting the simulation manually, we want to run this in robomaker, which starts the simulation and the robot code as two different things, so I wanted to accommodate that workflow.
It would be nice to also gett launch_testing or colcon test integration. We could add that as a follow up issue.

Ok, now colcon test will run the test (but you need to start the simulation first)

@francocipollone I added a commit that closes issue #14 as the PR was not merged yet (and I cannot merge PRs)


make install-for-dev is failing to install python modules

I tried to install the plugin for development using make, and I had this below issue which is not able to install some dependencies.
pip-compile -o requirements/test.txt requirements/test.in
  ERROR: Cannot install -r requirements/test.in (line 8) because these package versions have conflicting dependencies.
Traceback (most recent call last):
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 316, in _backjump
    name, candidate = broken_state.mapping.popitem()
KeyError: 'dictionary is empty'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 92, in resolve
    result = self._result = resolver.resolve(
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 434, in resolve
    success = self._backjump(causes)
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 318, in _backjump
    raise ResolutionImpossible(causes)
pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('redis<4.4'), parent=LinkCandidate('https://files.pythonhosted.org/packages/6b/d1/05dcf84b58ad53ac21e17fc48045f1932a39ef3b41f115013e44abac2f8e/fakeredis-1.9.1-py3-none-any.whl (from https://pypi.org/simple/fakeredis/) (requires-python:>=3.7,<4.0)'))]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/bin/pip-compile", line 8, in <module>
    sys.exit(cli())
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/piptools/scripts/compile.py", line 630, in cli
    results = resolver.resolve(max_rounds=max_rounds)
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/piptools/resolver.py", line 604, in resolve
    is_resolved = self._do_resolve(
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/piptools/resolver.py", line 636, in _do_resolve
    resolver.resolve(
  File "/home/ubuntu/Projects/Seita/flexmeasures-openweathermap/venv/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 101, in resolve
    raise error from e
pip._internal.exceptions.DistributionNotFound: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
make[1]: *** [Makefile:36: freeze-deps] Error 1
make[1]: Leaving directory '/home/ubuntu/Projects/Seita/flexmeasures-openweathermap'
make: *** [Makefile:17: install-for-dev] Error 2

Because of this issue, github actions are also failing.

Let's try make upgrade-deps first

this would upgrade the dependencies but my concern is about install-for-dev.

Which installs dependencies...

yes.

The issue is raising because of fakeredis latest version which is 0.17.0. If we downgrade it to 0.16.0 then we can close this issue. @