I got "Self referencing loop detected with type" without loops...

Source/destination types
using System;
using Newtonsoft.Json;

public class ISomeJsonConverter : JsonConverter<ISome>
 {
    public override void WriteJson(JsonWriter writer, ISome value, JsonSerializer serializer)
    {
        serializer.Serialize(writer, value);
    }

    public override ISome ReadJson(JsonReader reader, Type objectType, ISome existingValue, bool hasExistingValue,
        JsonSerializer serializer)
    {
        return null;
    }
}

[JsonConverter(typeof(ISomeJsonConverter))]
public interface ISome { }

public class Impl : ISome { }

public class Other
{
    public ISome SomeImpl = new Impl();
}

public static void Main()
{
    //Here 'loop detected' exception will be thrown...
    var sdf = JsonConvert.SerializeObject(new Other());
}

Expected behavior
It should just works, without loop exceptions.
Actual behavior
Well, i thought, this kind of construction should work fine, acording to docs (https://www.newtonsoft.com/json/help/html/JsonConverterAttributeClass.htm).
But it throws.
If i add [JsonConverter(typeof(ISomeJsonConverter))], to the field Other.SomeImpl, it will work as expected.
Steps to reproduce
Just run this code, in your IDE
P.S.
I got plenty of classes where interface based serialization used. And it will be nice if i could use JsonConverter attribute on Interface it self, cause it makes classes more clear, due to less attributes.
Hope you could fix it, or at least explain why this is "ok" behaviour.
Kind Regards.

I ve got this issue on 12.0.3 nuget version.
Runtimes 3.1.100 and 5.0.100

This is not a bug in Json.NET, but a bug in your project.
Before i explain what happens on a technical level in your code there, i want to point out a major flaw in your ISomeJsonConverter: From what i can tell, the ISomeJsonConverter should be invoked when serializing an ISome instance. But all the converter does is calling the serializer again to serialize the object. There is no point in doing that. The JsonConverter attribute tells the serializer to not serialize an ISome instance the normal way as the serializer would do, but rather invoke the ISomeJsonConverter. But then, all the ISomeJsonConverter is to tell the serializer to serialize the ISome object instance the normal way anyway. If the converter just invokes the serializer with the given ISome object instance again, what is the point of having that converter?
But back to why your serialization code loops in one case, but not in the other...
In the first case - the JsonConverter attribute associated with the ISome interface itself. the serializer eventually has to serialize an object instance that implements ISome. So, it invokes the ISomeJsonConverter associated with this interface type. The ISomeJsonConverter just tells the serializer to serialize the object that implements ISome. So the serializer invokes the ISomeJsonConverter associated with this interface type. The ISomeJsonConverter just tells the serializer to serialize the object that implements ISome. So the serializer invokes the ISomeJsonConverter ... add nauseum... there is your loop.
Removing the JsonConverter attribute from the interface type will break this loop. But then, why does the loop not happen if you have the JsonConverter attribute on the Other.SomeImpl property?
In the second case (JsonConverter attribute only on the Other.SomeImpl property), the serializer will eventually serialize the SomeImpl property of the Other object instance. Without looking at the type of the object assigned to the property, the serialize invokes the ISomeJsonConverter with the property value (an object implementing the ISome interface). The ISomeJsonConverter tells the serializer to serialize this object implementing the ISome interface, which the serializer does. Note that the ISome interface itself, nor any member of the ISome interface is associated with the ISomeJsonConverter. Thus, when serializing the object implementing ISome, the serializer won't ever come across a JsonConverter attribute attached to the ISome interface or its members, so there is no situation that the converter will be called recursively.

This is not a bug in Json.NET, but a bug in your project.
Before i explain what happens on a technical level in your code there, i want to point out a major flaw in your ISomeJsonConverter: From what i can tell, the ISomeJsonConverter should be invoked when serializing an ISome instance. But all the converter does is calling the serializer again to serialize the object. There is no point in doing that. The JsonConverter attribute tells the serializer to not serialize an ISome instance the normal way as the serializer would do, but rather invoke the ISomeJsonConverter. But then, all the ISomeJsonConverter is to tell the serializer to serialize the ISome object instance the normal way anyway. If the converter just invokes the serializer with the given ISome object instance again, what is the point of having that converter?
But back to why your serialization code loops in one case, but not in the other...
In the first case - the JsonConverter attribute associated with the ISome interface itself. the serializer eventually has to serialize an object instance that implements ISome. So, it invokes the ISomeJsonConverter associated with this interface type. The ISomeJsonConverter just tells the serializer to serialize the object that implements ISome. So the serializer invokes the ISomeJsonConverter associated with this interface type. The ISomeJsonConverter just tells the serializer to serialize the object that implements ISome. So the serializer invokes the ISomeJsonConverter ... add nauseum... there is your loop.
Removing the JsonConverter attribute from the interface type will break this loop. But then, why does the loop not happen if you have the JsonConverter attribute on the Other.SomeImpl property?
In the second case (JsonConverter attribute only on the Other.SomeImpl property), the serializer will eventually serialize the SomeImpl property of the Other object instance. Without looking at the type of the object assigned to the property, the serialize invokes the ISomeJsonConverter with the property value (an object implementing the ISome interface). The ISomeJsonConverter tells the serializer to serialize this object implementing the ISome interface, which the serializer does. Note that the ISome interface itself, nor any member of the ISome interface is associated with the ISomeJsonConverter. Thus, when serializing the object implementing ISome, the serializer won't ever come across a JsonConverter attribute attached to the ISome interface or its members, so there is no situation that the converter will be called recursively.

Well, thanks for this explanation.
I got your point of view, that this is not a bug , but a feature. But as a user of json.net library, and with out of clear knowlage of it's internal behaviours, i (and even my colleagues) couldn't tell that this particular case isn't a bug, or not some kind of unintended behaviour.
Again, from user perspective, "reference loop detected", is a wrong kinda error for this situation at the top level of serialization logic. May be for some internal error handling error it is ok, as one of the factors for resolving more descriptive user facing error, which should tell about bad/wrong library api usage. But for end user it isn't good enough. Because it missleading. I've spent lot of time debugging, and trying figure out where in my project i got loop references (but i was sure that there is no any, and even couldn't be).
But after many googling attempts, trying many different thing i found that, particular scenario (from example), which makes this "loop".
May be i should ask about it on SO, and got answer quicker, but common, this is looks like a bug. This is why i opened this issue. This behaviour should at least be documented, or mentioned somewhere. Like, "if you got ref loop, this might be, because of real loop refs, and also because we couldn't track some mad attribute usages", or "you shouldn't not mark ifaces with JsonConverter atrribute, because it may lead to wierd/strange behaviour at serialization time", but there is no any of that done anywhere in the docs/examples.
The best way of course will be throwing other type of exception, which is more clear for end user of json.net library, but i don't know if it possible at all.
Anyway, i understood, that my usage of this attribute isn't compatible with current logic of lib, but it isn't obvious, and this, i think should be fixed. At least by me writing about this case in issues on github.
About example, and about "bug in my project". My project little bit more complex than this boiled down example. And, obviously i shouldn't copy paste 50kloc+ here, to demonstrate where some strange thing happened.
This example just shows, how you could get, weird loop ref error.
About no point of doing things like that. There actually is point of doing something like that. In my particular case, i got node graph, which stores nodes in a list of INode derived objects, and list of links between them. INode contains common properties, and special property called NodeKind, which used to identify node when deserializing graph from json. I won't use explicit type handling, because this graph may be used outside of .net runtimes, and in case of refactoring namespaces, i won't deal with problems when loading some dated graphs with old ns/type names. And i am pretty happy how default serializer doing it's job when serializing this graphs. This is why JsonConverter from example written exactly like that. It should serialize node in a default way, and deserialize them with custom logic, based on node_kind property which was omited in example cause it doesn't deal with that error.
I've use kinda work around in my project, specifying item converter through JsonProperty attribute for lists. It worked, but i must use it everywhere, to get INode deserialized correctly. Which isn't as nice as i if could just mark my ifaces/abstract classes with JsonConverter attrib. And forgot about the fact that i should always specify converter type here and there.
Hope that description was clear enough, and problem became more obvious. But in my opinion, this error should be handled somehow else then just throwing loop ref detected.
Json.net is a great project, i really love it, and i hope it could become even better and more user friendly, if this kind of errors will be handled/documented.

Well, thanks for this explanation.
I got your point of view, that this is not a bug , but a feature. But as a user of json.net library, and with out of clear knowlage of it's internal behaviours, i (and even my colleagues) couldn't tell that this particular case isn't a bug, or not some kind of unintended behaviour.
Again, from user perspective, "reference loop detected", is a wrong kinda error for this situation at the top level of serialization logic. May be for some internal error handling error it is ok, as one of the factors for resolving more descriptive user facing error, which should tell about bad/wrong library api usage. But for end user it isn't good enough. Because it missleading. I've spent lot of time debugging, and trying figure out where in my project i got loop references (but i was sure that there is no any, and even couldn't be).
But after many googling attempts, trying many different thing i found that, particular scenario (from example), which makes this "loop".
May be i should ask about it on SO, and got answer quicker, but common, this is looks like a bug. This is why i opened this issue. This behaviour should at least be documented, or mentioned somewhere. Like, "if you got ref loop, this might be, because of real loop refs, and also because we couldn't track some mad attribute usages", or "you shouldn't not mark ifaces with JsonConverter atrribute, because it may lead to wierd/strange behaviour at serialization time", but there is no any of that done anywhere in the docs/examples.
The best way of course will be throwing other type of exception, which is more clear for end user of json.net library, but i don't know if it possible at all.
Anyway, i understood, that my usage of this attribute isn't compatible with current logic of lib, but it isn't obvious, and this, i think should be fixed. At least by me writing about this case in issues on github.
About example, and about "bug in my project". My project little bit more complex than this boiled down example. And, obviously i shouldn't copy paste 50kloc+ here, to demonstrate where some strange thing happened.
This example just shows, how you could get, weird loop ref error.
About no point of doing things like that. There actually is point of doing something like that. In my particular case, i got node graph, which stores nodes in a list of INode derived objects, and list of links between them. INode contains common properties, and special property called NodeKind, which used to identify node when deserializing graph from json. I won't use explicit type handling, because this graph may be used outside of .net runtimes, and in case of refactoring namespaces, i won't deal with problems when loading some dated graphs with old ns/type names. And i am pretty happy how default serializer doing it's job when serializing this graphs. This is why JsonConverter from example written exactly like that. It should serialize node in a default way, and deserialize them with custom logic, based on node_kind property which was omited in example cause it doesn't deal with that error.
I've use kinda work around in my project, specifying item converter through JsonProperty attribute for lists. It worked, but i must use it everywhere, to get INode deserialized correctly. Which isn't as nice as i if could just mark my ifaces/abstract classes with JsonConverter attrib. And forgot about the fact that i should always specify converter type here and there.
Hope that description was clear enough, and problem became more obvious. But in my opinion, this error should be handled somehow else then just throwing loop ref detected.
Json.net is a great project, i really love it, and i hope it could become even better and more user friendly, if this kind of errors will be handled/documented.

I feel like I should leave a comment here, because after googling for answers to the same exact issue, I came across this page.
I think what is missing from the OP's original bug report is the intent of the action they were trying to perform. In my case, my intent was to create a custom JsonConverter that performs a custom Deserialization on a particular type, and executes default Serialization on the same type. My first attempt had me trying OP's exact same method, because it feels like the right method in order to get whatever the default serialization behavior is: serializer.Serialize(writer, value);, with the same result - the self-referencing loop error. After wasting a couple of hours on the problem, I finally found the solution.
public class ISomeJsonConverter : JsonConverter<ISome>
{
    public override void WriteJson(JsonWriter writer, ISome value, JsonSerializer serializer)
    {
        throw new NotImplementedException();
    }

    public override bool CanWrite => false;

    public override ISome ReadJson(JsonReader reader, Type objectType, ISome existingValue, bool hasExistingValue, JsonSerializer serializer)
    {
        return null;
    }
}

Somehow, setting CanWrite to return false will actually pass serialization back to the default converter. To me, this is not intuitive at all - I figured that when trying to serialize it would throw the NotImplementedException (spoiler: it doesn't). And there is nothing anywhere that tells me that this would pass serialization control back to some other converter. It was basically just trial and error that got me here.

I ran into a similar issue recently. I was using a JsonConverterAttribute to mark a base class for items in a List to use a custom JsonConverter. My code could deserialize objects fine and that was all I was worried about for a while. Tried to test serializing objects back to JSON recently and then ran across the Self referencing loop issue. Tried many workarounds found on SO but nothing worked for both serializing and deserializing. Luckily I stumbled across this GitHub issue particularly the post by gwartnes.
The exception thrown in this case is not too clear and there aren't any docs, that I could find, that cover this use case.

My first attempt had me trying OP's exact same method
I also spent half a day arriving at the same initial solution, the same problem and after googling, arriving at the same page here.  This seems to be a common problem only to customize only Deserialization but not Serialization.

2024 and Bing AI / MS Copilot makes the same error! :-D I.e. not setting CanWrite to false to force the converter back to default. Agreed the Newtonsoft design is unintuitive and weird.


transaction error

When I successfully call EthGetBalance and then call EthSendTransaction, there will be errors reported, including requesting other interfaces。
My usage scenario is when I first use personal_ Sign successfully, and then my project must use ETH_ SendTransaction, and then report the same error as above.

Hey @GaoG001108 I'm sorry I can not help you with your request as I'm struggling myself with this. Could you share how did you achieve to succeed with eth_personalSign?

Hi @GaoG001108 and @dpradell-dev The specific error you posted should be resolved with the latest commit. However, doing EthGetBalance through WalletConnect may not be supported by your wallet. See #96

This issue is a duplicate of #96


[UX] Tag text selection forbidden

To forbid selecting tag text in the search page

LGTM, Merge it!


Is there any way to achieve theano scan?

rnn example only supports fixed length sequence.
Bind many executors for each length? Then how to train by batch? by bind a tmp sym of Group()?

I think your method will do the work.
Every batch, bind a few groups of symbols with same Weights to a different executor, and average the gradient to update the Weights.

We are currently discussing ways to implement it. Bind many executor is an optional solution.

@antinucleon So there will be some APIs like theano's scan?

This is now handled with bucketing. See example/rnn


Improve "about" section on the repository GitHub page

The current about section should concisely present the package.

Can you check this? I still see the old description.

(And the link to MTK is not correctly formatted, so it is probably not supported and we shouldn't use the link then.)

is it visible now? i see it fine on my end

are we not talking about this?

i.. did not see the correction, i thought it was just a citation, i'm really sorry!

i corrected it..


Identifiers validation failed for dataset Poliquetos litorales de la región norte y centro del estado de Veracruz

Identifier validation failed for the dataset Poliquetos litorales de la región norte y centro del estado de Veracruz:

Crawler attempt: 322
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 398
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 398 total records; 398 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740316/step

New IDs sample:

Old IDs sample:

754ebfade3ea5324fa4b96fd5b9d27f0
869eefb87b58aa8ece412aae0df4953d
29b5051902beed51d04365d59ec350a9
34e0371bd71cb82c5420899d97467c59
796a749b4092b5cd02be1a054428735b
b255679559eb3f50ae516c611666489d
cd5fdd66ae8497fee83a3c32f7f74ff2
006e34aab70bcc86aa48a96c2e0c6e9a
02409475b7f26189d9083ec33902d50c
0d0a9c4426c7b54eda5b9ce7f884fdde

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Poliquetos litorales de la región norte y centro del estado de Veracruz : https://doi.org/10.15468/k8pctf.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Poliquetos litorales de la región norte y centro del estado de Veracruz:

Crawler attempt: 323
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 398
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 398 total records; 398 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741176/step

New IDs sample:

Old IDs sample:

754ebfade3ea5324fa4b96fd5b9d27f0
869eefb87b58aa8ece412aae0df4953d
29b5051902beed51d04365d59ec350a9
34e0371bd71cb82c5420899d97467c59
796a749b4092b5cd02be1a054428735b
b255679559eb3f50ae516c611666489d
cd5fdd66ae8497fee83a3c32f7f74ff2
006e34aab70bcc86aa48a96c2e0c6e9a
02409475b7f26189d9083ec33902d50c
0d0a9c4426c7b54eda5b9ce7f884fdde

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Poliquetos litorales de la región norte y centro del estado de Veracruz : https://doi.org/10.15468/k8pctf.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Poliquetos litorales de la región norte y centro del estado de Veracruz:

Crawler attempt: 325
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 398
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 398 total records; 398 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741805/step

New IDs sample:

Old IDs sample:

754ebfade3ea5324fa4b96fd5b9d27f0
869eefb87b58aa8ece412aae0df4953d
29b5051902beed51d04365d59ec350a9
34e0371bd71cb82c5420899d97467c59
796a749b4092b5cd02be1a054428735b
b255679559eb3f50ae516c611666489d
cd5fdd66ae8497fee83a3c32f7f74ff2
006e34aab70bcc86aa48a96c2e0c6e9a
02409475b7f26189d9083ec33902d50c
0d0a9c4426c7b54eda5b9ce7f884fdde

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Poliquetos litorales de la región norte y centro del estado de Veracruz : https://doi.org/10.15468/k8pctf.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


Kotlin Platform refactor

Plan

[x] Rename Platform.kt
[x] Mechanical Refactor Platform
[x] Rename *Platform.kt
[x] Mechanical Refactor *Platform
[x] Cleanup & Sane JVM conventions (minimal for internal classes)

Later?

[ ] Idiomatic Kotlin code

We could also migrate file by file if this becomes too big

Some spaces to cleanup still, but potentially shippable.

I may have gone a little heavy on

"if to when"
lift return out
convert to expression body

@swankjesse @JakeWharton What's the current advice on japi for internal? Can't we ignore these?
Comparing binary compatibility of  against
***! MODIFIED CLASS: PUBLIC (<- PACKAGE_PROTECTED) FINAL (<- NON_FINAL) okhttp3.internal.platform.AndroidPlatform  (not serializable)
	---! REMOVED METHOD: PUBLIC(-) STATIC(-) okhttp3.internal.platform.Platform buildIfSupported()
***! MODIFIED CLASS: PUBLIC (<- PACKAGE_PROTECTED) STATIC FINAL okhttp3.internal.platform.AndroidPlatform$CloseGuard  (not serializable)
	***! MODIFIED METHOD: PUBLIC (<- PACKAGE_PROTECTED) FINAL (<- NON_FINAL) java.lang.Object createAndOpen(java.lang.String)
	***! MODIFIED METHOD: PUBLIC (<- PACKAGE_PROTECTED) FINAL (<- NON_FINAL) boolean warnIfOpen(java.lang.Object)
***! MODIFIED CLASS: PUBLIC FINAL (<- NON_FINAL) okhttp3.internal.platform.ConscryptPlatform  (not serializable)
***! MODIFIED CLASS: PUBLIC (<- PACKAGE_PROTECTED) FINAL (<- NON_FINAL) okhttp3.internal.platform.Jdk8WithJettyBootPlatform  (not serializable)
***! MODIFIED CLASS: PUBLIC (<- PACKAGE_PROTECTED) FINAL okhttp3.internal.platform.Jdk9Platform  (not serializable)
***! MODIFIED CLASS: PUBLIC okhttp3.internal.platform.Platform  (not serializable)
	---! REMOVED METHOD: PUBLIC(-) STATIC(-) java.util.List alpnProtocolNames(java.util.List)
	***! MODIFIED METHOD: PUBLIC FINAL (<- NON_FINAL) okhttp3.internal.tls.CertificateChainCleaner buildCertificateChainCleaner(javax.net.ssl.SSLSocketFactory)
	***! MODIFIED METHOD: PUBLIC FINAL (<- NON_FINAL) java.lang.String getPrefix()

Can you suppress everything in internal ?


400+ RPC requests until staking page is ready

When opening the staking page for specific pool - https://wallet.near.org/staking/buildlinks.poolv1.near/stake, it takes 400 RPC requests to get to the state when "Amount" is editable.

Working on a PR here to improve performance of /staking while we only load everything once when the user navigates to the route and again when the user performs a staking action, it's a lot of calls.
https://github.com/near/near-wallet/pull/1314
Couple of notes:
1314 removes an extra call to getValidators that results in all validators being pulled (reduces RPC calls by 53 on testnet and probably > 60 on mainnet)
We can bring down RPC calls even more when we use the new indexer. Here's why:
Currently, we have to make at least 1 RPC call across all validators to see if the user even has a balance with the validator. Only if they do, we make subsequent calls.
We can replace another > 60 RPC calls on mainnet because we'll have all this info from indexer. Already done here:
https://github.com/near/near-wallet/pull/1273
Was waiting on reviews and time for all this to be merged.
https://github.com/near/near-wallet/pull/1273 relies on https://github.com/near/near-contract-helper/pull/288

Can confirm RPC requests cut down significantly by https://github.com/near/near-wallet/pull/1273


Taking Long time to show Preview

It taking about 5 to 6 seconds to show preview

Related to this, has anyone came up with a solution to cache the data?

I m having same issue with loading the data , it takes long time

Takes a lot of time for me too. Core logic is there, maybe i will build my own wrapper around it.

i'm using this library in chat so if you have all the messages with link then it takes too much time to load, any solution for this?


Infinite flying with jetpack

On a 1.7.10 Server (Forge, FTB Infinity) I'm able to fly infinitly. Using the Jetpack, setting it in hover mode, turning it off and there you go. Now you can fly infinitly.

What version of AR and libvulpes are you using?

Im not sure about libVulpes (gonna edit this when I have acess to the files) but AR-1.2.2

Looks like #177

Closing this, has been to long and its a duplicate, never mind.


iOS 7 Compatibility

Why PhoneKit isn't compatible with iOS 7? this pod is quite useful but i think it needs iOS 7 support..

It certainly is compatible with iOS 7, what would make you think otherwise?


Add Chinese translation for some new features

Hi @MineTestGaming, this is showing all previous changes, you need to create a separate branch in your fork, with remote as this repo's master.
Follow this guide if you face any issues https://opensource.com/article/19/7/create-pull-request-github

Sorry for my wrong operaration, and I will try to use this correct way.


gvm install go1.16 requires go to already be installed

Description
Installing go requires that go is already installed.
Steps to Reproduce

Using Ubuntu 20.04cat <<-EOF > Vagrantfile
Vagrant.configure("2") do |config|
   config.vm.box = "generic/ubuntu2004"
end
EOF
vagrant up
vagrant ssh

Install gvmsudo apt-get install -y binutils bison gcc make
bash < <(curl -s -S -L https://raw.githubusercontent.com/moovweb/gvm/master/binscripts/gvm-installer)
source ~/.gvm/scripts/gvm
gvm install go1.16

Expected Results
go1.16 would be installed
Actual Results
I get this error:
Downloading Go source...
Installing go1.16...
 * Compiling...
/home/vagrant/.gvm/scripts/install: line 84: go: command not found
ERROR: Failed to compile. Check the logs at /home/vagrant/.gvm/logs/go-go1.16-compile.log
ERROR: Failed to use installed version

And looking at the compile log:
cat $HOME/.gvm/logs/go-go1.16-compile.log
ERROR: Cannot find /home/vagrant/go1.4/bin/go.
Set $GOROOT_BOOTSTRAP to a working Go tree >= Go 1.4.

https://github.com/moovweb/gvm#a-note-on-compiling-go-15

https://github.com/moovweb/gvm#a-note-on-compiling-go-15

I get this error when trying to follow those steps:
gvm install go1.4 -B
Installing go1.4 from binary source
ERROR: Binary Go unavailable for this platform

I'm using MacOS Big Sur

https://github.com/moovweb/gvm#installing-go
There is a list of switches, you might want to read the documentation carefully.

I am late to the party, but
...
Building C bootstrap tool.
cmd/dist
Building compilers and Go bootstrap tool for host, darwin/amd64.
lib9
libbio
liblink
cmd/cc
cmd/gc
cmd/6l
/Users/pebishop/.gvm/gos/go1.4/src/cmd/6l/../ld/dwarf.c:1472:15: error: implicit conversion from 'int' to 'char' changes value from 156 to -100 [-Werror,-Wconstant-conversion]
/Users/pebishop/.gvm/gos/go1.4/src/cmd/6l/../ld/dwarf.c:1756:21: error: implicit conversion from 'int' to 'char' changes value from 144 to -112 [-Werror,-Wconstant-conversion]
/Users/pebishop/.gvm/gos/go1.4/src/cmd/6l/../ld/lib.h:168:13: note: expanded from macro 'cput'
go tool dist: FAILED: clang -Wall -Wstrict-prototypes -Wextra -Wunused -Wno-sign-compare -Wno-missing-braces -Wno-parentheses -Wno-unknown-pragmas -Wno-switch -Wno-comment -Wno-missing-field-initializers -Werror -fno-common -ggdb -pipe -Wuninitialized -O2 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -mmacosx-version-min=10.6 -c -m64 -I /Users/pebishop/.gvm/gos/go1.4/include -I /Users/pebishop/.gvm/gos/go1.4/src/cmd/6l -o /Users/pebishop/.gvm/gos/go1.4/pkg/obj/cmd/6l/dwarf.o /Users/pebishop/.gvm/gos/go1.4/src/cmd/6l/../ld/dwarf.c
...
getting the same error.
I see this: https://github.com/moovweb/gvm/issues/369#issuecomment-826634454
was it helpful - cause I don't have a clear understanding of how the switches should work.

For others encountering this issue, as per the README, you need a preexisting go installation for gvm to function. However, unlikely the README, you can't use gvm to install go1.4 as the packages no longer are available. A quick solution that is less than optimal, but functional, is to do:
brew instal go
gvm install go1.16
gvm use go1.16
brew uninstall go

After that, you should be good to go (assuming you have both brew and gvm installed and configured).


Update action_session_start customisation code sample in Default Actions docs

Description of Problem:
I’m using Rasa 2.0, and have an actions server set up with a custom action working correctly. I wanted to try customising the action_session_start action, however, using the code sample in the docs for Default Actions I get errors about EventType being undefined.
I describe the issue in detail in this forum post: https://forum.rasa.com/t/are-2-0-docs-obsolete-for-customising-action-session-start/36219
Overview of the Solution:
Unless I've missed something big, it seems to me the code sample is for a previous version of Rasa?
I have a new code sample here that follows the same logic and works:
https://forum.rasa.com/t/are-2-0-docs-obsolete-for-customising-action-session-start/36219/2?u=digitalwestie
Definition of Done:

[ ] Code sample is updated in docs

Thanks for submitting this feature request 🚀 @tabergma will get back to you about it soon! ✨

@digitalWestie do you mind creating a PR for this, I just ran into this as well

@tmbo ok so that confirms it! Sure I'll send a PR.

Here we go: https://github.com/RasaHQ/rasa/pull/7287


Is there any plan for releasing any version with changes in dev?

I'm worried of using current bits of dev directly to avoid any future problem with an upgrade to an official release.
Is there any schedule or estimated release date  of a new version with changes in dev?
Are my concerns justified in your opinion? Or since last release still there is not any change that needs to add an upgrade process when the new version with changes in dev is going to be released, so I don't have to be worried.

@BenedekFarkas will help on this.

All the changes for fixing Dynamic Compilation (and support Roslyn for C# 6 and above) are now working on 1.10.x (I did some further improvements today). I just merged all those into dev and made the necessary changes there to the modules that aren't on dev (Orchard.Glimpse and Orchard.OpenId).
So I think 1.10.x is ready for a 1.10.3 version release. There's two things on dev that we should take care of (and then it's ready for a 1.11 version release):

https://github.com/OrchardCMS/Orchard/issues/7832#issuecomment-353670873
#7924

@jersiovic 1.10.3 is in pre-release now, so after that we'll focus on releasing 1.11 ASAP, but there are a few things to fix there as well.


Only one of two PV installation shown (both present on one address)

hi,
I have 2 separate Zonneplan PV installations. One with 15 panels (installed in 2021) and one with 18 panels (installed in 2024). The integration only shows one of the installations. Some sensors are duplicated ('Zonneplan last measured value' / 'Zonneplan yield total') but the given values belong only to the first installation of 2021. The sensor Zonneplan yield today shows the combined value of both PV installations.

Debug log;
The log shows both installations and unique 'last_measured_power_value' numbers.

[{'uuid': '', 'label': 'PV Installatie', 'type': 'pv_installation', 'start_date': '2021-06-24T22:00:00.000000Z', 'end_date': '2031-06-24T22:00:00.000000Z', 'meta': {'identifier': 'Identifier of installation 1', 'name': 'Zonneplan One omvormer', 'panel_count': 15, 'panel_type': None, 'installation_wp': 5550, 'panel_wp': 370, 'first_measured_at': '2021-06-24T18:31:23.000000Z', 'last_measured_at': '2024-03-06T08:55:23.000000Z', 'last_measured_power_value': 2281, 'grid_stabilization_active': False, 'total_power_measured': 13074780, 'network': {'name': 'Onbekend', 'color': 'unknown', 'status': 'Onbekend'}, 'sgn_serial_number': '', 'module_firmware_version': 'v3.0.10', 'inverter_firmware_version': 'v3.036', 'show_in_contract_screen': False, 'enable_pv_analysis': False}}, {'uuid': '', 'label': 'PV Installatie', 'type': 'pv_installation', 'start_date': None, 'end_date': None, 'meta': {'identifier': 'Identifier of installation 2', 'name': 'Zonneplan One omvormer', 'panel_count': 18, 'panel_type': None, 'installation_wp': 7920, 'panel_wp': 440, 'first_measured_at': '2024-03-05T15:10:09.000000Z', 'last_measured_at': '2024-03-06T08:55:00.000000Z', 'last_measured_power_value': 2819, 'grid_stabilization_active': False, 'total_power_measured': 5900, 'network': {'name': 'Vodafone', 'color': 'poor', 'status': 'Slecht'}, 'sgn_serial_number': '', 'module_firmware_version': '1.2.1r', 'inverter_firmware_version': '3063', 'show_in_contract_screen': False, 'enable_pv_analysis': False}}], 'features': [], 'buttons': []}]

I removed the integration from Homeassistant and deleted it from HACS. Installed again via HACS. Rebooted and installed the integration again but this didn't resolve my issue.
I hope you can help out!
Thanks in advance!
Best regards, Ruud

Looks like 2 different installs. 1 with 15 panels and 1 with 18 panels.
Was your install changed from 15 to 18 panels?

I have two separate installations. So also two converters. 1 with 15 panels and 1 with 18 panels. Total 33 panels.
Verzonden vanaf Outlook voor Androidhttps://aka.ms/AAb9ysg

From: Frans Saris @.>
Sent: Wednesday, March 6, 2024 8:04:03 PM
To: fsaris/home-assistant-zonneplan-one @.>
Cc: kuuf1986 @.>; Author @.>
Subject: Re: [fsaris/home-assistant-zonneplan-one] Only one of two PV installation shown (both present on one address) (Issue #99)
Looks like 2 different installs. 1 with 15 panels and 1 with 18 panels.
Was your install changed from 15 to 18 panels?
—
Reply to this email directly, view it on GitHubhttps://github.com/fsaris/home-assistant-zonneplan-one/issues/99#issuecomment-1981585202, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEMNOOI5FK4KU52OHRWJUZLYW5SCHAVCNFSM6AAAAABEIWCHFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBRGU4DKMRQGI.
You are receiving this because you authored the thread.Message ID: @.***>

Ah, sorry misread your first comment.
Need to investigate this further. This worked before but I suspect that the last changes broke this

Can you provide some logs with debug data? That enables me to reproduce the situation in my test setup. You can send it to me for example using direct message on the forum https://community.home-assistant.io/u/minifranske/

Are you able to view the statistics of each install separately in the Zonneplan app?

Can you test version 2024.3.0b2
Each install gets its own device and the total yield is now part of a different device that holds all total values

Are you able to view the statistics of each install separately in the Zonneplan app?

per PV installation I can see the momentary delivered power and the total delivered power of the installation. the grahps only show thet combined power

ah, sorry. tagged the wrong branch. Please try 2024.3.0b3

I get this now:
Two devices:

First one:

Second one:

The second one shows now two unique last measured values which match both installations so this is good.
One remark; the device info mentions "Zonneplan One omvormer 18 panels door Zonneplan". While the sensors behind this device belong to both installations. So perhaps leave out the 18 panels in the name?
For the rest does this solve the issue I've initiated. I can read both installations now so that is already very nice! :) Thanks!

Can you try to remove the integration and re-add it again? You should now have 3 devices.

Zonneplan (totals)
Zonneplan pv 1
Zonneplan pv 2

Currently your PV installs are still combined
When that doesn't resolve the issue can you provide a dump of your logs with debug enabled for Zonneplan?

Reinstall did indeed create three devices, exactly as you indicated. Seems to work just fine now! Thanks!

Fix is released with 2024.3.0


Use GITHUB_TOKEN more consistently.

https://docs.github.com/en/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token
This provides enough permissions for almost everything we want to do.
When it's not enough (e.g. for brew update-maintainers): generate a dedicated, repo-specific token for this.

Review period skipped due to critical label.


Update Soroban Dapps Challenge copy

This PR removes the dapp redeployment step in the Crowdfund and LP dapp challenges.

Preview is available here:http://soroban-docs-pr631.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr631.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr631.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr631.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr631.previews.kube001.services.stellar-ops.com/


examples/audio: Improve SE delay on browsers

Looks like https://github.com/hajimehoshi/oto/issues/75 is the cause?

I feel like https://github.com/hajimehoshi/oto/issues/92 is the blocker

#944 is more serious

Let's use AudioWorklet.


refactor: remove unnecessary fragments and spaces

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

While extra whitespace, via {' '}, can serve a role (spacing out screen-reader text, for example), it doesn't seem to do anything here.

Me too! The ones in the component do matter, because they impact how the text is read aloud, but these didn't seem to do a thing.


Enable Windows CI for apple/swift-foundation

We currently do not have Windows CI coverage for apple/swift-foundation.  This has resulted in multiple regressions in the Windows path to be introduced over the recent changes.

CC: @parkera @iCharlesHu @itingliu


Create LandscapeDesign

deneme

Why did you make this PR for TestUp? This looks like functionality for a completely separate extension.


index.html build not in the outDir

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ x] feature request

Versions.
@angular/cli: 1.0.2
node: 6.9.5
os: darwin x64
Desired functionality.
I have many app in my .angular-cli.json and each app have one main.ts, index.html, style.css like appIndex.html, appMain.ts, appStyle.css with outDir=dist_app
when i build apps, i have a dist_app with appIndex.html not index.html
A option for indicate the name of the index.html for the outDir will be a good idea ?
sry for my bad english
thx

We actually just use the name you provide the CLI config, as some users requested us not to rename. That gives users better control.
It's not yet published but you can find docs for multiple app support here as well: https://github.com/angular/angular-cli/blob/master/docs/documentation/stories/multiple-apps.md

Can this be reopened?
I'm running into the same issue -- the behavior one would expect is that index.html be placed at the path specified in outDir, but if outDir is outside of --source-dir, index.html gets placed at a path relative to --source-dir.
I have an app set up using ng new my-app --source-dir src/client, so my node_modules, e2e, etc live in ~/my-app and the source files live in ~/my-app/src/client. I've set outDir to "./dist/public".
My issue is that index.html, instead of being placed in ~/my-app/dist/public, is being placed in ~/my-app/src/client/dist/public.
Snippet of my angular-cli.json:
...
"apps": [
    {
      "root": "./source/client",
      "outDir": "./dist/public",
      "assets": [
        "assets",
        "favicon.ico"
      ],
      "index": "index.html",
...


new post: multi cluster monitoring with Prometheus and inlets

Signed-off-by: Johan Siebens<EMAIL_ADDRESS>

Can we have an image higher up in the post, like the architecture diagram we had before?
And a new lead image instead of the bridge.

The architecture diagram is already available in the introduction (line 16)
Do you have a source to find good lead images?

added new lead image

I use unsplash and pexels - crop and then resize to 1660px width. And export to 70% quality aiming for < 280KB size.

Just jumping in with a suggestion for image optimization:
Maybe https://github.com/marketplace/imgbot is a good idea for this. It reduces file sizes for images by removing human non-visible details from the images. Afaik it's free for public repos


Ability to terminate arpwitch on SIGINT

Hello, I was just testing arpwitch to package it for Debian,
Currently it seems like it's not possible to exit on SIGINT (ctrl+c), so if I run arpwitch I have to send a kill signal (SIGTERM) to terminate its execution. I believe the user experience could be improved if I could terminate arpwitch with a ctrl+c directly so I'd like to request this feature.
Thanks for working on arpwitch :)

Done, thanks for the feature request -
https://github.com/verbnetworks/arpwitch/releases/tag/0.3.7

Done, thanks for the feature request -
https://github.com/verbnetworks/arpwitch/releases/tag/0.3.7


nodeunit cannot be run in strict mode

If I try to run nodeunit in JS strict mode, I get
/Users/nick/git/medium2/out/final/node_modules/nodeunit/bin/nodeunit:25
    testFullSpec_param_found = false;
                             ^
ReferenceError: testFullSpec_param_found is not defined
    at Object.<anonymous>

because testFullSpec_param_found is not properly declared.

fixed via https://github.com/caolan/nodeunit/commit/0402cb016ac61de06e941b2926a66a372d569dfb


Target entity resolver for DQL

Since we have target entity resolver in doctrine this class check is not enought.
To gain interface resolution it is better to add interface check in addition to class_check here.

@oprokidnev the fix seems legit, but it needs to be backed by a test case.

@oprokidnev I added tests and merged this into master as well, thanks!


Add doctests and update docs

Checklist

[x] Appropriate tests were added

To fix a failing doctest, an implementation of Base.show() was changed (735ea5e), which is covered by said doctest (b79465c8b)

[x] Any code changes were done in a way that does not break public API
[x] All documentation related to code changes were updated
[x] The new code follows the contributor guidelines, in particular the SciML Style Guide and COLPRAC.
[x] Any new documentation only uses public API

Additional context
Main changes:

Update GitHub repository owner name (jonniedie -> SciML)
Turn almost every code example into a doctest (this revealed some inconsistencies between presented documentation and observed behavior)

Thanks!


test request

test for notion Bridge

Issue Title:test request
Issue Updated Status: closed

Issue Title:test request
Issue Updated Status: closed

Issue Title:test request
Issue Updated Status: closed


Cleanup up console log messages

This PR cleans up the console messages used during development and testing, and puts the ones useful for debugging behind the __DEBUG__ switch. To see them in the console, the environment variable DEBUG_ERROR should be true.
It also plays an "underwater" sound when the download completes (.wav file found in the public domain is the sounds of a gulf toadfish).

  Medtronic Alpha Test - Issue Resolution Card [uploader]

Yes, I would love to have a logger with different logging levels, that also has the capability to send those logs back to us automatically in case of a failed upload.


How can I load an pretrained model to train my dataset with num_cls=2.

After I loaded the pretrained model file (namely 'upernet_swin_small_patch4_window7_512x512.pth'), an error was raised as the follow. What is different between my custom dataset with ADE20K is that the num_cls of mine is 2, not 150. So, did the pretrained model only be useful to the ADE? How can I load an pretrained model to train my dataset with num_cls=2.
Thank you for your help!
Traceback (most recent call last):
File "/home/xxx/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 179, in build_from_cfg
return obj_cls(**args)
File "/home/xxx/paper_code2/Swin-Transformer-Semantic-Segmentation/mmseg/models/segmentors/encoder_decoder.py", line 39, in init
self.init_weights(pretrained=pretrained)
File "/home/xxx/paper_code2/Swin-Transformer-Semantic-Segmentation/mmseg/models/segmentors/encoder_decoder.py", line 68, in init_weights
self.backbone.init_weights(pretrained=pretrained)
File "/home/xxx/paper_code2/Swin-Transformer-Semantic-Segmentation/mmseg/models/backbones/swin_transformer.py", line 594, in init_weights
load_checkpoint(self, pretrained, strict=False, logger=logger)
File "/home/xxx/paper_code2/Swin-Transformer-Semantic-Segmentation/mmcv_custom/checkpoint.py", line 340, in load_checkpoint
table_current = model.state_dict()[table_key]
KeyError: 'backbone.layers.0.blocks.0.attn.relative_position_bias_table'
During handling of the above exception, another exception occurred:

The pretrained model you used is not Swin-T SSL model. You have to use this one

:

Have you solved this question？
Are you using swin for segmentation？


Specify the version of MRTRix when installing

This could be a commit hash or a tag. By specifying it in Dockerhub you will be able to trigger image rebuilding by updating the version in the file. It also helps with figuring out which version was used to build the container without having to pull the image.

We generate version tags like this: '0.3.15-367-g05dee093', which is the tag (0.3.15) followed by the number of commits since that tag, and then a hash snippet. So it makes sense that that's what should appear.
Not quite sure how best to handle this though. Should this go into its own 'version' file in the repo? When the container is built, should it be this version of MRtrix3 that is pulled and built, or should the version file be updated with whatever the build process pulls? It's slightly difficult here since MRtrix3 is still a moving target, we don't yet recommend versions at a particular tag but encourage use of the latest code, and the BIDS app script I expect will undergo its own parallel development so needs its own separate version tag.

I probably wasn't too clear when describing the problem.  This is problematic for two reasons 1) Docker is caching each line of the Dockerfile in a separate layer, it decides whether to reuse a cached layer based on the content of the Dockerfile; to force getting a new version of mrtrix this line would have to change 2) it would be nicer to have a clear indication of which version of MRtrix was used in this container (in the Dockerfile).
The easiest way is to checkout a commit hash or a tag. Like Anders is doing in BROCCOLI https://github.com/BIDS-Apps/BROCCOLI/blob/master/Dockerfile#L54
Now you also mentioned the version of the MRtrix3_connectome BIDS App. I have written about versioning extensively here: http://bids-apps.neuroimaging.io/dev_faq/ but you are raising a few new issues:

the /version file should not be touched - it is only a placeholder that is filled with the current tag in CircleCI (see: https://github.com/BIDS-Apps/MRtrix3_connectome/blob/master/circle.yml#L16)

when releasing a new version of the MRtrix3_connectome BIDS App you can use any string that is valid Docker Hub tag (so no "+" signs). It's really up to you. I would however recommend something that is combination of the version of the MRtrix installed in the container image and the version of runscript/Dockerfile. For example 0.3.15-367-g05dee093-2.

I hope this helps!

It's now a specific MRtrix3 commit hash that is checked out. Eventually this will be an MRtrix3 tag as we move to more stable versions, but for now I needed various fixes in a separate branch to get things going fully.
Regarding version numbering: I'm having this BIDS App follow its own version numbering. Updates to it may not track the MRtrix3 versioning very well or at all. Instead I I just have Dockerfile write the MRtrix3 version to a file in root during construction of the container.


Add basic retry policies to zebra-network.

This should be removed when https://github.com/tower-rs/tower/pull/414 lands
but is good enough for our purposes for now.

Closes #244


Consolidate the versions

Generally, it is a bad practice to use different versions of Spark together, therefore I'd suggest to set it to 2.2.2 for now using a Maven property.

@Fokko could you kindly rebase / merge your work on top of master so that we can merge?

Of course @arvindshmicrosoft. Thanks for pinging me!

Sorry one more thing - looks like the merge somehow removed the  property you had added in the previous PR. Could you verify that as well and push up another commit to ensure we keep the  attribute per your previous one?

Whoops, that wasn't my intention. I've restored the provided property.


Save position of the card

How do I get the source and destination that this card in order to save the future?

Just add a callback onEnd: onItemMoved and in the method (onItemMoved in this example) just go through the HTML nodes that have been sortable (they should have anything to identify what they represent, of course - an ID for example). That's the order you can save.

See onStart/onEnd/toArray/sort methods


fixing alert texts on anmeldung.php

I did this directly before using github via ftp:
Please adopt to github repository ..

Ok, then it is probably lost now... I'll check it out
Am 15/12/2015 um 18:42 schrieb multireadsts:

I did this directly before using github via ftp:
Please adopt to github repository ..
—
Reply to this email directly or view it on GitHub
https://github.com/Andreas-Schoenefeldt/viszerale-therapie.at/issues/11.

Ive a local copy to put in my branch if needed


rr.serve should be rr.serve_websocket, rr.connect should be rr.connect_tcp

And similarly, rerun --serve should be rerun --serve-websocket (or something along these lines, you get the idea).
Users get understandably confused by this. They expect a serving process (rr.serve()) to be ready to accept connections from other processes (rr.connect()), except the two things are in reality completely unrelated: one is hosting a websocket server to be polled by the web-viewer, while the other is trying to connect to the TCP sdk comms pipeline.
See e.g. this thread: https://discord.com/channels/1062300748202921994/1295914647165210634

+1, I ran into this confusion myself just yesterday

Yet another thing that would make documenting the app model (#919) easier.

Let's just rename these and keep the old names as deprecated redirects


build.py and build.cmd

build.py not exists.And build.cmd(from skybuild) is not working.
File "..Desktop\sky\shellcode_encoder-master\testival-master\build.cm d", line 27, in <module>     import command_line_options; ImportError: No module named command_line_options
Hard need this project after 7 years, waiting ur respond.

build.cmd can be found here https://code.google.com/archive/p/skybuild/downloads. However I can't find command_line_options module.


Update AWS-IoT Documentation

Change-type: minor
Signed-off-by: Daniel Andrade<EMAIL_ADDRESS>

I just realized the build changed a few sdk files, should that be the case as well? Otherwise, I can remove those changes.

@dansku for one reason or another, the CLI/SDK/supervisor docs are checked in here, but deployed directly from their respective masters. Imho including the changes is fine here since there's no effective change other than keeping our docs repo in sync.

@xginn8 great, then it should be fine ;)


Slow performance

Hi,
I segmented with GUI a 2008x2008 picture with dapi nuclei. (output see below)
First of all is shows (2008, 2008, 3) but is a grayscale image.
I use a 6 core I7-6800 CPU (3.4 GHz), 64GB Memory, GTX 1080 and Use GPU is on. Running Windows 10.
When looking at the GPU usage I see a few seconds of Cuda activity. But the total calculation time is 52 seconds.
I want to analyse 10K pictures (high content/throughput data). What can I do to speed the calculations up.
(So what hardware etc.) and how does the speed of your algorithm compares to Stardist for example (I used Stardist on the same data, and the calculation is done in 5 seconds).
Best, Ron
1 (2008, 2008, 3)
removed all cells
estimated diameter of cells using nuclei model = 37.0 pixels
removed all cells
using model nuclei
processing 1 image(s)
estimated masks for 1 image(s) in 52.57 sec

TOTAL TIME 52.57 sec
1859 cells found with cellpose net in 52.772 sec
plane 0 outlines processed

can you try the latest version of the pipeline? I just ran a 2025 x 2025 image on my Windows laptop (no GPU, not a particularly fast CPU) and the computation time for 4 networks is 41sec. with 1 network it's a 16sec runtime

Hi,
I used the new version (with the GUI) and these are the results (file in attached zip file).
It looks it is faster as the older version. The network over the GPU is very fast!! The calculations of the mask is the slower part. Is there a way to optimize the mask creation?
Best, Ron
test1.zip
--> Without GPU  (4 networks, 1 fast)
CUDA version not installed/working, will use CPU version.
E:/Ron/Anaconda/CellPoseTest/test1.tif
1 (2008, 2008, 3)
removed all cells
removed all cells
cyto
cellpose_residual_on_style_on_concatenation_off
using model cyto
processing 1 image(s)
time spent: running network 249.74s; flow+mask computation 32.14
estimated masks for 1 image(s) in 282.09 sec

TOTAL TIME 282.09 sec
2150 cells found with cellpose net in 282.300 sec
plane 0 outlines processed
removed all cells
using model cyto
processing 1 image(s)
time spent: running network 61.31s; flow+mask computation 32.55
estimated masks for 1 image(s) in 94.13 sec
TOTAL TIME 94.13 sec
2172 cells found with cellpose net in 94.277 sec
plane 0 outlines processed

--> With GPU  (4 networks(with autotune), 1 fast, 4 networks)
** CUDA version installed and working. **
E:/Ron/Anaconda/CellPoseTest/test1.tif
1 (2008, 2008, 3)
removed all cells
removed all cells
cyto
cellpose_residual_on_style_on_concatenation_off
using model cyto
processing 1 image(s)
[09:49:57] c:\jenkins\workspace\mxnet-tag\mxnet\src\operator\nn\cudnn./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
time spent: running network 13.74s; flow+mask computation 31.80
estimated masks for 1 image(s) in 45.74 sec

TOTAL TIME 45.74 sec
2150 cells found with cellpose net in 47.953 sec
plane 0 outlines processed
removed all cells
using model cyto
processing 1 image(s)
time spent: running network 1.17s; flow+mask computation 31.92
estimated masks for 1 image(s) in 33.31 sec
TOTAL TIME 33.31 sec
2172 cells found with cellpose net in 33.468 sec
plane 0 outlines processed
removed all cells
using model cyto
processing 1 image(s)
time spent: running network 4.95s; flow+mask computation 30.74
estimated masks for 1 image(s) in 35.89 sec
TOTAL TIME 35.89 sec
2150 cells found with cellpose net in 36.028 sec
plane 0 outlines processed

You can try turning off the quality control step in the flow+mask computation by setting flow_threshold=0. The QC step throws out masks that produce flows which are substantially different from the network's predicted flows. This mask->flow computation takes some time.


[Event Request] Table 38 "Purchase Line" - OnAfterSetReservationEntry

Please add new event in table 38: OnAfterSetReservationEntry
[IntegrationEvent(false, false)]
local procedure OnAfterSetReservationEntry(var ReservEntry: Record "Reservation Entry"; var PurchaseLine: Record "Purchase Line")
begin
end;

procedure SetReservationEntry(var ReservEntry: Record "Reservation Entry")
begin
    ReservEntry.SetSource(DATABASE::"Purchase Line", "Document Type".AsInteger(), "Document No.", "Line No.", '', 0);
    ReservEntry.SetItemData("No.", Description, "Location Code", "Variant Code", "Qty. per Unit of Measure");
    if Type <> Type::Item then
        ReservEntry."Item No." := '';
    ReservEntry."Expected Receipt Date" := "Expected Receipt Date";
    ReservEntry."Shipment Date" := "Expected Receipt Date";
    ReservEntry."Planning Flexibility" := "Planning Flexibility";
    OnAfterSetReservationEntry(ReservEntry, Rec);
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 44163.


To support the Solidus

Spree was stopped development.
So,I think this plugin is required to support solidus that .

@shogoland Spree is actively maintained and we'll be releasing Spree 3.1 this month.


I want to implement splitting an obj file into multiple obj files

Hi~
I want to implement splitting an obj file into multiple obj files. Can I use this? If you can give me some ideas.
Grateful.

You can split obj file after reading .obj according to various criteria. For example

per object
per material
for each specific number of vertices(e.g. 65536)

PR of example program is always welcome!

Is there any relevant code to refer to? It is time-consuming to encounter this problem. I am also learning about obj related knowledge at the same time. If I can get the code or information I can quote, I can speed up my speed. Your help makes me very happy, thank you again.

Please study wavefront .obj format and C++ firstly.


SSO fails with "Failed to find sso_session"

Describe the bug
When trying to use SSO with a .NET 8 app, it fails with Amazon.Runtime.AmazonClientException: Invalid Configuration.  Failed to find sso_session [Acme Dev] even though aws sso login was done before, and SSO seemingly worked fine (e.g., I can do aws s3 ls --profile acme-dev and it works).
Expected Behavior
.NET 8 app is able to auth with AWS using SSO.
Current Behavior
Fails with an exception
Amazon.Runtime.AmazonClientException: Invalid Configuration.  Failed to find sso_session [Acme Dev]
Reproduction Steps
1. Configure SSO
❯ aws configure sso
SSO session name (Recommended): Acme Dev
SSO start URL [None]: https://*********.awsapps.com/start/#
SSO region [None]: **-****-1
SSO registration scopes [sso:account:access]:
Attempting to automatically open the SSO authorization page in your default browser.
If the browser does not open or you wish to use a different device to authorize this request, open the following URL:

https://device.sso.**-****-1.amazonaws.com/

Then enter the code:

****-****
There are 3 AWS accounts available to you.
Using the account ID **************
The only role available to you is: dev-admin
Using the role name "dev-admin"
CLI default client Region [None]:
CLI default output format [None]:
CLI profile name [dev-admin-************]: acme-dev

To use this profile, specify the profile name using --profile, as shown:

aws s3 ls --profile acme-dev

Checking that it works:
❯ aws s3 ls --profile acme-dev
...
here it outputs an actual list of my buckets
...

2. Check the Profile File
❯ cat ~/.aws/config
[profile acme-dev]
sso_session = Acme Dev
sso_account_id = ***********
sso_role_name = dev-admin
[sso-session 'Acme Dev']
sso_start_url = https://*********.awsapps.com/start/#
sso_region = **-****-1
sso_registration_scopes = sso:account:access

3. Use SSO in .NET App
First, set the environment variable: AWS_PROFILE=acme-dev
Then in my code:
namespace Example;
public static class Settings {
  static Settings() {
    var region = RegionEndpoint.GetBySystemName("**-****-1"); // redacted
    var s3Client = new AmazonS3Client(region);
  }
}

Launching the program fails on new AmazonS3Client(region); with the following stack trace:
Unhandled exception. System.TypeInitializationException: The type initializer for 'Example.Settings' threw an exception.
 ---> System.TypeInitializationException: The type initializer for 'Amazon.Runtime.Internal.FallbackInternalConfigurationFactory' threw an exception.
 ---> Amazon.Runtime.AmazonClientException: Invalid Configuration.  Failed to find sso_session [Acme Dev]
   at Amazon.Runtime.CredentialManagement.SharedCredentialsFile.TryGetProfile(String profileName, Boolean doRefresh, Boolean isSsoSession, Boolean isServicesSection, CredentialProfile& profile)
   at Amazon.Runtime.CredentialManagement.SharedCredentialsFile.TryGetProfile(String profileName, CredentialProfile& profile)
   at Amazon.Runtime.CredentialManagement.CredentialProfileStoreChain.TryGetProfile(String profileName, CredentialProfile& profile)
   at Amazon.Runtime.Internal.ProfileInternalConfiguration.Setup(ICredentialProfileSource source, String profileName)
   at Amazon.Runtime.Internal.ProfileInternalConfiguration..ctor(ICredentialProfileSource source)
   at Amazon.Runtime.Internal.FallbackInternalConfigurationFactory.Reset()
   at Amazon.Runtime.Internal.FallbackInternalConfigurationFactory..cctor()
   --- End of inner exception stack trace ---
   at Amazon.Runtime.Internal.FallbackInternalConfigurationFactory.get_IgnoreConfiguredEndpointUrls()
   at Amazon.Runtime.ClientConfig.get_IgnoreConfiguredEndpointUrls()
   at Amazon.Runtime.ClientConfig.get_ServiceURL()
   at Amazon.S3.AmazonS3Config.Validate()
   at Amazon.Runtime.AmazonServiceClient..ctor(AWSCredentials credentials, ClientConfig config)
   at Amazon.S3.AmazonS3Client..ctor(RegionEndpoint region)
   at Example.Settings..cctor() in /path/to/app/src/Settings.cs:line 31
   --- End of inner exception stack trace ---

AWS .NET SDK and/or Package version used
AWSSDK.CORE – 3.7.304.30
AWSSDK.S3 – 3.7.310.7
AWSSDK.SecretsManager.Caching – 1.0.6
AWSSDK.SSO – 3.7.300.119
AWSSDK.SSOIDC – 3.7.302.30
Targeted .NET Platform
.NET 8
Operating System and version
OSX Sonoma 14.5

The error message could be better, but can you check if using a session name without spaces (i.e. acme-dev) works? Even though the CLI supports this use case, .NET (and other SDKs) are following this specification (https://docs.aws.amazon.com/sdkref/latest/guide/file-format.html):

A section definition is a line that applies a name to a collection of settings. Section definition lines start and end with square brackets ([ ]). Inside the brackets, there is a section type identifier and a custom name for the section. You can use letters, numbers, hyphens (-), and underscores (_), but no spaces.

Here's a similar report for the Rust SDK (that one was related to the profile name, but same logic applies to the SSO section): https://github.com/awslabs/aws-sdk-rust/issues/1097

Indeed, that worked, thank you @dscpinheiro!
I feel that this discrepancy is quite confusing though.

Agree. In hindsight the CLI shouldn't have allowed this format, but at this point it'd be a breaking change for them to fix it.

Relatedly, I had this happen with the Go SDK today and removing the space fixed it for me too.
import "github.com/aws/aws-sdk-go/aws/session"

sess, err := session.NewSessionWithOptions(s3Options)
if err != nil {
  return nil, err
}

Returns this error:
failed to find SSO session section, Acme Dev

Using acme-dev instead with aws configure sso solved the issue.


Improve target understanding

This adds a dependency on https://docs.rs/target-lexicon and explores which places we could start using it (for cross-compilation, definitely)

Closing in favor of #1470


Update docs to clarify that events must be registered on both the client and server

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a6609a5) 83.37% compared to head (10a805a) 83.37%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #162   +/-   ##
=======================================
  Coverage   83.37%   83.37%
=======================================
  Files          20       20
  Lines        1287     1287
=======================================
  Hits         1073     1073
  Misses        214      214

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


@conda-forge-admin, please add user @cnweaver

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @cnweaver in conda-forge/hop-client-feedstock#10.


[Feature request] Use portal to render results

I have a particular case where I need to render the autosuggest component inside a component which has overflow: hidden on it, this makes only a part of the results container visible.

If portals were used then there can be more flexibility on where the results container should be rendered in the DOM.

@DarkSouL11 I agree this could be nice. I tried to implement it at one point without vue-portal as a dependency, but didn't seem to work like I wanted. some of the features such as ARIA or highlight classes depend on the results being selectable as a child of the auto-suggest element e.g. https://github.com/darrenjennings/vue-autosuggest/blob/242dd4dee084d5f6133c09b88da7f9e87f7502be/src/Autosuggest.vue#L508
Since it's not trivial to implement wouldn't mind help investigating a solution or if you know of other components with prior art we could borrow.

@darrenjennings One solution I can think(doesn't use portals at all) of is using position: fixed on results container and calculating its left and top offsets manually.

Closing since, for now, it is acceptable to render results in the same html location as the <input /> and it follows from w3c examples: https://w3c.github.io/aria-practices/examples/combobox/aria1.1pattern/listbox-combo.html


Support node.js contexts with UserSession

Related to #500, also a comment by @origin in the v19 PR.
Now that we have the UserSession stuff almost merged with support for different storage strategies, we should build a strategy for using blockstack.js with node.js. This shouldn't be too hard. When defining the UserSession, you should be able to pass an appPrivateKey during instantiation. This can be done depending on the user's implementation, but most users will likely use an ENV variable.
There is also some code in authApp.js that uses window to do protocol handling stuff. This should be wrapped in a check for the presence of window. Right now, even importing that file in node.js will cause an error.

Is this something that can be worked on in parallel to #542?


fix: replace ReadableNativeMap with MapBuffer to run on rn 0.75

Fixing android issue that occured in RN 0.75
From my understanding with the latest release of react native ReadableNativeMap was replaced with  MapBuffer I used the current implementation of textManager to update to the new type, I did a patch for this fix on my own project to test the android build and things worked

Thanks! Released 🚀

Thanks! Released 🚀

Any time 🙏


Show and ShowT

There is now separate Show and ShowT traits. The ShowT is the type class trait. Their methods will be reformulated. str and strT will be parameterless properties. There will probably be just one other show / showT method on Show and ShowT, with multiple parameters. The other methods of convenience will all be moved to the ShowTExtensions class.

This is mostly implemented and will be completed with #141.

This is mostly implemented and will be completed with #141.


Vulkan randomly crashing with VK_ERROR_DEVICE_LOST error in editor on low end hardware

Godot version
v4.1.2.stable.mono.official [399c9dc39]
System information
Godot v4.1.2.stable.mono - Windows 10.0.22622 - Vulkan (Forward+) - integrated Intel(R) Iris(R) Plus Graphics (Intel Corporation; <IP_ADDRESS>5) - Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 Threads)
Issue description
When rotating or moving the in-editor camera, Godot will randomly freeze before crashing with the message ERROR: Vulkan: Cannot submit graphics queue. Error code: VK_ERROR_DEVICE_LOST at: (drivers/vulkan/vulkan_context.cpp:2360).
The graphics settings  anti_aliasing/quality/msaa_3d=2 anti_aliasing/quality/screen_space_aa=1 caused Vulkan to crash instantly on startup, but after disabling them the engine crashes randomly in the editor.
When I run the same project on my PC with a Nvidia 4070TI, there is no crashing and Vulkan runs fine.
Steps to reproduce

Run forward-plus vulkan on a system with a low end GPU (I have been using Intel Integrated Iris Plus Graphics).
Either enable 3D MSAA or just rotate and pan the camera.
Godot should freeze and crash.

Minimal reproduction project
N/A, Godot crashes even when opening a freshly made forward+ project.

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/71929.


🐛 Library doesn't work clientside

Thanks for the amazing work.
I noticed that the library doesn't work on any browser. It results in the error:
Refused to set unsafe header "user-agent"

Access to XMLHttpRequest at 'https://github.com/a-tokyo' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Your schema is amazing and i'd love to use this, however I will have to use https://github.com/itaditya/simple-unfurl for now as it works clientside as well

Oh interesting. I get "ReferenceError: Cannot access 'cross_fetch_1' before initialization". I'll see what I can do.

My workaround (I used this answer here to create a helper app that handles cross origin: https://stackoverflow.com/questions/43871637/no-access-control-allow-origin-header-is-present-on-the-requested-resource-whe):
    let raw;
    try {
      raw = await unfurled(url);
    } catch (err) {
      /** CORS failed to fetch? retry with cors proxy
       * this happens when for example localhost tries to unfurl dev-remote url due to different hosts
       * https://stackoverflow.com/questions/43871637/no-access-control-allow-origin-header-is-present-on-the-requested-resource-whe
       */
      try {
        raw = await unfurled(`${CORS_PROXY_URL}/${url}`);
      } catch (err2) {
        // handled - proceed and attempt to parse other data - eg: plural
      }
      // handled - proceed and attempt to parse other data - eg: plural
    }

Oh interesting. I get "ReferenceError: Cannot access 'cross_fetch_1' before initialization". I'll see what I can do.

I did look into this just now and looked into building for the browser in webpack. I only ran into this because i'm was testing the library directly in codepen with unpkg. I'm guessing you're using a bundler, so you didn't run into this.
But due to the restrictive nature of CORS in the browser, i don't think there is any merit in keeping those changes for a browser build.
Whilst your CORs proxy workaround works, I don't think it's the right approach. This library is approximately 1MB uncompressed (and 500kb compressed with webpack). So it'd add significant bloat and then when calling unfurl it'll block the event loop.
I will make it clearer in the readme that this is a server-side library and not supported for use client-side.

Do you not get the same CORS error with itaditya/simple-unfurl ?

Yes I get it :/ so I added the proxy CORS thing to avoid these issues.
However I think I will just add a backend endpoint today that handles this. I am just worried the library would have the same errors in the backend as well @jacktuck

You shouldn't have the same issue as you'd have control of the endpoint - meaning you can add CORS response headers - either wildcard or specific to your domain(s).


#515 [HxChipList] Support for Reset button (Remove all)

#515

@crdo I think the Reset button should not be displayed when there are no chips.
I will take care of that (if it is already not there "by design").


Updating of old URL (Pango Markup formatting page)

Overview: What does this pull request change?

Motivation and Explanation: Why and how do your changes improve the library?

Links to added or changed documentation pages

Further Information and Comments

The old URL https://developer.gnome.org/pango/stable/pango-Markup.html redirects to https://docs.gtk.org/Pango/ which is a generic page, not specific to the Pango Markup formatting. I replace it with the new address of the documentation:  https://docs.gtk.org/Pango/pango_markup.html

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

Oops... sorry for the mistake. It's because when I'm in the page https://docs.manim.community/en/stable/reference/manim.mobject.text.text_mobject.MarkupText.html, I have clicked on the Edit button on the top right:

and this go to an 404 error page : https://github.com/ManimCommunity/manim/edit/da3e99597d627b3e2e339dad977f8ef21d9b640d/docs/source/reference/manim.mobject.text.text_mobject.MarkupText.rst
So I searched the source on Github and found the .pod page (don't know what this extension file is).
Il will close this pull request after my new attempt with the right file.


Error on docker image

Hi, i'm trying to run your last docker image but i have got an issue and i don't know why :
standard_init_linux.go:211: exec user process caused "exec format error"
The script stop with this error. Do you know why ?

The image is compatible only with x86_64 CPUs.
Looks like you are trying to run it on ARM cpu?

That's right !
Sorry, i did not notice it was not compatible with ARM.
Is there any solution about this ?
Regards

Closing this issue.  Please re-open if needed.


Voting app - build error

Loading Application Details...
Evaluating project failed with exit code 1
Drats! 'build' failed:
Evaluated project metadata file could not be found for service results
I run tye build . in folder

Hi @andreatosato,
The error you are describing is usually caused by stray obj and binary files.
Would you mind cleaning out the obj and the bin folder and then trying out the tye build command again?


feat(Filtering): Add Best Practice category

Implements https://issues.redhat.com/browse/OCPADVISOR-111.
This adds one new category to the Category filter: users are now able to filter rules by the Best Practice category.
How to test
Go to /openshift/insights/advisor/recommendations, check that you are able to filter rules by Best Practice category. Do the same on any cluster details page. There are currently no recommendations that have this category, so you are supposed to see an empty list.
Screenshots
/recommendations:
https://github.com/RedHatInsights/ocp-advisor-frontend/assets/31385370/8d8ef14d-929e-4757-b9f5-bcae73536765
/clusters/%id:
https://github.com/RedHatInsights/ocp-advisor-frontend/assets/31385370/afdec0dd-f42a-4417-819e-c792f0c89ecb

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


Hello, can this problem be fixed? Try to show that the repair failed many times. Is it thunderbolt brick?

HaC-Mini-2.3.3
How do you do? Can you help me with the repair, thank you

![Uploading BADA68FA-502F-464A-8C0B-654FFAA818A5.png…]()

You need to patch AppleHPMDevice@70. it should be selected automatically when you launch the patcher.

You need to patch AppleHPMDevice@70. it should be selected automatically when you launch the patcher.
applehpmdevice @ 70, indicating that the repair failed

@osy86 70，76，4E，Repair failure

@osy86 HaC-Mini-2.2 Fixed successfully. Thunderbolt disappeared after upgrading HaC-Mini 2.3.3. Go back to HaC-Mini 2.2, still can't find thunderbolt

Tool not compatible with 2.2. You must upgrade to 2.3 first then use the tool. Select @70 and get a dump using File -> Dump.

Tool not compatible with 2.2. You must upgrade to 2.3 first then use the tool. Select @70 and get a dump using File -> Dump.

Can it be repaired now

@osy86 Can it be repaired now

@osy86 File -> Dump
Untitled.zip

@osy86 File -> Dump
Untitled.zip

windows No thunderbolt display

Please make sure you are dumping AppleHPMDevice@70. I see the wrong SPI.

After some direct messages, the device has been returned the device to Intel after some improper bios external flashing. This issue should be closed.

I see


Minor update HV_SOCK_Basic Test_Type since local have different TC_Co…

…vered value
Locally have random test case ID (without 1,2 at the end of name), cannot use TC_COVERED to select test part, so add TEST_TYPE here.

Thank you for the changes!
We were looking to actually not add an additional param just for this, but if you're using different test cases IDs then it makes sense.


Make indexstore.h importable by Swift.

This change removes some C++-specific things that prevented Swift from being able to import this header (when provided with a module map).

Ah, please get this committed at llvm.org first! Then we can cherry-pick it into either a release branch or just into stable for holding. For more info see swift/docs/Branches.md.

@jrose-apple Thanks for pinging this! I originally put this PR here because the indexstore API hadn't yet been accepted into mainline clang (https://reviews.llvm.org/D39050); unfortunately, even though it's been merged now, it's in a completely different form that's not compatible with this change so I'll abandon it and revisit what I was working on.


TTML and CEA-608 captions conflicting with each other when present in text tracks list

Have you read the FAQ and checked for duplicate open issues?
Yes

Possibly loosely related:

https://github.com/google/shaka-player/issues/3186

What version of Shaka Player are you using?

v2.5.20 but can repro on v3.0.8

Can you reproduce the issue with our latest release version?

Yes, can repro ono v3.0.8

Can you reproduce the issue with the latest code from master?

Have not tried, but can repro on v3.0.8 shaka demo player.

Are you using the demo app or your own custom app?

Custom app.

If custom app, can you reproduce the issue using our demo app?

Yes can repro on the demo app

What browser and OS are you using?

Chrome Version v89.0.4389.82 (Official Build) (x86_64)
MacOS v10.15.7

For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?
Please let us know if and when you want to reproduce and we will provide you with a way to access our video streams.
What did you do?

Using shaka demo player v3.0.8

Play a multi-period static dash asset that contains ttml and cea-608 text tracks.
Seek out of the first period
Toggle captions ON (ttml captions are selected in this case)

Note: captions for ttml look to be from the first period although playing video/audio from later period

Select cea-608 text track (now cea-608 text track is playing and all looks to be ok)

const player = document.getElementById('video').ui.getControls().getPlayer();
const trackToSelect = player.getTextTracks().find((track) => track.mimeType === 'application/cea-608');

player.selectTextTrack(trackToSelect);

Toggle captions OFF then ON again
I believe to be seeing both ttml and cea-608 captions although only one is active.

ttml captions show immediately (and are playing text from the first period)
cea-608 captions show properly but won't appear until already buffered content has been played.

What did you expect to happen?

We would expect only the active text track to be displaying and to be in sync with the audio.

What actually happened?

Note the above scenario may seem odd as this is how I was able to repo on the shaka demo player.

The above steps will get the player in a state in which there are multiple text tracks being displayed. Although only one is declared active when checking player.getTextTracks().

For our custom application, we are selecting cea-608 text tracks off the bat as we are not looking to display the ttml track.
When we toggle captions OFF then ON we end up in the same state as above.

player.setTextTrackVisibility(val);

We see the ttml captions from the first period immediately (not active track)
We will see the cea-608 text track (active text track) but does not show until we've made it through already buffered content
We have implemented a workaround to parse out adaptation sets with mime type application/ttml+xml and this looks to fix both the duplicate active text track behavior as well as the delay in viewing the cea-608 text tracks. Although not ideal.
We are looking to raise this bug in the hopes to help resolve the issue at its source or highlight any improper usage we may be doing on our end! Thanks!

You can send the reproduction issue (URIs and such) to<EMAIL_ADDRESS>and I'll look into the issue.

Sent over the information on how to access the application and how to reproduce the described issue. Please reach out if can assist in any way! Thanks for taking a look

I tried to reproduce this for a while, but failed.
For whatever reason, I can't see your embedded captions at all. Even if I specifically play an embedded track (by picking the spanish captions, for example, which only have an embedded version), the text displayer has no cues. I've tried in our demo player using both v3.0.X and v3.1.X, same thing in both. I don't know how to change the language in your application, but I've been unable to reproduce the error there too.
So for all I know, the player might be loading cues from both caption tracks at once, and I just can't tell because the embedded captions aren't being loaded properly to begin with. It's hard to say.
I'm not sure why yet, honestly. mux.js parsing captions shouldn't be platform-dependent. And even if it was, I am also testing using Chrome on Mac.

@theodab Thank you for taking a look! Apologies it didn't go to plan, let me create some screen recordings and improve the repo steps. I'll pass the recordings along via the email provided.

Alright. With the new repro steps and video you produced, I was able to reproduce this issue. Thanks for your patience!
I'll look into why this is happening. It does feel like a bug to me, you're right, so for now I'm marking it as a bug.

With that fix, the embedded and non-embedded captions should no longer be able to play at the same time. I'm still looking into why your non-embedded captions are so out of sync, though. Sorry for the delays!

So, your content is a multi-period manifest. It has a single master captions file that contains captions for the entire run-length, which is inserted separately into each non-ad period.
The content is super offset because if we are in (say) period 17 and see a captions file listed as an AdaptationSet on that period, we assume that the captions file is meant to start at the start time of period 17, so we offset everything by that amount of time. Thus, if you seek to right after an ad break ends, the captions "start over" from that point, so to speak.
According to the DASH IOP, section 6.4.5. Guidelines for side-loaded TTML and WebVTT files:

Such external files are assumed to have a timeline aligned with the Period, so that TTML time
00:00:00.000 corresponds to the start of the Period. The presentation time offset is expected to be
not presented, and if present, expected to be ignored by the DASH client.

So it sounds our current behavior is to-spec, and not a bug. With something as complex as the DASH spec, it always helps to check! In that case, then, each period should have its own caption file, that contains just the captions for that period, and is timed relative to the period rather than relative to the entire presentation.
I'm going to close this issue for now. If you run into any further caption sync/overlapping problems, feel free to re-open this! I didn't have a good way of testing the segmented captions solution, so I'm only mostly sure it will fix things.


freetype: 2.7.1 -> 2.8

Motivation for this change

freetype 2.7.1 -> 2.8. It includes almost all upstream patches which were cherry-picked to 2.7.1. 700 lines gone.
patch for useEncumberedCode required when the option is set to false, not to true as before.
added useSubpixelHinting to fix https://github.com/NixOS/nixpkgs/pull/26814

Things done
Please check what applies. Note that these are not hard requirements but mereley serve as information for reviewers.

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

there are some weird visual issues :(
I undid to 2.7.1


Fix edit texts

Summary
This PR fixes a bug that comes about when you use React Native and some versions of AppCompat (notably 1.4.1, not sure if this is present in the most recent versions) Specifically, when ReactEditText calls super, when the edit text is being created, the constructor in AppCompatEditText will end up calling setInputType(), where ReactEditText tries to do a manipulation to an internal Key listener. The problem is that the key listener is not initialized until later in ReactEditText's constructor.
This MR fixes this by making the mKeyListener not final and setting it surrounded by null checks.
This branch has so many changes because it enables the branch (or any branch it is merged to) to be used as a repository via npm by running npm install --save github:mavenclinic/react-native#fix-edit-texts
Changelog
Make React Native 0.63.2 compatible with AppCompat Emoji support from AppCompat 1.4.1
Test Plan
Open a screen that has a text input of some kind. The app should not crash
Screenshots of the changed code:

Nice catch! That seems like a poor practice in AppCompatEditText, to call a non-final method (setInputType()) in the constructor.

Thanks for the approval!


[Problem]: Container working but unhealthy

Description / Beschreibung
In my portainer environment i observed, that my iobroker installatin was suddenly unhealthy.
I tried to setup a fresh container with iobroker only and also this container changes from healthy to unhealthy immediately after installation.
in the logs (container and iobroker) i can not detect any problems. the iobroker is running as expected. but has the state unhealthy.
the only thing i can see is the following output in portainer.

is this a problem in the container, or do i have a problem on my system?
edit:
i checked within the container console... seems for me to be an issue in the container...

br peter
Image version
latest-v9
Docker logs / Docker Protokoll
--------------------------------------------------------------------------------

-------------------------     2023-12-28 11:39:18      -------------------------

--------------------------------------------------------------------------------

-----                                                                      -----

----- ██╗  ██████╗  ██████╗  ██████╗   ██████╗  ██╗  ██╗ ███████╗ ██████╗  -----

----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ -----

----- ██║ ██║   ██║ ██████╔╝ ██████╔╝ ██║   ██║ █████╔╝  █████╗   ██████╔╝ -----

----- ██║ ██║   ██║ ██╔══██╗ ██╔══██╗ ██║   ██║ ██╔═██╗  ██╔══╝   ██╔══██╗ -----

----- ██║ ╚██████╔╝ ██████╔╝ ██║  ██║ ╚██████╔╝ ██║  ██╗ ███████╗ ██║  ██║ -----

----- ╚═╝  ╚═════╝  ╚═════╝  ╚═╝  ╚═╝  ╚═════╝  ╚═╝  ╚═╝ ╚══════╝ ╚═╝  ╚═╝ -----

-----                                                                      -----

-----              Welcome to your ioBroker Docker container!              -----

-----                    Startupscript is now running!                     -----

-----                          Please be patient!                          -----

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

-----                          System Information                          -----

-----                    arch:                x86_64                       -----

-----                    hostname:            IOBroker                     -----

-----                                                                      -----

-----                          Version Information                         -----

-----                    image:               v9.0.1                       -----

-----                    build:               2023-10-26T23:44:46+00:00    -----

-----                    node:                v18.18.2                     -----

-----                    npm:                 9.8.1                        -----

-----                                                                      -----

-----                        Environment Variables                         -----

-----                    SETGID:              1000                         -----

-----                    SETUID:              1000                         -----

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

-----                   Step 1 of 5: Preparing container                   -----

--------------------------------------------------------------------------------

Updating Linux packages on first run... Done.

Registering maintenance script as command... Done.

--------------------------------------------------------------------------------

-----             Step 2 of 5: Detecting ioBroker installation             -----

--------------------------------------------------------------------------------

Existing installation of ioBroker detected in "/opt/iobroker".

--------------------------------------------------------------------------------

-----             Step 3 of 5: Checking ioBroker installation              -----

--------------------------------------------------------------------------------

(Re)setting permissions (This might take a while! Please be patient!)... Done.

Checking Database connection... Done.

Hostname in ioBroker matches the hostname of this container.

No action required.

--------------------------------------------------------------------------------

-----                Step 4 of 5: Applying special settings                -----

--------------------------------------------------------------------------------

Some adapters have special requirements/ settings which can be activated by the use of environment variables.

For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).

--------------------------------------------------------------------------------

-----                    Step 5 of 5: ioBroker startup                     -----

--------------------------------------------------------------------------------

Starting ioBroker...

##### #### ### ## # iobroker.js-controller log output # ## ### #### #####

host.IOBroker check instance "system.adapter.admin.0" for host "IOBroker"

host.IOBroker check instance "system.adapter.discovery.0" for host "IOBroker"

host.IOBroker check instance "system.adapter.backitup.0" for host "IOBroker"

Send diag info: {"uuid":"80ba583f-babc-4bb9-843d-750c66a4e62d","language":"de","country":"","hosts":[{"version":"5.0.17","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.18.2","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.12.0","platform":"Javascript/Node.js"},"discovery":{"version":"4.2.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.9.8","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":3,"compactMode":false,"noCompactInstances":0,"model":"Intel(R) Celeron(R) CPU  J1900  @ 1.99GHz","cpus":4,"mem":8023482368,"ostype":"Linux","city":""}

i deleted the image in portainer and explicitely loaded 9.0.1. with this image the container stayed healthy...
don't know exactly whats the matter here...
i think this can be closed


Ease local development by adding make targets

Also use them in Jenkinsfile for moar behavior consistency.
One can do for instance:

make # will build and test everything locally
make test-debian
etc.

(I came to do this locally to help me move forward JENKINS-51985)

I think I'm going to move forward and merge soon here, as I've already some local code using this and adding a -jdk11 build.
But please anyone coming possibly after this is merged, feel free to still review and I'll happily address comments in followups as needed.
Thanks!

plain reproducible commands

Definitely my goal, glad you like it :).

plain reproducible commands

Definitely my goal, glad you like it :).

My favourite pipeline is a Jenkinsfile.sh !

@ndeloof somewhat yeah, though I like the fact that in the actual Jenkins Pipeline you can split steps so that it's also a bit more steps by steps and make it quicker, when developing, to grasp at what point of your build process things went bad.
So here, I havde make all for local overall testing if really I want to test everything (and generally go take a coffee), or if I want to use more focused targets like make test-slim when working on a specific image or so.