Librespot crashes with "Tried too many access points"

Compatible Device

[X] I'm running Raspotify on a compatible Device

Are you sure?

[X] I'm not trying to run Raspotify on a ARMv6 device

Compatible OS

[X] I'm running Raspotify on a compatible OS

Compatible Configuration

[X] I'm running Raspotify on a compatible Configuration

Latest Version

[X] I'm running the latest version of Raspotify

Are you sure?

[X] I'm not running Raspotify <IP_ADDRESS> on a Pi v1 or Pi Zero

Due Diligence

[X] I have done my due diligence

What happened?
Raspberry Pi 3b+ running Debian Bullseye.  Just upgraded to latest raspotify and now every time I try to connect from my Spotify account, I get the following error and it fails to connect:
ov 18 07:00:26 pandorapi rngd[506]: stats: Lowest ready-buffers level: 2
Nov 18 07:00:26 pandorapi rngd[506]: stats: Entropy starvations: 0
Nov 18 07:00:26 pandorapi rngd[506]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us
Nov 18 07:05:19 pandorapi systemd[1]: Started Session 41 of user pi.
Nov 18 07:07:02 pandorapi librespot[3698]: [2024-11-18T13:07:02Z WARN  librespot_core::session] Try another access point...
Nov 18 07:07:08 pandorapi librespot[3698]: [2024-11-18T13:07:08Z WARN  librespot_core::session] Try another access point...
Nov 18 07:07:14 pandorapi librespot[3698]: [2024-11-18T13:07:14Z WARN  librespot_core::session] Try another access point...
Nov 18 07:07:21 pandorapi librespot[3698]: [2024-11-18T13:07:21Z WARN  librespot_core::session] Try another access point...
Nov 18 07:07:23 pandorapi systemd[1]: Stopping Raspotify (Spotify Connect Client)...
Nov 18 07:07:23 pandorapi systemd[1]: raspotify.service: Succeeded.
Nov 18 07:07:23 pandorapi systemd[1]: Stopped Raspotify (Spotify Connect Client).
Nov 18 07:07:23 pandorapi systemd[1]: Started Raspotify (Spotify Connect Client).
Nov 18 07:08:18 pandorapi librespot[4615]: [2024-11-18T13:08:18Z WARN  librespot_core::session] Try another access point...
Nov 18 07:08:25 pandorapi librespot[4615]: [2024-11-18T13:08:25Z WARN  librespot_core::session] Try another access point...
Nov 18 07:08:31 pandorapi librespot[4615]: [2024-11-18T13:08:31Z WARN  librespot_core::session] Try another access point...
Nov 18 07:08:37 pandorapi librespot[4615]: [2024-11-18T13:08:37Z WARN  librespot_core::session] Try another access point...
Nov 18 07:08:43 pandorapi librespot[4615]: [2024-11-18T13:08:43Z WARN  librespot_core::session] Try another access point...
Nov 18 07:08:50 pandorapi librespot[4615]: [2024-11-18T13:08:50Z ERROR librespot_core::session] Tried too many access points
Nov 18 07:08:50 pandorapi librespot[4615]: [2024-11-18T13:08:50Z ERROR librespot] could not initialize spirc: Deadline expired before operation could complete { timed out }
Nov 18 07:08:50 pandorapi systemd[1]: raspotify.service: Main process exited, code=exited, status=1/FAILURE
Nov 18 07:08:50 pandorapi systemd[1]: raspotify.service: Failed with result 'exit-code'.
Nov 18 07:08:50 pandorapi systemd[1]: raspotify.service: Triggering OnFailure= dependencies.
Nov 18 07:08:50 pandorapi systemd[1]: Starting Raspotify Crash Report Generator...
Nov 18 07:08:51 pandorapi kernel: [112121.571155] pcm512x 1-004d: No SCLK, using BCLK: -2

### Relevant log output and/or the contents of /etc/raspotify/crash_report if any ( sudo journalctl -u raspotify -b and sudo cat /etc/raspotify/crash_report )

```shell
-- System Info --

Linux pandorapi 6.1.21-v7+ #1642 SMP Mon Apr  3 17:20:52 BST 2023 armv7l GNU/Linux
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

-- Logs --

Nov 19 07:46:00 pandorapi librespot[5462]: [2024-11-19T13:46:00Z WARN  librespot_core::session] Try another access point...
Nov 19 07:46:06 pandorapi librespot[5462]: [2024-11-19T13:46:06Z WARN  librespot_core::session] Try another access point...
Nov 19 07:46:13 pandorapi librespot[5462]: [2024-11-19T13:46:13Z WARN  librespot_core::session] Try another access point...
Nov 19 07:46:19 pandorapi librespot[5462]: [2024-11-19T13:46:19Z WARN  librespot_core::session] Try another access point...
Nov 19 07:46:25 pandorapi librespot[5462]: [2024-11-19T13:46:25Z WARN  librespot_core::session] Try another access point...
Nov 19 07:46:31 pandorapi librespot[5462]: [2024-11-19T13:46:31Z ERROR librespot_core::session] Tried too many access points
Nov 19 07:46:31 pandorapi librespot[5462]: [2024-11-19T13:46:31Z ERROR librespot] could not initialize spirc: Deadline expired before operation could complete { timed out }
Nov 19 07:46:31 pandorapi systemd[1]: raspotify.service: Main process exited, code=exited, status=1/FAILURE
Nov 19 07:46:31 pandorapi systemd[1]: raspotify.service: Failed with result 'exit-code'.
Nov 19 07:46:31 pandorapi systemd[1]: raspotify.service: Triggering OnFailure= dependencies.
Nov 19 07:46:31 pandorapi systemd[1]: raspotify.service: Consumed 3.536s CPU time.

-- Config --

LIBRESPOT_QUIET=on
LIBRESPOT_DISABLE_AUDIO_CACHE=on
LIBRESPOT_DISABLE_CREDENTIAL_CACHE=on
LIBRESPOT_ENABLE_VOLUME_NORMALISATION=on

Hi @kblankenship1989
Do you have any Spotify-related host overrides in /etc/hosts?
Also try disabling the LIBRESPOT_DISABLE_[...]_CACHE flags and see if that changes anything?

Hosts file:
<IP_ADDRESS>       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

<IP_ADDRESS>       pandorapi

Config file:
# /etc/raspotify/conf -- Arguments/configuration for librespot

# A non-exhaustive list of librespot options and flags.

# Please see https://github.com/dtcooper/raspotify/wiki &
# https://github.com/librespot-org/librespot/wiki/Options
# for configuration details and a full list of options and flags.

# You can also find a full list with `librespot -h`.

# To avoid name collisions environment variables must be prepended with
# `LIBRESPOT_`, so option/flag `foo-bar` becomes `LIBRESPOT_FOO_BAR`.

# Invalid environment variables will be ignored.

# Raspotify defaults may vary from librespot defaults.
# Commenting out the environment variable will fallback to librespot's default
# unless otherwise noted.

# Flags can be set to either "on" or "off".
# Empty values may cause errors.

# Only log warning and error messages.
LIBRESPOT_QUIET=on

# Automatically play similar songs when your music ends.
# Respects client autoplay setting if commented out. Forces autoplay on or off when active.
# This value is either "on" or "off".
#LIBRESPOT_AUTOPLAY=on

# Disable caching of the audio data.
# Enabling audio data caching can take up a lot of space
# if you don't limit the cache size with LIBRESPOT_CACHE_SIZE_LIMIT.
# It can also wear out your Micro SD card. You have been warned.
# LIBRESPOT_DISABLE_AUDIO_CACHE=on

# Disable caching of credentials.
# Caching of credentials is not necessary so long as
# LIBRESPOT_DISABLE_DISCOVERY is not set.
# LIBRESPOT_DISABLE_CREDENTIAL_CACHE=on

# Play all tracks at approximately the same apparent volume.
LIBRESPOT_ENABLE_VOLUME_NORMALISATION=on

# Enable verbose log output.
#LIBRESPOT_VERBOSE=off

# Disable zeroconf discovery mode.
#LIBRESPOT_DISABLE_DISCOVERY=off

# Options will fallback to their defaults if commented out,
# otherwise they must have a valid value.

# Device name.
# Raspotify defaults to "raspotify (*hostname)".
# Librespot defaults to "Librespot".
#LIBRESPOT_NAME="Librespot"

# Bitrate (kbps) {96|160|320}. Defaults to 160.
#LIBRESPOT_BITRATE="160"

# Output format {F64|F32|S32|S24|S24_3|S16}. Defaults to S16.
#LIBRESPOT_FORMAT="S16"

# Displayed device type. Defaults to speaker.
#LIBRESPOT_DEVICE_TYPE="speaker"

# Limits the size of the cache for audio files.
# It's possible to use suffixes like K, M or G, e.g. 16G for example.
# Highly advised if audio caching isn't disabled. Otherwise the cache
# size is only limited by disk space.
#LIBRESPOT_CACHE_SIZE_LIMIT=""

# Audio backend to use, alsa or pulseaudio. Defaults to alsa.
#LIBRESPOT_BACKEND="alsa"

# Username used to sign in with.
# Credentials are not required if LIBRESPOT_DISABLE_DISCOVERY is not set.
#LIBRESPOT_USERNAME=""

# Password used to sign in with.
#LIBRESPOT_PASSWORD=""

# Audio device to use, use `librespot --device ?` to list options.
# Defaults to the system's default.
#LIBRESPOT_DEVICE="default"

# Initial volume in % from 0 - 100.
# Defaults to 50 For the alsa mixer: the current volume.
#LIBRESPOT_INITIAL_VOLUME="50"

# Volume control scale type {cubic|fixed|linear|log}.
# Defaults to log.
#LIBRESPOT_VOLUME_CTRL="log"

# Range of the volume control (dB) from 0.0 to 100.0.
# Default for softvol: 60.0.
# For the alsa mixer: what the control supports.
#LIBRESPOT_VOLUME_RANGE="60.0"

# Pregain (dB) applied by volume normalisation from -10.0 to 10.0.
# Defaults to 0.0.
#LIBRESPOT_NORMALISATION_PREGAIN="0.0"

# Threshold (dBFS) at which point the dynamic limiter engages
# to prevent clipping from 0.0 to -10.0.
# Defaults to -2.0.
#LIBRESPOT_NORMALISATION_THRESHOLD="-2.0"

# The port the internal server advertises over zeroconf 1 - 65535.
# Ports <= 1024 may require root privileges.
#LIBRESPOT_ZEROCONF_PORT=""

# HTTP proxy to use when connecting.
#LIBRESPOT_PROXY=""

# ### This is NOT a librespot option or flag. ###
# This modifies the behavior of the Raspotify service.
# If you have issues with this option DO NOT file a bug with librespot.
#
# By default librespot "download buffers" tracks, meaning that it downloads
# the tracks to disk and plays them from the disk and then deletes them when
# the track is over. This practice is very common, many other audio frameworks
# and players do the exact same thing as a disk based tmp cache is easy to use
# and very resilient. That being said there may be cases where a user may want
# to minimize disk read/writes.
#
# Commenting this out will cause librespot to use a tmpfs so that provided there
# is enough RAM to hold the track nothing is written to disk but instead to a tmpfs.
# See https://github.com/dtcooper/raspotify/discussions/567
# And https://www.kernel.org/doc/html/latest/filesystems/tmpfs.html
TMPDIR=/tmp

Same error

For the record, I have tried running librespot on its own and confirmed this is an issue there.  I have raised THIS ISSUE with them to address this

until this is resolved for me, is there any way to downgrade raspotify (I cannot figure out how to install an older version if that is even possible, still fairly new to linux)

So here is where I am @kimtore:

Tried all the suggestions above, same results
Tried running librespot directly on my pi, same issue
Tried running librespot on my Linux PC, no issues (narrowed it to my pi), so I closed the issue with librespot as it is not an issue with them (they don't necessarily claim to support Raspberry Pi's to my knowledge)
Tried brand new SD card, brand new install of raspotify following the documentation with the install script and all,  No changes to config file, same issue
Tried on a Pi 4 I have (I have been using a Pi 3b+ for the last 5 yrs now with raspotify), same issue
So not sure what the changes are or how they are causing issues but the changes in librespot appear to be causing issues at least for my raspberry pi's with respect to connecting to access points.

SOLVED!!!!!!!!
For anyone else that runs into this, the root cause was my NetworkManager on my pi was configured to point to <IP_ADDRESS> as a primary DNS on my network, with <IP_ADDRESS> as a backup.  Now why is this an issue, you ask? BECAUSE '<IP_ADDRESS>DOES NOT EXIST ON MY NETWORK!!!!!  Things like pinginggoogle.comwould still resolve, only delayed because it would attempt the.104address first, then fail and finally use the.1address and work, but librespot closes its connection before the pi has a chance to attempt the fallback DNS.  Once I followed [THESE DIRECTIONS](https://www.reddit.com/r/raspberry_pi/comments/18t6joj/dns_on_a_headless_rpi_os_not_resolving/?rdt=56138#:~:text=To%20change%20DNS%20settings%20using,show%20to%20list%20available%20connections.&text=Replace%20%5Bconnection_name%5D%20with%20your%20connection's,your%20desired%20DNS%20server%20address.) to reset my DNS to<IP_ADDRESS>` as primary, it all worked like magic!!!


ModuleNotFoundError: No module named 'dependency_injector' in ch03 project

Hi sir, when I run the application of ch03 project. It shows the error as below:

from dependency_injector.wiring import inject, Provide
ModuleNotFoundError: No module named 'dependency_injector'

Although I have tried to install:

pip install dependency_injector
pip install dependency_injection
and the IDE recognize the package.

I'm using python 3.11.4

please install the module first

hmmmm i think its the version of Python you use...Please follow the Python version in the book

In your book, it refers:

The FastAPI framework is a fast, seamless, and robust Python framework but can only work on Python
versions 3.6 and above.

And it seems that I'm using the appropriate python version which is 3.11.4

Hi,
Yeah but in the book I indicated the versions. The depends on modules and its versions. I always specify the versions so please follow them. Do not worry this year we will release a 2nd edition updating the projects to use Python 11. For now please use 8 or 9
Sent from Yahoo Mail for iPhone
On Wednesday, January 3, 2024, 4:51 PM, phihunng @.***> wrote:
In your book, it refers:
The FastAPI framework is a fast, seamless, and robust Python framework but can only work on Python
versions 3.6 and above.
And it seems that I'm using the appropriate python version which is 3.11.4
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

thank you for your support, I'm really hoping for your release!

Wow. Thank you. Actually it should been started last November but I am not finished with Mastering Flask 3.x. After this book and its codes, I can start with 2nd edition of FastAPI. Thank you again for your support.
Sent from Yahoo Mail for iPhone
On Wednesday, January 3, 2024, 10:14 PM, phihunng @.***> wrote:
thank you for your support, I'm really hoping for your release!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


rhsm_register resource fails on line 26 when activation_key not specified

Cookbook version
1.0.2
Chef-client version
12.21.26
Platform Details
Red Hat Enterprise Linux 7.3
Scenario:
Trying to execute the "rhsm_register" Chef resource by specifying "username" and "password" properties, as opposed to using the "activation_key" property.  Line 26 in libraries/helpers.rb is looking for activation_key and returning an "undefined method empty? for nil:NilClass" error when it is not found.  Activation keys are not required when specifying username/password and therefore the libraries/helpers.rb should not be looking for it when rhsm_regiser is used in conjunction with username/password.
Steps to Reproduce:
Define an rhsm_register resource using username/password without an activation_key.
Expected Result:
Successful registration to Satellite Server
Actual Result:
Cookbook throws NoMethodError: undefined method `empty?' for nil:NilClass

full error here:
Recipe: satellite-client::default
 * rhsm_register[XXX] action register

   ================================================================================
   Error executing action `register` on resource 'rhsm_register[XXX]'
   ================================================================================

   NoMethodError
   -------------
   undefined method `empty?' for nil:NilClass

   Cookbook Trace:
   ---------------
   /var/chef/cache/cookbooks/redhat_subscription_manager/libraries/helpers.rb:26:in `register_command'
   /var/chef/cache/cookbooks/redhat_subscription_manager/libraries/rhsm_register.rb:58:in `block (2 levels) in <class:RhsmRegister>'
   /var/chef/cache/cookbooks/redhat_subscription_manager/libraries/rhsm_register.rb:56:in `block in <class:RhsmRegister>'

   Resource Declaration:
   ---------------------
   # In /var/chef/cache/cookbooks/satellite-client/recipes/default.rb

    38:   rhsm_register node['fqdn'] do
    39:     satellite_host node['satellite-client']['capsule']['capsule_name']
    40:     username 'admin'
    41:     password 'XXX'
    42:     install_katello_agent node['satellite-client']['katello']
    43:     auto_attach true
    44:     action :register
    45:     #activation_key node['satellite-client']['key']
    46:     #organization node['satellite-client']['organization']
    47:     #ignore_failure true
    48:   end
    49: end

   Compiled Resource:
   ------------------
   # Declared in /var/chef/cache/cookbooks/satellite-client/recipes/default.rb:38:in `from_file'

   rhsm_register("XXX") do
     action [:register]
     retries 0
     retry_delay 2
     default_guard_interpreter :default
     declared_type :rhsm_register
     cookbook_name "satellite-client"
     recipe_name "default"
     satellite_host "XXX"
     username "admin"
     password "XXX"
     install_katello_agent false
     auto_attach true
     _name_unused "XXX"
   end

   System Info:
   ------------
   chef_version=12.21.26
   platform=redhat
   platform_version=6.9
   ruby=ruby 2.3.5p376 (2017-09-14 revision 59905) [x86_64-linux]
   program_name=chef-client worker: ppid=15482;start=20:35:42;
   executable=/opt/chef/bin/chef-client


add a note to the README about inspecting table schemas at runtime

Codecov Report

Merging #192 (8975e5d) into main (3955f64) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #192   +/-   ##
=======================================
  Coverage   69.88%   69.88%
=======================================
  Files          44       44
  Lines        2198     2198
=======================================
  Hits         1536     1536
  Misses        427      427
  Partials      235      235

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 3955f64...8975e5d. Read the comment docs.


Update dialog and add example

Clean up event handling and prevent context menus.   Add example using a util function and the dialog.

Looks good to me.

Thanks, merging.


348 migrate to dart sass

Trello
This work makes the necessary changes to migrate Publisher to use Dart Sass. It follows the instructions in Migrate to Dart Sass from LibSass.
It is close to the changes made in PR2250 (Switch from sassc-rails to dartsass-rails) with a couple of slight changes that seem to fix the issues encountered there, specifically bringing the legacy styles into the SASS Builds folder via the initialiser that is created as part of the work.

Kevin has commented on the govuk-docker PR on a better way of running the app, but that will involve some changes to this PR as well. I'm going to see if I can get that working locally.

I have updated Procfile.dev in line with Kevin's suggestions in the Docker PR770. That seems to run fine locally.

We're also going to need to make some similar fixes as were made to Content Tagger to resolve issues with some icons not appearing/appearing corrupted.

Ah right, good spot. This seems to be fixed by referencing the Glyphicons font in the legacy-application sass file.

We're also going to need to make some similar fixes as were made to Content Tagger to resolve issues with some icons not appearing/appearing corrupted.

Hello @mtaylorgds - this has been addressed but needs to be marked as such before I am able to merge. Could you have a quick look? Cheers 🙂


Added my name Ayoola Paul

Learning how to contribute to open source from live class

Hi Paul!
Your PR is about to be merged and you will be able to see your name on this url.
To enable me to do this, READ the README again carefully, update your code with the latest and push the update. I am here for you for the next 6 hours before I close the PR so you can initiate a fresh PR which will be easier to merge.

Thank you for your feedback.  I get to that now

How do i update my local.  I already did git pull but nothing changed

It says my branch is up to date with the origin

I'm not sure. I recommend that you update the fork here on github, then make a fresh clone on your local computer, then follow the instas per the Readme.
We recommend that you work on a branch that is different from the main branch.

I already created a branch and send a new pull request Can you please confirm that

The branch you have here is named main.
Refer to the guide in the README.md file on this repository


Add .vscode to .gitignore

We can discuss about it but I would suggest to add .vscode to .gitignore since it contains some configuration and user settings.

In every merge with the master, actions create a new version in publications. So I add this useful change to my own branch.


make false act like false in more endpoints

the last pull request didn't catch all the endpoints with broken T/F parameters
/admin/saveRemote (benchling & ice)
/admin/theme
/admin/newUser
/admin/updateUser
/admin/users
/admin/explorer

will be tested with sbh3


Set longer timeout for test cases

Set longer timeout to prevent some test failures on some slower operating systems.
Additionally change .gitignore

Thanks!


Focus indicator will jump of the ticket creation dialog after several tab key pressing

After several tab keys your focus will be lost form dialog ....

Cannot reproduce!

Working now! Cannot reproduce!
Client version:	v1.2.68
API version:	v0.4.26
IMG version:	v0.1.9


WIP: #165 UserIDを伝播する

@Shitomo
UserIDをサーバー間で伝播するように実装しました。

Codecov Report
Patch coverage: 63.63% and project coverage change: -0.08 :warning:

Comparison is base (40d80d0) 86.00% compared to head (f560455) 85.92%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #166      +/-   ##
==========================================
- Coverage   86.00%   85.92%   -0.08%
==========================================
  Files          61       61
  Lines        2072     2082      +10
==========================================
+ Hits         1782     1789       +7
- Misses        237      239       +2
- Partials       53       54       +1

Impacted Files
Coverage Δ

internal/adapter/handler/handler.go
76.62% <0.00%> (ø)

internal/domain/model/user.go
83.33% <70.00%> (-16.67%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


New checker type: ProjectChecker

Robocop currently supports two type of checkers : VisitorChecker and RawFileChecker. We can add third type, based on the VisitorChecker: ProjectChecker. It will allow to check issues in the whole project. For example file structure or duplicated keyword names.
The only difference from VisitorChecker is that it will have special method (for example "run_checks") that will be executed after visiting all the files.
We should be able to disable ProjectCheckers if we are not running Robocop on the directory but on the file(s).
It should support both internal and external rules.

POC implemented in https://github.com/MarketSquare/robotframework-robocop/compare/project_checker?expand=1


Api to know if the bluetooth is switched on or off

I'm trying to check if the bluetooth is switched on or switched off before use any of the other API's, I was not able to figure out which one had to be used.

#5


Parametrizing multiple dihedrals in one molecule

First of all thanks for the continued development of the notebooks, they are extraordinarily helpfull!
I was wondering how one should go about parametrizing multiple dihedral angles of one molecule.
How would one go about fitting dihedrals in multiple n-dimensions, could the fitting be done sequencially for each dihedral individually?

Hi @blebleblesm,
Thank you for your feedback. Your question is exactly what we are working right now. We are trying to fit multiple dihedral angles (two dihedral angles at the same time). We are still working on it, then I don't have a timeline when it will be ready.
Another implementation is to use your previous topology, from a previous dihedral parametrization, as an input to parametrize a new dihedral angle.
As I said before, we are working on all of these stuffs, but we have a lot of things on our plates right now, then I don't know when it will be ready. I hope soon...
Thank you.
Best,
Pablo


more operators

consider including *, ^, /

This is for constants, correct?

correct
maybe this feature never comes to PyCMDS, I don't know


mosquitto: 1.4.15 -> 1.5

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mosquitto/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 1.5 with grep in /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5
directory tree listing: https://gist.github.com/b5c8179ef176366fe98c4f442ce66385

Failure on x86_64-darwin (full log)
Attempted: mosquitto
Partial log (click to expand)
[ 93%] Building C object src/CMakeFiles/mosquitto.dir/websockets.c.o
[ 94%] Building C object src/CMakeFiles/mosquitto.dir/__/lib/will_mosq.c.o
[ 95%] Building C object src/CMakeFiles/mosquitto.dir/bridge.c.o
[ 96%] Linking C executable mosquitto_pub
[ 96%] Built target mosquitto_pub
[ 97%] Linking C executable mosquitto
[ 97%] Built target mosquitto
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/ii4z8qgh1zsfa61gx5fr1gxidjml2vpl-mosquitto-1.5.drv' failed with exit code 2
error: build of '/nix/store/ii4z8qgh1zsfa61gx5fr1gxidjml2vpl-mosquitto-1.5.drv' failed

Success on x86_64-linux (full log)
Attempted: mosquitto
Partial log (click to expand)
shrinking /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5/bin/mosquitto_sub
shrinking /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5/bin/mosquitto_passwd
shrinking /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5/sbin/mosquitto
gzipping man pages under /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5/lib  /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5/bin  /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5/sbin
patching script interpreter paths in /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5
checking for references to /build in /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5...
moving /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5/sbin/* to /nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5/bin
/nix/store/as2pydzjjv8n7lqa6q2pr5n8bj265vd4-mosquitto-1.5

Success on aarch64-linux (full log)
Attempted: mosquitto
Partial log (click to expand)
shrinking /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5/bin/mosquitto_pub
shrinking /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5/lib/libmosquittopp.so.1
shrinking /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5/lib/libmosquitto.so.1
gzipping man pages under /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5/share/man/
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5/lib  /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5/bin  /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5/sbin
patching script interpreter paths in /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5
checking for references to /build in /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5...
moving /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5/sbin/* to /nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5/bin
/nix/store/dwzad2siaa301w3galmzc19vjwf84pfg-mosquitto-1.5

changelog: https://projects.eclipse.org/projects/iot.mosquitto/releases/1.5

the build failure on darwin is a new regression.
It built before: https://hydra.nixos.org/eval/1454577?filter=mosquitto&compare=1454550&full=

upstream issue: https://github.com/eclipse/mosquitto/issues/240

@ralight it seems that CLOCK_REALTIME is unavailable on macOS.

I'm not sure if we can move forward until apple releases the updated CoreFoundation sources, but I think this problem is just Libsystem. Currently we still support back to 10.10.

mosquitto is already at 1.5.3 in nixpkgs. According to Hydra, it builds on darwin.


Can I set a model in TImageCreateParams?

Hi,
Currently I am using the following codes to generate images:
var Images := OpenAI.Image.Create(
  procedure(Params: TImageCreateParams)
  begin
    Params.Prompt(MemoPrompt.Text);
    Params.ResponseFormat('url');
  end);
try
  for var Image in Images.Data do
    Image1.Bitmap.LoadFromUrl(Image.Url);
finally
  Images.Free;
end;

However, the generated image is not very good. So I am thinking of changing the model. Can I set the model for the image parameters?
Also I check the model list, and it seems only the following one is used for image:
dall-e-2

Hi.
Just add the model parameter to the parameter list.
var Images := OpenAI.Image.Create(
  procedure(Params: TImageCreateParams)
  begin
    Params.Model('your-model-name');  <--- // here
    Params.Prompt(MemoPrompt.Text);
    Params.ResponseFormat('url');
  end);
try
  for var Image in Images.Data do
    Image1.Bitmap.LoadFromUrl(Image.Url);
finally
  Images.Free;
end;

Thank you. My code is out-dated again as it does not support Model parameter.
It seems there is only two models, dall-e-2 and dall-e-3? Is that correct?

Probably yes. Possible models are adjustable by OpenAI


Using remote images?

Apparently there is an issue drawing the labels when you try to use a remote background image. The console throws multiple native-level errors resulting in "invalid context 0x0". If you simply change the var img from a Label to an ImageView, the problem is solved. I haven't noticed any consequences, but I am only using iOS for now.

I am also having this issue. Did you keep it installed as a module or did you reference it some other way?

I don't understand what you are asking, sorry.


Audit library for any missing attribution for code snippets from Go's stdlib (encoding/json)

Issue #232 mentioned isEmpty() helper function is the same as encoding/json.
I noticed isEmpty() is missing a comment attributing the Go stdlib.  Fix this by adding a comment to isEmpty() and audit the library to correct similar issues (if any).
Example of a modified function that mentions original function:
https://github.com/fxamacker/cbor/blob/bffaf0cda7c548af6e819cd5385f025bb6fee6f8/structfields.go#L85-L86

In the meantime, update copyright notice in README.md and LICENSE as described in #234.
After that, update the copyright notice immediately below yours in each source code file if required.

Can you please audit the code for any snippet that may be from any other projects besides Go standard library?


[Aborea] Bugfix

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

fix Göttlicher Schlag

Character Sheet Info Roll20 Internal Use only.


the generated samples doesn't seem right.

the generated samples doesn't seem right.

how so?

I think the original examples are showing concept of fractal.
The input is 3x3 grid, the output is 9x9.

the overall shape of output is similar to input
and the each small 3x3 grid is the same as input.
But the generated samples doesn't show the same concept.

it's the same underlying idea, the generator is just more general in that it does not hardcode grid shapes. (3, 3) -> (9, 9) is a special case of (m, n) -> (m^2, n^2).

o, I see now.
Sorry for the fake issue feedback and thanks for your quick explain.


No tilde expansion in maildir-dir

It seems that even though the example config has
maildir-dir = "~/Maildir"

shell expansion is not yet supported in the maildir-dir variable.

Indeed, the tilde (and env vars) are not expanded in the maildir-dir. Although it should not be complicated to set up, it has already been done for the downloads-dir: https://github.com/soywod/himalaya/blob/158bc86cfaa1ad3ff2b9fb9ec842c7f941e61042/src/config/account_config.rs#L91

You can take with great pleasure! Happy to see you back :wink: (don't forget to start from the development branch).

The bug has been fixed by @TornaxO7 on the development branch, it will be shipped with the next release!


Start documenting

Consider actually documenting your code in more than one file if you are planning on actually continuing this project for real.

Actually I am trying to document the code. But yeah I should more document

Why did I closed this issue lmao


Stale render results still visible when each={} tag expression throws

See example at: http://jsfiddle.net/josschne/rg2xzvm8/
The example is a simple Todo list.
The list first has 3 items. Then 2 seconds later the items are cleared and the view is updated. However, the three original items remain in the rendered HTML. I would expect the old render results to be removed.

It looks like a bug, for now just use it in this way http://jsfiddle.net/gianlucaguarini/rg2xzvm8/3/

fixed thanks


New Relic Containerized Private Minion

Submission Template
Please provide the following information.

Vendor: New Relic
Product: Containerized Private Minion (CPM)
Version(s) affected: before 3.0.57
Status: Fixed
Update Available: Yes, NR21-04 https://docs.newrelic.com/docs/security/new-relic-security/security-bulletins/security-bulletin-nr21-04/
Notes:

New Relic released Containerized Private Minion (CPM) version 3.0.57 on December 14, 2021 to address critical vulnerability CVE 2021-44228 in the open source Apache Log4j framework that was publicly disclosed on December 9, 2021. A malicious actor may be able to execute arbitrary code using log messages or log message parameters.
This release also remediates CVE-2021-45046, a lower severity issue in the open source log4j framework that was publicly disclosed on 2021-12-14. A malicious actor may be able to trigger a denial of service condition in certain non-default configurations.
If you use Helm Charts to update your CPM configurations, you will want to implement New Relic Helm Charts version 1.0.45. This will update your CPM to version 3.0.57.
If you have already upgraded to Containerized Private Minion (CPM) version 3.0.55, Apache Foundation's current technical guidance is that your CPM has incomplete protection against CVE 2021-44228. We recommend updating to CPM version 3.0.57 at this time.
This step will remediate your New Relic Containerized Private Minion (CPM) only. You may also need to update your New Relic Java agent. Please refer to NR21-03 for more information.

References:  https://docs.newrelic.com/docs/security/new-relic-security/security-bulletins/security-bulletin-nr21-04/
Last Updated: package released 12/14/21, advisory updated 12/16/21

Note: given the change in Apache Foundation's technical guidance on CVE-2021-45046 we are in the process of revising our guidance/documentation, however the fix version remains sufficient.

@kprice-NR Thank you for your request - this has been added!


fix(global search): update global search service sdk after api changes

PR summary

PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

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


Blitz Cache and Sprig Query Params

Support Request
We are using Sprig in combination with Blitz Cache and noticed when caching a page with a Sprig include the sprig component does not pick up any of the query params in the URL.
The Sprig include code is:
{{ sprig('_pages/search-page/partials/index/sprig/results.twig', {}, {'s-trigger': 'load, refresh'}) }}

Even stranger is that when we try to change any of the query params it forces/redirects you back to the cached version (with different query params) of that page. This does not happen when Blitz Cache is disabled.
We are not sure if this is a configuration issue on our side or maybe a misunderstanding.
Here is a link to a video showcasing the scenario above: https://vimeo.com/1019780072/5d0a251c31
Application Info

PHP version: 8.3.11
Craft edition & version: Pro <IP_ADDRESS>
Database driver & version: MariaDB 10.10.7

Installed Plugins

Blitz: 5.9.0
CKEditor: 4.2.0
Embedded Assets: 5.1.2
Environment Label: 5.0.0
Formie: 3.0.8
Laméco Blitz: 5.0.0
Navigation: 3.0.4
Smith: 3.1.0
Sprig: 3.5.0
Vite: 5.0.1

Plugin Version
3.5.0

What is the Query String Caching plugin setting set to? And do you have any redirect tags in your Sprig component?

The Query String Caching setting is set to "Cache URLs with unique query strings as unique pages" which makes it kind of weird. And we don't have redirect tags inside the Sprig component.

Are you using server rewrites, and if so, have you added the correct rewrite for Cache URLs with query strings as unique pages?

I checked and can confirm we are using the first of the NGINX server rewrites with the $args.

So I’m not sure why the redirect is happening, but in general I think it’s a bad idea to cache search results as it can result in the cache store being flooded with both legitimate search queries and spam queries. I realise this doesn’t fully answer your question, but would excluding the search results page from being caching should resolve this for you?

Yes thats what we did in the end, exclude the pages that have the queries because of the reason you are describing.
Thanks anyway for try to figure it out :)


Template doc and type fixes

This fixes two issues with the templates in two commits. Let me know if you would rather like these as two separate PRs. I thought there may potentially be merge conflicts since they touch adjacent lines, so to start with, I've put them as two commits in sequence.
I'll try to illustrate the problems I'm attempting to address, using the grpcbox. I know routeguide_route_guide_bhvr.erl in that repo is a git-controlled file and not generated, so the example is admittedly a bit contrived, but nevertheless shows one of the issues.
The first commit removes @doc from the generated behaviour files since this seems to not be valid edoc:
$ cd _build/test/lib/grpcbox/test/
$ erl
1> edoc:file("routeguide_route_guide_bhvr.erl").
routeguide_route_guide_bhvr.erl, in module footer: at line 10: tag @doc not allowed here.
routeguide_route_guide_bhvr.erl, in module footer: at line 14: multiple @doc tag.
routeguide_route_guide_bhvr.erl, in module footer: at line 18: multiple @doc tag.
routeguide_route_guide_bhvr.erl, in module footer: at line 22: multiple @doc tag.
routeguide_route_guide_bhvr.erl, in module footer: at line 26: multiple @doc tag.
routeguide_route_guide_bhvr.erl, in module footer: at line 30: multiple @doc tag.

The second commit fixes the ctx type reference  in the generated code: ctx:ctx() ⟶ ctx:t()
This is with Erlang 24.3.4.

Thanks!
This is good, I'll fix up the doc to work later.


Using on Github Pages

How to use the plugin with the site hosted on Github pages where I can't set the environment variable?
Thanks

@carlosedp Github pages uses the --safe flag when building sites with Jekyll. This disallows all plugins that aren't white listed with github. You can work around this by using Travis CI with your own Jekyll build. I just did this and wrote about how I did it here. Hope this helps!


add jupyter to full and notebooks reqs

I tried pip installing the [full] and [notebooks] versions of oxonfair in empty envs, and realised i needed to install jupyter separately.

@ChrisMRuss @e-delaney not sure how to add people as reviewers to PRs - perhaps we need to add everyone to this org or fiddle around in the GH settings? Would also be good to add automatic CI tests on each PR.

Fixed.


stdlib documentation

Lots of fixes and improvements to doc output
Added requirements to list underlying requirements for a function or method
Added target listing the source targets that will output for
Control line visibility
Used visibility controls on stdlib to remove some of the internal stuff
Combine both stdlib files into single output
First pass of stdlib output

Issues:

If a function calls another function/s that has requirements/target issues that is not determined here and that is a problem for some stdlib definitions.
Types are not in general output correctly (just uses the toText of Type derived types)
No links/navigation
The 'targets' can only determine whats available based on markup - for C++ there's none. For HLSL very little is marked up and so code assumes it's always available, which is occasionally wrong.

An example is below

Texture1DMS<T>.Load
Signature
/// See Target Availability 1
T Texture1DMS<T>.Load(
    vector<int,1>        location,
    int                  sampleIndex);
T Texture1DMS<T>.Load(
    vector<int,1>        location,
    int                  sampleIndex,
    vector<int,1>        offset);
/// See Target Availability 2
T Texture1DMS<T>.Load(
    vector<int,1>        location,
    int                  sampleIndex,
    vector<int,1>        offset,
    out uint             status);

Requirements
GLSL GL_EXT_samplerless_texture_functions
Target Availability

GLSL, HLSL
HLSL

Parameters

location
sampleIndex
offset
status

I think the target availability stuff will get better over time as we make the capability system more codified and can thus use its information very directly to drive all of this.
What I'd like to see in terms of the availability information is something like a list of targets+capabilities for which the function/type/whatever is available, e.g.:

hlsl & sm_6_1
glsl_440 & GL_EXT_whatever & spirv_1_4
...

That kind of listing would seemingly allow us to both list where the feature is available and also what the conditions are on that availability.


python311Packages.sentry-sdk: 1.27.0 -> 1.27.1

Diff: https://github.com/getsentry/sentry-python/compare/refs/tags/1.27.0...1.27.1
Changelog: https://github.com/getsentry/sentry-python/blob/1.27.1/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] 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

[ ] Fits CONTRIBUTING.md.

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

4 packages marked as broken and skipped:

netbox_3_3
peering-manager
python310Packages.dalle-mini
python310Packages.dalle-mini.dist

64 packages built:

alerta-server
alerta-server.dist
cura
gns3-gui
gns3-gui.dist
gns3-server
gns3-server.dist
home-assistant-component-tests.sentry
ledfx
ledfx.dist
moodle-dl
moodle-dl.dist
mozphab
mozphab.dist
netbox
notus-scanner (python310Packages.notus-scanner)
notus-scanner.dist (python310Packages.notus-scanner.dist)
octoprint
octoprint.dist
openai-full
openai-full.dist
ospd-openvas
ospd-openvas.dist
pentestgpt
pentestgpt.dist
python310Packages.django-rq
python310Packages.django-rq.dist
python310Packages.fastai
python310Packages.fastai.dist
python310Packages.k-diffusion
python310Packages.k-diffusion.dist
python310Packages.langchain
python310Packages.langchain.dist
python310Packages.sentry-sdk
python310Packages.sentry-sdk.dist
python310Packages.skrl
python310Packages.skrl.dist
python310Packages.spacy
python310Packages.spacy-loggers
python310Packages.spacy-loggers.dist
python310Packages.spacy-transformers
python310Packages.spacy-transformers.dist
python310Packages.spacy.dist
python310Packages.textacy
python310Packages.textacy.dist
python310Packages.textnets
python310Packages.textnets.dist
python310Packages.wagtail-localize
python310Packages.wagtail-localize.dist
python310Packages.wandb
python310Packages.wandb.dist
python311Packages.django-rq
python311Packages.django-rq.dist
python311Packages.notus-scanner
python311Packages.notus-scanner.dist
python311Packages.sentry-sdk
python311Packages.sentry-sdk.dist
python311Packages.wagtail-localize
python311Packages.wagtail-localize.dist
skytemple
skytemple.dist
tribler
tts
tts.dist


feat: streamline server and ondevice templates

🚀 Deployed on https://66f580ab12da9c070a135bcf--cozy-fox-0defec.netlify.app


Scroll not Working in Safari 9.0

Hi,
Does anyone notice that scroll (by using magic mouse or touch pad) is not working in the latest version of Safari 9.0 (build 11601.1.56)? You can use one finger to scroll in the past but now you need to use two fingers (one hold and one scroll).
http://cubiq.org/dropbox/iscroll4/examples/pull-to-refresh/

me too

update iscroll.js to the latest iscroll4..v4.2.5

I am already using v4.2.5. It was okay before.

Try the 5

And rewrite a. Pull - to - refresh

It looks like that Safari doesn't like overflow-y.


a_acc_sol ,v_acc_sol in the file "planner",frequency and time looks uncontrolled

a_acc_sol = self.a_acc_start + (DT_PLAN / LON_MPC_STEP) * (self.a_acc - self.a_acc_start)
v_acc_sol = self.v_acc_start + DT_PLAN * (a_acc_sol + self.a_acc_start) / 2.0

1、why don't use actural vEgo,aEgo replace a_acc_start v_acc_start
2、Will the error increase over time?
3、In the while loop, I don't see the control of the DT_Plan time, will the time gap affect it?

This question confusing me too!

@gucasbrg , an equivalent discussion was brought up for lateral mpc in https://github.com/commaai/openpilot/pull/700 (a lot of comments... but you might get the point).
In summary:
1- in MPC, unless you have a perfect vehicle model, you really can't set the initial state as the actual vehicle state each time. Imagine your actuators have a time delay you don't consider in the MPC model: what will happen? that you would keep feeding back zero acceleration, hence the car will never decelerate. Makes sense?
2- the low level control (PID/LQR/INDI, depending on the car) is the one responsible in keeping the error low. If the error keeps increasing, then it's because the actuators are maxed out already.
3-let me think about it.

1-2: there is a long discussion
3- I'll check.


Address the 'long tail of visualization' in the documentation

HoloViews makes common operation and visualizations very easy. That said, HoloViews needs to be flexible enough to scale to finely tweaked or highly customized  visualizations.
Here are our current recommendations:

First make sure we haven't already exposed the style or plot options you are looking for.
If there is some style keyword that needs to be passed to the backend (i.e. matplotlib for now) the allowed keywords can easily be extended as detailed in the FAQ.  If you believe it ought to be available for all users, please submit a pull request explaining briefly why it is useful and showing which style_opts should list it, and we'll make it available by default
The finalize hooks need to be documented as these hooks are the easiest way for a user to change the behavior of our plotting system with minimal code.
Writing a new Plot class and if necessary a new Element type, typically extending from some existing class. Obviously the most work but extremely worthwhile, as your new plot will then compose nicely with the rest of HoloViews (automatic support for layouts, overlays, animation, the options system and more!).
Finally you can  consider exporting to SVG and tweaking the figure externally e.g. in Inkscape. This is only recommended for very minor changes just before publication as such tweaks are not reproducible!

We should definitely consider authoring a new notebook tutorial on this topic.

I've updated the above recommendations slightly by editing them.

I have now linked to this issue from the FAQ page: 44270ca9


[TA] SDK now targets 3.1-preview.2

New features generated + CI enabled with a PPE endpoint + recordings.
No new functionalities or public API changed with this PR
Fixes: https://github.com/Azure/azure-sdk-for-net/issues/14564

/azp run net - textanalytics - tests

/azp run net - textanalytics - tests


Upgrade T265 firmware to <IP_ADDRESS>1

Mask API (to convey image locations to avoid when detecting features)
Cross-device localization maps
Numerical stability improvements
2.5x lower latency for relocalizations

Closing in favor of #5169.


added screenName option to track events

Added a screenName option for GA track calls - to mimic this native GA functionality:
ga('send', 'Videos', 'play', 'Fall Campaign', {screenName: 'Home'});

How to add screenName per GA's docs: https://developers.google.com/analytics/devguides/collection/protocol/v1/parameters#cd

just needs a minor fix

lgtm!

@f2prateek do you think we should add context.screen spec + enrichment on mobile a la context.page in iOS

@sperand-io I think it makes sense functionally. We could track remember the last screen calls made by customers and parts of that call as context.screen for subsequent calls (until we see a new screen call).

@sperand-io Should I close this PR and inform the customer we are moving this functionality to context obj and it may take some time before it goes live?

Can we deploy this bug fix in the interim - until we add context.screen to
spec?
ᐧ
On Thu, Jul 21, 2016 at 2:48 PM, Prateek Srivastava <
<EMAIL_ADDRESS>wrote:

@sperand-io https://github.com/sperand-io I think it makes sense
functionally. We could track remember the last screen calls made by
customers and parts of that call as context.screen for subsequent calls
(until we see a new screen call).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/segment-integrations/integration-google-analytics/pull/44#issuecomment-234394520,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-F7N-RQYLmAIlqpQrKcjLB7z_ASr8Xks5qX-kigaJpZM4JRTqM
.

@myclamm this isn't a bug fix, it's a new feature implemented in a manner that violates first principles of Segment integrations (see below), so we can't deploy it. In order to expedite the fix we should spec context.screen ASAP and add support for forwarding the spec'd field via the integration right away. Automatic collection per Prateek's comment above will take a few weeks to get built and make its way through the release process, but the customer could implement the context.screen.name|title (whichever we decide) on their own and be in good shape.

For posterity and your understanding: here's why this fix is unacceptable:
As long as they follow our spec, customers should never have to augment their Segment tracking code for the sake of taking advantage of a downstream feature in a new or existing tool they enable. In order to ensure this, we only map standardized / spec'd properties and traits to standard downstream parameters — anything else is assumed to be custom and is sent as custom data (if possible).
properties.screenName is not a standard field, so we can't reasonably anticipate that customers would be able to take advantage of this feature of the integration having read our library quickstarts.

@sperand-io makes sense. should I change this PR to read from
context.screen.name, or should we wait for the next spec release?
On Wed, Jul 27, 2016 at 2:00 PM, Chris Sperandio<EMAIL_ADDRESS>wrote:

@myclamm https://github.com/myclamm this isn't a bug fix, it's a new
feature implemented in a manner that violates first principles of Segment
integrations (see below), so we can't deploy it. In order to expedite the
fix we should spec context.screen ASAP and add support for forwarding the
spec'd field via the integration right away. Automatic collection per
Prateek's comment above will take a few weeks to get built and make its way
through the release process, but the customer could implement the
context.screen.name|title (whichever we decide) on their own and be in
good shape.
For posterity and your understanding: here's why this fix is unacceptable:
As long as they follow our spec, customers should never have to augment
their Segment tracking code for the sake of taking advantage of a
downstream feature in a new or existing tool they enable. In order to
ensure this, we only map standardized / spec'd properties and traits to
standard downstream parameters — anything else is assumed to be custom and
is sent as custom data (if possible).
properties.screenName is not a standard field, so we can't reasonably
anticipate that customers would be able to take advantage of this feature
of the integration having read our library quickstarts.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/segment-integrations/integration-google-analytics/pull/44#issuecomment-235719207,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-F7DmpByQ818NommQ_rP_byJsAPdrWks5qZ8bXgaJpZM4JRTqM
.

@sperand-io makes sense. should I change this PR to read from context.screen.name, or should we wait for the next spec release?

@myclamm I think you should update the PR, so it's ready to be shipped with the spec update.

@f2prateek ready for review

PR revised - ready for review.
On Wed, Jul 27, 2016 at 2:35 PM, Prateek Srivastava <
<EMAIL_ADDRESS>wrote:

@myclamm https://github.com/myclamm I think you should update the PR,
so it's ready to be shipped with the spec update.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/segment-integrations/integration-google-analytics/pull/44#issuecomment-235728829,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-F7LX9w_cRm_aoUb7fgYpdqDBDPDXiks5qZ888gaJpZM4JRTqM
.

LGTM, I think we can ship this if you want to merge and release (the spec can be released later).


MKL: Adding MKL-DNN AddN op

Can one of the admins verify this patch?

@tensorflow-jenkins test this please.

What is the Ubuntu CC test that is preventing this PR from merging? It appears to be a Google Internal check. AFAICT none of these errors are related to the changes in this PR. Please merge.

All required checks are passing. Please merge.

Jenkins, test this please.


Test cli with ruby-2.5.0

2.1 is already EOL since 2017-03-31, maybe drop that while at it?

Cannot drop that yet, omnibus is still using 2.1.


Invalid step name in conditions

Expected Behavior
The generated step name for conditions is valid
Actual Behavior
If the parent name is long enough, it may become too long:
TestPipelineLevelFinally_OneDAGTaskFailed_Failure: kubelogs.go:197: E 09:59:06.501 tekton-pipelines-controller-655cb7594d-49ktz [pipelinerun/pipelinerun.go:211] [arendelle-7drp7/pipeline-level-finally-one-d-a-g-task-failed-failure-ynidsuge] Reconcile error: error creating ConditionCheck container called pipeline-level-finally-one-d-a-g-task-failed-failure-ynid-rz5k6 for PipelineTask dagtask3 from PipelineRun pipeline-level-finally-one-d-a-g-task-failed-failure-ynidsuge: admission webhook "validation.webhook.pipeline.tekton.dev" denied the request: validation failed: invalid value "condition-check-pipeline-level-finally-one-d-a-g-task-failed-failure-kmahgbvf": spec.taskspec.steps[0].name Task step name must be a valid DNS Label, For more info refer to https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names

Steps to Reproduce the Problem

See https://tekton-releases.appspot.com/build/tekton-prow/pr-logs/pull/tektoncd_pipeline/3392/pull-tekton-pipeline-integration-tests/1316675745287770115/

Additional Info
The code that builds the name is https://github.com/tektoncd/pipeline/blob/bd885f8c6d827d8114ff15718840fc8666f2b06c/pkg/reconciler/pipelinerun/resources/conditionresolution.go#L99 .
We may be able to use kmeta.ChildName to fix the issue.

Tekton Pipeline version:

v0.17.1

I can take a look at this if nobody else is.  I'm seeing it a lot and I dislodged the bug.
/assign


problem file name when the repository is downloaded

Few file name appear with upperCase like in the first version of the  library, but now every file vec is in lowercase
https://github.com/isaacs/github/issues/1520

Fixed


Wallet WSOD after CHAIN switch!!!

I have followed all the instructions on setting up the ethereum-boilerplate.
Here are the steps to reproduce the error...
1. The quick start page

2. Authenticate with MetaMask wallet.

3. Navigate to Wallet NavLink (Works!)

4. Change from Polygon Network to Ethereum

I'm at a loss.......

https://github.com/ethereum-boilerplate/ethereum-boilerplate/pull/147#issue-1207796046
You are gonna have to refresh the page after switching networks however

Closing since we released V2


fix make test-dependencies by only perform 'mv' if kubebuilder doesn't exist already

addresses https://github.com/open-cluster-management-io/community/issues/58
Signed-off-by: Mike Ng<EMAIL_ADDRESS>

/assign dhaiducek


False positive multiline values

When a line ends with an escaped backslash, it should not be considered a multiline value.
[Section]
Test1=foo\\
Test2=bar

ini = IniParse.parse(File.read('file.ini'))
puts ini.to_ini

[Section]
Test1 = foo\Test2=bar

Thanks for the report. Should be fixed in v1.4.1 which I just pushed to rubygems.org.

That was fast! Thanks!
It is not accurate though, since if you have 3 (or any other odd number of) backslashes it should be joined, but that's a rare use-case.


Document loadpaths in configuration.edn

As per the commit by Tims: https://github.com/arcadia-unity/Arcadia/commit/9f1a8d0737e804f6e6eaedffca9e3bb124cf4e31

Looks great! Can you add your name to CONTRIBUTORS.md with a commit message saying you've read and agree to CONTRIBUTOR-LICENSE-AGREEMENT.md? Ready to merge otherwise.

@nasser Done.

✌🏽


[GraphRBAC] Add delete owner

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go


other: update scala-library from 2.13.5 to 2.13.7

Updates org.scala-lang:scala-library from 2.13.5 to 2.13.7.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

labels: library-update, early-semver-patch, semver-spec-patch

Codecov Report

Merging #8 (96abdaf) into master (0706e54) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #8   +/-   ##
=======================================
  Coverage   98.64%   98.64%
=======================================
  Files          10       10
  Lines          74       74
  Branches        5        5
=======================================
  Hits           73       73
  Misses          1        1

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 0706e54...96abdaf. Read the comment docs.


Adding Border to Stack Causes Resize and Position Errors

Current behavior

When adding a border to stacks via CSS, e.g.
.lm_item.lm_stack {
border: 2px dashed red;
}
borders correctly appear around the stacks, but positioning and moving the stacks behaves in an inconsistent manner.
Expected behavior:

Stacks should be re-positioned as if the border had not be modified.
Codepen example:

https://codepen.io/benjaminlee314/pen/gWbOKW

This is because the layout is expecting a width of X, you then add a border so the total width is (2px x 2) x3 + X.
A simple work around would be to use outline instead of border

I did not investigate this issue but it sounds like a thing caused by a box-sizing:content-box default property. We should switch to a box-sizing:border-box model to address this kind of problems

@ldetomi Can confirm; this works -
.lm_item.lm_stack {
  border: 2px dashed red;
  box-sizing: border-box;
}

I think that this is caused by "how" JS calculates size of dragged boxes... changing box-sizing generally is not a light edit, causes some consequences...
Solution is surely passing though it, but it need attention before implementation... :-)

A possible solution: pull request #303 .


KAFKA-13834: fix drain batch starving issue

Maintains a drainIndex for each node

@ruanliang-hualun Thanks for the PR, and thanks to @showuon for the detailed reviews!! I took a look at the edge test and I think without the actual fix it would indeed cause starvation. I do not have any further comments, and would leave to @showuon to finally approve and merge it :)

Failed tests are unrelated.
    Build / JDK 8 and Scala 2.12 / kafka.server.KRaftClusterTest.testSetLog4jConfigurations()
    Build / JDK 8 and Scala 2.12 / kafka.server.KRaftClusterTest.testLegacyAlterConfigs()
    Build / JDK 8 and Scala 2.12 / kafka.server.KRaftClusterTest.testCreateClusterAndPerformReassignment()
    Build / JDK 17 and Scala 2.13 / kafka.server.KRaftClusterTest.testIncrementalAlterConfigs()

@ruanliang-hualun , thanks for your contribution!

@ruanliang-hualun , I found the test should add one more test case, which is "normal" test case. We can put the maxSize as a large one, and expect all the partitions should be drained. ex:
// new added
// set maxSize as a max value, so that the all partitions in 2 nodes should be drained: node1 => [tp1, tp2], node2 => [tp3, tp4]
Map<Integer, List<ProducerBatch>> batches1 = accum.drain(cluster, new HashSet<Node>(Arrays.asList(node1, node2)), Integer.MAX_VALUE, 0);
        verifyTopicPartitionInBatches(batches1, tp1, tp2, tp3, tp4);

        accum.append(tp1, 0L, key, value, Record.EMPTY_HEADERS, null, maxBlockTimeMs, false, time.milliseconds());
        accum.append(tp2, 0L, key, value, Record.EMPTY_HEADERS, null, maxBlockTimeMs, false, time.milliseconds());
        accum.append(tp3, 0L, key, value, Record.EMPTY_HEADERS, null, maxBlockTimeMs, false, time.milliseconds());
        accum.append(tp4, 0L, key, value, Record.EMPTY_HEADERS, null, maxBlockTimeMs, false, time.milliseconds());

// original tests
// drain batches from 2 nodes: node1 => tp1, node2 => tp3, because the max request size is full after the first batch drained
Map<Integer, List<ProducerBatch>> batches1 = accum.drain(cluster, new HashSet<Node>(Arrays.asList(node1, node2)), (int) batchSize, 0);
        verifyTopicPartitionInBatches(batches1, tp1, tp3);

What do you think?
If you think it makes sense, are you interested in submitting another PR to add the test?
Thank you.

@showuon  I am glad to submit another PR to add the test, thanks for your reminding


DOCKERCONFIG should be PFLT_DOCKERCONFIG and should not be required

Bug Description
PR #282 resolves an issue with private registry access when running the DeployableByOLM check by pushing an explicitly provided dockerconfigjson file to the cluster so that the CatalogSource can pull from a private registry.
With that said, it's not required and it should not be. If a user does not set this environment variable, preflight currently exists.
It's plausible that the index image used by the CatalogSource will be publicly available, and so we should not have to create any secret, or pass that secret to a CatalogSource resource in order to run the check.
Version and Command Invocation
ef91135080a4a4a8d927b7d78b797d269be837f9
Steps to Reproduce
Attempt to run preflight check operator <bundle> without DOCKERCONFIG set in the environment.
Expected Result
Preflight to execute for a publicly available image without having to set the variable.
Actual Result
(What actually happened)
Additional Context
(Anything else you think might help us troubleshoot, like your platform, dependency versions, etc).

The naming should be PFLT_DOCKERCONFIG just to help disambiguate between that and the standard DOCKER_CONFIG variable (and their respective purposes and formats).


Integration with Linkerd

Is your feature request related to a problem? Please describe.
Can easegress be integrated with Linkerd
Describe the solution you'd like
I would like to use Linkerd,  as it has lesser latency than other service meshes. But features like circuit break etc. are not available in Linkerd. Easegress anyhow helps in having those features..

Thanks for contributing 🎉!

hi @madugula007 , I'm unclear about the word integration and your requirement.
For service mesh, we have a product EaseMesh built on Easegress.

EaseMesh is limited to javaspring cloud ... My APIs are in Golang. Also no mTLS as of now..

EaseMesh also supports other languages besides Java/Spring by installing EaseMesh-CoreDNS .
And actually, we have supported mTLS[1] now without updating the document, which will be done soon.
[1] https://github.com/megaease/easegress/blob/38eac8e335ece1cb3494c1f2033c017cf999338b/pkg/object/meshcontroller/spec/spec.go#L120

EaseMesh is limited to java spring cloud ... My APIs are in Golang. Also no mTLS as of now..

EaseMesh supports other languages. we have the demo for golang application, you can have look - https://github.com/megaease/easemesh-demo

@madugula007  I've added a demo guide in README for https://github.com/megaease/easemesh-demo , please check it out.

Thank you will certainly try.
Kindly help me if I stuck somewhere.
Will update..


Possible invalid axioms for 'mesenchymal stem cell'

When the full versions of go-plus and Uberon ext are used together, these two axioms result in unsatisfiable classes:
'mesenchymal stem cell' SubClassOf 'capable of' some 'cardiac muscle cell differentiation'
'mesenchymal stem cell' SubClassOf 'capable of' some 'osteoblast differentiation'

I'm just going to paste the equivalent class here to give @dosumis nightmares:
'connective tissue cell'
 and ('has plasma membrane part' some endoglin)
 and ('has plasma membrane part' some 5'-nucleotidase)
 and ('has plasma membrane part' some 'Thy-1 membrane glycoprotein')
 and ('capable of' some 'osteoblast differentiation')
 and ('capable of' some 'cell migration')
 and ('capable of' some 'neuron differentiation')
 and ('capable of' some 'epithelial cell differentiation')
 and ('capable of' some 'fat cell differentiation')
 and ('capable of' some 'cardiac muscle cell differentiation')
 and ('capable of' some 'chondroblast differentiation')
 and (lacks_plasma_membrane_part some 'MHC class II protein complex')
 and (lacks_plasma_membrane_part some 'CD34 molecule')
 and (lacks_plasma_membrane_part some 'receptor-type tyrosine-protein phosphatase C')

Maybe we should consider a refactor where such things move to an annotation file.
On Jun 3, 2017, at 5:06 PM, Chris Mungall <notifications<EMAIL_ADDRESS>wrote:
I'm just going to paste the equivalent class here to give @dosumishttps://github.com/dosumis nightmares:
'connective tissue cell'
and ('has plasma membrane part' some endoglin)
and ('has plasma membrane part' some 5'-nucleotidase)
and ('has plasma membrane part' some 'Thy-1 membrane glycoprotein')
and ('capable of' some 'osteoblast differentiation')
and ('capable of' some 'cell migration')
and ('capable of' some 'neuron differentiation')
and ('capable of' some 'epithelial cell differentiation')
and ('capable of' some 'fat cell differentiation')
and ('capable of' some 'cardiac muscle cell differentiation')
and ('capable of' some 'chondroblast differentiation')
and (lacks_plasma_membrane_part some 'MHC class II protein complex')
and (lacks_plasma_membrane_part some 'CD34 molecule')
and (lacks_plasma_membrane_part some 'receptor-type tyrosine-protein phosphatase C')
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/obophenotype/cell-ontology/issues/474#issuecomment-305980589, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAwn3PPoHu5LbIaXLKt23h8UhSGuxQutks5sAXZagaJpZM4NvGYz.

When the full versions of go-plus and Uberon ext are used together, these two axioms result in unsatisfiable classes:

'mesenchymal stem cell' SubClassOf 'capable of' some 'cardiac muscle cell differentiation'
'mesenchymal stem cell' SubClassOf 'capable of' some 'osteoblast differentiation'

I suspect the problem is the taxonomic broadness of cardiac muscle cell def.  Do you have an explanation handy?

I'm just going to paste the equivalent class here to give @dosumis nightmares

You succeeded.  I'm skeptical of the biology, but even if true for mice or humans, the EC expression is still completely useless for automated classification.

Maybe we should consider a refactor where such things move to an annotation file.

This has been suggested in the past.  I'd certainly like to move the membrane markers out into some separate file marked as applicable to mouse &/or human.

As a first pass I was going to weaken to a taxon-specific equivalence, e.g.
(CL and part-of some NCBITaxon) EquivalentTo (....long complex expression...)
@davidos criticisms still apply, but at least we avoid outright logical incoherency and we can rapidly implement this, and it's easy to apply future refactoring

@dosumis here is the example I had put in my original oborel issue.

Ta.  Looks like very different usage of the term 'mesenchymal stem cell' between flies and mammals.

We need to fix this
Here is the axiom (this time in markdown):
mesenchymal stem cell EquivalentTo connective tissue cell and (has plasma membrane part some PR_000001345) and (has plasma membrane part some PR_000001800) and (has plasma membrane part some PR_000001843) and (capable_of some osteoblast differentiation) and (capable_of some cell migration) and (capable_of some neuron differentiation) and (capable_of some epithelial cell differentiation) and (capable_of some fat cell differentiation) and (capable_of some cardiac muscle cell differentiation) and (capable_of some chondroblast differentiation) and (lacks_plasma_membrane_part some MHC class II protein complex) and (lacks_plasma_membrane_part some PR_000001003) and (lacks_plasma_membrane_part some PR_000001006)
questions of species-specificity aside, the provenance for this is a paper about bone marrow MSCs: https://pubmed.ncbi.nlm.nih.gov/17986482/

Note also MSC and mesenchymal cell (MC) are not connected in the ontology.
I think we need a good definition of MC. I also think MSC should be a subclass. We should probably have something for MCs that have reached a terminal state?
MC and EC (epithelial cell) properties exist on a contimuum so this is fairly hard. Also defining where MC ends and subsequent cell types begin e.g. fibroblast
I'm going to treat MC as the more general class for now and change the uberon definition


Panics with deoplete-go on Windows

I'm trying to use deoplete-go in Windows in Neovim, which builds on top of gocode.
Unfortunately I get [deoplete] gocode panicked errors. I'm still seeing completions though.
Here is the output of gocode -s -debug for one such error:
2017/02/18 01:26:13 Go project path: hello
2017/02/18 01:26:13 Got autocompletion request for 'C:\Users\xelra\go\src\hello\hello.go'
2017/02/18 01:26:13 Cursor at: 83
panic: runtime error: slice bounds out of range
1(runtime.call32): C:/Go/src/runtime/asm_amd64.s:514
2(runtime.gopanic): C:/Go/src/runtime/panic.go:489
3(runtime.panicslice): C:/Go/src/runtime/panic.go:35
4(main.server_auto_complete): C:/Users/xelra/go/src/github.com/nsf/gocode/server.go:190
5(main.(*RPC).RPC_auto_complete): C:/Users/xelra/go/src/github.com/nsf/gocode/rpc.go:26
6(runtime.call64): C:/Go/src/runtime/asm_amd64.s:515
7(reflect.Value.call): C:/Go/src/reflect/value.go:434
8(reflect.Value.Call): C:/Go/src/reflect/value.go:302
9(net/rpc.(*service).call): C:/Go/src/net/rpc/server.go:387
10(runtime.goexit): C:/Go/src/runtime/asm_amd64.s:2197

This is my go env:
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\xelra\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
set PKG_CONFIG=pkg-config
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2

@xelra Hi, I'm deoplete-go author, also gocode contributor.
IIRC it seems to deoplete-go bug(maybe) But I don't know what your edited Go sources.
So, Could you re-post to deoplete-go issue with sample Go sources?
Thanks.

Seems like plugin passes cursor position outside of boundaries of the currently edited file. A source code example would be nice indeed. I also added some code for debug mode which does the boundaries check for cursor. It would yield a more useful error message. However it won't include the source code still though.

@nsf Yeah, maybe I think my plugin was get the wrong buffer or cursor position.
Thanks for adding the useful debug log message :)

As requested, I've created a cross-issue on zchee/deoplete-go.
The source code is a simple "hello world" file:
package main

import "fmt"

func main() {
    fmt.Printf("hello, world\n")
}

@xelra Are you still have this issue? If so, As @nsf said,

Seems like plugin passes cursor position outside of boundaries of the currently edited file

I think too, because if you tested with posted "hello world" file, that end of byte offset is 75. So 83 offset is impossible.
.
.
2017/02/18 01:26:13 Cursor at: 83
.
.

I think this issue is not gocode side, maybe Neovim's API(or wrong get offset by the deoplete-go). I'll create Windows10 VM on VMWare and try to test it.
Anyway, It seems better to close this issue.

Yes, I'm still having this issue. I just set it up on another Windows 10 Professional machine and it's exactly the same. Latest version of everything: Neovim, Neovim-Qt, gocode, deoplete.nvim and deoplete-go.

@xelra I see.
I'm macOS but works fine. So it certainly seems to be only of Windows issue.
If Neovim's API is wrong, another plugin will also have the same issue. I want to try to investigate this issue.
OK, Let's close this issue and move the discussion place there:
https://github.com/zchee/deoplete-go/issues/94

I get the reason.
It seems deoplete-go error.
I will fix it later.


Incorrect page title of the Sticky demo page

fixes #5686

Thanks for submitting the PR, but the issues labeled with good first issue are only for the first contributors, and more than one PR for them from a single contributor is not acceptable for our repository.
I'm sorry but I have to reject and close this PR.


Add a way to get the furthest Navigator

#12107

Either this patch or the patch before it (https://github.com/flutter/flutter/commit/f6135107bcba92f02df6572d1a8be5e93863e6f6) regressed flutter_gallery_ios__transition_perf average_frame_build_time_millis significantly. Please revert this patch then determine the cause before relanding it. Thanks!

It may also have caused a regression of complex_layout_scroll_perf_ios__timeline_summary ms average_frame_rasterizer_time_millis.

I think this PR wasn't it based on the benchmarks' metrics after the revert

Maybe it's https://github.com/flutter/flutter/pull/12578 then?

I've got a revert for that one in https://github.com/flutter/flutter/pull/12661.


@tanstack/react-query-devtools v4 does not include NODE_ENV check

Describe the bug
According to the documention, devtools should only be included in development mode:
https://tanstack.com/query/v4/docs/devtools#install-and-import-the-devtools
React Query v3 devtools include check for that:
https://github.com/TanStack/query/blob/v3/devtools/index.js
React Query v4 are missing this check which results in devtools being bundled in production and increasing overall bundle size:
https://github.com/TanStack/query/blob/main/packages/react-query-devtools/src/index.ts
Your minimal, reproducible example
https://stackblitz.com/edit/nextjs-odbs3c?file=pages/_app.js
React Query v3 does not have this issue:
https://stackblitz.com/edit/nextjs-ssq6g3?file=pages/_app.js
Steps to reproduce

Open _app.js file
Open terminal and run npm run build
Comment out <ReactQueryDevtools initialIsOpen={false} /> and import { ReactQueryDevtools } from '@tanstack/react-query-devtools';
Run npm run build
Notice that shared bundle size decreased from 103kB to 90kB

Expected behavior
React Query Devtools should not be bundled in production build by default.
How often does this bug happen?
Every time
Screenshots or Videos
Next 12.2 project with devtools enabled:

Next 12.2 project with devtools disabled:

Platform

OS: MacOS
Browser: Chromium
Version: 4.0.3

react-query version
4.0.3
TypeScript version
4.7.4
Additional context
No response

I re-created what we had in v3 here: https://github.com/TanStack/query/pull/3861
but it doesn't seem to work well with ESM. Do you have a better idea?

I am guessing this issue also causes these failures in my test too:

@jaworek can you try it out with this codesandbox preview build?
"@tanstack/react-query-devtools": "https://pkg.csb.dev/TanStack/query/commit/df9c197e/@tanstack/react-query-devtools",

it doesn't seem to work on my tests with the stackblitz - I get 101kb with the devtools and 87 without them.
However, I also get 101kb if I do:
      {process.env.NODE_ENV === 'development' && (
        <ReactQueryDevtools initialIsOpen={false} />
      )}

which, idk, should be the same as if the devtools were not there at all, right?

Hi,
"@tanstack/react-query": "^4.0.5",
"@tanstack/react-query-devtools": "^4.0.6",

@Manubi which bundler is this?

Having the same issue. Devtools not loading.

Can someone please provide more info?

Hi again,
"react": "18.2.0",
"react-dom": "18.2.0",
"next": "12.2.2", with webpack 5.
Anything else?

fix is here:

https://github.com/TanStack/query/pull/3884

I face the same problem like @Manubi


Feature | Login from a directory other than a layer

Describe the Feature
As per one of our client users request, it is desirable to be able to log in with Leverage from any directory inside a Leverage project.
Today there is a requirement to be in a layer directory to login. The idea is to allow the user to run the login command for Leverage from any directory under the Leverage project.
As per this line the login can be done from account, layer o layer-group dirs:
https://github.com/binbashar/leverage/blob/master/leverage/modules/aws.py#L147
When configuring:
❯ leverage aws configure sso
[16:45:00.071] ERROR    SSO configuration can only be performed at layer level.

Expected Behavior
To be able to log in from any directory under a project.

Adding extra comments based on @juanmatias and @diego-ojeda-binbash slack discussion.

The user wants to avoid going to a layer of the reference architecture to refresh credentials and be able to use kubectl.
An integration with kubeconfig would be needed - perhaps it could go hand in hand with the idea of @angelofenoglio / @Franr to create a script (a little independent and reusable) that handles credentials and other interactions with the AWS API via Boto.
There are two things here... one is how to log in to AWS (e.g. leverage aws sso login) and the other is how we're getting the kubectl creds (which is in the new version of leverage CLI).

For the first one, it's what I put in the ticket
For the second, you have to be in the cluster layer because of the outputs so some extra review and design will be needed.

CC: @binbashar/leverage-ref-architecture-aws-dev @binbashar/leverage-ref-architecture-aws-admin

Even if this could be seen as nice to have for a future version, for the moment we'll close this issue till customer projects actively requires it. This will give more space to work on more urgent fixes and features.
For the moment the user can get both AWS and Kubectl credentials using the leverage standard workflows

https://leverage.binbash.co/user-guide/leverage-cli/reference/kubectl/#configure
AWS SSO creds

https://leverage.binbash.co/user-guide/ref-architecture-aws/features/sso/configuration/#1-configuring-aws-sso
https://leverage.binbash.co/user-guide/leverage-cli/reference/aws/
https://gist.github.com/exequielrafaela/2d963c6f12186a1492f870ce2f9f9dde


Disabled radio-button still receives click events

Reproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/angular/xxjmayybegr
Steps to reproduce:

Click Disabled button: nothing happens
Click Summer disabled radio button: an alert is emitted.

Expected Behavior
What behavior were you expecting to see?
Since the radio button is disabled, the (click) output should not be emitted.
Actual Behavior
What behavior did you actually see?
The alert is emitted.
Environment

Angular: 8.2.9
CDK/Material: 8.2.2
Browser(s): Chromium Version 77.0.3865.90 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit)
Operating System (e.g. Windows, macOS, Ubuntu): Debian

Doesn't look like the stackblitz has any disabled options

Damn I failed my stackblitz. Here is the updated URL: https://stackblitz.com/edit/angular-aceywx

I think that the issue may be that you directly have the (click) event on the component on your side of your app. Even though the component is disabled, the (click) event will always be emitted, and the material library will not be able to prevent that.
So, the issue in my opinion is not related to the library itself. Any thoughts?

The disabled attribute only prevents events on native elements, whereas mat-radio-button is a custom one. You should be able to use the custom change event which won't fire on disabled radio buttons.


restrict people-accounts relationship to foreign key

person has exactly one account
accounts can belong to multiple people

this means Person should have a foreign key relationship to Account rather than a many-to-many. if this is hard, we can try to enforce it using frontend validation, but if not, we can go ahead and restrict it to a FK.

I don't think the constraint is a priority.  Am I correct in assuming that the constraint is mainly to help us avoid introducing errors?
J

On Apr 30, 2018, at 4:20 PM, Rebecca Sutton Koeser<EMAIL_ADDRESS>wrote:
We'll need to pay attention to how these changes affect the edit interface. We will also likely need a data migration to split out the current people with more than one account before we add/enforce this constraint.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


feat: make inputs signal based

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
Current Inputs are not signal based

Issue Number: #6
What is the new behavior?
Inputs are updated to signal based
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
This pull request is specifically for input-based signals. I will submit a separate pull request for output-based signals.

This MR has lot more issues than expected. @deepakrudrapaul please test all the variants of toast carefully.


Generating OPT predictions on prompts

Hi,
I'd like to know what's the process for setting up prompts (where can I find it in the code) for training to generate predictions on new ones?
I'm trying to use OPT-175B as an alternative to GPT-3.
Thanks a lot!

@AnaRhisT94 are you asking to generate from OPT-175B or to feed the model more data to train on / fine-tune with?

Hi,
I'm willing to finetune it on around 10k prompts.

This seems to be the same as https://github.com/facebookresearch/metaseq/issues/105 (adjusted to refer to finetuning).  We can follow-up there.


Issues with github repo exodus whatsapp version

Hello, hope you are all doing great. I have tried following the steps of deleting the package files and then installing whatsapp web js from pedros github repo.
It resolves the evaluation issue for me but now I am limited to only sending text messages. Whenever I try sending audio, video, or any image it doesn't work and just stuck at client.sendMessage.
Thank you for looking,
Arsal

I will soon study wwebjs to create a solution there to be able to use, use here in wppconnect normally the wa-version


Unexpected keyword arg 'inplace' for torch.nn.SiLU

🐛 Bug
NeMo's StableDiffusion uses SiLU activation in its UNet model. When UNet stage is run with thunder.jit, thunder gives an error:
silu() got an unexpected keyword argument 'inplace'.
Specifically the error is is raised in this line of torch/nn/modules/activation.py although inplace is a valid argument of the op.
CC: @tfogal
cc @tfogal

I had a chat with @athitten on this one. THe SiLu in question is purely internal to the model--we could just functionalize this as a solution.

triage review —

we can add the inplace argument to the signature and throw a NotImplementedError if it's True for now, that will also provide a more informative error message to tell us if this is actually being used inplace
we should revisit general inplace operator support with Q3 planning


cleanup game of life

This cleans some things up like using ? where applicable and removing unnecessary code.

I need to get the vscode rust extension to work again. It just doesnt do anything useful.

I thought I left replied for this ages ago!!! now they're all gone...

I thought I left replied for this ages ago!!! now they're all gone...


Publish to open-vsx.org

Pls publish the vscode plugin to OpenVSX, so users of OSS versions / vscode forks can also use markwhen.
This is a issue discussing the relavant background, and the approach taken by many other extensions can be navigated to using the issue references for other plugins.
https://github.com/microsoft/vscode/issues/31168

https://open-vsx.org/extension/Markwhen/markwhen


feat: add getAllOpList

#18

Rather than manually copying in all these protos (which may become out of date with the so library) is there some other way to link to these? Maybe having TF be a git-submodule? Or maybe we can get TF to distribute the proto files in its binary tarballs, since they are apparently part of the public API.

Rather than manually copying in all these protos (which may become out of date with the so library) is there some other way to link to these?

What my previous thoughts is downloads those proto files from GitHub raw files, and remove them from source.

Or maybe we can get TF to distribute the proto files in its binary tarballs, since they are apparently part of the public API

@ry current binary dist doesn't contain the proto files, maybe this a Pull Request for TensorFlow?

I found this package: https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow_proto-1.2.1.tar.gz

<Error>
  NoSuchKey
  <Message>The specified key does not exist.</Message>
</Error>

Unfortunately got the above error from this link @ry :(

Sorry. https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow_proto-1.2.1.zip

@yorkie @ry  yes, we can move the protos to https://github.com/tensjs/tensorflow-downloader

@demohi As the #21 has been merged, so that all the protos has been removed, and the OpList should be at protobuf/tensorflow/core/framework/op_def.proto. Could you please rebase it with the latest master, thank you :)

@yorkie 👍

ping @yorkie

CI is passing :)


Bookstore: style

Milestone: style
The following changes are being introduced:

Final design matching the design provided

Hi @MahmoudBakr23
Thanks👍


Kein Sponsoring gefunden

Describe the bug
After setting up the sponsoring for evcc, I try to get the token via this page: https://sponsor.evcc.io/
When selecting "Sponsortoken erhalten", I am forwarded to github to grant access to my account information, which I granted. After some time, a page with above message shows up.
How to show, that I am sponsor of great evcc?
Steps to reproduce

go to https://sponsor.evcc.io/
select "Sponsortoken erhalten"
wait for error message. it shows up all the time

Configuration details
n/a

Log details
n/a

What type of operating system are you running?
Linux
Version
No response

Ok, maybe I was too impatient, now the token is available. Maybe you add a hint that "Wenn Du erst kürzlich Sponsor wurdest, so probiere es bitte zu einem späteren Zeitpunkt erneut."


Implement basic support for bank account sources

This allows creating a customer using bank account tokens, defaulting to "new" state, and then always marking as verified when verify endpoint gets called.

Note that this was the minimum change necessary in order to make our feature specs work - I'm sure one could cover the API more extensively, but this is the minimum so we can use this library for mocking.

@alexmamonchik Yay, thanks for the fast merge - that makes me eager to contribute more in the future 🎉

@lfittl You're welcome! I started as you. Just sent PR with changes what I wanted. This is really nice library, let's make it more powerful!


Automator: update<EMAIL_ADDRESS>dependency in<EMAIL_ADDRESS>

Generated by Automator - 2020-11-04T01:17:04+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio_release-1.8
1b805cb45cf25c947e1833280b8ccb6e582725c0
link
/test integ-multicluster-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-multicluster-k8s-tests_istio_release-1.8
failed because start up is stuck on cluster warming.


[Removal]: The hotspot was added incorrectly

Hotspot Name
Petite Banana Gibbon
Hotspot b58 Address
11rG62vqvdDqunKhEBmcH2gyMcDMDn6C2PGK7QETjrWwFvjCLSn
Discord Handle
No response
Hotspot Manufacturer
Nebra
Removal Reason
This hotspot is legitimate and incorrectly included in the deny list. It is located with my other fleet of miners with my friends and family in Klotz, Germany. The hotspot was incorrectly added to the deny list.
Modifications
Yes
Extra forwarders
No
Extra antennas
No
Additional Information
only changed the original indoor antenna with an outdoor one

We do not have sufficient evidence to remove these hotspots from the denylist. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.

I'm sorry this is not acceptable , my hotspot is legitimate I didn't do any hacks, what evidence do you have to shut down my investment this way, at less tell me what I'm doing wrong so i can correct it,,
Please remove my hotspots from this list, i have been suffering from all kinds of bugs in your software for 3 months and now you shut my miners off without a reason..
this is not professional and not acceptable
Please remove my miners from this list. otherwise, provide instructions on what should i do from my end


Export data to useful formats

There are a number of different formats that one could need from your drawings.
Examples:

Hex Colors
AESPRITE format

@Kully What format would the Hex colors be? Is it just a .txt with a list of hex codes used in the image? Or would it be more detailed showing each hex code and its position as well?
Or maybe there is another format you had in mind.


caniuse.com/#feat=clipboardevent should redirect to caniuse.com/#feat=clipboard

caniuse.com/#feat=clipboardevent should redirect to caniuse.com/#feat=clipboard

This issue was imported from Google Moderator
Moderator votes: +4
Issue added by dotnetCarpenter on 2015-03-03
To vote this issue up or down, simply include +1 or -1 in your comment.

@Fyrd This is more of a simple alias.

Yeah, have added it to keywords.


Docs rendering error

https://federatedscope.io/docs/algozoo/#additional-functions-for-fedprox-algorithm
Here⬆The article format seems to be a bit messed up.

This thread is closed, as we have fixed this rendering issue. Thanks again!


Event Custom RPC

Goal
The goal of this PR is to offer an RPC endpoint with easier options for getting events and handling scale decoding.
It reduces the scale decoding issue to one of just the event enum/struct instead of needing to worry about the substrate wrapping of the events.
Closes #994
Testing

Start instant sealing
Create schema, msa, or other things that trigger events
Snag the block hash and put in into this curl command (feel free to skip the jq call if you want non-formatted response):

curl --location --request POST 'localhost:9933' --header 'Content-Type: application/json' --data-raw '{
    "id":1,
    "jsonrpc":"2.0",
    "method": "frequency_getEvents",
    "params": ["'$HASH'"]
}' | jq

You should see the events and can scale decode them using the event structure and https://www.shawntabrizi.com/substrate-js-utilities/codec/

MSA Create Event SCALE
{
  "Msa.MsaCreated": {
    "msa_id": "u64",
    "key": "[u8; 32]"
  }
}

To Do

[x] Test js/api-augment updates

Checklist

[x] Updated js/api-augment.
[x] Tests added

@shannonwells

Does the SCALE decoding information fall out of the RPC setup? How do you get it?

You still have to get that information from the Metadata or from hard coding it. The primary benefit is that you know what event it is before you decode it. This means that you could even ignore decoding the event if all you want to know is that the event happened. (or only decoding the events you care about the data from)


The result begins to corrupt around 140,000 iterations.

What is the reason?

I think it is because the different learning rate decay between gaussian model and deformation model. Is that reasonable?