Script to detect status of VM agent is incorrect.

I'm using Az module version 3.5.0
This section of Powershell does not detect the current status of the VM agent:
$vms = Get-AzVM
foreach ($vm in $vms) {
$agent = $vm | Select -ExpandProperty OSProfile | Select -ExpandProperty Windowsconfiguration | Select ProvisionVMAgent
Write-Host $vm.Name $agent.ProvisionVMAgent
}
This ProvisionVMAgent property is there for marketplace images that have the agent installed on creation.
The way you need to do it is to run: "$vm = Get-AZVM -Name "VMName" -ResourceGroupName "RGName" -Status". You can't run -Status on a group of VMs, so you have to get the specific one. From there, you check the status with:
$vm.VMwagent.Statuses[0]
So, to get a list of VM names and the GA status, I guess you would have to run it twice. For example:
$vm_list = Get-AZVM
foreach ($vm in $vm_list)
{
$vm_status = Get-AZVM -Name $Vm.Name -ResourceGroupName $Vm.ResourceGroupName -Status
$guest_agent_status = $vm_status.VMAgent.Statuses
Write-Output $vm.Name   $guest_agent_status.DisplayStatus
}

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

ID: ab75f449-661d-bd1e-3ebd-61e2384a911a
Version Independent ID: e7c93a31-6076-26b8-a53d-d36df01ec6bc
Content: Azure Virtual Machine Agent Overview
Content Source: articles/virtual-machines/extensions/agent-windows.md
Service: virtual-machines-windows
GitHub Login: @mimckitt
Microsoft Alias: akjosh

Thanks for the feedback! We are currently investigating and will update you shortly.

This document talks about the Marketplace images and thus the commands.
We will leave the doc as is for now. However the solution provided by you would stay with this document for others to reference.
We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Native review for notnew/access

https://github.com/notnew/access
Library to reduce boilerplate for record setters. Has functions like setter
setX value record = { record | x <- value }
setter .x == setX
setter .x 42 { x=0, y=10 } == { x=42, y=10 }

The native code exports a single javascript function makeRecordSetter that builds setters when passed builtin elm "dot accessors" like .x or .field.  It sets the field using Elm.Native.Utils.replace (the same function the compiler uses when it generates code for functions like setX above) so this should be pure.
It does ugly things to pull the name out of the dot accessor function (cast function to String and pull out name with regex). This will crash at runtime if passed an arbitrary function (but will print a message explaining what happened).  But by taking a dot accessor function, the compiler can infer the correct type of the setter function. And if types are annotated the a lot of bad functions will be caught at compile time.
Besides reducing boilerplate, this library lets people explore some of the proposals for alternatives to the current way of updating records simply by installing a library instead of needing to install an alternative compiler.

This is a cool trick. The code is pretty clever, but unfortunately it's probably a bit too clever.
There are two main issues I see here:

The library is not type safe. setter accepts any getter function, and if passed the wrong kind, it will crash at runtime. unsafeSetter is worse, as you can tell from the name.
The library uses a regular expression to determine which property the getting is trying to access. This means it depends on internal implementation details of Elm's code generation. A library should not depend on this.

For these reasons my recommendation is to not allow native for this library.
Please agree or disagree: @evancz @vilterp @rtfeldman @JoeyEremondi

Agree with @laszlopandy. This should not be accepted.


Needle does not redraw

When the gauge has a value that is outside of the lower and upper limit the needle is removed from the DOM. When the gauge is updated with a value that is within the lower and upper limit via ngOnChanges the needle is not redrawn.

Closing - Realized our local copy is out of date. Sorry!


(BUG) [RN] The center area of the photocamera button is not clickable

Precondition:
The "My profile " page is opened (the page where the user can edit his avatar)
Steps to reproduce:

Click the photo camera button at the center
Pay attention to the lack of response from the app
Click the photo camera button closer to the edge
Pay attention to the opened window for uploading

Actual result: The center area of the photocamera button is not clickable
Expected result: The whole photo camera button should be clickable
Video: https://www.screencast.com/t/NNJSuOk0T8

Checked on  native 1.3.1-1
LG V30+ // Android 8.0 // Google Chrome 86.0.4240.75
iPhone 8 //13.3.1

@mauriguz I've re-checked and for desktop, the button works well but for IOS and Android work like in the description
https://www.screencast.com/t/NNJSuOk0T8

@mauriguz that's still reproduced
https://www.screencast.com/t/LfCgTk5r
Checked on native 1.3.1-1
LG V30+ // Android 8.0 // Google Chrome 86.0.4240.75
iPhone 8 //13.3.1
HUAWEI P40 Lite // 10

@mauriguz @sirpy the button is clickable and the upload window is opened after one pressing
Video: https://www.screencast.com/t/kRPU2Kz0t
Checked on native 1.3.1-1
LG V30+ // Android 8.0 // Google Chrome 86.0.4240.75
iPhone 8 //13.3.1


Cache Mechanism

Align with #33 it would be nice if the underlying caching mechanism is changeable

Caching Strategy

Caching Duration

Purge Caching


Any face is a valid face

Hi!
I've installed and experimented Howdy and it simply recognizes if it is a face.
I've set it to use CNN instead of HOG, certainty=10, but the result is always the same: if a face is presented, any face, live or in a picture, it accepts it as the correct face. Male, female, etc., doesn't mater.
What am I doing wrong? Is this the expected behavior?
Thank you!
I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable): Bundgie, Ubuntu 20.10
Linux version 5.8.0-48-generic (buildd@lgw01-amd64-052) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #54-Ubuntu SMP Fri Mar 19 14:25:20 UTC 2021
Howdy version (sudo howdy version): 2.6.1

Makes sense that certainty 10 is matching any face, 1 is the most certain and 7 the least. I'd recommend setting it to 3 or lower

Oops, sorry, got it wrong!
I though 10 was the most accurate!
Tried the default value of 2.8 and worked fine.
With 2 I only got one match in about 20 attempts.
With 1 always failed ...
CNN all the time.
Thank you!
Regards,
On 03/04/2021 19:38, boltgolt wrote:

Makes sense that certainty 10 is matching any face, 1 is the most
certain and 7 the least. I'd recommend setting it to 3 or lower
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/boltgolt/howdy/issues/527#issuecomment-812908516,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGADOY7N3X4PTBNHP53KOOLTG5OC5ANCNFSM42JIZL5A.

--
Prof. André Ventura Zúquete | DETI / IEETA, Univ. of Aveiro
e-mail: @.*** | Campus Univ. de Santiago, 3810-193 Aveiro
Phone: +351 234 370504      | Portugal
URL: http://wiki.ieeta.pt/wiki/index.php/André_Zúquete
Zoom: https://videoconf-colibri.zoom.us/my/andre.zuquete

No problem, it's a bit counter-intuitive this way but that's how the underlying library implements this value


Feature: writeOutputsToSecret within different namespace

We have a use-case where we want the Secret containing outputs available within another namespace.
As an example;
writeOutputsToSecret:
  name: helloworld-outputs
  namespace: foobar

If writeOutputsToSecret.namespace isn't set, defaults to the current terraform.Namespace value.
Happy to open a PR if you feel there is value in this feature?

Hi @adamstrawson
This feature had been brought up many times.
We follow the multi-tenancy principle of Flux, which does not violate the namespace boundary for security reasons.
There are many workarounds like using a secret sharing operator to help you achieve the same result, but sorry we don't have any plan to implement features that read / write secrets in the different ns.

Thanks for the explanation @chanwit


test(worker): AttributeDuplicateFilter

Overview
Integration test for AttributeDuplicateFilter
What I've done

Integration Test

What I haven't done

NA

How I tested

cargo test --package reearth-flow-tests --test test-main -- testcase::attribute::duplicate --nocapture

Screenshot

NA

Which point I want you to review particularly

NA

Memo

NA

@jashanbhullar
The test is failing, please correct it.
https://github.com/reearth/reearth-flow/actions/runs/8615832862/job/23612181953?pr=144#step:4:815


Add tree-based input

SPDX-builder v0.6.0 supports tree-based input with the bom-base service.
Add support for these new features.

See https://github.com/philips-software/spdx-builder/blob/develop/docs/usage_with_tree.md for details.


New Design: Back button

Was viewing a listing. Hit the back button to run into the forever running loading wheel.

What are the steps to produce this consistently?
I went to the list and hit back and it worked.
This on a phone (what phone?) or what device and browser?


HotChocolate 12 HotChocolate.Execution package doesn't match the Instrumentation documentation (classes don't exist)

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
We're trying to move from HotChocolate 10 to HotChocolate 12 and are converting the instrumentation. The official documentation on this page (https://chillicream.com/docs/hotchocolate/server/instrumentation) shows that there's now multiple types of DiagnosticEventListeners instead of a single one. The two we're interested in are the ServerDiagnosticEventListener and ExecutionDiagnosticEventListener. It seems pretty straightforward: make a class that implements those and override the methods you want. But none of the examples show what package contains the event listeners. The closest package I found based in the examples was HotChocolate.Execution.Instrumentation. However, in that package the ServerDiagnosticEventListener and ExecutionDiagnosticEventListener don't exist. The only thing that's there is an interface for the Execution EventListener (IExecutionEventListener), and because that's an interface and not a class, we'd have to implement every single method on it rather than just overriding the couple of methods we want.
Why is there this discrepancy between the documentation and the packages available? Is it an error with the documentation? Are we using the wrong package and the correct classes are defined somewhere else?
What's the proper way to set this up?
Steps to reproduce

Set up any basic query
Install the HotChocolate.Execution package
Try to add instrumentation by following the HotChocolate 12 Instrumentation documentation
The classes it says to use do not exist

Relevant log output
No response
Additional Context?
No response
Product
Hot Chocolate
Version
12.4.1 (though I checked 12.6.0 as well)

The ServerDiagnosticEventListener is part of the HotChocolate.AspNetCore package. The ExecutionDiagnosticEventListener should be available through the HotChocolate.Execution package (namespace HotChocolate.Execution.Instrumentation), which is also referenced by HotChocolate.AspNetCore.
If you have added the HotChocolate.AspNetCore package and you are on 12.6 you should be able to have access to both these classes...

Thanks for clarifying where both of the event listeners come from! I think my issue was some sort of weird internal crash in Visual Studio itself and that's why it wasn't recognizing or suggesting the correct packages for the event listeners. After a few restarts of VS and my computer, I verified that I did indeed have the HotChocolate.AspNetCore package installed with 12.6 and tried to create the event listener classes again and this time it worked with no issues


⚠ DSO-API has degraded performance

In 39ab968, DSO-API ($SITE_URL_DSOAPI) experienced degraded performance:

HTTP code: 502
Response time: 11659 ms

Resolved: DSO-API performance has improved in 98f56d4 after 9 minutes.


Fix undefined np errors

Ran into some "undefined np" errors when running your fork, so decided to fix those.

Thanks for the heads up about the problem. I chose to fix it a little differently just to reduce the size of the diff https://github.com/jonathangjertsen/Analog-Fundamental-Frequency-Measurement/commit/5eb075b310e1f343e0ab6aab55515258af83a7c3. I'll comment on my PR since it was ignored or forgotten originally.


[Question]: Why doesn't response metadata capture the information always?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I have used the basic chunking and loading the data to Postgres database with the code from the example - https://gpt-index.readthedocs.io/en/v0.8.47/examples/low_level/oss_ingestion_retrieval.html
Here is the the code
text_chunks = []
# maintain relationship with source doc index, to help inject doc metadata in (3)
doc_idxs = []
for doc_idx, doc in enumerate(documents):
    cur_text_chunks = text_splitter.split_text(doc.text)
    text_chunks.extend(cur_text_chunks)
    doc_idxs.extend([doc_idx] * len(cur_text_chunks))

text_chunks = []
# maintain relationship with source doc index, to help inject doc metadata in (3)
doc_idxs = []
for doc_idx, doc in enumerate(documents):
    cur_text_chunks = text_splitter.split_text(doc.text)
    text_chunks.extend(cur_text_chunks)
    doc_idxs.extend([doc_idx] * len(cur_text_chunks))

for node in nodes:     node_embedding = embed_model.get_text_embedding(         node.get_content(metadata_mode="all")     )     node.embedding = node_embedding vector_store.add(nodes)
Here the issue I am facing, after the retrieval of the context from the database, it is not returning the metadata or the documents name it extracted the information from
response_1.sourcenode[0].metadata =
[NodeWithScore(node=TextNode(id_='0fb55059-e6cf-403e-89f0-3a5560437afb', embedding=None, metadata={'file_name': 'covid census and mortality protocol v2.docx'},....] // has document name
response_2.sourcenode[0].metadata = [NodeWithScore(node=TextNode(id_='be4ac130-a4eb-47b6-8cac-e9c652b109ba', embedding=None, metadata={},] // no document name
both the response_1 and response_2 - contexts are chunked and stored in Postgres in with same logic
hoverever metadata is being populated for smaller datasets and it is not happening for larger datasets
is there anything I am missing?

@ram510 I am confused maybe, I don't see you setting any metadata in your nodes in the provided code samples?


Move the pipeline generation scripts outside of libc++

Related to https://reviews.llvm.org/D155078

thanks @ldionne !


[Enhancement] Document cli testing of policies with generate rule types

Description
kyverno/kyverno#3456 has been merged. It needs to be documented.
Slack discussion
No response

@shubham4443 this feature did not ship in Kyverno 1.7.0. It will have to wait until 1.8.0 at this point.


The output is of the shortest length is a question mark.

DragonDecimal.zip
I generated decimal normal number by concatenate to integers together to this effect:
dbl = operand_fractpart / std::pow(10, n); // operand_fractpart is an integer
dbl += operand_intpart; // operand_intpart is also an integer
Then passes a double to DragonDecimal.cpp as attached. I passed 10000 doubles and toStringRaw() output is also attached.
fp_by_dragonbox_decimal_raw8.txt
My code makes sure operand_fractpart is only 8 digits. However we can see -7.018380128700001E2. By right it should be -7.0183801287E2?
However if I tried to verify whether -701.83801287 is a normal number by:
double d = -701.83801287;
memset(buffer, 0x0, sizeof(buffer));
jkj::dragonbox::to_chars(d, buffer);
std::cout << buffer << std::endl;
Then it's ok. I feel a literal double may be different from a dynamic memory double?
Every my 10000 double, there are always a couple of non-shortest values.

mpf_float_50 can print my 10000 number correctly if I call its function str(12). -701.83801287 is -701.83801287.

It's still you are guessing the answer wrongly.
dbl = operand_fractpart / std::pow(10, n); // operand_fractpart is an integer

This line is probably fine. Assuming operand_fractpart = 83801287, the resulting dbl will of course not be exactly 0.083801287, but 0.83801287 is surely the shortest & correctly rounded decimal output of what's stored in dbl, assuming that the hardware and the compiler are exactly implementing IEEE-754 binary64. In fact, the exact value of dbl is supposed to be 0.83801287000000002080923877656459808349609375.
However, a rounding that you seem to be missing is happening here:
dbl += operand_intpart; // operand_intpart is also an integer

Assuming operand_intpart = 701, what do you think will happen if you add these two numbers? In order to add two floating-point numbers with different exponent, you first have to match the exponent by shifting the mantissa bits, and then add the aligned mantissa bits. In this example, the exponent for 701 is 9 (because $2^{9}=512$ is the largest power of $2$ bounded by $701$) and the exponent for dbl = 0.83801287000000002080923877656459808349609375 is -1 (because $2^{-1}=0.5$ is the largest power of $2$ bounded by dbl). Since the difference is 10, your CPU shifts dbl's mantissa bits to right by 10-bits, and then add it to the mantissa bits of 701. Now, what happens is that among these 10-bits that are thrown away, only the MSB is 1 and all other bits are zero, which means that the result of addition is off by exactly 0.5. Since the last bit of this result of addition is 1, the "round-to-nearest, tie-to-even" rule kicks in and the final answer your CPU spits out is this addition result plus 1.
Before this plus 1, the addition result evaluates to<PHONE_NUMBER>699999431773903779685497283935546875, but after it the result becomes<PHONE_NUMBER>700000568642280995845794677734375. And the shortest & correctly rounded output for this second one is<PHONE_NUMBER>700001, which coincides with what Dragonbox outputs.
As you can see here, it is quite hard to randomly generate floating-point numbers with a prescribed number of decimal digits. Your attempts are just too naive. When I was testing Dragonbox, I used Ryu to accomplish that (now it's replaced by Dragonbox since it's only used for benchmarking now, not testing). And I don't think it's very likely that there actually are much simpler no-brainer ways of doing so. Please be wary of that almost all floating-point operations involve rounding.


Default sorting

How can I set a default sorting rule for the table?

hI @mfirry , there's no way to set sorting rules currently.
But I can add this feature.. in recently :)

I've release newest version v0.8.9 for this issue. Sorry a long time to fix it. :)

You can assign options prop on <BootstrapTable> and give two properties on that object, example as follow

var options = {
  sortName: "name",  //default sort column name
  sortOrder: "desc"  //default sort order
}
<BootstrapTable data={products} options={options}>
//...


Is there an online demo?

Is there an online demo?

我已经收到你的邮件啦~,表着急,待我仔细查看

i think not

there is no demo currently

我已经收到你的邮件啦~,表着急,待我仔细查看

Apparently not, but hopefully there will be soon!

please notify me once there is! the recent progress in text to image generators is just incredible, I don't want to miss a thing!


How can I access codemirror api?

Hi!
How can i access codemirror api? I need to refresh() on my cm instance.
I tried to use it with refs like:
this.$refs.codemirror.refresh();

but its seemed not working.

I've found different solution that doesn't involve codemirror. But im still curious :D


line break

Hello everyone, please tell me how to make a line break?
toasts.add({
description: Speed: 123Mbit\n\nPing: 123<br>test\rtest,
duration: 0,
placement: 'bottom-right',
type: 'success',
// showProgress: true,
theme: 'dark',
})
not working

gg, sorry

Doesn't seem like you're using this project. Closing for now.


Updated Activity struct and added an emoji function.

I've added everything to the Activity struct that is listed here and added a function to the Message struct that gets all the emojis from the content of the message, it then returns a Slice of Emoji structs.

I'm not sure why the build failed; I tested the PR on a bot in around 50 servers getting a lot of presence updates and it seemed to not have any problems after that fix.


ISPN-6372 Remove deprecatd ReplicableCommand.get/SetParameters

https://issues.jboss.org/browse/ISPN-6372

Looks fine to me, just waiting for CI to finish.

Tests seem to be hung.  I am not sure if it is caused by this or just a test failure somewhere else.  Waiting for now.

I doubt the test failures are caused by this, just minor comments.

@wburns javadoc updated!

Pulling...

Integrated into master, thanks @pruivo !


Support Deployments node on Linux Consumption

OS: All
Func: V2.4.317
Build Version: 20190222.12
Repro Steps:

Create a new slot for one function app with Linux OS.
Expand 'Deployment' node.
Check the result.

Expect:
Succeed to expand the node.
Actual:
Display 'Error: The service is unavailable'.

More Info:
This issues does not reproduce for slots with Windows OS.

The service unavailable error is a little odd, but the platform doesn't support deployments for linux consumption yet. Changed title to reflect that

Actually closing as duplicate of https://github.com/Microsoft/vscode-azurefunctions/issues/1046


Add abitility to calculate Topological dimension for all datasets in an avtDataTree

Description
The calculation is made only for Unstructured Grids and PolyData, all others return the 'reported' dimension passed in as an argument (which has been retrieved from avtDataAttributes).
For a tree with mixed topology, will return the largest found.
Have avtSourceFromDatabase::FetchDataset call this new method.
Resolves #

Type of change

[ ] Bug fix
[ ] New feature
[ ] Documentation update
[ ] Other

How Has This Been Tested?

Checklist:

[ ] I have followed the style guidelines of this project.~~
[ ] I have performed a self-review of my own code.~~
[ ] I have commented my code where applicable.~~
[ ] I have updated the release notes.~~
[ ] I have made corresponding changes to the documentation.~~
[ ] I have added debugging support to my changes.~~
[ ] I have added tests that prove my fix is effective or that my feature works.~~
[ ] I have confirmed new and existing unit tests pass locally with my changes.~~
[ ] I have added new baselines for any new tests to the repo.~~
[ ] I have NOT made any changes to protocol or public interfaces in an RC branch.~~
[ ] I have assigned reviewers (see VisIt's PR procedures for more information).~~

Here are the significant differences in regression test results based on this change, mostly with high order elements,
also point meshes that aren't getting Normals (calculation is bypassed due to new topo dim)
databases/vtk/vtk_28 (quadratic triangles)

operators/tessellate/quadratic_quad_01

databases/nastran/nastran8_0.png

plots/subset/subset_12 (points, Normals calculation was bypassed)

blueprint also had tests that failed in similar ways.

Here are the significant differences in regression test results based on this change, mostly with high order elements,

Remind me...which is the newest result, left or right?

@markcmiller86 sorry about that, I made the images smaller without considering the text.
The original baseline is on the left, the current results with this change on the right.

I wasn't sure about placement of the calculation in the pipeline, but I thought right after we retrieved the dataset would be good.
Thoughts?

I wasn't sure about placement of the calculation in the pipeline, but I thought right after we retrieved the dataset would be good.

Well, my first thought is that too early and we might be forcing problem-sized work that the pipeline never needed to do to fully execute.
I haven't started looking at implementation but how do we handle this calculation in the context of SIL restrictions? And, are we computing a maximum topo dim or counts of mesh entities of each dimension?

are we computing a maximum topo dim or counts of mesh entities of each dimension?

maximum (I tried to comment in the code and PR description).

how do we handle this calculation in the context of SIL restrictions

Not sure, didn't test this out.  But it operates on the datatree being passed down the pipeline, so I guess I should see if the SIL restriction is being applied before or after my calculation.

how do we handle this calculation in the context of SIL restrictions?

@markcmiller86 I just checked this.  SIL restrictions and Material Selections are applied in avtGenericDatabase::GetOutput, which is called by avtSourceFromDatabase::FetchDataset, and the Topological Dim calculation comes after the call to GetOutput, so should be good on that front.

I'm a little bit concerned about the high order element test result changes. At first blush it looks like an improvement, but I would like to understand why they changed.

Hmm, yes I think we should understand why the hi-order cases render differently?
Hard to tell if we have less detail (we are losing something), or if this is better - lines of sub elements are gone for sure, but how does this impact the fields?

I'm a little bit concerned about the high order element test result changes. At first blush it looks like an improvement, but I would like to understand why they changed.

I ran the vtk-28 test with develop and with my branch adding -dump, then compared the results.
The first difference in dumped vtkdatasets comes from  the output of avtFacelistFilter.
There are the same number of cells (all triangles), but they are in a different order.
Develop also has an extra cell-data array not present with my branch: 3DCellNumbers (only created when topo dim is 3).
This causes a difference in the number of lines output from vtkLinesFromOriginalCells (used in Mesh plot's avtMeshFilter).
The polygon count is still the same, so I don't think (for Mesh plot) there will be any difference when opaque mode is on.
Will look at the tessellate operator differences next (using only Pseudocolor plot).

For me, this case operators/tessellate/quadratic_quad_01 is the interesting one because the view IMHO definitely shows something new is happening w.r.t. to order of surface interpolation. Its not solely a matter of skipping internal boundaries (created by subdivision of high order elements).

For the tessellate operator test with Pseudocolor plot (this particular test actually doesn't use the tessellate operator).
The mesh is composed of quadratic triangles.
On develop,  the mesh remains an unstructured grid until avtFacelistFilter, which extracts the 'faces' and creates poly data.
On my branch, the mesh is converted to PolyData earlier in the pipeline, during the PostExecute of avtPseudocolorFilter(via avtDataObjectToDataset::PostExecute conversion when topdim < spatial dim).
This conversion uses vtkGeometryFilter, which understands higher-order elements.
avtFacelistFilter's conversion from quadratic-triangles to triangles is obviously very different than how it is handled in vtkGeometryFilter.
IMHO the new results for this particular case look much better and are 'correct'.

Any more comments? Changes?
If not I will create the new baselines and move this out of draft.

Just to confirm, the changes for quadratic elements are for ones that do NOT involve the tessellate operator. If so, then I don't have any more comments or concerns.

Just to confirm, the changes for quadratic elements are for ones that do NOT involve the tessellate operator. If so, then I don't have any more comments or concerns.

Correct.

Sounds good!


support for ssl_verify_hostname in the configuration

ruby-kafka introduce new configuration property that solve a critical issue when connecting to Heroku with SSL: SSL verification breaks Heroku Kafka #734
Without this fix I wasn't able to connect to heroku's Kafka with racecar...

hey 👋 I'm not sure why, but those changes are not available in 0.5.0.beta2, could we bump it?


Add Ranger Solr in the tdp-lib DAG

Hello,
We found that the Solr installation, initialization and startup playbooks for Ranger have been removed (in the playbook /playbooks/meta/ranger.yml since this commit).
Is Solr installed elsewhere or has it been removed (we don't find it anywhere else) ?
Thank you for your help !
C.L.

The first to open the PR wins :)
No one is assigned so to me that means no one is on it. You can do it if you want.


Made input[type="color"] square instead of rectangular

This supersedes #20103

Looking at this again, I'm not super happy with this approach. It feels like this is reimplementing vast majority of the .form-control, but missing all it's states. Plus it doesn't work in IE (11 down), doesn't work in iOS Safari, looks like a regular textual input in desktop Safari, and looks kinda jank in FF50.
Going to pass and mark this as a future potential feature for now.


Page titles in html/head/title in anthology pages still have a "LEMDO:" prefix

I'm not actually sure how/when this prefix gets added to the pages, but it must happen for all pages in the lemdo-dev build, and we'll need to replace it with the anthology identifier during the anthology build phase.

First shot at a fix committed in rev 11048.

Working. Closing.


Add size deduction for FixedMap, FixedSet & FixedVector

Add functions make_fixed_map, make_fixed_set and make_fixed_vector to deduce the size of their container at compile time.
When it's known that a container won't need to grow at runtime, it is now possible to create the container without specifying its maximum size, and its maximum size will be deduced to be the number of items passed to the make_fixed_[map/set/vector] function.
The SIZE template parameter in these functions has been pushed down as far as possible to make it possible to change other template parameters without having to specify the size.
Before:
FixedVector<int, 3> vector{1, 2, 3};

After:
auto v = make_fixed_vector<int>({1, 2, 3});

And now even the type can be deduced:
auto v = make_fixed_vector({1, 2, 3});

Thank you!


Don't ignore if submoduleName has an extension

Fix #2

I'm sorry for being late, will merge & publish by tomorrow. Thanks!

welcome :-)

Thank you :-) When will this be published?

Oh, I've seen it's published as 1.0.5, thanks :-)


Manually set node IP in config?

Hi, Im running the webserver on a different server but still the same external IP. I have tried using get IP from bitcoind however the field just remains blank.
Like this, Also MS doesnt show. and no links to bitnode ext.

Is their a way to solve this? Thanks.

I haven't added any option to manually set a public IP address. Either of the automatic options should work for you.
Can you please post your config.php file?

Hi thanks for the reply sorry for taking a while to get back to you!
I have it up now http://www.electrumser.noip.me however as you can see its still not showing MS.
I should mention i am running it on windows (xxamp) because thats what the node runs off.
Do you know if their is a way to show the uptime in windows on the page? :) Thanks!
This is my config.php http://pastebin.com/NWpRPMgd

Unfortunately all of my nodes are running on Linux, so I don't know any way of getting the bitcoind uptime on Windows, sorry. If you find out, you're welcome to post it or (even better) submit a pull request.
Can you confirm you've pulled the latest updates from GitHub? I've recently fixed an issue getting the Bitnodes latency, so that should work with the latest code.

It seems the recent update fixed it thanks! :)
I'm going to investigate how to show the uptime, ill let you know if i figure it out :P


Question concerning directory structure

I read the specification like it says that the eln file and the content of file should have the same name

Inside a .eln file, there MUST be a folder that will contain the rest of the data. The name of the folder SHOULD be the same as the archive name. This folder at root prevents issues when opening the file as a zip file and getting archived files extracted in the current directory, possibly overwriting other files, and probably polluting the current directory. […]

<root>
  some-data.eln/
    - ro-crate-metadata.json
    - experimentA/:[…]

However, to my knowledge, that would not work as unzipping the eln file would overwrite the currently unzipped file by a directory of the same name.
The examples are hence also not confirming to my interpretation of the text, but either have a completely different name (ok, because of should and not must) or the eln/zip file contains a directory without the .eln extension in its name (collections-example.eln -> collections-example/).
I would be pleased if either a formulation could be found that cannot be interpreted like I did or if the examples provided in this git repository would show the described behaviour and a description on how to generate and extract such zip files that are named exactly as their content.

Hello,
The important part is that the zip contains a folder. We don't care about its name, it doesn't have to end in .eln either. Yes, unzipping it will overwrite a folder of the same name, but it's okay, that's unevitable afaik.
Feel free to propose a PR if you think the spec formulation can be improved upon!

We could maybe just change the formulation/example slightly to recommend using the base name of the ELN file without the extension?


feat: create modify and export a local live app inside lld

📝 Description
Create modify and export a local live app inside lld
❓ Context

JIRA or GitHub link:  https://ledgerhq.atlassian.net/jira/software/c/projects/LIVE/boards/623?selectedIssue=LIVE-11400

✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[x] npx changeset was attached.
[ ] Covered by automatic tests.
[ ] Impact of the changes:

...

🧐 Checklist for the PR Reviewers

[ ] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[ ] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[ ] There are no undocumented trade-offs, technical debt, or maintainability issues.
[ ] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[ ] Any new dependencies have been justified and documented.
[ ] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

couldn't dapp.provider be hardcoded, as only "evm" is the accepted value ?
Only displaying string as the accepted value is misleading.

Have you considered select inputs for enum values ?

And multi-select inputs for the field platform and permissions ?

As a last comment the overall code in apps/ledger-live-desktop/src/renderer/modals/CreateLocalManifest/index.tsx will be hard to maintain, simple steps to make it easier to read.

You could put some logic in separate functions to not end up with such a huge return value :

        if (key === "content")  {
          return <ContentKeyInput />
        }
        ...
        if (key === "dapp") {
          return <DappFormInput />
        })

As a last comment the overall code in apps/ledger-live-desktop/src/renderer/modals/CreateLocalManifest/index.tsx will be hard to maintain, simple steps to make it easier to read.

You could put some logic in separate functions to not end up with such a huge return value :

        if (key === "content")  {
          return <ContentKeyInput />
        }
        ...
        if (key === "dapp") {
          return <DappFormInput />
        })

I don't know if it deserves a unique component for each case since it not that long and collapse do the job


Deep_SVDD to pytorch

All Submissions Basics:

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] Have you checked all Issues to tie the PR to a specific one?

All Submissions Cores:

[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully ran tests with your changes locally?
[ ] Does your submission pass tests, including CircleCI, Travis CI, and AppVeyor?
[ ] Does your submission have appropriate code coverage? The cutoff threshold is 95% by Coversall.

New Model Submissions:

[ ] Have you created a .py in ~/pyod/models/?
[ ] Have you created a _example.py in ~/examples/?
[ ] Have you created a test_.py in ~/pyod/test/?
[ ] Have you lint your code locally prior to submission?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 132 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.3%) to 92.482%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyod/models/deep_svdd_torch.py
0
132
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-1.3%

Covered Lines:
9005

Relevant Lines:
9737

💛  - Coveralls


How to search?

I probably have close to 100k photos in my Google Photos account. I can't find a way to search through them by keyword, date, etc. Is there one? And if not, then I would really like to add this as a feature request.

The channel used to have this feature but with the move to GooglePhotos new API, they dropped support for it.  You can see details here: https://issuetracker.google.com/issues/110300471.  Still an open feature request but unable to provide today.


Map info window overview shows HTML instead of plain text

When you click on the location of a case on the map, the overview displays raw HTML as opposed to text.
A screenshot is below:

This should be plain text. The HTML is being saved from CK Editor.

Actually @trystant can you expand on how exactly you cause the text to appear?  Because according to #912, a fix for this has already been merged into master.

@trystant pinging again - can you recreate this?  Like I said, a fix for this was merged into master before.

Yup...
Go to https://ebwiki.org/cases/elijah-james-smith
Go to map of cases at bottom of article.
Click on one of the cases.
See:

@trystant to be clear, we want the HTML to be rendered properly here, right?  Like links show up properly?
Or do we want it to be just plain text, with no styling?

@trystant Pinging again

We want plain text, I believe
On Fri, May 25, 2018 at 10:48 PM Rachel Green<EMAIL_ADDRESS>wrote:

@trystant https://github.com/trystant Pinging again
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/EBWiki/EBWiki/issues/1027#issuecomment-392230428, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA0xYs9xx-_GoQdzG5gVLaus2qoCXhPks5t2MJpgaJpZM4PcgkS
.

Ok.  This is coming from the overview, correct?  Shouldn't we enforce a character limit then, as well as tell them that it will be displayed in plain text?

To provide more context - it looks like on the view, we already truncate the overview to 500 characters in the display.  I see no reason not to enforce that at the model level and require users to enter overviews that are 500 characters or less to begin with.  This will be two PRs - one that fixes the HTML, then another that adds the requirement for 500 characters.

@trystant Wait, why do we allow the overview to be nil?  If that's what pops up in the marker, then shouldn't that always have a non-nil value?

This has been addressed in #1593 and other PRs that fixed the corresponding rake task (#1627, #1629, #1623)


Wrong import in tutorials for DQN

Here: https://pytorch-lightning-bolts.readthedocs.io/en/latest/reinforce_learn.html#dqn-results
It should be:
from pl_bolts.models.rl.dqn_model import DQN
and not:
from pl_bolts.models.rl import DQN

Hey @drozzy, you can actually do it both ways. In the __init__.py, DQN is already imported like below so you can also import like from pl_bolts.models.rl import DQN instead of from pl_bolts.models.rl.dqn_model import DQN.
https://github.com/PyTorchLightning/pytorch-lightning-bolts/blob/58536c260e7877c8c75dfccfaa58acee4fdc2ae1/pl_bolts/models/rl/__init__.py#L1-L3

Oh, strange. I got import error when I did it the tutorial way.

Nevermind, it works now. Thanks!


Center aligned flow layout

Hi thanks for this amazing library! loving it so far, the only issue that i have right now is that i need a center aligned collection view layout, is there any way we could add some sort of alignment to the new IGListGridCollectionViewLayout so that we could have both left and center alignment?

@jessesquires I can take on this, if you guys approve this api.

@zhubofei Are you still interested in working on the extra alignment ability of your grid layout?

@Sherlouk Yes, I'm gonna post a PR by the end of this week 😊.

Closing since we have a new layout inbound in #450. Once that's landed we can revisit if this is still needed.


fix text_bounds, accepts null bounds ptr

According to https://github.com/memononen/nanovg/blob/master/src/nanovg.c#L2759 the bounds parameter should be nullable.
Not sure if this is the proper FFI way, but the demo's still work, so...

Seems fair, merging, thanks


Ensure JavaIndexerServer exits on a server error [phab:D408]

Created by schroederc at 2015-07-15 19:13:47:

zarko accepted this revision at 2015-07-15 19:29:48

schroederc closed via commit 42a75460099fef8366153a8a53ee04bd0eac17e6 at 2015-07-15 19:38:36


What about the sets N, Z and Q?

As there is still no support for rational/integer numbers, see no reason to add these sets

After there is support for rational/integer numbers, there is no reason not to add these sets

Periodic root sets will be added. Hence, N, Z, Q will be added as well.


Cross Thread Access

Take the following contrived example, the user opens a file and then spins up a new thread (for some reason) to perform a write on it.
FileSystem.openFile("foo.txt", Append, (file, error) -> {
	Thread.createWithEventLoop(() -> {
		final text = "lorem ipsum";
		final data = Bytes.ofString(text);

		file.write(data, 0, data.length, (_, _) -> {});
	});
});

Might seem a bit odd given that async functions are supposed to avoid dealing with thread manually, but nothing seems wrong with this, with the exception that libuv doesn't allow it.
Libuv is not a thread safe API, you can only access handles on the thread they were created on which means the above sample won't work. I think there are probably two main things we could do here.

Store the thread the asys object was created on, any calls made from different threads queue up the work to be performed on that original thread and then shuttle the callback onto the calling thread event loop with a promise function. The one edge case with this is where the original thread has exited, In this situation queuing up work on the exited thread will never be executed and you wouldn't even get an error callback (unless we did a bunch of book keeping to know which threads have exited).
The alternative is to again store the original thread but return some sort of InvalidThreadAccessException to the callback if called from a different thread. This is much easier to implement but would probably seem a bit odd to most users. This limitation is also imposed by libuv and may not be true if other implementations are not libuv based, but they would still have to implement this behaviour as it seems too big to be left as target defined.

A decision on this might also be influenced by how haxe coroutines are going to handle suspendable functions potentially changing which thread a coroutine would continue on.

Had an idea the other day which might solve several questions around threading, lifetimes, and some coroutine stuff.
I've been operating on a 1 haxe thread, 1 libuv loop principle. But what if there was a dedicated background thread which just ran the libuv loop and which all asys api calls were serialised onto. I think this approach solves several problems.
Cross thread usage. You no longer have the limitation of asys objects only being usable on the thread they were created on. Passing asys objects around threads might seem odd but given that there as been a fair bit of discussion about coroutine scheduling, it might be possible for coroutines to resume on a threadpool which means asys objects being usable across threads is important and this approach would allow that.
Resouce management. A single libuv thread owned by the runtime makes object lifetimes much easier. If close hasn't been called by the time the asys object get finalised, it's easy to schedule the close on dedicated the libuv thread. You no longer have to worry about tracking haxe threads, which objects were created on them, is that thread still alive, etc, etc.
Not tied to the thread event loop. This would also free asys from the thread event loop and would allow a much easier blocking start implementation in coroutines. Basing this off my recent coroutine experiments and assuming the coroutine asys wrappers shuttles the callbacks through the coroutine scheduler, start could create its own EventLoop and pump that between checking for results. This way its true blocking, instead of the thread event loop pumping we were thinking of before which could cause other code to be executed.
There are potentially some downsides though. This approach would probably work fine for hxcpp and hl where they have their own runtime, but if another target which doesn't really implement its own runtime and wants to use libuv for its implementation, that might make things a bit more difficult.
This single thread could become a bottle neck as work will have to be placed in some sort of thread safe collection which can be picked up by the libuv thread to process. This might not end up being a problem under normal conditions though.

This is probably more coroutine related than asys but it's a follow on from the above comment so I'm putting it here.
Played around with the global libuv loop idea and it seems to work well, converted a very small subset of my asys stuff to use it (file open, write, and close). A coroutine implementation of openFile based on my coroutine branch would look like this.
@:coroutine public static function openFile<T>(path:FilePath, flag:FileOpenFlag<T>):T {
	if (path == null) {
		throw new ArgumentException('path', 'path was null');
	}

	return Coroutine.suspend(cont -> {
		cpp.asys.File.open(
			path,
			cast flag,
			file -> cont.resume(@:privateAccess new File(file), null),
			error -> cont.resumt(null, new FsException(error, path)))
	});
}

The cpp.asys.File.open call queues up work on the libuv thread and the callbacks are also performed on that thread. The call to the continuations resume which goes through the current scheduler will move execution back onto whatever the scheduler is implemented to do, that could be an event loop, thread pool, or something else.
This makes implementing a blocking coroutine start much more fesible. previously we were thinking we'd need to pump the threads main event loop, but with this setup we wouldn't need to. We can create a new sys.thread.EventLoop, setup a scheduler to execute functions on that event loop, and then pump just that event loop. Only work from the coroutine will be executed, not anything else which happens to also use the threads event loop.
// possible `start` implementation.
final loop    = new EventLoop();
final blocker = new WaitingCompletion(loop, new EventLoopScheduler(loop));
final result  = switch myCoroutine(blocker) {
	case Suspended:
		// wait will pump the provided event loop until its `resume` is called indicating the coroutine has completed.
		blocker.wait();
	case Success(v):
		v;
	case Error(exn):
		throw exn;
}

An enhancement / slight alternative to this global loop which might help libuv integration with other targets could be to have some sort of AsysContext type which is created by the initial coroutine and stored in the context. Suspending functions can then access that context which would manage a libuv loop / do whatever target specific stuff is needed without requiring a global thread.
You would start to reintroduce some unsupported operations though, e.g. not being able to use opened files across two different coroutine start calls as they would each have a separate context and therefore libuv loop. Although this might be an acceptable limitation.
I've created a new branch in both my hxcpp fork and hxcpp_asys repo with this small global loop test.


HADOOP-17415. Use S3 content-range header to update length of an object during reads

Description of PR
As part of all the openFile work, knowing full length of an object allows for a HEAD to be skipped. But: code knowing only the splits don't know the final length of the file.
If the content-range header is used, then as soon as a single GET is initiated against an object, if the field is returned then we can update the length of the S3A stream to its real/final length

Skip file status probe on openFile. Content length will be updated on first read.
As a side effect, modification time, etag and version id also be unknown as there is no probe on openFile.
Allow content length to be negative value, it means content length is unknown.
On read file, use information from Content-Range header to update content length.
If out of range exception occurs on read, ActualObjectSize from exception details can be used to update content length.

How was this patch tested?
Tested in eu-west-1 with mvn -Dparallel-tests -DtestsThreadCount=16 clean verify (AP tests failed from previous SDK upgrade)
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   ITestS3ABucketExistence.testAccessPointProbingV2:171->expectUnknownStore:103->lambda$testAccessPointProbingV2$12:172 » IllegalArgument
[ERROR]   ITestS3ABucketExistence.testAccessPointRequired:188->expectUnknownStore:103->lambda$testAccessPointRequired$14:189 » IllegalArgument
[INFO]
[ERROR] Tests run: 1063, Failures: 0, Errors: 2, Skipped: 186
[INFO] Results:
[INFO]
[WARNING] Tests run: 108, Failures: 0, Errors: 0, Skipped: 68

For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[x] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 5 new or modified test files.

_ trunk Compile Tests _

-1 :x:
mvninstall
34m 50s
/branch-mvninstall-root.txt
root in trunk failed.

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 33s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 24s

trunk passed

+1 :green_heart:
mvnsite
0m 40s

trunk passed

+1 :green_heart:
javadoc
0m 22s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 29s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m  4s

trunk passed

+1 :green_heart:
shadedclient
23m 56s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 33s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
compile
0m 29s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 29s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 16s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 5 new + 13 unchanged - 0 fixed = 18 total (was 13)

+1 :green_heart:
mvnsite
0m 33s

the patch passed

+1 :green_heart:
javadoc
0m 15s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 23s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m  7s

the patch passed

+1 :green_heart:
shadedclient
23m  4s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 31s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

94m 51s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3939

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 3906a857b626 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 6c22ebd32920723cc0988c9e13bab2388caeef29

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/1/testReport/

Max. process+thread count
524 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 5 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m 22s

trunk passed

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 34s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 25s

trunk passed

+1 :green_heart:
mvnsite
0m 41s

trunk passed

+1 :green_heart:
javadoc
0m 23s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 29s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m  6s

trunk passed

+1 :green_heart:
shadedclient
23m 22s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 33s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
compile
0m 29s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 29s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 16s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 5 new + 13 unchanged - 0 fixed = 18 total (was 13)

+1 :green_heart:
mvnsite
0m 33s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 23s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m  5s

the patch passed

+1 :green_heart:
shadedclient
23m 14s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 22s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

93m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3939

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 46e3e51ede75 4.15.0-162-generic #170-Ubuntu SMP Mon Oct 18 11:38:05 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 638d55904e79d9b14e62c6bc8ac622cbdfac84a3

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/2/testReport/

Max. process+thread count
570 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  2s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 5 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
36m 46s

trunk passed

+1 :green_heart:
compile
1m 16s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 34s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 28s

trunk passed

+1 :green_heart:
mvnsite
0m 48s

trunk passed

+1 :green_heart:
javadoc
0m 25s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 32s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 17s

trunk passed

+1 :green_heart:
shadedclient
25m 19s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 37s

the patch passed

+1 :green_heart:
compile
0m 43s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 43s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 20s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 5 new + 13 unchanged - 0 fixed = 18 total (was 13)

+1 :green_heart:
mvnsite
0m 39s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 15s

the patch passed

+1 :green_heart:
shadedclient
24m  2s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 25s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

100m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3939

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 974a824ac13d 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 638d55904e79d9b14e62c6bc8ac622cbdfac84a3

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/3/testReport/

Max. process+thread count
571 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 5 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
37m 59s

trunk passed

+1 :green_heart:
compile
0m 49s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 40s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 30s

trunk passed

+1 :green_heart:
mvnsite
0m 48s

trunk passed

+1 :green_heart:
javadoc
0m 26s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 34s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 17s

trunk passed

+1 :green_heart:
shadedclient
25m 56s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 40s

the patch passed

+1 :green_heart:
compile
0m 40s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 40s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 20s

the patch passed

+1 :green_heart:
mvnsite
0m 40s

the patch passed

+1 :green_heart:
javadoc
0m 18s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 27s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 21s

the patch passed

+1 :green_heart:
shadedclient
23m  9s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 25s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

101m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3939

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 07cb9ea50d86 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 89778a2848732a68767a4d26caf53fee50072286

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/4/testReport/

Max. process+thread count
693 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3939/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Secured Service with JWT Auth BBE link returns 404 page

First filtered link (https://ballerina.io/learn/by-example/secured-service-with-jwt-auth.html)  for JWT documentation drives to 404 page when searching documentation and BBEs for JWT module by googling with ballerina jwt key words.
https://www.google.com/search?q=ballerina+jwt&oq=ballerina+jwt&aqs=chrome..69i57j69i60l3.4447j0j7&sourceid=chrome&ie=UTF-8

Closing since this is addressed in https://ballerina.io/learn/by-example/http-service-jwt-auth.html now.


New logging

A logging shim for Twisted and asyncio logging facilities that allows us to write single-source logging code in AutobahnPython

I'd guess this should include dealing with .message vs .args sorts of issues, similar to https://github.com/tavendo/AutobahnPython/issues/484

That would be could to factor out in txaio, yes. Log a Twisted failure with all these guards, so we don't have to add that code everywhere

Okay, so the idioms for logging and formatting IFailedFuture instances are:
class Foo(object):
    log = txaio.make_logger()

    def connect(self):
        try:
            self.log.info("Connecting")
            raise Exception("an error")
        except:
            fail = txaio.create_failure()
            self.log.error("Connection failed: {msg}", msg=txaio.failure_message(fail))
            self.log.debug("{traceback}", traceback=txaio.failure_format_traceback(fail))
            # Exception instance in fail.value

Cool! That looks good.
Ah, we could also collect hints like this in the Dev.md
Am 17.09.2015 3:28 vorm. schrieb meejah<EMAIL_ADDRESS>Okay, so the idioms for logging and formatting IFailedFuture instances are:
class Foo(object):
log = txaio.make_logger()
def connect(self):
    try:
        self.log.info("Connecting")
        raise Exception("an error")
    except:
        fail = txaio.create_failure()
        self.log.error("Connection failed: {msg}", msg=txaio.failure_message(fail))
        self.log.debug("{traceback}", traceback=txaio.failure_format_traceback(fail))
        # Exception instance in fail.value

—
Reply to this email directly or view it on GitHubhttps://github.com/tavendo/txaio/issues/8#issuecomment-140939360.

https://github.com/tavendo/AutobahnPython/pull/513

ok, this is in trunk now


Add logic to disable HBase region replication

When HBase region replication is enabled it creates a peer  region_replica_replication. Need to add logic to the code to disable this peer if region replication is disabled.
disable_peer 'region_replica_replication'

Got this error
Got this error when building a VM cluster.
Recipe: bcpc-hadoop::hbase_repl

bash[stop_repl_remove_repl_peer] action run (skipped due to only_if)

bash[disable_hbase_region_repl_peer] action run
[execute] /tmp/chef-script20171016-25575-1656kfr: line 1: hbase: command not found
================================================================================
Error executing action run on resource 'bash[disable_hbase_region_repl_peer]'
Mixlib::ShellOut::ShellCommandFailed
Expected process to exit with [0], but received '127'
---- Begin output of "bash"  "/tmp/chef-script20171016-25575-1656kfr" ----
STDOUT:
STDERR: /tmp/chef-script20171016-25575-1656kfr: line 1: hbase: command not found
---- End output of "bash"  "/tmp/chef-script20171016-25575-1656kfr" ----
Ran "bash"  "/tmp/chef-script20171016-25575-1656kfr" returned 127
Resource Declaration:
In /var/chef/cache/cookbooks/bcpc-hadoop/recipes/hbase_repl.rb
35:   bash "disable_hbase_region_repl_peer" do
36:     code <<-EOH
37:       echo "disable_peer 'region_replica_replication'"|hbase shell
38:       EOH
39:     not_if "echo list_peers|hbase shell|grep region_replica_replication|grep ENABLED"
40:     user 'hbase'
41:   end
42: end
Compiled Resource:
Declared in /var/chef/cache/cookbooks/bcpc-hadoop/recipes/hbase_repl.rb:35:in `from_file'
bash("disable_hbase_region_repl_peer") do
action [:run]
retries 0
retry_delay 2
default_guard_interpreter :default
command "disable_hbase_region_repl_peer"
backup 5
returns 0
user "hbase"
code "      echo "disable_peer 'region_replica_replication'"|hbase shell\n"
interpreter "bash"
declared_type :bash
cookbook_name "bcpc-hadoop"
recipe_name "hbase_repl"
not_if "echo list_peers|hbase shell|grep region_replica_replication|grep ENABLED"
end
Platform:
x86_64-linux

@leochen4891 , FYI. the change was tested on an existing cluster and not on a fresh cluster. Looks like this is breaking on a fresh VM cluster. Correct?

Yes, I see this breaking a build of master @bijugs

But more because bcpc-hadoop::hbase_repl is called before we install hbase in role::BCPC-Hadoop-Head-HBase?

Yes. Looks like we had a role[BCPC-Hadoop-Head] in the role file for head node and it got removed which made the repl recipe the first one. Refer this.

The original issue and some rework have been performed. I am closing this unless we see related issues crop up again.


Update short description and logo

Questions
Answers

Description?
Update short description and logo.

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes https://github.com/PrestaShop/PrestaShop/issues/15858

How to test?
Please check that short description and logo are updated. Sorry for the little confusion, the correct short description is: "Enrich your stats, add a tab showing what keywords have been searched by your visitors."

Thanks @Julievrz


Make bytes_to_send in tsi_handshaker_next const

The bytes_to_send in tsi_handshaker_next is owned by TSI handshaker, not the caller. Thus, it is better to make it const.

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Please write up a draft CL that matches this API change for internal projects that implement the tsi_handshaker_vtable!
And cc @a11r, who is handling the next import.

@ncteisen I sent a draft CL on import.
Thanks all for comments/reviews. I will submit it now.


WebView.invokeScriptAsync updates

Improve documentation for invokeScriptAsync: fix args parameter and the reference to start on MSWebViewAsyncOperation, and more specifics on functionName, and the result of the async operation.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Make Snyk SCA scan failures block builds

Trello card
This is a requirement before we can implement RFC-167, "Allow automatic patching of all dependencies".
If this change causes problems on any our repos, we could temporarily patch those repos (and those repos only) to refer to the previous version of this workflow instead of @main. For example:
jobs:
  snyk-security:
    name: SNYK security analysis
    uses: alphagov/govuk-infrastructure/.github/workflows/snyk-security.yml@533143ddd823518b97165a4a80c2995e9ffe980a
    secrets: inherit

Just fyi these checks still flake a bit. Dunno if that's gonna be a problem (happy to try it and find out — we can always revert).

Last I looked, the flakiness was within the third-party action.

Going to merge this for now, if it's flaky then it's easy enough to re-run failed jobs.
I don't know if it's possible to get GH to cache the Snyk binary without forking the snyk/actions/setup action, but I'll have a quick look and maybe write up a card for PSR to do a spike if it looks doable.


Donation widget/form improvements

What:
Add country select with country codes (2 characters country codes)
Why:
We need to make sure we make life easier for our users when filling the forms
Media:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Breaking change not detected

The v5 release had to be done manually with --major because the automatic release kept tagging it as v4.12.0.

Note: the relevant commit for this is https://github.com/relekang/python-semantic-release/commit/740f4bdb26569362acfc80f7e862fc2c750a46dd

Here is the text of commit 740f4bd:
feat(build): allow config setting for build command (#195)

* feat(build): allow config setting for build command

BREAKING CHANGE: Previously the build_commands configuration variable
set the types of bundles sent to `python setup.py`. It has been replaced
by the configuration variable `build_command` which takes the full
command e.g. `python setup.py sdist` or `poetry build`.

Closes #188

Look at this code from parse_text_block:
https://github.com/relekang/python-semantic-release/blob/3baf55bf425b340e1be12a70868526066c9708b6/semantic_release/history/parser_helpers.py#L18-L24
740f4bd has the commit message followed by 3 paragraphs of extended description. This means that the if statement on L21 evaluates to false (as 3 is not equal to 2), so the 'footer' is not considered, despite it still existing.
https://github.com/relekang/python-semantic-release/blob/3baf55bf425b340e1be12a70868526066c9708b6/semantic_release/history/parser_helpers.py#L10-L12
The above docstring is wrong, 'footer' is actually defined as the second paragraph.
Also, with squashed commits, there are often many paragraphs in the description, which means that the breaking change (or multiple breaking changes) could appear later on.
I recommend that we change the way these breaking changes are searched for so that instead we loop over all paragraphs. This could possibly be handled entirely in the commit parser itself, adding a list of breaking changes as the fifth item in the returned tuple. That would also allow for future alternative parsers to find breaking changes differently.

Is this still working?  I found a squashed merge that has a breaking change in it was not detected.  It was detected previously when it was on a separate branch.  After the squash, it failed to be detected.


two more issues

many thx for the previous reply！
two more issues：

have you tested the model on the CASIA_B dataset？  can you achieve the 90% around accuracy？

have you observed the final performance difference between  using  nn.LogSoftMax and nn.SoftMax （since you used nn.LogSoftMax here）

I have not tried, I guess you can achieve around 90%.
If you use nn.ClassNLLCriterion as loss function you need to add nn.LogSoftMax as your last layer. you can see more from  nn.ClassNLLCriterion document here., if you use nn.Softmax, I do not find suitable Criterion class as loss function, you may write the Criterion youself. Besides, combining Log and SoftMax  is for speed purpose.


Resolving #824

Updated the DevOps save step to use gitUrl when its not blank for localGitUrl as well.

@jstrachan - can you please review and merge this ?

ok to test

[merge] - thanks!


Overlay service performance data on graph

Is your feature request related to a problem? Please describe.
Current trace analytics feature does not have an option to display the performance metrics such as txn/min, avg latency etc for each component, we need to go to explicit component to triage the issue.
Describe the solution you'd like
Would like to see performance metrics for each component while analyzing the traces for services.
Describe alternatives you've considered
AWS Xray has the feature and would like to get it built on OpenSearch trace analytics as well.

on service map node: show transaction per minute - throughput per minute over selected time range


[feature request] Add 'it.concurrent' async support?

I am trying to use both concurrent and reporter methods, then it throws an exception
After some research, found out that the specStarted method executed after the async function.
so, I have to use concurrent without reporter invoked, or quit using concurrent.
Help needed, thanks
code example:
it.concurrent("create api", async () => {
    reporter.description("create api");

    reporter.startStep("check");
    expect(true).toBeTruthy();
    report.endStep();
});

    TypeError: Cannot read property 'currentTest' of undefined

      3 |
      4 | it.concurrent("create api", async () => {
    > 5 |     reporter.description("create api");
        |              ^
      6 |
      7 |     reporter.startStep("check");
      8 |     expect(true).toBeTruthy();

      at Allure.Object.<anonymous>.Allure.getCurrentTest (node_modules/allure-js-commons/index.js:25:34)
      at Allure.Object.<anonymous>.Allure.setDescription (node_modules/allure-js-commons/index.js:79:10)
      at Reporter.description (node_modules/jest-allure/dist/Reporter.js:24:21)

@ccckblaze https://www.npmjs.com/package/jest-allure-circus implemented here


YAGA (Yet Another GIFT Visualizer)

Only requires matplotlib, can open GIFT coordinates or work without them, can open CSV effects as well as PY ones, can compile PY effects into CSV. My 'gift' this year since I didn't contribute last year, expect some effects from me too later.

I needed 3 commits for one line because am on mobile, don't blame me :p

Thank you so much for this!!
While I haven't tried the other ones, your visualizer was really straightforward to set up and use.


Saturation sensor seems to send wrong data

The values send/received over the MQTT Broker for saturation are always 1. On the display itself seems to be correct.
I set the wet_point to 0.5 and the dry_point to 2.5.
In the moisture.py the values are calculated like this:
    @property
    def range(self):
        """Return the range sensor range (wet - dry points)."""
        return self._wet_point - self._dry_point

    @property
    def saturation(self):
        """Return saturation as a float from 0.0 to 1.0.
        This value is calculated using the wet and dry points.
        """
        saturation = float(self.moisture - self._dry_point) / self.range
        saturation = round(saturation, 3)
        return max(0.0, min(1.0, saturation))

That should get me for example on sensor_0:
(0.577 - 2.5) / -2 = 0.9615 -> 96.2
Here the values from the MQQT Explorer:
{
  "light": 620.5799,
  "sensor_0": {
    "moisture": 0.5770714248173359,
    "saturation": 1
  },
  "sensor_1": {
    "moisture": 0.5150805488783872,
    "saturation": 1
  },
  "sensor_2": {
    "moisture": 0.6929367700550096,
    "saturation": 1
  }
}

Used new sensors now it seems to go again.


Issue #14 🎫: Fix Excessive Involvement API Requests Triggered by -LikeButton- UI Component.

Pull Request Summary for Issue #14 Completion

Overview:

Issue #14.

Issue: 1. When the user goes to the ProjectsPage, each project is rendered with its respective LikeButton component, each of these like buttons triggers a request to the involvement API to get all the likes, i.e. 18 requests for the same likes array. That is 17 redundant network requests.
Issue: 2. When the user likes a project, this will too trigger a new request to fetch all the likes, again, a redundant network request.

Changes Made:
Added:

n/a.

Modified:

/src/services/involvementAPI/involvementAPI.ts

Removed unnecessary try-catch block in the getLikes function.
Now if the response is not ok, the function will throw an error class with the response statusText as the message.

/src/components/pages/ProjectsPage.tsx

Imported involvement from services/involvementAPI/involvementAPI.ts.

Set a new local state for the projects likes that will be fetched from the API.

Created the asynchronous function getProjectsLikes that will fetch all the projects likes, this will be done within a try-catch block, if everything goes well, the likes will be set in the local state, if not, the error will be logged and the local state will be also set but to an object with two properties, error and message. This error object will be used in the UI component LikeButton for error handling.

In addition, the new local state projectsLikes will be passed down to:

SplideCarousel => SplideCarouselSlide to finally reach the LikeButton component.

/src/components/UI/SplideCarousel.tsx

Added a new property to the SplideCarouselProps interface, projectsLikes, that will be passed down to the SplideCarouselSlide component.

/src/components/UI/SplideCarouselSlide.tsx

Added a new property to the SplideCarouselSlideProps interface, projectsLikes, that will be passed down to the LikeButton component.

/src/components/UI/LikeButton.tsx

Multiple important changes have been made here:

The Like interface will be moved outside the component and it will now take a new property, error with the type of boolean.

Update the LikeButtonProps interface to take the new projectsLikes prop that has been passed down from the ProjectsPage component through the SplideCarousel and SplideCarouselSlide UI components.

Renamed the old setLoadingToFalse function for a more descriptive name, setLoadingFalseAfterTimeout and all the references to it.

Removed the projects likes fetching logic from the updateLikeCount function since this is now done in the ProjectsPage component.

In this updateLikeCount function, there are new conditions to handle certain scenarios:

Now we will check for the projectsLikes prop at index 0 to have the error property set to true, if so, we will set the Error local state to true and invoke setLoadingFalseAfterTimeout.
The condition to check for the length of the projectsLikes array to be 1 is still in used, because if a new involvement App API Id is set, the response will be an array with a single object. If that happens then we will just invoke setLoadingFalseAfterTimeout to show the loading spinner and finally the lke button with no likes.
Now when we filter the projectsLikes array to find the project likes by the itemId passed down as a prop, we will cast this as a Like array or undefined if none is found.
If the likedProject is not undefined, the block is the same as before, but now it it is undefined, the only thing we will do is to invoke setLoadingFalseAfterTimeout to show the loading spinner and finally the lke button with no likes.

In the handleLikeSubmit function, there were also a few changes:

Renamed the wasLiked argument state name at the setState function.
Now the conditional for the error state will also include the check for the projectsLikes prop at index 0 to have the error property set to true, if so, we will set the loading local state to true, invoke setLoadingFalseAfterTimeout and finally set the Error local state to true to show the user the error button instead of the like button. All these checks are done to prevent the user to POST a new like if the API is not working properly.
And finally, the invocation of the old async function updateLikeCount has been removed, since this is not longer needed.

At line 162: Invert the conditional statement to prioritize displaying an error message when an error is present, otherwise display the like count. This change is also to always check for truthy values.

Deleted:

n/a.

Impact:

The impact of this changes is that now the ProjectsPage component will fetch all the projects likes at once, and then pass down this data to the LikeButton component through SplideCarousel and SplideCarouselSlide, this will prevent the project to make redundant network requests and also will prevent the user to make a new request when the user likes a project.

Testing:

n/a.

Related Issues:

Closes #14.

Dependencies:

n/a.

Additional Notes:

n/a.

✅ Good for merge.
Note:

The changes made in this branch have just been deployed, check the new SemVer Deploy to gh-pages - v2.1.0 - Address redundant Project Likes network requests.


[HELP] K3d assumes runtime path in the wrong place

What did you do?
I'm trying to implement a cobra command for uploading a Docker image to a node in a single-node k8s cluster, using the LoadImagesIntoCluster function from here: https://github.com/rancher/k3d/blob/master-v3/pkg/tools/tools.go
However, GetRuntimePath for containerd runtime assumes the containerd.sock is under the path /var/run/containerd/ when in the created cluster it's under /var/run/docker/containerd/, causing the function to fail with:
  Logs from failed access process:
ctr: failed to dial "/run/containerd/containerd.sock": context deadline exceeded

How was the cluster created?

via the k3d pkg create cluster function (from master-v3 branch)

What did you do afterwards?

tested this with the latest k3d CLI and it worked fine there

What did you expect to happen?

would expect the runtime path to be correct

Which OS & Architecture?

MacOS

Which version of k3d?

k3d version from master-v3 branch (dev)

Which version of docker?

19.03.8

Hi @helgifeiti , thanks for testing this stuff :+1:
Actually, the containerd runtime support is super experimental and I just put it there for testing some interfaces.


firefox: fix crash, enable debug symbols and clean up

Motivation for this change

Fix #146382 by disabling jemalloc by default.
It's caused by jemalloc violates clang's alignment assumption of malloc from LLVM 13. Check details in https://bugzilla.mozilla.org/show_bug.cgi?id=1741454
Try this POC to confirm it's actually fixed by this PR.

Enable separated debug symbols by default for easy debugging.

Clean up unnecessary makeFlags and NIX_LDFLAGS since we're now using LLVM stdenv.

Use --enable-lto=cross. I add this to make our configure flags closer to Arch's, and potentially make it more optimized.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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/)
21.11 Release Notes (or backporting 21.05 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.

lets set , crashreporterSupport ? false to , crashreporterSupport ? !privacySupport

lets set , crashreporterSupport ? false to , crashreporterSupport ? !privacySupport

I'd think it's not useful currently. Since generated crash report still doesn't have symbols even after this PR. They require building a custom symbol pack with a custom tool dump_syms and uploading it to mozilla symbol server with an account. See Mozilla docs. This process is usually done by distribution, like uploading in Arch's PKGBUILD. But of course Hydra cannot and should not do this.
If you want to package dump_syms and the symbol package, or have better approach, please create a separated issue or PR.

One can test firefox-wayland like this:
nix-store -r /nix/store/xvsiw2v6nwahqwzs767xl0dj66xkifzv-firefox-94.0.1/ --option binary-caches 'https://cache.nixos.org/ https://mic92.cachix.org/' --option trusted-public-keys 'mic92.cachix.org-1:gi8IhgiT3CYZnJsaW7fxznzTkMUOn1RY4GmXdT/nXYQ='

I'm afraid this PR broke nixosTests.firefox, blocking the nixos-unstable channel.  So far I only blindly tried it on the commits directly before and after merging.

I'm afraid this PR broke nixosTests.firefox, blocking the nixos-unstable channel. So far I only blindly tried it on the commits directly before and after merging.

this didn't break it
Kernel panic - not syncing: Out of memory: compulsory panic_on_oom is enabled its running out of ram and it was fixed in https://github.com/NixOS/nixpkgs/pull/146804

The latest channel update for nixos-unstable as of a few hours ago https://github.com/NixOS/nixpkgs/commit/263ef4cc4146c9fab808085487438c625d4426a9 has a fixed version of firefox (just verified myself) for anyone who was running into this issue. Thanks to the folks who worked on this.


[MB-13856] New columns for PPM closeout tab in Services Counselor queue

Jira ticket for this change
Summary
The PPM closeout tab has the following new columns:

Closeout initiated

The latest time that any of the PPM shipments associated with a move was submitted.

Full or partial PPM

This comes from the ppm_status field on moves

Destination duty location
PPM closeout location

For Army/Air Force moves, this will show the closeout location chosen by the customer (however, customers cannot set this field yet, so it will mostly be blank, that work will be done in MB-11915)
For Navy, Coast Guard, and Marines moves, this will show the "closeout GBLOC" associated with their service: NAVY for Navy, USCG for Coast Guard, and TVCB for Marines.

Both sorting and filtering on this column have no effect for NAVY/USCG/TVCB office users because every move they see will have exactly the same value in here.

The filters on PPM closeout location and Destination duty location work the same as the existing filter on Origin duty location: they do a case insensitive search, matching from the beginning of the word.
So a search for "fort bra" will match "Fort Bragg"
But a search for "bragg" will not.
We may change the way the closeout location filter works in the future: MB-14594
Is there anything you would like reviewers to give additional scrutiny?
Passing the closeout gblocs through to the closeout location was kind of awkward. I decided just send back kind of a fake transportation office with the GBLOC set as the name. If there's a classier way to do this I'd love to hear about it.
An alternative approach would have been to look up the transportation offices used by the office users in the those GBLOCs. We would still have to go through those somewhere (probably model to payload?) to use the GBLOC instead of the transportation office name though.
Also I used a bit of a hack to fix the issue with filters persisting when you switch tabs: I just wrapped one of the TableQueues in a div. As far as I can tell, this hasn't broken the styling and seems to work fine.
The complexity in order_fetcher.go is getting out of hand. I think we should split Services Counselor and TOO queues up. I think at this point the logic is getting hard enough to follow that it's worth duplicating some code. This code originally started as a pretty generic thing that fetched orders, but it's exclusively used for queues and the business logic for the queues has gotten way more complicated than it used to be, so i think it's worth coming up with more specific solutions.
Setup to Run Your Code
make db_dev_e2e_populate
make server_run

make client_run

Additional steps

Log in as a Services Counselor user
Try sorting and filtering the new columns and make sure the results make sense
Verify that switching between the Counseling and PPM Closeout tabs resets any filters or sorts that were applied
Verify that values in the new columns match the designs
For at least one of the closeout GBOCs (TVCB, NAVY, USCG):

Login as a services counselor in that gbloc
On the PPM Closeout tab, make sure that the new filters and sorts work
Note that filtering by the "Closeout location" column will do nothing if you are in a closeout GBLOC

https://user-images.githubusercontent.com/2627844/205415280-8f090b82-d63d-4989-be55-0e5c56ef9e96.mov
In this screen recording, it's a bit hard to test some of the columns because the test data I was using didn't have any moves with the Full ppm type, so everything is Partial. And the destination duty location for every move was Fort Gordon.
Verification Steps for Author

[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-13856

  Generated by :no_entry_sign: dangerJS against 3c147c050ff5fe5618efb1c1f26f20b8047e84a9

It returns full results no matter what the search is for (instead of just matching results)

This is intentional for office users in closeout GBLOCs, but I meant to do a little more here to make it less confusing and forgot in the weekend shuffle.
It was going to be both hard and sort of pointless to implement the closeout location search for office users in closeout GBOCs because every single move that is visible to them has exactly the same closeout location (which is the same as the office user's GBLOC).
So I just ignored that filter for office users in closeout GBLOCs. I think it would probably make sense to disable it on the frontend as well, to prevent confusion, but I should ask design about that.


Addon presents/blueprints

The addon list is based on a rough selection I did. Though I expect this high subject of change. Open an issue to discuss how this can be populated in a nice way.

Some of my ideas with this: Support presets and blueprints.

This would be great for small teams. I'm not sure what this would look like, though. A few possibilities:

ember-cli-create could look at an environment variable when it installs. This could be a comma-separated list of addon names.
Installing ember-cli-create could allow one to point to a person/team's Github fork of ember-cli-create which prefers that fork's own list of addons to include.

The idea is very similar to what vue does: ember-cli-create --preset gossi/my-preset or ember-cli-create --preset gitlab:gossi/my-private-preset. So companies can host their own presets and are good to go. Gists can also be supported.
The hard part would be to set the schema for the preset file. Also vue does a very good job here, which can be taken as inspiration/base work.
PS. I hate environment variables, that's why I create this project :p

It also requires a deeper look at blueprints, as they might be extendable. It's more of a research project towards a preset schema.


AVRO-2318: Add a new hadoop3 profile and include it in test execution

As explained in #448 Avro's hadoop dependencies are provided/runtime so we can ensure our compatibility just by running tests against Hadoop 3 to ensure no change breaks compatibility with both versions, given that tests pass fully we may not need to release extra artifacts.
Notice that hadoop 3 uses a version of jetty that does not depend on jetty-util so we need to explictly add it to ipc-jetty to avoid runtime issues (ClassNotFoundException) in Avro's tools when using Hadoop 3.
R: @Fokko @dkulp
CC: @scottcarey

Simple enough.. LGTM


Pyright and Jedi language server don't provide InlayHint support.

Just checked with python and both the language servers don't provide the InlayHints.

See #33. Out of scope for this project.


pmxbot generous (!!) with karma when linking two already-linked nicks

(15:18:41) whit537: !k jaraco == jara
(15:18:48) pmxbot: jaraco  and  jara are now linked and have a score of 4650
(15:19:46) jaraco: oh, man.
(15:19:50) jaraco: That's an awesome bug.
(15:20:01) jaraco: !k jaraco == jaraco
(15:20:03) pmxbot: jaraco  and  jaraco are now linked and have a score of 9300
(15:20:38) ***jaraco makes a note to divide his karma by 4

Bitbucket: https://bitbucket.org/yougov/pmxbot/issue/17
Originally reported by: Jason R. Coombs
Originally created at: 2012-04-17T21:25:46.674

(Reply via chri...@gmail.com):
Best. Bug. Ever.

Original comment by: Chris Mulligan

Added test to capture issue #17
→ <<cset 346defe5c172>>

Original comment by: Jason R. Coombs


Calypso - write secrets

@jbsv Sorry, I had most things in place and forgot to add tests for LIST_SECRETS. 🤦
Thank you for pointing that issue out.

Closing this PR as the logic was moved to the HBT repository.
https://github.com/dedis/hbt/pull/53


Information of the datasets

Hello,
Thanks for sharing these datasets !
I just try to find some more specific information on it ; for instance, how many tweets/comments/news are on the WNUT17 and on the CONLL 2003 ?
Thanks,
Cheers,
Camille

Hi Camille,
It's probably best to find these statistics in either the associated papers or by looking at the datasets. However, I do have some statistics (number of tokens, sentences, and annotated entities by entity type) for these two:
https://github.com/juand-r/entity-recognition-datasets/blob/master/data/WNUT17/CONLL-format/docs/entity-list.txt
https://github.com/juand-r/entity-recognition-datasets/blob/master/data/conll2003/CONLL-format/docs/entity-list.txt