Using DNS Lookup crashes with RES

Steps to produce:

Install Reddit Enchantment Suite
Install IPFS Redirect
Restart FF
Open Reddit and try opening extending some image.
Crash.

I was unable to reproduce. Could you provide a reddit link which triggers the crash for you?

It is not a link, it is action of opening a image (RES adds option to open image without going out of the reddit). DNS entry can't be cached.

Yup, it seems to work for me on random image (https://goo.gl/3yCzSj – IPFS was up and dnslookup active, image opens fine).
Does it work for you? Perhaps the problem is caused by something else?

Any update on this? ;-)

I can't reproduce it not. I will reopen if it happens again.

Just was able to reproduce. It has to be a .gifv, cache can't be populated. Try restarting FF, opening https://www.reddit.com/r/aww/comments/452pcx/our_puppy_wilson_meeting_a_cat_for_the_first_time/ and opening the gifv with RES.

Tried a few times (only two addons installed, fresh profile), works fine for me:

Perhaps there is a clash with other addon due to synchronous dnslink  lookup. Let's wait and see if https://github.com/lidel/ipfs-firefox-addon/issues/69  solves the problem.
Int he meantime, try to get some debug information from Browser Console from the moment of crash (try running in terminal etc).
Does Firefox segfaults?

I am running Windows right now, if I was on Linux I would just gdb it.
Will check.

In console I was able to get:
Assertion failure: !mDoingStableStates, at c:/builds/moz2_slave/rel-m-beta-w32_bld-00000000000/build/xpcom/base/CycleCollectedJSRuntime.cpp:1057

FF45b4

Seems that it is a bug in Firefox itself (HTMLMediaElement)
Someone run into the same problem with NoScript addon:

https://bugzilla.mozilla.org/show_bug.cgi?id=1235183 (as of this moment, still not fixed)

@Kubuxu please update to v1.5.4, perhaps asynchronous lookup helped with this Firefox bug.
If not, I am afraid you need to wait for upstream fix.


Do not include contrib/ in coverage measurements

As per title. Comes from https://github.com/poliastro/poliastro/pull/1451#issuecomment-1018510181 by @jorgepiloto.

Respect Sir,
I'm Siddharaj Yadav a computer engineering undergraduate, Pursuing TE at D Y Patil College under (Pune University).
I am new to open source contribution but I am well aware of Python,Django,HTML and Git& GitHub. I would to contribute to your organization but could you please tell me how to get started? Gsoc
Hoping to hear from you soon
mail-<EMAIL_ADDRESS>


Peer to peer code review

To have a good structure of HTML You should add a Doctype at the top of you document html, here's a link for more information about the importance of adding a DOCTYPE in your html: https://www.w3.org/wiki/Choosing_the_right_doctype_for_your_HTML_documents#:~:text=The doctype is used for,on that later as well).
You did a good design and a good structure of css like naming the class.

👍  Good job!
👉 I think it's better to end a tag in the same line as its content in most of the time.


In HystrixCollapser, only check if request cache is enabled once

NetflixOSS » Hystrix » Hystrix-pull-requests #170 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » Hystrix » Hystrix-pull-requests #172 SUCCESS
This pull request looks good


Smooth reward redemption flow

The Chore
From the reward screen it is slightly janky to pull out your rewards.  Suggest the following.
Tasks

[ ] The from account is not automatically defaulted to VESTED_REWARDS which it should be if you are arriving here from pressing the REDEEM button

Note that there is already a ticket to fix the fact that the selected asset does not change when clicking redeem. It might be worth fixing that here too.

[ ] The text at the top should be a bit more generic ... suggest "Transfer funds to another Vega key or redeem rewards from your vested account to your general account. If you are at all unsure, stop and seek advice."

Discussed in refinement that we'll

Remove all the text from the top
If a key is selected that is not in your wallet, show a warning saying "Are you sure, this cannot be reversed etc"

Additional details / background info

@candida-d based on the changes above, what do you think would be a nice message about the transferring to another key risks

@mattrussell36 I like JR's suggestion above, particularly adding the detail about redeeming. You could save some retail space and write "If you are unsure" instead of "If you are at all unsure", I think the point still stands in either phrasing.
For the risk of transferring to a different key, how about: "This Vega key you're transferring to is not in your wallet. If you proceed, the transfer cannot be reversed."

Bumping this up because in the post-sidebar world this is even jankier than it was.


rvm_shell provider accepts an environment for both user and system-wide installs

I have a system-wide RVM installation and there times when I need to use an rvm-aware shell in a chef recipe, but in the context of a given user's environment (I need to access that user's SSH keys, other things that are found by referencing a HOME and USER environment variable).
Currently, the rvm_shell provider only allows an environment to be specified if:

there is a "user" specified
RVM was installed on a per-user basis

This patch addresses both cases:
A base environment is still applied when in an rvm-per-user context, a specified environment is still merged onto this base.
But, also -- regardless of specifying a "user" or the type of RVM installation used (system-wide vs per-user), if a specified environment is found, we'll use it.
This would fix issue #69

Closing due to inactivity.
If this is still an issue please reopen or open another PR.
Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help!
Thanks,
Sous-Chefs


module system: types.attrsWith { nameType, valueType, ... }?

Project description
Some attribute sets are not allowed to contain any string as attribute name.
This type will add nameType to allow restriction of the names.
It may also add nameConfigPath (represented by the figurative ... in the title) to allow an alternative name for what's currently the _module.args.name config value path. (When reconsidering https://github.com/NixOS/nixpkgs/pull/177576)
I'd suggest this type to be lazy like lazyAttrsOf, or at least make that the default behavior (lazy ? true).
Example:

nixosTest node names must be valid python identifiers
https://github.com/NixOS/nixpkgs/pull/181482
some key-value formats may reject empty names or names with weird characters such as newlines

It is now clear that we really need this.

https://github.com/NixOS/nixpkgs/issues/351888
#97378
related conversations

May be closed by #344216


solving failed: invalid filename when using path to dockerfile

I am used to build an image which Dockerfile is in a subfolder like images/bla/Dockerfile.
This is possible with docker by:
docker build -f images/bla/Dockerfile .
which makes the whole project available as context but still keeps the root directory save.
Doing the same with img results into:
img build -f images/bla/Dockerfile .
solving failed: invalid filename: images/bla/Dockerfile

working on this, thanks :)


The rules matched, but for some reason they were silenced

          If you don't want it silenced, why do you specify realert of 1 hour?

Also, please read #11 and format your messages appropriately. It's difficult to read them without proper formatting.
Originally posted by @jertel in https://github.com/jertel/elastalert2/issues/1484#issuecomment-2205732407

@jertel   And not as you understand, yesterday by execution  bin/elastalert-test-rule  rules/prod.yaml --config config.yaml --alert
Successfully received the alert message. But bin/python3 -m elastalert.elastalert  --config config.yaml --verbose  isn't received the alert message.

Today test again, try to delete elastalert_status_silence doc. Start and Successfully received the alert message.
delete all index elastalert_*  ,Recreate elastalert_* index with bin/elastalert-create-index,  Start and Successfully received the alert message.
So, I don't know exactly what the problem is, but it looks healthy after rebuilding by removing the index at the moment.

Please read #11 and avoid creating issues when requesting support.


[eas-json] Make not recognized image error handler run only if image is present under valid key with invalid value

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
https://github.com/expo/eas-cli/issues/1562
Before this fix, the handler would show the error message if anything is invalid about the image field in the eas-json. We want it only to show the custom error when image is placed in the correct spot but has an invalid value.
How
Run the handler only if image is placed under the proper key.
Test Plan
Test manually.

/changelog-entry bug-fix Make the not recognized image error handler run only if the image is present under a valid key and has an invalid value


D435i how to get left IR image and right IR image

cfg.enable_stream(RS2_STREAM_INFRARED, 1, 1280, 720, RS2_FORMAT_Y8, 30);
cfg.enable_stream(RS2_STREAM_INFRARED, 2, 1280, 720, RS2_FORMAT_Y8, 30);
when I set the config as described above,the function pipe.start(cfg) will report error. this error occur when I use the latest SDK and firmware.

Case closed due to solution achieved and no further comments received.


Update to Spark 2.1.0, Flink 1.2.0, Kafka <IP_ADDRESS>, Redis 3.2.8

Update to Spark 2.1.0, Flink 1.2.0, Kafka <IP_ADDRESS>, Redis 3.2.8.

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:


Address QR code not able to export

Address QR code export option is not there .

There is button to download QR in https://github.com/nemgrouplimited/symbol-desktop-wallet/releases/tag/v0.13.5


Slow to restart for a full-history node

I have a private ripple-network,and have ran for about two years with 5 full-history valiator nodes.
Recently,when I restart a full-history node, it takes so long time to begin work（about 24 hours) and even some nodes will not work(complete_ledgers is always "empty").
Does anybody know why?
Is this a normal phenomenon?
And how can I start a full-history node and let it work quickly.
The debug.log shows below:
2020-Jan-15 03:18:58 LedgerConsensus:WRN Need consensus ledger 1849022A6743A07BD1B5FCC0CAAA539D71718BCDF5F38E63DEE97B26D2E15AC4
2020-Jan-15 03:19:01 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:01 LedgerConsensus:WRN Need consensus ledger B4D6966EBB97337E288692545EC88050A15E42A888C69AFB41A44E42228DF0A4
2020-Jan-15 03:19:04 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:06 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:06 LedgerConsensus:WRN Need consensus ledger 91C933ED19EA3EA5689BA8EF3CDCAB149DBE471D0E0C2EB2AE5001C16AC4F46A
2020-Jan-15 03:19:08 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:08 LedgerConsensus:WRN Need consensus ledger 210E563AF58EDDB6B5F7733DC59157F36C66B86100CC8CA94AA5D2CBABDEEDAB
2020-Jan-15 03:19:11 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:11 LedgerConsensus:WRN Need consensus ledger 0BD9D507F881900FC4BF23D8EC6989D330DD07DBBD54B76F88658F354C64E083
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 80679ms wait: 85801ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17576ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17575ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17575ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17573ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17568ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17568ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17568ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17567ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17567ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17566ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17566ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17563ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17560ms
2020-Jan-15 03:19:13 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 17559ms
2020-Jan-15 03:19:14 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:14 LedgerConsensus:WRN Need consensus ledger 8CEC221976D93011926B636B0538A5B7A9549EA2984D8AED07374F5946739DAB
2020-Jan-15 03:19:18 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:18 LedgerConsensus:WRN Need consensus ledger 206A5B7D2639CB1034B54871C238F486DD791DE99D27A9B028B97C8DE3BB8E06
2020-Jan-15 03:19:21 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:21 LedgerConsensus:WRN Need consensus ledger 8D0B1B78280BA710EB69EB38C9FBF43EC07EA1CD7B64D59C135DF88993C12B3E
2020-Jan-15 03:19:24 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:24 LedgerConsensus:WRN Need consensus ledger C49E82173C569742599B7C10D28D5CA15538C9CF85E1BFB236FDDDAB86650BBD
2020-Jan-15 03:19:27 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:27 LedgerConsensus:WRN Need consensus ledger F1C6F5ECCE3B45FA768EEC4E1EB3D2B2FBCFA897703E3A0E2961684EF161705E
2020-Jan-15 03:19:30 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:30 LedgerConsensus:WRN Need consensus ledger 1D60FB534AC13B74FF6332BDF94DC62E97E4C5FD7BD59B30B708BE07633F94BD
2020-Jan-15 03:19:33 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:33 LedgerConsensus:WRN Need consensus ledger E4C1774DB5B8B5BA3162EDF35EF83153483D27AF9516ACD545AE06FBB7915222
2020-Jan-15 03:19:36 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:38 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:38 LedgerConsensus:WRN Need consensus ledger 333FCB2A965235A0DFFD0A0DE807EBE2E1CD3C0F458BD43DDF2515AC166F32B5
2020-Jan-15 03:19:40 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:40 LedgerConsensus:WRN Need consensus ledger 9AA97CFABFF62E722C78D2DFFC7AB5711FC493F0D14014F51F859FBDDDB127B6
2020-Jan-15 03:19:43 NetworkOPs:WRN We are not running on the consensus ledger
2020-Jan-15 03:19:43 LedgerConsensus:WRN Need consensus ledger FE362B0ECFAC6DD679EEDF6580E66307C6AEF9198672A918D3E518744C6F44E5

@nbougalis I have my ripple full history nodes starting up forever after restart. I notices that it took 40 min for one of my node to start after upgrade, and it takes about 30 hours for 2 others. Is there any way to see if they indeed do house-keeping or they are stuck? Some cli commands, or api calls maybe? Will appreciate a link to any guide/article describing this first start after upgrade procedures

@ksemaev If you are using version 1.40, please read the following upgrade advisory. https://xrpl.org/blog/2020/rippled-1.4.0-upgrade-advisory.html

Closing due to inactivity. If the issue persists, please open a new issue.


[Pokemon Tabletop Adventures v3] Refactors skill talents

Changes / Comments

Changes the header of the talent checkboxes to Talent to make it easier for users to identify their purpose
Sets the value of each checkbox to 2 to eliminate the need to select talent in a particular order
Updates the skill total sheet workers to add the extra +1 if both checkboxes are on
Updates the skill total sheet workers to encapsulate some repeated code into a function to make the scripts section neater
Updates sheet workers to react to attribute mods, which ensures attribute changes have time to propagate to the mod before being used
Updates the README

Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[x] Does this add or change functional aesthetics (such as layout or color scheme)?

Hello @mrianmerry your PR has some conflicts within PTA3.html and the Readme files. Could you rebase from master and fix those issue? Thanks!

@mperes thanks! Got that sorted.
Out of interest, do you know why I have three files in the Aventures folder that show as modified after I pulled in the upstream master branch to my local master? It makes it particularly cumbersome to work with...

Out of interest, do you know why I have three files in the Aventures folder that show as modified after I pulled in the upstream master branch to my local master? It makes it particularly cumbersome to work with...

Did that appear to you like if you had uncommited changes after you pulled from upstream master? I've encountered it a couple of times as well and not sure exactly what causes it. So far have I've usually resolved it by creating a temporary branch, saving and committing the unstaged changes there, and and then deleting the temporary branch.

@mrianmerry, working with forks sometimes is not as straight forward as we would like it to be. Not sure how comfy you are with terminal, so here is a link to explain how to perform it via UI: https://stackoverflow.com/questions/20984802/how-can-i-keep-my-fork-in-sync-without-adding-a-separate-remote/21131381#21131381
Once your fork is synced, you can rebase you branch against your own master. Hope that helps.

Ahh yeah, I usually use git from the terminal anyway (I use GUI clients mostly for when I have larger diffs).
I'll give @Anduh's solution a go, and, hopefully, the issues will all go away.


Validate fortigate GC-CAP/GC-TIP architecture - dual LB sandwich or VDOM config

see https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/issues/45
Fortinet Fortigate config
The guidance on the KCC LZ project is that we use a single cluster (3 VMs tbd) for both gc-cap and gc-tip and use flow separation or the existing LB sandwich architecture and 2 clusters of 2VMs for CAP/TIP separation.
See TF PBMM LZ https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/issues/45
Verify the config and shadow deployment of a VDOM fortigate configaration - thanks Dave (triple fortigate zone for example)
https://docs.fortinet.com/document/fortigate/6.0.0/cookbook/154890/vdom-configuration

https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/dev/solutions/landing-zone/architecture.md#di-24-validate-vdom---virtual-domain-fortigate-zone-isolation
notes

https://cloud.google.com/architecture?category=networking&text=appliance to https://cloud.google.com/architecture/deploying-nat-gateways-in-a-hub-and-spoke-architecture-using-vpc-network-peering-and-routing?hl=en

Thanks Dave for the heads up on the example LB HA master/slave repo
Fortigate HA LB active/standby up (both vms)- but issues with payg instead of byod license being worked out
Example project contains the entire stack including 4 VPCs for the fortigates and 2 for the public and private perimeters - hence a compute-networks quota request is required to move from 5 to 6 VPCs (you can delete the default VPC)
https://github.com/fortinet/fortigate-tutorial-gcp/issues/1

na-ne1 deployment

https://github.com/fortinet/fortigate-tutorial-gcp/blob/main/docs/architecture-reference.md
Update: using BYOL for now - thank you Fortinet as usual
I will look at marketplace roles later
login change must be done within 10 sec
All good on the gcloud deployment - thank you team
fgt-vm-nanortheast1-b #
=======================================
# Next step:
# - run tutorial-test.sh to verify everything works
michael@cloudshell:~/github/fortigate-tutorial-gcp/gcloud (fortigate-tutorial-gcp-lgz5)$ ./tutorial-test.sh
------------------------------------------------------------------------------------
# This script will run a series of tests to verify if your deployment works correctly.
# With each test you will see information about the expected output - verify if it's
# matching what is returned by the test commands.
------------------------------------------------------------------------------------

-----------------------------------------------------------
##  TEST: FGT HA clustering and licensing
##  Expected output: primary and secondary reported with proper hostnames and non-empty serial numbers
fgt-vm-nanortheast1-b # HA Health Status: OK
Primary     : fgt-vm-nanortheast1-b, FGVM08TM22004699, HA cluster index = 1
Secondary   : fgt-vm-nanortheast1-c, FGVM08TM22004700, HA cluster index = 0
fgt-vm-nanortheast1-b #
-----------------------------------------------------------
##  TEST: ELB health
##  Expected output: one healthy, one unhealthy backend
{
  "ipAddress": "<IP_ADDRESS>",
  "healthState": "HEALTHY"
}
{
  "ipAddress": "<IP_ADDRESS>",
  "healthState": "UNHEALTHY"
}
-----------------------------------------------------------
##  TEST: ILB trusted health
##  Expected output: one healthy, one unhealthy backend
{
  "ipAddress": "<IP_ADDRESS>",
  "healthState": "HEALTHY"
}
{
  "ipAddress": "<IP_ADDRESS>",
  "healthState": "UNHEALTHY"
}
-----------------------------------------------------------
##  TEST: peering routes for wrkld-tier1
##  Expected output: STATIC_PEERING_ROUTE to <IP_ADDRESS> is listed as accepted
DEST_RANGE: <IP_ADDRESS>/24
TYPE: SUBNET_PEERING_ROUTE
NEXT_HOP_REGION: northamerica-northeast1
PRIORITY: 0
STATUS: accepted

DEST_RANGE: <IP_ADDRESS>/0
TYPE: STATIC_PEERING_ROUTE
NEXT_HOP_REGION: northamerica-northeast1
PRIORITY: 1000
STATUS: accepted
-----------------------------------------------------------
##  TEST: peering routes for wrkld-tier2
##  Expected output: STATIC_PEERING_ROUTE to <IP_ADDRESS> is listed as accepted
DEST_RANGE: <IP_ADDRESS>/24
TYPE: SUBNET_PEERING_ROUTE
NEXT_HOP_REGION: northamerica-northeast1
PRIORITY: 0
STATUS: accepted

DEST_RANGE: <IP_ADDRESS>/0
TYPE: STATIC_PEERING_ROUTE
NEXT_HOP_REGION: northamerica-northeast1
PRIORITY: 1000
STATUS: accepted
-----------------------------------------------------------
##  TEST: website working
##  Expected output: HTTP 200 OK headers from nginx server
HTTP/1.1 200 OK
Server: nginx/1.18.0
Date: Tue, 01 Nov 2022 13:38:31 GMT
Content-Type: text/html
Content-Length: 612
Connection: keep-alive
Last-Modified: Tue, 01 Nov 2022 13:36:31 GMT
ETag: "636120df-264"
Accept-Ranges: bytes

-----------------------------------------------------------
##  TEST: website protected
##  Expected output: information about blocked access to EICAR_TEST_FILE virus
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4810  100  4810    0     0  84385      0 --:--:-- --:--:-- --:--:-- 84385

High Security Alert

You are not permitted to download the file "eicar.com" because it is infected with the virus "EICAR_TEST_FILE".

========================================
# Next step:
# - open http://35....3 to open protected web page
# - open https://35..3 to explore your FortiGate
# - run tutorial-delete.sh to clean up
michael@cloudshell:~/github/fortigate-tutorial-gcp/gcloud (fortigate-tutorial-gcp-lgz5)$ ^C

tracking add kcc version of fortigate-tutorial-gcp (collaboration PR) https://github.com/fortinet/fortigate-tutorial-gcp/issues/5

20221130: LZ office hours meet questions
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/dev/solutions/landing-zone/architecture.md#fortigate-multitenant-architecture

Fortigate HA cluster sharing or independence across orgs

Fortigate cluster per Multitenant LZ

Performance for different machine types e2-standard-4 to 32 in terms of processing but also up to 50Gpbs throughput
25 peering limit workarounds shared/standard workload VPCs to each perimeter VPC

how VPNs would limit bandwidth


Support "cargo binstall"

As a user of proa, I want to use cargo binstall to install proa quickly, so that my container images build quickly.
AC:

Support cargo binstall or similar.

Can just use published releases as an alternative.


sigma argument as a function of observation and parameters- for scipy.optimize.curve_fit

Suppose that one wants to minimize the weighted least squares function:
$\sum \frac{y_i-f(x_i,\theta)^2}{\sigma_i^2} $ .
np.sum( (y-f(x,*params) / sigma)**2)
If the dataset comes from, e.g., Poisson distributions (centered at the "true" values), it is possible to make as an approximation the substitution $\sigma_i^2=y_i$ (sigma=np.sqrt(y)).
However, another choice could be made by making the substitution $\sigma_i^2=f(x_i,\theta)$ (sigma=f(x,*params)) (see for example G. Cowan, Statistical Data Analysis, paragraph 7.4).
Can curve_fit or generally the Levenberg-Marquardt algorithm handle this situation?
Sorry for the Latex-style writing of expressions, I am new and I don't know how to write them.

You can do it by faking y = zeros, but it might not solve the optimization problem that you want, see below.
statsmodels has Poisson model that estimates parameters by maximum likelihood. I had an example open in a notebook.
(Poisson uses exp mean function to impose positive Poisson mean)
def fun(data, *params):
    y = data[:, 0]
    x = data[:, 1:]
    m = np.exp(x @ params)
    return (y - m) / np.sqrt(m)

optimize.curve_fit(fun, np.column_stack((y,exog)), np.zeros(len(y)), respoi.params)
(array([1.14423838, 2.0634058 ]), ...

with leastsquares
x = exog

def fun2(params):
    m = np.exp(x @ params)
    return (y - m) / np.sqrt(m)

res_nl = optimize.least_squares(fun2, respoi.params)
res_nl.x
array([1.14423838, 2.0634058 ])

However, this does not estimate a poisson model.
If weights are also a function of the parameters in the optimization, then the first order conditions for the optimization are not the same as for Poisson maximum likelihood.
For fixed sigma2 that corresponds to the Poisson MLE
m2 = respoi.predict()  # results from statsmodels Poisson

def fun2(params):
    m = np.exp(x @ params)
    return (y - m) / np.sqrt(m2)

res_nl = optimize.least_squares(fun2, respoi.params)
res_nl.x
array([0.99325177, 1.99786989])

respoi.params
array([0.99325177, 1.99786989])

related aside
iteratively reweighted least-squares IRLS is a default method for Poisson and similar generalized linear models.
IRLS iterates over weighted least squares estimate, where the least squares estimates take weights as fixed and the outer iterations update weights.
In standard IRLS, we can use linear least squares inside the iteration loop.

It looks to me like this was a question, and it has been answered. Please re-open if there is an associated feature request.


feat: added pick many distinct

Added Feature Pick Many Distinct

Has capability to pick many but distinct
If amount of items needed is more than the length of array or equal to it returns all items

closes #2

@Balastrong requesting for your review

Thank you for the PR!
I'll have a look at the code in the evening. In the meantime, I see the build failed because the code is not formatted, you can run npm run format and commit again, should be enough :)

Hi seems like no change when running npm run format

Ah, you're right, I created #15 to fix it.
You're on windows, right? You can try with npx prettier --write 'src\\**\\*.{js,jsx,ts,tsx,json,css,scss,md}'

@Balastrong done formatting

Codecov Report
Base: 100.00% // Head: 98.79% // Decreases project coverage by -1.20% :warning:

Coverage data is based on head (a74b270) compared to base (cadc428).
Patch coverage: 95.45% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##              main      #14      +/-   ##
===========================================
- Coverage   100.00%   98.79%   -1.21%
===========================================
  Files            2        2
  Lines           61       83      +22
  Branches         8       12       +4
===========================================
+ Hits            61       82      +21
- Misses           0        1       +1

Impacted Files
Coverage Δ

src/randomPicker.ts
98.57% <95.00%> (-1.43%)
:arrow_down:

src/index.ts
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@Balastrong updated code with changes requested and added additional test. I am not sure about the code coverage part, that's something new to me. Below is the result of test run


Pipeline support for multiple environments

As a developer I want AWS environments parameterized So That a given PR is deployed to the intended environment.
Additional Context

Currently (post FAM#51) the AWS environment (dev/test/prod) being deployed to is hardcoded to 'dev'

Acceptance Criteria

[ ] Given a PR, When the branch is merged to TEST/PROD, then the PR is deployed to TEST/PROD
[ ] Avoid duplication of code (probably need to introduce Terragrunt on this ticket)

Definition of Done

[ ] Ready to Demo in Sprint Review
[ ] Documentation and/or scientific documentation exists and can be found
[ ] Peer Reviewed by 2 people on the team
[ ] Manual testing of all PRs in Dev and Prod
[ ] Merged

There are many ways to accomplish this; design/spike needed to sort this out  - and Derek!

@ConradBoydElliottGustafson - does this issue duplicate #233?

Closed a duplicate of #233


fix: add go.clear-output-folder flag

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/check-enforcer override


make pipeline more efficient

https://www.bswanson.dev/blog/optimizing-azure-static-web-apps-builds-github-actions-caching/


change library name

hi!
i shortened my library name from "MaquinitasParameters" to "MaquinitasParams"
to comply with the Arduino linting,
i already did the update and new version on my repo,
and i am quoting this issue on a PR reflecting that change on this repo, thanks!

@per1234 backend maintenance operations are done


External access

Please, how i can access from external url to dashboard? I use  docker installation and cloudflare domain. If i set a second level url like hafusion.myhome.org redirect to myinternalip:5050 i have mixed content problem and no script was loaded. I not find how to access to dashboard throught my homeassistant installation.

For clarification - I am also new to this ingress stuff.
The url shouldn't be localip:5050. It should rather be your home Assistant up:8123/{ha-fusion-hostname}/...
So if you already exposing your HA then just add the ha-fusion path..


Need change "-" to "_"

Hi There,
Would you please change the "-" to "_" in the website:
import 'package:iconify_flutter/iconify_flutter.dart';
import 'package:iconify_flutter/icons/carbon.dart';

Iconify(Carbon.chart-multi-line) // widget

The correct one should be:
Iconify(Carbon.chart_multi_line) // widget
Thank you.

just solved
but waiting for github actions to deploy the website

@kevinxxq can you try it now pls

Thank you. It is correct now.

Thank you. Some of them still need be changed: Iconify(Carbon.settings-check) // widget
Thank you.

Thank you. Some of them still need be changed: Iconify(Carbon.settings-check) // widget
Thank you.

Pleas

Thank you. Some of them still need be changed: Iconify(Carbon.settings-check) // widget
Thank you.

Please try again

Hi Andrew,
I am very sorry. Now I checked it and works very good.
Thank you.


Does group membership actually govern the application access?

Hi all,
The option with 'To which group should assigned users be added?' does this actually govern the access to application, or is it meant more like just a inventory thing? i.e. if a user is removed as a member of the group, do they also lose the access to the application? Or is this a separate action needed to be performed?
Regards,

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

ID: 580e9e5d-4685-f5d0-b272-97035861d97e
Version Independent ID: 23e3c30a-e4e7-4387-2709-5979a415842d
Content: How to configure self-service application assignment
Content Source: articles/active-directory/manage-apps/manage-self-service-access.md
Service: active-directory
Sub-service: app-mgmt
GitHub Login: @kenwith
Microsoft Alias: kenwith

@xNiklasJern
Thanks for your feedback! We will investigate and update as appropriate.

@xNiklasJern
When it comes to self-service application assignment, this is solely used so users can self-discover applications from their My Apps without bothering the IT group. By enabling this feature, users (once requested access has been approved) are added to a pre-configured group so you can see who has requested access, remove access, and manage the roles assigned to them.
From my understanding, the group is primarily used for management purposes, since you can manage users once they're added to the group. However, if a user is removed, they'll need to request access in order to gain access to the application.
I hope this helps! If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.

Thanks @JamesTran-MSFT , this answered my question


Update  spec.md with gRPC definitions

ping @jeffvance @wlan0

Is the idea to replace the gRPC section of the official KEP with this pr?

Target audience: driver author


Remove api_gateway policy from template creation

The PR #1903 attempted to fix issue #1747, however, the
travis build failed because at the time botocore, required
a version of docutils >= 0.10 and <0.15. botocore has
since changed the requirements to docutils>=0.10,<0.16. So
This should fix the build issue for the PR to address #1747.

Description
Removed policy from template creation. This fix was attempted in PR #1903, but failed because of botocore requirements for docutils at the time.
GitHub Issues
#1747

Coverage decreased (-43.9%) to 29.34% when pulling b82247209f47f5f3f101a0ee859fd87a44d56392 on aabdullah-bos:remove_policy_from_template into 60fbb55fffa762a85e79e756f2a1373832d78320 on Miserlou:master.

@Miserlou So all this is a simple change and all of the build jobs passed except for one, Python: 3.6 amd64 TESTCASE=tests/tests_docs.py. Two questions:

What's the procedure re-running the build?
I made a one line change which should not have affected the code coverage yet, there appears to be a decrease in code coverage. Is this because of the test failure?


Third attempt at refactoring garbage collector

The condition for requesting collections is replaced by requesting a collection
if an allocation passes a tripwire. This tripwire is initially set at MIN_SPACE
and is recalculated after each garbage collation as max(MIN_SPACE, |live data|).

Furthermore, garbage collections are only trigged by allocations in youngspace.
Allocations in oldspace no longer trigger collections since oldspace collections
are handled during a youngspace collection.
Allocations in alwaysgcspace no longer trigger collections since collection
of this space is handled outside of the main garbage collector.
Some class arena member functions have the arena_ component removed as superfluous.

This code tries to make collections happen more frequently when the live memory shrinks in order to improve cache performance of the garbage collector. It would be helpful before we merge this to see data about gc throughput to determine whether we see any regression that might be caused by the data not bearing out that assumption.

Actually I got the formula wrong in the description - the tripwire is set to max(MIN_SPACE, EXPAND_FACTOR * |live data|). I set EXPAND_FACTOR = 2 but this could well be too low - I don't think you'd want to go any lower. An alternative would be to track the largest value of |live data| seen in collections to date and multiply this by EXPAND_FACTOR.


Add mpsc::channel usage examples to the tutorial and/or docs

I found no examples of futures::sync::mpsc::channel usage in the tutorial and in the docs.

I think this is covered by https://tokio.rs/docs/going-deeper/synchronization/ now, so closing.


Segmentation fault on iojs 3.2, Mac OS X

Hi,
all works fine up to version 3.1 - but with 3.2 I get:
Segmentation fault: 11

Stefan

Is there any stacktrace?

Just looked into it. It was not caused by gc-stats. It was another native module.
Sorry.


[Vmware/NGC] Unmount operation shows error in vsphere UI even though it is success.

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
unmount operation from NGC plugin shows "some error occured"

but the unmount operation is SUCCESS from openSDS
What you expected to happen:
Do not show error message when the backend operation is sussess.
How to reproduce it (as minimally and precisely as possible):
create blockstorage from plugin.
use unmount from plugin
Anything else we need to know?:
NA
Environment:

NBP version:v0.6.1
OS (e.g. from /etc/os-release):Windows
Kernel (e.g. uname -a):
Install tools:
Others:

Not blocking any operations now. need to move post daito

fixed with #352


There was 1 error after running phpunit

phpunit output:

...
There was 1 error:

tests\web\admin\models\StroageFileTest::testCrud
yii\db\Exception: SQLSTATE[HY000]: General error: 1364 Field 'passthrough_file_password' doesn't have a default value
The SQL being executed was: INSERT INTO admin_storage_file (name_original, name_new, mime_type, name_new_compound, extension, hash_file, hash_name, folder_id, upload_timestamp, file_size, upload_ user_id) VALUES ('0', '1', '2', '3', '4', '5', '6', 7,<PHONE_NUMBER>, 9, 10)
...

Could please provide more informations? Have you run the tests as described:

Create Database (example luya_phpunit)
Insert Database dump from tests/sql/1.0.0-beta5.sql
Rename phpunit.xml.dist to phpunit.xml
Change dsn, username and passwort in phpunit.xml
Ensure you have installed current composer packages composer install.
Execute the phpunit bin file ./vendor/bin/phpunit.

in your LUYA fork? Version?

I have done all the 6 steps in Unit Tests from README.md.
And I used git clone to get Luya, and imported database from tests/sql/1.0.0-beta5.sql.
Maybe the 1.0.0-beta5.sql is not suit for luya's current version 1.0.0-beta6?

@squirrelm i just checked a few things:

passthrough_file_password is not in use yet, this will be used to procted files by a password soon.
in the migration its declared as NOT NULL (which makes no sense in this context).

What version of MYSQL do you have? This could be a problem cause of mysql strict mode, but i am not sure yet.
could you just try to remove the NOT NULL "flag" attribute in your database (in phpmyadmin for example) where your run the LUYA tests, just to be sure.

My MySQL version is 5.7.10, for Win64 on x86_64.
And i just done a test after removing NOT NULL attribute from column passthrough_file_password, all of the tests was passed.

I just added a beta6 sql file without the NOT NULL statement and also fixed the issue in the migration file. Thank you for the report.

you're welcome.


Fix labels on manifests

I noticed there were 4 resources in the mixer chart that don't have the standard labels. (This breaks some of our process.) This PR adds the missing labels.
I also noticed the main istio chart uses the old style chart label of istio-1.1.0 instead of the new istio label. This PR updates the helper to match the others.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: dwradcliffe
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ostromart
If they are not already assigned, you can assign the PR to them by writing /assign @ostromart in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @dwradcliffe. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@dwradcliffe those labels were intentionally removed in a prior PR.  Labels are very expensive, and they were added for what reason we don't know to 1.1, so were removed.
Could you explain how the missing lables break your workflow?
Thanks again for the contribution :)
Cheers
-steve

Ah, interesting. Is there a reason just these few were removed and the 100+ others are still there?
We don't use Helm, and we have a process to generate the yaml from the helm templates. I'm using the labels (specifically chart) to sort the resources into different yaml files for easier review. These were the only resources that broke that workflow.

@dwradcliffe: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sdake Any update here? Would be nice to get these cleaned up for the final 1.1 release.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: dwradcliffe
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ostromart
If they are not already assigned, you can assign the PR to them by writing /assign @ostromart in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Ah, interesting. Is there a reason just these few were removed and the 100+ others are still there?
We don't use Helm, and we have a process to generate the yaml from the helm templates. I'm using the labels (specifically chart) to sort the resources into different yaml files for easier review. These were the only resources that broke that workflow.

@dwradcliffe - apologies for lag - this fell off my radar inadvertently.  Upgrade will not work if these are removed.  They’ve should have never been added in the first place, but once they were in (in 1.0) - they caused 1.1 to break in an upgrade scenario.
We are resolving this mess of annotations in 1.2 with new installer tech that permits a blue/green deployment of Istio.
Cheers
-steve

Upgrade will not work if these are removed.

I’m adding labels here to make them consistent.

The fundamental issue as I recall is that:

labels are immutable in a manifest
labels are expensive in etcd

Here is @costinm's attempt to remove added labels added to 1.0 prior to 1.1 release:
https://github.com/istio/istio/pull/12240.
Re your workflow and the usage of chart for sorting, I will manually test this PR now and if does not break upgrades (i.e. from 1.1.2 to 1.1.3) I'll mergge it.  Longer term would you consider the app: label as the helm labels will not be carried into the next generation installer.  The labels should not be considered an API.
Cheers
-steve

after applying your diff, the following happens:
sdake@beast-01:~/istio-1.1.0-dwradcliffe$ kubectl get pods -n istio-system
NAME                                      READY   STATUS      RESTARTS   AGE
grafana-57586c685b-p4rzs                  1/1     Running     0          11m
istio-citadel-645ffc4999-rsf2w            1/1     Running     0          11m
istio-cleanup-secrets-1.1.0-fpnf7         0/1     Completed   0          11m
istio-egressgateway-5c7fd57fdb-cqnhl      1/1     Running     0          11m
istio-galley-978f9447f-gnlrp              1/1     Running     0          11m
istio-grafana-post-install-1.1.0-lp6dj    0/1     Completed   0          11m
istio-ingressgateway-8ccdc79bc-25mw4      1/1     Running     0          11m
istio-init-crd-10-nrcmt                   0/1     Completed   0          12m
istio-init-crd-11-sbthj                   0/1     Completed   0          12m
istio-pilot-679c6b45b8-6mbkm              2/2     Running     0          11m
istio-policy-fccd56fd-6qpl9               2/2     Running     2          11m
istio-security-post-install-1.1.0-tw2gc   0/1     Completed   0          11m
istio-sidecar-injector-6dcc9d5c64-x4f47   1/1     Running     0          11m
istio-telemetry-9bcfc78bd-vpswt           2/2     Running     2          11m
istio-tracing-656f9fc99c-qlbzz            1/1     Running     0          11m
kiali-69d6978b45-2ldpr                    1/1     Running     0          11m
prometheus-66c9f5694-zn27n                1/1     Running     0          11m

/lgtm
/approve
@duderino As the PR improves consistency and the current labels in the charts are a mess and were not repaired priorr to 1.1, I'd reecommend a merge to release-1.1.  With the next gen installer we will need to take greater care on label usage.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dwradcliffe, sdake
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [sdake]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dwradcliffe: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
3b8c9a77512363a50b8c508c1fd2cc7cf45119a3
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@dwradcliffe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
3b8c9a77512363a50b8c508c1fd2cc7cf45119a3
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
3b8c9a77512363a50b8c508c1fd2cc7cf45119a3
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@dwradcliffe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
3b8c9a77512363a50b8c508c1fd2cc7cf45119a3
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
3b8c9a77512363a50b8c508c1fd2cc7cf45119a3
link
/test istio-pilot-multicluster-e2e

prow/e2e_pilotv2_auth_sds.sh
3b8c9a77512363a50b8c508c1fd2cc7cf45119a3
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio_auth_sds_e2e

/ok-to-test

@dwradcliffe: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
3b8c9a77512363a50b8c508c1fd2cc7cf45119a3
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

The labels only cause update issues with the old deployments app, apps/v1 handles them fine I believe, and we are migrating to apps/v1.
I have never heard of labels being expensive, any source for that?
/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dwradcliffe, howardjohn, sdake
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [sdake]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sdake @wenchenglu there's enough stuff going into 1.1.3 already that I'm a bit hesitate to merge this, but if @sdake think it's OK then I think we should merge it next week for 1.1.4

The labels only cause update issues with the old deployments app, apps/v1 handles them fine I believe, and we are migrating to apps/v1.
I have never heard of labels being expensive, any source for that?
/lgtm

@costinm had indicated that - but other than that I have no source.

@duderino 1.1.4 is fine.  I personally tested this change outside of CI, as our upgrade CI test cases can't be trusted.
This causes some pain for some folks that have custom workflows around our helm charts.

/test istio-pilot-multicluster-e2e

@dwradcliffe: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
3b8c9a77512363a50b8c508c1fd2cc7cf45119a3
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


modularize cohortfinder

Modularize cohortfinder by relocating the main algorithm into the method runCohortFinder()
Change the behavior of cohortFinder's CLI and output structure.
-- CF takes the positional argument histoqcdir instead of the optional argument histoqctsv.
-- CF uses histoqcdir to automatically locate the results.tsv file (assumes 1 results.tsv file per histoqc output directory).
-- CF writes all output to histoqcdir by default, unless the users specifies the optional --outdir (-o) argument.
Update readme to reflect the above changes.
General formatting upkeep and additional comments.

CohortFinder can now be run with:
python3 -m cohortfinder --help

Will need to update the readme to reflect new module behavior. @FanFAN0703 let's discuss the readme update together.


Feat/configurable check name

TODO:

[x] Write new tests or update the old ones to cover new functionality.
[x] Update doc-strings where appropriate.
[x] Update or write new documentation in packit/packit.dev.
[ ] [FIXME]: retriggering via GitHub re-run BROKEN

Fixes
Related to
Merge before/after

RELEASE NOTES BEGIN
Packit now supports automatic ordering of ☕ after all checks pass.
RELEASE NOTES END

I wonder if it wouldn't be better/safer to use template strings, what do you think?


[Request deployment] New Cluster: projectpythia.2i2c.cloud

Phase 1: Account setup (READY)
This is applicable for cases where this is a dedicated cluster. The following table lists the information before this phase can start.

Question
Answer

Cloud Provider
AWS

Will 2i2c pay for cloud costs and recover them via invoice?
No

AWS Account ID
590183926898

Target Start Date
2024-05-15

Community Representatives
@jmunroe

Technical Contacts added to Airtable?
Yes

Docs at https://infrastructure.2i2c.org/hub-deployment-guide/cloud-accounts/
Procedure: https://infrastructure.2i2c.org/hub-deployment-guide/runbooks/phase1/aws-external-account/
@jmunroe is the account owner and can create
Phase 2: Cluster setup (READY)
This assumes all engineers have access to this new account, and will be able to set up the cluster + support, without any new hubs being set up.

Question
Answer

Region / Zone of the cluster
us-west-2

Name of cluster
projectpythia

Is GPU required?
Yes

Docs at https://infrastructure.2i2c.org/hub-deployment-guide/new-cluster/new-cluster/
and https://infrastructure.2i2c.org/hub-deployment-guide/deploy-support/configure-support/

This can be delay in favour of the catalyst hubs. @jmunroe shared that perspective on slack.

Phase 1 and Phase 2 are currently ready, but they need to be split into separate tickets. @jmunroe will split this before the planning meeting. This has lower priority than the 4 catalyst requets

2024-05-09. @jmunroe points that this is an example of a cross-team dependency. This is completed on the operations board but not closed.


Add cache for player heads

Add a temp cache ( 7 days ?) for players head.

I will look into this. Please review the latest update for recent API and head/skull changes.

Nice change about heads, but so long to load, that's why you need to add a cache for this ^^

I understand. I will look into a similar concept when I get a chance.

I probably won't be adding complete support for skulls at this time, as I'm having trouble finding a reliable API. You can look at the other issue you created for more information.
#35


[11.x] create Laravel internal components

most Blade tags are just PHP logic, and make sense as Blade. however, some of them are outputting full blocks of HTML, and feel more like components.
this creates a new set of Laravel internal components, which makes it easier to override values, and append additional attributes.
my original motivation was to try and solve the problem of being able to append attributes to [Vite tags]](#53429), but clearly that is a much more complicated issue that I originally thought.
I'll admit I have low hopes for this, but I figured I'd throw it up here anyway to see if it sparks any ideas for anyone where this feature would be more impactful.

Isnt there quite some overhead for using components with such small html snippets? I have been using manual helper functions like new HtmlString('...'.e($someVar)) for years when the snippet is either very tiny or it occurs a lot of times.

Isnt there quite some overhead for using components with such small html snippets? I have been using manual helper functions like new HtmlString('...'.e($someVar)) for years when the snippet is either very tiny or it occurs a lot of times.

I wouldn't think so, but I'm not sure. Good question.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!


CoxPH Cross validation raise delta nan values while fit don't

I'm using a dataset contaning no missing values, the following code return False :
np.any(np.isnan(survival_df_inline))

The normal call to the fit function works just fine ( tried with and without penalizer ) :
from lifelines import CoxPHFitter
cph = CoxPHFitter(penalizer=10)
cph.fit(survival_df_inline, duration_col='duration', event_col='observed',show_progress=True)

it return the following with a concordance of 0.823 :
Iteration 1: norm_delta = 1.62941, step_size = 0.95000, ll = -6270.72988, seconds_since_start = 0.1
Iteration 2: norm_delta = 6.71986, step_size = 0.95000, ll = -8373.19389, seconds_since_start = 0.2
Iteration 3: norm_delta = 40.81242, step_size = 0.71250, ll = -14545.39092, seconds_since_start = 0.2
Iteration 4: norm_delta = 95.62474, step_size = 0.20947, ll = -142580.12076, seconds_since_start = 0.3
Iteration 5: norm_delta = 62.79576, step_size = 0.06159, ll = -125745.30013, seconds_since_start = 0.3
Iteration 6: norm_delta = 10.84011, step_size = 0.01811, ll = -177715.85727, seconds_since_start = 0.4
Iteration 7: norm_delta = 8.29702, step_size = 0.01955, ll = -113763.80804, seconds_since_start = 0.5
Iteration 8: norm_delta = 5.95707, step_size = 0.02112, ll = -83896.59499, seconds_since_start = 0.5
Iteration 9: norm_delta = 4.19774, step_size = 0.02281, ll = -70525.86880, seconds_since_start = 0.6
Iteration 10: norm_delta = 5.71564, step_size = 0.03284, ll = -65067.11859, seconds_since_start = 0.7
Iteration 11: norm_delta = 4.78023, step_size = 0.02897, ll = -57929.07073, seconds_since_start = 0.7
Iteration 12: norm_delta = 5.38390, step_size = 0.03407, ll = -52282.84271, seconds_since_start = 0.8
Iteration 13: norm_delta = 4.51666, step_size = 0.03005, ll = -46034.38293, seconds_since_start = 0.8
Iteration 14: norm_delta = 5.07915, step_size = 0.03534, ll = -40899.91321, seconds_since_start = 0.9
Iteration 15: norm_delta = 4.14024, step_size = 0.03117, ll = -35209.95972, seconds_since_start = 1.0
Iteration 16: norm_delta = 4.41768, step_size = 0.03665, ll = -30750.27464, seconds_since_start = 1.0
Iteration 17: norm_delta = 4.63542, step_size = 0.04310, ll = -26256.37485, seconds_since_start = 1.1
Iteration 18: norm_delta = 4.67559, step_size = 0.05069, ll = -21694.12706, seconds_since_start = 1.2
Iteration 19: norm_delta = 4.44170, step_size = 0.05961, ll = -17366.36244, seconds_since_start = 1.3
Iteration 20: norm_delta = 3.91515, step_size = 0.07010, ll = -13739.10649, seconds_since_start = 1.4
Iteration 21: norm_delta = 5.12346, step_size = 0.10094, ll = -11747.34373, seconds_since_start = 1.5
Iteration 22: norm_delta = 3.95976, step_size = 0.08903, ll = -9704.55162, seconds_since_start = 1.5
Iteration 23: norm_delta = 3.98334, step_size = 0.10470, ll = -8205.12000, seconds_since_start = 1.6
Iteration 24: norm_delta = 2.81115, step_size = 0.12313, ll = -6759.03196, seconds_since_start = 1.7
Iteration 25: norm_delta = 0.31151, step_size = 0.14480, ll = -5923.55720, seconds_since_start = 1.7
Iteration 26: norm_delta = 0.30179, step_size = 0.20851, ll = -5876.00063, seconds_since_start = 1.8
Iteration 27: norm_delta = 0.25063, step_size = 0.30026, ll = -5837.62288, seconds_since_start = 1.9
Iteration 28: norm_delta = 0.17235, step_size = 0.43237, ll = -5812.61537, seconds_since_start = 2.0
Iteration 29: norm_delta = 0.09597, step_size = 0.62262, ll = -5800.38090, seconds_since_start = 2.0
Iteration 30: norm_delta = 0.03900, step_size = 0.89657, ll = -5796.35131, seconds_since_start = 2.1
Iteration 31: norm_delta = 0.00393, step_size = 0.95000, ll = -5795.67827, seconds_since_start = 2.2
Iteration 32: norm_delta = 0.00023, step_size = 0.95000, ll = -5795.65809, seconds_since_start = 2.3
Iteration 33: norm_delta = 0.00001, step_size = 0.95000, ll = -5795.65749, seconds_since_start = 2.3
Iteration 34: norm_delta = 0.00000, step_size = 0.95000, ll = -5795.65746, seconds_since_start = 2.4
Convergence completed after 34 iterations.

<lifelines.CoxPHFitter: fitted with 1850 observations, 978 censored>

but when i try to do cross validation :
from lifelines.utils import k_fold_cross_validation
cph = CoxPHFitter(penalizer=10)
scores = k_fold_cross_validation(cph, survival_df_inline, duration_col='duration', event_col='observed', k=5)
print(scores)
print(np.mean(scores))
print(np.std(scores))

it raise the following :
ValueError                                Traceback (most recent call last)
<ipython-input-101-f778d7116ace> in <module>()
      1 from lifelines.utils import k_fold_cross_validation
      2 cph = CoxPHFitter(alpha=0.95,penalizer=10)
----> 3 scores = k_fold_cross_validation(cph, survival_df_inline, duration_col='duration', event_col='observed', k=5)
      4 print(scores)
      5 print(np.mean(scores))

C:\Anaconda\lib\site-packages\lifelines-0.14.1-py3.6.egg\lifelines\utils\__init__.py in k_fold_cross_validation(fitters, df, duration_col, event_col, k, evaluation_measure, predictor, predictor_kwargs, fitter_kwargs)
    564             # fit the fitter to the training data
    565             fitter.fit(training_data, duration_col=duration_col,
--> 566                        event_col=event_col, **fitter_kwargs)
    567             T_pred = getattr(fitter, predictor)(X_testing, **predictor_kwargs).values
    568

C:\Anaconda\lib\site-packages\lifelines-0.14.1-py3.6.egg\lifelines\fitters\coxph_fitter.py in fit(self, df, duration_col, event_col, show_progress, initial_beta, strata, step_size, weights_col)
    141                                          initial_beta=initial_beta,
    142                                          show_progress=show_progress,
--> 143                                          step_size=step_size)
    144
    145         self.hazards_ = pd.DataFrame(hazards_.T, columns=df.columns, index=['coef']) / self._norm_std

C:\Anaconda\lib\site-packages\lifelines-0.14.1-py3.6.egg\lifelines\fitters\coxph_fitter.py in _newton_rhaphson(self, X, T, E, weights, initial_beta, step_size, precision, show_progress, max_steps)
    230                 raise ValueError("""delta contains nan value(s). Convergence halted. Please see the following tips in the lifelines documentation:
    231 https://lifelines.readthedocs.io/en/latest/Examples.html#problems-with-convergence-in-the-cox-proportional-hazard-model
--> 232 """)
    233
    234             # Save these as pending result

ValueError: delta contains nan value(s). Convergence halted. Please see the following tips in the lifelines documentation:
https://lifelines.readthedocs.io/en/latest/Examples.html#problems-with-convergence-in-the-cox-proportional-hazard-model

The dataset is extracted from another one from which i removed some outliers due to the nature of the data, all the data is numeric and converted to via panda.to_numeric function and each covariates verify the proportional hazards condition.
Am i missing something or this some kind of bug ?

Hey @baraline, thanks for the details issued. There's a folk theorem of computational statistics that says "When you have computational problems, often there’s a problem with your model". Looking at your output of the fit, we can see that the model is on the precipice of fitting: the delta explodes and we have to taper the step_size down. When we break the dataset into K pieces, we probably fall over the precipice into unstable convergence areas due to the smaller sample size.
So along with the usual checks that lifelines does (which includes some variance calculations and correlations with the duration column), I would also suggest:

Looking for high (>.95) correlations between covariates
linearly-dependent covariates (harder to find)

Are you able to share the dataset with me? As lifelines matures, these datasets that cause convergence problems become rarer and rarer, and I like to test with them locally to build new "protection" into lifelines.

Thank you for you quick response ! The case might not repeat as the dataset i'm using is growing in size.
As the data i'm using are under company property, i would have to do heavy anonymisation to make it available to you. Would you still be interested ?

I still would yes, if we are able to reproduce the behaviour.

I'll ask my hierarchy about it tomorrow and I'll keep you in touch !

Hi, sorry for the delay, getting a response took quite some time. Unfortunately i will not be able to share the data with you, my sincere apologies ...
If i ever get my hands on something with the same behavior that i'll can share i'll get back to you.


Element Hierarchy

The element hierarchy on this page should say uap7 instead of uap6.
Additionally, some guidance should be provided as to why the uap7 variant of this extension should be used instead of the uap4 variant.   Presumably, the uap7 should be preferred over the uap4 as the shared fonts are typically applicable to any application in the package.  As the uap7 variant is applied at the package level and uap4 is applied at the application level, the behavior is more clear when placed at the package level.
[Enter feedback here]

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

ID: 8e6170c0-cb6e-34f0-a6bd-2106ca8aa8d4
Version Independent ID: 80f676f0-d887-96ff-3b43-4f5d766291ad
Content: uap7:Extension - Windows UWP applications
Content Source: winrt-related-src/schemas/appxpackage/uapmanifestschema/element-uap7-extension.md
Product: uwp
Technology: winrt-reference
GitHub Login: @drewbatgit
Microsoft Alias: drewbat

@TimMangan I have fixed the issue with the element hierarchy. With regard to the question of uap4 vs. uap7, I have sent email to the subject matter experts to try to get an answer but have not yet been able to get an answer.  I apologize, but as we transition to a new feedback system, we are closing all outstanding issues. Any issues that can be addressed will be tracked using a different internal tool. You can still comment on this issue if you have more info.


Add troubleshooting guide

Add a troubleshooting guide in e.g. issues (maybe also a link somewhere).
Something like this:

[ ] Are you using the correct version of minecraft for this version of the mod?
[ ] Did you install the mod via Fabric? Does it e.g. show up in Mod Menu?
[ ] Are there any other mods installed?

[ ] Does the mod work if all other mods are disabled?

[ ] Does the mod work in another world?
[ ] Are there any warnings related to the mod when launching the game? (Log output can be enabled in the Minecraft launcher under Settings (bottom left) > General > Minecraft: Java Edition settings → Check "Open output log when Minecraft: Java Edition starts")

Fixed


Enable ASP for WCOJ

As stated in the title, ASP is not currently enabled for wcoj. We need to add the support soon.

Done in PR #1366


Link pipeline docs pages for QLFS and NEET to main page

@gilesdring is this ready? Anything else needed to get it into doable?

Have added links to any dashboard page that has <dashboard url>/pipeline/ defined.
Currently works for labour market and neet
Simple wording - can be updated in https://github.com/open-innovations/yff-data/blob/main/src/_includes/layouts/dashboard.njk

@ODILMichelle Look OK to you?

Looks grand.


[FEA] Add config option for the parquet reader input read limit.

We need to make sure the pass_read_limit parameter of the parquet chunked reader is a configurable option for the plugin.  The sub-rowgroup PR is not yet merged but the parameter is already exposed in cudf.
https://github.com/rapidsai/cudf/blob/c8074b5176a74630101c78c43c24b66141352b24/cpp/include/cudf/io/parquet.hpp#L466

This was closed by https://github.com/NVIDIA/spark-rapids/pull/9991


Dev hid

add hid feature

@chengkai15 could you please fix your pull request titles to be more descriptive. I already fixed it for SSP, and here you could e.g. say "Bluetooth: Classic: Add HID profile support". Same for your other pull requests too, like PNP.
In addition to the title, please provide more content in the pull request description as well. It should be possible to get a high-level overview of what's in the pull request without having to go look at individual commits.


Subscribe to PUSH notification - incorrect parameter name

Version (e.g. 1.0, dev-master):
dev-master
Microsoft Exchange version:
online
Description of problem:
Getting SOAP-ERROR: Encoding: object has no 'URL' property when trying to subscribe to PUSH notifications. According to https://msdn.microsoft.com/en-us/library/aa563599(v=exchg.150).aspx the URL property of PushSubscriptionRequestType is all-upper-case. Changing it from Camel case to upper case will resolve this error.
PR with fix included

#391 has been merged, closing this.


enable_default_entities key does not exists.

enable_default_entities key does not exists.

Hi!
can you please give me more details?
have you installed the lmc user module?
Did you activate this module after the lmcuser module?
Regards Alex

yes , I followed all the steps. @alexz707  also you can check into code , there is no such key reference available.

I figured out that the key is converted into function name using camel 🐪 case.


Log spam in tests due to failed attempts at loading ELF for fixtures.

The specific error is:
[ERROR:flutter/testing/elf_loader.cc(72)]
  App AOT file does not exist for this fixture.
  Attempts to launch the Dart VM with these AOT symbols will fail.

This error is benign but makes it hard to read logs while investigating unrelated failures on bots.
This was introduced with the recent change to split loading AOT code.

cc @GaryQian

Ahh, I'll remove this message, it is unnecessary.


refactor: Move the 2nd test WIFI AP to a header file

Description
refactor: Move the 2nd test WIFI AP to a header file
Checklist:

[ x] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

Looks like the section size has been exceeded on Renesas...

/bot run checks


Install failing with unmet sinon peer dependency

Im trying to run greenkeerper on my OSS repo but its failing
Details:
1)Machine : Win 10 Pro
2) Error
`λ npm install-test

<EMAIL_ADDRESS>node_modules\util
<EMAIL_ADDRESS>C:\Users\lnovo\Documents\Projects\eb-checkin-module
-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>
Crashes with the following error
sinon-as-promised\index.js:14
sinon.behavior.resolves = resolves
^
TypeError: Cannot set property 'resolves' of undefined`

same problem here, did you find a solution yet?

I'm not sure what the problem is here, but it seems unrelated to Greenkeeper. I'm going to close this issue to keep our issue tracker clean and actionable.
Happy to reopen upon further explanation.