Unable to authenticate

Hi - Thanks for the integration; I'm really grateful someone's finally done it :)
I want to report that the climate entities were showing up as unavailable in the last day or two. I tried reloading the integration and doing partial and full reboots of Home Assistant, but neither helped. I checked the logs and there was an authentication error. I didn't find a way to reconfigure the integration, so I opted to remove the integration altogether and add it back again.
As I did that, adding the integration asks you to sign in. I keep getting the "Invalid authentication" error (screenshot below). I can confirm that my username and password work. I validated that through the app and their online website; so it's not a credentials problem. Any ideas on how to proceed? Thanks in advance!

Works now! HACS hadn't picked up the new version. I managed to bump it and it's all good now. Thanks!


Added largest 5 digit number to CodeWars

Hey thanks for your contribution ❗. Keep up the good job and leave a star if you liked the repo .
Happy hacking 😉


All checks run at the same time causing spiky CPU and throttling

all our checks run at the same time and eats up a lot of cpu. it would be nice to have an offset value so the checks can be staggered to run at different times (or some random start time flag)

This is interesting. I think both custom plugin monitor and system stats monitor periodically checks node problems. Could you confirm which one is contributing to the CPU spikiness?
You could confirm by checking the period of the custom plugin monitor config and the period of the system stats monitor config, and then comparing them to the period of the CPU spikiness.
Thanks!


trigger dbt Cloud job and track progress with polling, with the option to do async

https://documenter.getpostman.com/view/14183654/UVsSNiXC#90e68665-c32f-44fa-b4cc-0ce2c8c7db69

This should display a nice link URL to the exact job run.
Example: https://cloud.getdbt.com/#/accounts/16173/projects/36467/runs/52180613/


Match Design Guidelines and Headless Components

Problem
As the app grows we must start relying on design guidelines to maintain consistent styling and user experience. Further, components must be customizable, and accessible for screen readers and keyboard users.
Proposed Solution
We must start creating components that adhere to our design guidelines and maintain accessibility throughout the app. Since we use Tailwind CSS it makes sense to use headless components like Headless UI and Radix that integrate beautifully and are accessible. Furthermore, following modern practices standardized by libraries like Material UI and Chakra UI, we'll use the library CVA to build components with variants to avoid the arduous task of class matching.
I've identified the following components that must be migrated/integrated:
Button

[ ] General Component

Popover

[ ] Topbar Settings
[ ] Transaction Settings

Modal

[ ] New Pool
[ ] Deposit
[ ] Withdraw
[ ] Connect Wallet

Switch

[ ] Assets table

Input

[ ] Search input

Select

[ ] Deposit (Network select)

Disclosure (can also be considered a drawer)

[ ] Token select
[ ] Bond Card

Adjust Swap settings to match Figma UI https://www.figma.com/file/om93lu8iXOhxwGHSUpAXEP/Trade-UI?node-id=93%3A1765&t=3ZhgpLpgcHzq2Pia-1

Closing in favor of tracking on ClickUp


OPENTRACING_FORWARD_HEADER throws error

Hello.
I've encountered a couple of issues when attempting to specify an alternative to uber-trace-id as the HTTP header used for forwarding opentracing information:

 APIcast/docs/parameter.md .  Minor problem:  Should be OPENTRACING_FORWARD_HEADER (not OPENTRACING_HEADER_FORWARD)

When adding an env var of OPENTRACING_FORWARD_HEADER set to: x-request-id, apicast bombs with this stack trace

I'm currently using the following version of apicast:
registry.access.redhat.com/3scale-amp24/apicast-gateway:1.13
thanks!

Seems to be the same issue reported here: https://issues.jboss.org/browse/THREESCALE-1660


Support new line protocol for ints

https://github.com/influxdb/influxdb/issues/3519

Enjoy :) https://github.com/influxdb/influxdb-fsharp/pull/6

Thanks!
FYI there still has possible issue with influxdb 0.9.3 #7


Please make a feature to revert the changes!

My PC has been running weird lately and I wanted to try to go back to see if it would fix the problem, but I can't without resetting my PC, please help!!

NO!!!
you deserve to live with the consequences, we live to learn!

Well I don't think you deserve the consequences, but you should have made a restore point.


Design of two-way streets with priority (= only one lane)

It seems that two-way streets are rendered as 2 separate lanes, even when there is a priority specified (= when there is actually only one lane, with a priority for backward or forward trafic)
See exemple :
https://www.openstreetmap.org/way/406015980

Trafic coming from here has to give way https://panoramax.ign.fr/#focus=pic&map=19/48.6062/7.751619&pic=f3634a35-8dc3-4627-bc11-e142cf2937fd&speed=250&xyz=38.80/6.76/14
Trafic coming from here has priority https://panoramax.ign.fr/#focus=pic&map=18.98/48.606289/7.751869&pic=c8a0bdd2-ab95-403f-8e57-2a83f608e90f&speed=250&xyz=260.81/-2.48/47

Going to keep this one open to think through Direction::Both support here and better rendering


detect_multiple_languages_of crashes on Arabic

The following command causes a panic exception:
>>> detector.detect_multiple_languages_of('صباغ الكتريك')
...
pyo3_runtime.PanicException: byte index 12 is not a char boundary; it is inside 'ل' (bytes 11..13) of `صباغ الكتريك`

This works:
>>> detector.detect_language_of('صباغ الكتريك')
Language.ARABIC

Hi @tbarkai, this bug has already been reported in #203. I've fixed it already and will release it when the other issues of the 2.0.2 milestone have been resolved.


Add unimplemented for 6 and 7 parameters

As I was writing a protocol witness for the Auth0 package I found some of their functions take 6 or 7 parameters.

Hey @kgrigsby59! Sorry for missing this, I think it came in during the busy period around WWDC. We'll take a look soon (we're both traveling and busy at the moment).

@kgrigsby59 Spoke with @mbrandonw about this today and we're mainly worried about the overload space slowing down compiler speed. We think 5 is probably the limit we want to have for now (and is maybe even more than we want, since we think most methods take <4 arguments), unless it can be demonstrated that additional overloads don't have an impact on downstream compile speed. So, if you have a dependency that requires 6+ arguments, we think it's probably OK to manually open up the closure and call XCTFail inside instead of expecting unimplemented to work.
One thing that might be worth looking into is if parameter packs allow us to avoid the overloads. Not sure if you'd be willing to see if parameter packs in 5.9 would allow us to do so...
Thanks for taking the time to PR, though! I'm going to close it for now, but if you do look into using parameter packs, we can either reopen, or you can open a new PR for us to take a look.

Hello. Parameter packs are implemented.
https://github.com/apple/swift-evolution/blob/main/proposals/0393-parameter-packs.md
Can we make it now and allow any number of arguments, or there are any other concerns?


Telegram refactor

Last try.

Travis failing with:
The command "conda install -y protobuf pylint -q" failed and exited with 1 during .

Is this woking ??

Yes.
On Sep 17, 2016 7:37 PM, "Simba Zhang"<EMAIL_ADDRESS>wrote:

Is this woking ??
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PokemonGoF/PokemonGo-Bot/pull/5514#issuecomment-247814638,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJJalbO2KoFhBWYSo50zlOWhp7D349pOks5qrHmmgaJpZM4J_pZE
.

👍  Nice

I can no longer merge so some else will need to.


Using thread_pool.gd as an autoload causes Parse Error

Assigning thread_pool.gd as an autoload with name ThreadPool causes Godot to disable the plugin and show the following error message: res://addons/thread_pool/thread_pool.gd:1 - Parse Error: The class "ThreadPool" conflicts with the AutoLoad singleton of the same name, and is therefore redundant. Remove the class_name declaration to fix this error.

Godot doesn't like that name anymore. 😞
You have to workaround using another name, like GlobalThreadPool.


Token Expired Issue with Auth::guard('api')->login($user) in Production

Subject of the issue
I'm experiencing an issue in production where tokens generated using Auth::guard('api')->login($user) are expiring prematurely with the error PHPOpenSourceSaver\JWTAuth\Exceptions\TokenExpiredException: Token has expired . This issue only occurs in the production environment, while local and staging environments work as expected. Here is some relevant configuration and setup information:
Your environment:

Q
A

Bug?
yes

New Feature?
no

Framework
Laravel

Framework version
^9.52.4

Package version
^2.2

Configuration: Here’s my current JWT configuration in config/jwt.php:
'ttl' => env('JWT_TTL', 60 * 24 * 30), // 30 days TTL
In .env, I have also set: JWT_TTL=43200
Steps to reproduce
Call Auth::guard('api')->login($user) and Auth::guard('api')->tokenById($user->user_id)
Expected behaviour
Token created
Actual behaviour
Throws exception PHPOpenSourceSaver\JWTAuth\Exceptions\TokenExpiredException: Token has expired

I have configured JWT without expiration by commenting out in jwt.php:
'required_claims' => [
    'iss',
    'iat',
    // 'exp', // uncomment if you want to make 'exp' a required claim
    'nbf',
    'sub',
    'jti',
],

config jwt.php :
<?php

return [
    /*
    |--------------------------------------------------------------------------
    | JWT Authentication Secret
    |--------------------------------------------------------------------------
    |
    | Don't forget to set this in your .env file, as it will be used to sign
    | your tokens. A helper command is provided for this:
    | `php artisan jwt:secret`
    |
    | Note: This will be used for Symmetric algorithms only (HMAC),
    | since RSA and ECDSA use a private/public key combo (See below).
    |
    */

    'secret' => env('JWT_SECRET', 'wBCLhvK4bVOHDXqVBIiHx9HyaYTWnt6AHvoacHlKi2W'),

    /*
    |--------------------------------------------------------------------------
    | JWT Authentication Keys
    |--------------------------------------------------------------------------
    |
    | The algorithm you are using, will determine whether your tokens are
    | signed with a random string (defined in `JWT_SECRET`) or using the
    | following public & private keys.
    |
    | Symmetric Algorithms:
    | HS256, HS384 & HS512 will use `JWT_SECRET`.
    |
    | Asymmetric Algorithms:
    | RS256, RS384 & RS512 / ES256, ES384 & ES512 will use the keys below.
    |
    */

    'keys' => [
        /*
        |--------------------------------------------------------------------------
        | Public Key
        |--------------------------------------------------------------------------
        |
        | A path or resource to your public key.
        |
        | E.g. 'file://path/to/public/key'
        |
        */

        'public' => env('JWT_PUBLIC_KEY'),

        /*
        |--------------------------------------------------------------------------
        | Private Key
        |--------------------------------------------------------------------------
        |
        | A path or resource to your private key.
        |
        | E.g. 'file://path/to/private/key'
        |
        */

        'private' => env('JWT_PRIVATE_KEY'),

        /*
        |--------------------------------------------------------------------------
        | Passphrase
        |--------------------------------------------------------------------------
        |
        | The passphrase for your private key. Can be null if none set.
        |
        */

        'passphrase' => env('JWT_PASSPHRASE'),
    ],

    /*
    |--------------------------------------------------------------------------
    | JWT time to live
    |--------------------------------------------------------------------------
    |
    | Specify the length of time (in minutes) that the token will be valid for.
    | Defaults to 1 hour.
    |
    | You can also set this to null, to yield a never expiring token.
    | Some people may want this behaviour for e.g. a mobile app.
    | This is not particularly recommended, so make sure you have appropriate
    | systems in place to revoke the token if necessary.
    | Notice: If you set this to null you should remove 'exp' element from 'required_claims' list.
    |
    */

    'ttl' => env('JWT_TTL', null),

    /*
    |--------------------------------------------------------------------------
    | Refresh time to live
    |--------------------------------------------------------------------------
    |
    | Specify the length of time (in minutes) that the token can be refreshed
    | within. I.E. The user can refresh their token within a 2 week window of
    | the original token being created until they must re-authenticate.
    | Defaults to 2 weeks.
    |
    | You can also set this to null, to yield an infinite refresh time.
    | Some may want this instead of never expiring tokens for e.g. a mobile app.
    | This is not particularly recommended, so make sure you have appropriate
    | systems in place to revoke the token if necessary.
    |
    */

    'refresh_ttl' => env('JWT_REFRESH_TTL', 60 * 24 * 60),

    /*
    |--------------------------------------------------------------------------
    | JWT hashing algorithm
    |--------------------------------------------------------------------------
    |
    | Specify the hashing algorithm that will be used to sign the token.
    |
    | See here: https://github.com/namshi/jose/tree/master/src/Namshi/JOSE/Signer/OpenSSL
    | for possible values.
    |
    */

    'algo' => env('JWT_ALGO', 'HS256'),

    /*
    |--------------------------------------------------------------------------
    | Required Claims
    |--------------------------------------------------------------------------
    |
    | Specify the required claims that must exist in any token.
    | A TokenInvalidException will be thrown if any of these claims are not
    | present in the payload.
    |
    */

    'required_claims' => [
        'iss',
        'iat',
        // 'exp', // uncomment if you want to make 'exp' a required claim
        'nbf',
        'sub',
        'jti',
    ],

    /*
    |--------------------------------------------------------------------------
    | Persistent Claims
    |--------------------------------------------------------------------------
    |
    | Specify the claim keys to be persisted when refreshing a token.
    | `sub` and `iat` will automatically be persisted, in
    | addition to the these claims.
    |
    | Note: If a claim does not exist then it will be ignored.
    |
    */

    'persistent_claims' => [
        // 'foo',
        // 'bar',
    ],

    /*
    |--------------------------------------------------------------------------
    | Lock Subject
    |--------------------------------------------------------------------------
    |
    | This will determine whether a `prv` claim is automatically added to
    | the token. The purpose of this is to ensure that if you have multiple
    | authentication models e.g. `App\User` & `App\OtherPerson`, then we
    | should prevent one authentication request from impersonating another,
    | if 2 tokens happen to have the same id across the 2 different models.
    |
    | Under specific circumstances, you may want to disable this behaviour
    | e.g. if you only have one authentication model, then you would save
    | a little on token size.
    |
    */

    'lock_subject' => true,

    /*
    |--------------------------------------------------------------------------
    | Leeway
    |--------------------------------------------------------------------------
    |
    | This property gives the jwt timestamp claims some "leeway".
    | Meaning that if you have any unavoidable slight clock skew on
    | any of your servers then this will afford you some level of cushioning.
    |
    | This applies to the claims `iat`, `nbf` and `exp`.
    |
    | Specify in seconds - only if you know you need it.
    |
    */

    'leeway' => env('JWT_LEEWAY', 300),

    /*
    |--------------------------------------------------------------------------
    | Blacklist Enabled
    |--------------------------------------------------------------------------
    |
    | In order to invalidate tokens, you must have the blacklist enabled.
    | If you do not want or need this functionality, then set this to false.
    |
    */

    'blacklist_enabled' => env('JWT_BLACKLIST_ENABLED', true),

    /*
    | -------------------------------------------------------------------------
    | Blacklist Grace Period
    | -------------------------------------------------------------------------
    |
    | When multiple concurrent requests are made with the same JWT,
    | it is possible that some of them fail, due to token regeneration
    | on every request.
    |
    | Set grace period in seconds to prevent parallel request failure.
    |
    */

    'blacklist_grace_period' => env('JWT_BLACKLIST_GRACE_PERIOD', 0),

    /*
    |--------------------------------------------------------------------------
    | Show blacklisted token option
    |--------------------------------------------------------------------------
    |
    | Specify if you want to show black listed token exception on the laravel logs.
    |
    */

    'show_black_list_exception' => env('JWT_SHOW_BLACKLIST_EXCEPTION', true),

    /*
    |--------------------------------------------------------------------------
    | Cookies encryption
    |--------------------------------------------------------------------------
    |
    | By default Laravel encrypt cookies for security reason.
    | If you decide to not decrypt cookies, you will have to configure Laravel
    | to not encrypt your cookie token by adding its name into the $except
    | array available in the middleware "EncryptCookies" provided by Laravel.
    | see https://laravel.com/docs/master/responses#cookies-and-encryption
    | for details.
    |
    | Set it to true if you want to decrypt cookies.
    |
    */

    'decrypt_cookies' => false,

    /*
    |--------------------------------------------------------------------------
    | Providers
    |--------------------------------------------------------------------------
    |
    | Specify the various providers used throughout the package.
    |
    */

    'providers' => [
        /*
        |--------------------------------------------------------------------------
        | JWT Provider
        |--------------------------------------------------------------------------
        |
        | Specify the provider that is used to create and decode the tokens.
        |
        */

        'jwt' => PHPOpenSourceSaver\JWTAuth\Providers\JWT\Lcobucci::class,

        /*
        |--------------------------------------------------------------------------
        | Authentication Provider
        |--------------------------------------------------------------------------
        |
        | Specify the provider that is used to authenticate users.
        |
        */

        'auth' => PHPOpenSourceSaver\JWTAuth\Providers\Auth\Illuminate::class,

        /*
        |--------------------------------------------------------------------------
        | Storage Provider
        |--------------------------------------------------------------------------
        |
        | Specify the provider that is used to store tokens in the blacklist.
        |
        */

        'storage' => PHPOpenSourceSaver\JWTAuth\Providers\Storage\Illuminate::class,
    ],
];

my .env
JWT_TTL=null
In the staging environment, the JWT no longer has an expiration. However, in production, it still has an expiration.

Try:
php artisan config:clear


{CDN} Fix rule creation failure with action type RouteConfigurationOverride and route creation issue with disabled --link-to-default-domain option

Description

az afd rule create: Fix rule creation failure with action type RouteConfigurationOverride
az afd rule create: Fix route creation issue with disabled --link-to-default-domain option
Testing Guide

Test rule creation with action type "RouteConfigurationOverride"
az afd rule create --action-name RouteConfigurationOverride --order 1 --profile-name p-bugbash101 --resource-group bogroup --rule-name rule2204071 --rule-set-name rs0407
Test route creation with --link-to-default-domain set to Disabled
az afd route create -g "bogroup" --custom-domains "domain1" --endpoint-name "bugbash101" --profile-name "p-bugbash101" --route-name "test-route" --https-redirect Enabled --origin-group "og0407"  --supported-protocols Http Https --link-to-default-domain "Disabled" --forwarding-protocol HttpOnly --patterns-to-match /test345/*
History Notes

[CDN] az afd rule create: Fix rule creation failure with action type RouteConfigurationOverride
[CDN] az afd route create: Fix route creation issue with disabled --link-to-default-domain option

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Fix https://github.com/Azure/azure-cli/issues/21938

Fix https://github.com/Azure/azure-cli/issues/21844

Hi @necusjz will you help to take a look at the PR?


Certik revisions for Beta-Protocol

The Following Issues are addressed in this pull request
ARO-01
ARR-02
MAO-01
RBS-01
RBS-04
SRR-01
TUO-01

Please have more attention to detail while writing and reviewing contract code (as I've mentioned I didn't review the tests)

Apologize for being inconsistent with code quality. These small inconsistencies frustrate me as well and I'll try to avoid pushing such changes.
I've updated the code according to the review comments.

Thanks, will do a second pass tomorrow


Add slideshow to animals to be adopted

We want to add one or more pictures for our animals onto their rehoming page.
The theme unfortunately does not have a build-in way of doing so, so we need to add it by ourselves.

current look:


Script to build and package Cloud Tools for PowerShell

Adds a script to automate the process of building and packaging the cmdlets so they can be
added to the Cloud SDK installer.
The script is very straight forward, the only tricky part is the introduction of a new
GoogleCloudPowerShell.psd1 module. This is necessary to maintain backwards compatibility
with existing Cloud SDK installs due to the new module layout from the fix to #314 / #315.
Existing installs have the PSModulePath pointed to a GoogleCloudPowerShell folder that
will no longer exist after gcloud components update gets run. So we put this new module
in that location, so it will load the updated assemblies.
New installs will have their PSModulePath pointed to a PowerShell folder, and and will not
pick up the new module located in ..\GoogleCloudPowerShell directory.

@ILMTitan PTAL

PTAL

Done.


Organise an internal project announcement webinar

Context
Organise an internal webinar for GSF Member Orgs where @aecurrie can speed-walk us through how this project got started, what we hope to achieve during incubation, and how we will measure the impact/success.
https://github.com/Green-Software-Foundation/green-software-maturity-matrix/wiki/2024‐01‐XX:-GSF-Member-webinar
Acceptance Criteria

[ ] Schedule for after https://github.com/Green-Software-Foundation/green-software-maturity-matrix/issues/5
[ ] Only open to GSF Member organisations

Actions

[ ] @aecurrie @NAMRATA-WOKE agree basic details (when & where)
[ ]

Hia, I think an introductory webinar (Q&A?) is a great idea to get people to understand a project and decide if they want to get involved!
What's the thinking around how we communicate this to members? An explicit dedicated email that goes out to members inviting them to this session, or a mention in one of our existing regular communications which goes out to all members with a registration link?

Yes I think a webinar is a great idea. I'm currently swamped trying to earn
some money so it might have to be Feb before we record it (given by then
I'll have to have done an educational session on it for my new course
https://maven.com/strategically-green/softwarep-iwolil)
We were thinking explicit email?
On Fri, Dec 22, 2023 at 4:01 PM Asim Hussain @.***>
wrote:

Hia, I think an introductory webinar (Q&A?) is a great idea to get people
to understand a project and decide if they want to get involved!
What's the thinking around how we communicate this to members? An explicit
dedicated email that goes out to members inviting them to this session, or
a mention in one of our existing regular communications which goes out to
all members with a registration link?
—
Reply to this email directly, view it on GitHub
https://github.com/Green-Software-Foundation/green-software-maturity-matrix/issues/17#issuecomment-1867846199,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2TULCY76V5IDQ33LWG4DLYKWVFBAVCNFSM6AAAAAA77OSKBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRXHA2DMMJZHE
.
You are receiving this because you were mentioned.Message ID:
<Green-Software-Foundation/green-software-maturity-matrix/issues/17/1867846199
@github.com>

Ahh yes I saw you're course announcement, very exciting!!!
Let's discuss how to announce this, if we do an explicit email then we'd have to offer every project an explicit email and that's a lot of explicit emails! We normally just highlight things in our regular communication and we only send explicit emails for our main events like decarb and the hackathon to reduce noise.
But perhaps let's think differently about this, what would be a successful outcome for you for this session? More contributors? Specific buy in from member organizations to adopt? What does success look like?
This is an async project I believe so you can have external contributors right? If so then are you looking for more external eyeballs/collaborators on this?
What about a very short 2 min video which we have our producer edit down and perhaps add some graphics, and then somehow share it to our members in a way that they can comment async? Just thinking out of the box for alternatives, esp. ones that down require a meeting since that alienates large parts of our membership.
wdyt?

Sorry for the slow response. The OR book is finally submitted so I've
returned to the world ;-) That contains a link to the project and the GSF
graphic so good for bringing in externals (my suspicion is that won't be
too tricky)
Very happy to do the announcement in the general comms. Yes a 2 min video
is fine. Perhaps that's the best thing although I'd also be happy to do a
kickoff in different timezones.
I think this is something where we need as many people at least aware as
possible both inside and outside the GSF. I think Namrata has been
mentioning it and it sounds like there are a few folk already interested.
Perhaps a chat about it on EnvVars would be a good option? I haven't been
on in a while!
On Thu, Dec 28, 2023 at 4:02 PM Asim Hussain @.***>
wrote:

Ahh yes I saw you're course announcement, very exciting!!!
Let's discuss how to announce this, if we do an explicit email then we'd
have to offer every project an explicit email and that's a lot of explicit
emails! We normally just highlight things in our regular communication and
we only send explicit emails for our main events like decarb and the
hackathon to reduce noise.
But perhaps let's think differently about this, what would be a successful
outcome for you for this session? More contributors? Specific buy in from
member organizations to adopt? What does success look like?
This is an async project I believe so you can have external contributors
right? If so then are you looking for more external eyeballs/collaborators
on this?
What about a very short 2 min video which we have our producer edit down
and perhaps add some graphics, and then somehow share it to our members in
a way that they can comment async? Just thinking out of the box for
alternatives, esp. ones that down require a meeting since that alienates
large parts of our membership.
wdyt?
—
Reply to this email directly, view it on GitHub
https://github.com/Green-Software-Foundation/green-software-maturity-matrix/issues/17#issuecomment-1871301863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2TULAWB67C2B5GD57CQELYLWJYHAVCNFSM6AAAAAA77OSKBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZRGMYDCOBWGM
.
You are receiving this because you were mentioned.Message ID:
<Green-Software-Foundation/green-software-maturity-matrix/issues/17/1871301863
@github.com>

So is the goal to raise the profile of the project more generally? A winning hearts and minds tour? Hmm how about a proper open source speakers deck with nice graphics, get lots of people speaking about it at conferences?
Things like that?
Or like specifically getting companies onboard to use it so you've got hard case stufies. cause thats a different approach I think, more 1-1tlc.

Reached out to Namrata on 17th May to start scheduling

@russelltrow @aecurrie am I clear to understand this is an internal webinar for GSF members? If so, I'd recommend creating a Doodle with 4-5 day/time options to share with GSF-all to give them a 'vote' on when to host the webinar. The days/times can come from Anne and the project co-lead based on their availability.
I can then inform everyone and specifically reach out to those who have shown an interest in the project's outcomes.
If we can target end June/early July, that would be great.

Actually, the idea was to organise an open webinar for a wider community to start promoting adoption of the GSMM.
We could explain the main idea and discuss initial steps in the green software journey

@NAMRATA-WOKE that works.
@pinireznik / @aecurrie if the project is in a finished state then before public release it needs to go through a consensus approval by the WG and then ratified by the SC. I'd give plenty of time for people to review, information is passing slowly through orgs right now, maybe the internal meeting can be an exercise to explain the work to the members so they are informed before being asked to give consensus to it's publishing?

We had something else in mind - start explaining the Matrix to potential
users with a message that it is still WIP. We would mostly talk about the
first steps a typical company would want to take before trying to achieve
everything at once.
But an internal webinar for members sounds good too. Anne, what do
you think?
BTW, Asim, a bit off topic, we're using PACT Pathfinder
https://www.wbcsd.org/Programs/Climate-and-Energy/Climate/SOS-1.5/News/Pathfinder-Framework-Version-2.0
as Scope 3 emissions sharing standard and earlier this week I was talking
with the project PO and she didn't know anything about GSF.
Do you know about this project? Is some sort of collaboration between the
foundations relevant?
If you like, I can make an introduction and you can explore it with them
directly.
Pini
On Thu, May 23, 2024 at 11:17 PM Asim Hussain @.***>
wrote:

@NAMRATA-WOKE https://github.com/NAMRATA-WOKE that works.
@pinireznik https://github.com/pinireznik / @aecurrie
https://github.com/aecurrie if the project is in a finished state then
before public release it needs to go through a consensus approval by the WG
and then ratified by the SC. I'd give plenty of time for people to review,
information is passing slowly through orgs right now, maybe the internal
meeting can be an exercise to explain the work to the members so they are
informed before being asked to give consensus to it's publishing?
—
Reply to this email directly, view it on GitHub
https://github.com/Green-Software-Foundation/green-software-maturity-matrix/issues/17#issuecomment-2128034474,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOJRVBKK2M3MXGHGRFVAZDZDZMHTAVCNFSM6AAAAAA77OSKBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRYGAZTINBXGQ
.
You are receiving this because you were mentioned.Message ID:
<Green-Software-Foundation/green-software-maturity-matrix/issues/17/2128034474
@github.com>

@aecurrie @pinireznik Can you help me understand the desired outcome?
Suppose the objective is to gain support to develop/refine the matrix. In that case, we should focus the event on our members because they are the group of people who can actually get into it and develop the project with you. Prini's suggestion and sharing a couple of specs for how members can contribute can be helpful.
If we aim to raise awareness about the project and, in this early stage, have people use it and offer feedback or give some insight into its effectiveness. Again, I would focus on increasing adoption within our member network as its not a graduated project, and create a use case template or survey that we can ask users to complete to capture information systematically. It might even be worth creating a Pilot for member organizations to adopt -- where we lay out the conditions for use to validate/debunk a critical assumption?
@russelltrow curious to hear your thoughts on the above!

@pinireznik that actually sounds pretty interesting and valid for some of out other projects (like IF) feel free to connect them to me if you want<EMAIL_ADDRESS>cheers!
@aecurrie
Let's chat about where this project is, I'm a little confused :/
From what I can see from the repo:

The only contributor according to GH is @russelltrow!
There have been 2 PRs start/end of last year and one is open and not merged.
This is currently a draft consensus project in the GSF.
There is communication about this wanting to be discussed with external people in an adoption capacity, which is something we can only do when the project has consensus of the members, ratified by the steering committee. Until then the communication externally has got to be in terms of getting feedback and the feedback has got to come in a way that is captured in the repo (ideally as a PR but can also be an issue template). We also need to ensure DCO is setup correctly to make sure that any non-members who provide feedback are also automatically signing that they are free to provide their feedback royalty free etc... all members have already signed that in their membership agreement.

Is this project "finished", in terms of that the core team is happy with the content and ready to get to the next stage? If not then the fact there has been no updates in 6 months indicates this project has stalled and should be archived!
If it's finished the next stage is getting feedback from the members of the GSF in such a form that there feedback is recorded in the repo. I'd recommend an issue template, ask a few questions you specifically want answers to and also we should preliminary as them if in it's current form they would endorse, consent or object. That will give us some early signals, you really only want to go for consensus once you're pretty sure you'll get it.
You'll need to deal with whatever feedback you get, esp. any people who've said they would object - update content etc...
Once we've done that internally then the next step might be to get some external feedback, same form, send people the link to specifically provide feedback in the repo. That's not necessary for internal consensus but it's good to have if you want to attempt to get this into an an ISO standard.
Ultimately once we've done a very explicit round of formally asking and recording feedback, if it all looks good we need to send it out for a consensus vote amongst all our members and again give them the opportunity to endorse, consent or object.
If there are no objections then we go for ratification by the SC.
Once it's ratified, it's a proper, published GSF project and we can put all our energies into promoting it, sharing it etc... and if there is interest, perhaps trying for an ISO certification.
If you are not ready and want some super early feedback we can try to arrange an internal workshop, if you are "ready" as it looks like you are, then a feedback form and formal request to provide feedback is probably the right way. We can facilitate an email asking org leads to fill out a form, it's is a lot easier for everyone to action rather than joining a call, also having people submit issues is a a great way to demonstrate that this project has engagement/consensus. These requests tend to get fielded internally inside organizations, they huddle together, decide how they are going to respond and then respond (or don't!).
But ultimately I think you need to decide what your goal for this project is, if you don't want to go for consensus and have this published as a GSF product then we can perhaps help publish this as an opinion piece on our blog if that helps?
If you want to eventually go for ISO we need to be very careful about how we demonstrate who contributes to this project, ISO want to see lots of evidence of multiple organizations engaging, lots of contributors on the repo is best (which is why it's a problem this started out as a gdoc and that @russelltrow is the only contributor) but if there are lots of people giving feedback as issues on the repo that works also. For the SCI we demonstrated there were 20+ organizations who contributed.
If this eventually wants a chance to get into regulation, then that's where all our frustrating rules become a life saver - we can guarantee as much as possible that everyone who's contributed has released any IP so if it goes to regulation, no company can come back years later and ask for royalty fees. We can only do that if all contributions are evidenced through GitHub, we can prove who contributed every line of the text and also prove that that person either worked for a member org who released their IP in their membership agreement or signed a DCO which does the same for external contribution.
Makes sense?


Fix probeSelector typo in VMAgent example

Sorry, just a small typo fix

Thanks for contribution!
Feel free to submit any other fixes.


Remove remaining usages of legacy Rect2D component

What
Followup to

https://github.com/rerun-io/rerun/pull/3282

Fully removes old Rect2D component. Had to patch over some tests. re_query range example is slightly incomplete for the moment.
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[ ] I have tested demo.rerun.io (if applicable)

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

alright that should be better, now we wait... :slow_beach_ball:

oh didn't even notice that one yet. Thanks so much for swooping in and fixing it!


AttributeError: 'ClientInfo' object has no attribute 'to_grpc_metadata'

Environment details

OS type and version: MacOS 13.0 (22A8380)
Python version: 3.8.0
pip version:  19.2.3

Steps to reproduce

Requirements:

cachetools==5.3.3
certifi==2024.2.2
charset-normalizer==3.3.2
Deprecated==1.2.14
google-api-core==2.17.1
google-auth==2.28.1
google-cloud-bigquery==3.17.2
google-cloud-core==2.4.1
google-cloud-documentai==2.24.0
google-cloud-documentai-toolbox==0.13.0a0
google-cloud-storage==2.14.0
google-cloud-vision==3.7.1
google-crc32c==1.5.0
google-resumable-media==2.7.0
googleapis-common-protos==1.62.0
grpc-google-iam-v1==0.12.7
grpcio==1.62.0
grpcio-status==1.62.0
idna==3.6
immutabledict==3.0.0
intervaltree==3.1.0
Jinja2==3.1.3
lxml==4.9.4
MarkupSafe==2.1.5
numpy==1.24.4
packaging==23.2
pandas==2.0.3
pikepdf==8.13.0
pillow==10.2.0
proto-plus==1.23.0
protobuf==4.25.3
pyarrow==15.0.0
pyasn1==0.5.1
pyasn1-modules==0.3.0
python-dateutil==2.9.0
pytz==2024.1
requests==2.31.0
rsa==4.9
six==1.16.0
sortedcontainers==2.4.0
tabulate==0.9.0
tzdata==2024.1
urllib3==2.2.1
wrapt==1.16.0

Execution:
python3 main.py

Code example
main.py:

from google.cloud import documentai
from google.cloud.documentai_toolbox import document

wrapped_document = document.Document.from_batch_process_operation(
    operation_name=operation_name
    location=location
)

wrapped_document.entities_to_bigquery(
        dataset_name=dataset, table_name=table, project_id=project
)

Stack trace
  File "main.py", line 4, in <module>
    wrapped_document = document.Document.from_batch_process_operation(
  File "/<my_script_location>/venv/lib/python3.8/site-packages/google/cloud/documentai_toolbox/wrappers/document.py", line 600, in from_batch_process_operation
    metadata=_get_batch_process_metadata(
  File "/<my_script_location>/venv/lib/python3.8/site-packages/google/cloud/documentai_toolbox/wrappers/document.py", line 156, in _get_batch_process_metadata
    client = documentai.DocumentProcessorServiceClient(
  File "/<my_script_location>/venv/lib/python3.8/site-packages/google/cloud/documentai_v1/services/document_processor_service/client.py", line 775, in __init__
    self._transport = Transport(
  File "/<my_script_location>/venv/lib/python3.8/site-packages/google/cloud/documentai_v1/services/document_processor_service/transports/grpc.py", line 187, in __init__
    self._prep_wrapped_messages(client_info)
  File "/<my_script_location>/venv/lib/python3.8/site-packages/google/cloud/documentai_v1/services/document_processor_service/transports/base.py", line 134, in _prep_wrapped_messages
    self.process_document: gapic_v1.method.wrap_method(
  File "/<my_script_location>/venv/lib/python3.8/site-packages/google/api_core/gapic_v1/method.py", line 241, in wrap_method
    user_agent_metadata = [client_info.to_grpc_metadata()]
AttributeError: 'ClientInfo' object has no attribute 'to_grpc_metadata'```

Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!

The code below uses ClientInfo from google.api_core.client_info.py
https://github.com/googleapis/python-documentai-toolbox/blob/ecb656cd88d36b401587f4173882e5238d8dbea0/google/cloud/documentai_toolbox/utilities/gcs_utilities.py#L27-L28
However there is also a ClientInfo in google/api_core/gapic_v1/client_info.py which has the to_grpc_metadata method
The latter one is the one used in gapic-generator-python.
https://github.com/search?q=repo%3Agoogleapis%2Fgapic-generator-python "clientinfo"&type=code
Changing the code below to use ClientInfo from google/api_core/gapic_v1/client_info.py instead of google.api_core.client_info.py should resolve the issue ClientInfo' object has no attribute 'to_grpc_metadata'
https://github.com/googleapis/python-documentai-toolbox/blob/ecb656cd88d36b401587f4173882e5238d8dbea0/google/cloud/documentai_toolbox/utilities/gcs_utilities.py#L27-L28

from google.cloud import documentai
from google.cloud.documentai_toolbox import document

wrapped_document = document.Document.from_batch_process_operation(
    operation_name=operation_name
    location=location
)

wrapped_document.entities_to_bigquery(
        dataset_name=dataset, table_name=table, project_id=project
)

Not sure if this was just a copy-paste error, but there should be a comma after operation_name=operation_name before the location parameter. The code won't run otherwise, but it's this error instead.
    operation_name=operation_name
                   ^^^^^^^^^^^^^^
SyntaxError: invalid syntax. Perhaps you forgot a comma?

I was able to reproduce this behavior in Python3.8 in the compiled library only.
I'll also add in Samples (w/tests) for this import method to catch this.

I think I see why this wasn't an issue earlier. In #249, I made changes to how from_batch_process_operation() gets the Operation data, which might now require the gapic import for 3.8. The Unit/Integration tests didn't catch this.

@holtskinner thanks for addressing this so quickly! But now Im getting another error: the method 'from_batch_process_metadata' raises the following error,
ValueError: Invalid Document - shardInfo.shardCount (1) does not match number of shards (1053)

which is strange to me, since I expected to input my operation name (that succeeded FYI), and get all the wrapped documents. But the error is claiming that there are too many shards (?).
The same thing happens if I use the 'from_gcs' method, passing the root directory (<root_operation> dir let's call it) of that operation output as gcs_prefix. If I use the <root_operation_dir>// as gcs_prefix, the method succeeds.


ResourceManagementClient resources list operation doesn't include resource tags

I want to list resources in Azure filtering by a specific tag and then perform operations based on other tags the resource might have.
Listing resources by tag works correctly. However, the resources returned by the list operation always have the following:
tags = {NoneType} None

Even though the resources have tags.
Code snippet:
def get_resources_by_tag(tag_name, tag_value):
    """
    Retrieves a list of resources in Azure that contain a specific tag with a certain value.
    :param tag_name: The name of the tag to filter resources
    :param tag_value: The value of the tag to filter resources
    :return: A list of resources matching the tag criteria
    """
    rm_client = get_client_from_cli_profile(ResourceManagementClient)
    logger.info(f"Collecting Azure resources for {tag_name} = {tag_value}")
    resources = rm_client.resources.list(filter=f"tagName eq '{tag_name}' and tagValue eq '{tag_value}'")

    return list(resources)

I am using:
Python 3.7.3

And I have tried with azure-mgmt-resource 2.2.0 up to  azure-mgmt-resource 5.0.0

Hi @antgonmir,
Thanks for reporting this issue - Do you mind attaching a sample response of the list operation that you tried so @hamidtirmizi can take a look?
Thanks.

Hi @antgonmir, this is currently the expected behavior. Listing resource using tag filters does not return tags at present.
This is one of the things we are working on, and targeting for enabling early next year.

Thanks @hamidtirmizi,
I have verified that I can retrieve the resource tags by using the list_by_resource_group method, which provides a reasonable workaround.
I would suggest mentioning the limitation that listing resources using tag filters has in the documentation.
Other than that, I guess this issue can be closed.
Thanks.

Thanks @antgonmir
Documentation would be updated as suggested - https://github.com/Azure/azure-rest-api-specs/pull/7721


Option for MySQL?

For a number of projects, MySQL is still required and not PostgreSQL - can you create a requirements file that does not require PostgreSQL  and allows for MySQL?

Hi @gamesbook ! Thanks for your interest in the project
This project should be an starting point to create a django project and changing the database backend it's easy, just modify the requirements.txt and the settings. I think create a separate requirements file will create an extra overhead for very little benefit.
I was planning to include both in the requirements file but sometimes either psycopg2 or mysql-python give problems during installation. Again too much trouble for very little gain.
Sorry for my broken English.

@fasouto Yes, I did create my own requirements file.  Perhaps the point is to not include any database-specific modules in the base requirements file at all; certainly the one for PostgreSQL generates an error on a machine without PostgreSQL already installed (you can test that yourself) which seems to defeat the point of a ready-to-use template.

I think it's quite the opposite: remove the DB support defeat the point of having a ready-to-use template that covers the majority of the cases. While there are many sites that work without a database I think most Django projects are backed by one.
This project template is opinionated: some people won't need bootstrap, others won't need django-compressor.... if I removed everything else I will end with a barenones django-admin startproject  :smile:


Update docs for feat: etcd election componet for pg_kv_backend

A document change request is generated from https://github.com/GreptimeTeam/greptimedb/pull/5127

Close this since PR 5127 has been closed.


CUDA 10.1, failure to copy cublas_v2.h to build directory (again)

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Fedora 29
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source
TensorFlow version: 1.13
Python version: 3.7.4
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source): 19.2
GCC/Compiler version (if compiling from source): 7.4
CUDA/cuDNN version: 10.1 / <IP_ADDRESS>
GPU model and memory: GeForce GT 750M with 2 GB

Describe the problem
As with the second issue in #28936, I am having problems when compiling tensorflow with CUDA 10.1. It seems that libcublas_v2.h is not being copied to the build directory. That ticket was closed with a comment indicating that it was due to a bug that had been fixed -- but the bug seems to have returned.
Provide the exact sequence of commands / steps that you executed before running into the problem

Installed CUDA 10.1 and cuDNN 7.5.
Created logical links from /usr/lib64 to /usr/local/cuda-10.1/targets/x86_64-linux/lib/ for libcublas.so.10.1 (This removed the first issue reported in #28936.)
Ran ./configure, accepting defaults, except 'Y' for CUDA support, 3.0 for Cuda capability (actually, this is the default, as my GPU is correctly identified)
bazel clean --expunge
TMP=/tmp time bazel build --config=opt --local_resources=6144,6,1.0 //tensorflow/tools/pip_package:build_pip_package

This ran for more than an hour before yielding the error:
ERROR: /usr/local/src/git/tensorflow/tensorflow/core/kernels/BUILD:2809:1: C++ compilation of rule '//tensorflow/core/kernels:cholesky_op' failed (Exit 1)
In file included from tensorflow/core/kernels/cholesky_op.cc:35:0:
./tensorflow/core/kernels/cuda_solvers.h:29:10: fatal error: cuda/include/cublas_v2.h: No such file or directory
 #include "cuda/include/cublas_v2.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~

Note that unlike the report for #28936, the file is missing from cuda/include/, rather than third_party/gpus/cuda/include/.
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

My mistake: ran the clean --expunge after, rather than before, ./configure.


Feat/prettier integration

Description
This PR fixes #129: Integrated Prettier for consistent code formatting and updated project documentation.
Changes Made:

Installed Prettier (npm install --save-dev prettier).
Configured .prettierrc for uniform formatting rules.
Added formatting (npm run format) and checking (npm run format:check) scripts for JavaScript, TypeScript, JSON, CSS, SCSS, and Markdown files in src.
Updated documentation with Prettier usage instructions.

Looks good! Thanks for the contributions!


AL(AA0131) The number of parameters passed to a string must match the placeholders

Describe the bug
Getting the warning:
AL(AA0131) The number of parameters passed to a string must match the placeholders
Despite having the same number of parameters as the number of placeholders.
To Reproduce
In VScode, use:
local procedure WhyIsThereAWarning()
    var
        SalesHeader: Record "Sales Header";
        PmtDiscText: Text;
        PmtDiscTxt: Label 'If we receive the payment before %1, you are eligible for a 2% payment discount.', Comment = '%1 Discount Due Date %2 = value of Payment Discount % ';
    begin
        PmtDiscText := StrSubstNo(PmtDiscTxt, SalesHeader."Pmt. Discount Date", SalesHeader."Payment Discount %");
    end;

Expected behavior
Since using two parameters and two placeholders, we do not expect a warning for this.
Also tried this with a field of the sales header without a '%' in the name, but that didn't change anything to the warning.
Screenshots
Summary:

5. Versions:

AL Language: 6.0.344420

Typo: You don't ever substitute in %2; instead, you write 2% unconditionally...

As mentioned above you have one placeholder and two substitutions.

My bad, been staring at code whole day, fixing warnings for upcoming BC17 and just never saw the typo in it. Thanks!


convert api_clients:last_access from date to datetime

Fixes #2742
I did not include the resulting db/schema.rb in this PR,
as it accidentally includes other tables as well that I happen
to have in my database. Not sure if that file is even necessary.
Previous entries in last_access now have zero time appended to the date.

Pff, apparently it is important to update schema.rb: https://github.com/DMPRoadmap/roadmap/pull/2764/checks?check_run_id=1564220368 (its runs rails db:setup)
It do not feel confident enough to update the schema manually, and discard unwanted stuff.

Hi @nicolasfranck I have submitted a new PR #2766 that adds the appropriate schema.rb updates to your migration here. Please have a look and make sure that it looks correct.


Exception Handling

Hi Team -
I am facing an issue with running profiler on a datetime column in my dataset. Ideally, the values in this column are in the format, for example, "Tue Apr 03 18:00:12 +0000 2012". But there are some exceptions to this rule. In some cases, the values are a long number which results in following error being thrown -
OverflowError: signed integer is greater than maximum
at org.apache.spark.api.python.BasePythonRunner$ReaderIterator.handlePythonException(PythonRunner.scala:332)
at org.apache.spark.sql.execution.python.ArrowPythonRunner$$anon$1.read(ArrowPythonRunner.scala:171)
at org.apache.spark.sql.execution.python.ArrowPythonRunner$$anon$1.read(ArrowPythonRunner.scala:155)
at org.apache.spark.sql.execution.python.ArrowPythonRunner$$anon$1.read(ArrowPythonRunner.scala:121)
at org.apache.spark.api.python.BasePythonRunner$ReaderIterator.hasNext(PythonRunner.scala:286)
at org.apache.spark.InterruptibleIterator.hasNext(InterruptibleIterator.scala:37)
at org.apache.spark.sql.execution.python.ArrowEvalPythonExec$$anon$2.hasNext(ArrowEvalPythonExec.scala:101)
at scala.collection.Iterator$$anon$11.hasNext(Iterator.scala:408)
at org.apache.spark.sql.catalyst.expressions.GeneratedClass$GeneratedIteratorForCodegenStage2.agg_doAggregateWithKeys_0$(Unknown Source)
at org.apache.spark.sql.catalyst.expressions.GeneratedClass$GeneratedIteratorForCodegenStage2.processNext(Unknown Source)
at org.apache.spark.sql.execution.BufferedRowIterator.hasNext(BufferedRowIterator.java:43)
at org.apache.spark.sql.execution.WholeStageCodegenExec$$anonfun$10$$anon$1.hasNext(WholeStageCodegenExec.scala:619)
at scala.collection.Iterator$$anon$11.hasNext(Iterator.scala:408)
at org.apache.spark.shuffle.sort.BypassMergeSortShuffleWriter.write(BypassMergeSortShuffleWriter.java:125)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:96)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:53)
at org.apache.spark.scheduler.Task.run(Task.scala:109)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:345)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
... 1 more

I am trying to delete those records which have bad datetime value and collect in a separate dataframe for analysis purpose. I would appreciate your help if you can please guide me how it can be done with the help of optimus. The library is so promising that my expectations keep on increasing, sorry for that :)
Thank you for your help.
Best-
Ishan

Hi @IshanDindorkar,
Can you help me with the exact line number that is raising the Exception?
Or much better can you paste a link to some data so I could replicate the error? Maybe via dropbox o google drive

Hi @argenisleon ,
I tried capturing that part of dataset which is creating issue but it is more than 5GB. I am not able to even open that in an editor like Notepad++ or something. I created a dummy dataset that would resemble the situation and attached with this. Please let me know if it helps you in recreating the scenario.
Thank you again for your help. Much appreciated.
error_reproduce.txt

To be sure. What are the columns data types? Can you run df.cols.dtypes() and paste the result here?
To handle your case I think you can use df.rows.drop_by_dtypes("names","int") to delete the that rows? Or what are you planning to do with those values?

Not right now near my laptop so couldn’t run these commands. drop_by will help me serve my purpose but I wanted to copy those rows to another data frame before deleting. Is there any operation which just filters rows in data frame based on type of values in a specific column?

Sure,
You can use df.rows.select_by_dtypes("your_columns","int")

Thanks!


Update README

This PR retouches the wording, updates the links and make it more clear for people to learn about Server Components in Next.js.

Let's keep this on hold for now 👍


Aborts on what():  data for rust::String is not utf-8 on non-utf8 terminals (LC_CTYPE)

Newsboat version: r2.23-141-g83ca0
Config file: [no config - started with -C /dev/null]
This was apparently introduced in 7eb8cbdb832bc74ee0f1fc3b1cdf86a24ad3544d. Found using git bisect.
Steps to reproduce the issue:

Add https://www.theregister.co.uk/headlines.atom to ~/.newsboat/urls
Start LC_CTYPE=en_US newsboat -C /dev/null or export LC_CTYPE=en_US ; newsboat -C /dev/null
Refresh the feeds and type Enter to view the feed.

-> Results in a broken terminal and an abort message:
Newsboat r2.23-141-g83ca0 - Your feeds (1 unread, 1 total)
terminate called after throwing an instance of 'std::invalid_argument'
                                                                        what():  data for rust::String is not utf-8
                                         Aborted

Other info:

rustc 1.51.0
gcc 10.3.0

@Minoru , did this get fixed? Are there still plans to fix it? Is there a workaround in the meanwhile?

@danniel3 It's not yet fixed, but of course there are plans! I think we need to create our own string type that would guarantee that its contents are encoded in UTF-8; then, we'll add encoding conversions to all the places that talk to outside world (including our own database if possible, to keep backwards compatibility). I started working on the string type a while ago, but it's a big task and I didn't finish it yet.
I won't hold a grudge if someone else just steals the idea, improves it, and sends me a nice pull request. I won't yell at you, honestly! :)
There are only two workarounds, to my knowledge:

downgrade to an older Newsboat (I don't know the exact version, probably a year old or even more);
remove ~/.newsboat/cache.db, loosing all the accumulated articles, flags etc., but maybe getting Newsboat to start again.

Not a good look, I realize. I'm really sorry about that ._.


Added parse function to retrieve the port from an address

see #404

Coverage increased (+0.05%) to 75.221% when pulling 1db5185d7ca6c50396b8dc48dea63544dc1caaac on fix/parse-ports into 47c74df7cc9c560c88deb2b9fae00e03a26fb4dd on develop.

Coverage increased (+0.06%) to 75.229% when pulling beac9e6349afa98bbb9856b853f6b1527c45379a on fix/parse-ports into 47c74df7cc9c560c88deb2b9fae00e03a26fb4dd on develop.


Nan loss during training

Dear authors,
I used bi_tempered_binary_logistic_loss as my NN's loss function, and I noticed that after a few hundreds steps training, some loss becomes nan. I printed the value outputted by bi_tempered_binary_logistic_loss and confirmed the nan value was from bi_tempered_binary_logistic_loss. Any idea why? Do I need to adjust the parameter setting and how? Thank you for answering!!

Can you please share more details about your hyperparameters? Generally, if your model is stable with t1 = t2 = 1.0 (i.e. cross entropy loss), it should also run without a problem when t1 < 1.0 and t2 > 1.0.

Currently I'm using t1=0.8 and t2=2.0. I printed value of probabilities and loss_value in _custom_gradient_bi_tempered_logistic_loss(activations) function, and I didn't find any nan in probabilities, but identified [-nan 6.30556154] in loss_value. This value caused nan propagation in loss.

Can you please run the same model using t1 = t2 = 1.0?

Hi @eamid
I switched to t1 = t2 = 1.0, the training seems OK, nan value doesn't appear

Thanks for checking! This is a bit strange since we expect bi-tempered loss to be more stable than cross entropy. If you can, please also try t1=0.8, t2=1.0 and t1=1.0, t2=2.0 to see which component is causing the instability. You can also try temperature pairs closer to 1.0, e.g. t1=0.99, t2=1.01. I am happy to take a look at your code if you can share it here.

Hi @eamid
I tried with following settings
t1=0.8, t2=1.0
t1=1.0, t2=2.0
t1=0.99, t2=1.01
All of them produced nan loss after a few steps training. I could introduce our scenario and some observations first. We would like to utilize bi-tempered loss to boost our recommendation model, as for training data, about 5% of them is positive samples (clicked), rest is negative. Our model's output is simply a logit, so I use bi_tempered_binary_logistic_loss for experiment. The code is the same as your open-sourced version.
`def bi_tempered_binary_logistic_loss(activations,
labels,
t1,
t2,
label_smoothing=0.0,
num_iters=5):
"""Bi-Tempered binary logistic loss.
Args:
activations: A tensor containing activations for class 1.
labels: A tensor with shape and dtype as activations.
t1: Temperature 1 (< 1.0 for boundedness).
t2: Temperature 2 (> 1.0 for tail heaviness, < 1.0 for finite support).
label_smoothing: Label smoothing
num_iters: Number of iterations to run the method.
Returns:
A loss tensor.
"""
with tf.name_scope('binary_bitempered_logistic'):
t1 = tf.convert_to_tensor(t1)
t2 = tf.convert_to_tensor(t2)
out_shape = tf.shape(labels)
labels_2d = tf.reshape(labels, [-1, 1])
activations_2d = tf.reshape(activations, [-1, 1])
internal_labels = tf.concat([1.0 - labels_2d, labels_2d], 1)
internal_logits = tf.concat([tf.zeros_like(activations_2d), activations_2d],
1)
losses = bi_tempered_logistic_loss(internal_logits, internal_labels, t1, t2,
label_smoothing, num_iters)
return tf.reshape(losses, out_shape)
def bi_tempered_logistic_loss(activations,
labels,
t1,
t2,
label_smoothing=0.0,
num_iters=5):
"""Bi-Tempered Logistic Loss with custom gradient.
Args:
activations: A multi-dimensional tensor with last dimension num_classes.
labels: A tensor with shape and dtype as activations.
t1: Temperature 1 (< 1.0 for boundedness).
t2: Temperature 2 (> 1.0 for tail heaviness, < 1.0 for finite support).
label_smoothing: Label smoothing parameter between [0, 1).
num_iters: Number of iterations to run the method.
Returns:
A loss tensor.
"""
with tf.name_scope('bitempered_logistic'):
t1 = tf.convert_to_tensor(t1)
t2 = tf.convert_to_tensor(t2)
if label_smoothing > 0.0:
num_classes = tf.cast(tf.shape(labels)[-1], tf.float32)
labels = (
1 - num_classes /
(num_classes - 1) * label_smoothing) * labels + label_smoothing / (
num_classes - 1)
@tf.custom_gradient
def _custom_gradient_bi_tempered_logistic_loss(activations):
  """Bi-Tempered Logistic Loss with custom gradient.
  Args:
    activations: A multi-dimensional tensor with last dim `num_classes`.
  Returns:
    A loss tensor, grad.
  """
  with tf.name_scope('gradient_bitempered_logistic'):
    probabilities = tempered_softmax(activations, t2, num_iters)

    loss_values = tf.multiply(
        labels,
        log_t(labels + 1e-10, t1) -
        log_t(probabilities, t1)) - 1.0 / (2.0 - t1) * (
            tf.pow(labels, 2.0 - t1) - tf.pow(probabilities, 2.0 - t1))

    def grad(d_loss):
      """Explicit gradient calculation.
      Args:
        d_loss: Infinitesimal change in the loss value.
      Returns:
        Loss gradient.
      """
      delta_probs = probabilities - labels
      forget_factor = tf.pow(probabilities, t2 - t1)
      delta_probs_times_forget_factor = tf.multiply(delta_probs,
                                                    forget_factor)
      delta_forget_sum = tf.reduce_sum(
          delta_probs_times_forget_factor, -1, True)
      escorts = tf.pow(probabilities, t2)
      escorts = escorts / tf.reduce_sum(escorts, -1, True)
      derivative = delta_probs_times_forget_factor - tf.multiply(
          escorts, delta_forget_sum)
      return tf.multiply(d_loss, derivative)

    return loss_values, grad

def reduced_loss(activations):
  return tf.reduce_sum(
      _custom_gradient_bi_tempered_logistic_loss(activations), -1)

loss_values = tf.cond(
    tf.math.logical_and(tf.equal(t1, 1.0), tf.equal(t2, 1.0)),
    functools.partial(
        tf.nn.softmax_cross_entropy_with_logits,
        labels=labels,
        logits=activations), functools.partial(reduced_loss, activations))
return loss_values`

I printed the probabilities fed into the loss_values calculation and identified which probabilities value caused nan. It seems [0.996272922 0.0037270959] -> [-nan 6.30556154]

One more thing to note, we used tf.losses.sigmoid_cross_entropy as loss function before. And t1=1.0, t2=1.0 works fine in our case.

Thanks for the info. I tried the loss with t1=0.8, t2=2.0 and a sigmoid probability of 0.996272922. At least in this setting, I am not getting a NaN. Can you please also share the logit values and the labels that are causing a NaN?

Hi @eamid
After careful debugging, I think the issue might due to our side. I print internal_logits and internal_labels as you suggested, I share the value caused NaN here
internal_logits = [0 -2.14406967]
internal_labels = [-1 2]
probabilities = [0.895113289 0.104886681]
loss_values = [-nan 3.25809574]
The internal_labels value seems wired. I will look into the training data further and update this issue if I found something.

Your internal_labels = [-1 2] seem wrong. The labels should be in between 0 and 1 (i.e. correspond to probabilities).


BUG: Fix bug with plot_projs_topomap

plot_projs_topomap currently fails when vlim='joint' in one way when using meg="combined" and n_mag = n_grad = 2 in projector computation:
mne/viz/tests/test_topomap.py:168: in test_plot_projs_topomap_joint
    fig = plot_projs_topomap(projs, info=raw.info, vlim=vlim, **fast_test)
mne/viz/topomap.py:406: in plot_projs_topomap
    fig = _plot_projs_topomap(
mne/viz/topomap.py:470: in _plot_projs_topomap
    assert len(these_ch_types) == 1
E   AssertionError

and (arguably) with the default vlim=(None, None) in another, only plotting one channel type:
mne/viz/tests/test_topomap.py:169: in test_plot_projs_topomap_joint
    assert len(fig.axes) == 4  # 2 mag, 2 grad
E   AssertionError: assert 2 == 4

I'll work on changing the first failure to at least produce 2 axes using the "mag" channel type. But I think in principle both of these should maybe produce 4 plots (second "failure"). That might be a more invasive/breaking change, though, we'll see!

LMK when this is ready for a review @larsoner

Okay I think this one is ready to go. TL;DR is that the trick was to split the projs into their component channel types before plotting, which I think makes sense anyway. A joint mag and grad projector (i.e., computed with meg="combined", which can be useful with Maxwell filtered data is the use case here) will have different magnitudes in the projection vector... so vlim="joint" should still be done for mag and grad separately.


CEF 104 failed with Linux

@raphipod I reverted CEF version to 103 it seems that on my Debian I have a failure. I have to investigate.

@raphipod I have also added a new demo + used Godot-3.5, is this working for you ?

Well, what a coincidence. I am on Fedora right now, I'm setting it up right now. Afterwards I'll test it!

@raphipod I emailed you. The issue is CefInitialize failed I guess it's because the build/gdcefSubProcess is broken: it is supposed to run as a standalone application, but it's frozen.

I've successfully compiled gdcef from your master branch with CEF 103 (with Fedora 36), I have yet to test it with Godot 3.5

Hmm. When I try to run CEF.tscn in /examples/01/, it spits out the following:
Invalid call. Nonexistent function 'create_browser' in Node
It errors out in the CEF node, the gdnlib script is attached, but it shows up as empty in the editor:

@raphipod I emailed you. The issue is CefInitialize failed I guess it's because the build/gdcefSubProcess is broken: it is supposed to run as a standalone application, but it's frozen.

Ok. I'll continue working on this tomorrow. I'll write something if I got news.

@raphipod the main scene is gui_in_3d

So, CEF 104 successfully compiled on my Fedora machine. A wild guess: They've probably changed something in the backend of CEF that a development package of Debian can not provide due to a newer version of it being needed.

@raphipod closed. Tried with the newer CEF 104 has fixed issues or more probable the issue was on my side with LD_LIBRARY_PATH referring to an older CEF version


Add results for Radeon RX 570; Print half-precision with a capital letter

Please merge. Thanks.

Please merge. Thanks.

Thanks


Any other way other than ssh to get data from storage box

SCP='sshpass -p DMg5bmLPY7npHL2Q scp -o StrictHostKeyChecking=no<EMAIL_ADDRESS>This command in init.sh file can it be replace by some other working command as port 22 is not allowed to make a ssh connection to outside world from my internal network I tried to replace with the previous version init.sh file but it didn't work so any help would be appreciated

You can download the files separately, then specify the path to them with the IMPORT_* settings https://github.com/mediagis/nominatim-docker/tree/master/4.3#configuration For example IMPORT_WIKIPEDIA=/home/someuser/pre-downloaded/files/

But when I try to run the docker it tries to make a connection to the ssh so I need to modify the docker file? Or just add it in the docker environment variable?

You can download the files separately, then specify the path to them with the IMPORT_* settings https://github.com/mediagis/nominatim-docker/tree/master/4.3#configuration For example IMPORT_WIKIPEDIA=/home/someuser/pre-downloaded/files/

I'm getting this error when trying to do it
2023-12-17 12:09:50: Initialising replication updates
2023-12-17 12:09:50: Failed to load URL: https://www.openstreetmap.org/api/0.6/node/11420726320/1
Traceback (most recent call last):
File "/usr/lib/python3.10/urllib/request.py", line 1348, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File "/usr/lib/python3.10/http/client.py", line 1283, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1329, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1278, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1038, in _send_output
self.send(msg)
File "/usr/lib/python3.10/http/client.py", line 976, in send
self.connect()
File "/usr/lib/python3.10/http/client.py", line 1455, in connect
self.sock = self._context.wrap_socket(self.sock,
File "/usr/lib/python3.10/ssl.py", line 513, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1100, in _create
self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1371, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1007)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/nominatim", line 14, in
exit(cli.nominatim(module_dir='/usr/local/lib/nominatim/module',
File "/usr/local/lib/nominatim/lib-python/nominatim/cli.py", line 264, in nominatim
return parser.run(**kwargs)
File "/usr/local/lib/nominatim/lib-python/nominatim/cli.py", line 126, in run
return args.command.run(args)
File "/usr/local/lib/nominatim/lib-python/nominatim/clicmd/replication.py", line 191, in run
return self._init_replication(args)
File "/usr/local/lib/nominatim/lib-python/nominatim/clicmd/replication.py", line 79, in _init_replication
replication.init_replication(conn, base_url=args.config.REPLICATION_URL,
File "/usr/local/lib/nominatim/lib-python/nominatim/tools/replication.py", line 41, in init_replication
date = status.compute_database_date(conn)
File "/usr/local/lib/nominatim/lib-python/nominatim/db/status.py", line 50, in compute_database_date
data = get_url(node_url)
File "/usr/local/lib/nominatim/lib-python/nominatim/tools/exec_utils.py", line 171, in get_url
with urlrequest.urlopen(request) as response: # type: IO[bytes]
File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.10/urllib/request.py", line 519, in open
response = self._open(req, data)

I guess port 443 is also blocked? In that case replication (data updates) won't work after the initial import. You can disable that by setting UPDATE_MODE=none. If you never run updates in the future then can also set FREEZE=true.

It's not possible I'm afraid. We used to download via http but some people ran endless loops and used up all of nominatim's bandwidths so we had to migrate.

Even after opening the port I'm still getting the dh key too small issue

Which port did you open? Which commands did you run to open it? How did you verify it's open?

To open the port I used the command
Sudo ufw allow 443
And to check if the port is open or not I did run the command
Sudo ufw status verbose

To test if the port is open run curl "https://www.openstreetmap.org/api/0.6/node/11420726320/" inside the Docker container. If that prints an error then talk to your system administrators to open the port.

To test if the port is open run curl "https://www.openstreetmap.org/api/0.6/node/11420726320/" inside the Docker container. If that prints an error then talk to your system administrators to open the port.

Thank you so much for you help really appreciate it


Added MariaDB keywords GENERATED and PERIOD

Both keywords are used for System Versioned tables.
GENERATED marks a column as auto generated.
PERIOD is ignored fro the script.

Thanks for adding the keywords. Could you add a minimal example to tests/scripts/ddl2cpp_sample_good.sql (e.g. as a new table)?
Double-check the results of ctest -R sqlpp11.scripts.ddl2cpp.good_succeeds --verbose in the generated fail.h.

Ok, already done. The test passes with warnings for using TIMESTAMP columns.
36: Warning: date and time values are assumed to be without timezone.
36: Warning: If you are using types WITH timezones, your code has to deal with that.
Other than that, it seems ok.

Just as a note, when you define a table WITH SYSTEM VERSIONING, with implicit column definitions for ROW START and ROW END, the scripts generate a correct table definition, but without the columns for ROW START and ROW END, so there is no way for sqlpp to access them. If you want to access those columns you have to define them explicitly.

Nice work, thanks.
As for the WITH SYSTEM VERSIONING: I´d be happy to accept a PR for supporting that (would require a slightly more involved test to make sure those two columns are actually created).


Reduce log spam from Avro decoders.

These objects get constructed semi-frequently (any time a parser is
deserialized) and so info logs are spammy. They'll still appear in
task logs at least once, since they're part of the task definition and
will get logged due to that.

👍


[pipeline] optimize for generated_samples

multiapi package may don't generate samples every time so we can't delete the folder

/check-enforcer override


Util.h extensions

Add UTIL_OR and UTIL_AND, along with tests for MACRO_MAP_CAT.

I was not aware of UTIL_BOOL and i missed that in few places.

Got excited too early. UTIL_BOOL returns true when define does not exist so it does not solve the problem I wanted to solve.


[Crash] The latest version crashes the game with the mod AdventureZ

Describe the bug
The latest version crashes the game with the mod AdventureZ
p.s. 1.5.71 work normaly
Crash report
vanillatweaks_adventureZ.txt
Versions:(check log if you don't know)

Fabric Loader Version: 0.14.24
MC Version: 1.20.1
Mod Version: 1.5.72
Fabric API Version (if present) : 0.91.0

Use VanillaTweaks-fabric-1.20.1-1.5.71. Version that you are using was mistakenly marked as supporting 1.20.1


feat(core): introduce debug mode

This adds a debug mode to Autocomplete Core (and therefore Autocomplete JavaScript) so that it's easier to inspect the dropdown which doesn't close when the blur event occurs.
This is a feature that was implemented in Autocomplete v0 and that several developers requested in this version as well.

ahhhh, I'm happy to see this feature back!


prepare for v0.7.0

I decided on 0.7.0 for this version because we are removing support for Python 2.
@horstle, do you think we should include anything else in this version? I'd appreciate your eyes on this seeing as you've done the heavy lifting as usual. :-)

Apart from removing the import that pylint is moaning about, I wouldn't add anything else.
Actually I still haven't tested #558 as much as I wanted to before a release (currently don't have the time for it), but I'm rather confident it's fine.

@horstle Thanks! I pushed the release now.


Lovelace - Configure UI

Home Assistant release with the issue:
0.84.0

Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Docker

Component/platform:
Configure UI

Description of problem:
Editing a card no longer works if you click outside of the popup type window. Click edit on a card after selecting Configure UI. Click outside the box and it will close. Clicking edit again will not open the editor anymore. Reboot required.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

/move to home-assistant-polymer


Add note on requirement for x86_64 instruction set architecture.

Based on my experience of not being able to get weasyprint to work as a layer, because I was using arm64 instead of x86_64, have added a clarifying note where I think people will see it.

Can you change this note to reference releases? I don't know if arm build doesn't work at all.

Thanks!


As a player in-game I want to see small & big blind values automatically be deduced from the correct players to setup the betting

Story: As a player in-game I want the small and big blind to be forced to bet the small and big blind at the beginning of each game-round so the betting can begin.
Acceptance criteria:

[x] #53
[x] #54

Priority: critical
Estimate: 4-8 h

Closed in commit: 236f74a333977cc6dc0c5824c7535abde7b33244


update to golang 1.15 and alpine 3.12

Golang 1.13 used for build is now EOL, updated to latest 1.15. Updated main image to alpine 3.12 to match alpine used in build.

 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.

Thanks for this. Can you press the CLA button above?


Add support for AWS Cape Town region (af-south-1)

Hi there! Had a look at the existing PRs and Issues and found nothing related to this, so apologies if it's a duplicate.
I am currently getting the following error:
Exception: invocation of aws:ec2/getVpc:getVpc returned an error: Invalid AWS Region: af-south-1

As per this pull request, Terraform has added support for the recently launched af-south-1 region. Are there plans by the Pulumi team to add support for this region soon as well?
I'm really looking forward to migrating my infra closer to home. :smile:
Edit:
I am running Pulumi 2.1.0

Hi @stack72
This was released in Pulumi-aws 2.2.0 that was released on April 29th in #947
Thanks
Paul

Hi @stack72

🤣

Hi @stack72

🤣

Doh!! I’ve even started replying like a bot :)
I meant @CSergienko of course!!

@stack72 Ah, I think I see why it wasn't working for me. I'm using the Python package, and it doesn't appear to have been added to that part of the SDK as yet.

@CSergienko yeah we don’t have overlays in Python as of yet - it’s on the plan though!


@W-15638748 | Changes to support EnblProgramTaskSubCategory and LearningItemType

We have created the new setup entities EnblProgramTaskSubCategory and LearningItemType and exposed them to mdApi.
What does this PR do?
Supports EnblProgramTaskSubCategory and LearningItemType entities in retrieve/deploy
What issues does this PR fix or reference?
The specified metadata type is unsupported: [EnblProgramTaskSubCategory]
The specified metadata type is unsupported: [LearningItemType]
@W-15638748@
Functionality Before
When we tried to retrieve this entity using sfdx commands getting the following error The specified metadata type is unsupported: [EnblProgramTaskSubCategory]. Same for the LearningItemType.
<insert gif and/or summary>
Functionality After
<insert gif and/or summary>

I have signed CLA even though that wasn't required.


Segment a human head

Hello, thank you very much for this great project!
How could I segment a person's head (face + hair + ears)? Well I have noticed that when segmenting the person's head it always includes part of the neck.
Thanks in advance!

i comfuse it too,is there any solution??


Electrum server host - connections

Hello
I wanted to connect my computer with my Electrum Wallet to my computer with my Bitcoin Core and Electrum Personal Server.
I tried to specify my IP address, but could only choose between : localhost and <IP_ADDRESS>
Being able to specify a LAN IP address would be a usefull feature imho.

I'm not exactly sure what you mean. Are you talking about editing config.cfg to change host in [electrum-server] ? I believe you could set that to be the IP address of your Electrum Wallet computer and then Electrum Personal Server would only accept connections from that.
I haven't tested that though, so if you've already done that and it doesn't work then IDK. That host and port just get passed to socket.bind()

Yes, I edited the config.cfg and changed the host in [electrum-server]
When set to <IP_ADDRESS> it works, but when I set the host to the IP address from my Electrum Wallet computer I get the following error : "OSError: [WinError 10049] The requested address is not valid in its context"
The IP address is correct, the Electrum Personal Server log confirms this.
So my guess is that there is some sort of hard coded limit to <IP_ADDRESS> and <IP_ADDRESS> ...
I have it covered by my hardware firewall, but still ... this is a needed feature imho.
I will look into it further and see if I can make something of it.

Looks like it is expected behavior in Python. It needs to bind to a local address. For now I have changed my windows firewall rule so that it only allows Python connections from the specified IP address.

Looks like it is expected behavior in Python.

Is that right? Sucks if true.
I just saw on the raspberry pi guide that he also does it by binding to <IP_ADDRESS> and then using the firewall to control access.
I could add a whitelisting address feature where after server_socket.accept() returns with a socket, that socket's IP address is checked and if it isn't in the whitelist then close() is called.

Whitelisting feature added https://github.com/chris-belcher/electrum-personal-server/commit/5a255e406a578622f074259ece66e9d047d8ac98

Agreed, use on your private and secured LAN.
The feature looks good. Going to test it in the weekend.

Hey, it took a bit longer to test it, but it is working fine, so thanks for the work.


Release 0.8.0.RC1

Resolved via https://github.com/r2dbc/r2dbc-proxy/commit/b538795ca1511a0ad17238cfe779494c3666e756.


ARROW-188: Add numpy as install requirement

Successfully tested with NumPy 1.9 which should be a recent but still old version that we can support for now.

+1, thank you


Need csvs/ directory with base job csv file

Webpage requires csv file in csvs directory after uploading the resume for initial job matching scores (before clicking the update jobs button)
We probably need it in github (or somewhere that downloads into the csvs directory upon setting up the environment) so we can guarantee that the user has at least some jobs to match with initially (also in case the scraping breaks bc no guarantees there lmao)

added a sample file here #97 but need to generate a file with all 3 job titles (elaine can't scrape anymore)

Need to clean up sample files/rename them

csv done here #162
need to make sample resume generic


Pull out coinview validation rule

Temporary PR to get some feedback on the restructuring.
This is NOT complete so please avoid feedback on documentation and code style at this stage. I am interested in the structure, and perhaps the rule name / rule breakdown possibilites etc.
Something is also not quite right with the Proof of Stake code path as the Proof of Stake integration tests fail with this current code - so there must be a mistake in the logic - most likely related to the original confusing conditional !isCoinbase && !IsPos  ||  IsPos && !IsStake

Actually, the staking tests are failing for me on master too

We prefer creating issues for such discussions, instead of PRs. This is really too early for PR.
As for the implementation, I can see 2 problems, 1st 1 is that I would not expect for 2 separate it will still exist here PosTransactionRelativeLocktimeAndSignatureOperationCostRule  and PowTransactionRelativeLocktimeAndSignatureOperationCostRule , at least not as distinguished as it is on proof of work versus proof of stake level. I would probably be looking for transaction finality rule and separated signature operation costs rule.
The 2nd problem for me is that regardless of how those rules are called, they include much more – they actually fully connect the inputs, which means they do much more than you would expect from them. Therefore for other things besides transaction finality and signature operation costs, I would expect more separated rules.


parser for hocr

BDRC will get a lot of OCR from Google in hocr format. The files will be available on s3 just like the json files we currently have. Creating opf files from these will require parsing hocr. There are tools available for this in Python, such as https://github.com/jlieth/hocr-parser

There is now a full working example of hocr on s3 so we can start to develop the hocr parser. Here's a little bit of information:

the base directory is s3://ocr.bdrc.io/Works/83/W2PD17457/
instead of having json files, the ocr output for each image is a .txt file (that I think we should ignore) plus an .html file in hocr format
there is some detailed information returned by Google Books for each volume in the xml files in s3://ocr.bdrc.io/Works/83/W2PD17457/google_books/batch_2022/info/ but it's unclear if anything necessary is there
the mapping between the file names of the html and the image file name on BDRC is kept in json files named gb-bdrc.map.json in each volume folder in info/, it should be relatively easy to navigate

Note that the hocr import should have the same features as the Google Vision import, namely #162 and #164

(note that this would be a good opportunity to do that last two points of https://github.com/OpenPecha/OCR-Helper-Scripts/issues/6#issuecomment-1165357318 which also impact the Google Vision import

the confidence index given in hocr is an integer between 1 and 100, it should be converted to a float between 0 and 1 in order to be coherent with the Google Vision formatter

See https://github.com/buda-base/archive-ops/issues/694#issuecomment-1234796952 for a small change in the way files are structured. It should have a little impact on the import but not too much

a new development: the hocr must have two modes, one for google_books (one file per page, as in the example) and one for ia (one file per volume), they use different conventions for the image numbering also. See https://github.com/buda-base/archive-ops/issues/754 for IA and https://archive.org/download/bdrc-W22084/bdrc-W22084-100_hocr.html for an example

note also that the IA files have xml:lang="bod" so there must be a mapping happening to create the Language layer, mapping bod to bo. The following library does exactly that: https://github.com/rspeer/langcodes

for an example of abstraction layer, see the GoogleVisionBDRCFileProvider class introduced in https://github.com/OpenPecha/Toolkit/pull/188 , this will allow some good flexibility for the different ways the files can be accessed / organized


Example doesn't work

The example:
<!doctype html>

  <title>Hello requirex</title>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

Doesn't seem to work.
In Firefox I get:
Error: Parse error
    translating http://localhost:8080/#1.js
    importing http://localhost:8080#1.js from http://localhost:8080/ requirex:1:13289

Huh, wonder how come I never tested that. Several bugs were unearthed!

Should be finally fixed in v0.1.5.


CosmosClient.WithEncryption() does not accept AzureKeyVaultStoreProvider

In the example (https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-always-encrypted?tabs=dotnet), the CosmosClient modifier .WithEncryption() should take a reference of AzureKeyVaultKeyStoreProvider, however it is looking for EncryptionKeyWrapProvider.
I also tried 3.23.0 (instead of preview) which then renders ClientEncryptionIncludedPath as protected.
The documentation also shows usage of:
DataEncryptionKeyAlgorithm.AEAD_AES_256_CBC_HMAC_SHA256
Which seems to actually be:
DataEncryptionKeyAlgorithm.AeadAes256CbcHmacSha256
Environment summary
SDK Version: net6
Azure.Identity" Version="1.5.0"
Microsoft.Azure.Cosmos" Version="3.23.0-preview"
Microsoft.Azure.Cosmos.Encryption" Version="1.0.0-previewV19"
Microsoft.Data.Encryption.AzureKeyVaultProvider" Version="0.2.0-pre"

Under closer inspection, it looks like the example uses:
AzureKeyVaultKeyStoreProvider
When it should be using:
AzureKeyVaultKeyWrapProvider

@kr-santosh  and/or @abhijitpai can you take a look?


maintainers: remove cfriedt as ti collaborator

Just in an effort to reduce notifications in areas that I'm not super actively involved in. I was getting a lot of false positive notifications for sensors.
Feel free to ping me for individual reviews on simplelink parts or TI HAL or radio drivers.

Merging as trivial.


feat: support lazy initialization of the SDK

Description

support lazy initialization of the SDK

General Checklist

[x] Added new tests to cover change, if needed
[x] Build succeeds using Swift Package Manager
[x] All unit tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[x] PR title conforms to conventional commit style
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.69%. Comparing base (a850795) to head (44b0476).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #58      +/-   ##
==========================================
+ Coverage   95.66%   95.69%   +0.02%
==========================================
  Files          35       35
  Lines        1986     1999      +13
==========================================
+ Hits         1900     1913      +13
  Misses         86       86

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Per Account mailing

Hi guys,
since login is only working with cookies right now, I want to implement some file drop for my users to update their cookies if needed.
I don't know how to realize this yet, however it will be necessary that users will get notified.
For this would suggest sending a mail either to users Epic mail address or to add some new config attribute to specify a notification mail address per account when login fails.
This way, users would know it's time to update their cookie again.
I don't know how mailing is handle right now and don't use TypeScript regularly, but with some help I might be able to suppose a merge request myself.

I just saw #101 this might be an incremental addition but account.email is available within that function already.
Might be worth considering a boolean for deciding whether sending to account.email or this.emailConfig.emailRecipientAddress.

Added in v4: https://github.com/claabs/epicgames-freegames-node/releases/tag/v4.0.0


[CONTROLLER-DB]add npb new column

One or more of:

Server

NPB
Checklist

[ ] Added unit test.

Backport to branches

 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.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Deployment Issue

Hello All,
Trying to Deploy Company Communicator but getting this error.

{
"status": "Failed",
"error": {
"code": "RoleAssignmentUpdateNotPermitted",
"message": "Tenant ID, application ID, principal ID, and scope are not allowed to be updated."
}
}

Hi @ayotwice ,
This issue normally arises when attempting multiple deployments with the same GUID. As per suggestion, it is recommended to have new GUID’s generated for each deployment if it is performed in the same subscription.

@v-royavinash How do I generate a new one? Thank you kindly.

@ayotwice you can use any online tool to generate new GUID's

@ayotwice , Could you please confirm the closure of this issue?

Not yet, I generated with https://www.guidgenerator.com/online-guid-generator.aspx but still getting error.

@ayotwice , Please provide more details of the error you are getting? Is it the same error you were getting previously?

I am having the same error, I've not used Company Communicator before - I did have a previous failed install so I've removed the resource groups, do I need to remove anything else?

@Jonroberts84 even if you delete the resource group, the value might be cached, hence we recommend using new GUID's for the values highlighted in the above screenshot so that deployment will not fail.

@ayotwice , We are closing this request as we have provided the expected resolution steps. If you still face any further issue please request you to raise a new request.


naming cleanups

changes some of the names to improve consistency with their request counterparts

test failure is unrelated to these changes, just tested


converting data between physical testing machines

When will U3M be able to convert physical properties from CLO to Browswear and visa versa?

Public physics are going to be available with U3M 1.1 (see newsletter this week). This will start the discussion towards data conversion, depending on the vendors

This is awesome ☺
From: vizoomartin<EMAIL_ADDRESS>Sent: Monday, May 4, 2020 9:37 AM
To: vizoogmbh/u3m<EMAIL_ADDRESS>Cc: Michelle.Greenhouse<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: [EXTERNAL] Re: [vizoogmbh/u3m] converting data between physical testing machines (#12)
Public physics are going to be available with U3M 1.1 (see newsletter this week). This will start the discussion towards data conversion, depending on the vendors
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/vizoogmbh/u3m/issues/12#issuecomment-623502826, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALDAGUVEH7CQ4OG4SEP6TB3RP3HJZANCNFSM4GO62HYA.


Upgrade rubocop to 0.36

Also fix offenses introduced by the upgrade.

:+1: @jawshooah could you look into the 'codeclimate-test-reporter' error in the test?

That error has been around ever since RuboCop switched from Coveralls to CodeClimate, nothing to do with the changes in this PR.

Great! In that case ping @nevir :smile:

My PR (#63) should fix the Travis issues with CodeClimate, but it requires both PR's by @jawshooah to be merged first.

What is the status of this, when can we merge?

/cc @geniou @bquorning

Any news on this one?

Waiting on @nevir, looks like.

+1

Now there's Rubocop 0.37 https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md#0370-04022016

Yup, I will merge this today, and go through other tickets. Then update to 0.37.0.

@nijikon Will you be pushing a new version to rubygems?

@DexterTheDragon yes, working on it right now


Bug: Toolbar extract text not shown correctly with a small window width

Description
The extract option is labled "E" when you resize your window down and the menu bar is reduced in size causing the "..." button to appear

Steps To Reproduce

Resize window down that the menu bar has a "..." option
Select a zip folder
Click the "..."

Notice extract is labled "E"
Requirements
Fix Extract label on context menu
Files Version
<IP_ADDRESS>
Windows Version
1000.22700.1020.0
Log File
debug.log

Thanks for the report, I've added this to the project board.

Isnt this the same as https://github.com/files-community/Files/issues/10291?

Yes, we can continue tracking there.


Implement command to validate Glottocodes

Glottolog data should be made available via a dataset locator pointing to its CLDF datasets. Now having to specify e.g. the Zenodo DOI for Glottolog CLDF v5.0 rather than just "glottolog-v5.0" may be a bit tedious. But possibly we can think of a "discovery" library (i.e. a package implementing a pycldf_dataset_resolver entry point) which can resolve such short-hand notations, maybe via looking up the clld meta catalog.

We already have cldf check.