Simplify Msg trait by removing unnecessary interfaces

Closes: #218
Definition
Examine the usage of Msg APIs in both internal and external contexts (dependent Repos) and implement the best approach. The Msg is mainly employed to convert different messages to Any type but through various practices.
Use Cases

Internally, It is implemented on all message types but only operated once the validate_basic() method, which could be ported and coded locally. It is not used for converting to Any type.
Inside ComposableFi/Centauri repo, the type_url is called to build Any messages, like here.
This part can be delegated to the respective const TYPE_URL
Looking at Penumbra-zene/penumbra repo, Msg trait was recently implemented on the IbcAction type here,
but not utilized yet.
Anoma/Namad uses the to_any() method, like here
nomic-io/orga build the needed Any message locally

Approaches

Remove Msg trait and leave it to be implemented outside the ibc-rs boundary. You could do it by importing TYPE_URL and using raw_msg.encode_vec()
Remove Msg trait, but implement From<Msg* types> for Any for each of the message types to expose Any conversion, similar to here
Simplify the current Msg trait by cleaning route(), validate_basic() and Error type

I chose the 3rd one. 1st may not be developer-friendly. Also, the 3rd offer the min required methods with fewer lines of code than the 2nd approach, except it exposes excessive type_url() and get_sign_bytes()
Btw, Please lmk your thoughts on this to pick the best one.

PR author checklist:

[X] Added changelog entry, using unclog.
[ ] Added tests.
[X] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Thank you @plafer 🙏
Fixed here https://github.com/cosmos/ibc-rs/pull/315/commits/c8353fdf184919f915191c3fa6a3971c40256177


Beta 2 - Broken images, weird text editing behaviour (line duplication, mirage text)

Bug Description
So I was informed by a client that the page I directed them to was not working. Upon checking the pages in the editor, images that were in the gallery were showing as missing (broken image). Also, while changing text, a line lower on the page was duplicated higher up on the page but in reality, that text wasn't really there. It was covering up some other text underneath it. Deleting that text was deleting the actual text on that line. (Sorry best I could describe what I saw happening. It was truly f'd up hence the 'mirage' text description)
Expected Behaviour
Just reporting odd issues. Images shouldn't be showing as missing if they are in the gallery.
Steps to Reproduce
Unsure
Screenshots
I missed the opportunity to grab shots. I will for next time.
Additional Context

Plugin Version: 1.00Beta2
Operating System: Win10
Browser: Chrome (latest)
WP5.5 w/WPMigrate installed
PHP php74rc

Downgraded to 1.00Beta1 and those problems resolved.

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

@quadcom thanks for reporting!

If possible could you send us a URL of the story and perhaps a recording of what you experience? You can use something like Recordit to capture a screencast the issues.

When you create a new story does the issue persist?

@quadcom is your client using Cloudflare or LiteSpeed cache?

No, I'm the client. It's my own site.
One thing I have to add is I moved the site from torontoheadshot.com/m to m.torontoheadshot.com. That move caused Google Site Kit to completely implode which was causing major issues just loading stories in the editor. I keep getting fatal errors pop up.
I had to completely remove Site Kit and reinstall it and then go and reconnect all the services. Once that was done Stories started working ok again. Not sure where the connection is between Site Kit and Stories.
While I was able to get the story opened in the editor. I had to replace the broken images in the pages and I haven't seen the issue pop up since so I can't say 100% what the cause of the problem was. I wish I could.
I will add {off topic} that while I do like the main stories gallery layout. I often find myself going to list view and then WordPress list view so that I can get to both the view link and to adjust SEO focus keyword settings provided by Rankmath. There's also no place to provide or adjust and SEO details for the story.

@quadcom thanks for these details! It looks like we were also troubleshooting your site in this issue previously. For Site Kit, it relies on your WordPress site settings to determine where your site is located and where to place code snippets.
There is automatic compatibility with Site Kit and Web Stories, so when both are activated and configured the Analytics tracking for Web Stories will be applied to Web Story URLs given that the location of the site is defined in the WordPress settings (in your previous case it appears you may have had a redirect on the URL where your stories were located which could affect the way Site Kit works).

There's also no place to provide or adjust and SEO details for the story.

This is on our radar and implementation can be tracked in the following issues:
https://github.com/google/web-stories-wp/issues/490
https://github.com/google/web-stories-wp/issues/3134
Note that the Web Story URL provides default metadata (SEO and Social), so are valid out of the box and soon to be customizable.


Use the new AshMoney package

We should use AshMoney instead of separate currency and amounts identifiers. I have a branch for this currently: use-ash-money, but I'm still working on it.

This is done.


added images and custom css

Added both images as requested and adjusted images such that logos are same size.
Desktop:

Tablet:

Mobile:

thnx!


AOT compilation script reference missing

🐞 bug report
In AOT compilation script reference missing
Description
In development build sample render properly but production build not render properly.
Production Build
Value not binded properly
"build:prod": "node_modules/.bin/ng build --prod --aot --source-map=false --vendor-chunk=true --output-hashing none"

Development Build
Value is properly binding
"build:dev": "node_modules/.bin/ng build --source-map=false --vendor-chunk=true --output-hashing none"

Hi @SathishKumarRajendran, please share the full output of ng version?
In case you are on Angular 8 or lower, kindly update to Angular 9 and verify if the problem persists. If you are already on Angular 9 please setup a minimal repro please.
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

HI @alan-agius4 ,
Due to this issue, we have changed our mixin method like below:
export function applyMixins(derivedClass, baseClass) {
    baseClass.forEach(function (baseClass) {
        Object.getOwnPropertyNames(baseClass.prototype).forEach(function (name) {
            if (!derivedClass.prototype.hasOwnProperty(name)) {
                derivedClass.prototype[name] = baseClass.prototype[name];
            }
        });
    });
}

But this change working fine in development mode, but when we run application in prod mode it affects my form base components value binding

Hi @kumaresan-subramani, can you please share a reproduction containing the least amount of code to reproduce the problem and push the repository to github and link it here please.
Can you confirm if turning Build Optimizer off fixes the problem?

Can you confirm if turning Build Optimizer off fixes the problem?
Yes if turning build optimizer off, it is working fine.

Hi @SathishKumarRajendran, I just tried to use your reproduction however I am getting installations errors such as Couldn't find any versions for "@syncfusion/ej2-angular-calendars" that matches "^18.1.43"
Also it looks like the application was generated using Angular CLI version 8. Can you please update the reproduction to use the current latest stable version (9.1)?
Thanks

Hi @alan-agius4 ,
We have resolved installation issue, please follow same steps again
https://github.com/angular/angular-cli/issues/17421#issuecomment-611313272
since we need to get this application work in angular 8

Hi @kumaresan-subramani, I tried to take a look at the reproduction again. However, it is still not in a working state.
I am getting the below errors;

ERROR in src/app/app.module.ts:6:41 - error TS2307: Cannot find module '@syncfusion/ej2-angular-inputs'.

6 import { NumericTextBoxAllModule } from '@syncfusion/ej2-angular-inputs';
                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/app/app.module.ts:7:37 - error TS2307: Cannot find module '@syncfusion/ej2-angular-calendars'.

7 import { DatePickerAllModule } from '@syncfusion/ej2-angular-calendars';
                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/app/app.module.ts:8:39 - error TS2307: Cannot find module '@syncfusion/ej2-angular-dropdowns'.

8 import { DropDownListAllModule } from '@syncfusion/ej2-angular-dropdowns';
                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ERROR in src/app/app.module.ts(17,9): Error during template compile of 'AppModule'
  Could not resolve @syncfusion/ej2-angular-inputs relative to [object Object]..
src/app/app.module.ts(17,34): Error during template compile of 'AppModule'
  Could not resolve @syncfusion/ej2-angular-calendars relative to [object Object]..
src/app/app.module.ts(17,55): Error during template compile of 'AppModule'
  Could not resolve @syncfusion/ej2-angular-dropdowns relative to [object Object]..
src/app/app.module.ts(17,9): Error during template compile of 'AppModule'
  Could not resolve @syncfusion/ej2-angular-inputs relative to [object Object]..
src/app/app.module.ts(17,34): Error during template compile of 'AppModule'
  Could not resolve @syncfusion/ej2-angular-calendars relative to [object Object]..
src/app/app.module.ts(17,55): Error during template compile of 'AppModule'
  Could not resolve @syncfusion/ej2-angular-dropdowns relative to [object Object]..
: 'ejs-numerictextbox' is not a known element:
1. If 'ejs-numerictextbox' is an Angular component, then verify that it is part of this module.
2. If 'ejs-numerictextbox' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. ("

                    [ERROR ->]<ejs-numerictextbox [(ngModel)]="orderData.Freight" name="Freight" id="Freight" placeholder="Freight"")
: 'ejs-datepicker' is not a known element:
1. If 'ejs-datepicker' is an Angular component, then verify that it is part of this module.
2. If 'ejs-datepicker' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. ("

                    [ERROR ->]<ejs-datepicker id="OrderDate" name="OrderDate" required [(ngModel)]="orderData.OrderDate" placeholde")
: Can't bind to 'dataSource' since it isn't a known property of 'ejs-dropdownlist'.
1. If 'ejs-dropdownlist' is an Angular component and it has 'dataSource' input, then verify that it is part of this module.
2. If 'ejs-dropdownlist' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("          <ejs-dropdownlist id="ShipCountry" name="ShipCountry" [(ngModel)]="orderData.ShipCountry" [ERROR ->][dataSource]='shipCountryDistinctData' [fields]="{text: 'ShipCountry', value: 'ShipCountry' }" placeh")
: Can't bind to 'fields' since it isn't a known property of 'ejs-dropdownlist'.
1. If 'ejs-dropdownlist' is an Angular component and it has 'fields' input, then verify that it is part of this module.
2. If 'ejs-dropdownlist' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("ntry" name="ShipCountry" [(ngModel)]="orderData.ShipCountry" [dataSource]='shipCountryDistinctData' [ERROR ->][fields]="{text: 'ShipCountry', value: 'ShipCountry' }" placeholder="Ship Country" popupHeight='300px")
: 'ejs-dropdownlist' is not a known element:
1. If 'ejs-dropdownlist' is an Angular component, then verify that it is part of this module.
2. If 'ejs-dropdownlist' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. ("

                    [ERROR ->]<ejs-dropdownlist id="ShipCountry" name="ShipCountry" [(ngModel)]="orderData.ShipCountry" [dataSource")
: Can't bind to 'dataSource' since it isn't a known property of 'ejs-dropdownlist'.
1. If 'ejs-dropdownlist' is an Angular component and it has 'dataSource' input, then verify that it is part of this module.
2. If 'ejs-dropdownlist' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("                   <ejs-dropdownlist id="ShipCity" name="ShipCity" [(ngModel)]="orderData.ShipCity" [ERROR ->][dataSource]='shipCityDistinctData' [fields]="{text: 'ShipCity', value: 'ShipCity' }" placeholder="Sh")
: Can't bind to 'fields' since it isn't a known property of 'ejs-dropdownlist'.
1. If 'ejs-dropdownlist' is an Angular component and it has 'fields' input, then verify that it is part of this module.
2. If 'ejs-dropdownlist' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. (" id="ShipCity" name="ShipCity" [(ngModel)]="orderData.ShipCity" [dataSource]='shipCityDistinctData' [ERROR ->][fields]="{text: 'ShipCity', value: 'ShipCity' }" placeholder="Ship City" popupHeight='300px' floatLa")
: 'ejs-dropdownlist' is not a known element:
1. If 'ejs-dropdownlist' is an Angular component, then verify that it is part of this module.
2. If 'ejs-dropdownlist' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. ("

                    [ERROR ->]<ejs-dropdownlist id="ShipCity" name="ShipCity" [(ngModel)]="orderData.ShipCity" [dataSource]='shipCi")

After installing the missing modules, I get more errors;
ERROR in src/app/template-driven.html(14,32): : Property 'OrderID' does not exist on type 'object'.
src/app/template-driven.html(24,32): : Property 'CustomerID' does not exist on type 'object'.
src/app/template-driven.html(35,41): : Property 'Freight' does not exist on type 'object'.
src/app/template-driven.html(38,78): : Property 'OrderDate' does not exist on type 'object'.
src/app/template-driven.html(43,75): : Property 'ShipCountry' does not exist on type 'object'.
src/app/template-driven.html(46,69): : Property 'ShipCity' does not exist on type 'object'.
src/app/template-driven.html(52,35): : Property 'ShipAddress' does not exist on type 'object'.
src/app/template-driven.html(14,32): : Property 'OrderID' does not exist on type 'object'.
src/app/template-driven.html(24,32): : Property 'CustomerID' does not exist on type 'object'.
src/app/template-driven.html(35,41): : Property 'Freight' does not exist on type 'object'.
src/app/template-driven.html(38,78): : Property 'OrderDate' does not exist on type 'object'.
src/app/template-driven.html(43,75): : Property 'ShipCountry' does not exist on type 'object'.
src/app/template-driven.html(46,69): : Property 'ShipCity' does not exist on type 'object'.
src/app/template-driven.html(52,35): : Property 'ShipAddress' does not exist on type 'object'.
src/app/template-driven.html(1,50): : Property 'pageSettings' does not exist on type 'AppComponent'.

Hi @alan-agius4
Sorry for inconvenience, We are now resolved above mentioned two issues. Could you please repeat that repro steps again.
Thanks

Hi @alan-agius4
Any updates on this?

Hi @SathishKumarRajendran,
I looked at the reproduction provided and the problem is caused the the following
function applyMixins(derivedClass, baseClass) {
    baseClass.forEach(baseClass => {
        Object.getOwnPropertyNames(baseClass.prototype).forEach(name => {
            if (!derivedClass.prototype.hasOwnProperty(name) || baseClass.prototype.constructor.name === 'FormBase') {
                derivedClass.prototype[name] = baseClass.prototype[name];
            }
        });
    });
}

The below, is the problematic statement, because class names are mangled when using optimizations (aka production builds), this means that it the result will also be false.
baseClass.prototype.constructor.name === 'FormBase'

There are a couple of things you can do there:

You can disable mangling by extending the build pipeline using ngx-build-plus, though this will take you on the unsupported path.
Another approach would be to add a static property in the FormBase class and in the mixin check for that.

export class FormBase {
  static readonly isFormBase = true;
}

export function applyMixins(derivedClass, baseClass) {
    baseClass.forEach(function (baseClass) {
        Object.getOwnPropertyNames(baseClass.prototype).forEach(function (name) {
            if (!derivedClass.prototype.hasOwnProperty(name) || baseClass.isFormBase) {
                derivedClass.prototype[name] = baseClass.prototype[name];
            }
        });
    });
}


Domoticz log overflow with zigbee comments

Issue description
Since tatest update Domoticz log overflow with zigbee comment
Additional information
Zigbee2MQTT version:1.3.1
Python version:3.5.3
Domoticz version:4.10693
Plugin version:00.18
Logs
Domoticz log look like this, how can I stop this
2019-05-08 20:18:58.631 (Zigbee Gateway) Received available devices list from bridge
2019-05-08 20:18:58.631 (Zigbee Gateway) Device WXKG02LM 0x00158d0002569754 (aqara_ws01)
2019-05-08 20:18:58.632 (Zigbee Gateway) Device MFKZQ01LM 0x00158d00028f419c (aqara_cube)
2019-05-08 20:18:58.632 (Zigbee Gateway) Device WXKG02LM 0x00158d0002fceef7 (aqara_ws02)
2019-05-08 20:18:58.633 (Zigbee Gateway) Device KS-SM001 0x01124b001bae7cd6 (zonoff_01)
2019-05-08 20:18:58.633 (Zigbee Gateway) Device ZNCZ02LM 0x00158d00032d365d (mijia_ps01)
2019-05-08 20:18:58.634 (Zigbee Gateway) Device JTYJ-GD-01LM/BW 0x00158d0002cb06a7 (honeywell_01)
2019-05-08 20:18:58.634 (Zigbee Gateway) Device MCCGQ11LM 0x00158d0003121273 (aqara_ds01)
2019-05-08 20:18:58.635 (Zigbee Gateway) Device MCCGQ11LM 0x00158d000312e39d (aqara_ds02)
2019-05-08 20:18:58.635 (Zigbee Gateway) Device WSDCGQ11LM 0x00158d0002d79082 (aqara_thp02)
2019-05-08 20:18:58.636 (Zigbee Gateway) Device WSDCGQ11LM 0x00158d000303ca09 (aqara_thp01)
2019-05-08 20:18:58.637 (Zigbee Gateway) Device WSDCGQ11LM 0x00158d0003499181 (aqara_thp03)
please how can I stop this

@Tjilie Plugin restart usually helps. It is intermittent issue I cannot regularly reproduce to be able to fix

Within Domoticz wen interface I disabled and update the plugin and after that I enabled and update the plugin. This does not changed the logging. Also I update to the mast recent stable version this make also no differents.

Sorry I accidentally closed issue.
So as I wrote before restart plugin does not help.
When I open the Domoticz outside my home network I don't have this Zigbee log and have only the normal log

Could you please also try to restart your MQTT server

I will do so tomorrow. I planned to make a back-up of my SD-card tomorrow morning.

I restarted my RPI (and cloned Sd-card), update CC2531 USB stick to latest version.
This also did not help, logging still the same unfortunately

Now most of the switches don't work any more but are connected to broker an visable in log. Only the

@ stas-demydiuk
The Domoticz log still overflow with zigbee comment. What a also see is that my domoticz database is growing big fast. Is this related to each other?

Looks like issue was on Domoticz side, haven't seen this issue for more than 3 months, so will close this issue. Please reopen ticket if will occur again.


commands:run - recent parameter values

Store the recent parameters that were set during the last calls.

Implemented


Tmux option for separation of SSH and local session autostarts

Proposed Changes

Allow the user to set a variable in .zpreztorc to create different sessions for local and remote connections on auto-start
Allow the user to independently name the auto-started local and remote connections
Update README.md to represent the above functionality

Motivation
Currently, there is only a single global configuration for the session auto-started by the tmux module.  It can be extraordinarily inconvenient to be working on a desktop and laptop, and by logging in through SSH on the laptop have the session detach on the desktop. This is especially true in cases when a command is left running in the foreground of one session intentionally, only to have it pop up in your face on logging in to another. This seems like far more convenient and intuitive behavior.
While I realize there are numerous ways to work around this built into tmux, it is extremely convenient to not have to go through the extra steps. I have confirmed that the behavior when none of my added options are set is identical to before, and I maintained the coding style present in the rest of init.zsh, so I can think of no reason not to add in this functionality.
Usage
If you would like to create separate background sessions by default for SSH connections and local connections, you may do so by adding the following line to ${ZDOTDIR:-$HOME}/.zpreztorc:
zstyle ':prezto:module:tmux:auto-start' separate 'yes'

If separation is enabled and names are not provided, the sessions will be named prezto-local or prezto-remote respectively. If a name is provided for one of the two connection types but not the other, only the unassigned name will be set to the default. The names of these sessions are customizable in a similar manner to above:
zstyle ':prezto:module:tmux:session:local' name '<YOUR DEFAULT LOCAL SESSION NAME>'
zstyle ':prezto:module:tmux:session:remote' name '<YOUR DEFAULT REMOTE SESSION NAME>'

I've modified the tmux module as well to add a few functions that allow you to spawn a new session from an arbitrary directory, naming the session after the starting directory. This pull request would work well with that.


Fix infinite recursion in the record algebra parser

Fixes parsing of
type broken = record {
  test: : string
}

as reported by @satta.

That was fast, thanks :)


bad window button positioning on Yosemite

I've run my app (built on Xcode 6.1) on Yosemite, and I've noticed that the three buttons in the top-left are positioned incorrectly - they sit in the top-left part of the title bar like in standard apps, and they jump to center-left of the bar when the window is moved. Is this a known issue (or something you've fixed on master)?

Same issue here. 👍
One other thing to note: It fixes itself when you move (or resign/make key) the window, yet the buttons' tracking area stays in the wrong location.


fix answer display for questionnaire response that doesn't have answer

per slack chat with Justin related to questionnaire responses sent by Care Plan:
questionnaire id should populate question column
answer code should populate the answer column

@achen2401 actually, did you confirm w/ @ivan-c ? We've had recent changes around this and more in flight...

@mcjustin
Justin, Yes, I did confirm with Ivan before I made the changes.


Define protocol for talking to autograder

We need to decide how we want to talk to the autograder.
Do we want to use the edX autograder protocol? It looks like they send the password in plaintext...?
If we make our own, we should document this in the wiki.

I think @kvchen and @Sumukh are working on an autograder now.

I believe this was finished by @joseph-choi and co.


The code worked before the change of variables into rates and now it isn't working

https://github.com/wikpur/Spacial-Econometrics-Project/blob/f12e530994bb4025f811a1ba6b30d68c48c33c41/Spacial-Econometrics-Project.Rmd#L349
@rsbivand

This line works for me - what was the error message?


Problem when using register_buf_ring on udp echo server, expect error: ENOBUFS,  but the error not occur

I make a udp echo server  using io_uring register_buf_ring refer to register_buf_ring test demo
Problem:
I register 2 bufs, expect error: ENOBUFS when processing the 3rd packet without calling std::mem::drop(buf1). But the error not occur.
The udp echo server is simple, whether my usage is wrong or there is a bug ?
Operating System: Ubuntu 22.04.1 LTS
          Kernel: Linux 6.1.8-060108-generic
    Architecture: x86-64

@FrankReh would you have time to give a look at this problem ？

@glenn-wang
In the future, you may want to provide a simpler example for a volunteer to look at a problem for you. You didn't create a minimal case that works vs not working. You didn't provide code that compiles on its own. You didn't make it easy to see what you had taken from my unit test and what you had changed and added.
But I was curious if I could figure this out. Especially because you said it was working and thought it shouldn't be working and you're using a newish feature of urings, the buf_ring. And it turns out, you're using another new feature, the multishot receive.
I've spent too much time writing up what I found and guessing what you thought should be happening and ended up deleting it all and starting over. So here it is.
You are creating a multi receive operation that will pick a buffer from the ring and always use 3 as the user_data field.
You then have a loop that blocks, waiting for at least one cqe to come in. You do some book keeping for the cqe, I don't know if that's right in all cases, but it works in how I was testing it.
Then you loop through the CQEs.
Your first block seems designed to handle the results of the echo response operation, the write. You recognize it because you use user_data values that are less than 2, so just 0 and 1. And in it you have a comment leading me to believe you think that is the right place to drop a buf_ring buffer. Well it's not. The buf_ring buffer was dropped automatically when it went out of scope at the bottom of the loop. Buf_ring buffers cannot be used for sending data safely unless you expressly keep the buffer from going out of scope until the operation is complete. You don't do that. You use the buffer's storage for parts of the write's msg and get away with it because the storage is not rewritten until the buffer is cycled through again, every 2nd time a UDP packet is received.
If you tested by flooding three UDP packets at a time before the loop could run, you would see the buf ring being exhausted. If the flood test were a little slower, you would notice that the data being sent back to the UDP client wasn't correct.
The second block in the CQE loop handles receiving a user_data 3 cqe, so a result from the multishot receive.
The cqe provides the buffer id that was picked, so 0 or 1. You create the buffer reference from that bid. You then use its parts to build up a msg that you will use to start a write operation at the bottom of the loop. You submit the write. And here  you don't seem to understand the buffer named my_buf goes out of scope. The my_buf type is designed to clean itself up. You, the user are not required to manually drop it.
The fact you use the bid as the user_data for the write should not make sense - there is no reason to. You could always just use a value of 0, or any value that wasn't 3, so you could differentiate the recv results from the write results. The user_data is a way of matching a cqe received with the sqe created at an earlier time.
So I want to say you can't really do what you are trying to do with that loop but it is possible, just with more code. At the bottom of the loop, you need some storage space for the data but make no allowance for keeping that storage alive while the write operation is in flight. So you are breaking the safety contract necessary by the unsafe block at line 281, where you push the write operation onto the submission queue. This is a common problem with the io-uring unsafe push operation. Lots of designers have not taken the unsafe contract to heart when they call it. I've seen it now four times myself and I'm very new to these projects.
You could go to pains to use more permanent storage. You could use a slab and use the slab indexes as the user_data field. The slab entry could be a simple byte array that you had copied the ingress buffer's data into. Or you design the slab to take ownership of the buf_ring buffer so it doesn't get dropped until you take it from the slab later, in the block where you handle the write CQEs. Either way, the slab entry gets released when the write's cqe is processed, so the data it was keeping live would outlive the in-flight write. Of course there are other ways not involving slabs, but the slab is a useful tool and happens to be used by the tokio-uring for just this purpose.

@FrankReh
Thank you very much for your patient reply and suggestions. I will digest and absorb the suggestions.
This project has no demo of udp server.  My purpose is to implement the following demo with Rust lang.
https://github.com/axboe/liburing/blob/master/examples/io_uring-udp.c
Moreover，I really didn't realize that the buf was automatically dropped.

You submit the write. And here you don't seem to understand the buffer named my_buf goes out of scope. The my_buf type  is designed to clean itself up. You, the user are not required to manually drop it.

A couple of things. You seem new to all this. Maybe you don't know Rust that well yet. Then my suggestion is to try and code anything you want, but don't use unsafe. In the code you copied and added to, there are lots of unsafe calls. unsafe should only be used when one knows a lot about the Rust borrow checker rules and have a good idea of memory management. The fact you didn't know how to interpret the code you copied from the unit test indicates that regular Rust is still a struggle.
So just read through Rust you find interesting, and teach yourself what every little bit of it does. When you see an impl that Drops, be curious what that means and ask yourself why the author wrote that. With any Rust code, one should ask what happens to a variable type when it goes out of scope.
When you copy a large part of code like that. It maybe isn't legally required to attribute where it comes from, but it's a nice courtesy.
When you get back to writing Rust code and using unsafe blocks in it. Document each as to how the code you are writing is maintaining the safety contract. Why should a reader believe it is safe, why are you resorting to unsafe and what do you know that the compiler doesn't that makes it actually safe.
The reason the compiler didn't help you know you were sending a buffer that was going out of scope was that you had wrapped the submit call in an unsafe.  Now you might say, well the io-uring author requires it is wrapped in unsafe. That would be correct. But in a language like Rust, then you should ask yourself why? Why did the author require the unsafe tag to that call? If you can't understand their reason, then when things start going wrong, you should first assume you don't understand enough.
The io-uring library, and even the tokio-ouring library, are not meant for people new to Rust. Rust is hard by itself at first. One could learn a lot just using the std library which is essentially all synchronous. Even the io-uring library is still all synchronous but it is providing the bindings for the asynchronous world of the Linux io_uring device and it requires unsafe programming. And asynchronous programming is harder. There is a lot to understand. There are a lot of user manuals to read in the liburing repo's man directory. Understanding what goes in an SQE and what comes back from the CQE, and how buffers are shared between the userland and the kernel takes some time. Actually you got quite far but it was your misunderstanding of buffer memory that tripped you up. The C language has no such complexity. All the heap memory is handled with manual calls like malloc and free. So a buffer could live a long time, outside of the scope where it was allocated - and C programmers make great use of that and also create bugs that are hard to find and great security holes.
Rust wants to protect you from yourself, and help, by freeing memory when it's handle goes out of scope. And it normally would not let you pass a pointer to that memory, or any address within it, to something that can outlive the scope ... unless you do those operations in an unsafe block.
So brush up on drop. See how the buf_ring buffer is added back to the kernel's buf_ring when the drop function is called. And learn to recognize where the compiler would put that drop function call.
And you probably shouldn't create issues with errors making it sound like a fundamental feature is broken and you shouldn't assume you may have uncovered a bug so quickly.
Maybe you could change the title of this issue, for posterity's sake. Something like, "Looking for help understanding buffer lifetimes".
Good luck. Thanks for being interested in Rust, mutlshot accept operations and buffer rings.


Additional functions to control interval/range parameters on the API

Hi!
I needed these two parameters and so I went ahead and added them. I left the original functions intact for legacy reasons and duplicated the tests.
Cheers :)

Thanks! That is certainly an improvement and I was just to lazy to implement it myself, since I didn't need it.


MonadFail support

You will need to merge #185 also, and the two together should give you proper GHC8.8 support.

This seemed to break GHC < 8. https://travis-ci.org/yesodweb/Shelly.hs/jobs/551518946

Looks like the MonadFail instances don't hit transformers until transformers-<IP_ADDRESS>: https://hackage.haskell.org/package/transformers-<IP_ADDRESS>/changelog
GHC 7.10.3 (the last <8 release) has transformers-<IP_ADDRESS>. GHC 7.10.3 was released in 2015; is it still necessary to support?

I don't think it is necessary. But if its easy to support I would

I believe the fix would be to the test suite: putting orphan instances
behind CPP to check MIN_VERSION_transformers.
It doesn't pass my effort:reward tradeoff, but it may pass yours.

no, does't pass mine either.


Cursor isn't scrolled into view on backspace, delete

To reproduce, spam text into the project page demo until you have enough scroll height, scroll your cursor out of view, and hit backspace or delete.
Expected: The cursor is scrolled into view
Observed: Key takes effect but cursor stays scrolled out of view
(Is scrolling the selection into view in case of text input and other keys like enter entirely handled by the browser? I searched for code related to this, but failed to find any.)

+1
Also it isn't scrolled when undo / redo.

+1
And when you paste text using cmd+v you also have this bug.

+1
same problem with @vesai

The bug seems to happen only when the pasted text doesn't contain any new line, it's really annoying when you have to scroll down to see the pasted content.


v2.0.1 (or v2.1.0) planning

https://github.com/containerd/nerdctl/milestone/38?closed=1
The amount of the changes since v2.0.0 are relative small, so probably this can be v2.0.1 rather than v2.1.0.
cc @containerd/nerdctl-committers

Yes please go ahead @AkihiroSuda. When  do you plan to release ?

When do you plan to release ?

Can be today, after:

s/2.1.0/2.0.1/ https://github.com/containerd/nerdctl/blob/3c41efe581fd7291b446709f11c7439594abf347/docs/config.md?plain=1#L48
bumping up the deps

@AkihiroSuda if possible, would like to have #3708 in. Addressing comments rn.

Thanks @AkihiroSuda
Appreciate the inclusion of #3708. This one gave me a serious migraine.

https://github.com/containerd/nerdctl/releases/tag/v2.0.1


Let Dedicated EThreads use EThread::schedule

EThread::schedule_local allows calls from Dedicated EThreads by scheduling events on the ET_CALL pool. This change brings the same behavior to the EThread::schedule function.

[approve ci]

[approve ci docs]


enable appveyor (windows CI testing)

will close #9

Coverage remained the same at 96.252% when pulling 664e1c2dee15c3f114217942df316a478d160b5e on appveyor into e980b0d6679b4a832c235c16b8af48af1536cc61 on master.


Add new exercise: Hangman

problem specification | description |  ~canonical data~

I've added the links. Since there is no canonical data, let yourself be inspired by tracks already implementing it :)

Before working on this, please check out the discussion in #774.


Pasting on macOS with translated line breaks

Copying and pasting text art at the cursor in macOS (Ventura) always drops line break characters. I have experimented at length with using other programs to change the text encoding, and even written to the clipboard with JS, and I can't seem to get the result that I'd see if I open the same files in iCY DRAW and copy & paste within the app.

Am I doing something wrong?
Can this be supported, whether as a default or an elected mode for pasting?
If it simplifies the implementation, pasting directly into a new floating layer would serve well.

Benchmark, in summary: pasting ASCII art copied from the web browser renders as expected.
Copying out of the app on macOS produces an invisible PNG object, which also feels unexpected. Copy as characters, copy as utf-8, copy as PNG (rendered) would all be incredibly useful — but for the most part, getting art into iCY is tricky.
INCREDIBLE WORK in general, though. Thank you!

Can reproduce this exact same issue here on OpenBSD-current and 7.4.


Top-level topics

Create top-level topics for submissions, with UI.

Great.

After discussions with Nathan last week, the demanded feature seems to be for top-level tasks, at least. Since tasks are already hierarchical, we'll update the task index view to show the highest level topics, and users will have the option of clicking to see either the top-level task detail or child tasks, successively. (We'll track progress here in this issue.)
Since task detail views already list child tasks, the actionable content of this issue becomes to restrict the task index view to display only top level tasks. This is trivial. We can also do the same with methods, if we add a method hierarchy.

@nathanshammah @willzeng Do we have particular top level topics in mind, for tasks? Most of the work here seems to be to decide what these top level categories actually are, and to update the database to reflect that decision. (I have a PR up already that restricts the tasks index view to top level categories, but the de facto categories are ad hoc, right now.)

The topics you had drafted were great! Applications, Compilation, Hardware
and Simulators.
Worth keeping in mind in design that we may want to edit, remove, and
extend them later.
On Mon, Feb 14, 2022, 3:54 PM Daniel Strano @.***>
wrote:

@nathanshammah https://github.com/nathanshammah @willzeng
https://github.com/willzeng Do we have particular top level topics in
mind, for tasks? Most of the work here seems to be to decide what these top
level categories actually are, and to update the database to reflect that
decision. (I have a PR up already that restricts the tasks index view to
top level categories, but the de facto categories are ad hoc, right now.)
—
Reply to this email directly, view it on GitHub
https://github.com/unitaryfund/metriq-app/issues/411#issuecomment-1039546579,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHZDATNUJNZ44B2OTGB7WLU3FTW5ANCNFSM5NQH744A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Looks fine to me, thanks!

By the way, next to tasks, I see use also for top-level categories for Methods to help with a tidier taxonomy #363 and sort out questions like the one here #435. For example, top-level methods could be:
"Superconducting-circuit processors">Rigetti80Q,H1, etc.
"Neutral-atom processors">"Cs", etc.
"Trapped-ion processors">"Yb+","Ca+", etc.

I'm collecting notes on the general topic of taxonomy and data model reorganization here, as we've gathered the related issues and seek to address them this week:
@crazy4pi314  raised the point in the submission party today that our data model seems to put the task of visualization first and work backwards to a schema. While this lets us visualize data easily, it puts a lot of load on the user, and it centers the visualization rather than the domain-specific knowledge in our data model. For example, for the t|ket> submission, hardware architecture becomes a permutation of a child task for a parent circuit definition task. We see almost the same thing happen with Quantum Search on Noisy Intermediate-Scale Devices, where hardware is permuted as sub-tasks, which is counterintuitive to domain experts.
While we might actually permute these out as tasks in our back end and database, it makes more sense, in terms of domain logic, to specify a single task, like the t|ket> circuit to compile. Then, as metadata on the result, the user has the option of selecting one hardware architecture per result, for this same task. Users can move up and down the task hierarchy in the task detail view, to see architecture-specific as well as cross-architecture comparisons, but this is much easier and more intuitive if the work of permuting tasks is done on the demand for metadata association with the result. I'll be adding this as well, this week, at least for choices of hardware architecture, and any other result metadata fields that come up.


Fix typo in man3.0/man7/crypto.html

CLA: trivial

Page URL: https://www.openssl.org/docs/man3.0/man7/crypto.html
Section: OPENSSL PROVIDERS
Error: Paragraph says "implemment" instead of  "implement"
original:

As well as the OpenSSL providers third parties can also implemment providers. For information on writing a provider see provider(7).

fixed:

As well as the OpenSSL providers third parties can also implement providers. For information on writing a provider see provider(7).

Checklist

[x] documentation is added or updated

You could also reword the commit message to be a little bit more descriptive: doc: crypto(7) - fix typo

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

We do not allow merge commits. Could you please drop the latest two commits? git reset --hard HEAD~~ and force push.

Sorry for the confusion @t8m. I have dropped the latest commits and pushed the changes.

Merged to master and 3.0 branches. Thank you for the contribution.


Feature/stage channels

Pull Request Etiquette

[ ] I have checked the PRs for upcoming features/bug fixes.
[ ] I have read the contributing guidelines.

Changes

[ ] Internal code
[ ] Library interface (affecting end-user code)
[ ] Documentation
[ ] Other: _____

Closes Issue: NaN
Description
Replace this sentence with general description of what your Pull Request does.

Sorry lmao wrong target

Stage channels are also already worked on. See #1575

@Andre601 i know i wanted to merge them in my fork but accidentally chose the base repo


[ssclj/tools] optimise the size of jar providing ss-config* CLI

At the moment it gets build as uberjar in assumption that it can be ran fully independently.  The size of the resulting jar is ~60MB and it takes a lot of IO disk/network in handling it in CI/Nexus.

@mebster if you are considering this as an impediment - I could start working on this right away.  In fact, we've discussed this issue yesterday with @loomis There are different options on how to resolve it.  For example, the one proposed by @loomis is to not to create the uberjar at all and use boot on the target machine to bring the dependencies and run the ss-config* scripts.

How long do you think it'll take @konstan?

I'll stop building the uberjar and set the classpath of the ss-config* utils to contain /opt/slipstream/ssclj/lib/ext/ (this is where all the ssclj server deps are and all that the utils need.)  Checked with @loomis
I start working on this now.

@mebster Sorry I didn't see your previous comment.   I think that the "boot on config host" based solution may take 4, while the "/opt/slipstream/ssclj/lib/ext/ in classpath" is 1.


Fix for getUserInfo method throwing an error

The participants property on thread object is returning a list of unicodes. If you then pass these unicodes to getUserInfo, they are not being picked up in the if statement on line 905 in the fbidStrip method, so the fbidStrip method was returning a tuple of None objects. The conditional now matches and reformats both str and unicode objects.

I see. Thanks for the PR!


[WIP] enable large tensor in np

Description
(Brief description on what this PR is about)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@TaoLv @PatricZhao large tensor build for MKL builds seems to be failing. See the CI checks.

@szha, do you mean the errors below? As I mentioned in https://github.com/apache/incubator-mxnet/pull/18645#issuecomment-652198544, we need also enable MKL_USE_ILP64 in cmake line when LTS is enabled. More information, see https://software.intel.com/content/www/us/en/develop/documentation/mkl-macos-developer-guide/top/linking-your-application-with-the-intel-math-kernel-library/linking-in-detail/linking-with-interface-libraries/using-the-ilp64-interface-vs-lp64-interface.html. I'm afraid that similar problem may also exist in mshadow code: https://github.com/apache/incubator-mxnet/blob/master/3rdparty/mshadow/mshadow/dot_engine-inl.h#L317.
[2020-07-03T21:00:50.972Z] /work/mxnet/src/operator/contrib/transformer.cc:143:31: error: narrowing conversion of 'm' from 'mxnet::index_t {aka long int}' to 'int' inside { } [-Werror=narrowing]
[2020-07-03T21:00:50.972Z]    MKL_INT p_m[GROUP_SIZE] = {m};
[2020-07-03T21:00:50.972Z]                                ^
[2020-07-03T21:00:50.972Z] /work/mxnet/src/operator/contrib/transformer.cc:144:31: error: narrowing conversion of 'n' from 'mxnet::index_t {aka long int}' to 'int' inside { } [-Werror=narrowing]
[2020-07-03T21:00:50.972Z]    MKL_INT p_n[GROUP_SIZE] = {n};
[2020-07-03T21:00:50.972Z]                                ^
[2020-07-03T21:00:50.972Z] /work/mxnet/src/operator/contrib/transformer.cc:145:31: error: narrowing conversion of 'k' from 'mxnet::index_t {aka long int}' to 'int' inside { } [-Werror=narrowing]
[2020-07-03T21:00:50.972Z]    MKL_INT p_k[GROUP_SIZE] = {k};
[2020-07-03T21:00:50.972Z]                                ^
[2020-07-03T21:00:50.972Z] /work/mxnet/src/operator/contrib/transformer.cc:146:35: error: narrowing conversion of 'lda' from 'mxnet::index_t {aka long int}' to 'int' inside { } [-Werror=narrowing]
[2020-07-03T21:00:50.972Z]    MKL_INT p_lda[GROUP_SIZE] = {lda};
[2020-07-03T21:00:50.972Z]                                    ^
[2020-07-03T21:00:50.972Z] /work/mxnet/src/operator/contrib/transformer.cc:147:35: error: narrowing conversion of 'ldb' from 'mxnet::index_t {aka long int}' to 'int' inside { } [-Werror=narrowing]
[2020-07-03T21:00:50.972Z]    MKL_INT p_ldb[GROUP_SIZE] = {ldb};
[2020-07-03T21:00:50.972Z]                                    ^
[2020-07-03T21:00:50.972Z] /work/mxnet/src/operator/contrib/transformer.cc:148:35: error: narrowing conversion of 'ldc' from 'mxnet::index_t {aka long int}' to 'int' inside { } [-Werror=narrowing]
[2020-07-03T21:00:50.972Z]    MKL_INT p_ldc[GROUP_SIZE] = {ldc};

@TaoLv thanks. I will wait for that PR to be resolved.

@access2rohit - Please help review. Thanks.

@sandeep-krishnamurthy the CI is currently stuck on build issue that @TaoLv pointed out. @access2rohit 's PR on the build fix is needed to address the issue but it seems that there has been no progress in #18645. What's the plan?

As discussed in this issue https://github.com/apache/incubator-mxnet/issues/17331#issuecomment-656725373 as a first step we are focussed on OpenBLAS updates only as it is the primary BLAS engine we ship with PyPi. MKL updates is next.

@szha
Can we move the file: tests/python/unittest/test_np_large_array.py to nightly folder instead? Keeping them in unittest will significantly slowdown the CI and may result in timeouts as we are allocating tensors with over 4.3 Billion elements. Even if CI doesn't timeout right now once all numpy ops are added it will definitely timeout.

@sandeep-krishnamurthy I'm not asking about MKL as feature request. I'm saying that the current build is broken and it needs fix.

Overall functionality seems fine. Can you run all the tests in the file tests/python/unittest/test_np_large_array.py using pytest and paste the output in the comments section so we can be sure that nightly CD pipeline doesn't break.

@access2rohit will do. We still need to fix the CI for enabling large tensor first.

@sandeep-krishnamurthy I'm not asking about MKL as feature request. I'm saying that the current build is broken and it needs fix.

Basically I will disable large tensor build with MKL in CI when enabling Large Tensor by default and that should fix it(Since we are currently focusing on making Large Tensor work with openBLAS). For now you can remove your change to make USE_INT64_TENSOR_SIZE=ON as default from CMakeLists.txt and your PR should pass CI. Sounds good ?

@access2rohit thanks for the review. no codecov isn't enforced yet.


Account update transaction resets thresholds

Description
When updating an existing threshold such as addition a sub-threshold, the tool zeroes out existing thresholds requiring the values be re-entered.
Steps to reproduce

Launch the tool
Go to Create tab
Select Account Update under Transaction Type
Enter an account ID for which you have an account info file in the Account to update field
Click Modify Key and make a change to an existing threshold such as adding a new public key
The existing thresholds will reset across all thresholds in the key structure.

Additional context
No response
Hedera network
mainnet
Version
v0.3.0
Operating system
macOS

This particular behavior was designed in order to push the user to set the threshold if there are changes to the key.
I will change it to just change the threshold of the part that is modified.


documentation - any guide on how to build a new data source (ie DB2) ?

i want to make some dev changes to add new datasource ie URL/API data or DB2 data. Any developer guide on all files needed to change?

@tooptoop4 #934 Maybe ... Can you wait until January next year? ;;;; Or, I can briefly guide you through this comments, but if we change the structure after 3.1, you need to change it again.

@tooptoop4 I'm sorry to long... late reply.
We have begun to support the data connection extension since version 3.2. However, it does not officially support DB2, so if you want to use it, you can implement the extension.
Please, follow this link : https://github.com/metatron-app/metatron-discovery/tree/master/discovery-extensions


expose time format

Also, please provide an explanation of why you need this exposed.

Closed due to inactivity.  Also, I don't think exposing the backup time format is a good idea in general.


Update plugin API endpoints to use dynamoDB

/plugins
Should return only public plugins
e.g. visibility == 'public' and is_blocked == False

https://github.com/chanzuckerberg/napari-hub/issues/949

/plugins/index
Should return only public plugins metadata as a list
e.g. visibility == 'public' and is_blocked == False

https://github.com/chanzuckerberg/napari-hub/issues/950

/plugins/excluded
Should return non-public plugins
e.g. visibility != 'public'

https://github.com/chanzuckerberg/napari-hub/issues/951

/plugins/<plugin>
/plugins/<plugin>/versions/<version>
Should only return plugin data if it has public or hidden visibility and is not blocked.
e.g. visibility IN ('public', 'hidden')  and is_blocked == False

https://github.com/chanzuckerberg/napari-hub/issues/864

/manifest/<plugin>
/manifest/<plugin>/versions/<version>

https://github.com/chanzuckerberg/napari-hub/issues/952

Notes:
If collaborating on this in parallel, creating the pynamo models for plugin, and plugin-excluded should be done first.

Closing this ticket out as it's redundant with the info provided in the epic - https://github.com/chanzuckerberg/napari-hub/issues/845 - and to avoid having to update info in two places.


Failed Tests on Install QEMU (Windows) stage

Tests are consistently failing on the Install QEMU (Windows) stage due to a Can't shim 'qemu-system-moxie.exe': File doesn't exist. error. I found a similarly described issue on the scoop project at https://github.com/ScoopInstaller/Main/issues/2560, though the fix did not seem immediately clear.

Looks like phil-opp beat me to a previous issue https://github.com/lukesampson/scoop/issues/4183

Fix in https://github.com/ScoopInstaller/Main/pull/2553

I think we should directly download the installer from https://qemu.weilnetz.de/w64/2021/
That's all scoop is doing anyway, so it seems weird to download an installer that just essentially downloads another installer.
@phil-opp is there any reason we shouldn't just download qemu directly?

I assume it's for the easy unattended install. But if the preference is to do away with scoop, I can sort out a PR to get that working.

I think I originally used scoop to download multiple dependencies and because it was easier to set up. However, it already took down our CI pipeline a few times, so maybe installing qemu directly would be better. This would also give us the option to fix any issues ourselves instead of waiting for fixes in scoop.

This of course all depends on how much effort the manual install would be. If it requires more than ~2-4 commands, sticking to scoop is probably the better option.

So in #287 I changed the CI to just do choco install qemu, which works and properly installs QEMU.
However, now the tests timeout. I'm guessing it has something to do with the arguments passed to QEMU being different on Windows vs Linux. For now, I've just changed things to allow the Windows tests to fail to unblock things.
@phil-opp does it even make sense to run the QEMU tests on non-Linux platforms? Running the same binary on QEMU on multiple platforms seems unnecessary. At that point it seems like we're testing QEMU, not the x86_64 crate.
My preference would be to only run the QEMU integration tests on Linux. We would still run the cargo build/cargo test/etc... commands on Linux, macOS, and Windows.

So in #287 I changed the CI to just do choco install qemu, which works and properly installs QEMU.

Good solution, thanks! I didn't know that GitHub Action runners now have choco installed by default.

However, now the tests timeout. I'm guessing it has something to do with the arguments passed to QEMU being different on Windows vs Linux. For now, I've just changed things to allow the Windows tests to fail to unblock things.

Hmm, the tests still worked a week ago, so it would be good to get them working again. The only reason that the Windows tests are not marked as required is that the install step failed a few times. The tests themselves normally worked without problems.

does it even make sense to run the QEMU tests on non-Linux platforms? Running the same binary on QEMU on multiple platforms seems unnecessary. At that point it seems like we're testing QEMU, not the x86_64 crate.

I think it makes sense to run it in QEMU on all major platforms because our code should not cause problems on any platform (people are using this crate in QEMU on Windows). Another advantage of the current approach is that we test our code against the common QEMU versions for each OS, which can be very different. For example, the latest CI job of #287 (which timed out on Windows) uses QEMU 4.2.1 on Linux, v6.0.0 on macOS, and v6.0.93 on Windows. So the version used on Windows is the newest, so I think it's more likely that the issue is caused by some breaking change in QEMU and not by platform differences.

So the version used on Windows is the newest, so I think it's more likely that the issue is caused by some breaking change in QEMU and not by platform differences.

Given that the Windows seems to be a release candidate version, so it might be a regression (instead fo a breaking change). Maybe it works if we force the version to v6.0.0. I just opened https://github.com/rust-osdev/x86_64/pull/297 to try that.

Seems like using version 6.0.0 on Windows fixes the timeout problems: https://github.com/rust-osdev/x86_64/runs/3358253309?check_suite_focus=true (https://github.com/rust-osdev/x86_64/pull/297)

@phil-opp awesome to hear!! Thanks for looking into this.

With #297 merged this is fixed.


an issued occurred when I'm going to train the coco dataset

I have followed the instruction provided by the author, but an issue occurred. Then I tried on three different computer with a whole new OS, the same issue still occurred.
ImportError: /home/buu/anaconda3/envs/querydet/lib/python3.6/site-packages/detectron2/_C.cpython-36m-x86_64-linux-gnu.so: undefined symbol: _ZN6caffe28TypeMeta21_typeMetaDataInstanceIdEEPKNS_6detail12TypeMetaDataEv

It looks like you're encountering an ImportError related to a missing symbol in a Python package called detectron2. This error typically occurs when there's a compatibility issue or a missing dependency.
Here are a few steps you can try to troubleshoot:
Update Detectron2: Make sure you're using the latest version of detectron2. Sometimes, newer versions fix compatibility issues.
Check Dependencies: Ensure that all dependencies required by detectron2 are installed and up-to-date. You may need to reinstall or update the package that contains the missing symbol.
Check Environment: Verify that your Python environment is set up correctly and doesn't have conflicting packages or versions.
Reinstall Caffe: Since the error mentions a symbol related to Caffe, try reinstalling Caffe or ensuring that it's properly linked with detectron2.
Community Forums: If the issue persists, consider searching online forums or GitHub repositories related to detectron2 for similar issues or solutions. You may find helpful tips from other users who have encountered the same problem.
If none of these steps resolve the issue, you may need to provide more information about your environment and the steps you took before encountering the error for further assistance.
these's chatgpt ans,hope it useful.


fix(build): update return codes for build scripts (#2583)

fix(build): update return codes for build scripts

fix(build): update return codes for build scripts

fix(build): update return codes for build scripts

revert test file

(cherry picked from commit 96e8d8ec38fcb9f8b3b678bcbba91de402f32c36)

Merging in as builds are now (properly) failing. @vermas2012 to provide fix for current test failure in new PR


Number and date datatype issues

Hi, I use the formatting for number and date fields and it works fine. Also, when I select the cell it shows correct data type. But there are issues - number field does not have all characteristics of it. It is not right aligned and does not honor custom settings. For example, the decimal should be comma when the excel is opened in the computers from certain countries. It does not happen.
Is it possible to apply these custom settings though sheetJS?
I use aoa_to_sheet utility and here is my code that performs formatting (kotlin).
private fun applyFormattingToWorkSheet(rowCount: Int, workSheet: dynamic, xlsx: dynamic) {
data class CellObject(val r: Int, val c: Int)
data class RangeObject(val start: CellObject, val end: CellObject)

val numberFormat = "0.00"
val numberRange = RangeObject(CellObject(1, 3), CellObject(rowCount, 4))
for (row in numberRange.start.r..numberRange.end.r) {
    for (column in numberRange.start.c..numberRange.end.c) {
        val cell = workSheet[xlsx.utils.encode_cell(CellObject(row, column))]
        cell.z = numberFormat
    }
}

val dateFormat = "DD-MM-YY"
val dateRange = RangeObject(CellObject(1, 1), CellObject(rowCount, 2))
for (row in dateRange.start.r..dateRange.end.r) {
    for (column in dateRange.start.c..dateRange.end.c) {
        val cell = workSheet[xlsx.utils.encode_cell(CellObject(row, column))]
        cell.z = dateFormat
    }
}

}

The thousands separator and decimal point are computer regional settings.  There is nothing we can write in an XLSX or XLS or XLSB file that will force Excel to use en-US or de-DE or zh-CN or any other locale.
Setting the z field tells Excel what format we wish to apply.  As of the writing of this comment, that is all we can do.  If Microsoft adds special record metadata to Excel for overriding the locale, then it can be implemented here.


Logo files added

The logo gets a white strip on the top (it looks partially stripped away) after scrolling up and down. Please check.

Logo top ripped off.docx

Thanks, Chiefsan! Advance birthday wishes!!
Regards,
Balaji R
On Sat, 31 Oct 2020, 20:13 Sanjay Seetharaman<EMAIL_ADDRESS>wrote:

Merged #2
https://github.com/ISO-Audit-Guru/ISO-Audit-Guru.github.io/pull/2 into
master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ISO-Audit-Guru/ISO-Audit-Guru.github.io/pull/2#event-3944183574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APZ252WMAKOMARF55QJSKNDSNQO7TANCNFSM4RVQYS5Q
.

oBRigado _/_


Move "Reusing OMERO sessions" from public to web dev

"Reusing OMERO sessions" isn't suitable for public sharing since it provides a full read-write session with access to all data. Including it in the public user doc implies it's somewhat equivalent.
Background: https://forum.image.sc/t/omero-public-datasets-with-permanent-session-id/44939

MSTM

Looks good.
Thanks


Monitor container exit code and output logs

When a container fails store its exit code and output the container logs.

Fixed https://github.com/ContainerSolutions/mini-mesos/pull/54


Meta function overload support

The current implementation doesn't work when argument cast is required. I look into it tomorrow or the day after or on the third day.

I've split new changes into several commits to make them easier to spot. When you're ready - tell me which commits to squash into the "main" commit ([meta] Meta-function overload support).

I thought about this change. Imho, meta_func isn't the right place for it.

I think you're right here. If the meta_func represents the "function pointer" concept then iterating the overloads is out of its scope.

My opinion is that we have now these functions in for the meta type: ...

Isn't the second function exactly the same as the current meta_type.func()? Something like this could be more useful:
template< class... TArg >
[[nodiscard]] meta_func func (id_type const id) const;

This function would return an overload accepting the given argument types, one way or the other. A version of this function working with meta_type objects could also exist. It's useless when you know all the types but in generic code working with reflection, it would be quite useful. I'd keep both functions, even though the former can be implemented in the terms of the latter.

On the other side, we could rework the second function as... Then, we can resolve the overload during name/params resolution.

Yes, this version will be more logical. Same goes for data and set/get pair.
Could we go further and replicate the meta-data and meta-function access functions in meta_any, especially for those meta-functions that require an instance? This could further ease using meta. With what we have now it requires too many hoops to get what you want. I know that it's not that much - just another variable or something like any.type().func("id"_hs).invoke(any, ...), but being able to just any.invoke("id"_hs, ...) looks a bit nicer to me. It's shouldn't be the only way to have purely "static" meta-functions.

As for this PR, we could

either defer this feature, rework the way meta-members are accessed and then implement it as part of the update to meta - this should be pretty straight forward, like moving the code to another function almost without changes
or introduce it "as is" to get more experience with it and then rework the way meta-members are accessed.

Oh, well, next week I'll take a break during which I will struggle to keep up with my work, then I'll come back stronger than before to fix things as said and proceed with this issue. I'd avoid doing the job twice though. The other changes should be easy at a first glance.

I'll squash commits then and lay the PR on ice until you're ready to use it.


[youtube] Fix age gate detection

Merging random-nick's patch into my repository

See https://github.com/ytdl-org/youtube-dl/pull/26100


Tags get multiplied on delivery (some kind of looping)

Tag a post you got from a forum whose author you also have as a connection (this will happen if they sent it privately to the forum).
Post gets tagged multiple multiple multiple times.
There might be some kind of multiple route check that we're skipping for tags but we have for comments.

@solstag This issue is closed because Redmatrix evolved into Hubzilla. When this is still an issue in the most recent version of Hubzilla, please recreate this issue over there. We're sorry for any inconvenience this will maybe give you.


Adds remove_non_framed_screenshots action

This action is a dirty fix to get deliver working, https://github.com/fastlane/deliver/issues/403
It looks for *.png images in the default screenshot folder and removes the png-images that don't have framed in the filename or are named background.png. The screenshots path and background.png can both be set using optional arguments.

Thanks for the pull request, but I think we should fix the underlying issue instead, let's move further discussion to https://github.com/fastlane/deliver/issues/403 where I prepared a fix :+1:
Sorry for the delay from my side


net: benchmarks leak goroutines

$ go test -benchtime=10ms -run=NONE -bench=. net
PASS
BenchmarkGoLookupIP                    	       1	  40965233 ns/op
BenchmarkGoLookupIPNoSuchHost          	       1	  19965162 ns/op
BenchmarkGoLookupIPWithBrokenNameServer	       1<PHONE_NUMBER> ns/op
BenchmarkDNSName                       	   20000	       527 ns/op
BenchmarkInterfaces                    	     500	     22694 ns/op
BenchmarkInterfaceByIndex              	    2000	      8077 ns/op
BenchmarkInterfaceByName               	    1000	     23937 ns/op
BenchmarkInterfaceAddrs                	     500	     25500 ns/op
BenchmarkInterfacesAndAddrs            	    2000	      9571 ns/op
BenchmarkInterfacesAndMulticastAddrs   	    1000	     16570 ns/op
BenchmarkParseIP                       	    5000	      2782 ns/op
BenchmarkIPString                      	   10000	      1979 ns/op
BenchmarkIPMaskString                  	   30000	       518 ns/op
BenchmarkTCP4OneShot                   	     100	    124088 ns/op
BenchmarkTCP4OneShotTimeout            	     100	    161610 ns/op
BenchmarkTCP4Persistent                	     500	     22614 ns/op
BenchmarkTCP4PersistentTimeout         	     500	     22398 ns/op
BenchmarkTCP6OneShot                   	     100	    191345 ns/op
BenchmarkTCP6OneShotTimeout            	     100	    185625 ns/op
BenchmarkTCP6Persistent                	     500	     23476 ns/op
BenchmarkTCP6PersistentTimeout         	     500	     23658 ns/op
BenchmarkTCP4ConcurrentReadWrite       	    1000	     16150 ns/op
BenchmarkTCP6ConcurrentReadWrite       	    1000	     19477 ns/op
Leaked goroutines:
time.Sleep(0x12a05f200)
	/Users/jbleechersnyder/src/go/src/runtime/time.go:59 +0xfc
net.loadConfig.func1(0x12a05f200, 0x0, 0x32cb50, 0x10, 0xc20800e2e0)
	/Users/jbleechersnyder/src/go/src/net/dnsclient_unix.go:241 +0x36
created by net.loadConfig
	/Users/jbleechersnyder/src/go/src/net/dnsclient_unix.go:267 +0x17d

ok  	net	5.498s

Possibly will be fixed by CL 9991. /cc @axaxs

FWIW, I changed the banner "Leaked goroutines:" to "Running goroutines:" in 3b38626f7d5c9b85e3acb2601e34324879438fae. Because we need some persistent goroutines when we run IO completion cancellation mech. unsupported Windows kernels, as @alexbrainman suggested in the review.

Can we remove it entirely, then? If it isn't informing the user that something is wrong, then it is just noise.

Or be careful about which ones you complain about, like net/http's tests.

Yup, it's stole from net/http, behaving like net/http makes sense. I'll tweak it once change 9991 lands.


fix: Always run build tasks in the plugin directory

Before this, only shell commands were run in the plugin directory.
This ensures a coherent behavior by always changing to the plugin directory for build tasks.

I don't see why this is necessary. Might also be unexpected

Well, at least sg.nvim expected that to be the actual behavior. I don't really understand the point of the automatic build discovery feature with the current behavior, but that's your project so fine.

Build.lua will be deprecated soon in favor of packspec.


Failed to build chamfer-3D

Hello @louis-wiesmann
when I install the 3rdparty dependencies, I meet the problem:
ERROR [12/13] RUN cd depoco/submodules/ChamferDistancePytorch/chamfer3D/ && pip3 install -U . 2>/dev/null
I guess what matters is the setup process for chamfer-3D,the details are:
Building wheels for collected packages: chamfer-3D
#0 1.824   Building wheel for chamfer-3D (setup.py): started
#0 2.682   Building wheel for chamfer-3D (setup.py): finished with status 'error'
#0 2.682   Running setup.py clean for chamfer-3D
#0 3.509 Failed to build chamfer-3D
#0 4.069 Installing collected packages: chamfer-3D
#0 4.069     Running setup.py install for chamfer-3D: started
#0 4.940     Running setup.py install for chamfer-3D: finished with status 'error'
is there any way to solve the problem?
thanks in advance

Hello @YYYY1213800,
unfortunately

thanks a lot .I think I have solved the problem. Some versions are in conflict.

Okay thank you. If you tell me which ones I can have a look and update the repo probably.

I have the same question, could you please tell me how to resolve this?

@louis-wiesmann  I think this problem is caused by a mismatch between the computational power requirements of my computer with the torch version,So I added computational power constraints to bashrc and it works。@aprilbian maybe you can solve the problem in this way

@louis-wiesmann By the way,I have noticed that there is a performance test for the Nuscene dataset in the paper, and I want to reproduce this result. Could you please provide me with code on Nuscene data processing? I downloaded the Nuscene mini dataset, but it's structure is quite different from the semantic kitti.
It doesn't matter if it's inconvenient to provide。
Thanks a lot

@louis-wiesmann I think this problem is caused by a mismatch between the computational power requirements of my computer with the torch version,So I added computational power constraints to bashrc and it works。@aprilbian maybe you can solve the problem in this way

What should be done specifically？


Gaussian square parametric pulse documentation

What is the current behavior?
The formula above does not seem to implement a Gaussian square pulse
Steps to reproduce the problem
After logging into the IBM Q experience account and selecting the 'ibmq_rome' backend, run (fixing indents):
backend_defaults = backend.defaults()
inst_map = backend_defaults.instruction_schedule_map
cx_default = inst_map.get('cx', qubits=(0,1))
CR_max_amp = np.max(cx_default.instructions[5][1].pulse.get_waveform().samples)
cx_duration = cx_default.instructions[5][1].pulse.duration
cx_risefall = int((cx_default.instructions[5][1].pulse.duration - cx_default.instructions[5][1].pulse.width)/2)
cx_sigma = cx_default.instructions[5][1].pulse.sigma
CR = []
for t in range(cx_duration):
    if t < cx_risefall:
        CR.append( CR_max_amp*np.exp(-0.5*((t-cx_risefall/2)**2)/(cx_sigma**2)) )
    elif t >= cx_risefall and t < cx_duration - cx_risefall:
        CR.append(CR_max_amp)
    elif t >= cx_duration - cx_risefall and t < cx_duration:
       CR.append( CR_max_amp*np.exp(-0.5*((t-(pulse_duration-cx_risefall)/2)**2)/cx_sigma**2) )
plt.plot(CR, label = 'from formula')
plt.plot(cx_default.instructions[5][1].pulse.get_waveform().samples, label = 'from backend')
plt.legend()
plt.show()

What is the expected behavior?
Bugs in the code above aside, the two curves in the plot above should be identical. But they are not. Is the formula different?
Suggested solutions
Report the correct formula for the Gaussian square pulse, the way it's created in the backend

Update for Santa:elf:- QGoGP
✅ Issue reproducible and has interesting results on different backends! Since ibmq_rome is retired, the next closest cousins I could find were ibmq_manilla
Updated fixed code with imports -
import matplotlib.pyplot as plt
from qiskit import QuantumCircuit, transpile, Aer, IBMQ
from qiskit import pulse
# Loading your IBM Quantum account(s)
provider = IBMQ.load_account()

backend = provider.get_backend('ibmq_manila')
backend_defaults = backend.defaults()
inst_map = backend_defaults.instruction_schedule_map
cx_default = inst_map.get('cx', qubits=(0,1))
CR_max_amp = np.max(cx_default.instructions[5][1].pulse.get_waveform().samples)
cx_duration = cx_default.instructions[5][1].pulse.duration
cx_risefall = int((cx_default.instructions[5][1].pulse.duration - cx_default.instructions[5][1].pulse.width)/2)
cx_sigma = cx_default.instructions[5][1].pulse.sigma
CR = []
for t in range(cx_duration):
    if t < cx_risefall:
        CR.append( CR_max_amp*np.exp(-0.5*((t-cx_risefall/2)**2)/(cx_sigma**2)) )
    elif t >= cx_risefall and t < cx_duration - cx_risefall:
        CR.append(CR_max_amp)
    elif t >= cx_duration - cx_risefall and t < cx_duration:
       CR.append( CR_max_amp*np.exp(-0.5*((t-(cx_duration-cx_risefall)/2)**2)/cx_sigma**2) )

plt.plot(CR, label = 'from formula')
plt.plot(cx_default.instructions[5][1].pulse.get_waveform().samples, label = 'from backend')
plt.legend()
plt.show()

Plot achieved on ibmq_manila -

Will update comment/add more comments if cause is found/fixed!

Python version 3.9.7
qiskit-terra version: 0.19.1

I am able to recreate the waveform with
import numpy as np
import matplotlib.pyplot as plt
from qiskit import QuantumCircuit, transpile, Aer, IBMQ
from qiskit import pulse
# Loading your IBM Quantum account(s)
provider = IBMQ.load_account()

backend = provider.get_backend('ibmq_manila')
backend_defaults = backend.defaults()
inst_map = backend_defaults.instruction_schedule_map

cx_default = inst_map.get('cx', qubits=(0,1))
CR_max_amp = cx_default.instructions[5][1].pulse.amp
cx_duration = cx_default.instructions[5][1].pulse.duration
cx_risefall = int((cx_default.instructions[5][1].pulse.duration - cx_default.instructions[5][1].pulse.width)/2)
cx_sigma = cx_default.instructions[5][1].pulse.sigma

def old_formula(max_amp, duration, risefall, sigma):
    CR = []
    for t in range(cx_duration):
        if t < cx_risefall:
            CR.append( CR_max_amp*np.exp(-0.5*((t-cx_risefall/2)**2)/(cx_sigma**2)) )
        elif t >= cx_risefall and t < cx_duration - cx_risefall:
            CR.append(CR_max_amp)
        elif t >= cx_duration - cx_risefall and t < cx_duration:
           CR.append( CR_max_amp*np.exp(-0.5*((t-(cx_duration-cx_risefall)/2)**2)/cx_sigma**2) )
    return CR

def gaussian_square_function(times, max_amp, duration, risefall, sigma):
    CR = []
    for t in times:
        if t < cx_risefall:
            CR.append( CR_max_amp*np.exp(-0.5*((t-cx_risefall)**2)/(cx_sigma**2)) )
        elif t >= cx_risefall and t < cx_duration - cx_risefall:
            CR.append(CR_max_amp)
        elif t >= cx_duration - cx_risefall and t < cx_duration:
           CR.append( CR_max_amp*np.exp(-0.5*((t-(cx_duration-cx_risefall))**2)/cx_sigma**2) )
    return np.asarray(CR)

def gaussian_square(max_amp, duration, risefall, sigma, lifted=True):
    times = np.arange(0, cx_duration)
    CR = gaussian_square_function(times, max_amp, duration, risefall, sigma)
    if lifted:
        lift_val = gaussian_square_function([-1.0], max_amp, duration, risefall, sigma)
        CR = (CR - lift_val) / (1-lift_val)
    return CR

plt.plot(old_formula(CR_max_amp, cx_duration, cx_risefall, cx_sigma), label = 'from formula')
plt.plot(gaussian_square(CR_max_amp, cx_duration, cx_risefall, cx_sigma), label = 'from new formula')
plt.plot(cx_default.instructions[5][1].pulse.get_waveform().samples, label = 'from backend')
plt.legend()
plt.show()

There are two problems with the current documentation.

There is a bug in risefall/2 -> risefall, (risefall+width)/2 -> (risefall+width).
The GaussianSquare is really a lifted gaussian square function which removes initial pulse discontinuities and so should be updated as. LiftedGaussianSquare(t) = (GaussianSquare(t)-GaussianSquare(1.0))/(1-GaussianSquare(-1.0)) where GaussianSquare is the corrected definition above. Perhaps this should have been named LiftedGaussianSquare to begin with, but it is a backwards compatibility issue now.

Please let me know if you wish to make the documentation updates @mrvee-qC, otherwise, I can take this on.

Please go ahead with the updates @taalexander! :)

On inspecting the latest docs, problem 1. has already been corrected.

I will add a note about the pulse being lifted.


Consensus getting stuck after block 135,000

Bug Report
I checked my 1.3.0 node a day or so after the hardfork and noticed it was stuck at block 135,088 (block height was ~135,300 at the time). Following the SiaStats-posted workaround helps it along, but it doesn't seem to fix it entirely, as it keeps getting stuck.
We're getting more reports of this on reddit:

https://www.reddit.com/r/siacoin/comments/7ijo5u/are_not_all_wallet_addresses_working_anymore/dqzw68p/?st=jazmghjz&sh=84dffc11
https://www.reddit.com/r/siacoin/comments/7immb8/36_hours_later_i_still_havent_received_any_payout/?st=jazmgwxw&sh=72e5e35a
https://www.reddit.com/r/siacoin/comments/7in5xy/not_getting_payouts_or_transactions_check_your/?st=jazmhuq4&sh=dc8df77d
https://www.reddit.com/r/siacoin/comments/7ind0m/sia_ui_isnt_fully_synchrozing/?st=jazmhq9l&sh=5268dafc
Megathread: https://www.reddit.com/r/siacoin/comments/7iocnu/troubleshooting_thread_20171209_wallet_not/?st=jazo13sk&sh=6c41994a

I also had a node running from a recent master build (47514b4). That seems to be running fine.
So 1.3.1 appears to work, but will 1.3.1 have the same issue on the next hardfork?

The same here. Even after deleting consensus.db and adding nodes it doesn't start syncing.
Also I have warning in gateway.log
WARN: could not automatically forward port 9981: no UPnP-enabled devices found: no UPnP-enabled gateway found

For any users who find this issue looking for a fix, try following the steps in this blog post: https://blog.sia.tech/troubleshooting-the-recent-hardfork-ca77e0b17f0f

To answer the question, v1.3.1 will not have the same connection issues after the hardfork. The connection issues are separate, and were not a problem for 130 before the hardfork because the 122 nodes were keeping everyone connected. But now, 122 nodes are obsolete, which removed the safety net that was protecting 130 nodes. 131 fixes the issues, and will be released soon

With 1.3.1 now released I'm closing this issue.


Licence

Hello! Please, add license to let to reuse you code. You can read more about why license is important here, for example.  Thanks a lot!

Done. Thanks for the heads up.


Build failed on wasm32 when enabling mp3 feature

Bevy version
0.9.1
[Optional] Relevant system information
AdapterInfo { name: "Apple M1", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
stable-aarch64-apple-darwin (default)
rustc 1.67.0 (fc594f156 2023-01-24)
What you did

enable mp3 feature
cargo run --target wasm32-unknown-unknown

What went wrong
error[E0425]: cannot find function `allocation_granularity` in this scope
 --> /Users/lewis/.cargo/registry/src/github.com-1ecc6299db9ec823/slice-deque-0.3.0/src/mirrored/buffer.rs:7:14
  |
7 |     let ag = allocation_granularity();
  |              ^^^^^^^^^^^^^^^^^^^^^^ not found in this scope

error[E0425]: cannot find function `allocation_granularity` in this scope
   --> /Users/lewis/.cargo/registry/src/github.com-1ecc6299db9ec823/slice-deque-0.3.0/src/mirrored/buffer.rs:112:15
    |
112 |             * allocation_granularity();
    |               ^^^^^^^^^^^^^^^^^^^^^^ not found in this scope

error[E0425]: cannot find function `allocation_granularity` in this scope
   --> /Users/lewis/.cargo/registry/src/github.com-1ecc6299db9ec823/slice-deque-0.3.0/src/mirrored/buffer.rs:135:41
    |
135 |         assert!(mem::align_of::<T>() <= allocation_granularity());
    |                                         ^^^^^^^^^^^^^^^^^^^^^^ not found in this scope

error[E0425]: cannot find function `allocation_granularity` in this scope
   --> /Users/lewis/.cargo/registry/src/github.com-1ecc6299db9ec823/slice-deque-0.3.0/src/mirrored/buffer.rs:148:36
    |
148 |         debug_assert!(alloc_size % allocation_granularity() == 0);
    |                                    ^^^^^^^^^^^^^^^^^^^^^^ not found in this scope

error[E0425]: cannot find function `allocate_mirrored` in this scope
   --> /Users/lewis/.cargo/registry/src/github.com-1ecc6299db9ec823/slice-deque-0.3.0/src/mirrored/buffer.rs:151:19
    |
151 |         let ptr = allocate_mirrored(alloc_size)?;
    |                   ^^^^^^^^^^^^^^^^^ not found in this scope

error[E0425]: cannot find function `deallocate_mirrored` in this scope
   --> /Users/lewis/.cargo/registry/src/github.com-1ecc6299db9ec823/slice-deque-0.3.0/src/mirrored/buffer.rs:172:18
    |
172 |         unsafe { deallocate_mirrored(first_half_ptr, buffer_size_in_bytes) };
    |                  ^^^^^^^^^^^^^^^^^^^ not found in this scope

For more information about this error, try `rustc --explain E0425`.
error: could not compile `slice-deque` due to 6 previous errors
warning: build failed, waiting for other jobs to finish...
The following warnings were emitted during compilation:

warning: In file included from minimp3.c:1:
warning: minimp3/minimp3.h:46:10: fatal error: 'stdlib.h' file not found
warning: #include <stdlib.h>
warning:          ^~~~~~~~~~
warning: 1 error generated.

error: failed to run custom build command for `minimp3-sys v0.3.2`

Caused by:
  process didn't exit successfully: `/Users/lewis/Github/jump-jump/target/debug/build/minimp3-sys-34aad8d2d1c9d1ee/build-script-build` (exit status: 1)
  --- stdout
  TARGET = Some("wasm32-unknown-unknown")
  OPT_LEVEL = Some("0")
  HOST = Some("aarch64-apple-darwin")
  cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
  CC_wasm32-unknown-unknown = None
  cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
  CC_wasm32_unknown_unknown = None
  cargo:rerun-if-env-changed=TARGET_CC
  TARGET_CC = None
  cargo:rerun-if-env-changed=CC
  CC = None
  cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
  CFLAGS_wasm32-unknown-unknown = None
  cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
  CFLAGS_wasm32_unknown_unknown = None
  cargo:rerun-if-env-changed=TARGET_CFLAGS
  TARGET_CFLAGS = None
  cargo:rerun-if-env-changed=CFLAGS
  CFLAGS = None
  cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("true")
  running: "clang" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "--target=wasm32-unknown-unknown" "-I" "minimp3/" "-Wall" "-Wextra" "-DMINIMP3_IMPLEMENTATION" "-o" "/Users/lewis/Github/jump-jump/target/wasm32-unknown-unknown/debug/build/minimp3-sys-5bf8631b6090c524/out/minimp3.o" "-c" "minimp3.c"
  cargo:warning=In file included from minimp3.c:1:
  cargo:warning=minimp3/minimp3.h:46:10: fatal error: 'stdlib.h' file not found
  cargo:warning=#include <stdlib.h>
  cargo:warning=         ^~~~~~~~~~
  cargo:warning=1 error generated.
  exit status: 1

  --- stderr

  error occurred: Command "clang" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "--target=wasm32-unknown-unknown" "-I" "minimp3/" "-Wall" "-Wextra" "-DMINIMP3_IMPLEMENTATION" "-o" "/Users/lewis/Github/jump-jump/target/wasm32-unknown-unknown/debug/build/minimp3-sys-5bf8631b6090c524/out/minimp3.o" "-c" "minimp3.c" with args "clang" did not execute successfully (status code exit status: 1).

Additional information
cargo run don't have any problem.
project: https://github.com/NightsWatchGames/jump-jump (I tried on my other project, still build failed on wasm32)

This is a known limitation, although I don't immediately see it documented anywhere.
In Bevy 0.10 I think it should be possible to use the symphonia-mp3 feature instead, but for now if you're targeting the web I'd suggest using ogg/vorbis.

Ok, Thanks. I see symphonia-mp3 feature already in docs/cargo_features.md.

I think resolved, but not tried. Closing now as I can reopen later if needed.


useLabel's labelProps fails type-check when used with a div

Provide a general summary of the issue here
It seems useLabel().labelProps is typed in a way that only works on "label-like" elements.
While type-check works for span, it fails for a div.
🤔 Expected Behavior?
This should pass type-check:
const { labelProps, fieldProps } = useLabel({ labelElementType: 'div' });

return (

I'm a label

);

😯 Current Behavior
It fails with the following (quite verbose) type-check error:
Type '{ children: string; id?: string | undefined; role?: AriaRole | undefined; tabIndex?: number | undefined; style?: CSSProperties | undefined; className?: string | undefined; ... 219 more ...; onTransitionStartCapture?: TransitionEventHandler<...> | undefined; } | { ...; }' is not assignable to type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'.
  Type '{ children: string; form?: string | undefined; htmlFor?: string | undefined; defaultChecked?: boolean | undefined; defaultValue?: string | number | readonly string[] | undefined; suppressContentEditableWarning?: boolean | undefined; ... 271 more ...; onTransitionStartCapture?: TransitionEventHandler<...> | undefined...' is not assignable to type 'DetailedHTMLProps<HTMLAttributes<HTMLDivElement>, HTMLDivElement>'.
    Type '{ children: string; form?: string | undefined; htmlFor?: string | undefined; defaultChecked?: boolean | undefined; defaultValue?: string | number | readonly string[] | undefined; suppressContentEditableWarning?: boolean | undefined; ... 271 more ...; onTransitionStartCapture?: TransitionEventHandler<...> | undefined...' is not assignable to type 'HTMLAttributes<HTMLDivElement>'.
      Types of property 'onToggle' are incompatible.
        Type 'ToggleEventHandler<HTMLLabelElement> | undefined' is not assignable to type 'ToggleEventHandler<HTMLDivElement> | undefined'.
          Type 'ToggleEventHandler<HTMLLabelElement>' is not assignable to type 'ToggleEventHandler<HTMLDivElement>'.
            Property 'align' is missing in type 'HTMLLabelElement' but required in type 'HTMLDivElement'.

💁 Possible Solution
labelProps are currently typed as:
export interface LabelAria {
  labelProps: DOMAttributes | LabelHTMLAttributes<HTMLLabelElement>,
  // ...

While only { id: string, htmlFor?: string } is returned.

One approach can be to narrow down the type, to just what we know we return, but I can see how that can be undesirable, as it can make changing the API surface in the future harder.

Another approach can be to make the returned type depend on the optional labelElementType key:
https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAJQKYEMDGMA0cDecAyKARkgDYASAKgLL4CCMMUwRArjEgM5wC+cAZlAgg4AciioMogNwAoUJFi44AEQDy1BkxbsuvAUJGiAAhPQwAtDACeYLgHpOACxQSAJjNlebdgsTJ0zCgACkJgnAA8lHBIAB4cAHZu3ADWSNYQ-HBUtACipEggSAkwlCgA5gByKEXUKGAAfHAAvLJw7XDRcYnJYqT+pKJwAPy4bR0T-SSk+YXFpbZIwwBcnXITfKs44xPtU2SzRSWUi6uUmDu8cvIlSFD86Eh+04HAKFEx8cW9aRlZOfhDvMylUakg6o0xpMBqEIOFVupNIxmGwONwAD7PMgArQo3SRAFA44Vaq1eoAbUoAF0GnIeF5+KwEhhgBAEnBWJwkIRph9ut9UulMtkaICCkdSiSwRCWn0BqIGgAKMBhTirHkBIKw8JRBoASnVA1e70otK8aDZnHgeH2pG13D4zQ5XI1pEVOB4erkFoSVuUtvtq1trvt+idnO5A3dcFtRIWdlWoltQ093st1pjMNVq04YBQCRDqrDzsj02jsfFwNOYlz+ZTXtkPr9NqzcLVcDcwAAboW28WI67ywM4ycE2JO1369cm-B6AAhXL4WURW24AB0G4Dqr4OA3a+DrfCPAaKEz0zPZAi9ltZpnqgAkgA1WWKy4RCcNS4Td-d9cbie9keDTOBArCkG4cAkHAEApFeH5fh0P5drum6Hpwx4gWBEEPMApBwd2n7fvY8ENneADKwR0JUy61uyKFrrRgHoSecC0ReeGOHmCS0kAA
(Notice the change from ElementType to keyof HTMLElementTagNameMap, so we can correctly index it with T)
🖥 Steps to Reproduce
https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAJQKYEMDG8BmUIjgcilQ3wG4AoUSWOAbzgFcBnJAGRQCMkAbOAXzjZcBIuhgBaFFGAoy5cmggA7JvHrdOPAAo4wTAFxwAJsABu7Ltx0Q9-OAF5GLCzwAU6zdwCi3JCCRKMAAqAJ5gSIb4Jqb4-ACUFIoqanAaltZ6hkxgKEouVrpMdo7MbJ7uqZ4+fgHBYREE2bmxfAnySapwTUoOcAA83XQAdCPd+RlMfAB8KF05PWk8fQD03VOJyp3RvX3btCND0eOF07Pbi9wr0etAA
function SomeComponent() {
  const { fieldProps: divFieldProps, labelProps: divLabelProps } = useLabel({
    label: 'This is a div label',
    labelElementType: 'div',
  });
  const { fieldProps: spanFieldProps, labelProps: spanLabelProps } = useLabel({
    label: 'This is a span label',
    labelElementType: 'span',
  });

  return (

        This is a span label

This is what's being labelled

This is a div label

This is what's being labelled

  );
}

Version
Latest react-aria.

I think you're right that useLabel should work with a div. Did some digging and it seems that in the docs, when you look up the props for LabelAriaProps that labelElementType accepts either a 'label' or 'span'. That said, later in the docs it says "However, if you are labeling a non-native form element, be sure to use an element other than a  and set the labelElementType prop appropriately" which makes it seem more open-ended.
I'll need to consult with the team to see why this is the case.

Talked with the teams and they agreed that we should open it up to work with div. I think the solution that you provided here would work but we wouldn't want it to work with element types like "button" which it seems like it does right now. We would just open it up so that it would work with label, span, or divs.


ListItem subtitle or rightTitle is empty string

The subtitle or rightTitle is an empty string, will report an error
RawText "" must be wrapped in an explicit  component.

Thanks @CecilLee , this should be fixed on the next release later today.


More comprehensive examples

Originally, this page showed three examples, but the only difference between them was in just one switch. This update replaces two of those examples to demonstrate:

How to designate multiple volumes for scan
How to scan a volume without a drive letter

These changes have already been applied to winserver2012r2-ps/storage/Repair-Volume.md, following my pull request #279.

Looks like some conflicts. Let me know if I can help.

@kenwith So I see. The conflict seems to be in the metadata/header area, so I assume the master takes precedence. But the conflict resolution UI seems not to respond to me. I assume it is because I do not have permissions for it.

let me see if I have permissions.

@skycommand - you were 100% correct. It was the metadata. I resolved it and confirmed the example. Much appreciated for sharing your expertise to make the docs better. This is a nice example and much clearer than before.

@kenwith You are welcome. 😊 Glad to be of help. Would you please make sure #540 is handled in the same manner? Thanks in advance.


chore: more explicit str(Dataset) + str(empty Dataset) != ""

cool, yes, slices would be nicer :D

do we want to have a non-empty str() for empty datasets?
is it a worthy format Dataset(...) or do we want something else?


have not been 3 transactions in the wallet SiaUI

Hello!
Coins were sent to the siaui wallet, 3 of all transactions did not come to the wallet, and the rest were credited. Whether there are such failures? Will my coins come with time? Or should something else be done?

no one will answer? or all weekend?)

This is not the best place to get support for Sia.  I recommend you ask your question in the Sia Discord #Help channel.  The devs are not going to be able to help you without more information.  Can you tell us where you sent the coins from?  What the TXid is?  You can follow these steps for lost transactions: https://siawiki.tech/wallet/lost_transactions_troubleshooter
I recommend you try the link I sent, ask for help on Discord, email<EMAIL_ADDRESS>I'm closing this issue as there is no actionable item for a dev.