[as2_core] Refactor sensors and add gimbal sensor

Basic Info

Info
Please fill out this column

Issue(s) this addresses
-

ROS2 version tested on
Humble

Aerial platform tested on
as2_multirotor_simulator, Gazebo

Description of contribution in a few bullet points
*The gimbal sensor has been added, to incorporate it into TF and publish it via a topic.
*Three utility classes have been added:

TFStatic: Adds methods for managing static transformations in TF.
TFDynamic: Adds methods for managing dynamic transformations in TF.
SensorData: Adds methods for managing sensor data and its publication via a topic.
GenericSensor: Adds utilities for managing the publication of data at a specific frequency.

Through composition and inheritance, different sensors can be added.
The Sensor, Camera, and GroundTruth classes all maintain the same interface for backward compatibility with the rest of the system.
Old sensors architecture:

Proposed architecture:

Future work that may be required in bullet points

Add more sensors, such as Odometry, and also incorporate them into TF.

Codecov Report
Attention: Patch coverage is 51.53846% with 126 lines in your changes are missing coverage. Please review.

Project coverage is 4.80%. Comparing base (96fdc4b) to head (6973d71).
Report is 48 commits behind head on main.

:exclamation: Current head 6973d71 differs from pull request most recent head 6dc382f. Consider uploading reports for the commit 6dc382f to get more accurate results

Files
Patch %
Lines

as2_core/tests/sensor_test.cpp
23.91%
0 Missing and 70 partials :warning:

as2_core/src/sensor.cpp
68.49%
11 Missing and 35 partials :warning:

as2_core/include/as2_core/sensor.hpp
54.54%
0 Missing and 10 partials :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##            main    #461      +/-   ##
========================================
+ Coverage   2.55%   4.80%   +2.25%
========================================
  Files        108     109       +1
  Lines       5999    6244     +245
  Branches     332     469     +137
========================================
+ Hits         153     300     +147
+ Misses      5660    5628      -32
- Partials     186     316     +130

Flag
Coverage Δ

unittests
4.80% <51.53%> (+2.25%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@RPS98 maybe we shall add this information in a docs/ folder ?


Uncaught TypeError: Cannot read property 'match' of undefined

I get this in Chrome any time I click the "Back to List >" link:

It is not impacting any functionality as far as I can tell.

I see this on production but not on staging or my local dev version. Are you seeing this on the latest staging? If not I'll hold off doing anything here till we push the latest staging to production.

Don't see it on staging, getting this instead:


No information on result codes

We are preparing to migrate our legacy user folders to OneDrive and I am trying to create documentation to help users understand the scan logs which we will send them. Ideally, this page should include the possible values for the ResultCode field of the scan logs, but I cannot find that information anywhere. We have performed a few test scans and I know there are at least two: INVALID_SHAREPOINT_NAME and ITEM_IS_EMPTY.
Are there more?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cfa08336-690e-0d21-6491-3f14f6d13391
Version Independent ID: 8927975a-7956-fc72-055e-36603e4eddaf
Content: Troubleshoot SharePoint Migration Tool - Migrate to Microsoft 365
Content Source: migration/troubleshooting-common-spmt-issues.md
Service: sharepoint-online
Sub-service: sharepoint-migration
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Ci updated

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@7403619). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main        #3   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         4
  Lines           ?        29
  Branches        ?         0
========================================
  Hits            ?        29
  Misses          ?         0
  Partials        ?         0

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 7403619...7dd23ad. Read the comment docs.


libpng: 1.2.55 > 1.2.56

Motivation for this change
CVE-2015-8540
Old package. Old bug. Not even sure whose using it anymore but if it's in the tree...
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[x] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

travis run out of room...

Thanks! Also backported to 16.03 as c2050a492cbbd2d2e575d26bb912c17361cc6892.

Several packages still do use it: git grep libpng12.

@vcunat I'll PR glmark2 off the new github repository with libpng 1.6 support. I'll look into the rest of them too when I'm done.


fix: [WINDOWS] ChangeSubclass after 2024-05-23 update

I dont have a linux machine, so I just updated windows signature.
But if anyone can provide linux server.so binary I can help to find it.

I took a look at the Linux signatures and they look good. I was waiting for CSSharp update, but let's merge it now. Thank you.


[mxnet_mnist_byom] How can I import mxnet model for inference only?

I have two questions on bring-your-own-mxnet model for inference only.
I followed the mxnet_mnist_byom example:
https://github.com/awslabs/amazon-sagemaker-examples/tree/master/advanced_functionality/mxnet_mnist_byom

Why do we need mnist.py as the entry_point while importing the model into SageMaker?

from sagemaker.mxnet.model import MXNetModel
sagemaker_model = MXNetModel(model_data = 's3://' + sagemaker_session.default_bucket() + '/model/model.tar.gz',
                                  role = role,
                                  entry_point = 'mnist.py')

In the mnist.py, I find there are only training related code blocks.
https://github.com/awslabs/amazon-sagemaker-examples/blob/master/advanced_functionality/mxnet_mnist_byom/mnist.py
Which part of mnist.py is essential for inference?

Will it work with .params only tar.gz?
From https://mxnet.apache.org/api/python/docs/tutorials/packages/gluon/blocks/save_load_params.html , I find the non-hybrid model cannot export a .json architecture file.

Can a params only model.tar.gz in s3 bucket be imported for inference into SageMaker?
Thanks in advance.

It doesn't look that there is any code that would be used for inference. I guess it was set because entry_point is a required parameter on MXNetModel.
The logic seems to rely on default model loading and default inference handlers:
https://github.com/aws/sagemaker-mxnet-serving-container/blob/master/src/sagemaker_mxnet_serving_container/default_inference_handler.py#L36-L68

SageMaker expects a tar.gz and this is what would be copied and unarchived for you:
https://aws.amazon.com/blogs/machine-learning/bring-your-own-pre-trained-mxnet-or-tensorflow-models-into-amazon-sagemaker/
But you can provide your own model loading function (as well as other inference handlers) and have files in any format inside this tarball:
https://sagemaker.readthedocs.io/en/stable/using_mxnet.html#load-a-model

There are more MXNet examples with SageMaker provided default functionality as well as examples on how it can be overridden:
https://github.com/awslabs/amazon-sagemaker-examples/tree/master/sagemaker-python-sdk


how to select the best model ?

Hi, after finishing training the KITTI 3D detection train + val set for 80 Epochs, which one of the trained models would be the best for submitting to the KITTI official?

Since we don't have an additional validation set, I recommend to pick the final model at Epoch 80.

Thanks!


Building package qt5:x64-windows failed with: BUILD_FAILED

I get the following error when building qt5, specifically the qtdeclarative module. From what I can tell it is having problems using python to generate the source files. I have python27 installed and it is functional for everything else on the system.
Console Output:
Building package qt5:x64-windows...
-- CURRENT_INSTALLED_DIR=C:/src/vcpkg/installed/x64-windows
-- DOWNLOADS=C:/src/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/src/vcpkg/packages/qt5_x64-windows
-- CURRENT_BUILDTREES_DIR=C:/src/vcpkg/buildtrees/qt5
-- CURRENT_PORT_DIR=C:/src/vcpkg/ports/qt5/.
-- Using cached C:/src/vcpkg/downloads/qt-<IP_ADDRESS>z
-- Testing integrity of cached file...
-- Testing integrity of cached file... OK
-- Extracting done
-- Applying patch C:/src/vcpkg/ports/qt5/fix-qalgorithms-vs2017.patch
-- Applying patch failed. This is expected if this patch was previously applied.

-- Applying patch C:/src/vcpkg/ports/qt5/fix-qalgorithms-vs2017.patch done
-- Applying patch C:/src/vcpkg/ports/qt5/fix-commandline-overrides.patch
-- Applying patch failed. This is expected if this patch was previously applied.

-- Applying patch C:/src/vcpkg/ports/qt5/fix-commandline-overrides.patch done
-- Configuring x64-windows-rel
-- Configuring x64-windows-rel done
-- Configuring x64-windows-dbg
-- Configuring x64-windows-dbg done
-- Package x64-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:43 (message):
    Command failed: C:/src/vcpkg/downloads/tools/jom/jom-1.1.2/jom.exe;/J;8
    Working Directory: C:/src/vcpkg/buildtrees/qt5/x64-windows-rel
    See logs for more information:
      C:\src\vcpkg\buildtrees\qt5\build-x64-windows-rel-out.log
      C:\src\vcpkg\buildtrees\qt5\build-x64-windows-rel-err.log

Call Stack (most recent call first):
  ports/qt5/install_qt.cmake:19 (vcpkg_execute_required_process)
  ports/qt5/portfile.cmake:67 (install_qt)
  scripts/ports.cmake:72 (include)

Error: Building package qt5:x64-windows failed with: BUILD_FAILED

Error Log:
Fatal Python error: Py_Initialize: unable to load the file system codec
ImportError: No module named 'encodings'

Current thread 0x00000428 (most recent call first):
Project ERROR: Building QtQml requires Python.
jom: C:\src\vcpkg\buildtrees\qt5\x64-windows-rel\Makefile [module-qtdeclarative-make_first] Error 3

The encodings module imports fine on the CLI, I'm not sure why it doesn't work when vcpkg tries to build.
python
>>> import encodings
>>> encodings.codecs

Windows Version: 7
Visual Studio: 2015
Python Version: 2.7.13

I did some digging and found that the install_qt.cmake script uses the vcpkg bundled python3. This would explain why my system python wasn't working as it wasn't being used. I tried manually using the python.exe  in downloads/tools/python and it imediately segfaults.
C:\src\vcpkg\downloads\tools\python>python.exe
Fatal Python error: Py_Initialize: unable to load the file system codec
ImportError: No module named 'encodings'

Current thread 0x00002690 (most recent call first):

Is there something wrong with the packaged python-3.4.3-embed-win32?

I updated to the most recent 3.5.x version and its now working.
https://www.python.org/ftp/python/3.5.4/python-3.5.4-embed-win32.zip

I'm getting this error with the latest master:
Fatal Python error: Py_Initialize: unable to load the file system codec
ImportError: No module named 'encodings'

Current thread 0x000008e4 (most recent call first):

Any hints on how to fix it?


Before onChangeTab method

I have gone through these following points

[x]   Check latest documentation: https://docs.nativebase.io/
[x]   Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[x]   Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[x]   Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[x]   For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[x]   For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description
Is there any method or workaround that allows me to handle touch events BEFORE tab changes? The 'onChangeTab' method fires AFTER the view changed to the selected tab. Thanks!

We're using this package as our base for tabs and it doesn't support the feature.
So it'd be best fork it and implement it yourself.


Consider merging .NET Framework Runtime and Builder Docker repos

We recently produced builder images for .NET Framework. Folks have been asking for those images for a long time, so that's good. We chose to add docker source assets for the builder images within this GitHub repo. Conversely, we chose to create a different Docker repo than the .NET Framework runtime repo for image assets. This is the same model as microsoft/aspnetcore-build.
For .NET Core, we chose a differently model, to share the same Docker repo and GitHub repo for both the runtime and builder/SDK images.
We decided to talk about this asymmetry in our approaches. Here are our take-aways:
Pros on using a single Docker repo for runtime + builder (SDK) assets:

Most of our samples use multi-stage-build, which then pull from a single repo. That's simpler.
Forces a single tag scheme.
Any difference in support (like chip or OS) between runtime and builder is obvious.
Builder and SDK together results in higher pull counts on a single repo, which pushes a given repo higher in the ranking in various Docker views where pull count is important. This isn't a vanity thing but a way of rising above the crowd around us.
For .NET Core, we think of the SDK as the "getting started" distro while we seem to think of the Runtime as the "getting started" distro for .NET Framework. This leads to potential discontinuity in naming across .NET Core and .NET Framework if we we were to have separate runtime and builder repos with only one of them getting the "good" short name.

Pros on separate Docker repos:

Smaller set of tags offered per repo, but the same set of tags to learn in aggregate.
More focused meaning of a Docker repo, meaning a smaller set of tags to search through for a given repo.

A major take-away is that the microsoft/dotnet repo has been highly successful. By pull counts, it is far and away the most popular of our repos, with almost 10x pull traffic relative to the next .NET Docker repo. We think that this is in part due to the whole (runtime and SDK) of .NET Core being available in one place. Effectively, we nailed the discoverability problem. We're now wondering if we should do the same thing with microsoft/dotnet-framework, that is make the SDK/builder images available there as well. We want to make .NET Docker use/adoption easier and more convenient. Will this help with that?
We'd like your feedback.

I have been thinking more about this. If we do this, the naive approach would be to add a new build tag as a direct translation of the microsoft/dotnet-framework-builder repo. The build tag would behave much like the sdk tag we use in the microsoft/dotnet repo. But then, why wouldn't we re-use the sdk tag instead? That seems accurate and would make it easier to talk about .NET Framework and .NET Core repos.
The only downside is that the current  microsoft/dotnet-framework-builder images don't contain the .NET Framework SDK (certainly not in its entirety). I'd say that any .NET Framework SDK tool that is relevant for use in Docker is fair game for being pulled in.

I like what PHP has done around your last point, by providing a Docker-specific way to consistently and easily install extensions -- check out the docker-php-ext-installsection here -- this keeps the base image smaller and (a benefit in my opinion) leads to explicitly stating those types of dependencies.

That makes sense. For our platform, we don't have the extensions in a package manager, like NuGet. So, I don't see a good path forward to enable the proposal.

The repos were merge with https://github.com/Microsoft/dotnet-framework-docker/pull/123.


Fix dependencies in calculators app

This should fix the error we get currently.
ERROR: Service 'calculators-app' depends on service 'router-live' which is undefined.

Should have been caught by CI!


Simplify command line output

Information

JIRA story QPPCT-874.

Checklist

[X] All JUnit tests pass (mvn clean verify).
[X] New unit tests written to cover new functionality.
[X] Added and updated JavaDocs for non-test classes and methods.
[X] No local design debt. Do you feel that something is "ugly" after your changes?
[X] Updated documentation (README.md, etc.) depending if the changes require it.

SonarQube analysis reported 1 issue

 1 major

Watch the comments in this conversation to review them.


Suggestion: "Go to Anywhere"

Just throwing up a suggestion in the air...
I find myself using Quick Open Scene, Quick Open Script, and Search Help all the time via shortcuts.
What about adding a "Go to Anywhere" dialog, which could be triggered via Ctrl+G. It would search from (at least):

Scripts
Scenes
Godot Help

I wonder what would be the benefit of mixing them all in one dialog, since they are wildly different stuff. There is no time lost in using them, and there would be if it was a single dialog because you would have to triage what you want (at least I would not use it if it was added).
I miss such a dialog for resources, though (and I wonder if a cache for all this stuff is accessible somewhere? Would speed up search/indexing tools in general, like Find in Files).

I wonder what would be the benefit of mixing them all in one dialog, since they are wildly different stuff. There is no time lost in using them, and there would be if it was a single dialog because you would have to triage what you want (at least I would not use it if it was added).

The benefit is that you need to remember one single shortcut to access any part of the project.
Would be cool if it would also find different options in the menus or even stuff inside scenes and scripts.

I wonder what would be the benefit of mixing them all in one dialog, since they are wildly different stuff.

I'm not always sure what file I'm going to have to change before I do it.
In most current code editors (e.g. VS Code, sublime) ctl+p allows you to fuzzy search your project.
Depending on your naming convention, this can be extremely powerful, especially in bigger projects. I'm assuming here this applies to Godot as well as it does to web-dev projects.
Translated to Godot, that'd mean that, wanting to change fictional BlastGuardian, searching e.g. "blgu" would find basically anything "res://BlastGuardian/*", showing the scene, maybe scripts and materials the thing is made of. Now you have an overview, from which you can pick which resource you actually need to edit.
You can then use the arrow keys, or add e.g. "mat" (so search for "blgumat"), to select the material file.
Also searching the docs would be a nice addition.

#28789 has added a Quick Open dialog which can be used to open any resource in the project (scene, script or any other file that inherits from Resource). I think this suffices for now, so this can probably be closed.
Merging the help search and list of files together may not be a good idea. It'd be easy to accidentally select the wrong result because a method in a built-in node has the same name as one of your files. This could also impact search performance negatively.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


Articles archive page

Articles archive CMS page.

Depends on https://github.com/City-of-Helsinki/react-helsinki-headless-cms/pull/37, but the change is already published in the new HCRC-package.

There are some questions that still needs answers:

Should the archive page be visible in the menu? It's not in the designs.
Should the results be filtered with a selected language? If so, it should be noted that some articles might not have version for every language.
What information is wanted to be shown in the large card and in the small card?
Should the large card be changed to a a small card after a search is triggered?

Also, some improvements could be done

[ ] add some tests
[ ] the page could be found by using the pageByTemplate -query. Now the URI is hard coded.
[ ] the page load (from CMS) could be done with an Apollo-component that could be exported from the HCRC. The HCRC -lib does not contain such a component yet.

Also fixed the article's too big hero image

the page could be found by using the pageByTemplate -query. Now the URI is hard coded.
this does not make much sense if we have have a hardcoded route rewrite for it (for localization reasons)


Revert "Prefix secrets with DBT_ENV_SECRET_ for test env vars"

Reverts dbt-labs/dbt-snowflake#995
This didn't work for the release workflows, which make stricter assumptions on environment variables. This is being reverted while we discuss a more thorough approach.

Since this is a workflow change, CI needs to run using the workflow on this branch. Here's the run: https://github.com/dbt-labs/dbt-snowflake/actions/runs/8916286219


Two small typos in Beit2 docs

1/ directory structure is now unilm/beit2 (not v2)
2/ there is a new url for mmsegmentations' dataset_prepare.md

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree

@twak  Thank you for the fix! I've merged the PR.


Need to do something with own provided certificate to get management tools working in secure mode?

Hi,
I installed the framework by compiling my own debian install files with maven. So I added the certificates into my my browser (MacOS keychain). After that I used the docker version of your management tools and at first sight it looked all good until I open one of the other functions (i.e.: Orchestrator Store, or Auth.) and after that all pages went blank.
It looks like the same issue as issue #5 the only difference between them is that I used the core system on a self installed debian machine instead of the docker one (read: own certificate).
Do I need to do something with the certificate to be able working with the management tools? Cause it looks like it can't use the ssl connection because it needs someone to approve that it  is unsafe?

For more information, header of the main request (http://localhost:3000/registry):

Hello!
In Mac OS as and Chrome, you need to to import the Certificate to your Keychain (what you did). Please make sure it is usable.
Chrome should open you a window, asking which certificate should it use.

Okay, this is not happening, but the certificate I added from /etc/arrowhead/system/sysop is also not green but red, as in not trusted.

So probably why it is not working, is because Chrome keeps throwing me a warning screen instead.

If the installation creates its own certificates, do I have to do something with them before I install them on my Mac?

No, you just have to install them. But as your screenshot shows, you installed the root arrowhead certificate and not the sysop.p12.
Please install the sysop.p12 certificate.
If it is not green, please select Always trust

I did install the sysop.p12 and then it installs the root version and also the sysop one. So now I have both.
I put the root on always Trust and then it does also trust the sysop cert:

But it still throws this warning message in Chrome on Swagger and at the management tools it stays blank.
I'll try to clear the cache and let you know what happend.

Okay I found the problem:

So I use the localhost name (deb-arrowhead.local) of my debian machine, and that is not in the certificate. So the certificate only has the ip address, "localhost" and "deb-arrowhead":

The error that Chrome gives is a bit misleading, because it's not about the common names. Chrome checks the Subject Alternative Names (SAN).

SAN must contain proper DNS or IP entry.

When DNS is used, it should be a resolvable FQDN name.
When an IP address is used, it should be explicitely specified as such within the SAN chain.

As found in this answer: https://serverfault.com/questions/880804/can-not-get-rid-of-neterr-cert-common-name-invalid-error-in-chrome-with-self
So now I entered the ip number and Chrome stops crying about it, and also used the ip number to start the management tools from docker. Works as it should be.
Thanks for looking into this!


more accurate sleep

I had problems with running the script in a docker container (milaq#16). It never reached the expected pulselength, was always too long.
But I could workaround the problem by use a more accurate sleep by dividing it.
The solution is not really nice but it works...

i can't test this right now.
does this introduce any weird side effects on low spec machines (e.g. rpi 1)?

I've tested with RPi3. With less performance we have less loop cycles so this should not matter...

(In theory)

Alright,
I'll merge this and wait a bit before tagging this in a new release.
Please report back ASAP if you discover any side effects.
Thanks for your endeavours :1st_place_medal:

Do you have a plan when you create  the new release?


genpy: 0.6.10-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository genpy to 0.6.10-1:

upstream repository: git@github.com:ros/genpy.git
release repository: https://github.com/ros-gbp/genpy-release.git
distro file: melodic/distribution.yaml
bloom version: 0.9.3
previous version for package: 0.6.9-1

genpy
* various code cleanup (#117 <https://github.com/ros/genpy/issues/117>)
* update logic for newer PyYAML output for dump() (#116 <https://github.com/ros/genpy/issues/116>)
* small optimization in dynamic.py (#109 <https://github.com/ros/genpy/issues/109>)
* use setuptools instead of distutils (#115 <https://github.com/ros/genpy/issues/115>)
* bump CMake version to avoid CMP0048 warning (#114 <https://github.com/ros/genpy/issues/114>)
* serialization: always set _x var for correct exception msg (#113 <https://github.com/ros/genpy/issues/113>)
* sort generated imports to make them reproducible (#111 <https://github.com/ros/genpy/issues/111>)
* make the generated "struct" constructs reproducible (#110 <https://github.com/ros/genpy/issues/110>)

Waiting for other Melodic releases...


Roundabout: duplicate instructions

Hello, there.
I noticed there are duplicate instructions when running through roundabouts, for instance:

Enter the roundabout and take the 2nd exit onto Avenue du Bon Curé on entering the roundabout;
Make a slight right onto Avenue du Bon Curé on exiting the roundabout.

These instructions essentially tell the same thing: when you're at the enter of a roundabout, you have no other choice than entering it; the useful information in this case is at which point leave it, which is already said on the entering point. Only one point, out of enter and exit, should generate instructions; for clarity, it should be the first, to emphasize the entering on the roundabout in case of a possibility to evade it just before the enter; the second instruction should be removed, as it is merely a duplicate of a part of the first one.
Note that I don't have much experience with real world examples, so there could be cases justifying this duplication for clarity.
Regards.

You’re right that these two instructions are a bit redundant. In real-time turn-by-turn navigation, it also means that there isn’t enough time to say the exit instruction before the exit needs to be taken.
The Mapbox Directions API does have some heuristics behind the scenes that make this particular scenario easier on the ears: when roundabout_exits=true, the entrance and exit instructions are joined together. That heuristic isn’t implemented in the OSRM demo site, which is intended to reflect OSRM output in rawer form.
OSRM Text Instructions, likewise, is intended to be fairly lightweight so that clients can implement their own heuristics as needed. I’m closing this issue because #15 would need to be implemented before OSRMTI could feasibly do that for the client.


fix: revert #8 to prevent infinite loops

Oh just noticed this doesn't have any workflow setup @getlarge

@mcollina Nice to see you :) BTW the test will be added with the error handler we suggested (using a custom function in option)


Bump dependencies to support Apple M* chips

Due to issues with the Argon2 version not being built for arm64 this does not work on Apple machines.
Are we able to bump all the deps?
I was able to get it working with the following package.json update and no other changes:
  "dependencies": {
    "argon2": "^0.40",
    "chalk": "^4.1.2",
    "cli-spinners": "^3.1.0",
    "ethereumjs-wallet": "^1.0.2",
    "keccak": "^3.0.2",
    "log-update": "^6.0.0",
    "nunjucks": "^3.2.3",
    "rlp": "^3.0.0",
    "secp256k1": "^5.0.0",
    "secp256r1": "^0.0.3",
    "toml": "^3.0.0",
    "tweetnacl": "^1.0.3",
    "yargs": "^17.3.1"
  },
  "devDependencies": {
    "@types/jest": "^29.5.12",
    "@types/keccak": "^3.0.1",
    "@types/node": "^20.14.12",
    "@types/nunjucks": "^3.2.1",
    "@types/secp256k1": "^4.0.3",
    "@types/tmp": "^0.2.0",
    "@types/yargs": "^17.0.8",
    "@typescript-eslint/eslint-plugin": "^7.17.0",
    "@typescript-eslint/parser": "^7.17.0",
    "eslint": "^8.56.0",
    "eslint-config-prettier": "^9.1.0",
    "eslint-plugin-import": "^2.25.0",
    "eslint-plugin-jsdoc": "^48.8.3",
    "eslint-plugin-prefer-arrow": "^1.2.1",
    "husky": "^9.1.1",
    "jest": "^29.7.0",
    "lint-staged": "^15.2.7",
    "ts-jest": "^29.2.3",
    "typescript": "^5.5.4"
  },

NB: The chalk and eslint are the only packages not at the latest version.

Hi @mdochdev could you confirm this works on amd64 and arm64? If so we can bump up and merge and I'll cut a fresh release

Confirmed it works on arm64

fixed in v 0.2.17


Revert "Bump jakarta.enterprise:jakarta.enterprise.cdi-api from 4.0.1 to 4.1.0"

Reverts liquibase/liquibase#5810

Closing this PR because the build issue was due to the changes added in #5941 were not merged in #5810.


Publish own credential types

Publish EPCISEventCredential and EPICSDocumentCredential types in the GS1 VC-Data-Model
GS1 Issue: https://github.com/gs1/VC-Data-Model/issues/9

Now in PR https://github.com/gs1/VC-Data-Model/pull/10

Closed with Version 1.1.0 https://github.com/COPPA-CCP/epcis-signing/releases/tag/v1.1.0 in commit https://github.com/COPPA-CCP/epcis-signing/commit/cf96d6f26cfac66503d87e8faaa40d5f2835c8c7


inclavared: sanity check the validation of request from shelter

Fixes: #985
Signed-off-by: zhiminghufighting<EMAIL_ADDRESS>

test result here:

Verify log here:

Local test here:


[UI] New performance request headers are taking mouse focus

Description
When the Meshery UI /performance page loads, the "Request Body" field automatically receives the mouse's focus.
Expected Behavior
No field should receive focus.
Screenshots

#1151 will fix this, right @dhruv0000 ?

No. Its a quick fix. Let me include it in #1151.

Fixed in #1151


fix: update build tasks, package.json and changelog

PR Checklist

[ ] Unit Tests have been added for new changes
[ ] API tests have been updated if applicable
[ ] All commented code has been removed
[ ] If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. open-amt-cloud-toolkit/repo#365 )

:tada: This PR is included in version 2.13.2 :tada:
The release is available on:

GitHub release
v2.13.2

Your semantic-release bot :package::rocket:


Specify maximum number of messages

I want to fetch some fix number of message in a time interval.
Eg. I want 5 message in every  10 seconds.
How can I do this?

+1

You can't do that in KafkaJS itself. Fetching from Kafka happens in numbers of bytes, not messages. So there's no way we can ask the broker for X number of messages.
In order to support this we would need to start keeping an internal buffer of records returned from fetch requests and then only feeding the userland code max.poll.records at a time from there.

KIP-41
Initial Java implementation

Even after having my consumer setup like below
` const app = await NestFactory.createMicroservice(AppModule, {
transport: Transport.KAFKA,
options: {

  client: {
    brokers: KAFKA_BROKER ? KAFKA_BROKER.split(',') : [],
  },
  consumer: {
      groupId: KAFKA_GROUP_ID,
      minBytes: 5242880,
      maxBytes: 7372800,
      maxBytesPerPartition: 153600,
      maxWaitTimeInMs: 5000
  },
  subscribe: {
    fromBeginning: false
  }
}

});`
and my event handler like below
    @MessagePattern('TOPIC_NAME')   async dataFromTopic(@Payload() message): Promise<any> {     let data = await new Promise((resolve, reject) => {       setTimeout(()=>{         console.log('Processing delay of 250ms')         resolve({})       }, 250)     })     console.log(message['topic'], Object.keys(message))     return data   }
Not able to consume message is bulk.
Doing anything wrong here?

@vikashhrs Please don't derail this issue with unrelated comments. Your question is better suited for the NestJS support channels rather than KafkaJS.

You can process the first 5 message of the batch, then setOffset  5 time to move the batch forward.

I've made a package for a similar use case, you may find it useful.


Release 0.11 forwardport (things on release branch that should go to main)

What

picked from #4347

Changelog, link fixes, doc fixes, release script fixes etc.
This is a collection of cherry picks from the release branch, some of them squashed and reordered for a more comprehensive commit log
[Draft until the release is actually through.]
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[ ] I have tested app.rerun.io (if applicable)
[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

let's go with the release branch direclty - did so on the last few releases


Implement the embedded-hal Read trait for the RNG peripheral

Simple peripheral, equally simple implementation. Did not include an example but did verify that it works as expected locally.

Implementation looks fine, but can we figure out if the RNG has actually been enabled? This document talks about what's required for the RNG to work, and given that we are using the second stage boot loader it will work but in the future that might change. We don't have to implement the clock enable in this PR, but maybe as a bare minimum we can add check to make sure it has?

Code looks good to me. But Scott's point about the pre-conditions is very good. I'd probably have totally missed that.
The scary thing is that apparently when the pre-conditions are not met it will produce pseudo-random numbers so it is not obvious to the user. A PRNG might probably be good enough for many things but for some things it's not
Not sure if we should add a runtime-check and panic - as said maybe some users might be totally fine with a PRNG.
So, the very least would be to document this behavior (i.e. TRNG vs PRNG). And/or maybe have an optional constructor that checks it and panics?
Also, is this worth to have an example for? The API is simple enough so most people will figure out how to use the RNG

I'm sort of on the fence with regards to how we should handle this. My gut says that we should avoid runtime checks whenever possible, but I'm happy to hear any refutations to this.
Generally speaking, I'm against trying to hold the user's hand too much. If somebody is not using the bootloader from ESP-IDF I assume that they know well enough to properly initialize the device. I'm not sure if this is a reasonable assumption or not, though.
Given that we're still in the early stages of the HAL, and that there are already technically incorrect implementations present in the repo (eg. the Xtensa delays) I'm not sure how big of a deal we need to make of this. I think adding a comment stating the per-conditions is probably adequate for the time being, but please let me know how you both feel about this.

I personally would be totally fine with a reasonable warning (with a reference to the TRM) in the comments and I agree that a bare-metal HAL is usually not a "batteries-included" thing. Also, since this is not named TRng hopefully people will read the docs to find out if it's TRng or PRng.
Maybe it's also a good occasion to think about the general philosophy of the HAL (i.e. should it be as much "batteries-included" as possible or not). While there are a lot of wild assumptions currently (e.g. regarding the various clock speeds) which we need to address there are also other things more similar to this (e.g. is synchronization something that should be taken care of at the call-site (with some hints in the docs where needed) or not)
As said, I personally think a bare-metal HAL could assume more care taken by the user than e.g. the ESP-IDF-HAL. Which makes we wonder if the wording no-std and std isn't a bit confusing since people could do no-std on top of ESP_IDF ... but that's a different story certainly

I've added documentation for this driver, should be adequate I believe.
@bjoernQ I think you're right and that discussion needs to be had. I've created a discussion where we can talk about such things.


Https connection does not show up.

I have tried the above tutorial to create an ingress and apply TLS on it. It is not working as expected and as shown in the last step of this tutorial.
My cluster is created in "australiaeast" resource group. Please confirm is this documentation is updated and has it worked for anybody in this region.

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

ID: ada58160-dc50-b977-d3bc-65f92406e16d
Version Independent ID: 5c596e04-fddb-effe-3b72-575f4df42d4e
Content: Configure ingress with Azure Kubernetes Service (AKS) cluster
Content Source: articles/aks/ingress.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the feedback! We are currently investigating and will update you shortly.

Can you clarify by not working as expected? What error are you seeing?

A secure encrypted connection with a certificate issues by Let's encrypt did not show up, like the way its mentioned in the tutorial on that day. But today (after 2 days of my deployment) I just checked app
'https://aks-helm-ingress.australiaeast.cloudapp.azure.com/' it is working now.
I don't know why?

Thanks @guptaisha5484. I tried to repo the issue but did not see any delay. If you like you can try and reproduce the issue and we can dig in deeper. I will close this for now since it is working as expected but just let me know if you want to continue to debug and we can reopen.
CC @iainfoulds


[Feature]: Number card - slider with buttons

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Is your feature request related to a problem?
I like slider, but sometimes I need to change value by a notch. It's hard to point exact value with slider. Ok, I could use buttons, but then if I want to change by a significant value then I need to push that button many times.
Describe the solution you'd like
I would like to have input number slider with +/- buttons on its sides. Like for fine tuning.
Describe alternatives you've considered
Tried using both, one slider, and one buttons card for the same entity, but it doesn't suits my needs.
Additional context
No response

First of all thank you for the component set - they are awesome.
I would appretiate the same as @JohnyMielony:  +/- buttons (large enough to be simply pressed also on mobile devices).
If there would be also editable text field where I'd be able to put number directly - (i.e. the component would contain all 3: slider, +/- buttons and editable text field), it would be great.
All 3 parts could be optional based on the configuration.
Some variants for inspiration:


Geofencing Support

This isn't exactly an issue but I was wondering if there would be Geofencing support for the MAXM10S modules soon? Or if that is even in the pipeline, I know the data sheet says a code change is required for it to be supported. Thanks

I'll check: I'm not aware of there being a FW version for MAXM10S that supports geofencing yet.  Were you told which version it would appear in?

Nope - wasn't told by anyone but it just says "Code change required" in the data sheet. So I was hoping with any luck support has been added by now, its not critical for me but it would be really nice to have. Thanks for checking

I've checked internally and it seems that the feedback we get from customers is that they would prefer to do the geofencing on the MCU-side rather than have it done in the GNSS chip, so I'm going to have a look at what we might do in ubxlib to make that easy.
I've tagged this is a feature request and will update when we have something; might be a month or two, can't be certain just yet.

I've checked internally and it seems that the feedback we get from customers is that they would prefer to do the geofencing on the MCU-side rather than have it done in the GNSS chip, so I'm going to have a look at what we might do in ubxlib to make that easy.

Ok, so I'm lurking here. I think the value of doing it within the receiver comes down to low-power or more autonomous behaviour, reducing the number of MCU required in a system, or that need to be powered/involved at a given instant.
I don't think having the GEOFENCE functionality as it was is overly burdensome from a receiver perspective. I built something very similar for prior generations.
Yes, it's a bit limited and crude, but if customers want to define complex bounding polygons that's really an application side decision. I'm not sure why them complaining it didn't suit their specific needs means it needs to be deprecated entirely for every one.
Now even with complex bounding polygons you can compute a circle that contains them, this can be very helpful for sieving large numbers of fences, can be done with integers, and without square roots, so can be very computationally efficient. ie course filtering. You can then check a decimated list of more complex fences. Perhaps caching a list you're within proximity of if they are geographically dispersed, and moving at less than Mach 3. I was dropping circles over traffic intersections I was interested in knowing when a vehicle traversed..
The API looks good, will review as it develops.

We'd be interested in any comments you may have, if you have time of course. The feature is in active development, so subject to wild changes depending on how things go with the implementation, no promises and all that, but your feedback would be very much valued.

Thoughts here, make sure it scales well. That dealing with very large lists is considered from the outset. People are going to want/expect to dump the whole task on you, and not actively manage and cull the lists themselves.

I don't think having the GEOFENCE functionality as it was is overly burdensome from a receiver perspective. I built something very similar for prior generations.

Understood: it surprised me also as I thought this was a neat feature but it was a product management decision.  My guess [I'm not close to this, I'm actually in the cellular side of the business] is that resources in the chip are tight.

make sure it scales well

Also understood: the lists will scale provided the heap implementation of the platform is good.  That or we move to fixed arrays and the overhead/compile-time-limitations they bring.  Since I've not yet come across a problem I could blame on heap fragmentation on the platforms we support, I think that pure linked lists should be good enough.
Anyway, thanks for the feedback, will update the preview branch in a moment with the latest.

Yes I think some other people pointed out exactly why it would be nice to run on the module - it's low power and you wouldn't have to poll the gps constantly. That being said I would prefer a concave/convex polygon that could be loaded into the module and then alerted on changes but also distance from the nearest point on the polygon. So that's a big ask if we are extremely research constrained - but I have written code to do this on the MCU that might be useful? I'll take a look at the new branch.

I would prefer a concave/convex polygon

It's possible this is the other issue: every application has its own needs and so the relatively limited facilities a module can provide end up being unused in most cases.
Anyway, your feedback would be appreciated.

One thing: the implementation I have in mind is currently flat; if you have a simple way of taking the curvature of the earth into account when calculating the intersection of two lines then that would be interesting.

One thing: the implementation I have in mind is currently flat

That would be my expectation, that you're perhaps dealing with a few hundred meters, rather than multiple km, but I suppose if boundary is of a large field, airfield, test-range or military-industrial complex, these could get quite large in terms of boundaries.
Close-in, I'd opt for flat/simple model.
I think one of the scalability tricks here is to decimate what you're dealing with, ie the ability to quickly discard geofences that you're clearly way outside, and then drill down in the math and details for those candidates which are more problematic.
The list can also be diminished by understanding how fast the vehicle, or whatever, is moving, and lists of candidates being refreshed periodically to reflect what you might encounter during those intervals, rather than testing every thing, every time, and the receiver can teleport.
Perhaps the FAA, or similar national/international agencies, have some keep-out / no-fly databases one might use to test/validate usability expectations?

The other consideration is how tightly does any of this need to resolve? With large keep-out zones the idea is to keep you away from a site, not necessarily allow for you to hug the perimeter and tip-toe between in/out of violating the site boundaries.

Here's some of the stuff I used to implement my MCU solution.
https://raw.githubusercontent.com/chrberger/WGS84toCartesian/master/WGS84toCartesian.hpp
And I also used //https://github.com/chrberger/geofence/tree/master
I made some tweaks to these but nothing crazy and pretty application specific.
I think some really good points have come up so it sounds like we would need to define some different use cases and then allow those to be set.

Thanks both: having browsed random things on the internet for less than 10 minutes (:-)) I'm going to suggest we stick with the flat.
The issue with WGS84toCartesign, though simple, is that it would bring in floating point types, which we have so far not allowed as they cause clib sizes to balloon and, in order to keep us fleet-on-our-feet, we need to be able to "compile and run/test once", which any largish compile-time options would prevent.  Maybe, though we could construct the calculation of the intersection such that WGS84toCartesign could be plugged-in?
The question then becomes, how big can a fence get before it messes up with "flat".  I couldn't find a definitive answer to this but it seems like it is in kilometres, rather than metres: @michaelboeding, you plainly felt a need to handle the curvature, what kind of scale were you dealing with?
@cturvey: had anticipated that there are short-cuts to be made in the calculation to drop pointless maths, hadn't thought about keep-out zones though.  Can definitely make use of speed.

The arc-minute, nautical mile, knot stuff relates to the 1852 - 1854m type distances.
For consideration:
Range-Safety
Track-Limits
Property-Boundary
Political-Boundary
No-Fly / Keep-Out Zones
One of your large customers is DJI, they probably lamented the current GEOFENCE implementation to be inadequate for their use cases. Not familiar exactly with their processes, but imagine pre-flight check/validation, and in-flight enforcement.

Thanks both: having browsed random things on the internet for less than 10 minutes (:-)) I'm going to suggest we stick with the flat.
The issue with WGS84toCartesign, though simple, is that it would bring in floating point types, which we have so far not allowed as they cause clib sizes to balloon and, in order to keep us fleet-on-our-feet, we need to be able to "compile and run/test once", which any largish compile-time options would prevent. Maybe, though we could construct the calculation of the intersection such that WGS84toCartesign could be plugged-in?
The question then becomes, how big can a fence get before it messes up with "flat". I couldn't find a definitive answer to this but it seems like it is in kilometres, rather than metres: @michaelboeding, you plainly felt a need to handle the curvature, what kind of scale were you dealing with?
@cturvey: had anticipated that there are short-cuts to be made in the calculation to drop pointless maths, hadn't thought about keep-out zones though. Can definitely make use of speed.

My scale was variable - user defined. But the main reason I went with that implementation is I have written code before for 3D modeling from drone images and part of the calculation includes that type of conversion for a few projections and other things - so I just wrote the exact math into it for precision. I wasn't really resource constrained for my application.

Understood: I've modified the code in the preview branch to split-out the function that is currently "flat" so that an application which has the resources to do so can replace it at link-time with a function which takes the curvature of the earth into account.  I've also explained in hopefully relevant places that the default implementation is only good for fences around the 1 km range.
The other API aspect that I am unsure of is whether I need to include a "confidence" factor or not.  My current plan is to rely on the horizontal accuracy estimate, as reported by the GNSS device for the fix, and that alone: do you I think I need to allow some sort of multiplier on top of that?  Seems a but odd having an accuracy estimate and then just randomly multiplying it by something..  Thoughts?

The geofencing API is now implemented and pushed to master, c169912d1055b55ffa2eecd4f223b973d73c14fa being the last relevant commit.
An example of how to use it with GNSS is included but it can equally be used with cellular (position established through the u-blox CellLocate service) and u-ConnectExpress Wi-Fi (location established through Google, Skyhook or Here).  You can also get position any which way you like and throw it at a Geofence with uGeofenceTest().
An overview of the implementation can be found at the top of u_geofence.c.
Gonna close this now, please re-open, or open a new issue, if you have additional comments/suggestions.

Although this may not be the best place to put this, since it would be useful by itself not just with geofencing but the ability to take GPS coordinates and accelerometer readings to create a more accurate fix over time using a Kaman filter could be very useful. Especially for geofencing but as a separate component also for hardware that has access to accelerometer data. It would need to be able to ingest a standard format of data from the accelerometer.
https://robotics.stackexchange.com/questions/11178/kalman-filter-gps-imu

I will add this as a separate feature request.


Add Profile

What type of PR is this? (check all applicable)

[x] 🚀 Added Name
[ ] ✨ Feature
[ ] ✅ Joined Community
[ ] 🌟 ed the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
Added me to profiles that use Github Actions.
Add Link of GitHub Profile
https://github.com/keshavsingh4522

please review my profile


Comparison with original MATLAB scripts from Chartrand

Has any testing been done to compare the outputs of TVRegDiff with Chartrand's original MATLAB code?
I see he has a couple of demo's included in his code:

demo_large.m
demo_small.m

I tried running tvregdiff with the same parameters as demo_small.m but couldn't get exactly the same results.  Maybe I am doing something wrong.

Here is my test script:
noisy_abs_data = np.loadtxt('smalldemodata.csv')  # data from smalldemodata.mat
n_iters = 1
        alph = 0.2
        scale = 'small'
        ep = 1e-6
        dx =  0.01
        u = TVRegDiff(noisy_abs_data, n_iters, alph, u0=None, scale=scale,
                      ep=ep, dx=dx, plotflag=False, diagflag=True)

Could be a problem with my test setup.  I'm getting the "WARNING:root:WARNING - convergence to tolerance not achieved!" warning on every iteration.
I tried varying the number of iterations.  The results seem to be heading towards the values I got from running Chartrand's MATLAB script.

So I'm thinking that maybe I need to adjust one of the parameters to make this converge.  Any advice on what to try next?

This is from using his 'noisy abs data' (from demo_small.m) which looks like this:

I have the same issue. In fact, it will never converge, no matter how large you make the n_iters variable. You can make it converge by modifying the maxit variable in the tvregdiff.py file. However, this makes the routine extremely slow, and I had to increase the number of iterations to more than 5000 in order to get rid of all the WARNING:root:WARNING - convergence to tolerance not achieved! errors.

Not sure what to do.  I don't have time right now but at some point it would be good to work through the demo example in both MATLAB and Python and figure out where they diverge and why maybe?

I could get good results for small_dataset by disabling the preconditioner matrix P. You can also have a try. I suspect that the difference between Python and Matlab code is due to the difference between sparse.linalg.cg and Matlab pcg, although there are supposed to be equivalent.

I made some changes to address this. Two things, mainly:

added a flag to disable the preconditioner if one wishes to (it was the cause of many of those 'convergence not achieved' error messages, and did nothing good)
added a new mode of weighing the second derivative in the functional. In Rick's original script and paper it's |u'|, which results in a non-linear operator that is then approximated iteratively. However I see no reason why it can't be (u')^2, which in fact gives a linear operator and works better in some cases (specifically the ones where the derivative we're looking for does not have any steps). So now that's an option too, diffkernel='sq'.

I've also changed the testing a bit, now the data is generated on the fly and new functions to test can be added. The tolerances achievable are pretty low though. I agree that something must be different between Scipy and Matlab, because clearly the results aren't always exactly the same.

Thanks for looking at this.
B.t.w. I haven't look at it but this recent paper from University of Washington might be worth looking at:
Numerical differentiation of noisy data: A unifying multi-objective optimization framework
Floris van Breugel, J. Nathan Kutz, Bingni W. Brunton
https://arxiv.org/abs/2009.01911
It references the Chartrand algorithm and includes a Python library (https://github.com/florisvb/PyNumDiff) but not sure if it includes an implementation.


Update typos & minor edits.

Thanks for the PR! Received your email too, will follow up once merged.

Glad to be of service!


az storage blob upload-batch truncates blob URIs after v2.34.1

Describe the bug
Command Name
az storage blob upload-batch
To Reproduce:
On v2.31.0:
az storage blob upload-batch --destination extensions --source d:\temp\1 --destination-path sometest/blah --account-name someaccount --account-key "somekey"
Responds with
[
  {
    "Blob": "https://someaccount.blob.core.windows.net/extensions/sometest/blah/filename",
    "Last Modified": "2022-03-18T20:05:08+00:00",
    "Type": null,
    "eTag": "\"0x8DA091A9A03E9CB\""
  },
  {
    "Blob": "https://someaccount.blob.core.windows.net/extensions/sometest/blah/anotherfilename",
    "Last Modified": "2022-03-18T20:05:08+00:00",
    "Type": null,
    "eTag": "\"0x8DA091A9A0AED96\""
  }
]

After upgrading to v2.34.1:
az storage blob upload-batch --destination extensions --source d:\temp\1 --destination-path sometest/blah --account-name someaccount --account-key "somekey"
[
  {
    "Blob": "https://someaccount.blob.core.windows.net/",
    "Last Modified": "2022-03-18T20:15:00+00:00",
    "Type": null,
    "eTag": "\"0x8DA091BFB2C42F2\""
  },
  {
    "Blob": "https://someaccount.blob.core.windows.net/",
    "Last Modified": "2022-03-18T20:15:00+00:00",
    "Type": null,
    "eTag": "\"0x8DA091BFB3430F5\""
  }
]

As you can see, file path is gone.
Expected Behavior
Blob property contains full URI to the newly uploaded file.
Our automation is completely broken because of this change.
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.34.1

Extensions:
aks-preview 0.5.52
azure-devops 0.22.0
front-door 1.0.16
log-analytics 0.2.1
resource-graph 2.1.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

Looks like this change broke it.
@calvinhzy

@evelyn-ys @calvinhzy please take a look


Installation on Debian

Hi all,
I'm trying to start a clone of instant.io in my debian server but I got an erreur when I try to run it.

stylus css/main.styl -o static/ -c

/usr/bin/env: node: No such file or directory
npm ERR<EMAIL_ADDRESS>build-css: stylus css/main.styl -o static/ -c
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build-css script.
npm ERR! This is most likely a problem with the instant.io package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     stylus css/main.styl -o static/ -c
npm ERR! You can get their info via:
npm ERR!     npm owner ls instant.io
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.14.32-xxxx-grs-ipv6-64-vps
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "run" "build-css"
npm ERR! cwd /home/instant.io
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
What is stylus ?
Merci ;)

What were the commands you did to start it? Did you run npm run build before npm start to compile all the css and javascript files?

See http://stackoverflow.com/a/18130296/292185
Duplicate of https://github.com/feross/instant.io/issues/112

Yes it work 👍
Thanks everyone


Expose testing api for use by external plugins

See original issue on GitLab
In GitLab by [Gitlab user @phildawson] on Jan 7, 2019, 16:46
Background
In the future, we are planning on reducing the number of plugins contained in BuildStream Core.
We are planning on reducing the number of plugins contained in BuildStream Core. As we migrate plugins away from core, we want to maintain at least their current levels of test coverage. Currently, external plug-ins are maintaining their own copies of BuildStream's testing utilities [1,2]. This unnecessarily increases the maintenance effort associated with external plug-ins.
In order to make testing of external plug-ins easier and keep their maintenance overhead manageable, we should expose the testing utilities required to test plug-ins as a stable public api. This was originally discussed here.
This will also make it easier for users who wish to create their own plug-ins.
[1] https://gitlab.com/BuildStream/bst-external/tree/master/tests
[2] https://gitlab.com/BuildStream/bst-plugins-container/tree/master/tests
Task description
The starting point for this api is testutils/runcli.py and testutils/integration.py test fixture.

[ ] Expose testing api for use by external plugins

Acceptance Criteria

In GitLab by [Gitlab user @phildawson] on Jan 16, 2019, 09:55
I've created the branch phil/plugin-testing-api showing what I think is the starting point for a testing API.
As it stands I've exposed the utilities required to test the existing bst-external plug-ins. In the future, we will almost certainly want to make more utilities available, but in my view it's better to wait for the demand.

In GitLab by [Gitlab user @phildawson] on Jan 16, 2019, 13:16
mentioned in merge request !1075

In GitLab by [Gitlab user @tlater] on Jan 18, 2019, 17:36
Related to #281

In GitLab by [Gitlab user @phildawson] on Feb 8, 2019, 16:28
closed via merge request !1075

In GitLab by [Gitlab user @phildawson] on Feb 8, 2019, 16:28
mentioned in commit 77ce0c1607d060eda098779228d5b0ab62ec04ef


Struct binded function's stacktrace contains double package name.

See the following sample.
error, message: failed to get last accessed time: No such session in progress
at ballerina.net.http:ballerina.net.http:Session.getLastAccessedTime(:0)
at .:sample2.new5(httpSessionTest.bal:382)

We no longer have struct bound functions


README: Fix Header Formatting

The README lacked spaces after the '#'s in several spots, causing Github
to improperly render them. This commit fixes the problem by adding them
in.
Signed-off-by: Mark Stenglein<EMAIL_ADDRESS>

Duplicate of #92.


Improve error catching

Pull Request
Description

improve error catching
unique gsp ids in fake

How Has This Been Tested?
normal unittest

[ ] Yes

Checklist:

[ ] My code follows OCF's coding style guidelines
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my code and corrected any misspellings

Codecov Report

Merging #607 (d951028) into main (b901dcd) will decrease coverage by 0.08%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main     #607      +/-   ##
==========================================
- Coverage   93.36%   93.27%   -0.09%
==========================================
  Files          45       45
  Lines        2982     2990       +8
==========================================
+ Hits         2784     2789       +5
- Misses        198      201       +3

Impacted Files
Coverage Δ

...ng_dataset/data_sources/metadata/metadata_model.py
94.36% <70.00%> (-4.05%)
:arrow_down:

nowcasting_dataset/data_sources/fake/batch.py
87.17% <100.00%> (ø)

nowcasting_dataset/dataset/batch.py
98.47% <100.00%> (ø)

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 b901dcd...d951028. Read the comment docs.


Nintendo DSi Browser

I know this is kinda out of the scope of this project, but if anyone else wants to try, you should know
Browservice doesn't really work on the Nintendo DSi
Video of it not really working
Log for anyone who cares:
./browservice-v<IP_ADDRESS>-x86_64.AppImage --vice-opt-http-listen-addr=<IP_ADDRESS>:8080
INFO @ src/main.cpp:153 -- Loading vice plugin retrojsvice.so
INFO @ src/main.cpp:160 -- Initializing vice plugin retrojsvice.so
INFO @ retrojsvice.so src/context.cpp:251 -- Creating retrojsvice plugin context
INFO @ src/xvfb.cpp:62 -- Starting Xvfb X server as child process
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
INFO @ src/xvfb.cpp:133 -- Xvfb X server :1 successfully started
[1213/130447.550964:ERROR:gl_surface_glx.cc(431)] glxQueryVersion failed
[1213/130447.552142:ERROR:gl_initializer_linux_x11.cc(166)] GLSurfaceGLX::InitializeOneOff failed.
[1213/130447.588182:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[1213/130447.726435:WARNING:vaapi_wrapper.cc(586)] VAAPI video acceleration not available for swiftshader
[1213/130447.728720:ERROR:gpu_init.cc(453)] Passthrough is not supported, GL is swiftshader, ANGLE is
INFO @ retrojsvice.so src/context.cpp:301 -- Starting plugin
INFO @ retrojsvice.so src/http.cpp:620 -- Starting HTTP server (listen address: <IP_ADDRESS>:8080)
INFO @ retrojsvice.so src/http.cpp:628 -- HTTP server started successfully
INFO @ retrojsvice.so src/window_manager.cpp:317 -- New window requested by user
INFO @ src/server.cpp:50 -- Got request for new window from vice plugin
INFO @ src/window.cpp:460 -- Creating window 1
INFO @ retrojsvice.so src/window_manager.cpp:328 -- Creating window 1
INFO @ src/window.cpp:147 -- CEF browser for window 1 created
INFO @ src/bookmarks.cpp:114 -- Bookmark file '/home/playerd_uwu/.browservice/bookmarks' does not exist, using empty set of bookmarks
INFO @ retrojsvice.so src/window.cpp:480 -- Closing window 1 due to inactivity timeout
INFO @ src/window.cpp:504 -- Closing window 1
INFO @ src/window.cpp:189 -- Cleanup of CEF browser for window 1 complete
^CINFO @ src/main.cpp:125 -- Got signal 2, initiating shutdown
INFO @ src/server.cpp:27 -- Shutting down server
INFO @ retrojsvice.so src/context.cpp:336 -- Shutting down plugin
INFO @ retrojsvice.so src/http.cpp:542 -- Shutting down HTTP server
INFO @ retrojsvice.so src/http.cpp:585 -- HTTP server shutdown complete
INFO @ retrojsvice.so src/task_queue.cpp:114 -- Shutting down task queue
INFO @ retrojsvice.so src/task_queue.cpp:94 -- Task queue shutdown complete
INFO @ retrojsvice.so src/context.cpp:632 -- Plugin shutdown complete
INFO @ src/server.cpp:267 -- Server shutdown complete
INFO @ src/main.cpp:26 -- Quitting CEF message loop
INFO @ retrojsvice.so src/context.cpp:275 -- Destroying retrojsvice plugin context
INFO @ src/xvfb.cpp:159 -- Sending SIGTERM to the Xvfb X server child process to shut it down
INFO @ src/xvfb.cpp:164 -- Waiting for Xvfb child process to shut down
INFO @ src/xvfb.cpp:167 -- Successfully shut down Xvfb X server
uname -a of my machine:
Linux playerd-uwu 5.4.163-1-MANJARO #1 SMP PREEMPT Wed Dec 1 14:47:09 UTC 2021 x86_64 GNU/Linux
lspci -v of my machine:
00:00.0 RAM memory: NVIDIA Corporation MCP65 Memory Controller (rev a3)
	Subsystem: Gigabyte Technology Co., Ltd Device 5001
	Flags: bus master, 66MHz, fast devsel, latency 0, NUMA node 0
	Capabilities:
00:01.0 ISA bridge: NVIDIA Corporation MCP65 LPC Bridge (rev a3)
Subsystem: Gigabyte Technology Co., Ltd Device 0c11
Flags: bus master, 66MHz, fast devsel, latency 0, NUMA node 0
00:01.1 SMBus: NVIDIA Corporation MCP65 SMBus (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 0c11
Flags: 66MHz, fast devsel, IRQ 11, NUMA node 0
I/O ports at fc00 [size=64]
I/O ports at 1c00 [size=64]
I/O ports at 1c40 [size=64]
Capabilities:
Kernel driver in use: nForce2_smbus
Kernel modules: i2c_nforce2
00:01.2 RAM memory: NVIDIA Corporation MCP65 Memory Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 0c11
Flags: 66MHz, fast devsel, NUMA node 0
00:02.0 USB controller: NVIDIA Corporation MCP65 USB 1.1 OHCI Controller (rev a3) (prog-if 10 [OHCI])
Subsystem: Gigabyte Technology Co., Ltd Device 5004
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23, NUMA node 0
Memory at fe02f000 (32-bit, non-prefetchable) [size=4K]
Capabilities:
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci
00:02.1 USB controller: NVIDIA Corporation MCP65 USB 2.0 EHCI Controller (rev a3) (prog-if 20 [EHCI])
Subsystem: Gigabyte Technology Co., Ltd Device 5004
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22, NUMA node 0
Memory at fe02e000 (32-bit, non-prefetchable) [size=256]
Capabilities:
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:06.0 Ethernet controller: NVIDIA Corporation MCP65 Ethernet (rev a3)
Subsystem: Gigabyte Technology Co., Ltd Device e000
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 25, NUMA node 0
Memory at fe02d000 (32-bit, non-prefetchable) [size=4K]
I/O ports at f000 [size=8]
Capabilities:
Kernel driver in use: forcedeth
Kernel modules: forcedeth
00:08.0 PCI bridge: NVIDIA Corporation MCP65 PCI bridge (rev a1) (prog-if 01 [Subtractive decode])
Flags: bus master, 66MHz, fast devsel, latency 0, NUMA node 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000c000-0000cfff [size=4K]
Memory behind bridge: fde00000-fdefffff [size=1M]
Prefetchable memory behind bridge: fdf00000-fdffffff [size=1M]
Capabilities:
00:09.0 IDE interface: NVIDIA Corporation MCP65 IDE (rev a1) (prog-if 8a [ISA Compatibility mode controller, supports both channels switched to PCI native mode, supports bus mastering])
Subsystem: Gigabyte Technology Co., Ltd Device 5002
Flags: bus master, 66MHz, fast devsel, latency 0, NUMA node 0
Memory at 000001f0 (32-bit, non-prefetchable) [virtual] [size=8]
Memory at 000003f0 (type 3, non-prefetchable) [virtual]
Memory at 00000170 (32-bit, non-prefetchable) [virtual] [size=8]
Memory at 00000370 (type 3, non-prefetchable) [virtual]
I/O ports at ec00 [virtual] [size=16]
Capabilities:
Kernel driver in use: pata_amd
Kernel modules: pata_amd, pata_acpi, ata_generic
00:0a.0 SATA controller: NVIDIA Corporation MCP65 AHCI Controller (rev a3) (prog-if 01 [AHCI 1.0])
Subsystem: Gigabyte Technology Co., Ltd Device b002
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 24, NUMA node 0
I/O ports at 09f0 [size=8]
I/O ports at 0bf0 [size=4]
I/O ports at 0970 [size=8]
I/O ports at 0b70 [size=4]
I/O ports at d800 [size=16]
Memory at fe02a000 (32-bit, non-prefetchable) [size=8K]
Capabilities:
Kernel driver in use: ahci
Kernel modules: ahci
00:0c.0 PCI bridge: NVIDIA Corporation MCP65 PCI Express bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, NUMA node 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000b000-0000bfff [size=4K]
Memory behind bridge: fdd00000-fddfffff [size=1M]
Prefetchable memory behind bridge: 00000000fdc00000-00000000fdcfffff [size=1M]
Capabilities:
Kernel driver in use: pcieport
00:0d.0 PCI bridge: NVIDIA Corporation MCP65 PCI Express bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, NUMA node 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 0000a000-0000afff [size=4K]
Memory behind bridge: f8000000-fbffffff [size=64M]
Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff [size=256M]
Capabilities:
Kernel driver in use: pcieport
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration
Flags: fast devsel, NUMA node 0
Capabilities:
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map
Flags: fast devsel, NUMA node 0
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller
Flags: fast devsel, NUMA node 0
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control
Flags: fast devsel, NUMA node 0
Capabilities:
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control
Flags: fast devsel, NUMA node 0
01:08.0 Multimedia audio controller: Creative Labs EMU10k1 [Sound Blaster Live! Series] (rev 07)
Subsystem: Creative Labs SB0100/SB0102 SBLive! 5.1
Flags: bus master, medium devsel, latency 32, IRQ 18, NUMA node 0
I/O ports at cc00 [size=32]
Capabilities:
Kernel driver in use: snd_emu10k1
Kernel modules: snd_emu10k1
01:08.1 Input device controller: Creative Labs SB Live! Game Port (rev 07)
Subsystem: Creative Labs Gameport Joystick
Flags: bus master, medium devsel, latency 32, NUMA node 0
I/O ports at c800 [size=8]
Capabilities:
Kernel driver in use: Emu10k1_gameport
Kernel modules: emu10k1_gp
01:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Flags: bus master, medium devsel, latency 32, IRQ 18, NUMA node 0
Memory at fdeff000 (32-bit, non-prefetchable) [size=2K]
Memory at fdef8000 (32-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: firewire_ohci
Kernel modules: firewire_ohci
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. Device 8197
Flags: bus master, fast devsel, latency 0, IRQ 27, NUMA node 0
I/O ports at bc00 [size=256]
Memory at fddfc000 (64-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: rtl8188ee
Kernel modules: rtl8188ee
03:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2) (prog-if 00 [VGA controller])
Subsystem: Point of View BV Device 902a
Flags: bus master, fast devsel, latency 0, IRQ 26, NUMA node 0
Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at f8000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at ac00 [size=128]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia
ip address:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s6:  mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether DATA REMOVED brd ff:ff:ff:ff:ff:ff
3: wlp2s0:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether DATA REMOVED brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic noprefixroute wlp2s0
       valid_lft 251036sec preferred_lft 251036sec
    inet6 fd38:bc01:c5cb:cb00:faf5:12cb:644c:5a36/64 scope global dynamic noprefixroute
       valid_lft 7063sec preferred_lft 3463sec
    inet6 fe80::a519:713b:58f:785a/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Well the DSi Browser is based on Opera 8.5, and while the lowest tested Opera version is 10.63, if it runs on Firefox 2 and IE4 it probably has a decent chance of at least running on the DSi without further modifications.
I'll go ahead and grab Opera 8.5 and maybe I can get an actual error.

On Opera 8.5 on a 3GHz Windows 98 Machine, with 512MB ram - much more then the DSi - I get the exact same result. Howerver, I don't get any output in the Javascript console. In fact, the page works just fine...at less then 1 frame per second. After dragging the quality down to 10, I get what feels like 1 frame every 4 seconds, and dragging the window down from 1024x768 to around 358x259 (the minimum size at which Browservice will work), it's now usuable. Keep in mind, this is on a machine almost 24 times as fast (and at that point the difference between ARM and x86 does not matter), with 32 times as much memory.
The conclusion therefore, is that it works just fine, but you need to somehow get the resolution and quality lower. From my vague recollection of using this browser as a kid, it always rendered pages larger then the actual screen, and sense this browser was developed independently of most websites at the time, the fix may involve being able to set the desired resolution and quality of the image via the url.

Note that you can set the default quality to a lower value using the --vice-opt-default-quality command line option, for example
./browservice-v<IP_ADDRESS>-x86_64.AppImage --vice-opt-default-quality=20


Push not received when the app is in foreground after 10min from the last installation

Expected Behaviour
The app receives the push both in background and foreground even after 10min or so from installation.
Actual Behaviour
The app receives the the push always in background not in foreground after 10min or so from installation
Reproduce Scenario (including but not limited to)
Steps to Reproduce
1.install the app with the push activated
2.wait 10 min or so
3.send push when the app is in foreground
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
android 6.0
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Motorola moto g3
Cordova CLI version and cordova platform version
cordova 6.3.1
cordova android 3.7.0
Plugin version
1.8.4
Sample Push Data Payload
{"payload": {"type": "notification", "pushid": "11", "foreground": true}, "message": "Hello World oh man!"}
Sample Code that illustrates the problem
.run(function($ionicPlatform,$ionicPush,$cordovaPushV5,$localStorage,$rootScope,$ionicPopup,$cordovaPushV5,$cordovaNetwork,$ionicLoading,$cordovaStatusbar,$cordovaGoogleAnalytics,Messages,EventServices) {
$ionicPlatform.ready(function() {
$rootScope.push = PushNotification.init({
android: {
senderID: "XXX",
//"forceShow": "true",
"icon": "icon",//"ic_icon_google",
//"iconColor": "blue"
},
ios: {
alert: "true",
badge: "true",
sound: "true"
}
});
		$rootScope.push.on('registration', function(data) {
		    // data.registrationId
			console.log('REG TOKEN'+JSON.stringify(data))
			alert('dev token'+data.registrationId+'--'+$localStorage.device_token_new)
			if(data.registrationId!=$localStorage.device_token_new){
				$localStorage.device_token_new = data.registrationId
			}
		});

})
$rootScope.push.on('notification', function(data) {
alert('push:'+JSON.stringify(data))
})
})
Logs taken while reproducing problem

@ai2010 can you clarify what you mean by "Push not received when the app is in foreground"? Do you mean you don't see the push in the notification shade or does your on push event handler not get called?

@macdonst I mean '$rootScope.push.on('notification', function(data) {' is not triggered

@ai2010 okay, I got you now but I can't reproduce it. I don't use Ionic very often. Do you know if the $rootScope clears down the push variable?

no the rootScope is not really the problem. As an hack what I'm doing now is a period function that every minute or so initialize the push plugin:
$rootScope.push = PushNotification.init({ android: { senderID: "XXX", //"forceShow": "true", "icon": "icon",//"ic_icon_google", //"iconColor": "blue" }, ios: { alert: "true", badge: "true", sound: "true" } });

@ai2010 that's redundant, I wouldn't do that. Can you check to see if the on('notification') handler gets cleared periodically? Without seeing your code I'm guessing that is the issue.
Also, if you reproduce the problem while running adb logcat | grep PushPlugin it'll help pin down the issue.

$rootScope functions more like a namespace than like a scoped object, @macdonst . I see no way it'd be getting cleared in the sense that would break the plugin or event propagation/lifecycle. That said, I still can't see what's going on without logs either.

@ai2010 You might be running into issues with livereload or deploy wherein you are not calling register() every time the page is loaded. This is necessary for the notification handler to work properly.


SPA mode access index.html on Azure Storage return 'page not found'

Version
v2.12.1
Reproduction link
https://github.com/bactn/bactn.github.io
Steps to reproduce
I install and build  Nuxtjs vs spa: mode. Then deploy the dist folder to Azure Storage Blob with subpath public-contents
But when I try to access index.html via the following link. It displays 'This page couldn't be found'
It works normally with http-server . command or a static web.
So my question: Can I access directly to the index.html file? what is my wrong?
(Edited) The static web work normally:
https://mystaticapp1.z22.web.core.windows.net/
The reproduce link:
https://mystaticapp1.blob.core.windows.net/public-contents/index.html
It maybe relates to this issue:
https://github.com/nuxt/nuxt.js/issues/1661
The Azure Storage Blob setup:

What is expected ?
work normally with spa mode when access directly index.html.
What is actually happening?
SPA mode return 'The page couldn't be found'

This bug report is available on Nuxt community (#c10731)

Finally, I found a solution to resolve this issue:

With router.mode is 'hash' It can work normally because when opening the index.html directly Nuxt will know the router / after #

With router.mode is 'history' It needs to define a new router has a path:  '/index.html' and router.base: '/public-contents/'.
For example in my case:

router: {
    mode: 'history',
    base: '/public-contents/',
    extendRoutes (routes, resolve) {
      routes.push(
        {
        name: 'home',
        path: '/index.html',
        component: resolve(__dirname, 'pages/index.vue')
        },
      )
    },
  },

But It will error with default building. Because Nuxt generate directory by each router, so It will create a folder has a name: 'index.html'
-> To solve this problem, add the below source code:
generate: {
    subFolders: false,
  },

I'm not sure It can resolve your issue or not but It worked for me and hope to help someone


Feedback from Google Form for CoDiOS

The comments below are from responses from the form with regards to feedback for stock CoDi, and the future of this project.
All feedback is anonymous, and any personal details remain with me. The Markdown table below is only for CoDi-related feedback.

Question: What bugs you about stock CoDi?

Question 1: What bugs you about stock CoDi?

Stopped working at all, no update possible -> dead? (my notes: what's dead? Is the screen cracked? Resources not flashed? Corrupt bootloader/firmware? I will be following up)
Power consumption
Jerky camera, phonebook unusable - only loads up to the letter 'L'
A little unresponsive, lacks a bit of functionality (my notes: What functionality? What aspect of CoDi is unresponsive? I will be following up)

What bugs you about stock CoDi?
What would you like to see in CoDiOS?
Is there anything else you would like to feedback?
On a scale of 0-10, how happy are you with stock CoDi?

Can’t flash the codi to operate outer display
Easy use
No
3

It goes jerky with the camera and, above all, the phonebook is unusable because it only loads up to the letter l
meteo; basic gps indications like models on bicycle
No, thanks
1

Inability to reply to text messages (sms).
Easily extensible, a stable well documented api that is available from both android and Linux operating systems.
 Lacks a bit of functionality
Similar app support and functionality as the notification bar. - like ability to control more apps. Full contact support - not just a certain number.
Thanks heaps for taking this project on!
7

impossible to be 'always blank until silver button pressed'
Ability to turn screen off completely (without disabling CoDi itself)
CoDi could be great, just needs some love!
6

You can only dial your favourites or the people near the top of your contacts list.
Some way to overcome what bugs me most. Maybe you could do the same as on the iPod where as you scroll fast it flips to the first letter, then if you slow again it lists all the names starting with the letter.
It's great that you are looking at improving this.
8

The notifications are not correct unless you re-boot the Cosmo
Make the alerts accurate
No
8

Stopped working at all, no update possible -> dead
Stable working as advertised is good enough for me ;-)
Anybody trying to improve is welcome.
0

Just about everything: it doesn't work as advertised, doesn't display all contacts as it has an inbuilt limitation, is slow, causes random reboots, drains battery like a sponge
Try to make the absolutely basic functions work, no need to do anything fancy like have the camera display, an easy to use volume switch
Best of luck!
0

very buggy. often just stops working and says "planet". when its working, the camera is very slow to update on screen. SW updates are very hit and miss. 20 attempts for latest codi version to install!
more reliable implimentation of current feature set. Better battery life from a well implimented/designed software. reliable sw update installer.
really appreciate your effort with this!
3

Power consumption
Configuration for disabling unused functionalities
no
1

With latest FW, biggest issue is that pressing silver button to make codi "off" and it still wakes up on "any and all" notification change.
When pressing silver button to make codi "off", have codi to stay off until I press the button again, or when actually something important comes that implies looking codi anyway, like incoming call or alarm clock.
The next Q is still hard to answer accurately as when I DO have codi enabled it seems to mainly work fine, but I rarely have it enabled because of issue described above.
5

Umm everything LOL. In short it attempts to do too much and poorly. But ill try to stick to the critical points. The screen is SMALL and therefore not really practical for tapping multiple small icons therefore... The camera function is totally useless, not fitting for the screen resolution and not appropriate for the processing power and interface. And of course its apparent lack of power management.
I would love to see a simple implementation that's more fitting for the hardware and "real world" use. I would love to see a nice basic interface and use, keeping in mind that it is only a notification / status screen. Not a bloody screen for selfies and scrolling though an address list or nested menus when touch interaction is difficult at best with such physical limitations. But If there was just ONE thing i could change with CoDi as it is now, well lets suppose it was working perfectly and THEN there would be just ONE thing I'd love to add. It would be some kind of touch "muting" option. For example I feel it would be more reliable and less prone to false inputs if the screen would stay touch muted (i don't know what to call it but work with me) until a button press or similar would ready it for touch input. Many times i would take out my cosmo to find it in flight mode or calling a contact etc. I guess in brief I wish it were to behave like a simple notification screen first and foremost and then as a touch screen, but only if really necessary. In other words I'd rather it did basic things well and reliably than trying to do everything halfheartedly. Think of the original LED design, it worked, and all people wanted to have was the ability use the phone without opening the unit - we got colour OLED - touchy feely - power sapping - crappy selfie LOL
I wish you the best of luck for your project. It's is fantastic that people like yourself have the patience and willingness to try these challenges. Hope it turns out better than you expected. Thanks for you work.
0

1. It turns on when it shouldn't, all the time.The silver button on the side should turn it the f*** off and only turn it on when I press it again.2. Partially caused by that, it's very easy to accidentally change settings, skip tracks in the music player, etc.3. It reacts even when Cosmo is open (even with current android and codi firmware), causing more instances of 2.4. Track and artist in the music player status are too small and too dim. (That, apart from caller id, is the only feature I really would like to use, but it's easier to just open the Cosmo to see the running track.)5. Power consumption is about triple the rate when I have it turned off. (I didn't really do measurements, but that's what it feels like.)So as a result of all these things, I keep mine turned off all the time (from android settings), occasionally turn it on when I want to try something, find that it doesn't work and then keep it turned off.
1. stay off with a simple button press (e.g. silver button)2. do not react to anything when turned off or opened3. see caller id and take calls4. show playing music track, but no interaction (i.e. no pause or skip track) possible if cosmo is locked (I have a blutooth headset for that.)5. some useful interaction with notifications (i.e. maybe skim through messages or mails... my sports watch is actually doing that better than stock codi)6. less power consumption (maybe as a result of 1)
Big thanks for taking up that project! I'm intrigued what you will manage. But no pressure *g* ;)
0

Battery Usage, speed
Less battery drain, Quick SMS response on declined call
I think as a bare minimum, the ability to make/receive calls that doesn't kill the battery is what is needed.
1

eats a lot of battery if powered on (even if idle); no way to power down/up when the lid is closed; no configurability; no technical documentation; closed source
a way to mirror main screen if needed, either scaled down or panning (even if slow or static); a picture viewer
thanks for your effort :-)
3

It loses connection/communication with the phone which requires a reboot to fix/remedy.
Either a more responsive screen when taking pics or a way to take a selfie with a button on the external cam
The screen is really unresponsive.
5


Update install information

Update the installation information in INSTALL (and wherever necessary to be seen in the published docs):

reference installation-recipes
conda

I think this information has been added.


Fields set in script not detected in C++?

Maybe something changed here recently? In my program fields that are added to a C++ object in script are not detectable from the C++ side. GetType is always returning "nil".
Here is the code I have been using to expose the C++ class:
L->new_usertype<Entity> (
	"Entity",
	sol::base_classes, sol::bases<SharedObject>(),
	sol::meta_function::index, &SharedObject::dynamic_get,
	sol::meta_function::new_index, &SharedObject::dynamic_set };

	void SharedObject::dynamic_set(std::string key, sol::stack_object value)
	{
		auto it = entries.find(key);
		if (it == entries.cend()) {
			entries.insert(it, { std::move(key), std::move(value) });
		}
		else {
			std::pair<const std::string, sol::object>& kvp = *it;
			sol::object& entry = kvp.second;
			entry = sol::object(std::move(value));
		}
	}

	sol::object SharedObject::dynamic_get(std::string key) {
		auto it = entries.find(key);
		if (it == entries.cend()) {
			return sol::lua_nil;
		}
		return it->second;
	}

This was caused my Trim() function not working correctly since some changes in C++.


Update Remove-SPAppPrincipalPermission.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Remove-SPAppPrincipalPermission.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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.


Re-run flaky integration tests 2x when they fail

I suspect we're not always waiting for events to come in or in some cases we're waiting for too long.  That's the next investigation.


Is it GetChildren Bug?

Hi there~
When I use Treeview with GetParent property, SelectedItems property works fine.
But when using it with [GetChildren="(item) => item.Children"], whenever I expand and collapse the treenode,
the SelectedItems property value is weird. SelectedItems refresh and initialize whenever click the expand and collapse button..
please check this out

Hi @HongJinHyeon,
please provide the code that you experience this issue with.
Thanks
Stefan

hi there~
this is what I wrote.
thanks
@page "/errorTree"

<TreeView Items="@Nested" GetChildren="(item) => item.Children" AllowSelection="true" @bind-SelectedItems="SelectedValues">
    <ItemTemplate>
<EMAIL_ADDRESS>    </ItemTemplate>
</TreeView>

Current Selected Items : @string.Join(", ", SelectedValues.Select(s => s.Seq))

@code {
    private List<Item> _selectedValues = new List<Item>();
    public List<Item> SelectedValues
    {
        get => _selectedValues;
        set
        {
            _selectedValues = value;
        }
    }

    private static readonly List<Item> AllItems = new List<Item>
{
            new Item
            {
                Self = "regaion1",
                Seq = "S1",
                Parent = "",
                Children = new List<Item>
            {
                    new Item
                    {
                        Parent = "S1",
                        Seq = "S2",
                        Self = "regaion1-1"
                    },
                    new Item
                    {
                         Parent = "S1",
                        Seq = "S3",
                        Self = "regaion1-2"
                    },
                    new Item
                    {
                         Parent = "S1",
                        Seq = "S33",
                        Self = "regaion1-3"
                    }

                }
            },
            new Item
            {
                Parent = "",
                Seq = "S4",
                Self = "regaion2"
            },
        };

    public class Item
    {
        public string Seq { get; set; }
        public string Self { get; set; }
        public string Parent { get; set; }
        public List<Item> Children { get; set; }
    }
    private List<Item> Nested = AllItems.ToList();

}

Thanks @HongJinHyeon for providing the code. I was able to reproduce the issue and fix it. Version 1.6.0 is going to be available in a few minutes. This issue was a side-effect of supporting lazy-loaded tree views.


Floatzel cannot learn growl.

It should only be allowed to use Growl if it is a Valley Windworks encounter and not a Route 205 encounter.  This shouldn't ever be a major issue unless they have a Drifloon on their team.

Fixed for next server reboot.


Release Google.Geo.Type version 1.2.0

Changes in this release:
New features

Change netstandard2.1 target to netstandard2.0 (commit 82bea85)

Created release for Google.Geo.Type-1.2.0


Update tokens.ts

Could you please give more context of what this token is, what project it is for etc.


Design 2 : Design REST APIs for operations on products and shops

Description
Provide detailed design on how REST APIs looks like to perform desired operations on products and shops
Design Details Required

Information REST endpoints with URL, request body JSON and HTTP Method.
Information on the response returned by the API
Information on all error responses returned by the API

Note: JSON template of request, response and error response need to maintain as a standard for upcoming APIs as well.

Updated the API documentation
https://github.com/pavan-nw/stock-admin/wiki/API-Documentation


Create ttSECURITY.md

I have no education in coding .. I barely graduated 8th grade .. I've been trying to get a hacker off my device for 5 years .. I don't know what I'm doing on this site.sorry


iOS 7.0 & Cocoapods

Hi,
Your readme says it is compatible with 7.0 but your podspec says 8. Could you please update one of the two. Cheers!

@Cedrick84 unfortunately Cocoapods only supports iOS 8.0 for Swift integration because of the need for dynamic frameworks and the fact they are not accepted into the app store for iOS 7.0 targets.
Your best integration option is to manually include the *.swift files into your application target.
Hope this helps.


About the stability of finetuning vae with LoRA

Hi author, thanks for the enlightening work! When I try to reimplement OSEDiff, I find fine-tuning VAE and UNet in one stage is hard to converge. Do you have any recommendations/tricks to stablize this process or they should be trained step by step.

It will be more stable but unable to generating more details.


Add ScriptPairSimilarityEstimator deserializer.

@giagiannis A small fix to the estimator deserializer.
Maybe it's a good idea to also change:
log.Println("Unsupported Estimator Type.")

to:
log.Fatal("Unsupported Estimator Type.")

Coverage decreased (-0.2%) to 82.941% when pulling dfb58eb3e26b2ff8cea3cf86aff8475426809c91 on tabac:script-pair-estimator-deserializer into 09e4c69dabea2eeceb31137e8234efc21c18f7fc on giagiannis:devel.


Method descriptor

Is there a way to get the method descriptor for a method (see http://docs.oracle.com/javase/specs/jvms/se8/html/jvms-4.html#jvms-4.3.3 ).  JavaSymbolSolver would be great to resolve the fully qualified objects wondering if anyone already has written something like this?
Thanks!

No, but we have some code to do the opposite thing because we work also with compiled code and from compiled code we want to derive readable descriptors.
That said it should not be too hard to implement. It is just not a top priority right now (but I would love to receive a Pull Request for this).


QdtViz not render piecharts

Qdt viz is not render piecharts. It is working for barcharts, linecharts, but for piecharts it simply not render. Any idea about this behavior?

Qdt viz is not render piecharts. It is working for barcharts, linecharts, but for piecharts it simply not render. Any idea about this behavior?

This issues was caused because of the Qlik Sense version (February 2020). After updated to April version the charts back to render normally