Release ci

copilot:all

🤖 Generated by lychee action
Summary

Status
Count

🔍 Total
981

✅ Successful
379

⏳ Timeouts
0

🔀 Redirected
0

👻 Excluded
601

❓ Unknown
0

🚫 Errors
0

Full action output
Full Github Actions output


Feature/better bondi

Improved bondi.hpp such that it solves Bondi analytical solutions in a stable way. In detail, the bounds for looking for the solution are updated in order to only pick up the inflowing branch out of the two branches and changed the numerical method to a simple and stable bisection method.

Merging as-is.
Finally got around to testing this (sorry!) and it works for me out much farther than the old bondi code, though I still needed to add back the if(isnan()) cases if I went too far.  Might have been my issue in testing, I'd take another look if the problem gets more popular.
There's some cleanup I would have proposed but it's not really related to the the main changes here, and I'm worried the branch might fall behind if I merge other things to 'dev' first.


[Event request] PAG 475 OnBeforeOnAfterGetRecord

For Slovenian localization we have our own VAT statement report, including the CalcLineTotal function which we would like to call instead of current one from Report 12. Our suggestion:

add a function CalcColumnValue which calculates the ColumnValue variable

on begining of the function set an event publisher with var parameter IsHandled
trigger OnAfterGetRecord()
begin
CalcColumnValue(Rec, ColumnValue, 0);
if "Print with" = "Print with"::"Opposite Sign" then
ColumnValue := -ColumnValue;
end;
procedure CalcColumnValue(Rec: Record "VAT Statement Line"; var TotalAmount: Decimal; Level: Integer)
var
IsHandled: Boolean;
begin
OnBeforeCalcColumnValue(Rec, ColumnValue, 0, IsHandled);
if IsHandled then
exit;
VATStatement.CalcLineTotal(Rec, ColumnValue, 0);
end;
[IntegrationEvent(true, false)]
local procedure OnBeforeCalcColumnValue(VATStatementLine: Record "VAT Statement Line"; var TotalAmount: Decimal; Level: Integer; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Rich Text editor does not work correctly

Hello, there is some kind of bug preventing a user from using the rich-text editor as expected (compared to the one in the builtin entry editor).
How it's implemented
Via @contentful/create-contentful-app using the @contentful/app-sdk:
<FieldWrapper
  sdk={sdkRef}
  name={label}
>
  <Field
    sdk={sdkRef}
    widgetId={widget}
  />
</FieldWrapper>

Expected behavior
Builtin entry editor:
https://user-images.githubusercontent.com/5041305/153089246-c8296e1a-5fd9-4435-971b-343de6dfb199.mov
Actual behavior
FieldWrapper with Field
https://user-images.githubusercontent.com/5041305/153089293-94ef91de-5141-44c3-b2cd-6ea0b2bf668f.mov
Versions

@contentful/default-field-editors:  1.1.2

@contentful/field-editor-rich-text: 1.1.1

@contentful/app-scripts: 0.14.114
@contentful/app-sdk: 4.3.1
npm: 8.1.2
node: 16.13.1

Please let me know if there is anything else I need to provide. Thank you.

Hello! I am seeing this exact same issue.

this behavior still persists when creating a brand new contentful app via @contentful/create-contentful-app@latest.
updated versions:

@contentful/default-field-editors: 1.1.16
@contentful/app-scripts: 1.1.2
@contentful/app-sdk: 4.4.0
node: 16.15.0
npm: 8.9.0


Accomodate out-of-repo builds

Fix #514, cc @mid-kid for the interface/behaviour.

Sounds good to me! What would the correct invocation of mdbook build be?

Hopefully you're able to figure that out on your own? (This is not a taunt, but rather I tried to make this reasonably easy for other packagers who may not be able to ask us for help, and I want to check that.)

If I got this right, it's MDBOOK_preprocessor__pandocs__out_of_repo=true mdbook build?

Yep, that matches my understanding. Hopefully both of us are correct :D

Yeah, :+1:


Aerosol Masking for WOfS

This adds a yaml for using LS8 and masking out the high aerosol pixels.
Changes from the original yaml include:

only for LS8
uses the qa_aerosol layer
adds colours to the lookup table for when things have high aerosol as well as other properties.

I don't think we need this any more.


Issue branch 1348

Removed data-bind from a parent div from My Assigned Tasks
Fixes #1348

cc @stevejgordon
There appears to be changes to the .sln file as part of this which I don't think is needed.  Is there an issue from the move to vs2017 or maybe just something else that came in?
@wmay1991 let us know how we can help to clear that up/out.

I recently did a fetch from VS2015 and I received MS Build errors. I did some researched and it seemed to be related to VS2015 being incompatible. I downloaded VS2017 and everything worked fine. You may need to indicate in your instructions that VS2017 should be used.

thanks @wmay1991 we had just moved to VS2017 in the last few days so good point on our docs needing to be updated.  I think we will need to amend this to not include the sln changes

I reverted my commit and made sure only the event tasks page was added.

thanks @wmay1991 merging now

@tonysurma My company is sponsoring a Hackathon second Friday of May. Is there any section/issues in particular that would be good for us to work on?

thanks for asking @wmay1991 send me an email if you can to firstname dot lastname at htbox.org and I can connect you with folks who have run hackthons for HTBox at their company like @stevejgordon for some best practices and approaches.  I can also pull you into our slack channel if you like.
Again thanks a lot for your contribution and for thinking of pulling together a hackathon for our project!

@wmay1991 Happy to help and thanks for getting involved. After my first code-a-thon I put together this blog post on the event - https://www.stevejgordon.co.uk/running-humanitarian-toolbox-code-thon


Do not wipe offsets when rationalizing claims

I believe this line is responsible for consumer rewinding observed on several Marshal consumers lately. When a claim attempt writes to __marshal but then proceeds to fail (either to finish the claiming process or to issue the first heartbeat), this line of code causes the rationalizer in all subsequent claimers to believe that the current offset is 0 when really they ought to use the last current offset seen in a heartbeat message.
In the case where a claim succeeds, the rationalizer will observe the heartbeats which overwrite this 0 with the real current offset, as observed here:
I0719 22:08:19.026897 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: releaseClaim(swoosh-ingestor-squid) start with CurrentOffset 63653613
I0719 22:08:19.026903 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: releaseClaim(swoosh-ingestor-squid) exiting normally with CurrentOffset 63653613
I0719 22:08:19.027169 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) start with CurrentOffset 63653613
I0719 22:08:19.027351 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) exiting normally with CurrentOffset 0
I0719 22:08:19.027371 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) start with CurrentOffset 0
I0719 22:08:19.027376 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) exit with CurrentOffset 63653613
I0719 22:08:19.027451 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: releaseClaim(swoosh-ingestor-squid) start with CurrentOffset 63653613
I0719 22:08:19.027457 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: releaseClaim(swoosh-ingestor-squid) exiting normally with CurrentOffset 63653613
I0719 22:08:19.027592 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) start with CurrentOffset 63653613
I0719 22:08:19.027617 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) exiting normally with CurrentOffset 0
I0719 22:08:19.027904 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) start with CurrentOffset 0
I0719 22:08:19.027913 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) exit with CurrentOffset 63653613
I0719 22:08:19.028281 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) start with CurrentOffset 63653613
I0719 22:08:19.028286 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) exit with CurrentOffset 63661389
I0719 22:08:19.028644 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) start with CurrentOffset 63661389
I0719 22:08:19.028649 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) exit with CurrentOffset 63665435

Note that the offset is 0 temporarily but the heartbeat recovers the offset. Compare to the case where the claim fails:
I0719 22:08:20.541845 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: releaseClaim(swoosh-ingestor-squid) start with CurrentOffset 65634730
I0719 22:08:20.541852 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: releaseClaim(swoosh-ingestor-squid) exiting normally with CurrentOffset 65634730
I0719 22:08:20.541929 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) start with CurrentOffset 65634730
I0719 22:08:20.541936 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) exiting normally with CurrentOffset 0
I0719 22:08:20.542593 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) start with CurrentOffset 0
I0719 22:08:20.542600 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) exiting normally with CurrentOffset 0
I0719 22:08:20.542608 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) start with CurrentOffset 0
I0719 22:08:20.542615 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: handleClaim(swoosh-ingestor-squid) exiting normally with CurrentOffset 0
I0719 22:08:20.542622 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) start with CurrentOffset 0
I0719 22:08:20.542628 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) exit with CurrentOffset 63863000
I0719 22:08:20.542780 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) start with CurrentOffset 63863000
I0719 22:08:20.542788 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) exit with CurrentOffset 63871619
I0719 22:08:20.542891 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) start with CurrentOffset 63871619
I0719 22:08:20.542898 15141 log.go:32] O HAI: [goscribe.traffic-swoosh-squid:2] rationalize: updateClaim(swoosh-ingestor-squid) exit with CurrentOffset 63877783

Here the second claimer believes the CurrentOffset is 0 which is then fast-forwarded to the earliest non-expired offset.
I claim this line is correct to delete because every rationalizer which reads it either:

Already read a heartbeat message with a real CurrentOffset embedded, and it is always safe to resume consumption from a CurrentOffset which was heartbeated even if the Kafka committed offsets differ.
Would need to fall through to Kafka committed offsets due to expiry of the __marshal topic, which will still happen because 0 is the zero value for CurrentOffset.

I believe this bug has existed since the dawn of time, but has mostly been non-impacting because Marshal attempts to fall back to Kafka committed offsets. However, all the recent offset related issues (SEV Arctic Bison) are also preventing Marshal from observing correct Kafka offsets so we fall all the way through to using earliest offset.

Oops, I didn't mean for this to reach you out of band on PTO @zorkian . I think we're going to yolo it due to time constraints :-/


Jest Snapshot Version Header

We discussed adding a header like:
// Jest Snapshot v1

and then validate Jest and throw if the snapshot version doesn't match, like:
Error: The snapshot file associated with this project is for version 1 but Jest 25 expects version 2.

@cpojer You mean everytime snapshot updates.increment new version?

@anilreddykatta no, it's a version that we define in jest-snapshot, like:
const SNAPSHOT_VERSION = '1';

// later:
writeSnapshot() {
  const content = `// Jest Snapshot v${SNAPSHOT_VERSION}, <short url description>`
}

// readSnapshot
const content = readSnapshot();
if (snapshotVersionFromFirstLine < SNAPSHOT_VERSION) {
  throw new Error('update your snapshots!');
}

does that make sense?

@cpojer Yeah makes sense..so when we update snapshots next time..will the version number change?

Yes. This is just to let you know, that there's a change in snapshot formatting, which you should just update, because it breaks your tests

@thymikee Thanks 👍

can we add something like
exports['Schema Version'] = 1;

Instead of a comment? (as it's easier to get it for checks later)

What about naming collision, when someone names the snapshot the same way?

I think a comment is way more correct for this use case.

From: Michał Pierzchała<EMAIL_ADDRESS>Sent: Friday, February 10, 2017 6:20:32 PM
To: facebook/jest
Cc: Christoph Pojer; Mention
Subject: Re: [facebook/jest] Jest Snapshot Version Header (#2853)
What about naming collision, when someone names the snapshot the same way?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/jest/issues/2853#issuecomment-279023472, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAA0KAJACWu5BsHNvPbHRfhiM8ZUZYT9ks5rbKpwgaJpZM4L8fDc.

Maybe for first version we should not throw an error? We could just save the information about the version 1 in Jest 19 and error on future changes, what do you think?

It should definitely throw an error in the first version. If Jest doesn't detect this header, throw -> it means you are pre Jest 19 and the snapshot must be updated.

BTW, I'll be working on this tomorrow, but if anyone has time to deal with it today, don't hesitate!


suggest add requestDatas property in Curl class

when I set errorFunction that log all request data and response data, I can't get post data from \Curl\Curl object. So I sugest add request Datas in curl object.

Hi. Try to get from options:
$data = $instance->getOpt(CURLOPT_POSTFIELDS);


Which part in particular did you find to be outdated? I can work through all the instructions but knowing what you found would be good!


Extend Textformfield validation - programatical interaction is missing

I noticed there seems to be no way to interact with Textformfield validation programatically.
This is quite limiting. At least there should be mehtods to set or clear the errors of a Formfield.
But I suggest to rework the validation as a whole and add for example a structure like:

To TextFormField or the TextEditingController some methods:

addValidator(Validator validator)
removeValidator(Validator validator)
clearValidators()
setError(ValidationError error)
getErrors()
clearErrors()
onValidationStateChanges(ValidationState state=>{})
...?

classes for ValidationState, Validator and ValidationError

Some common Validators for email, length, phone number, regex and custom option

Arguable it would be favorable using an array  for validation errors. So every Validator class has assigned an error, and the TextFormField can have assigned various Validators. Maybe with an option to show only the first unmet Validationerror, or all of them.
These are just some ideas and need definately some more thought. Nevertheless the current validation functionality is imo too rudimentary and will not quite suffice the needs of many developers.

The lack of "clear validation error" method confuses users. They input the value, press submit, the form responds with validation error under the TextFormField, user clears the input, gets distracted, returns back and sees an empty field with an error message. Developers implementing programmatic way of clearing the field (with an (X) button or else) should be able to also clear the error message from validation.


Import & Export paths/settings?

Thanks for this awesome little tool. As a matter of fact I have a client that wanted to update a set of paths in a graphic so this could have been very helpful if only you supported im- and exporting the settings/paths ;-)
Could we expect something like this in the future?

I'm working on a function to edit the path code manually, but I'm not sure this is what you mean by "import and export the paths". Could you be more specific? :)

Editing the path code manually (and thus being able to copy-paste) is partially what I meant.
Manual editing would allow us to 'load' and 'save' path data (by copy-pasting). This, however, does not handle the SVG 'canvas' dimensions, etc. Pasting path data based on different dimensions would result in in—or partially—visible path's.
It would be better to be able to save all settings: path-data and app-settings (canvas dimensions, etc).
Off the top of my head a simple svg-path-builder.json object would be great, but even better would be to (also) have the option to save only the image (your-paths.svg).
Absolutely brilliant would be to be able to import an SVG containing path's and make that editable :-)

Oh ok, I get it. Well this is an excellent idea. I think the JSON file would be redundant, because you already have all the data in the SVG file.
Export is easy, and I can load paths from an SVG image by parsing the file. I'll add these functions for sure. :)

:+1: :rocket:


Remove symbols map from TSDB head

This saves memory, effort and locking.
Since every symbol is also added to postings, Symbols() can be implemented there instead.
This now has to build a map for deduplication, but Symbols() is only called for compaction, and gc() used to rebuild the symbols map after every compaction so not an additional cost.
Benchmark:
name            old time/op    new time/op    delta
CreateSeries-8    2.02µs ± 8%    1.50µs ± 1%  -25.78%  (p=0.016 n=5+4)

name            old alloc/op   new alloc/op   delta
CreateSeries-8    1.19kB ± 5%    1.08kB ± 5%   -8.85%  (p=0.008 n=5+5)

name            old allocs/op  new allocs/op  delta
CreateSeries-8      5.00 ± 0%      5.00 ± 0%     ~     (all equal)

/prombench main

Looking at the prombench dashboard, everything is very close between the two versions, so at least I haven't made things worse.
On the other hand it doesn't show up as any better, but in environments (e.g. Cortex) where many more appenders are used in parallel I am confident this will make an improvement.

/prombench cancel


Not a valid zip file

Hello,
I have been using the oci datasource plugin successfully for a couple of weeks now, but it stopped working.  When I try to install it, I get the following error message:
$ grafana-cli plugins install oci-datasource
installing oci-datasource @ 1.0.2
from: https://grafana.com/api/plugins/oci-datasource/versions/1.0.2/download
into: /var/lib/grafana/plugins
Error: ✗ zip: not a valid zip file
NAME:
Grafana cli plugins install - install  <plugin version (optional)>
USAGE:
Grafana cli plugins install [arguments...]
$

Hi @mikwagner,
Today the latest version(1.04) of the plugin is available only with the manual installation.
Linux
https://github.com/oracle/oci-grafana-plugin/blob/master/docs/linux.md#manually-installation
MACOS
https://github.com/oracle/oci-grafana-plugin/blob/master/docs/macos.md#manually-installation
p.s. We are working on your issue, It takes time to integrate the plugin  with grafana repository.


Drag slides with mouse

Currrently im showing this carousel in desktop with nearly six slides.
I want to drag the mulitple slides with mouse drag event.
Current implementation facilitates only one slide at a time.

Any updates??

Any updates??


about "NaNs in the encoded observations"

Thanks for your contribution！
How can I fix this problem, can you give me some advice?

By the way, will you upload the validation part, or how can i validate?

First, track down where the NaNs originate. Either the input observations contain some NaNs, or the weights became NaN during training due to instability or NaNs in the loss function.
I’ve used NaNs in the dataset to flag any invalid/illegal observations (e.g., far-away trajectories, occlusions) so that there is no leakage. After the mask is generated:
https://github.com/sisl/SceneInformer/blob/efce1976e939b08eb4608f4eb679a1179926e4e5/sceneinformer/model/encoder.py#L57
They should all be set to 0 to prevent any PyTorch errors done here: https://github.com/sisl/SceneInformer/blob/efce1976e939b08eb4608f4eb679a1179926e4e5/sceneinformer/model/encoder.py#L72
The same logic applies to polylines, so this issue shouldn't occur unless something has been commented out.
A similar approach is used for the loss function (sceneinformer/model/loss.py):
https://github.com/sisl/SceneInformer/blob/efce1976e939b08eb4608f4eb679a1179926e4e5/sceneinformer/model/loss.py#L23
Check that as well.
If none of the above applies, then it is most likely caused by training instability, in which case typical solutions should be applied, such as lowering the learning rate, clipping gradients, or increasing precision.
I’ve included the hyperparameters in the config file for easy adjustment:
https://github.com/sisl/SceneInformer/blob/efce1976e939b08eb4608f4eb679a1179926e4e5/configs/scene_informer.yaml#L113-L122
Hopefully, that's helpful.

By the way, will you upload the validation part, or how can i validate?

I'll try to find the exact script I've used.
Validation script just compares the FDE/ADE of the generated trajectories and compares the anchor occupancy (like in the loss function).


README misleading usage of react-router

Note: preact-router is simple and does not do orchestration for you. If you're looking for more complex solutions like nested routes and view composition, react-router works with preact as long as you alias in preact-compat.

I find the last part of this statement very misleading. It is not the case that react-router must be aliased with preact-compat. I deduced that from the example http://jsfiddle.net/developit/wtpfyfnt. I think it should be rephrased in clearer manner.
Have a great day!

@omarchehab98 that statement refers to react-router v4, which works out of the box with Preact.


Finetuning for the TVR task

I only have two gpu in my computer. When I use the command " horovodrun -np 2 python train_vcmr.py --config config/train-tvr-8gpu.json', the code meets deadlock. I attach the screenshot. Could you help me to solve this issue?

[1,1]<stdout>:Defaults for this optimization level are: [1,1]<stdout>:enabled                : True [1,1]<stdout>:opt_level              : O2 [1,1]<stdout>:cast_model_type        : torch.float16 [1,1]<stdout>:patch_torch_functions  : False [1,1]<stdout>:keep_batchnorm_fp32    : True [1,1]<stdout>:master_weights         : True [1,1]<stdout>:loss_scale             : dynamic [1,1]<stdout>:Processing user overrides (additional kwargs that are not None)... [1,1]<stdout>:After processing overrides, optimization options are: [1,1]<stdout>:enabled                : True [1,1]<stdout>:opt_level              : O2 [1,1]<stdout>:cast_model_type        : torch.float16 [1,1]<stdout>:patch_torch_functions  : False [1,1]<stdout>:keep_batchnorm_fp32    : True [1,1]<stdout>:master_weights         : True [1,1]<stdout>:loss_scale             : dynamic [1,0]<stdout>:Selected optimization level O2:  FP16 training with FP32 batchnorm and FP32 master weights. [1,0]<stdout>: [1,0]<stdout>:Defaults for this optimization level are: [1,0]<stdout>:enabled                : True [1,0]<stdout>:opt_level              : O2 [1,0]<stdout>:cast_model_type        : torch.float16 [1,0]<stdout>:patch_torch_functions  : False [1,0]<stdout>:keep_batchnorm_fp32    : True [1,0]<stdout>:master_weights         : True [1,0]<stdout>:loss_scale             : dynamic [1,0]<stdout>:Processing user overrides (additional kwargs that are not None)... [1,0]<stdout>:After processing overrides, optimization options are: [1,0]<stdout>:enabled                : True [1,0]<stdout>:opt_level              : O2 [1,0]<stdout>:cast_model_type        : torch.float16 [1,0]<stdout>:patch_torch_functions  : False [1,0]<stdout>:keep_batchnorm_fp32    : True [1,0]<stdout>:master_weights         : True [1,0]<stdout>:loss_scale             : dynamic [1,1]<stdout>:restorer is finished [1,0]<stdout>:restorer is finished [1,0]<stderr>:02/01/2021 22:11:46 - INFO - __main__ -   Waiting on git info.... [1,0]<stderr>:fatal: not a git repository (or any parent up to mount point /) [1,0]<stderr>:Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). [1,0]<stderr>:02/01/2021 22:11:46 - INFO - __main__ -   Git branch:  [1,0]<stderr>:fatal: not a git repository (or any parent up to mount point /) [1,0]<stderr>:Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). [1,0]<stderr>:02/01/2021 22:11:46 - INFO - __main__ -   Git SHA:  [1,0]<stderr>:fatal: not a git repository (or any parent up to mount point /) [1,0]<stderr>:Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). [1,0]<stderr>:02/01/2021 22:11:47 - ERROR - __main__ -   Command '['git', 'status', '--short']' returned non-zero exit status 128. [1,0]<stderr>:Traceback (most recent call last): [1,0]<stderr>:  File "/src/utils/save.py", line 51, in save_training_meta [1,0]<stderr>:    cwd=git_dir, universal_newlines=True).strip() [1,0]<stderr>:  File "/opt/conda/lib/python3.6/subprocess.py", line 356, in check_output [1,0]<stderr>:    **kwargs).stdout [1,0]<stderr>:  File "/opt/conda/lib/python3.6/subprocess.py", line 438, in run [1,0]<stderr>:    output=stdout, stderr=stderr) [1,0]<stderr>:subprocess.CalledProcessError: Command '['git', 'status', '--short']' returned non-zero exit status 128. [1,0]<stderr>:02/01/2021 22:11:47 - WARNING - __main__ -   Git info not found. Saving code into zip instead... [1,0]<stderr>:02/01/2021 22:11:47 - INFO - __main__ -   Saving code from /src to /storage/tvr_default/code.zip... [1,0]<stderr>:[2021-02-01 22:13:23.215038: W horovod/common/stall_inspector.cc:105] One or more tensors were submitted to be reduced, gathered or broadcasted by subset of ranks and are waiting for remainder of ranks for more than 60 seconds. This may indicate that different ranks are trying to submit different tensors or that only subset of ranks is submitting tensors, which will cause deadlock.  [1,0]<stderr>:Stalled ranks: [1,0]<stderr>:0: [allgather.noname.40] [1,0]<stderr>:[2021-02-01 22:14:23.216625: W horovod/common/stall_inspector.cc:105] One or more tensors were submitted to be reduced, gathered or broadcasted by subset of ranks and are waiting for remainder of ranks for more than 60 seconds. This may indicate that different ranks are trying to submit different tensors or that only subset of ranks is submitting tensors, which will cause deadlock.  [1,0]<stderr>:Stalled ranks: [1,0]<stderr>:0: [allgather.noname.40][1,0]<stderr>: [1,0]<stderr>:[2021-02-01 22:15:23.218786: W horovod/common/stall_inspector.cc:105] One or more tensors were submitted to be reduced, gathered or broadcasted by subset of ranks and are waiting for remainder of ranks for more than 60 seconds. This may indicate that different ranks are trying to submit different tensors or that only subset of ranks is submitting tensors, which will cause deadlock.  [1,0]<stderr>:Stalled ranks: [1,0]<stderr>:0: [allgather.noname.40] [1,0]<stderr>:[2021-02-01 22:16:23.223750: W horovod/common/stall_inspector.cc:105] One or more tensors were submitted to be reduced, gathered or broadcasted by subset of ranks and are waiting for remainder of ranks for more than 60 seconds. This may indicate that different ranks are trying to submit different tensors or that only subset of ranks is submitting tensors, which will cause deadlock.  [1,0]<stderr>:Stalled ranks: [1,0]<stderr>:0: [allgather.noname.40]

``
[1,0]:02/01/2021 22:11:30 - INFO - main -   Loading tvr train dataset /video/tv
[1,0]:02/01/2021 22:11:33 - INFO - main -   87153 samples loaded
[1,1]:
[1,0]:02/01/2021 22:11:33 - INFO - main -   Loading tvr validation dataset/video/tv
[1,0]:02/01/2021 22:11:33 - INFO - main -   10895 samples loaded
[1,0]:02/01/2021 22:11:33 - INFO - main -   Loading Inference Dataset /txt/tvr_val.db (val)
[1,0]:02/01/2021 22:11:34 - INFO - model.model -   Model config:
[1,0]:02/01/2021 22:11:34 - INFO - model.model -        Cross-Modal Transformer config: {
[1,0]:  "attention_probs_dropout_prob": 0.1,
[1,0]:  "hidden_act": "gelu",
[1,0]:  "hidden_dropout_prob": 0.1,
[1,0]:  "hidden_size": 768,
[1,0]:  "initializer_range": 0.02,
[1,0]:  "intermediate_size": 3072,
[1,0]:  "layer_norm_eps": 1e-12,
[1,0]:  "max_position_embeddings": 514,
[1,0]:  "num_attention_heads": 12,
[1,0]:  "num_hidden_layers": 6,
[1,0]:  "output_attentions": false,
[1,0]:  "output_hidden_states": false,
[1,0]:  "type_vocab_size": 2,
[1,0]:  "vocab_size": 50272
[1,0]:}
[1,0]:
[1,0]:02/01/2021 22:11:34 - INFO - model.model -        Temporal Transformer config: {
[1,0]:  "attention_probs_dropout_prob": 0.1,
[1,0]:  "hidden_act": "gelu",
[1,0]:  "hidden_dropout_prob": 0.1,
[1,0]:  "hidden_size": 768,
[1,0]:  "initializer_range": 0.02,
[1,0]:  "intermediate_size": 3072,
[1,0]:  "layer_norm_eps": 1e-12,
[1,0]:  "max_position_embeddings": 514,
[1,0]:  "num_attention_heads": 12,
[1,0]:  "num_hidden_layers": 3,
[1,0]:  "output_attentions": false,
[1,0]:  "output_hidden_states": false,
[1,0]:  "type_vocab_size": 2,
[1,0]:  "vocab_size": -1
[1,0]:}
[1,0]:
[1,0]:02/01/2021 22:11:34 - INFO - model.model -        QueryEncoder config: {
[1,0]:  "attention_probs_dropout_prob": 0.1,
[1,0]:  "hidden_act": "gelu",
[1,0]:  "hidden_dropout_prob": 0.1,
[1,0]:  "hidden_size": 768,
[1,0]:  "initializer_range": 0.02,
[1,0]:  "intermediate_size": 3072,
[1,0]:  "layer_norm_eps": 1e-12,
[1,0]:  "max_position_embeddings": 514,
[1,0]:  "num_attention_heads": 12,
[1,0]:  "num_hidden_layers": 0,
[1,0]:  "output_attentions": false,
[1,0]:  "output_hidden_states": false,
[1,0]:  "type_vocab_size": 1,
[1,0]:  "vocab_size": 50272
[1,0]:}
[1,0]:
[1,0]:02/01/2021 22:11:34 - INFO - model.model -        Decoder Transformer config: None
[1,1]:02/01/2021 22:11:34 - INFO - model.model -   Model config:
[1,1]:02/01/2021 22:11:34 - INFO - model.model -        Cross-Modal Transformer config: {
[1,1]:  "attention_probs_dropout_prob": 0.1,
[1,1]:  "hidden_act": "gelu",
[1,1]:  "hidden_dropout_prob": 0.1,
[1,1]:  "hidden_size": 768,
[1,1]:  "initializer_range": 0.02,
[1,1]:  "intermediate_size": 3072,
[1,1]:  "layer_norm_eps": 1e-12,
[1,1]:  "max_position_embeddings": 514,
[1,1]:  "num_attention_heads": 12,
[1,1]:  "num_hidden_layers": 6,
[1,1]:  "output_attentions": false,
[1,1]:  "output_hidden_states": false,
[1,1]:  "type_vocab_size": 2,
[1,1]:  "vocab_size": 50272
[1,1]:}
[1,1]:
[1,1]:02/01/2021 22:11:34 - INFO - model.model -        Temporal Transformer config: {
[1,1]:  "attention_probs_dropout_prob": 0.1,
[1,1]:  "hidden_act": "gelu",
[1,1]:  "hidden_dropout_prob": 0.1,
[1,1]:  "hidden_size": 768,
[1,1]:  "initializer_range": 0.02,
[1,1]:  "intermediate_size": 3072,
[1,1]:  "layer_norm_eps": 1e-12,
[1,1]:  "max_position_embeddings": 514,
[1,1]:  "num_attention_heads": 12,
[1,1]:  "num_hidden_layers": 3,
[1,1]:  "output_attentions": false,
[1,1]:  "output_hidden_states": false,
[1,1]:  "type_vocab_size": 2,
[1,1]:  "vocab_size": -1
[1,1]:}
[1,1]:
[1,1]:02/01/2021 22:11:34 - INFO - model.model -        QueryEncoder config: {
[1,1]:  "attention_probs_dropout_prob": 0.1,
[1,1]:  "hidden_act": "gelu",
[1,1]:  "hidden_dropout_prob": 0.1,
[1,1]:  "hidden_size": 768,
[1,1]:  "initializer_range": 0.02,
[1,1]:  "intermediate_size": 3072,
[1,1]:  "layer_norm_eps": 1e-12,
[1,1]:  "max_position_embeddings": 514,
[1,1]:  "num_attention_heads": 12,
[1,1]:  "num_hidden_layers": 0,
[1,1]:  "output_attentions": false,
[1,1]:  "output_hidden_states": false,
[1,1]:  "type_vocab_size": 1,
[1,1]:  "vocab_size": 50272
[1,1]:}
[1,1]:
[1,1]:02/01/2021 22:11:34 - INFO - model.model -        Decoder Transformer config: None
[1,1]:02/01/2021 22:11:45 - INFO - model.modeling_utils -   Weights from pretrained model not used in HeroForVcmr: ['vocab_padded']
[1,0]:02/01/2021 22:11:45 - INFO - model.modeling_utils -   Weights from pretrained model not used in HeroForVcmr: ['vocab_padded']
[1,1]:Selected optimization level O2:  FP16 training with FP32 batchnorm and FP32 master weights.
[1,1]:
[1,1]:Defaults for this optimization level are:
[1,1]:enabled                : True
[1,1]:opt_level              : O2
[1,1]:cast_model_type        : torch.float16
[1,1]:patch_torch_functions  : False
[1,1]:keep_batchnorm_fp32    : True
[1,1]:master_weights         : True
[1,1]:loss_scale             : dynamic
[1,1]:Processing user overrides (additional kwargs that are not None)...
[1,1]:After processing overrides, optimization options are:
[1,1]:enabled                : True
[1,1]:opt_level              : O2
[1,1]:cast_model_type        : torch.float16
[1,1]:patch_torch_functions  : False
[1,1]:keep_batchnorm_fp32    : True
[1,1]:master_weights         : True
[1,1]:loss_scale             : dynamic
[1,0]:Selected optimization level O2:  FP16 training with FP32 batchnorm and FP32 master weights.
[1,0]:
[1,0]:Defaults for this optimization level are:
[1,0]:enabled                : True
[1,0]:opt_level              : O2
[1,0]:cast_model_type        : torch.float16
[1,0]:patch_torch_functions  : False
[1,0]:keep_batchnorm_fp32    : True
[1,0]:master_weights         : True
[1,0]:loss_scale             : dynamic
[1,0]:Processing user overrides (additional kwargs that are not None)...
[1,0]:After processing overrides, optimization options are:
[1,0]:enabled                : True
[1,0]:opt_level              : O2
[1,0]:cast_model_type        : torch.float16
[1,0]:patch_torch_functions  : False
[1,0]:keep_batchnorm_fp32    : True
[1,0]:master_weights         : True
[1,0]:loss_scale             : dynamic
[1,1]:restorer is finished
[1,0]:restorer is finished
[1,0]:02/01/2021 22:11:46 - INFO - main -   Waiting on git info....
[1,0]:fatal: not a git repository (or any parent up to mount point /)
[1,0]:Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[1,0]:02/01/2021 22:11:46 - INFO - main -   Git branch:
[1,0]:fatal: not a git repository (or any parent up to mount point /)
[1,0]:Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[1,0]:02/01/2021 22:11:46 - INFO - main -   Git SHA:
[1,0]:fatal: not a git repository (or any parent up to mount point /)
[1,0]:Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[1,0]:02/01/2021 22:11:47 - ERROR - main -   Command '['git', 'status', '--short']' returned non-zero exit status 128.
[1,0]:Traceback (most recent call last):
[1,0]:  File "/src/utils/save.py", line 51, in save_training_meta
[1,0]:    cwd=git_dir, universal_newlines=True).strip()
[1,0]:  File "/opt/conda/lib/python3.6/subprocess.py", line 356, in check_output
[1,0]:    **kwargs).stdout
[1,0]:  File "/opt/conda/lib/python3.6/subprocess.py", line 438, in run
[1,0]:    output=stdout, stderr=stderr)
[1,0]:subprocess.CalledProcessError: Command '['git', 'status', '--short']' returned non-zero exit status 128.
[1,0]:02/01/2021 22:11:47 - WARNING - main -   Git info not found. Saving code into zip instead...
[1,0]:02/01/2021 22:11:47 - INFO - main -   Saving code from /src to /storage/tvr_default/code.zip...
[1,0]:[2021-02-01 22:13:23.215038: W horovod/common/stall_inspector.cc:105] One or more tensors were submitted to be reduced, gathered or broadcasted by subset of ranks and are waiting for remainder of ranks for more than 60 seconds. This may indicate that different ranks are trying to submit different tensors or that only subset of ranks is submitting tensors, which will cause deadlock.
[1,0]:Stalled ranks:
[1,0]:0: [allgather.noname.40]
[1,0]:[2021-02-01 22:14:23.216625: W horovod/common/stall_inspector.cc:105] One or more tensors were submitted to be reduced, gathered or broadcasted by subset of ranks and are waiting for remainder of ranks for more than 60 seconds. This may indicate that different ranks are trying to submit different tensors or that only subset of ranks is submitting tensors, which will cause deadlock.
[1,0]:Stalled ranks:
[1,0]:0: [allgather.noname.40][1,0]:
[1,0]:[2021-02-01 22:15:23.218786: W horovod/common/stall_inspector.cc:105] One or more tensors were submitted to be reduced, gathered or broadcasted by subset of ranks and are waiting for remainder of ranks for more than 60 seconds. This may indicate that different ranks are trying to submit different tensors or that only subset of ranks is submitting tensors, which will cause deadlock.
[1,0]:Stalled ranks:
[1,0]:0: [allgather.noname.40]
[1,0]:[2021-02-01 22:16:23.223750: W horovod/common/stall_inspector.cc:105] One or more tensors were submitted to be reduced, gathered or broadcasted by subset of ranks and are waiting for remainder of ranks for more than 60 seconds. This may indicate that different ranks are trying to submit different tensors or that only subset of ranks is submitting tensors, which will cause deadlock.
[1,0]:Stalled ranks:
[1,0]:0: [allgather.noname.40]

Hi,
Thanks for your interests in this project. During our experiments, we have observed the same error a few times. However, the error is not reproducible. When we repeat the exact experiment, the training runs smoothly. As the appearance of this error is rare and random at our end, we do not have any insight on why it was happening. You can also look into horovod repo, they may provide a more insightful explanation.
A quick fix is to run your experiments with 1 gpu. However,  it may results in lower performance and slower speed.

@linjieli222 OK, thanks for your reply. This problem may be related with our hardware. I run the experiments on single gpu, and it is fine. I have another request. Could you provide us a subset of data for pre-training? The code is somewhat complicated...

You can use TV dataset to conduct a relative "smaller"  pre-training experiment.

Closed due to inactivity.


the "What country issued your most recent passport?" question prepopulates with a country (probably of birth) even if the applicant HAS no passport or travel documents

Pretty sure this is fixed now


Question

Would you consider making the universalbeasiary compatible with The Betweenlands mod?

I had someone working on this, so I have a foundation of the work. Alas, he got busy with life and couldn't help further. Would you be willing to help provide these entries?

I'm so sorry! I forgot I posted this so long ago. I might be able to do that for you, though I am not a dev for that mod. And although I am in contact with the devs via their discord, I wouldn't want to bother them over this. A lot can be found on the betweenlands wiki. I can try drafting some things up. Thanks again for your response, and sorry for the late reply


Showcase Submission for challenges/175-3D-cube-applesoft-basic

Thank you Damian Gray for your contribution! A member of the Coding Train team will review it shortly.

Optimized spinning cube
Damian Gray

Oh, awesome, I will have to try this!


Allow passing fs.FS when calling functions

Issue
Close https://github.com/tetratelabs/wazero/issues/563
ToDo

[x] FSContext
[x] FSConfig
[x] FSKey
[x] Override fs.FS in WASI
[x] Add an example
[x] Unit test
[x] Example test

taking a look now, thanks!

ping me when you are ready for the next round. I'll keep a look out

@codefromthecrypt I think I finished reflecting your comments. There are a few concerns though.

I've added a test for WithFS to PathOpen only.

I'm not sure if it is enough or you may prefer another approach

FSConfig is still embedded into ModuleConfig

Do you think it should be extracted?

@mathetake I think this is on the right track. I'm going to be mostly away this evening until tomorrow. Can you make sure this gets past the finish line. Cheers!

I think this is on the right track :D

Meanwhile once done experimenting, maybe roll back the changes to the examples/wasi as we don't put experiemental things in that dir.

Reverted. https://github.com/tetratelabs/wazero/pull/571/commits/56714b8862959f661a9f408c8b61c774b2079af4

The main test needed would be to ensure that the context FS overrides vs adds to the one you expect. So one neat way to prove that is to have a test with the base FS having two files and the overlay having only one with a different content.

I wanted to do that, but I didn't find a good place to add the test. Also, it appeared to require somewhat larger changes. I probably missed something.
BTW, please feel free to add any commits. Sometimes it's faster to write code than to explain it in writing.

@knqyf263 thanks for all the work here. I'll be at the conference all day, but I can review and add commits to address any things, possibly today but more likely by tomorrow. In any case thanks for putting this together as you made it possible to land during a busy time 👍

ps I started fiddling with this, but might not push commits until tomorrow. Main thing I noticed was tension in the packages and made internal/fs instead. There are some tests in sys_test.go that should move into there also. I'll do it!

I landed the other PRs that would drift this, and ran out of time to finish this up (still at conference and should meet people :) ). I'll finish this soon

I force pushed a squash of the preceding work because the merges were getting hairy. I'll add a commit later with the changes I mentioned above

@mathetake I finished re-org, can you take a look and add a commit as needed? otherwise merge it.

@knqyf263 thank you so much for working to this! 🏅 👍

@codefromthecrypt Thanks for your help!
I saw you added internal/fs package. It looks good!


Add-on not running

Hello, how are you?
The application is not exporting the letters I created and this error occurs. What could have happened? Note: I used the examples and the same error occurs

Hey,
I think this is related to #71 I will push a fix this weekend

For a temporary fix you can change the language to English and add the basic cards to the model types

This should be fixed by 680e962
Please update and let me know if you are still having issues.
I saw another potential issues but looking into it


Split roles

This patch is removing all the roles. Those roles are now handled in
separate git repostiories:

https://github.com/ovirt/ovirt-ansible-manageiq
https://github.com/ovirt/ovirt-ansible-infra
https://github.com/ovirt/ovirt-ansible-vm-infra
https://github.com/ovirt/ovirt-ansible-cluster-upgrade
https://github.com/ovirt/ovirt-ansible-image-template

The host deploy roles are part of ovirt-engine.

ci buid please

ci buid please

ci build please

ci build please

ci build please

ci build please

ci build please


[TEST] Add Zookeeper 3.4 integration test

Why are the changes needed?
This PR proposes to add Testcontainers based Zookeeper 3.4 integration test, we need it to verify the compatibility if we upgrade Zookeeper client to the new version. See details in #1941
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

thanks for driving this. it will be great if the compatibility is not an issue for us to upgrade zk.
Using sql pipeline to verify this looks not that good to me, I recommand we do not go this way.
the sql tests are not built and suite for this

not that complete, we can not ensure the zk apis are all called, e.g. lock hehavior, error handling, zk acls, and those between ctl module and embedded zk. etc.
too heavy, it take much time for test for our own ci building, and too much resources from the entire ASF github account. Althougth the resources are free for us, we'd better make reasonable use of it.
if we add more tests to the trait, might make it even worse.

If we can build it individually to test all the apis between the kyuubi-ha(client) module and kyuubi-zookeeper(server), it will be much specific, complete and.resouece-friendly, WDYT?

If we can build it individually to test all the apis between the kyuubi-ha(client) module and kyuubi-zookeeper(server), it will be much specific, complete and.resouece-friendly, WDYT?

Make sense, I will try in this direction.

If we can build it individually to test all the apis between the kyuubi-ha(client) module and kyuubi-zookeeper(server), it will be much specific, complete and.resouece-friendly, WDYT?

Sorry for wrong close.  test all the apis seems more friendly. We can try it after #1989.

Codecov Report

Merging #2040 (680ce82) into master (7d66e9a) will decrease coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Current head 680ce82 differs from pull request most recent head a5f1e3a. Consider uploading reports for the commit a5f1e3a to get more accurate results

@@             Coverage Diff              @@
##             master    #2040      +/-   ##
============================================
- Coverage     60.70%   60.69%   -0.02%
  Complexity      108      108
============================================
  Files           320      320
  Lines         15468    15468
  Branches       1989     1989
============================================
- Hits           9390     9388       -2
- Misses         5273     5274       +1
- Partials        805      806       +1

Impacted Files
Coverage Δ

.../org/apache/kyuubi/operation/KyuubiOperation.scala
61.33% <0.00%> (-1.34%)
:arrow_down:

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
96.30% <0.00%> (-0.15%)
:arrow_down:

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 7d66e9a...a5f1e3a. Read the comment docs.

cc @yaooqinn @hddong, it's ready for review now

Thanks, merging to master


[Feature Request]: Add crop yield calculator used for farmers

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Add crop yield calculator used for farmers
Use Case
FArmers can calculate how much yeild they can obtain
Benefits
useful for farmers
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Can you please share any demo video of how this feature works... @KapuluruBhuvaneswariVspdbct

https://github.com/user-attachments/assets/f08b601e-febc-458f-afa7-db096b08ab71
please have a look it is used to calculate no of kgs of yield can be produced

wanted to work on this


ssl-opt.sh: Skip tests instead of conditional hard abort

Description
Closes #4471.

Replaced all occurrences of config.py with get_config_value_or_default.
Remove exit 1 hard abort and replaced with requires_config_value_at_least when MBEDTLS_X509_MAX_INTERMEDIATE_CA != MAX_IM_CA. The explanation given on hard exit was reworded and put in a comment.
Remove exit 1 hard abort when MAX_IN_LEN or MAX_OUT_LEN < 4096. This was replaced with requires_config_value_at_least + requires_max_content_len, and the threshold was adjusted for each test:

For the "Max Fragment Length" suite, it requires an amount that can fit both party's MFLs.
For two tests in the "Connection ID" suite, it requires MFL+1 so it triggers a buffer reallocation
For the "DTLS fragmenting" suite, it requires an amount that can fit both party's MFLs.

With this fix, tests should skip and continue through the rest of the suite when conditions don't match, resulting in lower or no false failures.
Requires Backporting
YES. The commits were cherry-picked and replayed in the relevant branches.

2.16
2.x

Additional Comments
I have tested my changes through rigorous manual testing and a bit of automated testing. I still could have missed something (and this is my first contribution), so please point anything of interest in the reviews.
Steps to test or reproduce
Run ssl-opt.sh -f "max int" / ssl-opt.sh -f "Max fragment length", or through other means like all.sh.

Rebased upon development and force-pushed.

For information, I used this script to validate the requires_max_content_len calls.

For information, I used this script to validate the requires_max_content_len calls.

Uh,oh. The script itself is brilliant and I thank you, but I just force-pushed 10 or so minutes ago and that seems to have convoluted the history between our PRs.


chore(cli-core): tagged release for double hooks invocation

Description of changes

Issue #, if available
#9996 testing if this closes this issue

Description of how you validated changes
testing locally
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

abandoning this, in favor of a tagged release with e2e tests enabled


apko: init at 0.3.3

Description of changes

Packages apko at 0.3.3
https://github.com/chainguard-dev/apko

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[X] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 169312 run on x86_64-linux 1

1 package built:

apko

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/882

No worries, we're all busy

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 169312 run on x86_64-linux 1

1 package built:

apko


Fixes #160 - Skip signature without access_key_id and secret_access_key

Thank you @xprazak2!

@xprazak2 Tagged as v0.13.3 :+1: Available on hex.pm as well as Github Release :+1:


{APIM} Fixed the --api-id parameter description

{APIM} Fixed the --api-id parameter description
Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Fixes #19673

APIM


ransak with kaminari seems not paginate.

In my controller:
@q = Shop.search(params[:q])
@shops = @q.result.page(params[:page]).per(10)
but I have no pagination.
There something wrong in my code?

I don't believe you have... result returns a relation -- it should allow any of the usual methods that kaminari would allow...

Sorry my mistake, it works very well, thank you.


To view this content, install and set up a web browsing app.

Steps to Reproduce

add package url_launcher
try to open url launch("https://play.google.com/redeem")

Expected results: You should see page where you can enter promo code
Actual results: You will see error "To view this content, install and set up a web browsing app."
But I have two browsers.
related issue:
https://github.com/flutter/flutter/issues/17596
Looks like there is some solution:
https://www.reddit.com/r/Android/comments/7lv04m/google_play_now_intercepts_all_links_to_the/druxaz0/

Logs

Analyzing fitmer...

   info • The value of the local variable 'streamId' isn't used • lib/data/audio_player.dart:64:9 • unused_local_variable
   info • The value of the local variable 'streamId' isn't used • lib/data/audio_player.dart:76:9 • unused_local_variable
   info • The value of the local variable 'streamId' isn't used • lib/data/audio_player.dart:88:9 • unused_local_variable
   info • The value of the local variable 'streamId' isn't used • lib/data/audio_player.dart:100:9 • unused_local_variable
   info • Unused import: 'storage.dart' • lib/data/exercise_repository.dart:4:8 • unused_import
   info • This function has a return type of 'String', but doesn't end with a return statement • lib/data/interstitial.dart:43:17 • missing_return
   info • This function has a return type of 'String', but doesn't end with a return statement • lib/data/interstitial.dart:51:17 • missing_return
   info • Name non-constant identifiers using lowerCamelCase • lib/data/storage.dart:36:11 • non_constant_identifier_names
   info • Name non-constant identifiers using lowerCamelCase • lib/data/storage.dart:37:13 • non_constant_identifier_names
   info • Unused import: 'package:flutter/material.dart' • test/widget_test.dart:8:8 • unused_import
   info • Unused import: 'package:flutter_app/main.dart' • test/widget_test.dart:11:8 • unused_import

11 issues found. (ran in 4.5s)

[✓] Flutter (Channel stable, v1.12.13+hotfix.9, on Mac OS X 10.14.5 18F132, locale en-RU)
    • Flutter version 1.12.13+hotfix.9 at /Users/vvv/Library/flutter
    • Framework revision f139b11009 (3 weeks ago), 2020-03-30 13:57:30 -0700
    • Engine revision af51afceb8
    • Dart version 2.7.2

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/vvv/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2.1, Build version 11B500
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.43.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.0

[✓] Connected device (1 available)
    • Redmi 4X • b2af1cc17d04 • android-arm64 • Android 7.1.2 (API 25)

• No issues found!

Hi @vivchar
as mentioned in the closing comment in the issue you linked,
this doesn't appear to be a flutter related problem;
moreover the workaround you proposed is aimed to Android's Intent
rather than flutter's url_launcher.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


Erroneous Account renaming in ACCT_IndividualAccounts_TDTM

We received a question in the HUB where a user was seeing non-Household accounts getting renamed with Household naming logic whenever a new Contact was added to that account. In this case, they had an Account with no recordtype that existing before HEDA was installed. With HEDA installed, when they modified or added a Contact to that Account, the household name was applied. There are a number of vulnerabilities in the ACCT_IndividualAccounts_TDTM that can lead to this behavior.
Contact On Delete Events:
If an existing contact linked to an existing account is Deleted, line 115 of the trigger handler is checking if the account should be renamed. That if statement is ONLY checking if there is an account Id. It is not checking if the Account is a household account. So the Account would be renamed for ALL (including blank) recordtypes.
AccountId is Cleared on an existing Contact:
If the Account field on an existing contact is CLEARED (not modified to another account, just removed entirely), line 174 is checking if the originally linked Account should be renamed...but it is not checking if that Account is a Household account. So the Account would be renamed for ALL (including blank) recordtypes.
The Household record type (HH_Account) is deleted from the org (or never installed)
It's possible that an org decides it doesn't need the Household record type and chooses to delete it. Or they may install HEDA directly from the package url (shown for each release) rather than use the installer. Many of the checks in the trigger handler are calling Util_Describe.getHhAccRecTypeID. That method looks at the available record types available on Account and returns the one where the developer name is HH_Account. If it does not find a RecordType with that name, the method returns null. So the comparison "if (c.Account.RecordTypeId == UTIL_Describe.getHhAccRecTypeID()) " is actually matching if the Account's RecordType is null. So Accounts with blank RecortTypeIds are treated as Households...and so are renamed when a linked Contact is edited or new Contact added. This is the exact scenario encountered by our Hub question. Ideally an additional check would see if the Account's RecordTypeId isn't blank (on lines 141 and 204).
Potential for Hierarchy_Settings.Automatic_Household_Naming__c to be null
A checkbox field can have 3 values: true, false and null. When a new field is added to to an existing custom settings object (or any object), that field is going to be Null for any existing records (not False). So the comparison "UTIL_CustomSettingsFacade.getSettings(). Automatic_Household_Naming__c != false" would succeed even if the actual value of the field is null instead of true). A better comparison would distinctly check for "== true" instead of != false. I'm not sure if this is actually happening in an org but noticed it as an additional vulnerability. The workaround in this case would just be to edit HEDA settings, uncheck "Automatic Household Naming" and click Save (this makes sure the value stored is actually False, not Null)

**lurch: add

Tracking W-026410

@kevinswiggum  are there any other ways to duplicate this issue besides:

Have an Account with no recordtype that existing before HEDA was installed.
Install HEDA- what are their settings in heda settings?
Modify a Contact on that Account, the household name was applied. (was this with any field modified, or just last name?)
Add a Contact to that Account, the household name was applied.

Included in beta release 1.70 (Beta 2)

Included in production release 1.70


off-by-one error in R.invoker

R.invoker(n, methodName) returns a function with length n + 1. This seems odd to me: I expect the function to have length n.

It's an interesting point.  If you turn a method of arity n into a function of arity n + 1, which value is the better expected value for the parameter?  The real point, of course, is to deal with possible optional arguments.
var index = R.invoker(2, 'indexOf');  // include the `fromIndex`
index('a', 5, 'a22: some value'); //=> 'a22: some value'.indexOf('a', 5) = 11

I don't see a strong reason to change this.  Do you think it would be significantly improved if the parameter reported the output function length rather than the length of the method you're trying to invoke?

Do you think it would be significantly improved if the parameter reported the output function length rather than the length of the method you're trying to invoke?

No. I now see that n relates to the method in question rather than the function we're creating. This seems reasonable.


ReferenceError: err is not defined

How to fix this?
/myproject/node_modules/mysql/lib/protocol/Parser.js:77
        throw err; // Rethrow non-MySQL errors
        ^

ReferenceError: err is not defined
    at Query._callback (database.js:37:13)
    at Query.Sequence.end (/myproject/node_modules/mysql/lib/protocol/sequences/Sequence.js:96:24)
    at Query._handleFinalResultPacket (/myproject/node_modules/mysql/lib/protocol/sequences/Query.js:144:8)
    at Query.OkPacket (/myproject/node_modules/mysql/lib/protocol/sequences/Query.js:78:10)
    at Protocol._parsePacket (/myproject/node_modules/mysql/lib/protocol/Protocol.js:280:23)
    at Parser.write (/myproject/node_modules/mysql/lib/protocol/Parser.js:73:12)
    at Protocol.write (/myproject/node_modules/mysql/lib/protocol/Protocol.js:39:16)
    at Socket.<anonymous> (/myproject/node_modules/mysql/lib/Connection.js:96:28)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)

Calling code:
  let dfd = q.defer();
  db.query(
    "UPDATE `markets` SET `rate` = ? WHERE `id` = ?",
    [rate, market.id],
    (error, results, fields) => {
      debug.log(1, error);
      debug.log(1, results);
      debug.log(1, fields);

      if (err) {
        dfd.reject(err);
        return;
      }
      dfd.resolve();
    }
  );

Version: 2.10.2
Node: v5.0.0

Found. It was a thrown Exception from my own code that got rerouted through your error handlers.

Hi @jublo, yep, you got it! Sorry for the confusion that Node.js creates when an error is re-thrown; the first line is the line of the throw vs the line of where the error occurred (the first one in the stack trace).

I have the same issue. But I am still not knowing how to handle the exception. Is there anyone tell me?

^^ +1 same here...
This is happening when I throw an exception from inside a mysql.connection.query callback

You can't throw from inside callback functions in Node.js, since there is no way to catch it. Node.js only gives you two options:

Be very careful not to throw any errors.
Wrap the full contents of your callback function body in a try-catch.

Strange, I don;t understand why does it work in some cases..

@atif089  how did you solve your problem, I am having the same issue. ....

@bitsofinfo it was not a problem in the library. It was a problem in my code. However, I don't know why it shows like it's a problem with Mysql.
Check your code, and follow what @dougwilson replied.

Hi


Mine

https://github.com/Ashry00/docs/blob/dependabot/npm_and_yarn/postcss-8.3.9/assets/images/contribution_cta.png

Do you have a bug to report regarding ShellJS?


wt32 sc01 v5.0 cant update

So tried to update to v5.0 and i get this when i use  1. esphome and this when i use  2.  tasmo.
1
Using 'COM6' as serial port.
Connecting....
Detecting chip type... ESP32
Connecting....
Chip Info:

Chip Family: ESP32
Chip Model: ESP32D0WDQ5 (revision 1)
Number of Cores: 2
Max CPU Frequency: 240MHz
Has Bluetooth: YES
Has Embedded Flash: NO
Has Factory-Calibrated ADC: YES
MAC Address: 24:6F:28:D2:61:C8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Flash Size: 4MB
Unexpected error: The firmware binary is invalid (magic byte=FF, should be E9)
2
Invalid head of packet (0x46)

The full binary is meant to be flashed with ESPtool, Flash Download Tools (ESP8266 & ESP32 & ESP32-S2) or Tasmota-PyFlasher :
You need to write the full binary to the ESP32 flash chip, starting at address 0x0:

Make sure to select the correct com port.
Tasmota-PyFlasher also works:

The ota binary can be uploaded via the web UI, if the plate has been previously flashed with openHASP 0.4.0.
The ESPhome-Flasher expects the ota binary to be written to address 0x10000. You can flash the ota firmware directly using ESPhome-Flasher, but the ESP only boots correctly if the bootloader and partitiontable are already present.

Oh ya sorry brain fart. Mix them up  again sorry.


MyPy plugin?

MyPy is very useful when detecting @abtractmethod definitions that are unfilled.
I don't think that there's a clean way to do that with just type-hints. Maybe this can be added via a plugin?

Yes, a mypy plugin would be great and I would most likely use it myself. I think it could also work as a reference implementation for suggesting standardizing Abstract in the standard library.


Creating a Faunal List with the Filters

Feature or enhancement
When getting a resulting list of Taxon Names within a specific geographic area, the total number of taxon names resulting may be overestimated because of the species that include subspecies, since TW consider them both in the resulting list.
In OSF we can filter that with an option of Nomenclature Rank that is called: "subspecies and species that don't have subspecies".
In the last session @mjy proposed to solve this through the "linker"whit a specification of a geographic scope (faunal list) so we can download this Faunal List considering each species o subspecies just once.
Location
Filters
Screenshot, napkin sketch of interface, or conceptual description
No response
Your role
Curator

@mabecabrera this was OTU filter, right?
I think I now know how to make the query, so maybe we can integrate it directly.
Note to self: leaves.

This will fail, if you have distribution on species, but no distribution on subspecies (probably).

Here is where we need OTUs with valid names really, that's all.

It was the Nomenclature Filter.
I first used the Filter OTUs, to select an area, and a family. All this in the OTU Filter. I then used the unified filter to take those OTUs to the Nomenclature Filter so I could have a list only of the valid names for those OTUs.
That is how I created the Faunal list.
I tried to do it the way Matt said in that session the previous week (Using first the Filter Nomenclature), but having first all the valid taxon names that belong to a family and then moving that to the OTU filter... I was having a list of OTUs... but I needed Taxon Names... so I discarded that path.
Am I right?

Understood @mabecabrera, you are correct in terms of trying to get the result you want.  We had a little more discussion on this with a couple more insights.  Might be able to run some experimental reports in the near future, we'll see.


Add URI encoding and decoding on login redirect

Fixes #595 exactly as outlined by the issue author.

Coverage remained the same at 70.918% when pulling fd04ce659158a02174454dd2eb950856ee94d759 on fix/next-uri-encoding into 80cf1a4e3b53a6608cb89a0ba17fdec653415761 on master.

Coverage remained the same at 70.918% when pulling fd04ce659158a02174454dd2eb950856ee94d759 on fix/next-uri-encoding into 80cf1a4e3b53a6608cb89a0ba17fdec653415761 on master.

Coverage remained the same at 70.918% when pulling fd04ce659158a02174454dd2eb950856ee94d759 on fix/next-uri-encoding into 80cf1a4e3b53a6608cb89a0ba17fdec653415761 on master.


Update cats-effect, cats-effect-testkit to 3.5.3

About this PR
📦 Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-testkit

from 3.5.2 to 3.5.3
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #62.


Add readConcern and collation support

readConcern
The readConcern options is not intuitive and have to be an object containing level property.
If we just pass string to it, the native driver will throw error.
See Automattic/mongoose#6777 for the motivation
Before this pull request
Model.find().setOptions({ readConcern: { level: 'linearizable' } })
Model.find().maxTime(5000)

After this pull request
Model.find().readConcern('linearizable')
Model.find().readConcern('lz')

maxTimeMS
Also, this pull request make maxTimeMS alias of maxTime.
So the syntax is now closer to mongo shell.
See Automattic/mongoose#6777 for the motivation
Before this pull request
Model.find().maxTime(5000)

After this pull request
Model.find().maxTime(5000) // work
Model.find().maxTimeMS(5000) // also work. same syntax with mongo shell

collation
Add collation support
Before this pull request
Model.find({ caseInsensitive: 'abc' }).setOptions({ collation: { locale: "en_US", strength: 1} })

After this pull request
Model.find({ caseInsensitive: 'abc' }).collation({ locale: "en_US", strength: 1} })

mongoose currently inherit mquery and extend collation support.
mongoose may remove the implementation if using this version of mquery

@Fonger quick question: do you use mquery directly or do you go through mongoose?

@vkarpov15 Thanks for the merge. #106 fix some documentation errors.
I use both. I'm currently working on a project that use mquery as template in browser and convert it to  pass all of the options, conditions... etc to backend to process the query in node
I would like to add eslint for this project to keep consistent coding style. Like eliminate the mix use of == and ===
Any idea on this?

@fonger +1 for the addition of eslint

@Fonger thanks for eslint! That's an interesting approach. Mongoose has been slowly but surely moving away from using mquery internally because its proven to be a tangled abstraction and there are several features in Mongoose queries that aren't in mquery. But I've seen several projects popping up recently that use mquery so I'm thinking about whether we should focus on mquery more or focus on exporting something more like mquery from mongoose. I have a couple questions:

What do you use to serialize mquery for HTTP?
If Mongoose's browser lib included a serializable query builder, would you use that instead of mquery?
If Mongoose's browser lib supported connecting to the browser and executing queries via MongoDB Stitch, would you use that instead or would you still prefer to send queries to a server for validation?

@vkarpov15
I prefer to support more query helpers in mquery and working on it. #108 support write concern now
The best is to make the syntax compatible with mongo shell to avoid confusion as the goals shown in README
What do you use to serialize mquery for HTTP?
I use mongodb-extjson to preserve data types such as ObjectId, Date, NumberLong, ...etc. Because JSON only support string, number, boolean and plain
object.
I have another version using socket.io and transfer with binary. To enhance the performance, in this websocket version, I serialize and encode it via bson which is compatible with browser, sending with websocket binary data and then deserializing using bson-ext because it uses native C++ module in backend
If Mongoose's browser lib included a serializable query builder, would you use that instead of mquery?
I don't know at this moment. In fact in my project i'm using mongoose for developer accounts only because I need custom validation. The actually mongodb operations are done by calling native mongodb driver.
If Mongoose's browser lib supported connecting to the browser and executing queries via MongoDB Stitch, would you use that instead or would you still prefer to send queries to a server for validation?
I have never heard of MongoDB Stitch before and I googled it and find it fantastic!
I think I'm developing similar service like MongoDB Stich. When I finish this project I'll open source it.
It's great to support MongoDB Stitch but I think it should be created in another npm package because it is not really related to mongoose.

I'm thinking about whether we should focus on mquery more or focus on
exporting something more like mquery from mongoose

mquery literally was exported from Mongoose. That is why it came to exist.
+1 to enhancing this.
On Mon, Jul 30, 2018, 4:43 PM Fonger<EMAIL_ADDRESS>wrote:

@vkarpov15 https://github.com/vkarpov15
I prefer to support more query helpers in mquery and working on it. #108
https://github.com/aheckmann/mquery/pull/108 support write concern now
The best is to make the syntax compatible with mongo shell to avoid
confusion as the goals shown in README
What do you use to serialize mquery for HTTP?
I use mongodb-extjson https://github.com/mongodb-js/mongodb-extjson to
preserve data types such as ObjectId, Date, NumberLong, ...etc. Because
JSON only support string, number, boolean and plain
object.
I have another version using socket.io and transfer with binary. To
enhance the performance, in this websocket version, I serialize and encode
it via bson https://github.com/mongodb/js-bson which is compatible with
browser, sending with websocket binary data and then deserializing using
bson-ext https://github.com/mongodb-js/bson-ext because it uses native
C++ module in backend
If Mongoose's browser lib included a serializable query builder, would you
use that instead of mquery?
I don't know at this moment. In fact in my project i'm using mongoose for
developer accounts only because I need custom validation. The actually
mongodb operations are done by calling native mongodb driver.
If Mongoose's browser lib supported connecting to the browser and
executing queries via MongoDB Stitch, would you use that instead or would
you still prefer to send queries to a server for validation?
I have never heard of MongoDB Stitch before and I googled it and find it
fantastic!
I think I'm developing similar service like MongoDB Stich. When I finish
this project I'll open source it.
It's great to support MongoDB Stitch but I think it should be created in
another npm package because it is not really related to mongoose.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aheckmann/mquery/pull/105#issuecomment-409047389, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKLsi13P3Y47H7-ccqY1poRM47A0sqAks5uL5o-gaJpZM4VlQqj
.

Yeah, I meant winding mquery back into mongoose, because adding new functionality to both mongoose and mquery is cumbersome. Not actively pushing on that, just an idea to think about.


Added functionality to I18n::Backend::Cache to clear cache when trans…

Restored changes from https://github.com/svenfuchs/i18n/pull/70, because original repo is missing. Still need to address comments in original PR

@stereobooster Are you still completing this PR or is it good for review now? It's a little unclear from here, so I thought I'd ask.

I'm not sure if this is the right approach. WDYT?
Plus need to fix tests

This seems like a fine approach. Let me know when you're done!

The problem is that
a. we store all keys in a set, which can lead to memory leak
b. deleting keys from store one by one is ineffective
This is should be done some other way, for example, configuration which would instruct to use cache reset (by default it will be off)
def store_translations(locale, data, options = {})
  I18n.cache_store.clear if config.clear_cache_on_store_translations
  super
end

So user would need to use dedicated cache for this feature


Correct link URL to be local, not absolute

This was missed by the review of the original pull request.

:+1:


[Bug] expand and collapse don't work on json view

after manually expand or collapse:

~But the bug can not be reproduced everytime.~
How to reproduce:

click Expand
collapse any one of inner levels
click Expand again

It seems json view will remember user's collapse level and ignore the collapse property.

Yes, it is designed.
See: https://github.com/mac-s-g/react-json-view/issues/166#issuecomment-365442432

Decide to remove Extend & Collapse buttons.


!##[TRENDING!]!## Sophie Rain Leaked Video Viral Files Updated -TikTok Star - 3MF8P

27 seconds ago Sophie Rain L𝚎aked Video Viral On Social Media. Θ(ＷＡＴＣＨ VIDEO𝕊) Sophie Rain Viral ᴠɪᴅᴇᴏ ʟᴇᴀᴋᴇᴅ Update Files Trending On Social Media X Telegram
L𝚎aked Video Sophie Rain Original Video Viral Video L𝚎aked on X Twitter Telegram
Sophie Rain Dark Video Female Sophie Rain Dark Video Link Viral On Social Media X TikTok Trending Now
Sophie Rain Original Video video took the internet by storm and amazed viewers on various social media platforms. Sophie Rain , a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Sophie Rain Original Video Viral Video L𝚎aked on X Twitter
Sophie Rain Original Video video oficial twitter
L𝚎aked Video Sophie Rain Original Video Viral Video L𝚎aked on X Twitter.
.
.
.
.
.
Sophie Rain's latest video has taken the internet by storm, sparking lively discussions across various social media platforms. The rising digital influencer, known for her captivating content—especially her recent Spiderman-themed video—has experienced a massive surge in popularity. Fans are eagerly awaiting the full version, while audiences flock to Instagram, X (formerly Twitter), and Discord to engage with her latest creation.
As excitement continues to grow, fans are actively sharing their thoughts online, highlighting the crucial role social media plays in propelling creators like Sophie Rain into the spotlight. With her unique style and creative approach, she has made a significant impact on the digital scene, leaving fans excited for what’s to come next. The viral success of her video further underscores the power of social media in boosting visibility and fostering stronger connections between creators and their audiences.
.
..
In the digital age, content spreads at an unprecedented speed. Social media has transformed how we communicate, share, and consume information. From trending topics to viral videos, platforms like Twitter, TikTok, Instagram, and Facebook have become central to modern discourse. Amid this environment, the name "Sophie Rain" has gained significant attention following the leak of a controversial video. The so-called "Sophie Rain Leaked video" became viral, making waves on various social media platforms and sparking a debate on privacy, online safety, and the implications of going viral.
This article aims to delve into the phenomenon of the Sophie Rain Leaked video, examining its origins, how it became viral, and the broader implications of such content in the age of social media virality. It also explores the ethical and legal dimensions surrounding Leaked videos and the influence of digital culture on personal privacy.zxvs.
.
..//

cvbcvb

bvnvb

cvv


Docker setup rework

Hi Hi,
Not sure where the project currently lays regarding the docker support but here could be the begging of a plan for it.
An option would be to "micro-service" it, this PR goes into this direction
If you find it useful I can also rework the other FreeTAKTeam projects to have an easy docker compose stack that could look like this:
version: '3'

Services:
    tak-server: {}
    tak-server-ui: {}
    tak-server-map: {}

How would you feel about it ?

@RadioAndrea please review and comment

I like this, just the service name I think should be changed to something like free-tak-server-ui or fts-ui to ensure delineation from the US Gov tak offering, as they are now also providing some docker images.
Presumably someone may operate both and we should, by default, try to prevent confusion.

Make sense :ok_hand: thanks for the review !

@naman108 please review for impacts on the rest of FTS

I approve, but haven't heard from @naman108 yet.
Once this is merged in, I'll also move the changes to the FTS-hub for the prodbuilds

All changes to config.py look good, so that's an ok on the code side.


Client/Server plugin and Discovery

This PR:

converts nsmdp into a new NSM plugin,
adds DiscoverRequest handler for server side and call it from nsm client,
fixes several issues discovered during debugging.

Signed-off-by: Serguei Bezverkhi<EMAIL_ADDRESS>

Log from the client, it prints discovered via API call network services:
time="2018-07-01T17:06:36Z" level=info msg="nsm client: connection to nsm server on socket: /var/lib/networkservicemesh/nsm.ligato.io.sock succeeded."
time="2018-07-01T17:06:38Z" level=info msg="nsm client: %d NetworkServices discovered from Local NSM.1"
time="2018-07-01T17:06:38Z" level=info msg="nsm client: pod's namespace is [NS(6: 3,<PHONE_NUMBER>)]"
time="2018-07-01T17:06:38Z" level=info msg="nsm client: pod's interfaces:"
time="2018-07-01T17:06:38Z" level=info msg="Name: lo Type: device"
time="2018-07-01T17:06:38Z" level=info msg="Name: eth0 Type: veth"
time="2018-07-01T17:06:38Z" level=info msg="nsm client: requested network services:"
time="2018-07-01T17:06:38Z" level=info msg="&{Name:network-service-1 ServiceInterface:[{Type:KERNEL_INTERFACE Metadata:name:\"interface-1\"  Preference:FIRST Parmeters:<nil> XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0} {Type:MEM_INTERFACE Metadata:name:\"interface-2\"  Preference:THIRD Parmeters:<nil> XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}]}"
time="2018-07-01T17:06:38Z" level=info msg="&{Name:network-service-2 ServiceInterface:[{Type:KERNEL_INTERFACE Metadata:name:\"interface-3\"  Preference:FIRST Parmeters:<nil> XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}]}"
time="2018-07-01T17:06:38Z" level=info msg="nsm client: initialization is completed successfully, exiting..."

nsm client log indicating discovery of 1 NetworkService via API
time="2018-07-01T17:20:21Z" level=info msg="nsm client: connection to nsm server on socket: /var/lib/networkservicemesh/nsm.ligato.io.sock succeeded."
time="2018-07-01T17:20:23Z" level=info msg="nsm client: 1 NetworkServices discovered from Local NSM."

@mestery @edwarnicke @fkautz  PTAL when you have time..


fix(seed): Best practice for radio button

Closes #15946

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new functionality)
[x] Breaking change (fix or feature that would change existing functionality)
[x] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #XXXXX
Description

Also please fill the checklist in the PR description above

It's telling me the Travis CI build failed. I'm not sure what went wrong there.

There is an invalid + character in the new changes. This is also easily caught when you run tests and locally check by running the local server.
npm run test

npm run develop

Sorry about that. I'm new to all this.

:sparkles: :sparkles: LGTM. :sparkles: :sparkles:
Real nice work! Sorry about so many change requests, its just a part of reviewing.
Thanks @darthm3gatron,  for this pull request and contributing to the code-base for the first time.
Happy contributing!


Support both API v1 and v2 at the same time

With this commit we allow user to quickly switch between v1 and v2 per API call:
client = AnsibleTowerClient::Connection.new(
  :base_url   => 'http://localhost:54321',
  :username   => 'admin',
  :password   => 'password'
)

# Credentials from API v1
client.api.credentials.all.each do |c|
  pp c
end

# Credentials from API v2
client.api2.credentials.all.each do |c|
  pp c
end

This way migrating ManageIQ to use v2 will be easier because we can migrate API call by API call.
Related issue: https://github.com/ManageIQ/manageiq-providers-ansible_tower/issues/96

@jameswnl this PR is a result of our conversation on the linked issue. As far as I've tested, everything works as intended if we stick with API v1 for other calls and only use v2 to fetch credentials. The only difference then is that also credentials that are using custom credential types are also visible/usable.
I kindly ask for review.

Anyone? :)

I don't like the two different api and api2 methods.  If anything, I think it would be nicer to have client.api default to the latest available version and optionally allow client.api(:version => "v1") to support using a specific version.

Thanks for the comment @bdunne . Since we're supporting only the first v2 response for now (˙client.api.credentials`), I think we'd better default to API v1 and optionally allow v2. Will come up with  code tomorrow.

I'd prefer to default to the latest in the gem and override it where it's used in ManageIQ

Done as you suggest @bdunne . Kindly ask for another pass of review.

@bdunne @syncrou @miha-plesko  This PR seems to have remove the connection caching altogether...was that intentional and if so, why?
Before @connection memoizing variable: https://github.com/ansible/ansible_tower_client_ruby/pull/107/files#diff-68ecb5d8417901430d83bc5f650e766eL15
After no memoization: https://github.com/ansible/ansible_tower_client_ruby/pull/107/files#diff-68ecb5d8417901430d83bc5f650e766eR35

@Fryguy connection caching is still there, only it was moved a bit to allow for switching between v1 and v2: https://github.com/ansible/ansible_tower_client_ruby/pull/107/files#diff-68ecb5d8417901430d83bc5f650e766eR46
Before:
conn = AnsibleTowerClient::Connection.new(...) # "global" memoization via @connection
conn.api.credentials
conn.api.inventories
...

After:
conn = AnsibleTowerClient::Connection.new(...)
conn.api(:version => 1).credentials # memoization via @api[1] for AWX API v1
conn.api(:version => 1).inventories

conn.api(:version => 2).credentials # memoization via @api[2] for AWX API v2
conn.api(:version => 2).inventories
...

Reason to implement memoization per api version instead globally is that URL is different for v1 and v2, hence we need to memoize the two separately:
http://localhost:54321/api/v1 # url for API v1
http://localhost:54321/api/v2 # url for API v2 (on the same Ansible Tower instance)

Please let me know if my explanation makes any sense!


Auto-fix line length (E501)

Does auto-fix support E501? It doesn't seem to auto-fix line lengths in my setup, wondering if this is by design or a bug on my side.

E501 does not support auto-fix. I'd recommend using a formatter instead e.g. Black or #1904

Ah ok thanks, I'll try using Black for now.


Deployment commit for prod-beta

Merged stage-stable branch to prod-beta.
Use latest commit to update namespace ref in app-interface repo. Don't use merge commit, SHAs must be unique when images are created for each branch.

Codecov Report
Attention: Patch coverage is 10.52632% with 34 lines in your changes missing coverage. Please review.

Project coverage is 65.18%. Comparing base (6c8e39d) to head (dbc6d81).

Files
Patch %
Lines

...ngs/costModels/costModelWizard/costModelWizard.tsx
7.14%
26 Missing :warning:

src/components/drawers/exports/exportsTable.tsx
25.00%
6 Missing :warning:

src/routes/components/dataTable/dataTable.tsx
0.00%
2 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##           prod-beta    #3913      +/-   ##
=============================================
- Coverage      65.72%   65.18%   -0.55%
=============================================
  Files            515      519       +4
  Lines          10001    10138     +137
  Branches        2357     2255     -102
=============================================
+ Hits            6573     6608      +35
- Misses          3180     3526     +346
+ Partials         248        4     -244

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


"parseFromDeveloperNoteTrimCharacters" parameter missing in Sync-XliffTranslations / Test-BcAppXliffTranslations

Hi @rvanbekkum ,
We've finally moved the translation logic to our pipelines and are 99% close to auto-generate translations as part of the build process. However, we lack support for the parseFromDeveloperNoteTrimCharacters setting in PS Xliff Sync (although it is supported in VS Code > https://github.com/rvanbekkum/vsc-xliff-sync/issues/100)
Our PS script currently looks like this ...
...
$SyncAdditionalParameters = @{
    "preserveTargetAttributesOrder"   = $true
    "findBySource"                    = $true
    "findBySourceAndDeveloperNote"    = $true
    "parseFromDeveloperNote"          = $true
    "parseFromDeveloperNoteOverwrite" = $true
    "parseFromDeveloperNoteSeparator" = "||"
    # parseFromDeveloperNoteTrimCharacters" = "\""    ### <<< This is currently missing
}

...

Test-BcAppXliffTranslations -printProblems -appFolders $AppFolders -translationRules @("OptionMemberCount", "OptionLeadingSpaces", "Placeholders", "ConsecutiveSpacesConsistent", "ConsecutiveSpacesExist") -restrictErrorsToLanguages @("nl-BE", "nl-NL") -buildProjectFolder $BuildProjectFolder -syncAdditionalParameters $SyncAdditionalParameters -AzureDevOps $AzureDevOps # -reportProgress -FormatTranslationUnit

... but we would like to specify parseFromDeveloperNoteTrimCharacters similar to how we can specify this in VS Code.
Any chance of integrating below commit into the PS version of XLiff Sync?
https://github.com/rvanbekkum/vsc-xliff-sync/commit/fc0ba6a4fba177da831bf81101d76e33982286a8

Hi @fvet,
I think that should be possible with limited effort, so I'll add it soon.

@rvanbekkum Sorry for being pushy, but any update on the progress of this issue?

Hi @fvet,
I have just pushed a commit which will add support for the parseFromDeveloperNoteTrimCharacters parameter.
I will need to test and release it. If you have any feedback then please let me know as well.
The implementation is taken from the vsc-xliff-sync implementation and converted to PowerShell.

The new parameter is now available in version <IP_ADDRESS>.


Add Git cli calls into output channel

1/2 main <- this <- #2226
This PR moves all calls made to Git into the DVC output channel. This will make the user aware of these calls and should let them debug should something go wrong.
Demo
https://user-images.githubusercontent.com/37993418/185831174-2e480fb5-f36f-40f3-9116-d0559cc5148d.mov

Will have to integrate with #2091


[TK-18] Add the "Return a Book" page

Pull Request
Story ID: [TK-18]
Title: [TK-18] Add the "Return a Book" page
Card URL: https://trello.com/c/duzwLwlI
Author: @paminicha


Introduce Profile Atom

What does this change?
Introduce the Profile Atom based on the amazing recent work by @nitro-marky on the Guide Atom.

+1


Add Frogs as CODEOWNERS

Description
Changes proposed in this pull request:

Add Frogs as CODEOWNERS for ~Connectivity Adapter and~ Runtime Provisioner

Please, check if I added it to the correct file :D Currently there are CODEOWNERS, OWNERS and OWNERS_ALIASES files and I'm not quite sure if I did it right

As far as I know, the Compass changes will be updated to this repository. I already merged a PR with the same change. I have a problem with retriggering the license/cla status so I'll just close this PR and wait for the Compass unification 😄


[Bug]: Page unresponsive due to multiple calls of ds schema on action change

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Page becomes unresponsive due to large number of tables in postgres db due to multiple schema calls on action change.
Slack thread : https://theappsmith.slack.com/archives/C0341RERY4R/p1692014095222679
Steps To Reproduce

Create a postgres datasource having large number of tables
Create multiple action for the above datasource
Observe on switching between actions the page becomes unresponsive

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Cloud

Can i know the status or when this issue can be resolved ?


Exercise 6... no looping allowed?

I understand if the goal is to get the total-n00b (me :point_left:) to write a solution without any loops, but it isn't terribly clear that you can't do that based on the previous lessons and the exercises instructions. I got a message about using a for loop without a "constant" because it relies on the param, and a message that while's were 'not allowed' or something to that effect. I remember recursion was out, but I tried it just for kicks.
If there are such contraints in general, maybe during the intro to looping these constraints could be made known?

Yeah I agree with this. A little further explanation here would've helped.

Wouldn't it be better to just make an exercise which squares a matrix, rather than forcing the student to do all sorts of ugly decision making due to the fact that looping and recursion aren't possible? It's also unlikely that you would raise a matrix to a power like this, you would likely use a diagonalization method or use a matrix library to do it, and then pass the new matrix to the shader. A function which squares a matrix is sufficient to demonstrate matrix multiplication, or you could create a function which multiplies a vector by a matrix, which was in the lesson and is highly relevant to graphics programming.

I am having the same problem, though n is given 1<n<16, I can't figure out a way to tell the machine = =

@sparkmorry I solved it like this:


Revert #6591 to fix issue with failed tests

Signed-off-by: jgallucci32<EMAIL_ADDRESS>

/ok-to-test

LGTM
but I think @mheon had another thought elsewhere and I can't find it quickly.

@TomSweeneyRedHat I did a rebase with the recent #6640 push from @edsantiago to verify his change in log testing still works and it has passed all the checks. This is ready for review.

/assign @umohnani8

@jgallucci32 This looks fine to me because it removes functionality, but does the logs --follow code work correctly after this reversal?
Does podman logs -f CTR work if Container is stopped? Paused?
If I am doing podman logs -F CTR and CTR is stopped, does podman logs stop?
LGTM

This is all green now and I think will solve a number of CI tests issues once merged.

/lgtm
/approve

Ok Thanks @jgallucci32


All I can say is 'useless'

Another guide that just trails off into the world of useless. Start here to set up the service principal:
https://learn.microsoft.com/en-us/azure/databricks/dev-tools/service-principals
Follow the link at the end to set up the service principal authentication:
https://learn.microsoft.com/en-us/azure/databricks/dev-tools/auth#azure-sp-auth
The documentation is completely useless from here. I've just followed a guide to set something up. The next logical guide is how to use it. Instead a list of environment variables for a multitude of tools is rattled off and then simply ceases. No document is better than this rubbish.

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

ID: 5025a8d1-514b-406a-de38-32a464e9ddc8
Version Independent ID: 5025a8d1-514b-406a-de38-32a464e9ddc8
Content: Authentication for Azure Databricks automation - Azure Databricks
Content Source: databricks/dev-tools/auth.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

This is the kind of docco I was expecting after the service principal setup guide:
https://learn.microsoft.com/en-us/azure/databricks/dev-tools/service-prin-aad-token
Combined with setting the SP's permissions inside Databricks for databases and views, I was able to get a token and then query the Databricks API. Hooray! :D

@joelraymondgraves
Thanks for your feedback! We will investigate and update as appropriate.

@joelraymondgraves
I've delegated this to @mssaperla, a content author, to review and share their valuable insights.

Thanks for providing feedback that helps improve our documentation. We've created an internal work item (DOC-11127) to address your feedback. The timeline for resolution varies based on resourcing.
#please-close