v3.0.0 RC1 imposes tracecontext as propagation

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?
v2 allowed to have several tracer implementation and hence different propagation models. v3 has migrated to OTel as single tracer implementation and imposed tracecontext as the only propagation format which can be a big pain for migration. The reason is that although traefik supports tracecontext, applications have to do their tracing theirselves and forcing them all to migrate towards is not a trivial task (are the tracing libraries they use compatible with tracecontext? are they willing to upgrade or reimplement tracing for this?). I suggest you either allow it being configurable (otel already supports many propagation models opentelemetry-go-contrib/propagators at main · open-telemetry/opentelemetry-go-contrib · GitHub 2) or support both tracecontext and b3 as most of the tracers support b3.

Hello @jcchavezs,
Thanks for opening this!
Indeed, in v3 we reworked the tracing feature completely to support only OpenTelemetry and instrumenting only with OpenTelemetry SDK, with, as the first intention, trace context propagation, as OpenTelemetry follows the W3C Trace Context specification.

The reason is that although traefik supports tracecontext, applications have to do their tracing theirselves and forcing them all to migrate towards is not a trivial task (are the tracing libraries they use compatible with tracecontext? are they willing to upgrade or reimplement tracing for this?). I suggest you either allow it being configurable (otel already supports many propagation models opentelemetry-go-contrib/propagators at main · open-telemetry/opentelemetry-go-contrib · GitHub 2) or support both tracecontext and b3 as most of the tracers support b3.

This makes sense, and we are open to considering integrating other propagation models and are eager to read community feedback on this.
We are marking this issue as a proposal accordingly.

Ping @zetaab given that he worked out migration from OT to OTel.

Hello,
We do think that multiple propagation models should be possible to configure, and we are marking this issue as an enhancement.
For that, we are working on supporting the OTEL_PROPAGATORS environment variable: https://opentelemetry.io/docs/languages/sdk-configuration/general/#otel_propagators.

I think this issue is solved by #10465, I'm closing it accordingly.

Awesome!


[FEATURE] be able to host statics myself

Is your feature request related to a problem? Please describe.
I am using FastAPI on my private network and can't connect to the internet. but the /docs use cdn. I cannot visit that page.
Although I can rewrite /docs router to replace the html template , and add a /staitc route , but I feel a bit ugly. I wish there is some config for it.
Describe the solution you'd like
add two variable for FastAPI
api = FastAPI(static_prefix="/statics", static_url="/data/swagger-dist/")

with static_prefix="/statics", the /docs html may look like:
<link type="text/css" rel="stylesheet" href="/statics/swagger-ui.css">

with static_url="/data/swagger-dist/" , FastAPI will add router for static_prefix automatically, like
self.router.get(self.static_prefix, response_description=PlainTextResponse, ...)

Describe alternatives you've considered
If you don't want to handle statics, just ignore static_url , I can create it myself, or put it behind nginx.
If do so, you may need to write in the document how to download all static files .
Additional context

Thanks for the report. I'll think about how to best solve this use case.

In the latest versions you can re-use the documentation generator functions to override the default docs: https://github.com/tiangolo/fastapi/blob/master/fastapi/openapi/docs.py
Then you need to download the assets and serve them in your code.
I still have to document it, but maybe you can use that information already.


Plot2D no longer sorts coordinates before plotting

I have a dataset with decreasing latitude coordinates.
With xarray v0.10.8, this is what happens when plotting:

But on latest master the image is now upside down:

Sorry if I missed a change along the way, I was off for a long time.

The most likely source here is https://github.com/pydata/xarray/pull/2294

Looks like a difficult thing to test, also...

Yes #2294 changed the default xincrease, yincrease to be None rather than True. Previously, if xincrease was True we were setting axis limits and this prevented the axis from auto-updating its limits. Now that we are using the invert_axis() method, this might not be an issue. (Actually, now that I look at the code for invert_axis(), all I needed to do earlier was set the kwarg auto=None in the call to set_xlim, so this would be an easy way to revert to the previous code.)
I switched the default to None because I thought it was better to make the least number of modifications to the axis by default.
That said, I cannot reproduce this with a dataset with decreasing latitude so I'm very confused about what's happening.
da = xr.DataArray(np.arange(24).reshape(3,8), dims=('latitude', 'longitude'),
                 coords={'latitude': [8, 0, -8],
                        'longitude': np.arange(8)})

da.plot()

PS: I'm on a ship in the middle of the Pacific with crappy internet access. @fmaussion I'd appreciate it if you could look at this so we can get the release out. I will respond but there'll be a large time lag.

I cannot reproduce this with a dataset with decreasing latitude

Maybe a MPL version issue? Because our docs are also afffected, see:

http://xarray.pydata.org/en/stable/plotting.html#two-dimensions
http://xarray.pydata.org/en/latest/plotting.html#two-dimensions

@fmaussion I'd appreciate it if you could look at this

I Will have a look now

I think this is fixed by #2425?


Update on the Unexpected reserved type string (26:30) error ?

Hello I would like to know if there are any update on this issue with RN 0.62.2 ?
Thank you a lot for your package
node_modules\react-native-common\src\components\other\SegmentedControl.js: Unexpected reserved type string (26:30)

  24 |   static propTypes: {
  25 |     values: PropTypes.array,
> 26 |     selectionColor: PropTypes.string,
     |                               ^
  27 |     selectedIndex: PropTypes.number,
  28 |     onChange: PropTypes.func,
  29 |     titleStyle: PropTypes.any,

I have the same problem. Can anyone help ???
SyntaxError: C:\Users\Mohammad\Desktop\test\node_modules\react-native-common\src\components\other\SegmentedControl.js: Unexpected reserved type string (26:30)
24 |   static propTypes: {
25 |     values: PropTypes.array,

26 |     selectionColor: PropTypes.string,
|                               ^
27 |     selectedIndex: PropTypes.number,
28 |     onChange: PropTypes.func,

+1

already have the same issue.
any support, please

Same here

1- in vscode open \node_modules\react-native-common\src\components\other\SegmentedControl.js
2- In class SegmentedControl delete the following lines
static propTypes: {     values: PropTypes.array,     selectionColor: PropTypes.string,     selectedIndex: PropTypes.number,     onChange: PropTypes.func,     titleStyle: PropTypes.any,     segmentStyle: PropTypes.any,     style: ViewPropTypes.style,   };
3- In class Segment delete the following lines
props: {     value: string;     isSelected: boolean;     selectionColor: string;     segmentStyle?: any;     titleStyle?: any;     onPress: () => void;   };
4- build your project
yarn build
5- Remember to redo this process every time running 'yarn install' or 'npm install' Or use https://www.npmjs.com/package/patch-package


Add the -p option to nc

Purpose
When I run the quick start tutorial in Docker containers (docker run flink), the example/streaming/SocketWindowCount.jar job would fail if it listens on a netcat process started with nc -l 9000. This tutorial works if I change the command into nc -l -p 9000.
Verifying
To reproduce the failure and fix:

In a terminal, start the container docker run --rm -it --name my_flink flink bash.
In the container, install and run netcat apt-get update && apt-get install -y netcat && nc -l 9000.
In another terminal, attaches to the container docker exec -it my_flink bash
In the attached terminal session, start the cluster start-cluster.sh and run the example flink run example/streaming/SocketWindowWordCount.jar --port 9000.

The example would fail with the following errors. The failure could be avoided if we redo the above step but with nc -l -p 9000.
root@493ef04c41ee:/opt/flink# flink run examples/streaming/SocketWindowWordCount.jar --port 9000
Starting execution of program

------------------------------------------------------------
 The program finished with the following exception:

org.apache.flink.client.program.ProgramInvocationException: Job failed. (JobID: b58996c431847f40852dad17f0d21244)
	at org.apache.flink.client.program.rest.RestClusterClient.submitJob(RestClusterClient.java:268)
	at org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:486)
	at org.apache.flink.streaming.api.environment.StreamContextEnvironment.execute(StreamContextEnvironment.java:66)
	at org.apache.flink.streaming.examples.socket.SocketWindowWordCount.main(SocketWindowWordCount.java:92)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:529)
	at org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:421)
	at org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:426)
	at org.apache.flink.client.cli.CliFrontend.executeProgram(CliFrontend.java:816)
	at org.apache.flink.client.cli.CliFrontend.runProgram(CliFrontend.java:290)
	at org.apache.flink.client.cli.CliFrontend.run(CliFrontend.java:216)
	at org.apache.flink.client.cli.CliFrontend.parseParameters(CliFrontend.java:1053)
	at org.apache.flink.client.cli.CliFrontend.lambda$main$11(CliFrontend.java:1129)
	at org.apache.flink.runtime.security.NoOpSecurityContext.runSecured(NoOpSecurityContext.java:30)
	at org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1129)
Caused by: org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
	at org.apache.flink.runtime.jobmaster.JobResult.toJobExecutionResult(JobResult.java:146)
	at org.apache.flink.client.program.rest.RestClusterClient.submitJob(RestClusterClient.java:265)
	... 17 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.flink.streaming.api.functions.source.SocketTextStreamFunction.run(SocketTextStreamFunction.java:96)
	at org.apache.flink.streaming.api.operators.StreamSource.run(StreamSource.java:94)
	at org.apache.flink.streaming.api.operators.StreamSource.run(StreamSource.java:58)
	at org.apache.flink.streaming.runtime.tasks.SourceStreamTask.run(SourceStreamTask.java:99)
	at org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:300)
	at org.apache.flink.runtime.taskmanager.Task.run(Task.java:711)
	at java.lang.Thread.run(Thread.java:748)

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

nc on MacOS does not allow use of both -l and -p. Ubuntu seems fine either with or without -p. What variant of nc is Flink's Docker image using? Is this BusyBox? Rather than change the listed command, we may want to include a note that some variants of nc require the additional flag.

Thanks for following up @greghogan and @zentol . I am closing this PR.


Get Chains Data

This will return the similar accounts, that you see, when you click on the ARROW in a profile.

Merged after rebase https://github.com/jlobos/instagram-web-api/pull/122


@l2succes => Loyalty Applicant submission tracking

Just a little thing to start...this basically loads the segment JS and passes in our key thru sharify.
This does work in the browser JS console...now to try to actually use it in the react code.
This adds the segment JS into the inquiries template, and also directly tracks the successful loyalty submission with the required props.
I did a tiny refactor to the state to just store an array of the selected conversations.

Just pushed a commit that adds the typings, so from the React code you can now just do window.analytics.track(... or whatever.

Ok I think this is ready to go! Unless you want me to do that analytics refactor now @l2succes, I didn't quite follow the other lib recommendation- but I'm down to pair :)

@mzikherman Ok dope! We can do the refactor later


Write minValidatorCount to genesis.json

Write the value from the genesis '--min-validator-count' flag to the genesis.json output
Description
Please provide a detailed description of what was done in this PR
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Breaking changes
Please complete this section if any breaking changes have been made, otherwise delete it
Checklist

[ ] I have assigned this PR to myself
[ ] I have added at least 1 reviewer
[ ] I have added the relevant labels
[ ] I have updated the official documentation
[ ] I have added sufficient documentation in code

Testing

[ ] I have tested this code with the official test suite
[ ] I have tested this code manually

Manual tests
I ran the following command and verified the file:
./polygon-edge genesis --block-gas-limit 10000000 --epoch-size 10 \
--validators-path ./ --validators-prefix test-chain- \
--consensus polybft \
--reward-wallet ... \
--transactions-allow-list-admin ... \
--transactions-allow-list-enabled ... \
--block-gas-limit ... \
--block-time ... \
--min-validator-count 3 \
--max-validator-count 100

Documentation update
Please link the documentation update PR in this section if it's present, otherwise delete it
Additional comments
Please post additional comments in this section if you have them, otherwise delete it

@Stefan-Ethernal, we are doing some prep work to understand the configurable parameters, how they influence the behaviour of our chain, and make decisions on what the genesis for our public testnet and mainnet should look like. While doing that, I found that the genesis.json file was not documenting this setting. I have yet to look into how it would apply to our chain, if at all.
Can you explain what the intended use of MinValidatorSetSize is ATM?

@Stefan-Ethernal, we are doing some prep work to understand the configurable parameters, how they influence the behaviour of our chain, and make decisions on what the genesis for our public testnet and mainnet should look like. While doing that, I found that the genesis.json file was not documenting this setting. I have yet to look into how it would apply to our chain, if at all.
Can you explain what the intended use of MinValidatorSetSize is ATM?

We will definitely use it in on-chain governance, since we are starting to implement that feature for the next release. We will be using it to update the current active validator set. We also added it to PolybftConfig in that governance PR we started: https://github.com/0xPolygon/polygon-edge/pull/1519/files#diff-8291393e7671084ce64a724f76f24df16cf0e262de84905168c4667f94a320abR43

@goran-ethernal seems like the PR you referenced already includes the changes in the branch. I will close this PR as redundant.

Nah, we can merge your PR ASAP. No need to wait for ours.


Prefill attributes when creating new entity

Is there a way to prefill attributes on the entity form? Just like the entityFormOptions in Xrm.Navigation.openForm. I use the dialog to create a new record.

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

ID: 0c917fb9-84c8-2676-9c6a-f33f03ba5da7
Version Independent ID: 057dd7ac-8383-1650-ceb5-cbea3995180c
Content: navigateTo (Client API reference) in model-driven apps - Power Apps
Content Source: powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-Navigation/navigateTo.md
Service: powerapps
GitHub Login: @KumarVivek
Microsoft Alias: kvivek

Please provide parameter similar to openForm - formParameters so that the fields can be prefilled when creating a new record.

In issue 1194 I asked for more info for the pageType entityrecord. Now this is added, I can see how to prefill a form. The createFromEntity and data attributes can now be used.

@Miesjh Thanks for the feedback. I hope you got the issue resolved. Closing the issue. Please re-open the issue if you need to have any information on this.


transparency only on buffers and telescope

First things first: Nice theme! Thx for your work.
Im trying to go for transparency, but all non buffer windows (except telescope and the current active buffer) still have background. Is this a feature or a bug? :D

It's a feature. See onedark_sidebars and onedark_dark_sidebar in README.md.

But even when I unset these, their background stay (at a lighter color).

This is absolutely a bug, I likely missed overriding the sidebar/terminal backgrounds to be transparent. I'll take a look later today!

Well, unset onedark_dark_sidebar in packer doesn't work:
use {
    'monsonjeremy/onedark.nvim',
    config = function() vim.g.onedark_dark_sidebar = false end
}

But unset it outside packer works:
packer.startup(function()
    use {'monsonjeremy/onedark.nvim'}
end)

// ...

vim.g.onedark_dark_sidebar = false

I don't know why. Maybe a bug.
By the way, this plugin is brilliant!

Well, unset onedark_dark_sidebar in packer doesn't work:
use {
    'monsonjeremy/onedark.nvim',
    config = function() vim.g.onedark_dark_sidebar = false end
}

But unset it outside packer works:
packer.startup(function()
    use {'monsonjeremy/onedark.nvim'}
end)

...

vim.g.onedark_dark_sidebar = false

I don't know why. Maybe a bug.
By the way, this plugin is brilliant!

I think this may depend on when you call colorscheme onedark. Are you setting that option before or after?

I believe i've fixed the transparency issue, if you don't mind pulling down the latest and letting me know. It looked good on my local but I may have missed some stuff.

Hi,
thx for this good start into the week :D
One small add to the issue: If onedark_hide_inactive_statusline is set while transparent will not draw a thin line.

Hi,
thx for this good start into the week :D
One small add to the issue: If onedark_hide_inactive_statusline is set while transparent will not draw a thin line.

Nice find, it should also be transparent on the background. I'll fix that as well.
As for the thin line, i've had issues with getting the hidden bar to work when using Packer. If I reload my config it works as expected, so I think there's something that's running async an overwriting it. I'll take a look another night.

@monsonjeremy
It works whether before or after colorscheme onedark. Just does not work in the packer config.
I put them into packer. Now everything works:
use {
    'monsonjeremy/onedark.nvim',
    config = function()
        vim.g.onedark_dark_sidebar = false
        vim.api.nvim_command [[colorscheme onedark]]
    end
}

@aserowy That's interesting I'm not sure where that red line would come from. Definitely can't be from git since it's in the end of buffer gutter. I can take a look in the next couple days.

Sry for the confusion. I have drawn it to show the end of buffer signs 🤣

Ahh i see the issue now @aserowy. This one is a little tricky. The way the transparency works for the background is that the guibg is set to NONE when transparency option is set. Doing this for the EndOfBuffer highlight group just makes it show up white.
I'll take another look and see if I can figure out a workaround.

These signs are unimportant. Don't waste your time on this! 😅

@aserowy I'm going to close the issue, since I don't think there is a good way to resolve the highlights for those. My recommendation is just to hide them by setting this in your config
set fillchars=eob:\ ,


GoogleSigninError: INTERNAL_ERROR code: 8

I am getting code 8 error when I add new account and login with in this package
Any solution for this?

Please add more details, provide information of versions and logs about you are getting.
Is this happening on both IOS and Android and if possible provide a reproducible example


"Method not found" using getBlock with RpcProvider

getBlock throws an error when using it with an RpcProvider
Error: -32601: Method not found     at RpcProvider.<anonymous> (/node_modules/starknet/dist/provider/rpc.js:91:35)
but everything is fine with a default provider

Hello!
Can you please provide more code, how do you call getBlock? Since this method exists... Also, which version of starknet.js are you using?

I'm using starknet v4.3.0
here is how I call getBlock:
import { RpcProvider } from 'starknet'; const providerConfig1 = { 	nodeUrl: url }; const provider1 = new RpcProvider(providerConfig1); provider1.getBlock(150000).then(console.log);
or
import { Provider } from 'starknet'; const providerConfig2 = { 	rpc: { 		nodeUrl: url 	} }; const provider2 = new Provider(providerConfig2); provider2.getBlock(150000).then(console.log);
same error for both cases
I remember it worked previously, but recently, it stopped (literally from one day to another), maybe the lib changed? but I don't know if it is possible as it is the same version

hi, I just found the problem
starknet hasn't been updated for pathfinder v0.3.0
e.g. for getBlock with an rpc provider, starknet tries to call either starknet_getBlockByHash or starknet_getBlockByNm umber depending on the type of blockIdentifier (can be a hash or a number), but both methods have been deleted in v0.3.0 of pathfinder
you should use starknet_getBlockWithTxs or starknet_getBlockWithTxHashes instead

hi, I just found the problem
starknet hasn't been updated for pathfinder v0.3.0
e.g. for getBlock with an rpc provider, starknet tries to call either starknet_getBlockByHash or starknet_getBlockByNumber depending on the type of blockIdentifier (can be a hash or a number), but both methods have been deleted in v0.3.0 of pathfinder
you should use starknet_getBlockWithTxs or starknet_getBlockWithTxHashes instead

hi, I just found the problem
starknet hasn't been updated for pathfinder v0.3.0
e.g. for getBlock with an rpc provider, starknet tries to call either starknet_getBlockByHash or starknet_getBlockByNumber depending on the type of blockIdentifier (can be a hash or a number), but both methods have been deleted in v0.3.0 of pathfinder
you should use starknet_getBlockWithTxHashes instead

hi, I just found the problem
starknet hasn't been updated for pathfinder v0.3.0
e.g. for getBlock with an rpc provider, starknet tries to call either starknet_getBlockByHash or starknet_getBlockByNumber depending on the type of blockIdentifier (can be a hash or a number), but both methods have been deleted in v0.3.0 of pathfinder
you should use starknet_getBlockWithTxHashes instead
same problem for getCode and getTransactionCount


[Test] add TinyYoloV2 into the model test

TinyYoloV2 is one of the first wave models and is supported by webnn-samples, please add it into the model test. Thanks.

Fixed by #87, close it.


Introduce KeyIdentifier class

For historic reasons, many places in the OpenPGP API and specification rely on 64-bit key-ids.
However, later versions of the standard migrate to use fingerprints (20 or 32 bytes) to reduce the risk of attacks based on the birthday paradox (key-id collisions).
In this PR I introduce the KeyIdentifier class, which can be created from both a key-id or a fingerprint, and which shall be used as a common stand-in for either key-id or fingerprints.
This enables a smooth transition from using key-ids to using fingerprints.
TODO:

[x] Implement tests
[x] integrate KeyIdentifier into existing API to transition away from pure key-ID uses

In main as a7930a250edb83c625c9a0f5297456272e8cf25d


improve block scrolling

use js to prevent scrolling to avoid jumping content, due to scrollbar bidding
https://codepen.io/wesleypimentel/pen/KpgXJW

#1013

done in 12.12.0


loadPCMFromByteArray is not working

I have a function that generates a sound, and then loads it into a Sound object:
  public function SynthSamplesToSound(sound:Sound):Void {
    // get the samples
    var sampleOutput=new ByteArray();
    SynthAllSamples(sampleOutput);
    sampleOutput.position=0;
    sound.loadPCMFromByteArray(sampleOutput, sampleOutput.length>>2, "float", false, 44100.0);
  }

This function works in Flash (>15.0), but on native, I get the following message:
Error after opening sound data
Not Sound
AL lib: (EE) alc_cleanup: 1 device not closed

I figured this one out. Here's my new function:
  public function SynthSamplesToSound(sound:Sound):Void {
    // get the samples
    var sampleOutput=new ByteArray();
    sampleOutput.bigEndian = false;
    #if flash
      SynthAllSamples(sampleOutput);
      sampleOutput.position=0;
      // The following function only works in Flash Players >= 15.0
      sound.loadPCMFromByteArray(sampleOutput, sampleOutput.length>>2, "float", false, 44100.0);
    #else
      ExportWAVToByteArray(sampleOutput); // Adds WAV headers, then calls SynthAllSamples() internally.
      sampleOutput.position=0;
      // OpenFL support WAV as a compressed data format.
      sound.loadCompressedDataFromByteArray(sampleOutput, sampleOutput.length);
    #end
  }

The v2 implementation of loadPCMFromByteArray does something similar. However, the generated samples are floating point samples. I changed ExportWAVToByteArray() to generate 16-bit samples to get everything working.
However, the reason that loadPCMFromByteArray wasn't working initially was that it accepts "float" (and "float" is the default), but in lime, OpenALSound::OpenALSound(float *inData, int len), and a few other constructors for other input types have the following lines:
     //Work out the format from the data
     if (_channels == 1) {
        if (_bitsPerSample == 8 ) {
           format = AL_FORMAT_MONO8;
        } else if (_bitsPerSample == 16) {
           format = (int)AL_FORMAT_MONO16;
        }
     } else if (_channels == 2) {
        if (_bitsPerSample == 8 ) {
           format = (int)AL_FORMAT_STEREO8;
        } else if (_bitsPerSample == 16) {
           format = (int)AL_FORMAT_STEREO16;
        }
     } //channels = 2

However, _bitsPerSample is 32! To use OpenAL to play FLOAT32 samples requires an extension, which isn't available on all platforms. Ogg will not produce FLOAT32, so we're safe there. Since the main use for WAV files will be very short sounds, we may want to consider converting FLOAT32 samples to 16-bit samples in this block. It will be something like:
while(inPtr < endInPtr)
  *outPtr++ = (float)(*inPtr++) / 32767.0f;

where inPtr and endInPtr are float*, and outPtr is short* (or int16_t).
That change in lime legacy will make OpenFL's loadPCMFromByteArray work as expected. However, that's adding the hidden cost of this loop. I think it's worth it because this function is usually called only when the app is loading something, so it's probably during a "Loading . . ." screen. It's still so fast that it's unnoticeable for small files.

It seems that there's some work for html5 sound loading, but I'm not sure if that includes from samples. It looks like only loading from an URL with sound.js is currently supported in OpenFL. Does Lime have a way to load samples on html5, yet?

Hi!
Although this is technically in Lime legacy, I'm moving legacy issues into the OpenFL issue tracker, so they can be tracked as Flash API behavior bugs and fixes. From a Lime API perspective, the legacy API is deprecated, so I'm going to keep the Lime issue tracker open for issues in the Lime 2 API.
It sounds like, ideally, we want to find a way to automatically detect the audio type without adding a header, and then make sure that when you use a ByteArray, that it's in a format that's compatible with OpenAL? Happy to talk about this more on the new issue I've opened:
https://github.com/openfl/openfl/issues/511
Thank you! :smile:


Nodevertical parameter-ize the number of nodes

This will enable NodeVertical to run on smaller clusters  (clusters =< 4 nodes)

#43 fixes this


support reading config in csi cinder driver

support reading config in csi cinder driver

/cc @rootfs @chakri-nelluri
hey rootfs and chakri, welcome to review, thank you.

@chakri-nelluri Thanks your perfect suggestion, I will consider it in another pr:)

Hi @rootfs @chakri-nelluri, done, PTAL. thanks.

would love to have a followup PR with instructions and screenshot.


Denon AVR-X2400H not working

My new 2400H is not working properly, before i had an 2100 and this one worked fine.
The names of the different inputs have changed, how can i retrieve the different input names? especially internet radio.

http://manuals.denon.com/AVRX2400H/EU/EN/GFNFSYicezyjvb.php#OKNRMLjzyiwmvh
Internet Radio looks like it is handled via HEOS which works differently.  Domoticz does support that as well, but this plugin does not

hello, i also have Denon AVR-X2400H, on/off and volume works fine, but selector switch isnt working (dont care aboout inet radio). Any idea what should i check or add support in this script...
Jan


Finish merged layer/filter

The demo-v2-options branch has our new map view UI, which includes a merged layer/zone navigation for the data choices UI. The UI of this is mostly working but not all of the data is actually being applied to the filter view.

[ ] Get the new combined 'location' selection to apply appropriate filters to the location
[ ] Changing location type will need to clear any selected 'location' filters (since previously selected choices are no longer relevant). Need to make this obvious to user -maybe use a tooltip to show that it has been cleared? Include a 'don't show again' button that removes the tooltip for the current session (this is much easier to implement than adding cookies which can be a long term add, if we keep this ui element).
[x] Merge filterView.components with mapView.initialOverlays for a unified list to be used for all views. After #388 is complete, we can move a lot of this out to meta.json - for now it can be either in code or in a static config file.
[x] For now, flag any 'layer' items that do not work with filters yet - after #388 is complete we will have the necessary data available.
[x] Add the legend for layers when a layer-relevant data source is selected. Move this out of the data dropdown where it was in 'layers' and instead put it in the bottom right of the map.

I'll be working on the first bullet points of this one today so we can close out this issue.

Closing this - #443 resolves the first two bullets.


Rename lint.sh to verify-lint.sh

Rename hack/lint.sh to hack/verify-lint.sh to make the naming consistent.
Signed-off-by: Random-Liu<EMAIL_ADDRESS>

@mikebrow Thanks for reviewing!


DotnetCoreInstaller does not set active tool

Required Information
Question, Bug, or Feature?
Type: Bug
Enter Task Name: DotNetCoreInstaller@1
Environment

Server:
https://dev.azure.com/aahyp/SF/_build/results?buildId=432022&view=results

Agent - Hosted or Private:
Private: Ubuntu 16.04 LTS-based, with dotnet 2.2 and 3.0 sdk's preinstalled (self-built container running in Kubernetes).
Agent version: v2.160.1
Dotnet installations based on code almost similar to: https://github.com/microsoft/azure-pipelines-image-generation/blob/master/images/linux/scripts/installers/1604/dotnetcore-sdk.sh

Issue Description
Selecting dotnet version does not work (well). Often after selecting 2.2.x dotnet 3.0 is still used. Although sometimes it does seem to have an effect.
I expect the version to be used that I have just installed.
Task logs
Full log of build in first reply (to keep this item clean).
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
No errors.

2019-12-05T15:13:33.7918074Z ##[section]Starting: Job
2019-12-05T15:13:34.7992238Z ##[section]Starting: Initialize job
2019-12-05T15:13:34.7992560Z Agent name: 'buildagent-vnext-6c7dbd9c5-4fmfs'
2019-12-05T15:13:34.7992650Z Agent machine name: 'buildagent-vnext-6c7dbd9c5-4fmfs'
2019-12-05T15:13:34.7992700Z Current agent version: '2.160.1'
2019-12-05T15:13:34.8001128Z Agent running as: 'root'
2019-12-05T15:13:34.8108094Z Prepare build directory.
2019-12-05T15:13:34.8464165Z Set build variables.
2019-12-05T15:13:34.8516054Z Download all required tasks.
2019-12-05T15:13:34.9128346Z Start tracking orphan processes.
2019-12-05T15:13:34.9256799Z ##[section]Finishing: Initialize job
2019-12-05T15:13:34.9804163Z ##[section]Starting: Checkout
2019-12-05T15:13:35.0136657Z ==============================================================================
2019-12-05T15:13:35.0136954Z Task         : Get sources
2019-12-05T15:13:35.0136993Z Description  : Get sources from a repository.  Supports Git, TfsVC, and SVN repositories.
2019-12-05T15:13:40.9665128Z Version      : 1.0.0
2019-12-05T15:13:40.9665164Z Author       : Microsoft
2019-12-05T15:13:40.9665199Z Help         : More Information
2019-12-05T15:13:40.9665281Z ==============================================================================
2019-12-05T15:13:41.4473637Z Cleaning any cached credential from repository: AzureDevOps (Git)
2019-12-05T15:13:41.4527219Z ##[section]Finishing: Checkout
2019-12-05T15:13:41.4601052Z ##[section]Starting: Finalize Job
2019-12-05T15:13:41.4644977Z Start cleaning up orphan processes.
2019-12-05T15:13:41.4741282Z ##[section]Finishing: Finalize Job
2019-12-05T15:13:41.4799191Z ##[section]Finishing: Job

My test build pipeline:
ASP.NET
Build and test ASP.NET projects.
Add steps that publish symbols, save build artifacts, deploy, and more:
https://docs.microsoft.com/azure/devops/pipelines/apps/aspnet/build-aspnet-4
trigger:

master

pool:
name: 'Docker Build Agents'
steps:

task: Bash@3
inputs:
targetType: 'inline'
script: 'echo "ToolsDir = $(Agent.ToolsDirectory)"'

task: Bash@3
inputs:
targetType: 'inline'
script: 'echo "PATH = $PATH"'

task: Bash@3
inputs:
targetType: 'inline'
script: 'echo "DOTNET_ROOT =  $DOTNET_ROOT"'

task: Bash@3
inputs:
targetType: 'inline'
script: 'ls -l /root/.dotnet/tools'

task: Bash@3
inputs:
targetType: 'inline'
script: 'ls -l /azp/agent/_work/_tool/dotnet'

task: Bash@3
inputs:
targetType: 'inline'
script: 'which dotnet'

task: Bash@3
inputs:
targetType: 'inline'
script: 'dotnet --version'

task: Bash@3
inputs:
targetType: 'inline'
script: '/azp/agent/_work/_tool/dotnet/dotnet --version'

task: DotNetCoreInstaller@1
displayName: 'Use .NET Core sdk 2.2'
inputs:
packageType: 'sdk'
version: '2.2.x'

task: Bash@3
inputs:
targetType: 'inline'
script: 'which dotnet'

task: Bash@3
inputs:
targetType: 'inline'
script: 'echo "DOTNET_ROOT =  $DOTNET_ROOT"'

task: Bash@3
inputs:
targetType: 'inline'
script: 'dotnet --version'

task: Bash@3
inputs:
targetType: 'inline'
script: '/azp/agent/_work/_tool/dotnet/dotnet --version'

It's also unclear to me what the difference is between DotnetCoreInstaller and UseDotNet. They both seem to be maintained and work similar.

So UseDotNet has the same issue:
2019-12-06T11:36:05.5307004Z ##[section]Starting: Job
2019-12-06T11:36:11.5503763Z ##[section]Starting: Initialize job
2019-12-06T11:36:11.5503979Z Agent name: 'buildagent-vnext-6c7dbd9c5-4fmfs'
2019-12-06T11:36:11.5504047Z Agent machine name: 'buildagent-vnext-6c7dbd9c5-4fmfs'
2019-12-06T11:36:11.5504114Z Current agent version: '2.160.1'
2019-12-06T11:36:11.5513593Z Agent running as: 'root'
2019-12-06T11:36:11.5624227Z Prepare build directory.
2019-12-06T11:36:11.5989374Z Set build variables.
2019-12-06T11:36:11.6041007Z Download all required tasks.
2019-12-06T11:36:11.6750822Z Start tracking orphan processes.
2019-12-06T11:36:11.6991636Z ##[section]Finishing: Initialize job
2019-12-06T11:36:11.7639742Z ##[section]Starting: Checkout
2019-12-06T11:36:11.7969681Z ==============================================================================
2019-12-06T11:36:11.7969825Z Task         : Get sources
2019-12-06T11:36:11.7969866Z Description  : Get sources from a repository.  Use this task to change the version of .NET Core used in subsequent tasks. Additionally provides proxy support.
2019-12-06T11:36:18.2058892Z Version      : 2.0.24
2019-12-06T11:36:18.2058929Z Author       : Microsoft Corporation
2019-12-06T11:36:18.2059133Z Help         : https://aka.ms/AA4xgy0
2019-12-06T11:36:18.2059239Z ==============================================================================
2019-12-06T11:36:18.6088979Z Tool to install: .NET Core sdk version 2.2.x.
2019-12-06T11:36:20.5011433Z Found version 2.2.402 in channel 2.2 for user specified version spec: 2.2.x
2019-12-06T11:36:20.5645148Z Version: 2.2.402 was found in cache.
2019-12-06T11:36:20.5647075Z Creating global tool path and pre-pending to PATH.
2019-12-06T11:36:20.5648650Z ##[section]Finishing: UseDotNet
2019-12-06T11:36:20.5654000Z ##[section]Starting: Bash
2019-12-06T11:36:20.5657253Z ==============================================================================
2019-12-06T11:36:20.5657302Z Task         : Bash
2019-12-06T11:36:20.5657340Z Description  : Run a Bash script on macOS, Linux, or Windows
2019-12-06T11:36:20.5657375Z Version      : 3.159.3
2019-12-06T11:36:20.5657422Z Author       : Microsoft Corporation
2019-12-06T11:36:20.5657459Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash
2019-12-06T11:36:20.5657712Z ==============================================================================
2019-12-06T11:36:20.7333150Z Generating script.
2019-12-06T11:36:20.7349131Z Script contents:
2019-12-06T11:36:20.7349361Z which dotnet
2019-12-06T11:36:20.7371482Z ========================== Starting Command Output ===========================
2019-12-06T11:36:20.7397789Z [command]/bin/bash --noprofile --norc /azp/agent/_work/_temp/23bc2787-3ab4-44d1-b8ca-a7d7c103be0d.sh
2019-12-06T11:36:20.7492187Z /azp/agent/_work/_tool/dotnet/dotnet
2019-12-06T11:36:20.7549036Z
2019-12-06T11:36:20.7620723Z ##[section]Finishing: Bash
2019-12-06T11:36:20.7627082Z ##[section]Starting: Bash
2019-12-06T11:36:20.7630322Z ==============================================================================
2019-12-06T11:36:20.7630373Z Task         : Bash
2019-12-06T11:36:20.7630410Z Description  : Run a Bash script on macOS, Linux, or Windows
2019-12-06T11:36:20.7630445Z Version      : 3.159.3
2019-12-06T11:36:20.7630526Z Author       : Microsoft Corporation
2019-12-06T11:36:20.7630577Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash
2019-12-06T11:36:20.7630613Z ==============================================================================
2019-12-06T11:36:20.9186348Z Generating script.
2019-12-06T11:36:20.9193419Z Script contents:
2019-12-06T11:36:20.9194116Z echo "DOTNET_ROOT =  $DOTNET_ROOT"
2019-12-06T11:36:20.9217266Z ========================== Starting Command Output ===========================
2019-12-06T11:36:20.9243700Z [command]/bin/bash --noprofile --norc /azp/agent/_work/_temp/0d48c6a1-d662-4ccc-9ed7-20606b467362.sh
2019-12-06T11:36:20.9367947Z DOTNET_ROOT =  /azp/agent/_work/_tool/dotnet
2019-12-06T11:36:20.9380920Z
2019-12-06T11:36:20.9441450Z ##[section]Finishing: Bash
2019-12-06T11:36:20.9447466Z ##[section]Starting: Bash
2019-12-06T11:36:20.9450803Z ==============================================================================
2019-12-06T11:36:20.9450847Z Task         : Bash
2019-12-06T11:36:20.9451070Z Description  : Run a Bash script on macOS, Linux, or Windows
2019-12-06T11:36:20.9451104Z Version      : 3.159.3
2019-12-06T11:36:20.9451183Z Author       : Microsoft Corporation
2019-12-06T11:36:20.9451217Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash
2019-12-06T11:36:20.9451251Z ==============================================================================
2019-12-06T11:36:21.0968974Z Generating script.
2019-12-06T11:36:21.0984682Z Script contents:
2019-12-06T11:36:21.0984933Z dotnet --version
2019-12-06T11:36:21.1010006Z ========================== Starting Command Output ===========================
2019-12-06T11:36:21.1035456Z [command]/bin/bash --noprofile --norc /azp/agent/_work/_temp/7a709e7d-cee4-40fe-90a5-11f7788f3087.sh
2019-12-06T11:36:21.2408595Z 3.0.101
2019-12-06T11:36:21.2529201Z
2019-12-06T11:36:21.2614312Z ##[section]Finishing: Bash
2019-12-06T11:36:21.2620800Z ##[section]Starting: Bash
2019-12-06T11:36:21.2623734Z ==============================================================================
2019-12-06T11:36:21.2623807Z Task         : Bash
2019-12-06T11:36:21.2623838Z Description  : Run a Bash script on macOS, Linux, or Windows
2019-12-06T11:36:21.2623868Z Version      : 3.159.3
2019-12-06T11:36:21.2623942Z Author       : Microsoft Corporation
2019-12-06T11:36:21.2623975Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash
2019-12-06T11:36:21.2624008Z ==============================================================================
2019-12-06T11:36:21.4134502Z Generating script.
2019-12-06T11:36:21.4150734Z Script contents:
2019-12-06T11:36:21.4151190Z /azp/agent/_work/_tool/dotnet/dotnet --version
2019-12-06T11:36:21.4196207Z ========================== Starting Command Output ===========================
2019-12-06T11:36:21.4227415Z [command]/bin/bash --noprofile --norc /azp/agent/_work/_temp/fe1c6e27-da48-4292-a9a5-b39dc60a71d4.sh
2019-12-06T11:36:21.5551929Z 3.0.101
2019-12-06T11:36:21.5643710Z
2019-12-06T11:36:21.5711028Z ##[section]Finishing: Bash
2019-12-06T11:36:21.5770716Z ##[section]Starting: Checkout
2019-12-06T11:36:21.5772728Z ==============================================================================
2019-12-06T11:36:21.5772774Z Task         : Get sources
2019-12-06T11:36:21.5772809Z Description  : Get sources from a repository. Supports Git, TfsVC, and SVN repositories.
2019-12-06T11:36:21.5772852Z Version      : 1.0.0
2019-12-06T11:36:21.5772886Z Author       : Microsoft
2019-12-06T11:36:21.5772920Z Help         : [More Information](https://go.microsoft.com/fwlink/?LinkId=798199)
2019-12-06T11:36:21.5772961Z ==============================================================================
2019-12-06T11:36:22.0493086Z Cleaning any cached credential from repository: AzureDevOps (Git)
2019-12-06T11:36:22.0549503Z ##[section]Finishing: Checkout
2019-12-06T11:36:22.0629516Z ##[section]Starting: Finalize Job
2019-12-06T11:36:22.0673804Z Start cleaning up orphan processes.
2019-12-06T11:36:22.0862639Z ##[section]Finishing: Finalize Job
2019-12-06T11:36:22.0925086Z ##[section]Finishing: Job

@hiyadav can you please reply to this

Hey @kwaazaar
Will get to this issue today, you can expect a reply by tomorrow.

Hey,
The UseDotNet task by default installs/makes version available at $(Agents.ToolsDirectory). In your case it can find 2.2.402 version already present (probably installed from previous run of pipeline) in the agent's tool cache $(Agent.ToolDirectory) = Agent/_work/tools/dotnet.
As the same agent might be getting used in different pipelines, which could have installed 3.1.101 SDK version using the same task. Those installed version by default gets cached (so that consecutive runs are faster) and hence are also present in the agent's cache.
How you can use the task for getting exclusive version:
The task has been designed to provide you with the required version, but as dotnet versions can co-exist, there might be other versions installed at the default location. You can thus do either:

Use global.json in source code to specify the required sdk version. (ensures the right version is picked out of the many available)
Specify this task input installationPath: $(Agent.TempDirectory) . This will ensure that the versions installed during a pipeline instance's execution, are the only ones available. The installed versions at this path will not be cached and hence won't be available for subsequent pipeline's execution.

The documentation for global.json states that "In general, you want to use the latest version of the tools, so no global.json file is needed.". Because of breaking changes in the dotnet cli the latest SDK is not what I want, but I want to use the latest 2.2 SDK for my build pipeline.
So the use of global.json could indeed fix my problem. However, the version-field has to be a full version specification (it does not have globbing support), but by using DotnetInstallerTask/UseDotnetTask I dó have globbing support.
Therefore it could be useful if both of these tasks would support the generation of a global.json in the working folder, so that the dotnet cli would use the exact version these tasks have just downloaded.
I know this is a different way of handling global.json, since it can already read version specs from existing global.json files below the working folder, but I think this could be a nice way of working and a central place for specifying sdk-version, instead of maintaining multiple global.json files.

The documentation for global.json states that "In general, you want to use the latest version of the tools, so no global.json file is needed.". Because of breaking changes in the dotnet cli the latest SDK is not what I want, but I want to use the latest 2.2 SDK for my build pipeline.
So the use of global.json could indeed fix my problem. However, the version-field has to be a full version specification (it does not have globbing support), but by using DotnetInstallerTask/UseDotnetTask I dó have globbing support.
Therefore it could be useful if both of these tasks would support the generation of a global.json in the working folder, so that the dotnet cli would use the exact version these tasks have just downloaded.
I know this is a different way of handling global.json, since it can already read version specs from existing global.json files below the working folder, but I think this could be a nice way of working and a central place for specifying sdk-version, instead of maintaining multiple global.json files.

Adding @pulkitaggarwl to consider the enhancement.
You can still use the 2nd approach to work with exact versions, mentioning it below here:
2. Specify this task input installationPath: $(Agent.TempDirectory) . This will ensure that the versions installed during a pipeline instance's execution, are the only ones available. The installed versions at this path will not be cached and hence won't be available for subsequent pipeline's execution.

@kwaazaar

So the use of global.json could indeed fix my problem. However, the version-field has to be a full version specification (it does not have globbing support), but by using DotnetInstallerTask/UseDotnetTask I dó have globbing support.

Even if you specify a full version in global.json and a newer patch version is installed, it will be picked up by dotnet. See the matching rules.

I know this is a different way of handling global.json, since it can already read version specs from existing global.json files below the working folder, but I think this could be a nice way of working and a central place for specifying sdk-version, instead of maintaining multiple global.json files.

Maintaining multiple global.json files is a choice by design. If we attempt to replace it by a single global.json, it might actually be wrong.
Additionally, auto-generating a global.json might result in different behaviors across local dev environment (where no global.json is used) and CI environment (where global.json will be auto-generated based on task input). This might be a confusing and unnecessary impact.

You can still use the 2nd approach to work with exact versions, mentioning it below here:
2. Specify this task input installationPath: $(Agent.TempDirectory) . This will ensure that the versions installed during a pipeline instance's execution, are the only ones available. The installed versions at this path will not be cached and hence won't be available for subsequent pipeline's execution.

I believe the solution suggested by @hiyadav solves your problem


Update readme

Bring readme up to date.

Coverage remained the same at 63.989% when pulling c23da9e3ba351daa7de9a16aeb84926b07a93c38 on ernfrid:update_readme into 2c3645f43daea297f3719959574c3346315a224d on hall-lab:master.

Coverage remained the same at 63.989% when pulling c23da9e3ba351daa7de9a16aeb84926b07a93c38 on ernfrid:update_readme into 2c3645f43daea297f3719959574c3346315a224d on hall-lab:master.


Do wallet_rpc_client.send_transaction Throw Excepiton KeyError: 'coin_solutions'

Do wallet_rpc_client.send_transaction Throw Excepiton KeyError: 'coin_solutions'
Im use latest version
pip list :
chia-blockchain        1.2.4.dev5

@mariano54 Can U help me?

Im try use chia-bloackchain 1.2.3  , It's still the same。
Do not close this issue until this issue is resolved！！！

Use latest version chia-blockchain and pool-reference
Do wallet_rpc_client.send_transaction
Throw Exception:
res = await self.wallet_rpc_client.send_transaction(self.wallet_id, amount, address, fee)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/chia/rpc/wallet_rpc_client.py", line 132, in send_transaction
return TransactionRecord.from_json_dict(res["transaction"])
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/chia/util/streamable.py", line 358, in from_json_dict
return dataclass_from_dict(cls, json_dict)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/chia/util/streamable.py", line 73, in dataclass_from_dict
return klass({f: dataclass_from_dict(fieldtypes[f], d[f]) for f in d})
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/chia/util/streamable.py", line 73, in
return klass({f: dataclass_from_dict(fieldtypes[f], d[f]) for f in d})
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/chia/util/streamable.py", line 61, in dataclass_from_dict
return dataclass_from_dict(get_args(klass)[0], d)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/chia/util/streamable.py", line 73, in dataclass_from_dict
return klass({f: dataclass_from_dict(fieldtypes[f], d[f]) for f in d})
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/chia/util/streamable.py", line 73, in
return klass({f: dataclass_from_dict(fieldtypes[f], d[f]) for f in d})
KeyError: 'coin_solutions'

did you sh install.sh in chia-blockchain, and download the lastest pool-reference code?