text:
Replace UIFont with Font, add image to AppearanceProvider

Some small changes which will likely be scrapped by 4.0 but help get rid of some UIKit bits for now

Nice!
Before I merge...I'm all for scrapping all UIKit parts from the parts used by the SwiftUI components. Does this change affect the UIKit namespace or the demo in any way?

Nice!
Before I merge...I'm all for scrapping all UIKit parts from the parts used by the SwiftUI components. Does this change affect the UIKit namespace or the demo in any way?

Oh shoot I didn't check the demos projects 😬 it might mess with those... what do you mean UIKit namespace?

Oh shoot I didn't check the demos projects 😬 it might mess with those... what do you mean UIKit namespace?

There is an entire section called UIKit that can be used to build keyboards with UIKit. Even if I'd love to remove those parts of the library, to make it more compact, I understand the need for UIKit support going forward.
So, while the future focus of the library is SwiftUI, I have decided to keep the UIKit namespace at least until the next major version. However, those parts must not limit the SwiftUI parts going forward.
So, for instance, if the UIKit namespace or the demo uses any of the UIFont or UIColor parts that are now removed, we can't just simply remove them. Instead, we should then keep the UIKit parts, but move them into the UIKit namespace to make them isolated there. They do not have to be part of the overall design. Plain extensions are just fine.
If the UIKit demo nor the UIKit namespace is affected by this change, we can just merge them. The UIKit namespace will more and more become an isolated thing that just uses the models and UI agnostic parts of the library.

There is an entire section called UIKit that can be used to build keyboards with UIKit. Even if I'd love to remove those parts of the library, to make it more compact, I understand the need for UIKit support going forward.
So, while the future focus of the library is SwiftUI, I have decided to keep the UIKit namespace at least until the next major version. However, those parts must not limit the SwiftUI parts going forward.
So, for instance, if the UIKit namespace or the demo uses any of the UIFont or UIColor parts that are now removed, we can't just simply remove them. Instead, we should then keep the UIKit parts, but move them into the UIKit namespace to make them isolated there. They do not have to be part of the overall design. Plain extensions are just fine.
If the UIKit demo nor the UIKit namespace is affected by this change, we can just merge them. The UIKit namespace will more and more become an isolated thing that just uses the models and UI agnostic parts of the library.

Oh wow I didn't understand you were trying to keep the UIKit folder and demo working for 4.0!  So if current files that deal with font are copied over into the UIKit folder to be used in the UIKit namespace only, can these SwiftUI changes that I did here be kept?
Also if these changes don't work how you like, it's no big deal to scrap them lol they are pretty small changes anyways.

Oh wow I didn't understand you were trying to keep the UIKit folder and demo working for 4.0!  So if current files that deal with font are copied over into the UIKit folder to be used in the UIKit namespace only, can these SwiftUI changes that I did here be kept?
Also if these changes don't work how you like, it's no big deal to scrap them lol they are pretty small changes anyways.

If the following is true, we can merge the changes without problems:

The library code builds
The unit tests pass
Both demo apps work like before

If not, we may have to add some UIKit-exclusive extensions and use them in the UIKit parts.
The changes are exactly how I imagine the library will evolve during the 4.0 development phase. 👍

If the following is true, we can merge the changes without problems:

The library code builds
The unit tests pass
Both demo apps work like before

If not, we may have to add some UIKit-exclusive extensions and use them in the UIKit parts.
The changes are exactly how I imagine the library will evolve during the 4.0 development phase. 👍

I'm merging this to another branch to see if it works.

I'm merging this to another branch to see if it works.

Hmmm...getting build errors on this branch...

Hmmm...getting build errors on this branch...

authors: Brennanium danielsaidi

repo: danielsaidi/KeyboardKit


text:
Latest change in 2.7.4 breaks models that have an attribute type

We have a non-polymorphic model that has an attribute type. This was working fine on 2.7.3 but since 2.7.4 (this commit in particular) the tests fail as it's trying to create a model of type type rather than the generic model with an attribute type.
More concretely, we have a model user that has an attribute type:
DS.Model.extend({
  type: DS.attr('string')
});

We then have factories for several types. So
FactoryGuy.define('user', {
  teacher: {
    type: 'teacher'
  },
  student: {
    type: 'student'
  }
});

In 2.7.3, doing make('teacher') resulted in creating a record of type user with the type attribute equal to teacher.
In 2.7.4, doing make('teacher') results in creating a record of type teacher (which fails because there's no such model).
There's probably something to be said about our choice of the attribute name type. But I think explicitly indicating a factory as polymorphic could provide a way to make a distinction between the two cases and act accordingly.

I have been waiting for a complaint about this issue for a long time.  As you said, the latest commit forced the issue. There is a way to fix it ( I think ) .. but give me a moment to do that.

Actually we do use Rails on the back-end :-). And there it's a polymorphic model. However, to keep the front-end model architecture simpler, we decided not to use the polymorphism there.

Hmm .. wow .. that is interesting.
Not sure actually how to fix this issue, since I can't really force people to say this factory is polymorphic ( can I ? ) .. seems pretty harsh but maybe it's not too bad?  Otherwise there is no way to tell if that type attibute is used for the polymorphic type or not .. any thoughts?

That's what I was thinking about too. Polymorphism is only enabled by your latest commit right?
That would be the most "flexible" in terms of allowing everyone to configure their app to work with ember-data-factory-guy. I agree that our choice of naming causes confusion but we're technically not doing anything "wrong" wrt the JSON-API standard and thus Ember Data.

Polymorphism has been enabled forever in factory guy. I just always based everything on the assumption that no one would use the type attribute.
So, let me ponder what to do about this. And yeah, I guess your not doing anything wrong, just bringing up a tricky issue.

How about it I make it so you flag your factory as NOT polymorphic
polymorphic: false

when you are using type as attribute
That was it is backwards compatible. And it is the exception anyway, so ?? what do you think about that.

That sounds like a good solution to me!

fixed in v2.7.5 ( but let me know if otherwise )

source: gharchive/issue

authors: YoranBrondsema danielspaniel

repo: danielspaniel/ember-data-factory-guy

license: mit

license_type: permissive

license_source: bigquery


text:
Ubuntu 20.04 segmentation fault

When running on Ubuntu 20.04 video exits with SIGSEGV

This will be fixed in 0.1.3. A work around is to import decord before importing from the cvvideoplayer and before importing cv2

Fixed

license: MIT

license_source: github-api


text:
Dreamer for DMLab

I'm not sure if you're still working on this, but if you are, I was wondering why the implementation here doesn't support DMLab environments. The older implementation does, but I'd rather not use have to use the older dependencies it relies on. Are you planning on adding this, or do I have to go with the older implementation on google-research?

Hey, I'm planning on adding this but I don't have a clear timeline for it yet.

authors: danijar syigzaw

repo: danijar/dreamer


text:
文件后缀名不能识别

提bug前先检查以下是否已经执行

[x] 我已更新了最新版本的代码
[x] 我已经仔细地阅读了readme 文档
[x] 我已在FAQ里查找了可能寻找的答案
[x] 我已经尝试搜索过历史关闭issue寻找可能的答案

bug描述
不能识别文件类型，原来是png的，用py写的代码
提供有用的信息

#184

和微信规则一样，你要识别成啥，自己加后缀名。

可不可以加上参数来指定

可以，目前有一个pr在进行中

authors: Cassius0924 danni-cool hhhhhge

repo: danni-cool/wechatbot-webhook


text:
Made MAX_WIND_INTENSITY configurable. Fixed links to canvas_layer.js in the examples.

Making MAX_WIND_INTENSITY configurable allows plotting vectors other than wind of different scale (say sea currents).

Apologies for the slow reply, thanks for sending this along. Had just a few comments -- will merge when I hear back.

source: gharchive/pull-request

authors: dannycochran paarthneekhara

repo: dannycochran/windable


text:
Break the loop after a timeout

Example
const iterator = forEmitOf(readStream, {
    timeout: 1000, // ms
});

for await (const chunk of iterator) {
    console.log(chunk);
}

After 1000ms iterator will break.

I want to contribute with this one!
How do you want it to behave?
Did you though that the iterator should just end for it should throw an error if the timeout is reached?

I just made a PR that throws an error if the timeout is reached. I hope that is what you was expecting :)

authors: Farenheith danstarns

repo: danstarns/for-emit-of


text:
Investigating completion block not firing bug.

This is an investigation of #175 which is a bug report indicating that completion blocks are not always called.

With the code as it currently is, where there is a condition attached to the operation which fails - the test fails. Approximately 0.2% of the operations do not have their completion block executed after the operation finishes.
However, if the condition line is commented out, the test passes.

Okay, so there is still something going on here. Definitely a race condition. Test passes on Mac OS X, Fails on iOS, about 0.1% of operations do not have their state proceed past .Ready.
The state moves to .Ready however - the operation does not begin...

So, it's not a case of the evaluator not returning, as the state is set to .Ready - it's now just a case of the the KVO mechanisms not kicking in for some reason.

So... for example, if we set the severity to .Verbose.

Interation: 4590: Initialized -> Pending
Interation: 4589: Finishing -> Finished
Interation: 4590: Pending -> EvaluatingConditions
Interation: 4590: EvaluatingConditions -> Ready
Interation: 4591: Initialized -> Pending
Interation: 4590: Ready -> Finishing
Interation: 4591: Pending -> EvaluatingConditions
Interation: 4590: Did finish with no errors.
Interation: 4591: EvaluatingConditions -> Ready
Interation: 4590: Finishing -> Finished
Interation: 4592: Initialized -> Pending
Interation: 4592: Pending -> EvaluatingConditions
Interation: 4592: EvaluatingConditions -> Ready
Interation: 4593: Initialized -> Pending

Where iteration 4591 is the failed iteration. If we separate out the iterations:

Interation: 4591: Initialized -> Pending
Interation: 4591: Pending -> EvaluatingConditions
Interation: 4591: EvaluatingConditions -> Ready

And Iteration: 4591 does not progress further from here.

Interation: 4590: Initialized -> Pending
Interation: 4590: Pending -> EvaluatingConditions
Interation: 4590: EvaluatingConditions -> Ready
Interation: 4590: Ready -> Finishing
Interation: 4590: Did finish with no errors.
Interation: 4590: Finishing -> Finished

So, the question is.... why would stop the KVO from kicking in?

Current coverage is 74.31%

Merging #180 into development will increase coverage by +0.02% as of 765feca

@@            development    #180   diff @@
===========================================
  Files                51      51
  Stmts              3240    3232     -8
  Branches              0       0
  Methods               0
===========================================
- Hit                2407    2402     -5
  Partial               0       0
+ Missed              833     830     -3

Review entire Coverage Diff as of 765feca

Powered by Codecov. Updated on successful CI builds.

And yet sometimes.... it works.
@ansf, @jshier have you got any thoughts on this? I'm running out of ideas here.
Something that I have done, but didn't commit, was actually to also wrap up all the internal state (like, the conditions, observers, logger, cancelled flag, etc) in Operation in to a many-readers-one-writer thread safe structure. However, this actually caused way more problems and still didn't solve this original issue.

Considering the same works fine on OS X it seems like an underlying KVO issue to me. Is KVO compliance necessary for triggering underlying NSOperation functionality? If not I'd almost say KVO isn't worth it. Could you clarify exactly how KVO is involved in this issue?

NSOperation uses KVO to manage the state of itself and I expect to perform dependency management across queues.
We register "State" as the key path which affects "isReady" which is the key path observed by NSOperation for when it becomes ready to execute. When this changes (to true), NSOperation invokes start(). I guess the next thing which I can try to check is, what happens inside our ready override for this non-progressing operation instance. I guess ultimately, if there is a bug in Operation it would be there. However, I suspect more than likely this is an artifact of KVO when working with this number of objects - 5000 is quite a lot of operations to add to a queue.
@davedelong - can you offer any insight into this?

I added more logging to see what is happening inside an operation which fails. After we set state = .Ready, it then checks ready and we correctly return true as the result of super.ready || cancelled. However, what should happen is then start(), main(), finish() - but instead nothing happens.
And just to clarify, without adding the condition, running 5000 iterations works okay. Performing the same test using NSOperation and NSOperation queue works okay up to around 7500 iterations - but beyond that things start to go off the rails, either with unfulfilled expectations or just stalling on the main thread.
So, in conclusion, I feel that this is mostly just reaching the limits to KVO, and I'm reluctant to spend any more time on it.
This issues was initially raised by @bastianschilbe, so will wait wait now to hear back from him.

I don't have any additional suggestions, aside from using something like Hopper to debug into the system frameworks on iOS. I do want to add, though, that I think I've run into this issue, where some network operation in my app fails to finish because it gets stuck like this.
A related question is, does this issue change in frequency depending on the iOS hardware it's being run on?

Thanks for the feedback @jshier. Good questions - I've run the tests on a range of Mac hardware - haven't noticed a discernible difference, although on my 12" MacBook it's far more likely that the tests fail because the main thread stalls.
I think possible another thing to look into, is to write an example app which does something similar (but not a unit test) and then run it on some iOS hardware to see if this is an issue which only presents in the iOS simulator. I get the sense that it's less likely to occur in the Mac test target than the iOS one - but can't say so definitely.
And again, I'm a little bit reluctant to sweep the whole thing under the carpet as I'm pretty sure this issue can present itself with "normal" usage. I don't really see that running tight loops adding 5,000 or 10,000 operations to a queue as being normal.
Having said all of that.... if this is an issue with NSOperation or KVO, then I feel that it's largely out of my hands. I might as well begin work on v3.0 which breaks the inheritance from NSOperation and goes "pure Swift".

@ansf and me are rather clueless regarding this one, too :( We've tested several scenarios and only observe missing completion callbacks when we introduced KVO with an additional state variable. Couldn't find a way to fix this so far. We totally agree that 5000+ operations is not a default use case, but can confirm that it seems to fail more often when URLOperations are involved... somehow.
We put all our hope in the next version in "pure Swift"

I changed the original reproducer to use a fresh OperationQueue in each iteration. This still triggers a wait timeout, often within a few hundred iterations:
    func test__multiple_operations_completion_blocks() {
        continueAfterFailure = false

        (0...500000).forEach { i in
            let q = OperationQueue()
            q.maxConcurrentOperationCount = 1

            let e = expectationWithDescription("wait\(i)")
            let operation = BlockOperation()
            operation.addObserver(FinishedObserver { _, _ in e.fulfill() })

            let condition = BlockCondition { false }
            operation.addCondition(condition)
            q.addOperation(operation)

            waitForExpectationsWithTimeout(10, handler: nil)
        }
    }

I think we should continue to investigate this issue.
As an aside, I also saw this test failing on the MacOs scheme, but it took several 100k iterations to trigger the bug.

You have the waitForExpectations inside the loop? Is that right?

Yes, basically I wanted to test if I can trigger the issue with one OperationQueue and one Operation.
The loop is just there to execute this test many times in sequence.

@ansf @bastianschilbe @jshier okay, so definitely still looking into this, but for now, I'm going to merge this PR as there are some fixes in here which I don't want to go stale.
The original bug report #175 is still open, and can track progress, or until another PR is created.
My thinking is that other than bug fixing, I probably won't be adding any new "features" to the version 2.0 line in this project, and I'll probably start work afresh on an pure Swift implementation with Operation as a base class in the near future.

@davedelong @smileyborg I apologize for spamming, but I naively hope that maybe somebody from Apple could take a look at what's going on in NSOperation?

@pronebird Please file a radar if you think there's an Apple bug. If you can also include a minimal sample project that clearly reproduces the issue, it is much more likely to get prompt attention.
I know you have good intentions, but tagging random Apple folks on GitHub isn't going to help if you haven't filed a bug report; it's a huge company and issues will only get properly screened, routed, & fixed if they are in our bug tracking system (Radar).
Thanks!

authors: ansf bastianschilbe codecov-io danthorpe jshier pronebird smileyborg

repo: danthorpe/Operations


text:
Questions about how the reward is used and how imitation learning is used in your paper

Dear Authors,
After reading your paper, I have a  question about how imitation learning is used in your paper. In your code (https://github.com/daochenzha/rapid/blob/HEAD/rapid/agent.py#L153), I found at the end of each episode, the agent's policy will be updated with imitation learning by using the good episodes. In https://github.com/daochenzha/rapid/blob/HEAD/rapid/agent.py#L272, the agent's model will be updated with RL. Is my understanding right? By the way, is imitation learning necessary and important for the improvement of the rewards?
In Line 8, Algorithm 1, Give score S_{\tau} to all the state-action pairs in  \tau and store them into the buffer. Does it mean in this sparse reward setting, each timestep of this episode will be reassigned an identical reward?

@GoingMyWay Thanks for reading our paper!
Yes. Your understanding is correct. The imitation part is very important. If you try --disable_rapid, which will disable imitation learning, the performance will be very bad.
Yes, the same score will be assigned to all the state-action pairs in \tau. The score is given in the episode level to quantify the overall exploration behavior and we assume all the state-action pairs contribute equally. It is possible to achieve better performance if up-weighting some important state-action pairs (but I have not tried).

@GoingMyWay Thanks for reading our paper!
Yes. Your understanding is correct. The imitation part is very important. If you try --disable_rapid, which will disable imitation learning, the performance will be very bad.
Yes, the same score will be assigned to all the state-action pairs in \tau. The score is given in the episode level to quantify the overall exploration behavior and we assume all the state-action pairs contribute equally. It is possible to achieve better performance if up-weighting some important state-action pairs (but I have not tried).

Thanks. Your answer enhanced my understanding.

authors: GoingMyWay daochenzha

repo: daochenzha/rapid


text:
Remove deprecated dependencies

github.com/pkg/errors is deprecated in favor of the standard library
go.uber.org/multierr was used once and it's now part of the standard library in Go 1.20

Looks like the CI is failing due to the Go version used by GH Action being < 1.21.3

maybe we should set check-latest: true in the setup-go action configuration to force that action to skip the cache

authors: ItalyPaleAle lburgazzoli

repo: dapr-sandbox/dapr-kubernetes-operator


text:
Update E2E tests to build and use dapr/dapr from source code

Describe the proposal
The Dapr CLI E2E tests are intended to tests the execution of dapr CLI commands and their effects.
For example dapr init installs a particular version of dapr and that is what the E2E tests verify.
An interesting scenario that is also there is when a new flag is added to daprd, that needs to be added to the CLI dapr run also.
In this case the E2E tests for dapr run will fail since it uses a daprd binary which is the previously released stable version of Dapr. In that case dapr run tries to pass the flag onto to daprd in the E2E test and it fails with the error flag provided but not defined
Example: flag provided but not defined: -api-log-level
See error
But for testing dapr init flow, we still need to test only if the stable version of daprd and dashboard are downloaded and installed.
But for the command like dapr run, argument can be made that it needs to be tested with the latest built code from dapr/dapr master. Similar arguments can be made for dapr dashboard and such. Otherwise contributors would have to wait for the stable release of the enhancement made in dapr/dapr to be in stable release phase for it to be echoed in CLI. This is with respect to only commands and arguments that are proxied over to daprd or dashboard.
A solution would be to have the current E2E tests for dapr init as such and once that is done for any further commands, get the source code for dapr/dapr and build and use the binary from that. (Similar to how a DAPR_REF is specified for Java_SDK as an override to build and use the specified commit). In the CLI E2E tests, we would need to have the binary built. Complete dapr init test and verify; once that is done replace the installed daprd binary within ~/.dapr/bin with the built from source edge binary and run the tests for the other commands on that. This is for the self hosted scenarios.
@yaron2 @artursouza Any thoughts on this?
Release Note

RELEASE NOTE:

Have two separate flows for testing with stable version as well as with built from master. Thoughts?

@mukundansundar Have two separate flows for testing with stable version as well as with built from master. Thoughts?

That can be tested for certain commands like dapr run, dapr publish, dapr invoke etc. But certain commands like dapr init, dapr upgrade only need to be tested with the latest stable release/ RC releases during release endgame.

@artursouza @yaron2 thoughts on this?

authors: mukundansundar pravinpushkar

repo: dapr/cli


text:
May 3rd, Community Meeting Agenda

Dapr Community Meetings
Every two weeks we host a community meeting to showcase new features, review upcoming milestones, and engage in Q&A with the Dapr community - all are welcome, and we encourage participation.
The purpose of this thread is to form a discussion amongst the Dapr community on potential topics to highlight during the meeting. If you have a topic you wish to present or learn more about, please comment and be sure to include your name and a short description of the topic.
The conversations in this thread will directly influence the meeting agenda for the community call on May 3rd, at 9:00 PST. The meeting agenda is finalized by a Community Call Host prior to the meeting.
Thank you and we look forward to hearing your input.

Completed

repo: dapr/community


text:
Documentation / samples for additional consistency levels with Cosmos Db

Provide samples and documentation on how to support additional consistency levels within Dapr for Cosmos Db
https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

@sowsan - Dapr provides concurrency and consistency flags. Are there scenarios that you cannot do with these Dapr settings? Can you provide some details here?

authors: msfussell sowsan

repo: dapr/components-contrib


text:
Fixed issue preventing authentication fallback to MSI

Description
Wrong condition was preventing the Key Vault secret store to fallback to MSI authentication when needed.
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ x] Code compiles correctly
[ x] Created/updated tests
[ ] Extended the documentation

Hi @shalabhms, @yaron2 I was testing edge builds in a k8s cluster to add the docs requested in #185 and the key vault secret store was not falling back to MSI cause of a wrong if statement. This PR fixes that.

@cmendible Thanks for your contribution!

authors: cmendible youngbupark


text:
Measure publish time E2E tests.

Description
Measure and log publish time in for pubsub grpc test.
Output as follows:
2021/09/07 19:44:27 Connecting to dapr using url 127.0.0.1:50001
2021/09/07 19:44:27 Dial elapsed: 510.2µs
2021/09/07 19:44:27 NewDaprClient elapsed: 0s
2021/09/07 19:44:27 PublishEvent elapsed: 837.6µs
2021/09/07 19:44:27 Publish succeeded
2021/09/07 19:44:27 performPublish() called
2021/09/07 19:44:27     commandBody.ContentType=application/json
2021/09/07 19:44:27     commandBody.Topic=pubsub-raw-topic-grpc
2021/09/07 19:44:27     commandBody.Data=message-grpc-103
2021/09/07 19:44:27     commandBody.Protocol=grpc
2021/09/07 19:44:27     commandBody.Metadata=map[rawPayload:true]

Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test

/ok-to-test

repo: dapr/dapr


text:
Document no default content-type feature flag

Signed-off-by: Bernd Verst 4535280+berndverst@users.noreply.github.com
Thank you for helping make the Dapr documentation better!
This documents https://github.com/dapr/dapr/pull/4491

@berndverst - See my suggested edits above.

authors: berndverst msfussell

repo: dapr/docs


text:
Add docs for using Dev Container feature

Updated the documentation for using Dev Containers:

Recommend using the new Dev Container Feature that works with every stack. https://github.com/dapr/cli/pull/1233
Fixed some wording and branding ("Remote Containers" has been rebranded to "Dev Containers")

@ItalyPaleAle - I'm not sure why, but https://containers.dev/features/ gives a 404. https://containers.dev/features (without the trailing slash) works

👋 bot

authors: ItalyPaleAle stuartleeks


text:
Fix 787

Signed-off-by: Matej Nedic matejnedic1@gmail.com
Description
Introduce non blocking calls
Issue reference
Fix #787
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation

Fixed checkstyle issues.

repo: dapr/java-sdk


text:
feat: add Routes and Rules support through Subscription API spec v2

Describe the proposal
Dapr upgraded the Subscription API spec to v2
https://github.com/dapr/dapr/blob/master/pkg/apis/subscriptions/v2alpha1/types.go#L36
It is backwards compatible, so we should support v2

Will be part of #321

Note: this require an API change as we are moving away from a singular route to a rules based route.
https://docs.dapr.io/developing-applications/building-blocks/pubsub/howto-route-messages/
The above will now require us to return:
{
    'pubsubname': 'pubsub',
    'topic': 'inventory',
    'routes': {
      'rules': [
        {
          'match': 'event.type == "widget"',
          'path': '/widgets'
        },
        {
          'match': 'event.type == "gadget"',
          'path': '/gadgets'
        },
      ],
      'default': '/products'
 }

while in the JS SDK we use:
  await server.pubsub.subscribe(pubSubName, "topic-1", async (data: any) => console.log(`[topic-1] ${JSON.stringify(data)}`));
  await server.pubsub.subscribe(pubSubName, "topic-2", async (data: any) => console.log(`[topic-2] ${JSON.stringify(data)}`));

The subscribe events are to subscribe on the topics. While with Dapr we can subscribe on topics and sub events (or paths) that will be called. So that when we subscribe on topic-1 we can split this in item-type-1 and item-type-2 or item-type-deadletter
An option could be to return a "multi-callback" where we return multiple callbacks based on the amount of "rules" but this would make it harder to hook into it.
Another option which is being proposed for this change is to add the server.pubsub.onEvent(path:string) and server.pubsub.listRoutes() methods.

server.pubsub.onEvent(path:string): Create a listener that receives events for the given path. These paths are set through the route option in the subscribe method and default to pubSubName-topicName-default else we will use pubSubName-topicName-routeName to prevent HTTP Server collisions. It will throw an error if the provided path does not exist and is not receiving events.
server.pubsub.listRoutes(): This will list all the different paths that are created and which are receiving events

repo: dapr/js-sdk


text:
Training stuck at 40% on epoch one

Hi,
I am running the training of Boat example on a 12G RTX3060LHR which is a rather low end card compare to the hardware the model been tested with.
I managed to run training without dump core but the it stuck at around 40% at epoch 1 without improvement.
Setting i tried:
Inner batch size : 4 or 8
Batch size: 2
Train crop size: 256 or 128

Does the problem still persists with the latest patches?

authors: darglein hammerchu

repo: darglein/ADOP


text:
Add contents from "Exam Block #4: Functions and Exceptions"

Go to PCEP-30-02 Practice Test Compendium at edube.org
Copy and paste contents from "Exam Block #4: Functions and Exceptions" to GitBook

Complete


text:
Add status messages in Cornish

Status messages and tests added.

This looks great, we'll get it in right away. Thanks so much!

authors: ironwallaby steronydh

repo: darkskyapp/translations


text:
pgbouncer parsing does not work from STDIN

Testes on the master branch commit  2a99d51d149d3aa82dcc598ce1e49847b993e443:
Parsing file works like a charm (pgBouncer pgbouncer-1.12.0-1.rhel7.x86_64 - format pgbopuncer3 correctly detected):
zelenya@alesnbbs:~/var/pgBadger$ pgbadger/pgbadger -O /home/zelenya/var/pgBadger/rep -v pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz
DEBUG: pgBadger version 11.8.
DEBUG: Output 'html' reports will be written to out.html
DEBUG: Looking for file size using command: gunzip -l "pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz" | grep -E '^\s*[0-9]+' | awk '{print $2}'
DEBUG: Starting progressbar writer process
DEBUG: Compressed log file, will use command: gunzip -c "pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz"
DEBUG: Autodetected log format 'pgbouncer3' from pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz
DEBUG: pgBadger will use log format pgbouncer3 to parse pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz.
DEBUG: timezone not specified, using -7200 seconds
DEBUG: Processing log file: pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz
DEBUG: Compressed log file, will use command: gunzip -c "pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz"
DEBUG: Starting reading file "pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz"...
DEBUG: Start parsing pgbouncer log at offset 0 of file pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz to 101713701
DEBUG: Unknown pgbouncer line format: 2022-08-15 03:25:01.933 CEST [1078] LOG got SIGHUP, re-reading config
[========================>] Parsed 101713701 bytes of 101713701 (100.00%), stats: -45706, events: 0
DEBUG: the log statistics gathering took:13 wallclock secs ( 0.21 usr  0.03 sys + 12.54 cusr  0.26 csys = 13.04 CPU)
DEBUG: Output 'html' reports will be written to out.html
LOG: Ok, generating html report...
DEBUG: building reports took:  0 wallclock secs ( 0.38 usr +  0.00 sys =  0.38 CPU)
DEBUG: the total execution time took: 13 wallclock secs ( 0.59 usr  0.03 sys + 12.54 cusr  0.26 csys = 13.42 CPU)

From STDIN with specified format option, it reports "queries" instead of "stats" and nothing is parsed:
zelenya@alesnbbs:~/var/pgBadger$ gzip -dc pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz | pgbadger/pgbadger --format pgbadger3 -O /home/zelenya/var/pgBadger/rep -v -
DEBUG: pgBadger version 11.8.
DEBUG: Output 'html' reports will be written to out.html
DEBUG: Can not autodetect log format, assuming pgbadger3.
DEBUG: timezone not specified, using -7200 seconds
DEBUG: Starting progressbar writer process
DEBUG: Processing log file: -
DEBUG: Starting reading file "-"...
DEBUG: Start parsing postgresql log at offset 0 of file "-" to -1
[+] Parsed 101713701 bytes, queries: 0, events: 0
DEBUG: the log statistics gathering took: 2 wallclock secs ( 0.00 usr  0.00 sys +  0.88 cusr  0.01 csys =  0.89 CPU)
DEBUG: Output 'html' reports will be written to out.html
LOG: Ok, generating html report...
DEBUG: building reports took:  0 wallclock secs ( 0.00 usr +  0.01 sys =  0.01 CPU)
DEBUG: the total execution time took:  2 wallclock secs ( 0.00 usr  0.01 sys +  0.88 cusr  0.01 csys =  0.90 CPU)

STDIN with autodetect behaves similar way except it assumes the format is stderr:
zelenya@alesnbbs:~/var/pgBadger$ gzip -dc pgb_work/pgb.172.25.0.231.pgbouncer.log.7.gz | pgbadger/pgbadger -O /home/zelenya/var/pgBadger/rep -v -
DEBUG: pgBadger version 11.8.
DEBUG: Output 'html' reports will be written to out.html
DEBUG: Can not autodetect log format, assuming stderr.
DEBUG: timezone not specified, using -7200 seconds
DEBUG: Starting progressbar writer process
DEBUG: Processing log file: -
DEBUG: Starting reading file "-"...
DEBUG: Start parsing postgresql log at offset 0 of file "-" to -1
[+] Parsed 101713701 bytes, queries: 0, events: 0
DEBUG: the log statistics gathering took: 7 wallclock secs ( 0.00 usr  0.01 sys +  5.29 cusr  0.04 csys =  5.34 CPU)
DEBUG: Output 'html' reports will be written to out.html
LOG: Ok, generating html report...
DEBUG: building reports took:  0 wallclock secs ( 0.00 usr +  0.00 sys =  0.00 CPU)
DEBUG: the total execution time took:  7 wallclock secs ( 0.00 usr  0.01 sys +  5.29 cusr  0.04 csys =  5.34 CPU)

In your second example there is a type, you use --format pgbadger3 how about if you use  --format pgbouncer3?

Oh, sorry for the mistake, with an explicitly defined format it works even from pipe:
zelenya@alesnbbs:~/var/pgBadger$ gzip -dc pgb_work/pgb.172.25.0.231.pgbouncer.log.1.gz | pgbadger/pgbadger --format pgbouncer3 -v -
DEBUG: pgBadger version 11.8.
DEBUG: Output 'html' reports will be written to out.html
DEBUG: Can not autodetect log format, assuming pgbouncer3.
DEBUG: Starting progressbar writer process
DEBUG: timezone not specified, using -7200 seconds
DEBUG: Processing log file: -
DEBUG: Starting reading file "-"...
DEBUG: Start parsing pgbouncer log at offset 0 of file - to -1
DEBUG: Unknown pgbouncer line format: 2022-08-22 03:33:01.802 CEST [1078] LOG got SIGHUP, re-reading config
DEBUG: Unknown pgbouncer line format: 2022-08-22 14:39:46.619 CEST [1078] LOG got SIGINT, shutting down
DEBUG: Unknown pgbouncer line format: 2022-08-22 14:44:46.713 CEST [10253] LOG listening on 0.0.0.0:5432
DEBUG: Unknown pgbouncer line format: 2022-08-22 14:44:46.713 CEST [10253] LOG listening on unix:/tmp/.s.PGSQL.5432
[+] Parsed 253080038 bytes, stats: 986976, events: 14082
DEBUG: the log statistics gathering took:30 wallclock secs ( 0.20 usr  0.01 sys + 28.78 cusr  0.12 csys = 29.11 CPU)
DEBUG: Output 'html' reports will be written to out.html
LOG: Ok, generating html report...
DEBUG: building reports took:  0 wallclock secs ( 0.37 usr +  0.01 sys =  0.38 CPU)
DEBUG: the total execution time took: 30 wallclock secs ( 0.57 usr  0.02 sys + 28.78 cusr  0.12 csys = 29.49 CPU)

I spot a difference between default parsing - like the above and incremental - STATS counter shows negative numbers in the incremental mode, but the report is created:
zelenya@alesnbbs:~/var/pgBadger$ gzip -dc pgb_work/pgb.172.25.0.231.pgbouncer.log.1.gz | pgbadger/pgbadger --format pgbouncer3 -I -O /home/zelenya/var/pgBadger/rep -v -
DEBUG: pgBadger version 11.8.
DEBUG: Output 'html' reports will be written to out.html
DEBUG: waiting for log entries from stdin.
DEBUG: Can not autodetect log format, assuming pgbouncer3.
DEBUG: timezone not specified, using -7200 seconds
DEBUG: Starting progressbar writer process
DEBUG: Processing log file: -
DEBUG: Starting reading file "-"...
DEBUG: Start parsing pgbouncer log at offset 0 of file - to -1
DEBUG: Unknown pgbouncer line format: 2022-08-22 03:33:01.802 CEST [1078] LOG got SIGHUP, re-reading config
DEBUG: Unknown pgbouncer line format: 2022-08-22 14:39:46.619 CEST [1078] LOG got SIGINT, shutting down
DEBUG: Unknown pgbouncer line format: 2022-08-22 14:44:46.713 CEST [10253] LOG listening on 0.0.0.0:5432
DEBUG: Unknown pgbouncer line format: 2022-08-22 14:44:46.713 CEST [10253] LOG listening on unix:/tmp/.s.PGSQL.5432
DEBUG: Saving pgbouncer last parsed line into /tmp/tmp_LAST_PARSED (2022-08-23 03:22:01	253080038)
DEBUG: Reading temporary last parsed line from /tmp/tmp_LAST_PARSED

DEBUG: Saving last parsed line into /home/zelenya/var/pgBadger/rep/LAST_PARSED
DEBUG: the log statistics gathering took:34 wallclock secs ( 0.01 usr  0.00 sys + 32.41 cusr  0.17 csys = 32.59 CPU)
DEBUG: Building incremental report for 2022-08-22
LOG: Ok, generating HTML daily report into /home/zelenya/var/pgBadger/rep/2022/08/22/...
DEBUG: Building incremental report for 2022-08-23
LOG: Ok, generating HTML daily report into /home/zelenya/var/pgBadger/rep/2022/08/23/...
LOG: Ok, generating HTML weekly report into /home/zelenya/var/pgBadger/rep/2022/week-35/...
LOG: Ok, generating global index to access incremental reports...
DEBUG: writing global index into /home/zelenya/var/pgBadger/rep/index.html
DEBUG: building reports took:  1 wallclock secs ( 1.18 usr +  0.02 sys =  1.20 CPU)
DEBUG: the total execution time took: 35 wallclock secs ( 1.19 usr  0.02 sys + 32.41 cusr  0.17 csys = 33.79 CPU)

So the problem is only in autodetect pgnouncer3 (haven't tested other formats) log format from a pipe.
BTW, it might help to add some note to the readme option --format logtype description that there are more pgbouncer formats (2, 3), since when the default is used it fails (but in can be found in the code):
zelenya@alesnbbs:~/var/pgBadger$ gzip -dc pgb_work/pgb.172.25.0.231.pgbouncer.log.1.gz | pgbadger/pgbadger --format pgbouncer -I -O /home/zelenya/var/pgBadger/rep -v - |& head -20
DEBUG: pgBadger version 11.8.
DEBUG: Output 'html' reports will be written to out.html
DEBUG: Found log offset 253080038 in file /home/zelenya/var/pgBadger/rep/LAST_PARSED
DEBUG: waiting for log entries from stdin.
DEBUG: Can not autodetect log format, assuming pgbouncer.
DEBUG: timezone not specified, using -7200 seconds
DEBUG: Starting progressbar writer process
DEBUG: Processing log file: -
DEBUG: Starting reading file "-"...
DEBUG: Start parsing pgbouncer log at offset 0 of file - to -1
DEBUG: Unknown pgbouncer line format: 2022-08-22 03:33:01.802 CEST [1078] LOG got SIGHUP, re-reading config
DEBUG: Unknown pgbouncer line format: 2022-08-22 03:33:02.022 CEST [1078] LOG C-0x213c258: XXX/YYY@172.25.0.139:52336 login attempt: db=....
DEBUG: Unknown pgbouncer line format: 2022-08-22 03:33:02.027 CEST [1078] LOG C-0x2164438: XXX/YYY@172.25.0.139:52338 login attempt: db=....

Kind regards Ales Zeleny

Commit 186679d fixes the negative value when parsing pgbouncer file. I have decide to not talk about pgbouncer2 or pgbouncer3 logformat in the doc because they are internal. I should review the way pgbadger can autodetect the real format even if pgbouncer format is chosen.

authors: aleszeleny darold

repo: darold/pgbadger

license: PostgreSQL


text:
Removed include unistd.h

See PR #63 for context

Coverage decreased (-0.03%) to 96.257% when pulling 4c15ef7e75680481e2ab878191a24f1e67456509 on no-unistd-h into fa406eec86fc13c840abb3461e7189254e2cc488 on master.

authors: coveralls darrenldl

repo: darrenldl/reed-solomon-erasure


text:
Versions

Nice little library. Could you possibly create a stable version branch rather than just "master".

Thanks! I'm using tags instead of branches for stable versions - the latest stable version is 2.0.2 which can be installed via composer with composer require "darsyn/ip:^2.0".

authors: twifty zanderbaldwin

repo: darsyn/ip


text:
Clarify which docs people should look at

The README should clearly point people to the docs at angular.io/dart.
Also, we should clarify everywhere people might end up when looking for these docs. E.g., when you go to https://pub.dartlang.org/packages/angular2, you see the following links:

(everything from the README)
Homepage: github.com/dart-lang/angular2
we can change this in angular2's pubspec with the homepage field
Documentation: www.dartdocs.org/documentation/angular2/2.0.0-beta.21/ (which, fortunately, now points to https://angular.io/docs/dart/latest/api/, but that itself could have a more helpful intro)
we can change this in angular2's pubspec by adding a documentation: field

I'm creating an internal CL for the pubspec.yaml changes.

CL submitted. Not sure when it'll be reflected in this repo.


text:
Using Colors.black as a primarySwatch causes an opaque error

Using Colors.black as a primarySwatch causes an opaque error

open https://dartpad.dev/b6409e10de32b280b8938aa75364fa7b
change primarySwatch from Colors.blue to Colors.black
click Run
Observe the app stops working without analysis errors or console output

Here's the error in the javascript console:
Uncaught Error: Assertion failed: file:///Users/brettmorgan/Documents/GitHub/dart-services/flutter/packages/flutter/lib/src/widgets/framework.dart:2687:20
_debugCurrentBuildTarget == context
is not true
    at Object.throw_ [as throw] (storage.googleapis.com/compilation_artifacts/2.10.0/dart_sdk.js:4328)
    at Object.assertFailed (storage.googleapis.com/compilation_artifacts/2.10.0/dart_sdk.js:4275)
    at storage.googleapis.com/compilation_artifacts/2.10.0/flutter_web.js:318195
    at framework.BuildOwner.new.buildScope (storage.googleapis.com/compilation_artifacts/2.10.0/flutter_web.js:318199)
    at RenderObjectToWidgetAdapter.new.attachToRenderTree (storage.googleapis.com/compilation_artifacts/2.10.0/flutter_web.js:306959)
    at binding$.WidgetsFlutterBinding.new.attachRootWidget (storage.googleapis.com/compilation_artifacts/2.10.0/flutter_web.js:306827)
    at storage.googleapis.com/compilation_artifacts/2.10.0/flutter_web.js:306822
    at internalCallback (storage.googleapis.com/compilation_artifacts/2.10.0/dart_sdk.js:23761)

Related to https://github.com/dart-lang/dart-pad/issues/1649

I'm curious why this code doesn't throw a type error during analysis. primarySwatch is typed as MaterialColor and Colors.black is typed as a Color.
Anyways,

As of Flutter 1.25 this is much less of an issue. The analyzer issues an error.

As of Flutter 1.25 this is much less of an issue. The analyzer issues an error.

Type checking FTW. Now I'm thinking that the problem is with printing assertion failures:
import 'package:flutter/material.dart';
void main() {
  assert(1 == 2);
}

This prints an error in the javascript console, but not the DartPad console.

Type checking FTW. Now I'm thinking that the problem is with printing assertion failures:
import 'package:flutter/material.dart';
void main() {
  assert(1 == 2);
}

This prints an error in the javascript console, but not the DartPad console.

One of the areas of tech debt we really need to address is error reporting in general. If this can be bundled into some of the DartPad work we've already talked about in the next few months (by you or anyone else), it'd be worth the investment.

One of the areas of tech debt we really need to address is error reporting in general. If this can be bundled into some of the DartPad work we've already talked about in the next few months (by you or anyone else), it'd be worth the investment.

Another case where this shows up:
import 'package:flutter/material.dart';

void main() {
  runApp(const ListViewApp());
}

class ListViewApp extends StatelessWidget {
  static const itemCount = 10;
  const ListViewApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(),
        body: ListView.builder(
          // itemCount: itemCount, // uncomment to fix!
          itemBuilder: (context, idx) {
            assert(idx < itemCount);
            return ListTile(
              title: Text('$idx'),
            );
          },
        ),
      ),
    );
  }
}

We should be displaying something more user-friendly instead of crashing. Running locally shows a red widget of death:

but in DartPad we get a stack trace in the JavaScript console and Script error. in the DartPad console:
Uncaught Error: Assertion failed: file:///Users/brettmorgan/Documents/GitHub/dart-services/flutter-sdk/packages/flutter/lib/src/rendering/object.dart:1532:12
_debugCanPerformMutations
is not true
    at Object.throw_ [as throw] (dart_sdk.js:5037)
    at Object.assertFailed (dart_sdk.js:4976)
    at view.RenderView.new.markNeedsLayout (flutter_web.js:195881)
    at view.RenderView.new.set configuration [as configuration] (flutter_web.js:442310)
    at binding$.WidgetsFlutterBinding.new.handleMetricsChanged (flutter_web.js:327613)
    at binding$.WidgetsFlutterBinding.new.handleMetricsChanged (flutter_web.js:325887)
    at Object.invoke (dart_sdk.js:175219)
    at _engine.EnginePlatformDispatcher.__.invokeOnMetricsChanged (dart_sdk.js:156971)
    at _engine.DomRenderer.new.[_metricsDidChange] (dart_sdk.js:140844)
    at Object._checkAndCall (dart_sdk.js:5242)
    at Object.dcall (dart_sdk.js:5247)
    at VisualViewport.<anonymous> (dart_sdk.js:100617)

Tracking this issue here: https://github.com/dart-lang/dart-pad/issues/1650

authors: RedBrogdon domesticmouse johnpryan

repo: dart-lang/dart-pad


text:
List modification apis should edit the dart list when used from JS

Currently if you were to use a dart element from js, and then modify a property that was a list, the actual dart list would not get modified, even if you go through the proper list modification apis.
We could override the list apis on Polymer.Base to check if there is a corresponding dart list for the js list (there should be one under list.dartClass), and make the proper modifications there if so.

array-selector and some other elements do do this, so had to add this to 1.0. Fixed in 63c114462c7d54e0cbb28aac927afec599c31fb4

repo: dart-lang/polymer-dart


text:
document.querySelectorAll(":enabled") does not recognize elements of type "a" and "menuitem".

This issue was originally filed by alexe.kaigorodov@gmail.com

http://www.w3.org/html/wg/drafts/html/master/#pseudo-classes reads:
4.15.2 Pseudo-classes
:enabled
The :enabled pseudo-class must match any element falling into one of the following categories:
a elements that have an href attribute
area elements that have an href attribute
link elements that have an href attribute
button elements that are not disabled
input elements that are not disabled
select elements that are not disabled
textarea elements that are not disabled
optgroup elements that do not have a disabled attribute
option elements that are not disabled
menuitem elements that do not have a disabled attribute
fieldset elements that do not have a disabled attribute
However, call to document.querySelectorAll(":enabled") does not return elements of type "a" and "menuitem".

Bumped into this one due to an Exception with thrown value: Error: SyntaxError: DOM Exception 12 error related to querySelectorAll(":disabled"). See this issue is kind of old though and actually was wondering if this was not just querySelectorAll perhaps not being able to deal with HTML5..?

authors: DartBot jasperf

repo: dart-lang/sdk


text:
Please merge revision #e1c39602ba1ef866934f35d3d8a0ab7f8efa38e5 into dev channel

@whesse @mit-mit @kasperl
This fixes a bug in the status pages that can prevent users from providing us with debugging information.
e1c39602ba1ef866934f35d3d8a0ab7f8efa38e5

Merged to dev 426edff01629bb92ac8e88f27ae25404c35f769b

authors: bwilkerson dgrove


text:
Exception from analysis server (running from VSCode / Dart Code)

Exception from analysis server (running from VSCode / Dart Code)
What I was doing
Defining a function with an argument of type Map<String, bool Function(dynamic)>. (The exceptions appears to be due to the bool Function(dynamic).)
Versions

Dart SDK 1.24.2
Visual Studio Code 1.15.1
Dart Code 2.4.0

Analyzer Info
The analyzer was launched with the arguments:
--client-id=DanTup.dart-code
--client-version=2.4.0

Exception
Captured exception
NoSuchMethodError: The getter 'beginToken' was called on null.
Receiver: null
Tried calling: beginToken
#0      Driver._captureExceptions.<anonymous closure> (package:analysis_server/src/server/driver.dart:502)
#1      _CustomZone.handleUncaughtError (dart:async/zone.dart:981)
#2      _Future._propagateToListeners (dart:async/future_impl.dart:552)
#3      _Future._completeError (dart:async/future_impl.dart:486)
#4      _SyncCompleter._completeError (dart:async/future_impl.dart:55)
#5      _Completer.completeError (dart:async/future_impl.dart:27)
#6      AnalysisDriver.performWork (package:analyzer/src/dart/analysis/driver.dart:909)
#7      new Future.microtask.<anonymous closure> (dart:async/future.dart:184)
#8      _rootRun (dart:async/zone.dart:1116)
#9      _CustomZone.run (dart:async/zone.dart:1001)
#10     _CustomZone.runGuarded (dart:async/zone.dart:901)
#11     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:926)
#12     _rootRun (dart:async/zone.dart:1120)
#13     _CustomZone.run (dart:async/zone.dart:1001)
#14     _CustomZone.runGuarded (dart:async/zone.dart:901)
#15     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:926)
#16     _microtaskLoop (dart:async/schedule_microtask.dart:41)
#17     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
#18     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:375)
#19     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:394)
#20     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:151)
<asynchronous suspension>
#21     AnalysisDriverScheduler.start (package:analyzer/src/dart/analysis/driver.dart:1481)
#22     new AnalysisServer (package:analysis_server/src/analysis_server.dart:458)
#23     SocketServer.createAnalysisServer (package:analysis_server/src/socket_server.dart:89)
#24     StdioAnalysisServer.serveStdio (package:analysis_server/src/server/stdio_server.dart:37)
#25     Driver.start.<anonymous closure> (package:analysis_server/src/server/driver.dart:474)
#26     _rootRun (dart:async/zone.dart:1120)
#27     _CustomZone.run (dart:async/zone.dart:1001)
#28     runZoned (dart:async/zone.dart:1467)
#29     Driver._captureExceptions (package:analysis_server/src/server/driver.dart:513)
#30     Driver.start (package:analysis_server/src/server/driver.dart:473)
#31     main (file:///b/build/slave/dart-sdk-mac-stable/build/sdk/pkg/analysis_server/bin/server.dart:12)
#32     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:263)
#33     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:151)

I believe that this has been fixed, but that the fix has not yet made it into a stable build. If you want to use the new function type syntax, I would recommend that you move to the latest 0.25.0 dev build.


text:
flutter_tester.exe exits when main is async

When I run windows-x64\flutter_tester.exe --non-interactive test2.dart it prints Started! and then exists. It does not exit and prints Tick! when I run darwin-x64/flutter_tester --non-interactive test2.dart. It also does not exist on Windows if I remove async from main.
C:\Users\scheglov\AppData\Local\Temp\flutterDesigner>flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel beta, v0.2.8, on Microsoft Windows [Version 6.1.7601], locale ru-RU)

import 'dart:async';

main() async {
  print('Started!');
  new Timer.periodic(new Duration(seconds: 1), (_) { print('Tick!'); });
}

I was able to reproduce a few weeks ago but it looks like this has been resolved since. Feel free to reopen if you run into the issue again.

authors: bkonyi scheglov


text:
Create new dir, move files to new dir -> error

Analyzer Feedback from IntelliJ
Version information

IDEA IU-192.6262.58
2.5.0-edge.06d3769ac6d775ede7ca87e6ba2f056db93e2e27
IU-192.6262.58, JRE 11.0.3+12-b304.39x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14.6, screens 2560x1440, 1680x1050  Retina

Exception
Dart analysis server, SDK version 2.5.0-edge.06d3769ac6d775ede7ca87e6ba2f056db93e2e27, server version 1.27.2, error: FileSystemException(path=/Users/sanekyy/Projects/terra/admin-flutter/lib/service/client.dart; message=Cannot open file)
#0      _PhysicalFile.readAsStringSync (package:analyzer/file_system/physical_file_system.dart:212:7)
#1      _OverlayFile.readAsStringSync (package:analyzer/file_system/overlay_file_system.dart:249:18)
#2      FileSource.contentsFromFile (package:analyzer/src/source/source_resource.dart:92:46)
#3      FileSource.contents.<anonymous closure> (package:analyzer/src/source/source_resource.dart:76:14)
#4      _PerformanceTagImpl.makeCurrentWhile (package:analyzer/src/generated/utilities_general.dart:258:15)
#5      FileSource.contents (package:analyzer/src/source/source_resource.dart:75:37)
#6      MoveFileRefactoringImpl._isPackageReference (package:analysis_server/src/services/refactoring/move_file.dart:182:43)
#7      MoveFileRefactoringImpl._computeNewUri (package:analysis_server/src/services/refactoring/move_file.dart:163:9)
#8      MoveFileRefactoringImpl.createChange.<anonymous closure> (package:analysis_server/src/services/refactoring/move_file.dart:149:25)
#9      ChangeBuilderImpl.addFileEdit (package:analyzer_plugin/src/utilities/change_builder/change_builder_core.dart:88:20)
<asynchronous suspension>
#10     MoveFileRefactoringImpl.createChange (package:analysis_server/src/services/refactoring/move_file.dart:148:27)
<asynchronous suspension>
#11     _RefactoringManager.getRefactoring.<anonymous closure> (package:analysis_server/src/edit/edit_domain.dart:1029:41)
<asynchronous suspension>
#12     _rootRun (dart:async/zone.dart:1124:13)
#13     _CustomZone.run (dart:async/zone.dart:1021:19)
#14     _runZoned (dart:async/zone.dart:1516:10)
#15     runZoned (dart:async/zone.dart:1500:12)
#16     _RefactoringManager.getRefactoring (package:analysis_server/src/edit/edit_domain.dart:985:5)
#17     EditDomainHandler._getRefactoring (package:analysis_server/src/edit/edit_domain.dart:863:24)
#18     EditDomainHandler.handleRequest (package:analysis_server/src/edit/edit_domain.dart:393:16)
#19     AnalysisServer.handleRequest.<anonymous closure>.<anonymous closure> (package:analysis_server/src/analysis_server.dart:332:45)
#20     _PerformanceTagImpl.makeCurrentWhile (package:analyzer/src/generated/utilities_general.dart:258:15)
#21     AnalysisServer.handleRequest.<anonymous closure> (package:analysis_server/src/analysis_server.dart:328:50)
#22     _rootRun (dart:async/zone.dart:1124:13)
#23     _CustomZone.run (dart:async/zone.dart:1021:19)
#24     _runZoned (dart:async/zone.dart:1516:10)
#25     runZoned (dart:async/zone.dart:1500:12)
#26     AnalysisServer.handleRequest (package:analysis_server/src/analysis_server.dart:327:5)
#27     ByteStreamServerChannel._readRequest.<anonymous closure> (package:analysis_server/src/channel/byte_stream_channel.dart:185:16)
#28     _PerformanceTagImpl.makeCurrentWhile (package:analyzer/src/generated/utilities_general.dart:258:15)
#29     ByteStreamServerChannel._readRequest (package:analysis_server/src/channel/byte_stream_channel.dart:175:47)
#30     ByteStreamServerChannel.listen.<anonymous closure> (package:analysis_server/src/channel/byte_stream_channel.dart:118:26)
#31     _rootRunUnary (dart:async/zone.dart:1132:38)
#32     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#33     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
#34     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#35     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
#36     _SinkTransformerStreamSubscription._add (dart:async/stream_transformers.dart:68:11)
#37     _EventSinkWrapper.add (dart:async/stream_transformers.dart:15:11)
#38     _StringAdapterSink.add (dart:convert/string_conversion.dart:236:11)
#39     _LineSplitterSink._addLines (dart:convert/line_splitter.dart:150:13)
#40     _LineSplitterSink.addSlice (dart:convert/line_splitter.dart:125:5)
#41     StringConversionSinkMixin.add (dart:convert/string_conversion.dart:163:5)
#42     _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:120:24)
#43     _rootRunUnary (dart:async/zone.dart:1132:38)
#44     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#45     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
#46     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#47     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
#48     _SinkTransformerStreamSubscription._add (dart:async/stream_transformers.dart:68:11)
#49     _EventSinkWrapper.add (dart:async/stream_transformers.dart:15:11)
#50     _StringAdapterSink.add (dart:convert/string_conversion.dart:236:11)
#51     _StringAdapterSink.addSlice (dart:convert/string_conversion.dart:241:7)
#52     _Utf8ConversionSink.addSlice (dart:convert/string_conversion.dart:312:20)
#53     _Utf8ConversionSink.add (dart:convert/string_conversion.dart:305:5)
#54     _ConverterStreamEventSink.add (dart:convert/chunked_conversion.dart:72:18)
#...

For additional log information, please append the contents of
file:///private/var/folders/hx/klmbwq7j3wx1kzz491c_dt_00000gp/T/report.txt.

Thanks for reporting this issue! It looks like this has been previously reported at #36204; please follow along there.

Duplicate of #36204

authors: sanekyy srawlins


text:
Insert signature stubs

When multiple inherited members meet in a class without an explicit overriding declaration, the most specific signature (if there is one) is chosen for the interface of the class. However, this choice is not embodied in the kernel.
Inserting an explicit abstract method ("signature stub") at these meeting points will have several benefits:

It is a cleaner, more explicit representation.
Code wanting to know the interface of a class becomes simpler, as it can always just search up the super chain for each member and take the first one it finds.
All instance calls have a well-defined, unique interface target.
Computing a good partitioning of methods into selectors for table dispatch becomes much easier, as it can just compute the connected components of override relationships.

Partitioning of table selectors for AOT has been implemented without relying on signature stubs. So feel free to not be constrained by this when designing the new method call representation.


text:
Expose WebSocket onPing and onPong and allow manually sending both

Hello,
Currently, the WebSocket implementation hides away the messages for both ping and pong.
I'm asking that you expose both so people who want to handle these messages manually can use the default library too.
Looking at the code, you can probably create an option so the user can either use the built-in ping/pong manager or bypass it and handle it in code.
Also, _WebSocketPong and _WebSocketPing need to be made public so the user can send these messages manually.
And you also would need to stop intercepting these types of messages so the user can receive them via the listen call, or even better, intercept and send it to a onPong and onPing callback.
Please consider this. not having this makes using the WebSocket class very frustrating to use for my case, and since other libraries that implement websocket uses Flutter channels, I cannot use them inside isolates so this class is my only option.

onPong and onPing callbacks would really help.

authors: diasnrg sezaru


text:
Kythe implementation for named arguments anywhere

See #47451 for the meta issue and dart-lang/language#1072 for the language issue.

FYI, the flag has been flipped so these can be used without a flag internally now.

@emmanuel-p do you have a status on this?

Basic support is implemented.
Some improvements are planned.
Tracked internally by b/225119276.
On Fri, 6 May 2022 at 03:42, Leaf Petersen @.***> wrote:

Reopened #47579 https://github.com/dart-lang/sdk/issues/47579.
—
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/47579#event-6560471325, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AK5LPCB46C3NTAK7QGTQQKTVIR2GRANCNFSM5HAE4X4A
.
You are receiving this because you were mentioned.Message ID:
@.***>

authors: devoncarew emmanuel-p leafpetersen


text:
LSP server doesn't provide/update diagnostics for fix_data.yaml or pubspec.yaml, nor report diagnostics for fix_data/**.yaml

Split from #52108.

[ ] In lib/fix_data.yaml, diagnostics are not updated as you type
[ ] In pubspec.yaml, diagnostics are not updated as you type
[x] In lib/fix_data/foo.yaml there are no diagnostics at all, even when saving
https://dart-review.googlesource.com/c/sdk/+/296801

Ah, good point. Shall we close this then now https://github.com/dart-lang/sdk/commit/bbacf39e9c1085650b5f2a180285792ad0dd76d9 has solved the other issue? Or keep it open as a future enhancement?
It's probably not a priority, but the current behaviour does feel a bit odd in VS Code (because it's not obvious this is what's happening).

Unless we think that we're going to (a) verify whether the behavior is reasonable and/or (b) improve the behavior of the parser, I don't think we're going to implemented analysis-as-you-type for YAML files. While it would be nice to have, supporting YAML files is never going to be as high a priority as supporting Dart files. But we can leave it open for community contributions.

authors: DanTup bwilkerson


text:
"/"-prefixed part files fails to compile but is fine in analyzer

// lib/fruits.dart
part '/src/fruits/apple.dart';

// lib/src/fruits/apple.dart
part of '../fruits.dart';

class Apple {}

// lib/main.dart
import '/fruits.dart';

void main() {
  Apple();
}

This program appears fine in the analyzer, but fails to compile (in the CFE?) citing that "Apple" cannot be found/resolved. It appears the CFE (?) doesn't resolve part files the same as the analyzer when using /-prefixed URIs.

@lrhn Doesn't / in the beginning of the path mean that the path is absolute? In which case the lookup shouldn't resolve to a Uri relative to the current Uri?

(The part of needs another .., so part of '../../fruits.dart';, to get out of both the fruits and src directories. That's not the problem, but it is one.)
A URI reference of /fruits.dart is an absolute path, but not an absolute URI. It has no authority and no scheme, so if resolved against another URI, it should still inherit those from the base.
That is, when resolved against a full base URI, for example http://example.com/banana/boat.dart, the relative URI reference /fruits.dart would/should give http://example.com/fruits.dart.
The rules for resolving against package: URIs is not as formally specified as I'd like, but I've implemented the canonical implementation in the Dart Uri class. The implementation if the Uri class should treat package URIs specially, and treat the package name as not part of the path when doing resolution. (But not when asking for uri.path, because that would be too breaking. I'd love to move the package name to be accessed through host instead, but too many things depend on the current behavior).
So with a base URI of package:my_package/banana/boat.dart, the /fruits.dart path should give package:my_package/fruits.dart.
That's if things work correctly, and the code actually uses the Uri class to do the resolution. (And the special behavior only works for valid package: URIs, a package: URI cannot have an authority part, the one with host-name, port etc., and cannot have an actual URI path which starts with /. If you create one, like Uri.parse('package://example.com/banana/boat.dart'), it will not be considered a valid package URI, and will not be subject to the special logic. I doubt that's what's happening here, but I'd have to see the URI being resolved against to be certain.)
The Uri class seems to work when I check it.
So is the front-end not using Uri to resolve URIs against the library's package: URI, or are they not using a package: URI to begin with, because they already resolved it to a file URI? (If you resolve /fruits.dart against a file:///some/long/file.dart URI, you get file:///fruits.dart which won't be correct.)
If I run dart lib/main.dart or dart run lib/main.dart, I get the error. The location of that error is:
lib/fruits.dart:2:6: Error: Error when reading '/src/fruits/apple.dart': No such file or directory
part '/src/fruits/apple.dart';
     ^

aka lib/fruits.dart, which looks like a relative path, not a package URI. That's suspicious.
(And it's defintely the front-end, using dart compile js doesn't change anything, so it's not, e.g., VM only.)(
The front end should, like the analyzer seems to do, and like the front-end itself does in some cases, see that lib/main.dart is actually a packge file (it's in the lib directory of a package of the current package configuration), and the file should therefore be identified by the URI package:fruits/main.dart.
It should not use the lib/main.dart file path from the command line when running files inside lib/.
We used to do that, and it the stream of issues asking "why doesn't this work correctly" was a clear sign that it didn't work. We changed the parser so that if your entry script file is inside lib/, we convert its URI to a package: URI before loading and parsing it. (But after finding the package resolution config file relative to the original file location.)
It's actually worse than that. The front end is not just using the wrong URI by accident, it's deliberately throwing the correct URI away, even if it has it.
Even if I specify the file using a package: URI, by first selecting the package resolution,
it still doesn't work:
$ dart --packages=.dart_tool/package_config.json package:fruits/main.dart
lib/fruits.dart:2:6: Error: Error when reading '/src/fruits/apple.dart': No such file or directory
part '/src/fruits/apple.dart';
     ^
...

It finds the lib/main.dart file, specified with a package:fruits/main.dart URI, then fails to resolve /src/fruits/apple.dart correctly against that URI (because if it did, it would find lib/src/fruits/apple.dart, which exists).
My bet is on not using Uri to do the resolution, and doing some shorthand for replacing the entire path when the part file URI starts with /. Or assuming that a "relative" URI (one with no scheme) can always be resolved realtive to the file: URI of the current library, instead of its canonical package: URI, just to save some steps.
Or something.
In any case, it's wrong, and should be fixed.
Also see: https://github.com/dart-lang/sdk/issues/44151
I think we still have unified our treatment of input script paths.

@johnniwinther Thanks for fixing so quickly!

authors: johnniwinther lrhn matanlurey


text:
Is DateTime.now constructor result unique?

(1) I suppose that executing only one Isolate, every time this constructor is executed would create a different DateTime value (maybe close, but with different microseconds). But I have this doubt.
(2) Another doubt would be if my Dart Server is using only one isolate or multiple, because I'm using Http Shelf library and maybe is creating multiple isolates to handle requests.
UPDATE: By default it is run only in one isolate
https://pub.dev/documentation/shelf/latest/shelf_io/serve.html
https://api.flutter.dev/flutter/dart-io/HttpServer/bind.html
Thank you

(1) I suppose that executing only one Isolate, every time this constructor is executed would create a different DateTime value (maybe close, but with different microseconds). But I have this doubt.

Nothing ensures they are unique. It depends on multiple factors including how often the time is set to "ticking" on your running platform since no platform have infinite precision when it comes to definition of time (even if your OS have microseconds it does not mean the value is updated for each microsecond ongoing).
E.g. this program returns true on my Windows 11 machine running with a i9-12900K:
void main() {
  final d1 = DateTime.timestamp();
  final d2 = DateTime.timestamp();

  print(d1 == d2);
  print(d1.microsecondsSinceEpoch);
  print(d2.microsecondsSinceEpoch);
}

But returns false on my Linux server running with a i7-4770.

@julemand101 There is the Uuid Dart package which is supposed to generate unique identifiers:
// Generate a v1 (time-based) id
uuid.v1(); // -> '6c84fb90-12c4-11e1-840d-7b25c5ee775a'

// Generate a v4 (random) id
uuid.v4(); // -> '110ec58a-a0f2-4ac4-8393-c866d813b8d1'

// Generate a v5 (namespace-name-sha1-based) id
uuid.v5(Uuid.NAMESPACE_URL, 'www.google.com'); // -> 'c74a196f-f19d-5ea9-bffd-a2742432fc9c'

V1 says it is time based, so  will I have the same problem that you mentioned?

@busslina
Need to look into the actual implementation of UUIDv1 in that package but based on the wiki article, the UUIDv1 algorithm are suppose to handle the cases where multiple UUID's ends up being generated before the clock have yet to advance:
https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_1_(date-time_and_MAC_address)

@busslina Ok, based on the code in the uuid package, it does look like they attempt taking care of this scenario:
https://github.com/daegalus/dart-uuid/blob/main/lib/v1.dart
They even make sure to throw an error in case of too many UUID's is generated at a given time before the clock is advanced. So I think it handles the "issue" of the clock not being guarantee to be unique every time being asked.

@julemand101 Thank you very much.
For now I resolved it by adding a few lines of code:
static DateTime generateUniqueTimestamp() {
    var ret = now();

    while (ret == _timestampIndex) {
      ret = now();
    }

    return _timestampIndex = ret;
  }

Not using async delays (sleep) because it is needed in class constructor.

@busslina Maybe a bit weird to call it generateUniqueTimestamp since nothing prevents a computer from changing the clock to a previous point in time (e.g. network sync of clock).
Timestamps are just really bad for unique ID's.... I would recommend allowing duplicate timestamps in your design and use something else as the ID.

Well, I need some logic to discard previous versions of objects. Until today I was using an integrity index (incremented int value). It was working okay, but as I introduced a timestamp field for other purpose I thought I could use also for version controlling, so I removed the integrity index mechanism... I will think next move... haha

Agree that there are no guarantees that DateTime.now or DateTime.timestamp are unique. In fact, it's a requirement that they are not all distinct if you call them multiple times within a single microsecond. That might not be physically possible, but web code only has millisecond granularity, so there it's within the same millisecond, which is much more likely. And while native code might have microsecond precision, but it might not have microsecond granularity.
So the answer is, officially, "no".
(And if you run in different isolates, it's even more "no", since it's technically possible to run both isolates at the exact same time.)

authors: busslina julemand101 lrhn


text:
Refactorings with non-fatal error, or warning statuses

https://github.com/dart-lang/sdk/issues/53433
It would be nice to let users continue, even if some places cannot be updated.
@DanTup

It looks like the current prompt we have is only for rename:
https://github.com/dart-lang/sdk/blob/06d644196a8b351f991b4baafe22bfc9223cd942/pkg/analysis_server/lib/src/lsp/handlers/handler_rename.dart#L186-L194
I'll try adding support for this to refactors and see what it's like (I think we might have to show something like the first warnings text and "Refactor Anyway" as a button).

... we might have to show something like the first warnings text ...

How often do we have multiple warnings? I'm concerned about showing the user a warning they don't care about and not showing one they do care about.

Multiple warnings? Easily, if you have several places with cascades.
Can we show all warnings in a list?

Can we show all warnings in a list?

We can't use any formatting in the toast notification, so while we could join them together they would all be merging into a single paragraph.
What we could possibly do is:

Show a summary of the warnings (we'd need to build it)
Offer a preview of the changes we'll make (I've shown this diff preview before though we don't use it anywhere yet)
Give a button to show the "full details" that opens a text file that has the full set of warnings in (although it probably wouldn't have clickable locations)

authors: DanTup bwilkerson scheglov


text:
Uri: complete hashCode property description.

The documentation for the Uri hashCode property is incomplete.
Complete the description of the property.

Apologies for the incorrect base branches in #44363 and #44364. GitHub didn't make changing the base branch straightforward, so I've just created a new PR.
(See #44363 and #44364)
Thank you for all things dart-lang.

Thanks for your patience! This time things look better and our tooling was able to import the PR.
Gerrit CL:
https://dart-review.googlesource.com/c/sdk/+/174765

Thanks @ybakos !

authors: athomas kevmoo ybakos


text:
change smoke to use String instead of Symbol

 Issue by sigmundch
Originally opened as https://github.com/dart-lang/sdk/issues/17863

Strings are easier to use and faster than symbol (e.g. lookup in tables), and if the only purpose of symbol is for dart:mirrors, we could change smoke to hide them under the smoke/mirrors.dart implementation.
In that case, should we also be changing package:observe and other packages to use String instead of symbol?

 Comment by jmesserly

Removed Area-Polymer label.
Added Area-Pkg label.

 Comment by sigmundch

Added Pkg-Smoke label.

 Comment by sigmundch

Added this to the 1.6 milestone.

 Comment by sigmundch

Removed this from the 1.6 milestone.
Added Polymer-P-1 label.

 Comment by sigmundch

Added PolymerMilestone-Next label.

 Comment by sigmundch

Removed Polymer-Milestone-Next label.

 Comment by sigmundch

Removed Polymer-P-1 label.
Added Polymer-Milestone-Next label.

repo: dart-lang/smoke


text:
Expose ZoneSpecification parameters

Reopening after https://github.com/dart-lang/stack_trace/pull/167 was closed because of the repo's migration.
Closes https://github.com/dart-lang/tools/issues/1864 exposing several parameters from the ZoneSpecification.
This change will allow apps to have more control over the ZoneSpecification they need, when using this package. For exmaple, for security reasons many apps will override the PrintHandler, so no prints are exposed in production, but currently it's impossible to do it when using this package.

@devoncarew @lrhn I migrated this PR from the old repo, I would appreciate if you could review this, as the only reason why I don't use the stack_trace package in my app it's because I can't override the PrintHandler, and I have to do it for security reasons, so no prints are exposed in production.
Since I was going to expose the PrintHandler, I thought it would be better to just expose all the others, if anyone else needs them.

I'm not sure this is necessary.
If you do:
runZoned(
  zoneSpecification: someSpec,
  () => capture(...));

it should create a zone with all the overrides you want, and then a nested zone for capturing stack traces, which only has access to what  that parent zone exposes.

Does this work with guarded zones too? Because I need to intercept exceptions and prints.

authors: feinstein lrhn

repo: dart-lang/tools


text:
camera flyto

how do you get cameraflyto work when data is changed.  I am able to have the globe with a specified position work with componentDidMount.  I tried to get the following code to work but cannot get it to update on change - what am i missing
entityOnMount(entity) {
console.log(entityonmount, entity);
entity.name = "hoge";
}
entityOnUpdate(entity, prevProps) {
// const { viewer } = this;
entity.description = "someplace";
console.log('entity updating', entity, prevProps);
componentDidUpdate(prevProps)
if (prevprops != this.props) {
this.viewer.camera.flyTo({ destination: Cartesian3.fromDegrees(this.props.longitude, this.props.latitude, 50000.0) })

also, the flyto will not be by a click event. Data needs to be passed via props

repo: darwin-education/resium


text:
we should care about the transfer implement of the thirdparty tokens

https://github.com/darwinia-network/darwinia-bridge-sol/blob/53655320e06540c8748248fa61726b18ace4119c/contracts/issuing-backing/contracts/ethereum/Ethereum2DarwiniaBacking.sol#L122
The transferFrom may transfer less then amount tokens to the backing contract.
And some tokens may rebase their balance.

similal to https://github.com/helix-bridge/contracts/issues/18

repo: darwinia-network/darwinia-messages-sol


text:
chore: cleanup remove unused shacl and redundant StringFormatter setup

Pull Request Checklist
Task Description/Number

Remove unused shacl implementations
Remove redundant StringFormatter initialization
Rename AppConfig.layer as only a single AppConfig is loaded anyway
Remove unused testing boolean flag from AppConfig and application.conf

Basic Requirements
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] fix: represents bug fixes
[ ] refactor: represents production code refactoring
[ ] feat: represents a new feature
[ ] docs: documentation changes (no production code change)
[x] chore: maintenance tasks (no production code change)
[ ] test: all about tests: adding, refactoring tests (no production code change)
[ ] other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No
[ ] Maybe (not 100% sure => check with FE)

Does this PR change client-test-data?

[ ] Yes (don't forget to update the JS-LIB team about the change)
[x] No

LGTM, I don't remember why we had a separate test layer for the AppConfig but I assume you've tested that it still works and the test.conf is loaded when running the tests. If this works, than this is a nice simplification.

It works and that is due to a feature of the underlying typelevel config. It will load the application.conf from the main source set and if in the test or it it finds another application.conf it will merge both overwriting any value from main. Since the test.conf is included in the application.conf from the it source set its values will also have precedence and hence overwrite existing values from the main. For more details please refer to the documentation: https://github.com/lightbend/config#standard-behavior
The config is designed this way so that library authors can even provide an application.conf with default values in their jars so that the user of these libraries are then able to provide their own values with their own conf files.

repo: dasch-swiss/dsp-api


text:
feat(permissions): Data Browser permissions (DEV-1462)

resolves DEV-1462

@Vijeinath @domsteinbach the permissions in the dat browser now line up with the chart in the Notion page under "What are the Permissions for the Workspace?"

repo: dasch-swiss/dsp-app


text:
Full text search : user should be able to sort search results by label

Describe the bug
User should be able to sort search results after a full-text search.
To Reproduce Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

OPTIONAL: Expected behavior
I know you are planning to filter search results by facets (#111). But if you have a lot of resources, it won't be enough. After, or even before sorting search results by facets, users will still want to sort search results by rdfs:label, which is the common property/metadata for all resources classes.
Screenshots
If applicable, add screenshots to help explain your problem (drag-and-drop the image directly here).
Desktop (please complete the following information):

OS: macOS 10.14.6 (18G103), French
Browser Firefox
Version 70.01.1

Additional context
Add any other context about the problem here.

this issue has been moved to YouTrack: DSP-342

authors: flavens mrivoal

repo: dasch-swiss/knora-app


text:
feat: ci optimize

feat: ci optimize

1

repo: dashingdog/dashingdog-blog-admin


text:
fix excessive banning, remove some redundant logic

Since we send all mnb's now regardless of mn state ( #1149 ), ping check for sigTime being too old is obsolete (and wrong). Removing it should fix excessive banning.
Also removing fRequireEnabled, this logic seems to be deprecated too.
NOTE: it looks like non-(pre-)enabled MNs still won't be added to the list on receiving node. If that was the goal of #1149 - CMasternodeMan::Add() should be fixed in some way too because it still has this:
    if (!mn.IsEnabled() && !mn.IsPreEnabled())
        return false;

and therefore actual "add" logic never executes for such MNs if I get it right.
Correct me if I'm wrong pls :)

Yep, I think it's safe to remove that check. Done :)

utACK
(review button didn't appear to work for some reason)

repo: dashpay/dash


text:
Implement epoll support

As promised, here is the straight forward implementation of epoll on Linux, which should bring down overhead of the socket handler thread to nearly 0 (compared to 60-80% cpu load with select/poll when hundreds of connections are involved).

fyi, https://gitlab.com/dashpay/dash/-/jobs/517521269 used epoll in integration tests and all is green :)

Looks good 👍 Seems to be working fine on Ubuntu 16.04 for almost a day now. However, I had to specify -socketevents=epoll manually and (assuming epoll is the preferred mode) I guess we should also tweak conditions here https://github.com/dashpay/dash/blob/develop/src/net.h#L101:
-#if defined USE_POLL
+#if defined USE_EPOLL
+#define DEFAULT_SOCKETEVENTS "epoll"
+#elif defined USE_POLL

@UdjinM6 oh, yes, I somehow lost the "making it default" code while rebasing in the past. Added a commit.

In net.cpp line 3067 there should be rather EPOLL_CTL_ADD. As it logs error when issuing:
int r = epoll_ctl(epollfd, EPOLL_CTL_ADD, wakeupPipe[0], &event);

@MrDefacto Thanks for reporting this. Do you actually see an error message? The code you mentioned is only about the logging of an error, but it can't produce an error.

No. i'm adding kqueue support for FreeBSD and durning analyzing of Your patch i found this copy&paste mistake.

authors: MrDefacto UdjinM6 codablock


text:
Update competitive.conf

Changed 10slots to 12slots.

Opps. forget the extra file.

repo: dasisdormax/csgo-multiserver


text:
Raise an error if the optimizer cannot terminate

xref https://github.com/dask/dask-expr/issues/965

thx

authors: fjetter phofl

repo: dask/dask-expr


text:
Changed HDFSConfigException

Just allowing user to override the autodetected IP/Ports without raising HDFSConfigException

@milesgranger Thanks for the PR!  Perhaps we should consider a flag in the constructor: ignore_exceptions ?

@quasiben Probably a better solution indeed, just thought I'd share what I did to make it work for me. I'll get back to you with the updated PR. :)

Coverage increased (+0.02%) to 92.176% when pulling 7e197647c9d776f1ccdf40302ffdce5f6530d07d on milesgranger:milesgranger-override-autodetection into d79ccd70031ce6d630cde8eb60d4967cb25638e6 on dask:master.

Looks good.  Thanks for the PR!

authors: coveralls milesgranger quasiben

repo: dask/knit


text:
better performance with file backed cache

current cache in s3fs is relatively limited. it constantly grows and shrinks to keep reasonable memory usage. unfortunately, it will have a huge read amplification ratio (with fill_cache = True) or poor performance with fill_cache = False for random workload.
one way to solve this is to introduce an optional local file backed cache. for each s3 object  opened for read, a local tmp file with same size will be created and mmaped. a cache miss will fetch from s3 and copied into mmaped file. a mmaped file will provide much larger cache than current cache and much faster performance than S3.
i can submit a PR if you have interest

That is certainly an interesting idea! Would I be right in thinking that it only applies to posix systems?
Would you have any interest in generalising to any fetch-range file-like, as implemented in fsspec's AbstractBufferedFile? I suggest this, because the idea should be applicable to gcsfs, azure and other similar file-systems. (note #161 has preliminary support for s3fs-on-fsspec)

Whichever you decide, this would be an optional, opt-in caching strategy, (fill_cache='memmap'), and should be careful to remove the file on close, and also to remove anything lingering at __del__ or atexit/weakref.finalize.

in theory, it could apply to any slow storage that has a need for local cache. i will check fsspec and see whether it fits there. thanks for pointing out.
also i use tempfile.TemporaryFile, which will be released as soon as file object get closed. the only concern is the disk space, if someone load a huge object and touch every part, it will take full space. that is why it is just optional.

Implemented via fsspec


text:
Add support for bucket versioning

When s3 is used with bucket versioning this adds additional safely to reading objects preventing potential inconsistent state when reading an object whilst something else writes to it.
This also adds a utility to specifically open a given version of the file.
For non-version enabled buckets this should have no change.

So my only real reservation is that this expands the required permission set for users to include s3:GetObjectVersion for IAM managed s3 buckets

That is a pretty major reservation, as it can prevent usage of the library for some who currently use it without problem.

In conversation elsewhere, we talked about attempt at listing versions where the user doesn't have permissions (because the bucket has versioning), or attempting to fetch permissions without auth - do these provide appropriate errors now, and can users who know nothing about versioning use the existing functionality without problem? In short, are there any downsides to this PR we need to be aware of?

I still need to do some changes to ensure there are good errors and that a user can opt out of this functionality

OK @mariusvniekerk , let me know when you want me to review this.

@martindurant ready for review

Done, thanks.

authors: mariusvniekerk martindurant


text:
CDAP-13558 Support CDC pipelines on Spark version 2.x

JIRA - https://issues.cask.co/browse/CDAP-13558
WIKI - https://wiki.cask.co/display/CE/CDC+Solution+Enhancements
In scope of this PR:

implemented integration tests for CTSQLServer source plugin
introduced OperationType enum to make CDC records more type safe

@albertshau, could you please take a look.

@albertshau fixed all comments

repo: data-integrations/change-data-capture


text:
Fix cargo build failed caused by no authentication

What is changed and how it works?
Close #31
What's Changed:
Only those authorized to database-mesh/lrpar can clone project by ssh. Using https instead of ssh when cloning lrpar.

Thanks a lot

authors: TeslaCN mlycore

repo: database-mesh/pisanix


text:
Create  historical.py

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Hi @rony23-byte
Thanks for your interest in Databento!
We're not currently accepting PRs, however feel free to ask any questions you may have in Discussions, or file bug reports in Issues.

repo: databento/databento-python


text:
Modify build copyright/discliamer

Modify the last cell of our builds with this disclaimer about data usage:
`%md-sandbox
© 2018 Databricks, Inc. All rights reserved.

Apache, Apache Spark, Spark and the Spark logo are trademarks of the Apache Software Foundation.
The data made available in this notebook may only be used for the course it was provided during and for no other purpose.
Privacy Policy | Terms of Use | Support`

Done awhile ago.

authors: bmc conorbmurphy

repo: databricks-edu/build-tooling


text:
Use Spark 2.3.4 in Travis CI.

Spark 2.3.4 is released and Apache mirror only contains latest versions.

Codecov Report

Merging #768 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #768   +/-   ##
======================================
  Coverage    93.9%   93.9%
======================================
  Files          32      32
  Lines        5691    5691
======================================
  Hits         5344    5344
  Misses        347     347

Continue to review full report at Codecov.

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

authors: codecov-io ueshin

repo: databricks/koalas


text:
[BUG] FAQ needs updating

Describe the bug
FAQ is missing refs to some APIs, and is using OKG/Open Knowledge Graph terminology.

Fixed in #145

authors: beets tjann

repo: datacommonsorg/website


text:
Redesign merge

Merge in changes from the redesign branch to master.

@googlebot I signed it!

Yea, I agree. I was careful merging but there were quite a few conflicts. Let's test on staging.
@qlj-lijuan @wh1210 - could you both help with the CLA warning? Thanks!

@googlebot I fixed it.

@googlebot I fixed it

@googlebot I fixed it

@googlebot I fixed it

@pradh @tjann could you also please retrigger googlebot? Thanks!

@googlebot I signed it!

Thanks all - I'm not sure what's wrong with the CLA and see no way to fix it :(
I'm going to make this a draft and send you a new PR.

took the bot a day to respond ...

big sad...

I actually reached out to the team late last night, and they fixed it immediately today! And probably retriggered on open PRs. It was a parse error, probably from the merge.

authors: beets qlj-lijuan shifucun tjann wh1210


text:
Correction for raw affiliation APCoSS, Institute of Physical Education and Sports Sciences (IFEPSA), UCO, Les Ponts de Cé, France; CNRS, UMR6214, Inserm, U771, Medical School, University of Angers, Angers, France

Correction needed for raw affiliation APCoSS, Institute of Physical Education and Sports Sciences (IFEPSA), UCO, Les Ponts de Cé, France; CNRS, UMR6214, Inserm, U771, Medical School, University of Angers, Angers, France
raw_affiliation_name: APCoSS, Institute of Physical Education and Sports Sciences (IFEPSA), UCO, Les Ponts de Cé, France; CNRS, UMR6214, Inserm, U771, Medical School, University of Angers, Angers, France
new_rors: 02feahw73;04yrqp957;02vjkv261
previous_rors: 02feahw73;02nwvxz07;04yrqp957;02vjkv261
works_examples: W1997869713
contact: 33a1b90ffc94e8f3eabf75e917384490:83f02101627067daf492fae6d6889d @ recherche.gouv.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.

repo: dataesr/openalex-affiliations


text:
Correction for raw affiliation CNRS, ENS Lyon, Université de Lyon LIP (UMR 5668), France

Correction needed for raw affiliation CNRS, ENS Lyon, Université de Lyon LIP (UMR 5668), France
raw_affiliation_name: CNRS, ENS Lyon, Université de Lyon LIP (UMR 5668), France
new_rors: 029brtt94;02feahw73;04zmssz18;04msnz457
previous_rors: 029brtt94;02feahw73;04zmssz18
works_examples: W2157657301;W2171773189
contact: 9e35145f994c537ab10702c7d3b49842:5c25672821b912cd0ce65a3b3a57 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


text:
Correction for raw affiliation Université de Lyon, EVS-ITUS UMR 5600, INSA de Lyon

Correction needed for raw affiliation Université de Lyon, EVS-ITUS UMR 5600, INSA de Lyon
raw_affiliation_name: Université de Lyon, EVS-ITUS UMR 5600, INSA de Lyon
new_rors: 050jn9y42;029brtt94;0256r1e04
previous_rors: 050jn9y42;029brtt94
works_examples: W3022602101
contact: 70c5943c34ca3bafad790c83ecf6740d:09791ec55bee7387d99a4846e37c @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


text:
Email alerts are getting sent with schedule ID instead of name

Hello,

Your schedule cih8oaiyna from project dataform-data on dataform completed successfully.
See more details on the run page on dataform.co.

Moved from dataform-co/dataform-co#697
/cc @lewish

Now you will get email like below:
Hello,

Your schedule test-fai : t1fakfd6bh from project dataform-staging-test-project on dataform completed successfully.
See more details on the run page on dataform.co.

Will get rid of the random number when we move to the schedules.json

repo: dataform-co/dataform-web-tracking


text:
remplacement chaudière fioul par bois

1er version de l'action consistant à remplacer une chaudière fioul par une au bois

[ ] attention, nous avons un problème dans la désactivation de "bois" ici, qui fait que la soustraction ne se fait pas :thinking:

authors: Benjamin-Boisserie-ABC laem

repo: datagir/nosgestesclimat


text:
3D scatter plot enhancements

Enhance 3d scatter plot with the following features:

[x] ability to show labels
[x] show axis (with and without values)
[x] log, -log transformations

Done in v1.8.0

authors: StLeonidas dionissqq

repo: datagrok-ai/public


text:
Fix

Fix for:

start/end both are mandatory for archive files,
configurable file mime type

@Surefire report : surefire_report.pdf
@Newman report : newman.pdf

repo: datakaveri/iudx-file-server


text:
introduced st and et in summary endpoint

added startime and endtime in summary api
junit
postman updated

Can one of the admins verify this patch?

ok to test

authors: ankitmashu jenkins-datakaveri kailash

repo: datakaveri/iudx-resource-server


text:
🛑 Aadhaar Login is down

In 3e7aa78, Aadhaar Login (https://ssup.uidai.gov.in/ssup/login.html) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Aadhaar Login is back up in e85afb7.

repo: datameet/upptime


text:
dotenv and transformers are not included as dependencies when installing using pip

Is there an existing issue for this?

[X] I have searched the existing issues and found nothing

Bug description
python-dotenv is used here:
https://github.com/datamol-io/molfeat/blob/87f90c17456accc18d92e8bd6e51ff44ec3c3c9b/molfeat/store/modelstore.py#L12
however it's not included in the pyproject.toml, though it is included in env.yml. This results in an error when importing molfeat.
ModuleNotFoundError: No module named 'dotenv'

How to reproduce the bug
No response
Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- Molfeat version (e.g., 0.1.0):
#- PyTorch Version (e.g., 1.10.0):
#- RDKit version (e.g., 2022.09.5):
#- scikit-learn version (e.g.,  1.2.1):
#- OS (e.g., Linux):
#- How you installed Molfeat (`conda`, `pip`, source):

Additional context
No response

ah I see, don't know how I missed that. will fix now

repo: datamol-io/molfeat


text:
chore(main): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2024-10-10)
Contributors: @FilipMilic11, @iva-marusic, @matejpetravic, @EmilHuzjakSynth, @Skenktio, @IvonaFarkasSyntio, @stipesuto, @AnaParac, @lukamacan, @dinosehic-syntio, @KristinaSkufcaa, @iderek1, @andrijadukic-syntio, @petartisma, @Laura-B5
⚠ BREAKING CHANGES

initial implementation of persistor (#1) (#2)

Features

initial implementation of persistor (#1) (#2) (f156486)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.0.0
:sunflower:

repo: dataphos/persistor


text:
Automatically find link references for stops

Fixes #57.
Now we are able to connect stops to links like this:

The red areas (20 m in the picture) show the right-hand buffer areas from the oneway link versions, considered when matching stops to the closest links. If a stop does not fall within a side buffer area, it will not get a link reference automatically:

I.e., the red stop point should be moved below the link so it gets correctly to the right-hand side of it.

No automated tests, still, but the ./test.sh seems to run beautifully and I have also tested in QGIS that the key features with the stops and links work correctly.

repo: datarttu/sujuikoDB


text:
Add same day panel to the UI

Changes Unknown when pulling 54b8aaea22611c3c0671f6c604042cc7a53877da on cuducos-same-day-ui into ** on master**.

authors: coveralls cuducos

repo: datasciencebr/jarbas