Execute @BeforeClass before resolving @Parameters

The test below will throw an exception because getAwesomeParameters is called before setupEnvironment and RequiresJniLibrary requires that the libraries are loaded to be instantiated.
I would like to see JUnitParamsRunner updated so that any methods annotated with @BeforeClass are called before @Parameters annotations are resolved.
@RunWith(JUnitParamsRunner.class)
public final class ReallyCoolClassTests {

    @BeforeClass
    public final void setupEnvironment() {
      LibraryLoader.loadJniLibraries();
    }

    @Test
    @Parameters(method = "getAwesomeParameters()")
    public final void doSomethingAwesome_withDependency_returnsExpected(
        final RequiresJniLibrary dependency, final boolean expected) {
        final ReallyCoolClass subjectUnderTest = new ReallyCoolClass(dependency);

        final boolean result = subjectUnderTest.doSomethingAwesome();

        Assertions.assertThat(result).isEqualTo(expected);
    }

    private final Object getAwesomeParameters() {
      return new Object[][]{
          {new RequiresJniLibrary(1), true},
          {new RequiresJniLibrary(2), false}
      };
    }
}

See #37 for why that's not possible at the moment.
However, changing your setupEnvironment() to a plain static initializer should solve your issue since a static initializer is executed at class loading time, which must happen before any class method is executed, so before getAwesomeParameters().

I'm not looking for why this isn't possible at the moment. I'm requesting this is supported in the future.


Change build and clean to get target from package.json

Changed build and clean to get target configuration and webpack public paths from package.json.

Coverage remained the same at 94.595% when pulling 5a4feb792558fa615c00cbd70bcfcb26157d4da9 on raythree:build-config-changes into 134b5f9b7dfcc3619a2af604e824f539b386ea47 on coryhouse:master.

Coverage remained the same at 90.476% when pulling bcd13c452fbe6cb035ea69a9f53988579cf71c70 on raythree:build-config-changes into 15963df1cb511add2e6ee7b16cdaf6441e02754d on coryhouse:master.

Coverage remained the same at 90.476% when pulling 0aac32ec784208b349842ff945ae65991c552d62 on raythree:build-config-changes into b69802f507a6ec3aa61c0565714ac16ce773d0a5 on coryhouse:master.

it would be nice if these configs would be asked during setup


Release current state

Please create a release with the current state, since chrono v3 is broken otherwise.
Cheers.

Published 0.10 which uses chrono 0.3. Thanks!

Great, thanks


[Qustion] Why SDXL Lora has no effects in stable diffusion webui

I found the webui version in the end, but still, really interested in the difference between these 2 versions, and what should we do to transfer one into another one?

They are the same. I converted the checkpoint of diffusers to the webui format for user convenience.

They are the same. I converted the checkpoint of diffusers to the webui format for user convenience.

fine, thanks


Unexpected behaviour

I wrote some bindings to the java.util.zip.Adler32 library, but I am experiencing some issues. Here's the code:
{-# LANGUAGE MagicHash #-}
module Main where

import Java
import Data.Word (Word8)
import GHC.CString

-- ================================================================================
-- java.util.zip.Adler32
-- ================================================================================

data {-# CLASS "java.util.zip.Adler32" #-} Adler32 = Adler32 (Object# Adler32)
  deriving Class

foreign import java unsafe "@new" newAdler32 :: Java a Adler32
foreign import java unsafe getValue :: Java Adler32 Int64
foreign import java unsafe reset :: Java Adler32 ()
foreign import java unsafe "update" updateInt :: Int -> Java Adler32 ()
foreign import java unsafe "update" updateBytes :: JByteArray -> Java Adler32 ()
foreign import java unsafe "update" updateBytesOffLen :: JByteArray -> Int -> Int -> Java Adler32 ()

-- Version of updateInt that works as expected
-- updateInt only uses the lower 8 bytes of its input
updateWord8 :: Word8 -> Java Adler32 ()
updateWord8 = updateInt . fromIntegral

main :: IO ()
main = java $ do
  a <- newAdler32
  io.print =<< a <.> getValue
  a <.> updateWord8 10
  io . print =<< a <.> getValue

This should print:
1
720907

But it prints:
1
1

Have I done something wrong?

No you have done nothing wrong. Looks like a subtle bug. I have a suspicion that a <.> getValue is getting shared. I took a look at the generated code and it's not executing getValue() twice as it should. Will investigate further.

{-# LANGUAGE MagicHash #-}
module Main where

import Java
import Data.Word (Word8)
import GHC.CString
import System.IO

-- ================================================================================
-- java.util.zip.Adler32
-- ================================================================================

data {-# CLASS "java.util.zip.Adler32" #-} Adler32 = Adler32 (Object# Adler32)
  deriving Class

foreign import java unsafe "@new" newAdler32 :: IO Adler32
foreign import java unsafe getValue :: Java Adler32 Int64
foreign import java unsafe reset :: Java Adler32 ()
foreign import java unsafe "update" updateInt :: Int -> Java Adler32 ()
foreign import java unsafe "update" updateBytes :: JByteArray -> Java Adler32 ()
foreign import java unsafe "update" updateBytesOffLen :: JByteArray -> Int -> Int -> Java Adler32 ()

-- Version of updateInt that works as expected
-- updateInt only uses the lower 8 bytes of its input
updateWord8 :: Word8 -> Java Adler32 ()
updateWord8 = updateInt . fromIntegral

main :: IO ()
main = do
  adler <- newAdler32
  javaWith adler $ do
    io.print =<< getValue
    updateWord8 10
    io . print =<< getValue

This gives the correct output. I need to add a warning about mutating Java objects in the docs.

This bug is strikingly similar to https://ghc.haskell.org/trac/ghc/ticket/5916. To make things safe, we just need to implement the runRW# primitive (present in GHC 8) which is a very clean solution.

The final fix involved:

Backporting runRW# from GHC 8 which was more involved than expected (had to backport a lot of other features too to make sure it doesn't kill perf), but this only took care of taking out realWorld# from the array operations.
Adding new primops that generate fresh state tokens & object tokens:

freshStateToken# :: a -> State# s
freshObjectToken# :: a -> Object# b -> Object# b
freshNullObjectToken# :: a -> Object# b

Where the a's are levity-polymorphic (accepts types of kinds * and #). Eta currently does not support language-level expression of levity polymorphism which is ok - it keeps the types simple.
Basically these primops generate a hard dependency and prevents the Float Out transformation in the simplifier from destroying the meaning of the original program. The cool part is that all these primops are essentially nops when the code generator gets around to it, so they add no runtime cost.


[Filter] Remove "Title"-Filter

Suggestion:
It would be cool if you remove "Title"-Filter in usdb-syncer.
Why:

This filter lists every title of the whole usdb. Which doesn't make sense as a dropdown-select field (with over 10.000 entries).
Titles should be just searched in the searchfield.

Estimation

Filler task: low effort, low impact.

Thank you 🚀

I agree that it doesn't help with finding songs. However, after the last GUI rework (apart from ditching the dropdown) it allows you to filter for specific titles, which the free text search field doesn't.
Maybe you're still right, but since it doesn't cause any harm, I would first like to see how it pans out in its new form before removing it.

That's fine for me, take your time and try things out. Thanks for making syncer possible 🙏


Select a single AZ for a machine pool in a multi-AZ cluster

Add availability-zone and multi-availability-zone flags to the create machine pool command.
Related: SDA-6155

@zgalor @pvasant PTAL

LGTM.
Let's wait for @pvasant 's approval for merging

OTher than two it looks good to me

/lgtm


refactor: defaultConfig -> processEnvConfig

A more accurate name?
⚠  base not master

May reopen and rebase when things are quieter!


Fix Spring Authorization Server Reference hyperlink on README.adoc

The hyperlink for the 'Spring Authorization Server Reference' on README.adoc was incorrect and points to an non existing resource. It redirects the user to 'https://docs.spring.io/spring-authorization-server/docs/current/reference/html/' instead of 'https://docs.spring.io/spring-authorization-server/reference/'
Have updated the README.adoc with the correct url.

Thanks for the update @OSKUDA! This is now merged.


New mutators

Summary
maybe good mutators could be made of:

> -> <
> -> === (etc)
== -> === -> ==
!= -> == -> !=
{ some object } -> {}
remove all cases from switch and leave only default

Based on https://stryker-mutator.io/mutators.html

Thanks for opening an issue for this!
We already support:

> -> <
== -> ===
=== -> ==
!= -> ==
== -> !=

Mutating case statements and switch statements sounds interesting! I don't really understand what you mean with

> -> === (etc)
Could you be more specific on that one? Why is this a construction that you think should be changed?

@simondel etc v

< -> ===
> -> ===
>= -> ===
<= -> ===
It would test another cases.

Also i would like to notice that on your official page -> > -> <; == -> === are not included; https://stryker-mutator.io/mutators.html

My bad! We actually don't have these mutators that I claimed we have.

> -> < is already covered by > -> <=
== -> ===  will almost never cause an issue and the use of == is not recommended
=== -> == should never cause any issues except for linting

We could add the above mutators (same goes for the > -> === etc.) but since they are will almost never cause an issue that is not found using other mutators, I believe it's not the smartest move to add them. They will increase the time it takes to run stryker while not providing a lot of value.
 You could also try emptying each object like Int8Array etc but i dunno if it won't cause some issue (or can be hard to implement)

@simondel i think this object replacer would look sth like
import { types } from 'babel-core';
import NodeMutator from './NodeMutator';
export default class ObjectExpressionMutator implements NodeMutator {
  name = 'ObjectExpressionMutator';

  mutate(node: types.Node, copy: <T extends types.Node>(obj: T, deep?: boolean) => T): void | types.Node[] {
    let nodes: types.Node[] = [];

     /* PseudoCode */
     if(typeof node === "object") {
         if(node.length > 0) {
            node = new (node.constructor.name)();
        }
        nodes.push(node);
     }
     return nodes;
  }
}

I second the object mutators. I just had some tests pass that in one of my projects that should not have passed if the object was emptied.

I'm closing this issue, since now have 2 new mutators! (Thanks @tommilligan, @kmdrGroch ). Please report a new issue per proposal from now on (so it is easier for issue tracking) 👍


Fails to load component

When trying to run the extension and preview a component, displays an error that the previewConfiguration.json file cannot be found. Looks like it's attempting to access the wrong folder - C:\c:\..

@scooby359 I'm assuming you are using the windows operating system? This extension only works on mac operating system for now.

@unwls Ah yes, I'm on Windows. Just looked at the extension page in VS Code, realised it doesn't mention being Mac only until half way down the page. Maybe that could be made more prominent in the extension description.


Update README.md

Replace Sqlite with Postgresql

Why? This isn't true :) Only the sync server uses postgres

I'm so sorry. I didn't read everything. Self-righteous modified README.md

haha, that's ok!

Please allow me to write Chinese documentation for this project,
I will create a new directory under the docs directory to store all the translation files.

Of course! That would be fantastic :)


Ability to choose easing curve

This is really awesome, thanks! One minor feature request - is there a way to change the transition easing curve? You can change the durations, but the easing curve appears to be hard-coded to easeExpInOut which I find a bit "snappy". I think this is the relevant code:
function newCubeLayer(presenter, config, cubeData, highlightColor, lightSettings, lightingMix, interpolator) {
    const getPosition = getTiming(config.transitionDurations.position, easeExpInOut);
    const getSize = getTiming(config.transitionDurations.size, easeExpInOut);
    const getColor = getTiming(config.transitionDurations.color);

Just needs a config.transitionCurve or something too.

Thanks for the request @Timmmm. This would make a good first PR - begin by copying TransitionDurations in interfaces.ts: https://github.com/microsoft/SandDance/blob/011ac1e7d444b4f3b24b64ad96359814f0ee07b5/packages/sanddance/src/vega-deck.gl/interfaces.ts#L119
to create TransitionEasings, like this:
export interface TransitionEasings {
    color?: (t: number) => number;
    position?: (t: number) => number;
    size?: (t: number) => number;
    view?: (t: number) => number;
}

then add it to PresenterConfig:
https://github.com/microsoft/SandDance/blob/011ac1e7d444b4f3b24b64ad96359814f0ee07b5/packages/sanddance/src/vega-deck.gl/interfaces.ts#L130
and finally to the place you mentioned in newCubeLayer:
https://github.com/microsoft/SandDance/blob/54e14a0bf865b6dbd0ff4fe74b073f65eff26583/packages/sanddance/src/vega-deck.gl/layers.ts#L55
That would take care of the Presenter which integrates with deck.gl
Next, we add it to the SandDance Viewer by copying TransitionDurations in types.ts:
https://github.com/microsoft/SandDance/blob/1e3e1f766b852a6b9cc7ffbbe92ce03d69d8d5b6/packages/sanddance/src/types.ts#L49
to create TransitionEasings at the next level, and adding it to ViewerOptions:
https://github.com/microsoft/SandDance/blob/1e3e1f766b852a6b9cc7ffbbe92ce03d69d8d5b6/packages/sanddance/src/types.ts#L90
Lastly, we can add it to the defaultPresenterConfig in viewer.ts in the createConfig function:
https://github.com/microsoft/SandDance/blob/54e14a0bf865b6dbd0ff4fe74b073f65eff26583/packages/sanddance/src/viewer.ts#L540
Hope that makes sense.

Hey @danmarshall  , can i take up this issue ?

Hi @imrishabh18 , yes please and thank you!

What should I add at layer.ts file for TransitionEasings ?

@imrishabh18 - not sure what you are asking exactly... do you mean https://github.com/microsoft/SandDance/blob/master/packages/vega-deck.gl/src/layers.ts#L54 ?


Validate metadata for Covid Tracking Project

There are some discrepancies between the metadata file we received and the published data on the CTP CRDT website. We should make sure our metadata is correct, decide how to handle inconsistencies, and document any edits we need to make.

We have reached out to CTP to ask about discrepancies in the metadata, but haven't heard back yet. The known discrepancies and open questions are described as follows:

There are a few mismatches between the race & ethnicity combined vs. separate columns for cases and deaths in the metadata spreadsheet:

GA: Website card, dashboard, and data = combined. Metadata = separate.
MS: Website card, dashboard, and data = combined. Metadata = separate.
MN: Website card, dashboard, and data = separate. Metadata = combined.
For WY, everything matches except for the website card:
WY: Website dashboard, data, and metadata = combined. Website card = separate.

WY's website card is also saying right now that 0% of cases report race and ethnicity. So maybe WY's card is having a separate, unrelated issue?

NC and SC don't match between the website and the metadata spreadsheet for API. Both are listed as "Yes" for API-cases in the spreadsheet but their website cards show Asian on its own without Pacific Islander, and the dashboard has the note that NC/SC don't say if Pacific Islander is included in Other. In related news, AL handles Pacific Islander in the same way, and it has API-cases = "No" in the spreadsheet.

We are not certain what "known denominator-cases" means in the metadata spreadsheet. Katrina's guess: whether a state reports the total case count, which helps when a state reports cases as percentages rather than raw numbers. If so, how can AR report the number of cases but have a "No" for "known denominator-cases?"

Based on my [Katrina's] #crdt-web lurking, three states have changed how they report from race & ethnicity combined to separate or vice versa (GA, UT, WY). If a state changes how they report on a certain date, can we assume that cumulative numbers after that date use the new reporting scheme and cumulative numbers before that use the old scheme?

The columns "race & ethnicity combined" and "race & ethnicity separately" appear to have the opposite meanings that one would expect. In the doc Structured Metadata for Covid Tracking Project, we define "race & ethnicity combined" to mean that race numbers include both Hispanic and Non Hispanic and "race & ethnicity separately" to include only Non Hispanic numbers. However, the data on their site seems to indicate that "race & ethnicity combined" corresponds to Non Hispanic only while "race & ethnicity separately" corresponds to both Hispanic and Non Hispanic.

We have reached out to CTP to ask about discrepancies in the metadata, but haven't heard back yet. The known discrepancies and open questions are described as follows:

There are a few mismatches between the race & ethnicity combined vs. separate columns for cases and deaths in the metadata spreadsheet:

GA: Website card, dashboard, and data = combined. Metadata = separate.
MS: Website card, dashboard, and data = combined. Metadata = separate.
MN: Website card, dashboard, and data = separate. Metadata = combined.
For WY, everything matches except for the website card:
WY: Website dashboard, data, and metadata = combined. Website card = separate.

WY's website card is also saying right now that 0% of cases report race and ethnicity. So maybe WY's card is having a separate, unrelated issue?

NC and SC don't match between the website and the metadata spreadsheet for API. Both are listed as "Yes" for API-cases in the spreadsheet but their website cards show Asian on its own without Pacific Islander, and the dashboard has the note that NC/SC don't say if Pacific Islander is included in Other. In related news, AL handles Pacific Islander in the same way, and it has API-cases = "No" in the spreadsheet.

We are not certain what "known denominator-cases" means in the metadata spreadsheet. Katrina's guess: whether a state reports the total case count, which helps when a state reports cases as percentages rather than raw numbers. If so, how can AR report the number of cases but have a "No" for "known denominator-cases?"

Based on my [Katrina's] #crdt-web lurking, three states have changed how they report from race & ethnicity combined to separate or vice versa (GA, UT, WY). If a state changes how they report on a certain date, can we assume that cumulative numbers after that date use the new reporting scheme and cumulative numbers before that use the old scheme?

The columns "race & ethnicity combined" and "race & ethnicity separately" appear to have the opposite meanings that one would expect. In the doc Structured Metadata for Covid Tracking Project, we define "race & ethnicity combined" to mean that race numbers include both Hispanic and Non Hispanic and "race & ethnicity separately" to include only Non Hispanic numbers. However, the data on their site seems to indicate that "race & ethnicity combined" corresponds to Non Hispanic only while "race & ethnicity separately" corresponds to both Hispanic and Non Hispanic.

Another mismatch to add to #1:
FL: Website, card, dashboard, and data = combined. Metadata = separate.

Another mismatch to add to #1:
FL: Website, card, dashboard, and data = combined. Metadata = separate.

Finished this verification with results in this doc: https://docs.google.com/document/d/1lJSc050AetmFCw4JHq0pX8owRtdkrX5Zz8WHMCLK6ak/edit?resourcekey=0-5BxFke_S_4rAqDMc_WYeTw#heading=h.vsf3jfqzfqfu
Both the staging and prod pipelines have been updated with the fixed metadata.


Fix building of utf8.hpp on clang-10 / libstdc++-8

e.g. on Ubuntu 18.04: __cpp_char8_t is indeed >= 201811 as clang-10 already supports a C++20 mode with char8_t, but it uses by default libstdc++'s standard library there which did not provide std::u8string_view at this time

Please provide changed single-header libraries too, you can do it with make single-header(you will probably need to install pip package quom)

also, the change break some of builds, please look at the failures and try to find a workaround

should be fixed now, one build remains when GH can run it: https://github.com/jcelerier/compile-time-regular-expressions/runs/7834679637?check_suite_focus=true

thanks!

thank you :)


The game crashes if you hit the key which is directly opposite to the snake's direction.

#12 is the final fix to this


@jmchilton's GCC Training Homework

Included in this PR:

Tool development using Conda and Bioconda slides. Fixes #231.
Tool development with Containers and BioContainers slides. Fixes #232.
Galaxy Code Architecture slides synchronzied from galaxyproject/galaxy.

I still have a lot I'd like to do but this seems like a workable first draft.
Conda:

[ ] Discussion of merged mulled environments perhaps, more slides about dependency resolution in general?

Containers:

[ ] Update all slides for mulled-v2.
[ ] Update with information on multi-package-containers repository and monitoring tool repositories for missing containers.
[ ] Singularity information.
[ ] Information on newer container-based deployment options - Kubernetes, Chronos, and Condor Docker universe.

Arch:

[ ] Redo startup slides since they may have changed since last year - especially tool monitoring and stuff.
[ ] Add a section about web hooks.

I think that since topics/dev/tutorials/conda/slides.html reuses lots of slides from topics/dev/tutorials/tool-integration/slides.html, it would be good to remove the Conda part from the latter, because:

it was too big and, as discussed at the Cambridge hackathon, it would be good to split some tutorial/slide decks in smaller pieces
having both would inevitably cause a duplication of maintenance effort.

Thoughts? Ping @lecorguille @abretaud

it would be good to remove the Conda part from the latter

Yeah - a few of us discussed this on Gitter and that was agreed to. On my next pass I'll include those changes in this PR.
John Chilton @jmchilton May 30 13:01
Not for planemo - I'm making a new module inside of training-materials - I just want to reuse some of the slides from a different module (maybe module isn't the right word)
It is fine I think - I'll copy and paste for now - an ability to arbitrarily import shared slides would be cool though

Björn Grüning @bgruening May 30 13:03
mh, I think then the correct way is to split the huge slide-deck into smaller onces
we agreed to make it more modular

John Chilton @jmchilton May 30 13:11
@bgruening Fair enough point on breaking the big deck into smaller ones - I'll look at this work I'm doing now as a first step to break the Conda and Dependency Management stuff out of tool integration deck then.

Björn Grüning @bgruening May 30 13:11
Great, thanks!

Gildas Le Corguillé @lecorguille May 31 10:01
:thumbsup:

Has I said, I agree to extract the conda slides from the dev part.

I catched some issue with some pictures in the dev part.
I will fix them as soon as you remove the conda stuff.

No problem for me :+1: :+1:

For me, you can cut from the slide 73 and by this way keep some references to Conda. And eventually, add a link to the new dedicated material.

Yep, till slide 95.

@jmchilton I'm working on removing the Conda slides and other fixes to tool-integration/slides.html, I can push them to your branch if that's OK with you.

@nsoranzo Yes - definitely feel free to push directly to my branch thanks - that will be a huge help!
I've spent the day redoing the Planemo docs for changes in the last couple weeks and so I haven't gotten back to reviewing these slides. I will update the slides for all your inline comments as I make my way back through the slides to synchronize them with the updated Planemo docs.
Thanks for the comments all!

@jmchilton
I plan to remove the Hands-on slides from the tool_integration slides to link the Planemo tutorial.
I will check your last version but maybe I will add some anchors along the tuto if needed.

@lecorguille Please wait for my changes to appear in this PR tomorrow morning, I'm moving some Planemo slides, thanks!

Take your time!
I'm on holiday the evening until the GCC :)

@jmchilton @lecorguille I pushed my changes.
@martenson You may want to take a look at this PR which has the Conda slides removed from the "Tool development and integration" tutorial.
@bebatut @bgruening It would be good to also have a review from one of you core GTN maintainers.

@nsoranzo - I just noticed these slides are broken like described in #358 - I don't know how to fix them. Do you know? I tried the change from that PR but applied to these files and it didn't seem to work.

@jmchilton Broken how? I think tutorial_slides layout should be fine, since they have Hands-on sections.

The questions, objectives, and key points are not being automatically populated from the metadata anymore (they were fine before I rebased against the merged build-pipeline master branch).

I'm going to merge this so we can all work on master for smaller changes. It should now render fine!
Thanks a lot for your work, this looks awesome! To bad I can not see this in action :)


Not working on device (Hololense 2 / iOS)

Everything works perfectly in the editor.
I have tested the app on the Hololense and iOS devices and found that the app does not work properly in WayFinding mode.
After the base point is found and the destination is selected, the app searches for the next anchor. As soon as it is found, it will connect to the base point. From here on the search for new anchors does not work anymore.

Thank you for your feedback!
I'm sorry that I can't tell you how to use this app well.
(I’m translating the 'README.md',so I'm not yet push English version.)

After the base point is found and the destination is selected, the app searches for the next anchor. As soon as it is found, it will connect to the base point. From here on the search for new anchors does not work anymore.

This app doesn't show all the anchors related with the selected destination at once.
Way-Finding mode is the follow operations.

After The base point is found and the destination is selected.
this app search and placement the first point automatically.
If we get close to first visualized anchor,this app search next anchor nearby the anchor.

After The base point is found and the destination is selected, please get close to next visualized anchor.
the app search next anchor. If you don't visualize the next anchor, there is possibility that Azure Spatial Anchors is  failed to search the anchor. In that situation,the app restart(sorry,this sample isn't implement to retry searching).
Would you please confirm it anyway?
Best regards,

Sorry for the delay.
Really great work from you.
On both the Hololens and the iPhone, the App only works up to the first waypoint.
The base point is always found, and you can also choose different destinations. (if different destinations are defined)
As soon as the destination is selected, the next waypoint is found. But from that point on no other waypoint is found.
I took a closer look at your code. I noticed a few things.
Wayfinding:

If the first waypoint is too close to the basepoint and you start the app between both points, the OnTriggerEnter method of the waypoint is executed immediately and the app searches for close anchors. This leads to an exception, because two watcher are created at the same time and this is currently not supported by ASA.
If the first waypoint is about 3 meters away from the base point, it will be found and visualized after selecting the destination. At this time both, the base point and the first waypoint, are visualized. But both points are not connected to each other (no line connects the two points). Only when you get close to the waypoint, the OnTrigger method is executed and the base point is connected to the first waypoint.

In general.
If I have seen this correctly, when creating the waypoints or the endpoint at each anchor properties are saved. These AppProperties contain the type of point (waypoint or endpoint) and the anchor ID of the previous anchor.
This means that when I search for Nearby Anchors, it always searches for the AnchorID of the previous anchor and not for the next Anchor?
To enable universal wayfinding you have to get a direction to the next waypoint as soon as the navigation is started.
Is it not possible to save the relative positions to the previous anchor in the AppProperties to give a direction if the anchor is not in range of the camera and therefore can not be found directly when the OnTriggerEnter method is executed?

Hi florolf1,
Sorry for the delay.
Thank you for sharing the details!

Wayfinding:
1.If the first waypoint is too close to the basepoint and you start the app between both points, the OnTriggerEnter method of the waypoint is executed immediately and the app searches for close anchors. This leads to an exception, because two watcher are created at the same time and this is currently not supported by ASA.
2.If the first waypoint is about 3 meters away from the base point, it will be found and visualized after selecting the destination. At this time both, the base point and the first waypoint, are visualized. But both points are not connected to each other (no line connects the two points). Only when you get close to the waypoint, the OnTrigger method is executed and the base point is connected to the first waypoint.

Thank you for telling this to me.
There was not enough my idea.
At the time,when I share this sample, I had thought some ideas how realizing way-finding with ASA.

searching the next anchor using OnTriggerEnter. (on this time)

searching the next anchor using AirTap.

setting next anchor Id to AddProperties of the current anchor,seraching the next anchor by the anchor id.

and more...
I had supposed the sample of searching the anchors nearby the current anchor is few, so I implement this sample on this time.

To enable universal wayfinding you have to get a direction to the next waypoint as soon as the navigation is started.
Is it not possible to save the relative positions to the previous anchor in the AppProperties to give a direction if the anchor is not in range of the camera and therefore can not be found directly when the OnTriggerEnter method is executed?

Great Idea!!!
Actually I had known this problem(the direction of camera), but I couldn't came up with how to resolve.
I can set the general direction of the next anchor in AppProperties.
I thought the below featrures,what do you think about this?

On setting the route

we set below infomations to AppProperteis of the current anchor.

next anchor id(for searching  the next anchor)
next anchor direction and distance(general).
anchor type(point / destination)
previous anchor id(for visualizing link)
destination title

Way-finding

Setting the base point.
visualize the marker for searching the next anchor direction. This is because that it is guided user to the next anchor direction.
When we exists the marker in range of camera and reach nearby the marker (about 1-2 m,changeable optional variable) , searching automatically the next anchor by 'Anchor Id'.
If CloudSpatialAnchorWatcher already create(searching the net anchor), next anchor search process is ignore until finish searching it in current process.
When the next anchor is loaded, the app visualize 'Link Object'connected between current to next.

Best Regards,
Takahiro

Definition of the route
I would also try (just an idea) to save the direction to the last anchor in the AppProperties. This does not have to be stored in the azure cloud, but can be stored in a separate DB.

I haven't tested it myself yet, so just an idea:
Once the ARSession is started, I can determine the distance and angle between 2 objects created during the AR session.
Additionally ASA offers functions for approximate location:
Coarse relocalization

Wayfinding
that's exactly what I would do

Especially the approximate location sounds very interesting and will certainly be helpful in the implementation.


8 1 1 rebase main candidate

closes #478

Please enter an issue for the tests that are disabled as part of this upgrade.

there already is -
https://github.com/speedb-io/speedb/issues/491
https://github.com/speedb-io/speedb/issues/492
https://github.com/speedb-io/speedb/issues/493
https://github.com/speedb-io/speedb/pull/499

done


⚠ DDoS-Relay US-W-sfo3-01 has degraded performance

In 9b602f6, DDoS-Relay US-W-sfo3-01 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 3195 ms

Resolved: DDoS-Relay US-W-sfo3-01 performance has improved in 0b671af after 43 minutes.


Enhancement: add github integration config GitSavvy.ghBranch

This is needed to produce a correct comparision when the integered
remote is a forked remote.
For example, if the integrated remote is configed as randy3k,
the original code opens
https://github.com/randy3k/GitSavvy/compare/randy3k:comparision?expand=1
However, github redirects it to
https://github.com/divmain/GitSavvy/compare/master...randy3k:comparision?expand=1
To adderss the issue, the new link used is
https://github.com/randy3k/GitSavvy/compare/randy3k:master...randy3k:comparision?expand=1

Actually, I was thinking whether I should use GitSavvy.ghBranch or a project specific settings
as in rebase.

Yeah, I think this would be an appropriate place for the project config.  If we really want to get fancy, we could use the GitHub API to see if the specified remote is a fork, and act accordingly.  Should be able to borrow a lot from here.

I think there is no need for now to check if the remote is a fork as we switched to a more general url format: https://github.com/{}/{}/compare/{}:{}...{}:{}?expand=1 to replace the old format
https://github.com/{}/{}/compare/{}:{}?expand=1
The current implementation should be good enough.

Cool, that sounds reasonable.  One minor change, and then I'll merge this in.

Fixed the typo.


IP anonymization

Due to EU law, IP anonymization is required.
How can you set IP anonymization on vue-gtag library?
https://developers.google.com/analytics/devguides/collection/gtagjs/ip-anonymization

@MatteoGabriele Awesome, thanks for the quick support! I will patiently wait for a solution, and fix our version to 1.6.2 in the meanwhile.

FYI: Removed the other Github account. I'm the Ghost above 😜

Hi! Just checking in wondering what the status of this bug is. Thanks again!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Repo sync for protected CLA branch

The pull request is created from main637933286300328918sync_temp to main to fix git push error for protected CLA branch

@opbld15 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Namespace all constants

I've namespaced Log class and Util module under MongoidSearch so that they don't collide with Log and Util constants in my application which are pretty common names. I didn't put them into Mongoid::Search because they would be included in models and may have collisions there. I also removed meaningless InstanceMethods module (which is also deprecated in AS 3.2) and put methods directly in the module.

+1


Making navigation easy on android tv

Describe your suggested feature
If by any chance you could make navigation easy to use with a remote and if possible you also add in an android tv icon, it doesn't show in Chromecast with Google tv.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I will fill out all of the requested information in this form.

I would like to help out, I'm not an expert in android development (just barely made a tiny app few years ago) but if anyone would like to work on it together feel free to drop by.
Seeing this has been raised multiple times here (#114, #162, #229, #854, #751, #1347 ,#1006), we could make this work. If we make it stable enough, we could have a pull request made and @jmir1 could review and merge it in no time!
I believe the task should be relatively straightforward:

Set Focus Handling properties for the UI Elements Android Docs This should help the remotes move around the selection without integrating a mouse.
Add an appearance theme to the library to show selected items in a more brighter colour

I've started to work on the app on my fork, I've tried adding NextFocus Properties (firstly) to the player_controls.xml but the DPAD interactions doesn't navigate correctly even after disabling the KeyDown events in the Gestures function.
Anybody knows what's going wrong?
Idea references:

Focus Events - Android Docs
Making apps TV friendly - Amazon Dev

What happens is that aniyomi is divided by modules, you must specify where it should jump when it reaches (x) or (y)

True! But since it's not a mouse pointer based solution, it just tells where the next selection box needs to go when the DPAD arrow keys are pressed.
I tried this out, and some stuff seem to work, but I need an expert 😂 to help me out. I'm editing the xml file of the layout and adding the NextFocusRight ...  to the attributes, but for some reason the focus finding algorithm ignores these properties.

True! But since it's not a mouse pointer based solution, it just tells where the next selection box needs to go when the DPAD arrow keys are pressed.
I tried this out, and some stuff seem to work, but I need an expert 😂 to help me out. I'm editing the xml file of the layout and adding the NextFocusRight ... to the attributes, but for some reason the focus finding algorithm ignores these properties.

I recommend you join the official aniyomi server, so you can talk more comfortably with more developers
https://discord.gg/Emm7xgSh

Hello, I don't know if this is the right place, but I would like to raise a small issue.
Yes, control with the remote control is a bit of a problem. Mouse control is better. But there is a problem in scrolling down by dragging the lists while controlling with the mouse. I would like to make a notification about this issue. Maybe this is not the place for this, I apologize in advance.

aniyomi works on android tv kinda with the cloudstream extension but i don't think its actively maintained a lot of aniyomi extensions don't work on it rn but i believe its because webview is not implemented in this extension but im no expert maybe this could help  https://github.com/CranberrySoup/AniyomiCompatExtension

Duplicate of #162


notebooks should not cd into parent directory

I think it is confusing to have this optional instruction for users and is not best practice. Output files will be written (if created), will not be written next to the notebooks, but in the parent, which is unexpected.
We should ensure, that the package is installed prior execution. So we should mention to install (which now should be super easy with pip/conda). On binder it is already installed, right?

yes that is mostly a relic from early dev stages and not very convenient when creating files
I'm ok with simply removing those cells 👍


App crashed

Description
I was browsing my files, and had 3 tabs open in the app window.
It suddenly froze and force-closed, I don't know why.
Steps To Reproduce
No response
Expected behavior
It shouldn't crash while using the app for a simple task as this one.
Files Version
Versión: <IP_ADDRESS> OS Version: 10.0.19044.1415
Windows Version
Windows 10 21H2 19044.1415
Relevant Assets/Logs
debug.log
debug_fulltrust.log

@Galloclau is this still an issue in the preview version? https://files.community/download/preview


Postman license change

Hi,
Does the postman recent license changes for usage of scatchpad affect this plugin?
Is this plugin in anyway related/owned by Postman itself? Please confirm, so that we can use it.

This is an unofficial extension.


doc: add 0 arguments Function type constructor definition #262

Sorry, maybe it was not necessary duplicate the PR.

It's not a big deal since this is a relatively small change. But in larger changes it gets kind of hard to keep context across PRs.
For other people that might be confused this is followup from #263


readablility issue since highlighted (mouse_over) is differnt if leaving an entity or a connection

Release 1.14.0
Last working: can't say
Browser/OS: chrome / windows 11
Got a problem with the readability of the entity names/values.
Not always but I think I found a reproducable way.
Got 2 sankeys in a vertical stack, unsure if that does matter.
If you hover with the mouse over an entity it gets highlighted, Aswell as all it's connections and the connected entities.
This leads to a poorer readability of the textual parts, but that's ok, since what one wanted is to the highlight all connected things.
Highlighting gets turned off once you move the mouse away from an entity object (normal behaviour I'd say)
But, if you move the mousepointer onto a connection while being highlighted and then move it out of the sankey chart the highlighting remains static.
From a code perspective I'd say the mouse_over = true gets turned into false when the pointer leaves an entity bar object while it remains true if the mousepointer leave  connection.
Forgive for te poor coloring I wantd to keep that animated gif as small as possible.
But you should see the difference between the pointer moving out of the chart from an entity vs. moving out of the chart from a connection.

Yes because some time in the past you recommended it to me to address a differnt problem which was that from time to time some entities were simply missing (not displayed at all). And yes throttle did nearly fix that issue.
Looks as if I must give it a try with smaller throttle values then.

throttle changed from 120 down to 12 ... seems to work

The highlighting should ignore or restart the throttle I guess but seems like low priority


.bat file seems wrong !!

The user needs to change the path in the codepg.bat file after cloning which can be a risky process and can be avoided i think

Now the application can be installed using pip. The .bat file can now remain like that for developer who just want to try/test it out without installing the application.


Create testMatrix to rerun failed tests in FTL

Create testMatrix to rerun failed tests in FTL

can you add tests? ty.

Added. Ready for review again.

Addressed all the feedback I think. Please review!


[deCONZ] : warning: using default xy gamut

Hi Eric,
my best wishes for 2024. I had the below warning on my Deconz-Homebridge:
homebridge-deconz v1.0.9, node v20.10.0, homebridge v1.7.0, homebridge-lib v6.7.3
I have 3 Hue Play lights with the latest firmware and I get the below messages (as I intend to replace the Hue bridge with Heombridge Deconz):
[deCONZ] : warning: using default xy gamut
I checked and I saw that there was similar issues reported on Homebridge Hue few years ago but did not find the solution.
Is there anything that I can do to get rid of those messages?
Thanks in advance for your answer.

Make sure the lights are exposed correctly by deCONZ, including the capabilities for colour.  I guess these lights aren’t yet included in any oppressive the DDFs.  You should see a warning for that as well.

This is the deCONZ API results for the Hue Play:
{
"capabilities": {
"alerts": [
"none",
"select",
"lselect"
],
"color": {
"ct": {
"max": 500,
"min": 153
},
"effects": [
"none",
"colorloop"
],
"modes": [
"ct",
"effect",
"hs",
"xy"
]
}
},
"colorcapabilities": 31,
"config": {
"groups": [
"0"
]
},
"ctmax": 500,
"ctmin": 153,
"etag": "0b629aae57dd30be28ec807a70c65dd3",
"hascolor": true,
"lastannounced": "2023-12-25T17:41:38Z",
"lastseen": "2023-12-26T14:00Z",
"manufacturername": "Philips",
"modelid": "LCT024",
"name": "Play 1",
"state": {
"alert": "none",
"bri": 254,
"colormode": "ct",
"ct": 280,
"effect": "none",
"hue": 9390,
"on": false,
"reachable": true,
"sat": 46,
"xy": [
0.402,
0.3903
]
},
"swversion": "0x01002402",
"type": "Extended color light",
"uniqueid": "00:17:88:01:06:11:4b:8e-0b"
}

So no capabilities.color.xy advertising the gamut.

@ebaauw  is there a way to adapt the DDF for this? or we can close the point.

That needs to be done in the deCONZ REST API plugin, see https://github.com/dresden-elektronik/deconz-rest-plugin/wiki.

That needs to be done in the deCONZ REST API plugin, see https://github.com/dresden-elektronik/deconz-rest-plugin/wiki.

@ebaauw if you think is worthed I can submit the request on deCONZ REST API community, but I need your mentorship for describing the request. Let me know.


Switch from mariasql to mariadb

Looks like MariaSQL is not maintained anymore and also doesn't build on node 12 anymore, we should switch to https://www.npmjs.com/package/mariadb

I've checked all the references to mariasql and sqlClient (496 results in 34 files) in the codebase and it turns out that all of them end up in either query or prepare functions from services/api/src/util/db.js. This is most likely good news because thanks to that it should be relatively easy to to swap the packages. I'll be experimenting with that now.
One things struck me during this review. If all the ~490 appearances of the text sqlClient end up in the same method, does it really make sense to pass them around? It looks like getting the client in the query/prepare methods would let us remove hundreds of lines of code (literally). Would it make sense to do that along with the package swap?

Yes, switching sql clients is a good opportunity to refactor, and I think that the new client would be an improvement but there are some considerations.
MariaSQL has a shared, non-asynchronous query queue. Previously we used a single, global instance but that meant every query for every request was placed into a single queue and caused issues, see #920. This is the reason sqlClient is instantiated and passed to all resolvers via apollo server context (one client per api request).
I've only looked briefly but it appears that the MariaDB node.js connector has a proper connection pool. So it would probably make sense to come up with some api that can abstract this out for every query. The current query/prepare methods are very MariaSQL centric though and I probably would refactor all that as well.
So: 1) We really need to test that we can switch to a "singleton" with a pool and not have same problems as #920 2) Even though it looks dirty, passing sqlClient around is proper dependency injection and I don't think a connection-handling-query with direct in-function calls is the "right way." We don't have unit tests now, but that would make it impossible to add.
We're moving away from having all the business logic in the resolver functions (see models/group, models/user), so those will become skinnier and have less passing.

Now that Node:10 is Maintenance LTS - we should look to switch to Node:14 - which will force this change.

With the release of alpine 3.13 - the need to move away from node:10 based images has increased.  Technically the Alpine 3.11 EOL is 2021-11-01 - but the upstream node 10 images are in maintenance only until 2021-05-01

With the release of alpine 3.13 - the need to move away from node:10 based images has increased.  Technically the Alpine 3.11 EOL is 2021-11-01 - but the upstream node 10 images are in maintenance only until 2021-05-01

I think we could aim to do a first pass of replacing the instances of mariasql with mariadb along with the required API changes. Then we could look into refactoring out a better solution or do a complete rewrite?

I think we could aim to do a first pass of replacing the instances of mariasql with mariadb along with the required API changes. Then we could look into refactoring out a better solution or do a complete rewrite?

In addition to not working on supported versions of node, it looks like our api is crashing a lot due to https://github.com/mscdex/node-mariasql/issues/73

In addition to not working on supported versions of node, it looks like our api is crashing a lot due to https://github.com/mscdex/node-mariasql/issues/73


FR: Nav & Menu add options variable to sub items

Please add options to subitems so we could add class to sub ul tag.
if ($items !== null) {
            $linkOptions['data-toggle'] = 'dropdown';
            Html::addCssClass($options, 'dropdown');
            Html::addCssClass($linkOptions, 'dropdown-toggle');
            $label .= ' ' . Html::tag('b', '', ['class' => 'caret']);
            if (is_array($items)) {
                if ($this->activateItems) {
                    $items = $this->isChildActive($items, $active);
                }
                $items = Dropdown::widget([
                    'items' => $items,
                    'encodeLabels' => $this->encodeLabels,
                    'clientOptions' => false,
                    'options' => $options,
                    'view' => $this->getView(),
                ]);
            }
 }

I think this should be available for as many levels as it can render. Just because navbar/dropdown don't do second level pop-outs, doesn't mean you can't display extra levels of menu indented or however you like. This should apply to \yii\widgets\Menu (as per Yii 1.1 CMenu) and \yii\bootstrap\Dropdown (#7480) as well.

keeping this open for yii\widgets\Menu

Won't be implemented in 2.0.


does nvm change npm too when it changes node version?

Please fill out the issue template; it’s there for a reason.
nvm changes only the node version. However, each node version has its own copy of npm, so that will likely change too (it might be the same, depending on which npm version is in the previous and current node version).


[AutoPR] msi/resource-manager

Created to accumulate context: msi/resource-manager

Build output:


xds-failover: not sending initial_resource_versions when moving from fallback to primary

Commit Message: xds-failover: not sending initial_resource_versions when moving from fallback to primary
Additional Description:
The initial_resource_versions field is used in delta-xDS s.t. Envoy supplies the versions of the resources it is aware of, and the server doesn't need to send these resources if they haven't been modified.
This PR updates Envoy to avoid populating that field when connecting to the primary source after being connected to the failover source.
Risk Level: low
Testing: Added integration tests.
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A

@htuch unfortunately this PR required some small updates to many tests. Please take a pass on this, and LMK if this should be broken even further.
/assign @htuch

Is the intuition that the primary version might be different or more up-to-date? Shouldn't this be captured in the version itself?

Is the intuition that the primary version might be different or more up-to-date? Shouldn't this be captured in the version itself?

Theoretically speaking, the version needs to be determined by the resource contents (e.g., hash of the contents).
The assumption is that the primary source always has same or better view of the resources.
The request is to "reset" the resources when moving from the failover to the primary, so no lingering resources will be kept in the Envoy.

FWIW, the docs describing the xDS-Failover feature are in #35746 (which is currently in draft mode until this is merged).

/assign @nezdolik

LGTM modulo comment (and assuming perfect test coverage ;-)

:) Trying to rerun the flaky test, to get the coverage report.

LGTM modulo comment (and assuming perfect test coverage ;-)

coverage LGTM. We'll need 2 stamps to merge.

I will take a look in couple of hours.


Node-Red  Palette

Hallo,
pls you can provide the version 0.3.5 that we can downlaod and integrate easy in RedMatic?

Hi, the node-red flow library seems to be updated now:
https://flows.nodered.org/node/@runnane/node-red-contrib-easee

Hallo, new version is now avaiable, but run on error when I try to install:

2023-05-09T17:16:35.748Z installieren : @runnane/node-red-contrib-easee 0.3.5
2023-05-09T17:16:35.112Z npm install --no-package-lock --global-style --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production<EMAIL_ADDRESS>2023-05-09T17:16:45.336Z [out]
2023-05-09T17:16:45.336Z [out] up to date in 9s
2023-05-09T17:16:45.364Z rc=0
Maybe you can have a second look?


Support Chart component

keywords: "Cannot read properties of null"
Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Make it possible to display charts
Benchmark 🌈

https://www.notion.so/mui-org/Chart-component-7b30cff4fdab4d2e8adbe0c796821f45
https://github.com/mui/mui-x/issues/1408
https://retool.com/components/chart (Integrated ploty.js)
https://docs.appsmith.com/reference/widgets/chart (Integrated fusioncharts)
Superblocks (ploty.js)
Openblocks (echarts.js)
Tooljet (ploty.js)

Motivation 🔦
I would like to plot this data https://api.ossinsight.io/q/analyze-issue-open-to-first-responded?repoId=23083156 which is about the median time to get feedback on issues in https://github.com/mui/material-ui. It's meant to replace https://mui-repository-health-dashboard.vercel.app/. So far, I have tried:

reaviz ❌ https://master--toolpad.mui.com/_toolpad/app/cl42qt2jx01249xnr14xjce8b/editor/codeComponents/cl6rsvyg400003b6gwlzpovht. Fail with

victory ❌ https://master--toolpad.mui.com/_toolpad/app/cl42qt2jx01249xnr14xjce8b/editor/codeComponents/cl6rsxp8q00023b6gu7dfcvg6. Fail with

react-vis ✅ https://master--toolpad.mui.com/_toolpad/app/cl42qt2jx01249xnr14xjce8b/editor/codeComponents/cl6rtolju00003b6gcl9wrueb

Source
import * as React from "react";
import { createComponent } from "@mui/toolpad-core";
import {
  XYPlot,
  XAxis,
  YAxis,
  HorizontalGridLines,
  VerticalGridLines,
  LineMarkSeries,
} from "https://cdn.skypack.dev/react-vis";

export interface ChartProps {
  msg: string;
}

async function createReactVisStyles(doc) {
  let styles = doc.getElementById("react-vis-css");
  if (styles) {
    return;
  }
  const res = await fetch("https://esm.sh/react-vis/dist/style.css");
  if (!res.ok) {
    throw new Error(`HTTP ${res.status}: ${res.statusText}`);
  }
  const css = await res.text();
  styles = doc.createElement("style");
  styles.id = "react-vis-css";
  styles.appendChild(doc.createTextNode(css));
  doc.head.appendChild(styles);
}

function Chart({ msg }: ChartProps) {
  const root = React.useRef(null);

  React.useEffect(() => {
    const doc = root.current.ownerDocument;
    createReactVisStyles(doc);
  }, []);

  return (
    <div ref={root}>
      <XYPlot width={300} height={300}>
        <VerticalGridLines />
        <HorizontalGridLines />
        <XAxis />
        <YAxis />
        <LineMarkSeries
          className="linemark-series-example"
          style={{
            strokeWidth: "3px",
          }}
          lineStyle={{ stroke: "red" }}
          markStyle={{ stroke: "blue" }}
          data={[
            { x: 1, y: 10 },
            { x: 2, y: 5 },
            { x: 3, y: 15 },
          ]}
        />
        <LineMarkSeries
          className="linemark-series-example-2"
          curve={"curveMonotoneX"}
          data={[
            { x: 1, y: 11 },
            { x: 1.5, y: 29 },
            { x: 3, y: 7 },
          ]}
        />
      </XYPlot>
    </div>
  );
}

export default createComponent(Chart, {
  argTypes: {
    msg: {
      typeDef: { type: "string" },
      defaultValue: "Hello world!",
    },
  },
});

Ant Design charts ❌ https://master--toolpad.mui.com/_toolpad/app/cl42qt2jx01249xnr14xjce8b/editor/codeComponents/cl6umjlzv00013b6gsf59dy1y

i would vote for echart. While it's api has pretty much everything you may need from the charts.
It was created like a decade ago. Is stable as could be. Had a lot of updates. API is stable for the last at least 5 or more years. Has pretty good visual, if you don't like that there are theme options too for anything visible. It's open source too.
https://echarts.apache.org/examples/en/index.html

@liesislukas Based on the benchmark that we did for MUI X, echart is definitely the biggest one https://mui-org.notion.site/Chart-component-7b30cff4fdab4d2e8adbe0c796821f45.
As a side note, On MUI X, we are considering building charts as well as it's a frequent request we hear, but we struggling a bit to identify strong enough problems with the existing charting library for the effort to make sense.

@oliviertassinari on side note
Charting sounds offtopic for me in mui org context, because it's more of svg component. Reactjs focus is on dom, not svg. mui org is doing all the stuff around dom too. charting has a lot of things to be done well which requires a lot of high quality talent, which means a lot of expenses. Yet charting market is full of solutions. If you want to provide some better way to use charts within mui.com components, i would consider better making some helper components for top 5 open source charting solutions like echarts, while it's super old, stable and has everything in it already.
Maybe it would make sense in some case to add some basic charts - like simple pie, line, bar, gauge but in general i would not focus much. Only benefit would be to have minimal charts w/o need to add big charting lib. Building something like echarts will eat up a ton of resources and building something with less polish level wouldn't make sense for someone like mui.com too, while i at least expect quality from mui.com, like it delivers now.
i would rather focus those resources you consider to put into building one more charting solution to rather building some freelancing area which would allow to find talent for ui tasks & focus on continue to provide best possible ui components for DOM via Joi project (components + theming), then for designers best possible design kits for figma etc. and some interesting productivity boosts via Toolpad instead.

@liesislukas Thanks for sharing your thoughts on this.
Related to it. What's your take on recharts? It's React only, SVG only, and seems to be the most popular charting library that we could find on for the web. It's also abandoned by its 1-2 maintainers.

I have tried recharts, it seems to work well:

https://master--toolpad.mui.com/deploy/clcdobvof0008n99jpx86fede/pages/331kqzd
import * as React from "react";
import { createComponent } from "@mui/toolpad-core";
import {
  PieChart,
  Pie,
  Cell,
  Tooltip,
  ResponsiveContainer,
} from<EMAIL_ADDRESS>
// Copied from https://wpdatatables.com/data-visualization-color-palette/
const COLORS = [
  "#ea5545",
  "#f46a9b",
  "#ef9b20",
  "#edbf33",
  "#ede15b",
  "#bdcf32",
  "#87bc45",
  "#27aeef",
  "#b33dc6",
];

export interface PieChartProps {
  data: object[];
}

function PieChartExport({ data }: PieChartProps) {
  return (
    <PieChart width={300} height={300}>
      <Pie
        data={data}
        cx={150}
        cy={150}
        innerRadius={0}
        outerRadius={80}
        fill="#8884d8"
        dataKey="value"
      >
        {data.map((entry, index) => (
          <Cell key={`cell-${index}`} fill={COLORS[index % COLORS.length]} />
        ))}
      </Pie>
      <Tooltip
        formatter={(value, name, props) =>
          Intl.NumberFormat("en", { notation: "compact" }).format(value)
        }
      />
    </PieChart>
  );
}

export default createComponent(PieChartExport, {
  argTypes: {
    data: {
      typeDef: { type: "array" },
      defaultValue: [
        { name: "Group A", value: 400 },
        { name: "Group B", value: 300 },
        { name: "Group C", value: 300 },
        { name: "Group D", value: 200 },
      ],
    },
  },
});

I have tried recharts, it seems to work well

This is not working for me locally, for e.g. the https://github.com/mui/mui-public/tree/master/tools-public is failing locally with the error<EMAIL_ADDRESS>
Using<EMAIL_ADDRESS>in a local project, the same code fails with this error:

It's worth mentioning that I am on Windows.

I have tried recharts, it seems to work well:

https://master--toolpad.mui.com/deploy/clcdobvof0008n99jpx86fede/pages/331kqzd
import * as React from "react";
import { createComponent } from "@mui/toolpad-core";
import {
  PieChart,
  Pie,
  Cell,
  Tooltip,
  ResponsiveContainer,
} from<EMAIL_ADDRESS>
// Copied from https://wpdatatables.com/data-visualization-color-palette/
const COLORS = [
  "#ea5545",
  "#f46a9b",
  "#ef9b20",
  "#edbf33",
  "#ede15b",
  "#bdcf32",
  "#87bc45",
  "#27aeef",
  "#b33dc6",
];

export interface PieChartProps {
  data: object[];
}

function PieChartExport({ data }: PieChartProps) {
  return (
    <PieChart width={300} height={300}>
      <Pie
        data={data}
        cx={150}
        cy={150}
        innerRadius={0}
        outerRadius={80}
        fill="#8884d8"
        dataKey="value"
      >
        {data.map((entry, index) => (
          <Cell key={`cell-${index}`} fill={COLORS[index % COLORS.length]} />
        ))}
      </Pie>
      <Tooltip
        formatter={(value, name, props) =>
          Intl.NumberFormat("en", { notation: "compact" }).format(value)
        }
      />
    </PieChart>
  );
}

export default createComponent(PieChartExport, {
  argTypes: {
    data: {
      typeDef: { type: "array" },
      defaultValue: [
        { name: "Group A", value: 400 },
        { name: "Group B", value: 300 },
        { name: "Group C", value: 300 },
        { name: "Group D", value: 200 },
      ],
    },
  },
});

cc @joserodolfofreitas The composable SVG API of recharts felt great, however, their docs isn't great, we could do much better. I think that we could move in this direction.

@oliviertassinari We love recharts. Docs with more advanced features would be nice but the community has good examples. Doesn't support 3d rendering but it gets the job done.

@oliviertassinari There are some points, which available libraries do not address, in my opinion:
We need true X/Y charts for technical diagrams (think line charts with "knots") and also real time capabilities.
Almost every charting library we evaluated has the assumption that one X value has at most one Y value. They seem to be mostly optimized for financial applications (candle diagrams, trend lines, etc.) and often they are not fast enough.
There are a few commercial alternatives available with steep price points (approx. >$10K/year) and prohibitive licensing, which require to rebuy for every new domain, which factually excludes SaaS applications.
Currently we use as a workaround victory with a custom X/Y chart component, which is clearly not ideal.
If you would add fast and simple charting components, which include true X/Y diagrams (line charts with "knots"), good usability (pinch/zoom, mobile support) and integrated into MUI, I think the engineering community would love it. I see use cases for web interfaces for embedded devices and data gathering/management portals.

@markus-kraeutner would you have a visual illustration of this need?

There are a few commercial alternatives available with steep price points (approx. >$10K/year) and prohibitive license terms, which require to rebuy for every new domain, which factually excludes SaaS applications.

@markus-kraeutner Do you mean Highcharts?
Note that we have released the first alpha version of our chart library: https://mui.com/x/react-charts/.


Issues resolving order for 2.0.0 release

The order is such:
Core

[x] #71
[x] #72
[x] #70
[x] #78
[x] #31

Plus, update dependencies asap (first of all, NetVips.Native to 8.10+, but it would be great to update gdal too)
Tests

[x] #28

Console

[x] #79
[x] #76
[x] #74

And if possible:
~#43~ (moved to future milestone)
GUI

[x] #80
[ ] #75

Benchmarks

[x] #10

Solution problems

[x] #86

Repo organization

[x] #73
[x] #44
[x] #77
[ ] #81 (this issue)

Plus:

[ ] #94

Trackable through milestones


[Request] Gasses in JEI

JEI now has support for custom ingredient types, in addition to ItemStack and FluidStack.
I think Mekanism's gasses are a good candidate for this feature.
Here's the wiki documentation on adding new ingredients: https://github.com/mezz/JustEnoughItems/wiki/Non-Item-Ingredients
The vanilla plugin in JEI adds ItemStack and FluidStack using the same API, so you can look there for an example.
Let me know if you have any questions.

Maybe doing it the other way and changing Mekanism gases to use the regular fluid types in Forge would be a better idea, though that might be a lot more work.

Have their been any further thoughts on doing this? It's hard to remember how to make Sulfuric Acid without consulting a wiki.

I'm willing to pick this up, together with an update of the used JEI api as soon as my 1.12 update and 1.10 back port are accepted and merged.

This appears to already have been added in https://github.com/aidancbrady/Mekanism/commit/89905c836bc31b3043b62d5f521ad69150dff089#diff-055b8be0fe0984f3a1efe9ff4ff5173cR162 ..

Completed fully here: https://github.com/aidancbrady/Mekanism/commit/7b9bf2194257ee42d74ec328619c0d96510c6bd5


Effects are not applying when keyboard is hide

Scenario for reproducing:

Run sample app
Focus on editor, type some symbols
Hide keyboard with back button
Tap "bold" button.
Then open keyboard again and type something.

Actual result - font is still usual
Expected result - font should be bold

when we will select text and click on button like bold etc. , apply all effects without using keyboard.

glebhotomcev did you find a solution? I'm facing this problem too.


Download issue

Sorry but I don't have time to read through all the guidelines for this project - here is some information that you can take or leave though.
└─[$]› youtube-dl --verbose https://www.youtube.com/watch?v=itKhvrUekDs
[debug] System config: []
[debug] User config: []
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.02.22
[debug] Python version 2.7.12 - Linux-4.10.0-37-generic-x86_64-with-Ubuntu-16.04-xenial
[debug] exe versions: ffmpeg 2.8.11-0ubuntu<IP_ADDRESS>, ffprobe 2.8.11-0ubuntu<IP_ADDRESS>, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] itKhvrUekDs: Downloading webpage
[youtube] itKhvrUekDs: Downloading video info webpage
[youtube] itKhvrUekDs: Extracting video information
WARNING: unable to extract uploader nickname
WARNING: unable to extract html5 player; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[youtube] {43} signature length 41.40, html5 player None
ERROR: Signature extraction failed: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 905, in _decrypt_signature
    video_id, player_url, s
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 797, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'/yts/jsbin/player-vflwcUIMe/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
 (caused by ExtractorError(u"Cannot identify player u'/yts/jsbin/player-vflwcUIMe/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 905, in _decrypt_signature
    video_id, player_url, s
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 797, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'/yts/jsbin/player-vflwcUIMe/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 666, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 316, in extract
    return self._real_extract(url)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1407, in _real_extract
    encrypted_sig, video_id, player_url, age_gate)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 915, in _decrypt_signature
    'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 905, in _decrypt_signature
    video_id, player_url, s
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 797, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'/yts/jsbin/player-vflwcUIMe/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
 (caused by ExtractorError(u"Cannot identify player u'/yts/jsbin/player-vflwcUIMe/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

[debug] youtube-dl version 2016.02.22

Your version is too old. Most likely you have installed it via apt-get. As Debian/Ubuntu people don't update this package often, please uninstall it from apt-get and install the latest version.

@yan12125 right, foolishly i thought that I'd have reasonable versions as I'd updated my system to the latest Ubuntu.
sorry for the lazy issue - i wasn't expecting help, I just included it on the off chance that it was of some use to people here.
Thanks for your response

I need to talk to Ubuntu packaging team... There are at least 100 "bugs" due to old Ubuntu youtube-dl versions. They should really maintain their packages correctly.
Notes to myself:
Relevant Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/youtube-dl/+bug/1529647
My previous mails with Arch developers: https://lists.archlinux.org/pipermail/arch-general/2016-September/041859.html

@yan12125 np. If there's an appropriate channel / repo you'd like me to comment on supporting this issue let me know


[4.2] IRGen: Don't outline enum value functions when they involve ope…

…n existential types
We don't support doing so.
rdar://41009775

@swift-ci Please test


Replace some rocksdb databases with lmdb

Explain your changes:
*
Explain how you tested your changes:
*
Checklist:

[ ] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

Closes #0000

!ci-build-me

!ci-toolchain-me

@rbonichon Thanks so much for looking this over and for your suggestions

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me


An input error when select data path

Hello,
Thank you for your tool! It has been really helpful to me. However, I am encountering a problem after upgrading to version 2.0.7.
When I input my data path and try to start, I receive an unexpected error message stating that some fields are not properly filled (as shown in the figure). However, the input paths all exist. I am currently stuck at this point.
Could you please fix these problems or provide me with some advice?
Thank you!

Hello,
Do you have any error messages in the terminal?

Sorry for the late reply.
Actually, I can't find any new error message in the terminal except for an error message when the program starts (see the following figure).

Ok, I see.
Could you please double-check that you have only "XXXX_PH_0X.fits" photon files in your photon directory?
I noticed that easyfermi 2.0.7 does not give an alert if it finds no PH files, so probably this is the case for you.
I already fixed that and this new feature will be available in version 2.0.8.
Let me know if this solves the problem.

Yes, I discovered that the spacecraft file was also placed in the photo directory, as I used to do in version 1.X.X.
After moving the spacecraft out of the photo directory, the program started working.
Thanks for your help!

Thank you for the feedback!

I still get this error from the latest commit on the main branch when starting an analysis from scratch.

I only managed to download Diffuse data, but trying to download either of Spacecraft or Photons triggers this error.

My use case is slightly different than this, as I am starting from scratch, but the error is the same: feel free to open a separate issue if you feel it is better!

Hmm, I see. In this case the problem is probably with astroquery. The diffuse emission files are downloaded directly from here: https://fermi.gsfc.nasa.gov/ssc/data/access/lat/BackgroundModels.html, while the Photon and spacecraft files are queried with astroquery. If you see a "404 error" in the terminal, this means that astroquery could not reach the Fermi-LAT server. There are two ways to proceed in this case:

Wait a couple of hours and try again.
Download the files manually as shown in the YouTube tutorials.

Is this warning related?

/Users/michele/Applications/miniforge3/envs/easyfermi/lib/python3.9/site-packages/astroquery/fermi/init.py:37: UserWarning: Experimental: Fermi-LAT has not yet been refactored to have its API match the rest of astroquery.
warnings.warn("Experimental: Fermi-LAT has not yet been refactored to have "

This warning is not a problem. Do you see the Photon and spacecraft files in the ./Photon and ./spacecraft directories? In v2.0.8 easyfermi prints a warning in the log if it does not find the Photon files.

I am starting from scratch, so I am starting from an empty directory (apart from the Diffuse sub-directory that I managed to download)

Tried again this morning with the same result, unfortunately.
Can you replicate this issue yourself?

Problem solved. Can you try again with vesion 2.0.9?

Now it works again


Updates to conda-packaging and meta data

Updated license from GPL to MIT
Updates to README for program name changes
Update to VERSION (0.1.0_beta -> 0.1.0)
Build script tweaks

To finish conda-forge PR, we need to tag an official 0.1.0 release, which I'm thinking should be this branch.


Can't save Global with nested lists

Bug Report
If a global have nested lists, it can't be saved.
Current Behavior
If a global have nested lists, it can't be saved.
Expected Behavior
It should be saved.
Steps to Reproduce

Create a payload server with this "MemberGroup" global
Add the first group with one member and save: (this step should work correctly)

Don't refresh the page, add the second group and save:

Detailed Description
Payload version: 1.1.21

Hey @PegasisForever — thanks for this report! This is now fixed and will be released shortly in our next patch version.


crossplane-cli: init at 1.14.3

Description of changes
Crossplane released a crossplane cli tool with 1.14.0 release version.
Nixpkgs already has a crossplane tool, so I decided to name it crossplane-cli.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Do I need to do something for merging that? Ask somebody or do some additional actions?

Do I need to do something for merging that? Ask somebody or do some additional actions?

The "best" option is to send your PR to this thread. Sometimes it gets merged, sometimes it gets ignored (unfortunately)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1266

@selfuryon I don't think it's necessary to change the name of the binary too, as an example see kubernetes-helm which still uses the binary name helm.

It's the problem of naming:

Crossplane already has crossplane application: it's original crossplane controller in Kubernetes pod
Crossplane internally called this cli utility as crank, but in all manuals reference it like crossplane or crossplane cli. For example, their installation script rename crank to crossplane
nixpkgs already has crossplane app, so I needed to specify crossplane somehow, so I decided to name it crossplane-cli.

But how do you suggest to name it? crossplane-crank?

Thanks! Welcome to nixpkgs :)


Update catalog_filtering.py

remove thumbnail url in catalog filtering example

Codecov Report

Merging #157 (a8ee01a) into master (9a011aa) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #157   +/-   ##
=======================================
  Coverage   56.50%   56.50%
=======================================
  Files          20       20
  Lines        3235     3235
  Branches      479      479
=======================================
  Hits         1828     1828
  Misses       1288     1288
  Partials      119      119

Continue to review full report at Codecov.

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


Fix bb script (clippy isn't test)

@naomijub I can still rebase and merge without review. I can't when CI doesn't pass, like in the EdnError draft.

Can you check if this works?

Can you check if the new ruleset works?

Looks good. I can't merge #125 without a review.


New version: LibTracyClient_jll v0.9.1+0

Autogenerated JLL package registration

Registering JLL package LibTracyClient_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/LibTracyClient_jll.jl
Version: v0.9.1+0
Commit: fbb12be1d182a86185e6397af12b2e7f84c5c4a8
Revision on Yggdrasil: https://github.com/JuliaPackaging/Yggdrasil/commit/9f51be66b98185837885d123180f71b4d21b276d
Created by: @topolarity

This failure is expected, since most VMs don't support the hardware timers that Tracy use.
[noblock]


Convert stored procedures, views, and functions

[ ] Convert everything to support PostgreSQL

AWS SCT for tables and views
Manual conversion for functions and stored procedures
Break down by categories - 26 categories of MP checks
Each category has a few checks

https://app.zenhub.com/files/287570343/00b7e756-1721-4d64-be6a-10d379ef60e0/download

https://app.zenhub.com/files/287570343/f2b3ab72-2813-4234-8fa8-35ec8610b000/download


[GSSoC'23] Palindrome Checker Ready

Title and Issue number

Title - Palindrome Checker
Issue Number - #2139
Close #2139

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

@pranjay-poddar @Saurabh-kumar09 @MohitGupta121 Sirs, please review this pull request and requsted to merge it into the main branch of the repository for a successful contribution under GSSoC'23 program


ssl3 ext invalid servername

Describe the bug
Hello, I'm using your helm charts but getting stuck trying to use the Python pulsar-client library from outside the cluster.
To Reproduce
1 - Deploy the helm charts in a Kubernetes cluster.
2 - Enable ingress for pulsar-proxy.
3 - Use the code below:
import pulsar
client = pulsar.Client('https://pulsar-proxy.domain:443')
producer = client.create_producer('my-topic')

Expected behavior
Create a connection and a topic called 'my-topic'.
Error
ssl3 ext invalid servername (SSL routines, ssl3_ctrl): Error while setting TLS SNI
Additional context
It looks like this variable in the reply (proxyThroughServiceUrl) should be 1 for it to use the service URL as proxy and not try to go direct to the cluster using pulsar protocol on port 6650, as that is not available from outside the cluster.
I tried using the additional listeners feature without luck.
Logs
2024-09-18 09:17:57.471 INFO  [139927618582208] HTTPLookupService:223 | Curl Lookup Request sent for https://pulsar-proxy.domain:443/admin/v2/persistent/public/default/my-topic/partitions?checkAllowAutoCreation=true
2024-09-18 09:17:57.642 INFO  [139927618582208] HTTPLookupService:239 | Response received for url https://pulsar-proxy.domain:443/admin/v2/persistent/public/default/my-topic/partitions?checkAllowAutoCreation=true responseCode 200
2024-09-18 09:17:57.642 INFO  [139927618582208] HTTPLookupService:280 | parsePartitionData = { LookupDataResult [brokerUrl_ = ] [brokerUrlTls_ = ] [partitions = 0] [authoritative = 0] [redirect = 0] proxyThroughServiceUrl = 0] }
2024-09-18 09:17:57.643 INFO  [139927618582208] HandlerBase:111 | [persistent://public/default/my-topic, ] Getting connection from pool
2024-09-18 09:17:57.643 INFO  [139927618582208] HTTPLookupService:223 | Curl Lookup Request sent for https://pulsar-proxy.domain:443/lookup/v2/topic/persistent/public/default/my-topic
2024-09-18 09:17:57.738 INFO  [139927618582208] HTTPLookupService:239 | Response received for url https://pulsar-proxy.domain:443/lookup/v2/topic/persistent/public/default/my-topic responseCode 200
2024-09-18 09:17:57.739 INFO  [139927618582208] HTTPLookupService:315 | parseLookupData = { LookupDataResult [brokerUrl_ = pulsar://pulsar-broker:6650] [brokerUrlTls_ = ] [partitions = 0] [authoritative = 0] [redirect = 0] proxyThroughServiceUrl = 0] }
2024-09-18 09:17:57.739 INFO  [139927618582208] ClientConnection:187 | [<none> -> ] Create ClientConnection, timeout=10000
2024-09-18 09:17:57.741 ERROR [139927618582208] ClientConnection:268 | ssl3 ext invalid servername (SSL routines, ssl3_ctrl): Error while setting TLS SNI
2024-09-18 09:17:57.741 INFO  [139927618582208] ConnectionPool:124 | Created connection for --0
2024-09-18 09:17:57.741 ERROR [139927618582208] ClientConnection:579 | [<none> -> ] Invalid Url, unable to parse: system:0 Success
2024-09-18 09:17:57.741 ERROR [139927618582208] ClientConnection:1318 | [<none> -> ] Connection closed with ConnectError (refCnt: 2)
2024-09-18 09:17:57.741 INFO  [139927618582208] ConnectionPool:141 | Remove connection for --0
2024-09-18 09:17:57.742 INFO  [139927618582208] ClientConnection:275 | [<none> -> ] Destroyed connection to -0
2024-09-18 09:17:57.742 INFO  [139927618582208] ProducerImpl:757 | Producer - [persistent://public/default/my-topic, ] , [batching  = off]

client = pulsar.Client('https://pulsar-proxy.domain:443')

Does it work if you use the Pulsar binary protocol (pulsar+ssl://pulsar-proxy.domain:6651)?

client = pulsar.Client('https://pulsar-proxy.domain:443')

Does it work if you use the Pulsar binary protocol (pulsar+ssl://pulsar-proxy.domain:6651)?

Hello, unfortunately not as the proxy doesn't expose 6651 but 443 (ingress).

Hello, unfortunately not as the proxy doesn't expose 6651 but 443 (ingress).

@meyerbro Do you have 443 mapped to Pulsar binary protocol? You cannot proxy Pulsar binary protocol over HTTPS. Pulsar client can use https for lookups, but it needs Pulsar binary protocol to connect to a broker.
In the default values.yaml, pulsarssl port is 6651.
  ports:
    http: 80
    https: 443
    pulsar: 6650
    pulsarssl: 6651

Hello, unfortunately not as the proxy doesn't expose 6651 but 443 (ingress).

@meyerbro Do you have 443 mapped to Pulsar binary protocol? You cannot proxy Pulsar binary protocol over HTTPS. Pulsar client can use https for lookups, but it needs Pulsar binary protocol to connect to a broker. (alternative is SNI proxy, but that's not covered in the Pulsar Helm chart) In the default values.yaml, pulsarssl port is 6651.
  ports:
    http: 80
    https: 443
    pulsar: 6650
    pulsarssl: 6651

I created an ingress that points to 6650 of the pulsar-broker pod (I only have 1 replica) and then I just try to hit that from a python client on my windows machine (outside the kube cluster).
Can you disclose more? I'm really happy with the support I'm getting here, thank you.

We use nginx ingress, wondering if I can do the SNI config on that.

Can you disclose more? I'm really happy with the support I'm getting here, thank you.

#423 contains some related information.

We use nginx ingress, wondering if I can do the SNI config on that.

it should be possible, but you are on your own.


how to change gfm-plugin/jxbrowser default console log level

Hi,
too many logs write to console by default, they begin as below
12:11:14 INFO: OS name: Linux
12:11:14 INFO: JRE version: 1.8.0_91 64-bit
12:11:14 INFO: JxBrowser version: 5.4.3
12:11:14 INFO: Starting IPC...
12:11:14 INFO: Starting IPC Server...
12:11:14 INFO: Starting IPC Process...
12:11:14 INFO: Start Chromium process...
.
.
.
toooo many lines
.
.
.

to stop it, i tried these methods below before i submit this issue:

add IDEA boot option -Djxbrowser.logging.level=OFF as [jxbrowser's document said] (https://jxbrowser.support.teamdev.com/support/solutions/articles/9000013125-logging)
same as above, but change word jxbrowser to JxBrowser, or OFF to SEVERE.
add IDEA boot option -Djava.util.logging.config.file="<'file/path/to/logging.properties' which contents include lines and all contexts about 'level' set to 'OFF' or 'SEVERE' >", because it seems belong to java.util.logging
edit <IDEA_home>/bin/log.xml, maybe it belongs to log4j.

but not work.

wow, such a quick response !


⚠ Avatar API Endpoint has degraded performance

In 7bf4598, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 4512 ms

Resolved: Avatar API Endpoint performance has improved in 5861fb1.


Update codeowners

Pull Request Description
The whole app/ide-desktop is now owned by cloud / dashboard team since we moved all parts into react. Lemme know if anything should be changed
Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[ ] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

I put my two cents by adding the rest of the GUI team to appropriate folders.


events+music+{finish.js}

(node:1322) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'send' of undefined
at module.exports (/home/runner/AssistantRobot/events/music/finish.js:2:18)
at DisTube.emit (events.js:314:20)
at DisTube.EventEmitter.emit (domain.js:483:12)
at DisTube._handleSongFinish (/home/runner/AssistantRobot/node_modules/distube/src/DisTube.js:936:35)
at StreamDispatcher. (/home/runner/AssistantRobot/node_modules/distube/src/DisTube.js:904:34)
at StreamDispatcher.emit (events.js:326:22)
at StreamDispatcher.EventEmitter.emit (domain.js:483:12)
at finishMaybe (_stream_writable.js:639:14)
at _stream_writable.js:616:5
at StreamDispatcher._final (/home/runner/AssistantRobot/node_modules/discord.js/src/client/voice/dispatcher/StreamDispatcher.js:248:5)
(node:1322) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1322) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I directly deleted that file cuz its useless for the queue within autoplay.


acl2: fix build on darwin

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/145271
cc: @jwiegley
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build acl2-minimal


hwmv2: hardware model version 2 (squashed)

Is there a need to list all the commit SHA's in the commit log. Instead could we point to the branch name since we plan to retain it.

Also should we update release notes and migration guide documents?

Is there a need to list all the commit SHA's in the commit log. Instead could we point to the branch name since we plan to retain it.

It was agreed in the Discord conversation.

Also should we update release notes and migration guide documents?

Good point, this needs to come straight after the merge.


Fix for #188, widget field errors not displaying

While I like the idea of catch, this fixes the problem. It makes sense if the actions are FSAs, since error better not be present if there's no error. Thoughts?
ref: #188

As a newcomer, it was an exercise figuring out the pipes in this.. not that it wasn't fun =) However, it may make sense to have form-submission-specific middleware, so that it may simply return a rejected promise, instead of having to code that logic into the component?

Or maybe simply a helper for the handleSubmit function argument that checks for x.error and creates a rejection.

I like it.


validating a body with a schema

Hi!!
I'm trying to do a PUT request with a body. I'm specifying the schema as the documentation says, but it seems like the body validation is not doing anything. ¿any idea?
Here are my json files.
the impostor:
  {
    "request": {
      "method": "PUT",
      "endpoint": "/v1/users/123/country",
      "schemaFile": "schemas/put-update-account.json"
    },
    "response": {
      "headers": {
        "Content-Type": "application/json"
      },
      "status": 204
    }
  }

the schema file
{
  "country": {
    "type": "string",
    "enum": [
      "SPANISH",
      "ENGLISH"
    ]
  },
  "required": [
    "country"
  ]
}

the test request
{
  "in": {
    "method": "PUT",
    "url": "http://localhost:8090/v1/users/123/country",
    "body": "{\"country\":\"SPANISH\"}"
  },
  "out": {
    "status_code": 204,
    "header": {
      "Content-Type": ["application/json"]
    }
  }
}

my krakenD definition
{
  "endpoint": "/v1/users/{userId}/country",
  "method": [
    "PUT"
  ],
  "output_encoding": "no-op",
  "backend": [
    {
      "host": [
        "http://my-micro"
      ],
      "encoding": "no-op",
      "url_pattern": "/v1/users/{userId}/country",
      "circuit_breaker": {
        "enabled": true,
        "timeout": 2000.0
      }
    }
  ]
}

Thanks in advance

Hi @amartinm7,
I have tested your example and it seems to be working correctly, as expected.
What do you see as output when you start Killgrave? 🤔
Make sure that Killgrave is loading correctly your imposters:

You're pointing to the corrrect imposters directory.
Your imposters have a valid extension (either .imp.yml or .imp.yaml for YAML or .imp.json for JSON).

Thanks!

Hi @joanlopez
The previous example is working, but it's not taking account the schema and the body. I mean, if you change the request body with "body": "{"country":"FRANCE"}"... the test is working too... but you expect an error!!. This is my point, the validation is not executed. I don't know why.

Sorry 🙏🏻  Yes, you're right. I assumed the schema you shared was a "subset" of the entire file.
But, if it still fails, I guess it's probably because that's literally your whole file, and I think the problem is that your JSON Schema definition is not completely correct. It should be something like:
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "country": {
      "type": "string",
      "enum": [
        "SPANISH",
        "ENGLISH"
      ]
    }
  },
  "required": [
    "country"
  ]
}

Technically you can omit the $schema field, but you should:

Specify the type of the root object
Move the country, into the root object properties
Leave the required attribute at the root level.

I have tried it with that, and it works as expected.
Thanks, and apologies for the confusion!

Hi @joanlopez
Using the schema as you say, it's working. So thank you very much for your help :)
But when I'm sending the "body": "{"country":"FRANCE"}" in request, or empty body, I'm getting a 404 error message.
I think the error should be a 400 Bad Request, doesn't it?
I mean, It's a validation error more than if the resource exists or not.
Thxs in advance

Hi @amartinm7,
By default, Killgrave returns a 404 Not Found for any non-covered endpoint. There has been some discussions about having the possibility of defining a fallback behavior, but so far is not possible.
However, you can still use Killgrave to achieve the behavior you expect with the following imposters definition:
[
  {
    "request": {
      "method": "PUT",
      "endpoint": "/v1/users/123/country",
      "schemaFile": "schemas/put-update-account.json"
    },
    "response": {
      "headers": {
        "Content-Type": "application/json"
      },
      "status": 204
    }
  },
  {
    "request": {
      "method": "PUT",
      "endpoint": "/v1/users/123/country"
    },
    "response": {
      "headers": {
        "Content-Type": "application/json"
      },
      "status": 400
    }
  }
]

So, basically, you're defining an imposter to respond to PUT /v1/users/123/country requests that satisfy your schema with 204 No Content, and another one to respond to PUT /v1/users/123/country requests with 400 Bad Request. So, if you order them (remind that order matters!) as in the example above, the correct requests will satisfy the schema, and fall into that imposter (returning a 204 No Content), while the incorrect requests will fall to the second imposter (returning a 400 Bad Request) , which has no requirements other than the method and the path.
I hope that helps you!

Hi @joanlopez
Yes, it helps. Thxs a lot! :)


Update stable version in repo from 1.3.21 to 1.3.22

Think about update stable version to 1.3.22
Version: stable=1.3.21 (540 days old) => latest=1.3.22 (25 days old)
Installs: stable=6476 (76.55%), latest=424 (5.01%), total=8460
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.3.22 but the current stable version is already 1.3.23.
So this issue should be closed.


Allow to delete measurement in InfluxDB

Is your feature request related to a problem? Please describe.
Currently, DBeaver does not allow to delete InfluxDB 1.x measurement in the UI.
Describe the solution you'd like
It would be great to add a "Delete" option in the menu when right click the measurement. Similarly, for future InfluxDB 2.x. Thanks! 😃

Describe alternatives you've considered
Right now I need use InfluxDB CLI to run DROP MEASUREMENT <measurement_name>.

Hello @Hongbo-Miao
Thanks for the idea.