Using string as a field's default value in AVRO schema when null and string are defined in field type

Hello guys,
Thanks for the great work you put in this project!
We have a kafkajs consumer, consuming AVRO messages from kafka topic and decoding them with your library.
Pretty straightforward setup, works great except for one case.
In some AVRO schemas we have the following field definition:
{
    "name": "exampleField",
    "type": ["null","string"],
    "default": "VALUE1",
    "doc": "Allowed values ['VALUE1', 'VALUE2']"
}

When we try to decode schema with your library, we are getting this error ConfluentSchemaRegistryArgumentError: invalid "null": "VALUE1"
We checked all schemas and found out that field definition from above breaks decoder because it expects null to be default value because null is listed in type
Can you add support for also allowing other types in default when they are defined in field type? Why restricting to null if multiple types are allowed?
If you need any more information, I'm happy to provide them.
Cheers,
Marko

If allowed values for your exampleField are ['VALUE1', 'VALUE2'] why do you need to define its type as a union of ["null","string"]?
In avro, the default type for a union is the first one you define, hence defaulting a value to a non null string will collide with your definition resulting in the error that you get.
If allowed values are in fact ['VALUE1', 'VALUE2', null], simply switching the type definition to ["string", "null"] should solve your problem, otherwise I'd suggest dropping the null from the type.

Hey @iAlex97 thanks for the reply!
It appears that some of our schemas didn't follow avro specifications for union types as you mentioned, so we changed that and everything works fine now, so I will close this issue.
Cheers,
Marko


Feature | Dark Light Mode Toggle / Changer

Add dark light mode toggle for the whole website.
What to do:

Create a light theme for the website.
Make a toggle for light and dark themes.
Make sure the theme should persist until the user changes it again.
Use CSS variables for colors.
Try to make a good UI.

Don't:

Don't use any kind of library try to make it manually.

I want to work on this issue Can you assign me

Are you a JWOC participant?

I want to work on this issue under JWOC

I want to work on this issue under JWOC

Assigned @soumali28, Go for it.
Also, comment in discord project channel too for further working.

I want to work on this issue under JWOC.

I want to work on this issue under JWOC.

Can I work on this issue?


Apollo 5.5 RTX 2080 Perception Support

System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): Ubuntu 18.04
Apollo installed from (source or binary): Source
Apollo version (3.5, 5.0, 5.5, 6.0): 5.5
Output of apollo.sh config if on master branch:

Hi, I've been working with Apollo 5.5, setting up everything to test the perception module using LGSVL. From documentation and issues I've notice that until recently the nvidia RTX 2080 was not supported on Apollo, leading the perception module to crash (exactly what happened to me). From more recents discussions it seems that RTX 2080 is now supported by Apollo but only on release 6.0. Since on the Apollo 6.0 the camera perception is not working I want to keep with Apollo 5.5, which is more stable and have the camera perception working. I would like to know if the RTX 2080 is also supported on Apollo 5.5 or if not, what would be necessary to make it supported.
Since on Apollo 6.0 the camera perception does not work I need to keep with Apollo 5.5 due to camera importance on my current project.

We have run Apollo  success on rtx 2080. The question is not the gpu but camera perception  itself.

@oska874 so at the moment it is not possible to run the camera perception on rtx 2080 right?

As our experience no matter which gou you use ,camera perception need to be small modify. And 2080 is suitable for apollo.

I've tested the Apollo 5.5 camera perception with nvidia 1080 and it worked, but when I tried to use nvidia 2080 it crashes.

Ohoh, we test apollo 5.5 with 2080 with newest nvidia driver and cuda 11. It's okay.

Hi @lucasnmatias ,
Sorry for my late reply.
This issue is about Nvidia GPU support capability of the Apollo project.
In Apollo 5.5, only GPU cards with limited set of compute capabilities are supported, as can be seen below:
https://github.com/ApolloAuto/apollo/blob/r5.5.0/tools/cuda_library.bzl#L12
So,  GeForce GTX 1080 cards (SM=6.1) was supported in Apollo 5.5, while Geforce RTX 2080 cards (SM=7.5) was not fully supported: Maybe it runs in a backward-compatibility mode?
To enhance Apollo's capability to support more recent GPU cards, we have made breaking changes in Apollo 6.0. @jeroldchen @panfengsu Do you have any updates on camera support since Apollo 6.0 release?
You can try to modify  tools/cuda_library.bzl in Apollo 5.5 to see if sm=7.5 can work:
 "-gencode=arch=compute_61,code=sm_61",
"-gencode=arch=compute_75,code=sm_75",
 "-gencode=arch=compute_75,code=compute_75",

Most probably this can't work, and there seems no easy way to fix this issue in Apollo 5.5.


Wireless Crafting  Grid

A feature request, as the title suggests, it's the crafting grid except in your pocket! : ) Perhaps it would be an upgrade for the wireless grid made in the solder with it, a crafting grid, and maybe an advanced processor? Not sure of the difficulties this would be to code but it would be awesome raoulvdberge!

@raoulvdberge Can you please state it again? I want to know your reasoning.
I get that it may be considered OP to have all your items at your disposal whilst being able to craft almost anything, provided you have the resources, but it’s not much more different than using a wireless grid and a type of crafting table (especially the crafting table on a stick from Actually Additions).
What you could do is make the recipe expensive, like require one or two Nether stars, and make it require lots of RS. A wireless crafting grid would be so useful. Hell, you could add it and leave it disabled by default, so people have to change the config to enable this. pls


Add rounded corners to EditorProperty and EditorSpinSlider and scale corner radius to editor scale

This PR makes a number of small tweaks to the editor theme:

Adds rounded corners to the EditorProperty background, EditorSpinSlider label background, and resource sub-inspector borders and background.
Makes sub-inspector margins consistent.
Removes extra horizontal space between buttons in NodePath, Resource, and multiline string property editors.
Scale corner radius with the editor scale.

Before
After

Corner radius at 200% editor scale:
Before:

After:

Rebased and added a commit description.

For reference, here's how it looks as of the latest revision of this PR:

Contrast-enhanced version if you have trouble spotting the rounded corners

Corner radii do not seem to be scaled with the editor scale though. At 200% editor scale, rounded corners are barely noticeable (contrast-enhanced image):

It seems that most corners in the editor aren't scaled either because make_flat_stylebox() in editor_themes.cpp doesn't multiply by EDSCALE. Doing that makes corners everywhere across the editor scaled, including properties:
Before:

After:

Rebased.

Thanks!


fix: correct return type for useFloatingPortalNode

Without the explicit return type, the built TS definitions say that the return is always HTMLElement, which is not correct:
export declare const useFloatingPortalNode: ({ id, enabled, }?: {
    id?: string;
    enabled?: boolean;
}) => HTMLElement;

After this, the return type also includes null, as is correct.
An alternative solution would be to set "strict": true in tsconfig, then the null is added by TS - that might be the better solution overall, as it would add the missing nulls to other potential places as well, but it might also create more churn for users who haven't dealt with nulls..

The alternative solution sounds better because there may be other places in need of it (I previously added explicits but wasn't aware of that rule). The user not dealing with null seems like a type bug to me, anyway

Alright, changed the solution then 👍

Not sure if I should change the rolling versions myself or not, but currently it's set to only publish react-dom-interactions. I think this should publish all the packages, as the global tsconfig change can affect the types of all of them?

@mihkeleidast good point, let me update


Is the code of eval_gpt4_longqa.sh is correct?

The code in it seems to be Python code rather than a shell script.

Thanks for catching this, it's been fixed!


Fix #3366: UI: Avoid loading assets from external web pages

Describe your changes :
See #3366
I tested the changes by turning off the internet. The icons and fonts render well without external dependency.

Type of change :

[x] Improvement

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

@harshach @darth-coder00 Thanks for the reviews. I have added Fontawesome library and refactored almost the entire UI codebase. Please take another look.


Inference timing summary added to example *image_client.py tools

At the conclusion of the example Python clients, display a summary of the time needed for the inference processing:

Inference time: 151.170 ms for 8 images, 18.896 ms per image, ~52.9 images per second

I seem to have made a mistake in a previous commit and merge - the conflicting file should not be part of this pull request.

@mvpel Just rebase to master and adjust the PR to match what you want.

I'm going to close this for now. Reopen once rebased and conflicts fixed.


Integrated terminal sticky header font has broken anti-aliasing

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.92.0
OS Version: Ubuntu 22.04.4 (with latest updates)

Steps to Reproduce:

Enable sticky scroll in terminal "terminal.integrated.stickyScroll.enabled": true
Launch some command in the integrated terminal, which has output long enough to see the sticky scroll (eg. ls /bin)

The font in the sticky header has poor anti-aliasing that is significantly different from the standard font in terminal (marked using the red box on the screenshot):

This only happens in light themes though! See the difference

Yes, it is fixed in version: 1.93.0-insider (Commit: 4693ac3d4dce852b747d08d4bc54db5e35afe268).
Thank you!


Video has not been completely processed

Just a few frames are being processed
https://github.com/kijai/ComfyUI-LivePortraitKJ/assets/157212332/61a911b0-d604-4ea4-afc5-bae48d7e367d

That's because the video loader node is set to load only 32 frames, and that example vid seems to have really high frame rate. So either increase the "select_every_nth" to skip frames, or increase the load cap:

Thanks!


Create CLR metrics semantic convention

Area(s)
area:system
Is your change request related to a problem? Please describe.
The idea is to create SemConv CLR metrics for .NET, similar to JVM metrics.
System and Process metrics cover lots of useful things that can be utilized by .NET already, but similarly to Java, there are relevant metrics not covered by currently defined general metrics. Examples:

GC metrics
Thread pool metrics
Metrics around loaded/unladed assemblies
Exception related metrics

Describe the solution you'd like
Add a clr.* namespace and define metrics for the list above. Everything defined there should be very general and applicable to most .NET applications and instrumentations should be able to collect those on most environments.
Describe alternatives you've considered
An alternative could be to look at the already defined .NET metrics and try to fit the CLR metrics there. I believe that would not be ideal since those metrics are specific to higher level frameworks. CLR metrics that I propose here are purely runtime metrics, not tied to any framework. In this sense these are more like the jvm metrics for Java.
Additional context
There are already .NET metrics defined. Those are not really runtime metrics from the CLR (the runtime itself), rather they are metrics for higher level components (like ASP.NET Core, SignalR, etc.). I think these two can co-exist. Whatever higher level frameworks emit, still can live in their specific namespaces (like aspnetcore.*, signalr.*, http.client.*), but pure runtime level metrics (like GC, etc - see list above) would be on a clr.* namespace. So I suggest there should be no change to the current .NET metrics and there should be a clr.* namespace additionally to pure CLR runtime metrics.

I'd be interested in starting work on adding these.

@stevejgordon  Awesome! I will assign this to you then if it's fine. Let me know if you need any help with working with the semconv tooling/things. :)

/cc @open-telemetry/semconv-dotnet-approver

IMO standardization should happen in parallel with the implementation of the metrics. This is what we did with the HTTP metrics and it uncovered a lot of dragons. The runtime work is tracked by https://github.com/dotnet/runtime/issues/85372 which seems to be on the 9.0 roadmap but I don't see an owner assigned and there was no activity around the issue for almost a year.

Be aware that .NET runtime metrics are defined and already shipped via (one of the few) stable .NET instrumentation packages (OpenTelemetry.Instrumentation.Runtime).
Any related work should be coordinated with @open-telemetry/dotnet-maintainers, who decided to make the specification of runtime metrics part of the instrumentation library instead of semantic conventions.

@pyohannes If I've followed the Java story around this, I believe their instrumentation defined many of the metrics later added to the semantic conventions, and I saw a comment from @trask plan(ned) in the Go issue, to handle the switch by using the OTEL_SEMCONV_STABILITY_OPT_IN=jvm configuration. Would that be the way forward here?

@stevejgordon A viable first step would be to sync with the .NET SIG and align with their vision for runtime metrics.

@pyohannes Yep, I agree. Unfortunately, the timing of those SIGs is very difficult for me to attend but I'll try to get to one soon and put this on the agenda. The way I see it we have a couple of challenges here.
a) The runtime isn't yet natively instrumented with metrics and that needs some discussion, including if any metrics that are added will comply with the semantic conventions format. It sounds like right now, the intention is that they will not.
b) There is some existing naming against the stable contrib runtime instrumentation package which differs from the semantic conventions recommendations that have come since.
In regards, to naming, a potentially naive solution is to introduce an env var as Java have, that any .NET runtime metrics and/or OTel contrib instrumentation honour when setting up the metric names. That way, users could opt-in to semantic convention naming, but the existing names (or new .NET runtime names) are the default.

Looking into https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Runtime, we'd make some breaking change if we attempted to make them consistent with general semantic conventions requirements:

metrics would be renamed (process.runtime.dotnet.* -> dotnet.*)
attribute names would need to be namespaced

I.e. I don't think there is a benefit in documenting existing semantic conventions for this package and if runtime is instrumented natively, this package would either need to be deprecated or would need to come with v2 compatible with new metrics.

@lmolkova Over on the runtime issue, I have the go-ahead to implement the metrics inside the runtime itself. This will likely be a port of the existing metrics from the instrumentation package, renamed to align with whatever we agree here for the naming. I like @gregkalapos's proposal to prefix these as clr.* since that describes that actual runtime. dotnet could be too general as arguably code could be running on the CLR or something like mono for Blazor etc.
My plan going forward is to create an initial PR with experimental metrics and attributes based on those from the runtime instrumentation library while also working to see if we can implement it in the runtime before .NET 9 is locked down.
I agree that once this all happens, the runtime library could then likely be deprecated.

Looking into https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Runtime, we'd make some breaking change if we attempted to make them consistent with general semantic conventions requirements:

metrics would be renamed (process.runtime.dotnet.* -> dotnet.*)
attribute names would need to be namespaced

I.e. I don't think there is a benefit in documenting existing semantic conventions for this package and if runtime is instrumented natively, this package would either need to be deprecated or would need to come with v2 compatible with new metrics.

@lmolkova Not sure I follow your point here. Are you saying we should not define semantic conventions when there is already existing instrumentation / implementation that emits data that is inconsistent with semantic convention guidelines because we would break the implementation?
In semantic conventions we have the JVM metrics. IMHO, for consistency and usability reasons we should follow that pattern and define meaningful runtime metrics for other runtimes / languages in semantic conventions as well. So SemConv should be the single point of specification / documentation that users and vendors can rely on (rather then docs spread over different implementations).
Or do I understand you comment wrong?

Are you saying we should not define semantic conventions when there is already existing instrumentation / implementation that emits data that is inconsistent with semantic convention guidelines because we would break the implementation?

@AlexanderWert The main point here is that the OpenTelemetry.Instrumentation.Runtime package emits runtime metrics and is declared stable. If we would now add semantic conventions for .NET runtime metrics that differ from the metrics emitted by this package, .NET maintainers would need to deal with a stable instrumentation library that doesn't conform with semantic conventions.

I think it's reasonable to implement the metrics in the runtime to align with the conventions established for Java. Consumers can opt into those from the runtime or stick with the instrumentation package. At least then, we have semantic convention consistency for those being added.

My plan going forward is to create an initial PR with experimental metrics and attributes based on those from the runtime instrumentation library while also working to see if we can implement it in the runtime before .NET 9 is locked down.

@stevejgordon I think it would be a great way to start!

I think it's reasonable to implement the metrics in the runtime to align with the conventions established for Java.

I believe there were a lot of discussions wrt consistency between runtimes and the decision was to put metrics into individual namespaces and not target consistency. So JVM metrics can be used as an inspiration, but not as a guidance.
//cc @trask if I got it wrong.

Are you saying we should not define semantic conventions when there is already existing instrumentation / implementation that emits data that is inconsistent with semantic convention guidelines because we would break the implementation?

@pyohannes explained my concern much better than I would https://github.com/open-telemetry/semantic-conventions/issues/956#issuecomment-2098563081
The only thing to add is that if we defined proper CLR semconv right now we would need to keep them experimental until the .NET runtime (hopefully) emits them natively since there usually are a lot of nuances and changes coming out of the native implementation process.

@lmolkova Starting with these as experimental makes sense. I'm hoping to also contribute to the implementation in runtime so we can move to stable once those are merged and we know the release timeframe. Ideally, we'll get these in for .NET 9.


I can revert the code easily ;)

#Edit the obfuscate file:

Find the line: "$_();$_($_($_($))); $_____=$_();"
Delete all to end of file
Add some lines to see the original source code:
--------------------------------------
$source = base64_decode(gzuncompress(base64_decode($)));
$idx = strpos($source, "eval(\$__)");
$orgSource = substr($source, $idx + 24);
echo "
ORIGIN SOURCE

 $orgSource

";
---------------------------------------

Please see the php code at my gist:
https://gist.github.com/tbvinh/d3a833321b4ba7e292253aa5a76ef52e

Yes, within 5 minutes I figure it out too .. its just a "stupid base64 encode script"

Thanks for your suggestions! I appreciate this. Would you like to add more level of complexity and obfuscation? I'm more than happy to review any of your PRs you want to add here 🥳

Try this one https://github.com/pk-fr/yakpro-po
its a really good one, it transform functions, classes, variable in to random characters it also add a lot of goto statement to make it even more hard to read.

@MasterB0t How is Yak better and harder to decode? I assume you can tell us the difference and how it is better.

@2braincells2go  sure,
This software use base64_encode and gzcompress to encode the php code you can use base64_decode and gzuncompress and you will get the original code. Those function are not to encode source code or obfuscate it, made it hard to understand.
Yakpro in other hard transform code, it rename variables, functions, class name, method into random characters so if you have a function something like this
function login($username,$password) {  }
it turn it into
function dd30d0uj09r03uru30r03ur($odj0303ui0d3ur,$fj03j0j30jf30) {}
but also use the the goto statement so the code is not in order from line 1 to bottom ... you can read more about goto here

@MasterB0t Thank you for explaining! Makes perfect sense now:)

@tbvinh it works, it is just base64 encoding

https://github.com/pH-7/Obfuscator-Class/blob/bf7ad9cefa63dd40ec1109cc2ee240557adb3486/README.md?plain=1#L5


Update header for native crypto / ERC 20 token screens #2007

Closes #2007

Looks good. I understand it's a WIP. There shouldn't be "Market Price" for ERC20s (which don't have a price/ticker):

Also tap to cycle between "Market Price" etc when it's available.

yep, its wip.

@vladyslav-iosdev is this good for review?

@vladyslav-iosdev is this good for review?

yep

[ ]  Discover token (0x8C0Edb69eBF038BA0c7a4873E40fC09725064c2e on mainnet) shouldn't show Value: xxx

this one detected as ERC20Token
here as i undarstand right, old map for displaying states
native crypto where fiat value is available         -   marketPriceLabel
native crypto where fiat value is not available   -   earnedSoFarLabel
tokens, no fiat value                                             -   valueLabel
native crypto or tokens for testnets                   -   blockChainTagLabel
and now it should be like this, right?
fiat value is available                                            -   marketPriceLabel
tokens, no fiat value                                             -   valueLabel
native crypto or tokens for testnets                    -   blockChainTagLabel

Oh, I get where we misunderstood each other now :)

[ ]  Here's how it should be:

if native crypto where fiat value (i.e price/ticker) is available (so just ETH for mainnet and xDai):

show value
tap on value and switch to show Market Price
tap on the market price to show value again, i.e. looping back to (1)

(Ignore "Available", "Earned so Far". I said to include "Available" previously, but just realised we don't have a value for that yet)
If fiat value is not available:
A. If it's a testnet (RPCServer.isTestnet), show the blockchain label
B. If it's not a testnet, hide the row completely. So this will be basically be all ERC20 tokens on non-testnets

[ ]  Showing the token name and symbol at the navigation bar is good. Can you remove the name below the token icon? It seems to be showing up for ERC20 (but not native cryto). Hide it for both cases, only show the symbol. So instead of "1 AlphaWallet Discover (ALP)", only show "1 ALP", and for native crypto too: instead of "0.0997 (ETH)", just show "0.90997 ETH"

now should be ok.

Forced pushed after rebase master


Troubles with creating PMAX campaign components

I'm trying to create PMAX campaign using .Net library based on documentation provided here.
So campaign creation and assets creations passed successfully, but on asset group creation I'm getting bunch of errors about "headline,marketing image, square image...(and a lot more) assets are not enough".
Errors I'm getting are - "NOT_ENOUGH_LONG_HEADLINE_ASSET",
"NOT_ENOUGH_HEADLINE_ASSET",
"NOT_ENOUGH_DESCRIPTION_ASSET",
"NOT_ENOUGH_BUSINESS_NAME_ASSET",
"NOT_ENOUGH_MARKETING_IMAGE_ASSET",
"NOT_ENOUGH_SQUARE_MARKETING_IMAGE_ASSET",
"NOT_ENOUGH_LOGO_ASSET".
And this is in case I have successfully created all of them before trying too Create Asset Group.
I tried to use both types of Asset Group creation : with MutateOperation and AssetGroupOperation, and both were failed.
So, how can I create asset group, having already created corresponding required assets using .Net library?
I followed up all the steps in documentation, but it seems non-working solution. Can you help with this? It's not possible to create empty asset group, and also not possible to create asset group with manually given resourceName, and also not possible to link already created asset to assetGroup because in first stage of creation it's not possible to have asset group resource name. So, nothing is possible.
Here is code example which I'm using to create asset group (already having created assets)
var googleAdService = googleAdsClient.GetService(Services.V13.GoogleAdsService);

                var operations = new List<MutateOperation>();
 operations.Add(new MutateOperation()
                {
                    AssetGroupOperation = new AssetGroupOperation()
                    {
                        Create = new AssetGroup()
                        {
                            Name = $"CF-AdPro-{Guid.NewGuid()}",
                            Campaign = "customers/8951792349/campaigns/20213486313",
                            FinalUrls = { listingUrl },
                            FinalMobileUrls = { listingUrl },
                            Status = AssetGroupStatus.Enabled
                        }
                    }
                });

                var response = await googleAdService.MutateAsync(customerId, operations);

We had a temporary issue around the time you were experiencing this, and it could likely be related with the issue you are referring to.
The issue on our end has been resolved, so can you please confirm whether this is still happening to you?

yes, now we don't have problems.

Thanks for confirming!


Querying outside of .svelte files?

I don't understand the underlying complexity, I know a lot of the point of houdini is to take queries in pages into endpoints. However, I was trying to refactor a page's queries into a little util file and simply import the query stores into the page, and got the following error:
Looks like you don't have the preprocessor enabled.
Error: Looks like you don't have the preprocessor enabled.
    at Module.graphql (/$houdini/runtime/index.js:12:11)
    at /src/routes/catalog/_db.js

Is there any way to support this, or will I always have to only use queries in the .svelte pages proper?

Hey @eden-omb, thanks for checking out houdini. I think you are slightly confused about the overall approach. Houdini does not try to push queries to endpoints but instead lets you define your queries inside of your pages/components and handles the rest. It does this be generating the corresponding load function for a given page. Because of this, you must define your query inside of a .svelte file that the preprocessor can manipulate.
If you have a query that you want to reuse in multiple parts of you app, i suggest building a component that either uses and query or fragment and then reusing that where you need the information.

Closing this to keep things tidy. Please let me know if you need more help


Asserting on reading valid .tex file

Encountered when trying to extract every file in the game (lmao).
use ironworks::{ffxiv, sqpack::SqPack, Ironworks};
use std::path::Path;

fn main() {
    let game_path = Path::new("G:/Steam/steamapps/common/FINAL FANTASY XIV Online");
    let ironworks = Ironworks::new().resource(SqPack::new(ffxiv::FsResource::at(game_path)));
    let file = ironworks
        .file::<Vec<u8>>("chara/monster/m0023/obj/body/b0003/texture/v01_m0023b0003_s.tex");

    println!("{:#?}", file);
}

thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `16000`,
 right: `6`: Block info and header decompressed size differs.', C:\Users\Julian\.cargo\registry\src\github.com-1ecc6299db9ec823\ironworks-0.3.1\src\sqpack\file.rs:55:5

reopening 'cus i'm a big meanie i need a reminder to shore up 0.4 and actually release it because current cargo release is stale.

scratch that i found a real bug baby
"bg/ex4/02_mid_m5/twn/m5t1/level/envl/evl8949334.tex"
thread 'main' panicked at 'index out of bounds: the len is 13 but the index is 13', C:\Users\Julian\.cargo\git\checkouts\ironworks-836e4c5d0f0f4516\272d3af\ironworks\src\sqpack\file\texture.rs:82:33
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


Github actions

I suggest you update your github actions workflow, as it fails even if the code is ok.

I make some changes last night, but i will still make it upto date. 💯


Tag spec for publishing is too restrictive and not up to semver specs

Orb version:
11.1
What happened:
I tried to deploy a private orb with the tag v0.0.0-alpha-1 and received the following error in the Publishing Orb Release step
Malformed tag detected.
Tag: v0.0.0-alpha-1

Ensure your tag fits the standard semantic version form. Example: v1.0.0
Aborting deployment. Push a new tag with the compatible form.

Expected behavior:
Per Semver's spec:
https://semver.org/

A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.–.

The example shows 1.0.0-alpha.1, but 0.0.0-alpha-1 also meets that requirement so I expected my tag to work.
Additional Information:
Looks like the function validateProdTag here is restricting the tag: https://github.com/CircleCI-Public/orb-tools-orb/blob/master/src/scripts/publish.sh#L2

Hello George,
CircleCI's orbs do not have full semver support. A CircleCI orb can only be published as a numbered version X.Y.Z, or with a dev tag, such as namespace/orb-name@dev:x. Orbs can also be called via @volatile for the last published release (does not respect version numbers). So unfortunately it is not a limitation of this orb or tool, it is the design of the orbs product.
More information can be found here: https://circleci.com/docs/orb-concepts#semantic-versioning
If you are attempting to publish an alpha version of an orb, I recommend using a dev tag. This however is not supported by the automatic deployment job currently, due to the default tag regex.


Dashboard doesn't update for SAML user upon login

Log-in as a SAML user such as on https://qa.cloudstack.cloud/client/ (use rick user), the dashboard looks like the following and doesn't show the values correctly.

However, upon changing the project and back to default view the dashboard is fixed.
ISSUE TYPE

Bug Report

COMPONENT NAME

SAML

CLOUDSTACK VERSION

4.19

Fixed by https://github.com/apache/cloudstack/pull/9097
Tested on https://qa.cloudstack.cloud/simulator/ using SAML using rick


WebUI indicates configuration is missing after mapping a required field

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[] feature request
[] support request
[] general question

Current behavior (how does the issue manifest):
When mapping a required field, the ui highlights the activity as if not all configuration is done.
Expected behavior:
The activity should not show configuration missing if the required fields have been mapped vs configured in the configure pane.
Minimal steps to reproduce the problem (not required if feature enhancement):

Add an activity with at least one required field
Map the value into the field rather than configuring it

What is the motivation / use case for changing the behavior?
Resolve a minor visual defect
Please tell us about your environment (Operating system, docker version, browser & web ui version, etc):

Chome, macOS

Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.5.3
Additional information you deem important (e.g. issue happens only occasionally):

@fcastill have you had a chance to take a look at this?

no longer an issue.


Passed tests accrue a score instead of simple PASS/FAIL system

Matt had the idea that we could make tests less of a PASS/FAIL and instead score challengers based on some additional tests.
For instance, basic functionality will be required and may give the user 75 percent of their grade. But depending on the challenge we may check any number of other "good to have"-"important" tests. If all the tests pass then they would have a score of 100. This will require us to carefully consider each additional tests importance.
Some of these will be very specific to the challenge but others may be somewhat generic and we can record here any ideas for above and beyond scoring.
Here is one thought I had that may apply to several challenges:

Reentrancy: we could check the contract to make sure it is not vulnerable to reentrancy as this would be a critical issue

Add any more a comments to this issue.

Implementation wise, would you think of doing this by having a script check how many tests pass and assigning scores to each respective test to compile out to a scoring?

Implementation wise, would you think of doing this by having a script check how many tests pass and assigning scores to each respective test to compile out to a scoring?

Yeah, something like that. Maybe the essential tests would be in one file and the extra credit tests would live in a second file. Wondering if we could bypass needing to parse the output of the tests by using vm.ffi or the file related cheatcodes to write to a file when each test passes. Thinking about this a lot.
In addition to checking for each test passing I would like to record the gas used for each test as well so that we have that data to further comprise scores.

The biggest hurdle IMO is being able to think of several tests that are above and beyond the basic functionality. The more advance the challenges are the easier they will come but some of these contracts are just too simple to have a lot of edge cases.

The biggest hurdle IMO is being able to think of several tests that are above and beyond the basic functionality. The more advance the challenges are the easier they will come but some of these contracts are just too simple to have a lot of edge cases.

I like the idea of scoring gas optimization on every challenge, and then adding bonus features on challenges where they make sense. That way people can still prove their above and beyond knowledge, even for the simpler challenges with no edge cases.


[Enhancement][Responsive] Make the Navbar responsive to Mobile format

Problem

The Navbar looks scrunched up on mobile view.

Reference
-https://cfpb.github.io/design-stories/?path=/docs/components-navbar--overview

This component has not yet been picked up to be built but I will leave this issue to document the bug.


Doesn’t work on 1.16.2.

Game crashes for reasons like snow/water rendering on 1.16.2 when the mod is active.
Any plans on updating to the next version and fixing this problem?
Thank you.

New release soon yes.


[core] improve reusability of animation code in Clarity

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[x] enhancement

Expected behavior

It would be nice to re-use functions that generate animation metadata (we have collapse, fade, fade-slide, and slide) so that the animations are centralized and standardized.
Actual behavior

As part of AoT refactor, the animation metadata has been hard-coded into the components (Modal and StackBlock). Let's revisit this to evaluate if we can import functions into the component decorator as we used to before the AoT. There might be a way to make ngc happy. Need to investigate.
Reproduction of behavior

N/A
Environment details

Angular version: 2.2.X

Clarity version: 0.8.X

OS and version: All

Browser: All

@jeeyun: May be this helps: https://github.com/btroncone/ngrx-store-localstorage/issues/13

Closing as stale.


Query-frontend Data faults In Grafana

my thanos query-frontend start command is :
docker run -d --network host --name thanos-queryfrontend -v /etc/thanos:/etc/thanos thanosio/thanos:v0.19.0-rc.2
query-frontend
--http-address=<IP_ADDRESS>:15902
--query-frontend.downstream-url=http://<IP_ADDRESS>:11902
--query-range.split-interval=12h
--labels.split-interval=12h
--labels.max-retries-per-request=10
--query-range.align-range-with-step
--query-frontend.compress-responses
--query-range.partial-response
--query-range.request-downsampled
but in grafana , when i look up historical data , there is a lack of data

query-frontend
if i set grafana data source to query , there would be no such situation

query
why is this happening ?  because of query-frontend cahing or what else ??

@DreamDZhu Yes, it might be related to caching. But I need to investigate. Do you configure any HTTP parameters in your Prometheus datasource? Like downsampling?

@DreamDZhu Yes, it might be related to caching. But I need to investigate. Do you configure any HTTP parameters in your Prometheus datasource? Like downsampling?

Thank you for your reply 。 In  compact , I set 5 minutes of down-sampling data and 60 minutes of down-sampling data for 60 days 。
I think I found the cause of the problem.
Since my sidecar was set cmd  :
-min-time=-2h
and my store set cmd :
--store_min_time: -180d
--store_max_time: -2h
When the local prometheus generates the TSDB data, because the block is too large and the network is limited, it is not uploaded to the object storage in time, which leads to the data fault between the sidecar and the store merge query.
At this point Using queryfrontend to query ,  his cache causes this problem in the grafana.
I'd like to ask how to set queryfrontend cache expiration date ?

@DreamDZhu Yes, it might be related to caching. But I need to investigate. Do you configure any HTTP parameters in your Prometheus datasource? Like downsampling?

@yeya24 Thank you for your reply 。 In compact , I set 5 minutes of down-sampling data and 60 minutes of down-sampling data for 60 days 。
I think I found the cause of the problem.
Since my sidecar was set cmd :
-min-time=-2h
and my store set cmd :
--store_min_time: -180d
--store_max_time: -2h
When the local prometheus generates the TSDB data, because the block is too large and the network is limited, it is not uploaded to the object storage in time, which leads to the data fault between the sidecar and the store merge query.
At this point Using queryfrontend to query , his cache causes this problem in the grafana.
I'd like to ask how to set queryfrontend cache expiration date ?

expiration parameter should control that (https://thanos.io/tip/components/query-frontend.md/#memcached). Have you tried it? Thank you for digging into this! As this is a non-issue, I will close this to keep our issue tracker a bit tidier. I hope you understand :hugs:


Add test for $.fire

I don't know if the second test with params needed so much test.
So let me know if it's too much, or if there is better way to do it. :)

Tests are failing. Was that expected?

Nevermind, I don't think this was you, @wcastand. Sorry.

Yeah i make the same mistake and look for error for like 30min until i see the build failed already without my PR :P


WIP: virtual machines UI

This patch extends viewing of Kubevirt virtual machines (VMs)
in Overview page by separate listing of Virtual Machines (vm) and detail
pages for vm and Virtual Machine Instance (vmi) entity.
The api communicates with old api endpoints ovm/vm.

Menu > Applications > Virtual Machines entry added
Pages listing Virtual Machines and Virtual Machines added
vms (currently still ovms) are not listed in Menu > Resources > Other
resources page; vmi are still listed since this is the only listing
we provide
Pages showing details of vms and ovms added. Each detail page shows
Details, Events and Metrics (if enabled) tab. Ovm detail allows to
control life-cycle actions: Start, Restart, Stop.
Click to VM name in Overview page now leads to a VM detail page.
Overview row allow YAML editing.

Common parts of Overview page and VM detail page shares code.
Metrics and RDP were coded in best effort manner.
Screenshots

@mareklibra @mfrances17 just to let you know

this needs to be verified against most recent kubevirt (https://github.com/kubevirt/kubevirt/releases/tag/v0.7.0-alpha.1)

Commit adding compatibility for kubevirt https://github.com/kubevirt/kubevirt/releases/tag/v0.7.0-alpha.1 added. It seems to work however thorough verification is still needed.

Thanks @jniederm!
FYI @spadgett @serenamarie125

Note also that tabbing from the kebab menu should tab through each menu item in the kebab

@serenamarie125 , thanks for your comments. I'll address them within a follow-up.

Fix for capital letters: #3


Remove duplicate config check

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

#sign-off


[WIP] add graphical support to define parameters with sirius

Changes made from https://github.com/ipa320/ros-model/pull/104
Non-working version, do not merge!


testHelper handleFindAll cannot handle RESTAdapter relationships

It looks like the intent of the testHelper is handle both JSONAPI and other adapters. However, the responseJSON built is incorrect for RESTAdapter relationships.
Currently
{
  posts: [
    {
      id: 1,
      author: {
        id: 1,
        name: "bob"
      }
    }
  ]
}

But should be
{
  posts: [
    {
      id: 1,
      author: 1
    }
  ],
 authors: [
  {
    id: 1,
   name: "bob"
  }
 ]
}

hmm .. interesting .. I wonder why the tests were passing for the REST adapter .. I will investigate further .. ( do I have relationship test for them? ( not sure? ) )  but I am doing big refactor of the json responses right now, so this issue might be fixable in this refactor if I can get a failing test.

Huh, interestingly, it seems to work if the relationship fields are defined with { async: true }

That is kinda interesting .. I will factor that in when testing .. man .. that is going to be another whopper, testing sync and async for everything .. I am doing alittle bit now .. but for everything .. gulp ..

I think it works because your test helper builds the models and adds them to the store. When the request is made, the async fields are ignored. When they are looked up, they already exist in the store, so ED does not make another network request.

I don't think that is correct .. but feel free to slap some code in here to prove me wrong.
I will slap first:
  handleFindAll: function () {
    var args = Array.prototype.slice.call(arguments);
    var modelName = args.shift();
    var json = FactoryGuy.buildList.apply(FactoryGuy, arguments);

    var responseJson;
    if (!FactoryGuy.useJSONAPI()) {
      responseJson = this.mapFindAll(modelName, json);
    } else {
      responseJson = json;
    }
    var url = this.buildURL(modelName);
    this.stubEndpointForHttpRequest(url, responseJson);
  },

All this is doing is building json and returning it in mockjax call

Ah yeah, buildList not makeList...
Looking again at my test, I see that the template does not render related model properties.

So, is that a nice failure case that I can bank on?

@FilmKnurd , I am working on this one now.  Boy, this is such a good issue.
It's forcing me to change the way a few things work ( simplifying here, complicating there ) .. and now the build method will return correctly formatted REST or AMS data with sideloaded relationships  that can be pushPayloaded right into the store or sent right to the adapter through mockjax response handler

@FilmKnurd , finally got this one .. ( v2.0.1 ) Let me know if there are any problems.  This was a big nternal refactor, but very very worth it, so thanks for pushing me along.

All my tests are passing :-)


Mobstate Refactor

About the PR
A complete refactor of mob state to utilize a ticketing system. Each mob state has a ticket pool. The lowest mobstate with the most tickets (Death or Crit) is the active state. By default entities have 0 tickets in each pool, systems can add or remove tickets from a state's pool to change the state.
Additionally, mob state thresholds now have their own component and system. Eventually the mob threshold system will be depreciated in favour of body simulation systems. This also helps simplify the mobstate logic and differentiate functionality.
Example:
If I request a death ticket, it will immediately cause the targeted entity to enter the dead state.  If I later return my dead state ticket, the entity will transition to the crit state since that is the lowest state that has tickets.
How is this useful?:
One of the major issues with the old mobstate system is that many different gameplay systems all interacted with it, this made it's logic very complex and resulted in alot of unneeded dependencies. This ticketing system allows multiple systems to interact with mob states without causing redundant dependencies.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

!!!DOWNSTREAMS NOTICE!!!:
There is a breaking change in YAML, replace any current uses of 'MobState' in entity prototypes with 'MobThresholds', otherwise mob thresholds will not work properly. I've already made this change in the WizDen YAML files if you need a reference.
Changelog

Surgery, just a week away...

This is required for wounds/bobbysim

Surgery is just a week away.


Issue 373, v2: Upgrade rdf-toolkit and Java

This Pull Request will resolve all requirements of Issue 373.
This PR adjusts the strategy of v1, PR 386, due to issues having been found when running a normalized file through rdf-toolkit multiple times.  Issue documentation is on CASE-Examples PR 75.  pre-commit usage is removed from v2 of resolving Issue 373.
Review steps taken:

[x] Pull request is against correct branch
[x] CI passes in (CASE/UCO) feature branch
[ ] CI passes in (CASE/UCO) current unstable branch (merge-commit)
[ ] Impact on SHACL validation reviewed for CASE-Examples
[ ] Impact on SHACL validation remediated for CASE-Examples
[ ] Impact on SHACL validation reviewed for casework.github.io
[ ] Impact on SHACL validation remediated for casework.github.io

The update changes all ordered lists into sets of IRIs. The application can only select one set element.

I'm not quite sure I follow this remark - the syntactic style of the ordered lists is changed, but they have not been converted into sets.  ( ... ) is Turtle shorthand for an RDF List.  Or is there something I'm missing?

Closing as superseded by PR 398.


Create Game Classes and Methods to track things like Start Game, End Game, Player Details and Abilities

The changes include:

Creation of a /util folder containing a game_class.py with a series of Game, Player, and Abilities related classes
Update of the basic_bot.py to have an example of starting the game and then output game and player details

User Story:
https://thomas-arambula-iii.atlassian.net/browse/CAA-25

Reviewing this now.

Made some changes to fix the pre-commit linting complaints as well as standardized the type-hinting for Pythonic best practices.

Didn't mean to close this. Merging to develop branch now. Thanks @Zuzah


Supported method to inject a custom fluentd configuration

What kind of request is this (question/bug/enhancement/feature request):
Enhancement Request
Request a supported solution from Rancher to drop logs generated by the fluentd containers or even better, a supported method to inject a custom fluentd configuration.
Rancher version:
v2.1.3

It was listed as "advanced mode" internally in engineering: https://github.com/rancher/rancher/issues/15558


clean-math-thesis:0.2.0

I am submitting

[ ] a new package
[x] an update for a package

Description: We implemented several improvements, among them

possibility to set the link color
improved equation numbering: possibility to use equate or i-figured to enable sub-numbering or equation numbers that include the chapter
improved handling of contents: no need for #pagebreak() between chapters anymore
title and author in pdf meta data now

And sorry for the two PRs I had to close, this one should finally be merged!

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Thanks :)


change templates layout to match sb admin styling (task #1577)

Affected templates:

register
profile
change password

:+1:


Fix update-community and add logging

Changes
Pass organization info into Update-Community, so it can find the right file.
Add some debugging output.

/kind bug
/assign @n3wscott

/assign @n3wscott

(It turns out I broke syncing OWNERS_ALIASES when I added support for knative-sandbox)


Apply rule button disabled

Hi there,
I'd like to disable finding CVE-2019-18276 for as long as it's not patchable. However, when I try to create such rule (CVEs value CVE-2019-18276 & 'Non-patchable' checkbox checked), I cannot select subscription (the checkbox seems to be disabled) and 'Apply rule' button is disabled as well.
Am I missing something? is there anyonther way to create such rule? do you have any template?

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

ID: 29434ef1-ac47-9226-c97a-b3ebd76438b1
Version Independent ID: d7ca7e00-09b4-819d-2e8b-f7699024a0e4
Content: How to use Azure Defender for container registries
Content Source: articles/security-center/defender-for-container-registries-usage.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@slebodat Thank you for your feedback  We will investigate and update the thread.

@slebodat Can you confirm if you have the Edit role for Azure policy. What role do you have on the subscription you are trying to disable this on ?

@vipulsparsh yes, I can. I'm subscription's owner and  tenant's GA.

@slebodat Apologies for delay on this. Can you create a support case with us for further investigation. Thanks


[#108] ExtendedData returns wrong number of sections

Signed-off-by: Marcus Pridham<EMAIL_ADDRESS>Signed-off-by: David Joo<EMAIL_ADDRESS>Signed-off-by: Saliou Diallo<EMAIL_ADDRESS>

@marcuspridham Could you please grab the latest develop branch and merge locally and push another commit? Much easier to do on your machine. May be a case of blowing away the project file you have locally and replacing with the latest from develop. Definitely recommending reloading in XCode after the merge to ensure the build/project isn't broken. Thanks!

@marcuspridham Could you please grab the latest develop branch and merge locally and push another commit? Much easier to do on your machine. May be a case of blowing away the project file you have locally and replacing with the latest from develop. Definitely recommending reloading in XCode after the merge to ensure the build/project isn't broken. Thanks!


The overriding stdenv example doesn't seem to work

I've followed the simple example, but I'm seeing:
       error: The option `mkDerivation.stdenv' does not exist. Definition values:
       - In `<unknown-file>': <derivation stdenv-linux>

Edit: I downloaded the examples and the same issue is occurring.

Haven't been able to achieve a workaround... I know Helix switched to using crane and seems to have this working, but I do prefer this project due to simplicity.

This looks like it was because dream2nix changed something upstream, and the CI wasn't running tests for that specific example. deps.stdenv should be used instead of mkDerivation.stdenv. I've updated the examples to match that.


Upgrade to 7.0.0.CR1

[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for other issues
[x] Attached commits represent units of work and are properly formatted
[x] You have read and agreed to the Developer Certificate of Origin (DCO) (see CONTRIBUTING.md)
[x] Every commit contains Signed-off-by: Your Name<EMAIL_ADDRESS>- use git commit -s

@ryanzhang or @rbarriuso please review.

Looks good to me. Just to double check: the DISTRIBUTION_PATH of the execution server (which is used in the install script) hasn't changed, right? Now it's jboss-bpmsuite-7.0-execution-server-ee7

@rbarriuso I built & started the images without any issue, so I presume it is the same.


net_symbols package in final_fcn_resnet50.py cannot be found everywhere

Hi ascust，
Thank you very much for sharing your code here and i really appreciate it.
Recently, I found  a problem of your code. The net_symbols package used in final_fcn_resnet50.py cannot be found everywhere. Could you please kindly tell me how i should install this package to my computer to run the code?
Thank you very much for your help in advance.
Best regards
yuan

oh, i found it from here: https://github.com/ascust/BDWSS/tree/master/cores/symbols.
Thanks. :-)


Whois

Aim
This script will retrieve and parse Whois (technically RDAP) information for IP addresses.
Details
The script has the ability to quickly perform reverse DNS lookups for any given domain name(s). This script was created primarily to facilitate recursive Whois queries.
Do I want to work on this:

[x]  Yes
[ ] No

Go Ahead @infiniteoverflow


Add other states for bspwm dimmed desktops

Hi Michael, one more idea. :D
On bspwm, you can configure overrides for dimmed desktop, however, it overrides any other state, including occupied, empty, urgent, etc. It would be nice if we could configure overriding dimmed granular to the other states.
Use case:
On active monitor, I have a bar like this where active desktop have a blue overline and occupied ones have a gray overline.
However, if I want to make the dimmed desktops with a gray overline for occupied ones and no overline for empty, it's not possible at the moment (or I haven't figured out how?). If I override the overline color on dimmed, it applied to all desktops on that monitor.

Yeah that's how it works at the moment. That's how I styled my bar when I wrote it so that's why. But yeah, it would be a nice thing to have.

ah, so, it wasn't just me goofing. :D nice to know. also, sorry for those issue opening lately. i really enjoy the project and would love to send some pr, but I have absolutely no experience with X/XCB programming. maybe in the future. :D

merged #167


Drive Speed

Want to try getting used to faster drive for MTI submission. For driver 1, change the fast mode (pressing down on the left joystick) to full speed (I think it's set to .8 right now), and the normal drive speed increased by .1 -Gianni

Fast mode: 0.9 -> 1.0
Normal mode: 0.65 -> 0.75
Fixed with commit https://github.com/FTC7393/FtcRobotController/commit/9412fd6a36c3cb3a939da84e1fe2749606673663


Authenticating Users with native file sessions

Hi,
I'm stuck on a problem that I haven't found a solution yet, I've tried too many things to tell. Here is the reason for this issue.
I would like to set up a websocket channel allowing users to receive their notifications on the site. But for that I need to check if the user is authenticated and I need to know who he is to send his notifications to him only.
Note: I am using localhost for development (Symfony CLI web server).
So, here is where I stand:
For the storage of sessions I use the native_file handler. I started by declaring it as a :
# config/services.yaml
imports:
    - { resource: 'parameters.yaml' }

services:
    app.session.handler.native_file:
        public: true
        class: Symfony\Component\HttpFoundation\Session\Storage\Handler\NativeFileSessionHandler
        arguments:
            - '%app.session.native_file.save_path%'

Then I configured the framework to use this service for session management and so far everything works fine:
# config/packages/framework.yaml
framework:
    secret: '%env(APP_SECRET)%'
    #csrf_protection: true
    #http_method_override: true

    session:
        handler_id:      'app.session.handler.native_file'
        cookie_secure:   'auto'
        # cookie_samesite: lax

For your information, here is my current security configuration:
# config/packages/security.yaml
security:
    # https://symfony.com/doc/current/security.html#where-do-users-come-from-user-providers
    enable_authenticator_manager: true # Necessary to login throttling. See: https://symfony.com/doc/current/security/experimental_authenticators.html
    providers:
        app_user_provider:
            entity:
                class: App\Entity\User\User
                property: email
    password_hashers:
        App\Entity\User\User:
            algorithm: auto # Auto-selects the best possible hashing algorithm.
    firewalls:
        main:
            anonymous: false # Must be false with `enable_authenticator_manager: true`.
            lazy:      true
            provider:  app_user_provider
            login_throttling: # See: https://symfony.com/doc/current/security.html#limiting-login-attempts and framework.rate_limiter in framework.yaml
                max_attempts: 3 # 3 login attempts per minute.
            custom_authenticator: App\Security\LoginFormAuthenticator
            logout:
                path: logout
                invalidate_session: false
            remember_me:
                secret:   '%kernel.secret%'
                lifetime: 1_296_000 # 15 days in seconds
                path: /
                name: EEREMEMBERME # Cookie name

Now my current gos_websocket configuration:
# config/packages/gos_web_socket.yaml
gos_web_socket:
    authentication:
        enable_authenticator: true
        providers:
            session:
                session_handler: 'app.session.handler.native_file'
                firewalls:       'main'
        storage:
            type: in_memory
    server:
        # The host IP address on the server which connections for the websocket server are accepted.
        host: <IP_ADDRESS>
        # The port on the server which connections for the websocket server are accepted.
        port: 8080

        origin_check: true

        router:
            resources:
                -
                    resource: '%kernel.project_dir%/config/pubsub/websocket/*'
                    type: 'glob'

Finally, I created a Topic, the NotificationsTopic:
<?php

namespace App\Websocket\Topic;

use App\Entity\User\User;
use Gos\Bundle\WebSocketBundle\Authentication\ConnectionRepositoryInterface;
use Gos\Bundle\WebSocketBundle\Router\WampRequest;
use Gos\Bundle\WebSocketBundle\Topic\TopicInterface;
use Ratchet\ConnectionInterface;
use Ratchet\Wamp\Topic;

class NotificationsTopic implements TopicInterface {
    private ConnectionRepositoryInterface $connectionRepository;

    public function __construct(ConnectionRepositoryInterface $connectionRepository) {
        $this->connectionRepository = $connectionRepository;
    }

    public function onSubscribe(ConnectionInterface $connection, Topic $topic, WampRequest $request) {
        $user = $this->connectionRepository->getUser($connection); // empty string
        $topic->broadcast(['msg' => gettype($user) . ' : ' . $user]);
        $user = $this->connectionRepository->findTokenForConnection($connection)->getUser(); // empty string
        $topic->broadcast(['msg' => gettype($user) . ' : ' . $user]);

        if (!$user instanceof User) {
            $topic->broadcast(['msg' => $connection->resourceId . ' has joined ' . $topic->getId()]);
        } else {
            $topic->broadcast(['msg' => $connection->resourceId . ' (' . $user->getEmail() . ') has joined ' . $topic->getId()]);
        }

        $topic->broadcast(['msg' => 'SessionId: ' . $connection->WAMP->sessionId]); // Generated session ID
        $topic->broadcast(['msg' => 'SessionId: ' . $connection->Session->getId()]); // null (or empty string ?)

        // TODO: Implement onSubscribe() method.
    }

    public function onUnSubscribe(ConnectionInterface $connection, Topic $topic, WampRequest $request) {
        $topic->broadcast(['msg' => $connection->resourceId.' has left '.$topic->getId()]);
        // TODO: Implement onUnSubscribe() method.
    }

    /**
     * @inheritDoc
     */
    public function onPublish(ConnectionInterface $connection, Topic $topic, WampRequest $request, $event, array $exclude, array $eligible) {
        $topic->broadcast(['msg' => $event]);
        // TODO: Implement onPublish() method.
    }

    /**
     * Name of the topic.
     * @return string
     */
    public function getName(): string {
        return 'notifications.topic';
    }
}

And finally his statement as a service:
    # Websocket services
    App\Websocket\Topic\NotificationsTopic:
        tags:
            - { name: gos_web_socket.topic }

This is what I get:
No errors are returned (neither in the logs nor elsewhere), however all my attempts to get the user end up with an empty string.
$connection->WAMP->sessionId does return a session id but it doesn't match any available sessions.
And $connection->Session->getId() returns nothing.
I don't know what to try anymore, what to do for the moment.
Does anyone have any ideas?
Thanks in advance,

As noted in the docs, not all of the session handlers are compatible with Ratchet’s SessionProvider component, so you need to make sure you’re using a compatible handler.

Oh boy, I'm sorry, I didn't see that.
Too bad..
I thank you very much.

When I switched to the pdo session handler, it still didn't work, the result was identical.
I found a solution, I put it here, if it helps someone.
As you probably know, the session must be accessible to the web server and the websocket server. For that, their domain names must be identical (to keep it simple). Except that the GeniusOfSymfony/WebSocketBundle configuration only takes an IP address as host.
So, on the JS client side, I replaced :
const webSocket = WS.connect('ws://{{ gos_web_socket_server_host }}:{{ gos_web_socket_server_port }}'); (which gives the IP address of the server).
By:
const webSocket = WS.connect('ws://localhost:{{ gos_web_socket_server_port }}'); (because I am in localhost).
And it works!


fix(eventhandler): add all devices to hierarchy before filtering

Signed-off-by: Akhil Mohan<EMAIL_ADDRESS>Why is this PR required? What issue does it fix?:
When a filter excludes the parent disk and includes the partition, it caused to NDM error out, because the parent disk was not added in the hierarchy cache. This PR adds the device into the hierachy cache irrespective of whether it is filtered or not. This removes issues while such filter configurations are provided.
What this PR does?:

add device to hierarchy cache before filtering

Does this PR require any upgrade changes?:
No
If the changes in this PR are manually verified, list down the scenarios covered::

tested with the scenario mentioned in openebs/openebs#3321

Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[x] Fixes openebs/openebs#3321
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[x] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #538 (469d896) into master (6bfbfe7) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #538   +/-   ##
=======================================
  Coverage   47.64%   47.64%
=======================================
  Files          73       73
  Lines        3373     3373
=======================================
  Hits         1607     1607
  Misses       1601     1601
  Partials      165      165

Impacted Files
Coverage Δ

cmd/ndm_daemonset/probe/addhandler.go
71.13% <ø> (-0.10%)
:arrow_down:

cmd/ndm_daemonset/probe/eventhandler.go
43.63% <100.00%> (+1.04%)
:arrow_up:

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 6bfbfe7...469d896. Read the comment docs.


Log gql query before it is sent.

Is it possible to add interceptor to gql_link so that I can display queries before it is sent. I know there is some kind of a transformer maybe it can be used.

You can use a TransformLink to log requests and responses. Just log to query and then return it in the ?requestTransformer` .
Or you can log in the HTTP layer, e.g. if you use dio, you can just add a PrettyDioLogger to your dio client.


PR : Level

Description
The User can see his level and current exp in the left corner (needs styling @DepartureLV おねがいします)
The Data gets fetched

upon loading first time
each time the user guesses: done with a state that gets passed down to the poi card

Run npm i to install shad/cn progress bar
Card Link
https://3.basecamp.com/5802516/buckets/37608217/card_tables/cards/7493055345
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

[x] Manually, ran npm run build as well

Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Move progress.tsx into _component/ui then delete the root/component/ui folder before push. By default shadcn will created a folder at root and create a file in that folder. But we have our own component folder so that folder is not needed. Also shadcn didn't require a npm install since it just created a file not node module.

https://github.com/CC34-Senior-Project/senior-project-frontend/assets/128316768/60310215-4a5b-4aef-a13a-20609d5954f5
https://github.com/CC34-Senior-Project/senior-project-frontend/assets/128316768/ba506fd9-2324-49ae-abc4-655a7a6da00f


[web][a11y] Web cannot enable accessibility when the page has a focused autofillable text element

Observed both in Desktop Chrome with VoiceOver. Text field gets VoiceOver focus in the web area, therefore user is not able to enable accessibility button.
[✓] Flutter (Channel unknown, 1.20.0-3.0.pre.76, on Mac OS X 10.15.4 19E287, locale en-US)
    • Flutter version 1.20.0-3.0.pre.76 at /Users/nurhan/development/flutter
    • Framework revision fd7a72ee6f (49 minutes ago), 2020-06-26 15:18:02 -0700
    • Engine revision fc0e27210c
    • Dart version 2.9.0 (build 2.9.0-19.0.dev 63cf56d925)

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/nurhan/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.46.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.0

[✓] Connected device (4 available)
    • sdk gphone x86 • emulator-5554                        • android-x86    • Android 11 (API 30) (emulator)
    • iPhone 11 Pro  • 82A0BF3E-8596-4AE4-BFA3-4E5E45FE2CF3 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-13-0 (simulator)
    • Web Server     • web-server                           • web-javascript • Flutter Tools
    • Chrome         • chrome                               • web-javascript • Google Chrome 83.0.4103.116

This worked when tested with gallery code (when I locally run it with the current engine).
It didn't work with the example https://gist.github.com/nturgut/de835f60afe83d945d2573ab5ddd375e
Therefore, I suspect, using form element for implementing Autofill caused the issue.

some update: @nturgut  will get back to this issue once they has time.

flutter doctor -v
[✓] Flutter (Channel master, 1.22.0-10.0.pre.251, on Mac OS X 10.15.6 19G2021
    x86_64, locale en-GB)
    • Flutter version 1.22.0-10.0.pre.251 at
      /Users/tahatesser/Code/flutter_master
    • Framework revision d26268bb9e (13 hours ago), 2020-09-18 09:06:26 +0900
    • Engine revision 2abe69c608
    • Dart version 2.10.0 (build 2.10.0-136.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0, Build version 12A7209
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 49.0.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.49.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.14.1

[✓] Connected device (3 available)
    • macOS (desktop)  • macos      • darwin-x64     • Mac OS X 10.15.6 19G2021
      x86_64
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome
      85.0.4183.102

• No issues found!

/cc @nturgut , is this dup of 60404?


Use nodes for alpha clipping

This is a PR that merges into a single one the following PR #2147 #2152 #2153 from @scurest
Keeping only this one open, as it is easier to test it all in once, and less maintenance tasks.
For details, check on each PR

EEVEE next is now default since yesterday.
I am out of office this week, PR will be merged next week


Failed to install from repository

I'm using Ubuntu with Docker to work with OctoberCMS, using this image.
After create the container I follow the steps on the Readme with the following result:
$ sudo docker exec octobercms_web_1 composer update
    1/13:	http://repo.packagist.org/p/provider-archived$5c1908fde45bc1e079038576bffd87719ff95f6527dee583897cd4b324d9fe1e.json
    2/13:	http://repo.packagist.org/p/provider-2020-04$ef737c3de718fa98deb29654a0c52ea9b180e4fdf4a25ba22f292dae8b2f22c1.json
    3/13:	http://repo.packagist.org/p/provider-2019-10$7568d1c39206f33251365b82b7134f502ffee570631941c9cb775f259603aab5.json
    4/13:	http://repo.packagist.org/p/provider-latest$548015ce5ac59f6ec7c2a8bf982782ac3226e5d2fe33ca56e23a7a791d86dd71.json
    5/13:	http://repo.packagist.org/p/provider-2019-07$e59eba9f1a57e928f08e2409d9a543a937531c13ec7317ad86a20a2d3546f9e1.json
    6/13:	http://repo.packagist.org/p/provider-2016$49676b5257a094cd2052e0c0ba81cd4d66464f7dad1eb120889fcf2ba6511093.json
    7/13:	http://repo.packagist.org/p/provider-2020-01$bc44ec901584f77b837f47a12c3d7c464cb70543b3d92b9fea822b234afda790.json
    8/13:	http://repo.packagist.org/p/provider-2019$e43f35fefb76a3b0aa71f888106a4809121ec49d20c3db9c672cd56705a4c463.json
    9/13:	http://repo.packagist.org/p/provider-2015$d92c2535980f04ed2ca88296ab4ea9c8101e7b46250d8ac95e09435da2095676.json
    10/13:	http://repo.packagist.org/p/provider-2014$c8b3b14ed88b7d84e62d615be1c1d7527b14183d339941da66717adeebb5037e.json
    11/13:	http://repo.packagist.org/p/provider-2017$8798d76d15734215ece6ed74ca73a0ee812d1d911561ea84457e769e67ef8d1f.json
    12/13:	http://repo.packagist.org/p/provider-2013$8f2b738de0bff98323c1b7190f9b4aafa7ef7830c32b90e89c20ada893fed5b0.json
    13/13:	http://repo.packagist.org/p/provider-2018$7c4045a8b768ddf2107bacc914a63b1f78f1b70fead48660d761959ade04f1b3.json
    Finished: success: 13, skipped: 0, failure: 0, total: 13
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - wikimedia/composer-merge-plugin dev-master requires php >=7.2.0 -> your PHP version (7.2.27) overridden by "config.platform.php" version (7.0.8) does not satisfy that requirement.
    - wikimedia/composer-merge-plugin dev-master requires php >=7.2.0 -> your PHP version (7.2.27) overridden by "config.platform.php" version (7.0.8) does not satisfy that requirement.
    - Installation request for wikimedia/composer-merge-plugin dev-master -> satisfiable by wikimedia/composer-merge-plugin[dev-master].

$ sudo docker exec octobercms_web_1 composer require rainlab/debugbar
    1/3:	http://repo.packagist.org/p/provider-latest$191746a3b21d50c2b808e2afcc46556f831af144ab5f6dac88b039ffb1fcc4c8.json
    2/3:	http://repo.packagist.org/p/provider-2018$d0dc2ad3b6ecdcca7d195a7122b7bbf690456254e11056eec89b3b3161059c1e.json
    3/3:	http://repo.packagist.org/p/provider-2020-01$13971cb365a1914b43bec6da67cdf76888fd35258a73c6fb06b972a37d5c4930.json
    Finished: success: 3, skipped: 0, failure: 0, total: 3
Using version ^3.0 for rainlab/debugbar
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
    1/3:	https://codeload.github.com/rainlab/debugbar-plugin/legacy.zip/a37499b3ac8749c026ccef5aca176faae7b13f13
    2/3:	https://codeload.github.com/barryvdh/laravel-debugbar/legacy.zip/67ced7c6a7451b8bb079d92a57d75f1111f3342d
    3/3:	https://codeload.github.com/maximebf/php-debugbar/legacy.zip/6c4277f6117e4864966c9cb58fb835cee8c74a1e
    Finished: success: 3, skipped: 0, failure: 0, total: 3
Package operations: 3 installs, 0 updates, 0 removals
  - Installing maximebf/debugbar (v1.15.1): Loading from cache
  - Installing barryvdh/laravel-debugbar (v3.3.1): Loading from cache
  - Installing rainlab/debugbar (3.0.0): Loading from cache
maximebf/debugbar suggests installing predis/predis (Redis storage)
Package jakub-onderka/php-console-color is abandoned, you should avoid using it. Use php-parallel-lint/php-console-color instead.
Package jakub-onderka/php-console-highlighter is abandoned, you should avoid using it. Use php-parallel-lint/php-console-highlighter instead.
Package jakub-onderka/php-parallel-lint is abandoned, you should avoid using it. Use php-parallel-lint/php-parallel-lint instead.
Package leafo/scssphp is abandoned, you should avoid using it. Use scssphp/scssphp instead.
Package mtdowling/cron-expression is abandoned, you should avoid using it. Use dragonmantank/cron-expression instead.
Package phpunit/phpunit-mock-objects is abandoned, you should avoid using it. No replacement was suggested.
Writing lock file
Generating autoload files
Carbon 1 is deprecated, see how to migrate to Carbon 2.
https://carbon.nesbot.com/docs/#api-carbon-2
    You can run './vendor/bin/upgrade-carbon' to get help in updating carbon and other frameworks and libraries that depend on it.
> php artisan october:util set build
-
*** October sets build: 465
-
Ping? Pong!
-
Ping? Pong!
-
> php artisan package:discover
Discovered Package: jenssegers/date
Discovered Package: laravel/tinker
Discovered Package: nesbot/carbon
Package manifest generated successfully.

As a result OctoberCMS is broken: nothing is shown on the frontend nor the backend, just a blank page.
The log from the container shows:
[Thu Apr 16 13:11:48.691816 2020] [php7:error] [pid 20] [client <IP_ADDRESS>:42846] PHP Fatal error:  Uncaught ReflectionException: Class view does not exist in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php:752\nStack trace:\n#0 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(752): ReflectionClass->__construct('view')\n#1 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(631): Illuminate\\Container\\Container->build('view')\n#2 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(586): Illuminate\\Container\\Container->resolve('view', Array)\n#3 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(732): Illuminate\\Container\\Container->make('view', Array)\n#4 /var/www/html/vendor/october/rain/src/Foundation/Application.php(158): Illuminate\\Foundation\\Application->make('view')\n#5 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php(110): October\\Rain\\Foundation\\Application->make('view', Array)\n#6 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundat in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 752
[Thu Apr 16 13:11:48.692776 2020] [php7:error] [pid 20] [client <IP_ADDRESS>:42846] PHP Fatal error:  Uncaught ReflectionException: Class view does not exist in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php:752\nStack trace:\n#0 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(752): ReflectionClass->__construct('view')\n#1 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(631): Illuminate\\Container\\Container->build('view')\n#2 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(586): Illuminate\\Container\\Container->resolve('view', Array)\n#3 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(732): Illuminate\\Container\\Container->make('view', Array)\n#4 /var/www/html/vendor/october/rain/src/Foundation/Application.php(158): Illuminate\\Foundation\\Application->make('view')\n#5 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php(110): October\\Rain\\Foundation\\Application->make('view', Array)\n#6 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundat in /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php on line 752
<IP_ADDRESS> - - [16/Apr/2020:13:11:48 +0200] "GET / HTTP/1.1" 500 211 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0"

Any idea?

That's an issue for the docker container repo, either remove the platform requirement from your composer.json or change the wikimedia merge plugin to require 1.4.1 instead of dev-master.


chore: replace tslint with prettier

I copied the config from @electron/get. I did not, however, add a pre-commit hook.
CI support is coming in a future PR, when we add CFA support.

The lock file's still there. It's just significantly smaller, because tslint is huge.


⚠ Bofrost.at has degraded performance

In f6ed4a5, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 978 ms

Resolved: Bofrost.at performance has improved in 7e695ae.


What Is The Expression Syntax/Language Used In The Rule Expression Editor

Are the operators used in generating the Rule Expression for Best Practice Analyser(BPA),  C#-like or are they based-off some other expression syntax/language? I see rules being written with expressions like Model.Cultures.Count = 0 which I expect to be an assignment but it is being used as a predicate/condition! I expected it to be like Model.Cultures.Count == 0, but the former is being used consistently in all the rules I have seen from the BPA Repo, so far.
My assumption was since Tabular Editor is built using C#, the operators, syntax and semantics were C# complaint? Or is the Rule Expression Editor overriding the C# operators, and how can I get to know the valid operators for predicates/conditions used when creating a BPA Rule?

They are Dynamic LINQ.
More information here.

Thank you @otykier , this is appreciated.


Multiple Firefox profiles not detected or displayed

Describe the bug
I have 2 firefox profiles, but only one is displayed in the Browsers popup.
System:
Fedora Workstation 38
Firefox installed natively (not snap or flatpak)

Hi. Could you also attach a screenshot?

I see. There is no profile name in the Firetox option in Browsers. This means Browsers doean't recognize it as Firefoz but just "some browser".
It identifies Firefox by the .desktop file name right now. Could you find out the name of the .desktop file that Firefox uses in your distro?

[andreas@amnesix ~]$ rpm -ql firefox | grep desktop
/usr/share/applications/firefox.desktop

That is from Fedora 37, but I do share the symptoms.
firefox.txt

Sorry for never getting back to this. The name and content of the desktop file looks correct.
Does the problem still exist?

Hey! The original issue is slightly different - about seeing no profiles.
Do you refer to default-release profile being missing?
If it happens again, please share your profiles.ini

Yes, default-release is missing
When I deleting install.ini and items in profiles.ini, Browsers sees all profiles
But on next Firefox launch everything broke again
Files:
installs.txt
profiles.txt

Which Linux distribution do you use?
How is Firefox package installed? apt/snap/something else?

openSUSE Slowroll (Tumbleweed)
zypper (I think rpm is builds somewhere here: https://build.opensuse.org/package/show/openSUSE:Factory/MozillaFirefox)
$ firefox --full-version
Mozilla Firefox 121.0.1<PHONE_NUMBER>3603<PHONE_NUMBER>3603

Could you try out this experimental build - https://nightly.link/Browsers-software/browsers/workflows/ci/firefox-ignore-lock
(it will be ready once https://github.com/Browsers-software/browsers/actions/runs/7746747952 finishes)

CI failed for linux :)

CI failed for linux :)

Oop, sometimes GH fails with their cache, fixed

Nightly shows only Firefox without profiles
tar.gz browsers-nightly after refresh

If select in profile appears "profile": "firefox#",
When opens with nightly with that config opens firefox main profile
When opens with 0.5.1 with that config opens firefox ProfileManager

tar.gz browsers-0.5.1 same as rpm installed after refresh

If select in profile appears "profile": "firefox#tmp",

Firefox Profiles

Thanks for reporting back!
Could you also attach the logs (logs directory is visible in About dialog and also Settings...->Advanced->Directories? Please also refresh the profiles before.

Nightly shows only Firefox without profiles
This is probably caused by the fact that linux binary assumes resources are relative to the executable at ../resources/...

0.5.2 is now released with the same fix, let me know if all Firefox profiles show up if installing the release version.

Fixed for me, thank you


Question: multi-threads option support?

Do you have plans to support multi-threading options in profiles.yml?

Its already supported. Just enable threads:x
dbt_hive_demo:   outputs:     dev_cia_cdp:       auth_type: ldap       host: hostname       http_path: path       password: pwd       port: 443       schema: dbt_hive_demo       threads: n       type: hive       use_http_transport: true       use_ssl: true       username: name   target: dev_cia_cdp


add k8s health service + example

Using our basic web router it would be great to also provide a k8s health web service given that it is something needed for any rama driven proxy service that runs as a k8s workload.

This is now implemented and working:
use rama::{
    http::{server::HttpServer, service::web::k8s_health},
    rt::Executor,
};

#[tokio::main]
async fn main() {
    let exec = Executor::default();
    let startup_time = std::time::Instant::now();
    HttpServer::auto(exec)
        .listen(
            "<IP_ADDRESS>:8080",
            // by default the k8s health service is always ready and alive,
            // optionally you can define your own conditional closures to define
            // more accurate health checks
            k8s_health()
                .ready(move || {
                    // simulate a serice only ready after 10s for w/e reason
                    let uptime = startup_time.elapsed().as_secs();
                    uptime > 10
                })
                .build(),
        )
        .await
        .unwrap();
}


Decompressor stream hangs

The decompressor hangs on my files, compressed with xz from liblzma 5.1.0alpha (on Ubuntu Trusty). For my files it looks like it pretty consistently happens around > 650MB.
Here is a test file.
My test script (ES6):
'use strict';

import lzma from 'lzma-native';
import fs from 'fs';
import split from 'split';
import stream from 'stream';

let byteCount = 0;

class TestWriter extends stream.Writable {
  constructor() {
    super({objectMode: true});
    this.count = 0;
  }

  _write(obj, encoding, callback) {
    if ((this.count++ % 10000) === 0) {
      console.log(`${this.count} lines, ${byteCount} bytes`);
    }
    callback();
  }
}

let file = fs.createReadStream('test.xz');
let decompressor = lzma.createDecompressor();
let decompress = file.pipe(decompressor);
let lines = decompress.pipe(split(/\r?\n/));
lines.on('data', line => {
  byteCount += line.length;
});

let writer = new TestWriter();
writer.on('finish', () => {
  console.log("Finish");
  process.exit(0);
});
lines.pipe(writer);

Thanks, I’m looking into this!

Sorry to tell you, but I don’t think this is (much of) an issue with this module, but rather with the split module.
In your test file, around the byte mark you named, are some extremely long lines (up to 33 MB). Unfortunately, split has (due to its generic approach) a rather simplistic way of splitting at delimiters: It basically buffers up all data from the input stream until string.split(regex) returns more than one result.
Now, when the decompressor writes the blocks making up the long lines to the split() stream, each time a block of data is appended to split()’s internal buffer and the regex is run over it, resulting in O(n²) complexity and, thereby, in the extremely long delays (Your test script takes about 15 minutes on my machine).
I found at least two solutions for this:

One: Increase the size of the data blocks. This is not really a fix or anything (and may even drive up memory consumption in many cases), but it brought the test script’s timing into the same order of magnitude as unxz < test.xz | wc -l. I’ve just released<EMAIL_ADDRESS>which introduces a bufsize option for streams with a default value of 64 KB. You can test for yourself by using lzma.createDecompressor({bufsize: …}). I’ve found a value of a few megabytes to be sufficient for speeding this particular script up a lot, definitely into the acceptable range.
Two: Since you are only checking for newlines, the char-split module might be just what you want. It splits a stream on a single character (default \n), which allows it to reduce the complexity of searching for the delimiter to O(n). Using import split from 'char-split'; and let lines = decompress.pipe(split());, your test script runs in about 15 seconds, which is very close the native solution of unxz + wc. If it is important to you that you also can accept windows newlines, I’d suggest you just strip a possible trailing \r character manually of each line after splitting.

Thank you for your detailed bug report! If you think that I missed something (which is perfectly possible) or have any further questions, feel free to re-open this issue. :)

Awesome response, thank you! I had no idea my file contained lines of that length.
I appreciate the buffer size addition. But I agree that a simpler splitting stream is the way to go — though I can't get char-split to work. I'm not very familiar with pre-Streams 2.0 streams: When I pipe anything to it, it gets an object (a buffer, possibly?) that's not a string, and emits:
TypeError: Object [... bunch of lines in one chunk ...] has no method 'indexOf'
    at Stream.<anonymous> (./node_modules/char-split/index.js:14:36)
    at Stream.stream.write (./node_modules/char-split/node_modules/through/index.js:26:11)
    at [object Object].ondata (./node_modules/lzma-native/node_modules/readable-stream/lib/_stream_readable.js:583:20)
    at [object Object].emit (events.js:95:17)
    at readableAddChunk (./node_modules/lzma-native/node_modules/readable-stream/lib/_stream_readable.js:201:16)
    at [object Object].Readable.push (./node_modules/lzma-native/node_modules/readable-stream/lib/_stream_readable.js:165:10)
    at [object Object].Transform.push (./node_modules/lzma-native/node_modules/readable-stream/lib/_stream_transform.js:133:32)
    at ./node_modules/lzma-native/index.js:166:16
    at process._tickCallback (node.js:419:13)

My test case:
fs.createReadStream("test.xz", 'binary')
  .pipe(lzma.createDecompressor())
  .pipe(split())
  .pipe(fs.createWriteStream('/dev/null'));

Perhaps you have a better idea of what the cause is?

Hm, the [... bunch of lines in one chunk ...] is kinda the interesting part here; I think it should be something like <Buffer 70 f2 5a 02 00 00 00 00 70 f2 …>… right? Are you using some node version up to 0.12 (node -v)? Buffer objects have .indexOf() only since after 0.12, so that might be the problem. If so, buffer-indexof-polyfill seems to be a solution for this.

It's literally just a fragment of the input, and typeof says object. Maybe it's a buffer. This is Node 0.10.33, sounds like the problem might be that. I'll try the polyfill, thanks!

Okay, that’s something I have never seen then :D Let me know if it works!

Must be a buffer, because the polyfill worked. Thanks again, that saved me a bunch of googling and trial/error.

Great! :)


Update env_stocktrading.py reset

removed * param and options

all functions use this style in gymnasium.
could you pls describe why did you revise it?
pls refer to https://github.com/AI4Finance-Foundation/FinRL/pull/1039/files


[question] does netty support fixed size of heap buffer pool?

so that we can specify the total amount of heap memory a pool can use. Also providing customized strategies used to wait for enough memory.

so that we can specify the total amount of heap memory a pool can us

The heap memory is limited in the typical way for a java application (e.g. -Xms and -Xmx).

Also providing customized strategies used to wait for enough memory.

No. ByteBufAllocator is synchronous (e.g. ByteBuf b = allocator.heapBuffer()) so there is nothing "built in" that you can rely upon to delay the result if there isn't enough memory. This would have to be built on top at a higher level. This is the same semantics as the new operator.


add_extsources does not seems to work (or maybe I do not understand how it should)

Describe the bug
Since my pacman update PR, I wanted to update xmake-repo so that some packages could know that on mingw you can use pacman to install the dependencies. I thus created a local xmake-repo copy and added some add_extsources to some packages.
I wanted to try it, so I downloaded Nazara Engine, added my local copy of xmake-repo to local-repo using xrepo:
xrepo add-repo local-repo /c/Users/<hidden_username>/Documents/Github/xmake-repo/

I added mingw as an available platform in the xmake.lua, then launched the xmake config command:
xmake config --arch=x86_64 --mode=releasedbg -v -D -P

And the result was:
xmake config --arch=x86_64 --mode=releasedbg -v -D -P
checking for platform ... mingw
checking for mingw directory ... C:/tools/msys64/mingw64
checking for unzip ... ok
checking for git ... ok
checking for gzip ... ok
checking for tar ... ok
git rev-parse HEAD
checking for cmake ... no
checking for vswhere.exe ... C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe
checking for Microsoft Visual Studio (x86_64) version ... no
checking for cmake ... ok
finding zlib from xmake ..
checking for xmake::zlib ... no
finding assimp from xmake ..
checking for xmake::assimp ... no
finding catch2 from xmake ..
checking for xmake::catch2 ... no
finding nodeeditor from xmake ..
checking for xmake::nodeeditor ... no
finding chipmunk2d from xmake ..
checking for xmake::chipmunk2d ... no
finding dr_wav from xmake ..
checking for xmake::dr_wav ... no
finding entt from xmake ..
checking for xmake::entt ... no
finding freetype from xmake ..
checking for xmake::freetype ... no
finding libogg from xmake ..
checking for xmake::libogg ... no
finding libflac from xmake ..
checking for xmake::libflac ... no
finding libsdl from xmake ..
checking for xmake::libsdl ... no
finding minimp3 from xmake ..
checking for xmake::minimp3 ... no
finding stb from xmake ..
checking for xmake::stb ... no
finding libvorbis from xmake ..
checking for xmake::libvorbis ... no
finding openal-soft from xmake ..
checking for xmake::openal-soft ... no
finding newtondynamics from xmake ..
checking for xmake::newtondynamics ... no
note: the following packages are unsupported for mingw/x86_64!
  -> assimp 5.0.1
  -> freetype 2.10.4
error: @programdir\core\main.lua:279: stack traceback:
    [C]: in function 'error'
    [@programdir\core\base\os.lua:840]: in function 'raise'
    [...modules\private\action\require\impl\install_packages.lua:563]: in function 'install_packages'
    [@programdir\modules\private\action\require\install.lua:85]: in function 'install_packages'
    [@programdir\actions\config\main.lua:408]:
    [C]: in function 'load'
    [@programdir\core\base\task.lua:519]: in function 'run'
    [@programdir\core\main.lua:277]: in function 'cotask'
    [@programdir\core\base\scheduler.lua:365]:

stack traceback:
        [C]: in function 'error'
        @programdir\core\base\os.lua:829: in function 'raise'
        @programdir\core\main.lua:279: in function 'cotask'
        @programdir\core\base\scheduler.lua:365: in function <@programdir\core\base\scheduler.lua:362>

Expected behavior
I would have expected, since I added add_extsources("pacman::assimp") in the assimp package, that the command would not fail and would just ask me if I wanted to install assimp from pacman. But maybe there is something more I need to do ?
Related Environment
Please provide compiling and running environment information:

xmake version: 2.5.6 dev (xmake update dev)
os: windows
target platform: mingw with msys2

I have improved it on dev.

Seems to work as expected now, thanks.


Add ref to make archiving easier to understand

minor typo fix

@silverhook Thanks for your contribution but your are missing the Signoff in your commit message. Please check https://scancodeio.readthedocs.io/en/latest/contributing.html#code-contributions in order to fix this so we can merge your PR ;)

@pombredanne said I could simply use the web ui for it.
If it’s possible to add DCO through the web ui, happy to do that. If I need to re-create the PR locally and push again, happy to do that too. Please advise :)

@silverhook you can do it either locally and force push, or you can add your signoff in a comment here and we can handle it from there.

Included in https://github.com/nexB/scancode.io/commit/1ba99cb625364e695393023e17cc563d392f629a


Upgrade Users To Native Bracket Pair Colorization

Now that VS Code (Insiders) supports native bracket pair colorization inspired by your extension, it would be awesome if both your extensions could prompt users to upgrade to the native experience.
However, we would like to get more feedback of our native implementation before users are prompted to upgrade (and have a look at https://github.com/microsoft/vscode/issues/131001). Ideally, users are asked to upgrade early October.
If you are fine with that, I'll open PRs for each of your two extensions in the next weeks that implement this notification.
I suggest that users are prompted the first time your extensions load and then a month later again if they did not upgrade.
When they discarded both notifications, they are not bothered again.
What do you think?
Btw. thank you so much for your contribution towards VS Code and collaborating with us on making bracket pair colorization as fast as possible!

Good with me

@hediet I just tried out the native experience and was a bit disappointed that it doesn't come with the connector line which I find very useful and to be a very important part of this extension. This makes me not quite ready to do make the switch yet.

I agree with @silkfire. The connector line is really useful!

Vote in the VS code issue.


Print average coverage percentage in console output

I'm working on a project separated into modules. Each module has its own unit tests. Currently, the output in console looks like this:

I am curious if it's possible to print out the average coverage percentage for all included targets. So later I can pick this value in a job log on my CI.

I wish this average result would also show up in the slack report.