UXPLATFORM-9611: Enhance screen reader support to announce column headers are interactable.

Summary
Added additional screen reader support to announce that column headers are interactable upon selection by giving focus to the button control that allows column headers to be selected.
What was changed:
Focus of a column header cell is changed from the cell to the button control inside the cell that allows selection.
Why it was changed:
To ensure screen readers announce that column headers are interactable upon selection.
Testing
This change was tested using:

[x] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[x] Accessibility review
[ ] Functional review

This PR resolves: UXPLATFORM-9611

What is the plan to get these changes into the new Terra Table component?

What is the plan to get these changes into the new Terra Table component?

The plan is to merge these into #1813 for now and then integrate that PR into the Table component once that is ready. This way, there will be a single PR that needs to be refactored.

@KoushikKalli  @brithom Tested for accessibility. Looks good, great job! Updating the label to a11y reviewed.
Tested with Edge and JAWS 2022.2202.38
The screen reader communicated appropriately on a sortable column header 'to activate press enter', upon pressing enter the sort updated appropriately


Initialization of multiple providers (module.json) have wrong direction

Hello,
I will start directly with my example:
I have 2 modules: Core and Test.
Within Core I have 2 Providers: CoreServiceProvider and MenuServiceProvider.
Within Test I have 1 Provider: TestServiceProvider.
module.json files in the attachment.
When I load my site I get the following load direction:
CoreServiceProvider
TestServiceProvider
MenuServiceProvider
But this is false, because MenuServiceProvider is attached to the Core Module (see module.json). So I think the correct direction is
CoreServiceProvider
MenuServiceProvider
TestServiceProvider
Can u help here ? The correct direction is very important for me, because each module can register menu points through the MenuServiceProvider in Core-Module. But when it loaded at last I will have errors.
Thanks for Help.

Closed.
I was my error. Sorry!


Update Statement request - Exclude fields Or automatique mapping of fields received

Hi,
Continue playing with pg and Iris.
I use CockroachDB. Currently when we used a CreatedAt or UpdateAt has Timestamp it will create a trigger to assign those field and it's a great feature!
CockroachDB, do not support trigger so I renamed my audit field to CrtdAt and UpdtAt.
So now in my Create method, I will assign both CrtdAt and UpdtAt with time.Now()
And now in my Update method, I will assign only UpdtAt with time.Now()
Because, my json do not send back my CrtdAt field, the CrtdAt is reset to default value
"id": "7b303113-18f7-443b-a2a0-9609fab7beb9",
"crtdAt": "0001-01-01T00:00:00Z",
"updAt": "2023-07-07T01:22:26.17382Z",
"email"<EMAIL_ADDRESS>"password": "$2a$06$NTf24l4/IAhapOktfoDewu749lpxm2EV6ZKuiqFxL7SYqb2r1CGpm",
"firstName": "André",
"middleName": "sssssssss",
"lastName": "Leblanc",
"sex": "M"
If we have a way to exclude field instead of UpdateOnly:
return repo.UpdateOnlyColumns(ctx, nil, values...)
I could just exclude my CrtdAt on Update.
OR
Event better, if the Update SQL statement was base only on the received fields from the body.
We need to make sure when we create the record all our non null fields are valid. Then we should be good.
What do you think does it make senses ?
type User struct {
	Id         string    `json:"id" pg:"type=uuid,primary"`
	CrtdAt     time.Time `json:"crtdAt" pg:"type=TIMESTAMPTZ"`
	UpdAt      time.Time `json:"updAt" pg:"type=TIMESTAMPTZ"`
	Email      string    `json:"email" pg:"type=varchar(255),username,unique"`
	Password   string    `json:"password" pg:"type=varchar(128),password"`
	FirstName  string    `json:"firstName" pg:"type=varchar(255)"`
	MiddleName *string   `json:"middleName" pg:"type=varchar(255),null"`
	LastName   string    `json:"lastName" pg:"type=varchar(255)"`
	Sex        *string   `json:"sex" pg:"type=char(1),null"`
}

Thanks!

Hello @aleblanc70, the update with exclude is a good idea, I am going to add it, but I think you don't need it. Did you try to add the ,default=clock_timestamp()" to your CrtdAt and UpdAt fields?

OK @aleblanc70, I have added the new UpdateExceptColumns method, can you try it and reply back if that works for you?

OK @aleblanc70, I have added the new UpdateExceptColumns method, can you try it and reply back if that works for you?
go get github.com/kataras/pg@main

I got the error
exec: ERROR: multiple assignments to the same column "id" (SQLSTATE 42601)

@aleblanc70 you column fields does not match the except ones that's why you getting the error probably.
When you don't define a column name (pg:"name=columnName...") in your struct field tag, the default column name is the lowercase version of the struct field name and if it contains an uppercase letter then it adds a _ except ID, URL. For example
Title string `pg:"type=varchar(255),unique

^ The column name is not Title but title.
I assume you are using lowercase for your column naming in your database, right? If no, please specifiy the name tag option (Title string pg:"name=Title,type=varchar(255),unique"`) or I can add a global variable which you can use to declare to keep the column names same as the struct field names if the name tag option is missing.
If the column name in your database are in lowercase, then you need to pass those column names instead of this:
except := []string{"Title", "EndAt", "UpdAt", "CrtdAt", "ID"}

to:
except := []string{"title", "end_at", "upd_at", "crtd_at", "id"}

@aleblanc70 you column fields does not match the except ones that's why you getting the error probably.
When you don't define a column name (pg:"name=columnName...") in your struct field tag, the default column name is snake_case version of the struct field name. For example:
Title string `pg:"type=varchar(255),unique"`

^ The column name is not Title but title.
I assume you are using lowercase for your column naming in your database, right? If no, please specifiy the name tag option:
Title string `pg:"name=Title,type=varchar(255),unique"`

Or I can add a global variable which you can use to declare to keep the column names same as the struct field names if the name tag option is missing.
If the column name in your database are in lowercase, then you need to pass those column names instead of this:
except := []string{"Title", "EndAt", "UpdAt", "CrtdAt", "ID"}

to:
except := []string{"title", "end_at", "upd_at", "crtd_at", "id"}

@aleblanc70 you column fields does not match the except ones that's why you getting the error probably.
When you don't define a column name (pg:"name=columnName...") in your struct field tag, the default column name is snake_case version of the struct field name. For example:
Title string `pg:"type=varchar(255),unique"`

^ The column name is not Title but title.
I assume you are using lowercase for your column naming in your database, right? If no, please specifiy the name tag option:
Title string `pg:"name=Title,type=varchar(255),unique"`

Or call the new pg.SetKeepColumnName(true) before everything else to keep the column names same as the struct field names when the tag option name is missing.
If the column name in your database are in lowercase, then you need to pass those column names instead of this:
except := []string{"Title", "EndAt", "UpdAt", "CrtdAt", "ID"}

to:
except := []string{"title", "end_at", "upd_at", "crtd_at", "id"}

@aleblanc70 The column names to except do not match the schema's ones, that's why you getting that error. Why they don't match? Answer follows up:
When you don't define a column name (pg:"name=columnName...") in your struct field tag, the default column name is snake_case version of the struct field name. For example:
Title string `pg:"type=varchar(255),unique"`

^ The column name is not Title but title.
I assume you are using lowercase for your column naming in your database, right? If no, please specifiy the name tag option:
Title string `pg:"name=Title,type=varchar(255),unique"`

Or call the new pg.SetDefaultColumnNameMapper(pg.NoColumnNameMapper) before everything else to keep the column names same as the struct field names when the tag option name is missing OR if you want to use the JSON naming: pg.SetDefaultColumnNameMapper(pg.JSONColumnNameMapper)
$ go get github.com/kataras/pg@main

func init() {
    pg.SetDefaultColumnNameMapper(pg.NoColumnNameMapper)
}

If the column name in your database are in lowercase, then you need to pass those column names instead of this:
except := []string{"Title", "EndAt", "UpdAt", "CrtdAt", "ID"}

to:
except := []string{"title", "end_at", "upd_at", "crtd_at", "id"}

@aleblanc70 The column names to except do not match the schema's ones, that's why you getting that error. Why they don't match? Answer follows up:
When you don't define a column name (pg:"name=columnName...") in your struct field tag, the default column name is snake_case version of the struct field name. For example:
Title string `pg:"type=varchar(255),unique"`

^ The column name is converted to title.
You can set a custom column name for each field by passing the name pg struct field tag option:
Title string `pg:"name=Title,type=varchar(255),unique"`

You can also set a global column name mapper for all column names if the name pg struct field tag option is missing, as shown below:
$ go get github.com/kataras/pg@main

To keep the column names same as the struct field names (Title -> Title, CrtdAt -> CrtdAt):
func init() {
    pg.SetDefaultColumnNameMapper(pg.NoColumnNameMapper)
}

except := []string{"Title", "EndAt", "UpdAt", "CrtdAt", "ID"}

To convert the column names to their json struct field (if exists, otherwise field name):
func init() {
    pg.SetDefaultColumnNameMapper(pg.JSONColumnNameMapper)
}

except := []string{"title", "endAt", "updAt", "crtdAt", "id"}

To keep the default behavior (snake_case column names), just change your except list to (Title -> title, CrtdAt -> crtd_at):
except := []string{"title", "end_at", "upd_at", "crtd_at", "id"}

@aleblanc70 The column names to except do not match the schema's ones, that's why you getting that error. Why they don't match? Answer follows up:
When you don't define a column name (pg:"name=columnName...") in your struct field tag, the default column name is snake_case version of the struct field name. For example:
Title string `pg:"type=varchar(255),unique"`

^ The column name is converted to title.
You can set a custom column name for each field by passing the name pg struct field tag option:
Title string `pg:"name=Title,type=varchar(255),unique"`

You can also set a global column name mapper for all column names if the name pg struct field tag option is missing, as shown below:
$ go get github.com/kataras/pg@main

To keep the column names same as the struct field names (Title -> Title, CrtdAt -> CrtdAt):
func init() {
    pg.SetDefaultColumnNameMapper(pg.NoColumnNameMapper)
}

except := []string{"Title", "EndAt", "UpdAt", "CrtdAt", "ID"}

To convert the column names to their json struct field (if exists, otherwise field name):
func init() {
    pg.SetDefaultColumnNameMapper(pg.JSONColumnNameMapper)
}

except := []string{"title", "endAt", "updAt", "crtdAt", "id"}

To keep the default behavior (snake_case column names), just change your except list to (Title -> title, CrtdAt -> crtd_at):
except := []string{"title", "end_at", "upd_at", "crtd_at", "id"}

Bonus tips:
To log all the performed queries you can register a logger:
import (
  // ...
  "github.com/kataras/golog"
  "pgxgolog "github.com/kataras/pgx-golog"
)

// ...
db, err := pg.Open(
  context.Background(),
  schema,
  dsn,
  pg.WithLogger(pgxgolog.NewLogger(golog.Default))) // <- HERE

You don't have to set type=TIMESTAMPTZ, you can use its lowercase version as well type=timestamptz.
Please don't hesitate to reply back if the problem was not solved!

@aleblanc70 The column names to except (except string slice) do not match the schema's ones. But why they don't match? Answer follows up:
When you don't define a column name (pg:"name=columnName...") in your struct field tag, the default column name is snake_case version of the struct field name. For example:
Title string `pg:"type=varchar(255),unique"`

^ The column name is converted to title.
You can set a custom column name for each field by passing the name pg struct field tag option:
Title string `pg:"name=Title,type=varchar(255),unique"`

You can also set a global column name mapper for all column names if the name pg struct field tag option is missing, as shown below:
$ go get github.com/kataras/pg@main

To keep the column names same as the struct field names (Title -> Title, CrtdAt -> CrtdAt):
func init() {
    pg.SetDefaultColumnNameMapper(pg.NoColumnNameMapper)
}

except := []string{"Title", "EndAt", "UpdAt", "CrtdAt", "ID"}

To convert the column names to their json struct field (if exists, otherwise field name):
func init() {
    pg.SetDefaultColumnNameMapper(pg.JSONColumnNameMapper)
}

except := []string{"title", "endAt", "updAt", "crtdAt", "id"}

To keep the default behavior (snake_case column names), just change your except list to (Title -> title, CrtdAt -> crtd_at):
except := []string{"title", "end_at", "upd_at", "crtd_at", "id"}

Bonus tips:
To log all the performed queries you can register a logger:
import (
  // ...
  "github.com/kataras/golog"
  pgxgolog "github.com/kataras/pgx-golog"
)

// ...
db, err := pg.Open(
  context.Background(),
  schema,
  dsn,
  pg.WithLogger(pgxgolog.NewLogger(golog.Default))) // <- HERE

You don't have to set type=TIMESTAMPTZ, you can use its lowercase version as well type=timestamptz.
Please don't hesitate to reply back if the problem was not solved!

It work great now thanks for your help! :)

You're welcome @aleblanc70! Glad to help


Wrong delimiter in db2 script

Describe the issue:
The provided DB2 script in $subject contains a delimiter issue. The script, as currently written, uses ";" as the delimiter, but it should use "/".
CREATE TABLE UM_HYBRID_ROLE_AUDIENCE(
    UM_ID DECIMAL(31,0) NOT NULL,
    UM_AUDIENCE VARCHAR(255) NOT NULL,
    UM_AUDIENCE_ID VARCHAR(255) NOT NULL,
    UNIQUE (UM_AUDIENCE, UM_AUDIENCE_ID),
    PRIMARY KEY (UM_ID)
);

**How to reproduce:**
Attempt to run the SQL script using DB2 with the following command:

docker exec -t $container_id su - db2inst1 -c "db2 connect to $SHARED_DB_NAME user $DB_USERNAME using
$DB_PASSWORD; db2 -td/ -f /tmp/dbscripts/db2.sql"
**Expected behavior:**
- The SQL script should execute without any problems

**Environment information** (_Please complete the following information; remove  any unnecessary fields_) **:**
- Product Version: [e.g., IS 5.10.0, IS 5.9.0]
- OS: [e.g., Windows, Linux, Mac]
- Database: [e.g., MySQL, H2]
- Userstore: [e.g., LDAP, JDBC]

---

### Optional Fields

**Related issues:**
<!-- Any related issues from this/other repositories-->

**Suggested labels:**
<!-- Only to be used by non-members -->

This issue is fixed from following PR

https://github.com/wso2/carbon-kernel/pull/3761


Fix update issue

https://github.com/docker-php/docker-php/issues/260

It should be available on 2.0, if you really need it on 1.24, please reopen this pr, update the specification and regenerate the code instead of direct modification.


Runtime error: load of value 8199, which is not a valid value for type 'PropertyHint'

Godot version:
3.2.alpha.custom_build.24e1039eb
OS/device including version:
Ubuntu 19.04
Issue description:
This is caused by this line
https://github.com/godotengine/godot/blob/24e1039eb6fe32115e8d1a62a84965e9be19a2ed/scene/gui/rich_text_label.cpp#L2634
@Eoin-ONeill-Yokai
Steps to reproduce
Just run Godot, to see this errors compile Godot with sanitizers support.

Thanks for tagging me. Could you try my latest pull request? I have resolved the issue on my end and want to make sure it is working well for you as well.

This should be closed now since the fix has been merged. @KoBeWi or anyone else who can do that for me.


horizontal line elements *** don't render correctly when centred

when rendering a markdown document, if I apply a .multilineTextAlignment(.center) modifier, the text will center just fine but but horizontal  lines *** start at the center point and are not centered.
example centred:

example left justified:

I will look into this. Thanks for reporting it.

Hey @bartreardon,
The fix for this issue will be included in the next release.
Thanks!


Logo contribution

Here is my small and humble contribution for a logo for the app. Nothing fancy here as I'm not a designer, but something clean and minimal.

The "logo" can be done without the image, use the string 🐻 STANDUP APP and give it the font "Work Sans" with the bolder weight you can get with the BearStudio yellow and you are good to go.

More than a standup app, this application will become a huge part in the BearStudio processes. We should probably think about a renaming before making a logo?

More than a standup app, this application will become a huge part in the BearStudio processes. We should probably think about a renaming before making a logo?
Thanks you very much for logo idea Yoann.
I agree with the idea of a renaming, maybe we can imagine something like "Bearstudio Hub", I will sound out Bearstudio team.

Following your idea but waiting for the new app name, i put a not definitive logo with simply "BEARSTUDIO"


how configure interstitial ad between 2pages.

This is not issue.I have no idea how handle interstitial ad between pages.I have 2 page.name_one.dart and name_two.dart.I want to show interstitial when exist from name_two.dart and go to name_one.dart.
Thanks you

I use WillpopScope widget but don't show intersittial ad.```
    Future<bool> _willPopCallback() async {
  // await showDialog or Show add banners or whatever
  // First, create an interstitial ad
  AdmobInterstitial interstitialAd = AdmobInterstitial(
    adUnitId: AdUtil.getInterstitialAdUnitId(),
  );

// Interstitials must be loaded before shown.
// Make sure to always load them ahead so they can be
// available to be shown immediately to the user
// Check if the ad is loaded and then show it
  if(await interstitialAd.isLoaded) {
    interstitialAd.show();
  }

// Finally, make sure you dispose the ad if you're done with it
interstitialAd.dispose();
// then
//return true; // return true if the route to be popped
return true;
}

solved thanks


One Dockerfile to rule them all...

Sorry for the epic title :-)
@brettowe proposed a Dockerfile in #15 that runs the Crusader server. This is great: it removes the (significant) hassle of installing and using a rust development environment, etc. (It's a boatload easier to tell newcomers how to install Docker than Rust...)
But this Crusader container only solves part of the problem: there's no way to run either the CLI client or (more interestingly) the GUI client.
Here's a wacky thought: What would be involved in making the Docker container run all three pieces: Server, CLI Client, and GUI Client? Here are my thoughts:

The Docker container already runs the server

The Docker container could run a web server (in parallel with the Crusader server) that responds to commands from a web GUI as needed.

It would be a minimal GUI to retrieve an address from the web page and invoke ./crusader test <address>

The web server could return the results using the existing .png

To use the interactive charts, it would be a modest project to process the .crr file which I assume contains the data to produce the graphs.

Does this idea even make sense? Thanks for listening.

I'm not convinced of the Docker aspect, but it might make more sense as a remote client.

Yes - Docker takes a little getting used to - but I'm completely sold on it. I dabble in lots of different projects. I used to wind up with many, sometimes incompatible, versions of development tools: wrasslin' with pyenv, nvm, various versions of the rust tool chain, etc. I have vivid (bad) memories of trying to get a python or node project working on my laptop with exactly the right combination of library versions that don't conflict with another project.
With Docker, you create a container that bundles a known-good set of tools. When new people use the container, they get the very same versions of all the tools. And it's a piece of cake for new developers to join the project. Things just work.
And it's easy to install Docker on virtually any computer (and it's well within the capacity of anyone who'd be interested in Crusader). <end of sales pitch>
To kick things off, I'd be willing to spend some time on the Dockerfile to build Crusader and bundle in the web server. Might this be interesting? Thanks.

I did add a simple crusader remote command for now which runs a web server.

Wow! That was speedy. I like the web interface!
I still think a Dockerfile will be valuable, but crusader remote makes it much simpler. Thanks.

Oh, wait... I just realized that you have pre-built binaries for all kinds of platforms: Windows, Mac, Linux, Android...
I am going to close this - most people won't need a Dockerfile to run Crusader. I'll raise a PR to update the documentation


Publish Docker images as part of each release

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I would like users to be able to download Ballista docker images instead of having to build them themselves.
Describe the solution you'd like
Publish Docker images to Apache repo in DockerHub. Based this on how Spark does this?
Describe alternatives you've considered
None
Additional context
None

I 1000% support this. Every other major software has pre-packaged docker image you can just pull and run. Pushing it to docker hub is easy, the harder part is that we need an apache account with credentials, then to put that secret in CI. Even if it is in CI, I don't know how we could prevent it leaking from PRs, but I could look into it.

I filed a ticket with INFRA: https://issues.apache.org/jira/browse/INFRA-23709

My understanding is that the Docker image URLs would be
gcr.io/apache/arrow-ballista-scheduler
gcr.io/apache/arrow-ballista-executor

We may also want to publish some client images to make it easier for users who don't already have appropriate Rust or Python setups.
gcr.io/apache/arrow-ballista-cli
gcr.io/apache/arrow-ballista-python

Just a heads up, gcr.io is google's container registry, ghcr.io is github's.

Here is the updated proposal for how this will work:
We can use a GitHub action to push to ghcr.io when we push release tags to the repo.
When we tag the repo with a release candidate tag e.g. 0.10.0-rc1, we start a vote that covers both the source release (tarball) and also the published Docker image release candidate.
Once the vote passes, we push the 0.10.0 tag, and this will cause the image to be published with the 0.10.0 version, and we can then announce that as an official release.

@avantgardnerio fyi

S&t will 100% volunteer for this 🤠

Thanks @avantgardnerio. I assume that this is too much to try and get into 0.10.0 (planning on releasing this in the next few days), so I have tagged this for 0.11.0. Let me know if do you want to try and do this for 0.10.0 (we an always delay the release to accommodate this).

Adding for reference: currently blocked by https://issues.apache.org/jira/browse/INFRA-23897


Alignment issue in mi_malloc_aligned when requested size = alignment (regression on dev-slice)

Hello,
We recently tried to bump mimalloc from 1.7.9 to 2.0.9.
However we noticed a regression in mi_malloc_aligned when size = alignment for the following values: 256, 512, 1024 (all other values down to 8 and up to 1MB are correctly handled though).
Tests done on windows using Visual Studio 2022, MI_PADDING and MI_DEBUG are not set.

I've just started using mimalloc, so I'm not familiar enough with the code to say for certain yet, but...
The sizes up to 128 are correct, and starting from 1024 again, so that's a factor of 8.
In mi_heap_malloc_aligned, is that supposed to say MI_SMALL_WSIZE_MAX instead of MI_SMALL_SIZE_MAX in those ifs?
That would at least solve the issue, and it'd be an easy mistake to make.
Maybe @daanx knows?

Wow, that was a terrible bug; :-(  Should be fixed in the latest dev-slice -- Thanks so much for the report!


Add metric monitoring doc

Add metric monitoring under tutorial section. A quick note on how to access it. (as part of 0.3.0 release)

@dcrankshaw fixed!

You're still missing the link to Prometheus website


WAMR debugging improvements

Summary
I've created this issue to track a few of the debugging improvements that we've planned to add, so that we can use it as a reference in PRs and close on any open decisions. We have merged some improvements into WAMR already, which are marked in the tasks, but the latter require a little more organisation.
Publish WAMR IDE vscode extension to marketplace

What: Publish the WAMR IDE extension to VS Code marketplace on when release job is run
Why: This saves the debugging engineer time finding WAMR IDE extension version & will automatically update it when a new version is created.
How: There is a WAMR release step that bundles the VScode extension and uploads it to WAMR releases. This should be updated to also upload to the VS Code extension marketplace. There is a guide on publishing an extension through VSCode.

Add memory watchpoint control to WAMR IDE

What: Add ability to set watchpoints in a WAMR IDE vscode debug session
Why: This is a more user-friendly way of viewing and setting watchpoints vs the CLI
How: Memory watchpoint support enabled in the debug interpreter, however we need to update the LLDB debug adapter so that VSCode can interface with it.

Add disassembly view to WAMR IDE

What: Add ability to see disassembly of WASM in a WAMR IDE vscode debug session
Why: This will allow a more fine grain view into what is actually being executed by WAMR, rather than the DWARF mapped code.
How: It's possible to disassemble WAMR debug interpreter in CLI. This requires an update to the LLDB debug adapter WAMR IDE uses so that VSCode can interface with it.

Tasks

[x] Build macOS patched lldb in WAMR pipeline
[x] Install patched lldb on WAMR IDE vscode extension activation
[x] Add memory watchpoint support to classic interpreter
[ ] Publish WAMR IDE vscode extension to marketplace
[ ] Add memory watchpoint control to WAMR IDE
[ ] Add disassembly view to WAMR IDE

Our current plans are:
Publish WAMR IDE vscode extension to marketplace - bafadumi@ is ready to make a contribution here. We think there is some discussion needed with WAMR maintainers about what destination we should be publishing the vscode extension to. I believe it may require a Microsoft account to be published.
Add memory watchpoint control to WAMR IDE & Add disassembly view to WAMR IDE - We have some changes ready for review. We're planning to push these to upstream LLVM & then pull the latest version into WAMR. For internal use in the meantime, we can build the WAMR IDE ext from a fork with a patch to enable them. If we get to the point of publishing the vscode extension to marketplace, and the LLVM contribution is still pending, we might request temporarily including the changes in the existing LLDB patch WAMR applies as part of the CI.

Thanks @cimacmillan

I believe it may require a Microsoft account to be published.

From what I see in the doc, we need azure devops account to generate personal access token. @xwang98 do you know if we already have WAMR account for that? Or should we discuss in the next TSC meeting how do we manage this (and I guess, in the future, similar) accounts, how to grant access etc.?

we can build the WAMR IDE ext from a fork
@cimacmillan where is the fork hosted?

Also, @wenyongh I remember there were some discussions about getting the patch for enabling WAMR debugging merged to LLVM; is there any progress on that? Should we chase LLDB maintainers to provide us with more specific feedback so we could possibly address it and merge it upstream?

Also, not sure if this should be done as part of this ticket or should we have another one for this, but I think it'd be great to support core dumps as they're defined here: https://github.com/WebAssembly/tool-conventions/pull/195 @cimacmillan what's your opinion?

@loganek Looks like a useful tool! I suppose this ticket is useful for general discussions about the work we have planned so don't mind including this here (& debugging WASI threads).

Or should we discuss in the next TSC meeting how do we manage this (and I guess, in the future, similar) accounts, how to grant access etc.?

Thanks for calling this out. Is there a regular meeting we can join to help close out that item?

Thanks for calling this out. Is there a regular meeting we can join to help close out that item?

I think you can propose a solution and if reasonable, we can implement it; otherwise, I can bring up the topic in the next TSC meeting (which happens monthlyish) and share the update.

Thanks @cimacmillan

I believe it may require a Microsoft account to be published.

From what I see in the doc, we need azure devops account to generate personal access token. @xwang98 do you know if we already have WAMR account for that? Or should we discuss in the next TSC meeting how do we manage this (and I guess, in the future, similar) accounts, how to grant access etc.?

we can build the WAMR IDE ext from a fork
@cimacmillan where is the fork hosted?

Also, @wenyongh I remember there were some discussions about getting the patch for enabling WAMR debugging merged to LLVM; is there any progress on that? Should we chase LLDB maintainers to provide us with more specific feedback so we could possibly address it and merge it upstream?

@loganek No any progress yet. We are trying to upgrade the toolkits (llvm, wasi-sdk, emsdk, wabt, etc.), I think we can upgrade llvm to version 15.0 and update the lldb patch accordingly: current lldb patch is based on llvm 13.0, maybe we can re-create the patch based on llvm 15.0 (and llvm main branch), and then try to make it upstream.
And yes, it would be great if the LLDB maintainers can provide us with more specific feedback so that we can address it.


Requiring unknown module './react-native' since upgrade to 2.0.0

Hello,
Since upgrade to 2.0.0, I get the following error while launching my app:

Seems that it should be 'react-native' instead of './react-native', is it normal ?
Thanks,

I can't reproduce the error you are getting using the IconExplorer project, did you restart packager after upgrading? ./react-native is necessary to support react-native-desktop.

@oblador
Thanks for your quick answer, I had to perform all those steps to make it work:

Relaunch packager
Delete node_modules folder and reinstall all

rm -rf node_modules && npm install

Delete list of files watched by Watchman

watchman watch-del-all

Reset packager cache

react-native start --reset-cache

Closing this.


Provide support or recommendation for how to interact with conda-lock lockfiles

Proposed change

At the moment, repo2docker supports conda/mamba/micromamba environment.yml environment files as Binder config files. This is great, but even if you pin packages with == their dependencies can still float and so reproducibility into the future can break. For long term reproducible builds (e.g. launching into Binder from a Zenodo DOI) you would want to be able to also have repo2docker work with lock files. As the conda ecosystem is already supported a natural extension would be to use conda-lock, and with mamba/micromamba you can interact with conda-lock lock files on a nearly equal footing as you would an environment.yml.
However, at the moment, if you place a conda-lock lock file named environment.yml under a binder/ directory in a repo, repo2docker will fail to build from it and error with
EnvironmentSectionNotValid: The following sections on '/home/jovyan/binder/environment.yml' are invalid and will be ignored:
 - version
 - metadata
 - package

(c.f. https://github.com/matthewfeickert-talks/talk-pyhep-2023/pull/5)
It would be super nice if conda-lock lock files could have support added for them as a valid repo2docker config file.
Alternative options

Though if that is too big of a feature request, it would be nice if there was a method to allow users to interact with a conda-lock lock file that works with postBuild. At the moment, if you try to have a postBuild config file that has
conda env update --file binder/conda-lock.yml --prune

this will again fail with
EnvironmentSectionNotValid: The following sections on '/home/jovyan/binder/environment.yml' are invalid and will be ignored:
 - version
 - metadata
 - package

While micromamba is able to handle a command like
micromamba install --file binder/conda-lock.yml

it seems that conda can not and so similarly having a postBuild file with
conda install --file binder/conda-lock.yml

will fail with
CondaValueError: could not parse 'version: 1' in: binder/conda-lock.yml

If the ability to install an environment from a conda-lock lock file without supporting conda-lock could be supported then if instructions on how to work with conda-lock lock files were also added this could resolve things as well.
Who would use this feature?

People that want to ensure that a Binder link will run far into the future (so maybe the same people that put things on Zenodo).
How much effort will adding it take?

I'm not sure. I would hope not much, but I haven't taken the time to look at how repo2docker currently supports all the config files it already does.
Who can do this work?

Someone with familiarity with conda-lock.

We already have lock files for pinning the base requirements, though these aren't yaml files:
https://github.com/jupyterhub/repo2docker/tree/main/repo2docker/buildpacks/conda
Is this a different type of lock file?

@manics This might be a conda-lock version issue. The conda-lock format was unified in conda-lock v1.0.0 (c.f. https://github.com/conda/conda-lock/pull/124)

By default, conda-lock store its output in conda-lock.yml in the current working directory. This file will also be used by default for render, install, and update operations. You can supply a different filename with e.g.
conda-lock --lockfile superspecial.conda-lock.yml

It seems though, that yes, the format of what you have is different. Example:
https://github.com/jupyterhub/repo2docker/blob/8c32db99878fa3cd532f2b9ee107cfded058088a/repo2docker/buildpacks/conda/environment.py-3.11-linux-64.lock#L1-L10
compared to something like https://iris-hep.org/analysis-systems-env-nightlies/iris-hep-rc/3.11/conda-lock.yml
# This lock file was generated by conda-lock (https://github.com/conda/conda-lock). DO NOT EDIT!
#
# A "lock file" contains a concrete list of package versions (with checksums) to be installed. Unlike
# e.g. `conda env create`, the resulting environment will not change as new package versions become
# available, unless you explicitly update the lock file.
#
# Install this environment as "YOURENV" with:
#     conda-lock install -n YOURENV --file conda-lock.yml
# To update a single package to the latest version compatible with the version constraints in the source:
#     conda-lock lock  --lockfile conda-lock.yml --update PACKAGE
# To re-solve the entire environment, e.g. after changing a version constraint in the source file:
#     conda-lock -f iris-hep-rc/3.11/environment.yml --lockfile conda-lock.yml
version: 1
metadata:
  content_hash:
    linux-64: e002febb8b04300e80dded8f2b7dabb269ace11a83f98db20719007774f0f52c
  channels:
  - url: conda-forge
    used_env_vars: []
  platforms:
  - linux-64
  sources:
  - iris-hep-rc/3.11/environment.yml
package:
- name: _libgcc_mutex
  version: '0.1'
  manager: conda
  platform: linux-64
  dependencies: {}
  url: https://conda.anaconda.org/conda-forge/linux-64/_libgcc_mutex-0.1-conda_forge.tar.bz2
  hash:
    md5: d7c89558ba9fa0495403155b64376d81
    sha256: fe51de6107f9edc7aa4f786a70f4a883943bc9d39b3bb7307c04c41410990726
  category: main
  optional: false
...

Supporting conda-lock outputs would be... nice, but would likely require some guardrails, and blessing some "r2d knows best" conventions.
conda-lock itself hauls in... a lot of dependencies, so may not be a good candidate for the "base coat" environment. micromamba, already present, is certainly up to the task of consuming both formats... though pixi very well might end up "winning" for this use case.
As, ideally, it would replace (not change) the notebook environment, supporting the raw lock (in either format) would ideally be able to preflight before doing a still-expensive download by:

checking some marker that is compatible with the runtime (e.g. linux-64) in some non-cosmetic place

comments and filenames can't count
but really, the presence of e.g /linux-64/ in any URL would probably enough...

i don't think a fully /noarch/ environment is even creatable at this time for anything except a "dataset" environment

contain e.g. jupyterhub[singleuser] at a version that would be at least compatible with the hosting hub...

running micromamba install jupyterhub-singleuser could upgrade something in an undesirable way, even with a bunch of flags on it

The yml format directly supports dependencies from other package managers, like pip (and even other package manager managers like poetry and pipenv), while the @EXPLICIT format kinda half-supports them, but behind #s, so probably needs to be ignored entirely.
Thus far, there is no specific naming convention for A Well-Known Conda Lock File in a repo, as a number of "first-party" tools within the conda org don't agree on what the extension should even be:

the reference implementation (conda itself) does not (and might not ever) support the .yml format

conda env won't support an @EXPLICIT file, only conda create

by default, conda-lock generates lockfiles like conda-lock.yml or conda-{platform}.lock

both can be overriden, though the YAML format must end in .yml

constructor expects a .txt file for an @EXPLICIT (but has no guidance on the prefix)

it doesn't support the .yml format, even if micromamba is used as the solver, and would try to use it like an environment.yml

So, to tighten up the above as a recommendation:

while a file has not been selected, for each of the below opinions (in basically this order, assuming linux-64):
.binder/conda-lock.yml
.binder/conda-linux-64.lock
.binder/conda-linux-64.lock.txt
binder/conda-lock.yml
binder/conda-linux-64.lock
binder/conda-linux-64.lock.txt
conda-lock.yml
conda-linux-64.lock
conda-linux-64.lock.txt

if the file ends in .yml

and linux-64 is found in #/metadata/platforms/

and a member of#/package/ contains name: jupyterhub-singleuser

select this file

otherwise, if the file contains /linux-64/

and the file contains jupyterhub-singleuser

select this file

if no file is selected, fail

COPY {the file} /tmp/

micromamba env create --prefix {wherever/it/goes} --file /tmp/{the-file} && micromamba clean -yaf

Chiming in here with a user experience, leading to a question about the above recommendation. My goals are to keep only my project's dependencies in an environment.yml with minimal pinning, have some lockfile for protection against untested updates, and to not conflict with packages added by the conda buildpack. I do not understand how I can create or use a lockfile that is aware of the package constraints introduced in the conda buildback. Wouldn't the recommendation, which uses create rather than update, require me to include jupyterhub-singleuser and friends with all the repo2docker constraints? If it were update though, how/where/when could I invoke conda-lock on my environment.yml and repo2docker's environment.yml?
Aside: If not for some few packages that seem to need the notebook kernel to be the same as the environment running jupyterhub-singleuser, I would have used a separate environment for my project's kernel.


Native: tried calling StatusBar.styleDefault, but Cordova is not available. Make sure to include cordova.js or run in a device/simulator

Note: If you are having problems formatting your issue please refer to this article on using markdown in Github:
https://guides.github.com/features/mastering-markdown/
Note: for support questions, please use one of these channels:
https://forum.ionicframework.com/
http://ionicworldwide.herokuapp.com/
Note: for build related issues you can open up an issue on the ionic-app-scripts repo
https://github.com/driftyco/ionic-app-scripts
Note: for Ionic-Native related issues you can open up an issues on the Ionic-Native repo
https://github.com/driftyco/ionic-native
Short description of the problem:
What behavior are you expecting?
Steps to reproduce:
1.
2.
3.
insert any relevant code between the above and below backticks

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Which Ionic Version? 1.x or 2.x
Plunker that shows an example of your issue
For Ionic 1 issues - http://plnkr.co/edit/Xo1QyAUx35ny1Xf9ODHx?p=preview
For Ionic 2 issues - http://plnkr.co/edit/me3Uk0GKWVRhZWU0usad?p=preview
Run ionic info from terminal/cmd prompt: (paste output below)

Hello! While we appreciate you opening an issue with us i am going to close this issue and ask that you open a new one that has the issue template filled out please. Thanks for using Ionic!

It can still happen, it seems the cause are version incompatibilities:

New Issue 1380
Previous related issue: 467
Related workaround


2 DCO checks per PR

I created a PR (https://github.com/hiero-ledger/.github/pull/3) and recognized that we have 2 DCO checks/rules configured:

Is that expected / the wanted behavior?

@hendrikebbers DCO2 is in beta. DCO is the currently shipping version. Once DCO2 is out of beta, we can remove DCO


[SourceKit] Add test case for rdar://64230277

rdar://64230277 seems to already be fixed. Add a test case for it.

@swift-ci Please smoke test

@swift-ci Please smoke test Windows


Update incorrect doc

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

/release-note-none
/ok-to-test
/approve


[Feature request]: T8210 doorbell - Get RTSP Url to be able to start or get the video

Describe the solution you'd like
Hello
The T8210 doorbell, unlike cameras, does not let us redirect the RTSP stream to a NAS and therefore we do not have access to the RTSP stream to start it, or even just view it in third-party software like directly with Euft app.
Is there a way to get the T8210 doorbell stream URL and start it through the plugin ? If not, is there just a way to retrieve this URL?
Thanks

I can chime in as a consumer of this package. If RTSP is not supported by your device, you should either write your own library and generate RTSP address using P2P bytes or you can use home assistant and generate the URL there using custom integration. It is far from reliable but it is working to some extent


Switch to a pure STM core; remove concur dependency

Whoa! Would you be willing to give a one sentence motivation for this, and how it's intended to affect app developers?

I'm guessing it will make things a little slower but remove edge case bugs, which sounds awesome.

You're exactly right, the motivation was to remove edge case bugs and finally have a stable core to build on.
The bad news is this approach won't work and is completely and utterly broken and misguided and introduces even more edge case bugs :D Utter madness, this is super tricky to get right.
So don't use this commit, I'll have to revert it.

Haha, good to know! I'll wait to upgrade.


JCF Select dropdown not the same width as the select

When using the custom dropdowns for the JCF select they would sometimes not match up to the width of the select on the page. This seems to occur in a responsive design where the select is set to a percentage width. To resolve it I added the below to line 335 of jcf-select.js which makes the select on the page the same width as the custom dropdown.
this.fakeElement.css({
width: selectWidth
});
I then remove this in the hideDropdown function.
this.fakeElement.attr('style', '');

Hi, @NigelOToole !
JCF library tries to avoid inline styles on the fake select element so you don't have to worry about priority of your CSS rules vs inline html styles.
Responsive behavior can be achieved with CSS. For example you have:
<select class="foo">...</select>

Now you can control styles of custom select like this:
select.foo,
select.foo + .jcf-select {
    width: 50%;
}

Or you can use the class of your select element which is automatically copied and prefixed with "jcf-select-" by JCF library:
.jcf-select-foo {
    width: 50%;
}

Will this work for your case?

Hi
Thanks for the reply and I can understand trying to avoid inline styles but
this is the only way I could always get them to line up.
I have already tried using styles as suggested but this didnt work. The
strange thing is that my developer tools in firefox are saying all the
element, the native select, the jcf-select and the jcf-select-drop have the
same pixel width but the edges dont line up untill I added the inline
styles.
Regards,
Nigel
On 23 June 2015 at 17:11, Sergey<EMAIL_ADDRESS>wrote:

Hi, @NigelOToole https://github.com/NigelOToole !
JCF library tries to avoid inline styles on the fake select element so you
don't have to worry about priority of your CSS rules vs inline html styles.
Responsive behavior can be achieved with CSS. For example you have:
...
Now you can control styles of custom select like this:
select.foo,select.foo + .jcf-select {
width: 50%;
}
Or you can use the class of your select element which is automatically
copied and prefixed with "jcf-select-" by JCF library:
.jcf-select-foo {
width: 50%;
}
Will this work for your case?
—
Reply to this email directly or view it on GitHub
https://github.com/w3co/jcf/issues/6#issuecomment-114559606.

Ok. Are you testing on the retina display?
Maybe you could provide a jsfiddle, so I can reproduce the issue?
BTW, you can try fakeDropInBody: false option which will put the drop inside the fake select element and it will have the same width as the container without any inline styles.

Need more information to reproduce the issue.

Having the same issue in Bootstrap 3. It is caused by jQuery outerWidth() behavior, it rounds the actual width. I managed to solve it in jcf.select.js, function `repositionDropdown' (line 309):
selectWidth = this.fakeElement.outerWidth(),

replace it with
selectWidth = this.fakeElement[0].getBoundingClientRect().width,

(see stackoverflow to take care about browser support)

If you wish, I could make a pull request (browser-safe version of this comment).

Ok, so .offset() already returns floating point value and only width is calculated with rounded values. I think this is the only place that needs to be updated in jcf.select module.
@nikolai-katkov will be waiting for your PR ;)


Add box2d type

I am trying to do a select st_envelope(...)::box2d and I get the error:
* (Postgrex.QueryError) type `box2d` can not be handled by the types module Test.PostgresTypes

We don't have any support for box2d yet. I just did a quick search on trying to figure out how what the specs are for it but haven't found anything yet. But yes, support should be added


Differentiating between idToken acquired on sign in vs idToken acquired silently/renewed

Library

[x]<EMAIL_ADDRESS>- 0.1.4

Browser

Chrome - Version 78.0.3904.108

Description
Hi Team,
I am fairly new to the MSAL-Angular realm and I have this question of differentiating between idToken acquired on sign in vs idToken acquired silently/renewed. Are there any identifiers in the idTokens themselves that can indicate that the token acquired, is either a fresh one or a renewed one. Some internal operations in our app depend on the token types and we wish to know if there are any such indications in the idTokens themselves.
Upon some digging and debugging, when I subscribe to 'msal:loginSuccess' event, the payload shows tokenType:'id_token' which can be confirmed via the HTTP request containing response_type parameter set to id_token when signing in for the first time.
The same payload when token is renewed silently, the payload shows tokenType:'' but the HTTP request contains response_type parameter set to token.
What I was also curious to know about is are there events to subscribe to, similar to 'msal:loginSuccess' which i can use to identify whether the token was issued during sign in or renewed silently
Any info on this can be really helpful

Hi @sameerag @jasonnutter Thabks for your inputs guys. I did manage to find out another easy way to identify a new token from renewed token
The objectIdFromSession when exposed via custom policy in B2C, it will come up as false if it's a fresh token and will come up as true if it is a renewed token

Thanks @NareshKumarM. Closing this ticket.


Two volto sites in one domain

I want to host two volto sites in one domain.
For example, the First site root is /, second site root is /sub.  But I don't know how to host the /sub folder. Can I set the Path?

@terapyon This may help https://github.com/plone/volto/pull/3190

thank you! I will close this issue soon


[BUG] "this.provider.disconnect" seems faulty

I am using Rainbowkit + Nextjs (typescript). There is a problem that keeps occurring. After some hot-reloading of the page, an error keeps occurring
index.es.js:99 Uncaught (in promise) TypeError: this.provider.disconnect is not a function

After reloading when this error occurs, the page shows that you are not connected to the internet (which there is no need for, I am developing locally).
I have tried reinstalling all modules. But it did not work.
Any idea what the reason is?

Gm, this was patched in https://github.com/WalletConnect/walletconnect-monorepo/releases/tag/2.17.2
Please let us know if you can still reproduce in latest Rainbowkit 🙏


fix serialize hardBreak node type undefined

Crash after typing hard break in a table (non-standard Markdown table) cell.

Fixed

This tweak is due to prosemirror-markdown checking the name of the mark (https://github.com/ProseMirror/prosemirror-markdown/blob/5e454a9b4d59c14a5826e112813e78b6b7325668/src/to_markdown.ts#L280)
I'll see if I can fix this without breaking something else.
Please note that I do not recommend using this package with complex tables. Default tiptap HTML fits better.

Thank you, the fix has been released in 0.6.1.


Quoting relations and columns (discussion)

By default relations and columns are quoted by double quotes " in dbt. What do you think about setting the quoting to [] which is more T-SQL like?

@ericmuijsvanoord , quoting character in dbt is a single character. dbt cannot support [ and ] characters because it has different starting and ending characters. Let me take a look into this to see if there is way to support a approach.

@ericmuijsvanoord , The double quotes standard is used in dbt-core and adapter implementation way too many places. Standardizing that would not be a small effort and I am putting this on back burner.

also I want to tie-in an issue that I opened over 3 years ago
related: https://github.com/dbt-msft/dbt-sqlserver/issues/91


Inconsistent battery energy data

Describe the bug
I have two inverters, a SE10K-RWB (hybrid) and a SE10K (not hybrid). A SolarEdge battery is connected to the hybrid inverter. The energy meter is a SE-MTR-3Y-400V-A.
I have read that some battery energy meters regularly reset to 0 and others are ever-increasing.
In my installation, I get sparse readings which randomly increase and decrease:
The other energy meters look fine (grid import/export are continuously increasing lines).
Expected behavior
I expect the energy meters to increase over time so that I can extract a daily min/max and compute the charged/discharged energy on a daily basis.
Screenshots

Diagnostic File
config_entry-solaredge_modbus_multi-7b87ebcb4b1fe3c518722fe6c09782cf.json
Debug logs
No response
Home Assistant Version
2024.5.5
solaredge-modbus-multi Version
2.4.15
Installation Type
Container
Read the Instructions

[X] My configuration follows https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration
[X] I have read the Known Issues https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues
[X] This issue is not about a template error (do not report template errors, read https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Template-Design-Notes)

Additional Context
No response

This is already documented in Known Issues. Only SolarEdge can fix battery energy.

I remember seeing someone use an Integration helper (Riemann sum integral sensor) to approximate battery energy from unreliable data. You could try that. I don't have a link though since I don't remember if I saw it in github discussions or on the HA forums.

In that case, I apologize for asking about a well-known issue. If you don't mind, I'll add the SolarEdge Home Battery 48V to the list of known problematic products (it's separate from the high-voltage Energy Bank).
I've createdd a support ticket but don't hold my breath. In the meantime, computing a Riemann sum integral from the DC power measurement seems like a suitable workaround (compromising precision, of course).


resque-web has schedule and delayed tabs , delayed tabs shows delayed jobs but scheduled tab doesnt show

I am using resque-scheduler
everything is working fine , jobs are scheduled as i run resque:schedule rake
they are worked upon as in run resque:work . so my functionality is achieved
now i wanted to see scheduled jobs in resque-web UI however i am having an issue
I have resque_config.rb in Rails root
contents
require 'resque-scheduler'
require 'resque'
require 'resque/scheduler/server'
Resque.redis = "localhost:6379"
Resque::Scheduler.dynamic = true
i do this
bundle exec resque-web -f -p 9292  ~/Documents/Promise-API/coms/resque_config.rb
where "/Documents/Promise-API/coms/" my Rails.root
but schedule jobs are still not shown .
alternatively
if i do
Rails.application.routes.draw do
mount Resque::Server.new, :at => '/resque'
end
schedule jobs are still not shown , only delayed jobs .
i need this a bit urgently
Any help will be appreciated

See https://github.com/resque/resque-scheduler/issues/541, you must also load the static schedule for the scheduler web to read since it is not persisted in Redis.


Multi-tenancy

Summary

Closes #16
Changes

Bump v1 to v2beta1
Add multi-tenancy

Notes for Reviewers

Check all commits except the first one to see a diff from v1

When approved, we probably want to bump this straight to v2


Update dependencies to use NPM for @astropub/md

Describe the pull request
Why
When installing the package with Yarn, it fails to resolve gitpkg link in the @astropub/md dependency. Apparently that's due to Yarn likely not being able to resolve query params.
How
Looks like the necessary changes are already published in the NPM version of the package, so this small update replaces the gitpkg link with an NPM link.
Screenshots
Not applicable

My apologies, this PR totally slipped through my notifications and I randomly saw it today while fixing unrelated issues in another branch.
As I was in the process of fixing other issues preventing to build this PR and in order to get this out quickly, I've used your fix in my branch and co-authored it with you.
This should be now fixed in v0.4.0 that I've just released.

No worries, at all and thanks for all your work on this! Just FYI, I've merged a new update to the @astropub/md that's in v0.4.0 dependency that will make it work with Astro 4: https://github.com/astro-community/md/pull/11

Just FYI, I've merged a new update to the @astropub/md that's in v0.4.0 dependency that will make it work with Astro 4: astro-community/md#11

Wow, that's an amazing news, thanks a lot. This means that when the upstream Starlight issue preventing the update is fixed, we won't hit again this Yarn issue by just using v0.4.0 🎉
Note: it looks like something is wrong with the https://github.com/astro-community/md repo as it now contains the content of the https://github.com/astro-community/context repo. I'll open an issue.


Feat/collapsible if else

Issue
#8
Description

Lint implementation
Fix implementation
Tests added

hey @0xLucqs comments addressed!

For the nested ifs change on the linter your suggestion was generating some compilation issues, so I fixed it in another way.
For the complex fix, I changed the approach I was using (with the text) and instead started using the tree. This is working good, I just noticed that there is a small indentation issue with the fix on the else if clause. Do you have an idea of how can I approach that small issue?

let's ignore complex indentation problems it's a nightmare

let's ignore complex indentation problems it's a nightmare

Got it! Then the PR is ready for review.

@0xLucqs is there any action needed from my side to make the ci/cd run correctly?

Yep you need to run cargo fmt

Yep you need to run cargo fmt

done! @0xLucqs

@all-contributors please add @lindsaymoralesb for code and test


docs: remove module-metadata.json and commitlint.config.js

/run pipeline

/run pipeline

:tada: This PR is included in version 2.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[CMake] CMake Gardening Project: Part 3

This PR is yet another entry in the CMake Gardening Project (TM), which cleans up the SwiftManpage.cmake module to conform to proper CMake styling conventions and use the module import guard pattern (similar to header guards in C). This PR is a non-functional change.
Related to #16982
rdar://40764844

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - afae647e639e61895ffbd1a14100f74988cbdb19

@swift-ci please test


refactor(SpriteImage): Use image tag & transform property

Issue
#210
Details
Use image tag & transform property instead of background property enhancement

Coverage decreased (-0.2%) to 92.852% when pulling 3a302da0fe8153bfa4e8e3902a2a166fccb4af85 on jongmoon:SpriteImage#210 into 6adcc218507258844050137c9145bdfe5f336abe on naver:master.

LGTM


Updating MRTK requirements to specify 2018.4.x instead of 2018.3.x

Updating MRTK requirements to specify 2018.4.x instead of 2018.3.x

Docs Build status updates of commit 26e2170:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mrtk-getting-started.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Chat fixes

Closes #352

PM recipient not found doesn't play the SFX

I couldn't replicate this. The SFX played for me

Public and Group chat always shows speech bubble over the main character

This was a bug where we were always overwriting the render character with the main character. Now we always find one in _characterRendererProvider.CharacterRenderers with the matching player id

Admin chat does not play sfx when you send a message, only when you receive one

Added sound effect to chat controller when sending message

Group chat does not play sfx when you are on a different map as the sender

We were only looking at party members in the local map repository instead of the party repository before. Now it shows messages from members no matter where they are in game.

PM tab [x] button doesn't work in resizable display mode

I believe this was a render order bug? Seemed like some kinda z-index kind of thing. Adding the Tab clickable area before the close buttons fixed it. I also adjusted the dimensions a bit to match the gfx.

Closes #352

PM recipient not found doesn't play the SFX

I couldn't replicate this. The SFX played for me

I was having a bunch of issues with PMs, so it might work inconsistently. The chat code was some of the first code I rewrote and it has not aged well.

Can you add some details to the PR description about why the fixes work? You have the "what" in the commit history, but I'd like a clear line between "I changed this" and "this is the effect"

@ethanmoffat PR description updated and can you show an example of how you'd replace the FirstOrDefault usage?


Add click-based verfiications

Adds tests to verify all of the properties/attributes/states by exercising clicks on all of the things.  This should really merge after #28 if possible imo so they all pass :)

Shout out to Lajja Shah asking the questions and doing initial work for these tests :)


On iOS 11 this library doesn't work anymore.

Hi,
The library doesn't work anymore on iOS 11, when a table is pulled to refresh the spinner doesn't show and when the refresh is done all the table goes under the navigation bar.
Thanks

Having the same issue.. But these settings magically makes it work:

self.navigationController?.navigationBar.isTranslucent = false
self.navigationController?.navigationBar.setBackgroundImage(UIImage(), for: .default)
self.navigationController?.navigationBar.shadowImage = UIImage()

I update the lib for swift 4 it's amazing here :D

Working for me if I use SWIFT_VERSION = 3.2

+Bragegs solution works, thanks for sharing

I have forked one and fixed this problem, update for iOS 11 safeArea & Swift 4.2. https://github.com/catofdestruction/DGElasticPullToRefresh


Sort by estimate after due date and priority

This is useful when trying to decide between tasks due on the same day
and of the same priority. My preference would be to do the longest one
first.

I think this one's good-to-go.


Update bruno-cli readme changelog link Fixes #1769

Description
Point the bruno-cli readme changelog link to the bruno release page as suggested in the readme file itself
Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[ ] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Fixes #1769

Merged!
Thank you @patest-dev !


Conflict hotkeys

I have a conflict with 'ALT + o'.
How can I turn off keyboard shortcuts or change it in plugin?

You mean CTL+ALT+o for "Open from Cloud"?
Looks like this is hard-coded: https://github.com/Kyrodan/KeeAnywhere/blob/ebeb344177353ad663e1d0270920f7ca057b737c/KeeAnywhere/KeeAnywhereExt.cs#L99
So no way to turn off or change.

CTRL+ALT+o opened "Open form Cloud", and ALT+o to.
I can't find my record where I used a diacritical character like 'ó'


Browse nomenclature/taxa: problem with separation in cited names and citations

The more citations the more confusing this gets. While experimenting in the OSF sandcastle I accidentally created (wanted to test something else) a confusing situation with just two citations. Only the page numbers indicate that the references are chronologically inverted.

Would it be possible to offer the selection of an integrated dispay form where cited names are directly listed in chronological order with the corresponding references? The more citations a particular taxon has, the more cumbersome it becomes to jump up and down to look up the references for the cited combinations/relationships.

@typophyllum I had the same problem. Just yesterday pushed a change where the references are highlighted and with the mouse over, the full source is displayed in a popup. Not on the production yet.
Does this solve the issue?

For citations, you have to provide the publication date for each source, this keep the order of the sources.

Yes, nice idea. This could possibly solve the issue indeed. Of course the user would need to know that mouse-over provides this information.
(In OSF it would be an close-to-impossible amount of work to investigate publication months for thousands of references. Perhaps @LocoDelAssembly could extract a list of same-author-and-year references to add the data after the migration. Wouldn't solve the issue of same year/different authors for the sequence of cited names though. It would be better to somehow import directly the curated sequences from OSF.)


Fix cleaning up recently closed streams

Ever since 16dec9f2c44d3a525a49fe92bc15c7b79e9de097 in 2018
@streams_recently_closed cleanup was broken.
to_delete contains hash of { stream_id => time } so in
to_delete.each do |stream_id| stream_id is actually array of [ stream_id, time ].
This leads to the same memory leak as there was before the first cleanup
but also adds heavy CPU usage when thousands of streams are being
checked on every stream close.
Since 15s delayed cleanup was intended but actually infinite delay was
added so 15s was never tested in production code and thus might be not
enough.
This change also improves performance of searching streams to delete by
relying on the fact that Ruby Hash is ordered and so once fresh stream
was met we can stop searching.
Also minor performance and memory improvement by storing only timestamp
instead of Time object.
Extracted this part of the code to a separate function for test
convenience.

Coverage increased (+0.09%) to 97.28% when pulling e4a6980c57e27296dadd3576687a8f600bccea84 on crazyshot:master into d52934f144db97fc7534e4c6025ed6ae86909b6a on igrigorik:master.

Coverage increased (+0.09%) to 97.28% when pulling e4a6980c57e27296dadd3576687a8f600bccea84 on crazyshot:master into d52934f144db97fc7534e4c6025ed6ae86909b6a on igrigorik:master.

Actually I think that the cleanup shouldn't be related to the :close event and should be triggered by an external timer every second, this way even if there won't be any stream close it will still do the cleanup. But I wasn't sure it's safe to do it with multithreading and not sure it can be done via already existing Emitter events. Maybe on(:frame) with time throttle could do the trick?

Hi @igrigorik, will you merge it?

Thanks again for the patch!

@igrigorik Hi. Do you have a plan when to release a new version?

Sorry about the delay, 0.10.2 should be live now!


Enable "open with code" feature by default in msstore build

Right now, these option are not enabled by default:

And you cannot enable this options while installing vscode from msstore as installation is silent.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!

@joaomoreno can i ask why this can't be enabled for msstore build?


Utah County Data

From reviewing the COVID-19 Data file it appears that many Utah counties have Zero for COVID-19 cases & deaths.
The COVID-19 Map (and Status Reports) also displays Zero for many of these counties.
The Map FAQ has a comment that some Utah counties are banded together to protect identities of individuals. Although this county data seems to be publicly available on Google Charts.
Are there any plans to include this county level data in the Data file and Maps?
Alternatively, should the Zeros be removed from the Data file and Map?
Data File
Examples can be seen for Utah counties Cache and Washington,  both with population > 100,000
https://raw.githubusercontent.com/govex/COVID-19/master/data_tables/JHU_USCountymap/df_Counties2020.zip
Maps & Status Report
https://coronavirus.jhu.edu/us-map
https://bao.arcgis.com/covid-19/jhu/county/49005.html

We've resolved this at our end by removing the Zero records and creating a new spatial file that's a hybrid of counties and the banded together counties for Utah (and Massachusetts).
However, I've left this open for your review - as this seems to be relevant for other users of the data.
For example, the JHU Map appears to have the same issue with Zeros (for COVID-19 cases, deaths, rates) for many Utah counties (refer attached image for Confirmed By Population.

We've resolved this at our end by removing the Zero records and creating a new spatial file that's a hybrid of single counties and the banded counties for Utah (and Massachusetts).
However, I've left this open for your review - as this seems to be relevant for other users of the data.
For example, the JHU Map appears to have the same issue with Zeros for many Utah counties for COVID-19 cases and deaths. The following image of the JHU Map demonstrates this for Weber County, Utah, with 'Confirmed by 100k Population' = 0.

The county data file also seems to have an issue for recent months with Zero new Cases/ Deaths for Nebraska and Zero new Deaths for Florida. This can be seen when displaying only the more recent data as per the following maps.
Cases Past 2 Months (0 = yellow, 1-4 = orange, 5+ = red)

Deaths Past 2 Months (0 = yellow, 1-4 = orange, 5+ = red)

These maps also show the use of Banding to resolve the Zero issue for Utah and Massachusetts (as discussed in prior posts for the single/banded counties). However, we’re not able to resolve the Zeros from our end for the recent data for Nebraska and Florida. Any feedback you can provide here would be much appreciated.
Also, many thanks for all the work you’re doing on these datasets.


No data using DF_RawStreams

Following instructions from tutorial I get the following after pressing 'Start' button:
Device connected
Streaming...
Stopped
No files are generated and no camera images are visible.
Running on Windows 8.1 64 bit. Camera images are visible in other Intel Realsense SDK apps.
Any ideas?

hi, what is the version of your Realsense SDK?

I got Build Number: <IP_ADDRESS>777 here:
https://software.intel.com/en-us/intel-realsense-sdk/download

yeh, there have some problem with the 5.xx SDK version.
I use the 4.xx SDK version for now.
Maybe you can try 4.xx version first.

I tried version 4.xx of the SDK in combination with version 1.3.xx of the depth camera manager (Also tried 1.2.xx, but this didn't work for me).
I still get the same behavior (Device connecteed streaming..., stopped. No image visible and no files generated). Maybe the debug logs can help:
'DF_RawStreams_d.exe': Loaded 'C:\Program Files\Common Files\Intel\RSSDK\v4\bin\x64\libpxcpowermanager.dll', Cannot find or open the PDB file
'DF_RawStreams_d.exe': Loaded 'C:\Windows\System32\msxml3.dll', Cannot find or open the PDB file
'DF_RawStreams_d.exe': Loaded 'C:\Windows\System32\urlmon.dll', Cannot find or open the PDB file
'DF_RawStreams_d.exe': Loaded 'C:\Windows\System32\iertutil.dll', Cannot find or open the PDB file
'DF_RawStreams_d.exe': Loaded 'C:\Windows\System32\wininet.dll', Cannot find or open the PDB file
'DF_RawStreams_d.exe': Loaded 'C:\Windows\System32\userenv.dll', Cannot find or open the PDB file
First-chance exception at 0x00007ffc99ab8b9c in DF_RawStreams_d.exe: 0xE0000001: 0xe0000001.
First-chance exception at 0x00007ffc99ab8b9c in DF_RawStreams_d.exe: 0xE0000001: 0xe0000001.
'DF_RawStreams_d.exe': Loaded 'C:\Windows\System32\wintrust.dll', Cannot find or open the PDB file
'DF_RawStreams_d.exe': Loaded 'C:\Windows\System32\crypt32.dll', Cannot find or open the PDB file
'DF_RawStreams_d.exe': Loaded 'C:\Windows\System32\msasn1.dll', Cannot find or open the PDB file
The thread 'Win64 Thread' (0x1298) has exited with code 0 (0x0).
The thread 'Win64 Thread' (0x1624) has exited with code 0 (0x0).

Are you able to view the depth/rgb stream using any of the other sample apps? I've had issues with certain computers where the camera disconnects as soon as I try to access the depth stream. This is possibly because the USB port doesn't provide enough power. You could also try an externally powered USB hub if this is the case.

Ok, I've got it working.
Power supply was indeed the problem. USB 3.0 port with 100 mA should be enough, but on some hardware I found it was not. External hub did not work for me. See also discussion here:
https://software.intel.com/en-us/forums/topic/542101.
In the end I switched to another laptop.
I installed the 4.xx version of the SDK and the 1.2.xx version of the depth camera manager.
Maybe you can illuminate some of the process happening in the app:

Are there requirements for image used in the Raw Streams app? e.g.  should the image be static?
What exactly is stored in the bin file? With 2.4 MB per file and 2047 files, this seems a lot of data.

Maybe it's good to update the readme with some of these questions and installation instructions for the SDK, etc. I'd be happy to do this.

thank you.
If you happy to do this, you can fork this repo, and modify README.md file, then create a pull request. I will merge it.
I will write some detail about the uvmap file.

Since Readme is now updated, I'll close the issue.


Support Python 3.12 runtime

Expected Behavior
Similar to #170 (3.10) and #205 (3.11), would be awesome to have support for Python 3.12 runtime :).
Actual Behavior
At the moment, it is not supported so the layers got dropped because 3.12 has no match in constants.ts.
Specifications

Datadog Lambda Layer version: v1.10.0

Stacktrace

Hey @PierreKiwi, thanks a ton for pointing this out. I've opened a PR https://github.com/DataDog/datadog-cdk-constructs/pull/244.

Thanks a lot @purple4reina !

Closing due to latest release.


Matching for unknown label does not work

Given the following test
  test("Match on unknown label") {
    // Given
    val given = TestGraph(
      """
        |(:Person {firstName: "Alice", lastName: "Foo"})
      """.stripMargin)

    // When
    val result = given.cypher(
      """
        |MATCH (a:Animal)
        |RETURN a.name
      """.stripMargin)

    // Then
    result.records.toMaps should equal(Bag())

    result.graph shouldMatch given.graph
  }

I get the following error:
Did not find slot for a:Animal :: BOOLEAN
org.opencypher.spark.api.exception.SparkCypherException: Did not find slot for a:Animal :: BOOLEAN

Fixed by #199


add increment/decrement selections command (no interaction)

I added the command that like "Increment Selection" extension on Sublime text.
https://github.com/yulanggong/IncrementSelection
Because I could not found a extension like "Increment Selection" in vscode extensions.

Thank you for PR and sorry for late response.
It looks same as inputted only '1' in command palette.
Unfortunately, I hadn't used IncrementSelection, please tell me the difference of these behaviors.

Thank you for your reply.
As you said, IncrementSelection is same behavior as inputted only '1' in command palette.
However, it requires only one key input(Ctrl+Alt+i). Well, it's just that... (For me it is convenient.)
Please ignore this PR if you do not like it.


TypeError: __init__() got an unexpected keyword argument 'normalizations' in pyleecan/Tutorials/tuto_Simulation_FEMM

Hi,
Thanks for building this amazing project,
The issue occurs while I try to running the jupyter-notebook tutorial (tuto_Simulation_FEMM),
it was work until run
rot_dir = simu_femm.machine.stator.comp_rot_dir()
it will got an error
TypeError                                 Traceback (most recent call last)
<ipython-input-4-230e2e5aa176> in <module>
     28 I0_rms = 250/sqrt(2)
     29 felec = p * simu_femm.input.N0 /60 # [Hz]
---> 30 rot_dir = simu_femm.machine.stator.comp_rot_dir()

c:\python37\lib\site-packages\pyleecan\Methods\Machine\LamSlotWind\comp_rot_dir.py in comp_rot_dir(self)
     20     # Compute unit mmf
     21     MMF, _ = self.comp_mmf_unit(
---> 22         Nt=20 * p, Na=20 * p
     23     )  # 20 points per pole over time and space is enough to capture rotating direction of fundamental mmf
     24

c:\python37\lib\site-packages\pyleecan\Methods\Machine\LamSlotWind\comp_mmf_unit.py in comp_mmf_unit(self, Na, Nt, freq)
     59         symmetries={"period": per_a},
     60         values=angle,
---> 61         normalizations={"space_order": self.get_pole_pair_number()},
     62     )
     63     Phase = Data1D(

TypeError: __init__() got an unexpected keyword argument 'normalizations'

How can I fix it?
thanks for your help.

Hello Mark,
I guess you have to upgrade your SciDataTool.
Best regards, Sebastian

Hello Mark,
I guess you have to upgrade your SciDataTool.
Best regards, Sebastian

Hi  Sebastian,
it's work after I upgrade SciDataTool package.
thanks for your help

Hi  Sebastian,
it's work after I upgrade SciDataTool package.
thanks for your help


Describe app capabilities, features and security implications in README

Add feature list, permission list (see #69 ) and security implications to the README

Update the current dost to explain things in detail including screenshots etc.

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Added the ability to configure JVM options (i.e. setting memory heap size)

Currently, there is no way to configure JVM settings for Nexus with this module.
An update has been added to allow setting various JVM settings. Example hiera below:
nexus::vmoptions :
  jvm-xmx:
    match: '^-Xmx'
    line: '-Xmx2703M'
  jvm-xms:
    match: '^-Xms'
    line: '-Xms2703M'
  jvm-max-direct-memory-size:
    match: '^-XX:MaxDirectMemorySize'
    line: '-XX:MaxDirectMemorySize=2703M'

This effectively configures: "${nexus_root}/${nexus_home_dir}/bin/nexus.vmoptions" using file_line from the Puppet standard library.

Hi @pranav.
Have you had a chance to review this Pull Request?
It would be great to have your feedback on this as I am sure it is a very useful addition.
Thanks

@leewilson86
Thanks for contribute. I'm looking forward to seeing this feature in master

@pranav and @nevoff89 any chance of this getting merged?

@tykeal is this project now dead?

@leewilson86 wow... I just saw this comment while cleaning up my mailbox (shows how bad my personal mailbox has gotten).
I dunno why you're asking me if this project is dead. I have no control over the hubspotdevops repos...
I would almost hazard a yes though given that there has been no code merges since 2018.

https://github.com/hubspotdevops/puppet-nexus#-no-longer-maintained-

@kenbreeman well, I guess that answers the question from @leewilson86
Thank you for having made a good module, sorry you aren't maintaining it anymore but I totally get that!

This project is dead. So I am closing my PR. I have a fork which has this solution for me.


fix: transform all styles, not only first block; ensure font-weight property is stringified

closes #20

Thanks @davidgruebl


fix(twitch): no longer needed note

🔧 What does this fix? 🔧
the previous commit fixed the shadow problem with latte on dark mode, this note is no longer needed
🗒 Checklist 🗒

[x] I have read and followed Catppuccin's contributing guidelines.
[x] I have updated the version appropriately in the ==UserStyle== header of the catppuccin.user.css file.

@isabelroses


Screenshot of unetbootin isn't from Ubuntu

In the Ubuntu installation directions section, the screenshot of Unetbootin isn't actually from Ubuntu

Yes, but it is their "official" screenshot.

Yeah, but it's not a screenshot from Ubuntu, which is what the section claims