fix: update all downloaded files with their SHA256 checksum

Description

Use SHA256 checksums for all the downloaded files.
Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Depends on https://github.com/autowarefoundation/autoware/pull/3848


Adding static map to HIA?

Question that came up during the User Test insights presentation:
Is it possible to add a (static) map to show the location of an organisation?
We also see that a lot of organisations hand out A4 papers with relevant information (usually address & contact details) that also includes a screenshot of a map.
Important to consider: loading time with slow/low internet connectivity when using HIA on shared WiFi network.

Free free option: https://openfreemap.org/


Test Efficiency of PyPy Tests With Coverage Disabled

I found that someone did this and got good results. Let's see if this actually helps us out.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Codecov Report

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

@@           Coverage Diff           @@
##           master    #4596   +/-   ##
=======================================
  Coverage    49.5%    49.5%
=======================================
  Files        6332     6332
  Lines      177160   177160
=======================================
  Hits        87710    87710
  Misses      89450    89450

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 4ea38dd...9f0c153. Read the comment docs.


Is implementation of verifyScope required?

I understand the point of validateScope function, however, the library also has a verifyScope definition in model which never get's called at any point. I also tried searching for this function in the repository and couldn;t find any place where it is called but there are references to it. What's the deal with this function? Can I delete verifyScope implementations from my model?

@shrihari-prakash which version of the package do you refer to and in which file is this function call located?

Hello @jankapunkt ,
I am on version 4.3.0.
This is the function I am talking about: https://node-oauthoauth2-server.readthedocs.io/en/latest/model/spec.html#verifyscope-accesstoken-scope-callback
The model specification strictly wants this function, but when I implement it with a simple console, I never see it called. (See sample here: https://github.com/shrihari-prakash/liquid/blob/352f6f96cc518452489aabd11d9587be0dca3cb3/src/model/oauth.ts#L329)

This seems to be an outdated documentation. However, let me check the code whether this might still be located somewhere.

These are the search results when I tried to see where this is called: https://github.com/search?q=repo%3Anode-oauth%2Fnode-oauth2-server verifyScope&type=code
Not sure if something doesn't appear in git search.

Oh there were matches I did not expand :). In any case, verifyScope is never called when calling authenticate

Okay I rechecked and they were named differently because they implement different things:
verifyScope  - In AuthenticateHandler - Invoked during request authentication to check if the provided access token was authorized the requested scopes.
validateScope - In AuthorizeHandler - Invoked to check if the requested scope is valid for a particular client/user combination.
Note that verifyScope is never called when you provide your own authenticateHandler for the server.authorize  method: https://node-oauthoauth2-server.readthedocs.io/en/latest/api/oauth2-server.html#authorize-request-response-options-callback

Aah ok understood! Perhaps it is a good idea to make verifyScope optional in types as TypeScript throws an error if you do not implement it even though it is optional. :)

Hm this is a bit problematic, since it's only optional if you provide your own authenticateHandler but by default it's could be required when scope is passed. I'm not sure if this kind of logic can be covered by TypeScript?

Let me check the types file and see if such a logic can be incorporated.

@jankapunkt you are right. It's pretty hard to achieve this conditional thing. However, one realistic option is we make the verifyScope optional and throw an error if we do not find it when custom auth handler is passed. What do you think?

Hm this is a bit problematic, since it's only optional if you provide your own authenticateHandler but by default it's could be required when scope is passed. I'm not sure if this kind of logic can be covered by TypeScript?

@jankapunkt are you saying even if you do not provide your own authenticateHandler verifyScope might only be required under certain other conditions?

@shrihari-prakash this logic is already implemented, see https://github.com/node-oauth/node-oauth2-server/blob/development/lib/handlers/authenticate-handler.js#L40
What I'm referring to is to project this logic into the types system:

verifyScope is optional if a custom authenticateHandler is passed as options to authorize
it's also optional if the authentication request does not contain a scope (see line above)
otherwise it's required

Nice.. Good that the error logic is already there. Then I do not see a problem with making the verifyScope function optional in types. Can I send a PR?

Thanks, would you mind helping out with #210 as well?

Sure. No problem.

Closing as verifyScope has been made optional.


Add an init command to enable easy installation

This change will add a nebula-css command line tool.
You can run:
nebula-css.js --help
For the list of commands.
The only available command at the moment is init.
nebula-css.js init
By default it will create a scss folder with everything in it.
You can override this folder by doing:
nebula-css.js -d mydirectoryname
or
nebula-css.js --dirname mydirectoryname
You can also get info on the command by doing:
nebula-css.js init --help.
I'm pretty sure when installed via npm, this would enable the user to do:
node_modules/bin/nebula-css --help
Or, if installed globally, I think this will work:
nebula-css --help

I will check this out in detail as soon as I can.  Really swamped this week with work...

@rbrtsmith No worries. Don't feel under any pressure to merge if it's not how you would want to do it.
I figured doing it this way opens you up to being able to use the commander npm tool to potentially ask the user questions about default settings and so on and so forth.


Integrated LocoNet

For planning purposes it is good to know if a module has integrated LocoNet or not. For modules with integrated LocoNet, LN-boxes are not required.

Fixed in release 1.0.2.


How to get headers from SpanContext?

I have a SpanContext and I'm attempting to get those encoded into headers, should I just do a 1:1 with the X-B3's? or should that be provided in some way? Am I missing what that way should be?

We do not have a proper implementation yet.
I described the idea here
https://github.com/typelevel/otel4s/issues/147

Hmmm, well I was going to attempt the basics as a PoC, which means getting information in and out of headers in some form. I was going to do basic B3 style, but I also don't seem to be able to get the ParentSpanId from a span/spancontext.

I also don't seem to be able to get the ParentSpanId from a span/spancontext

I've just come into this too :o was expecting to find the parent span ID in the SpanContext. Is there no way to get it atm?

Neither Span nor SpanContext holds a reference to the parent in Otel.  Remote parents can be extracted via propagators.  joinOrRoot is a high-level method with lower-level usage.  A TextMapGetter instance for the carrier (e.g., HTTP headers) would make it convenient to call.
Injecting the current context into headers is awkward as of 0.2.1, for reasons discussed in #147.  But thanks to the unsafeSet on TextMapSetter, I imagine we can create an alternate injector signature that uses an immutable carrier and a mutable builder with a TextMapSetter that hides the mutation and still interoperates with all the propagators in a compliant SDK.

Starting from 0.3.0-RC1, you can use:
val headers: F[Map[String, String]] = Tracer[F].propagate(Map.empty[String, String])

as 0.3.0 has been released, I'm closing this as fixed/addressed


Lower accuracy than expected on VOC 2007 model & data

Thank you for providing your code. I have installed and run the test provided but unfortunately I am seeing lower accuracy on the VOC 2007 benchmark than I expected.
On the Readme I see that the model achieves 71.2 but when I run ./experiments/scripts/test_vgg16.sh 0 pascal_voc with VOC 2007 data and your model I see a result of Mean AP = 0.4955. If I am right this is meant to be interpreted as an mAP of 49.55. Should I be using a different testing script or different model than the one downloaded by ./data/scripts/fetch_faster_rcnn_models.sh ? Here are the full results:
AP for aeroplane = 0.5898 AP for bicycle = 0.5308 AP for bird = 0.4317 AP for boat = 0.3876 AP for bottle = 0.2347 AP for bus = 0.6052 AP for car = 0.5414 AP for cat = 0.6908 AP for chair = 0.2789 AP for cow = 0.5222 AP for diningtable = 0.5555 AP for dog = 0.6149 AP for horse = 0.7065 AP for motorbike = 0.5160 AP for person = 0.4421 AP for pottedplant = 0.2304 AP for sheep = 0.4441 AP for sofa = 0.5538 AP for train = 0.6770 AP for tvmonitor = 0.3559 Mean AP = 0.4955

I should also note that after completion of the testing script I receive a notification about a segfault which I am unsure how to trace. Perhaps this may be a part of the problem?
./experiments/scripts/test_vgg16.sh: line 60:   338 Segmentation fault      (core dumped) CUDA_VISIBLE_DEVICES=${GPU_ID} python ./tools/test_vgg16_net.py --imdb ${TEST_IMDB} --weight data/imagenet_weights/vgg16.weights --model ${NET_FINAL} --cfg experiments/cfgs/vgg16.yml --set ${EXTRA_ARGS}

Just tried, got 0.7092 mAP, similar to what's reported in the paper.

Not sure what happened in your case. Can you provide your hardware and software setup? I don't have segfault here.

Hey! Thank you very much for replying. As it turns out the reason for the incorrect accuracy was due to the wrong GPU architecture being specified in the extra_compile_args in the setup.py script. I needed -arch=sm+52 because I am using a Titan X. Interestingly the segfault still appears at the end of testing, but since the testing is functional I have all that I need to continue.
I'll close this issue for sure since everything is working, but I should also mention that a few things might want to be changed in the code to help Linux users like myself. I've made a pull request that you might be interested in. Thanks again!

Suffered from similar problem! I have a little old GPU, gtx 780, the third generation architecture (Kepler). If using the default sm_52, the accuracy is incorrect. Change it to 'sm_35' will get the reported mAP...
It is so tricky. I wonder why the compilation of nms was successful when using incorrect -arch parameter..

@mbuckler After correct the sm_xx, did you get extact 71.2 mAP? I correct the sm_xx for my GTX780, but tested with the pretrained model voc07 from the authors page, I got the mAP 70.89; while with the pretrained model on voc07+voc12, I tested with the mAP 74.95.  Is these correct numbers? @endernewton

TEST.MODE top? default is a little bit lower TEST.MODE nms.

Ender X. Chen
Language Technologies Institute,
School of Computer Science,
Carnegie Mellon University, Pittsburgh, PA
On Sat, Apr 29, 2017 at 6:40 PM, Xiaoke Jia<EMAIL_ADDRESS>wrote:

@mbuckler https://github.com/mbuckler After correct the sm_xx, did you
get extact 71.2 mAP? I correct the sm_xx for my GTX780, but tested with the
pretrained model voc07 from the authors page, I got the mAP 70.89; while
with the pretrained model on voc07+voc12, I tested with the mAP 74.95. Is
these correct numbers? @endernewton https://github.com/endernewton
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/endernewton/tf-faster-rcnn/issues/5#issuecomment-298198949,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTwEWmz0_yiND8-Y2pcNgXWtv-G3piGks5r07x5gaJpZM4L9-wq
.

Hi, I also got 0.5206 mAP after running the test script.  I am using Telsa P100 and I have set the arch to be sm_60 according to "http://arnon.dk/matching-sm-architectures-arch-and-gencode-for-various-nvidia-cards/". Is it anything wrong?


Maximum call stack size exceeded with 1.3M data points

I'm trying to load a file with 1.3M points into hexagon layer (using the 3d-heatmap example) but I get this error in Chrome:
deck.gl deck.gl error during update of <HexagonLayer:'heatmap'> RangeError: Maximum call stack size exceeded
    at BinSorter.getMaxCount (bin-sorter.js:104)
    at new BinSorter (bin-sorter.js:45)
    at HexagonLayer.getSortedBins (hexagon-layer.js:172)
    at HexagonLayer.updateState (hexagon-layer.js:129)
    at HexagonLayer.updateLayer (layer.js:537)
    at LayerManager._updateLayer (layer-manager.js:701)
    at _loop (layer-manager.js:514)
    at LayerManager._matchSublayers (layer-manager.js:562)
    at LayerManager._updateLayers (layer-manager.js:465)
    at LayerManager.updateLayers (layer-manager.js:257)

This should be a one line fix, just replace the apply with a loop.

Fixed on master, will be published in patch release soon.


运行yolov4的export报错

Environment
Hardware Environment(Ascend/GPU/CPU):

Uncomment only one  /device <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/device ascend

Software Environment:

MindSpore version (source or binary):
Python version (e.g., Python 3.7.5):
OS platform and distribution (e.g., Linux Ubuntu 16.04):
GCC/Compiler version (if compiled from source):

Describe the current behavior
Traceback (most recent call last):
File "./deploy/export.py", line 84, in
export_weight(args)
File "./deploy/export.py", line 68, in export_weight
checkpoint_path=args.weight,
File "/home/ma-user/work/mindyolo-master/mindyolo/models/model_factory.py", line 30, in create_model
model = create_fn(**model_args, **kwargs)
File "/home/ma-user/work/mindyolo-master/mindyolo/models/yolov4.py", line 41, in yolov4
model = YOLOv4(cfg=cfg, in_channels=in_channels, num_classes=num_classes, **kwargs)
File "/home/ma-user/work/mindyolo-master/mindyolo/models/yolov4.py", line 24, in init
self.model = build_model_from_cfg(model_cfg=cfg, in_channels=ch, num_classes=nc, sync_bn=sync_bn)
File "/home/ma-user/work/mindyolo-master/mindyolo/models/model_factory.py", line 45, in build_model_from_cfg
return Model(**kwargs)
File "/home/ma-user/work/mindyolo-master/mindyolo/models/model_factory.py", line 52, in init
deepcopy(model_cfg), ch=[in_channels], nc=num_classes, sync_bn=sync_bn
File "/home/ma-user/work/mindyolo-master/mindyolo/models/model_factory.py", line 193, in parse_model
m_ = nn.SequentialCell([m(*args, **kwargs) for _ in range(n)]) if n > 1 else m(*args, **kwargs)
File "/home/ma-user/work/mindyolo-master/mindyolo/models/layers/bottleneck.py", line 12, in init
c_ = int(c2 * e)  # hidden channels
TypeError: unsupported operand type(s) for *: 'int' and 'Mish'
Describe the expected behavior
Steps to reproduce the issue

python ./deploy/export.py --per_batch_size=1 --file_format AIR --config ./configs/yolov4/yolov4.yaml --weight ./ckpt/yolov4-cspdarknet53_320e_map454-50172f93.ckpt

Related log / screenshot
Special notes for this issue

传入参数没有对齐导致，已经修改为key=value形式传入act参数


write_fillable_pdf() not saving?

Essentially, it seems to be able to fill the PDF with the data dictionary which I specified. Sound like it's working okay in this instance, right?
Afterwards, I open the PDF which I have modifed and I see that adobe treats the file as if it hasn't been saved? The save button at the top of Adobe Acrobat Pro is pressable after running my PDF through the write_fillable_pdf() function.
What's more weird is the fact that it changes the PDF version all the way down to 1.4, instead of 1.7 like how I used to have it.
Is this a known issue?

Same thing


Warning 357 Could not resolve this reference. Could not locate the assembly "nunit.framework". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.  C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1697    5   Stanford.NLP.POSTagger.FSharp.Tests
Warning 443 Could not resolve this reference. Could not locate the assembly "nunit.framework". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.  C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1697    5   Stanford.NLP.Segmenter.FSharp.Tests
Warning 50  Could not resolve this reference. Could not locate the assembly "stanford-corenlp-3.5.2". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.   C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1697    5   Stanford.NLP.CoreNLP.FSharp.Tests
Warning 210 Could not resolve this reference. Could not locate the assembly "stanford-ner". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1697    5   Stanford.NLP.NER.FSharp.Tests
Warning 7   Could not resolve this reference. Could not locate the assembly "stanford-parser". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.  Stanford.NLP.Parser.CSharp
Warning 254 Could not resolve this reference. Could not locate the assembly "stanford-parser". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.  C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1697    5   Stanford.NLP.Parser.FSharp.Tests
Warning 363 Could not resolve this reference. Could not locate the assembly "stanford-postagger-3.5.2". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1697    5   Stanford.NLP.POSTagger.FSharp.Tests
Warning 451 Could not resolve this reference. Could not locate the assembly "stanford-segmenter-3.5.2". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1697    5   Stanford.NLP.Segmenter.FSharp.Tests
Warning 49  Could not resolve this reference. Could not locate the assembly "xom". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.  C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets 1697    5   Stanford.NLP.CoreNLP.FSharp.Tests
Warning 387 The referenced component 'ejml-0.23' could not be found.    Stanford.NLP.Parser.CSharp
Warning 389 The referenced component 'IKVM.AWT.WinForms' could not be found.    Stanford.NLP.Parser.CSharp
Warning 390 The referenced component 'IKVM.OpenJDK.Beans' could not be found.   Stanford.NLP.Parser.CSharp
Warning 391 The referenced component 'IKVM.OpenJDK.Charsets' could not be found.    Stanford.NLP.Parser.CSharp
Warning 392 The referenced component 'IKVM.OpenJDK.Cldrdata' could not be found.    Stanford.NLP.Parser.CSharp
Warning 393 The referenced component 'IKVM.OpenJDK.Corba' could not be found.   Stanford.NLP.Parser.CSharp
Warning 394 The referenced component 'IKVM.OpenJDK.Core' could not be found.    Stanford.NLP.Parser.CSharp
Warning 395 The referenced component 'IKVM.OpenJDK.Jdbc' could not be found.    Stanford.NLP.Parser.CSharp
Warning 396 The referenced component 'IKVM.OpenJDK.Localedata' could not be found.  Stanford.NLP.Parser.CSharp
Warning 397 The referenced component 'IKVM.OpenJDK.Management' could not be found.  Stanford.NLP.Parser.CSharp
Warning 398 The referenced component 'IKVM.OpenJDK.Media' could not be found.   Stanford.NLP.Parser.CSharp
Warning 399 The referenced component 'IKVM.OpenJDK.Misc' could not be found.    Stanford.NLP.Parser.CSharp
Warning 400 The referenced component 'IKVM.OpenJDK.Naming' could not be found.  Stanford.NLP.Parser.CSharp
Warning 401 The referenced component 'IKVM.OpenJDK.Nashorn' could not be found.     Stanford.NLP.Parser.CSharp
Warning 402 The referenced component 'IKVM.OpenJDK.Remoting' could not be found.    Stanford.NLP.Parser.CSharp
Warning 403 The referenced component 'IKVM.OpenJDK.Security' could not be found.    Stanford.NLP.Parser.CSharp
Warning 404 The referenced component 'IKVM.OpenJDK.SwingAWT' could not be found.    Stanford.NLP.Parser.CSharp
Warning 405 The referenced component 'IKVM.OpenJDK.Text' could not be found.    Stanford.NLP.Parser.CSharp
Warning 406 The referenced component 'IKVM.OpenJDK.Tools' could not be found.   Stanford.NLP.Parser.CSharp
Warning 407 The referenced component 'IKVM.OpenJDK.Util' could not be found.    Stanford.NLP.Parser.CSharp
Warning 408 The referenced component 'IKVM.OpenJDK.XML.API' could not be found.     Stanford.NLP.Parser.CSharp
Warning 409 The referenced component 'IKVM.OpenJDK.XML.Bind' could not be found.    Stanford.NLP.Parser.CSharp
Warning 410 The referenced component 'IKVM.OpenJDK.XML.Crypto' could not be found.  Stanford.NLP.Parser.CSharp
Warning 411 The referenced component 'IKVM.OpenJDK.XML.Parse' could not be found.   Stanford.NLP.Parser.CSharp
Warning 412 The referenced component 'IKVM.OpenJDK.XML.Transform' could not be found.   Stanford.NLP.Parser.CSharp
Warning 413 The referenced component 'IKVM.OpenJDK.XML.WebServices' could not be found.     Stanford.NLP.Parser.CSharp
Warning 414 The referenced component 'IKVM.OpenJDK.XML.XPath' could not be found.   Stanford.NLP.Parser.CSharp
Warning 416 The referenced component 'IKVM.Runtime' could not be found.     Stanford.NLP.Parser.CSharp
Warning 415 The referenced component 'IKVM.Runtime.JNI' could not be found.     Stanford.NLP.Parser.CSharp
Warning 388 The referenced component 'stanford-parser' could not be found.  Stanford.NLP.Parser.CSharp

You need to run build.cmd in the root folder to build everything first time.

Hi Sergey,
Thanks that helped.  After Paket was done, there were several dialog boxes from the F# type security manager asking me to enable various F# types.  I clicked "Enable" on each of them and then was able to build.
I ran the sample project Standford.NLP.Parser.CSharp.  It appeared to work, parsing a single sentence and dumping the parts-of-speech tree to the console.  Then it exited.  However, I did see this list of Exceptions in the output window:
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_<IP_ADDRESS>__b77a5c561934e089\mscorlib.dll'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities\<IP_ADDRESS>__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.dll'. Cannot find or open the PDB file.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Windows.Forms.dll'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a\System.Drawing.dll'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.dll'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities.Sync\<IP_ADDRESS>__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll'. Cannot find or open the PDB file.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.Debugger.Runtime\<IP_ADDRESS>__b03f5f7f11d50a3a\Microsoft.VisualStudio.Debugger.Runtime.dll'.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\Users\Robert\Documents\GitHub\Stanford.NLP.NET\samples\Stanford.NLP.Parser.CSharp\bin\Debug\Stanford.NLP.Parser.CSharp.vshost.exe'. Cannot find or open the PDB file.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Core.dll'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Xml.Linq.dll'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Data.DataSetExtensions.dll'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a\Microsoft.CSharp.dll'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Data.dll'. Cannot find or open the PDB file.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Xml.dll'. Symbols loaded.
The thread 0x1f04 has exited with code 259 (0x103).
The thread 0x1b88 has exited with code 259 (0x103).
The thread 0x271c has exited with code 0 (0x0).
The thread 0x3268 has exited with code 259 (0x103).
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\Users\Robert\Documents\GitHub\Stanford.NLP.NET\samples\Stanford.NLP.Parser.CSharp\bin\Debug\Stanford.NLP.Parser.CSharp.exe'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\Users\Robert\Documents\GitHub\Stanford.NLP.NET\samples\Stanford.NLP.Parser.CSharp\bin\Debug\stanford-parser.dll'. Module was built without symbols.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\Users\Robert\Documents\GitHub\Stanford.NLP.NET\samples\Stanford.NLP.Parser.CSharp\bin\Debug\IKVM.OpenJDK.Core.dll'. Module was built without symbols.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\Users\Robert\Documents\GitHub\Stanford.NLP.NET\samples\Stanford.NLP.Parser.CSharp\bin\Debug\IKVM.Runtime.dll'. Module was built without symbols.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a\System.Configuration.dll'. Symbols loaded.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\Users\Robert\Documents\GitHub\Stanford.NLP.NET\samples\Stanford.NLP.Parser.CSharp\bin\Debug\IKVM.OpenJDK.Text.dll'. Module was built without symbols.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\Users\Robert\Documents\GitHub\Stanford.NLP.NET\samples\Stanford.NLP.Parser.CSharp\bin\Debug\IKVM.OpenJDK.Util.dll'. Module was built without symbols.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\Users\Robert\Documents\GitHub\Stanford.NLP.NET\samples\Stanford.NLP.Parser.CSharp\bin\Debug\IKVM.OpenJDK.Localedata.dll'. Module was built without symbols.
'Stanford.NLP.Parser.CSharp.vshost.exe' (CLR v4.0.30319: Stanford.NLP.Parser.CSharp.vshost.exe): Loaded 'C:\Users\Robert\Documents\GitHub\Stanford.NLP.NET\samples\Stanford.NLP.Parser.CSharp\bin\Debug\ejml-0.23.dll'. Module was built without symbols.

The thread 0x1a64 has exited with code 259 (0x103).
The program '[912] Stanford.NLP.Parser.CSharp.vshost.exe' has exited with code 0 (0x0).
The program '[912] Stanford.NLP.Parser.CSharp.vshost.exe: Program Trace' has exited with code 0 (0x0).

@volhav What do you know about these exceptions in C# project?

Any news on this issue?

@roschler I cannot understand where all these exceptions from ...
Build log on AppVeyor is clear enough https://ci.appveyor.com/project/sergey-tihon/stanford-nlp-net

@sergey-tihon They happen when I run the test project and it parses a sentence.  The execution of build.cmd executed properly.  But when I run the test project, I get the long list of Exceptions above.

I cannot reproduce this neither on my machine or on AppVeyour
https://ci.appveyor.com/project/sergey-tihon/stanford-nlp-net/build/<IP_ADDRESS>
there are couple knows warnings left (related to slf4j) and track them in separate issue #65
Close this for now


koji_promote: fixes for logging upload progress

LGTM

Blocksize change looks good as well

Coverage decreased (-0.003%) to 87.316% when pulling bab7f135401ef18037e5ba8e04d7c205154a31f2 on koji-promote-upload-logging into d408c587d710cd34fb6c98ef956def3b0147f8e5 on master.

Coverage decreased (-0.003%) to 87.316% when pulling 7eda91cf70d1790f42e1954811dea56b7a50c5db on koji-promote-upload-logging into d408c587d710cd34fb6c98ef956def3b0147f8e5 on master.


Update README.md

Minor grammatical fixes
Converted headings to "sentence case" where only the first letter is capitalized; this is the preferred style for Nest documentation
I left all "Thread" instances as "Thread" and "OpenThread" as "OpenThread". I would like to make sure there are not instances where "Thread" is intended to refer to "OpenThread".

Minus the License changes, all suggestions LGTM!

LGTM 👍


Verified and modified instructions.

I've added a bunch of changes. That's all I got for now however I will test later this or next week more distros and provide working instructions. I've added a check/x section at the top to track which distros I have working.

Awesome changes! Merging them. Thanks for excellent work


Image Build Fails on Podman

Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
Currently, attempting to build an image for Podman fails, producing the following error:
$ cargo build-docker-image $target --engine podman
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/xtask build-docker-image aarch64-linux-android --engine podman`
[cross] note: Build aarch64-linux-android for x86_64-unknown-linux-gnu
Error: unable to parse value provided `` to --cache-from: invalid repo "type=registry,ref=ghcr.io/cross-rs/aarch64-linux-android:main": must contain registry and repository: invalid reference format
Error:
   0: `podman buildx build --platform linux/amd64 --load --pull --cache-from 'type=registry,ref=ghcr.io/cross-rs/aarch64-linux-android:main' --tag ghcr.io/cross-rs/aarch64-linux-android:local --label 'org.cross-rs.for-cross-target=aarch64-linux-android' --label 'org.cross-rs.runs-with=x86_64-unknown-linux-gnu' -f /home/ahuszagh/git/cross/docker/Dockerfile.aarch64-linux-android --progress auto .` failed with exit status: 125

Location:
   /rustc/a8314ef7d0ec7b75c336af2c9857bfaf43002bfc/library/core/src/convert/mod.rs:55

What target(s) are you cross-compiling for?
aarch64-linux-android
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[ ] Windows
[X] Linux / BSD
[ ] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[ ] docker
[X] podman
[ ] other container engine (specify in description)

cross version
cross 0.2.4 (d92e563cdded42aa5468746fc821f9b795880ce2)
Additional information / notes
Removing the --cache-from step fixes the issue. We should probably also add a build image step for podman, using the fast image build (x86_64-unknown-linux-gnu) to avoid this issue in the future. The podman version is 4.2.0.

It seems --cache-from only supports a repository using podman, and this might be true for other container engines. type=registry might be implicit. type=registry is the default for docker, so we should be able to omit it.

I don't think there is a situation where not being explicit about it is bad. Removing the explicitness sounds good 👍🏼


backup: introduce "starting" state

To make the backup state machine more clear, this commit introduces a new "starting" state to the existing "in_progress," "complete," and "error" states.
Previously, a backup task consisted of preparation, backupstore initialization, and backup execution, with "in_progress" starting from backup execution. However, this meant that any stuck caused by an NFS connection during backupstore initialization could not be detected by the Longhorn manager. With the new "starting" state, the backup process will have a more complete state machine, ensuring better tracking and monitoring of the backup process.
Longhorn/longhorn#5662

@Mergifyio backport v1.4.x

@Mergify v1.4.x

@mergify backport v1.4.x


update build

What changes were proposed in this pull request
Issue Number: close:#2695

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (yes / no)

Thanks for your contribution, I will review it later.

The bug has been fixed in the latest code, please see: https://github.com/apache/incubator-streampark/pull/2697

Thanks for your contribution, there are some checkstyle issue need to be resolved. you can run the command:
mvn spotless:apply

@wolfboys PTAL,thanks.

@zhoulii PTAL,thanks.

@wolfboysPTAL,thanks.


Make logging after success in jobset more apparent

tools/run_tests/artifacts/artifact_targets.py is used in the artifact build process to create the relevant jobset.JobSpec, but currently prints the console output only if the build fails.
jobset.JobSpec has a verbose_success flag that is used to print the process output even if it ends in PASSED, but is currently not easily perceivable and is hard to find, making it very difficult to debug PASSED/SUCCESS cases. Make the flag more apparent by adding it as parameters to jobspec creation methods in artifact_targets.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Merging with the thought that the test failures are not related to the content of this change.


Typo in sisimai/rhost/yahooinc.go

https://github.com/sisimai/p5-sisimai/issues/546

%  find sisimai -type f -exec grep -i 'notcomplaintrfc' {} +
sisimai/rhost/yahooinc.go:			"notcomplaintrfc": []string{"headers are not rfc compliant"},

The bug has been fixed at commit f79072ce9ce722e5a629d9b92e95c6bbbf89c28a


Race condition in ev_epollex_linux.cc for client connections

What version of gRPC and what language are you using?
v1.20.1
What operating system (Linux, Windows,...) and version?
Linux Debian 8 and Linux Debian 9
What runtime / compiler are you using (e.g. python version or version of gcc)
clang 3.7
What did you do?
I have a client that attempts to connect to a server. If the connection is unsuccessful the client tries again 2 seconds later.
What did you expect to see?
I expected the client to connect to the server on the first try.
What did you see instead?
Occasionally the client times out on the connection attempt. Sometimes multiple times in a row.
On the server side it looks like this:
D0525 16:30:14.790699091 21074 tcp_posix.cc:1258] cannot set inq fd=154 errno=92
D0525 16:30:16.791713096 21074 tcp_posix.cc:1258] cannot set inq fd=157 errno=92
D0525 16:30:18.791578080 21074 tcp_posix.cc:1258] cannot set inq fd=158 errno=92
D0525 16:30:20.791485232 21074 tcp_posix.cc:1258] cannot set inq fd=159 errno=92
D0525 16:30:22.791244970 21074 tcp_posix.cc:1258] cannot set inq fd=160 errno=92

Looking at tcpdump on the server side, I see that for every "cannot set inq" above:

the TCP handshake succeeds
roughly 2 seconds after the handshake, the client sends an FIN,ACK followed by a RST,ACK.
Shortly after that (within a couple milliseconds) the client establishes another connection
possibly repeat cycle.

Looking at strace, it looks to me like the client calls connect() and then subsequently adds it to an edge-triggered epoll descriptor.
I suspect this is racy because if the server establishes the connection quickly enough then you lose the event.
I added the following as a test. This causes the client to fail connecting indefinitely:

diff --git a/third_party/grpc/src/core/lib/iomgr/ev_epollex_linux.cc b/third_party/grpc/src/core/lib/iomgr/ev_epollex_linux.cc
index 01be46c..1a758d3 100644
--- a/third_party/grpc/src/core/lib/iomgr/ev_epollex_linux.cc
+++ b/third_party/grpc/src/core/lib/iomgr/ev_epollex_linux.cc
@@ -635,6 +635,7 @@ static grpc_error* pollable_add_fd(pollable* p, grpc_fd* fd) {
   ev_fd.data.ptr = reinterpret_cast<void*>(reinterpret_cast<intptr_t>(fd) |
                                            (fd->track_err ? 2 : 0));
   GRPC_STATS_INC_SYSCALL_EPOLL_CTL();
+  sleep(1);
   if (epoll_ctl(epfd, EPOLL_CTL_ADD, fd->fd, &ev_fd) != 0) {
     switch (errno) {
       case EEXIST:

Alternatively, when I ran the following inside the bazel sandbox the connections succeeded 100% of the time. This is without the patch above.

# https://stackoverflow.com/questions/40196730/simulate-network-latency-on-specific-port-using-tc
/sbin/tc qdisc add dev lo root handle 1: prio priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
/sbin/tc qdisc add dev lo parent 1:2 handle 20: netem delay 150ms
/sbin/tc filter add dev lo parent 1:0 protocol ip u32 match ip sport 51053 0xffff flowid 1:2

Port 51503 is the port I happen to be using for this experiment.
Anything else we should know about your project / environment?
Problem was exposed in a LAN environment.
It can be reproduced in a sandboxed bazel test.
Will update the ticket when I have a standalone test I can post.

I'm having trouble creating a stripped down test case so I am posting strace logs in the meantime.
The following file shows a single connect() timeout on the client side.
The expection was that there would be no timeout.
bug-report-grpc.log
The following file shows two subsequent connect() calls timing out even though the first one should have succeeded.
bug-report-grpc-2.log
Here you can see the connection being accepted ~1s after the connect() call.
bug-report-grpc-success.log
Note that these are all bazel test logs.
The first set of strace messages in each file is from the client.
The second set of strace messages in each file is from the server.

github_grpc_bug_19161_test_case.tar.gz
Here's a minimal test case that I hope illustrates the issue.
The knob is in bug_test.sh:
# Change this to 1 and the test will rarely fail.
# Change this to 2 and the test will always fail.
# Change this to 3 and the test will always pass.
sleep 1

The test pass/fail criterion is how many connections the server sees being established. It should always be 1 connection. If it's not exactly 1 connection then the test is considered a failure.

Cool find

I'm guessing we need something like this to fix it - https://github.com/grpc/grpc/pull/19426

@philsc does #19426 solve the issue for you?

Thanks @yashykt . I'll give that a try shortly.

I can see that the epoll_ctl happens before the connect, but it still decides to shut down the connection even though the server responded with success:
strace: Process 29 attached
I0625 21:21:44.521260069      21 subchannel.cc:920]          Failed to connect to channel, retrying
[pid    21]<PHONE_NUMBER>.521800 socket(AF_INET6, SOCK_STREAM, IPPROTO_IP) = 7
[pid    21]<PHONE_NUMBER>.521929 setsockopt(7, SOL_IPV6, IPV6_V6ONLY, [0], 4) = 0
[pid    21]<PHONE_NUMBER>.522426 setsockopt(7, SOL_TCP, TCP_NODELAY, [1], 4) = 0
[pid    21]<PHONE_NUMBER>.522522 getsockopt(7, SOL_TCP, TCP_NODELAY, [1], [4]) = 0
[pid    21]<PHONE_NUMBER>.522610 setsockopt(7, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
[pid    21]<PHONE_NUMBER>.522693 getsockopt(7, SOL_SOCKET, SO_REUSEADDR, [1], [4]) = 0
Adding FD
[pid    21]<PHONE_NUMBER>.522911 epoll_ctl(5, EPOLL_CTL_ADD, 7, {EPOLLIN|EPOLLOUT|EPOLLEXCLUSIVE|EPOLLET, {u32=4173390720, u64=93836323906432}}) = 0
[pid    21]<PHONE_NUMBER>.523006 connect(7, {sa_family=AF_INET6, sin6_port=htons(50051), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=htonl(0), sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress)
[pid    29]<PHONE_NUMBER>.617975 shutdown(7, SHUT_RDWR) = 0
[pid    29]<PHONE_NUMBER>.618238 close(7)  = 0
I0625 21:21:46.618470696      29 subchannel.cc:960]          Connect failed: {"created":"@1561497706.618166624","description":"Failed to connect to remote host: FD Shutdown","file":"external/com_github_grpc_grpc/src/core/lib/iomgr/lockfree_event.cc","file_line":194,"os_error":"Timeout occurred","referenced_errors":[{"created":"@1561497706.617923024","description":"connect() timed out","file":"external/com_github_grpc_grp
c/src/core/lib/iomgr/tcp_client_posix.cc","file_line":119}],"target_address":"ipv6:[::1]:50051"}
I0625 21:21:46.618968281      29 subchannel.cc:895]          Subchannel 0x5557f8bae6c0: Retry immediately
I0625 21:21:46.619124869      29 subchannel.cc:920]          Failed to connect to channel, retrying
[pid    29]<PHONE_NUMBER>.619452 socket(AF_INET6, SOCK_STREAM, IPPROTO_IP) = 7
[pid    29]<PHONE_NUMBER>.619557 setsockopt(7, SOL_IPV6, IPV6_V6ONLY, [0], 4) = 0
[pid    29]<PHONE_NUMBER>.619962 setsockopt(7, SOL_TCP, TCP_NODELAY, [1], 4) = 0
[pid    29]<PHONE_NUMBER>.620053 getsockopt(7, SOL_TCP, TCP_NODELAY, [1], [4]) = 0
[pid    29]<PHONE_NUMBER>.620136 setsockopt(7, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
[pid    29]<PHONE_NUMBER>.620226 getsockopt(7, SOL_SOCKET, SO_REUSEADDR, [1], [4]) = 0
Adding FD
[pid    29]<PHONE_NUMBER>.620394 epoll_ctl(5, EPOLL_CTL_ADD, 7, {EPOLLIN|EPOLLOUT|EPOLLEXCLUSIVE|EPOLLET, {u32=4173390720, u64=93836323906432}}) = 0
[pid    29]<PHONE_NUMBER>.620475 connect(7, {sa_family=AF_INET6, sin6_port=htons(50051), inet_pton(AF_INET6, "::ffff:<IP_ADDRESS>", &sin6_addr), sin6_flowinfo=htonl(0), sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress)
[pid    21]<PHONE_NUMBER>.514068 epoll_wait(5, [{EPOLLIN|EPOLLOUT, {u32=4173390720, u64=93836323906432}}], 100, 0) = 1
[pid    21]<PHONE_NUMBER>.514226 getsockopt(7, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
[pid    21]<PHONE_NUMBER>.514385 setsockopt(7, SOL_TCP, 0x24 /* TCP_??? */, [1], 4) = -1 ENOPROTOOPT (Protocol not available)

Looks like there's no call to epoll_wait between the two connection attempts.

Sorry for the super late reply. I got pulled into some higher priority work.
I think the reason why epoll_wait did not happen is because the DEFAULT_POLL_INTERVAL for the backup poller is 5 seconds. I believe if you increase the wait time, we won't run into this. I'll try running the tests myself to verify.

Ah, that's fair. You're right. It does work if I increase the wait time.
Still seems odd to me that a connect() is invoked without adding it to the list of epoll FDs to watch.
But yeah, this is perfect for what we need.
Thanks a ton!


Add new repository for the web app

I would like the commit the current web app code into its own repo like "germany-says-welcome-webapp". That code could be deployed to "dev.germany-says-welcome.de" later.

Added repo (germany-says-welcome-webapp)[https://github.com/socialc0de/germany-says-welcome-webapp].


import both name and members from module

Example:
import React, {Component} from 'react';
gives error:
Identifier Component could not resolve name
when using the Component variable.
It seems to be supported in ES6: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import
modules are reported as done in #560 .

Thanks for the report! This will be fixed when https://github.com/facebook/flow/pull/600 lands
(closing in favor of tracking that PR)


expense tracker app running issue fixed

Title and Issue number
Expense Tracker
Close #4143
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[x] I have fixed the file structure and the app not running issue
[x] I have added addtional features and the UI is improved
[x] I have updated the readme file with the screenshots.

Hello @MohitGupta121 , Sir please review my PR and also add a label for gssoc'23

can't able to make changes and I am closing this PR and I will make the desired changes in new PR.


chore: release 1.7.1

:robot: I have created a release *beep* *boop*
1.7.1 (2022-02-24)
Bug Fixes

cannot import URL from url package (b89721e)
esm parse failed (b95a97c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/keq-request/keq/releases/tag/v1.7.1 :sunflower:


Add an alignment option to position images within sprite

It could simplify the background-positioning of sprite images in certain cases if there was an "alignment" option that controls the alignment of images within the sprite (e.g. horizontally centered images within a vertical layed out sprite). See issue #15 for further details.

As of release v1.0.6 grunt-svg-sprite now supports extended alignment options.


npx react-native init fails at 'Installing cocoapods dependencies'

OS: MacOS 10.15.7
When I run npx react-native init demo-react-project, everything goes ok till 'Installing cocoapods dependencies' and then it stays on it for a while, then it consumes all the available RAM (20GB) and hangs the computer.
I tried going into the /ios folder and running 'pod install --verbose' and the same thing happens at 'Generating deterministic UUIDs'.
Tried this on two different mac machines.

should be resolved: https://github.com/facebook/flipper/issues/2248

should be resolved: facebook/flipper#2248

Isn't working still.

install! 'cocoapods', :deterministic_uuids => false
Have you tried adding this in your podfile? It should be above all the target-related code, I placed this right below the  platform :ios, '13.0'


No such file or directory: 'peer_urls.txt'

Looks like installing from pip doesn't provide peer_urls.txt, which is required in latest skepticoin version.

I will provide a fix for this one. For the time being, this is the content of peer_urls.txt:
https://pastebin.com/raw/CcfPX9mS
https://skepticoin.s3.amazonaws.com/peers.json


feat: Added the rendercv_settings block

As discussed in #146, A new block named rendercv_settings is added.
Usage of this block:
rendercv_settings:
  output_folder_name: 'str'
  use_local_latex_command: 'str'
  pdf_path: 'str'
  latex_path: 'str'
  html_path: 'str'
  png_path: 'str'
  markdown_path: 'str'
  no_html: false
  no_markdown: false
  no_png: false

Each and every property in this block is direct equivalent implementation of the cli option.
fixes: #146

Thanks a lot for your great work! It looks really good. I've included some comments.
I'm quite tied up these days, so I might not be able to respond immediately, but I'll get back to you as soon as I can.

When everything is all set, we need to write tests for every function created. Overriding the settings from YAML with CLI should be tested, too.

I'll Use the comments as check-boxes and resolve them as I implement them. Is it okay? Once I resolve all the comments I'll use the ready for review.

@sinaatalay  Can you please review the changes now? I think most of the issue is resolved. and after your answer on the unresolved comments. I'll update and make the pr final.

Thank you! I have made a few more comments; then it will be ready. But we need tests. If you don't want to implement tests, I can do that too. If you want to work on it, let me know.

It would be very helpful. If you can implement testing as I'm not familiar with testing tools used in this project. But I'll surely can do documentation. All the change is implemented now. Only the documentation is remaining.

Let me know when you have finished the pull request following our last discussion.

@sinaatalay Please review the documentation. and overall code structure. I think the pull request is ready for merging now.


How to debug shader?

Checklist

[x] I've read the README
[x] I've searched for existing GitHub issues

Like the sample demo of apple's document.
I want to see every texel value,every variable value in shader,how can i do that?

https://developer.apple.com/documentation/metal/shader_authoring/developing_and_debugging_metal_shaders

How to make it in metalpetal?

I don't think you need to do anything special with MetalPetal.

You mean metalpetal does not suppurt shader debug?

I mean I don't think you need to do anything special to enable shader debugging with MetalPetal.

Debugging with the demo.

I checked it again,it works.Maybe something wrong with my project.

I found that what I can only see is the display stage.
What should I do if I want to debug shader in Intermediate stage,or some filter's shader in filter chain?


Server shall send empty object  for triggerData if client or webhook not sending it.

currentlty it is sending triggerData:null . so validation on rts is returning error

Hey team! Please add your planning poker estimate with Zenhub @ayushpahwa @nsarupr


refactor(execution): split get_additional_os_resources

This change is

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

Comparison is base (e93efdb) 71.32% compared to head (12bbfbb) 70.46%.

Files
Patch %
Lines

...es/blockifier/src/transaction/transaction_utils.rs
50.00%
0 Missing and 2 partials :warning:

Additional details and impacted files
@@                                     Coverage Diff                                      @@
##           ori/blockifier/ep_syscall_counter/add_ep_syscall_counter    #1411      +/-   ##
============================================================================================
- Coverage                                                     71.32%   70.46%   -0.86%
============================================================================================
  Files                                                            59       59
  Lines                                                          8080     7724     -356
  Branches                                                       8080     7724     -356
============================================================================================
- Hits                                                           5763     5443     -320
+ Misses                                                         1907     1853      -54
- Partials                                                        410      428      +18

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


Make configuration command more visible

@abellotti please review

Ok by me. @kbrock ?

@romanblanco did you test from boot?
I'm pretty sure they don't use cat
if you have, then LGTM

@kbrock I did.

Only when I tried it in KVM, the color is not green, but still better than before:

About issue.template -- i don't know where to find this message, to make sure it works.


⚠ Bofrost.lu has degraded performance

In 8ed1964, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1171 ms

Resolved: Bofrost.lu performance has improved in ccde820.


waitForFunction chain throws an error

I get this error : "Method VerumConsilium\Browsershot\PDF::waitForFunction() does not exists", when I ca;; waitForFunction along with other functions.
You have written that all of the chains of Browsershot would work fine, but this one doesn't

The package was using an outdated version of Browsershot

I got it.! thank you so much for your reply.!


Remove code repetition

Add a file like base-uploader.html for to-json and to-spreadsheet to remove some of the duplicate code.
This could be done in the last PR to merge from the list:

[x] #96
[x] #87
[x] #67

closed by #119


Can vary_length be used with the stable branch?

Hello.
I would like to use the vary_length option to refine my binder.
It seems that the argument is not accepted by the stable branch but works with the dev branch.
I can change the script to accept it but I wanted to know if there is something wrong with using this with the stable branch and that's why this option has not been enabled in the stable branch.
I would really appreciate your suggestions.
Best,
Amin.

Hi, we have seen some rare, strange errors (probably some edge cases) when using the vary_length option - so you can use it, but the program may crash rarely! This is why we have not enabled this option in the stable branch.


Add --importmap option to use deno import maps

@verdel path to chart is replaced in output for better developer experience
https://github.com/CSSSR/helm-deno/blob/1e5d9fbcc28c9a1a413049179bd6bdaac7a12f49/src/index.ts#L141-L150


Building for 'visionOS-simulator', but linking in object file FIRAAdExposureReporter.o built for 'iOS-simulator'

Description
Hi,
I need to have support for iPhone, iPad and now for visionOS. I use CocoaPods. I have Xcode 15.2
I have applied rivera-ernesto workaround from https://github.com/CocoaPods/CocoaPods/issues/12094 and my Podfile is per below
source 'https://github.com/CocoaPods/Specs.git'
platform :ios,                              '15.0'
use_frameworks!
target 'XYZ' do
pod 'Firebase',                             '~> 10.22.0'
pod 'FirebaseDatabase',                     '~> 10.22.0'
pod 'FirebaseCore',                         '~> 10.22.0'
pod 'FirebaseAuth',                         '~> 10.22.0'
pod 'FirebaseStorage',                      '~> 10.22.0'
pod 'FirebaseAppCheck',                     '~> 10.22.0'
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
            # Upgrade the minimum version
            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'

            # Activate VisionOS support for all Pods
            config.build_settings['SUPPORTED_PLATFORMS'] = 'iphoneos iphonesimulator xros xrsimulator' # Includes VisionOS (xros) and its simulator (xrsimulator)
            config.build_settings['TARGETED_DEVICE_FAMILY'] = '1,2,7' # Incorporate device family '7' for VisionOS
    end

if target.name == 'Cache'
  target.build_configurations.each do |config|

            level = '-Osize'
            config.build_settings['SWIFT_OPTIMIZATION_LEVEL'] = level
            puts "Set #{target.name} #{config.name} to Optimization Level #{level}"

    end
end

end
end
I do not have a visionpro yet, so I need to use the simulator.
It throws
Building for 'visionOS-simulator', but linking in object file (/Users/aaa/Library/Developer/Xcode/DerivedData15/XYZ-azxtzecwtbuysxhagymjaoytbgqj/Build/Products/Debug-xrsimulator/XCFrameworkIntermediates/FirebaseAnalytics/AdIdSupport/FirebaseAnalytics.framework/FirebaseAnalytics[arm64]3) built for 'iOS-simulator'
I do not use Analytics at all, but I have been told it comes with Core.
How can get this resolved please? Can't integrate the new platform otherwise.
Reproducing the issue
No response
Firebase SDK Version
10.22
Xcode Version
15.2
Installation Method
CocoaPods
Firebase Product(s)
All
Targeted Platforms
iOS, visionOS
Relevant Log Output
Building for 'visionOS-simulator', but linking in object file (/Users/aaa/Library/Developer/Xcode/DerivedData15/XYZ-azxtzecwtbuysxhagymjaoytbgqj/Build/Products/Debug-xrsimulator/XCFrameworkIntermediates/FirebaseAnalytics/AdIdSupport/FirebaseAnalytics.framework/FirebaseAnalytics[arm64][3](FIRAAdExposureReporter.o)) built for 'iOS-simulator'

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

PODS:
  - AppCheckCore (10.18.1):
    - GoogleUtilities/Environment (~> 7.11)
    - PromisesObjC (~> 2.3)
  - Firebase (10.22.0):
    - Firebase/Core (= 10.22.0)
  - Firebase/Core (10.22.0):
    - Firebase/CoreOnly
    - FirebaseAnalytics (~> 10.22.0)
  - Firebase/CoreOnly (10.22.0):
    - FirebaseCore (= 10.22.0)
  - FirebaseAnalytics (10.22.0):
    - FirebaseAnalytics/AdIdSupport (= 10.22.0)
    - FirebaseCore (~> 10.0)
    - FirebaseInstallations (~> 10.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.11)
    - GoogleUtilities/MethodSwizzler (~> 7.11)
    - GoogleUtilities/Network (~> 7.11)
    - "GoogleUtilities/NSData+zlib (~> 7.11)"
    - nanopb (< 2.30911.0, >= 2.30908.0)
  - FirebaseAnalytics/AdIdSupport (10.22.0):
    - FirebaseCore (~> 10.0)
    - FirebaseInstallations (~> 10.0)
    - GoogleAppMeasurement (= 10.22.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.11)
    - GoogleUtilities/MethodSwizzler (~> 7.11)
    - GoogleUtilities/Network (~> 7.11)
    - "GoogleUtilities/NSData+zlib (~> 7.11)"
    - nanopb (< 2.30911.0, >= 2.30908.0)
  - FirebaseAppCheck (10.22.0):
    - AppCheckCore (~> 10.18)
    - FirebaseAppCheckInterop (~> 10.17)
    - FirebaseCore (~> 10.0)
    - GoogleUtilities/Environment (~> 7.8)
    - PromisesObjC (~> 2.1)
  - FirebaseAppCheckInterop (10.23.0)
  - FirebaseAuth (10.22.0):
    - FirebaseAppCheckInterop (~> 10.17)
    - FirebaseCore (~> 10.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.8)
    - GoogleUtilities/Environment (~> 7.8)
    - GTMSessionFetcher/Core (< 4.0, >= 2.1)
    - RecaptchaInterop (~> 100.0)
  - FirebaseAuthInterop (10.23.0)
  - FirebaseCore (10.22.0):
    - FirebaseCoreInternal (~> 10.0)
    - GoogleUtilities/Environment (~> 7.12)
    - GoogleUtilities/Logger (~> 7.12)
  - FirebaseCoreExtension (10.23.0):
    - FirebaseCore (~> 10.0)
  - FirebaseCoreInternal (10.23.0):
    - "GoogleUtilities/NSData+zlib (~> 7.8)"
  - FirebaseDatabase (10.22.0):
    - FirebaseAppCheckInterop (~> 10.17)
    - FirebaseCore (~> 10.0)
    - FirebaseSharedSwift (~> 10.0)
    - leveldb-library (~> 1.22)
  - FirebaseInstallations (10.23.0):
    - FirebaseCore (~> 10.0)
    - GoogleUtilities/Environment (~> 7.8)
    - GoogleUtilities/UserDefaults (~> 7.8)
    - PromisesObjC (~> 2.1)
  - FirebaseSharedSwift (10.23.0)
  - FirebaseStorage (10.22.0):
    - FirebaseAppCheckInterop (~> 10.0)
    - FirebaseAuthInterop (~> 10.0)
    - FirebaseCore (~> 10.0)
    - FirebaseCoreExtension (~> 10.0)
    - GTMSessionFetcher/Core (< 4.0, >= 2.1)
  - GoogleAppMeasurement (10.22.0):
    - GoogleAppMeasurement/AdIdSupport (= 10.22.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.11)
    - GoogleUtilities/MethodSwizzler (~> 7.11)
    - GoogleUtilities/Network (~> 7.11)
    - "GoogleUtilities/NSData+zlib (~> 7.11)"
    - nanopb (< 2.30911.0, >= 2.30908.0)
  - GoogleAppMeasurement/AdIdSupport (10.22.0):
    - GoogleAppMeasurement/WithoutAdIdSupport (= 10.22.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.11)
    - GoogleUtilities/MethodSwizzler (~> 7.11)
    - GoogleUtilities/Network (~> 7.11)
    - "GoogleUtilities/NSData+zlib (~> 7.11)"
    - nanopb (< 2.30911.0, >= 2.30908.0)
  - GoogleAppMeasurement/WithoutAdIdSupport (10.22.0):
    - GoogleUtilities/AppDelegateSwizzler (~> 7.11)
    - GoogleUtilities/MethodSwizzler (~> 7.11)
    - GoogleUtilities/Network (~> 7.11)
    - "GoogleUtilities/NSData+zlib (~> 7.11)"
    - nanopb (< 2.30911.0, >= 2.30908.0)
  - GoogleUtilities/AppDelegateSwizzler (7.13.0):
    - GoogleUtilities/Environment
    - GoogleUtilities/Logger
    - GoogleUtilities/Network
    - GoogleUtilities/Privacy
  - GoogleUtilities/Environment (7.13.0):
    - GoogleUtilities/Privacy
    - PromisesObjC (< 3.0, >= 1.2)
  - GoogleUtilities/Logger (7.13.0):
    - GoogleUtilities/Environment
    - GoogleUtilities/Privacy
  - GoogleUtilities/MethodSwizzler (7.13.0):
    - GoogleUtilities/Logger
    - GoogleUtilities/Privacy
  - GoogleUtilities/Network (7.13.0):
    - GoogleUtilities/Logger
    - "GoogleUtilities/NSData+zlib"
    - GoogleUtilities/Privacy
    - GoogleUtilities/Reachability
  - "GoogleUtilities/NSData+zlib (7.13.0)":
    - GoogleUtilities/Privacy
  - GoogleUtilities/Privacy (7.13.0)
  - GoogleUtilities/Reachability (7.13.0):
    - GoogleUtilities/Logger
    - GoogleUtilities/Privacy
  - GoogleUtilities/UserDefaults (7.13.0):
    - GoogleUtilities/Logger
    - GoogleUtilities/Privacy
  - GTMSessionFetcher/Core (3.3.1)
  - leveldb-library (1.22.4)
  - nanopb (2.30910.0):
    - nanopb/decode (= 2.30910.0)
    - nanopb/encode (= 2.30910.0)
  - nanopb/decode (2.30910.0)
  - nanopb/encode (2.30910.0)
  - PromisesObjC (2.4.0)
  - RecaptchaInterop (100.0.0)

DEPENDENCIES:
  - Firebase (~> 10.22.0)
  - FirebaseAppCheck (~> 10.22.0)
  - FirebaseAuth (~> 10.22.0)
  - FirebaseCore (~> 10.22.0)
  - FirebaseDatabase (~> 10.22.0)
  - FirebaseStorage (~> 10.22.0)

SPEC REPOS:
  https://github.com/CocoaPods/Specs.git:
    - AppCheckCore
    - Firebase
    - FirebaseAnalytics
    - FirebaseAppCheck
    - FirebaseAppCheckInterop
    - FirebaseAuth
    - FirebaseAuthInterop
    - FirebaseCore
    - FirebaseCoreExtension
    - FirebaseCoreInternal
    - FirebaseDatabase
    - FirebaseInstallations
    - FirebaseSharedSwift
    - FirebaseStorage
    - GoogleAppMeasurement
    - GoogleUtilities
    - GTMSessionFetcher
    - leveldb-library
    - nanopb
    - PromisesObjC
    - RecaptchaInterop

SPEC CHECKSUMS:
  AppCheckCore: d0d4bcb6f90fd9f69958da5350467b79026b38c7
  Firebase: 797fd7297b7e1be954432743a0b3f90038e45a71
  FirebaseAnalytics: 8d0ff929c63b7f72260f332b86ccf569776b75d3
  FirebaseAppCheck: 8e85fc837a3f006b7c4ef3f50c0a3474395e76f7
  FirebaseAppCheckInterop: a1955ce8c30f38f87e7d091630e871e91154d65d
  FirebaseAuth: bbe4c68f958504ba9e54aee181adbdf5b664fbc6
  FirebaseAuthInterop: a458e398bb1e9b71b9b42d46e54acc666b021d0f
  FirebaseCore: 0326ec9b05fbed8f8716cddbf0e36894a13837f7
  FirebaseCoreExtension: cb88851781a24e031d1b58e0bd01eb1f46b044b5
  FirebaseCoreInternal: 6a292e6f0bece1243a737e81556e56e5e19282e3
  FirebaseDatabase: fee604b3bee8800a1bdc834757d13813cfde1c90
  FirebaseInstallations: 42d6ead4605d6eafb3b6683674e80e18eb6f2c35
  FirebaseSharedSwift: c92645b392db3c41a83a0aa967de16f8bad25568
  FirebaseStorage: bc7bddc743548a89cfb896843a77cf4bdde2c231
  GoogleAppMeasurement: ccefe3eac9b0aa27f96066809fb1a7fe4b462626
  GoogleUtilities: d053d902a8edaa9904e1bd00c37535385b8ed152
  GTMSessionFetcher: 8a1b34ad97ebe6f909fb8b9b77fba99943007556
  leveldb-library: 06a69cc7582d64b29424a63e085e683cc188230a
  nanopb: 438bc412db1928dac798aa6fd75726007be04262
  PromisesObjC: f5707f49cb48b9636751c5b2e7d227e43fba9f47
  RecaptchaInterop: 7d1a4a01a6b2cb1610a47ef3f85f0c411434cb21

PODFILE CHECKSUM: abf9adf0dbe48a7fcbe2096039f36312a7462f40

COCOAPODS: 1.13.0

FirebaseAnalytics does not support visionOS. There is an open feature request at #12230.
Also, while the CocoaPods workaround may work, we've only tested Firebase via Swift Package Manager for visionOS targets.

Remove pod 'Firebase', '> 10.22.0' form the Podfile to stop pulling in Analytics.

@abbana Does removing Analytics from the installation address the build issue?

Hi @paulb777 ,
Removing Analytics resolved the issue.
Now we have a bigger issue that blocks us from proceeding.
Any of the below pulls GoogleDataTransport (9.4.1, latest) which won't run in visionOS Simulator "CoreTelephony is not available when building for visionOS Simulator."
FirebaseCrashLytics
FirebaseMessaging
GoogleMLKit
which we all use.
They compile perfectly to iOS simulator, can we have this fixed so we can move forward please?
v9.4.1 (CocoaPods Only)
The v9.4.0 podspec did not include the intended dependency range for nanopb (https://github.com/firebase/firebase-ios-sdk/issues/12477)

v9.4.0
Add privacy manifest. (#114)
v9.3.0
Added new APIs for attaching product ID data to an event.
Fix 0x8BADF00D crashes and add diagnostics. (https://github.com/firebase/firebase-ios-sdk/issues/9859)
v9.2.5
Replace 'TARGET_OS_XR' with 'TARGET_OS_VISION' for compatibility with Xcode 15 Beta 5.
v9.2.4 (SwiftPM Only)
Fix build errors on the visionOS platform. (#97)
I tried to open a bug in GoogleDataTransport , but it has redirected us here.
Do I need to fill a new bug for this or is a quick fix?
Thank you.

@abbana At first glance that looks like a CocoaPods issue: CoreTelephony is specified only for iOS and OSX in the podspec - https://github.com/google/GoogleDataTransport/blob/main/GoogleDataTransport.podspec#L36.
There may be a way to extend your Podfile workaround to address it, or you may be able to remove CoreTelephony from the linker settings manually after pod installation.

Raised https://github.com/CocoaPods/CocoaPods/issues/12316
Let's give this some more time as in short of ideas on how to proceed further.
Thanks.

Ok,
so after hours of work, we still have this issue left unfortunately.
Apple wants us use one unique big app bundle for multiple platforms so we need to go through this pain, so sorry about this.
I have tried multiple thing amongst which the ones you suggested
There may be a way to extend your Podfile workaround to address it
post_install do |installer|
installer.pods_project.targets.each do |target|
puts "\033[33m  scanning platform #{target.platform_name} , target #{target.name}   \033[0m"
if target.platform_name == :visionos
if target.name == "GoogleDataTransport"
target.build_configurations.each do |config|
config.build_settings['OTHER_LDFLAGS'] = '$(inherited) -framework "CoreTelephony"'
puts "\033[33m  found and removed CoreTelephony on visionOS   \033[0m"
    end
  end
end

end
end
Which gives us something around the lines below
scanning platform ios , target FirebaseCoreInternal-FirebaseCoreInternal_Privacy
scanning platform ios , target FirebaseDatabase
scanning platform ios , target FirebaseDynamicLinks
scanning platform ios , target FirebaseDynamicLinks-FirebaseDynamicLinks_Privacy
scanning platform ios , target FirebaseSharedSwift
scanning platform ios , target FirebaseStorage
scanning platform ios , target FirebaseStorageUI
scanning platform ios , target FirebaseUI
Of course CocoaPods has just one platform and we have set it ios. We can't distinguish at this stage between the two, so nothing we can do here
or you may be able to remove CoreTelephony from the linker settings manually after pod installation.
In Xcode, under "Frameworks, Libraries and Embedded Content" all are linked to just Pods_.framework , so we can't workaround anything here it either, am I wrong?
I was not able to find in the podspec  s.visionos.frameworks = 'SystemConfiguration', while all the other platforms have it, so maybe it defaults to the platform specified in the podfile if not sepcified in the .podspect?
I am not an expert and need an help in pinpoint this.
It will be worth adding the s.visionos.frameworks value to the .podspec and try with an ios-visionos empty project if that fixes the built issue.
Let me know if anything I can do from my side.
And thank you.

Here's an example of how to manually edit, both in GoogleDataTransport.debug and GoogleDataTransport.release:

Thank you @paulb777 ,
but I haven't found a way to remove that frame either in Xcode or Podfile as after installation task, simply we were not able to.
Also supposing you can effectively remove it from the framework list that way, which is not, you will remove it from all the build targets.
So the only solution I see is that the maintainer, you, fix the repo so that it won't be included for visionOS and visionOS simulator.

We haven't yet prioritized CocoaPods support for VisionOS, so we're currently more able to help people using Swift Package Manager for VisionOS builds.

Thank you Paul,
There are some Google Products like MLKit which do not support SPM , see https://github.com/googlesamples/mlkit/issues/180
We use them in Android, iOS, ipadOS, and we should use them on visionOS as well.
Can we have a rough ETA on to when a Firebase project will be able to run for both iOS and visionOS using CocoaPods?

We don't yet have an ETA for visionOS via CocoaPods, partly because CocoaPods support for visionOS is still TBD.
I don't think there are any Google products that support visionOS that don't also support Swift Package Manager.

Understood, thank you.


[AutoPR compute/resource-manager] Moving Priority and EvictionPolicy enum to the definitions section and adding 'Spot' priority. Updating both 2019-03-01 and 2019-07-01 Api versions.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7748

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/8464


search-members helper works in terminal (cURL) but not with this wrapper

Hey there,
first of all, thank you for all the great work! :-)
I am having a hard time getting the search-members helper to work with this wrapper.
Example:

$result = $MailChimp->get("search-members?query=$search_string");
print_r($result);

Output:

Array
(
[exact_matches] => Array
(
[members] => Array
(
)
[total_items] => 0
)
[full_search] => Array
(
[members] => Array
(
)
[total_items] => 0
)
[_links] => Array
(
[0] => Array
(
[rel] => self
[href] => https://us12.api.mailchimp.com/3.0/search-members
[method] => GET
[targetSchema] => https://us12.api.mailchimp.com/schema/3.0/SearchMembers/Collection.json
)
[1] => Array
(
[rel] => parent
[href] => https://us12.api.mailchimp.com/3.0/
[method] => GET
[targetSchema] => https://us12.api.mailchimp.com/schema/3.0/Root.json
)
)
)

It does however work with a cURL GET request:

curl -H "Authorization: apikey ***" https://us12.api.mailchimp.com/3.0/search-members?query=$search_string

Any ideas? Thank you in advance!

Try this:
$result = $MailChimp->get("search-members", ['query' => $search_string]);
print_r($result);


Day395

Resolves #793.

Pull Request Test Coverage Report for Build 1508

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1506:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls

Pull Request Test Coverage Report for Build 1500

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1506:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


Error: Unexpected token if 'for' in Error constructor

If word for before expression in template strings which passed to Error constructor then occurs an error:
"SyntaxError: Unexpected token ;
    at https://static.jsbin.com/js/prod/runner-3.39.14.min.js:1:13926
    at https://static.jsbin.com/js/prod/runner-3.39.14.min.js:1:10855"

Example code generates above error:
const foo = 'bar'
const err = Error(`Foobar for ${foo} bar`)

Example templates strings works correct:
`Foobar fork ${foo}`
`Foobar for ${foo} for`
`for Foobar for ${foo}`

Error is not present with ES6/Babel transpiler.
Browsers: Firefox 48.0.1, Chrome 52.0.2743.116 (64-bit)

Can you use // noprotect to work around the problem.
On Sun, 28 Aug 2016, 00:41 jakub-gawlas<EMAIL_ADDRESS>wrote:

If word for before expression in template strings passed to Error
constructor occurs an error:
"SyntaxError: Unexpected token ;
at https://static.jsbin.com/js/prod/runner-3.39.14.min.js:1:13926
at https://static.jsbin.com/js/prod/runner-3.39.14.min.js:1:10855"
Example code generates above error:
const foo = 'bar'
const err = Error(Foobar for ${foo} bar)
Example templates strings works correct:
Foobar fork ${foo}
Foobar for ${foo} for
for Foobar for ${foo}
Error is not present in ES6/Babel.
Browsers: Firefox 48.0.1, Chrome 52.0.2743.116 (64-bit)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jsbin/jsbin/issues/2864, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA1hNu-0Zcs5OrkIOVokJdNJSCobjCjks5qkMsygaJpZM4Juzzw
.


Update AzureIoTEdgeV2 to support node10

Task name: AzureIoTEdgeV2
Description: update to support node10
Documentation changes required: (Y/N)
Added unit tests: (Y/N)
Attached related issue: (Y/N) https://github.com/microsoft/azure-pipelines-tasks/issues/15184
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

/azp run

Hi, @cindydeng1998
Could you fix from (done: MochaDone) to (done: Mocha.Done)  in https://github.com/microsoft/azure-pipelines-tasks/blob/user/xinzed/update-node/Tasks/AzureIoTEdgeV2/Tests/L0.ts#L12 .
Thank you in advance.

@cindydeng1998 thanks! Merged PR.


Move probe.inner_attach before hardware reset

Before this change the manipulation of the reset pin on my MAX32625PICO programmer doesn't actually work. The reset pin stays high during the entire connection phase.
I'm working on getting support for the Microchip ATSAML10 family working in probe-rs. This is a preliminary fix that I've found along the way. I'm not sure how much this is unique to my situation, but it feels likely that it's an artifact of the programmer more than the chip I'm attempting to connect to.
Below are a couple of logic analyzer screen shots before and after the fix. I'm running the command cargo flash --chip ATSAML10E16A --connect-under-reset using a build of cargo-flash that is linked against a fork of probe-rs that includes this commit plus the chip definition for the ATSAML10.
Note that in the first screenshot the reset line (bottom row, labeled D2 and RESET and colored red) never changes when starting to connect to the chip. In the second screenshot the reset line goes low.

There's more work to be done to get the connection to actually work for this chip, but this seemed like an obvious bug fix to get in before I finish the rest of the work. I'm way out of my element here, so any suggestions on how to do this differently are very welcome.

Thanks a lot for this!
I would like us to test this against more probes & targets before we merge to ensure we do not regress anywhere.

I think this conflicts with the current implementation for several probes:

esbusbjtag: In this probe, initial communication with the target chip happens in the attach function.
ftdi: Detection of JTAG TAPS happens in the attach function.
jlink: IDCODE is read in attach function.

This all seems JTAG related, so there is probably some mismatch between the JTAG and SWD implementations.
What kind of probe is the MAX32625PICO ?

What kind of probe is the MAX32625PICO ?

CMSIS-DAP SWD only.
https://www.maximintegrated.com/en/products/microcontrollers/MAX32625PICO.html

This change doesn't match the behavior of the named flag - you're no longer attaching under reset aka while it is asserted.  I suspect that will break many assumptions in many cases.
The reset line should be deasserted at session.rs:225, and the CMSIS DAP seems to have the right logic implemented for this, but I don't have a CMSIS DAP probe to help debug.  @neonquill - can you run again with RUST_LOG=info - that should at least confirm that the assert / deassert functions are being called correctly and may give us some extra info to help figure out what's going on.

can you run again with RUST_LOG=info

I may be misunderstanding something, but I'm going to interpret this as asking me to run with a higher level of logging. Since info doesn't really log very much, I'm just going to give you trace level logging and hope that's ok. Also, there is very little logging within the sequence_handle.reset_hardware_assert(dap_probe)?; call which is where I think the problem is, so I also ran a trace bracketing that function with additional logging:
Both traces were collected by running env RUST_LOG=trace cargo flash --chip ATSAML10E16A --chip-description-path ./SAML10.yaml --connect-under-reset

trace_stock.txt - This should be a run using a master build of cargo-flash
trace_with_extra_logging.txt - This should be a trace modified to compile against a modified version of master-branch probe-rs using the diff shown below.

diff --git a/probe-rs/src/architecture/arm/sequences/mod.rs b/probe-rs/src/architecture/arm/sequences/mod.rs
index 2dd1ddd0..d8579259 100644
--- a/probe-rs/src/architecture/arm/sequences/mod.rs
+++ b/probe-rs/src/architecture/arm/sequences/mod.rs
@@ -396,10 +396,12 @@ pub trait ArmDebugSequence: Send + Sync {
     /// [ARM SVD Debug Description]: http://www.keil.com/pack/doc/cmsis/Pack/html/debug_description.html#resetHardwareAssert
     #[doc(alias = "ResetHardwareAssert")]
     fn reset_hardware_assert(&self, interface: &mut dyn DapProbe) -> Result<(), crate::Error> {
+        log::debug!("start sequences reset_hardware_assert");
         let mut n_reset = Pins(0);
         n_reset.set_nreset(true);

         let _ = interface.swj_pins(0, n_reset.0 as u32, 0)?;
+        log::debug!("finish sequences reset_hardware_assert");

         Ok(())
     }
diff --git a/probe-rs/src/probe/cmsisdap/mod.rs b/probe-rs/src/probe/cmsisdap/mod.rs
index bdbd24d9..13be1446 100644
--- a/probe-rs/src/probe/cmsisdap/mod.rs
+++ b/probe-rs/src/probe/cmsisdap/mod.rs
@@ -722,6 +722,7 @@ impl RawDapAccess for CmsisDap {
         pin_select: u32,
         pin_wait: u32,
     ) -> Result<u32, DebugProbeError> {
+        log::debug!("In cmsisdap::swj_pins");
         let request = SWJPinsRequest::from_raw_values(pin_out as u8, pin_select as u8, pin_wait);

         let Pins(response) = commands::send_command(&mut self.device, request)?;

The difference between these two trace files is larger than I would have expected. It's either the difference between 0.12.0 probe-rs and master or I somehow picked up some of my other changes. Hopefully one or both of these files is useful for you, I'm happy to try again if I misinterpreted the intent.

you're no longer attaching under reset aka while it is asserted

This comment also confuses me. I have been working under the assumption that probe.inner_attach()?; is attaching to the probe, not to the chip we're trying to debug/flash. My understanding is that one of the first steps of connecting to the chip itself is reading the idcode. As far as I can tell, the cmsis-dap probe doesn't attempt to read the idcode from the chip until the arm interface.initialize() call. As I said above, it looks like the jlink/jtag code path reads the idcode in the attach function, which would match what you're saying. As far as I can tell for cmsis-dap it doesn't make a difference since the actual communication with the chip isn't happening in inner_attach. It's also extremely likely I'm just not understanding the code correctly.

I have been working under the assumption that probe.inner_attach()?; is attaching to the probe, not to the chip we're trying to debug/flas

probe.inner_attach is just a wrapper around DebugProbe::attach, which has this comment explaining it is attaching to the underlying target / chip.  In many probes this involves talking to the chip, such as reading the IDCODE or powering on debug systems.
    /// Attach to the chip.
    ///
    /// This should run all the necessary protocol init routines.
    fn attach(&mut self) -> Result<(), DebugProbeError>;

Both traces were collected by running env RUST_LOG=trace cargo flash --chip ATSAML10E16A --chip-description-path ./SAML10.yaml --connect-under-reset

I'm not sure there's much that can be easily debugged on the 0.12 build - there's a lot of change since then.  What I'm trying to prove is with the failure case does it call reset_hardware_assert / reset_harware_deassert properly.
I looked at the public cmsis-dap firmware and it doesn't setup its GPIO outputs, including nRESET, until after a "Connect" command has been received.  The current cmsis-dap probe-rs code does that in attach, which probably explains both what you're seeing on the logic analyzer, since the nRESET pin wouldn't be configured for output yet, and why moving the code fixes it.  The other probes, like the j-link, can toggle pins in any state, which explains why they don't have this problem.
I think the fix here that works in all cases is to if not already attached run the connect command in swj_pins.  This allows the early reset operations to happen correctly without changing the contract on what attach means for other probes.
I coded up an attempted fix here:
https://github.com/thefaxman/probe-rs/tree/thefaxman/cmsis-dap
Can you try this and see if it causes the reset lines to work properly for you?

Can you try this and see if it causes the reset lines to work properly for you?

Looks good to me!

Seems like a much better approach so I'm going to close this PR.


For japanese keyboard EISUU with DF-XCVB to 56-7890 return some error in Dvorak

I'm totally confuzzed. Could you help me?

By add it manually. it works.

I found the conflict.But how it conflict?

Do you enable other settings?
Karabiner applies only the first matched .
So, if you change these keys by other settings, the setting might not work.
https://pqrs.org/osx/karabiner/xml.html.en#order

THKs

I does use Workman layout now.


Updated links

Updated links to follow to your profile :)

Wanted to give you proper credits , so fixed the links :D

Forgot to check there already exists pull request for this  https://github.com/cobiwave/simplefolio/pull/147 , will try contributing in some other way


error: constexpr function return is non-constant

I use tf1.13,cuda10.0 and g++-4.8,and my os is ubuntu16.04.However,when I run python run.py --help,some errors occur：
/usr/local/lib/python3.5/dist-packages/tensorflow/include/absl/strings/string_view.h(496):
error: constexpr function return is non-constant
/usr/local/lib/python3.5/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(55):
warning: integer conversion resulted in a change of sign
/usr/local/lib/python3.5/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(309):
warning: integer conversion resulted in a change of sign
/usr/local/lib/python3.5/dist-packages/tensorflow/include/google/protobuf/arena_impl.h(310):
warning: integer conversion resulted in a change of sign
1 error detected in the compilation of "/tmp/tmpxft_00003790_00000000-6_backward_warp_op.cu.cpp1.ii".
Traceback (most recent call last):
File "/home/kjq/UnFlow/src/e2eflow/ops.py", line 59, in
op_lib = tf.load_op_library(lib_path)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/load_library.py", line 61, in load_op_library
lib_handle = py_tf.TF_LoadLibrary(library_filename)
tensorflow.python.framework.errors_impl.NotFoundError: ./backward_warp_op.so: cannot open shared object file: No such file or directory
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "run.py", line 7, in
from e2eflow.core.train import Trainer
File "/home/kjq/UnFlow/src/e2eflow/core/train.py", line 11, in
from . import util
File "/home/kjq/UnFlow/src/e2eflow/core/util.py", line 2, in
from ..ops import downsample as downsample_ops
File "/home/kjq/UnFlow/src/e2eflow/ops.py", line 61, in
compile(n)
File "/home/kjq/UnFlow/src/e2eflow/ops.py", line 43, in compile
subprocess.check_output(nvcc_cmd, shell=True)
File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
**kwargs).stdout
File "/usr/lib/python3.5/subprocess.py", line 708, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'nvcc -std=c++11 -c -o backward_warp_op.cu.o backward_warp_op.cu.cc -I/usr/local/lib/python3.5/dist-packages/tensorflow/include -D_GLIBCXX_USE_CXX11_ABI=0 -L/usr/local/lib/python3.5/dist-packages/tensorflow -ltensorflow_framework -D GOOGLE_CUDA=1 -x cu -Xcompiler -fPIC -I /usr/local --expt-relaxed-constexpr' returned non-zero exit status 1
could you give some advices ？

hello, I have the same issue,
Did you solve the problem?


[CELEBORN-1665] CommitHandler should process CommitFilesResponse with COMMIT_FILE_EXCEPTION status

What changes were proposed in this pull request?
CommitHandler should process CommitFilesResponse with COMMIT_FILE_EXCEPTION status.
Why are the changes needed?
CommitHandler processes CommitFilesResponse with statuses including SUCCESS, PARTIAL_SUCCESS, SHUFFLE_NOT_REGISTERED, REQUEST_FAILED and WORKER_EXCLUDED at present. Meanwhile, Controller replies CommitFilesResponse with COMMIT_FILE_EXCEPTION status for throwable. Therefore, CommitHandler should process COMMIT_FILE_EXCEPTION status.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
No.

Thanks. merge to main(v0.6.0) and branch-0.5(v0.5.2)


A state hook to do and undo

I wrote a simple state hook that allows to undo/redo changes to a state: https://github.com/arnaudNYC/useDo
const [state, setState, undo, redo, canUndo, canRedo] = useDo(initialState);
Calling undo reverts to the previous state, and calling redo undoes the last undo. The canUndo and canRedo are booleans indicating if the operation can be performed.
Is this something you'd be interested in having in this project? I'm happy to donate the code and open a PR here. Let me know.

He already have such hook: useStateWithHistory

Thanks, good to know!


clang-format check is broken

In the "Check current commit" step, git fails to find the repository. For an example, see this job: https://github.com/google/cpu_features/actions/runs/5221342145/jobs/9425484204?pr=310

Good Catch ! Thanks for the report !

@Mizux can we fix this one before I release v0.9.0? If not I'll just remove it from the milestone.


Inconsistent Polygon Rendering (iOS/Android)

Is this a bug report?
Yes

Have you read the Installation Instructions?
Yes
Environment

react-native: 0.53.0
react: 16.2.0
react-native-maps: 0.20.0
Steps to Reproduce

Use a simple <MapView> component with a <Polygon> covering half the world.

<MapView>
          <Polygon
            coordinates={
              [{
                longitude: 180,
                latitude: 90
              }, {
                longitude: 0,
                latitude: 90
              }, {
                longitude: 0,
                latitude: -90
              }, {
                longitude: 180,
                latitude: -90
              }, {
                longitude: 180,
                latitude: 90
              }]
            }
            strokeColor={'#ff0000'}
            fillColor={'rgba(0,0,0,0.5)'}
            strokeWidth={2}
          />
        </MapView>

Expected Behavior
Polygon covers the right half the world on both iOS and Android.
The Polygon on Android is 'filled', same like on iOS.
Actual Behavior
Polygon only covers the right half the world on iOS, partially covers the left side of the world on Android.

Reproducible Demo
https://snack.expo.io/rJEdDBgvG
Additional information
Initially, I wanted to create a polygon covering the entire world and then have holes in it to create a mask effect. However, the <Polygon> component does not seem to render the polygon covering the entire world, instead it's hidden.
Polygon covering the world:
<Polygon
            coordinates={
              [{
                longitude: 180,
                latitude: 90
              }, {
                longitude: -180,
                latitude: 90
              }, {
                longitude: -180,
                latitude: -90
              }, {
                longitude: 180,
                latitude: -90
              }, {
                longitude: 180,
                latitude: 90
              }]
            }
            strokeColor={'#ff0000'}
            fillColor={'rgba(0,0,0,0.5)'}
            strokeWidth={2}
/>

I made approximate and middle coordinates for mask.
And it works on me.
<Polygon
coordinates = {
[
    { latitude: -90, longitude: -179.99999999 },
    { latitude: 0, longitude: -179.99999999 },
    { latitude: 90, longitude: -179.99999999 },
    { latitude: 90, longitude: 0 },
    { latitude: 90, longitude:<PHONE_NUMBER>9 },
    { latitude: 0, longitude:<PHONE_NUMBER>9 },
    { latitude: -90, longitude:<PHONE_NUMBER>9 },
    { latitude: -90, longitude: 0 },
    { latitude: -90, longitude: -179.99999999 },
  ]
}

@socar-chef Thanks, that seems to be a valid workaround for now!


Setup GitHub Actions

Auto-run unit tests
Integrate with CodeCov for coverage

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


[Bug] [Module Name] Bug title I deleted default tenant in tenant management, but it often appears when replenishing data, can this be fixed ？？？？？？？

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
I deleted default tenant in tenant management, but it often appears when replenishing data, can this be fixed ？？？？？？？
What you expected to happen
![image](https://github.com/user-attachments/assets/c

854eff9-678b-45cb-a5e6-b4f29b64769e)
How to reproduce
i don't konw
Anything else
No response
Version
3.2.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I really don't get this. Why is this a problem?

Already fixed in dev.

已在开发中修复。
I updated to 3.2.2 but every time I make up data for more than two days, it goes to rerun using the default user, can you fix this

I really don't know how to fix this


grading issue

Companion is giving an error due to width not being set to 370px. It is stating "expected 370px but found 355px" Screen shot attached.

Version: 1.93.1
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

/causedByExtension
Please use your course support channel.


fix: test on OCP

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
TODO(replace-me)
Use this space to explain how you validated that your change functions exactly how you expect it.
Feel free to attach JSON snippets, curl commands, screenshots, etc. Apply a simple benchmark: would the information you
provided convince any reviewer or any external reader that you did enough to validate your change.
It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list.
It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only.
It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are
responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change
ASAP after it gets merged or explain in PR when the validation will be performed.
Explain here why you skipped testing in case you did so.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/test ocp-4-16-lp-interop-acs-tests-aws

/test ?

/test ?

/test ocp-4-preview-qa-e2e-tests

/test ocp-4-preview-qa-e2e-tests


Secure-Configuration-Properties.jar does not exist

Attempting to download the secure-configuration-properties.jar file from the website yields a "resource not found".
Link to the article: https://docs.mulesoft.com/mule-runtime/4.4/secure-configuration-properties
Link to the download: https://docs.mulesoft.com/downloads/mule-runtime/4.2/secure-properties-tool.jar

Thank you. It is available for download now. @QuentinX5


checkin for issue#1041

@nishakm  please review #vGHC OSD

@Samaiya Can you update your commit message title to Direct check for key in command_lib['snippets'] ?
You will need to run:
git commit --amend

Then you update your  title in the editor and save it.
Then run
git push -f origin samaiya_1041

@Samaiya Can you update your commit message title to Direct check for key in command_lib['snippets'] ?
You will need to run:
git commit --amend

Then you update your title in the editor and save it. Then run
git push -f origin samaiya_1041

done


Select Input: Hide the options popup on pointer out after some delay

https://github.com/1CRM/oceanfront/assets/5743284/a6e49de2-e3d8-446c-ab3b-e3d386ebfd0e
https://github.com/1CRM/oceanfront/assets/5743284/a2f0464c-7937-4a64-8619-8c67bf5b994b

This popup appears to happen on a scroll but for a very short span.

This popup appears to happen on a scroll but for a very short span.

sorry. don't understand what do you mean


Add methods setUseDocStore(), setDisableLazyLoading(), setDisableReadAuditing(), validate() ... to query root bean type

The setUseDocStore() requires Ebean 7.1.1 so going to bump the version to match that.

  /**
   * Set to true if this query should execute against the doc store.
   *

   * When setting this you may also consider disabling lazy loading.
   *

   */
  public R setUseDocStore(boolean useDocStore) {
    query.setUseDocStore(useDocStore);
    return root;
  }

  /**
   * Set true if you want to disable lazy loading.
   *

   * That is, once the object graph is returned further lazy loading is disabled.
   *

   */
  public R setDisableLazyLoading(boolean disableLazyLoading) {
    query.setDisableLazyLoading(disableLazyLoading);
    return root;
  }

  /**
   * Disable read auditing for this query.
   *

   * This is intended to be used when the query is not a user initiated query and instead
   * part of the internal processing in an application to load a cache or document store etc.
   * In these cases we don't want the query to be part of read auditing.
   *

   */
  public R setDisableReadAuditing() {
    query.setDisableReadAuditing();
    return root;
  }

  /**
   * Returns the set of properties or paths that are unknown (do not map to known properties or paths).
   *

   * Validate the query checking the where and orderBy expression paths to confirm if
   * they represent valid properties or paths for the given bean type.
   *

   */
  public Set<String> validate() {
    return query.validate();
  }

e.g.

Hit the doc store (ElasticSearch) where name matches "rob" ... returning pagedList with total hits and list of customer.

    new QCustomer()
        .name.contains("rob")
        .setUseDocStore(true)
        .setMaxRows(10)
        .findPagedList();


after unzipped, it cannot run with default.yml,even after several error is fixed.

11:27:48.649 [main] ERROR com.hotels.styx.StyxServer - Styx server failed to start due to configuration error in file [D:\workspace\styx\distribution.\conf\default.yml]: Unexpected field type. Field 'routingObjects[h2Handler].config' should be OBJECT(status, content, headers), but it is NULL

same error


⚠ Diverse AirCon & Mechanical has degraded performance

In b790eeb, Diverse AirCon & Mechanical (https://diverseaircon.com.au) experienced degraded performance:

HTTP code: 200
Response time: 7932 ms

Resolved: Diverse AirCon & Mechanical performance has improved in c20ef1c.


hope to bring back the aggresive mode

I love this app and I wish you guys could bring back aggresive mode! thankyou!

#250