Flavor selection should always appear when appropriate

Is your feature request related to a problem? Please describe.
Flavor select only appears when site is selected, this is confusing for users
Describe the solution you'd like
Always display flavor selection, disable flavor select button if no site is selected
Additional context
Result submission, result search

Resolved in c42b27088876cd16d076396eb8030ab2c036f2d4, flavor select will now always display, though disabled by default unless a site is selected


HHH-10059 Make EntityManagerFactoryBuilderImpl.populate(SessionFactor…

…yBuilder sfBuilder, StandardServiceRegistry ssr) protected
To be able to inject Spring managed interceptors into Hibernate, we need the
EntityManagerFactoryBuilderImpl.populate(SessionFactoryBuilder sfBuilder, StandardServiceRegistry ssr)
method to be protected.
This is a follow up of this discussion: http://markmail.org/thread/jslaxcep2j3v4cru .

I just did this directly.  I also went ahead and made all of the #populate methods here protected


add validator ETH addresses (ERC20)

This is a validator for ERC20 Ethereum (ETC) addresses.

@joe733
Please merge this PR first and merge #277 after that to avoid conflicts.

@msamsami, please make this PR do one thing. Create another PR to move btc_adderess.py.

@msamsami, please make this PR do one thing. Create another PR to move btc_adderess.py to validators/crypto_addresses.

@joe733
It's done. Here is the correct order for merging the PRs: #276 --> #277 --> #278

Tests have failed. Ref: https://github.com/python-validators/validators/actions/runs/5387269990/jobs/9778426797?pr=276#step:6:182
Also, please use black to format code. Ref: https://github.com/python-validators/validators/actions/runs/5387269990/jobs/9778426797?pr=276#step:6:203
Instead if you simply run tox, all of this could be resolved, locally.

@joe733 I added backend dependencies of eth-hash and reformatted code using black.

@msamsami thanks for the PR!


Change file hook handler to callback function

This commit removes the function hook part of hook_file and turns it into a callback execution instead. Regular hooks can still be applied through the callback, but it now also allows modifying non-function values.

Maybe call it mod:on_require to differentiate it from hooks, which are usually done on functions?

mod:on_require, at least to me, gives the impression that it's the callback handler for an event propagated by DMF.
Perhaps mod:require_callback or even mod:register_require_callback?

Perhaps mod:require_callback or even mod:register_require_callback?

With that name, I would expect that value to be the callback function, e.g. some_async_function(..., mod.require_callback).
I guess mod:hook_require would also work, as this is essentially what it does, and what people should use instead of mod:hook(_G, "require").

That's fair.
mod:hook_require seems enough to me.

Line 433 doesn't work as expected if more than one mod hooks the same file (the [mod_name] = {} initialization is skipped).
Recommend conversion to:
_file_hooks_applied_to_file[obj_str]           = _file_hooks_applied_to_file[obj_str] or {}     _file_hooks_applied_to_file[obj_str][mod_name] = _file_hooks_applied_to_file[obj_str][mod_name] or {}

Line 433 doesn't work as expected if more than one mod hooks the same file (the [mod_name] = {} initialization is skipped).
Recommend conversion to: _file_hooks_applied_to_file[obj_str] = _file_hooks_applied_to_file[obj_str] or {} _file_hooks_applied_to_file[obj_str][mod_name] = _file_hooks_applied_to_file[obj_str][mod_name] or {}

Good catch!

I've made the suggested changes to hook_require and fixed the initialization bug


Broken tests on armv7

I don't even know how it's possible for a pure Python package to break on a specific architecture, but it happens anyway.
Where the tests succeed on all other architectures I tried this on (x86, x86_64, ppc64le, s390x, aarch64), it fails only on armv7.
============================= test session starts ==============================
platform linux -- Python 3.8.2, pytest-5.4.1, py-1.8.1, pluggy-0.13.1
rootdir: /builds/PureTryOut/aports/testing/py3-scikit-optimize/src/scikit-optimize-0.7.4, inifile: setup.cfg
Fatal Python error: Aborted

Current thread 0xf7de0558 (most recent call first):
  File "/usr/lib/python3.8/site-packages/matplotlib/font_manager.py", line 991 in __init__
  File "/usr/lib/python3.8/site-packages/matplotlib/font_manager.py", line 1334 in _rebuild
  File "/usr/lib/python3.8/site-packages/matplotlib/font_manager.py", line 1343 in <module>
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 783 in exec_module
  File "<frozen importlib._bootstrap>", line 671 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 975 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 991 in _find_and_load
  File "/usr/lib/python3.8/site-packages/matplotlib/contour.py", line 16 in <module>
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 783 in exec_module
  File "<frozen importlib._bootstrap>", line 671 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 975 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 991 in _find_and_load
  File "/usr/lib/python3.8/site-packages/matplotlib/colorbar.py", line 31 in <module>
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 783 in exec_module
  File "<frozen importlib._bootstrap>", line 671 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 975 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 991 in _find_and_load
  File "/usr/lib/python3.8/site-packages/matplotlib/pyplot.py", line 32 in <module>
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 783 in exec_module
  File "<frozen importlib._bootstrap>", line 671 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 975 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 991 in _find_and_load
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1042 in _handle_fromlist
  File "/usr/lib/python3.8/site-packages/matplotlib/__init__.py", line 1280 in use
  File "/usr/lib/python3.8/site-packages/matplotlib/cbook/deprecation.py", line 358 in wrapper
  File "/usr/lib/python3.8/site-packages/matplotlib/cbook/deprecation.py", line 296 in wrapper
  File "/builds/PureTryOut/aports/testing/py3-scikit-optimize/src/scikit-optimize-0.7.4/skopt/plots.py", line 15 in <module>
  File "<frozen importlib._bootstrap>", line 219 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 783 in exec_module
  File "<frozen importlib._bootstrap>", line 671 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 975 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 991 in _find_and_load
  File "/usr/lib/python3.8/site-packages/py/_path/local.py", line 701 in pyimport
  File "/usr/lib/python3.8/site-packages/_pytest/doctest.py", line 483 in collect
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 264 in <lambda>
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 244 in from_call
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 264 in pytest_make_collect_report
  File "/usr/lib/python3.8/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.8/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 382 in collect_one_node
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 681 in genitems
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 684 in genitems
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 490 in _perform_collect
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 452 in perform_collect
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 257 in pytest_collection
  File "/usr/lib/python3.8/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.8/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 246 in _main
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 191 in wrap_session
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 240 in pytest_cmdline_main
  File "/usr/lib/python3.8/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.8/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.8/site-packages/_pytest/config/__init__.py", line 124 in main
  File "/usr/bin/pytest", line 11 in <module>
Aborted (core dumped)

This seems to have been resolved since 0.9.0 in combination with Python 3.10.


Not able to define an string ID

I tried defining an ID for my entity, where the ID is stored in the database as CHAR(50), using the following code:
public readonly partial record struct CRM_BS_ROLE_ID(string Value) : IStructId<string>;

However, it’s throwing an error
The type 'string' must be a non-nullable value type in order to use it as parameter 'TValue' in the generic type or method 'IStructId'

You don't need a T for string. Just implement IStructId with no type.


make a copy of a files inside "project explorer"

it would be nice if spyder can add the feature that we can  do copy and paste inside the "project Explorer" windows, or if we can do ctr+C and ctr+v

You mean to copy/paster files inside the Project Explorer?

yes

It's a good suggestion. We'll try to implement it after we release Spyder 4.


removed unused variables in app/models/miq_/

Removed two unused variables.

Coverage decreased (-20.4%) to 12.039% when pulling fc0bdd89daddcf475205ca3ce0a7bb69099c68a1 on ZitaNemeckova:unused_variables_in_miq into c253de196b6eb97106e7336d45c686937fe091af on ManageIQ:master.

Coverage decreased (-0.0008%) to 32.392% when pulling 38e3ed5942da2f691391d8393209abd64159c543 on ZitaNemeckova:unused_variables_in_miq into c253de196b6eb97106e7336d45c686937fe091af on ManageIQ:master.

@ZitaNemeckova commit message has [WIP] in it.  Please address

LGTM :+1:


fix: warn about dynamic import polyfill only during build

Description
Since we are enabling the dynamic import polyfill only during build, we can not reliably warn about an unneeded import 'vite/dynamic-import-polyfill'. We can also not detect the legacy plugin, since the user may want to enable this plugin only without the full legacy build. This PR removes this warning. See related discussion in #3434

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

We can actually safely warn during build, I restored the warning with this check


KAFKA-9451: Enable producer per thread for Streams EOS

Enabled producer per thread via KIP-447.

add configs to enable EOS-beta and for a safe upgrade from older versions
for eos-beta, create a single shared producer and StreamsProducer over all tasks
when committing, commit all tasks

Call for review @abbccdda @guozhangwang

Updated this PR. Call for review @abbccdda @guozhangwang

could we postpone the reordering of the ActiveTaskCreator tests and get it done in another PR?

The re-ordering itself should be small -- the main change is that the PR adds all missing tests (for existing and new functionality) -- hence, I am not sure if it would be good to extract it in it's own PR? -- maybe checkout the PR and only look at the final version of the test instead of the diff?

The re-ordering itself should be small -- the main change is that the PR adds all missing tests (for existing and new functionality) -- hence, I am not sure if it would be good to extract it in it's own PR? -- maybe checkout the PR and only look at the final version of the test instead of the diff?

Sounds good to me since I've bite it and reviewed the changes anyways :P

Updated this PR. @abbccdda @guozhangwang

Rebased to resolve merge conflicts. If no objection is raised, I will merge this after Jenkins build passed.

Triggered system tests: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/3839/

EOS system tests failed with  Transaction offset Commit failed due to consumer group metadata mismatch: Specified group generation id is not valid. -- Rebased this PR to pick up the fix for it that was merged yesterday.
Version Probing Upgrade test also failed with org.rocksdb.RocksDBException: lock : /mnt/streams/EosTest/0_2/rocksdb/KSTREAM-AGGREGATE-STATE-STORE-0000000003/LOCK: No locks available -- seems unrelated to this PR.
New system test run: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/3840/

StreamsUpgradeTest.test_version_probing_upgrade failed again (know as flaky).
Also the new StandbyTaskEOSIntegrationTest failed -- seems it fails 100% locally for me on this branch but is only flaky on trunk -- hence, we should not merge this PR atm to not break trunk completely \cc @abbccdda

@mjsax Actually John reported that the StandbyTaskEOSIntegrationTest is also flaky on trunk FYI


Cannot debug Python skill locally due to missing site.getsitepackges() in virtualenvs

Describe the bug
I'm getting this error when I want to test my Python based skill locally by clickung Run -> Start Debugging:

To Reproduce
I followed the instructions to test my Python based skill locally:
https://developer.amazon.com/de-DE/docs/alexa/ask-toolkit/vs-code-ask-skills.html#test
The error pops up when I click Run -> Start Debugging.
My virtualenv lives in ./venv and is Python version 3.6.9 on Ubuntu Linux 18.04. The ask-sdk-local-debug package is installed in this venv. It seems that the extensions uses site.getsitepackages() to get the list of installed packages. But that is not available in a virtualenv. This seems to be related:
https://github.com/pypa/virtualenv/issues/737
** launch.json **
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Debug Alexa Skill (Python)",
"type": "python",
"request": "launch",
"program": "${command:ask.debugAdapterPath}",
"pythonPath": "${command:python.interpreterPath}",
"args": [
"--accessToken",
"${command:ask.accessToken}",
"--skillId",
"${command:ask.skillIdFromWorkspace}",
"--skillHandler",
"lambda_handler",
"--skillFilePath",
"${workspaceFolder}/lambda/lambda_function.py"
],
"console": "internalConsole"
}
]
}
Extension Logs
[info - 2020-08-11 18:53:16.282Z] log level changed to debug
[debug - 2020-08-11 18:53:23.390Z] Calling method: ask.debugAdapterPath, args: [{"name":"Debug Alexa Skill (Python)","type":"python","request":"launch","program":"${command:ask.debugAdapterPath}","pythonPath":"/home/joerg/iubh_alexa/IUBH/venv/bin/python","args":["--accessToken","${command:ask.accessToken}","--skillId","${command:ask.skillIdFromWorkspace}","--skillHandler","lambda_handler","--skillFilePath","/home/joerg/iubh_alexa/IUBH/lambda/lambda_function.py"],"console":"internalConsole","cwd":"/home/joerg/iubh_alexa/IUBH","envFile":"/home/joerg/iubh_alexa/IUBH/.env","env":{"ELECTRON_RUN_AS_NODE":"1","GTK_CSD":"1","USER":"joerg","LANGUAGE":"de_DE","LC_TIME":"de_DE.UTF-8","XDG_SEAT":"seat0","XDG_SESSION_TYPE":"x11","SSH_AGENT_PID":"4310","SHLVL":"1","HOME":"/home/joerg","DESKTOP_SESSION":"pantheon","QT_STYLE_OVERRIDE":"adwaita","GTK_MODULES":"gail:atk-bridge","XDG_SEAT_PATH":"/org/freedesktop/DisplayManager/Seat0","LC_MONETARY":"de_DE.UTF-8","DBUS_SESSION_BUS_ADDRESS":"unix:path=/run/user/1000/bus","MANDATORY_PATH":"/usr/share/gconf/pantheon.mandatory.path","QT_QPA_PLATFORMTHEME":"gtk3","LOGNAME":"joerg","DEFAULTS_PATH":"/usr/share/gconf/pantheon.default.path","XDG_SESSION_ID":"c2","GDM_LANG":"de_DE","GTK3_MODULES":"pantheon-filechooser-module:pantheon-filechooser-module","PAPERSIZE":"a4","S_COLORS":"auto","LC_ADDRESS":"de_DE.UTF-8","XDG_RUNTIME_DIR":"/run/user/1000","XDG_SESSION_PATH":"/org/freedesktop/DisplayManager/Session0","DISPLAY":":0","LANG":"de_DE.UTF-8","XDG_CURRENT_DESKTOP":"Unity","LC_TELEPHONE":"de_DE.UTF-8","XDG_SESSION_DESKTOP":"pantheon","XAUTHORITY":"/home/joerg/.Xauthority","XDG_GREETER_DATA_DIR":"/var/lib/lightdm-data/joerg","SSH_AUTH_SOCK":"/run/user/1000/keyring/ssh","LC_NAME":"de_DE.UTF-8","SHELL":"/bin/bash","QT_ACCESSIBILITY":"1","GDMSESSION":"pantheon","LC_MEASUREMENT":"de_DE.UTF-8","GPG_AGENT_INFO":"/run/user/1000/gnupg/S.gpg-agent:0:1","LC_IDENTIFICATION":"de_DE.UTF-8","XDG_VTNR":"7","JAVA_HOME":"/usr/lib/jvm/java-8-openjdk-amd64/","PWD":"/home/joerg","ANDROID_HOME":"/home/joerg/Android/Sdk","XDG_DATA_DIRS":"/usr/share/gnome:/usr/share/pantheon:/home/joerg/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop","XDG_CONFIG_DIRS":"/etc/xdg/xdg-pantheon:/etc/xdg","LC_NUMERIC":"de_DE.UTF-8","LC_PAPER":"de_DE.UTF-8","QT_IM_MODULE":"ibus","XMODIFIERS":"@im=ibus","GNOME_DESKTOP_SESSION_ID":"this-is-deprecated","XDG_MENU_PREFIX":"gnome-","SESSION_MANAGER":"local/rog:@/tmp/.ICE-unix/4194,unix/rog:/tmp/.ICE-unix/4194","GIO_LAUNCHED_DESKTOP_FILE":"/usr/share/applications/code.desktop","GIO_LAUNCHED_DESKTOP_FILE_PID":"18035","CHROME_DESKTOP":"code-url-handler.desktop","ORIGINAL_XDG_CURRENT_DESKTOP":"Pantheon","VSCODE_NLS_CONFIG":"{"locale":"de","availableLanguages":{},"languagePackSupport":true}","VSCODE_NODE_CACHED_DATA_DIR":"/home/joerg/.config/Code/CachedData/91899dcef7b8110878ea59626991a18c8a6a1b3e","VSCODE_LOGS":"/home/joerg/.config/Code/logs/20200811T203240","VSCODE_IPC_HOOK":"/run/user/1000/vscode-f8c03cfe-1.47.3-main.sock","VSCODE_PID":"18035","LESSCLOSE":"/usr/bin/lesspipe %s %s","LESSOPEN":"| /usr/bin/lesspipe %s","LS_COLORS":"","NVM_BIN":"/home/joerg/.nvm/versions/node/v14.5.0/bin","NVM_CD_FLAGS":"","NVM_DIR":"/home/joerg/.nvm","NVM_INC":"/home/joerg/.nvm/versions/node/v14.5.0/include/node","":"/usr/share/code/code","AMD_ENTRYPOINT":"vs/workbench/services/extensions/node/extensionHostProcess","PIPE_LOGGING":"true","VERBOSE_LOGGING":"true","VSCODE_IPC_HOOK_EXTHOST":"/tmp/vscode-ipc-2f14383e-97a0-478e-a0ab-c5f67fc4c6ec.sock","VSCODE_HANDLES_UNCAUGHT_ERRORS":"true","VSCODE_LOG_STACK":"false","APPLICATION_INSIGHTS_NO_DIAGNOSTIC_CHANNEL":"true","PATH":"/home/joerg/bin:/home/joerg/.local/bin:/home/joerg/.nvm/versions/node/v14.5.0/bin:/home/joerg/bin:/home/joerg/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/joerg/Android/Sdk/emulator:/home/joerg/Android/Sdk/tools:/home/joerg/Android/Sdk/tools/bin:/home/joerg/Android/Sdk/platform-tools:/home/joerg/flutter/bin:/home/joerg/Android/Sdk/emulator:/home/joerg/Android/Sdk/tools:/home/joerg/Android/Sdk/tools/bin:/home/joerg/Android/Sdk/platform-tools:/home/joerg/flutter/bin","PYTHONIOENCODING":"UTF-8","PYTHONUNBUFFERED":"1"},"stopOnEntry":false,"showReturnValue":true,"debugOptions":["ShowReturnValue","RedirectOutput"],"justMyCode":true,"workspaceFolder":"/home/joerg/iubh_alexa/IUBH","redirectOutput":true}]
[debug - 2020-08-11 18:53:26.326Z] Successfully uploaded telemetry data.
Expected behavior
Being able to test the skill locally.
Desktop (please complete the following information):
OS: Linux x64 4.15.0-101-generic
Visual Studio Code Version:  1.47.3
Alexa Skills Toolkit Version: 2.0.0
Git Version: git version 2.17.1

Hey @joerg86 , thanks for reporting this issue. Looks like virtualenv has problems figuring out site packages in Linux environments, since the same code works fine in virtual envs in Mac/Windows. Anyways, as mentioned in the underlying issue that you tagged, we definitely need a better way to check if the local debug package is installed in the python interpreter selected.
Since this is related to virtualenv issues, to get unblocked, can you install the ask-sdk-local-debug package to the global site-packages location and change the interpreter to use that instead?

Hi @nikhilym , thanks for the super fast response. Yes, installing ask-sdk-local-debug and switching to the global interpreter fixes the issue. However, this would then force me to install all my skill's python requirements globally which is really problematic (version conflicts etc.).
Anyway, good news: I have solved the problem.
It seems like the virtualenv (from python3-virtualenv deb package) shipped with Ubuntu 18.04 is outdated and the problem is solved in newer versions. After doing a sudo pip install --upgrade virtualenv followed by deleting and rebuilding my virtualenv everything works fine (virtualenv version 20.0.30).
Sorry for bothering you with that! Anyway, we now have a documented solution - just in case anybody else runs into this problem.
Thanks,
Jörg

Oh wow, thanks for the update @joerg86 . This should definitely be added in your FAQs then. I was about to do more research on this, but glad that you figured this out.
Closing this ticket at the moment. Please let us know if you face any problems with the extension or your general feedback about it 😄


no session provider 'mysql'

Gitea version (or commit ref): 1.4.0
Git version: 2.7.4
Operating system: Ubuntu 17.04
Database:

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist: https://gist.github.com/donlui/a91a6ad3bc22e5198db9132742d1d865

Description
when i try use mysql session provider, gitea print error
panic: session: unknown provider 'mysql'(forgotten import?)

Currently only values memory, file or redis is supported for session storage. Probably we need to update github.com/go-macaron/session dependency to support this...


Add mockserver endpoints

Codecov Report

Merging #190 (60cab89) into main (5af8f94) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #190      +/-   ##
==========================================
- Coverage   19.39%   19.32%   -0.08%
==========================================
  Files          12       12
  Lines        1593     1599       +6
==========================================
  Hits          309      309
- Misses       1253     1259       +6
  Partials       31       31

Impacted Files
Coverage Δ

client/mockserver.go
76.00% <0.00%> (-24.00%)
:arrow_down:

Continue to review full report at Codecov.

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


Add extensions to gradle plugin

Description
In order to run integration testing for the SDK and future extensions, the OpenSearch gradle plugin needs to be able to run both extensions and plugins at the same time.  This PR adds the capability to run extensions from the gradle plugin, while leaving all existing plugin functionality untouched.
Issues Resolved
https://github.com/opensearch-project/opensearch-sdk-java/issues/589
Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This doesn't only affect extensions, so should I add a changelog entry?

LGTM!
Looking at this code, I am wondering whether we should extract the connectivity parts of an extension into an interface? I suspect that for in-proc we will not want host/port as a communication channel. WDYT?

Makes sense. Definitely they have to be APIs. And abstract out inner structures. We started with something very simple, its about time to build these changes.


Add the Swagger client for activiti-rest

We should add a new Maven module for generating the Swagger client using the Open API specs provided by the activiti-rest.war

Released in v1.0.1:
https://github.com/OpenPj/activiti-sdk/releases/tag/v1.0.1


Card Rendering Fails with Re-Sizing Safari Browser Window

I don't know fully how to reproduce this bug or the extent of it - basically I have seen weird behavior with cards loading (or not loading) across several apps running both locally and in the H2O.ai Cloud.
This has come up when I load an app with my safari browser about half screen size (because I am screen recording safari and PyCharm).

Sentiment Analysis App Running in H2O AI Cloud
I could not see all of the cards and there was no scroll, so I make safari full screen. The browser widened but the app did not:

Credit Risk App running locally (I am not sure if this app has responsive layout or not)
When half screen cards do not load, if I widen the browser they are appear and then stay after I narrow it
https://h2oai.slack.com/files/UFY03NQ4V/F01GUFGRJTW/screen_recording_2020-12-10_at_1.29.37_pm.mov

I will keep adding examples and details to this issue as they come up - I know this is pretty vague at this point but I'm not seeing a lot of rhyme or reason

Hi @mtanco, could you please check if you can still reproduce these? I had no luck with repros.
1 seems like Safari didn't manage to expand correctly, not something we can fix. I couldn't repro this though.
2 I didn't manage to repro even with video provided. I couldn't find Credit Risk on HAC, so tried only locally.
https://user-images.githubusercontent.com/64769322/106458049-1d9f9d00-6490-11eb-85a9-b4e528d8a58b.mov

@mtanco Is this still relevant? If not, we can close.


Don't work - ERROR! This extension can only download protected PDFs from google drive. It doesn't work on this site!

Don't work in Chrome and Edge.

Which site did you try to download the PDF on? Please look at your URL. If it's drive.google.com/file/d, it should download the PDF. If it doesn't, you may be viewing a PDF from your Google Drive, click "Open in new window" on the three-dot menu and try downloading again.


[WIP] Add ssh keys capability to furyagent

Hi  👋 !
the purpose of this pr is to move the management of the ssh keys to furyagent.
I have currently introduced the following behaviour:

furyagent init ssh-keys => will copy to bucket folder the local ssh/ssh-users file structured as follow:

githubuser1
githubuser2
....
githubuserN

furyagent configure ssh-keys => basically will download from the bucket the previous file  and setup the github.keys for every user listed in the authorized_keys of ubuntu user

Missing task to be added that i need to handle:

add the default key as external parameter to be pass from ClusterComponent SSHkey struct

and probably more, i look forward for your thoughts and suggestions 🙏

LGTM, let me know when we can see this in action with a demo 🥇

can we go ahead with this, or is missing anything ?


Supporting Spring Cloud 2023.x and Spring Boot 3.2.x

Spring Cloud has officially announced its first 2023 stable release - 2023.0.0 at the beginning of the last month of 2023. Together with this version, it also had the underlying Spring Boot upgraded to 3.2.x while still requires JDK 17 as the lowest JDK version.
So based on the regular plan and also the voices we hear recently from the community, I think it's time to add the Spring Cloud Alibaba 2<IP_ADDRESS> release to the schecule. Along with Spring Cloud and Spring Boot upgrading, we will also have the core SCA components upgraded to their latest major versions respectively:

Nacos, 2.3.0
Sentinel, 1.8.7
Seata, 2.0.0
RocketMQ, 5.1.4

References:

Spring Cloud Release Train
Spring Cloud 2023.0 Release Notes
Spring Boot 3.2 Release Notes

要加快了，spring 3.2是最重要的一次更新，支持了jdk21的虚拟线程。
我估计很多公司都会趁着这次机会全面迁移到jdk21。

pls assign to me, I will completed.

Sentinel 1.8.7 does not currently support Spring 6.x ( Sentinel 1.8.6 Adopting a temporary solution ).
I will follow up on this.

Sentinel 1.8.7 does not currently support Spring 6.x ( Sentinel 1.8.6 Adopting a temporary solution ). I will follow up on this.

Sure, we can stick to the version that is proved to work well with Spring 6.x, not necessarily need to be the latest version.

When do you plan to release versions that are compatible with Spring Cloud 2023. x and Spring Boot 3.2. x? I can't wait anymore

RocketMQ reference documentation https://www.yuque.com/spring-cloud-alibaba/xgu1l3/mqxn9k

2023.0.0得RC 请问有定期吗

建议等Nacos 2.3.1， Seata 2.1.0修复bug版本再一起发布吧

2023.0.0得RC 请问有定期吗

2<IP_ADDRESS>-RC1 发布了，可以试一下


urgently need this feature for iOS

Hi, how soon can we have this feature available on iOS?  We urgently need this for our app that will allow students to learn a language.  Isn't it a backend option? So it shouldn't depend on the device/language?
Thanks

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1ee95b20-a793-b370-f7a0-5661e9b2b569
Version Independent ID: 5a83c187-fad2-e1cb-e3cb-8af69b3edf83
Content: How to use automatic language detection for speech to text - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/how-to-automatic-language-detection.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @SusanHu
Microsoft Alias: qiohu

@ShakAttacked Do you mean a support of the speech sdk for iOS? The speech SDK reference for iOS using Objective-C reference is available here

Hi
No I mean the support of multiple language in detection. There is no way to pass array of languages in the config. I’m using swift.
Sent from my iPhone

On 11 Mar 2020, at 16:53, RohitMungi-MSFT<EMAIL_ADDRESS>wrote:

@ShakAttacked Do you mean a support of the speech sdk for iOS? The speech SDK reference for iOS using Objective-C reference is available here
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ShakAttacked Yes, this feature is only available for the Speech SDK for C#, C++ and Java. We are checking internally to understand if there are any plans to implement the same for other SDKs and will update this thread as soon as we have more information.

Thank you.  It’s quite urgent please. Students will be studying from home as of next week and we want to help them study at home. Thank you so much.
Sent from my iPhone

On 12 Mar 2020, at 06:05, RohitMungi-MSFT<EMAIL_ADDRESS>wrote:

@ShakAttacked Yes, this feature is only available for the Speech SDK for C#, C++ and Java. We are checking internally to understand if there are any plans to implement the same for other SDKs and will update this thread as soon as we have more information.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ShakAttacked We currently do not have visibility of this implementation on iOS. We have provided feedback to our team and will post an update on this thread when it is avialable.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply.


feat: Update borders color

Description
fixes #581
Demo

Checklist:

[x] I have read and followed the Contributing Guide
[x] lighten border color

In general LGTM. It was hard to test pr in the testnet, it trows 404 issue again and again.

Thank you! I see, we will improve it. In such scenarios as UI fixes, not related to any network, checking the testnet deployment is not important


Fix MAV_FRAME_MISSION usage

Fix for Issue #2984

It might be worthwhile to add back support for local-coordinates in AUTO missions at the same time.

The local frame is a fringe use case requiring someone with enough commitment to maintain it. Since that doesn't seem on the horizon we rather shouldn't add unmaintained and untested features.


Script error

A number of users are encountering a 'Script error.' on line 0. Reading around, the suggestion is that this is the result of an error thrown within a cross-site script and that, as a result, we get no further information (see http://blog.errorception.com/2012/04/script-error-on-line-0.html).
Unfortunately it's not acceptable to simply ignore these errors as they often result in the application failing to load. Presumably a crash somewhere within the Google Drive client libraries?

It seems that at least one of the causes for this is:
Failed to load resource: the server responded with a status of 401 (Unauthorized)

This occurs occasionally when querying Google Drive.

Not see this in a long time. Closing.


fix: use total duration of timedelta objects

This PR fixes a bug where the py-rattler solver timeout did not use the entire duration of the timedelta object.
edit: With this fix, it should work. The hack I was using to get around this bug doesn't work and so the solver thought I passed a timeout of zero.

@wolfv This one is ready for review. There is still a bug somewhere else, but we can merge this fix right away.

Hmm, strange - I just checked the code, and we do in fact convert in Rust to a
timeout: timeout.map(std::time::Duration::from_micros),

So not sure what would have been wrong with the code before.

IDK what that code snippet means.
However, this is a pure-python fix. The time timedelta object holds different amounts of time like this
In [23]: td = datetime.timedelta(seconds=100)

In [24]: td.microseconds
Out[24]: 0

In [25]: td.total_seconds()
Out[25]: 100.0

In [26]: td = datetime.timedelta(seconds=100, microseconds=10)

In [27]: td.microseconds
Out[27]: 10

In [28]: td.total_seconds()
Out[28]: 100.00001

So the .microseconds attribute only holds the microseconds part of the timedelta. It does not have the total timedelta in microseconds. For the total duration, you need to call .total_seconds().

Yep, I also double checked. Your conversion has one 0 too many though. The Python docs suggest to use teh following:
duration / datetime.timedelta(microseconds=1)

Do you want to push the fix or should I?

🤦♂
will fix.

I'll merge it right away! Thanks for spotting.

Thank you for the review!

FYI the tests are not running here. I didn't know if you noticed or not, so please ignore if this is noise. :)

Yup, thanks for pointing that out :) merged! Hopefully we can get a fix tomorrow for the constraints and then we'll make a new release.


Promtail saturates CPU

Describe the bug
Promtail saturates CPU
To Reproduce
Steps to reproduce the behavior:

Install Promtail
Start it
Run Loki
Check CPU usage of the Promtail container

Expected behavior
Promtail should not saturate
Logs
Include any relevant logs

Environment (please complete the following information):

Add-on version: 1.6.1
Supervisor version: supervisor-2021.06.8
Operating system Home Assistant OS 5.4.83-v8

Additional context

I would need to troubleshoot promtail process.

I've noticed that I had to leave it running for a while before getting ok. I think it was saturating because of the indexing operation at the first bootstrap.

Hm so when you first turn this addon on assuming your using the default config it will start going through your entire systemd journal. Everything on your system logs there and it survives restarts so that is a lot of information to go through.
So if you just turned it on on an rpi or something you've had running stuff for a while it doesn't seem that surprising that it would have a lot of work to do indexing all the existing logs. Eventually it should catch up to reality and stabilize. Maybe let it run for a bit longer to see if it levels out? Or could try clearing out your journal to let it start from a blank slate if you just want to index from here on out.
Not entirely sure what I can do about it otherwise though. Promtail isn't my software, I just repackaged it in a form compatible with home assistant. So if it continues to chew up unbounded cpu you'll likely have to report an issue on the loki+promtail repo.

Now everything looks fine

And promtail is doing its nice job.
Thanks @mdegat01
We can close this


site/src/cdk-outputs.json file is missing

Describe the issue
I didn't see cdk-outputs.json file in site/src. Please let me know is it missing in the repo or it will generate by a command.
Steps to Reproduce
N/A
Current behavior
ERROR in ./src/Config.js 9:0-44
Module not found: Error: Can't resolve './cdk-outputs.json' in '/Users/vend/Documents/Projects/amazon-chime-sdk-click-to-call/site/src'
resolve './cdk-outputs.json' in '/Users/vend/Documents/Projects/amazon-chime-sdk-click-to-call/site/src'
using description file: /Users/vend/Documents/Projects/amazon-chime-sdk-click-to-call/site/package.json (relative path: ./src)
Field 'browser' doesn't contain a valid alias configuration
using description file: /Users/vend/Documents/Projects/amazon-chime-sdk-click-to-call/site/package.json (relative path: ./src/cdk-outputs.json)
no extension
Field 'browser' doesn't contain a valid alias configuration
/Users/vend/Documents/Projects/amazon-chime-sdk-click-to-call/site/src/cdk-outputs.json doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/Users/vend/Documents/Projects/amazon-chime-sdk-click-to-call/site/src/cdk-outputs.json.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/Users/vend/Documents/Projects/amazon-chime-sdk-click-to-call/site/src/cdk-outputs.json.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/Users/vend/Documents/Projects/amazon-chime-sdk-click-to-call/site/src/cdk-outputs.json.wasm doesn't exist
as directory
/Users/vend/Documents/Projects/amazon-chime-sdk-click-to-call/site/src/cdk-outputs.json doesn't exist
@ ./src/App.js 24:0-41 28:18-31 29:14-27
@ ./src/index.js 3:0-24 9:92-95
webpack 5.73.0 compiled with 1 error in 31711 ms
AWS SDK version used
"amazon-chime-sdk-js": "3.4.0",
Operating System and version
macOS Monterey (ver:12.4)

That file should be created when the yarn launch command is run.
https://github.com/aws-samples/amazon-chime-sdk-click-to-call/blob/07da19e04b5cd8a3bc0b30427ba6ccde388e54af/.projenrc.js#L28
Previous versions used ./deploy.sh instead, but in both cases the deploy output should create that file.

That might be a permissions issue with the account you're using to deploy with.  Can you check the IAM permissions on that account?  Or hardcode it here: https://github.com/aws-samples/amazon-chime-sdk-click-to-call/blob/07da19e04b5cd8a3bc0b30427ba6ccde388e54af/src/amazon-chime-sdk-click-to-call.ts#L48

Closing


New OIC demo and commits necessary to support it - v2

Changelog:

Adding commit a000a76af

Scanning was not working as expected in previous branch because coap was ignoring all replies after the first one. So multicast packets that expects response from several servers was failing.
We had some discussions on how to have a good way of informing sol-coap that a reply is no longer needed. The fist step, that is implemented in a000a76af is to look at the return of reply_cb.
We still need to have a function to let users cancel a request, a way of stoping waiting for replies when a timeout occurs and support for cancelling observer requests. And also there are a leak in reply elements that need to be fixed.
I sent the pr because with this commit because now demo is working, the light-client.fbp demo was fixed and this make sense even without implementing the full strategy we discussed.
Replaces #1021

@bdilly commented on Nov 6, 2015, 6:58 PM GMT-2:

How is this oic_res lifecycle? Do you really need to duplicate this string? No way to ref it or something like that?

For each device that's found on the network, a resource is created with refcount = 1, the user callback is called, and then the ref count is decremented. If the user wants to use the resource, they need to grab their own reference, or else this will destroy the resource.


Concerns with zip version 1.x

I am working on packaging uv for Fedora Linux. Currently, we are wary of updating the zip crate past version 0.6.x (and will hold off on doing so for now) due to concerns with how the zip-rs project project is being handled:
All releases starting with v1.0.0 were developed and released by different people than the original crate, with the hand-off being handled in a kind of weird way. Additionally, releases 1.2.0+ of the "new" zip crate contain breaking API changes which are not going to be fixed in the 1.x series.
Since uv can be made to work with version 0.6.6, would it be possible to either:

depend on zip 0.6.6 for now, if you decide you share these concerns, or:
at least relax the dependency to something like >=0.6.6, <2.0 to explicitly allow building with both zip v0.6 and v1?

Note that the zip crate maintainer is planning a 2.0 release in a couple of weeks.
In order to build with zip 0.6.6, with tests passing, one source change is necessary:
https://github.com/astral-sh/uv/blob/39af09f09b89611953f503927499b4129091bf68/crates/install-wheel-rs/src/wheel.rs#L14
needs to be use zip::write::FileOptions as SimpleFileOptions, since the SimpleFileOptions alias was added in 1.x.
If the uv project decides to change nothing, I will just carry a small downstream patch to support zip 0.6.6 for the time being.

See also: https://github.com/PyO3/python-pkginfo-rs/issues/13

We're still considering this as a team, but it seems likely we'd pin until we have more details. Would you be willing to open a pull request?

We're still considering this as a team, but it seems likely we'd pin until we have more details. Would you be willing to open a pull request?

Sure! I hope https://github.com/astral-sh/uv/pull/3645 is what you needed. Thanks for considering this.

In https://github.com/astral-sh/ruff/pull/11779, we're adding zip as a dependency to Ruff as well, for red-knot. For now we're pinning it to the same version that uv has it pinned to.


update to mollify Elixir 1.2 compiler warnings

Prior to this commit, when compiled with Elixir 1.2, the compiler would
generate various warnings, mostly about ambiguous parameters near |>.
This commit adds parens to be explicit about additional parameters when
used with |>. This commit also adds a few other minor changes in
response to a handful of other minor compiler warnings.

Thank you so much @jeffweiss !


Travis CI for python - Linux only, since mac not supported

Linux

[x] python 3.5
[x] python 3.5 dev
[ ] 3.6
[ ] 3.6-dev
[ ] 3.7-dev

Why is 'mac not supported'?

Issue completed in #213.


DCOS-8106: Fix column order on service detail page

This PR fixes the order of the columns in the service detail page.

Reviewer: @MatApple

LGTM 🚢


Git view report wrong number of changed files

In my git view of vscode, it shows there are two files changed but actually there is no change. See below screenshot. The git command line also gives no change. I am using vscode 1.25.0 on Mac OS.

My bad. there are multiple source repositories loaded into my workplace. And vscode shows the correct number.


2023-11-21 Forward merge master into release/7.0

Forward merging changes merged into master that are missing from release/struts-7-0-x.

This will clean up the diff for other PRs targeting release/struts-7-0-x. (They shouldn't need to cherry-pick these changes into their PR)


fix: Taps running in parallel use a different temporary catalog file

Description

Related Issues

Closes https://github.com/meltano/meltano/issues/8763

I believe we need to handle the meltano run command with a --state-id-suffix or use a meltano el command with a --state-id to provide uniqueness regardless of the command which is issued.
I am not sure whether the targeted changes are just for the meltano run command or whether it will help with the meltano el commands as well.


Add category for extension

The extension interface adds support for specifying a category in version 0.2.0.
We must upgrade to the latest interface version and configure category cloud-storage.
See also https://github.com/exasol/extension-manager/issues/100 and https://github.com/exasol/extension-manager-interface/issues/42

Closed with https://github.com/exasol/cloud-storage-extension/pull/262


[expo] Unable to resolve "@openauthjs/openauth/client"

reproduction workflow

create an expo app

npx create-expo-app@latest

for info, the tsconfig of the expo app will be https://github.com/expo/expo/blob/main/packages/expo/tsconfig.base.json

now import createClient like documented at https://github.com/openauthjs/openauth?tab=readme-ov-file#auth-client

import { createClient } from "@openauthjs/openauth/client"

You will get the error
Cannot find module '@openauthjs/openauth/client' or its corresponding type declarations.
  There are types at<EMAIL_ADDRESS>but this result could not be resolved under your current 'moduleResolution' setting. Consider updating to 'node16', 'nodenext', or 'bundler'.

I update the tsconfig.json of the project accordingly

{
  "extends": "expo/tsconfig.base",
  "compilerOptions": {
     "moduleResolution": "bundler",
   ...
   }
}

The type error disappear, but now I get an error at build time
iOS Bundling failed 4901ms<EMAIL_ADDRESS>(1285 modules)
Unable to resolve "@openauthjs/openauth/client" from "app/(tabs)/index.tsx"

apparently I'm not the only one. a user found a workaround, which is to copy the client in a local context, along with the files it depends on:

session
utils
error
pkce

https://gist.github.com/xinha-sh/723fae6bad78a303bbaeeb2b41634c76


Add compatibilty for TechReborn's implementation of EU

Hello!
I understand that universal cables are compatible with IC2's EU but they don't seem to work with TechReborn's EU. I'm testing this with Mek 1.10-9.1.0
Screenshot can be seen here: http://i.imgur.com/feLfCr1.png
Their curseforge: http://minecraft.curseforge.com/projects/techreborn
Their repo: https://github.com/TechReborn/TechReborn/tree/1.10
Please let me know if I've neglected any important information

I'm going to stick with IC2's still-maintained API for now.  Perhaps I'll add support for TechReborn later if necessary.


[DNM] boards: arm: add nrf52840_pca10059

This PR adds support for the nrf52840_pca10059 board.
The flash partitions are configured to allow migrating from the stock,
factory-programmed bootloader to MCUBoot.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #8812   +/-   ##
=======================================
  Coverage   52.34%   52.34%
=======================================
  Files         195      195
  Lines       24723    24723
  Branches     5139     5139
=======================================
  Hits        12941    12941
  Misses       9708     9708
  Partials     2074     2074

Continue to review full report at Codecov.

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

Since this is a new board, I think we should move some of the HW configuration (UART pins, LEDs, buttons) to DTS.

Hi, @dbkinder I addressed your comments :)

@lemrey #8912 is now merged, can you rebase?

@carlescufi Rebased.
@ioannisg Revised storage partitions in DTS.
@thedjnK Corrected the documentation.

@ioannisg @mike-scott @dbkinder please re-review


Change nautic miles to kmh

Hello,
thanks or great work.
Is it possible to change the incoming data for speed of my tracker to km/h? I use the tk103 protokoll. The tracker delivers speed in nautic miles and i whant to see it in km/h.
Thanks for helping.
ThoGo

You can change units in the web interface. Check account or server settings.

thanks, that is right in /preferences/speed unit.
Of wikepedia https://en.wikipedia.org/wiki/Knot_(unit)
1 international knot =
1 nautical mile per hour (by definition),
1.852 kilometres per hour (exactly),[3]
0.514 metres per second (approximately),
1.151 miles per hour (approximately),
20.254 inches per second (approximately).
So my traccer transmited 0.2699785 nmh or knot than traccar has to show 0,5 km/h 0,26knots and 0,31mph. But traccar shows only 0,4 km/h, 0,22 knots and 0,25 mph.
How can i change the factor or do i make a mistake.
Thanks
ThoGo

Here is the code:
https://github.com/tananaev/traccar/blob/master/web/app/store/SpeedUnits.js
Values are correct as you can see. Are you sure you are looking at the same position instance in the web interface and database?

thanks, sorry for late answer. I think it is my tracker. I use the tk20 (vjoy or kingneed) with protokoll tk103. This thing transmit something like 0.05399570000000001 this. And when i export it of mysql, it is ugly in excel. And why not for trackar too. I think i wait for protokoll update. Thanks a lot ThoGo

Traccar converts all data into knots, that's why you see so many decimal digits. You should probably round them if you want to export data into excel.


Disable uncorrectable unsafe cops when using --safe-auto-correct --disable-uncorrectable

…sable-uncorrectable
Replace this text with a summary of the changes in your PR.
The more detailed you are, the better.

Before submitting the PR make sure the following are checked:

[ ] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[ ] Feature branch is up-to-date with master (if not - rebase it).
[ ] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[ ] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[ ] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

Just a heads' up, I'll be merging #7868 today, so you'll get merge conflicts, you may want to wait a bit before working some more on this.

Merged! You'll find the code in cop/base.rb now

Thanks! I actually just wanted to run this against the test suite, doesnt work the way I wanted it to anyway 😄 Delighted that PR is merged, nice work!


[feaLib.variableScalar] fix value_at_location() method

VariableScalar's value_at_location() method is untested and unused, but I find it useful (if only for playing and testing) and found that it's broken. I fixed it, but that makes an assumption about the intended call signature: I assume the intention was to feed it a location dict in user coordinates.

Tangent: It really sucks that Adobe people decided to add user-space variable values to the .fea format, since those can't work with avar2.

I also don't quite like it, but given that fvar is all that's guaranteed to available during compile time, I can understand it.
I'm also not quite sure what the fundamental problem is: these coords get normalized without applying any avar, and that allows us to express everything that's needed, even if the coords aren't in designspace coords. These coordinates are effectively source coordinates, even if they are expressed in user coordinates. Not sure I'm expressing myself very clearly :)

I'm also not quite sure what the fundamental problem is: these coords get normalized without applying any avar, and that allows us to express everything that's needed, even if the coords aren't in designspace coords. These coordinates are effectively source coordinates, even if they are expressed in user coordinates. Not sure I'm expressing myself very clearly :)

Well if avar is not applied, then the "user" values mentioned in the .fea file won't actually match the observed user value coordinates. Eg. you say "switch to this other shape at wght=700" but then avar maps wght=700 somewhere different from what the .fea compiler does...

But the fundamental issue is that with avar2, any point in the user space can be mapped to a point in the normalized space. But the same is not necessarily true about an orthogonal plane. That is to say, there might not be a simple formulation of 'wght >= 700' if eg. the font is a parametric design.

Any thoughts on this PR, @simoncozens, @anthrotype?

Thanks!

It really sucks that Adobe people decided to add user-space variable values to the .fea format, since those can't work with avar2.

to be fair, the variable scalar proposal came from @simoncozens, who also implemented it in fonttools, not from "Adobe people", and it's not even officially in the FEA spec (https://github.com/adobe-type-tools/afdko/issues/153, https://github.com/adobe-type-tools/afdko/pull/1350).


No documentation for db init and migration

I'm finding myself struggling with finding answers about how to init my db and doing migrations.
Eventually I managed to use the sequelize migrations with typescript in a type safe way, but there are more things sequelize-typescript related that I still haven't figured out and I feel it would be of great help to add them to the readme. All related to DB init and migrations:

What type and best way to define the default Id type? flags (autoincrement, primarykey...)
How to define the temporal timestamps types? (createdDate, updatedAt, deletionDate) + flags (most importantly, default values)
** I can probably think of more stuff but these 2 are the ones I'm currently facing

I feel that the init & migrations should be handled more gracefully with this lib. Generally speaking It would be great if the migration script could be generated from the annotations

Yes! I really like using sequelize-typescript, but this is the one thing I cant figure out how to do in an easy way.

I'm in the same boat. Looking at sequelize-cli-typescript now, but I cannot get it to work yet.

@hmol Do you rewrite your schemas in that migration file or does it generate for you, mine did generate a file but it just has some instructions on how to do the migration instead of actually detecting that would be so much to expect I guess.
@FreifeldRoyi Can you elaborate the safe way you mentioned please.

@ertankara Unlike the official sequelize manual, I used the DataTypes and QueryInterface types from sequelize to create the functions:
import { DataTypes, QueryInterface } from 'sequelize';
export async function up(qi: QueryInterface) {
   try {
       const ret = await qi.createTable('table_name', {id: {type: DataTypes.UUID, primaryKey: true, defaultValue: DataTypes.UUIDV4}})
       // .......
   } catch (e) {
       console.error(e);
       throw e;
   }
}

It's not that it's REALLY typesafe, but at least I can get better code completions.
What I'd like to get is some automatic way to map between the decorators, already defined with this project, to create the db or generate the migration script.
Or at least a documentation on how to map the decorated fields to the migrations script

@ertankara I am using the following command for migrations:
tsc src/database/migrations/* --outdir dist/migrations && npx sequelize-cli db:migrate --url 'postgres://'$(dotenv -p DB_USERNAME)':'$(dotenv -p DB_PASSWORD)'@'$(dotenv -p DB_HOST)':'$(dotenv -p DB_PORT)'/'$(dotenv -p DATABASE)'' --migrations-path dist/migrations
As I am using dotenv-cli along with dotenv package for reading .env file, I can read the database credentials from .env and create the postgresql url easily. We do not need a configuration file if --url flag is used. What do you think about this solution?
Sample migration script (src/database/migrations/16085945884-test.ts)
`import { DataTypes, QueryInterface } from 'sequelize';
export async function up(qi: QueryInterface) {
try {
await qi.addColumn('PaymentMethods', 'number', {
allowNull: true,
type: DataTypes.DOUBLE
})
// .......
} catch (e) {
console.error(e);
throw e;
}
}
export async function down(qi: QueryInterface) {
try {
await qi.removeColumn('PaymentMethods', 'number')
// .......
} catch (e) {
console.error(e);
throw e;
}
}`

@ertankara I am using the following command for migrations:
tsc src/database/migrations/* --outdir dist/migrations && npx sequelize-cli db:migrate --url 'postgres://'$(dotenv -p DB_USERNAME)':'$(dotenv -p DB_PASSWORD)'@'$(dotenv -p DB_HOST)':'$(dotenv -p DB_PORT)'/'$(dotenv -p DATABASE)'' --migrations-path dist/migrations
As I am using dotenv-cli along with dotenv package for reading .env file, I can read the database credentials from .env and create the postgresql url easily. We do not need a configuration file if --url flag is used. What do you think about this solution?
Sample migration script (src/database/migrations/16085945884-test.ts)
`import { DataTypes, QueryInterface } from 'sequelize';
export async function up(qi: QueryInterface) {
try {
await qi.addColumn('PaymentMethods', 'number', {
allowNull: true,
type: DataTypes.DOUBLE
})
// .......
} catch (e) {
console.error(e);
throw e;
}
}
export async function down(qi: QueryInterface) {
try {
await qi.removeColumn('PaymentMethods', 'number')
// .......
} catch (e) {
console.error(e);
throw e;
}
}`

Well, on behalf or our tribe, you're welcome @piyusharora1989, but it seems you meant to thank @FreifeldRoyi

Well, on behalf or our tribe, you're welcome @piyusharora1989, but it seems you meant to thank @FreifeldRoyi

Yeah I meant to thank @FreifeldRoyi  :)

Yeah I meant to thank @FreifeldRoyi  :)

@zhangchi1, Seems you (too) meant @FreifeldRoyi and not me :)

Well, I don't get what the result of this discussion is. Have you found a way to use migrations?

+1 following, useful link
https://stackoverflow.com/questions/21105748/sequelize-js-how-to-use-migrations-and-sync


Won't work if the path contains Chinese.

When TerminalFinderButton was pressed, if directory ~/tem/测试 was selected, terminal will show following error:

$ cd "/Users/koc/tem/æµ^Ëè¯^Õ/";clear;
cd: no such file or directory: /Users/koc/tem/æµ\M-^Kè¯\M-^U/

I believe it's a best practice to create directories with ASCII. 😄 Thus I won't try to fix this bug.


Always panics: Incorrect Key on x86_64

This crate is used in keepass-diff , I'm trying to check diffs with my two out of sync  .kdbx(kdbx4) its about 9-11Mb , but it always shows incorrect key specified. Built from aur https://aur.archlinux.org/packages/keepass-diff
This is the full backtrace.
thread 'main' panicked at 'Error opening database A: IncorrectKey', src/main.rs:117:18
stack backtrace:
0:     0x55b96a052cbd - <unknown>
1:     0x55b96a07013c - <unknown>
2:     0x55b96a050931 - <unknown>
3:     0x55b96a0544b5 - <unknown>
4:     0x55b96a0541d1 - <unknown>
5:     0x55b96a054a46 - <unknown>
6:     0x55b96a054937 - <unknown>
7:     0x55b96a0531b4 - <unknown>
8:     0x55b96a054669 - <unknown>
9:     0x55b969f7fd73 - <unknown>
10:     0x55b969f7fe03 - <unknown>
11:     0x55b969f926d0 - <unknown>
12:     0x55b969f87976 - <unknown>
13:     0x55b969f87f95 - <unknown>
14:     0x55b96a04be6e - <unknown>
15:     0x55b969f96082 - <unknown>
16:     0x7fda3e5e9290 - <unknown>
17:     0x7fda3e5e934a - __libc_start_main
18:     0x55b969f7ffb5 - <unknown>
19:                0x0 - <unknown>

IncorrectKey would be thrown if the database was opened with an incorrect key (either wrong password, wrong keyfile, or both).
I will close for now since there is not enough information to help debug this further. If you can provide a minimal example to reproduce (e.g. a testing database and a password), I am happy to re-open the issue :)

IncorrectKey would be thrown if the database was opened with an incorrect key (either wrong password, wrong keyfile, or both).
I provided the proper password and keyfile, yet i get this error, the db opens on keepassxc, other android clients, but just not with keepass-diff

IncorrectKey would be thrown if the database was opened with an incorrect key (either wrong password, wrong keyfile, or both).
I provided the proper password and keyfile, yet i get this error, the db opens on keepassxc, other android clients, but just not with keepass-diff

Could you please create a reproducible example, e.g.

Make a copy of your database
Remove all entries and clear recycle bin
Change the password and keyfile
Check if the problem is still reproducible with the changed database
Share that database, password and keyfile, together with steps to reproduce


Add Indexes to Firebase Database

Add Indexes to Firebase Database
Related Issue and PR

[x] #1141
[x] #1142

Description
We need to add the following indexes to our Firebase database

roles.archived
username
__name__

Steps to Add Indexes

Open the Firebase console.
Navigate to the database section.
Click on the "Indexes" tab.
Click on the "Add Index" button.
Enter the following details for each index:

Collection ID:users
Field Path:
1. roles.archived -> Ascending
2. username -> Ascending
3. __name__ -> Ascending
Query Scope: Collection

Click on the "Create Index" button to add the index.

@sahsisunny Index is being created ✅
Thank you for the details.


[SPARK-28623][SQL] Support dow, isodow and doy by extract()

What changes were proposed in this pull request?
In the PR, I propose to use existing expressions DayOfYear, WeekDay and DayOfWeek, and support additional parameters of extract() for feature parity with PostgreSQL (https://www.postgresql.org/docs/11/functions-datetime.html#FUNCTIONS-DATETIME-EXTRACT):

dow - the day of the week as Sunday (0) to Saturday (6)
isodow - the day of the week as Monday (1) to Sunday (7)
doy - the day of the year (1 - 365/366)

Here are examples:
spark-sql> SELECT EXTRACT(DOW FROM TIMESTAMP '2001-02-16 20:38:40');
5
spark-sql> SELECT EXTRACT(ISODOW FROM TIMESTAMP '2001-02-18 20:38:40');
7
spark-sql> SELECT EXTRACT(DOY FROM TIMESTAMP '2001-02-16 20:38:40');
47

How was this patch tested?
Updated extract.sql.

Can one of the admins verify this patch?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13796/
Test PASSed.

Test build #108711 has started for PR 25367 at commit ef3552b.

Test build #108711 has finished for PR 25367 at commit ef3552b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108711/
Test PASSed.


To change a Expression from Infix to Postfix.

The Expression would contain only uppercase Alphabets and some special characters .
I would be using C++ for changing the expression from infix to postfix.

You can start working on this issue. All the best!


[Bug]: Ledger HID does not work on Android 12+

Impacted Library name
@ledgerhq/react-native-hid
Impacted Library version
6.28.12
Describe the bug
When trying to connect to the Ledger device using TransportHID.open(device) on an Android 12 device, an error is thrown:
[Error: com.myapp.wallet: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.
Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.]

Expected behavior
It should not throw the error and Ledger connection via HID using an Android 12 device should be successful
Additional context
I suspect this pull request could've fixed it, but it went stale:
https://github.com/LedgerHQ/ledger-live/pull/1771

Hey @tzechuen thanks for reporting this, I missed both this issue and the proposed pull request 🤦🏼♂.
However!, we've tackled this in our current sprint and it's currently being validated and reviewed. Feel free to test the build if you want and see if it detects your device again, I'll close the issue now but if you find issues on the build please report them on the PR.


emet proanlem

Type: Bug
dom element emet not found on vs code
VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:40:56.878Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 7 5700G with Radeon Graphics          (16 x 3793)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.40GB (2.58GB free)

Process Argv
--crash-reporter-id 8af8bf6c-1342-4173-8c30-a195d0cf0a0c

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

vscode-tailwindcss
bra
0.10.5

dom-js-inject
Chr
2.2.2

vscode-html-css
ecm
2.0.9

prettier-vscode
esb
10.1.0

code-runner
for
0.12.1

auto-save
mcr
1.0.3

LiveServer
rit
5.7.9

code-spell-checker
str
3.0.1

material-theme
zhu
3.16.2

html-css-class-completion
Zig
1.20.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30968133
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
pydisww1:30959800
edj9j583:30969295
7j2b6412:30969109
bg6jg535:30958357

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!


Milestone friendships v1

We have attempted to create User methods and associations between users to implement features of Friendships such as

Accepting friend requests
Rejecting friend requests
Showing pending friend requests

Also we have added some tests for our app.

I have tried to implement all the required changes suggested even though I feel the milestone in particular was to deal mainly with the model and associations.


Fix small typo in readme

From looking through the code it seems like the the function name is isPreviewable.

Thank you for this!!


Add PhysicalAddress and CapabilitiesManagedBySatellite to SatelliteLocation API

PhysicalAddress and CapabilitiesManagedBySatellite have been added as new parameters to SatelliteLocationAPIs already. Here, Address has been added to Create and Get APIs, whereas Capabilities has been added to Create, Get and List APIs.
Therefore, I would like to submit this Pull-Request, in order to add Address and Capabilities respectively in the SatelliteLocation methods of IBM-Cloud/container-services-go-sdk/kubernetesserviceapiv1, so that it can be used to extend SatelliteLocation functionality in terraform-provider-ibm.

Hello Zoltan @TwoDCube, kindly requesting you for a new review. Many thanks in advance.


Voicemail email time zone

I did see issue #11 mentioned the same thing, but wasn't sure if anyone would see my reply since it has been closed.
This is also an issue for our environment. It would be great if there was an easier way to change the time zone other than changing the code. Maybe there could be an environment variable in the Lambda function that could be easily changed to the desired value like "America/New_York" or "America/Denver"

With some direction from AWS support, I was able to modify the code. Here was my solution.
Download the Lambda code package for the following two functions:
TranscriptionEventsLambdaFunction
ContactVoicemailStreamLambdaFunction
Change the code in the following two javascript files for each package:
transcription.js
voicemail.js
sendMail(e, t, n, r) {
        return new Promise((s, i) => {
                    let o = `<p>${(new Date(1e3*e.timestamp)).toLocaleString('en-US', { timeZone: 'America/Denver' })}</p>`;
                    if (o += `<p>New voicemail from ${e.contactPhoneNumber}.</p>`, r.transcription && (o += `<b>Voicemail Transcript:</b><p>${r.transcription.transcripts[0].transcript}</p>`), o += "<b>Voicemail:</b>", r.preSignedUrl) {
                        o += `<p>Voicemail Expiration Date: ${(new Date(1e3*Math.floor(Date.now()/1e3+r.preSignedUrl.expires))).toLocaleString('en-US', { timeZone: 'America/Denver' })}</p>`, o += `<p><a href="${r.preSignedUrl.url}">Click Here</a> to listen to the voicemail</p>`
                    }

Then re-zip the packages and upload them into the functions. I had trouble zipping in Windows due to file/path length, so I did it in Linux.
Next time I'll have to try cloning the dev branch and building my own.
It would be great if there was an Environment Variable that could be easily edited in the Lambda function overview for this value.

I would also like to request this feature be implemented.  An environment variable for timezone would be most appreciated.


Cannot invoke task: TypeError: Object of type 'LambdaContext' is not JSON serializable

Context
When invoking tasks a TypeError is raised as zappa tries to JSON encode the LambdaContext object.
Expected Behavior
The task should be invoked
Actual Behavior
A TypeError is raised as context.identity (CognitoIdenity instance) cannot be serialized as it has no '__dict__' attribute and hence cannot be serialized.
Object of type 'LambdaContext' is not JSON serializable: TypeError
Traceback (most recent call last):
  File "/var/task/handler.py", line 505, in lambda_handler
    return LambdaHandler.lambda_handler(event, context)
  File "/var/task/handler.py", line 242, in lambda_handler
    return handler.handler(event, context)
  File "/var/task/handler.py", line 341, in handler
    result = self.run_function(app_function, event, context)
  File "/var/task/handler.py", line 272, in run_function
    result = app_function(event, context) if varargs else app_function()
  File "/var/task/zappa/async.py", line 344, in _run_async
    aws_region=aws_region).send(task_path, args, kwargs)
  File "/var/task/zappa/async.py", line 143, in send
    self._send(message)
  File "/var/task/zappa/async.py", line 151, in _send
    payload = json.dumps(message).encode('utf-8')
  File "/var/lang/lib/python3.6/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/var/lang/lib/python3.6/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/var/lang/lib/python3.6/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/var/lang/lib/python3.6/json/encoder.py", line 180, in default
    o.__class__.__name__)
TypeError: Object of type 'LambdaContext' is not JSON serializable

Possible Fix
Remove unserializable types before serialization or define custom encoder. It's a horrible solution, I admit.
# create dict from context with serializable types (this list almost certainly missing many valid types!)
context_serializable = {k:v for k, v in context.__dict__.items() if type(v) in [int, float, bool, str, list, dict]}
json.dumps(context_serializable)

Steps to Reproduce

Create test task

from zappa.async import task

@task
def my_func():
    print("All good!")

 I was attempting to return another raised error type and its lack of JSON-afinity made it super ugly.

So I have been playing around with this today to try and come to a solution, however, I believe I may have stumbled on another issue.
First, my solution:
import json
from zappa.async import task, ASYNC_CLASSES, LambdaAsyncResponse

# Define a custom encoder which casts non base types to string
class LambdaMessageEncoder(json.JSONEncoder):
    def default(self, obj):
        if not type(obj) in [int, float, complex, dict, tuple, list, bool] and obj is not None:
            return str(obj)

        return json.JSONEncoder.default(self, obj)

# Extend LambdaAsyncResponse to rework the _send method
# The send method is only included due to a bug where response_id is not set
class TestLambdaAsyncResponse(LambdaAsyncResponse):
    def send(self, task_path, args, kwargs):
        """
        Create the message object and pass it to the actual sender.
        """
        message = {
                'task_path': task_path,
                'capture_response': self.capture_response,
                'response_id': getattr(set, 'response_id', None),
                'args': args,
                'kwargs': kwargs
            }
        self._send(message)
        return self

    def _send(self, message):
        """
        Given a message, directly invoke the lamdba function for this task.
        """
        message['command'] = 'zappa.async.route_lambda_task'

        # Use custom encoder class
        payload = json.dumps(message, cls=LambdaMessageEncoder).encode('utf-8')

        if len(payload) > 128000: # pragma: no cover
            raise AsyncException("Payload too large for async Lambda call")

        self.response = self.client.invoke(
                                    FunctionName=self.lambda_function_name,
                                    InvocationType='Event', #makes the call async
                                    Payload=payload
                                )
        self.sent = (self.response.get('StatusCode', 0) == 202)

# Add service to ASYNC_CLASSES
ASYNC_CLASSES['test'] = TestLambdaAsyncResponse

@task()
def my_func_default_encoder(*args, **kwargs):
    print("All good, default encoder!")

@task(service='test')
def my_func_with_encoder(*args, **kwargs):
	print("All good, new encoder!")

This fixes our issues with LambdaContext being unserializable but raises a new issue as Zappa is trying to call the method asynchronously when we invoke it through the command line. The response object, TestLambdaAsyncResponse, is in turn unserializable. Output below:
Calling invoke for stage bugtest..
[DEBUG] 2017-09-12T11:52:17.97Z d327d303-97b0-11e7-86c5-114d325c08e9 StringToSign:
AWS4-HMAC-SHA256
20170912T115217Z
20170912/eu-west-2/lambda/aws4_request..............
[DEBUG] 2017-09-12T11:52:17.97Z d327d303-97b0-11e7-86c5-114d325c08e9 Signature:
..................
[DEBUG] 2017-09-12T11:52:17.98Z d327d303-97b0-11e7-86c5-114d325c08e9 Sending http request: <PreparedRequest [POST]>
[INFO]	2017-09-12T11:52:17.98Z	d327d303-97b0-11e7-86c5-114d325c08e9	Starting new HTTPS connection (2): lambda.eu-west-2.amazonaws.com
[DEBUG] 2017-09-12T11:52:17.211Z d327d303-97b0-11e7-86c5-114d325c08e9 "POST /2015-03-31/functions/zappabug-bugtest/invocations HTTP/1.1" 2020
[DEBUG] 2017-09-12T11:52:17.211Z d327d303-97b0-11e7-86c5-114d325c08e9 Response headers: {'content-type': '', 'date': 'Tue, 12 Sep 2017 11:52}
[DEBUG] 2017-09-12T11:52:17.211Z d327d303-97b0-11e7-86c5-114d325c08e9 Response body:
<botocore.response.StreamingBody object at 0x7f72a708df98>
[DEBUG] 2017-09-12T11:52:17.211Z d327d303-97b0-11e7-86c5-114d325c08e9 Event needs-retry.lambda.Invoke: calling handler <botocore.retryhandle>
[DEBUG] 2017-09-12T11:52:17.212Z d327d303-97b0-11e7-86c5-114d325c08e9 No retry needed.
Result of test.my_func_with_encoder:
<test.TestLambdaAsyncResponse object at 0x7f72a7cf1d30>
An error occurred during JSON serialization of response: <test.TestLambdaAsyncResponse object at 0x7f72a7cf1d30> is not JSON serializable
Traceback (most recent call last):
  File "/var/lang/lib/python3.6/json/__init__.py", line 238, in dumps
    **kw).encode(obj)
  File "/var/lang/lib/python3.6/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/var/lang/lib/python3.6/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/var/runtime/awslambda/bootstrap.py", line 110, in decimal_serializer
    raise TypeError(repr(o) + " is not JSON serializable")
TypeError: <test.TestLambdaAsyncResponse object at 0x7f72a7cf1d30> is not JSON serializable
[END] RequestId: d327d303-97b0-11e7-86c5-114d325c08e9
[REPORT] RequestId: d327d303-97b0-11e7-86c5-114d325c08e9
Duration: 131.44 ms
Billed Duration: 200 ms
Memory Size: 512 MB
Max Memory Used: 34 MB

I'm not sure my understanding of the internals of Zappa is quite strong enough to tackle this one, would appreciate some guidance/thoughts on how to tackle this.

Further to the above, I believe an error in the TestLambdaAsyncResponse method was causing Zappa to retry calling our method.
I need to find the time to work through this issue as right now I have very little confidence in my solution.

@robwatkiss any update on this?

I am getting same error.
I added task decorator to function and I am calling the function from  zappa_settings.json shown as below:
"events": [
    {
        "function": "tasks.print_for_test_lambda",
        "expression": "rate(1 minute)"
    }
],

Project directory structure:
rootDir/
   tasks.py
   zappa_settings.json
  ...

@mesuutt to have a method execute from an event it can't have the task decorator (based on my last tests ~2 months ago)

I believe that when the event calls a function with a task decoy or the event launches a separate lambda function to do the task.
Sent from my iPhone

On Nov 27, 2017, at 11:52 AM, Rob Watkiss<EMAIL_ADDRESS>wrote:
@mesuutt to have a method execute from an event it can't have the task decorator (based on my last tests ~2 months ago)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@mcrowson Yes, I do agree with you but I am still confused that If the task function has some dependencies on imported modules then how would it going to run.
Please look at below snippet.
import os
from flask import Flask
from flask_restful import Api as FlaskRestfulAPI, Resource,reqparse
from elasticsearch import Elasticsearch
from zappa.async import task

from config import config
from analyzer import Paradigmatic

app = Flask(__name__)
app.config.from_object(config['dev'])

class ParadigmaticResource(Resource):
    post_parser = reqparse.RequestParser()
    post_parser.add_argument('word1', required=True, location='json')
    post_parser.add_argument('word2', required=True, location='json')

    @task
    def calculate_paradigmatic(self, *args, **kwargs):
        paradigmatic = Paradigmatic()
        score = paradigmatic.similarity(kwargs['word1'], kwargs['word2'])
        return {'score': score }

    def post(self):
        args = self.post_parser.parse_args()
        data = self.calculate_paradigmatic(word1=args['word1'], word2=args['word2'])
        return {'score': data}

with app.app_context():
    api = FlaskRestfulAPI(app)
    api.add_resource(ParadigmaticResource, '/paradigmatic')

if __name__ == '__main__':
    app.run(debug=True)

Now When I execute this endpoint then I am getting the below-mentioned error.
[1521814433242] [DEBUG] 2018-03-23T14:13:53.226Z 6a8d7647-2ea4-11e8-8f8b-3f7ca6a6d141 Zappa Event: {'resource': '/{proxy+}', 'path': '/paradigmatic', 'httpMethod': 'POST', 'headers': {'Accept': '*/*', 'Accept-Encoding': 'gzip, deflate, br', 'Accept-Language': 'en-GB,en-US;q=0.9,en;q=0.8', 'cache-control': 'no-cache', 'CloudFront-Forwarded-Proto': 'https', 'CloudFront-Is-Desktop-Viewer': 'true', 'CloudFront-Is-Mobile-Viewer': 'false', 'CloudFront-Is-SmartTV-Viewer': 'false', 'CloudFront-Is-Tablet-Viewer': 'false', 'CloudFront-Viewer-Country': 'IN', 'content-type': 'application/json', 'Host': 'voxvx70ba3.execute-api.ap-south-1.amazonaws.com', 'origin': 'chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop', 'postman-token': '0c8ebf3f-22b9-c825-e54a-0325e486171d', 'User-Agent': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36', 'Via': '2.0 affc54995ded64e4c5647f6363ed884e.cloudfront.net (CloudFront)', 'X-Amz-Cf-Id': 'zt9m6CYbOqvOWZOPE9BQftFnEqD4qDK2WTkE5k3mIJ5gnr19MogfYA==', 'X-Amzn-Trace-Id': 'Root=1-5ab50ba1-a06594aae7a25b8e84eefedc', 'X-Forwarded-For': '<IP_ADDRESS>, <IP_ADDRESS>', 'X-Forwarded-Port': '443', 'X-Forwarded-Proto': 'https'}, 'queryStringParameters': None, 'pathParameters': {'proxy': 'paradigmatic'}, 'stageVariables': None, 'requestContext': {'requestTime': '23/Mar/2018:14:13:53 +0000', 'path': '/dev/paradigmatic', 'accountId': '445420586144', 'protocol': 'HTTP/1.1', 'resourceId': 'ne01c4', 'stage': 'dev', 'requestTimeEpoch':<PHONE_NUMBER>148, 'requestId': '6a85fbf4-2ea4-11e8-9c0b-3f97e930b286', 'identity': {'cognitoIdentityPoolId': None, 'accountId': None, 'cognitoIdentityId': None, 'caller': None, 'sourceIp': '<IP_ADDRESS>', 'accessKey': None, 'cognitoAuthenticationType': None, 'cognitoAuthenticationProvider': None, 'userArn': None, 'userAgent': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36', 'user': None}, 'resourcePath': '/{proxy+}', 'httpMethod': 'POST', 'apiId': 'voxvx70ba3'}, 'body': 'ewoJIndvcmQxIjogIm15c3FsIiwKCSJ3b3JkMiI6ICJqcXVlcnkiCn0=', 'isBase64Encoded': True}
[1521814433243] Object of type 'ParadigmaticResource' is not JSON serializable

I am not sure what is missing, I followed as per the documentation.
I want to execute this function asynchronously.
Please do let me know if someone has any idea about it.
Thanks

Have you tried creating a wrapper function that's not in the class? The async function call stuff needs a function name, not a method of a class.

Yes, I got it. It should an independent method.

I'm getting this error when trying to call a task from inside a task.
@task(...)
def test():
    inside_task()

@task(...)
def inside_task():
    pass

With the following traceback:
Traceback (most recent call last):
  File "/var/task/handler.py", line 567, in lambda_handler
    return LambdaHandler.lambda_handler(event, context)
  File "/var/task/handler.py", line 240, in lambda_handler
    return handler.handler(event, context)
  File "/var/task/handler.py", line 372, in handler
    result = self.run_function(app_function, event, context)
  File "/var/task/handler.py", line 275, in run_function
    result = app_function(event, context) if varargs else app_function()
  File "/var/task/zappa/async.py", line 424, in _run_async
    capture_response=capture_response).send(task_path, args, kwargs)
  File "/var/task/zappa/async.py", line 170, in send
    self._send(message)
  File "/var/task/zappa/async.py", line 178, in _send
    payload = json.dumps(message).encode('utf-8')
  File "/var/lang/lib/python3.6/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/var/lang/lib/python3.6/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/var/lang/lib/python3.6/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/var/lang/lib/python3.6/json/encoder.py", line 180, in default
    o.__class__.__name__)
TypeError: Object of type 'LambdaContext' is not JSON serializable

Yes same here. @charlax Did you find a workaround?

@charlax it seems like trying to run  a task either via events field in the zappa_settings or invoke command will throw that exception. task's service needs to be specified in the decorator and the function signature needs to be func(event, context). The kwargs will be in event dictionary but there is another bug pending for passing arguments, so you are pretty much left with hard coded defaults.

I'm getting this error when trying to call a task from inside a task.
@task(...)
def test():
    inside_task()

@task(...)
def inside_task():
    pass

With the following traceback:
Traceback (most recent call last):
  File "/var/task/handler.py", line 567, in lambda_handler
    return LambdaHandler.lambda_handler(event, context)
  File "/var/task/handler.py", line 240, in lambda_handler
    return handler.handler(event, context)
  File "/var/task/handler.py", line 372, in handler
    result = self.run_function(app_function, event, context)
  File "/var/task/handler.py", line 275, in run_function
    result = app_function(event, context) if varargs else app_function()
  File "/var/task/zappa/async.py", line 424, in _run_async
    capture_response=capture_response).send(task_path, args, kwargs)
  File "/var/task/zappa/async.py", line 170, in send
    self._send(message)
  File "/var/task/zappa/async.py", line 178, in _send
    payload = json.dumps(message).encode('utf-8')
  File "/var/lang/lib/python3.6/json/__init__.py", line 231, in dumps
    return _default_encoder.encode(obj)
  File "/var/lang/lib/python3.6/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/var/lang/lib/python3.6/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/var/lang/lib/python3.6/json/encoder.py", line 180, in default
    o.__class__.__name__)
TypeError: Object of type 'LambdaContext' is not JSON serializable

you should not use @taskdecorator to the function that used for events in zappa_settings.json

So I have been playing around with this today to try and come to a solution, however, I believe I may have stumbled on another issue.
First, my solution:
import json
from zappa.async import task, ASYNC_CLASSES, LambdaAsyncResponse

# Define a custom encoder which casts non base types to string
class LambdaMessageEncoder(json.JSONEncoder):
    def default(self, obj):
        if not type(obj) in [int, float, complex, dict, tuple, list, bool] and obj is not None:
            return str(obj)

        return json.JSONEncoder.default(self, obj)

# Extend LambdaAsyncResponse to rework the _send method
# The send method is only included due to a bug where response_id is not set
class TestLambdaAsyncResponse(LambdaAsyncResponse):
    def send(self, task_path, args, kwargs):
        """
        Create the message object and pass it to the actual sender.
        """
        message = {
                'task_path': task_path,
                'capture_response': getattr(self, 'capture_response', False),
                'response_id': getattr(self, 'response_id', None),
                'args': args,
                'kwargs': kwargs
            }
        self._send(message)
        return self

    def _send(self, message):
        """
        Given a message, directly invoke the lamdba function for this task.
        """
        message['command'] = 'zappa.async.route_lambda_task'

        # Use custom encoder class
        payload = json.dumps(message, cls=LambdaMessageEncoder).encode('utf-8')

        if len(payload) > 128000: # pragma: no cover
            raise AsyncException("Payload too large for async Lambda call")

        self.response = self.client.invoke(
                                    FunctionName=self.lambda_function_name,
                                    InvocationType='Event', #makes the call async
                                    Payload=payload
                                )
        self.sent = (self.response.get('StatusCode', 0) == 202)

# Add service to ASYNC_CLASSES
ASYNC_CLASSES['test'] = TestLambdaAsyncResponse

@task()
def my_func_default_encoder(*args, **kwargs):
    print("All good, default encoder!")

@task(service='test')
def my_func_with_encoder(*args, **kwargs):
	print("All good, new encoder!")

This fixes our issues with LambdaContext being unserializable but raises a new issue as Zappa is trying to call the method asynchronously when we invoke it through the command line. The response object, TestLambdaAsyncResponse, is in turn unserializable. Output below:
Calling invoke for stage bugtest..
[DEBUG] 2017-09-12T11:52:17.97Z d327d303-97b0-11e7-86c5-114d325c08e9 StringToSign:
AWS4-HMAC-SHA256
20170912T115217Z
20170912/eu-west-2/lambda/aws4_request..............
[DEBUG] 2017-09-12T11:52:17.97Z d327d303-97b0-11e7-86c5-114d325c08e9 Signature:
..................
[DEBUG] 2017-09-12T11:52:17.98Z d327d303-97b0-11e7-86c5-114d325c08e9 Sending http request: <PreparedRequest [POST]>
[INFO]	2017-09-12T11:52:17.98Z	d327d303-97b0-11e7-86c5-114d325c08e9	Starting new HTTPS connection (2): lambda.eu-west-2.amazonaws.com
[DEBUG] 2017-09-12T11:52:17.211Z d327d303-97b0-11e7-86c5-114d325c08e9 "POST /2015-03-31/functions/zappabug-bugtest/invocations HTTP/1.1" 2020
[DEBUG] 2017-09-12T11:52:17.211Z d327d303-97b0-11e7-86c5-114d325c08e9 Response headers: {'content-type': '', 'date': 'Tue, 12 Sep 2017 11:52}
[DEBUG] 2017-09-12T11:52:17.211Z d327d303-97b0-11e7-86c5-114d325c08e9 Response body:
<botocore.response.StreamingBody object at 0x7f72a708df98>
[DEBUG] 2017-09-12T11:52:17.211Z d327d303-97b0-11e7-86c5-114d325c08e9 Event needs-retry.lambda.Invoke: calling handler <botocore.retryhandle>
[DEBUG] 2017-09-12T11:52:17.212Z d327d303-97b0-11e7-86c5-114d325c08e9 No retry needed.
Result of test.my_func_with_encoder:
<test.TestLambdaAsyncResponse object at 0x7f72a7cf1d30>
An error occurred during JSON serialization of response: <test.TestLambdaAsyncResponse object at 0x7f72a7cf1d30> is not JSON serializable
Traceback (most recent call last):
  File "/var/lang/lib/python3.6/json/__init__.py", line 238, in dumps
    **kw).encode(obj)
  File "/var/lang/lib/python3.6/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/var/lang/lib/python3.6/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/var/runtime/awslambda/bootstrap.py", line 110, in decimal_serializer
    raise TypeError(repr(o) + " is not JSON serializable")
TypeError: <test.TestLambdaAsyncResponse object at 0x7f72a7cf1d30> is not JSON serializable
[END] RequestId: d327d303-97b0-11e7-86c5-114d325c08e9
[REPORT] RequestId: d327d303-97b0-11e7-86c5-114d325c08e9
Duration: 131.44 ms
Billed Duration: 200 ms
Memory Size: 512 MB
Max Memory Used: 34 MB

I'm not sure my understanding of the internals of Zappa is quite strong enough to tackle this one, would appreciate some guidance/thoughts on how to tackle this.

I'm facing same issue, any update on this?

As mentioned in the comment, a scheduled event cannot use a @task decorator.
If the function is called in code other than the scheduled event, and you still want it to run as a scheduled event, I believe if you create a simple handler (my_async_task_handler() below) to manage the scheduled event you can work around this issue. (same when calling a task in a task).
...
"events": [
    {
        "function": "tasks.my_async_task_handler",
        "expression": "rate(1 minute)"
    }
],
...

tasks.py:
@task(...)
def my_async_task():
    print("code here")

def my_async_task_handler():
    my_async_task()


Use latest expensify-common

Fixes issues with sending or editing messages with empty markdown tags. This was already more thoroughly detailed and tested in this PR: https://github.com/Expensify/expensify-common/pull/443
Fixed Issues
$ https://github.com/Expensify/App/issues/8720
Tests

[x] Verify that no errors appear in the JS console

Log in
Start a chat conversation
Send a message with empty backticks (code block with no text in-between)
Verify empty backticks are sent and NOT an empty code block
Send a message with empty code fence backticks
Verify 2 code blocks with a back tick in each is sent and NOT an empty code fence
Send a message with a markdown link with no text
Verify the text is sent as is and an invisible link is NOT sent

QA Steps
Same as Tests section

I have read the CLA Document and I hereby sign the CLA

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @amyevans in version: 1.1.58-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @AndrewGable in version: 1.1.60-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


wip: stacks/transactions: verifySingleSig() and verifyMultiSig() work like the rust code

This PR adds the code to match stacks-blockchain's verification of signing conditions in transactions.  In particular, this adds support for verifying multisig signatures.
This code is needed to complete the STX integration for BitGo.
Type of Change

[X] New feature
[ ] Bug fix
[ ] API reference/documentation update
[ ] Other

Does this introduce a breaking change?
Yes -- see the failing test: STX token transfer transaction multi-sig uncompressed keys serialization and deserialization
The code in stacks-blockchain appears to reject such transactions (line 296 or so in src/chainstate/stacks/auth.rs):
if have_uncompressed && self.hash_mode == MultisigHashMode::P2WSH {
            return Err(net_error::VerifyingError(
                "Uncompressed keys are not allowed in this hash mode".to_string(),
            ));
        }

Are documentation updates required?
All changes are internal.
Testing information
Needs more tests.
Checklist

[ ] Code is commented where needed
[X] Unit test coverage for new or modified code paths
[ ] npm run test passes
[ ] Changelog is updated
[ ] Tag 1 of @yknl or @zone117x for review

Adapting the tests from stacks-blockchain to work with this code is difficult -- some of the constants used by authorization.ts are not exported, like AuthType and AddressHashMode.
What should the next steps be, @reedrosenbluth?

@fariedt those constants appear to both be exported and usable from tests

I got that wrong -- what isn't exported is AuthFieldType.  It's not necessary, though.
I've added three more tests from stacks-blockchain for multi-sig support.  I've also added support for P2WSH and P2WPKH address types (needed for some of the authorization tests).

@fariedt is this still WIP?

@reedrosenbluth I've rebased this against master, and fixed a couple of lint + type errors, and removed the WIP label.
There is an older test case that fails: #bcf66b75b --  STX token transfer transaction multi-sig uncompressed keys serialization and deserialization.  It doesn't seem like stacks-blockchain allows the use of uncompressed keys here, and my code reflects that.

This implementation looks good to me, but I'd like to see more tests of the verification function that use something like transaction vectors (both valid and invalid) to test that the verification routine is operating correctly.

Update:

Added the aforementioned tests (valid/invalid) using transaction vectors
Added missing checks in deserialize spending conditions
Fixed and updated breaking tests
Ready for rereview or if it's needs any further actions.


[Feature Request] Add ubuntu icon

Description of the new feature/enhancement
Currently the icon for the ubuntu shell is the linux icon. Would be nice to have to ubuntu logo for the ubuntu shell.

Thanks for the heads up. Should I leave this issue open until a solution is found?

We'll be tracking this as part of #2282. Thanks!