User configurable baud rates

Type: Feature Request
The hardcoded list of baud rates is a good start, but I've already found a number of projects that utilize higher baud rates than the list supports currently (ex 921600 or even 3MBaud). Rather than try to account for every possible baud rate in the hardcoded list, could a user supply a custom baud rate either directly or via a user setting to provide a custom list?
For example:
"serial-monitor.baudRates": [         115200,         921600,         3000000     ],

Great suggestion! I'm marking this as a feature request, and I expect we'll be able to add this functionality in the next release.
Out of curiosity, what devices or projects are you working with that use these high baud rates? If we can reproduce your setup, we'll be better able to test the functionality before release.

They're embedded devices (Cortex-M4/M33) that utilize an FTDI chip to translate from UART to a virtual COM port over USB. Our main use case is debug printf's on pre-production hardware, although if you give a developer a tool it's ripe for abuse. 😁

Hi, @BoomBoxHPB! I wanted to let you know that we now have support for setting additional settings like Data bits, stop bits, and parity, as well as logging to a file, available in the pre-release channel. We haven't gotten around to custom baud rates (the feature you requested), but I wanted to give an update about our other features and let you know that it is in the backlog!

Works

@gcampbell-msft  The serial ports of my "rock pi s" and "firefly rk3399" development boards are both 1.5Mbps, I really need this function. It would be better if it could replace "putty", "mobaxterm", "xshell"...

Please check out the new release!


Invalid IAM Instance Profile name

When creating ocp the 2.0.0 and master release both abort and end with the following error in the *-create-cluster.log
level=debug msg=aws_instance.bootstrap: Still creating... [2m30s elapsed]
level=debug
level=debug msg=Warning: Value for undeclared variable
level=debug
level=debug msg=The root module does not declare a variable named "control_plane_ips" but a
level=debug msg=value was found in file
level=debug msg="/tmp/openshift-install-bootstrap-1444555998/cluster.tfvars.json". If you
level=debug msg=meant to use this value, add a "variable" block to the configuration.
level=debug
level=debug msg=To silence these warnings, use TF_VAR_... environment variables to provide
level=debug msg=certain "global" settings to all configurations in your organization. To
level=debug msg=reduce the verbosity of these warnings, use the -compact-warnings option.
level=error
level=error msg=Error: creating EC2 Instance: InvalidParameterValue: Value (sales-ocp-04-tzpxw-bootstrap-profile) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
level=error msg=        status code: 400, request id: f0ea9e29-77fc-4510-a30d-a32cdf5a648b
level=error
level=error msg=  with aws_instance.bootstrap,
level=error msg=  on main.tf line 146, in resource "aws_instance" "bootstrap":
level=error msg= 146: resource "aws_instance" "bootstrap" {
level=error
level=error msg=failed to fetch Cluster: failed to generate asset "Cluster": failure applying terraform for "bootstrap" stage: failed to create cluster: failed to apply Terraform: exit status 1
level=error
level=error msg=Error: creating EC2 Instance: InvalidParameterValue: Value (sales-ocp-04-tzpxw-bootstrap-profile) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
level=error msg=        status code: 400, request id: f0ea9e29-77fc-4510-a30d-a32cdf5a648b
level=error
level=error msg=  with aws_instance.bootstrap,
level=error msg=  on main.tf line 146, in resource "aws_instance" "bootstrap":
level=error msg= 146: resource "aws_instance" "bootstrap" {
level=error
level=error

Sample ocp self managed sno .yml
---
global_config:
  environment_name: dev
  cloud_platform: aws
  aws_region: us-west-2
  env_id: sales-ocp-03
  confirm_destroy: False

nfs_server:
- name: "{{ env_id }}-elastic"
  infrastructure:
    aws_region: "{{ aws_region }}"

openshift:
- name: "{{ env_id }}"
  ocp_version: 4.12.3
  domain_name: replacewithyour.cloud
  control_plane_flavour: m7i.24xlarge
  control_plane_nodes: 1
  compute_flavour: m7i.24xlarge
  compute_nodes: 0
  infrastructure:
    type: self-managed
    aws_region: "{{ aws_region }}"
    multi_zone: False
  openshift_storage:
  - storage_name: "{{ env_id }}-elastic"
    storage_type: aws-elastic

This is due to a limitation of single-node OpenShift. Cannot solve in the deployer.


Conflicting App Config in Documentation

Told here to modify mbed_app.json
Told to compile with configs/mesh_6lowpan.json. mesh_6lowpan.json not mentioned or explained previously.
Also told to modify mbed_app.json when choose radio-type - https://github.com/ARMmbed/mbed-os-example-mesh-minimal#changing-the-radio-driver-optional.

ARM Internal Ref: ONME-3330

I agree with @sarahmarshy , these are confusing steps.
We shouldn't be asking the user to edit json files.
@SeppoTakalo can we remove instructions to edit json file and also delete the mbed_app.json in the root directory? This remove conflicting messages.

Fixed in #162


Errors from EPUB validator 3.0 (Metadata)

Mimetype, Meta-inf should be the first in the archive.

[x] Move contents files to a folder (oebps)
[x] rootfile Full-path to the folder

Delete not frequently used dublin core in metadata,
i.e. dc:contributor, dc:coverage, dc:relation, dc:source, dc:subject.

cover image

[ ] metadata : meta name="coverimage_id" content="cover-image" /
[ ] manifest : add properties="cover-image" to cover image

dcterms: modified ss.sssZ -> ssZ

TOC.xhtml should not be declared as scripted

Add TTF manifest:
 <item href="fonts/Noto-Light-Subset.ttf" id="fonts-Noto-Light-Subset-ttf" media-type="application/x-font-ttf"/>
 <item href="fonts/Noto-Normal-Subset.ttf" id="fonts-Noto-Normal-Subset-ttf" media-type="application/x-font-ttf"/>
 <item href="fonts/Noto-Bold-Subset.ttf" id="fonts-Noto-Bold-Subset-ttf" media-type="application/x-font-ttf"/>
 <item href="fonts/Noto-ExtraLight-Subset.ttf" id="fonts-Noto-ExtraLight-Subset-ttf" media-type="application/x-font-ttf"/>
 <item href="fonts/Noto-Heavy-Subset.ttf" id="fonts-Noto-Heavy-Subset-ttf" media-type="application/x-font-ttf"/>
 <item href="fonts/Noto-Regular-Subset.ttf" id="fonts-Noto-Regular-Subset-ttf" media-type="application/x-font-ttf"/>
 <item href="fonts/Noto-Medium-Subset.ttf" id="fonts-Noto-Medium-Subset-ttf" media-type="application/x-font-ttf"/>

NTS: how to fix "mimetype entry missing or not the first in archive": http://www.mobileread.com/forums/showthread.php?t=58913

Jush fix #14 at 8aa18de.
It passed the EPUB-Checker, would you please check it again?
https://github.com/ChineseCubes/react-odp/blob/structure-1/two-tigers.epub

EPUB Validator find no error but there's no cover image.
Actually we can ignore:

[ ] metadata : meta name="coverimage_id" content="cover-image" /

But have to add "properties="cover-image" to assign cover picture, And cover usually the first page of the slide? or will we upload separately?

[ ] manifest : add properties="cover-image" to cover image

If the cover image can have any ratio, I can use the image from page1.

Sure, just do it.
WANDERER Bobby Tung
Sent from my iPhone.

caasi Huang<EMAIL_ADDRESS>©ó 2015¦~2¤ë12¤é ¤W¤È12:49 ¼g¹D¡G
If the cover image can have any ratio, I can use the image from page1.
¡X
Reply to this email directly or view it on GitHub.


⚠ Bofrost.fr has degraded performance

In b126fab, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 2035 ms

Resolved: Bofrost.fr performance has improved in 6a72c70 after 13 minutes.


Clean up/expand/clarify Watch expressions docs

Request type

[x] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[X ] Correction or update

Details

This description is vague and will be corrected. I was going to use this article as a source for a dev tool tip, but @chrisdavidmills noticed that it doesn't behave as described, namely not indicating when the expression value changes. He suggested that the article needs cleanup.

Page in question: https://wiki.developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Set_Watch_Expressions
Val is right — when you set an expression (such as watching the value of a variable, or testing whether it is higher than a certain value), it seems to set ot the correct value initially, but then doesn't update as the variable value changes in the environment.
We miust be missing something here, but it'd be good to expand the page with some more information and steps to get it to work, and use cases.

@chrisdavidmills I used some very simple test code: testwatch.zip. Dumped both files into any folder, load HTML, set  breakpoint in example.js in myFunction1() then pressed the button1. This should allow you to then trace through the code watching test iterate.
My observation is that watch expressions are fragile, particularly if side effects are used (watch expressions that modify values in the code itself). For example, the screenshot shows second last value of 7 irrespective of what you do (refresh or step) and the first two values of text are mismatched/can't both be true.

Generally however it seems to work OK as long as you don't have a side effect.
Observations:

You can specify a variable you like to watch. If it is in scope it will be displayed with a value (otherwise undefined). If it is an object you can expand it.
You can add a watch on a variable or expression and it is evaluated immediately, but other (old) watches are not re-evaluated until you trigger a new evaluation by debugging or hitting the refresh icon.
You can add a watch like fred=1+3, but you can't add var fred = 1+3. I suspect it looks for a real var in this case, and it is undefined.
Side effects are possible - so text=text+1 will change the variable in code. If you hit refresh the variable will update the stored value even if you don't iterate through the code. The watch is evaluated in order, so if you change the value of the variable in a later watch, the earlier values are not updated in the watch window.

I have updated. It is certainly a lot better IMO but would appreciate feedback, as this is a feature I rarely use.

@hamishwillee LGTM; I've done a bit of cleanup on the page, and I think this is ready to close now.

Thanks. FWIW, the fact that you are expected to add boilerplate text to notes, tips etc (e.g. Important:) drives me crazy. Could so easily be done automatically.

Yup ;-)


tests: fix failpoint cases

Signed-off-by: qupeng<EMAIL_ADDRESS>What have you changed?
Make fail point cases comilable again.
What is the type of the changes?
Engineering.
How is the PR tested?
Integration test
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No.
Does this PR affect tidb-ansible?
No.
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Any examples? (optional)

@MyonKeminta please help me to re-enable gc worker tests, thanks!

/run-all-tests

/merge

/run-all-tests

/run-all-tests


fix: accessibility compatibility button & checkbox

Summary
Type

Feature
Refactor

Summarise concisely:
What is expected?
In order to continue accessibility compatibility, we should re-check Button and Checkbox to make them accessible.
I've run a11y tests on those components and error went out of it, then solve them.
To test run pnpm test:a11y
Relevant logs and/or screenshots

@Lawndlwd please change your commit and PR title by using test: instead of fix:


OwnedUnorderedConnectionPool fixes

While it's perfectly valid for a stream_id to be the same as another stream_id, it is very unlikely that a client will be sending multiple messages with the same stream_id asynchronously. If they are, it would indicate that they don't care about the order that the messages are coming back in. What's more likely is that they will only reuse a stream_id if sending messages synchronously so we wouldn't have any messages with the same stream_id waiting for responses in Shotover at the same time.
More info on the use of stream_id in the Cassandra protocol is here.
The current implementation of OwnedUnorderedConnectionPool will lose messages if they have the same stream_id so I have switched over to using a multi-map. If the same stream_id is used, the order doesn't matter, we just need to make sure we don't lose any messages.
TODO:

https://github.com/havarnov/multimap/pull/33 wait for this to be upstreamed. This PR is pointing at my personal fork for the moment.

I think we can ignore the bench noise as the changes don't touch the regressed tests.

I think MultiMap is problematic as it effectively leaks memory as empty entries are never cleaned up.
In general im struggling to review this because I do not understand unordered_cluster_connection_pool.rs
Im kind of hoping we can clear out a bunch of this complexity once we understand what its actually doing.

I'm not impressed by the existing implementation of OwnedUnorderedConnectionPool.

Its not generic and is instead designed around cassandra. - relies on cassandra's stream id field.
While it generates a bunch of connections its pool functionality is poor and only one of these connections is ever actually used.
it doesnt seem unordered to me?

Can we throw it away and instead have CassandraSinkSingle do the following:

create a single connection to the cassandra server
send every message at once
wait till we receive every reply and then return the replies.

In the future we can reimplement connection pooling for cassandra sinks, but we can ensure it is properly tested and code reviewed.

I think that's the best way forward, I'll close this PR and open a new one for removing the connection pool.

Unfortuantly when you call the method call_next_transform on a wrapper in a transform, we need to guarentee (well... try really really hard) that we return the response associated with that request. Which is why we do all this stuff with maps and why I suggested that @conorbros should look at multi-maps and cassandra stream_ids to solve this challenge.
As @rukai rightfully points out in https://github.com/shotover/shotover-proxy/issues/459, it is valid for the stream id to always be the same value. However this would usually be in the case of a synchronous client (one request, one response only ever on the wire). With this in mind, we would expect that even by reusing a stream id, we would only have to deal with one set of request/responses in flight.
This doesn't take into account the fact a client could misbehave and this is where the choice to use the multi-map came in.
If a cassandra client sends multiple requests with the same stream_id it is perfectly valid from a protocol perspective despite the fact it is somewhat of a "yolo" and now you don't know what response is for what request. This approach also breaks our ability to meet the call_next_transform guarenetee, with a multi-map approach we can at least guarentee we don't loose the message.
Re-reading through the code, some of the weirdness can certainly go away.

The needless clone is due to the fact that ResponseDetails wants a copy of the originating request! Which now that I look at it, is very silly. Transform authors, if they need the original request while doing stuff with the response, can simply clone it themselves before calling call_next_transform.
Connection pooling on a per host basis (e.g. multiple upstream tcp sessions to a single host, from a single shotover tcp incoming session), largely doesn't make sense on a broader model of shotover. We should just maintain 1 connection per upstream host per shotover tcp session by default. If the client wants to drive more connections, they should open more connections through shotover. Stuff like this exists in the codebase for redis, but it's probably worth removing as it never improved performance and could also break assumptions about pipelined request ordering.

However some of the weirdess around unordered message processing, but still being able to match requests and responses for sensible clients via stream_id to provide ordering / consistency for transform authors still very much needs to happen.

Can we throw it away and instead have CassandraSinkSingle do the following:

if a connection doesnt exist, create a single connection to the cassandra server
send every message at once
wait till we receive every reply and then return the replies

We can do this approach, however there are some changes / conditions we would need to do, to support it:

Ensure the order of the ChainResponse messages matches the received order which we read the requesets off the wire, this would need to be done via stream_id.
Change the cassandra codec to support reading multiple frames off the network buffer in one go (the same way that redis does)

Thanks for your work @conorbros, though the points raised by @rukai and some further reflection of the whole way we do cassandra stuff means this as a whole needs a rework. So my apologies for the narrow guidance I provided earlier!

Change the cassandra codec to support reading multiple frames off the network buffer in one go (the same way that redis does)

Its possible tokio-util might do this internally for us already.
Will need to investigate how tokio-util implements this before we commit one way or the other.

Moving forward, my plan is to:

simplify OwnedUnorderedConnectionPool to just be a single CassandraConnection. Keep most of the code that matches up responses using the stream_id.
Make CassandraSinkSingle have one of CassandraConnection similar to the way that RedisSinkSingle does.
Investigate/fix the memory leak in the MultiMap.

After that I'll investigate changing the Cassandra codec to support reading multiple frames off the network buffer in one go.

Closing in favour of #483


Dont try to recycle 0 items

Short Description: Assuming a max count of 100 of an item, picking up the 100th of that item will try to recycle 0 of that item.  Don't try to recycle 0 of an item.
Fixes:

Thanks for the PR, another on was already submit.
https://github.com/PokemonGoF/PokemonGo-Bot/pull/1101


Question about spotlightOnKeyPressAndHold

The extension is very cool! I have a technical question, though, and hope you can help! I hope to turn on the spotlight when I want rather than every time I click the mouse. I guess this function may relate to the spotlightOnKeyPressAndHold. If I am correct, do you mind providing a simple YAML demo of how to set it up? Apologize for not being very familiar with js and keycode settings. Thanks a lot!

Thanks for using the extension.
Tou can disable the activation on mouse down and setup whatever keyboard key using its code.
For example:
spotlight:
  toggleSpotlightOnMouseDown: false
  spotlightOnKeyPressAndHold: 73 # keycode for "i"


Doesn't appear to work

Chrome v90.
For some reason, on the extension list, it's greyed out.
I can click 'More actions' and Options and add the requested URL but no such luck.
Within Options, I've tried clicking Permissions and added Approve to all, just in case.
It this something to do with the fact my homepage is "managed by your administrator"? It's the reason I wanted the extension - to overwrite this.

Unfortunately, if your administrator blocks extensions then you can't install extensions to get around that in any way.

Many of my other extensions work.

Do you think they're disabling specific extensions?


Need Vertical List Layout

What feature or improvement do you think would benefit Files?
Make the List layout vertical rather than horizontal
Requirements

make a vertical list layout
or add grid layout with smallest icon in default windows explorer

Files Version
3.3.00
Windows Version
10.0.22621.1848
Comments
No response

Thanks for the feedback, Files can already go as small as Windows File Explorer using the grid view

What reason do you want a vertical list view?

Thank you for your feedback, a vertical list view isn't currently planned, but you can access a smaller grid view as shown in the screenshot @Josh65-2201 posted.

Yea I know there's grid view in files, but even the smallest icons they are bigger than windows default explorer's small grid view, as shown in the pictures following:

I'm just used to view files in the smallest grid view in a folder. This helps me to see whats in this folder clearly. But in files the grid view's icons are too big, which means i can see fewer files in a view than before. I prefer the icons with the same size as the List view, but it is horizontal. So all I need is actually a vertical view with smaller icons.

Thanks for the feedback, Files can already go as small as Windows File Explorer using the grid view
What reason do you want a vertical list view?

I'm just used to view files in the smallest grid view in a folder. This helps me to see whats in this folder clearly. But in files the grid view's icons are too big, which means i can see fewer files in a view than before. I prefer the icons with the same size as the List view, but it is horizontal. So all I need is actually a vertical view with smaller icons.

Thank you for your feedback. We're open to reconsidering this in future, and we'll keep an eye out for similar feedback to see if there is additional interest.


Modif0.2 flo and bapt

This pull-request tries to implement, for the WSDL, the last decisions of the last CARMIN meeting.
This pull-request provides:

Simplification of authentication mechanism.
Improvement of authentication mechanism.
remove autoplay boolean of "initExecution".
Rename of "initExecution" to "createExecution".

I've included these changes in another PR, so we should close this one imo.


Segmentation fault accessing attributes

Here is the script that reproduces the crash
import urllib.request

import selectolax

with urllib.request.urlopen(
    "https://rhodes-ltd-339.myshopify.com"
) as response:
    data = response.read()

html = data.decode("utf-8")
parser = selectolax.lexbor.LexborHTMLParser(html)

for elem in parser.head.iter():
    print("tag", elem.tag)
    print("attributes", elem.attributes)

print("done")

It crashes when trying to access attributes of 3rd comment

Commenting to indicate another case where the lexbor causes segmentation fault but modest works:
Causes segmentation fault:
import selectolax
parser = selectolax.lexbor.LexborHTMLParser("")
for node in parser.root.traverse():
    parent = node.parent.attributes.get("anything")

print("done")

Works as expected:
import selectolax
parser = selectolax.parser.HTMLParser("")
for node in parser.root.traverse():
    parent = node.parent.attributes.get("anything")

print("done")

Here the issue seems to be that when generating html elements the parents won't have attributes


initial benchs on Dell T30

Here is my bench results on a modest Dell T30, comparing XCP-ng 8.0 and XenServer 7.6.
In short: results are very similar.

Thanks for your input!!


[RFC] Add frozen python Lib to WASM build

Summary
In the current WASM build we can import the stdlib libraries written in Rust (time, hashlib for example) but we cannot import any python libs  (collections for example). I would suggest to freeze all the modules in the Lib/ folder to allow them to be imported in WASM.
Detailed Explanation
When building the WASM build we will add all the modules in Lib/ to the hashmap in frozen.rs.
Drawbacks, Rationale, and Alternatives

This will increase the WASM build size.

Unresolved Questions

Should we add libraries like io and os?
Should we add this as a feature flag to the regular build?

What we could also do, it extend the pythonpath with an url, and create wasm import hook. So, sys.path will contain https://demo.rustpython.github.io/stdlib, and when we import the logging module, this url is also queried. If a 404 is returned, it means not found, and import resolution continues.
How is this done in brython and skulpt?

The only problem with that is that http requests are asynchronous, so we'd have to have some way of pausing execution of a module and then coming back to it once the promise resolves.

@windelbouwman I actually thought the same could be done but as @coolreader18 says that will be a problem with the asynchronous requests.
I think that allowing people to import code in the WASM without having to deal with asynchronous requests and promises will be great. I believe we should add the stdlib as default but allowing people to freeze whatever they want into the binary would be a great feature.


Add "no value" and "unknown value" as possible values for a Wikidata statement

Is your feature request related to a problem or area of OpenRefine? Please describe.
It would be great if there could be a possibility to put "no value" or "unknown value" as a value for statements in a Wikidata scheme.
Describe the solution you'd like
When editing the Wikidata scheme for exporting values, it would be nice to have an additional command to add a "no value" or "unknown value" option, much like the Wikidata one (see image below).

Describe alternatives you've considered
none
Additional context
none

Indeed! Adding this to the todo list.
https://www.wikidata.org/wiki/Wikidata:Tools/OpenRefine/Editing/FAQ#Can_I_add_unknown_value_/_no_value_claims?

Fantastic, thanks for updating the FAQs. :)

Olivier from packed.be would also be interested in this.

@wetneb  just checking in to see if there's been any development on this or if there are any plans to implement this soon. It would actually be really valuable for custom Wikibase integrations, because apparently unknown values are not supported by wikidata integrator either, so not many options to work with that without resorting to manual editing.

We can try to attract a bit more attention to this issue, since it is not that hard.

I would like to work on this. As I am new to OpenRefine and Wikidata. I went through the following tutorial to get an idea - https://www.wikidata.org/wiki/Wikidata:Tools/OpenRefine/Editing/Tutorials/Basic_editing
I followed the above tutorial, during the edit wikibase scheme, I added an item, and a statement(see the following image) should "no value" or "unknown value" be present here?

And also it would be helpful if I can get to know how to test this? Or if there is any documentation available that can help me to test this.

Yes this is the area where we would add support for this. Here are a few ideas.
The simplest approach would be to replicate Wikibase's UI in OpenRefine (see the screenshot above). The advantage of this is that users will find it very easy to use, since they are probably already used to Wikibase's UI (and that would make it consistent with the rest of our schema editing UI, which closely mimics Wikibase's UI). But the downside is that this would not let us add any dependency on the tabular data. For instance consider the following table:

organization
director

Warner Bros.
Barry Meyer

Cycling Without Age
Lars Christiansen

Canadian Anarchist Federation

Perhaps we want to upload these relations to Wikibase and use a "no value" statement for the last row. In that case our UI needs to be a bit different from Wikibase's own UI, to let this aspect of the schema be row-dependent.
I think the simplest way to implement this would be to introduce some special keywords which could be used as cell value and evaluate to "no value" or "unknown value".
For instance the user would first modify their table to get something like this:

organization
director

Warner Bros.
Barry Meyer

Cycling Without Age
Lars Christiansen

Canadian Anarchist Federation
#WB_NO_VALUE

Then they would build a schema as usual, drag and drop the "director" column as statement value and that would generate a no value claim when the special keyword is encountered (and similarly for "unknown value"). The downside of this is that if you actually want to add "#WB_NO_VALUE" as a string-valued statement in Wikibase, you cannot do it anymore.
I'd be happy to hear more suggestions of how to proceed on this :)
To test this I think you could first write some backend unit tests. In addition it would be great to have some frontend tests as well but I think it could be a big task since we haven't started testing the Wikibase extension yet on this side.

Thanks for the ideas, Antonin. As a user, I can confirm that this solution would be quite helpful, and I don't think the downside of not being able to add "#WB_NO_VALUE" as a string-valued statement in Wikibase is a going to be a big detriment down the line.
If it's helpful, I could try testing with the Wikibases I have access to, once there is a version of the extension I can pull and test with.

@wetneb An alternative (and more complex but also more powerful and unlimited) would be introducing the Cell Variable approach that Ettore had asked for in that other issue.  Essentially Cell Flags or Stars or whatever dreamed up...instead of only have Row level Flags or Stars.  Then you could use that special signal of the Cell Flag, etc. to determine what to do regarding the statements sent to Wikibase.

I have worked on two good first issues. Now I would like to work on this issue, kindly assign it to me.

@Binita-tech : this issue is more involving. There is a proposition to make as to where you control that, either in the WD Schema or at the cell edit level.
At the WD Schema level, it doesn't give you much power, and at the cell edit level, it migth prove not so simple…
Regards, Antoine

We need this for the Wikimedia Commons integration too.
One frequently-used modeling convention on Wikimedia Commons (for creators of files imported from external websites) is the following:

Where Creator is set to 'somevalue', with qualifiers. This is used extremely frequently and will be a common use case for file uploaders.
Example file from Flickr.
I was in the process of batch adding Creator statements with similar modeling, to around 40,000 files on Wikimedia Commons that have been uploaded from iNaturalist, but am currently unable to do so.
Adding this to the 'on the radar' tasks for the Commons integration!

Terminology / naming related remark... in the UI on Wikimedia Commons the potential values are called Custom value/ Some value / No value.

@trnstlntk there is a work in progress branch over at my fork.
Technical issues aside one major question is how to make the columns with the special values droppable in the schema builder. Currently we do type checking against WB properties to allow or not allow certain columns, however, these special columns(which are just strings) should always be droppable. My local solution so far is to remove type checking all together.

Technical issues aside one major question is how to make the columns with the special values droppable in the schema builder. Currently we do type checking against WB properties to allow or not allow certain columns, however, these special columns(which are just strings) should always be droppable. My local solution so far is to remove type checking all together.

Mmmh @wetneb any opinions or ideas?

Note that if you are dealing with a column of Wikibase entities, the other cells will still be reconciled, so the column metadata will still contain a reconciliation configuration as usual. This will make it possible to drag and drop this column in the corresponding input field as usual.

Should this be how it behaves currently?

Yes, at the moment, the only sort of type checking we are doing on the columns is whether they are reconciled or not (and to the correct identifier space), for input fields which expect Wikibase entities. For all other fields, any column is accepted (since we do not have any column metadata which can give us insights about the type of values stored in them). If a column is partly reconciled, it will be usable in an input field for Wikibase entities, and all cells which are not reconciled will be ignored.

I think we might talk about different things because I do not recognize
that behavior. I'm only concerned about the UX/frontend logic for making
fields droppable(in schema-aligment.js). I currently need to comment out
the type checking part of that file to test the backend(which works as you
describe).
On Fri, Oct 7, 2022 at 8:15 PM Antonin Delpeuch @.***>
wrote:

Yes, at the moment, the only sort of type checking we are doing on the
columns is whether they are reconciled or not (and to the correct
identifier space), for input fields which expect Wikibase entities. For all
other fields, any column is accepted (since we do not have any column
metadata which can give us insights about the type of values stored in
them). If a column is partly reconciled, it will be usable in an input
field for Wikibase entities, and all cells which are not reconciled will be
ignored.
—
Reply to this email directly, view it on GitHub
https://github.com/OpenRefine/OpenRefine/issues/1713#issuecomment-1271907202,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUCQJ4RUORWX47MHHEZUPLWCBSFVANCNFSM4FQLYXBQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ok, then indeed I do not know what type checking you have in mind, it will probably be clearer once the front-end part of your changes are visible in your PR.

I was wondering if finishing this request could be in scope for the Wikimedia 2023 grant. I notice I'm hesitant to document and teach people about the partial approach using #SOMEVALUE# and #NOVALUE# in the grid because, well, it's partial ;-)

I have heard many questions about this, I have noticed that there's not much awareness of the partial solution now, and if folks know that it's possible, they can't find documentation on how to currently do some value (unknown value) / no value  statements in Wikibases.
To hopefully make this partial approach more visible and the approach discoverable, here's a demo video I just made.
https://commons.wikimedia.org/wiki/File:OpenRefine_-_somevalue_and_novalue_or_unknown_value_and_no_value.webm


JWT

It would be nice to have a zio-native JWT library. https://github.com/pauldijou/jwt-scala/tree/master/core/src/test/scala is a good example to reference.
Json integration should be supported via typeclasses, and integrations with zio-json/circe/etc published as separate packages.

The question is if the jwt handling should be added to this project or in a separate zio-jwt project, leveraging the crypto facilities of zio-crypto. I'm more in favor of the latter.

@emarx getting 404 - page not found on the mentioned link, here is the correct link


fix: upgrade to version 3.1.250

from: https://github.com/jenkins-x/jx-cli

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign abayer
You can assign the PR to them by writing /assign @abayer in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test kube

gsm
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test kube

gsm
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test gsm

vault
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test kube

gsm
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test gsm

vault
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test vault

tls
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test kube

vault
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test vault

tls
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test tls

gsm
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test kube

vault
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test vault

gsm
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test gsm

tls
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test kube

gsm
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test gsm

tls
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test tls

vault
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test gsm

tls
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test tls

vault
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test vault

kube
40d8885f549c2e6b80ea63eb5703447f2fe05ce3
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Fatal upstream request timeout

time="2020-02-13T08:57:53Z" level=error msg="[prysm] rpc error: code = Unavailable desc = UNAVAILABLE:upstream request timeout"
time="2020-02-13T08:57:53Z" level=fatal msg="[telemetry] rpc error: code = Unavailable desc = UNAVAILABLE:upstream request timeout"
Docker image was alethio/eth2stats-client@sha256:a0b388460afcaf3a336fb47ef188eede0a5b92760a72fd0b1ec3e77025055f31

hi @prestonvanloon is this persistent or just happened once?
i can't tell 100% but it might be the connection between eth2stats cli and prysm. if possible could you also update to latest? added some more detailed error messages
cheers

Updated to latest image. I'll let you know if we see more issues. Thanks!


fix(gatsby-ipfs-web-wallet): Bumping version

:tada: This PR is included in version 1.0.7 :tada:
Your semantic-release bot :package::rocket:


Allow list initialization of thread::attributes

I would like do do something like this
thread myThread(someFunc, nullptr, {4000, thread::priority::high});

Since there is only a default constructor for thread::attributes I have do do this
thread::attributes attr;
attr.th_stack_size_bytes = 4000;
attr.th_priority = thread::priority::normal;
thread myThread(someFunc, nullptr, attr);

A practical use case is having thread as member of a class with the need to initialize via the member initializer list.
This doesn't work:
class MyClass
{
public:
  MyClass() : myThread(someFunc, nullptr, {4000, thread::priority::high})
  {
  }
  ~MyClass()
  {
    // ..stop/join..
  }
private:
  thread myThread;
}

so I have to use this workaround
class MyClass
{
public:
  MyClass()
  {
    thread::attributes attr;
    attr.th_stack_size_bytes = 4000;
    attr.th_priority = thread::priority::normal;
    new (&threadStorage) thread(someFunc, nullptr, attr);
    threadPtr = (thread*) &threadStorage;
  }
  ~MyClass()
  {
    // ..stop/join..
   threadPtr->~thread();
  }
private:
  std::aligned_storage_t<sizeof(thread),alignof(thread)> threadStorage;
  thread* threadPtr;
}

Using a separate attributes structure to initialise various objects is a POSIX trick in C to avoid changing the API when adding new members to the structure, and for those using the C API probably there is not much to do.
However, in C++ life is a bit better, and we have the luxury of multiple constructors, so I think that your proposal makes sense, and not only for threads, but possibly for other objects that use attributes.
The only thing that we have to be very careful when adding the new constructors is to leave space for incremental updates, which, as far as I can tell at first sight, probably means not using defaults, but defining separate constructors with 1, 2, 3, ...
parameters.
Could you study if such a solution is realistic?

Using a separate attributes structure to initialise various objects is a POSIX trick in C to avoid changing the API when adding new members to the structure, and for those using the C API probably there is not much to do.
However, in C++ life is a bit better, and we have the luxury of multiple constructors, so I think that your proposal makes sense, and not only for threads, but possibly for other objects that use attributes.
The only thing that we have to be very careful when adding the new constructors is to leave space for incremental updates, which, as far as I can tell at first sight, probably means not using defaults, but defining separate constructors with 1, 2, 3, ...
parameters.
Could you study if such a solution is realistic?

That seems to be the most straightforward way
class attributes
{
  // allocated stack with default size and default priority or non-default priority
  // forward to second constructor
  attributes(priority_t = priority::normal);

  // allocated stack and default priority or non-default priority
  attributes(std::size_t, priority_t = priority::normal);

  // provided stack and default priority or non-default priority
  attributes(void*, std::size_t, priority_t = priority::normal);

private:
  void* th_stack_address;
  std::size_t  th_stack_size;
  priority_t th_priority;
}

Some constructors needs to be marked as explicit and/or scoped enums need to be used in order to prevent direct conversion from integer types: attributes myAttr(5);
When looking at the code I thought it might also be helpful to

separate stack properties from priority
use more descriptive types for the stack properties (std::span (C++20) or at least some pointer + length struct)

That seems to be the most straightforward way
class attributes
{
  // allocated stack with default size and default priority or non-default priority
  // forward to second constructor
  attributes(priority_t = priority::normal);

  // allocated stack and default priority or non-default priority
  attributes(std::size_t, priority_t = priority::normal);

  // provided stack and default priority or non-default priority
  attributes(void*, std::size_t, priority_t = priority::normal);

private:
  void* th_stack_address;
  std::size_t  th_stack_size;
  priority_t th_priority;
}

Some constructors needs to be marked as explicit and/or scoped enums need to be used in order to prevent direct conversion from integer types: attributes myAttr(5);
When looking at the code I thought it might also be helpful to

separate stack properties from priority
use more descriptive types for the stack properties (std::span (C++20) or at least some pointer + length struct)

I guess it might eventually work, but I'm not convinced that using defaults is a good idea.

separate stack properties from priority

What exactly do you mean by this? I have to read the C++20 specs for std::span.

I guess it might eventually work, but I'm not convinced that using defaults is a good idea.

separate stack properties from priority

What exactly do you mean by this? I have to read the C++20 specs for std::span.


Add missing space

All the other list items have a space after the linked resource

I signed it

Thanks.
/lgtm
/approve


rename getFrozenIncidenceHistory to getDistrictsFrozenIncidenceHistory

because now we have districts and states frozen-incidence history data we should rename the old getFrozenIncidenceHistory function and the associated interface.

rename getFrozenIncidenceHistory to getDistrictsFrozenIncidenceHistory
rename interface FrozenIncidenceData to DistrictsFrozenIncidenceData
remove unnecessary import

@marlon360 Are you concerned about changing the function name?


[API] Admin create new category

@KristianGombosh could we change the request to add an only category?
I will change the requirements.
I think adding subcategory will be as separate task.

@KristianGombosh could we change the request to add an only category? I will change the requirements.
I think adding a subcategory will be a separate task.

Subcategory required when we get all categories so adding category without subcategory will cause an issue for get all category request

@KristianGombosh you are correct.
Could you add an //TODO to this, and open a new issue to refactor and remove that dependency?
Because It breaks a single responsibility principle.
After you create an issue, I will merge your PR.

@KristianGombosh you are correct. Could you add an //TODO to this, and open a new issue to refactor and remove that dependency?
Because It breaks a single responsibility principle.
After you create an issue, I will merge your PR.

https://github.com/afj-solution/buy-it-api/issues/63


Tests needed for TimeOut parameter to Test-Connection

See #2492 - no tests were added but we want to add at least one test.

We should port Test-Connection from WMI to .Net Core. It is ready on 80% in my repo and new tests too


chmod -+ is broken

I'm curious about this issue. Since even GNU coreutils doesn't provide such usage.
I try
$ chmod +0020 file
only get: chmod: invalid mode: +0020'`

Since even GNU coreutils doesn't provide such usage.
It (chmod (GNU coreutils) 8.25) does.

My GNU chmod on Debian is chmod (GNU coreutils) 8.5, and it doesn't provide such usage.
However it can be added, of course.

I found that in rust coreutils
chmod +octal file works fine, -octal will fail with same reason as chmod -x. The arguments are invalid with lib getopts

I'm about to issue a pull request that fixes the behaviour.


feat(backend): added aiosqlite as a new backend

greetings @adriangb !
not sure if this little PR would suit you since the name of the package is very postgresql-centric but I hacked this real quick as I needed it and it was rather easy as the abstractions are very good.
lmk if that suits you, I'm going on holidays tomorrow so likely won't be fast to answer though !
some little comments:

I added latest version of aiosqlite and it's python >= 3.8 so I had to remove 3.7 support here which is not necessarily suitable, I took the opportunity to add 3.11 and 3.12 though
I added extras so that you install either asyncpg or aiosqlite depending on which driver you target
CREATE_TABLE and CREATE_INDEX have to be seperated, sqlite doesnt accept ; in scripts it seems.
I kept the tests folder asyncpg_revisions even for aiosqlite, there doesnt seem to be any driver-specific differences in it anyways.

You know I was planning on keeping this postgres only BUT given that this change is so clean and that I suspect your the main user of this package let's do it! Please just bump the version and we can merge.


@conda-forge-admin, please update version

Additional comment:
No response

@forsyth2, this is what you can do if you're too impatient to wait for the bot to make a PR on its own.  The downside is you probably want to rename the resulting PR...


RFC: turn on Github Discussions

This project just got access to Github Discussions, which I'm considering turning on to focus constructive conversation here, rather than split across stack overflow, ruby mailing lists, and issues.
In particular, I'm wondering if it wouldn't be great to move "Installation" issues to discussion threads. Although generally the docs could be improved, it's uncommon these days (2020) for a github issue to turn into something actionable/fixable in the code.
The downside is that the maintainers (mostly me) may have to do some sort of moderation, which, ugh, doesn't sound fun. But maybe I should go out on a limb.

Anyway, this issue was opened to see if anybody who's listening has an opinion; or can point me to a project that's using Discussions particularly well; or can make suggestions on how to structure the Discussions board.

Parcel.js has a nice board going!

Parcel.js has a nice board going!

I guess that additional downside is that it increases GitHub lockin and makes any future migration more complicated.
But it seems a good place for installation help requests.

Done.


Status bar remains hidden

I like the idea that the status bar hides when the slide menu is in front, but...
If I dismiss the SlideMenuController while the left controller is on top, then next time when I present the slideMenuController the status bar remains hidden forever, even when the leftController is not visibile and the main controller is central on screen.

May bug. I will check it.

I have this issue and its very annoying..

What is the situation of the matter? I still have same issue.

A partial solution is not to hide the status bar:
SlideMenuOptions.hideStatusBar = false

Any progress on this?  Also seeing the issue intermittently.


Enforce maximum amount of users for new users only

When the maximum amount of users is reached, verdaccio-htpassword returned a 403 error when existing users tried to login. This PR is supposed to fix that.
Please verify/test before merging, I only performed a manual test (and concluded that this fixes the outlined issue).

Codecov Report

Merging #28 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #28   +/-   ##
=======================================
  Coverage   89.09%   89.09%
=======================================
  Files           3        3
  Lines         110      110
  Branches       31       31
=======================================
  Hits           98       98
  Misses         11       11
  Partials        1        1

Impacted Files
Coverage Δ

src/utils.js
95.74% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a24b494...ccc967b. Read the comment docs.

What do you think @ayusharma  ?

@juanpicado something like this? I'm a bit out of my comfort zone here as a PHP developer to be honest 😄

@jbtbnl I think would be rather something like this
it('should throw error for existing username and password with max number of users reached', () => {
    const verifyFn = jest.fn(() => true);
    const input = sanityCheck('testNew', users.test, verifyFn, users, 1);

    expect(input.status).toEqual(403);
    expect(input.message).toEqual('maximum amount of users reached');
    expect(verifyFn).toHaveBeenCalledTimes(0);
  });

At the end what you are trying to test is 'maximum amount of users reached'. Could you ammend it?

@juanpicado the behaviour I'm testing here is that error 403 (maximum amount of users reached) should not be thrown when an existing user tries to login (with valid credentials). Instead, NPM client seems to be happy with a 409 error (username is already registered) because the login is successful then.
My test breaks on verdaccio-htpasswd@master, while it passes given the changes in this PR.
Your test passes on both versions. While the test might be valid, it seems to be unrelated to this PR.

@jbtbnl it has been merged on verdaccio master. All seems to works fine. All test passes


Bug 1968253: Start provisioner with controller-publish-readonly option

Let's make use of the new option that would cause ROX volumes to be published read-only.

The migration test failure doesn't seem to be caused by the patch but rather problems in shared-resource-csi-driver.

/lgtm


Determine the visibility based on the original type

The visibility of the projected type and projection method is based on the original type. However, if the visibility of the original type is pub, the visibility of the projected type and the projection method is pub(crate).
Closes #81

bors r+


Bdrate tool

This new tool allows us to inspect BD-rate changes between codecs without going through the
graph generation step.

Unittest added. Also fixed some other stuff, but no major code moves.

Tests added. PTAL.


Port HttpClient Factory test fixes

Porting some improvements to flaky tests that were made in master

/cc @HaoK

Are the test failures known? I didn't do that.
Microsoft.Extensions.Caching.Memory.Tests.Microsoft.Extensions.Caching.Memory.CapacityTests.DoNotAddIfSizeOverflows
Assert.True() Failure
Expected: True
Actual:   False

I'm not sure I have seen some random caching tests fail occasionally on my pr runs too (mostly on linux) but that one doesn't seem familiar, @natemcmaster @Tratcher any ideas?
For example this one failed for me the other day in a PR run too, but its not the same test
https://dnceng.visualstudio.com/public/_build/results?buildId=56490
2018-12-11T23:33:05.3736663Z   Failed   Microsoft.Extensions.Caching.Memory.CapacityTests.AddingReplacementWhenTotalSizeExceedsCapacityDoesNotUpdateRemovesOldEntryAndTriggersCompaction
2018-12-11T23:33:05.3736966Z   Error Message:
2018-12-11T23:33:05.3737156Z    Assert.True() Failure
2018-12-11T23:33:05.3737272Z   Expected: True
2018-12-11T23:33:05.3737420Z   Actual:   False
2018-12-11T23:33:05.3737545Z   Stack Trace:

Some of the tests that depend on background threads have become flaky in the mondo repo because there's a lot more tests run concurrently. We'll have to revisit their synchronization and timeouts.


[BUG]: Error using azure agent to run bundle install to install project gems

What happened?
I have a React Native project that uses Fastlane to handle CI/CD. I have two Mac machines with arm64 chips that I use to run my pipelines using the azure-pipelines-agent. In order to install Fastlane and the required gems for the build process, I run bundle install. When I do this from my repos locally, the command succeeds and all required gems are installed, but when I run that command from within my .yaml file, I get the following error:
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
...
linking shared-object json/ext/generator.bundle
ld: warning: ignoring file
/Users/****/.rbenv/versions/3.1.2/lib/libruby.3.1.dylib, building for
macOS-x86_64 but attempting to link with file built for macOS-arm64
Undefined symbols for architecture x86_64

Is there some reason the agent is trying to build for macOS-x86_64, when I downloaded and am using the arm64 agent on an arm64 machine?
Any help would be appreciated as this is completely preventing me from running my pipelines.
Versions
Occurring with both agent versions 2.170.1 and 3.220.2
macOS versions 13.4 and 13.1
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
No response
Operation system
No response
Version controll system
No response
Relevant log output
current directory:
/Users/bpelton-cox/myagent/_work/1/s/vendor/bundle/ruby/3.1.0/gems/json-2.6.3/ext/json/ext/generator
make DESTDIR\= sitearchdir\=./.gem.20230601-15727-1hqyc
sitelibdir\=./.gem.20230601-15727-1hqyc
compiling generator.c
linking shared-object json/ext/generator.bundle
ld: warning: ignoring file
/Users/bpelton-cox/.rbenv/versions/3.1.2/lib/libruby.3.1.dylib, building for
macOS-x86_64 but attempting to link with file built for macOS-arm64
Undefined symbols for architecture x86_64:
  "_rb_ary_entry", referenced from:
      _cState_to_h in generator.o
      _generate_json_array in generator.o
  "_rb_attr_get", referenced from:
      _cState_aref in generator.o
  "_rb_cArray", referenced from:
      _generate_json in generator.o
  "_rb_cFalseClass", referenced from:
      _generate_json in generator.o
      _json_object_i in generator.o
  "_rb_cFloat", referenced from:
      _generate_json in generator.o
      _json_object_i in generator.o
  "_rb_cHash", referenced from:

Hi @bpeltonc  thanks for the reporting! We're working on higher priority issues, but we'll get back to this one soon

I'm running into the same issue. I'm able to ssh into the agent and run bundle install in a bash shell no problem, but when I run bundle install in a bash task in the pipeline it gives me this "wrong architecture" error for a few packages.
@bpeltonc Have you found any workarounds for this?
@kirill-ivlev Would you happen to have a timeline for when y'all could start looking into this?

I'm running into the same issue. I'm able to ssh into the agent and run bundle install in a bash shell no problem, but when I run bundle install in a bash task in the pipeline it gives me this "wrong architecture" error for a few packages.
@bpeltonc Have you found any workarounds for this?
@kirill-ivlev Would you happen to have a timeline for when y'all could start looking into this?

No workaround yet. I'm doing all my deployments locally instead of via Azure.

@kirill-ivlev My team is looking at abandoning Azure Pipelines since it is at this point completely incompatible with self-hosted arm64 build agents. Is there any roadmap to address this issue, or is it best for us to migrate to another CI/CD provider?

This issue is still a problem for arm64 users running the Azure Build Pipelines client

On Feb 10, 2024, at 11:02 AM, github-actions[bot] @.***> wrote:
This issue has had no activity in 180 days. Please comment if it is not actually stale
—
Reply to this email directly, view it on GitHub https://github.com/microsoft/azure-pipelines-agent/issues/4304#issuecomment-1937063552, or unsubscribe https://github.com/notifications/unsubscribe-auth/AU3TODHT73ER6SMLNJWYAJDYS6R25AVCNFSM6AAAAAAYXHIKQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGA3DGNJVGI.
You are receiving this because you were mentioned.

Please fix this problemOn Aug 8, 2024, at 3:03 PM, github-actions[bot] @.***> wrote:
This issue has had no activity in 180 days. Please comment if it is not actually stale
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@bpeltonc  could you please specify (our provide sample block of YAML schema) - how you are building the project? is it some task or just bash script?

@kirill-ivlev Here are the relevant steps the lead up to and produce the failure
    steps:
      - script: git reset --hard
        displayName: 'Git reset'

      - script: yarn install
        displayName: 'Install Dependencies'

      - script: gem install bundler
        displayName: 'Install bundler'

      - script: bundle install
        displayName: 'Install gems'


fixed missing open quotation mark

missing opening quotation mark in one of the comments for declaring variables examples.

sorry it was bothering me when I came across it, great book though learning a lot about Go!

thanks for the contribution! I'm stuck up with other things, don't check github often


add bitdb.network to services

add bitdb.network to services

Services should apply via https://www.bitcoincash.org/get-listed.html


how cnf claim can be used with any other types of "binding"

like biometrics-based binding
Torsten started with this example in this PR in sd-jwt repo but i do not think it's viable anymore:
    "binding":
      [
        {
          "type": "CryptographicBinding2022",
          "cnf":
            {
              "jwk":
                {
                  "kty": "RSA",
                  "n": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx4cbbf
                    AAtVT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMst
                    n64tZ_2W-5JsGY4Hc5n9yBXArwl93lqt7_RN5w6Cf0h4QyQ5v-65YGjQR0_F
                    DW2QvzqY368QQMicAtaSqzs8KJZgnYb9c7d0zgdAZHzu6qMQvRL5hajrn1n9
                    1CbOpbISD08qNLyrdkt-bFTWhAI4vMQFh6WeZu0fM4lFd2NcRwr3XPksINHa
                    Q-G_xBniIqbw0Ls1jF44-csFCur-kEgU8awapJzKnqDKgw",
                  "e": "AQAB",
                },
            },
        },
        { "type": "BiometricBinding2022", "template": "..." },
      ]

That is similar to the holder binding proposal in W3C that @paulbastian and myself authored. I'm wondering if you would expect binding to be defined by the SD-JWT VC spec, or is this a domain-specific claim? If we want to add something like this to SD-JWT VC and express some sort of holder authentication based on cryptographic binding, then this would relate to this: https://github.com/vcstuff/draft-terbu-sd-jwt-vc/issues/116
Questions:

What does binding express in that case` Holder authentication?
Is the idea to add binding to SD-JWT VC?

I think there is no reason to have the cnf claim so many levels down in the JSON. I'd keep it a top-level claim.
What about the following?
{
  "cnf": {
    "jwk": {
      "kid": "some-kid",
      "...",
    }
  },
  "binding":[{
    "kid": "some-kid",
    "some_metadata": "..."
  }]
}

@awoie I created that example based on you proposal ;-)
Have you implemented any of the proposed options? I'm asking since I have come to the conclusion that it is to pre-mature to standardize the representation of bindings. I would like to see more requirements, concrete use cases and implementations before.

@awoie I created that example based on you proposal ;-)
Have you implemented any of the proposed options? I'm asking since I have come to the conclusion that it is to pre-mature to standardize the representation of bindings. I would like to see more requirements, concrete use cases and implementations before.

We have only an implementation based on the W3C VCDM. Back then we used the binding in the VP actually. So, no, we don't have an implementation.

@Sakurann what do you want to have changed, or was this just a question and we can we close this issue?

We had a Session on this topic at IIW#37.
I still support the ideas that Oliver, I and others described at RWOT#11 Holding Binding Paper.
In my opinion, the cnf claim is the form of binding for cryptogaphic keys.
The alternative binding mechanisms are either claim-based bindings or biometric (claim-based) binding.
Today, there is no equivalent for these claim-based bindings in the SD-JWT-VC Data model and I would suggest something like cbb for claim-based bindings.
Lets take an example as a diploma. The trivial data model could look like:
{
  "title" : "Master of Science in Physics",
  "grade" : "excellent",
  "given_name" : "Erika",
  "family_name" : "Mustermann",
  "date_of_birth" : "1970-01-01"
}

However, this does not communicate which claims are "actually" about the diploma and which ones the diploma issuer used to authenticate the subject and are intended for a relying party to validate user binding of the diploma. The fact that firstname, lastname and birthdate are used for "binding" the diploma is just common human knowledge but not explicitly communicated, the semantic meaning is missing.
A simple approach therefore could be:
{
  "title" : "Master of Science in Physics",
  "grade" : "excellent",
  "cbb" : {
    "given_name" : "Erika",
    "family_name" : "Mustermann",
    "date_of_birth" : "1970-01-01"
  }
}

Other approaches inside cbb are possible.
cbb is not anything mandatory for the Relying Party and things might be different in various jurisdictions. One of the key questions is wehther these policy shall be inside vc or in metadata. I would prefer to have some guidance inside the VC.

I know we discussed this in our paper but can we summarize what we want to achieve @Sakurann @paulbastian. Is this about specifying how the RP wants to verify the holder authenticated the transaction?

I would frame it as "give the RP guidance on how to verify legitimate ownership of the credential". RPs are free to do whatever, they may also ignore a cnf.
My main argument is that the key for keybinding could be in any random claim, but people chose to standardize what the issuer of a token intended to be used for verification. There is no difference to claim-based binding. Our intuition that name, surname, date of birth on a diploma shall be used for binding or totally arbitrary despite seeming "common knowledge".
I believe many Issuers will want to use claim-based binding as this is a 1:1 match of what they have been doing with physical documents and it would mean little changes to their processes, so this is actually very important. Same for biometric binding, e.g. mdL portrait like.
How can we move this forward?

Do we need a separate IETF Draft for biometric+claim-based bindings in JWT or shall this go in here?

A Draft was proposed at OAuth Security Workshop 2024, showing the examples above, advice was more in this direction:
{
  "title" : "Master of Science in Physics",
  "grade" : "excellent",
  "given_name" : "Erika",
  "family_name" : "Mustermann",
  "date_of_birth" : "1970-01-01",
  "cbb" : [ "given_name", "family_name", "date_of_birth" ]
}

Discussion was around whether things should be in policies or metadata, a good argument for this approach/putting it into the JWT is that data available  to the Issuer for binding may not always be the same based on the quality of his user database.
The approach would work really well for countries like Estonia that have a unique national identifier in the PID.

FYI, I created in issue in eKYC-IDA to see if there is some overlap: https://bitbucket.org/openid/ekyc-ida/issues/1414/discuss-a-way-to-express-binding-claims

WDYT about using an object like
"binding": {$type: {claim: ..., any other required by future proof binding type}}

example
{
  "title" : "Master of Science in Physics",
  "grade" : "excellent",
  "given_name" : "Erika",
  "family_name" : "Mustermann",
  "some-memberstate.eu/credentials/schemas/pid/national_id" : "572047251836",
  "credential_binding" : {
     "claims": ["some-memberstate.eu/credentials/schemas/pid/national_id" ]
  }
}

this may open the possibility to specify other types, likecredential_binding.hkb referencing cnf.jwk or any other key binding type

I am not convinced this should be in the JWT itself or that this spec is the appropriate place to define such a thing. Having said that, something like the "cbb" : [ "given_name", "family_name", "date_of_birth" ] seems the most reasonable/logical of the ideas in this issue thus far.

cross comment from https://github.com/openid/OpenID4VP/issues/161 -> This is a somewhat tangential friendly reminder that the cnf claim specified in Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs) is strictly about representing a proof-of-possession key and is therefore entirely inappropriate as a means of conveying 'claims based binding'.


eks-node-viewer: init

Description of changes
They don't have any releases yet, though I still think that community might benefit of having this package in nixpkgs.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] 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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

eks-node-viewer

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

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

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


Add promtool check rules to o11y CI

Enhancement Proposal
Might be useful for detecting syntax errors: promtool check rules.

Apparently there's an action for that:
https://github.com/marketplace/actions/promtool-github-actions


Why does the paper utilize duplicate data from the Alpaca dataset?

Dear @WangRongsheng,
Thank you for your contribution; this paper is amazing. However, I have a question regarding the instruction finetuning dataset as mentioned below:
In the datasets alpaca_data_zh_51k and alpaca_gpt4_data_zh, can you explain why both datasets from Alpaca were used? It appears that the alpaca_gpt4_data_zh dataset might have higher quality as it contains natural responses, unlike the alpaca_data_zh_51k original dataset. Is it more beneficial to utilize both datasets for the instruction finetuning step, or would it be preferable to prioritize using only the alpaca_gpt4_data_zh set due to its inclusion of natural responses?
Thank you for your clarification.
Best regards,

Hi, @danghieuan
I am sorry for taking so long to respond to you.
alpaca_data_zh_51k comes from the response of ChatGPT3.5, and alpaca_gpt4_data_zh comes from the response of GPT-4. Generally, the quality of alpaca_gpt4_data_zh is better than that of alpaca_data_zh_51k, but compared to the data collected from other websites, we believe that both alpaca_data_zh_51k and alpaca_gpt4_data_zh are of high quality.
On the other hand, command fine-tuning requires sufficient data training. Therefore, we have adopted two datasets.
I hope this helps. Thank you.

Thank @WangRongsheng . I got it.


Gaussian Processes with Input-dependent Noise Variance

Can GPy handle the Input-dependent Noise Variance case?
dataset like:
X = np.random.random_sample((500,)) * 20
print X
Y = []
for x in X:
    var = np.random.normal(0,x*x,1)[0]
    y = x*x + var
    Y.append(y)
Y = np.array(Y)
X = X[:, None]
Y = Y[:, None]

other example: http://www.robot.t.u-tokyo.ac.jp/~yamashita/paper/B/B122Final.pdf
Expected effect：

my code, did not succeed：
import numpy as np
import math

X = np.random.random_sample((500,)) * 20
print X
Y = []
for x in X:
    var = np.random.normal(0,x*x,1)[0]
    y = x*x + var
    Y.append(y)
Y = np.array(Y)
X = X[:, None]
Y = Y[:, None]
print X
print Y

max_iters = 100
warp_k = GPy.kern.RBF(1)
warp_f = GPy.util.warping_functions.TanhFunction(n_terms=2)
warp_m = GPy.models.WarpedGP(X, Y, kernel=warp_k, warping_function=warp_f)
warp_m['.*\.d'].constrain_fixed(1.0)
m = GPy.models.GPRegression(X, Y)
m.optimize_restarts(parallel=False, robust=True, num_restarts=5, max_iters=max_iters)
warp_m.optimize_restarts(parallel=False, robust=True, num_restarts=5, max_iters=max_iters)
#m.optimize(max_iters=max_iters)
#warp_m.optimize(max_iters=max_iters)

print(warp_m)
print(warp_m['.*warp.*'])

warp_m.predict_in_warped_space = False
warp_m.plot(title="Warped GP - Latent space")
warp_m.predict_in_warped_space = True
warp_m.plot(title="Warped GP - Warped space")
m.plot(title="Standard GP")
warp_m.plot_warping()
pb.show()

This sounds like the use case of chained GP. @alansaul, do you have a version of chained GP available in GPy?

Thank you for your reply. @zhenwendai
It seems that **
Heteroscedastic Gaussian processes** also meets my needs.
such as https://github.com/OxfordML/GPz. I tested its code, although it is implemented with matlab.

I also found that GPy had a issue about it. https://github.com/SheffieldML/GPy/issues/306
But I don't know how to implement and which API to invoke.


AWS SQS: Respect scaleOnDelayed

Provide a description of what has been changed
Checklist

[x] When introducing a new scaler, I agree with the scaling governance policy
[x] I have verified that my change is according to the deprecations & breaking changes policy
[x] Tests have been added
[x] Changelog has been updated and is aligned with our changelog requirements
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[x] A PR is opened to update the documentation on (repo) 1091
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #

Relates to #4377

@ding1992 any update on this please?

I'm very interested in this functionality. @ding1992 any updates at all? Anything I can help with?

I'm very interested in this functionality. @ding1992 any updates at all? Anything I can help with?

I feel that @ding1992 has abandoned it :/
Are you willing to implement it from your side @phr3nzii and open another PR?

@JorTurFer Yes, I'll give it a go!

I linked to this PR in my new PR, but just for clarity, here is the new PR https://github.com/kedacore/keda/pull/4900

already done by https://github.com/kedacore/keda/pull/4900


Remove test target

There is no target in the Makefile for tests (and there is no tests in this repo in general it seems like)

The other option is to actually add tests here like in a.js-private (https://github.com/segmentio/analytics.js-private/blob/master/test/index.test.js)

@f2prateek I definitely agree, #541, I don't have access to analytics.js-private BTW


[Event Request] - PurchPost.Codeunit.al - OnAfterInsertReceiptHeader

We like to request the following Event:
Object: PurchPost.Codeunit.al
Where is the event placed:
procedure InsertReceiptHeader
...
if WhseShip then begin
WhseShptHeader.Get(TempWhseShptHeader."No.");
OnBeforeCreatePostedWhseShptHeader(PostedWhseShptHeader, WhseShptHeader, PurchHeader);
WhsePostShpt.CreatePostedShptHeader(PostedWhseShptHeader, WhseShptHeader, "Receiving No.", "Posting Date");
end;
end;
OnAfterInsertReceiptHeader(PurchHeader, PurchRcptHeader, TempWhseRcptHeader, WhseReceive, SuppressCommit);
end;
local procedure InsertReceiptLine(PurchRcptHeader: Record "Purch. Rcpt. Header"; PurchLine: Record "Purchase Line"; CostBaseAmount: Decimal)
var

Event Code:
[IntegrationEvent(false, false)]
local procedure OnAfterInsertReceiptHeader(var PurchHeader: Record "Purchase Header"; var PurchRcptHeader: Record "Purch. Rcpt. Header"; var TempWhseRcptHeader: Record "Warehouse Receipt Header" temporary; WhseReceive: Boolean; CommitIsSuppressed: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Update react intl dependency format

Summary

This PR updates the formatting of the react-intl dependency in the packages for better clarity. The allowed packages before and after the change should be identical as with the npm semver calculator tool.
Before:

After:

Testing

This change was tested using:

[ ] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-XXXX

Thank you for contributing to Terra.
@cerner/terra

Fails
🚫	Please include a CHANGELOG entry for each changed package this PR. Looks like a CHANGELOG entry is missing for:

terra-abstract-modal
terra-application-header-layout
terra-application-layout
terra-application-links
terra-application-navigation
terra-application-utility
terra-collapsible-menu-view
terra-compact-interactive-list
terra-data-grid
terra-date-input
terra-date-picker
terra-date-time-picker
terra-embedded-content-consumer
terra-infinite-list
terra-navigation-side-menu
terra-notification-dialog
terra-pills
terra-popup
terra-slide-panel
terra-table
terra-tabs
terra-time-input

Generated by 🚫 dangerJS against 7d62824

CHANGELOG entries are not needed for this update.


Adding className to non-dom elements

styled-jsx works fine, however, as soon as we have a component like an <Icon /> component that we want to customize with <Icon className='invisible' />, the className is not passed down.
This is a huge problem, as we use a lot of these components and now our workaround is to use global all the time, which removes the isolation.
With styled-components you don't have that problem, there you can do styled(Icon)`...`
Is there a better approach than using global?
Thank you!

Do you mean that the className prop is not passed down or are you asking if it is possible to pass down [data-jsx="currentComponentID"] to Icon?

I'm asking if it is possible to pass down [data-jsx="currentComponentID"] to Icon

This is intentionally removed by https://github.com/zeit/styled-jsx/issues/71
Actually, I also feel this is inconvenient in some situations, but closestparent :global(> *) { color: red; } is a way to do something similar for now.
https://github.com/zeit/styled-jsx/issues/66#issuecomment-270601315

Updated my comment, it is closestparent > :global(*) {}
One problem with the above is that * doesn't affect the selector specificity which sometimes it is what we want instead. A workaround is to target children by tag, class, attribute or id e.g. closestparent > :global(div)
The reason why I think that passing down the data-jsx attribute with the parent id currentComponentID is not a good idea is that:

the child component might already have its own data-jsx attribute (elements can't have duplicate attributes by spec) and we don't have a way set or override it
setting the data attribute on the child component root doesn't buy you much – you'd still need to target descendants with global if you want to style them.

the child component might already have its own data-jsx attribute (elements can't have duplicate attributes by spec) and we don't have a way set or override it

I think we can avoid this if we change data-jsx="123" to data-jsx-123 ?

setting the data attribute on the child component root doesn't buy you much – you'd still need to target descendants with global if you want to style them.

I think this is not required when you assume webcomponent-like behaviors. Style for top level element is enough.
Though I am not trying to say we should revert it. I just want to have a clean alternative way.

I think we can avoid this if we change data-jsx="123" to data-jsx-123 ?

Yep that could work (probably better call it data-jsx-parent={123}) although we'd need to rewrite every react component to set that attribute

Hey @giuseppeg thanks for that workaround!
Indeed :global(.child-class) works perfectly, I'm even using it with styled-jsx-postcss and cssnext.
I also just realized that it's described here in the README.
So for me it's resolved, we can close it.
This passing down thing is not needed and I like this parent class scoping.


Fix action on invisible

Remove option selectHiddenElements on selectors
Introduce option force on page actions to enforce action irrespective of element being unactionable
Element wrapper chooses first visible element to perform action if nothing is visible returns the first available element

@NivedhaSenthil You removed the definition for SelectionOptions in index.d.ts but currently they are still being referenced in the 'Selectors' section of index.d.ts. Example:
// https://docs.taiko.dev/api/image
export function image(
  selector: SearchElement,
  options?: SelectionOptions | RelativeSearchElement,
  ...args: RelativeSearchElement[]
): ImageWrapper;

Ideally options as a parameter can be removed from the selectors except for ones that are using Text based searches.. but for now it is fine to just remove the SelectionnOptions as mentioned above in your PR.


[FEAT] Add Support for Astro framework

Is your feature request related to a problem? Please describe.
Yes
Since astro is the favourite framework as per the latest rising star directory
Refine supports Remix which has only 26k stars while Astro has 38k stars
So please add the support for Astro since it's way more popular
Describe alternatives you've considered
No response
Additional context
No response
Describe the thing to improve
Nothing to improve
Just add Astro support

Hello @RayyanNafees could you elaborate more on this Astro integration?


deposit form: add responsive layout

Closes #445

Stacked sidebar for tablet and mobile.

Screenshots
Tablet

Mobile

the PR needs rebase

Updated screenshots
Note: The deposit form components also need responsive improvements. This PR is only for the overall layout.


Added blot writer

[x] I have read the steps to getting a blot

[x] I am submitting art that alows you to write with wour own font

[x] is algorithmically generated (will change each time the program is run) (if you change your input)
[x] is drawable on a blot (fits in the work area & doesn't overlap too much)
[x] is original (not copied from somewhere else) didn't found any project thats allow you to set your own font
[x] doesn't call Math.random() (See the documentation on randomness)

[ ] Optional, if you used a tutorial or based your art on something else, please include the link here:

[ ] Optional, if you remixed this from something else, mention it here:

There is no problem if it can't be shared, made it to be useful, not famous haha, maybe in the future if a section for scripts that doesn't meet the requirements but still are cool were made I would apply for it. I don't want this to be an issue if somebody took my script as a reference for their design and demanded their to be accepted because mine did.
Thanks for taking me into account 😄

I'm going to close this for now, but nice work! Maybe somebody will use it someday. Feel free to make another submission if you would like in the future!


Better "404 - Page not Found" page

Create a better design for the  "404 - Page not Found" page (NotFound Component).
Currently it only displays a h1 with the "404 - Page not Found" text and with no styling... 🤔
The objective is to give it some nice styling so that the 404 page could potentially fit any project created from this template and needing little to no changes.

I would like to give it a try. 💪🏻

@BillNas Thank you for your effort. Let me know if you need any help! 👌👍


No CI

It would be nice if this repo had CI that automatically ran the test suite and build documentation on PRs.

About to be fixed in #4 :)


Skipping test that randomly fails.

Pull Request Description
What issue does this change request address?
Closes #1730
What are the significant changes in functionality due to this change request?
Skips tests/cluster_tests/test_mpiqsub_limitnode

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Test qsubs falcon on c96de4f : invalidated by @joshua-cogliati-inl
Failed tests/framework/ensembleModelTests/testEMReusability  tests/framework/ensembleModelTests/testEMConnection

Changes are good, and checklist is satisfied. PR can be merged.


Disable DM

Hey guys, - newbie here.. is there a way to disable direct messaging hubot on slack to run commands? Would like to keep all comms in a specific channel.

It depends on Hubot Adapter you use. Some may have this specific functionality, some may not.
See https://github.com/hubotio/hubot/issues/1356
Also in theory, it might be possible to implement it, after looking at https://github.com/slackapi/hubot-slack/issues/339
Contributions are welcome here!


Show LV2 to Text is not working on my side using version 2.1

I poked the message "Hello World!" at the LV2 address 0x8000000000000000 using the web command:
http://0/poke.lv2?0=Hello+World!
The message does not display and the values are not cleared from memory by the plugin.
I'm using Evilnat 4.88.2 Cobra 8.30.

I tested your method and also through ps3mapi and both worked. Internal code uses PS3MAPI_OPCODE_LV2_PEEK could that be an issue on CEX?
http://<IP_ADDRESS>/setmem.ps3mapi?proc=2&addr=0&val=68656C6C6F2066726F6D206B65726E656C000000

http://<IP_ADDRESS>/poke.lv2?0=Hello+World!

Thank you for your reply. I wonder if you uploaded a version 2.1 without the LV2 to text. The Celcius / Fahrenheit is showing fine.

I actually tested this with the VshFpsCounter sprx you provided with the lastest wMM

OK. Could you test on CEX?

It is not working on CEX. Something is resetting the bytes to 00 00 00 00 @ 0x8000000000000000 I even tried to remove the reset code in the sprx and somehow it is still getting reset.

Could you try reading from a different address?

I've changed the offset from 0x8000000000000000 to 0x8000000000700000 this seems to work on both CEX and DEX. This could be bad if LV2 allocates to that offset or boot_plugins_kernel payload decided to allocate to that offset. I will say this method should be used as just a concep.
We should definitely create a cobra opcode with ps3mapi and let xai_plugin handle it as a vsh notfication what do you think?
Test this sprx and report back
https://gofile.io/d/QkDpRE

I tested your new plugin and for some reason it still doesn't show the text.
Maybe the issue is the method that you use to peek the value. Could you use syscall 6 (peek lv2) intead of peek lv2 through ps3mapi?
If check the memory the poked value is not removed by the plugin.

I don't think xai would be a solution, since I'm looking for a persistent overlay message to show the progress of the content scanning, dumping %, copy progress, etc.

Well I used peek from ps3mapi because of my hen console which I did the tests on.
On my end both this one and previous one are confirmed working.
This one is using syscall 6
https://gofile.io/d/ShbNtL
By the way the message is cleared by the plugin after 5 seconds

Now it's working 😄 THANK YOU!!! ❤ ❤ ❤ ❤ ❤

The message clearing is cool as it is now, but I think it is working as regular popup.
I was looking for something that show the poked value in real time until it is removed by the homebrew. So if I poke 100 messages in minute (e.g. during a copy progress), it display at least 10 or 20 messages (depending of the poll rate that you use).
The idea is to have a "label" not a "msgbox" :-)

Probably the original address 0x8000000000000000 works with syscall 6

Probably the original address 0x8000000000000000 works with syscall 6

will syscall 6 work on hen though?

Ahhh I'm not sure... I don't use HEN. I was thinking in using the address also in-game.

is there a reason why your PS3MAPI_OPCODE_LV2_PEEK isn't working?

On Cobra or HEN?

On Cobra and HEN. I tried it on cobra 8.3 and HEN 3.0.3 and both worked fine for me.

I was using syscall 6 in my test. I only use PS3MAPI opcode if syscalls are disabled.

So should I revert back to PS3MAPI_OPCODE_LV2_PEEK for compatability since you had syscalls disabled?

What I understood is that it worked when you used syscall 6 (lv2 peek).

for me it had always worked no matter the peek syscall. but for you it only started working with syscall 6

I only used syscall 7 (lv2 poke). Maybe the ps3mapi opcode in the payload is peeking in a wrong address.

This version has persistence until message is cleared by the user.
https://gofile.io/d/kwUUqG

This version has persistence until message is cleared by the user. https://gofile.io/d/kwUUqG

Perfect!! 😀

This version has persistence until message is cleared by the user. https://gofile.io/d/kwUUqG

Hi master, this 2.1 version can "Quit Game" PSN PS3 normally.
Only when "Disable CFW" appears 1 Chinese character at the top right of the screen and all games don't work.
I'm using HEN 3.0.3
Thanks.

This version has persistence until message is cleared by the user. https://gofile.io/d/kwUUqG

Hi master, this 2.1 version can "Quit Game" PSN PS3 normally. Only when "Disable CFW" appears 1 Chinese character at the top right of the screen and all games don't work.
I'm using HEN 3.0.3
Thanks.

And reboot or turn off seems abnormal, triple beeps.
Thanks.


0.1.5 release pre-validation

Description
I've made all the changes listed in https://github.com/spatialos/gdk-for-unity/wiki/Release-Process and am now opening a PR to pull this branch into develop as per that process.
Tests
None yet, I'm about to run validation steps.
Documentation
Noted the release in the changelog.
Primary reviewers
@jamiebrynes7

Closed as this release will not be cut fresh from develop next week


Add jsonb has, has_any, has_all lookups

Also moves the lookup value coercion to the more
appropriate get_prep_lookup function
Tested with Django 1.8 and Python 2.7.8

Thanks!


Fix live update when an administrator revokes an invitation created by another user

As detailed in https://github.com/zulip/zulip/pull/25884/files#r1317898370, we are introducing a subtle live-update bug where if an administrator revokes an invitation created by another user, that user's invitations settings panel won't live-update properly. I expect the fix to be pretty simple, so we should just aim to get it in during the next week.
(We don't need an API feature level change -- the right way to think about this is just that there's a subtle logic bug in the existing about-to-be-merged documented API)

Closing this since there was some confusion due to variable name and there was no live-update bug introduced by #25884.


gm batch not find -safe-mode category. now change to -stop-on-error

GraphicsMagick 1.3.21 2015-02-28 Q8 http://www.GraphicsMagick.org/
Copyright (C) 2002-2014 GraphicsMagick Group.
Additional copyrights and licenses apply to this software.
See http://www.GraphicsMagick.org/www/Copyright.html for details.
Usage: gm batch [options ...] [file|-]
Where options include:
-echo on|off         echo command back to standard out, default is off
-escape unix|windows force use Unix or Windows escape format for command line
argument parsing, default is platform dependent
-fail text           when feedback is on, output the designated text if the
command returns error, default is 'FAIL'
-feedback on|off     print text (see -pass and -fail options) feedback after
each command to indicate the result, default is off
-help                print program options
-pass text           when feedback is on, output the designated text if the
command executed successfully, default is 'PASS'
-prompt text         use the given text as command prompt. use text 'off' or
empty string to turn off prompt. default to 'GM> ' if
and only if batch mode was entered with no file argument
-stop-on-error on|off
when turned on, batch execution quits prematurely when
any command returns error
Unix escape allows the use backslash(), single quote(') and double quote(") in
the command line. Windows escape only uses double quote(").  For example,
Orignal             Unix escape              Windows escape
[a\b\c\d]           [a\\b\\c\\d]             [a\b\c\d]
[Text with space]   [Text\ with\ space]      ["Text with space"]
[Text with (")]     ['Text with (")']        ["Text with ("")"]
[Mix: "It's a (\)"] ["Mix: \"It's a (\\)\""] ["Mix: ""It's a (\)"""]

Use '-' to read command from standard input without default prompt.

Fix is committed, would you please help to test and report if that fixes the problem?

closing as no issue reported.


Delete app.js

🎉 Snyk hasn't found any issues so far.
✅ security/snyk check is completed. No issues were found. (View Details)


Errors feels like dead ends; need better error messaging (Elise/Drake to help define)

Wasn't sure what to name this one so feel free to adjust.

In this case, I tried to score a submission on a challenge that I did not signal to review for.
The error tells me that I didn't signal but as a user I'm not sure where to go next
It is entirely possible that I could still signal and score this submission but the error makes me bail. Are there ways to have the errors be encouraging of an action to take?

Users shouldn't even be allowed to see this UI unless they've signaled. I think this is fixed by properly gating the review action.

@sebruiz is it possible to export a list of all the error messages we have in Metrics App so Drake and I can try and wordsmith some better language for each?

Drake idea -- also add CTAs in addition to messaging. i.e. you need to signal, direct them to signal