balanced_consumer ConsumerStoppedException

hi,
I have some troubles when i use balanced_consumer to get msg..
code is like this:
    client = KafkaClient(hosts=Config.brokerList)
        topic = client.topics[Config.topic]
        consumer = topic.get_balanced_consumer(
            consumer_group='testgroup',
            auto_commit_enable=True,
            zookeeper_connect=Config.zookeeperList,
            consumer_timeout_ms=5000
        )
        msgs = []
        while True:
            msg = consumer.consume()
            if (msg == None):
                return msgs
            print(str(msg.offset) + ":" + msg.value)
            #msgs.append(msg)

when it runs on "consumer.consume()",it raise the exception:ConsumerStoppedException
so, hope someone tell me what's wrong with it... thx

Hi @hxxgy. Please ensure that the zookeeper and broker hosts you're supplying are accessible from the machine you're running this code on. The ConsumerStoppedException is expected from the consume() call every once in a while, but if you're encountering it on every call, it's likely that you have something misconfigured. It could also be a bug in pykafka, but other instances of this problem I've seen have been misconfigurations. Also, please test with the most recent version of pykafka.

I met the same problem.
➜  temp pip freeze
pykafka==2.4.0.
when changed the code to get_simple_consumer(),my code works well
my code looks like this:
_balanced_consumer = topic.get_balanced_consumer(
consumer_group='infogen_yunying_topic_job_create',
auto_commit_enable=False,
zookeeper_connect='<IP_ADDRESS>:2181,<IP_ADDRESS>:2181,<IP_ADDRESS>:2181'
)
for message in balanced_consumer:
if message is not None:
print message.offset, message.value_
and exception looks like this:
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/site-packages/pykafka/balancedconsumer.py", line 742, in iter
message = self.consume(block=True)
File "/usr/local/lib/python2.7/site-packages/pykafka/balancedconsumer.py", line 731, in consume
raise ConsumerStoppedException
pykafka.exceptions.ConsumerStoppedException

hey, @emmett9001 thanks for your response...
seems someone else also has the same question. @lolandkidtress
the version of pykafka I used is 2.4.0, and if i used simple_consumer, the code works fine..
but as you know, simple_consumer can't set the consumer-group, so it's not meet my demand
i also try kaka-python which can set consumer-group，it works fine too...
so i'm confused...

@hxxgy Do you have any additional log output you can provide? To get more complete output from pykafka, you can add this code to the top of your test script:
    import logging
    kafkalogger = logging.getLogger('pykafka')
    kafkalogger.setLevel(logging.DEBUG)
    console_handler = logging.StreamHandler()
    formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')
    console_handler.setFormatter(formatter)
    console_handler.setLevel(logging.DEBUG)
    kafkalogger.addHandler(console_handler)

Without additional log output it will be very difficult to solve your issue. Thanks!

2016-08-05 23:48:26,778 - pykafka.cluster - INFO - Attempting to discover offset manager for consumer group 'test_group'
2016-08-05 23:48:26,806 - pykafka.cluster - ERROR - Error discovering offset manager.
2016-08-05 23:48:26,808 - pykafka.cluster - ERROR - Error discovering offset manager.
2016-08-05 23:48:26,811 - pykafka.cluster - ERROR - Error discovering offset manager.
2016-08-05 23:48:26,814 - pykafka.cluster - ERROR - Error discovering offset manager.
2016-08-05 23:48:26,814 - pykafka.cluster - DEBUG - Retrying offset manager discovery
2016-08-05 23:48:27,739 - pykafka.handlers - INFO - RequestHandler worker: exiting cleanly
2016-08-05 23:48:27,752 - pykafka.handlers - INFO - RequestHandler worker: exiting cleanly
2016-08-05 23:48:28,823 - pykafka.cluster - ERROR - Error discovering offset manager.
2016-08-05 23:48:28,823 - pykafka.cluster - DEBUG - Retrying offset manager discovery
2016-08-05 23:48:30,841 - pykafka.cluster - ERROR - Error discovering offset manager.
2016-08-05 23:48:30,842 - pykafka.cluster - DEBUG - Retrying offset manager discovery
2016-08-05 23:48:32,845 - pykafka.cluster - ERROR - Error discovering offset manager.
2016-08-05 23:48:32,845 - pykafka.cluster - DEBUG - Retrying offset manager discovery
2016-08-05 23:48:34,880 - pykafka.cluster - ERROR - Error discovering offset manager.
2016-08-05 23:48:34,880 - pykafka.cluster - DEBUG - Retrying offset manager discovery
2016-08-05 23:48:38,889 - pykafka.cluster - ERROR - Error discovering offset manager.
2016-08-05 23:48:38,890 - pykafka.balancedconsumer - ERROR - Stopping consumer in response to error
Traceback (most recent call last):
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/balancedconsumer.py", line 306, in start
self._rebalance()
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/balancedconsumer.py", line 603, in _rebalance
self._update_member_assignment()
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/balancedconsumer.py", line 578, in _update_member_assignment
if self._setup_internal_consumer(new_partitions):
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/balancedconsumer.py", line 359, in _setup_internal_consumer
cns = self._get_internal_consumer(partitions=list(partitions), start=start)
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/balancedconsumer.py", line 417, in _get_internal_consumer
consumer_id=self._consumer_id
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/rdkafka/simple_consumer.py", line 62, in init
super(RdKafkaSimpleConsumer, self).init(**callargs)
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/simpleconsumer.py", line 190, in init
self._discover_group_coordinator()
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/simpleconsumer.py", line 326, in _discover_group_coordinator
self._group_coordinator = self._cluster.get_group_coordinator(self._consumer_group)
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/cluster.py", line 394, in get_group_coordinator
res = future.get(GroupCoordinatorResponse)
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/handlers.py", line 72, in get
return response_cls(self.response)
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/protocol.py", line 929, in init
self.raise_error(error_code, response)
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/protocol.py", line 122, in raise_error
clsname, response))
GroupCoordinatorNotAvailable: Response Type: "GroupCoordinatorResponse"	Response: (15, -1, '', -1)
2016-08-05 23:48:38,891 - pykafka.balancedconsumer - DEBUG - Stopping <pykafka.balancedconsumer.BalancedConsumer at 0x7fc99a29b750 (consumer_group=test_group)>
2016-08-05 23:48:38,895 - pykafka.simpleconsumer - DEBUG - Finalising <pykafka.rdkafka.simple_consumer.RdKafkaSimpleConsumer at 0x7fc99a2cd050 (consumer_group=test_group)>
Traceback (most recent call last):
File "test2.py", line 26, in
for message in balanced_consumer:
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/balancedconsumer.py", line 745, in iter
message = self.consume(block=True)
File "/usr/local/lib64/python2.7/site-packages/pykafka-2.4.1.dev2-py2.7-linux-x86_64.egg/pykafka/balancedconsumer.py", line 734, in consume
raise ConsumerStoppedException
pykafka.exceptions.ConsumerStoppedException
2016-08-05 23:48:39,901 - pykafka.balancedconsumer - DEBUG - Finalising <pykafka.balancedconsumer.BalancedConsumer at 0x7fc99a29b750 (consumer_group=test_group)>
2016-08-05 23:48:39,901 - pykafka.handlers - INFO - RequestHandler.stop: about to flush requests queue
2016-08-05 23:48:39,901 - pykafka.handlers - INFO - RequestHandler.stop: about to flush requests queue
2016-08-05 23:48:39,901 - pykafka.handlers - INFO - RequestHandler.stop: about to flush requests queue
2016-08-05 23:48:39,901 - pykafka.handlers - INFO - RequestHandler.stop: about to flush requests queue

@hxxgy  I encounter the same error.
How did you fix this issue?

thanks for all replies..
I fix this issue by upgrading the version of kafka...
i met this issue when i used version 0.8..
when i upgrade to 1.0, everything is ok
hope useful for any guys..


Push credentials from local to cloud as part of deploy flow

For connectors whose credentials are explicitly specified as part of the connector configuration in the .env file. We would like to push those credentials as part of the project deploy, In order to avoid any errors after the deployment.
The admin would have the option to change the credentials via rill env configure and via admin UI in the future.
This is a subtask of the bigger credential management.

+cc @ericokuma


send_file send png files as photo

The problem
When passing a png file path to send_file method, it sends the file as photo (instead of uncompressed file)
Your environment
Python3.4.3 on Manjaro
Steps to reproduce
Run telegram-cli bin/telegram-cli -k tg-server.pub --json -P 9102 -W --accept-any-tcp
from os import path
from pytg.sender import Sender
s = Sender('localhost', 9102)
s.send_file(u'Hossein_Taleghani', path.abspath('assets/sign.png'))

Expected behaviour
Send file as uncompressed file.
send_document does what I expected
Actual behaviour
Sends file as photo

send_file automatically detects the type as intended. What you are looking for is send_document

Now documented in the DOCUMENTATION.md

Actually it isn't


How you can use external css libraries within flexx?

Question:
Can you use external css libraries such as Materialzie.css in flexx (mainly based on assigning classes to elements to change their appearance)?

Many css frameworks require you to use specific HTML structures, and that in particular is hard to combine with Flexx widgets.

Indeed, it depends on the situation. You can assign css classes to Flexx widgets, and use ui.html for more control, but it might now always work well.

See the new with_bootstrap.py example.


Test Broker Blotter with Serialization

In the current tests I don't believe that we check how a broker blotter would behave (just a zipline blotter). We should have someone who knows that code look it over and also try serializing an algo actually connected to IB before we turn serialization on for any important algos.

@jdricklefs

Think this belongs in our internal bug tracker.


Monster Development

Come up with names, types, skill set, basic flesh out of base stats

Determine how many types there will be and what they will be called. The player can choose a beast sprite, then the types they can choose from depend on what beast sprite they chose. The attacks they can choose from depends on what sprite and type they chose.
Average beast max hp will be about 100 and all incoming attacks will have their damage reduced by the beast's armor value. Base stats will include max hp, armor. Maybe more base stats but beast base stats aren't meant to be the main source of complexity. I think it would be more meaningful for the most complexity to come from things the player controls like the attacks they choose.

Plan to have 10 total beast options. Currently have:
Alzrius - Fire type (close combat)
Auril - Ice type (close combat)
Solanac - Poison type (distance)
Names and types will be further developed as the sprite development occurs. I'm thinking certain beasts will have strengths in distance attacks or close combat attacks.
@noahd15: as these develop, attacks can be created based on these.
Given that time allows I may add sprite sheets to create more animation to beasts for attacks.

Moved to Sprint 2

d7a053f2cb2ffd764f3a6fdd27cf64752d54f18b

f4072b90467658140727d3fba417d74b6f909bef

b1c3e41e93e0423cc3d64c8816993ca8e343387c


There were some Build Errors.

Hi bro~ I run catkin build mav_voxblox_planning ,then I met some errors. And it showed as follows.

Errors     << voxblox:cmake /home/ssz/catkin_ws/mav_voxblox_planning/logs/voxblox/build.cmake.000.log
CMake Error at /home/ssz/catkin_ws/mav_voxblox_planning/devel/share/catkin_simple/cmake/catkin_simple-extras.cmake:38 (find_package):
By not providing "Findprotobuf_catkin.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"protobuf_catkin", but CMake did not find one.
Could not find a package configuration file provided by "protobuf_catkin"
with any of the following names:
protobuf_catkinConfig.cmake
protobuf_catkin-config.cmake

Add the installation prefix of "protobuf_catkin" to CMAKE_PREFIX_PATH or
set "protobuf_catkin_DIR" to a directory containing one of the above files.
If "protobuf_catkin" provides a separate development package or SDK, be
sure it has been installed.
Call Stack (most recent call first):
CMakeLists.txt:5 (catkin_simple)
cd /home/ssz/catkin_ws/mav_voxblox_planning/build/voxblox; catkin build --get-env voxblox | catkin env -si  /usr/bin/cmake /home/ssz/catkin_ws/mav_voxblox_planning/src/voxblox/voxblox --no-warn-unused-cli -DCATKIN_DEVEL_PREFIX=/home/ssz/catkin_ws/mav_voxblox_planning/devel -DCMAKE_INSTALL_PREFIX=/home/ssz/catkin_ws/mav_voxblox_planning/install -DCMAKE_BUILD_TYPE=Release; cd -
...............................................................................
Failed     << voxblox:cmake                                [ Exited with code 1 ]
Failed    <<< voxblox                                      [ 16.0 seconds ]
Abandoned <<< loco_planner                                 [ Unrelated job failed ]
Abandoned <<< mav_planning_rviz                            [ Unrelated job failed ]
Abandoned <<< mav_path_smoothing                           [ Unrelated job failed ]
Abandoned <<< voxblox_rviz_plugin                          [ Unrelated job failed ]
Abandoned <<< voxblox_ros                                  [ Unrelated job failed ]
Abandoned <<< voxblox_planning_common                      [ Unrelated job failed ]
Abandoned <<< voxblox_loco_planner                         [ Unrelated job failed ]
Abandoned <<< mav_local_planner                            [ Unrelated job failed ]
Abandoned <<< voxblox_rrt_planner                          [ Unrelated job failed ]
Abandoned <<< voxblox_skeleton                             [ Unrelated job failed ]
Abandoned <<< voxblox_skeleton_planner                     [ Unrelated job failed ]
Abandoned <<< mav_planning_benchmark                       [ Unrelated job failed ]

Warnings   << mav_planning_common:make /home/ssz/catkin_ws/mav_voxblox_planning/logs/mav_planning_common/build.make.000.log
At the Last of the terminal , it showed :
Finished  <<< ceres_catkin                                 [ 1 minute and 45.4 seconds ]
[build] Summary: 16 of 29 packages succeeded.
[build]   Ignored:   6 packages were skipped or are blacklisted.
[build]   Warnings:  6 packages succeeded with warnings.
[build]   Abandoned: 12 packages were abandoned.
[build]   Failed:    1 packages failed.
[build] Runtime: 2 minutes and 16.6 seconds total.
[build] Note: Workspace packages have changed, please re-source setup files to use them.
So how can I solve this? Any suggestions? Thanks a lot.

cd ~/catkin_ws/src
git clone https://github.com/ethz-asl/protobuf_catkin.git
catkin build protobuf_catkin

This repo does not provide protobuf_catkin. We just need to build it by ourselves.


Ability to setup with rnpm

Amazing work :)
Rnpm will be good dev exp

I used rnpm. Only thing you need to set manually is add the package in MainApplication.java

react-native link works for me on Android.
One thing that breaks is settings.gradle.
Note lib at the end project directory
include ':react-native-mauron85-background-geolocation'
project(':react-native-mauron85-background-geolocation').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-mauron85-background-geolocation/android/lib')

@casoetan answer is correct. If you don't like this manual step please "enable subprojects in native Android Components to enable code reuse with cordova":
Link is in the issue:
https://github.com/mauron85/react-native-background-geolocation/issues/126

Implemented in 0.5x branch


warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.

Description
Got this on the docker contianer after yeserdays update:
warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
$ NODE_ENV=production node dist/index.js
2024-10-16T05:56:48.085Z [info]: Commit Tag: $GIT_SHA
2024-10-16T05:56:48.328Z [info]: Starting Overseerr version 2.0.0
2024-10-16T05:56:48.592Z [info][Notifications]: Registered notification agents
2024-10-16T05:56:48.612Z [info][Jobs]: Scheduled jobs loaded
2024-10-16T05:56:48.672Z [info][Server]: Server ready on port 5055
Since then nothing works except the web interface. I can send a request or change settings. Everything just reports that there is an issue.
Version
2.0.0
Steps to Reproduce
Install update with docker I guess?
Screenshots
No response
Logs
warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
$ NODE_ENV=production node dist/index.js
2024-10-16T05:56:48.085Z [info]: Commit Tag: $GIT_SHA
2024-10-16T05:56:48.328Z [info]: Starting Overseerr version 2.0.0
2024-10-16T05:56:48.592Z [info][Notifications]: Registered notification agents
2024-10-16T05:56:48.612Z [info][Jobs]: Scheduled jobs loaded
2024-10-16T05:56:48.672Z [info][Server]: Server ready on port 5055

Platform
desktop
Device
Dell Notebook
Operating System
Windows 11
Browser
Firefox
Additional Context
No response
Code of Conduct

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

I need the full logs

I need the full logs

those are the full logs after a start of the docker

I need the full logs

I need the full logs

ah sorry you meant from the overseerr.log in the config log folder:
2024-10-16T06:03:27.344Z [info]: Starting Overseerr version 2.0.0
2024-10-16T06:03:27.607Z [info][Notifications]: Registered notification agents
2024-10-16T06:03:27.627Z [info][Jobs]: Scheduled jobs loaded
2024-10-16T06:03:27.686Z [info][Server]: Server ready on port 5055
2024-10-16T06:05:00.010Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Scan
2024-10-16T06:05:00.011Z [info][Jellyfin Sync]: Jellyfin Sync Starting {"sessionId":"918f857b-03ac-4fa3-9820-aac583f14f69"}
2024-10-16T06:05:00.014Z [info][Jellyfin Sync]: Beginning to process recently added for library: redacted
2024-10-16T06:05:04.148Z [info][Jellyfin Sync]: Beginning to process recently added for library: redacted
2024-10-16T06:05:04.155Z [info][Jellyfin Sync]: Beginning to process recently added for library: redacted
2024-10-16T06:05:08.475Z [info][Jellyfin Sync]: Beginning to process recently added for library: redacted
2024-10-16T06:05:12.659Z [info][Jellyfin Sync]: Recently Added Scan Complete

I need the full logs

reverted back to 1.9.2 and this works again. So it is defenitely a change from 2.0

I need the full logs

reverted back to 1.9.2 and this works again. So it is defenitely a change from 2.0

2024-10-16T06:13:03.327Z [info]: Starting Overseerr version 2.0.0
2024-10-16T06:13:03.596Z [info][Notifications]: Registered notification agents
2024-10-16T06:13:03.615Z [info][Jobs]: Scheduled jobs loaded
2024-10-16T06:13:03.674Z [info][Server]: Server ready on port 5055
2024-10-16T06:14:00.032Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-16T06:14:00.098Z [debug][Download Tracker]: Found 2 item(s) in progress on Sonarr server: redacted
2024-10-16T06:14:03.249Z [info]: Commit Tag: $GIT_SHA
2024-10-16T06:14:03.490Z [info]: Starting Overseerr version 2.0.0
2024-10-16T06:14:03.755Z [info][Notifications]: Registered notification agents
2024-10-16T06:14:03.775Z [info][Jobs]: Scheduled jobs loaded
2024-10-16T06:14:03.835Z [info][Server]: Server ready on port 5055
2024-10-16T06:15:00.026Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-16T06:15:00.039Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Scan
2024-10-16T06:15:00.039Z [info][Jellyfin Sync]: Jellyfin Sync Starting {"sessionId":"946ccddc-d1c6-426b-964c-c6f22c834d2c"}
2024-10-16T06:15:00.049Z [info][Jellyfin Sync]: Beginning to process recently added for library: redacted
2024-10-16T06:15:00.128Z [debug][Download Tracker]: Found 2 item(s) in progress on Sonarr server: redacted
2024-10-16T06:15:00.159Z [debug][Jellyfin Sync]: Title already exists and no new media types found Der wilde Roboter
2024-10-16T06:15:00.179Z [debug][Jellyfin Sync]: Title already exists and no new media types found Beetlejuice Beetlejuice
2024-10-16T06:15:00.197Z [debug][Jellyfin Sync]: Title already exists and no new media types found John Wick: Kapitel 3
2024-10-16T06:15:00.202Z [debug][Jellyfin Sync]: Title already exists and no new media types found Alles steht Kopf 2
2024-10-16T06:15:00.207Z [debug][Jellyfin Sync]: Title already exists and no new media types found John Wick
2024-10-16T06:15:00.208Z [debug][Jellyfin Sync]: Title already exists and no new media types found Batman Begins
2024-10-16T06:15:00.209Z [debug][Jellyfin Sync]: Title already exists and no new media types found John Wick: Kapitel 2
2024-10-16T06:15:00.216Z [debug][Jellyfin Sync]: Title already exists and no new media types found Deadpool & Wolverine
2024-10-16T06:15:00.222Z [debug][Jellyfin Sync]: Title already exists and no new media types found The Dark Knight
2024-10-16T06:15:00.223Z [debug][Jellyfin Sync]: Title already exists and no new media types found Transformers: The Last Knight
2024-10-16T06:15:00.224Z [debug][Jellyfin Sync]: Title already exists and no new media types found The Dark Knight Rises
2024-10-16T06:15:00.323Z [debug][Jellyfin Sync]: Title already exists and no new media types found Transformers: Aufstieg der Bestien
2024-10-16T06:15:04.324Z [info][Jellyfin Sync]: Beginning to process recently added for library: redacted redacted
2024-10-16T06:15:04.331Z [info][Jellyfin Sync]: Beginning to process recently added for library: redacted
2024-10-16T06:15:04.411Z [debug][Jellyfin Sync]: Updating existing title: Du gewinnst hier nicht die Million bei Stefan Raab
2024-10-16T06:15:04.423Z [debug][Jellyfin Sync]: Updating existing title: Squid Game
2024-10-16T06:15:04.425Z [debug][Jellyfin Sync]: Updating existing title: Agatha All Along
2024-10-16T06:15:04.428Z [debug][Jellyfin Sync]: Updating existing title: Loki
2024-10-16T06:15:04.434Z [debug][Jellyfin Sync]: Updating existing title: The Penguin
2024-10-16T06:15:04.443Z [debug][Jellyfin Sync]: Updating existing title: The Mandalorian
2024-10-16T06:15:04.444Z [debug][Jellyfin Sync]: Updating existing title: The Lord of the Rings: The Rings of Power
2024-10-16T06:15:04.481Z [debug][Jellyfin Sync]: Updating existing title: White Collar
2024-10-16T06:15:04.517Z [debug][Jellyfin Sync]: Updating existing title: Scrubs
2024-10-16T06:15:08.518Z [info][Jellyfin Sync]: Beginning to process recently added for library: redacted
2024-10-16T06:15:08.601Z [debug][Jellyfin Sync]: Updating existing title: The Strongest Sage With the Weakest Crest
2024-10-16T06:15:08.618Z [debug][Jellyfin Sync]: Updating existing title: Dragon Ball DAIMA
2024-10-16T06:15:08.620Z [debug][Jellyfin Sync]: Updating existing title: Ranma1/2
2024-10-16T06:15:08.620Z [debug][Jellyfin Sync]: Updating existing title: Dragon Ball Super
2024-10-16T06:15:08.650Z [debug][Jellyfin Sync]: Updating existing title: Death Note
2024-10-16T06:15:08.651Z [debug][Jellyfin Sync]: Updating existing title: Shangri-La Frontier
2024-10-16T06:15:08.652Z [debug][Jellyfin Sync]: Updating existing title: Solo Leveling
2024-10-16T06:15:08.664Z [debug][Jellyfin Sync]: Updating existing title: My Hero Academia
2024-10-16T06:15:08.669Z [debug][Jellyfin Sync]: Updating existing title: Jujutsu Kaisen
2024-10-16T06:15:08.671Z [debug][Jellyfin Sync]: Updating existing title: Demon Slayer: Kimetsu no Yaiba
2024-10-16T06:15:12.672Z [info][Jellyfin Sync]: Recently Added Scan Complete
2024-10-16T06:16:00.016Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-16T06:16:00.079Z [debug][Download Tracker]: Found 2 item(s) in progress on Sonarr server: redacted
2024-10-16T06:17:00.033Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-16T06:17:00.070Z [debug][Download Tracker]: Found 2 item(s) in progress on Sonarr server: redacted
2024-10-16T06:18:00.007Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-16T06:18:00.042Z [debug][Download Tracker]: Found 2 item(s) in progress on Sonarr server: redacted
2024-10-16T06:19:00.031Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-16T06:19:00.055Z [debug][Download Tracker]: Found 2 item(s) in progress on Sonarr server: redacted
2024-10-16T06:19:43.801Z [info]: Commit Tag: $GIT_SHA
2024-10-16T06:19:44.008Z [info]: Starting Overseerr version 1.9.2
2024-10-16T06:19:44.467Z [info][Notifications]: Registered notification agents
2024-10-16T06:19:44.484Z [info][Jobs]: Scheduled jobs loaded
2024-10-16T06:19:44.548Z [info][Server]: Server ready on port 5055
2024-10-16T06:19:52.924Z [debug][API]: User push subscription already exists. Skipping registration.
2024-10-16T06:19:55.930Z [debug][API]: User push subscription already exists. Skipping registration.
2024-10-16T06:19:59.771Z [debug][Notifications]: Sending email notification {"recipient":"Active7803","type":"TEST_NOTIFICATION","subject":"Test Notification"}
2024-10-16T06:20:00.006Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-16T06:20:00.011Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Scan
2024-10-16T06:20:00.016Z [debug][Download Tracker]: Found 2 item(s) in progress on Sonarr server: redacted
2024-10-16T06:21:00.008Z [debug][Jobs]: Starting scheduled job: Download Sync
2024-10-16T06:21:00.017Z [debug][Download Tracker]: Found 2 item(s) in progress on Sonarr server: redacted

I need the full logs

reverted back to 1.9.2 and this works again. So it is defenitely a change from 2.0

That is not a good idea...
2.0.0 is not designed to be backportable...
Can you try with a fresh config and see if it still works

I need the full logs

reverted back to 1.9.2 and this works again. So it is defenitely a change from 2.0

That is not a good idea... 2.0.0 is not designed to be backportable...
Can you try with a fresh config and see if it still works

I cant even login to the emby server:

log from docker:
2024-10-16 06:45:12
yarn run v1.22.22
2024-10-16 06:45:12
warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
2024-10-16 06:45:12
$ NODE_ENV=production node dist/index.js
2024-10-16 06:45:13
2024-10-16T06:45:13.483Z [info]: Commit Tag: $GIT_SHA
2024-10-16 06:45:13
2024-10-16T06:45:13.723Z [info]: Starting Overseerr version 2.0.0
2024-10-16 06:45:14
2024-10-16T06:45:14.010Z [info][Notifications]: Registered notification agents
2024-10-16 06:45:14
2024-10-16T06:45:14.015Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet
2024-10-16 06:45:14
2024-10-16T06:45:14.077Z [info][Server]: Server ready on port 5055

and log from the overseerr.log
2024-10-16T06:45:03.331Z [info]: Commit Tag: $GIT_SHA
2024-10-16T06:45:03.528Z [info]: Starting Overseerr version 1.9.2
2024-10-16T06:45:04.151Z [info][Notifications]: Registered notification agents
2024-10-16T06:45:04.156Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet
2024-10-16T06:45:04.159Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":1,"enabled":true,"isBuiltIn":true,"order":0}}
2024-10-16T06:45:04.173Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":2,"enabled":true,"isBuiltIn":true,"order":1}}
2024-10-16T06:45:04.184Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":3,"enabled":true,"isBuiltIn":true,"order":2}}
2024-10-16T06:45:04.195Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":4,"enabled":true,"isBuiltIn":true,"order":3}}
2024-10-16T06:45:04.208Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":5,"enabled":true,"isBuiltIn":true,"order":4}}
2024-10-16T06:45:04.221Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":6,"enabled":true,"isBuiltIn":true,"order":5}}
2024-10-16T06:45:04.235Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":7,"enabled":true,"isBuiltIn":true,"order":6}}
2024-10-16T06:45:04.249Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":8,"enabled":true,"isBuiltIn":true,"order":7}}
2024-10-16T06:45:04.262Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":9,"enabled":true,"isBuiltIn":true,"order":8}}
2024-10-16T06:45:04.278Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":10,"enabled":true,"isBuiltIn":true,"order":9}}
2024-10-16T06:45:04.293Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":11,"enabled":true,"isBuiltIn":true,"order":10}}
2024-10-16T06:45:04.307Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":12,"enabled":true,"isBuiltIn":true,"order":11}}
2024-10-16T06:45:04.385Z [info][Server]: Server ready on port 5055
2024-10-16T06:45:13.483Z [info]: Commit Tag: $GIT_SHA
2024-10-16T06:45:13.723Z [info]: Starting Overseerr version 2.0.0
2024-10-16T06:45:14.010Z [info][Notifications]: Registered notification agents
2024-10-16T06:45:14.015Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet
2024-10-16T06:45:14.077Z [info][Server]: Server ready on port 5055

I need the full logs

reverted back to 1.9.2 and this works again. So it is defenitely a change from 2.0

That is not a good idea... 2.0.0 is not designed to be backportable...
Can you try with a fresh config and see if it still works

I cant even login to the emby server:

Tried to ping the emby server from inside the jellyseerr container which works fine.
log from docker:
2024-10-16 06:45:12
yarn run v1.22.22
2024-10-16 06:45:12
warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
2024-10-16 06:45:12
$ NODE_ENV=production node dist/index.js
2024-10-16 06:45:13
2024-10-16T06:45:13.483Z [info]: Commit Tag: $GIT_SHA
2024-10-16 06:45:13
2024-10-16T06:45:13.723Z [info]: Starting Overseerr version 2.0.0
2024-10-16 06:45:14
2024-10-16T06:45:14.010Z [info][Notifications]: Registered notification agents
2024-10-16 06:45:14
2024-10-16T06:45:14.015Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet
2024-10-16 06:45:14
2024-10-16T06:45:14.077Z [info][Server]: Server ready on port 5055

and log from the overseerr.log
2024-10-16T06:45:03.331Z [info]: Commit Tag: $GIT_SHA
2024-10-16T06:45:03.528Z [info]: Starting Overseerr version 1.9.2
2024-10-16T06:45:04.151Z [info][Notifications]: Registered notification agents
2024-10-16T06:45:04.156Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet
2024-10-16T06:45:04.159Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":1,"enabled":true,"isBuiltIn":true,"order":0}}
2024-10-16T06:45:04.173Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":2,"enabled":true,"isBuiltIn":true,"order":1}}
2024-10-16T06:45:04.184Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":3,"enabled":true,"isBuiltIn":true,"order":2}}
2024-10-16T06:45:04.195Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":4,"enabled":true,"isBuiltIn":true,"order":3}}
2024-10-16T06:45:04.208Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":5,"enabled":true,"isBuiltIn":true,"order":4}}
2024-10-16T06:45:04.221Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":6,"enabled":true,"isBuiltIn":true,"order":5}}
2024-10-16T06:45:04.235Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":7,"enabled":true,"isBuiltIn":true,"order":6}}
2024-10-16T06:45:04.249Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":8,"enabled":true,"isBuiltIn":true,"order":7}}
2024-10-16T06:45:04.262Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":9,"enabled":true,"isBuiltIn":true,"order":8}}
2024-10-16T06:45:04.278Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":10,"enabled":true,"isBuiltIn":true,"order":9}}
2024-10-16T06:45:04.293Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":11,"enabled":true,"isBuiltIn":true,"order":10}}
2024-10-16T06:45:04.307Z [info][Discover Slider]: Creating built-in discovery slider {"slider":{"type":12,"enabled":true,"isBuiltIn":true,"order":11}}
2024-10-16T06:45:04.385Z [info][Server]: Server ready on port 5055
2024-10-16T06:45:13.483Z [info]: Commit Tag: $GIT_SHA
2024-10-16T06:45:13.723Z [info]: Starting Overseerr version 2.0.0
2024-10-16T06:45:14.010Z [info][Notifications]: Registered notification agents
2024-10-16T06:45:14.015Z [info][Server]: Skipping starting the scheduled jobs as we have no Plex/Jellyfin/Emby servers setup yet
2024-10-16T06:45:14.077Z [info][Server]: Server ready on port 5055

ok got it working again with 2.0 but had to redo the config volume twice and setup jellyseerr completely new.
It is working again but this sucks if you have to delete everything for this update to work and the warning with pnpm is still there?

You don't have to delete everything for this update. Everyone updated normally including me. There must be an issue with your config folder. (Always backup and we could try recovering it but you'll have to hop onto discord for it)

You don't have to delete everything for this update. Everyone updated normally including me. There must be an issue with your config folder. (Always backup and we could try recovering it but you'll have to hop onto discord for it)
Always. Always. Backup before updating. That's a known rule. If backed up before we can easily recover the data.
Not just for jellyseerr. Emby, jellyfin any. Especially with big major update like going from 1.0 to 2.0

Yeah I know that got a container in place to backup my docker volumes every day. This was my first time that a container that I used actually broke. Dunno what could be wrong with the config folder. But everything is back now.


Implement Google Authentication. Merge conflicts with master.

Also updated name of controller being imported into routes to be less confusing with model name.

@drewctate @mountain01 @sttracy4 @gshigeto I know the build is failing, it has to do with the .env file that is not committed for obvious reasons. I'm working on a solution for that. For now, go through the changes, ask questions, comment, approve etc.

👍

Making a few updates to this pull request, I'll comment again when I need review.

@gshigeto @drewctate @mountain01 @sttracy4 It is now ready to be fully code reviewed!!!

👍 It looks good to me


chore: Enable codeql action

This action runs GitHub's industry-leading semantic code analysis engine,
CodeQL, against a repository's source code to find security vulnerabilities.
https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql
https://github.com/ossf/scorecard/blob/main/docs/checks.md#sast
Signed-off-by: naveen<EMAIL_ADDRESS>

I think this looks good, but I think it would be a good idea to have @jmrodri or @asmacdo to take a look at this as well before merging

A friendly ping

What is the plan for dealing with this action? Are we going to fail PRs because of them? Are we going to maintain these?
I like the idea but not sure if I want to maintain these long term. Do we have a report of the output to see how bad we are right now?

What is the plan for dealing with this action? Are we going to fail PRs because of them? Are we going to maintain these?
I like the idea but not sure if I want to maintain these long term. Do we have a report of the output to see how bad we are right now?

@jmrodri I think we can make it so that the check won't fail PRs. I'm not sure how much maintenance this action would need on our end. I personally think just having the reports to look at would be good, even if we don't fail PRs on it. I am working on generating a report on my fork to see how it says we are now.

What is the plan for dealing with this action? Are we going to fail PRs because of them? Are we going to maintain these?
I like the idea but not sure if I want to maintain these long term. Do we have a report of the output to see how bad we are right now?

@jmrodri I think we can make it so that the check won't fail PRs. I'm not sure how much maintenance this action would need on our end. I personally think just having the reports to look at would be good, even if we don't fail PRs on it. I am working on generating a report on my fork to see how it says we are now.

👍

Here is the current report that I was able to get from the CodeQL scan on my fork:
https://github.com/everettraven/operator-sdk/security/code-scanning
Looks pretty clean from what I can tell


Color mode: proposal to handle color mode for components

Description
Add some cases to color-mode mixin in order to allow using on each component.
The proposed solution is maybe far from ideal but before going deeper, I'd like to have some feedback on something like this.
Not quite sure it's breaking since it might be an internal mixin.
Motivation & Context
Be able to introduce the use of data-bs-theme=dark on every component (Not implemented in this PR apart the one already implemented).
Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[x] Breaking change (fix or feature that would change existing functionality)

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[x] I have updated the documentation accordingly
(NA) I have added tests to cover my changes
[x] All new and existing tests passed

Live previews

https://deploy-preview-38917--twbs-bootstrap.netlify.app/docs/5.3/components/accordion
https://deploy-preview-38917--twbs-bootstrap.netlify.app/docs/5.3/components/carousel
https://deploy-preview-38917--twbs-bootstrap.netlify.app/docs/5.3/components/close-button
https://deploy-preview-38917--twbs-bootstrap.netlify.app/docs/5.3/components/navbar
https://deploy-preview-38917--twbs-bootstrap.netlify.app/docs/5.3/forms/checks-radios#switches
https://deploy-preview-38917--twbs-bootstrap.netlify.app/docs/5.3/forms/select

and some docs.
Related issues
Might close or help on #38853.
Might superseed #38807.

Might close or help on https://github.com/twbs/bootstrap/issues/38853.

It appears to fix #38853


ton: 2024.08 -> 2024.09

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for ton is: Fully decentralized layer-1 blockchain designed by Telegram
meta.homepage for ton is: https://ton.org/
meta.changelog for ton is: https://github.com/ton-blockchain/ton/blob/v2024.09/Changelog.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.09 in filename of file in /nix/store/k03xms9fkcg8jppfbxxhpg81iaxz2n5g-ton-2024.09

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

ton

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k03xms9fkcg8jppfbxxhpg81iaxz2n5g-ton-2024.09 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ton https://github.com/r-ryantm/nixpkgs/archive/5d0e7f1e3b954d5c6ca0ba40013b694945f82728.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5d0e7f1e3b954d5c6ca0ba40013b694945f82728#ton

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/k03xms9fkcg8jppfbxxhpg81iaxz2n5g-ton-2024.09
ls -la /nix/store/k03xms9fkcg8jppfbxxhpg81iaxz2n5g-ton-2024.09/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

ton
ton.dev

Maintainer pings
cc @misuzu for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 343795 run on aarch64-darwin 1

2 packages marked as broken and skipped:

ton
ton.dev