Video rag

This is an open source implementation of video rag app
Accompanying blog https://ploomber.io/blog/rag-video-app/
Please refer to README for instructions
This PR contains the complete pipeline and app and assumes an ElasticSearch instance (local or cloud based)

📚 Documentation preview 📚: https://ploomber-doc--63.org.readthedocs.build/en/63/

Readme with instructions
https://github.com/ploomber/doc/tree/video-rag/examples/docker/video-rag


Feature: Migrate Project Partials to View Components

Is your feature request related to a problem? Please describe
Currently the Project Partial for edit (_form.html.erb), delete (_delete_project_confirmation_modal.html.erb), add and delete collaboration (_add_collaborator_modal.html and _delete_collaboration_confirmation_modal.html) are being rendered as standard partial.
Edit Form

Delete Modal

Add Modal

Describe the solution you'd like
we can convert them to View Components for better performance, and write tests for them.
Describe alternatives you've considered
No response
Additional context
No response
Are you working on this?
Yes

Check out issue #4330

@deepak05kr18 it is a seperate issue for fixing the ui of email box, this issue is for migrating the components from partial to View Component to follow Rails approach of classes and improve the performance

Hi @senbo1 , can you raise 3 separate PRs for that. Then it will be easy to track !
You have been assigned !

sure @tanmoysrt

actually this is not completed yet @tanmoysrt

actually this is not completed yet @tanmoysrt , some partials are remaining, I will make the PRs in the next week because my endsems are going right now

I have only verified the modal portion.
Should I revert this or the changes will


fix: Only enable ublue-update on F39 builds

Gives us time to telegraph needed supporting changes downstream.

Okay, happy with that now.


Dart define no longer working as expected after upgrading to Flutter 2.2.0

Hello, just had a problem running a flutter project which appends postfix to applicationId in build.gradle in flutter 2.2. It works fine in flutter 2.0.6 and previous, using dart define. After reading it, I think it's related to https://github.com/flutter/flutter/pull/75027 but not sure what exactly or how to make it work.
Update: Turns out the problem is there on dart 2.12.3++. It works fine in 2.12.0. Any idea why?
Problem description
Inside android/app/build.gradle
def dartEnvironmentVariables = [
    DART_DEFINE_APP_NAME: 'BackOffice',
    DART_DEFINE_APP_SUFFIX: null
];
if (project.hasProperty('dart-defines')) {
    dartEnvironmentVariables = dartEnvironmentVariables + project.property('dart-defines')
        .split(',')
        .collectEntries { entry ->
            def pair = URLDecoder.decode(entry).split('=')
            [(pair.first()): pair.last()]
        }
}
...
android {
   ...
    defaultConfig {
        ...
        applicationIdSuffix dartEnvironmentVariables.DART_DEFINE_APP_SUFFIX
        resValue "string", "app_name", dartEnvironmentVariables.DART_DEFINE_APP_NAME
        ...
    }
    ...
}

Run using .vscode/launch.json
{
  ...
  "configurations": [
        {
      "name": "back office dev",
      "cwd": "apps/back_office",
      "request": "launch",
      "program": "lib/main_dev.dart",
      "type": "dart",
      "args": [
        "--dart-define=DART_DEFINE_APP_NAME=dev-BackOffice",
        "--dart-define=DART_DEFINE_APP_SUFFIX=.dev",
      ]
    },
  ]
}

Error

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugGoogleServices'.
No matching client found for package name 'com.myapp.myapp'

Flutter Doctor -v
[✓] Flutter (Channel unknown, 2.2.0, on macOS 11.3.1 20E241 darwin-x64, locale en-ID)
    • Flutter version 2.2.0 at /Users/moseskarunia/fvm/versions/2.2.0
    • Framework revision b22742018b (6 days ago), 2021-05-14 19:12:57 -0700
    • Engine revision a9d88a4d18
    • Dart version 2.13.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/moseskarunia/Development/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /Users/moseskarunia/Development/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5, Build version 12E262
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.56.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.22.0

[✓] Connected device (2 available)
    • // truncated
    • // truncated

• No issues found!

Hi @moseskarunia
This is a duplicate of https://github.com/flutter/flutter/issues/82865, see https://github.com/flutter/flutter/issues/82865#issuecomment-844222972
Closing as duplicate
Thank you


pkg_resources error in django-widget-tweaks after upgrading to Python 3.12 on my distro (Fedora 39)

This issue is with Python 3.12 and I suggest it should be fixed in no time because some projects using django-widget-tweaks are broken after system upgrade (Fedora 39). I guess all other distros that switched to Python 3.12 are having this issue as well.
Error:
venv/lib/python3.12/site-packages/widget_tweaks/init.py", line 1, in
from pkg_resources import get_distribution, DistributionNotFound
ModuleNotFoundError: No module named 'pkg_resources'
Where pkg_resources is called:
"venv/lib/python3.12/site-packages/widget_tweaks/init.py"
from pkg_resources import get_distribution, DistributionNotFound
try:
version = get_distribution("django-widget-tweaks").version
except DistributionNotFound:
# package is not installed
version = None

Looks like in 3.12 pkg_resources is not installed by default:

easy_install, pkg_resources, setuptools and distutils are no longer provided by default in environments created with venv or bootstrapped with ensurepip, since they are part of the setuptools package. For projects relying on these at runtime, the setuptools project should be declared as a dependency and installed separately (typically, using pip).

Al

Looks like in 3.12 pkg_resources is not installed by default:

easy_install, pkg_resources, setuptools and distutils are no longer provided by default in environments created with venv or bootstrapped with ensurepip, since they are part of the setuptools package. For projects relying on these at runtime, the setuptools project should be declared as a dependency and installed separately (typically, using pip).

Looks like this was fixed in #135 and released in 1.5.0. What version of django-widget-tweaks are you using?

Alright I am currently using  django-widget-tweaks==1.5.0


CiderCollective.Cider.Nightly version 1.3.1325

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

last commit with different url, next commit will be using dl.circleci.com

Hi, may i ask what is missing from my commit to be merged into winget?

Hi, may i ask what is missing from my commit to be merged into winget?

Nothing.
Azure Pipelines are currently limited to 20 PRs per run due to 800+ PRs being opened.


Question about auto detect encoding

My database's charset is UTF8MB4, when I use OHMySQL to connect to the database, it says:
[INFO] New character set: utf8
It seems that it can't tell the difference between different 'kinds' of UTF-8? I get error when try to insert or update emoji into the database. If I manually executeSET NAMES UTF8MB4 after connected to the database, it will work properly.
It's really a tough task to write an SQL driver😂

Hmm... Looks like on UTF-8MB4 is MySQL-specific encoding and iOS can still use UTF-8.
I will add this encoding to the enum CharsetEncoding.
Thanks for reporting ;]

Hi there,
Take a look at release 1.0.2.


Numpy - Accessing and Changing Elements, Rows, Columns

Describe your problem and how to reproduce it:
The output does not align with the question, nor does it align with the code. I suspect this is what the output was meant to be:
# Output:
# [[ 1  2  20  4  5 ]
# [ 6  7  20  9 10 ]]

Also, I would suggest the formatting of the code to change. Ie. spacing between numbers and [], and spacing between numbers.
Add a Link to the page with the problem:
https://www.freecodecamp.dev/learn/data-analysis-with-python/numpy/accessing-and-changing-elements-rows-columns
If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

Thanks for catching this @Sky020.
I remember copying the output directly from the repl.it console, but I must have messed up the spacing while adding the hashes. Took another look and this is what the console outputs:
[[ 1  2  3  4  5]
 [ 6  7  8  9 10]]

So perhaps it can be:
# Output:
# [[ 1  2  3  4  5]
#  [ 6  7  8  9 10]]

Or with the spacing at the end like you suggest:
# Output:
# [[ 1  2  3  4  5 ]
#  [ 6  7  8  9 10 ]]

@scissorsneedfoodtoo , well. What was your intent? I assumed the output was there as an example for what the end result should become. Ie. after performing:
a[:, 2] = 20

Or, was the output just another representation of the output of the np.array?
I suggest it be the expected output of the code the user needs to select, as this helps the user clarify what needs to be done.

@Sky020, right, my intent was to show what the expected end result would be after running a[:, 2] = 20. So really the output should be
[[ 1  2 20  4  5]
 [ 6  7 20  9 10]]

not
[[ 1  2  3  4  5]
 [ 6  7 20  9 10]]

like it is now. My mistake. I must have forgotten to change the output when I was writing these questions.

Is someone working on this? Can I work on this?

@niteshseram , I am unsure of anyone working on this. You can go ahead, if you want.

Okay. I will be working on it.


LSP snippets incorrectly expanded

Not sure if this is from nvim-cmp or nvim-cmp-lsp, but when using emmet-ls with nvim-cmp, it give the output as in the screenshot.
Autocompletion suggestions

Once select the suggestion

I also notice that on the emmet-ls repository, there seems to be an issue for compe support.
And here's my LSP setup, part of it is under my setup framework

My autocompletion setup: spywhere/dotfiles

I'll do a full test again later today. But from what I have tried so far, it's seems like working now. Feel free to close the issue if you needed. I'll get back on this later. Thanks for the fix!

@spywhere I'm still facing this issue but idk if it's a emmet-ls problem
From the example you show table>tr*3 I get this:

But those ${1} ${2} ${3} are just plain text, they are not jumpable snippets, If they are not jumpable it would be better to generate the emmets empty, are you getting the same?

It's emmet-ls side problem.

Also getting some unexpected behavior using rust-analyzer

@sharksforarms are you on the latest commit? I can't replicate this. This looks like the behavior before the fix maybe?

The emmet-ls has a problem.
The problem is that is not set insertTextFormat = InsertTextFormat.Snippet to the completion items.
So you will see ${0} as literal string.
I don't know why the server is setting insertTextFormat when the completion item resolved.
https://github.com/aca/emmet-ls/blob/master/src/server.ts#L121
I think it should be moved to here

Sorry for a long reply, been busy this weekend so I don't have a chance at my computer til now.
Just finish testing it, here's my result...
The selection is better but still off, as it seems to expanded the snippet then truncate to only the first line.
But once selected, it get expanded correctly.
For the issue about jumping points, mine seems fine so far.
Autocomplete suggestions

Once select the suggestions

And once it's expanded

@spywhere What did you do since the first comment? How do you solve the jumping points problem?

@spywhere What did you do since the first comment? How do you solve the jumping points problem?

I did nothing to my setup, only plugin update. You can check out my setup on the original description above.
I am using LuaSnip for the snippet engine though, if that would help...

@sharksforarms are you on the latest commit? I can't replicate this. This looks like the behavior before the fix maybe?

Latest rust-analyzer and latest nvim-cmp, here's a smaller example

@sharksforarms Reproduced. And it is nvim-cmp's bug. Thank you for your report.
This issue is very insightful to me! Thank you for all!

I've fixed it~! Thank you~!

Confirmed fixed!
One thing I noticed, is the first character of the snippet expanded on selection? For example, I expected the '#' to come after I select it using  and it's rendered in a single chunk, instead I need to undo twice, is this intended or a bug?

It is a intended behavior... (In this case, I don't like this behavior but so)

But Probably we can improve the undo point management.

Good to know! Thanks for your work!

So far I think the only thing left here is when hover the selection, text on the buffer get changed.
Take a look in this video, you'll see that the code kept changing from the original text (table>tr*3>td*4) to expanded one (<table>).
https://user-images.githubusercontent.com/1087399/131257954-14515f45-2383-429b-a577-ca446203c6af.mov
All and all, the issue is minor to me. I can live with that. Let me know if want to turn this into a new issue, so we can close this one.

The temporary inserted text (I call it as so) is the most complex thing if we implement the LSP completion plugin in vim.

I think let's close this issue, since the original request was to fix the snippet expansion is now fixed. I'll open a new one just for this temporary inserted text then. Thanks for the swift fix and reply @hrsh7th! 😄

@hrsh7th look at that video, I tried and it's the same for me.
If I use the auto-select feature it output the plain text ${1} ${2} ...
But if I manually select the item it works perfect, with the jumpable points

The emmet-ls has a problem. I can't fix it in nvim-cmp.

Sorry
:'(

I created a better emmet language server solving all bugs. here is the repo


User getting annoyed by many "already seen" and "finished" banners

This is really just a follow on to #1640, but it seems like it is not an occasional problem, at least for some users, but rather a common one.
https://www.zooniverse.org/projects/kosmala/season-spotter-questions/talk/62/39930

It's high on our list @mkosmala see #1676

Super!

closing this in favour of #1640


Mines

Hi, I've been looking for a long time for where I can play the Mines slot in India? Maybe someone can tell me?

I had heard good things about the 1win platform, so I decided to check it out via https://mines.com.in/1win. I jumped straight into the Mines game, and it didn’t disappoint. The fast-paced action and strategic gameplay made it incredibly enjoyable. As a player in India, the platform runs seamlessly, and I’ve had a lot of fun exploring it. Definitely worth a try if you enjoy slots with a twist!


Sylvania support

Hi, do you have any idea of what is the platform name for Sylvania Smart WIFI bulbs? The official app connects to tuya.com so I'm guessing it can be compatible with this plugin using the correct platform name. I've tried guessing it with no luck.

I am afraid that app is not supported by the API this plugin is using.
This however does not mean that you cannot use your devices with this plugin!
Please use one of the supported apps (Tuya, Smartlife, Jinvoo Smart) and add your devices there, if they are Tuya-compatible it shouldn't matter which app you are using. Once you have created an account for one of these apps and added your devices to that app/account, you should be able to use this plugin.
I understand that this seems stupid, having to move all your devices to a different app, but this is a limitation by Tuya, this is not something we can change.


Design improvements in dictionary.html page

search word and buttons are not spaced properly i would like to improve the look

I would like to work on this.

i would request you to assign it to me as a part of hacktoberfest contributions

Go ahead @Phoenix-031!

Don't forget to star the repository! @Phoenix-031


Add Build Readme

Build Readme should be built in as a part of the workflow.

After much trial and error, I was unable to get these two CLI tools to play nice with each other. The main problem is both CLI prompt would fire at the same time so that two questions were always asked together and a single answer would count towards two separate questions from each package. Even after waiting for v1.2.0 to come out for Build Readme with broken out functions, this still did not work. Abandoning this for now.


Unable to use RBAC

changed Postgres server details in entrypoint.sh to an RDS in AWS
removed postgres service from  LocalExecutor .yml and used that to bring up webserver
all tables are getting created in postgres backend and UI is asking for login
Once I run airflow create_user -r Admin -u test -e<EMAIL_ADDRESS>-f test -l test -p test log is showing using SequentialExecutor instead of LocalExecutor
airflow@ac85221fed9f:~$ airflow create_user -r Admin -u test -e<EMAIL_ADDRESS>-f test -l test -p test
[2019-04-10 07:21:44,605] {{init.py:51}} INFO - Using executor SequentialExecutor
[2019-04-10 07:21:44,847] {{cli_action_loggers.py:69}} ERROR - Failed on pre-execution callback using <function default_action_log at 0x7f5b566910d0>
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1236, in _execute_context
cursor, statement, parameters, context
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 536, in do_execute
cursor.execute(statement, parameters)
sqlite3.OperationalError: no such table: log
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/airflow/utils/cli_action_loggers.py", line 67, in on_pre_execution
cb(**kwargs)
File "/usr/local/lib/python3.6/site-packages/airflow/utils/cli_action_loggers.py", line 98, in default_action_log
session.add(log)
File "/usr/local/lib/python3.6/contextlib.py", line 88, in exit
next(self.gen)
File "/usr/local/lib/python3.6/site-packages/airflow/utils/db.py", line 44, in create_session
session.commit()
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1023, in commit
self.transaction.commit()
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 487, in commit
self._prepare_impl()
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 466, in _prepare_impl
self.session.flush()
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 2446, in flush
self._flush(objects)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 2584, in _flush
transaction.rollback(_capture_exception=True)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 67, in exit
compat.reraise(exc_type, exc_value, exc_tb)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 277, in reraise
raise value
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 2544, in _flush
flush_context.execute()
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/unitofwork.py", line 416, in execute
rec.execute(self)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/unitofwork.py", line 583, in execute
uow,
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 245, in save_obj
insert,
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1116, in _emit_insert_statements
statement, params
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 980, in execute
return meth(self, multiparams, params)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 273, in _execute_on_connection
return connection._execute_clauseelement(self, multiparams, params)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1099, in _execute_clauseelement
distilled_params,
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1240, in _execute_context
e, statement, parameters, cursor, context
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1458, in _handle_dbapi_exception
util.raise_from_cause(sqlalchemy_exception, exc_info)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 296, in raise_from_cause
reraise(type(exception), exception, tb=exc_tb, cause=cause)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 276, in reraise
raise value.with_traceback(tb)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1236, in _execute_context
cursor, statement, parameters, context
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 536, in do_execute
cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such table: log [SQL: 'INSERT INTO log (dttm, dag_id, task_id, event, execution_date, owner, extra) VALUES (?, ?, ?, ?, ?, ?, ?)'] [parameters: ('2019-04-10 07:21:44.843311', None, None, 'cli_create_user', None, 'airflow', '{"host_name": "ac85221fed9f", "full_command": "['/usr/local/bin/airflow', 'create_user', '-r', 'Admin', '-u', 'test', '-e'<EMAIL_ADDRESS>'-f', 'test', '-l', 'test', '-p', 'test']"}')] (Background on this error at: http://sqlalche.me/e/e3q8)
[2019-04-10 07:21:44,984] {{manager.py:525}} WARNING - No user yet created, use fabmanager command to do it.
[2019-04-10 07:21:46,055] {{models.py:273}} INFO - Filling up the DagBag from /usr/local/airflow/dags
[2019-04-10 07:21:48,279] {{security.py:437}} INFO - Start syncing user roles.
[2019-04-10 07:21:48,331] {{security.py:186}} INFO - Initializing permissions for role:Viewer in the database.
[2019-04-10 07:21:48,504] {{security.py:186}} INFO - Initializing permissions for role:User in the database.
[2019-04-10 07:21:48,680] {{security.py:186}} INFO - Initializing permissions for role:Op in the database.
[2019-04-10 07:21:48,809] {{security.py:346}} INFO - Fetching a set of all permission, view_menu from FAB meta-table
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1236, in _execute_context
cursor, statement, parameters, context
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 536, in do_execute
cursor.execute(statement, parameters)
sqlite3.OperationalError: no such table: dag
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/bin/airflow", line 32, in
args.func(args)
File "/usr/local/lib/python3.6/site-packages/airflow/utils/cli.py", line 74, in wrapper
return f(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/airflow/bin/cli.py", line 1341, in create_user
appbuilder = cached_appbuilder()
File "/usr/local/lib/python3.6/site-packages/airflow/www_rbac/app.py", line 214, in cached_appbuilder
cached_app(config, testing)
File "/usr/local/lib/python3.6/site-packages/airflow/www_rbac/app.py", line 207, in cached_app
app, _ = create_app(config, session, testing)
File "/usr/local/lib/python3.6/site-packages/airflow/www_rbac/app.py", line 167, in create_app
security_manager.sync_roles()
File "/usr/local/lib/python3.6/site-packages/airflow/www_rbac/security.py", line 445, in sync_roles
self.create_custom_dag_permission_view()
File "/usr/local/lib/python3.6/site-packages/airflow/utils/db.py", line 73, in wrapper
return func(*args, **kwargs)
File "/usr/local/lib/python3.6/site-packages/airflow/www_rbac/security.py", line 366, in create_custom_dag_permission_view
.filter(~models.DagModel.is_subdag).all()
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 2925, in all
return list(self)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3081, in iter
return self._execute_and_instances(context)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3106, in _execute_and_instances
result = conn.execute(querycontext.statement, self._params)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 980, in execute
return meth(self, multiparams, params)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 273, in _execute_on_connection
return connection._execute_clauseelement(self, multiparams, params)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1099, in _execute_clauseelement
distilled_params,
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1240, in _execute_context
e, statement, parameters, cursor, context
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1458, in _handle_dbapi_exception
util.raise_from_cause(sqlalchemy_exception, exc_info)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 296, in raise_from_cause
reraise(type(exception), exception, tb=exc_tb, cause=cause)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 276, in reraise
raise value.with_traceback(tb)
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1236, in _execute_context
cursor, statement, parameters, context
File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 536, in do_execute
cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such table: dag [SQL: 'SELECT dag.dag_id AS dag_dag_id, dag.is_paused AS dag_is_paused, dag.is_subdag AS dag_is_subdag, dag.is_active AS dag_is_active, dag.last_scheduler_run AS dag_last_scheduler_run, dag.last_pickled AS dag_last_pickled, dag.last_expired AS dag_last_expired, dag.scheduler_lock AS dag_scheduler_lock, dag.pickle_id AS dag_pickle_id, dag.fileloc AS dag_fileloc, dag.owners AS dag_owners \nFROM dag \nWHERE (dag.is_active = 1 OR dag.is_paused = 1) AND dag.is_subdag = 0'] (Background on this error at: http://sqlalche.me/e/e3q8)

FIXED
to run airflow create_user or any other airflow command, open bash as
docker exec -it <container_name> /entrypoint.sh bash

@siddardha7 saved my day, thank you! For anyone running airflow helm chart on k8s, run airflow create_user after opening bash as kubectl exec -it <pod_name> /entrypoint.sh bash


Grub points the wrong way when walking into a wall

Walk into a wall, notice that the grub is facing the wrong way.
This is related to either component ordering, the order at which components are created, etc.

https://github.com/apetavern/sbox-grubs/pull/172


Add an overload to Shape method in DisplayDriverBase

This allow DisplayDriver to return strongly type shape without knowing the exact type when in development.
Basically just exposing the same ShapeFactory.Create here. https://github.com/OrchardCMS/Orchard2/blob/master/src/OrchardCore/Orchard.DisplayManagement/IShapeFactory.cs#L89

@awyl,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


Update ITK

We are currently using ITK 4.9 and ITK will soon release 4.12 (May 24th).
I already did the update to 4.11 on my computer and it requires a handful of changes.
We can wait for the next release to do the update.

Interesting. I upgraded my xubuntu to 17.04, and found that bug http://vtk.1045678.n5.nabble.com/Problem-with-building-VTK-td5742905.html
It means that our current version of VTK will soon need to be upgraded too if we can't compile it with new versions of linux (and maybe of other OS?).

I managed to solve the Ubuntu 17.04 compilation problem:
1° (boost library was missing, just need to re-install it through apt-get or aptitude)
2° (i needed to add LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/mathildemerle/Dev/medinria-superproject/build/DCMTK/install/lib and export LD_LIBRARY_PATH )
3° the main solution is in VTK file vtkCompilerExtras.cmake:
line 26: exec_program(${CMAKE_C_COMPILER} --version OUTPUT_VARIABLE
line 28: string (REGEX MATCH "[3-9]\\.[0-9]\\.[0-9]"
these changes are done in the last versions of VTK.

This issue was about ITK, but ok good to know :)


[BUG] Offerings > VPC offerings - not human-readable service capabilities

Describe the bug
The service capabilities description is not really human-readable in "Offerings > VPC offerings" - it's just a JSON object.
To Reproduce
Steps to reproduce the behavior:

Go to 'Offerings > VPC offerings' and click on a VPC offering. Look at the 'service' label.

Expected behavior
The information about the service capabilities should be easy to understand.
Screenshots

Desktop (please complete the following information):

OS: Linux Ubuntu 18.04 LTS
Browser: Chrome
Version: 80.0.3987.116 (Official Build) (64-bit)

Additional context
None.

Fixed in master now please re-test and close @vladimirpetrov

Fix confirmed, closing the issue.


Guanchao: Add SME sharing slides, other updates and minor fixes

Please squash merge this PR, thx a lot!

Not yet! Some updates impend.

Ready to merge now, please go ahead!


arch: arm64: Remove useless asm code

The content of the SCR_EL3 register is overwritten by a later instruction. Also no need to route SError, IRQs and FIQs to EL3.

I think we missed this in previous review.
Till the time control has not switched to lower EL we should be able to catch any abort arising out of EL3 code.
Instead of removing this we may have to put back the 'z_fatal_error()' handling esr_eln dump to consider EL3 as well. IRQ or FIQ are not possible to come at this point. But still as a convention

This was not overlooked but the chances that an abort occurs during the reset routines are really low (probably only in case of a faulty hardware). I can adjust the PR as you suggested but this is probably gonna be over-engineered :)

we can give a valid configuration. ie: if interrupt comes ( I would consider that as hardware glitch) then handle ( which is b .) at EL3 vector because there is no other option.

Interrupts should be masked by the DAIF register at this stage.

Interrupts should be masked by the DAIF register at this stage.

Yeah, right. we need not trap them. Pls ignore I/F.

chances that an abort occurs during the reset routines are really low

But I think its worth to retain the capability especially considering the platform hook can be extended to add any code at EL3.

buildkite failure unrelated (I hope). Force pushing again to re-trigger the CI.


Additional text file when saving pdf, csv or xls file to file system (iCloud Drive also)

Any time I share generated pdf (same with csv, xls) to a iCloud Drive there is additional text file generated with content taken from message field passed to window.plugins.socialsharing.shareWithOptions method.
For example calling:
window.plugins.socialsharing.shareWithOptions(
	 {
		subject: 'subject',
		message: 'some shared file',
		files:  ['file:///[...]/sharedFile.pdf']
	},
		() => {},
		() => {}
);

results with exported two files:
one pdf sharedFile.pdf
one text file Text File with the only content: some shared file (the same as value of message property passed to method above).
Any ideas how to prevent from Text File from being generated?

In my case (Ionic app), I don't need any message, so all I had to do was remove the that key.
this.socialSharing
	.shareWithOptions({ files })
	.then(() => {})
	.catch(() => {});

Same goes for the .share() method. I initially had empty strings for the message and subject arguments, which generated an extra empty Text File. Changing those params to null fixed the issue:
this.socialSharing
	.share(null, null, files)
	.then(() => {})
	.catch(() => {});

Following this issue...

Following this issue...

@Anuj-logiciel You can use the subscribe button on GitHub to follow issues ;) No need to comment and notify everybody.

Yep, I know @stovmascript. I just added a comment to prompt contributors to fix this. Thanks for the advice.


Missing metrics to monitor internal replication status

This is more a general design question than a bug report.
Description
We are running our CouchDB clusters on GKE.
Entire setup is very simple: each cluster has 3 nodes, default sharding settings (q=8,n=3).
To make sure that our clusters are healthy, we monitor:

/_membership data on every node, to verify that every node has connectivity to other nodes.
couchdb_httpd_request_time metric, which contains "length of a request inside CouchDB without MochiWeb", to verify that every node responds in a reasonable time.

We are looking to improve our monitoring solution to cover more failure modes, and have couple of questions:

Is there a way to determine that node is lagging to process writes?
After split brain situations (node lost connectivity to other nodes, but now connectivity is restored and node is syncing data) – is there a way to determine  "replication lag" or, in other words, amount of documents that are left to update?
Does it make sense to monitor if databases contain documents with conflicts after split brain situations?

Thanks!
Your Environment
GKE, CouchDB is installed with Helm using semi-official chart:
https://github.com/gpii-ops/gpii-infra/tree/master/shared/charts/couchdb

CouchDB Version used: 2.3.1
Browser name and version: None
Operating System and version: None, GKE

Hi @natarajaya,
As you said, this is not a CouchDB bug. GitHub is for actual CouchDB bugs only. Unfortunately this means your question got ignored.
If you are looking for general support with using CouchDB, please try one of these other options:

The user mailing list. Signup instructions are here
The Slack/IRC chat room. Joining instructions are here


Linting issue when trying to commit changes

Hi, I'm having an issue trying to commit my changes to the plugin list. When I commit my changes I get the following error below. Should this be occurring considering I've not changed the files it's telling me about?
husky > pre-commit (node v13.8.0)

Authors list sucessfully updated in only: 6.802ms

><EMAIL_ADDRESS>lint /Users/limitlessloop/Sites/postcss-plugins
> eslint ./scripts/ ./test/ --quiet

gi
/Users/limitlessloop/Sites/postcss-plugins/scripts/add-new-plugin.js
  19:1  error  Expected indentation of 8 spaces but found 4    indent
  21:1  error  Expected indentation of 12 spaces but found 8   indent
  22:1  error  Expected indentation of 16 spaces but found 12  indent
  23:1  error  Expected indentation of 12 spaces but found 8   indent
  24:1  error  Expected indentation of 12 spaces but found 8   indent
  25:1  error  Expected indentation of 16 spaces but found 12  indent
  26:1  error  Expected indentation of 12 spaces but found 8   indent
  27:1  error  Expected indentation of 12 spaces but found 8   indent
  28:1  error  Expected indentation of 12 spaces but found 8   indent
  30:1  error  Expected indentation of 12 spaces but found 8   indent
  31:1  error  Expected indentation of 12 spaces but found 8   indent
  32:1  error  Expected indentation of 16 spaces but found 12  indent
  33:1  error  Expected indentation of 12 spaces but found 8   indent
  34:1  error  Expected indentation of 12 spaces but found 8   indent
  35:1  error  Expected indentation of 12 spaces but found 8   indent
  36:1  error  Expected indentation of 8 spaces but found 4    indent
  37:1  error  Expected indentation of 8 spaces but found 4    indent
  38:1  error  Expected indentation of 8 spaces but found 4    indent

/Users/limitlessloop/Sites/postcss-plugins/scripts/data/banner.js
  1:7   error  Expected a line break after this opening brace   object-curly-newline
  1:19  error  Expected a line break before this closing brace  object-curly-newline

/Users/limitlessloop/Sites/postcss-plugins/scripts/update-authors.js
  34:18  error  Expected a line break after this opening brace   object-curly-newline
  34:59  error  Expected a line break before this closing brace  object-curly-newline
  40:1   error  Expected indentation of 4 spaces but found 0     indent
  41:1   error  Expected indentation of 4 spaces but found 0     indent

/Users/limitlessloop/Sites/postcss-plugins/scripts/update-stars.js
  18:1   error  Expected indentation of 4 spaces but found 0     indent
  19:1   error  Expected indentation of 8 spaces but found 4     indent
  19:54  error  Expected a line break after this opening brace   object-curly-newline
  19:86  error  Expected a line break before this closing brace  object-curly-newline
  20:1   error  Expected indentation of 8 spaces but found 4     indent
  21:1   error  Expected indentation of 4 spaces but found 0     indent
  22:1   error  Expected indentation of 4 spaces but found 0     indent
  23:1   error  Expected indentation of 8 spaces but found 4     indent
  24:1   error  Expected indentation of 4 spaces but found 0     indent

/Users/limitlessloop/Sites/postcss-plugins/test/test.utils-write-plugins.js
  19:26  error  Expected a line break after this opening brace   object-curly-newline
  19:56  error  Expected a line break before this closing brace  object-curly-newline
  21:1   error  Expected indentation of 12 spaces but found 8    indent
  23:1   error  Expected indentation of 16 spaces but found 12   indent
  24:1   error  Expected indentation of 12 spaces but found 8    indent
  25:1   error  Expected indentation of 12 spaces but found 8    indent
  30:1   error  Expected indentation of 12 spaces but found 8    indent
  32:1   error  Expected indentation of 16 spaces but found 12   indent
  33:1   error  Expected indentation of 12 spaces but found 8    indent
  34:1   error  Expected indentation of 12 spaces but found 8    indent

Nope, you should not be seeing that. I have a hunch that something funky is going with your local ESLint -- can you try to reinstall the local dependencies?

Thanks for the reply. Hmm, I'm not sure what was happening. I tried reinstalling the dependencies but that didn't work. In the end, I did another fork and copies the plugins.json and docs/authors.md across. Is that ok? If I get chance I can try doing it again using the npm run add script.

Yep that's totally fine. Sorry for the hassle!
Closing this as resolved for now, but willing to re-open if others are experiencing the same issue.


Settings dependency uses default values rather than environment variables when used directly

First check

[x] I added a very descriptive title to this issue.
[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.
[x] I already read and followed all the tutorial in the docs and didn't find an answer.
[x] I already checked if it is not related to FastAPI but to Pydantic.
[x] I already checked if it is not related to FastAPI but to Swagger UI.
[x] I already checked if it is not related to FastAPI but to ReDoc.

The FastAPI docs, when using settings as a dependency, don't depend directly on the Settings class but instead on a function that creates an instance of the Settings class.
I thought I would try depending on the class directly so as to make things slightly neater and not have to import both the class and the function.
MCVE:
from fastapi import FastAPI, Depends
from pydantic import BaseSettings

class Settings(BaseSettings):
    my_setting: str = "default"

def settings():
    return Settings()

app = FastAPI()

@app.get("/small")
async def small(settings: Settings = Depends(settings)):
    """
    Following the pattern from the docs, works as expected.
    """
    print(settings.my_setting)
    return {}

@app.get("/capital")
async def capital(settings: Settings = Depends(Settings)):
    """
    Depend on the class - does not use environment variables.
    """
    print(settings.my_setting)
    return {}

Now if I run the server with say,
MY_SETTING=non_default uvicorn app:app --reload

then loading the /small view will print non_default, but loading the /capital view will print default.
It's unclear to me whether this is intentional; I haven't found anything in the docs that suggests it would behave like this. I would have expected both versions to print "non_default".
Environment

OS: Linux
FastAPI Version: 0.63.0
Python: 3.8.1

Additional context
I played around a fair bit trying to track it down. I've got as far as finding that in solve_dependencies in dependencies/utils.py:
    545                 call=call, stack=stack, sub_values=sub_values
    546             )
    547         elif is_coroutine_callable(call):
    548             solved = await call(**sub_values)
    549         else:
--> 550             solved = await run_in_threadpool(call, **sub_values)
    551         if sub_dependant.name is not None:
    552             values[sub_dependant.name] = solved
    553         if sub_dependant.cache_key not in dependency_cache:
    554             dependency_cache[sub_dependant.cache_key] = solved

At this point, sub_values['my_setting'] is "default", which causes the Settings object to be constructed with that value.

FastAPI doesn't have any integration with the BaseSettings class - it's treating it as it would any other function/callable with default arguments with no annotation. Which is as a dependency that takes query parameters

Yeah I didn't expect that there would be any special integration with BaseSettings. But it's still not clear to me why my Settings class when constructed by FastAPI would be constructed differently than if I called Settings() myself.
Ie. FastAPI is calling Settings(my_setting="default") whereas I would have just expected it to call Settings() which would then allow the BaseSettings constructor to set the attributes based on the environment variables.

As I said in my my comment, FastAPI is treating it as Settings(my_setting: str = Query("default")), IE, like any other dependency

Thanks for the help here @Mause ! 👏  🙇
@amagee it seems you are passing Settings directly to Depends(), you are not supposed to do that.
Please check the docs here: https://fastapi.tiangolo.com/advanced/settings/#settings-in-a-dependency

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Customization of the initial day of the week in KalendarKonfig

A new parameter called isMondayInitialDay of type Boolean is included in KalendarKonfig, in which we can indicate if the first day of the week is Monday (if true) and if not, the initial day would be Sunday

Thanks for making it work for other parts of the world ;) It must be something else than a boolean though, because it's not saturday or monday, it's rather more colorful:
CLDR 40 has territories starting the week with friday, saturday, sunday, monday: https://unicode-org.github.io/cldr-staging/charts/40/supplemental/territory_information.html

@jeluchu please check the code?

@hi-manshu I am reviewing another way of doing it so that it can be applied with the different countries as you have indicated within the issue

Its fixed, Thanks for doing it


Auto-Detect and List Windows Terminal

Did you try to use FindPackageForUser?

@tsvietOK That is a restricted capability and the store didn't certify our app to use that permission.

I have found a bug.
Repro:
Revert this patch.
Copy this json to terminal.json
{
  "version": 1,
  "terminals": [
    {
      "id": 1,
      "name": "CMD",
      "path": "cmd.exe",
      "arguments": "/k \"cd /d {0} && title Command Prompt\"",
      "icon": ""
    },
    {
      "id": 2,
      "name": "Windows PowerShell",
      "path": "powershell.exe",
      "arguments": "-WorkingDirectory \"{0}\"",
      "icon": ""
    },
    {
      "id": 3,
      "name": "Windows Terminal",
      "path": "wt.exe",
      "arguments": "-d \"{0}\"",
      "icon": ""
    }
  ]
}

Restart app
Set default terminal Windows Terminal.
Close app
Apply this patch.
Start app and try to open terminal in folder.
Crash.
That happen because of localSettings terminal_id store old terminal id value = 3. But current updated terminal.json contain only two items.
So i would suggest to save default terminal id right in terminal.json file.


refresh token failed

“refreshToken must be a jwt string”

You have been banned in bybit coinsweeper. I have the same situation

You have been banned in bybit coinsweeper. I have the same situation

Banned from start? I launched it for the first time and the same message.

No, I used this program and I was banned after a week. There is a wave of bans now, even honest players suffer.

yep that's a ban

Banned :(

Have a fix?

If you are banned, you need to create a new telegram account. Then download the update of this repository and it will work


Disable nginx access_log, enable error_log instead

What does this PR do?

Disabled access_log for nginx by setting log target /dev/null
Enabled error_log for nginx, so that errors and critical exceptions of nginx are still logged

Motivation

improve data privacy by default (this is also a suggested change from https://docs.bigbluebutton.org/admin/privacy.html )
in case the access_log is temporarily needed (for example during a DDoS), the nginx configuration can easily be changed and applied without the need to restart nginx.

I don't know how to ansible, sorry. Thus, I'd suggest to either merge this PR and then improve from there on, or feel free to directly commit to this branch here and thus improve the pull request.


Kakfa changefeed stucks

What did you do?

create kafka changefeed with big table scale out is enabled

[scheduler]
region-per-span = 1_000

Use lightning to import ~300GB data to upstream via TiDB backend.
Check changefeed status

What did you expect to see?
Changefeed should adavance normally
What did you see instead?
Changefeed stucks

Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
[root@upstream-tidb-0 /]# /tidb-server -V
Release Version: v6.6.0-alpha
Edition: Community
Git Commit Hash: 93c6492418ae1bfa91479b8b465e61c78f29a995
Git Branch: heads/refs/tags/v6.6.0-alpha
UTC Build Time: 2023-02-08 11:51:47
GoVersion: go1.19.5
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: unistore

Upstream TiKV version (execute tikv-server --version):
[root@upstream-tikv-0 /]# /tikv-server -V
TiKV
Release Version:   6.6.0-alpha
Edition:           Community
Git Commit Hash:   d513b789f0709520cdccc20bc4e6560761ad01a5
Git Commit Branch: heads/refs/tags/v6.6.0-alpha
UTC Build Time:    2023-02-09 11:50:03
Rust Version:      rustc 1.67.0-nightly (96ddd32c4 2022-11-14)
Enable Features:   pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp clo
ud-azure
Profile:           dist_release

TiCDC version (execute cdc version):
[2023/02/09 10:46:54.599 +00:00] [INFO] [version.go:47] ["Welcome to Change Data Capture (CDC)"] [release-version=v6.6.0-alpha] [git-hash=0e1322f90b9b72697ca74513c32c0cb64479064c] [git-branch=heads/refs/tags/v6.6.0-alpha] [utc-build-time="2023-02-08 11:41:41"] [go-version="go version go1.19.5 linux/amd64"] [failpoint-build=false]

/severity critical

/found automation


Reference panel accepts a csv

PR checklist

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

This PR addresses this issue https://github.com/nf-core/phaseimpute/issues/11

Sorry @eugeniafontecha this code is a duplicate of #18
For it to works we need to correctly manage the files by chromosome and use the meta map accordingly.
You effectively saw the different problem I've ran into.
Could you look at my PR ? it contains all the modification you've done.

Hi @LouisLeNezet!
I understand your concerns regarding the duplication of code but I would like to provide additional context. The contribution from @eugeniafontecha, while overlapping with your work, represents a unique effort during the hackathon that I believe deserves consideration.
This is one of Eugenia's first contributions in Nextflow and she went above and beyond during her first hackathon. I think it would be nice, as members of the nf-core community, to welcome participation from less experienced contributors.
Since Eugenia's code contains partially the same modifications as yours, you could perhaps review Eugenia's PR and consider how her modifications can complement and improve upon your work. Then, if you accept her PR, you can sync your code with these changes and then submit your additional modifications accordingly. I think that this way we all benefit and foster a supportive community :)

@atrigila I understand completely.
It will break a few things on my PR but I will manage.
Would it be possible for her to do the following command ?
nf-core subworkflows update vcf_impute_glimpse
nf-core subworkflows update vcf_phase_shapeit5

We will merge even if the test fail as the #18 will fix it :)

Thank you @LouisLeNezet and @atrigila !!


Fritzbox device tracker errors

Home Assistant release with the issue:
0.103.0
Last working Home Assistant release (if known):
Not sure, 0.100.0 ?
Operating environment (Hass.io/Docker/Windows/etc.):
hassbian
Integration:
https://www.home-assistant.io/integrations/fritz/
Description of problem:
The integration only starts after several restarts. I got these errors in the log:
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
device_tracker:
- platform: fritz
  host: <IP_ADDRESS>
  username: !secret fb_login
  password: !secret fb_pw
  consider_home: 180
  new_device_defaults:
   track_new_devices: true
   hide_if_away: True

Traceback (if applicable):
2019-12-17 08:28:37 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/device_tracker/setup.py", line 164, in async_device_tracker_scan
    found_devices = await scanner.async_scan_devices()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/fritz/device_tracker.py", line 68, in scan_devices
    self._update_info()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/fritz/device_tracker.py", line 88, in _update_info
    self.last_results = self.fritz_box.get_hosts_info()
  File "/srv/homeassistant/lib/python3.7/site-packages/fritzconnection/fritzhosts.py", line 73, in get_hosts_info
    'ip': host['NewIPAddress'],
KeyError: 'NewIPAddress'
2019-12-17 08:29:17 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/device_tracker/setup.py", line 164, in async_device_tracker_scan
    found_devices = await scanner.async_scan_devices()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/fritz/device_tracker.py", line 68, in scan_devices
    self._update_info()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/fritz/device_tracker.py", line 88, in _update_info
    self.last_results = self.fritz_box.get_hosts_info()
  File "/srv/homeassistant/lib/python3.7/site-packages/fritzconnection/fritzhosts.py", line 73, in get_hosts_info
    'ip': host['NewIPAddress'],
KeyError: 'NewIPAddress'
2019-12-17 08:29:42 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/device_tracker/setup.py", line 164, in async_device_tracker_scan
    found_devices = await scanner.async_scan_devices()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/fritz/device_tracker.py", line 68, in scan_devices
    self._update_info()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/fritz/device_tracker.py", line 88, in _update_info
    self.last_results = self.fritz_box.get_hosts_info()
  File "/srv/homeassistant/lib/python3.7/site-packages/fritzconnection/fritzhosts.py", line 73, in get_hosts_info
    'ip': host['NewIPAddress'],
KeyError: 'NewIPAddress'
2019-12-17 08:30:22 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/device_tracker/setup.py", line 164, in async_device_tracker_scan
    found_devices = await scanner.async_scan_devices()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/fritz/device_tracker.py", line 68, in scan_devices
    self._update_info()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/fritz/device_tracker.py", line 88, in _update_info
    self.last_results = self.fritz_box.get_hosts_info()
  File "/srv/homeassistant/lib/python3.7/site-packages/fritzconnection/fritzhosts.py", line 73, in get_hosts_info
    'ip': host['NewIPAddress'],
KeyError: 'NewIPAddress'

Additional information:

Hello, I have the some problem.
Home Assistant release with the issue:
0.103.0
Last working Home Assistant release (if known):
0.102.3

Duplicate of #13608

Closing this issue since it is a duplicate as mentioned above.

Hello, I had the same after a new installation!
after I was in the

platform: fritz
host: !secret fritz_ip
replaced the hostname with the IP address, it worked for me again.

thanks!!
https://sspaeth.de/2018/01/home-assistent-pitfalls/
I have a FritzBox from AVM, so I installed the “platform: fritz” module to track devices in our WLAN. However, that led to mysterious “Failed to establish connection to FRITZ!Box with IP: <IP_ADDRESS>” errors. Debugging the underlying package “fritzconnection”, it turns out that you need to turn on “Zugriff für Anwendungen zulassen” AND “Statusinformationen über UPnP übertragen” in your Homenetwork->Network Settings, to make it work. This will turn on TR-64 and the transmission of the necessary status information. Error handling of this package could be a tad better….


Confusion effect is not rolled per character but rather once per turn for all creatures

Version: 1.0
Error: confusion effect is not rolled per character but rather once per turn for all creatures:

Roll on the following table at the start of each subject's turn each round to see what it does in that round.

Confusion should now give a chat message on the token's turn as of v1.1


Extended to support non-orthogonal box vectors

Extended to support non-orthogonal box vectors

I've also updated the functions in potential.py to work with pymbar v4, as the function names changed between v3 and v4


clang symbols not found

Hi,
I have all the toolchains setup correctly. When I build from the command line I get a successful build. However when I try to build from Xcode the linker cannot link to the MongoKitten.swiftmodule.
Do I have to use a different version of clang?
Undefined symbols for architecture x86_64:
"MongoKitten.Server.__allocating_init (at : Swift.String, port : Swift.Int, using : (username : Swift.String, password : Swift.String)?, automatically : Swift.Bool) throws -> MongoKitten.Server", referenced from:
test.AppDelegate.applicationDidFinishLaunching (__ObjC.NSNotification) -> () in AppDelegate.o
ld: symbol(s) not found for architecture x86_64
Any idea?
Thanks,
Eddy

Are you using the Swift Development Snapshot 2016-03-24-a?
We (me and @Joannis) haven't used MongoKitten with a 'normal' OS X app project, we just swift build --init and then swift build -X. How did you set up your Xcode project to use MongoKitten?

Yes, I am using Swift Development Snapshot 2016-03-24-a?
I did the same initialization swift build —init and swift build -X
Opened the project file and added to Build Settings -> Swift compiler - Search -> Import Path the path to .build/debug
Then I added just ten #iport MongoKitten to main.swift and built.  It was OK.
After that I added the example code to the main.swift  (connect to local mongo etc). Then the build failed. but the code complete did show the functions etc in the editor.

Eddy

On Apr 6, 2016, at 1:56 AM, Robbert Brandsma<EMAIL_ADDRESS>wrote:
Are you using the Swift Development Snapshot 2016-03-24-a?
We (me and @Joannis https://github.com/Joannis) haven't used MongoKitten with a 'normal' OS X app project, we just swift build --init and then swift build -X. How did you set up your Xcode project to use MongoKitten?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/PlanTeam/MongoKitten/issues/13#issuecomment-206232835

Could you post your Package.swift?

On another note: Why are you adding an import path?
swift build -X should take care of that.

@EddyHahn I've managed to reproduce the error. Tell me if I'm incorrect:
You've created a project in XCode. Added a package.swift with the required information. Then you've linked the .build/debug directory in the import path. Ran swift build and then you got the error, correct?
Currently XCode does not support SPM (Swift Package Manager) projects by default. So to solve this you'll have to generate the project differently.
Create a directory with the name of your project:
mkdir MyAwesomeProject
Go in the direcotry:
cd MyAwesomeProject
Initialize the project:
swift build --init
Edit the Package.swift file to contain your dependencies:
open Package.swift
Save it (of course) and go back to the terminal
Create the XCode project using the Command Line tools
swift build -X
Enter the directory using finder
open .
and open the XCode project by double-clicking it
This is not a bug in MongoKitten or any similar project. It's a missing feature in XCode that everyone is still waiting for. So I'll also write some instructions for when you're adding more dependencies:
Open the Package.swift using your editor and add the dependencies like above.
Open the terminal and enter your root-directory of the project again (same level as Package.swift)
Clean all build-directories:
swift  build --clean dist
And remake the project:
swift build -X
Now you can open the project again with XCode and you'll be set with your new dependencies.
If you're having issues for any reason within the XCode project at this point it's best to clean your XCode project. (CMD + K)
I hope this helps!

Thanks!
I do not know what happened but this time around the swift build -X worked and all the packages now show up in Xcode.  Build did work swell and I can debug too!
Thank you Again!
Eddy

On Apr 6, 2016, at 8:47 AM, Joannis Orlandos<EMAIL_ADDRESS>wrote:
@EddyHahn https://github.com/EddyHahn I've managed to reproduce the error. Tell me if I'm incorrect:
You've created a project in XCode. Added a package.swift with the required information. Then you've linked the .build/debug directory in the import path. Ran swift build and then you got the error, correct?
Currently XCode does not support SPM (Swift Package Manager) projects by default. So to solve this you'll have to generate the project differently.
Create a directory with the name of your project:
mkdir MyAwesomeProject
Go in the direcotry:
cd MyAwesomeProject
Initialize the project:
swift build --init
Edit the Package.swift file to contain your dependencies:
open Package.swift
Save it (of course) and go back to the terminal
Create the XCode project using the Command Line tools
swift build -X
Enter the directory using finder
open .
and open the XCode project by double-clicking it
This is not a bug in MongoKitten or any similar project. It's a missing feature in XCode that everyone is still waiting for. So I'll also write some instructions for when you're adding more dependencies:
Open the Package.swift using your editor and add the dependencies like above.
Open the terminal and enter your root-directory of the project again (same level as Package.swift)
Clean all build-directories:
swift build --clean dist
And remake the project:
swift build -X
Now you can open the project again with XCode and you'll be set with your new dependencies.
If you're having issues for any reason within the XCode project at this point it's best to clean your XCode project. (CMD + K)
I hope this helps!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/PlanTeam/MongoKitten/issues/13#issuecomment-206437003

No problem! Good luck with MongoKitten! Just enter another ticket if you need additional assistance.


Nick: Watch avisaservices.com

Nick requests the watch of the watch_keyword avisaservices\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

avisaservices\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


TypeError: Input does not meet YAML 1.2

Warning: Unhandled error in Gradle post-action - job will continue: TypeError: Input does not meet YAML 1.2 "Core Schema" specification: cache-read-only
[8](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:8)
Support boolean input list: `true | True | TRUE | false | False | FALSE`
[9](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:9)
TypeError: Input does not meet YAML 1.2 "Core Schema" specification: cache-read-only
[10](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:10)
Support boolean input list: `true | True | TRUE | false | False | FALSE`
[11](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:11)
    at Object.getBooleanInput (/home/runner/work/_actions/Wandalen/gradle-build-action/dist/webpack:/gradle-build-action/node_modules/@actions/core/lib/core.js:151:1)
[12](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:12)
    at isCacheReadOnly (/home/runner/work/_actions/Wandalen/gradle-build-action/dist/webpack:/gradle-build-action/src/cache-utils.ts:60:1)
[13](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:13)
    at Object.<anonymous> (/home/runner/work/_actions/Wandalen/gradle-build-action/dist/webpack:/gradle-build-action/src/caches.ts:77:1)
[14](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:14)
    at Generator.next (<anonymous>)
[15](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:15)
    at /home/runner/work/_actions/Wandalen/gradle-build-action/dist/webpack:/gradle-build-action/src/caches.ts:31:1
[16](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:16)
    at new Promise (<anonymous>)
[17](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:17)
    at __webpack_modules__.3800.__awaiter (/home/runner/work/_actions/Wandalen/gradle-build-action/dist/webpack:/gradle-build-action/src/caches.ts:27:1)
[18](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:18)
    at Object.save (/home/runner/work/_actions/Wandalen/gradle-build-action/dist/webpack:/gradle-build-action/src/caches.ts:73:1)
[19](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:19)
    at Object.<anonymous> (/home/runner/work/_actions/Wandalen/gradle-build-action/dist/webpack:/gradle-build-action/src/setup-gradle.ts:79:1)
[20](https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:20)
    at Generator.next (<anonymous>)

Thanks for the report @ben-manes: a few questions

Does this happen consistently for you, or is it sporadic?
Does this still occur if you apply the gradle-build-action directly, and not via<EMAIL_ADDRESS>Does it still happen if you explicitly add cache-read-only: false to your action params?

For my own reference, here's a link to the failing run: https://github.com/ben-manes/caffeine/runs/6786982478?check_suite_focus=true#step:36:7

analysis.yml job

variant: Removed wretry.action
result: no errors, and see job summaries

benchmarks.yml

variant: Added cache-read-only with wretry.action
result: no errors, and see job summaries

examples.yml

variant: Added cache-read-only, removed wretry.action
result: no errors, and see job summaries

build.yml

variant: No change (with wretry.action, without cache-read-only)
result: TypeError  warnings, no  job summaries

This does seem to have started with the latest release when combined with wretry.action. When originally configuring that retry this warning had not occurred.
The wretry.action was added because I was seeing spurious network failures when downloading the jdk and gradle distribution. This started after splitting the build.yml job into parallel 117 jobs to reduce the runtime from 2.5hrs to ~30 minutes or less, where Github will run up to 20 jobs concurrently on the free tier. That could reasonably trigger some ddos protection rules and explain these network glitches. Adding the wretry.action seemed like a simple fix and removed the noise of these random failures. I am open to alternative suggestions.
Thanks @bigdaz!

Done. I will set this explicitly for now as I might prefer the old behavior since I use a long-lived dev branch and merge into the main branch once the changes are ready. I doubt many others use these two actions together and I agree with your preference to having it more explicitly in the action definition. Closing this in favor of https://github.com/Wandalen/wretry.action/issues/49

Thanks for the follow up. I really appreciate the testing and feedback.


Update documentation

Why:
Some of our documentation is out of date and we would like for new users
to the project be able to onboard without the friction of stale info.
This commit:

Updates the example.env.bt
Updates the readme
Removes the unused changelog
Updates the pull request template to follow the team's conventions

Not sure why unit-test-ios is failing here as there are no changes to any application code in this commit. Im assuming its a caching issue of some sort on the action. Going to close and reopen to try an resolve.


Remove 'jsx'

https://github.com/gaearon/react-hot-boilerplate/pull/32#issuecomment-133881240

:+1:


Kedar/scl package

making the repo into a package. Maybe lets merge this after the course?
Some more things:

might be good to add some "plug-n-play" of Huffman, Adaptive Arithmetic and LZ which don;t requite any input
Might be good to see how to make the repo a bit less bloated (maybe remove ProbDist object etc. and use simple ordered dict to represent it? (Need to think about it). Usually better to have less custom classes. Some classes like encoded stream, data stream might still be useful though :-|

Looks good and works!


Update terragrunt.hcl

Ran Plan for dir: . workspace: default
Show Output
Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "~> 3.0"...
- Installing hashicorp/null v3.2.3...
- Installed hashicorp/null v3.2.3 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # null_resource.example will be created
  + resource "null_resource" "example" {
      + id = (known after apply)
    }

  # null_resource.path will be created
  + resource "null_resource" "path" {
      + id = (known after apply)
    }

Plan: 2 to add, 0 to change, 0 to destroy.

:arrow_forward: To apply this plan, comment:atlantis apply -d .

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -d .

Plan: 2 to add, 0 to change, 0 to destroy.

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

atlantis apply

Ran Apply for 0 projects:

atlantis apply -d .

Ran Apply for dir: . workspace: default
Show Output
null_resource.example: Creating...
null_resource.path: Creating...
null_resource.path: Provisioning with 'local-exec'...
null_resource.path (local-exec): Executing: ["/bin/sh" "-c" "cd /tmp && pwd"]
null_resource.example: Provisioning with 'local-exec'...
null_resource.example (local-exec): Executing: ["/bin/sh" "-c" "echo 'Hello from Terragrunt!!!'"]
null_resource.example (local-exec): Hello from Terragrunt!!!
null_resource.example: Creation complete after 0s [id=549695902714548321]
null_resource.path (local-exec): /tmp
null_resource.path: Creation complete after 0s [id=8141827840400330744]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: . workspace: default


feat: port scripts to ts

Refs #57
Resolve #46

Ah you mean because the schema are in some senses the "source"? Yeah I see what you mean, although in another way they are, like you say, static assets for the TypeScript source - which is what is compiled to become the actual published package code 🤷♂

Yeah, exactly. So I'm not 💯 sure what should be considered source here – though my gut feeling tells me it's the schema. If there's no more elegant alternative to the Current setup I'm happy to run with this one though.

I'm comfortable how it is at the moment, since it's a bit six of one, half a dozen of the other. We can see how it sits for a while. It doesn't affect the public api of the package which remains just import fileFormat from '@sketch-hq/sketch-file-format.


[staging & production] Empty folders have '+' in project overview and files tab

Reported by @nicipfeiffer on the 0.32 Trello board:
Steps

Create a new project
Go to the files tab
Click on the '+' to create a new folder in OSF storage folder
Submit
Return to the files tab
Look at the symbol preceding the folder name

Expected
A new folder would have no files inside, and therefore would not have '+' preceding it.
Actual
The new folder with no content has a '+' indicating that it holds files

Notes
This is hard to compare with production, as you cannot currently make folders, but as per a comment from @brianjgeiger: "Yes, I explicitly avoided having the plus by empty folders because it lets people know that it is empty before they click on it."
And another from @brianjgeiger: "That is a shame, because it inconsistent with existing UI. We will either want to do the necessary requests to determine if the folders at least contain things or not, or we will want to change how the Project Organizer (and other parts of the files grid) handle that situation to match."

Quick note: Implementing the FileTree (which is a currently a requirement for the V2 API) will fix this issue. The File Tree, only roughly defined so far, is essentially a cache of a project's entire file structure (although cache might not be the correct word). Once we have this, we should also have the count of items in the folders. There will be times when this information is out of date, but it'll be better than what we have.

HOLD'ing for now. TY


Enable label alignment for token classification datasets

This PR extends the Dataset.align_labels_with_mapping() method to support alignment of label mappings between datasets and models for token classification (e.g. NER).
Example of usage:
from datasets import load_dataset

ner_ds = load_dataset("conll2003", split="train")
# returns [3, 0, 7, 0, 0, 0, 7, 0, 0]
ner_ds[0]["ner_tags"]
# hypothetical model mapping with O <--> B-LOC
label2id = {
    "B-LOC": "0",
    "B-MISC": "7",
    "B-ORG": "3",
    "B-PER": "1",
    "I-LOC": "6",
    "I-MISC": "8",
    "I-ORG": "4",
    "I-PER": "2",
    "O": "5"
  }
ner_aligned_ds = ner_ds.align_labels_with_mapping(label2id, "ner_tags")
# returns [3, 5, 7, 5, 5, 5, 7, 5, 5]
ner_aligned_ds[0]["ner_tags"]

Context: we need this in AutoTrain to automatically align datasets / models during evaluation. cc @abhishekkrthakur

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Hmm, not sure why the Windows tests are failing with:
Did not find path entry C:\tools\miniconda3\bin
C:\tools\miniconda3\envs\py37\python.exe: No module named pytes

One last nit and we can merge then

Thanks, done!


Cilium-operator-generic: "cilium-operator-generic": executable file not found in $PATH: unknown

Is there an existing issue for this?

[X] I have searched the existing issues

Version
higher than v1.15.7 and lower than v1.16.0
What happened?
Finding 1.15.7 cilium operator weird when pulling from a private repo
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "cilium-operator-generic": executable file not found in $PATH: unknown
I ran into a similiar issue in 1.13.x where the chart would automatically add generic at the end, does anyone have any ideas?
How can we reproduce the issue?
pull operator image to private repo and deploy.
for 1.15.3 had to rename image to cilium-operator-generic
Cilium Version
1.15.6 & 1.15.7
Working in 1.15.3
Kernel Version
5.14.0-427.26.1.el9_4.x86_64
Kubernetes Version
1.27.14
Regression
No response
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

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

Please provide your Helm configuration / values.yaml to see if this is reproducible with the standard Helm charts.

helm install cilium v1.15.7-cilium/
--namespace kube-system
--set imagePullSecrets[0].name="pullsecret"
--set operator.image.repository="mylocalregistry.com/cilium-operator"
--set operator.image.tag="v1.15.7"
--set operator.image.useDigest=false
--set operator.image.pullPolicy="Always"
Testing 1.16.0 now

Same issue with 1.16.0

I can't reproduce this locally with a similar values configuration. After some initial delay in pulling images, all Cilium Pods started successfully.
$ cat values.yaml
operator:
  image:
    repository: "quay.io/cilium/operator"
  tag: "v1.15.7"
  useDigest: false
  pullPolicy: "Always"
$ cilium install --values values.yaml --version v1.16.0
🔮 Auto-detected Kubernetes kind: kind
✨ Running "kind" validation checks
✅ Detected kind version "0.22.0"
ℹ  Using Cilium version 1.16.0
🔮 Auto-detected cluster name: kind-kind
🔮 Auto-detected kube-proxy has been installed
$ kubectl -n kube-system get pods -w | grep cilium
cilium-envoy-7gq2t                           0/1     ContainerCreating   0          8s
cilium-envoy-qk59f                           0/1     ContainerCreating   0          8s
cilium-operator-676d46f99b-zgdjs             0/1     ContainerCreating   0          8s
cilium-qnhxh                                 0/1     Init:0/6            0          8s
cilium-r5pf5                                 0/1     Init:0/6            0          8s
cilium-r5pf5                                 0/1     Init:0/6            0          11s
cilium-r5pf5                                 0/1     Init:1/6            0          12s
cilium-r5pf5                                 0/1     Init:2/6            0          13s
cilium-operator-676d46f99b-zgdjs             0/1     Running             0          14s
cilium-operator-676d46f99b-zgdjs             1/1     Running             0          14s
cilium-r5pf5                                 0/1     Init:3/6            0          15s
cilium-qnhxh                                 0/1     Init:1/6            0          15s
cilium-r5pf5                                 0/1     Init:4/6            0          15s
cilium-qnhxh                                 0/1     Init:2/6            0          16s
cilium-envoy-qk59f                           0/1     Running             0          16s
cilium-r5pf5                                 0/1     Init:5/6            0          17s
cilium-qnhxh                                 0/1     Init:3/6            0          17s
cilium-r5pf5                                 0/1     PodInitializing     0          18s
cilium-qnhxh                                 0/1     Init:4/6            0          18s
cilium-r5pf5                                 0/1     Running             0          19s
cilium-qnhxh                                 0/1     Init:5/6            0          19s
cilium-qnhxh                                 0/1     PodInitializing     0          20s
cilium-qnhxh                                 0/1     Running             0          21s
cilium-envoy-qk59f                           0/1     Running             0          26s
cilium-envoy-qk59f                           1/1     Running             0          26s
cilium-envoy-7gq2t                           0/1     ErrImagePull        0          26s
cilium-r5pf5                                 0/1     Running             0          27s
cilium-r5pf5                                 1/1     Running             0          27s
cilium-qnhxh                                 0/1     Running             0          29s
cilium-qnhxh                                 1/1     Running             0          29s
cilium-envoy-7gq2t                           0/1     ImagePullBackOff    0          38s
cilium-envoy-7gq2t                           0/1     Running             0          42s
cilium-envoy-7gq2t                           0/1     Running             0          46s
cilium-envoy-7gq2t                           1/1     Running             0          46s

Most likely the private repository is making a clone of the wrong operator images.

you've tried you own repository?  I have no issues w/ quay.io/cilium/operator

I suggest double-checking how you are pushing images into your private repository, and compare those with the various flavors of operator image from the different quay.io/cilium/operator* repositories.

I will, i'm in the middle of eliminating the repo, and just going to do it locally w/ a different name and see where i'm at.   Having done this 200+ times we'll see.

 And then use quay.io/cilium/operator-generic error solved.


Leyning spreadsheets have wrong weekday parashah after Shabbat Shuvah this year

At https://www.hebcal.com/sedrot/#download, in the "Leyning spreadsheet downloads" section, in years when Rosh Hashanah is Thursday-Friday (such as 5785), the csv for weekday reading incorrectly says that the reading for Monday 5 Tishrei and Thursday 8 Tishrei is Bereshit, when it should be Vezot Haberakhah. (The csv is correct that Monday 12 Tishrei is Vezot Haberakhah.)
I suspect the needed fix is at https://github.com/hebcal/hebcal-leyning/blob/bac80c79471eff00eda7115f8269224a4bc3c967/src/getLeyningOnDate.ts#L18-L29 . (However, reading that code, I can't figure out why the csv is correct in years with Rosh Hashanah on Monday-Tuesday (such as 5783) regarding the reading on Thursday 11 Tishrei, so I don't think I'll be submitting a patch...)

It appears to me that this code is doing exactly what it should be doing, setting the leining to vezos haberacha between YK and ST. This requires an exception because, unlike the the other parshiyos, Vezos Haberacha is associated with a yom tov rather than Shabbos. This is it's own special case and should remain as is. It appears to me the issue is not having a separate special case for when Haazinu falls on Shabbos Shuva. It appears that the period between RH and YK is treated like any other week, where the method is to look for the next regular shabbos leining. Because Vezos Haberacha is not associated with a Shabbos, in years when Haazinu is in Shabbos Shuva, the next regular leining is Bereishis. This would explain the error in the spreadsheet. This error does not arise in years when Vayelech is on Shabbos Shuva since in that case, the next regular weekly reading is indeed Haazinu, so there is no issue. If RH starts on Monday or Tuesday, or Shabbos Shuva, Shabbos Shuva will be Vayelech, while Haazinu will be read on the Shabbos in Between YK and Sukkos, thus avoiding this error, whereas when RH starts on Thursday, there will be no Shabbos between YK and Sukkos, and so Shabbos Shuva will be Haazinu, giving this error.

Thanks. This is fixed now.
@MaxBGreenberg, we think we already have the Shabbat Shuva special cases correct for both Ha'azinu and Vayeilech
https://github.com/hebcal/hebcal-leyning/blob/main/src/holiday-readings.json#L529-L536

@mjradwin I meant add a special case for determining the weekday reading for between RH and YK based upon what parsha is read on Shabbos Shuva. If Vayelech is read on Shabbos Shuva, you can determine the leining for weekdays Between RH and YK just like any other Parsha. It's only when Haazinu is read on Shabbos Shuva that you need to have a special rule like for between YK and ST. The comment on the fix you implemented says "If Vayeilech or Ha'azinu occurs between RH and YK..." But that's not really an "if". One of those is always read. What matters is which of them it is. Which is what I meant by having a special rule, i.e. a special rule for determining weekday readings between RH and YK separate from the special case between YK and ST.

Got it. My comment is indeed incorrect but I believe the implementation is correct. If it's a Mon/Thu weekday reading and the immediately upcoming Shabbat is a regular parsha (Vayeilech or Ha'azinu, or during the rest of the year really any regular parsha) and not a holiday reading, the block of code immediately above will have already returned the correct parsha.
I believe the special case for Vezot Habracha on Mon/Thu weekday readings during Tishrei 3 through 22 works correctly because the other cases (e.g. Chag or Chol haMoed Sukkot) are also handled elsewhere.


Error: Not found

Hi @z0al!
Thank you for this nice action! I'm trying to use it but I'm getting the following error:

I've verified and confirmed that the secret is available to use in the action. Can you please share any tips or point me in the right direction to solve this issue? Thank you!!

Hey. Thanks for reporting this!

Can you please share any tips or point me in the right direction to solve this issue?

My first guess would be that one of the dependencies declared on the issue (or PR) #292  is:

not valid or
inaccessible by the action due to permissions

In both cases, GitHub returns 404 - Not found error. Is possible to share the description of  #292? I'm mainly concerned about the point where you declare the dependencies. If all dependencies are local (as in they all belong to the same repo) then my guess is wrong.

Thanks for the quick response! #292 is a PR in the same repo that uses the action. Would this error be consistent with a PR that was merged and no longer open? I'll try again with another and/or issue. Again, thanks for taking the time to look into this!

Thanks for the quick response! #292 is a PR in the same repo that uses the action.
Yeah, that part is clear and most likely not the issue. What I'm interested in is the description of that PR @onel0p3z

If it has something like:
depends on user/another-repo#123

Then my guess is that the provided token is not sufficient to read issues of user/another-repo.

Would this error be consistent with a PR that was merged and no longer open?

No. Closing a dependency shouldn't cause any problem.

Is that a public repo I can look at?

@z0al it's not on a public repo. I'll try to add the action to another repo that's public within the same org and see if I can recreate the issue there. Thank you!

Hi @z0al. Sorry for the delay. I just realized that the error is thrown whenever a PR is created and the action runs for that PR. Not sure if it's a configuration error on my side or if the action throws whenever it runs for a PR that doesn't have any keywords or labels. I haven't tried to recreate on a public repo yet. Thanks for keeping this open!

Hey. No worries.
Having no keywords shouldn't throw anything really. It just means the PR has no dependencies. The Not found is an API error, the cause can be either a misconfiguration (invalid token permissions) or a bug on the action code that makes it request something it shouldn't.

I will try to add more action logs on the upcoming weekend to help us identify the cause now and in future.

Hey @onel0p3z . I just updated the action to log the full error stack when possible. Can you try to run it manually again in the original #292 issue and check the log?

Got a similar error when referencing a PR in an other private repository from the same organization:
HttpError: Not Found
    at /home/runner/work/_actions/z0al/dependent-issues/v1/webpack:/dependent-issues/node_modules/@octokit/request/dist-node/index.js:66:1
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Im not sure if it's the same cause as the issue reported by @onel0p3z.
The description of the pull request looks like the following:
Depends on https://github.com/orgname/repository-name/pull/1

The referenced PR is closed an merged.
Thanks in advance for your support

Got a similar error when referencing a PR in an other private repository from the same organization:
HttpError: Not Found
    at /home/runner/work/_actions/z0al/dependent-issues/v1/webpack:/dependent-issues/node_modules/@octokit/request/dist-node/index.js:66:1
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Im not sure if it's the same cause as the issue reported by @onel0p3z.
The description of the pull request looks like the following:
Depends on https://github.com/orgname/repository-name/pull/1

The referenced PR is closed an merged.
Thanks in advance for your support

I am having the exact same issue, trying to reference across an organisations repos.

Got a similar error when referencing a PR in an other private repository from the same organization:
HttpError: Not Found
    at /home/runner/work/_actions/z0al/dependent-issues/v1/webpack:/dependent-issues/node_modules/@octokit/request/dist-node/index.js:66:1
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Thanks for the report @MathiasSchwaller . That's expected though, I'm assuming you're not using a Personal Access Token (PAT), right?
The solution to your issue is using a PAT with repo scope instead of the auto-generated GITHUB_TOKEN. That's because GITHUB_TOKEN only gives access to the current repo and not the whole org repos.

I should probably create a FAQs section in the README later. PRs to improve that are welcome

Got a similar error when referencing a PR in an other private repository from the same organization:
HttpError: Not Found
    at /home/runner/work/_actions/z0al/dependent-issues/v1/webpack:/dependent-issues/node_modules/@octokit/request/dist-node/index.js:66:1
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Thanks for the report @MathiasSchwaller . That's expected though, I'm assuming you're not using a Personal Access Token (PAT), right?
The solution to your issue is using a PAT with repo scope instead of the auto-generated GITHUB_TOKEN. That's because GITHUB_TOKEN only gives access to the current repo and not the whole org repos.

Thank you for the fast response.
Yes i was using the default GITHUB_TOKEN, but because of security concerns i can't switch to a PAT token with repo access. A PAT with repo:status access ins't sufficient for the action (i'm not that familiar with PATs and the documentation isn't that specific about the different scopes)?
I'm going to create a FAQ for cross-repository-dependencies later in the evening.

@z0al my issue was definitely the same as @MathiasSchwaller. After updating the token with a PAT, the error went away and the action finished without an issue. Thanks for all the help and patience! I'll go ahead and close this issue. @MathiasSchwaller thanks for adding the FAQ in #109 ❤

A PAT with repo:status access ins't sufficient for the action?

I understand your concern @MathiasSchwaller , but I'm afraid the PAT token scopes are not that flexible. What this Action needs is permission to do the followings:

Update PR commit status (the repo:status should be enough for this part)
Update labels
Write comments

What I'd do in your case is to simply review the code and then fork the repo and run your own fork, which is fairly easy to do. Luckily, there isn't much going on on this repo code-wise so you don't have to update your fork as often (you can safely ignore Dependabot PRs). You could watch "Releases" and update accordingly.

Hey z0al, I've tried to use a PAT in your action, but I still run into problems, it won't let me access the other repo. I just replaced the "GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN}}" with the PAT. Is this the correct approach?
Thanks!

Yeah, that sounds about right @KillWolf, maybe double-check the token has repo scope?. You can also check this guide in the FAQs (thanks to @mathias-schwaller )


Support PSR-6 Cache Library

Adds a FigCache which can work with any PSR-6 compatible caching library

Coverage remained the same at 100.0% when pulling e2d0be6ee51106ddafab978a2743507ed9aad389 on baileylo:support-psr-cache-adapter into eb6d81a27429ff4052ac46d8dd09774bfc903765 on aol:master.

Coverage remained the same at 100.0% when pulling e2d0be6ee51106ddafab978a2743507ed9aad389 on baileylo:support-psr-cache-adapter into eb6d81a27429ff4052ac46d8dd09774bfc903765 on aol:master.

Coverage remained the same at 100.0% when pulling 098e671279aa8c05848d2e40658c52bd5722e91b on baileylo:support-psr-cache-adapter into eb6d81a27429ff4052ac46d8dd09774bfc903765 on aol:master.

I closed this PR because the PSR-6 caching spec doesn't support atomic cache writes.


Error in executing  00_compute_features.py

carolindavis@carolindavis-Aspire-E5-575G:~/Documents/eye-movements-predict-personality-master$ python 00_compute_features.py
('merging window size', 5)
('did not find ', 'features/Participant00/window_features_5.npy')

When you extract all zip files under data folder, "python 00_compute_features.py" enable to compute gaze features for all participants.

i din see any options for this how can i do it can u help me please
On Tue, Mar 17, 2020 at 11:34 PM M.A.S<EMAIL_ADDRESS>wrote:

When you extract all zip files under data folder, "python
00_compute_features.py" enable to compute gaze features for all
participants.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sarikayamehmet/eye-movements-predict-personality/issues/1#issuecomment-600217702,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM2DSPOO5UAGIMDCZNB67OTRH63S3ANCNFSM4LNLS37A
.

i do unzipped those file and again executed but the sme error is raising


SCMOD-12730: Add pause, resume + status endpoints

https://portal.digitalsafe.net/browse/SCMOD-12730

CI Build Link:
http://sou-jenkins2.swinfra.net:8080/job/JobService/job/JobService~job-service-client~SCMOD-12730~CI


Dont work login

AttributeError: 'list' object has no attribute 'send_keys'
The browser remains on the page all the time
https://chat.openai.com/auth/login?next=/chat

I would like to help you if you can elaborate the issue. Can you share more details, please?


Missing commands

Hi guys,
Today it added amphp/redis to our project to replace the classic phpredis implementation. I noticed that a couple of commands are missing - e.g. zrangebyscore, zrevrangebyscore and others.
Those commands are quite simple to implement. Would you accept an MR? What are your requirements on tests etc?
Thanks :)

Looks like we forgot to close this after merging these commands in #77. Tagged as v1.1.0.

@trowski Seems like you didn't actually tag anything?

No, it seems I either forgot to push or the push failed. Since I didn't actually tag, should we review and make changes to #78, merge, then tag?

Aaron Piotrowski @.***> schrieb am Sa. 31. Dez. 2022 um
16:07:

No, it seems I either forgot to push or the push failed. Since I didn't
actually tag, should we review and make changes to #78
https://github.com/amphp/redis/pull/78, merge, then tag?
—
Reply to this email directly, view it on GitHub
https://github.com/amphp/redis/issues/76#issuecomment-1368239326, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACRAZ4FXSCJPV3IVQLVCMLWQBD2RANCNFSM6AAAAAAQZ7CN5E
.
You are receiving this because you authored the thread.Message ID:
@.***>


First draft of docs for streaming connector from Braze Currents

Believe I addressed all your feedback, please let me know if you have anything further.

Believe I addressed all your feedback, please let me know if you have anything further.

Looks good. I will bring this over to our internal repo

@jeffreystutz closing this PR. We've merged and published a copy on the internal repo here: https://experienceleague.adobe.com/docs/experience-platform/sources/ui-tutorials/create/marketing-automation/braze.html?lang=en Thanks for working on this!


boards: PCA10056: add board.c for nRF52840 PCA10056

Add board.c for nRF52840 PCA10056 to enable changes to regulator voltage
Current status:
Voltage set fixed to 3.3V, can be changed in board.c (current line 31)
Background:
If nRF52840 is fed by high-voltage input the low-voltage output will be 1.8V by default but then SWD won't work (because of the different voltage lvl)
I've added this because we don't actually use a PCA10056 but our own board which comes close to it - except that we only use high-voltage input. It won't harm to include it here (in PCA10056) as a reference for everyone to adopt, as I guess that PCA10056 will be the most commonly used starting point for anyone working with nRF52840.
ToDo:
Maybe implement the selectable voltage levels in config

@derchrismakaio you have a merge commit on your pull request. Please rebase instead to get rid of it: https://docs.zephyrproject.org/latest/contribute/contribute_guidelines.html#commit-guidelines

does this work?

Removed a few people from review who got there by initial incorrect submission which was later rebased. @derchrismakaio, In such cases, closing and submitting a new PR may be not that bad idea indeed.

Is this PR abandoned @chris-makaio ?

Closing this @chris-makaio . Pls, re-open if there is plan to continue working on it.


Testing - add backdoor testing for LogicApps integration tests

Adds some backdoor testing for test mocks (technically they were stubs, but with the backdoor testing they became mocks 😉).
Closes #107

Was the renaming of variables "resourceGroupName" to "resourceGroup" done on purpose to avoid overlapping internal resourceGroupName and test-variables? Or is this because I was late in the review-process.

Yeah was bc of overlapping. Case insensitive variables so we need them to be different variables to be sure that we assert the right ones.


Carousel Cycle as standard

Is it possible you guys could make the carousel.js cycle as standard? By adding a div class for those who only want the one slide cycle?

the single cycle is a bug in 2.0.1 and will be fixed with the release of 2.0.2 (hopefully this week)

Thank you!! I thought it was me!! :)


created aiaa template

I have created an aiaa template based upon the ones located here:
https://www.aiaa.org/events-learning/events/Technical-Presenter-Resources

Thanks for the contribution! Unfortunately, I can't merge it because this repository is only a temporary home for the five templates we built for the web app. To make the experience of using community templates as seamless as possible, we want to add special support for templates to the package manager. We ask for your patience while we're building the necessary infrastructure. Meanwhile, you could host the template on your own GitHub repository and open a PR to add it to https://github.com/qjcg/awesome-typst.

You have an IEEE one. Why not include the AIAA one? AIAA is the largest aerospace professional organization in the world. I think, if you're going to reject this template, then you should not have included the IEEE one. Oh well.

It's not about IEEE or AIAA. It's just that this is a "legacy" repository of a few templates we created in the beginning. It will be superseded by template support in the package manager and we'd be happy to have the AIAA template there once everything is ready.