Validation Script

In what area(s)?

/area API
/area autoscale
/area build
/area monitoring
/area networking
/area test-and-release

Describe the feature
It would be helpful to have a validation script that took in a kubeconfig and gave a pass/fail or likelihood of passing if knative could be run on the cluster. The script would be run by a cluster admin and validate that the kubernetes cluster is properly setup to support knative.
It would be run like: validate-cluster.sh --kubeconfig=/path/to/kubeconfig
I'm not immediately sure what all the checks would be, one initial suggestion by @dgerd is the initial check would simply check the k8s version and perhaps a version of a supported ingress/gateways services.

I would like to work on this item.

/assign @yu2003w

@yu2003w Are u a member of Knative? Why cannot I assign it to you?

@houshengbo I'm not member of knative.

@yu2003w You definitely need to join the knative community as a member. However, you can start working on it anyhow
@k4leung4 @greghaynes Since we folks have gone the process of proposing knative member before, could you propose @yu2003w as a member of knative? I can be another member proposing @yu2003w if needed.

validation scripts check following items:
1,  k8s cluster version
2, Istio version and following services deployed
cluster-local-gateway
istio-ingressgateway
3, cert manager installed

Thanks for working on this. What do we think about rather than a shell script we make this go code which our operator can run? I expect we will want our operator to perform checks like this as part of normal operation and it will be difficult to bake in a shell script which it runs.

Operator should perform the checks before installing Knative Serving.
Does operator need to check the conditions such as ingress gateway periodically after knative serving installed?
Does operator support to install serving with Gloo preinstalled rather than istio?

Operator should perform the checks before installing Knative Serving.
Yes. I am open to the idea of updating the KnativeServing CRD to add the desired dependency configuration. @houshengbo  @greghaynes and @trshafer jcrossley3

Something like this?
spec:
  deps:
    istio: true
    gloo: false
    mtls: false

Does operator need to check the conditions such as ingress gateway periodically after knative serving installed?
I don't think it's necessary for the operator to be continually checking conditions for ingress gateway. Actually the more I think about this, I think it might make sense for the operator to be in a caution state if the ingress gateway goes away. One thing I'm thinking of is upgrading a cluster from one version to another. Upgrading the operator should upgrade the knative config and report any dependency issues. So if we're upgrading in a cluster where the operator is in a "caution" state, that should probably still update knative-serving.

I'm also thinking if upgrading the operator means knative has a backward incompatible change with a prior version of istio. It would not want to squash an existing istio configuration, but also it should fail to install.

Does operator support to install serving with Gloo preinstalled rather than istio?
I think it's still undecided if the operator should install the dependencies or just report the dependencies are uninstalled. We definitely don't want the operator to override an existing istio/gloo installation.

@greghaynes Per your comments, instead of running scripts to validate. We can use the kind job to run commands for the validations, like the following pods in istio:
istio-cleanup-secrets-1.2.0-wblhw         0/1     Completed   0          2m43s
istio-init-crd-10-qcfkp                   0/1     Completed   0          2m55s
istio-init-crd-11-c9sps                   0/1     Completed   0          2m54s
istio-init-crd-12-v7v8z                   0/1     Completed   0          2m54s
istio-security-post-install-1.2.0-tc2p5   0/1     Completed   0          2m42s

We can have a pod named "knative-serving-operator-dependency-validation" running the validation one by one. Completed means the validation has passed. If it fails, we can either try to fix it, or log the error message. Any thoughts on that?
@trshafer @yu2003w We can list the desired dependencies, and specify whether to validate them in a ConfigMap, for example? The pod "knative-serving-operator-dependency-validation" can access this ConfigMap and run the validate one by one.
This is currently some of my consideration. Welcome your comments.

Do we need to run all validation tasks in one job and check error message to determine which failed? Or is validation divided into several jobs?

What value do we get from the additional complexity of a separate job and possibly a configmap when we already have an operator and a CRD? I think we agreed in the recent WG meeting that the best way to communicate the status of the installation (including any missing deps) is through the status field of the custom resource. And I think the best way to do that is by having the operator invoke any necessary validation logic.

Thanks for the comments. I will try to update CRD and send PR later this week.

A few comments on script vs-CRD:

Being able to run these on an ongoing basis would be great. This is probably pro-CRD.
There are a set of getting-started problems that may be difficult to diagnose which happen before the CRD and operator are running on the cluster. Some examples (these are mostly fixed, but there may be others):

Calling role does not have sufficient RBAC (this is a sample from GKE that I'm aware of).
Certain Kubernetes flags or addons are disabled in the cluster (e.g. mutating admission control)

It may be desirable to capture the output of the tool for later analysis. apiserver CRD storage might be good for this, though a text file is probably also fine.
Whatever is running the system checks may need a fairly broad RBAC role (though hopefully this would mostly be "read" capabilities). This may run into some of the same problems as Tiller. (Though, see point 1 about running on an ongoing basis.)

For the dependencies, shall we also check the version?
For example, for istio, except validating ingress/cluster-local gateway working as expected, shall we check wether Istio-version is meet the requirement?
Maybe version is in a range of 1.1.3,1.1.7, 1.2.0.

I think so, it makes sense for knative to support a range of istio installations. Probably makes sense to be a wildcard on patch version. Currently the installation guide supports one version, 1.1.7: https://knative.dev/docs/install/installing-istio/#downloading-istio-and-installing-crds

@trshafer what's your meaning of patch?

The third number in a release: Major.Minor.Patch.

@trshafer
How could istio/certmanager version be retrieved? From image tag or other? I need some advice.
For istio, version could be get from at least two points:
1, "productVersion" in annonation
Annotations:        productID: istio-galley_1.1.7_apachev2_00000
                    productName: istio-galley
                    productVersion: 1.1.7
                    sidecar.istio.io/inject: false

2, image tag
now istio images are tagged with version.  {docker repo}/istio-galley:1.1.7
For certmanager, it seems that image tag is the only approach to get version.
quay.io/jetstack/cert-manager-controller:v0.6.1

Which do you prefer? Or is there any other conventional method?
For patch, could we use a smallest number rather than wildcard?
Take istio as an example, now istio 1.1.2, 1.1.3, 1.1.7 and 1.2.0 could be installed, if wildcard used and user installed istio 1.1.0, it will pass validation check. However, maybe istio 1.1.0 couldn't be supported.
If using istio 1.1.2 as the baseline version, versions higher than 1.1.1 could be accepted.
Do you think this make sense?

/assign yu2003w

I don't think it can reliably be used from the image tag. Similarly how users can change the format of the image digest in the operator using the KnativeServing CRD, users may change the istio image digest.
Does this work for getting the istio version? It grabs the istio version from the environment variable in the proxy container?
ISTIO_PILOT_POD=$(kubectl get pod --selector=istio=pilot -n istio-system -o jsonpath='{$.items[0].metadata.name}')
kubectl exec -it $ISTIO_PILOT_POD -n istio-system --container istio-proxy env | grep VERSION

@trshafer  Thanks a lot. I think we should rely on ISTIO_META_ISTIO_VERSION=1.1.7 to get Istio version.

@trshafer I have updated code and got Istio version from Istio-pilot code.
Currently version of cert-manager should be the image tag. Developer of cert-manager confirmed this.

@trshafer For istio 1.2.4, in isitio-pilot pod, env ISTIO_META_ISTIO_VERSION is not set any more.
I'm afraid we couldn't get Istio version from pod.
Maybe we need to get it from image tag.
Any thoughts about this?


Bump jsdom from 16.4.0 to 16.7.0

Bumps jsdom from 16.4.0 to 16.7.0.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: jsdom dependency-type: indirect ...

@dependabot rebase

 Issues in android signing GH action


Hide channel key when joining

Heisenbridge currently just shows the key as part of the channel modes when joining a channel.
I'm not sure if this is intended.

Currently intentional as there's no filter for the chanmodes the server sends.
I'm not sure if it's any better to try to censor it but to make it possible #72 needs to be fixed first.


SHOC: BSD 3-clause link broken in README

To reproduce-

Go to README.md
Scroll to Licensing https://github.com/GoogleCloudPlatform/PerfKitBenchmarker#licensing
Click on SHOC: BSD 3-clause
See 404 page-

Expected Behaviour-
It should redirect to the correct link.

Please assign me this issue. I would like to fix it.


The value of deployment parameter 'keyVaultPrincipalId' is null

Describe the bug
While running the minimal deployment with the following command;
$context = Get-AzContext
./deploy.ps1 -type minimum -version latest -resourceGroupName rg-iiot-prd -subscriptionId xxxx -tenantId xxxx -applicationName xxx-xxx -context $context

i get this output & error;
Created new resource group rg-iiot-prd in australiaeast.
Deployment will use 'master' branch in 'https://github.com/Azure/Industrial-IoT'.
Start time: 09:47

Registering client and services AAD applications in your tenant...
Importing module AzureAD
Using passed context (Account xxxx, Tenant 0000-0000xxxxx)
Client and services AAD applications registered...

Starting deployment...
09:48:04 - Error: Code=InvalidDeploymentParameterValue; Message=The value of deployment parameter 'keyVaultPrincipalId' is null. Please specify the value or use the parameter reference. See https://aka.ms/resource-manager-parameter-files for details.

Deployment failed.
Removing resource group rg-iiot-prd...
True
New-AzResourceGroupDeployment: C:\xxxxx\Industrial-IoT\deploy\scripts\deploy.ps1:925
Line |
 925 |  … eployment = New-AzResourceGroupDeployment -ResourceGroupName $resourc …
     |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | 09:48:04 - Error: Code=InvalidDeploymentParameterValue; Message=The value of deployment parameter 'keyVaultPrincipalId' is null. Please specify the value or use the parameter reference. See
     | https://aka.ms/resource-manager-parameter-files for details.

I am not a Global Admin, but I am owner on the subscription. But it looks like it was able to create the AAD apps just fine?
To Reproduce
Steps to reproduce the behavior:
Run the command above
Expected behavior
The deployment to work as explained in readme
Desktop (please complete the following information):

OS: Windows
Version 10

Tried again with the Cloud App Administrator role in AAD and it failed again with the same error

After being granted Cloud App Admin role in AAD, I tried again and received the same error.
I tried to run the following;
./deploy/scripts/aad-register.ps1 -Name data-platform-prd -ReplyUrl https://ci-data-platform-prd.azurewebsites.net/ -tenantId xxxxxxxx -Output aad-prd.json

and all that I get in the output file aad-prd.json is null

Tried to run the deploy script again on a AAD tenant where I am Global Administrator and it still fails with the same error.

@nspyke could you please try deploying and/or registering directly from the Azure Cloud Shell?

I was able to get this to work by dropping all the additional parameters apart from -type minimum and then switching from the master branch to the latest release branch. This is a work around though. I will try using the Cloud Shell when I get to work tomorrow.

I just deployed using master and all your minimum parameters and it was successful:

@nspyke Are you able to create/modify app registrations manually in the AAD tenants that you are using?

@nspyke could you please try deploying and/or registering directly from the Azure Cloud Shell?

deploy.ps1 works on the master branch, in Azure Cloud Shell, only using the parameter -type minimum.

@nspyke Are you able to create/modify app registrations manually in the AAD tenants that you are using?

Yes, I have the Cloud Application Administrator role.
I was having this issue while Powershell 7, and I'm thinking that its possible that that may have something to do with it.
Now that I've reverted back to Powershell 5, I'm not encountering the issue.

Closing for now. We can reopen if necessary.

As reference that I had this same issue but it got fixed by deleting existing powershell module installations and letting the deploy script install the dependencies.
I wonder could it be related to how the module dependencies are checked in file aad-register.ps1 and whether there would be any scenario where it detects a module installation but the version is old or incompatible with the deployment?

@vjrantal One important module used by aad-register.ps1 is AzureAD, you can check if it's installed like this:
Get-Module -ListAvailable -Name "AzureAD"
The script also includes two fallbacks for running it in the Azure Cloud Shell. I've noticed that if you start a cmd command prompt from VS2019, then start powershell and run the above command, the module might not be found. If you start a PS directly (blue window), the module does get found. So the module path may also affect the execution: $env:psmodulepath -split ";"
Here are other useful commands:
Get-Module -ListAvailable -Name "AzureAD"
Install-Module -Name "AzureAD"
Update-Module -Name "AzureAD"


ansible.CephLab: touch ~/.vault_pass.txt

To avoid ansible bailing with an OSError. Normally we don't even need
the vault password for cephlab.yml.
Signed-off-by: Zack Cerza<EMAIL_ADDRESS>

empty file is probably the best option, if a little dissatisfying.


[Crash Report]: My App suddenly crash when I open a new Write Window

What did you do in the app? How long it was running?
The app has been open for around 4 hours. I had two Sites added, like 5 windows opened and 2 windows openned prepared for Writing.
What OS version are you running? Intel or ARM?
Intel Mac Mini
How did you run the app? Nightly bundle, ./dev run-desktop, something else?
Build app
Did you have macOS crash report window? If so, what's the output?

Did you see our own modal window saying "Daemon crashed"?
Send log output from Console if it's relevant.

not happening anymore


V0.2.6

New version release. See changelog for details.

Coverage remained the same at 94.236% when pulling 4590b1dc9718f814c385167db67b6d6aca22e0f5 on v0.2.6 into 75a2d15584a61ad11536104fa280f2885454a394 on master.


Plotting issue: Invalid Jupyter notebook plotting backend "pythreejs"

Hi all,
Very excited about this repo. I ran into an issue as I was trying to run the intro notebooks. I can't seem to set the plotting backend correctly (this happens in line 17 in plotting.py). I've tested in Windows and Ubuntu and I did make sure to install pythreejs... regardless it can't seem to find it. Curious if you have some tips for fixing this issue. If I set the backend to none or static, the code runs fine, but doesn't plot anything. Hoping for some pointers here... Thanks!
The error:
ValueError: Invalid Jupyter notebook plotting backend "pythreejs".
Use one of the following:
"static", "client", "server", "trame", "none"

I fixed this by going back to an older version of pyvista as pythreejs has been 'deprecated as a backend'.
Although there appears to be no mention of this in the release notes and I had to dig through the commits to find out when it was removed.
Anyway, let there be light:
pip install pyvista==0.38.1

Great, thanks a lot for solving the issue! I will update the documentation and requirements accordingly in the next days.


helm: Allow disabling xt_socket fallback

Helm cannot distinguish between empty and false value, so previously used if-statement prevented from disabling the fallback when "--set global.enableXTSocketFallback=false" was set.
Fixes: 68858fcf95b ("iptables: Add a fallback to missing xt_socket module.")

This change is

test-me-please

If we do this then we have to add a default value in values.yaml to make sure it is always initialized.

Isn't that the case already?
https://github.com/cilium/cilium/blob/cec34b10ce1830bf20397a08971fd1f5603edbfb/install/kubernetes/cilium/values.yaml#L85-L90


[Bug] Error executing vim.schedule lua callback [...] lean: Executable not found

I installed lean.nvim using the following steps:

Running sudo npm install -g lean-language-server to install the language server
Adding the plugin to Packer with use{'Julian/lean.nvim', requires = {'neovim/nvim-lspconfig', 'nvim-lua/plenary.nvim'}}
Running :PackerSync

However, upon attempting to open a .lean file, I received the following error:
Error executing vim.schedule lua callback: .../site/pack/packer/start/plenary.nvim/lua/plenary/job.lua:105: lean: Executable not found
stack traceback:
        .../site/pack/packer/start/plenary.nvim/lua/plenary/job.lua:105: in function 'new'
        ...nvim/site/pack/packer/start/lean.nvim/lua/lean/_util.lua:36: in function 'subprocess_check_output'
        ...nvim/site/pack/packer/start/lean.nvim/lua/lean/lean3.lua:43: in function '__detect_elan'
        ...re/nvim/site/pack/packer/start/lean.nvim/lua/lean/ft.lua:5: in function 'cb'
        vim.lua:277: in function <vim.lua:277>

So I copied the setup in the Configuration and Usage section of the README, but to no avail. Interestingly, after that, running :source $MYVIMRC also yields this error:
E5108: Error executing lua vim/shared.lua:225: after the second argument: expected table, got nil
stack traceback:
        vim/shared.lua:225: in function 'tbl_extend'
        ...m/site/pack/packer/start/lean.nvim/lua/lean/infoview.lua:433: in function 'enable'
        .../nvim/site/pack/packer/start/lean.nvim/lua/lean/init.lua:40: in function 'setup'
        /home/luiz00martins/.config/nvim/plugins.lua:592: in main chunk
        [C]: in function 'require'
        [string ":lua"]:10: in main chunk

Line 592 is where I call require('lean').setup{, so it seems the setup call is failing.

After some pruning, I have reduced my plugins.lua to this configuration:
require('packer').startup(function(use)
  use{"wbthomason/packer.nvim"}
  use{'Julian/lean.nvim', requires = {'neovim/nvim-lspconfig', 'nvim-lua/plenary.nvim'}}
end)

-- If you don't already have a preferred neovim LSP setup, you may want
-- to reference the nvim-lspconfig documentation, which can be found at:
-- https://github.com/neovim/nvim-lspconfig#keybindings-and-completion
-- For completeness (of showing this plugin's settings), we show
-- a barebones LSP attach handler (which will give you Lean LSP
-- functionality in attached buffers) here:
local function on_attach(client, bufnr)
    local function buf_set_keymap(...) vim.api.nvim_buf_set_keymap(bufnr, ...) end
    local function buf_set_option(...) vim.api.nvim_buf_set_option(bufnr, ...) end
    buf_set_keymap('n', 'gd', '<Cmd>lua vim.lsp.buf.definition()<CR>', {noremap = true})
    buf_set_keymap('n', 'K', '<Cmd>lua vim.lsp.buf.hover()<CR>', {noremap = true})
    buf_set_option('omnifunc', 'v:lua.vim.lsp.omnifunc')
end

require('lean').setup{
  -- Enable the Lean language server(s)?
  --
  -- false to disable, otherwise should be a table of options to pass to
  --  `leanls` and/or `lean3ls`.
  --
  -- See https://github.com/neovim/nvim-lspconfig/blob/master/CONFIG.md#leanls for details.

  -- Lean 4
  lsp = { on_attach = on_attach },

  -- Lean 3
  lsp3 = { on_attach = on_attach },

  -- Abbreviation support
  abbreviations = {
    -- Set one of the following to true to enable abbreviations
    builtin = false, -- built-in expander
    compe = false, -- nvim-compe source
    snippets = false, -- snippets.nvim source
    -- additional abbreviations:
    extra = {
      -- Add a \wknight abbreviation to insert ♘
      --
      -- Note that the backslash is implied, and that you of
      -- course may also use a snippet engine directly to do
      -- this if so desired.
      wknight = '♘',
    },
    -- Change if you don't like the backslash
    -- (comma is a popular choice on French keyboards)
    leader = '\\',
  },

  -- Enable suggested mappings?
  --
  -- false by default, true to enable
  mappings = false,

  -- Infoview support
  infoview = {
    -- Automatically open an infoview on entering a Lean buffer?
    autoopen = true,
    -- Set the infoview windows' widths
    width = 50,
  },

  -- Progress bar support
  progress_bars = {
    -- Enable the progress bars?
    enable = true,
    -- Use a different priority for the signs
			priority = 10,
  },
}

Both errors still appear, so I assume it's not because of conflicts with other plugins.

Even with this very minimal plugins.lua setup, the first error still persists:
require('packer').startup(function(use)
  use{"wbthomason/packer.nvim"}
  use{'Julian/lean.nvim', requires = {'neovim/nvim-lspconfig', 'nvim-lua/plenary.nvim'}}
end)

System details:

Pop_OS 21.04
NVIM v0.6.0-dev+155-g15b736d6e
npm 7.5.2

By chance do you not have elan installed according to the instructions at nvim-lspconfig? (It seems like we don't even mention this in the README at the moment, which we definitely should)

Indeed, this solved the problem! I come from Isabelle, where the isabelle binary is the language server, so I didn't know that in lean the kernel and LS were separate entities. It would definitely help having that noted it the README.
I can now open a .lean file and have the infoview running and working. Thanks!

However, the other error still persists, specifically in the line where I call require('lean').setup{. After running :source $MYVIMRC, this pops up:
E5108: Error executing lua vim/shared.lua:225: after the second argument: expected table, got nil
stack traceback:
        vim/shared.lua:225: in function 'tbl_extend'
        ...m/site/pack/packer/start/lean.nvim/lua/lean/infoview.lua:433: in function 'enable'
        .../nvim/site/pack/packer/start/lean.nvim/lua/lean/init.lua:40: in function 'setup'
        /home/luiz00martins/.config/nvim/plugins.lua:592: in main chunk
        [C]: in function 'require'
        [string ":lua"]:10: in main chunk

It's worth noting that this error does not happen when starting up neovim, nor when I open a .lean file. Those work fine. It only happens when I re-source manually with :source (which is a bit puzzling).

Making running setup{} idempotent might take a bit more work, but probably isn't prohibitively hard.
For the minute you can ensure it only runs once by doing it in e.g. ~/.config/nvim/plugin/lean.lua rather than in your init.{vim,lua} and then not re-sourcing that, if that helps.
I can add a note ensuring we mention you need to install Lean 3 as well to the README in a second -- for Lean4 things work the way you mentioned (in Isabelle).
Also thanks for the feedback! Share any more you've got.

@luiz00martins I've added a quick note to the README to note that Lean 3 is a separate install.
I'll track a separate (new) ticket for allowing re-running require'lean'.setup{} multiple times, but I can't say when someone'll get around to it (patches certainly welcome). Otherwise hopefully stuff here is worked out, but let us know if you have more feedback, hopefully things are going well!


Client stuck at "Loading..."

I've seen the other threads that discuss this issue (most from mid-2016), but nothing suggested seems to work.
my log id: f732726c16843e47132bb81c

Thanks for the report, CC @gabriel and @chrisnojima

michael$ /Applications/Keybase.app/Contents/Resources/KeybaseInstaller.app/Contents/MacOS/Keybase --app-path=/Applications/Keybase.app --run-mode=prod

02.08.2017 13:29:00.681 Installer:42[DEBG] Version: 1.1.46
02.08.2017 13:29:00.681 Installer:54[ERROR] Error parsing: Error Domain=Keybase Code=-1 "Invalid timeout: 0" UserInfo={NSLocalizedDescription=Invalid timeout: 0, NSLocalizedRecoveryOptions=(
OK
)}

Can concur:

[~]$ keybase log send
This command will send recent keybase log entries to keybase.io
for debugging purposes only.

These logs don’t include your private keys or encrypted data,
but they will include filenames and other metadata keybase normally
can’t read, for debugging purposes.

Continue sending logs to keybase.io? (type 'YES' to confirm): yes
▶ INFO ignoring error getting keybase status: API network error: doRetry failed, attempts: 6, timeout 11.390625s, last err: Get https://api.keybase.io/_/api/1.0/sesscheck.json: dial tcp: lookup api.keybase.io: no such host (error 1601)
▶ ERROR API network error: Post https://api.keybase.io/_/api/1.0/logdump/send.json: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

I just looked at the documentation, and it says:
To restart Keybase after an update, type run_keybase. This will kill and restart everything, including the KBFS fuse mount.

After that, my client started normally.
I think a more visible instruction to do this would be really helpful, or an OS-specific hook.

@michael-pesce This is same issue as https://github.com/keybase/client/issues/5830
I finally was able to repro and made a fix. Should be in upcoming version early next week.
I'll close this so discussion can be centralized there.

@poppingtonic Your issue is different, maybe we can open up a different issue for that? (cc @oconnor663 )

I've seen this one before (cc @maxtaco): API network error: doRetry failed, attempts: 6, timeout 11.390625s, last err: Get https://api.keybase.io/_/api/1.0/sesscheck.json: dial tcp: lookup api.keybase.io: no such host (error 1601)
For me it comes up after closing and opening my laptop sometimes. I've filed an internal issue for us to fix it. Could you tell me as much as you can about your Arch setup? Is that Gnome 3? Are you running NetworkManager? So far I've never seen it happen outside of Arch, so it might be related to one of our packages. Thanks for your help.

No problem, @oconnor663. I'm running Gnome 3 with NetworkManager, yes.


Failed to publish to store. Release Notes should contain min 10 to max 4000 characters but contain 9 characters.

Describe the solution you'd like
When pushing a commit with a message smaller than 10 characters, the push to Apple's servers will fail for iOS apps.
Apple's servers reject the publish with this error:
##[error]{"code":"bad_request","message":"Error: Failed to publish to store. Release Notes should contain min 10 to max 4000 characters but contain 9 characters."}

The commit message was fix build in this case.
As a possible fix I would suggest adding some padding to commit messages to make them at least 10 characters, and also trimming to 4000 if somehow it goes overboard.
Describe alternatives you've considered
Most times this will be fine, but we had to log in to app center and check why the build was failing, so it added a bit of friction to the experience.

This is by the design of Apple, not App Center.


npm run build fails (no such file or directory: static/*)

▶ npm run build

><EMAIL_ADDRESS>build /Users/rcoupe/Mine/raai-vue
> node build/build.js

  Tip:
  Built files are meant to be served over an HTTP server.
  Opening index.html over file:// won't work.

⠋ building for production...cp: no such file or directory: static/*
Hash: 87d968f0784b80b50d5e
Version: webpack 1.13.3
Time: 6512ms
                                                  Asset       Size  Chunks             Chunk Names
             static/js/manifest.af02cf99ac1b79acb4d4.js  832 bytes       0  [emitted]  manifest
               static/js/vendor.db1ea9386ddc7ab50fc0.js     107 kB    1, 0  [emitted]  vendor
                  static/js/app.6bc4a6380cc1f204e7ed.js    5.83 kB    2, 0  [emitted]  app
    static/css/app.dc58cacf83731f06a937aa8bf11cea65.css    1.56 kB    2, 0  [emitted]  app
         static/js/manifest.af02cf99ac1b79acb4d4.js.map    8.86 kB       0  [emitted]  manifest
           static/js/vendor.db1ea9386ddc7ab50fc0.js.map     851 kB    1, 0  [emitted]  vendor
              static/js/app.6bc4a6380cc1f204e7ed.js.map    39.3 kB    2, 0  [emitted]  app
static/css/app.dc58cacf83731f06a937aa8bf11cea65.css.map    2.73 kB    2, 0  [emitted]  app
                                             index.html  663 bytes          [emitted]

~/Mine/raai-vue  master ✔                                                                                53m
▶ ls -al static
total 0
drwxr-xr-x   3 rcoupe  staff  102  2 Dec 10:07 .
drwxr-xr-x  20 rcoupe  staff  680  6 Dec 12:37 ..
-rw-r--r--   1 rcoupe  staff    0  2 Dec 10:07 .gitkeep

build/build.js is unmodified.

Please open an issue in the actual template repository, they are linked in the README of this project.
Also, a link to the project as some information about yous setup (OS/node/npm/yarn version ...) would be helping to help you.


Add new information

Hi, I'm Tejas. I would like to add new information in the MS Dhoni section about his recent investments in startups. Could you please assign the task to me?

okay you can do it

Done! 👍🏻

I wanted to add information about a cricketer ,please assign this to me


Implement azd version in azure.yaml for backwards compat

          From team discussion:

We will include azd version in azure.yaml to specify a range (use semantic versioning expressions - e.g. min/max)

Originally posted by @savannahostrowski in https://github.com/Azure/azure-dev/issues/287#issuecomment-1400827181

Do you think the support in azure.yaml for min/max is a different feature than the CI/CD pinning feature? Or is the CI/CD pinning purely doc?

Do you think the support in azure.yaml for min/max is a different feature than the CI/CD pinning feature? Or is the CI/CD pinning purely doc?

I think these are separate things.  The first is a way for a template to express "I need this range of azd versions for me to work correctly".  I view this more as "I found some existing template and want to use it with azd, but it may require a newer version of azd because it uses some newer features".
For the second case, I view it more as "I want to ensure that when I'm running in CI, I use this exact version of azd, and that if the team releases a new version, I don't automatically upgrade".  I view this as "pin your dependencies" in CI story.

@ellismg is this change already in?


Add a default cpack "package" target.

Add a default cpack "package" target when dlib is directly built, as an alternative to building for immediate installation.

Thanks for the PR.
I've never used cpack.  Can you say what does this change enable/why is it useful?

It enables building an archive which neatly packages up the built library.
This PR can be used by running
cmake --build . --target package --config Release
where you would otherwise run
cmake --build . --config Release
The result on my mac is an archive called dlib-19.12.99-Darwin.tar.gz, containing the headers under include/dlib and libdlib.a under lib. There are also pkgconfig and cmake configuration files. As usual passing BUILD_SHARED_LIBS determines whether that build library is shared or static; I would instead get libdlib.19.12.99.dylib under lib with that enabled.
Our particular use case is to isolate building dlib from building the rest of our source code, while still having something we can easily depend on with cmake. We want the isolation primarily because we'll want to build dlib in release mode for speed even while building our code in debug mode. It also allows for slightly faster rebuilds of our code, because we do not usually want to rebuild our stable dependencies.

Cool, sounds good :)
Can the include(CPack) statement be put with the other install and configure directives? Or does it need to be where it is?  It would be slightly cleaner if co-located with the other install instructions.

Sure. I've moved it down.

Awesome, thanks for the PR :)


int32 to elems (type int64)

github.com\scjalliance\comutil\comutil.go:272:13: cannot assign int32 to elems (type int64) in multiple assignment
Windows 10.

Thank you for the report! This should be fixed now.


Event timeout

Ares needs a way to kills events to due to timeout.

OK this is going in the post-release bin then


Move Vagrant-based tests from GitHub Actions to Cirrus CI

Cirrus CI supports nested virtualization and free to use from open
source projects. runc has been using the service since
https://github.com/opencontainers/runc/pull/3088.
Signed-off-by: Kazuyoshi Kato<EMAIL_ADDRESS>

@AkihiroSuda - runc has been using Cirrus CI. Would you recommend containerd to move from GitHub Actions to Cirrus CI as well regarding Vagrant-based tests?
@cpuguy83 - Some of the reporting you've added wouldn't work on Cirrus CI. Would it be a blocker?

Some of the reporting you've added wouldn't work on Cirrus CI. Would it be a blocker?

Definitely 😞  but it won't break anything.


send_from_directory can't  continue send large file

I have a file over 40G, if break off on download,idm can't continue download from server,but if rate of progress is low it will continue,about 50% the download would't work.

hope send_from_directory work with large file
Environment:

Python version:Python 3.9.6
Flask version: 2.0.1

i try to  use chrome download to test,i found that the download will resumed few minutes，maybe the idm feel time out~~~~~~


fix(reactivity): align the get/set operations to ECMA spec

close: #3024
I would say that this PR introduces expensive operations(Reflect.getOwnPropertyDescriptor?), but it aligns with the ECMA spec. For issue #3024, I think it's also a good way to document it so that expensive operations can be avoided.
Related specs: https://www.ecma-international.org/ecma-262/11.0/index.html#sec-invariants-of-the-essential-internal-methods
The main part is:
[[Get]] ( P, Receiver )

The normal return type is any ECMAScript language type.
If P was previously observed as a non-configurable, non-writable own data property of the target with value V, then [[Get]] must return the SameValue as V.
If P was previously observed as a non-configurable own accessor property of the target whose [[Get]] attribute is undefined, the [[Get]] operation must return undefined.

[[Set]] ( P, V, Receiver )

The normal return type is Boolean.
If P was previously observed as a non-configurable, non-writable own data property of the target, then [[Set]] must return false unless V is the SameValue as P's [[Value]] attribute.
If P was previously observed as a non-configurable own accessor property of the target whose [[Set]] attribute is undefined, the [[Set]] operation must return false.

@evan as this might be an expensive change, can you take a look for cost/benefit?

I don't suppose anyone has looked at this any further?

Just wondering what the status of this is, specifically regarding using three.js in Vue 3.

What was the reason for closing this? Just wondering.


Spanish translations for Intro to Static Web Apps

This issue is for the short workshop on Introduction To Static Web Apps being translated into Spanish
The structure of the translation should follow other translations like https://github.com/microsoft/workshop-library/tree/main/full/intro-nlp-tensorflow/translations

Thanks to @daniel692a for taking this one!


FEA A function to determine if an edge is "visible"

Is your feature request related to a problem? Please describe.
In causal graphs (DAG, ADMG, CPDAG, PAG, MAG), there is the notion of an edge being visible. For the DAG/ADMG/CPDAG, edges are by definition always visible.
Describe the solution you'd like
Implement function visible_edge(graph, source, target) to determine if the edge between source and target is visible or not.
One can follow the papers https://auai.org/uai2015/proceedings/papers/155.pdf and https://www.jmlr.org/papers/volume18/16-319/16-319.pdf, and figures to use as unit-test cases.
Additional context
https://github.com/py-why/dowhy/issues/402#issuecomment-1404457573

cc: @aryan26roy

@adam2392 does this need to be implemented before #112 ? I kind of forgot the order in which we need to call these functions.

No I think visibility is a graphical property of an edge.
Proper possibly directed paths is just a generator function for finding paths with specific features. So I think the easiest route is to first implement all_proper_pd_paths generator function, and then implement visible_edge discussed in this GH issue, and then finally implement the generator function for m_separating_sets discussed in #116


M3-3011 show booted config

Description
Update eventMessageGenerator to show which config is associated with linode_boot and linode_reboot events. The exact syntax is up for debate (other options include "Linode my-linode has been booted with my-config by prod-test-004), please weigh in.
There's a ton of other stuff we can do in this file now that we have secondary entities, but afaict the other boot events e.g. lassie_reboot don't have them (I'm asking the API team for confirmation).
I also cleaned up some of the messaging, we were getting things like "Linode my-linode has been booted by the Lassie watchdog service by Linode" and "Linode my-linode is booting by Linode".
Type of Change

Non breaking change ('update', 'change')

Note to Reviewers
Boot and reboot things with different config profiles.

The exact syntax is up for debate (other options include "Linode my-linode has been booted with my-config by prod-test-004), please weigh in


getting memory issues in latest develop branch

It doesn't happen every time, but quite often. URL is
kadist-ios.herokuapp.com/knews_main?channel=kadist&lang=en
logs:
2017-06-22 21:34:18.478562-0700 Jasonette[18579:5013853] libMobileGestalt MobileGestaltSupport.m:153: pid 18579 (Jasonette) does not have sandbox access for frZQaeyWLUvLjeuEK43hmg and IS NOT appropriately entitled
2017-06-22 21:34:18.478707-0700 Jasonette[18579:5013853] libMobileGestalt MobileGestalt.c:550: no access to InverseDeviceID (see <rdar://problem/11744455>)
2017-06-22 21:34:20.554422-0700 Jasonette[18579:5013853] [LayoutConstraints] _UIConstraintBasedLayoutLogUnsatisfiable is OFF
2017-06-22 21:35:54.151587-0700 Jasonette[18579:5013853] [MC] System group container for systemgroup.com.apple.configurationprofiles path is /private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles
2017-06-22 21:35:54.152854-0700 Jasonette[18579:5013853] [MC] Reading from public effective user settings.
2017-06-22 21:38:35.203198-0700 Jasonette[18579:5014658] [] nw_socket_get_input_frames recvmsg(fd 12, 1024 bytes): [57] Socket is not connected
2017-06-22 21:38:35.203248-0700 Jasonette[18579:5014658] [] nw_socket_get_input_frames recvmsg(fd 15, 1024 bytes): [57] Socket is not connected
2017-06-22 21:38:35.203337-0700 Jasonette[18579:5014658] [] nw_socket_get_input_frames recvmsg(fd 16, 1024 bytes): [57] Socket is not connected
2017-06-22 21:38:35.223385-0700 Jasonette[18579:5015095] [] nw_endpoint_handler_add_write_request [22.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:38:35.223567-0700 Jasonette[18579:5015095] [] nw_endpoint_handler_add_write_request [3.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:38:35.223748-0700 Jasonette[18579:5014658] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:38:35.223760-0700 Jasonette[18579:5014658] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:38:35.240330-0700 Jasonette[18579:5015095] [] nw_endpoint_handler_add_write_request [23.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:38:35.240828-0700 Jasonette[18579:5015095] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:13.961876-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 14, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.961935-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 15, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.961974-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 16, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.962009-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 17, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.962041-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 18, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.962079-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 19, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.989077-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [25.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:13.999319-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [31.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:13.999504-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [30.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:13.999629-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [28.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:13.999734-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [29.1 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:14.000044-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [26.2 <IP_ADDRESS>:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:14.000177-0700 Jasonette[18579:5017328] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001015-0700 Jasonette[18579:5016517] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001038-0700 Jasonette[18579:5017325] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001054-0700 Jasonette[18579:5016115] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001070-0700 Jasonette[18579:5016694] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001083-0700 Jasonette[18579:5016102] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
Message from debugger: Terminated due to memory issue

Could you try a fresh clone and retry, just to make sure it's completely in sync?
Also it would be nice if you could isolate the problem and share steps to reproduce.
I tried the url multiple times on my 3 iDevices just now but couldn't replicate it (btw the app looks really great)

the clone is fresh, I have some local changed but those are only styling related to the $util.picker. I can't reliably reproduce it, I open the app, scroll around, switch tabs, etc, there's no pattern that definitely gets to the issue - I noticed earlier today (when not running under the debugger) that it would crash a few times, so tonight started it under Xcode to see if there's anything in the output. Xcode doesn't tell me much!
Thanks for trying it out. Did you scroll down in the main tab? If there was a pattern that would be the closest thing, but really it was just playing with the app.

Just to explore further, has this problem NOT existed before the update?
It could be a problem that's been there all along, or it could be something introduced by the latest update, and these two would be completely different problems, so the more info I have the more helpful it will be to replicate this. Thanks

I haven't seen it crash like this before I merged changes from upstream, the last merge was June 17, so the new code I picked up today is since then, bit the content I show changes so its hard to say that is has to be from those commits.
Were you able to reproduce it?

I have a hunch (hopefully i'm right)
Could you try removing that "color" style attribute from the image component, and see if that fixes it? The color attribute for the image creates a tinted image but in this case you're using a black image anyway so it wouldn't make a difference, but it could be the source of the memory problem when there are a lot of these images being loaded.

I think your hunch is right, I removed the color attribute and cannot make it crash. I'll play more with it in the CA morning, but you've probably guessed this correctly.

I took a deeper look into the code, and looks like it's actually a problematic situation because you have only one of that tinted image and it crashes. I was thinking it was being loaded many times.
Anyway so I tried to fix it and think this should do https://github.com/Jasonette/JASONETTE-iOS/commit/70fe85c5bc233c5019230efbb936ddd2cdaf3685 but let me know if this doesn't fix the tint problem. (Maybe you can try briefly adding the tint back and see if it happens again. I couldn't replicate)

thanks - just did a build and am trying, I'll try it over the day and report back.  I will also try to see in Xcode what the memory footprint is over time running it. Really appreciate you looking at this.

Not been able to make it fail since this fix, so closing issue - have a great weekend.

great to hear, thanks for reporting!


[BEAM-11531] Remove transform implementation

It incorrectly infers proxy and fails in pandas 1.2.0 which disallows calling transform on an empty DataFrame.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run PythonLint PreCommit

Run PythonLint PreCommit

Looks like PythonLint flaked with BEAM-11540

Looks like PythonLint flaked with BEAM-11540

Run PythonLint PreCommit

Run PythonLint PreCommit


Add integration with GDC plugin for isoform quantification

The ICGC has Splice Junction data that will need to utilize the Sashimi plot https://docs.icgc.org/dictionary/viewer/#?viewMode=details&dataType=jcn_p
Since it needs to be used by both plugins I'd say lets keep the three separate and have Splice Junction data from the ICGC and the GDC simply display an informative message to the user that to display this data type they will need to install the Sashimi plot plugin

Might want to call it something other than sashimi plot, 'arc plot', 'arc-rendered sashimi plot', or 'splice junction track' like igv http://software.broadinstitute.org/software/igv/splice_junctions might work


Document code

We must document studio code and use some lib to generate documentation from it. Any ideas on the lib?

I tend to use DocStrap (a JSDoc3-based doc generator) because it's easy to get running, everyone understands JSDoc, is themeable, has search built in and has the ability to add markdown tutorials right to the final output.
Here is an example including tutorials:
http://docstrap.github.io/docstrap/themes/flatly/index.html

@ericholiveira I really like gitbook. It's really sexy and simple to use. Check out featherjs as an example. It's also easy to use with Github, so that's a plus 👍

@ericholiveira we could also create a Studio organization because it sounds like we'll have multiple repositories, and it'd be helpful to not have them all under your own github account, and have us all as contributors instead.

@ericholiveira as an example I threw this together really quick.
Gitbook example

@sean-hill i completely agree with a Studio organization, thats the reason ive been asking you guys about your vision on the future of the project to make sure we are all on the same page. Also, i loved this gitbook, its possible to generate api documentation from codes comments like jsdoc? If its not possible, can we integrate both (jsdoc and gitbook)?

@ericholiveira we can probably make jsdoc to gitbook happen by using (jsdoc-to-markdown)[https://www.npmjs.com/package/jsdoc-to-markdown] as part of the build steps...


”Alexandru Vlahuță” is listed in the drop-down menu

Description:
"Alexandru Vlahuță" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Alexandru Vlahuță" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Alexandru Vlahuță, VASLUI".


OpenML ConnectionRefused

Downloading openml dataset throws connection refused error after max retries expire.
The problem is solved when openml version is updated to the latest one.

Are you working on a cluster or behind a proxy? I had the same issue and fixed it here in the openml-python pacakge.
https://github.com/openml/openml-python/pull/1184

That's a good question.
@ayushi-3536 could you please give some more details of the setup you're using to test this?
Also, a minimal example if possible.
It would also help to know if you're using HPOBench with or without containers.

I was working behind the proxy but I face the same issue while running on the cluster node too, both the times without the container. I was simply executing one of the test files: https://github.com/automl/HPOBench/blob/master/tests/test_svm.py


Bump starlette to 0.20.4

Security vulnerability was fixed in 0.20.3

<EMAIL_ADDRESS>dropped support for Python 3.6 https://github.com/encode/starlette/pull/1616

The test failed and that's what the previous pr for 0.20.2 did by Kludex

Last starlette version that supported python 3.6 is 1.19.1 https://github.com/encode/starlette/blob/e3de71f1433568a3f7ac3dc69ef86cf4f72f5651/README.md?plain=1#L44
so verison 0.20.4 will never pass the tests since it requires Python >=3.7
https://github.com/encode/starlette/blob/e3de71f1433568a3f7ac3dc69ef86cf4f72f5651/setup.py#L27

Yeah this version change would require following and dropping Python 3.6 support

Any chances to push this PR?

Python 3.6 reached EOL and stopped getting security patches 7 months ago, so it's probably for the best to drop support.

Push this PR, please.

Nobody closed this pull, version has been bumped and Python 3.6 has been dropped.


[SPARK-38723][SS][TEST][FOLLOWUP] Deflake the newly added test in QueryExecutionErrorsSuite

What changes were proposed in this pull request?

The newly added test in https://github.com/apache/spark/commit/7d7afb06f682c10f3900eb8adeab9fad6d49cb24 could be flaky, this change deflakes it. Details see comments.
Why are the changes needed?

Deflaky
Does this PR introduce any user-facing change?

Test only change
How was this patch tested?

Test only change
Was this patch authored or co-authored using generative AI tooling?

No

cc @HeartSaVioR

@HyukjinKwon Also the test should have failed in previous CI because the parameter wasn't provided in the checkError method. Could this be a build issue (like the test isn't ran..?

Looks like the test failure in CI is irrelevant.

@MaxGekk Please either merge this or let me know once you're OK with the change. Thanks!

+1, LGTM. Merging to master.
Thank you, @WweiL and @HeartSaVioR for review.


[New Feature]:  support grpc transcoding

https://cloud.google.com/endpoints/docs/grpc/transcoding
.proto files can be obtained through grpc reflection service.

This doesn't need to be built into YARP, it's shipping as part of ASP.NET Core's grpc implementation in .NET 7 cc @JamesNK

Yes. See https://docs.microsoft.com/en-us/aspnet/core/grpc/httpapi?view=aspnetcore-6.0
Note that the way it's implemented means it needs to run in the same app as the gRPC service. Some code could be reused to replicate the reverse proxy approach used by Envoy and grpc-gateway, but it would be more work and we'd need customer demand and compelling reason to consider it.

This doesn't need to be built into YARP,

Yes. See https://docs.microsoft.com/en-us/aspnet/core/grpc/httpapi?view=aspnetcore-6.0
Note that the way this feature is implemented for ASP.NET Core means it needs to run in the same app as the gRPC service. Some code could be reused to replicate the reverse proxy approach used by Envoy and grpc-gateway, but it would be more work and we'd need customer demand and compelling reason to consider it.

The backend is not only asp.net core, but also other grpc servers such as grpc.core (can't migrate to asp.net core for some reason).

@pengweiqhca What's your scenario? You have a .NET Framework application that you can't upgrade to .NET Core and you are routing to it using YARP?

@pengweiqhca What's your scenario? You have a .NET Framework application that you can't upgrade to .NET Core and you are routing to it using YARP?

Yes

Grpc.Core is being deprecated. I think the end-of-life date has been moved back by a year, but you should make plans to stop using it.

Grpc.Core is being deprecated. I think the end-of-life date has been moved back by a year, but you should make plans to stop using it.

If the ideas is easy to implement, there will be less troubles. 😒😒😒

Some code could be reused to replicate the reverse proxy approach used by Envoy and grpc-gateway, but it would be more work.
This feature asp.net core may be not implemented, but as a reverse proxy, YARP need to consider whether to implement similar feature to Envoy and grpc-gateway.

@davidfowl Are there any plans to support grpc-gateway on YARP?

Not currently, no.

There seem to be two approaches to this problem:
a) On-the-fly transcoding which is what https://cloud.google.com/endpoints/docs/grpc/transcoding does
b) Use code generation from the protobuf definition to create a service that will transcode, which is what https://github.com/grpc-ecosystem/grpc-gateway#usage does.
Neither of these directly fit well with the design ethos of YARP. One of the main decisions we have made for YARP is to be transparent about the bodies of requests - we just stream them through the proxy as fast as possible. Modifying grpc streams in-flight would not be congruous with that design decision.
But this seems like something that could be done with the ASP.NET core infra at the heart of YARP. Having middleware that is either doing dynamic transcoding on the fly or a code generator that will take the proto definitions and spit out a transcoding middleware both seem feasible.
I would suggest that this request gets moved to either ASP.NET repo, or the gRPC repos. @JamesNK where would be the most applicable?

ASP.NET Core and grpc-dotnet has support for this using the in-app gRPC JSON transcoding library. Realistically we aren't going to duplicate doing this in YARP middleware unless there is a compelling reason and a lot of customer demand.

Triage: Out of scope of YARP per discussion above. Closing.


Remove duplicate readme sentance

Closing PR - I didn't realize this software wasn't under an open source license.


Add support for OIDC authentication with kubernikusctl

This PR aims at providing a simple way for kubernikus user to login leveraging an OIDC provider. This is already possible using the OpenStack API and Kubernikus API, but this require manipulation and manual updates of the kubeconfig.
In this change we use the standard authentication mechanism which is branched based on the value of auth-type argument. If it is equal to oidc, we call the GetClusterCredentialsOIDC operation (see https://github.com/sapcc/kubernikus/blob/master/pkg/api/client/operations/operations_client.go#L173) instead of the GetClusterCredentials one (see https://github.com/sapcc/kubernikus/blob/master/pkg/api/client/operations/operations_client.go#L144)
Here is a sample command:
kubernikusctl auth init --username john --user-domain-name mydomain --project-id 145529bcs6338df4900fg6733899cc12xx --auth-url https://auth.my-domain.com/v3 --url https://kubernikus.my-domain.sap --name my-cluster-01 --auth-type oidc

Hello,
Thanks a lot for the review.
The issue in the tests seems to be linked to this commit which appears to also fail for the same reason: https://github.com/sapcc/kubernikus/commit/0631b9ecfdc95e7ac961d95d4e66d486b0eebb56.
It could be related to this: https://github.com/helm/helm/issues/2033#issuecomment-304767849
Regards,
Arnaud

Hello @onuryilmaz ,
Can you approve the workflow for testing the pull request again ?
I have merged my branch with master to get the commit Fix chart lock file .
It should solve the issues that previously occured in the CI build.
Thanks and regards,
Arnaud

Hello,
Can you please merge this PR into master ?
Thanks and regards,
Arnaud


2.4.3 memory leak on state change/restart

On versions 2.4.3 and 2.4.4, changing or restarting a state will increase the used memory, and it is never released. On previous versions, this memory was released in one or two seconds.
Tested this in NW.js, if that matters.

Closing due to inactivity / no code example.


Fix ELB 5XX alarm dimensions.

The metric HTTPCode_ELB_5XX_Count does not include the
TargetGroup dimension. It should be removed.
The general dimension set for this metric is only LoadBalancer.

Can I have a review on this please?


feat: return valid actual_fee in get_transaction_receipt

Currently the get_transaction_receipt rpc return an incomplete object. The actual_fee field is set to 0.
Instead we should retrieve it from the events related to this TX and return it.
Also, uncomment the check for this in starknet-rpc-test/get_transaction_receipt.rs (signaled by a TODO)

Can I take this one?

My DM are open if you have questions about the required impl


Allow People to be tagged as Administrators

Allow People to be tagged as Administrators who would have privileged access and who would be able to see and possibly alter details of People, Events and Volunteers (in practice this is always going to possible one way or another for whoever operates the system, but adding Administrators as a concept makes it more transparent and easier to spread the workload load). This also supports the possibility of having one or more Administrators who actively encourage and manage the volunteering process.

Done see all event details and usr list.
Still to do:
* Suspend/unsuspend users
* Approve users (for #75)
* Edit/cancel all events, users, volunteers

All done, except for providing edit access which is now covered by mew action #101


Rethink Demographics (remove fudge multiplier!)

Need to remove the fudge multiplier introduced at Demographics so as to ensure that the model would reach the target number of households. This fudge parameter should be removed or its value re-defined so as to make it adaptable to different system sizes.

As currently implemented, we create new households in the aggregate, according to the national birth probability of first-time buyers and then we distribute them geographically in proportion to the number of jobs in each region. This should be made clear in the paper and model documentation, as there are obvious caveats. To be discussed with Doyne.

Bugs and utilities for new algorithm solved or implemented at a553d220dcfcbec2b9e25b7aca4092841225479d, bf306a1efaa654a78b927edb92ba8ed851bbafa2, fed9178199770f64e394aa434e1c3c8ccee3bc62, c7a9ca19d4f3c5ff85a1f3a05ec47cdfa1ef407b.
New algorithm, which derives the birth rate endogenously to match a target population with a given distribution of ages at birth and a given probability to die dependent on age, implemented at commit f214e49b157e054c2ccc0ac8422b2aed52e957cb


haskellPackages: update stackage and hackage

This Merge
This PR is the regular merge of the haskell-updates branch into master.
This branch is being continually built and tested by hydra at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates. You may be able to find an up-to-date Hydra build report at cdepillabout/nix-haskell-updates-status.
We roughly aim to merge these haskell-updates PRs at least once every two weeks. See the @NixOS/haskell team calendar for who is currently in charge of this branch.
haskellPackages Workflow Summary
Our workflow is currently described in pkgs/development/haskell-modules/HACKING.md.
The short version is this:

We regularly update the Stackage and Hackage pins on haskell-updates (normally at the beginning of a merge window).
The community fixes builds of Haskell packages on that branch.
We aim at at least one merge of haskell-updates into master every two weeks.
We only do the merge if the mergeable job is succeeding on hydra.
If a maintained package is still broken at the time of merge, we will only merge if the maintainer has been pinged 7 days in advance. (If you care about a Haskell package, become a maintainer!)

This is the follow-up to #193927. Come to #haskell:nixos.org if you have any questions.

fyi, I encountered a bug while builiding ghc-check for 9.4 (on route to ghcide) and have reported it upstream.
I think it’s an upstream bug, but if any of you know if this could be our fault, that would be good to know.
https://gitlab.haskell.org/ghc/ghc/-/issues/22260

haskell-updates build report from hydra
evaluation 1783181 of nixpkgs commit 6d4c324 as of 2022-10-08 12:28 UTC
:yellow_circle: Potential issues (and possibly evaluation errors)

maintained jobset failed.

Build summary

Platform
Failed :x:
DependencyFailed :heavy_exclamation_mark:
TimedOut :hourglass::no_entry_sign:
Success :heavy_check_mark:

aarch64-linux :iphone:
25
37

6637

x86_64-darwin :apple:
59
24
6
6545

x86_64-linux :penguin:
4
8
6
6716

Maintained packages with failed dependency

[ ] cabal2nix @peti

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] toplevel
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc902
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc924
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc942
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages
[:penguin::heavy_check_mark:] pkgsStatic.haskell.packages.native-bignum.ghc924
[:penguin::heavy_check_mark:] pkgsStatic.haskellPackages

[ ] git-annex @peti @roosemberth

[:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] toplevel
[:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages

[ ] [:penguin::heavy_exclamation_mark:] maintained @cdepillabout @expipiplus1 @maralorn @sternenseemann

Unmaintained packages with build failure
76 job(s)

[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.OrderedBits  :arrow_heading_up: 5 | 36
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.persistent-postgresql  :arrow_heading_up: 5 | 23
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.hasql-transaction-io  :arrow_heading_up: 5 | 5
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hw-json-simd  :arrow_heading_up: 4 | 8
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hw-simd  :arrow_heading_up: 4 | 8
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.long-double  :arrow_heading_up: 2 | 2
[ ] [:iphone::x:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.quic  :arrow_heading_up: 2 | 2
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.freetype2  :arrow_heading_up: 1 | 8
[ ] [:iphone::x:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.easytensor  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.nlopt-haskell  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.openal-ffi  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.swisstable  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.unicode-properties  :arrow_heading_up: 1 | 1
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.flatparse  :arrow_heading_up: 0 | 15
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.PyF  :arrow_heading_up: 0 | 4
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hmidi  :arrow_heading_up: 0 | 4
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.json-rpc  :arrow_heading_up: 0 | 2
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.posix-socket  :arrow_heading_up: 0 | 2
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.gi-gdkx11  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hamid  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hmatrix-morpheus  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.huckleberry  :arrow_heading_up: 0 | 1
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.picosat  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.select  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.sysinfo  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.FractalArt
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.HsASA
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.chiphunk
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.comfort-fftw
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.diskhash
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.env-extra
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.epub-tools
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.fudgets
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.gerrit
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.ghc-gc-hook
[ ] [:apple::x:] haskellPackages.gi-gtkosxapplication
[ ] [:iphone::x:] [:penguin::heavy_check_mark:] haskellPackages.gnome-keyring
[ ] [:apple::x:] haskellPackages.gtk-mac-integration
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.gtk-traymanager
[ ] [:apple::x:] haskellPackages.gtk3-mac-integration
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hid
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.highlight
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hssh
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hsshellscript
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.hssourceinfo
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.interprocess
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.intricacy
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.ipcvar
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.jammittools
[ ] [:apple::x:] haskellPackages.kqueue
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.leveldb-haskell-fork
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.linux-framebuffer
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.mediawiki2latex
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.memfd
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.mercury-api
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.nano-cryptr
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.nix-serve-ng
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.phatsort
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.ping-wrapper
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.posit
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.posix-timer
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.procex
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.pthread
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.risc386
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.satchmo-backends
[ ] [:iphone::x:] [:apple::x:] [:penguin::x:] haskellPackages.satchmo-minisat
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.sfml-audio
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.skews
[ ] [:iphone::x:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.slugify
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.tailfile-hinotify
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.wiringPi
[ ] [:iphone::x:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.x86-64bit
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.xmonad-utils
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.yoga
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.zot
[ ] [:iphone::heavy_check_mark:] [:apple::x:] [:penguin::heavy_check_mark:] haskellPackages.zxcvbn-c

Unmaintained packages with failed dependency
85 job(s)

[ ] ghc-lib-parser-ex  :arrow_heading_up: 17 | 38

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc902
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc924
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc942
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] ghc-lib-parser  :arrow_heading_up: 11 | 36

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc902
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc924
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc942
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.PrimitiveArray  :arrow_heading_up: 4 | 35
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.esqueleto  :arrow_heading_up: 4 | 21
[ ] hpack  :arrow_heading_up: 4 | 14

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] toplevel
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc902
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc924
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc942
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hasql-streams-core  :arrow_heading_up: 4 | 4
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.BiobaseTypes  :arrow_heading_up: 3 | 21
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hw-json-standard-cursor  :arrow_heading_up: 2 | 6
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hw-json-simple-cursor  :arrow_heading_up: 2 | 4
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.BiobaseENA  :arrow_heading_up: 1 | 18
[ ] hoogle  :arrow_heading_up: 1 | 3

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc902
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc924
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc942
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hw-json  :arrow_heading_up: 1 | 3
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.http3  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.persistent-postgresql-streaming  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.wss-client  :arrow_heading_up: 1 | 1
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.BiobaseXNA  :arrow_heading_up: 0 | 17
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.BiobaseFasta  :arrow_heading_up: 0 | 3
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hw-dsv  :arrow_heading_up: 0 | 3
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hw-json-lens  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.snaplet-persistent  :arrow_heading_up: 0 | 1
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.align-audio
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.bcp47-orphans
[ ] cabal2nix-unstable

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc902
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc924
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc942
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.easytensor-vulkan
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.esqueleto-streaming
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.experimenter
[ ] ghc-lib

[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc8107
[:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc884
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc902
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc924
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskell.packages.ghc942
[:iphone::heavy_check_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages

[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.harfbuzz-pure
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hasql-streams-conduit
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hasql-streams-pipes
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hasql-streams-streaming
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.hasql-streams-streamly
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.heroku-persistent
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hmatrix-nlopt
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.hs-swisstable-hashtables-class
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.hw-simd-cli
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.kmn-programming
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.network-messagepack-rpc-websocket
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.persistent-mtl
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.persistent-pagination
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.persistent-typed-db
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.rounded
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.rounded-hw
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_exclamation_mark:] haskellPackages.satchmo-examples
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.sound-collage
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_check_mark:] [:penguin::heavy_check_mark:] haskellPackages.unicode-names
[ ] [:iphone::heavy_exclamation_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.warp-quic
[ ] [:iphone::heavy_check_mark:] [:apple::heavy_exclamation_mark:] [:penguin::heavy_check_mark:] haskellPackages.xbattbar

Top 50 broken packages, sorted by number of reverse dependencies
50 job(s)
amazonka-core :arrow_heading_up: 185
gogol-core :arrow_heading_up: 184
haskell98 :arrow_heading_up: 153
enumerator :arrow_heading_up: 56
util :arrow_heading_up: 49
derive :arrow_heading_up: 48
amazonka :arrow_heading_up: 43
accelerate :arrow_heading_up: 42
parseargs :arrow_heading_up: 42
MonadCatchIO-transformers :arrow_heading_up: 41
data-lens :arrow_heading_up: 33
rank1dynamic :arrow_heading_up: 33
distributed-static :arrow_heading_up: 31
language-ecmascript :arrow_heading_up: 31
distributed-process :arrow_heading_up: 30
iteratee :arrow_heading_up: 29
jmacro :arrow_heading_up: 29
mmsyn3 :arrow_heading_up: 28
autodocodec-yaml :arrow_heading_up: 27
crypto-numbers :arrow_heading_up: 25
either-unwrap :arrow_heading_up: 25
sydtest :arrow_heading_up: 24
crypto-pubkey :arrow_heading_up: 22
haskelldb :arrow_heading_up: 22
wxdirect :arrow_heading_up: 22
alg :arrow_heading_up: 21
amazonka-s3 :arrow_heading_up: 21
mmsyn2 :arrow_heading_up: 21
wxc :arrow_heading_up: 21
biocore :arrow_heading_up: 20
wxcore :arrow_heading_up: 20
attoparsec-enumerator :arrow_heading_up: 19
bytestring-show :arrow_heading_up: 19
fay :arrow_heading_up: 19
wx :arrow_heading_up: 19
asn1-data :arrow_heading_up: 18
dbus-core :arrow_heading_up: 18
gtksourceview2 :arrow_heading_up: 18
ukrainian-phonetics-basic :arrow_heading_up: 18
HGamer3D-Data :arrow_heading_up: 17
certificate :arrow_heading_up: 17
dbus-client :arrow_heading_up: 17
gconf :arrow_heading_up: 17
gtk-serialized-event :arrow_heading_up: 17
cuda :arrow_heading_up: 16
happstack-jmacro :arrow_heading_up: 16
manatee-core :arrow_heading_up: 16
monads-fd :arrow_heading_up: 16
tls-extra :arrow_heading_up: 16
ADPfusion :arrow_heading_up: 15

:arrow_heading_up:: The number of packages that depend (directly or indirectly) on this package (if any). If two numbers are shown the first (lower) number considers only packages which currently have enabled hydra jobs, i.e. are not marked broken. The second (higher) number considers all packages.
Report generated with maintainers/scripts/haskell/hydra-report.hs

cabal2nix ghc942 failure is still https://github.com/haskell-foundation/foundation/issues/571

@lf- @9999years @ttuegel
It looks like cabal2nix is broken on aarch64 with ghc942 because foundation isn't building:
https://hydra.nixos.org/build/193180160
Any interest in either looking into this, or reporting upstream?

failures:
x `div` y) * y + (x `mod` y) == x failed after 7 tests:
             use param: --seed<PHONE_NUMBER>6187018093
parameter 1 : 145
parameter 2 : 137
Property `a == b' failed where:
    a = 145 :: Word8
        ^^^^ ^^^^^^^
    b = 26 :: Word8
        ^^^^ ^^^^^^

         ✗ Divisible failed after 1 test
           use param: --seed<PHONE_NUMBER>6187018093
           ✗ (x `div` y) * y + (x `mod` y) == x failed after 32 tests:
             use param: --seed<PHONE_NUMBER>6187018093
Word16
         ✓ Integral (100 tests)
         ✓ Property (400 tests)
         ✓ Additive (300 tests)
         ✓ Multiplicative (400 tests)
           ✗ (x `div` y) * y + (x `mod` y) == x failed after 32 tests:
             use param: --seed<PHONE_NUMBER>6187018093
parameter 1 : 50577
parameter 2 : 42533
Property `a == b' failed where:
    a = 50577 :: Word16
        ^^  ^
    b = 27574 :: Word16
        ^^  ^

         ✗ Divisible failed after 1 test
           use param: --seed<PHONE_NUMBER>6187018093

I have a sneaking suspicion that this is an upstream bug in some way but I'm too sleepy right now to stare at arithmetic to figure out what went wrong.

Upstream bug report: GHC 9.4.2 regresses being able to do math on aarch64


Inferring type parameter in arrow function / function expression fails

Bug Report

🔎 Search Terms

inferred type parameter arrow function expression
🕗 Version & Regression Information

I tried every version between 3.3.3 and 4.4.2 in the playground, and I got the same results

⏯ Playground Link

Playground link with relevant code
💻 Code

declare function test1<Fn extends <Context>(arg1: Context) => [Context]>(fn: Fn): ReturnType<Fn>;
declare function test2<Fn extends <Context>(arg1: Context) => { key: Context }>(fn: Fn): ReturnType<Fn>;

// Ok in TypeScript 4.4.2
test1((arg2) => [arg2]);

// Error in TypeScript 3.3.3 - 4.4.2;
// TS2719: Type 'Context' is not assignable to type 'Context'. Two different types with this name exist, but they are unrelated.
//   'Context' could be instantiated with an arbitrary type which could be unrelated to 'Context'.
test2((arg2) => ({ key: arg2 }));

// Error in TypeScript 3.3.3 - 4.4.2;
// TS2345: Argument of type '<Context>(arg2: Context) => { key: Context; }' is not assignable to parameter of type '<Context>(arg1: Context) => { key: Context; }'.
//   Call signature return types '{ key: Context; }' and '{ key: Context; }' are incompatible.
//     The types of 'key' are incompatible between these types.
//       Type 'Context' is not assignable to type 'Context'. Two different types with this name exist, but they are unrelated.
//         'Context' could be instantiated with an arbitrary type which could be unrelated to 'Context'.
test2((arg2) => { return { key: arg2 } });
test2(function(arg2) { return { key: arg2 }; });

🙁 Actual behavior

There's a TS2719 or TS2345 error indicating that Context could be instantiated with an arbitrary, unrelated typ.
🙂 Expected behavior

It should be possible to infer the type of 'Context' since it must be the same in these cases.

I have a basic fix for this behavior at https://github.com/OlofKalufs/TypeScript/tree/main


Explicitly mention type: "integer" in definition of Schema Object

OAS 3.0 and 3.1 explicitly define "integer" as an allowed value of the type keyword in section Data Types.
This difference between OAS and pure JSON Schema is not mentioned in section Schema Object.
Proposal
Explicitly mention this significant difference and define OAS type: "integer" as a shortcut for JSON Schema type: "number", multipleOf: 1.
Explicitly state in the Format Registry that column "Type" uses the extended OAS definition.

This is not a difference.  integer is an allowed value for the type keyword in all relevant versions of JSON Schema.
However, integers are not part of the JSON data model, and therefore it is not something that can control the applicability of JSON Schema keywords of format values.
These are two separate things, as the JSON Schema specification explicitly states.
We cannot change the applicability criteria for the format registry, because that is defined by JSON Schema and not the OAS.

String values MUST be one of the six primitive types ("null", "boolean", "object", "array", "number", or "string"), or "integer" which matches any number with a zero fractional part

source

Note that JSON Schema vocabularies are free to define their own extended type system. This should not be confused with the core data model types defined here. As an example, "integer" is a reasonable type for a vocabulary to define as a value for a keyword, but the data model makes no distinction between integers and other numbers.

source

Note that the "type" keyword in this specification defines an "integer" type which is not part of the data model. Therefore a format attribute can be limited to numbers, but not specifically to integers. However, a numeric format can be used alongside the "type" keyword with a value of "integer", or could be explicitly defined to always pass if the number is not an integer, which produces essentially the same behavior as only applying to integers

source
@handrews I know you've already tried to explain this multiple times. Thank you for you patience here.
Based on those, it seems that using format alongside with integer is explicitly permitted/defined in the specification.
Even if it wasn't defined, this second paragraph as far as I understand it, would effectively allow the OAS vocab to define it.
I couldn't find any information in the specifications I could link that'd implicitly or explicitly invalidate the statement I made above.

@handrews thanks. Let's try to backtrack this together then.
If the type keyword does not define the data model, what does?

@baywet

If the type keyword does not define the data model, what does?

the section you linked titled "Instance Data Model" which explicitly lists the six types:  null, boolean, object, array, number, string.  This is in turn derived from the JSON data model, which defined four types (object, array, number, string) and three literals (true and false, which JSON Schema groups as booleans, plus null, which JSON Schema treats as its own type).

Allow me to rephrase my question. If the type keyword is not how a given schema declares which model it's using, how does the schema declare which model it's using?

@baywet the data model type is inherent in the instance.
JSON (RFC 8259) defines a data model.  JSON Schema is defined for JSON, so that is all the data model we have to work with.  JSON Schema is not defined for any other data model / type system.
JSON Schema refines the JSON data model slightly by doing a few things:

defining two types that encompass the three literals in addition to the four types defined by JSON
specifying that duplicate property keys are not supported (JSON allows them but leaves the behavior undefined)
specifying that, for the purpose of evaluating JSON Schema constraints, integers are a mathematical rather than lexical property (e.g. 1.0 is still an integer)

Beyond that, JSON Schema is a constraint system.  It is not a data definition system.  There is no further data model or type system.  There are just constraints against which an instance is valid or invalid.
JSON Schema keywords and format values can be tied to a particular data model type, which (as explicitly shown in the section that has now been quoted many times, does not include integer).  What this means is that, in terms of validation, if the instance is of the applicable data model type, then the constraint is evaluated.  If the instance is of some other data model type, then the constraint automatically passes.
The type and format keywords are just constraints.  They have nothing to do with any data model at all, as far as the JSON Schema specification is concerned.

If OpenAPI wants to have an actual data definition system, then it should invest in creating one, or in adapting an existing one that was actually designed for that purpose, which JSON Schema was not.  JSON Schema could still be retained for complex runtime validation, to which it is well-suited, using exactly the features that are so problematic for data definition (e.g. anyOf).
It's not a coincidence that the various VC-backed companies out there (or large estabished companies such as Microsoft) have made alternative ways to define data that then gets mapped down to OpenAPI.  While some of these are positioned as "OpenAPI alternatives", they almost exclusively work around JSON Schema's lack of suitability for data definition / code generation.  It's going to continue to be a problem for as long as OpenAPI relies exclusively on JSON Schema for this functionality.

For completeness (and in case anyone didn't read the other several PRs on this topic):
I am opposed to mentioning "integer" in the Schema Object section in either 3.0 or 3.1.  The use of "integer" in the type keyword is standard JSON Schema.
In 3.1, we use standard JSON Schema in its entirety and should not comment on any particular keyword- we intentionally removed that entire section for 3.1, and it was the right decision.
In 3.0, there is a list of keywords, but only for explaining differences between the use of the keywords in OAS and their use in standard JSON Schema.  The use of "integer" with type is not one of those differences, therefore it must not go in that list.

Sorry, I missed that "integer" was removed only from the instance data model in the JSON Schema Core and is still listed as an allowed value for type in JSON Schema Validation.
@handrews Glad to have you here to educate us 😎

Will be fixed by #4045


Radiometric capture

Can anyone tell me if pylepton can capture radiometric 14 bit arrays from the camera SPI interface that contains temperature*1000 values for 160x120 pixels?
Also, does it support 160x120 resolution?
Thx,
Zoltán

Yes, that's what the capture() function returns. You can use the lepton3 or lepton3-dev branch for lepton 3 support.

Thanks!


Jakarta-less dependency for 3rd party usage in frameworks ?

Hello
This is not a bug, more a question.  This is probably related to https://github.com/maruTA-bis5/mattermost4j/issues/308
Under Quarkus framework, client construction throws (1)
This is because jersey 3.0.4 wants import jakarta.inject.Singleton;
I opened https://github.com/quarkusio/quarkus/issues/30069 on their side.
Quarkus uses (at the moment) javax. and RESTeasy.
Do you know if there is a way to force a dependency of jersey<3.0.4 to keep the javax. compatibility ?
Thanks !
(1)
2022-12-24 16:43:44,900 ERROR [org.jbo.res.rea.com.cor.AbstractResteasyReactiveContext] (executor-thread-0) Request failed: java.lang.NoClassDefFoundError: jakarta/inject/Singleton
	at org.glassfish.jersey.model.ContractProvider$Builder.<clinit>(ContractProvider.java:67)
	(...)
	at org.glassfish.jersey.client.JerseyClientBuilder.register(JerseyClientBuilder.java:244)
	at org.glassfish.jersey.client.JerseyClientBuilder.register(JerseyClientBuilder.java:48)
	at net.bis5.mattermost.client4.MattermostClient.buildClient(MattermostClient.java:201)

solved this by https://github.com/quarkusio/quarkus/issues/30069#issuecomment-1364730702
the #308 plan is indeed a good idea tho.  @maruTA-bis5 feel free to close my issue, however it does not directly relate to Jersey or RESTeasy, it's more about the jakarta EE migration.

Hi @laurentperez
I've just released version 1.0.0-beta.1 includes #308 changes.
Please add mattermost4j-resteasy dependency to your project then you can use RESTEasy as a client under the Quarkus framework afaik.
(*) Version 1.0.0-beta.1 will be available by Maven Central Repository within 2-3 hours.
If you are facing any problems, feel free to open a new issue.


Test Corda network on EKS v1.19

TBD
Description
As a ... I want to ... so that ....
(add more description and relevant links)
Acceptance Criteria

First acceptance criteria
...
...

@pppazos can you have a look on this one

I can take this one


StorageLoader: write JSON path file for com.amazon.aws.ec2.snowplow/instance_metadata

For the second instance I think proper name would be "instance_identity_document". It refers to URL where it can be found (/dynamic/instance-identity/document).

I think we can probably get away with just "instance_identity" - i.e. the document is just a way of requesting the JSON version?

There three more endpoints: signature, dsa2048 and pkcs7. All with meaningless keys (or some other base64).

Okay cool - go with "instance_identity_document" then.


No fonts

Clicking on font or trying to scroll left and right does not change from 'undefined'.
I have confirmed the normal 'CR Draw Text' node loads fonts that I place there however. What would cause this to not detect any fonts?

The only way I've been able to load a font is to convert the 'font' widget to an input, and then use the 'CR Select Font' node.

there's a font directory inside the extension

I do have that font directory populated (it also has some by default). Presuming the 'Draw Text' on the right side is actually a part of this repository, that is not working. The CR Draw Text is working fine.


chore(master): release 1.0.5

:robot: I have created a release beep boop
1.0.5 (2023-08-08)
Miscellaneous

deps: update dependency orchestra/testbench to v8.6.1 (d597451)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-webhook-client/releases/tag/v1.0.5 :sunflower:


cmd/cgo: exported function doesn't support pointer to array arguments

package p
import "C"
//export F
func F(x *[10]C.int) {}

$ go build issue10889.go
# command-line-arguments
./issue10889.go:6:11: Go type not supported in export: [10]_Ctype_int
./issue10889.go:6:11: Go type not supported in export: [10]_Ctype_int

We can't support [10]_Ctype_int as argument, that's for sure, but why
can't we support *[10]_Ctype_int as argument?
I imagine one reason is probably that the C pointer to array layout and
Go's are incompatible, but I don't think that is the case today. Now people
need to resort to passing pointers to Go exported functions, but that also
assumes that the array layout is compatible between C and Go.

C doesn't have array arguments nor pointer-to-array arguments. It just has pointers.
I suppose we could turn Go [10]C.int into C int*, but there's already Go **C.int for that.
In general arrays in argument position are not well understood by most C programmers.
Given that there is already an equivalent syntax supported (plain pointers), I'm not inclined
to do anything here.