Add Android FillableLoaders library definition

I hope this is ok.
I didn't ask the author to include the definition directly in his library because it's not updated since 2015.

Thank you so much for your contribution


Use VariantWalkerBase in our HaplotypeWalker

After https://github.com/broadinstitute/gatk/pull/2182

Probably I won't implement this, but after that PR was accepted the code could be simplify.


Can't running cmake command, command "cmake.xxxxx" not found

Brief Issue Summary
After connect to WSL,the cmake command cannot running.

CMake Tools seem not active(尚未激活)

CMake Tools Diagnostics
CMake: Log Diagnostics can not running.

Debug Log
No response
Additional Information
No response

@bidjc Could you paste a screenshot of what is populated when you type "CMake" into the command palette? Is it evident that the CMake extension activated?
There shouldn't be any reason why the CMake Tools extension wouldn't work in WSL, so any logs or screenshots or context would be very helpful to help us investigate.

@gcampbell-msft  sorry for later responsed,I have make screenshot,if need more info,please @to me.
Thanks

when I change vscode display language to English, cmake tools was work well.
And cmake tools can not work after switch display language to Chinese.

Today,I install Chinese (Simplified) (简体中文) Language Pack for Visual Studio Code v1.84 to WSL,and change language to Chinese,cmake tools work well.
It's seem need install Chinese language between local and WSL,then cmake tools can work well in Chineses.


Changes to contrib collector release process, and latest tag

With 0.42.0 of the collector contrib release came about some changes that were not communicated.
The 0.42.0 image has a different binary name, going from otelcolcontrib to otelcol-contrib. Though the entry point should handle this, it is still a change that will cause pain to some deployments.
The latest tag image isn't the same as the 0.42.0 image.  latest still has the old binary name, and the image itself is over 50MB, while the 0.42.0 image is around 29MB in size.
Tagging @jpkrohling on this per this CNCF slack thread: https://cloud-native.slack.com/archives/C01N6P7KR6W/p1641846859039500

While unfortunate, I would just keep the binary name change. Changing it back would potentially break people again.
I think the image size is OK, but I have yet to check why this is different. And about the latest, we could certainly fix this for 0.43. @silverlyra, it should be relatively easy to do with the new Go structs, right?

Should the binary name change be documented in a changelog?

I suspect that the size change is related to the change in debug symbol stripping noted in #58.

Should the binary name change be documented in a changelog?

It might be too late for that already, but doing it retroactively is indeed possible: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CHANGELOG.md#v0420

And about the latest, we could certainly fix this for 0.43.

@jpkrohling If I’m understanding this issue right, the fix in this repo would be update DockerManifest and add a second identical manifest with the latest tag in its name instead of {{ .Version }}.
For the core otelcol distribution, I think that would suffice, as the current published latest is out of date anyway:

But as this issue notes, otelcol-contrib has a recent but completely different latest image:

I don’t know where that image is published from, but that’d need to be turned off as well.

I don’t know where that image is published from, but that’d need to be turned off as well.

This was being published by the otel-collector core repository before we switched to building the distribution here in this repository. I understand that the job that published the image there got disabled already.

Ah I’m thinking about it a bit more and keeping the latest tag up to date is not quite so straightforward. We’d only want to update it when publishing a tag that is newer than the current latest by a semver comparison.

Good point. While this is true for the moment, it might not be true after v1. Is that handled by the Docker GitHub Action? We could have a workflow that is kicked on tags, publishing images to latest only (if this case is handled by that action).

The latest tag is now reliably updated, and we decided to keep the binary rename so I am closing this :)


Create video CLI to make video from a sesion.

should be something like
python manage.py makevideo --session basic  --outputfile ~/test.mp4

The command line code for this is in the utils.py file.

It seems like you've already added this function? Is there anything else further you wish to do or should this issue be closed?


[bug] fix duplicate error when update in h2 when use update entity an…

…d wrapper

Problem Summary:
What is changed and how it works?
Proposal: xxx
Feel free to ping committers for the review!
Contribution Checklist

Make sure that the pull request corresponds to a GITHUB issue.

Name the pull request in the form "[Feature] [component] Title of the pull request", where Feature can be replaced by Hotfix, Bug, etc.

Minor fixes should be named following this pattern: [hotfix] [docs] Fix typo in README.md doc.

Purpose of this pull request

fix duplicate error when update in h2 when use update entity and wrapper

LGTM


Start the daemon in linux.

Because the daemon in linux spawns a separate process to run the daemon and returns
an exit status of 0 there is no running child to kill when stopping the app.
Should fallback to RPC stop command.

I was not able to implement the RPC stop function, this needs to be done still.

Great. Thanks. The RPC function will most likely need to be implemented on the master Paycoin Core branch. :+1:

I don't see why, there's already an rpc command of simply "stop" which is used to stop the wallet. We just need to call it from the electron app.

Ah right, Sounds like a good idea for shutdown.

iirc this should be called from all OS not just linux to allow the daemon to properly stop, processing all shutdown hooks such as detaching the databases if such a flag is in the conf.


Vulnerability in API

The vulnerability is quite simple. It is in fact really a programming error.
When we are on the page, and inspect it with the browser, we can see that the image url is provided in clear text with an API call (containing the key) to a sharepoint url.
When we take the URL and decode it, call it via the postman tool (also works with a browser but the data is not formatted correctly) we recover several information on the sharepoint and well the video download url.
So the thumbnails of files on SharePoint have a base64 encoded object with information about the SharePoint environment. The thumbnail url is actually something that is delivered by the OneDrive API when the plugin wants to display it. It is quite odd that it contains all this information as it should just only deliver the thumbnail.
As far as I can see this affects OneDrive Business accounts only.

I don't know if it's just one particular plugin or the API in general.

Let me jump in here as I am also quite interested in this behaviour.
Expected or Desired Behavior
I would expected the thumbnail url obtained via GET /me/drive/items/{item-id}/thumbnails for OneDrive Business  accounts to just deliver the thumbnail and nothing else. Basically what the thumbnail url for OneDrive Personal does.
Observed Behavior
When an application wants to list files in a folder and display their thumbnails, the application requests a thumbnail URL via GET /me/drive/items/{item-id}/thumbnails. This returns the available thumbnailSet, which contains the thumbnail urls for the file. For OneDrive Business accounts, the provided url will look like:
https://......mediap.svc.ms/transform/thumbnail?provider=spo&inputFormat=jpg&cs=NjU1ZjZhOTgtZTNiNi00....ThlYmQtZTFhNjcxNDQ3MWQ0fFNQTw&docid=https://..../_api/v2.0/drives/b!..../items/....?tempauth=eyJ0eXAiO.......&width=...&height=...
So the thumbnail url contains base64 encodeded information in the tempauth part which includes some personal information of the owner of the file
{
 ...
 "given_name":"...",
 "family_name":"...",
<EMAIL_ADDRESS>  ..
}

The main personal information that is 'leaked' here is the given_name, family_name  and the owners email addres in the upn field.
Also, if you make a GET request to the decoded docid url in the thumbnail link and include the tempauth parameter, you can get access to all the metadata of the file including the @content.downloadUrl download link.
This causes problems in cases where the end user should only have read-only access in the application to, say, list the file names, sizes and thumbnails. But, using the thumbnail url, someone will be able to download the file and get access to all its metadata.
Is this the expected behavior of the API or is this a bug?


Avoid bulk checkbox to pollute the first column in exported files

Fix for https://github.com/Laravel-Backpack/CRUD/issues/4698.
WHY
BEFORE - What was wrong? What was happening before this PR?
Bulk checkbox was polluting the first column in exported files;

AFTER - What is happening after this PR?
It works properly;

HOW
How did you achieve that, in technical terms?
By ignoring bulk checkboxes on data export :not(.crud_bulk_actions_line_checkbox).
Is it a breaking change?
No 👌

Thanks @promatik 🎉


chore(deps): update common-dev-assets digest to 67f3ce5

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
d3a341c -> 67f3ce5

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

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


[BUG] Computer Vision OCR sample bug

Describe the bug
Text not properly recognized in attached image. This happens with sample in the repo listed below (also here: https://github.com/Azure-Samples/cognitive-services-dotnet-sdk-samples/blob/master/samples/ComputerVision/OCR/Program.cs), and happens when I use the Computer Vision SDK for Go. This image is in the image repo. Other images with cursive/handwritten text are recognized accurately.

Exception or Stack Trace
Recognizing text in a local image with OCR ...
Text:
Language: en
Text angle: 0
Orientation: Up
Text regions:
Region bounding box: 102,27,384,87
Line bounding box 102,27,58,27
Word bounding box: 102,27,58,27
Text: musAv
Line bounding box 312,84,174,30
Word bounding box: 312,92,17,21
Text: in
Word bounding box: 406,84,80,30
Text: woacl
To Reproduce
Run this sample: https://github.com/Azure-Samples/cognitive-services-dotnet-sdk-samples/blob/master/samples/ComputerVision/OCR/Program.cs
Expected behavior
Text output should be:
You must be the change
you want to see in the world!
Screenshots
N/A
Setup (please complete the following information):

OS: Windows 10
IDE : command-line
Version of the Java Library used: "Microsoft.Azure.CognitiveServices.Vision.ComputerVision" Version="4.0.0"
Version of the Go Library used: 2.0

Additional context
None.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[X] Bug Description Added
[X] Repro Steps Added
[X] Setup information Added

@LukeBayler, the sample code is using wrong API for calling OCR service. It's recommend to use BatchReadFile instead of RecognizePrintedText.

Got it. Thanks. I'm working with the SDKs and don't see support for BatchReadFile in the Java SDK. Is that correct?

Yes. The Java SDK hasn't been updated for quite a long time. I submitted an issue for that.
https://github.com/Azure/azure-sdk-for-java/issues/3785

Hi Luke,
The latest iteration of the Computer vision APIs has a new async operation called Read which should perform well with handwritten text.
You can refer to this guide to get started in Java: https://docs.microsoft.com/en-us/azure/cognitive-services/computer-vision/quickstarts-sdk/client-library?pivots=programming-language-java
I hope this helps.
Thanks,
Tom


[BUG] Readme "register-here" link for slack is broken

Bug
Clicking the "register-here" link results in a "This link is no longer active" error:

Describe the problem
Clicking the "register-here" link results in a "This link is no longer active" error, preventing new enrollments though that channel.
Steps to reproduce

Visit the readme
Click "Register-Here"
Feel disappointed

Observed results

Expected results

Further details

Environment information

Delta Lake version:
Spark version:
Scala version:

Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?

[ ] Yes. I can contribute a fix for this bug independently.
[ ] Yes. I would be willing to contribute a fix for this bug with guidance from the Delta Lake community.
[ ] No. I cannot contribute a bug fix at this time.

cc @MrPowers @nkarpov

Thanks @scottsand-db, I opened an issue here to address this one.


Contact component

Description:
Creating a contact page with forms that will allow the user send in emails when need.
Priority:
High
Type:
MVP Feature
User story -
Currently blank
User Story - Expected Behaviour:
When the contact button on the nav-bar is clicked it takes you to the page which in turn allows you to contact the company either via a form or calls or emails.
Steps to Reproduce:
not applicable
Screenshots:
none
Branch Name:
8-Contact-component
Additional Information:
[Provide any additional information, context, or suggestions that might be helpful.]
Acceptance Criteria:

This should have a form created with formik this will allow for inquiries to be made.
when you click on contact button it should open to a page with "Inquiries" link which opens up to a form when you click on inquiries (form should have name, email, phone numbers, message).
contact details below.

Subtasks:
not applicable.
Assignees:
Leading Developer: [@Chiamaka]
Leading QA: [@Shola]
Labels:
MVP
Due Date:
20/01/2024
Dependencies:
None
Notes for Reviewers:
None.

Hi @d-sholaakanbi, Please QA this branch and confirm if they are okay. I am yet to manage the state and run validation for the form which I intend to do on another branch. I'm also aware that i need to include a section of the field according to the template issued. This will come in on the next issue as contact component updated.
Kind regards,
Chiamaka


Can't compile on local machine but fine on online compiler

Hi, I've just installed the mbed-cli on my Macbook but can't the project to compile.
It's compiling great with the online compiler though but on my local machine I've got
[DEBUG] Output: ./mbed/platform.h:21:20: fatal error: device.h: No such file or directory

I've tried to update the librairies and all but nothing seems to work 😔
I'm with gcc-arm-none-eabi-4_9-2015q2 toolchain and the NRF51_DK target.

Hi @peterpan666,
I would like to help you out with this, but I don't have enough information to do that.
Could you point me at the program you are trying to compile?
Could you tell me which target you are trying to compile for?
Could you list the versions of mbed-cli and mbed-os?

Hi and thanks for your answer! Here we go :

I can't show you the entire program, it is private and not mine 😕
The target is the NRF51_DK
The mbed-cli is version 1.1.1 I'm not really sure using the mbed-os, how can I see which version it is?

The mbed-cli is version 1.1.1 I'm not really sure using the mbed-os, how can I see which version it is?

mbed ls

should do the trick

This is the output of mbed ls
|- BLE_MIDI (2b71bfbaa458)
|  |- BLE_API (8c645f5694b2)
|  |- mbed (487b796308b0)
|  `- nRF51822 (bdc690669431)
`- LSM9DS1_Library (87d535bf8c53)

Thanks for the info. You are using the mbed hal revision 96, which is quite old.

Yeah I believe it's due to the BLE_MIDI dependency but still, I don't get why I could compile the project online and not on my local machine 😕

Agreed. It should compile in both. I'm going to try to reproduce the error on my end. If I can, then I can give you some insight on why it's failing.

I created a test project with an empty main to test the BLE_MIDI + sub-library structure.
mbed ls
testing-BLE-MIDI (None)
`- BLE_MIDI (2b71bfbaa458)
   |- BLE_API (8c645f5694b2)
   |- mbed (487b796308b0)
   `- nRF51822 (bdc690669431)

mbed compile -t gcc_arm -m nrf51_dk
Building project testing-BLE-MIDI (NRF51_DK, GCC_ARM)
Scan: .
Scan: mbed
Scan: env
Compile [  3.2%]: GapAdvertisingParams.cpp
Compile [  6.5%]: UUID.cpp
Compile [  9.7%]: BLEDevice.cpp
Compile [ 12.9%]: GattService.cpp
Compile [ 16.1%]: GapAdvertisingData.cpp
Compile [ 19.4%]: DFUService.cpp
Compile [ 22.6%]: UARTService.cpp
Compile [ 25.8%]: btle_advertising.cpp
[Warning] assertion.h@83,1: multi-line comment [-Wcomment]
[Warning] assertion.h@86,1: multi-line comment [-Wcomment]
[Warning] ble_gap.h@722,42: 'uint32_t sd_ble_gap_address_set(uint8_t, const ble_gap_addr_t*)' defined but not used [-Wunused-function]
Compile [ 29.0%]: btle_gap.cpp
[Warning] assertion.h@83,1: multi-line comment [-Wcomment]
[Warning] assertion.h@86,1: multi-line comment [-Wcomment]
[Warning] ble_gap.h@722,42: 'uint32_t sd_ble_gap_address_set(uint8_t, const ble_gap_addr_t*)' defined but not used [-Wunused-function]
Compile [ 32.3%]: app_gpiote.c
Compile [ 35.5%]: custom_helper.cpp
[Warning] assertion.h@83,1: multi-line comment [-Wcomment]
[Warning] assertion.h@86,1: multi-line comment [-Wcomment]
[Warning] ble_gap.h@722,42: 'uint32_t sd_ble_gap_address_set(uint8_t, const ble_gap_addr_t*)' defined but not used [-Wunused-function]
Compile [ 38.7%]: crc16.cpp
Compile [ 41.9%]: app_scheduler.c
Compile [ 45.2%]: hci_mem_pool.c
Compile [ 48.4%]: nRF51Gap.cpp
[Warning] assertion.h@83,1: multi-line comment [-Wcomment]
[Warning] assertion.h@86,1: multi-line comment [-Wcomment]
[Warning] nRF51Gap.cpp@226,12: enumeration value 'LOCAL_HOST_TERMINATED_CONNECTION' not handled in switch [-Wswitch]
Compile [ 51.6%]: btle.cpp
[Warning] assertion.h@83,1: multi-line comment [-Wcomment]
[Warning] assertion.h@86,1: multi-line comment [-Wcomment]
[Warning] nordic_common.h@36,9: comparison of unsigned expression < 0 is always false [-Wtype-limits]
[Warning] nordic_common.h@36,9: comparison of unsigned expression < 0 is always false [-Wtype-limits]
Compile [ 54.8%]: ble_bondmngr.cpp
Compile [ 58.1%]: ble_advdata_parser.cpp
[Warning] ble_gap.h@722,42: 'uint32_t sd_ble_gap_address_set(uint8_t, const ble_gap_addr_t*)' defined but not used [-Wunused-function]
Compile [ 61.3%]: BLEMIDI.cpp
[Warning] BLEMIDI.cpp@268,24: deprecated conversion from string constant to 'char*' [-Wwrite-strings]
[Warning] BLEMIDI.cpp@432,0: suggest parentheses around arithmetic in operand of '|' [-Wparentheses]
[Warning] BLEMIDI.cpp@441,0: suggest parentheses around arithmetic in operand of '|' [-Wparentheses]
Compile [ 64.5%]: nRF51822n.cpp
[Warning] nRF51822n.h@20,0: "NRF51" redefined
[Warning] assertion.h@83,1: multi-line comment [-Wcomment]
[Warning] assertion.h@86,1: multi-line comment [-Wcomment]
[Warning] ble_gap.h@722,42: 'uint32_t sd_ble_gap_address_set(uint8_t, const ble_gap_addr_t*)' defined but not used [-Wunused-function]
Compile [ 67.7%]: ble_debug_assert_handler.cpp
Compile [ 71.0%]: bootloader_util_arm.c
Compile [ 74.2%]: ble_advdata.cpp
[Warning] ble_gap.h@722,42: 'uint32_t sd_ble_gap_address_set(uint8_t, const ble_gap_addr_t*)' defined but not used [-Wunused-function]
Compile [ 77.4%]: ble_srv_common.cpp
[Warning] ble_gap.h@722,42: 'uint32_t sd_ble_gap_address_set(uint8_t, const ble_gap_addr_t*)' defined but not used [-Wunused-function]
Compile [ 80.6%]: ble_error_log.cpp
Compile [ 83.9%]: nRF51GattServer.cpp
[Warning] assertion.h@83,1: multi-line comment [-Wcomment]
[Warning] assertion.h@86,1: multi-line comment [-Wcomment]
[Warning] ble_gap.h@722,42: 'uint32_t sd_ble_gap_address_set(uint8_t, const ble_gap_addr_t*)' defined but not used [-Wunused-function]
Compile [ 87.1%]: main.cpp
Compile [ 90.3%]: dfu_app_handler.c
Compile [ 93.5%]: softdevice_handler.cpp
[Warning] nrf_soc.h@348,32: 'uint32_t sd_mutex_new(nrf_mutex_t*)' defined but not used [-Wunused-function]
Compile [ 96.8%]: pstorage.cpp
[Warning] nrf_soc.h@348,32: 'uint32_t sd_mutex_new(nrf_mutex_t*)' defined but not used [-Wunused-function]
Compile [100.0%]: ble_conn_params.cpp
[Warning] ble_gap.h@722,42: 'uint32_t sd_ble_gap_address_set(uint8_t, const ble_gap_addr_t*)' defined but not used [-Wunused-function]
Link: testing-BLE-MIDI
Elf2Bin: testing-BLE-MIDI
+-----------+-------+-------+------+
| Module    | .text | .data | .bss |
+-----------+-------+-------+------+
| Fill      |    37 |     0 |   22 |
| Misc      | 15347 |   128 | 1438 |
| Subtotals | 15384 |   128 | 1460 |
+-----------+-------+-------+------+
Allocated Heap: 2048 bytes
Allocated Stack: 2048 bytes
Total Static RAM memory (data + bss): 1588 bytes
Total RAM memory (data + bss + heap + stack): 5684 bytes
Total Flash memory (text + data + misc): 15512 bytes

Image: ./BUILD/nrf51_dk/gcc_arm/testing-BLE-MIDI.hex

Looks fine.
I don't know what's going wrong here.

Sigh and with the same libraries version 😔
Ok I'll try to find something missing and put it back here if I find anything.
Thanks for your help and time!

Wich version of GCC ARM are you using?

You're welcome.
I'm just glad that you got it working :D


Solution for exercise 1.3

I used delay function before executing kernel_main to avoid race in uart equipment

Sent with GitHawk


Add client-go 8.0.0 changelog

Ref: https://docs.google.com/spreadsheets/d/1jPexPgSohmD7zVmIeVvAFjjK_pqFu4MdjsmBXlINfvg/edit#gid=0
/assign sttts caesarxuchao

I moved the [k8s.io/api] changes to another section called "API Changes" for easier readibility (as discussed on slack).

/lgtm
/approve
/hold
We merge when we tag 8.0.0.

1.11 has been released. This should be good to go?

/cancel hold


expose getTransactionResultByIndex

Expose the grpc method to get TransactionResultByIndex since it is the only way to get systemChunkEvents and not get all other transactions in the same block

Codecov Report

Merging #427 (47abbbe) into master (ba0b0e0) will decrease coverage by 0.40%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #427      +/-   ##
==========================================
- Coverage   62.30%   61.90%   -0.40%
==========================================
  Files          24       24
  Lines        2966     2985      +19
==========================================
  Hits         1848     1848
- Misses        994     1013      +19
  Partials      124      124

Flag
Coverage Δ

unittests
61.90% <0.00%> (-0.40%)
:arrow_down:

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

Impacted Files
Coverage Δ

access/grpc/client.go
0.00% <0.00%> (ø)

access/grpc/grpc.go
79.15% <0.00%> (-3.72%)
:arrow_down:

@bjartek can you update this PR?

updated, sorry was away for a bit


Remote Sequences

Building on #777, https://github.com/impactasaurus/app/issues/774 and https://github.com/impactasaurus/server/issues/329, support individual and multiple beneficiary remote links for questionnaire sequences.

 Questionnaire Series


dvc init command should not support --target-file option

whenever you execute dvc init -h, the console output contains the text below,
[--target-file TARGET_FILE]
However, it should not contain it.

Already fixed in master.


plugin error

Plugin error: File '~/.local/share/Google/AndroidStudio2021.2/Kotlin/lib/kotlin-idea.jar' contains invalid plugin descriptor

how to solve this

💪 Building with sound null safety 💪
Running Gradle task 'assembleRelease'...
Building with Flutter multidex support enabled.
lib/controllers/common/drawer_controller.dart:8:32: Error: Method not found: 'ZoomDrawerController'.
final zoomDrawerController = ZoomDrawerController();
^^^^^^^^^^^^^^^^^^^^
lib/screens/home/home_screen.dart:30:9: Error: No named parameter with the name 'backgroundColor'.
backgroundColor: Colors.white.withOpacity(0.5),
^^^^^^^^^^^^^^^
../../../snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_zoom_drawer-3.0.2/lib/flutter_zoom_drawer.dart:34:9: Context: Found this candidate, but the arguments don't match.
const ZoomDrawer({
^^^^^^^^^^
lib/screens/leaderboard/leaderboard_screen.dart:12:22: Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.

'SchedulerBinding' is from 'package:flutter/src/scheduler/binding.dart' ('../../../snap/flutter/common/flutter/packages/flutter/lib/src/scheduler/binding.dart').
SchedulerBinding.instance!.addPostFrameCallback((d) {
^

FAILURE: Build failed with an exception.

Where:
Script '/home/jishnu/snap/flutter/common/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 1156

What went wrong:
Execution failed for task ':app:compileFlutterBuildRelease'.

Process 'command '/home/jishnu/snap/flutter/common/flutter/bin/flutter'' finished with non-zero exit value 1

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 1m 13s
Running Gradle task 'assembleRelease'...                           76.0s
Gradle task assembleRelease failed with exit code 1
Process finished with exit code 1

I'm also getting these errors

pull new commit and  run flutter pub upgrade

Thaks bro


Interrupt wdt timeout after updating to ESP-IDF v4.2 (IDFGH-4991)

Environment

Module or chip used:  ESP32-WROVER-IB
IDF version: v4.2
Build System:  idf.py
Compiler version: (crosstool-NG esp-2020r3) 8.4.0
Operating System: Windows
environment type: PowerShell
Using an IDE?: VScode
Power Supply:  USB & Battery

Problem Description
After the update to ESP-IDF 4.2 (coming from v4.1.1), a watchdog is triggered on every boot. However, it was not happening before.
Normally, I leave both the RTC and Interrupt watchdogs enabled, like this:
CONFIG_BOOTLOADER_WDT_ENABLE=y
# CONFIG_BOOTLOADER_WDT_DISABLE_IN_USER_CODE is not set
CONFIG_BOOTLOADER_WDT_TIME_MS=9000
CONFIG_ESP_INT_WDT=y
CONFIG_ESP_INT_WDT_TIMEOUT_MS=800
CONFIG_ESP_INT_WDT_CHECK_CPU1=y
CONFIG_ESP_TASK_WDT=y
CONFIG_ESP_TASK_WDT_PANIC=y
CONFIG_ESP_TASK_WDT_TIMEOUT_S=5
CONFIG_ESP_TASK_WDT_CHECK_IDLE_TASK_CPU0=y
CONFIG_ESP_TASK_WDT_CHECK_IDLE_TASK_CPU1=y

But then, this happens:
^other logs, not relevant (the app doesn't finish loading)... ^
D (1774) efuse: coding scheme 0
D (1774) event: runninets Jun  8 2016 00:22:57     <--- (notice how the execution stops here. The watchdog gets triggered 9s after this)

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

*reboots*

I tried to check if there are tasks that are taking too long to return, but I couldn't find any. This actually seems to happen even before my app is able to register any task. I suppose the problem might not be related to my code, especially when considering that this wasn't happening with the old version.
Out of ideas, in order to diagnose what's going on, I played a little with the sdkconfig file and performed the following:
1. If I disable CONFIG_ESP_INT_WDT_CHECK_CPU1
I thought about this because it looks like that a panic from both cores (like above) isn't diagnosed. Instead, I kept the watchdog enabled on just the core 0 (which fails as well).
Result:
Guru Meditation Error: Core  0 panic'ed (Interrupt wdt timeout on CPU0).

Core  0 register dump:
PC      : 0x4008cb78  PS      : 0x00060034  A0      : 0x8008d893  A1      : 0x3ffb0750
0x4008cb78: compare_and_set_native at C:/development/v4.2/esp-idf/components/soc/include/soc/compare_set.h:28
 (inlined by) spinlock_acquire at C:/development/v4.2/esp-idf/components/soc/include/soc/spinlock.h:97
 (inlined by) vPortCPUAcquireMutex at C:/development/v4.2/esp-idf/components/freertos/xtensa/include/freertos/portmacro.h:202
 (inlined by) vPortEnterCritical at C:/development/v4.2/esp-idf/components/freertos/xtensa/port.c:394

A2      : 0x3ffb11ec  A3      : 0x0000cdcd  A4      : 0x00060023  A5      : 0x00060021
A6      : 0x0000abab  A7      : 0xb33fffff  A8      : 0x0000abab  A9      : 0x3ffb4b4c
A10     : 0x3ffb4b44  A11     : 0x00060023  A12     : 0x00060021  A13     : 0x00060e20
A14     : 0x000000fe  A15     : 0x00000001  SAR     : 0x00000004  EXCCAUSE: 0x00000005
EXCVADDR: 0x00000000  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xfffffffe
Core  0 was running in ISR context:
EPC1    : 0x401cf657  EPC2    : 0x00000000  EPC3    : 0x00000000  EPC4    : 0x4008cb78
0x401cf657: uart_hal_write_txfifo at C:/development/v4.2/esp-idf/components/soc/src/hal/uart_hal_iram.c:35

0x4008cb78: compare_and_set_native at C:/development/v4.2/esp-idf/components/soc/include/soc/compare_set.h:28
 (inlined by) spinlock_acquire at C:/development/v4.2/esp-idf/components/soc/include/soc/spinlock.h:97
 (inlined by) vPortCPUAcquireMutex at C:/development/v4.2/esp-idf/components/freertos/xtensa/include/freertos/portmacro.h:202
 (inlined by) vPortEnterCritical at C:/development/v4.2/esp-idf/components/freertos/xtensa/port.c:394

Backtrace:0x4008cb75:0x3ffb0750 0x4008d890:0x3ffb0780 0x4008caef:0x3ffb07a0 0x4008cdb1:0x3ffb07c0 0x40085329:0x3ffb07d0 0x4010be99:0x3ffbc6f0 0x4010cc12:0x3ffbc710 0x400d3fd9:0x3ffbc730 0x4000bd83:0x3ffbc750 0x4000117d:0x3ffbc770 0x400592fe:0x3ffbc790 0x4005937a:0x3ffbc7b0 0x40058bbf:0x3ffbc7d0 0x401b92bb:0x3ffbc800 0x401be89f:0x3ffbc830 0x401bea21:0x3ffbcb40 0x401cf569:0x3ffbcb70 0x40090a19:0x3ffbcba0 0x401cec0b:0x3ffbcbf0 0x4008ca1d:0x3ffbcc10
0x4008cb75: spinlock_acquire at C:/development/v4.2/esp-idf/components/soc/include/soc/spinlock.h:81
 (inlined by) vPortCPUAcquireMutex at C:/development/v4.2/esp-idf/components/freertos/xtensa/include/freertos/portmacro.h:202
 (inlined by) vPortEnterCritical at C:/development/v4.2/esp-idf/components/freertos/xtensa/port.c:394

0x4008d890: xTaskIncrementTick at C:/development/v4.2/esp-idf/components/freertos/tasks.c:2491

0x4008caef: xPortSysTickHandler at C:/development/v4.2/esp-idf/components/freertos/xtensa/port.c:300

0x4008cdb1: _frxt_timer_int at C:/development/v4.2/esp-idf/components/freertos/xtensa/portasm.S:328

0x40085329: _xt_lowint1 at C:/development/v4.2/esp-idf/components/freertos/xtensa/xtensa_vectors.S:1105

0x4010be99: uart_tx_char at C:/development/v4.2/esp-idf/components/vfs/vfs_uart.c:164 (discriminator 1)

0x4010cc12: uart_write at C:/development/v4.2/esp-idf/components/vfs/vfs_uart.c:221

0x400d3fd9: esp_vfs_write at C:/development/v4.2/esp-idf/components/vfs/vfs.c:420 (discriminator 4)

0x401b92bb: __sprint_r at /builds/idf/crosstool-NG/.build/HOST-x86_64-w64-mingw32/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/vfprintf.c:433
 (inlined by) __sprint_r at /builds/idf/crosstool-NG/.build/HOST-x86_64-w64-mingw32/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/vfprintf.c:403

0x401be89f: _vfprintf_r at /builds/idf/crosstool-NG/.build/HOST-x86_64-w64-mingw32/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/vfprintf.c:1781 (discriminator 1)

0x401bea21: vprintf at /builds/idf/crosstool-NG/.build/HOST-x86_64-w64-mingw32/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/vprintf.c:34 (discriminator 5)

0x401cf569: esp_log_writev at C:/development/v4.2/esp-idf/components/log/log.c:189

0x40090a19: esp_log_write at C:/development/v4.2/esp-idf/components/log/log.c:199

0x401cec0b: esp_event_loop_run_task at C:/development/v4.2/esp-idf/components/esp_event/esp_event.c:112

0x4008ca1d: vPortTaskWrapper at C:/development/v4.2/esp-idf/components/freertos/xtensa/port.c:143

That, unfortunately, neither does look very clear to me or explain clearly where the problem could be.
2. If I disable CONFIG_ESP_INT_WDT
The app just works as expected. Everything is loaded, even the WiFi+MQTT stuff seems to work. I doubt it would if a task was stuck somewhere.
The problem, however, is that I can't win an app without Interrupt watchdogs. This isn't a solution.
Expected Behavior
The app should just run like it was doing before.
Actual Behavior
It's boot looping. The watchdogs are being triggered every time.
Steps to reproduce
I was unable to find a way to reproduce the issue and shrink the application due to its complexity.
I'm not allowed to share the entire application.
Addtional details
I tried to generate a coredump but with all the watchdogs enabled, although nothing is generated.
Any idea? Thanks in advance

Thanks for reporting and sorry for the inconvenience, we will look into.

Hi @leofabri,
Thanks for the detailed report. Could you attach your full sdkconfig file, please?

Hi @leofabri,
Thanks for the detailed report. Could you attach your full sdkconfig file, please?

Sure, here is it: sdkconfig

Any update about this? I'd like to investigate, but I don't have a very clear about what I'm looking at.

Hi @leofabri,
Sorry for going quiet on you for so long.
The sdkconfig file itself seems fine, I don't see any configuration items there that are likely to cause a problem.
Given that everything works fine with INT WDT off, the most likely explanation is that something is disabling or generating a lot of interrupts for a relatively long time (800ms). That doesn't necessarily mean a task is stuck - the INT WDT will timeout if interrupts are being processed non-stop, even though nothing is necessarily stuck it's just a big queue of interrupts to handle. With PSRAM, it's possible for certain operations to run relatively slowly especially during initialization when a lot of new code is being loaded so the flash cache (which is shared with PSRAM) has a high miss rate.
To rule this out, set the CONFIG_ESP_INT_WDT_TIMEOUT_MS to something higher than the default 800ms - maybe 2000ms, for example, and then if the firmware starts to work then you can try reducing it from there. Do you notice any significant pause during startup, either with this config or when the INT WDT is disabled?
If this isn't the cause then I assume it must be something related to the particular application code. Can you give any clues about what the app does during initialization? If you selectively disable initialization for parts of the application, can you zero in one element that causes it for fail?
Also, do you have any backtrace of INT WDT failing when configured on Core 1 only (similarly to the backtrace for Core 0, only)?
Thanks,
Angus

Hi @projectgus,
I tried to set CONFIG_ESP_INT_WDT_TIMEOUT_MS to 2000 (and also to 5000) but the bootloop is still occurring.

Also, do you have any backtrace of INT WDT failing when configured on Core 1 only (similarly to the backtrace for Core 0, only)?

For some reason, I was unable to backtrace the execution like I was doing before. Maybe something did change with version v.4.2.1.
The only thing I can see now is:
rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:4
load:0x3fff0034,len:7064
load:0x40078000,len:12176
ho 0 tail 12 room 4
load:0x40080400,len:4500
0x40080400: _init at ??:?

entry 0x400806ec
I (183) boot: ESP-IDF v4.2.1-dirty 2nd stage bootloader
I (183) boot: compile time 09:16:22
I (183) boot: chip revision: 1
I (188) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (195) boot.esp32: SPI Speed      : 80MHz
I (200) boot.esp32: SPI Mode       : DIO
I (204) boot.esp32: SPI Flash Size : 16MB
W (209) boot.esp32: PRO CPU has been reset by WDT.
W (214) boot.esp32: WDT reset info: PRO CPU PC=0x4008c9f1
0x4008c9f1: panic_handler at C:/development/esp-idf/components/esp_system/port/panic_handler.c:490 (discriminator 2)

W (220) boot.esp32: WDT reset info: APP CPU PC=0x4008f826
0x4008f826: vListInsert at C:/development/esp-idf/components/freertos/list.c:189

I (226) boot: Enabling RNG early entropy source...

What I'm going to try now is to disable some parts of the applicationt o idetify the problem. I'll get back to you as soon as I discover something.

Hi @leofabri,
Did you have any luck isolating this in a way that we can try to reproduce it?

Thanks for reporting, will close now, feel free to reopen with more updates.


I used it to post test,but response network error

I use same way in postman to test api, and it worked. but I try to send request by postwoman. it reponsed newwork error! why

To test endpoints in localhost, install browser extension. Links can be found in readme.

I hava  installed,browser extension,andI also open use the browser extension in Settings. but it's response network error too.

me too...


Inconsistent variable names in sauce.js and driverProvider.js, config_.webDriverProxy needs to be added to sauce.js file

It seems that webDriverProxy variable is missing in the 'sauce.js' file!  Therefore,  we have the following workaround in place to have our Protractor test run on Sauce Labs via our corporate proxy:

In protractor config.js add following lines

exports.config = {
     sauceUser:'SauceUser',
     sauceKey:'SauceKey',
     webDriverProxy: 'http://proxy.mysite.com:18099',

   // things you had in there before
};

In node_modules/protractor/lib/driverProviders/sauce.js file (i.e. the DriverProvider for Sauce Labs in Protractor), add this:

this.sauceServer_ = new SauceLabs({
    username: this.config_.sauceUser,
    password: this.config_.sauceKey,
    agent: this.config_.sauceAgent,
    proxy: this.config_.webDriverProxy   // this line needs to be added
});

In node_modules/protractor/lib/driverProviders/driverProvider.js modify the getNewDriver function as below.

DriverProvider.prototype.getNewDriver = function() {
 var newDriver = new webdriver.Builder().
     usingServer(this.config_.seleniumAddress).
  usingWebDriverProxy(this.config_.webDriverProxy).    // here we have webDriverProxy
     withCapabilities(this.config_.capabilities).
     build();
 this.drivers_.push(newDriver);
 return newDriver;
};

Change (3) already exists in protractor (at least at master).
@juliemr you know why we have both sauceProxy and webDriverProxy?


fix(startup): allow congregation account creation after mfa verification

:tada: This PR is included in version 1.0.0-alpha.133 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Codelab Issue] Testing Codelab 5.2, Step 7 - Issue description

Link of the Codelab
https://codelabs.developers.google.com/codelabs/advanced-android-kotlin-training-testing-test-doubles/index.html?index=..%2F..index#6
Describe the problem
Wrong description of text on item 7.3.4 of this Codelab.

Advanced Android in Kotlin 05.2: Introduction to Test Doubles and Dependency Injection

7 . Task: Use the Fake Repository inside a ViewModel
Step 3. Also Update TaskDetail Fragment and ViewModel
4 . Update TasksFragment to use the factory.

In which lesson and step of the codelab can this issue be found?
Lesson number 7 + step number 3.4.
How to reproduce?
At item 7.3.4, the current description is:
"Update TasksFragment to use the factory."
The correct description here should be the one below, because the file that is updated here it the TaskDetailFragment.kt and not the TasksFragment.kt.
"Update TaskDetailFragment to use the factory."
codelab: advanced-android-kotlin

This seems fixed