Steampipe virtual tables.

https://steampipe.io/
https://sqlite.org/forum/forumpost/87a01d8a9f3e51e8

I also use steam pipe and love the SQL way ...
will try this out for sure..

This one is stalled for complete lack of interest on their part. My issue was ignored; then I pinged their community lead (with whom I'd discussed this on SQLite forum), he tries to rope people in and he is completely ignored.

They have a (1) “plugin” API (in Go) and use those plugins to feed data into (2) virtual tables (in C). I have a (3) pure Go API for virtual tables.
I'd like to plug (1) into (3). Unfortunately (1) is a contrived thing that can, apparently, only communicate with (2) through an obscure gRPC interface. Which is a shame.
I asked for a little help to understand (1) better, but TBH I don't think they're interested. Basically, it'd help me tap into their ecosystem, rather than the opposite, so it makes sense that they just don't care™.

I reckon your hunch is right. It’s a business for them is maybe how they see it ultimately.


[Bug]: MacOS install failure -- onnxruntime 1.17.0

What happened?
I just installed chromadb on my mac with a python setup. I'm running the example script from the installation docs and I get an error with onnxruntime. Log is provided below.
Versions
python: 3.10.0
chromadb: 0.4.22
MacOS: 12.6.3
pip: 21.2.3
Relevant log output
2024-02-08 18:03:11.829324 [W:onnxruntime:, helper.cc:67 IsInputSupported] CoreML does not support input dim > 16384. Input:embeddings.word_embeddings.weight, shape: {30522,384}
2024-02-08 18:03:11.830080 [W:onnxruntime:, coreml_execution_provider.cc:81 GetCapability] CoreMLExecutionProvider::GetCapability, number of partitions supported by CoreML: 49 number of nodes in the graph: 323 number of nodes supported by CoreML: 231
2024-02-08 18:03:12.598377 [E:onnxruntime:, sequential_executor.cc:514 ExecuteKernel] Non-zero status code returned while running CoreML_11612189108157573330_1 node. Name:'CoreMLExecutionProvider_CoreML_11612189108157573330_1_1' Status Message: Error executing model: Error computing NN outputs.
Traceback (most recent call last):
  File "/Users/farzadsharifbakhtiar/projects/PRchatbot/chroma_test.py", line 9, in <module>
    collection.add(
  File "/Users/farzadsharifbakhtiar/projects/PRchatbot/.venv/lib/python3.10/site-packages/chromadb/api/models/Collection.py", line 154, in add
    embeddings = self._embed(input=documents)
  File "/Users/farzadsharifbakhtiar/projects/PRchatbot/.venv/lib/python3.10/site-packages/chromadb/api/models/Collection.py", line 633, in _embed
    return self._embedding_function(input=input)
  File "/Users/farzadsharifbakhtiar/projects/PRchatbot/.venv/lib/python3.10/site-packages/chromadb/utils/embedding_functions.py", line 509, in __call__
    res = cast(Embeddings, self._forward(input).tolist())
  File "/Users/farzadsharifbakhtiar/projects/PRchatbot/.venv/lib/python3.10/site-packages/chromadb/utils/embedding_functions.py", line 458, in _forward
    model_output = self.model.run(None, onnx_input)
  File "/Users/farzadsharifbakhtiar/projects/PRchatbot/.venv/lib/python3.10/site-packages/onnxruntime/capi/onnxruntime_inference_collection.py", line 220, in run
    return self._sess.run(output_names, input_feed, run_options)
onnxruntime.capi.onnxruntime_pybind11_state.Fail: [ONNXRuntimeError] : 1 : FAIL : Non-zero status code returned while running CoreML_11612189108157573330_1 node. Name:'CoreMLExecutionProvider_CoreML_11612189108157573330_1_1' Status Message: Error executing model: Error computing NN outputs.

@thedamnedrhino, do you mind checking your onnxruntime release?

onnxruntime==1.17.0
Thanks @tazarov.

A downgrade to 1.16.0 fixed the issue.


⚠ ClamAV has degraded performance

In 568d054, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 470 ms

Resolved: ClamAV performance has improved in 9fd6ef7.


Node 18 support?

I see that the cloudformation templates uses node10, however we have managed to get this running on Node16 without any trouble.
Node16 is LTS until March 11 2024.
https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
Is there any plan to update Tachyon to support AWS-SDK v3 which is required to use the node18 runtime.

I successfully updated the package.json to work with node 18.4.
Not yet tested on AWS (the node engine in the cloudformation-template.json file should be updated).
Here are the updated package.json dependencies:
"dependencies": {     "animated-gif-detector": "^1.2.0",     "imagemin-pngquant": "^8.0.0",     "sharp": "^0.32.5",     "smartcrop-sharp": "^2.0.8"   },   "devDependencies": {     "aws-sdk": "^2.276.1",     "aws-xray-sdk-core": "^2.4.0",     "cli-table": "^0.3.1",     "filesize": "^4.1.2"   }

Yep, the main issue that I found was the requirement for AWS SDK v3 when using Lambda.
This seems to be quite a rework, moving to async functions, removal of the makeUnauthenticatedRequest function, etc.

ok, I understand what you're saying.
I join your question about upgrading to aws-sdk v3.
In the meantime I'll try to make some attempts.

This was done in #162


feat(doctor): identify missing/extra shims

Summary
Closes #1511
These changes enable mise doctor to identify missing or extra shims and will request users to run mise reshim if needed.
Additional Notes

Quite a bit of refactoring here really just to make the changes more obvious.
Uses checks rather than a warning, but can be trivially updated to warnings if desired

also, keep in the back of your mind other potential checks we might be able to add here


Alwayd display label/data on pie charts

Is there a setting/option to always display the label and data on the pie chart? Instead of displaying the legend on hover that is. Also notice that pie charts are accepting a maximum of three data items. Can that also be changed? It is ignoring the 4th data onwards.

@aparna1591 you might be able to find an answer from the issues linked in #78
Closing as all pie/doughnut labelling issues are consolidated there.


Release annotations

Initial version of release annotation with drafted data for #83

Thank you @NikolovI
We are going to merge it with the clear idea that the release annotations a are in hardcoded date.
We will make the annotations dynamic when we do a bit more backend work :)


Emotion 10

Description
Update to Emotion 10 and other API changes
See the migration guide for details.
Outstanding issues:

https://github.com/emotion-js/emotion/issues/1105#issuecomment-457259458
https://github.com/emotion-js/emotion/issues/1178

Motivation and context
Closes #813
Connects #652 #765
Screenshots, videos, or demo, if appropriate
https://emotion-10--mineral-ui.netlify.com
How to test

Try the aforementioned demo
Try using the css prop and the as prop on different components
Take it for a test drive in CRA, in various browsers
Review updated documentation and migration guide.

An npm package has been published with the next tag for anyone wishing to take it for a test drive locally. npm i mineral-ui@next
Types of changes

New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

See the migration guide for details.
Checklist

[x] Renders and functions properly in all supported browsers
[x] Automated tests written and passing
[x] Accessibility and inclusivity considered
[x] Rendering performance (initial load time & 60fps) and perceived performance considered
[x] Documentation created or updated
[x] Tested in sandbox if new component or breaking change

This is just awesome! When do you think this will hit the next release?

Thanks @avetisk We will publish as soon as Emotion publishes a release with the fix from https://github.com/emotion-js/emotion/pull/1209

Thanks @brentertz!
Was this published already? https://github.com/emotion-js/emotion/commit/41f7ba1c6b7f74cde2c6b6fd5f3333e02e2c154b

Thanks for the heads up @wmonk We'll get right on it.

Awesome thank you!!
On 14 Mar 2019, 13:48 +0000, Brent Ertz<EMAIL_ADDRESS>wrote:

Thanks for the heads up @wmonk We'll get right on it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

This update has been published and is now available on npm as<EMAIL_ADDRESS>

👍
On 14 Mar 2019, 15:37 +0000, Brent Ertz<EMAIL_ADDRESS>wrote:

This update has been published and is now available on npm as<EMAIL_ADDRESS>—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


add documentation for rangeSelector.edge.zIndex

Motivation
Document the new theme value rangeSelector.edge.zIndex
Issue
https://github.com/grommet/grommet/issues/5565
Pull Request
https://github.com/grommet/grommet/pull/5564
Thank you !

Since the solution was not to add a new value to the theme but update the default value, this pull request became useless.


Fix handling of nested left-braces

Previously, nested braces (such as might be used in syntax like .lest || { {} } would fail linting and get corrected to .lest || {{} }.  This commit adjusts the logic so that the former style is considered correct and the latter would be auto-corrected to the former.

As a data point, I ran this across my 120+ internal modules and didn't see any negative effects as a result of the changes.


Generating an OpenAPI Schema automatically

We may still want to tweak it a bit

[ ] Check if it is possible to sort in categories
[ ] Add the generation of the schema to the manual CI

Will close #89 when merged

So how does this work? Is there a command to run? Is it supposed to expose a specific API endpoint?

So how does this work? Is there a command to run? Is it supposed to expose a specific API endpoint?

For now there's a command, I use docker exec -it infra-insalanfr-beta-backend-1 python manage.py generateschema --file openapi-schema.yml when pyyaml and uritemplate are installed in the docker, but I'm thinking about addind a CI to directly generate a schema then a swagger that would be deployed as every other documentation statics

Ok so exploring this a bit, it will require a lot of work to ensure everything in the existing code base is right and correctly documented since we do some serialization by hand. We can put this on hold for later.

Done better in #145


Module "secured_data_warehouse" cannot be found in the module registry at registry.terraform.io.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave +1 or me too comments; they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If the issue is assigned to a user, that user is claiming responsibility for the issue.

Secured Data Warehouse Specifications

Version: v0.1 & v0.2.0
Platform:

Terraform execution logs
https://gist.github.com/guptamukul-google/f7e3222aa2b429473015adbc5f4f3f8a#file-terraform-init-secured-data-warehouse

Expected Behavior
terraform init should work and download secured-data-warehouse terraform module
Actual Behavior
Getting below error when running terraform init
│ Error: Module not found
│
│ Module "secured_data_warehouse" (from main.tf:192) cannot be found in the module registry at registry.terraform.io.
╵

Steps to Reproduce

Have a config with below module:

module "secured-data-warehouse" {
  source  = "terraform-google-modules/secured-data-warehouse/google"
  version = "~> 0.1"

  # with other required variables here
}

Run terraform init

Important Factoids

References

You can check the exact secure data warehouse config here

When using the provision instructions from the Hashicorp site
i.e.
module "secured-data-warehouse" {
  source  = "GoogleCloudPlatform/secured-data-warehouse/google"
  version = "0.2.0"

  # with other required variables here
}

we are getting below error:
╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider hashicorp/google: no available releases match the given constraints >= 2.5.0, >= 3.43.0, >= 3.50.0, >= 3.53.0, ~> 3.53, ~>
│ 3.63, ~> 3.77, ~> 4.0, < 4.0.0, ~> 4.5, ~> 4.11, < 5.0.0
╵

╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider hashicorp/google-beta: no available releases match the given constraints >= 3.43.0, >= 3.50.0, ~> 3.77, ~> 4.0, ~> 4.11, <
│ 5.0.0
╵

We did 2 things to resolve the issue:

Used the provision instructions from the Hashicorp site

i.e.
module "secured-data-warehouse" {
  source  = "GoogleCloudPlatform/secured-data-warehouse/google"
  version = "0.2.0"

  # with other required variables here
}

Changed terraform version FROM:

terraform {
  required_version = "~> 1.0"
  required_providers {
    google      = "~> 4.0"
    google-beta = "~> 4.0"
  }
}

TO:
terraform {
  required_version = ">= 0.13"
  required_providers {
    google      = "~> 3.77"
    google-beta = "~> 3.77"
  }
}


Add symbolic link for docs

Such that we can point GH-pages to the docs-directory (as it doesn't support other directories)

Tested and worked.


test: LandV3 mainnet tests

Description
Tests for the mainnet LandV3 contract
Link to Jira Issue or relevant doc

Added also polygon tests.


Check 'line' for nullptr before using it

Thank you for reporting this. Due to our software release process we cannot directly accept PRs on GitHub but we nevertheless fixed this issue in the update we just released.


PoolThreadCache isn't referencing any shared arena

Motivation:
PoolThreadCache.Cache doesn't have any strong reference, making eligible for GC immediately and causing any shared allocation to be unpooled
Modification:
Mpoving the weak reference to the arena into the Cache, while keeping a strong reference to the Cache.
Result:
Shared allocation(s) are now hitting the arena(s)

PTAL @chrisvest


ctrl+c in gitbash on windows terminal kills ssh remote sessions

Windows Terminal version
1.11.3471.0
Windows build number
10.0.19043.0
Other Software
Gitbash - mintty 3.5.2
Steps to reproduce

Added the gitbash as default profile in Windows Terminal
Logged into ssh remote systems
Pressing ctlr+c(keyboard interrupt) kills the remote sessions and brings the prompt back to git bash

This behavior is not observed when directly running on Gitbash terminal
Expected Behavior
ctlr+c should just interrupt the current process not the sessions
Actual Behavior
Pressing ctlr+c(keyboard interrupt) kills the remote sessions and brings the prompt back to git bash

Bug is also discussed in git for windows:
https://github.com/git-for-windows/git/issues/3657#issuecomment-1024020071

Okay, I thought this issue was with my keyboard. This is happening here multiple times per day, and it's making me crazy. 🤪

This also happen to me when using puTTY via plink command.
Windows Terminal
Version: 1.11.3471.0

huh, so this is like the opposite of #8034

Got the same behavior but also with the older Git Version:
git version 2.35.1.windows.2
It only hapens in the git shell, other shells like powershell work.
Also the keyboard buttons home and end seem to behave weird, but only on some kind of target machines (ARM/Yoctolinux/Busybox in my case) on Ubuntu 20 home and end works. but Ctrl-c also closes the connection.
Running windows Terminal 1.12.10733.0 from the store on:
Windows 11:
21H2
OSBuild: 22000.593
Windows Feature Experience Pack 1000.22000.593.0
Reinstalled Windows Terminal, Reset the settings nothing worked so far.

I noticed this bug a while ago already and haven't found a fix for it. So far I've stuck to 2.34.1, because I really need SSH and ctrl+c to work.
Would be nice to know, if the issue is caused by Windows Terminal or Gitbash, though.

ssh in Command Prompt (on Windows Terminal) has no such issue

Seems to be fixed in git version 2.36.0.windows.1, running on Windows Terminal build 1.12.10982.0.

@joaommartins that's great to hear! I had a sneaking suspicion this was a git bash issue, but I was having a hard time tracking this down.
Can any other folks confirm/? Hopefully we can just close this one out ☺

I can confirm, works fine with 2.36.0 again.

im runnning git version 2.36.0.windows.1 and still seeing this issue. Should i attempt a rollback? or uninstall and re-install git?

Same for me. That's awfull.

marked

im runnning git version 2.36.0.windows.1 and still seeing this issue. Should i attempt a rollback? or uninstall and re-install git?

git for windows is really awfull, uninstalling wont even revert the anonying bug.

I am on 2.36.1.windows.1 and still getting issue,

I am on 2.36.1.windows.1 and still getting issue,

just upgraded (chocolatey) to microsoft-windows-terminal 1.14.1861.0 + git 2.37.0
forks fine (resolved)

I'm having the same issue, but only when using Git Bash. In the PowerShell and CMD, it works correctly.
Any idea?

@OrlinAlvarado not sure that everyone noticed the workaround quoted in git-for-windows/git/issues/3657  and that worked for me

export MSYS=enable_pcon

@OrlinAlvarado not sure that everyone noticed the workaround quoted in git-for-windows/git/issues/3657 and that worked for me

export MSYS=enable_pcon

Hi, @boly38 I added what you suggested, but CTRL+C, exit my ssh session.

@rdoering it's not in the store, but if you are asking when will an official Git for Windows be available with this fix: It is now. https://github.com/git-for-windows/git/releases/tag/v2.36.0.windows.1

@OrlinAlvarado  2.36.0 works.

@Shenmin-Z thanks

I rolled back till https://github.com/git-for-windows/git/releases/tag/v2.32.0.windows.1 to solve this issue. What a long and winding road.

reverted back to 2.30.0 to get this to work again

I decided to use a different terminal for windows.
https://conemu.github.io/

Perfect, works with new Version of Git! 2.38

It really depends on the SSH connection. For example
The latest one (gitbash  v2.38.1) is working fine with SSH connections to AWS EC2 instances.
But it does not work with Vagrant (Oracle VM).
To work with Vagrant (Oracle VM) the working options would be

gitbash v2.32.0.windows
Windows PowerShell

For me it happen when I have X-Forwarding enabled (e.g. -Y or -X) or the equivalent setting in .ssh/config.
Without it - no problems.

This issue made Windows terminal quite useless for me, and I always thought this was a Win Term issue. This thread made me realise that the culprit could be git bash. Problem seems to have gone away for SSH to AWS EC2 (my usecase) with gitbash v2.38.1.

still happening in version 2.39.0.windows.1 using vagrant

Had the same issue with 2.35.0, updated to 2.39.0(2), now it's working fine.

I have fresh windows 10  installations and fresh git version 2.39.0.windows.2 install and see this behavior (am using vagrant)

I had new installation of windows 10 and updated it. Installed git version 2.39.0.windows.2 and it is not working as expected Ctrl+C exits me out of the ssh session and returns to git-bash prompt. vagrant is running the guest machine on virtualbox in my case.

2.39.1 still happening

This issue still observed in Git-2.39.0.

Dito, really annoying! 😭

This still seem to be an issue on git 2.40.0, OpenSSH_9.2.p1
This also happens with these versions of git/OpenSSH using a vanilla powershell window.  after connecting via ssh, issuing a CTRL-C (which is muscle memory to end interrupt the remote task) results in
client_loop: send disconnect: Broken pipe

git --version
git version 2.39.2.windows.1

OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2 does NOT have this problem
The ssh client bundled with git does
To work around it I installed OpenSSH Beta Microsoft.OpenSSH.Beta <IP_ADDRESS> and updated the path to prefer that version.

@blakeduffey Please share more details like, where did you download the OpenSSH Beta Microsoft.OpenSSH.Beta <IP_ADDRESS> for windows 10 host and what file you updated the path to prefer that version. Thanks.

The OpenSSH Beta <IP_ADDRESS> is available via winget
winget install Microsoft.OpenSSH.Beta
Since this default install requires admin (it installs the server component as well) - I use this instead:
msiexec /a https://github.com/PowerShell/Win32-OpenSSH/releases/download/v<IP_ADDRESS>p1-Beta/OpenSSH-Win64-v<IP_ADDRESS>.msi /qb TARGETDIR="$env:LOCALAPPDATA\Programs\OpenSSH"
This will extract the zip into a user profile directory in $env:LOCALAPPDATA
I generally add that path to the USERS path
[Environment]::SetEnvironmentVariable("PATH", $Env:PATH + ";$env:LOCALAPPDATA\Programs\OpenSSH\program files\openssh", [EnvironmentVariableTarget]::User)
That way that version can be invoked from any directory.
If you restart Terminal, you should be able to issue
ssh -V
and get OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2
If I ssh to a remote linux system, run top, and issue CTRL-C - I get the linux prompt back (it doesn't terminate the ssh session)
-B

So to followup on this...
The version of OpenSSH included with git 2.41 reports as:
OpenSSH_9.3p1, OpenSSL 1.1.1u  30 May 2023
The version of OpenSSH available from https://github.com/PowerShell/Win32-OpenSSH/releases reports as:
OpenSSH_for_Windows_9.2p1, LibreSSL 3.7.2
If I connect to server X with the first client, run top, and issue CTRL-C - I get
client_loop: send disconnect: Broken pipe
if I connect to server X with the second client, run top, and issue CTRL-C...
it ends top and the connection remains
Both of these are the latest version available.  Obviously this isn't an issue with Terminal - but rather a certain version of the OpenSSH client.

After a year of suffering, I have a solution.
Reinstall it with "Use external OpenSSH" option.

I was mainly using cmd instead of Gitbash when I use ssh
But I haven't had this symptom for a while even in Gitbash.
Using 1.16.10261.0 and git version 2.39.2.windows.1 BTW
I found today,
vagrant ssh

^c killed the session ONLY in Gitbash
It didn't happen when
ssh -F ssh.config default

where ssh.config was generated by
vagrant ssh-config > ssh.config

It's weird but I think it's happening only in limited situation.
BTW, for external OpenSSH, can we also use /c/Windows/System32/OpenSSH/ssh.exe? I think that's the ssh used in cmd

I have side by side two PCs using Windows as a host, Rocky Linux as a guest, with Vagrant + VirtualBox.  The use case is issuing a vagrant up and vagrant ssh using the git bash, and then hitting Ctrl + C

Win7 SP1, git version 2.35.1.windows.2, vagrant version 2.2.19: Ctrl+C working fine, prints ^C only
Win10 22H2, git version 2.42.0.windows.1, vagrant version 2.3.7: Not working, closes terminal :(


Rebase kubeflow-pipelines

Child of https://github.com/StatCan/kubeflow-pipelines/issues/7
In order to push upstream, we need to get the kubeflow-pipelines repo up to date, we are currently more than 500 commits behind.

Created a branch and rebased on upstream master branch.
https://github.com/StatCan/kubeflow-pipelines/tree/feat-rebase-pipelines
Will create and comment on the next ticket about the items to be careful about.
I noticed there were at least 3 new features.

New items in the NavBar
Recurring Runs
Metrics


update？？？

Why hasn't it been updated yet？

Why should it be updated in your opinion?
On Wed 8. Apr 2020 at 05:05, INHOPEKEEP<EMAIL_ADDRESS>wrote:

Why hasn't it been updated yet？
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/namazso/nSkinz/issues/198#issuecomment-610726155, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AG75EZSPV4YPAPJSF35K3GLRLPSYTANCNFSM4MDS5VGQ
.

@M1XT3NZ
https://github.com/danielkrupinski/Osiris/issues/1336
How to solve this problem?

I have the same problem, and I think it's that what is getting me the vac kick

@M1XT3NZ
danielkrupinski/Osiris#1336
How to solve this problem?

namazso

@namazso
danielkrupinski/Osiris#1336
How to solve this problem?


feat(ethers-providers): expose pending tx_hash with a getter

Motivation
ContractCall::send returns PendingTransactions, there is no way to access the tx hash since its a private field.
Solution
Adding a getter so the user can get a contract call's tx hash.
PR Checklist

[ ] Added Tests
[x] Added Documentation
[ ] Updated the changelog

Interesting, didn't notice the DeRef impl


Usage in Lambda functions

I'm submitting a ...
[ ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[X] question about how to use this project
Summary
Has anyone tried using this package inside an AWS Lambda function?
While locally it is working as expected, when trying to use it in a lambda function, I get an error.
I deployed a simple lambda function with this package installed and I am getting the following error:
"Missing path for FFmpeg, \n Set the FFMPEG_PATH env variable"
This is the code for the lambda function:
const index = async (event, context, cb) => {
  const puppeteer = require('puppeteer-core')
  const chromium = require('chrome-aws-lambda')
  const browser = await puppeteer.launch({
    args: chromium.args,
    defaultViewport: chromium.defaultViewport,
    executablePath: await chromium.executablePath,
    headless: chromium.headless
  })

  const { PuppeteerScreenRecorder } = require('puppeteer-screen-recorder')

  const page = await browser.newPage()
  const recorder = new PuppeteerScreenRecorder(page)
  const recordingsPath = path.resolve(`${os.tmpdir()}/`, 'recordings')
  const timeStamp = Math.floor(Date.now() / 1000)
  const fileName = `${timeStamp}-video.mp4`

  await recorder.start(`${recordingsPath}/video.mp4`)
  await page.waitForTimeout(2000)
  await recorder.stop()
}

Hi @ziverlichson,
Thanks for reachout.
ffmpeg is one of the dependency for puppeteer-screen-recorder extension.
It seems the path of the ffmpeg is not resolved properly inside AWS lambda function.
Could you please ensure whether ffmpeg is installed in AWS environment (ideally it should be installed while installed Puppeteer-screen-recorder as part of dependency)?
you can also point the location the ffmpeg using option.ffmpeg_Path

There is also an option where you can use AWS Layers for ffmpeg and just point the location of the ffmpeg using option.ffmpeg_Path as suggested in the comment by @prasanaworld.
Below is the quick rundown of how to achieve this:

Download and unpack the latest static release build of FFmpeg for Linux amd64 of ffmpeg from here (ffmpeg-release-amd64-static.tar.xz).

Once you download and unpack .tar.xz file you will also need to unpack .tar file (I was using 7-Zip for this).

Then create a folder ffmpeg (anywhere on your file system) and inside it a folder bin and inside bin folder put the file ffmpeg (it has no extension) that you got after unpacking the FFmpeg release build (there are more files/folders that you got after unpacking but you only need ffmpeg file)
Now zip the ffmpeg folder (the one we just created) to .zip extension
You can upload this ffmpeg.zip file anywhere to AWS S3 for the next step (I believe you can accomplish the next step even without upload but I am writing how it's done in the tutorial)
Next, go to AWS console, Lambda > Layers and create a new layer

Name: ffmpeg
Choose option Upload a file from Amazon S3 (here you can also upload your .zip from file system)

Enter AWS S3 url where ffmpeg.zip file is located (if you selected Upload a file from Amazon S3 option)

Choose a runtime you are using in your lambda function from the list (in tutorial it's Python, for me it was Node.js 12x)
For Licence enter this: https://www.ffmpeg.org/legal.html
Click Create

Now in your Lambda function, instantiate Puppeteer object like this:

const recorder = new PuppeteerScreenRecorder(page, { ffmpeg_Path: '/opt/bin/ffmpeg' });

When you create/upload your lambda function (manually, or using serverless) you will need to connect this layer we created to that lambda function. You do this by going into your lambda function, then in the Code section you will an option to Add a layer (click at the bottom).
Choose Custom Layers and select the ffmpeg layer from dropdown list. For version, choose the latest (this is important if you replace your layer with a new version for example, initially it should be 1).
Click Add. Now the ffmpeg layer should be connected to your function.

Here you can find the tutorial I was following when I was building ffmpeg with AWS.
Hope this helps.

Hey @prasanaworld,
I was able to install and use your package within a lambda function! 🥳
I followed @MiselKING's snippet to instantiate the recorder: const recorder = new PuppeteerScreenRecorder(page, { ffmpeg_Path: '/opt/bin/ffmpeg' });
The session is recorded and I am able to play it just fine, however, in my logs, I see this error message:
Error unable to capture video stream: spawn /opt/bin/ffmpeg ENOENT
Any idea why am I seeing this message and how can I fix it?

Closing this issue, since no active discussions were made.

When I tried to install it on lambda, unzip size is over 300+ MB
Anyways to reduce that?
I am already having Chrome and FFMPEG as separate layers.


semver in packages are causing breaking changes

1.0.2 contains breaking change in types.
Trying to use phenyl 1.0.1 causes an error, since the monorepo dependencies are labeled in hat notation (^1.x.x), causing packages to depend on latest version 1.x.x.
In order to prevent this from happening, we should publish 1.0.1 as 1.2.0,
and release version past 1.0.2 as 2.0.0.

It's not problem


fix #148

$ go vet github.com/oragono/oragono/irc
irc/server.go:1605: the cancel function returned by context.WithTimeout should be called, not discarded, to avoid a context leak

I'm still trying to fully understand how context lifecycles work, but this seems to be the correct solution as per:

https://blog.golang.org/context
https://stackoverflow.com/questions/44393995/what-happens-if-i-dont-cancel-a-context

Noice. Taking a good look at the web interface, I ended up just pulling it all out since I don't think it's that useful. I've merged 5e8f86abe08a4a23c7d13457eb7ea01cd7403f31 into master though, since that definitely makes sense.


docs(material/custom-form-field): required prop

required state should also depends on NgControl
The same pattern used in material components - https://github.com/angular/components/blob/6883100b4cfea4c822a5173535d7e710cfcac580/src/material/input/input.ts#L211

Thank you for the contribution but this change is beyond the scope of the example and documentation. Additionally there are several issues with the contribution, e.g. required variable is not being set properly, just the getter.

required variable is not being set properly, just the getter.

It's like addition for code above


Plugin is not working witn Jquery 3.1.0 version

Plugin is not working with Jquery 3.1.0 version

+1
@sravan4rmhyd  Did you find any solution ?


Pico Display 2.0 Button Test

The button test example for the Pico Display does not appear to work for the Pico Display 2.0. I changed DISPLAY_PICO_DISPLAY to DISPLAY_PICO_DISPLAY_2. None of the buttons work and nothing else happens.

The code below seems to be working as expected for me using the latest release - which UF2 are you using (and what board are you using it on?)
# This example shows you a simple, non-interrupt way of reading Pico Display's buttons with a loop that checks to see if buttons are pressed.

import time
from pimoroni import Button
from picographics import PicoGraphics, DISPLAY_PICO_DISPLAY_2, PEN_P4

# We're only using a few colours so we can use a 4 bit/16 colour palette and save RAM!
display = PicoGraphics(display=DISPLAY_PICO_DISPLAY_2, pen_type=PEN_P4, rotate=0)

display.set_backlight(0.5)
display.set_font("bitmap8")

button_a = Button(12)
button_b = Button(13)
button_x = Button(14)
button_y = Button(15)

WHITE = display.create_pen(255, 255, 255)
BLACK = display.create_pen(0, 0, 0)
CYAN = display.create_pen(0, 255, 255)
MAGENTA = display.create_pen(255, 0, 255)
YELLOW = display.create_pen(255, 255, 0)
GREEN = display.create_pen(0, 255, 0)

# sets up a handy function we can call to clear the screen
def clear():
    display.set_pen(BLACK)
    display.clear()
    display.update()

# set up
clear()

while True:
    if button_a.read():                                   # if a button press is detected then...
        clear()                                           # clear to black
        display.set_pen(WHITE)                            # change the pen colour
        display.text("Button A pressed", 10, 10, 240, 4)  # display some text on the screen
        display.update()                                  # update the display
        time.sleep(1)                                     # pause for a sec
        clear()                                           # clear to black again
    elif button_b.read():
        clear()
        display.set_pen(CYAN)
        display.text("Button B pressed", 10, 10, 240, 4)
        display.update()
        time.sleep(1)
        clear()
    elif button_x.read():
        clear()
        display.set_pen(MAGENTA)
        display.text("Button X pressed", 10, 10, 240, 4)
        display.update()
        time.sleep(1)
        clear()
    elif button_y.read():
        clear()
        display.set_pen(YELLOW)
        display.text("Button Y pressed", 10, 10, 240, 4)
        display.update()
        time.sleep(1)
        clear()
    else:
        display.set_pen(GREEN)
        display.text("Press any button!", 10, 10, 240, 4)
        display.update()
    time.sleep(0.1)  # this number is how frequently the Pico checks for button presses

Hmm, I wonder if trying to update() the screen right at the beginning of the program is causing problems - the example is working for me but I did encounter a few MicroPython hardlocks that required a reset.
Does adding a short sleep before triggering the clear function (and invoking the first display.update()) help?
# set up
time.sleep(0.5)  # short pause to allow USB time to initialise
clear()

There are some monumental changes in the 1.19.17 which could cause weirdness. If you can find a minimal failure case I can do some sleuthing.
The example right from GitHub seems to run fine on a Pico at least.

Okay I think I'm barking up the wrong tree here, PEN_P8 - which also requires converting from a palette mode to RGB565 - appears to work...

This should be fixed in v1.19.18 so closing this one for now - let us know if you're still having trouble though!


Automatically install caret as a package dependency

Hi,
I am writing an OpenCPU scoring package that utilizes caret and have it listed in the Imports: section in the package DESCRIPTION file. However, when I try to install my package it fails because the caret package install fails and I have to install caret and its dependencies manually first before installing my package. Is there an easier way to do this? I am looking to have a simple one line install of my package and all Dependencies and Imports get installed.
In the same vein, but maybe a separate issue. Is it possible to tell caret to install new packages required by the R script without prompting? Again, this is to reduce the manual installation aspects.
Thanks!

Hi,
this would be best asked in the official caret section
https://github.com/topepo/caret/issues
Cheers
Tobias

caret installs required packages on demand. You can to check all caret dependencies (Imports and Suggests) and add them to the Imports section in the DESCRIPTION file of your package.

@tobigithub Sorry about that. I thought this was the official caret section
@ddbs Thanks! Let me give this a go. If it doesn't work I'll head on over to the official caret github.


login isssue with github

Issue Type: Feature Request
I am unable to login using my github acciunt
VS Code version: Code 1.63.2 (Universal) (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:37:28.172Z)
OS version: Darwin x64 21.2.0
Restricted Mode: No

/gifPlease


chore(nav-list): create active state class for matching 2018 spec update

Fixes #13084

Doesn't #13084 also call for there to be a rounded outline around the link?

Ahh, didn't see that.

@jelbourn Ready for another look

Hello guys,
Should we expect this to be merged soon?


Fix main-is in package.json

Previously, I was getting a module not found error when I depended on this package.

Thank you @chrismwendt ! 👍


Update button-card.js to work in HA 0.88

Have not tested it in previous versions to see what happens in those versions 🤷♂
This is for issue #57
The result looks something like this...

With this code, all the colors are lost for me.

I tried thas and I also tried merging your changes with @iantrich changes in his pull request (to use the mwc button) and still used your extra  additions...
What is working best for me is the css code I posted in the issue I created on kuuji's github along with the first change to the new element.
Using that all my colours are right but it's still using paper-button of course. I believe the good stuff from kuuji's button is going into core anyway so it's a waiting game. It's a pity Kuuji is no longer maintaining this button.

He’s agreed to test and merge PRs. It’s effectively a community card now, so solutions need to come from the community

ok... @ammmze... still using paper-button though... not mwc-button...

So hopefully I can go back to my normal styling pre-0.88 and it should all be nice again? Great job.

When I use the latest code I get this error: http://192.168.xxx.yyy:8123/local/button-card.js:1:39 Uncaught TypeError: Cannot convert undefined or null to object

Did you do a hard refresh and clear cache? In chrome, F12 and rightclick refresh and select the hard reload and clear cache. The new one is working for me... the button is still slightly smaller than the normal button-card and previous custom-button-card but it works...

Home Assistant throws this error, not Chrome.

Same error for me: https://XXXX.duckdns.org:XXXX/local/custom_ui/button-card/button-card.js:1:39 Uncaught TypeError: Cannot convert undefined or null to object
Position of my button-card is correct (www/custom_ui/button-card/).


Files with #! can not be read

While bone_load() skips the first line of a file if it starts with #!, the reader itself does not. Trying to read such a file results in an error due to the unknown reader macro that was requested to be called.

does the read sub know where it is in a file?
worst case we can define ! as a reader that consumes a line, but then any occurrence of #!foo in the code base will be silently ignored.
Ideally #!foo will only be consumed and ignored if it is the first line.

We can find out about the line in read.
By the way, ! as a reader would not work, because we use symbols as reader names, not single characters, so #!foo is the reader !foo. Sure, Unix has always supported optional whitespace after the #!, but we wouldn't want to limit users to #! foo.
My advice for designers of new Lisp dialects: Just use # as a comment character and use something else (like $ or %) for reader macros etc. That'll help you keep your sanity.


Video 4601 fix audio input device

Contributing to Twilio

All third party contributors acknowledge that any contributions they provide will be made under the same open source license that the open source project is provided under.

[X] I acknowledge that all my contributions will be made under the project's license.

Pull Request Details
JIRA link(s):

VIDEO-4739

Description
This PR fixes the bug addressed in GitHub Issue #462.
When a user is connected to a room and uses an external microphone (or headphones with a built-in microphone), and then disconnects that mic, the other participants can no longer hear the user despite being unmuted. We fixed this bug by adding a new hook (useRestartAudioTrackOnDeviceChange()) to the VideoProvider. This hook restarts the local audio track whenever there is a device change event and the track's mediaStreamTrack.readyState is equal toended.
Burndown
Before review

[ ] Updated CHANGELOG.md if necessary
[X] Added unit tests if necessary
[ ] Updated affected documentation
[X] Verified locally with npm test
[X] Manually sanity tested running locally
[ ] Included screenshot as PR comment (if needed)
[X] Ready for review

Before merge

[ ] Got one or more +1s
[ ] Re-tested if necessary

@timmydoza do you know when this will be released? Thanks

Hey @jszem! A new release that includes this bug fix has been published just now. Please let us know if you run into any other issues, or have any questions!


add proxy config file path for Xcode11 #15819

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

Fix #15819
Description

Add how to set up proxy configuration for Xcode11 or later. Since Xcode11, path of itms has changed. So I add new path information to deliver's document.
This is my first PR to fastlane.
I am always grateful for your help 😄 .  Thank You.
Testing Steps

Ooops !!
Sorry, close this PR to change my email address of commit...


[BUG] BlobServiceClient throws a AuthenticationFailed from SAS connection string

Describe the bug
The BlobServiceClient builds an invalid queue URI from a SAS connection string and the blob operations fail with an AuthenticationFailed exception.
Expected behavior
Using the same connection string was working in the deprecated WindowsAzure.Storage package version 9.3.3, and it is also working if I use that connection string from Microsoft Azure Storage Explorer
Actual behavior (include Exception or Stack Trace)
In my code, I get the SAS token and use it to construct the connection string (note the ? in the SharedAccessSignature)
BlobEndpoint=https://testaccount.blob.core.windows.net;SharedAccessSignature=?sv=2020-02-10&ss=b&srt=c&sp=rwdlacx&se=2020-03-18T19:49:15Z&st=2021-03-18T11:49:15Z&spr=https&sig=mockedsignature
Using that connection string, the BlobServiceClient generates a URL with an extra ?.
https://testaccount.blob.core.windows.net/??sv=2020-02-10&ss=b&srt=c&sp=rwdlacx&se=2020-03-18T19:49:15Z&st=2021-03-18T11:49:15Z&spr=https&sig=mockedsignature
After that, if I try to access data in blob (for example, verify if a container exists), I get the following error:
Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
RequestId:58fa4342-b01e-0065-09cb-159609000000
Time:2021-03-10T16:39:24.4103037Z
Status: 403 (Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.)
ErrorCode: AuthenticationFailed

To Reproduce
In this example, I've generated a SAS token from Azure portal and use it to construct my connection string (I have removed the real signature value from here, but I've used the correct one when I did my test). If I trim the initial ? from the SAS token, it works fine.
var sasToken = "?sv=2020-02-10&ss=b&srt=c&sp=rwdlacx&se=2020-03-18T19:49:15Z&st=2021-03-18T11:49:15Z&spr=https&sig=mockedsignature";

var correctConnectionString =
    $"BlobEndpoint=https://testaccount.blob.core.windows.net;SharedAccessSignature={sasToken.TrimStart('?')}";
var correctBlobClient = new BlobServiceClient(correctConnectionString);

var azureContainer = correctBlobClient.GetBlobContainerClient("test");
await azureContainer.ExistsAsync(); //this works

var wrongConnectionString = $"BlobEndpoint=https://testaccount.blob.core.windows.net;SharedAccessSignature={sasToken}";

var wrongBlobClient = new BlobServiceClient(wrongConnectionString);

azureContainer = wrongBlobClient.GetBlobContainerClient("test");
await azureContainer.ExistsAsync(); //this throws an exception

In my code, I trim the initial ? as a workaround, but as this was working with the previous package and it is also working in Azure Storage Explorer, I would also expect it to work with this package.
Environment:

Name and version of the Library package used: Azure.Storage.Blobs 12.8.0
Hosting platform or OS and .NET runtime version: Azure AppService .NET Framework 4.7.2
IDE and version: Visual Studio 16.8.1

@pilarodriguez According to documentation and samples here the connection string with SAS isn't supposed to have leading "?" in the SAS token part.
Therefore I think that previous version and Storage Explorer handling that is rather unintentional.
Have you considered using BlobServiceClient(Uri, BlobClientOptions) ctor instead of connection string?


update v1 tag to v1.4 release

Hi @tlambert03 ,
Thank you for providing this action!
Could you update the v1 tag of the repository to your latest release in order to prevent the nodejs-related warnings in github workflows that include your action using the v1 tag?
Thanks,
Gregor

thanks, did it!  lemme know if you have any more issues


Bug when saving a field: String containing '$'

Looks like there's an insidious bug where Kotlin is interpreting a field containing a String with a dollar sign ($) as an actual token for replacement in bind parameters:
Exception in thread "main" java.lang.IndexOutOfBoundsException: No group 5
	at java.util.regex.Matcher.start(Matcher.java:375)
	at java.util.regex.Matcher.appendReplacement(Matcher.java:880)
	at com.github.andrewoma.kwery.core.DefaultSession.bindParameters(DefaultSession.kt:219)

Filling a String with any text containing '$' and performing an insert/update should recreate the issue.
A quick study seems to indicate that we could fix this in MysqlDialect::bind().

Wow. Surprised I haven't hit it. I imagine it's in the logging code. Will get on it in the morning (3:30an) here

FYI, rhe parameter binding uses regular expressions under the covers so I'll have to escape dollar signs in the replacement bound value or the regex is treating it as a group.

Makes sense. LMK if you don't find time. I should have time to open a PR this weekend and definitely don't mind contributing. It's an awesome library.
Now get some rest ;)

Fixed in https://github.com/andrewoma/kwery/commit/d901ddd6d403c0bb6dd36569d392f6ec4898ed22. Want me to push out a new release for this and the mysql auto increment issue?

That would be great -- when you have time. Thanks!


[BUG] darkmode not working on auth pages

Describe the bug
When toggeling Darkmode (/config/adminlte.php) the auth pages stay in light mode
Steps To Reproduce
'layout_dark_mode' => true and then visit auth pages
Expected behavior
auth pages sould be in darkmode too

Thanks, I will review this soon...

@Dennis159 Please confirm changes of the Pull Request: #1329 address this situation...


please add if not already in it

What feature do you want to get added on the base engine?
I already posted a help me post about this but if its not in it please add it if you don't know wat I mean here: https://github.com/ShadowMario/FNF-PsychEngine/issues/2719

it already exist go to the charting menu and use the change character event


options argument is defined but never used

options argument is defined but never used, also snippet's in readme.md is outdated

"options" is optional argument
https://nodejs.org/api/dns.html#dnsresolve4hostname-options-callback

Thanks!
What do you mean with snippet's in readme.md is outdated?
Can you update it too? 🙏

tests are broken because the code change, so let keep options


Make validator::new return ValidatorError.

In the future, we need to match specific error type when wen_restart returns.
Make Validator::new() return ValidatorError instead of a String Error.

I think we need to parse the validator error and return a new code here https://github.com/anza-xyz/agave/blob/61473bc5d9b5f0148ee71fb4aea669997343f643/validator/src/main.rs#L2002-L2003 so operators can switch on the return value

I think we need to parse the validator error and return a new code here
https://github.com/anza-xyz/agave/blob/61473bc5d9b5f0148ee71fb4aea669997343f643/validator/src/main.rs#L2002-L2003
so operators can switch on the return value

Planned to that in a separate PR to make this PR small.


Web UI WebSocket Error

Deployment to Azure Kubernetes Service as well as to Docker Desktop Kubernetes results in inability to login and a lot of WebSocker Error messages in the UI.

Docker Desktop Kubernetes version: v1.19.7
AKS version: v1.20.5
Steps to reproduce:

Create namespace: kubectl create namespace cryostat-operator-system
Deploy Operator: kubectl apply -k 'github.com/cryostatio/cryostat-operator//config/default?ref=v2.0.0'
Deploy Cryostat:

cat <<EOF | kubectl apply -n cryostat-operator-system -f -
apiVersion: operator.cryostat.io/v1beta1
kind: Cryostat
metadata:
  name: cryostat-test
spec:
  minimal: false
  enableCertManager: false
EOF

Port-forward to cryostat pod: kubectl port-forward -n cryostat-operator-system pod/cryostat-test-9cb696549-zdkp7 8181 9090 3000

I can see the same issue with Ingress configured on AKS - the following configuration:
apiVersion: operator.cryostat.io/v1beta1
kind: Cryostat
metadata:
  name: cryostat-test
spec:
  minimal: false
  enableCertManager: false
  networkOptions:
    coreConfig:
      annotations:
        nginx.ingress.kubernetes.io/proxy-read-timeout: "7200"
        nginx.ingress.kubernetes.io/proxy-send-timeout: "7200"
        nginx.org/websocket-services: cryostat-test
      ingressSpec:
        rules:
        - host: cryostat.my-private-domain.azure
          http:
            paths:
            - path: /
              pathType: Prefix
              backend:
                service:
                  name: cryostat-test
                  port:
                    number: 8181
    commandConfig:
      annotations:
        nginx.ingress.kubernetes.io/proxy-read-timeout: "7200"
        nginx.ingress.kubernetes.io/proxy-send-timeout: "7200"
        nginx.org/websocket-services: cryostat-command
      ingressSpec:
        rules:
        - host: cryostat-command.my-private-domain.azure
          http:
            paths:
            - path: /
              pathType: Prefix
              backend:
                service:
                  name: cryostat-command
                  port:
                    number: 9090
    grafanaConfig:
      annotations:
        nginx.ingress.kubernetes.io/proxy-read-timeout: "7200"
        nginx.ingress.kubernetes.io/proxy-send-timeout: "7200"
        nginx.org/websocket-services: cryostat-grafana
      ingressSpec:
        rules:
        - host: cryostat-grafana.my-private-domain.azure
          http:
            paths:
            - path: /
              pathType: Prefix
              backend:
                service:
                  name: cryostat-grafana
                  port:
                    number: 3000

Also the specified annotations are not applied to the Ingress resources for some reason.
Expected results:
I should be able to successfully login with the credentials from Kubernetes Secrets resource.

Could you check your browser's devtools and see if there is any more information there about the specific WebSocket error that was encountered? Usually the plain message "WebSocket Error" indicates that the connection couldn't be opened at all, and not an authentication failure. If there is some networking misconfiguration then that could explain both the WebSocket Error message and the inability to log in. When using the Operator and deployed in a non-OpenShift Kubernetes we would also not expect to see that Basic Auth login form - I think the auth login form appearing here is a red herring, and the web-client is just stuck displaying it as the initial loading state, after which it's failing to communicate with Cryostat at all.
Could you do a quick sanity check on your deployment and post the results?
export CRYOSTAT_URL=https://cryostat.my-private-domain.azure # or http:// if no SSL, or use your localhost:8181 for Docker Desktop
curl -vk $CRYOSTAT_URL/health
curl -vk $CRYOSTAT_URL/api/v1/notifications_url
curl -vk -X POST $CRYOSTAT_URL/api/v1/auth
curl -vk \
    --include\
    --no-buffer\
    --header "Connection: Upgrade"\
    --header "Upgrade: websocket"\
    --header "Host: localhost:8181"\
    --header "Origin: https://localhost:8181"\
    --header "Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ=="\
    --header "Sec-WebSocket-Version: 13"\
    $CRYOSTAT_URL/api/v1/notifications

Here are the requested outputs:
curl -vk $CRYOSTAT_URL/health
*   Trying <IP_ADDRESS>:80...
* TCP_NODELAY set
* Connected to cryostat.my-private-domain.azure (<IP_ADDRESS>) port 80 (#0)
> GET /health HTTP/1.1
> Host: cryostat.my-private-domain.azure
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Tue, 09 Nov 2021 15:46:28 GMT
< Content-Type: application/json
< Content-Length: 82
< Connection: keep-alive
<
* Connection #0 to host cryostat.my-private-domain.azure left intact
{"datasourceAvailable":true,"cryostatVersion":"864940f","dashboardAvailable":true}

curl -vk $CRYOSTAT_URL/api/v1/notifications_url
*   Trying <IP_ADDRESS>:80...
* TCP_NODELAY set
* Connected to cryostat.my-private-domain.azure (<IP_ADDRESS>) port 80 (#0)
> GET /api/v1/notifications_url HTTP/1.1
> Host: cryostat.my-private-domain.azure
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Tue, 09 Nov 2021 15:47:41 GMT
< Content-Type: application/json
< Content-Length: 94
< Connection: keep-alive
<
* Connection #0 to host cryostat.my-private-domain.azure left intact
{"notificationsUrl":"wss://cryostat.my-private-domain.azure:80/api/v1/notifications"}

curl -vk -X POST $CRYOSTAT_URL/api/v1/auth
*   Trying <IP_ADDRESS>:80...
* TCP_NODELAY set
* Connected to cryostat.my-private-domain.azure (<IP_ADDRESS>) port 80 (#0)
> POST /api/v1/auth HTTP/1.1
> Host: cryostat.my-private-domain.azure
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Tue, 09 Nov 2021 15:48:49 GMT
< Content-Type: text/plain
< Content-Length: 0
< Connection: keep-alive
<
* Connection #0 to host cryostat.my-private-domain.azure left intact

And the last one with headers:
*   Trying <IP_ADDRESS>:80...
* TCP_NODELAY set
* Connected to cryostat.my-private-domain.azure (<IP_ADDRESS>) port 80 (#0)
> GET /api/v1/notifications HTTP/1.1
> Host: localhost:8181
> User-Agent: curl/7.68.0
> Accept: */*
> Connection: Upgrade
> Upgrade: websocket
> Origin: https://localhost:8181
> Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ==
> Sec-WebSocket-Version: 13
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
< Date: Tue, 09 Nov 2021 15:49:26 GMT
Date: Tue, 09 Nov 2021 15:49:26 GMT
< Content-Type: text/html
Content-Type: text/html
< Content-Length: 146
Content-Length: 146
< Connection: keep-alive
Connection: keep-alive

<

<title>404 Not Found</title>

404 Not Found

nginx

* Connection #0 to host cryostat.my-private-domain.azure left intact

From the browser developer tools I can see that there is always one WebSocket connection to 'wss://cryostat.my-private-domain.azure:80/api/v1/notifications' failed error and one undefined error at NotificationChannel.service.tsx?5f4f:157

It looks like the port number and protocol are not matching up here. Since the ingresses are not using TLS, I would expect the WebSocket protocol should be ws, not wss. Looks like there's a bug there.
@misastovicek would you mind sharing the YAML for the Cryostat deployment? kubectl get deploy cryostat-test -o yaml

Sure, no problem:
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    app.openshift.io/connects-to: cryostat-operator-controller-manager
    deployment.kubernetes.io/revision: "1"
  creationTimestamp: "2021-11-09T15:36:10Z"
  generation: 1
  labels:
    app: cryostat-test
    app.kubernetes.io/name: cryostat
    kind: cryostat
  name: cryostat-test
  namespace: cryostat-operator-system
  ownerReferences:
  - apiVersion: operator.cryostat.io/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: Cryostat
    name: cryostat-test
    uid: 26184d88-f3b2-4f71-aceb-a37eb6b6fbb7
  resourceVersion: "81808941"
  uid: a37abdff-edf8-46a0-aeb7-6211ca33a045
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: cryostat-test
      kind: cryostat
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: cryostat-test
        kind: cryostat
      name: cryostat-test
      namespace: cryostat-operator-system
    spec:
      containers:
      - env:
        - name: CRYOSTAT_SSL_PROXIED
          value: "true"
        - name: CRYOSTAT_ALLOW_UNTRUSTED_SSL
          value: "true"
        - name: CRYOSTAT_WEB_PORT
          value: "8181"
        - name: CRYOSTAT_LISTEN_PORT
          value: "9090"
        - name: CRYOSTAT_CONFIG_PATH
          value: /opt/cryostat.d/conf.d
        - name: CRYOSTAT_ARCHIVE_PATH
          value: /opt/cryostat.d/recordings.d
        - name: CRYOSTAT_TEMPLATE_PATH
          value: /opt/cryostat.d/templates.d
        - name: CRYOSTAT_CLIENTLIB_PATH
          value: /opt/cryostat.d/clientlib.d
        - name: CRYOSTAT_EXT_WEB_PORT
          value: "80"
        - name: CRYOSTAT_WEB_HOST
          value: cryostat.my-private-domain.azure
        - name: CRYOSTAT_EXT_LISTEN_PORT
          value: "80"
        - name: CRYOSTAT_LISTEN_HOST
          value: cryostat-command.my-private-domain.azure
        - name: GRAFANA_DATASOURCE_URL
          value: http://<IP_ADDRESS>:8080
        - name: GRAFANA_DASHBOARD_URL
          value: http://cryostat-grafana.my-private-domain.azure
        - name: CRYOSTAT_DISABLE_SSL
          value: "true"
        envFrom:
        - secretRef:
            name: cryostat-test-jmx-auth
        image: quay.io/cryostat/cryostat:2.0.0
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /health
            port: 8181
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: cryostat-test
        ports:
        - containerPort: 8181
          protocol: TCP
        - containerPort: 9090
          protocol: TCP
        - containerPort: 9091
          protocol: TCP
        resources: {}
        startupProbe:
          failureThreshold: 18
          httpGet:
            path: /health
            port: 8181
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /opt/cryostat.d/conf.d
          name: cryostat-test
          subPath: config
        - mountPath: /opt/cryostat.d/recordings.d
          name: cryostat-test
          subPath: flightrecordings
        - mountPath: /opt/cryostat.d/templates.d
          name: cryostat-test
          subPath: templates
        - mountPath: /opt/cryostat.d/clientlib.d
          name: cryostat-test
          subPath: clientlib
        - mountPath: truststore
          name: cryostat-test
          subPath: truststore
      - env:
        - name: JFR_DATASOURCE_URL
          value: http://<IP_ADDRESS>:8080
        envFrom:
        - secretRef:
            name: cryostat-test-grafana-basic
        image: quay.io/cryostat/cryostat-grafana-dashboard:2.0.0
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /api/health
            port: 3000
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: cryostat-test-grafana
        ports:
        - containerPort: 3000
          protocol: TCP
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      - env:
        - name: LISTEN_HOST
          value: <IP_ADDRESS>
        image: quay.io/cryostat/jfr-datasource:2.0.0
        imagePullPolicy: IfNotPresent
        livenessProbe:
          exec:
            command:
            - curl
            - --fail
            - http://<IP_ADDRESS>:8080
          failureThreshold: 3
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: cryostat-test-jfr-datasource
        ports:
        - containerPort: 8080
          protocol: TCP
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext:
        fsGroup: 18500
      serviceAccount: cryostat-test
      serviceAccountName: cryostat-test
      terminationGracePeriodSeconds: 30
      volumes:
      - name: cryostat-test
        persistentVolumeClaim:
          claimName: cryostat-test

I think the problem here is the operator shouldn't set the CRYOSTAT_SSL_PROXIED environment variable if the Ingress or Route is not using TLS.
@andrewazores does that seem right to you?

I was just thinking the same thing. Cryostat uses CRYOSTAT_SSL_PROXIED when constructing URLs pointing back to itself, like the notification channel WebSocket URL, or download links for recordings and reports. If it's set to true then http -> https, ws -> wss.

Also the specified annotations are not applied to the Ingress resources for some reason.
Hi @misastovicek, do you recall if you added the annotations to the Cryostat custom resource after it was already created?

We have a few inconsistencies where updates to an existing Cryostat custom resource are not propagated to the affected objects. The Ingress configuration is one of those. I've filed #294 to ensure we handle modification properly.

Hi @misastovicek, we just added a fix in the operator to fix the WebSocket protocol used when the configured Ingress do not use TLS. You can try it out by deploying the operator with:
kubectl apply -k 'github.com/cryostatio/cryostat-operator//config/default?ref=v2
This points to our maintenance branch for the 2.0.0 release. I'm unfortunately still seeing some different WebSocket problems in Minikube. So I'll leave this issue open for now, and continue to investigate. (Related issue: https://github.com/cryostatio/cryostat-web/issues/338)

Hi @ebaron, looks much better now! No websocket errors (at least in Azure Kubernetes). Thanks

Glad to hear it!

With our upcoming 2.1 release there are a lot of improvements that have gone into the WebSocket connection handling. I'll close this for now, but please feel free to reopen if issues reoccur in 2.1.


fix(containers): multiple clics on image commit

Multiple clics on image commit button were creating a lot of images for the container.
Related to #2442 .

@xAt0mZ as apart of this PR can you change the success message from Container commited to Image created and the error message from Unable to commit container to Unable to create image.
This would make more sense as the user is creating an image with this feature.


Add @types/node as devDependency to all typescript templates

Description
When following official guides that imports path library or use __dirname in https://vite.dev/guide/build.html#multi-page-app we will encounter typescript errors.

This is not a very good developer experience.
Suggested solution
Add @types/node to devDependencies of vite templates.
Alternative
Add a description section in the document that user needs to import such library or change tsconfig.node.json settings.
Additional context
No response
Validations

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

Seems fair to me 👍 The tricky thing I guess is that users may want to align the node version to the one they're using locally while calling npm create vite. Maybe that can be separately tackled if needed.


[DO NOT MERGE] Add --noDecorate so LUIS/Dispatch names don't get prepended

Fixes #https://github.com/Microsoft/botbuilder-tools/issues/667
Proposed Changes
Add --noDecorate switch so bot.config files don't get pre-pended with the bot name.
Testing
@tomlm/@stevengum Need some help here.

Pull Request Test Coverage Report for Build 1660

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 67.113%

Totals

Change from base Build 1657:
0.0%

Covered Lines:
3961

Relevant Lines:
5628

💛  - Coveralls


chore: patch vite to work with preconstruct dev

While waiting for https://github.com/vitejs/vite/issues/2405 to be fixed, patch Vite with temp fix explained here https://github.com/preconstruct/preconstruct/issues/378#issuecomment-789681043
This should allow Vite demo to work without preconstruct watch!

Just went down this rabbit hole for about a week and using your patch-package strategy worked, thank you!


Firefox dark-theme "below the fold" colours inverted

🐛 Bug Report
Which package?
I don't know - I reported this problem to FormatJS and they requested I file a bug report here (see https://github.com/formatjs/formatjs/issues/1701).
Where is the problem found
All pages on http://formatjs.io.
Describe the bug
The area below the initial view is displayed in inverted colours on a dark background.
To Reproduce

Go to https://formatjs.io
Scroll down

Expected behaviour
Colours should not be inverted.
Screenshots

Environment - Desktop
OS: Ubuntu 12.04
Browser: Firefox
Version: 76.01
Preferences - extensions: dark-theme enabled

Docusaurus version used: not known - please ask the FormatJS team.

Reproducible Demo
see above
-->

In fact, in my browser Firefox I do not observe a similar problem. Perhaps the matter is in the included extensions, or something like that.


DCOS-12458: Fix keyboard tab navigation

This PR fixes JSONEditor tab nav issue and removes tabindex from the documentation link so that it doesn't get in the way.
I also extracted a CNVS issue of missing :focus selectors: https://mesosphere.atlassian.net/browse/DCOS-13175

Nice! :shipit:

Rebased for integration test goodness

LGTM! 🚢


Error in Imagej

Hello,
I am trying to use celltraxx for my phase contrast images using Imagej to track cancer cells. I first wanted to run the sample data given in the folder to later optimize the tuning for my own set of data. However, when I run the Imagej with celltraxx macro via the plugins I can not see the changes in the images. I run to check if something happens when I get this error saying file not found. Can you help me out with this.

Thank you!
Cheers,
Phani

Hello Phani,
Thank you for your interest in using CellTraxx and for informing me of the issue you describe. For this kind of troubleshooting it is most efficient to have a Teams or Zoom session where I can see your screen and find out why that file is missing. If you have the opportunity for such a session, please e-mail me directly at<EMAIL_ADDRESS>and we can agree on a suitable time.
Best wishes,
Børge

Hello Borge,
Thanks for your prompt response. I will reach out to you via mail then
Cheers,
Phani


suggestion: give it a more visible name

I am loving this so far. I started using Plex but there were a few issues so I decided to try Emby. It was better in some ways, but Jellyfin looks promising so I'm kind of bouncing back and forth. Plus, my family still uses Plex so I was looking for a way to sync statuses so they can try the others without issues of sync status. I was going to make my own until I found this.
Anyway, my small suggestion is to give it a less generic name to make it more visible. It took a bit of digging to find this app and I suspect the name might contribute to that. Keep up the good work and thank you!

Hello,
I am glad the tool works for you. About the renaming, Sadly i think it's past the point where i can change the name as there are so many automation going on changing the name right now might break those things. However, I am very open for someone well versed in English language to help fix README/FAQ to be more clear.
Thank you for your suggestion.


determine validation step

What should happen during validation?

List of validation steps for Sprint 20.12 (2020 December)
NLP tools

[ ] GET / must return an object that follows the JSON schema Service

I split this up into individual validation tasks


Creating windows and CRA

Hey,
I'm trying to render some third-party react components (react-table and regraph) inside a new window I'm creating (using react-popout). The components render but without the CSS.
I tried ejecting and enabling css modules. For my own components it's OK I guess, but changing the way react-table and react-graph accept their styles seems like HELL (If even completly possible).
What's the best approach to address this issue? Is there a better solution then ejecting+css modules then change everything? I don't need the flexibility of CSS modules right now, just trying to make the popouts work...
Orel

This question would be better asked on their respective repos.
From our side, however, you can follow https://github.com/facebookincubator/create-react-app/pull/2285 for support for CSS modules which will prevent you from having to eject.


Use /usr/bin/env to select python interpreter in script headers

The following scripts specifically select /usr/bin/python as their interpreter, which is problematic when environments such as Anaconda are used, dependencies are sandboxed, and python selected should be what's resolved by the PATH variable.

utils/api_version.py
deployment/docker-compose/docker-compose.py
build/manage-docker.py

Merged fix: https://github.com/deepsense-ai/seahorse/pull/20


x/build: make sure builders always set $HOME and $USER

The builders don't always set $HOME and $USER.
Fix that, and revert the os/user testing hacks from https://go-review.googlesource.com/c/go/+/107300

For all builders? or all non-windows builder?

$HOME/$USER or equivalent for windows/plan9. But we happen to be fine already for Windows & Plan 9, so this is really only about the Unix builders.


Fix promise Error when creating route to a container

Coverage remained the same at 98.415% when pulling e267c14342030b4141a5711dc028787beb53d08c on n4cr:master into 89dc9808b474dc98bb18a93fd5bdbab9df71af48 on mxstbr:master.

Awesome, thanks so much @n4cr!


Add keepalive config to BGPPeer object

This config option depends on metallb #PR 1017
Signed-off-by: Mohamed Mahmoud<EMAIL_ADDRESS>

LGTM


Fix JSON null handling

Description
JSON assigned NULL values to int8 as a placeholder. This doesn't work out too good if you try to put it through maxlogicaltype.
[
null,
{"col1": 1, "col2": 2, "col3": "asdf"}
]

In the above case, it would assign the first object to INT8, then the second object to STRUCT. It'd then combine the two to deduce that we're reading from a one column table and interpret the whole thing as string.
It now assigns nulls to be ANY, and then purges the result to turn any instances of ANY into STRING. The above example now works as expected.
Fixes # (issue)
Contributor agreement

[x] I have read and agree to the Contributor Agreement.

Feel free to merge this if you don't have any feedback; it's a tiny PR.


Show opening not working on mobile, where the Wiki is hidden

Also check pawn structures

They are both displayed. Perhaps not in a visible spot, but they are there if you scroll down.


RS-544 Fix compatability with new infractl json output

Description
These changes are to make sure the changes from https://github.com/stackrox/infra/pull/706 will be compatible with the rest of stackrox's CI.
Testing Performed
CI

The workflow downloads infractl every time it is needed. Is it infractl version or server version change? I wonder if we need to support the old format, or can switch directly to the new one.
We probably want to copy the change to test-gh-actions first for smoke-testing.
Otherwise LGTM.

Is it infractl version or server version change?
The former.

If .github/workflows/scripts/create-cluster.sh doesn't run on push triggers, I agree we can get rid of the old format. I didn't want to break backward compatibility if it was going to be disruptive to the daily workflow.
@0x656b694d Do you have an example of using test-gh-actions for smoke testing?


[WIP] Specify plans for stability in repo2docker dependency

What do you think? What did I misrepresent or express too vaguely?

Once this is merged we should link to it from places like https://mybinder.readthedocs.io/en/latest/introduction.html#what-can-i-do-with-binder

I like it.


Missing source file

Hi,
teavm writes in the info log that it is missing source files (quite a lot). But compiles and writes sourcefiles successfully. The thing is I am linking to 2 other local maven repositories. Is it possible to configure maven to include those source files from other locations on my harddrive or change the linked maven projects to provide source maps?
Best regards pizzadox9999

Hello. It's not possible. If you have a multi-module project, you need to attach source artifacts for each module, see documentation. You can copy source files manually, or you can use TeaVM plugin for IDEA to run dev server, which serves source files properly. Or you can try to find a way to tell your browser's dev tools to pick sources from specific FS location.


Events in watch mode stop being detected

I am deploying the objects chart on a 1.11.2 K8S cluster with a watch on events only, and after roughly 45-60 min, new events are no longer detected and therefore not sent to Splunk. Bouncing the pod makes the events available again for the same 45-60 min, and the cycle repeats.
I had trace logging enabled and there is absolutely no notification or change in pattern to hint something is off. Searching around, it seems related to https://github.com/abonas/kubeclient/issues/273.
Can you confirm if you see this issue?
I can provide the full trace log if needed, but I'd rather do it via a new ticket in the Splunk Support Portal. Let me know if you'd like to have the log.
Thank you

@gmichels Do you have an active support entitlement with Splunk?  If that is the case, It would be good to have a diag of the indexer to see if there are any errors in addition to looking at the kubeclient link you provided.  Send back the case number if you can open a ticket.

@dbaldwin-splunk sure thing, case number is 1213839.
Shall I go ahead and produce the diag and attach to the ticket? Do you want the trace log as well?

Forgot to mention pull mode works fine. Even when watch events are no longer sent, the pull events (e.g. pods, namespaces, nodes in the below config) continue to be sent over and properly received by Splunk:
objects:
  core:
    v1:
      - name: pods
      - name: namespaces
      - name: nodes
      - name: events
        mode: watch

Events also work just fine when not using mode: watch.

Please attach all logs to the ticket.  Prefer earlier so they don't roll off indexer in case of large volume of ingestion.

I generated the diag yesterday right after your comment and attached to the ticket this morning, along with the pod trace log, for which watching the events API worked for 46 min (timestamps are in EST):

Hey @gmichels!
Apologies for the delay on this one.
I have confirmed I can re-create this behavior.
Working internally to see what we can do to finally resolve this.
Thanks for your patience.

This is fixed in splunk/kube-objects:1.1.2.
The current objects chart defaults to 1.1.0, so until there is a new objects chart release, you need to override the image version in your values file.


history.replace is not working after upgrading to 6.9.2 version

After upgrading from 6.6.1 to 6.9.2 version I have found bugs in my application that calling history.replace does not replace the current url, but acting like push, I mean it stores the previously stored path in history. So clicking back button in browser does not skip this replaced path. For example:

the user is on page /page1;
then he clicked some button and he is redirected to /page2 url;
on that /page2 page there is some useEffect that must replace the current url to /page3, useEffect(() => history.replace('/page3'), []);
user is redirected to /page3 url;
when clicking browser back button he is redirected to /page2 but he must be redirected to /page1, that's how replace should work and previously worked.

I did not change any code, just upgraded this package.

@Pareder by any chance did you find the culprit version with the problem? Trying to decide how I should roll back.


DatePicker and ScrollView combined causes some end-of-month dates to not be selectable

Please list the package(s) involved in the issue, and include the version you are using
"@shopify/ui-extensions": "2023.10.x",
"@shopify/ui-extensions-react": "2023.10.x",
"react": "^18.0.0"
Describe the bug
I use the DatePicker component and a ScrollView wrapping a ChoiceList to enable the merchant to select a date and a time slot. Today on the 30th of November, the 30th of November was enabled in the calendar as expected, but on mouse over or when clicking, the date could not be selected.
December 31st was possible to select, but not January 31st, so it is not consistent.
It turns out that when I remove the BlockSpacer or the ScrollView from my minimum code example below, the date becomes selectable again.
Steps to reproduce the behavior:

Insert the code below in a checkout UI extension
Attempt to select January 31st

Expected behavior
It is possible to select January 31st
Actual behaviour: it is not possible to select January 31st even though it is not in the list of disabled dates. The date is enabled, but not selectable.
Screenshots
Video:
https://drive.google.com/file/d/19NluRljpkmpHutooAI4aC0jcmW5uN2vK/view?usp=sharing
Additional context
Minimum code example below.
When I remove either the BlockSpacer or the ScrollView the last day of e.g. January can be selected, but not if the code is as below:
import moment from 'moment'
import 'moment/locale/pt-br'
import { useState } from 'react'
import {
  BlockStack,
  BlockSpacer,
  ChoiceList,
  DatePicker,
  Heading,
  reactExtension,
  ScrollView,
  useTranslate,
} from '@shopify/ui-extensions-react/checkout'

reactExtension('purchase.checkout.block.render', () => <ExtensionDatePicker />)

const DISABLE_CALENDAR_IN_DAYS = 90

export default function ExtensionDatePicker() {
  const translate = useTranslate()

  const [selectedDate, setSelectedDate] = useState('')
  const [selectedTime, setSelectedTime] = useState('')

  const datesWithoutTimes = [
    "2023-12-01",
    "2023-12-02",
  ]

  return (
    <>
      <BlockStack>
        <Heading level='2'>{translate('header')}</Heading>
        < DatePicker
          selected={selectedDate}
          onChange={setSelectedDate}
          disabled={[...datesWithoutTimes, { end: moment().subtract(1, 'day').format('YYYY-MM-DD') }, { start: moment().add(DISABLE_CALENDAR_IN_DAYS, 'day').format('YYYY-MM-DD') }]}
        />
      </BlockStack>
      <BlockSpacer />
      <BlockStack>
        <ScrollView maxBlockSize={300} hint={{ type: 'pill', content: translate('moreAvailableTimes') }}>
          <ChoiceList
            name='choice'
            value={selectedTime}
            onChange={setSelectedTime}
          >
            <BlockStack spacing='none'>
              {[]}
            </BlockStack>
          </ChoiceList>
        </ScrollView>
      </BlockStack>
    </>
  )
}

@jun-shop Thank you for your input. Sure - I was just providing a minimum example. Instead of {[]} I actually have {getChoices()} in my actual code, which gives a list of choices. The issue is still there whether the list of choices is empty or not.

👋 just wanted to check in and see if any of the suggestions helped, especially placing the BlockStack inside of the ScrollView?

Hi I just removed the block spacer as I originally mentioned as a workaround when I created the issue.
So there is a workaround, but the issue is still open as the bug should be fixed for other developers that might run into the same issue, because it is not intuitive that the above code combination prevents certain dates from being selectable, and can be quite time consuming to debug.


New data: Is "Nuclear electricity production per person" included in "Total"->"Energy production per person"?

Explanation for "Total"->"Energy production per person" data:

Energy production refers to forms of primary energy--petroleum (crude oil, natural gas liquids, and oil from nonconventional sources), natural gas, solid fuels (coal, lignite, and other derived fuels), and combustible renewables and waste--and primary electricity, all converted into tonnes of oil equivalents, calculated by dividing with the population of each country during the given year, counted in tonnes of oil equivalent (toe).

Does it mean that "Nuclear electricity production per person" should be included in "Total"->"Energy production per person" as well?
Because now for some countries "Nuclear electricity production per person" is bigger than "Total"->"Energy production per person".

So if it shouldn't be included than we should mention this in explanation for "Total"->"Energy production per person" data.

Another point.
How could it be that France produces only 0.00221 toe (tons in oil eqv) of energy and uses 4.11 toe?
Import?

Answer from Mattias:

The indicator seems to have been removed from its source (the world bank data page) so I cannot fin any more details about the definition. After a quick googling I found the following definition of "primary electricity" (which is included in the definition of total energy production): "Primary electricity is nuclear, hydraulic, wind, solar, photovoltaic and geothermic electricity.” Hence it would seem that all those things, including nuclear, is included in total production.
What to do: - we could rewrite the definition to include all the energy sources mentioned above (although we are not 100% sure). -a better solution is simply to upload new data with some other source, and give a more detailed definition of the indicator". But I do not know how urgent that would be

.


Feat: Add testing for utils & delete extraneous code;

I deleted a substantial portion of utils: merge, rgb_to_hsv, hsv_to_rbg, darken, and lighten.
And the utils that did survive now have some tests.

I am going to make tests echo the output. I don't think it will break anything, and I want to see my new error messages...

Alright, that's all of the utils tested or deleted.

Nice work on this PR, you really went all out :)

Closes #140.

I think it's good to go!

My one issue still with merge is that it does merge in place if one of the tables is empty... I have a few miscellaneous code changes like that, but I will make an issue and then a PR for those at a later date.
It's no longer being used anywhere, so it won't break anything in the meantime.

This should be good to merge into dev an soon as #150 is merged into it

@5-pebbles Neovim has some nice builtin lua utils, don't forget to check them out :)

@5-pebbles Neovim has some nice builtin lua utils, don't forget to check them out :)

I usually forget those exist... I will try to use them more in the future!

Lol accidentally pushed a failing test.  At least we can see it working now :)


CarmotShieldMixin has @Debug annotation in production jar

Describe the bug
This mod's CarmotShieldMixin class has the @Debug mixin annotation applied, meaning the mixin processor is set to export its target class every time the game starts. This is not necessary in a production environment. Ideally the annotation can simply be removed.
https://github.com/KonSola5/HephaestusPlus/blob/b7d10ce23a7400810455542481ff469ea6111360/src/main/java/konsola5/hephaestusplus/mixin/CarmotShieldMixin.java#L20-L22
To Reproduce

Install Fabric, Hephaestus, HephaestusPlus, Mythic Metals, etc.
Start the game.
The CarmotShield class is exported by the mixin processor to .minecraft/.mixin.out.

Expected behavior
That doesn't happen.
Screenshots
N/A
Crash log or game log (if applicable)
N/A
Mod List

Mod List: click to show

Fabric API
Hephaestus
HephaestusPlus
Mythic Metals
Alloy Forgery
owo-lib

Versions

Loader: Fabric
Fabric API: 0.92.1+1.20.1
Hephaestus: 1.20.1-<IP_ADDRESS>3
HephaestusPlus: 1.1.1
Mythic Metals: 0.19.7

Alloy Forgery: 2.1.2
owo-lib: 0.11.2

Additional context
N/A

Oops, will remove!


[Suggestion] Show total submissions near "Final Results" on the individual game pages

It would be really nice to see how our game ratings stands out from others. For example, 370th place doesn't give me much information... if there were 371 submissions, then our game was bad - if there were 3700 submissions, then our game was pretty good relative to everyone else's. Seeing a "Out of  submissions" lets us know how well we are doing over time. It will show us if we are looking at a rating just from Compo or just from Jam (which is confusing btw, I don't know if my 370th place is just from Jam!).

Was just looking to do something like this today, best I could come up with using current info is:
x = "My ranking"
y = "Total amount of games submitted to category my game is in (Compo/Jam)"
z = "% of *all* submitted games with over 20 ratings"

result = 1 - ( x / (y*z) )


Can't resolve 'polished' in /node_modules/@storybook/ui/node_modules/@storybook/components/dist/Button

Describe the bug
When running build-storybook on Codeship I will get an error:
info clean outputDir..
info => Copying prebuild dll's..
info => Building manager..
info => Loading manager config..
info => Loading presets
info => Compiling manager..
ERR! => Failed to build the manager
ERR! Module not found: Error: Can't resolve 'polished' in '/editor/node_modules/@storybook/ui/node_modules/@storybook/components/dist/Button'
(node:7803) UnhandledPromiseRejectionWarning: ModuleNotFoundError: Module not found: Error: Can't resolve 'polished' in '/editor/node_modules/@storybook/ui/node_modules/@storybook/components/dist/Button'

To Reproduce
Steps to reproduce the behavior:
The problem is I cannot reproduce this locally.
What I can see locally is that I do not have  the 'components' directory in 'editor/node_modules/@storybook/ui/node_modules/@storybook'.
Running the build on codeship will produce errors.
I have tried adding NODE_PATH=src to the build rule, but that did not work
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Code snippets
If applicable, add code samples to help explain your problem.
System:

OS: Codehip: Ubuntu, local: MacOSX
Device:  Macbook Pro 2018
Browser: does not matter in this case: chrome, firefox
Framework: React
Addons: addon-storyshots, addon-storyshots, addon-actions
Version: @storybook/react v 4.1.13

Additional context
Using Yarn
The error started occuring yesterday. I have the feeling some of the dependancies of Storybook may be changed somehow resulting in this issue.

Just read this command on an other issue for 5.0.0.
However I can see the same thing happening here where the dependancy is not avaiable, and even hidden deeper as this requires it Button to be in:
/@storybook/ui/node_modules/@storybook/


Remove the string comparison signature from the throws assertion

In v2.0, we should remove the string comparison signature from the throws assertion type.  It is an awkward signature because it requires that there is also a message string provided in order for the assertion to work correctly.

If anyone wants this functionality (in a convenient way, without having to write a comparison function), the best way to handle that is to write a custom assertion. Here is one I have written:
	QUnit.assert.raisesErrorMessage = function (block, expectedErrorMessage, assertionMessage) {
		if (typeof block !== "function") {
			throw new TypeError("Expected function block as first argument to raisesErrorMessage");
		}

		if (typeof expectedErrorMessage !== "string") {
			throw new TypeError("Expected error message as second argument to raisesErrorMessage");
		}

		if (!assertionMessage) {
			assertionMessage = "Expected error with message \"" + expectedErrorMessage + "\"";
		}

		this.raises(block, function (err) {
			return err.message === expectedErrorMessage;
		}, assertionMessage);
	};


[10.x] Add DatabaseChannel::requireDatabaseType() method

This PR is inspired by the Relation::enforceMorphMap feature. It allows to require the definition of a type for database notification.
Why
To ensure consistency for the notification type saved in the database, it may be useful to require the existence of the databaseType method on notifications which use the database channel.
Indeed, by default when the notification does not have the databaseType method, the type saved in database is the notification class name. If a notification class name changes, the previously database notifications type saved will not be updated, leading to inconsistency.
Solution
Adding a DatabaseChannel::requireDatabaseType() allows to require the usage of a databaseType method on all database notifications.
When sending a notification via the database channel, if the notification do not have a databaseType method, an DatabaseTypeNotificationMissingException exception is thrown.
// Enable database type requirement
DatabaseChannel::requireDatabaseType()
DatabaseChannel::requireDatabaseType(true)

// Disable database type requirement
DatabaseChannel::requireDatabaseType(false)

You may call the requireDatabaseType method in the boot method of your App\Providers\AppServiceProvider class or create a separate service provider if you wish.
There is no breaking changes as  the database type requirement is disabled by default.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Instant Tracking Lerp

There is a set duration for when the tracking lerp is set to a lower value, it is then set instantly to a higher value after that duration, it would be nice if rather then instantly it was set gradually to that new value.
https://github.com/valkyrienyanko/Survivor/blob/734ffafcf1b0c8346cdcc046a5f9d3e086fd6c75/Assets/Scripts/CameraController.cs#L104-L110

Resolved by commit: 7acb6811d2b7e3d7e4943b5c574e7c2b8a7a7c2f.


koa

Can it will be support koa like mongoose!

what exactly is koa? how does it compare to bluebird or es6 promises


Use Python GAPIC package name to determine Python gRPC package name

What
The Python GAPIC package name is currently configured in the GAPIC config. The Python gRPC package name is determined by combining the prefix google.cloud.grpc with the proto package name. For consistency, it would be good to use the same package name structure for both GAPIC and gRPC; that is, any GAPIC package {prefix}.gapic.{suffix} will depend on the gRPC package {prefix}.grpc.{suffix}.
Why
This avoids the verbosity of some proto package names while ensuring a consistent naming strategy across Python packages. See @bjwatson's comment in https://github.com/googleapis/api-client-staging/pull/154
Concerns
The simplest implementation requires artman to read the GAPIC config to obtain the GAPIC package name and pass it to the gRPC package renaming task. I'm wary about introducing a dependency on the GAPIC config for a gRPC pipeline, since none currently exists, and such a dependency is counterintuitive (GAPIC should depend on gRPC, not the other way around).
An alternative is to move package name configuration to the artman config. This has the drawback that the package name must still be propagated to the GAPIC config (so it's duplicated across configs) and introduces the possibility of inconsistency if the GAPIC config is manually edited, but doesn't introduce any new dependencies to the gRPC pipeline.
cc: @bjwatson, @lukesneeringer

@bjwatson After discussing with @lukesneeringer, I'm opposed to this for a few reasons, mostly related to proto dependencies:

It requires artman AND toolkit to know not only about the GAPIC config for the API it is generating, but about all GAPIC configs in existence (since protos can import arbitrary other protos)
A change the configured GAPIC package name in one API potentially entails breaking changes across any API that depends on its protos
We don't have any good way to handle protos for APIs where there is no GAPIC wrapper, since there is no GAPIC config. Furthermore, introducing a GAPIC config down the road for those protos is a breaking change to any API that relies on them

Per offline discussion with @lukesneeringer and @bjwatson, the current state of things will be maintained. In summary:

The package name that appears on PyPI (e.g., proto-google-cloud-errorreporting-v1beta1 and gapic-google-cloud-errorreporting-v1beta1) will be consistent and derived only from the artman config.
The package path within these PyPI packages (e.g., google.cloud.proto.devtools.clouderrorreporting, google.cloud.gapic.errorreporting) may be inconsistent because the Python-language proto package is derived from the proto-language proto package, and the GAPIC package is derived from the GAPIC config.


Scripts for dumping reference json data from ABC database for each mod

also added some fixes to pubmed update scripts.

@azurebrd Just did a test. The current code will not upload the files to s3 if ENV_STATE is set to 'test'. Am I understanding your question correctly?

@azurebrd Just did a test. The current code will not upload the files to s3 if ENV_STATE is set to 'test'. Am I understanding your question correctly?

Yes, sorry about that, I should have taken a break before reviewing.  I thought it was a continue instead of a return.  I made another comment earlier that you were right about that, and resolved that conversation.  Thanks Shuai.

@azurebrd No problem. Thank you for looking over everything! and all the good suggestions/comments!

@azurebrd  just added reference_curie to comment_corrections field.
also got rid of URL/pages for cross_refs.

@azurebrd Thanks!


filter out bad pool per request from adam and johnny

What is the purpose of the change:
Filtering out pool 2159
Linear Task
https://linear.app/osmosis/issue/POL-1363/filter-out-pool-2159
Brief Changelog

Filter out bad pool

Testing and Verifying
This change has been tested locally by rebuilding the website and verified content and links are expected

I commented in slack, but I'm also no longer seeing the Cosmo pool in prod

I reiterate the request to unblock liquidity pool 2159. As confirmed in the thread https://forum.osmosis.zone/t/dao-proposal-establish-transparent-rules-for-token-and-liquidity-pool-blocking/3233 , this pool should not be blocked.


[BUG] Issue with Document Sets Not Inheriting Properties on Communication Site via PnP PowerShell and XML Template

##Description:
When deploying Document Sets on a SharePoint Communication Site using PnP PowerShell along with an XML template, the Document Sets are not inheriting properties into the contained files as expected.
##Steps to Reproduce:
Deploy a Document Set to a SharePoint Communication Site using PnP PowerShell.
The XML template created by powershell before.
After deployment, the Document Set does not inherit properties to its contained files.
##Expected Behavior:
The Document Sets should inherit specified properties into the contained files, as is the standard functionality.
##Actual Behavior:
The properties are not being inherited by the files within the Document Sets.
##Environment:
PnP PowerShell Version: PnP.PowerShell 1.11.0
SharePoint Online
Communication Site
EDIT: Tests in other tenants with other versions of pnp return the same result. Even if the inheritance is activated , the properties wont inherit to the files in the document sets.

@J3D1m0
When you say " the Document Set does not inherit properties to its contained files." are referring to the metadata columns on the files? We just started seeing an issue a couple of weeks ago where we have a document set that is configured to share some columns with the files contained within it but they are not being populated on the files when uploaded. I think this is the same issue you are describing. Can you confirm?

@diver7  yes i can confirm. we created round about 400 sites and deployt via pnp powershell the xml with the document sets and now the shared columns dont get the values from the set.

@J3D1m0
Thanks for the confirmation. I created a new issue on the pnpframework repo because I saw some instructions that told me that issues with this pnp command should be there. Hopefully it will get some attention. Here is the link: https://github.com/pnp/pnpframework/issues/948

Closing the issue here since it is a PnP Framework issue. Once it is fixed there, it will be automatically fixed in here.