Contained list versus Structured List

This is a summary of the various conflicting information and considerations between the documentation of Contained List versus Structured list (as well as how they fit on the spectrum between List and the single selectable row version of Data table).
It is drawn from comments in the PDF reviews of these topics, which have more detailed comments and should be reviewed:

Structure list reviews
Contained list review

The high level themes are as follows:

structured and contained lists, despite having very similar origins (data table 'lite') and intended uses, have unaligned variants
both of them deviate significantly from the presentation of selectable data tables, and the reasons are unclear
the contained list has 2 kinds of search mechanisms; the structured list has none. Yet they both offer single-select versions
both are considered 'read-only' but both also allow deletion; so maybe it would be better to call them something else like "uneditable" or "unalterable" data?

Unaligned variants
The structured lists are divided by function (Default, Selectable) while the contained lists are divided by visual style differences (On-page list, Disclosed list).
The contained lists have dedicated sub-sections listing each these interactions:

clickable rows
inline actions
interactive elements
search and filtering
scrolling

Structured list has a simple Interactions heading with a few 'rules' listed under "Selectable structured list" (few if any of which are given for contained lists):

– Only one item can be selected from the list.
– By default, one option should be selected.
– If you need to select multiple items, use a data table.
– When the user selects an item from the list, the selected row will appear
with the icon.

I infer that both list types share most if not all these features -- and where they do not, those become some of the distinguishing features between them. The distinction (and shared features) should be much more clearly indicated for both components.
I think consistent variant names between them (where they’ll  share similar qualities) would really help. For example, 'Read-only' and 'Interactive' (or 'Selectable' or 'Actionable' -- or possibly those are additional variants, where warranted).
I also wonder if the components should be renamed to make them easier to compare (e.g., List-simple, List-contained, List-structured). Obviously the organizing/naming of the components within Carbon has quite a bit to do with how important it is seen to position them within the List <> Data table continuum. (Also bearing in mind that Data table--which lists variants of Default, Selection and Expansion--fails to add in Sortable and other interactions which could themselves be variants).
List versus table row selection indicators.
I already have an issue open about Structured list selection indicators, https://github.com/carbon-design-system/carbon/discussions/11506 . All the concerns there seem to apply to selectable contained lists as well. There was a proposed WCAG addition to ensure that elements that were operable had a visual affordance before the user began interacting with it (i.e., users should understand component operation without having to 'accidentally' discover it based on hover, etc). Unfortunately wording could not be proposed to make this predictably testable, but the need is real.
I encourage Carbon to adopt a consistent single-select model, based on the radio-button group behaviour.
[to be continued]

Unaligned variants
The structured lists are divided by function (Default, Selectable) while the contained lists are divided by visual style differences (On-page list, Disclosed list).
The contained lists have dedicated sub-sections listing each these interactions:

clickable rows
inline actions
interactive elements
search and filtering
scrolling

Structured list has a simple Interactions heading with a few 'rules' listed under "Selectable structured list" (few if any of which are given for contained lists):

– Only one item can be selected from the list.
– By default, one option should be selected.
– If you need to select multiple items, use a data table.
– When the user selects an item from the list, the selected row will appear
with the icon.

I infer that both list types share most if not all these features -- and where they do not, those become some of the distinguishing features between them. The distinction (and shared features) should be much more clearly indicated for both components.
I also wonder if the components should be renamed to make them easier to compare (e.g., List-simple, List-contained, List-structured).

Search/FIltering mechanisms
The contained list has 2 kinds of search mechanisms; the structured list gives none. Is that accurate, or does the structured list also have search/filtering capabilities, just not specified?
I note there is a stated limit of 25 items on structured list. Is that why there is no filter mechanism? Perhaps contained lists have an unlimited number? I don't really understand the use case for this.

'Read-only' versus 'deletion'
Both components offer single-select versions. Both are considered 'read-only' but both also allow deletion. Normally, you cannot do anything to read-only material. For example, here's a first hit on searching "read-only data features":

Read-only is a file attribute which only allows a user to view a file, restricting any writing to the file. Setting a file to “read-only” will still allow that file to be opened and read; however, changes such as deletions, overwrites, edits or name changes cannot be made.

So I feel like maybe Carbon needs another term. I think the idea being discussed is that the information cannot be edited or altered, but list items  can be deleted? It might be better to call them something else like "uneditable" or "unalterable" data? I don't have any great suggestion, except to expand on the intended interaction in the usage sections.

This comment may become its own issue (or part of a future issue I'll likely open on Contained list) but based on a slack with @janhassel and @andreancardona, I thought I'd better add a bit of that conversation here.

Hey folks. Quick question irt to the a11y discussion around ContainedList. I’ve been trying to follow the conversation through the GitHub issues but am unsure if I get the whole picture.
https://github.com/carbon-design-system/carbon/issues/13950
In this issue Andrea mentioned that the semantics should be switched to a table. Are you only talking about the example with the column-style or the entire component? Because from Taylor’s comment in https://github.com/carbon-design-system/carbon/issues/13849#issuecomment-1653981330 it sounds like the entire component should be refactored from a list to a table and I wonder how to properly implement use cases like these then where the individual items have different structures?

Andrea Cardona
7:02 AM
Hey
@jan.hassel
that's a good question! I'm not sure - we haven't looked at this specific use case - I'll have to talk to Gower and Taylor more about this - thank you for bringing it up!

Michael Gower
7:40 AM

Wow, that’s a pretty interesting interaction! From what I see, it has the following- disclosure pattern (which isn’t a surprise in a disclosed list, I guess!)
superfluous heading. Unless there’s a situation where multiple different kinds of lists are  stacked in this dropdown, wouldn’t the name of this button be “Tasks” with no need to list that in the disclosure?
Non-interactive section names (Active, Failed), which interestingly enough would appear to be status categorizations, and so may appear dynamically? I also wondered if something that’s run is really “Active”, or if there’s going to be an additional category called “Successfuly” or something
second (dynamic?) line for one item (“Data task”)
real-time information on status (“Processing” plus blue animated icon)
Icon-based outcome status (green tick mark, red fail)
Ability to delete/remove items from list?! (icons at end of each list item)

I realize that this visual is on the Usage page. In hindsight, I ’bleeped” over some of these examples when I was doing my review, because a) the particulars are not documented on the Usage page, b) there is no such implementation on storybook, c) experience has led me to spend less time on non-interactive examples. So my apologies I’m only flagging these things now. We could probably spend quite a bit of time on some of these points, so maybe I should transfer this into part of the issue I opened on Contained lists…?
In regard to Jan’s statement, IMO these single-column lists (disregarding the action icons)  don’t need to be constructed as tables. I suspect that the disclosed contained lists, overall, are less beneficial to be tables. It just seems a bit problematic to me at a gut level for a screen reader to navigate a table in a disclosure pattern, where the arrow key interaction of table navigation is likely to conflict with the arrow key navigation of the  dropdown items.


Fix namespaces.

Adding a composer post install script to fix namespaces in vendor/symfony/var-dumper/Cloner/AbstractCloner.php.
Fixing https://github.com/spatie/wordpress-ray/issues/24

Thanks!

Thanks!

Why don't you simply use mozart for prefixing namespace?

Why don't you simply use mozart for prefixing namespace?

@szepeviktor Because I simply don't know Mozart (I'm not into WordPress). If this can be fixed in a a simpler way, feel free to create a PR that fixes the problem.

@szepeviktor Because I simply don't know Mozart (I'm not into WordPress). If this can be fixed in a a simpler way, feel free to create a PR that fixes the problem.

I manage WordPress installations with Composer, so I don't know Mozart :)

I manage WordPress installations with Composer, so I don't know Mozart :)


What is the reason to do that?

What is the reason to do that?
https://github.com/imager-io/ffmpeg-dev-rs/blob/b8dc9f73bfe6b8b5389ab4f744c1da6f05cdfb49/examples/remux.rs#L183

Regarding
https://github.com/imager-io/ffmpeg-dev-rs/blob/b8dc9f73bfe6b8b5389ab4f744c1da6f05cdfb49/examples/remux.rs#L183
Honestly I don’t remember why. It’s possible I was being paranoid and wanted to ensure that any associated drop implementations got called (unsafe rust is confusing sometimes, let alone the insanity of FFmpeg C APIs, though perhaps it's just me LOL).


[v8] Fix #8308 non-chunked file uploads directly dropped to dropzones

Related to #8309
Original issue #8308
This fixes a bug caused by #8309 with non-chunked file uploads that are directly dropped to the dropzones.
The issue is further explained in this comment in the original pull request:
https://github.com/concrete5/concrete5/pull/8309#issuecomment-594708442

I'm having this problem on a production site, the problem is not present on my dev server. Is it safe to replace this file on the live site?

updating this file does not solve the issue for me. Do I need to change something else?


Deploy RiboViz under Windows Subsystem for Linux on Windows 10

Try the Windows Subsystem for Linux which allows running of a Linux environment on Windows 10 without the need for a VM. It comments that "most" command-line tools, utilities, and applications can be directly on Windows, unmodified. Ubuntu, openSUSE, Debian, Kali Linux flavours can be used. If successful, update user documentation.
Arose from #1.

Followed Windows Subsystem for Linux Installation Guide for Windows 10, 04/07/2021, selecting WSL2 and Microsoft Store Ubuntu 18.04 LTS.
Used develop branch, commit 015467d Fri May 28. The following additional commands were required from those in docs/user/install.md:
Required before starting 'Install general packages', otherwise bedtools, hdf5-tools, pigz etc. won't be found:
$ sudo apt update

$ sudo apt-get install -y git
$ sudo apt-get install -y curl
$ sudo apt-get install -y bedtools
$ sudo apt-get install -y hdf5-tools
$ sudo apt-get install -y pigz
$ sudo apt-get install -y pandoc
$ sudo apt-get install -y graphviz

Required, otherwise unzip is not available:
$ sudo apt-get install unzip

Required, due to known issue generate_stats_figs.R has testthat dependency #334:
> install.packages("testthat")

Successfully run vignette and all tests, including regression tests.

TODO update documentation to state WSL works, link to Microsoft WSL docs, and requirement to run apt update and apt-get install unzip to docs/user/install.md`.

Commit 656592f of develop has docs/user/install.md with above updates.


portainer should not manage its own container

portainer v 1.17.1
I Use --restart=unless-stopped, and if I look at the container list
I can both stop,kill,remove the portainer container. then the webgui starts behaving strange :-)
Should be a breeeze to add a filter which grays out the portainer container.

Using the -l option to hide Portainer does not work very well. The portainer_data volume is still visible (even if it's labeled with the "hide-label", which only seems to work for containers). The portainer image is listed and is wrongly marked as "unused".

Agreed. It would be nice to be able to hide the container, image, volume and network associated with portainer, but the label approach only works for the container, and it doesn't work for me either.
This is an old thread... is there a workaround or new approach since then?

For the container, we have disabled the start/stop/kill/etc functions for the Portainer container in the UI. This is a bit harder for the volume and image however, so those still need work.


Get rid of goog.functions

This PR suggests to remove goog.functions usage in the quest for closure library independence.
The reusable functions returning true or false have been ported to ol.functions. Other use of goog.functions had only a single call site and has been replaced by local code.

Haha awkward... #5084 should I close my one?

Hah, yep. :) But there is actually value in this duplicated effort. I spot at least three things:

Good idea to have test cases, though they should be finished.
You are missing type annotations for some of the functions in ol.functions.
Ported code differs (at least in annotation). Should make sure code is ported from the correct closure library version (closure-util indicates version dated 20160208).

Yes, I am a bit new to type annotations.
One thing I did note was arguments usage, I am a bit unsure as to if this gets de-optimized. However  it is noted in V8 Optimization Killers that it can be if the function is bound and apply is used. Thats why I added the copying of arguments. Thoughts?

@nicholas-l, I think we got good input (thanks @tschaub) to make a final effort on removing goog.functions usage. Do you want to do the honors or is it up to me? :)

Probably going to run out of time, grab anything from my pull request if you like

I've made a new effort on this now and updated the PR description to the current status. I've replaced single code site usage with local code as recommended by @tschaub.

Looks great and now it doesn't look like it needs any tests added

Rebased and ready for review. Ping @tschaub.

I really like this. I added one minor comment / question.
Plus one for merging.
A follow-up PR might move ol.nullFunction into the ol.function namespace.
Thanks for the work on this,  @bjornharrtell and @nicholas-l

Thanks @marcjansen, wasn't aware of ol.nullFunction, updated branch to use it as suggested.

Thanks. Can you rebase again, so I can merge this, @bjornharrtell?

Rebased. Is it just me or was GitHub more lenient before, not requiring rebasing of out of date branches if they did not have merge conflicts?

Is it just me or was GitHub more lenient before, not requiring rebasing of out of date branches if they did not have merge conflicts?

It's not you alone… I think the same. It isn't that bad for everyone, though.

Could be to do with this

Ah nice find @nicholas-l. Should perhaps be discussed by the core devs. Problem is I don't know which forum, if any, to use to reach the core devs except here. @marcjansen any thoughts?

Mhhm… maybe the dev mailing list or a dedicated issue here with a good rationale and some suggestions.
In this ticket here, the context is obviously wrong :wink:

Github have just changed the way this works when you have status checks https://github.com/blog/2137-protected-branches-improvements


Update FanEntityFeature.TURN_OFF / TURN_ON

To comply
https://developers.home-assistant.io/blog/2024/07/19/fan-fanentityfeatures-turn-on_off/
HA Core 2024.8

Hi, please also add
    _enable_turn_on_off_backwards_compatibility = False
as described in the article. You can take inspiration in the climate.py, where I did similar compatibility change earlier. Thank you.


Does mlc-llm support nv gpu using CUDA instead Vulkan

I notice that mlc-llm has supported nv gpu by Vulkan. Does mlc-llm support nv gpu using CUDA instead Vulkan? I guess nv prefers CUDA than Vulkan so CUDA will be faster than Vulkan?

Of course MLC-LLM supports CUDA, the reason we release Vulkan versions is it's general and supported by more backends to NV GPUs. You can compile the CUDA version manually by running
python build.py --model MODEL_NAME --target cuda ...

MLC-LLM supports CUDA, the reason we release Vu

Thanks, I will have a try.

btw, you need to compile and install the relax project before running this build.py script.

@yzh119 does cuda got a faster speed to vulkan after both tuned?

奇怪的是，我的笔记本电脑没有安装Vulkan驱动，而是安装的CUDA驱动。运行MLC Chat也没有问题。
是不是我哪里操作不对？会不会是我在运行MLC Chat时没有跑在显卡上而是跑在CPU上？
Strangely, my laptop does not have the Vulkan driver installed, but CUDA driver installed.
There is also no problem running MLC Chat.
Is there something wrong with me? Could it be that I am not running on the NV GPU but on the CPU when I run MLC Chat?

most recent gpu drivers usually automatically comes with vulkan support

We haven't particularly focused a lot on CUDA optimization yet, as torch.compile() should already work for huggingface models out of the box. Happy to bring in more optimization later

cuda got a faster speed to vulkan after both tuned?

Thanks a lot. I have got the vicuna-v1-7b_cuda_float16.so. But error happened when building mlc-llm-cli. Could you please have a look? @yzh119  Detail infor can be found in #119

Close it as the discussion continues in #119 .


Unable to update when primary key is character(x)

A [DbUpdateConcurrencyException] occurs when an UPDATE to a record with a fixed length character primary key is Saved to the DB and that key has trailing spaces.  The Concurrency check appears to trim the value on the primary key which causes it to fail validation of the change even though the SQL log shows a valid UPDATE command (with space padding) was received and processed.  I have attached a small .NET Core Console application that generates the exception.
I have tried numerous ways to define the entity model but without success.  Prior to this <IP_ADDRESS> release of Npgsql.EntityFrameworkCore.PostgreSQL I was able to make this work using a property definition of .HasColumnType("varchar").HasMaxLength(8) which didn't make sense but worked.  Re-scaffolding the database using the <IP_ADDRESS> release outputs the property as .HasColumnType("character(8)") with a string property.
Postgresql log:
2018-08-03 16:44:19 CDT LOG:  execute : UPDATE testchar.tablechar SET char_value = $1 WHERE char_ident = $2
2018-08-03 16:44:19 CDT DETAIL:  parameters: $1 = 'This will NOT update', $2 = '123456  '
testchar.zip

This program will execute if you change the package references to:

And update the model builder definition of CharIdent to be:
.HasColumnType("varchar").HasMaxLength(8)
But I really need to update to .NET 2.1!

This behavior is actually defined in the SQL specification (1992):
3) The comparison of two character strings is determined as follows:

    a) If the length in characters of X is not equal to the length
        in characters of Y, then the shorter string is effectively
        replaced, for the purposes of comparison, with a copy of
        itself that has been extended to the length of the longer
        string by concatenation on the right of one or more pad char-
        acters, where the pad character is chosen based on CS. If
        CS has the NO PAD attribute, then the pad character is an
        implementation-dependent character different from any char-
        acter in the character set of X and Y that collates less
        than any string under CS. Otherwise, the pad character is a
        <space>.

    b) The result of the comparison of X and Y is given by the col-
        lating sequence CS.

    c) Depending on the collating sequence, two strings may com-
        pare as equal even if they are of different lengths or con-
        tain different sequences of characters. When the operations
        MAX, MIN, DISTINCT, references to a grouping column, and the
        UNION, EXCEPT, and INTERSECT operators refer to character
        strings, the specific value selected by these operations from
        a set of such equal values is implementation-dependent.

Source credit to SQL: Where spaces may not matter.

@tom-mulligan I misread your description initially. Sorry about that.
This could be related to the string comparisons I referenced above....but it's much more likely to be another instance of what we could call the explicit cast and broken inference problem.
As a short term solution, you could create the column as varchar(8) (or text + your own check constraint). Alternatively, you can take a look here for a solution that involves creating overloaded operators.
Borrowing a description of the problem from @rwasef1830:

I imagined there was a tsvector @@ text overload and implemented a Matches method that took a string parameter in addition to the overload that takes NpgsqlTsQuery. Strangely enough, the unit test for this was passing but I now I think that it was due to the test passing the string as a literal constant to the Matches method and Npgsql embedding the literal directly in the SQL thus allowing the PostgreSQL type coercion to work.
However, when it is passed as a parameter, Npgsql sends the parameter with explicit type of text which causes PostgreSQL to fail since it won't do type coercion when the types are specified explicitly in the query protocol for the parameters and there is no tsvector @@ text overload.

/cc @roji
--
-- Pretend that the LHS value is a column and the RHS value is a parameter:
--

-- this is the answer we want
SELECT '123456  '::char(8) = '123456  '::char(8);
 ?column?
----------
 t
(1 row)

-- but this is what we actually have
SELECT '123456  '::char(8) = '123456  '::text;
 ?column?
----------
 f
(1 row)

-- this would still fail from the lengths
SELECT '123456  '::char(8) = '123456  '::char;
 ?column?
----------
 f
(1 row)

-- works because varchar(8) is really text + a check constraint
SELECT '123456  '::varchar(8) = '123456  '::text;
 ?column?
----------
 t
(1 row)

-- works because of literal type inference
SELECT '123456  '::char(8) = '123456  ';
 ?column?
----------
 t
(1 row)

Related
https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/issues/428
https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/issues/561
https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/issues/562
https://github.com/aspnet/EntityFrameworkCore/issues/4978

@austindrenski your analysis here seems correct, we keep running into this issue again and again.
One new thought I've just had on this, is that there's the theoretical possibility of relaxing the strong typing approach when it comes to string. Npgsql currently sends specific type OIDs for all parameters, but there's also the option to send 0 ("unknown"), to allow PostgreSQL to infer the type from the context. This would make string parameters behave like literal strings above, and allow PostgreSQL type inference to do the right thing. Note that in EF Core literal representations are currently also always strongly-typed, except for strings (and numbers) as can see above: we don't generate 'some_text'::TEXT, but rather simply some_text. This was more a concern of readability, but also affects inference.
I'm not sure I understand the exact consequences of not typing our parameters in this way. SQL where the context isn't enough to infer would start failing; an example is SELECT $1, but there are surely some less-contrived real-world scenarios. This definitely merits some analysis, we could also simply send type OID 0 and see what it does to our current test suite :) Finally, note that this is really something that's needed for EF Core (but possibly also other ORMs) rather than for Npgsql itself - if you're working at the ADO.NET level you always have the option of explicitly setting the exact desired type via NpgsqlDbType.
PS Here are the PostgreSQL docs on character types, documenting the bizarre truncation behavior with trailing whitespace.

Split off the general type OID discussion to https://github.com/npgsql/npgsql/issues/2095

The more I dig into the comparison semantics for text/varchar/char(n), the more bewildered fascinated I am.
While the OID discussion is good to have, I'm not entirely sure it would help here. It almost looks like this is just a case of extreme differences between how the CLR and PostgreSQL think about string comparisons and type resolution.
See below for a worked out example, but I'm concerned that even if we sent string parameters with OID = unknown, dealing with char(n) could still break down in ways that are difficult to anticipate.
Personally, I would like to see us strongly discourage the use of char(n)/character(n) in EF Core altogether (much like timestamptz or tstzrange).
Per the string type docs:

However, trailing spaces are treated as semantically insignificant and disregarded when comparing two values of type character.

Trailing spaces are removed when converting a character value to one of the other string types.

Per the string function docs:

Unless otherwise noted, all of the functions listed below work on all of these types, but be wary of potential effects of automatic space-padding when using the character type.

--
-- Pretend that the RHS value is a parameter:
--

CREATE TEMP TABLE test ( a char(8) );
INSERT INTO test (a) VALUES ('123456  ');

-- note the two extra dashes in the row separator which indicate trailing spaces are present
SELECT a FROM test;
    a
----------
 123456
(1 row)

-- not no extra dashes in the row separator which indicates truncation occured
SELECT a::text FROM test;
   a
--------
 123456
(1 row)

-- if we use OID = unknown
SELECT a = '123456  '::unknown FROM test;
 ?column?
----------
 t
(1 row)

-- but this is still what's really happening
 SELECT RTRIM(a) = RTRIM('123456  '::unknown) FROM test;
 ?column?
----------
 t
(1 row)

-- here's how the lengths work out
SELECT
  char_length(a)                   AS a,
  char_length('123456  ')          AS infer_type,
  char_length('123456  '::text)    AS cast_text,
  char_length('123456  '::char(8)) AS cast_char8,
  char_length('123456  '::unknown) AS cast_unknown
FROM test;
 a | infer_type | cast_text | cast_char8 | cast_unknown
---+------------+-----------+------------+--------------
 6 |          8 |         8 |          6 |            8
(1 row)

Thank-you for this information.  It identified what the problem is and a means to overcome it.  The true cause is the logic change in Npgsql to now specify parameter data types instead of letting the database infer the type.  Prior to 2.1 this was not happening for literal strings.
I understand that the project that identified this problem is working with a poor database design, but we are now forced to change a large legacy database from character(x) to varchar(x) for all the PK and FK columns that were character(x).  This has complications because there are other legacy applications and external systems that utilize this database for content.  The testing and approval process required for this change will take a large amount of resources and considerable time.
Yes this is a poor database design choice, but it had been working on various database servers for over 20 years until now.  I also understand the decision of Npgsql to strongly (??? except string ???) type parameters instead of letting the database infer them (although, the database does a pretty good job when it does infer the data type...IMO).

@tom-mulligan wrote:

I understand that the project that identified this problem is working with a poor database design, but we are now forced to change a large legacy database from character(x) to varchar(x) for all the PK and FK columns that were character(x). This has complications because there are other legacy applications and external systems that utilize this database for content. The testing and approval process required for this change will take a large amount of resources and considerable time.

I am very sympathetic to your situation. I've just recently reworked a legacy schema and dealt with all of the headaches that come with updating an old system.
At the end of the day, an ORM is just an abstraction intended to help you add value to your organization. It shouldn't dictate business decisions, nor do we intend it to.
We can provide guidance on how this project will work with your database, but in the end, we can only offer advice that should be weighed against many other factors before applying it to real-world business decisions.
With all of that in mind, I do plan to take another look this weekend to see what—if anything—can be done in the EF Core provider to better support the char(n) semantics as defined by PostgreSQL.
@austindrenski wrote:

Personally, I would like to see us strongly discourage the use of char(n)/character(n) in EF Core altogether (much like timestamptz or tstzrange).

To be clear, this is strictly my personal opinion for an idealistic world where every database is a greenfield project. PostgreSQL supports these data types because each has a role and adds value in some way.

This seems fringe enough to "let it go", though continue to consider this issue in future planning.  Thanks again for the prompt and intelligent discourse.  Consider this closed?

FWIW, I do think there's room to revisit the decision that literal representations be strongly-typed. This is somewhat related to the discussion in https://github.com/npgsql/npgsql/issues/2095, although that discussion is for parameters and not literal representations.
My primary objection, apart from a general preference of strong typing, is that if we remove strong typing we introduce a behavior discrepancy between parameters (which as per https://github.com/npgsql/npgsql/issues/2095 will stay strongly-typed) and literal values. I think it's better for these two types of things to behave in the same way.
There's also a possible solution on the way, namely https://github.com/aspnet/EntityFrameworkCore/issues/4978. At that point there would at least be a way to manually override the type chosen by EF Core, even if it would be somewhat verbose etc.
But we can definitely close for now, @austindrenski what do you think?

@roji I've taken another pass at this with #588 and I think I've got a working patch in place. But, the fix feels fragile, so I'd appreciate another set of eyes on it before calling this closed...

@tom-mulligan We've merged #588 to patch the comparison discrepancies reported here. This should make character data easier to work with the release of version 2.2.0 later this year.
If you would like to try it out sooner, have a look at our unstable MyGet feed for the latest build:
dotnet add package Npgsql.EntityFrameworkCore.PostgreSQL --version 2.2.0-ci.935 --source https://www.myget.org/F/npgsql-unstable/api/v3/index.json

This was a challenging bug, so many thanks for taking the time to report it to us!


main.sh.jinja's need set -e

I had a bug in my changes but rsc didn't blow up
Source: /var/tmp/radia-run-17302-27777/20240801164924-docker.sh
/srv/docker/volumes: exists, docker already installed
bash: line 51: docker_need_update: command not found
curl -L -s -S -n http://v3.radia.run:2916/host/v3.radia.run//etc/docker/certs.d/v3.radia.run:5000/ca.crt

Looks like none of our main.sh.jinja's have set -e (or ou pipefail). @robnagler why is that? Should it come from somewhere outside?

An if statement overrides -e, since -e is simply testing that any command returns non-zero, which is what if does. There is no concept of an exception or error in Bash. This is why tests are important, I think, but that's not easy to do for this type of code without a lot of mocking, which reduces the quality of the tests. I would say this is simply a consequence of programming in Bash, and why we do as little of it as possible in rsconf, and rely on Python for the heavy lifting.

Ah of course. Thank you.
FWIW - came across this interesting shellcheck https://www.shellcheck.net/wiki/SC2155 . Maybe something we should add to our style.


[ALLUXIO-6291]  Improve Something

Improve core/client/fs/src/main/java/alluxio/client/block/stream/NettyPacketWriter.java as mBufferEmptyOrFailed can be marked as final.
Change
private Condition mBufferEmptyOrFailed = mLock.newCondition();
to
private final Condition mBufferEmptyOrFailed = mLock.newCondition();

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17211/
Test PASSed.

alluxio-bot, check this please


New User book recommendations on Home Screen

Currently, no recommendations are shown for a new user because the recommendation is based on a book in their library (since the user is new, there will not be any books in their library).
Motivation
As a new user, I would like to see a few suggestions on what books I might like to read next.
Finish Line
User will be presented with a list of suggestions based on a random data model.

Need to test both new user and a current user for proper error handling and alert displays.


RL2 Extensions Wishlist

What extensions would you like to see bundled with Robotlegs 2 (or officially provided and supported)?

SignalCommandMap

modular is already there am i right? (if not please add) so it should be SignalCommandMap with named args eg. http://blog.sjhewitt.co.uk/2010/02/robotlegs-and-as3signals-injecting-interfaces-and-named-arguments/
and yes i surely need it both :)

@katopz do you know if the modifications outlined in that post ever made it back into Joel's fork? I don't know enough about the SignalCommandMap to know what status it's in.

ModularityExtension

@darscan hmm, AFAIK i don't think so, normally i did fork it and do some optimize here
https://github.com/katopz/signals-extensions-CommandSignal
but i never make pull request because i think i've to do all unit test and performance test 1st but i didn't have time to
finger cross btw, i already use it in real production, shame on me ;p
i think we should ping both @sjhewitt and @joelhooks for this :)

@katopz I have opened up an issue for a v2 SignalCommandMap here:
https://github.com/robotlegs/robotlegs-framework/issues/56

What is the scope of an 'extension'? Is it commonly needed, yet not required, functionality?  If so,...
I recommend platform specific functionality. An example would be a 'TabbedViewNavigatorApplicationExtension' that would handle the common 'app-level' operations a developer would need from the 'TabbedViewNavigatorApplication' class. For instance, as3-signals and the corresponding commands to change the ViewNavigator's currently shown Tab.

The currently provided extensions seem sufficient:
https://github.com/robotlegs/robotlegs-framework/tree/version2/src/robotlegs/bender/extensions
Closing for now, feel free to re-open.


[network] Simplify identity exchange protocol and API

Cleans up some design decisions that were useful when using Yamux, but are no longer relevant.
Identity exchange will be split into the handshake protocol and a PeerId exchange, the latter serving as an alternative for connections which don't use Noise.

@bors-libra r=davidiw

:pushpin: Commit 3b482ca has been approved by davidiw

@bors-libra retry

:hourglass: Testing commit 3b482ca0511e455a15797a6cd46f30d4c598f870 with merge 0d0d73b645b0d8ee292c196430bd760bab55e76f...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra retry

:hourglass: Testing commit 3b482ca0511e455a15797a6cd46f30d4c598f870 with merge cf943510104b1d29efb9cc56fb41b2a54eadd02c...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: davidiw
Pushing cf943510104b1d29efb9cc56fb41b2a54eadd02c to master...


import error

ImportError                               Traceback (most recent call last)
 in <cell line: 1>()
----> 1 from langchain_cohere import ChatCohere
2 from langchain_core.messages import HumanMessage
3 from langgraph.graph import END, MessageGraph
4
5 model = ChatCohere(temperature=0)
2 frames
/usr/local/lib/python3.10/dist-packages/langchain_cohere/cohere_agent.py in
2 from typing import Any, Callable, Dict, List, Sequence, Tuple, Type, Union
3
----> 4 from cohere.types import (
5     ChatRequestToolResultsItem,
6     Tool,
ImportError: cannot import name 'ChatRequestToolResultsItem' from 'cohere.types' (/usr/local/lib/python3.10/dist-packages/cohere/types/init.py)

NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.

Name: langchain-cohere
Version: 0.1.4
Summary: An integration package connecting Cohere and LangChain
Home-page: https://github.com/langchain-ai/langchain-cohere
Author:
Author-email:
License: MIT
Location: /usr/local/lib/python3.10/dist-packages
Requires: cohere, langchain-core
Required-by:

came across the same error.
It seems cohere updated their library and ChatRequestToolResultsItem does not exist any more, it got replaced.

yes, and thanks for helping.


Dark mode, example environmental keys, updated contribution section

Dark Mode: Added support for dark mode, enhancing readability and reducing eye strain for users who prefer a darker interface.
Example Environmental Keys: Included example environmental keys to provide clear guidance for setting up environment variables, facilitating a smoother onboarding process for contributors.
Updated Contribution Section: Enhanced the contribution section to ensure accuracy and clarity, making it easier for new contributors to understand how to get past common hurdles in contribution.

academics/scheduling: Separators between courses are invisible. Is this intentional?
Darkmode icon conflicts with sidebar (see: career/study-plan/), also it won't click when there's overlap.

courses/: Filter control buttons are unreadable


[Feature Request] Mobile compatibility (./me)

Can't pass the Mobile-Friendly Test (MFT)

Problem fixed by redirecting to zh.m.wikipedia.org


Specifying config file for use by CLI

Is your feature request related to a problem? Please describe.
If I have multiple databases, and therefore multiple different configs, I'd like to be able to specify one to use when running a CLI command. For example, my project has its "normal" database, and then a separate database which gets used for running tests against, so that the normal database does not have its data changed. Therefore I have a mikro-orm.config.js file and a mikro-orm.test.config.js file. I'd like to be able to specify which config file the CLI commands should use
Describe the solution you'd like
An optional additional flag passed to all CLI commands. This could either be a literal filename (e.g. --config=mikro-orm.config.js), or what I think would be cleaner is to allow an array of named config options within a single mikro-orm.config.js file, similar to TypeORM. Then we could do --configname=main or --configname=test
Describe alternatives you've considered
A rather hacky workaround where a custom script temporarily copies/renames files and then reverts them when the CLI commands are finished

You can use MIKRO_ORM_CLI env var for that.
$ MIKRO_ORM_CLI=/foo/bar/... npx mikro-orm debug


include LICENSE to sub-crates

Signed-off-by: Igor Gnatenko<EMAIL_ADDRESS>

ping?

https://ticki.github.io/blog/why_im_leaving_open_source/


ui: elided button

we can overriding  mousePressEvent if need press state in this control.

Much cleaner, I'll check it out soon!

any update on this?

done


Adding a property for disabling animated scroll.

This gives the option to disable animated scrolling, which might be something users want, but more importantly this is a temp fix for this issue here, https://github.com/deanmcpherson/react-native-sortable-listview/issues/97, that will allow for people to fix the ios scrolling problem temporarily while a long term solution is addressed.

Thanks for your contribution, I'll find if there is another way to solve the issue or I'm happy to land this

I appreciate the quick response. Hopefully there is a better solution, because it looks better with the animation. Thank you and all the other devs for all your hardwork on this project.

I'm so sorry I'm absent for such a long time leaving this open, I think that's the right solution for now, as the scrollTo takes no duration param, thanks so much

@chetstone can you release a new version as I've landed several important fixes

Done.
@deanmcpherson Could you please give @nihgwu permission to publish to npm? He understands the code much better than I do and has been doing a great job responding promptly to issues. I intend to continue to help as much as I can --- sorry about the delay in responding to this request.

No problem! I just added @nihgwu as another owner of the npm package. @chetstone

@chetstone @deanmcpherson Thanks


Fix checkPropertiesEqual

Supersedes #1561
In our case, we pass quite a few props in navigation calls, including arrays and functions. The !== check fails for those, allowing for the double-tap effect mentioned in #384
The proposed solution is to use lodash's isEqual which provides a solid equality check that should suffice for most cases. isEqual is bundled separately to prevent bloating RNRF.
Additionally to isEqual I also opted to exclude checking functions altogether, as those are usually generated inline as part of the navigation call, failing isEqual as well.

@aksonov here's the updated PR


Mobile improvements

Whenever I was reading documentation generated by this renderer on a mobile device, I always found it too small to read comfortably. So, I wanted to find an easy way to improve this.
https://user-images.githubusercontent.com/795488/197769619-e97f1fdd-7394-42bd-ae0e-09d12783d6e4.mp4
This PR adds a standard viewport <meta> tag, which makes the font size on mobile devices ideal for me. This change caused tables to overflow, making the whole page horizontally scrollable, so we ensure that overflowing tables are individually scrollable. I also increased overall horizontal padding a little bit, so that it's more comfortable on mobile devices.
https://user-images.githubusercontent.com/795488/197769744-74886494-3455-455b-9e20-719886ed644f.mp4

Looks good, thanks for the patch!


ts def typo fix and addtions

This enables us typescript users to use such component properties.
Also, I use react-toolbox heavily with typescript at work, so I'll likely create this kind of pull request again. :smiley:

Thanks!


Memory leak when print request and response debugDescription

Hello,
I noticed that in my code , when use
print(response.debugDescription)
or
print(request.debugDescription)

There will be a memory leak shows in instrument.
Here is my code:
 Alamofire.request(.GET, "https://www.github.com").responseJSON { (response) in
    print(response.debugDescription)
}

and this is the screenshoot of instrument

you can see more in my repo
thanks a lot ~

Hi @sosng,
Thanks for putting this issue together along with the sample project. I'm able to reproduce the leaks you're referring to. They have to do with leaks in string interpolation for building the debugDescription strings. I should have a fix in for this over the next few days.
Thanks again for reporting! 🍻

I've opened up PR #1262 to address this issue. Please direct all future comments to #1262.

Good Job!


WebAPI doc correction

The document is not correct in this URL(https://sendgrid.com/docs/API_Reference/Web_API/mail.html)
"Files to be attached. The file contents must be part of the multipart HTTP POST. Ex:
files[file1.jpg]=file1.jpg&[file2.pdf]=file2.pdf"

The example is wrong, it should be
files[file1.jpg]=file1.jpg&files[file2.pdf]=file2.pdf

I have a full correct .net demo here:
https://github.com/justrun1983/sendgrid-csharp-webapi
Sent to me by a current customer
-Garrett

I wanted to send multiple Attachment. But when i kept in for loop it was sending only one pdf and other didn't got send

Hello @dhruvJaiswal,
Which library were you using for this? If it is the C# library, could you please post your issue along with the relevant source code here: https://github.com/sendgrid/sendgrid-csharp/issues
Thank you!
With Best Regards,
Elmer


refactor: reorganise code structure to prepare for Snyk OSS integration [ROAD-236]

The code is grouped by product and organised in the following way:

itly
snyk

common
Code that will be shared between different product and feature integrations: configuration, analytics, logging, shared view elements, etc.
base
Code that provides base elements for the extension: status bar item, loading badge, welcome web view. Current monolith module is included as it's the entry point to the extension functionality.
snykCode
Code related to Snyk Code product integration, including view and code providers.
openSource
Code related to Snyk Open Source integration. Folder will be added later during dev work on it.

Additionally, this refactoring includes:

File naming brought to consistency (updated to camelCase)
BundlesModule refactored and extracted to corresponding SnykCode class with event subscriptions in the Progress class.
Redundant interfaces removed
Some interfaces were moved closer to the code that uses them
Interface naming brought to consistently (start with letter "I").

@pavel-snyk thank you. ROAD-236 - that's correct, amended the heading :)


Update Javadocs for Event Hubs

Description

Adds more documentation to Event Hubs
Cleans up samples that still use connections string and replace with DefaultAzureCredential
Consolidate code snippets and remove ReadmeSamples.java

All SDK Contribution checklist:

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

General Guidelines and Best Practices

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

Testing Guidelines

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

API change check
API changes are not detected in this pull request.


Add Apache License v2

Signed-off-by: xcaspar<EMAIL_ADDRESS>
Describe what this PR does / why we need it
Add Apache License v2 to files.
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Where to find Monaco editor supported browsers list?

Hi,
at https://microsoft.github.io/monaco-editor/ there's infomration about supported browsers, but those are just names.
Where can I find information about exact/minimal browsers' versions?
I've searched the repo, but didn't find any information on this

supports Classic Edge, Edge, Chrome, Firefox, Safari and Opera

@nmkedziora We support only the latest versions of these browsers.

@nmkedziora We support only the latest versions of these browsers.

Thank you @alexdima :)

Thank you @alexdima :)


Bevy and winit examples won't run on macOS Monterey 12.6.2 on a MacBook Pro (Retina, 15-inch, Mid 2015)

This was the output on running cargo run -p with_winit
warning: `vello` (lib) generated 10 warnings
    Finished dev [unoptimized + debuginfo] target(s) in 0.26s
     Running `target/debug/with_winit`
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_compute_pipeline
    Internal error: new_compute_pipeline_state: "Compiler encountered an internal error"

', /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2403:5
stack backtrace:
   0: rust_begin_unwind
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/panicking.rs:65:14
   2: wgpu::backend::direct::default_error_handler
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2403:5
   3: core::ops::function::Fn::call
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:78:5
   4: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/alloc/src/boxed.rs:2001:9
   5: wgpu::backend::direct::ErrorSinkRaw::handle_error
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2389:17
   6: wgpu::backend::direct::Context::handle_error
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:254:9
   7: <wgpu::backend::direct::Context as wgpu::Context>::device_create_compute_pipeline
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:1462:13
   8: wgpu::Device::create_compute_pipeline
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/lib.rs:2202:17
   9: vello::engine::Engine::add_shader
             at ./src/engine.rs:215:24
  10: vello::shaders::full_shaders
             at ./src/shaders.rs:138:26
  11: vello::Renderer::new
             at ./src/lib.rs:57:23
  12: with_winit::run::{{closure}}
             at ./examples/with_winit/src/main.rs:57:24
  13: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/future/mod.rs:91:19
  14: pollster::block_on
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/pollster-0.2.5/src/lib.rs:125:15
  15: with_winit::main
             at ./examples/with_winit/src/main.rs:213:9
  16: core::ops::function::FnOnce::call_once
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:251:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

with -p with_bevy it was
warning: `vello` (lib) generated 10 warnings
    Finished dev [unoptimized + debuginfo] target(s) in 0.62s
     Running `target/debug/with_bevy`
2023-01-16T10:37:25.132773Z  INFO bevy_render::renderer: AdapterInfo { name: "Intel Iris Pro Graphics", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
2023-01-16T10:37:25.477810Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_compute_pipeline
    Internal error: new_compute_pipeline_state: "Compiler encountered an internal error"

', /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2403:5

..and then continued the same

Do the wgpu examples run?
Specifically, the boids example uses compute shaders.
Additionally, does the bevy compute_shader_game_of_life example run?
It is probably also worth asking on the wgpu matrix about this.

wgpu boids doesn't run, no: zsh: segmentation fault  cargo run --example boids
sorry, this probably wasn't your fault.


handle_local_blobstore.sh cannot create directories

Issue
The handle_local_blobstore.sh will not be able to create default directories as it is called from the cloud_controller_ng_ctl/cloud_controller_worker_ctl scripts which are launched from their monit jobs running as user vcap.
Context
cf-release 239 fresh install
Steps to Reproduce
cf-release 239 fresh install with local blobstore - cloud_controller_ng job will not complete successfully.  Manually create local blobstore directories and mark as owned by vcap:vcap and job can then complete.
Expected result
handle_local_blobstore.sh would have been able to create the required directories
Current result
handle_local_blobstore.sh cannot create directories since it is indirectly running as user vcap:vcap
Possible Fix
handle_local_blobstore has to be run as root, perhaps from the pre-start script

Hey @rboykin,
We just pushed up a commit that should fix the problem you are seeing. The fix will be available in the next cf-release. If you feel that your issue has been resolved, please go ahead and close the issue.
Thank you,
@luan & @youreddy,
CF CAPI Team

Thanks @luan and @youreddy


Module pyrabbit2

Hi!
Try this module https://github.com/deslum/pyrabbit2. This is fork pyrabbit with new features and support

It is spam. Opening identical issues in 28 repos to advertise your project is definitely a spam.


'React/RCTBridgeModule.h' file not found in RNBluetoothTscPrinter.h

Build keeps failing with ~/node_modules/react-native-bluetooth-escpos-printer/ios/RNBluetoothTscPrinter.h:8:9: 'React/RCTBridgeModule.h' file not found

I also currently have this issue when building for iOS.
This is my environment information:

<EMAIL_ADDRESS><EMAIL_ADDRESS>Xcode 11.7
macOS 10.15.3

The project I am working was inherited to me, and don't know how exactly this package is used and for what (though, I located where it is). On Android, I remember that the screens/components that make use of kept throwing error.
So I notice that my current react native tooling is supporting auto-linking in all packages by except this one. What should I do with?

I also currently have this issue when building for iOS.
This is my environment information:

<EMAIL_ADDRESS><EMAIL_ADDRESS>Xcode 11.7
macOS 10.15.3

The project I am working was inherited to me, and don't know how exactly this package is used and for what (though, I located where it is). On Android, I remember that the screens/components that make use of kept throwing error.
So I notice that my current react native tooling is supporting auto-linking in all packages by except this one. What should I do with?


iosSwipeBack && mdSwipeBack 2.2.0

iosSwipeBack && mdSwipeBack
has a bug

Your issue is closed because it is not filled correctly. Before you open an issue please review the contributing guideline.
Please fill the issue template correctly and:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with isssue

It will save a lot of time for other contributors to check your issue and fix it.

ok now
each view in views ('.views .tabs') must have 'view-main' class
didn't know that
sorry


spike: a separate canvas iframe

this spike repurposes the property controls iframe to render a Canvas.
at the current stage, the biggest issue seems to be that there's a delay between sending an update message from the editor until the iframe receives it.
probably I made a mistake by piggybacking on the (special-cased) sendPropertyControlsInfoRequest function which does some form of throttling.
I'll pick this up today and try to make a more responsive version!
so far the spike seems promising, I think a few more hours of trial and error and I will have an answer whether canvas in a separate iframe is a viable performance improvement.

Note:
Even if this is not good enough for the canvas, this is definitely a viable direction to improve the Preview which now takes seconds to respond to user actions.

sadly, I think there's strong indication that we shouldn't spend more time on this for the Canvas (the preview will probably need a solution like this, if we keep it around)

the main hurdle seems to be that user events (like mouse move or wheel) have higher priority than interprocess communication. the messages are send via window.postMessage, and they only arrive at the iframe side in batches, very suspiciously precisely when there's a little break between mouse events
this means that this iframe lags behind the main canvas and I don't know about a way to remove this lag.


Problem appearance_modeling

Hi @ARuiChen!
I encountered a problem when running the following command：
python3 -m torch.distributed.launch --nproc_per_node=8 train.py --config configs/Gundam_appearance.json
Here's my log :
Traceback (most recent call last):
File "train.py", line 603, in
lgt = light.load_env(FLAGS.envmap, scale=FLAGS.env_scale)
File "/data0/xxl/Fantasia3D/render/light.py", line 146, in load_env
return _load_env_hdr(fn, scale)
File "/data0/xxl/Fantasia3D/render/light.py", line 135, in _load_env_hdr
latlong_img = torch.tensor(util.load_image(fn), dtype=torch.float32, device='cuda')*scale
File "/data0/xxl/Fantasia3D/render/util.py", line 423, in load_image
img = load_image_raw(fn)
File "/data0/xxl/Fantasia3D/render/util.py", line 420, in load_image_raw
return imageio.imread(fn)
File "/home/amax/.local/lib/python3.8/site-packages/imageio/core/functions.py", line 265, in imread
reader = read(uri, format, "i", **kwargs)
File "/home/amax/.local/lib/python3.8/site-packages/imageio/core/functions.py", line 181, in get_reader
raise ValueError(
ValueError: Could not find a format to read the specified file in single-image mode

This because naive imageio can not read the HDR file.
run imageio_download_bin freeimage in terminal to install the extension will slove it.


[AutoRelease] t2-connectedvmware-2023-09-23-67577(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4547
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=3325

issue link:https://github.com/Azure/sdk-release-request/issues/4547


shattered-pixel-dungeon: 0.8.1 -> 0.8.1a

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/00-Evan/shattered-pixel-dungeon/releases.
meta.description for shattered-pixel-dungeon is: "Traditional roguelike game with pixel-art graphics and simple interface"
meta.homepage for shattered-pixel-dungeon is: "https://shatteredpixel.com/"
meta.changelog for shattered-pixel-dungeon is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.8.1a with grep in /nix/store/8kc5sd4cbxmy9a1s0hykrldqqyz5p7p9-shattered-pixel-dungeon-0.8.1a

directory tree listing: https://gist.github.com/5a5015bdee0ce8b984b101a77b0fd436

du listing: https://gist.github.com/1b34c088b68caf4e0bb746914fe1c3a0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
shattered-pixel-dungeon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8kc5sd4cbxmy9a1s0hykrldqqyz5p7p9-shattered-pixel-dungeon-0.8.1a \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A shattered-pixel-dungeon https://github.com/r-ryantm/nixpkgs/archive/03812ea8065e16b7c60204f69d9f26fb268e74bc.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8kc5sd4cbxmy9a1s0hykrldqqyz5p7p9-shattered-pixel-dungeon-0.8.1a
ls -la /nix/store/8kc5sd4cbxmy9a1s0hykrldqqyz5p7p9-shattered-pixel-dungeon-0.8.1a/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

shattered-pixel-dungeon

Maintainer pings
cc @fgaz for testing.

@ryantm Does your bot also try to update this hash too or do I have to rebuild and check if it changed?:
https://github.com/NixOS/nixpkgs/pull/94313/files#diff-d1cdeb8216135d33b3370cd29bc4aa41R46


Visualising a "direct ancestry" ARG

It would be interesting to see how the visualiser copes with a tree sequence output from SLiM before any simplification, i.e. where all edge intervals (apart from those above recombination nodes) are 0..L. I paste an example below (the Wiuf & Hein 1999 example ARG)

Contrast this with the simplified version:

For the original ARG, the sequence of edges between h-g, g-e, e-c would be highlighted:

on, on, on for (0,2]
on, off, on for (2,5]
off, off, on for (5,7]

The visualizer does not check whether the edge intervals lead to highlighted edges being unconnected. Is this the behavior that you would expect/want? That sequence of edges in the simplified ARG would have the following highlighting pattern:

on, on, on for (0,2]
off, off, on for (2,7]

I've been working with SLiM outputs recently for my spatial research. At least in how we have done it, one big complication is that the SLiM tree sequences contain lots of unary nodes along every edge and at every time step. We have a few custom simplification steps that keeps the "full ARG" but gets rid of most of the unary nodes. This includes fixing the edge intervals with ts.simplify(). We've been using the visualizer to view small examples from SLiM outputs (a few trees for a small number of samples), though the ARGs are often too complex to visualizer in their entirety.


About the seed.jsonl

Great work!
I'm curious about how seed.jsonl is constructed, it is mentioned in src/script/data_generate.sh and is the args of the source_data_path.
It would be great to show parts of it.

Hi,Ch3nYe. Thank you for your suggestion. Actually, the seed.jsonl just contains the raw code snippet after KCenterGreedy(process A in paper). In our generation, we adopt a  process where the raw code snippet is rewritten to a code-related text and then to generated code (The last two steps is shown in https://github.com/microsoft/WaveCoder/blob/main/src/data/llm_gen_dis/fewshot_case/bad_case/bad_case_0.txt).


SDIFF not returning correct response

If I add values to 2 different sets via SADD and then try to diff them using the SDIFF method, the wrong result is returned. But, if I run sendCommand(['SDIFF', 'key1', 'key2']) it returns the correct result.
For Example:
import redis from 'redis';

const client = redis.createClient();
await client.connect();

const array1 = ['a', 'b', 'c', 'd', 'e', 'f', 'g'];
const array2 = ['d', 'c', 'f', 'a'];

await client.SADD('key1', array1);
await client.SADD('key2', array2);

const badDiff = await client.SDIFF('key1', 'key2');
console.log('Bad Diff: ', badDiff);
// Bad Diff: [ 'g', 'a', 'd', 'c', 'f', 'b', 'e' ] (Incorrect!)

const goodDiff = await client.sendCommand(['SDIFF', 'key1', 'key2']);
console.log('Good Diff: ', goodDiff);
// Good Diff: [ 'g', 'b', 'e' ] (Correct!)

It doesn't make a lot of sense why this would be happening but its easily verifiable.
Environment:

Node.js Version: 18.7.0
Redis Server Version: 7.0.4
Node Redis Version: 4.3.1
Platform: MacOS 12.5.1 & AlmaLinux 8.6

The SDIFF syntax is changed... it accepts array instead of single parameters.
So you should use this:
const badDiff = await client.SDIFF(['key1', 'key2']);

I can confirm that works, thanks!
Why is this one method different than most others? Is this change documented anywhere? If not, I can probably add that to some docs somewhere.

its documented here (and I know we should do better work at "exposing" this, please share any ideas you have... :) ).
The reason "spread" is not supported is to allow optional arguments in the future.

Is there a specific type of command that qualifies it to take arguments like this? Like all commands that take multiple "input" arguments (not quite sure how to describe it). Just trying to think of some verbiage that would make sense and be clear to users in the docs...
I was thinking of explaining which kinds of commands need this syntax, list a few of the commands that follow this format, and then show an example of it in action.


Unrecognized property place-self

The shorthand property place-self (used on a grid item) is not recognized:
Unknown property: 'place-self'

Upstream issue: https://github.com/Microsoft/vscode/issues/64835

https://github.com/mdn/data/issues/253 is fixed and adopted  in<EMAIL_ADDRESS>Can we upgrade to 4.0.2 from 3.0.13?


feat(ios): add possibility to add arguments to hermes

Summary:
Today, someone who wants to use a third-party bundler (like rnx-kit's bundler, for example) can do so by exporting the "BUNDLE_COMMAND" variable in the "Bundle React Native code and images" phase in XCode.
This Pull Request would allow the user to customize the compilation step via hermes, by allowing him to add arguments.
This is already possible on Android, thanks to the "hermesFlag" property (addable in android/app/build.gradle).
In my case, this would allow me to add the "-w" flag to hermes so that the compilation emits less logs (which breaks the archiving when using rnx-kit as a bundler).
Linked issues:
https://github.com/microsoft/rnx-kit/issues/2419
https://github.com/microsoft/rnx-kit/issues/2424
Changelog:
[INTERNAL] [ADDED] - Add  possibility to add arguments to hermes on XCode via HERMES_EXTRA_ARGS environment variable
Test Plan:
I tested locally my modification: the arguments added via the environment variable are well transmitted to Hermes, and the compilation always works when no argument is added, or when the variable is not exported in the bundle phase on XCode.

Change makes sense to me but it looks like this ran into a merge conflict.

could you also fix the merge conflicts, please? 🙏

Everything is right to me. I was curious to understand your use case and how/where you intend export the variables specifically.
I hate that we have all those scripts in Xcode, I would love to move them somewhere else and, perhaps, rewrite them in a different language (maybe JS... Swift for iOS would be even better! :D). So, by knowing better your use case, I could have some more ideas! 😄

My use case is a bit particular: it's simply to solve a bug I encounter when trying to use rnx-kit as a bundler for my application.
When I set up rnx-bundle as a bundle command, I could not create archives of my application because of the problem described here: https://github.com/microsoft/rnx-kit/issues/2424
We found that passing the "-w" parameter to Hermes solved this bug, but I did not find an easy way to pass this parameter to Hermes when archiving an iOS project.
Hence this new environment variable!
I hope I answer your question about my use case!

/rebase


Create procedural_art_generator.py

For issue no  #64

Hey @aniruddhaadak80  looks like you are our leading contributor for now ! You have done good contributions and it will be even better if you can add a Read.me file in the folder giving a small explanation of your project so others can understand easily. Happy coding !

Hey @aniruddhaadak80 looks like you are our leading contributor for now ! You have done good contributions and it will be even better if you can add a Read.me file in the folder giving a small explanation of your project so others can understand easily. Happy coding !

Hi @sumanth-0 ,
Thank you so much for your kind words! I'm thrilled to be a leading contributor and appreciate your feedback. I will definitely add a README file to the project to provide a clearer understanding for everyone.
Looking forward to continuing to enhance the project together!
Happy coding!
Best,
Aniruddha Adak


Redo PR #435

fix: remove the export defaults

What does this fix exactly? Please explain it in the commit msg body.

fix: logger.ts imports

What does this fix exactly? Please explain it in the commit msg body.

Occur? I guess you meant to use the past tense, because your commit fixes the errors, right?
And what errors? There’s zero effort in copy+pasting the errors you’re talking about in the commit message body.

tsconfig: avoid git pollution by enabling outdi

What in the world is “outdi”???

fix: find & replace require with import

You’re missing the the why (what does this fix exactly?)

On one of my old commits, I chose the wrong type for an arg function.

This commit message is much better than the others, but still not perfect. What was the consequence of choosing the wrong type?

The throw was also removed because it throws nonsense if the community is null.

What does “throw nonsense” means??

we need to make the following changes:
const logger = require('./logger');

to
const { logger } = require('./logger');

Why are you repeating in the commit msg what can already be seen in the commit's diff?

@ts-check enables type checking in a Javascript file,
so typescript compiler also checks these Javascript files and
error messages appear because JS files are missing types.

 SO EXPLAIN WHY!

tsconfig: avoid git pollution by enabling outdir

What do you mean with "git pollution"? I don't get it. Explain it in commit message body.

tsconfig: avoid git pollution by enabling outdir

You're also enableding allowJs and skipLibCheck, but are not mentioning them and not explaining why.

it may be necessary to replace the require calls with TypeScript syntax for imports.

Why???

It's not working when calling functions with named parameters,

Define what "it's not working" means. We are software engineers, not users.

Also, the throw was removed since it always throws.

I have so many issues with the above:

I guess you meant to use the past tense, not the present tense, right?
If it always threw, you mean it was always null???

Error messages appear when JS files lack types,

What do you mean??? JavaScript code doesn't have types so it obviously lacks types.

The outDir option specifies the output directory for
the compiled JavaScript files.
When outDir is set, the compiled JavaScript files
are emitted into this directory, preserving
the directory structure of the original source files.
Using outDir is a good practice when working with Git because
it allows you to keep your source code and compiled
code separate.
This makes it easier to manage your repository and avoid
unnecessary merge conflicts.
When migrating to TypeScript, you might have existing
JavaScript files that you want to include in your project.
The allowJs option allows you to include JavaScript files in
your TypeScript project.
However, when using allowJs, it’s important to note that
TypeScript will not perform type-checking on these files.
This means that you won’t get the full benefits of
TypeScript’s type system for these files.
The skipLibCheck option is used to skip type-checking of
declaration files, which can hide errors in third-party
libraries that you might be using in your project & I had to
use it to resolve this below error.

So what's the reason of mixing these 3 changes in one single commit?

@Mersho
fix(util/index): fix arg type & fn calls
63cc0b5
It's not working when calling functions with named parameters,
so I changed it, and there's a telegram argument with the
wrong type, and community might be null on isDisputeSolver.
@Mersho
fix(validations): fix named export
5423b77
As community may sometimes be null, I edited the
isDisputeSolver function ( in previous commit ) to accept null,
so we don't have to do a null check over it.

The community null check thing is being explained in 2 different commits, shouldn't it be in the same commit?

The logger.ts is named export, and this commit makes JS compatible.

I can't parse this sentence above. I think it's missing some word.

It's not working when calling functions with named parameters,

You're still not explaining what "not working" means.

Error messages appear when JS files lack types,

What do you mean??? JavaScript code doesn't have types so it obviously lacks types.

What's the problem here? I see that you guys agree. JS allows for implicit/non-existent types so ts-check fails on it. what's the big deal?

It's not working when calling functions with named parameters,

You're still not explaining what "not working" means.

I've explained in commit msg:

This makes it easier to manage your repository and avoid
unnecessary merge conflicts.

so ts-check fails on it

Why was CI before this commit green then?


Change the trace signal that will be driven for security control to address issue #11

Change the trace signal that will be driven for security control to address issue #11


[build-script] Compute targets in build-script

What's in this pull request?
This is a work-in-progress branch to move the computation of the target list up to build-script. It does size by inventing a new mechanism to pass host-specific variables down to build-script-impl, and it also factors out explicit objects for platform/target to attach metadata to.
Finally, this branch itself doesn't actually remove the build-script-impl logic. Instead, it runs both implementations and asserts that they compute the same result -- the logic itself is hairy so this has been a good source of catching bugs in the implementation for all the different flag combinations.
Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

/cc @gribozavr @rintaro @modocache
I'd like to clean this up a bit more before landing, but I'm posting it now in case anyone has feedback on the approach. The good news is that this will allow us to start ripping out much more of the code in build-script-impl once it lands and we are comfortable ripping out the validation logic.

After this PR land, direct use of build-script-impl is almost impossible.
I think, it's time to hide it in Python package directory.
https://github.com/apple/swift/compare/master...rintaro:build-script-hide-impl

@rintaro I agree about the build-script becoming unusable, but I'm not sure if it is worth moving it... my hope is that we continue to iterate quickly on just eliminating it, and in practice anyone using it has to migrate no matter what.

@rintaro I agree about the build-script becoming unusable, but I'm not sure if it is worth moving it...

I think build-script-impl has been not suitable for manual use for a long time already.  The only time I would expect someone to call it directly is while debugging it.  I don't think moving the file is worth the churn.

LGTM modulo comments!

@gribozavr @rintaro @karwa pushed an updated version which I am personally happy with, and would like to land ASAP and address feedback in follow on work.
This PR depends on #2919, and I will rebase once that lands.
I have completely reworked the last commit in this sequence to factor out a helper object, add additional comments, and respond to feedback. I have tried to structure this in such a way that it will be useful when we are doing all of the build-script interactions ourselves (not via build-script-impl).
The other commits in the sequence are basically unchanged, so I recommend focusing only on that one for re-reviewing purposes.

Rebased after landing #2919

@swift-ci please Python lint

@swift-ci please Python lint

@swift-ci please smoke test

Linux test failure definitely my fault, investigating.

Turns out Linux bash didn't behave the same way in parsing environment variables, fixed to normalize out - -> _.
@swift-ci please smoke test

Linux failure is unrelated -- OS X failure is based on a misunderstanding of mine about the shell API, which I intend to adjust in #2959.

@swift-ci please smoke test

@swift-ci please smoke test

Linux failure is unrelated, and got a LGTM from @gribozavr


Tensorboard integration cannot see the needed packages in any conda env on a remote host

Type: Bug

Behaviour
Expected vs. Actual
Using the "launch tensorboard" command gives me options to launch a tensorboard session from a specific directory.
What actually happens is this error:

Even though the minimum needed versions are installed on all conda envs on the machine, and seen by the command logged in the Output pane.
Running it manually gives:
$ conda run -n dev --no-capture-output python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py -c "import tensorboard; print(tensorboard.__version__)"
>>>PYTHON-EXEC-OUTPUT
2.4.1
<<<PYTHON-EXEC-OUTPUT
$ conda run -n dev --no-capture-output python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py -c "import torch_tb_profiler; print(torch_tb_profiler.__version__)"
>>>PYTHON-EXEC-OUTPUT
0.4.0
<<<PYTHON-EXEC-OUTPUT

Steps to reproduce:

Run from a remote environment.
Choose the "launch tensorboard" command.
Get the error asking to install the correct versions.
Click the button to install them.
Retry. Still doesn't work.
If instead you run tensorboard manually by tensorboard --logdir $logdir then open the UI locally via the forwarded port, it works. Opens fine in the local browser and shows everything.

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.8.5
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
Value of the python.languageServer setting: Pylance

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Experiment 'pythonaacf' is active
Experiment 'pythonTensorboardExperiment' is active
Experiment 'PythonPyTorchProfiler' is active
Experiment 'pythonDeprecatePythonPath' is active
Experiment 'pythonInterpreterInfoUnpinned' is active
LSP Notebooks experiment is disabled -- not in treatment group
LSP Notebooks interactive window support is disabled -- not in LSP Notebooks experiment
> conda info --json
Python interpreter path: /opt/conda/envs/dev/bin/python
[ERROR 2022-7-26 14:37:44.457]: Failed to initialize source map support in extension
> /bin/python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/interpreterInfo.py
> /bin/python3 ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/interpreterInfo.py
> /usr/bin/python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/interpreterInfo.py
> /usr/bin/python3 ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/interpreterInfo.py
> /opt/conda/bin/python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/interpreterInfo.py
> conda run -n dev --no-capture-output python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/printEnvVariables.py
> /opt/conda/envs/dev/bin/python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/interpreterInfo.py
Starting Pylance language server.
> conda run -n dev --no-capture-output python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py -c "import tensorboard; print(tensorboard.__version__)"
> conda run -n dev --no-capture-output python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py -c "import torch_tb_profiler; print(torch_tb_profiler.__version__)"
> conda run -n dev --no-capture-output python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py -c "import tensorboard; print(tensorboard.__version__)"
> conda run -n dev --no-capture-output python ~/.vscode-server-insiders/extensions/ms-python.python-2022.13.12381007/pythonFiles/get_output_via_markers.py -c "import torch_tb_profiler; print(torch_tb_profiler.__version__)"

User Settings

Multiroot scenario, following user settings may not apply:

languageServer: "Pylance"

terminal
• activateEnvironment: false

Extension version: 2022.13.12381007
VS Code version: Code - Insiders 1.71.0-insider (1a582f7c079d1eb4c89d4f637da2fc2fcb688b31, 2022-08-15T05:17:18.259Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: Yes
Remote OS version: Linux x64 5.0.0-1032-azure

Duplicate of https://github.com/microsoft/vscode-python/issues/19591


Adding the option to route requests through a proxy

For my use of rsspls I have added the option to route all requests through a proxy url (my home residiential IP, while rsspls runs on a VPS which gets blocked) specified in the [rsspls] section of feeds.toml. It supports socks5, http and https proxies with a quite minimal code change.
Would you be ok with a PR for this feature?

Sounds good! it just adds needs an additional feature to the reqwest create.
I am going to open the PR then.
Ps: FYI I just found out that this also enables using external scraping tools like headless browsers through projects like this:
https://github.com/FlareSolverr/FlareSolverr


Vimeo fullscreen issues in Safari

Hello,
Issue: i was able to reproduce issue that i am facing on plyr's demo page. full screen on "https://plyr.io/#vimeo" is not taking full screen. It takes width of half screen. Attached is the screenshot.

Appreciate It.

It looks like this is a Safari-wide issue. It also does it on desktop. I'm looking into it now.

Can also confirm this is happening on Chrome with iOS.

Any news about finalizing the other feature for releasig new stable version with fixed Safari bug?

This is now fixed in v3.5.0 👍

Thank you..

I'm still seeing this (or similar) issue on the Plyr demo page in Safari Version 12.0.1 (146<IP_ADDRESS>.1)
Also happening on my local files using v3.5.0 (and still only in Safari)

Weird. It looks fine for me in Version 12.0.3 (14606.4.5). Perhaps there was a bug in 12.0.1?

@sampotts How the heck do you have Safari 12.0.3 ?  I can't seem to even find a way to upgrade!
I'm even still having this issue in Safari Tech Preview 76 (Safari 12.2, WebKit 146<IP_ADDRESS>)
Grrrr.  Dangit Safari!

@sampotts How the heck do you have Safari 12.0.3 ? I can't seem to even find a way to upgrade!
I'm even still having this issue in Safari Tech Preview 76 (Safari 12.2, WebKit 146<IP_ADDRESS>)
Grrrr. Dangit Safari!

I can confirm, that everything is working fine with current stable safari version (12.0.3) .. can´t tell anything about tech previews etc.. but with current existing version everything runs like expected !

I'm even still having this issue in Safari Tech Preview 76 (Safari 12.2, WebKit 146<IP_ADDRESS>)
Grrrr. Dangit Safari!

I've just tested Release 76 (Safari 12.2, WebKit 146<IP_ADDRESS>) of Safari Tech Preview and it also seemed ok. In Safari Tech Preview there seems to be issues with hover interaction but that also effects loads of other sites and isn't isolate to Plyr. YouTube does the same. I presume this is a bug with Safari Tech Preview. However, the fullscreen works fine for me on https://plyr.io. I tried to use Safari and Safari Tech Preview for a while but they are quite buggy.

This issue persists with the current version of Safari (Version 12.1.1 (146<IP_ADDRESS>.1)). Vimeo videos are either displayed with huge borders or just in the upper left quarter of the screen. Vimeo example on  does not work as well.
Any updates on this?


Automatically detect private/public addresses

Feature Description
Version 1 of the proxy seems to automatically detect that the instance is running on a private address and connect to that. In contrast, Version 2 requires us to provide the --private-ip flag.
In situations where the instance does not have a public address, I think it would be preferable for the proxy to connect to the private addresses automatically.
Alternatives Considered
Are there any workaround or third party tools to replicate this behavior? Why would adding this feature be preferred over them?
A workaround is to use Version 1 of the proxy or pass the --private-ip flag explicitly. However, given that this instance does not have a public address, it seems reasonable to expect that the proxy could connect to the private address.
Additional Context
This is what I get when I connect using the v1 proxy (this is a very old version installed with gcloud components install cloud_sql_proxy -- incidentally, it would be nice if this was updated):
$ cloud_sql_proxy -version
Cloud SQL Auth proxy: 1.27.0+darwin.arm64

$ cloud_sql_proxy -enable_iam_login -instances PROJECT_ID:REGION:INSTANCE_ID=tcp:9470
2022/12/27 10:32:18 current FDs rlimit set to 1048575, wanted limit is 8500. Nothing to do here.
2022/12/27 10:32:20 Listening on <IP_ADDRESS>:9470 for PROJECT_ID:REGION:INSTANCE_ID
2022/12/27 10:32:20 Ready for new connections
2022/12/27 10:32:20 New connection for "PROJECT_ID:REGION:INSTANCE_ID"
2022/12/27 10:32:20 refreshing ephemeral certificate for instance PROJECT_ID:REGION:INSTANCE_ID
2022/12/27 10:32:20 Generated RSA key in 67.990208ms
2022/12/27 10:32:21 Scheduling refresh of ephemeral certificate in 59m2.640099s

This is the same output for a recent version of the v2 proxy (same instance):
$ cloud-sql-proxy --version
cloud-sql-proxy version 2.0.0-preview.4

$ cloud-sql-proxy     --auto-iam-authn     'PROJECT_ID:REGION:INSTANCE_ID?port=9470'
2022/12/27 10:31:15 Authorizing with Application Default Credentials
2022/12/27 10:31:16 [PROJECT_ID:REGION:INSTANCE_ID] Listening on <IP_ADDRESS>:9470
2022/12/27 10:31:16 The proxy has started successfully and is ready for new connections!
2022/12/27 10:31:32 [PROJECT_ID:REGION:INSTANCE_ID] accepted connection from <IP_ADDRESS>:50823
2022/12/27 10:31:32 [PROJECT_ID:REGION:INSTANCE_ID] failed to connect to instance: Config error: instance does not have IP of type "PUBLIC" (connection name = "PROJECT_ID:REGION:INSTANCE_ID")

Hi @jawnsy,
Thanks for taking the time to open a feature request.
The change from v1 to v2 was very much intentional, for 2 major reasons:

The original behavior was not intuitive -- we've had hundreds of support cases where the root cause was that the behavior was not predictable. Customers would assume they were connecting over private ip and really be connecting over public ip.
The original behavior was not static -- if someone added or remove an ip type it could change the behavior. For large scale deployments this could introduce issues with debugging; it created scenarios where instances of the proxy could have different behavior based on if they were started before/after the change.

Connecting over private IP is a very intentional thing - you need to have access through a VPC which is generally not a straightforward task. By making the flag for private ip an explicit setting, the behavior is not just more straightforward, but also leaves us room to improve the feedback when the user fails to connect.
If we do add something similar to this, it would probably be something like an --auto-ip option that would still require an explicit opt-in. However, we'd prefer not to at this time because we feel it's not a good choice for production.

That makes sense, thanks for the comprehensive explanation @kurtisvg!
Your explanation might be worth copying into the migration guide's Notes column, to make it clearer that this was an intentional change/expected difference in behavior.


Question for file download

Hi, I see that OpenAPI have description for file upload, But what about for file download?  is there any guide for it?

@darmenliu which version of OAS are you using?

Closing due to inactivity - but please feel free to reopen the issue if necessary.


Add coverage badge

I was looking at code coverage setups and realized there's no badge specific to the current coverage.
NOTE: I will be adding this to the core code after the gradle migration. I believe it's a similar number.

Good call, I think I added the badge before there was any coverage.


Workflow Foundation: XamlAppDef

I'm trying to do a similar thing for Workflow Foundation XAML Activities.
A typical activity item is added to a csproj as follow:
<ItemGroup>
    <XamlAppDef Include="Activity1.xaml">
      <Generator>MSBuild:Compile</Generator>
      <SubType>Designer</SubType>
    </XamlAppDef>
  </ItemGroup>

What would be required to make this work, similar to WPF XAML?

The trick here, is around the implicit includes and what they should be. WPF, UWP, Workflow, and XamForms, all use the XAML file extension and need to be included in different ways.
Question is how to tell them apart in a meaningful way.
I wonder if it'd be enough if the project had something like:
 <XamlAppDef Include="Activity1.xaml" /> or a glob  <XamlAppDef Include="myactivities/*.xaml" />
in your project file. In that scenario, it's easy to add the additional metadata (Generator and Compile)

I did something like this:
At least for .NET Framework, I did like this
https://github.com/nirin/msbuild-sdks/blob/develop/TestProjects/Windows.PresentationFoundation.Application/Windows.PresentationFoundation.Application.csproj#L3-L8
https://github.com/nirin/msbuild-sdks/blob/develop/TestProjects/Windows.Forms.Application/Windows.Forms.Application.csproj#L3-L9
Still what if a project has a mix of WF, WPF, WWF, ASP.NET, etc... I had one project like that before I split that up but this seems a perfect excuse to cook that up again.
I was also thinking up of rules like *Page*, *Activity*, *Flow*, *App*, *Window*, *Form*, *Dialog*, etc... just like #47 to include TFMs either as a parent folder or part of a filename.


Use serde-indexed to optimize the size of resident credentials

Requires https://github.com/nickray/cbor-smol/pull/8
Thankfully serde's default deserialization support both deserializing with fields as integers, and deserializing with fields as str. So there is no need for manual deserialization code.

We could potentially implement migrations to the new format too, but that would make it much more complex.

Replaced by #59


fix: dataset list panic

Fixed the following panic issue.
./observe list dataset
list: panic: type "dataset" doesn't have property "dataset"

@jwatte Can you please review the PR? thanks


orcania: 2.0.0 -> 2.0.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/orcania/versions.
meta.description for orcania is: '"Potluck with different functions for different purposes that can be shared among C programs"'.
meta.homepage for orcania is: '"https://github.com/babelouest/orcania"
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.0.1 with grep in /nix/store/1bhydkr75lv1nfxqn70lc6v7lykcag7k-orcania-2.0.1
directory tree listing: https://gist.github.com/173d211ceb2d74aac40eb9933604c6fd
du listing: https://gist.github.com/ea6edd1410df5799ecd670e783e561a7

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
orcania
yder

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1bhydkr75lv1nfxqn70lc6v7lykcag7k-orcania-2.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A orcania https://github.com/r-ryantm/nixpkgs/archive/ab9287c98fa99c4667e03acb3ba87b900c63b8c3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1bhydkr75lv1nfxqn70lc6v7lykcag7k-orcania-2.0.1
ls -la /nix/store/1bhydkr75lv1nfxqn70lc6v7lykcag7k-orcania-2.0.1/bin

cc @johnazoidberg for testing.

Included in #65966


API Gateway request integration does not support for VPC_PROXY integration.

HI,
In API Gateway it supports to have VPC Link integration with "Use Proxy Integration" is set to True. So it takes the type as VPC_PROXY.
CloudFormation they have "connectionType" to handle this VPC_LINK.  https://docs.aws.amazon.com/apigateway/api-reference/resource/integration/#type
But it seems this property is missing in the troposphere APIGateway Integration class (https://github.com/cloudtools/troposphere/blob/master/troposphere/apigateway.py).
Please correct me if I am wrong here.
So would like to know is there any time frame that you will include this feature ?
Thanks in advance.
Nirosh

It's not a CloudFormation property, it's just AWS API - CloudFormation (surprisingly) doesn't cover 100% of the API.


Expose AudioContext

Hi,
I'm using Crunker in a small rhythm game prototype; I need the current playback time which you can normally get from AudioContext.prototype.getOutputTimestamp, but I'm unable to do this since Crunker isn't exposing the audioContext.
Is it possible to expose this, or against the design philosophy?

I believe previously it was actually accessible by calling crunker._context. After the typescript refactor this may no longer be possible which could be considered a breaking change.
I see no reason not to expose the context and many reasons (such as your's) to expose it to be interfaces with.
I believe this will only make the library more powerful.
If you'd like to create a PR and to add a getter, for example, which returns the context then please go for it and I'll create an npm release shortly after. Otherwise, if you're unsure how to do this then I'm happy to help.
Do you want to have a go at extending the functionality first. Please also update the docs with the methods as well.
Hope this helps.

I agree in this situation, too.
The Typescript refactor hasn't changed this, but has made it more clear that access to this is considered private API. In JavaScript there isn't any way to restrict access to class attributes, hence the private access modifier is more documentation than anything else.

Does typescript intellisense autocomplete or suggest for private properties though, that may be part of the confusion here. I actually don't know if it does or not, would be easy to test I suppose.

No, you're right, it would not.

I agree in this situation, too.
The Typescript refactor hasn't changed this, but has made it more clear that access to this is considered private API. In JavaScript there isn't any way to restrict access to class attributes, hence the private access modifier is more documentation than anything else.

Using # instead of _ work for private attributes/methods: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields

Yes, but that's only supported in very recent browsers, most notably iOS 14.5+, which could significantly limit Crunker's usefulness.

I think that private/public things is just for the developer experience, the final user will not ever notice this difference. And the developer can edit the source code on his machine and use whatever he want. So its not like hiding private keys or something...
The library is already in TS, I'm not suggesting going back to JS just for this...

@lmiller1990 would you like to create a PR for this and become a contributor, or one of us can implement the PR for you. Will be a very minor change really.

Whoever gets there first, it's like a 2 liner. I might have time this weekend - seems like there's a lot of momentum behind this feature; as long as we are all in agreement, anyone can write the code/make the associated PR :)

Ok, PR https://github.com/jackedgson/crunker/pull/67


Will the code of SemVLP model  be released?

Thanks for the attention. We will release more VLP models later with the update progress of AliceMind.