can not connect with mobile to vtrust-flash ssid

Hi
running the proces on a respberry.
vtrust-flash hotspot ap is coming up
but can not connect to it with the mobile
raspberry crashes, can not enter anything on the keyboard, seems that hotspot is still up but no connection possible
what am I missing?
thanks for your support

Could be #409 or #373

ok thanks will check
where do I find the log files?
I was working on the raspberry without ssh.
ap vtrusth-flush is up but cvonfig is still
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
inet6 fe80::76da:38ff:fe7f:b271  prefixlen 64  scopeid 0x20
ether 74:da:38:7f:b2:71  txqueuelen 1000  (Ethernet)
RX packets 2834  bytes 378263 (369.3 KiB)
RX errors 0  dropped 7  overruns 0  frame 0
TX packets 36  bytes 5954 (5.8 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Thanks

Hi still can no connect
after deleting of the modprob exclude and wlan setting at least I get the ip config required
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
inet6 fe80::76da:38ff:fe7f:b271  prefixlen 64  scopeid 0x20
ether 74:da:38:7f:b2:71  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 10159  bytes 1846009 (1.7 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
But mobile can not connect
where a the logfiles?

After you pulled the latest from git, did you uninstall sslpsk and run install_prereq again?

Hi, how to  uninstall sslpsk?
I will do a clean install again

After you pulled the latest from git, did you uninstall sslpsk and run install_prereq again?

no just a new pull, so will do a new clean install

sudo -H pip3 uninstall sslpsk
sudo -H python3 -m pip uninstall sslpsk

ok thanks will try

Hi Colin,
after running install_prereq again. I got :

Installing collected packages: sslpsk
  Running setup.py install for sslpsk ... done
Successfully installed sslpsk-1.0.0
Ready to start upgrade
pi@RPI2_ST_PX_157:~/tuya-convert $ sudo apt-get upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete sind zurückgehalten worden:
  wolfram-engine
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.

running apt upgrade, -> noting to upgrade?
so what is expected to do after this message?
Successfully installed sslpsk-1.0.0
Ready to start upgrade

so now , I think I have a clean new installatoion.
But mobile is not connecting to ssid vtrust-flash
see logs
Thanks for the great support!!
smarthack-mqtt.log
smarthack-udp.log
smarthack-web.log
smarthack-wifi.log

No psk log?


[feature request] add support for enterprise routes

I occasionally run into situations where the api.github.com routes aren't sufficient enough when working with GHE, so it would be great if you considered adding at least the latest version of the GHE routes.

To grab the GitHub Enterprise Server (GHES) routes:

https://octokit.github.io/routes/routes/ghe-2.16/index.json
https://octokit.github.io/routes/routes/ghe-2.16/index.json
https://octokit.github.io/routes/routes/ghe-2.17/index.json
etc

Since we're already processing the octokit routes for the standard API, I assume this wouldn't be TOO difficult to implement. I may take this one on, /cc @swinton

Working on it in #45.

Enterprise routes are now generated for all currently supported versions of GitHub Enterprise Server:
https://github.com/swinton/github-rest-apis-for-insomnia/tree/master/routes


WebNews: new module to handle site news stories and present them to the user through a dedicated interface and discreet notifications

Originally by nkasioum (@kasioumis) on 2013-02-07
Users are often interested in reading about all the significant changes on the site, in the form of news, concerning usability, appearance, content etc. At the same time administrators want to keep a history of all those news. The WebNews module suggests the creation of an infrastructure that will enable the administrators to add and manage news and the users to be informed at will through complete articles as well as through discreet notifications in the form of tooltips. Read more at the WebNews RFC wiki page.
Development: see master-webnews branch.

see https://github.com/inveniosoftware/invenio-news


207 numeric input component

What is the context of this PR?

This PR introduces a number spinner component.
How to review
All tests should pass.
Component should match the design.
Behaviour should work as expected (up button increases number, down button decreases number).

 Numeric input component (2)


Remove TextControl from Control hierarchy

The abstraction of TextControl doesn't seem to serve any clear purpose. In particular, there isn't a clear need to iterate over disparate types of text controls (Label, Button, Window, etc.), and manipulate each of their text values through a common interface. I propose removing the TextControl from the Control hierarchy. Any text manipulation methods can be moved to the derived controls.

I'm not really sure why these functions were moved out of the base Control. Every control should have the ability to have some form of text associated with it. Whether that text is drawn or not is irrelevant.

Ehh, I'd rather not have text fields in controls that don't logically have text.

It's a fair point, but I will put out there that every control in the Win32 API has a text field.
That stated, this isn't an attempt at cloning the Win32 API, just that there are some design choices that I modeled this GUI code off of. :)

I was looking back at this. There are two main features supported by TextControl:

Getting and setting text
Managing onTextChange events

The onTextChange event is only particularly relevant to TextField. That is the control that allow for user input, and so may receive new text input at arbitrary times. The other controls, such as Label, Button, CheckBox, RadioButton, and TextArea can only have the text changed programatically, which means the caller will always know exactly when the text is changed, so there is little need for event handling.

It's not super obvious where TextArea is used. It sounds like the control might permit free form multi-line text entry, but the control actually has no code support for text editing, and there is nowhere in the game that permits multi-line text editing. Instead, it seems TextArea is just a multi-line Label control. It's not clear why the Label control couldn't be used in it's place. The TextArea control is currently used in three places:

PlanetSelectState for mPlanetDescription field
NotificationWindow for the mMessageArea field
FactoryReport for the txtProductDescription field

It may make sense to move the onTextChange event support code from TextControl to TextField. That way we don't waste space in the other derived controls that don't need that support. We should also look into potentially using Label to replace TextArea in the three places it's used.

TextArea is intended as a an area with wrapped text. The Label control could be used in this way with a flag for 'text wrapping' as a boolean. E.g., when it's turned on the text will wrap, etc. Label was added after the fact by another developer I think.
I'm fine with combining these into one control.


Add support for checking request limits per hour

Untappd only allows 100 requests an hour. Despite caching for 10 minutes, it is possible that something could be going flaky for someone and things don't get transient cached.

In master branch


AWS: Public RDS/EBS snapshot

Feature request
Title: AWS: Public RDS/EBS snapshot
Description:

It would be good to add AWS public RDS/EBS snapshot check.

[optional Relevant Links:]

https://www.cloudconformity.com/knowledge-base/aws/RDS/public-snapshots.html
https://asecure.cloud/a/rds-snapshots-public-prohibited/

Just to make sure I understand, is this feature request asking to add RDS DB snapshots as nodes to the graph?

Add RDS DB snapshots as nodes.
Check the value of DBSnapshotAttributes/AttributeValues

It would be good to add an analysis job.

Ah interesting:

From: https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DBSnapshotAttribute.html
The attribute named restore refers to the list of AWS accounts that have permission to copy or restore the manual DB cluster snapshot. For more information, see the ModifyDBSnapshotAttribute API action.

I'm assuming you're thinking of an analysis job that would connect snapshots to the AWS accounts that are allowed to restore them?

I'm just considering to check whether AttributeValues are all.
It means any AWS user account can restore snapshots.

Ah I see, yeah that's super interesting.
We can't make any commitments on adding this feature at the moment but I like the idea a lot.  If others have cycles to add/modify an intel module we'll be happy to give guidance.


Subscriptions documentation

If I do a metadata request I find some information about subscriptions but cannot find any documentation on it.
        <EntityType Name="subscriptions">
            <Key>
                <PropertyRef Name="subscriptionId" />
            </Key>
            <Property Name="subscriptionId" Type="Edm.String" Nullable="false" MaxLength="150" />
            <Property Name="notificationUrl" Type="Edm.String" />
            <Property Name="resource" Type="Edm.String" />
            <Property Name="userId" Type="Edm.Guid" />
            <Property Name="lastModifiedDateTime" Type="Edm.DateTimeOffset" />
            <Property Name="clientState" Type="Edm.String" MaxLength="250" />
            <Property Name="expirationDateTime" Type="Edm.DateTimeOffset" />
        </EntityType>

have to do a post with something like:
{
"notificationUrl":"your-url",
"resource": "https://api.businesscentral.dynamics.com/v1.0/api/beta/companies(company-id)/items"
}
it then sends a POST request to your-url with a validation token and then i'm lost...

Hello, thanks for your feedback. We are just about to release docs on subscriptions, so stay tuned - docs will be refreshed (here)[https://docs.microsoft.com/da-dk/dynamics-nav/fin-graph/].

Hey there - just pushed the docs for subscriptions that we have live. Thanks for your interest. Closing this issue for now.

Great!


Wiki codes out-of-date?

MC version: 1.16.1
Cardinal Components Version: 2.4.2
Hi I tried the wiki example to register a component. I have a question regarding this.
public class Handler_Components implements EntityComponentInitializer {

    public static final ComponentType<IComponentFloat> FLOAT_COMPONENT_TYPE =
            ComponentRegistry.INSTANCE.registerIfAbsent(new Identifier("eltcore:float"), IComponentFloat.class);

    @Override
    public void registerEntityComponentFactories(EntityComponentFactoryRegistry registry) {
        registry.register(FLOAT_COMPONENT_TYPE, IComponentFloat::new);
    }
}

This method does not work because it requires three components.
registry.register(FLOAT_COMPONENT_TYPE, IComponentFloat::new);
And my entry point is added.
"entrypoints": {
    "cardinal-components-entity": [
      "net.moeg.eltcore.handlers.Handler_Components"
    ]
  },

I saw in the source saying that many of these above methods are experimental or scheduled to be removed. Can you recommend a stable version to use Cardinal-Components-API? I like the mod's utility very much.

This method does not work because it requires three components.

Entity components require you to tell the API what type of entity the component should be attached to, by passing the entity class. see the javadoc comment on that interface.

I saw in the source saying that many of these above methods are experimental or scheduled to be removed.

The V3 api is somewhat in flux still, it will be promoted to stable in 1.17.
If you don't want that, use the old way of registering component factories via the respective events instead.


Methods are not overridden by the child class's implementation

If I have a serializer, TopLevelSerializer with a MethodField which uses a method get_thing to calculate the value of the field, when I create another serializer which inherits from TopLevelSerializer and re-implement get_thing on that child class, I expect the child class's implementation of get_thing to be called when I serialize an object with the child class. However, the TopLevelSerializer's implementation is always called. This breaks the standard way that inheritance is supposed to work in Python.

The above PR just demonstrates the issue at the moment. I'll try and get a fix together in the meantime.

Well, I goofed that up. Still working on a test to reproduce the issue I'm seeing in my application. Might actually be an error on my end after all...

Ugh, my bad, had my MRO confused. Schoolboy error :/


Replace session stickiness with source pinning

Continuing the discussion here: https://github.com/dagger/dagger/pull/3421#issuecomment-1296089591
This is all just my interpretation and summary of that discussion, @vito please correct me if I misrepresent anything.
Problem
Buildkit sessions are hard to work with as is. They result in certain state being sticky for the duration of a client connection. But once that connection is closed, you can't resume the session or otherwise reobtain that sticky state.
Examples of state associated with sessions:

Resolution of container image tags to digest (i.e. mapping :latest to an image SHA)
Resolution of git refs to commit SHAs
Synchronization of HTTP sources
Synchronization of local directories
Blocking of cache reference pruning (i.e. anything in buildkit's cache that you have touched during your session won't be able to be pruned until the session has ended)
Gateway containers (i.e. what we use to implement services)
(Maybe) Temporary cache of "no-cache" vertices

Forcing all the above to be intricately tied to a single client connection is limiting to our architecture and makes it much harder to enable "seamless reproducibility" on behalf of our users.
For example, in the current state of things if a user submits a query that references the main branch of a git repo, they can only be guaranteed to be using a consistent mapping of main->commit sha for the duration of their client object due to the fact that the client object is one-to-one with buildkit sessions.

This means that we are completely tied to always having client objects maintain a single continuous connection with a single remote engine and that connection must be one-to-one with a buildkit session in order to guarantee source consistency. This rules out a lot of possible architectures and other changes.

Possible Solutions
One possible solution to items 1 through 4 above (image, git, http and local sources) is to enable "source pinning" as a separate feature to replace session stickiness.

There's also some overlap w/ 5 above. 6 is a different problem probably.

Two variations (among many more possibilities) on how this could work are:
A) Pin sources in returned IDs
When an ID of an object is resolved, all sources that use non-pinned references (i.e. latest, main, etc.) are replaced with pinned versions. So if you do
Container().From("alpine:latest").ID()

The ID that is returned to you won't contain latest, it will contain the SHA that latest resolved to.
Same would be true for all the other source types (how this could work for local dirs is mentioned below).
Pros:

Pretty easy to understand both for us and for users (also probably relatively easy to implement)

Cons:

We need to think through cases where a single client could end up resolving the same reference to different pinned versions, could result in surprising behavior at times.
Wanting to retain pins across different client instances becomes a matter of re-using IDs, so we'll be committing to making IDs re-usable in this case (I think, could be wrong). That itself has a lot of implications that need thinking through.

B) Support source pin policies attached to queries
Buildkit will likely soon have support for attaching policies that enable not only pinning but also more complex rules for where to obtain a source from: https://github.com/moby/buildkit/pull/2943
Buildkit also already returns "BuildInfo" metadata from solves that can be used to determine which specific sources were resolved in the solve. Apparently support for SLSA provenance info is in the works too: https://github.com/moby/buildkit/pull/3240
We could use these features in combination with one another to support highly configurable policies that would be capable of modeling both the current behavior where pins last the duration of a session but also quite a bit more.
e.g.
// Clients are now internally initialized with a pinning policy. By **default**, it's initially empty
// You can also optionally provide something like `WithSourcePolicy` to Connect
client, err := dagger.Connect()

// When you use the client, it sends the pinning policy alongside each request.
// Here's it's empty, so "alpine:latest" will be resolved to a SHA by the builder.
// That SHA gets returned to you w/ the query result.
// Client will then (by default) update its own pinning policy to now use that SHA
_, err := client.Container().From("alpine:latest").Exec(...).Stdout()

// So then future queries from the same client will use that new pinning policy
// e.g. this will tell buildkit to use the same SHA rather than resolving latest
_, err = client.Container().From("alpine:latest").Exec(...).Stdout()

// The above is just the default behavior for users who don't care and want the same degree
// of stability that sessions previously provided (sources are sticky for the duration of
// the `client` object).
//
// There'd also be interfaces on `client` for reading+modifying the pinning policy for users who care about that
// (either because they want to or their company forces them to, etc.).

Pros:

May be more aligned with the features buildkit is starting to provide, could make life easier for us in the long run.
Source policies are detached from IDs, so we don't have to tie ourselves into making IDs reusable necessarily. More flexible in that respect.

Cons:

Pretty complicated. If we can get the "default path" easy so users don't need to understand all of this right away, then maybe it's okay. But if every users needs to learn about all this to use Dagger then it's probably not a good path.

Pinning Local Dirs and HTTP Sources
Container image and Git sources are nice in that when you resolve a non-pinned reference to a SHA, you can still obtain the source from that SHA. I.e. if I resolve latest->sha:1234 I can pull the image using just sha:1234 later. Basically, they come from content addressable stores.
Local sources and HTTP sources are different in that arbitrary local filesystems and arbitrary http web servers are not content addressable stores. You can't sync a local dir, calculate its content checksum and then later ask the local filesystem for the contents based on that checksum (I think some filesystems have abilities similar to this, but it's far from universal).
I think this might be okay though. If we support pinning those resources based on their content checksum, that just means that buildkit needs to search its cache as the content addressable store. If it doesn't have it anymore (or never did), then an error is returned.

Basically, if the user tries to reproduce something that can't be reproduced, error out.
We'll need to think through how to make this a nice experience though not a frustrating one.
This is where point 5 in the list of session state above becomes relevent. We may need to do things with time based containerd leases that buildkit uses internally. This is too much of a tangent for now, but needs more thought.

I'm just dumping this as is to start getting more thoughts. Next steps would be to write out in more detail specifically what this would look like in the context of the other changes we want to make in terms of the engine archictecture.

Does this also include the problem of scoping cache volume names, or is that unrelated?

Does this also include the problem of scoping cache volume names, or is that unrelated?

Good question, I think this isn't necessarily tied into that namespacing problem, but there might be potential for them to have overlapping or at least conceptually similar solutions.
Thinking out loud:
For example, if you submit a query that internally gets the ID of a cache volume, then maybe the ID returned to you can be namespaced somehow (very similar to what's described in Solution A above).
Or maybe there's a way of attaching namespacing information to queries that impact which cache volume is ultimately used when your query is executed (very similar to what's described in Solution B above).
So, probably something we need to design separately while keeping in mind the implementations could have meaningful overlap?

@sipsma I'm guessing this change (https://github.com/moby/buildkit/pull/3332) will be helpful for implementing source pinning? Looks like that dropped in the v0.11.0-rc2 buildkit release

@jlongtine

I'm guessing this change (https://github.com/moby/buildkit/pull/3332) will be helpful for implementing source pinning? Looks like that dropped in the v0.11.0-rc2 buildkit release

Yep! That's the follow up of the PR I linked in the description, glad to see it got in for v0.11. Still need to figure out whether+how we can integrate this w/ dagger, but it's pretty powerful and nice to have that flexibility when needed.

That's awesome! I can see it coming in handy!


Openreader: Implement  entity interfaces

https://docs.subsquid.io/reference/openreader-schema/interfaces
Under the hood we should just implement additional top level resolver, which would do SELECT ... UNION ALL ... for each entity implementing the interface.
We can do that as part of our subscriptions effort #13 .

Solved by #115


enable declarationMap flag

Go to JS file when using IDE functions like "Go to Definition" in VSCode.
See https://www.typescriptlang.org/tsconfig#declarationMap

It won't work since the source code is not included in npm packages.

@promer94 thanks for spotting the files attribute content.

they should not be included in a published NPM package

sounds like an opinion, many developers jump to definitions in any context.

Thanks for the PR. We expect users to use the published and bundled types which tree-shake out the internal types and only keeps the exported types. like types of swr core. Since the source files may change and may have more inrelavant or internal purposed types, we don't want users to jump between the original sources.


Upgrade JDKs used by GitHub Actions builds

Suggested commit message:
Upgrade JDKs used by GitHub Actions builds (#521)

Additionally:
- Update the example version numbers mentioned in the issue template.
- Drop some redundant whitespace from `SourceCodeTest` test code.
- Sort some compiler arguments.

See:
- https://www.oracle.com/java/technologies/javase/11-0-17-relnotes.html
- https://www.oracle.com/java/technologies/javase/11-0-18-relnotes.html
- https://www.oracle.com/java/technologies/javase/17-0-5-relnotes.html
- https://www.oracle.com/java/technologies/javase/17-0-6-relnotes.html
- https://www.oracle.com/java/technologies/javase/19-0-1-relnotes.html
- https://www.oracle.com/java/technologies/javase/19-0-2-relnotes.html

(Added one more commit.)


Add tests in keyring package

Although we have unit tests for the keyring package in, there are still several error paths in KeyRing.SignPSBT() that don't have unit tests to exercise them. We also don't currently test the taproot script commitment paths. We should add tests for these parts of the code.

Duplicate of https://github.com/NYDIG-OSS/lndsigner/issues/12


[Feature request]: Easier way to listen to DB tables

General Info

[X] I installed the latest version of Supabase Kt
[X] I checked for similar feature requests

Feature request
Just like Supabase Dart Client's .stream() method:

The Kotlin client should also have a similar mechanism to easily start observing a table in the DB. Right now, I have to create a callBackFlow, manually read and emit the current DB value (using supabaseClient.postgrest["my-table"].select()) to initialise the flow, and only then am I able to observe further changes in the DB table.
I would like to be able to start observing the flow with some initial value. That would reduce a lot of boilerplate code for most users.
Usecase
A very common usecase would be to observe DB tables that I believe all users of this library will do on a frequent basis.

I'll make a PR soon, but won't include this in the 2.0.0 coming out this week/next week.

Hey.. same person here.. the other one is my account only.

I'll make a PR soon, but won't include this in the 2.0.0 coming out this week/next week.

Sure, no issues, that works for me 👍🏻

One more request @jan-tennert , please let me know if I should create a separate feature request ticket for this.
Is it possible in the library's current state to do something like this?
fun observeUser(userId: String): Flow<List<User>> {
   return channel.postgresChangeFlow<PostgresAction>("public") {
       table = "users"
       filter("id", FilterOperator.EQ, userId)
   }
}

In essence, I want to be able to simply start observing a table without having to deal with all the separate PostgresActions (i.e. DELETE, SELECT, INSERT, UPDATE). I just want a list of items (or a single item) that is kept updated with the latest DB changes. I will then only be concerned with collecting values and handling exceptions.
If it is not possible in the library's current state, do you think it's a good idea to implement it? And what would go into the efforts to make something like this possible?

So the Realtime module doesn't save any data itself and I think that is the best solution for now because the general idea is that you just receive events when something changes and nothing more (like the js library).

So the Realtime module doesn't save any data itself and I think that is the best solution for now because the general idea is that you just receive events when something changes and nothing more (like the js library).

It's not necessary to make changes in the realtime module directly. Maybe we could create an extension module called extensions and implement this (and other such experimental features) in that module for people to test out and give feedback on without having to hamper the original modules at all. What do you think?

So the Realtime module doesn't save any data itself and I think that is the best solution for now because the general idea is that you just receive events when something changes and nothing more (like the js library).

It's not necessary to make changes in the realtime module directly. Maybe we could create an extension module called extensions and implement this (and other such experimental features) in that module for people to test out and give feedback on without having to hamper the original modules at all. What do you think?
Slowly and gradually once the features in the extensions module start getting more stable, they can be promoted into the appropriate modules (like postgrest, realtime, etc).

So what you are describing is essential that the library takes care of caching the data in memory, that may be a good usecase for a new plugin.

So what you are describing is essentially that the library takes care of caching the data in memory, that may be a good usecase for a new plugin.

That is up to you (the library owner) to decide if it's good enough or not. It's totally understandable if it doesn't align with the goals of the library.
Being a consumer of the library, those were my 2 cents based on my own experiences that might save some time and effort for other consumers as well.
It's alright even if we decide to not move forward with the approach 👍🏻

The idea is perfect for a plugin, but I'd leave the main modules without these extras. We could have a plugin Caching (or some better name), which builds on top of Realtime & Postgrest, providing essentially the same methods but with the features you suggested

So what you are describing is essentially that the library takes care of caching the data in memory, that may be a good usecase for a new plugin.

That is up to you (the library owner) to decide if it's good enough or not. It's totally understandable if it doesn't align with the goals of the library.
Being a consumer of the library, those were my 2 cents based on my own experiences that might save some time and effort for other consumers as well.
It's alright even if we decide to not move forward with the approach 👍🏻

The idea is perfect for a plugin, but I'd leave the main modules without these extras. We could have a plugin Caching (or some better name), which builds on top of Realtime & Postgrest, providing essentially the same methods but with the features you suggested

That would be perfect! Thank you @jan-tennert 🙌🏻

Hey

So what you are describing is essentially that the library takes care of caching the data in memory, that may be a good usecase for a new plugin.

That is up to you (the library owner) to decide if it's good enough or not. It's totally understandable if it doesn't align with the goals of the library.
Being a consumer of the library, those were my 2 cents based on my own experiences that might save some time and effort for other consumers as well.
It's alright even if we decide to not move forward with the approach 👍🏻

The idea is perfect for a plugin, but I'd leave the main modules without these extras. We could have a plugin Caching (or some better name), which builds on top of Realtime & Postgrest, providing essentially the same methods but with the features you suggested

That would be perfect! Thank you @jan-tennert 🙌🏻

Hey, so I'm going to scrap the idea of emitting the initial data in the Realtime module and include this functionality in the plugin instead. I got a preview working, currently looking like this (method & property names subject to change):
val table = client.postgrestCaching.from<Message>("messages")
val dataFlow: Flow<List<Message>> = table.listFlow(filter = "channel_id=eq.5") { it.id.toString() } //provide the primary key
dataFlow.collect {
    println(it)
}
//or for a single item
val dataFlow: Flow<Message> = table.dataFlow("id=eq.12") //provide a filter
dataFlow.collect { //Note that the flow closes when the item is deleted
    println(it)
}

What do you think about that?

Hey

So what you are describing is essentially that the library takes care of caching the data in memory, that may be a good usecase for a new plugin.

That is up to you (the library owner) to decide if it's good enough or not. It's totally understandable if it doesn't align with the goals of the library.
Being a consumer of the library, those were my 2 cents based on my own experiences that might save some time and effort for other consumers as well.
It's alright even if we decide to not move forward with the approach 👍🏻

The idea is perfect for a plugin, but I'd leave the main modules without these extras. We could have a plugin Caching (or some better name), which builds on top of Realtime & Postgrest, providing essentially the same methods but with the features you suggested

That would be perfect! Thank you @jan-tennert 🙌🏻

Hey, so I'm going to scrap the idea of emitting the initial data in the Realtime module and include this functionality in the plugin instead. I got a preview working, currently looking like this (method & property names subject to change):
val table = client.postgrestCaching.from<Message>("messages")
val dataFlow: Flow<List<Message>> = table.listFlow(filter = "channel_id=eq.5") { it.id.toString() } //provide the primary key
dataFlow.collect {
    println(it)
}
//or for a single item
val dataFlow: Flow<Message> = table.dataFlow("id=eq.12") //provide a filter
dataFlow.collect { //Note that the flow closes when the item is deleted
    println(it)
}

What do you think about that?

This looks very promising 🙌🏻 and very similar to Flutter's approach 👏🏻 and one concern I saw about this approach by the community was that there's no way to implement a more complex filter with 2 or more items. It only accepts a single filter.
Here's that issue:
https://github.com/supabase/realtime/issues/303
If this is somehow worked around in the Kotlin library, that would be very exciting!!
I also do accept that this is ideally an issue for the realtime module itself and not for us to fix. So it's perfectly fine if we're not able to work on it 👍🏻

@shubhamsinghshubham777 Moving this thread to https://github.com/supabase-community/supabase-kt/discussions/379

Drafted the syntax: #386. Let me know what you think!

Drafted the syntax: #386. Let me know what you think!

Sure! Super excited to try it out.. thanks for the quick implementation 🌟

Drafted the syntax: #386. Let me know what you think!

This looks very good to me @jan-tennert 🚀
Although it's definitely not important for now, but If I were to nitpick, I would take a look at the syntax of listFlow:
inline fun listFlow(
        filter: String = "",
        crossinline primaryKey: (Data) -> String,
    )

Maybe instead of just asking for a String as filter, we can make the API a little easier for the users by writing it as follows:
inline fun listFlow(
        column: String,
        filterOperator: FilterOperator,
        filterValue: Any,
        crossinline primaryKey: (Data) -> String,
    )

or maybe even shorten it down to:
inline fun listFlow(
        filterOperation: FilterOperation,
        crossinline primaryKey: (Data) -> String,
    )

like you've already done before.
We can internally handle a few common usecases (like List filterValue(s)). For example, it's very common for people to use the IN filter operator and pass a List/Array of items. The new syntax would make it as simple as:
val messageFlow: Flow<List<Message>> = table.listFlow(
    filterOperation = FilterOperation(
        column = "id",
        filterOperator = FilterOperator.IN,
        filterValue = listOf("1", "2", "3"),
    ),
    primaryKey = Message::id
)

There's an isIn filter block in PostgrestFilterBuilder that we can reuse in listFlow implementation when we detect that filterValue is List:
https://github.com/supabase-community/supabase-kt/blob/dd66f129f50f6e5c9263a26e9f3ebb5652d3c043/Postgrest/src/commonMain/kotlin/io/github/jan/supabase/postgrest/query/filter/PostgrestFilterBuilder.kt#L133-L136

@shubhamsinghshubham777 Good idea, I'm probably integrating this simpler filter syntax for the base Realtime module too. Besides that I also plan to provide the same caching for Realtime Presence data, so you don't have to care about presence joins & leaves and just get a list of connected users.

@shubhamsinghshubham777 Good idea, I'm probably integrating this simpler filter syntax for the base Realtime module too. Besides that I also plan to provide the same caching for Realtime Presence data, so you don't have to care about presence joins & leaves and just get a list of connected users.

That's awesome @jan-tennert! I'm excited about it 🙌

Also very excited about this - would make using and filtering realtime data so much easier!

Also very excited about this - would make using and filtering realtime data so much easier!

Great to hear that! I'm currently still thinking about the syntax. @shubhamsinghshubham777 I updated the PR again, but now these new methods are integrated within realtime because of some design issues with a completely new plugin. Let me know what you both think!

Also very excited about this - would make using and filtering realtime data so much easier!

Great to hear that! I'm currently still thinking about the syntax. @shubhamsinghshubham777 I updated the PR again, but now these new methods are integrated within realtime because of some design issues with a completely new plugin. Let me know what you both think!

Just skimmed through it and the current API seems good to me @jan-tennert ✅

Also looks good to me, looking forward to using it!


Webpack crash on nodejs@12

Bug report

What is the current behavior?
If use nodejs@12, webpack crash with error:
MacBook:~/www/$ webpack

#
# Fatal error in , line 0
# Check failed: U_SUCCESS(status).
#
#
#
#FailureMessage Object: 0x7ffeefbf4fc0Illegal instruction: 4
MacBook:~/www/

If the current behavior is a bug, please provide the steps to reproduce.

nvm use 12
npm i webpack webpack-cli
./node_modules/.bin/webpack

What is the expected behavior?
Any, at least run

Other relevant information:
webpack version: 4.X.X and 5.X.X-alpha.X
Node.js version: 12.0.0
Operating System: Mac OS X
Additional tools: nvm

Thanks for your report. It would be great if you reduce your issue to a small reproducible example. Best put this example into a github repository together with instructions how to get to the problem.

same issue here, when running an Aurelia project with au run --watch
it shows
`#
Fatal error in , line 0
Check failed: U_SUCCESS(status).

#FailureMessage Object: 00000090F37ADDC0the node version isnode --version
v12.0.0`
so the example maybe just create a new aurelia project

Thanks for your report. It would be great if you reduce your issue to a small reproducible example. Best put this example into a github repository together with instructions how to get to the problem.

@montogeek for reproduce issue you not need project. Just go this code:
cd /tmp && npm i webpack webpack-cli && ./node_modules/.bin/webpack
it is only important - node.js version: 12.0.0

我也发现了这个问题，webpack-dev-server在nodev12的环境下不能要运行。而vue-cli和Create-react-app都是用到了这个包。目前我的解决办法是把node环境降级到v11.5

I think problem in webpack-dev-server, please create minimum reproducible test repo

I am getting the same result, taking the reproducing steps that OP provided. Any create-react-app that is based on webpack is now broken with node 12.0.0.

Currently, this problem does not occur in Node12.1.0 so I'll close.

cd /tmp && npm i webpack webpack-cli && ./node_modules/.bin/webpack

I confirm, updating to node 12.1.0 fix the issue.


Question regarding transitions

Well, lit-element and lit-html are some of the best tools in web app developement.
And it could provide more opportunities if a solution on this matter was documented or a directive was provided. I looked at previous issues but they haven't progressed further for a while.
When will such a directive or doc come to lit-html? Are there any plans?

What specifically are you referencing?

@justinfagnani I mean #1017 & #1018.

Any updates would be in #1017. Let's keep the conversation there so we don't create too many open issues.
Our team road map is here: https://github.com/Polymer/project/blob/master/Roadmap.md and we're currently focusing on SSR. I've been experimenting with animation directives on the side though, and if I have updates I'll post them to #1017.


Cesium3DTileset flickers in large data.

What happened?
Thank you for a great work. I found a strange behavior, let me share it.
Some features of Cesium3DTileset are flickering when they are loaded. It means the feature is displayed once, but it's disappearing at the moment.
I think it should be caused by cachesSize option. The data has large texture, so it occupies large memory. Then some features are disappear. I think it's correct behavior, but it keeps flickering.
Reproduction steps

Load 3D Tiles
Move camera to the displayed feature's position.
Wait few minutes
As soon as some features are appear, it's disappear. It's happened repeatedly.

Sandcastle example
https://sandcastle.cesium.com/#c=5Vp5byI5Fv8qHjRSw2xS3AlJh2g7hJlGSzqtgZ5RqysipsqAO8YuVbkg7CjffZ/tOrkz3TvS7vwDKftdfsfvPRcpl9E7FNC5xwhyyVwgMUH1WzSkjARoQrAMfYI86jxRPkVLKmdoJhbER5i7KCCMOBKNyQwvqPBtXi6jm5AyV9G6WGLkiNCXJFgpqR8+d9C9R/it2vCELzG7RDMpvctyeblcVi2+cqypWJQDKknZFVTKMuVUUizpggTluns6joRbHp4SmzuCBxItKFmCQW3EyRJ1SEDDufWbXivaBUc/dwSXmHLi24UT9IfNEZLE92HlMmYYmmdr4ov578JnbrRQLJ3Y/KX01uY2N4qswCGcWFMmxsRyiSdnQxLId1MgDmTEBcZIPySaC3wyIBLJGUHmNAw5eE58rA1HUiAmxBPCEt1hPsNSYh6fLKL/KMAjVCipkbUdrLxKMa9rg2/J1CckKKqDVesX1tlFvVo9q9UblfPGRetELdeb1lmr2mieXTRa9XrzrKFXz5t1m6vD5fTd+5SAvyKVGa++J1h5/yOVzuxXwdiG8lrVqp23zi9a563aRb1Vb2otp7Bcb9QvKs1mpXVea5xV9XLFqpxXzy6a1Ytqq3XRalSbxpacm42rrIBIFdKijp0L/qZc23e57iMtWaQHuNxyKE1DuDv0MQ8mwp8nWXCHpU+fG1bvtvth2Bt+TmMPUewL7OowqkSOMzFAUlUKkTaX/srklnFmtA4exEtMZRI6/VW/HZpt7cJPPoNUVaUQQC3gANYDy5kHlsewJDi0wMEQ8ZlFRbRbrrnlStXBlfppEzx62nBqtdMxbjXB1+OL+lm9VXXdarlar1Yao2BG+dfwKTx9CkeeTyajWqVWHzlUrqZzNqqOhDcaM3c6qrva5tEmFxNurRwdyPoaCK7rCPLYmZGbFaTiJSpWK7UG+gnVS/AR/a2/tAMRykXV8+mc6qq2sOsWI8mK8AWEQnahIhSS8EupQwUjFhPT4mNXbUDN6FSMvXyJfvxDc7w8ailRyN4P7/pIwRXDKwSRRsFMLBVbDGwc0gtBms9FGBBFGJeC2riPGNvIFU44h/SxHB8YSZcR9QQxc+nCLmSS1omBxsIeQJ3bmUGaFDPCFG3m0XIYBPSDsqKN7MIYO0+uLzy7sEYWyBWc36WBZwyyC1xwsoPMS/HCLuAxuC6Uu2jHQkox15SVHSSMTOQ+gi92wROUA6KekgW4JbALDwdNhLCrOCiyhve8yzhwx9QXIfhRMOEbFzFY1PQ6wj2uCthgFR6L0ACtE/o+WMJWUYsibhzxOL7JetukWLR9iUAZmUAE3RhJpgA1TOu/zGKhXjHdIbblHQdUkVBWSIy/qsa4nFFI5SVlDJomcwGKJuIoK3WuKuqxeEZR1Nct7xpVOYA2a8UEsn4B/IHj4JBJpMPoMOjkaAbNm0HLVFqWMwKeSxTTAHEhdcMHc8CpKVtsgH54H4lop4UNIMUHHnZIV2VBRGBNiexxL5TvHBUj3SUiYwdrHMOVR6x+9+fhqNPvdf5lmoE+xicPhgmiffYmkyVv9AHU6hSghMdGR0c50axYZgiKxsgSiivEsvkk5NoyFGolH1LxRSPv50hcwhSBEp2g4g/RUaKUyXOUIkKEjqxkReoTYOX64UV9qLRKgrPEQXTIExQIDWaIyiBBOIU+4EjFt1/lmImoiLZRJpjw+GN0gBjdMF9g6ExMtdL3hE5nEp2mzlxpq73nxx1yIyABqQnLc0Kewi6Q5PyoUugjgCLxIbXtwk3vg4HcvApJnmXHnF/VBOxk+kBHw7bOBN0SJMxZpi7HMNyGavKBOcyMaFCiquo0ifJwoCXQV+NMklimZ3zMHumWQCZST1dEPmeyE4SbUqG2CUQSEYTeXEk8hqFdd5B2POmeKkNvxPNpVPZDRWMXrq/kWLir6zfoHzG/XbiSPqzPrsGjV2X4vpLutV0w+y8QpINBeAE29xo+/OvHWPBjLPX2vjccot5tInqvxMQozTbq3caG7FcyuP/0a6f7ei2G72g1fcGnVIYueaWahO9INZBff0ZLxHacElO3r1RhmI5TEN+BIoAodhmjXiCoW3ql0kjQUbrLJr/hWyX8tcEUA6bZOspgQm8C1142EyGRMMAiDPgahJ66l2p4Tbbiig4AA9CYhem8iNKLcEqtLkM8JdHN0tqlULXajFIHGvPUwFQM+Y4efACcVoQxgPtN3TsUqvaUabZwP1IuBpAIBhIuz3069rG/smgwSGwaxJYUs8N6yY47nrrJ7vJYilrpGW+Us9qHLIhGancKqCiJhky9XzQYnxdnhXAwAGJoQtFEmB3HrJv+p+5eLkb4VM6ADS6f1W2Umbnwy4OePzbP9Yv2+Pc7mJZ34GT93l13P9u+oxnSbWfLX8vWTmJuZ6bEjjpsJpf0Sb/ExZz38snmsrYwWn8oqe9SZGEu6zKTalyK+nWUlTvL9kk0yE+iSX8W/E5Vzh3Iic46hz/n0SCVDHGmgnF+GPPJggIzDAAzACmmgEoVMlwizDiRrBoZRySbVqSGBVClJvtknlBbJhNz2JmdwHUMYbMYH8CCK2j8ZqSUKDg46e5nf8Xgm5tn9USbHPF97Jkc3IFsKt+YOwhmkFNuOlpZqfq8B35ot1OiSW6QOuD0nJyH1Er4ODl0U7m7/zToju7uf+seylTIMaNUD4+qXajBfU4k1u9Ioa0oF/TM4PZtmdyHEbujOsA3ZHLsoGPSeDewfN889jJZ+OoczF5YE5GxpD0pOjCvt4/Nz9SyXf75UnlA7fba9eaYYhnghRkL1q8ZYEr8isKMCln/ZiApdfKOagDT3u6qL2XypqzjKuxhb+lDYmy9Ox1Kso26zcRMpsGKX6Ck81/uOrvxJiW/EFmeX7Ryl7JDd7vYQTl7ozn27XEwk74QMa9HCYMhb9c4lpsnLYCUQEKK7h4srQS4Dr1Hy8Q/G6aNRIvfp+18o3bcOzXwTAqq5uVfilfpKPy/1PtVXa0hVoYv6VuZstqynQyH2b2cQ9/u4Qa+JBjZZvdfnTn+hhPHdtfnRCRhyk35DhOcJKixhhsm9ifp7s4ciEnSHrdF0PoN43O337///TvMQOvl+n83/myp5I1kyHbHtb3E/cnG9gJe5/trqvevnLS+ec7a8NArhqsdLt5WpX9iAjs4RW2Bjb1QsLPYM4CwPaE20eDI1pCZNXaYtw2fdlhR2gj7cWPgEcgVvRv5+8yAhZPClf5J5ToW/k86V0MfCn1WtKyyJHP9rwNBeRyCVmk5QRAH4KqcZb1y6QJRt73lP2WSXxYmIWMD+m/9M0IZ6DdYox/jo96uyGbV675ZtCzrqgyP2zmlEGyM/TXJ/wE
Environment
Browser: Chrome
CesiumJS Version: 1.116.0
Operating System: macOS

Hi @keiya01,
We have a cache size limit to prevent large tilesets from crashing the browser when they use too much memory.
If you want to bypass this default behavior, you can set the cache size higher. However, for the best solution, I would recommend reducing the size of the textures in the tileset, or compressing them such as with KTX2.

Yes, I can also set Infinity to the cacheSize option. However, I personally think that it causes unexpected behavior when the cache size limit is exceeded. Ideally, it would be more useful if it behaved more naturally.
For example, the feature that exceeds the cache size should be removed from the scene, not flickered. And the removed feature should be appear at a higher zoom level.

Thanks for clarifying @keiya01!
When the cache size limit is exceeded, we adjust the scene's maximumScreenSpaceError, which typically "unloads" higher LODs. This typically does not result in flickering. While I see your point that this can be unexpected behavior, at this point I think this appears to rare. In this case I would suggest optimizing the tileset or adjusting the cache size limit.
I'm going to close the issue for now, but we'll keep our eyes open if we see other reports.

我也遇到这个问题，一个大70多G得也是加出来后一直闪烁不断

https://github.com/user-attachments/assets/082b883d-51b0-42a1-b333-ee6b826f0743


[SPARK-30087][CORE] Enhanced implementation of JmxSink on RMI remote calls

What changes were proposed in this pull request?
Enhanced implementation of JmxSink on RMI remote calls.
E.g:
service: jmx:rmi://<IP_ADDRESS>:1986/jndi/rmi://<IP_ADDRESS>:1986/jmxrmi to connect
Why are the changes needed?
JMX supports RMI remote which can be more suitable for production use.
Does this PR introduce any user-facing change?
Added JMX RMI remote port connection method.
How was this patch tested?
JmxSinkSuite.scala

Can one of the admins verify this patch?

Can one of the admins verify this patch?

hi @jerryshao Have time to review this PR?

hi, @dongjoon-hyun Thank you very much. Hive any time to review this PR?

One concern is that this will expose a security hole of Java RMI, I'm not sure if it is OK, but somehow it will lead to CVE issue.

One concern is that this will expose a security hole of Java RMI, I'm not sure if it is OK, but somehow it will lead to CVE issue.

hi @jerryshao Can I add a parameter for the user to decide whether to enable JAVA RMI?...

Can you please investigate how other systems like Kafka, Hadoop handle this problem? Adding parameter could be a way, but my thinking is that if we want to enable RMI, it would be better to provide a security way also.

Can you please investigate how other systems like Kafka, Hadoop handle this problem? Adding parameter could be a way, but my thinking is that if we want to enable RMI, it would be better to provide a security way also.

Well, okay, let me look at the implementation of hadoop first. Flink is similarly implemented using open rmi ports.

hi @jerryshao What do you think about this PR? Add a parameter to control or implement the serverlet or the current RMI?

Can one of the admins verify this patch?


Installer/Launcher incompatibilities

When installing Toolbox using the .msi and then using the GWToolbox.exe launcher, it'll say that Toolbox is not installed and re-download everything if you say yes to install. It will also create a separate entry in the Programs section of windows settings/control panel, meaning you have gwtoolbox with the icon (the .exe) and gwtoolbox without an icon (the msi) installed.
The msi should not create a separate installation key and instead be equivalent to installing via gwtoolbox.exe.

fixed with https://github.com/HasKha/GWToolboxpp/pull/776/commits/12c541aa49c6a9fe9ab2aac87d5ad84290c9f5a3

no longer relevant as we got rid of the d3dx dependency


PARSE ERROR

Hi Feng,
no matter what I do, its giving me the following error:
XHR finished loading: POST "XXX/crop.php".
index.php parsererror...SyntaxError: Unexpected token <...[object Object]
I can't see any further details. I'm using your original code of "crop-avatar". CHMOD is set to 777 for testing usage.
What could the problem be or how can I enable more detailed error reporting?
Looking for help...

https://github.com/fengyuanchen/cropper/issues/252
(parsererror, but another situation - no solution yet)

@nywuctuk Mine looks same but after XHR comes the parseError
XHR finished loading: POST "###/user.file.crop.php".
index.php:2836
parsererror...SyntaxError: Unexpected token <...[object Object]

@larsklein The "crop.php" should return valid JSON only.

@fengyuanchen I uploaded your whole git, set chmod to 777 for crop.php and the image directories, it doesn't work. Do I need any other CHMOD to 777? Anything else what I need to notice? I haven't changed anyhting!

@larsklein Check your PHP version / HTTP server.

Maybe you don't have permission to create folder in you PHP server, you can try the v0.9.2.


Add attribution metadata slug to emissions metadata

I've included the changes in the frontend to use the source id instead of the hardcoded one and also added the metadata modal in the ghg-emissions page.


[7.x] Add dynamic slot name support

This pr adds support for dynamic slot names using the : prefix:
<x-slot :name="$foo">
    {{-- ... --}}
</x-slot>

@cbl good one!

Should we add it to the main docs as Dynamic Slots?

@mnabialek I think the way it works now is the way you would expect it to work since dynamic attributes on Blade X components work the same way. However it might be useful to read that it is possible when flying over the docs.


Can't change the value if a default value is entered into the Input component

react-native, react and native-base version
react-native : 0.43.1
react : 16.0.0-alpha.3
native-base : 2.1.1
... forked from the NativeBase Starter Kit
Expected behaviour
Should be able to delete/edit the value in the text Input component if a default value is given.
Actual behaviour
Can't delete/edit the value in the Input component.
After every keystroke, the value in the Input text box always jumps back to the default value.
Steps to reproduce (code snippet or screenshot)
<Form>
  <Item>
    <Label>Test label</Label>
    <Input
      placeholder="test placeholder"
      value="test"
    />
  </Item>
</Form>

Screenshot of emulator/device
n/a
Is the bug present in both ios and android or in any one of them?
Tested on Android emulator.
Any other additional info which would help us debug the issue quicker.

Not related to NativeBase
Check controlled components and uncontrolled components

Im having the same problem. Input should still be editable even when there is a default value

I use TextInput to wrap it, and it works for me.

@soleilgl can you share your code for this? I have the same issue with not being able to change the text.

@pratomchaip what you want is defaultValue not value.
As @SupriyaKalghatgi suggested checking up on controlled / uncontrolled components might be helpful.

Yeah, I eventually figured that out. ;)

nativebase: 2.4.5
react: ^16.3.1
react-native: ^0.55.3
<Input defaultValue="{defaultValue}"/>

shows an emty textbox, whereas it should display the numeric value.


Calibration DB Docker Compose Update

A small change made to the Calibration DB's docker-compose.yml file to fix a couple of issues that were causing the DB data to not persist after the host machine was rebooted.
This has already been tested on the dev and prod machines for a while and seems to have solved the issue.

Why is the actual pgdata folder in the var directory instead of a more visible mount (say.. dev_fim_share/foss_fim/calibration/data/pgdata)  Just curious?    But.. the PR is just fine and I was able to get it running on Dev2

There is a long-standing issue with Docker where host mounts (a docker volume attached to an actual folder on the host filesystem) is not immediately available upon reboot of the host system. So the issue was happening on the weekly IT patching and rebooting that after the host was up and docker-compose brought back up the containers that were running, it was not properly mounting the PGDATA mount.
To remedy this, I switched the PGDATA from a host mount to a regular named Docker volume, which does not suffer from this issue.
You can ready more about this issue here https://github.com/docker/for-win/issues/584#issuecomment-286792858


Adding creation and last loaded date properties to datasets

Adds creation_date and last_loaded_date properties to FiftyOne datasets, which are automatically populated/updated.
Poll question
Should we use creation_date and last_loaded_date or creation_time and last_loaded_time? Or other suggestions?
Example dataset
import fiftyone as fo
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset("quickstart")

print(dataset.creation_date)  # 2021-08-26 01:57:12.378000
print(dataset.last_loaded_date)  # 2021-08-26 01:57:12.378000

Example use case
One can use this information, for example, to locate recently used/created datasets. The fiftyone datasets info command shown below sorts by last loaded date (if known) as a helpful way to locate datasets that you've recently worked with.
fiftyone datasets info

# These are also possible
fiftyone datasets info --sort-by creation_date
fiftyone datasets info --sort-by name --reverse

name                               creation_date        last_loaded_date     version    persistent    media_type      num_samples
---------------------------------  -------------------  -------------------  ---------  ------------  ------------  -------------
coco-2017-validation-500           2021-08-26 01:53:31  2021-08-26 01:53:31  0.13.1     ✓             image                   500
looker-video                       ???                  2021-08-26 01:52:28  0.13.1     ✓             video                    10
looker-polylines                   ???                  2021-08-26 01:52:24  0.13.1     ✓             image                   500
open-images-v6-validation-100      2021-08-26 01:52:01  2021-08-26 01:52:01  0.13.1     ✓             image                   100
looker-image                       ???                  2021-08-25 22:42:25  0.13.1     ✓             image                   200
bdd100k-validation                 ???                  2021-08-25 22:39:34  0.13.1     ✓             image                 10000
bdd100k-validation-embeddings      ???                  ???                  0.13.1     ✓             image                 10000
bdd100k-validation-embeddings2     ???                  ???                  0.13.1     ✓             image                 10000
bdd100k-validation-location        ???                  ???                  0.13.1     ✓             image                  9994
bdd100k-validation-nyc             ???                  ???                  0.13.1     ✓             image                  7953
bdd100k-validation-similarity      ???                  ???                  0.13.1     ✓             image                 10000
cifar10-test-similarity            ???                  ???                  0.13.1     ✓             image                 10000
coco-2017-failure-modes            ???                  ???                  0.13.1     ✓             image                 45670
coco-2017-failure-modes2           ???                  ???                  0.13.1     ✓             image                 45670
coco-2017-recommendations          ???                  ???                  0.13.1     ✓             image                 45670
coco-2017-segmentation-validation  ???                  ???                  0.13.1     ✓             image                  5000
coco-2017-validation-embeddings    ???                  ???                  0.13.1     ✓             image                  5000

LGTM. My naming recommendation is created_at and last_loaded_at, but the current choices work too.

I like created_at and last_loaded_at


CI workflow fixes for forked PRs

Proposed Changes
SSIA

Codecov Report

Merging #339 (44ba8d9) into main (1c6bc30) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #339   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          153       153
  Branches         9         9
=========================================
  Hits           153       153

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add host identifier to resource info

Summary
Adding hostname as an identifier to find the resource.
Test
build passed

Codecov Report
Attention: 25 lines in your changes are missing coverage. Please review.

Comparison is base (f61c699) 72.46% compared to head (a2405dc) 18.34%.
Report is 1 commits behind head on master.

Files
Patch %
Lines

...m/github/ambry/clustermap/HelixClusterManager.java
0.00%
22 Missing :warning:

.../github/ambry/frontend/GetResourceInfoHandler.java
0.00%
3 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2679       +/-   ##
=============================================
- Coverage     72.46%   18.34%   -54.12%
+ Complexity    11576     2789     -8787
=============================================
  Files           811      816        +5
  Lines         65893    69771     +3878
  Branches       8042     8419      +377
=============================================
- Hits          47748    12802    -34946
- Misses        15520    55780    +40260
+ Partials       2625     1189     -1436

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Make langsmith-pyo3 v0.1.0rc2 release.

The JS integration tests are flaky, the failure is not relevant here since this PR has nothing to do with them. Proceeding with the merge.


Update app.properties to reflect project details

Create a chore branch and update the app.properties file with the neccessary details

Ok..


core[minor]: Add llm cache in stream

Description:
The current implementation does not exploit the cache when using stream.
This PR add the usage of the llm cache with the stream.
Twitter handle:
@pprados

@pprados i'm going to close this PR for now due to lack of activity, if you want to make a fix for supporting cache in streaming for llms or chat models feel free to make a new PR!


investigate alternative to relay pings/why we need them

Problem
https://github.com/waku-org/js-waku/issues/1189#issuecomment-1494025562 made us aware that relay pings (sending messages over the relay protocol manually) are required to ensure connection stays alive.
This isn't ideal as we end up sending a lot of messages (maybe spam).
Proposed Solutions
This issue should track:

[ ] why we need relay pings
[ ] alternative to relay pings if possible
[ ] if we can reopen the connection after it closes (in 10 mins)
[ ] confirm if after 10 mins, does message sending and receiving both fail, or just receiving?

Notes
Refer to some investigation been done in https://github.com/waku-org/js-waku/issues/1189

The output of this issue should be:

relay ping are removed
Yet, a browser is able to use Relay for an extensive period of time (e.g. 1 hour)

At this point in time it does not really make sense to use Relay anyways because we can only connect to nodes via wss.
This issue can be addressed once Relay over WebRTC is done and we start to worry about connection management for it.
Let's keep the ping for now as some projects do use Relay. Do note that in terms of documentation, we will only push light client protocols.


Fix styling of dropdown's in dark mode

Dropdown's are hard to view in dark mode

As far as I can understand, we need to change the color code in settings.scss file so that it will be more visible.
If that so, I would like to work on this issue.
if there is anything else needed in this issue, which is needed/asked, please guide me so that I could have a better understanding of this issue.

Yeah, you're on the right track. We're using React Select for the drop downs. You can see an example of where it's being used in namespaceFilter.tsx. The css for the Select control should all be found in select.scss. The colors we want should all come from the variables being declared in settings.scss (just like you suggested). Really the tricky part of this one is going to be figuring out which css classes that control exposes and setting everything correctly. I think it's going to just be a bit of trial and error until it looks good. Also, we'll want to make sure that whatever changes we make for dark mode don't break "light" mode.
Also, just to make sure you're aware... you can toggle between light and dark mode from the "Profile" menu option. Just scroll down and toggle the "Use Dark Mode" switch to go between the two.
Hope that helps. Let me know if you have any other questions. Thx!

@herbrandson just one thing, is there some resources where I can get help to set up it offline to check and do changes to not mess up anything else while doing it apart from reading from the Development section's Part of k8dash in Main Readme.md? if so, could you give their reference here?
I would love to work on this issue, but could I get some time for it ( min2-3 days because having some papers for the next 2 days)

Not really. But, let me know if you run into issues with getting a local environment working after following the readme.md and I'll be happy to lend a hand getting you unstuck :)

@herbrandson I tried setting up docker, starting minikube, cloning the repo, and then starting the project as is there in the docs of how to start with development for the client.
Good news. it started and the localhost got setup.
problem is I can't see anything, as it will only show loading

and not anything else, what could I be missing?

A shot in the dark. When you startup the server, what do you see for Version and Available APIs?
For example, I get
[nodemon] 1.19.4
[nodemon] to restart at any time, enter `rs`
[nodemon] watching dir(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node .`
OIDC_URL:  None
API URL:  https://<IP_ADDRESS>:6443
[HPM] Proxy created: /  ->  https://<IP_ADDRESS>:6443
[HPM] Subscribed to http-proxy events:  [ 'error', 'proxyRes', 'close' ]
Server started. Listening on port 4654
Version Info:  {
    "major": "1",
    "minor": "17",
    "gitVersion": "v1.17.2",
    "gitCommit": "59603c6e503c87169aea6106f57b9f242f64df89",
    "gitTreeState": "clean",
    "buildDate": "2020-01-18T23:22:30Z",
    "goVersion": "go1.13.5",
    "compiler": "gc",
    "platform": "linux/amd64"
}
Available APIs:  [
    "acme.cert-manager.io/v1alpha3",
    "admissionregistration.k8s.io/v1",
    "apiextensions.k8s.io/v1",
    "apiregistration.k8s.io/v1",
    "apps/v1",
    "authentication.k8s.io/v1",
    "authorization.k8s.io/v1",
    "autoscaling/v1",
    "batch/v1",
    "cert-manager.io/v1alpha3",
    "certificates.k8s.io/v1beta1",
    "coordination.k8s.io/v1",
    "discovery.k8s.io/v1beta1",
    "events.k8s.io/v1beta1",
    "extensions/v1beta1",
    "metrics.k8s.io/v1beta1",
    "networking.k8s.io/v1",
    "node.k8s.io/v1beta1",
    "policy/v1beta1",
    "rbac.authorization.k8s.io/v1",
    "scheduling.k8s.io/v1",
    "storage.k8s.io/v1"
]

One thing to confirm, do I need to set up nodeport also?
And after getting the token from Server-account-token where do i need to use it?

I don't think you need the nodeport.
I just tried to go through the steps, using a new minikube cluster and I was able to get k8dash to load via the following steps.
Start a new minikube cluster
$ minikube start -p k8dash
😄  [k8dash] minikube v1.8.2 on Ubuntu 18.04
✨  Automatically selected the virtualbox driver. Other choices: docker, none
🔥  Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🐳  Preparing Kubernetes v1.17.3 on Docker 19.03.6 ...
🚀  Launching Kubernetes ...
🌟  Enabling addons: default-storageclass, storage-provisioner
⌛  Waiting for cluster to come online ...
🏄  Done! kubectl is now configured to use "k8dash"

This will populate ./kube/config.  So, ensure that the context is currently this minikube cluster that was setup.
kubectl config use-context k8dash
Double check that you get use kubectl to see the content there.  I get
$ kubectl get pods -A
NAMESPACE     NAME                          READY   STATUS    RESTARTS   AGE
kube-system   coredns-6955765f44-gv266      1/1     Running   0          3m50s
kube-system   coredns-6955765f44-xslc7      1/1     Running   0          3m49s
kube-system   etcd-m01                      1/1     Running   0          3m52s
kube-system   kube-apiserver-m01            1/1     Running   0          3m52s
kube-system   kube-controller-manager-m01   1/1     Running   0          3m52s
kube-system   kube-proxy-88kn7              1/1     Running   0          3m49s
kube-system   kube-scheduler-m01            1/1     Running   0          3m52s
kube-system   storage-provisioner           1/1     Running   1          3m55s

Next, I build and startup k8dash stuff in the following way

In a terminal window, start from the k8dash checkout
1.1 cd server
1.2 npm i
1.3 npm start
1.4 Leave this terminal open, so the server can remain running
In another terminal window, start from the k8dash checkout
2.1 cd client
2.2 npm i
2.3 npm start
2.4 Again, leave this terminal open, so the client side will run

After the client starts up, it should open up a browser tab.  There will be a scary error message, but there is also an X option in the top right of the error panel.  Click the X and that should take you to the Token input page, which is where you input the token from  Server-account-token that is obtained via kubectl describe secret k8dash-sa-token-xxxxx.

Another possible break point might be the kubectl version, which is really meant to only be 1 minor version way from the cluster version at any point. For example, if kubectl version is 1.18, it will work with cluster's on 1.16-1.18.
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.9", GitCommit:"94f372e501c973a7fa9eb40ec9ebd2fe7ca69848", GitTreeState:"clean", BuildDate:"2020-09-16T13:56:40Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:07:13Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}

If you already tried to replicate my path, please note the EDIT

<EMAIL_ADDRESS>start C:\Users\Jasvinder Singh\Desktop\SP\github cloned repos\k8dash\server
cross-env DEBUG_VERBOSE=true nodemon .

[nodemon] 1.19.4
[nodemon] to restart at any time, enter rs
[nodemon] watching dir(s): .
[nodemon] watching extensions: js,mjs,json
[nodemon] starting node .
OIDC_URL:  None
API URL:  https://<IP_ADDRESS>:32772
[HPM] Proxy created: /  ->  https://<IP_ADDRESS>:32772
[HPM] Subscribed to http-proxy events:  [ 'error', 'proxyRes', 'close' ]
Server started. Listening on port 4654
(node:10400) ExperimentalWarning: The dns.promises API is experimental
Error getting cluster info { Error: connect ECONNREFUSED <IP_ADDRESS>:32772
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1106:14)
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 32772 }
Looks like I am having an error

Ideally, if kubectl works then k8dash will work. I am wondering whether there is a problem loading the kubeconfig or something else with routing in Docker for Windows.
To validate that the kubeconfig isn't the issue, are you able to kubectl get pods -A and see what I saw?
Following up on that, I wonder where that kubeconfig is.  k8dash/server/index.js is getting the kubeconfig from the call new k8s.KubeConfig();.  The logic looks for the kubeconfig in the home directory of your OS, in a subdirectory .kube/config.  Open that configuration and make sure that it is the configuration for the minikube cluster you created.
Even if that is the right config, maybe there is another environment variable that is hijacking the path that k8s.KubeConfig(); uses to search for the config.  The code for this k8s module is here, and in particular the logic that finds the home directory likely should be using this line for Windows.  If it doesn't reach that line it might be that one of the other environment variable checks, above that particular line of code, is providing an alternative path to the HOME directory.
You might be able to get some insight quickly by adding a log statement under this line to look like the following, so we can make sure that the minikube context is being seen
const kc = new k8s.KubeConfig();
console.log('Loaded context: ', kc.currentContext);

Hey @simarpreetsingh-019 , are you still interested in working on this issue? Are you still blocked on getting things working on Windows? Anything we can do to help?

@herbrandson  sorry I was not able to connect with you during the whole time, got infected with our novel virus during my exams, just got back with the development.
some points to discuss:
is there any update on the client-side? 2 weeks back, it started to deploy locally with windows popping up showing the dashboard start.
But now, I can't start it because it got stuck with errors when I run npm start on the client side.

@simarpreetsingh-019 sorry, to hear you got COVID. My son also caught it at while at university. What a mess!
From reading through the thread above, it looks like @ericblackburn was helping you get a working development environment going. Were you able to work through his last couple of suggestions? For example, does kubectl get pods -A work for you?
Can you explain more about what errors you're seeing when running npm start on the client side?

@herbrandson i followed @ericblackburn steps , before getting affected , when i was trying to so , i got to see client side working with web page getting displayed, but can't enter the token.
but now, when i try to run npm start in client , it shows :

<EMAIL_ADDRESS>start C:\Users\Jasvinder Singh\Desktop\SP\github cloned repos\k8dash\client
cross-env react-scripts start
C:\Users\Jasvinder Singh\Desktop\SP\github cloned repos\k8dash\client\node_modules\react-scripts\scripts\utils\verifyTypeScriptSetup.js:231         appTsConfig.compilerOptions[option] = suggested;                                             ^
TypeError: Cannot add property noFallthroughCasesInSwitch, object is not extensible
at verifyTypeScriptSetup (C:\Users\Jasvinder Singh\Desktop\SP\github cloned repos\k8dash\client\node_modules\react-scripts\scripts\utils\verifyTypeScriptSetup.js:231:45)
at Object. (C:\Users\Jasvinder Singh\Desktop\SP\github cloned repos\k8dash\client\node_modules\react-scripts\scripts\start.js:31:1)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: cross-env react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
 npm ERR!      C:\Users\Jasvinder Singh\AppData\Roaming\npm-cache\_logs\2020-11-17T16_54_38_803Z-debug.log

and after running this kubectl get pods -A , i got
NAMESPACE     NAME                               READY   STATUS         RESTARTS   AGE
kube-system   coredns-f9fd979d6-ssx7h            1/1     Running        4          41d
kube-system   etcd-minikube                      1/1     Running        2          5d20h
kube-system   k8dash-87fd8b696-bdldd             0/1     NodeAffinity   0          40d
kube-system   k8dash-87fd8b696-x5smp             1/1     Running        1          4d20h
kube-system   k8dash-87fd8b696-xgw8l             0/1     NodeAffinity   0          5d20h
kube-system   kube-apiserver-minikube            1/1     Running        2          5d20h
kube-system   kube-controller-manager-minikube   1/1     Running        8          41d
kube-system   kube-proxy-jlcjx                   1/1     Running        4          41d
kube-system   kube-scheduler-minikube            1/1     Running        4          41d
kube-system   storage-provisioner                1/1     Running        18         41d
I have tried the steps that was suggested when i got error from running client side. but still no response.
i will try to delete and re install npm and node's latest version also and will try after that.

Is this issue still going, I'd like to work on it? guidance needed :)


Questions about the performance of evo

Given the example "ACGT" as prompt, it seems that the output data from 8k-base model are strange:

Is it possible to discover such a DNA sequence in the real world? I assume there are no sequence with so many Ts like this. Thanks.

Try playing around with the settings to control the quality, temperature, top_k etc


Problems parsing company names with punctuations

Hello,
Very nice module but it doesn't always handle well some real human entered company names we deal a lot with. Below some obvious examples where the name is not parsed:
LIBGAS,LTD -> LIBGAS,LTD
AIRDAS USA,LLC -> AIRDAS USA,LLC
GF LOGISTICS.INC -> GF LOGISTICS.INC
HAKUTATZ.TECH.CO.,LTD. -> HAKUTATZ.TECH.CO.,LTD
Thanks

Perhaps the issue here is that there is no space between the name and the suffix? What countries are these companies based in?

Correct, as long as there is a missing white space it is parsed ok.
These companies are based in USA and China but I believe the key is that probably the data was entered in China where they're not used to white spaces.
I believe the library could be immune to that.

I have seen the entity abbreviation being separated by a comma (more often comma + whitespace, actually). Although I'd agree that whitespace (no comma) is a more common separator.
I guess we could replace commas with whitespace as a preprocessing step? I am a little surprised we did not already have this :) In any case, I don't have time to work on that.
As @psolin pointed out, replacing commas with whitespace would probably be an easy data cleanup workaround.


What's public?

The tslint npm package contains autogenerated .d.ts files from source file.
Presumably only index.d.ts is public though?
Is there a way that only that can be published?

We generally consider the public API to include symbols exported from index.d.ts. Users may import symbols from submodules, but those are not guaranteed to be stable or follow semver.
// ok
import { Linter } from "tslint";

// use at your own risk
import * as LanguageUtils from "tslint/lib/language/utils";

Excluding "non-public" types from the distribution seems like extra effort & complexity that doesn't provide many benefits. We might consider marking certain things we really don't want to make available as /** @internal */ to elide them from typings, but there would have to be a convincing reason to do it.

SGTM. Is this documented anywhere?

💀 It's time! 💀
TSLint is being deprecated and no longer accepting pull requests for major new changes or features. See #4534. 😱
If you'd like to see this change implemented, you have two choices:

Recommended: Check if this is available in ESLint + typescript-eslint ✅
Not Recommended: Fork TSLint locally 🤷♂

👋 It was a pleasure open sourcing with you!
If you believe this message was posted here in error, please comment so we can re-open the issue!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


card sorting bug

on today's challenge, the solution is  not sort by the order suggested, please view the image below.

Hi, the cards are first sorted in order of quads, triples, pairs and singles, and then in the order of rankings from highest to lowest. In this case, the trips should go before the pair in a full house. More examples are given in the card order menu. I hope it's clear for you!


Upgrade eslint; Add --es6 flag; Add --line-length flag

This pull request upgrades the version of eslint used and adds an --es6 flag (off by default) and a --line-length flag that you can use to set the line length.
Once everything is good, I'll merge this in as major version change.
The only new rule I was uncertain about is the no-continue, which I think would be good to enable.
https://github.com/eslint/eslint/blob/master/docs/rules/no-continue.md
I also was curious if anyone had any opinions on turning on the object-shorthand rule for the --es6 flag?
https://github.com/eslint/eslint/blob/master/docs/rules/object-shorthand.md
@raynos @lxe @mlmorg @freeqaz
(This is the same pull request as previously but with separate commits for all the changes)

Did you forget to rebase commits out of this pr ? It still does everything the last one does.

@raynos What do you mean? I went back to master and re-added all the work as separate commits each implementing a different feature. Isn't that what you asked?


updated hopper to use 3 sensors

moved shooting stop logic from hopper to superstructure also, and added speed constants for harvester

Just waiting on #149  before merging this. (hopefully done today)

Merged by #153


Add Feed - minor suggestions to UI text for the steps

Here are a couple of suggestions for the steps for adding a feed, mostly to make them consistent to be all nouns or all starting with verbs (other than Submit). I think the only one that has to change is upload, as this could suggest that you are browsing to a file.
Current --> Suggestion as a noun (starting with a verb)

Upload feed --> Feed URL (Specify feed)
Add operator(s) --> Transit operators (Review transit operators)
License info --> License (Add license)
Submit

Another idea. Is there a step 5 for "Completed" or "Done" or "Finished" or "Submitted"? Rather than change the header on the page to SUCCESS!, perhaps it stays as ADD A TRANSIT FEED with an additional step that shows the confirmation that the feed is in review?

Update: following the front-end meeting on 1/21/16, we were going to think more on these headings in the wizard. We did decide that there should not be a step 5 -- the success page should take you to a new page that would look different from the others (like confirming an online order shows a new page).
Some liked verbs for the headings.

Specify feed
Review transit operators
Add license
Submit

PR #143 addresses most of the UI suggestions for the add a feed flow, but not these overall heading names.

Suggestions -

Specify feed (specify feels a little harsh I feel)
Review transit operators - Review Operators
Add license - Good
Submit - Good

@souperneon @meghanhade for specify in the paragraph, we went back to "find". Is that preferred for the heading?

Feed
Operators
License
Submit

https://github.com/transitland/feed-registry/issues/164


Add preview disclaimer to Pulumi Cloud

Partially addresses https://github.com/pulumi/pulumi-cloud/issues/737.

Is this along the lines of the change you were looking for, @CyrusNajmabadi ? I haven't removed the original paragraph yet, found at https://www.pulumi.com/serverless/. Once we finalize, I'll apply the final note to the other www and docs pages.

FWIW, and luke to confirm, for 1.0 we probably want to take those pulumi/cloud tutorials and at least have the awsx equivalent that we can point to.   This shouldn't be too hard to do and i can help you out if you need with getting the right code for the containers examples.

Are these quickstarts linked from the TOC?  I don't see them as an end-user.
I think to first approximation these are deprecated content.  Assuming we see very low traffic to these from inbound links - we could consider just fully removing them.

IIRC, /docs/quickstart/cloudfx/ is one of the quickstart directories we intentionally left out of the TOC (left navigation). You could access the landing page at  https://www.pulumi.com/docs/quickstart/cloudfx/.
@lukehoban can you please confirm if we're going to keep these in for now or remove them entirely? I can open an issue around updating the tutorials to their non-cloud equivalent and work with @CyrusNajmabadi on that.

I think it's fine to keep them as-is, especially now that it's marked preview.
If we deprecated/removed the package, I could see an argument for removing them, but we've explicitly decided to keep the package and mark it as preview (at least based on my understanding).
More than anything, I vote for plowing ahead and making forward progress.

Keeping the content sounds fine, but I don't think it makes sense under /docs/quickstart anymore because similar content was already moved out of /docs/quickstart. For example, the overviews of the clouds and setup pages were moved to be under "Supported Clouds" and the tutorials for each cloud were moved to be under "Tutorials".
So:

Move the Cloud FX page to either the  "Supported Clouds" (although, it doesn't make as much sense to me there because it isn't a cloud, it's a library that works with multiple clouds), or perhaps better, move the content into the API docs for the package.
Move the tutorials to be under Tutorials.

I believe we can close this out based on the conversation above.  We may still come back and move some of these pages - but they aren't in TOC so that isn't critical - and it would be a different change than what's currently in this PR anyway.


Query:How to enable gzip compression

This may be a bit lame question. I am using spring MVC REST, Is there a way to enable gzip compression using Heroku build pack for that or is there any way by which I can change the server.xml?

@vsharma02 not a lame question at all. Are you using webapp-runner? If so, you can add the --enable-compression option to your java command. Otherwise, it will depend on the framework or server you're using.

@jkutner , Thanks a lot! It worked


what does instance do in your sample init code in README.md?

Please explain, 'cause jshint says it's never used

imgLoad.on( 'fail', function( instance ) {
  console.log('FAIL - all images loaded, at least one is broken');
});

or here:
imgLoad.on( 'progress', function( instance, image ) {
  var result = image.isLoaded ? 'loaded' : 'broken';
  console.log( 'image is ' + result + ' for ' + image.img.src );
});

instance is the instance of imagesLoaded. It's useful when use its properties

@desandro Oh yeah, it's just that I didn't make use of instance, the jshint says it's never used, thanks


Fix comment shape compatibility issue with the recent Excel versions

PR Details
Fix comment shape compatibility issue with the recent Excel versions
Description
Change comment shape type v:path o:connecttype. To be honest I'm not sure about the root cause, but the fix seems to work.
Related Issue
#672
Motivation and Context
Solve the issue above: When open files created by Excelize with comments, then save again, the comment shapes are changed by Excel.
How Has This Been Tested
Manually on Mac OSX Catalina & Excel version 16.39
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #673 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #673   +/-   ##
=======================================
  Coverage   96.67%   96.67%
=======================================
  Files          30       30
  Lines        8934     8934
=======================================
  Hits         8637     8637
  Misses        183      183
  Partials      114      114

Impacted Files
Coverage Δ

comment.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

LGTM, @xuancanh thanks very much for your contribution.


ark-pixel-font: fix build for ZHF

ark-pixel-font uses a custom build system,
and the latest release is incompatible with pixel-font-builder 0.0.28 introduced in commit 985dd2a1f0f51a5b1e9bdf04c8ed4462dfceedeb.
To fix the build I've overridden the used version of pixel-font-builder to 0.0.26
The main branch of the repo does use the newer version of pixel-font-builder but it completely changed the build system as well.
I am not knowlegable enough yet to make a new derivation for the newer commits since it still doesn't use a standard python build system.
ZHF #352882

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

ZHF: https://github.com/NixOS/nixpkgs/issues/352882

cc @TakWolf

LGTM. better if we update it to the newest.

Agreed, but I don't have the time to completely rewrite the derivation right now, so may try after the 24.11 release


Fixed GCC Compiler warnings

Thanks, looks good to me. You could have shared the output of warnings prior this changeset and after.
I'll manually merge this to remove that merge branch.

Thanks Martin,
compiler.h:
This files comes from our standard ASF library code to avoid warning we commented it out we thought  it may be useful when we try to update latest version of ASF code.
i2c_api.c:
'return 0'  can be deleted, I will remove it in my next change requests.


feat: charge deposit fees by default to counter dust attacks

Fixes #4611

Should we take a similar fee for outgoing payments while we are at it?

No, outgoing payments already pay a (typically much higher) on-chain fee.

Could not the same argument be made against input fees? I am wondering if there might be a not yet known DOS vector for outgoing payments as well that is prevented by fees in a similar manner.

Edit: I suppose a hacky workaround is audit.net_assets() assuming the only way net assets increase is fees.

This is the way for now. With #4283 we could calculate it even more effortlessly and make it a public API (audits are private for now due to DoS concerns).


Edit a Subdimension displays the wrong entry

Go to the Subdimensions page
Select a specific entry to edit.
The entry that opens isn't the entry you selected.

Done


OnScrollEvent for Listview don't work for flet 0.23.2

Duplicate Check

[X] I have searched the opened issues and there are no duplicates

Describe the bug
hi ,  OnScrollEvent for Listview don't work in flet 0.23.2 , it give an error
i use e: OnScrollEvent to print  (e.pixels )   to find  scrolling position ( delta )
it working fine in flet 0.22
on flet 0.23.1 it work fwhe i run  main.py (  for test code) but when not when i build APK (when code is compiled)

Code sample
Logs

import flet as ft

def main(page: ft.Page):
    page.title = "Scrolling ListView"

    def goo (e:ft.OnScrollEvent):

        print(f"{e.pixels}")
        print(f"{e.data}")
        global position
        position = e.pixels
        tx1.value= str(position)
        tx2.value= str(e.scroll_delta)
        tx1.update()
        tx2.update()
        return position

    lv = ft.ListView(expand=1, spacing=10, padding=20, auto_scroll=False ,
            on_scroll = goo,    )

    count = 1

    for i in range(0, 60):
        lv.controls.append(ft.Text(f"Line {count}" ))
        count += 1
    tx1 = ft.Text( size = 20 , color = "cyan")
    tx2 = ft.Text( size = 20 , color = "yellow")
    page.add(tx1 )
    page.add(tx2)
    page.add(lv)

ft.app(target=main)

To reproduce
Task exception was never retrieved
future: <Task finished name='Task-61' coro=<__run_socket_server..on_event() done, defined at /home/vox/.local/lib/python3.10/site-packages/flet_runtime/app.py:217> exception=KeyError('sd')>
Traceback (most recent call last):
File "/home/vox/.local/lib/python3.10/site-packages/flet_runtime/app.py", line 219, in on_event
await conn.sessions[e.sessionID].on_event_async(
File "/home/vox/.local/lib/python3.10/site-packages/flet_core/page.py", line 905, in on_event_async
await handler(ce)
File "/home/vox/.local/lib/python3.10/site-packages/flet_core/event_handler.py", line 18, in fn
ce = self.__result_converter(e)
File "/home/vox/.local/lib/python3.10/site-packages/flet_core/scrollable_control.py", line 22, in
self.__on_scroll = EventHandler(lambda e: OnScrollEvent(e))
File "/home/vox/.local/lib/python3.10/site-packages/flet_core/scrollable_control.py", line 134, in init
self.scroll_delta: Optional[float] = d["sd"]
KeyError: 'sd'
Expected behavior
No response
Screenshots / Videos

Screenshots / Video demonstration
[Upload media here]

Operating System
macOS
Operating system details
ubuntu 24  /  Flutter 3.22.2
Flet version
Name: flet Version: 0.23.2 Summary: Flet for Python - easily build interactive multi-platform apps in Python Home-page: https://flet.dev Author: Appveyor Systems Inc. Author-email<EMAIL_ADDRESS>License: Apache-2.0 Location: /home/vox/.local/lib/python3.10/site-packages Requires: cookiecutter, fastapi, flet-runtime, packaging, qrcode, uvicorn, watchdog Required-by:
Regression
I'm not sure / I don't know
Suggestions
No response
Logs
Logs
[Paste your logs here]

Task exception was never retrieved
future: <Task finished name='Task-61' coro=<__run_socket_server..on_event() done, defined at /home/vox/.local/lib/python3.10/site-packages/flet_runtime/app.py:217> exception=KeyError('sd')>
Traceback (most recent call last):
File "/home/vox/.local/lib/python3.10/site-packages/flet_runtime/app.py", line 219, in on_event
await conn.sessions[e.sessionID].on_event_async(
File "/home/vox/.local/lib/python3.10/site-packages/flet_core/page.py", line 905, in on_event_async
await handler(ce)
File "/home/vox/.local/lib/python3.10/site-packages/flet_core/event_handler.py", line 18, in fn
ce = self.__result_converter(e)
File "/home/vox/.local/lib/python3.10/site-packages/flet_core/scrollable_control.py", line 22, in
self.__on_scroll = EventHandler(lambda e: OnScrollEvent(e))
File "/home/vox/.local/lib/python3.10/site-packages/flet_core/scrollable_control.py", line 134, in init
self.scroll_delta: Optional[float] = d["sd"]
KeyError: 'sd'

Additional details
No response

Sorry for the inconvenience.
Issue has been raised in https://github.com/flet-dev/flet/issues/3566 and a fix has been implemented in #3551

Issue has been fixed.
Give it a try by installing the latest Flet prerelease: pip install flet --pre (https://pypi.org/project/flet/#history)
Report if the issue persists.

hello ,
sorry , it s not working     (i tried  with 0.24.0.dev3170, 0.24.0.dev3171 and flet 0.24.0.dev3108)
the  terminal  shown nothing   (o)
perhaps  here / see  in  :   self.scroll_delta: Optional[float] = d.get("sd")          :    [get fonction is not define ]

What errors do you get?

nothing displayed on terminal , and  it  s not working  :
i call this fonction when scroll on Listview :
def on_listview_scroll(e:ft.OnScrollEvent):
  position = f"{e.pixels}"
  print(f"{e.pixels}")

please see  in :    self.scroll_delta: Optional[float] = d.get("sd")    => =>   (   "get " fonction is not define  in scrollable_controle.py)
perhaps you forget to import somthing or defiine correctly the call of the "get" fonction

"get " fonction is not define in scrollable_controle.py

Thats by the type checker, but don't mind it, it not an issue.
Can you share the code you run and the result you have? Does the scrollable control scroll as expected?

I also suggest you give another try to the latest prerelease. Maybe what I recently pushed will fix your issue.

hi  ,
it work  :)  thank you for your work ...
simple test for delta scroll  :
def on_listview_scroll(e:ft.OnScrollEvent):
position = f"{e.pixels}"
print(f"{e.pixels}")

ps : i will try to build an APK  for test and give you a feedback

hi ,
bad news , it s not working when you build apk for android   :(
it s ok for linux (desktop)  i tested it , but not working  for androis , and i don't know what s wrong ....

Saying it like this doesn't help anyone. 😅
Provide appropriate details on how to repro.

hi , this is le code :
import flet as ft
def main(page: ft.Page):
page.title = "Auto-scrolling ListView"
tx1 = ft.Text(value= " start position e.pixels = 0 " , color = "red" , size = 23 )
page.add(tx1)
def on_listview_scroll(e:ft.OnScrollEvent):

    position = f"{e.pixels}"
    print(position)
    tx1.value = f"Listview delta position {position}"
    tx1.update()

lv = ft.ListView( spacing=10, padding=20, expand = True ,  on_scroll= on_listview_scroll)

count = 1

for i in range(0, 60):
    lv.controls.append(ft.Text(f"Line {count}"))
    count += 1

page.add(lv)

ft.app(target=main)

Hi ,  it's note done , when build apk , it not working on Android

Which version of Flet do you have in your requirements.txt file?
Make sure it is one of the latest prerelease: https://pypi.org/project/flet/#history

it s the last dev version 0.24.0.dev3274

on_scroll dosent work on android.
`import flet as ft
def main(page: ft.Page):
page.title = "Scroll Increment Example"
counter_value = 0
counter = ft.Text(f"Counter: {counter_value}")

def on_scroll(e):
    nonlocal counter_value
    counter_value += 1
    counter.value = f"Counter: {counter_value}"
    counter.update()

items = [ft.Text(f"Item {i}") for i in range(50)]

list_view = ft.ListView(
    controls=items,
    on_scroll=on_scroll,
    height=400,
    expand=True
)

page.add(counter, list_view)

ft.app(target=main)
`

on_scroll dosent work on mobile apk:
import flet as ft
def main(page: ft.Page):
page.title = "Scroll Increment Example"
counter_value = 0
counter = ft.Text(f"Counter: {counter_value}")

def on_scroll(e):
    nonlocal counter_value
    counter_value += 1
    counter.value = f"Counter: {counter_value}"
    counter.update()

items = [ft.Text(f"Item {i}") for i in range(50)]

list_view = ft.ListView(
    controls=items,
    on_scroll=on_scroll,
    height=400,
    expand=True
)

page.add(counter, list_view)

ft.app(target=main)

Might be a new android "weirdos": https://github.com/flet-dev/flet/issues/3867
You can report it there so it can be considered when fixing the others.


ModuleNotFoundError: No module named 'torchdiffeq' for from torchdiffeq import odeint_adjoint as odeint

When I run this notebook from you, I get the following error.
Could you please guide me how to fix it?
https://colab.research.google.com/drive/13qu74xDsHCgQLsHfjACJ5DGF9JkOJYYu#scrollTo=VGwZinRQHX-T

Not sure, but the notebook seems to be running just fine at my end. Can you please check again if you are facing the problem?

Hi Kunal,
Thank you so much for having a look. Yeah I ran it again and occurred the same problem. Despites all the cell above having no problem with execution.
Here's more screenshot. I really appreciate if you could help me fix it:

Hi.
I think I can replicate the problem on my end. It seems to work sometimes but fail otherwise. I am looking into it. In the mean time, I'd suggest that you download the notebook and run it locally. That should hopefully work.
Kunal

I am facing the same issue

I solved it by restarting runtime and installed torchdiffeq using !python3 -m pip install torchdiffeq


Makefile: make check_sequence a order-only prerequisites

The Makefile rule for the $(EMOJI).ttf target passes the first
prerequisite to the emoji_builder python script using the $< automatic
Makefile variable. For this reason, the first prerequisite of this
target must be $(EMOJI).tmpl.ttf. Otherwise the following
error message is emitted:
FileNotFoundError: [Errno 2] No such file or directory: 'check_sequence'

This commit moves the check_sequence prerequisite to the order-only
prerequisites of where it actually belongs as the target itself should
not be updated if check_sequence is executed.

I built the font from source and have not come across this error, just offering a different data point here.

Ok, that's strange. I don't really see how this Makefile target, which uses $< (i.e. the first prerequisite) as an argument to $(EMOJI_BUILDER), is supposed to work if $< == check_sequence. Maybe the Makefile target wasn't invoked in your case, who knows.

Could be, to be honest I haven't dug deep into it, I only wanted to offer my anecdotal evidence.

This was fixed in c679409f9bd14537cdf81c96774f028d6d9efdba.


isValid doesn't work for particular mask

I want to validate input value before applying plugin (because plugin amends current input value and in this case I just want to erase current value). But there is no way to invoke isComplete and $.inputmask.isValid fails for mask.

@azhuchkov ,
Can you provide the mask you are using?

I tried something like:
$.inputmask.isValid('DE123123131', {mask: 'DE9{9}'});

I will have a look

@azhuchkov ,
When you are using a version above 3.1.63 you need to use
inputmask.isValid('DE123123131', {mask: 'DE9{9}'});


 I stated no. We should expand the omnibus to include rules regarding NSFW images on the site.

omnibus has been expanded and this should be added in in short order


Unit Test Failures Related to OBJECT_ID in FeatureLayer Tests

Description
There seems to be a recurring issue with the OBJECT_ID attribute when executing ApplyEdits in the FeatureLayer tests.
Two tests consistently fail, producing errors indicating that OBJECT_ID cannot be read from undefined.
Steps to Reproduce

Execute the TestCanUpdateManyFeaturesWithApplyEdits test case.
Execute the TestCanDeleteManyFeaturesWithApplyEdits test case.

Expected Behavior
The tests should complete without any errors, successfully updating and deleting multiple features with ApplyEdits.
Actual Behavior
Both tests are failing. The screenshot attached to this issue illustrates the test failures and their associated error messages.

Potential Causes

The OBJECT_ID attribute may not be correctly set or passed to the ApplyEdits function.
The features being edited might not be correctly initialized with an OBJECT_ID.

Should be fixed as part of #313


[New port request] zydis

Fast and lightweight x86/x86-64 disassembler library https://zydis.re

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.