ESP32 and SPI connection: corrupt accelerometer and magnetometer values

Hi,
Issue:
when using the library with an ESP32 connected via SPI, accelerometer and magnetometer values are corrupt. Example: Serial.print(IMU->getAccelX_mss(),6) prints "ovf".
Reason:
When not performing a calibration, numerous values for accelerometer biases such as "_axb" etc. defined in  MPU9250.h are not initialized.

Please post the code that you are running and getting ovf.

Hi,
the following Arduino code
`
#include "MPU9250.h"
MPU9250* IMU = NULL;
SPIClass * vspi = NULL;
void setup(void) {
Serial.begin(115200);
vspi = new SPIClass(VSPI);
//SCLK = 18, MISO = 19, MOSI = 23, SS = 5
vspi->begin();
IMU = new MPU9250(*vspi, 33);
int status = IMU->begin();
if (status != 1)
{
Serial.println("IMU initialization unsuccessful, error code " + String(status));
}
else
{
Serial.println("IMU SPI readout OK, configuring accelerometer range: " + String(IMU->setAccelRange(MPU9250::ACCEL_RANGE_2G)));
}
}
void loop(void) {
delay(1000);
IMU->readSensor();
Serial.print(IMU->getAccelX_mss(), 6);
Serial.print("\t");
Serial.print(IMU->getAccelY_mss(), 6);
Serial.print("\t");
Serial.print(IMU->getAccelZ_mss(), 6);
Serial.print("\t");
Serial.print(IMU->getGyroX_rads(), 6);
Serial.print("\t");
Serial.print(IMU->getGyroY_rads(), 6);
Serial.print("\t");
Serial.print(IMU->getGyroZ_rads(), 6);
Serial.print("\t");
Serial.print(IMU->getMagX_uT(), 6);
Serial.print("\t");
Serial.print(IMU->getMagY_uT(), 6);
Serial.print("\t");
Serial.print(IMU->getMagZ_uT(), 6);
Serial.print("\t");
Serial.println(IMU->getTemperature_C(), 6);
}
`
produces serial outputs such as
18:20:07.032 -> ovf	ovf	ovf	0.031426	0.067246	-0.006924	ovf	ovf	ovf	25.762333
best regards
Jan

I'm having the exact same issue in one of my sketches.
Did you just initialize the _axb, _ayb and _azb to 0 to fix it?

Hi,
yeah, that is exactly what i did. once I find the time I should add init values for all variables and make a merge request.
cheers
Jan

Please do submit a pull request. Not sure why the ESP32 compiler is treating those differently and I don't have an ESP32 to test with, but seems like a straightforward fix.

I'm running it on the Arduino Due fyi

Hello,
I am having the exact same issue where all 9 values show ovf without the bias correction that @JeroenGar  suggested. After the bias variables being initialized to 0.0f, all the values are 0.0f. My sketch is exactly same as that of @jtec.
How should I debug this?

Never mind, got it working! Was a connection issue. Still had to initialize the bias variables though.

Thanks @skulumani! Please make a pull request for the initialization, that works and IMHO should be definitely in the current code.


Upgrade to node 8

Currently route-annotator does not publish binaries for node 8.
This blocks OSRM from upgrading to node 8.
Publishing binaries for node 8 would be awesome
Maybe this is an issue that needs to tell travis to build it with node 8:
https://github.com/mapbox/route-annotator/blob/master/.travis.yml
Maybe there is more to do.

Done with https://github.com/mapbox/route-annotator/pull/35
Node8 binaries are available from v0.1.1 onwards


Feature Request - Command to use via shortcut

I would find it very useful to be able to set a shortcut/macros to have the relative path written as the first line of the file.

try this
https://gofile.io/d/Lji8KD
select the desired compiler in the installer


COVERALLS_REPO_TOKEN freezes tap

So I've just setup my first project with node-tap, Travis CI, and Coveralls.
I followed instructions found here: http://www.node-tap.org/coverage/
I can't get Coveralls to work though, and it seems to be an issue with running tap CLI.
npm test fails when COVERALLS_REPO_TOKEN is set.
Removing the env var makes the test run successfully in 45 secs.
Running locally with the coveralls env set, and DEBUG=* does not display at all, and just freezes.
Might be related to #210.
Results from Travis CI:
https://travis-ci.org/marcusnielsen/rxjs-server#L480
$ npm test
><EMAIL_ADDRESS>test /home/travis/build/marcusnielsen/rxjs-server
> tap --reporter=classic -- ./app/**/**/**/**/*.test.js
/home/travis/build.sh: line 45:  2628 Killed                  npm test
The command "npm test" exited with 137.
Done. Your build exited with 1.

Reproduced with codecov on travis CI.
Same error.

Seems to be an issue just generating the --coverage locally. So don't put any thought into this until I debug some more.

Issue solved by changing npm test script:
https://github.com/marcusnielsen/rxjs-server/commit/2153ad3205aed9bcb198a8af0614c171faafc2e9
Does not work: "test": "tap --reporter=classic -- ./app/**/**/**/**/*.test.js"
Does work:"test": "tap ./app/**/**/**/**/*.test.js --reporter=classic"
Since npm also uses --, Maybe that messes up the arguments for tap. Still weird results though!
I'm closing this as the issue feels really minor, and I managed to solve it easily anyhow.


The latest sickrage docker image no longer has SickBeard.py

/ # ls /sickrage/
COPYING.txt         Gruntfile.js        README.txt          changelog.md        package-lock.json   pre-commit-hook.sh  requirements.txt    setup.cfg           sickrage            tests
Dockerfile          MANIFEST.in         SiCKRAGE.py         crowdin.yaml        package.json        readme.md           runscripts          setup.py            src                 webpack.config.js

I actually found out more info over the weekend. Apparently sickrage was taken over by a former dev and the project has actually moved to https://github.com/SickChill/SickChill/
It seems like a big mess at the moment, but the version that is at https://github.com/SickRage/sickrage is hijacking people's sickrage installs and sending them to some outside domain.

Hi
I've already fixed and moved to SickChill :).
I picked up the problem when testing the changes.
:)


error: building boost-config:x64-windows failed with: BUILD_FAILED

Copy issue body from C:/dev/vcpkg/installed/vcpkg/issue_body.md
error: building boost-config:x64-windows failed with: BUILD_FAILED
I have the latest port files with git pull and vcpkg update
Had the same problem with 'building boost-build:x64-windows' right before but soved it with https://github.com/microsoft/vcpkg/pull/26527 @thebelin

c:\dev\vcpkg>.\vcpkg install tgbot-cpp:x64-windows
Computing installation plan...
The following packages will be built and installed:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>vcpkg-cmake:x64-windows@2023-05-04
vcpkg-cmake-config:x64-windows@2022-02-06#1
vcpkg-cmake-get-vars:x64-windows@2023-12-31
<EMAIL_ADDRESS>Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\User\AppData\Local\vcpkg\archives in 1.73 ms. Use --debug to see more details.
Installing 1/73<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- Downloading https://github.com/boostorg/config/archive/boost-1.84.0.tar.gz -> boostorg-config-boost-1.84.0.tar.gz...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Trying to load bundleconfig from c:\dev\vcpkg\vcpkg-bundle.json
[DEBUG] Failed to open: c:\dev\vcpkg\vcpkg-bundle.json
[DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt
[DEBUG] Metrics enabled.
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Feature flag 'dependencygraph' unset
Downloading https://github.com/boostorg/config/archive/boost-1.84.0.tar.gz
warning: Download failed -- retrying after 1000ms
warning: Download failed -- retrying after 2000ms
warning: Download failed -- retrying after 4000ms
error: Failed to download from mirror set
error: https://github.com/boostorg/config/archive/boost-1.84.0.tar.gz: WinHttpReceiveResponse failed with exit code 12175
error: https://github.com/boostorg/config/archive/boost-1.84.0.tar.gz: WinHttpReceiveResponse failed with exit code 12175
error: https://github.com/boostorg/config/archive/boost-1.84.0.tar.gz: WinHttpReceiveResponse failed with exit code 12175
error: https://github.com/boostorg/config/archive/boost-1.84.0.tar.gz: WinHttpReceiveResponse failed with exit code 12175
[DEBUG] D:\a_work\1\s\src\vcpkg\base\downloads.cpp(1030):
[DEBUG] Time in subprocesses: 0us
[DEBUG] Time in parsing JSON: 2us
[DEBUG] Time in JSON reader: 0us
[DEBUG] Time in filesystem: 1066us
[DEBUG] Time in loading ports: 0us
[DEBUG] Exiting after 12 s (11505912us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):
  Failed to download file with error: 1
  If you are using a proxy, please check your proxy setting. Possible causes are:

  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
     set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
     The value set by your proxy might be wrong, or have same `https://` prefix issue.

  3. Your proxy's remote server is out of service.

  If you've tried directly download the link, and believe this is not a temporary
  download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
  to report this upstream download server failure.

Call Stack (most recent call first):
scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
scripts/cmake/vcpkg_from_github.cmake:106 (vcpkg_download_distfile)
ports/boost-config/portfile.cmake:3 (vcpkg_from_github)
scripts/ports.cmake:170 (include)
error: building boost-config:x64-windows failed with: BUILD_FAILED
Elapsed time to handle boost-config:x64-windows: 12 s
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+boost-config
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[boost-config]+Build+error+on+x64-windows&body=Copy+issue+body+from+C%3A%2Fdev%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

@CBugBuster, Thanks for posting this issue, I can not repo your issue on my local machine, It looks like this error is a network problem, you try again using the latest vcpkg.

@JonLiu1993, thank you for your reply, I have the latest port files with git pull and vcpkg update and it really seems like a network issue, due to the message "Your connection is not private" when trying to open any link. I hope we could find the solution together

@CBugBuster, Can you still reproduce your error now?

@JonLiu1993, yes, it's exactly the same as on my second comment. Or maybe I got you wrong, if that's so, let me know

@CBugBuster, We consider this error from two points:

Can you download this package manually https://github.com/boostorg/config/archive/boost-1.84.0.tar.gz
Second, do you have anti-virus software installed on your computer or a firewall blocking SSL connections?

@JonLiu1993

No, I can't with either Google or Bing(
I have Avast and I have turned off all the screens. I also have Windows Defender, and I don't actually know how to deal with it or even whether it works or not. Have cleared the cache and cookies, https://www.google.com opens successfully

C:\Windows\System32>netsh firewall show state
Firewall status:
Profile                           = ???????
Operational mode                  = Enable
Exception mode                    = Enable
Multicast/broadcast response mode = Enable
Notification mode                 = Enable
Group policy version              = ?????????? ????????? Windows
Remote admin mode                 = Disable
Ports currently open on all network interfaces:
Port   Protocol  Version  Program
1688   TCP       Any      (null)
3389   TCP       Any      (null)
IMPORTANT: Command executed successfully.
However, "netsh firewall" is deprecated;
use "netsh advfirewall firewall" instead.
For more information on using "netsh advfirewall firewall" commands
instead of "netsh firewall", see KB article 947709
at https://go.microsoft.com/fwlink/?linkid=121488 .

@CBugBuster, https://github.com/boostorg/config/archive/boost-1.84.0.tar.gz I can download package manually.
In addition, if you have a firewall or some anti-virus software on your computer, this issue is not a vcpkg problem, but your "network problem".

@JonLiu1993 it worked but partly. 10/71 pieces are already installed, I use psiphon. Thank you! But another problem has appeared.
### error: building boost-build:x64-windows failed with: BUILD_FAILED
C:\dev\vcpkg>.\vcpkg  install tgbot-cpp
warning: In the September 2023 release, the default triplet for vcpkg libraries changed from x86-windows to the detected host triplet (x64-windows). For the old behavior, add --triplet x86-windows . To suppress this message, add --triplet x64-windows .
Computing installation plan...
The following packages will be built and installed:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>vcpkg-cmake-get-vars:x64-windows@2023-12-31
<EMAIL_ADDRESS>Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
-- Setting "%HTTP_PROXY%" environment variables to "<IP_ADDRESS>:52066".
-- Setting "%HTTPS_PROXY%" environment variables to "<IP_ADDRESS>:52066".
-- Setting "%SOCKS_PROXY%" environment variables to "<IP_ADDRESS>:52065".
Restored 0 package(s) from C:\Users\User\AppData\Local\vcpkg\archives in 1.11 ms. Use --debug to see more details.
Installing 1/61<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- Downloading https://github.com/boostorg/build/archive/boost-1.84.0.tar.gz -> boostorg-build-boost-1.84.0.tar.gz...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Trying to load bundleconfig from C:\dev\vcpkg\vcpkg-bundle.json
[DEBUG] Failed to open: C:\dev\vcpkg\vcpkg-bundle.json
[DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt
[DEBUG] Metrics enabled.
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Feature flag 'dependencygraph' unset
Downloading https://github.com/boostorg/build/archive/boost-1.84.0.tar.gz
[DEBUG] Trying to hash C:\dev\vcpkg\downloads\boostorg-build-boost-1.84.0.tar.gz.18920.part
[DEBUG] C:\dev\vcpkg\downloads\boostorg-build-boost-1.84.0.tar.gz.18920.part has hash 61540a3b2b7b6167ed8286daed4b4fde515ae9e0de81d17ef688d7972a0a6325b15afbe4e9a73ec883a81d5b86998d612cadbdc79abaf1b087a74e4e6b7cc2b5
error: Failed to download from mirror set
error: File does not have the expected hash:
url: https://github.com/boostorg/build/archive/boost-1.84.0.tar.gz
File: C:\dev\vcpkg\downloads\boostorg-build-boost-1.84.0.tar.gz.18920.part
Expected hash: 11ac21b27c5c656951784734c6642a2d4efa185e074ec48561f2800203b639d4a628fec6d356bb733494889141327a7ac730ce127449bfc7d509d5d213216995
Actual hash: 61540a3b2b7b6167ed8286daed4b4fde515ae9e0de81d17ef688d7972a0a6325b15afbe4e9a73ec883a81d5b86998d612cadbdc79abaf1b087a74e4e6b7cc2b5
[DEBUG] D:\a_work\1\s\src\vcpkg\base\downloads.cpp(1030):
[DEBUG] Time in subprocesses: 0us
[DEBUG] Time in parsing JSON: 2us
[DEBUG] Time in JSON reader: 0us
[DEBUG] Time in filesystem: 980us
[DEBUG] Time in loading ports: 0us
[DEBUG] Exiting after 11 s (11373807us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):
  Failed to download file with error: 1
  If you are using a proxy, please check your proxy setting. Possible causes are:

  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
     set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
     The value set by your proxy might be wrong, or have same `https://` prefix issue.

  3. Your proxy's remote server is out of service.

  If you've tried directly download the link, and believe this is not a temporary
  download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
  to report this upstream download server failure.

Call Stack (most recent call first):
scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
scripts/cmake/vcpkg_from_github.cmake:106 (vcpkg_download_distfile)
ports/boost-build/portfile.cmake:9 (vcpkg_from_github)
scripts/ports.cmake:170 (include)
error: building boost-build:x64-windows failed with: BUILD_FAILED
Elapsed time to handle boost-build:x64-windows: 11 s
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+boost-build
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[boost-build]+Build+error+on+x64-windows&body=Copy+issue+body+from+C%3A%2Fdev%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

@CBugBuster, What I can confirm is that there is no problem with the boost hash value. Please delete your vcpkg and your download cache, and try cloning a new vcpkg try again.

Thank you for help @JonLiu1993

Thank you for help @JonLiu1993


Actions bot testing 2

Pull request merged

This is an automated message from Hunajaholisti [BOT].

Thank you for your contribution! Your pull request has been merged.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects here.


Fix typo

a -> an

@changeworld : Thanks for your contribution! The author, @jseb225, has been notified to review your proposed change.

Thanks for the fix!
#sign-off


Re-check bug undefined is not an object when perform transaction

Describe the bug
Re-check bug undefined is not an object when perform transaction
To reproduce the bug
Version test: v1.1.6(231)
Device test: IP 11
Steps:

Perform any transaction
Observe the displayed screen

Actual: Sometimes show message: Undefined is not an object(evaluting't.timeAutoLock')

This issue is relating to background. @S2kael will take this task, thanks!

Version test: https://d346e75f.subwallet-webapp.pages.dev/
Validation passed.


Issue with numeric literal inference

This code produces a type error:
-- clamp :: Number -> Number -> Number -> Maybe Number
clamp : min -> max -> n ->
	if (n > min)
		(if (n < max) (Some n) None)
		None

-- single-digit :: Number -> Maybe Number
single-digit : clamp -10 10

show (single-digit 5)
show (single-digit 10)
show (single-digit -4)

error: mismatched types
  --> playground:12:20
   |
12 | show (single-digit -4)
   |                    ^^ expected number, but found number

Uncommenting the explicit type annotations resolves the error.

The different numeric types were removed in #66 — maybe we'll come back to this in the future.


Retain azure-cli support for connecting to cosmosdb emulator

Describe the bug
Currently, when connecting to the cosmosdb emulator using azcli, there is deprecation notice for the "az cosmosdb database" command. The new alternatives (az cosmosdb SQL Database) doesn't seem to have support for connecting to the cosmosdb emulator since it is lacking the --key argument and always expects the --account-name argument
To Reproduce
Run the cosmosdb emulator using the docker container on Mac OS X or linux
Run the following command to list databases on cosmosdb emulator
az cosmosdb database list --key "C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==" --url-connection "https://localhost:8081"
The following deprecation is displayed

This command has been deprecated and will be removed in a future release. Use 'cosmosdb sql database, cosmosdb mongodb database, cosmosdb cassandra keyspace or cosmosdb gremlin database' instead.
This command is implicitly deprecated because command group 'cosmosdb database' is deprecated and will be removed in a future release. Use 'cosmosdb sql database, cosmosdb mongodb database, cosmosdb cassandra keyspace or cosmosdb gremlin database' instead.

Expected behavior
The newer commands like "az cosmosdb SQL Database" should support the --key argument and thus provide a way to connect to cosmosdb emulator running locally instead of depending on cloud resources
Environment summary
OS: Mac OS X
azure-cli                         2.24.2
core                              2.24.2
telemetry                          1.0.6
Python location '/usr/local/Cellar/azure-cli/2.24.2/libexec/bin/python'
Extensions directory '/Users/vishuma/.azure/cliextensions'
Python (Darwin) 3.8.10 (default, May  4 2021, 03:06:52)
[Clang 12.0.0 (clang-1<IP_ADDRESS>)]
Additional context
As a developer I want a way to work completely isolated from cloud resources during development thus reducing cloud costs and being isolated from other developer's changes

route to service team

Thanks for raising the issue, we are discussing on the next steps.

ConnectionKey based access to the resources is not supported using Azure Resource Manager based operations. CLI intended to expose the ARM operations.
Ideally, there should be some other tool to access your resources using Connection Key based access. Unfortunately, there is none I am aware of.
CLI is not intended to be used for this purpose, hence we do not intend to support it.

ConnectionKey based access to the resources is not supported using Azure Resource Manager based operations. CLI intended to expose the ARM operations.
Ideally, there should be some other tool to access your resources using Connection Key based access. Unfortunately, there is none I am aware of.
CLI is not intended to be used for this purpose, hence we do not intend to support it.

The cli module you are using predates our current resource provider and has been deprecated.
In either case, all management clients in Azure such as Azure CLI, Azure PowerShell, ARM Templates, Terraform, etc. are designed to talk to the Azure Resource Management (ARM) endpoint management.azure.com. As such we would not look to provide key-based access to Cosmos DB resources using any current Azure Management clients.
The Cosmos DB emulator supports the dev/test for our data plane SDKs. If you are looking to do dev/test on your DevOps or management operations you can provision a serverless Cosmos DB account. This will have zero cost as long as you are not doing any data plane operations.


Errors with AWS: extra fields not permitted (type=value_error.extra)

Describe the bug
Using iambic 0.9.1 I'm getting a couple of errors when importing my AWS Organisation with SSO, both during setup and also when running import.
During setup:
2023/06/15 16:40:35 [info     ] Failed to refresh AWS accounts
  error=ValidationError(model='RoleProperties', errors=[{'loc': ('InlinePolicies', 2, 'id'), 'msg': 'extra fields not permitted', 'type': 'value_error.extra'}])
? What would you like to configure in AWS? Go back

During import afterwards:
2023/06/15 16:45:22 [info     ] Finished templated user generation
Traceback (most recent call last):
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/bin/iambic", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/iambic/main.py", line 411, in import_
    asyncio.run(config.run_import(exe_message, repo_dir))
  File<EMAIL_ADDRESS>line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/iambic/config/dynamic_config.py", line 245, in run_import
    await asyncio.gather(*tasks)
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/iambic/plugins/v0_1_0/aws/handlers.py", line 458, in import_aws_resources
    await asyncio.gather(*tasks)
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/iambic/plugins/v0_1_0/aws/handlers.py", line 335, in import_service_resources
    await asyncio.gather(
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/iambic/plugins/v0_1_0/aws/iam/role/template_generation.py", line 605, in generate_aws_role_templates
    resource_template = await create_templated_role(
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/iambic/plugins/v0_1_0/aws/iam/role/template_generation.py", line 435, in create_templated_role
    RoleProperties(**role_template_properties),
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/simon/.local/share/virtualenvs/iambic-templates-5HIzPko0/lib/python3.11/site-packages/iambic/core/models.py", line 85, in __init__
    super().__init__(*args, **kwargs)
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for RoleProperties
InlinePolicies -> 2 -> id
  extra fields not permitted (type=value_error.extra)

To Reproduce
Steps to reproduce the behavior:
Run iambic import
Expected behavior
A successful import
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Community Engagement
Your vote counts! Please support this bug report by adding a 👍 reaction to the original issue, which will aid the community and maintainers in addressing this problem.
Please refrain from adding "+1" or "me too" comments, as these create unnecessary noise for issue followers and do not help in prioritizing the issue. If you wish to contribute to solving this issue or have submitted a pull request, please leave a comment.

I am able to replicate the bug by making this as the role inline policy:
{
    "Version": "2012-10-17",
    "Id": "cd3ad3d9-2776-4ef1-a904-4c229d1642ee",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Deny",
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::fake-bucket/hello"
        }
    ]
}


Allow clients to report if they own or share the underlying connection string (Part 2)

Fixes https://github.com/Azure/azure-sdk-for-net/issues/6032
Breaking change. Should be merged for the next major.

Can one of the admins verify this patch?

@jsquire @AlexGhiondea have you had a chance to triage this one?

Ping

I don't have good insight into the current plans for the next Service Bus release, as I'm focused elsewhere at present.   I'll need to defer to @AlexGhiondea, who will have better insight.

Hey @SeanFeldman! As we don't yet have sufficient context on this, I am adding @binzywu and @makam to take a look.

@AlexGhiondea have you had a chance to connect with the broker team?
Would be nice to have this PR labelled with Client, Service Bus, and breaking-change to indicate what it stands for.

I'll have to continue to defer to @AlexGhiondea for insight regarding conversations with the service team.   However, I assigned the issue, applied tags, and tagged reviewers.

@SeanFeldman:  I didn't see any objections and the change seems reasonable to me;  I merged it in so that it'll go with the pending set of breaking changes.


Update deployment configurations for KSP

Signed-off-by: Emiliano Suñé<EMAIL_ADDRESS>

Please note that due to the nature of the service, all traffic between containers is via Internet so the only policies that are necessary are the ones to enable Ingress traffic to the pod(s).


Issue with silent refresh of token, while using OAuth2 implicit grant flow with Azure AD

We're observing issues while attempting to do a silent refresh of our access token, using userManager().signinSilent().
The following are the our configured settings:

The following is the error we receive:

It seems like the state is transferring as a # parameter over via redirect in the iframe:

The issue seems to be related to IFrameWindow.prototype._message.

After making the suggested change, as specified in the image, everything works fine. The state is read correctly and user token is refreshed properly.
Seems odd that we have to make that change though, and so we're wondering if someone can point out what we might be doing wrong here.
Thanks in advance!

Not sure why e.data is incorrect?


fix(trace): use LastValue for open connections

This commit replaces an erroneous Sum aggregation for a LastValue
aggregation for open connections.
In addition, this commit encapsulates package-level global state for the
metrics into a MetricsCollector.

Now the number of open conns looks like this (and doesn't require any additional configuration to see correctly).


Add CITATION file to repo

Hi, just wanted to let you know that Github supports CITATION.cff files which might make sense to include in this repo

Oh, thanks for the hint


feat: configure calico admission in extension setup

How to categorize this PR?

/area networking
/kind cleanup
What this PR does / why we need it:
So far, only providers and cilium admission controllers were deployed in the (local) extensions setup. This PR adds calico admission as well.
Special notes for your reviewer:
Release note:

NONE

/lgtm

/test pull-gardener-e2e-kind-ha-multi-zone-upgrade

/test pull-gardener-e2e-kind-migration-ha-single-zone

@timuthy ping for approval


Serve + Nested Routing results in Error

I'm currently using serve with the following config to redirect all routes back to index.html:
{
  "rewrites": [
    { "source": "/**", "destination": "/index.html" },
    { "source": "/**/**", "destination": "/index.html" }
  ]
}

My Routes are defined as follows in Solid:
const AppRoutes = () => {
  return (
    <Routes>
      <Route
        path="/"
        element={

            <Link href={'/app/2'}>Link</Link>

        }
      />
      <Route path={'/app'}>
      <Route path={'/'} element={
Hi
}></Route>
        <Route path={'/*all'} element={
Hello
}></Route>
      </Route>
    </Routes>
  );
};

Going directly in the browser to localhost:3000/app results in the correct Hi being displayed. Clicking the link if I go to localhost:3000 correctly displays Hello.
However, if I decide to hit localhost:3000/app/2 in my address bar, I get the following errors:
[Error] SyntaxError: Unexpected token '<'
	(anonymous function) (runtime.js:1)
[Error] SyntaxError: Unexpected token '<'
	(anonymous function) (solid-js.js:1)
[Error] SyntaxError: Unexpected token '<'
	(anonymous function) (regexparam.js:1)
[Error] SyntaxError: Unexpected token '<'
	(anonymous function) (rturnq.js:1)
[Error] SyntaxError: Unexpected token '<'
	(anonymous function) (main.js:1)
[Error] Did not parse stylesheet at 'http://localhost:3000/app/main.css' because non CSS MIME types are not allowed in strict mode.

I'm using the latest solid/solid-router and webpack
Any chance there's a known solution to this and I'm just being dumb?

It looks like your paths for your assets in your index.html are relative rather than absolute. So when you refreshing it can't find things like main.css in the right place. So when you are at / then it's /main.css which exists.. but when you are at /app it tries /app/main.css which doesn't.

Closing as stale.


fix: rewrite Dockerfile to resolve architecture mismatch issues

Description
This should address the arm/amd64 binary errors in the built image while keeping the Go build stage fast by using the BUILDPLATFORM/TARGETPLATFORM and cross-compiling.
It also moves the tools stage from bullseye to bookworm: bookworm has clang-14 available in the package manager and directly installable, so all of the manual downloads are removed, and the explicit installations are cut down significantly.
Removes some unnecessary Docker cruft which may have been well-intentioned but isn't useful.
Related Issue
This builds on #260 which fixed #130.
Checklist

[x] I have read the contributing documentation.
[x] I signed and signed-off the commits (git commit -S -s ...). See this documentation on signing commits.
[x] I have correctly attributed the author(s) of the code.
[x] I have tested the changes locally.
[x] I have followed the project's style guidelines.
[x] I have updated the documentation, if necessary.
[x] I have added tests, if applicable.

Screenshots (if applicable) or Testing Completed
Please add any relevant screenshots or GIFs to showcase the changes made.
Additional Notes
Add any additional notes or context about the pull request here.

Please refer to the CONTRIBUTING.md file for more information on how to contribute to this project.

tested by deploying the image from my branch on to an amd/arm+windows cluster and verifying that all retina-agents started and plugins loaded without error
cc @anubhabMajumdar

what was the cause of the segfault? @rbtr

upgrade the tools image to debian 12 (and installed clang14 there) but the agent image was still using debian 11 distroless. updated that and it resolved


fix: raw json result

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.875%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3241

Relevant Lines:
5238

💛  - Coveralls


respect xasx and yaxs params when calculating usr

currently only does "i"

#48 but need to get these from the right place, probably gs.config

this is now taken care of w/ the switch to plot.window(), which will use those pars for usr


[ENH] forecasting grid/random search estimators return wrong indices in update_predict

ForecastingGridSearchCV and ForecastingRandomSearchCV fail the test for update_predict_predicted_index:
from sktime.forecasting.model_selection._split import SingleWindowSplitter
from sktime.forecasting.exp_smoothing import ExponentialSmoothing
from sktime.performance_metrics.forecasting import MeanAbsolutePercentageError
from sktime.forecasting.model_selection import ForecastingGridSearchCV

params = {
    "forecaster": ExponentialSmoothing(),
    "cv": SingleWindowSplitter(fh=1),
    "param_grid": {"initialization_method": ["estimated", "heuristic"]},
    "scoring": MeanAbsolutePercentageError(symmetric=True),
}
f = ForecastingGridSearchCV(**params)

from sktime.utils.estimator_checks import check_estimator

check_estimator(f, return_exceptions=False, tests_to_run="test_update_predict_predicted_index")

yields traceback
AssertionError:
Arrays are not equal

Mismatched elements: 12 / 12 (100%)
Max absolute difference:<PHONE_NUMBER>000000
 x: array(['2000-02-07T00:00:00.000000000', '2000-02-07T00:00:00.000000000',
       '2000-02-07T00:00:00.000000000', '2000-02-07T00:00:00.000000000',
       '2000-02-07T00:00:00.000000000', '2000-02-07T00:00:00.000000000',...
 y: array(['2000-02-08T00:00:00.000000000', '2000-02-09T00:00:00.000000000',
       '2000-02-10T00:00:00.000000000', '2000-02-11T00:00:00.000000000',
       '2000-02-12T00:00:00.000000000', '2000-02-13T00:00:00.000000000',...

Strangely, it works for the NaiveForecaster which is the default test parameter choice.
However, it fails similarly, with NaiveForecaster, after the simplification in PR https://github.com/alan-turing-institute/sktime/pull/2874. That it fails with ExponentialSmoothing indicates that the problem is with the grid search, not with the refactor #2874.

Potential explanation: the delegation in grid/random search was calling _update instead of update, which did not update the cutoff. But, that bug cancelled out with the nested structure of NaiveForecaster which was wrapping a _NaiveForecaster inside NaiveForecaster, so the _update of NaiveForecaster was actually patched through to the update to _NaiveForecater.


MCS-1569 remove unnecessary ai2thor stuff

@ThomasSchellenbergNextCentury I deleted all commented out code. Reviewing should be much easier now.

@phile-caci

The next pr removes coffee machine and many many more scripts.
ActionFinished called with agentState not in processing this message is ok it only affects the editor.
This happens whenever a goal is not present in the scene. As a separate ticket we could add a check for it but its not an issue as is.

@phile-caci

The next pr removes coffee machine and many many more scripts.
ActionFinished called with agentState not in processing this message is ok it only affects the editor.
This happens whenever a goal is not present in the scene. As a separate ticket we could add a check for it but its not an issue as is.

Thanks @jaudick !


Do not use FQDN as Mail-From

Make Mail-From a config option. Prevents Sendmail from mocking about some nonexisting domain
/sendmail: 553 5.1.8 Sender address<EMAIL_ADDRESS>domain does not exist

Fixed in =app-portage/porticron-0.7.1. Please re-open if needed.


possible api tweak for v1

While I love the simplicity of the current api, it runs into issues with certain formats of code.
If someone writes something like if (a<c), the usage of either innerHTML or textContent breaks down. There is no way (that I know of) to prevent the <c being parsed as a new node.
I have a few potential solutions...
The traditional <script type="x-shader/x-fragment" />:
<script id="my-shader" type="x-shader/x-fragment">
  ...SHADERCODE
</script>
<shader-doodle src="#my-shader"></shader-doodle>

This solution would create two attributes: raw and src. src could receive a url or an id selector, and raw would take a plain string (primarily for usage in js/react/vue).
A custom script tag <script is="shader-doodle-main" />:
<shader-doodle>
  <script is="shader-doodle-main">
    ...SHADERCODE
  </script>
</shader-doodle>

This would open up shader-doodle for more modular components for adding additional passes/uniforms/etc...
you could add more processing/channels like
<shader-doodle>
  <script is="shader-doodle-main">
    ...SHADERCODE
  </script>
  <script is="shader-doodle-pass" order="0">
    ...MORE
  </script>
  <script is="shader-doodle-pass" order="1">
    ...MORE
  </script>
  <shader-doodle-uniform val="..." type="..." name="..."></shader-doodle-uniform>
  <shader-doodle-texture src="..." type="..." name="..."></shader-doodle-texture>
</shader-doodle>

Or something along that line.
I would love to get opinions/thoughts.

Mmm... yes it's not ideal to mix so many languages. In https://github.com/patriciogonzalezvivo/glslCanvas is possible to load source through JS as text strings which don't bring up this kind of issues.

going to close for now, as right now we are moving forward with the more traditional <script type="x-shader/x-fragment" />, but can/will open back up if anyone ever comes across this issue and has more thoughts.


pre-commit is not ran in ci, resulting in possible commits that don't pass pre-commit

continuation of #3604 #3603
https://github.com/charliermarsh/ruff/blob/main/.github/workflows/ci.yaml doesn't contain an action to run pre-commit, so it only happens locally, and doesn't seem to be validated in ci.
There's two options for this, adding a job which runs pre-commit in ci, or installing https://pre-commit.ci on the repo (and perhaps adding configuration to change autoupdate)
Config will have to be added to skip the local hooks unless they aren't part of ci already.
I'm interested in adding the ci or pre-commit.ci config, for whichever route is chosen.

Yeah we're in kind of a weird state right now. Some people want pre-commit, so it exists, and there's a set of checks that only run on pre-commit right now, but candidly I don't use it at all, it's not part of the contributor guidelines or getting started, and I'm hesitant to make it something contributors have to install and run.
As long as it exists, though, we should at least validate it on CI, i.e., incorporate it into ci.yaml. We'll want to skip the steps that are already captured by our established CI workloads (I believe they're enumerated at the bottom already) -- I think those are all the local hooks anyway.

Would you rather implement it in CI or using the external plugin https://pre-commit.ci/ ?

I would rather implement it in CI.

Can I work on it?

I would like to implement this

Sorry, go ahead.


Decode URL pathname for opened file

Pull Request Description

Attempt to fix an issue where a project opened by double clicking does not URL decode the path to be opened.

Unable to properly test as I don't normally use Windows (file associations do not work on Linux as we use an AppImage for that platform.)

Important Notes
None
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[x] Unit tests have been written where possible.

@jdunkerley testing would be appreciated

Just tested on mine and it fixed the issue. Thanks


Blurry text

Describe the bug
Text is blurry and difficult to read
To Reproduce
To reproduce just run this code
import nodesnim

Window("Hello, world!")

build:
  - Scene scene:
    - Label hello:
      call:
        setSizeAnchor(1, 1)
        setTextAlign(0.5, 0.5, 0.5, 0.5)
        setText("Hello, world!")
        setBackgroundColor(Color(31, 45, 62))

addMainScene(scene)
windowLaunch()

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop

OS: Linux
DE: xfce
Nim: 1.6.0

Additional context
Ran using latest commit on nightly branch (#398858c)

Specifying a font seems to improve it

Which version of nodesnim are you using?
on Linux the standard_font is unifont.ttf from core folder

In future versions, I want to get rid of SDL dependencies and render text using OpenGL.

I am using the latest version of the nightly branch (398858c atm), have also tried using v0.4.2 and get the same result

maybe it helps https://github.com/Ethosa/nodesnim/blob/nightly/src/nodesnim/core/nodes_os.nim#L19-L33
https://github.com/Ethosa/nodesnim/commits/nightly


[6.x] roadmap

We should set some expectation on future development.
I must say, there will be BC breaks, it sure. But don't worry, we will try to make it more pleasant.
Changes:

Nette >=3.0 only
PHP >=7.3 only
change namespace Ublaboo -> Contributte
transfer dynamic doc on Github docs (to display it on https://contributte.org)
apply contributte's codestyle
apply phpstan
rewrite completely tests
merge datasources into single repository

https://github.com/contributte/datagrid-nette-database-data-source (>=3.0) [#748]
https://github.com/contributte/datagrid-leanmapper-data-source (>=3.3) [#751]
https://github.com/contributte/datagrid-elasticsearch-data-source [#928]
https://github.com/contributte/datagrid-dibi-data-source (>=4.0) [#749]
https://github.com/contributte/datagrid-doctrine-data-source (>=2.6) [#750]
https://github.com/contributte/datagrid-nextras-data-source (>=3.0) [#752]

refactoring

rename snake_case to camelCase

Awesome!.. Could you tag existing issues and create new ones describing what you need help with towards reaching v6?

@martingold I will try to ;-)

@martingold Better? :-)

I would really love it if tests are in phpunit which is far better supported. nette tester plugin for phpstorm is crashed for few months already...

@dakorpar nette/tester can be simply ran using command line interface. :) I would stick to nette/tester because of its simplicity.

@paveljanda sure you can, but having codecoverage directly in IDE is big plus plus right click and debugging selected test method is huge advantage and thats not possible woth nette tester... :)

Resolved, v7.0.0 roadmap here #1025


Issue with "WARNING: TypeScript < 1.8 does not allow....."

Hi,
I am trying to run grunt-ts on several files which I need to have concatenated at the end.
I have set the module to "amd" but I get the warning anyway!
I create a config by the following helper function.
function createTypeScriptBuild(outfile, sourceMap, genDeclaration, files) {
    var config = { files: [] };
    sourceMap = sourceMap || false;
    genDeclaration = genDeclaration || false;
    config.options = {
        compiler: './node_modules/typescript/bin/tsc',
        module: 'amd',
        inlineSourceMap: sourceMap,
        inlineSources: sourceMap,
        noImplicitAny: true,
        declaration: genDeclaration,
    };
    config.files.push({
        src: files,
        dest: outfile
    })
    return config;
}

Am i doing something wrong?

What version of TypeScript are you using and are you getting the expected result other than the warning?

I am using the following:
  "devDependencies": {
    "grunt": "^1.0.1",
    "grunt-contrib-clean": "^1.0.0",
    "grunt-sass": "^2.0.0",
    "grunt-ts": "^6.0.0-beta.11",
    "typescript": "^2.1.5"
  }

And it produces the correct result (for now at least)

The reason for this is that you're using a custom compiler.  I'm going to see if I can just not send the error in this case.  Thank you for the report!

Would you please test again with<EMAIL_ADDRESS>which has just been published?
Thank you.

Works like a charm. Thank you

Thank you for for the report!


[Snyk] Upgrade org.jodd:jodd-core from 3.5.2 to 3.9.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.jodd:jodd-core from 3.5.2 to 3.9.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 24 versions ahead of your current version.
The recommended version was released 6 years ago, on 2017-09-10.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Can one of the admins verify this patch?


Provider "libwindowsfidobridge.so" dlopen failed: Exec format error

I added the apt repository and am on Ubuntu 22.04 in WSL2, which has OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2.
I get an error message Provider "libwindowsfidobridge.so" dlopen failed: Exec format error when trying to use the fido bridge.

Got it to work, this must have been an error.


Fix for issue #317

Issue #, if available:
317
Description of changes:

in AwsHttpServletResponse#flushBuffer - charset was always taken from LambdaContainerHandler.getContainerConfig().getDefaultContentCharset(); even if characterEncoding and or headers.Content-Type contained ; charset=

updated Spring dependencies to address https://pivotal.io/security/cve-2020-5398

Note: com.amazonaws.serverless.proxy.spring.SecurityAppTest#helloRequest_withAuth_respondsWithSingleMessage succeeds on Spring Boot 2.1 but fails on 2.2 (-Dspringboot.version=2.2.3.RELEASE -Dspring.version=5.2.3.RELEASE -Dspringsecurity.version=5.2.2.RELEASE fails)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Tests of SpringBoot 2 are expected to fail for 2.0.x (enforcer plugin will complain) and 2.2.x (one unit test seems to fail probably due to the new Spring Security dependency version, needed due to https://pivotal.io/security/cve-2020-5398)

Issue link https://github.com/awslabs/aws-serverless-java-container/issues/317


Unify terminology

We have remove_peer and delete_device. Might want to unify terminology?
If it's some kind of convention then ignore me 😅

I was following the terminology used in the lower level library wireguard-control and the subcommand remove for the wg utility.

All good then!


Expo SDK44 - @expo/bugsnag using expo-constants "~12.1.3" breaks build

Describe the bug
With<EMAIL_ADDRESS>it is impossible to build the app because of incorrect expo-modules-core used by expo-constants "~12.1.3"
Please update @bugsnag/expo for SDK44 using "expo-constants": "~13.0.0", this will remove dependency on<EMAIL_ADDRESS>Steps to reproduce
after npx bugsnag-expo-cli init
Yarn.lock contains :
"<EMAIL_ADDRESS>  version "7.14.1"
  resolved<EMAIL_ADDRESS>  integrity sha512-QqrB8c6dipxfhRxoYkN7oIXsvFBuykHcErntakWpZX6FFV+bJHOAK4Ijqg3ICP1UjseBvaicFoWEzaxzJYHrKw==
  dependencies:
    "@bugsnag/core" "^7.14.0"
    "@bugsnag/delivery-expo" "^7.14.0"
    "@bugsnag/plugin-browser-session" "^7.14.0"
    "@bugsnag/plugin-console-breadcrumbs" "^7.14.0"
    "@bugsnag/plugin-expo-app" "^7.14.0"
    "@bugsnag/plugin-expo-device" "^7.14.0"
    "@bugsnag/plugin-network-breadcrumbs" "^7.14.1"
    "@bugsnag/plugin-react" "^7.14.0"
    "@bugsnag/plugin-react-native-app-state-breadcrumbs" "^7.14.0"
    "@bugsnag/plugin-react-native-connectivity-breadcrumbs" "^7.14.0"
    "@bugsnag/plugin-react-native-global-error-handler" "^7.14.0"
    "@bugsnag/plugin-react-native-orientation-breadcrumbs" "^7.14.0"
    "@bugsnag/plugin-react-native-unhandled-rejection" "^7.14.0"
    "@bugsnag/source-maps" "^1.0.1"
    bugsnag-build-reporter "^1.0.1"
    expo-constants "~12.1.3"

I had to remove @bugsnag/expo package from the build which is not good ;)

As a workaround, until you solve this issue, Expo's team member @tsapeta suggested adding a 'resolutions' item in package.json :
"resolutions": {
  "**/expo-constants": "~13.0.0"
}

I didn't test this as I removed bugsnag until the issue is solved.

Hey @lc3t35, Expo SDK 44 is not yet supported. But we'll keep you posted here when support for Expo SDK 44 is added.

Any timeline in when SDK44 will be supported?

Expo SDK v44 is now supported in the latest release v7.15.0

Release v7.15.0 encountered an issue, and was patched in https://github.com/bugsnag/bugsnag-js/releases/tag/v7.15.1, please use this release instead 😄


Provision a cloud instance creates more instances than the count that was set

When attempting to provision an instance in a cloud provider (in my case it was OpenStack). I observed duplicate instances created when I only specified 1 as the instance count. I am using the docker image based on the main website documentation: manageiq/manageiq:gaprindashvili-2. I was able to reproduce the same problem performing the provision request by REST API and the GUI.
Steps to reproduce the problem:

Start new container:
$ sudo docker run --privileged -d -p 8443:443 manageiq/manageiq:gaprindashvili-2

Add cloud provider (OpenStack in my case)

Provision an instance through the GUI:

Navigate to instances page Compute > Clouds > Instances
Select to provision instances Lifecycle > Provision Instances
Select image to provision based on
Fill in the following fields:

E-Mail
Count = 1
Instance Name
Cloud Tenant
Availability Zones
Cloud Network
Security Groups
Instance Type
Guest Access Key Pair

Then submit the provision instance request. Shortly after ManageIQ begins processing the request. You can see from the actual provider itself two instances being created with the same name you define in the provision instance request.
I checked the request details Services > Requests and it says my request has finished and Provisioned VMs is 1.
Has anyone else observed this behavior in this release of ManageIQ? Previously when using the tag fine-4, I was not seeing this behavior.

The same issue affects also gaprindashvili-1. Networks are being duplicated as well but for example flavors are created correctly.

So the issue exists only when running ManageIQ from docker image. OpenStack OVA and Vagrant image are running correctly and no duplicated instances are created.


Enable ports 5900-5999 for HTML5 console

Removed the firewall command in favor of opening
ports in the post section.
The kickstart firewall command was adding the ports
to the default zone which is "public" at the time the
main section runs.
We later create the "manageiq" zone and set that to the
default causing the ports to still be closed in the active
zone.
https://bugzilla.redhat.com/show_bug.cgi?id=1278432

@abellotti @gtanzillo @martinpovolny

:+1: LGTM


QueryManager error: listener is not a function

I've talked/worked through part of this -- after posting a gist -- with @stubailo
Encountering the following error during query execution:
(program):12 TypeError: listener is not a function
    at eval (eval at <anonymous> (main.js:3742), <anonymous>:300:13)
    at eval (eval at <anonymous> (main.js:5308), <anonymous>:40:11)
    at baseForOwn (eval at <anonymous> (main.js:5332), <anonymous>:22:20)
    at forOwn (eval at <anonymous> (main.js:5332), <anonymous>:54:20)
    at QueryManager.broadcastQueries (eval at <anonymous> (main.js:3742), <anonymous>:297:7)
    at Array.eval (eval at <anonymous> (main.js:3742), <anonymous>:53:23)
    at dispatch (eval at <anonymous> (main.js:3640), <anonymous>:180:19)
    at Object.eval [as dispatch] (eval at <anonymous> (main.js:4108), <anonymous>:8:16)
    at Object.dispatch (<anonymous>:1289:344)
    at eval (eval at <anonymous> (main.js:3742), <anonymous>:231:29)

After inserting some console.log entries QueryManager.js:
    QueryManager.prototype.broadcastQueries = function () {
      var queries = this.getApolloState().queries;
      console.log({listeners: this.queryListeners, queries: queries});
      forOwn(this.queryListeners, function (listener, queryId) {
            console.log('queryId', queryId);
            var queryStoreValue = queries[queryId];
            listener(queryStoreValue);
        });
    };

I notice that listeners and queries both have keys for query IDs 0 and 6 -- but, where the queryId is logged, an additional query ID, 4 is output.
Checking further up the console log (and checking redux dev tools), I do see a APOLLO_QUERY_STOP for query ID 4.

Confirmed that guarding the listener invocation with if (listener) { ... } fixes my application issue, so this appears to be (from a layman's view) some housecleaning debris that just needs to be cleaned up.

I've verified interleaving of stopQuery() and broadcastQueries() that's seemingly leading to a race condition. Logging at the beginning and ending of each function (and which query IDs are present on this.queryListeners), I'm seeing:
BEGIN: broadcastQueries()
- this.queryListeners has queryId = 0 with a listener
BEGIN: stopQuery() with queryId = 2
BEGIN: broadcastQueries()
- this.queryListeners has queryId = 0 with a listener
END: broadcastQueries()
END: stopQuery() with queryId = 2
BEGIN: startQuery()
BEGIN: broadcastQueries()
- this.queryListeners has queryId = 0 with a listener
- this.queryListeners has queryId = 4 with a listener
END: broadcastQueries()
BEGIN: broadcastQueries()
- this.queryListeners has queryId = 0 with a listener
- this.queryListeners has queryId = 4 with a listener
END: broadcastQueries()
END: startQuery()
- this.queryListeners has queryId = 2 WITHOUT a listener (listener is undefined).
(ERROR)

Interestingly, it seems the use of forOwn is the problem. This code works perfectly fine:
for (var queryId in this.queryListeners) {
  if (this.queryListeners.hasOwnProperty(queryId)) {
    var queryStoreValue = queries[queryId];
    var listener = this.queryListeners[queryId];
    listener(queryStoreValue);
  }
}

It appears the forOwn use of a callback function, being asynchronously executed, causes the issue.
I would happily provide a PR that either:

Explicitly checks listener and retains the use of forOwn
Removes the use of forOwn and uses for (var in ...) { ... }

I would guess, based on the use of forOwn elsewhere, that the first option is likely the best choice.

Thank you for identifying the issue and adding the PR!

Published the fix in 0.3.10!


fix: udpate deps

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

v1.79.3
GitHub release

Your semantic-release bot :package::rocket:


As a host, I want to make sure that each participant can only submit one Answer-Set

Once-per-Squeak-Image


Add pluginmachinery k8s KubeClient

Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

@kumare3 yup that's the idea.


Add some more classes to whitelists, fix getters/setters on others.

Pushed a fix for the jdbc issue

LGTM, merging.

Squashed, rebased and merged as 17e37d17d32de73295292ccb27e55e6cdbe49780 along with the changes to include Redis Pool/Sentinel properties into whitelist properties dd6447a9934a098b3e2c49a41d5a8a5c5ac30747


Sprint 1

Skill
Mastered (Y/N)
Link
Notes

Laptop Verification or Cloud Workspace
Y
Link
verification by Linux commands notebook

VSCode
Y
Link
live change code, commit, make, run localhost, test, debug

Show VSCode GitLens
Y
Link
verify commits, show change, comments, reset to commit, run on old commit

GitHub student_2025 repo
Y
Link
template create, push changes, verify id, review analytics

GitHub Pages Actions
Y
Link
review runs and verify runtime, receive demo

Hacks Tools & Equipment Play
Y
Link
Hacks

Hacks GitHub Pages Playground
Y
Link
Hacks

Hacks SASS Basics
Y
Link
Hacks

Hacks Frontend
Y
Link
Hacks

Pair Programming
Y
Link
tangibles that show coop work

Fun presentations.   A little more balance on machine, your was used less.   90% plus on creativity in project.


Versioning | Link version number in TFRS to release repo in Github |1|

https://trello.com/c/fLA6qoHp/706-versioning-link-release-number-in-tfrs-to-releases-in-github

 Versioning | Link version number in TFRS to release repo in Github |1|


I can't manipulate the instance with 'init:false'

After several tries, I'm stuck on a problem:
I can't manipulate the instance after initializing my swiper with “init:false”.
If I go back to the examples, I can use my 'swiper.prev' and 'swiper.next' buttons in this example:
`

`
But they no longer work in this one:
`

`
Is it a bug? Or am I doing something wrong?

@RemyAlbanes Can you supply a stackblitz example for me to debug?
Thanks!

@RemyAlbanes This actually might be related to this PR #140. I will have to double check the code, but this could be due to it returning the computed instance of the swiper, I will take a look here soon.
Thank you!


PCL installation fails post-build validation

OS Name: Microsoft Windows 10 Pro
Version: 10.0.16299 Build 16299
System Type: x64-based PC
Package: pcl:x64-windows
Vcpkg version: 0.0.105-2018-03-08-965e99cf268b32cc32e0599d99e6c9a1991e95f4
Issuing vcpkg install pcl[qt,tools,cuda] --head
the following error occurs:
/debug/share should not exist. Please reorganize any important files, then use
    file(REMOVE_RECURSE ${CURRENT_PACKAGES_DIR}/debug/share)
Found 1 error(s). Please correct the portfile:
    C:\Users\<user>\vcpkg\ports\pcl\portfile.cmake
-- Performing post-build validation done
Error: Building package pcl:x64-windows failed with: POST_BUILD_CHECKS_FAILED

Trying to fix it.

This change is probably the cause of error, as correctly reported by the error log.

Thanks again!


Camel 2.19.x

CAMEL-11668: CompositeApiClient class in the camel-salesforces component cannot close a null InputStream

This PR is probably based on 2.19.x branch. We use master branch and backport if needed. Could you please close and renew your PR?

I thought this is what I tried. The PR is for 2.19.x branch. I can't seem to open a PR on the master branch. Does this PR help to fix the issue?

You can open PR against 2.19.x. In that case, it may require forward porting. This is not what we usually do, we always first go to master branch for any fix, feature / other implementation and cherry-pick to other branches if it seems relevant to backport.

So do i just reopen my current PR? because this is opened on 2.19.x right? Or did I get that wrong?

this is opened against master branch and it is already probably based on 2.19.x. Nobody can easily review and approve your changes.

Thanks for the quick replies and help "onders86". This is me first contribution to the apache camel community. Thats why I have soo many questions.  I have created a fork of the master branch now and made my patch on the 2.19.x branch. Now I will create the PR on the master branch from my clone. I believe this is what is expected right?

not a problem. As far as i can, i will help you.
yes, that's right.


Include and exclude globs cause all files to be ignored in backup

I'm trying to exclude some directories from my backup, and using globs to do so per this discussion
Using any include glob causes every single file to be ignored in the backup, but leaves directories. It will report Files:       0 new, 0 changed, 0 unchanged and the resulting snapshot reports 0 files, however many dirs it found, and 0 bytes size.
The behavior does not depend on the order of the globs.
 But some games store their saves next to them, so they need to be backed up. The behavior I expect is that explictly providing a path later in the list will "override" or "inject" it, ignoring the exclusion. I explictly put it there, after all.
Writing this I've realized that adding it as an entirely separate backup source kind of achieves this, but then as i understand it, it would create a ton of disconnect snapshots for all the different paths and generally be rather annoying and unwieldy, as well as very verbose?

config
[[backup.sources]]
source = "/some/path"
glob = [
    "!/some/path/to/exclude",

"/some/path/to/exclude/some/exception",

# Or

    "/some/exception",
]

System
rustic 0.5.4
6.3.9-arch1-1

It seems that include glob is not working at all... when I configure it no files are backed up.

@DianaNites Sorry for the late answer - I somehow delayed the answer as I intended to start an effort about how to generally improve including/excluding. But then that topic got out of sight.
I think that a glob like this will work in your case:
glob = [
"/some/path/to/exclude",
"!/some/path/to/exclude/**",
"/some/path/to/exclude/some/exception",
]
The problem is, if you exclude the complete /some/path/to/exclude/, it won't be even traversed and therefore your include pattern isn't even applied.
But I agree that this is absolutely not user-friendly, so I think we have to do something about this!

@cactushydrocodone Thanks a lot for your analyis! I think you are right and using the OverrideBuilder with / obviously wasn't a good idea!
I'll add a PR to change this.


arch: kconfig: Set flash size/address to 0 by default when !XIP

Many boards/SoCs in-tree do this:
if !XIP
config FLASH_SIZE
    default 0
config FLASH_BASE_ADDRESS
    default 0
endif

And many other boards are missing this configuration (e.g. stm32 series).
Making this the default helps get non-XIP just working
ref: #72307

What are the failures? If there is no flash, there is no need to specify these kconfigs. Some flash do have address starting at 0x00000000 so it should not be considered an invalid config.

What are the failures? If there is no flash, there is no need to specify these kconfigs. Some flash do have address starting at 0x00000000 so it should not be considered an invalid config.

The failure outputs an obscure error message e.g:
west build -b nucleo_f756zg zephyr/samples/hello_world -DCONFIG_XIP=n
...
/tmp/cc2CISlB.s: Assembler messages:
/tmp/cc2CISlB.s:49: Error: missing expression
/tmp/cc2CISlB.s:55: Error: missing expression

as these configs exist with no value.
These configs are used in common C files and linker scripts, so they need to be defined e.g:
#if !defined(CONFIG_XIP) && (CONFIG_FLASH_SIZE == 0)
#define ROM_ADDR RAM_ADDR
#else

@gramsay0 Would you mind adding the related clean-up from boards/socs configurations ?

In that case, maybe just make flash size default to 0, and leave the address untouched?

In that case, maybe just make flash size default to 0, and leave the address untouched?

Integer configs need a value, otherwise you get an error during prebuild.
We could make config FLASH_BASE_ADDRESS depends on FLASH_SIZE > 0, although that would require a larger refactor (there is ~120 uses of FLASH_BASE_ADDRESS in-tree) and likely break some out-of-tree apps/boards


use __declspec for visibility on mingw

Reference answer: https://stackoverflow.com/a/9939664/2676533
Related issue: https://github.com/recp/AssetKit/issues/27

Mingw complains about visibility attribute only in src/ds/default/default.c:24
deps\ds\src\default\default.c:28:1: error: visibility attribute not supported in this configuration; ignored [-Werror=attributes]

No _MSC_VER does not mean linux thing missed at src/utils.c:72 where st_blksize is st_size on mingw.
src\utils.c:72:23: error: 'struct stat' has no member named 'st_blksize'; did you mean 'st_size'?
   72 |   blksize = infile_st.st_blksize;
      |                       ^~~~~~~~~~
      |                       st_size

And a lot of _MSC_VER defines in src/mmap.c and incorrect mmap functinons/defs.
src\mem\mmap.c:20:12: fatal error: sys/mman.h: No such file or directory
   20 | #  include <sys/mman.h>
      |            ^~~~~~~~~~~~

If I hand fix these defines everything builds.

Shared build works much better, but it fails at final linking stage:
objects.a(utils.c.obj):utils.c:(.text+0x206): undefined reference to `strptime'
collect2.exe: error: ld returned 1 exit status
CMakeFiles\assetkit.dir\build.make:2768: recipe for target 'libassetkit.dll' failed
mingw32-make[2]: *** [libassetkit.dll] Error 1
CMakeFiles\Makefile2:662: recipe for target 'CMakeFiles/assetkit.dir/all' failed
mingw32-make[1]: *** [CMakeFiles/assetkit.dir/all] Error 2
Makefile:154: recipe for target 'all' failed
mingw32-make: *** [all] Error 2

By some reason it did not build and/or link strptime

Mingw complains about visibility attribute only in src/ds/default/default.c:24

I added this chage to libds too:
#if defined(_MSC_VER) || defined(__MINGW32__) || defined(__MINGW64__)
#  ifdef DS_STATIC
#    define DS_EXPORT
#  elif defined(DS_EXPORTS)
#    define DS_EXPORT __declspec(dllexport)
#  else
#    define DS_EXPORT __declspec(dllimport)
#  endif
#  define DS_HIDE
#else
#  define DS_EXPORT  __attribute__((visibility("default")))
#  define DS_HIDE    __attribute__((visibility("hidden")))
#endif

it now must be work.

And a lot of _MSC_VER defines in src/mmap.c and incorrect mmap functions/defs.

There are lot of _MSC_VER usages, maybe we can define it as:
#if defined(_MSC_VER) || defined(__MINGW32__) || defined(__MINGW64__)
#  define AK_COMPILER_MSC
#endif

/* ad use AK_COMPILER_MSC instead of  _MSC_VER in all places */

#if AK_COMPILER_MSC
...
#endif

but I'm not sure if it is the right path to go

Also to note it does not include strptime in static build so you also have to include the strptime.c file into the project.

But I have checked CI and it seemed like it broke msvc or something?

Let me pull the changes and see what kind of results I get.

There's still that util.c error complaining about struct stat
\src\utils.c: In function '[ 20%] ak_readfileBuilding C object CMakeFiles/assetkit.dir/src/bbox/mesh_prim.c.obj                                                                                ':                                                                                D:\!Development\AssetKit\src\utils.c:72:23: error: 'struct stat' has no member named 'st_blksize'; did you mean 'st_siz '?                                                                                72 |   blksize = infile_st.st_blksize;                                                                                |                       ^~~~~~~~~~                                                                                |                       [ 20%] st_size

Pretty much AK_COMPILER_MSC would work apart from the src/utils.c somehow having a different struct member name.
Only the util.c and mmap.c have old defs.

So then at src/utils.c:71 it should be:
#ifndef AK_COMPILER_MSC
  #ifndef _MSC_VER
    blksize = infile_st.st_size;
  #else
    blksize = infine_st.st_blksize;
  #endif
#else
  blksize = 512;
#endif

And at src/mem/mmap.c:19 it should be:
#ifndef AK_COMPILER_MSC
#  include <sys/mman.h>
#else
#  define WIN32_LEAN_AND_MEAN
#  include <windows.h>
#  include <io.h>
#endif

What about this commit: https://github.com/recp/AssetKit/pull/29/commits/2996c5df74638894b563d5e6531c40b41fa3385a ?

By some reason it did not build and/or link strptime

Let me check

We must include src/win32/ folder into build it is mingw

@eLeCtrOssSnake can you pull and try again please?

Trying out.

blksize = infile_st.st_blksize in mingw must be blksize = infile_st.st_size or 512. No such property st_blksize

It passed on my Windows with mingw, no compiling errors?

Did you pull the PR with newest commits?

Woopsie, I messed up the stash. Yes, it compiles properly now. Seems like the mingw build is good. Checked msvc build just in case, also built fine.

@eLeCtrOssSnake many thanks for help. I'll try to update morph targets and material system asap... Feel free to bring any other issues by creating issue/pr...

@eLeCtrOssSnake many thanks for help. I'll try to update morph targets and material system asap... Feel free to bring any other issues by creating issue/pr...

Yes, I will be watching AssetKit closely, because I want to migrate my engine to it and stop using assimp.
I'd want to chat with you in private. I wrote an email but you did not respond @recp. Can I get in touch with you outside github?

I want to migrate my engine

great to hear that!
With this repo (https://github.com/recp/assetkit-gl) I integrated AssetKit to my render engine, you may check it how to use AssetKit (until docs are finished) or you can use it another way maybe...  But it may be updated in the future and I'm considering to integrate AssetKit, my render engine[s], physics engine... in a engine called Universal Engine which is private for now but it may be public in the future, it that case assetkit-gl may become obsolete or stay as another library maybe...

I wrote an email but you did not respond @recp. Can I get in touch with you outside github?

I didn't check emails last days I guess, I'll do that later... but it is better to continue onn Github which may help to others' issues...

I obviously keep stuff that has public value. It's obviously something I wouldn't like to disclose or leave here.

I'll check mails later, sorry for the delay then


Enforce error diagnostics by aborting execution

Motivation

Fixes https://github.com/apple/swift-openapi-generator/issues/180

Modifications

Create ErrorThrowingDiagnosticCollector wrapper collector.

Result

The ErrorThrowingDiagnosticCollector throws an error when a diagnostic with severity .error is emited.

Test Plan

Make sure all tests pass and add additional test.

I have a question because I'm a bit confused about what to do after the creation of the wrapper. Should we use the wrapper in place of the extensions from DiagnosticCollector?

I think DiagnosticCollector's emit method should become throwing, and then create a new concrete collector implementation that looks something like this:
struct ErrorThrowingDiagnosticCollector: DiagnosticCollector {
    var upstream: any DiagnosticCollector

    func emit(_ diagnostic: Diagnostic) throws {
        upstream.emit(diagnostic)
        if diagnostic.severity == .error { throw diagnostic }
    }
}

And then use this collector by default, wrapping today's collector.

I think DiagnosticCollector's emit method should become throwing, and then create a new concrete collector implementation that looks something like this:
struct ErrorThrowingDiagnosticCollector: DiagnosticCollector {
    var upstream: any DiagnosticCollector

    func emit(_ diagnostic: Diagnostic) throws {
        upstream.emit(diagnostic)
        if diagnostic.severity == .error { throw diagnostic }
    }
}

And then use this collector by default, wrapping today's collector.

It makes sense, perfect!!

@swift-server-bot test this please

Ok the code looks good, would you be able to add one test that constructs the pipeline with a malformed input and ends up throwing the error? Just to verify that it's really working?

Sure.

@swift-server-bot test this please

Got some build failures on Linux:
/code/Tests/OpenAPIGeneratorTests/Test_GenerateOptions.swift:38:34: error: cannot call value of non-function type 'String'
        let arguments = [docPath.path(), "--config", configPath.path]
                                 ^   ~~

/code/Tests/OpenAPIGeneratorTests/Test_GenerateOptions.swift:42:94: error: 'nil' requires a contextual type
            try await generator.runGenerator(outputDirectory: outputDirectory, pluginSource: nil, isDryRun: false)

You can fix the first one by using docPath.path (the property) instead. For the second, just pass the "build plugin" plugin source case.

@swift-server-bot test this please

** Running /code/scripts/check-license-headers.sh...
** ERROR: Unsupported file extension for file (exclude or update this script): Tests/OpenAPIGeneratorTests/Resources/Docs/malformed-openapi.yaml

You'll need to add the file to the license check ignore list.

Hmm this actually breaks 5.9.0, because it creates a dependency of a test target on an executable target. https://ci.swiftserver.group/job/swift-openapi-generator-swift590-prb/246/console
To fix this, you'll need to start depending on _OpenAPIGeneratorCore instead of swift-openapi-generator, and move _YamlFileDiagnosticsCollector to _OpenAPIGeneratorCore, and create a method called e.g. preparedDiagnosticsCollector(...) -> DiagnosticCollector & Sendable that lives in _OpenAPIGeneratorCore. Then just test that method, and call the method from the swift-openapi-generator code.
I don't think we'll be able to make the new dependency work otherwise.

@swift-server-bot test this please

@swift-server-bot test this please

@swift-server-bot test this please

@PARAIPAN9 The CI is happy, but I believe we still need to move the remaining diagnostic collection code into the new prepare... function, so that it's called from the CLI and also from tests. Right now we're still re-creating the collectors using different code in the CLI vs the tests.


Refactor Mistral to use PostgreSQL instead of MySQL

This also needs a corresponding change in workroom.

Are we sure about this change? I don't think we should be changing anyones /etc/hosts without notifying them - if I have some terrible reason for this configuration I would hate it if some deploy script went in an changed things!

st2_deploy.sh is designed for standalone deployments for testing/POC purposes.  I don't have a problem with us ensuring that the localhost entry we are looking for exists on these boxes.  Now if we were doing this as part of a package install it would be a different story...but this all in one installer isn't designed to be dropped in to a production environment.


Flink scripts. Documentation or CR retrieval

I think it would be useful to have some explanation on how data is retrieved from the Cloudflow CR and the configuration.
As I understand the scripts work in two ways they read and then write. They read the current deployment from the CR and config from ConfigMaps.  Based on that then they create a deployment to be executed with Flink CLI. The write side is Flink-related and requires reading Flink docs but not the read side.
I think there is value in making explicit through documentation how and what needs to be read from the Cloudflow CR and the configuration to learn what needs to be deployed.

Make it so @franciscolopezsancho ! 😆


osm2streets cutover

#71, about cutting A/B Street over to using osm2lanes, kind of died off. I wanted to start fresh here based on new goals and problems. Since the last update there, we successfully detangled the overall OSM import and geometry logic out of A/B Street into https://github.com/a-b-street/osm2streets. It has a standalone web UI, its own unit tests, etc and is no longer tied to A/B Street. A/B Street directly depends on it. That's the same thing we want to achieve with osm2lanes, but now the integration is a bit more focused -- osm2streets will depend on osm2lanes. A/B Street will depend on osm2streets, and osm2lanes is an implementation detail one layer in.
Goal
osm2streets is still using the original lane_specs parsing code. In the short-term (next few weeks), I want to start adding a lane type for shared walking/cycling paths, fix bugs like this and many of the others filed in this repo, and handle lanes with explicitly tagged widths. I do not want to invest further in the monolithic lane_specs.rs; I want to cutover to osm2lanes.
Problems
When I've tried to jump in and work on osm2lanes for some of these things, it's felt like the codebase is very complex, even though I've been reviewing all the changes.
Error handling / permissiveness
cargo run way 260912073 fails outright because sidewalk=none is deprecated. I think we need to rethink how strict we are, maybe using something like taginfo popularity to guide decisions. Any pushback against treating this as a warning but otherwise proceeding?
Alternatively, there can be an optional layer in osm2lanes that preprocesses tags and corrects common mistakes. Some examples in https://github.com/a-b-street/abstreet/blob/f0f13bc50aac28cf0f41d960602258ddfb61a566/raw_map/src/lane_specs.rs#L135 -- not the ones involving directions and such, or sidewalk inference.
Adding a test
osm2streets progress has happened quickly because of being able to iterate very quickly with tests. The table-driven tests in the original code were very quick to crank out:
            (
                "https://www.openstreetmap.org/way/49207928",
                vec!["cycleway:right=lane", "sidewalk=both"],
                DrivingSide::Left,
                "sddbs",
                "^^vvv",
            ),

The last time I attempted to add an osm2lanes test, I was a bit overwhelmed by having to figure out the locale and write out the full JSON (with separators or not?). Some ideas for making this experience easier:

Add something to the web app to export as a copy-pasteable test case template
Maybe make a tiny tool to transform the "sddb" + "^^vv" notation into full JSON, and also use that to copy into the yaml. It's easier to type.
Maybe split the test yaml by how much we want to assert. Most test cases don't need to specify separators or width in the output. We can start a different file where we include those in the expected output and enforce that.

If the drag-and-drop UI worked, we could also use that to quickly specify the expectation and copy it into the YAML.
Matching up lanes
osm2streets still uses the old LaneType enum. It'd be nice to use osm2lanes' representation directly at some point, but this is out of scope for now. One major change that has to happen in osm2streets and beyond is properly modelling Direction = Both or Direction = None. Until then, bidi lanes will get split into two directional lanes.
Some of that logic is https://github.com/a-b-street/abstreet/blob/f0f13bc50aac28cf0f41d960602258ddfb61a566/raw_map/src/lane_specs.rs#L238. Since it's non-trivial, I think it makes sense for osm2streets unit tests to also include the translated lane config in the expectation. I will probably add that as a preliminary step.
Rough plan
Because of the way work is going right now, I get the most done when I quickly crank out code in a few days. What I would work on is:

fixing the above test issues, making it much easier to quickly iterate
getting parity with the current implementation. Maybe that means turning errors into warnings, or adding an optional layer to "fix" common tagging issues that happen in the real world.
a cutover
then fixing reported bugs and starting on things like lane widths

Any feedback, @droogmic and @BudgieInWA? When I go rapid-fire mode and start this, do you want me to wait for reviews on PRs, or would y'all be OK leaving feedback whenever is convenient and I'll address it later? (If the former, I'll probably send bigger PRs to reduce communication latency)

As far as deprecated tags go, I think we should aim to support incorrect tags that are easy to support, like sidewalk=none. This need for preprocessing to normalise tags is one of the biggest benefits of the schemes we've been implementing, I think. If the raw tags are only used to generate schemes, then it becomes much easier to support a variety of tags for the same meaning.
Providing PR feedback after merge works fine for me.


DefectDojo cannot parse imported MobSF Scan

Bug description
DefectDojo is having issues parsing a MobSF scan when trying to import its JSON file into an Engagement. This is occurring after the latest MobSF update (version 3.1.7)
Steps to reproduce
Steps to reproduce the behavior:

Grab MobSF scan as a JSON file
Go to an Engagement and click Import Scan Results
Scroll down to Choose report file and upload MobSF scan
See error

Expected behavior
A successful scan import, DefectDojo parses the scan and properly displays findings.
Deployment method (select with an X)

[ ] Kubernetes
[X] Docker
[ ] setup.bash / legacy-setup.bash

Environment information

Operating System: macOS Catalina 10.15.4

Sample scan file
mobsf-scan.zip
Screenshots

can you provide the error/tracback from the log please?

logs from running docker logs --since=2m --details django-defectdojo_celeryworker_1
upload took place at the last two timestamps shown below:
[2020-11-02 16:52:00,964: INFO/MainProcess] Received task: dojo.tasks.async_dupe_delete[99045c38-b9a3-40ce-b8cc-52340aed3fc4]
[2020-11-02 16:52:00,971: INFO/MainProcess] Task dojo.tasks.async_dupe_delete[99045c38-b9a3-40ce-b8cc-52340aed3fc4] succeeded in 0.006090350914746523s: None
[2020-11-02 16:53:01,014: INFO/MainProcess] Received task: dojo.tasks.async_dupe_delete[ae123cc4-ed07-4a1a-a9c9-802ca8963cdd]
[2020-11-02 16:53:01,021: INFO/MainProcess] Task dojo.tasks.async_dupe_delete[ae123cc4-ed07-4a1a-a9c9-802ca8963cdd] succeeded in 0.005998729029670358s: None

we need logs from uwsgi container

I ran docker logs --since=2m django-defectdojo_uwsgi_1 but there was no output, any other suggestions?

I tried it again and got some output, here it is:
'title'
 Traceback (most recent call last):
   File "./dojo/engagement/views.py", line 624, in import_scan_results
     parser = import_parser_factory(file, t, active, verified)
   File "./dojo/tools/factory.py", line 195, in import_parser_factory
     parser = MobSFParser(file, test)
   File "./dojo/tools/mobsf/parser.py", line 124, in __init__
     "title": details["title"],
 KeyError: 'title'
 Error in parser: 'title'

the same issue:
version 1.10.0
Deployment method (select with an X)
Kubernetes
x Docker
setup.bash / legacy-setup.bash
Operating System: Ubuntu 20
report.json.zip
log:
uwsgi_1         | [26/Nov/2020 18:28:24] ERROR [dojo:635] 'title'
uwsgi_1         | Traceback (most recent call last):
uwsgi_1         |   File "./dojo/engagement/views.py", line 628, in import_scan_results
uwsgi_1         |     parser = import_parser_factory(file, t, active, verified)
uwsgi_1         |   File "./dojo/tools/factory.py", line 198, in import_parser_factory
uwsgi_1         |     parser = MobSFParser(file, test)
uwsgi_1         |   File "./dojo/tools/mobsf/parser.py", line 124, in __init__
uwsgi_1         |     "title": details["title"],
uwsgi_1         | KeyError: 'title'
uwsgi_1         | [26/Nov/2020 18:28:24] ERROR [dojo:636] Error in parser: 'title'

Same pb here. I think the format of MobSF had changed a little bit.
It's the binary analysis part of the report that is broken.
I'm working on a patch to fix that. @Ivanello @jayala-29

@jayala-29 is this specific error now resolved for you?

@valentijnscholten no, the parsing error is still showing up

@valentijnscholten no, the parsing error is still showing up

@jayala-29 is this specific error now resolved for you (in dev)?

hello, sorry cant understand how to install dev version of Defectdojo?

@jayala-29 is this specific error now resolved for you (in dev)?

hello, sorry cant understand how to install dev version of Defectdojo?

Still don't work in latest DefectDojo version with any MobSF version. Please, support at least one, maybe old version of MobSF.

@whitespots please help to describe and make issues more clear. if there is new bugs with new versions of MobSF just create a new issue with details. I will work on it but it's difficult to follow this kind of "don't work" feedback.
We have an opportunity. Next week we will release our new 0.14.0 release. So if you're able to point to the pb or share with us some reports that break the import, we can fix it for the next release and have it ready before next Tuesday.

@damiencarol Thank you for your response! We will describe this issue as soon as possible.


Add -no-pull option to autoupdate

Without this option, autoupdate will panic if the "cdnjs" directory
isn't a git repository, in addition, it is overkill to pull if the repo
was just cloned, and it can take a long time as the cdnjs repo is very
big.

Thanks for adding this flag 😄

@klausenbusk the git repo will need to go away eventually. Instead of adding flags for each git operations could we add a -no-git flag? also worth updateing the dev docs in the README. (sorry I can't invite you on slack, if you need anything feel free to reach out: sven at cloudflare com)


Is there any way to get unreleased PR's?

Is it possible to get all PR's from the latest release tag to now?
I tried to use the commit sha from the latest release to the current commit sha but with no luck. Is there any way this can be achieved?
Thank you!

Hi @lucasgismondi-bitbuy
Thank you very much for the ticket.
Currently this action is focusing around merged PRs.
Could you may outline a bit on your usecase to understand better on this ask?

Hey @mikepenz, thanks for the reply.
Within our changelog we are looking to include PR's that are "unreleased" so that our QA and other internal teams can know exactly what is coming up and what has already been released to production

That's an interesting usecase.
You outline the toTag to have no bound, but given the note you'd still like to have those in a unreleased section. would those be meant to follow a similar categorisation, or could it be a plain unreleased section with everything listed? Filtered by some label?
It's an interesting feature proposal, and I believe it could add further value to the action.

Yes, I would expect it to follow a similar categorization. If it can get a list of PR's that are "unreleased" then it should be able to read the labels on those PR's and sort them accordingly. I'm not sure if that is actually possible though on the actions side but that is what I would expect. If it's just easier to have a plain unreleased section with everything listed, that is still a viable solution.
Yeah, I think it's super interesting as well. It can help make the changelog the single source of truth instead of relying on other ticket management tools that require more manual work to keep things organized.

@lucasgismondi-bitbuy if you could please have a look at the following PR and maybe see if it matches your requirements: \

https://github.com/mikepenz/release-changelog-builder-action/pull/726
(at the time of writing docs are not yet updated, but I hope the testcases added can be a good starting point)

@lucasgismondi-bitbuy as before those should be included if you use the latest commit on the branch those were merged into up until the tag which you want to use as fromTag.

In a strongly simplified fashion the following should outline your usecase.

If you look at the config it refers the hash instead the tag.
and 1 open PR.
using a special tag --rcba-open to add additional flexibility when configuring the sections you may want.

So my workflow step looks like this at the moment:
- name: Build Changelog
        id: build_changelog
        uses: mikepenz/release-changelog-builder-action@v1
        with:
          fromTag: "3.77.0"
          toTag: "${{ github.sha }}"
          configuration: "changelog_config.json"
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

I also tried referencing an existing hash manually and I also tried using "v3.77.0" for the fromTag but I'm getting this:

Any ideas as to why this may be failing?

Could it be that the TOKEN is invalid?
Also it looks you are using v1 while we are already at v2.9.0 and the specific branch created for you with the new feature would have the SHA-1 (df9a35580f26de56d97c703c0505929f31b4693b - which you can use as version spec)

The token is definitely valid since it works very well between two releases. I tried using 2.9.0 and the new branch sha but neither of those worked. But before this PR was created, was it expected that you can get merged PR's between a release tag and any commit sha that came after that? If so, I'm not sure if the PR you linked is needed since we don't need to reference open PR's

You can enable debug logging which should give you additional details on the reason for the failure:
https://docs.github.com/en/github-ae@latest/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging
When you verify the sha used looks correct?
Other than that usual common causes for something like this may be wrong scope/permissions of the token.
Yes it is and was possible before this PR to retrieve merged PRs between 2 git hashes.
So that's great news of things already being available as needed prior to the PR.

I can assist to setup local debugging if you wish to iterate faster, or guide you in this direction.

Yes, the sha used is correct in both scenarios (using "${{ github.sha }}" or inserting manually)
Thank you very much for all the support you've provided. As of right now this action works very well for automating our changelog on release. I'm going to have to come back to this and iterate on this in the future.

@lucasgismondi-bitbuy thank you. So you found the cause for the HttpError: Not found issue?

No this issue hasn't been resolved yet. I will come back to this probably within a few weeks

Closing this issue due to inactivity. Please re-open with additional information so we can investigate further and resolve it :)
Given the error it looks that it is most likely a permission issue.

@dtcMLOps  You can enable to includeOpen PRs by doing:

Which will result in open PRs being included for the changelog generation. (please note that they are included in the general set of PRs and are to be categorized with the category)

@dtcMLOps I'll need to think of some additional APIs to make the category more flexible

Awesome, thanks @dtcMLOps !


Postbacks not Working

Hi, I am trying to set up the post backs in my app and have been unsuccessful. Also, nothing is showing in the logs, any ideas?

The logs should definitely say something – if you've registered a hook on :postback it should run that code, and otherwise it should say that it's ignoring the event. Did you remember to subscribe to the page? Also, please help us to help you by sharing your code.

Totally unrelated question, but is there a way to retrieve the sender's first name on either the message or postback method?

Did you figure the first question out...?

And yes, you can use the Graph API to query user data.

Ok thanks, yeah everything is working now!

I know this issue is closed, but as an FYI to future readers, be sure when subscribing to the page to enable the messaging_postbacks event.
To receive messages and other events sent by Messenger users, the app should enable webhooks integration.
Selected events: message_deliveries, messages, messaging_optins, messaging_postbacks

When I initially setup my bot and webhooks, I only enabled the messages event (as shown in the README image).

Good catch, @dthyresson! I just got that image from Facebook's documentation, but it'd be good to update it with something that has all the right settings.

Hello. I am still facing the same issue :(
After sending this, I get the 2 quick reply options:
  optin.reply(
      text: "Welcome #{user.name}! Should I notify you of job updates via messages?",
      quick_replies: [
          {
              content_type: 'text',
              title: 'Yes, definitely',
              payload: 'notifications-yes'
          },
          {
              content_type: 'text',
              title: 'No',
              payload: 'notifications-no'
          }
      ]

but the, after selecting the 'yes. definitely' option, nothing happens in the postback callback:
Bot.on :postback do |postback|
  postback_debug = {
      sender: postback.sender,
      payload: postback.payload,
  }
  Rails.logger.debug "New postback: #{postback_debug.to_s}"
  case postback.payload
    when 'notifications-yes'
      postback.reply(text: 'Great')
    when 'notifications-no'
      postback.reply(text: 'Okay :(')
    else
      raise "Cannot handle postback payload: #{postback.payload}"
  end
end

However, I do get a message callback with :text=>"Yes, definitely", as seen in my logs.

A quick reply is not a postback, @vedant1811. Here's the documentation on postbacks.

I'm facing the same issue, it only occurs when I do broadcast


Facebook UI Clone

Description 📜
Added Fcaebook Homepage Clone .
Fixes #664

Type of change 📝

[X] Add a new project

Domain of Contribution 📊

[X] Project using only HTML & CSS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GSSoC'22 contributor

Screenshots / Gif (Optional) 📸
https://user-images.githubusercontent.com/77873383/163515692-3a3eecdd-1085-464f-8e88-fa954ddc0646.mp4

@khushi-purwar please check

@Mrjoy832 conflicts solve kre

@Mrjoy832 conflicts solve kre

Okay 🙃🙃

@gurjeetsinghvirdee , created new PR, Closing this one https://github.com/khushi-purwar/WebDev-ProjectKart/pull/897


Resolve errors in the pdf generation from ReadTheDocs

Reviewer
@hmunfru
Description
Resolve problems in the visualization of generated pdf from ReadTheDocs
Tester
In github and in ReadTheDocs

LGTM


Cant Find \vendor\autoload.php

So i a currently trying to install Solder and i keep getting this error http://<IP_ADDRESS>/TechnicSolder/public/
I do not know how to fix it.

composer install