text:
feat: readonly primitives new ui looks better

What does this pull request change?
Readonly now looks more like an inputField.
Is a custom component.

Why is this pull request needed?
Issues related to this change

Maybe just keep it, it is more flexible to have it inside the widgets.
The alternative is to do something like this inside the  StringField and Numberfield
const Widget = getWidget(uiAttribute?.widget ?? (readOnly ? 'ReadOnlyWidget : ' TextWidget'))

source: gharchive/pull-request

authors: eoaksnes pbullhove

repo: equinor/dm-core-packages

license: MIT

license_type: permissive

license_source: github-api


text:
Refactor textblock

Its seems that with portable text or something every  is wrapped in a div.
And headings is wrapped in a div.
These wrappers increase dom size and is unnecessary.
rewrite to merge wrapping div styling into the tag itself
defaultSerializers should not use div containers. A text paragraph should be a paragraph.

@meols @NickHaggerty1
https://web-global-development-equinor-web-sites-dev.c2.radix.equinor.com/news/20230105-equinor-rwe-cooperation
Can you take a look at the general look and the 2 headings used in that news article and let me know if the editorial team wants it even smaller?
I have suggested;

heading 2 styling in the "Strengthening energy security" that should apply for heading inside an article.
heading 3 styling in the "Driving forward". The h3 is a bit smaller, but with same fontweigth

@BorghildSelle - in Equinor news articles in general we don't get the content from our stakeholders structured with a H2. If a H2 should be used to "introduce a new section/chapter" of content we are unsure if a H2 is suitable for the content. Wouldn't it be wrong to use a H2 when the content only is within the same topic? Our thinking is that H3 is more suitable as all content in a news article is subsections within the same topic. Is it critical to introduce H2 in news articles? If so, would it be better for screen readers to have only H2 headers instead of H3? In most cases all headers in the content are on the same level/within the same topic.

According to WCAG one should not skip heading ranks, because it can be confusing and should be avoided where possible. So a H1 should not have a h3 directly following but as the image below shows.
A page should have the title as h1, then the article should be sectioned into h2 headings as one would make chapters in a book. If one h2 heading is long it can be further divided into h3 headings.
Screen reader users can navigate a page according to its headings, listen to a list of all headings, and skip to a desired heading to begin reading at that point.

So you can dictate now how you would like a level 2 heading in an article should look like.
It will not affect the headings on other elements/components.
Only headings in an article (it can for instance also be applied for magazine, so that longer articles look the same)

source: gharchive/issue

authors: BorghildSelle meols

repo: equinor/energyvision


text:
[Snyk] Upgrade pixi.js from 6.4.2 to 6.5.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade pixi.js from 6.4.2 to 6.5.2.
: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 7 versions ahead of your current version.
The recommended version was released 21 days ago, on 2022-08-24.

Release notes

Package name: pixi.js

6.5.2 - 2022-08-24💾  Download
Development Build:

https://pixijs.download/v6.5.2/pixi.js
https://pixijs.download/v6.5.2/pixi.js.map
https://pixijs.download/v6.5.2/pixi.mjs
https://pixijs.download/v6.5.2/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.2/pixi.min.js
https://pixijs.download/v6.5.2/pixi.min.js.map
https://pixijs.download/v6.5.2/pixi.min.mjs
https://pixijs.download/v6.5.2/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.2/docs/index.html

Changed
v6.5.1...v6.5.2
🐛 Fixed

Normalize more uses of document.createElement('canvas') for Node (#8523) @ bigtimebuddy
Add support for base64 images with Assets (#8559) @ talhaozdemir
Loosen Graphics.drawPolygon types to use IPointData (#8573) @ mhazy
Fix typo in Resolver basePath setter (#8569) @ qwertywelch
Fix jittering caused by incorrect BitmapText text width (#8536) @ grebinka
Fix Assets' text-based loading of fnt BitmapFonts (#8568) @ bigtimebuddy
Fix Assets' onProgress with multiple bundles (#8565) @ Zyie
Add missing SVG loader to Assets (#8574) @ Zyie
Fix documentations for PIXI.DisplayObject#childRemoved (#8582) @ ryiwamoto
Fix implementing test "should load texture array correctly" (#8578) @ qwertywelch
Add cross-compatible path utils for Assets (#8605) @ Zyie

🧹 Chores

Add installation error help to readme (#8563) @ Zyie
Add pixijselementals.com to "Learn" section of main readme (#8581) @ domis86

6.5.1 - 2022-07-24🔥  Hotfix
Previous release accidentally bundled the core into packages it wasn't suppose to including in ticker, canvas-mesh, canvas-sprite. It is strongly recommended that you update to 6.5.1 if you upgraded (or tried to) 6.5.0.
💾  Download
Development Build:

https://pixijs.download/v6.5.1/pixi.js
https://pixijs.download/v6.5.1/pixi.js.map
https://pixijs.download/v6.5.1/pixi.mjs
https://pixijs.download/v6.5.1/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.1/pixi.min.js
https://pixijs.download/v6.5.1/pixi.min.js.map
https://pixijs.download/v6.5.1/pixi.min.mjs
https://pixijs.download/v6.5.1/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.1/docs/index.html

Changed
v6.5.0...v6.5.1
🐛 Fixed

Hotfix: Make sure core isn't bundled in ticker, canvas-sprite, canvas-mesh (#8527) @ bigtimebuddy

6.5.0 - 2022-07-22 Read more

6.5.0-rc.4 - 2022-07-20🔥 Sorting blocking bug related to @ pixi/assets
💾  Download
Development Build:

https://pixijs.download/v6.5.0-rc.4/pixi.js
https://pixijs.download/v6.5.0-rc.4/pixi.js.map
https://pixijs.download/v6.5.0-rc.4/pixi.mjs
https://pixijs.download/v6.5.0-rc.4/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.0-rc.4/pixi.min.js
https://pixijs.download/v6.5.0-rc.4/pixi.min.js.map
https://pixijs.download/v6.5.0-rc.4/pixi.min.mjs
https://pixijs.download/v6.5.0-rc.4/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.0-rc.4/docs/index.html

Changed
v6.4.2...v6.5.0-rc.4

6.5.0-rc.3 - 2022-07-20🔥 Sorting more blocking bugs related to @ pixi/node
💾  Download
Development Build:

https://pixijs.download/v6.5.0-rc.3/pixi.js
https://pixijs.download/v6.5.0-rc.3/pixi.js.map
https://pixijs.download/v6.5.0-rc.3/pixi.mjs
https://pixijs.download/v6.5.0-rc.3/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.0-rc.3/pixi.min.js
https://pixijs.download/v6.5.0-rc.3/pixi.min.js.map
https://pixijs.download/v6.5.0-rc.3/pixi.min.mjs
https://pixijs.download/v6.5.0-rc.3/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.0-rc.3/docs/index.html

Changed
v6.4.2...v6.5.0-rc.3

6.5.0-rc.2 - 2022-07-15🔥 Hotfix for @ pixi/node
💾  Download
Development Build:

https://pixijs.download/v6.5.0-rc.2/pixi.js
https://pixijs.download/v6.5.0-rc.2/pixi.js.map
https://pixijs.download/v6.5.0-rc.2/pixi.mjs
https://pixijs.download/v6.5.0-rc.2/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.0-rc.2/pixi.min.js
https://pixijs.download/v6.5.0-rc.2/pixi.min.js.map
https://pixijs.download/v6.5.0-rc.2/pixi.min.mjs
https://pixijs.download/v6.5.0-rc.2/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.0-rc.2/docs/index.html

Changed
v6.4.2...v6.5.0-rc.2

6.5.0-rc - 2022-07-14This is a do-no-harm prerelease and to test new packages @ pixi/assets and @ pixi/node.
💾  Download
Development Build:

https://pixijs.download/v6.5.0-rc/pixi.js
https://pixijs.download/v6.5.0-rc/pixi.js.map
https://pixijs.download/v6.5.0-rc/pixi.mjs
https://pixijs.download/v6.5.0-rc/pixi.mjs.map

Production Build:

https://pixijs.download/v6.5.0-rc/pixi.min.js
https://pixijs.download/v6.5.0-rc/pixi.min.js.map
https://pixijs.download/v6.5.0-rc/pixi.min.mjs
https://pixijs.download/v6.5.0-rc/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.5.0-rc/docs/index.html

Changed
v6.4.2...v6.5.0-rc

6.4.2 - 2022-06-02💾  Download
Development Build:

https://pixijs.download/v6.4.2/pixi.js
https://pixijs.download/v6.4.2/pixi.js.map
https://pixijs.download/v6.4.2/pixi.mjs
https://pixijs.download/v6.4.2/pixi.mjs.map

Production Build:

https://pixijs.download/v6.4.2/pixi.min.js
https://pixijs.download/v6.4.2/pixi.min.js.map
https://pixijs.download/v6.4.2/pixi.min.mjs
https://pixijs.download/v6.4.2/pixi.min.mjs.map

Documentation:

https://pixijs.download/v6.4.2/docs/index.html

Changed
v6.4.0...v6.4.2
🔥 Hotfix

Fix: Resolves issue where "exports" broke Webpack (#8381) @ zwade

🐛  Fixed

Clarify that the object's mask must be in the subtree of its parent in the docs (#8378) @ lazarljubenovic

    from pixi.js GitHub release notes

Commit messages

Package name: pixi.js

48ab2f2 v6.5.2
4ccb3be Merge branch 'dev'
4b86c27 Add cross-compatible path utils for Assets (#8605)
c9e43d3 Add support for base64 images with Assets (#8559)
fdbdc45 Add pixijselementals.com to "Learn" section of main readme (#8581)
27889a1 Fix implementing test "should load texture array correctly" (#8578)
fca5a8e Fix documentations for PIXI.DisplayObject#childRemoved (#8582)
ac965dd Add missing SVG loader to Assets (#8574)
3c205ce Fix Assets' onProgress with multiple bundles (#8565)
0b06a7d Fix Assets' text-based loading of fnt BitmapFonts (#8568)
6f136de Fix jittering caused by incorrect BitmapText text width (#8536)
e514f65 Fix typo in Resolver basePath setter (#8569)
e02c696 Loosen Graphics.drawPolygon types to use IPointData (#8573)
eb64a3e Add installation error help to readme (#8563)
d38270f Add support for base64 images with Assets (#8559)
fd9c930 Update package-lock.json
b095861 Fix more uses of document.createElement('canvas') (#8523)
a344b58 v6.5.1
27365ba Hotfix: Make sure core isn't bundled in ticker, canvas-sprite, canvas-mesh (#8527)
63b9f0c v6.5.0
bff5c47 Move VERSION to core instead of bundle (#8520)
1db04bb Fix LoaderResource tests (#8518)
6fc416e Fix app and ismobilejs typings (#8517)
611ca6a v6.5.0-rc.4

Compare

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

Updating dependencies in https://github.com/equinor/esv-intersection/pull/488
Will cover this upgrade, closing.

authors: Brynjulf ovineq

repo: equinor/esv-intersection


text:
fix: fetch available operating systems from azure

..Instead of the hard coded list

the list is currently hard coded

repo: equinor/sepes-api


text:
Add trait syntax

Add trait features. For more information, see the documentation.
TODOs:

[x] Add Trait function
[x] Implement trait checking

[x] type check
[x] side effect check
[x] ownership check

[x] Implement trait code generating

Implemented in v0.5.0.

repo: erg-lang/erg


text:
added sqlite3_serialize() and sqlite3_deserialize() (src)

Opening this PR for discussion.  I'm not sure about the approach, or if there are additional requirements to get a change like this accepted.
The raw additions seem heavy compared to its other methods, but I tried to take a similar stance of handling all memory management there.  Since the sqlite flags for these functions are related to memory management, they are not exposed in the raw api.  The support for Stream is a simple, standard way to avoid a buffer, but it is a new reference to System.IO.

From an initial read, this is nice work.  Thanks for submitting it.  I may still have feedback or requested changes when I go through it more closely, which I hope to get done soon.

Sorry for the long delay in reviewing this.

In principle, I have to push back on the use of System.IO.Stream.  Anything that high-level is usually omitted from this library, with the expectation that upper layers will provide it.

I'm staring at the deserialize call that accepts a ReadOnlySpan and then allocates a block and copies it.  That just feels wrong.  I haven't actually used the sqlite3_deserialize() API, so I've been reading the docs, and I sort of see why you did things this way.  But it raises questions as I look at the code.

Once we get the code looking okay for merge, I'll be asking for this PR to include test cases.

See #547

authors: ericsink garthmz

license_source: bigquery


text:
Issue while creating ONLINE indexes for localhost.

Discussed in https://github.com/erikbra/grate/discussions/576

Originally posted by anuksap August 20, 2024
Hello Team,
I was trying to migrate from rh to grate.
So I executed grate command locally to see changes on localhost . But it got failed for online indexes.
When I did ONLINE = OFF it works. But rh works totally fine for Online = ON.
Could you please assist if anything I am missing.
Below are the snippets from logs
Online index operations can only be performed in Enterprise edition of SQL Server or Azure SQL Edge.

That is by design of SQL Server and not something Grate can change.
Doing a index create or rebuild with Index ONLINE = ON is an enterprise feature
Microsoft has publish the difference between the editions on Editions and supported features of SQL Server 2022
I think it will work in developer edition also.

repo: erikbra/grate


text:
tradelog does not display the correct item name mmoitems

I want the log to show items like this:
before:
https://imgur.com/g81zkoY
affer:
Roguez18 received 1x SWORD.AAA
image and mmoitems folder:
https://imgur.com/RIrh9pB
https://imgur.com/CvjcrPB

thank Erik <3

nothing seems to have changed

name item:

repo: erikzimmermann/TradeSystem


text:
Notes: Mixtape 09

Title (as of 20210403): I Know What It Takes to Be Invincible
Versions:
20191110 (New), 20191112 (Repeat)?, 20200531 (Archive), 20201108 (Updated)
Other broadcasts: 20191222?, 20200109?, 20200227, 20200419, 20200707, 20200927

Timecode
Tag

#20200119_20.00:00:00.000
FOR-BIDDEN

#20200119_20.00:00:22.533
ORIGINAL

#20200119_20.00:00:47.633
VIDEWO

#20200119_20.00:01:05.533
HANG LUNG WAVE

#20200119_20.00:01:30.700
HARRY LOOK

#20200119_20.00:02:41.533
EZ MOVIE

#20200119_20.00:03:15.367
Commercial block 1

#20200119_20.00:03:34.433
JOC

#20200119_20.00:03:51.200
TBS art

#20200119_20.00:05:55.066
Spiderman

#20200119_20.00:07:39.533
JOCX

#20200119_20.00:08:27.600
Atari Lynx BOB

#20200119_20.00:11:06.666
My pet monster

#20200119_20.00:11:43.933
IFD

#20200119_20.00:13:20.200
TIME GANG nukes

#20200119_20.00:14:19.333
Commercial block

#20200119_20.00:14:49.500
IFD

#20200119_20.00:16:14.567
Salamander credits

#20200119_20.00:18:22.167
Zoomby

#20200119_20.00:20:46.634
IFD

#20200119_20.00:23:53.533
Eagle baseball

#20200119_20.00:25:25.066
Stan fat wife

#20200119_20.00:26:07.034
Commercial block

#20200119_20.00:26:20.167
MegaKidsTV

#20200119_20.00:28:24.400
For your eyes only

#20200119_20.00:29:19.800
IFD

#20200119_20.00:29:48.500
Photoshop

#20200119_20.00:30:14.733
Undefeatable

#20200119_20.00:35:11.066
Commercial block

#20200119_20.00:35:34.567
TV Science Report NEC

#20200119_20.00:36:34.533
IFD

#20200119_20.00:38:24.800
MegaKidsTV

#20200119_20.00:39:34.133
1000 slaps

#20200119_20.00:40:08.567
Jushin Liger v Crab

#20200119_20.00:52:14.300
IFD

#20200119_20.00:52:47.933
Diff IFD?

#20200119_20.00:53:58.866
Kamen Rider

#20200119_20.00:56:28.634
IFD

#20200119_20.01:01:25.834
Ultraman Balls

#20200119_20.01:02:37.466
IFD

#20200119_20.01:04:20.200
ROBOWAR

#20200119_20.01:04:55.866
Commercial block

#20200119_20.01:05:29.167
RO-BOXER

#20200119_20.01:07:24.100
Anime initial d?

#20200119_20.01:07:36.333
Ultra monsters cute

#20200119_20.01:08:04.700
Commercial Block

#20200119_20.01:08:23.900
IFD knife juggler

#20200119_20.01:10:23.967
DOOT DOOT

#20200119_20.01:10:36.266
Fatal Command creek

#20200119_20.01:16:47.333
SEASIDE

#20200119_20.01:17:04.033
IFD

#20200119_20.01:22:38.033
MOG ROG

#20200119_20.01:23:10.133
IFD ninjitsu

#20200119_20.01:28:18.800
PROJECTOR TOWER

#20200119_20.01:28:35.967
IFD Morna Lee

#20200119_20.01:31:32.733
BERL


text:
mdbx_chk: do Main dbi full-check at start

Example long-running mdbx_chk which I interrupted by Ctrl+C in the middle:
mdbx_chk v0.10.5-0-gedda9515 (2021-10-13T16:35:26+03:00, T-31713895aac05dd55b3ebc8cadd419f96b38de54)
Running for /evo/mainnet/chaindata in 'read-only' mode...
 ~ skipped update meta.geo in recovery mode: from l3-n140401953-u536870912/s1048576-g524288, to l3-n140401953-u536870912/s1-g524288
 - monopolistic mode
 - current boot-id afbd54fddf3ad801-8106c58c535b4926
 - pagesize 4096 (4096 system), max keysize 1980..2022, max readers 118
 - mapsize 2199023255552 (2.00 Tb)
 - dynamic datafile: 12288 (12.00 Kb) .. 2199023255552 (2.00 Tb), +2147483648 (2.00 Gb), -4096 (4.00 Kb)
 - current datafile: 575086399488 (535.59 Gb), 140401953 pages
 - meta-0: steady txn#67409, tail, forced for checking
 - meta-1: steady txn#67411, head
 - meta-2: steady txn#67410, stay
 - skip checking meta-pages since the 0 is selected for verification
 - transactions: recent 67411, selected for verification 67409, lag 2
Skipping b-tree walk...
Processing '@MAIN'...
 - key-value kind: usual-key => single-value
 - last modification txn#67408
 - summary: 44 records, 0 dups, 526 key's bytes, 2112 data's bytes, 0 problems
Processing '@GC'...
 - key-value kind: ordinal-key => single-value
 - last modification txn#67408
 - fixed key-size 8
 - summary: 494 records, 0 dups, 3952 key's bytes, 26776204 data's bytes, 0 problems
 - space: 536870912 total pages, backed 140401953 (26.2%), allocated 140401953 (26.2%), available 403162516 (75.1%)
 - skip check used and gc pages (btree-traversal with monopolistic or read-write mode only)
Processing 'AccountChangeSet'...
 - key-value kind: usual-key => multi-value
 - last modification txn#67408
 - summary: 28621309 records, 28531308 dups, 228970472 key's bytes, 848425652 data's bytes, 0 problems
Processing 'AccountHistory'...
 - key-value kind: usual-key => single-value
 - last modification txn#67408
 - summary: 16000293 records, 0 dups, 448008204 key's bytes, 765509238 data's bytes, 0 problems
Processing 'BittorrentInfo'...
 - key-value kind: usual-key => single-value
 - last modification txn#4
 - summary: 0 records, 0 dups, 0 key's bytes, 0 data's bytes, 0 problems
Processing 'BlockBody'...
 - key-value kind: usual-key => single-value
 - last modification txn#67408
 - summary: 13446756 records, 0 dups, 537870240 key's bytes, 747138407 data's bytes, 0 problems
Processing 'BlockTransaction'...
 - key-value kind: usual-key => single-value
 - last modification txn#67408

^C - interrupted by signal
 - summary: 309979899 records, 0 dups, 2479839192 key's bytes, 52642179159 data's bytes, 0 problems
No error is detected, elapsed 91.456 seconds
mdbx_chk v0.10.5-0-gedda9515 (2021-10-13T16:35:26+03:00, T-31713895aac05dd55b3ebc8cadd419f96b38de54)
Running for /evo/mainnet/chaindata in 'read-only' mode...
 - monopolistic mode
 - current boot-id afbd54fddf3ad801-8106c58c535b4926
 - pagesize 4096 (4096 system), max keysize 1980..2022, max readers 118
 - mapsize 2199023255552 (2.00 Tb)
 - dynamic datafile: 12288 (12.00 Kb) .. 2199023255552 (2.00 Tb), +2147483648 (2.00 Gb), -4294967296 (4.00 Gb)
 - current datafile: 575086399488 (535.59 Gb), 140401953 pages
 - meta-0: steady txn#67409, tail
 - meta-1: steady txn#67411, head, forced for checking
 - meta-2: steady txn#67410, stay
 - skip checking meta-pages since the 1 is selected for verification
 - transactions: recent 67411, selected for verification 67411, lag 0
Skipping b-tree walk...
Processing '@MAIN'...
 - key-value kind: usual-key => single-value
 - last modification txn#67408
 ! corrupted leaf-page #77581853, mod-txnid 67410
 ! invalid page txnid (67410) for parent-page' txnid (67408)
 ! mdbx_cursor_get() failed, error 1 Operation not permitted
 - problems: different number of entries (1)
 - summary: 0 records, 0 dups, 0 key's bytes, 0 data's bytes, 1 problems
 ! abort processing '@GC' due to a previous error
 - space: 536870912 total pages, backed 140401953 (26.2%), allocated 140401953 (26.2%), available 396468959 (73.8%)
Total 4 errors are detected, elapsed 0.007 seconds.

As you can see, error ! corrupted leaf-page #77581853, mod-txnid 67410 was found at the end.
Is it possible to move (or add) this check (of Main dbi) to the start of mdbx_chk work?
Main dbi is small - likely it will be cheap. But, such move will allow mdbx_chk "fail fast" on this scenarios. (to find good meta-page faster).

How about moving this check from end to start of mdbx_chk?

How about moving this check from end to start of mdbx_chk?

No, since this is unreasonable.
In general, for a complete check, it is always necessary to first walk a page tree, and only if successful, then walk an entries via cursor.

However, with this database I saw a problem related to #238, i.e. seems that:

some time you ran this DB with v0.10.5;
then was commit 3 transactions with some release early than v0.10.5;
and at the the end have checked it by mdbx_chk v0.10.5.

At a whole this gave a false-positive diagnosis of database corruption - I'll think about what to do.

At a whole this gave a false-positive diagnosis of database corruption - I'll think about what to do.

@AskAlexSharov, any ideas are welcome.

for a complete check - yes, but before complete check and switch meta-page - there is another step "to find which meta-page are for sure bad, and don't run complete check for them", because complete check is long. But i'm fine with "no".

authors: AskAlexSharov erthink

repo: erthink/libmdbx


text:
能不能直接做成脚本啊

直接传参设置mirror

这里的内容范围比较广，做成通用脚本并不容易，不过可以思考思考

https://github.com/RubyMetric/chsrc

authors: eryajf fengzhao

repo: eryajf/Thanks-Mirror


text:
Can not display video thumb.

When I try to pick videos only, it cannot display video thumbs, and check Logcat it shows:
2020-07-06 12:48:59.018 16674-16674/com.example.test W/Glide: Failed to find GeneratedAppGlideModule. You should include an annotationProcessor compile dependency on com.github.bumptech.glide:compiler in your application and a @GlideModule annotated AppGlideModule implementation or LibraryGlideModules will be silently ignored
2020-07-06 12:49:01.044 16674-16674/com.example.test W/Glide: Load failed for content://media/external/images/media/1681 with size [358x358]
    class com.bumptech.glide.load.engine.GlideException: Failed to load resource
    There were 3 causes:
    java.io.FileNotFoundException(No entry for content://media/external/images/media/1681)
    java.io.FileNotFoundException(No entry for content://media/external/images/media/1681)
    java.io.FileNotFoundException(No entry for content://media/external/images/media/1681)
     call GlideException#logRootCauses(String) for more detail
      Cause (1 of 4): class com.bumptech.glide.load.engine.GlideException: Fetching data failed, class java.io.InputStream, LOCAL
    There was 1 cause:
    java.io.FileNotFoundException(No entry for content://media/external/images/media/1681)
     call GlideException#logRootCauses(String) for more detail
        Cause (1 of 1): class java.io.FileNotFoundException: No entry for content://media/external/images/media/1681
      Cause (2 of 4): class com.bumptech.glide.load.engine.GlideException: Fetching data failed, class android.os.ParcelFileDescriptor, LOCAL
    There was 1 cause:
    java.io.FileNotFoundException(No entry for content://media/external/images/media/1681)
     call GlideException#logRootCauses(String) for more detail
        Cause (1 of 1): class java.io.FileNotFoundException: No entry for content://media/external/images/media/1681
      Cause (3 of 4): class com.bumptech.glide.load.engine.GlideException: Fetching data failed, class android.content.res.AssetFileDescriptor, LOCAL
    There was 1 cause:
    java.io.FileNotFoundException(No entry for content://media/external/images/media/1681)
     call GlideException#logRootCauses(String) for more detail
        Cause (1 of 1): class java.io.FileNotFoundException: No entry for content://media/external/images/media/1681
      Cause (4 of 4): class com.bumptech.glide.load.engine.GlideException: Failed LoadPath{HierarchicalUri->Object->Drawable}, LOCAL
        Cause (1 of 2): class com.bumptech.glide.load.engine.GlideException: Failed DecodePath{HierarchicalUri->Drawable->Drawable}
        Cause (2 of 2): class com.bumptech.glide.load.engine.GlideException: Failed DecodePath{HierarchicalUri->Bitmap->Drawable}
2020-07-06 12:49:01.048 16674-16674/com.example.test I/Glide: Root cause (1 of 3)
    java.io.FileNotFoundException: No entry for content://media/external/images/media/1681
        at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel(DatabaseUtils.java:144)
        at android.content.ContentProviderProxy.openTypedAssetFile(ContentProviderNative.java:704)
        at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1412)
        at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1249)
        at android.content.ContentResolver.openInputStream(ContentResolver.java:969)
        at com.bumptech.glide.load.data.StreamLocalUriFetcher.loadResourceFromUri(StreamLocalUriFetcher.java:74)
        at com.bumptech.glide.load.data.StreamLocalUriFetcher.loadResource(StreamLocalUriFetcher.java:50)
        at com.bumptech.glide.load.data.StreamLocalUriFetcher.loadResource(StreamLocalUriFetcher.java:13)
        at com.bumptech.glide.load.data.LocalUriFetcher.loadData(LocalUriFetcher.java:44)
        at com.bumptech.glide.load.engine.SourceGenerator.startNextLoad(SourceGenerator.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNext(SourceGenerator.java:63)
        at com.bumptech.glide.load.engine.DecodeJob.runGenerators(DecodeJob.java:310)
        at com.bumptech.glide.load.engine.DecodeJob.decodeFromRetrievedData(DecodeJob.java:434)
        at com.bumptech.glide.load.engine.DecodeJob.onDataFetcherReady(DecodeJob.java:390)
        at com.bumptech.glide.load.engine.SourceGenerator.onDataReadyInternal(SourceGenerator.java:148)
        at com.bumptech.glide.load.engine.SourceGenerator$1.onDataReady(SourceGenerator.java:76)
        at com.bumptech.glide.load.data.mediastore.ThumbFetcher.loadData(ThumbFetcher.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNextLoad(SourceGenerator.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNext(SourceGenerator.java:63)
        at com.bumptech.glide.load.engine.DecodeJob.runGenerators(DecodeJob.java:310)
        at com.bumptech.glide.load.engine.DecodeJob.runWrapped(DecodeJob.java:279)
        at com.bumptech.glide.load.engine.DecodeJob.run(DecodeJob.java:234)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
        at com.bumptech.glide.load.engine.executor.GlideExecutor$DefaultThreadFactory$1.run(GlideExecutor.java:393)
2020-07-06 12:49:01.052 16674-16674/com.example.test I/Glide: Root cause (2 of 3)
    java.io.FileNotFoundException: No entry for content://media/external/images/media/1681
        at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel(DatabaseUtils.java:144)
        at android.content.ContentProviderProxy.openTypedAssetFile(ContentProviderNative.java:704)
        at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1412)
        at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1249)
        at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1172)
        at com.bumptech.glide.load.data.FileDescriptorLocalUriFetcher.loadResource(FileDescriptorLocalUriFetcher.java:20)
        at com.bumptech.glide.load.data.FileDescriptorLocalUriFetcher.loadResource(FileDescriptorLocalUriFetcher.java:12)
        at com.bumptech.glide.load.data.LocalUriFetcher.loadData(LocalUriFetcher.java:44)
        at com.bumptech.glide.load.engine.SourceGenerator.startNextLoad(SourceGenerator.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNext(SourceGenerator.java:63)
        at com.bumptech.glide.load.engine.DecodeJob.runGenerators(DecodeJob.java:310)
        at com.bumptech.glide.load.engine.DecodeJob.onDataFetcherFailed(DecodeJob.java:408)
        at com.bumptech.glide.load.engine.SourceGenerator.onLoadFailedInternal(SourceGenerator.java:160)
        at com.bumptech.glide.load.engine.SourceGenerator$1.onLoadFailed(SourceGenerator.java:83)
        at com.bumptech.glide.load.data.LocalUriFetcher.loadData(LocalUriFetcher.java:49)
        at com.bumptech.glide.load.engine.SourceGenerator.startNextLoad(SourceGenerator.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNext(SourceGenerator.java:63)
        at com.bumptech.glide.load.engine.DecodeJob.runGenerators(DecodeJob.java:310)
        at com.bumptech.glide.load.engine.DecodeJob.decodeFromRetrievedData(DecodeJob.java:434)
        at com.bumptech.glide.load.engine.DecodeJob.onDataFetcherReady(DecodeJob.java:390)
        at com.bumptech.glide.load.engine.SourceGenerator.onDataReadyInternal(SourceGenerator.java:148)
        at com.bumptech.glide.load.engine.SourceGenerator$1.onDataReady(SourceGenerator.java:76)
        at com.bumptech.glide.load.data.mediastore.ThumbFetcher.loadData(ThumbFetcher.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNextLoad(SourceGenerator.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNext(SourceGenerator.java:63)
        at com.bumptech.glide.load.engine.DecodeJob.runGenerators(DecodeJob.java:310)
        at com.bumptech.glide.load.engine.DecodeJob.runWrapped(DecodeJob.java:279)
        at com.bumptech.glide.load.engine.DecodeJob.run(DecodeJob.java:234)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
        at com.bumptech.glide.load.engine.executor.GlideExecutor$DefaultThreadFactory$1.run(GlideExecutor.java:393)
2020-07-06 12:49:01.054 16674-16674/com.example.test I/Glide: Root cause (3 of 3)
    java.io.FileNotFoundException: No entry for content://media/external/images/media/1681
        at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel(DatabaseUtils.java:144)
        at android.content.ContentProviderProxy.openTypedAssetFile(ContentProviderNative.java:704)
        at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1412)
        at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1249)
        at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:1172)
        at com.bumptech.glide.load.data.AssetFileDescriptorLocalUriFetcher.loadResource(AssetFileDescriptorLocalUriFetcher.java:20)
        at com.bumptech.glide.load.data.AssetFileDescriptorLocalUriFetcher.loadResource(AssetFileDescriptorLocalUriFetcher.java:11)
        at com.bumptech.glide.load.data.LocalUriFetcher.loadData(LocalUriFetcher.java:44)
        at com.bumptech.glide.load.engine.SourceGenerator.startNextLoad(SourceGenerator.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNext(SourceGenerator.java:63)
        at com.bumptech.glide.load.engine.DecodeJob.runGenerators(DecodeJob.java:310)
        at com.bumptech.glide.load.engine.DecodeJob.onDataFetcherFailed(DecodeJob.java:408)
        at com.bumptech.glide.load.engine.SourceGenerator.onLoadFailedInternal(SourceGenerator.java:160)
        at com.bumptech.glide.load.engine.SourceGenerator$1.onLoadFailed(SourceGenerator.java:83)
        at com.bumptech.glide.load.data.LocalUriFetcher.loadData(LocalUriFetcher.java:49)
        at com.bumptech.glide.load.engine.SourceGenerator.startNextLoad(SourceGenerator.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNext(SourceGenerator.java:63)
        at com.bumptech.glide.load.engine.DecodeJob.runGenerators(DecodeJob.java:310)
        at com.bumptech.glide.load.engine.DecodeJob.onDataFetcherFailed(DecodeJob.java:408)
        at com.bumptech.glide.load.engine.SourceGenerator.onLoadFailedInternal(SourceGenerator.java:160)
        at com.bumptech.glide.load.engine.SourceGenerator$1.onLoadFailed(SourceGenerator.java:83)
        at com.bumptech.glide.load.data.LocalUriFetcher.loadData(LocalUriFetcher.java:49)
        at com.bumptech.glide.load.engine.SourceGenerator.startNextLoad(SourceGenerator.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNext(SourceGenerator.java:63)
        at com.bumptech.glide.load.engine.DecodeJob.runGenerators(DecodeJob.java:310)
        at com.bumptech.glide.load.engine.DecodeJob.decodeFromRetrievedData(DecodeJob.java:434)
        at com.bumptech.glide.load.engine.DecodeJob.onDataFetcherReady(DecodeJob.java:390)
        at com.bumptech.glide.load.engine.SourceGenerator.onDataReadyInternal(SourceGenerator.java:148)
        at com.bumptech.glide.load.engine.SourceGenerator$1.onDataReady(SourceGenerator.java:76)
        at com.bumptech.glide.load.data.mediastore.ThumbFetcher.loadData(ThumbFetcher.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNextLoad(SourceGenerator.java:70)
        at com.bumptech.glide.load.engine.SourceGenerator.startNext(SourceGenerator.java:63)
        at com.bumptech.glide.load.engine.DecodeJob.runGenerators(DecodeJob.java:310)
        at com.bumptech.glide.load.engine.DecodeJob.runWrapped(DecodeJob.java:279)
        at com.bumptech.glide.load.engine.DecodeJob.run(DecodeJob.java:234)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
        at com.bumptech.glide.load.engine.executor.GlideExecutor$DefaultThreadFactory$1.run(GlideExecutor.java:393)

Steps to Reproduce the Problem

in gradle

    compileSdkVersion 29
    minSdkVersion 24
    targetSdkVersion 29
implementation 'com.github.esafirm.android-image-picker:imagepicker:2.3.0'
implementation 'com.github.bumptech.glide:glide:4.11.0'

in Activity

ImagePicker.create(ReadyCreationActivity.this)
                    .includeVideo(true)
                    .onlyVideo(true)
                    .start();

Specifications

Image Picker Version:2.3.0
Android OS: 8.0.0
Phone: Sony XZs

You can use the following for the fix in the meantime ..
implementation 'com.github.sr1dh4r:android-image-picker:2.3.4'

Issue Fixed :
Import ImagePicker as Module in Project and go to following class :
com.esafirm.imagepicker.features.imageloader
Please change DefaultImageLoader class loadImage Method to this and it works Fine (All Images & Videos Thumbs Showing)
@Override
public void loadImage(Image image, ImageView imageView, ImageType imageType) {

    Glide.with(imageView.getContext())
            .load(new File(image.getPath()).toString())
            .apply(RequestOptions
                    .placeholderOf(imageType == ImageType.FOLDER
                            ? R.drawable.ef_folder_placeholder
                            : R.drawable.ef_image_placeholder)
                    .error(imageType == ImageType.FOLDER
                            ? R.drawable.ef_folder_placeholder
                            : R.drawable.ef_image_placeholder)
            )
            .transition(DrawableTransitionOptions.withCrossFade())
            .into(imageView);
}

I am using version 2.3.2
This issue still persists.

This should be fixed in master

repo: esafirm/android-image-picker

license: mit


text:
Cannot find module 'concat-stream'

I've been running into this error recently with the node.js newrelic agent on startup.  Any ideas on what I'm doing wrong?
New Relic for Node.js was unable to bootstrap itself due to an error:
Error: Cannot find module 'concat-stream'
  at Function.Module._resolveFilename (module.js:338:15)
  at Function.Module._load (module.js:280:25)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/var/www/node-app/current/node_modules/newrelic/lib/aws-info.js:6:14)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (/var/www/node-app/current/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/var/www/node-app/current/node_modules/newrelic/lib/system-info.js:4:20)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (/var/www/node-app/current/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/var/www/node-app/current/node_modules/newrelic/lib/collector/facts.js:3:23)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (/var/www/node-app/current/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/var/www/node-app/current/node_modules/newrelic/lib/collector/api.js:4:13)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (/var/www/node-app/current/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/var/www/node-app/current/node_modules/newrelic/lib/agent.js:9:20)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (/var/www/node-app/current/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/var/www/node-app/current/node_modules/newrelic/index.js:58:17)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (/var/www/node-app/current/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/var/www/node-app/current/server/server.coffee:1:1)
  at Object.<anonymous> (/var/www/node-app/current/server/server.coffee:1:1)
  at Module._compile (module.js:456:26)

it seems like newrelic agent relies on concat-stream but is this something I have to install before running the nodejs-agent recipe?  I had gotten it to work for a few minutes without any problems and now I can't seem to get it working again...just see this error all the time now.

Hi @PurrBiscuit,
thanks for reaching out!
By the sounds of it the issue is not a cookbook issue, but an issue with New Relic for Node.js. It should resolve its dependencies, but perhaps it's safer running this past New Relic support.
Would you be able to run this past NR support and update the issue here with their feedback?
Thanks in advance for your help!
Kind regards,
David

authors: PurrBiscuit djoos

repo: escapestudios-cookbooks/newrelic


text:
Detect rotated faces

The number of faces in this image should be 4 rectangles, so why get -out file is 3 rectangles (-iou 0.1 or -iou 0.2)

-iou 0.1

-iou 0.2

Once the object rotation feature will be implemented this won't be an issue anymore.

Hey Endre. Thanks for the library. I too am wondering about detecting faces that are in a profile view.
I tested both eunseo.jpg and jimin3.jpg from this dataset https://github.com/Kagami/go-face-testdata without specifying an angle, but pigo didn't find a face.

Hey Nathan, that's true. I will try to investigate and get a workaround for this kind of limitation. Anyway i'm not really sure if the detector can detect 100% profile faces, but can detect deviations from face views.

Okay.

@esimov  any update on this?

Not yet, right now i'm working on WASM support. Afterwards i can check this issue.

@esimov Any idea whether it will be possible to support profile or semi-profile face images?

Any idea whether it will be possible to support profile or semi-profile face images?

Not yet!

I feel like this should be the top priority for now. Without rotation detection, performance on video streams is horrible even with the slightest movement of the head.

I have a few ideas in my mind how this issue could be resolved, but meantime any contribution is welcomed ;).

I am wondering if we could just train a new cascade dataset as explained here: https://github.com/nenadmarkus/pico/tree/master/gen/sample - using a dataset which includes faces that are in various degrees of profile/rotation? I am guessing there are some good datasets around at this point that include markers for these variations of faces?

The thing is that I don't really know if that this kind of dataset is available on the https://www.vision.caltech.edu/ which the training model is referring to.  The caltech_10k_webfaces contains only frontal faces, so not rotated faces. So in order to train the model with the rotated faces we need some dataset with rotated faces, but also using the format appropriate for picolrn.

Yes, definitely. I know about a few companies that have trained frontal+profile face cascades via Pico.

The question is from where did they obtained the training data? Did you know or somehow Nenand mentioned what kind of training data they used?

I notice in your code in the caltechfaces.py file you seem to be converting the eye data into bounding boxes, and many datasets already come with bounding boxes. I am wondering if this would be fairly straightforward...

Why this is important to you?

There are lots of resources for this, here is a good place to start: https://www.face-rec.org/databases/ - in particular I think this might be a good dataset to use? http://www.cs.tau.ac.il/~wolf/ytfaces/

Why this is important to you?

Because it's important to understand the requirements we need to satisfy to train a new cascade. In this case, as long as the bounding boxes in the dataset that we find to train with maintain the same aspect ratio, we can more or less "plug" them in to picolrn in the same way that Nenand did, even skipping a few steps in caltechfaces.py (because we don't have to generate our own bounding boxes).

Thanks for the links. BTW some of them are broken or outdated. Now, since you mentioned that you have discussed with Nenand and he told that a few companies have already trained with frontal+profile faces, the obvious question is doesn't he by any chance obtained such a cascade file?

I haven't got any updates from you regarding my question. Do you know by any chance if such cascade files are somehow available? Or should I contact personally Nenad.

No they are not available as far as I understand as these are companies and they cannot share their intellectual property like that - these are things you would have to train yourself, but luckily Nenand has really great documentation and information on how to do that, all of the ingredients are available, you just gotta put the pieces together.

authors: ItsJasonPan esimov fengweiqiang kafan1986 kamranjon nathany olekukonko

repo: esimov/pigo


text:
Site redesign

@eslint/eslint-team Hi! @nogaraviv, @nzakas, and I want to share the progress we've made on the site redesign (focusing mostly on the homepage so far) and open it up to feedback from the team. Note that the documentation redesign is still being discussed.

We would love to hear your input!

Very nice in terms of the layout of the information, I like it a lot more then current homepage. I'm personally not a fan at all of the dark themes, though. I always turn them off in all of my editors. I know I'm in minority, but to me it feels unnatural. People have been reading black on white for a few centuries now, not white on black...

And for further info: this white-on-dark feeling is primarily for the homepage. Documentation pages would still have black-on-white (though with the black header).

Yes, sorry I didn't clarify that point!

I'm wondering if maybe the ESLint version should be on the left rather than
the right. How do people feel about that?
Any other thoughts?
On Wed, Feb 6, 2019 at 8:31 PM Kai Cataldo notifications@github.com wrote:

Yes, sorry I didn't clarify that point!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eslint/eslint.github.io/issues/537#issuecomment-461284822,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACWkoIZxZYvRaNrGIIF34Pj7hvF-ynkks5vK6wngaJpZM4ah-K-
.

--

Nicholas C. Zakas
@slicknet
Author, Principles of Object-Oriented JavaScript http://amzn.to/29Pmfrm
Author, Understanding ECMAScript 6 http://amzn.to/29K1mIy

I'm wondering if maybe the ESLint version should be on the left

I like that a lot. It’s a different level of navigation that Docs/Demo/Blog/About, and having it on the left a) makes the version more prominent and b) puts the package name and version right next to each other: “ESLint v5.12.0”.

I'd love to continue this discussion, given I'll now have time to dedicate to this. How would we like to move forward? Do we want to start with the initial design assets we currently have and tweak it as we go along, or do we want to try to find a designer we can actively work with (and compensate)? If we do the latter, it would be great to come up with initial design comps and then to be able to retain the designer for questions/working through unforeseen issues as we go along.

Do we have any assets for the screenshots above? If we do, I think we should just use that until we hire designer for the site re-design. I like the screenshots above a lot more than our current homepage.

Hi Kai!
I'd love to help continue this project and take it to completion.
Are you free Sunday to hop on a call? Think it'll be easier to chat things
through: see where we're at, share my availability to help, etc
Cheers,
Noga
On Fri, Nov 15, 2019, 7:40 AM Ilya Volodin notifications@github.com wrote:

Do we have any assets for the screenshots above? If we do, I think we
should just use that until we hire designer for the site re-design. I like
the screenshots above a lot more than our current homepage.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eslint/website/issues/537?email_source=notifications&email_token=ADT7PV3XGJUF44WVERUXSB3QT27HRA5CNFSM4GUH4K7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEFZ4BQ#issuecomment-554409478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADT7PV7E4VRQGTQY2TUR6LLQT27HRANCNFSM4GUH4K7A
.

@nogaraviv I’ll send you an email!

Please read this for theme choosing https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme

Closing due to age

authors: btmills ilyavolodin kaicataldo nogaraviv nzakas vitaly-zdanevich

repo: eslint/website


text:
esp32c6 needs bigger heap than esp32s3

My S3 can enable wifi just fine with the default heap, but C6 immediately runs out of memory:
C6:
[INFO] - Initializing Wifi driver
[INFO] - esp-wifi configuration Config { rx_queue_size: 16, tx_queue_size: 16, static_rx_buf_num: 32, dynamic_rx_buf_num: 16, static_tx_buf_num: 12, dynamic_tx_buf_num: 16, ampdu_rx_enable: 1, ampdu_tx_enable: 1, amsdu_tx_enable: 0, rx_ba_win: 8, max_burst_size: 0, country_code: "CN", country_code_operating_class: 0, mtu: 1492, heap_size: 65536, tick_rate_hz: 200, listen_interval: 3, beacon_timeout: 6, ap_beacon_timeout: 300, failure_retry_cnt: 1, scan_method: 0 }
[WARN] - Unable to allocate 2216 bytes
[WARN] - esp_wifi_init_internal(&G_CONFIG) returned an error: 257
[ERROR] - panicked at 'unwrap failed: esp_wifi ::
[ERROR] - initialize(EspWifiInitFor :: Wifi, resources.timer, resources.rng,
[ERROR] - resources.rcc, clocks,)'
[ERROR] - error: `WifiError(InternalError(EspErrNoMem))`

S3:
[INFO] - Initializing Wifi driver
[INFO] - esp-wifi configuration Config { rx_queue_size: 16, tx_queue_size: 16, static_rx_buf_num: 32, dynamic_rx_buf_num: 16, static_tx_buf_num: 12, dynamic_tx_buf_num: 16, ampdu_rx_enable: 1, ampdu_tx_enable: 1, amsdu_tx_enable: 0, rx_ba_win: 8, max_burst_size: 0, country_code: "CN", country_code_operating_class: 0, mtu: 1492, heap_size: 65536, tick_rate_hz: 200, listen_interval: 3, beacon_timeout: 6, ap_beacon_timeout: 300, failure_retry_cnt: 1, scan_method: 0 }
[INFO] - Wifi driver initialized

Increasing the heap size to 98304 immediately resolves this problem. My guess is that the various buffers might take up more space, maybe due to a different feature set, but might be good to dig into it a bit more.

The heap is now configurable via the config so I think we can close this now.

The heap size has been configurable some time before I opened this issue. I understand it's not exactly actionable, but the 1.5x memory requirement is still something that at least should be investigated, or at least acknowledge the problem. Because reserving a bit more than a quarter of available RAM may be a problem.

authors: MabezDev bugadani

repo: esp-rs/esp-wifi


text:
SPI operation failed when flashing .crt being not multiple of 4

:wave: I was trying to flash a x509 certificate bundle in a .crt format to 0x3c0000 address. Unfortunately, the tool returns the following error:

Error:   × The bootloader returned an error
├─▶ Error while running FlashDeflateEnd command
╰─▶ SPI operation failed

Talking to other guys on the team we hypothesized that we could have some padding problems, so I added a few bytes at the end. Surprisingly making the .crt file multiple of 4 solved the problem, and the espflash worked perfectly!
stat -c %s google.crt

before
after

3649 Bytes
3652 Bytes

Steps to reproduce the problem
openssl s_client -showcerts -connect google.com:443 </dev/null | sed -n -e '/-.BEGIN/,/-.END/ p' > google.pem
openssl x509 -outform der -in google.pem -out google.crt
espflash write-bin -p /dev/ttyACM0 -b 921600 0x3C0000 google.crt

[2023-07-03T14:49:58Z INFO ] Serial port: '/dev/ttyACM0'
[2023-07-03T14:49:58Z INFO ] Connecting...
[2023-07-03T14:49:58Z INFO ] Using flash stub
[2023-07-03T14:49:59Z WARN ] Setting baud rate higher than 115,200 can cause issues
Chip type:         esp32s3 (revision v0.1)
Crystal frequency: 40MHz
Flash size:        8MB
Features:          WiFi, BLE
MAC address:       dc:54:75:c3:01:18
[00:00:00] [========================================]       2/2       0x3C0000                                                                                Error:   × The bootloader returned an error
├─▶ Error while running FlashDeflateEnd command
╰─▶ SPI operation failed

Steps to fix the problem
openssl s_client -showcerts -connect google.com:443 </dev/null | sed -n -e '/-.BEGIN/,/-.END/ p' > google.pem
openssl x509 -outform der -in google.pem -out google.crt
dd if=/dev/zero of=google.crt bs=1 count=1 seek=3651
espflash write-bin -p /dev/ttyACM0 -b 921600 0x3C0000 google.crt

[2023-07-03T15:01:31Z INFO ] Serial port: '/dev/ttyACM0'
[2023-07-03T15:01:31Z INFO ] Connecting...
[2023-07-03T15:01:32Z INFO ] Using flash stub
[2023-07-03T15:01:32Z WARN ] Setting baud rate higher than 115,200 can cause issues
Chip type:         esp32s3 (revision v0.1)
Crystal frequency: 40MHz
Flash size:        8MB
Features:          WiFi, BLE
MAC address:       dc:54:75:c3:01:18
[00:00:00] [========================================]       2/2       0x3C0000

Additional information
I'm running on Ubuntu 22.04
$ uname -a
Linux ale 5.19.0-45-generic #46~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 7 15:06:04 UTC 20 x86_64 x86_64 x86_64 GNU/Linux

$ espflash --version
espflash 2.0.0

I was trying the flash on one the new Arduino Uno R4 WiFi (datasheet)

Hi! I just tried reproducing the issue and I was not able to:
❯ openssl s_client -showcerts -connect google.com:443 </dev/null | sed -n -e '/-.BEGIN/,/-.END/ p' > google.pem

depth=2 C = US, O = Google Trust Services LLC, CN = GTS Root R1
verify return:1
depth=1 C = US, O = Google Trust Services LLC, CN = GTS CA 1C3
verify return:1
depth=0 CN = *.google.com
verify return:1
DONE

❯ openssl x509 -outform der -in google.pem -out google.crt

❯ espflash write-bin -p /dev/ttyACM0 -b 921600 0x3C0000 google.crt

[2023-12-11T15:58:32Z INFO ] Serial port: '/dev/ttyACM0'
[2023-12-11T15:58:32Z INFO ] Connecting...
[2023-12-11T15:58:32Z INFO ] Using flash stub
[2023-12-11T15:58:33Z WARN ] Setting baud rate higher than 115,200 can cause issues
Chip type:         esp32s3 (revision v0.1)
Crystal frequency: 40MHz
Flash size:        8MB
Features:          WiFi, BLE
MAC address:       60:55:f9:f5:20:d4
[00:00:00] [========================================]       2/2       0x3C0000

❯ stat -c %s google.crt
3701

I also tried with other sizes:
❯ dd if=/dev/zero of=google.crt bs=1 count=1 seek=3748
1+0 records in
1+0 records out
1 byte copied, 1.329e-05 s, 75.2 kB/s

❯ stat -c %s google.crt
3749

❯ espflash write-bin -p /dev/ttyACM0 -b 921600 0x3C0000 google.crt

[2023-12-11T15:57:43Z INFO ] Serial port: '/dev/ttyACM0'
[2023-12-11T15:57:43Z INFO ] Connecting...
[2023-12-11T15:57:43Z INFO ] Using flash stub
[2023-12-11T15:57:44Z WARN ] Setting baud rate higher than 115,200 can cause issues
Chip type:         esp32s3 (revision v0.1)
Crystal frequency: 40MHz
Flash size:        8MB
Features:          WiFi, BLE
MAC address:       60:55:f9:f5:20:d4
[00:00:00] [========================================]       2/2       0x3C0000

I am using espflash with that latest main changes (commit 71d7a63). We did some changes in main, could you try reproducing it with this espflash version (cargo install espflash --git https://github.com/esp-rs/espflash --force) and see if the issue still persists for you @alessio-perugini?

@SergioGasquez Tested on 71d7a63 now it's working flawlessly! :rocket:

authors: SergioGasquez alessio-perugini

repo: esp-rs/espflash


text:
LoadLibraryExW failes on libclang.dll

When trying to run cargo build on Windows 10 after performing every step from the book I am getting an error:
Unable to find libclang: "the `libclang` shared library at C:\\Users\\Dmitrij\\.rustup\\toolchains\\esp\\xtensa-esp32-elf-clang\\esp-clang\\bin\\libclang.dll could not be opened: LoadLibraryExW failed"

The path to the file is correct, the file exists and is not corrupted.
Here is the full log:
D:\vats>cargo build
   Compiling bindgen v0.69.5
   Compiling embuild v0.32.0
   Compiling esp-idf-sys v0.35.0
   Compiling esp-idf-hal v0.44.1
   Compiling esp-idf-svc v0.49.1
   Compiling vats v0.1.0 (D:\vats)
The following warnings were emitted during compilation:

warning: esp-idf-sys@0.35.0: Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `cc` installed? (see https://docs.rs/cc/latest/cc/#compile-time-requirements for help)
warning: esp-idf-sys@0.35.0: Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `c++` installed? (see https://docs.rs/cc/latest/cc/#compile-time-requirements for help)
warning: esp-idf-sys@0.35.0: Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `cc` installed? (see https://docs.rs/cc/latest/cc/#compile-time-requirements for help)

error: failed to run custom build command for `esp-idf-sys v0.35.0`

Caused by:
  process didn't exit successfully: `D:\vats\target\debug\build\esp-idf-sys-794f3a5c7d9aa6c9\build-script-build` (exit code: 101)
  --- stdout
  cargo:rerun-if-env-changed=ESP_IDF_TOOLS_INSTALL_DIR
  cargo:rerun-if-env-changed=ESP_IDF_SDKCONFIG
  cargo:rerun-if-env-changed=ESP_IDF_SDKCONFIG_DEFAULTS
  cargo:rerun-if-env-changed=MCU
  cargo:rerun-if-env-changed=ESP_IDF_SYS_ROOT_CRATE
  cargo:rerun-if-env-changed=ESP_IDF_VERSION
  cargo:rerun-if-env-changed=ESP_IDF_REPOSITORY
  cargo:rerun-if-env-changed=ESP_IDF_CMAKE_GENERATOR
  cargo:rerun-if-env-changed=IDF_PATH
  cargo:rerun-if-env-changed=EXTRA-COMPONENTS
  cargo:rerun-if-env-changed=ESP_IDF_COMPONENTS
  cargo:rerun-if-env-changed=ESP_IDF_COMPONENT_MANAGER
  Python 3.13.0
  pip 24.3.1 from D:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\Lib\site-packages\pip (python 3.13)
  Requirement already satisfied: pip in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (24.3.1)
  Requirement already satisfied: setuptools in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (71.0.0)
  Collecting setuptools
    Using cached setuptools-75.6.0-py3-none-any.whl.metadata (6.7 kB)
  Using cached setuptools-75.6.0-py3-none-any.whl (1.2 MB)
  Installing collected packages: setuptools
    Attempting uninstall: setuptools
      Found existing installation: setuptools 71.0.0
      Uninstalling setuptools-71.0.0:
        Successfully uninstalled setuptools-71.0.0
  Successfully installed setuptools-75.6.0
  Looking in indexes: https://pypi.org/simple, https://dl.espressif.com/pypi
  Ignoring importlib_metadata: markers 'python_version < "3.8"' don't match your environment
  Collecting setuptools (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 3))
    Using cached https://dl.espressif.com/pypi/setuptools/setuptools-71.0.0-py3-none-any.whl (908 kB)
  Requirement already satisfied: packaging in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 4)) (24.2)
  Requirement already satisfied: click in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 7)) (8.1.7)
  Requirement already satisfied: pyserial in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 8)) (3.5)
  Requirement already satisfied: cryptography in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 9)) (41.0.7)
  Requirement already satisfied: pyparsing in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 10)) (3.2.0)
  Requirement already satisfied: pyelftools in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 11)) (0.31)
  Requirement already satisfied: idf-component-manager in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (2.0.4)
  Requirement already satisfied: esp-coredump in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 13)) (1.12.0)
  Requirement already satisfied: esptool in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 14)) (4.8.1)
  Requirement already satisfied: esp-idf-kconfig in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 15)) (1.4.0)
  Collecting esp-idf-kconfig (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 15))
    Using cached https://dl.espressif.com/pypi/esp-idf-kconfig/esp_idf_kconfig-1.4.3-py3-none-any.whl (44 kB)
  Requirement already satisfied: esp-idf-monitor in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 16)) (1.5.0)
  Requirement already satisfied: esp-idf-size in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 17)) (1.6.1)
  Requirement already satisfied: esp-idf-panic-decoder in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 18)) (1.2.1)
  Requirement already satisfied: pyclang in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 19)) (0.5.0)
  Requirement already satisfied: construct in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 20)) (2.10.70)
  Requirement already satisfied: freertos_gdb in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from -r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 23)) (1.0.3)
  Requirement already satisfied: colorama in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from click->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 7)) (0.4.6)
  Requirement already satisfied: cffi>=1.12 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from cryptography->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 9)) (1.17.1)
  Requirement already satisfied: pyyaml in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (6.0.2)
  Requirement already satisfied: requests in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (2.32.3)
  Requirement already satisfied: requests-file in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (2.1.0)
  Requirement already satisfied: requests-toolbelt in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (1.0.0)
  Requirement already satisfied: tqdm in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (4.67.1)
  Requirement already satisfied: jsonref in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (1.1.0)
  Requirement already satisfied: pydantic in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (2.10.2)
  Requirement already satisfied: pydantic-core in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (2.27.1)
  Requirement already satisfied: pydantic-settings in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (2.6.1)
  Requirement already satisfied: pygdbmi>=0.9.0.2 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from esp-coredump->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 13)) (0.11.0.0)
  Requirement already satisfied: bitstring!=4.2.0,>=3.1.6 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from esptool->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 14)) (4.2.3)
  Requirement already satisfied: ecdsa>=0.16.0 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from esptool->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 14)) (0.19.0)
  Requirement already satisfied: reedsolo<1.8,>=1.5.3 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from esptool->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 14)) (1.7.0)
  Requirement already satisfied: intelhex in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from esptool->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 14)) (2.3.0)
  Requirement already satisfied: kconfiglib>=13.7.1 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from esp-idf-kconfig->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 15)) (14.1.0)
  INFO: pip is looking at multiple versions of esp-idf-kconfig to determine which version is compatible with other requirements. This could take a while.
    Using cached https://dl.espressif.com/pypi/esp-idf-kconfig/esp_idf_kconfig-1.4.2-py3-none-any.whl (44 kB)
    Using cached https://dl.espressif.com/pypi/esp-idf-kconfig/esp_idf_kconfig-1.4.1-py3-none-any.whl (43 kB)
  Requirement already satisfied: rich in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from esp-idf-size->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 17)) (13.9.4)
  Requirement already satisfied: bitarray<3.0.0,>=2.9.0 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from bitstring!=4.2.0,>=3.1.6->esptool->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 14)) (2.9.3)
  Requirement already satisfied: pycparser in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from cffi>=1.12->cryptography->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 9)) (2.22)
  Requirement already satisfied: six>=1.9.0 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from ecdsa>=0.16.0->esptool->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 14)) (1.16.0)
  Requirement already satisfied: annotated-types>=0.6.0 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from pydantic->idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (0.7.0)
  Requirement already satisfied: typing-extensions>=4.12.2 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from pydantic->idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (4.12.2)
  Requirement already satisfied: python-dotenv>=0.21.0 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from pydantic-settings->idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (1.0.1)
  Requirement already satisfied: charset-normalizer<4,>=2 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from requests->idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (3.4.0)
  Requirement already satisfied: idna<4,>=2.5 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from requests->idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (3.10)
  Requirement already satisfied: urllib3<3,>=1.21.1 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from requests->idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (1.26.20)
  Requirement already satisfied: certifi>=2017.4.17 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from requests->idf-component-manager->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 12)) (2024.8.30)
  Requirement already satisfied: markdown-it-py>=2.2.0 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from rich->esp-idf-size->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 17)) (3.0.0)
  Requirement already satisfied: pygments<3.0.0,>=2.13.0 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from rich->esp-idf-size->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 17)) (2.18.0)
  Requirement already satisfied: mdurl~=0.1 in d:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\lib\site-packages (from markdown-it-py>=2.2.0->rich->esp-idf-size->-r D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt (line 17)) (0.1.2)
  Installing collected packages: setuptools
    Attempting uninstall: setuptools
      Found existing installation: setuptools 75.6.0
      Uninstalling setuptools-75.6.0:
        Successfully uninstalled setuptools-75.6.0
  Successfully installed setuptools-71.0.0
  Upgrading pip and setuptools...
  Skipping the download of D:\vats\.embuild\espressif\espidf.constraints.v5.2.txt because it was downloaded recently.
  Installing Python packages
   Constraint file: D:\vats\.embuild\espressif\espidf.constraints.v5.2.txt
   Requirement files:
    - D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt
  cargo:rerun-if-changed=D:\vats\sdkconfig.defaults
  cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `cc` installed? (see https://docs.rs/cc/latest/cc/#compile-time-requirements for help)
  cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `c++` installed? (see https://docs.rs/cc/latest/cc/#compile-time-requirements for help)
  cargo:warning=Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `cc` installed? (see https://docs.rs/cc/latest/cc/#compile-time-requirements for help)
  CMAKE_PREFIX_PATH_xtensa-esp32s3-espidf = None
  CMAKE_PREFIX_PATH_xtensa_esp32s3_espidf = None
  TARGET_CMAKE_PREFIX_PATH = None
  CMAKE_PREFIX_PATH = None
  CMAKE_xtensa-esp32s3-espidf = None
  CMAKE_xtensa_esp32s3_espidf = None
  TARGET_CMAKE = None
  CMAKE = None
  running: "cmake" "D:\\vats\\target\\xtensa-esp32s3-espidf\\debug\\build\\esp-idf-sys-bda06fad2065c1fc\\out" "-G" "Ninja" "-DCMAKE_TOOLCHAIN_FILE=D:\\vats\\.embuild\\espressif\\esp-idf\\v5.2.2\\tools\\cmake\\toolchain-esp32s3.cmake" "-DCMAKE_BUILD_TYPE=" "-DPYTHON=D:/vats/.embuild/espressif/python_env/idf5.2_py3.13_env/Scripts/python" "-DCMAKE_INSTALL_PREFIX=D:\\vats\\target\\xtensa-esp32s3-espidf\\debug\\build\\esp-idf-sys-bda06fad2065c1fc\\out" "-DCMAKE_C_FLAGS= -mlongcalls -fno-builtin-memcpy -fno-builtin-memset -fno-builtin-bzero -fno-builtin-stpcpy -fno-builtin-strncpy" "-DCMAKE_CXX_FLAGS= -mlongcalls -fno-builtin-memcpy -fno-builtin-memset -fno-builtin-bzero -fno-builtin-stpcpy -fno-builtin-strncpy" "-DCMAKE_ASM_FLAGS= -mlongcalls"
  -- git describe returned 'fatal: bad revision 'HEAD''
  -- Could not use 'git describe' to determine PROJECT_VER.
  -- Building ESP-IDF components for target esp32s3
  -- Checking Python dependencies...
  Python requirements are satisfied.
  Constraint file: D:\vats\.embuild\espressif\espidf.constraints.v5.2.txt
  Requirement files:
   - D:\vats\.embuild\espressif\esp-idf\v5.2.2\tools\requirements\requirements.core.txt
  Python being checked: D:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\Scripts\python.exe
  -- Project sdkconfig file D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/sdkconfig
  Loading defaults file D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/gen-sdkconfig.defaults...
  D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/gen-sdkconfig.defaults:2 CONFIG_COMPILER_OPTIMIZATION_DEFAULT was replaced with CONFIG_COMPILER_OPTIMIZATION_DEBUG
  Loading defaults file D:/vats/sdkconfig.defaults...
  -- Compiler supported targets: xtensa-esp-elf
  -- App "libespidf" version: 1
  -- Adding linker script D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/build/esp-idf/esp_system/ld/memory.ld
  -- Adding linker script D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/build/esp-idf/esp_system/ld/sections.ld.in
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom/esp32s3/ld/esp32s3.rom.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom/esp32s3/ld/esp32s3.rom.api.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom/esp32s3/ld/esp32s3.rom.libgcc.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom/esp32s3/ld/esp32s3.rom.newlib.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom/esp32s3/ld/esp32s3.rom.version.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/soc/esp32s3/ld/esp32s3.peripherals.ld
  -- Components: app_trace app_update bootloader bootloader_support bt cmock console cxx driver efuse esp-tls esp_adc esp_app_format esp_bootloader_format esp_coex esp_common esp_eth esp_event esp_gdbstub esp_hid esp_http_client esp_http_server esp_https_ota esp_https_server esp_hw_support esp_lcd esp_local_ctrl esp_mm esp_netif esp_netif_stack esp_partition esp_phy esp_pm esp_psram esp_ringbuf esp_rom esp_system esp_timer esp_wifi espcoredump esptool_py fatfs freertos hal heap http_parser idf_test ieee802154 json log lwip main mbedtls mqtt newlib nvs_flash nvs_sec_provider openthread partition_table perfmon protobuf-c protocomm pthread sdmmc soc spi_flash spiffs tcp_transport touch_element ulp unity usb vfs wear_levelling wifi_provisioning wpa_supplicant xtensa
  -- Component paths: D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/app_trace D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/app_update D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/bootloader D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/bootloader_support D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/bt D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/cmock D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/console D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/cxx D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/driver D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/efuse D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp-tls D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_adc D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_app_format D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_bootloader_format D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_coex D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_common D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_eth D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_event D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_gdbstub D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_hid D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_http_client D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_http_server D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_https_ota D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_https_server D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_hw_support D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_lcd D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_local_ctrl D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_mm D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_netif D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_netif_stack D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_partition D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_phy D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_pm D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_psram D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_ringbuf D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_system D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_timer D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_wifi D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/espcoredump D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esptool_py D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/fatfs D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/freertos D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/hal D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/heap D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/http_parser D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/idf_test D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/ieee802154 D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/json D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/log D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/lwip D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/main D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/mbedtls D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/mqtt D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/newlib D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/nvs_flash D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/nvs_sec_provider D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/openthread D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/partition_table D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/perfmon D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/protobuf-c D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/protocomm D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/pthread D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/sdmmc D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/soc D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/spi_flash D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/spiffs D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/tcp_transport D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/touch_element D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/ulp D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/unity D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/usb D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/vfs D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/wear_levelling D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/wifi_provisioning D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/wpa_supplicant D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/xtensa
  -- Configuring done
  -- Generating done
  -- Build files have been written to: D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/build
  running: "cmake" "--build" "D:\\vats\\target\\xtensa-esp32s3-espidf\\debug\\build\\esp-idf-sys-bda06fad2065c1fc\\out\\build" "--config" "MinSizeRel" "--parallel" "4"
  [1/7] Performing build step for 'bootloader'
  -- Building ESP-IDF components for target esp32s3
  -- Project sdkconfig file D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/sdkconfig
  -- Compiler supported targets: xtensa-esp-elf
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/soc/esp32s3/ld/esp32s3.peripherals.ld
  -- Bootloader project name: "bootloader" version: 1
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom/esp32s3/ld/esp32s3.rom.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom/esp32s3/ld/esp32s3.rom.api.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom/esp32s3/ld/esp32s3.rom.libgcc.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom/esp32s3/ld/esp32s3.rom.newlib.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/bootloader/subproject/main/ld/esp32s3/bootloader.ld
  -- Adding linker script D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/bootloader/subproject/main/ld/esp32s3/bootloader.rom.ld
  -- Components: bootloader bootloader_support efuse esp_app_format esp_bootloader_format esp_common esp_hw_support esp_rom esp_system esptool_py freertos hal log main micro-ecc newlib partition_table soc spi_flash xtensa
  -- Component paths: D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/bootloader D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/bootloader_support D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/efuse D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_app_format D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_bootloader_format D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_common D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_hw_support D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_rom D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esp_system D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/esptool_py D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/freertos D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/hal D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/log D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/bootloader/subproject/main D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/bootloader/subproject/components/micro-ecc D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/newlib D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/partition_table D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/soc D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/spi_flash D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/xtensa
  -- Configuring done
  -- Generating done
  -- Build files have been written to: D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/build/bootloader
  [0/1] Re-running CMake...
  [1/1] cmd.exe /C "cd /D D:\vats\target\xtensa-esp32s3-espidf\debug\build\esp-idf-sys-bda06fad2065c1fc\out\build\bootloader\esp-idf\esptool_py && D:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\Scripts\python D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/partition_table/check_sizes.py --offset 0x8000 bootloader 0x0 D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/build/bootloader/bootloader.bin"
  Bootloader binary size 0x5250 bytes. 0x2db0 bytes (36%) free.
  [2/5] Generating ld/sections.ld
  [3/5] Linking CXX executable libespidf.elf
  [4/5] Generating binary image from built executable
  esptool.py v4.8.1
  Creating esp32s3 image...
  Merged 2 ELF sections
  Successfully created esp32s3 image.
  Generated D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/build/libespidf.bin
  [5/5] cmd.exe /C "cd /D D:\vats\target\xtensa-esp32s3-espidf\debug\build\esp-idf-sys-bda06fad2065c1fc\out\build\esp-idf\esptool_py && D:\vats\.embuild\espressif\python_env\idf5.2_py3.13_env\Scripts\python D:/vats/.embuild/espressif/esp-idf/v5.2.2/components/partition_table/check_sizes.py --offset 0x8000 partition --type app D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/build/partition_table/partition-table.bin D:/vats/target/xtensa-esp32s3-espidf/debug/build/esp-idf-sys-bda06fad2065c1fc/out/build/libespidf.bin"
  libespidf.bin binary size 0x32900 bytes. Smallest app partition is 0x100000 bytes. 0xcd700 bytes (80%) free.
  cargo:root=D:\vats\target\xtensa-esp32s3-espidf\debug\build\esp-idf-sys-bda06fad2065c1fc\out
  cargo:rerun-if-changed=C:\Users\Dmitrij\.cargo\registry\src\index.crates.io-6f17d22bba15001f\esp-idf-sys-0.35.0\src\include\esp-idf\bindings.h
  cargo:rustc-env=EMBUILD_GENERATED_BINDINGS_FILE=D:\vats\target\xtensa-esp32s3-espidf\debug\build\esp-idf-sys-bda06fad2065c1fc\out\bindings.rs

  --- stderr
  Build configuration: BuildConfig {
      esp_idf_tools_install_dir: None,
      esp_idf_sdkconfig: None,
      esp_idf_sdkconfig_defaults: None,
      mcu: Some(
          "esp32s3",
      ),
      native: NativeConfig {
          esp_idf_version: Some(
              Tag(
                  "v5.2.2",
              ),
          ),
          esp_idf_repository: None,
          esp_idf_cmake_generator: None,
          idf_path: None,
          extra_components: [],
          esp_idf_components: None,
          esp_idf_component_manager: None,
      },
      esp_idf_sys_root_crate: None,
  }
  Using managed esp-idf repository: RemoteSdk { repo_url: None, git_ref: Tag("v5.2.2") }
  Using esp-idf v5.2.2 at 'D:\vats\.embuild\espressif\esp-idf\v5.2.2'
  Built components: xtensa, esp_ringbuf, efuse, esp_mm, driver, esp_pm, mbedtls, esp_bootloader_format, esp_app_format, bootloader_support, bootloader, esptool_py, partition_table, esp_partition, app_update, spi_flash, pthread, esp_system, esp_rom, hal, log, heap, soc, esp_hw_support, freertos, newlib, cxx, esp_common, esp_timer, app_trace, esp_event, nvs_flash, esp_phy, vfs, lwip, esp_netif_stack, esp_netif, wpa_supplicant, esp_coex, esp_wifi, bt, unity, cmock, console, http_parser, esp-tls, esp_adc, esp_eth, esp_gdbstub, esp_hid, tcp_transport, esp_http_client, esp_http_server, esp_https_ota, esp_https_server, esp_psram, esp_lcd, protobuf-c, protocomm, esp_local_ctrl, espcoredump, wear_levelling, sdmmc, fatfs, idf_test, ieee802154, json, mqtt, nvs_sec_provider, openthread, perfmon, spiffs, touch_element, ulp, usb, wifi_provisioning, main
  thread 'main' panicked at C:\Users\Dmitrij\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bindgen-0.69.5\lib.rs:622:31:
  Unable to find libclang: "the `libclang` shared library at C:\\Users\\Dmitrij\\.rustup\\toolchains\\esp\\xtensa-esp32-elf-clang\\esp-clang\\bin\\libclang.dll could not be opened: LoadLibraryExW failed"
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I have all dependencies installed and using the unmodified generated template with correct options on the correct board (ESP32-S3).
Does anyone have any ideas? I am stuck.

Hi!
Have you checked that C:\\Users\\Dmitrij\\.rustup\\toolchains\\esp\\xtensa-esp32-elf-clang\\esp-clang\\bin\\libclang.dll exists?? It should be there if the espup command succeeded, but just to verify.

Hi!
Have you checked that C:\\Users\\Dmitrij\\.rustup\\toolchains\\esp\\xtensa-esp32-elf-clang\\esp-clang\\bin\\libclang.dll exists?? It should be there if the espup command succeeded, but just to verify.

Yes, it exists:

The path to the file is correct, the file exists and is not corrupted.

I traced back the issue to the bindgen crate. Especially the ensure_libclang_is_loaded function in lib.rs. It fails on
clang_sys::load().expect("Unable to find libclang");

But when I run this function manually in a dummy project it loads without any issues, so it's not a problem with my configuration or setup I guess. At this point I have no clue what is going on.

Fixed by downgrading to a lower espup version.
https://github.com/esp-rs/espup/issues/440

authors: FssAy SergioGasquez

repo: esp-rs/rust-build


text:
Add search UI that allows closed, owner, reviewer, cc

https://codereview.chromium.org/search?

Fixed by https://chromium.googlesource.com/infra/infra/+/5b36a5c39ed5b1a395ce08ad5427d94adfdcca8b

repo: esprehn/chromium-codereview


text:
ESP32 i2s_write - Idle1 task starved? (IDFGH-569)

Hello ESP-IDF team,
I have a ported a little program to ESP32 and one issue on this is I have no control over when I can put in more samples to the i2s_write after the batch of buffers are being streamed to the I2S's codec.
Worse of all, one of the Idle tasks had been starved and it kept shouting to me the WDT hasn't been reset. Shutting the Idle WDT doesn't help much here as I have other stuff at the background to worry about.
For example:

// Generate Samples here at Task A in Core no. 1:
while (1)
{
GenerateSamplesHere(audio_buffer);
i2s_write(I2S_NUM_0, audio_buffer, sizeof(audio_buffer), &bytesWritten, portMAX_DELAY);
}

Console output after about 6~8 seconds:

E (14243) task_wdt: Task watchdog got triggered. The following tasks did
not reset the watchdog in time:
E (14243) task_wdt:  - IDLE0 (CPU 1)
E (14243) task_wdt: Tasks currently running:
E (14243) task_wdt: CPU 0: TaskB
E (14243) task_wdt: CPU 1: TaskA

Could it be possible if the task or function would yield or wait until the I2S has almost finished streaming the samples, and then place in some more samples instead of just continuously pushing into the I2S buffers?

Hi there,

Is it possible that there is another task running which is also monopolizing the CPU?

I have a summary of available tasks at that time:
1.) Task No.1 processing and pushing samples to the I2S module.

The processing takes 2.217ms for 256 samples.

2.) Task No.2 has a function that is being polled every 1ms (MIDI requirements).
Would (2) actually affect this too? Even if I remove (2) the Idle1 task was still starved.

Hi, sorry for the late response, is your problem solved now?
while (1) { GenerateSamplesHere(audio_buffer); i2s_write(I2S_NUM_0, audio_buffer, sizeof(audio_buffer), &bytesWritten, portMAX_DELAY); }
If (quote) generating the samples is taking longer than transmitting them, then the loop will be problematic. This loop may also be problematic if you have too large a buffer, I guess? Then i2s_write never fills the buffer and blocks before the watchdog causes a reset. (Because the idle task only runs if all other tasks on that CPU are blocked. If this loop never blocks at i2s_write, then the CPU will never go in idle task.) You can call explicitly vtaskdelay if you become too annoyed.
To avoid stutters you need to make data quickly so that the i2s doesn't have to use old data. It depends on your settings and you can calculate it yourself. For example, if you are using 2 channels and 16 bits and 36kHz sample rate, you need to make 36k216bits per second.
You can also set tx_desc_auto_clear in the config struct to 1 to make the i2s (try) to send nothing, instead of sending noise, when it runs out of data.

Hello @wilhelmw201 and ESP team,
Thanks for the assistance and apologies for the late reply. I have not been working on this issue for the time being - I highly suspect that the generating samples part require more computational power (preferably a Raspberry Pi) and could not be done in the ESP32 at a shorter time. I have already found an alternative in the meantime.

authors: nyh-workshop uncle-yong wilhelmw201

repo: espressif/esp-idf


text:
esp-idf可以用来开发ESP8266芯片吗? (IDFGH-2329)

请问一下:
esp-idf是否只是用来开发ESP32芯片, 能否用来开发ESP8266芯片?
如果要开发ESP8266芯片, 是否需下载另外的开发包, 如: ESP8266_RTOS_SDK-3.2
ESP8266芯片的SDK包新老版本配置都不一样,  搞得迷糊得很. 请指点, 谢谢!

Hi @hscxg,
Currently ESP-IDF doesn't have support for ESP8266. This may change in the future, but I can't give you a firm timeline when this might happen. For now, to develop for the ESP8266 you need to use the ESP8266_RTOS_SDK.
The ESP8266 RTOS SDK has been significantly refactored since version 2.0, more information on this here: https://github.com/espressif/esp8266_rtos_sdk#roadmap. If you find something in the documentation of the ESP8266 RTOS SDK which is confusing, please open an issue at https://github.com/espressif/esp8266_rtos_sdk/issues.

authors: hscxg igrr


text:
ESP SoftAP Prov HTTP request sample (IDFGH-3100)

Can someone provide a sample HTTP request to set SSID and password via Postman software or chrome for ESP SoftAP Prov example?
Note: I don't want to use ESP SoftAP Prov Android App

@25prithvi , the provisioning HTTP handlers use protobuf for data serialisation and so, it isn't that straight forward to be used from Postman. Please check the python script at https://github.com/espressif/esp-idf/tree/master/tools/esp_prov if Android app isn't an option for you.

@25prithvi Thanks for reporting, feel free to reopen if you still have issues/questions, thanks.

Hi,
I also would like to know if there is a option to configure the WiFi credentials via a "normal" http web interface.
Could you give me some information how to proceed regarding this?
Regards