Added show-hide public methods

I have added show, hide, collapse, expand and isExpanded public methods.
Those methods gives you a better control of the component and could be useful when you want to show or hide fab button on list scroll.

Why delete the sample project?

Sorry I just wanted to merge the first commit of my fork. I deleted it
after make the PR :S
I will open a PR with this commit later.
Hope you find it useful. If you find interesting the coordinator behaviour
class tell me and I will include it in the Pull request.
Greetings and congratulations for your job!
El 4/11/2017 18:17, "André Servidoni"<EMAIL_ADDRESS>escribió:

Why delete the sample project?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DeKoServidoni/OMFM/pull/3#issuecomment-341914000, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ARjhLw0KTwH1-DkezTUkh-xdIoPIXbiRks5szJwhgaJpZM4QR9Xi
.

Hahaha don't worry :)
I liked a lot the coordinator behavior!
Thanks :)


the insertion actions insert redundant imports which break the code parse

steps to reproduce:

open this project https://utopia.pizza/project/d059cb25/
select the CardRoot element in the navigator
press W to Wrap
select FlexRow
observe a new import for FlexRow be added
try to save in the code editor or change the code
parse error on the canvas-error-overlay

the relevant action is WRAP_IN_VIEW https://github.com/concrete-utopia/utopia/blob/d6d2d8b4a2ba29c4dc579557b1a1fff528d6b766/editor/src/components/editor/actions/actions.ts#L2068

INSERT_WITH_DEFAULTS is also affected, I suspect they use a common function that contains the bug


Better webgl support

Fixes #issue
PR checklist:

[x] make succeeds
[ ] make reftests succeeds
[ ] tested examples with the following backends:
[ ] rustfmt run on changed code

I assume the winit git dependency is temporary?
bors r+

bors retry

@kvark yes, winit git depenency is temporary. Probably until next release.

some sort of a network outage on CI :(

Bors retry

On Aug 13, 2019, at 15:18, Zakarum<EMAIL_ADDRESS>wrote:
@kvark yes, winit git depenency is temporary. Probably until next release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Looks like the CI failure is legitimate and caused by the winit branch:
error[E0432]: unresolved import `web_sys`

  --> C:\Users\travis\.cargo\git\checkouts\winit-c2fdb27092aba5a7\dbdde3d\src\platform\web.rs:10:5

   |

10 | use web_sys::HtmlCanvasElement;

   |     ^^^^^^^ use of undeclared type or module `web_sys`

cc @omni-viral

Oh, right, my winit fix wasn't merged yet.

@omni-viral looks like the winit branch has been merged, but this branch needs to be rebased

Please rebase

@omni-viral can we revive this?

@kvark working on it
It seems that winit web support will take another month or so, IDK.
So I will stick to custom codepath as it is right now in master.
Expect update on weekend.


Simple access to the (top level) cell count

The computational cost that is associated with using a FEM mesh primarily depends on the number of elements (e.g. triangles in a 2D mesh). Thus during meshing it is useful to print the number of elements, to allow balancing the mesh resolution vs the computational cost. For that reason it would be useful to easily get the number of elements of a mesh.
Alternatively, it could be useful to be able to print some additional mesh statistics. For example print the number of elements per region.

print(mesh) will print the number of elements.
Is there anything else you would like to see?

Oops, completely overlooked your reply. print(mesh) looks like it contains all the information that I need.


ingest after bbknn produces poor results

Hi,
I tried ingest using the reference made with BBKNN. As @ivirshup said, ingest was worked by adding adata_ref.uns['neighbors']['params']['metric'] = 'euclidean'. However, the result was quite poor.

In contrast, if I merge all datasets (eg references and query), it worked well, but when we want to take over the reference embedding, I actually want to use ingest rather than run bbknn again. Is there any option to feed in this case? or should I ask this in the BBKNN repo?

This is the notebook can reproduce the problem.
https://nbviewer.jupyter.org/github/yyoshiaki/ingest_after_bbknn/blob/main/notebook.ipynb
https://github.com/yyoshiaki/ingest_after_bbknn/blob/main/notebook.ipynb
Originally posted by @yyoshiaki in https://github.com/theislab/scanpy/issues/1122#issuecomment-838476193

I'm not completely sure it makes sense to me to run ingest while trying to use the bbknn neighbor graph. @Koncopd, do you have any thoughts here?

I am also not sure. You run bbknn for the reference, but then the standard knn for the query. I don't think it makes much sense.

Thank you. For example, I'm considering a situation that first I create a reference dataset using bbknn, then map bulk RNAseq data onto the reference.  I'm happy if I classify the bulk RNA dataset without rearranging the reference embedding. Is it possible to achieve this with good quality?

Some questions that you may want to consider: Does the bulk RNA-seq dataset actually contain "pure" cell types? Is it possible a deconvolution approach would make more sense? If you're looking for classification, is projection into the umap embedding important?
As a side note: sc.datasets.pbmc3k and sc.datasets.pbmc3k_processed are the same dataset.

Yes, I'm assuming pure cells with previously known as a cell type. As you suggest, deconvolution is a nice idea. I didn't hit upon the idea to deconvolve pure cells to examine whether the cell pool is truly pure and which cells on a single cell experiment are the source of the pure cell pool. I thought it is straightforward to project bulk cells on the umap. I also tried the same workflow to ingest public data on our dataset consisted of several experiments with bbknn batch correction, but similarly, the ingestion is not good as the notebook above.  In these cases, I'm believing these are important for the visualization and the acquisition of the known cell labels. Is it possible to attain these by `ingest?
I'm sorry that the example may make the question ambiguous. And I apologize that I confused the dataset, too.


Update batcher to new autosign system

This task has a few sub-tasks

Bring the batcher codebase into the paima-engine repo
Update the Paima standalone building and documentation to properly handle the bacher's new location in this repo
Reduce code re-use by having the batcher import Paima's logic instead of having a lot of code duplicated like we have now
Update the batcher system so support the new auto-sign mechanism

Notes from Martin
As far as I can tell, the code duplicated in the batcher and in paima-engine comes down to two categories:

Signature verification code: paima-engine/paima-funnel/src/verification/[chain-name].ts  vs. paima-batcher/address-validator/src/[chain-name].ts

Note that buildTransaction in algorand.ts in the batcher is already present in paima-utils as buildAlgorandTransaction, because the backend and middleware both use it;
Batcher has some extra functions for address validation (which aren't even very useful TBH), besides that, the code is mostly identical (but note that paima-engine's polkadot code has an extra call to cryptoWaitReady);
I would simply move all the funnel helper functions + the extra batcher address validation functions to paima-utils-backend (or paima-utils) and then import it from there in both funnel and batcher.

Various helper functions and constants: paima-engine/paima-utils vs paima-batcher/utils:

In constants.ts, both AddressType and outer / inner divider must be the same between PE and Batcher (but note that they use different identifiers for the dividers)
Some functions are used in both batcher and paima-engine, including:

wait, hexStringToBytes, hexStringToUint8Array,
getWeb3 in batcher is the same as initWeb3 in paima-engine (renamed because of middleware state)
getStorageContract in batcher is basically the same as getPaimaL2Contract

The batcher also has its own copy of the PaimaL2Contract artifact (still called Storage there), which can be replaced by artifacts in paima-utils (although note that batcher doesn't have all of the same setup, e.g. typechain)

The refactoring task (minus testing) will probably simply come down to:

add paima-sdk as a filesystem dependency to the batcher repo (using the entire paima-engine repo simply renamed or linked should work);
move the funnel verification functions to paima-utils-backend;
add address validation functions from the batcher there
rework the batcher to import all that it can from paima-utils and paima-utils-backend (i.e. what is listed above, though I might have missed some other tiny things)

Closed when we merged the batcher into the codebase


Prevent deleting linked service

Currently when deleting service that is linked to another service, another service will have broken service link. To avoid this situtation this PR prevents deletion and returns error instead.

LGTM!


Closing because this was addressed in #13


feat: style definition applicable to all views

Add a feature to define a style applicable to all views. It is useful to define in a unified way how e.g. elements tagged as #deprecated are styled in all the diagrams.
Please note, I'm an embedded developer and I was learning about TypeScript on the go. I'm happy to fix any issues in my code and broaden my higher-level language horizons :)
This is intended to fix https://github.com/likec4/likec4/discussions/961

Hey @hubertmis, great job 👏🏻👏🏻 ! And quite elegant considering this:

Though I'm skeptical about making these global. Let me explain.
My first thought when looking at this syntax was that these rules are scoped to the current views block and are only applied to nested views.
While I wouldn't say this breaks the Open/Closed principle, imagine a scenario where someone in your organization creates another .c4 file with global styles that satisfy their needs but interfere with others.
I like the idea, but I would keep it scoped to the current views.
I think the implementation would be simpler this way. Instead of introducing c4GlobalRules, we could just prepend these "global" rules to each parsed view directly in the model parser.
No need to change compute views (by the way, you missed dynamic views).
What do you think?
I'd also suggest adding:

Parser smoke tests, see examples views-2.spec.ts
Tests in model-builder.spec.ts to ensure the styles are applied correctly

I like the idea, but I would keep it scoped to the current views.

Sounds good. It still meets my needs. I'll try to change the solution thr way you suggest.

by the way, you missed dynamic views)

I did this on purpose to limit the scope of the changes for now.

I'd also suggest adding:

I had a feeling the tests are missing, but I didn't have a clue where to look for them. Not to mention how to run them. Thanks for the hint!

I had a feeling the tests are missing, but I didn't have a clue where to look for them. Not to mention how to run them. Thanks for the hint!

First ensure yarn build in root or default build task in VSCode.
And start yarn vitest:ui in root (run all tests) or inside packages/language-server.
You can keep it running - it reruns tests on file changes.
Changes in *.langium require code generation. This is done by either:

Default build task in VSCode
yarn generate in packages/language-server

Or better keep running yarn watch:langium in folder packages/language-server.
To debug tests - vitest extension or check their docs

My first thought when looking at this syntax was that these rules are scoped to the current views block and are only applied to nested views.

After looking more into this solution, I don't think we can properly apply these "global rules" to the nested views without significant modifications to the syntax.
If I understand correctly, the parser iterates through the .likec4 files in the workspace folder in any order and the views are applied to doc.c4Views on the fly without any control over the hierarchy. So, if I created
views {
  style element.tag = #deprecated {
    color red
  }
}

in my index.likec4 containing the specification, I would expect this style to be applied to all the views being children of this file in my model hierarchy. But I don't see a way to express this hierarchy now.
If my understanding is correct, and I changed this feature as you suggested, I would need to copy
  style element.tag = #deprecated {
    color red
  }

part all over my files in each views {} block. I would prefer to avoid it.
If you see the proposed syntax confusing, what do you think about applying the global view rules in the specification {} block instead?

In other words, I need a syntax that would allow me to define tag styles in one file that would be applicable to all views defined in all files. I'm open to suggestions on how to sketch this syntax to be aligned with the vision of likec4.
I was considering the following options:
1:
specification {
  ...
}

views {
  style element.tag = ... {
    ...
  }
}

2:
specification {
  style element.tag = ... {
    ...
  }
}

3:
specification {
  ...
}

styles {
  style element.tag = ... {
    ...
  }
}

@davydkov, what's your suggestion?

Hi, @hubertmis !
Good job! It's gone be very helpful feature.
In my opinion the second option is most suitable to express "global style" concept.

But I don't see a way to express this hierarchy now.
Probably this could be implemented with 'extend view' feature: create an "abstract" base view with base styles and extend it in child views.

In my opinion the second option is most suitable to express "global style" concept.

Should I then modify the PR to define global styles like this?
specification {
  style element.tag = ... {
    ...
  }
}

Is this agreed? Or should we discuss the options before I proceed?
I'm not sure how this repository is governed :)

Probably this could be implemented with 'extend view' feature: create an "abstract" base view with base styles and extend it in child views.

I don't think that the extended views are enough to express the view hierarchy throughout the files. I see a challenge like this:
landscape.likec4:
specification {
  ...
}

model {
  environment system { ... }
}

views {
  // This is top-level views
  view of system {
    include *
  }
}

system.likec4:
model {
  extend system {
    component component1 {
    }
  }
}

views {
  // These are nested views
  // But the nesting can be only indirectly deducted based on the model
  view of component1 {
    ...
  }
}

I think that finding views hierarchy implicitly, based on the models hierarchy, and applying styles or other rules based on this implicit hierarchy would be a confusing syntax.
Alternatively, we could explicitly define the hierarchy by something like:
views {
  view of component1 {
    inherits_rules_from view.title = "system view"
  }
}

But then again the syntax gets complicated and I'm not sure if that gives real value.
I think most cases (at least all issues I need to solve) can be addressed by the global styles. I would stick to this feature, at least in this PR.

@hubertmis ,

Should I then modify the PR to define global styles like this?
Is this agreed? Or should we discuss the options before I proceed?
The final decision is on @davydkov. I'm here just as a future user of this feature :)

I don't think that the extended views are enough to express the view hierarchy throughout the files.
I see. I meant explicit hierarchy of views (https://likec4.dev/dsl/views/#extend-views). It should work for non-scoped view, but in your example child view are scoped to component. It's not possible to extend non-scoped base view in scoped child view. Thus, it's not an option.

@hubertmis @pavelpykhtin

I vote for option 1
specification {
  ...
}

views {
  style element.tag = ... {
    ...
  }
}

However, I insist on making these styles "local" (I think "local" describes it better than "scoped").
Consider this:
// Green views
views {
  style * {
    color green
  }

  view view1 {
  }
}

// Red views
views {
  style * {
    color red
  }

  view view2 {
  }
}

Pros:

reduces boilerplate by sharing the same styles
deterministic order and simple implementation
looks very clear; almost no cognitive load in understanding

Cons:

sharing is limited to the views block, not reusable.

I would say pros 2 and 3 are a good trade-off, and we still achieve some result, don't we?
I suggest starting with this, and keeping all same-styled views in the same views block.

Here is a possible implementation
In Langium:
https://github.com/likec4/likec4/blob/3201a2bf6b89e603ff000bd8b0c72f0d3e85ffd5/packages/language-server/src/like-c4.langium#L196-L199
I'm suggesting changing it to:
ModelViews:
  name='views' '{'
    (
      // Local styles
      styles+=ViewRuleStyle |
      views+=LikeC4ViewRule
    )*
  '}';

We separate views and local styles at the AST level.
In the model parser:
https://github.com/likec4/likec4/blob/3201a2bf6b89e603ff000bd8b0c72f0d3e85ffd5/packages/language-server/src/model/model-parser.ts#L285-L299
First of all, we do not use flatMap on line 286 but rather iterate over each views block separately.
In each iteration, we first parse the styles.
When we parse a view, we prepend local styles to its rules.
We don't even need to store these local styles somewhere; we prepend them during the parsing phase.

But I agree, the ultimate goal is sharing across the views block.
And, as it seems to me, a good and, again, deterministic solution is option 3.
global styles {

  style1
    // reuse filter predicate
    where tag is #deprecated and ... {
      color red
    }
}

views {
  view {
    // Syntax Option 1, we need something to indicate "global":
    // like __.style1, ::style1, &style1
    include __.style1

    // Syntax Option 2
    style.global style1

    // Suggest yours
  }
}

Now, an interesting implication:
views {

  // Apply global style to all views in a block
  style.global style1

  view {
  }
}

I'm also considering the concept of "namespacing" (or something like domains in IcePanel).
As you can see below, local styles also fit perfectly:
// By defining a path, we create a navigation tree and breadcrumbs
views "DataLake / Marketing / Ingestion" {

  // By default, all non-marketing elements are gray
  style element.tag != #marketing {
    color muted
  }

  // Marketing and ingestion elements are green
  style
    element.tag == #marketing,
    element.tag == #ingest {
      color green
    }

  dynamic view IngestPosthogToLake  {
    ...
  }

}

@davydkov , thanks for the suggestions.
I would like to clarify one point:

But I agree, the ultimate goal is sharing across the views block. And, as it seems to me, a good and, again, deterministic solution is suggested option 3.
global styles {

  style1
    // reuse filter predicate
    where tag is #deprecated and ... {
      color red
    }
}

views {
  view {
    // Syntax Option 1, we need something to indicate "global"
    // like __.style1, ::style1, &style1
    include __.style1

    // Syntax Option 2
    style.global style1

    // Suggest yours
  }
}

Assuming I create a few global styles that I would like to apply to all my views the code would look like:
global styles {

  style1
    // reuse filter predicate
    where tag is #deprecated and ... {
      color red
    }

  style2 where tag is #unstable { ... }
  style3 where tag is #thirdparty { ... }
  style4 where tag is #contractor { ... }
}

views {
  view {
    style.global style1
    style.global style2
    style.global style3
    style.global style4
  }
}

So I need to copy this style.global ... sequence through all my view {} nodes, or at least through all my views {} nodes (if local views {} styles get implemented). If a created style5, I would need to copy it across all files and nodes. This is a maintenance overhead I would like to avoid (one of the reasons I didn't decide to move to likec4 from structurizr yet :) ).
I would prefer to define a solution that applies a defined style to all matching elements, similar to the already existing specification element styles:
specification {
  element x {
    style {
    }
  }
}

I was considering making something similar. Another option would be:
specification {
  tag x {
    style {
    }
  }
}

Or even better, option 2 I suggested in the previous message because it could replace the specification element style, apply to the specification tag style, and potentially more like wildcards:
specification {
  element x
  tag y

  style element.kind = x { ... }
  style element.tag = #y { ... }
  style element.tag != #y { ... }
  style * { ... }
}

Pros:

Applicable to all views in the workspace - little maintenance when updating and creating global styles
Simple implementation (I already created a PoC on a branch)
Clear, simple syntax, similar to already existing
Can't be misused by adding global styling in sub-files, considering only one file can include specification {}.

Cons:

Missing granular control on applying only selected styles in views {} or view {} nodes

I believe the value of the granular styling control is not worth more complex syntax.
Moreover, the approach I sketched could be extended to solve another issue I described in #962 :
specification {
  exclude * where tag is #project1 and tag is not #project2
}

It allows an architect to define one specification file per project and share model files (including correctly tagged elements) between multiple projects.

And another attempt: keeping option 2, but applying rules in the model parser. The specification type, model builder, and compute remain unchanged: https://github.com/likec4/likec4/commit/bad7ba4c7520e8072480cdc3c4423395f14de55d

I started experimenting with global predicates to meet #962 requirements.
After writing a few tests, I like @davydkov 's proposal better, but I would suggest some enhancements to the syntax:
global {
  styles {
    // global styles are grouped in sets
    set style_set_1 {
      style where tag is ... {
        ...
      }
      style where tag is ... {
        ...
      }
    }

    style style_2 where tag is ... { // implicitly create a set 'style_2' containing 1 style
      ...
    }
  }

  predicates {
    set project1 {
      exclude * where tag is #project2 and tag is not #project1
    }
    predicate project2 exclude * where tag is #project1 and tag is not #project2
}

views {
  apply style style_set_1

  view {
    global style style_2
    include *
    global predicate project1
}

This seems to meet all @davydkov 's requirements, and introducing sets of rules meets my requirements of minimal maintenance when I modify the global styles. I expect to have a single set of styles in my diagrams that I apply to all views. I would also apply a few sets of predicates to most of my views (each view includes one of the global predicates' sets).
What do you think about this proposal?

@hubertmis Do we close this one?

Replaced with #1058


supabase.auth.getUser(token) receives "Bad Request" from supabase api

Bug report

[ x] I confirm this is a bug with Supabase, not with my own application.
[ x] I confirm I have searched the Docs, GitHub [Discussions]

Description
Running locally, I'm following https://supabase.com/docs/guides/functions/auth and the github example https://github.dev/supabase/supabase/blob/master/examples/edge-functions/supabase/functions/select-from-table-with-auth-rls/index.ts
When doing const response = await supabase.auth.getUser(token) there is a response.error:
AuthUnknownError: Unexpected token 'B', "Bad request
" is not valid JSON
    at handleError (fetch.js:34:15)
    ...

It looks like the supabase client is sending the request to the api server and getting the response "Bad request", and then excepting when attempting to parse it as JSON.
My main concern is why is it getting "Bad request"?  / this is blocking me. It must be something about my setup but I haven't been able to find it.
But it's also worth noticing potential bugs with the supabase client and/or server:

Is the supabase client not checking for 200 before attempting to parse?
Was "Bad request" sent with 500 or 200 from the api server?

To Reproduce

supabase start
supabase functions serve --inspect-mode brk (optionally)
Make request from browser with a supabase client.
Function end point looks like:

import { corsHeaders } from '../_shared/cors.ts'
import { createClient } from 'jsr:@supabase/supabase-js@2';

const supabaseUrl = Deno.env.get('SUPABASE_URL'); // this is 'http://kong:8000'
const supabaseAnonKey = Deno.env.get('SUPABASE_ANON_KEY'); // this is set correctly

Deno.serve(async (req) => {
  console.log('corsHeaders: ', corsHeaders)
  if (req.method === 'OPTIONS') {
    return new Response('ok', { headers: corsHeaders })
  }

  const authorization = req.headers.get('Authorization');
  if (!authorization) {
    return new Response(
      JSON.stringify({ error: `No authorization header passed` }),
      {
        status: 500,
        headers: { 'Content-Type': 'application/json' },
      }
    );
  }

  const supabase = createClient(supabaseUrl, supabaseAnonKey, {
    global: {headers: {authorization}}
  });

  const token = authorization.replace('Bearer ', '');

  const response = await supabase.auth.getUser(token);
  console.log('response.error: ', response.error);

...

response.error:
AuthUnknownError: Unexpected token 'B', "Bad request
" is not valid JSON
    at handleError (fetch.js:34:15)
    ...

Expected behavior
Should retrieve the user without error
System information

OS: macOS Sonoma 14.6
Version of supabase-js: ^2.43.2
Version of Node.js: v21.7.1
Version of CLI:supabase -v 1.200.3
Version of Docker:docker -v Docker version 27.1.1, build 6312585
Versions of services: [output from supabase services command]

        SERVICE IMAGE      │      LOCAL       │   LINKED
  ─────────────────────────┼──────────────────┼─────────────
    supabase/postgres      │ <IP_ADDRESS>       │ <IP_ADDRESS>
    supabase/gotrue        │ v2.162.1         │ v2.162.1
    postgrest/postgrest    │ v12.2.3          │ v12.2.3
    supabase/realtime      │ v2.30.34         │ -
    supabase/storage-api   │ v1.11.7          │ v1.11.7
    supabase/edge-runtime  │ v1.58.3          │ -
    supabase/studio        │ 20240729-ce42139 │ -
    supabase/postgres-meta │ v0.83.2          │ -
    supabase/logflare      │ 1.4.0            │ -
    supabase/supavisor     │ 1.1.56           │ -

This was due to passing the header wrong
  const supabase = createClient(supabaseUrl, supabaseAnonKey, {
    global: {headers: {authorization_header}}
  });
 // Should be:
  const supabase = createClient(supabaseUrl, supabaseAnonKey, {
    global: {headers: {Authorization: authorization_header}}
  });


Input lield on mobile

The URL input field gets covered on mobile by soft keyboard, also doesn't have a default button assigned.

Default button is fixed, but still gets covered by soft keyboard


Reading Time Estimator

Implement reading-duration from https://www.npmjs.com/package/reading-duration to give blog post reading time estimations.
Changes:

new read_estimate.js
add Readtime function into posts

PR CHECKLIST

[x] My code follows the style guidelines of this project (variable naming, commenting, copyright, etc.)
[x] I have performed a self-review of my code
[x] Changes are clearly highlighted and easy to understand
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have meaningful commit messages that explain what was changed/committed
[x] I have built and locally tested my changes
[x] My changes generate no new errors or regressions (pending verification)
[x] I have made corresponding changes to the documentation OR this is N/A
[x] Documentation accurately reflects the current state of the project OR this is N/A
[x] I have added tests that prove my fix is effective or that my feature works OR this is N/A
[x] New and existing unit tests pass locally with my changes OR this is N/A
[x] Any dependent changes have been merged and published in downstream modules OR this is N/A
[x] All links are working and correct OR this is N/A
[x] Spelling and grammar are correct
[x] I have added the "READY FOR REVIEWS" tag when this PR is ready for reviews

Tested PR branch build on local system. No regressions detected. UI and Readingtime function working as intended.
Project should be updated to nextra version 3.0+ -- will create new topic branch so this can be completed later.


Render issues

I have tried fabric and forge, and both versions of the mod are rendering the portal red in the nether and blue in the overworld. Is there something I'm doing wrong? Could it be because I'm using a third party launcher?

Maybe your videocard does not support some GL features. Try using command /immersive_portals_debug front_clipping_disable

Maybe your videocard does not support some GL features. Try using command /immersive_portals_debug front_clipping_disable

This didn't seem to help. Is there anything else I can do?

Probably nothing. The critical GL feature is not supported there and the portal cannot be rendered.

Probably nothing. The critical GL feature is not supported there and the portal cannot be rendered.

If I use a launcher that uses a different renderer could that help? One such as zinc or osmesa?

I don't know


Review GitHub issues needing creation during pre-release process

What
Review the issues we create ahead of a pre-release to ensure they match what we need for that process
Why
So we can line-up actions to actually do the pre-release, as the actions we need to take to prepare may slightly differ from an actual release.
Who needs to work on this
Developers, Tech writers
Who needs to review this
Developers, Tech writers
Done when

[ ] Issues to be created have been reviewed
[ ] Relevant issue to prepare for the pre-release have been created and tracked by #3640

We've done a few pre-releases now and merged documentation for steps to follow: https://github.com/alphagov/govuk-frontend/pull/3977


Get Java client integrated into build process

[x] Integrate into build.cmd with automatic skipping when Java is not present (#2678)

I think we should try to fail the build if Java is not present when on the CI though to avoid accidentally forgetting to build it because we spun up a new agent and didn't install Java.
Stretch goal: Acquire Java as part of the build (only on CI)

[x] Make sure VSTS and Jenkins agents have the necessary JDK installed
[x] Make sure TeamCity (if we're still using it by then ;)) has the necessary JDK installed.
[x] Integrate JAR signing into the build
[ ] Publish packages to a MyGet Maven feed as part of the build on the CI
[ ] Integrate GPG signing into build
[ ] Consider publishing packages to Maven Central Staging feed as part of build.

The remaining work for this is P3 for 2.2. We should do it for 3.0, but it doesn't need to hold up 2.2

Assigning to me to document the manual shipping procedures for 2.2. Will bump priority down and move the rest to 3.0 after that.

Documented. Automation will have to wait until I have some cycles, which won't be in 2.2


VLI image contains grub2 for aarch64

The VLI image should not contain the grub2-arm64-efi package. VLI images are for x86-64 only and based on the SLE For SAP product which is not available for aarch64

Well, it's not actually in the images, but it is in the image descriptions. It gets included from data/csp/sle15/profile_defaults.yaml. It includes this in basically everything, and ends up as a kind of a no-op in x86_64 only builds.
Excluding this from all SAP and SUMa builds is actually more fiddly than one might think. The grub package is included in the CSP specific profiles, and the product modules is in common profile, so the product module can't overwrite it. It could be easily removed from Azure LI/VLI though.

Yes, it's not in the image, that is correct. Lets' start with removing it from the LI/VLI images and try and figure a more elegant way to handle architecture. Maybe the arch needs to bubble up to the command line rather than being implicit to the image build.

This is handled via the architecture parameter for keg, which filters out packages for architectures that are not enabled.


Rename info & testnet.sh to edge-info and edge-testnet

Rename the tools to have some common theme with the names and most importantly - avoid overlap with names - there is already an info tool in the Linux world, so we cannot re-use that name.
Todos

[x] Changelog updated
[x] Run shellcheck or pysh-check before committing code - no more warnings than earlier (preferrably less)
[x] Will tag a proper release, if need be.
[ ] Will update required recipes/builds as well.

Fixed the filenames now.


Swagger Tanstack Query Example not working

What is the type of issue?
Example code is not working
What is the issue?
The example config on the bottom of page https://kubb.dev/plugins/swagger-tanstack-query/ is not working.
Getting: Error This plugin has a pre set that is not valid(["plugin-oas", "plugin-ts", "plugin-zod"]) [...]
Also some of the plugins used in the example are missing from the installation example in the top of the page.
Steps to reproduce:
pnpm create vite@latest [react + SWC Typescript]
cd [chosen-projectname]
pnpm install
pnpm add @tanstack/react-query
pnpm add @kubb/cli @kubb/core
pnpm add @kubb/swagger-tanstack-query @kubb/swagger-ts @kubb/swagger @kubb/swagger-client
pnpm add @kubb/plugin-oas // missing from above
// add script to package.json e.g. "codegen": "kubb --config ./kubb.config.ts"
// pnpm run codegen

Where did you find it?
https://kubb.dev/plugins/swagger-tanstack-query/

@kubb/swagger is deprecated in favour of @kubb/plugin-oas. So normally if you install that one it will work(I will update the docs).
If you are still using @kubb/swagger then your kubb.config.ts file will look like this:
import { defineConfig } from '@kubb/core'
import { definePlugin } from '@kubb/swagger'
import { pluginTs } from '@kubb/swagger-ts'

export default defineConfig(async () => {
  return {
    root: '.',
    input: {
      path: './petStore.yaml',
    },
    output: {
      path: './src/gen',
      clean: true,
    },
    plugins: [
      definePlugin(),
      pluginTs(),
    ],
  }
})

Thank you. I am in the project startup process, so I am basically looking for something to create ts types/schemas and especially react-query hooks. The error I got though seemed to be linked to the swagger-tanstack-query plugin. Tried a clean project with setup as described above (pnpm create vite@latest etc.) and a config like this:
import { defineConfig } from '@kubb/core'
import { pluginOas } from '@kubb/plugin-oas'
import { pluginTanstackQuery } from '@kubb/swagger-tanstack-query'

export default defineConfig({
  input: {
    path: "https://petstore3.swagger.io/api/v3/openapi.json",//'./swagger.json',
  },
  output: {
    path: './src/gen',
  },
  plugins: [
    pluginOas(),
    pluginTanstackQuery({
      output: {
        path: './hooks',
      },
    }),
  ],
})

Commenting out the pluginTanstackQuery will make it work though.
attached my package.json:
package.json
I will be happy to help out with docs if you need it, but need to get to know the framework to do that of course :)

@kubb/swagger-tanstack-query needs @kubb/swagger-ts, can you try with adding the following:
I also did an update for the docs so normally it should now be correct.
import { defineConfig } from '@kubb/core'
import { pluginOas } from '@kubb/plugin-oas'
import { pluginTanstackQuery } from '@kubb/swagger-tanstack-query'
import { pluginTs } from '@kubb/swagger-ts'

export default defineConfig({
  input: {
    path: "https://petstore3.swagger.io/api/v3/openapi.json",//'./swagger.json',
  },
  output: {
    path: './src/gen',
  },
  plugins: [
    pluginOas(),
    pluginTs(),
    pluginTanstackQuery({
      output: {
        path: './hooks',
      },
    }),
  ],
})

That did the job! Thank you!


State of Machine in Cluster Management page is seen as Active when the node is in Provisioning state

Addresses Github issue: #5443
Addresses Zube issue: #5469

Fix pending and ready counts for MgmtNodePool model

@richard-cox I spent quite some time looking into the code and for the MachineSummaryGraph component we need not only the count of each occurence of a state but also the pending and ready counts for each element.
We chatted about changing the stateParts in the models, but not only they are present in multiple components/formatters they won't fix the "view" of provisioning nodes in the cluster management list.
With that in mind, imo, I don't think it's worth changing a ton of stuff and risk "breaking" the view of multiple components.
I only fixed the "countS" for the RKE1's


[wip] added extra documentation for skip_waiting_for_build_processing

Added guidance for users using a billed CI service.
See issue for more details:
https://github.com/fastlane/fastlane/issues/13953#issuecomment-461831673
@janpio

@janpio thanks for your feedback, I've made 2 changes. 👍


Do not use inline yml for the parameters.yml

Expand the yaml to be mor euser friendly

So this addresses symfony/symfony#14015?

Exactly, I stumbled upon it yesterday and thought to fix it. However, I see there are discussions going on to remove the config completely, so I did not bother fixing the (other people's) coding standards issues ;-)

Merging it in the 3.0 branch.

Thank you @Xosofox.


Handling NULLs in databases

It seems that Metanome cannot handle NULLs in databases so far. Here is an example stacktrace:
Exception in thread "main" java.lang.NullPointerException: at index 8
        at com.google.common.collect.ObjectArrays.checkElementNotNull(ObjectArrays.java:240)
        at com.google.common.collect.ObjectArrays.checkElementsNotNull(ObjectArrays.java:231)
        at com.google.common.collect.ObjectArrays.checkElementsNotNull(ObjectArrays.java:226)
        at com.google.common.collect.ImmutableList.copyOf(ImmutableList.java:295)
        at de.metanome.backend.input.database.ResultSetIterator.next(ResultSetIterator.java:94)
        at de.metanome.backend.input.database.ResultSetIterator.next(ResultSetIterator.java:28)
        at de.hpi.metanome.algorithms.hyucc.structures.PLIBuilder.calculateClusterMaps(PLIBuilder.java:49)
        at de.hpi.metanome.algorithms.hyucc.structures.PLIBuilder.getPLIs(PLIBuilder.java:38)
        at de.hpi.metanome.algorithms.hyucc.HyUCC.executeHyUCC(HyUCC.java:188)
        at de.hpi.metanome.algorithms.hyucc.HyUCC.execute(HyUCC.java:170)
        at de.hpi.metanome.flixrunner.mocks.MetanomeMock.executeHyUCC(MetanomeMock.java:153)
        at de.hpi.metanome.flixrunner.mocks.MetanomeMock.execute(MetanomeMock.java:56)
        at de.hpi.metanome.flixrunner.MetanomeTestRunner.run(MetanomeTestRunner.java:42)
        at de.hpi.metanome.flixrunner.Main.main(Main.java:8)

It seems that the culprit is ImmutableList.copyOf(...), which enforces all elements to not be null. In this case, it is used to wrap a tuple fetched from the database. Here, NULLs in the tuple will be represented by null values and, hence, the ImmutableList.copyOf(...) fails.
To solve this issue, it might be considered to change the signature of the method
public ImmutableList<String> next() throws InputIterationException

in ResultSetIterator to
public List<String> next() throws InputIterationException

so as to use a different List implementation that allows for nulls..
The other solution would be to represent NULL values with empty Strings, then we lose a bit of semantic.

Nevermind, it just seems that the currently deployed snapshot version is subject to this issue. But it seems that this bug has been fixed in 4086abf.


don't hardcore GITEA_USER and GITEA_PASSWORD

use the global variables

Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

will merge since it's trivial and need it to deploy infra


Object placement scene

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to Test
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist
Please delete options that are not relevant.

[ ] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build 5712

2 of 67 (2.99%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 27.247%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/features/storySimulator/objects/SSObjectManagerHelper.ts
0
1
0.0%

src/features/storySimulator/scenes/StorySimulatorMenu.ts
0
1
0.0%

src/pages/academy/storySimulator/subcomponents/storySimulatorGame.ts
0
1
0.0%

src/features/storySimulator/scenes/ObjectPlacement/ObjectPlacementHelper.ts
0
2
0.0%

src/features/storySimulator/scenes/ObjectPlacement/ObjectPlacement.ts
0
19
0.0%

src/features/storySimulator/objects/SSObjectManager.ts
0
41
0.0%

Totals

Change from base Build 5711:
-0.1%

Covered Lines:
1970

Relevant Lines:
6691

💛  - Coveralls


Packing with Microsoft.Build.NoTargets doesn't put dependency under proper target framework group when reference other Microsoft.Build.NoTargets project

Describe the Bug

Hi @kzu!
I want to create "Microsoft.Build.NoTargets" project which uses Library project as reference and another "Microsoft.Build.NoTargets" which uses another Library project and the first "Microsoft.Build.NoTargets" project as references.
In the generated package's nuspec file the first "Microsoft.Build.NoTargets" project should be in the proper target framework group dependency, but it is inside common group and target framework group dependency is empty:
<dependencies>
  <group>
    <dependency id="Common" version="1.0.0" />
  </group>
  <group targetFramework="net5.0" />
</dependencies>

Steps to Reproduce

Open HierarchyTest.sln from attached file.
HierarchyTest.zip
Build HierarchyTest.sln solution with Visual Studio.
Unzip the result Core.1.0.0.nupkg file.
Open Core.nuspec file with some editor.
Observe - the "Common" package is inside common group dependency and there is empty net5.0 target framework group.

Expected Behavior

The "Common" package is inside net5.0 target framework group dependency.
Version Info

NuGetizer 0.7.5

@kzu,
I made a little donation, because fixing of this will help me mostly finish transition of my product packing to NuGetizer.
Thanks. 😉

Hi @kzu,
I found a way to workaround this behavior by setting TargetFramework="net5.0" attribute to Common.NuGet.msbuildproj project reference inside of Core.NuGet.msbuildproj project like so:
<ItemGroup>
  <ProjectReference Include="..\Common.NuGet\Common.NuGet.msbuildproj" TargetFramework="net5.0" />
  <ProjectReference Include="..\Core\Core.csproj" />
</ItemGroup>

I'm not sure if the original issue is designed behavior or actual bug, but the workaround resolves the problem.
Thanks.

Heya! Thanks for the donation!
Taking a look now. Sorry for the delay

Ok, found the reason, and it turns out it's "by design": the reasoning is that packaging projects can (and typically will) contain assets for multiple target frameworks. It's one of the main reasons why you'd want to have a packaging project in the first place, rather than just referencing the library (in your case), which would be framework specific.
There is another place where this is specified explicitly, as the BuildOutputFrameworkSpecific property, for authoring projects (aka packaging projects).
It would require performing packaging project contents analysis to determine if it indeed provides more than one target framework specific assets in order to automagically set the behavior you are looking for. Note, that if the packaging project provides build (with no TFM) assets, we'd also need to account for that, as well as potentially tools and other arbitrary assets you might want to include. It can get quite complicated quite fast.
I'm tempted to change the condition that sets the packaging project as non-TFM specific by checking for both authoring project and BuildOutputFrameworkSpecific!=true, which would allow you to get the behavior you want with:
<PropertyGroup>
   <BuildOutputFrameworkSpecific>true</BuildOutputFrameworkSpecific>
</PropertyGroup>

This would override the property we set by default, and should then kick in the updated behavior. As you noted, though, passing a target framework explicitly also sets the returned items with that value, which is another alternative (although perhaps not as intuitive).


Teleport double click bug

Hello friends!
Firstly, it seems that my mouse is crap, once is a time it does double click instead of just one click (yes, I know that I need to replace it...).
Anyways, I have been playing GW and wanted to teleport to Kamadan.
So I clicked on the Kamadan-shortcut in the teleport-window, and my mouse double-clicked it.
Instead of teleporting to kamadan, I found myself in Character-select scereen (https://i.imgur.com/d16KKFf.jpg) - with empty char slots, like the Client of a new account. From here I had to close GW and reopen it.
It happened to me few times, not only when I wanted to teleport to Kamadan (also the others, Vlox, Gadds etc.).

restart client because that is not a toolbox bug its related to the client itself I used to have that too

@BearsMan It happened alot of times (not only today), even after I restart GW Client.

Will look into that, but it's not suprising.

I was about to suggest making a new button type that had a delay check but its possible to duplicate this bug using TP command too

Yeah, we didn't put any guard arround it. I still want to deal with the button event in a single frame, but maybe we could disable button event for the next few ms.


AssertionError: Failed to build the detection model. Check if you have installed mmcv-full properly. You should first install mmcv-full successfully, then install mmdet, mmpose.

When I ran this script "python demo/demo_skeleton.py demo/ntu_sample.avi demo/demo.mp4", I met the problem below, would you please help me solve the problem, thanks!

Environment: mmcv 1.3.18, mmcv-full 1.3.18, mmdet 2.23.0, mmpose 0.24.0, torch 1.8.1+cu111

I noticed that the installation instructions for MMCV on the ReadTheDocs page mention a way to check the version of your installed MMCV package. Here's the link to the relevant section of the page:
https://mmcv.readthedocs.io/en/latest/get_started/installation.html#install-mmcv-full
Alternatively, if you need to reinstall MMCV or install a specific version, you can use the following command:
pip install mmcv-full==1.7.0 -f https://download.openmmlab.com/mmcv/dist/cu111/torch1.8/index.html
This will install version 1.7.0 of MMCV with CUDA 11.1 support for PyTorch 1.8. Keep in mind that you may need to adjust the cu111 and torch1.8 parts of the URL to match your specific CUDA and PyTorch versions, respectively.
I hope this helps! Let me know if you have any further questions.

Please following the new installation guide to reinstall pyskl and see if the problem has been fixed now.

请按照新的安装指南重新安装 pyskl 并查看问题是否已解决。
你好，我按照最新指南安装，仍出现相同的错误，请问需要如何解决?


Overlay widget ancestor cannot befound although it is in the tree (since version 3.7)

Steps to Reproduce
Since Flutter Version 3.7 the Overlay widget ancestor cannot be found although it is there.

Run example https://pub.dev/packages/showcaseview/example
Open view where overlay will be used
Exception in output

The error message states that for example a MaterialApp should be used in tree which is the case.
Issue is also tracked in plugin: https://github.com/SimformSolutionsPvtLtd/flutter_showcaseview/issues/330
Expected results:
A overlay should be visible.
Actual results:
Exception will be thrown and no overlay is visible

Code sample
https://pub.dev/packages/showcaseview/example

Logs
E/flutter (32324): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: No Overlay widget found.
E/flutter (32324): Some widgets require an Overlay widget ancestor for correct operation.
E/flutter (32324): The most common way to add an Overlay to an application is to include a MaterialApp, CupertinoApp or Navigator widget in the runApp() call.
E/flutter (32324): The context from which that widget was searching for an overlay was:
E/flutter (32324):   ShowCaseWidget
E/flutter (32324): #0      Overlay.of.<anonymous closure>
package:flutter/…/widgets/overlay.dart:384
E/flutter (32324): #1      Overlay.of
package:flutter/…/widgets/overlay.dart:387
E/flutter (32324): #2      _OverlayBuilderState.addToOverlay
package:showcaseview/src/layout_overlays.dart:174
E/flutter (32324): #3      _OverlayBuilderState.showOverlay
package:showcaseview/src/layout_overlays.dart:164
E/flutter (32324): #4      _OverlayBuilderState.initState.<anonymous closure>
package:showcaseview/src/layout_overlays.dart:129
E/flutter (32324): #5      SchedulerBinding._invokeFrameCallback
package:flutter/…/scheduler/binding.dart:1289
E/flutter (32324): #6      SchedulerBinding.handleDrawFrame
package:flutter/…/scheduler/binding.dart:1227
E/flutter (32324): #7      SchedulerBinding._handleDrawFrame
package:flutter/…/scheduler/binding.dart:1076
E/flutter (32324): #8      _invoke (dart:ui/hooks.dart:145:13)
E/flutter (32324): #9      PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:338:5)
E/flutter (32324): #10     _drawFrame (dart:ui/hooks.dart:112:31)
E/flutter (32324):
E/flutter (32324): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: No Overlay widget found.
E/flutter (32324): Some widgets require an Overlay widget ancestor for correct operation.
E/flutter (32324): The most common way to add an Overlay to an application is to include a MaterialApp, CupertinoApp or Navigator widget in the runApp() call.
E/flutter (32324): The context from which that widget was searching for an overlay was:
E/flutter (32324):   ShowCaseWidget
E/flutter (32324): #0      Overlay.of.<anonymous closure>
package:flutter/…/widgets/overlay.dart:384
E/flutter (32324): #1      Overlay.of
package:flutter/…/widgets/overlay.dart:387
E/flutter (32324): #2      _OverlayBuilderState.addToOverlay
package:showcaseview/src/layout_overlays.dart:174
E/flutter (32324): #3      _OverlayBuilderState.showOverlay
package:showcaseview/src/layout_overlays.dart:164
E/flutter (32324): #4      _OverlayBuilderState.initState.<anonymous closure>
package:showcaseview/src/layout_overlays.dart:129
E/flutter (32324): #5      SchedulerBinding._invokeFrameCallback
package:flutter/…/scheduler/binding.dart:1289
E/flutter (32324): #6      SchedulerBinding.handleDrawFrame
package:flutter/…/scheduler/binding.dart:1227
E/flutter (32324): #7      SchedulerBinding._handleDrawFrame
package:flutter/…/scheduler/binding.dart:1076
E/flutter (32324): #8      _invoke (dart:ui/hooks.dart:145:13)
E/flutter (32324): #9      PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:338:5)
E/flutter (32324): #10     _drawFrame (dart:ui/hooks.dart:112:31)
E/flutter (32324):

0 issues found. (ran in 3.3s)

[√] Flutter (Channel stable, 3.7.3, on Microsoft Windows [Version 10.0.22621.1105], locale de-AT)
    • Flutter version 3.7.3 on channel stable at D:\Development\SDK\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision<PHONE_NUMBER> (4 days ago), 2023-02-08 15:46:04 -0800
    • Engine revision 248290d6d5
    • Dart version 2.19.2
    • DevTools version 2.20.1

[X] Windows Version (Unable to confirm if installed Windows version is 10 or greater)

[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at C:\Users\thoma\AppData\Local\Android\sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: C:\Program Files\Java\jdk-18\bin\java
    • Java version Java(TM) SE Runtime Environment (build 18+36-2087)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Professional 2022 17.0.5)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Professional
    • Visual Studio Professional 2022 version 17.0.32112.339
    • Windows 10 SDK version 10.0.22000.0

[!] Android Studio (version 2022.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    X Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[√] IntelliJ IDEA Ultimate Edition (version 2020.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2020.2.4
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin version 202.8346

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22621.1105]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 110.0.5481.77
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 110.0.1587.41

[√] HTTP Host Availability
    • All required HTTP hosts are available

Hey @Spitzbua. Can you provide a complete and minimal, reproducible code sample that doesn't use any 3rd party libraries?

Hi all. It's not flutter problem(maybe..) I refactorted code of the 3rd pary plugin and resolve the same problem
new code without problem:
  Future<void> addToOverlay(OverlayEntry overlayEntry) async {
    if (mounted) {
      if (ShowCaseWidget.of(context)?.context != null) {
        final overlay = Overlay.of(context);
        WidgetsBinding.instance
            .addPostFrameCallback((_) => overlay.insert(overlayEntry));

      } else {
        final overlay = Overlay.of(context);
        WidgetsBinding.instance
            .addPostFrameCallback((_) => overlay.insert(overlayEntry));
      }
    }
  }

not working code
  void addToOverlay(OverlayEntry overlayEntry) async {     final showCaseContext = ShowCaseWidget.of(context).context;     if (mounted) {       if (Overlay.of(showCaseContext) != null) {         Overlay.of(showCaseContext)!.insert(overlayEntry);       } else {         if (Overlay.of(context) != null) {           Overlay.of(context)!.insert(overlayEntry);         }       }     }   }

@exaby73, thank you for your answer. Actually I have tried to create a complete and minimal, reproducible code sample but in that case it is not really simple. My codebase is quite big and to extract only that code that is problematic is not possible because it is actually a combination of the new flutter version, go router and the showcase plugin.
It's a fact that the same codebase is working with 3.3.10 and is not working with 3.7 and above. The behaviour that changed is the search for an Overlay widget in the context.
final showCaseContext = ShowCaseWidget.of(context).context;
Overlay.of(showCaseContext)

Using version 3.3.10 the call succeeded. Using version 3.7 ends in following exception.
E/flutter (23237): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: No Overlay widget found.
E/flutter (23237): Some widgets require an Overlay widget ancestor for correct operation.
E/flutter (23237): The most common way to add an Overlay to an application is to include a MaterialApp, CupertinoApp or Navigator widget in the runApp() call.
E/flutter (23237): The context from which that widget was searching for an overlay was:
E/flutter (23237):   ShowCaseWidget

It seems the mystery is solved. Starting with version 3.7, the call
Overlay.of(context)
throws a hard error which no longer allows the condition check
 if (Overlay.of(context) != null)
I guess the solution is to use the maybeOf method which throws an error.
if (Overlay.maybeOf(context) != null)

This looks like an issue in the package you're using. I suggest you raise an issue with the package author


Add questions related to array

can i work on this??? @Nexengineer

Go ahead dude

please do raise a PR

i have raised the PR for sortings in array @Nexengineer

Merged

Hey @Nexengineer, I also want to add questions. Can you pls assign it to me.

Assigned

@Nexengineer  can you please assign me this!

It is mostly an open-ended Issue. Who soever wants to work on this can work on it directly. This will be open till hacktoberfest lasts

I will add Some array questions. Please merge it...

please assign me this task

@Hanuvesh go ahead

@Nexengineer please assign me this issue.


Session 1: Questions for Prof Taleb

Please use this thread to submit questions for Session 1:
https://www.meetup.com/global-technical-incerto-reading-club/events/275697847/

Chapter 5: Zipf Plot
Question
How do you draw the tail fit line in Zipf plots?
Context:
I want to build a Python function for survival plots.

Is OLS regression a bad idea?
What's a better idea?
Is the answer later in the book? 😄

Examples:
Chapter 5 Zipf plot:

Python Zipf plot code:

https://github.com/FergM/fattails/blob/main/notebooks/NB-25 - Survival Plot - Gamestop.ipynb

Mathematica Code
Could you share some of the Mathematica Code?

Chapter 8: How much data do I need?
Question
Can you confirm whether Equation 8.8 is correct?
Equations
Book version:

My derivation:

My workings:

https://github.com/FergM/fattails/blob/main/docs/Notes-02 - Derivation - How much data do I need.pdf

Shouldn't the quote at the beginning of chapter 3 be:

תְּהֽוֹם־אֶל־תְּה֣וֹם ק֖וֹרֵא

instead of:

תְּהֽוֹם־אֶל־תְּה֣וֹם כוֹרֵא
?

How can we apply (further) fat-tailed distributions in clinical research (clinical epidemiology) and biostatistics (i.e. survival analysis, clinical trials, and observational studies)? Or what limitations should doctors and epidemiologists acknowledge whenever they report results using their statistical models? I have been reading your posts on your comments on some Lancet journal articles, Lindy Effect, and using the entropy approach, and the "Tail Risk of Contagious Diseases", and I find them very insightful...

Chapter 25
First I would like to thanks Mr. Taleb and the organizers for this opportunity. Hopefully I got the line correct and my questions are not too amateur.
25.2.1 Analyzing the Constrains:

can we first set epsilon at some level (say 0.99 or maybe other "ideal" level?) and then proceed to calculate VaR assuming normality (as per maximizing entropy condition) or perhaps should we calculate it after an EVT approach?
it's there an impact on the risk of ruin or on the overall performance if the choice of K happens to be "too small" given the initial capital?

Proposition 25.1

pluging the parameters in the mu formula for a simple B&H portfolio of two risky assets would often yield a negative value for epsilon around 0.5 or higher, does that mean the portfolio should avoid losses above this apparently "low" threshold? (so that the condition mu>0, sigma>K/n(e) are satisfied) and further dynamically adjusted via stop-loss/options?

Trying to execute the function in R under the global mean constraint would often yield a distribution with a huge spike, would that be the spot what which we set the Dirac function for the stop?
Thank you for your time!