e2e testing documentation update with docker hermes build

Closes: #965
Description

The PR fixes the relayer.Dockerfile to build hermes in docker. The documentation was slightly updated too.
Rendered readme here.

For contributor use:

[X] Updated the Unreleased section of CHANGELOG.md with the issue.
[X] If applicable: Unit tests written, added test to CI. (locally tested)
[X] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[X] Updated relevant documentation (docs/) and code comments. (ci/README.md)
[X] Re-reviewed Files changed in the Github PR explorer.

Just a note that the instructions fail for me here:
docker exec relayer /bin/sh -c /relayer/e2e.sh
The keys seem to be added with success:
Success: Added key 'testkey' (cosmos1fg67nue7pv9cl7m6enzr2g2y80hp62hye28kvd) on chain ibc-0
But in create client later:
    raise ExpectedSuccess(self.cmd, status, result)
e2e.cmd.ExpectedSuccess: Command 'TxCreateClient(dst_chain_id='ibc-0', src_chain_id='ibc-1')' failed. Expected 'success', got 'error'. Message: tx error: error raised while creating client: failed sending message to dst chain (ibc-0) with err: GRPC error: GRPC error: status: Unknown, message: "rpc error: code = NotFound desc = account cosmos1fg67nue7pv9cl7m6enzr2g2y80hp62hye28kvd not found: key not found", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }

Oh, right, I should have closed this PR long ago without merging it.
This solution might be ok for one-off testing specific branches but for the kind of developer testing we're looking for (hey I just have this new code, let's run it in e2e), this won't work well.

I'll come back to #965 a bit later and work it out.


Fix nightly clippy

also add's lower bound check for Thread prio input #234

Cherry-picked with
https://github.com/esp-rs/esp-idf-hal/commit/d228f185137de331446c9d5f9fb2284333a08507
and
https://github.com/esp-rs/esp-idf-hal/commit/e6cf130666dca8f8eeb1d4f66e73794a09784056


Laravel 10.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 9.x.
Before merging, you need to:

Checkout the l10-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/l5-very-basic-auth.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "olssonm/l5-very-basic-auth": "dev-l10-compatibility",
    }
}

Finally, run: composer update


Copy object multipart

Transparently do multipart copy.
One note: The current default MULTI_PART_SIZE (as also used by upload) restricts file to be a maximum of 78GB as you can only do 10.000 parts, while S3 supports 5TB, it might be a good idea to change that.

thanks, I'll extend the bucket name via a pulsar settings


AKS - Error while updating taint on the cluster

Hello guys I'm trying to install Sysbox in my AKS cluster and I got this error:
Error from server: admission webhook "aks-node-validating-webhook.azmk8s.io" denied the request: (UID: 9a9f6a3d-c7c3-4dcc-b73b-a22885904ebe) Label update/add request "sysbox-runtime:installing" refused. User is attempting to update/add a label configured on node pool. Please change node pool label configuration through Azure..
I saw different issues that mention that AKS modified their workaround, and it is no longer feasible to update the taints.
I would like to know if you are aware of this or if it's a different workaround to manage Sysbox in AKS
cc: @ctalledo
Thanks.

Thanks @andresvasile.

I would like to know if you are aware of this or if it's a different workaround to manage Sysbox in AKS

Not aware of it, thanks for lettings us know.

I saw different https://github.com/Azure/AKS/issues/2934 that mention that AKS modified their workaround, and it is no longer feasible to update the taints.

Strange that they wouldn't allow a daemonset to set the labels though, I believe it's a fairly common practice.
When running the sysbox-deploy-k8s daemonset, what do the logs for the daemonset show? Maybe there's a further clue in there.
FYI, the sysbox-deploy-k8s daemonset runs a bash script that "drops" Sysbox onto the K8s node(s) and then reconfigures K8s to become aware of the new runtime.  That script sets the labels using a function called add_label_to_nodes (see here for example).

Sure, here is the full log:
Detected Kubernetes version v1.29
Adding K8s taint "sysbox-runtime=not-running:NoSchedule" to node ...
node/aks-isolated-26818767-vmss000000 modified
Adding K8s label "crio-runtime=installing" to node ...
node/aks-isolated-26818767-vmss000000 not labeled
Deploying CRI-O installer agent on the host (v1.29) ...
Running CRI-O installer agent on the host (may take several seconds) ...
Removing CRI-O installer agent from the host ...
Configuring CRI-O ...
Configuring CRI-O for GKE
Adding K8s label "sysbox-runtime=installing" to node ...
Error from server: admission webhook "aks-node-validating-webhook.azmk8s.io" denied the request: (UID: c80b6ee7-8444-4752-b5f3-963a6db70b09) Label update/add request "sysbox-runtime:installing" refused. User is attempting to update/add a label configured on node pool. Please change node pool label configuration through Azure..

@ctalledo for now I'm using this particular command to bypass the validation:
kubectl delete ValidatingWebhookConfiguration aks-node-validating-webhook
but I'm not really sure what concerns or implications could bring it..

Thanks @andresvasile for the work-around above to install Sysbox on AKS.
I guess we could improve the sysbox-deploy-k8s daemonset to detect it's installing on AKS and try to label the node, but if it's unsuccessful (e.g., because AKS restricts this), then just move on instead of failing.
IIRC, sysbox-deploy-k8s uses those labels to keep track of it's progress and it installs Sysbox on the K8s cluster, as well as to prevent sysbox containers from getting deployed on a node until Sysbox is actually installed and running on it.


Bug in C# 8.0 compiler or .NET Core 3 run-time

I've bumped into a strange issue that when I..

Implement a generic interface with at least one generic type parameter, and...
Add two generic overloads to that interface, where the type parameter constraint on the method's generic type parameter references the parent interface's generic type parameter, and...
One of the overloads provides a default implementation...

...then when I try to call the interface's overload that provides the default implementation with a type parameter that satisfies all constraint, the compiler thinks it's fine, but the run-time throws a System.Security.VerificationException at the point of invoking the interface method.
For more explanation and a way to reproduce this error, see my question on StackOverflow.

It looks like Jon Skeet answered this question on StackOverflow, so I'm going to close this here. If you'd still like feedback or believe he was incorrect, please file an issue on the dotnet/roslyn or dotnet/runtime repos.


Can we change the package source?

I can never install the package postgres-9.4.6 for the network issue,and I try to use VPN to improve but help little.
So I wonder if there is a way to change the package source,because of the HORRIBLE network in China.
Any help will be appreciated!

I tried at least 10 times ,and finally passed......

使用迅雷下载s3资源到本地，然后修改源码从本机加载


Add some links to decodes doc

No idea why the test docs build didn't run this time? Would like to see those links working before merge.


merge from arlac77/template-github-action,arlac77/template-kronos-component

.github/workflows/auto_approve.yml

chore(actions): merge from template .github/workflows/auto_approve.yml

Codecov Report

Merging #828 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #828   +/-   ##
=======================================
  Coverage   28.94%   28.94%
=======================================
  Files           1        1
  Lines          76       76
  Branches        1        1
=======================================
  Hits           22       22
  Misses         54       54

Continue to review full report at Codecov.

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


The requested package endroid/qrcode could not be found in any version

composer install:
try:
composer require "endroid/qrcode"
composer require endroid/qrcode:1.6.2
composer require "endroid/qrcode:dev-master" --prefer-dist
composer require "endroid/qrcode:dev-master" --prefer-source

Problem 1
- The requested package endroid/qrcode could not be found in any version, there may be a typo in the package name.
Potential causes:

A typo in the package name
The package is not available in a stable-enough version according to your minimum-stability setting
see https://getcomposer.org/doc/04-schema.md#minimum-stability for more details.

Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

Hi @wkii when I create a clean composer file (via "composer init") and then require the library it is installed without any issues so nothing seems wrong with the library itself. I assume this is caused by a conflicting dependency or something else in your environment.


Password substring stronger than password

From a user interface perspective while typing in a password, I would expect the score to be non-decreasing... ie, the password meter never goes down as I type new characters. Technically as well, a substring should never have more entropy than the string.
While testing "correcthorsebatterystaple" (via meter on https://www.dropbox.com/register), the password jumped from Good to So-so between "correcthorsebatte" and "correcthorsebatter". I understand the technical reasons why the entropy goes lower as it hits a known word given the current algorithm. I think there is some potential room for improvement in this regard.

Hey @devinrsmith, while different from other ranking algorithms and potentially confusing to users (hence zxcvbn's verbal feedback which can help), I disagree that substrings should necessarily have less entropy than strings.
For example, consider elephant, which zxcvbn ranks as the 275th most common password in the Xato 10M password corpus. Crackers generally iterate through common passwords first (say up to a dictionary size of 10k, 100k, 1M) before applying mangling rules such as trying substrings -- otherwise they'd need to make many more guesses before getting to the most likely passwords. Operating under that threat model:
elephan and elepha should both be stronger than  elephant.
A weakness of zxcvbn is it doesn't recognize edit distance from dictionary words -- it analyzes elepha as a bruteforce match, for example, vs a mangling of elephant. Even if it had that capability I would still give higher weight to elepha (add guesses for mangling).
(Other small note is that zxcvbn ranks elephan as a common password with rank 12828 vs 275, because it too is a common password, but less common than elephant.)
I'd still be interested to hear ideas if you have them on how to make this better, or user interface-level ideas that make it less confusing to people.

Yeah, the key thing here is we are assuming a threat model to assign entropy (ie: given a password cracking algorithm, how long until we generate the given password). The problem is that the current state of the "threat model" changes over time as users' password preferences change and password crackers update algorithms. Of course, we have to make assumptions somewhere...
Anyways, I think it's still a valid concern from a UI point of view. I don't have any solutions to offer though!


Release 0.10.0

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

@gq1 @muffato The github CI checks are fine, I'm happy to merge as long as get an approval. Thanks :)

The CI job only submit the job on farm, not sure why pending so long. This is the first time you run all the code together on dev, better to wait.


Adding model name resolver and user_foreign_key option

Adds model name resolver to migration generator.
Adds user_foreign_key option from config to migration generator.

@ahmetkapikiran Sorry, can you please elaborate on this?


how to cancel the  lazy loading function

Hello, my received video delay is very high, how can I cancel the delay loading function, or how to make the player's buffer smaller?

to cancel the lazy loading,you should modify the GPlayer/android/build.gradle and uncomment the line 38 compile 'com.github.tcking:ijkplayer-armv7a:0.8.8',then rebuild the project, aflter that the so files will build in the apk


credhub set -t value defaults to string

What version of the credhub server you are using?
λ credhub --version
CLI Version: 2.0.0
Server Version: 2.0.2

If you were attempting to accomplish a task, what was it you were attempting to do?
I was attempting to store a variable which determines how many instances of a BOSH deployment to deploy. With this credential storage:
λ credhub set -t value -n /bosh/rabbitmq/haproxy-instances -v 2

It should be storable as an int. When I deployed the BOSH release with ((haproxy-instances)) as the /instance_groups/name=haproxy/instances value, it failed because it's a string and not an integer.
What did you expect to happen?
The BOSH deployment to succeed because I passed a raw integer when creating the variable in credhub.
What was the actual behavior?
Task 28112

Task 28112 | 23:41:14 | Preparing deployment: Preparing deployment (00:00:01)
                     L Error: Property 'instances' value ("2") did not match the required type 'Integer'
Task 28112 | 23:41:15 | Error: Property 'instances' value ("2") did not match the required type 'Integer'

Task 28112 Started  Sun Nov 11 23:41:14 UTC 2018
Task 28112 Finished Sun Nov 11 23:41:15 UTC 2018
Task 28112 Duration 00:00:01
Task 28112 error

Updating deployment:
  Expected task '28112' to succeed but state is 'error'

Exit code 1

Please confirm where necessary:

[ ] I have included a log output
[x] My log includes an error message
[ ] I have included steps for reproduction

Hey @mxplusb - we have reproduced this issue locally. This is in line with the expected behavior per the API docs as the value credential type only accepts strings.
We found, however, that if the credential type that you are interpolating into your BOSH manifest is JSON, then you can get an integer type to be substituted. For example, if you say credhub set -t json -n /bosh/rabbitmq/haproxy-instances -v 2, then that variable will be interpolated as an integer in the BOSH manifest. Would this be a valid workaround for your use case?

@crawsible @jparnala have y'all seen this type of request before where we are wanting to explicitly set values as integers in Credhub? Is this something that we have talked about supporting before?

This is in line with the expected behavior per the API docs as the value credential type only accepts strings.

That's good to know. I think the CLI could use a significant overhaul on the documentation regarding set. The API docs are helpful if I was developing an API client, but I'm using the CLI and the docs don't cover use cases like this. The rest of the CF CLIs are very verbose in their help messages and don't point to external docs. I think that's definitely an area of improvement - the fact I had to file this issue to figure out how to store a different data type speaks to that.

Would this be a valid workaround for your use case?

Yes, it should work just fine. Thanks! 👍

@mxplusb - thanks very much for your feedback, this is valuable for us to hear. Just to make sure we understand properly, is this docs shortcoming specifically in reference to the set CLI command, or is it an issue with all CLI commands?
Also, we could benefit from concrete examples of how the CLI could be improved - do you have any ideas off the top of your head? E.g., is it the fact that we are missing that value/password/json types are supposed to be strings?

Excellent question. I think the --type flag is useful, and I'd be interested in seeing it be extended/reassociated to support other types for static types that aren't part of a greater JSON structure. In my mind I could see something like this:
credhub set --type int -n /int_var -v 2
credhub set --type string-array -n /string_array_var -v '["a","b"]'
credhub set --type int-array -n /int_array_var -v '[1,2,3]'
credhub set --type bool-array -n /bool_array_var -v '[true,false]'
credhub set --type bool -n /bool_var -v 'true'

For the default --type value, it would be good to specify in the docs that --type value defaults to a string type so it's more clear.
How the Credhub API handles those specific flags internally I don't think matters to the end user so much, so you could really just have those be wrappers around the existing JSON implementation. That way you don't have a large logical overhead, but an operator then feels like they are storing the proper data type needed for a given consumer.
Thoughts?

@mxplusb  Thanks for your suggestions and feedback!
@jparnala Let's talk about this in our next sync up.

We're taking your documentation feedback in mind for improvements. Closing this issue, thank you!


Revert "Merge pull request #10880 from Bo98/cli-stronger-types"

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Just in case we need it.
Fixes #10906.
This reverts commit 25373a18cc6c529243558be6f67401f1e4100a30, reversing
changes made to a045cd7a614246a2debc537e9cd406ab55316743.

Review period skipped due to critical label.

Not sure why git thought I was reverting a045cd7a614246a2debc537e9cd406ab55316743. I'm pretty sure I'm reverting the other parent, 8e98ce69f39cf014f63195ed880d3f445c905757.

It was somewhat expected there would be breakages. It's why I wanted to wait for a new tag first.
#10908 will fix the error reported in #10906.

Nice. I'll just leave this here just in case, but I don't expect that it'll need to be merged.

Don't think this will be needed anymore.


Fix log at ^0.4.16 to make tests compile

Before this the tests were failing with the error detailed in this issue https://github.com/rust-lang/log/issues/500


Metrics webapp

Project requirements

You will select an API that provides numeric data about a topic that you like and then build the webapp around it. The webapp will have several pages:

one page with a list of items that could be filtered by some parameters; in the example below, it's a list of metrics that can be filtered by the country (imagine a search field to introduce the country name like Italy, Croatia, etc.). This page should be your homepage.
one page for the item details; in the example, the detail page for Czech Republic cities with number of views.

@DianaBeki - Please implement all the request changes that were asked for in the first PR you submitted.
Your test still not passing, perhaps you can show us in the video where the test passed from your end.
Try to checklist the following;

[ ] Deploy your website and put the link in the readme.
[ ] Create a presentation video. Requirement
[ ] Make your test pass.

Hi @DianaBeki,
This is a manual review
Approved 👍
Cheers and Happy coding!:clap::clap::clap:

@DianaBeki - kindly go ahead and merge.


Bump flake8 and demisto-sdk

Status
Ready
Related PRs

branch
PR

demisto-sdk PR
https://github.com/demisto/demisto-sdk/pull/1170

content PR
https://github.com/demisto/content/pull/11826

client PR
https://github.com/demisto/web-client/pull/7654

Description
The updates to the ValidateContent script and the client depend on the new output format of the latest release of the demisto-sdk. Note that the flake8 dependency was bumped as well because there is a dependency conflict with flake8 == 3.8.3 and demisto-sdk == 1.3.2 as can be seen in the copied logs from the installation failure below -
There are incompatible versions in the resolved dependencies:
  pycodestyle<2.7.0,>=2.6.0a1 (from flake8==3.8.3->-r /var/folders/ds/lf7sb1x93dnc62q3jpk_c9mxq6drz5/T/pipenvsvpe93zarequirements/pipenv-w5uyzpw5-constraints.txt (line 2))
  pycodestyle>=2.7.0 (from autopep8==1.5.6->demisto-sdk==1.3.2->-r /var/folders/ds/lf7sb1x93dnc62q3jpk_c9mxq6drz5/T/pipenvsvpe93zarequirements/pipenv-w5uyzpw5-constraints.txt (line 6))

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/xsoar-tools:<IP_ADDRESS>87
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/xsoar-tools/tags
Get started by pulling the image:
docker pull devdemisto/xsoar-tools:<IP_ADDRESS>87

Docker Metadata

Image Size: 108.12 MB

Image ID: sha256:154df5c12acb2147fd94faf469a9cb0f8138e15678f8d7ce2c67c3ab50458dc1

Created: 2021-03-18T14:39:26.245750881Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
GPG_KEY=E3FF2839C048B25C084DEBE9B26995E310250568
PYTHON_VERSION=3.9.1
PYTHON_PIP_VERSION=20.3.3
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/5f38681f7f5872e4032860b54e9cc11cf0374932/get-pip.py
PYTHON_GET_PIP_SHA256=6a0b13826862f33c13b614a921d36253bfa1ae779c5fbf569876f3585057e9d2
DOCKER_IMAGE=devdemisto/xsoar-tools:<IP_ADDRESS>87

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:5a316559768513eacffff6e83b80677aa2b299df
org.opencontainers.image.version:<IP_ADDRESS>87

Docker Image Ready - Production
Docker automatic build at CircleCI has deployed your docker image: demisto/xsoar-tools:<IP_ADDRESS>88
It is available now on docker hub at: https://hub.docker.com/r/demisto/xsoar-tools/tags
Get started by pulling the image:
docker pull demisto/xsoar-tools:<IP_ADDRESS>88

Docker Metadata

Image Size: 108.12 MB

Image ID: sha256:a1551a4355de615ff676a111cffa844efd1b174098364587ec13c4ea3b2c20e2

Created: 2021-03-18T15:42:45.585224698Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
GPG_KEY=E3FF2839C048B25C084DEBE9B26995E310250568
PYTHON_VERSION=3.9.1
PYTHON_PIP_VERSION=20.3.3
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/5f38681f7f5872e4032860b54e9cc11cf0374932/get-pip.py
PYTHON_GET_PIP_SHA256=6a0b13826862f33c13b614a921d36253bfa1ae779c5fbf569876f3585057e9d2
DOCKER_IMAGE=demisto/xsoar-tools:<IP_ADDRESS>88

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:48690c28333141cc825e29780b60f752eec19cb4
org.opencontainers.image.version:<IP_ADDRESS>88


doc(gi): swapped package source and doc links in README.md

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (09e5ad8) to head (4e2998d).

Additional details and impacted files
@@            Coverage Diff             @@
##              main       #53    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           76         5    -71
  Lines         1328       415   -913
==========================================
- Hits          1328       415   -913

Flag
Coverage Δ

gi
?

optional
100.00% <ø> (ø)

result
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

coverage: 100.0%. remained the same
when pulling 4e2998d59513b3b224c6b6a6254b4477a1116cdd on feature/gi
into 09e5ad8593990ae92bb1e84b77e0aa671723ab1a on main.


apply_gradients.run seems to leak memory

I'm running a large scale network with tensorflow and I keep getting memory errors, so I pull out memory_profiler and found this
Filename: parameterservermodel.py
Line    Memtotal    Increment   Line Contents
110   2121.9 MiB     39.2 MiB            self.apply_gradients.run(session=self.session, feed_dict=feed_dict)
If I'm not mistaken, it looks like like apply_gradients.run allocates almost 40MB and doesn't return anything for me to free. I might be missing something here.

Looks like the memory_profiler has a lag, it was a previous line in the code that was causing it.


Cpf 3645/resend email is not work after sigin up

address: https://nanopay.atlassian.net/browse/CPF-3645
note:
signUp after use sigin up they will log out and stoping them resend verification email.
signIn if unverified user try to login they will login both verifyEmail screen and dashboard screen. (
(
the way to recreate:
0.must be unverified use
1.login
2.go back to ablii
3.login again
)
^

I don't think the image shown has anything to do with signin-ing in, or being logged in.
While using connect, the side navigation occasionally renders, unexpectedly.
@yij793 did you test the context at the point where you think you are logged in to see if the user is indeed logged in? Believe the SideNav - menu is toggled with loginSuccess, so it's possible this is not getting set correctly, considering you moved this, isn't that the problem??
and further, the change  you made by deleting the logout, you are virtually keeping the user logged in - in the context even though you are just redirecting the user to another view.
This is a potential security risk.
@TW80000 can you give your opinion


v0.15 allows to install libv8 v6.7 which breaks the compilation

✅ I solved by adding a requirement for an older libv8
gem 'libv8', '~> 6.3.0'

See it in action: https://travis-ci.org/opal/opal/jobs/407141833
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
current directory:
/home/travis/build/opal/opal/vendor/bundle/ruby/2.2.0/gems/mini_racer-0.1.15/ext/mini_racer_extension
/home/travis/.rvm/rubies/ruby-2.2.10/bin/ruby -r
./siteconf20180723-7687-np79m9.rb extconf.rb
checking for main() in -lpthread... yes
creating Makefile
current directory:
/home/travis/build/opal/opal/vendor/bundle/ruby/2.2.0/gems/mini_racer-0.1.15/ext/mini_racer_extension
make "DESTDIR=" clean
current directory:
/home/travis/build/opal/opal/vendor/bundle/ruby/2.2.0/gems/mini_racer-0.1.15/ext/mini_racer_extension
make "DESTDIR="
compiling mini_racer_extension.cc
mini_racer_extension.cc: In function ‘void gc_callback(v8::Isolate*, v8::GCType,
v8::GCCallbackFlags)’:
mini_racer_extension.cc:129:9: error: ‘TerminateExecution’ is not a member of
‘v8::V8’
         V8::TerminateExecution(isolate);
         ^
mini_racer_extension.cc: In function ‘VALUE rb_isolate_idle_notification(VALUE,
VALUE)’:
mini_racer_extension.cc:508:35: error: ‘class v8::Isolate’ has no member named
‘IdleNotification’
return isolate_info->isolate->IdleNotification(NUM2INT(idle_time_in_ms)) ?
Qtrue : Qfalse;
                                   ^
mini_racer_extension.cc: In function ‘void* gvl_ruby_callback(void*)’:
mini_racer_extension.cc:737:2: error: ‘TerminateExecution’ is not a member of
‘v8::V8’
  V8::TerminateExecution(args->GetIsolate());
  ^
mini_racer_extension.cc:761:7: error: ‘TerminateExecution’ is not a member of
‘v8::V8’
       V8::TerminateExecution(isolate);
       ^
mini_racer_extension.cc: In function ‘VALUE rb_context_stop(VALUE)’:
mini_racer_extension.cc:1036:5: error: ‘TerminateExecution’ is not a member of
‘v8::V8’
     V8::TerminateExecution(isolate);
     ^
mini_racer_extension.cc: In function ‘VALUE rb_isolate_idle_notification(VALUE,
VALUE)’:
mini_racer_extension.cc:509:1: warning: control reaches end of non-void function
[-Wreturn-type]
 }
 ^
make: *** [mini_racer_extension.o] Error 1
make failed, exit code 2
Gem files will remain installed in
/home/travis/build/opal/opal/vendor/bundle/ruby/2.2.0/gems/mini_racer-0.1.15 for
inspection.
Results logged to
/home/travis/build/opal/opal/vendor/bundle/ruby/2.2.0/extensions/x86_64-linux/2.2.0/mini_racer-0.1.15/gem_make.out
An error occurred while installing mini_racer (0.1.15), and Bundler
cannot continue.
Make sure that `gem install mini_racer -v '0.1.15' --source
'https://rubygems.org/'` succeeds before bundling.
In Gemfile:
  mini_racer

I'm seeing the same problem

latest mini_racer is 0.2.0, it resolves this issue and adds support for libv8  6.7
no way we can fix this short of yanking the old gem which would be over drastic. also no plans to release a 0.16 with old bugs ....

👍🏼 makes sense
I added the stack-trace to the issue description so it can help others facing the same problem

One super odd thing I noticed is that somehow bundler version of libv8 is not making any diff, if the libv8 latest is installed on the box you are hosed until you remove the gem from the system.

Not an expert, but maybe earlier versions look for v8 dynamically and found the latest version, maybe this is related: https://github.com/cowboyd/libv8/commit/0f4419ed82ab1bfd23b86f5b60490066f4596a5d#diff-8a86c291c14db6920c162c9888b9977d

Nope.... tried suggestion above (mklink)
$ gem uninstall -a libv8 mini_racer
Successfully uninstalled libv8-6.3.292.48.1-x86_64-darwin-16
Successfully uninstalled libv8-6.7.288.46.1-universal-darwin-16
$ bundle
Fetching mini_racer 0.1.15
Installing mini_racer 0.1.15 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
Platform is Mohave, rails<IP_ADDRESS>@ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
Is there a better way to pursue this solution?
--JWM

Nope.... tried suggestion above (mklink)
$ gem uninstall -a libv8 mini_racer
Successfully uninstalled libv8-6.3.292.48.1-x86_64-darwin-16
Successfully uninstalled libv8-6.7.288.46.1-universal-darwin-16
$ bundle
Fetching mini_racer 0.1.15
Installing mini_racer 0.1.15 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
Platform is Mohave, rails<IP_ADDRESS>@ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
Is there a better way to pursue this solution?
--JWM

I am having the same issue and tried mkllnk's solution also, but it's still failing.
macOS Mojave 10.14.5
ruby v2.3.0p0 (2015-12-25 revision 53290)
rails v4.2.3

The solution I posted worked only for a while for us. Then developers using MacOS couldn't run the project any more. We since reverted back to therubyracer (0.12.0) because we couldn't find a solution.

have you tried upgrading your mini_racer version to the latest released?

No, we still use Ruby 2.1.5 which is out of support now.

The fixes above no longer work as there is another issue with installing mini_racer 0.1.15 on new MacOS. It has been fixed  (ld: library not found for -lstdc++). This has been fixed in newer versions (0.2.3 to be exact, https://github.com/discourse/mini_racer/commit/644487e976f3a05de9964617cdbd90506bad918b)

Hi,
The mini_racer 0.1.15 pile-up is extremely frustrating!  I was able to work around it back in January and from that process I kept these notes:
Bundler site:  https://bundler.io/docs.html https://bundler.io/docs.html
How to fix the problem with mini_racer ‘0.1.15'
$ bundle remove mini_racer
$ bundle add mini_racer
Verify is now in gem file.lock at right level.  It’s that simple.
This may not entail using bundler2.  In the back of my mind I’m thinking it wasn’t quite that simple, but it was correct to dig into bundler and use it’s tools to thread the needle and get the right version of a java run time in Gemfile and Gemfile.lock.
The fact that I am able to work on this code set and have steadily been doing that since I sorted this out last winder means it can be done!  By the way I was initially migrating from early. Rails to v5.2.3.
Good luck!
JWM

On Jun 12, 2019, at 1:40 AM, Petko Bordjukov<EMAIL_ADDRESS>wrote:
The fixes above no longer work as there is another issue with installing mini_racer 0.1.15 on new MacOS. It has been fixed (ld: library not found for -lstdc++). This has been fixed in newer versions (0.2.3 to be exact, 644487e https://github.com/discourse/mini_racer/commit/644487e976f3a05de9964617cdbd90506bad918b)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/discourse/mini_racer/issues/92?email_source=notifications&email_token=AAAMTEVFEI24OXFUMF5GL63P2CZA5A5CNFSM4FLMT6BKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXPVX7Y#issuecomment-501177343, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAMTEQT2EHCU7KLRCFHNXDP2CZA5ANCNFSM4FLMT6BA.

John
<EMAIL_ADDRESS>+1<PHONE_NUMBER>
www.linkedin.com/in/jwmount/


Feature: Add a method that checks if database is connected or not

Is your feature request related to a problem?
if somehow the connection dropped, there is no way to check if the driver is still connected or not, and you wont notice it until the application throws a exception
Describe the solution
a easy solution would be to add a method called checkConnetion or something that refers to checking the connection, the method would be a boolean and would return true if database is connected else false
Alternative methods
Yes, for now i am using a alternative way to check if its connected or not
public boolean checkConnection() {
        try {
            driver.ping();
        } catch (Exception e) {
            return false;
        }

        return true;
    }

SurrealDB version
1.0.0
Contact Details
<EMAIL_ADDRESS>Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

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

Is there any reason why would you need to know that the connection is severed if you aren't using the client? Surely, you would only need that information once you tried using the client, like in the existing solution, no?

well i run a discord bot, and it uses surrealdb, well for some reason the database dropped the connection, its been happning for quite a while recently, and sometimes even the surrealdb it self crashes, with this connection check we can atleast either try to reconnect to database or notify the issue, and might aswell connect to a backup
as for the issue with connection dropping i have asked this in surrealdb's discord and the devs has replied to it, but still its being discussed there

Are you able to capture the logs for the database crashing? And open an issue in the surrealdb/surrealdb repo for it - the database certainly shouldn't be crashing.
RE the disconnects - tcp connections can drop at any point and the only way to determine that the connection is dropped is with a timeout on receiving data. So a is connected doesn't particularly work, unless we are relying on heartbeats. I am not sure if the driver currently supports heartbeats, but could definitely look into it. Either way, I don't think the helper function would be particularly useful - you can't really action the boolean. We should have event handling of a failed connection instead.

public boolean checkConnection() {
try {
driver.ping();
} catch (Exception e) {
return false;
}
    return true;
}

The implementation would be slightly different. The protocol already supports pings (and we should add that to the driver). We would then use that liveness as the value.
We can certainly add this method, as I can see people wanting it even though it's not quite necessary. It would certainly help in determining if a client passed as an argument has been connected or not. So we can add this.

it would be great if you guys add one, thanks in advance


Remove typescript-vscode-sh-plugin

Tracks removing typescript-vscode-sh-plugin
This TypeScript service plugin added support for semantic highlighting before a proper api was exposed to VS Code
Semantic highlighting has been supported for three major TS releases now, so I think we should remove the typescript-vscode-sh-plugin. Users only older TS versions can install it to their workspace if they rely on semantic highlighting

/cc @aeschli Let me know if you have any concerns about this

No concerns!


Position Sticky not working

Current Behavior:
The figma plugin for eos-icons doesn't have a sticky search bar and the dropdowns.
What I found out is that the code is implemented in the CSS but is not working
https://user-images.githubusercontent.com/67755381/159114878-f3fa040e-7412-455c-8694-1ef11808830e.mp4

Expected Behavior:
The search bar and the dropdown should be made sticky so that they can appear if user scrolls the plugin.

I am working on this.


AdamW does not have args warmup and t_total

In finetune_on_pregenerated.py, below code throw error cause AdamW does not have those two arguments. This can be fixed by comment out those two columns but not sure if that means warmup will be not effective after that?
optimizer = AdamW(optimizer_grouped_parameters,
lr=args.learning_rate)
#warmup=args.warmup_proportion,
# t_total=num_train_optimization_steps)

Yes this example should have been updated now by #797.
Regarding AdamW and the schedule, details, and examples for the conversion are indicated in the migration section of the readme: https://github.com/huggingface/pytorch-transformers#Migrating-from-pytorch-pretrained-bert-to-pytorch-transformers


Custom exit code for fallback mode error

Story
https://trello.com/c/GCRO05YP/513-custom-exit-code-when-cannot-connect-to-the-api-and-fallback-mode-is-disabled
Description
Allow users to set a custom error exit code (KNAPSACK_PRO_FALLBACK_MODE_ERROR_EXIT_CODE) whenever Knapsack Pro fails because Fallback Mode cannot be used.
Since we are catching the error, we don't print the backtraces anymore. This is a plus as you'd expect those only in case of an unhandled error. See below for the actual differences.
This PR also removes a test that fails deterministically with bundle exec rspec spec --seed 20635.
Checklist reminder

[x] You added the changes to the UNRELEASED section of the CHANGELOG.md, including the needed bump (ie, patch, minor, major)
[x] You follow the architecture outlined below for RSpec in Queue Mode, which is a work in progress (feel free to propose changes):

Pure: lib/knapsack_pro/pure/queue/rspec_pure.rb contains pure functions that are unit tested.
Extension: lib/knapsack_pro/extensions/rspec_extension.rb encapsulates calls to RSpec internals and is integration and e2e tested.
Runner: lib/knapsack_pro/runners/queue/rspec_runner.rb invokes the pure code and the extension to produce side effects, which are integration and e2e tested.

Comparison before/after
I run locally Knapsack Pro with:
  KNAPSACK_PRO_ENDPOINT=http://TODOapi.knapsackpro.test:3000 \
  KNAPSACK_PRO_MAX_REQUEST_RETRIES=0 \
  KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false \

And additionally (to check the other failure path):
  KNAPSACK_PRO_FALLBACK_MODE_ENABLED=true \
  KNAPSACK_PRO_CI_NODE_RETRY_COUNT=1 \

bin/knapsack_pro_rspec; echo $?
after
W, [2024-11-08T16:40:34.478942 #90791]  WARN -- : [knapsack_pro] POST http://TODOapi.knapsackpro.test:3000/v1/build_distributions/subset
W, [2024-11-08T16:40:34.479047 #90791]  WARN -- : [knapsack_pro] Request failed due to:
W, [2024-11-08T16:40:34.479080 #90791]  WARN -- : [knapsack_pro] #<Errno::ECONNREFUSED: Failed to open TCP connection to TODOapi.knapsackpro.test:3000 (Connection refused - connect(2) for "TODOapi.knapsackpro.test" port 3000)>
E, [2024-11-08T16:40:34.479153 #90791] ERROR -- : [knapsack_pro] Fallback Mode was disabled with KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false. Please restart this CI node to retry tests. Most likely Fallback Mode was disabled due to https://knapsackpro.com/perma/ruby/regular-mode-connection-error-with-fallback-enabled-false
1

before
W, [2024-11-08T16:44:33.584195 #90992]  WARN -- : [knapsack_pro] POST http://TODOapi.knapsackpro.test:3000/v1/build_distributions/subset
W, [2024-11-08T16:44:33.584308 #90992]  WARN -- : [knapsack_pro] Request failed due to:
W, [2024-11-08T16:44:33.584334 #90992]  WARN -- : [knapsack_pro] #<Errno::ECONNREFUSED: Failed to open TCP connection to TODOapi.knapsackpro.test:3000 (Connection refused - connect(2) for "TODOapi.knapsackpro.test" port 3000)>
E, [2024-11-08T16:44:33.584396 #90992] ERROR -- : [knapsack_pro] Fallback Mode was disabled with KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false. Please restart this CI node to retry tests. Most likely Fallback Mode was disabled due to https://knapsackpro.com/perma/ruby/regular-mode-connection-error-with-fallback-enabled-false
rake aborted!
Fallback Mode was disabled with KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false. Please restart this CI node to retry tests. Most likely Fallback Mode was disabled due to https://knapsackpro.com/perma/ruby/regular-mode-connection-error-with-fallback-enabled-false
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/allocator.rb:32:in `test_file_paths'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/runners/base_runner.rb:16:in `test_file_paths'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/runners/base_runner.rb:28:in `test_files_to_execute_exist?'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/runners/rspec_runner.rb:16:in `run'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/tasks/rspec.rake:7:in `block (2 levels) in <top (required)>'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/exe/rake:27:in `<top (required)>'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/bin/ruby_executable_hooks:22:in `eval'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/bin/ruby_executable_hooks:22:in `<main>'
Tasks: TOP => knapsack_pro:rspec
(See full trace by running task with --trace)
1

bin/knapsack_pro_queue_rspec; echo $?
after
I, [2024-11-08T16:40:55.104101 #90819]  INFO -- : [knapsack_pro] KNAPSACK_PRO_FIXED_QUEUE_SPLIT is not set. Using default value: true. Learn more at https://knapsackpro.com/perma/ruby/fixed-queue-split
W, [2024-11-08T16:40:55.109043 #90819]  WARN -- : [knapsack_pro] POST http://TODOapi.knapsackpro.test:3000/v1/queues/queue
W, [2024-11-08T16:40:55.109099 #90819]  WARN -- : [knapsack_pro] Request failed due to:
W, [2024-11-08T16:40:55.109132 #90819]  WARN -- : [knapsack_pro] #<Errno::ECONNREFUSED: Failed to open TCP connection to TODOapi.knapsackpro.test:3000 (Connection refused - connect(2) for "TODOapi.knapsackpro.test" port 3000)>
E, [2024-11-08T16:40:55.109230 #90819] ERROR -- : [knapsack_pro] Fallback Mode was disabled with KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false. Please restart this CI node to retry tests. Most likely Fallback Mode was disabled due to https://knapsackpro.com/perma/ruby/queue-mode-connection-error-with-fallback-enabled-false

Finished in 0.08829 seconds (files took 2.85 seconds to load)
0 examples, 0 failures

1

It's a bit unfortunate that we print the summary as it seems nothing went wrong. But I think it's not that bad.
before
I, [2024-11-08T16:44:55.087071 #91021]  INFO -- : [knapsack_pro] KNAPSACK_PRO_FIXED_QUEUE_SPLIT is not set. Using default value: true. Learn more at https://knapsackpro.com/perma/ruby/fixed-queue-split
W, [2024-11-08T16:44:55.091751 #91021]  WARN -- : [knapsack_pro] POST http://TODOapi.knapsackpro.test:3000/v1/queues/queue
W, [2024-11-08T16:44:55.091798 #91021]  WARN -- : [knapsack_pro] Request failed due to:
W, [2024-11-08T16:44:55.091821 #91021]  WARN -- : [knapsack_pro] #<Errno::ECONNREFUSED: Failed to open TCP connection to TODOapi.knapsackpro.test:3000 (Connection refused - connect(2) for "TODOapi.knapsackpro.test" port 3000)>
E, [2024-11-08T16:44:55.091895 #91021] ERROR -- : [knapsack_pro] Fallback Mode was disabled with KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false. Please restart this CI node to retry tests. Most likely Fallback Mode was disabled due to https://knapsackpro.com/perma/ruby/queue-mode-connection-error-with-fallback-enabled-false

Finished in 0.08774 seconds (files took 2.71 seconds to load)
0 examples, 0 failures

E, [2024-11-08T16:44:55.094315 #91021] ERROR -- : [knapsack_pro] An unexpected exception happened. RSpec cannot handle it. The exception: #<RuntimeError: Fallback Mode was disabled with KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false. Please restart this CI node to retry tests. Most likely Fallback Mode was disabled due to https://knapsackpro.com/perma/ruby/queue-mode-connection-error-with-fallback-enabled-false>
E, [2024-11-08T16:44:55.094358 #91021] ERROR -- : [knapsack_pro] Exception message: Fallback Mode was disabled with KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false. Please restart this CI node to retry tests. Most likely Fallback Mode was disabled due to https://knapsackpro.com/perma/ruby/queue-mode-connection-error-with-fallback-enabled-false
E, [2024-11-08T16:44:55.094463 #91021] ERROR -- : [knapsack_pro] Exception backtrace: /Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/queue_allocator.rb:34:in `test_file_paths'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/runners/queue/base_runner.rb:29:in `test_file_paths'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/runners/queue/rspec_runner.rb:153:in `pull_tests_from_queue'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/runners/queue/rspec_runner.rb:78:in `block in with_batch'
<internal:kernel>:187:in `loop'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/runners/queue/rspec_runner.rb:76:in `with_batch'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/extensions/rspec_extension.rb:93:in `block (2 levels) in knapsack__run_specs'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rspec-core-3.13.0/lib/rspec/core/configuration.rb:2091:in `with_suite_hooks'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/extensions/rspec_extension.rb:92:in `block in knapsack__run_specs'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rspec-core-3.13.0/lib/rspec/core/reporter.rb:74:in `report'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/extensions/rspec_extension.rb:91:in `knapsack__run_specs'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/runners/queue/rspec_runner.rb:54:in `run'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/knapsack_pro/runners/queue/rspec_runner.rb:20:in `run'
/Users/riccardoodone/code/knapsack/knapsack_pro-ruby/lib/tasks/queue/rspec.rake:12:in `block (3 levels) in <top (required)>'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/task.rb:279:in `block in execute'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/task.rb:279:in `each'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/task.rb:279:in `execute'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/task.rb:199:in `synchronize'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/task.rb:188:in `invoke'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/application.rb:188:in `invoke_task'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/application.rb:138:in `block (2 levels) in top_level'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/application.rb:138:in `each'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/application.rb:138:in `block in top_level'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/application.rb:147:in `run_with_threads'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/application.rb:132:in `top_level'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/application.rb:83:in `block in run'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/application.rb:214:in `standard_exception_handling'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/lib/rake/application.rb:80:in `run'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/gems/rake-13.2.1/exe/rake:27:in `<top (required)>'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/bin/rake:25:in `load'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/bin/rake:25:in `<main>'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/bin/ruby_executable_hooks:22:in `eval'
/Users/riccardoodone/.rvm/gems/ruby-3.3.5/bin/ruby_executable_hooks:22:in `<main>'

1

#suggestion
Ensure the new feature works in a real project scenario just in case.
# .circleci/config.yml

      - run:
          working_directory: ~/rails-app-with-knapsack_pro
          command: |
            # fallback ||
            export KNAPSACK_PRO_ENDPOINT=https://api-fake.knapsackpro.com
            export KNAPSACK_PRO_MAX_REQUEST_RETRIES=1
            bundle exec rake knapsack_pro:rspec

      # add the following
      - run:
          working_directory: ~/rails-app-with-knapsack_pro
          command: |
            # fallback off and custom exit code ||
            export KNAPSACK_PRO_ENDPOINT=https://api-fake.knapsackpro.com
            export KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false
            export KNAPSACK_PRO_FALLBACK_MODE_ERROR_EXIT_CODE=0 # won't fail the build and it won't run tests
            bundle exec rake knapsack_pro:rspec

...

# queue

      - run:
          working_directory: ~/rails-app-with-knapsack_pro
          command: |
            # fallback ||
            export KNAPSACK_PRO_ENDPOINT=https://api-fake.knapsackpro.com
            export KNAPSACK_PRO_MAX_REQUEST_RETRIES=1
            bundle exec rake knapsack_pro:queue:rspec

      # add the following
      - run:
          working_directory: ~/rails-app-with-knapsack_pro
          command: |
            # fallback off and custom exit code ||
            export KNAPSACK_PRO_ENDPOINT=https://api-fake.knapsackpro.com
            export KNAPSACK_PRO_FALLBACK_MODE_ENABLED=false
            export KNAPSACK_PRO_FALLBACK_MODE_ERROR_EXIT_CODE=0 # won't fail the build and it won't run tests
            bundle exec rake knapsack_pro:queue:rspec

Ensure the new feature works in a real project scenario just in case.

I decided not to test it e2e because:

it's already covered at the integration level
it's a marginal feature
the proposed tests is a bit hacky

I'd prefer to keep the e2e tests as smoke tests that don't cover edge cases.


Allow ontology as input parameter

Validating the mappings according to the ontology is specially relevant when sources are complex and there are many mapping rules

This will not be be added in the short term


add dockerimage to readme

Minimal docker image containing Ubuntu + Miniconda + Jupyter notebook + Torch + iTorch kernel

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Thanks!


Suggest IT companies, conferences, education, certificates, communities, podcasts, and internships in Croatia

In the continuous effort to make the IT Croatia a comprehensive and up-to-date resource, I am seeking suggestions from the community for IT companies, conferences, education, certificates, communities, podcasts, and internships in Croatia.

.debug konferencija

Thank you for the suggestion @wast - added!


Add GUI NavBar

1. Default view:
Displays a list of contacts.

2. Events view:
Currently shows an empty list, which will be populated with event details in future updates.

Codecov Report
Attention: Patch coverage is 0% with 23 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/main/java/seedu/address/ui/MainWindow.java
0.00%
14 Missing :warning:

src/main/java/seedu/address/ui/NavBar.java
0.00%
9 Missing :warning:

Files with missing lines
Coverage Δ
Complexity Δ

src/main/java/seedu/address/ui/NavBar.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)


[generic] fails to extract title

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that a supported site is broken
[X] I've verified that I'm running yt-dlp version 2023.03.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
World
Provide a description that is worded well enough to be understood
While the generic extractor fetches the audio file from "In the Studio" podcacsts just fine, it fails to extract the title. Looking at the dumped web page, the title is as easy as it gets: Within a <title> / </title> tag.
I haven't managed to figure out why the given title regex search doesn't match this.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--get-title', 'https://www.inthestudio.net/online-on-demand/rolling-stones-some-girls/']
[debug] User config "/home/barsnick/.config/yt-dlp/config": ['-o', '%(title)s [%(extractor)s %(id)s].%(ext)s']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[392389b7d] (source)
[debug] Lazy loading extractors is disabled
[debug] Git HEAD: 21b9413cf
[debug] Python 3.11.3 (CPython x86_64 64bit) - Linux-6.2.14-300.fc38.x86_64-x86_64-with-glibc2.37 (OpenSSL 3.0.8 7 Feb 2023, glibc 2.37)
[debug] exe versions: ffmpeg 6.0 (setts), ffprobe 6.0, phantomjs 1.9.8
[debug] Optional libraries: Cryptodome-3.17.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[debug] Proxy map: {}
[debug] Loaded 1813 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>yt-dlp is up to date<EMAIL_ADDRESS>[generic] Extracting URL: https://www.inthestudio.net/online-on-demand/rolling-stones-some-girls/
[generic] rolling-stones-some-girls: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] rolling-stones-some-girls: Extracting information
[debug] Looking for embeds
[debug] Identified a JW Player data
WARNING: Extractor failed to obtain "title". Creating a generic title instead
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec:vp9.2(10), channels, acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] rolling-stones-some-girls: Downloading 1 format(s): 0
generic video #rolling-stones-some-girls

yt-dlp: generic video #rolling-stones-some-girls
yt-dl: Rolling Stones- Some Girls 45th- Mick Jagger, Keith Richards, Ron Wood (ie, the page title).
Arguably yt-dlp is misleading since it's an audio (mp3) download.

After git bisect, I figured out:
Regression in ade1fa70cbaaaadaa4772e5f0564870cea3167ef

Arguably yt-dlp is misleading since it's an audio (mp3) download.

Indeed, but that's purely cosmetic, and I couldn't care less. ;-)
s/video/media/

It looks like this change to the generic extractor around l.2834->2840 means that the page title isn't being passed through to the JWPlayer extraction:
                     self.report_detected('JW Player data')
-                    return merge_dicts(info, info_dict)
+                    return [info]
             except ExtractorError:


How to Use Code Genaration ?

What is the status of the code generator? Is it actively working now? If it is working, can you give information about how it works?

Yes its working now, Issue was fixed few days back.

Yes its working now, Issue was fixed few days back.

Do you have any idea how it works? I'm not talking about the interface used to create the project.

The ApiClient Code Generation works by running the nswag-regen.ps1, if you are talking about some other code generation, I don't have any idea about it.

ApiClient Kod Üretimi, swagger json'ı açığa çıkarmak için api sunucusunu çalıştırırken nswag-regen.ps1'i çalıştırarak çalışır, eğer başka bir kod üretiminden bahsediyorsanız, bu konuda hiçbir fikrim yok.

Yes, what I'm talking about is what I underlined in the picture.

Its not implemented yet, as it says, its still pending development


Make electron-toolkit/preload optional on package install

Clear and concise description of the problem
electron-toolkit/preload is a neat package that simplifies IPC code, but to use it, sandbox is required to be disabled because sandboxed preload scripts can only load polyfilled api.
Suggested solution
Would it be possible to make the preload package install optional, when you first initialize the project using npm create @quick-start? With an explanation as to why sandbox needs to be disabled if used? Would make for a nicer UX, especially for beginners like me.
Alternative
No response
Additional context
No response
Validations

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

Not only the electron-toolkit/preload module requires sandbox. All third-party modules require it. You can disable externalizeDep plugin (in preload config) to support sandbox and also you can use electron-toolkit/preload module and other  third-party modules. For developers, they need to have knowledge about sandbox before they can make a decision. It is inappropriate to choose in scaffolding.

I understand sandbox needs to be disabled to use any external modules. I
guess my thinking is that it's better to have it most secure by default,
and let people choose to disable sandbox if they want to, vs having it
disabled by default. And as far as I can see, preload is the only 3rd party
module loaded?
I also think it's a good thing to make developers think about sandbox
explicitly during scaffolding, as it involves application security, but I
understand where you are coming from and will not push this matter any
further.
Thanks for the response and thanks for building and maintaining the repo!
It's extremely useful.
On Sun, Feb 25, 2024 at 7:29 PM alex.wei @.***> wrote:

Not only the electron-toolkit/preload module requires sandbox. All
third-party modules require it. You can disable externalizeDep plugin (in
preload config) to support sandbox and also you can use
electron-toolkit/preload module and other third-party modules. For
developers, they need to have knowledge about sandbox before they can
make a decision. It is inappropriate to choose in scaffolding.
—
Reply to this email directly, view it on GitHub
https://github.com/alex8088/electron-vite/issues/425#issuecomment-1963212679,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7BLNKE2X6NAPK5OF54C7GTYVPXRFAVCNFSM6AAAAABDZCLRAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRTGIYTENRXHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@mdruuu Thanks for the suggestion, security practices are very important and I will improve this in the future including scaffolding and documentation.


fix: M1 and non-M1 macs now agree on xcodeproj

This PR resolves []
Description

M1 macs and non-M1 macs generated different EXCLUDED_ARCHS, because of https://github.com/facebook/react-native/blob/0.66-stable/scripts/react_native_pods.rb#L135-L139. That is fixed and remove on RN 0.67, but we are still on 0.66, so I added that tiny change as a patch, so our macs can stop fighting about what needs to be in that variable.
PR Checklist

[ ] I tested my changes on iOS / Android.
[ ] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Works in an m1, builds the app without generating the diff anymore 🤘

awesome! now to figure out what's wrong with the tests. do you both mind hitting cmd-u on Xcode?

awesome! now to figure out what's wrong with the tests. do you both mind hitting cmd-u on Xcode?

I missed this comment, happy to try it out


extend scaffolding examples

discuss potentially adding scaffolding for some popular frameworks/setups (e.g. React, Vue, ..) to make it easier for devs to integrate their smart contracts into an UI project

Some ideas:

have a zk project --monorepo command which creates the structure that we have currently, but in a subfolder which still leaves room for a UI (& server, etc) in the same git repo. You could then add a UI template as another subfolder to the same project., and we could set up node module resolution so that you just have to import from "myproject/zkapp" in your UI (or similar)
have a zk project --no-git command which can be used to scaffold everything as a subfolder in an existing git repo. This could be handy when you're starting out from a UI template which is already a git repo (not sure what options popular templates frameworks like Next / CRA give you re git)
Have custom commands for particular UI frameworks. My least favourite option as it requires far more work from us

I really like this.
We could add --sveltekit, --nextjs, --vue, & --monorepo and initialize the projects using their init commands (e.g. npm create svelte@latest ui,  npx create-next-app@latest ui , etc) or --monorepo creates an empty ui directory for the dev to put what they want in it.
This way our maintenance is reasonably low.
// zk project <name>

name/
  ui/
  contracts/

Note: This also requires an update to the zk file command to always create files inside within /contracts/src if it's a monorepo or inside src/ as currently does if not a mono repo, which is doable.

Which user experience do you all prefer? @mitschabaude @Trivo25 @ymekuria @MartinMinkov @bkase

1.) Command:

zk project foo --svelte

Help menu:

❯ zk project --help
zk project [name]
Create a new project
Options:
--svelte, --sveltekit  Creates an accompanying SvelteKit UI      [boolean]
--next, --nextjs       Creates an accompanying NextJS UI         [boolean]
--vue, --vuejs         Creates an accompanying VueJS UI          [boolean]
-h, --help                 Show help                                 [boolean]
-v, --version              Show version number                       [boolean]

2.) Command:

zk project foo --ui svelte

Help menu:

❯  zk project --help
zk project [name]
Create a new project
Options:
--ui       Creates an accompanying UI
[string] [choices: "svelte", "next", "vue"]
-h, --help     Show help                                             [boolean]
-v, --version  Show version number                                   [boolean]

The 2nd can be implemented a bit DRYer and feels more "correct", but is more to type for the user. The first may be easiest to remember.

@jasongitmail I love the direction this is going. I prefer the 2nd command although it's more verbose because it is more clear that a user is creating a project with a UI included. If a user enters zk project foo --ui , we could display all the available options for them to select similar to how a user can select which alias to deploy to when entering zk deploy with entering the alias.

I like the second one as well. It feels more intuitive to use, and for a CLI argument that can have multiple values, it feels better to specify it under a single option with a meaning that is easy to remember.

Cool. I put together a working version of this for Svelte, NextJS, & Vue. Took a bit of refactoring and needs more clean up and a lot more thinking through and testing.
I'll push a branch and open a PR so we can play with it.

I think we should ask this by default. Most people will want a UI — I think if you omit the —ui then there is a prompt asking you which one you want (with none as an option too)

Should we support a create react app version also? I personally prefer NextJS for React projects, but some devs may not. What does everyone think? Could be an addition further down the road if we get requests for it.
With this option, it will now be easy for devs to add their contracts into a UI directly through a file path. The question we should discuss and answer is what pattern we should recommend.

Add UI directly through a file path or
Publish to npm and import into the UI

The first option is definitely easier and will have less friction for devs. We could even add a very basic UI with the a contract and the mina provider connected into the template.

Agreed 100% , we should support create react app in addition to next

This has taken a great direction! I'd also still like the --monorepo flag to enable the long tail of ui setups which we don't support, or maybe add "empty" as an option to the --ui flag for getting a monorepo setup with an empty ui folder. This is what I'd personally use I guess.

With this option, it will now be easy for devs to add their contracts into a UI directly through a file path. The question we should discuss and answer is what pattern we should recommend.
1. Add UI directly through a file path or

2. Publish to npm and import into the UI

Definitely the first option! Publishing to npm has independent value for composability and visibility, but is not reasonable as a dev experience when iterating on a UI. Also we should stop recommending "npm link", in favor of the monorepo setup with a local import
What we could do is make the zkapp package name resolve to the local folder, so devs can use the same import as if it was coming from npm / npm link

maybe add "empty" as an option to the --ui flag

That's the approach I landed on too. 👍
WIP PR to play with. A dev can use any of these commands:
zk project foo
zk project foo --ui svelte     // SvelteKit
zk project foo --ui next        // NextJS
zk project foo --ui vue         // VueJS
zk project foo --ui empty
zk project foo --ui unsupported // shows user an error to select from one of supported choices

WIP. Tests need to be fixed and there are a few improvements I'd want to add, like a good monorepo README.  But this works to try it out. It could be further improved if all UI options allowed passing flags b/c I'd want to automatically add Prettier and ESLint to the UI project too.
I did NOT update the zk file command, so a dev would need ot be in their contracts dir, if using a monorepo for it to work. I want to give this more thought. Any options if you want that command to work in the monorepo root? We could support that, but I currently envision people to be cd'd into the project they're working on.

Definitely the first option! Publishing to npm has independent value for composability and visibility, but is not reasonable as a dev experience when iterating on a UI. Also we should stop recommending "npm link", in favor of the monorepo setup with a local import
What we could do is make the zkapp package name resolve to the local folder, so devs can use the same import as if it was coming from npm / npm link

To be explored still

For scaffolding a UI, are we just creating the UI project for the user or are we additionally modifying the scaffolded UI to be ready for use with SnarkyJS right away? If we are doing the latter, there are a few steps that should be included to make sure that someone can start using their UI as seamless as possible:

Set up correct headers on the server
Set up a global context with SnarkyJS where appropriate?

I'm probably missing others but we should land on either letting the user set up these details themselves or doing it for them.

or scaffolding a UI, are we just creating the UI project for the user or are we additionally modifying the scaffolded UI to be ready for use with SnarkyJS right away?

I'd like to land a smaller PR first and explore these afterward. Just to control complexity and let us kick the tires on this to ensure it works as expected across systems, etc first. Some of this will veer into "stuff we have to maintain" for each platform as it changes, so we will need to figure out tests too; but it'd be very useful.

Yeah I agree @MartinMinkov, setting correct headers and stuff needed to make it work should be definitely handled by us in these commands. But yeah separate PR.
I'm conflicted about the idea of adding imports snarkyjs / the contract for the user, or setting up global state (I guess you mean stuff like isReady, Mina,setActiveInstance?). It adds complexity for us; but it could potentially give lots of devs a less bumpy start.

I'd prefer to wait on Create React App, at least until there is demand for it

One data point is that Matej used CRA and had quite a bit of pain connecting it with snarkyjs, see https://github.com/o1-labs/snarkyjs/issues/385
I personally wouldn't use CRA anymore, but from my experience the fully client side rendered architecture is not necessarily ill performant if you're careful enough that the initial load is small, I like client side rendering tbh for its simplicity


investigate apache gaucamole

https://news.ycombinator.com/item?id=11744430

https://github.com/edoceo/guacamole-auth-http

https://www.cb-net.co.uk/linux/enabling-duo-dual-multi-factor-authentication-mfa-for-guacamole-docker/
https://www.cb-net.co.uk/linux/using-lets-encrypt-with-an-nginx-docker-container-plus-bye-bye-startssl/


Feat: Add beta support for anthropic

The anthropic beta API has multiple features  other than those currently supported by instructor. This PR enables the ability to connect to the beta api endpoint to use any of them.

[!IMPORTANT]
Adds beta parameter to from_anthropic() in client_anthropic.py to support beta message creation.

Behavior:

Adds beta parameter to from_anthropic() in client_anthropic.py.
When beta is true, uses client.beta.messages.create instead of client.messages.create.

Functionality:

Supports both synchronous and asynchronous client types.
Ensures compatibility with enable_prompt_caching and beta parameters.

This description was created by  for 047a5bb609a8c22a85951cd4a4af3c5024c812f9. It will automatically update as commits are pushed.

can you make sure to run ruff and add docs

I have run my ruff on my submission. If I run it one everything there are 30+ files changed beyond what I have modified, would you like me to commit those changes?

i got devin to fix it off your PR :)


Add failing test for deleting a language

Details: https://github.com/lunarphp/lunar/issues/785

Can't seem to reproduce with tests after all, nvm.


How to call undocumented Plotly calls

Is there a way to call Plotly.Fx.hover using this wrapper?  We have a a need for that functionality based on the code from this page: https://plot.ly/javascript/hover-events/#triggering-hover-events

The plotly instance could be passed back to the component via an event and then you could use anything in it. I can do a quick PR for this if still interested.
 // Plotly.vue
  mounted() {
    Plotly.newPlot(this.$el, this.data, this.innerLayout, this.options);
    events.forEach(evt => {
      this.$el.on(evt.completeName, evt.handler(this));
    });
    this.$emit("plotlyready", Plotly);
  },

@sjennen You can import ploty in your code to access  Plotly.Fx.hover.

@David-Desmaisons could you give an example? I don't find anything related to Fx in plotly when imported.

It's been a while since anyone commented on this, but here's what I did:
import { Plotly } from 'vue-plotly'
import * as PlotlyJs from 'plotly.js'
// then
PlotlyJs.Fx.hover()


Error when running inference on CPU using C++ bindings: Not found: Container localhost does not exist

System information

Have I written custom code: yes
OS/Distro: Arch Linux
TensorFlow installed from: virtualenv with pip, C/C++ bindings from source without CUDA support
TensorFlow version virtualenv: v1.12.1-34938-g99fea8da0d 2.3.0-rc0
TensorFlow version C/C++ bindings: v1.12.1-35361-ge89160d8d3 2.5.0-dev20200629
Python version: 3.7
Bazel version: 3.1.0- (@non-git)
GCC/Compiler version: 10.1.0
CUDA/cuDNN version: 10.2z (Error happens on CPU)
GPU model and memory: Nvidia RTX 2080 Ti

Describe the current behavior
Predicting works fine in Python, however when I try to run inference on CPU by using the C++ bindings I get the following error:
Failed precondition: Error while reading resource variable dense/kernel from Container: localhost. This could mean that the variable was uninitialized. Not found: Container localhost does not exist. (Could not find resource: localhost/dense/kernel)
	 [[{{node dense/Tensordot/ReadVariableOp}}]]

Describe the expected behavior
Being able to predict in C++ without issues.
Standalone code to reproduce the issue
Code is on pastebin.com to increase readability. Links:
Training the model in Python
C++ Header
C++ Code
cli_saved_model --dir ... --all output
Other info / logs
A similar issue was already posted on Stackoverflow, however with no answers.
Issue is persistent in TF2.2.

Might not be the same cause as for you, but I just had a very similar issue with a self-built TF2.2. In my case it was caused by trying to load a saved model from a folder where I only put a saved_model.pb, but not the variables subfolder. When I copied the variables there as well, it started working again.

@TylerTheHumanCompiler
Please update as per above comment, there is a similar issue please refer and let us know if it helps.
#28287

@Saduf2019 The variables folder exists and is populated. Can I provide you with additional information?
As for the tf update: I've compiled from source and now have:
v1.12.1-35409-ge085901e2c 2.4.0

@TylerTheHumanCompiler
Is there any particular reason for using tf 1.12 when there are later versions available.
Please upgrade the tf version and see if you still face the issue as this is a very old version that does not have support [please use 1.15 or 2.x versions].

@Saduf2019 No, there isn't, because I'm not using tf 1.12. I don't know why tf.version.GIT_VERSION outputs this, but there are reports of it outputting a wrong version here. Note that the hash above ge085901e2c matches no commit, whereas tf.version.VERSION outputs 2.4.0. Further, my libraries in /usr/lib are named libtensorflow_cc.so.2.4.0, and libtensorflow_framework.so.2.4.0, and printing the tf version in C++ using TF_VERSION_STRING (defined in core/public/version.h) also gives me 2.4.0.
I used to following code for installation:
git clone git://github.com/tensorflow/tensorflow.git
cd tensorflow
git checkout master
./configure
bazel build -c opt --config=numa --config=v2 //tensorflow:libtensorflow_cc.so
bazel build --verbose_failures -c opt --config=numa --config=v2 //tensorflow/tools/pip_package:build_pip_package
./bazel-bin/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg
sudo pip install /tmp/tensorflow_pkg/tensorflow-2.4.0-cp38-cp38-linux_x86_64.whl

Note that the hash above ge085901e2c does not match any commit

The 'g' at the start seems to mean "git" or "group", the hash itself is the following part: e085901e2c (matching what you found using git rev-list).

@DouglasLivingstone thanks for shedding light on this.

I don't work on TF anymore, sorry!

Any updates on this?

@TylerTheHumanCompiler Could you please try on latest stable version of tf 2.5 or 2.4.1 and let us know if this is still an issue.Thanks!


RFC JSON Schema-based record editor (replacement for BibEdit)

Problem
BibEdit served well in Invenio 1.x but is MARC-centric and is not designed for extensibility. Since Invenio is moving towards using jsonalchemy as its record representation (thus opening the ports for infinitely flexible record models), an hardcoded table-based web editor is no longer sufficient to natively edit Invenio records.
Proposal
Since jsonalchemy is about (inveniosoftware/jsonalchemy#9) to support JSON Schemas which is a proposed standard to describe JSON models (including validation), we could automatically generate a form that allows the cataloger to edit a given record according to the schema. This would allow the system to leverage on data models, for more and more consistent records.
It happens that this is already implemented thanks to json-editor. E.g. see: http://jeremydorn.com/json-editor/.
Starting from this pre-existing editor one can build around/on top of it additional functionalities such as:

[ ] record preview
[ ] PDF preview
[ ] auto-completion based on KBs
[ ] automatic linking (e.g. when editing an arXiv ID, to be able to jump to it)
[ ] server side validation based on JSONAlchemy
[ ] keyboard shortcuts
[ ] re-ordering through drag&drop
[ ] editing references to other records (e.g. author signatures, affiliations, citations, superseeding... see #2573)
[ ] shurtcuts such as *automatically generating new field instances by splitting the content of a given field

+1
Ideally, it would great if the editor could work for not only records by also documents, authors, and all the other jsonalchemy namespaces we may have.

Yes, I guess this will come transparently if the corresponding JSONs are available through the same APIs. On the other hand I would like to foreseen into this nice previewers (for PDF/detailed record view) as this is really what is needed by a cataloguer. Not sure how to implement this in a generic way.

Guess we might have sorts of default widgets that can be configured to be enabled upon given models.

I think you can simply solve it by having editors per module, as long as they can rely mostly on common code.

Looks promising!

There is some really good idea, that we will perhaps at TIND implements for master like the PDF preview, record preview.
But will we not loose all of the specificity of BibEdit ? I mean what it seems to be will be like in django the administration interface that can manipulate everything.
Currently we are adding librarian specific functionnalities to BibEdit, but if the editor become multi-roles I don't see how it will be possible to adds all this functionnalities.
Perhaps did I misunderstand, any hint ?

What are the specificities of BibEdit you think are going to miss? The proposed editor is going to adapt to the given schema, thus allowing the cataloguer to only enter valid metadata (up to the provided constraints).
Additional niceties such as shortcuts for reference extractions, PDF previewer etc. could be added in the form of simple widgets or block that are conditional on the type of document being opened...

For example we have a check which print a flash message if someone entered an ISBN which is already existing. We have hint which popup depending of the tag of fields, if autocompletion is active for this field etc... shortcut indicators, what does the MARC tags means, we have complex autocompletion on authority, if you select and authority record for autocompletion we can copy some information from the authority record etc ...
And we would like to add more things.
So it is why I would like to be sure it will not be a problem in the future if we want to add features.

So this editor is JSON based so it will not support MARC tags and indicators. These will have sense only as part as their importing into Invenio and the corresponding exporting.
On the other hand, yes, I plan to have fancy validator being possible. This JSON-Editor is fully pluggable, so one can add local tricks such as the proposed ISBN one. Hints for sure! Autocompletion for sure.
Have a look at the demo at http://jeremydorn.com/json-editor/ .
All the missing parts that we would have to add locally are listed as subtasks of this ticket.

Note that on the other hand, if you decide to stay fully on MARC as internal format, BibEdit is still there. AFAIK @jmartinm managed to fix the small glitches needed to make it work on Invenio 2

Okay so that is good news.
In another hand, are we agree that from the title of the RFC we are discussing of BibEdit, that will be replaced by JSON Schema-based record editor. (That I start to doubt if @jmartinm  kept it alive).
And that BibEdit is manipulating records, that are composed of MARC fields, so it is a bit strange to say that it will not support them.
I looked at the demo and even if I have faith in you I am a bit worried.  I don't really see how it will be able to replace BibEdit.

And that BibEdit is manipulating records, that are composed of MARC fields, so it is a bit strange to say that it will not support them.

We are going to provide (almost) 1:1 mapping between MARC and JSON in https://github.com/inveniosoftware/jsonalchemy/pull/9.

I looked at the demo and even if I have faith in you I am a bit worried. I don't really see how it will be able to replace BibEdit.

Once you have a both directional mapping it's pretty straight-forward to support (almost) full MARC21 standard.

And that BibEdit is manipulating records, that are composed of MARC fields, so it is a bit strange to say that it will not support them.

We are going to provide (almost) 1:1 mapping between MARC and JSON in inveniosoftware/jsonalchemy#9.

Okay so it makes sense ! The architecture is interesting.
But from the demo I still don't really see how will be the user-case "modify a record" (let say 100__a [Marc author field]), from the moment the guy click on the edit this record to the action completed.
I mean how will the modification interfaces will be, what will be the different steps etc.
Thanks for you answers !

@PXke Besides an option of relying on 1:1 mapping between MARC and JSON, let me mention another option.  If cataloguers of an Invenio instance are fully living in the MARC world, editing only MARC files, and would like to keep it that way, then they wouldn't have to use this new JSON editor at all.  (It would be an "internal editor" in this case.)  The cataloguers could presumably use (refreshed) BibEdit or some say MS Windows editing tool that speaks MARC-in, MARC-out, and talks to Invenio via REST API, so that they would perform and upload changes that way.  Just to mention this other theoretical possibility.

I think you can simply solve it by having editors per module, as long as they can rely mostly on common code.

:+1: for editing each JSON namespace in this way

But from the demo I still don't really see how will be the user-case "modify a record" (let say 100__a [Marc author field]), from the moment the guy click on the edit this record to the action completed.

So: say the cataloger reaches /record/123/jsonedit, this would open up the editor which would receive the record representation in JSON and the corresponding JSON Schema matching the model of the record (that depends on JSONAlchemy and how it will evolve). Based on JSON Schema an editor is automatically built that will allow the cataloger to manipulate the defined properties according to the defined constraints. If the cataloger wants to add a new author (s)he will have to reach for the corresponding field in the editor and click on a plus button. Of course this can be optimized and we can introduce shortcuts such as automatically jumping fields (according to the provided JSON-Schema) using some search query (e.g. as you would do in your shell with Ctrl+R).
Anyway, after having edited the JSON using the editor (and having everyfield validated client side thanks to JSON-Schema), the cataloger submits it and it's then validated sever side and uploaded.

I start to using this approach for deposit forms in the analysis preservation project. It won't cover all the mentioned features, but the first results look very very promising. My current plan is to create a special JsonField field for the deposit, which uses the json-editor as a frontend and validates the schema in the editor (for convenience) and on the server side (for security). So if someone has questions about this technology or wants to see code in very unready+unstable state, feel free to ask.
If someone wonders: This will NOT replace normal deposit forms. They are always better than auto-generated ones. But we expect to have many different forms for many different data catalogues.

Hi @crepererum, will you attack at the same time some of the points listed in the beginning of this RFC? (e.g. autocompletion from KBs)

@kaplun that's low priority, because I don't need that for the deposition part.

Some updates for you guys: I started to stress-test the json-editor using a record with >3000 authors.
Let's start with the bad news: Chrome on my desktop machine (proper i7 + 8GB + SSD) needs ~35seconds to generate the form. During this time, the site is unusable. On Firefox the situation is even worse. After I went through the json-editor source code I think that it is totally unusable for this task. The data and update handling is way to inefficient (e.g. O(n^2) when processing arrays).
The good news: I managed to render the form in <3sec using good old plain JavaScript. And there is room for improvement (e.g. use elements p instead of input and generate the input fields only on click/access, because input fields seem to be very heavy food for the browser). There are many features missing (e.g. add/sort array elements, change types, collapsing) but I'm already able to retrieve JSON from the form. And the data handling looks good so far. For validation I would try https://github.com/geraintluff/tv4 + lightweight local validation (so you get errors directly when editing fields).
Btw: I won't use clusterize.js because on my browserS it is slower than a rendered form and is very unsmooth when scrolling. I think up-to-date browers are will work here very well when we are smart enough to provide them the right (KISS-)input.
CC @kaplun @egabancho

Uh oh! I was fearing that. Regarding clusterize I think there is an other similar javascript trick (@eamonnmag I never remember its name...) Is it really impossible to improve the situation?
Because basically it would mean giving up on generating forms from schemas...

Nevermind, what @eamonnmag was talking me about was precisely clusterize.

One side solution, is simply that we exclude author fields when they are larger than N, as anyway a JS editor is probably not the right tool to manipulate them.

Indeed. @crepererum, I was looking at the performance levels for input as well recently. One possible change, if you wanted to keep input like features would be to use the editable content feature of HTML5 (but this requires an up to date browser) - this is pretty fast. I wrote a test here with 3000 generated elements http://jsfiddle.net/xL7c8ke7/ - but using a p tag is probably best for support of older browsers.

@kaplun when the form IS generated, scrolling feels very smooth. So you don't get anything of this hack (which is basically the try to be more efficient in JS than your browser when it comes to viewport calculation, which sounds ridiculous to me). Also I think clusterize only works with an all-eqal-height-row table layout. The generation itself could be improved (as I mentioned).
Getting the form from schemas (=json-editor) instead of the JSON (=status now) should not be a problem but I need some time to implement this. The problem with json-editor is not the schema-handling, but the coding style in general, a suboptimal "just always update+signal+check everything" (works fine for small records, sure) and a not-that-cooperative maintainer (just have a look at all the open and uncommented PRs).

@eamonnmag I thought about that one as well. I will evaluate both. My current idea is: use p plus click-listener (and some others) to detect when the user wants to write into the specific field. If so, we generate an input field which gets removed when the focus (of the field, not the window) is lost. That assumes that the browser handles the amount of listeners well (which I think is the case, at least better than all the input fields).

@crepererum you only need one listener on the class of the element, then you can assert the id and build the input from that. e.g. http://jsfiddle.net/hs27btp6/

@eamonnmag This is the reason why I do NOT use jquery, because it hides a very bad fact here:
$(".author").bind("click", function () {
    alert(this.id);
})

equals (under the hood)
var _f = function () {
    alert(this.id);
};
var _all = document.getElementsByClassName('author');
for (var _i = 0; _i < _all.length; ++_i) {
  _all[_i].addEventListener('click', _f.bind(_all[_i]));
}

Event listeners have to be registered on specific DOM elements. You could in fact register one listener on something like form and then use the mouse coords to figure out which element was clicked. As far as I remember their is a nice and performant and browser-driven way to get elements under the mouse cursor.

Ah, sorry, what I meant to do was attach that event to the parent, so http://jsfiddle.net/hs27btp6/1/ - That way you have one listener and perform the logic.

Also what is interesting, if you test in the JSfiddles, is that the addition of CSS really slows things down a lot on rendering, much more than attaching events etc. So adding 3000 items to the DOM is quick, but the time taken for the browser to also consider the CSS and render that is fairly large. I guess in your tests so far, you've only been adding the p elements without CSS styling?

You could in fact register one listener on something like form and then use the mouse coords to figure out which element was clicked.

==

Ah, sorry, what I meant to do was attach that event to the parent, [...] That way you have one listener and perform the logic.

:wink:

Also what is interesting, if you test in the JSfiddles, is that the addition of CSS really slows things down a lot on rendering, much more than attaching events etc. So adding 3000 items to the DOM is quick, but the time taken for the browser to also consider the CSS and render that is fairly large. I guess in your tests so far, you've only been adding the p elements without CSS styling?

I only add classes to the elements and let the CSS doing its job. I don't know you specific implementation, but:

Never add style-data to the elements directly (only if it is really required, which is very very rare)
Never alter an element after you've attached it to the parent.
Do not build the DOM (here the form stuff) while your target element (e.g. <div id="jsonform">) is attached to the document/main DOM. Instead use a detached target and attach the final assembled result to the main DOM. Otherwise you're just stresstesting your brower's reflow performance. (btw: this is the reason why mathjax performs so badly on bigger pages, esp. compared to KaTeX).
Do use jQuery to parse all that data.  And especially do no concatenate strings just to get them processed by another engine (jQuery) which then parses them and sets the final results to the browser. No offence, but this style is exactly what makes browser apps slow.

I'll do another perf test later. Btw: jsfiddle turns out to be very bad when it comes to this task, because they're including Facebook, Google, Kickstarter?! and other code in their page which heavily interferes with the submitted code.

jsFiddle does load a lot of crap, but I'm performing the same task on the same platform. Just adding one CSS class (in a CSS file) has a big effect on the time taken to paint the element. Bear in mind that each set of input boxes for each author is styled by many classes in the CSS...when you add your p elements, the CSS is likely to be much less complicated. I've never spent much time before checking the performance of all these elements, it's a very informative process!

Using p instead of input cuts my time down to 1.5secs. And surprise: editable does not influence the time that much :open_mouth: BUT: We need to parse the result (because of all the div and br elements that represent newlines in editable elements) to get the final result back. So that might speed up initial render performance but might kill the time we need to calculate the result JSON. 'element.innerText' might be a solution but is said to be slow :disappointed:

Cool :)

Follow https://github.com/inveniosoftware/invenio-records-js

I realize it was only mentioned IRL but never on Github that in INSPIRE we are also working on a Jsonschema editor as we promised in the past. The aim of this editor is to replace BibEdit from Invenio 1, hence cataloguer oriented.
Internal project description is available at: https://docs.google.com/document/d/1y_v4bqACdMCpd8XWwTw8UswX278hSP0Gbj8CVwZhpno/edit?usp=sharing
and prototypes:
https://github.com/inspirehep/record-editor


add constants to ObjectFormat property

Hi @grahampcharles, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;


[C++][Parquet] Fix undefined behavior in encoding.cc when num_dictionary_values is 0.

There is code that potentially references a nullptr.
Reporter: Micah Kornfield / @emkornfield
PRs and other links:

GitHub Pull Request #4336

Note: This issue was originally created as PARQUET-1581. Please see the migration documentation for further details.

Antoine Pitrou / @pitrou:
Issue resolved by pull request 4336
https://github.com/apache/arrow/pull/4336


fix: Fix ES6 TypeScript definition files

Following the type definitions on ./index.d.ts and ./react.d.ts, we need to use declare module on TypeScript definition files.
I've published a proof-of-concept on npm (also because I needed it now) as fast-deep-equal-ts. It will be deprecated once this is released.
Closes #9
Closes #40
Closes #48

Coverage remained the same at 100.0% when pulling 666c2a1532e31ed35523d5c481f46ec54e628f9a on WesSouza:fix-es6-typescript into 32f8e288c2ed5b7f71aa47d5f9b980da5c9951aa on epoberezkin:master.

@epoberezkin ping

Why would this be needed? 🤔
I've never seen another module that uses declare module when the .d.ts file lives next to the source file...

#48 is merged


link to jersey 2.22.1 docs, not 1.18

Since dropwizard has upgraded to jersey 2, the dropwizard-client docs should link to jersey 2 docs.

Thanks!


VendorV3 URL needs quotes in parameters

Hi there! We're using this library and are super thankful for the effort you put in to build it. We're just encountering a small issue when trying to get an entity by its ID, specifically VendorV3. The library creates a URL of /data/VendorsV3(dataAreaId=XXX,VendorAccountNumber=VEN-000001) for example, but gets a 404 error. I found in order to make this work, I have to add single-quotes to the parameters, like so: /data/VendorsV3(dataAreaId='XXX',VendorAccountNumber='VEN-000001').
Any help you could provide would be great. If you'd like a PR, I'm fully willing to work on one, but wanted to check this wasn't already covered first. Thank you!

Glad it's going to be useful. The relevant odata 4 specification will probably mention quote usage. We should check it. I'm away camping for the week so can't sort it out for you right now but a PR welcome.

Feel free to wait till Monday when I'll address this

Thanks @davidmoten! Had some other things come up this week. I'd appreciate it if you can look at it, but no rush!

There's a bit of ambiguity in the standard about this:
with quotes:
http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_AlternateKeys
without quotes:
http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_URLsforRelatedEntitieswithReferentia
This is a bit more enlightening, appears that the presence of quotes is dependent on the type of the value (for example a string is quoted but a date-time is not):
https://docs.oasis-open.org/odata/odata/v4.01/os/abnf/odata-abnf-construction-rules.txt

Thanks very much for reporting this. I've fixed the problem in odata-client 0.1.86. Please give it a spin and any problems reopen this issue or open a new one.


Re-enable hibernate-osgi

Really does 2 things:

re-enables the hibernate-osgi module
disables the hibernate-envers module

@Naros I added you here as a heads up because I ended up completely disabling the hibernate-envers module.  The build "works" but it produces an artifact that simply does not work atm.

Had to removal addditional references to hibernate-envers (hibernate-orm-modules)


Support for scripting languages?

So far it seems that plugin support is limited to compiled binaries. Are there plans to eventually add a scripting language such as lua so that plugins can be written in a more dynamic hackish manner?

no plans to add a scripting language.


chore: solve not necessary anymore porting notes

Solves porting notes claiming

"not necessary anymore"
"not used anymore"

by simply deleting them.

bors r+