Build failes

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux powerai 4.4.0-109-generic #132-Ubuntu SMP Tue Jan 9 20:00:40 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

TensorFlow installed from (source or binary):
source (R1.11)

TensorFlow version (use command below):
R1.11

Python version:
3.5.2

Bazel version (if compiling from source):
1.15.2

GCC/Compiler version (if compiling from source):
5.4.0 20160609

CUDA/cuDNN version:
CUDA 9.2, cuDNN 7.1

GPU model and memory:
4 x  Tesla P100-SXM2-16GB

Exact command to reproduce:
bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package

Describe the problem
Build failes at the end:
cc1plus: warning: unrecognized command line option '-Wno-self-assign'
ERROR: /root/tensorflow/tensorflow/BUILD:592:1: Executing genrule //tensorflow:tensorflow_python_api_gen failed (Exit 1)
Traceback (most recent call last):
File "/root/.cache/bazel/_bazel_root/efb88f6336d9c4a18216fb94287b8d97/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api.runfiles/org_tensorflow/tensorflow/python/tools/api/generator/create_python_api.py", line 27, in
from tensorflow.python.tools.api.generator import doc_srcs
File "/root/.cache/bazel/_bazel_root/efb88f6336d9c4a18216fb94287b8d97/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api.runfiles/org_tensorflow/tensorflow/python/init.py", line 52, in
from tensorflow.core.framework.graph_pb2 import *
File "/root/.cache/bazel/_bazel_root/efb88f6336d9c4a18216fb94287b8d97/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api.runfiles/org_tensorflow/tensorflow/core/framework/graph_pb2.py", line 6, in
from google.protobuf import descriptor as _descriptor
File "/usr/local/lib/python3.5/dist-packages/google/protobuf/init.py", line 37, in
import('pkg_resources').declare_namespace(name)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2927, in
@_call_aside
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2913, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2952, in _initialize_master_working_set
add_activation_listener(lambda dist: dist.activate())
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 956, in subscribe
callback(dist)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2952, in
add_activation_listener(lambda dist: dist.activate())
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2515, in activate
declare_namespace(pkg)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2097, in declare_namespace
_handle_ns(packageName, path_item)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2047, in _handle_ns
_rebuild_mod_path(path, packageName, module)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 2066, in _rebuild_mod_path
orig_path.sort(key=position_in_sys_path)
AttributeError: '_NamespacePath' object has no attribute 'sort'
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 7114.719s, Critical Path: 1859.33s
INFO: 4737 processes: 4737 local.
FAILED: Build did NOT complete successfully

It looks like to be related to https://github.com/pypa/setuptools/issues/1282
Wondering if upgrade setuptools will resolve the issue?

So that shouldn't happen with the 40.2.0 version?

I agree with @yongtang
The stacktrace points to an issue outside tensorflow.
Could you try the recommendation on pypa/setuptools#1282

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

Similar issue is https://github.com/pypa/setuptools/issues/1321 and it's solved in setuptools-40.3.0, so I hope that with latest setuptools build will succeed.


update webpack to webpack-cli

In the new version of webpack, the CLI moved into a separate package: webpack-cli.
So update the Readme.md.

If not set the mode, there will be a warning.
So webpack to  webpack  --mode development


improve pagure unit tests

improve pagure unit tests

What exactly needs to be improved? Can you elaborate, please?
(We have no Pagure unit tests. There are only integration ones.)

What exactly needs to be improved? Can you elaborate, please?
(We have no Pagure unit tests. There are only integration ones.)

created based on  https://github.com/packit-service/ogr/pull/333#pullrequestreview-360895023, but didn't check existing tests so incorectly thought that its units, sorry my bad
so it will be work on integration tests on pagure.service
this is what  you meant by command above?

this still needs better description

I've updated the title and description to make it clear also for others..;)


Bump identity-apps-core version

Purpose
Bump identiy-apps-core version to<EMAIL_ADDRESS>release.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6194175971

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6194175971
Status: success


Remove ml-commons section in the 3.0.0 manifest YAML file

Signed-off-by: Sicheng Song<EMAIL_ADDRESS>Description
Delete ml-commons chunk in the 3.0.0 manifest YAML file.

name: ml-commons
repository: https://github.com/opensearch-project/ml-commons.git
ref: main
platforms:

linux
windows
checks:
gradle:properties:version
gradle:dependencies:opensearch.version: opensearch-ml-plugin

Issues Resolved
Previously ml-commons will fail in CI workflow becuase OpenSearch 3.0 removed some deprecated class. So we remove ml-commons from manifest file temporarily to unblock infra team's CI workflow.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2720 (dea2c23) into main (1d84633) will decrease coverage by 0.33%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2720      +/-   ##
==========================================
- Coverage   94.10%   93.77%   -0.34%
==========================================
  Files         156      156
  Lines        4208     4208
==========================================
- Hits         3960     3946      -14
- Misses        248      262      +14

Impacted Files
Coverage Δ

src/system/temporary_directory.py
64.44% <0.00%> (-28.89%)
:arrow_down:

src/system/os.py
93.75% <0.00%> (-6.25%)
:arrow_down:

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


Error trying to build from code (master branch)

I'm trying to build ripple from the master branch and I'm getting this error time after time:
developer@ubuntu:~/rippled$ scons
scons: Reading SConscript files ...
ValueError: time data 'reproducible build, date unspecified' does not match format '%a %b %d %H:%M:%S %Z %Y':
  File "/home/developer/rippled/SConstruct", line 619:
    config_base(base)
  File "/home/developer/rippled/SConstruct", line 282:
    check_openssl()
  File "/home/developer/rippled/SConstruct", line 133:
    if parse_time(line) < parse_time(BUILD_TIME):
  File "/home/developer/rippled/SConstruct", line 117:
    return time.strptime(t, '%a %b %d %H:%M:%S %Z %Y')
  File "/usr/lib/python2.7/_strptime.py", line 467:
    return _strptime(data_string, format)[0]
  File "/usr/lib/python2.7/_strptime.py", line 325:
    (data_string, format))

Any help?

This problem seems related to the change in the openssl version date as you can see here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794218. It seems it is fixed in the develop branch but it has not been promoted to the master branch. Anyone could confirm?

That seems plausible @alexandrev - I will verify that develop fixes the issue, and if so, this will be resolved automatically when we merge develop into master.

@alexandrev: this issue will be solved shortly, when we update the master branch. I expect it will happen in the next day or two.


Update secret related documentation on how to use Azure Key Vault

Update secret related documentation on how to use Azure Key Vault as a configuration provider. Also includes some adjustments to payment docs.
Strongly related to https://github.com/Altinn/app-lib-dotnet/pull/704

LGTM. Are the deployment/values.yaml changes mentioned/linked anywhere?

Yep. That part is already mentioned here: https://docs.altinn.studio//nb/altinn-studio/reference/configuration/secrets/


Typo in async functions article

Whoops!
There were 5 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/primers/async-functions.md#L6 - WF Tag 'wf_updated_on' must be within the last 7 days.
src/content/en/fundamentals/primers/async-functions.md#L150 - Line must be at most 100 characters
src/content/en/fundamentals/primers/async-functions.md#L153 - Line must be at most 100 characters
src/content/en/fundamentals/primers/async-functions.md#L303 - Line must be at most 100 characters
src/content/en/fundamentals/primers/async-functions.md#L311 - Line must be at most 100 characters

:tada: This has been pushed live to https://developers.google.com/web/


west.yml: Update libmetal for fixes

Update to a newer libmetal snapshot to pickup some upstream fixes
Fixes #26848
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

This also fixes libmetal part of: #26142
We still need an upmerge of open-amp, to completely get rid of the warning, and thus be able to close #26142.

The discussed PRs have been merged, and the manifest for libmetal has been updated. Now, just missing an update for open-amp.


[4.0] Don't classify bridging casts as WillSucceed if the object-to-value cast can fail.

Explanation: When casting from an object type to a bridged Swift value type, classifyDynamicCast would use the cast classification for the target type's bridged object type, which would be trivially WillSucceed for thinks like NSNumber-to-Int or NSError-to-SomeError, even though the bridging itself could fail.
Scope: nsError as? SwiftError casts would miscompile as unconditional casts, crashing the program if the cast failed. This is also a lurking bug in classifying casts from NSNumber or NSValue, though in those cases another optimizer pass that turns the casts into bridging calls fires first and manages to do the right thing.
Issue: SR-2920, rdar://problem/31404281
Risk: Low
Testing: Swift CI, Test case from Jira

@swift-ci Please test

@DougGregor Mind reviewing this for the 4.0 branch?

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - e86ae69be6e9acde89ec4f1c9ac5eceeab50b02b
Test requested by - @jckarter

I have to tweak this a bit to preserve the bridging cast optimization behavior for MaySucceed casts. Stand by.

@swift-ci Please test

@swift-ci Please test

@DougGregor This should be ready for review now.

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - e86ae69be6e9acde89ec4f1c9ac5eceeab50b02b
Test requested by - @jckarter

@jckarter Please run benchmarks before merging it. We need to check that it does not hit the performance.

@swiftix It's a correctness fix, though. I took care to ensure the bridging call optimizations still happen (and, in fact, they should fire in more situations now where they could have been used but we had skipped them before).

@jckarter I do agree with you. But you touch the code in Locals.cpp, which is used by mandatory constant propagation and during optimizations. I just want to be sure we have not lost something along the way. If you are very confident that it could not happen, feel free to merge and our performance bots will report the problem later if there is one.

@swift-ci Please benchmark

@swiftix Since you're here, mind reviewing the cast code for 4.0 to double-check my work?

@jckarter LGTM!

Build comment file:
Build failed before running benchmark.

The benchmark build unfortunately failed because it looks like the builder can't find the benchmark logs. The raw results are there in the build log, though.


rush update --full

#13353 once again re-introduced karma-remap-instanbul into our lockfile, perhaps due to bad merge from master. This PR hopefully will resolve this for the last time.

cc @sarangan12
@xirzec, What could we have done to prevent the regression?

cc @sarangan12
@xirzec, What could we have done to prevent the regression?

@xirzec, What could we have done to prevent the regression?

I gotta figure out if rush is just not doing the right thing, or if I can document a process for handling pnpm-lockfile conflicts that will work for everyone.

@xirzec, What could we have done to prevent the regression?

I gotta figure out if rush is just not doing the right thing, or if I can document a process for handling pnpm-lockfile conflicts that will work for everyone.


Different buttons looks almost identical: "btn-outline-secondary" and "btn-outline-dark disabled"

See plunker: https://plnkr.co/edit/hBi8RhSqgtnLtki0K0KS?p=preview

Yeah, not much to do about this tbh. I'm inclined to wait it out and see how much of an issue it truly becomes for folks. Yes, we could decrease opacity, but that's a color contrast issue. We could further differentiate the grays, but that doesn't buy us much either.

I understand your reasoning. I'm thinking perhaps that btn-outline-secondary looks too much like a disabled button to begin with (and the regular btn-secondary too). For now I've simply stopped using these variants.


Sphinx Design

Hi, I will now start to test some sphinx designs and share them in this thread.
Therefore I will make two screenshots for each design (scree resolution of 2560 x 1440), one of an example page, one of a function from the reference page.
For each theme, I will post a separate comment, so please wait a little bit before you answer in this issue.

sphinx_rtd_theme

sphinx_modern_theme

guzzle_sphinx_theme

#sphinx_modern_theme

python_docs_theme

sphinx_fossasia_theme

Ok, this is something to get started with.
By the way:
The black background of the scenes is sticking out for me a little to much.
I tested some other, maybe a little more decent background colors, what would you say to these:

original: Black

#2B2B2B (from the pycharm dracula colortheme)

#1D2126 (from an online dark theme)

And number 3 in action on the website:

I like guzzle theme. I think it's a good idea to choose some some colors for our examples, as long as all of them use the same color palette. That will give some consistency and a totally different vibe to the site.

I have a slight preference for the RTD theme, though it's mostly because the others don't have much color.

Whatever theme we chose we choose, I consider we would need some JavaScript work for adding some lazy loading things(like pictures and gifs) for the site to be fast enough because our documentation is going to be filled with pictures and videos. :)

I have a slight preference for the RTD theme, though it's mostly because the others don't have much color.

For me the opposite is the case: I don't like the rtd so much because of the color.
I would prefer a design that is plain, with maybe some small accents, but the color will come from the images and videos.

Whatever theme we chose we choose, I consider we would need some JavaScript work for adding some lazy loading things(like pictures and gifs) for the site to be fast enough because our documentation is going to be filled with pictures and videos. :)

Sounds good, but also a bit of work to implement.
When we use javascript, would it then be possible to have the gifs/videos on pause by default, and make them move as soon as you hover over them with the mouse? Just like at the youtube front page.
Sometimes I find it a little strenuous  to have lots of moving gifs on the screen  (just like Homer's website)

When we use javascript, would it then be possible to have the gifs/videos on pause by default, and make them move as soon as you hover over them with the mouse? Just like at the youtube front page.

Everything is possible. But I don't think standard themes allow us to changes these JavaScripts directly. If they allow it is good. Or else, we can make fork out of it and customize it. :)

Yes, we will most likely need to have a custom theme in the future.
I'm neutral about whether the color comes from the examples only or the theme itself. But what I do not like from the ones that are really plain is that the documentation is hard to read for me. For example, in the second screenshot of python_docs_theme, there are no font colors or accents anywhere and I can barely look at that page. Eww.

Update: once #324 is merged, then all that stands between us and a dedicated site for documentation (for example on ReadTheDocs) is this issue.
I suggest we quickly choose one of the themes posted by @kolibril13 and use that for the time being. After all, not a ton of people would be visiting the RTD website as soon as that's up. We can keep tweaking this theme as we approach a release version.


[Bug] Module 'invariant' not found on production environments

Expected behavior
The invariant module appears to be used only for debugging purposes on non-production environments, so it shouldn't need to be installed on production environments.
Current behavior
When building my project with webpack for production, an error is thrown:
ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve 'invariant' in '~/Projects/website/node_modules/@researchgate/react-intersection-observer/lib/es'
<EMAIL_ADDRESS>12:0-34
<EMAIL_ADDRESS> @ ./src/components/ProductPaymentMethods.js
 @ ./src/pages/Page.js
 @ ./src/App.js
 @ ./server/render.js
 @ ./server/app.js
 @ ./server/index.js

I assume this happens since npm doesn't install devDependencies on production environments. IntersectionObserver tries to import invariant (although it's not used) and then fails to find it.
Steps to reproduce

Use IntersectionObserver in a project
Compile the project with webpack in a production environment
Tada! 🎉

Context (environment)

Version: 0.3.0
Platform: x86_64 GNU/Linux

Thanks for reporting this bug. This is obviously wrong, seems we made a mistake there.
Will release a new version tomorrow.


Rotation degrees are opposite.

In the python module, Image.py rotation with positive degrees returns a rotated image with the given number of degrees counterclockwise around its center, but not clockwise. So the function rotate90, rotate270, rotate, rotate_without_crop give out results with left and right opposite.
And also to mention, rotate function can't rotate with certain degrees when max_left_raotion == max_right_rotation.

Hi @YiweiZou - so in your case the rotate function always results in the rotations going in the wrong direction? So for example:
p.rotate(probability=0.7, max_left_rotation=0, max_right_rotation=10)

This would result in a rotation going in the wrong direction (counter clockwise)?
As for the max_left_rotation == max_right_rotation that might well be a bug and I will investigate that....

Hi @YiweiZou - so in your case the rotate function always results in the rotations going in the wrong direction? So for example:
p.rotate(probability=0.7, max_left_rotation=0, max_right_rotation=10)

This would result in a rotation going in the wrong direction (counter clockwise)?
As for the max_left_rotation == max_right_rotation that might well be a bug and I will investigate that....

Yes, for the example, the images would randomly rotation within 0-10 degrees counterclockwise.

Hi @YiweiZou - so in your case the rotate function always results in the rotations going in the wrong direction? So for example:
p.rotate(probability=0.7, max_left_rotation=0, max_right_rotation=10)

This would result in a rotation going in the wrong direction (counter clockwise)?
As for the max_left_rotation == max_right_rotation that might well be a bug and I will investigate that....

Hi @mdbloice ,
After reviewing the Operations.py file, I noticed that you assigned the angle of rotation as positive for clockwise rotation and negative for anticlockwise rotation. However, this is opposite to the default behavior of the image.rotate() method. In image.rotate() method, when a positive angle of rotation is provided, it performs an anticlockwise rotation, whereas a negative angle results in a clockwise rotation.
To address this inconsistency, I added a negative sign whenever you are passing the angle in the image.rotate() method in the Operations.py file. By adjusting the sign of the angle of rotation passed to the image.rotate() method, I ensured that the rotations are now correctly aligned with the intended clockwise and anticlockwise directions.
Since implementing these modifications I have tested, and all rotations have been functioning correctly in my local system.
Thank you.


Feat/signing support

:tada: This PR is included in version 2.0.1-beta.67 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Currency: support symbol-alt-narrow

CLDR exposes also symbol-alt-narrow for some currencies (since CLDR 24: http://cldr.unicode.org/index/downloads/cldr-24)
Example in 'et' locale Globalize.currencyFormatter( "PLN" )( 1 ) - outputs:
1,00 PLN
With symbol-alt-narrow support the output should be:
1,00 zł

CLDR indeed has the data. But, it doesn't specify how to use it. This same topic has been discussed in https://github.com/tc39/ecma402/issues/4. So, the first step is to define how this could be supported.
I recommend researching CLDR tickets (e.g., http://unicode.org/cldr/trac/search?changeset=on&milestone=on&ticket=on&wiki=on&q=symbol+alt&page=2&noquickjump=1) and its documentation (http://www.unicode.org/reports/tr35/tr35-numbers.html#Currencies) to find substance to elaborate a suggestion. Perhaps, a variant subtag could be specified in the locale to define the preference for the alt symbol. Perhaps, an additional option on the currencyFormatter could be specified. Either way, I suggest that whatever is considered here should be aligned with CLDR.

For my purpose an additional option for the currencyFormatter() would be sufficient.
Quote from the change log:

The narrow forms are intended to be as narrow as possible, however, there may be no good narrow term for some units in some languages. As always, narrow forms are not necessary unique; they should only be used where the context is sufficiently clear (eg, it is a length).

I think that adding an option named 'narrow' to currencyFormatter() would then do exactly what it's meant to. As the usage is context sensitive I don't think that would be the perfect place. It wouldn't make sense to make it some global option.

A {form: "narrow"} option sounds good to me. Basically, it should try symbol-alt-narrow || symbol given narrow is not available for all currencies.
Given the change log makes reference for the narrow form. But, http://www.unicode.org/reports/tr35/tr35-numbers.html#Currencies does not. I believe we should request it to be inlcuded by filing a ticket on CLDR (http://unicode.org/cldr/trac/) as a preliminary step. If you agree, please do so and add a new comment here with the ticket number. I will help bringing this to focus on the CLDR committee.

There seems to be already a ticket: http://unicode.org/cldr/trac/ticket/8461

It's targeted for CLDR 28, so we could give the implementation a try. Basically, what needs update is:

https://github.com/jquery/globalize/blob/master/src/currency.js
https://github.com/jquery/globalize/blob/master/src/currency/symbol-properties.js#L18-L22

Feel free to submit a Pull Request. :)

I'll better leave this to someone who knows what he is doing :)
Anyway thanks in advance - can't wait to use this.

Looks like this has now been added to the spec: http://unicode.org/cldr/trac/ticket/8405#comment:7
Is there any movement here or is someone working on an implementation? It would be great to get this feature!

Hey @zolitch, no one seems to be working on it, but I believe it's a quick change. Would you be interested in implementing it? Just let me know if you have any questions? Thanks

I can't right now but can do if I get some time over the next week or. Provided a workaround on the project I'm working on right now.

Has this been integrated into the current version? Would be a useful feature to have, any ETA on this.

Hi @sreekanthjnayar thanks for your interest. The implementation is close to complete, it misses some review fixes #631 (which stalled). Would you be interested in moving forward with this work (see #631)? Just let me know if you have any questions? Thanks

This change is technically ready to merge. It's waiting on Foundation matters.

This is good to go as you can see in #738 which shows all checks passing, including @gethinwebster's signature which I have also verified is in the database.

Yeap. Thanks... @gethinwebster has re-signed it.


How to disable editing of country code ?

Can you please let me know, how we can disable the editing of country code in input field.
For eg: if I select India for india it's +91. So I want nobody can edit this +91 to something else.
Please acknowledge.

There is no way to do it right now. I don't plan to add it in near future.


feat: no_std eth rpc types

Description

[!NOTE]
Stacked ontop of #1248

Adds support for no_std in alloy-rpc-types-eth.

Can you update the workflow and no_std script from alloy-rs/core?

Can you update the workflow and no_std script from alloy-rs/core? Would like them to be the same

Yes definitely, mind if I do this in another PR to unblock this?


Create installer.php Redirect

Redirects visitors automatically to the installer.php page.

Hi, thank you for wanting to contribute to Pockethold,
Alas, adding another file with the sole purpose of redirecting to another file is not something I believe is necessary. One of my goals with Pockethold is to have it as a single-file installer, and if I was to do this, I could just as well go all out and split the installer into several other pieces (Html in one file, php in one and JS in one file).


[Bug]: missing treesitter-based highlight for JS/TS properties after breaking nvim-treesitter update

Your minimal.lua config
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  {
    "olimorris/onedarkpro.nvim",
    opts = {
      -- Your OneDarkPro config goes here
    },
    config = true
  },

  { "nvim-treesitter/nvim-treesitter", build = ":TSUpdate" },

  -- Delete if you do not require LSP
  {
    "VonHeikemen/lsp-zero.nvim",
    branch = "v2.x",
    dependencies = {
      -- LSP Support
      {"neovim/nvim-lspconfig"},             -- Required
      {                                      -- Optional
        "williamboman/mason.nvim",
        build = function()
          pcall(vim.cmd, "MasonUpdate")
        end,
      },
      {"williamboman/mason-lspconfig.nvim"}, -- Optional

      -- Autocompletion
      {"hrsh7th/nvim-cmp"},     -- Required
      {"hrsh7th/cmp-nvim-lsp"}, -- Required
      {"L3MON4D3/LuaSnip"},     -- Required
    },
    config = function()
      local lsp = require("lsp-zero").preset({})

      lsp.on_attach(function(client, bufnr)
        lsp.default_keymaps({buffer = bufnr})
      end)

      lsp.ensure_installed({ "lua_ls", "tsserver" })

      -- (Optional) Configure lua language server for neovim
      require("lspconfig").lua_ls.setup(lsp.nvim_lua_ls())

      lsp.setup()
    end
  }

  -- add any other plugins here
}

require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

-- setup treesitter
local ok, treesitter = pcall(require, "nvim-treesitter.configs")
if ok then
  treesitter.setup({
    ensure_installed = "all",
    ignore_install = { "phpdoc" }, -- list of parser which cause issues or crashes
    highlight = { enable = true },
  })
end

vim.cmd("colorscheme onedark")

Error messages
No response
Describe the bug
Properties in JS/TS objects are not properly highlighted, especially when the language server is not active to provide semantic tokens.
The comment at the top indicates if the file was a JS or TS file.
Without the language server:

With the language server:

:point_up: this one may be all good

:point_up: still missing for one property

Probably unrelated, but interesting: the highlighting of brackets is different in TS vs JS.
Reproduce the bug

Edit a JS or TS file:// ts
const obj = {
    key: 'value',
    other: () => {},
}

View the outcome.

Final checks

[X] I have made sure this issue exists in the latest version of the plugin
[X] I have tested with the minimal.lua config file above and still get the issue
[X] I have confirmed that Treesitter is working correctly by running :checkhealth treesitter
[X] If related to semantic tokens, I have checked that my LSP server supports them
[X] I have made sure this is not a duplicate issue

+1
More details on the changes are here: https://www.reddit.com/r/neovim/comments/19aratu/psa_nvimtreesitter_breaking_changes_on_highlight/
For me, the lack of syntax coloring is really quite evident in markdown files where even bold/italic type styling is gone, heading styling is gone, etc.

+1
More details on the changes are here: https://www.reddit.com/r/neovim/comments/19aratu/psa_nvimtreesitter_breaking_changes_on_highlight/
For me, the lack of syntax coloring is really quite evident in markdown files where even bold/italic type styling is gone, heading styling is gone, etc.

@zmre this was fixed in #222

@mmirus can you let me know if the latest commit resolve this?

Yep! There are still differences between JS and TS, but that's probably for a separate ticket if anyone cares. I haven't verified the colors that are being used now are "correct" (i.e., what they were previously or what's in the vscode theme), but nothing is lacking color now.
Thank you!
Without LSP

With LSP

I think I still have it on my todolist to unify the TS/JS styling actually. I think we discussed it over a year ago and I never quite got around to doing it.


docs/kv address example updates to fix non-unique indexes range scenario.

Updates to the kv-address-book example smart contract:

got rid of the using namespace eosio; and using namespace std; and use it explicitly everywhere else to help the user see better from what namespace each object comes from; we assume the users reading this example are beginners and need this explicit style of coding
fix the non-unique indexes to be able to showcase the get all persons in the addressbook with the same last name scenario.

this can not be merged yet, because we can't yet get rid of the using namespace statements


(follow Up)Facing issues in executing different spec files in desired order with rspec #1899

thanks your quick response( to request no 1900).I have gone through link that you suggested.i have few clarifications on below provided code.
Could you please provide your answers on below points.
1.In which file i need to add below provided code( is it spec_helper.rb or new spec file)?
1.1 if it is spec_helper,now different scrum team using same spec_helper file. will it affect others execution,if so how to handle it?
1.2  can archive  same by  creating new spec file and add below code to that.will it execute all other spec files in desired order by running new spec?
2.what is the significance of numerics in below code? as per my understanding groups execution order will be based on tags and the order will be feature,request and model.

lets say i have  3 test under each spec file . can the below code support in executing test in written order ? if not, could tell me how to that?

Could you point me  to the link that gives detailed info about rspec for beginners?

RSpec.configure do |config|
config.register_ordering(:global) do |items|
items.sort_by do |group|
case group.metadata[:type]
when :feature then 50
when :request then 40
when :model then 10
else 20
end
end
end
end
thanks in advance,
Chandana

Please do not open new duplicates for your issues.  Please respond to the one where we've had the conversation (#1900) and I'll be happy to answer there.  Creating new threads just creates noise in our issue tracker.

sure..will do that. apologies for inconvenience.


[FR] - CLI - Command to check which pools a certificate is delegating to

Assuming that we mean "stake address" as opposed to "certificate", this functionality seems to be subsumed by #1053. Closing this.


If I import a component that has a fragment as props, and I import that and render as suggested in the docs, e.g.
import FragmentedComponent from 'components/FragmentedComponent';

storiesOf('FragmentedComponent')
  .add('it works', () => {
    const props = {
      exampleFragmentProp: {
        name: "blah"
      }
    };
    return <StubContainer Component={FragmentedComponent} props={props}/>;
  })

Then I get the following error
Invariant Violation: `Relay(Component)` tried to render a context that was not valid this means that `Relay(Component)` was rendered outside of a query renderer.

This makes total sense, but what's the best way of setting up Relay for the purposes of Storybook? Should we wrap each component to be displayed in a QueryRenderer?  Or is there some global config that can work?

Looks to me like this got replaced with https://github.com/artsy/eigen/blob/467d6b75fd3c8b55ec6ff37489aba7e10de8bddd/mocks/react-relay.js in the Artsy codebases, so I'd copy that

Ah OK...so you'd use that instead of the StubContainer entirely?
I'm not too familiar with Storybook mocks, in this case would you add them using a decorator like this?

Managed to get this working by creating a decorator:
import React from 'react'
import { RelayEnvironmentProvider } from 'react-relay-offline'
import { createMockEnvironment } from 'relay-test-utils'

export function relayProviderDecorator(story) {
    return (
        <RelayEnvironmentProvider environment={createMockEnvironment()}>
            {story()}
        </RelayEnvironmentProvider>
    )
}

Then the example above worked well for me! Perhaps the mock approach works as well (or solves a slightly different problem).


The default file extension, default file language mode

Introduction
Hello, I couldn't find in the settings how to choose the default syntax. I didn't have similar problems in npp - a smaller ide
When I want to put the code (for example from stackoverflow) and do not want to format the entire document, I should - create a new file, but this file will be created in txt format(in the program for developers), and if you hit ctrl+s, the file will pick up the first line as a title(in more cases | but I found: workbench.editor.untitled.labelFormat, and I'm sure you need to change the default param to the "name" instead), and then you will need to type\select the extension for this file... fyi: hit ctrl+s in npp and I can working with it without saving..
i.e. this is a big time waste, instead of me just doing:

2 clicks \ Ctrl+N
Ctrl+V
> Format
Ctrl+A + Ctrl+C
Ctrl+W > Don't save

ps I know about editor.formatOnPaste, and the situation is taken as an example

Describe the feature you'd like.
I need option (editor.defaultSyntax or editor.defaultExtension, selector) for the default extension, because I can't format a (code in) file (that I haven't saved anywhere), because the formatter doesn't know its extension. [And\Or] Saving a file & Choosing a file format every time is too time-consuming.
Same for the left folder tree (explorer.applyDefaultExtension), my idea for it - are: If the user did not specify an extension, select the default one from editor.defaultExtension

files.defaultLanguage ?

xd, @usernamehw 👍
I was looking for: [selector] \ syntax \ extension, but it's not too late to update_it \ expand_tags 🙂
btw, it does not cancel the 2 point - about the folder tree 🙃

You can also select the language mode for an unsaved file with the command "Change Language mode".
@isidorn for

Same for the left folder tree (explorer.applyDefaultExtension), my idea for it - are: If the user did not specify an extension, select the default one from editor.defaultExtension

files.defaultLanguage is the way to go here
We will not add anything apart from this. Thus closing

@isidorn re-read again please, files.defaultLanguage is not a solution for the folder tree


super user is localhost, and don't persist superuser

Companion PR: https://github.com/dolthub/dolt/pull/3810

Should definitely squash and merge, we probably shouldn't have why do you people keep giving me conflicts as one of our commit messages in the history.


notebook 15 dependency error

Dependency Error on 15.langchain-quickstart-with-llama-2.ipynb
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
transformers 4.33.2 requires tokenizers!=0.11.3,<0.14,>=0.11.1, but you have tokenizers 0.14.0 which is incompatible.

This happens in the llava notebook as well...


Storybook v8 migration PoC

PoC to demonstrate the migration process and what's required.

The main job is to comply with: https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#titles-are-statically-computed. We can't opt-out anymore in v8, so we need to do some grunt work to:

Remove id from the default export: We relinquish control.
Exposes the name 'directly' from the template, not as the result of a function
This PR demonstrates the grunt work on a select set of stories (and 🗑 the other, so that it builds)

Run the migration script https://storybook.js.org/docs/migration-guide. The result is in 2e66499d49f1d84b500c5d92c6daec976d7d8012

For now, I checked:

that the path query param fit with what's present on the CDN
Shadow Part is reflected on both the HTML preview and code preview
Control (attribute changes) is reflected on both the HTML preview and code preview

I tested locally and aside from the default story names (which really has no impact) the only "odd" thing I noticed is that the atomic-format-* stories now appear both under ResultList/ResultNumber/Format and NumericFacet/Format (they used to only appear under the former).
I believe this will cause no issues on the docs site.

And they are actually two different stories, so it was most likely a bug even IMO


racecheck

https://github.com/cakebytheoceanLuo/dogqc/issues/53#issuecomment-995854344

Code: https://github.com/cakebytheoceanLuo/dogqc/pull/54

Recheck my stackoverflow question.


Support for scrambling messages with HTML in them

Is your feature request related to a problem? Please describe.
When composing messages, it's often helpful to use bold and italics to add tonal information. This can be done through a markdown module such as df-chat-enhance, or alternatively by writing simple HTML directly into the message editor, such as Hello world.
Currently, it appears that Polyglot is skipping messages that contain any HTML content. I haven't checked the source code to verify this assumption, but given the consistent behavior, I'm fairly certain of it.
Describe the solution you'd like
First off- I don't think its feasible or necessary to apply the HTML tags to the scrambled version of messages. After all, it wouldn't make much sense to. If you don't understand a foreign language, you're likely going to have a hard time discerning tonal indicators that may be used by native speakers.
So, to solve this, I'd to about it via one of two ways:

If Polyglot is scrambling messages before they've been committed to the HTML, I'd simply use the browsers DOMParser API on the message text, then extract the text that should be scrambled via .body.innerText on the returned HTMLDocument.
If Polyglot is scrambling messages after they've been committed to the HTML, then simply use a property like .innerText on the DOM node. However, this approach would have some unintended side effects- for example, I'm working on a chat enhancement module to replace df-chat-enhance, and it appends (edited) to messages that have been edited. Since Polyglot would be getting the text from the .innerText property, it would include this edited marker in the text to be scrambled.

Additional context
I'd be willing to implement this feature myself, so long as it would be accepted.

You are correct, it ignores text that starts with a <. It's a leftover from 2021 when links in a ChatMessage.content started with anchors (<a ) and Polyglot mistankenly scrambled them.
Nowadays, links on ChatMessage.content are just plaintext and Polyglot actually checks for things like @ and :// instead, so I think it can start accepting HTML stuff back again.

Btw I've released a version yesterday that should accept HTML elements now, let me know if that's enough for you to work with so this issue can be closed.

I was going to say something about the [object Object] bug, but it seems you've gotten that fixed. Works on my end. Cheers!


Cruelly reveling in council unraveling

Hopefully this isn't seen as mean-spirited!

I must have missed the news but I love this.


Abort ping test if pings are too long

Shiverwarp complained recently that he was getting login ping test times of 23000+ msec and it was taking seemingly forever to login. I sympathize; I usually get <30 msec and the longest I've see in a 10-ping test is a bit more than 800 - which would still be an intolerably slow connection. And to think it took 10 pings to get that "average".
I can't imagine what caused Shiverwarp's insanely bad connection, but if it took 4 minutes to run the first test and decide it is time to retry, seems to me that we could recognize way earlier - as early as the very first ping - that this connection is a no-go.

Comparing ping average times with goals and thresholds in floating point seems right, but displaying them as integers, calculated either by Math.round() or Math.floor(), is problematic. If your threshold calculation says you cannot exceed 30.2 msec and you generate 30.4, it will fail, and using Math.round, will report "you wanted 30 msec but got 30 msec, so it failed".  I changed it to display floating point results in floating point. So far, it always seems to display with a single digit to the right of the decimal point, which seems fine.

If you get a really slow connection, it will be obvious early on that it will be too slow.
Allow configuration for "PingAbortTrigger" triggers.

If "pingTestAbort" has "4:3|1:10", you are specifying:
Retry if 4 pings exceed 3 times average historical ping
Retry if 1 ping exceeds 10 times average historical ping
Default is "1:10"
On the PingOptionsPanel, you can add rows to specify additional abort triggers or delete rows to remove them. If you try to delete the last row, it just zeroes it - which will leave the property empty.
I think the GUI is pretty spiffy.
PingManager now checks those triggers after each ping it submits. If that results in any trigger firing - 4 exceeding 3 times historical average or 1 exceeding 10 times historical average, from the above example - PingManager aborts the ping test and returns the test with the trigger that fired to LoginManager.
Could be that the aborted ping test was still good enough, but if not, it reports that the ping test aborted and it moves on to the next timein attempt.

Eyes a little glazed but...

Did you try it out? I'll merge it and you can see for yourself.


Implement Tweets on Home Page as in Twitter and Loklak Search

Looking at the start page: The tweets are not showing up in the same way as twitter, e.g. images are missing. My understanding was, that this gets implemented in the same way as the search, but there is no change here?
This was partly discussed here: https://github.com/loklak/loklak_webclient/issues/227

Is this live? Does not seem to work on test.loklak.net


Plug-in API

I've two queries--

Does Kanboard has any plug-in API like WordPress has? Cause I made some modification in Kanboard. So now I wanna share this with every body. If there is a plug-in API that should be better for me.

Which framework you've used to develop Kanboard?

Thank You.

There is no plugin api at the moment.
As you can see in the source code, there is no framework, it's just a MVC web application that use a couple of libraries...


Understanding the live rate limitations

Hey Anurag, this project looks really interesting and I was wondering if you can let me know if I understand it's limitations correctly.

At the moment, as transferwise at maximum blocks live rate for first three of all your transfers booked. Thus, the batch also gets only the first three or less existing transfers you have to compare for better rates.

Let's say I want to make 30 transfers and fund/fulfill a single transfer at maximum 4 days after creating it. Does this mean in the worst case scenario (every transfer funds after the full 4 days), it would take me 40 days to process all 30 transfers?
I hope I'm making sense :)
Thanks,
Matthias

@mmlkrx
With the current limitations on TransferWise, you can only create 3 quotes with guaranteed transfer rate e.g. your quoted transfer rates would last for the next X hours.
After 3 unset guaranteed-quote transfers, you can still create new quotes on TransferWise, but they will not have any guaranteed rates, rather TransferWise will use the future instantaneous rates when the actual payment/transfer occurs.
Hope this helps. Thanks.

@mmlkrx
I think @gsbabil answered it to the point.
Seems like recently they are reducing the number of quotes with guaranteed rates for specific accounts, where they suspect multiple transfers were created with the intention of getting a better rate but not fulfilling them all.
You can read more about it here: https://wise.com/help/articles/2448203/whats-a-guaranteed-rate


[fs-watch] function watch() callback interface WatchEvent Type mismatch.

The Problem:
The docs state that the watch() function of plugin-fs as follows:
function watch(
   paths,
   cb,
options?): Promise<UnwatchFn>

and the cb is a function defined as: (event: WatchEvent) => void
the interface WatchEvent is declared as follows:
interface WatchEvent {
  type: WatchEventKind
  paths: string[]
  attrs: unknown
}

And checking out interface WatchEventKind: https://github.com/tauri-apps/plugins-workspace/blob/da64d9b665694f541b1ee2d533535210e118969f/plugins/fs/guest-js/index.ts#L1177
However, upon implementing the watch() callback function, I found out that the actual data didn't contain type instead it had kind.
ie. the interface states that type : WatchEventKind, but the data was actually kind: WatchEventKind
Actual callback data sample:
{kind: {modify: {kind: "data", mode: "content"}}, paths: [".../some_path/..."], attrs: {}}

And upon checking out the watcher.rs native rust code, I can see that it's also declared as kind
Am I missing something?
How to fix?
As a workaround, I've declared a custom interface for this process in my own source code.
I think it'd be best if the type declaration was fixed on javascript.
Additional Info & Environment
my Cargo.toml:
[dependencies]
...
tauri-plugin-fs = { version = "2.0.0", features = ["watch"] }
...

Using verion 2.2.0 for tauri-plugin-fs didn't fix.
Operating system & App Platform : MacOS Silicon

Seems like notify changed the serialization in https://github.com/notify-rs/notify/pull/558 and we thought with serialization-compat-6 feature introduced in https://github.com/notify-rs/notify/pull/568, it would be the same as before but looks like there's a bug so... Will take a look and see if I could open a fix there

I just published notify-types-1.0.1, so a cargo update should fix the issue.
Thanks again for the PR @Legend-Master.

Awesome, thanks a lot ! 💪


graph,graphql,server,store: Subgraph Sql Service

Semiotic Labs is thrilled to present the Subgraph SQL Service in partnership with TheGuild and Edge & Node. This exposes a GraphQL type to any graph-node user, providing a secure SQL interface to directly query a subgraph's entities.
SQL Service
We introduce a new sql field on the "Query" type that exposes inputs so graph-node can receive raw SQL.
We also implemented a lot of safe sql rewrite to remove functions that we think may break the postgres instance along with some schema safety.
We also expose each of the tables via Common Table Expressions where we can have granular control over what is exposed or not and some workaround exposing only the latest block data.
What we cover on this PR

New sql query type
Defined API for inputs for backward compatibility with future work
Environment variable/Config to enable or disable the SQL service
Safety measures for SQL threats via complete AST SQL scan.
Latest block data
Single subgraph query
JSON and CSV union output

What we do not cover on this PR

Cross subgraph joins
Query on specific block/snapshot
Query optimizations
Query parameters binding
Query/Join between two different blocks/snapshots

Wow .. that's a really nice addition!
Before I start reviewing this in detail, I noticed a few things from a quick look at the PR:

there is no end-user documentation. Can you add something to docs/ that explains how to run queries? Obvious questions that should answer are: how do I send a query (example)? how do I use bind params? how does the GraphQL schema relate to the tables that this can query? What are the attributes/columns that can be queried? How much of SQL does this cover? I haven't looked but does this allow e.g., aggregations, window functions, CTEs etc.?
for operators: since SQL queries can be arbitrarily complex and take an arbitrary amount of time, how do they guard against long-running queries?
a minor nit is that commit messages should follow the guidelines here This won't cause us to not approve the PR, but it would be nice to keep with the current scheme.
this might be too much work, but I see that a sql crate appears and is then folded into the store - would it be possible to squash various commits so that there are fewer commits that fix up previous ones, not just for that crate but other fix commits, too? It'll make reviewing a lot easier

Wow .. that's a really nice addition!
Before I start reviewing this in detail, I noticed a few things from a quick look at the PR:

there is no end-user documentation. Can you add something to docs/ that explains how to run queries? Obvious questions that should answer are: how do I send a query (example)? how do I use bind params? how does the GraphQL schema relate to the tables that this can query? What are the attributes/columns that can be queried? How much of SQL does this cover? I haven't looked but does this allow e.g., aggregations, window functions, CTEs etc.?
for operators: since SQL queries can be arbitrarily complex and take an arbitrary amount of time, how do they guard against long-running queries?
a minor nit is that commit messages should follow the guidelines here This won't cause us to not approve the PR, but it would be nice to keep with the current scheme.
this might be too much work, but I see that a sql crate appears and is then folded into the store - would it be possible to squash various commits so that there are fewer commits that fix up previous ones, not just for that crate but other fix commits, too? It'll make reviewing a lot easier

Hey @lutter, thank you for the information. Here are some notes:

we added end-user documentation about the SQL-service to /docs as requests
graph-node has some build-in mechanisms to cancel long-running queries and we are relying on that
thanks for pointing out the guidelines, we rebased and reworded all the commits to make it easier to review
while rebasing, we removed how it was made and created commits of the "happy-path". We removed this appearance and fold of the SQL crate and fix up some commits.


Change date encoding from xs:datetime to allow more flexibility

including year only, and iso-8601 dates. Need to see what downstream impact is.

These regexes cover a broader range of ISO-8601 dates: https://stackoverflow.com/a/37563868 and https://www.myintervals.com/blog/2009/05/20/iso-8601-date-validation-that-doesnt-suck/
Used the fuller latter regex, with the lookahead expressions removed to abide by the constrains of XSD regexes.


'Alamofire/Alamofire.h' file not found

Xcode12.0.1  carthage.sh bootstrap --platform iOS --cache-builds
Alamofire.framework include Alamofire/Info.plist/Modules but not Headers

Alamofire's Obj-C module has been removed, so you'll need to update your version of Carthage.


[Query] Using ctx=gpu performance difference. Is this expected?

Hi. Thanks for the amazing repository.
I installed using -DUSE_CUDA option and then tried the example here (https://github.com/zhreshold/decord/blob/master/examples/video_loader.ipynb). I averaged over ten runs using %time Walltime output. The statement I timed was
vl = de.VideoLoader(videos, ctx=ctx, shape=shape, interval=interval, skip=skip, shuffle=0)

cpu
gpu

53
40

I also tried across various shuffle strategies, but nearly all of them were the same when the same device is used.
Wondering if this is what is expected.

GPU frames need to be copied to CPU before display so that can be an considerable overhead.
During training, if you are going to consume these frames directly in GPU, it saves twice the traffic:
t(CPU->GPU) - t(GPU->CPU)

Does it make sense?

I only used %time for the line vl = de.VideoLoader(videos, ctx=ctx, shape=shape, interval=interval, skip=skip, shuffle=0). If I understand correctly (let me know if I am incorrect), that shouldn't require transfer of frames from gpu to cpu.

Ok, the line you pointed actually does nothing but instantiate an instance of videoLoader, basically only some header and proprocessing is done. You need to measure the real time elapsed by reading frames.


[Darwin] MTRDevice should log better

Reproduction steps
For debugging, when MTRDevice filters incoming reports or read callbacks (because values did not change), a log should be generated about it.

Platform
darwin
Platform Version(s)
1.0
Type
Platform validated
(Optional) If manually tested please explain why this is only manually tested
No response
Anything else?
No response

Originally title was "MTRDevice should log when reports / read callbacks do not generate a report to delegate" but using this issue to track better logging all around for MTRDevice.


Interrupts don't work while using stream adapter

For context:
whisper_stt = openai.STT(detect_language=True)
vad=silero.VAD()
use_stt = StreamAdapter(vad=vad, stt=whisper_stt)
use_tts = elevenlabs.TTS(api_key=os.environ["ELEVEN_API_KEY"],model_id="eleven_multilingual_v2",voice=custom_11labs_voice)

When i run this setup with the voice assistant i've noticed a few things happen as listed below:

Message duplication -> it's likely because there are two events "FINAL_TRANSCIPT" and "END_OF_SPEECH" both the messages are pushed into context on the stream adapter end when using openAI STT.
Interrupts don't work, if i were to interrupt the agent with a new prompt, the agent continues talking finishing previous prompt and then moves on to the next message automatically (this is not an issue when i stream using deepgramSTT but there's no language detect option for this particular usecase and i NEED to use a stream adapter)
I realised that we're passing the vad param explicitly in the VoiceAssistant class inspite of declaring it again to build the streamAdpater.

assistant = VoiceAssistant(
        vad=silero.VAD(),
        stt=use_stt,
        llm=gpt,
        tts=use_tts,
        chat_ctx=initial_ctx,
        fnc_ctx=DrSmilez(),
        allow_interruptions=True,
    )

Above feels unnecessary and could potentially be causing the issue?

the same error...,how to fix it?

We have improvements to the voice assistant coming soon. You can try it with the following versions:
livekit-agents>=0.8.0.dev3
livekit-plugins-silero>=0.6.0.dev2
livekit-plugins-azure>=0.3.0.dev2
livekit-plugins-openai>=0.7.0.dev2
livekit-plugins-elevenlabs>=0.7.0.dev2

There are some slight breaking API changes for your agent entrypoint code. You can look here for reference: https://github.com/livekit/agents/blob/dev/examples/voice-assistant/minimal_assistant.py
Could you give that a try and see if you have the same issue?

@keepingitneil
not found
https://github.com/livekit/agents/blob/dev/examples/voice-assistant/minimal_assistant.py
the dev branch is not exits

Ahh this has been recently merged and the versions have been released. Here's the main branch link:https://github.com/livekit/agents/blob/main/examples/voice-assistant/minimal_assistant.pyAnd all of the above versions are the same but without the .devX suffix

{"message": "unhandled exception while running the job task\nTraceback (most recent call last):\n  File "E:\gitee\code\livekit-agents-0.8.0\examples\_deployed\kitt\kitt.py", line 88, in entrypoint\n    chat = rtc.ChatManager(ctx.room)\n           ^^^^^^^^^^^^^^^^^^^^^^^^^\n  File "C:\Python312\Lib\site-packages\livekit\rtc\chat.py", line 39, in init\n    self._lp = room.local_participant\n               ^^^^^^^^^^^^^^^^^^^^^^\nAttributeError: 'Room' object has no attribute 'local_participant'", "pid": 2768, "job_id": "AJ_ShiPzvtCuTsA", "timestamp": "2024-07-25T06:28:54.172341+00:00"}

livekit                        0.12.0.dev1
livekit-agents                 0.8.0
livekit-api                    0.6.0
livekit-plugins-azure          0.3.0
livekit-plugins-openai         0.6.0
livekit-plugins-silero         0.6.0
livekit-protocol               0.6.0

{"message": "Error in _synthesize_answer_task\nTraceback (most recent call last):\n  File "C:\Python312\Lib\site-packages\livekit\agents\utils\log.py", line 16, in async_fn_logs\n    return await fn(*args, **kwargs)\n           ^^^^^^^^^^^^^^^^^^^^^^^^^\n  File "C:\Python312\Lib\site-packages\livekit\agents\voice_assistant\voice_assistant.py", line 455, in _synthesize_answer_task\n    llm_stream = self._opts.will_synthesize_assistant_reply(self, copied_ctx)\n                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n  File "C:\Python312\Lib\site-packages\livekit\agents\voice_assistant\voice_assistant.py", line 79, in _default_will_synthesize_assistant_reply\n    return assistant.llm.chat(chat_ctx=chat_ctx, fnc_ctx=assistant.fnc_ctx)\n           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\nTypeError: LLM.chat() got an unexpected keyword argument 'chat_ctx'", "pid": 15548, "job_id": "AJ_9djEYFdBsPkC", "timestamp": "2024-07-25T06:52:59.548455+00:00"}

@keepingitneil
There are too many bugs, and the examples cannot run

Hey, it seems like the LLM plugins are not updated. Can you update livekit-plugins-openai to 0.7.0

I'm using the latest plugins and the error still persists, interrupts don't work properly when using a stream adapter.
i even turned off preemptive synthesis, that doesn't seem to do anything really.
i also still see duplicate transcripts whenever using streamAdapter.

Hey on v0.8.0. Interruption doesn't rely on the SpeechToText at all.
I'm unable to reproduce the issue, can you share more about it?

Using STT plugins that don't support streaming like openai-STT in conjunction with streamAdapter.
This is the particular scenario where interrupts fail.
Highlighted Issue
please refer the above code snippet.

Hey, the duplicated speeches should be fixed in livekit-agents v0.8.3.
I also tested using openai with the stream adapter and I was successfully able to interrupt the agent. Note that the interruption doesn't come from the STT but VAD.


zonal mean 3D variable trying to use a DASK array

ADF run type
Model vs. Model
What happened?
Generating zonal mean plots...
NOTE: Plot type is set to png
⌛ zonal mean plots for SWCF
⌛ zonal mean plots for LWCF
⌛ zonal mean plots for PSL
⌛ zonal mean plots for Q
Q has lev dimension.
...
Traceback (most recent call last):
File "/glade/u/apps/opt/conda/envs/npl/lib/python3.7/site-packages/xarray/core/ops.py", line 190, in _call_possibly_missing_method
method = getattr(arg, name)
AttributeError: 'Array' object has no attribute 'item'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./run_adf_diag", line 175, in
diag.create_plots()
File "/glade/u/home/bundy/cam/diag/ADF_top/ADF/lib/adf_diag.py", line 844, in create_plots
log_section = "create_plots")
File "/glade/u/home/bundy/cam/diag/ADF_top/ADF/lib/adf_diag.py", line 435, in __diag_scripts_caller
module_name=func_name)
File "/glade/u/home/bundy/cam/diag/ADF_top/ADF/lib/adf_diag.py", line 468, in __function_caller
return func(self)
File "/glade/u/home/bundy/cam/diag/ADF_top/ADF/lib/../scripts/plotting/zonal_mean.py", line 248, in zonal_mean
oseasons[s], ops_season, ohya, ohyb, **vres)
File "/glade/u/home/bundy/cam/diag/ADF_top/ADF/lib/plotting_functions.py", line 550, in plot_zonal_mean_and_save
diffnorm = normfunc(vmin=min(np.min(diff),-1*np.max(diff)), vcenter=0.0, vmax=np.max(diff))
File "/glade/u/apps/opt/conda/envs/npl/lib/python3.7/site-packages/matplotlib/colors.py", line 1324, in init
super().init(vmin=vmin, vmax=vmax)
File "/glade/u/apps/opt/conda/envs/npl/lib/python3.7/site-packages/matplotlib/colors.py", line 1135, in init
self._vmin = _sanitize_extrema(vmin)
File "/glade/u/apps/opt/conda/envs/npl/lib/python3.7/site-packages/matplotlib/colors.py", line 100, in _sanitize_extrema
ret = ex.item()
File "/glade/u/apps/opt/conda/envs/npl/lib/python3.7/site-packages/xarray/core/ops.py", line 202, in func
return _call_possibly_missing_method(self.data, name, args, kwargs)
File "/glade/u/apps/opt/conda/envs/npl/lib/python3.7/site-packages/xarray/core/ops.py", line 192, in _call_possibly_missing_method
duck_array_ops.fail_on_dask_array_input(arg, func_name=name)
File "/glade/u/apps/opt/conda/envs/npl/lib/python3.7/site-packages/xarray/core/duck_array_ops.py", line 65, in fail_on_dask_array_input
raise NotImplementedError(msg % func_name)
NotImplementedError: 'item' is not yet a valid method on dask arrays
114.032u 8.277s 2:50.97 71.5%	0+0k 8+0io 0pf+0w
ADF Hash you are using
187c929
What machine were you running the ADF on?
CISL machine
What python environment were you using?
NPL (CISL machines only)
Extra info
Brian told me this needs to change to a numpy array. Happy to do that if I can find an example.

Ah, this is not actually as much my fault as I thought! This error is happening when we try to set the color normalization. Inside matplotlib, it tries to "sanitize" the values that get used (https://github.com/matplotlib/matplotlib/blob/main/lib/matplotlib/colors.py). It looks like they assume a numpy array, so use item to get a scalar. In our case, for some reason a dask array is being used, so we need to call compute on it before using it in the color normalization function.


Task/ASB-747 Address line 3 becomes Town or county

Address Line 3 label becomes Town or county in the address entry.
This commit also fixes a large number of tests due to the click location problem for over 100 tests.

:tada: This PR is included in version 2.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Allows list type to be used with this gem

Cassandra list type does not currently work with this gem. This is due to get_column_type method not returning the correct column type (it does not parse the column_info.first["validator"] string properly) which this PR fixes. Please see my last comment in issue #59 for more details.

I'll merge it but can you add a test?

Thanks for the merge! I'll work on a test for this next.


pkoch's review

Created this just to have a place to accrete my thoughts.

I'm going to abstain from commenting on code style. I've found that evm/test/AccessGrants.js could be made a little easier to read. Let me know if you'd like to delve on that.

Stopped at insert_grant on rust

Done with near. I could maybe re-read the tests to see if they make sense, since I was a bit tired, but I feel confident enough.

@juliosantos I'm done with my first pass. :tennis:

Thank you — incorporated a bunch. Closing.


BlackduckAPI: remove test_product_connection

This fix should avoid error: 'BlackduckAPI' object has no attribute 'get_asset'
More details (and story behind): https://owasp.slack.com/archives/C2P5BA8MN/p1676985422740079?thread_ts=1675768685.949799&cid=C2P5BA8MN

Thanks for attaching the slack link. The extra context was helpful. I think commenting out that function and adding a #TODO comment would be better for the sake of this proposed solution sometime in the future:

It would be nice if somebody who actively use BlackDuck will be able to correctly implement functions test_connection and test_product_connection

Otherwise it will likely be forgotten about

I can test it on my side. We have a real instance of BlackDuck


[vm errors] Propagate status message to adapters

This makes the internal status message of VM errors available in VMStatus and accessible by adapters. The purpose is to allow adapters to show more detail of errors like they appear e.g. during bytecode verification. These errors happen more often in practice as anticipated, mainly because uses operate with different versions of networks and tools, e.g. deploying code to some chain where it is not deserializable, or using wrong dependencies on disk which do not match those on the network. Currently, the errors produced by the system are as unspecific as 'LINKER_ERROR'.

Related issues:
https://github.com/aptos-labs/aptos-core/issues/5864
https://github.com/aptos-labs/aptos-core/issues/6232
https://github.com/aptos-labs/aptos-core/issues/6041


Remove "target" folder from the files to push

Repairnator now checks if the target folder is ignored or not by Git, and checks if the .gitignore file is present or not.
In the first case, if the .gitignore file is present, but the target folder is not ignored, Repairnator adds these lines to the file:
# Added by Repairnator
target/

In the second case, if the .gitignore file is not present, Repairnator creates the file and writes the same content of the first case.
In this way, Repairnator doesn't push the target folder to GitHub, avoiding the publication of the GitHub token contained in some files of the folder target/surefire-reports.
Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>

please rebase :)

I did the rebase and I used the Logger method also in the catch of another exception. I also updated the documentation of the method that I implemented.

Everything is green https://travis-ci.org/github/eclipse/repairnator/builds/668104922, merging. Thanks a lot Davide!


Add .circleci/config.yml

Adding template circle ci to address https://github.com/opera-adt/PROTEUS/issues/5

@rtburns-jpl will open a new PR for the CI.


Fix footprint for AVHRR19_G-NAVO-L2P-v1.0 collection

Notes from Simon:
unable to generate the same footprint that is on prem using polar and polar sides strategy, even tried the l2ss-footprinter and seem to generate the same footprint as cloud one
unknown why this may be

Moving this to the new pyforge repo


Service Groups with different application names are grouped together

Describe the bug
When loading a new habitat service with event streaming enabled, the automate beta UI will group that service into any existing service group that matches the name, ignoring the ----event-stream-application setting.
To Reproduce
Steps to reproduce the behavior:

Start one supervisor with event streams enabled and --event-stream-application=app-1
Load up a redis server: hab svc load core/redis
Start another supervisor on a different VM with event streams enabled and --event-stream-application=app-2
Load up the same service as the first supervisor: hab svc load core/redis
The automate UI will show 2 instances of redis.default grouped under app-1

Expected behavior
I would expect there to be 2 groupings of redis.default in the UI. One showing app-1 as the App name and the other showing app-2.
Screenshots
TBD
Versions (please complete the following information):

OS: TBD
Supervisor version 0.83.0
Browser: firefox
Automate Build Number: TBD

Additional context
N/A

Working on this one, see the referenced PR for more

I didn't get the buildstamp of the first build with the patch applied, but the patch is present in the current dev build with buildstamp<PHONE_NUMBER>1254. Any version after this will contain the fix. If we are able to keep to our normal promotion schedule, then the fix should be released to the acceptance channel on August 5 or 6.

Thanks @danielsdeleo !


Redundancy between --fasta CLI argument and required fasta path in config file?

Is there a reason the FASTA path is required in the config file while it can be provided as a command line argument? I feel like it would make more sense - since it is a CLI argument - to let the user provide the path to the fasta with the CLI and/or the config file.  Happy to open a pull request if you agree.

The FASTA path is not actually required in the config file, this is a just a holdover/bug in the docs that was never updated when the CLI argument was added 😉 . If the user provides the path via CLI, then it overwrites anything in the config file.
If you want to submit a PR to fix, I will merge it. Otherwise, I can update the README.

I see. That's my bad - I forgot JSON files don't like trailing commas, which I had when I removed the FASTA path. On re-reading the README with this as the cause of the error in mind, the docs are actually clear and was just a syntax error on my part. Thanks!


Date values presented as timestamps

Thank you for creating this extension - this is very useful.
One oddity I discovered was that it presents date values as timestamps.

In the database (postgres) the column is a date type column so it is confusing that a time component is also being shown here.
Here is the same query result presented in another db interface (beekeeper)

There is also some timezone conversion happening due to which the date does not match (my server is in US where as I am running the notebook in India).

Thanks for this report. I suspect there is a way to discern timestamp vs. date in the types returned by each respected database driver but it may be tricky because JS only has one native Date type. Either way, we'll need to address this for each underlying driver implementation.
Will be a bit tedious but nothing difficult. Can likely be fixed by only editing https://github.com/cmoog/vscode-sql-notebook/blob/master/src/driver.ts. If someone wants to pick this up I'll make sure to review quickly and provide feedback / merge when ready.


Improved Decapodes integration: domains, meshes, initial conditions, plot variables

We can now do the Navier-Stokes vorticity equation in addition to the diffusion/heat equation. To accomplish this, we had to generalize the frontend support and Julia interop in several directions. A Decapodes simulation now analysis now requires that you specifiy:

the geometric domain: rectangle or sphere)
the mesh that discretizes the domain: several choices for both rectangle and sphere
initital/boundary conditions for specific variables: again, several fixes choices available
which variables to plot

The code is a quite raw in certain places and will need to be cleaned up later.

This latest push anticipates more integrations with AlgebraicJuliaService more and, concretely, generalizings some code from the Decapodes integration. AlgebraicJuliaService specifies integrations in an AlgebraicJuliaIntegration ADT and then has submodules through a basic yet vague interface specify how they will build theories/models/diagrams for CatColabsumption.
While I do not think this is entirely complete, I've

added a Geometry struct to contain the domain, mesh, and dualmesh.
used ThDecapode <: AlgebraicJuliaIntegration to tag generic-sounding structs like Theory, which is currently mapping names to TheoryElements, which may be Obs or Homs each responsible for storing data consumed from the incoming JSON. This interface is vague but, barring one failing test for unrelated reasons, does not currently break functionality.
threaded the system::PodeSystem variable further into functions, which allows us to carry more data further into functions, keeping the number of method arguments smaller
housekeeping such as reorganizing code into functions and relevant functionality into distinct files, added documentation, cleaned up tests

I'd like to generalize the methods in Theory so that further integration points would have an interface they integrate with, but I'm not sure if these packages would require different data structures (specifically, would the fields of Theory be different, or can we can away with type parameterizing the struct by T<:AlgebraicJuliaIntegration?)

Thanks @quffaro! I like this reorganization and refactor.


Change Repository name

Chang repository name to password_generator to when hosted in Heroku to your URL  to be https://password_generator.herokuapp.com rather than https://password-generato.herokuapp.com 😄

Renamed

You rename to password-generato instead of password_generator


Incorrect OpenSSL version detected in WSL 2 (Ubuntu)

Bug description
When I execute openssl version I get OpenSSL 3.0.9 30 May 2023 (Library: OpenSSL 3.0.9 30 May 2023).
However when I execute npx prisma --version I get:
Error: Unable to require(`/home/jeipiou/code/qbic/pulpos/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node`).
Prisma cannot find the required `libssl` system library in your system. Please install openssl-1.1.x and try again.

Details: libssl.so.1.1: cannot open shared object file: No such file or directory
    at loadLibrary (/home/jeipiou/code/qbic/pulpos/node_modules/prisma/build/index.js:85527:11)
    at getEngineVersion (/home/jeipiou/code/qbic/pulpos/node_modules/prisma/build/index.js:85540:16)
  prisma:getConfig  Using getConfig Wasm +0ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +8ms
prisma                  : 5.1.1
@prisma/client          : 5.1.1
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : E_CANNOT_RESOLVE_VERSION (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 6a3747c37ff169c90047725a05a6ef02e32ac97e (at<EMAIL_ADDRESS>Schema Wasm             : @prisma/prisma-schema-wasm 5.1.1-1.6a3747c37ff169c90047725a05a6ef02e32ac97e
Default Engines Hash    : 6a3747c37ff169c90047725a05a6ef02e32ac97e
Studio                  : 0.492.0
Preview Features        : fullTextSearch, jsonProtocol, orderByNulls
  prisma:getConfig  Using getConfig Wasm +3ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +5ms

Which ends up generating problems when executing the application since Prisma cannot find the .so for OpenSSL 1.1.
How to reproduce

Create a wsl instance of Ubuntu
Create a project that uses the latest Prisma version
Confirm that the reported OpenSSL version is the one expected (3).
Execute npx prisma --version

Expected behavior
OpenSSL 3 engine is being used since it is the one available.
Prisma information
N/A since this isn't a problem with queries or the schema.
Environment & setup

OS: Windows (WSL 2, Ubuntu)
Database: PostgreSQL
Node.js version: v18.16.1

Prisma Version
Error: Unable to require(`/home/jeipiou/code/qbic/pulpos/node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node`).
Prisma cannot find the required `libssl` system library in your system. Please install openssl-1.1.x and try again.

Details: libssl.so.1.1: cannot open shared object file: No such file or directory
    at loadLibrary (/home/jeipiou/code/qbic/pulpos/node_modules/prisma/build/index.js:85527:11)
    at getEngineVersion (/home/jeipiou/code/qbic/pulpos/node_modules/prisma/build/index.js:85540:16)
  prisma:getConfig  Using getConfig Wasm +0ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +8ms
prisma                  : 5.1.1
@prisma/client          : 5.1.1
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : E_CANNOT_RESOLVE_VERSION (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 6a3747c37ff169c90047725a05a6ef02e32ac97e (at<EMAIL_ADDRESS>Schema Wasm             : @prisma/prisma-schema-wasm 5.1.1-1.6a3747c37ff169c90047725a05a6ef02e32ac97e
Default Engines Hash    : 6a3747c37ff169c90047725a05a6ef02e32ac97e
Studio                  : 0.492.0
Preview Features        : fullTextSearch, jsonProtocol, orderByNulls
  prisma:getConfig  Using getConfig Wasm +3ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +5ms

I have not set anything neither in the Prisma schema nor in any environment variable

Hey @jporsay, could you please run DEBUG="prisma:get-platform" npx prisma version, and paste the output in here? Thanks.

Sure! Here you go:
$ export DEBUG="prisma*"
$ npx prisma --version
  prisma:engines  binaries to download libquery-engine, migration-engine +0ms
  prisma:get-platform  Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
} +0ms
  prisma:get-platform  Trying platform-specific paths for "debian" (and "ubuntu") +0ms
  prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.1.1 +1ms
  prisma:get-platform  The parsed libssl version is: 1.1.x +0ms
  prisma:get-platform  Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
} +1ms
  prisma:get-platform  Trying platform-specific paths for "debian" (and "ubuntu") +0ms
  prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.1.1 +0ms
  prisma:get-platform  The parsed libssl version is: 1.1.x +0ms
Environment variables loaded from .env
  prisma:get-platform  Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "ubuntu"
} +0ms
  prisma:get-platform  Trying platform-specific paths for "debian" (and "ubuntu") +0ms
  prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.1.1 +1ms
  prisma:get-platform  The parsed libssl version is: 1.1.x +0ms
Error: Unable to require(`/home/[...]/node_modules/prisma/libquery_engine-debian-openssl-1.1.x.so.node`).
Prisma cannot find the required `libssl` system library in your system. Please install openssl-1.1.x and try again.

Details: libssl.so.1.1: cannot open shared object file: No such file or directory
    at loadLibrary (/home/[...]/node_modules/prisma/build/index.js:97408:11)
    at getEngineVersion (/home/[...]/node_modules/prisma/build/index.js:97422:16)
Error: Could not find migration-engine binary. Searched in:
-<EMAIL_ADDRESS>- /home/[...]/node_modules/prisma/migration-engine-debian-openssl-1.1.x
- /home/[...]/node_modules/migration-engine-debian-openssl-1.1.x
- /home/[...]/node_modules/prisma/runtime/migration-engine-debian-openssl-1.1.x
    at resolveBinary (/home/[...]/node_modules/prisma/build/index.js:97363:9)
Error: Could not find migration-engine binary. Searched in:
-<EMAIL_ADDRESS>- /home/[...]/node_modules/prisma/migration-engine-debian-openssl-1.1.x
- /home/[...]/node_modules/migration-engine-debian-openssl-1.1.x
- /home/[...]/node_modules/prisma/runtime/migration-engine-debian-openssl-1.1.x
    at resolveBinary (/home/[...]/node_modules/prisma/build/index.js:97363:9)
  prisma:getConfig  Using getConfig Wasm +0ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +7ms
prisma                  : 4.13.0
@prisma/client          : 4.13.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : E_CANNOT_RESOLVE_VERSION (at node_modules/prisma/libquery_engine-debian-openssl-1.1.x.so.node)
Migration Engine        : E_CANNOT_RESOLVE_VERSION (at E_CANNOT_RESOLVE_PATH)
Format Wasm             : @prisma/prisma-fmt-wasm 4.13.0-50.1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a
Default Engines Hash    : 1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a
Studio                  : 0.484.0
Preview Features        : fullTextSearch, orderByNulls, jsonProtocol
  prisma:getConfig  Using getConfig Wasm +2ms
  prisma:getConfig  config data retrieved without errors in getConfig Wasm +5ms

I'm a bit confused how this shows the Prisma version as4.13.0 but in the issue description it was 5.1.1 🤔
Can you try the same command with 5.1.1?

My bad, I had tried to upgrade Prisma's version and reverted that change after I saw that it wasn't fixed, reason for why the log is displaying that version. However I did a clean installation of my development box (WSL: Ubuntu) and the problem does not seem to happen anymore. Closing this ticket since the version is correctly detected now:
$ npx prisma --version
prisma                  : 5.1.1
@prisma/client          : 5.1.1
Current platform        : debian-openssl-3.0.x
Query Engine (Node-API) : libquery-engine 6a3747c37ff169c90047725a05a6ef02e32ac97e (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 6a3747c37ff169c90047725a05a6ef02e32ac97e (at<EMAIL_ADDRESS>Schema Wasm             : @prisma/prisma-schema-wasm 5.1.1-1.6a3747c37ff169c90047725a05a6ef02e32ac97e
Default Engines Hash    : 6a3747c37ff169c90047725a05a6ef02e32ac97e
Studio                  : 0.492.0
Preview Features        : fullTextSearch, jsonProtocol, orderByNulls

Seems I might have had some leftover libssl version somewhere.
Thanks for the help!

Glad that this was so quickly solved! Have a nice day, @jporsay 😄

That is correct! I didn't have much to loose so that's what I did and it
fixed it.
On Tue, 12 Dec 2023, 03:14 Nutt Chokwittaya, @.***>
wrote:

@jporsay https://github.com/jporsay I have a same problem, so you
remove WSL2 ubuntu and reinstall it?
—
Reply to this email directly, view it on GitHub
https://github.com/prisma/prisma/issues/20682#issuecomment-1851193694,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAESXSQYIGE5YIJJLPP66NTYI64XLAVCNFSM6AAAAAA3PVS54WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJRGE4TGNRZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>