Unwrap InvocationTargetException from coroutine data fetcher

Pull request checklist

[x] Please read our contributor guide
[ ] Consider creating a discussion on the discussion forum
first
[x] Make sure the PR doesn't introduce backward compatibility issues
[x] Make sure to have sufficient test cases

Pull Request type

[x] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Other (please describe):

Changes in this PR
Issue #753
Alternatives considered
N/A

Thanks for the contribution @LEECHHE!


Authentication data

Hi. Is there a way to send authentication (user and password) data with this library?
Thanks.

Is there any way to do that?

Not at this time.  If somebody wants to add it via a PR I would be happy to include it in the library.


Migrate documentation to Wiki

Organize the READMEs in the root and install directories into separate Wiki pages and CONTRIBUTING.md

Migrated the READMEs to the wiki, but TBD what to do with them (keep/modify/delete)

Decided to keep for this project, but will exclusively use the wiki for the new project


Example usage please

Folks,
Its not apparent what the correct usage is.
$ dyndump dump --filename="tableOut" --s3-bucket="myS3BucketName" --s3-prefix="" myTableName

https://github.com/gwatts/dyndump/pull/7


Add smoke test

While attempting to glue rudy to specs (slide-rs/specs#204), I discovered that this code:
use rudy::rudymap::RudyMap;

let mut map: RudyMap<u32, u32> = RudyMap::new();
map.insert(0, 0);
map.insert(1, 1);
map.insert(2, 2);
map.insert(3, 3);

fails with:
thread 'smoke_test' panicked at 'Unexpected insertion overflow', src/rudymap/results.rs:15:39

I packed linear insertion/removal into a rudimentary smoke test, which currently fails.

This is a good basic test to have. The bug was introduced from a pull request. Time to set up some CI!


refactor: unify serde and serde_derive under the derive feature

Description

Makes serde usage more unified across the project thanks to the derive feature
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (no code change)
[x] Refactor (refactoring production code)
[ ] Other

Checklist:

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

Codecov Report

Merging #57 (1543161) into main (848d8a5) will increase coverage by 0.26%.
The diff coverage is 12.50%.

@@            Coverage Diff             @@
##             main      #57      +/-   ##
==========================================
+ Coverage   41.14%   41.39%   +0.26%
==========================================
  Files          13       13
  Lines         812      807       -5
  Branches      210      210
==========================================
  Hits          334      334
+ Misses        371      364       -7
- Partials      107      109       +2

Impacted Files
Coverage Δ

git-cliff-core/src/config.rs
24.45% <0.00%> (ø)

git-cliff-core/src/release.rs
14.29% <0.00%> (-10.71%)
:arrow_down:

git-cliff-core/src/commit.rs
72.90% <50.00%> (ø)

git-cliff-core/src/repo.rs
29.17% <0.00%> (+2.09%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 848d8a5...1543161. Read the comment docs.


I did follow but failed

I did follow but failed, you can mail your source for Bootstrapping CakePHP Helpers 3.x succeeded. Mail your<EMAIL_ADDRESS>Thank you! Looking forward to help !!

Hi,
I am sorry but I did not understand what you failed at? If you want help installing the helpers, please explain what you have tried so far so that I can correct you.
Mikael

Hi,
I've followed your instructions but the results are not correct.
Result :

Thank you! Looking forward to help !!
2015-08-30 22:50 GMT+07:00 Mikaël Capelle<EMAIL_ADDRESS>
Hi,
I am sorry but I did not understand what you failed at? If you want help
installing the helpers, please explain what you have tried so far so that I
can correct you.
Mikael
—
Reply to this email directly or view it on GitHub
https://github.com/Holt59/cakephp3-bootstrap-helpers/issues/49#issuecomment-136155289
.

--
Vo Thanh Phat
Tel   :<PHONE_NUMBER> -<PHONE_NUMBER>
Add : Hoa Tien, Hoa Vang, Da Nang

You probably forget to include bootstrap css and js files into your project. The helpers does not include these files.


Any interest in getting this written in C?

If there is interest in getting this written in C code so it can be added to the firmware as a user c module I can help do that. I wanted to check if there is interest before doing the work.

@kdschlosser I'm interested in this! Though it might be a good idea to simply add support for the existing stdlib into the micropython-lib repo.

The reason why this would not be a good for for the standard micropython library is because not all of the MCU's that MicroPython supports can deal with float/double. It will also take up space for something not every user would use. It is easy to compile into MicroPython as C code using the USER_C_MODULE parameter when compiling.

The other thing is that I believe all of the modules located in the micropython-lib are python source files.
The reason why I asked about writing it as a C module is for speed and also memory use.

The reason why this would not be a good for for the standard micropython library is because not all of the MCU's that MicroPython supports can deal with float/double.

Really? Do you have a reference link to the docs for this? I can't seem to find it.
https://docs.micropython.org/en/latest/genrst/builtin_types.html#float

It will also take up space for something not every user would use. It is easy to compile into MicroPython as C code using the USER_C_MODULE parameter when compiling.

The libraries in micropython-lib are all optional and must be included explicity, they would not take up more space for everyone.

The other thing is that I believe all of the modules located in the micropython-lib are python source files.

Hm, that does appear to be the case. Kind of unfortunate, but likely a limitation of them being easily importable without requiring cross compilation.

The reason why I asked about writing it as a C module is for speed and also memory use.

Well, this repo hasn't seen an update in 3 years, so perhaps it makes sense to create a new one that is just a micropython specific C-module implementation of decimal.Decimal from stdlib? I'd certainly use it.

Really? Do you have a reference link to the docs for this? I can't seem to find it.

Search the MicroPython source for MICROPY_PY_BUILTINS_FLOAT

The libraries in micropython-lib are all optional and must be included explicity, they would not take up more space for everyone.

micropython-lib is a submodule of MicroPython so anything that is included in micropython-lib takes up space in the firmware, see here
importing a module take up RAM where as baking it into the firmware takes up flash space which is what happens even if a module goes unused.

Well, this repo hasn't seen an update in 3 years, so perhaps it makes sense to create a new one that is just a micropython specific C-module implementation of decimal.Decimal from stdlib? I'd certainly use it.

Regardless of whether it is done in this repo or a new one my question was to see if there would be interest in it. It would take a bit of work to duplicate the decimal module from CPython in MicroPython due to builtin functions being able to handle decimal.Decimal instances. If there is no interest then I will not bother doing all of the work when I only needed a tiny subset of the features to allow what I was working on to work correctly.

Search the MicroPython source for MICROPY_PY_BUILTINS_FLOAT

Ok, so there's a flag that can be used to enable it if supported, that's useful at least.

micropython-lib is a submodule of MicroPython so anything that is included in micropython-lib takes up space in the firmware, see here

Those are submodules, but it does not link to include all of micropython-lib.

Regardless of whether it is done in this repo or a new one my question was to see if there would be interest in it. It would take a bit of work to duplicate the decimal module from CPython in MicroPython due to builtin functions being able to handle decimal.Decimal instances. If there is no interest then I will not bother doing all of the work when I only needed a tiny subset of the features to allow what I was working on to work correctly.

Even if you get things started with a working first version, including only the essentials, that provides an example and place for other contributors (like me) to help fill in the rest.

I have to do some research to see if I am able to override the default behavior of some of the MicroPython builtins like round. I believe that I can because a really large portion of the MicroPython C API are function like macros which can be changed. I just need to locate what needs to be changed to be able to do it. If MicroPython supported more of the API that CPython has like the __round__ dunder method it would be a lot easier to alter the behavior of builtin functions like round. I am only using round as an example and i know there are other builtin functions that would need to have their behavior altered to deal with a decimal.Decimal instance.

round IO should be able to work with. I have to check things like the math functions to see if they are going to place nice nice or not. It all depends on whether or not the math model is coded to call the dunder methods or if they perform operations directly.. If it uses the dunder methods that is going to make life easier that's for sure. if not then I am going to have to probably write a large chunk of the module over so it either uses the dunder methods or takes into consideration the decimal.Decimal instance.


Add handling for class "Item" property "text" being null

Disclaimer
First pull request. Roast me.
Fixes #1
Problem
In the Item class, the init method was encountering an error on assigning self.text with values[1] when it was null, as it was calling strip on a null value
Why does the problem exist
I do not know what changed (if anything) in the sqlite schema to cause this new issue.
Solution
Adding a quick check to only set the property if the value is not none fixes the immediate issues, however the self.text property must exist for line 141, so I added an else clause to manually set to None.

Thanks, resolved with new version.


Fix ardupilot_gazebo install in ROS 2 Iron

Changes Made
The ardupilot_gazebo installation has recently been updated, which broke the Docker pipeline. This PR updates the installation to address these changes.
Testing
Basic build testing with Docker

Please target the main branch for development, we will backport the changes to iron for you if approved and if they don't break API.

don't tell me what to do mergify


fix: serve self-hosted fonts

This PR removes the fonts from the static/ folder and serve them using the webfonts plugin.

Are we actually using all of these font sub-types?  My browser downloads 15 woff2 files.

Indeed! I removed the variants that we are not using (directly at least).


Progress update for implementation of the ACCPM (issue #112).

This pull request reflects the progress I've made over the last week. So the computation of the analytic center given I input a strictly feasible initial point seems to work and this is reflected in ac_computation.ipynb. The file accpm_implementation.ipynb is very messy and has more been my personal 'lab', so to speak. I have also put the entire code for the implementation into accpm.py.
The major issue that I have been grappling with this week is the implementation of the phase I method used to find an initial point for the optimisation method which is used to compute the analytic center. I've spent quite a lot of time trying to get this to work, which involved first resolving some technical issues as well as writing some more code. At this point, it runs, but the optimization procedure is not producing expected results. I'm not sure if it is a technical issue or if I have a misunderstanding of the theory. The relevant file phase_i.ipynb will be contained in my next pull request but for the moment you can access it from my repository.
If you have any ideas or suggestions that might lead me in the right direction please let me know.
For now I will begin improving and testing other aspects of the code.

Changes Unknown when pulling 2ba6e1183494d499b9a690153e498831f3d5043b on davidjwu:master into ** on chengsoonong:master**.

Changes Unknown when pulling 2ba6e1183494d499b9a690153e498831f3d5043b on davidjwu:master into ** on chengsoonong:master**.

It seems accpm.py is the outcome of your development of notebooks accpm_implementation.ipynb and phase_i.ipynb, which is a good practice and I suggest you create another notebook to test every function in accpm.py so that bugs can be easily caught, e.g.,

in function analytic_center(), line 113, you may want to return the success flag of optimisation as you try to use it in function accpm(), line 175.
the return statement in function feasible(), line 122,  would lie outside of the for loop I guess.
Ideally only 3 files are included in this pull request, i.e., notes.tex, accpm.py and ac_computation.ipynb.

Changes Unknown when pulling 8bddcd5c489210557862f8104b63fee8243628ed on davidjwu:master into ** on chengsoonong:master**.

Hi Dawei, thank you for the feedback.
So I decided to change my approach for computing the analytic center entirely. I now compute it using the infeasible start Newton method. Prior to this, my intent was to compute it using a standard Newton method with initial point exactly the solution of the associated phase I optimization problem. Unfortunately, this didn't work as expected. Fortunately, however, this new approach seems to work quite well, given the polyhedron is not too small.

Changes Unknown when pulling 41eac2badb8f8da22de34b1205a31580b3be8e3b on davidjwu:master into ** on chengsoonong:master**.

Changes Unknown when pulling 8fdce73027551120f32be8a574fce12ab586e553 on davidjwu:master into ** on chengsoonong:master**.

Changes Unknown when pulling 609e8398842358ea4015690d965039e502b2393c on davidjwu:master into ** on chengsoonong:master**.

Changes Unknown when pulling 682b679d5da55c6eaa625e6d7c4d847805b2a522 on davidjwu:master into ** on chengsoonong:master**.


chore(main): release 0.0.10

:robot: I have created a release beep boop
0.0.10 (2024-06-04)
What's Changed

Change from LiteralString to Literal (typing) by @dSupertramp in https://github.com/QuivrHQ/MegaParse/pull/21
chore: Add Dockerfile and Makefile for project setup by @StanGirard in https://github.com/QuivrHQ/MegaParse/pull/23

New Contributors

@dSupertramp made their first contribution in https://github.com/QuivrHQ/MegaParse/pull/21

Full Changelog: https://github.com/QuivrHQ/MegaParse/compare/v0.0.9...v0.0.10

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/QuivrHQ/MegaParse/releases/tag/v0.0.10 :sunflower:


Add sandbox annotation

@yegle GitHub says there's no changes?

@yegle GitHub says there's no changes?

Oops, I should send a CL for the verification server.


rename template

Applied mkpr on package.json
sed s/template-pacman"/template-npm-pkgbuild"/

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

npm package (@latest dist-tag)
v6.4.5
GitHub release

Your semantic-release bot :package::rocket:


Development

Cleaned up warnings.
Include swift build command output with --verbose.
Updated dependencies.

Cleaned up warnings.
Include swift build command output with --verbose.
Updated dependencies.


HVAC client instrumentation

This adds HVAC instrumentation to Baseplate. The HVAC client is created in each server span using the secrets store to fetch a current Vault token. The client does share a connection pool, so TLS setup should be amortized. This comes with integration tests and docs too.

:haircut_man:

:haircut_man: i moved the url from config to the output of the fetcher. squashed it all together, sorry.

:haircut_man:

f48c8cf070d881942f9ce30e560d99b9dd9e1dce...89e1cd70d2e7fdcbb271c84ad053b78a24d83203


updated readme

Trivial change to README to check that circleCI has been set up properly

Hmm, this didn't work for some reason. Merging but will fix later.


Any chance 1080p support might return?

@moritzmhmk I see that the release notes for v0.0.2 show that 1080p support was removed due to cropping issues.
Is there any chance this might be fixed or is it just not possible at this stage?  Thank you for the quick reply and thank you very much for making this great plugin for HomeBridge.

If I wanted to enable it to take a look would I just have to remove the // from the configvshown above?


Operator proposal: idle

Some operations in our application have lower priority than others, I purpose to add an operator to postpone event propagation until browser is idle.
const $fitler = restore(fitlerChanged, null)

const $filteredItems = createStore([])

sample({
  clock: idle({ clock: filterChanged }),
  source: $items,
  fn: doSmth,
  target: $filteredItems
})

In this case, we can change $filter value immediate and respond to user input, but filtering of a large list will be delayed.

What about case when no clock is provided?
For example, plan event triggering until browser is idle.
const readyToCompute = idle();


Testing document for mobile

A document which describes what and how we are testing our mobile app.

I propose to not write this completely alone as the discussion on the PR can be unsatisfying. Instead, grab a sparring partner and discuss before hand.

I cannot find the matching document, but this was done.


Empty values sorted incorrectly

There's a regression bug, the issue was fixed in alphanumeric sort https://github.com/javve/list.js/pull/136 but is present in natural sort algorithm used now. As a result, empty strings are always on top, whatever the sort direction.
The correct way would be not to do any string replacement at all if one of (or both) passed values are null/empty

I've just created an issue where I reference all sort related problems. See #385. Thanks!


WIP: Clean unused permissions for prometheus

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
DO NOT REVIEW YET. WORK IN PROGRESS.
Cleans up role and role bindings for prometheus. Currently prometheus already has cluster scope permissions, so we don't need to worry about namespaced permissions.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Looks like tests are passing, also I haven't seen any errors in prometheus logs so I think it's good to merge.
FRT here are cluster level permissions for prometheus, which are giving more permissions than namespaced roles.
Here is list of cluster level permissions to compare:  https://github.com/kubernetes/perf-tests/blob/master/clusterloader2/pkg/prometheus/manifests/0prometheus-operator-clusterRole.yaml

/assign @mm4tt

/lgtm
/approve


Default to Chrome 41.0.2228.0 user-agent for getHttp()

As discussed in #19, this addresses the issue by using a different browser user-agent in getHttp() during the request for configuration from speedtest.net. The previous default user-agent has been blocked by the service so the request fails if consumers rely on the default option.
Long-term solution would possibly be to cache the client xml being used from http://www.speedtest.net/speedtest-config.php and clearing this cache when there's a change in IP.

Fixes #19


Description
Adding a preloader will enhance user interest .
Suggested Solution
The preloader will contain animation that will be rendered until the site is being loaded
Alternatives
The preloader will be completely respnonsive and matching the theme of project
Additional Context
Kindly assign this issue to me under GSSoC'24

please assign this issue to mee under gssoc24 I can fix this issue

@Jagpreet153  ok, go on. @riyasaxena32 issues are assigned on First Come First Serve basis. So if @Jagpreet153  fails to do the task, it will next assigned to you.

@Jagpreet153 ok, go on. @riyasaxena32 issues are assigned on First Come First Serve basis. So if @Jagpreet153 fails to do the task, it will next assigned to you.

Assign it to me


Podcast Component in homepage and separate Page

@Shehanka you have merged this, right? Why still open...


How to use values in home assistant automation?

Hi everyone,
I'm trying to create an automation that turns on a light when my active power is below a certain threshold.
In the GUI of HA:
TRIGGERS

CONDITIONS

ACTIONS

However, this seems not to work. I checked the values, i.e.:

PS.
In YAML, the automation became

- id: '1642434242283'
  alias: SchakelAlsVerbruikOnderGrens
  description: SchakelAlsVerbruikOnderGrens
  trigger:
  - platform: numeric_state
    entity_id: sensor.p1_meter_active_power_l1
    id: sensor.p1_meter_active_power_l1_250W
    attribute: unit_of_measurement
    below: '325'
  condition: []
  action:
  - type: toggle
    device_id: 829993eca56b2896acc3b9851fec86f7
    entity_id: light.my_n00_p03_light_l19_hanglamp
    domain: light
  mode: single

What am I doing wrong?
Any help is appreciated,
kind regards,
Bart Plessers

Don't automate on unit_of_measurement. Just leave it blank.
Unit of measurement is like 'Watts'. So you are literally asking When "Watts" goes below 250.
  id: '1642434242283'
  alias: SchakelAlsVerbruikOnderGrens
  description: SchakelAlsVerbruikOnderGrens
  trigger:
  - platform: numeric_state
    entity_id: sensor.p1_meter_active_power_l1
    id: sensor.p1_meter_active_power_l1_250W
-    attribute: unit_of_measurement
    below: '325'
  condition: []
  action:
  - type: toggle
    device_id: 829993eca56b2896acc3b9851fec86f7
    entity_id: light.my_n00_p03_light_l19_hanglamp
    domain: light
  mode: single

Also, trigger_id is not required. Only if you want to some advances automations.

@bartplessers Did it work?


Read from package.json engines.node

Folks who are deploying Rails apps to Heroku define their version of node in the package file under the engine.node key.
Docs at https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
This PR shows how the node, yarn, and npm version could be resolved from the package.json file to be compatible with Heroku Rails app configurations.
If this approach is palatable, it could be expanded to include yarn and npm.
Problems
The problem with the current approach is it doesn't resolve an exact version of node.js. In my case, I have the following package.json file:
{
  "name": "thingybase",
  "engines": {
    "node": "16.x"
  },
  "private": true,
  "dependencies": {},
  "devDependencies": {},
  "packageManager"<EMAIL_ADDRESS>}

The version 16.x gets set in All The Places™. Node then somehow resolves this to the latest version, which is 16.19.0 at the time of this writing. Ideally the Dockerfile would have NODE_VERSION=16.19.0 instead of NODE_VERSION=16.x. Whatever resolves that would have to be found and included in the generator to make this happen.
Additionally, it's possible to define a range of versions, https://docs.npmjs.com/cli/v9/configuring-npm/package-json#engines. I haven't tested how those would resolve, but it seems like it would be a really bad idea to set NODE_VERSION equal to a range of versions since the goal is to generate Dockerfiles where versions don't change.
Finally, the other issue is there's a lot of ways to specify versions for different engines, etc. In the package.json file above, you can see there's a packageManager key set with the yarn version. Also, if a node engine is defined in package.json and via .node-version is a warning displayed or do we go by some precedence?

After doing some more research, the engine.node key probably shouldn't be directly read to set the node version.
For now the best thing to do is use an exact node version.
I'm going to so more digging and see if I can find the exact mechanism that resolves the versions of engines.

probably shouldn't be directly read to set the node version

How about we don't impose the creation of a .node-version file if they are using engine.node to manage their version?  I pushed a change along these lines.  See if you like it.


(WIP) Metadata of C# (and other) Assemblies.

Better support for loading C# (and other) dlls (we need IsFSharp to be false to get all methods in "MembersFunctionsAndValues"). This will be used by FSharp.Formatting for example.
I used this with success in https://github.com/tpetricek/FSharp.Formatting/pull/208 but I'm not exactly sure what I have done :)
If somebody can comment on this why it's needed or why it's wrong that would be nice. It looks like the right thing to do would be to get the ccu from the entitiy, but this seems to be impossible in this case (because it is not unresolved).

I have now added a C# project and a test-case showing the issue (I ensured that the test fails without the patch).
One sidenote: The API to analyse dll files is quite cumbersome to use and is basically a hack which first compiles a very simple F# project with the contents module M? I think it would be better to provide a more direct API in the future (to be used by FSharp.Formatting an other projects).
The commented lines in the test-method are not working (even with my patch), but they should eventually (imho).
I hope this can bring more attention to this issue!
PS: please tell me if that format is OK (ie. directly adding the C# project to the solution)

I don't know enough about F# compiler internals, but the test certainly looks correct to me!
Also +1 to providing simpler API for analyzing DLLs (so that the boilerplate code to create an empty project does not have to be repeated in F# Formatting and elsewhere).

It seems wrong to include a solution test case into FSharp.Compiler.Service.Tests solution. Could you  move CSharp_Analysis solution to https://github.com/fsharp/FSharp.Compiler.Service/tree/master/tests/service/data instead?

The CSharp_Analysis.sln file was not really used anyway so I deleted it and moved the project to the destination you recommend.
Can the reference to the project and the project itself stay in the FSharp.Compiler.Service solution? Otherwise I'm not sure how to make the (new) test work by just opening the solution file and building FSharp.Compiler.Service.Tests...

@matthid I think it's fine as is. You need CSharp_Analysis project to be compiled anyway.
In general, this is a nice improvement. I wonder what @dsyme thinks about this.

It looks good, I've made one suggestion for a code simplification

Thanks for looking into this, I pushed the simplification.


ESP32 support

Please add ESP32 support.
It looks like it could be added similar to its predecessor, ESP8266. The command line tool is there on my mac:
./Library/Arduino15/packages/esp32/tools/mklittlefs
./Library/Arduino15/packages/esp32/tools/mklittlefs/3.0.0-gnu12-dc7f933/mklittlefs
I'd be willing to work on this myself, if you are able to provide instructions on how to build the VSIX file. I see that it is a deflate/zip file, but I am not sure how to build it.

The problem isn't making the filesystem, unfortunately (in fact, I think they use my mklittlefs tool or a close fork).  The issue is the ESP32 partitioning infrastructure.  I never really got into the ESP32 ecosystem and am unfamiliar with how they go about doing things like FS partitions/etc.
That said, a PR adding ESP32 support would be much appreciated!
My build-and-test.sh script simply calls
rm -f *.vsix
vsce package

to build the bundle.  To remove old versions, build and install the edited one, and test it out I use:
#!/bin/bash
rm -f *.vsix; vsce package && ( rm -rf ~/.arduinoIDE/plugins/* /tmp/vscode-unpacked/ ; cp *vsix ~/.arduinoIDE/plugins/. ) && ~/Downloads/arduino-ide_nightly-20230925_Linux_64bit.AppImage

For those following along, to build the project I needed to install a couple of npm packages:
npm install -g vsce
npm install -g typescript
npm install (post install script to fetch vscode libraries?)
npm install -g vscode-arduino-api
Lastly in tsconfig.json, add under compilerOptions "allowSyntheticDefaultImports": true
To add support for ESP32 I examined this Java project: arduino-esp32littlefs-plugin.
The partitions offered in the menu map to CSV files. Parsing the CSV files, you can find the spiffs entry.
I was able to translate it from Java to Typescript, and merge it into your project.
Patch coming.

Great, thanks.  I think I followed some online VSCode plug-in development blog to get those npm packages installed so your explicit listing is very handy.  You may want to edit the readme.md file, too, to add those bits in for posterity if you have a second.
One thing, though, my tsconfig has no allowSynthetic... in it so maybe that's not really required (or maybe for the CSV/JSON parsing?):
$ cat tsconfig.json
{
	"compilerOptions": {
		"module": "commonjs",
		"target": "ES2020",
		"outDir": "out",
		"lib": [
			"ES2020"
		],
		"sourceMap": true,
		"rootDir": "src",
		"strict": true   /* enable all strict type-checking options */
		/* Additional Checks */
		// "noImplicitReturns": true, /* Report error when not all code paths in function return a value. */
		// "noFallthroughCasesInSwitch": true, /* Report errors for fallthrough cases in switch statement. */
		// "noUnusedParameters": true,  /* Report errors on unused parameters. */
	}
}

Without the change in tsconfig.json, I get a stream of errors like:
node_modules/ardunno-cli/dist/api/google/rpc/status.d.ts:1:8 - error TS1192: Module '"/Users/dacarson/Documents/GitHub/arduino-littlefs-upload/node_modules/protobufjs/minimal"' has no default export.

1 import _m0 from 'protobufjs/minimal';

and it fails to compile:
Found 14 errors in 14 files.

Errors  Files
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/board.d.ts:1
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/commands.d.ts:2
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/common.d.ts:1
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/compile.d.ts:1
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/core.d.ts:1
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/debug.d.ts:1
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/lib.d.ts:1
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/monitor.d.ts:1
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/port.d.ts:1
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/commands/v1/upload.d.ts:1
     1  node_modules/ardunno-cli/dist/api/cc/arduino/cli/settings/v1/settings.d.ts:2
     1  node_modules/ardunno-cli/dist/api/google/protobuf/any.d.ts:1
     1  node_modules/ardunno-cli/dist/api/google/protobuf/wrappers.d.ts:1
     1  node_modules/ardunno-cli/dist/api/google/rpc/status.d.ts:1
 ERROR  npm failed with exit code 2

Googling the issue, it can be fixed with the change to the tsconfig.json file

FWIW, I did not add the changes to tsconfig.json to the PR.
Would be interest to know if it compiles fine for you.

It would be good to update the release to 1.1.0
Also update the project 'About' to include ESP32:-
"Build and uploads LittleFS filesystems for the Arduino-Pico RP2040 and ESP8266 cores under Arduino IDE 2.2.1 or higher."

Added the ESP32 to the about statement.
For some reason when I did the 1.1.0 release it wasn't set as the latest.  Corrected and now shows up on the landing page.


use script setup alongside export default will got compile error when exporting types

Version
3.2.21
Reproduction link
sfc.vuejs.org/
Steps to reproduce
Use as guide: https://github.com/vuejs/rfcs/blob/master/active-rfcs/0040-script-setup.md#usage-alongside-normal-script
This works (only export variable).
This breaks (export type and reference it in the script setup).
What is expected?
No compile error
What is actually happening?
Got compile error like this:
[plugin:vite:vue] Transform failed with 1 error:
/Users/upupming/projects/vue3-compact-template/src/components/Demo.vue:16:27: error: Expected ";" but found "++"
/Users/upupming/projects/vue3-compact-template/src/components/Demo.vue:16:27
Expected ";" but found "++"
14 |    expose()
15 |
16 |  const props = __props as ue++
   |                             ^
17 |  }
18 |
    at failureErrorWithLog (/Users/upupming/projects/vue3-compact-template/node_modules/.pnpm/esbuild@0.13.12/node_modules/esbuild/lib/main.js:1493:15)
    at /Users/upupming/projects/vue3-compact-template/node_modules/.pnpm/esbuild@0.13.12/node_modules/esbuild/lib/main.js:1282:29
    at /Users/upupming/projects/vue3-compact-template/node_modules/.pnpm/esbuild@0.13.12/node_modules/esbuild/lib/main.js:629:9
    at handleIncomingPacket (/Users/upupming/projects/vue3-compact-template/node_modules/.pnpm/esbuild@0.13.12/node_modules/esbuild/lib/main.js:726:9)
    at Socket.readFromStdout (/Users/upupming/projects/vue3-compact-template/node_modules/.pnpm/esbuild@0.13.12/node_modules/esbuild/lib/main.js:596:7)
    at Socket.emit (events.js:400:28)
    at addChunk (internal/streams/readable.js:290:12)
    at readableAddChunk (internal/streams/readable.js:265:9)
    at Socket.Readable.push (internal/streams/readable.js:204:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23

But volar static type checking is okay with no error:

Duplicate of https://github.com/vuejs/vue-next/issues/4423


Master head fixes 2

Various fixes aligned to Trello

@isbm
If this pull request is still relevant, please update it.
If it's not, please remove it.


[TF2.0] Sequential API serialization bug

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
docker image from tensorflow/tensorflow:2.0.0a0-gpu-jupyter
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
binary
TensorFlow version (use command below):
git version 'v1.12.0-9492-g2c319fb415'
tensorflow version '2.0.0-alpha0'
Python version:
2.7
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
cuda version 415.27
GPU model and memory:
GTX 1080Ti

Describe the current behavior
If I serialize a model built using the Sequential API and recreate the model from the config it fails.
Describe the expected behavior
The model to be initialized from the configuration
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
import tensorflow as tf
import numpy as np

data = np.random.random((1000, 32))
labels = np.random.random((1000, 10))
model = tf.keras.models.Sequential([
  tf.keras.layers.Dense(128, activation='relu'),
  tf.keras.layers.Dropout(0.2),
  tf.keras.layers.Dense(10, activation='softmax')
])

# The compile step specifies the training configuration
model.compile(optimizer=tf.keras.optimizers.RMSprop(0.001),
              loss='categorical_crossentropy',
              metrics=['accuracy'])

model.fit(data, labels, batch_size=32, epochs=5)
config = model.get_config()
new_model = tf.keras.Model.from_config(config)

Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
------------------------------------------------------------
KeyError                   Traceback (most recent call last)
<ipython-input-48-db6b212995c2> in <module>()
     12 model.fit(data, labels, batch_size=32, epochs=5)
     13 config = model.get_config()
---> 14 new_model = keras.Model.from_config(config)

/usr/local/lib/python2.7/dist-packages/tensorflow/python/keras/engine/network.pyc in from_config(cls, config, custom_objects)
   1229     # First, we create all layers and enqueue nodes to be processed
   1230     for layer_data in config['layers']:
-> 1231       process_layer(layer_data)
   1232     # Then we process nodes in order of layer depth.
   1233     # Nodes that cannot yet be processed (if the inbound node

/usr/local/lib/python2.7/dist-packages/tensorflow/python/keras/engine/network.pyc in process_layer(layer_data)
   1208           ValueError: In case of improperly formatted `layer_data` dict.
   1209       """
-> 1210       layer_name = layer_data['name']
   1211
   1212       # Instantiate layer.

An example can be seen here :- https://machinelearningmastery.com/save-load-keras-deep-learning-models/

I am interested in architecture only saving. As can be seen in the tensorflow documentation https://www.tensorflow.org/alpha/guide/keras/saving_and_serializing#architecture-only_saving
The documentation says that both Functional and Sequential APIs support this functionality. However only the Functional API works as the documentation says.
Here is the same example written in the Functional API and it works without a problem.
import tensorflow as tf
import numpy as np

data = np.random.random((1000, 32))
labels = np.random.random((1000, 10))

inputs = tf.keras.Input(shape=(32,))
x = tf.keras.layers.Dense(128, activation='relu')(inputs)
x = tf.keras.layers.Dropout(0.2)(x)
outputs = tf.keras.layers.Dense(10, activation='softmax')(x)

model = tf.keras.Model(inputs=inputs, outputs=outputs)
# The compile step specifies the training configuration
model.compile(optimizer=tf.keras.optimizers.RMSprop(0.001),
              loss='categorical_crossentropy',
              metrics=['accuracy'])

model.fit(data, labels, batch_size=32, epochs=5)
config = model.get_config()
new_model = tf.keras.Model.from_config(config)

@TahaK There are approaches (to_json, clone_model) other than get_config to save only model architecture. Please check the gist that uses to_json and clone_model approaches to save architecture of the model. Thanks!

Automatically closing this out since I understand it to be resolved, but please let me know if I'm mistaken.Thanks!

While this issue has already been closed, I guess the problem still persists?
With TensorFlow 2.0.0, get_config and model_from_config are still incompatible.
According to https://www.tensorflow.org/guide/keras/save_and_serialize, I would expect the config serialization / deserialization to be compatible with each-other (as I think they were in TensorFlow 1.13.1).
Has the config serialization / deserialization been deprecated (and meant to be superseded by JSON serialization / deserialization)?
Example, adapted from @TahaK, with the config serialization / deserialization added.
import tensorflow as tf
import numpy as np

print("TensorFlow " + tf.__version__)

data = np.random.random((1000, 32))
labels = np.random.random((1000, 10))
model = tf.keras.models.Sequential([
      tf.keras.layers.Flatten(input_shape=(32,)),
        tf.keras.layers.Dense(128, activation='relu',),
          tf.keras.layers.Dropout(0.2),
            tf.keras.layers.Dense(10, activation='softmax')
            ])

# The compile step specifies the training configuration
model.compile(optimizer=tf.keras.optimizers.RMSprop(0.001),
                      loss='categorical_crossentropy',
                                    metrics=['accuracy'])

model.fit(data, labels, batch_size=32, epochs=5)
# json approach
json_config = model.to_json()
new_model = tf.keras.models.model_from_json(json_config)
# model cloning
cloned_model=tf.keras.models.clone_model(model)
# config approach
dict_config = model.get_config()
new_model2 = tf.keras.models.model_from_config(dict_config)

model.summary()
new_model.summary()
cloned_model.summary()
new_model2.summary()

Output:
TensorFlow 2.0.0
Train on 1000 samples
Epoch 1/5
1000/1000 [==============================] - 1s 503us/sample - loss: 12.6396 - accuracy: 0.0990
Epoch 2/5
1000/1000 [==============================] - 0s 43us/sample - loss: 14.7099 - accuracy: 0.0940
Epoch 3/5
1000/1000 [==============================] - 0s 40us/sample - loss: 16.9181 - accuracy: 0.0840
Epoch 4/5
1000/1000 [==============================] - 0s 39us/sample - loss: 18.8631 - accuracy: 0.0900
Epoch 5/5
1000/1000 [==============================] - 0s 39us/sample - loss: 21.1111 - accuracy: 0.0980
Traceback (most recent call last):
  File "test2.py", line 28, in <module>
    new_model2 = tf.keras.models.model_from_config(dict_config)
  File "/home/?/.conda/envs/nn-test/lib/python3.7/site-packages/tensorflow_core/python/keras/saving/model_config.py", line 55, in model_from_config
    return deserialize(config, custom_objects=custom_objects)
  File "/home/?/.conda/envs/nn-test/lib/python3.7/site-packages/tensorflow_core/python/keras/layers/serialization.py", line 94, in deserialize
    layer_class_name = config['class_name']
KeyError: 'class_name'

@Sussch You can use tf.keras.Sequential.from_config(dict_config). I have used it for instantiating model object to load successfully as shown below.
# config approach
dict_config = model.get_config()
#new_model2 = tf.keras.models.model_from_config(dict_config)
new_model2 = tf.keras.Sequential.from_config(dict_config)
new_model2.summary()

Here is the gist for your reference. Thanks!

Ah, thank you.
Indeed, it says keras.Model.from_config, not keras.models.model_from_config in the guide at https://www.tensorflow.org/guide/keras/save_and_serialize.
Sorry, I must have missed it.
I now tried keras.Model.from_config and got a slightly different exception:
Traceback (most recent call last):
  File "test2.py", line 29, in <module>
    new_model2 = tf.keras.Model.from_config(dict_config)
  File "/home/indrek/.conda/envs/nn-test/lib/python3.7/site-packages/tensorflow_core/python/keras/engine/network.py", line 906, in from_config
    config, custom_objects)
  File "/home/indrek/.conda/envs/nn-test/lib/python3.7/site-packages/tensorflow_core/python/keras/engine/network.py", line 1842, in reconstruct_from_config
    process_layer(layer_data)
  File "/home/indrek/.conda/envs/nn-test/lib/python3.7/site-packages/tensorflow_core/python/keras/engine/network.py", line 1816, in process_layer
    layer_name = layer_data['name']
KeyError: 'name'

@jvishnuvardhan Your suggested tf.keras.Sequential.from_config(dict_config) works perfectly.
Could the guide (https://www.tensorflow.org/guide/keras/save_and_serialize) be updated accordingly?
Thank you!


Fixes #511: Allow deserialize_string for map fields originating from struct-formatted maps

This commit fixes an incoherence problem in the Deserializer implementation for fields in struct-encoded maps. deserialize_str was accepted, while deserialize_string was rejected. This behavior caused a problem when deserializing e.g. serde_json::Values from RON-files.

[x] I've included my change in CHANGELOG.md

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (1ff0efa) 100.00% compared to head (bc45a7d) 99.98%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##            master     #512      +/-   ##
===========================================
- Coverage   100.00%   99.98%   -0.02%
===========================================
  Files           79       80       +1
  Lines        11109    11159      +50
===========================================
+ Hits         11109    11157      +48
- Misses           0        2       +2

Files
Coverage Δ

src/de/id.rs
100.00% <100.00%> (ø)

tests/non_identifier_identifier.rs
100.00% <ø> (ø)

tests/511_deserialize_any_map_string_key.rs
96.07% <96.07%> (ø)

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

@grindvoll Thanks for the PR! It looks good to me once codecov is 100% and with the small CHANGELOG tweak.

@grindvoll Could you add a second test function to the new file, which just checks your motivating case, e.g.
#[test]
fn ron_struct_as_json_map() {
    let json: serde_json::Value = ron::from_str("(f1: 0, f2: 1)").unwrap();
    assert_eq!(
        json,
        serde_json::Value::Object(
            [
                (
                    String::from("f1"),
                    serde_json::Value::Number(serde_json::Number::from(0))
                ),
                (
                    String::from("f2"),
                    serde_json::Value::Number(serde_json::Number::from(1))
                ),
            ]
            .into_iter()
            .collect()
        )
    );
}


Init exception with latest xamarin.forms

Description
I updated the Xamarin.Forms NuGet Package to the latest version and now I get an exception on OnCreate in Android (iOS untested so far).
Actual Behavior

Unhandled Exception:
System.TypeLoadException: VTable setup of type FFImageLoading.Forms.Platform.CachedImageFastRenderer failed

Basic Information

Version with issue: <IP_ADDRESS>0 with XF v<IP_ADDRESS>8975
Last known good version: <IP_ADDRESS>0 with XF v<IP_ADDRESS>7583
Platform: Android, not sure about iOS

Reproduction Link / Code
In MainActivity, in OnCreate(), it happens on this line:
FFImageLoading.Forms.Platform.CachedImageRenderer.Init(enableFastRenderer: true);

Same issue here.

+1

same issue

Same here

Could you write more info of your dev environment? Xamarin.Android version, VS version, etc?

I was getting FATAL error using XF 3.4 on Xamarin.Forms App running on Android platform
Downgrading to XF 3.3 removed that error but the from resources folders are showing with lowest resolution (Android 8.0). My usage of FFImageloading is in the context of using it while building UI with Gorilla player  and Gorilla SDK.

Now back to XF v3.2 but not happy about that.

@daniel-luberda - with the new rhythm for Xamarin.Forms release since 3.2 .. It might be worthwhile to have regression plugged in to validate compatibility and report any issues into Xamarin.Forms team directly .. ? thoughts ?
In the mean time, please help in updating FFImageLoading compatible with XF 3.3, 3.4 that will also help in picking up the images with resolution corresponding to the underlying device resolution.
Thanks

Could you try <IP_ADDRESS>8-pre.nupkg?

did it pass your regression under XF 3.3 and 3.4; including image issue I mentioned above ?
just asking because it takes a lot of time to upgrade , compile , deploy and test .. and revert in case...
Sorry but thanks a lot.

I only updated packages & recompiled as I can't reproduce that issue on my projects (even sample project from FFImageLoading is working fine)

help in picking up the images with resolution corresponding to the underlying device resolution.

Could you explain it in details and create a separate issue for it?

@daniel-luberda .. the FATAL error is gone but images problem I mentioned as in XF 3.3 still exist.
On Android 8.0, while previewing my UI using Gorilla player - FFImageloading package is picking up images from the lowest resolution … that problem doesn't exist in FFImageloading stable version + XF 3.2. Please help.

Did you compile it against XF 3.4 or XF 3.3 ?

3.4

.. the FATAL error is gone but images problem I mentioned as in XF 3.3 still exist.
On Android 8.0, while previewing my UI using Gorilla player - FFImageloading package is picking up images from the lowest resolution … that problem doesn't exist in FFImageloading stable version + XF 3.2. Please help.

I don't use Gorilla Player but I don't think it's FFImageLoading related issue. You can review code responsible for retrieving assets here: https://github.com/luberda-molinet/FFImageLoading/tree/master/source/FFImageLoading.Droid/DataResolvers
and you'll see that it supports device size specific assets.

Well.. I am just wondering how come that's working with XF 3.2 and stable version of FFImageloading ?

@daniel-luberda <IP_ADDRESS>8-pre fixes the issue.

@daniel-luberda - just curious why the stable version numbers are lower than -pre.nupkg ?

@daniel-luberda
Still seeing this issue in the release that just went out
11-16 14:06:02.954 D/Mono    (18252): DllImport attempting to load: '/system/lib/liblog.so'.
11-16 14:06:02.954 D/Mono    (18252): DllImport loaded library '/system/lib/liblog.so'.
11-16 14:06:02.964 D/Mono    (18252): DllImport searching in: '/system/lib/liblog.so' ('/system/lib/liblog.so').
11-16 14:06:02.964 D/Mono    (18252): Searching for '__android_log_print'.
11-16 14:06:02.964 D/Mono    (18252): Probing '__android_log_print'.
11-16 14:06:02.964 D/Mono    (18252): Found as '__android_log_print'.
11-16 14:06:02.994 I/MonoDroid(18252): UNHANDLED EXCEPTION:
11-16 14:06:03.104 I/MonoDroid(18252): System.TypeLoadException: Could not load list of method overrides due to Method not found: void Xamarin.Forms.Platform.Android.IVisualElementRenderer.add_LayoutChange(System.EventHandler`1<Android.Views.View/LayoutChangeEventArgs>)
11-16 14:06:03.104 I/MonoDroid(18252):   at HamburgerMenu.Droid.MainActivity.OnCreate (Android.OS.Bundle savedInstanceState) [0x00037] in D:\Dev\Hamburger\New UX Components Test\Droid\MainActivity.cs:24
11-16 14:06:03.104 I/MonoDroid(18252):   at Android.App.Activity.n_OnCreate_Landroid_os_Bundle_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_savedInstanceState) [0x00011] in <ad2f15102b3a4d36b40e9b0cbc11c376>:0
11-16 14:06:03.104 I/MonoDroid(18252):   at (wrapper dynamic-method) System.Object.7(intptr,intptr,intptr)
11-16 14:06:03.134 W/art     (18252): JNI RegisterNativeMethods: attempt to register 0 native methods for android.runtime.JavaProxyThrowable
11-16 14:06:03.144 D/Mono    (18252): DllImport searching in: '__Internal' ('(null)').
11-16 14:06:03.144 D/Mono    (18252): Searching for 'java_interop_jnienv_throw'.
11-16 14:06:03.144 D/Mono    (18252): Probing 'java_interop_jnienv_throw'.
11-16 14:06:03.144 D/Mono    (18252): Found as 'java_interop_jnienv_throw'.
Unhandled Exception:

System.TypeLoadException: Could not load list of method overrides due to Method not found: void Xamarin.Forms.Platform.Android.IVisualElementRenderer.add_LayoutChange(System.EventHandler`1<Android.Views.View/LayoutChangeEventArgs>)

FFIMageLoading <IP_ADDRESS>9
Visual Studio: 17.9
Androidf Support: <IP_ADDRESS>

@mackayn Hi, I tested it on Mac VS 7.7 but I don't see anything related to FFImageLoading in the given stack trace. Are you sure it's FFImageLoading? Maybe it's other lib?
I didn't make any fix for XF 3.4 - I only rebuild it with XF packages updates. Maybe VS is caching those files somewhere?
@IoTFier Stable is released already

@daniel-luberda
It's definitely FFImageLoading that fails

I had the same TypeLoadException on Mac as well, until I upgraded the XF package from 3.4.0-pre1 to stable. As @daniel-luberda says it's probably the IDE holding onto something. In any case, 2.4.4 definitely works with XF 3.4.0 stable.

@daniel-luberda, a BIG THANK for removing FATAL Error.
All good with VS 17.9.1, XF 3.4 except my image resolution issue that I talked about ..
Appreciate your help in making us look good. Many paid vendors struggle to reach this bar and level of understanding to serve their customers.
A big Applaud for your professionalism.  Thank you !

@daniel-luberda
Yah, finally got there, delete all obj & bin, close VS, clear %temp%, re-open VS, clear nuget cache, open solution, restore & rebuild, all good.
Thanks for sorting this so quickly.

@daniel-luberda i have cleaned obj, bin, tmp, nuget cache all folders and restart VS2017 but Svg images are either not displayed or displayed badly.  it looks there is something terribly breaking with Svg images. i think the problem with this issue https://github.com/luberda-molinet/FFImageLoading/issues/1156

It seems to be working for me now after updating XF again, and also FFImageLoading!

I had the same issue when I updated XF to 3.4. I solved it when I also updated FFImageLoading and FFImageLoading.Forms to the newest stable version. In addition, I had to delete bin und obj folders. Now it works.

I had this issue using latest FFImageLoading and Xamarin.Forms 3.3. I've fixed it by updating X.F to 3.4.

I just had this issue using:
XF <IP_ADDRESS>8975
VS 15.9.3
Android Support 27.0.2
Minimum API level 6.0
Target level Android 9.0
FFImageLoading <IP_ADDRESS>9
Samsung Galaxy Tab 8.0 A running Android 7.1.1
It's random though.  This is the second time I've seen it but it doesn't happen all the time.

I have the same issue using
XF = <IP_ADDRESS>8975
VS 17 =15.9.3
Minimum API level 5.0
Target level Android 8.0
Onplus 3 running Android 7.1
FFImageLoading <IP_ADDRESS>9
So I update my
XF to <IP_ADDRESS>55-pre
FFImageLoading library to <IP_ADDRESS>0
Its working now.

I have the same issue too using
XF <IP_ADDRESS>8975
VS 17 15.9.3
Minimum API level 5.0
Target level Android 8.0
FFImageLoading <IP_ADDRESS>9
Oneplus 3 running android 7.1
I update to
XF <IP_ADDRESS>55-pre
FFImageLoading <IP_ADDRESS>0-pre
its working now

+1... same issues but with:
Xamarin Forms <IP_ADDRESS>1581
FFImageLoading <IP_ADDRESS>9
VS 15.8.7
Target level Android 8.0

I can confirm the issue the same as @dblookup. I have attempted to follow the steps outlined by @mackayn in the earlier comment:

delete all obj & bin, close VS, clear %temp%, re-open VS, clear nuget cache, open solution, restore & rebuild

This does not remedy the problem for the call to FFImageLoading.Forms.Platform.CachedImageRenderer.Init within the MainActivity.cs file of the Android project.
I have attempted the following FFImageLoading NuGet versions:

<IP_ADDRESS>9
<IP_ADDRESS>0-pre

Xamarin.Forms: <IP_ADDRESS>1581
Visual Studio 2017: 15.9.4
Android SDK Levels:
Target: 27
Min: 15
I have also attempted this within two different xamarin forms apps, both resulting in the same exception of:
System.TypeLoadException: Could not load list of method overrides due to Method not found: void Xamarin.Forms.Platform.Android.IVisualElementRenderer.add_LayoutChange(System.EventHandler1<Android.Views.View/LayoutChangeEventArgs>)
I am attempting to take a look and see if there is a missing event hookup (per the exception received) that was added with the Xamarin 3.2 (and up) image modifications that were implemented for the ImageButton feature. I just wonder this because there have been large changes added that caused other images issues as well, like the issue with Images unable to be set to null for Android found here.

Same error here, FF <IP_ADDRESS>9 and XF 3.3.0

Xamarin.Forms introduced a breaking change here. We added an interface event IVisualElementRenderer.LayoutChange which FFImageLoading implemented and when mono goes to load the FFImageLoading type that implemented the old interface it discovers it doesn't implement the new LayoutChange event and throws the exception you are seeing.
We plan to roll back this change with this PR.
We do not believe this will "re-break" FFImageLoading because we see that the implementation here of IVisualElementRenderer was not upgraded to include the LayoutChange event.

Looking at the current releases of FFIMageLoading.Forms it looks like the fix for the added interface is inside the 2.4.5-pre package but not 2.4.4
It's our plan to get this PR out https://github.com/xamarin/Xamarin.Forms/pull/5398 as soon as possible which will fix FFImageLoading when used with XF 3.6+
If the timing isn't right for 3.6 RC then we will definitely have the fix inside the next 3.6 SR1 release
I just wanted to get this note out before @daniel-luberda makes the 2.4.5 release official.

@kingces95 @PureWeen Thanks for info. I replied in XF issue.

Hi, with the current Xamarin.Forms 3.6.xx I get the init exception too. Downgrade to XF 3.5.xx

Hi, I can confirm I get the same init exception with Xamarin.Forms 3.6 and 2.4.5 pre.

Same error here for Xamarin.Forms 3.6 and 2.4.5 pre

Now that Forms has rolled back the interface a new 2.4.5 pre version of FFImageLoading will need to be released.
Once that's released then it'll fix the exception

Same same error here for Xamarin.Forms 3.6 and 2.4.5 pre

@mjspk

Now that Forms has rolled back the interface a new 2.4.5 pre version of FFImageLoading will need to be released.
Once that's released then it'll fix the exception

Same here XF <IP_ADDRESS>655 FFIL <IP_ADDRESS>7-pre

@dgonzalezp
Once a new build of FFIMageLoading 2.4.5 is created against XF 3.6 then it won't crash

Thanks! Meanwhile v<IP_ADDRESS>0 seems to be working.

@daniel-luberda FYI, 3.6.0 is stable now and contains the fixed API, so it's ready for a rebuild. Thanks!!!

use    CachedImageRenderer.Init(true);   at OnCreate(Bundle savedInstanceState)
Unhandled Exception:
System.TypeLoadException: Could not load list of method overrides due to Method not found: void Xamarin.Forms.Platform.Android.IVisualElementRenderer.add_LayoutChange(System.EventHandler`1<Android.Views.View/LayoutChangeEventArgs>)
xamarin.forms version:<IP_ADDRESS>665
oh my god... help me..
I can't live without FFImageLoading.
当使用xf版本：<IP_ADDRESS>665时，报错，请大家帮助我。谢谢各位。

I can only use it by rolling back to the previous version(xf:<IP_ADDRESS>047). But this is not a good idea.
我现在只能通过回滚到上一个版本(xf:<IP_ADDRESS>047)，才能使用。但这不是好办法。

@mazhiyuan1981 Either downgrade XF to latest 3.5.x or downgrade ff image to <IP_ADDRESS>0 for awhile, as this worked on my end. They might push a new version for ffimage to fix the issue.

@jbtamaresgit
i see ...thank you very much...

@jbtamaresgit  downgrade ff to <IP_ADDRESS>0 worked for me

I got this error too with XF: <IP_ADDRESS>655 and FF: <IP_ADDRESS>9.
Downgrading FF to <IP_ADDRESS>0 resolved the issue.

I think that downgrading is not a good solution. we had several fixes between those versions.

this is using XF <IP_ADDRESS>655   and FF <IP_ADDRESS>9

I too get the same error using the combinations @scharada and @haldocalypse mention.  I've resolved by downgrading XF for the moment.

the same issue

Please check <IP_ADDRESS>0-pre. Cheers.

Please check <IP_ADDRESS>0-pre. Cheers.
Works fine with XF: <IP_ADDRESS>655 !

I'm having the same issue here.
Downgrading to <IP_ADDRESS>0 solved, even being a weird solution.

There is in Android: System.TypeLoadException by using the <IP_ADDRESS>0-pre

@Polyariz that sounds like one of your binaries is off. Can you make sure all your nugets are the same version and try deleting your bin/obj folders

The same, bin and obj were deleted and the nuget's were removed and installed again

Anyone tried the latest version with FastRendererers enabled? I'm getting the exception still.

Updated today from XF 3.4 to 3.6 and got this error. For me FFIL <IP_ADDRESS>0-pre solved the problem. Using VS 15.9.7

I don't know if anybody has noticed because I haven't read comments about it, but I just wanted to point out that as someone suggested, yes, "v<IP_ADDRESS>0-pre" builds and deploys without errors, but most of my SVG images look bad now.
So I am gonna keep v<IP_ADDRESS>0 which displays my images correctly.

This is a great library but there does still appear to be a compat issue with Xamarin Forms 3.6. Any released or pre-release version of FFIL (e.g., <IP_ADDRESS>9, <IP_ADDRESS>0-pre, etc.) causes borkage on init. Maintaining plateau of Xamarin Forms 3.5 works however. So we are for the moment sticking with XF 3.5.

As @stesvis said it works on v<IP_ADDRESS>0 and the latest version of Xamarin Forms but it does not display my images correct.
Give a try on this one:
https://openclipart.org/download/159037/violin.svg

Seeing the same issue, deleting Bin/obj folders and rebuilding does nothing. Rolling back only resolves the issue.

Same issue on XF <IP_ADDRESS>4807

Works with the latest XF 4.0 pre-release and version <IP_ADDRESS>0-pre of FFImageLoading

Well, but we need it working on stable releases.

I got this error too with XF: <IP_ADDRESS>655 and FF: <IP_ADDRESS>9.
Downgrading FF to <IP_ADDRESS>0 resolved the issue.

Issue is resolved using FFImageLoading version <IP_ADDRESS>0-pre and XF 3.6

I can also confirm the above - <IP_ADDRESS>0-pre and XF 3.6 are working. I'll leave it here pending formal release of the next FFImageLoading version.

@daniel-luberda Any ETA on a stable release for <IP_ADDRESS>0-pre?

working in pre

Same as @EaranMaleasi  and @craigajohnson: FFImageLoading <IP_ADDRESS>0-pre works with Xamarin.Forms <IP_ADDRESS>4807.

Same problem for Xamarin.Forms 3.5.0-sr2  (<IP_ADDRESS>4416), this also needs FFImageLoading2.4.5-pre

It works after installing the <IP_ADDRESS>0-pre version,
Thanks for that

I confirm that the crash is gone with that pre-release version. Thanks.

Sorry, how can I download and install the pre-release version: <IP_ADDRESS>0-pre?

@fjsosa in VS package manager, there is a tick box next to the search that says 'Include prereleases'

System.TypeLoadException: Could not load list of method overrides due to Method not found: void Xamarin.Forms.Platform.Android.IVisualElementRenderer.add_LayoutChange(System.EventHandler`1<Android.Views.View/LayoutChangeEventArgs>)
still error there for XF.3.6  and also cannot find option in include pre-releases please help

@Monikaprime You should just follow @IeuanWalker suggestion, this is as easy as that:

With <IP_ADDRESS>0-pre + Forms <IP_ADDRESS>3080 I am running into another issue now on Android:

Constructor on type 'FFImageLoading.Forms.Platform.CachedImageFastRenderer' not found.

  at System.RuntimeType.CreateInstanceImpl (System.Reflection.BindingFlags bindingAttr, System.Reflection.Binder binder, System.Object[] args, System.Globalization.CultureInfo culture, System.Object[] activationAttributes, System.Threading.StackCrawlMark& stackMark) [0x0022b] in <58604b4522f748968296166e317b04b4>:0
  at System.Activator.CreateInstance (System.Type type, System.Reflection.BindingFlags bindingAttr, System.Reflection.Binder binder, System.Object[] args, System.Globalization.CultureInfo culture, System.Object[] activationAttributes) [0x000a1] in <58604b4522f748968296166e317b04b4>:0
  at System.Activator.CreateInstance (System.Type type, System.Object[] args) [0x00000] in <58604b4522f748968296166e317b04b4>:0
  at Xamarin.Forms.Internals.DependencyResolver.ResolveOrCreate (System.Type type, System.Object source, System.Type visualType, System.Object[] args) [0x00075] in D:\a\1\s\Xamarin.Forms.Core\DependencyResolver.cs:51
  at Xamarin.Forms.Internals.Registrar`1[TRegistrable].GetHandler (System.Type type, System.Object source, Xamarin.Forms.IVisual visual, System.Object[] args) [0x00052] in D:\a\1\s\Xamarin.Forms.Core\Registrar.cs:71
  at Xamarin.Forms.Internals.Registrar`1[TRegistrable].GetHandlerForObject[TOut] (System.Object obj, System.Object[] args) [0x0002c] in D:\a\1\s\Xamarin.Forms.Core\Registrar.cs:103
  at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\Platform.cs:339
  at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:120
  at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:268
  at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:92
  at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].SetPackager (Xamarin.Forms.Platform.Android.VisualElementPackager packager) [0x00007] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:414
  at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].SetElement (TElement element) [0x000e0] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:231
  at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00027] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:127
  at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x0001f] in D:\a\1\s\Xamarin.Forms.Platform.Android\Platform.cs:341
  at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:120
  at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:268
  at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:92
  at Xamarin.Forms.Material.Android.MaterialFrameRenderer.OnElementChanged (Xamarin.Forms.Platform.Android.ElementChangedEventArgs`1[TElement] e) [0x00072] in D:\a\1\s\Xamarin.Forms.Material.Android\MaterialFrameRenderer.cs:130
  at Xamarin.Forms.Material.Android.MaterialFrameRenderer.set_Element (Xamarin.Forms.Frame value) [0x00018] in D:\a\1\s\Xamarin.Forms.Material.Android\MaterialFrameRenderer.cs:67
  at Xamarin.Forms.Material.Android.MaterialFrameRenderer.Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00000] in D:\a\1\s\Xamarin.Forms.Material.Android\MaterialFrameRenderer.cs:259
  at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x0001f] in D:\a\1\s\Xamarin.Forms.Platform.Android\Platform.cs:341
  at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:120
  at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:268
  at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:92
  at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].SetPackager (Xamarin.Forms.Platform.Android.VisualElementPackager packager) [0x00007] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:414
  at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].SetElement (TElement element) [0x000e0] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:231
  at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00027] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:127
  at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x0001f] in D:\a\1\s\Xamarin.Forms.Platform.Android\Platform.cs:341
  at Xamarin.Forms.Platform.Android.ScrollViewContainer.set_ChildView (Xamarin.Forms.View value) [0x0002f] in D:\a\1\s\Xamarin.Forms.Platform.Android\Renderers\ScrollViewContainer.cs:36
  at Xamarin.Forms.Platform.Android.ScrollViewRenderer.LoadContent () [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\Renderers\ScrollViewRenderer.cs:356
  at Xamarin.Forms.Platform.Android.ScrollViewRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x000a6] in D:\a\1\s\Xamarin.Forms.Platform.Android\Renderers\ScrollViewRenderer.cs:93
  at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Content.Context context) [0x0001f] in D:\a\1\s\Xamarin.Forms.Platform.Android\Platform.cs:341
  at Xamarin.Forms.Platform.Android.VisualElementPackager.AddChild (Xamarin.Forms.VisualElement view, Xamarin.Forms.Platform.Android.IVisualElementRenderer oldRenderer, Xamarin.Forms.Platform.Android.RendererPool pool, System.Boolean sameChildren) [0x000af] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:120
  at Xamarin.Forms.Platform.Android.VisualElementPackager.SetElement (Xamarin.Forms.VisualElement oldElement, Xamarin.Forms.VisualElement newElement) [0x00139] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:268
  at Xamarin.Forms.Platform.Android.VisualElementPackager.Load () [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementPackager.cs:92
  at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].SetPackager (Xamarin.Forms.Platform.Android.VisualElementPackager packager) [0x00007] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:414
  at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].SetElement (TElement element) [0x000e0] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:231
  at Xamarin.Forms.Platform.Android.VisualElementRenderer`1[TElement].Xamarin.Forms.Platform.Android.IVisualElementRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x00027] in D:\a\1\s\Xamarin.Forms.Platform.Android\VisualElementRenderer.cs:127
  at Xamarin.Forms.Platform.Android.Platform.CreateRenderer (Xamarin.Forms.VisualElement element, Android.Support.V4.App.FragmentManager fragmentManager, Android.Content.Context context) [0x00031] in D:\a\1\s\Xamarin.Forms.Platform.Android\Platform.cs:388
  at Xamarin.Forms.Platform.Android.AppCompat.FragmentContainer.OnCreateView (Android.Views.LayoutInflater inflater, Android.Views.ViewGroup container, Android.OS.Bundle savedInstanceState) [0x00008] in D:\a\1\s\Xamarin.Forms.Platform.Android\AppCompat\FragmentContainer.cs:56
  at Android.Support.V4.App.Fragment.n_OnCreateView_Landroid_view_LayoutInflater_Landroid_view_ViewGroup_Landroid_os_Bundle_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_inflater, System.IntPtr native_container, System.IntPtr native_savedInstanceState) [0x00020] in <96541ba8a6104b52aadf4218488f978c>:0
  at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.30(intptr,intptr,intptr,intptr,intptr)

I'm having the same issue here...

Same here

Yup, same issue here:
Constructor on type 'FFImageLoading.Forms.Platform.CachedImageFastRenderer' not found.

For the people still getting the error, using Xamarin.Forms <IP_ADDRESS>4807 works, but version <IP_ADDRESS>3080 does not.

So here's the rundown of version compatibles. Let me know if something here seems incorrect and I can update
As of now we rolled back the interface change that caused this initial headache on every XF 3 version. This change needed to be applied to XF 3.4, 3.5, 3.6 meaning that
https://www.nuget.org/packages/Xamarin.FFImageLoading/<IP_ADDRESS>9
is incompatible with the latest versions of 3.4, 3.5, and 3.6, 4.0 pre(*)
https://www.nuget.org/packages/Xamarin.FFImageLoading/<IP_ADDRESS>9 and all 2.4.5 versions prior to
https://www.nuget.org/packages/Xamarin.FFImageLoading/<IP_ADDRESS>0-pre
are compatible with:

https://www.nuget.org/packages/Xamarin.Forms/<IP_ADDRESS>655
https://www.nuget.org/packages/Xamarin.Forms/<IP_ADDRESS>047
https://www.nuget.org/packages/Xamarin.Forms/<IP_ADDRESS>9999

https://www.nuget.org/packages/Xamarin.FFImageLoading/<IP_ADDRESS>0-pre
is compatible with the latest versions of 3.4, 3.5, and 3.6

It works after installing the <IP_ADDRESS>0-pre version,
Thanks for that

Same here.

FYI
https://www.nuget.org/packages/Xamarin.FFImageLoading/<IP_ADDRESS>0-pre
Is listed as coming out 2 days ago so updating to that might also fix your woes
I tested latest 3.6 against that version and everything worked for me

Its appear that "SvgCachedImage.LoadingPlaceholder" is not being replaced by svg file URL, someone can confirm if it's really a issue?

I found the cause: The Project was referering to version <IP_ADDRESS>0-pre insted of <IP_ADDRESS>0-pre

Works well with <IP_ADDRESS>0-pre and XF <IP_ADDRESS>4807. Thank you all.

Yes, <IP_ADDRESS>0-pre and XF <IP_ADDRESS>4807 is good for me.

@candidodmv @KishorTiwari @mackayn
Out of curiosity why are you opting to use  <IP_ADDRESS>0-pre opposed to  <IP_ADDRESS>0-pre?
<IP_ADDRESS>0-pre works with the latest version of XF <IP_ADDRESS>3080

@PureWeen as mentioned above https://github.com/luberda-molinet/FFImageLoading/issues/1154#issuecomment-480989539, with the version <IP_ADDRESS>0-pre is not loading svg files for me

I'm getting this when I try to upgrade to the pre release
NU1605: Detected package downgrade: Xamarin.FFImageLoading from <IP_ADDRESS>0-pre to <IP_ADDRESS>9. Reference the package directly from the project to select a different version.
SalesApp.iOS -> Xamarin.FFImageLoading.Forms <IP_ADDRESS>0-pre -> Xamarin.FFImageLoading (>= <IP_ADDRESS>0-pre)
SalesApp.iOS -> Xamarin.FFImageLoading (>= <IP_ADDRESS>9)
NU1605: Detected package downgrade: Xamarin.FFImageLoading from <IP_ADDRESS>0-pre to <IP_ADDRESS>9. Reference the package directly from the project to select a different version.
SalesApp.Droid -> Xamarin.FFImageLoading.Forms <IP_ADDRESS>0-pre -> Xamarin.FFImageLoading (>= <IP_ADDRESS>0-pre)
SalesApp.Droid -> Xamarin.FFImageLoading (>= <IP_ADDRESS>9)
Installing NuGet package Xamarin.FFImageLoading.Forms <IP_ADDRESS>0-pre.
NU1605: Detected package downgrade: Xamarin.FFImageLoading from <IP_ADDRESS>0-pre to <IP_ADDRESS>9. Reference the package directly from the project to select a different version.
SalesApp.iOS -> Xamarin.FFImageLoading.Forms <IP_ADDRESS>0-pre -> Xamarin.FFImageLoading (>= <IP_ADDRESS>0-pre)
SalesApp.iOS -> Xamarin.FFImageLoading (>= <IP_ADDRESS>9)

With <IP_ADDRESS>0-pre and XF <IP_ADDRESS>4807 combination, some images are showing in black and others good. I try with <IP_ADDRESS>0-pre and XF <IP_ADDRESS>3080 with no luck. Also, I delete bin/obj folders, clear nuget cache, rebuild and close VS 2019 for mac and continue with same issue.

In iOS (XF <IP_ADDRESS>3080, XF Visual Material <IP_ADDRESS>3080, Xamarin.FFImageLoading.Svg.Forms <IP_ADDRESS>9, VS2019) everything works fine.
I believe is Android's problem. I tried everything mentioned to the previous posts without luck!

After some research, the problem is related to Xamarin.Forms.Visual.Material!
When the CachedImage or SvgCachedImage are inside a, for example, StackLayout which has the property Visual="Material", then you take an exception.
I set, for CachedImage,  the property Visual="Default" and everything works fine!
(XF <IP_ADDRESS>3080, XF Visual Material <IP_ADDRESS>3080, Xamarin.FFImageLoading.Svg.Forms <IP_ADDRESS>0-pre, VS2019)
BR.

@kmagalios

When the CachedImage or SvgCachedImage are inside a, for example, StackLayout which has the property Visual="Material", then you take an exception.

is there any special setup for this? Or literally any CachedImage/SvgCachedImage you use when set to material will cause an exception?
Do you have the stack trace of the exception by chance?

@kmagalios We could use a fix for this, see: https://github.com/luberda-molinet/FFImageLoading/pull/1246
Reflection is needed as we need to be backward compatible. What do you think? Can you confirm if non-default style is an issue?

@daniel-luberda Thank you for your reply. Reflection sounds ok to me! I'll check it at afternoon.
@PureWeen
If CachedImage/SvgCachedImage is hosted into a container (Frame/StackLayout etc) which has the property Visual="Material", then the value of the property is propagated to contained components. For this case you have to set Visual="Default" to CachedImage/SvgCachedImage.
If the property Visual is not set or is set to "Default" you don't have any problem.
The default value for Visual property is "Default".

SvgCahcedImage doesn't display anything after I updated to the pre-release version. The source of the SvgCahedImage is a resource file in the shared project and I use it like below:
<forms:SvgCachedImage Source="resource://SharedProject.Images.share.svg">
This code worked before the update.

@IbrahimElshafey Could you attach a repo?

@daniel-luberda  while I create a sample to post it here I found it works fine, I will try to find the reason why it didn't work in the original project I worked on.

@daniel-luberda It seems that some images that were displayed correctly using the old version can't be displayed with the new one.
I created a sample that demonstrates that In this sample I display two images using the old version (2.3.6) and the other use the pre-release version (<IP_ADDRESS>0), the old sample display both images correctly but the new one display only one image and the other is white.

@kmagalios We could use a fix for this, see: #1246
Reflection is needed as we need to be backward compatible. What do you think? Can you confirm if non-default style is an issue?

@daniel-luberda I've installed the latest preview version (<IP_ADDRESS>0-pre) and everything works fine.
I remove the property Visual="Default" and everything is ok.
Thank you.

I pushed quite a lot of fixes and improvements lately. New prerelease package should be a lot more performant, especially on Android. I tested it while fast scrolling tons of images (also with poor internet connection scenario), not a single crash or exception and memory usage is lower than with previous versions. SVG parsing is also improved, etc.
I plan to release new stable. If you could test prerelease first and submit your feedback I would be grateful as I would like to fix all potential issues before a release.

@daniel-luberda I upgraded to the latest prerelease package but SVG images that were displayed by the old version (2.3.6) can't be displayed.

Also having this issue that IbrahimElshafey mentioned.  Using the latest stable Xamarin Forms release.

Which version of SkiaSharp do you use?
Are you sure you have the same FFIL packages version in all projects?

SkiaSharp wasn't referenced in my project, so I guess it was whichever version is bundled with Xamarin?
Adding SkiaSharp reference via Nuget fixed this issue.

@daniel-luberda First of all thank you, I very appreciate your work, FFIL is an essential package to any Xamarin.Forms project.
I use  the same SkiaSharp version in all projects, the smaple  contains two Xamarin forms projects, the code in both is the same but in the old (SvgCachedImageTest_old) I use FFIL version as the image
 the other one uses the latest pre-release version as the following

the result of both project is different, The old version display both SVG fine but the new pre-release isn't

@IbrahimElshafey Thanks.

You're not referencing all packages in your projects (Xamarin.FFImageLoading, Xamarin.FFImageLoading.Svg)
The important thing is you should use the same package version in all your projects. Both images render just fine on latest prerelease package. Also:
Always delete all bin / obj folders and then rebuild if you experience any problems.

@daniel-luberda Thanks for your response.
I added the missing packages and I deleted the bin/obj folders but with the new version the arrow image didn't display. bellow is the SVG for the image:
<svg xmlns="http://www.w3.org/2000/svg" width="8.5" height="14.9">
  <path fill="#f0f" d="M2.5 7.5a2 2 0 0 1 .3.2L8 13a1 1 0 1 1-1.5 1.5l-3.8-3.9L.4 8.2a1 1 0 0 1 0-1.6L6.6.4a1 1 0 0 1 1.8.4 1 1 0 0 1-.3 1L4.7 5.4 2.5 7.5z"/>
</svg>

If I deleted the bold attribute (fill="#f0f") it displayed fine, I tried this on two diffrent emulators and a my phone.
<svg xmlns="http://www.w3.org/2000/svg" width="8.5" height="14.9">
  <path d="M2.5 7.5a2 2 0 0 1 .3.2L8 13a1 1 0 1 1-1.5 1.5l-3.8-3.9L.4 8.2a1 1 0 0 1 0-1.6L6.6.4a1 1 0 0 1 1.8.4 1 1 0 0 1-.3 1L4.7 5.4 2.5 7.5z"/>
</svg>

@daniel-luberda I didn't want to waste your time If it works fine on your machine ignore the latest message because I use the old version in the real project and it works fine.

See screenshot above, it works. I just tested it on FFIL sample project:

@daniel-luberda It may be some packages cached on my machine I will try again.

@IbrahimElshafey
Clear your Visual Studio nuget cache.

@mackayn I tried this already, I deleted all FFIL packages in the packages folder C:\Users\UserName\.nuget\packages\  but the problem still exists, I will compile source code locally.

Using <IP_ADDRESS>9-pre and Xamarin forms <IP_ADDRESS>4457 resolves this issue for me.

Hi
Using <IP_ADDRESS>9-pre (Core, iOS and Android) and Xamarin forms <IP_ADDRESS>4457 but the images are not visible.

I confirm

Same issue here, SVGs are not rendered

Please make sure you:

have included all necessary packages in all projects, https://github.com/luberda-molinet/FFImageLoading/wiki/Xamarin.Forms-API#step-1  (including SkiaSharp)
all packages all in the same version
delete all bin/obj folders from all projects & rebuild

Please make sure you:

have included all necessary packages in all projects, https://github.com/luberda-molinet/FFImageLoading/wiki/Xamarin.Forms-API#step-1  (including SkiaSharp)
all packages all in the same version
delete all bin/obj folders from all projects & rebuild

This worked, however, only the first time i run the app after a clean+delete obj/bin+rebuild.
After that, if i run the app again there is no error, but all my svg icons are invisible.
I would have to clean+delete obj/bin+rebuild the app every time to make it work....
Is there a reason?

I have install SkiaSharp and it's working. Thanks @daniel-luberda

I updated the Xamarin.Forms NuGet Package to the latest version and now I get an exception on OnCreate in Android (iOS untested so far).
Is there a solution to this problem?

commit your code or take a copy of your project.
After the apply this command on package manager console "update-package".
After this clean build your project, then restart visual studio and rebuild your project.
This procedure work for me.

Using version <IP_ADDRESS>9 works well with XForms <IP_ADDRESS>9.
The following versions did not work for me (combined with the same XForms version above):

<IP_ADDRESS>2
<IP_ADDRESS>1

Hello,
it also crashed for me, I use FFImageLoading version <IP_ADDRESS>8 pre and Xamarin.forms <IP_ADDRESS>0.
It throws this exception:

System.TypeLoadException: Could not load list of method overrides due to Method not found: void Xamarin.Forms.Platform.Android.IVisualElementRenderer.add_LayoutChange(System.EventHandler`1<Android.Views.View/LayoutChangeEventArgs>)

I did everything requested here: https://github.com/luberda-molinet/FFImageLoading/wiki/Xamarin.Forms-API#step-1
I did not do:

Xamarin.FFImageLoading.Transformations (if you’ll use transformations like CircleTransformation)

Xamarin.FFImageLoading.Svg (for SVG support)

Xamarin.FFImageLoading.Svg.Forms (for SVG support)

SkiaSharp (for SVG support)

As it is optional - I don't use SVG, and I don't use transformations

@daniel-luberda, a BIG THANK for removing FATAL Error.
All good with VS 17.9.1, XF 3.4 except my image resolution issue that I talked about ..
Appreciate your help in making us look good. Many paid vendors struggle to reach this bar and level of understanding to serve their customers.
A big Applaud for your professionalism. Thank you !

@IoTFier screenshots helped me a lot.. thanks....


Description of managedFields.fieldsV1 in ObjectMeta is garbled

Found in an auto-generated page: https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/object-meta/#System
The field managedField.fieldV1 has the following description:

FieldsV1 holds the first JSON version format as described in the "FieldsV1" type.
*FieldsV1 stores a set of fields in a data structure like a Trie, in JSON format.
Each key is either a '.' representing the field itself, and will always map to an empty set, or a string representing a sub-field or item. The string will follow one of these four formats: 'f:', where is the name of a field in a struct, or key in a map 'v:', where is the exact json formatted value of a list item 'i:', where is position of a item in a list 'k:', where is a map of a list item's key fields to their unique values If a key maps to an empty Fields value, the field that key represents is part of the set.
The exact format is defined in sigs.k8s.io/structured-merge-diff*

The third paragraph especially doesn't really make sense, it seems to be missing a lot of words.
The description seems like it may be sourced from this file, which makes a bit more sense.
As an additional note, I've been able to find the "exact format" referred to in the last paragraph, could that be replaced with a more specific reference?

/language en
/sig docs
/sig api-machinery

This is an autogenerated page the fix need to be done in the code. Cannot be fixed in the documentation.

I will raise a PR for this
/assign

/remove-lifecycle stale


how to run doctests?

How are doctests in the docs run here? Are they run on CI? I think they should be.

I was looking through some of the examples and noticed this too.
According to the documentation: doctests seem like they should be set up through CircleCI:
https://github.com/scikit-learn-contrib/project-template/blob/e588f28c91b3664bc4fc3cc6ae8b38407e319624/doc/quick_start.rst#L109-L111
However, the pipeline in .circleci/config.yml currently performs:
https://github.com/scikit-learn-contrib/project-template/blob/e588f28c91b3664bc4fc3cc6ae8b38407e319624/.circleci/config.yml#L20-L21

Normally I would expect doctests to run with make doctest, producing something like the following:
$ make doctest

# -snip-
Doctest summary
===============
   38 tests
    0 failures in tests
    0 failures in setup code
    0 failures in cleanup code
build succeeded.

If any doctests fail, make doctest should return 2:
$ make doctest
# -snip-
Doctest summary
===============
   38 tests
    1 failure in tests
    0 failures in setup code
    0 failures in cleanup code
build finished with problems.

$ echo $?
2

Seems like this should be a fairly easy fix. I'll experiment a bit and submit a pull request in an hour or so.


Add support for users/groups in the underlying Image metadata

This adds support for the User/Group metadata of the Image Configuration. This is a prereq for supporting hardened containers, as we will need to know the image's users/group metadata in order to set these fields on the TAR files and directory structures to ensure correct permissions at run-time.
I have not surfaced this on the CreateNewImage task, there is a lot of additional work around that we need to dig into, but we will need this property for read-level access at minimum to tackle #148.
I surfaced this as two different properties (User/Group) because while they are one string, the value has two distinct parts, and users may want to customize each individually.

Closes https://github.com/dotnet/sdk-container-builds/issues/115

Going to close this as there has been quite a bit of drift and we may not need it for quite a while.


onClickOutside not working when select date

Help me, fix issues when using React 15.5 and React-datepicker v.0.40.0.

Actually I see the same thing. Clicking outside the calendar after I select a date but not the time doesn't close the calendar.


Fix unescaped @ in snippet

Codecov Report

Merging #1111 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1111   +/-   ##
=========================================
  Coverage     85.62%   85.62%
  Complexity     3617     3617
=========================================
  Files           368      368
  Lines         14179    14179
  Branches       1634     1634
=========================================
  Hits          12141    12141
  Misses         1601     1601
  Partials        437      437

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6d45bb0...19c0058. Read the comment docs.


Add a composite shipping method to allow more advanced price and availability calculations

Basically, outsource the price and advanced availability options to another shipping method. Like the Weight, Country, or Google Routes shipping methods.
The price overrides the regular base price on the shipping method, so the per-slot price can still add a "surcharge" to specific high-value slots.

This is really cool. 👍🏻
However there seems to be a problem when testing with GoogleRoutes shipping methods. When used via a Timeslots shipping method, parent::isAvailableForShipment() always returns false even though all the checks pass which is quite odd...
Still working on debugging.

Hmm, maybe the origin coords are getting saved on the copy because that happens dynamically? No origin coords = no results = not available?

Because the composite shipping method is only stored in memory, that means an id isn't assigned, so any shipping methods relying on that will have trouble.
Perhaps we can override the get() method to account for that 🤔
Also, other composite methods needed would be save(), getProperty(), setProperty().
Something along the lines of:
public function save($cacheFlag = null): bool
    {
        if ($comp = $this->getCompositeMethod()) {
            $save = $comp->save();
        }
        else {
            $save = parent::save();
        }

        return $save;
    }

    public function setProperty($key, $value = null)
    {
        parent::setProperty($key, $value);
        if ($comp = $this->getCompositeMethod()) {
            $comp->setProperty($key, $value);
        }
    }

    public function getProperty($key, $default = null)
    {
        if ($property = parent::getProperty($key, $default)) {
            return $property;
        }
        if ($comp = $this->getCompositeMethod()) {
            return $comp->getProperty($key, $default);
        }
        return null;
    }

Though not sure if that'd cause other problems haha

Hmm, maybe the origin coords are getting saved on the copy because that happens dynamically? No origin coords = no results = not available?

Yes exactly!

Looks like you're all over it but two ideas for that:

in TimeSlots, make sure the id is copied to the composite object and that we manually merge properties after calling getModelFields or getPriceForShipment
in Google routes add hidden fields for the coords - because they then appear in the form, that might help?

We may need a way of checking if a shipping method is "composable". For example if a shipping method overrides save() while acting as a composite method, it'll create another in the database.


Advisory Standards

One of the fields in the data is an advisory, which is a boolean based on the local water quality standard.
It's not exactly clear to me how this will be determined — would it be done by the user uploading the data? Will there also be an open data specification for the local water quality standards by the cities / municipalities?

Confirming that the "description" field can be used to describe the nature of the advisory, include the local rwq criteria, and includes ability for the record issuer to include a link to their own website, or docs outlining standards/protocols/policies/fed recommendations under which the advisory was issued.


how to add the sum of yAxis values under a line?

Is it a way to extend the plugin that exports to XLS and CSV to add additional line with the sum value?

Currently the plugin doesn't support that, but you can do that by extending the module. Here's a boilerplate where you can add some logic to summarize the values: http://jsfiddle.net/cqjvD/1206/

Thank you for your help. I solve my issue thanks to your solution.


Could not find theme file error

Could not find theme file error is received from Alfred when trying to use alfred-atom, probably because it is looking for a theme file that does not exist.
I also tried to add an empty json file at the specific location and that removed the error but alfred-atom output was still empty.
Hugo version: 1.2.0 used by alfred-atom 2.3.2
Alfred version: 3.6.1
NodeJS version: v9.5.0
Exception / Stacktrace:
[2018-04-09 15:43:23][STDERR: input.scriptfilter] Could not find theme file "/Users/martin/Library/Application Support/Alfred 3/Alfred.alfredpreferences/themes/theme.bundled.default/theme.json"
Could not find theme file "/Users/martin/Library/Application Support/Alfred 3/Alfred.alfredpreferences/themes/theme.bundled.default/theme.json"

Ah, thanks for reporting this. I moved the issue to the alfred-atom repository as it's not a bug in Hugin.
https://github.com/Cloudstek/alfred-atom/issues/19


fix(ui): enable cypress for entity tags and fix saving issue when ui get scrolled

Describe your changes:

Enable cypress for entity tags
Enable cypress for glossary tags too
Fix the tags saving issue when ui get scrolled

https://github.com/open-metadata/OpenMetadata/assets/66266464/7004a7ba-5f37-4d9e-bdc5-f70136df7601

Type of change:

[x] Bug fix
[x] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Cypress is failing can you please check? @Ashish8689


fix(middleware): adjust invalid key response

Return a proper response when the key is invalid.
Instead of 500 we now respond with a 401.

LGTM
IMO we could use more logging as it doesn't hurt

LGTM
IMO we could use more logging as it doesn't hurt

Would love that too, let's do that in a follow-up :)


Add documentation on how to configure Amazon Route53 for a new Deis cluster

Similar to #146, we should have detailed instructions for how to configure Route53 after a Deis cluster is up and a load balancer is running in front of the routers. The docs should preferably handle load balancers that provide domains (so you'd have to create a CNAME record) and ones that provide IPs (so you'd have to create an A record.

Might be worth bringing route53-wildcard.py forward from Deis v1, and/or writing an equivalent script to make dealing with Google's DNS easier.

Punting to RC1

yes, especially since the AWS documentation only specifies nip.io at this point. Users are not going to go into prod with that setup.


New package: Hayaku.QuickDash v0.5.1

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\quickdash.exe returned exit code: 1

(Automated response - build 895.)

@wingetbot waivers Add Validation-Executable-Error


Test CephFS usage

With Block Storage which allows a single pod to mount storage, when crashes, all the pods located on the crashed node will go into terminating state and application will be unavailable since terminating pods blocking access to ReadWriteOnce volume and new pod can't create. We need to check CephFS possibilities.
Desired output from this task would be guide when to use which type of storage.
Look here

As the description says, Block Storage allows a single pod to mount storage in RWO mode and when there will be a crash for example node will break or will be unavailable (shutdown) the pod will go into terminating state and application will be unavailable :
Error:
Unable to attach or mount volumes: unmounted volumes=[wordpress-persistent-storage], unattached volumes=[wordpress-persistent-storage default-token-4nj25]: timed out waiting for the condition
Moreover, it is not possible to run deployment and have clustered application with PVC and Block Storage, due to the same error as above.
In this case, CephFS is much more better option and after crash, Pod will recreate after 5 minutes (default eviction time can be changed) and application will have only short downtime. Moreover, in compare to Block Storage, deployments and replicas work as expected since shared filesystem can be mounted with read/write permission from multiple pods .
Summing up, for Epiphany usage, I could highly recommend to use Block Storage in StatefulSets since StatefulSets allow to use volumeClaimTemplates and problem with PVC in RWO mode doesn't affect our clustered application, it could be nice solution for database. Block volumes are critical to applications like databases (MongoDB, Cassandra, PostgreSQL) that require consistent I/O performance and low latency. As far as CephFS is consider, I would highly recommend to use this kind of storage for clustered application using deployment with multiple pods.

Nothing to do here more, tomorrow demo will be presented


Update (conference): MEC2021 postponed

This PR updates the MEC2021 pages to announce the conference being postponed to July 2021.
Previous dates are striked out to keep the changes visible; they can be removed by the end of January.
Ready to merge.

Thank you @rettinghaus !


Rename Isos to Core and move it into its own module

Depends on #52

Sorry for force-pushing changes. I missed a dependency.
On that note: compiling Everything fails with the error
Categories/Category/Construction/Graphs.agda:29,8-86
Failed to find source of module
Relation.Binary.Construct.Closure.ReflexiveTransitive.Equivalence