Deny relaying from certain accounts

Some pædofiles have been pimping lolitas on twister for some time now.  And while I strongly believe in free speech and do not wish to support censoring, I'd like to be able to tell my twister node(s) not to relay any data from certain accounts.  Would that be possible?

I'm getting tired of saying my .0002BTC worth every time the subject of "let's censor just a wee tiny lil bit. only there real nasty stuff".

Our duty is to be censorship proof. This means we relay everyfokingthing!!!!!1
Even child porn.
Especially child porn.
It's forensics damnit.
Sorry for body language. Back from 2 rough months (ask around), and last thing I need is to lose one of the only things I was coming back "home" [to Sparta] for.
@miguelfreitas, please don't let them lobotomize your baby.
Alright. I'm calm now.
Grow a spine already. So far, we're the losing party in this war. We should at least get our goals straight.
OBTW this goes for #269 and whateverfok else I've missed. @miguelfreitas — pretty please post on your blog a statement saying censorship-resillience is not open for debate.
Don't end up like tox. OK. Let's not escalate into gossip, but some of you can feel what I'm talking about [I hope].

xkcd talks about rights

not to listen
not to host/store relay

1 is still relevant (just don't watch child porn [unless youre investigating a case]
2 is something you willingly give up if you accept twister phylosophy [as I understand it]. It doesn't mean I should host child porn in other places, but twister is a treaty where all users relay everything or China and GCHQ will have you for breakfast. Kapish?

@thedod, I totally disagree, but I already said so more than a year ago. I haven't changed opinion.

@kseistrup how can you protect against cartel of judges forcing all users to delete a twist?
In my scenario, it's just like a judge telling me to ignore gravity.
Can't is a powerful word.
What's your trick against serial child killer Carmen Ortiz and her ilk?

There will always be users who want to relay everything. Let them relay it.

not open for debate

heh, is it your position for free speech?
judge and his beloved friends with guns can force you to delete your twister. they can beat you until you forget the word twister itself. they can force you to not do what you want in twisterverse already.
seriously, I believe it will come one day, fork or not.

@thedod I doubt, if you correctly use the term censorship! If somebody is in a position of power, he can enforce censure. But in case of Twister, even a judge couldn't prevent other nodes from relaying stuff. If we had such a non-relaying feature, the result would always be one of a swarm and not of somebody with power to enforce his will on others.
BTW1. German Nazis came to power in a total legal way, exploiting possibilities of freedom, they were not willing to grant others.
BTW2. You can turn every principle into it's opposite by strictly applying it's rules.

I suggest a compromise:
an I relay everything option (maybe even fork, so that you can't hack/legally-forcce one into the other), and the ones running ``no-censorship-on-my-watch` branch look different on all clients. (like the blue "verified" checkmark.
I want the judge to quickly understand that alice can't delete a twist [even though bob could]. See that "no censorship logo? Sir? I'm terribly sorry. Software [Hopefully math] wouldn't let me do that.
No idea how to lock down "fanatics" so that you can't switch it.
Maybe best is if I start a different blockchain (maybe i2p only) and start a splinter group.
Who's with me? Jboss? ;)

@RealVegOs:

BTW1. German Nazis came to power in a total legal way, exploiting possibilities of freedom, they were not willing to grant others.
That's exactly it. If the system allows control over who gets which rights, you get nazis/gchq/syria/whatever

BTW2. You can turn every principle into it's opposite by strictly applying it's rules.
I'm not here to mince words. I still burp adrenaline. No time for mind games. I'm as practical as a molotov coktail at the moment ;)

Don't shit on the most effective thing to come out of the post-snowden #ybti movement (most effective should have been tox never mind the gossip, we haven't got assets to lose, and we're losing twister to those perverts.
I could scream, but I'll stay normative until we sort this out. a man zgadadoo and all that.

Maybe best is if I[/we?] start a different blockchain (maybe i2p only) as a "splinter group".

come on! stay here. don't wanna miss you.
btw think about deep packet inspection tools on net providers side. gov can force them to drop any Alice torrents. I'd like to see some i2p flavour in twister and 'retwist anonymously' function.

come on! stay here. don't wanna miss you.
I can stay here just like I stay at twitter (and those naaiers have share holders).
I trust you to be zef enough and join us on i2p-cureses-no-js venture. Bring friends (especially the ones too nasty for twister). a few months from now - i2p becomes public enemy #1 with 10 times more nodes.
At the moment, I got other wars. DM if interested in gossip ;)

Adding censors to an censor resistant network is like adding a bomb to a car for anti theft purposes. it's not just a bad idea from a moral level but from a technical one too.

:hand: I knew I could count on you,
You're a rare Van Zandt in a desert of paul simons.
We ain't gonna play sun city 'cause we've seen this movie already.
https://www.youtube.com/watch?v=TlMdYpnVOGQ

Again, I reject the term censure and I also will not grant you the right, to decide something for me, that could be everybody's personal decision.  Please read this thread from the start and try to understand what we are talking about.

I am here because of the renewed interest and outrage shown by certain individuals on Twister. First they started saying abusive things to users, telling them to "fuck off" etc. Then they revived this feature request targeting the same opponents. I urge everyone to take this as a political step, not merely as a technical issue. This renewed interest has something to do with certain political tensions between certain groups on Twister. One section wants to silence another section because of their political views. If we take a decision to implement censorship of some sort at this point, it will provide precedence for further (politically motivated) censorship in the future.

You cannot invent censorship on this network without implementing fundamental changes to how Twister is made. In other words you have to turn in into something else.

If someone wants to implement such things, I suggest forking Twister and creating your own network that allows censorship (Twister2 is a bad name, but you get my point. Come up with a good name)

If I do not follow or unfollow somebody, it's censorship too? Alas others can bring that back to my timeline by retwisting. So we talking about spam. But according to some here, I have to endure it.

Following and Unfollwing options are already there. You can simply unfollow people you don't like. But you will still see posts from those already-unfollowed people if other users RT their posts. RTs are not necessarily spam. RTs are part of a social network or a microblogging platform. This is how you get to spread things you find interesting. This is one of the ways you find more people to follow too. Calling it spam is not the right choice of words.
But still, if you see posts from people you don't want to see or hear fro, this is an issue that needs to be addressed. There seem to be two possible ways to resolve this on Twister:
(1) Adding an option to block a user. This will stop showing their posts, directly or indirectly through other people's RTs. If user X blocks user Y, user X will no longer see posts from user Y. But your node will not ban this user's node. Instead it will continue to be a full part of the network, it will continue to "host" and relay posts from the whole network including the notices from the users you hate.
(2) Implementing a way to relay selectively. This will give individual nodes to ban certain nodes and stop relaying their data entirely. This is a fundamental change to how Twister operates. This can be used to silence people who express ideas that are not widely held or approved. It will diminish the entire network. This is dangerous.
A certain influential user on Twister ( @vegos ) is already campaigning for the option (2) with the aim of preventing users who express a certain set of political views and certain interpretation of history from using Twister. If implemented, the same method will be used against many more schools of thoughts. Twister will no longer be able to circumvent censorship.
P.S. Please pardon me if I misused the tech jargon. But I believe I still managed to convey my point.

If I would be forced by the CIA to decide between this feature (not relaying) and freedom, I'd tend more to freedom of speech.
The main page of twister (1) tells, I think, the direction of twister (what it should be, or what it should not be):
"... no one can censor you. No one can remove your posts. Your account cannot be blocked."
(1) http://twister.net.co

@thedod :
"@miguelfreitas — pretty please post on your blog a statement saying censorship-resillience is not open for debate."
no need to wait for that, we could also make a user manifesto for twister + let willing users edit-"sign" via github

@Erkan-Yilmaz "no need to wait for that, we could also make a user manifesto for twister + let willing users edit-"sign""
+1
Excellent idea.

@lohang

(2) Implementing a way to relay selectively.

As you and others wrote, this is a horrible idea.
@RealVegOs

Again, I reject the term censure

Unless you want to use your own forked version of English, what you are proposing is censorship. Be honest with yourself and embrace that you want to stop relaying content that you disapprove of, making it harder for others to see it.
Otherwise, what is the point in not relaying certain content if you do not, in fact, intend to censor?
If you just want to stop yourself from seeing it that is entirely different and that is not what this ticket is requesting.

Given such a non-relaying feature was technically possible, what would be the effect? Does it affect you, if I - the one you may call censor - do not relay certain content? Really? Does it keep you from seeing it or does it impact you ability to relay it? First NO! Second, if enough others do so too, the stuff may take a little bit longer to be spread to the whole network. But will it be blocked 100%?
I absolutely cannot imagine that, seeing this discussion here!
And what, if a 100% blocking really happens? Then there won't be many to complain about or why did they use the non-relaying feature? Of course all variants not only the extrem ones are imaginable. May be a big number of nodes does not relay and another big group complains, because some stuff has become to slow. Then we have to discuss the content (good idea!) and if enough undo their non-relaying, the problem is solved collectively.
What are you afraid of? A judge or a law will force us all to do so? OK, as soon as we have global laws, we should abandon the non-relaying feature. But I rather think as soon as they understand Twister, they will not force single nodes. They would rather ban Twister completely. The network's hardly controllable peer to peer nature and the persistent nature of posts alone was it worth.
Even if there ever was a 100% blocking of content, I absoutely would not call it what historically and politically is known as censure. There is no instance which arbitrarily has enforced this 100% blocking, it's the result of a consent that happend if it ever ever should happen.
Why do I want this?  You can try to discuss with them or cry "fuck off", like I helplessly did with some unintended adverse effect. At least it taught me, that it's better to delete non targeted Twister handles before doing so! But try to discuss with extremists, I whish you good luck!

  censor
      v 1: forbid the public distribution of ( a movie or a newspaper)
           [syn: {ban}, {censor}]

I cannot put it any more simply than this: I am 100% opposed to censorship.
I believe that even unpopular ideas should be allowed. I don't have to read them. I'm debating the merits of censoring on a platform which proclaims:

Because twister is completely decentralized no one can censor you. No one can remove your posts. Your account cannot be blocked.

What you want is the antithesis of that.
I'm not passing judgment on you for wanting to censor others.  You want to censor and I guess that's OK.
We just completely disagree about free speech being important. I just hope that the developers don't turn their backs on the ideals this project started with.

Because twister is completely decentralized no one can censor you. No one can remove your posts. Your account cannot be blocked.

This will not be touched! Only some accounts will not support your account in the network.
There is no hierarchical structure, nobody is more powerful like you. Nobody has the power to censor the network. Everybody has only power over his node. To forbid something, you must have the power to enforce your ban on everybody. That's censorship.
Another question is, whether an non-relaying feature may be externally exploited by real censors. I'm open for such considerations. But I cannot agree on an orthodox definition of censure, no matter if the non-relaying feature will be implemented or not. I hope at least timeline filtering - what some of you call blocking - will come. Isn't that censure too? What if govs force mandatory blocking lists on us? They could do that with a trojan.

We just completely disagree about free speech being important.

We disagree, but you cannot tell me that free speech is not important for me. I do my best, to help unheard voices and to address ignored topics. Heard of EDCs? I'm not neutral, that's it! I am absolutely biased for peace, freedom, health, equality, culture and for those who lack it. Neutrality is a bad idea in a world where some few aim to own all.

I think the problem with this is that the example that people have been using for selected relaying is fundamentally flawed.
Everyone here keeps comparing it to a conversation, when in fact the Twister network is a lot more complicated by that. In fact, the reason why Twister works so well is because it relays content irrespective of the user.
A better analogy would be to compare this to an ISP who is actively trying to block their users from accessing something like the Tor network because it contains illegal material. It's completely within the right of the ISP to do this, but for me personally, it's not morally acceptable to selectively transmit information in this way, and it also defeats the purpose that Twister was supposed to fill.

Hey people! I'm only reading this thread now and i see it has reached some overly emotional moments but hopefully calmed down to more rational terms already.
I think there are some misunderstandings which helped spread some FUD.
Of course the original statement "Because twister is completely decentralized no one can censor you. No one can remove your posts. Your account cannot be blocked" is not negotiable, but let's think for a moment on what it really means.
When I say "no one" what i meant is that "no organization" or "no entity" can do it, because block/censorship implies forcing a collective behavior on the entire network. twister network is distributed and each node accepts/rejects things based just on simple (technical) rules which have been coded. Banning a specific user or content is not among this rules, that is, the ones which are distributed in the standard twister client.
Now let's consider for a moment that @RealVegOs opens his copy of twister.cpp at function bool acceptSignedPost and writes some code like that:

if (username == "badguy") return false;

Ignoring some possibly unwanted side-effects (triggering libtorrent's peer banning unnecessarily) this would cause @RealVegOs node, and just his node, to refuse receiving/relaying both DHT and swarm posts of user "badguy".
What would be the net effect for "badguy"? None at all.
This probably only gives peace of mind to @RealVegOs to know that he is not relaying badguy's post anymore but twister network keep working as usual.
@RealVegOs has an interesting point: what if badguy is really upsetting people to the point that everybody takes the pain to edit his own twister.cpp file and recompile?
So, what I'm trying to say here is:

No one, not even me, can force what code you decide to run on your computer.
If you want to patch your own twister copy to deny relaying some users, it is not difficult to so. Is this censorship? (imho one has to really stretch the definition to say 'yes')
Turning this local patching into a nicely interface where you can configure your personal blacklist is debatable, but it is not such a big deal. It is a matter of lowering some difficulty bars but it is not fundamentally different of something that is already possible.
Creating a mechanism to share a centralized blacklist (which every node enforces) would be censorship. This is never going to happen.

Btw, on a technical side: acceptSignedPost is not a good place for such check as it has the semantic of a corrupt post (like bad signature).
That is what I've mentioned about triggering libtorrent's peer banning: you don't want to stop connecting to a certain peer just because he tried to relay you a post you don't want to receive (it is not his fault!). He might also relay you "good" people's posts...
A better strategy would be to prevent such torrents from starting locally and also denying at DHT posts checks. Just a little bit more of work but still quite easily doable for C/C++ programmers.

If you want to patch your own twister copy to deny relaying some users, it is not difficult to so. Is this censorship? (imho one has to really stretch the definition to say 'yes')
Turning this local patching into a nicely interface where you can configure your personal blacklist is debatable, but it is not such a big deal. It is a matter of lowering some difficulty bars but it is not fundamentally different of something that is already possible.

all that anybody need to know about this issue.

I agree that we should keep the conversation about infrastructure. The political discussion over at the related google thread (google groups? really?) is circling the fundamental issue that any decentralized service has to face or condemn itself to failure.
Recall in the USA the 'net neutrality' debate recently caused somewhere in the range of hundreds of millions of USD to move around, and is still being litigated between government and telecom infrastructure corporations. That debate is a macrocosm of what is being discussed here: the notion of privileging certain services over others at an infrastructure level. I don't think that the arguments thrown around at the time, that an anti-neutral net literally threatens the future of the Internet, are hyperbolic in the slightest. It's about the eventual result--the life or death of the structure.
If a centralized, immobile network maintained by a cohort of well-funded oligarchic actors including nation-states experiences this much sturm und drang over something as tame as the speed at which Netflix episodes can reach your TV, I think we ought to take the idea of 'neutral infrastructure', and the slippery slopes which lead away from it, seriously. Not even the million-horsepower worldwide Internet can live with systematic privileging of traffic (QoS aside)--do you honestly think that a (currently) tiny service like Twister will be more than a momentary blip in history if it allows anti-neutral traffic privileging to grow without bound?
The Four Horsemen of the Infocalypse definitely use roads, and libraries, and computers. But this time, we're the ones maintaining the roads, and libraries, and computers. We have a solemn obligation to ensure that at the infrastructure level, (i.e., the protocol level), traffic passes through unrestricted. @miguelfreitas raised an issue above where that kind of anti-neutral behavior damages the functioning of the torrent system--a system designed with these kinds of infrastructure concerns in mind.
If there is illegal activity passing through these roads we maintain, then by all means, feel free to notify authorities you trust. Tell them to register a Twister account--you can even show them how. They can get onto these same roads and go chase criminals. But don't take that power into your hands, or as @thedod said, you will definitely be asked to use it one day in ways you didn't anticipate.
If you still want to play judge and jury on a network that is literally maintained by everyone else using it on an equal footing, well, go ahead and fork, but don't expect that effort to be appreciated.
I highly encourage everyone with a stake in this issue to read this USA hosting provider's stance on the content they host. They've stayed in business for long enough--perhaps they're doing something right?

Thanks @miguelfreitas for carving out some sensibility in this discussion. Part of seizing back the public forum with decentralisation and P2P is having the responsibility to collectively police its use. Individual, not infrastructural, block-lists are an anarchistic way to protect the commons of Twister and to keep things high-signal and low-abuse.
As stated, this isn't a protocol or algorithmic thing; this is already very possible for nodes who wish to patch their own software, and no other network nodes would be affected. The danger is that sets of patches will proliferate which lead to network instability because they're sloppy or non-standard, and all for nothing but grousing about "censorship" (which is being misplaced in this case) and nonsense assertions that other users are morally obliged to carry child-abusive content.
Please do include a standard, clean way for nodes to reject and refuse to relay data. Free speech is as much about what you choose not to say as what you do say, and when I relay others' content, that's my speech. I steadfastly believe protecting my right not to speak is critical to Twister's mission of protecting my Freedom of Speech.

@cathalgarvey Perhaps I was unclear. In a decentralized context, you are both user and provider. As a provider, I think you should not lose sight of certain obligations you have, as I have raised above. "Users" are not "morally obliged" to carry any content they don't want to. Users don't carry content. As others have mentioned, as a user, information you don't want to see is not part of your UX.
Please speak straightforwardly, without conflating these two separate concerns: are you for per-node inspection, monitoring, and control over traffic, or not?

When people say "Just report to your local police" they are asking for censorship. Censorship is the involvement of a third party who prevents you and another from communicating. It's clearly not always bad; we are generally all happy to see child abuse not being uploaded by child abusers...right?
The disagreement is what happens once it is uploaded. Many, including you I think @talexand, appear to want abuse material to freely circulate once it hits a network, and to pretend that it's not your problem if you don't see it (i.e. UX layer).
This is simply washing your hands. You want kids to be protected from child abuse, so you clearly want policing, but you don't want to be responsible for policing because it doesn't fit your aesthetic of anarchism.  If you want to be decentralised, prepare to accept the responsibility that centralisation took from you.
I know exactly the difference between my refusal to relay content and third-party/state censorship. I live in Ireland, and we have plenty of censorship over here still. In fact, I've written a microstatus network explicitly to protest Irish state censorship (albeit a really bad one written in code-golf Python). So yes, thanks, I know the difference and I know exactly what I'm requesting. I'm requesting the ability to enact my responsibilities towards an anarchic network.

And btw @talexand, if "Relaying traffic is not speech" then the free-speech argument is totally irrelevant. So either claim it is speech, in which case refusing to relay is also free speech, or stop discussing this as a freedom issue at all.
It is about Free Speech, but not about Censorship, because this is about our individual choices to relay; to speak, or not to speak.

Thanks, @cathalgarvey, for inspiring the name of my I2P fork:
OliverTwister :smiling_imp:
@miguelfreitas - I don't think "NSA proof" is a "serious claim" (they don't make journalists like they used to), but it's the thought that counts. Do you still think it?
You drive your fork carefully. Ours will be "paedo-friendly" simply because we're unconditionally friendly.
Peace, :passport_control: JulleNaaiers

http://scary.tasty.sexy/2015/09/on-the-perception-of-imaginary-differences

For the record [we've chatted much since :wink:], my reply. :heartbeat:

we've chatted much since

friendly fire incident, case closed.


Benchmark M1 Max Mac Studio

TODO.

262.45 Gflops in my first run, but need to do some power profiling and tweak Docker settings to see if I can get better. (I'm running inside Docker so there will inevitably be a little overhead).

================================================================================
HPLinpack 2.3  --  High-Performance Linpack benchmark  --   December 2, 2018
Written by A. Petitet and R. Clint Whaley,  Innovative Computing Laboratory, UTK
Modified by Piotr Luszczek, Innovative Computing Laboratory, UTK
Modified by Julien Langou, University of Colorado Denver
================================================================================

An explanation of the input/output parameters follows:
T/V    : Wall time / encoded variant.
N      : The order of the coefficient matrix A.
NB     : The partitioning blocking factor.
P      : The number of process rows.
Q      : The number of process columns.
Time   : Time in seconds to solve the linear system.
Gflops : Rate of execution for solving the linear system.

The following parameter values will be used:

N      :   50004
NB     :     256
PMAP   : Row-major process mapping
P      :       1
Q      :      10
PFACT  :   Right
NBMIN  :       4
NDIV   :       2
RFACT  :   Crout
BCAST  :  1ringM
DEPTH  :       1
SWAP   : Mix (threshold = 64)
L1     : transposed form
U      : transposed form
EQUIL  : yes
ALIGN  : 8 double precision words

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

- The matrix A is randomly generated for each test.
- The following scaled residual check will be computed:
      ||Ax-b||_oo / ( eps * ( || x ||_oo * || A ||_oo + || b ||_oo ) * N )
- The relative machine precision (eps) is taken to be               1.110223e-16
- Computational tests pass if scaled residuals are less than                16.0

================================================================================
T/V                N    NB     P     Q               Time                 Gflops
--------------------------------------------------------------------------------
WR11C2R4       50004   256     1    10             315.36             2.6432e+02
HPL_pdgesv() start time Fri Nov 18 04:40:23 2022

HPL_pdgesv() end time   Fri Nov 18 04:45:39 2022

--------------------------------------------------------------------------------
||Ax-b||_oo/(eps*(||A||_oo*||x||_oo+||b||_oo)*N)=   8.60823560e-04 ...... PASSED
================================================================================

Finished      1 tests with the following results:
              1 tests completed and passed residual checks,
              0 tests completed and failed residual checks,
              0 tests skipped because of illegal input values.
--------------------------------------------------------------------------------

End of Tests.
================================================================================

So 264.32 Gflops at 66W, or 4 Gflops/W


options.json files returns incomplete year range

Hi,
I have a weird issue, the year 2011 is not showing in my graph < http://<IP_ADDRESS>/mccallum/ >
The json.catalog.txt file has plenty of entries for 2011 eg
{"date": 2011, "uni": "uow", "searchstring": "<a href=\"http://www.uow.edu.au/content/groups/public/<EMAIL_ADDRESS>target=\"_blank\">2011 document from uow", "filename": "_var_www_html_mccallum_bookworm_transform_2011_uow_uow125352_2011_uow"}

The catalog.txt file also has plenty of entries
1       _var_www_html_mccallum_bookworm_transform_2011_uow_uow125352_2011_uow   <a href="http://www.uow.edu.au/content/groups/public/<EMAIL_ADDRESS>target="_blank">2011 document from uow  uow     2011

The fastcat table seems to have 2011 entries eg
 26 |   4976 |      23 |      2011 |

Appreciate any suggestions on diagnosing.
Kind regards
Tim

Hmm, this seems to be caused by some poor decision making on the part of the algorithm that determines what years are in the database (many bookworms have a lot of year 0 dates in them, and it tries to trim those out).
This is bad behavior and should remain as a bug--but you should be able to fix it manually by opening the options.json file in your web directory, which looks like this: and replacing the occurrences of 2012 with 2011.
{"ui_components": [{"type": "text", "dbfield": "word", "name": "Word(s)"}, {"categorical": {"sort_order": [], "descriptions": {}}, "type": "categorical", "dbfield": "uni__id", "name": "uni"}, {"name": "date_year", "initial": [2012, 2023], "range": [2012, 2023], "type": "time", "dbfield": "date_year", "unit": "date_year"}], "default_search": [{"counttype": "Occurrences_per_Million_Words", "smoothingSpan": 0, "words_collation": "Case_Sensitive", "time_measure": "date_year", "search_limits": [{"word": ["test"]}]}], "settings": {"sourceName": "mccallum", "sourceURL": "mccallum", "itemName": " text", "dbname": "mccallum"}}

Hi Ben,
Thank you, I updated the options.json file and achieved the result I was after.
Chat soon
Tim


README links to nothing

### » **[Install]() • [FAQ]() • [Modifications ]() • [Support]() • [Contributing]()**
They are formatted as links but lead to nothing. Is documentation planned?

What's unclear about "undocumented"? I had no chance to do anything here, this is nowhere near a stable release. Originally there only was a "dev" branch and master was empty. Somehow it has gone "viral" since then, before anything was ready.
I've said this everywhere, but OK, here is it again: Wait for the release. This is undocumented..

Duplicate of #5


CockroachDB

Add CockroachDB to supported databases.

Using the org.hibernate.dialect.CockroachDB201Dialect dialect
Updated migrate taskdef's
Added COCKROACHDB_21_1 to DriverTypeEnum
Added tests similar to other database driver tests to cover CockroachDB.

Heya Joe, this looks pretty cool! I think we will be able to merge this and allow it to be used experimentally in the 6.1.0 release, but won't be able to officially support CockroachDB as one of our primary databases. Does that work?

Heya Joe, this looks pretty cool! I think we will be able to merge this and allow it to be used experimentally in the 6.1.0 release, but won't be able to officially support CockroachDB as one of our primary databases. Does that work?

That would be great!  It is in line with what I was hoping to achieve for the time being.

@JoeShook thanks for the contribution!
I'd love to hear about your experiences with CockroachDB. I've been hearing great things about it for a while now, but I don't have any first hand experience with it. No obligation of course, but I bet if you posted a note about your experience so far in the Google Group others would probably be interested.


Add tutorial for using components in systems

🎉 New feature
Practices:

I tried to keep it as straight-forward as possible, only providing brief explanation when needed. This is so that tutorials are not explanations, following the Divio documentation principles.
Links to other pages are provided when context and examples are needed, so that a user who isn’t a dev team developer can understand what we’re talking about. But, IANAD, IANAL, IANAU (I am not a user).
For the sake of maintenance, all links are \ref links or relative links, except for links going to GitHub source code.

Summary
This PR adds two pages.
Parent page is an overview of using components in systems. It has a high-level overview of what people need to know, linking to prerequisites and resources. It then talks about the ECM object in practical terms as the gateway to access entities and components.
It then links to a list of case studies, of which there is just 1 item right now, for JointForceCmd component (child page). The assumption is that we will be adding more case studies to this list for other components.
The child page uses the simplest built-in system plugin ApplyJointForce to explain how to use the JointForceCmd component through the ECM, by finding the Joint and then modifying the component.
Test it
colcon build --merge-install --packages-select gz-sim8 --cmake-target doc

Navigate browser to build/gz-sim8/doxygen/html/usingcomponents.html (parent page) and build/gz-sim8/doxygen/html/compjointforcecmd.html (child page).
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[x] Added example and/or tutorial
[x] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

DCO was complaining because the 4 automatic signoffs used gmails. I just set it to pass.
Ready for another look.

DCO complained again, so I fixed it for real.


Grounds not connected

Grounds not connected between the two ground pins in the uno power header and then that circuit and the one that connects to the servos.

Resolved by virtue of new SBS from freetronics.


Console reporter and Serenity-bdd report not showing the correct value executed using Scenario Outline Examples

Hi Team,
I noticed an issue with the console reporter and serenity-bdd report when Examples are used in the feature file(s).
For example:
Scenario Outline: User verifies the strings in the menu are translated
        When Select <Language> language
        * Save the language selection
        * User navigates to the menu
        Then Verify the language string in menu is translated to <Translation>

        Examples:
            | Language | Translation |
            | German   | Sprache     |
            | French   | Langue      |
            | English  | Language    |

The "When" and "Then" statements printed on the report show always the first value in the table, though the tests are validated against the correct values. It created confusion in the reports as to what values were being tested.

Hi @Nywlem! I'm not able to reproduce this issue locally. Would you be able to publish a minimal reproducible example based on the template to Github? It can have empty step defs.
Thanks!
Jan

Serenity/JS v 2.20.0 introduced support for Cucumber 7 and an updated version of the Serenity BDD reporting CLI.
Since I wasn't able to reproduce the issue you're seeing, @Nywlem, I'm going to close this ticket.
Please feel free to reopen it if you spot the same thing in the latest version.
Thanks!

Serenity/JS v 2.20.0 introduced support for Cucumber 7 and an updated version of the Serenity BDD reporting CLI.
Since I wasn't able to reproduce the issue you're seeing, @Nywlem, I'm going to close this ticket.
Please feel free to reopen it if you spot the same thing in the latest version.
Thanks!


Add vertical line on x-axis during creation

Input from Karen B
Spencer: "vertical line can be handled with a custom option like (pseudo-code) referenceLine: {studyDay: 28)"

Array of reference lines

Test Notes: Test in CAT using: {"referenceLines":[{"studyDay":100,"label":"More than 99"},150]}

Pass


composer cant find package

[InvalidArgumentException]
Could not find a matching version of package kopokopo/k2-connect-php. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (stable).
Kindly assist.

@abiudeko, the package is not yet published. Please check again before the end of the week.

@abiudeko, the package has been published.  Let me know if you encounter any issues.


Appveyor:  force install grpcio >= 1.0rc1.

Toward #1863.

@dhermes I'm going to merge this one as soon as Travis  green, to see if it can un-hork our Appveyor problems.

LGTM. No need to wait on Travis but can you fix the typo I referred to?
PS Thanks for creating the gRPC label.


Extract type information

Hi there! Re issue #1076, I am wondering if it is possible to render the tag information so that it for each method, there can be a list of information like ClassName, MethodName, "(Param1Type, Param2Type, ...) ->  ReturnType" ?
Right now using  p obj.tags(:param) or  p obj.tags(:return), I am able to get a list of objects [#<YARD::Tags::Tag:0x007fea390943b0 @tag_name="param", @text="an Object to compare this {Country} with.", @name="c", @types=["Object"], @object=#<yardoc method TZInfo::Country#eql?>>] but I can't seem to combine the two type information together. Thank you!

@ericazhang17 I'm not sure I'm following this. To combine the two objects you would simply extract the .types attribute out of each of the two tags. It looks like you have all the data printed in your example, you just need to use the values in the way you want. Perhaps you can explain a bit about what you're trying to do?


new rule: add config parameters to missing-jsdoc rule

While jsdoc-format is enough to require correct formatting of docs, there’s no rule that I know of to ensure the docs exist in the first place. It would be useful to have a rule that requires they exist and not be blank for a configurable list of major items (default to everything?), such as:

classes
exported variables
functions
member variables
member functions
...anything else?

Thanks for the idea. This is very similar to #33. I will close that one as a duplicate.

Modules
exported classes
all classes
exported variables
functions
exported functions
public member variables
all member variables
public member methods
all member methods

From a limited TSLint knowledge and reading https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API, I think this requires the type checker for symbol.getDocumentationComment(). Yes?

@JoshuaKGoldberg I am pretty sure you can get the comments without using the type checker... but if you use the type checker then you probably get a much more structured object and would not have to use RegEx to pick apart the comment. Your suggestion is probably the way to go.

@ian-craig I think this issue is resolved?


Scala.js Module Splitting

Scala.js now supports module splitting, which would need some fiddling about to get the set up right but would improve game download times since they wouldn't need to be bundled with the engine.
How are engine versions managed?
This may not make 0.6.0, but it's on the board since it may be related to #105.

I looked into this ages ago and I think I decided it wasn't worth the hassle, or just wasn't right for our use case. Will close for now and see if anyone re-raises it.


Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

Coverage remained the same at 99.096% when pulling c2b0ad84ec0aa8214abf7a0c011e0f6469bd9bdc on analysis-z3vWv1 into 984aec2087a63ff6ef3615433b1b6bf230ef01f9 on master.


characteristic was supplied illegal value

Describe the bug

Just providing my log that I am getting from this plugin on homebridge v1.3.0 Beta
Steps To Reproduce

Install Homebridge Beta v1.3.0
Plugin Version

v0.7.1
Homebridge Config

{
           "name": "TuyaWebPlatform",
           "options": {
               "username"<EMAIL_ADDRESS>               "password": "xxxxxxxxxx",
               "countryCode": "1",
               "platform": "tuya",
               "pollingInterval": 600
           },
           "defaults": [
               {
                   "id": "12345678a1aaa11a1aa1",
                   "device_type": "light",
                   "light_characteristics": [
                       "Brightness",
                       "Color",
                       "Color Temperature"
                   ]
               }
           ],
           "scenes": false,
           "platform": "TuyaWebPlatform"
       },

Additional Context

[1/4/2021, 8:55:11 AM] [TuyaWebPlatform] Existing Accessory found [Name: Merkury EW003 LED Strip] [Tuya ID: 12345678a1aaa11a1aa1] [HomeBridge ID: 1234aa1a-123a-123a-12aa-1a1234aaaa1a]
[Merkury EW003 LED Strip@Merkury EW003 LED Strip@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[1/4/2021, 8:55:11 AM] [TuyaWebPlatform] Enable cloud polling with interval 605s
[Merkury EW003 LED Strip@Merkury EW003 LED Strip@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.

Thanks @donavanbecker!

Thanks @donavanbecker!

@milo526 no problem!

@milo526 no problem!

Hi, I am also seeing a similar issue for Color Temperature. Similar setup as above. These are FEIT lightbulbs if it matters. Thanks!
[Porch 2@Porch 2@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Porch 2@Porch 2@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Porch 1@Porch 1@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Porch 1@Porch 1@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 1@Garage 1@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 1@Garage 1@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 3@Garage 3@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 3@Garage 3@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 2@Garage 2@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 2@Garage 2@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Living room 2@Living room 2@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living room 2@Living room 2@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room 3@Living Room 3@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room 3@Living Room 3@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room 1@Living Room 1@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room 1@Living Room 1@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room Spot Light@Living Room Spot Light@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room Spot Light@Living Room Spot Light@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.

Hi, I am also seeing a similar issue for Color Temperature. Similar setup as above. These are FEIT lightbulbs if it matters. Thanks!
[Porch 2@Porch 2@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Porch 2@Porch 2@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Porch 1@Porch 1@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Porch 1@Porch 1@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 1@Garage 1@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 1@Garage 1@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 3@Garage 3@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 3@Garage 3@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 2@Garage 2@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Garage 2@Garage 2@Color Temperature] characteristic was supplied illegal value: number 1486 exceeded maximum of 500.
[Living room 2@Living room 2@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living room 2@Living room 2@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room 3@Living Room 3@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room 3@Living Room 3@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room 1@Living Room 1@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room 1@Living Room 1@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room Spot Light@Living Room Spot Light@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.
[Living Room Spot Light@Living Room Spot Light@Color Temperature] characteristic was supplied illegal value: number 1962 exceeded maximum of 500.

@milo526 now getting
[TuyaWebPlatform] Cannot read property 'context' of undefined

with Homebridge v1.3.0-beta.52

Hello,
Just updated to HB beta, here is the log I get for the plugin, might be helpful:
[17/2/2021, 09:22:22] Received warning for the plugin '@milo526/homebridge-tuya-web' from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 1477 exceeded maximum of 500.
[17/2/2021, 09:22:22] Received warning for the plugin '@milo526/homebridge-tuya-web' from the characteristic 'Brightness': characteristic was supplied illegal value: number 118 exceeded maximum of 100.
[17/2/2021, 09:22:22] Received warning for the plugin '@milo526/homebridge-tuya-web' from the characteristic 'Brightness': characteristic was supplied illegal value: number 275 exceeded maximum of 100.
[17/2/2021, 09:22:22] Received warning for the plugin '@milo526/homebridge-tuya-web' from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 1491 exceeded maximum of 500.
Beside this log everything still works as before.

@bosco90 thanks for informing me!
@donavanbecker with the latest version of the plugin you should no longer get the context error - could you confirm?
I believe this error was only shown when you restarted homebridge after adding new devices.

I am still getting the color temperature log that you see above.

Yeah I know - I was only wondering about your second comment

@milo526 now getting
[TuyaWebPlatform] Cannot read property 'context' of undefined

with Homebridge v1.3.0-beta.52

This should no longer happen.
The other errors will hopefully be solved shortly

FYI:
After updating to HB 1.3.0-beta.59 the log says:
[17/2/2021, 13:37:34] [@milo526/homebridge-tuya-web] This plugin generated warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 1469 exceeded maximum of 500. See https://git.io/JtMGR for more info.
Probably it's the same log that in latest beta shows this way.

@milo526 Yes that is gone.

I too am seeing this warning error after updating to 1.3.0
[22/02/2021, 19:49:10] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 1493 exceeded maximum of 500. See https://git.io/JtMGR for more info.
It seems to be working and all the extra logging info has gone under the previous version which is good.

Same errors with the release version of 1.3.1
[2/23/2021, 10:04:12 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 351 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[2/23/2021, 10:04:12 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.

Didn't see this sorry. Also having the same issue.

@milo526/homebridge-tuya-web v1.0.0
I'm also getting a lot of "illegal characteristic value" messages:
[3/17/2021, 12:28:41 AM] [TuyaWebPlatform] Existing Accessory found [Name: Smart Bulb] [Tuya ID: eb2a3268a518fe06d9tzno] [HomeBridge ID: e85017a9-5b19-4075-8a67-45f253499d66]
[3/17/2021, 12:28:41 AM] [TuyaWebPlatform] Existing Accessory found [Name: Smart Bulb 3] [Tuya ID: ebbc5c932afe52aebab7fx] [HomeBridge ID: 64e410d5-d1b9-49b2-945b-ad9491deca27]
[3/17/2021, 12:28:41 AM] [TuyaWebPlatform] Existing Accessory found [Name: Smart Bulb 2] [Tuya ID: eb06fb5aaa13424be0xl9z] [HomeBridge ID: 7f0a01d4-fe0c-462c-8c53-d8bb900fc600]
[3/17/2021, 12:28:41 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:28:41 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:28:41 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:28:41 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:28:41 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:28:41 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:49 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:52 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:52 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:52 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:52 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:53 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:53 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:55 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:55 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:55 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:55 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:55 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:55 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:56 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:56 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:56 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:56 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:56 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 196 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/17/2021, 12:33:56 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 2000 exceeded maximum of 500. See https://git.io/JtMGR for more info.
[3/17/2021, 12:34:20 AM] [Homebridge UI] [admin] Accessory layout changes saved.

Generic tuya smart bulbs purchased on AliExpress.

The colortemperature warning should be fixed with the newly released v1.0.1

Hey,
i have now very. 1.0.1 and Homebridge vers. 1.3.4.
Ive some issues in the log and HomeKit reacts very slowly. I use a Raspi 4.
[3/28/2021, 15:41:16] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/28/2021, 15:41:16] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 220 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/28/2021, 15:41:16] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/28/2021, 15:41:16] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/28/2021, 15:41:16] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number 78 exceeded minimum of 140. See https://git.io/JtMGR for more info.
[3/28/2021, 15:41:16] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[3/28/2021, 15:41:16] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number -196 exceeded minimum of 140. See https://git.io/JtMGR for more info.
[3/28/2021, 15:41:16] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.

Hello,
today I become this msg too...
[3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info. [3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info. [3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'Color Temperature' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info. [3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'Hue' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info. [3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'Saturation' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info. [3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info. [3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info. [3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'Color Temperature' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info. [3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'Hue' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info. [3/29/2021, 11:37:04] [@milo526/homebridge-tuya-web] This plugin slows down Homebridge. The read handler for the characteristic 'Saturation' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

@Sebastian-Voigt thanks for the info.
Could you please try running Hoobs/Homebridge in debug mode and see if that gives you any stack trace?
It's a bit hard to debug now since my own instance doesn't give the This plugin slows down Homebridge instance.

After the Reset its seems to be good for the first.
But I have seen this for the illegal values:
[3/29/2021, 12:08:15] [TuyaWebPlatform] [Licht] Characteristic.ColorTemperature - [GET] 18400
[3/29/2021, 12:08:15] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Color Temperature': characteristic was supplied illegal value: number -196 exceeded minimum of 140. See https://git.io/JtMGR for more info.
[3/29/2021, 12:08:15] [@milo526/homebridge-tuya-web] Error:
    at ColorTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
    at ColorTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
    at ColorTemperatureCharacteristic.updateValue (/usr/local/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/colorTemperature.ts:70:19)
    at /usr/local/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/colorTemperature.ts:32:14
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Any resolution on this? Still have the same issue. Thanks!!!
[03/04/2021, 08:15:13] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info. [03/04/2021, 09:00:01] [Ring] Setting Laval Mode to home [03/04/2021, 09:18:26] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info. [03/04/2021, 09:18:44] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.

YUP still happening v1.0.1
[4/7/2021, 5:23:55 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 314 exceeded maximum of 100. See https://git.io/JtMGR for more info.

[07/04/2021, 23:03:09] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
Plugin Ver: TuyaWebPlatform
@milo526/homebridge-tuya-web v1.0.1

Thanks for the help guys, I'll look into this when I have some time.
Live is crazy busy for me at the moment as you might have already noticed.

@milo526 ...not sure if you've seen what they've done on HomeAssistant with their Tuya integration, but looks like they made it a configurable option. Maybe this would help restart this discussion?
See reference to setting to brightness range under Lights --> https://www.home-assistant.io/integrations/tuya/
Code: https://github.com/home-assistant/core/blob/dev/homeassistant/components/tuya/light.py
Is this adaptable?

@milo526 ...not sure if you've seen what they've done on HomeAssistant with their Tuya integration, but looks like they made it a configurable option. Maybe this would help restart this discussion?
See reference to setting to brightness range under Lights --> https://www.home-assistant.io/integrations/tuya/
Code: https://github.com/home-assistant/core/blob/dev/homeassistant/components/tuya/light.py
Is this adaptable?

Short answer - no.
Our code-bases are very different. They are even in different programming languages.
The vauge idea is useful but also the same one we already came up with before.
It is not that it is unclear how to fix it. The problem is that there is nobody available to write the fix without needing a lot of guidance (which would once more require my time, that I simply do not have available at the moment).

@milo526 Understood...thx

@milo526 how could I help with that Brightness issue?

Getting same on latest release. [5/4/2021, 3:57:57 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.

I hope that the newest pre-release (v1.1.0-0) solves these issues (or at least enables you to solve them)
It adds new configuration options (per device) for the min and max number of kelvin as well as a warning when your kelvin range is not configured correctly.
If you are able to install the pre-release, please do so and let me know how it goes!
If you have other (non-kelvin-configuration related) issues with the pre-release, please post them in the discussion https://github.com/milo526/homebridge-tuya-web/discussions/276

Thks Milo
I confirm that installing pre release V1.1.0-0 and then configure each light device by defining brightness to min and max value sent by tuya, the warning messages disapeared

@dodelafo are you able to provide me a sample config snippet on how you did that? I'm still getting an error message:
[Kitchen R Top] Characteristic.ColorTemperature - Characteristic 'ColorTemperature' will receive value lower than allowed mired (-9703) since provided Tuya kelvin value (25071) exceeds configured maximum Tuya kelvin value (255). Please update your configuration!

I can understand that the values don't match. What I don't get is why they're so wildly all over the place. What I've got is:
{
    "id": "[ID]",
    "device_type": "light",
    "min_brightness": "10",
    "max_brightness": "1100",
    "min_kelvin": "255",
    "max_kelvin": "0",
    "light_characteristics": [
        "Brightness",
        "Color Temperature"
    ]
}

Still Facing the same issue can someone please provide steps to follow to remove these
[1/30/2023, 1:30:19 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:30:19 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:30:21 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:30:21 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:30:24 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:30:24 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:30:31 PM] [Homebridge UI] Terminal session ended.
[1/30/2023, 1:30:33 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:30:33 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:30:34 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:30:34 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:31:12 PM] [Homebridge UI] Starting terminal session
[1/30/2023, 1:31:12 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:31:12 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:31:13 PM] [Homebridge UI] Terminal session ended.
[1/30/2023, 1:31:13 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:31:13 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:36:22 PM] [Homebridge UI] Starting terminal session
[1/30/2023, 1:36:22 PM] [Homebridge UI] Terminal session ended.
[1/30/2023, 1:36:23 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:36:23 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:36:24 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:36:24 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:36:27 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:36:27 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:37:03 PM] [Homebridge UI] Changes to config.json saved.
[1/30/2023, 1:37:07 PM] [Homebridge UI] Starting terminal session
[1/30/2023, 1:37:07 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:37:07 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:37:08 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:37:08 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:37:11 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:37:11 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:37:28 PM] [Homebridge UI] Terminal session ended.
[1/30/2023, 1:37:29 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:37:29 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:37:30 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:37:30 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:37:33 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:37:33 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:37:35 PM] [Homebridge UI] Starting terminal session
[1/30/2023, 1:37:35 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:37:35 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.
[1/30/2023, 1:37:39 PM] [TuyaWebPlatform] [Smart WiFi music LED Strip] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[1/30/2023, 1:37:39 PM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info.


Setup testing

Please create a pull request against develop next time. I created a new branch from develop and merged your request into it (wilke/merge-wltrimble-369). Testing and debugging there.


MAINT: use disable parameter for progress bar hiding

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
36 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.06%) to 92.471%

Files with Coverage Reduction
New Missed Lines
%

.nox/test-3-12/lib/python3.12/site-packages/diverse_seq/cluster.py
6
91.44%

.nox/test-3-10/lib/python3.10/site-packages/diverse_seq/cluster.py
6
91.44%

.nox/test-3-11/Lib/site-packages/diverse_seq/cluster.py
6
91.44%

.nox/test-3-11/lib/python3.11/site-packages/diverse_seq/cluster.py
6
91.44%

.nox/test-3-12/Lib/site-packages/diverse_seq/cluster.py
6
91.44%

.nox/test-3-10/Lib/site-packages/diverse_seq/cluster.py
6
91.44%

Totals

Change from base Build<PHONE_NUMBER>9:
-0.06%

Covered Lines:
6669

Relevant Lines:
7212

💛  - Coveralls


(Wallet Addition) Add Galaxy Station wallet

What is the purpose of the change:
Include Galaxy Station Cosmos-Kit wallet

I enough Osmo in my wallet for the tx but wallet is not selecting Osmo and also Osmo is not included in the gas token list.
https://github.com/osmosis-labs/osmosis-frontend/assets/103904125/8e315734-5846-4eea-ad09-775cda85f680

@echel0n-HX sometimes the networks are disabled and deposit/withdraw doesn't pop up the tx window.
Screencast from 25-06-24 01:10:56 PM IST.webm

@echel0n-HX this is my Osmosis address but as you can see in the video above Osmo is not included in the gas fee token list
osmo1qnqzdknfvr97uswyvr5qcehmlxhja92zq74dz5

@kamal-sutra I've updated the LCD endpoint for Sentinel and performed a Osmosis -> Sentinel swap
https://www.mintscan.io/osmosis/tx/928A20D3833E3794480A429C84F0C45692E567A5E55D13F112F4A8A4480A192D

@echel0n-HX check again and still same issue
https://github.com/osmosis-labs/osmosis-frontend/assets/103904125/020e05a3-b931-41bd-8cd9-dfc224749e91

@CryptoAssassin1 what dev env are you testing this from, I'm currently using Win 11 and Edge with Galaxy Station Wallet v1.0.51

Osmo -> Tia
https://www.mintscan.io/osmosis/tx/8F197DBD75406441EF0675AC2DFDCD9B1B1E59CF63091F4DA0A69B4F310708C8
Tia -> Osmo
https://www.mintscan.io/osmosis/tx/C64B9260084C5900A4B26E59A1B57E443FC5B43203F8ADE8E36C949FC3F82E05

@echel0n-HX im using Ubuntu 22.04.1 LTS and extension version 1.0.51

@CryptoAssassin1 I've messaged you on Discord, I believe the issue may be related to Chrome browser

@echel0n-HX

When Max Osmo is selected to swap, it is not deducting gas fee automatically. Need to manually input Max minus gas amount.
When there is 0 Osmo balance, the wallet is not switching to other available whitelisted fee tokens like atom/tia/usdc etc..

@echel0n-HX i dont think its OS and browser issue.
The issue is related to wallet.

@kamal-sutra thanks for that info, I am now able to reproduce @CryptoAssassin1 issue and am working to resolve it.

@kamal-sutra I removed the preferNoSetFee sign option, please authorize Vercel and lets see if that resolves the fee issues.

@CryptoAssassin1 @kamal-sutra deploy authorized

@CryptoAssassin1 @kamal-sutra so after extensive debugging, what I have determined is that osmosis zone app is posting a request to Galaxy Station extension with the wrong denom, its using ibc/0EF15DF2F02480ADE0BB6E85D9EBB5DAEA2836D3860E9F97F9AADE4F57A31AA0, when it should be using uosmo
Its not cosmos-kit issue either, as we have tested on another app that uses cosmos-kit to swap whale -> to osmosis and logged the posted request, the proper denom of uosmo was present.
Any ideas ?

@CryptoAssassin1 @kamal-sutra so after extensive debugging, what I have determined is that osmosis zone app is posting a request to Galaxy Station extension with the wrong denom, its using ibc/0EF15DF2F02480ADE0BB6E85D9EBB5DAEA2836D3860E9F97F9AADE4F57A31AA0, when it should be using uosmo
Its not cosmos-kit issue either, as we have tested on another app that uses cosmos-kit to swap whale -> to osmosis and logged the posted request, the proper denom of uosmo was present.
I should also note that I did try whale -> osmosis as well on the latest osmosis zone preview, same issue with the wrong denom.
Any ideas ?

@JoseRFelix perhaps you have some context here?

@kamal-sutra regarding the gas fee issues, it seems this was brought up before when Terra Station was added and it was determined the issue to be on the side of osmosis app possibly, please see previous thread regarding this https://github.com/osmosis-labs/osmosis-frontend/pull/2210#issuecomment-1886867424

what next steps are required to get this moving forward ?
the gas fee denom issue doesn't look like its something on our side that is fixable, as long as there is osmo in the end-users wallet, tx's go through fine.

@echel0n-HX does galaxy station accept alternative fee tokens? Our FE suggests alternative tokens to pay fees depending on the user's balance

@jonator based on the gas fee denom passed in via the TX request, and if there is not enough of it to cover the gas, galaxy station will provide the end-user the ability to swap other coins using swap.io to get the required amount of said gas fee denom.
so in the case of the gas denom required being osmo, then osmo needs to be sent as the gas fee denom in the TX request, if there is not enough osmo in the end-users wallet, they will be able to swap other tokens to get more osmo, such as swapping whale -> osmo or chihuahua -> osmo.
the problem right now with trying to swap lunc through swap.io is that there are no routes for it, and its an issue that swap.io is looking into still on their end.
is there a way to have osmosis frontend pass in osmo instead of passing in alternative fee tokens based on balance specifically for galaxy station ? also, this same issue plagues terra station.

@jonator another idea would be to implement a dropdown to allow the end-user to select the gas denom they wish to use for the fee, that will then be passed on in the TX request to the connected wallet, sort that dropdown by balance as well

@jonator I see PR https://github.com/osmosis-labs/osmosis-frontend/pull/3423 has been created to address the alt fee issue, this PR should resolve the fee issues we are seeing with Galaxy Station, is there a time frame for when that PR will be merged so we can update our PR as well ?
Thanks!

stale


101-merge-classes

Resolves #101
Questions:

Do you want to add some comments to that code?
I think we don't need to remove duplicated classes during merging, am I right?

Note for the future: We can probably use a faster hasher in HashMaps.

1: No. I think the short function comment, and function name describe well enough what it does, and your code is straightfwd.
2. I agree. From the DOM's perspective, I don't think it matters; removing duplicates or not here is subjective, and I don't have an opinion.
Nice job cleaning up my naive approach.


Needle in the wrong location

Perhaps I'm doing something wrong here, but the needle location is not matching the value. Not sure if its me messing this up or an internal defect.

Your proportions on the dial was off just a bit. Try the code I am pasting below, I completed the divisions by 300 with minorTicks = 12. Hope it helps! Johnkosh

`
<!doctype html>

Gauge Test

I'm having a similar problem. I don't know what I'm doing wrong!

    minValue: 0
    maxValue: 100
    valueInt: 3
    valueDec: 0
    width: 174
    height: 222
    exactTicks: 1
    majorTicks: [0,20,40,60,80,100]
    minorTicks: 10
    highlights: [{'from': 0, 'to': 20, 'color': 'rgba(255, 0, 0, .3)'},{'from': 20, 'to': 100, 'color': 'rgba(0, 0, 255, .3)'}]


ingest metrics to Splunk only when metrics index is given

when metrics are ingested to event type splunk index, client doesn't error out but it is not right. metrics should be sent to
Splunk's metric type index.
this prevents metrics data being sent when metrics_index is not specified.

with blank metrics_index, i get this error.
$ helm upgrade olly -f .tmp/values.yaml .
Error: UPGRADE FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
splunk-otel-collector:
- (root): Must validate "then" as "if" was v
- splunkPlatform.metrics_index: String length must be greater than or equal to 1
- (root): Must validate all the schemas (allOf)

so the validation is working correctly.

Should we also add a comment to metrics_index saying that it's required when metricsEnabled=true?
I still don't get why it's only applicable to metrics. Does HEC exporter set's some default value for logs, but not for metrics?

add comment and applied same validation to index

It looks good to me.
I'm thinking would it be easier for users if we have default value for indexes in values.yaml? I see SCK uses main for both logs and metrics. Shouldn't we do similar here?
I'm ok with any approach, just trying to think of it from end user perspective. Right now we call out only endpoint and token as required fields, but if user sets them up they'll get this validation error.

yea, it would work sending all to main index, but metric data shouldn't really go to main index (event type index)
so even for SCK, we print this warning.
##################################################################
####   WARN: You did not set splunk.hec.indexName correctly   ####
##################################################################

Metrics collected by splunk-kubernetes-metrics are supposed to be indexed in
a Metrics Index. But you are using the same index for metrics as for logs
and/or objects. You should use splunk-kubernetes-metrics.splunk.hec.indexName
to set index for metrics.

Follow
http://docs.splunk.com/Documentation/Splunk/latest/Indexer/Setupmultipleindexes#Create_metrics_indexes
to create a Metrics Index in your Splunk.

Then run:

    helm upgrade sck -f values.yaml splunk/splunk-connect-for-kubernetes

Hm.. Ok does setting up metrics index require some manual steps on Splunk side while main log index is always available?
I'm thinking maybe we should make metricsEnabled: false by default and set default index: main for logs?

I'm merging this PR, but let's try to do something with default values before the release to make it work with endpoint and token as only required fields

right. main is always there and it requires users to manually create metric type index. I like your suggestion for default. will create PR

Thanks @rockb1017, could you please also submit a PR to change this line in the specification https://github.com/signalfx/gdi-specification/blob/main/specification/configuration.md?plain=1#L140 with justification that it requires metrics index to be created on Splunk side, so we should keep it disabled by default.


UX Improvements + Update Model Version

This commit adds a few UX improvements and the ability to update model version.

Waiting on new endpoint from server to merge this in.  Want to provide import validation before adding to main.


Clarify Guarantees about grpc.Future Interface

Since the beginning, grpc.UnaryStreamMultiCallable.__call__ and  grpc.StreamStreamMultiCallable.__call__ have returned objects that fulfill three interfaces: iterator, Call, and Future. However, in the docstrings, only the first two of these interfaces are mentioned. Many of our users have come to depend on the fulfillment of the Future interface. We need to document the continued satisfaction of that interface as an API guarantee.
The same problem exists in the docstrings for the interceptors. However, the situation is fundamentally different there, as we are not in control of all interceptor implementations. There are likely some floating around that do not implement the Future interface. We amend the docstrings here to merely recommend that interceptor authors fulfill the Future interface.

iOS Binary Size Diff was an infra flake:
Tue Feb  9 13:01:02 PST 2021 - Error in download: java.io.IOException: Error downloading [https://dl.google.com/go/go1.12.5.darwin-amd64.tar.gz] to /Volumes/BuildData/tmpfs/tmp/bazel/external/go_sdk/go_sdk.tar.gz: Read timed out


HOWTO: how to show big json in sentry's GUI?

Hello.
I just need an advice. I'm sending json in post request to my API server and dump's it to sentry in case of an Exception.
This json has the following data
{
"field1": "10_chars",
"field2":"20_chars",
"field3":"100kb_chars",
"field4":"15_chars",
"field5":"35_chars",
}

Due to my debug everything is ok on client's side. The whole request is being sent to sentry but sentry's GUI shows the body as
{
"field1": "10_chars",
"field2":"20_chars",
"field3":"7kb_chars..."
}

So the problems are:

The field3 is truncated to 7-8kb (I do not mind)
Fields after field3 are not shown at all

I'm using sentry Sentry 21.8.0 and latest symfony sentry PHP
I just want to understand - is this client's issue on my side e.g. incorrect configuration or server side can be adjusted or fixed ?
Thank you

This is something that relates to the serializazion done by the base SDK, so I'll move the issue there.
In any case, the answer may depend on the kind of data that is being sent: if it's a JSON, on the PHP level is a simple string, so the serializer truncates the data do avoid bloating the payload, that would be otherwise rejected for being too big.
If instead it's a PHP array, the serializer would act on a per-element basis, and the truncation would work on the single element, making the payload probably more useful.


The console always outputs these.

I/AssistStructure( 4613): Flattened final assist data: 476 bytes, containing 1 windows, 3 views
I/AssistStructure( 4613): Flattened final assist data: 480 bytes, containing 1 windows, 3 views
I/AssistStructure( 4613): Flattened final assist data: 480 bytes, containing 1 windows, 3 views
I/AssistStructure( 4613): Flattened final assist data: 476 bytes, containing 1 windows, 3 views

D:\flutter\bin\flutter.bat doctor --verbose
[√] Flutter (Channel stable, 3.0.1, on Microsoft Windows [版本 10.0.22000.675], locale zh-CN)
    • Flutter version 3.0.1 at D:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fb57da5f94 (3 weeks ago), 2022-05-19 15:50:29 -0700
    • Engine revision caaafc5604
    • Dart version 2.17.1
    • DevTools version 2.12.2

[√] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at D:\AndroidSDK
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: D:\AndroidStudio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.11+9-b60-7590822)
    • All Android licenses accepted.

[X] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[X] Visual Studio - develop for Windows
    X Visual Studio not installed; this is necessary for Windows development.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[√] Android Studio (version 2021.1)
    • Android Studio at D:\AndroidStudio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+9-b60-7590822)

[√] IntelliJ IDEA Ultimate Edition (version 2022.1)
    • IntelliJ at D:\IntelliJ IDEA 2021.3.3
    • Flutter plugin version 68.1.4
    • Dart plugin version 221.5787.37

[√] Connected device (3 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 10 (API 29) (emulator)
    • Windows (desktop)                  • windows       • windows-x64    • Microsoft Windows [版本 10.0.22000.675]
    • Edge (web)                         • edge          • web-javascript • Microsoft Edge 102.0.1245.33

@ddxl123
This seems to be coming from Android native. See this: https://developer.android.com/reference/android/app/assist/AssistStructure
Also check below issue comments from flutter team member on the I/AssistStructure log:
https://github.com/flutter/flutter/issues/11292#issuecomment-356792594
https://github.com/flutter/flutter/issues/11292#issuecomment-356831569
Can you provide more details on when do you see the said log ? Are you using accessibility and are there steps to replicate these logs ?

I facing the same issue, I using the android studio emulator and every time I touch the screen the terminal output this:
I/AssistStructure(11967): Flattened final assist data: 388 bytes, containing 1 windows, 3 views
D/InputConnectionAdaptor(11967): The input method toggled cursor monitoring on


CanvasOffscreen uses fallback with Vite

First of all thanks @drcmda for this amazing package.
I tried integrating the example on a Vite based project and it seems like CanvasOffscreen always use fallback scene.
Using the CRA example provided in this repo works fine instead.
Minimal Vite example: https://stackblitz.com/edit/vitejs-vite-pujh5e?file=src/App.jsx
Tested on latest Chrome on a Macbook Pro M1.

i tried using vite as well but couldn't make it work, it looks like it has trouble loading the worker. it's more like a vite problem, nothing that i think i can fix here, it's just a worker after all. but if you figure it out i would love to document what must be done to make it work.

it looks like vite can't handle jsx in workers. if the <Scene /> is removed at least i can console.log in it to make sure the worker runs, but once any jsx is in there the worker doesn't execute.

ok, started to see something if i rename to worker.jsx, and if i just render a mesh with a geometry. as soon as i import the scene component vite tries to inject styles to document, which doesn't exist in the worker. :-S

this is the workaround :( it's very bad
https://github.com/pmndrs/react-three-offscreen#vite

Hello, I've fiddled with rendering r3f offscreen a while ago and in conjunction with this I made a patch plugin for Vites dev client to re-enable fast refresh in workers.
Just saw this project and updated the plugin for latest Vite, it seems to work okay-ish still: codesandbox
Plugin vite-plugin-react-worker
Any updates outside the canvas re-triggers the effect doing the canvas offscreen handover, which will fail. This results in the fallback being rendered instead. But for changes inside of the worker it seems to work.


refactor: Cleaner flags

Raised bug https://github.com/kyma-project/cli/issues/1256 to address pipeline flakiness