added May data files and read w/ Jupyter notebook

Probably should create a new folder.
Protoype reader doesn't follow CookieCutter path conventions. Everything is just right in /code.
Any need to separate julia/python/matlab code?

boiler plate missing for tests.

My cookiecutter template is a work in progress.  I actually tried to get rid of all of the tests.  The template I originally cloned had them (https://github.com/jbusecke/cookiecutter-science-project).  I have been gradually editing the template to be more of a bare bones repo that incorporates some best practices for reproducible science.

i couldn't (figure out how to) make new folders in the github repo. i guess that makes sense since it's a clonable diffable version of a repo that each of us could have on our local pc. so "refactoring" directories in a git repo is another unknown for me.
i don't understand the 4 generations of data. perhaps it accommodates some good data mgmt practices. if revising paths, one can migrate from little data-adjacent reader codes to libraries of higher level analysis on more organized and refined data sets. like i said though, i don't know how to revise the paths.

From: Tom Farrar @.>
Sent: Wednesday, September 28, 2022 6:46 AM
To: jtomfarrar/submersible_humidity_sensor @.>
Cc: de Szoeke, Simon @.>; State change @.>
Subject: Re: [jtomfarrar/submersible_humidity_sensor] added May data files and read w/ Jupyter notebook (PR #1)
[This email originated from outside of OSU. Use caution with links and attachments.]
Any need to separate julia/python/matlab code?
I would say not now. We could do it later if needed.
—
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjtomfarrar%2Fsubmersible_humidity_sensor%2Fpull%2F1%23issuecomment-1260941834&data=05|01|simon.deszoeke%40oregonstate.edu|6bfdc84737764257b3c308daa157e510|ce6d05e13c5e4d6287a84c4a2713c113|0|0|637999696117352083|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2B24f2q52DwHePvFXw4GPCBr45jg4zXbN34geVswvGTc%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADE4O4YEFUT24ROJR3N6IBDWARD4TANCNFSM6AAAAAAQXMNQLM&data=05|01|simon.deszoeke%40oregonstate.edu|6bfdc84737764257b3c308daa157e510|ce6d05e13c5e4d6287a84c4a2713c113|0|0|637999696117352083|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=NuQSniFlDJ8jUHuVviTnadWKSgheXAqWzNjDtQcCAJo%3D&reserved=0.
You are receiving this because you modified the open/close state.Message ID: @.***>


copilot

[Enter feedback here]

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

ID: 79c8bed6-42a2-4690-bf26-d034800025a7
Version Independent ID: 79c8bed6-42a2-4690-bf26-d034800025a7
Content: Overview - Microsoft Copilot Studio
Content Source: power-virtual-agents/fundamentals-what-is-copilot-studio.md
Service: copilot-studio
GitHub Login: @iaanw
Microsoft Alias: iawilt

Thanks for your comment, @manjulamahes. This issue has been assigned to the doc author for review.


sub class of OpenAdmin\Admin\Grid\Selectable

I'm trying to use a relation based on documentation from Open Admin.
My Model Files :
App\Model\Contact.php

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;

class Contact extends Model
{
    protected $table = 'contact';
}

App\Model\WorkObject.php
<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\Eloquent\SoftDeletes;

class WorkObject extends Model
{
    use SoftDeletes;

    protected $table = 'work_object';

    public function contact()
    {
        return $this->belongsTo(Contact::class);
    }

}

App\Model\ConatctSelect.php

<?php

namespace App\Admin\Selectable;

use App\Models\Contact;
use OpenAdmin\Admin\Grid\Filter;
use OpenAdmin\Admin\Grid\Selectable;

class ContactSelect extends Selectable
{
    public $model = Contact::class;
    public static $display_field = "contact";

    public function make()
    {
        $this->column('Name');
        $this->column('company');
        $this->column('phone');
        $this->column('email');

        $this->filter(function (Filter $filter){
            $filter->like('name');
            //$filter->like('company');
            //$filter->like('phone');
            //$filter->like('email');
        });
    }
}

Controller file:
<?php

namespace App\Admin\Controllers;

use App\Admin\Selectable\ContactSelect;
use App\Models\Contact;
use OpenAdmin\Admin\Controllers\AdminController;
use OpenAdmin\Admin\Form;
use OpenAdmin\Admin\Grid;
use OpenAdmin\Admin\Show;
use \App\Models\WorkObject;

class WorkObjectController extends AdminController

//------

protected function grid()
    {
        $grid = new Grid(new WorkObject());

       //
        $grid->column('contact_id', 'Osoba kontaktowa')->belongsTo(ContactSelect::class);
       //

        return $grid;
    }

//------

protected function form()
    {
        $form = new Form(new WorkObject());
       //
        $form->belongsTo('contact_id', ContactSelect::class, 'Osoba kontaktowa');
       //

        return $form;
    }

Im getting error of list and add new objetc
InvalidArgumentException In BelongsTo.php line 54 :
[Class [App\Admin\Selectable\ContactSelect] must be a sub class of OpenAdmin\Admin\Grid\Selectable
Everything looks fine but the error keeps coming back. I have verified several times that the item is entered correctly and that there are no typos.
This is my first question here so forgive me for the confusion and maybe not professionally asked question.
The ContactSelect class is in namspace and has an extend Selectable. How to solve this bug. I am using Laravel v10.13.5 and Open Admin v1.0

Change this in App\Model\ConatctSelect.php, make an alias (use OpenAdmin\Admin\Grid\Selectable as AdminSelectable; ) and use that:
<?php

namespace App\Admin\Selectable;

use App\Models\Contact;
use OpenAdmin\Admin\Grid\Filter;
use OpenAdmin\Admin\Grid\Selectable as AdminSelectable;

class ContactSelect extends AdminSelectable
{
    public $model = Contact::class;
    public static $display_field = "contact";

    public function make()
    {
        $this->column('Name');
        $this->column('company');
        $this->column('phone');
        $this->column('email');

        $this->filter(function (Filter $filter){
            $filter->like('name');
            //$filter->like('company');
            //$filter->like('phone');
            //$filter->like('email');
        });
    }
}

I`m guessing the problem lies in the name of the file, so likely it won't even find the class.
App\Model\ConatctSelect.php
is not compatible with you namespace
namespace App\Admin\Selectable;
move your file to:
App\Admin\Selectable\ConatctSelect.php


[NETBEANS-1074] Module Review languages.apacheconf

Change the licesne of license.txt
Add ApacheConfTemplate.conf to the licenseinfo.xml because it is a template file
Add ApacheConfExample.conf to the licenseinfo.xml because it is an example file
Add skeleton.netbeans to the licenseinfo.xml because it does not support comments

could we just remove it?

I think so, will remove it.

Removed it.

Thanks, merging.


Allow multi indexing

Pull Request
What does this PR do?
Closes #15
PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

What's inside this PR ?

Renaming of the field queries into indexes
The indexes field is now an array and allows us to provide multiple indexes and queries for indexation
Separation of the validatePluginOptions in 2 functions : validatePluginOptions for the global plugin options, and validateIndexOptions for the validation of each indexes options
Update of the playground plugin config to pass the indexes as an array
Update of each tests name for better understanding of what it should do
Update of the tests with the new naming (indexes) + addition of a new test testing the multi-indexation

How to test ?

yarn test
yarn playground:dev and update the playground/gatsby-config.js by adding a second index (see example below). By going to your MeiliSearch's mini-dashboard (http://<IP_ADDRESS>:7700/ for me), you should see that the 2 indexes were created. You can also edit the INDEX_NAME inside playground/src/pages/index.js and see the changes on http://localhost:9000/

Example of second index :
 {
            indexUid: 'index2',
            transformer: data => data.allMdx.edges.map(({ node }) => node),
            query: `
              query MyQuery {
                allMdx {
                  edges {
                    node {
                      id
                    }
                  }
                }
              }
            `,
          },

bors merge

bors merge


enhanced add_electrical_series

fix #196
Motivation
Allowing user control over write options for ecephys electrical series in order to speed the process in certain cases.
How to test the behavior?
New tests have been added for each option, as well as time reporting for write speed comparison.
!pytest

Checklist

[X] Have you checked our Contributing document?
[X] Have you ensured the PR description clearly describes the problem and solutions?
[X] Is your contribution compliant with our coding style? Read about PEP8 and black.
[X] Have you checked to ensure that there aren't other open or previously closed Pull Requests for the same change?
[X] Have you included the relevant issue number using #XXX notation where XXX is the issue number?

@bendichter This PR should be ready for review now.
I was thinking of adding some util functions that allow users to estimate NWB write speed on their given system with specified data types and write/parallelization options to help them understand how long it should take them to convert a given RecordingExtractor ahead of time, but that will all be in a subsequent PR.

@bendichter This PR should be ready for review now.
I was thinking of adding some util functions that allow users to estimate NWB write speed on their given system with specified data types and write/parallelization options to help them understand how long it should take them to convert a given RecordingExtractor ahead of time, but that will all be in a subsequent PR.

Granted, the changes we talked about with specification of Chunk size and enhancement of the underlying DataChunkIterator are not a part of this PR; I'm thinking a subsequent PR would be best given how technically focused that change will be.

@bendichter Added direct tests of final compression to confirm it went through as expected. Anything else to do here?


Push-to-Talk button not accessibility enabled

Blind users can't really use the app because of this.

I have done a bit to aid this and submitted a pull request.

3D Touch for push to talk on screen would help. Feeling it tap when you toggle on and off would make for a great user experience and aid accessibility.


trying to connect to existing mysql database

Describe the bug
[root@CentOS-73-64-minimal prisma]# prisma deploy
environment FetchError: request to http://localhost:4466/management failed, reason: connect ECONNREFUSED <IP_ADDRESS>:4466
datamodel.prisma seems to be created correctly, does Prisma support existing MySQL databases yet ? I saw that this was a problem like 1 year ago, but I suppose you made it support importing from existing database since datamodel.prisma is generated and it seem that prisma init worked.
Seems that the docker image created with docker-compose up -d keeps restaring it-self.
I can never attach to it because it keeps restarting. Error in docker-compose logs is
prisma_1  | Exception in thread "main" java.lang.RuntimeException: Unable to load Prisma config: com.prisma.config.InvalidConfiguration: Only Postgres connectors specify a schema. If they do they also need to specify a database. Other connectors only specify a database. prisma_1  | 	at scala.sys.package$.error(package.scala:26)
if I remove the schema from docker-compose.yml I get another error
prisma_1  | Exception in thread "main" java.lang.RuntimeException: There is not passive mysql deploy connector yet!    | 	at scala.sys.package$.error(package.scala:26)
docker-compose.yml file with schema:
version: '3'
services:
  prisma:
    image: prismagraphql/prisma:1.32-alpha
    restart: always
    ports:
    - "4466:4466"
    environment:
      PRISMA_CONFIG: |
        port: 4466
        # uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
        # managementApiSecret: my-secret
        databases:
          default:
            connector: mysql
            host: <IP_ADDRESS>
            user: dbusername
            schema: dbpassword
            password: 'pass'
            rawAccess: true
            port: '3306'
            migrations: false

Notice mysql server is on different server but when I run prisma init prisma the setup wizard connects to the mySQL server and retrives the correct databases and I choose an existing one.
[root@central ~]# mysql --version
mysql  Ver 14.14 Distrib 5.5.45, for Linux (x86_64) using readline 5.1
Versions (please complete the following information):

Connector: MySQL
Prisma CLI version: prisma/1.32.0-alpha.3 (linux-x64) node-v10.15.2
also tried with last stable prisma first then upgraded to alpha
server is on CentOS 7 , remote server hosting mySQL db is CentOS 6

@mrtornado
In MySQL schema is synonymous with the database, so schemas are only consumed by postgres.
So can you please change schema to database in your config

If I change schema to database the error there is no passive db connector, but connector is set to mysql.
prisma_1  | Exception in thread "main" java.lang.RuntimeException: There is not passive mysql deploy connector yet!

Can confirm @mrtornado issue.

I also got the same error and I'm using version v1.31 because I notice that in the last release note the introspection for MySQL databases was supported. (https://spectrum.chat/prisma/general/releasing-prisma-v1-31~0d4dcb59-a58f-4ecf-84e6-b8509bad4abf)

I can reproduce @mrtornado issue.
Looking at the documentation, it seems that MySQL is not supported.
But if so, why is it offered as an option?

It's supported on the last version (v1.31) and here is the documentation: https://www.prisma.io/docs/1.31/datamodel-and-migrations/introspection-MYSQL-soi2/

yea it should be supported but something seems to be wrong.

i have the same issue...

same issue here as well

Same issue here

I encountered 2 issues when using prisma with an existing MySQL DB:
(1) on introspection, prisma init correctly retrieves DB name , but creates docker-compose.yml with 'schema: ' rather than 'database: '
(2) after  'schema: ' is substituted with 'databes: ' in docker-compose.yml, and 'docker-compose up -d' is run, prisma tries to connect to DB=prisma, not DB= and throws:
Access denied for user 'user_name'@'IP_addr' to database 'prisma'

My tags were omitted so I'll re-post:
I encountered 2 issues when using prisma with an existing MySQL DB:
(1) on introspection, prisma init correctly retrieves DB name as XXX, but creates docker-compose.yml with 'schema: XXX' rather than 'database: XXX'
(2) after 'schema: XXX' is substituted with 'databes: XXX' in docker-compose.yml, and 'docker-compose up -d' is run, prisma tries to connect to DB=prisma, not DB=XXX, and throws:
Access denied for user 'user_name'@'IP_addr' to database 'prisma'

I am not able to reproduce any of this now with 1.32. The CLI issue of writing schema instead of database property is still persistent but it is being tracked by another issue: https://github.com/prisma/prisma/issues/4434
@g1t1n Make sure that your MySQL user has full DB access. Prisma will need to create "prisma" database in your MySQL server in order to store metadata information about the migrations

Closing as duplicate of https://github.com/prisma/prisma/issues/4434

@pantharshit00 What if database creation is not allowed? Is it necessary, can it be circumvented?
Also, as docker-compose.yml created by prisma introspection has "migrations: false" why is migration enforced?
version: '3'
services:
prisma:
image: prismagraphql/prisma:1.32
restart: always
ports:
- "4466:4466"
environment:
PRISMA_CONFIG: |
port: 4466
# uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
# managementApiSecret: my-secret
databases:
connector: mysql
host: <IP_ADDRESS>
database: regus
user: regus_provisioning
password: .5(9QQ)uYuX+asGR
rawAccess: true
port: '3306'
migrations: false

I encountered 2 issues when using prisma with an existing MySQL DB:
(1) on introspection, prisma init correctly retrieves DB name , but creates docker-compose.yml with 'schema: ' rather than 'database: '
(2) after 'schema: ' is substituted with 'databes: ' in docker-compose.yml, and 'docker-compose up -d' is run, prisma tries to connect to DB=prisma, not DB= and throws:
Access denied for user 'user_name'@'IP_addr' to database 'prisma'

this help


Update JS/CSS libs

Should update this to use newer technologies probably. But this at least gets octobot off really old versions of things.


Update mandatory sample attributes for sample file changes

Motivation and Context

The format of social sample file is changing for the LMS pilot, these changes allow the new format of sample file to be loaded and stored.
What has changed

Changed the mandatory columns for social sample files
Updated tests for new mandatory column set

How to test?

Run acceptance tests against services using this version

Links

https://trello.com/c/3PK5xIDM/238-sample-file-changes-for-operational-test-8
https://github.com/ONSdigital/rm-sample-service/pull/72

 Sample file changes for Operational Test (8)


Codeunit 12 - OnBeforeRun... Events are using emtpry records

The Events OnBeforeRunWithCheck and OnBeforeRunWithoutCheck are using an unitialized local record GenJnlLine.
It should raised after GenJnlLine.Copy(GenJnlLine2).
    procedure RunWithCheck(var GenJnlLine2: Record "Gen. Journal Line"): Integer
    var
        GenJnlLine: Record "Gen. Journal Line";
    begin
        OnBeforeRunWithCheck(GenJnlLine);

        GenJnlLine.Copy(GenJnlLine2);
        Code(GenJnlLine, true);
        OnAfterRunWithCheck(GenJnlLine);
        GenJnlLine2 := GenJnlLine;
        exit(GLEntryNo);
    end;

    procedure RunWithoutCheck(var GenJnlLine2: Record "Gen. Journal Line"): Integer
    var
        GenJnlLine: Record "Gen. Journal Line";
    begin
        OnBeforeRunWithoutCheck(GenJnlLine);

        GenJnlLine.Copy(GenJnlLine2);
        Code(GenJnlLine, false);
        OnAfterRunWithoutCheck(GenJnlLine);
        GenJnlLine2 := GenJnlLine;
        exit(GLEntryNo);
    end;

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


refactor(tabset): use proper camelCase directives

Hey @pkozlowski-opensource correct me if I am wrong, but shouldn't we code tabset like this?

You are probably right. What do we have in the style guide for this?

"Do Use lower camel case for naming the selectors of our directives."
We normally put all attribute selectors as camelCase, but this one is a bit of an advanced case.
Still, I see stuff like <template ngSwitchWhen...>. It is not the saaame selector a the end, but still camelCase.


[WIP] feat(service): add cloud debugger service

Please do not review this pull request until I remove the WIP. This is just for final evaluation purposes.

I will close this one for now, one day we can reopen it and finish it.
Eugene thanks a lot for your effort! Feel free to comment this PR anytime when you would like to continue this work.


Datepicker with an empty ng-model

Cannot have a datepicker with an empty ng-model because it shows invalid date or the current date. I think it would be a good idea to have an option to specify if I want to have a value when the model is initialized (with the current date) or an empty object (or string). There are some cases (such as having a form where the input field related to the datepicker is not required) when it is not necessary to select a date; it is confusing then that the current date appears always in the input field. I made a workaround for this and modified the code below sending an empty string in the function "formatter". This is only a workaround but I think a functionality like this will add value to your component.
function formatter(value) {
return value != ""  ? dateFilter(value, format, timezone) : "";
}

+1

#199

Would be fixed by PR https://github.com/g00fy-/angular-datepicker/pull/293


Weapon workbench wrong rotation axis/placement

(1)When choosing weapon workbench in the build menu for placement (either on ship decoration or outpost),
axis of its rotation is on the front end of the workbench, instead of the center of the object like the other items.
(2)When placing inside the ship, the weapon workbench's bottom does not stick onto the floor, and it gets built half buried into the floor.

Details
Tried purging mods from Nexus but the problem continued.
(few mods from the official Creation was still active, but they were downloaded ages ago)
No mod that alter the weapon workbench is used (unless there is something which affects it unintentionally).
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Open the build menu on outpost or inside owned ship, then find and choose weapon workbench

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

I can confirm this issue. Not sure what is causing it though.
The data record for this furniture object has not changed since the last update. Changing the model that this workbench uses to another one (such as the armor bench) makes it possible to place correctly, however using the weapon workbench model from a previous update does not correct it.
Needs investigated further.


Allow to display a conversion

Pass a conversion name along (e.g. 'thumb') to display a converted image rather then original.

if no conversion provided: return empty string (will display the original image)
if conversion doesn't exist on collection: return empty string (will display the original image)
if conversion exist: profit

Great, thanks :)


Differences in GWT WebGL2 vs WebGL1 rendering

Can I help?  Is it a shader issue?  From my investigation it looks it gets shaders from gdx-gtlf.  Do I need to open an issue on gdx-gltf?
Rendering on GWT with WebGL2 (useGL30 = true;)

Rendering on GWT with WebGL1 (useGL30 = false;)

No differences on desktop.

Directly related to https://github.com/JamesTKhan/Mundus/issues/240


io-sim and io-sim-classes changes towards publication on Hackage

Please use a spell checker. This is going on Hackage and hopefully attract some attention.

That's not finished yet, anyway thanks for proof reading.

Please use a spell checker. This is going on Hackage and hopefully attract some attention.

That's not finished yet, anyway thanks for proof reading.

You're welcome. It's one of my pet peeves :slightly_smiling_face:.

This is massive enough for a review.

Related to #2608

bors merge


draft up with monorepo

I've been scratching my head for the past week on how I can use Draft in a mono repo. Has anybody got any advice on this?
At the moment I have a directory structure like this.
/gateway
---/charts
/services
--/service-1
-/charts
--/service-2
-/charts
--/service-3
-/charts
Ideally I want to bring up all of these services during development from a single command and monitor their logs in one log stream rather than have to run draft up and have 4 terminal tabs open. I can do this out of the box using Skaffold.
I'm starting to think that I need to use Skaffold for this functionality and then use Helm to package up my service.

Possibly duplicate of #902?

yep. thanks.


Bigger textures data than need.

Right?

Also need write 256 short value before palette (something like palette size?) it requires in some cases.

I don't know, padding (4 bytes align?) is really needed ?

@wootguy this is mistake in code


Create a Maintainers Committee discussion category

In the discussions, each committee seems to have its own category for dumping things like meeting notes, general discussion, or whatever else.
One of these should probably be created for the maintainers committee.

We will need to investigate, GitHub seems to not allow more than 10 categories per repository.

Yeah I think it'd make sense to have per-committee discussions anyway, there's a lot of general chatter on the home repo (which I guess is what it's for) whereas committee discussions are (hopefully) a lot more focused.

There's now a maintainers category 👍
https://github.com/dotnet-foundation/Home/discussions/categories/maintainers-committee


using Trixi crashes due to missing symbol _clock_gettime

On Julia v1.7.2, loading Trixi.jl main branch crashes with the following stack trace
julia> using Trixi
[ Info: Precompiling Trixi [a7f1ee26-1774-49b1-8366-f1abc58fbfcb]
dyld: lazy symbol binding failed: Symbol not found: _clock_gettime
  Referenced from: /Users/panalluri/.julia/artifacts/1de252c3f8c1eeb3c18189b1a27222e8dc806171/lib/./libpmpi.12.dylib
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _clock_gettime
  Referenced from: /Users/panalluri/.julia/artifacts/1de252c3f8c1eeb3c18189b1a27222e8dc806171/lib/./libpmpi.12.dylib
  Expected in: /usr/lib/libSystem.B.dylib

signal (11): Segmentation fault: 11
in expression starting at REPL[7]:1
jl_exit_thread0_cb at /Applications/Julia-1.7.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.dylib (unknown line)
Allocations: 40477897 (Pool: 40466764; Big: 11133); GC: 27

signal (11): Segmentation fault: 11
in expression starting at REPL[7]:1
jl_exit_thread0_cb at /Applications/Julia-1.7.app/Contents/Resources/julia/lib/julia/libjulia-internal.1.dylib (unknown line)
Allocations: 40477897 (Pool: 40466764; Big: 11133); GC: 27

This is a Mac laptop with an intel CPU, OSX 10.11.6

This happens for both the main branch and the latest release.

This is a 2016 Macbook laptop for reference. Not sure why there is such different behavior - everything works fine on my current Macbook Pro. Maybe old version of OSX?

clock_gettime was not implemented prior to OS X 10.12. I have not found any definitive resource on this, but it seems to be the consensus on the interwebs, e.g., here, here, or here. Thus you should upgrade your OS X to at least 10.12 and also your Xcode SDK to 10.12 to have support for it.

Thanks!

Did updating your OS help? Can we close this issue?

We haven't updated the OS yet. We can close this issue - I'll reopen it if we still have issues after updating.


falky: TestEGUpgrade/EGUpgrade

https://github.com/envoyproxy/gateway/actions/runs/8896241845/job/24429998115

this one failed on eg_upgrade.go:78: Failed to upgrade the release: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/envoyproxy/gateway-helm/blobs/sha256:529769988b9569b5e7b005df7ad6d2b7ccfdded07d2f374a08b91eadaaa6e2d2: 503 Service Unavailable, looks like docker issue?

this one failed on eg_upgrade.go:78: Failed to upgrade the release: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/envoyproxy/gateway-helm/blobs/sha256:529769988b9569b5e7b005df7ad6d2b7ccfdded07d2f374a08b91eadaaa6e2d2: 503 Service Unavailable, looks like a docker.io connectivity issue?

if so, should retry.

closed in favour of https://github.com/envoyproxy/gateway/pull/3764


Fixes broken markdown in OAuth2 section

As per the picture below:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Any blockers to get this merged?

Wow, I even forgot about this one...


Failed to upgrade to 0.9

When updating ghost, it looks lit successfully deployed but it won't load anything.
iisnode was unable to establish named pipe connection to the node.exe process before the process terminated

I've seen this too, for some reason the package 'moment-time' (I think) failed to install on checking the logs.
The only way I could get round it was to deploy into a staging slot and upgrade that manually (npm install --production) via the kudu console, then copy my database over.

I looked at the logs and saw errors on some libraries under node_modules, such as
ERROR: Cannot find module 'lodash/object/assign'
or
  Cannot find module 'har-validator'
  Cannot find module 'has-ansi'
  Cannot find module 'hawk'
  Cannot find module 'hoek'
  Cannot find module 'html-to-text'
  Cannot find module 'htmlparser2'
  Cannot find module 'http-signature'
  Cannot find module 'iconv-lite'
  Cannot find module 'ini'
  Cannot find module 'intl'
  Cannot find module 'intl-messageformat'
  Cannot find module 'is-my-json-valid'
  Cannot find module 'jodid25519'
  Cannot find module 'jsbn'
  Cannot find module 'json-stringify-safe'
  Cannot find module 'jsonpath'
  Cannot find module 'jsonpointer'
  Cannot find module 'jsprim'
  Cannot find module 'knex'
  Cannot find module 'lodash'
  Cannot find module 'mime-db'
  Cannot find module 'mime-types'
  Cannot find module 'minimatch'

I fixed it by removing node_modules folder in Kudu console, then rebuild again. I did have a staging slot where I tested 0.9 first, and didn't really wanna solve it by copying my database over and promoting that one as my production.


accessing the request object

In starlette you can access request object  in function decorated with the route decorator.
it seems very handy to be able to access middlewares etc,
is there a way in fastapi to do that using the provided get/post/options.... decorators?
same question for the ApiRouter.
@app.route("/notes", methods=["GET"])
async def list_notes(request):
    query = notes.select()
    results = await request.database.fetchall(query)

Yes! It's not properly documented yet.
It's pretty much what (I guess) you would expect. Declare it with a Starlette Request type and FastAPI will provide it:
from fastapi import FastAPI
from starlette.requests import Request

app = FastAPI()

@app.get("/")
def read_root(request: Request):
    query = notes.select()  # Not sure where `notes` comes from
    results = await request.database.fetchall(query)
    return {"Hello": results}

omg this rocks, I think my attempt at using the async postgresql will be
soon up!
Le ven. 1 févr. 2019 à 9:40 PM, Sebastián Ramírez<EMAIL_ADDRESS>a écrit :

Yes! It's not properly documented yet.
It's pretty much what (I guess) you would expect. Declare it with a
Starlette Request type and FastAPI will provide it:
from fastapi import FastAPIfrom starlette.requests import Request
app = FastAPI()
@app.get("/")def read_root(request: Request):
query = notes.select()  # Not sure where notes comes from
results = await request.database.fetchall(query)
return {"Hello": results}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tiangolo/fastapi/issues/19#issuecomment-459860605,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDZPmZuQ3qnbVexqJaiAs2SnnbZdAuKks5vJKZBgaJpZM4ae_ub
.

:tada: :taco:


Add Liviu Enache to contributors

[x] Add member to CONTRIBUTORS.md (top level)  - PR for the list changes #7677
[x] Add member to organization contributors group
[ ] Issue badge
[x] Notify member

Invited Liviu to contributors group (he needs to respond, and join the odpi github organization. ANy problems let me know)

cc @LeeVi3w

@LeeVi3w Your badge should now be issued to the email address in https://github.com/odpi/egeria/blob/main/CONTRIBUTORS.md -- can you confirm you have it ok?

Closing. please re-open if there are any issues


Some fixes

@CornyjK thank you for the help, however, I don't understand the changes in the clean up commit

@CornyjK thank you for the help, however, I don't understand the changes in the clean up commit

I like no newlines at the end of files, I can remove it if you wish.


Examples are placed later in the article

https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs#resource-specific
This section on top states "The preceding example creates three tables:", however, the examples are added in the later section. Please rearrange the contents for reader's convenience. Thanks

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

ID: fa75a1e5-a1c7-ca5d-7fbc-8a932c429f70
Version Independent ID: f86cd80a-c337-3f2f-a7d6-02f03331f4f9
Content: Azure resource logs - Azure Monitor
Content Source: articles/azure-monitor/essentials/resource-logs.md
Service: azure-monitor
Sub-service: essentials
GitHub Login: @EdB-MSFT
Microsoft Alias: edbaynash

@jaesoni Thanks for your comment! We will review and provide an update as appropriate.

Thanks @jaesoni, I've updated the article.
#please-close


chore: split up plurals and other arrays/mod

chore
Split plurals.rs (JArrays, ArrayPair), word.rs (Word), empty.rs (HasEmpty) and error.rs (JError) off arrays/mod.rs, leaving it mostly empty.
This also changes JArrays over to a view, but the code change here is tiny.

This looks good, was there anything else you wanted to do here before I merge it?


Api parsing

Checklist

[x] I have read the coding guide.
[ ] My change requires a documentation update, and I have done it.
[ ] My change requires updating the Open API specification and/or changing its version, and I've done it.
[x] I have added tests to cover my changes.
[ ] I have filled out the description and linked the related issues.

Description

Motivation and context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):

This change is

when this is merged make sure the title says something like fix: api parsing and validation

Closed in favor of #3344


Page not available

Problem description

Problem location

I saw a problem on the following URL:

I couldn't find the information I wanted. I expected to find it near the following URL:

Other:

Project version(s) affected

Suggestions for a fix

docker cloud info not available

Thank you for your feedback. There doesn't seem to be enough details in the issue for us to work on. If this really is a documentation issue and I have misunderstood, please reopen it with more information.


Use GitHub Actions

Switch to using GitHub actions for linting and unit tests and remove CircleCI

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


couldn't parse image reference "${REPOSITORY_PREFIX}

Show files with REPOSITORY_PREFIX
grep -R  {REPOSITORY_PREFIX}/api-gateway:latest .
./scripts/pushImages.sh:docker push ${REPOSITORY_PREFIX}/api-gateway:latest
./k8s/api-gateway-deployment.yaml:      - image: ${REPOSITORY_PREFIX}/api-gateway:latest

Create ENV variable
export REPOSITORY_PREFIX=antonpatsev

Run skafford
skaffold dev --default-repo antonpatsev
Listing files to watch...
 - spring-petclinic-config-server
 - spring-petclinic-discovery-server
 - spring-petclinic-customers-service
 - spring-petclinic-visits-service
 - spring-petclinic-vets-service
 - spring-petclinic-api-gateway
Generating tags...
 - spring-petclinic-config-server -> antonpatsev/spring-petclinic-config-server:latest
 - spring-petclinic-discovery-server -> antonpatsev/spring-petclinic-discovery-server:latest
 - spring-petclinic-customers-service -> antonpatsev/spring-petclinic-customers-service:latest
 - spring-petclinic-visits-service -> antonpatsev/spring-petclinic-visits-service:latest
 - spring-petclinic-vets-service -> antonpatsev/spring-petclinic-vets-service:latest
 - spring-petclinic-api-gateway -> antonpatsev/spring-petclinic-api-gateway:latest
Checking cache...
 - spring-petclinic-config-server: Found Remotely
 - spring-petclinic-discovery-server: Found Remotely
 - spring-petclinic-customers-service: Found Remotely
 - spring-petclinic-visits-service: Found Remotely
 - spring-petclinic-vets-service: Found Remotely
 - spring-petclinic-api-gateway: Found Remotely
Tags used in deployment:
 - spring-petclinic-config-server -> antonpatsev/spring-petclinic-config-server:latest@sha256:2792e7678e83f01cda7d71754f7dad1403416ac672f7078d81cbe8ebb1cf1c33
 - spring-petclinic-discovery-server -> antonpatsev/spring-petclinic-discovery-server:latest@sha256:3af5b8f83d44cf11f7aa26be1fcf595a68ee82a73ea6c2b8feaa1478c213080b
 - spring-petclinic-customers-service -> antonpatsev/spring-petclinic-customers-service:latest@sha256:62e940d6655e18d4b3af73902839b1fc377379fa6acc0bc33e72204e47acb6df
 - spring-petclinic-visits-service -> antonpatsev/spring-petclinic-visits-service:latest@sha256:38f48e411ce963ca5e8e083ca6a64b36438f2ca51b613ee2830e8aecda25d214
 - spring-petclinic-vets-service -> antonpatsev/spring-petclinic-vets-service:latest@sha256:9ad091cd546153f4ccafffdbf31db2c7f987c2b6cc18146ed07fa5ebd05636d3
 - spring-petclinic-api-gateway -> antonpatsev/spring-petclinic-api-gateway:latest@sha256:7f8b9598f263c16ec75ec6e9d8bc8e1885be090f180150470a6d452a2b52d953
Starting deploy...
Helm release customers-db-mysql not installed. Installing...
NAME: customers-db-mysql
LAST DEPLOYED: Fri Oct  1 05:32:43 2021
NAMESPACE: spring-petclinic
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

Tip:

  Watch the deployment status using the command: kubectl get pods -w --namespace spring-petclinic

Services:

  echo Primary: customers-db-mysql.spring-petclinic.svc.cluster.local:3306

Execute the following to get the administrator credentials:

  echo Username: root
  MYSQL_ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic customers-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)

To connect to your database:

  1. Run a pod that you can use as a client:

      kubectl run customers-db-mysql-client --rm --tty -i --restart='Never' --image  docker.io/bitnami/mysql:8.0.26-debian-10-r60 --namespace spring-petclinic --command -- bash

  2. To connect to primary service (read/write):

      mysql -h customers-db-mysql.spring-petclinic.svc.cluster.local -uroot -p"$MYSQL_ROOT_PASSWORD"

To upgrade this helm chart:

  1. Obtain the password as described on the 'Administrator credentials' section and set the 'root.password' parameter as shown below:

      ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic customers-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)
      helm upgrade --namespace spring-petclinic customers-db-mysql bitnami/mysql --set auth.rootPassword=$ROOT_PASSWORD
Helm release vets-db-mysql not installed. Installing...
NAME: vets-db-mysql
LAST DEPLOYED: Fri Oct  1 05:33:08 2021
NAMESPACE: spring-petclinic
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

Tip:

  Watch the deployment status using the command: kubectl get pods -w --namespace spring-petclinic

Services:

  echo Primary: vets-db-mysql.spring-petclinic.svc.cluster.local:3306

Execute the following to get the administrator credentials:

  echo Username: root
  MYSQL_ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic vets-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)

To connect to your database:

  1. Run a pod that you can use as a client:

      kubectl run vets-db-mysql-client --rm --tty -i --restart='Never' --image  docker.io/bitnami/mysql:8.0.26-debian-10-r60 --namespace spring-petclinic --command -- bash

  2. To connect to primary service (read/write):

      mysql -h vets-db-mysql.spring-petclinic.svc.cluster.local -uroot -p"$MYSQL_ROOT_PASSWORD"

To upgrade this helm chart:

  1. Obtain the password as described on the 'Administrator credentials' section and set the 'root.password' parameter as shown below:

      ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic vets-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)
      helm upgrade --namespace spring-petclinic vets-db-mysql bitnami/mysql --set auth.rootPassword=$ROOT_PASSWORD
Helm release visits-db-mysql not installed. Installing...
NAME: visits-db-mysql
LAST DEPLOYED: Fri Oct  1 05:33:35 2021
NAMESPACE: spring-petclinic
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

Tip:

  Watch the deployment status using the command: kubectl get pods -w --namespace spring-petclinic

Services:

  echo Primary: visits-db-mysql.spring-petclinic.svc.cluster.local:3306

Execute the following to get the administrator credentials:

  echo Username: root
  MYSQL_ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic visits-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)

To connect to your database:

  1. Run a pod that you can use as a client:

      kubectl run visits-db-mysql-client --rm --tty -i --restart='Never' --image  docker.io/bitnami/mysql:8.0.26-debian-10-r60 --namespace spring-petclinic --command -- bash

  2. To connect to primary service (read/write):

      mysql -h visits-db-mysql.spring-petclinic.svc.cluster.local -uroot -p"$MYSQL_ROOT_PASSWORD"

To upgrade this helm chart:

  1. Obtain the password as described on the 'Administrator credentials' section and set the 'root.password' parameter as shown below:

      ROOT_PASSWORD=$(kubectl get secret --namespace spring-petclinic visits-db-mysql -o jsonpath="{.data.mysql-root-password}" | base64 --decode)
      helm upgrade --namespace spring-petclinic visits-db-mysql bitnami/mysql --set auth.rootPassword=$ROOT_PASSWORD
WARN[0081] image [antonpatsev/spring-petclinic-config-server:latest@sha256:2792e7678e83f01cda7d71754f7dad1403416ac672f7078d81cbe8ebb1cf1c33] is not used.
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration
WARN[0081] image [antonpatsev/spring-petclinic-discovery-server:latest@sha256:3af5b8f83d44cf11f7aa26be1fcf595a68ee82a73ea6c2b8feaa1478c213080b] is not used.
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration
WARN[0081] image [antonpatsev/spring-petclinic-customers-service:latest@sha256:62e940d6655e18d4b3af73902839b1fc377379fa6acc0bc33e72204e47acb6df] is not used.
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration
WARN[0081] image [antonpatsev/spring-petclinic-visits-service:latest@sha256:38f48e411ce963ca5e8e083ca6a64b36438f2ca51b613ee2830e8aecda25d214] is not used.
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration
WARN[0081] image [antonpatsev/spring-petclinic-vets-service:latest@sha256:9ad091cd546153f4ccafffdbf31db2c7f987c2b6cc18146ed07fa5ebd05636d3] is not used.
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration
WARN[0081] image [antonpatsev/spring-petclinic-api-gateway:latest@sha256:7f8b9598f263c16ec75ec6e9d8bc8e1885be090f180150470a6d452a2b52d953] is not used.
WARN[0081] See helm documentation on how to replace image names with their actual tags: https://skaffold.dev/docs/pipeline-stages/deployers/helm/#image-configuration
Waiting for deployments to stabilize...
Deployments stabilized in 7.411549ms
 - Warning: resource namespaces/spring-petclinic is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically.
 - namespace/spring-petclinic configured
 - secret/regcred created
 - configmap/petclinic-config created
 - role.rbac.authorization.k8s.io/namespace-reader created
 - rolebinding.rbac.authorization.k8s.io/namespace-reader-binding created
 - service/api-gateway created
 - service/customers-service created
 - service/vets-service created
 - service/visits-service created
 - deployment.apps/api-gateway created
 - deployment.apps/customers-service created
 - deployment.apps/vets-service created
 - deployment.apps/visits-service created
Waiting for deployments to stabilize...
 - spring-petclinic:deployment/api-gateway: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/api-gateway-5bc8d44664-48tgv: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/customers-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/customers-service-75c77f6cd9-qf9ts: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/vets-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/vets-service-854775b9b9-nz6vr: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/visits-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/visits-service-86f868f9f7-nczj7: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/api-gateway: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/api-gateway-5bc8d44664-48tgv: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/api-gateway failed. Error: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/api-gateway:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/api-gateway:latest": invalid reference format: repository name must be lowercase.
 - spring-petclinic:deployment/visits-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/visits-service-86f868f9f7-nczj7: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/visits-service failed. Error: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/visits-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/visits-service:latest": invalid reference format: repository name must be lowercase.
 - spring-petclinic:deployment/vets-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/vets-service-854775b9b9-nz6vr: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/vets-service failed. Error: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/vets-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/vets-service:latest": invalid reference format: repository name must be lowercase.
 - spring-petclinic:deployment/customers-service: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase
    - spring-petclinic:pod/customers-service-75c77f6cd9-qf9ts: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase
 - spring-petclinic:deployment/customers-service failed. Error: InspectFailed: Failed to apply default image tag "${REPOSITORY_PREFIX}/customers-service:latest": couldn't parse image reference "${REPOSITORY_PREFIX}/customers-service:latest": invalid reference format: repository name must be lowercase.
Cleaning up...
release "customers-db-mysql" uninstalled
release "vets-db-mysql" uninstalled
release "visits-db-mysql" uninstalled
 - namespace "spring-petclinic" deleted
 - secret "regcred" deleted
 - configmap "petclinic-config" deleted
 - role.rbac.authorization.k8s.io "namespace-reader" deleted
 - rolebinding.rbac.authorization.k8s.io "namespace-reader-binding" deleted
 - service "api-gateway" deleted
 - service "customers-service" deleted
 - service "vets-service" deleted
 - service "visits-service" deleted
 - deployment.apps "api-gateway" deleted
 - deployment.apps "customers-service" deleted
 - deployment.apps "vets-service" deleted
 - deployment.apps "visits-service" deleted
4/4 deployment(s) failed

Try envsubst later

Work:
envsubst < k8s/vets-service-deployment.yaml | tee k8s/vets-service-deployment.yaml
envsubst < k8s/api-gateway-deployment.yaml | tee k8s/api-gateway-deployment.yaml
envsubst < k8s/visits-service-deployment.yaml | tee k8s/visits-service-deployment.yaml
envsubst < k8s/customers-service-deployment.yaml | tee k8s/customers-service-deployment.yaml


Add a section about implementation review

This incorporates feedback received in the Language Workgroup meeting, as well as some of the ideas from https://github.com/apple/swift-evolution/pull/957.

Rhetorically, there's a couple things that I think we could make clearer.

Thanks, incorporated.


Failed deployment is shown as successful

In order to deploy the docs corresponding to prism v2.9, https://github.com/input-output-hk/atala-releases/blob/master/Atala PRISM/2.9.md, I have chosen the wrong version (OEA version instead of the documentation version).
In https://github.com/input-output-hk/atala-prism-docs/actions, click on Deployment and then Run workflow
I chose: main branch, v1.25.0 and production and click Run workflow.
It gave a successful deployment when looking after but the docs.atalaprism.io was still not updated as it showed in API --> Agent API the same old version v1.22.0. See attached screenshot.
The expectation is that as the workflow failed, the status should show as failed.

If you look at the workflow file, there is no information that would give any indication of what was run.
If you look at the https://github.com/input-output-hk/atala-prism-docs/actions/runs/7959863521/job/21727672596 , there is no information on the parsing of the version for example.

@mkbreuningIOHK, is this still an issue?

@essbante-io , I could follow the steps again and give an update, but I would propose the process to be the maintainers to reproduce the issue following the steps first. If the steps are not clear, then it would be asked to me to provide more info with a label needs-repro.

@essbante-io , the steps to deployment have been changed since the migration. This bug needs to be reviewed if it is still applicable indeed.


Add Terraform validate test

Add Terraform validation test. This test will scan the entire repo for Terraform modules and run terraform init and terraform validate on each.

This example repo contains Terragrunt, not Terraform modules, so this PR is not really applicable.

@zackproser Should we have a TerragruntValidateAll too? Doesn't have to be part of same PR / Jira card, but seems just as valuable...

@zackproser Should we have a TerragruntValidateAll too? Doesn't have to be part of same PR / Jira card, but seems just as valuable...

Good idea! Filed https://gruntwork.atlassian.net/browse/IAC-1871


Correct the Example Configuration; Add more commentary to rational-ui.el

The example configuration now uses an unquoted symbol in the weight face attribute plist, as M-x customize-group "rational" would do when customizing the variable.
Using the example configuration on the current HEAD causes an error, because the symbolp fails; this may confuse some users, because the predicate will pass interactively.

Seemed related to #97, so bringing this one along as well. Thanks very much!


favicon isn't updated correctly when scan ends

We are updating the favicon file via JavaScript but we don't have the cache busted names so we are just using images/favicon_XXX.ico in scanner-submit
I'm not sure how to fix this (maybe have the icons commented in the HTML and uncomment them?)

The red bird does appear for a second, and then it disappears.
Example with Chrome Canary with /static/images/favicon_failed-13305bf6b9.ico:
https://webhint.io/scanner/e3e5cfb3-8b1c-4018-98db-4684e288d904

I think we are still executing the JS of the scanner results even though the test is finished.
IIRC https://github.com/webhintio/webhint.io/pull/474 should fix that particular issue where the icon changes even though the results are finished. @sarvaje is that true?
Re updating the icon while the tests are running I still need to figure out how to do that.

@sarvaje is taking care of this with the new results page.

@sarvaje is this fixed with the new results page?

@molant I need to take a look at this.

It was fix, but I have create a new PR to update the icon as soon as we get some result. https://github.com/webhintio/webhint.io/pull/542


Adding listener to read data causes node to exit

SerialPort Version:6.0.3

NodeJS Version:v6.11.2

Operating System and Hardware Platform:win 10 x86_64

Have you checked the right version of the api docs?:?

Summary of Problem
i am able to write to the serial port
when i am doing a port.on("readable or on("data the script ends immediately, even if the event queaue is not empty
Steps and Code to Reproduce the Issue
var SP= require('../');

var port = new SP("COM2");

port.on('error', function(err) {
  console.log('Error: ', err.message);
})

//when this is uncomented the script keeps running
port.on('data', function () {
  console.log('Data:');
});

port.on('open', () => {
  console.log(`echo: Port open: COM2`);

    console.log('echo: READY!');

  //port.write("a");

});

//code to keep the event loop running
(function wait () {
   if (true) setTimeout(wait, 1000);
})();

oh,,, sorry. I made a big mistake about reading. I'll send a pull request soon.

For the time being, after googling, i used core node .js for that, it
worked, and i am wondering... (maybe its a new feature of node?, or its not
cross platform?)
var fs = require('fs');
var buffer=""
fs.open("\\.\COM2","r+" ,function (err, fd) {
if (err) {
    return console.error(err);
}

var buffr = new Buffer(1);
fs.write(fd,"aaa")

function nextread(){
fs.write(fd,"@C"+buffer)
fs.read(fd, buffr, 0, buffr.length, 0, function (err, bytes) {
    if (err) throw err;

    // Print only read bytes to avoid junk.
    if (bytes > 0) {
        console.log(buffr.slice(0, bytes).toString());

buffer+=buffr.slice(0, bytes).toString()
console.log(buffer)
nextread()
}
});

}
nextread()
});
@C clears the display and echos the whole string (for my purpose)
In my raspberry pi i managed with "/dev/ACM0"
Are there any benefits of going C?
On Mon, Oct 23, 2017 at 9:08 PM, kimushu<EMAIL_ADDRESS>wrote:

oh,,, sorry. I made a big mistake about reading. I'll send a pull request
soon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EmergingTechnologyAdvisors/node-serialport/issues/1375#issuecomment-338840693,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQJ0rdeyBeqUWyeZ4GBUuevwafScDCkrks5svTh2gaJpZM4QCEko
.

--
Pinchas S. Neiman
845.213.1229 #2


Windows users can use the Resolve-DnsName command.

Why:
Windows users aren't required to install BIND to verify DNS records but can also use the Resolve-DnsName PowerShell command.
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[ ] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ] For content changes, I have completed the self-review checklist.

@j0eybrinkman Thanks for opening a PR! ✨ It looks like this is still a draft - could you ping me whenever you're ready? I'll then have the PR reviewed 💛

@nguyenalex836 Hi Alex, it is ready for review. Thank you!

@j0eybrinkman Thank you for letting me know! I'll get this triaged for review 💛


tls/ssl flags

I think only you guys can test this.
I am no bash expert, but I cannot see anything else to change

Thanks! :tada:


Stop the event queue task when event queue is empty

This change set include:

Stop the event queue task when the queue is empty and the current time has passed the task stop time.
Simplify the implementation by not disposing the event queue task, it is not needed as we are not using the internal wait handle.
Simply the implementation by removing the OnLinkedListItemRemoved(), no longer needed
Introduced the _eventQueueRunDurationInSeconds to reduce possible overhead of restarting tasks.

How was this verified at scale?

I'll kick off some long term stress to get some numbers.


Ignore in-source cmake build residue.

This commit makes adds the files produced by in-source cmake builds to .gitignore.

Thank you.  We got merge conflict here.  Could you review the change?

Hi
Ah. I accidentally made the change against my fork's master branch which
was a little behind. It turns out that this change was already made.
Sorry about all that.
Anders
On Sun, Jun 7, 2015 at 12:26 AM, Tatsuhiro Tsujikawa <
<EMAIL_ADDRESS>wrote:

Thank you. We got merge conflict here. Could you review the change?
—
Reply to this email directly or view it on GitHub
https://github.com/tatsuhiro-t/wslay/pull/21#issuecomment-109709528.


make and test original Ronneberger Unet

3x3 kernel
1x1 stride
2x2 upsample
number of filters=8

{
"MODEL": "unet",
"KERNEL":3,
"STRIDE":1,
"FILTERS":8,
"DROPOUT":0.0,
"LOSS":"cat",
}

ok, for "TARGET_SIZE": [768,1024],, using the values above for the config,
i get a tensor shape error:
ValueError: A Concatenate layer requires inputs with matching shapes except for the concat axis. Got inputs shapes: [(None, 1536, 2048, 128), (None, 768, 1024, 64)]

stride =2 works...

we can close this, and merge into #24


feat(vite-node): support passing through arguments

Clear and concise description of the problem
Similar to how the node command works where you can run node file.ts arg1 arg2, it would be great if we could pass arguments similar to above where calling npx vite-node file.ts arg1 passes the arg1 to the file when executed. This is useful for CLI tools or apps that use arguments themselves.
Perhaps it might be better to put the pass-through arguments behind a flag to prevent conflicting with vite-node's own args/flags.
Suggested solution
My real concern is whether this is even possible with the Vite runner code? I went through the current project and I couldn't see a clear approach to modify the code to support arguments, so is this perhaps a limitation with this Vite oriented model? Or is it possible?
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I am not sure how this would be possible, since you can pass several files to vite-node: vite-node ./f1.ts ./f2.ts?
I think you might want something like tsx.

The universal behaviour here is to forward everything after the first -- in the process argument list.

Agreed, I just ran into this myself and expected everything after -- to be passed to vite-node. Seems like a simple addition which would allow for using vite-node for cli tools.


Try pull requests (try 1)

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Fix #780 - Update Code of Conduct

Many thanks for submitting your Pull Request :heart:!
Please specify parts of this PR update:

[ ] Specification
[ ] Schema
[ ] Examples
[ ] Extensions
[ ] Roadmap
[ ] Use Cases
[x] Community
[ ] TCK
[ ] Other

Discussion or Issue link:

Fix #780
What this PR does / why we need it:

Update the code of conduct to reflect the new defaults. See #780
Special notes for reviewers:
Please take a look ASAP, I missed this issue from my notifications. Sorry about that.
Additional information:

Closed because I need to sign the commit and it's not possible via the web UI. See #787


Automated Package Upgrade

:tada: This PR is included in version 12.0.30 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


@available(iOS 14.0, *) Stored properties cannot be marked potentially unavailable with '@available'

@available(iOS 14.0, *) Stored properties cannot be marked potentially unavailable with '@available'

The problem has been solved and the solution is available at this address but I did not understand if it is already present in the latest version or if it must be released with a new version of the plugin
https://github.com/pichillilorenzo/flutter_inappwebview/pull/1238/commits/06f87e81c4f55b7b251a149ec0db60442bb351c3


Added PowerShell One-liner to install Azure CLI

Added PowerShell One-liner to install Azure CLI

Docs Build status updates of commit 93e784e:
:clock10: Full build: the average full build time is 6 min(s) 47 sec(s), this is based on the last 152 build(s) for this repository.

Docs Build status updates of commit 93e784e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/install-azure-cli-windows.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

LGTM, thank you for your contribution!


added jacoco

#3
jacoco added
user
./gradlew jacocoTestReport
./gradlew testAggregateTestReport

Build is failing.
You can use this PR as a reference.

close.
PR is inactive.


Can't find doc about SafePlan

Hello guys,
i've seen that OctoDNS includes a "SafePlan" to prevent too much updates. I haven't seen any documentation regarding this feature setting. It's an interesting point and i think that the main documentation should describe fields like this, it will be definitively useful :).
Have a good week!

There's two optional parameters on the BaseProvider which makes them available to app providers
https://github.com/github/octodns/blob/de4dc76b3f17ab41a2cc562439584d834e4c4c5e/octodns/provider/base.py#L16-L17
They can be configured with something like:
    foo:
        class: foo.bar.Provider
        update_pcent_threshold: 0.5
        delete_pcent_threshold: 0.5

The defaults are on the Plan object
https://github.com/github/octodns/blob/de4dc76b3f17ab41a2cc562439584d834e4c4c5e/octodns/provider/plan.py#L20-L21
Would welcome a PR getting that into something starting on documenting providers in the docs/ dir 😁


Added old actions to the sim and combo validity for unheated shots

Small update so old synced content doesn't display logs as broken. This is only a resource sim/combo action update. I'm not bothering to add analysis for Rook Autoturret usage; the Automaton Queen section of the parse will still come up empty even though Battery expenditure is calculated properly.

I thought we don't support old <80 content (._.)


Can't delete image that is in a DCIM subfolder

Describe the bug
Giving storage access for an image located inside a DCIM subfolder and grants access to "DCIM", resulting in a failed message upon pressing delete.
But doing the same for an image directly inside the DCIM folder grants access to a "dcim" folder and allows for successful deletion of media both in the DCIM folder and its subfolders.
The "DCIM" storage access entry (in Aves settings) doesn't seem correlate with the actual folder on the device (but the "dcim" entry does.)
To Reproduce
Steps to reproduce the behavior:

Have an image in DCIM/subfolder/image.jpg
Press delete button.
Give storage access to "DCIM" folder.
See error message.

Subsequently

Have an image in DCIM/image.jpg
Press delete and grant access to "dcim" folder.
No error and successful deletion.

Expected behavior
Giving storage access for an image in a DCIM subfolder should grant access correctly.
Screenshots

System information and logs:
Package: deckers.thibault.aves
Installer: com.android.vending
Aves version: 1.9.7-play, build 108
Flutter: stable 3.13.7
Android version: 13, API 33
Android build: TP1A.220624.014 release-keys
Device: vivo I2011
Geocoder: ready
Mobile services: ready
System locales: en_US
Storage volumes: /storage/emulated/0/, /storage/C0B5-9BF6/
Storage grants: /storage/emulated/0/Movies/, /storage/emulated/0/Pictures/, /storage/emulated/0/Documents/, /storage/emulated/0/DCIM/, /storage/emulated/0/dcim/
Error reporting: true
aves-logs-20231029_232523.txt
Additional context
The above image was in DCIM/Screenshots.

I'll take a closer look at this later, but for now i have a quick question: i see in your grants that there is both "/storage/emulated/0/DCIM/" and "/storage/emulated/0/dcim/". How is that possible? Was the folder name at some point "DCIM", you gave permission for it, then deleted it and recreated it as "dcim"?

"DCIM" entry was created when I granted permission for an image located inside "/DCIM/Screenshots/". "dcim" was created when I granted permission for an image located directly inside "/DCIM/". I never renamed any folder. Aves apparently recognizes the folder differently based on where the image is.

I see. So the first weird thing is that the app should never have asked you for another permission when editing the image directly inside DCIM, as it already had the permission.
I've dealt with some file path casing issues before and it's tricky. I'll need to try and reproduce your situation on my device.

I've tried to reproduce the issue on my device, to no avail (and the logs did not yield anything useful).
Actually, I don't understand why Aves would ask/get permission as "dcim" if the directory name is indeed DCIM in uppercase. All the rest is probably a consequence of this weirdness.
If you clear the grants for DCIM and dcim via Settings > Privacy > Storage access, then can you reproduce the bug at will by following the same sequence of actions you indicated in your reproduction scenario above?
Also, do you use a custom ROM?

No custom ROM, just FuntouchOS (vivo/iqoo ROM).
I have discovered a new behaviour with user-created directories in DCIM. It's in the linked video.
https://crepe.moe/kESinNul
In the video, the "placeholder" folder was created by me, and "Screenshots" was created by the OS.
And yes, it is completely reproducable.

Thanks for digging further.
The first mystery to me is why the system file picker shows the directory as "dcim" while mixplorer shows it as "DCIM".
Android is technically case sensitive, but normally everything is made to present it to the user as case insensitive. What I mean is that it's possible for the system to have both "dcim" and "DCIM" folders side by side but typical file managers won't let you create this situation.
My guess is that on your system you indeed have both. Different apps will show the combined content from both in a single directory called either "DCIM" or "dcim", depending on the API used and how paths are resolved, as if there was a single directory.
This is a mess. I'm not even sure i can recreate this situation without FuntouchOS.

"All File Access" would make the app redundant and useless. Drill down the issue and solving it would be the best way, and why we users take the time to post and report the issue.
What might help is different people reporting it. Or a work around.
It looks like if you save or move all images out of DCIM the problem should not apply. I dont know if the camera app I use has the ability to store taken photos into another folder, but I would do that if possible.

You're missing the point: that app is a fundamental system app. If your device doesn't have it, it's non standard.

I experienced the same thing here with Aves 1.11.13 on Android 13.
As it looked like a difficulty with storage access, I checked the storage in my settings, I saw that there were two SD card listed when I only have one. The "empty" one could be removed so I removed it. After that, even the camera could not save photos but after a reboot, it all got together and the camera as well as deleting with Aves.
I am not sure this is the same issue that everybody here has but I am sharing this experience in case that can help.
Otherwise checking the settings of Aves and unticking Privacy > Use recycle bin may also help.

@aloxe Thanks for sharing your experience.

there were two SD card listed when I only have one. The "empty" one could be removed so I removed it.

Just to be clear, you mean there were 2 SD card listed in the Android system settings? If so, was it a phantom SD card that you inserted before and had removed since then?

It was a phantom card listed, but the incident was possibly due to the opening of the phone and the removal of the card earlier on. Aves took time to find the photos and resync them again. I think the phantom card is a result of this hardware hiccup.

I have the same issue, this is really annoying because if you have "Use recycle bin" enabled, then you might not even notice this problem. I figured out because after a while (now I can reproduce it every time by simply killing the app and opening again) the deleted images pop up again in the main gallery. Tried to delete it many times, also from recycle bin and they alwas come back. Now when I disabled recycle bin and when I delete them it also shows just "Failed" toast, like on the screenshot of OP.
In my case "DCIM" folder is uppercase on both locations. Tried removing and granting the permission multiple ways, no success. So not sure what is going on. I use stock OS, Xiaomi HyperOS <IP_ADDRESS>, Xiaomi 13T Pro, Android 14.

Okay, I might be onto something.
Under the "Storage access" list, the "DCIM" is uppercase in the path, using file managers also uppercase. Both look correct.
But if look at the image details that cant be deleted, it shows the Path with lowercase "dcim", while other parts in the path look correct, e.g. "Camera" with uppercase C. So it's not that the whole path "got lowercased" somehow but only "dcim" part.
I have a set of images with such lowercase "dcim" which cant be deleted, but most of other images have "DCIM" and can be deleted just normally. So aparently it's actually only subset of files with such issue. See screenshots of two cases. Both taken with standard camera app, not sure what I did differently...

Yes, I agree it's confusing. My understanding is the following. Underlying Android is a case sensitive OS that allows both "DCIM" and "dcim" to coexist, but everything is done in Android to present to the user the file storage as being case insensitive, so the user cannot create a folder or file with the same name only differing in case.
In your example, I suppose the app that created the files registered them in the Media Store with different case for "DCIM". Not sure whether it's only differing in the Media Store, or whether they are actually in 2 different folders. Anyway now the user only sees one folder "DCIM" in their file storage, merging both cases.
I would need to try different workarounds. It's easy to get wrong, as I use multiple approaches to access the file storage, depending on location.

Many thanks for the reply. You are right. Seems like its not the fault of your app regarding the path representation. I actually see it in "Files by Google" app like that as well when I select info about the file. Althought I was able to delete it there and seems like that's the workaround for such files for now (probably with other file managers and stock gallery would work as well).


Allowlist, Denylist

I'm guessing we'll need this, including local commands to modify while running.  If so, we probably need to move our config from the Plugins section of ~/.ipfs/config to a separate file so we can write it out without risk of clobbering ipfs settings.

Consider if UCANs could come into play here.


Add alias for multi-line padding workaround

Re-did #273 after test was failing.

Add mixin
Add test and fixtures
Add description

Nice, this looks good. What is browser support like for this? And would you be willing to also add documentation for this to axis' docs site? Also ping @dbox for comment :+1:

IE says nope. Source: caniuse
It works with background only, not with borders i am afraid.
Currently on the docs :+1: Does this look good?

Looks good. I think my only concern with this is that it's a one-line thing, so I'm not sure how useful an alias is since you could probably type the original declaration with fewer characters.

I have been checking this article by Chris Coyier and this seems to be the most sensible solution for the problem. There are several others available and neither box-decoration-break: clone; nor the other solutions are intuitive. Once some other technique turns out to be better we can possibly just drop-in the replacement.

I was looking at open-type-ligatures and figured multi-line-padding is justified too. Both shorten a longer expression and make it more semantically accessible imo.

bumpity

Sorry, I missed this one. LGTM!


sql: add feature flag for CREATE STATISTICS/ANALYZE

PR: https://github.com/cockroachdb/cockroach/pull/57076
From release notes:

Adds a feature flag via cluster settings for the CREATE STATISTICS and ANALYZE feature. If a user attempts to use the command while disabled, an error indicating that the database administrator had disabled the feature is surfaced. Example usage: SET CLUSTER SETTING feature.stats.enabled = FALSE; SET CLUSTER SETITNG feature.stats.enabled = TRUE;. [#57076][#57076] {% comment %}doc{% endcomment %}

Related to From https://cockroachlabs.atlassian.net/browse/CRDB-2219.

From https://cockroachlabs.atlassian.net/browse/CRDB-2219:

We don’t plan on publicly documenting these cluster settings but we should document them internally for CC SREs.

@vy-ton
What is the plan around internal documentation work? Please let me know if I can help in any way. I'll leave this issue open for now.

(see comment above)
Closing for now.


Permit leading zero value to stay in conversion

The data conversion may contain meaningful data with a leading zero.

Included as of 0.3


Update SASI.md

Minor grammatical fixes to improve readability.

Thanks @joaquincasares :)

This commit actually broke some formatting, you can preview it here.
Screenshot:

Could you address this @joaquincasares?
Thank you!

Super sorry for the delay! I edited the file in Github and didn't realize that the text was correct and that Github does not use a monospaced font!
I've submitted #91 to fix the issues. Thanks for pointing it out @ifesdjeen !


Support sync tx submission

In GRPC it's now possible to specify that the GRPC client should wait for a response, rather than submitting everything asynchronously. This should be exposed by go-wallet's REST-ish API to allow us to catch some errors that are currently invisible
Tasks

Add optional sync property to signTx

@edd Would it be useful for traderbot to be able to submit sync tx?

@edd Would it be useful for traderbot to be able to submit sync tx?

@edd Would it be useful for traderbot to be able to submit sync tx?

I might be useful for the trader bot in the case they try to place order and have no funds available. When a netwokr restart, not funds are available, but the network check if the party have any funds available of any sorts. if not, then the transaction is rejected straight in the pool. An error is return, but you will b eable to see it only with SubmitTransactionSync or SubmitTransactionCommit;

@edd Would it be useful for traderbot to be able to submit sync tx?

I might be useful for the trader bot in the case they try to place order and have no funds available. When a netwokr restart, not funds are available, but the network check if the party have any funds available of any sorts. if not, then the transaction is rejected straight in the pool. An error is return, but you will b eable to see it only with SubmitTransactionSync or SubmitTransactionCommit;

Also @edd this was actually already implemented.

That's great news, I totally missed that. I see it's already in the latest release - I suspect Console should switch over for some TXs.

Also @edd this was actually already implemented.

That's great news, I totally missed that. I see it's already in the latest release - I suspect Console should switch over for some TXs.


New TileMapPattern GUI

Pull request with a cleaner commit history similar to PR #95826 https://github.com/godotengine/godot/pull/95826. The difference is that it doesn't contain the multilayer TileMapPattern system in favor of just adding a new TileMapPattern GUI that is backwards compatible with the old TileMapPattern system (A new pattern set is created and all old patterns are imported to it).

Your rebase went wrong, you can fix this by:
git reset --hard 20750b6

And then performing your rebase and finally pushing with:
git push --force

Please use a rebase, not a merge to update your branch

I did some testing:

The default width of the left panel is too small and the label is trimmed.

Context menu appears at wrong position. It's always above cursor when clicking empty space and at weird offset when clicking item:

Although I'd completely remove the menu, as the UX is awkward. Add some "Add Pattern Set" button at the bottom and display sets with a delete button.
The rename popup for patterns always appears in the corner and can't be cancelled:

https://github.com/user-attachments/assets/f3678d07-6765-4a37-8364-3ea3a14dea18

When you drag a new pattern, the current pattern set will be deselected

https://github.com/user-attachments/assets/8948728a-464f-45b9-a122-64bd827ca9b7

When opening Patterns tab for the first time, I think the first set should be selected automatically. Currently you need extra click to see patterns
If a pattern has default name, the displayed name is changed when rearranging:

https://github.com/user-attachments/assets/b71af7a7-b286-47f0-af8c-5751e1892fdc

I think the pattern array should be called patterns not pattern_set.

pattern_set_0/name = "Set"
pattern_set_0/pattern_set = []

The help labels need improving. They mix with the list and disappear as content is added.

I know we have similar labels in Tiles tab, but these are much bigger. It would be better to have some sort of info button or foldable info panel (though I'm not sure if we have something similar already). If not, they should be at least fixed at the bottom and not disappearing.

Other than UX problems, the feature works correctly. You can create, rename and reorder sets and patterns. Also compatibility is handled properly.

I did some testing:

The default width of the left panel is too small and the label is trimmed.

Context menu appears at wrong position. It's always above cursor when clicking empty space and at weird offset when clicking item:

Although I'd completely remove the menu, as the UX is awkward. Add some "Add Pattern Set" button at the bottom and display sets with a delete button.
The rename popup for patterns always appears in the corner and can't be cancelled:

godot.windows.editor.dev.x86_64_ngng4Jm8nU.mp4

When you drag a new pattern, the current pattern set will be deselected

godot.windows.editor.dev.x86_64_MS9lqQ6kAJ.mp4

When opening Patterns tab for the first time, I think the first set should be selected automatically. Currently you need extra click to see patterns
If a pattern has default name, the displayed name is changed when rearranging:

godot.windows.editor.dev.x86_64_Z8VNGYtLVc.mp4

I think the pattern array should be called patterns not pattern_set.

pattern_set_0/name = "Set"
pattern_set_0/pattern_set = []

The help labels need improving. They mix with the list and disappear as content is added.

I know we have similar labels in Tiles tab, but these are much bigger. It would be better to have some sort of info button or foldable info panel (though I'm not sure if we have something similar already). If not, they should be at least fixed at the bottom and not disappearing.

Other than UX problems, the feature works correctly. You can create, rename and reorder sets and patterns. Also compatibility is handled properly.

Noted. I will take this feedback and iterate upon it to improve the UX. Most of this feedback is reasonable.

Have you considered implementing a path instead of pattern sets? I feel it would be more flexible to just let people create folders however they want in the list of patterns.

Have you considered implementing a path instead of pattern sets? I feel it would be more flexible to just let people create folders however they want in the list of patterns.

I have a little bit. But decided it wasn't worth going to that level of complexity and wanted to avoid using strings/paths to access things wherever possible. Can you elaborate on what you mean? Rather than a pattern set>patterns you would do FileFolderName>InnerFileFolderName>Patterns+Folders containing patterns and stuff like that?
As with most other things in development I'm sure it can be done but it's a question of if it is needed and worth the effort. I think it would require a good deal of effort and a rewrite of the code as I have it. It would be a bit more fickle and complex with regards to how those patterns are accessed (e.g a path every time in order to get a pattern, if the path changes you're in trouble! Would patterns still have indexes as an additional parameter to access them? How would selecting a pattern between indexes 0-5 at random work if not?). Although, I would need to know exactly what you mean/want regarding the folder system to say for certain. The ultimate question much like any other feature added to Godot is "is there a situation where pattern sets would not suffice and a more in-depth/flexible system like folder paths would be needed?". In my personal experience working with patterns the answer is no.


ORM has tight dependency on LengthAwarePaginator

At the moment the query builder instantiates a fresh LengthAwarePaginator each time the pagination method is called. As times are moving on a lot of developers are starting to use Laravel more and more for API driven applications. I for one am writing a JSON API v1.0 API in Laravel 5.1 at the moment and have had to write a rather ugly adapter for the LengthAwarePaginator due to the inability to swap out the paginator used by the ORM.
Currently the method looks like this.
/**
 * Paginate the given query into a simple paginator.
 *
 * @param  int  $perPage
 * @param  array  $columns
 * @param  string  $pageName
 * @param  int|null  $page
 * @return \Illuminate\Contracts\Pagination\LengthAwarePaginator
 */
public function paginate($perPage = 15, $columns = ['*'], $pageName = 'page', $page = null)
{
    $page = $page ?: Paginator::resolveCurrentPage($pageName);

    $total = $this->getCountForPagination($columns);

    $results = $this->forPage($page, $perPage)->get($columns);

    return new LengthAwarePaginator($results, $total, $perPage, $page, [
        'path' => Paginator::resolveCurrentPath(),
        'pageName' => $pageName,
    ]);
}

If the LengthAwarePaginator was built through the IoC this problem would not exist.
Is this a problem anyone else has faced? I would like to submit a PR to allow this functionality but would like some feedback before I make any headway on it.

I don't see a problem with creating a new Illuminate contact to make this work via the IoC... but there looks like it would be a decent amount of work to make it happen.

You'd better talk to Taylor about this on one slack. Maybe this is something we can get done for L5.3.

I spoke to Taylor about this and we came up with an alternative as he
wasn't keen on having something resolving from the IoC with arguments but
recognised that we could do something. It'll probably take on the form of a
static resolving method to build the LAP instance. I'm going to go ahead
and put this together.
On Sat, 19 Dec 2015 at 22:41, Graham Campbell<EMAIL_ADDRESS>wrote:

Closed #11017 https://github.com/laravel/framework/issues/11017.
—
Reply to this email directly or view it on GitHub
https://github.com/laravel/framework/issues/11017#event-496663547.


chore: change engine to Node.js v14

The purpose of this change is to squelch a "bad engine" warning when installing under Node.js v14.
This package currently supports Node.js v14, but:

the engines field says otherwise, and
TS is configured to target Node.js v16

The resulting build artifact (dist/index.js) is identical to the previous changeset.
To that end, I've changed the configuration and dependency from @tsconfig/node16 to @tsconfig/node14.  I have also enabled the build to run across multiple Node.js versions and upgraded a couple actions while I was there.
It also looked like there was a problem on npm referencing the repo, so I fiddled with the repository field.  Could just be old, though.

I totally understand why you might not want to merge this, however!
Thanks for this plugin.  We're using it in appium.

Hi,
Thank you for the work!
I can't review right now, but I'll be able to in a few hours.
Glad to see that this package is helping you!

@boneskull Just published version v0.3.3


Event app_mention event will not fire

Attempting to use bolt-python with Flask, using the bolt-python/examples/flask/app.py example. The message is received, but the app_mention event will never fire.
Reproducible in:
The slack_bolt version
Flask==1.1.2
slack-bolt==1.3.1
slack-sdk==3.3.1
Python runtime version
Python 3.6.7
OS info
Microsoft Windows [Version 10.0.19042.685]
Steps to reproduce:

app.py

from dotenv import load_dotenv

basedir = os.path.abspath(os.path.dirname(__file__))
load_dotenv(os.path.join(basedir, '.env'))

from slack_bolt import App

app = App(
    token=os.environ.get("SLACK_BOT_TOKEN"),
    signing_secret=os.environ.get("SLACK_SIGNING_SECRET")
)

@app.event("app_mention")
def event_test(body, say):
    print("Event app_mention is never called. This will never print.")
    say("What's up?")

@app.event("message")
def handle_message(body, say):
    if body['event']['channel_type'] == 'im':
       say("I saw a private message to me, but I cannot print ['event'].['text']")
    else:
        say('I heard something, but it wan not directed to me.')

@app.message("knock knock")
def ask_who(message, say):
    print("message is never called. This will never print.")
    say("_Who's there?_")

from flask import Flask, request
flask_app = Flask(__name__)

from slack_bolt.adapter.flask import SlackRequestHandler
handler = SlackRequestHandler(app)

@flask_app.route("/slack/events", methods=["POST"])
def slack_events():
    print("slack event routed")
    return handler.handle(request)

DM bot (@bolt) with message "knock knock"
Message "bolt @bolt knock knock blah" in invited channel

Expected result:

In DM:

Who's there?

In channel, not sure if it should be:

What's up?

or

Who's there?

Actual result:

In DM:

I saw a private message to me, but I cannot print ['event'].['text']

In channel:

I heard something, but it was not directed to me.

Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Please disregard. Had to subscribe to bot event "app_mention" to receive app_mentions.


lightweight head

@wgcban Hi, as for the design of lightweight head, can you share some experiences and tips? I want to follow the pipeline to do other tasks.

@wgcban I have the same question. And Can you share some experiences about the choice of multi-level feature and the step t.


There should be a way of preventing .despawn_recursive() from despawning specific child entities.

What problem does this solve or what need does it fill?
despawn_recursive is a useful extension method for removing a hierarchy of entities. However, some entities move between different parents, and/or are meant to survive their parent. There should be a way of making specific entities get ignored by despawn_recursive.
What solution would you like?
Some type of marker component that tells despawn_recursive to skip a descendant entity.
#[derive(Component)]
pub struct NoDespawnRecursive;

What alternative(s) have you considered?
None.

I would like to suggest an alternative with two variations. Having a filtered version of despawn_recursive would be more flexible.
where T: ReadOnlyWorldQuery
commands.entity(entity).despawn_recursive_filtered::<With<FungalSpores>>()

where T: Bundle
commands.entity(entity).despawn_recursive_filtered::<MyNoDespawnRecursive>()


[MRG] ENH: modify time_as_index to allow arbitrary origin

Fixes #5523
This PR is required for #4936

Now it should be green. @agramfort
The fact that this failed might suggest that passing origin=xxxx to my_epochs.tima_as_index might produce undesired results. Looking at the blame, @dengemann and @larsoner might have some saying in adding this feature.

I don't think epochs.time_as_index should have an origin arg. It doesn't make sense there, or in Evoked, SourceEstimate, or any other object -- except for BaseRaw. So you should probably override the method in BaseRaw to call the super method, and then adjust the time indices to respect the origin arg.

@larsoner ok for you?

thx @massich


Dependencies: Super State Machine - not maintained

Last update to the Super State Machine repository took place 7 years ago.
There already happened a discussion in 2017 to refactor it out of bluesky.
Expected Behavior
We use dependencies with good maintenance status.
Current Behavior
Bluesky imports a not-maintained module.
Possible Solution
Refactor out the super state machine

short-term we should vendor a copy of that library into bluesky so we can drop the dependency.
medium-to-long term we should either right our own state machine or find a replacement.  This is primarily used to keep track of the state of the RE so we need to be very careful about any changes to it.

vendoring seems to match was has been already discussed before. this issue could focus on that.
for the longer view a quick search reveals libraries:

fgmacedo/python-statemachine  with 635 stars,
pytransitions with 5.3 k stars
p-org/P state machine focused programming language - 2.9k stars
mriehl/fysom with 385 stars
statesman with 50 stars.
that's the top of the google search so it's highly unlikely we could find something better. Of course it's at the core so care needs to be taken. Do you think this issue fits the hackathon theme well @tacaswell ? or too fragile of a system element? Maybe still some investigation would be harmless?

Just a quick check in other languages - same situation, finite state machines seem to be a niche use case.

looplab/fsm finite - state - machine in golang - so that we know it's not just Python
stonecypher/jssm 296 stars
xstate in the javascript ecosystem hasn't proven that successful

Agreed with the above. And I will add that our usage is pretty simple, so we might consider just using implementing something simple with dictionaries. Caproto has something like this and it works well.

I've dabbled with automat, spun out of twisted https://github.com/glyph/automat

Here's the PR for this issue. @stan-dot, @tacaswell, could you please have a look?

Fixed by #1708


Possibility to proxy non containers

Hi There, thank you for your great bundle! I'm looking for a way to proxy & create Let's Encrypt Certificates for vhosts that don't have a container. For instance some remote control interface that is running on a raspberry pi. Right now I'm using a second (regular) nginx container to achieve this:
client --(https)--> nginx-proxy ---(http)---> nginx --(http)---> raspberrypi
It works but it's a bit inefficient to have 2 proxies :). Is there already a way to tell nginx-proxy about a vhost that isn't a container but still receive an SSL certificate from letsencrypt or would that be a new feature?
Best regards.
Pascal Helfenstein

I don't think that is going to be easy to accomplish with this project. Probably you'll want to build the Let's Encrypt functionality into your first Nginx container. There is also a companion container @JrCs built which may give you an ideas for a way to inject the certificate into your server. https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion


[NuGet] Examples package: add dependency on Extensions

This change adds the extensions package as a dependency of the examples. This is needed to ensure the experimental ExamplesHub has all of the required script files available.

/azp run mrtk_docs

closing as the example that depends upon extensions is experimental. the code layout and dependency graph will be revisited in a future release (when examples hub is no longer experimental)


HIVE-26242: Compaction heartbeater improvements

What changes were proposed in this pull request?
This PR introduces a new component (CompactionHeartbeatService) to centralize the compaction transaction heartbeating, and reduce resource usage. It consist of a Scheduled exevutor service and a MetaStoreClient pool.
Why are the changes needed?
The heartbeat of the compaction txns are wasting resources by having a dedicated separate thread and MetaStore client for every compaction transaction.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manually and through unit tests.

I think we should do something like this:
    ExecutorService executorService = CompactorUtil.createExecutorWithThreadFactory(numberOfWorkers, "CompactionHeartbeat-executor-thread-%d");
    Ref<CompletableFuture<Void>> submittedTask = Ref.from(null);

    Future<?> scheduledTask = heartbeatExecutor.scheduleAtFixedRate(() -> {
      submittedTask.value = CompletableFuture.runAsync(heartbeater, executorService);
    }, initialDelay, period, TimeUnit.MILLISECONDS);
    tasks.put(txnId, new TaskWrapper(scheduledTask, submittedTask.value));
  }

void stopHeartbeat(long txnId) throws InterruptedException {
    ....
    wrapper.scheduledTask.cancel(false);
    try {
      wrapper.submittedTask.get(initialDelay, 100);
    } finally {
      tasks.remove(txnId);
    }
    ....
  }

I think we should do something like this:
ExecutorService executorService = CompactorUtil.createExecutorWithThreadFactory(numberOfWorkers, "CompactionHeartbeat-executor-thread-%d");

Future<?> submittedTask = heartbeatExecutor.scheduleAtFixedRate(() -> executorService.execute(heartbeater));
tasks.put(txnId, new TaskWrapper(heartbeater, submittedTask));

What is the benefit of this construct?

I think we should do something like this:
ExecutorService executorService = CompactorUtil.createExecutorWithThreadFactory(numberOfWorkers, "CompactionHeartbeat-executor-thread-%d");

Future<?> submittedTask = heartbeatExecutor.scheduleAtFixedRate(() -> executorService.execute(heartbeater));
tasks.put(txnId, new TaskWrapper(heartbeater, submittedTask));

What is the benefit of this construct?

none, I was playing with it trying to extract CompletableFuture, so we can just call 'join' or 'get' instead on manual hacks in runnable


support sandbox secret remove --all

Environment information
n/a

Describe the feature
It can be tedious to remove all secrets related to a sandbox environment without removing each individual secret, or by navigating to the AWS console to remove secrets manually. Support the --all flag on sandbox secret remove to remove all secrets in a single command
Use case
see above

Marking as feature request