Yabasanshiro 1.9 Issues

I'm running the latest ArkOS on my rg351mp, and loaded some games to check the improvements with Yabanshiro, the Sega Saturn emulator.
I tried Sonic 3D Blast, Nights into Dreams, Shining Force III and Legend of Oasis. Every game had flickering issues not present on the other emulators/cores. For example, Nights has flickering on text, while Legend of Oasis has the flickering on shadow effects.
Is this emulator specific and thus happening on other distributions too, or is this an ArkOS specific problem?

I haven't had this issue on my unit.  Try standalone-nobios or standalone-bios and see if there's a difference there.

I checked this again and I do notice some flickering of text for Night into Dreams when entering your name.  Gameplay seems ok.  That's the emulator and not something specific to any OS.  Hopefully it will improve in a future update of the Emulator.


States missing after adding device

The states (and sometimes the controls) of a device are missing after adding a device:

adding device

open device details of added device

states missing

4 refresh page
5 states appear

Browser
Mozilla Firefox 41.0

The states are here now, but they will not be updated until I refresh the page. (the API events will be ignored). Even if I execute the update action the states are not updated!

Should now work. Please reopen if this bug occurs again.


Add sideEffects

This PR adds sideEffects field, which will be supported in upcoming Webpack 4.

Just wonder if ES6 modules (I mean real ES6 modules) prohibit side effects (or get evaluated once)? Need to read more about this


HELP: Error 'ICompleteBuilder<IFluentQueryBuilder, SqlBuilder, IDapperSqlCommand>' does not contain a definition for 'Query'

Error (active)	CS1929	'ICompleteBuilder<IFluentQueryBuilder, SqlBuilder, IDapperSqlCommand>' does not contain a definition for 'Query' and the best extension method overload 'IDapperSqlBuilderExtensions.Query(IDapperSqlBuilder, IDbTransaction?, bool, int?, CommandType?)' requires a receiver of type 'InterpolatedSql.Dapper.SqlBuilders.IDapperSqlBuilder'	242
my query is:
con.FluentQueryBuilder().Select(......).Query();
Error only happen when i am using v2.0.0 stable release,
and it work well when i am using v2.0.0-beta2 or beta1
my project is blazor dotnet 8 webapp

Try .Build().Query()

Try .Build().Query()

many thanks save me, it work,
now i can update to stable release.....


Licensing

Hi, what license are these icons available under?

Hey @msanders – this icon is no longer the official one shipped with iTerm2 so I've added The Unlicense licensing to the repo.


[Feature Request] Add PrompDialog option to not post TooManyAttempts error back to user

SDK language: C#
SDK version: <IP_ADDRESS>
Development environment: localhost
We have multiple requirements to handle the failed parsing events on prompt dialogs differently.
This is possible by setting the attempts to 0 and handling the TooManyAttemptsException, the only problem is the TooManyAttepts error is still posted to the client before the exception is thrown.
We need an option to turn off the TooManyAttepts error being posted to the client.

@nwhitmont This is a feature request, not a question.

Cool...I was looking for something like this!!!

Yes needed, I would also like to inspect the user input, rather then completely fail.

We also have the need set the PromptOptions.attempts to 0 and handle the TooManyAttemptsException ourselves, but as previously mentioned, it is presently not possible to prevent a posting of the error back to the user. The best we can do is set the PromptOptions.tooManyAttempts to an empty string, so the user sees a blank message before we handle the error ourselves.

#4533

Workaround here is to set the retries to a very large number. You can also catch and swallow the too many attempts exception. There are no plans to add support for this to the V3 SDK.


select-field : automatically select first available option

Hey,
I use filtered select fields and I was wondering if there is a way to select the first option on blur ?
Basically what I want to achieve is that a user can enter data in te field and press the tab key to switch to the next field without having to click on the option
It will also help end to end testing with Protractor, because I have to simulate a click on the first available option for each select field
Thanks

Hello,
I don't need this anymore as we found another way to automate select field with protractor
Thanks !

Ok. Thanks for the update :)


Added node 4 as an acceptable engine

The tests are already passing for node 4, but npm complains about the missing engine.

Refer https://github.com/tj/axon/pull/151


no build clickhouse-odbc-bridge aarch64

There is no build clickhouse-odbc-bridge for aarch64 in ci.
How do I build it myself ?
./packager --output-dir=$HOME/clickhouse --package-type binary --compiler=clang-11-aarch64  --version=<IP_ADDRESS>  --official

this is no clickhouse-odbc-bridge output.

You should ask this question in the main ClickHouse project: https://github.com/ClickHouse/ClickHouse
clickhouse-odbc-bridge is a part of the ClickHouse server, not ClickHouse ODBC driver project.

ok


Do you have the document for Bottle of early version?

Hi,
I am a novice programmer of Python Web from China.I want to develop a web framework of myself.Now,I want to learn from bottle.However,I find Bottle 0.12 a little complicated,and the Bottle 0.4.3 have only about 700 lines,so ,I want to learn from it know.Do you have the document for Bottle of early version?0.4 or any other early version?Please e-mail them to me.What'more,I can only read English document.
Thanks.

It looks like the first version that has anything to do with API docs is 0.7.1RC. Before that it was extracting pages from the GH wiki, which I don't think would be useful now.
I'd suggest you work with the current version, though. I'm pretty sure tons of bugs have been fixed meanwhile, and important features introduced. It might be a lot to handle for a novice developer, but I'm sure the time you invest in it would be well worth it.

Everything ever written should be in git history. Even the wiki pages were copied there some time.
For a more history view on things, there is a (german) forum thread here: http://www.python-forum.de/viewtopic.php?t=19451 This is literally the first hour of the bottle project ;)


Revert "[SPARK-30245][SQL] Add cache for Like and RLike when pattern is not static"

What changes were proposed in this pull request?
This reverts commit 8ce7962931680c204e84dd75783b1c943ea9c525. There's variable name conflicts with https://github.com/apache/spark/commit/8aebc80e0e67bcb1aa300b8c8b1a209159237632#diff-39298b470865a4cbc67398a4ea11e767.
This can be cleanly ported back to branch-3.0.
Why are the changes needed?
Performance investigation were not made enough and it's not clear if it really beneficial or now.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Jenkins tests.

Test build #118109 has started for PR 27514 at commit 32f8dc8.

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-K8s/22874/
Test PASSed.

Test build #118109 has finished for PR 27514 at commit 32f8dc8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #118125 has started for PR 27514 at commit f1d8157.

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-K8s/22890/
Test PASSed.

Test build #118125 has finished for PR 27514 at commit f1d8157.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #118133 has started for PR 27514 at commit f1d8157.

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-K8s/22896/
Test PASSed.

Test build #118133 has finished for PR 27514 at commit f1d8157.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #118161 has started for PR 27514 at commit f1d8157.

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-K8s/22923/
Test PASSed.

Test build #118162 has started for PR 27514 at commit f1d8157.

Test build #118161 has finished for PR 27514 at commit f1d8157.

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/118161/
Test PASSed.

Test build #118162 has finished for PR 27514 at commit f1d8157.

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/118162/
Test PASSed.

Thanks! Merged to master.

and merged to branch-3.0.


mednist_app:latest -- No module named 'nibabel'

Discussed in https://github.com/Project-MONAI/monai-deploy-app-sdk/discussions/301

Originally posted by Leengit June  8, 2022
I am trying to run the Jupyter lab notebook 02_mednist_app.ipynb on my local machine but the invocation of
!monai-deploy run mednist_app:latest input output

is giving me ModuleNotFoundError: No module named 'nibabel'.  Thoughts?
To reproduce:
sudo apt install cuda=11.3.1-1 libcudnn8-dev=<IP_ADDRESS>-1+cuda11.3 libcudnn8=<IP_ADDRESS>-1+cuda11.3
python3 -m venv ~/venv/mednist
source ~/venv/mednist/bin/activate
pip install -U pip setuptools wheel ipykernel
python -m ipykernel install --user --name=mednist
pip install -U torch torchvision torchaudio ipywidgets 'monai[pillow, tqdm, ignite, gdown, nibabel]' \
    monailabel monai-deploy-app-sdk pandas transformers mlflow \
    --extra-index-url https://download.pytorch.org/whl/cu113
# Then run the whole notebook using the `mednist` kernel

The full output from !monai-deploy run mednist_app:latest input output is
Checking dependencies...
--> Verifying if "docker" is installed...

--> Verifying if "mednist_app:latest" is available...

Checking for MAP "mednist_app:latest" locally
"mednist_app:latest" found.

Reading MONAI App Package manifest...
--> Verifying if "nvidia-docker" is installed...

Traceback (most recent call last):
  File "/opt/monai/app/mednist_classifier_monaideploy.py", line 13, in <module>
    import monai.deploy.core as md  # 'md' stands for MONAI Deploy (or can use 'core' instead)
  File "/root/.local/lib/python3.8/site-packages/monai/__init__.py", line 43, in <module>
    load_submodules(sys.modules[__name__], False, exclude_pattern=excludes)
  File "/root/.local/lib/python3.8/site-packages/monai/utils/module.py", line 187, in load_submodules
    mod = import_module(name)
  File "/opt/conda/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/root/.local/lib/python3.8/site-packages/monai/deploy/operators/__init__.py", line 39, in <module>
    from .stl_conversion_operator import STLConversionOperator, STLConverter
  File "/root/.local/lib/python3.8/site-packages/monai/deploy/operators/stl_conversion_operator.py", line 19, in <module>
    import nibabel as nib
ModuleNotFoundError: No module named 'nibabel'

ERROR: MONAI Application "mednist_app:latest" failed.

Versions are:
Python 3.8.10
MONAI version: 0.8.1
Numpy version: 1.22.4
Pytorch version: 1.11.0+cu113
MONAI flags: HAS_EXT = False, USE_COMPILED = False
MONAI rev id: 71ff399a3ea07aef667b23653620a290364095b1
Pytorch Ignite version: 0.4.8
Nibabel version: 3.2.2
scikit-image version: 0.19.2
Pillow version: 9.1.1
Tensorboard version: 2.9.0
gdown version: 4.4.0
TorchVision version: 0.12.0+cu113
tqdm version: 4.64.0
lmdb version: 1.3.0
psutil version: 5.9.1
pandas version: 1.4.2
einops version: 0.3.2
transformers version: 4.19.2
mlflow version: 1.26.1

REPOSITORY               TAG         IMAGE ID       CREATED          SIZE
mednist_app              latest      361424005b6f   17 minutes ago   15.5GB
<none>                   <none>      114e7e0380f6   20 hours ago     15.5GB
nvcr.io/nvidia/pytorch   21.07-py3   7beec3ff8d35   10 months ago    15GB

Thanks in advance!

Hi all.
I have stumbled on the same issue last week. I fixed it by modifying the file monai-deploy-app-sdk/requirements.txt. The original file contains the following :
numpy>=1.21  # CVE-2021-33430
networkx>=2.4
colorama>=0.4.1
typeguard>=2.12.1
I changed it for :
numpy>=1.21  # CVE-2021-33430
networkx>=2.4
colorama>=0.4.1
typeguard>=2.12.1
nibabel
monai
pydicom
with this new file saved, I have changed the MONAI packager command line by providing the requirements.txt file as dependency input :
monai-deploy package examples/apps/mednist_classifier_monaideploy/mednist_classifier_monaideploy.py --requirements ./requirements.txt --tag mednist_app:latest --model classifier.zip -l DEBUG
After these 2 modifications the container generated works as expected.
Hope this helps.

@jeanpatrickleger yes that helps, thank you!  I modified the requirements.txt as you did.  I modified the command in the jupyter lab to be
!monai-deploy package mednist_classifier_monaideploy.py --requirements ../monai-deploy-app-sdk/requirements.txt --tag mednist_app:latest --model classifier.zip  # -l DEBUG
So, I am good now.  A pull request from a knowledgeable person (i.e., not me) would be the frosting on the cake.

The App SDK was designed to have minimal dependencies, however, as the number of built-in increases, more and more dependencies are needed. This is typically handled with using "optional import" in the operator module, but inadvertently the stl_conversion_operator.py failed to have the "optional import" for nibabel, currently on line 19.
For application that uses the STLConversionOperator, the dependencies are inspected and automatically added to the requirements.txt when generating the app package docker image. Setting the "optional import" for nibabel will allow apps that do not use the STLConversionOperator succeed without needing the nibabel package.


bugfix: 插件模板序列化器错误 (closed #1037)

Codecov Report

Merging #1039 (3e2d7a9) into V2.2.22-rc (ced6435) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@              Coverage Diff               @@
##           V2.2.22-rc    #1039      +/-   ##
==============================================
- Coverage       73.24%   73.23%   -0.01%
==============================================
  Files             322      322
  Lines           22942    22942
==============================================
- Hits            16804    16802       -2
- Misses           6138     6140       +2

Impacted Files
Coverage Δ

apps/node_man/constants.py
97.05% <100.00%> (ø)

apps/backend/subscription/steps/plugin.py
55.21% <0.00%> (-0.66%)
:arrow_down:

...nents/collections/agent_new/choose_access_point.py
95.60% <0.00%> (+0.48%)
:arrow_up:

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


verify clipboard works under Chrome 43

http://updates.html5rocks.com/2015/04/cut-and-copy-commands
Since this is how the Chrome app works this should just work (assuming I'm not stripping the clipboard code out from the web version).

This works in Chrome 43!


floor_generator build dependency

Currently, floor_generator depends on an older version of build, ^1.6.3.  This causes incompatibilities with other packages that utilizes the latest versions, >=2.0.0 <2.1.01

As a workaround:
dependency_overrides:
  build: ^2.0.0
  source_gen: ^1.0.0

I didn't realize this was already in #504 and #507...


Sensor_data empty resulting in black screen in manual_control.py

I am using CARLA_0.7.1
I'm starting Carla Simulator on remote machine via
./CarlaUE4.sh /Game/Maps/Town01 -carla-server -benchmark -fps=15
Then I call manual_control.py on my machine to connect to the server
./manual_control.py --host $REMOTE_HOST --port 2000

It starts and I can control my vehicle (and see changing vehicle speed)
But the pygame screen remains blank black.
Received sensor_data object is an empty dict.
On the server side there are no errors.

However when I check logs on the server.
What is suspicious is that CARLA Settings on the server differ from the one provided by Python script. On the server I can config without any sensors, while they were defined in settings string on the client side.
Did any one had similar problem? Cheers
Server Log after client connecting:
[2018.03.26-12.12.03:164][ 15]LogCarla: == CARLA Settings ==============================================================
[2018.03.26-12.12.03:164][ 15]LogCarla: Last settings file loaded: <string-provided-by-client>
[2018.03.26-12.12.03:164][ 15]LogCarla: [CARLA/Server]
[2018.03.26-12.12.03:164][ 15]LogCarla: Networking = Enabled
[2018.03.26-12.12.03:164][ 15]LogCarla: World Port = 2000
[2018.03.26-12.12.03:164][ 15]LogCarla: Server Time-out = 10000 ms
[2018.03.26-12.12.03:164][ 15]LogCarla: Synchronous Mode = Disabled
[2018.03.26-12.12.03:164][ 15]LogCarla: Send Non-Player Agents Info = Enabled
[2018.03.26-12.12.03:164][ 15]LogCarla: [CARLA/LevelSettings]
[2018.03.26-12.12.03:164][ 15]LogCarla: Player Vehicle        = Default
[2018.03.26-12.12.03:164][ 15]LogCarla: Number Of Vehicles    = 15
[2018.03.26-12.12.03:164][ 15]LogCarla: Number Of Pedestrians = 30
[2018.03.26-12.12.03:164][ 15]LogCarla: Weather Id = 8
[2018.03.26-12.12.03:164][ 15]LogCarla: Seed Vehicle Spawner = 29956
[2018.03.26-12.12.03:164][ 15]LogCarla: Seed Pedestrian Spawner = 42264
[2018.03.26-12.12.03:164][ 15]LogCarla: Found 15 available weather settings.
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 0 - Default
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 1 - ClearNoon
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 2 - CloudyNoon
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 3 - WetNoon
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 4 - WetCloudyNoon
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 5 - MidRainyNoon
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 6 - HardRainNoon
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 7 - SoftRainNoon
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 8 - ClearSunset
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 9 - CloudySunset
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 10 - WetSunset
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 11 - WetCloudySunset
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 12 - MidRainSunset
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 13 - HardRainSunset
[2018.03.26-12.12.03:164][ 15]LogCarla:   * 14 - SoftRainSunset
[2018.03.26-12.12.03:165][ 15]LogCarla: [CARLA/SceneCapture]
[2018.03.26-12.12.03:165][ 15]LogCarla: Added 0 cameras.
[2018.03.26-12.12.03:165][ 15]LogCarla: Semantic Segmentation = Disabled
[2018.03.26-12.12.03:165][ 15]LogCarla: ================================================================================

@Ajk4 Which version of the "manual_control.py" are you using? If you are running CARLA 0.7.1 you should use the client examples provided with the 0.7.1 package.

Oh. It must have been it! I took latest code for python package from CARLA 0.7.1 and it works!
Thanks!


Make -f optional

Resolves #438
I also cleaned up and added a relevant test to test/check-bin.sh.

Sorry, I take that comment back about const... I see why it's allowed now. Babel also allows const in for-of loop var declarations. At least it prevents you from re-assigning file within the loop body.

:+1: leaving it up to @adidahiya to review and merge

Looks good, but the commit should be titled "Make -f optional in CLI", not "Remove -f option".


Setup SAP HANA, express edition, in Amazon Web Services or Microsoft Azure using SAP Cloud Appliance Library

Under "Step 4: Connect to your machine using SSH" the command "ssh ssh -i /path/my-key-pair.pem root@vhcalhxedb" is listed, this should be "ssh -i /path/my-key-pair.pem root@vhcalhxedb". Would someone please fix this?

Thanks, Sven! It's fixed now.


duplicate : in the generation script

When I ran this command :
mvn archetype:generate -DarchetypeVersion=0.0.3 -DarchetypeRepository=https://jitpack.io -DarchetypeGroupId=com.github.Riduidel.agile-architecture-documentation-system -DarchetypeArtifactId=archetype -Pjitpack

I see that there is two times the : in the following log trace :
Define value for property 'package' com.lhauspie.example: :

Well, I guess it is more a bug of the maven-archetype-plugin as I have no control over the way it is displayed.

Is that bug still existing with latest version?

Closed by lack of activity


Option to skip CSS compilation within the "bin/console theme:compile" command

This PR adds a CLI option --skip-css to the command bin/console theme:compile to allow to skip CSS compilation. When developing JavaScript in the Production Template, a recompile of the JavaScript is needed (which usually takes less than 0.1 seconds). However, the CSS compilation adds another ~3.6 seconds on top of this, which is totally not needed. This option makes that development faster. Theoretically, more flags could be added (like skipping the JavaScript compilation, skipping assets) - let's debate that later.
1. Why is this change necessary?
When dealing with JavaScript-only compilation, this PR kind of speeds up things 35x.
2. What does this change do, exactly?
This PR implements a new CLI option to the command theme:compile.
3. Describe each step to reproduce the issue or behaviour.
Once the PR is applied, run the command bin/console theme:compile -k. Note the time it takes to complete. Next, run bin/console theme:compile -k --skip-css. Note the time it takes to complete.
4. Please link to the relevant issues (if any).
Not relevant.
5. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[X ] I have read the contribution requirements and fulfil them.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I have a similar todo on my bucket list. Can I add it in here as well? :D it is about the performance of the scss compilation for dev-purposes.

Hey @jissereitsma, could you please add an changelog?

@JoshuaBehrens @jissereitsma How do you compile your JS during development? Are you using watch-storefront.sh or storefront:hot-proxy? Because then both CSS and JS compilation should be done completely via node/webpack which should not trigger a theme:compile as far as I know. Or do you use the storefront:build command because of issues with the watcher regarding sales channel etc.?
Also the theme:compile is only concatenating the already build JS. The compiling itself is also done via webpack. One of the main purposes of the theme:compile was to compile the SCSS on the server side for systems which do not have nodeJS support which makes it kind of odd for me to skip this in the command.
But maybe you can share more information how you develop.
Best regards
Tobias

I had not enough time to find the issue why watch-storefront is not really working for me in the production template. The storefront does not reload, there is no proxy that hosts the page for me. Just does not work for the most of us. And sometimes node is breaking something and we still go for the theme:compile way. And I want to make the Sabberworm compilation optional (opt-out) as I do not need compatibility prefixing when I develop.

@tobiasberge To comment on your earlier question: I'm running the Production Template in this case. Command storefront:hot-proxy is therefore not available. If I place a file src/Resources/app/storefront/src/main.js in a new plugin or theme (named SwagExample), the following commands have the following results:

Command bin/build-storefront.sh generates the dist/storefront/js/swag-example.js file as expected
Command bin/watch-storefront.sh doesn't pick up on changes
Command bin/console theme:compile doesn't pick up on changes in the source file

So while the build-storefront.sh command generates the right file, it is dead-slow. Because of this, I've been using a custom Webpack config ever since starting development with Shopware 6.
As I understand the theme:compile command is not only needed for the SCSS compilation, it also is needed for the JS concatenation. In other words, if you only want to make changes to your JavaScript file (either manually by adding ES5 script to the distributed JS file, or by using Webpack to compile things from the source JS file, the concatenation task of theme:compile still needs to be run. This is where this PR comes in.
So, the test-case would be the following: Create a file dist/storefront/js/swag-example.js in a plugin in the Production Template and then try to concatenate this into the main JS bundle. As far as I know, the only way to do this is to use the theme:compile command which spends 90% on other things. That's where this PR comes in. Hope this clears up a few things.
PS: I still hope to pick on the other tasks to complete this PR (failed tests, CHANGELOG, etc).

@jissereitsma Thanks for your explanation and apologies for my late reply.
I think I get what you wan't to achieve in general and imo it would be ok for now to allow a skip with an option like that. However to me it still feels "shipping around" the core issue - which is that the tool provided for actual JS development is somehow not working for you. You mentioned that bin/watch-storefront.sh does not pick up the changes. Does that mean that all changes of a plugin are not being compiled or does this also apply for the core storefront? Is there just "nothing" happening or is there some kind of error? Because in the background there should be running pretty much the same as for psh hot-proxy.
@JoshuaBehrens Do you think it would make sense to add an extra skip for Sabberworm in addition to the CSS skip? If Sabberworm costs most of the performance it might be a solution to skip this instead of CSS in general.
Best regards
Tobias

@tobiasberge I need compiled css but not any-browser-optimized one for dev. So I can't skip css completely.

@JoshuaBehrens Yes this is basically what I wanted to say. If Sabberworm is the bottleneck here maybe it makes sense to make that skippable instead of CSS in general.

Sorry for the confusion. Yes, I want that skip and it is in my bucket-list. But it sounded useful here as well. That is why I interrupted here. sorry @jissereitsma

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-16626
Please use this issue to track the state of your pull request.

Hey @jissereitsma,
As you already pointed out, the Changelog is missing. Also, a rebase is necessary, because there were some minor changes to the ThemeCompileCommand about a month ago.

Hey @jissereitsma
This PR seems to be inactive, therefore I'm closing it for now. If there is still interest in this, feel free to re-open it. Sorry for the inconvenience.

@jakob-kruse Understood. I might still pickup on this soon, but simply lack the time currently. No worries.

I just stumbled upon this: when disabled sabberworm you can style placeholder selectors correctly. On the otherhand: by default you can't insert scss that affects placeholders :(


Font Customization via CSS Variable

I'm submitting a:

[ ] bug report
[x] feature request

It would be great to be able to customize things like font-family across all components via a CSS variable e.g. --mdc-theme-font-family. Right now I'm unsure how to customize fonts at all, which is leading me away from using MWC.

Besides the font-family especially the font-size should be adjustable as well.

Looks like we also have an upstream issue for this request (https://github.com/material-components/material-components-web/issues/5003)

https://github.com/material-components/material-components-web-components/pull/866 will fix this!

^ along with material-components/material-components-web#5618

Fixed in #866 and material-components/material-components-web#5618


Npm package fixes

DO NOT MERGE, NOT READY FOR REVIEW
This fixes the majority of the npm issues an the app still runs.  The remaining 14 moderate and 1 high issue have not been fixed yet

Let's review after merging in the "Big PR".

closing. superseded by PR 214


updated workshop roadmap

Updated Workshop Roadmap to account for recent changes and updates

Pushed out timelines and added achievable goals for features and enhancements

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM!


Not 100% height superslides — window.height - 80px

HI!
I need a full screen superslides, but I have a 80px height menu on top of page.
How can I set up superslides to use window.height - 80px? When I set a jQuery event to resize, it conflicts with superslides resize.

I have full screen slides minus my headers height.
I wrapped the slides in another div and set that height using jQuery.
You tell superslides to fit that div with by passing its class/id in the inherit_height_from option when you initiate superlides
e.g.

var heightFill = $('.height-fill')
$(heightFill).height(calculatedHeight);
// superslides
$(function()  {
    $('#slides').superslides({
        inherit_height_from: '.height-fill',
        play: 5000
    });
});

Wow, thank you so much!
2015-04-16 18:40 GMT+03:00 Tim Davies<EMAIL_ADDRESS>
I have full screen slides minus my headers height.
I wrapped the slides in another div and set that height using jQuery.
You tell superslides to fit that div with by passing its class/id in the
inherit_height_from option when you initiate superlides
e.g.
var heightFill = $('.height-fill')
$(heightFill).height(calculatedHeight);// superslides
$(function()  {
$('#slides').superslides({
inherit_height_from: '.height-fill',
play: 5000
});
});
—
Reply to this email directly or view it on GitHub
https://github.com/nicinabox/superslides/issues/312#issuecomment-93766747
.

--
С уважением,
Негреев Александр
http://negreev.ru

hello good people,
i am having the same issue but these solution doesn't solve it
can u help me please the image is getting its full height
http://infobasehost.com/xeon/

+1

+1


Import from reactor-core

Note that the package is changed to reactor.kotlin

@bsideup I'm assuming the reactor-kotlin/ subfolder is there because we're expecting more distinct submodules in this repo? (reactor-kotlin-extras, reactor-kotlin-netty perhaps?)

@simonbasle yes, that's a good practice in general to always have modules, otherwise we would have to move a lot of files around if we add a module in future (like the modules you mentioned)

If the plan is to use a single module to provide additional features for various reactor modules lie the name suggests it, I would vote to avoid this artificial reactor-kotlin sub module.
Also what about using reactor-kotlin-extensions repository name to be consistent with reactor-scala-extensions and avoid some confusion like people that will think this is Reactor developed in Kotlin instead of Java?


new ui bug fixes

Codecov Report
Patch coverage: 6.12% and project coverage change: -0.74% :warning:

Comparison is base (ccd13ca) 34.85% compared to head (d82d1de) 34.11%.
Report is 11 commits behind head on main.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
- Coverage   34.85%   34.11%   -0.74%
==========================================
  Files         103      105       +2
  Lines        1449     1486      +37
==========================================
+ Hits          505      507       +2
- Misses        944      979      +35

Files Changed
Coverage Δ

lib/core/cache/app_cache.dart
0.00% <ø> (ø)

lib/core/network/endpoint_manager.dart
75.00% <ø> (ø)

lib/core/network/network_provider.dart
0.00% <0.00%> (ø)

.../features/authentication/auth_service_locator.dart
0.00% <0.00%> (ø)

...esentation/login/states/bloc/login_state_bloc.dart
43.47% <0.00%> (-0.53%)
:arrow_down:

.../presentation/signup/states/bloc/sign_up_bloc.dart
34.21% <0.00%> (ø)

...ates/check_user_bloc/bloc/check_username_bloc.dart
0.00% <0.00%> (ø)

...tes/check_user_bloc/bloc/check_username_event.dart
0.00% <0.00%> (ø)

...et_private_key_bloc/bloc/get_private_key_bloc.dart
0.00% <0.00%> (ø)

...t_private_key_bloc/bloc/get_private_key_event.dart
0.00% <0.00%> (ø)

... and 1 more

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Console?

Will we provide console?
Unless, to where stdout of lambda will print out?

Decide it supports stdin or not. maybe it required some argument for process.

if it will support stdin, we should find the way for mapping stdin (or similar process for make stdin)

select one of type: real time console or not.

if it won't support stdin, we don't need make any decision.

Stdout mapping is not difficult issue than stdin. first of all, decide support stdin or not

@TaeyoungJang
I'm not considering stdin, and all functions using stdin will throw an exception.
so no stdin

Ok, I'm closing this issue, and concluding that we don't have console, but I'm gonna consider other options to handle STDOUT

Ok, I'm closing this issue, and concluding that we don't have console, but I'm gonna consider other options to handle STDOUT


Update the script to build the css and minimize it to work with the files checked in

I was running into issues starting fresh locally working with the CSS and noticed that the script for building the css didn't point to the write files or included the compressed style of the finished output.  This should fix that part.

I like this idea. It exposed a potential hole in my build and upload process that uses gulp.
My normal development cycle uses VSCode and I've just got sass watching for changes. Then my gulp upload task can just grab the pre-compiled scss.
Would you be ok with this becoming a gulp task, and then including it in npm scripts as your pull request has?

Well... Moving it to gulp was a good idea but gulp-sass and the live sass compile extension in VS code produce every so slightly different css. One liked to add a few -webkit vendor prefixes, and the other -moz. It would be a lot of diff churn and I don't feel like sorting out exactly why they're slightly different.
I'll go ahead and merge your fix.


[OTel Demo] - Quote Service Metrics

This OTel Demo PR added metrics to the PHP service.
We need to add the process to the docs.

thanks for raising this @julianocosta89 !

@open-telemetry/demo-approvers @open-telemetry/php-approvers is this still relevant?

Yes, we need to update this section: https://opentelemetry.io/docs/demo/services/quote/#metrics
I can take care of this

thanks @julianocosta89

if this issue is still active, please assign this issue to me, thanks

hey @kennykguo, Please note that we are not assigning issues, as per our contribution guidelines, if you are interested to work on this issue let us know, and we keep track and wait for a PR from you. I recommend that you pick 1 or 2 issues you fill confident to provide a PR for within ~2 weeks.

@brettmc do you think we have something to add to the Metrics section of the PHP service in the docs?
Otherwise I'll just close this issue

do you think we have something to add to the Metrics section of the PHP service in the docs?

Yes, I've just submitted a PR to add some manual metrics to quote service (there are some auto-generated ones there already), then I'll update the Metrics and Logs sections of the docs.


Feature: disable HVF per VM in macOS VM Config

Not sure if this is feasible to implement, as the emulator used is platform and target architecture dependent. Use case is a user with multiple different virtual machines of which some run fine with HVF and some don't. For example, I have a Windows 7 VM that works fine with HVF but a Mac OS X Lion one that doesn't. This means that I need to return to UTM preferences often to check and uncheck "Force slower emulation".

Added in https://github.com/utmapp/UTM/commit/72bf274a6e711bfe708c67fec6a6f7af3d78bca8#diff-bc255c7c28d4fefbfade29423c6e3d82a824f8a6b6569d24b0e32d2d3bf6a309


feat: add project settings and marker manager to global show list

Let me know what you think. As always thank you for this gamechanging script!

Alright thanks! I'll merge it

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


Bar does not show up anymore

After upgrading my Xcode to 8.0 and my project to Swift 2.3, the Bar indicating the current view controller in my Bar Button Pager does not show up in 2 out of the 3 places in which I use this feature.  As far as I can tell, they are all configured the same except for slight variation in sizing of the height of the Button Bar View.
I can still see the Indicator titles and functionality is fine.

Yeah its not working ... any remedy ??

I updated to Swift 3.  Issue still remains.

My bar disappears when I use "add missing constraints" in storyboard but the title and everything is seems to be working fine. I'm also using swift 3.

I met the same bug.
Why
It is bcz in the function updateSlectedBarYPosition , selectedBar.frame is zero
How to fix it
I used code instead of Xib, I set frame as zero, now I set frame with screen.width. it worked.
let frame = CGRect(x: 0, y: 0, width: screenWidth, height: Constants.NavigationSwipBarHeight)
buttonBarView = ButtonBarView(frame: frame, collectionViewLayout: UICollectionViewFlowLayout())

I didn't use the stroyboard, I believe you can set the initial frame like this.

Anyone could fix it?

Any fix for anyone who used auto layout

@ashanatexilesoft I added this line and the buttonbar got visible again...
self.buttonBarView.collectionViewLayout = UICollectionViewFlowLayout()
self.buttonBarView.frame.size.height = 40

@anafinotti Yes! This made my bar appeared again. Thank you so much. :)

@anafinotti's solution worked for me too!

Seems to be an issue with the origin being incorrectly calculated. I added the following to the first line in updateSelectedBarPosition of ButtonBarView.swift:
selectedBar.frame.origin.y = self.frame.size.height - CGFloat(self.selectedBarHeight)

@anafinotti to which method did you add the lines in your solution?

after ViewDidLoad
add below code , it works to me
self.view.layoutIfNeeded()
buttonBarView.selectedBar.frame.origin.y = buttonBarView.frame.size.height - settings.style.selectedBarHeight

I may be reading this all wrong, but it appears that the original post was regarding the selected bar (i.e., the thin, orange bar in the ButtonBar and Bar type pager screenshots and examples). Some of the replies seem to be solving different problems. I too am seeing the missing selected bar issue, and was able to fix it using the code posted by @cruisediary. I added the code to viewDidLoad just after the call to super.viewDidLoad().
Some additional info. Prior to the fix the selected bar is present, just being clipped. You can see it using Xcode's View Debug Hierarchy and then selecting Show Clipped Views:

Those of you who used @anafinotti 's solution, can you try switching the order of button bar and container view in storyboard? Set container to be first and button bar second. It seems adjust scroll view insets (which is on by default) causes this issue and there's no need for any workarounds.

@jnemecekitk I confirm that disabling "Adjust Scroll View Insets" fixes the issue


add more sponsors

@q9f I see the URL is to abacus but the logo is hyperlane. Can please check that entry?

@q9f I see the URL is to abacus but the logo is hyperlane. Can please check that entry?

Yes, I double-checked with them. This is intended.


Constants deprecation fix & manifest updates

Starting in Home Assistant 2024.1 users will get bombarded with a log message for every deprecated constant that is being used. While the integration will continue to work, the log messages will continue until this is fixed and will ask the users to report this to the integration maintainer. By release 2025.1, if these changes haven't been made, the integration will fail to load. This PR addresses the needed changes and is an attempt to get ahead of the 2024.1 release so you aren't bombarded with users attempting to report the issue.
Info regarding deprecations can be found at these two links:

https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation/
https://developers.home-assistant.io/blog/2023/12/19/constant-deprecation

Specific changes in this PR
Const.py, humidifier.py, sensor.py
Enums are used (SensorDeviceClass, UnitOfTemperature, UnitOfTime, HumidifierEntityFeature, UnitOfEnergy, UnitOfPower) instead of the deprecated constants.
common.py
The logging level for devices found has been changed to debug instead of warning. There is no need to log what devices are returned by the API unless the user is attempting to investigate an issue in which case the appropriate debug level will be set by the user for the integration. Setting the level to warning creates unnecessary noise in a user's log.
manifest.json
The documentation and issues URL has been changed to your repo. The way it stands, the current deprecation warnings and any future warnings would instruct users to open an issue on the now archived repo instead of this repo. This change will now correctly send users to create reports on this repo.
The documentation URL was linked to the official VeSync Home Assistant integration - not sure why this was ever the case since that documentation is not 100% reflective of this integration. Custom component documentation should always point to the custom component's repo URL where the README is located.
Side note: I see that issues are not enabled on this repo, which means users won't be able to report any issues with the integration until they are enabled.
README
I commented out the HACS default badge since this repo is not in the default HACS repo list. The badge may confuse users into thinking that they can search for the integration in HACS without needing to add the repository first to HACS (which would be the case if the repo was in fact a default HACS repo). If you do choose to go through with getting this repo added to the default HACS repo, then adding the badge back will involve just removing the markdown comment line.
Thanks for taking over the repo!

Please merge this. It's not just the deprecation messages.  With these changes, everything works fine.
Btw. since this is the reference fork now, please enable the issue tracker.

In case it's any use, the specific error in the log (which prevents the humidifier entity from working) is:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 243, in _handle_refresh_interval
    await self._async_refresh(log_failures=True, scheduled=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 399, in _async_refresh
    self.async_update_listeners()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 182, in async_update_listeners
    update_callback()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 941, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1062, in _async_write_ha_state
    state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1001, in __async_calculate_state
    attr.update(self.state_attributes or {})
                ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/humidifier/__init__.py", line 217, in state_attributes
    if HumidifierEntityFeature.MODES in self.supported_features:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'int' is not iterable

Incidentally, I just came across this repo today and am still using the original version by @vlebourl. Is the replacement process a case of: uninstall original custom integration, then add and install this integration?

@Valdorama

Delete the old custom repo link in HACS (don't delete the vesync integration!).
In HACS, add the new custom repo: https://github.com/micahqcade/custom_vesync/
Search for the custom vesync repo in HACS, click on it, in the upper right-hand corner click on the overflow menu (3 dots), select redownload, and click on download - this should replace all the integration files that you have in the custom_components/vesync folder from the old repo with files found in this repo. HACS will use this new repo to check for future releases.

In order to use the changes that I have made in this PR:

Replace the code found in custom_components/vesync/const.py with the code found here: https://github.com/micahqcade/custom_vesync/blob/c330ed303601331f539f3450e57f515d4b4cf999/custom_components/vesync/const.py
Replace the code found in custom_components/vesync/common.py with the code found here: https://github.com/micahqcade/custom_vesync/blob/c330ed303601331f539f3450e57f515d4b4cf999/custom_components/vesync/common.py
Replace the code found in custom_components/vesync/humidifier.py with the code found here: https://github.com/micahqcade/custom_vesync/blob/c330ed303601331f539f3450e57f515d4b4cf999/custom_components/vesync/humidifier.py
Replace the code found in custom_components/vesync/sensor.py with the code found here: https://github.com/micahqcade/custom_vesync/blob/c330ed303601331f539f3450e57f515d4b4cf999/custom_components/vesync/sensor.py

After doing all of that, restart Home Assistant for the changes to go into effect.

@RobertD502 Thank you so much for the detailed reply!

@RobertD502, I also thank you for the detailed reply. Your instructions
were very helpful and got my humidifiers working again after the latest
HomeAsistant update.
On Thu, Jan 4, 2024 at 6:14 PM Valdorama @.***> wrote:

@RobertD502 https://github.com/RobertD502 Thank you so much for the
detailed reply!
—
Reply to this email directly, view it on GitHub
https://github.com/micahqcade/custom_vesync/pull/1#issuecomment-1877890353,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BE4U3CTYI776BLEVF3OURXDYM4ZVFAVCNFSM6AAAAABBJIKFJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXHA4TAMZVGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

looks like we need to manually modify the code on the HA installation, do you plan to have this implemented in the next release?

It seems the latest HA release fixed humidifiers, specifically https://github.com/home-assistant/core/pull/107026. Mine is no longer "unavailable" after updating HA

Please merge this. It's not just the deprecation messages.  With these changes, everything works fine.
Btw. since this is the reference fork now, please enable the issue tracker.

Came here to find this exactly. Unfortunately found the instructions too late and have already deleted the VeSync integration. However, adding it back and re-setting everything up seems to have worked fine, only real 'issue' now is that one of my Core 300s units is not showing any "Air Quality Value". The entity is just missing entirely.

2 300s' show the AQV.
1 600s shows the AQV.
But this one doesn't. I'm not sure why, all of the 300s units are on the same firmware version: 1.1.10(2.0.13).
And no, the Air quality value is incorrect (showing a 1 when the AQV would be say, 80).
And yes, the issue tracker would be nice to have since currently there is nowhere else to report issues as the old repo is read-only.
My current HA install is Core v. 2024.1.1
Supervisor 2023.12.0
Operating System 11.3
Frontend 20240104.0

Maybe it is still broken...this is from 2024.1.4...
2024-01-19 15:46:33.070 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry<EMAIL_ADDRESS>for humidifier
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 561, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/humidifier/__init__.py", line 135, in async_unload_entry
    return await component.async_unload_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 203, in async_unload_entry
    raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!^[[0m
2024-01-19 15:46:33.071 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry<EMAIL_ADDRESS>for button
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 561, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/button/__init__.py", line 77, in async_unload_entry
    return await component.async_unload_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 203, in async_unload_entry
    raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!

Thanks for making these changes!
I see these errors with 2024.1:
Entity None (<class 'custom_components.vesync.humidifier.VeSyncHumidifierHA'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <HumidifierEntityFeature.MODES: 1>, please create a bug report at https://github.com/vlebourl/custom_vesync and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
1:53:28 PM – (WARNING) helpers/entity.py
SUPPORT_MODES was used from vesync, this is a deprecated constant which will be removed in HA Core 2025.1. Use HumidifierEntityFeature.MODES instead, please create a bug report at https://github.com/vlebourl/custom_vesync
1:53:26 PM – (WARNING) Humidifier
DEVICE_CLASS_TEMPERATURE was used from vesync, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.TEMPERATURE instead, please create a bug report at https://github.com/vlebourl/custom_vesync
1:53:26 PM – (WARNING) helpers/deprecation.py - message first occurred at 1:53:25 PM and shows up 5 times

Will this PR get merged?

Thanks for getting this PR done, I was just looking at doing something about the "found devices" warning, but saw you covered this too.
@micahqcade any chance this could be merged please?

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
migege, @Zhanxueyou, @lovekpo, @wxthon, @legos4, @rashidmya, @jcbjcbjc, @Lunaticf, @0xvivi, @prateektiwari7, @wangyanchao, @gaosy87, @hanky312, @CockyCat, @fixedelineation, @usoop, @whatisoop, @thednp, @Arutha3, @kelthzuard, @oblank, @xiao93, @ricemouse, @runesign, @Flowlessx, @yinghuihong, @johnny-yue, @yiwang, @liyuechun, @clockworkgr, @testzcrypto, @zhouxiaobao-2010, @lookforwardto, @coolspeed, @yumenohosi, @Almagest01, @KambizAsadzadeh, @jhonsu01, @MiracleZhang, @wangleihd, @bitcard, @ewssir, @phantomcoco, @stjordanis, @mosjin, @Dimfred, @feng1990liu, @quantlord, @0xae, @idemkmillionu

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
timothyklim, @foxboxparadox, @linkwechat, @why168, @coinevernote, @micahqcade, @yjjnls, @ety001, @debuggor, @lchengsh, @xeoshow, @zapply, @alphafoobar, @sagar-man, @andreviegas, @squarezhou, @adotsloan, @Stepease1, @predmach, @Doracoin, @q158073378252010, @deepbits, @devilzz63, @BarrySauce, @hwlsniper, @debrayc, @hotraygroup, @haojianyun, @stmic999, @aprasadh, @1detgrl, @xuefengcl, @bmwcmw, @etale-cohomology, @HarukaMa, @bittree9527, @faddat, @grctest, @ruslanys, @operano02, @broker, @dotneet, @betachen, @bartlomiejbeta, @dopearsall, @realm520, @Honglei-Cong, @bliu2000, @sealter, @dust

It doesn't look like @micahqcade is active. Does anyone else want to take over?

Sorry my wife has been sick I'll merge the changes this week; I am sorry for missing this.

Sorry my wife has been sick I'll merge the changes this week; I am sorry for missing this.
No need to apologise, family and health should come first, I hope your wife is on the mend.


Cursor jumping around on typing

On 678f87ed45c0f18a76ad19fa9de555e77dea78a8
Steps to Reproduce:

Enable outline
Open a json file:

{
    "a": {
        "b": 1,
        "a":
    }
}

Type a value for a.a in the json file

Bug

Only seems to repo when outlined is enabled

Seems caused by the calls to _revealTreeSelection. Doesn't repo 100% of the time. May require switching back and forth between some files first

This is horrible 😅 Was thinking i was being pranked.
Thanks for the workaround.

🙈 happens to me as well, also inside TypeScript files. VSCode Insiders basically not usable right now 😞

When will this be updated to Vscode Insider Release, VSCode it totally unusable right now.

Yeah, I can push another release for today

ETA on release?

@changavila @jrieken @whimzee Meanwhile you can disable the "outline". that'll fix it for now.

@juristr How do you go about disabling it?

Which one??
Outline does not exist in settings.

Keep in mind you can also use the stable version of vscode until this is fixed. Stable is working fine.

@WoodyWoodsta just in the vscode file explorer, right-click on the title area and uncheck "outline"

I'm using 1.25.1 (stable) and running into the same issue. It's only started recently though.
Using Windows 10

I don't remember enabling any "outline" setting though.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/159 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 3a746c9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-10-09-09-29-46 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-10-09-09-29-46

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[BUG][Functional] Route53 API Errors route53-recovery-readiness and route53-recovery-control-config

Bug reports which fail to provide the required information will be closed without action.
Required Basic Info

Accelerator Version:  v1.5 but also seen in v1.3.6 environment
Install Type: Clean
Upgrade from version: N/A

Describe the bug
Route53 APIs are now split over 4 API sets:
"route53:",
"route53domains:",
"route53-recovery-readiness:",
"route53-recovery-control-config:",
The first two are part of  "Sid": "GBL1" SCP but not the last two, causing
Route 53 couldn’t update the page
Route 53 encountered an unknown error and couldn't update your page. Try refreshing the page.
API error messages
User: arn:aws:sts::xxxx:assumed-role/Admin/xxxx is not authorized to perform: route53-recovery-readiness:ListReadinessChecks on resource: arn:aws:route53-recovery-readiness:us-west-2:271715271383:readinesschecks/* with an explicit deny
User: arn:aws:sts::xxxx:assumed-role/Adminxxxx is not authorized to perform: route53-recovery-control-config:ListControlPanels on resource: arn:aws:route53-recovery-control-config:us-west-2:271715271383:$arn{} with an explicit deny
Failure Info

What error messages have you identified, if any:
What symptoms have you identified, if any:

Required files

Please provide a copy of your config.json file (sanitize if required)

Steps To Reproduce

Go to Route53 console in the Shared Net work account. You will see the API error messages.

Expected behavior
A clear and concise description of what you expected to happen.
IMHO SCPs should be adjusted to allow those new APIs
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Adding
"route53-recovery-readiness:",
"route53-recovery-control-config:",
to GBL1 SCPs and rerunning the state machine, resolves the issue.

New global services added to SCPs in PR#885


Infrastructure for nightly releases

I found some resources for our proposed nightly builds and hosting solutions plus options as to how we can configure them to work with our existing release infrastructure.

Anaconda provides artifact storage as a custom PyPI repository and offers 5 GB of storage on a free plan. The paid plans start from $9/month. Note: this method will require the creation of our own Anaconda organisation since the scientific-python repository is not open for packages outside its ecosystem. Some examples of this are
a. NumPy and SciPy store their weekly wheels in this repository: https://anaconda.org/scipy-wheels-nightly/repo
b. Some packages under the scientific-python umbrella (scikit-learn, pandas, matplotlib, xarray, et cetera) publish at https://anaconda.org/scientific-python-nightly-wheels/repo
c. Anaconda’s own repository
d. AstroPy used Azure earlier, now they use Anaconda.
Cloudsmith.io provides an expensive artifact repository priced at $89 per user per month.
Google Cloud Artifact Registry provides hosting and storage for Python packages. This is an enterprise solution so it might be private-only, I am not sure if it can be used for public, open-source projects.
A Homebrew formula using Ruby for PyBaMM (this one is a mostly undocumented and niche solution and does not have many resources to seek. Requires submission to and acceptance from homebrew-core. Here is a tutorial I found: https://til.simonwillison.net/homebrew/packaging-python-cli-for-homebrew). cookiecutter is an example of a Python package that has been packaged for Homebrew, since it is possible to install it with brew install cookiecutter. This solution would be available for Linux and macOS only, since Homebrew does not support Windows.
Nexus Repository from Sonatype has support for many packaging formats and supports proxying and hosting for PyPI packages. This might also be a private-only solution.
Artifactory also provides a super expensive artifact registry plan priced at $150 per user per month.
PEP 503 describes how we can make our own PyPI repository for indexing. Anaconda is compliant with this specification. Some self-hosted solutions that are compatible with this comprise
a. devpi
b. pypiserver, and a tutorial by Linode to accompany it
c. Artipie, an open-source PyPI package repository
d. Pulp is another self-hosted package index that can be used as described in this blog by Red Hat
I looked at GitHub Packages (https://github.com/features/packages) and found it to be pretty cool, but it doesn’t support Python packages yet and probably will not. There have been discussions around this in their roadmap earlier, but they closed the feature request, sadly: https://github.com/github/roadmap/issues/94, possibly because Microsoft owns GitHub; so they have more precedence over what the folks at GitHub end up doing—plus I assume that they would like to keep Azure as the standard for a Python package registry, rather than offer a competing standard.
However, related to point 7, we could create a PEP-503 compliant pybamm-team/pybamm-nightly repository and push wheels to it daily. The size of a PyBaMM installation is around 160 MB, sourced from (libraries.io). We could write a workflow to delete releases older than 30 days so that the size of the repository remains limited. scientific-python has a workflow to do this in their Anaconda index. Though there is no real-time vulnerability detection in this case like how other commercial solutions provide, we have more control over our release infrastructure anyway and we can mitigate bad actors. It is easy to install a package from GitHub as well since we can use pip install git+ with the version from the release tag. There are many resources available, some of them I found are
a. https://www.freecodecamp.org/news/how-to-use-github-as-a-pypi-server-1c3b0d07db2/
b. https://medium.com/network-letters/using-github-as-a-private-python-package-index-server-798a6e1cfdef
c. An example of a PyPI index hosted as a GitHub repository: https://github.com/astariul/github-hosted-pypi which works with GitHub Releases. The total size of cumulative GitHub Releases has no limits, but individual releases have to be below 2 GB each, which is many margins above our release size.
The GitLab package registry supports PyPI packages. We could host a read-only mirror of PyBaMM on GitLab that gets updated with every commit to the develop and main branches. The better way would be to create a package registry there and write a GitLab CI pipeline to download artifacts from a GitHub Actions pipeline that uploads them, therefore starting a chain of CI/CD pipelines. Some resources (GitHub Actions in the marketplace, StackOverflow answers, and blogs) that might be useful in this case are listed below.
a. https://github.com/marketplace/actions/trigger-gitlab-ci
b. https://stackoverflow.com/questions/63308904/push-to-gitlab-with-access-token-using-github-actions
c. https://github.com/marketplace/actions/trigger-gitlab-ci-through-webhooks
d. https://github.com/marketplace/actions/trigger-gitlab-ci-job
e. https://github.com/marketplace/actions/gitlab-pipeline-trigger
f. https://dev.to/edersonbrilhante/gitlab-runners-as-a-service-with-github-action-149n
g. https://www.anapaulagomes.me/2021/04/publishing-your-python-package-in-your-gitlab-package-registry/

We might need to ensure that the guide to downloading and using nightly releases is documented properly and warn unsuspecting users from using them. An edge case to take care of is that pip does not fall back to using PyPI to download via the --extra-index flag if a package is not found on the custom index which is a common modus operandi for dependency hijacking attacks. Source: https://discuss.python.org/t/advice-to-avoid-extra-index-url-to-install-private-packages-from-gitlab-ci/18242/11

I think either Anaconda or GitHub Releases would be the best methods overall. Both of them can be integrated with the existing release infrastructure very well

We are below the 5Gb limit so we can try the Anaconda free plan https://pypi.org/project/pybamm/#files

Hello! I work at Cloudsmith. :-) Small correction is that it's $89 flat pcm, not per user, at Cloudsmith.
Happy to help with questions!

Hi there @lskillen, does Cloudsmith's artifact management solution offer a free plan for technical open-source scientific projects like PyBaMM? The reason I ask this is because I found this resource in the Cloudsmith guides: https://help.cloudsmith.io/docs/open-source-hosting-policy, it would be great if we do qualify as an apposite project!

Hi there @lskillen, does Cloudsmith's artifact management solution offer a free plan for technical open-source scientific projects like PyBaMM? The reason I ask this is because I found this resource in the Cloudsmith guides: https://help.cloudsmith.io/docs/open-source-hosting-policy, it would be great if we do qualify as an apposite project!

If it's open-source, I don't see why? 😁 Generally we don't require pre-approval for OSS projects, just signup, create an OSS repository, add a license, and away you go. All we require is an attribution link to say we're providing it for you. Approval is only needed is you start to use significantly more bandwidth (as mentioned in the doc).


[BUGFIX] Rename ernie-gen tokenizer name

PR types

Bug fixes
PR changes

Tokenizer
Description

rename "ernie-gen-large-430g-en" to "ernie-gen-large-en-430g"

docs/readthedocs.org:paddlenlp ci挂了，已反馈 @yingyibiao ，先合入。


Exporting training data error

Hello. I'm trying to export training data using the Deepness Training Data Export tool to detect building outlines in my aerial imagery. I've set my output directory path, and have my geotiff raster set in the "input layer" section, and the export image tiles option checked. I also have the Export segmentation mask for layer" option checked, and it points to a polygon shapefile of my building outlines labels seen in the imagery.
However, when I press export training data, I get this error:

Any thoughts on where my problem exists?
I'd love to train my own model and share it openly with others, but I have a bit of work to do to train a model.

Hi @jducnuigeen
Thanks for your interest and for reporting this issue! You did everything correctly, as you described, but a bug entered the code during some refactorization. It is already fixed and will be available in the next release soon.
In the meantime, you can download the latest code from here, and install it from a zip file as described in documentation. Hope everything will work now, otherwise please let me know :)

Resolved in release 0.5.1


wpbakery compatibility does not account for bucket_folder name

When adding an image to a gallery using wpbakery page builder, I receive the following error:

In our GCS buckets, and in the wp-stateless settings, our bucket folder (root_dir) is set to "uploads" which is not accounted for in the str_replace and results in an invalid filepath because "uploads/uploads" does not exist.
`Error is being thrown by this code: https://github.com/wpCloud/wp-stateless/blob/v2.1/lib/classes/compatibility/wpbakery-page-builder.php#L51-L57
wp eval "var_dump(wp_upload_dir());"
array(6) {
'path' =>
string(37) "/var/www/html/web/app/uploads/2019/12"
'url' =>
string(53) "https://xxxxxxxxxxx/app/uploads/2019/12"
'subdir' =>
string(8) "/2019/12"
'basedir' =>
string(29) "/var/www/html/web/app/uploads"
'baseurl' =>
string(45) "https://xxxxxxxxxxx/app/uploads"
'error' =>
bool(false)
}
sm_root_dir	uploads
wp eval "var_dump(str_replace('https://storage.googleapis.com/xxxxxxxxxxx', '', 'https://storage.googleapis.com/xxxxxxxxxxx/uploads/New-2018-slide-ext-9.jpg'));"
string(33) "/uploads/New-2018-slide-ext-9.jpg"
$absolute_path = $dir['basedir'] . '/' . $path;
So the resulting value of $absolute_path: "/var/www/html/web/app/uploads" + "/uploads/New-2018-slide-ext-9.jpg"`
Should the str_replace also remove the sm_root_dir?

It also looks like all wpbakery uploads have been saved to /var/www/html/web/app/uploads/uploads

Hey @jjtroberts
I was trying to reproduce your issue but I could not.
Can you provide some details about how we can replicate it?
Maybe some specific steps or configuration.
I was trying to upload images from inside the Image Gallery component and it all works with custom Bucket Folder setting.
My version of WPBakery is 5.3 and WP is latest.

I don't recall which site this error took place on. I'll close this issue and if it recurs I'll create a new issue.


Remove "Building an Advanced Web Test Plan" template

Hi,
Remove "Building an Advanced Web Test Plan" template
Everyone use the recorder to create a Web test plan.
The documentation is enough
Antonio

I  think this template can be useful to see a sample structure of a web test plan.
It is also used by the manual.
I use it for debugging.
So IMHO, we should keep it but maybe change listeners.


Update command gui namespaces

The arm command gui needed to be updated with the new "victor/" prefix.

Is there a better way to namespace these functions, given we will be launching via rosrun victor_hardware_interface arm_command_gui.py? I'm looking for setting the namespace in the rospy.init or similar.

There are probably other files that should be updated accordingly, but I have not searched.

You can set the namespace via the encouragement variable ROS_NAMESPACE but I don't think rospy init has an argument for that. Tbh I think doing it manually is the right way because not every topic in a node should be remapped.


(#379) Validate old config file do not exist

Description

The changes in this pull requests adds an additional check to ensure that no new configuration file is created, even in the case that a configuration file with the old legacy name exist.
Related Issue

fixes #379
Motivation and Context

How Has This Been Tested?

A new unit test has been created to test the new check.
Screenshots (if appropriate):
Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@AdmiringWorm thanks for getting this added!


If that was the wrong commit, why not update this to use the right one (and keep the date/prefix/etc)?


Make Contact-us page functional

Architecture: propose a subtle architecture to get assigned
package: nodemailer

@shaurya35  Please provide more description

Architecture: propose a subtle architecture to get assigned package: nodemailer

hello @shaurya35, i can work on making contact us page working few reasons:

i have implemented otp based verification on other projects, so i am well versed with nodemailer working

my idea:

using form to collect data (currently form layout is made, just have to integrate with states and collect input field data)
creating an api endpoint to collect these data on backend
on backend sending users message with user data (name, email id, message) to owner, and also sending a mail to user's email id to verify them their message is been sent
designing a html layout for proper formatting of mail


Error: The service is unavailable.

Does this occur consistently?
Repro steps:

Go to https://docs.microsoft.com/en-us/azure/app-service/quickstart-nodejs?pivots=platform-linux
Follow the instructions.  That's all I did.  It's a "hello world" app, it shouldn't be out of resources.  I generated the express app, installed the azure extension and attempted to deploy twice with the same result.

Action: postCreateWebApp
Error type: 503
Error Message: The service is unavailable.
Version: 0.18.0
OS: darwin
OS Release: 19.6.0
Product: Visual Studio Code
Product Version: 1.48.0
Language: en

Call Stack
extension.bundle.js:309:388829
retryCallback extension.bundle.js:225:116429
retryCallback extension.bundle.js:157:31051
extension.bundle.js:157:32664
handleRedirect extension.bundle.js:171:7747
extension.bundle.js:157:29836
Request._callback extension.bundle.js:1:593285
Request.r._callback.r.callback.r.callback extension.bundle.js:201:4468
Request.emit events.js:203:13
Request.<anonymous> extension.bundle.js:201:17577
Request.emit events.js:208:15
IncomingMessage.<anonymous> extension.bundle.js:201:16367
Object.onceWrapper events.js:291:20
IncomingMessage.emit events.js:208:15
endReadableNT _stream_readable.js:1168:12
processTicksAndRejections task_queues.js:77:11

I deleted the app and recreated it manually in windows and it works

Yeah service unavailable errors can happen from time to time and it usually works if you just try again. There's also these troubleshooting tips for future reference:
https://docs.microsoft.com/azure/app-service/troubleshoot-http-502-http-503


SceneTree tab does not immediately reflect undo action

Godot version:
3.2.4 RC2, RC3
OS/device including version:
macOS Big Sur
M1 Mac Mini
Issue description:
After some undo actions, such as undoing moving or deleting nodes, the SceneTree tab does not visually reflect the undo until the user clicks somewhere inside the tree tab. Other actions, such as undoing an "add new node" or renaming a node, still work normally.
Bug is present in 3.2.4 RC2 and RC3, but not present in RC1. So RC2 introduced the regression.
Steps to reproduce:
Add some nodes into the scene, move or delete them, then undo the action.

can't reproduce the issue on a non-M1 MBP with MacOS 10.14.6

My mistake, I got RC2 and 3 mixed up in my testing - it's been fixed somehow in RC3. Closing this then :)


File download name

In siphon overview we're calling a download file data.nc4... it's not netCDF 😞 Let's just call it data.

Closed via #361


fix: Break out Superdrawer validation

CH5749
Description (what was changed/updated/added.. etc…)

This PR fixes an issue with the Superdrawer where the drawer would open and close when the Previous/Next buttons were pressed. The fix was achieved by:

pulling the Superdrawer validation checks that were previously done within useSuperdrawer's onClose method into a new private function, validateDrawerChange. This allows the openInDrawer method to validate that ta new drawer can be opened, without closing the current drawer.
Always having the confirmation modal's Close button run closeModal

Screenshots (if UI was changed)

Before (buggy behavior)
https://user-images.githubusercontent.com/36432040/128536372-9373ea48-c16e-4eb6-8992-771110fd59cf.mov
After
https://user-images.githubusercontent.com/36432040/128536394-d88e8eb9-8c6c-4e69-a07f-5efc72b5528b.mov
Mental Checklist

[x] Updated tests for this change.
[x] Tested changes locally.
~- [ ] Updated Documentation (if necessary).~

whoa, sweet @khalidwilliams ! this made my day! :)


DurationArgumentType

#182 Added Duration type.
Takes a string in this format: 1mo2w3d4h5m6s7ms or 1mo 2w 3d 4h 5m 6s 7ms.
The issue mentioned having methods for this type but I don't believe they can be accessed. If I'm wrong about that, it would be a quick to add them back in.

I'll make those changes. None of these popped up from npm test or npm run lint for me.


OCaml 5+ is a multicore release

Partial fix (hopefully) for the problems being seen with lwt, etc.

This is deployed on live at the moment, and has unblocked, say, Lwt. See also https://github.com/ocurrent/ocaml-version/issues/58.

Now that OCaml 5 is multicore, it's possible that a lot of this special-case trickery used for multicore isn't necessary. However, it's important if that's implemented to be sure that we don't lose the testing matrix... e.g. for Lwt, the main libraries should continue to be tested on 4.08-5.0 with lwt_domain only being tested on 5.0.

This explicit is_multicore code has been removed and should be handled correctly in solver-service / ocaml-ci. I've added a test in https://github.com/ocurrent/solver-service/pull/73 to be more explicit about it.
It might also be useful to have some testing in ocaml-ci to ensure certain packages have stable Analysis results. LWT project being a good example which should have a solution for many older OCaml versions.


VLAZ: Watch icgram.com

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

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

Approved by Dragonrage in Charcoal HQ


forc require openssl shared lib

$ ~/.fuelup/bin/forc --help
/home/john/.fuelup/bin/forc: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

This is weird because I was expecting it to be statically linked?

I've opened https://github.com/FuelLabs/sway/issues/1742 with a little more context.


Tab Navigation setParams freeze screen

Hi, I tried to call setParams from a screen inside a tab navigation and it freeze the screen. Is there no way to setParams when inside a tab? Any other solution if I want to pass this.props to the navigation option then?
This is the code inside my screen:
componentDidMount() {
        this.props.navigation.setParams({handleTextSearch: this._onHandleChangeTextSearch.bind(this)});
    }
_onHandleChangeTextSearch(text) {
        this.props.searchTopicList(text);
    }
static navigationOptions = ({navigation}) => {
        console.log(navigation.state.params.handleTextSearch);
}

Thanks.

Can you provide a demo of this issue?

Hi, @spencercarli , I created a new project to reproduce the issue and found out how the issue crops up.
Current Behavior
I have a splash screen that will check if my app should show a login screen or enter home screen (tab navigation). The issue crops up whenever my app enter the home screen. The screen freezes up

Expected Behavior
From splash screen, the app should have open the home screen.

The project to reproduce can be grabbed here:
https://github.com/adhicl/emptyprojectv20
(is this what you mean?)
The problem of the code is in
Tab1Screen.js
componentDidMount() {
        this.props.navigation.setParams({
            handleEnterChild: this._onHandleEnterChild.bind(this)
        });
}

My Environment
(I am using expo)
| expo | ^20.0.0",
| react |16.0.0-alpha.12",
| react-navigation | ^1.0.0-beta.11
| react-native | https://github.com/expo/react-native/archive/sdk-20.0.0.tar.gz
| react-redux | ^5.0.6
| redux | ^3.7.2
| redux-thunk | ^2.2.0

Hi @spencercarli, is my post before has enough information? Need anything more?

This may be an infinite loop related to my issue here: #2702

Hey @adhicl thanks for that repro. Swamped by the number of issues but hopefully, this can get sorted out.

@tehwayne yes, it looks to me that it freezes because of the infinite loop. I'll close this in favour of the other one.

okay. I will watch to the other tread then


Using defineOgImageScreenshot() with no prerendering on Vercel

Details
This is a fantastic library!
I'm able to generate static screenshots, but I'd like to be able to dynamically generate some on Vercel.
Locally (Mac OS), using defineOgImageScreenshot() for dynamic generation of images works fine as I have all the necessary dependencies available system wide.
Vercel serves me an empty 204 response.
Is there a configuration option I'm missing? I've ensured playwright is part of build step but I'm unsure if this is available to the app once deployed.

Hi, I got the same issue as yours. I can't get it dynamically generate screenshot on Vercel. Works fine locally.

Hey guys, currently it's not supported to take browser screenshots at runtime. This is because you need to have a chromium binary and it's very heavy and slow.
You should look into using the Satori provider if you need runtime images.
Saying that I will support it under a flag, might be a few days before I can take a look though

In 1.4.4 you can try enabling the experimentalRuntimeBrowser config. You may need to explicitly add playwright as a dependency

I opt for the defineOgImageStatic because the playwright is very slow and heavy indeed.

Going to close, flag is available if anyone is brave enough to try.


Not available on Pursuit anymore

The readme links to http://pursuit.purescript.org/packages/purescript-inject, resulting in 'Package not found'.

It's back on Pursuit now, thanks for the note!


prevent spoofed beacons from transmitting

Version info
Tested on the latest version from git but I observed this behaviour for several prior versions:
root@DietPi:~/blah# hcxdumptool -v
hcxdumptool 6.3.4-14-g3693e77 (C) 2024 ZeroBeat
running on Linux kernel 6.1.21+
running GNU libc version 2.36
compiled by gcc 12.2.0
compiled with Linux API headers 6.6.20
compiled with GNU libc headers 2.36
enabled REALTIME DISPLAY
enabled GPS support
enabled BPF compiler

root@DietPi:~/blah# hcxdumptool -l
  0       2     deadbeef1    deadbeef1    -       wlan0                   brcmfmac        NETLINK
  1       3     deadbeef2    deadbeef2    *       wlan1                   mt76x2u NETLINK

Describe the bug
I am unable to prevent hcxdumptools from transmitting beacons of SSID networks that are requested by the client.
I have various hidden and offline networks configured on a client and I can see them each time I run hcxdumptools, it's a mix of hidden network and visible networks but that are offline. I have tried to configure --proberesponsetx=0 but it can't be set to 0.
The options --disable_proberequest and --disable_beacon (which I think is jsut for the wildcard SSID?) also does not prevent the beacons from being transmitted.
Is there any other setting that I am missing and should be set, I believe it may be a bug that it's still transmitting the spoofed beacons for these networks.  I am 100% sure these networks are not active because the access points associated with them no longer exists (physical hw).
To Reproduce
run hcxdumptool with a client that has hidden network configured or with a network that is not online
Expected behavior
I expect to not see spoofed SSID beacons of networks that are not currently active

There are three kinds of attacks, which can be disabled by options and by a Berkeley Packet FIlter (BPF).

attacks against an AP
attacks against a NETWORK (AP and connected CLIENTs)
attacks against a CLIENT

To disable attacks on CLIENTs run:
$ sudo  hcxdumptool -i INTERFACENAME --attemptclientmax=0 --disable_beacon
To monitor outgoing traffic run Wireshark on the same interface as hcxdumptool and use this filter to monitor outgoing packets:
radiotap.present.dbm_antsignal == False
or by tshark:
$ tshark -i INTERFACENAME -Y "radiotap.present.dbm_antsignal == False" -o 'gui.column.format:"No.","%m","Time","%t","Source","%s","Destination","%d","Protocol","%p","Length","%L","Info","%i"'
Capturing on INTERFACENAME'
hcxdumptool will not respond to clients. Wireshark should confirm this and you should see this kind of frames (which belongs to attack mode 1 and 2:
deauthentication
authentication
associationrequest
reassociationrequest

To protect a CLIENT, I recommend to set up a BPF and disable MAC randomization on CLIENT side!
BTW:
At specific time intervals CLIENTs transmit a PROBEREQUEST to a NETWORK SSID stored in their wpa_supplicant.conf
hcxdumptool will show you the entire traffic on a channel. That include this REQUESTs.

Thank you for the great explanation and help, I can confirm that the --attemptclientmax=0 --disable_beacon did exactly as described and I no longer see the spoofed beacons to appear.

Glad to hear this.
You're welcome.


Make usage-/help-string behavior consistent with original docopt

Fixes https://github.com/docopt/docopt.hs/issues/32.
(moved from https://github.com/docopt/docopt.hs/pull/50 -- it looks like it'll need a few more edits now since 2.5 years ago :) )
This makes 3 main changes to this library's behavior:

pUsagePatterns (and thus pDocopt) parses out the "Usage:" section
of the helpstring as a string and returns that. The way I'm parsing
it feels really hacky but I wasn't sure a better way to achieve it.
exitWithUsage and exitWithUsaegMessage now print that "short
usage string" rather than the whole helpstring. exitWithHelpstring
has been added, which prints the whole helpstring.
parseArgsOrExit automatically exits printing the helpstring if
longOption "help" is present, to be more consistent with the
original docopt behavior. I'm not sure this is the correct place in
the library to put it, but it creates the intended behavior.

Ah, thank you for opening a new PR!


Can't use specified redis db

When I want get a pyreBloon instance I can do this,
pyreBloom.pyreBloom("gbloomfilter", 100000000, 0.001, host='<IP_ADDRESS>', port=6379)
But I have no idea that how to use a specified redis db, anyway only can use db 0.

As of the version on master, you can now provide an optional db parameter when instantiating a bloom filter:
pyreBloom.pyreBloom('key', 1000, 0.001, db=4)


chore(slideshow-controls): export component

General summary

Export SlideshowControls component.
Make Slideshow controllable externally

Screenshots

Check list

[ ] (if has style) Add need: review-integration label
[ ] (if has textual documentation) Add need: review-doc label
[x] (if has code) Add need: review-frontend label
[x] (if has react) Check through the react dev check list
[x] (if fix or feature) Add need: test label

Check out the contribution guide for general guidelines for submissions to the design system.

Test OK
Rebased, waiting for CI...


ESP32-S3 wiki update suggestion

Tl;dr The esp-idf framework does not appear to work with these boards. Stick with arduino. All other settings seem to work ok.
After a little experimentation and some frustrations, I have been able to get a handful of ESP32-S3 devices flashed and working with Bermuda 🎉. I've had one S3 running with Bermuda for a few months and I recently decided to add a few more around the house to improve detection. From the time I flashed my first device to my latest devices some documentation has been updated which suggests to use the esp-idf framework. Every time I tried using that framework I was never able to wirelessly connect to the devices after the initial install. I thought this might be useful information to add to the wiki.

Hi Chris! Thanks for letting me know what you've found.
I don't have any S3 chips myself, so I'm reliant on other reports at this stage. I notice that the esphome ready-made bluetooth proxy configs also use esp-idf for the m5stack-atom-s3, but they do specify some versions on the framework, I don't know if that might be relevant: https://github.com/esphome/bluetooth-proxies/blob/main/m5stack/m5stack-atom-s3.yaml
The arduino framework is definitely sub-optimal for ble proxies, but if it works and esp-idf doesn't it makes it an easier choice :-) that said, ESPHome recommends esp-idf for the esp32-s3.
When you flashed with esp-idf, did you do the update OTA or via usb connection? It may be worth trying a direct USB connection if you haven't already (it allows esphome to repartition the flash for extra space the BT stack can use). What exact yaml did you use?
I know there is a lot of older info around that just says the s3's don't work, but the esphome bt stack has come a long way in the last year, plus bad config advice is everywhere! I just don't want to add to the out-dated advice out on the web if I can help it, but having accurate info would be really good.
Could you share the exact yaml you tried?

I tried both OTA and via usb connection and I had more luck with the usb connection so I just stuck with that. The yaml I attempted to flash is below which is a combination of the esphome wizard and the ble configuration I used on an older S3 proxy (that also uses the arduino framework):
esphome:
  name: livingroom-bermuda
  friendly_name: livingroom-bermuda

esp32:
  board: esp32-s3-devkitc-1
  framework:
    type: esp-idf

# Enable logging
logger:
  baud_rate: 0

# Enable Home Assistant API
api:
  password: ""

ota:
  - platform: esphome
    password: ""

wifi:
  ssid: "super-secret"
  password: "thepassword"

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Livingroom-Bermuda"
    password: "yz61CdtkDqSh"

captive_portal:

bluetooth_proxy:
  active: true

esp32_ble_tracker:
  scan_parameters:
    active: True # Whether to send scan-request packets to devices to gather more info (like devicename)
    interval: 320ms # suggested 211ms # default 320ms
    window:   300ms # suggested 120ms # default 30ms

I'm using the Lolin S3 Mini fine with esp-idf. You might not be specifying the right platform options for your device. For mine, I have to either specify a newer esp-idf version that includes support for lolin_s3_mini or manually configure it like this. The flash_mode option is important:
esphome:
  name: lolin-s3-mini-test
  friendly_name: lolin s3 mini test
  platformio_options:
    board_build.arduino.memory_type: qio_qspi
    board_build.flash_mode: dio
    board_upload.ram_size: 327680
    board_upload_maximum_size: 4193404
    board_upload_speed: 460800
esp32:
  flash_size: 4MB
  variant: esp32s3
  board: esp32-s3-devkitc-1
  framework:
    type: esp-idf


An empty

 tag crashed the converter

toMarkdown('foo

 bar')

Updated in v1.3.0 but will need to look at the whitespace being stripped.


Tensorflow.NET chatbot label?? and Tensorflow.NET.Text

I know SciSharp has chatbot repositories. e.g. BotSharp etc.
However, Tensorflow.NET repository has a chatbot label.

Is there a plan to port tensorflow chatbot code (e.g. transformer) to tensorflow.NET?
Currently, it seems the Tensorflow.NET.Text project  has not planned yet.
Any feedback?
On possible milestone towards Deep NLP using tensorflow.NET e.g. recent merge for Text preprocessing?
I also notice Seq2SeqSharp has been selected. Is there a plan to integrate Seq2SeqSharp to Tensorflow.NET or in whatever form?

@GeorgeS2019 Currenty master branch is foucsed on make NLP/ NLU related task be runnable. The ultimate goal is to support BotSharp to use the state of art NLP model .NET.