AttributeError: type object 'Environment' has no attribute 'Development'

Hi! Just stumbled upon your script, which seems very useful to me as an user of Moneydance in EU, which doesn't have support for European banks yet. So I need to use qfx!
I created an account in Plaid, obtained the secrets, then run the scripts and I got this error:
Please provide your client API Secret:
Traceback (most recent call last):
  File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 795, in <module>
    main()
  File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 136, in main
    link_name = link_account()
  File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 277, in link_account
    response = get_client().link_token_create(request)
  File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 99, in get_client
    host=plaid.Environment.Development, # Available environments are 'Production', 'Development', and 'Sandbox'
AttributeError: type object 'Environment' has no attribute 'Development'

Did I get anything wrong? Or API has changed in the meantime?
Thanks!

I had to follow my own instructions to get this set up again, it has been a while 😊. I gave up on Quicken and moved on to Monarch Money.
Found an explanation Plaid Production APIs in June 2024 : r/fintech (reddit.com)https://www.reddit.com/r/fintech/comments/1c8xxet/plaid_production_apis_in_june_2024/ that the Development environment has been deprecated. Sounds like today you need a production API key.
I’ll play with this for a bit and see if I can easily get it working again.
Glad to hear someone is interested in this project!
Thanks,
Phil

From: marmata @.>
Sent: Saturday, September 14, 2024 12:29:10 PM
To: philliphall/plaid2qfx @.>
Cc: Subscribed @.***>
Subject: [philliphall/plaid2qfx] AttributeError: type object 'Environment' has no attribute 'Development' (Issue #11)
Hi! Just stumbled upon your script, which seems very useful to me as an user of Moneydance in EU, which doesn't have support for European banks yet. So I need to use qfx!
I created an account in Plaid, obtained the secrets, then run the scripts and I got this error:
Please provide your client API Secret:
Traceback (most recent call last):
File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 795, in
main()
File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 136, in main
link_name = link_account()
File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 277, in link_account
response = get_client().link_token_create(request)
File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 99, in get_client
host=plaid.Environment.Development, # Available environments are 'Production', 'Development', and 'Sandbox'
AttributeError: type object 'Environment' has no attribute 'Development'
Did I get anything wrong? Or API has changed in the meantime?
Thanks!
—
Reply to this email directly, view it on GitHubhttps://github.com/philliphall/plaid2qfx/issues/11, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7BXRCW6BWD6YZBPFILAKB3ZWRP5NAVCNFSM6AAAAABOG7LNJKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUZDMNJQGEZDGMQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Of course I'm interested! Great project if you ask me!
Simply ch anging that line to this let me continue:
host=plaid.Environment.Production, # Available environments are 'Production', 'Development', and 'Sandbox'
so the html is not created correctly. However when I try to link, I only get a list of US institutions (I'm in Italy). By further research it looks like only US and Canada are enabled by default, and I need to file a support ticket to request access to EU institutions. Perhaps it will work once I do that, I'll let you know!

Updated the script on GitHub. You can re-sync or just change…
“host=plaid.Environment.Development,”
To…
“host=plaid.Environment.Production,”
I started requesting the Oauth permissions, but the questions get pretty invasive for personal use, so I tested with a non-Oauth institution (which is free for what they are calling “limited production” access). Seems to work okay, but let me know if you have any issues.
Make sure you are using your production API Secret when the script asks for it.
Let me know how it goes!
Phil

From: Phillip Hall @.>
Sent: Saturday, September 14, 2024 12:58:27 PM
To: philliphall/plaid2qfx @.>; philliphall/plaid2qfx @.>
Cc: Subscribed @.>
Subject: RE: [philliphall/plaid2qfx] AttributeError: type object 'Environment' has no attribute 'Development' (Issue #11)
I had to follow my own instructions to get this set up again, it has been a while ??. I gave up on Quicken and moved on to Monarch Money.
Found an explanation Plaid Production APIs in June 2024 : r/fintech (reddit.com)https://www.reddit.com/r/fintech/comments/1c8xxet/plaid_production_apis_in_june_2024/ that the Development environment has been deprecated. Sounds like today you need a production API key.
I’ll play with this for a bit and see if I can easily get it working again.
Glad to hear someone is interested in this project!
Thanks,
Phil

From: marmata @.>
Sent: Saturday, September 14, 2024 12:29:10 PM
To: philliphall/plaid2qfx @.>
Cc: Subscribed @.***>
Subject: [philliphall/plaid2qfx] AttributeError: type object 'Environment' has no attribute 'Development' (Issue #11)
Hi! Just stumbled upon your script, which seems very useful to me as an user of Moneydance in EU, which doesn't have support for European banks yet. So I need to use qfx!
I created an account in Plaid, obtained the secrets, then run the scripts and I got this error:
Please provide your client API Secret:
Traceback (most recent call last):
File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 795, in
main()
File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 136, in main
link_name = link_account()
File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 277, in link_account
response = get_client().link_token_create(request)
File "c:\Users\Marco\Documents\src\plaid2qfx\plaid2qfx.py", line 99, in get_client
host=plaid.Environment.Development, # Available environments are 'Production', 'Development', and 'Sandbox'
AttributeError: type object 'Environment' has no attribute 'Development'
Did I get anything wrong? Or API has changed in the meantime?
Thanks!
—
Reply to this email directly, view it on GitHubhttps://github.com/philliphall/plaid2qfx/issues/11, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7BXRCW6BWD6YZBPFILAKB3ZWRP5NAVCNFSM6AAAAABOG7LNJKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUZDMNJQGEZDGMQ.
 Let me know how Italy access goes.
I’ll be moving my family to Italy (at least for the 3 months Italy will let me stay at a time) as soon as my house sells 😊.
Thanks,
Phil

From: marmata @.>
Sent: Saturday, September 14, 2024 1:33:33 PM
To: philliphall/plaid2qfx @.>
Cc: philliphall @.>; Comment @.>
Subject: Re: [philliphall/plaid2qfx] AttributeError: type object 'Environment' has no attribute 'Development' (Issue #11)
Of course I'm interested! Great project if you ask me!
Simply ch anging that line to this let me continue:
host=plaid.Environment.Production, # Available environments are 'Production', 'Development', and 'Sandbox'
so the html is not created correctly. However when I try to link, I only get a list of US institutions (I'm in Italy). By further research it looks like only US and Canada are enabled by default, and I need to file a support ticket to request access to EU institutions. Perhaps it will work once I do that, I'll let you know!
—
Reply to this email directly, view it on GitHubhttps://github.com/philliphall/plaid2qfx/issues/11#issuecomment-2351075838, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7BXRCUWMXLIPLQEVPMQCWTZWRXO3AVCNFSM6AAAAABOG7LNJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJRGA3TKOBTHA.
You are receiving this because you commented.Message ID: @.***>


Fix/sheet

Codecov Report

Merging #43 (f137feb) into main (34b938a) will increase coverage by 0.04%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##             main      #43      +/-   ##
==========================================
+ Coverage   89.25%   89.30%   +0.04%
==========================================
  Files          54       54
  Lines        1992     1991       -1
==========================================
  Hits         1778     1778
+ Misses        143      142       -1
  Partials       71       71

Impacted Files
Coverage Δ

internal/excels/excel.go
91.74% <40.00%> (+2.65%)
:arrow_up:

internal/layouts/jsonPack.go
80.48% <0.00%> (-4.88%)
:arrow_down:

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


Draft - public target for NT

Part 1 of future changes to NetworkTransform features
1: Target now public on NT, to merge the 2 components (NT and NTC) into one (done)
2: Boolean to auto assign this.transform as target, false to leave as null which will be used for something later (done)
3: Tooltip explanations (done)
4: Depreciation message on NTC (to do)

Its auto adding anything i submit to my fork 🙈


Add Matern priors and refactor priors a bit more

Codecov Report

Merging #214 (74dd784) into main (3ad4947) will decrease coverage by 0.05%.
The diff coverage is 97.88%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #214      +/-   ##
==========================================
- Coverage   95.62%   95.57%   -0.05%
==========================================
  Files          26       30       +4
  Lines        1074     1131      +57
==========================================
+ Hits         1027     1081      +54
- Misses         47       50       +3

Impacted Files
Coverage Δ

src/ProbNumDiffEq.jl
72.41% <ø> (ø)

src/caches.jl
95.52% <0.00%> (-2.94%)
:arrow_down:

src/priors/matern.jl
94.11% <94.11%> (ø)

src/perform_step.jl
97.80% <100.00%> (-0.30%)
:arrow_down:

src/priors/common.jl
100.00% <100.00%> (ø)

src/priors/ioup.jl
100.00% <100.00%> (ø)

src/priors/iwp.jl
100.00% <100.00%> (ø)

src/priors/ltisde.jl
100.00% <100.00%> (ø)

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


[kie-issues#653] Don't use System.out and logger debug mode in test output in traits

Fixes https://github.com/apache/incubator-kie-issues/issues/653

Changes logger debug mode in tests in the whole repository
Replaces or removes the use of System.out or System.err in drools-traits tests. When an occurence is replaced, it is replaced with logger.

@jstastny-cz this should fix the huge logs you reported from drools-traits in the CI logs.

I will review the PR check logs in the morning, but seems promising ;-) Thanks.


On the LB, would like to see host names of hosts that are part of LB.

Version: Build from Master (4/7/15)
Instead of only seeing the number of hosts in a LB on the summary of LB page. It'd be nice to show all the hosts and status of the host.

v0.17.0
Verified Fixed


Python interface for Dataset Aggregation

Implement dataset aggregation interface in Python and create unit tests for it

Codecov Report

Merging #256 (10be43f) into develop (5e1320c) will increase coverage by 0.04%.
The diff coverage is 94.54%.

@@             Coverage Diff             @@
##           develop     #256      +/-   ##
===========================================
+ Coverage    80.15%   80.19%   +0.04%
===========================================
  Files           54       55       +1
  Lines         3326     3439     +113
===========================================
+ Hits          2666     2758      +92
- Misses         660      681      +21

Impacted Files
Coverage Δ

src/python/module/smartredis/client.py
95.30% <94.54%> (-0.12%)
:arrow_down:

include/redisserver.h
0.00% <0.00%> (-33.34%)
:arrow_down:

include/pipelinereply.h
33.33% <0.00%> (-16.67%)
:arrow_down:

include/srexception.h
20.58% <0.00%> (-3.55%)
:arrow_down:

src/cpp/threadpool.cpp
74.46% <0.00%> (ø)

src/cpp/redisserver.cpp
94.66% <0.00%> (+0.46%)
:arrow_up:


Adding some feature in Audiobooks

Is your feature request related to a problem? Please describe.
adding a command-line argument to specify the PDF file to read.
Describe the solution you'd like
This can make the script more versatile and user-friendly.
This addition makes your script more flexible and user-friendly by allowing users to specify the PDF file they want to read as a command-line argument.
Describe alternatives you've considered
Additional context
I'm practicing for the hacktoberfest , so let me solve this issue

Hey @ayan-joshi ,
I liked your idea , go for it 🚀

Merged 👍


Major Changes

Added fromMessageId to fetch messages before latest 100.
Remove jar support and used github packages for Spring boot Starter Telegram Pkgs.

Will update documentation in root directory


How to offset the offset of a constraint?

If we want to offset the offset of a constraint right now, we need to bookkeeping the original value as there is no Constraint.getOffset().
Can we have Constraint.getOffset() or Constraint.addOffset() ?

@soapsign unfortunately this isn't going to be possible the way the API works the offset is stored in a way that results in destructiveness.
Do you have a specific use case you always find yourself having to implement this for?

Ok. I think I will work around this.
By the way, I would like to ask can we have a Constraint.updateMultipler()?

@soapsign, I remember we can only change the constant variable of NSLayoutConstraint rather than the multiplier. We must remove a constraint and add a new constraint to archive such things.

Thank you for your prompt reply!

@soapsign yea @wizzardchao is correct, the multiplier is not able to be modified after the constraint is created, you have to remove it, re-create it and re-add it. Or in SnapKit terms you need to do a snp_remakeConstraints

@robertjpayne snp_remakeConstraints is really handy! Thank you.


COMBO feature

I got a redox wireless from falbatech and I'm trying to flash my own firmware
I have several keyboards and share many features across them including COMBO keys. However if I enable COMBO with the redox_w firmware, the keyboard doesn't produce any keys. If I remove COMBO it works just fine
Any ideas on what could it be?

I found the issue, the combo were not defined, odd that nothing worked in that case but it is fine now


Fix matplotlib error in mnist example

It tries to set 'Agg' as the displaying backend of matplotlib if it's running on Linux environment to avoid RuntimeError: Invalid DISPLAY variable.

Why is it required only for linux?

Sorry that was my misunderstanding. It's also available on macOS. So just removed the part to check the platform.

LGTM


Respect default file namespace for docblocks

namespace ForumHouse\Common\Conversion\Converters;

interface IConverter {}

class Factory
{
    /**
     * @param string $name Converter name
     * @returns IConverter
     */
    public function create($name) {}
}

IConverter in Factory::create() is actually ForumHouse\Common\Conversion\Converters\IConverter.
But in _ide_helper.php it is \IConverter

So there is no way to fix this? I've noticed it for a while but get around it by just defining the type with a /** @var /Full/Path/To/Class $class */ tag.

@barryvdh any word on getting this fixed? showing me all kinds of warnings when trying to make commits...

Is this still an issue then?

@barryvdh this can be closed as duplicate of https://github.com/barryvdh/laravel-ide-helper/issues/627 :} (which IMHO has more/better details)

Closing per my comment https://github.com/barryvdh/laravel-ide-helper/issues/108#issuecomment-650617938


Firefox RU 41.0.1

When submitting these type of updates, feel free to do them all in a single PR.


chore(main): release eslint-config 0.1.0

:robot: I have created a release beep boop
0.1.0 (2023-12-16)
Features

update eslint plugin (b713548)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fission-codes/stack/releases/tag/eslint-config-v0.1.0 :sunflower:


feat(p4_api): support older perforce servers

This change allows use of this software with older perforce servers and clients which don't support "-r" option.
See https://github.com/salesforce/p4-fusion/issues/52 for more.

Thanks for the quick reply!

Thanks for sending this! I think you also need to sign the CLA to finally merge this in.
I did, I guess im watiting now for bot to recognize that.
However I had a few comments on the PR which are really just stylistic changes, if you don't mind.
they are solved, i also didnt run clang format so we'll see how it goes.

@ppavacic Thanks for reminding me, I just ran workflows on this PR. Looks like there are a couple formatting fixes left - https://github.com/salesforce/p4-fusion/actions/runs/7420887077/job/20381786678?pr=71

@ppavacic Thanks for reminding me, I just ran workflows on this PR. Looks like there are a couple formatting fixes left - https://github.com/salesforce/p4-fusion/actions/runs/7420887077/job/20381786678?pr=71

can you try now?

Thanks a ton for the work

that's only a small change heh
thank you for review and fast merge!


doc versioning

Signed-off-by: Bettygogo2021<EMAIL_ADDRESS>Hi, Ben, I tested the doc versioning function of Docsy, and found it is not viable to add a drop-down menu to Documentation, but we can achieve versioning in another way. Hope the following pictures can make my point clear:

Next time we need a new version, we can add a folder in the Docs repo:

Then we comment out earlier versions in the _index file.

The final display is as follows:

As for i18n display issues, I've discussed them with the frontend developer Lichangjiang, and he will fix them. Pls kindly review and merge this PR.
/assign @benjaminhuo

 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.

Signed-off-by: Bettygogo2021<EMAIL_ADDRESS>Hi, Ben, I tested the doc versioning function of Docsy, and found it is not viable to add a drop-down menu to Documentation, but we can achieve versioning in another way. Hope the following pictures can make my point clear:

Next time we need a new version, we can add a folder in the Docs repo:

Then we comment out earlier versions in the _index file.

The final display is as follows:

As for i18n display issues, I've discussed them with the frontend developer Lichangjiang, and he will fix them. Pls kindly review and merge this PR.
/assign @benjaminhuo

That's great, thanks!

@Bettygogo2021 @Patrick-LuoYu,  kubesphere.io's documentation is not using docsy?
Just wondering how kubesphere.io adds versions links on the top menu?

Yes. kubesphere.io's documentation is not using it. It is written by ourselves.

@Bettygogo2021 @weili520 @Patrick-LuoYu, kubesphere.io's documentation is not using docsy? Just wondering how kubesphere.io adds version links on the top menu?

Yes. kubesphere.io's documentation is not using it. It is written by ourselves.

Got it


CLDR 41 update - date formats

Checklist

[ ] At least one test case is included for this feature or bug fix.
[x] ReleaseNotes has added or is not needed.
[x] This PR has passed all of the test cases on Nodejs and Chrome Browser.
[ ] This PR has passed all of the test cases on QT/QML.
[ ] This is an API breaking change.
[ ] Requires a major version change.

Issue Resolved / Feature Added
Resolution
Links

@gouniLee This one should go in first. After it is merged, we can rebase the other ones to get a much smaller set of files and make it much easier to code review.

doesn't need to add additional test cases regarding locale data change?

CLDR 41 did not change much in the existing locales. Mostly, it added a few new locales that we don't test.


ADDS does not have to have three parameters

Currently ADDS assumes three parameters. However, when adding an imm8 to a register, only two have to be given, ie ADDS R0, #8
The same issue exists with SUBS.

There seems to be conflicting documentation on this.
DDI0484 has no mention of this, which would lead me to believe that it assembler magic, except that DUI0662 does talk about it. Since DUI0489 does mention it, but not what it does, DUI0662 should be used as reference for this.
Looking at page 3-20, it looks like the destination register is optional for all forms of the ADD[S] and SUB[S] instructions except in ADD when using PC as the second operand.
In fact, it looks like many more instructions support the implicit destination register.

If it is assembler magic, both armasm and arm-none-eabi-* have chosen to implement the implicit destination register.


Update FROM line in Dockerfile

The new docker images are located on Google Container Registry under these URLs.

Looks good. Do you know if the base image has been updated to the 1.4.2 toolchain? (And if so, can we remove the subsequent line?)


Request fails with invalid JSON

It seems there was a bug introduced with df18a5d.
My call crashes with an invalid JSON error after this change was applied. If I undo it everything works fine.

Nevermind: It seems to be an invalid swagger source file that expects a type with a list, which cannot be represented as URL encoded.


update to oqs-provider 0.6.0

Updates external test oqsprovider to latest release 0.6.0.
Among others, now supports NIST draft PQ standard algs ML-KEM, ML-DSA. OSSL provider-interface testing also extended.

Thanks for the quick review and approval. Is this also (going to be) automatically applied to 3.0/3.1/3.2/3.3 release branches or would/should I have to do something for this? The tests should adapt to the limited feature sets in those versions but test what is supported.

That's actually a good question.  I assume that 0.6.0 is designed to work with any of the OpenSSL (minor) releases since 3.0, so from the oqs-provider perspective, testing against all OpenSSL versions since 3.0 makes sense.
But for OpenSSL, the question is reversed; should we test all OpenSSL (minor) releases against oqs-provider 0.6.0?

But for OpenSSL, the question is reversed; should we test all OpenSSL (minor) releases against oqs-provider 0.6.0

I'd argue it would be sensible for older but still supported versions of OpenSSL (particularly new releases of those) to be tested against a supported oqsprovider version (which is (only) 0.6.0, see rationale below) prior to releasing them as there may be people using only (those) supported versions of openssl and oqsprovider.
I could of course also offer to manually test new openssl (maintenance/"downlevel") releases against oqsprovider each time I see them coming up, but a) this would probably be too late if this would detect problems and b) oqsprovider still pretty much is a one-guy show (still looking for reliable commitments by others to share real work...); so any CI/automated "testing help" would be very welcome (& sensible) from my perspective.

@beldmit Are you OK with applying this to stable branches?

I don't mind if tests pass

Merged to the master, 3.3 and 3.2 branches. Thank you for your contribution. As the commit conflicts on 3.1 branch, please open a separate PR against that branch if you want it merged there.


Add user-driven API support

Add API support for user-driven API
This should also remove the necessity of DebugMode and make tests a little better (DebugMode is a hack, API tests should just authenticate/get an API key with this feature instead)

Fixed this by properly implemented authenticated key/secret API, as of commit d2fd2b1


Very large thumbnail images for videos in Facebook Bridge

When a Facebook post has an embedded video, the thumbnail image within the RSS feed for the video tends to be huge.
E.g this post
This is the resulting image used in the feed
The image is 1920x1080 in this case, presumably a still frame from video at source resolution.
Can video stills used within the feed be shrunk somehow?

Thanks for opening this request.

Can video stills used within the feed be shrunk somehow?

Technically, yes. Images are embedded as <img> tags with whatever image Facebook returns to the request. It would be possible to add styles to specify the maximum width and height.
Alternatively images could be removed from the contents and attached as enclosures. I'm sure there are arguments against it though.
I quickly tried the code below, but it doesn't seem to work for me. It correctly removes the width and height attributes, but doesn't add the style attribute as one would expect.
// Set maximum scale of images within contents
foreach($content->find('img') as $img) {
	$img->style = 'display: block; width: 100%; max-width: 640px;';
	$img->height = null;
	$img->width = null;
}

It has something to do with how the parser handles attributes (new attributes are not exactly parsed). There is a workaround for it by adding the code below to the bridge at line 671:
$content = str_get_html($content);

// Set maximum scale of images within contents
foreach($content->find('img') as &$img) {
	$img->style = 'max-width: 640px;';
	$img->height = null;
	$img->width = null;
}

I'd rather find a proper solution for this before committing that workaround.

Since maximum image width is going to be a fairly subjective setting, there's an argument for including it as a bridge parameter in any final solution.

Also I'd be against moving the images to enclosures, I think a good rule of thumb is to keep the RSS feed looking as close to the appearance of the source website as possible. In this case the issue arises because an image size constraint which is present on the source website is not being applied to the feed.

@triatic Is this still an issue?

@dvikan I don't know, I've had to stop using this bridge is because of #2047 .

I will close and reopen if I can use this bridge once again.


Need some advice on setting up occurrences.

Hi there,
I have a sensu check that would use an email handler on CRITICAL and OK states.   When I don't specify occurrences, it would trigger the first time something hits critical and triggers when things "recover" and goes back to normal.  This is working good.
I wanted to change the check so that after 5 checks (1 min per check) it will send an email saying something is in CRITICAL state, and after it drops back to OK state I wanted it to send the recover email.   My problem now is that the 5 CRITICAL checks triggers the email, but when it goes back down to OK state, I no longer get an email trigger.   I also have a Slack check that is also not posting recovery messages now.   What is the best way to solve this?
My check looks like this
{
  "checks": {
    "check-sidekiq-queue": {
      "handlers": ["default", "mailer", "slack"],
      "occurrences": 5,
      "command": "/etc/sensu/plugins/check-sidekiq-queue.rb",
      "interval": 60,
      "subscribers": [ "check_sidekiq_queue" ]
    }
  }
}

My mailer configuration
{
  "handlers": {
    "mailer": {
      "type": "pipe",
      "command": "/etc/sensu/handlers/mailer.rb",
      "severities": [
        "critical",
        "ok"
      ]
    }
  }
}

@tleung999 does the Sensu server log /var/log/sensu/sensu-server.log provide any hints to as why the resolve action is not sending an email?

I have observed something lately that might be related. The problem is that the event will only resolve when the handler has received consecutive "OK" results equal to the "occurrences" setting.  So in your case it needs 5 OK results before it resolves.  But it appears that the client will only send one OK result and then not send anything more until the state changes again.  So in other words, if this is correct, it's broken.  I'm pretty sure this used to work somehow at some point, so it might be a recent change, perhaps in the sensu-plugins module.

I happened to find another check where the resolution works, in spite of the observation described above.  This particular check has occurrences set to 2.  Some interesting pieces of the message are:
"status":0,"history":["0","0","0","0","0","0","0","0","0","0","0","0","0","0","0","2","2","2","2","2","0"],"total_state_change":11},"occurrences":5,"action":"resolve"}}

Note that the message says "occurrences": 5.  Apparently, the occurrences count does not get reset when the status changes to 0. (Why?) As a consequence, the handler is happy to resolve the incident, because 5 > 2.
The other check I referred to above has occurrences set to 5.  The interesting parts of the message are
"status":0,"history":["0","0","0","0","0","0","0","0","0","0","0","0","1","1","2","2","2","2","2","1","0"],"total_state_change":22},"occurrences":1,"action":"resolve"}}

Apparently, because the state changed from critical to warning just before resolving, the occurrences were reset to 1 and are then never updated afterwards, as described above.
You didn't indicate that your check could issue warning results, so I don't know if this actually matches your scenario. But I'm coming around to the conclusion that the occurrences stuff is pretty shaky.  (See also debate in #885 about what occurrences actually mean for flapping checks.)

I wonder if we can close this now? We've made a number of improvements around occurrence filtering, including a PR that specifically addressed issues related to resolutions.
Barring any new updates to this issue indicating otherwise, we will look to close this issue due to inactivity at our next issue triage. :v:

Could it be a flapping event? If so then the handler needs to be configured to handle flapping events and the handler must actually support this. I recently saw something similar in the pagerduty handler but patched it to support this behavior: https://github.com/sensu-plugins/sensu-plugins-pagerduty/pull/41

Closing, as we have made several improvements to occurrence/refresh filtering, including moving it into core as built-in filters.
Please reopen this issue if it is still an issue!


IOError: [Errno 32] Broken pipe on    File "eval/meteor_bridge.py

th train.lua
.....
Processed image 2395971.jpg (997 / 1000) of split 1, detected 100 regions
Processed image 2395960.jpg (998 / 1000) of split 1, detected 107 regions
Processed image 2395955.jpg (999 / 1000) of split 1, detected 93 regions
Processed image 2395949.jpg (1000 / 1000) of split 1, detected 109 regions
Loss stats:
{
mid_box_reg_loss : 0.0010088438019855
captioning_loss : 27.884303262711
end_box_reg_loss : 0.0020599792839494
end_objectness_loss : 0.042175837257504
total_loss : 28.011510998734
mid_objectness_loss : 0.081963075679541
}
Average loss:   28.011510998734
Traceback (most recent call last):
File "eval/meteor_bridge.py", line 69, in
score = m._score(r['candidate'], r['references'])
File "eval/meteor_bridge.py", line 39, in _score
self.meteor_p.stdin.write(w)
IOError: [Errno 32] Broken pipe
/home/rzai/torch/install/bin/luajit: ./densecap/utils.lua:86: attempt to index local 'file' (a nil value)
stack traceback:
./densecap/utils.lua:86: in function 'read_json'
./eval/eval_utils.lua:100: in function 'score_captions'
./eval/eval_utils.lua:231: in function 'evaluate'
./eval/eval_utils.lua:83: in function 'eval_split'
train.lua:153: in main chunk
[C]: in function 'dofile'
...rzai/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00406670
rzai@rzai00:~/prj/densecap$
rzai@rzai00:~/prj/densecap$ ll eval
total 19088
drwxrwxr-x  2 rzai rzai     4096 10月 27 11:29 ./
drwxrwxr-x 14 rzai rzai     4096 10月 27 13:42 ../
-rw-rw-r--  1 rzai rzai    10674 10月 24 17:18 eval_utils.lua
-rw-rw-r--  1 rzai rzai       38 10月 24 17:18 .gitignore
-rw-rw-r--  1 rzai rzai 13190274 10月 27 14:31 input.json
-rw-r--r--  1 rzai rzai  6318623 10月 27 03:09 meteor-1.5.jar
-rw-rw-r--  1 rzai rzai     2695 10月 24 17:18 meteor_bridge.py
-rw-rw-r--  1 rzai rzai     2851 10月 24 17:18 README.md
rzai@rzai00:~/prj/densecap$

I have also met this problem and this confuse me several days. Hope someone can give an awesome solution for this  issue.

i have solve this issue. i do not know whether the cause of my problem is same as your's, but i can tell you my solution as reference.
When execute eval_utils.lua, it calls 'meteor_bridge.py', the function of this python file is just as the author announced. when new a subprocess.Popen object, it need a 'arg' parameter, and "By default, the program to execute is the first item in args if args is a sequence". in this python file, this 'arg' parameter give the way the meteor-1.5.jar execute. I try to execute the java command in terminal, and i found it can not identify the "....../data/paraphrase-en.gz" path, because the path contains some character the java problem can not identify, so i change the directory to all english name, and it worked out!!!

@Dorniwang
I don't find the "....../data/paraphrase-en.gz" path
rzai@rzai00:/media/rzai/ai_data/prj/densecap$ find . -name "*en.gz" -print
rzai@rzai00:/media/rzai/ai_data/prj/densecap$ find . -name "paraphrase" -print
rzai@rzai00:/media/rzai/ai_data/prj/densecap$ cd data/
rzai@rzai00:/media/rzai/ai_data/prj/densecap/data$ tree
.
├── models
│   ├── densecap
│   │   └── densecap-pretrained-vgg16.t7
│   └── vgg-16
│       ├── VGG_ILSVRC_16_layers.caffemodel
│       └── VGG_ILSVRC_16_layers_deploy.prototxt.lua
├── VG-regions-dicts.json
└── VG-regions.h5
3 directories, 5 files
rzai@rzai00:/media/rzai/ai_data/prj/densecap/data$

you should notice what the author said:https://github.com/jcjohnson/densecap/blob/master/eval/README.md, it is mentioned in the Requirement that "you'll need to download the METEOR binary meteor-1.5.jar and place it in eval folder and also paraphrase-en.gz and place it it in eval/data folder."

so, you got this error by non-english characters, and I missed the paraphrase-en.gz


Navigation to URLs with # should focus on that respective section of the webpage

Presently, our "jump to" or "focus on this section" URL behavior does not focus on that section of a webpage. For example if you go to https://designsystem.webstandards.ca.gov/style/content/#our-inspiration the focus is NOT at the Our inspiration header.
This presents an accessibility tabbing issue. If you were to tab to Our inspiration > hit Enter... at next tab the expectation would be to be focused on 18F. However if you hit tab, you're focused on Share your thoughts
This behavior is present across all pages with a left nav.

Issue:
Tab focus shifts back to the local navigation instead of the link below the section selected.
Recommendation
Tab should begin from the section that has focus and not wrap to the top of the page once a local navigation link is clicked.
WCAG 2.1 Guidelines
2.4.3 Focus Order (Level A)

3.2.1 On Focus (Level A)

Confirmed working. Closing. Pending move to done once merge completed tomorrow.


Update DPE to latest commit

In particular, this adds license headers to several files which makes the file header check run cleanly on the DPE code.
It also contains several other DPE features.

No longer relevant. Submodule is updated well past this point.


add validation to check if stagingPath exists

Describe what this PR does
It's CO responsibility to create the staging path as per the CSI spec.
The CO SHALL ensure
// that the path is directory and that the process serving the
// request has read and write permission to that directory. The
// CO SHALL be responsible for creating the directory if it does not
// exist.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>Is there anything that requires special attention
Do you have any questions?
Is the change backward compatible?
Are there concerns around backward compatibility?
Provide any external context for the change, if any.
For example:

Kubernetes links that explain why the change is required
CSI spec related changes/catch-up that necessitates this patch
golang related practices that necessitates this change

Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #485
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.

@Madhu-1 can you cleanup the PR description. Rest looks good to me.

@humblec done

Thanks . LGTM.

@ShyamsundarR @poornimag  PTAL .

@humblec I have added some more validation PTAL

@humblec @ShyamsundarR @poornimag rebased PTAL

@ShyamsundarR in the CSI spec  I didn't find anything related to  CO's responsibility to delete the stagingPath. so deleting it

@ShyamsundarR in the CSI spec I didn't find anything related to  CO's responsibility to delete the stagingPath. so deleting it

If it is not the plugin's responsibility to create it, it is not the plugins responsibility to delete it as well. I would hence suggest we fix the deletion in unstage as well.

@ShyamsundarR done PTAL

@ShyamsundarR PTAL

@ShyamsundarR Can you please review this ?


Fix conda python env config

fixes #169

CI is green, I'm merging this

Should we report the issue with file: to cond upstream?


Add Chinese Simplified translations

Add Chinese Simplified translations

Thanks, but it seems you did not use Visual Studio, therefore Language.zh_CN.resx wasn't listed in Solution Explorer. And you haven't translated the Forms

Yes. I use Zeta Resource Editor, which is an open source localization tool that can translate the required characters directly.

I see. Also the file must be Language.zh-CN.resx, not Language.zh_CN.resx, otherwise the tool will not be able to detect it. I have added Chinese Simplified now


openresty: <IP_ADDRESS> -> <IP_ADDRESS>

Motivation for this change
close #90936
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

/nix/store/x2xb13a6k18sld2a1kxlk2gl89dnsdpy-openresty-<IP_ADDRESS>   471.8M
/nix/store/vwim8acwff2fn2dprv8bxkww0f2ycj8g-openresty-<IP_ADDRESS>   471.7M

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/217

thanks!


White screen when visiting the Web UI

Hello,
I am new to mailpit and have just installed it using go install github.com/axllent/mailpit@latest. While mailpit is apparently successfully launched:
me@localhost:~/go/bin> ./mailpit
INFO[2023/10/29 11:23:11] [smtpd] starting on <IP_ADDRESS>:1025
INFO[2023/10/29 11:23:11] [http] starting server on http://localhost:8025/

Visiting the web page gives me a blank page and I can see the following messages in dev tools:
Content Security Policy: The page's settings blocked the loading of an inline resource (« script-src »)
 http://localhost:8025/dist/app.css?dev » was blocked due a MIME type (« text/plain ») incorrect (X-Content-Type-Options: nosniff)
 http://localhost:8025/dist/app.js?dev » was blocked due a MIME type (« text/plain ») incorrect (X-Content-Type-Options: nosniff)

I apparently get 404 errors for these two files. The HTML of the page is:
<!DOCTYPE html>

	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width,initial-scale=1.0">
	<meta name="referrer" content="no-referrer">
	<meta name="robots" content="noindex, nofollow, noarchive">
	<link rel="icon" href="/favicon.svg">
	<title>Mailpit</title>
	<link rel=stylesheet href="/dist/app.css?dev">

		You require JavaScript to use this app.

There is nothing fancy in my setup (no reverse proxy etc...) I am just launching the binary.

Hi there. You cannot install Mailpit in this way because it doesn't come bundled with precompiled CSS & J's files. Please refer to the documentation if you wish to compile it yourself.

@nkosi23 Good questions. The pre-compiled binaries do include everything including the "virtual" filesystem used by the web UI (bundled JS, CSS, images etc), but the source code does not include the compiled assets (just the source files to build these). The reason for this is simple: as I'm sure you can image, the precompiled CSS & JavaScript is quite large (relatively speaking). If the compiled versions were bundled and I was to make a small change to either of those, the entire compiled files would be checked back into git each time (not just the line or character change as they are minified, so everything is on a single line). This would lead to a much bigger source repository filled with tonnes of irrelevant historical data.
Anyway, this is the path I chose, and while that does mean that go install... doesn't work, I have provided multiple ways to install a fully working version, and instructions for those wanting to compile it (all) from source.
I hope that makes sense?


Option for which characters to return?

First of all this is an amazing idea.
I am intrigued by the notion of using this for UI facing inputs. There are many potential ways to solve thousands separators with javascript, but they pose many complications that a font-based solution completely and utterly removes. The added complication of managing what font is being used is many orders of magnitude more straightforward.
However... in a case where we're using a licensed font, running a fontfile through a patcher is potentially illegal! I was thinking an alternative would be to bake a custom font with similar numbers based on an open source font into a component, but ideally JUST a subset of characters that will be needed. An option to specify characters would allow this while using the patcher would be awesome so that a frontend component could bundle with it a much lighterweight font (There is probably a way to do it separately as well, but I have very little experience with open type fonts)

Yah this is totally possible, and shouldn't be too hard to do just by looking at what the patcher does and maybe also what the powerline font patcher does, it should be possible to only copy a subset of characters. I don't plan on implementing this though, but you can if you want to.
If you are making a Javascript component and using underlines, I recommend just inserting underline tags since that will be slightly more seamless and lightweight, and work with any font. But if you specifically want fake commas that aren't part of the text when copy-pasted then you may need a font.

Yes I am more concerned with commas than underlines. This approach would solve a few issues really nicely:

Can use native number inputs which means far fewer accessibility issues and less complicated code (arrows up and down works by default, can rely on input value being a number, automatic masking)
Live formatting as you type without any js overhead
Copy would give the literal number and copy/paste would work with no issues
With locale settings in the font it could handle languages that separate thousands with spaces out of the box


Replace all ListViews/GridViews with RecyclerViews.

Replace all ListViews/GridViews with new RecyclerViews.
http://developer.android.com/reference/android/support/v7/widget/RecyclerView.html

Everything is refactored so far, but I couldn't achive it for the ItemList inside ModuleList in CourseLearningsFragment. Need a GridLayoutManager that calculates the fixed height for the nested RecyclerView.

Should be fixed soon: https://code.google.com/p/android/issues/detail?id=74772


The VVR version of Aliyun Flink is not supported

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

StreamPark Version
1.2.3
Java Version
No response
Flink Version
1.13
Scala Version of Flink
2.11
Error Exception
The current Scala version of StreamX is 2.11.12, but the scala version of Flink to be added is 2.11-1.13-vvr-4.0.12, which does not match, Please check

Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @fantasticKe , thanks for your feedback.
I think the root cause is StreamPark parse the scala version from flink-dist_(.)-(.).jar. And the second (.*) is the scala version.
You can try to rename the flink-dist_(.)-(.).jar inside VVR version, change the second (.*) to 2.11. I think it can work after change.

yes,i got it. thx

Hi @fantasticKe , thanks for your feedback.
I think the root cause is StreamPark parse the scala version from flink-dist_(.)-(.).jar. And the second (.*) is the scala version.
You can try to rename the flink-dist_(.)-(.).jar inside VVR version, change the second (.*) to 2.11. I think it can work after change.

yes,i got it. thx

supported


optionally consider nested repos

Fixes #57.
Since the crawling for potentially nested repos might inflict a significant overhead it is better to require an explicit option.

Trying to test this. But get the following error vcs export: error: unrecognized arguments: -n.
F:\ReposVendor\vcstool (support_nested_repos -> origin)
λ git status
On branch support_nested_repos
Your branch is up to date with 'origin/support_nested_repos'.

nothing to commit, working tree clean

F:\ReposVendor\vcstool (support_nested_repos -> origin)
λ python setup.py develop
running develop
running egg_info
writing vcstool.egg-info\PKG-INFO
writing dependency_links to vcstool.egg-info\dependency_links.txt
writing entry points to vcstool.egg-info\entry_points.txt
writing requirements to vcstool.egg-info\requires.txt
writing top-level names to vcstool.egg-info\top_level.txt
reading manifest file 'vcstool.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'vcstool.egg-info\SOURCES.txt'
running build_ext
Creating n:\python36\lib\site-packages\vcstool.egg-link (link to .)
vcstool 0.1.31 is already the active version in easy-install.pth
Installing vcs-script.py script to N:\Python36\Scripts
Installing vcs.exe script to N:\Python36\Scripts
Installing vcs-branch-script.py script to N:\Python36\Scripts
Installing vcs-branch.exe script to N:\Python36\Scripts
Installing vcs-bzr-script.py script to N:\Python36\Scripts
Installing vcs-bzr.exe script to N:\Python36\Scripts
Installing vcs-custom-script.py script to N:\Python36\Scripts
Installing vcs-custom.exe script to N:\Python36\Scripts
Installing vcs-diff-script.py script to N:\Python36\Scripts
Installing vcs-diff.exe script to N:\Python36\Scripts
Installing vcs-export-script.py script to N:\Python36\Scripts
Installing vcs-export.exe script to N:\Python36\Scripts
Installing vcs-git-script.py script to N:\Python36\Scripts
Installing vcs-git.exe script to N:\Python36\Scripts
Installing vcs-help-script.py script to N:\Python36\Scripts
Installing vcs-help.exe script to N:\Python36\Scripts
Installing vcs-hg-script.py script to N:\Python36\Scripts
Installing vcs-hg.exe script to N:\Python36\Scripts
Installing vcs-import-script.py script to N:\Python36\Scripts
Installing vcs-import.exe script to N:\Python36\Scripts
Installing vcs-log-script.py script to N:\Python36\Scripts
Installing vcs-log.exe script to N:\Python36\Scripts
Installing vcs-pull-script.py script to N:\Python36\Scripts
Installing vcs-pull.exe script to N:\Python36\Scripts
Installing vcs-push-script.py script to N:\Python36\Scripts
Installing vcs-push.exe script to N:\Python36\Scripts
Installing vcs-remotes-script.py script to N:\Python36\Scripts
Installing vcs-remotes.exe script to N:\Python36\Scripts
Installing vcs-status-script.py script to N:\Python36\Scripts
Installing vcs-status.exe script to N:\Python36\Scripts
Installing vcs-svn-script.py script to N:\Python36\Scripts
Installing vcs-svn.exe script to N:\Python36\Scripts

Installed f:\reposvendor\vcstool
Processing dependencies for vcstool==0.1.31
Searching for PyYAML==3.12
Best match: PyYAML 3.12
Adding PyYAML 3.12 to easy-install.pth file

Using n:\python36\lib\site-packages
Finished processing dependencies for vcstool==0.1.31

F:\ReposVendor\vcstool (support_nested_repos -> origin)
λ cd ../../VcsExample/

F:\VcsExample
λ which vcs-export
/n/Python36/Scripts/vcs-export

F:\VcsExample
λ vcs-export -n
usage: vcs export [-h] [--exact] [--debug] [-w N] [--repos] [path]
vcs export: error: unrecognized arguments: -n

F:\VcsExample
λ vcs export
repositories:
  group:
    type: git
    url: https://github.com/ihmcrobotics/repository-group.git
    version: master```

--nested also does not work.
F:\VcsExample
λ vcs-pull --nested
usage: vcs pull [-h] [--debug] [-s] [-w N] [--repos] [paths [paths ...]]
vcs pull: error: unrecognized arguments: --nested

It doesn't look like using the "right" version of the code. When you run vcs export --help you will likely not see the option either? It works for me locally.
Maybe try to just pip install it.

That worked!
F:\ReposVendor\vcstool (support_nested_repos -> origin)
λ pip install -e .
Obtaining file:///F:/ReposVendor/vcstool
Requirement already satisfied: PyYAML in n:\python36\lib\site-packages (from vcstool==0.1.31)
Installing collected packages: vcstool
  Found existing installation: vcstool 0.1.31
    Uninstalling vcstool-0.1.31:
      Successfully uninstalled vcstool-0.1.31
  Running setup.py develop for vcstool
Successfully installed vcstool

F:\ReposVendor\vcstool (support_nested_repos -> origin)
λ vcs-export --help
usage: vcs export [-h] [--exact] [--debug] [-n] [-w N] [--repos] [path]

Export the list of repositories

optional arguments:
  -h, --help         show this help message and exit

"export" command parameters:
  --exact            Export exact commit hash instead of branch names
                     (default: False)

Common parameters:
  --debug            Show debug messages (default: False)
  -n, --nested       Search for nested repositories (default: False)
  -w N, --workers N  Number of parallel worker threads (default: 8)
  --repos            List repositories which the command operates on (default:
                     False)
  path               Base path to look for repositories (default: .)

All command appear to be working for me with -n! This is really great. Did a pull on my 65 or so nested repositories and it took 28 seconds. SmartGit takes 1m 22s for comparison. Thanks a bunch.

Thanks for trying it and reporting back.

:ship: in 0.1.32.


Bug: pageChange event isn't triggered in in-dom template.

Currently, camel case named event is not triggered in in-dom template.
Maybe we need to change the event name like page-change or trigger both events.
Refer https://github.com/vuejs/vue/issues/4044

I'll make sure to document this at some point, but much like @yyx990803's stance on in-dom templates, I'd prefer to advocate using string templates or standalone components as they're much more stable in the Vue ecosystem. Cheers!


[vcpkg] Attempt to make the upgrade command 'reasonably transactional'

Fix for #6317, #4360, #4367, #3864 (it's duplicates)

 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.:x: NulAsh sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Ask your questions.

I'm just going to leave my two cents here that I like this approach.
Even better, as pointed out #6317, would be to make the upgrade only create non-revertible changes once everything is clearly in order.
However, this is a quick fix that I think will remove most of the pain from failures during an upgrade without breaking backwards compatibility.
The only comment I might have is naming/location details of the update file (I don't really like it just hanging around the root of vcpkg), but likely @ras0219-msft has an opinion on that.

What's wrong with the tests?

@NulAsh Going to close this PR as this PR has been open too long. If you are interested in working on this, feel free to reopen, but it might make more sense to make a new PR (otherwise we might lose track of it).
That said, I do think the upgrade command needs fixing.

Also I realize we haven't given any feedback on this PR for a long time. If you are still interested in some feedback, let me know and we can reopen this and prioritize this PR.

Of course I'm interested, this is a working solution to a problem that many people face.

@NulAsh We will review it and get some feedback.

3.5 years later...

Closing this PR since it no longer applies to this repository. If still interested, please open a PR in Microsoft/vcpkg-tool.


Capsule should not run as Cluster Admin

Describe the feature
During the reconciliation loop, Capsule will ensure that the admin Role is going to be granted to the Tenant owner for their Namespace resources: this is actually mandatory with the current RBAC setup, otherwise, Capsule wouldn't be able to grant RBAC permissions that are not currently held.
What would the new user story look like?
We should investigate how to decrease the RBAC permissions to the minimum but, at the same time, allows Capsule to grant admin role to Tenants.
Probably we need to use the bind verb at RBAC for the admin resources at the cluster scope.
Expected behavior
Capsule would be running as a non Cluster admin and eligible to bind admin role to tenant owners without getting the following error:
user "system:serviceaccount:capsule-system:capsule" (groups=["system:serviceaccounts" "system:serviceaccounts:capsule-system" "system:authenticated"]) is attempting to grant RBAC permissions not currently held: (...)

As the linked PR explains, we have to run as Cluster Admin to bind admin roles to Tenant owners.


Update documentation for MSRIOGroup and related classes

After #435, MSRIOGroup's man page may need to be updated.  Also, some classes like MSRSignal may be deprecated and the documentation should reflect that.

Related to #1055

I think this can be closed.  We don't describe the signals/controls in the man page for any IOGroups.  We do have the separate lists of controls/signals on the various platforms we support (just SKX for now) which I think captures the spirit of this task.
https://geopm.github.io/signals_SKX.html


Add aria-label to dropdown component

This dropdown component was causing 'Accessibility check failed!' errors in my cypress tests. Below is a screenshot of the produced error. Simple fix was just to add an aria-label to the component.

This dropdown component was causing 'Accessibility check failed!' errors in my cypress tests. Below is a screenshot of the produced error. Simple fix was just to add an aria-label to the component.

Is this Cypress failure somewhere on CI (or on the Cypress dashboard) where I could take a look, or is it local dev?

This dropdown component was causing 'Accessibility check failed!' errors in my cypress tests. Below is a screenshot of the produced error. Simple fix was just to add an aria-label to the component.

Is this Cypress failure somewhere on CI (or on the Cypress dashboard) where I could take a look, or is it local dev?

The error is occurring locally. I'm pushing up the tests now so you can take a look but it seems to pass fine in CI. Interesting because the accessibility tab in Radiance for the dropdown component also points out the exact same issues I was seeing locally. Heres the PR

Closing in favor of the fix in userland mentioned above ^^^^
I've merged in https://github.com/curology/radiance-ui/pull/1117 to fix some misleading accessibility violations in our Storybook app, which includes mention of 3 new issues to fix the remaining issues, at least a couple of which are legitimate a11y issues in the library.


Too many dependencies

Too many dependencies referenced in go.mod.
It would be helpful to move the test suite to a separate Go module in the same repo. Go workspaces might be helpful for development.

Yeah this is a frustrating problem with go.mod. All the dependencies are actually test-only dependencies, and they won't be pulled on go get or go mod download.
I'm not a fan of changing how the code (and tests) is structured to bypass a shortcoming of the official tooling, so I'd rather keep it this way and wait for updates on https://github.com/golang/go/issues/44743 or https://github.com/golang/go/issues/26955
(I don't close the issue yet because I'm still a bit torn on this)

I changed my mind and did the split, having an empty root go.mod is great :D

An alternative would be to use a tool like https://github.com/komuw/ote.


[NTR] stratified squamous epithelial cell of anal canal

Note - please check that the term does not already exist (check OLS: https://www.ebi.ac.uk/ols/ontologies/cl)
Preferred term label:
stratified squamous epithelial cell of anal canal
Synonyms
anal canal stratified squamous epithelial cell
Definition (free text, please give PubMed ID in format PMID:XXXXXX)
Stratified squamous epithelial cell that is part of the anal canal
Parent cell type term (check the hierarchy here https://www.ebi.ac.uk/ols/ontologies/cl):
stratified squamous epithelial cell http://purl.obolibrary.org/obo/CL_0000240
What is the anatomical structure that the cell is a part of? Please check Uberon: https://www.ebi.ac.uk/ols/ontologies/uberon
anal canal http://purl.obolibrary.org/obo/UBERON_0000159
Your nano-attribution (ORCID)
0000-0003-3440-1876
Any additional notes or concerns

Hi @sfexova ,
Is this term request still for part_of 'anal canal', or should it be revised to part_of 'anorectum'?
Thanks,
Paola

Hi @paolaroncaglia, thanks - it is still needed, yes.


Update content

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/python-sdk-azure-multi-cloud.md
:white_check_mark:Succeeded

docs-ref-services/dns.md
:white_check_mark:Succeeded

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


Unable to use the nautobot helm chart as a dependency in a chart

Error:
Error: values don't meet the specifications of the schema(s) in the following chart(s):
nautobot:

(root): Additional property global is not allowed

This seems to be related to the values.schema.json

The likely issue is with root.additionalProperties being set to 'false' - https://github.com/nautobot/helm-charts/blob/02fd2b0025831a30909fde97007f1d93dc2bdfef/charts/nautobot/values.schema.json#L363
Similar issue discussed here: https://github.com/helm/helm/issues/10392


Document PREPARE statements

DataFusion supports PREPARE statements, with flavors to suite all tastes such as explicit or inferred types, and positional or named arguments. I noticed docs for this feature are entirely missing from the SQL Reference (link).

Yes, thank you @leoyvens
@NGA-TRAN , @erratic-pattern and @jonahgao  have done some great work in this area and indeed it would be great to get it documented


CORS support on GET /query

Hi, I'm working on a javascript web frontend to query my json formatted structured logs.
I ran into a snag while getting the data from the /query api endpoint: there's no CORS support so cross domain javascript queries fail.
Is this something that's desirable to add? If so I can submit a PR.

Yeah, PR happily accepted for that.

Yeah, PR happily accepted for that.


How to understand the cpu_time_percent(or 'Total CPU %') for multi-core CPUs?

100% means you are utilizing one entire CPU. In multi-core systems, CPU utilization can exceed 100%, where 100% represents full utilization of one core. For example, on a 4 core system, 400% utilization means all four cores are fully utilized.


Extended rights for volunteers to help supporting your micro project

@zyedidia
This issue shall be understood as a general request to officially support you and your project micro.
Currently we've a lot of issues and PRs open, but no capability to get them into an sufficient order. What I mean is, that maybe all or some specific people currently active in trying to support here will receive the right to add (existing) labels and maybe some priority (milestone) handling to been as efficient as possible to not doing things twice and get the things sorted in the right order.
micro is a very nice editor and has very interesting approaches and it needs to be frequently maintained. :)

I totally agree with @JoeKar.
Actually a lot of PRs open with people behind who took some of their time and deserve at least some communication 🙂
We are a lot to love this project ❤ and hope that it continues to grow in a good way 😌

I'm sorry for the lack of communication. Unfortunately I've been focusing on other projects recently, and the time I devote to micro has been strained. It's a blessing that so many people devote time to working on micro and I regret often leaving posts without a response. I will try to respond to the recent PRs and issues this weekend and do some general maintenance. I'll probably make a new minor release with those changes next week.
I think adding labels and milestones would be helpful. If you or others (generally people who have been engaged on the issue/PR tracker) would like to take that on, I'll look into how to make that happen. Thank you for your patience and your help in the development of micro.

That sure is a stack of issues and PRs. It's nice to see you offer to try and sort it out.
Micro is fantastic, I'm very thankful for it, and next time I need to pop by the repo to check some docs, I hope to see it appear as less of a burden to its creator and contributors, who so kindly share their work with us all.

If you or others (generally people who have been engaged on the issue/PR tracker) would like to take that on, I'll look into how to make that happen.

Yes, I would definitely appreciate that. With the help of labels we can tag what's really a bug and need to be fixed earlier, what's a feature request and what's a general question only. With the help of milestones the project can benefit of some sort of priority handling per next release or something like that.
@dmaluka:
Since you're one who is very committed to the project what do you think about it?

Sounds good, I wouldn't mind having rights to put labels like "reviewed and can be merged" or "solved and can be closed" (as a substitute for the lack of the actual rights to merge PRs or close issues ;)).

@dmaluka @JoeKar
Hello! How do you manage your version that includes all the not merged PR's? Just bunch of merge commits?

@dustdfg

How do you manage your version that includes all the not merged PR's? Just bunch of merge commits?

Yeah, just my local branch with a bunch of merge commits for the PRs I'm interested in. I was going to upload that to my fork so that others could just use it, but I've been too lazy for that.

Before we end up in more or less the same situation again after having the capabilities of labels/milestones and what ever.
How about directly adding merge rights and extended issue rights for at least some more trustworthy people (I don't count myself here :wink:)?
I've still the trust that micro will benefit from combining all of our efforts/time from every supporter.

It looks like now micro is a repo of @zyedidia and doesn't belong to https://github.com/micro-editor organization.
Anyway what I found: repository roles. I think Triage role is exactly what @JoeKar described when opened this issue. Also if Writer role is to permissive it can be restricted by branch protecting in particular via branch locking.
I am not sure if I my proposal is correct from point of view what github allows but I have to propose:

Start using Triage role
Separate branch where those who have Writer role will be able to push. It will be the only place where people with Writer role will be able to push...

Sounds good, I wouldn't mind having rights to put labels like "reviewed and can be merged" or "solved and can be closed" (as a substitute for the lack of the actual rights to merge PRs or close issues ;)).

Maybe the worst and dirty solution to create separate issue where will be collected links to all the "reviewed and can be merged" PR's.

One more PR that could be just merged #1838

It looks like now micro is a repo of @zyedidia and doesn't belong to https://github.com/micro-editor organization.

...but would fit there the best. Additionally the updated forks of tcell and json5 would be perfectly placed there. The organization would allow the best maintainability.
It's now up to @zyedidia to carefully decide what's best for micro.

It's now up to @zyedidia to carefully decide what's best for micro.

Or it can be ended up by creating a new repo (eg. micro-next) and fix the root problem of having a single maintainer.
And then grabbing every interesting contribution, etc...

From what I've read in the comments, I believe the consensus would be:

Put the editor's source code in an organization
Create positions in that organization for administrators and maintainers
Add people from the community who are willing to do so

This would decentralize some functions such as maintaining the source code, accepting pull requests, creating labels/milestones.
These functions would no longer be the responsibility of just one person, but of all the people who use the editor and who are already involved in improving it.
The only question that remains open to me is who will do this? Will it be @zyedidia using the already existing micro-editor organization on github, will it be someone else through a fork or will we organize ourselves to do it?
Do I understand correctly?

Something needs to change so there is someone (or some group of reviewers) with authority to accept/reject changes looking at new contributions at least a few times a year. I don't think the project needs to be particularly fast-moving but it's frustrating when reasonable PRs don't get any attention for years (even if that attention would be a "no thanks" from the maintainer).
I could help out with closing stale/outdated issues and adding labels such as "needs-attention" to high impact PRs/issues.

I’m sorry for my non-presence and lack of availability. I think it’s time to add some maintainers to the project to help out. I think @JoeKar and @dmaluka would make good candidates to start. Please let me know your thoughts. Thank you for your patience and understanding.

@taconi maintains alternative plugin channel so I think he can be used for merging and maintaining original plugin repo

I think @JoeKar and @dmaluka would make good candidates to start.

Thank you, I'm honored. @dmaluka is definitely a safe bet too!
I can only speak for myself and can already predict, that some more people to support are necessary. Especially when we deal with the stack of past issues (currently 780 issues and over 100 PRs). I assume that our free time isn't enough to handle that :smile:
So since @Andriamanitra named his self for this task I can only welcome that. The activity within the discussion section speaks for @Andriamanitra and @taconi too. @dustdfg was busy in some issues/reviews over the past couple of months as well.
There is already a lot of intention visible.
Let us help you and micro. :smiley: :+1:

I think it’s time to add some maintainers to the project to help out. I think @JoeKar and @dmaluka would make good candidates to start.

Thanks, I would be happy to have maintainer's rights. It's not exactly like I usually have a plenty of free time, but there is already a number of still-not-merged PRs that I've spent quite some time reviewing (so that now I feel confident those PRs are in a good shape and merging them would make micro better), and I'm gonna continue doing so. And if someone asks me to help reviewing/approving a specific PR or to help with a specific issue, I'm happy to (try to find time to) help.

Great, thank you very much! For now, I will give the two of you access to merge pull requests and later possibly delegate plugin maintainership as well. If possible, please send me an email so that I can also contact you for anything important that might come up. Also, please email me if you need something such as an extra review for a PR, desire to add another maintainer, request for a new release, or something else. I'll always make sure to respond to email within a few days. Thanks!

Do you have any prediction on when the repository will be migrated to the micro-editor organization or will it not be done?

Do you have any prediction on when the repository will be migrated to the micro-editor organization or will it not be done?

I would ask about plugin repo if I was you

The plugin-chanell has not been updated for two years, yes it is a point to mention, I ended up finding issues related to the behavior of the micro in the html code of the web page, the entire organization needs to be maintained and the plugins be part of this. But for what reason will the editor code remain outside the organization?

I personally think that a text editor with an abandoned plugin channel is the same as an abandoned editor, because of this I will migrate to GNU/Emacs and will no longer maintain the plugin-channel or the plugins that are in micro-plugins , if anyone wants to do this maintenance of a plugin or the plugin-channel, open an issue and I will be transferring the project

I think around 1 or 2 more people now has to be given access on maintaining micro sometime. Micro may be considered stable or usable enough with some people like me, but there are still a lot of places that can be improved. The places that can be improved may be considered big or convenient with other users even if they are small.
A lot of time is spent on maintenance and one maintainer may have less experience on some parts, so I do not think only having added 2 maintainers is enough. Maintenance does not have to be done fast but there may at least be progress in issues and pull requests instead of nothing happening in a period that is too long, even if there will be pull requests that are properly not accepted.
Specific rights or roles cannot be given on personal repositories so the repository has to be moved to the organization. I have not read documentation much but I do think assigning writer and triage roles at organization level may be appropiate. People assigned triage role can at least manage issues in other repositories.
There seems to be differences with the tcell fork in the organization so I do not know what can be done with it. I do not know if some will still be interested but I think the people @JoeKar mentioned are appropiate with the tasks that were mentioned. I think these also have to be considered:

not closing old issues if there is still relevance
closing duplicate issues
creating labels related with parts like clipboard, syntax definition files, plugin installer, UI
adding labels on issues and pull requests
probably allowing someone on maintaining builtin runtime files using something like CODEOWNERS?
merging pull requests approved by people that are not maintainers, especially including ones approved more than months ago

I have not checked if these can be filtered when searching.

I apologize for the long text but I wrote this comment thinking it may help with proceeding the discussion, and understanding why things mentioned in the thread would be done.

A lot of time is spent on maintenance and one maintainer may have less experience on some parts, so I do not think only having added 2 maintainers is enough.

I assumed that even with two people it would be hard to deal with the (legacy) issues.

I have not read documentation much but I do think assigning writer and triage roles at organization level may be appropiate.

Yep, moving micro and the core dependencies into the already existing organization would be the right step, but unfortunately only @zyedidia can do this.

Yep, moving micro and the core dependencies into the already existing organization would be the right step, but unfortunately only @zyedidia can do this.

"fork it on github"


Activatable todos

While prototyping (sometimes for a long)), I often bypass universality in multiple places, so spawn todos. But currently, for this case, I can't use this crate: I can't make time predictions for my pet-project to use after_date! , and can't use the rest as I'm still prototyping, so can't integrate Github. So I need some activatable todo, maybe when building release or via some environment variable. To choose time and instead of grepping for todos get compilation errors. May I be not alone?
Thanks

There is an environmental variable to skip checks. Would this work for you?

Missed that section, sorry. Now I can use recently-stabilized config.toml with [env] section to disable all todos. There may be a problem with a broken compatibility with other kinds of todos, but I can't formulate why new kind of todo is inevitable yet. I'll close this, thanks


castopod: 1.6.4 -> 1.7.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for castopod is: An open-source hosting platform made for podcasters who want to engage and interact with their audience
meta.homepage for castopod is: https://castopod.org
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.7.1 with grep in /nix/store/vjzsh6ys6yf9a47g18yrwha4z4xnjihx-castopod-1.7.1
found 1.7.1 in filename of file in /nix/store/vjzsh6ys6yf9a47g18yrwha4z4xnjihx-castopod-1.7.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
castopod

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vjzsh6ys6yf9a47g18yrwha4z4xnjihx-castopod-1.7.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A castopod https://github.com/r-ryantm/nixpkgs/archive/376dfe8cecacfec0968cecd7525ed9d3d815e293.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/376dfe8cecacfec0968cecd7525ed9d3d815e293#castopod

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vjzsh6ys6yf9a47g18yrwha4z4xnjihx-castopod-1.7.1
ls -la /nix/store/vjzsh6ys6yf9a47g18yrwha4z4xnjihx-castopod-1.7.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

castopod

Maintainer pings
cc @AleXoundOS @misuzu for testing.

This automatic update broke tests. Need to finish #260518 first.


Is this project still maintained?

Is this project still maintained? Can it be used or it's been abandoned?

It is definitely still usable and easy to extend.
I've added quite a bit in my fork: https://github.com/gwindes/hound

This project is still being maintained!
More details here: https://github.com/hound-search/hound/issues/326#issuecomment-648987584


sc commands give errors

sc commands, as presented, don't work in powershell because the alias to Set-Content
use sc.exe instead

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

ID: b0bd8cb8-7e28-8c4d-a550-3aea8f3ab4dd
Version Independent ID: 4b60d24e-ef05-15e5-10b4-483094081bf3
Content: Host ASP.NET Core in a Windows Service
Content Source: aspnetcore/host-and-deploy/windows-service.md
Product: aspnet-core
GitHub Login: @guardrex
Microsoft Alias: tdykstra

By-design at this point—it's console-only at this time. Note tho that we're going to moving the entire process to PS on an upcoming doc update. Therefore, I'll close this as a dup of https://github.com/aspnet/Docs/issues/10833.
@gzinger Please feel free to add any thoughts you would like considered to that issue. That's the one that I'll use to track the work. It's going to have to wait a bit tho. We're about to dig into 3.0 doc updates, and that's going to take top priority. I'll get to https://github.com/aspnet/Docs/issues/10833 as soon as I can.


Unnecessary Scans/Reads -> Extra I/O

Consider the following query:
MATCH (a)-e1->(b)
RETURN e1.time;
Currently, we consider two possible QVOs [a, b] and therefore generate two plans:
P1: Scan(a) → Extend(b) → ScanEdgeProperty(e1.time) → Project([e1.time])

OR
P2: Scan(b) → Extend(a) → ScanEdgeProperty(e1.time) → Project([e1.time])

The extension to (b) comes from the fact that we tend to cover all of the query edges and vertices blindly regardless of what the query actually requests. The two plans should actually be:
P1: Scan(a) → ScanEdgeProperty(e1.time) → Project([e1.time])

OR
P2: Scan(b) → ScanEdgeProperty(e1.time) → Project([e1.time])

In other cases, where we don’t actually need any properties all together, we should simply get the size from the Lists header and therefore not pin/unpin unnecessarily. The query:
MATCH (a)-e1->(b)
RETURN count(*);
Should generate:
P1: Scan(a) → GetListSize(e1) → GROUP BY (COUNT(*))
P1: Scan(b) → GetListSize(e1) → GROUP BY (COUNT(*))

We need to be more aware of the actual properties needed. ID is just another property we do a join on.

Solved in PR #1329


ps0 will be OOM using MonitoredTrainingSession when workers too many

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.4
Python version: 2.7.5
Bazel version (if compiling from source): 1.9
GCC/Compiler version (if compiling from source): 4.9.2
CUDA/cuDNN version: CPU
GPU model and memory: CPU
Exact command to reproduce: Using MonitoredTrainingSession and thousands of workers.

Describe the problem
My model is large and complex. Thousands of worker&ps are needed and MonitoredTrainingSession is used. In the stage of initialization, the memory of ps0 will raise up to 100G and then OOM, but other ps work correctly. Op device placement is tf.train.replica_device_setter and no other special strategy.
I open the log_device_placement and found that all ops related with report_uninitialized_xxx are placed on ps0. I think this is the root cause.
I change the code as PR #22136 , and then it works correctly.

@drpngx Hi, do you have some updates?

Nagging Assignee @drpngx: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ispirmustafa: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @karmel: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @martinwicke, @karmel: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@jackonan,
Respected PR #22136 was closed. Could you please take a look at the PR and confirm if the issue still persists. Thank you!


Allow configuration of build.sh script

The final step of building & installation is running the build.sh script for the appropriate target architecture. For my macOS system, this does not seem to work. The problem is mainly that it hard-codes paths like /opt/local/lib/perl5/ and /opt/local/libexec/perl5/. I have Homebrew Perl installed, which is under /usr/local. Also, it might be nice to install in a user-local location like ~/perl5. Finally, note that the version pp on macOS does not accept all the arguments the script passes to it.

Those scripts aren't really user-facing - they are used to build the pp versions for distribution - you should just modify a local copy for you needs if you are for some reason building your own packed version. If your pp doesn't recognise some arguments in those scripts then this means you don't have the latest version of PAR::Packer.

Oh, I see. What is the recommended way to install biber to my own system then?

Just install it with TeXLive and use tex TexLive updater to update it - it's all part of the standard distribution. Or, alternatively, if you need a more recent version or can't use TeXLive, just download the relevant binary version from SourceForge.

Okay, thanks.


Get job ids with filters

What changes are proposed in this pull request?
Use the existing interface of job master to allow filtering of jobs by name and by job status
Why are the changes needed?
Currently, there is no way for client to efficiently look up job status and find incomplete jobs with a specific name/type
This leads to O(n) rpc calls from replicationChecker every heartbeat.
Does this PR introduce any user facing changes?
No

@apc999 obvious need to add more unit test and integration tests, but want to get an early round of review as I continue to improve this.

Codecov Report

Merging #13831 (dafb2cc) into master (3f343ec) will decrease coverage by 20.19%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #13831       +/-   ##
=============================================
- Coverage     43.64%   23.45%   -20.20%
+ Complexity     9093     4071     -5022
=============================================
  Files          1386     1386
  Lines         80552    80578       +26
  Branches       9803     9807        +4
=============================================
- Hits          35158    18900    -16258
- Misses        42450    60010    +17560
+ Partials       2944     1668     -1276

Impacted Files
Coverage Δ

...io/master/file/replication/ReplicationChecker.java
8.82% <0.00%> (-59.89%)
:arrow_down:

.../main/java/alluxio/client/job/JobMasterClient.java
100.00% <ø> (ø)

...luxio/client/job/RetryHandlingJobMasterClient.java
10.00% <0.00%> (-0.26%)
:arrow_down:

.../job/plan/replicate/DefaultReplicationHandler.java
15.00% <0.00%> (-3.75%)
:arrow_down:

...er/src/main/java/alluxio/master/job/JobMaster.java
0.00% <0.00%> (-39.16%)
:arrow_down:

.../master/job/JobMasterClientRestServiceHandler.java
0.00% <0.00%> (ø)

...uxio/master/job/JobMasterClientServiceHandler.java
0.00% <0.00%> (ø)

...main/java/alluxio/master/job/plan/PlanTracker.java
0.00% <0.00%> (-67.09%)
:arrow_down:

...a/alluxio/master/job/workflow/WorkflowTracker.java
0.00% <0.00%> (-84.08%)
:arrow_down:

...mon/src/main/java/alluxio/shell/CommandReturn.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 539 more

Continue to review full report at Codecov.

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

@apc999 addressed comment, PTAL.

@apc999 will address any further comments in a separate PR. merging this for now.

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.6 please


Add an option to set TARGET to the oldest supported when DYNAMIC_ARCH is on

I've seen multiple projects (openblas, sagemath, numpy) building openblas hit by
this issue. All these projects now keep a list of oldest TARGET for each platform
and set TARGET when building with DYNAMIC_ARCH.
This is error prone and duplicates work among several projects.
Would it be possible to add an option to set TARGET to the oldest supported
when DYNAMIC_ARCH is on and TARGET is not set?

There is TARGET=GENERIC, do you mean imply it if in DYNAMIC_ARCH?

Ah, didn't realize that we could use TARGET=GENERIC with DYNAMIC_ARCH. Thanks

It is quite recent introduction.... But indeed having it by default would save a lot of duplicate work.

been thinking about that but not sure I want to change established behaviour, i.e. "no target named = use host cpu"

Maybe something like DYNAMIC_ARCH=1 and TARGET=OLDEST would set the target to the oldest. I haven't tried @brada4's suggestion yet, but if that works, then this issue can be closed.

TARGET=GENERIC (plain C code) is expected to work. This has no influence on the choice of BLAS kernels anyway (you will get CORE2 hardcoded as a worst-case fallback on x86_64, and similar for other architectures), but used to determine the compiler options used when compiliing the shared code parts (e.g code from the interface and  drivers directories). This mainly became a problem after the introduction of intrinsics, which led to the addition of more such options like -mavx2 or -msse3.
I think the current version has limited most if not all such options to the actual, cpu-specific kernel files so this should hopefully be a  problem of the past.

Great. Then let's document TARGET=GENERIC in all the places where DYNAMIC_ARCH=1 is documented.

Well, as I wrote this should be a problem of the past.

Ah, sorry about the noise.


Router checking

Devise a way for checking the existence of "@angular/router-deprecated" and "@angular/router".

Is Augury already working with the new router? My router tree is completely empty.

@semeano We have done the changes its still in the dev branch we will be releasing soon with support for new router.

@sumitarora thanks!


✨ httpx

:tada: This PR is included in version 1.0.0-beta.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Mapping problem in keyboard-apu from 48-key to Brazilian 47-key layout

The Apurinã keyboard should have tilde combinations for all vowels and a modifier letter apostrophe to mark glottal stop. In addition we want circumflex, grave, acute and diaereses.
This äëïöüÿ ãẽĩõũỹ àèìòùỳ áéíóúý works on my M2, Sonoma 14.3.1 in Finland, but it does not quite map to the Brazilian Mac Air used by Sidney Facundes, hence a distinction in the names apu_FI and apu_BR.
Note, for example, that the FI-board shows both sides of the square brackets in the QWERTY row, but the BR-board moves the right-hand bracket to the beginning of the next line.
Please, ask for additional information.

The por_BR board looks like this:

Now, there is only one difference observed in the layout.
On the por_BR keyboard tilde requires +shift ( see below).
Otherwise, the keyboard looks right and seems to work right.

Now, there is only one difference observed in the layout.
On the por_BR keyboard tilde requires +shift ( see below).
Otherwise, the keyboard looks right and seems to work right.

This is how it is on the Apple Brazilian keyboard. I want it to be identical with that one, and make sure it works everywhere the correct way before we start to change anything. And from the screen shots, it does not look like shift is required to get tilde.
On the other hand, it seems that the screen shots are not from the latest version that I pushed to GitHub, it contains deadkeys that I removed. Could you make sure that the version of the keyboard package is 0.1.1, not 0.1.0?
Whose computer are the screen shots from? It seems to be a Mac with an ANSI keyboard?

These pictures all come from Sidney's Mac Air.

Unable to generate macos version on own mac.
Have removed and reinstalled giellalt, and cloned
Still get:
"/Users/jackrueter/Dropbox/Github/giellalt/keyboard-apu/apu.kbdgen"
thread 'main' panicked at src/build/macos/generate_macos.rs:486:25:
dead key `"` in target list but not the transforms.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
make: *** [Makefile:604: mac] Error 101

Maybe you haven't pushed everything onto Github.
see also:
Github Bot: Check [Build keyboard: macos-latest - keyboard-apu](https://github.com/giellalt/keyboard-apu/runs/22033224856) completed (failure). ([b8aacd210c4](https://github.com/giellalt/keyboard-apu/commit/b8aacd210c4f77c029493e77e9ca933eab91cf9a))

Github Bot: Check [Build keyboard: windows-latest - keyboard-apu](https://github.com/giellalt/keyboard-apu/runs/22033225532) completed (failure). ([b8aacd210c4](https://github.com/giellalt/keyboard-apu/commit/b8aacd210c4f77c029493e77e9ca933eab91cf9a))

Unable to generate macos version on own mac.

Sorry, my bad. I have fixed it, and also replaced the Sámi flag with the UN flag. New version is 0.1.2, and it has already built successfully for Mac, and is available in Divvun Manager.


Handle local renamed but uncommitted files (git mv).

Accept git status output lines beginning with R in addition to the already accepted prefixes (A, M, D, UU, or ??).
I'm not convinced that the git status after popping is correct. The status is:
local_dir.should have_git_status({:deleted=>["lib/codes.rb"], :added=>["lib/codes2.rb"]})
I would expect:
local_dir.should have_git_status({:renamed=>["lib/codes2.rb"]})

Any feedback on this pull request? I currently have to work around file renames by hand. I prefer to use the official git-smart rather than a locally-modified version.


LDAP configuration stopped working

Hi. Since upgrading to 5.0.0-beta.101 it seems like the LDAP authentication stopped working.
I have validated that all the LDAP files within /run/config/netbox and /run/secrets/netbox/ldap_bind_password are identical to previous version 5.0.0-beta.82.
Unfortunately logging seem to be silent and is not outputting anything related to the failed LDAP login attempts.

Thanks for opening this issue @devasmith.
Let's investigate more this time.

What do you mean exactly by "stopped working"?
When was the last version your configuration worked?
Can you provide your remote auth values?
Do you have access to your LDAP server's log?

Thanks for opening this issue @devasmith. Let's investigate more this time.

What do you mean exactly by "stopped working"?

When authenticating I am prompted for my credentials but when I try to login with correct credentials I receive Please enter a correct username and password. Note that both fields may be case-sensitive..

When was the last version your configuration worked?

netbox-5.0.0-beta.82

Can you provide your remote auth values?

/run/config/netbox/ldap.yml
AUTH_LDAP_SERVER_URI: "ldap://ipa.example.com"
AUTH_LDAP_BIND_DN: "uid=ldap_search,cn=users,cn=accounts,dc=example,dc=com"
AUTH_LDAP_START_TLS: true
LDAP_IGNORE_CERT_ERRORS: false
LDAP_CA_CERT_FILE: /etc/netbox/config/ldap/ldap_ca.crt
AUTH_LDAP_USER_DN_TEMPLATE: uid=%(user)s,cn=users,cn=accounts,dc=example,dc=com
AUTH_LDAP_USER_SEARCH_BASEDN: "cn=users,cn=accounts,dc=example,dc=com"
AUTH_LDAP_USER_SEARCH_ATTR: "sAMAccountName"
AUTH_LDAP_GROUP_SEARCH_BASEDN: "cn=groups,cn=accounts,dc=example,dc=com"
AUTH_LDAP_GROUP_SEARCH_CLASS: "groupOfNames"
AUTH_LDAP_GROUP_TYPE: "GroupOfNamesType"
AUTH_LDAP_REQUIRE_GROUP: "cn=ipausers,cn=groups,cn=accounts,dc=example,dc=com"
AUTH_LDAP_FIND_GROUP_PERMS: true
AUTH_LDAP_MIRROR_GROUPS: true
AUTH_LDAP_MIRROR_GROUPS_EXCEPT: null
AUTH_LDAP_CACHE_TIMEOUT: 3600

Do you have access to your LDAP server's log?

In the logs I see error message that the operation failed due to failed credentials in the slapd access log. (err 49). Unfortunately it doesn't say much more than this.
[23/Sep/2024:08:47:12.406269472 +0200] conn=922230 TLS1.3 128-bit AES-GCM
[23/Sep/2024:08:47:12.406539315 +0200] conn=922230 op=1 BIND dn="uid=foobar,cn=users,cn=accounts,dc=example,dc=com" method=128 version=3
[23/Sep/2024:08:47:12.407446043 +0200] conn=922230 op=1 RESULT err=49 tag=97 nentries=0 wtime=0.005224359 optime=0.000915039 etime=0.006136950
[23/Sep/2024:08:47:12.408967481 +0200] conn=922230 op=2 UNBIND
[23/Sep/2024:08:47:12.408998648 +0200] conn=922230 op=2 fd=388 closed error - U1

Thanks for your detailed answer.
I see your LDAP values are using the former AUTH_LDAP_REQUIRE_GROUP instead of AUTH_LDAP_REQUIRE_GROUP_LIST. I'll try to ensure that former value can still be used, in a PR to come.
Meanwhile, can you try adding the following var to ldap.yml?
# Same value as AUTH_LDAP_REQUIRE_GROUP, but inside an array.
AUTH_LDAP_REQUIRE_GROUP_LIST: [ "cn=ipausers,cn=groups,cn=accounts,dc=example,dc=com" ]

Thanks for your detailed answer.
I see your LDAP values are using the former AUTH_LDAP_REQUIRE_GROUP instead of AUTH_LDAP_REQUIRE_GROUP_LIST. I'm going to ensure this former value can still be used in a PR to come.
Meanwhile, can you try adding the following var to your /run/config/netbox/ldap.yml?
# Same value as AUTH_LDAP_REQUIRE_GROUP, but inside an array.
AUTH_LDAP_REQUIRE_GROUP_LIST: [ "cn=ipausers,cn=groups,cn=accounts,dc=example,dc=com" ]

Hi sorry, I haven't had time to look into this yet. I don't know if I can test this easily as I would need to modify the contents inside the container.

No worries @devasmith.
If it's easier, you can also try the change in #351 as an alternative.

No worries @devasmith. If it's easier, you can also try the change in #351 as an alternative.

I proceeded using the new method using lists instead of strings for those values and that works fine. I don't know if there is a need to backport this.


Lua

What is your question?
How did u make the lua api i wanna make a lua api for a games i will work on so it will be easy to mod so how? And how did you add custom built in functions?

luaJIT stuff thats all i know


folding control still present when setting is changed to mouseover

Testing #191452

Set editor.showFoldingControls to always
Fold and unfold code using toggle on sticky scroll
Set editor.showFoldingControls to mouseover, thus you're no longer mousing over the toggle
🐛 it's still present

Note that if I then mouseover and then leave it, it does disappear after the delay


Inheritance issue with the entity

module API
  module V1
    module Entities
      class A < Grape::Entity
        expose :status

        def status
         'HI'
        end
      end
    end
  end
end

module API
  module V101
    module Entities
      class A < V1::Entities::A
        expose :status

        def status
         'BYE'
        end
      end
    end
  end
end

In this case, when I am calling the V101 it is calling the status function of V1 instead of the V101. This code perfectly works with the grape-entity version - 0.4.8. After version 0.5 >= this code does not behave normally like before. Ami I missing something? Thank you!

What do you mean by does not behave normally? @hay-wtag

@ssa-wtag  This issue is not related to the grape-entity and can thus be closed.  In the original code, there was an explicit call to the parent via another entity which caused this inheritance to fail!