feat: allow end user to turn on ssl mode for db connections

What kind of change does this PR introduce?
Allows end user to optionally enable SSL mode on db connections
What is the current behavior?
Currently the behavior is to disallow all SSL connections and not provide end user the option to allow them
What is the new behavior?
New behavior is to default to disallow SSL connections but allow end user to allow them via environment variable
Additional context
While this app is, as the readme states, intended to run in an unexposed environment, there are still valid use cases for having SSL enabled in these kinds of environments.

Maybe PG_CONNECTION should be named DEFAULT_PG_CONNECTION instead to avoid confusion, but you're meant to pass an x-connection-encrypted header to specify the DB URL per request. You can enable ssl this way.

Makes sense - but the main upstream project that uses this (Supabase) just uses and exposes the default connection string for downstream users: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml#L147
And I'm using that via the community helm chart: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml#L147
Should I ask there if it makes more sense to pass authentication via the headers? Seems like it might make configuring things a bit more difficult that way in downstream projects that call this and might be a much bigger change

Ah, I see - seems like it's easier to add this option instead. If you don't mind resolving the prettier check I'll merge this in :+1:

fixed by running prettier 👍


Visa card formatting error

It's removing the last digit from a Visa card (Mastercard seems ok) number when jumping to another field. It happens if we type a number then leave the cc number field, but it works just fine if we copy paste a number without spaces. Maybe a bug related with the added spaces between numbers.

Thanks, I'm not sure why. Would accept PR. Looks like #2

Couldn't find any bug. Maybe it's a bug from the "payment".

Would you mind if we disable the input formatting of the card first? That way we can use the other components while we figure this bug out.

The last line in payment READMe "You may have to turn off HTML5 validation (using the novalidate form attribute) when using this pattern, as it won't match space formatting."
This worked for me.

Thanks @Fettabachi ! 😊
https://github.com/jessepollak/payment#mobile-recommendations


Feature request: select directories for scraping

The built-in EmulationStation scraper downloads images and videos in arbitrary directories inside the roms system folder, such as /images and /videos.
It would be very useful if we could tell in which directories where we want each kind of asset to be downloaded.
For example, one could want to download 2d boxes into a /boxart directory, and screenshots into a /screenshots directory. Gamelist.xml creation could be also configurable in the same option screen, for example letting the user choose that the <image> tag that points to /boxart folder and the <thumbnail> tag that points to /screenshots folder.
While it would add a certain level of complexity to ES, it would be very useful and minimize the need to use a dedicated scraper tool, such as ARRM or Skraper.

No sorry. It should require to add new options + add a migration code, which will probably add complexity.
The internal scraper is meant to be simple.
You still have external tools if you want your own organisation.


Support passing arguments to {% include %} tag.

Would a patch to this effect be merged?
There are some scenarios where you want a have short syntax for useful helper, and using the {% with %} tag is not exactly succinct.
Even the Django guys, reputed to be ultra-conservative about their template language, supports this now.

There are a couple of ways to do this.
The Django style:
{% include file with key=value %} {# external context is accessible inside included file #}
{% include file with key=value only %} {# external context is not accessible #}

The Twig style (equivalent to the above):
{% include file with { "key" : value } %}
{% include file with { "key" : value } only  %}

The Twig style does provide some additional flexibility:
{% set key = "key1" if case else "key2" %}
{% include file with { key : value } %} {# keys can be dynamically determined #}

{% set args = { "key1" : value1, "key2" : value2 } %}
{% include file with args %} {# variable dictionaries can be passed in #}

Note that this functionality is not achievable using the with tag.
{% with key=value %}
{% include file %} {# the external context is accessible inside of the included file #}
{% include file without context %} {# the value set using with is not accessible #}
{% endwith %}

I've implemented the "Twig style" of this in a separate Jinja extension library, but in order to avoid branching jinja itself, I've had to copy and paste a lot of boilerplate, I've had to subclass Template and Environment, and I've even had to monkey patch a little.  Adding the functionality directly to jinja would be much cleaner and involve much less code.
I'd love to put a patch together, if there was some willingness to incorporate the functionality.  Is there any possibility that this feature would be accepted into Jinja?

I've come across this:
  <!--
    For some reason, the execution of the following tag: {{ active_page }}
    causes the active_page to be kept in "cache" and sent down to the nav.html.

    Without the inclusion of active_page above the below nav.html will not receive it.
  -->
  {% include 'nav.html' %}


cyclops-streams : Debounce returns last value in stream even if a value already sent for this time period

Debounce should only return the first value within specified debounce period (not first and last element in the Stream).

released in 7.1.0


update @radix-ui/react-dialog

Rebase delete my code

You must be doing rebase wrong then. Please look up some tutorials. It cannot be done with pull requests that have done merge already. In the future, you should only use rebase.


[Chip][material-ui] Outlined Chip variant is wider than the Filled counterpart

[x] I have followed (at least) the PR section of the contributing guide.

Fixes #39261


Dependency Issue. quart 0.18.4 requires blinker<1.6, but you have blinker 1.6.2 which is incompatible. but flask requires blinker 1.6.2

Environment:

Python version: 3.9.2
Quart version: 0.18.4
Flask Version: 2.3.2

This is addressed by c9b555ff284bb54a45adab44c8e6d78ab8713da0, which is not released yet.


Error when running on WebAPI + SPA

While running on a SPA project (WebAPI + VueJS) i got the following error:
C:\Users\nordes\.nuget\packages\illink.tasks\0.1.5-preview-1841731\build\ILLink.Tasks.targets(451,5): error MSB4044: The "CheckEmbeddedRootDescriptor" task was not given a value for the required parameter "AssemblyPath".

The log prior to that in verbose are normal msbuild dll creation and all.
Full log:
PS C:\GitRepo\gitlab\MyProject> dotnet-warp  --verbose
Running Publish...
Running dotnet publish -c Release -r win-x64 -o "C:\GitRepo\gitlab\MyProject\dotnetwarp_temp" "C:\GitRepo\gitlab\MyProject"
Microsoft (R) Build Engine version 16.0.443+g5775d0d6bb for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Persisting no-op dg to C:\GitRepo\gitlab\MyProject\obj\MyProject.csproj.nuget.dgspec.json
  Restore completed in 199.15 ms for C:\GitRepo\gitlab\MyProject\MyProject.csproj.
C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(151,5): message NETSDK1057: You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview [C:\GitRepo\gitlab\MyProject\MyProject.csproj]
  MyProject -> C:\GitRepo\gitlab\MyProject\bin\Release\netcoreapp2.2\win-x64\MyProject.dll
C:\Users\nordes\.nuget\packages\illink.tasks\0.1.5-preview-1841731\build\ILLink.Tasks.targets(451,5): error MSB4044: The "CheckEmbeddedRootDescriptor" task was not given a value for the required parameter "AssemblyPath". [C:\GitRepo\gitlab\MyProject\MyProject.csproj]

Publish failed. Set --verbose flag for more info.

Any idea how to fix this?
(It looks a bit like: https://github.com/mono/linker/issues/428 )

You are using .NET Core 3.0 preview SDK, which has some problems like one you described. In preview 5, there is already similiar Single File Deployment functionality (https://devblogs.microsoft.com/dotnet/announcing-net-core-3-0-preview-5/).
From path you supplied, I can see that you are building .NET Core 2.2 project.
You can add global.json file to root solution folder with
dotnet new globaljson

This will create global.json file with current project SDK entry, so it will use .NET Core 2.2 SDK instead of 3.0, which should fix that issue. Let me know if it helped


"violation: 1071 Specified key was too long"

Hi!
I'm trying to install your package and I am getting stuck on the migration.
I have tried the appservice provider fix
use Illuminate\Support\Facades\Schema;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    /**
     * Register any application services.
     *
     * @return void
     */
    public function register()
    {
        //
    }

    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        Schema::defaultStringLength(191);
    }
}

Ive even tried changing the database engine to innodb
'mysql' => [
            'driver' => 'mysql',
            'url' => env('DATABASE_URL'),
            'host' => env('DB_HOST', '<IP_ADDRESS>'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_unicode_ci',
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => 'InnoDB',
            'options' => extension_loaded('pdo_mysql') ? array_filter([
                PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
            ]) : [],
        ],

I was hoping maybe you might have an idea?

I did more research and I believe it is because of this line in your migration table. It seems that when the error is: "Specified key was too long; max key length is 1000 bytes" that 1000 always points back to the MyISAM table.
$table->engine = 'MyISAM';

Scroll to the bottom of this page: https://github.com/michaeldrennen/Geonames
Read the "Gotcha"

I did try that fix in the gotcha, like I said above, and still wasn't working.


Disable double write buffering in OpenSSL sockets

This fixes #7458 and #7456

I approve this because:

it apparently fixes two issues
I'm almost sure the code was supposed to match the comment, but it wasn't the case

@carlhoerberg Thank you!

I wonder if tests can be included for this. That way this stays working forever.

At least by including some manual specs (which are run before releasing, I think). This is in spec/manual

I don't know if it's reliable for all kind of things related to OpenSSL buffering, but for this case this code triggered it every time: https://github.com/crystal-lang/crystal/issues/7456#issuecomment-465319901


doc: update user and design documentation due to removal of AuthenticationFilter  and RateLimitFilter CRD resource.

What type of PR is this?
Documentation needs to be updated due to removal of AuthenticationFilter and RateLimitFilter CRD resource
What this PR does / why we need it:
Which issue(s) this PR fixes:
Releated
https://github.com/envoyproxy/gateway/pull/2079
Documentation needs to be updated due to removal of AuthenticationFilter CRD resource
#2196

@tmsnan this is the design doc, so we probably need to also update the design decisions mentioning that RateLimitFilter has been merged into the BackendTrafficPolicy

@tmsnan this is the design doc, so we probably need to also update the design decisions mentioning that RateLimitFilter has been merged into the BackendTrafficPolicy

Yes, Should we keep the rate-limit documentation by using subsetting, or should we remove it directly and only update it in the backend-traffic-policy?

/retest

Should we sync it also to site/content/en/v0.6.0 ?

Need to feed back to the already released v0.6.0 version.  In order to keep the document consistent, I will synchronize.


feature(mode): add mode choice and more log

Description

Now we can use cmd to debug this program locally.  By input arg likes -m local -f <filename>, the program can read from local file and fetch information from remote repo. A file called test_result.md will be generated locally, which writes all the changelog and no change to remote repo will be made. In addition, when the program runs, more detailed information about which step is finished will be printed for debugging. All work makes it easier for developer to debug locally and there is no change when the program runs on github.
Closes: #19
How Has This Been Tested

The local mode has been tested on my own PC and it works quite well.
The github mode has been tested on my own repo. There is no error detected.
Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[x] Code follows the code style of this project.
[x] Changes follow the CONTRIBUTING guidelines.
[x] Update necessary documentation accordingly.
[x] Lint and tests pass locally with the changes.
[x] Check issues and pull requests first. You don't want to duplicate effort.

Other information

another check, pls


feat(NavigationHeader): implement NavigationHeader component

Summary
Github issue: #816
Implements the NavigationHeader component for desktop and mobile
Checklist

[x] Default Story in Storybook
[x] LivePreview Story in Storybook
[x] Test Story in Storybook
[ ] Tests written
[ ] Variables from defaultTheme.ts used wherever possible
[ ] If updating an existing component, depreciate flag has been used where necessary
[ ] Chromatic build verified by @chanzuckerberg/sds-design

Looking great, thanks Jeremy!!
Some feedback below:

Logo Slot

Update color to Base/border for the dash border line around "logo slot"
Unbold the text "logo slot"

Tag

Update text inside the tags to title case
Remove the hover effect for the tags

Buttons

Update the "person" minimal button to a icon button (see design for the specific spec)

The entire area of "logo slot / logo name / beta tag" should be linked to the home page of the product. Not sure if this affects the code

Mobile Feedback
Logo

whole area should be a link

Secondary Nav Item

the whole row should be a target area - see spec for details
On hover, the background color of the whole row should have a gray (base/surface-secondary)
Secondary Nav Sub Item
the whole row should be a target area - see spec for details
On hover, bold the text with Narrow/fontBodyS/600 in addition to the background color change.

Buttons

the primary / secondary buttons / minimal button should extend to the whole row - see spec for detals
Use the S size of the person icon, the illustration is different from the larger size
bold the text - Narrow/fontBodyM/600

LGTM!!
Not a blocker, but IIRC many SDS components are wrapped in forwardRef() not sure if it makes sense to do it here too as a followup PR 😄
Thanks again!!

Actually React 19 is dropping ForwardRef! But we probably still need to add forwardRef until all of our projects upgrade to React 19 😁
https://react.dev/blog/2024/12/05/react-19


Need help with channel reference

My home app always displays my fist reference (goTV) when watching this IPTV stream:
log file:
[5/2/2020, 5:21:33 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Channel successful: Radio Regenbogen - Kinderlieder 4097:0:1:0:0:0:0:0:0:0:http%3a//streams.regenbogen.de/rr-kinderlieder-128-mp3:Radio Regenbogen - Kinderlieder

config:
{ "name": "Radio Regenbogen", "reference": "4097:0:1:0:0:0:0:0:0:0:http%3a//streams.regenbogen.de/rr-kinderlieder-128-mp3:Radio Regenbogen - Kinderlieder" }

Any Idea how to fix this?
Best regards

Just an idea...
delete
:Radio Regenbogen - Kinderlieder
From:
{ "name": "Radio Regenbogen", "reference": "4097:0:1:0:0:0:0:0:0:0:http%3a//streams.regenbogen.de/rr-kinderlieder-128-mp3:Radio Regenbogen - Kinderlieder" }
Result
{"name": "Radio Regenbogen", "reference": "4097:0:1:0:0:0:0:0:0:0:http%3a//streams.regenbogen.de/rr-kinderlieder-128-mp3}

Unfortunately still shows GoTV instead of... (using 2.6.28)
Any other idea? Did you try my reference in your tuner?
Best regards
config:
{ "name": "Radio Regenbogen", "reference": "4097:0:1:0:0:0:0:0:0:0:http%3a//streams.regenbogen.de/rr-kinderlieder-128-mp3" }

log:
[5/3/2020, 9:35:03 AM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Mute state: OFF
[5/3/2020, 9:35:03 AM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Volume level: 100
[5/3/2020, 9:35:06 AM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Power state successful: ON
[5/3/2020, 9:35:06 AM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Channel successful: Radio Regenbogen - Kinderlieder 4097:0:1:0:0:0:0:0:0:0:http%3a//streams.regenbogen.de/rr-kinderlieder-128-mp3:Radio Regenbogen - Kinderlieder

As U see Your old show different reference as Your config contain.

The first thing I tried was to copy from log to config, so it fully matched.
Since the Home App showed GoTV I decided to ask you, since I‘m running out of ideas...
Please have a look at the first post in this issue...
Is this working when you add the reference to your config?

Did you include this channel stream in your config bouqets? HomeKit only allows 97 inputs at the moment. Maybe if you didn’t configure this in you bouqets config the channel cannot be shown in HomeKit and shows the first option which is GoTV

Please find attached my full config.
PULS is the last reference, and this one is also shown correct in Home App.
Homebridge is reporting - Accessories: 56
config:
   {
      "platform": "OpenWebIfTv",
      "checkStateInterval": 5,
      "devices": [{
        "name": "Fernseher",
        "host": "<IP_ADDRESS>",
        "port": "80",
        "auth": false,
        "user": "root",
        "pass": "",
        "switchInfoMenu": true,
          "bouquets": [
            { "name": "gotv neu", "reference": "1:0:16:3404:3ED:1:C00000:0:0:0:" },
            { "name": "ORF1 HD", "reference": "1:0:19:132F:3EF:1:C00000:0:0:0:" },
            { "name": "ORF2N HD", "reference": "1:0:19:1334:3EF:1:C00000:0:0:0:" },
            { "name": "ORF III HD", "reference": "1:0:19:33FC:3ED:1:C00000:0:0:0:" },
            { "name": "ServusTV HD Oesterreich", "reference": "1:0:19:1331:3EF:1:C00000:0:0:0:" },
            { "name": "ATV HD", "reference": "1:0:19:33AC:3EB:1:C00000:0:0:0::ATV HD" },
            { "name": "ATV2", "reference": "1:0:1:33A7:3EB:1:C00000:0:0:0:" },
            { "name": "ProSieben", "reference": "1:0:1:445D:453:1:C00000:0:0:0:" },
            { "name": "Pro7 MAXX", "reference": "1:0:1:4461:453:1:C00000:0:0:0:" },
            { "name": "SAT.1", "reference": "1:0:1:445C:453:1:C00000:0:0:0:" },
            { "name": "VOX", "reference": "1:0:1:2F1C:441:1:C00000:0:0:0:" },
            { "name": "RTL Television", "reference": "1:0:1:2EE3:441:1:C00000:0:0:0:" },
            { "name": "NITRO", "reference": "1:0:1:2F1D:441:1:C00000:0:0:0:" },
            { "name": "RTLplus", "reference": "1:0:1:2F30:441:1:C00000:0:0:0:" },
            { "name": "RTL2", "reference": "1:0:1:2EF4:441:1:C00000:0:0:0:" },
            { "name": "SUPER RTL", "reference": "1:0:1:2F08:441:1:C00000:0:0:0:" },
            { "name": "PULS 4 Austria", "reference": "1:0:1:4E27:43A:1:C00000:0:0:0:" },
            { "name": "kabel eins", "reference": "1:0:1:445E:453:1:C00000:0:0:0:" },
            { "name": "kabel eins Doku", "reference": "1:0:1:4465:453:1:C00000:0:0:0:" },
            { "name": "WELT", "reference": "1:0:1:445F:453:1:C00000:0:0:0:" },
            { "name": "N24 DOKU", "reference": "1:0:1:30:5:85:C00000:0:0:0:" },
            { "name": "n-tv", "reference": "1:0:1:2F3A:441:1:C00000:0:0:0:" },
            { "name": "3sat HD", "reference": "1:0:19:2B8E:3F2:1:C00000:0:0:0:" },
            { "name": "arte HD", "reference": "1:0:19:283E:3FB:1:C00000:0:0:0:" },
            { "name": "KiKA HD", "reference": "1:0:19:2B98:3F2:1:C00000:0:0:0:" },
            { "name": "ZDF HD", "reference": "1:0:19:2B66:3F3:1:C00000:0:0:0:" },
            { "name": "zdf_neo HD", "reference": "1:0:19:2B7A:3F3:1:C00000:0:0:0:" },
            { "name": "ZDFinfo HD", "reference": "1:0:19:2BA2:3F2:1:C00000:0:0:0:" },
            { "name": "ANIXE HD", "reference": "1:0:19:526C:41D:1:C00000:0:0:0:" },
            { "name": "DMAX", "reference": "1:0:1:3F:21:85:C00000:0:0:0:" },
            { "name": "BR Fernsehen Süd HD", "reference": "1:0:19:2855:401:1:C00000:0:0:0:" },
            { "name": "ARD-alpha", "reference": "1:0:1:6F47:445:1:C00000:0:0:0:" },
            { "name": "Das Erste HD", "reference": "1:0:19:283D:3FB:1:C00000:0:0:0:" },
            { "name": "Disney Channel", "reference": "1:0:1:701:5:85:C00000:0:0:0:" },
            { "name": "tagesschau24", "reference": "1:0:1:7031:41B:1:C00000:0:0:0:" },
            { "name": "ONE HD", "reference": "1:0:19:2888:40F:1:C00000:0:0:0:" },
            { "name": "hr-fernsehen HD", "reference": "1:0:19:2873:425:1:C00000:0:0:0:" },
            { "name": "MDR S-Anhalt HD", "reference": "1:0:19:2871:425:1:C00000:0:0:0:" },
            { "name": "NDR FS SH HD", "reference": "1:0:19:285A:401:1:C00000:0:0:0:" },
            { "name": "SWR BW HD", "reference": "1:0:19:283F:3FB:1:C00000:0:0:0:" },
            { "name": "SIXX", "reference": "1:0:1:308:5:85:C00000:0:0:0:" },
            { "name": "phoenix HD", "reference": "1:0:19:285B:401:1:C00000:0:0:0:" },
            { "name": "rbb Berlin HD", "reference": "1:0:19:286F:425:1:C00000:0:0:0:" },
            { "name": "SR Fernsehen", "reference": "1:0:1:6F46:445:1:C00000:0:0:0:" },
            { "name": "WDR HD Bonn", "reference": "1:0:19:6F82:457:1:C00000:0:0:0:" },
            { "name": "SAT.1 Gold", "reference": "1:0:1:4460:453:1:C00000:0:0:0:" },
            { "name": "Comedy Central Austria", "reference": "1:0:1:3C:7:85:C00000:0:0:0:" },
            { "name": "NICKELODEON AT", "reference": "1:0:1:3D:7:85:C00000:0:0:0:" },
            { "name": "Eurosport 1 Deutschland", "reference": "1:0:1:79E0:443:1:C00000:0:0:0:" },
            { "name": "NICK/MTV+", "reference": "1:0:1:7008:436:1:C00000:0:0:0:" },
            { "name": "DELUXE MUSIC", "reference": "1:0:1:41:7:85:C00000:0:0:0:" },
            { "name": "TELE 5", "reference": "1:0:1:33:21:85:C00000:0:0:0:" },
            { "name": "ORF SPORT+ HD", "reference": "1:0:19:33FD:3ED:1:C00000:0:0:0:" },
            { "name": "Welt der Wunder", "reference": "1:0:1:332F:45B:1:C00000:0:0:0:" },
            { "name": "TOGGO plus", "reference": "1:0:1:2EFE:441:1:C00000:0:0:0:" },
            { "name": "Radio OE3", "reference": "1:0:2:334D:45B:1:C00000:0:0:0::OE3" },
            { "name": "Radio FM4", "reference": "1:0:2:334E:45B:1:C00000:0:0:0::FM4" },
            { "name": "Radio Antenne Bayern", "reference": "1:0:2:AA:7:85:C00000:0:0:0:" },
            { "name": "Radio Austria", "reference": "4097:0:1:0:0:0:0:0:0:0:http%3A//streamplus14.leonex.de%3A24954:Radio Austria" },
            { "name": "Radio Regenbogen", "reference": "4097:0:1:0:0:0:0:0:0:0:http%3a//streams.regenbogen.de/rr-kinderlieder-128-mp3:Radio Regenbogen - Kinderlieder" },
            { "name": "PULS", "reference": "1:0:2:6EF6:445:1:C00000:0:0:0:" }
          ]
        }
      ]
    }

log:
[5/3/2020, 9:01:30 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Mute state: OFF
[5/3/2020, 9:01:30 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Volume level: 100
[5/3/2020, 9:01:33 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Power state successful: ON
[5/3/2020, 9:01:33 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Channel successful: Radio Regenbogen - Kinderlieder 4097:0:1:0:0:0:0:0:0:0:http%3a//streams.regenbogen.de/rr-kinderlieder-128-mp3:Radio Regenbogen - Kinderlieder
[5/3/2020, 9:01:33 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Mute state: OFF
[5/3/2020, 9:01:33 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Volume level: 100
[5/3/2020, 9:01:36 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Power state successful: ON
[5/3/2020, 9:01:36 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Channel successful: PULS 1:0:2:6EF6:445:1:C00000:0:0:0:
[5/3/2020, 9:01:36 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Mute state: OFF
[5/3/2020, 9:01:36 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Volume level: 100
[5/3/2020, 9:01:39 PM] [OpenWebIfTv] Device: <IP_ADDRESS>, get current Power state successful: ON

It’s impossible for me to test this because I don’t have these ip channels. Is the regenbogen reference working if you set your tv to that input in HomeKit? Is your tv switching to the right channel?

Looking at your config I noticed the following
    { "name": "Radio Austria", "reference": "4097:0:1:0:0:0:0:0:0:0:http%3A//streamplus14.leonex.de%3A24954:Radio Austria" },                         { "name": "Radio Regenbogen", "reference": "4097:0:1:0:0:0:0:0:0:0:http%3a//streams.regenbogen.de/rr-kinderlieder-128-mp3:Radio Regenbogen - Kinderlieder" },
The name the first line here is Radio Austria this stream reference ends with ;Radio Austria.
The second item here has name Radio Regenbogen. But the stream ends with :Radio Regenbogen - Kinderlieder.
Maybe you have to change this and delete - Kinderlieder.
I also noticed the A not being a Captial letter.
Http%3A
Try changing this in your config, delete and add de tv to HomeKit and try again

Check latest version.

updated to 2.7.0 --> problem solved!
input is displayed in Home App as selected
THX and close


Constant temperature ensemble

Adds ability to run NVT ensembles
Added separate file NVT_Ar_config.yaml to run suitable constant temperature simulation.

Also removes some unused code or code that was in the simulate part but should be in the analyze part.


[🐛 Bug]:  Request fails when asset name start with 500 and 400

next-on-pages environment related information
No response
Description
This happens only when  if any asset contains name which start with error status codes .For example
http://abc.com/files/500-abc.pdf  this request fails. I recon it gets confused b/w error status pages.
Reproduction
Use above route pattern will reproduce bug.
Pages Deployment Method
None
Pages Deployment ID
No response
Additional Information
No response
Would you like to help?

[ ] Would you like to help fixing this bug?

@divyam234 thanks so much for the issue 🙂
it does look bizarre I'll have a look 👍
But anyways one quick question.... it looks to me like this only happens with 500s.... are you sure you've seen it with other numbers as well?

Correction, I think it only applies to 500s and 404s

Yeah 500 and 404


Make reason-react into a peer dependency.

Also updates reference to immutable-re repository.

Closing this, doesn't make sense anymore now that #45 has been merged.


[BUG] SCOPENPORTS reporting conflicts for system servers

Describe the bug
SCOPENPORTS reports a liveliness check.  It reports 2 errors on system definitions, for example, SSHD, FTP etc.
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:22':
system_sshd (System Secure Shell server)
sshd (System Secure Shell server)
To Reproduce
run scopenports
Expected behavior
not to show any conflict
Verbose output
Run the command with the -v option and share the output here.
scopenports -v
Initializing service myscript
Loading yaml service definition from file /QOpenSys/etc/sc/services/myscript.yml
Initializing service system_admin1
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_admin1.yaml
Initializing service system_admin2
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_admin2.yaml
Initializing service system_admin3
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_admin3.yaml
Initializing service system_admin4
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_admin4.yaml
Initializing service system_admin5
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_admin5.yaml
Initializing service system_ajs
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_ajs.yaml
Initializing service system_as-central
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_as-central.yaml
Initializing service system_as-database
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_as-database.yaml
Initializing service system_as-dtaq
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_as-dtaq.yaml
Initializing service system_as-file
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_as-file.yaml
Initializing service system_as-netprt
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_as-netprt.yaml
Initializing service system_as-rmtcmd
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_as-rmtcmd.yaml
Initializing service system_as-signon
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_as-signon.yaml
Initializing service system_as-sts
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_as-sts.yaml
Initializing service system_as-svrmap
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_as-svrmap.yaml
Initializing service system_cimom
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_cimom.yaml
Initializing service system_dbgsvr
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_dbgsvr.yaml
Initializing service system_ddm
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_ddm.yaml
Initializing service system_directoryserver
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_directoryserver.yaml
Initializing service system_ftp
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_ftp.yaml
Initializing service system_http_admin
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_http_admin.yaml
Initializing service system_lpd
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_lpd.yaml
Initializing service system_netserver
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_netserver.yaml
Initializing service system_pop
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_pop.yaml
Initializing service system_rmc
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_rmc.yaml
Initializing service system_slp
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_slp.yaml
Initializing service system_smtp
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_smtp.yaml
Initializing service system_sptprx
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_sptprx.yaml
Initializing service system_sshd
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_sshd.yaml
Initializing service system_telnet
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_telnet.yaml
Initializing service system_ypsjsvr
Loading yaml service definition from file /QOpenSys/etc/sc/services/system/system_ypsjsvr.yaml
Initializing service as-central
Loading yaml service definition from file /HOME/ANDY/.sc/services/as-central.yaml
Initializing service as-database
Loading yaml service definition from file /HOME/ANDY/.sc/services/as-database.yaml
Initializing service as-dtaq
Loading yaml service definition from file /HOME/ANDY/.sc/services/as-dtaq.yaml
Initializing service as-file
Loading yaml service definition from file /HOME/ANDY/.sc/services/as-file.yaml
Initializing service as-netprt
Loading yaml service definition from file /HOME/ANDY/.sc/services/as-netprt.yaml
Initializing service as-rmtcmd
Loading yaml service definition from file /HOME/ANDY/.sc/services/as-rmtcmd.yaml
Initializing service as-signon
Loading yaml service definition from file /HOME/ANDY/.sc/services/as-signon.yaml
Initializing service as-svrmap
Loading yaml service definition from file /HOME/ANDY/.sc/services/as-svrmap.yaml
Initializing service ddm
Loading yaml service definition from file /HOME/ANDY/.sc/services/ddm.yaml
Initializing service directoryserver
Loading yaml service definition from file /HOME/ANDY/.sc/services/directoryserver.yaml
Initializing service ftp
Loading yaml service definition from file /HOME/ANDY/.sc/services/ftp.yaml
Initializing service netserver
Loading yaml service definition from file /HOME/ANDY/.sc/services/netserver.yaml
Initializing service sshd
Loading yaml service definition from file /HOME/ANDY/.sc/services/sshd.yaml
Initializing service telnet
Loading yaml service definition from file /HOME/ANDY/.sc/services/telnet.yaml
Initializing service navigator
Loading yaml service definition from file /HOME/ANDY/.sc/services/navigator.yaml
Initializing service mariadb
Loading yaml service definition from file /HOME/ANDY/.sc/services/mariadb.yaml
Initializing service crond
Loading yaml service definition from file /HOME/ANDY/.sc/services/crond.yaml
Initializing service apache_framework
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_framework.yaml
Initializing service apache_helpdesk
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_helpdesk.yaml
Initializing service apache_students
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_students.yaml
Initializing service apache_ws_crm
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_ws_crm.yaml
Initializing service apache_apachedft
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_apachedft.yaml
Initializing service apache_f_files
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_f_files.yaml
Initializing service apache_f_contact
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_f_contact.yaml
Initializing service apache_f_crm
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_f_crm.yaml
Initializing service apache_f_mtd
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_f_mtd.yaml
Initializing service apache_f_quote
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_f_quote.yaml
Initializing service apache_f_support
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_f_support.yaml
Initializing service apache_f_train
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_f_train.yaml
Initializing service apache_intranet
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_intranet.yaml
Initializing service apache_iwadft
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_iwadft.yaml
Initializing service apache_school
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_school.yaml
Initializing service apache_t779
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_t779.yaml
Initializing service apache_ws_isws04
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_ws_isws04.yaml
Initializing service apache_ws_train
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_ws_train.yaml
Initializing service apache_zendsvr6
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_zendsvr6.yaml
Initializing service apache_zendsvr620160729085704
Loading yaml service definition from file /HOME/ANDY/.sc/services/apache_zendsvr620160729085704.yaml
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:1113':
apache_framework (Apache server Framework)
apache_f_support (Apache server f_support)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:1021':
apache_f_quote (Apache server f_quote)
apache_f_crm (Apache server f_crm)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:10083':
apache_zendsvr6 (Apache server zendsvr6)
apache_zendsvr620160729085704 (Apache server zendsvr620160729085704)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:8471':
as-database (System *DATABASE Host Server)
system_as-database (System *DATABASE Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:445':
netserver (System NetServer)
system_netserver (System NetServer)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:8470':
system_as-central (System *CENTRAL Host Server)
as-central (System *CENTRAL Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:446':
system_ddm (System DDM server)
ddm (System DDM server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:8473':
as-file (System *FILE Host Server)
system_as-file (System *FILE Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:8472':
system_as-dtaq (System *DTAQ Host Server)
as-dtaq (System *DTAQ Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:23':
system_telnet (System Telnet server)
telnet (System Telnet server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:8475':
system_as-rmtcmd (System *RMTCMD Host Server)
as-rmtcmd (System *RMTCMD Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:449':
as-svrmap (System *SVRMAP Host Server)
system_as-svrmap (System *SVRMAP Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:22':
system_sshd (System Secure Shell server)
sshd (System Secure Shell server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:8474':
system_as-netprt (System *NETPRT Host Server)
as-netprt (System *NETPRT Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:21':
ftp (System FTP server)
system_ftp (System FTP server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:8476':
as-signon (System *SIGNON Host Server)
system_as-signon (System *SIGNON Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'JOBNAME:QHTTPSVR/ADMIN2':
system_admin2 (IBM Navigator for i)
navigator (IBM Navigator for i)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:80':
apache_apachedft (Apache server apachedft)
apache_intranet (intranet)
Address          Port    'sc' service name (and friendly name)

Found pre-existing service for ad hoc specs: System FTP server
<IP_ADDRESS>          21      ftp (System FTP server)
Found pre-existing service for ad hoc specs: System Secure Shell server
<IP_ADDRESS>          22      sshd (System Secure Shell server)
Found pre-existing service for ad h.

Sorry for this. Please run sc_open_ports --cleanupv0 and see if that fixes it. I changed several things about how the system servers were handled, but if you ran sc_open_ports with v0.x, you can get conflicts

Thanks for that.  I am using;
Name        : service-commander
Arch        : ppc64
Version     : 1.1.0
but still getting 2 warnings for each server
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:22':
system_sshd (System Secure Shell server)
sshd (System Secure Shell server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:8474':
system_as-netprt (System *NETPRT Host Server)
as-netprt (System *NETPRT Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:21':
system_ftp (System FTP server)
ftp (System FTP server)
am I using the correct version?

v1.1.0 is best. The --cleanupv0 option should have cleaned up the definitions you had from an earlier release, but that doesn't seem to be the case. Did you get any errors when you ran with --cleanupv0?

no errors on running.
andy@GALATEA ~ $ scopenports --cleanupv10
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:8471':
system_as-database (System *DATABASE Host Server)
as-database (System *DATABASE Host Server)
WARNING: the following services all have conflicting definitions for liveliness check 'PORT:445':
netserver (System NetServer)
system_netserver (System NetServer)

Two things:

Sorry, the command I meant to ask  you to run is sc_install_defaults --cleanupv0 (oops!)
scopenports --cleanupv10 should have given you a warning since that's not a valid option for scopenports. I've opened #102 for that problem

What I believe happened here is:

You ran sc_install_defaults using service commander v0.x, which created the definitions not prefixed with _system
In v1.x, sc_install_defaults started prefixing those with system_
You ran sc_install_defaults with service commander v1.x, resulting in the conflicts
I didn't default to cleaning up those old ones by default because I didn't think anyone used sc_install_defaults with v0.x! (another oops)

thanks for the explanation.  sc_intall_defaults --cleanupv0 got rid of the majority of the duplicates, except.
WARNING: the following services all have conflicting definitions for liveliness check 'JOBNAME:QHTTPSVR/ADMIN2':
navigator (IBM Navigator for i)
system_admin2 (IBM Navigator for i)
Certainly a great cleanup.
I agree with your explanation of what I did (I think! )

Great!
This command should finish the fixup:
rm `sc file navigator`

I have opened issue #103 to track the missing file on cleanup.

All works fine now thanks.


Add physical properties

This PR can be closed since of lot of breaking changes are done to the master.
For now, focus on migrating only the following:


Add support for symfony/psr-http-message-bridge: ^6.4

Hopefully fixes #749 once Symfony 6.4 was tagged.

I can confirm that this change works. I updated a Symfony app to 6.4 and used my own fork of sentry/sentry-symfony that contained this exact change. Thanks.

Just tested as well and it works for me.

The root issue should be fixed by https://github.com/symfony/flex/pull/1003, but this change is still welcome (I'd suggest merging + releasing without waiting for 6.4-stable, that might make things a big smoother for end users.)

Released in 4.12.0


naming & directories

This is part of my review of the already merged #2; so see there for context.

Package name: spikeloc sounds good.
I solved the described problem (descriptive package name vs not wanting to have a long name repeated lots in a notebook using it) in my own PhD project by using an import alias: import voltage_to_wiring_sim as v (and then v.simulate(…).
You can then go as descriptive as you want (tab-completion in jupyter obsoletes typing long names in full).
Maybe go all the way in descriptiveness with shared_code_for_comob_snn_soundloc_project? :p
Instead of an import alias we can also go Brian-y and do from [our_package] import *, which is generally considered unpythonic, but for a jupyter notebook and homemade code with carefully curated automatic exports is fine. On the other hand, the big advantage of having namespaced objects is tab-completion: v.<tab>, and you get a list of the functions and types you can use. I.e. free api discoverability. (Has proved very useful, even if you wrote the package yourself!).

Directory names:
I propose naming the top level dir for shared code shared-code (or common-code,code, sth like that).
Someone reading the directory names then knows what's what (notebooks, shared-code, web).
The pyproject.toml / setup.py and package directory can then go inside that folder:
code/
    spikeloc/
        __init__.py
        …
    pyproject.toml
notebooks/
web/
…

For notebooks/, I was thinking people can also contribute just markdown files
instead of an .ipynb: JupyterBook builds these as well.
(They extended the common markdown with cross-references, citations, etc: 'MyST').
Use case I'm thinking of is e.g. someone doing a small lit review on a sub-topic.
(We could even draft parts of the paper, or the whole thing, in .md files compiled by JupyterBook).
Given that (namely that there's not only Jupyter Notebooks), maybe the dir name should change.
(notes, work, output, research-morsels? :p). But notebooks/ is probably
fine even when there's .mds in there.

Happy to use named and not * imports for this. For Brian we use * because we want to encourage absolute beginners, and because with lots of unit names it makes sense, but it's not the right approach here. I'm happy with spikeloc because I don't see it as being a heavily overloaded name, but still descriptive enough.
No strong feelings about directory structure so happy to go with @tfiers suggestion unless @synek or @ghoshm want to argue otherwise?

I think it makes sense to name the directory something self-explanatory, and spikeloc might not be intuitive. But I don't want to break open-source conventions, so maybe src/ is a reasonable middle ground? That's already a common choice. Using spikeloc is more the "poetry style", and src/ is more the older "pip style". Since we're dropping poetry, we don't need to follow its convention!
Regarding setup.py inside the source directory, that pattern is usually indicative of a "monorepo", which is where an org has multiple projects sharing a single repository (e.g. for microservices or something). Seeing a meta-file at the top-level of a repository is one of the implicit cues that people pick up on when they first open a project (or at least it is for me, I'd be a bit confused if I didn't see a setup.py or pyproject.toml at top-level).
In general, I don't think we should break open source conventions to "make things easier" for people. One of the goals of this project (I assume) is that participants learn how to collaborate on Github, and that includes learning the conventions of open source. If we teach them that code goes into shared-code and setup.py goes inside the source directory, then they will be confused when they look at other open source projects which follow the normal conventions. If it ain't broke, don't fix it.

I still have no strong feelings!

My proposal is to just stick with what we already have because it's there and I'd like to make progress! OK with everyone?


Implement backstopjs and Git LFS for visual regression testing

What is the context of this PR?
Replaces Percy with backstop js
How to review
Follow the readme
Testing - Visual regression tests
This project uses Backstop JS for visual regression testing. The tests run in Chrome headless using pupeteer inside docker and run in three viewports; 1920 (desktop), 768 (tablet) and 375 (mobile). Reference images are stored in Git LFS and any approved changes will automatically be stored in Git LFS when pushed to the repository.
The visual tests will run automatically on pull requests and the result will be available in the Github Action logs. If the tests fail, the process for viewing the failures and approving changes will need to be handled locally using the following workflow and commands.
The first time you run the tests locally you will need to install Git LFS on your machine. Follow the install instructions for Git LFS.
You will need to have Docker installed and started locally. We are using Docker as there are font rendering issues that caused failures across different os versions when we run the tests in CI. There is further information on this in the Backstop JS docs.
Checkout the branch locally and run:
git lfs checkout - This will pull the current reference images from the repository for you to test against.
yarn test-visual - This will run the same tests locally as were run in Github Actions. After they have completed the report will open in your default browser.
yarn test-visual:approve - This will approve the failures/diff caught by the tests and update the reference images locally on your machine.
git lfs push --all origin - First commit the files in the normal way then run the command. This will push the new reference images to Git LFS.
You can then commit and push your changes. The test images that would have been created when you ran yest test-visual are gitignored and the new references images will be pushed to Git LFS.

The section navigation snapshots don't look right. They no longer have sub sections?


Deleting a service that has just been deleted manually from Console fails

{"level":"info","ts":1572487334.5800693,"logger":"service","msg":"Error deleting resource","mytranslator":"Request failed with status code: 400, ServerErrorResponse: {"message":"Instance is already in pending_reclamation state.","status_code":400}\n"}
The controller doesn't recover from this

Fixed in v0.1.6


[Gardening][SR-2037] Documentation for Mirror.DisplayStyle missing a word

What's in this pull request?

A word.
Resolved bug number: (SR-2037)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci please test and merge.

Failure is unrelated.


Replace sed append with in place

https://github.com/neo4j-partners/amazon-cloud-formation-neo4j/pull/49
Replaced with echo


Thank you

This isn't an issue, but rather a thank you.
I love this little library. I think a simple templating library is exactly what the Rust community was lacking. Edo fills that void very nicely. thanks for sharing it with the community 🍻
I'll do my best to share it around.

Thanks, that means a lot. I would just like to point out however that this a super half baked project created to fill a need in another project that has since been put on hold (I've been really busy). It's probably broken in any manner of ways and I really don't have much time to maintain it right now.
That being said, if this helps you or anyone else, I'd be happy to accept any contributions.


Interventions [IG]

Formulation missing from intervention and alignment with IDMP.
See feature ticket #316
See JIRA 520

@czwickl : please see the updated IG for interventions for your review here: https://wiki.cdisc.org/display/USDMIGv4/Study+Interventions

Suggested edits for Study Intervention section of IG:
Paragraph 2:
For each administrable product optionally, information on the pharmacological class, and 1 or more identifiers, properties and ingredients may be specified. Each ingredient specified by its substance may have a reference substance, which is often, for example, used to indicate the identity, substance code,  and strength of the substance itself (as its own reference) or one of the moieties within a substance used as an ingredient (e.g., the free base/acid of the active pharmacologic component when its salt was added as the ingredient).
Paragraph 4:
Note that the internal sponsor code or compound number can be stored as the administrable product identifier.
The logic behind the proposed changes are:

The examples you showed sometimes showed the ingredient substance and the reference substance to be identical, even when they are salts (substance itself as its own reference; and sometimes the free base/acid moiety was used as the reference substance, which will have a separate identity, code, and strength.
I don’t think we should say anything about in vivo or about PK objectives, since these have more to do with what the body does to the product and is determined from analysis of biological specimens than it has to do with the administrable product itself.
The sponsor can assign the formulated product identifier and/or a compound number, but as a general rule we should avoid calling these drugs since a drug is really an approved product with an approved formulation, strength, and dosage form. I know there are examples where the term “drug” might be used in protocols, but strictly speaking, it is a “test article” or an “investigational new drug” and is only classified as a drug after the NDA is approved. Best to avoid the term as it’s not necessary in this case, but up to you.

@czwickl thank you for the review. Very helpful.

For the reference substance I have now copied the text from the IDMP IG as it is all about the active moiety. "The corresponding reference strength represents the strength (quantitative composition) of the active moiety of the active substance or of another substance used to express the strength of the product. There are situations when the active substance and active moiety are different resulting in different expression of the strength."
I left out the PK objectives as you suggested
I now added "of the administrable product" since that is also the name of the class it directly relates to and it is more specific.


Updating readme to recommend latest Core Tools to avoid issue

Updating readme to recommend latest Core Tools to avoid issue with Preview bundle not finding OpenAI triggers and bindings decorators
By updating to latest 4.0.6610 Azure Functions Core Tools version or higher, you will avoid this error:
[2024-12-13T21:13:00.240Z] Worker failed to index functions
[2024-12-13T21:13:00.242Z] Result: Failure
Exception: AttributeError: 'FunctionApp' object has no attribute 'text_completion_input'

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

@paulyuk Approved.


Update Readme.md information to match new configuration

Specifically, the references in "Building a configuration file".  Perhaps some later references as well.

This ticket is covering READMEs as lots of other documentation that has examples from the old config style.

@DStorck what should I be reviewing for this issue?

closed by https://github.com/samsung-cnct/k2/pull/380


Add Cosmic Eclipse initial Template

This PR adds the Cosmic Eclipse initial implementation template.  The previous closed PR did not have my latest commit where gen7 was tagged at the top which is required for testing on the dev server.

Hello @luongthomas the cards can now be tested on dev.tcgone.net


No mention of support or limitations for Public Folders mailboxes

I encountered an issue with one of our users recently and after I was able to consistently replicate that issue through testing, I'm led to believe that there are significant limitations with using Message Encryption with Public Folder mailboxes. The FAQ discusses limitations when using Shared Mailboxes but makes no mention of Public Folder mailboxes. It would be helpful to include a section on that and what limitations might be expected.
As an FYI, the issue identified above, was that while sending an encrypted email from a public folder mailbox is possible and is readable at the recipient's end; if the recipient replies back to that message, the following happens:

The email arrives but is not automatically decrypted and readable in the Public Folder. Instead, you see the " has sent to you a protect message" with a link to open it in a browser.
When clicking on that 'Read the Message' link, it tries to open an OWA sessions but never quite succeeds. Instead it gets stuck with a spinning wheel in the centre of the screen.

@KCCross Please help us in resolving this issue. Thanks

@denisebmsft - any chance you can help with this issue?
Thank you!!

Hi @yogkumgit. The correct writer to help with this is @KCCross

@KCCross Please update.

@andrew-harris Thanks for your feedback! New issues and pull requests for this content are closed while we update this content to support upcoming feature improvements.


CSP preventing LNC from working

https://stacker.news/items/653374?commentId=653466

It might be safe to add wasm-unsafe-eval considering all of other CSP stuff will prevent scripts that aren't ours from running?

I tried to get the prod build running locally to test if I can reproduce the issue. During development, we always use unsafe-eval because the dev build requires it for hot reload. This means that LNC might never have worked in prod but only locally thanks to unsafe-eval.
I unset grpc_proxy in .env.production, started required containers with sndev start db sn_lnd and then ran npm run build && PORT=3000 npm start but I got this error:
ApolloError: Cannot read properties of undefined (reading 'length')
    at new ApolloError (/home/ekzyis/prog/stacker.news/node_modules/@apollo/client/errors/errors.cjs:33:28)
    at /home/ekzyis/prog/stacker.news/node_modules/@apollo/client/core/core.cjs:1999:47
    at both (/home/ekzyis/prog/stacker.news/node_modules/@apollo/client/utilities/utilities.cjs:1347:31)
    at /home/ekzyis/prog/stacker.news/node_modules/@apollo/client/utilities/utilities.cjs:1338:72
    at new Promise (<anonymous>)
    at Object.then (/home/ekzyis/prog/stacker.news/node_modules/@apollo/client/utilities/utilities.cjs:1338:24)
    at Object.next (/home/ekzyis/prog/stacker.news/node_modules/@apollo/client/utilities/utilities.cjs:1349:49)
    at notifySubscription (/home/ekzyis/prog/stacker.news/node_modules/zen-observable/lib/Observable.js:135:18)
    at onNotify (/home/ekzyis/prog/stacker.news/node_modules/zen-observable/lib/Observable.js:179:3)
    at SubscriptionObserver.next (/home/ekzyis/prog/stacker.news/node_modules/zen-observable/lib/Observable.js:235:7) {
  graphQLErrors: [
    TypeError: Cannot read properties of undefined (reading 'length')
        at om (/home/ekzyis/prog/stacker.news/node_modules/@prisma/client/runtime/library.js:121:5438)
        at bl (/home/ekzyis/prog/stacker.news/node_modules/@prisma/client/runtime/library.js:121:5244)
        at _n.unpack (/home/ekzyis/prog/stacker.news/node_modules/@prisma/client/runtime/library.js:121:8476)
        at _n.mapQueryEngineResult (/home/ekzyis/prog/stacker.news/node_modules/@prisma/client/runtime/library.js:121:6943)
        at Object.singleLoader (/home/ekzyis/prog/stacker.news/node_modules/@prisma/client/runtime/library.js:121:6361)
        at async _n.request (/home/ekzyis/prog/stacker.news/node_modules/@prisma/client/runtime/library.js:121:6628)
        at async l (/home/ekzyis/prog/stacker.news/node_modules/@prisma/client/runtime/library.js:130:9355)
        at async itemQueryWithMeta (/home/ekzyis/prog/stacker.news/.next/server/chunks/7648.js:2119:19)
        at async Object.items (/home/ekzyis/prog/stacker.news/.next/server/chunks/7648.js:2160:93)
        at async Promise.all (index 1) {
      path: [Array],
      locations: undefined,
      extensions: [Object: null prototype] {}
    }
  ],
  protocolErrors: [],
  clientErrors: [],
  networkError: null,
  extraInfo: undefined
}

Apparently, itemQueryWithMeta triggers it but no idea which line exactly.
Reading what MDN has to say about unsafe-wasm-eval, I also think it's safe to add it:

The 'wasm-unsafe-eval' source expression controls WebAssembly execution. If a page has a CSP header and 'wasm-unsafe-eval' isn't specified in the script-src directive, WebAssembly is blocked from loading and executing on the page.
The 'wasm-unsafe-eval' source expression is more specific than 'unsafe-eval' which permits both compilation (and instantiation) of WebAssembly and, for example, the use of the eval operation in JavaScript. If the 'unsafe-eval' source keyword is used, then this overrides any occurrence of 'wasm-unsafe-eval' in the CSP policy.


⚠ Fortnite has degraded performance

In b373787, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1554 ms

Resolved: Fortnite performance has improved in f23e882.


pls add feature where in code i will gave the path and type and get list of files.

Hi, thank you for the suggestion, but I don’t quite get what you’re asking for.
May you provide an example?

Since there's not enough info on this, I'm closing it. Feel free to reopen if you have more details of what you're suggesting.
Thank you.


DS-590 Notifications component

Jira
https://pegadigitalit.atlassian.net/browse/DS-590
Summary
Adds a Notifications component to display user notifications.
Details

Twig template is built out without JS. Notifications JS will be handled on the Drupal side.
Changed Switch Button's on prop to follow conventions. Boolean props default to false.

How to test
Run the branch locally and check the Notifications docs. Make sure all props work as expected.

Approved, updated tests. I will merge once this passes.


[tempest] cinder-volume is not configured add more tests to skip

the following two tests fail due to missing cinder-volume being configured:

tempest.scenario.test_server_volume_attachment.TestServerVolumeAttachScenarioOldVersion
tempest.scenario.test_server_volume_attachment.TestServerVolumeAttachmentScenario

failing in openstack-operator-tempest-multinode job in https://github.com/openstack-k8s-operators/openstack-operator/pull/665 is failing on volume test , e.g. for tempest.scenario.test_server_volume_attachment.TestServerVolumeAttachmentScenario.test_server_detach_rules . from https://logserver.rdoproject.org/65/665/13c490f50624d9b9d1ff01d179c804a55044c16f/github-c[…]re.openstack.org/openstack-galera-network-isolation.yaml it seems cinder-volume is configured with 0 replicas.
The logs from a PR merged 2 days ago don't list this test and cinder-volume has also 0 replicas there https://review.rdoproject.org/zuul/buildset/1563314b7bd64b418182d2c643944afc /   https://logserver.rdoproject.org/62/662/fc54bdbb0d187b039903e5f423565f6823076283/github-c[…]oller/ci-framework-data/tests/tempest/podman_tempest.log

seems https://github.com/openstack-k8s-operators/openstack-operator/pull/643 hits the same issue https://logserver.rdoproject.org/43/643/5e2f93424e08ccfa1dc73d9f6c9364fa66015ee1/github-c[…]oller/ci-framework-data/tests/tempest/podman_tempest.log


Update for 1.6.x?

Great project!
Any hopes of an update for 1.6.x?
(or/and more platforms?)

I do plan on updating to 1.6, but I'd like to wait until all bugs are fixed first, and I have a lot of other stuff to do at the moment, so it may take some time unfortunately.
I'll message in this thread with any progress, so feel free to follow there :)


Update Services on Staging to have a Message Limit of 100

We want to minimize the SMS costs that come through our Staging environment. Currently VEText is the only customer using SMS and their limit is 1000/day.

[x] Update all services from 1000 to 100
[ ] Update code default for message limit to 100
[x] Update instructions for creating services to have this new value
[x] Communicate to the team

NOTE: If updating the code is non-trivial please open a new ticket.

Hey team! Please add your planning poker estimate with ZenHub @ianperera @jakehova @jessecanderson @k-macmillan @kalbfled @maham360 @EvanParish

Updated all services from 1000 to 100, the instructions for creating a service already has '100' as default value listed in the instructions, need to update code default for message limit to 100

When I check out Postman 100 is what it defaults to in the body. To finish this out you should just create a service in Dev and ensure that it actually set it to 100. May be no need for code/postman changes!

Created service "mahamservice" in Dev, sent "get service" request and it returned "100" in the message limit.


Add CLI command for binding a catalog entry to a workspace

The kcp-catalog bind command will bind a catalog entry to a workspace
by creating a singular or multiple APIBinding using ExportReference
listed in spec.Exports in the catalog entry.
For example, consider the command:
kcp-catalog bind catalogentry root:catalog:catalogentry-sample
Every export referenced in catalog entry-sample in root:catalog workspace will have an APIBinding created referencing it.
Design doc: https://docs.google.com/document/d/1J31wXY1-2aCyyGFjUlusKoHDzV-zktAmRdIMjMf4OR0/edit

@varshaprasad96 got this error with your PR:
make
test -s /Users/angoldst/code/kcp/catalog/bin/controller-gen || GOBIN=/Users/angoldst/code/kcp/catalog/bin go install<EMAIL_ADDRESS>/Users/angoldst/code/kcp/catalog/bin/controller-gen rbac:roleName=manager-role crd webhook paths="./..." output:crd:artifacts:config=config/crd/bases
Error: err: exit status 1: stderr: go: downloading github.com/kcp-dev/controller-runtime v0.12.2-0.20220808200255-4b60fd66e5de
go: downloading github.com/kcp-dev/kcp v0.9.1
go: downloading golang.org/x/tools v0.1.10
go build github.com/kcp-dev/kcp/pkg/openapi: build constraints exclude all Go files in<EMAIL_ADDRESS>

Adding snippets of the command after creating it locally:
When catalog entry is created successfully:
➜  catalog git:(bind-cli)  ./kcp-catalog bind catalogentry root:catalog:catalogentry-sample
Apibinding created and bound to catalog entry catalogentry-sample.

When binding already exists on cluster:
➜  catalog git:(bind-cli)  ./kcp-catalog bind catalogentry root:catalog:catalogentry-sample
Found an existing APIExport cert-manager-stable-dx467 pointing to the same export reference.
Apibinding created and bound to catalog entry catalogentry-sample.

When there is an error while creating a binding (intentionally):
➜  catalog git:(bind-cli)  ./kcp-catalog bind catalogentry root:catalog:catalogentry-sample
error: bindings for catalog entry catalogentry-sample could not be created successfully: resource name may not be empty

I have a follow up PR that have tests for these. After #5 gets merged, will open it.

/test

go build github.com/kcp-dev/kcp/pkg/openapi: build constraints exclude all Go files in<EMAIL_ADDRESS>
The error above and in CI was because controller-gen was not accepting files under cmd/ which had deps with build dependencies like (openapi). I have modified the controller-gen args in the makefile target to accept what we want. Now the following works - make test, make build and make install:
➜  catalog git:(bind-cli) make test
test -s /Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/controller-gen || GOBIN=/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin go install<EMAIL_ADDRESS>/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/controller-gen rbac:roleName=manager-role crd webhook paths="./controllers/...;./api/..." output:crd:artifacts:config=config/crd/bases
/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./api/..."
go fmt ./...
go vet ./...
test -s /Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/setup-envtest || GOBIN=/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin go install sigs.k8s.io/controller-runtime/tools/setup-envtest@latest
KUBEBUILDER_ASSETS="/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/k8s/1.25.0-darwin-amd64" go test ./... -coverprofile cover.out
?   	github.com/kcp-dev/catalog	[no test files]
?   	github.com/kcp-dev/catalog/api/v1alpha1	[no test files]
?   	github.com/kcp-dev/catalog/cmd/kcp-catalog	[no test files]
?   	github.com/kcp-dev/catalog/cmd/kcp-catalog/bind/catalogentry	[no test files]
ok  	github.com/kcp-dev/catalog/controllers	0.408s	coverage: 0.0% of statements

➜  catalog git:(bind-cli)  make install
test -s /Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/controller-gen || GOBIN=/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin go install<EMAIL_ADDRESS>/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/controller-gen rbac:roleName=manager-role crd webhook paths="./controllers/...;./api/..." output:crd:artifacts:config=config/crd/bases
test -s /Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/kustomize || { curl -Ss "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh" | bash -s -- 3.8.7 /Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin; }
/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/kustomize build config/crd | kubectl apply -f -
customresourcedefinition.apiextensions.k8s.io/catalogentries.catalog.kcp.dev created

➜  catalog git:(bind-cli) make build
test -s /Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/controller-gen || GOBIN=/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin go install<EMAIL_ADDRESS>/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/controller-gen rbac:roleName=manager-role crd webhook paths="./controllers/...;./api/..." output:crd:artifacts:config=config/crd/bases
/Users/vnarsing/go/src/github.com/kcp-dev/catalog/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./api/..."
go fmt ./...
go vet ./...
go build -o bin/manager main.go

@varshaprasad96 great, thanks! Would you be able to squash the commits down (e.g. to get rid of ones named wip 😄)?

@ncdc need a lgtm again to continue merging.


OpenAIEmbeddings to core module

OpenAIEmbeddings shouldn't be part of OpenAI module because it doesn't depend on any openai stuff. This PR is moving this class to the core module. I'm refactoring the names of some classes:

OpenAIEmbeddings now is EmbeddingsProvider on core module
com.xebia.functional.xef.llm.Embeddings now is LLMEmbeddings in order to avoid conflicts with com.xebia.functional.xef.embeddings.Embeddings and be clearer on the names
GcpEmbeddings was removed. We are using EmbeddingsProvider on GCP

If someone has a better names for that, please let me know

Considering the scope of the issue, LGTM.
Possible renames for EmbeddingsProvider I can think of are EmbeddingsStrategy and EmbeddingsService.
For another issue, I suggest making the embedQuery function an extension function that calls embedDocuments, as it is just a special case of the latter until now.
Additionally, the chunkSize should be passed in the constructor of EmbeddingsProvider and not be part of the Embeddings interface function signature, as the chunk size is specific to this implementation.
These are just my humble thoughts.


A check needs to be in place to ensure that there is an 'audit=1' parameter added to the kernel

Without this, auditing is not guaranteed to be started at the earliest possible moment during the boot sequence.

chef/inspec#2197 is relevant to this
@jburns12 You may want to take a swipe at this if you have time.

What control is this part of?

The best I can find is the RHEL 6 STIG V-38438 which is exactly what you are describing. I do not see a similar control for RHEL 7 (Lookin in the latest 2.2 January 2019).

While this is probably a good thing to have configured in general I don't think we want to be validating things that aren't mandated in the STIG.


support project lighthouse community levels for il races

should work on any lighthouse instance as long as it uses the default website layout
hopefully i didnt mess anything up

Why did you decide against having the URL in the level name? (as it was for lbp.me)

Why did you decide against having the URL in the level name? (as it was for lbp.me)

not entirely sure, changed it back to how it was before

https://github.com/kadiwa4/bingo-bot/blob/0c8ddcbd804abfada531b62d6b173af56a046037/src/command_modules/race_control.js#L510-L514
i would prefer to do this differently but im not sure how


[feature][pulsar-broker]: Add additional servlet support to broker

Motivation
Currently the broker does not support additional servlet, but some plugins need to add custom web routes on the broker.
Modifications
Add additional servlet support to broker
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

@Demogorgon314 thanks for your great work. Would you like to add docs accordingly? Then you can ping me to review, thanks

@Demogorgon314 thanks for your great work. Would you like to add docs accordingly? Then you can ping me to review, thanks

I think maybe we only need to add docs in the specific plugin?

@BewareMyPower @codelipenghui
I've discussed w/ @Demogorgon314 and we have the following issues. Could you please help answer? Thanks

If we want to add docs for this PR, the docs are targeted for the developers who want to develop a plugin (for example, KoP), should we add this kind of docs to the Development chapter on the Pulsar doc website?

@BewareMyPower after you developing KoP, did you write this kind of docs? If so, where did you add? Thanks

@Anonymitaet AFAIK, there's no related docs. IMO, I agree to add this kind of docs to the Development chapter on the Pulsar doc website.

/pulsarbot run-failure-checks

@Demogorgon314 thanks for your great work. Would you like to add docs accordingly? Then you can ping me to review, thanks

@Demogorgon314 thanks for your great work. Would you like to add docs accordingly? Then you can ping me to review, thanks
Thanks, I will add the docs later when I finish my work at hand.

Confirmed w @codelipenghui, @Demogorgon314 could you please help add the parameter and its description here (https://pulsar.apache.org/docs/en/next/reference-configuration/#broker) before EOD 8/9？Then you can ping me review, thanks

@Anonymitaet The docs is added in #11590 , please help me review, thanks.


Koalas DataFrame should only have Pandas corresponding APIs (not Spark APIs)

This is partially of https://github.com/databricks/koalas/issues/119
I was thinking Koalas DataFrame strictly should have Pandas corresponding APIs, although there might be few exceptions with some strong reasons.
Meaning Koalas DataFrame should not have Spark DataFrame specific APIs like explain() or selectExpr(). My current thought is we have a API like koalas_df.to_spark() (borrowed from @ueshin's idea via offline discussion) so that users can use Spark APIs.
Koalas API usages
koalas_df.loc(...)
koalas_df.drop(...)  # works as Pandas API

Spark API usages
koalas_df.to_spark().explain()
koalas_df.to_spark().selectExpr()
koalas_df.to_spark().drop(...)  # works as Spark API

This can clearly define what Koalas APIs expect and Spark APIs expect.

I think that users should be able to pick what they need, in particular things like .cache() or .repartition() which can be necessary. Doing koala_df.to_spark().cache().to_koalas() looses the index and metadata, so it is a no-go. Other users should also chime in though.

I'd prefer to separate API.
Since pandas has the same name functions as Spark, even the primitive ones, select, filter/where, then users can't pick the preferable one and will be confused by the APIs from the different origin.
Also what if pandas adds the same name function in the future?
I'd propose spark property which handles Spark APIs but try to preserve indexes as far as possible:
kdf.select(...)  # works as the same as pandas dataframe
kdf.spark.select(...)  # works as similar to spark dataframe but preserves index as far as possible, and return koalas dataframe
kdf.to_spark().select(...)  # drops out from Koalas, returns spark dataframe and select on it

Yes, I agree with @ueshin. If there's no choice, then I think https://github.com/databricks/koalas/issues/139#issuecomment-485728893 is the last resort.
But I was thinking the goal of this project is to let Pandas users can directly be able to use PySpark without any efforts. Since the targeted users are Pandas users, they might not use PySpark's APIs quite often.

I agree that we should not put everything. That being said, some of them are very helpful, simply because they do not have any equivalent in pandas and are very common in spark. Here is how we can start:
Unscoped (directly in DataFrame or Series):

select and selectExpr. This is very useful for quickly building expressions, and pandas has even a dialect for doing that. We should have a separate thread about how much we accept here.
very common functions like alias, join

Unscoped or scoped (no particular preference here). Expected to return a Koalas dataframe:

SQL-related: crossJoin, crosstab, hint etc.
understanding the underlying representation: printschema, schema
specify the memory layout (at least the core functions): cache, repartition

Scoped or only available through conversion with .toDF(). Expected to return a scalar, Series, pd.DataFrame or spark.DataFrame

streaming-related: withWatermark, isStreaming
big-data related: approxquantiles -> should actually return a pd.Series and should probably be scoped then.

@thunterdb, how about we start from: Koalas to have Pandas corresponding APIs only and provide an API like to_spark() first? I think this will be the subset of https://github.com/databricks/koalas/issues/139#issuecomment-485728893 and/or https://github.com/databricks/koalas/issues/139#issuecomment-485789617 anyway later.
a) this way is pretty clear to dev and users as the starting point too. b) we can decide which way is better later, and can adopt the actual user's expectation later easily

cc @rxin too to collect more feedback.

This is a tough one -- to be honest I think we can pick something safer, and try to use this more, get feedback, and then it might become more obvious what we should do.

Closing this as it will be part of the design philosophy doc.


git-stack Crash Report

Please complete the following tasks

[X] I have searched the discussions
[X] I have searched the existing issues

Description
This happened after I manually rebased one of my branches onto another one (because git sync kept unstacking them for some reason).
Crash report:
"name" = "git-stack"
"operating_system" = "Ubuntu 22.04 (jammy) [64-bit]"
"crate_version" = "0.10.17"
"explanation" = """
Panic occurred in file '/home/k/.cargo/registry/src/index.crates.io-6f17d22bba15001f/git-stack-0.10.17/src/graph/mod.rs' at line 88
"""
"cause" = "expected to contain 0afa2350991de3407cf98c76392ebad4f9095135"
"method" = "Panic"
"backtrace" = """

   0: 0x5633d5ed27a3 - git_stack::graph::Graph::rebase::hf9de67616fcf33b8
   1: 0x5633d5ed78e0 - git_stack::graph::ops::rebase_development_branches::hcd0d2c01e25b416d
   2: 0x5633d5dfc739 - git_stack::sync::plan_changes::he5b349d14baa3572
   3: 0x5633d5dfb1d5 - git_stack::args::Args::exec::h0ee9e87692bf6d7e
   4: 0x5633d5e16bfd - git_stack::run::h878e0dbdfec63a8f
   5: 0x5633d5e16424 - git_stack::main::hbb474cdebae09508
   6: 0x5633d5e3a313 - std::sys_common::backtrace::__rust_begin_short_backtrace::h8421f852f1a20e08
   7: 0x5633d5e3a329 - std::rt::lang_start::{{closure}}::h0eec47e08d1127ac
   8: 0x5633d61528c1 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h37600b1e5eea4ecd
                at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/ops/function.rs:284
                 - std::panicking::try::do_call::hb4bda49fa13a0c2b
                at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:552
                 - std::panicking::try::h8bbf75149211aaaa
                at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:516
                 - std::panic::catch_unwind::h8c78ec68ebea34cb
                at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panic.rs:142
                 - std::rt::lang_start_internal::{{closure}}::hffdf44a19fd9e220
                at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/rt.rs:148
                 - std::panicking::try::do_call::hcb3194972c74716d
                at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:552
                 - std::panicking::try::hcdc6892c5f0dba4c
                at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:516
                 - std::panic::catch_unwind::h4910beb4573f4776
                at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panic.rs:142
                 - std::rt::lang_start_internal::h6939038e2873596b
                at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/rt.rs:148
   9: 0x5633d5e1abe5 - main
  10: 0x7fa9fca29d90 - <unresolved>
  11: 0x7fa9fca29e40 - __libc_start_main
  12: 0x5633d5dbb1e5 - _start
  13:        0x0 - <unresolved>"""

Version
No response
Steps to reproduce
No response
Actual Behaviour
No response
Expected Behaviour
No response
Debug Output
No response

Thanks for reporting this!
Do you have any more context as to what your commit graph looked like and what operation you were performing?  Having the exact command line can be a big help.

Unfortunately I've lost track of the commit graph when this happened but this is roughly what I was doing:

I was working on a different computer and pushed a branch feature1 to remote.
I pulled that branch on another computer, and started a new branch stacked on top of the feature1 branch. Let's call it feature2.
For some reason whenever I called git sync it kept marking feature1 as a branch authored by someone else (my git email might have been different. I did a git commit --amend to try to solve this but it kept happening on that branch for some reason.
I manually rebased feature2 onto feature1 with git stack --rebase feature2 --onto feature1. For some reason this would get undone when I did another git sync.
Eventually I manually rebased stuff with git rebase but then this happened when I did git sync.

I was able to fix it somehow by doing a bunch of rebases, but I'm not entirely sure what fixed it.


Dashboard never loads.  Just sits on "Loading"

Running on Azure DevOps Server.

Dev tools shows me an error with the API call:

Hi @EmKayUltra,
Currently, the extension requires the version 5.2 of the APIs and your Azure DevOps Server uses 5.1. Do you know if you are able to upgrade the server to a newer version?
This seems to be related to #36 Pull Request. Unfortunately, I did not have enough time to test its impacts by downgrading the extension's version to 5.1.

This is Azure DevOps Server, running the latest update.  I don't think that on-prem DevOps supports API 5.2

Fixed #47

It now loads.  However, the hyperlinks on the dashboard don't seem to work.  When I click on a hyperlink to view a PR, I am presented with this:
{"$id":"1","innerException":null,"message":"The extension 'caribeiro84.pull-request-manager-hub' doesn't contain the requested asset type 'build/undefinedBAC/_git/HUSDMS.Common/pullrequest/166' in version '1.20191123.1'.","typeName":"Microsoft.VisualStudio.Services.Gallery.WebApi.ExtensionAssetNotFoundException, Microsoft.VisualStudio.Services.Gallery.WebApi","typeKey":"ExtensionAssetNotFoundException","errorCode":0,"eventId":3000}

I believe I know what happened. I'm now dynamically fetching the organization's URL but I forgot the OnPrem version the URL host is not dev.azure.com. I will work on this week! Sorry for this silly mistake.

@EmKayUltra,
I'm releasing a new version with the URL handling for OnPrem instance. Hope this fix the issues you are facing.

I'm closing this issue, feel free to reopen in case the problem is not gone yet.
Thanks a lot

With your latest update, we're back to the original problem of it just sitting on loading.

Let's reopen it again :-)
It seems now the same error but in a different place. I've introduced a new API call to fetch the organization URL (Cloud version). This call may causing this issue. Let me investigate it again and hopefully I will have a new version pretty soon.
Sorry for this.

@EmKayUltra - I have bad news! I just tried to downgrade the API version to the one that uses the version 5.1 of the Azure DevOps APIs and it's breaking all the extension. Unfortunately, I won't be able to downgrade it at this moment.
I will be looking for alternatives that I could make it compatible with the OnPrem Azure DevOps.

When you originally downgraded to 5.1 before (to fix the original problem), it worked great and the API error disappeared.  Did that change break the extension for everyone else?

I just released a new version (and new features) and also added the error handling when it calls APIs higher than your server supports. Would you be able to test it? I hope I could fix this annoying error for you!

Sure, but I'm not seeing a new version in the Azure marketplace yet.

That’s strange. It’s showing for me and also available working on my company’s account.
Would you mind to check again?

Got the update.  Loads again.  Hyperlinks still don't work.
{"$id":"1","innerException":null,"message":"The extension 'caribeiro84.pull-request-manager-hub' doesn't contain the requested asset type 'build/undefinedMyTeamName/_git/MyRepoName/pullrequest/95' in version '1.20191129.1'.","typeName":"Microsoft.VisualStudio.Services.Gallery.WebApi.ExtensionAssetNotFoundException, Microsoft.VisualStudio.Services.Gallery.WebApi","typeKey":"ExtensionAssetNotFoundException","errorCode":0,"eventId":3000}

Is there anything in the console of the browser? How the URL of your server is composed?
Thanks a lot

Nothing of note in the console.  The url that shows that exception (which the individual PR hyperlinks point to) is: https://MY_DOMAIN.com/tfs/_apis/public/gallery/publisher/caribeiro84/extension/pull-request-manager-hub/1.20191129.1/assetbyname/build/undefinedMY_TEAM_NAME/_git/MY_REPO_NAME/pullrequest/95
where the normal hyperlink to access the PR would be https://MY_DOMAIN.com/tfs/MY_COLLECTION_NAME/MY_TEAM_NAME/_git/MY_REPO_NAME/pullrequest/95

Got it, I will try to work with this information. My main issue at this moment is the lack of documentation from Azure DevOps Server APIs. I did not find anything related to capture its resources with the internal APIs. :-(
I'm really sorry about it but be sure I'm working to fix it asap.
Thank you so much for providing the additional details.

@EmKayUltra - I just released a new version trying to force the TFS URL based on the hostType when it's different of 4 (Cloud) and also from the URL Referrer that comes during the call to the extension. I hope this gets finally fixed :-)
Would you mind (sorry again for asking it) to test?

Unfortunately...
"$id":"1","innerException":null,"message":"The extension 'caribeiro84.pull-request-manager-hub' doesn't contain the requested asset type 'build/undefinedBAC/_git/EIHub/pullrequest/95' in version '1.20191202.1'.","typeName":"Microsoft.VisualStudio.Services.Gallery.WebApi.ExtensionAssetNotFoundException, Microsoft.VisualStudio.Services.Gallery.WebApi","typeKey":"ExtensionAssetNotFoundException","errorCode":0,"eventId":3000}

:-(
Would you be able to run a DEV mode extension to debug it? If so, I can add your organization to the dev mode extension I have (not public) and then you could clone this repo and then run the following commands:

npm install
HTTPS=true react-scripts start

If you agree, is it possible to send me (can be privately) your org's name or an account you have so you can download it?

In meantime I will try to install the Server version on my azure account and test it. :-)

Hi!  It's been a week, and I wonder if you've had any luck repro'ing.  Unfortunately, I can't run the dev mode extension at the moment.  Although I can probably make that happen in the coming days if it's still needed.

Yes, I was able to create my "OnPrem" Azure DevOps Server instance but I'm still debugging it to try to identify the issue. Hopefully in the following days I'll have the fix for it :-)

@EmKayUltra - I just released a new version after I created my own AzDevOps Server instance and it seems I was able to fix the URL issue. Could you please test it again? I'm looking forward for the feedback. :-)

Looks like the URL works now 👍 Awesome!
I know you've done a lot of work on this, and I appreciate it.  Is there any way you can change the links so they don't open in a new window?

@EmKayUltra I'm really glad to know that! Thanks a lot for the feedback.
About your question, this behavior is intentional because the idea is to highlight the latest PR you clicked in order to facilitate for you to remember where you left (last PR). I have in the backlog new improvements and one of them is to add some Preferences panel for you to configure the behaviors you prefer to have. Stay tuned :-)

Also, if you don't mind, please give your rate about this extension. :-)
https://marketplace.visualstudio.com/items?itemName=caribeiro84.pull-request-manager-hub&ssr=false#review-details


Draw tile data into the tilemap cache and ui layer

Need to be able to draw tile data into the tilemap cache and ui layer like drawing sprites

This has been added


Optimize vote reward data

Problem
Close #2844
Solution
https://github.com/neo-project/neo/issues/2815#issuecomment-1259916590
Test
GAS balances
GAS balances are compared
through FindStates and GetState at specific height by https://github.com/ZhangTao1596/NeoUtil/blob/4eb7f0bb9f8cbef30216bb597d3b2da328d222e8/Compare/GasComparer.cs#L83
Sync

network & config
branch
chains size
sync time (h:m)

mainnet fullstate
master
28G
2:27

this patch
25G
2:15

fs mainnet fullstate
master
9.3G
1:17

this patch
8.6G
1:11

testnet fullstate
master
6G
0:42

this patch
4.8G
0:37

mainnet lateststate 2911479
master
4.5G
6:10

4.6G
7:45

4.6G
6:29

this patch
4.2G
4:06

4.2G
4:10

BoltDB mainnet fullstate
master
49G
22:11

this patch
43G
18:09

Gas balances retest today on Testnet.

Can you also check NeoFS mainnet sync? The config is in config/protocol.mainnet.neofs.yml. Another thing to try is BoltDB, it's somewhat different. And KeepOnlyLatestState to see if it affects this as well.

@ZhangTao1596, I see there are some new numbers there and these numbers are good. But it'd be even better if we're to be notified about them, you can post a comment here when you update something. BoltDB is still of interest, we use it a lot.
Other than that let's see how neo-project/neo#2841 goes, I'd really like it to be a part of the standard protocol, but we can also accept it as a useful extension.

BoltDB is still of interest, we use it a lot

I'm still testing bloltdb sync. But it seems performance is poor with boltdb and I met an out of memory problem.
It only takes nearly 2hours when sync mannet with leveldb while boltdb takes around 10hours.
I will add new comment when test finished.

Huh. That's interesting. Depending on config it can be slower/faster (like in https://neospcc.medium.com/cutting-blockchain-tail-with-neogo-5256a120f6bb), but usually OOM is not a problem.

Mainnet fullstate sync with BoltDB

branch
sync time
data size

master
22:11
49G

this patch
18:09
43G

@ZhangTao1596, could you, please, rebase this PR onto the current master and fix the failing test I mentioned earlier? We'd like to merge this PR.

@ZhangTao1596, could you, please, rebase this PR onto the current master and fix the failing test I mentioned earlier? We'd like to merge this PR.

Done.

and
TestRPC/http/single_request/invokefunctionhistoric/positive,_by_stateroot

and
TestRPC/http/single_request/invokefunction/positive,_with_storage_changes

Why gitflow doesn't fail? 🤔

Why gitflow doesn't fail?

It actually fails, see the logs of https://github.com/nspcc-dev/neo-go/actions/runs/4749984725/jobs/8437756522?pr=2892 for example.

It's OK, don't be scared, all these tests are bound to the state data somehow, and it's clear that this PR changes state related data. It's not hard to fix, start with updating block20StateRootLE constant from the RPC server tests. After that there's a invokefunction/positive,_with_storage_changes test that compares storage data, it needs to be adjusted also.

TestNEO_GetAccountStateInteropAPI Failed. I think it's because this branch still depends on master pkg/interop.
Same result on my machine:

I suggest

use go.work to orginize modules to solve these self dependency problem, look:
 Glad to find out that we update go version to 1.8. I'm used to use replace in go.mod to test locally changes and remove it before commit.

only log FAIL tests in github workflow.

@AnnaShaleva how do you think?

TestNEO_GetAccountStateInteropAPI Failed

It's OK for it to fail, I'll update interop dependencies in a separate PR after merge.

use go.work to orginize modules

Let's leave it for https://github.com/nspcc-dev/neo-go/issues/2982, looks useful to me.

only log FAIL tests in github workflow

Also useful, let's make it in a separate PR.