Add documentation about our versioning policy and all releases

These documents describe the versioning and release policy of Tobira. The releases table still contains dummy releases just to show how I intend this table to work.

Story time for the people who might wonder how we arrived at this. (Lars and Julian, you don't need to read, you already know this).
One very prevalent versioning scheme is SemVer, of course. All three of us are not big fans of it, with me still saying it has useful properties and is sufficient for some use cases, Julian actively hating it, and Lars being somewhere in the middle. One important thing everyone should understand about SemVer, that the terms it uses (e.g. "breaking change") need to be defined for your software to make any sense. They do not have a universal meaning. So I suggested defining that for Tobira, as I am not a fan of completely opaque version identifiers or once that consists only of the release date.
There was disagreement about the usefulness of using SemVer with out definitions of "breaking" and "major" changes. I still hold the opinion that there is some usefulness, although I was convinced that it might be very small in our case. We also noted that the version identifier is also a big part of "marketing" a software product. And in that regard, SemVer might be harmful. But I still didn't like date-versions so the next suggestion would be to use a nice marketable name in something like bear and bear.1. The .1 was a patch release that would just contain small bug fixes and stuff. This should not be used for "compatibility" considerations, but just for marketing: to only use a new cute name when something "bigger" changes.
However, even with the idea of using cute names with starting letter in alphabetical order, Lars noted that it's harder to know whether sealion or runbird is the earlier release. So we introduced a number for the "major" version again. And to put the two numbers next to one another, arriving at x.y cutename.
We actually briefly considered adding another part to the version identifier. I noticed a nice property of semver versions: for any two given versions, you can trivially know whether there was a breaking change between them.  Using numbers is a lot smarter.) Further, you know exactly which version(s) in between contain the breaking change. I wanted something like that. But there are many different kinds of breaking changes for Tobira, and cramming they all into one category makes the number way less useful. The idea was to add something like t1:o4:m3 to the version. Each number tracks how many breaking changes of a specific kind were made since initial release. It gives the same nice semver property described above, but you even know in what category the change happened. Crucially, all numbers can be increased independent of one another (unlike semver).
In the end, it seemed a bit over-engineered and its actual usefulness was questionable. And then I also had the idea of this release overview table, which has even more useful information at a glance (just not in the version ID itself). So in the end I dropped the idea (and the others didn't mind at all).

 So I will just merge this to finally get this over with.


Refactor setAutoReconnect()

The functionality of setAutoReconnect() will be reworked to give the developer more control over when a container should and should not be reconnected. The new setAutoReconnect() will be defined as follows (the syntax may change in the future).
setAutoReconnect<T extends keyof typeof ReconnectMode>(
    mode: T,
    ...callback: T extends ReconnectMode.Custom ? [() => boolean] : never
): void;

Note about this syntax: If the given mode is ReconnectMode.Custom, then callback is required. If not, then callback not allowed.
We now allow ReconnectMode to be used to set the mode. This was done for a few reasons. First, we want to support the new Custom mode (introduced in https://github.com/microsoft/FluidFramework/issues/9166) which will make use of the callback argument. Secondly, using an enum as the modes will allow us to easily introduce new reconnection modes in the future if we so choose. Lastly, using an enum can help developers more easily understand what they are doing when calling this function.
We are also introducing the callback argument to provide additional control for the developer. This callback function will be required when the mode is set to Custom and will evaluate as a boolean. If the value is true then the container will reconnect, and if false it will not. This allows the developer as mechanism to control when a user is or is not reconnected based on information which the developer has access to, but Fluid does not.
These changes will be reflected in both the Container and ConnectionManager classes.

We are also introducing the callback argument to provide additional control for the developer. This callback function will be required when the mode is set to Custom and will evaluate as a boolean. If the value is true then the container will reconnect, and if false it will not. This allows the developer as mechanism to control when a user is or is not reconnected based on information which the developer has access to, but Fluid does not.

I think what you are trying to say is that developer wants pull model (FF asks it) vs. push model (developer changing auto-reconnect property as new data on his/her side arrives).
Before making API more complex, I'd love to understand why we believe we need to introduce more complexity and allow polling.
I have bigger issues with continuing to introduce these things on Container - I believe things like that should be exposed on Loader object, such that they apply to all containers under same context (here, "context" object is a loader, I do not think we need another context object). That way, it works great for things like guest components, where container points to a component from another container, and thus child container is loaded under same loader - doing operations on one container will miss this kind of scenario).
Developers should have ability to create any number of custom contexts (loader instances) and thus control the scoping of such policies.

This is a good point to consider.
If we do this at a loader level, is it still a natural place to inject callback? (Consider more complex FFX use cases around host apps). Also, maybe elaborate on "information which the developer has access to", so it's clear what those can be.
If the container is disconnected (say for an inactive tab), and you come back to it, what/who initiates reconnections?

I do not understand why callbacks are needed, so I can't answer that question. Access to information does not matter here though, as you can achieve same thing - the question is really why pull model is preferred over push, IMHO, and is this difference warrants more complicated API? Is there an example of scenario demonstrating it? I have not seen one.
Today, in FFX case, I believe OWH code initiates reconnect, I believe they use React capabilities to learn if user is there (any input generated), though I believe browser has similar capability (at global level).

Comments were for @scottn12 to clarify "information which the developer has access to", to understand need for callback. Scott - is this is all around "user inputs"?

Yes, user inputs such as mouse movements or clicks which are not accessible by Fluid. There may also be other relevant information, such as browser tab focus, for example. That said, based on feedback I received we probably won't be refactoring setAutoReconnect() after all, and I'll be updating the main issue shortly.


Provide a "allow reserved close codes" option

Per this conversation with Tobias Oberstein: WebSocket plugin developers and server admins should have a switch which allows reserved+undefined opcodes in the range 1000-2999. This would allow developers to research new official extensions to the protocol.
This switch should default to "off", since most end users of the module will not be doing official development work on RFCs. Additionally, reserved opcodes that are defined as "MUST NOT be set as a status code" should continue to be rejected even if this mode is turned on.

Added in 651ba19a.


Block query failing for frontend on high page number

Issue type

[ x] Bug

Issue Description
Looks like querying for a high page (~ >100000) will cause the block query page to say "No Block"
Description
Link / Screenshot

https://tracker.icon.community/blocks/422478?count=25
Steps to Reproduce the Problem / Desired Outcome

Go to Block page -> Search page 400000

Was just debugging something. No worries


Message context for Yii::t()

I feel that Yii::t() lacks ability to provide context of textual value and when translations start to count in couple hundreds, it starts to be quite hard to understand what was meant with translation.
If we look at popular translation systems like "Crowdin" (example), they allow to provide message context to support translators.
Currently, only way to provide some helpful information using Yii::t() is to write something in "key" area, that in turn defies purpose of "source language", for example, if you write a message "Propose (button in issue tasklist table header)" until I change that translation to "Propose", that message still be visible.
I am guessing, that there is performance issue with long keys, and length limitations does not allow long context descriptions.
For backwards compatability, I would like to suggest 5th optional attribute to Yii::t($category, $message, $params = [], $language = null, $context = null) (but this is not very convenient) that would allow to provide some sort of context description.
Maybe, we could convert Yii::t() to allow passing in first attribute array of attributes, like Yii::t(['category' => 'message.category', 'message' => 'message text', 'params' => [], 'language' => null, 'context' => null]) or even allow shorthand for category and message with numeric keys Yii::t(['message.category', 'message text', 'params' => [], 'language' => null, 'context' => null]).
With \yii\i18n\DbMessageSource, they would be stored in separate table source_message__context, where we would store source message ID and context description with 255 characters long string.
With \yii\i18n\PhpMessageSource, they would be stored in separate file, right next to current message files, in {category}_context.php format, where we would have associative array with source message category as a key, and array with context descriptions, as a value.
I have no experience with \yii\i18n\GettextMessageSource, but I see in their documentation, that they already have an option to provide context descriptions. But I would like to see some suggestions for this solution.
This feature would allow to display all of those context description together with message in interface, to help translator to translate messages and understand context of it.

Getext context is what we know as a category, not an example of usage: https://www.gnu.org/software/gettext/manual/html_node/Contexts.html

I am against such feature.
Placing some descriptive information around any call of Yii::t() sounds like overkill to me.
Besides how we can control same pair of 'category' and 'message' will have same 'context' at all its invocations? For example:
Yii::t('app', 'Some message', [], 'en', 'Some context');
// ...
Yii::t('app', 'Some message', [], 'en', 'Another context!!!');

Each translation message has unique key, which is a combination of category and message.
If you wish to add some description to them you can use this pair and your own custom wrapper.

Agree.

@klimov-paul I don't see arguments about such approach being overkill. I already explained how to control/store them. Each message can have multiple contexts as in your example. Nothing changes regarding identifiers.

OK. If comments are supported in GetText we may introduce it.

Still, I don't think these descriptions are good to be placed right in the code.

I don't see arguments about such approach being overkill.

For me internal program code should not contain such information since it does not influence the program logic. You propose to make source code, which will be executed on each(!) program run much heaiver to support translation functionality, which is performed relatively rare.
Yii::t() function serves the functioality purpose, while yii message command is a service. I do not like the idea to mix up functionality with the service.

Each message can have multiple contexts as in your example

And how it should look like in the end? How it should be stored? What it should mean for the interpreter who will work with translations?
One more thing. What you are planning to do in case your interface for the translations management should also provide i18n feature? This will mean that your 'context' should be translated as well. Otherwise it make not much sense then a plain message ID.

GetText supports comments:

GetText instroduce sperated file per each language. So you mean 'context' may vary per each language in your case?
As far I can see 'context' is something universal through all language translations. Saving context inside GetText will just cause a lot of data duplication.

Don't confuse comments with context/category.

With \yii\i18n\PhpMessageSource, they would be stored in separate file, right next to current message files, in {category}_context.php format, where we would have associative array with source message category as a key, and array with context descriptions, as a value.

I read this and can't find points why the aforementioned is worth than creating a separate dictionary for a specific context, but I see the following cons:

New entity
More code to support
More complexity to Yii::t API (passing 4-th argument after two optional)
More complexity to messages resolving
Need to re-write yii message, as @klimov-paul said in his last message

Therefore I'm standing against this feature request.

xgettext utility works like so:

Comments (starting with ///) placed directly before strings thus marked are made available as hints to translators by helper programs.
https://en.wikipedia.org/wiki/Gettext#Programming

I see the problem having comment in a method call. Couldn't the message parser support some kind of comments markup?
/// Some hint for translators here
echo Yii::t('app', 'Awesome string');

And for inline usage maybe the parser could be smart enough to recognise comment that is inserted immediately after method call?
echo '' . Yii::t('app', 'Awesome string')/* Some hint for translators here */ . '';

@SilverFire so you dislike the idea because it means someone needs to re-write yii message? Or why did you down vote without any comments? All other points from your earlier post has been addressed in this solution.

WordPress uses such approach.
https://developer.wordpress.org/themes/functionality/internationalization/#descriptions
https://develop.svn.wordpress.org/trunk/tools/i18n/extract.php

Or why did you down vote without any comments

I was disturbed while writing a comment. But indeed, @Renkas sorry, I've confused translators comments and context. :unamused:

Anyway I don't really like the opening and closing of this thread in a short amount of time without waiting for answers to open questions. And down voting from Yii core developer without giving a reason after all the issues have been addressed is a very odd move.

We have provided all necessary explanations. We consider this feature is not worth the overcomlication of the code (both yii2 core internal and possible actual project one). We can not accept such changes into the main codebase in near future.
However, you can implement this feature as a separated extension outside the yiisoft scope and use it as you pleased.

@klimov-paul I don't think you read the last posts here ... There's exactly 0 changes to Yii core code. Only thing that needs changing is message extraction and some documentation

So you consider yii\console\controllers\MessageController is not a part of Yii2???

I haven't said that. If it would not be a part of Yii then there would be no point for this thread would it?
But it's not part of core code as you said - core code would run perfectly fine without it. It's an utility - and quite useful one (at least for me). Support for message hints (should be the proper name for this feature I think?) is currently missing from it. And I don't really see why it could not be a part of the default functionality.
Right now it seems you just try to defend the decision on why the issue is closed and are not even thinking about the new proposal. That's not a very productive way of improving anything (which is what software development is all about I think?).
Anyway I'm not going to debate you on this anymore. If Yii team has made up it's mind then so be it. If I really need it I'll implement it myself - just seems like a thing that would probably be useful for lot's of developers.

@Renkas Can't you use actual message as descriptive context? What I mean is, set sourceLanguage to some dummy value, then run message command and translate to language.
'Welcome {user} # some context' => "Welcome {user}"`

Of course this is a possible hack and AFAIK I have seen from forum threads etc some people use it. But it's still kind of a hack.
My projects are all using proper base language as strings as I'm not a fan of this dummy language solution. But that's just my preference ...

I'd like to discuss it a bit more after some thinking. Adding more functionality to message parser isn't a big problem. The problem is not to complicate default usage which doesn't have this context.
Using comments for the purpose looks a bit like hacking to me and, as @klimov-paul said, it adds load to APC/OpCache requiring more memory to store these.
@Deele, @Renkas do you want these comments to appear strictly in the code or you just want them to be there to be filled later?

Me personally would like the possibility to write some hints/explanations to the translators when needed. In my use case I use parser to generate gettext files that are then synced to external translation service and then synced back to my application (overwriting the parsed .po files).
So what I want is a mechanism for the message parser to get these message hints from my application source code and save it to the generated .po file - which will be synced to the external service and the hints will be available there for translators.

These hints are in itself an exception - would only use when really needed - not everywhere.
One problem raised before was if the same message has multiple different hints/comments in different places in code.

My solution would be to append all of them (dividing them clearly of course).
When same string used in multiple places has hint defined only in one place then only that would be used - and there would be no problem

Load on APC/OpCache part seems not to be a real problem. In PHP source you have way more comments anyway. If you mean caching .po files then yes there would be some extra lines - but I think that's quite marginal.

Of course there are other message sources to think about. In PHP message source I think they could be used as PHP comments as well? And in DB message source maybe add a extra column?

The message and category are key fields with limited length and other limitations. I don't want to disturb this behavior, that is why putting more information in category or the message does not really work.  I want separate field, that is not keyed and indexed and could be provided within code.
I agree to @klimov-paul that there is a problem of overhead because of descriptions that are parsed in every code execution. That could be handled with use of comments as @Renkas proposed, but that could become ugly for multiple inline Yii::t() calls and even more ugly for parser to recognize.
If it is not possible to provide context description within code itself, then this feature should be handled separately altogether without changes to Yii::t() with separate table/model/solution (using message/category as the key) and this specific discussion is over.
Another idea is to gather and make available other kind of message context information - where exactly in code that specific Yii::t() is called, so that in interface, it would look like list of file names, class names, method names, line numbers and other information (to be able to create a URL to create clickable reference to repository, if application has one), that could be used by technically advanced translators, to use source code as a guide. This is not really user friendly approach, but could be much easier to implement and would not require any changes to Yii::t() syntax.

I'm against expanding method signature but comments approach looks at least acceptable:

It won't affect code execution much if not used everywhere extensively (number of comments affects how much is saved into memory from APC/OpCache).
It will be backwards compatible.
It would require to change only messages table and the message console command.

Sounds like a plan to me.
@Renkas, @Deele, is that what you want?

@klimov-paul, @SilverFire the approach above seems to not complicate framework much except console command message parser.

The main problem here is a extracted context should be saved somewhere.
Each particular message storage should provide a way to store it.
For the GetText its internal comments feature is proposed to be used. For the PHP and DB it should be defined.
As we have already found out each message may have several context. Thus context should be stored appropriately. For example: for DB there should be an extra table, which will reference as 'many-to-one' to the message table.

@samdark yes that would cover my needs

How will it help a human translator if a unique message has several (different) comments attached to it? I don't get it.

@kidol indeed. @Renkas ?

@kidol so what is the problem with it?
I think i already covered it in:

One problem raised before was if the same message has multiple different hints/comments in different places in code.
My solution would be to append all of them (dividing them clearly of course).
When same string used in multiple places has hint defined only in one place then only that would be used - and there would be no problem

I don't see what is the problem with it? You think that same message in same category could have conflicting hint or what? I dont think that is something that is in the scope of this change. I think that is something that should be handled at the app developers level not in framework.

@Renkas Let's say I do:
 Yii::t('app', "unique message", "context message 1");
...
 Yii::t('app', "unique message", "context message 2");

What's the point in storing context message 2 here? How will it help translator??
This would make sense if context was part of the key, so that translator may choose to do two different translations in target language for a unique message in source language, but that's not what this proposal is about as I understand.
So I see no benefit for translator and thus no benefit to add extra complexity, ie:

For example: for DB there should be an extra table, which will reference as 'many-to-one' to the message table.

@kidol That is the point - same message can have slightly different contexts, but still, same meaning.
To explain why message context is needed at all...
Approach for developer would be:

When there is a new message, he describes in one or two sentences what is the purpose of this text creating new context.
When message is reused, developer checks original message context for similarities (to determine if the same message can be used)

If message is used in the same way as original, the next usage does not require him to add the same context another time
If message context is quite similar, but some clarification is required, developer adds a new context description

For example, the message "call" could be used as "call (the short version of longer "Phone call" in the table header)", "call (of function)" or "(the event of) call". Even thou, in this case, message categories will be different (hopefully), each message will have its own description of context, that helps not only developer to choose whether or not he should create new unique message or reuse existing, but also translator, to choose the best way to translate that text message to another language or request developers to separate those messages in two separate ones, because of invalid usage.

@samdark I already expressed my doubts about comment usage. How would that look like? What exactly would be syntax?
Right next to the rightmost parenthesis
echo '' . Yii::t('app', 'Awesome string')/* Some hint for translators here */ . ' - ' . Yii::t('app', 'Another awesome string')/* Hint for the other string */ . '';
<?php
echo '' .
	Yii::t(
		'app',
		'Awesome string'
	)/* Some hint for translators here */ .
	' - ' .
	Yii::t(
		'app',
		'Another awesome string'
	)/* Hint for the other string */ .
'';

At the end of function call
echo '' . Yii::t('app', 'Awesome string'/* Some hint for translators here */) . ' - ' . Yii::t('app', 'Another awesome string'/* Hint for the other string */) . '';
<?php
echo '' .
	Yii::t(
		'app',
		'Awesome string'
		/* Some hint for translators here */
	) .
	' - ' .
	Yii::t(
		'app',
		'Another awesome string'
		/* Hint for the other string */
	) .
'';

What about spacing before/after comment block? What about \n, \r \t and leading * usage (for PHPDocumentator styled descriptions)? What would be limitations to such messages?

Yes, it's going to get messy but these comments aren't part of the code and I'd like to keep these out of it.

It seems we have no good way to implement it (method signature change isn't desired, comments have issues). At the same time there are categories so contexts could be separated.

What kind of issues there are with comments?
What's wrong with this implementation? https://github.com/yiisoft/yii2/issues/12182#issuecomment-245933148

What kind of issues there are with comments?

https://github.com/yiisoft/yii2/issues/12182#issuecomment-246177890

@samdark Why not support only basic syntax and ignore all weird variations? All these examples could be converted to:
/// Some hint for translators here
echo Yii::t('app', 'Awesome string');

I don't see any issues there.

Any comment that is on the line before Yii::t call is a contextual comment
Any comment that is after Yii::t call is a contextual comment (there should be whitespace between method call and comment.
(optional) Any comment that is after Yii::t call lines semicolon is a contextual comment

Or just go the easiest route and implement only basic syntax like @rob006 suggested. It would still be much better than no support at all.

OK. That actually makes sense. We won't work on it ourselves though since it's very low priority so you may submit a pull request if you need it.

Any plans for these hints to appear in the PhpMessageSource files? If so how to add them? Like this?
'original' => 'translated', // copied hint here

Will modified in-code hint update the source file as well?
In case the content is needed we usually use label approach like
Yii::t('app', 'user.registration.username')

which with forceTranslation set to true works perfectly fine. And the label can be hint of course.
And no additional work is needed.

Like this?

Yes.

Will modified in-code hint update the source file as well?

Ideally yes.

which with forceTranslation set to true works perfectly fine. And the label can be hint of course.
And no additional work is needed.

Yes, it's a good way to solve the issue and it's in the guide.

Post from Trello team mentioning similar context messages: http://tech.trello.com/ios-i18n-designing-for-translators/

зачем контекст передавать, если он указывается в конфиге, юзайте разные категории.
если и хотите запилить передачу контекста, тогда придется убирать translations из i18n, а без них теряется смысл переменных, такие как fileMap для phpsource

@lynicidn the discussion is in English so please stick to using it. Thanks.

@samdark ok, sorry, no problem, wait pr, may be i have wrong opinion

Here is an idea how to solve the problem of passing a hint for translator on how to translate the message.
Yii::t('app', 'Some message text'); // message without hint
Yii::t('app', '[[When translating this message take into account the following ...]]Another message text');  // message with hint

In the example above the [[ and ]] are some user CONFIGURABLE delimiters that mark the beginning and end of the hint for translator. For simplicity, the hint for translator must always appear at the beginning of the message and cannot contain the delimiters inside itself. Of course, the message may contain no hints.
Yii2 engine code impact:

No changes to message extraction machinery or the prototype of Yii::t().
The Yii:t() needs to be modified to check if the message starts with a hint and if so remove it completely before further processing the message (the way it processes it now).
Add the ability for the user to somewhere configure the delimiters for the hint to be used in the message.

You've mixing message itself with a hint in a single string. Usually that's not a good thing to do and in this case, while better than previous options, it isn't as well...

@lynicidn The context is required because you can have message that is related to the same page, form or block, but still, it requires a bit explanation so that translator can understand better the gist of it. For example, when message string contains variables and translator needs to know what sort of thing is meant to go there.
@PowerGamer1 Message string is used as a key to identify message, making it longer just gives bigger overhead for translation lookup procedure.
@samdark To wrap it up from my point of view, this is what script procedure should look like in order of precedence (correct me if I'm wrong):
1. Multi-line comment right after Yii::t(), but before concatenation dot or semicolon
function foo() {
    $variable = 'Lorem ipsum ' .
        Yii::t('dymmy.category', 'Message #1') /* Hint for "dymmy.category:Message #1" */ .
        'dolor sit amet, ' .
        'consectetur ' .
        'adipiscing elit.';
}

Resulting hint:
Hint for "dymmy.category:Message #1"

Multi-line hint (ignoring leading * (leading white-space, star, white-space) prefix like in PHPDocumentator):
function foo() {
    $variable = 'Lorem ipsum ' .
        Yii::t('dymmy.category', 'Message #1') /*
        Hint for "dymmy.category:Message #1".
        Second line of hint for "dymmy.category:Message #1".
        */ .
        'dolor sit amet, ' .
        'consectetur ' .
        'adipiscing elit.';
    $variable = 'Lorem ipsum ' .
        Yii::t('dymmy.category', 'Message #2') /*
         * Hint for "dymmy.category:Message #2".
         * Second line of hint for "dymmy.category:Message #2".
         */ .
        'dolor sit amet, ' .
        'consectetur ' .
        'adipiscing elit.';
}

Resulting hint for dymmy.category:Message #1:
Hint for "dymmy.category:Message #1"\nSecond line of hint for "dymmy.category:Message #1".

Resulting hint for dymmy.category:Message #2:
Hint for "dymmy.category:Message #2"\nSecond line of hint for "dymmy.category:Message #2".

Multi-line hint in HTML/PHP template:

<?= Yii::t('dymmy.category', 'Message #1') /* Hint for "dymmy.category:Message #1" */ ?>

<?= Yii::t('dymmy.category', 'Message #2') /*
    Hint for "dymmy.category:Message #2"
    Second line of hint for "dymmy.category:Message #1".
*/ ?>

Resulting hint for dymmy.category:Message #1:
Hint for "dymmy.category:Message #1"

Resulting hint for dymmy.category:Message #2:
Hint for "dymmy.category:Message #2"\nSecond line of hint for "dymmy.category:Message #2".

2. Single-line comment right after Yii::t() and line ending semicolon
function foo() {
    $variable = Yii::t('dymmy.category', 'Message #1'); // Hint for "dymmy.category:Message #1"
}

Resulting hint:
Hint for "dymmy.category:Message #1"

3. Multi-line comment right after Yii::t() and line ending semicolon
function foo() {
    $variable = Yii::t('dymmy.category', 'Message #1'); /* Hint for "dymmy.category:Message #1" */
}

Resulting hint:
Hint for "dymmy.category:Message #1"

Multi-line hint (ignoring leading * (leading white-space, star, white-space) prefix like in PHPDocumentator):
function foo() {
    $variable = Yii::t('dymmy.category', 'Message #1'); /*
    Hint for "dymmy.category:Message #1".
    Second line of hint for "dymmy.category:Message #1".
    */
    $variable2 = Yii::t('dymmy.category', 'Message #2'); /*
     * Hint for "dymmy.category:Message #2".
     * Second line of hint for "dymmy.category:Message #2".
     */
}

Resulting hint for dymmy.category:Message #1:
Hint for "dymmy.category:Message #1"\nSecond line of hint for "dymmy.category:Message #1".

Resulting hint for dymmy.category:Message #2:
Hint for "dymmy.category:Message #2"\nSecond line of hint for "dymmy.category:Message #2".

4. Single-line comment right after Yii::t() and concatenation dot
function foo() {
    $variable = 'Lorem ipsum ' .
        Yii::t('dymmy.category', 'Message #1') . // Hint for "dymmy.category:Message #1"
        'dolor sit amet, ' .
        'consectetur ' .
        'adipiscing elit.';
}

Resulting hint:
Hint for "dymmy.category:Message #1"

5. Single-line comment in previous line, where Yii::t() was used
function foo() {
    // Some other comment
    // Another comment that is ignored
    // Hint for "dymmy.category:Message #1"
    $variable = Yii::t('dymmy.category', 'Message #1');
}

Resulting hint:
Hint for "dymmy.category:Message #1"

Same hint for all messages that are used in same line
function foo() {
    // Some other comment
    // Another comment that is ignored
    // Hint for "dymmy.category:Message #1" and "dymmy.category:Message #2"
    $variable = 'Lorem ipsum ' . Yii::t('dymmy.category', 'Message #1') . 'dolor sit amet, ' . Yii::t('dymmy.category', 'Message #2') . 'consectetur adipiscing elit.';
}

Resulting hint for dymmy.category:Message #1:
Hint for "dymmy.category:Message #1" and "dymmy.category:Message #2"

Resulting hint for dymmy.category:Message #2:
Hint for "dymmy.category:Message #1" and "dymmy.category:Message #2"

6. Multi-line comment in previous line, where Yii::t() was used
function foo() {
    // Some other comment
    // Another comment that is ignored
    /* Hint for "dymmy.category:Message #1" */
    $variable = Yii::t('dymmy.category', 'Message #1');
}

Resulting hint:
Hint for "dymmy.category:Message #1"

Multi-line hint (ignoring leading * (leading white-space, star, white-space) prefix like in PHPDocumentator):
function foo() {
    /* Ignored comment */
    /*
    Hint for "dymmy.category:Message #1".
    Second line of hint for "dymmy.category:Message #1".
    */
    $variable = Yii::t('dymmy.category', 'Message #1');
    // Ignored comment
    /*
     * Hint for "dymmy.category:Message #2".
     * Second line of hint for "dymmy.category:Message #2".
     */
    $variable = Yii::t('dymmy.category', 'Message #2');
}

Resulting hint for dymmy.category:Message #1:
Hint for "dymmy.category:Message #1"\nSecond line of hint for "dymmy.category:Message #1".

Resulting hint for dymmy.category:Message #2:
Hint for "dymmy.category:Message #2"\nSecond line of hint for "dymmy.category:Message #2".

How about nested Yii::t() calls?

How or why would you nest Yii::t() calls? As far as I understand that's a thing you should never do.

See #8286

Well message parser handles it - couldn't it handle comments as well?
But in a bigger picture I think it's kind of a edge case that is very easy to write in some other way if you need to add context hints.

This long example is a great way of showing how overcomplicated comment hints can become. I would drop this idea in favour of category context mentioned earlier. Or we could always extend signature a bit so category can be optional array with first element being category name itself and second one being a context hint - this way is much easier to track.

I would drop multi-line comment support and everything would be much easier. There's no need to go the route to support every possible comment markup and position. It would be nice but it's not necessary.
These hint's are optional and good practice would be to use them only where needed.

@samdark I disagree for nested calls.
@bizley No, I do not agree that categories are enough for that. They are just like folders and give simple hierarchy while not exactly explaining what variables do or how this text is used.
I think for starters, the 1. Multi-line comment right after Yii::t(), but before concatenation dot or semicolon (ignoring multiple white-space and line endings) would be enough and easiest of all to implement. Others can be added in future, when hints will be already implemented and evaluated by users of framework as a feature.

@Deele nested calls are reality. They're used often:
echo Yii::t('app', 'here is {something}, [
    'something' => Yii::t('app', 'another string'),
]);

@samdark Oh, sorry, I imagined another thing with "nested calls" - yeah, nested calls are reality and used. But the most important thing here is that they do not help to explain, to give hints about context, they just make work of translators even worse - any kind of chopping up messages and creating more of them, or increasing number of variables in messages increase work.

@Deele What about array parameter for category?

@bizley What exactly did you mean by "array parameter", show us example. The only alternative to comments I see - fifth argument for the Yii::t() function, that will require providing optional third and fourth argument.
The problem is that translator never sees the code where that specific Yii::t() is used, so the intention is to allow describing message with both category and description, so that they could be interpreted and translated independently from application developers or code.

@Deele like I said in my comment. Something like:
Yii::t(['app', 'Hint for this'], 'Original text');

@bizley We should avoid changing syntax of existing Yii::t(). I guess, Yii::t() is most used function in any multi-lingual Yii based app, we should avoid adding any more code to it.

I think we have listed here all the caveats. Let's wait now for implementation proposal.


Let's see how long our AppVeyor builds are taking

/cc @iolsen

It looks like we're at about 30 minutes for TASK=installer builds on AppVeyor, and 20 minutes of that is script/build prep. That's much better than the 1 hour 15 minute installer build times we were seeing before. I feel like it's still beneficial to have the build matrix, though.


Calculate full BC artifact URL when updating it

LGTM - Maybe just test it in your fork if you can first. Then.. Ship ship ship 🚢

Seems to work: https://github.com/mazhelez/BCApps/pull/65/files


Remove our use of the stack-sizes tool.

As of version 0.5.0, stack-sizes is no longer a binary crate. This breaks our CI, which tries to install the latest version of the stack-sizes binary.
This PR removes all references to the tool from libtock-rs, so that CI can continue working.
stack-sizes appears to have been replaced by cargo-call-stack, which we may add support for in the future.

bors r+


Adding valuable info to README

Adding hint for Ubuntu (and variants) users which ttf package will help them to see the unicode fonts right.

Thanks for the PR!


Manually set JWT without having to call app.authenticate() on each page reload.

I normally work in React and understand how/why one would call the authentication method on app startup, and then not have to call it again when using client side routing to navigate to a new "page".
But, I am setting up an Express app that renders pages on the server. The pages include JS files that access my Feathers api directly (which is a totally separate server). With that said, each navigation to a new page is a full page reload, thus killing the authenticated instance of the feathers client/auth in the browser.
I know that I can retrieve the token and then api.passport.verifyJWT(token).
Is there any way to manually set the JWT token so that I do not have to call app.authenticate()?

If you are using a REST connection you can manually set params.headers['Authorization'] to the JWT in an application wide before hook:
app.hooks({
  before(context) {
    context.params.headers = Object.assign({
      Authorization: myJWT
    }, context.params.headers);
  }
});

That was the trick! I am using the websocket transport. Thanks for the speedy reply!
I am really loving feathers!

But what if I'm using socket client?


Mailjet adapter

Not 100% ready, some preparations are disabled, but already usable.
I would leave it in open pull requests in case someone needs it.

Hi @denispeplin , I added some changes based on your code. I'd appreciate if you can test the code I added and let me know if everything works.

Looks like it works, but I'll also test it on production next Monday.

Works fine, thanks!
I'm using it like this:
    new()
    |> to({name, email})
    |> bcc({@bcc_name, @bcc_email})
    |> from({"Sender", sender_email()})
    |> subject("Statistics")
    |> html_body("
Statistics
")
    |> text_body("Statistics\n")
    |> attachment(attachment)

And everything I'm using works.

Great, thanks for reporting back. Inline attachments didn't work for me last time I tested. Well, it got attached, but not inlined correctly. Not sure if it's the code or the service. I'll find some time to test again this weekend. The rest seems to work well. We will also need some tests if we want to merge this into master.

Still couldn't get inline attachments to work. Mailjet doesn't seem to do what its documentation says.

But this is not a problem for many users. For me for example :)

I don't mind merging it in without inline attachments working, as long as we put in a comment.
We still need tests though.

I'm working on tests for the adapter. Would you prefer to get a new PR here or should I open a PR for your fork @denispeplin ?

Hi @panmichal you can open a PR towards mailjet branch of this repo.

Here it is: https://github.com/swoosh/swoosh/pull/366

@panmichal, do whatever is easier for you, I don't mind.


removed extra the under Load Balancing rules

@ZER-0-NE : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks.


Recognize file triggers of spec files

https://rpm-software-management.github.io/rpm/manual/file_triggers.html
RPM 4.131 introduces file triggers support, the relavant scriptlets should be highlighted.

@ignatenkobrain


K3s pod not able to access internet which is in different network

Hi,
I have a K3s Cluster master node in the cloud and the worker nodes are Raspberry Pis both of them are in different networks. After deploying applications in the worker node pods cannot access the internet whereas the worker node has the internet. I am doing something wrong or this is expected.
K3s Version: v1.23.3+k3s1
Thanks for help
Ashis

Are you sure that your CNI backend can actually send traffic between the two networks? The default flannel backend is vxlan and is only designed for use between nodes on the same network; this is most likely not going to be successful in passing in-cluster traffic (for example, traffic to the coredns service) between the agent and server when they are not on the same private network.
You might look at using wireguard, or another encrypted tunnel that is suitable for use over the internet.


Fix compilation error caused by unnecessary lifetime placeholders

Attempting to install gluon repl from Cargo currently fails:
error[E0106]: missing lifetime specifier
   --> /Users/kinrany/.cargo/registry/src/github.com-1ecc6299db9ec823/gluon-0.18.1/src/query.rs:808:57
    |
808 | pub(crate) fn env(env: &(dyn Compilation + '_)) -> Env<&'_ CompilerDatabase> {
    |                        -----------------------          ^^ expected named lifetime parameter
    |
    = help: this function's return type contains a borrowed value, but the signature does not say which one of `env`'s 2 lifetimes it is borrowed from
help: consider introducing a named lifetime parameter
    |
808 | pub(crate) fn env<'a>(env: &'a (dyn Compilation + 'a)) -> Env<&'a CompilerDatabase> {
    |                  ++++       ++                    ~~           ~~

System: macOS Monterey 12.1, M1
Rust toolchain: 1.64.0
Gluon repl version: 0.18.0
This PR removes two lifetime placeholders that were preventing the compiler from inferring correct lifetimes.
Note that this makes dyn Compilation have a 'static lifetime.

Closed by #940


Which exact component of this procedure (moving a sub from one dir to another) is in preview ?

Which exact component of this procedure is in preview ?
Or is the entire move of a sub from one dir to another considered "in preview" . This has worked for us several times in the past and we are not sure, why Microsoft now labels it as "preview".
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9afab524-67c2-2e76-fd7a-46238cb9d249
Version Independent ID: ae2da577-6026-f322-1c09-dbcc6068c01a
Content: Transfer an Azure subscription to a different Azure AD directory (Preview)
Content Source: articles/role-based-access-control/transfer-subscription.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@dannradkov
Thanks for your feedback! We will investigate and update as appropriate.

@dannradkov
Looking at the document history, it looks like this has been up for a while, however, the preview should apply to the whole doc. I'll assign this issue to the author to investigate and update as needed.
If you have any other questions in the meantime, please let me know.
Thank you for your time and patience!

Hi @dannradkov
Yes, the preview just applies to the doc.
thanks

#please-close

ok, so its the approach documenter here(consisting of a number of steps), that is in preview. the actual transfer of subs from tenant to tenant is NOT in preview. I am asking , because customers get confused that transferring subs from AAD1 to AAD2 is in preview. Field CSA's like me then have a hard time with this.


FunctionNaming should exclude overridden functions

Expected Behavior
If I override a function, it should not trigger a naming warning, because I have no control over the name.
Current Behavior
It triggers the rule and prints a warning.

I think this should be configurable via property and also apply to PropertyNaming.

Good point. This could either be a configuration option that is enabled by default or it could just be encoded into the rule itself that we always ignore overridden functions.

I agree with @Mauin that this should be the default behavior.


Play inaudible sound every few seconds to keep speakers awake

Description of the new feature / enhancement
A sound file containing some inaudible sound will be played every so many seconds (default to 5 maybe?) so that the connected speakers don't fall asleep. Off by default, could probably be combined with the existing Awake module as a new option. Although, I personally would want the audio awake feature without the screen awake feature being on.
Scenario when this would be used?
Some speakers or drivers have a feature where they will go asleep if no audio is played for a set amount of time. When a sound is then played the speakers or driver takes a few seconds to wake up, and short sounds like notification bells are lost. I'm guessing this exists as an energy saving feature, and on some devices cannot be turned off.
When working from home, it can be important to listen out for notification sounds to know when someone is messaging you. I've definitely ghosted a few fellow devs because I didn't hear the notification from teams.
Supporting information
There are definitely scripts or tools that exist that do this, however their trustworthiness is often in question or people lack the motivation to create the scripts themselves.
Examples of people looking for solutions:

https://www.reddit.com/r/windows/comments/6lpp01/does_anyone_know_of_an_application_that/
https://sound.stackexchange.com/questions/44210/what-is-the-best-way-to-play-inaudible-sound
etc... Can provide more if needed...

I am willing to look at implementing this myself and submit a pull request, but as your guidelines state it's best to create an issue first the get the discussion started.

Didn't know this was a problem.  can you give a brand / model number for one that this occurs? /needinfo

Hey, so possibly a European only issue? My work laptop uses Bang and Olufsen audio drivers which cause the issue, and I know certain speakers have this built into them. (see https://youtu.be/wRXUXmExHuY).
That video mentions some European environmental laws forcing electronic appliances to have an auto sleep function. I could try and track down this legislation if you really need it... I've already begun creating a PoC to see how I could implement this.

Can I get this issue marked as In Progress please?

@Chris-Greaves I don't know if we all agreed to doing this.  I strongly believe in the idea of giving users power over their computers and devices.  I get the pain but not sure i agree with possible solution nor if it belongs in PowerToys since this isn't about doing work and circumventing an environment regulation.
I'm inclined to say having this in your personal repro would be the best spot for a solution.  If you want to use Awake as a base, we're MIT licensed so you are more than welcome to.

I don’t think this is something we will incorporate

I'm in the process of writing my own "Awake" app as well, that will allow you to set multiple devices to keep awake as well as keep the screen awake. I will post it here once done in case anyone finds this again in the future. 😄

Another problem that this feature may fix for me: I connected recently a subwoofer to my external speakers, and now, when you pause or start to play something, there is a loud short noise from the subwoofer triggered by sound card idle/awake status. I agree this may be a speaker issue, but still this feature kind of will help me with the problem.


We want the java implementation for web-socket RIVA speech services

We are using Nemo and RIVA framework for development and deployment of Speech Recognition system for Indic languages. And able to call speech services to other application, now we are trying to integrate RIVA speech services to Jitsi-meet VC solution but facing some issues.
We are also able to get transcription using websocket-bridge of RIVA speech services which implemented in javascriptl.Now we are working with java based jigasi server of Jitsi-meet client for transcription services,but we are not able to get transcription.We want your assistance for Riva transcription implementation using websocket.
Below I am attaching github repository of VoskTrancription service implementation in jigasi.
https://github.com/jitsi/jigasi/blob/master/src/main/java/org/jitsi/jigasi/transcription/VoskTranscriptionService.java

Hi sanhitapatil , I have seen in the above comment that this websocket-bridge is working which is in .js , did you changed any dependencies ?I am getting error when i am running npm install. if possible could you please share me any documentation if you have related to this.


Form validation for exact rule is not working in Form example

Form validation for exact rule is not working in the form example
I've entered the exact same text which is required, but unfortunately, it's not working. Please refer the screenshot below.

Hi @phalvinayak, there’s already a PR for that that’s waiting to be merged: Semantic-Org/Semantic-UI-Docs#312.


fix composer v2 compatibility

With composer v2 you get an fatal error.

@DavidBadura please merge

@DavidBadura please merge

Thank you. I already fixed this in #151 to get github actions working.

Thank you. I already fixed this in #151 to get github actions working.


Add sitemap.xml

Adding a sitemap.xml registered in Google Search Console will improve SEO and indexing.
Unfortunately Readme does not support this BUT we proxy all our traffic using Cloudflare. So, we want to

add a rule into Cloudflare for the explicit route mytiki.com/sitemap.xml
upload a custom sitemap to our hosted CDN
reroute calls to return the hosted sitemap

Can potentially be done using Page Rules, but if not a simple worker will suffice.

done & uploaded to google search console.
https://mytiki.com/sitemap.xml


Header.png

How did you make the strethcy/wavy natural looking BE, PA & JP flags in the Header.png?

Hi!
It's not really out of the box, but the basic is to use a SVG version and scale it up 4x. Then I've used a masking layer and then the a FlagKit SVG and another "effect" layer on top to make the shadowing and highlights. And voilá it's done.
Here is a sketch file with the structure and layers to make it:
https://www.dropbox.com/s/abfsoch5hgbv4c2/Wavy Flag.sketch?dl=0
/m

Brill, shame I'm not doing any iOS/Cocoa development - I'd love to submit a patch to add this as one of the effects :) Will see if I can come up with an NPM tool to convert SVGs with this effect added on!

Was about to ask the same, that effect is wonderful!


TextInput backgroundColor transparency issue

Hello,
I'm having a weird behavior when setting TextInput backgroundColor with transparency, the text gets some kind of background, See Screenshot
I'm using the latest React Native release tested on iOS 12.1
React Native version:
System:
    OS: macOS Mojave 10.14.3
    CPU: (4) x64 Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz
    Memory: 38.39 MB / 8.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 8.16.0 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
  SDKs:
    iOS SDK:
      Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
    Android SDK:
      API Levels: 26, 27, 28
      Build Tools: 26.0.2, 28.0.3
      System Images: android-26 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
  IDEs:
    Xcode: 10.1/10B61 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.4 => 0.61.4
  npmGlobalPackages:
    create-react-native-app: 1.0.0
    react-native-cli: 2.0.1
    react-native-rename: 2.2.2

Steps To Reproduce

create a TextInput
set backgroundColor to '#0006'

Describe what you expected to happen:
I expected to see text without the "highlight"
Snack, code example, screenshot, or link to a repository:
In snack expo it works fine but not in RN
<TextInput style={{height: 50, backgroundColor: '#0006'}}/>
Another user reported this issue #26494 but it was closed for not following the template
I hope this one is accepted and investigated
Thanks in advance.

For solid colors the issue doesn't appear.
For high transparency '#0001' the text background has also high transparency.
What I think is happening is that there's a text container inside the TextInput that is getting the same backgroundColor as the TextInput instead of 'transparent'
It feels like the 2 backgrounds are stacking

A workaround I went for while waiting for a response is to put the TextInput background to transparent and put it inside a view that has the desired transparency

#7964 might give some background on this

The issue #7964 is closed but not solved yet,
I might not know what I'm talking about but I think using transparent background on the text instead of inheriting the background would solve this.

Does it work if you do something like this
<TextInput style={{ backgroundColor: "#0006" }}>
  <Text style={{ backgroundColor: "transparent" }}>
    {yourTextContent}
  </Text>
</TextInput>

Didn't know you could do that ...
I thought TextInput was like me or like an html input tag .. no children
I tried it and It works for normal TextInput but it doesn't for password secureTextEntry={true}

Yeah, so I guess it looks like a RN bug. I suspect it's putting the background colour on the text attributes as well as the text input itself. Is this something you'd want to look into?

If you mean do I want it to be fixed .. then yes
If you mean do I want to fix it I'm afraid I can't, I'm a RN beginner with 0 experience in native Android & iOS
Thanks for the help identifying the issue @jacobp100
I hope this gets fixed

@jacobp100 @Sofianio I would like to take this up if this is not taken.

@jeswinsimon That'd be great! :+1:

This issue seems to be happening in RCTBaseTextInputShadowView.m where background color is also being passed as a textAttribute.
A fix seems to have been already committed by @shergin.

That's good news @jeswinsimon ... any idea when this fix will be public?


compile error

 Compiling rust_app v0.1.0 (/rust_app)
error: linking with `cc` failed: exit status: 1
= note: /usr/bin/ld: cannot find -lpq: No such file or directory

Hey @alenandry, could you try installing diesel_cli first?
Here are the instructions:
http://diesel.rs/guides/getting-started#installing-diesel-cli

hey @alenandry I'm going to close this  but feel free to re-open it if you still need help.
A hint for any visitors in the future:
note: /usr/bin/ld: cannot find -lpq: No such file or directory is indicating that libpq is missing!
One of the requirements for create-rust-app is the diesel_cli which won't work unless you libX (depending on which database you're using) -- see the link I've shared above.


NTR: Dietary fiber

For new term requests, please provide the following information:
Preferred term label
Dietary fiber
Textual definition
Plant material that is resistant to enzymatic digestion.
PMID: 23729846
Suggested parent term
CHEBI:16646 - carbohydrate

Definition clean up.
Not sure how good they could be but I would like to propose some definitions for Dietary fiber:

A plant material that resists enzymatic digestion in humans and other monogastric species

A plant material that resists digestion in the enzymatic digestive system in humans and other monogastric species

A plant material which has resistance to enzymatic digestion in humans and other monogastric species

I got the human and monogastric species concept from Mößeler A., & Kamphues J. 2017.
 The digestive processes in humans and other monogastric species like rat and pig are characterized by a predominantly enzymatic digestion within the small intestine and microbial fermentation located in the hindgut

Another definition suggested by @CropStoreDb
A plant material that resists enzymatic digestion in the digestive systems of humans and other monogastric species.

Another definition suggested by @CropStoreDb
A plant material that resists enzymatic digestion in the digestive systems of humans and other monogastric species.

We think this definition could be more appropriate for CDNO, because plant inheres in the whole ontology and carbohydrate is the "genus" of this definition, according to Seppälä et al., 2017.
A carbohydrate that resists enzymatic digestion in the digestive systems of humans and other monogastric species.
It is also interesting that some lignin can be considered sources of dietary fiber.

We think this definition could be more appropriate for CDNO, because plant inheres in the whole ontology and carbohydrate is the "genus" of this definition, according to Seppälä et al., 2017.
A carbohydrate that resists enzymatic digestion in the digestive systems of humans and other monogastric species.
It is also interesting that some lignin can be considered sources of dietary fiber.


Initial Commit to Upstream repo for the DataDashboard

What this PR changes/adds
This PR brings in the current code base from main in the forked, downstream Datadashboard repository.
Why it does that
To migrate code from newly established downstream repository and provide the base for  Datadashboard
Further Notes

Changes to some of the docs maybe required
Templates are based on those found in the Eclipse-DataspaceConnector Repo
Scaffolding is included
Existing code base from original project is included and expanded upon

closing to fix ECA contributor mismatch on emails


running Save Participants for

VSCode Version:
OS Version:

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

VSCode Version: 1.42.1
OS Version: Windows 10 Home
Steps to Reproduce:

Inside the body section of a .html document, add a  tag with no particular text.
Add a  tag inside the paragraph that encloses at least 1 word.
The doc doesn't seem to save anymore and live server enters in a infinite loop if active.

Does this issue occur when all extensions are disabled?: No
Additional info: the problem stop persisting when the following extension was disabled:
"Auto rename tag" (check the screenshot for more info about the extension).

auto rename tag causing a lot of issues lately.. :'(

@CodingReaction can confirm, disabling the extension "Auto Rename Tag" immediately solved it for me.
VSCode Version: 1.42.1
OS Version: Arch Linux
Kernel Version: 5.5.5

Auto Rename Tag was causing the problem in my case as well.

Please fix, I am not able to work with this $§"!%"$$%§!
Windows10, Latest version of VS, all extensions disabled.
It seems like the good times are over and there we are again in visual studio hell. Loading, waiting and guessing what it could be;)

It happened to me and @CodingReaction comment made it fix. Thank you.

I encounter "Running Save Participants for 'src/styles/global.css': Formatting" when I use HTML in an MDX file. It's seems prettier is having a hard time formatting it, but sometimes can and sometimes can't. And now always takes forever.

I encounter "Running Save Participants for 'src/styles/global.css': Formatting" when I use HTML in an MDX file. It's seems prettier is having a hard time formatting it, but sometimes can and sometimes can't. And now always takes forever.

if you have the auto rename tag extension, then disable it. worst case trying restarting your windows or do an nvram reset on your mac

@teds31 - you're suggestion of restarting the computer seems to be working. I am on mac. I basically restarted everything, and its seems to be behaving.  Thank you.

I'm seeing this issue on macOS Catalina when saving Go files.  I don't have auto rename tag installed and I tried resetting to no avail.

@zebralight I downgraded the Go extension to 0.12.0 and things are working ok again for me. That may be worth a shot.

In addition to the issue that files can't be saved anymore, which can be temporarily fixed by clicking the Cancel button inside the running save participants notification, I have had several occurrences of files getting mixed up with the content of another file when doing a Save all. The files that cannot be saved get contaminated with (parts of) the content of files that can.

Disabling Auto rename tag also fixed this issue for me. Using macOS Catalina.

Got the same issue, without Auto Rename Tag installed, need to investigate issues with other installed plugins though:

So it does not necessarily have to be an extension problem?
Has the problem occurred to someone who did not have any extensions enabled?

The issue is NOT limited to Auto Rename Tag.  I don't use that one.  I have a slow problem if I try to run PHP Code Beautifier.

Since I have uninstalled 'Auto Rename Tag', the problem hasn't occurred for days.
Right now I have tried to import a large (~41k lines) Javascript document into my project and the problem has reappeared.
I have disabled and tested all extensions one by one. The only two extensions where the problem occurred were Prettier and Bracket Pair Colorizer 2, whereas the problem occurred only for a very short time with Prettier and for a very, very long time with Bracket Pair Colorizer 2.
Other extensions, which did not seem to have any negative effects:

Color Highlight
CSS Peek
EJS language support
ES7 React/Redux/GraphQL/React-Native snippets
JavaScript (ES6) code snippets
ESLint
Import Cost
Live Server
Path Intellisense
VSCode React Refactor
React PropTypes Generate
Visual Studio IntelliCode


Confirming email: user sees 'invalid link' message

Current behavior
On dev when confirming email of a new user, user sees 'invalid link' error message
http://activity-dev.hikaya.dev/activate/NQ/5ff-6fe2eea959cd0cb98aee/

To Reproduce
Steps to reproduce the behavior:

User is on dev environment
User registers a new account
User goes to their email account
User clicks on Confirm email button
User sees invalid link error
However when user goes to the login page directly to log in. User is allowed to log in as if the email confirmation worked https://activity-dev.hikaya.dev/

Expected behavior
After clicking 'confirm email' user it directed to the Login page.

@ninetteadhikari This is the current implementation on the activation link, the token generated that is attached to the link for the activation of a user's account, can only be used once. In the first instance, the user will be redirected to the login page. On the second or more click on the link, you receive the message above.


Incorrect padding between the first 2 glyphs of the sample text in the Hiero Bitmap Font Tool

Issue details
In Hiero, the distance between the first two glyphs is reduced (the padding is not applied correctly). This only happens when using the Java or the Native renderer, not when using FreeType. It also only applies to the sample text, not the actual glyph cache.
Reproduction steps/code
Pick a font, set the sample text to ASCII or NEHE and start increasing the left/right padding and the x spacing. The distance between the first two glyphs will increase way more slowly, than between the rest of the glyphs.

This is an example of the issue using Arial with the Java renderer with left padding=8, right padding=6 and spacing x=8.
Version of LibGDX and/or relevant dependencies
Hiero v5
Please select the affected platforms

[ ] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[ ] HTML/GWT
[x] Windows
[ ] Linux
[ ] MacOS

Ok I could visualize what the problem may be but since windows are affected maybe its a bug in the system or a bug in the code


upgrade to jruby-1.7.19

install the newer jruby-1.7.19 version instead.
This commit also extracts the version number to image/ruby_versions
It also uses the canonical jruby mirror.

I like these changes. :+1:
Also: quite minor feedback commentary.

cc @perlun


Display model sources in model overview

It would be nice to see the model sources directly as badge on the models. Git sources shall have a hyperlink to the corresponding Git repository.

My proposal would be:

This is just an initial draft. The real implementation can look different.


Remember the state of collapsed/open menus on home tab

https://github.com/Bitcoin-com/Wallet/pull/101/files


Memory Error (64bit 8gb Ram)

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

```runfile('E:/Recommender vids/RecSys-Materials/RecSys-Materials/Framework/RecsBakeOff.py', wdir='E:/Recommender vids/RecSys-Materials/RecSys-Materials/Framework')
Reloaded modules: MovieLens, Evaluator, EvaluationData, EvaluatedAlgorithm, RecommenderMetrics
Loading movie ratings...

Computing movie popularity ranks so we can measure novelty later...
Estimating biases using als...
Computing the cosine similarity matrix...
Traceback (most recent call last):

  File "<ipython-input-3-491a7f5338b5>", line 1, in <module>
    runfile('E:/Recommender vids/RecSys-Materials/RecSys-Materials/Framework/RecsBakeOff.py', wdir='E:/Recommender vids/RecSys-Materials/RecSys-Materials/Framework')

  File "C:\Users\harrish\Anaconda3\envs\RecSys\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 827, in runfile
    execfile(filename, namespace)

  File "C:\Users\harrish\Anaconda3\envs\RecSys\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 110, in execfile
    exec(compile(f.read(), filename, 'exec'), namespace)

  File "E:/Recommender vids/RecSys-Materials/RecSys-Materials/Framework/RecsBakeOff.py", line 31, in <module>
    evaluator = Evaluator(evaluationData, rankings)

  File "E:\Recommender vids\RecSys-Materials\RecSys-Materials\Framework\Evaluator.py", line 15, in __init__
    ed = EvaluationData(dataset, rankings)

  File "E:\Recommender vids\RecSys-Materials\RecSys-Materials\Framework\EvaluationData.py", line 36, in __init__
    self.simsAlgo.fit(self.fullTrainSet)

  File "C:\Users\harrish\Anaconda3\envs\RecSys\lib\site-packages\surprise\prediction_algorithms\knns.py", line 281, in fit
    self.sim = self.compute_similarities()

  File "C:\Users\harrish\Anaconda3\envs\RecSys\lib\site-packages\surprise\prediction_algorithms\algo_base.py", line 293, in compute_similarities
    sim = construction_func[name](*args)

  File "surprise/similarities.pyx", line 72, in surprise.similarities.cosine

MemoryError

## Versions
<!--- You can get this information from Help > About Spyder...
or (if Spyder won't launch) the "conda list" command
from the Anaconda Prompt/Terminal/command line. --->

* Spyder version:
* Python version:
* Qt version:
* PyQt version:
* Operating System name/version:

### Dependencies
<!--- Please go to the menu entry Help > Dependencies,
press the Copy to clipboard button and paste below --->

PASTE DEPENDENCIES HERE

That's a problem with your code, not with Spyder. I think your system went out of memory.


Improve installation on kokoro macos

a few more fixes

Only affects kokoro, merging.

This has broken sanity on kokoro.

@dgquintas   no it hasn't.
It was actually broken by https://github.com/grpc/grpc/pull/11374/files
Right now, whenever someone changes the testing Dockerfile(s), the testing images need to be pushed to dockerhub by `tools/dockerfile/push_testing_images.sh' script (because kokoro recreates VMs for every build, we can't cache the dockerimages after they get build for the first time, so to avoid spending hours building the testing dockers imgs, we push the to dockerhub instead of caching).


docker

this error is coming how to resolve this

i am working on ubuntu 22 and having cuda 12.3


Move day-to-day development to master branch

Just a thought: people have often to be reminded to use the develop branch instead of master, so maybe it makes sense to branch off master as master-1.8 and merge develop into master and start using master instead of develop.
Wireshark does it like this:

All new commits are rebased unto master. This removes the merge commit and keeps commit history linear. Patch discussion is linked in the commit message. On Github we could use the squash button for pull requests, to automatically add a reference to the pull request and git rid of the merge commit (and manually rewrite commit message, if need be)
Version of master is odd. README links to where the most recent stable version can be downloaded, which is even
When a new stable version is due to come out, master is branched off as the next even version, e.g. master-1.8. This branch only gets bug fixes if required

Downside is occasional breakage for unexpecting people. Upside is they get the newest version and can report those breakages. Thoughts?
Also, is there a way to alias develop and master, so people don't need to update their tracking branches?

But being broken is good. With the increasing number of binary packages available (whether uploaded manually here, built by CI or in third-party package managers), users don't have to build raylib, except if they need the newest version. And if that version is broken, they are able to report it sooner.
Users that want to build a stable version just need to checkout the most recent release and build it themselves.

Hi @a3f, I decided to close develop branch and move development to master branch as proposed.
My main concern is all the places (documentation, forums, gitter...) that link to develop branch files, did you investigate what happens to those links, is there any alias possibility? links get broken?

I think there isn't. Maybe merge develop into master, delete files in develop and a last commit with a README that says

Development moved to master branch, please updating tracking branches and documentation

After lot of thinking and some reading, just deleted develop branch: https://github.com/raysan5/raylib/pull/474#event-1480330270
Let's see what happens from now on.


Can I specify a callback function for when the file is successfully uploaded?

Thanks
C

You can use an EventEmitter for that case, I think.


how to restart rutorrent

How do I  restart rutorrent service?

ruTorrent is a PHP frontend/web interface hosted by Nginx web server, so there isn't any specific service for it.
You can restart Nginx web server, but that shouldn't do much of a difference if you are having issues... What's the issue? Rebooting the device usually do wonders. Otherwise, go over the configurations and if that doesn't help, re-install both rTorrent/ruTorrent.
sudo systemctl restart nginx.service

How do I restart rutorrent service?

If at all you are looking to restart rtorrent use - rt restart
Use as non-root user (I hope you know username and remember SSH port which was changed during rutorrent installation) and no need to use sudo or anything.


Add an intersect service

Creating a lot of IntersectionObserver instance can have a negative impact on performances (see https://www.bennadel.com/blog/3954-intersectionobserver-api-performance-many-vs-shared-in-angular-11-0-5.htm). We could create a new service called intersect which would create a minimum amount of IntersectionObserver instances.
import { useIntersect } from '@studiometa/js-toolkit';

const intersect = useIntersect();

intersect.add('a', (entries) => {}, {
  target: document.body,
  rootMargin: '50%',
})

// Will use the same `IntersectionObserver` instance as the previous one as they have the same `rootMargin` option
intersect.add('b', (entries) => {}, {
  target: document.querySelectorAll('div'),
  rootMargin: '50%',
});

Its type could be:
interface IntersectServiceOptions extends IntersectionObserverInit {
  target: HTMLElement;
}

interface IntersectService<T extends HTMLElement> {
  add: (key:string, callback: (IntersectionObserverEntry[]) => void, options: IntersectServiceOptions<T>) => void;
  remove: (key:string) => void;
  has: (key:string) => void;
  props: () => { target: T, entries: IntersectionObserverEntry[] };
}

This might be a complex feature with little to no benefits (see Twitter discussion), closing for now.


Question regarding images in tutorials

Good morning,
In several places in the sap-conversational-ai tutorials, the screen images vary from the current state of the user interface. Mostly the differences are very minor - in others the terminology has changed or the highlighted buttons have moved to another place.
Would you like issues to be created for the more significant ones? and would it be helpful if the current screen image were provided?
Regards
Andrew Barnard

We will have some complete review of all the tutorials at some point this year to update them as best we can. Thanlks for keeping an eye out, though :-)


Make output columns customizable

This PR adds a new flag that lets one define what columns should be shown. For example:
$ swift run -c release BenchmarkMinimalExample --columns name,time.min,time.p50,time.max,iterations.div.time.total
running add string no capacity... done! (1857.03 ms)
running add string reserved capacity... done! (1845.22 ms)

name                         time (min) time (p50) time (max) iterations / time (total)
---------------------------------------------------------------------------------------
add string no capacity       39616.0 ns 40084.0 ns 98983.0 ns 24859.897253858646 /s
add string reserved capacity 39677.0 ns 39738.0 ns 78210.0 ns 25110.825638452126 /s

A brief overview of features:

It supports time, warmupTime, iterations and any user-defined counters via counter.$name.

Time measurements can be aggregated using following suffixes: .min, .max, .pN, .pN_N, .median, .avg, .total.

Counters (iterations and user defined counter.$name) can be divided by time via .div. binary operator to obtain throughput rates / second. For example ML benchmarks might define examples counter and then use counter.examples.div.time.total to get examples/second.

Divided results can be shown as percentage as well by adding percentage. prefix.

Columns automatically infer their unit as: time, inverse time, percentage, or without any unit (counters and iterations).

Inverse time unit can be customized via --inverse-time-unit s/ms/us/ns, with default of seconds. This is convenient because columns that are obtained through division automatically show result as throughput per second.

Columns can be renamed with custom names via $name= prefix before the column definition. For example:

$ swift run -c release BenchmarkMinimalExample --columns name,min=time.min,max=time.max
running add string no capacity... done! (1855.28 ms)
running add string reserved capacity... done! (1844.78 ms)

name                         min        max
--------------------------------------------------
add string no capacity       40028.0 ns 87857.0 ns
add string reserved capacity 39672.0 ns 83122.0 ns

Columns can be aligned either to left or to the right by using ":" as a prefix (left align) or a suffix (right align). For example --columns :time.min,time.max: will have min column be left-align, and max column be right-aligned.

Fixes #15

This PR depends on #39, #41.

3afd87a replaces previous column expression mini language with Swift-defined registry of known columns. It provides similar expressivity with much simpler implementation.


Internal Server Error on League Signup

I had a 1-3 run that I retired, and now I can no longer signup for a league.  I have been trying a new decklist, but it wouldn't let met signup with a previous list either.  In both cases I get "Internal Server Error"

Working now (5:32pm EST 11/16)


ARROW-3841: [C++] Suppress catching polymorphic type by value warning

../src/arrow/compute/compute-test.cc: In member function 'virtual void arrow::compute::TestCast_StringToNumber_Test::TestBody()':
../src/arrow/compute/compute-test.cc:917:17: warning: catching polymorphic type 'class std::runtime_error' by value [-Wcatch-value=]
   } catch (std::runtime_error) {
                 ^~~~~~~~~~~~~

Codecov Report

Merging #3003 into master will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3003      +/-   ##
==========================================
- Coverage   87.72%   87.66%   -0.06%
==========================================
  Files         435      423      -12
  Lines       65832    64021    -1811
==========================================
- Hits        57750    56125    -1625
+ Misses       8082     7896     -186

Impacted Files
Coverage Δ

cpp/src/arrow/util/parsing-util-test.cc
99.33% <ø> (ø)
:arrow_up:

cpp/src/arrow/compute/compute-test.cc
99.36% <ø> (ø)
:arrow_up:

cpp/src/arrow/csv/column-builder.cc
95.3% <0%> (-2.02%)
:arrow_down:

cpp/src/plasma/thirdparty/ae/ae.c
72.03% <0%> (-0.95%)
:arrow_down:

rust/src/record_batch.rs

rust/src/array.rs

rust/src/bitmap.rs

rust/src/util/bit_util.rs

rust/src/error.rs

rust/src/memory.rs

... and 6 more

Continue to review full report at Codecov.

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


Visual Studio 2019 Support

Is some plan to give support to Visual studio 2019? Thanks for reply.

Is some plan to give support to Visual studio 2019? Thanks for reply.

I would like to know that too

We need to update the VSIX. I don't have plans to update this project right now. That being said, I have my own UWP apps that I want to use Template 10 with, too. So, maybe. Sorry to be unclear.


run documentation typo?

run count Mouse.clicks seems to be missing an argument, e.g.,
run count 0 Mouse.clicks

Yes, you are right.

PR?


No response error in Home App

On / off button no longer works for http connected purifier. Nothing in home bridge logs except:
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Active': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Current Air Purifier State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Target Air Purifier State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Lock Physical Controls': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Rotation Speed': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Air Quality': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'PM2.5 Density': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Filter Change Indication': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Filter Life Level': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Filter Change Indication': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Filter Life Level': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Filter Change Indication': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Filter Life Level': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Target Air Purifier State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Lock Physical Controls': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Active': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Rotation Speed': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Current Air Purifier State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:35] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Air Quality': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:38] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Current Air Purifier State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:38] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Rotation Speed': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:38] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Target Air Purifier State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:38] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Lock Physical Controls': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:38] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Active': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:38] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Air Quality': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:40] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Target Air Purifier State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:40] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Lock Physical Controls': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:40] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Active': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:40] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Rotation Speed': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:40] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Current Air Purifier State': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.
[02/04/2021, 10:42:40] [homebridge-philips-air] This plugin generated a warning from the characteristic 'Air Quality': characteristic value expected valid finite number and received "undefined" (undefined). See https://git.io/JtMGR for more info.

Rolling back to version 2.3.2 fixed this error and the device now responds again. Something about a more recent version broke any controls in the Home app for my http and COAP purifier. Rolling back I can now at least use the HTTP purifier no problem

Excellent!
You can use 2.3.2 ver.
I cannot test all these models and protocols. I only have model AC3829

Aha ok. I thought you might want to know that something about the recent updates has broken Http functionality for some models, but never mind

Aha ok. I thought you might want to know that something about the recent updates has broken Http functionality for some models, but never mind

Thanks fro inform :)
My friend has a model with http protocol and it works fine with ver. 3.1

@mj16792 HI!
Try to install new version of plugin.

Still no luck :/

Still no luck :/

Show me you logs, please with debug and without debug mode.
Are you using http protocol?

@NikDevx
After downgrading the plugin & restarting homebridge it seems to work again. Thanks for the workaround!

@NikDevx
After downgrading the plugin & restarting homebridge it seems to work again. Thanks for the workaround!

The version above 2.3.2 has improvements only for humidifier.
If you only have a purifier without a humidifier function you need to install version 2.3.2.

So there still isn’t a way to run a http and COAP purifier using the same version?
I’m asking as one of mine is http and the other is coap. On the latest version neither my http nor coap purifier would work properly.

So there still isn’t a way to run a http and COAP purifier using the same version?
I’m asking as one of mine is http and the other is coap. On the latest version neither my http nor coap purifier would work properly.

What's the problem run all devices on version 2.3.2?
2.3.2 supports http and coap


Query listings for entire state

I've tested with multiple cities, and the total count in the csv matches with with the count on realtor.com (Select Hide Pending/Contigent)
However, when I tried to query for entire state, the count in the csv is significantly lower than on realtor.com.
Example:
For state CA:  From HomeHarvest csv < 10,000 listings
On Realtor.com: 78,097 listings
I've tested with other states too, but same observation

The max results are 10k, use filters such as date from and to, or past days to paginate.


Inquiry on Potential Gas or Security Issues for Large Supply Collections

Hello,
I'm considering creating a collection with a supply of 100,000 items and wanted to consult on whether this could potentially lead to any issues regarding gas fees or security within the collection. Specifically, I'm concerned about whether such a large supply might cause transactions to become excessively expensive or if there are any security vulnerabilities that could arise from managing a collection of this size. Additionally, is there a risk of the collection's transactions getting stuck or failing due to the high number of items?
Could you please advise on any best practices or considerations I should be aware of to avoid potential issues with gas costs, security, or transaction reliability for a collection of this magnitude?
Thank you for your assistance.

100k should be fine, provided _useExistsLookup() is left as default, returning true.


Implement login

This is a temporary solution, waiting for the IAM documentation and Realm API to be implemented.

What's been added?
Login Box component (with ability to choose Realm)

Login link in header (only if 1+ realms available)

Redux store + react rouder redux connector

Please use "squash and merge" for this one once approved.


chore(dependabot): schedule time

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


[Sprint: 50] XD-3131 Disable tap listener for spark streaming plugin

This avoids the creation of the curator pathchildren cache thread for Taplistener when the
SparkStreamingPlugin is initialized

Pushed the change.

Rebased, squashed & merged as 7d19adcf9302c2f58ec95c7ecacb70166387d88a

@pperalta This change needs to be cherry-picked and pushed to 1.1.x as well

Cherry-picked to 1.1.x as 1009a00764235d2a72682edc352d91f20d796ae8

@pperalta thank you!


Create _index.md

Just uploaded my profile picture.

I think you're almost there, but you have a few more < and > characters to remove. On line 36 try removing the wors "LINK TO YOUR GITHUB e.g. " so it looks like
  link: https://github.com/Sparisa

Then at the bottom of the page replace
user_groups:
- committee: members
  role: <PROJECT XXX MEMBER e.g. ATCO Project member>
---
<ADD A DESCRIPTION HERE, USE MARKDOWN SYNTAX>

with something like
user_groups:
- committee: members
  role: ATCO Project Member
---

When you're done. Hit commit and I think it should be ready to go.

Your image file was in the wrong location so I've renamed it and I've made a couple of tweaks to your _index.md file so you can see what it looks like. Can you take a look at the deploy preview and let me know if it is OK. If it is OK I can merge the changes in, if not you can keep making commits here to update it. You might want to replace "PROJECT Member" with the name of the project you're working in.

That looks great, thank you! I'll merge it now.


URGH!!!

Firstly, the if/else if/ else stateents aren't working
secondly, It starts the game as soon as the page loads
thirdly, I still need a way to exit the function if adventureStart === no.
SOMEBODY HELP ME

RESOLVED


Track model iteration4

Added in message directly to train controller for the transit light status. Keegans code should be working, he will need to change his setState({authority: payload.Authority}) to
this.state.authority = payload.Authortity;  inside of his subscribe message function. Also note for accessing signals sent from the track model:
Signal type will be 'trackModelStatus'
look at the TrackModel.jsx file for specific attributes being sent in sendMessages() function (control f).
~names will be easy to mess up, reference my code in TrackModel.jsx so not to get it messed up
Access an attribute with payload.AttributeName like any object

I don't think i need transit light status
so maybe remove that before  you merge

I don't think i need transit light status so maybe remove that before you merge

Didn't you just ask for this a few minutes ago?


GetFeatureinfo not passing FEATURE_COUNT

I had issues with mapproxy not passing this parameter to backend wms. Problem is present in both 1.7.1 and 1.8.0a nightly. #11 probably includes an attempt to fix this but I had to do one additional change in client/wms.py line 145 (tested in 1.8.0a nightly)
info_query = InfoQuery(info_bbox, query.size, info_srs, info_pos, query.info_format, feature_count=query.feature_count)

Thanks for the report. It was not implemented for feature info requests that were transformed to another projection.


[BUG] Error executing tool ToolInputParsingException [Error]: Received tool input did not match expected schema

As the title says, I don't know if this is limited to my instance, but I have a particular issue with the OpenAI Assistant and custom tools steps.
I have a total of three custom tools that I configured with the correct name, parameters, and JavaScript to send the data to the webhook URL. When the Assistant initiates the function calling, I get the error below, which I am trying to figure out to see how I can solve it.
Does anybody know how to solve this?

I have attached the error log screenshot.

this is not an instance issue, its custom tool. OpenAI Assistant does not givee the correct input arguments to the custom tool, hence causing the error. If you use OpenAI Function Agent, do you face the same problem?


CAMEL-12665 - Apache Pulsar integration via component

Adds a component for Apache Pulsar integration and example of use via spring.

This should be the camel-2.x branch and not 2.20.x. Also make sure to update the pom.xml with the correct Camel version, see the other pom.xml files what version they have.

ok sorry let me cherry-pick onto camel-2.x branch instead - too many branches to keep track of!


Add support for latest OpenNext

This PR add support for the latest OpenNext

Bumps OpenNext to 3.0.0-rc.16
Add support for request.geo in the middleware
Add support for static image optimization
Improve cache hit ratio with a custom cloudfront functions to compute a custom cache key depending on the path

Thanks @conico974 I just renamed imageOptimization.staticImageOptimization to imageOptimization.staticEtag. Sounds less wordy and naming aligns w/ the ON doc.
But lemme know if staticEtag is not a good name.


update dependencies

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

I'll merge, but note the Mac os Intel issues remain. (Still under investigation)