text:
Using the N1MM ID field for the duplicate QSO detection

N1MM now sends an ID in the contacting record. This appears to be a 32 byte GUID. I suggest that the duplicate detection can be simplified to use the ID to lookup the contact. This is important because the duplicate table is made up of the following fields:
def checksum(data):
    """
    generate a unique ID for each QSO.
    this is using md5 rather than crc32 because it is hoped that md5 will have less collisions.
    """
    hval = data['timestamp'] + data['rxfreq'] + data['txfreq'] + data['operator'] + data['mode'] + data['call']
    return int(hashlib.md5(hval.encode()).hexdigest(), 16)

But the deletes record from N1MM does not send everything in the hash.
From the N1MM UDP Documentation:
<?xml version="1.0" encoding="utf-8"?>
<contactdelete>
    <app>N1MM</app>
    <timestamp>2020-01-17 16 :43:38</timestamp>
    <call>WlAW</call>
    <contestnr>73</contestnr>
    <StationName>CONTEST-PC</StationName>
    <ID>a1b2c3d4e5f6g7h</ID>
</contactdelete>

So when a contact is corrected and N1MM sends the contact delete and then contact replace, the collector cannot delete the entry from the duplicates hash table.
If it uses the ID field, then it can be deleted.
If it is not deleted, when N1MM sends the contact replace packet (which has the same fields as contactinfo, it would flag as a duplicate unless the timestamp of the contact or callsign were changed.
So by just using ID for duplicates detection, it would allow the deletion/replace change process to work.
Where this is really important is that if N1MM resends all the contacts to UDP, it sends out contact delete and contact replace packets.
This is the sequence sent by N1MM on a rebroadcast:
'<?xml version="1.0" encoding="utf-8"?>\r<contactdelete>\r\t<app>N1MM</app>\r\t<timestamp>2022-06-27 19:45:53</timestamp>\r\t<call>W2IU</call>\r\t<contestnr>22</contestnr>\r\t<StationName>DESKTOP-4K20B9M</StationName>\r\t<ID>fcbdeb9c-c69d-4479-90b1-2944b6cd76be</ID>\r</contactdelete>

2022-06-27 19:59:36.086 INFO     DELETEQSO: W2IU, timestamp = 1656359153
Then it sends the contact replace
<?xml version="1.0" encoding="utf-8"?>\r<contactreplace>\r\t<app>N1MM</app>\r\t<contestname>FD</contestname>\r\t<contestnr>22</contestnr>\r\t<timestamp>2022-06-27 19:45:53</timestamp>\r\t<mycall>W4TA</mycall>\r\t<band>14</band>\r\t<rxfreq>1420000</rxfreq>\r\t<txfreq>1420000</txfreq>\r\t<operator>NY4I</operator>\r\t<mode>USB</mode>\r\t<call>W2IU</call>\r\t<countryprefix>K</countryprefix>\r\t<wpxprefix>W2</wpxprefix>\r\t<stationprefix>W4TA</stationprefix>\r\t<continent>NA</continent>\r\t<snt>59</snt>\r\t<sntnr>2</sntnr>\r\t<rcv>59</rcv>\r\t<rcvnr>0</rcvnr>\r\t<gridsquare> </gridsquare>\r\t<exchange1>1E</exchange1>\r\t
NLI
\r\t<comment></comment>\r\t<qth></qth>\r\t<name></name>\r\t<power></power>\r\t<misctext> </misctext>\r\t<zone>5</zone>\r\t<prec></prec>\r\t<ck>0</ck>\r\t<ismultiplier1>0</ismultiplier1>\r\t<ismultiplier2>0</ismultiplier2>\r\t<ismultiplier3>0</ismultiplier3>\r\t<points>1</points>\r\t<radionr>1</radionr>\r\t<run1run2>1</run1run2>\r\t<RoverLocation> </RoverLocation>\r\t<RadioInterfaced>0</RadioInterfaced>\r\t<NetworkedCompNr>0</NetworkedCompNr>\r\t<IsOriginal>True</IsOriginal>\r\t<NetBiosName>DESKTOP-4K20B9M</NetBiosName>\r\t<IsRunQSO>0</IsRunQSO>\r\t<StationName>DESKTOP-4K20B9M</StationName>\r\t<ID>fcbdeb9cc69d447990b12944b6cd76be</ID>\r\t<IsClaimedQso>1</IsClaimedQso>\r</contactreplace>

And then in the collector log, we get a duplicate message because the item was not deleted upon the contact delete.
2022-06-27 19:59:36.118 DEBUG    duplicate message

I'm glad to code this up but wanted to see if you agree Jeff before I do.

This sounds great to me.  Calculating the hash is way more expensive than simple string comparison, so this sounds like a win.  Please proceed.

This seems timely as Tom sent out a notification this morning stating that as of July 5 build, the  message will no longer be sent and it is now advisable to use GUID to identify rows.

Yes that was my doing. I noticed the packets came out of order so the combination of contact delete/replace and the seen set were not very useful. The ID GUID allows it to work better.  After discussing it with the team, they opted to skip the delete/replace sequence since that predated the ID GUID.
My thought was that double packets are rare so I just change the database code to do an INSERT or REPLACE and made ID NOT NULL and UNIQUE.
I am just using the database as the duplicate detection mechanism as seen did not seem to be adding anything. Again, simply because in my experience, double messages are rare (unless one does a rebroadcast or has one station set to Broadcast All). The overhead is not too great in that case.
cursor.execute(
'insert or replace into qso_log \n'
'    (timestamp, mycall, band_id, mode_id, operator_id, station_id , rx_freq, tx_freq, \n'
'     callsign, rst_sent, rst_recv, exchange, section, comment, msgID)\n'
'    values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?);',
(calendar.timegm(timestamp), mycall, band_id, mode_id, operator_id, station_id, rx_freq, tx_freq,
callsign, rst_sent, rst_recv, exchange, section, comment, msgID))
I have some significant changed in thew works to support all of this. I am finalizing my testing and will have a pull request by the weekend.
Tom NY4I

On Jun 29, 2022, at 8:50 AM, KD4Z @.***> wrote:
This seems timely as Tom sent out a notification this morning stating that as of July 5 build, the message will no longer be sent and it is now advisable to use GUID to identify rows.
—
Reply to this email directly, view it on GitHub https://github.com/n1kdo/n1mm_view/issues/39#issuecomment-1169940359, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6TWSW2RODO7S5CULXP3GDVRRBBDANCNFSM5Z7UWHRQ.
You are receiving this because you authored the thread.

I looked at your branch.  Can you name the new column 'n1mm_id' or 'qso_id' because I don't think it is really the msgID.
Otherwise I like it.  Thank you!  Jeff

Sure
Principal Solutions Architect
Better Software Solutions, Inc.
727-437-2771

On Jul 1, 2022, at 1:19 PM, Jeff Otterson @.***> wrote:

I looked at your branch. Can you name the new column 'n1mm_id' or 'qso_id' because I don't think it is really the msgID.
Otherwise I like it. Thank you! Jeff
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

Just an update. We are moving so I have this code but have to complete its testing. I will get to that after we move in September or October. It will be done well in time for Winter Field Day.

Winter Field Day is coming!  I hope your move went well, Tom.
One of the changes I am going to add at some time is the ability to control which displays are shown.  Feedback from one local club is that they were interested in the raw scores, but not so much the per-operator scores.  Personally, I like the per-operator scores, but the plan is to make which panels are shown (and perhaps for how long) configurable.
73, Happy New Year.

Hi. I was just thinking about this project as I found my PC after misplacing it.
That sounds like a great change. I will take a look this weekend to catch up on what I was working on before I moved.
Thanks,
Tom

On Dec 31, 2022, at 2:24 PM, Jeff Otterson @.***> wrote:
Winter Field Day is coming! I hope your move went well, Tom.
One of the changes I am going to add at some time is the ability to control which displays are shown. Feedback from one local club is that they were interested in the raw scores, but not so much the per-operator scores. Personally, I like the per-operator scores, but the plan is to make which panels are shown (and perhaps for how long) configurable.
73, Happy New Year.
—
Reply to this email directly, view it on GitHub https://github.com/n1kdo/n1mm_view/issues/39#issuecomment-1368268411, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6TWSWRI5ZDVTVZLWJO47TWQCB6JANCNFSM5Z7UWHRQ.
You are receiving this because you authored the thread.

Thank you for your code contribution.  This issue seems to now be fixed.


text:
🛑 peertube is down

In 0b0a382, peertube (https://peertube.n1l.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: peertube is back up in 24615b0 after 1 hour, 28 minutes.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Fix for annotation paths

I think in the commit of issue #28 there's a little bug. postcss needs the path for the annotation relative to the stylesheet that is output but  grunt.file.write writes relative to grunt working directory.
In addition I have added the possibility to set the annotation either to a sourcemap filename (as postcss's default behavior) or a directory (path ends with ’’/’’ for use with multiple source files).

Thanks for the first fix, but I won't merge this PR because of the second change. I think it is better to provide only the possibility to specify a directory for annotation because Grunt is a build tool and this kind of tools created to manage many files at once, so I believe nobody wants to specify a unique filename for each one. Also from users point of view we've got here two possible string options inside one that is complex even now and that's bad.

I did this second change from a users point of view. As options are passed through, users will often look at the documentation of postcss instead of grunt-postcss. If they do so and specify e.g.
path/to/mystyle.css.map

as annotation they end up with a source map at
path/to/mystyle.css.map/styles.css.map

which is certainly not intended and could be quite confusing. So i thought it would be a good idea to match postcss's behavior as close as possible and just extend it for special grunt tool use.
What do you think? Or should I add a commit to revert to the old behavior?

Ok I'll think about it, can't say right now.

Ok, I wait for green or red lights then :vertical_traffic_light:

I split this up into two different PRs #32 and #33 (as I should have done in the beginning, sorry) so that the bugfix part can be merged as fast as possible.

source: gharchive/pull-request

authors: nDmitry rarila

repo: nDmitry/grunt-postcss

license: mit

license_source: bigquery


text:
Requirements docs are misleading (or not correct)

Requirements section of the docs is probably taken from another repository https://nwidart.com/laravel-menus/v1/requirements
https://nwidart.com/laravel-modules/v2/requirements

Good catch, thanks! Fixed. 👍

authors: Kyslik nWidart

repo: nWidart/laravel-modules


text:
swagger documentation

hello
how can I do the integration with the library l5-swagger to document each module

Hi,
I haven't used that package so I can't help you with that.
Though I assume like explained on their documentation.

I'll close this as there hasn't been a reply in a while, feel free to comment if needed.

I'm using swagger package but unable to integrate with each module in Laravel 6

Hi,
You can make it in swagger's config.
'annotations' => [
            base_path('app'),
            base_path('Modules'),
        ],

How about scribe?

authors: JHONF2078 nWidart serkansahinn unaveen zkenstein


text:
How to use json translation files using modules? (Translation Strings As Keys)

I want to use translation strings as key, how to do it in laravel modules?
https://laravel.com/docs/6.x/localization#using-translation-strings-as-keys
I've tried adding the json file to modules lang folder. e.g. Modules\ModuleName\Resources\lang\id.json but laravel doesn't read it.
Does laravel modules support Translation Strings As Keys? (Not short key translation).
Thanks

Hi @dexcell,
This package can help you => laravel-json-translation-loader

@JamesHemery
Thank you! i will have a look at it

I'll close this as there hasn't been a reply in a while, feel free to comment if needed.

Unfortunately there is still no solution for this.

This is not related to this package as far as I can see. Users can choose to do this however they prefer.

Hi thank you for the reply,
I'm sorry i have to a bit disagree, i think laravel modules should support default laravel translation out of the box.
Since default laravel offers translation strings as keys, then i want to use it inside the modules just like normal laravel app. (isn't that the purpose of laravel modules?).
For now i managed to load the json translation manually by adding loadJsonTranslationsFrom inside registerTranslation function in service provider file.
I hope the generator would done this automatically (e.g php artisan module:make ModuleName)
/**
     * Register translations.
     *
     * @return void
     */
    public function registerTranslations()
    {
        $langPath = resource_path('lang/modules/modulename');

        if (is_dir($langPath)) {
            $this->loadTranslationsFrom($langPath, 'modulename');
            $this->loadJsonTranslationsFrom($langPath);
        } else {
            $this->loadTranslationsFrom(module_path('ModuleName', 'Resources/lang'), 'modulename');
            $this->loadJsonTranslationsFrom(module_path('ModuleName', 'Resources/lang'));
        }
    }

This package supports laravel translations out of the box. Both json and the PHP array way.

Unfortunately on my test it doesn't load the json translation file, only the PHP array way.
(On laravel v6) i haven't tried the v7 yet.
After i added loadJsonTranslationsFrom then it does read the json file correctly.
Looks like loadTranslationsFrom only load php array translation.

Sorry, i mean json translation file without prefixing.

I use this
$this->loadJsonTranslationsFrom(DIR.'/../Resources/Lang');

hey

Hi thank you for the reply,
I'm sorry i have to a bit disagree, i think laravel modules should support default laravel translation out of the box.
Since default laravel offers translation strings as keys, then i want to use it inside the modules just like normal laravel app. (isn't that the purpose of laravel modules?).
For now i managed to load the json translation manually by adding loadJsonTranslationsFrom inside registerTranslation function in service provider file.
I hope the generator would done this automatically (e.g php artisan module:make ModuleName)
/**
     * Register translations.
     *
     * @return void
     */
    public function registerTranslations()
    {
        $langPath = resource_path('lang/modules/modulename');

        if (is_dir($langPath)) {
            $this->loadTranslationsFrom($langPath, 'modulename');
            $this->loadJsonTranslationsFrom($langPath);
        } else {
            $this->loadTranslationsFrom(module_path('ModuleName', 'Resources/lang'), 'modulename');
            $this->loadJsonTranslationsFrom(module_path('ModuleName', 'Resources/lang'));
        }
    }

Thanks! This solution helped me! I believe this library should implement this solution, it is a flawed view to think that it should not be implemented.

This package supports laravel translations out of the box. Both json and the PHP array way.

Wouldn't it be nice if your answer was not always limited to state the fact that your packages can do stuff, but to guide others who care enough to give a try to your work? You state that your package supports json translations out of the box, but you don't care to show how we should do it, because you assume that if we idiots don't know how to do it we shouldn't even be using your package, right? WRONG! ... have a little modesty and get down to earth with mortals.

@bedoya Congratulations on your reply. I agree with you.

Nowdays still does not work out of the box as mentioned before. At least is not documented.
This is the registerTranslations() not using hardcoded module name, so it's easier to copy and paste.
`
public function registerTranslations()
{
$langPath = resource_path('lang/modules/' . $this->moduleNameLower);
    if (is_dir($langPath)) {
        $this->loadTranslationsFrom($langPath, $this->moduleNameLower);
        $this->loadJsonTranslationsFrom($langPath);
    } else {
        $this->loadTranslationsFrom(module_path($this->moduleName, 'Resources/lang'), $this->moduleNameLower);
        $this->loadJsonTranslationsFrom(module_path($this->moduleName, 'Resources/lang'));
    }
}

`

O Nowdays ainda não funciona fora da caixa, como mencionado antes. Pelo menos não está documentado. Este é o registerTranslations () que não usa o nome do módulo codificado, então é mais fácil de copiar e colar.
public  function  registerTranslations ()
    {
        $ langPath = resource_path ( 'lang / modules /' . $ this -> moduleNameLower );
        if ( is_dir ( $ langPath )) {
             $ this -> loadTranslationsFrom ( $ langPath , $ this -> moduleNameLower );
            $ this -> loadJsonTranslationsFrom ( $ langPath );
        } else {
             $ this -> loadTranslationsFrom ( module_path ( $ this -> moduleName , 'Resources / lang' ), $ this -> moduleNameLower );
            $ Presente -> loadJsonTranslationsFrom ( module_path ( $ presente -> moduleName , 'Resources / lang' ));
        }
    }

In my tests this works on Laravel 8.

Nowdays still does not work out of the box as mentioned before. At least is not documented. This is the registerTranslations() not using hardcoded module name, so it's easier to copy and paste.
public function registerTranslations()
    {
        $langPath = resource_path('lang/modules/' . $this->moduleNameLower);
        if (is_dir($langPath)) {
            $this->loadTranslationsFrom($langPath, $this->moduleNameLower);
            $this->loadJsonTranslationsFrom($langPath);
        } else {
            $this->loadTranslationsFrom(module_path($this->moduleName, 'Resources/lang'), $this->moduleNameLower);
            $this->loadJsonTranslationsFrom(module_path($this->moduleName, 'Resources/lang'));
        }
    }

In my tests this works on Laravel 8.

I'm having some trouble with this as well, but for me only the translations from the first module loaded are being actually loaded, translations from all other modules are not.
I can't find a way of making it work.

Nowdays still does not work out of the box as mentioned before. At least is not documented. This is the registerTranslations() not using hardcoded module name, so it's easier to copy and paste.
public function registerTranslations()
    {
        $langPath = resource_path('lang/modules/' . $this->moduleNameLower);
        if (is_dir($langPath)) {
            $this->loadTranslationsFrom($langPath, $this->moduleNameLower);
            $this->loadJsonTranslationsFrom($langPath);
        } else {
            $this->loadTranslationsFrom(module_path($this->moduleName, 'Resources/lang'), $this->moduleNameLower);
            $this->loadJsonTranslationsFrom(module_path($this->moduleName, 'Resources/lang'));
        }
    }

I followed your instruction, but translation is not loaded. It return raw string instead.
{{  __('reservation:Reservation Confirmed') }}
return
reservation:Reservation Confirmed
my ReservationServiceProvider:
/**
     * Register translations.
     *
     * @return void
     */
    public function registerTranslations()
    {
        $langPath = resource_path('lang/modules/' . $this->moduleNameLower);

        if (is_dir($langPath)) {
            $this->loadTranslationsFrom($langPath, $this->moduleNameLower);
            $this->loadJsonTranslationsFrom($langPath);
        } else {
            $this->loadTranslationsFrom(module_path($this->moduleName, 'resources/lang'), $this->moduleNameLower);
            $this->loadJsonTranslationsFrom(module_path($this->moduleName, 'resources/lang'));
        }
    }

I'll re-open this so I can look into this further.

it works for me, enabled both json and traditional files:
public function registerTranslations()
    {
        $langPath = resource_path('lang/modules/' . $this->moduleNameLower);

        if (is_dir($langPath)) {
            $this->loadTranslationsFrom($langPath, $this->moduleNameLower);
            $this->loadJsonTranslationsFrom($langPath, $this->moduleNameLower);
        } else {
            $this->loadTranslationsFrom(module_path($this->moduleName, 'Resources/lang'), $this->moduleNameLower);
            $this->loadJsonTranslationsFrom(module_path($this->moduleName, 'Resources/lang'), $this->moduleNameLower);
        }
    }

Changing my language in config to fr
'locale' => 'fr',

then in a module create a fr.json file:
{
  "Name ok": "changed",
}

In a view:
{{ __('Name ok') }}

shows changed for me.
When using json translations you can only prefix the key if you manually add a prefix such as:
{
  "reservation:Name ok": "changed",
}

In a view:
{{ __('reservation:Name ok') }}

This will be due to Laravel will be looking for an exact match.

it works for me, enabled both json and traditional files:
public function registerTranslations()
    {
        $langPath = resource_path('lang/modules/' . $this->moduleNameLower);

        if (is_dir($langPath)) {
            $this->loadTranslationsFrom($langPath, $this->moduleNameLower);
            $this->loadJsonTranslationsFrom($langPath, $this->moduleNameLower);
        } else {
            $this->loadTranslationsFrom(module_path($this->moduleName, 'Resources/lang'), $this->moduleNameLower);
            $this->loadJsonTranslationsFrom(module_path($this->moduleName, 'Resources/lang'), $this->moduleNameLower);
        }
    }

Changing my language in config to fr
'locale' => 'fr',

then in a module create a fr.json file:
{
  "Name ok": "changed",
}

In a view:
{{ __('Name ok') }}

shows changed for me.
When using json translations you can only prefix the key if you manually add a prefix such as:
{
  "reservation:Name ok": "changed",
}

In a view:
{{ __('reservation:Name ok') }}

This will be due to Laravel will be looking for an exact match.

I followed all of your code, but still not working:
1. service provider

2. km.json

3. blade

4. result

I also tried: {{ __('academic:Academic') }}, {{ __('academic::Academic') }}, {{ __('Academic') }} in blade, but still not render.
Laravel Version: "laravel/framework": "^9.0",
Module Version: "nwidart/laravel-modules": "^9.0",
docs: https://docs.laravelmodules.com/v9/languages

I am upgrading to Laravel 9 and experience the same as @limsocheat. I will try to find to root cause or is any found already?

I have found a solution to this problem. Open file: /config/app.php and change
'locale' => '',
'fallback_locale' => '',

Create the Locale middleware and set the locale you want.
public function handle($request, Closure $next)
    {
        $locale = 'en';
        \App::setLocale($locale);
        return $next($request);
    }

Add this middleware to your routes.
After it the translation will work.
Route::group(['middleware' => 'locale'], function() {
// your route
});

So basically the locale is not set?  Adding middelware is a workaround but not really a nice one. Is it possible to fix it somehow in de package?

For me it was the component BenSampo/laravel-enum. It loaded a translation too soon.
I found it by  adding
debug_print_backtrace();exit();
to
Illuminate\Foundation\Helpers.php
@line 882 in the function __($key = null, $replace = [], $locale = null) so i saw where it was used to soon.

it works for me, enabled both json and traditional files:
public function registerTranslations()
    {
        $langPath = resource_path('lang/modules/' . $this->moduleNameLower);

        if (is_dir($langPath)) {
            $this->loadTranslationsFrom($langPath, $this->moduleNameLower);
            $this->loadJsonTranslationsFrom($langPath, $this->moduleNameLower);
        } else {
            $this->loadTranslationsFrom(module_path($this->moduleName, 'Resources/lang'), $this->moduleNameLower);
            $this->loadJsonTranslationsFrom(module_path($this->moduleName, 'Resources/lang'), $this->moduleNameLower);
        }
    }

Changing my language in config to fr
'locale' => 'fr',

then in a module create a fr.json file:
{
  "Name ok": "changed",
}

In a view:
{{ __('Name ok') }}

shows changed for me.
When using json translations you can only prefix the key if you manually add a prefix such as:
{
  "reservation:Name ok": "changed",
}

In a view:
{{ __('reservation:Name ok') }}

This will be due to Laravel will be looking for an exact match.

I followed all of your code, but still not working:
1. service provider
2. km.json
3. blade
4. result
I also tried: {{ __('academic:Academic') }}, {{ __('academic::Academic') }}, {{ __('Academic') }} in blade, but still not render.
Laravel Version: "laravel/framework": "^9.0", Module Version: "nwidart/laravel-modules": "^9.0", docs: https://docs.laravelmodules.com/v9/languages

I have the same problem in a Laravel 8 installation, performing the same steps indicated by @dcblogdev and @limsocheat the translations are not read, keep getting the translations from project root (not module).
...beyond this, am I wrong or the loadJsonTranslationsFrom() method just want one parameter?
https://laravel.com/api/9.x/Illuminate/Support/ServiceProvider.html#method_loadJsonTranslationsFrom

For me, the problem with the translations are only the routes used, by default is not using the same standard path that in laravel projects. Also, for me, it may include the original array translation folder in the root module folder.

Modules/YourModule/lang/XX/YYYY.php (pending implementation)
Modules/YourModule/resources/lang/XX.json (solved with the minor change in the screenshot)

By default in laravel-modules it's using a combined path that is not based on the original laravel structure for languages:

Modules/YourModule/lang/XX.json

At this moment, for me is enough only with json file to get all translations in one file, but I think that is always preferable get it in the common way in the Laravel to get full compatibility on implement it has any dev prefers to use on each case.

For me, the problem with the translations are only the path used, by default is not using the same standard path that in laravel projects. Also, for me, it may include the original array translation folder in the root module folder (not in core project as lang/modules, the lang/XX/YYYY.php inside the module).

Modules/YourModule/lang/XX/YYYY.php (pending implementation)
Modules/YourModule/resources/lang/XX.json (solved with the minor change in the screenshot)

By default in laravel-modules it's using a combined path that is not based on the original laravel structure for languages:

Modules/YourModule/lang/XX.json

At this moment, for me is enough only with json file to get all translations in one file, but I think that is always preferable get it in the common way in the Laravel to get full compatibility on implement it has any dev prefers to use on each case.

I'm not sure if I use it correct with helper functions to call translation can you also share usage of it.
For example: trans("user::errors.not_found") or trans("errors.not_found")

authors: JamesHemery Marciobds Rattone alpemreelmas bedoya dcblogdev dexcell l1th1um limsocheat nWidart nyneplus raulpacheco2k shawe tuaititecnologia usmanabbas2211 vietsach0808


text:
Add multi-station weather querying

If one of the meteorological elements is not available from our preferred station, get it from the next one.
I.e. instead of
SELECT DISTINCT ON (timestamp)
    temperature,
    ...

do
SELECT
    timestamp,
    FIRST(temperature),
    ...
GROUP BY timestamp

This implies that we cannot return source information (station_id, location, etc.), since a single timestamp could be comprised of elements from multiple sources.

Benchmarks:
By lat/lon:
  50 one-day queries,  sequential:   2.76 s
  50 one-day queries,  parallel:     1.53 s
  50 one-week queries, sequential:   7.45 s
  50 one-week queries, parallel:     4.95 s

By lat/lon, no fallback:
  50 one-day queries,  sequential:   2.12 s
  50 one-day queries,  parallel:     1.16 s
  50 one-week queries, sequential:   5.70 s
  50 one-week queries, parallel:     3.77 s

By station:
  50 one-day queries,  sequential:   1.30 s
  50 one-day queries,  parallel:     0.59 s
  50 one-week queries, sequential:   3.42 s
  50 one-week queries, parallel:     1.64 s

By source:
  50 one-day queries,  sequential:   0.53 s
  50 one-day queries,  parallel:     0.25 s
  50 one-week queries, sequential:   2.11 s
  50 one-week queries, parallel:     1.00 s

repo: na-boa/brightsky


text:
Finished mobile version of portfolio project

-Added about section
-Added previous projects
-Added languages
-Added frameworks section

Hello dear reviewer,
I have resolved the issues above as follows:
issue 1 and 2: div tag changed to section tag
issue 3: display changed to grid
issue 4: div changed to button and font size updated
issue 5: background color changed
issue 6: design was improved and font-sizes matched with the Figma design
Thank you.

Hello reviewer, I have again updated it again according to the previous reviewers' requests. Please approve.

Dear Reviewer, please approve it as I have done all required changes and optional requirements.

I have added a break line.
I have used ul instead of div.
Thank you very much

repo: naanmohammed/my-portfolio


text:
ChartFox Integration

During the flight planning stage, particularly after the OFP output from SimBrief, it would be a welcome feature to be able to offer to pilots the respective departure, arrival and alternate airport charts.
Now, since all charts are copyright protected, for the most part, this falls on the responsibility of the user, to either have them or know how to access them.
ChartFox is a free website providing a consolidated library of publicly available charts, thus, offering a possibility for phpVMS pilots to quickly access the necessary reference material.
I don't believe that ChartFox offers any specific integration capability. I would simply see it as an admin option (to turn on/off the integration) and then, on the flight planning page, offer an external link to the departure, arrival and alternate ICAO airports (since ChartFox uses a straightforward URL structure.
https://chartfox.org/KLAX (example)

This can be done at theme stage, I see no core changes needed here.

You can have your charts uploaded to your server (if you wish to go that way and take copyright risks), then work for endless updates
Or you can have the above link in your template (specially at SimBrief Briefing page or any page you want, with some javascript to check if the link is alive or not etc)

You have the airport code in all pages you may need to display that link, or any link related to an airport ICAO code.
Btw, just to mention that ChartFox link needs VATSIM membership, considering that phpvms v7 is not online platform specific or tied, this is another reason for not having it in the core and shipped to all users.

My pleasure, as an example, in my theme (Disposable Theme v3) I have some modals (kind of pop-ups)... One in SimBrief Form (to open RouteFinder), another one in SimBrief Briefing (to open the OFP for editing).
That logic can be used for departure and arrival airport charts with ChartFox or any other source if you need to. As the theme is your own and not effected by core updates, it will be totally under VA Admin control ;)
Technically this is why I have "non-core" related stuff in my theme and modules.

authors: FatihKoz vCaptainMike

repo: nabeelio/phpvms


text:
Please update installation instructions for Linux

Please update installation instructions for Linux. Currently only shown for Ubuntu 16.04. The current version is 20.04 and doesn't offer dependencies as listed. libssl1.0-dev has not installation candidate. Please also include a pre-compiled executable.

If you know what is missing, I suggest submitting a PR.

authors: abitrolly lgmventura


text:
Secondary LEDs on X470 Gaming Plus not turning off

I set this to run on boot
/usr/local/sbin/msi-rgb 0 0 0
I noticed in windows if i use Mystic Light to turn off the leds off the ram and PCIe slot leds turn off also, the above command only turns the main rgb leds not and not the other LEDs

oh that is what -x is for
sudo msi-rgb -x 0 0 0
not sure if you can use the main leds and have the others off, but my problem is solved

repo: nagisa/msi-rgb

license: isc


text:
Subtitles2Text+ implementation on macOS - macOSでのSubtitles2Text+の実装

Hi there! I'm opening this issue as a continuation of the macOS install. Thank you for your work on the macOS compatibility!
こんにちは、macOSインストールの続きとしてこの問題を開きます。macOSとの互換性についてのご尽力に感謝します！
Anyway, I noticed there are components within the 2.4.1 version containing Subtitles2Text+.
とにかく、2.4.1バージョンの中にSubtitles2Text+を含むコンポーネントがあることに気づきました。

However, when I started installing your script via Resolve Launcher and opened Resolve via Launcher, those components were not present like in the Windows version.
しかし、Resolve Launcher経由でスクリプトのインストールを開始し、Launcher経由でResolveを開いたところ、Windows版のようにこれらのコンポーネントが存在しませんでした。

---//---
Environment - 環境
macOS Ventura 13.5.2
DaVinci Resolve Studio 18.5
Resolve_Script 2.4.1 alpha

pythonがdavinci resolveに認識されていないようです。
Resolve_Script2.4.2_mac_ALPHA2を使ってください。
・pythonをインストール(ツールは3.10.11で確認しています)
・setup_python.commandを実行
・りぞりぷと.commandを実行

Apologies for the delay in replying - My university schedule has been quite busy recently, so I could not get back to you instantly. :(
返信が遅れて申し訳ない。最近、大学のスケジュールがかなり忙しくて、すぐに返信できなかったんだ。
--##--
Anyway, the script is working now! The script has been loaded into DaVinci successfully and is running similarly to the Windows implementation.
とにかく、スクリプトは動くようになった！スクリプトは無事にDaVinciに読み込まれ、Windowsの実装と同様に実行される。

--##--
Thank you for implementing macOS support & for helping me resolve the issue!
macOSのサポートを導入し、問題を解決してくれてありがとう！
(env: Resolve_Script2.4.2_mac_ALPHA2 @ DaVinci 18.5 & 18.6 - macOS Sonoma 14.0)

Have a fun time


text:
Looking for ways for better accessibility linting

It's hard to interpret the accessibility linting results.
The generated report in json format is not very clear.
Maybe we find a better tool for accessibility linting.

pa11y looks promising
Current version works with node 8 only
So, we're waiting for end of active LTS of node 6 (may 2018)

We will remove the unused accessibility linting. For some accessibility inputs we will include "lighthouse" for now.

lighthouse score test was released in v4.11.0

repo: namics/generator-nitro


text:
Error in HSCIC calculation

https://github.com/namratadeka/circe/blob/07648726785337582dd08f693e1567eab8d9a8ff/utils/losses.py#L81
In the HSCIC calculation function, I identified an error that led to unreasonable outcomes in my research.
Upon inspection, I recommend modifying the following line.
WtKyy = torch.linalg.solve(Ky + ridge_lambda  * torch.eye(Ky.shape[0]).to(Ky.device), Kx)

given the equation in the paper as following.

The issues seems to be resolved, so I'm closing the issue.

authors: romanpogodin yichengleo

repo: namratadeka/circe


text:
Copy symbolic links as directories for release

build_embedded: true is no longer default on Mix projects. So priv directories inside _build are still symbolically linked to priv directories of each Erlang/Elixir app respectively.
This will cause crashes in production if only _build is made writable after deployment and any app tries to write to its own priv directory.
This fix adds -k to rsync so symbolically linked directories are copied during release, effectively forcing build_embedded: true always.

Thank you!

authors: jayjun tylerflint

repo: nanobox-io/nanobox-engine-elixir


text:
nanobox dev panic

2015-12-23 11:43:07 FATAL Cause of failure: close of closed channel
2015-12-23 11:43:07 FATAL Error output:
/Users/sdomino/gocode/src/github.com/nanobox-io/nanobox/main.go:24 (0x4002c73)
/usr/local/Cellar/go/1.5.2/libexec/src/runtime/asm_amd64.s:437 (0x405ae4e)
/usr/local/Cellar/go/1.5.2/libexec/src/runtime/panic.go:423 (0x402b649)
/usr/local/Cellar/go/1.5.2/libexec/src/runtime/chan.go:303 (0x4005c9e)
/Users/sdomino/gocode/src/github.com/nanopack/mist/core/remote.go:201 (0x41d6c88)
/Users/sdomino/gocode/src/github.com/nanobox-io/nanobox/util/server/develop.go:27 (0x40ef44a)
/Users/sdomino/gocode/src/github.com/nanobox-io/nanobox/commands/dev.go:109 (0x40854ec)
/Users/sdomino/godeps/src/github.com/spf13/cobra/command.go:547 (0x40fb389)
/Users/sdomino/godeps/src/github.com/spf13/cobra/command.go:630 (0x40fbb4a)
/Users/sdomino/gocode/src/github.com/nanobox-io/nanobox/main.go:40 (0x4002bba)
/usr/local/Cellar/go/1.5.2/libexec/src/runtime/proc.go:111 (0x402db30)
/usr/local/Cellar/go/1.5.2/libexec/src/runtime/asm_amd64.s:1721 (0x405d1a1)

fixed by #136

authors: sdomino tylerflint

repo: nanobox-io/nanobox


text:
Fixing serializer for objects as properties

Description

Fixing serializer for objects as properties.
Migrating projects to support VS2022.

Motivation and Context

Fixing serializer for objects as properties
Typically when you have a Hashtable and place a custom class in it

How Has This Been Tested?

Unit test, added
Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
[x] Unit Tests (work on Unit Tests, has no impact on code or features)
[ ] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

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

You seem to be using tabs for indentation now... We're using 4 spaces everywhere.

I just did ctrl+k+d to fix all the indentations issues in the test file.


text:
Adding some flexibility to PhysicalEphemerisSignal

Hi All, @danielreardon added inner Solar System planets to BayesEphem, which looks useful. I pulled Daniel's updates and I added some minor improvements to enterprise, so that there is flexibility on what BayesEphem components are included in a model. I also think it's better to replace kwargs of PhysicalEphemerisSignal , so that it takes priors rather than True/False. This way, people can choose priors on planet mass and orbit perturbations themselves, instead of using hardcoded values.
Update 2020/10/01: I also added a possibility to fit for orbital elements of all planets, not just Jupiter and Saturn. Orbit partials were obtained with this code

I don't understand the rational behind removing the default BayesEphem PhysicalEphemerisSignal kwargs.  A user can always pass their own kwargs when instantiating the signal to override the defaults.  Removing the defaults, makes it harder for users to implement BayesEphem effectively.  It also model breaks our unit tests which rely on the defaults being there.

@paulthebaker , thanks for your reply. The only change for the user is to pass d_saturn_mass=parameter.Uniform(...) instead of d_saturn_mass=True. The same is true for sat_orb_elements, for all planets. If a person doesn't need a planet to be included, he doesn't need to pass anything, all defaults are zero. My take is that people who work on planetary ephemerides might want to try different priors now or in the future. Currently, priors are hardcoded, and a few years ago you told me yourself that hardcoding numbers is not the best way :) I also noticed the test failure, and I am happy to try to fix the test too. Otherwise, I am still OK with changing the kwargs back to True/False. Please let me know what you think.
The rest of the update just generalizes enterprise to all planets and their orbital elements.

As a warning, a big PR that makes many unrelated changes is unlikely to be merged.  In this case I think adding more functionality to BayesEphem is acceptable, but a lot of the selection stuff isn't really right for enterprise base.  Enterprise provides the Selection class and an example usage, but the many special selection types really should be implemented in a specific project.
The github interface doesn't let you git cherry-pick individual commits from a PR, so its all or nothing.
If you want to work on the BayesEphem stuff, I'd recommend starting a clean PR from a fork of the current nanograv:master branch and only include the BayesEphem stuff in that PR.  I suspect @vallis will have some strong opinions about how best to implement any changes to BayesEphem.  It might be more productive to discuss possible enhancements to BayesEphem in an Issue.
You are right that it't not ideal to have numerical values hardcoded in that way.  Implementing those defaults in a more readable way would be a welcome enhancement.  The main thing is that the default behavior remains the same.  Many existing analyses, including most "blocks" in enterprise extensions, instantiate BayesEphem with the defaults.  If the default behavior, changes it would break a lot of code.  Changing the tests to work with new defaults isn't the solution.

@paulthebaker , I completely agree with you about selections. In fact, these selection updates are only displayed in commit history - there are no additional selections added in the current pull request. I really pulled the most recent nanograv:master and only changed deterministic_signals.py and utils.py to add these specific BayesEphem updates. There should be nothing else, although please correct me if I am wrong.
As for keeping the default BayesEphem behavior - that makes sense, I will fix that and let you know.

In the tab "Files changed", there are only the BayesEphem changes that I described. Thus, I assume, the rest is consistent with nanograv:master

No problem, @vallis ! For the PPTA DR2 GWB paper, I actually implemented a code that allows doing model selection for each orbital element separately and I included all Solar System planets. For that, I introduced a "UniformMaskPrior" that allows to switch on and off individual orbital elements. The code is here: https://github.com/bvgoncharov/correlated_noise_pta_2020/blob/1990d3aa4f2d436f84fcfb19317b00b11590c230/ppta_dr2_models.py#L150
If that is interesting, I could help to move that to the main branch.

authors: bvgoncharov paulthebaker

repo: nanograv/enterprise


text:
PB_BIND data offset static assertion failing in Segger Embedded Studio (clang and gcc)

I've got a project that uses nanopb protos to communicate via UART to another device.  It looks like every proto I've defined that's not just an empty message throws a compiler error.  The error is static_assert expression is not an integral constant expression.   The compiler also emits a message at that line, saying cast that performs the conversions of a reinterpret_cast is not allowed in a constant expression.  I'm aware of the definition that disables static assertions, but would like to keep them enabled if possible.
Digging into the precompiler output, it seems that the error is being thrown in the data offset check, which expands to the following:
_Static_assert(((uint32_t) (((size_t) & (((SetVolume *) 0)->volume))) < ((uint32_t) 1 << 8)), "FIELDINFO_DOES_NOT_FIT_width1_field1");

The proto itself is pretty simple:
message SetVolume
{
	uint32 volume = 1;
};

I've tested this with both clang 13.0.1 and gcc 10.3.1 as supplied by Segger Embedded Studio, and this static assertion threw an error for both.  Both compilers support C17.  I've also used this same code in another related project in vscode, compiled with the Arm GNU embedded toolchain (arm-none-eabi version 9 2019 q4 major), and there were no issues.

It might also matter where offsetof() macro definition comes from. That
looks a bit like C-style offsetof used in C++ mode.

This is a c++ project, but the project is configured to build .c files with the c compiler.  I've confirmed that the c compiler is being used by placing a check at the top of the .pb.c file to emit a warning if __cplusplus is set.  The full build string, stripping out a million includes, is
"C:\Program Files\SEGGER\SEGGER Embedded Studio for ARM 6.20a\llvm\bin\clang"
-cc1
-disable-free
-disable-llvm-verifier
-fgnuc-version=4.2.1
-mrelocation-model static
-mconstructor-aliases
-x c
-fcolor-diagnostics
-fansi-escape-codes
-std=c17
-triple thumbv7em-none-eabi
-target-cpu cortex-m4
-target-feature
-strict-align
-target-abi aapcs
-mfloat-abi hard
-fno-signed-char
-fallow-half-arguments-and-returns
-mllvm
-arm-global-merge=false
-nostdsysteminc
-nobuiltininc
-D__SIZEOF_WCHAR_T=4
-D__ARM_ARCH_7EM__
-D__SES_ARM
-D__ARM_ARCH_FPV4_SP_D16__
-D__HEAP_SIZE__=1024
-D__SES_VERSION=62001
-D__SEGGER_LINKER
-D_LIBCPP_HAS_NO_THREADS
-D_LIBCPP_HAS_NO_OFF_T_FUNCTIONS
-D__NO_AEABI_ERR__
-D__FPU_PRESENT
-D__FPU_USED
-DARM_MATH_CM4
-DSTM32F407xx
-D__STM32F4xx_FAMILY
-D__STM32F407_SUBFAMILY
-DFLASH_PLACEMENT=1
-DUSE_FULL_LL_DRIVER
-DHSE_VALUE=8000000
-dependency-file C:/proj/Output/PROJ_STM32F407_Debug/Obj/proj/casterlink.d
-sys-header-deps
-MT Output/PROJ_STM32F407_Debug/Obj/proj/casterlink.pb.o
-Wall
-Wextra
-Wstrict-prototypes
-Wstrict-aliasing
-dwarf-version=4
-debug-info-kind=standalone
-debugger-tuning=gdb
-mllvm
-generate-arange-section
-exception-model=dwarf
-gpubnames
-fno-dwarf-directory-asm
-fno-builtin
-fmath-errno
-ffunction-sections
-fdata-sections
-fshort-enums
-fno-common C:\proj\middleware\Modules\casterlink\src\casterlink.pb.c
-E
-o C:/proj/Output/PROJ_STM32F407_Debug/Obj/proj/casterlink.pb_PP.c

As near as I can tell, offsetof() is coming from Segger's stddef.h, where it's defined as
#define offsetof(s,m) ((size_t)&(((s *)0)->m))

I've never had to use this macro before, but wikipedia's got a page on it, as well as a couple alternative definitions.  Curiously, redefining offsetof() to their third alternative definition,
#define offsetof(st, m)  __builtin_offsetof(st, m)

works fine for me.  So, I'm suspecting that Segger is just being pedantic.  What else can I test, here?

Does defining PB_C99_STATIC_ASSERT make any difference?
It looks like gcc and clang special-case offsetof() in their headers to avoid spurious errors. But for some reason Segger ships a version of stddef.h that is not based on the one by the compiler authors.
For some reason, I still don't get the error message about "constant expression" unless building in C++ mode, but that could also have something to do with what is defined in the headers.

Unfortunately, defining PB_C99_STATIC_ASSERT doesn't seem to change anything.
I went back to my other project (gcc) and replaced the offsetof definition with Segger's.  As expected, gcc throws a warning:
warning: variably modified 'pb_static_assertion_FIELDINFO_DOES_NOT_FIT_width1_field1_13_2' at file scope

It's starting to look like this is a Segger problem, not anything in nanopb.  Segger's definition of offsetof just doesn't play nicely with their shipped compilers.  I even tried to use their own compilers, Segger and Segger-NG (whatever that means), and it still throws an error.  I propose to close this issue and I'll bring it up on Segger's support forum, unless there's anything else you'd be interested to try, first.

Yeah, that warning looks more like the ones I got when trying to reproduce the problem.
I don't currently have any other suggestions.

Sounds good.  Closing.
See also: https://forum.segger.com/index.php/Thread/6501-SOLVED-SES-4-20a-g-compiler-error-from-offsetof/ .  Looks like we're not the first people to have run into this.

authors: Jason-Bens-Teufel PetteriAimonen

repo: nanopb/nanopb

license: Zlib


text:
Update toc.yaml

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=ru
Description of changes:

ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/api-gateway/quickstart/index.md
ERR
ERR  No such file or has no access to /en/billing/quickstart/index1.md
ERR  Link is unreachable: ../quickstart/index.md#get_promocode in /en/billing/operations/change-data.md
ERR  Link is unreachable: ../quickstart/index.md#create_billing_account in /en/billing/operations/change-data.md
ERR  Link is unreachable: ../quickstart/index.md in /en/billing/concepts/bonus-account.md
ERR  Link is unreachable: ../quickstart/index.md in /en/billing/payment/payment-methods-individual.md
ERR  Link is unreachable: ../quickstart/index.md in /en/billing/payment/payment-methods-card-business.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/_includes/compute/before-you-begin-linux.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/compute/quickstart/quick-create-windows.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/compute/quickstart/ig.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/_includes/compute/before-you-begin-linux.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/data-transfer/quickstart.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/data-transfer/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/datasphere/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md in /en/free-trial/concepts/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md in /en/free-trial/concepts/trial-ending.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/iam/quickstart.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/iam/quickstart-sa.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/iot-core/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/kms/quickstart/index.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/load-balancer/quickstart.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/managed-kubernetes/quickstart.md
ERR  Link is unreachable: ../../../billing/quickstart/index.md#create_billing_account in /en/managed-kubernetes/operations/kubernetes-cluster/kubernetes-cluster-create.md
ERR  Link is unreachable: ../billing/quickstart/index.md in /en/_includes/quickstart-all.md
ERR  Link is unreachable: ../../../billing/quickstart/index.md#create_billing_account in /en/resource-manager/operations/cloud/create.md
ERR  Link is unreachable: ../../../billing/quickstart/index.md#create_billing_account in /en/resource-manager/operations/cloud/create.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/storage/quickstart.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/vpc/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/ydb/quickstart/create-db.md

WARN Variable specified_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable specified_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable label not found in /en/monitoring/concepts/querying.md
WARN Variable host not found in /en/monitoring/concepts/visualization/dashboard.md
WARN Variable myparm not found in /en/monitoring/concepts/visualization/dashboard.md
WARN Variable label not found in /en/monitoring/concepts/querying.md
WARN Variable isotime | clean_resource_name not found in /en/solutions/infrastructure-management/packer-quickstart.md
WARN Variable isotime | clean_resource_name not found in /en/solutions/infrastructure-management/packer-quickstart.md
WARN Variable .TablePathPrefix not found in /en/ydb/sdk/index.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable .TablePathPrefix not found in /en/ydb/sdk/index.md
WARN Variable ydb-cli not found in /en/ydb/maintenance/backup_and_recovery.md
WARN Variable label not found in /ru/monitoring/concepts/querying.md
WARN Variable host not found in /ru/monitoring/concepts/visualization/dashboard.md
WARN Variable myparm not found in /ru/monitoring/concepts/visualization/dashboard.md
WARN Variable label not found in /ru/monitoring/concepts/querying.md
WARN Variable isotime | clean_resource_name not found in /ru/solutions/infrastructure-management/packer-quickstart.md
WARN Variable isotime | clean_resource_name not found in /ru/solutions/infrastructure-management/packer-quickstart.md
WARN Variable .TablePathPrefix not found in /ru/ydb/sdk/index.md
WARN Variable .TablePathPrefix not found in /ru/ydb/sdk/index.md

WARN Variable specified_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable specified_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable unknown_key not found in /en/compute/concepts/instance-groups/variables-in-the-template.md
WARN Variable label not found in /en/monitoring/concepts/querying.md
WARN Variable host not found in /en/monitoring/concepts/visualization/dashboard.md
WARN Variable myparm not found in /en/monitoring/concepts/visualization/dashboard.md
WARN Variable label not found in /en/monitoring/concepts/querying.md
WARN Variable isotime | clean_resource_name not found in /en/solutions/infrastructure-management/packer-quickstart.md
WARN Variable isotime | clean_resource_name not found in /en/solutions/infrastructure-management/packer-quickstart.md
WARN Variable .TablePathPrefix not found in /en/ydb/sdk/index.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable ydb-cli not found in /en/ydb/quickstart/examples-ydb-cli.md
WARN Variable .TablePathPrefix not found in /en/ydb/sdk/index.md
WARN Variable ydb-cli not found in /en/ydb/maintenance/backup_and_recovery.md
WARN Variable label not found in /ru/monitoring/concepts/querying.md
WARN Variable host not found in /ru/monitoring/concepts/visualization/dashboard.md
WARN Variable myparm not found in /ru/monitoring/concepts/visualization/dashboard.md
WARN Variable label not found in /ru/monitoring/concepts/querying.md
WARN Variable isotime | clean_resource_name not found in /ru/solutions/infrastructure-management/packer-quickstart.md
WARN Variable isotime | clean_resource_name not found in /ru/solutions/infrastructure-management/packer-quickstart.md
WARN Variable .TablePathPrefix not found in /ru/ydb/sdk/index.md
WARN Variable .TablePathPrefix not found in /ru/ydb/sdk/index.md

ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/api-gateway/quickstart/index.md
ERR
ERR  No such file or has no access to /en/billing/quickstart/index1.md
ERR  Link is unreachable: ../quickstart/index.md#get_promocode in /en/billing/operations/change-data.md
ERR  Link is unreachable: ../quickstart/index.md#create_billing_account in /en/billing/operations/change-data.md
ERR  Link is unreachable: ../quickstart/index.md in /en/billing/concepts/bonus-account.md
ERR  Link is unreachable: ../quickstart/index.md in /en/billing/payment/payment-methods-individual.md
ERR  Link is unreachable: ../quickstart/index.md in /en/billing/payment/payment-methods-card-business.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/_includes/compute/before-you-begin-linux.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/compute/quickstart/quick-create-windows.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/compute/quickstart/ig.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/_includes/compute/before-you-begin-linux.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/data-transfer/quickstart.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/data-transfer/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/datasphere/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md in /en/free-trial/concepts/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md in /en/free-trial/concepts/trial-ending.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/iam/quickstart.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/iam/quickstart-sa.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/iot-core/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/kms/quickstart/index.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/load-balancer/quickstart.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/managed-kubernetes/quickstart.md
ERR  Link is unreachable: ../../../billing/quickstart/index.md#create_billing_account in /en/managed-kubernetes/operations/kubernetes-cluster/kubernetes-cluster-create.md
ERR  Link is unreachable: ../billing/quickstart/index.md in /en/_includes/quickstart-all.md
ERR  Link is unreachable: ../../../billing/quickstart/index.md#create_billing_account in /en/resource-manager/operations/cloud/create.md
ERR  Link is unreachable: ../../../billing/quickstart/index.md#create_billing_account in /en/resource-manager/operations/cloud/create.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/solutions/_solutions_includes/prepare-register-billing.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/storage/quickstart.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/_includes/ai-before-beginning.md
ERR  Link is unreachable: ../billing/quickstart/index.md#create_billing_account in /en/vpc/quickstart.md
ERR  Link is unreachable: ../../billing/quickstart/index.md#create_billing_account in /en/ydb/quickstart/create-db.md


text:
Keep screen from dimming during session

Screen dims or turns off during the breathing session, which force you to touch it a few times a minute (in my case), so that I can continue to see the rhythm aide and the count.

Noticed that there's an issue for this already: #5.


text:
Pin PySide2 and PyQt5 at <5.15

Description
We need to do some more testing on Qt 5.15 before we open it up in our requirements.  Definitely some things broken at the moment (though tests are passing)
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References
https://www.qt.io/blog/qt-for-python-5.15.0-is-out
How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

I guess we want to fix this on our end and then it doesn't matter if it's < or !=. BUT, if we do want to fix this on our end, then we should remove the "fixes #" above. =)

And if we would rather wait and see, then we should do !=
Either way we should probably add a test for this... Would that be hard? Sorry I am a noob at the Qt testing stuff...

it's actually quite tricky to test!  The strange thing is that the button does not seem to be emitting a signal when clicked, but let me try to mock it.  might take some time, so I'll do it in another PR, and this one can go in

yeah: napari/_qt/_tests/test_qt_buttons.py::test_push_button should be catching this but it doesn't ... might need to actually mock a click at a specific part of the screen

oh man... if you programmatically run viewer.window.qt_viewer.layerButtons.newPointsButton.click(), it adds a points layer... but actually clicking on it has no effect.

repo: napari/napari


text:
Check if milestone and label is added to PR

Description
This PR improves Label Checker action to run only if ready to merge is added and check if labels and milestones are added.
When adding a Label checker to requires workflows before merge it will enforce adding this information.
References
Type of change

[x] Maintenance (changes required to run napari, tests, & CI smoothly)

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

As triggers depend on main branch then adding and removing milestone will not trigger this workflow here, but one could play with it by adding/removing milestone/labels.

Awesome! One thing I'm not sure about: how does the milestone check even work, and should it be disabled separately?

miuestone check is GitHub app installed in repository and needs to be uninstalled after merge

Would be best if it warns about both things at once.

it will require own code to check this. It is doable but it will be next code to manage. But I you think that it is worth then I may do this.

Speaking of which, probably we should rename it to label and milestone check just so it's obvious you need to add both as a reviewer!

Rename is last steep as it will prevent from testing it here.

@Czaki From the conversation above, it sounds like you should change the action name before we merge?

Yes. But if I should update name or also file name?

I think it's nice if the filename matches the action title...

@jni, @brisvag could you check the new name?

Looks good. It's too far down so I can't suggest: can you change also the name of the job itself, and not just the workflow? So if you end up on the details page you also see the full name.

Ok, let's get this in!

hm. Adding this to required action before merge add pending state.

It is not faliture, but as I understand @Carreau it is still a problem?

@Czaki I suggest just removing it from required. Typically maintainers check all red status messages before merging and evaluate whether it's a quick fix etc.

Removed, maybe a number of PR without ready to merge will be small.

If not required, will it be ignored in the context of marking green/red on the PR list?

if not required then chek only impact PR with ready to merge label

if not required then chek only impact PR with ready to merge label

So right now:

if there is no ready to merge label and everything else passes, the PR is marked as green
if ready to merge is added and does not pass, the PR is marked a red? Or still green?

if there is no ready to merge label and everything else passes, the PR is marked as green

yes

if ready to merge is added and does not pass, the PR is marked a red? Or still green?

red

sounds great then :)

authors: Czaki brisvag jni


text:
Update the mod to factorio 0.17.X

please

Hi, sorry, the day job keeps me busy and I didn't even notice 0.17 was
available. If someone else wants to do the port, I do accept pull requests!
Otherwise, it'll be a while, sorry.
On Thu, Feb 28, 2019, 12:01 Nyhmus notifications@github.com wrote:

please
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/narc0tiq/YARM/issues/87, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkG1bkh-3o--sSPG-71ilLt-2EHUx5nks5vR6jwgaJpZM4bWbqQ
.


text:
[New Feature]: expose callbacks and ainvoke

Checked for duplicates

Yes

Alternatives considered

Yes - and alternatives don't suffice

Related problems

No, see below

Describe the feature request
However, in order for the GUI to stay responsive, deferring long-running tasks is essential. At the moment it is not possible to use ROSA for intermediate updates or react to errors. It would be nice if the ROSA constructor accepted a callbacks parameter to pass to its AgentExecutor. Exposing the ainvoke method would be useful, too.
As an aside, I'm not sure if adding double underscores to all class members is really necessary. It makes inheritance and monkey patching much more annoying :)

Changed the class methods from private to protected in #9

Can you elaborate on the intended use case a bit more? I'd like to understand how the callbacks would be used to keep the UI responsive.
Is it that you want to be able to submit arbitrarily many queries to the agent without waiting for the previous query to finish?
How will you keep track of the queries, their intermediate steps, and results?
Mostly just curious, I think it's a good idea either way.

Sure! Right now I'm running the request inside a thread and just update the UI from there once it returns. There are a couple of things I can't do with this approach (at least as far as I can tell):

stream responses
give user feedback about what tools are used
react to failed tool runs
cancel response generation

From what I saw, langchain uses a callback class and its member functions for handling response updates. I would construct this as I pass the request, then use a closure on my request and generated UI elements to keep the association.

Check out the astream implementation in rosa.py on feature/streaming. It's using LangChain astream_events method, which provides access to both streaming tokens, tool usage, etc.
Also see turtle_agent demo script for example usage.
One thing I noticed, and have yet to find a solution to, is that LangChain AgentExecutor cannot be pre-empted or cancelled with standard LangChain facilities. This will likely require use of asyncio tasks. What is unclear to me at the moment is whether ROSA should provide that integration, or if it should be left to the consumer (I am leaning more toward the latter).

Thank you! I'll have some time next week to test it out. I agree though that supporting request cancellation sounds like something langchain should provide.

Tried it out just now and works like a charm! The example was already very helpful. Seems like you had some fun with it :D Thank you!

authors: RobRoyce ndahn

repo: nasa-jpl/rosa


text:
Adding multiple of the same item

I noticed in the live demo, that if you add multiple of the same item, it just lists that item multiple times. Is there a way to show the item only once, and show a dropdown with the quantitiy.

Sounds like a future enhancement, or something you'd have to code yourself.

repo: nate-strauser/meteor-cart


text:
🛑 Cloud is down

In dc1bc2b, Cloud (https://cloud.astragroup.info) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cloud is back up in 9c2d19d after 14 minutes.


text:
difference with rust-ffmpeg?

hey i'm curious what is the difference with rust-ffmpeg:
https://github.com/zmwangx/rust-ffmpeg
? I'm using rust-ffmpeg atm in https://github.com/louis030195/screen-pipe but might be open to change because of the download feature etc. quite pain to package ffmpeg for deployment
what do you think are pros and cons?

Hey Louis,
The biggest difference is that rust-ffmpeg statically links against FFmpeg's source code library and libav directly. That means a lot of FFI, extern "C" stuff and whatnot. Compiling your program becomes a lot more involved, because you need an entire C toolchain in addition to what's required by Rust itself. I tried going down this route on Windows, and it was such a headache that it was one of the main motivations behind this crate.
Under the hood, ffmpeg-sidecar does everything through the FFmpeg CLI binary, the same way you might do it from the command line. You can think of it as just a wrapper around Rust std::Command and a bunch of helper functions for processing I/O. That means you can just ship with standard FFmpeg binaries if you want (or even have your users download them at runtime from an official source). As a bonus, since you aren't linking with FFmpeg's licensed source code, you can avoid a lot of the licensing restrictions that apply to the GPL-licensed parts of FFmpeg.

How does the performance compare? Given that data is transferred via stdin/stdout.

How does the performance compare? Given that data is transferred via stdin/stdout.

Good question, the short answer is that since IO is not the bottleneck, performance is not impacted by using stdout to transfer data.
The slowest part of the pipeline will be video encoding/decoding in 99% of cases; just a very very computationally expensive task. Stdio channels are built to handle data coming through at filesystem read/write speeds, and I've never encountered a situation where I can decode video faster than stdout can pipe it.
The biggest speed boost comes from decoding video on the GPU, and the FFmpeg CLI makes that extremely easy: just slap a -hwaccel auto on a command.
I do think it would be suitable for desktop streaming because in that use case both network bandwidth and video encoding speed would be a limiting factor before IO performance would.

cool thanks @nathanbabcock
i noticed someone forked ffmpeg-sidecar and use IPC for performance, do you recommend this?
https://github.com/CapSoftware/Cap/blob/63719073805f1fd040343ae27366272a29918078/apps/desktop/src-tauri/src/utils.rs#L47

Very interesting, I imagine it works very well!

How does the performance compare? Given that data is transferred via stdin/stdout.

Good question, the short answer is that since IO is not the bottleneck, performance is not impacted by using stdout to transfer data.
The slowest part of the pipeline will be video encoding/decoding in 99% of cases; just a very very computationally expensive task. Stdio channels are built to handle data coming through at filesystem read/write speeds, and I've never encountered a situation where I can decode video faster than stdout can pipe it.
The biggest speed boost comes from decoding video on the GPU, and the FFmpeg CLI makes that extremely easy: just slap a -hwaccel auto on a command.
I do think it would be suitable for desktop streaming because in that use case both network bandwidth and video encoding speed would be a limiting factor before IO performance would.

Gotcha, this is very helpful.
The examples that I see only seem to have the ability to give the input as file path? Any way for us to implement streams where we can continuously send RGBA data and receive H.264 frames (and vice versa).

/// To take input from stdin, use the value `-` or `pipe:0`.
pub fn input<S: AsRef<str>>(&mut self, path_or_url: S) -> &mut Self {
}

Just looked at the code, dropping it here in case anyone needs it as well.

repo: nathanbabcock/ffmpeg-sidecar


text:
Collecting the path (code)walker took

I have a nested data structure. Somewhere in the nested data structure, there are vectors with maps in them. (There are also vectors with not-maps in them, and I don't want those.) Those maps all have some primary key identifier; I am trying to turn the vector into a map, indexed by that identifier.
The vec-of-maps constraint seemed easiest to pour into a walker predicate: (sr/walker #(and (vector? %) (map? (first %)))). However, I need the path to each matched data structure in order to do the indexing correctly. Is there a way to get that out of walker, or do I need a totally different selector?

To collect the series of keys leading to each value, you'll need to make your own path that collects values along the way. For an example with a tree represented using vectors, it would look like:
(def PathTreeValues
  (recursive-path [] p
    (if-path vector?
      [(view #(map-indexed vector %)) ALL (collect-one FIRST) LAST p]
      STAY
      )))

(select PathTreeValues [:a :b [:c]])
;; => [[0 :a] [1 :b] [2 0 :c]]

Thanks!
I came up with:
(def vecs-of-maps-with-path
  (sr/recursive-path
   [] p
   (sr/cond-path
    #(and (vector? %) (map? (first %))) sr/STAY
    map? [(sr/collect-one sr/MAP-KEYS) sr/MAP-VALS p]
    vector? [(sr/view #(map-indexed vector %)) sr/ALL (sr/collect-one sr/FIRST) sr/LAST p]
    sr/STAY sr/STAY)))

(sr/transform
 vecs-of-maps-with-path
 (fn [& args]
   (let [path (butlast args)
         val (last args)
         key (-> val first keys first)] ;; imagine this actually depends on path
     (into {} (map (juxt key identity) val))))
 {:a [{:b 1} {:b 2} {:b 3}]})

(sr/transform
 vecs-of-maps-with-path
 (fn [& args]
   (let [path (spy (butlast args))
         val (last args)
         key (-> val first keys first)] ;; imagine this actually depends on path
     (into {} (map (juxt key identity) val))))
 {:some {:prefix {:a [{:b 1} {:b 2} {:b 3}]}}})

Is that somewhat idiomatic? Is there some preference that might lead to increased composability? (#(and (vector? %) (map? (first %))) is quite specific). I'd wrap it in a function that takes that pred and returns the recursive-path, but I don't know if there's a cleverer thing specter can do.
(also somewhat unrelated: I noticed you use CamelCase for this recursive-path. is there a distinction between, say ALL and PathTreeValues I'm missing?)
Thanks!

I would do it like this:
(def vecs-of-maps-with-path
  (sr/recursive-path [term-pred] p
   (sr/cond-path
    (pred term-pred) sr/STAY
    map? [ALL (sr/collect-one sr/FIRST) sr/LAST p]
    vector? [(sr/view #(map-indexed vector %)) sr/ALL (sr/collect-one sr/FIRST) sr/LAST p]
    sr/STAY sr/STAY)))

Your map case wasn't collecting the key properly, and you can define the recursive path to take in a parameter for the termination predicate. You then use vecs-of-maps-with-path as a function that returns a path.
Also, I'm not sure about your last case. This path will navigate to any non-map/vector value that doesn't match the termination predicate. If you don't want it to do that, just remove the last case.
Normally I put global paths as all-uppercase, and functions that return paths use same conventions as normal Clojure functions. No particular reason why I did camel case for my example.

Thanks, that worked a charm :) Complete example for posterity:
(def path-walker-orig
  (sr/recursive-path
   [term-pred] p
   (sr/cond-path
    (sr/pred term-pred) sr/STAY
    map? [sr/ALL (sr/collect-one sr/FIRST) sr/LAST p]
    vector? [(sr/view #(map-indexed vector %)) sr/ALL (sr/collect-one sr/FIRST) sr/LAST p]
    sr/STAY sr/STAY)))

(sr/transform
 (path-walker-orig #(and (vector? %) (map? (first %))))
 (fn [& args]
   (let [path (spy (butlast args))
         val (last args)
         key (-> val first keys first)] ;; imagine this actually depends on path
     (into {} (map (juxt key identity) val))))
 {:some {:prefix {:a [{:b 1} {:b 2} {:b 3}]}}})

I tried to factor out some of the paths so that they'd be easier to understand for people that are still learning specter (myself included), and got to:
(def indexed
  "A path that visits v and collects k in [[k v], ...]."
  [sr/ALL (sr/collect-one sr/FIRST) sr/LAST])

(def indexed-seq
  "A selector that visits all elements of a seq, and collects their indices."
  (sr/comp-paths (sr/view #(map-indexed vector %)) indexed))

(def path-walker
  (sr/recursive-path
   [term-pred] p
   (sr/cond-path
    (sr/pred term-pred) sr/STAY
    map? (sr/comp-paths indexed p)
    vector? (sr/comp-paths indexed-seq p))))

However, running that gets me:
1. Unhandled java.lang.IllegalArgumentException
   Cannot statically combine sequential when not in nav pos

                 impl.cljc:  700  com.rpl.specter.impl$static_combine/invokeStatic
                 impl.cljc:  693  com.rpl.specter.impl$static_combine/invoke
                 impl.cljc:  712  com.rpl.specter.impl$static_combine$fn__8637/invoke
                  core.clj: 2726  clojure.core/map/fn
              LazySeq.java:   40  clojure.lang.LazySeq/sval
              LazySeq.java:   49  clojure.lang.LazySeq/seq
                   RT.java:  525  clojure.lang.RT/seq
                  core.clj:  137  clojure.core/seq
                  core.clj: 3106  clojure.core/dorun
                  core.clj: 3121  clojure.core/doall
 ...

I searched the issue tracker and I can't tell if this is a bug or something I messed up.

comp-paths shouldn't be used within a navigator definition. You should remove that from path-walker. It's also better to use comp-paths for the definition of indexed, although for this case it doesn't really matter. It would matter in cases where you wanted to return indexed from a function somewhere and use it so that you don't pay the cost of compilation over and over.

Gotcha, thanks. For future reference for anyone who finds this ticket: comp-paths isn't what you want, (conj somepath p) also doesn't work -- what you're looking for is [thatpath p], e.g.:
(def INDEXED
  "A path that visits v and collects k in [[k v], ...].

  This is useful if you want to collect a path to something, see [[path-walker]]."
  [sr/ALL (sr/collect-one sr/FIRST) sr/LAST])

(def INDEXED-SEQ
  "A selector that visits all elements of a seq, and collects their indices.

  This is useful if you want to collect a path to something, see [[path-walker]]."
  [(sr/view #(map-indexed vector %)) INDEXED])

(def path-walker
  (sr/recursive-path
   [term-pred] p
   (sr/cond-path
    (sr/pred term-pred) sr/STAY
    map? [INDEXED p]
    vector? [INDEXED-SEQ p])))

I'm guessing if I want to understand why that is, I'm going to go read the source for cond-path :)

authors: lvh nathanmarz

repo: nathanmarz/specter


text:
Mypy precommit

Add a precommit hook for mypy and silence errors. Some of these are significant issues which suggest the code would not have run (e.g. pass missing argument, no return value from a function leading to a codepath being impossible)

 Add mypy to enrichment repo

Ticket added for Abbreviation Detector bug: https://trello.com/c/38Ee0vZD/704-abbreviation-pipeline-not-working


text:
Add pip requirement files to Renovate config

Our dependency files for pip are in a strange place which means they're not automatically found by Renovate. This fixes the problem by explicitly providing their locations.

Codecov Report

Merging #1190 (547318a) into main (bc6d4b1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1190   +/-   ##
=======================================
  Coverage   93.67%   93.67%
=======================================
  Files          50       50
  Lines        1629     1629
  Branches      206      206
=======================================
  Hits         1526     1526
  Misses         88       88
  Partials       15       15

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

repo: nationalarchives/ds-caselaw-editor-ui


text:
Which recent NATS server supports websockets?

Hi,
I am trying to find a version of nats-server with websocket support.
Even the latest version 2.1.9 does not support the configuration option "websocket".

The websocket support in the NATS Server is in the main branch and available on nightly builds (docker pull synadia/nats-server:nightly). The next public release planned for mid/end of this month (Dec 2020) will have official support for Websocket, MQTT and JetStream.

authors: kozlovic wutkemtt


text:
Binary carrier with json payload

Hi. There any workaround about JSON payload in nats and opentracing? Now, when I trying to send JSON with tracing. On the subscriber side, I got not valid JSON - because binary carrier added trace id before.

Hi,  i switched on  opentracing.HTTPHeaders

Hi, i switched on opentracing.HTTPHeaders

I'm also used  NATS as communication service.  I just put  opentracing.HTTPHeaders  in Metadata field.


text:
Permission to remove an issue

Is it possible to give one of the project group the right to delete issues completely?
It would make sense to give this to @jarkenau as the project leader.
If this is not possible or wanted, should we then write another issue to remove the issues?

You cannot remove issues. You can only close issues. I have seen that you have already closed some issues. Please think before you create a new issue. Also, use decent descriptions in the issues. Thank you.

And yes, please write down any issues that should be removed if it is really necessary.

The issues that are to be removed are only issues that arose in the planning phase. There we tried out how we could best organise the requirements. Perhaps I should have mentioned that. We don't want to remove issues that show the progress of the project. In the future, it should no longer happen that unnecessary issues have to be created and removed.

@spuetz Thank you very much!
Since all issues have been removed and the permission to remove them is not up for discussion, I am closing the issue.

authors: lucaslootalot spuetz


text:
Update version and release notes for v1.0.1 release

This bumps the version to v1.0.1 and updates the release notes.

LGTM, but there is a mixed-use of tense in Fix vs Fixed in several entries. We should be consistent.

I hate that you're right.

repo: nautobot/nautobot


text:
🛑 Harmony Bot Website is down

In 994f7fd, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in b0bd133.


text:
🛑 Harmony Bot Website is down

In 904f292, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 8798a83.


text:
🛑 Harmony Bot Website is down

In 2f284c8, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in d923d09.


text:
🛑 Harmony Bot Website is down

In 5c34616, Harmony Bot Website ($HARMONY_WEB) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Harmony Bot Website is back up in 9474517.