Support 64-bit processors

The sdk cannot scan card on a Nexus 9. Could you please add support for 64bit processors and other architectures.

The logs are below
03-24 11:27:29.117  17642-17642/I/card.io﹕ Checking hardware support...
03-24 11:27:29.117  17642-17642/I/card.io﹕ card.io 5.0.0 03/10/2015 11:22:54 -0500
03-24 11:27:29.119  17642-17642/D/card.io﹕ Loaded card.io decider library.  nUseNeon():false,nUseTegra():false
03-24 11:27:29.120  17642-17642/W/card.io﹕ unsupported processor - card.io scanning requires ARMv7 architecture
03-24 11:27:29.120  17642-17642/W/card.io﹕ - Processor type is not supported
03-24 11:27:29.120  17642-17642/W/card.io﹕ ERROR_NO_DEVICE_SUPPORT: This device cannot use the camera to read card numbers.

Hi,
Thanks for the update on this. But I'm not able to get it working with 5.0.1. There is a different error now.
06-04 17:12:18.121  10100-10100/? I/card.io﹕ Checking hardware support...
06-04 17:12:18.127  10100-10100/? I/card.io﹕ card.io 5.0.1 06/04/2015 17:39:33 -0500
06-04 17:12:18.129  10100-10100/? E/card.io﹕ Failed to load native library: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.x.x-1/base.apk"],nativeLibraryDirectories=[/data/app/com.x.x-1/lib/arm64, /vendor/lib64, /system/lib64]]] couldn't find "libcardioDecider.so"
06-04 17:12:18.130  10100-10100/? W/card.io﹕ - Processor type is not supported
06-04 17:12:18.130  10100-10100/? W/card.io﹕ ERROR_NO_DEVICE_SUPPORT: This device cannot use the camera to read card numbers.
06-04 17:12:18.130  10100-10100/? I/card.io﹕ Camera not available and manual entry suppressed.

I tried building card.io with card.io for arm64-v8a and I get the above error again.
Am I missing something.?
Thanks!

Hey @braebot, I have the same error as @varunkochar (couldn't find "libcardioDecider.so") on an S6 when I include an other third party lib which use arm64-v8a folder.
When I remove the other lib, it's fine so It seems that the fallback to the folder v7a occurs only if you don't have the arm64-v8a folder at all.

@braebot I have the same error on Samsung Galaxy Tab 3
We already use the latest  version
is there any solution ?

Same case here. On S6, with another 64bit library in arm64-v8a folder, card.io will not work with error ERROR_NO_DEVICE_SUPPORT: This device cannot use the camera to read card numbers

@braebot Can you please give us any feedback from your side?

Hey, I'd just like to mention that I'm hitting this same error on a nexus 9. The logs are below in case they help.
I'm happy to run any tests or provide any further details needed in adding support for the Nexus 9.
09-11 19:29:02.801  16349-16349/com.emberall.kiosk.local I/card.io﹕ Checking hardware support...
09-11 19:29:02.806  16349-16349/com.emberall.kiosk.local I/card.io﹕ card.io 5.0.1 06/04/2015 17:39:33 -0500
09-11 19:29:02.807  16349-16349/com.emberall.kiosk.local E/card.io﹕ Failed to load native library: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.emberall.kiosk.local-1/base.apk"],nativeLibraryDirectories=[/data/app/com.emberall.kiosk.local-1/lib/arm64, /vendor/lib64, /system/lib64]]] couldn't find "libcardioDecider.so"
09-11 19:29:02.808  16349-16349/com.emberall.kiosk.local W/card.io﹕ - Processor type is not supported
09-11 19:29:02.808  16349-16349/com.emberall.kiosk.local W/card.io﹕ ERROR_NO_DEVICE_SUPPORT: This device cannot use the camera to read card numbers.

Not working on galaxy s4 and nexus 4/5. getting the folowing output:
I/card.io: card.io 5.0.1 06/04/2015 17:39:33 -0500
D/card.io: Loaded card.io decider library.  nUseNeon():true,nUseTegra():false
D/card.io: Loaded opencv core library
D/card.io: Loaded opencv imgproc library
E/card.io: Failed to load native library: JNI_ERR returned from JNI_OnLoad in "/data/app/_/lib/arm/libcardioRecognizer.so"
W/card.io: - Processor type is not supported

please give a help

@braebot if you're wondering why the fallback worked for you in testing on an S6 and it's not working for some of us in the wild, it may be related to this answer on Stack Overflow. Basically if a project already has some 64-bit dependencies Android won't load 32-bit native libs.

Hey everybody, for those still struggling with this issue, after further investigation I've found a (very sub-optimal) workaround that I've tested and found to work on my Nexus 9. I wrote it up in a blog here. I'm still hoping for a 64-bit version of card.io, but at least this works in the meantime.

@corbt Thanks for your post. It works


Auto save files when rights change

Otherwise editing rights via the file settings dialog does not work.

Coverage remained the same at 99.053% when pulling e55a54d3fdd7d654a3571fd5cb8bf9c396a0c89d on tf:autosave-file-rights into 11b95b171ddbe6b59af36d9b841cddfc8da607a7 on codevise:master.


Be able to edit an existing connection

Issue Type: Feature Request
I am not able to edit existing connections. It realy makes ligfe easier if there is a way to edit an existing connection.
VS Code version: sqlops 0.28.6 (3abbc8fd9713cdf847dcde703402d10a09eaa4ec, 2018-04-24T21:19:12.047Z)
OS version: Windows_NT x64 10.0.17134

@yooakim there should be a UI-based experience for this.  The current workaround is to edit the connection settings in the User Settings file.

I second this!

Fixed by PR #10214


ElasticSearch v. 8 upgrade

Things to consider:

[ ]  HTTPS + Basic Auth are now enabled by default -- need to mention setup process in README and update CI workflows
[x] Index mass delete is disabled by default
[ ] Custom mappings are disabled (https://www.elastic.co/guide/en/elasticsearch/reference/7.17/removal-of-types.html) - is it already handled? in https://github.com/toptal/chewy/pull/783
[ ] ES 7 compatibility mode -- do we need to support it?

@konalegi it looks like you need to use elasticsearch-transport up to 7.17 to have compatibility mode:
here we have ELASTIC_CLIENT_APIVERSIONING flag:
https://github.com/elastic/elasticsearch-ruby/blob/7.17/elasticsearch-transport/lib/elasticsearch/transport/client.rb#L151
here we don't:
https://github.com/elastic/elastic-transport-ruby/blob/main/lib/elastic/transport/client.rb --
And official migration guide also recommends to start with 7.17 in compatibility mode, fix critical issues and then update libs to 8:
https://www.elastic.co/guide/en/elasticsearch/reference/current/rest-api-compatibility.html

@konalegi it looks like we need to use elasticsearch-transport up to 7.17 to have compatibility mode:
here we have ELASTIC_CLIENT_APIVERSIONING flag: https://github.com/elastic/elasticsearch-ruby/blob/7.17/elasticsearch-transport/lib/elasticsearch/transport/client.rb#L151
here we don't: https://github.com/elastic/elastic-transport-ruby/blob/main/lib/elastic/transport/client.rb --
And official migration guide also recommends to start with 7.17 in compatibility mode, fix critical issues and then update libs to 8: https://www.elastic.co/guide/en/elasticsearch/reference/current/rest-api-compatibility.html
Can one of you confirm if post this PR, this code would support both ES 7.17 and ES 8 ? Asking since I was looking into making changes for supporting ES 8 in our forked version. And it would make the migration seamless, if we can have the compatible mode

@amol21p this code is not supposed to support ES 7.17 as per official upgrade guide.
Only 7.* of elasticsearch-ruby  supports compatibility mode in Elastic server. Starting from 8 they've dropped compatibility support.
So theoretically upgrade goes like this:

Upgrade Elasticsearch server to last 7.17 version
Set ELASTIC_CLIENT_APIVERSIONING=1 env flag and use Chewy 7
Resolve issues (guide is a bit unclear on this, I guess there are deprecation warning in Elastic logs or something like this)
Upgrade Elasticsearch server to 8.15.0
Resolve all deprecation logs warnings "compatible_api"
Upgrade to Chewy 8

I guess for smooth upgrade we need to make sure Chewy 7 plays nice with ES 8 with the flag ELASTIC_CLIENT_APIVERSIONING set

However we had already some changes in our forked version. What would you suggest in that case ?
It would be good to move to a chewy version once with backward compatibility. Otherwise, effort would increase in the migration as we would have to resolve issues twice on ES8 once on the older chewy version and once on the newer version


open-event-webapp not deploying

Actual Behaviour
The latest version of open-event-webapp not working on the local machine as well as on Heroku.
But the strange thing is all CI build are passing.

Expected Behaviour
when someone tries to run the project, he/she will be able to run on the local machine as well as deploy it directly on Heroku.

Steps to reproduce it

Deploy the webapp directly to Heroku.
Run the project on local machine.

Screenshots of the issue

npm run start

npm logs

Would you like to work on the issue?
Yes, i would like to work on the issue. I would be great if someone helps me get this issue fix.

is this fixed now?  @aaqaishtyaq


Image upload not working correctly

Hi, I just updated cellpose to the newest version and I cannot drop in the images from folders as I was able before - the cursor changes to the black crossed circle.
In additon when I load the images via Ctrl+L, the phase image displayed is distorted (the bridgtness/contrast for each pixel line seems to be adjusted individually, please see attached image).
Any ideas what is wrong and how to fix this?
Thanks!

UPDATE: the drag and drop was fixed with reinstalling Anaconda navigator.
The image display issue was not solved by that, or by creating new environment and installing Cellpose from the beginning.
How do install an older version of Cellpose?

sorry for the trouble I think this is fixed, please try the latest github version, pip install git+https://github.com/mouseland/cellpose.git. if not I'll reopen the issue

Just tried it out: The stripes are gone, and nucleus segmentation seems to work again as expected.
Thank you so much!!!


state and refresh_token return undefined when logging in with emailcode

I'm using version 2.2.3 of passwordless lock. I have the following code within a function:
var lock = new Auth0LockPasswordless("x", "auth0domain");
lock.emailcode({autoclose: true}, function (error, profile, id_token, access_token, state, refresh_token) {
    if (!error) {
        localStorage.setItem(token, id_token);
        console.log(refresh_token);
    }
});

When this code is invoked, state and refresh_token return undefined.
Am I doing something wrong?

All sorted now
http://stackoverflow.com/questions/42975847/can-i-get-a-refresh-token-using-auth0-passwordless-lock-in-javascript?noredirect=1#comment73052934_42975847

Thanks for sharing the answer with us! 🎉


display and load data

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3883

PR #3884

PR #3885

PR #3886

PR #3887   👈

This comment was auto-generated by Graphite.

@wraeth-eth started a stack merge that includes this pull request via Graphite.

Graphite rebased this pull request as part of a merge.


Deploy VM using Terraform

The terraform deployment fails with
Error: failed to create contract: failed to create contract: extrinsic timeout waiting for block

  on main.tf line 21, in resource "grid_network" "net1":
  21: resource "grid_network" "net1" {

That's testnet? if so, it's currently being investigated here.


llmware/llmware/libgraph_llmware.so' (no such file)

/Users/bcm/.pyenv/versions/anaconda3-2022.05/envs/llmware/bin/python /Applications/PyCharm.app/Contents/plugins/python/helpers/pydev/pydevd.py --multiprocess --qt-support=auto --client <IP_ADDRESS> --port 50399 --file /Users/bcm/gh/llmware/examples/getting_started.py
Connected to pydev debugger (build 231.9225.15)
Traceback (most recent call last):
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/Users/bcm/gh/llmware/llmware/library.py", line 24, in <module>
    from llmware.util import Utilities, Graph
  File "/Users/bcm/gh/llmware/llmware/util.py", line 1888, in <module>
    _mod_utility = cdll.LoadLibrary(_path_graph)
  File "/Users/bcm/.pyenv/versions/anaconda3-2022.05/envs/llmware/lib/python3.10/ctypes/__init__.py", line 452, in LoadLibrary
    return self._dlltype(name)
  File "/Users/bcm/.pyenv/versions/anaconda3-2022.05/envs/llmware/lib/python3.10/ctypes/__init__.py", line 374, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: dlopen(/Users/bcm/gh/llmware/llmware/libgraph_llmware.so, 0x0006): tried: '/Users/bcm/gh/llmware/llmware/libgraph_llmware.so' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Users/bcm/gh/llmware/llmware/libgraph_llmware.so' (no such file), '/Users/bcm/gh/llmware/llmware/libgraph_llmware.so' (no such file)
python-BaseException

Cloned directory and ran pip install -e ., then the getting started example. I cleared out my python 3.10 pyenv installation and created a new one from 3.10.13. No fix.
/Users/bcm/.pyenv/versions/llmware/bin/python /Users/bcm/gh/llmware/examples/getting_started.py
Traceback (most recent call last):
  File "/Users/bcm/gh/llmware/examples/getting_started.py", line 9, in <module>
    from llmware.library import Library
  File "/Users/bcm/gh/llmware/llmware/library.py", line 24, in <module>
    from llmware.util import Utilities, Graph
  File "/Users/bcm/gh/llmware/llmware/util.py", line 1888, in <module>
    _mod_utility = cdll.LoadLibrary(_path_graph)
  File "/Users/bcm/.pyenv/versions/3.10.13/lib/python3.10/ctypes/__init__.py", line 452, in LoadLibrary
    return self._dlltype(name)
  File "/Users/bcm/.pyenv/versions/3.10.13/lib/python3.10/ctypes/__init__.py", line 374, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: dlopen(/Users/bcm/gh/llmware/llmware/libgraph_llmware.so, 0x0006): tried: '/Users/bcm/gh/llmware/llmware/libgraph_llmware.so' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Users/bcm/gh/llmware/llmware/libgraph_llmware.so' (no such file), '/Users/bcm/gh/llmware/llmware/libgraph_llmware.so' (no such file)

@dahifi - thanks for reporting this!  This is due to the change in our packaging, and so now the native libraries need to be pulled into the repo.   To fix the error run this script in the repo:
scripts/dev/load_native_libraries.sh

then run
pip install .

The script downloads the right wheel for your platform and extracts the llmware native libraries and dependencies into the right place in your local copy of the repo.   We've updated the readme to reflect this updated information as well.

Thank you for confirming that I'm not crazy!


Adding estuary to charts

smartcitiesdata/smartcitiesdata#340
co-authored-by: Sukaant Chaudhary<EMAIL_ADDRESS>

Once this is all shored up, you also need to run package.sh to produce a tar file which is a versioned chart for estuary.  This is the verison you'll be referencing in your jenkinsfile upstream

@sukaant one thing to keep in mind is that we are also probably going to want to pull the kafka stuff from this chart as well as the presto config. I know flair has an example of this in their chart.


Fix: review app not deleted

Replacing wait for native concurrency feature which is less brittle
Context
Changes proposed in this pull request
Guidance to review
Important business

Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?

Test delete review app

 Register: review app not deleted


Update ossl_config.json for later BoringSSL commit and add ErrorMap

Update the list of suppressions so that we can run a later BoringSSL set
of tests. This also adds an ErrorMap to greatly reduce the number of
failing tests. The remaining tests that still fail are just disabled for
now.

Checklist

[ ] documentation is added or updated
[x] tests are added or updated

Description of change

Pushed. Thanks.


Fix: Remove nullish values on set and on merge when no value is in storage

@tgolen @marcaaron @hannojg
In the native implementation with SQLite, the first call to merge on a key where no value is in storage will act like a regular set since the values are inserted into storage directly.
This is due to this SQLite operation in SQLiteStorage.mergeItem:
INSERT INTO keyvaluepairs (record_key, valueJSON)
VALUES (:key, JSON(:value))
ON CONFLICT DO UPDATE
SET valueJSON = JSON_PATCH(valueJSON, JSON(:value));

In order for this to be consistent with how later merge with JSON_PATCH are working, we need to remove nullish values from the batchedChanged in the first merge operation.
Additionally, we'll want to remove nullish values on set as well, so that the values in cache and storage are always identical.

Details

Related Issues

Automated Tests

Linked PRs

To give another explanation to the issue at hand:
Calling Onyx.merge for a new key:

Onyx.merge(newKey, { prop1: 12, prop2: null})
Calls INSERT INTO as there is no conflict
In storage we now have: { prop1: 12, prop2: null}

Where as, when...
Calling Onyx.merge for an existing key:

Onyx.merge(key, { prop1: 12, prop2: null})
Calls JSON_PATCH as we have a conflict
In storage we now have: { prop1: 12 }

First of all, this is inconsistent behaviour, and secondly in the app code we don't expect the null values to be persisted, so it creates issues like this one:

https://github.com/Expensify/App/issues/24006

Awaiting another round of review, are we good to continue? This is blocking:

https://github.com/Expensify/App/pull/24041

@mountiny @marcaaron @tgolen


Fix link URL

@hteumeuleu : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@stevewhims : Thanks for your contribution! The author(s) have been notified to review your proposed change.


install script issues

hi @dylski
I am awaiting a inky screen, hopefully arrives tomorrow :)
I have run the install.sh on a Pi 4 to test. Using bullseye not bookworm.
I cannot find the generate_picture.py or display_picture.py files anywhere after the install. Are they copied somewhere? I cannot find them.
Obviously, I can download them from src directory on github. Suggestion: add that to the install.sh.
A thought / enhancement: on a Pi 4 it takes a long time to install. Could you consider modifying the script for cmake to use more than 1 core? It does go a lot faster when using an SD card. I re-ran it with:
cmake --build .  --config Release -- -j4
and it goes a lot faster. cmake appears to have an --all option to use all available cores. Maybe you could add a how many CPUs to use or a use all cores as a script option to allow the user to select?
The last step Filtering content: 100% (2640/2640)
takes a long time: is that just a function of the CPU speed or can it be speeded up by using more cores?
I will test using bookworm when I have it working on bullseye.
Thanks for your help
regards
Roger G7RUH

Thanks for the feedback.
The install.sh just installs everything you need to run the scripts so yes, just copy the src scripts wherever you like and run them using the python you pip installed everything else to.
I forgot to say in the README to start by cloning the repo.
You'll probably also want to edit the paths in generate_picture.py to point to where the your stable diffusion build is (e.g. OnnxStream\src\build\sd) and model is.
I'll also check the --all flag for compilation on the Zero and might add that to the script.
re. filtering content - I don't know anything about that. In all the whole install process took about 3 hours on my RPi-Zero.
I'll update the README with this information.

Thank you for the swift response.
I was thinking about those with limited python skills, maybe adding the copy of src scripts to the install.sh will help those who have construction skills but not computing skills. It would help give a working "out of the box" experience for novice python users.
With my Pi4 4GB time ./install.sh with -j4 gave:
real    47m41.005s
user    77m19.046s
sys     17m47.288s
I will try the same on the Pi ZW2 and report back.
I saw your creation on Tom's Hardware https://www.tomshardware.com/raspberry-pi/raspberry-pi-zero-2-w-uses-ai-to-make-infinite-flower-paintings-on-an-e-ink-display and thought: Ah! a Christmas present for somebody.
regards
Roger G7RUH


Fix readme and np.float

Oh, in this case, I think all my issues are related to the working directory paths. You may ignore it, then. Thanks!


remove "default" driver name capability registration

We register capabilities.name based on driver name. Let's skip this field for "default" to have regular selenium sessionId assigned.
But let's continue to substitute for non "default" use case

done. @okamara testing should be done using 7.3.15-SNAPSHOT carina.
just execute on any env web-demo-test job. Video recording driver session should be named having long uuid instead of "default"

Verified, fixed.


punycode.toUnicode not working

That's it. A week ago I was able to convert emails with "xn--" to Unicode, and now it isn't.

The same I got with https://xn--d1aqf.xn--p1ai/, which should be https://дом.рф/, but this lib returns https://xn--d1aqf.эрф.

uri-js seems working for me.

UPD: that was my bad, Punycode works only with domains (hostnames; be careful: without ports), so I've changed the code to ugly one:
https://replit.com/@AlexWayfer/punycode


Parser fails if column name is synonym

Parser failed with JSQLParserException if a column name in select statement is synonym.
eg: select businessDate as "bd", synonym as "synonym" from sc.tab

On Tue, 2021-05-25 at 09:53 +0000, salonijuneja wrote:

select businessDate as "bd", synonym as "synonym" from sc.tab

It is NOT about the alias, but about the unquoted column name:
"synonym" is a Keyword and you can't use that without quotes.
Please close the issue, when confirmed.
Best regards
Andreas

It is NOT about the alias, but about the unquoted column name:

"synonym" is a Keyword and you can't use that without quotes.
Please close the issue, when confirmed.
Best regards
Andreas

But this query (without quotes) executes successfully without error on Database (Sybase IQ though)

@manticore-projects To allow keywords as object names you could include those in RelObjectNameWithoutValue. In some cases this is not possible because the conflicts in JSqlParser grammar would be to huge to tackle, but this synonym keyword made no problems.


Heatmap code not quite correct - I'll try and fix it

Bit more fiddly than I thought. It worked for 2019.02.XX because 2018 was always the projection years. @cgrandin let's work on this early this afternoon if we can.
We don't use the -1940 row (but have it hardiwred at the start of the function), so fixing that (to extract from wtatage) will actually be good anyway. But currently base.model$wtatage does not contain the -1940 row.

I guess SS doesn't need to know the weights until there is catch, which starts in 1966, so can ignore earlier years. However, since there is no weight-at-age data from 1966, you could just use the 1966 row in base.model$wtatage as the source for the mean. You could also just change the format of the plot however you wish.

There is still a hardwired mean in there but the code is fixed for the rest of the issues. I didn't use the 1966 values as the long term mean because some calls to the function can be with models that have the pre-1975 value being other than long-term mean. For example some of the fecundity sensitivity models.

I'm just finishing up switch sensitivity figures/captions for all
sensitivities (minus the fecundity ones).  Will commit shortly.
On Fri, Feb 1, 2019 at 1:25 PM Andrew Edwards<EMAIL_ADDRESS>wrote:

Great. I'll test it this afternoon when sorting out the sensitivity runs
(captions are still wrong). I'm off until about 3, then will work till 7....
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cgrandin/hake-assessment/issues/504#issuecomment-459872874,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHk_-i-31HQHZwbzP3AdONBDrUtACy79ks5vJLC9gaJpZM4ae0ti
.

--
Aaron M. Berger, Ph.D. Research Mathematical Statistician
Fishery Resource Analysis and Monitoring Division
Northwest Fisheries Science Center
2032 SE OSU Dr. Bldg. 955
Newport, OR 97365-5275
<EMAIL_ADDRESS><EMAIL_ADDRESS>


Error while fine tuning the demo model

Hi
I'm trying to fine tune the cyclevae model with my own data and I'm using the pretrained model of the compatible demo. I've done all the stages of preprocessing (0init123) and I don't need to do the stages 4 and 5. In stage 6 when I pass the pkl file to the script it requires another checkpoint file (checkpoint 53). I renamed the checkpoint file to checkpoint 53 and I got torch size mismatch error.
Can you tell me how to fine tune the compatible demo with my own data? Thanks for your reply.

Hi, very sorry for the late response.
It would be better if you train the initial VC model with your data because the given model was already fine-tuned twice, on stage 6 and stage 7, and will not be appropriate for further fine-tuning with unseen data. The error was indeed caused by the difference in the number of speakers, as the decoders in the VC module requires one-hot conditioning with n_spk dimension.
You could try to train the VC model from stage 4 using your own data, and then fine-tune it on stage 6 and 7 with the pretrained neural vocoder. If you still prefer to just use the given model, you might need to slightly modify your spk_list variable in the script to match the predefined number for VCC20 speakers, i.e., 14.
Hope it helps.


Unable to receive alert email

Hi, I unable to receive email alert from KaaE. I can see alerts under "Alarms" section of KaaE plugin dashboard.
I able to receive mail when sent through command line from the server where Kibana + KaaE is running.
_echo "testing"|mail -s "testing"<EMAIL_ADDRESS>
There is no username/password required to send email. I just need to specify email ID of recipient. [i tested Yelp/elastalert -- received alert by just giving email ID] Please suggest what setting i should put in kaae.json file. I even tried giving user and password but still no email in my inbox.
kaae.json
"settings" : {
"email" : {
"user":	"",
"password":	"",
"host":	"relay.mycompany.com",
"ssl":	true,
"active":	false
},
Below is the msg i get under kibana.log
{"type":"log","@timestamp":"2016-09-19T06:23:00+00:00","tags":["status","info","KaaE"],"pid":26910,"message":"Executing watch: RPM Next Round of RPM at Sun Sep 18 2016 23:23:00 GMT-0700 (PDT)"}
{"type":"log","@timestamp":"2016-09-19T06:23:00+00:00","tags":["status","info","KaaE"],"pid":26910,"message":"Action Report requires Email Settings! Reports Disabled."}
{"type":"log","@timestamp":"2016-09-19T06:23:00+00:00","tags":["status","info","KaaE"],"pid":26910,"message":"Processing action: email_admin"}
{"type":"log","@timestamp":"2016-09-19T06:23:00+00:00","tags":["status","info","KaaE","email"],"pid":26910,"message":"Subject: KAAE ALARM , Body: Series Alarm : 76"}
{"type":"log","@timestamp":"2016-09-19T06:23:00+00:00","tags":["status","info","Kaae","email"],"pid":26910,"message":"Delivery Disabled!"}
{"type":"log","@timestamp":"2016-09-19T06:23:00+00:00","tags":["status","info","KaaE"],"pid":26910,"message":"Storing Alarm to ES with type:email_admin"}

Hi @sunnynew , in your configuration block you explicitly need to set active-ness.
This log-line tells the story:
["status","info","Kaae","email"],"pid":26910,"message":"Delivery Disabled!"}

You can resolve by changing the following parameter:
"active":  true

Hi Imangani,
Thanks for quick response. After changing "active":  true, getting below exceptions.
{"type":"log","@timestamp":"2016-09-19T07:57:00+00:00","tags":["status","info","KaaE"],"pid":4746,"message":"Executing watch: RPM Next Round of RPM at Mon Sep 19 2016 00:57:00 GMT-0700 (PDT)"}
{"type":"log","@timestamp":"2016-09-19T07:57:00+00:00","tags":["status","info","KaaE"],"pid":4746,"message":"Processing action: email_admin"}
{"type":"log","@timestamp":"2016-09-19T07:57:00+00:00","tags":["status","info","KaaE","email"],"pid":4746,"message":"Subject: KAAE ALARM , Body: Series Alarm : 28"}
{"type":"log","@timestamp":"2016-09-19T07:57:00+00:00","tags":["status","info","Kaae","email"],"pid":4746,"message":"Delivering to Mail Server"}
{"type":"log","@timestamp":"2016-09-19T07:57:00+00:00","tags":["status","info","Kaae","email"],"pid":4746,"level":"error","message":"message is not a valid Message instance","error":{"message":"message is not a valid Message instance","name":"Error","stack":"Error: message is not a valid Message instance\n    at Object.Client.send (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/emailjs/smtp/client.js:122:19)\n    at /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/server/lib/actions.js:125:27\n    at /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/lodash/lodash.js:4738:15\n    at baseForOwn (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/lodash/lodash.js:2879:24)\n    at Function.forOwn (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/lodash/lodash.js:12670:24)\n    at exports.default (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/server/lib/actions.js:83:4)\n    at /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/server/lib/scheduler.js:79:19\n    at tryCatcher (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/util.js:26:23)\n    at Promise._settlePromiseFromHandler (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/promise.js:503:31)\n    at Promise._settlePromiseAt (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/promise.js:577:18)\n    at Promise._settlePromises (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/promise.js:693:14)\n    at Async._drainQueue (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/async.js:123:16)\n    at Async._drainQueues (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/async.js:133:10)\n    at Immediate.Async.drainQueues [as _onImmediate] (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/async.js:15:14)\n    at processImmediate [as _immediateCallback] (timers.js:383:17)"}
{"type":"log","@timestamp":"2016-09-19T07:57:00+00:00","tags":["status","info","KaaE"],"pid":4746,"message":"Executing watch: RPM Next Round of RPM at Mon Sep 19 2016 00:57:00 GMT-0700 (PDT)"}
{"type":"log","@timestamp":"2016-09-19T07:57:00+00:00","tags":["status","info","KaaE"],"pid":4746,"message":"Processing action: email_admin"}
{"type":"log","@timestamp":"2016-09-19T07:57:00+00:00","tags":["status","info","KaaE","email"],"pid":4746,"message":"Subject: KAAE ALARM , Body: Series Alarm : 28"}
{"type":"log","@timestamp":"2016-09-19T07:57:00+00:00","tags":["status","info","KaaE"],"pid":4746,"message":"Storing Alarm to ES with type:email_admin"}
Unhandled rejection Error: spawn phantomjs ENOENT
at exports._errnoException (util.js:870:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at nextTickCallbackWith2Args (node.js:442:9)
at process._tickDomainCallback (node.js:397:17

Hi @sunnynew
I suggest you activate one plugin at the time to ease troubleshooting. We'll need to see the watcher you scheduled as the issue seems to be with the body of the email you are trying to send, and with the absence of phantomjs for the Report issue, which needs to be available on the system upfront.

Hi,
Sorry for any confusion, I am just using KaaE for alerting as of now. Below is my watcher -- simple one to alert if requests in access log went above 25.
_{
"_index": "watcher",
"_type": "watch",
"_id": "RPM",
"_score": 1,
"_source": {
"trigger": {
"schedule": {
"later": "every 1 minute"
}
},
"input": {
"search": {
"request": {
"indices": [
"<access-{now/d}>",
"<access-{now/d-1d}>"
],
"body": {
"size": 0,
"query": {
"filtered": {
"query": {
"query_string": {
"analyze_wildcard": true,
"query": "*"
}
},
"filter": {
"range": {
"@timestamp": {
"from": "now-5m"
}
}
}
}
},
"aggs": {}
}
}
}
},
"condition": {
"script": {
"script": "payload.hits.total > 25"
}
},
"transform": {},
"actions": {
"email_admin": {
"throttle_period": "15m",
"email": {
"to"<EMAIL_ADDRESS>"subject": "KAAE ALARM {{ payload._id }}",
"priority": "high",
"body": "Series Alarm {{ payload.id}}: {{ payload.hits.total }}"
}
}
}
}
}

phantomjs is installed.
[root@host opt]$ phantomjs /opt/phantomjs/examples/hello.js
Hello, world!

As mentioned above getting below error.
{"type":"log","@timestamp":"2016-09-19T09:52:00+00:00","tags":["status","info","KaaE"],"pid":4746,"message":"Executing watch: RPM Next Round of RPM at Mon Sep 19 2016 02:52:00 GMT-0700 (PDT)"}
{"type":"log","@timestamp":"2016-09-19T09:52:00+00:00","tags":["status","info","KaaE"],"pid":4746,"message":"Processing action: email_admin"}
{"type":"log","@timestamp":"2016-09-19T09:52:00+00:00","tags":["status","info","KaaE","email"],"pid":4746,"message":"Subject: KAAE ALARM , Body: Series Alarm : 44"}
{"type":"log","@timestamp":"2016-09-19T09:52:00+00:00","tags":["status","info","Kaae","email"],"pid":4746,"message":"Delivering to Mail Server"}
{"type":"log","@timestamp":"2016-09-19T09:52:00+00:00","tags":["status","info","Kaae","email"],"pid":4746,"level":"error","message":"message is not a valid Message instance","error":{"message":"message is not a valid Message instance","name":"Error","stack":"Error: message is not a valid Message instance\n    at Object.Client.send (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/emailjs/smtp/client.js:122:19)\n    at /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/server/lib/actions.js:125:27\n    at /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/lodash/lodash.js:4738:15\n    at baseForOwn (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/lodash/lodash.js:2879:24)\n    at Function.forOwn (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/lodash/lodash.js:12670:24)\n    at exports.default (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/server/lib/actions.js:83:4)\n    at /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/server/lib/scheduler.js:79:19\n    at tryCatcher (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/util.js:26:23)\n    at Promise._settlePromiseFromHandler (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/promise.js:503:31)\n    at Promise._settlePromiseAt (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/promise.js:577:18)\n    at Promise._settlePromises (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/promise.js:693:14)\n    at Async._drainQueue (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/async.js:123:16)\n    at Async._drainQueues (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/async.js:133:10)\n    at Immediate.Async.drainQueues [as _onImmediate] (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/async.js:15:14)\n    at processImmediate [as _immediateCallback] (timers.js:383:17)"}}

Hi @sunnynew I see the problem now. You are missing the FROM email parameter which is mandatory.

Hooray! Lovely!!  -- Start getting alerts :+1:   Thanks a ton @lmangani
After adding FROM section in watcher, i got below error but i get rid of it by making ssl:false in kaae.json
{"type":"log","@timestamp":"2016-09-19T11:03:00+00:00","tags":["status","info","KaaE","email"],"pid":4746,"message":"Subject: KAAE ALARM , Body: Series Alarm : 36"}
{"type":"log","@timestamp":"2016-09-19T11:03:00+00:00","tags":["status","info","Kaae","email"],"pid":4746,"message":"Delivering to Mail Server"}
{"type":"log","@timestamp":"2016-09-19T11:03:00+00:00","tags":["status","info","KaaE"],"pid":4746,"message":"Storing Alarm to ES with type:email_admin"}
{"type":"log","@timestamp":"2016-09-19T11:03:00+00:00","tags":["status","info","Kaae","email"],"pid":4746,"level":"error","message":"connection encountered an error","error":{"message":"connection encountered an error","name":"Error","stack":"Error: connection encountered an error\n    at module.exports (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/emailjs/smtp/error.js:3:13)\n    at TLSSocket.error (/opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/emailjs/smtp/response.js:26:29)\n    at emitOne (events.js:82:20)\n    at TLSSocket.emit (events.js:169:7)\n    at emitErrorNT (net.js:1253:8)\n    at nextTickCallbackWith2Args (node.js:442:9)\n    at process._tickDomainCallback (node.js:397:17)","code":5}}

Just a suggestion: when we create new watcher by clicking "Set Watcher" button under Visualize section in kibana FROM section is missing. That is why FROM section was missing from email parameter in my watcher config.
Thanks again!

Excellent! I'll extend the wiki with this information.
Glad its working now and don't hesitate to open new issues in case you find any.
Resolving.

I'm wondering if we should just determine the from in the snmp configuration directly and have it apply for all actions using it? Comments?

Hi,
1). First check if FROM section is provided by user  under email parameter, if not
2). Pick from  snmp configuration directly
System shouldn't fail, some default should be picked.
Thanks!

Hi @lmangani
I would like to discuss issues related to hourly "Reporter" where we send snapshot of Alerts dashboard.
Issue 1)
I have created a Kibana dashboard which is accessible as per URL defined. There are few report graphs added in that dashboard. I do receive a email with snapshot attached but report graphs are not visible, kind of blank Snapshot, just  Discover | Visualize | Dashboard |  Setting menu on top and blank white body without any graph/report.
{
  "_index": "watcher",
  "_type": "watch",
  "_id": "Hourly Report",
  "_score": 1,
  "_source": {
    "trigger": {
      "schedule": {
        "later": "every 1 hour"
      }
    },
    "report": true,
    "transform": {},
    "actions": {
      "report_admin": {
        "throttle_period": "15m",
        "report": {
          "to"<EMAIL_ADDRESS>          "from"<EMAIL_ADDRESS>          "subject": "KaaE Hourly Alert Report",
          "priority": "high",
          "body": "Sample KaaE Screenshot Report",
          "snapshot": {
            "res": "1280x900",
            "url": "http://<hostname>.com:5601/app/kibana#/dashboard/Alerts",
            "path": "/tmp/",
            "params": {
              "username": "",
              "password": "",
              "delay": 300,
              "crop": false
            }
          }
        }
      }
    }
  }
}

I tied increasing delay value in assumption that may be dashboard taking time to load completely. But that also doesn't help.
Issue 2)
I tested "Reporter" with 5 min interval. After each execution, one process remain in running state in the system. Kibana get crashed when # of such process increased overtime. I had to kill all these manually.
root       502  0.2  0.8 2453696 137760 pts/1  SNl  21:49   0:06 phantomjs --load-images=true --ssl-protocol=any /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/node-phantom-simple/bridge.js
root       951  0.2  0.8 2450508 137664 pts/1  SNl  21:54   0:06 phantomjs --load-images=true --ssl-protocol=any /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/node-phantom-simple/bridge.js
root      1401  0.2  0.8 2450280 137692 pts/1  SNl  21:59   0:05 phantomjs --load-images=true --ssl-protocol=any /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/node-phantom-simple/bridge.js
root      2274  0.2  0.8 2450248 140476 pts/1  SNl  22:04   0:05 phantomjs --load-images=true --ssl-protocol=any /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/node-phantom-simple/bridge.js
root      2707  0.3  0.9 2463208 146908 pts/1  SNl  22:09   0:05 phantomjs --load-images=true --ssl-protocol=any /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/node-phantom-simple/bridge.js
root      3149  0.3  0.8 2463148 144840 pts/1  SNl  22:14   0:05 phantomjs --load-images=true --ssl-protocol=any /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/node_modules/node-phantom-simple/bridge.js

Hi,
Snapshot issue resolved after i increased delay: 5000, it seems like value is in ms.
@lmangani please take a look at phantomjs thread issue which remain running after every Reporter execution.
Thanks!

Please open a new issue for PhantomJS so we can troubleshoot it. Have you followed the Wiki steps?
https://github.com/elasticfence/kaae/wiki/KAAE-Report-Example#requirements

Sorry i didn't went through all Wiki steps.
Opened a new issue for PhantomJS
Thanks!

@lmangani Do we have any KaaE 95th response time watcher example.
I want watcher for 95th response time from access log which aggregated to elasticsearch. Field name : ResponeTime

You should be able to generate this from any visualizer using the Kaae SPY extension. Create an aggregation with 95th percentile and adapt the output to use it following the Aggs Watcher Example (this might be a bit tricky at the beginning)

Hi @lmangani
can you please review below watcher -- getting "message":"Condition Error for 95th: SyntaxError: Unexpected number"}
{
  "_index": "watcher",
  "_type": "watch",
  "_id": "95th",
  "_score": 1,
  "_source": {
    "trigger": {
      "schedule": {
        "later": "every 5 minutes"
      }
    },
    "input": {
      "search": {
        "request": {
          "indices": [
            "<access-{now/d}>",
            "<access-{now/d-1d}>"
          ],
          "body": {
            "size": 0,
            "query": {
              "filtered": {
                "query": {
                  "query_string": {
                    "analyze_wildcard": true,
                    "query": "*"
                  }
                },
                "filter": {
                  "range": {
                    "@timestamp": {
                      "from": "now-5m"
                    }
                  }
                }
              }
            },
            "aggs": {
              "2": {
                "percentiles": {
                  "field": "response_time",
                  "percents": [
                    95
                  ]
                }
              }
            }
          }
        }
      }
    },
    "condition": {
      "script": {
        "script": "payload.aggregations.2.values.95 > 1000"
      }
    },
    "transform": {},
    "actions": {
      "email_admin": {
        "throttle_period": "15m",
        "email": {
          "to"<EMAIL_ADDRESS>          "from"<EMAIL_ADDRESS>          "subject": "KAAE ALARM {{ payload._id }}",
          "priority": "high",
          "body": "Series Alarm {{ payload._id}}: {{ payload.aggregations.2.values.95 }}"
        }
      }
    }
  }
}

Watcher for Avg Response time is working fine...
            "aggs": {
              "avg": {
                "avg": {
                  "field": "response_time"
                }
              }
            }
          }
        }
      }
    },
    "condition": {
      "script": {
        "script": "payload.aggregations.avg.value > 1000"
      }

Just percentiles isn't working and keep giving below error
{"type":"log","@timestamp":"2016-09-21T03:16:00+00:00","tags":["status","info","KaaE"],"pid":1871,"message":"Condition Error for 95th: SyntaxError: Unexpected number"}
            "aggs": {
              "response_time_outlier": {
                "percentiles": {
                  "field": "response_time",
                  "percents": [
                    95
                  ]
                }
              }
            }
          }
        }
      }
    },
    "condition": {
      "script": {
        "script": "payload.aggregations.response_time_outlier.values.95.0 > 1500"
      }
    },

If you share the actual query response we can try figure this out

Elasticsearch response body
{
  "took": 14,
  "timed_out": false,
  "_shards": {
    "total": 6,
    "successful": 6,
    "failed": 0
  },
  "hits": {
    "total": 43386,
    "max_score": 0,
    "hits": []
  },
  "aggregations": {
    "response_time_outlier": {
      "values": {
        "95.0": 2007.6466
      }
    }
  }
}

I see. Could you try selecting the "95.0" field as follows:
payload.aggregations.response_time_outlier.values['95.0']

Hi, giving below error
{"type":"log","@timestamp":"2016-09-21T09:27:00+00:00","tags":["status","info","KaaE"],"pid":5868,"message":"Executing watch: Stats log Failures Next Round of Stats log Failures at Wed Sep 21 2016 02:27:00 GMT-0700 (PDT)"}
{"type":"log","@timestamp":"2016-09-21T09:27:00+00:00","tags":["status","info","KaaE"],"pid":5868,"message":"Executing watch: 95th Next Round of 95th at Wed Sep 21 2016 02:27:00 GMT-0700 (PDT)"}
{"type":"log","@timestamp":"2016-09-21T09:27:00+00:00","tags":["status","info","KaaE"],"pid":5868,"message":"Condition Error for 95th: SyntaxError: Unexpected token ["}
{"type":"log","@timestamp":"2016-09-21T09:27:00+00:00","tags":["status","info","KaaE"],"pid":5868,"message":"Clearing watcher: 95th"}
{"type":"log","@timestamp":"2016-09-21T09:27:00+00:00","tags":["status","info","KaaE"],"pid":5868,"message":"Scheduled Watch: 95th every every 1 minutes"}

{"type":"log","@timestamp":"2016-09-21T09:28:00+00:00","tags":["status","info","KaaE"],"pid":5868,"message":"Executing watch: 95th Next Round of 95th at Wed Sep 21 2016 02:28:00 GMT-0700 (PDT)"}
{"type":"log","@timestamp":"2016-09-21T09:28:00+00:00","tags":["status","info","KaaE"],"pid":5868,"message":"Processing action: email_admin"}
{"type":"log","@timestamp":"2016-09-21T09:28:00+00:00","tags":["status","info","KaaE","email"],"pid":5868,"message":"Subject: 95th Search RT -- KAAE ALARM , Body: Series Alarm : "}
{"type":"log","@timestamp":"2016-09-21T09:28:00+00:00","tags":["status","info","Kaae","email"],"pid":5868,"message":"Delivering to Mail Server"}
{"type":"log","@timestamp":"2016-09-21T09:28:00+00:00","tags":["status","info","KaaE"],"pid":5868,"message":"Storing Alarm to ES with type:email_admin"}
Trace: { [Error: [mapper_parsing_exception] Field name [95.0] cannot contain '.']
  status: 400,
  message: '[mapper_parsing_exception] Field name [95.0] cannot contain \'.\'',
  path: '/watcher_alarms-2016.09.21/email_admin',
  query: { op_type: 'create' },
  body:
   { error:
      { root_cause: [Object],
        type: 'mapper_parsing_exception',
        reason: 'Field name [95.0] cannot contain \'.\'' },
     status: 400 },
  statusCode: 400,
  response: '{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"Field name [95.0] cannot contain \'.\'"}],"type":"mapper_parsing_exception","reason":"Field name [95.0] cannot contain \'.\'"},"status":400}',
  toString: [Function],
  toJSON: [Function] } undefined
    at /opt/kibana-4.5.1-linux-x64/installedPlugins/kaae/server/lib/actions.js:77:22
    at tryCatcher (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/promise.js:503:31)
    at Promise._settlePromiseAt (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/promise.js:577:18)
    at Promise._settlePromises (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/promise.js:693:14)
    at Async._drainQueue (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/opt/kibana-4.5.1-linux-x64/node_modules/bluebird/js/main/async.js:15:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

You just need to escape the high commas to let the value being interpreted as string, ie:

payload.aggregations.response_time_outlier.values[\'95.0\']

KaaE editor doesn't allow -- says  Bad string

Hi @lmangani
I hope you are working on to get a fix :+1:

Hi @sunnynew this is not a bug but a syntax issue with fields containing a . in the key name - please experiment with the selection and update on the attempts and results, I'll help find a suitable way

I am trying to get rid of . in the key name, tried all permutation and combination but nothing worked as yet :(
Nothing to escape . from key name.

The error is because kaae try to insert alarm into es, but fieldname contains .. Maybe you need to upgrade to es 2.4.0 which allowed dot in fieldname again.

The error is because kaae try to insert alarm into es, but fieldname contains .. Maybe you need to upgrade to es 2.4.0 which allowed dot in fieldname again.

Thanks to kaaemaster @chenryn we might have a solution for this scenario:
https://github.com/elasticfence/kaae/commit/563bfa639cc0698f882e42bfee8bdaa23be2bb78

That great news -- so are we going to release a batch for KaaE

Thanks - please open a new issue with the new results so we can track this properly


Fix ComputeUncompute State Fidelity threading issue

Summary
Fixes #91
Details and comments
I changed the logic so that the sampler.run is done in the main thread and the resulting job and result is processed for the fidelity result in a separate method that is run by the thread executor of the algorithm job. This new method (_call which I named to be the same as the ref. primitives) gets passed all it needs as params, self is not passed, and where that logic was using some private instance utility methods I turned these to static (they never used self anyway).
As far as an end user goes the ComputeUncompute is used just the same way. As I changed things around a little bit though any developer that might have extended the base class, for some custom fidelity, would need to update their code for the _run.
I kept the changes minimal though the presence of the _run is a little harder to justify as things are now, but I figure, if more fidelities are added going forwards that may be a better time to sort out commonality than change things around more now.
I'll add a reno once others have had a chance to look over this. It would note the bug fix and point out the change to _run should anyone happen to have made their own fidelity off the base.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

16 of 16 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 90.537%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
6458

Relevant Lines:
7133

💛  - Coveralls

Its not so much about self itself more that it refers to a mutable object and if the thread can read values that are changing in the main thread context... Passing whatever values that the function run under the thread needs to me makes things explicit rather than passing a reference to a larger object and letting it have at it, and the values are on the stack. To me its more playing it safe and hopefully, if any future changes might be made, doing things explicitly like this is clearer etc. Of course if one of those values, is really a reference and again mutable you are back towards passing self....


Context menu key doesn't work in combobox

🐛 Bug Report
Pressing the context menu key on the keyboard when the combobox has focus should open the context menu. It does nothing.
💻 Repro or Code Sample
Give the combobox focus and press the context menu button on the keyboard.
🤔 Expected Behavior
Context menu should open
😯 Current Behavior
Nothing happens

@m-akinc is there any context for where this requirement comes from? Aria keyboard interactions? FAST behavior? Native select control parity?

So, for context, this issue seems to be present on Chrome and not Firefox. Additionally, this is happens with the FAST Combobox as well. My feeling is that we should be filing an issue against FAST.

Ah I see. This issue is about the combobox blocking the browser native context menu when using the menu key: https://en.wikipedia.org/wiki/Menu_key
Right clicking to open the context menu and shift+f10 (didn't know that shortcut) to open the context menu aren't blocked. I was able to reproduce the issue using the context menu key of the windows on-screen keyboard.
I misunderstood and thought we were trying to open the combobox menu with that key. Instead we are trying to not accidentally block the native context menu from opening. Thanks for the context.

Closing as low ROI


Improve I18n

This is happen mailing in the Breadcrumb, i think that is just in there. But it is nice for someone look around.

Sorry, but I didn't get. What tasks is involved in this issue?

Hi, again I ask: what this issue is for?

All the i18n problems and misspellings was already solved in other issues. So i am closing this one.


[patroni] Support updating database credentials via chart upgrade

Is this a request for help?:
Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug report

Version of Helm and Kubernetes:
Helm 2.7.0
Kubernetes 1.8.1-gke1
Which chart:
patroni
What happened:
helm install/upgrade of release succeeds and all pods start correctly, but connection to postgres using "to connect to your database" post-helm-install text fails with
psql: FATAL:  password authentication failed for user "postgres"
FATAL:  password authentication failed for user "postgres"

when attempting to connect as superuser.
This occurs when installing/upgrading a release name which has already has this chart installed to it currently/previously (i.e. purged)
What you expected to happen:
I expected to be able to connect to postgres
How to reproduce it (as minimally and precisely as possible):
# fresh install to not previously used release name
helm upgrade --install patroni-1 incubator/patroni

# login as superuser
PGPASSWORD_SUPERUSER=$(kubectl get secret --namespace default patroni-1 -o jsonpath="{.data.password-superuser}" | base64 --decode)
kubectl run -i --tty --rm psql --image=postgres --env "PGPASSWORD=$PGPASSWORD_SUPERUSER" --command -- psql -U postgres -h patroni-1.default.svc.cluster.local postgres

# auth is successful
> postgres=#

# logout and upgrade release with identical values (i.e. password not changed)
helm upgrade --install patroni-1 incubator/patroni

# attempt to login again
kubectl run -i --tty --rm psql --image=postgres --env "PGPASSWORD=$PGPASSWORD_SUPERUSER" --command -- psql -U postgres -h patroni-1.default.svc.cluster.local postgres

# authentication fails
> psql: FATAL:  password authentication failed for user "postgres"
> FATAL:  password authentication failed for user "postgres"

# now try completely removing release and redeploying
helm del --purge patroni-1
helm upgrade --install patroni-1 incubator/patroni

# login continues to fail
kubectl run -i --tty --rm psql --image=postgres --env "PGPASSWORD=$PGPASSWORD_SUPERUSER" --command -- psql -U postgres -h patroni-1.default.svc.cluster.local postgres

> psql: FATAL:  password authentication failed for user "postgres"
> FATAL:  password authentication failed for user "postgres"

# now deploy to a new release name on the same cluster and login when ready
helm upgrade --install patroni-2 incubator/patroni
PGPASSWORD_SUPERUSER=$(kubectl get secret --namespace default patroni-2 -o jsonpath="{.data.password-superuser}" | base64 --decode)
kubectl run -i --tty --rm psql --image=postgres --env "PGPASSWORD=$PGPASSWORD_SUPERUSER" --command -- psql -U postgres -h patroni-2.default.svc.cluster.local postgres

> postgres=#

Anything else we need to know:
n/a

I'm having the same issue with both postgres and redis.
Here is a shorter reproduction showing the password changing in the secrets store after an upgrade. I'm using redis in this example because the password is saved as clear text in the config, so it's easier to see what's going on.
> helm install --name password-bug stable/redis
...

> get secret password-bug-redis -o json | jq -r '.["data"]["redis-password"]' | base64 -d
c8pz98ACsD

> kubectl exec password-bug-redis-5484c8d64-dmw5k cat /opt/bitnami/redis/conf/redis.conf  | grep ^requirepass
requirepass c8pz98ACsD

> helm upgrade password-bug stable/redis
...

> kubectl get secret password-bug-redis -o json | jq -r '.["data"]["redis-password"]' | base64 -d
LBXTLIoN3U  # <-- newly generated password

> kubectl exec password-bug-redis-5484c8d64-dmw5k cat /opt/bitnami/redis/conf/redis.conf  | grep ^requirepass
requirepass c8pz98ACsD  # <-- original password

A not so optimal fix is not using the random password generation, and instead hardcode a password in the password parameter, i.e. postgresPassword and redisPassword.

Found this issue in https://github.com/kubernetes/helm/issues/3053

/remove-lifecycle stale


chore: deprecate splitVendorChunkPlugin

Description
We extracted the default split vendor chunking strategy to a plugin so users could more easily migrate to Vite 2.8. This strategy always had edge cases (see latest here https://github.com/vitejs/vite/issues/16268). This PR deprecates the plugin, so we can remove it in Vite 6.

It's a good plugin and I like it.
It you don't want to maintain it, it makes sense to publish it as a separate package. At least, for the archive purpose.
It works fine for me and I want to continue using it.

@patak-dev Could you please tell me how to divide the code into chunks now?

You can use build.rollupOptions and set output.manualChunks


Updated gem to allow the use of Jekyll 4

I've updated the gem version to 1.3.0 and updated the Jekyll dependency to allow the use of Jekyll version <5. I've tested locally and works as expected. We should add some tests to check these changes don't affect anything obscure; but my knowledge of Ruby/gems is limited sadly :/
https://github.com/robwierzbowski/jekyll-picture-tag/issues/131

I am a terrible programmer-- the "test suite" is just a jekyll site with a bunch of picture tags in it. I've been meaning to do it properly...
This PR looks good, I'll run the "tests" againts it and hopefully merge it in today. Thanks so much for the help!


Add workflow to add the community label on external contributor PRs

What does this PR do?

Create a github workflow to automatically add the community and team/triage labels as well as Triage milestone on PRs from forks.
Motivation

Have a clearer view of external contributor PRs.
Additional Notes

Initially tried to use author organization membership, but it would require a Github Token with access to the DataDog org.
Example opened from a fork (labels and milestone added): https://github.com/DataDog/datadog-agent/pull/22009
Example from this repo (job skipped): https://github.com/DataDog/datadog-agent/pull/22011
Note that in the first one the job appears failed on the PR but it's actually an older run, the run which added the labels succeeded (the event type changed from pull_request to pull_request_target so it doesn't override it).
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


docs: explain to users how to do function multiversioning / CPU dispatching with SIMDe

Including examples
See https://github.com/alexdobin/STAR/pull/1163#issuecomment-794130429

It would be nice, but doing this portably is a lot of work.
The major problem your build system would need to rebuild a file repeatedly using different flags, once for each variant that you'd like to offer.  There is no way to just repeatedly #include a file and keep everything in C; build system integration is required.  That means teaching X different build systems about the right flags for Y different compilers for Z different ISA extensions.
Next you would need some macros to tweak the symbol names for each extension (i.e., foo_sse, foo_avx, foo_avx512, foo_neonv7, foo_neonv8, foo_neonaarch64, etc.), or have a separate shared library for each variant which could then be dlopened (sort of like the how the new hwcaps stuff works).
Then you need a way to choose the best version based on runtime CPU feature detection.  cpu_features is a good choice, but last time I looked it requires CMake.  I also have some code in portable snippets which could do the job (though it would require a good amount of work first).
Basically, this is a pretty good sized project all on its own.  While it would be applicable to SIMDe, it would be by no means unique to SIMDe.  I'd be happy to participate, but not as a solo effort.
If this were a normal GSoC year I'd say a PoC may be a good project (with lots of mentor involvement), but since projects are compressed this year it's likely too big of a task for even a relatively skilled student.

Thanks @nemequ for your response. I think the task can be broken further down to manageable milestones that still provide value along the way.

That means teaching X different build systems about the right flags for Y different compilers for Z different ISA extensions.

I don't think the instructions vary for other ISA extensions. Showing one example for x86 on a single build system would already be a huge help.
Here's a possible breakdown of this project into phases.

Find examples of how current SIMDe using projects accomplish this, and put them in a table that mentions

Their build system

Which approach they took for organizing the compilation units (dynamically loaded shared objects or renamed top-level function)

How they did cpu feature detection

Which architectures (just x86?) they compile multiple versions for

Replicate minimal examples from these that we can test ourselves.

Write a guide for a single build system on how to upgrade an existing codebase using this technique. The guide should should the evolution of a small tool, and all stages should be under our CI. It doesn't have to target all compilers.

Iteratively improve all of the above. Writing new guides for additional build systems. Add different compilers to existing examples/guides.

Phase one and two might fit in a GSoC project (though if we suggest that for this year is another conversation). We can't do just phase one for GSoC because there needs to be code written. Phase 1, 3, and 4 could be part of a Season of Docs project (probably best combined with other documentation needs).

As discussed in chat, I'm working on this, but here is a very simple version which might help illustrate the concept.  The final version will be much harder to follow, so I just wanted to keep this around somewhere:
#include <stdio.h>

void my_function_sse2(void) {
  printf("Hello from SSE2\n");
}

void my_function_avx(void) {
  printf("Hello from AVX\n");
}

typedef struct {
  void (* my_function)(void);
} MyFunctionTable;

static const MyFunctionTable my_function_table_sse2 = {
  my_function_sse2
};

static const MyFunctionTable my_function_table_avx = {
  my_function_avx
};

static const MyFunctionTable*
my_function_table_resolve(void) {
  static const MyFunctionTable* table = NULL;

  if (table == NULL) {
    __builtin_cpu_init();

    if (__builtin_cpu_supports("avx")) {
      table = &my_function_table_avx;
    } else {
      table = &my_function_table_sse2;
    }
  }

  return table;
}

void my_function(void) {
  return my_function_table_resolve()->my_function();
}

int main(void) {
  my_function();

  return 0;
}


Connection automatically reconnects after intentionally calling pusher.disconnect()

Steps to reproduce
VERSION: "9.2.2"

Initialize Pusher instance: let pusher = Pusher(key: "APP_KEY")
Start connect to Pusher: pusher.connect()
Stop connect to Pusher: pusher.disconnect()

Expected behavior
No connection to Pusher after that
Actual behavior
After about 2 minutes, pusher automatically reconnects the connection
Any improvements you suggest
As I investigated, the reason is because of pongResponseTimeoutTimer is triggered in PusherConnection.swift, so the connect() method is called again.
My suggestion: We can check whether to reconnect again or NOT based on intentionalDisconnect instance property of PusherConnection class.

You're right, is reconnecting. I will get someone to take a look at your PR.


Vyper support

I was just wondering if Azure Blockchain Workbench supports or will support in the future the Vyper contract language (https://github.com/ethereum/vyper)?

As far as I know, Azure Blockchain Workbench has no plan to support Vyper contract languages.

Ok, thank you.


Support VS Code and Rider installed with scoop

Inspired by PR #237

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: oskar sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

thanks. this is now deployed

Thanks for the quick response!


MTR 3.2.2 Track, stations, elevator, fails, to save In server

Before reporting, I have confirmed that

[X] This bug does not appear to be reported on GitHub Issues before.
[X] This bug still exists in the latest version of the Minecraft Transit Railway mod.
[X] I have tested this in the official version of Minecraft Transit Railway, not a modified, custom, or unofficial build.

Describe the Bug
Every time I simply place down a track. or name a station even placing an elevator.  The rails is gone node Is invisible And the elevator is gone. and the stations are wipe. No names, no nothing. Not even a depot. Its like im starting from ground zero again. And is pretty sad because. everybody inside the server love this mod. It brings the life just traveling places and we can't do that because of the issue. I even tried fixing it using nemo transit mod and that didn't even work It just resort to the same issue. It used to work perfectly around. June until now it doesn't work.
Reproduction Steps

Simply placed down some tracks and names stations.
Turns off the server.
Turn the server back on. None of the stuff that I placed down saved.

In-game Log and Crash Report
[22Jul2024 00:04:11.515] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: devanohdevan was blown up by Wilden Chimera
[22Jul2024 00:04:11.522] [Server thread/INFO] [com.tiviacz.travelersbackpack.TravelersBackpack/]: Created new backpack backup file for devanohdevan with unique ID travelersbackpack.lapis_22.07.2024-00.04.11.dat
[22Jul2024 00:04:11.523] [Server thread/INFO] [com.tiviacz.travelersbackpack.TravelersBackpack/]: There's no space for backpack. Dropping backpack item at X: 6919 Y: 80.0 Z: -899
[22Jul2024 00:11:24.825] [Server thread/INFO] [net.minecraft.server.network.ServerGamePacketListenerImpl/]: devanohdevan lost connection: Disconnected
[22Jul2024 00:11:24.826] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: devanohdevan left the game
[22Jul2024 00:12:39.661] [Server thread/INFO] [net.minecraft.server.network.ServerGamePacketListenerImpl/]: KENDREX_ lost connection: Disconnected
[22Jul2024 00:12:39.662] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: KENDREX_ left the game
[22Jul2024 00:12:39.662] [Server thread/INFO] [de.geheimagentnr1.auto_restart.task.AutoRestartTask/]: Empty server timer started
[22Jul2024 00:16:37.355] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Stopping the server
[22Jul2024 00:16:37.406] [Server thread/INFO] [mtr.libraries.org.eclipse.jetty.server.AbstractConnector/]: Stopped<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:8888}
[22Jul2024 00:16:37.407] [Server thread/INFO] [mtr.libraries.org.eclipse.jetty.server.handler.ContextHandler/]: Stopped m.l.o.e.j.s.ServletContextHandler@9d6bd85{/,union:/C:/Users/kendr/Downloads/COBBLEMON%20ADVANCE%204.3.5/mods/MTR-forge-1.20.1-3.2.2-hotfix-2.jar%23421!/assets/mtr/website,STOPPED}
[22Jul2024 00:16:38.460] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Stopping server
[22Jul2024 00:16:38.461] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Saving players
[22Jul2024 00:16:38.461] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Saving worlds
[22Jul2024 00:16:38.572] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Saving chunks for level 'ServerLevel[New World]'/minecraft:overworld
[22Jul2024 00:16:38.665] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_end
[22Jul2024 00:16:38.666] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Saving chunks for level 'ServerLevel[New World]'/deeperdarker:otherside
[22Jul2024 00:16:38.667] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_nether
[22Jul2024 00:16:38.807] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: ThreadedAnvilChunkStorage (COBBLEMON ADVANCE): All chunks are saved
[22Jul2024 00:16:38.807] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: ThreadedAnvilChunkStorage (DIM1): All chunks are saved
[22Jul2024 00:16:38.807] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: ThreadedAnvilChunkStorage (otherside): All chunks are saved
[22Jul2024 00:16:38.808] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: ThreadedAnvilChunkStorage (DIM-1): All chunks are saved
[22Jul2024 00:16:38.808] [Server thread/INFO] [net.minecraft.server.MinecraftServer/]: ThreadedAnvilChunkStorage: All dimensions are saved
[22Jul2024 00:16:38.875] [Server thread/INFO] [de.geheimagentnr1.auto_restart.util.ServerRestarter/]: Saving restart status "STOP" to file
[22Jul2024 00:16:38.880] [Server thread/INFO] [dev.mikeretriever.cobblemonmikeskills.CobblemonMikeSkills/]: Mike Skills writing config files. . .
[22Jul2024 00:16:38.887] [Server thread/INFO] [Framework/]: Unloading server configs...
[22Jul2024 00:16:38.888] [Server thread/INFO] [Framework/]: Sending config unload event for mighty_mail.server.toml
[22Jul2024 00:16:38.937] [Server thread/INFO] [journeymap/]: Loading JourneyMap Forge Configs
[22Jul2024 00:16:39.139] [fr.denisd3d.mc2discord.shadow.reactor-http-nio-3/INFO] [fr.denisd3d.mc2discord.shadow.discord4j.core.shard.LocalShardCoordinator/]: [G:790fca49, S:0] Shard disconnected
[22Jul2024 00:16:39.140] [fr.denisd3d.mc2discord.shadow.reactor-http-nio-3/INFO] [fr.denisd3d.mc2discord.shadow.discord4j.core.shard.GatewayBootstrap/]: [G:790fca49, S:0] All shards disconnected
[22Jul2024 00:16:56.373] [pool-15-thread-1/WARN] [com.shutdowner.Shutdowner/]: Server shut down correctly, ending
2024-07-21-1.log
Mod Loader
Forge
Minecraft Version
1.20.1
Minecraft Transit Railway Version
3.2.2
Operating System
Windows 11
List of Mods or Modpack You Were Using

Extra Information
No response

Yeah, having the same issue too. The rails, elevator tracks are all missing even after saving with /save-all on terminal/shell

Same issue,  A mod from the discord said it could be an issue with your hosting provider blocking the servers access to files,  I have later debunked this as the trains will not save in single player either.   It has to be a mod confliction or this version of forge is not working correctly>  I hope this info can help you solve this reoccurring issue.

EVERYONE I FOUND THE ISSUE, you need to download the MTR file from their website NOT THE ONE LISTED ON CURSEFORGE, After this, i can reset my server and the rails stay on the server

What do we have to download? Because it still shows curse forge and modrith

Because the 4.0. version save. the rails completely. but not the 3.2.2

this is the version https://modrinth.com/mod/minecraft-transit-railway/version/FORGE-4.0.0-beta-8+1.20.1

yes the 4.0 works on hosted servers

I think I'm gonna wait for beta 9 There is a extreme bad issue with. RAM and CPU usage going up.


Remove version: ChilliBits.Spice version 0.7.5

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/spicelang/spice/releases/download/0.7.5/spice_x64_setup.msi
Status Code: 200
(Automated message - build 857)


Removal of 2 ExpressionStmt's associated to same parent fails when using LexicalPreserving CompilationUnit

Hey Guys, I have found your Project some days ago and appreciate it very much, thanks for that!
After using it and playing around with it for several days now, I have following issue:
For testing purposes I have declared following Java test class (to prove correct type resolution):
`
import org.slf4j.LoggerFactory;
import xxx.Logger;
import xxx.MessageLogger;

public class ComplexClass {

private static final Logger logger = MessageLogger.instance();
private static final org.slf4j.Logger LOGGER = LoggerFactory.getLogger(ComplexClass.class);

public void print(final Object pObject) {
    if (pObject instanceof String) {
        print((String) pObject);
    } else if (pObject instanceof Exception) {
        print((Exception) pObject);
    }
}

public void print(final Exception pExceptionToLog) {
    logger.error(pExceptionToLog); // Correctly resolved for removal
    org.slf4j.Logger logger = LOGGER;
    logger.error("Error!", pExceptionToLog);
    ComplexClass.logger.error("Blah"); // Correctly resolved for removal
    logger.error("Blah");
}`

And following Code to resolve the changes:
`
private void viaMethodCalls2(final CompilationUnit pCompilationUnit, final TypeSolver pTypeSolver) {
        if (trustImportStatements && !doImportsContainTargetType(pCompilationUnit, targetType)) { // targetType -> Saved as field and in this case xxx.Logger.class
            return;
        }

        final Set<FieldDeclaration> matchingFieldDeclarations = resolveFieldDeclarations(pCompilationUnit, targetType);

        final List<MethodDeclaration> methodsToProcess = Navigator.findAllNodesOfGivenClass(pCompilationUnit, MethodDeclaration.class);
        methodsToProcess.forEach(m -> {
            // Process every method in class from bottom to up
            final List<Node> nodesToRemove = Lists.reverse(m.findFirst(BlockStmt.class).get().getChildNodes()).stream()
                    .filter(child -> process(child, matchingFieldDeclarations, targetType, pTypeSolver)).collect(Collectors.toList());

            for (Node node : nodesToRemove) {
                node.remove();
            }
        });
        matchingFieldDeclarations.forEach(FieldDeclaration::remove);
        removeImport(pCompilationUnit, targetType);
    }`

The code is able to detect the correct lines of Code which should be removed (amazing!) and thus should be able to remove it. Unluckily it Fails to remove the second node! This is because after the removal of the first node the parent node for both nodes is nulled. And this is why the Node::remove method is not able to succeed on the second node.
After Debugging a little bit I noticed it is because of the "PropagatingAstObserver" - observer added by Setting up the parsed compilation unit with the LexicalPreservingPrinter.
Technically the error occurs on:
'LexicalPreservingPrinter.concreteListChange(line:192) -> LexicalDifferenceCalculator.calculateListRemovalDifference(line:93) -> LexicalDifferenceCalculator.calculatedSyntaxModelAfterListRemoval(line:290) -> LexicalDifferenceCalculator.calculatedSyntaxModelForNode(line:161) -> ListRemovalChange.getValue(line:28)'

After "addAll" is called the parentNode for both "nodesToRemove" is nulled and this is the Point after which any other removal of nodes will (probably) fail - at least in my scenario. Unluckily the Code is quite complex at this Point and hiding a lot of Information so I cannot go deeper into it nor suggest any other solution.
The Code for Setting up the compilation unit Looks like this:
'public static Pair<File, CompilationUnit> createPreservingCompilationUnit(final File pFromFile, final TypeSolver pTypeSolver) throws FileNotFoundException {
    JavaSymbolSolver symbolResolver = new JavaSymbolSolver(pTypeSolver);
    JavaParser.getStaticConfiguration().setSymbolResolver(symbolResolver);
    return new Pair<>(pFromFile, LexicalPreservingPrinter.setup(JavaParser.parse(pFromFile)));
}'

Hope you guys still work on it and that this helps you when having a look on it (and to fix? this). Thanks!

This also happens when adding new elements to a parsed node with following Code:

`
public void notWorking(final List<ExpressionStmt> pExpressionsToProcess) {
    for (final ExpressionStmt n : pExpressionsToProcess) {
        Optional<BlockStmt> parent = n.findParent(BlockStmt.class);
        parent.ifPresent(surroundingBlock -> {
            Optional<MethodCallExpr> firstContainedMethodCall = n.findFirst(MethodCallExpr.class);
            if (firstContainedMethodCall.isPresent()) {
                final MethodCallExpr methodCallExpr = new MethodCallExpr();
                methodCallExpr.setName(firstContainedMethodCall.get().getName());
                methodCallExpr.setArguments(firstContainedMethodCall.get().getArguments());
                surroundingBlock.addStatement(methodCallExpr);
            }
        });
    }
}

`
The above Code only adds one element (by passing a list with size of 2 as an argument). The following Workaround Code (correctly) adds 2 Elements - as desired/ expected:

`
public void working(final List<ExpressionStmt> pNodesToProcess) {
    // Workaround to add multiple children from same node in LexicalPreserving printer => Save former parent
    Optional<BlockStmt> parent = Optional.empty();
    for (final ExpressionStmt n : pNodesToProcess) {
        parent = parent.isPresent() ? parent : n.findParent(BlockStmt.class);
        parent.ifPresent(surroundingBlock -> {
            Optional<MethodCallExpr> firstContainedMethodCall = n.findFirst(MethodCallExpr.class);
            if (firstContainedMethodCall.isPresent()) {
                final MethodCallExpr methodCallExpr = new MethodCallExpr();
                methodCallExpr.setName(firstContainedMethodCall.get().getName());
                methodCallExpr.setArguments(firstContainedMethodCall.get().getArguments());
                surroundingBlock.addStatement(methodCallExpr);
            }
        });
    }
}

`

This bug is something we should fix in JavaParser, not JavaSymbolSolver but this issue is fine. Thanks for reporting this one, I will keep you posted as soon as I find the time to work on this one

Oh yeah of Course this has actually nothing to do with solving the Symbols. Thank you for having a look on it anyways!

Moved to the right project


Added 4.7.2 to list of .NET Framework versions

Added 4.7.2 to list of .NET Framework versions
Fixes #6471

Still do NOT see 4.7.2 in paragraph titled "Targeting and Running .NET Framework apps for version 4.5 and later"

It is on https://github.com/dotnet/docs/blob/master/docs/framework/migration-guide/versions-and-dependencies.md. It won't appear on docs.microsoft.com until we merge master to live, which provisionally is scheduled to happen sometime tomorrow morning, @jbruns2015.