Latest pika not supported

I have pika 0.9.3 installed. If I set transport="pika" I get the following error :
Traceback (most recent call last):
File "dumper.py", line 18, in
connection.connect()
File "/usr/local/lib/python2.6/dist-packages/kombu-1.0.3-py2.6.egg/kombu/connection.py", line 95, in connect
return self.connection
File "/usr/local/lib/python2.6/dist-packages/kombu-1.0.3-py2.6.egg/kombu/connection.py", line 396, in connection
self._connection = self._establish_connection()
File "/usr/local/lib/python2.6/dist-packages/kombu-1.0.3-py2.6.egg/kombu/connection.py", line 364, in _establish_connection
return self.transport.establish_connection()
File "/usr/local/lib/python2.6/dist-packages/kombu-1.0.3-py2.6.egg/kombu/connection.py", line 408, in transport
self._transport = self.create_transport()
File "/usr/local/lib/python2.6/dist-packages/kombu-1.0.3-py2.6.egg/kombu/connection.py", line 218, in create_transport
return self.get_transport_cls()(client=self)
File "/usr/local/lib/python2.6/dist-packages/kombu-1.0.3-py2.6.egg/kombu/connection.py", line 225, in get_transport_cls
transport_cls = get_transport_cls(transport_cls)
File "/usr/local/lib/python2.6/dist-packages/kombu-1.0.3-py2.6.egg/kombu/transport/init.py", line 125, in get_transport_cls
_transport_cache[transport] = _get_transport_cls(transport)
File "/usr/local/lib/python2.6/dist-packages/kombu-1.0.3-py2.6.egg/kombu/transport/init.py", line 107, in _get_transport_cls
import(transport_module_name)
File "/usr/local/lib/python2.6/dist-packages/kombu-1.0.3-py2.6.egg/kombu/transport/pypika.py", line 13, in
from pika import asyncore_adapter
ImportError: cannot import name asyncore_adapter

Did something change about that? PyPi shows kombu 2.0 supports pika sync and async. Looked in sources, and pika.py is for 0.5.2 but pika2 is for new pika. Yet, pika wont run.
Using pika 0.9.5 from pip.
WARNING 2012-01-23 06:47:15,066 celery: File "/opt/local/srv/python-environments/hydra/lib/python2.7/site-packages/kombu/transport/pika2.py", line 175, in Transport
WARNING 2012-01-23 06:47:15,066 celery: exceptions.AuthenticationError,
WARNING 2012-01-23 06:47:15,066 celery: AttributeError
WARNING 2012-01-23 06:47:15,066 celery: :
WARNING 2012-01-23 06:47:15,066 celery: 'module' object has no attribute 'AuthenticationError'
Tried pika from github, different error. So which is it? Supported or now? And which version if so?

@23doors: That error went away with using the github version of pika (or 0.9.6 pre-release, I guess), but BlockingConnection in seemed to be broken (not yet updated to match other changes in pika).
Any news on kombu and its pika2-backend?

@datakurre is right, it seems they have changed this from one point release to another.
4c895c9a228b6288529ac281265114c62ee6e490 should fix that.
Though, the pika2 transport is still experimental, for one it introduces long delays between consuming messages
for me.  I simply don't have the time to work on a pika backend.

Building 2.1.0 with pika 0.9.5 installed shows this message:
/tmp/buildd/kombu-2.1.0/docs/reference/kombu.transport.pika.rst:7: WARNING: autodoc can't import/find module 'kombu.transport.pika', it reported error: "Kombu only works with pika version 0.5.2", please check your spelling and sys.path
Is this intended as the changelog says it should work with pika 0.9.5?

@fladi,
There are now two pika transports:
 {"pika": "kombu.transport.pika2.Transport",
  "oldpika": "kombu.transport.pika.Transport"}

The pika transport works with 0.9.5/0.9.6dev, and the oldpika transport works with 0.5.
However, the old transport module checks the version at import time, so it will raise if imported
with the old pika version, and this is happening when Sphinx is trying to generate the API reference
docs for it.


Issue with method 'referentiel(self, referentiel)' in 'offres_emploi/api.py'

Hi, there is an issue when runing 'offres_emploi/api.py' method referentiel(self, referentiel)
--> 165         print('Making request with params {}'.format(params))
NameError: name 'params' is not defined
You could comment/remove/fix the line.
Regards

fixed in #2


furnace: 0.6pre18 -> 0.6

Description of changes
Closes: #259093

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 259128 run on x86_64-linux 1

1 package built:

furnace


[BEAM-13517] Unable to write nulls to columns with logical types

Try to write null to the column with type varchar(255) via JdbcIO.write(). The result is NPE.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

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

R: @pabloem @jbonofre @timrobertson100

retest this please

Thanks @vitaly-ivanov for reporting and fixing. LGTM


Rfnew

Fixes Issue🛠
Closes #41
Description👨💻
Added RandomForest Model with RandomizedSearchCV.
Type of change📄
Instead of using filenames to read the dataset. I used URLs from GitHub to read in the dataset. This helped me avoid some of these errors: https://stackoverflow.com/questions/76313685/python-pandas-dataframe-keyerror-date and https://stackoverflow.com/questions/76314345/typeerror-input-has-int-str-as-feature-name-column-name-types
I have added the RandomForest Model to the existing list of models.
How this has been tested✅
Yes, this has been tested. I have run the code in Google Colab and on my local machine.
Checklist✅

[] My code follows the style guidelines of this project
[] I have performed a self-review of my own code
[] I have commented my code, particularly in hard-to-understand areas
[] I have added demonstration in the form of GIF/video file
[] I am an Open Source Contributor

Screenshots/GIF📷

@Rakesh9100 can you please check this once?

First of all, pls change and mention a clear PR title.
Don't include the url for file as if we run on local, then it can't be accessed without internet. I and many others already have worked and there is no issue with the files.
Work on these @karthikbhandary2

ok @Rakesh9100


Neo4jrb Logging mechanism for Ruby

As a neo4jrb ruby user
I would like to be able to see what REST API queries are being generated by neo4jrb
So that I can debug building of objects in the system
Can a native ruby logging mechanism be created for seeing the REST queries generated by neo4jrb.
I'm using Sinatra (Padrino) to build an API for my neo4j data model. I would like to see what REST queries are being generated by neo4jrb object queries.
I'm new to neo4jrb and I know the neo4j queries for the data. I'm trying to learn how to use the object function and it would be good to see the resulting queries to understand how to use the functionality to make the code more readable.

Brian's recent work with logging should cover this.

It's true!  For anybody reading you can set the logger configuration to define a custom logger (in Rails this gets set to Rails.logger).  You can also set pretty_logged_cypher_queries = true to have it output the cypher in a nice way (assuming it was generated by query/association chaining methods).  See the configuration documentation for more info on how to set configuration variables:
http://neo4jrb.readthedocs.org/en/5.2.x/Configuration.html

Oh, and it sends logs at the debug level (which I think is what ActiveRecord does), so set log levels accordingly for your various environments


rbd-mirror: fix multiple rbd-mirror daemon support

This run_once: true breaks multiple rbd-mirror daemons support as it would make all rbd-mirror daemons use the same keyring. Each rbd-mirror daemon needs its own keyring in order to start.
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=2037646
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test centos-non_container-rbdmirror


Create radix_sort implementation in Javascript

Please follow the Contributing Guidelines & naming conventions in the guidelines accordingly. 🙂
Following naming guidelines is important to maintain consistency.😊
Please NOTE: In case, same implementation of an algorithm is submitted by someone else and it gets accepted, then your contribution won't be merged ( to avoid duplicates )

I will be working on it :)


How to turn prune on/off on demand for PRs

When we submit a PR, we since recently set prune to true via a pr specific config. This is super helpful when working on changes to the infrastructure (iterate on a given set of 'well behaved' iids), but is less then ideal when actually testing/debugging datasets.
As an example: The pruned version will result in different dynamic chunking for files that have e.g. very few timesteps.
I think we should have a way to turn prune on/off as needed. But what is the best way to do this? Filter commit messages, something tag based?

I think this is sufficiently nicely handled with our switch of config files (with pruning and other parameters changed for PRs) here


fix(explore): fix y-axis lower bound  0 value

SUMMARY

This pr fixes the viz that cannot be updated when the y-axis lower bound is changed to 0.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before
https://user-images.githubusercontent.com/11830681/121550073-fdd14480-ca40-11eb-95ee-5a160e57d631.mov
After
https://user-images.githubusercontent.com/11830681/121550116-07f34300-ca41-11eb-8d91-20ecad49bdc7.mov
TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[x] Has associated issue:   #14998
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up


error:This linux based install requires apt. To run with other distros (centos, arch, etc), you will need to manually install the requirements on Ubuntu 24.04 LTS (Noble Numbat)

Describe the bug
When I installed bittensor using a Bash command on Ubuntu 24.04 LTS (Noble Numbat),I encountered an error "This linux based install requires apt. To run with other distros (centos, arch, etc), you will need to manually install the requirements"
To Reproduce
1.Copy and paste the following bash command into a terminal:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/opentensor/bittensor/master/scripts/install.sh)"

the script exited and the screen printed "This linux based install requires apt. To run with other distros (centos, arch, etc), you will need to manually install the requirements"

Expected behavior
the script will continue exec on 24.04 LTS (Noble Numbat)
Screenshots

Environment
Ubuntu  24.04 LTS (Noble Numbat)
Additional context
Maybe line 179 in https://raw.githubusercontent.com/opentensor/bittensor/master/scripts/install.sh should be changed from 'if [[ $? == 0 ]] ; then' to 'if [[ $? != 0 ]] ; then'.

This issue has been preview on the Pull Requests. To resolve,
Contact the dAppNode page to initiate a chat with the live agent on the chat button to get more information about your request via dAppNode

Hey @liefh ,
You're welcome to submit a PR for this. Otherwise, you can also install through pip until this issue is resolved.


How to enable drupal console

I'm using last version of docker4drupal with last version of drupal core and I can't install drupal console.
If I execute:
 composer require drupal/console:~1.0 --prefer-dist --optimize-autoloader
It returns this:
  Problem 1
    - drupal/console 1.9.4 requires drupal/console-core 1.9.4 -> satisfiable by drupal/console-core[1.9.4].
    - Conclusion: don't install drupal/console-core 1.9.4
    - drupal/console 1.9.3 requires drupal/console-core 1.9.3 -> satisfiable by drupal/console-core[1.9.3].
    - Conclusion: don't install drupal/console-core 1.9.3
    - drupal/console 1.9.2 requires drupal/console-core 1.9.2 -> satisfiable by drupal/console-core[1.9.2].
    - Conclusion: don't install drupal/console-core 1.9.2
    - drupal/console 1.9.1 requires drupal/console-core 1.9.1 -> satisfiable by drupal/console-core[1.9.1].
    - Conclusion: don't install drupal/console-core 1.9.1
    - drupal/console v1.9.0 requires drupal/console-core 1.9.0 -> satisfiable by drupal/console-core[v1.9.0].
    - Conclusion: don't install drupal/console-core v1.9.0
    - drupal/console 1.8.0 requires drupal/console-core 1.8.0 -> satisfiable by drupal/console-core[1.8.0].
    - Conclusion: don't install drupal/console-core 1.8.0
    - drupal/console 1.7.0 requires drupal/console-core 1.7.0 -> satisfiable by drupal/console-core[1.7.0].
    - Conclusion: don't install drupal/console-core 1.7.0
    - drupal/console 1.6.1 requires drupal/console-core 1.6.1 -> satisfiable by drupal/console-core[1.6.1].
    - Conclusion: don't install drupal/console-core 1.6.1
    - drupal/console 1.6.0 requires drupal/console-core 1.6.0 -> satisfiable by drupal/console-core[1.6.0].
    - Conclusion: don't install drupal/console-core 1.6.0
    - drupal/console 1.5.0 requires drupal/console-core 1.5.0 -> satisfiable by drupal/console-core[1.5.0].
    - Conclusion: don't install drupal/console-core 1.5.0
    - drupal/console 1.4.0 requires drupal/console-core 1.4.0 -> satisfiable by drupal/console-core[1.4.0].
    - Conclusion: don't install drupal/console-core 1.4.0
    - drupal/console 1.3.2 requires drupal/console-core 1.3.2 -> satisfiable by drupal/console-core[1.3.2].
    - Conclusion: don't install drupal/console-core 1.3.2
    - drupal/console 1.3.1 requires drupal/console-core 1.3.1 -> satisfiable by drupal/console-core[1.3.1].
    - Conclusion: don't install drupal/console-core 1.3.1
    - drupal/console 1.3.0 requires drupal/console-core 1.3.0 -> satisfiable by drupal/console-core[1.3.0].
    - Conclusion: don't install drupal/console-core 1.3.0
    - drupal/console 1.2.0 requires drupal/console-core 1.2.0 -> satisfiable by drupal/console-core[1.2.0].
    - Conclusion: don't install drupal/console-core 1.2.0
    - drupal/console 1.1.1 requires drupal/console-core 1.1.1 -> satisfiable by drupal/console-core[1.1.1].
    - Conclusion: don't install drupal/console-core 1.1.1
    - drupal/console 1.1.0 requires drupal/console-core 1.1.0 -> satisfiable by drupal/console-core[1.1.0].
    - Conclusion: don't install drupal/console-core 1.1.0
    - drupal/console 1.0.2 requires drupal/console-core 1.0.2 -> satisfiable by drupal/console-core[1.0.2].
    - Conclusion: don't install drupal/console-core 1.0.2
    - drupal/console 1.0.1 requires drupal/console-core 1.0.1 -> satisfiable by drupal/console-core[1.0.1].
    - Conclusion: don't install drupal/console-core 1.0.1
    - drupal/console 1.0.0 requires drupal/console-core 1.0.0 -> satisfiable by drupal/console-core[1.0.0].
    - drupal/console 1.0.0-rc20 requires drupal/console-core 1.0.0-rc20 -> satisfiable by drupal/console-core[1.0.0-rc20].
    - drupal/console 1.0.0-rc21 requires drupal/console-core 1.0.0-rc21 -> satisfiable by drupal/console-core[1.0.0-rc21].
    - drupal/console 1.0.0-rc22 requires drupal/console-core 1.0.0-rc22 -> satisfiable by drupal/console-core[1.0.0-rc22].
    - drupal/console 1.0.0-rc23 requires drupal/console-core 1.0.0-rc23 -> satisfiable by drupal/console-core[1.0.0-rc23].
    - drupal/console 1.0.0-rc24 requires drupal/console-core 1.0.0-rc24 -> satisfiable by drupal/console-core[1.0.0-rc24].
    - drupal/console 1.0.0-rc25 requires drupal/console-core 1.0.0-rc25 -> satisfiable by drupal/console-core[1.0.0-rc25].
    - drupal/console 1.0.0-rc26 requires drupal/console-core 1.0.0-rc26 -> satisfiable by drupal/console-core[1.0.0-rc26].
    - drupal/console-core 1.0.0 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0].
    - drupal/console-core 1.0.0-rc20 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0].
    - drupal/console-core 1.0.0-rc21 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0].
    - drupal/console-core 1.0.0-rc22 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0].
    - drupal/console-core 1.0.0-rc23 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0].
    - drupal/console-core 1.0.0-rc24 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0].
    - drupal/console-core 1.0.0-rc25 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0].
    - drupal/console-core 1.0.0-rc26 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0].
    - Conclusion: don't install webflo/drupal-finder 0.3.0
    - Conclusion: don't install drupal/console 1.0.0-rc19
    - Conclusion: don't install drupal/console 1.0.0-rc18
    - Conclusion: don't install drupal/console 1.0.0-rc17
    - drupal/console 1.0.0-rc15 requires doctrine/collections 1.3.0 -> satisfiable by doctrine/collections[v1.3.0].
    - drupal/console 1.0.0-rc16 requires doctrine/collections 1.3.0 -> satisfiable by doctrine/collections[v1.3.0].
    - Conclusion: don't install doctrine/collections v1.3.0
    - drupal/console 1.0.0-rc13 requires psy/psysh 0.6|0.8 -> satisfiable by psy/psysh[v0.6.0, v0.8.0].
    - psy/psysh v0.6.0 requires dnoegel/php-xdg-base-dir 0.1 -> satisfiable by dnoegel/php-xdg-base-dir[0.1].
    - psy/psysh v0.8.0 requires dnoegel/php-xdg-base-dir 0.1 -> satisfiable by dnoegel/php-xdg-base-dir[0.1].
    - Conclusion: don't install drupal/console 1.0.0-rc14|install dnoegel/php-xdg-base-dir 0.1
    - Conclusion: don't install dnoegel/php-xdg-base-dir 0.1
    - Conclusion: don't install drupal/console 1.0.0-rc12
    - Conclusion: don't install drupal/console 1.0.0-rc11
    - Conclusion: don't install drupal/console 1.0.0-rc10
    - Conclusion: don't install drupal/console 1.0.0-rc9
    - Conclusion: don't install drupal/console 1.0.0-rc8
    - Conclusion: don't install drupal/console 1.0.0-rc7
    - Conclusion: don't install drupal/console 1.0.0-rc6
    - Conclusion: don't install drupal/console 1.0.0-rc5
    - Conclusion: don't install drupal/console 1.0.0-rc4
    - Conclusion: don't install drupal/console 1.0.0-rc3
    - Conclusion: don't install drupal/console 1.0.0-rc2
    - Conclusion: don't install drupal/console 1.0.0-rc1
    - Conclusion: don't install drupal/console 1.0.0-beta5
    - Conclusion: don't install drupal/console 1.0.0-beta4
    - Conclusion: don't install drupal/console 1.0.0-beta3
    - Conclusion: don't install drupal/console 1.0.0-beta2
    - Conclusion: don't install drupal/console 1.0.0-beta1
    - Conclusion: don't install drupal/console 1.0.0-alpha2
    - Conclusion: remove symfony/console v3.4.35
    - Installation request for symfony/filesystem (locked at v4.4.5) -> satisfiable by symfony/filesystem[v4.4.5].
    - Installation request for webflo/drupal-finder (locked at 1.2.0) -> satisfiable by webflo/drupal-finder[1.2.0].
    - Installation request for doctrine/collections (locked at v1.4.0) -> satisfiable by doctrine/collections[v1.4.0].
    - Installation request for dnoegel/php-xdg-base-dir (locked at v0.1.1) -> satisfiable by dnoegel/php-xdg-base-dir[v0.1.1].
    - Installation request for doctrine/annotations (locked at v1.4.0) -> satisfiable by doctrine/annotations[v1.4.0].
    - Installation request for drupal/console ~1.0 -> satisfiable by drupal/console[1.0.0, 1.0.0-alpha1, 1.0.0-alpha2, 1.0.0-beta1, 1.0.0-beta2, 1.0.0-beta3, 1.0.0-beta4, 1.0.0-beta5, 1.0.0-rc1, 1.0.0-rc10, 1.0.0-rc11, 1.0.0-rc12, 1.0.0-rc13, 1.0.0-rc14, 1.0.0-rc15, 1.0.0-rc16, 1.0.0-rc17, 1.0.0-rc18, 1.0.0-rc19, 1.0.0-rc2, 1.0.0-rc20, 1.0.0-rc21, 1.0.0-rc22, 1.0.0-rc23, 1.0.0-rc24, 1.0.0-rc25, 1.0.0-rc26, 1.0.0-rc3, 1.0.0-rc4, 1.0.0-rc5, 1.0.0-rc6, 1.0.0-rc7, 1.0.0-rc8, 1.0.0-rc9, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 1.4.0, 1.5.0, 1.6.0, 1.6.1, 1.7.0, 1.8.0, 1.9.1, 1.9.2, 1.9.3, 1.9.4, v1.9.0].
    - Conclusion: don't install symfony/console v3.4.35
    - drupal/console 1.0.0-alpha1 requires symfony/dependency-injection ~2.8 -> satisfiable by symfony/dependency-injection[2.8.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.47, v2.8.48, v2.8.49, v2.8.5, v2.8.50, v2.8.52, v2.8.6, v2.8.7, v2.8.8, v2.8.9].
    - symfony/dependency-injection 2.8.x-dev conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.0 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.0-BETA1 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.1 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.10 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.11 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.12 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.13 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.14 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.15 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.16 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.17 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.18 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.19 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.2 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.20 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.21 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.22 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.23 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.24 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.25 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.26 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.27 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.28 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.29 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.3 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.30 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.31 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.32 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.33 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.34 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.35 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.36 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.37 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.38 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.39 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.4 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.40 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.41 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.42 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.43 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.44 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.45 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.46 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.47 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.48 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.49 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.5 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.50 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.52 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.6 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.7 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.8 conflicts with symfony/console[v3.4.35].
    - symfony/dependency-injection v2.8.9 conflicts with symfony/console[v3.4.35].
    - Installation request for symfony/console (locked at v3.4.35) -> satisfiable by symfony/console[v3.4.35].

What's wrong? I don't understand if it's a drupal issue or a docker4drupal issue.
Thanks,
Sergio

Closing as it's not a docker4drupal bug, just a conflict in your dependencies as you can see it. You should normally have console already installed with Drupal if you're using something like https://github.com/drupal-composer/drupal-project

You're probably using recommended-project. According to official docs:

Note that Drupal Console currently conflicts with Drupal 9 dependencies. Follow [console] Make Drupal Console work with Symfony 4 · Issue #4220 · hechoendrupal/drupal-console. If it gets fixed, make sure to install it prior to installing Drush with:

ref https://github.com/hechoendrupal/drupal-console/issues/4220


String>>indexOfSubCollection:startingAt: works with negative starting at in Squeak, but not RSqueak

Squeak uses a primitive that seems to deal with negative start, but we run the fallback code, which doesn't. Should provide a trunk patch.

:+1:

Trunk patch committed..


Uglify issue

I'm still trying to track down the exact problem, but I'm running node 4.4.6 and I just tried to uglify your package and got an error. I think it was having issues parsing 'let', so I think I need to upgrade my node to 5 in order to actually uglify your code. Will it be a requirement to use node 5 in order to use your lib? if so, it should be indicated somewhere.

let is supported in Node v4. Also, we run v4 in our CI (see .travis.yml). Sounds like an uglify issue.

FYI, you were right. Needed to use uglify on the harmony branch.


How to turn off the scroll effect

Hi, do you know how to turn off the scroll effect but the card is still clickable and has zoom in/out effect? I appreciate for the pointer

Hi, @ianeinser. There are DefaultViewUpdater, CardSnapHelper and CardSliderLayoutManager classes which you need to modify to achieve any behavior you need. Play around with various properties in those classes.


Add environment variable

Add $ZPLUG_BIN.

You may want to describe your change in the readme as well: https://github.com/zplug/zplug#4-environment-variables-for-zplug

What does this change bring? Why is it necessary?

I already did rebase, but did you have any inadequacies?

Looks like he wants one commit from you ("add $ZPLUG_BIN variable"), not 4.

Apparently I seem to have misunderstood.
@Defman21 : Thank you


Occasionally fail to move to pokestops when using high walking speeds

Expected Behavior
Successfully arrive at pokestop and spin it
Actual Behavior
[09:26:55] Moving towards fort Key Guitar, 95.28m left
[09:26:55] Arrived at pokestop.
[09:26:55] Walking from (35.656926, 139.70108) to [35.659556, 139.700818] 293.40m
[09:27:15] Moving towards fort Key Guitar, 97.65m left
[09:27:15] Arrived at pokestop.
[09:27:38] Moving towards fort Key Guitar, 97.19m left
[09:27:38] Arrived at pokestop.
[09:27:58] Moving towards fort Key Guitar, 97.28m left
[09:27:58] Arrived at pokestop.
[09:28:20] Moving towards fort Key Guitar, 96.32m left
[09:28:20] Arrived at pokestop.
[09:28:41] Moving towards fort Key Guitar, 97.05m left
[09:28:41] Arrived at pokestop.
[09:29:09] Moving towards fort Key Guitar, 99.03m left
[09:29:09] Arrived at pokestop.
[09:29:33] Moving towards fort Key Guitar, 97.54m left
[09:29:33] Arrived at pokestop.

Steps to Reproduce
Set in config position 35.657756,139.700818 and walk 80 and wait for a while.
Other Information
OS: OSX 10.11.6
Git Commit: 5927c3b8a900ff79ce72fb8447c6c75dbb8ea858
Python Version: 2.7.6

20 seconds to walk less than 2 meters isn't exactly what I would call high walk speeds :P
Perhaps reset walk back to 4.16 ?
Although, it would seem the walk config value is a bit buggy then

Remove the FollowSpiral from your config.

@xorinzor I only pasted the part where the bot is acting up. Walk speed is set at 80. I guess 80 in the config means 80 km/h? Looks like when the bot is at certain distances from a pokestop (~95m in this case) thinks he's arrived, but fails to spin it.

@Pimentoso So it moved faster in the rest of the log?
Then try removing (if they exist in your config) the FollowSpiral and FollowPath tasks and restart your bot

If the step is bigger than the distance from the pokestop, obviously the bot walks past it, turns around, tries to walk towards it again, repeat.

put ur speed lower or remove spiral.

@ironbishop that's what I suspected, but I think the correct behavior would be to reduce the speed for the final step to reach the pokestop. Removing spiral does not help.


Automatically generating static rendering data from replica

❓ Questions and Help
Hi,
Thank you for the amazing work on this repository!
I want to generate static data from the replica, more specifically: camera intrinsics & extrinsics, RGB image, depth image, instance segmentation and bounding box. The only constraint it is that : The images should represent something useful - without being heavily occluded, and it should adequately capture the data for multiview training.
I could write a script through which I can manually navigate and capture data using keyboard and actions provided by the agent. I was wondering if there is a way to do that automatically so that it can be used even for bigger datasets like matterplot3D. Any insights will be highly appreciated.
Thank You
Ayush

See examples/instance_segmentation


Implements the photo registry use-case where users can be able to create photos, tag them and do various other activities with those saved photos that are usually associated with sites/devices.
WHAT JIRA STORY/TASK IS RELATED TO THIS PR?

Check out the read me and perform tasks in the development environment
WHICH ENDPOINTS SHOULD BE READY FOR TESTING?:

[ ] Create a photo
[ ] Update a photo
[ ] Delete a photo
[ ] View Photos

IS THERE ANY JENKINS CONSOLE LINK FOR CODE COVERAGE AND BUILD INFO?
N/A
ARE THERE ANY RELATED PRs?
N/A

Work on this has been migrated to another PR-600.
So I am closing this one.


NaN result for simple inputs

Specifying a single founder, doing a series a and then exiting, I get NaN as the result:
https://www.fundingsimulator.com/?data=BzUba%2Bf%3BFoo+Corp%3BJohn%2C100%3Bp%2CSeries+A%2C10000000%2C50000000%2C10%2C1%2C%3B100000000%2C20

Thanks for the issue.
Can you tell me how you were able to change the solo founder name (You) to (John) ?
The NaN issue is because we look for the equity of ["You"]

If I start editing the percentage for "You", I can use Shift+Tab to move backwards to the name field and change "You" to something else.
I only now realize that perhaps that wasn't intended :D

oh, that's clever. I'll fix that, thanks!


VueJS doesn't work through preview (out of the box)

Tell us about the problem
"Oops, something went wrong..." when trying to tns preview VueJS template
This does not happen with Angular, this only happens when using the VueJS.
To note, I have no changed the code or modifed it in anyway, I followed the steps on the quick guide.
The main error that stands out to me is Error: Could not find module './components/Home' I have checked and this does exist in the correct location. And again, this is straight out of the box followed by the guide.
Did you try it outside of {N} Playground?

No

Which browser are you using?

Chrome

Are there any errors/warnings logged in your browser console?
Yes
Which platform(s) does your issue occur on?

iOS

Are there any entries logged in the Device Logs tab?
Please provide the following information shown in devices tab in the playground:

Model
OS version - MacOS 10.14.3 (18D109)
Preview app version - latest
Runtime version

Please tell us how to recreate the issue with as much detail as possible.

Follow the quick setup guide: https://docs.nativescript.org/start/cli-basics
Use tns create my-app-name --template tns-template-blank-vue
tns preview (take the QR code) launch preview app
See Error

2019-03-26 00:34:52.484 nsplaydev[13557:6264938] *** Terminating app due to uncaught exception 'NativeScript encountered a fatal error: Error: Could not find module './components/Home'. Computed path '/var/mobile/Containers/Data/Application/137C79D0-B9EB-409C-A5FA-EAC154446A08/Documents/Playground/LiveSync/app/components/Home'.
 at
1   resolveSync@[native code]
2   @[native code]
3   promiseReactionJob@[native code]
', reason: '(null)'
*** First throw call stack:
(0x232581ea4 0x231751a50 0x1009e77b4 0x100a23c20 0x1007f73c8 0x10025f3f0 0x231fcabb4)
libc++abi.dylib: terminating with uncaught exception of type NSException
2019-03-26 00:34:52.484 nsplaydev[13557:6264938] PlayLiveSync: Uncaught Exception

Start sending initial files for platform ios.
Successfully sent initial files for platform ios.
LOG from device tmarois.com: 2019-03-26 00:34:56.179 nsplaydev[13559:6264981] ***** Fatal JavaScript exception - application has been terminated. *****
2019-03-26 00:34:56.179 nsplaydev[13559:6264981] Native stack trace:
1   0x10365f370 NativeScript::reportFatalErrorBeforeShutdown(JSC::ExecState*, JSC::Exception*, bool)
2   0x10369bc20 -[TNSRuntime executeModule:referredBy:]
3   0x1033473c8 -[UIApplication(PlayLiveSync) swizzled_executeModule:]
4   0x102daf3f0
5   0x231fcabb4 <redacted>
2019-03-26 00:34:56.180 nsplaydev[13559:6264981] JavaScript stack trace:
2019-03-26 00:34:56.180 nsplaydev[13559:6264981] 1   resolveSync@[native code]
2   @[native code]
3   promiseReactionJob@[native code]
2019-03-26 00:34:56.180 nsplaydev[13559:6264981] JavaScript error:
[native code]: JS ERROR Error: Could not find module './components/Home'. Computed path '/var/mobile/Containers/Data/Application/137C79D0-B9EB-409C-A5FA-EAC154446A08/Documents/Playground/LiveSync/app/components/Home'.
2019-03-26 00:34:56.181 nsplaydev[13559:6264981] PlayLiveSync: Uncaught Exception
2019-03-26 00:34:56.181 nsplaydev[13559:6264981] *** JavaScript call stack:
(

)
2019-03-26 00:34:56.181 nsplaydev[13559:6264981] *** Terminating app due to uncaught exception 'NativeScript encountered a fatal error: Error: Could not find module './components/Home'. Computed path '/var/mobile/Containers/Data/Application/137C79D0-B9EB-409C-A5FA-EAC154446A08/Documents/Playground/LiveSync/app/components/Home'.
 at
1   resolveSync@[native code]
2   @[native code]
3   promiseReactionJob@[native code]
', reason: '(null)'
*** First throw call stack:
(0x232581ea4 0x231751a50 0x10365f7b4 0x10369bc20 0x1033473c8 0x102daf3f0 0x231fcabb4)
libc++abi.dylib: terminating with uncaught exception of type NSException
2019-03-26 00:34:56.181 nsplaydev[13559:6264981] PlayLiveSync: Uncaught Exception

You are missing the --bundle flag. The runtime does not understand .vue files, so that's where the error comes from. If you run tns preview --bundle it should work out of the box.

I think that @rigor789 have explained what went wrong. Hope it helps.


fix vesting event doc

https://github.com/open-web3-stack/open-runtime-module-library/blob/443ee91bc2ca5f1fc155c0378eef6e89b67e2e97/vesting/src/lib.rs#L170-L176
Needs a rename to expose the correct type name in metadata

closed by #541


gnupg 2.1.4 -> 2.1.5

According to someone on #gnupg, the patch is not necessary anymore in the 2.1 series. Also, the patch does not apply.
@wkennington @shlevy what do you think?

The patch was submitted by someone via ML

@domenkozar so?

Yeah, the patch was rejected upstream, best to just remove it.


Trim 2 1 from travis matrix

Also, this is my attempt to address #101.

OK, I think this is ready to review.  I discovered what was preventing the bundle caching from caching dependencies for the other repos: travis run bundle clean before uploading the archive.  This makes sense -- it prevents the bundled directory from growing with each new version (as old versions would be left behind if bundle clean wasn't run).  However, in our case, it means that gems for the other repos get removed, which means on the next build they will have to be re-installed.
The solution I came up with was to stop using cache: bundler and to specify directories to cache instead.  The build manually runs bundle clean after running the spec suite for a repo (to ensure there aren't stale gems in the bundle).  The use of bundle clean forces us to have separate bundle directories for each repo so I changed that as well.
The builds are passing in each repo so I think it's working, but in looking at the build output it's still installing gems for the non-main repos of a particular build, even when I restart the build (I was hoping to see the bundle caching in affect speed things up on a re-run).  However, I think it has to do with the fact that travis may not update the cache for PR builds, instead only updating it when a PR is merged into master.  So I think this is ready to review and merge and we can always iterate if it doesn't work as we expect.

OK, I think this is ready to review.  I discovered what was preventing the bundle caching from caching dependencies for the other repos: travis run bundle clean before uploading the archive.  This makes sense -- it prevents the bundled directory from growing with each new version (as old versions would be left behind if bundle clean wasn't run).  However, in our case, it means that gems for the other repos get removed, which means on the next build they will have to be re-installed.
The solution I came up with was to stop using cache: bundler and to specify directories to cache instead.  The build manually runs bundle clean after running the spec suite for a repo (to ensure there aren't stale gems in the bundle).  The use of bundle clean forces us to have separate bundle directories for each repo so I changed that as well.
The builds are passing in each repo so I think it's working, but in looking at the build output it's still installing gems for the non-main repos of a particular build, even when I restart the build (I was hoping to see the bundle caching in affect speed things up on a re-run).  However, I think it has to do with the fact that travis may not update the cache for PR builds, instead only updating it when a PR is merged into master.  So I think this is ready to review and merge and we can always iterate if it doesn't work as we expect.

All the PRs in the other repos were green so I merged them with the exception of rspec-rails (leaving that one for @cupakromer).

All the PRs in the other repos were green so I merged them with the exception of rspec-rails (leaving that one for @cupakromer).


Table not rendering correctly in Safari browsers

Is your feature request related to a problem? Please describe.
This was already there but slipped through during release. It increases readability.
Describe the solution you'd like
Use smth like a css selector to choose the state row and :nth-child(odd/even) them.

@jeremyphilemon  Is this issue already resolved ?

@SanjeevYadavcr7 well, there seems to be an error in the way the tables are being rendered in safari at the moment,

Let me know if you'd like to have this assigned to you!

@jeremyphilemon i want to solve this issue.

@jeremyphilemon i want to solve this issue.

This has been solved with #319.

@AnirudhSriram Yep. Also, please follow the Github syntax for linking a PR with an issue: https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword.
This ensures that all the linked issues are automatically closed once the PR is merged. Thanks!

Sorry about that. It’s my first time contributing. I’ll follow the guidelines from now. Thank you for the link :)


Unicode character in name of dimension cause error

Make sure these boxes are checked before submitting your issue - thank you!
Superset version
Superset 0.19.0
Expected results
See a graph with russian names of dimensions
Actual results
Error: 'ascii' codec can't encode characters in position 104-110: ordinal not in range(128)
Steps to reproduce

create a slice with Time series-bar chart visualization, render some metric over time
click on Edit datasource
On Edit Table, click List metrics, select a metric used to display on step 1
rename metric to Unicode name
go back to slice, select a new metric from the list and try to render - got this error

Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/superset/viz.py", line 239, in get_payload
df = self.get_df()
File "/usr/local/lib/python2.7/site-packages/superset/viz.py", line 79, in get_df
self.results = self.datasource.query(query_obj)
File "/usr/local/lib/python2.7/site-packages/superset/connectors/sqla/models.py", line 554, in query
sql = self.get_query_str(query_obj)
File "/usr/local/lib/python2.7/site-packages/superset/connectors/sqla/models.py", line 326, in get_query_str
compile_kwargs={"literal_binds": True}
UnicodeEncodeError: 'ascii' codec can't encode characters in position 104-110: ordinal not in range(128)

Yeah, the str() at line 323 is not going to work fine, does replacing it with unicode() do the trick?

I made this change and got another error: 'latin-1' codec can't encode characters in position 111-117: ordinal not in range(256)
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/superset/connectors/sqla/models.py", line 559, in query
df = self.database.get_df(sql, self.schema)
File "/usr/local/lib/python2.7/site-packages/superset/models/core.py", line 582, in get_df
df = pd.read_sql(sql, eng)
File "/usr/local/lib/python2.7/site-packages/pandas/io/sql.py", line 416, in read_sql
chunksize=chunksize)
File "/usr/local/lib/python2.7/site-packages/pandas/io/sql.py", line 1087, in read_query
result = self.execute(*args)
File "/usr/local/lib/python2.7/site-packages/pandas/io/sql.py", line 978, in execute
return self.connectable.execute(*args, **kwargs)

Yeah, need to add this header at the start of the file:
# -*- coding: utf-8 -*-

BTW please quote properly stacktraces.

which file?

The one you modified earlier.

This did not help - same error.
Also i tested, that this modification str() -> unicode() does not affect the first error ( unicode data in dimension )

Notice: this issue has been closed because it has been inactive for 247 days. Feel free to comment and request for this issue to be reopened.


ValueError: validation_steps=None is only valid for a generator based on the keras.utils.Sequence class. Please specify validation_steps or use the keras.utils.Sequence class.

Loading dataset list from cache...
Found 0 videos for training.
Found 0 videos for validation.
raise ValueError('validation_steps=None is only valid for a'
ValueError: validation_steps=None is only valid for a generator based on the keras.utils.Sequence class. Please specify validation_steps or use the keras.utils.Sequence class
symlink has been created，but it still has error

Hey, have you received "Error loading video:"+path?
If you have, you may have the same problem as I do.
I have something wrong while running "skvideo.io.vreader".
I used "sudo apt-get install ffmpeg" to solve the problem.

Hey, have you received "Error loading video:"+path?
If you have, you may have the same problem as I do.
I have something wrong while running "skvideo.io.vreader".
I used "sudo apt-get install ffmpeg" to solve the problem.

Hey, have you received "Error loading video:"+path?
If you have, you may have the same problem as I do.
I have something wrong while running "skvideo.io.vreader".
I used "sudo apt-get install ffmpeg" to solve the problem.

@graycell666 Hey, I have not received"Error loading video:"+path.
But I may know that my mistake is that I didn't  understand the readme and created the wrong folder.I am using github for the first time.Can you show me how you created the folder based on the readme? thank you very much.

@gzz666 Take the unseen_speakers as an example, after the symlink, my path is:
/LipNet/training/unseen_speakers/datasets/train/s*/*.mpg
/LipNet/training/unseen_speakers/datasets/val/s*/*.mpg
/LipNet/training/unseen_speakers/datasets/align/*.align
I'm also new and I haven't trained yet because of some other problems, but maybe you can try create the folder like this.

我的路径和你的弄得一样。但是还是加载不了video。我想知道你是怎么创建sylink的。是在终端   ln  -s  xx   xx还是直接把数据放到文件夹里的啊？

是在终端使用 ln -s

你也是大学生吗？我这个是做毕业设计的。你也是吗？我就是用的终端弄得，结果就是不出来。崩溃！可以留个QQ或者微信嘛？方便一起讨论学习这个项目。我的QQ是2689226201。😂😂😂


added prefer-empty-constructor rule

PR checklist

[x] New feature, bugfix, or enhancement

[x] Includes tests

[x] Documentation update

Overview of change:
Added a new rule to require constructors that only assign class members with their parameters to be empty instead, as the compiler does that initialisation for you.
Is there anything you'd like reviewers to focus on?
I've had to jump through some hoops to deal with the fact that node.body can be undefined, I would like extra eyes on that bit. Also of course if there are other constructor shapes that wouldn't be covered by this.

CHANGELOG.md entry:
[new-rule] prefer-empty-constructor

There's a separate rule about not allowing parameter properties. Sometimes that's good, sometimes that's bad. It looks like this rule encourages the opposite. How would that rule and this one work when extending from tslint:all?
IMO it would be better to have more configuration on a single rule, choosing between something like the following three options:

Always use constructor parameter properties
Use parameter properties if all parameters become properties
Never use constructor parameter properties


Stack using Array

Implemented Stack using Array

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Description
(Write your answer here.)
Checklist

[ ] I've read the contribution guidelines.
[ ] I've checked the issue list before deciding what to submit.
[ ] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

Already present here


Add release note and change related version

Coverage remained the same at 33.933% when pulling eefa167524e1aeba78266ff8b1be86f179e0d052 on mintao/release-note-pai-1.5.y into 1c290c96ed56c4d888be42cc5d7ab6a5c8966f70 on pai-1.5.y.

Coverage remained the same at 33.933% when pulling eefa167524e1aeba78266ff8b1be86f179e0d052 on mintao/release-note-pai-1.5.y into 1c290c96ed56c4d888be42cc5d7ab6a5c8966f70 on pai-1.5.y.


Added initial history column

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fixes #

Added history column variation

Test URLs:

Original: https://www.sunstar.com/about/history

Before: https://main--sunstar--hlxsites.hlx.page/_drafts/dbute/toc/toc

After: https://history-block--sunstar--hlxsites.hlx.page/_drafts/dbute/toc/toc

[ ]  If you are adding a new block or a variation to an existing block, please fill below:
Block library path: https://--sunstar--hlxsites.hlx.page/tools/sidekick/library.html?plugin=blocks&path=/sidekick/blocks/&index=0

🔸 1 visual difference detected

/ (main vs branch)410141 pixels (ratio 0.08 of all image pixels) are different.

The diff images are attached in the artifact

Seem pretty identical to me on the actual pages


Can't use hyperion

Hi there. Yesterday I have received my led strand and a converter from lightberry.eu.
To deploy hyperion I have followed the instruction here : https://github.com/tvdzwan/hyperion/wiki/Installation-on-OpenELEC for APA102 but my led didn't react when I have tried the test installation command lines.
However Hyperion service is started. Result of 'ps' show the two lines bellow :
332 root       0:00 {hyperiond.sh} /bin/sh /storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.config.json   334 root       0:01 /storage/hyperion/bin/hyperiond /storage/.config/hyperion.config.json
So then I have tried the Hyperion plugin for OpenELEC to create a new configuration file, and here I can't see the rainbow wire. The error I get is :
Unable to open RS232 device (IO Exception (2): No such file or directory, file /home/sascha/hyperion/dependencies/build/serial/src/impl/unix.cc, line 100.) EFFECTENGINE ERROR: Effect directory can not be loaded: /opt/hyperion/effects EFFECTENGINE ERROR: effect Rainbow swirl fast not found terminate called after throwing an instance of 'std::runtime_error'   what():  JSONSERVER ERROR: could not bind to port Aborted
1. I use a RPI2 with OpenElec 6.0.3 as OS.
2. I have APA102 led directly connected to my RPI2
4. You can find my config file here : http://pastebin.com/vStFtFez
The point is, yesterday it has worked some times, but my blue and my red were inverced so I have done something wrong... And I can't figure out what.
I have reinstalled OpenELEC this morning and it's not woking better...

Did you contact lightberry? you paid them...they should help you...!

Hum didn't contact them because I thought it was a software problem maybe ?

Your effets path is wrong, search for openelec path. The wiki needs more information sharing anyway.
@tpmodding
We should consider to publish a "this is working" list

Why are you using adalightapa102 in your config, just usw apa102

This config file come with the hyperion plugin I think. I have make the modification you suggested but it is not working better.
I have modify the hyperion.config.new and now it finds the effect path, but I always end with the following error :
started INFO: Kodi checker created and started terminate called after throwing an instance of 'std::runtime_error'   what():  JSONSERVER ERROR: could not bind to port Aborted
On other forums I have found that it may comes from my gpio connections. Even if it is ok in my opinion I will investigate. I have found that it may come from spi which is not enable but in my config file it is (dtparam=spi=on).
I have a question. Yesterday when I first deployed Hyperion on my RPI2, I didn't know that my leds where APA102 (didn't pay attention to that) and I think i have choosen the command line sh ./install_hyperion.sh WS281X.What is the difference between this command line and the other ?

I have no idea why it throws that port error.
./install_hyperion.sh WS281X won´t add dtparam=spi=on to you config.txt (cause pwm leds don´t need it)
There is no known problem with official OE6.0.3 and hyperion.
Try to start from the beginning with a clean offiicial OE 6.0.3 .img and please don´t use any kodi addon config modificatory.
We don´t provide one so no support for this here, that is the fault of your vendor, if he suggested this. You could write a feedback to their support.

Ok, I'll do that asap and give you a feedback. Anyway, thanks for the help @brindosch

I've done a new installation of OE and ... it's still not working. It's like there is no connection between my led and my RPI, so I'm thinking about an issue with the converter.
The point is, yesterday it has worked some times, but my blue and my red were inverced so I have done You need to change the RGB Byte Order, just try it out
Yeah I know it now, but yesterday I didn't so I have make something else which has destroy it..
I understand that you make no support for the sellers ;) but I was thinking it was coming from Hyperion, otherwise I wouldn't have start an issue here !
I think you can close this one as it seems to be hardware finally


#2435 Restore signal disposition to previous one

Hi everyone! It is my first PR :) Glad to have the opportunity to contribute.

@bnoordhuis The PR fixes an issue https://github.com/libuv/libuv/issues/2435.

There is a comment in one of the libuv test files that NSIG is not available on some of the supported platforms. This should perhaps deal with that case and make sure not to assign to this array outside of that case.

That comment is about https://github.com/libuv/libuv/pull/1642. Easiest workaround is to default to 128. There's no OS with more signals than that.

Using 128 hardcoded sounds good too. Just so long as we aren't using a value that is apparently known to be wrong here 😬

@bnoordhuis @vtjnash I'v pushed updates, now UV__NSIG constant equals to 128 is used instead of NSIG.

@bnoordhuis @vtjnash Is the PR ready to merge?

Merged, thanks!


Change text in lines 25 and 52

For better translation, following the context of the paragraph, the lines 25 and 52 should be changed for this version,

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

There are 6 other PRs ahead of this one.  Once those PRs have been review/merged/closed, we will review this one.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Add 3space

Token Address : 0x8Bc2bCb1b1896291942C36F3Cca3C1afA0Aaa7fd
Token Name: 3SPACE ART
Token Decimals: 18
Token Symbol: PACE
Website: https://3space.art/
Etherscan: https://etherscan.io/token/0x8bc2bcb1b1896291942c36f3cca3c1afa0aaa7fd
Twitter: https://twitter.com/3spaceart

Hey @LeeWangKwang - are you able to reduce SVG image size? Logo like this should be < 20kb where current one is > 100kb

@MRabenda i changed svg file now it's under 20kb


feat: add base url as parameter

Waiting for https://github.com/gagoar/github-app-installation-token/pull/124

Hey @BlackDark I think now we are ready for this!

Hey @BlackDark I think now we are ready for this!

Hey @gagoar rebased PR and should be good to go.
@jnwng feel free to review + merge :)

The steps are failing because the tokens used in this Repo can't be accessed by you. I will cherry pick your commits and recreate the PR in the base repository.

Can you fix the tests ? these should pass in here for you.

Can you fix the tests ? these should pass in here for you @BlackDark

Done was a problem with the mocked input


Refactor tutorials

The goal here is to have an CI for this repo, and also a better organization to keep maintainability
motivation from https://github.com/kornia/kornia/issues/2171
Changes

Added pre-commit

TODO:

[ ] run pre-commit run --all-files - I didn't do it here to be able to review it,
[ ] add the pre-commit.ci/ on the repo

Renames / moves

The notebooks, with the tutorial/code example are now on nbs/ folder
the source folder was renamed to tutorials, here we add/update the sphinx files
Added a data directory for specific cases where we need to have some file

Split the requirements file into

a -dev just for libs necessary to build the documentation
and the other for third libraries used over the tutorials

Add a Makefile to simplify the pages build

make purge - will delete all files generated when building or testing the tutorials
make generate - will copy the tutorials to a subfolder of sphixs (tutorials/_nbs/) -- uses nbconvert
make execute - will execute all notebooks inside tutorials/_nbs/ -- uses nbconvert
make sphixs - will clean and build the HTML pages
make build- will purge, generate and then build the pages
make setup - will pip install the requirements files
make check-deps - will print the version of the important deps

Added a CI

Will generate and then execute the tutorials on different python versions and different OS. Also will check if the pages build is working.

Fix tutorials to work  (that were not working due to the Kornia update, among other reasons)

I just fixed locally on ubuntu -- Probably should have something not working on win or mac

small updates to pages config

setup language
add path of _nbs/ folder to index.rst
added the favicon

[ ] TODO: Add contributing file based on these changes
[ ] TODO: Replace colab links on headers

i will review soon

@johnnv1 is a bit complicated to review without the outputs. Have you verified that the outputs are correct ?

@johnnv1 is a bit complicated to review without the outputs. Have you verified that the outputs are correct ?

hmmm, yes I have checked -- but my idea here with nbstripout on pre-commit is to remove all outputs, in this manner the repo should get lighter (so it will be a little faster to download and setup on kornia CI). But that way we would have no way of checking if the tutorial is correct, so I will try to think of another way to do it...

I think the windows test are failing because can't download successfully the images with the wget on the notebooks

hmmm, yes I have checked -- but my idea here with nbstripout on pre-commit is to remove all outputs,

@johnnv1 if we do so, we have to somehow increase readthedocs limits for running cells. Heavy stuff like LoFTR https://kornia-tutorials.readthedocs.io/en/latest/image_matching.html is actually crashing on readthedocs because of timeout, and if we would strip the outputs, users would not see any final image there.

is actually crashing on readthedocs because of timeout

if we build on CI, deploy to ghpages (just push to the branch), and then in the readthedocs build we just clone that branch... would it work?

or, we keep it, the notebooks with their outputs, and we can disable the execution of the notebooks in the tutorial build
--- a/tutorials/conf.py
+++ b/tutorials/conf.py

+# -- myst_nb options --------------------
+nb_execution_mode = 'off'

and i think, this way we can have the preview on PR's too

i found out the time limit per cell of the myst-sb is 30s as default...
you think this time limit crash -- is from the config of the myst-sb  or it's a limitation from readthedocs?

you think this time limit crash -- is from the config of the myst-sb  or it's a limitation from readthedocs?

I tested it here, seems to be just the myst config:

the page itself: https://johnnv1-kornia-tutorials.readthedocs.io/en/latest/_nbs/image_matching.html
the page from the PR preview: https://johnnv1-kornia-tutorials--1.org.readthedocs.build/en/1/_nbs/data_augmentation_kornia_lightning.html

I replaced wget with a python function to download the data, and also run pre-commit for all files -- probably the easy way to check this is looking here: https://johnnv1-kornia-tutorials.readthedocs.io/en/latest/
It's a clone of this branch deployed to readthedocs just to test

I don't have a windows env, either time to try to fix the bugs in windows, so I just removed windows from the CI and will open an issue if someone wants to fix this later

@edgarriba can you add https://pre-commit.ci here? 😄


Fix wrong inputs/model placement when using a single core

What does this PR do?
It's a recent find that I did not experience before. Previously, when only a single neuron core was used, input tensors were allocated to the same core that the model has been loaded with torch.jit.load. But it seems that now the input tensors are always allocated to nc:0, whereas the model is loaded to a core with lower usage, so we could bump into unexpected situations where they are in different cores...
2024-Oct-25 15:40:20.728276 13974:13974 ERROR  NMGR:dlr_check_tensor_set_on_same_vtpb_v2    Tensor input249 allocated on vnc 0 must be allocated on same vnc as model (1)

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


make test on 32-bit platforms fails because -race isn't valid

I have a script that I use to automate running elvish unit tests on my primary macOS server and several VMs. One of the VMs is a Ubuntu 32-bit distro. After syncing my local elvish repo it runs
env TEST_ENV='' TEST_FLAGS='' ELVISH_TEST_TIME_SCALE=$TEST_SCALE make -e test

That worked fine up until commit 32328bb4 which removed the TEST_ENV and TEST_FLAGS vars from the ./Makefile. I know I can simply change my test runner script to replace the ... make -e test with go test ./.... I'm opening this issue to discuss whether we want make test to continue to be the standard way to run the elvish unit tests on all supported platforms. If not perhaps that makefile target should be removed.

The test target is mainly useful as part of the default target, which does both testing (go test) and installation (go get), so I'd rather not remove it.
There doesn't seem to be a simple way to ask go whether -race is supported, but since there is currently only a handful of platforms where it is (linux/amd64, freebsd/amd64, darwin/amd64 and windows/amd64), I'll hardcode this check in the Makefile. This has the small risk of being out of date when the race detector supports more platforms, but that seems to be the best we can do now.


Can't use RTSP with UDP connection

Error in Web GUI: "server wants to use the UDP transport protocol"
The RTSP client is fixed to TCP connections, see this line:
https://github.com/kerberos-io/agent/blob/3f29d1c46ff1f6557ac883f37b00e50c8bc2db9d/machinery/src/capture/gortsplib.go#L83
I think this line could just be deleted, as the documentation of gortsplib says that it has an automatism to choose the right transport variant (see https://github.com/bluenviron/gortsplib/blob/2c05e2d3ea16ae15d2bbc5846c6d823e3bcaed39/client.go#L228C1-L231C22):
        // transport protocol (UDP, Multicast or TCP).
        // If nil, it is chosen automatically (first UDP, then, if it fails, TCP).
        // It defaults to nil.
        Transport *Transport

I believe we might need an additional header to set/force TCP or UDP, but setting it to auto can give unwanted experiences. Let me know what you think @mvdberge

We'll add a method to choose for UDP, TCP or Auto


Platform: clarify documentation for executable, resolvedExecutable and script.

Clarify the behavior of executable, resolvedExecutable and script, showing the behavior when running on the Dart VM or from a compiled script (.exe). Also fix a word at executable description.

Review CL is https://dart-review.googlesource.com/c/sdk/+/230941

Review CL is https://dart-review.googlesource.com/c/sdk/+/230941

Just checking before commit:
"... name of the self-contained compiled executable ..."
Is it ok, to call it in this way? (not English native here).

Thanks for the contribution @gmpassos