optimize client-springmvc registration time

optimize client-springmvc registration time
It could be an example！
When registering, the project may not start successfully, but it just collides with polling, resulting in invalid registration
Please see the detailed description of the

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #1114 (d838e6c) into master (938b83b) will decrease coverage by 0.25%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #1114      +/-   ##
============================================
- Coverage     74.44%   74.18%   -0.26%
+ Complexity     2179     2173       -6
============================================
  Files           365      365
  Lines          8202     8202
  Branches        906      906
============================================
- Hits           6106     6085      -21
- Misses         1642     1656      +14
- Partials        454      461       +7

Impacted Files
Coverage Δ
Complexity Δ

...client/springmvc/init/ContextRegisterListener.java
89.65% <ø> (ø)
5.00 <0.00> (ø)

...soul/plugin/sofa/cache/ApplicationConfigCache.java
58.66% <0.00%> (ø)
11.00 <0.00> (ø)

...omara/soul/plugin/sofa/proxy/SofaProxyService.java
48.27% <0.00%> (ø)
4.00 <0.00> (ø)

...soul/client/tars/TarsServiceBeanPostProcessor.java
26.02% <0.00%> (-20.55%)
6.00% <0.00%> (-4.00%)

...plugin/tars/subscriber/TarsMetaDataSubscriber.java
77.27% <0.00%> (-9.10%)
7.00% <0.00%> (-1.00%)

.../soul/plugin/httpclient/NettyHttpClientPlugin.java
57.14% <0.00%> (-2.05%)
10.00% <0.00%> (ø%)

...omara/soul/sync/data/http/HttpSyncDataService.java
70.58% <0.00%> (-1.97%)
12.00% <0.00%> (ø%)

.../soul/admin/service/impl/UpstreamCheckService.java
75.38% <0.00%> (-1.54%)
14.00% <0.00%> (-1.00%)

...elimiter/handler/RateLimiterPluginDataHandler.java
74.13% <0.00%> (ø)
12.00% <0.00%> (ø%)

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 29278b1...d838e6c. Read the comment docs.

no， we also support springmvc， not only springboot


Create Enabled Flag

what

Add enabled flag

why

For the terraform-aws-kops-state-backend we need to be able to disable the zone creation for kops gossip clusters which do not rely on DNS zones

addressed in https://github.com/cloudposse/terraform-aws-route53-cluster-zone/pull/10


fix: cannot backup wallet on mobile app after disconnecting

Description
By diving into the random password mobile prompt issue, I noticed that if we deconnect from the current wallet, then select another one, the modalType is not set to mobile anymore, meaning that there are modalType set, so the BackupPassphrase modal is empty when you try to open it
It might be the root cause of #6704 too but I couldn't find a way to properly test it and I didn't reproduce it at all

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

n/a
Risk
Risk might be high if a user could not load a wallet from his mobile app
Testing
⚠ Absolutely use the mobile app while testing this!
Disconnect then select another wallet (or the same)
Click the disconnect button in the menu, select another wallet or the same, try to click on "Back up my passphrase" in the menu, it should display the right words
Disconnect then create a new wallet
Disconnect then create a new wallet then try to click "Back up my passphrase" in the menu, verify that the words are the right one
Disconnect then import a new wallet
Disconnect then import a new wallet then try to click "Back up my passphrase" in the menu, verify that the words are the right one

Engineering
n/a

Operations
n/a

Screenshots (if applicable)
Before: Disconnect then reconnect
https://jam.dev/c/1b1e840a-2f52-4e69-a06b-a12e29e546b3
After: Disconnect then reconnect
https://jam.dev/c/e6fbfb32-9cfb-4999-aa63-389023d832d1

Video of 3x auth issue:
https://github.com/shapeshift/web/assets/125113430/75433fd0-37d8-49f9-b89e-d561d306d0cf

The fix itself works, but on android this branch requires authentication 3 times to unlock the mobile wallet, compared to production which only needs 1 authentication to unlock.
Note the black screens are the fingerprint reader auto-redacted from the recording - the 3 black screens in a row are the 3 fingerprint auths.
screen-20240702-102733.3.mp4

Confirmed I was able to repro this on iOS


[TTS] Failed to convert onnx to TensorRT

For support and discussions, please use our Discourse forums.
If you've found a bug then please create an issue with the following information:
Describe the bug
failed to convert the onnx file generated by paddle2onnx to tensorRT model
To Reproduce

generator the files that paddle2onnx needed.

cd examples/csmsc/tts3/
source path.sh
FLAGS_allocator_strategy=naive_best_fit
FLAGS_fraction_of_gpu_memory_to_use=0.01
python3 ${BIN_DIR}/../synthesize_e2e.py --am=fastspeech2_csmsc --am_config=fastspeech2_cnndecoder_csmsc_ckpt_1.0.0/cnndecoder.yaml --am_ckpt=fastspeech2_cnndecoder_csmsc_ckpt_1.0.0/snapshot_iter_153000.pdz --am_stat=fastspeech2_cnndecoder_csmsc_ckpt_1.0.0/speech_stats.npy --phones_dict=fastspeech2_cnndecoder_csmsc_ckpt_1.0.0/phone_id_map.txt --voc=hifigan_csmsc --voc_config=hifigan_csmsc_ckpt_0.1.1/default.yaml --voc_ckpt=hifigan_csmsc_ckpt_0.1.1/snapshot_iter_2500000.pdz --voc_stat=hifigan_csmsc_ckpt_0.1.1/feats_stats.npy --lang=zh --text=${BIN_DIR}/../sentences.txt --output_dir=exp/default/test_e2e --ngpu=0 --inference_dir=infer

./local/paddle2onnx.sh . infer onnx fastspeech2_csmsc
push the onnx file to NGC  nvcr.io/nvidia/tensorrt:22.08-py3
run trtexec --onnx=fastspeech2_csmsc.onnx --saveEngine=fastspeech2_csmsc.trt --best --fp16

Expected behavior
no error in trtexec log
Screenshots
[11/02/2022-06:15:54] [W] [TRT] parsers/onnx/onnx2trt_utils.cpp:367: Your ONNX model has been generated with INT64 weights, while TensorRT does not natively support INT64. Attempting to cast down to INT32.
[11/02/2022-06:15:56] [E] Error[9]: [graph.cpp::computeInputExecutionUses::553] Error Code 9: Internal Error (p2o.Conv.16: IConvolutionLayer cannot be used to compute a shape tensor)
[11/02/2022-06:15:56] [E] [TRT] parsers/onnx/ModelImporter.cpp:773: While parsing node number 730 [ConstantOfShape -> "p2o.ConstantOfShape.3"]:
[11/02/2022-06:15:56] [E] [TRT] parsers/onnx/ModelImporter.cpp:774: --- Begin node ---
[11/02/2022-06:15:56] [E] [TRT] parsers/onnx/ModelImporter.cpp:775: input: "p2o.auto.cast.87"
output: "p2o.ConstantOfShape.3"
name: "p2o.ConstantOfShape.2"
op_type: "ConstantOfShape"
attribute {
name: "value"
t {
dims: 1
data_type: 1
name: "fill_constant_111.tmp_0"
raw_data: "\000\000\000\000"
}
type: TENSOR
}
[11/02/2022-06:15:56] [E] [TRT] parsers/onnx/ModelImporter.cpp:776: --- End node ---
[11/02/2022-06:15:56] [E] [TRT] parsers/onnx/ModelImporter.cpp:778: ERROR: parsers/onnx/ModelImporter.cpp:180 In function parseGraph:
[6] Invalid Node - p2o.ConstantOfShape.2
[graph.cpp::computeInputExecutionUses::553] Error Code 9: Internal Error (p2o.Conv.16: IConvolutionLayer cannot be used to compute a shape tensor)
[11/02/2022-06:15:56] [E] Failed to parse onnx file
[11/02/2022-06:15:56] [I] Finish parsing network model
[11/02/2022-06:15:56] [E] Parsing model failed
[11/02/2022-06:15:56] [E] Failed to create engine from model or file.
[11/02/2022-06:15:56] [E] Engine set up failed
&&&& FAILED TensorRT.trtexec [TensorRT v8402] # trtexec --onnx=fastspeech2_csmsc.onnx --saveEngine=fastspeech2_csmsc.trt --best --fp16
Environment (please complete the following information):

OS: Ubuntu
GCC/G++ Version [e.g. 8.3]
Python Version 3.8
PaddlePaddle Version  2.3.1
Model Version [e.g. 2.0.0]
GPU/DRIVER Informationo A100
CUDA/CUDNN Version 11.7
MKL Version
TensorRT Version 8.4.2-1+cuda11.6

Additional context
Add any other context about the problem here.

the related function is expand in paddlespeech/t2s/modules/predictor/length_regulator.py

sorry, We haven't tried to covert onnx to trt, but both onnxruntime and PaddleInference have tensorrt backend, you can try to use


Start exploring and elaborating the full breadth of GenAI use cases

Our current governance framework is based on a single use-case, the creation of a RAG-based chatbot. In order to meet the overall goals of this group, we need to create a framework that is able to accomodate a broad range of use cases.
As a group, we need to start considering the full breadth of GenAI use cases, ideally we would create a simple framework for characterising these use cases (e.g. client-facing, internal facing, cloud-based, self-hosted model), which would allow us to more easily navigate them.

Examples of AI uses in banks include:

fraud detection and prevention,
marketing,
chatbots,
credit underwriting,
credit and fair lending
risk management,
robo-advising (i.e., an automated digital investment advisory service),
trading algorithms and automation,
financial marketing analysis,
cybersecurity,
Bank Secrecy Act/anti-money laundering (BSA/AML), suspicious activity monitoring, customer due diligence,
robotic process automation,
audit and independent risk management

Source https://www.occ.treas.gov/publications-and-resources/publications/comptrollers-handbook/files/model-risk-management/pub-ch-model-risk.pdf Page 7

Luca to create a poll and share with the group

Here the poll https://github.com/finos/ai-readiness/discussions/25
Inspired by this: rsch_pdf_30255539 (1) (2).pdf

To provide a structured scoring system for evaluating GenAI use cases based on ease of implementation, impact, cost, risk, and probable development needs, here’s a proposed approach:

Criteria Definition:
Each use case will be scored based on the following criteria, with scores on a scale of 1 to 5 (where 1 is the easiest or lowest and 5 is the most difficult or highest).

Ease of Implementation: How easy it is to implement the use case based on technical requirements, integration, and resource availability.
1: Very easy (existing tools, plug-and-play)
5: Very difficult (high customization, complex integration)
Level of Impact if Goes Wrong: The level of disruption or harm if the use case fails or performs poorly.
1: Minimal impact (low business disruption, easily reversible)
5: Severe impact (major financial, legal, or reputational damage)
Cost of Impact: The monetary cost if something goes wrong with the AI model in production.
1: Low (minor losses, easily correctable)
5: High (substantial losses, legal penalties, or regulatory fines)
Risk Factor: The inherent risk posed by the use case in terms of data security, privacy, regulatory concerns, etc.
1: Low risk (little regulatory oversight, low data sensitivity)
5: High risk (high regulatory scrutiny, sensitive data involved)


Add support for arrays of more types

This is currently targeting a branch with https://github.com/realm/realm-cocoa/pull/5267 and latest master merged into master-3.0 for the sake of showing something sensible for review.
All functionality of RLMArray and List should now be supported for all of the Realm-supported data types, except for queries. Currently trying to query primitive lists just silently ignores the predicate passed in. See RLMTestObjects.h for examples of how the models are declared in obj-c (as with RLMObject arrays, generic type parameters can be used but are insufficient). In Swift the expected normal things work (e.g. List<Int?> etc.).
The bulk of the obj-c changes are adjusting how validation is done. Notably unbox() no longer validates its input and instead we validate all values before passing them to the object store. This is needed both for providing sensible error messages without threading even more awful state tracking into RLMAccessorContext, and to avoid duplicating all of the logic for unmanaged objects. The other obj-c changes are just adding support in the KVC and aggregate functions.
Swift changes were simpler; all that was left to do was make more types conform to RealmCollectionValue and make realm collections conditionally define aggregate functions for Lists and Results of aggregatable types.
The tests are unfortunately something of a mess. For obj-c I had the idea of generating tests on each array type from a template using a simple python script. This did not turn out as well as I hoped, and unsurprisingly the python script turned into a terrible pile of hacks and the template file is awful. For Swift I attempted to take the same approach as the C++ objectstore tests, but ran into a lot of issues with the current limitations of Swift generics (most notably the lack of conditional conformances). Both of these probably need to be rethought, but I think that can wait; the tests do at least serve to test the code for now.

Nothing stands out to me as being problematic, it looks good. I'll review it again tomorrow more carefully.

There's a linker error which suggests we'll need a core release including the fix from realm/realm-core#2823:
Undefined symbols for architecture i386:
  "unsigned long realm::Table::find_first<realm::BinaryData>(unsigned long, realm::BinaryData) const", referenced from:
      unsigned long realm::List::find<realm::BinaryData>(realm::BinaryData const&) const in libRealm.a(list.o)
      unsigned long realm::Results::index_of<realm::BinaryData>(realm::BinaryData const&) in libRealm.a(results.o)
ld: symbol(s) not found for architecture i386

One problem the tests reveal with Xcode 9 / Swift 4 is:
Simultaneous accesses to 0x6040000de518, but modification requires exclusive access.
Previous access (a modification) started at RealmSwift Tests`implicit closure #1 in PrimitiveListTests.testReplaceRange() + 209 (0x120c8fa21).
Current access (a read) started at:
0    libswiftCore.dylib                 0x00000001219418e0 swift_beginAccess + 605
1    RealmSwift Tests                   0x0000000120c77a40 PrimitiveListTestsBase.array.getter + 68
2    RealmSwift Tests                   0x0000000120c8e0c0 PrimitiveListTests.testReplaceRange() + 1114
3    RealmSwift Tests                   0x0000000120c8ff20 @objc PrimitiveListTests.testReplaceRange() + 36

This error occurs during the evaluation of:
array.replaceSubrange(0..<0, with: [values[0]])

I think Swift's new exclusive access checking isn't safe against Objective-C / C++ exceptions being thrown, so the earlier:
assertThrows(array.replaceSubrange(0..<1, with: []),
             reason: "Index 0 is out of bounds")

leaves the access checking state in an inconsistent state?

All of the remaining CI failures are due to flakiness.

The work remaining here appears to be:

[ ] Change log entry
[ ] Another review pass from all involved to determine if there's any other remaining work

The failing Swift test has already been fixed on master-3.0.

Obj-C and Swift tests now pass for me locally on both macOS and on my phone, so I think any remaining failures are just CI flakiness.


Fix URLs for docs-hosted repo files for 1.13 in archive

Hosting the .repo files was weird for us, and a quick fix. Now that v1.13 is in the archives, we need those links to point to the archived .repo files instead. This PR does that.
cc/ @fxdgear
@johndmulhausen we will need to rebuild / re-push docs-base for this one.

The follow-up commit fixes some Jekyll build warnings.

@aduermael pinging you in case you're curious about troubleshooting the build. I'm not going to hold up merging it.


fix: typo

Changes
Update async-rust.md
Replace syncrhonous -> synchronous
Checklist

[ ] An issue to be fixed by this PR is listed above.
[ ] New tests are added to ensure new features are working. Please refer to this page to see how to add a test.
[ ] ./frb_internal precommit --mode slow (or fast) is run (it internal runs code generator, does auto formatting, etc).
[ ] If this PR adds/changes features, documentations (in the ./website folder) are updated.
[ ] CI is passing. Please refer to this page to see how to solve a failed CI.

Remark for PR creator

./frb_internal --help shows utilities for development.
If fzyzcjy does not reply for a few days, maybe he just did not see it, so please ping him.

Nice catch!

@all-contributors please add @damywise for doc


Fix for crit bug when closing pipe stream

When we use pipe method of BinaryStream and close connected browser page - server got crit error:
TypeError: Cannot call method '_onClose' of undefined
  at WebSocket.<anonymous> (/srv/http/socialstream/server/node_modules/binaryjs/lib/client.js:59:28)
  at WebSocket.EventEmitter.emit (events.js:117:20)
  at WebSocket.cleanupWebsocketResources (/srv/http/socialstream/server/node_modules/binaryjs/node_modules/streamws/lib/WebSocket.js:619:23)
  at Socket.EventEmitter.emit (events.js:117:20)
  at _stream_readable.js:920:16
  at process._tickCallback (node.js:415:13)

It is fast fix for this. It easy to found reason by following callstack - when stream is closed it automatically close his pipe destination stream and removed it from self.streams array.

I'm seeing this as well, only happens when i send a stream created using client.createStream().
I think this bug might be a race condition where the stream reference is lost
https://github.com/binaryjs/binaryjs/blob/58af5aa53d3d574bdb4c0930d44fa022381ea285/lib/client.js#L241


Sqlite functionality and EN std level check working with db

Here is my attempt to get the EN std level check working with the new database structure. Tests pass and results on the quota_subset.dat dataset appear to be identical to before.
I was struggling to get the postgres to work outside the docker container so I've added in a fallback to use an sqlite database if postgres is not available. Hope this is OK. It seems to work with almost the same commands as postgres. Main difference is that it is necessary to store qc results as integers as booleans can't be stored, but I thought that would be OK.
I think I messed up when I started work on this as I seem to have got all the recent commits to the master branch mixed up with this one - sorry about that!

Thanks for this, @s-good! I'm a bit nervous about using sqlite for autoqc though, since it has concurrency difficulties that postgres avoids, which is why I chose postgres; see http://sqlite.org/faq.html#q5 for example. The level of parallelization we need in order for these calculations to not take weeks means that concurrent db access is a key priority.
Could I help either (a) getting postgres working on your machine or (b) getting running inside the docker container working for you? That helps us avoid a lot of complicated cases as well. In either case, I think the changes you made to the level check should be mergable on their own; I have most of Tuesday set aside to work on this, so I'll do some git surgery to pull those changes in then.

Hi @BillMills, I think that the postgres will work fine at home running in docker but if I'm running it at work I can't use docker and I'm going to struggle a lot with postgres because of having to set up a server. It sounds like sqlite is ok as long as using an ext4 file system and not too many threads so I'd like to include it to enable me to try to test running at work. NB I realised that what I have set up with the try: import psycopg2 will not work and there will need to be a command line argument instead.

@s-good okay, we can make sqlite work - but actually, I would rather just drop postgres and use one single database solution to avoid unnecessary complexity in that case. What do you think? If this is acceptable, let me know and I will make all the necessary changes immediately.

Having been playing with it a bit today I'm not sure if it is wise to put all our eggs in sqlite basket. I seem to be getting different behaviour from it depending on where I run it which makes me very nervous and it sounds like postgres would be better in general. I can make local modifications if necessary when running at work if you want to remove the sqlite parts. It is straightforward to do as commands are almost identical. I can run using docker when running it elsewhere and then there is no issue with postgres.

@s-good okay, let's do that - I will try and turn this around by the end of Wednesday, giving us a couple more days to validate at scale this week; if nothing goes wrong there, we can move onto large scale running by the weekend or first thing next week.

I'm going to close this as I have pulled the key changes for the standard level check into postgres, in a postgres-only scheme. @s-good, I went back to using bools for test results, but we don't have to; we can use 0 for fail / no problems and >0 for flags if that's convenient (also makes it easier in future to have different flavors of flags).


gcc build and tar cfv gcc-10.1.0.tar gcc-10.1.0 crashes WSL2 - just build and compression of directory?

Environment
Windows build number: Microsoft Windows [Version 10.0.19041.329]
Your Distribution version: Release:        20.04 Ubuntu
Whether the issue is on WSL 2 and/or WSL 1: Linux version 4.19.104-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Feb 19 06:37:35 UTC 2020 WSL2

Steps to reproduce
I can not build gcc and pack gcc build directory.
10GB of RAM, SWAP = 0GB

Unpack gcc-10.1.0 to /dptr/root/src
download dependencies /dptr/root/src/gcc-10.1.0# ./contrib/download_prerequisites
/dptr/root/src/gcc-10.1.0/configure" --prefix="/dptr/root/import" --disable-multilib
make it (should crash) /dptr/root/build/gcc-10.1.0# make -j 2

try /dptr/root/build/# tar cfv gcc-10.1.0.tar gcc-10.1.0

Expected behavior
gcc 10.1.0 build should success, tar should compress.

Actual behavior
gcc 10.1.0 build crash (no problem with memory)
tar crash on gcc build
I think it is problem with files/file system created by gcc build but I do not know why?

Some logs from gcc build crash.
logs.zip
I compile gcc 10.1.0 from source with options as above. Nothing special is done or extra flags.
This compilation works fine on CentOS 7 (real one not wsl).

Here is content of gcc build directory - maybe some name cause problem of too long path - I do not know. I can not tar cvf on this directory but tree works.
tree.txt

WSL2 uses a vhdx with ext4 as filesystem so it should behave exactly like in a real Linux.
What's the error you are seeing? Does dmesg show anything when that happens?
What is /dptr/root? Does the user have permission to write there? Did you try compiling in /home/username?
How much free space do you have in C:? The vhdx file expands while compiling so make sure you have enough disk space.

What it the nature of the "crash". Maybe a screencap, or at least a description. Start WSL with wsl.exe (or wsl.exe -d`) from a cmd prompt rather than the distro start menu item. Does do you get kicked out of WSL and back to the prompt, or...?
Like Ono says WSL2 is Real Linux and gcc 10 certainly builds. That doesn't help you of course. Hopefully you will get some me2s.

10GB of RAM, SWAP = 0GB

Evens this is #5410. Open up Resource Monitor during the run and see if you are hitting the wall. A big tar cvf is not materially different than a big dd as far as the kernel is concerned. In addition to giving yourself some Linux swap, try limiting your WSL memory with .wslconfig. You can also try upping your Windows pagefile manually.


I would like to generate an .apk file, to do that I need to have the SHA1 key that eas build are using to generate the .aab file

Build/Submit details page URL
Summary
I'm running into a problem when I submit the .aab file generated using eas build -p android into Play Store.
I realized that the problem is when the .aab file is converted into a .apk file.
I would like to generate a .apk file to test it and understand what is going on.
To generate a .apk file with the .aab file generated by eas build, I need to run this command:
bundletool build-apks --bundle=./android/app/build/outputs/bundle/release/app-release.aab --output=~/Downloads/app.apks --mode=universal --ks=./android/app/production-android.keystore --ks-key-alias=production-android --ks-pass=pass:pass; mv ~/Downloads/app.apks ~/Downloads/app.zip;
But if I generate a new SHA1 key will be different from the expo.
I need to understand how transform this .aab into a .apk file.
Managed or bare?
Bare
Environment
 expo-env-info 1.0.5
environment info:
    System:
      OS: macOS 12.5.1
      Shell: 5.8.1 - /bin/zsh
    Binaries:
      Node: 14.20.1 - ~/.nvm/versions/node/v14.20.1/bin/node
      Yarn: 1.22.19 - ~/.nvm/versions/node/v14.20.1/bin/yarn
      npm: 6.14.17 - ~/.nvm/versions/node/v14.20.1/bin/npm
      Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
    Managers:
      CocoaPods: 1.11.3 - /usr/local/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
      Android SDK:
        API Levels: 30, 31, 33
        Build Tools: 29.0.2, 30.0.3, 31.0.0, 33.0.0
        System Images: android-27 | Google APIs ARM 64 v8a, android-28 | Google APIs ARM 64 v8a, android-28 | Google ARM64-V8a Play ARM 64 v8a, android-29 | Google APIs ARM 64 v8a, android-33 | Google APIs ARM 64 v8a
    IDEs:
      Android Studio: 2021.3 AI-213.7172.25.2113.9123335
      Xcode: 14.0.1/14A400 - /usr/bin/xcodebuild
    npmPackages:
      expo: ~46.0.17 => 46.0.17
      react: 18.0.0 => 18.0.0
      react-dom: 18.0.0 => 18.0.0
      react-native: 0.69.6 => 0.69.6
      react-native-web: ~0.18.7 => 0.18.9
    npmGlobalPackages:
      eas-cli: 2.7.1
      expo-cli: 6.0.6
    Expo Workflow: bare

eas.json file
{
  "cli": {
    "version": ">= 2.7.1"
  },
  "build": {
    "development": {
      "distribution": "internal",
      "android": {
        "gradleCommand": ":app:assembleDebug"
      },
      "ios": {
        "buildConfiguration": "Debug"
      }
    },
    "preview": {
      "distribution": "internal",
      "channel": "preview"
    },
    "production": {
      "channel": "production"
    }
  },
  "submit": {
    "production": {}
  }
}

Error output
When Play Store convert the .aab file into a .apk file, I can't communicate my app with the AWS API.
But this problem only happens with Android, into App Store my app works fine.
Reproducible demo or steps to reproduce from a blank project
Have a project with Expo Bare Workflow and AWS, generate a .aab file and put it on Play Store.
If I install my app from Android Studio with the build variants Release, everything works fine, the problem only happens when the .aab file is turned into .apk file.
When I'm generating the .aab file, I'm not specifying which environment I want, which in this case would be production, I don't know if that would have to do with the problem.

It's not clear from your post what is not working. In one place you are saying that you can't submit app to play store and in another that the app can't communicate with api that verifies cert fingerprint that was used to sign your app. So which is it?
When you upload app to the Play store it's signed with one certificate, but the app that is visible to users it's signed with a different one, so the fingerprints of those apps will be different if you install it via play store or from apk. You can check both fingerprints in the play console.
If you are creating apk from aab you are signing it again with new certificate, if you want it to have the same fingerprint as aab you need to use the same keystore that was used during the build. You can download it from the website https://expo.dev/accounts/ildaneta/projects/Picblink/credentials or using eas credentials command
I see you have 2 keystores, if you have a problem with submitting app to the store it might be because you are using a wrong key. (legacy one is what was used in expo-cli)

@wkozyra95 thank you for answering me.
I'll try it. 🙂


aligned deivceSecurityGroups to stable

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Hi @liranc you are trying to introduce breaking change for preview api over 1 year. Please follow breaking change policy https://dev.azure.com/msazure/AzureWiki/_wiki/wikis/AzureWiki.wiki/43942/Policy-for-Breaking-Changes

Hi @liranc you are trying to introduce breaking change for preview api over 1 year. Please follow breaking change policy https://dev.azure.com/msazure/AzureWiki/_wiki/wikis/AzureWiki.wiki/43942/Policy-for-Breaking-Changes

@NullMDR we actually had the same discussion in this PR: https://github.com/Azure/azure-rest-api-specs/pull/8820 🙂 (the changes in this PR as the same).
The latest version of the swagger results in an error when attempt to generate code using AutoRest.
The issue is that the ruleType field was defined both in CustomAlertRule (the base type) and AllowlistCustomAlertRule (deriving type). Also, it wasn't marked as a discriminator even though it behaved like one.
So the changes in the PR remove the duplicate definition of the property and declare it as a discriminator.


Use a do-block syntax instead

I think doing a do-block syntax seems to be more sensible this way, any thoughts?

I think doing a do-block syntax seems to be more sensible this way, any thoughts?

One question: what is a do-block? 😅


Enable Fullscreen

I'm currently working on full screen feature, here's the demo:
http://duaraghav8.github.io/AlgorithmVisualizer
(notice the Fullscreen button next to Share button on nav bar)
The feature will work with browsers which support the Fullscreen API (I've added vendor IDs for chrome, firefox, opera, IE)
(https://github.com/duaraghav8/AlgorithmVisualizer/blob/gh-pages/js/dom/enable_fullscreen.js)
The issue is: when I change to full screen, a lot of the App's UI distorts (notice the loading bar, side menu).
CSS needs to be written to handle elements in full screen, but I'm not that good with it. I've written the JS part. I'm currently looking into:
https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API
https://www.sitepoint.com/html5-full-screen-api/
https://developer.mozilla.org/en-US/docs/Web/CSS/:fullscreen
but if anyone is willing to take up the CSS part (or help me write it), please let me know, would appreciate it:)

Great idea.
Can you create fullscreen branch in this repo and pull this?
I will look into it.


cannot find module '../gekko/config-backtester.js'

Hi @gekkowarez ,
Trying to run the bruteforce.js, I'm running into this error.
Thanks in advance!

This means that the config file doesn't exist. You need to edit the bruteforce.js file to point at the correct gecko config file, for me that's ../config-backtesting.js


May I change options on the fly?

I do something like this:
const cleave = new Cleave('.my-selector', {
  numericOnly: true,
  blocks: [3, 2, 3]
});

Then I need change blocks option for this element, for example (pseudo code):
cleave.setOptions({
  blocks: [4, 4]
});

How can I do this? Right now I need destroy cleave and create it again.
let cleave = new Cleave('.my-selector', {
  numericOnly: true,
  blocks: [3, 2, 3]
});
cleave.destroy();
cleave = new Cleave('.my-selector', {
  numericOnly: true,
  blocks: [4, 4]
});

Or am I do something wrong?

Hi @iserdmi
Unfortunately the lib doesn't provide any setOptions api on the fly, you are absolutely doing it correctly.
Destroy it first and create a new one is the right way.
Thanks


Using the dag implementation in pfs internal api server

Overview:
The big change is the addition of src/pkg/dag which implements some computations on directed acyclic graphs. This package is used by src/pfs/driver to implement pfs's version control semantics. Over time I expect src/pkg/dag to get more featureful and pfs will be able to lean on it harder. We'll also use it in pps to implement pipelines.
This pr also adds src/pfs/server/server_test.go which implements local pfs server tests. Being able to test the pfs layer locally should help us a lot. Their coverage isn't great right now but you gotta start somewhere.


Feature/standard documented endpoints

Full swagger documentation for workOrder and user endpoints. Fixed some bugs in the workOrder model. Standardized the workOrder endpoints. Once merged, documentation will appear at https://xcel-wom-api-b.herokuapp.com/api-docs/
On local machine, use: http://<IP_ADDRESS>/api-docs

 As IT, I would like standardized and documented API endpoints

 As IT, I would like standardized and documented API endpoints

 As IT, I would like standardized and documented API endpoints

 As IT, I would like standardized and documented API endpoints


remove resource group from login

the resource group name in 18 account is Default.
since its not needed for access to k8s removing it.

Thanks @moficodes


How can I convert an OpenAI endpoint to a local VLLM endpoint?

I deployed the vllm model locally and tried to connect using the void extension, but I can't initiate a conversation. What should I do?

We need more details - can you give a few screenshots of what you tried to do?

Whether it is possible to consider adding an OpenAI-compatible API, adding something like OpenAI_base_url, and being able to use https://xxxx.com/v1.

Just like this, I am trying to connect to a local model by modifying the endpoint url and the model.

@ShikangPang let us know if it's working now!

I can use openaiCompatible option normally。


Shorts view table on mediabanken is not updating

Last update was on March 8. Shorts published after that are not shown on the table
https://metabase.bcc.media/question#eyJkYXRhc2V0X3F1ZXJ5Ijp7ImRhdGFiYXNlIjo5LCJ0eXBlIjoicXVlcnkiLCJxdWVyeSI6eyJzb3VyY2UtdGFibGUiOjQwMjMsIm9yZGVyLWJ5IjpbWyJkZXNjIixbImZpZWxkIiw3NTM5NCxudWxsXV1dfX0sImRpc3BsYXkiOiJ0YWJsZSIsInZpc3VhbGl6YXRpb25fc2V0dGluZ3MiOnt9fQ==

@andreasgangso are the shorts that you add done directly to the DB or via Directus api?

@andreasgangso are the shorts that you add done directly to the DB or via Directus api?

directus api actually so thats weird. https://github.com/BCC-Media/utils/blob/master/go/scripts/import-shorts.go#L223

This seems to be working since 29.juni. Can we have an import on all missing data from 8. mars- 29.juni


Global components not recognized when using @vue/composition-api

repo: https://github.com/Ttou/volar-issue-global-components
versions:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

define global components

show unknown

recognized when using Vue.extend

This is an issue from @vue/composition-api: https://github.com/vuejs/composition-api/issues/940
If anyone wants to submit a PR for @vue/composition-api to fix it, I'll pass it on to the team for a release for this.


Store links in sidebar

ref #210
Adds a new setting to display custom links in the sidebar:
; Show custom links on top of the sidebar
sidebar-custom-links =
    Journal 2015: /journal/?time=2015
    Income Statement 2015: /income_statement/?time=2015

The format for the links is [label]: [link]. Note that ": " can not be part of the label.
Will be rendered like this:

TODO:

[ ] Add Documentation-entries.

This seems to be something file-specific to me, so why not use custom directives for this?

This seems to be something file-specific to me, so why not use custom directives for this?

I hesitate to implement this for just this feature - it would be generally better to implement #214 (Move fava settings to source file options) and have all the settings in the beancount-file, as otherwise fava-specific settings are spread over two places, when they should be in just one.
What do you think about #214? Good idea? What format should we choose to store the settings in the beancount file?

I hesitate to implement this for just this feature - it would be generally better to implement #214

I view this feature as being mostly unrelated to #214. This is not a "setting" for me, but rather something like a more flexible query directive. So it doesn't really make sense without the context of the beancount file (just like budgets).

What do you think about #214? Good idea? What format should we choose to store the settings in the beancount file?

Probably a good idea, although not a pressing issue IMHO. I guess the custom directives are the best choice right now. Before we tackle this, we should evaluate if we really need all the settings we currently have.

I hesitate to implement this for just this feature - it would be generally better to implement #214

I view this feature as being mostly unrelated to #214. This is not a "setting" for me, but rather something like a more flexible query directive. So it > doesn't really make sense without the context of the beancount file (just like budgets).
Implemented in 9f7cfb5

What do you think about #214? Good idea? What format should we choose to store the settings in the beancount file?

Probably a good idea, although not a pressing issue IMHO. I guess the custom directives are the best choice right now. Before we tackle this, we should > evaluate if we really need all the settings we currently have.
Let's discuss this in #214. Can you post your thoughts on the various settings there?

This works for me. The custom links can be specified with
2016-04-01 custom "fava-sidebar-link" "Income 2014" "/income_statement?time=2014"

Only a help entry is missing.

Does this still work after #259? If so, can you rebase?
I guess we'll have to wait for a new beancount release that contains the custom directive before we can merge this.

Does this still work after #259? If so, can you rebase?

It works, and I rebased.

I guess we'll have to wait for a new beancount release that contains the custom directive before we can merge this.

Agreed. But I think @blais would not hesitate to release a new version with the custom directives if requested.

Tests keep failing because the custom directive is not part of the last official PyPI release of beancount.
@blais Would you consider releasing a new version to PyPI with the custom directive included?

It works, and I rebased.

I think something went wrong with the rebase, as it shows 40 commits here. But the diff is not big, so it's probably easiest to just create one new commit with all the changes:
git merge master       # add new commits since the rebase
git reset master
# then git add and git commit

Done.
https://pypi.python.org/pypi/beancount/
2.0b10
On Sun, May 1, 2016 at 8:39 AM, Dominik Aumayr<EMAIL_ADDRESS>wrote:

Tests keep failing because the custom directive is not part of the last
official PyPI release of beancount.
@blais https://github.com/blais Would you consider releasing a new
version to PyPI with the custom directive included?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/aumayr/fava/pull/269#issuecomment-216039270

@blais The files on PyPI seem to be missing, so 2.0b10 cannot be found:
https://pypi.python.org/pypi/beancount/json

PyPI is pissing me off.
Tested manually, now I can't upload to the same filename.
I baked another version b11.
Try onw.
On Mon, May 2, 2016 at 4:13 PM, Dominik Aumayr<EMAIL_ADDRESS>wrote:

@blais https://github.com/blais The files on PyPI seem to be missing,
so 2.0b10 cannot be found:
https://pypi.python.org/pypi/beancount/json
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/aumayr/fava/pull/269#issuecomment-216349382

It works now, thanks @blais!

Sorry for causing trouble!

@yagebu I, again, messed something up with git. I will add the missing documentation here, and create a new PR once I am finished.

Because the git history was messed up, this PR will be closed, and the successor can be found here:
#279


[stable/datadog] Fix trace agent and useConfigMap

Is this a new chart
No
What this PR does / why we need it:
Version 2.0.0 of the stable/datadog introduced new issues.

If agents.useConfigMap is set to to true, it causes a templating error because .Values.image no longer exists.

Error: template: datadog/templates/datadog-yaml-configmap.yaml:38:28: executing "datadog/templates/datadog-yaml-configmap.yaml" at <.Values.image.tag>: nil pointer evaluating interface {}.tag

If agents.useConfigMap is false and agents.apm.enabled is true, the Datadog trace agent container fails to startup with this error:

trace-agent not enabled. Set the environment variable DD_APM_ENABLED=true or add "apm_config.enabled: true" entry to your datadog.yaml. Exiting...

Special notes for your reviewer:
Recreating this PR from https://github.com/helm/charts/pull/21118 due to issues rebasing my branch.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/lgtm


Module/sage/1.0

Pull Request Checklists
Important: When opening a pull request, keep only the applicable checklist and delete all other sections.
Checklist for New Module
Required

[X] I used the cookiecutter template and updated the placeholder rules.

[X] The snakemake rules follow the design guidelines.

[X] All references to the rules object (e.g. for input files) are wrapped with str().

[X] Every rule in the module is either listed under localrules or has the threads and resources directives.

[X] Input and output files are being symlinked into the CFG["inputs"] and CFG["outputs"] subdirectories, respectively.

[X] I updated the final target rule (*_all) to include every output rule.

[X] I explained important module design decisions in CHANGELOG.md.

[X] I tested the module on real data for all supported seq_type values and genome_builds.

[X] I updated the default.yaml configuration file to provide default values for each rule in the module snakefile.

[X] I did not set any global wildcard constraints. Any/all wildcard constraints are set on a per-rule basis.

[X] I ensured that all symbolic links are relative and self-contained (i.e. do not point outside of the repository). This includes environment files.

[X] I replaced every value that should (or might need to) be updated in the default configuration file with __UPDATE__.

[X] I recursively searched for all comments containing TODO to ensure none were left. For example:
grep -r TODO modules/<module_name>/1.0

If applicable

[X] I added more granular output subdirectories.

[X] I added rules to the reference_files workflow to generate any new reference files.

[ ] I added subdirectories with large intermediate files to the list of scratch_subdirectories in the default.yaml configuration file.

[ ] I updated the list of available wildcards for the input files in the default.yaml configuration file.

Very clean first version. A few minor suggestions and comments. Ideally we should make version 1.0 support crams if we can.

Thank you! I have addressed the comments and made some minor modifications. I also can confirm it works with cram files I tested. The updated version is ready for review.

Very clean first version. A few minor suggestions and comments. Ideally we should make version 1.0 support crams if we can.

Thank you! I have addressed the comments and made some minor modifications. I also can confirm it works with cram files I tested. The updated version is ready for review.

After I converted the vcfs to maf, I see it does not populate t_depth, t_ref_coun, t_alt_count. I will work on it to make them compatible.

After I converted the vcfs to maf, I see it does not populate t_depth, t_ref_coun, t_alt_count. I will work on it to make them compatible.

After I converted the vcfs to maf, I see it does not populate t_depth, t_ref_coun, t_alt_count. I will work on it to make them compatible.

It was more related to vcf2maf config than to SAGE itself. I fixed it and it is populating reads now. No changes are required to the SAGE module.

Ideally this would be incorporated into the demo but that can wait since we really need this tool in production.

Ideally this would be incorporated into the demo but that can wait since we really need this tool in production.

Ideally this would be incorporated into the demo but that can wait since we really need this tool in production.

I did not add it to the demo since the demo currently is being modified. I thought to include it in the demo with the demo development.

Ideally this would be incorporated into the demo but that can wait since we really need this tool in production.

I did not add it to the demo since the demo currently is being modified. I thought to include it in the demo with the demo development.

Did you need this re-reviewed?

Did you need this re-reviewed?

I have included it in the demo and decreased the disk_mb requirement. I have also tested it outside of the GSC network and found that main_chromosomes need to be added to the rule. These are all modifications. If you approve it, it will be ready to go, so yes, please.

I have included it in the demo and decreased the disk_mb requirement. I have also tested it outside of the GSC network and found that main_chromosomes need to be added to the rule. These are all modifications. If you approve it, it will be ready to go, so yes, please.


Automated cherry pick of #10510: fix: sku zone

Cherry pick of #10510 on release/3.7.
#10510: fix: sku zone

/lgtm
/approve

/lgtm
/approve


api-docs gives 404

Am using v2.6.1, springboot, java9, and have been able to get swagger-ui.html to return header but there is no content. I have set Docket, resourcehandler, websecurity, but /v2/api-docs is empy. Can i see in the log where it scans classes for methods ? I have set host and pathProvider also.

Could you please try with 2.8.0 and report back

On 2.8.0 I get unable to infer to base url, which I do not get with 2.7.0. Do you think swagger.io is more stable and better than springfox swagger ?

from maven repository, it shows that most uses 2.6.1 and 2.7 and not 2.8... have seen other developers having infer issues with 2.8.0 also..

appears to be very little support for this project, and only one person monitoring the forum....

@nickeyzh Yes it is for the most part only one person maintaining the project. Without providing details of your project it is impossible to help.

Well, its springboot apps, which invokes the Docket bean and configures webSecurity to allow the various urls included, via WebSecurityConfigurerAdapter. Can I see in the logs if it traverses the rest api's to collect info for swagger ?

You can turn on logging via normal techiniques... just enable the logging in the packages you need.

Have tried, what kind of messages should I e.g. see in the log ?

You should see logs like this

2018-02-17 09:44:11.461  INFO 34680 --- [           main] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/swagger-resources]}" onto public org.springframework.http.ResponseEntity<java.util.List<springfox.documentation.swagger.web.SwaggerResource>> springfox.documentation.swagger.web.ApiResourceController.swaggerResources()
2018-02-17 09:44:11.461  INFO 34680 --- [           main] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/swagger-resources/configuration/security]}" onto public org.springframework.http.ResponseEntity<springfox.documentation.swagger.web.SecurityConfiguration> springfox.documentation.swagger.web.ApiResourceController.securityConfiguration()
2018-02-17 09:44:11.462  INFO 34680 --- [           main] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/swagger-resources/configuration/ui]}" onto public org.springframework.http.ResponseEntity<springfox.documentation.swagger.web.UiConfiguration> springfox.documentation.swagger.web.ApiResourceController.uiConfiguration()
2018-02-17 09:44:11.465  INFO 34680 --- [           main] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/error]}" onto public org.springframework.http.ResponseEntity<java.util.Map<java.lang.String, java.lang.Object>> org.springframework.boot.autoconfigure.web.BasicErrorController.error(javax.servlet.http.HttpServletRequest)
2018-02-17 09:44:11.465  INFO 34680 --- [           main] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped "{[/error],produces=[text/html]}" onto public org.springframework.web.servlet.ModelAndView org.springframework.boot.autoconfigure.web.BasicErrorController.errorHtml(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse)
2018-02-17 09:44:11.591  INFO 34680 --- [           main] pertySourcedRequestMappingHandlerMapping : Mapped URL path [/api-docs/{swaggerGroup}/{apiDeclaration}] onto method [public org.springframework.http.ResponseEntity<springfox.documentation.spring.web.json.Json> springfox.documentation.swagger1.web.Swagger1Controller.getApiListing(java.lang.String,java.lang.String,javax.servlet.http.HttpServletRequest)]
2018-02-17 09:44:11.592  INFO 34680 --- [           main] pertySourcedRequestMappingHandlerMapping : Mapped URL path [/api-docs] onto method [public org.springframework.http.ResponseEntity<springfox.documentation.spring.web.json.Json> springfox.documentation.swagger1.web.Swagger1Controller.getResourceListing(java.lang.String)]
2018-02-17 09:44:11.596  INFO 34680 --- [           main] pertySourcedRequestMappingHandlerMapping : Mapped URL path [/v2/api-docs] onto method [public org.springframework.http.ResponseEntity<springfox.documentation.spring.web.json.Json> springfox.documentation.swagger2.web.Swagger2Controller.getDocumentation(java.lang.String,javax.servlet.http.HttpServletRequest)]

Make sure you have logging dialed up to INFO least for org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping  and springfox.documentation.spring.web.PropertySourcedRequestMappingHandlerMapping

Seems like its all mapped as expected. The last line shows its mapped url to /v2/api-docs

I have this in access log:
"GET /webSelv/null/swagger-resources/configuration/ui HTTP/1.1" 404 534
Any idea ?
On 21-2-2018 2:08 AM, Dilip Krishnan wrote:

Seems like its all mapped as expected. The last line shows its mapped
url to |/v2/api-docs|
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/2236#issuecomment-367178504,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATKvG-X9ie_TQ3VAdh2yrDQB5k-bb3fuks5tW2yBgaJpZM4R792Y.

What is alternative to springfox ?
On 22-2-2018 21:25 PM, Peter Holm wrote:

I have this in access log:
"GET /webSelv/null/swagger-resources/configuration/ui HTTP/1.1" 404 534
Any idea ?
On 21-2-2018 2:08 AM, Dilip Krishnan wrote:

Seems like its all mapped as expected. The last line shows its mapped
url to |/v2/api-docs|
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/2236#issuecomment-367178504,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATKvG-X9ie_TQ3VAdh2yrDQB5k-bb3fuks5tW2yBgaJpZM4R792Y.

Error:
16:39:34.064 [localhost-startStop-3] DEBUG o.s.jndi.JndiLocatorDelegate

Converted JNDI name
[java:comp/env/springfox.documentation.swagger.v2.host] not found -
trying original name [springfox.documentation.swagger.v2.host].
javax.naming.NameNotFoundException: Name
[springfox.documentation.swagger.v2.host] is not bound in this Context.
Unable to find [springfox.documentation.swagger.v2.host].
16:39:34.064 [localhost-startStop-3] DEBUG o.s.jndi.JndiPropertySource -
JNDI lookup for name [springfox.documentation.swagger.v2.host] threw
NamingException with message: Name
[springfox.documentation.swagger.v2.host] is not bound in this Context.
Unable to find [springfox.documentation.swagger.v2.host].. Returning null.
16:39:34.064 [localhost-startStop-3] DEBUG
o.s.c.e.PropertySourcesPropertyResolver - Could not find key
'springfox.documentation.swagger.v2.host' in any property source
16:39:34.064 [localhost-startStop-3] DEBUG o.s.jndi.JndiLocatorDelegate
Converted JNDI name
[java:comp/env/springfox.documentation.swagger.v2.path] not found -
trying original name [springfox.documentation.swagger.v2.path].
javax.naming.NameNotFoundException: Name
[springfox.documentation.swagger.v2.path] is not bound in this Context.
Unable to find [springfox.documentation.swagger.v2.path].

should host and path not be set ?
On 24-2-2018 16:45 PM, Peter Holm wrote:

What is alternative to springfox ?
On 22-2-2018 21:25 PM, Peter Holm wrote:

I have this in access log:
"GET /webSelv/null/swagger-resources/configuration/ui HTTP/1.1" 404 534
Any idea ?
On 21-2-2018 2:08 AM, Dilip Krishnan wrote:

Seems like its all mapped as expected. The last line shows its
mapped url to |/v2/api-docs|
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/2236#issuecomment-367178504,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATKvG-X9ie_TQ3VAdh2yrDQB5k-bb3fuks5tW2yBgaJpZM4R792Y.

Not really working, springfox:
"GET /webSelv/v2/api-docs HTTP/1.1" 404 534
Dispite:
Mapped URL path [/v2/api-docs] onto method [public
org.springframework.http.ResponseEntity<springfox.documentation.spring.web.json.Json>
springfox.documentation.swagger2.web.Swagger2Controller.getDocumentation(java.lang.String,javax.servlet.http.HttpServletRequest)]
and websecurity disabled:
Creating filter chain: Ant [pattern='/v2/api-docs/**'], []
What to try next, already on 2.8 - maybe 2.9 ?
On 24-2-2018 16:51 PM, Peter Holm wrote:

Error:
16:39:34.064 [localhost-startStop-3] DEBUG
o.s.jndi.JndiLocatorDelegate - Converted JNDI name
[java:comp/env/springfox.documentation.swagger.v2.host] not found -
trying original name [springfox.documentation.swagger.v2.host].
javax.naming.NameNotFoundException: Name
[springfox.documentation.swagger.v2.host] is not bound in this
Context. Unable to find [springfox.documentation.swagger.v2.host].
16:39:34.064 [localhost-startStop-3] DEBUG o.s.jndi.JndiPropertySource

JNDI lookup for name [springfox.documentation.swagger.v2.host] threw
NamingException with message: Name
[springfox.documentation.swagger.v2.host] is not bound in this
Context. Unable to find [springfox.documentation.swagger.v2.host]..
Returning null.
16:39:34.064 [localhost-startStop-3] DEBUG
o.s.c.e.PropertySourcesPropertyResolver - Could not find key
'springfox.documentation.swagger.v2.host' in any property source
16:39:34.064 [localhost-startStop-3] DEBUG
o.s.jndi.JndiLocatorDelegate - Converted JNDI name
[java:comp/env/springfox.documentation.swagger.v2.path] not found -
trying original name [springfox.documentation.swagger.v2.path].
javax.naming.NameNotFoundException: Name
[springfox.documentation.swagger.v2.path] is not bound in this
Context. Unable to find [springfox.documentation.swagger.v2.path].

should host and path not be set ?
On 24-2-2018 16:45 PM, Peter Holm wrote:

What is alternative to springfox ?
On 22-2-2018 21:25 PM, Peter Holm wrote:

I have this in access log:
"GET /webSelv/null/swagger-resources/configuration/ui HTTP/1.1" 404 534
Any idea ?
On 21-2-2018 2:08 AM, Dilip Krishnan wrote:

Seems like its all mapped as expected. The last line shows its
mapped url to |/v2/api-docs|
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/2236#issuecomment-367178504,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATKvG-X9ie_TQ3VAdh2yrDQB5k-bb3fuks5tW2yBgaJpZM4R792Y.

Hard to say without a reporducable project or test. Could you perhaps clone the demos application and try and reproduce the problem. Otherwise see how your project is different from the demos.

you can improve transparency, as many others have been commenting on the
issues with springfox, so more logging please. When is next release ?
On 25-2-2018 17:51 PM, Dilip Krishnan wrote:

Hard to say without a reporducable project or test. Could you perhaps
clone the demos https://github.com/springfox/springfox-demos
application and try and reproduce the problem. Otherwise see how your
project is different from the demos.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/2236#issuecomment-368324717,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATKvG0jiFYRlYJgxTSgKoZYafPKVFwhNks5tYY-pgaJpZM4R792Y.

http://localhost:8081/base/v2/api-docs gives 404 on this in access
/base/null/swagger-resources/configuration/ui - where does the null come
from ? bug ?
or this NullPointerException:
22:10:42.304 [localhost-startStop-1] DEBUG
o.s.b.f.annotation.InjectionMetadata - Processing injected element of
bean 'serviceModelToSwagger2MapperImpl': AutowiredFieldElement for
private springfox.documentation.swagger2.mappers.ModelMapper
springfox.documentation.swagger2.mappers.ServiceModelToSwagger2MapperImpl.modelMapper
22:10:42.304 [localhost-startStop-1] DEBUG
o.s.core.annotation.AnnotationUtils - Failed to meta-introspect
annotation [interface
org.springframework.beans.factory.annotation.Autowired]:
java.lang.NullPointerException
22:10:42.305 [localhost-startStop-1] DEBUG
o.s.b.f.s.DefaultListableBeanFactory - Returning cached instance of
singleton bean 'modelMapperImpl'
22:10:42.316 [localhost-startStop-1] DEBUG
o.s.b.f.a.AutowiredAnnotationBeanPostProcessor - Autowiring by type from
bean name 'serviceModelToSwagger2MapperImpl' to bean named 'modelMapperImpl'
22:10:42.316 [localhost-startStop-1] DEBUG
o.s.b.f.annotation.InjectionMetadata - Processing injected element of
bean 'serviceModelToSwagger2MapperImpl': AutowiredFieldElement for
private springfox.documentation.swagger2.mappers.ParameterMapper
springfox.documentation.swagger2.mappers.ServiceModelToSwagger2MapperImpl.parameterMapper
22:10:42.316 [localhost-startStop-1] DEBUG
o.s.core.annotation.AnnotationUtils - Failed to meta-introspect
annotation [interface
org.springframework.beans.factory.annotation.Autowired]:
java.lang.NullPointerException
On 27-2-2018 22:08 PM, Peter Holm wrote:

you can improve transparency, as many others have been commenting on
the issues with springfox, so more logging please. When is next release ?
On 25-2-2018 17:51 PM, Dilip Krishnan wrote:

Hard to say without a reporducable project or test. Could you perhaps
clone the demos https://github.com/springfox/springfox-demos
application and try and reproduce the problem. Otherwise see how your
project is different from the demos.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/springfox/springfox/issues/2236#issuecomment-368324717,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATKvG0jiFYRlYJgxTSgKoZYafPKVFwhNks5tYY-pgaJpZM4R792Y.


sample applications and grafana-operator argocd app for multi-account CDK Observability accelerator

This PR adds three new contents to artifacts:

grafana-operator-chart - helm charts to deploy grafana-operator resources like datasources, dashboards and grafana identity.
sample-apps - sample argocd apps that will be deployed multi-account clusters and grafana-operator-app to deploy grafana-operator resources as argocd apps.
teams - supporting resource for sample argocd apps.

@iamprakkie Please fix the warnings.

@elamaran11 All warnings fixed

incorporated review comments

moved teams, sample-apps and grafana-operator-chart to artifacts/argocd-apps
removed teams not in use with multi-account pattern (removed team-kirk, team-data, team-danger, team-scan, team-platform, team-burnham and team-riker). retained team-geordie and team-carmen
moved grafana-operator-app to artifacts/argocd-apps
removed samples-apps/envs/dev and samples-apps/envs/test. Retaining only samples-apps/envs/prod
updated apps with path changes


Feat: diff view can manipulate selected range

This PR fixes #88369 also fixes #9475

Need to update test

Need to update test

Yes,  that is a big issue,  I'm going to close this PR.

Yes,  that is a big issue,  I'm going to close this PR.


How to you do Site recovery if Resource group is  west us and VM is in east US

Resource Groups of one region allows resource from multiple regions. I am not able to use site recovery if Resource group belongs to one region and VM belongs to another region

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 94df3619-b79b-0ec3-ec94-5928c1458d94
Version Independent ID: 18fdcc5a-f2d1-93ce-9053-458e1cf1dd36
Content: Set up disaster recovery for an Azure IaaS VM to a secondary Azure region
Content Source: articles/site-recovery/azure-to-azure-quickstart.md
Service: site-recovery
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

@tkumark Thanks for your question. We are checking on this and will respond to you soon.

Please assign to me. Investigating

Investigating this one.

Thanks for your feedback. This should work. If it doesn't please request help in the Site Recovery forum - https://social.msdn.microsoft.com/forums/azure/en-us/home?forum=hypervrecovmgr
#please-close


Background audio playback always occurs, even when PiP is not active

When you exit the Youtube app while a video is playing, then background audio playback will be playing whether or not PiP is also playing. I troubleshooted with choicy to determine that this issue is in fact caused by YouPiP entirely independently of other tweaks.
I think that the background playback should be off by default in this tweak, but a toggle could be nice.

PiP requires background playback. YouPiP enables PiP and expects background playback to already function. In what real-world cases do you not want background playback?

I often will leave the YouTube app to do something else, not planning on
the video I'm watching to continue in background playback. This can often
happen when I'm following an instructional video on youtube, when I could
exit an app to follow along with the video and being able to return to the
youtube app where I left off. I also sometimes just want to quickly exit
the app of put my phone to sleep, and while this can be done by pausing, it
is more convenient without background playback.
To elaborate on what I meant by a toggle or disabling background playback,
I meant only disabling it when PiP is not in use, assuming this is
possible. I do realize that its a possibility that disabling background
playback as described may be impossible, buggy, or otherwise not viable.
On Sat, Aug 13, 2022 at 8:25 AM Thatchapon Unprasert <
@.***> wrote:

PiP requires background playback. YouPiP enables PiP and expects
background playback to already function. In what real-world cases do you
not want background playback?
—
Reply to this email directly, view it on GitHub
https://github.com/PoomSmart/YouPiP/issues/64#issuecomment-1214148642,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQRQHJHRW4GI4V6N56ZB2VLVY6H3ZANCNFSM56N2OQFQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

YouPiP doesn't plan to have this feature.


module.exports = vendor_a5a86878640dfc60743a; error in IE 11

I'm testing the React redux template, but are unable to get it to run in IE 11. It breaks at module.exports = vendor_a5a86878640dfc60743a as vendor_a5a86878640dfc60743a is undefined.  Works fine in Chrome.
Edit: after looking some more i found that the vendor.js had element using .map(() => {}) that EI 11 did not like. I tried to { test: /.js?$/, use: 'babel-loader' } to the webpack.config.vendor.js and setting up the .babelrc to this "presets": [ "react", "es2015-ie" ]. That did not work very well. Is there a way of making the vendor.js support IE 11?

We have issue #484 tracking the need for out-of-the-box IE11 support in the templates.
If you need to make your own app support IE11 quickly, I'd recommend referencing the core-js package (i.e., npm install --save core-js), and then putting import 'core-js/shim'; at the top of your boot-client.ts file. That package puts in polyfills for pretty much everything.


Serialize typescript related AST fields with undefined instead of null

Currently, when building oxc-compatible AST nodes from within Javascript, typescript-related fields (typeAnnotation, etc.) are serialized and deserialized as nullable fields. This makes for pretty inconvenient code if you're not working with them, i.e.
const param = {
  type: 'FormalParameter',
  pattern: {
    ...pattern,
    typeAnnotation: null,
  },
  decorators: [],
  accessibility: null,
  readonly: false,
  override: false
}

If these were serialized using something like #[serde(skip_serializing_if)], it would not only make the serialized values smaller (saving FFI transfer times), but also make constructing the nodes manually easier:
const param = {
  type: 'FormalParameter',
  pattern,
  // all the typescript-only fields are optional!
}

Here's an example of what it could look like. Since the javascript oxc-parser package is still experimental, this should be fine as a breaking change.

Thanks for raising this. I've actually been thinking along the same lines, but with a different implementation method. https://github.com/oxc-project/backlog/issues/119 (see section 3).
I'm sorry to say that the JS API is not our current focus - we're currently working on implementing the rest of the transforms down to ES6, and hardening the existing ones - so all Rust-side stuff. Hence why I opened the issue in our "backlog" repo instead of here. But, personally, I do feel it's really important that the JS-facing APIs are as good as the Rust ones, so we will turn our attention to this at some point soon(ish).
Closing this issue, not because it's an unreasonable request, but because I think https://github.com/oxc-project/backlog/issues/119 already covers it.

By the way, speaking of FFI transfer times, we do have something in the works which is going to massively speed that up. Watch this space...

Thanks for the response! The linked issue seems great, let me contextualize a bit more:
I'm currently researching what it would take to port Svelte's parser from acorn + acorn-typescript to oxc. So far I've found that even with FFI overhead, oxc via napi is anywhere from 5-20x faster! However, there are a few important limitations that have forced me to inject this code into oxc via a build script:

No way to parse_expression and return Trivias
No exposed method to parse a binding pattern

Additionally, I hacked together this type definition file by adding a new generator to ast_tools that invoked tsify. It works alright, but is definitely not as easy to use as @types/estree. One thing to consider is this: when building ASTs in JS, you can't specify the Span for each node. This forced me to duplicate the type definitions to have one version with start and end on the base node interface and one without.
In the linked backlog issue, you mentioned estree compatibility. This would save a lot of effort in the migration, but I'm curious if this would include having a single Literal node vs. NumericLiteral etc.? In the backlog issue, you mention

Currently we have pretty complex custom Serialize impls for massaging Oxc's AST into ESTree-compatible shape in oxc_ast/src/serialize.rs.

but currently while the shape is similar, it's definitely not a drop-in replacement.
Final question - what would the timeline look like? I would like to contribute to this if the oxc team is going to be focusing on other stuff.

Thanks for coming back. Interesting points. Am tied up now - will reply tomorrow.

On the ESTree compat question: Our intention is 100% ESTree compatibility (so, yes, one Literal type). Please see #2463 and #2854.
The only part that's fuzzy is what flavour of ESTree-like AST for TS? I've not got to the bottom of this question, but my understanding is there are a few competing implementations, and I'm not sure:

How similar they are to each other.
Whether they (a) extend ESTree by just adding extra types, and extra properties to existing types, or (b) in some places they diverge from original ESTree. i.e. a "TS ESTree" AST would not be a valid "original ESTree" AST. If the latter, it's more problematic.

Do you have any idea on that?

I've used https://astexplorer.net to compare different outputs. I've also looked at SWC's compatibility layer, which has an option for babel and acorn (although theirs is incomplete and doesn't convert all ASTs).
From what I understand, typescript ASTs are not standardized at all. You'll get different representations from typescript-eslint, acorn-typescript (which is abandoned and undocumented), or the official typescript parser.
typescript-eslint seems to represent declare function as a different node type which might be an issue.
In my mind since there's no consensus among parsers it might be best to take whichever path is easiest to implement for oxc. Acorn should be the primary target for compatibility, and since acorn has no official typescript support and the only plugin for it is undocumented, this is an opportunity to provide accurate and complete type definitions for future tooling.

Is there already any progress on https://github.com/oxc-project/backlog/issues/119 or would it be okay to start work on a PR for it?

@ottomated I've moved #6347 into the main repo. I've asked the main man Boshen if he sees any problem with what I've proposed. I assume he'll be fine with it, but I just want to check before you pile in and do a load of work - don't want to waste your time. Assuming all good, it'd be brilliant if you would like to take it on.

I'm currently researching what it would take to port Svelte's parser from acorn + acorn-typescript to oxc. So far I've found that even with FFI overhead, oxc via napi is anywhere from 5-20x faster!

I'm actually really surprised it's so fast. Oxc's parser is certainly speedy, but from when I last benchmarked, the cost of transferring AST between Rust and JS rather hobbles it, so it was in same ballpark as JS parsers (Acorn, Babel etc). But if it's working better than I thought, great!

One thing to consider is this: when building ASTs in JS...

You are aware that Oxc currently doesn't expose a JS interface to get an AST back from JS into Rust to print it? We should, and we will, but it's not there yet.

currently while the shape is similar, it's definitely not a drop-in replacement.

Yes, it's a work in progress. It's closer to ESTree than it was, but still diverges in a lot of places (as I'm sure you've found). One of the motivators for #6347 is to make it easier to complete the job of getting it in line. Writing Serialize impls by hand is not trivial (impl Serialize is pretty horrible API) and those impls need to be kept in sync when we make changes to the Rust AST, which is also painful.

In my mind since there's no consensus among parsers it might be best to take whichever path is easiest to implement for oxc. Acorn should be the primary target for compatibility, and since acorn has no official typescript support and the only plugin for it is undocumented, this is an opportunity to provide accurate and complete type definitions for future tooling.

Thanks for the background on this.
I agree that for plain JS we should converge with ESTree (Acorn) and aim for 100% compatibility.
For TS, either typescript-eslint or official TS parser's AST sounds like the best target. @ArnaudBarre, who did a lot of the last batch of work on getting Oxc's JS AST into line with ESTree, was keen to use Oxc as a parser for Prettier, which we gather requires a typescript-eslint AST (https://github.com/oxc-project/oxc/issues/2463#issuecomment-1956607866), so maybe that's the best starting point.

typescript-eslint seems to represent declare function as a different node type which might be an issue.

There will no doubt be many such oddities. We'll just have to work around them. It's not out of the question to alter our Rust AST to match ESTree/TS-ESTree on occasion to help. Personally I think our AST should have a separate node type for declare function anyway, though others might disagree.
Anyway... thanks loads for your interest in working on this. It's one of those things that I think is really important, and I have been meaning for ages to get onto it, but just not enough time in the day...

@ottomated Spoke to Boshen. We have go-ahead for #6347. I'll write up some thoughts on that issue later today.
I think we can close this issue in favour of that one? Or do you consider them slightly different things?


Support for Sony NEX-6 and a6000

Hello.
Nice job, and as per subject, I'd like to see support for those cameras. If nobody has objections, I'd fork and try the patch myself.
Notes: I'm a very experienced programmer and in the past I've also done a lot of reverse engineering work with EXIF and RAW metadata manipulation. Unfortunately I don't have experience in LUA. So, while I'm willing to try it, I can't be sure I'll be good on that. My message is: if somebody else wants to start working on the Sony support, please don't be blocked supposing I'm already near to provide a solution.

Is it working with Sony A6000 now? Or with any other from the Sony mirrorless line? A6x00 series? A7 series?

No support for Sony. You're welcome to add it though. It would be appreciated

Your work is great. I very much appreciate it. I wish I could provide support but I m afraid I cannot. My programming skills are nowhere sufficient.

On 24 Apr 2017, at 00:49, Joshua Musselwhite<EMAIL_ADDRESS>wrote:
No support for Sony. You're welcome to add it though. It would be appreciated
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

if you put 4 raw files from whatever sony camera you have into a google drive zip link I'll take a look. Put 1 focus point in the center and move the focus point somewhere else for the other. No promises. I've never seen sony add the metadata to an image yet, but I've only seen center shot raws.

You are great. Will get that done right away.

On 24 Apr 2017, at 19:29, Joshua Musselwhite<EMAIL_ADDRESS>wrote:
if you put 4 raw files from whatever sony camera you have into a google drive zip link I'll take a look. Put 1 focus point in the center and move the focus point somewhere else for the other. No promises. I've never seen sony add the metadata to an image yet, but I've only seen center shot raws.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

hello again,here is the link:focus-points – Google Drive
|
|    |
focus-points – Google Drive
|  |
|
I uploaded 15 raw files. All taken with Sony A7Rm2. There also are 15 txt files with the exif data. 1 xls file explaining my settings as I took the photos, 2 mov files showing how AF-C looked on certain cases.
You mentioned that Sony does not provided enough info on exif. Below are the tag names I found relavant to your work. I plotted some focus related data on Excel, looked very meaningful.
Focus Mode                      : AF-SAF Area Mode Setting            : Flexible SpotFlexible Spot Position          : 65 419AF Zone Selected                : n/aAF Points Used                  : (none)Focal Plane AF Points Used      : (none) **Focus Location                  : 3984 2656 404 2318AF Area Mode                    : Flexible Spot
Focus Position 2                : 155Exif Image Width                : 7952Exif Image Height               : 5304Sony Image Height               : 2656Sony Image Width                : 3984
** "Focal Plane AF Points Used" has values when AF-C is used.
I wish I had the programming skills to help but this is all I could.
All the very best.
Babur Hakarar
On Monday, April 24, 2017 7:29 PM, Joshua Musselwhite<EMAIL_ADDRESS>wrote:

if you put 4 raw files from whatever sony camera you have into a google drive zip link I'll take a look. Put 1 focus point in the center and move the focus point somewhere else for the other. No promises. I've never seen sony add the metadata to an image yet, but I've only seen center shot raws.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I extracted the exif data on txt files using a software I found on the internet: ExifToolGUI
On Tuesday, April 25, 2017 2:23 AM<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:

hello again,here is the link:focus-points – Google Drive
|
|    |
focus-points – Google Drive
|  |
|
I uploaded 15 raw files. All taken with Sony A7Rm2. There also are 15 txt files with the exif data. 1 xls file explaining my settings as I took the photos, 2 mov files showing how AF-C looked on certain cases.
You mentioned that Sony does not provided enough info on exif. Below are the tag names I found relavant to your work. I plotted some focus related data on Excel, looked very meaningful.
Focus Mode                      : AF-SAF Area Mode Setting            : Flexible SpotFlexible Spot Position          : 65 419AF Zone Selected                : n/aAF Points Used                  : (none)Focal Plane AF Points Used      : (none) **Focus Location                  : 3984 2656 404 2318AF Area Mode                    : Flexible Spot
Focus Position 2                : 155Exif Image Width                : 7952Exif Image Height               : 5304Sony Image Height               : 2656Sony Image Width                : 3984
** "Focal Plane AF Points Used" has values when AF-C is used.
I wish I had the programming skills to help but this is all I could.
All the very best.
Babur Hakarar
On Monday, April 24, 2017 7:29 PM, Joshua Musselwhite<EMAIL_ADDRESS>wrote:

if you put 4 raw files from whatever sony camera you have into a google drive zip link I'll take a look. Put 1 focus point in the center and move the focus point somewhere else for the other. No promises. I've never seen sony add the metadata to an image yet, but I've only seen center shot raws.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, Can you try opening the ticket on the web and not replying from the email? The links aren't coming through.

hello.
i m trying to post the link once again:
https://drive.google.com/drive/folders/0BzJJz2wN4bPzYTNMOTRwdEl6eFU?usp=sharing
thanks for bearing with me..

For 9856.txt
Focus Mode                           : AF-S AF Area Mode Setting            : Flexible Spot Flexible Spot Position            : 545 397 AF Points Used                      : (none) Focal Plane AF Points Used    : (none) Focus Location                      : 3984 2656 3392 2196 Focus Position 2                    : 160
The above are most likely the values that are needed. From what I'm seeing, the only thing that would make sense for where the camera focused is the Focus Location property but I'm not really sure what these values mean. Is it x y x y with 2 focus points active? Without a sony camera in my hand it's really hard to figure it out. If you can figure out how the metadata relates to the focus point, I might be able to program it. My guess right now is there was 2 focus points one at point {3984,2656} and one at {3392,2196}. If you were to map those points in photoshop does that look accurate? If not, I'm really not sure what Sony does for it's metadata. If you can figure that out and let me know how the metadata relates to the focus point, I might be able to add support for the camera.

I believe this is for 9865.txt
For Focus Location, what I understand is we have a 3x2 area of (0,0) and (3984,-2656) and that the camera's AF can scan from (404,-332) to (3579,-2318) on top left and bottom right respectively.
Sony a7rii has 399 PDAF focus points. That would mean I should be able to move my 'small' flexible spot in an area of 21x19 but the fact is I can only do it 19x17. That means the smallest spot the camera allows the user is larger than a focus point. I covered the x axis with 19 test shots and looked at the x axis increment value in between each shot: 2x93 and the rest either 186 or 187..
In my opinion Flexible Spot Position looks meaningful much like Focus Location but maybe in a 4x3 area..
I guess not I'm not much help ...
PS.
I uploaded the xls file I worked on to plot exif data and jpg showing sony a7rii pdaf focus points.
Corrected a minor mistake on prev. xls file.

I think this is going to be too complicated for me to do with having access to a Sony. Unfortunately we're at the mercy of someone else adding support for the camera.

I could find some time in the next days, if I don't run into unforeseen troubles, to run more tests. I have the NEX-6 and the a6000 (the a6300 is on its way).

Hi guys, are there any further plans to support Sony?
I can provide raw files from A7 mk3

Support for Sony cameras would be nice!