Cocoapods support

I see Cocoapods support was removed. Is there any chance it could come back?

Hello!
This isn't the first time that someone's asked about restoring CocoaPods support. I truly feel bad, because I don't want to dictate how you work. In fact, I had an extremely hard time migrating from Carthage to SPM myself. The reason I did that migration, and why I opted to remove CocoaPods was I felt I ultimately had no choice. The entire Apple ecosystem, including Apple themselves are using SPM.
This is particularly painful because I know that mixing CocoaPods and SPM is problematic.
If I can help you get started with SPM I'd be happy to. But, I don't think adding back CocoaPods is a good long-term solution.


upgrading issues (heap_caps_calloc undefined)

Hello,
after updating my esp-idf version to latest master my app would no longer compile, however the confusing part is that the errors do not originate in my code but in the framework components:
:~/esp/stekar$ make flash
LD build/stekar.elf
/home/###/esp/esp-idf/components/esp32/lib/libpp.a(esf_buf.o):(.text.esf_buf_alloc+0xc): undefined reference to `heap_caps_calloc'
/home/###/esp/esp-idf/components/esp32/lib/libpp.a(esf_buf.o): In function `esf_buf_alloc':
(.text.esf_buf_alloc+0x15d): undefined reference to `heap_caps_calloc'
/home/###/esp/esp-idf/components/esp32/lib/libpp.a(esf_buf.o): In function `esf_buf_alloc':
(.text.esf_buf_alloc+0x171): undefined reference to `heap_caps_calloc'
/home/###/esp/esp-idf/components/esp32/lib/libpp.a(esf_buf.o): In function `esf_buf_alloc':
(.text.esf_buf_alloc+0x18d): undefined reference to `heap_caps_calloc'
/home/###/esp/esp-idf/components/esp32/lib/libpp.a(esf_buf.o): In function `esf_buf_setup':
(.text.esf_buf_setup+0x1b3): undefined reference to `heap_caps_calloc'
/home/###/esp/esp-idf/components/esp32/lib/libpp.a(esf_buf.o):(.text.esf_buf_setup+0x1c6): more undefined references to `heap_caps_calloc' follow
collect2: error: ld returned 1 exit status

what could be wrong ? also is there any migration guide ? (i get tons of errors in my bluetooth code, for now i just commented it out)

try running git submodule update and you may fix this.

try running git submodule update and you may fix this.


[html] find/peek references to CSS

VSCode Version: 1.5.0 - insider
OS Version: Windows 10

-- Sorry for the English, I used Google Translator --
Add functionality similar to QuickEdit the Adobe Brackets for quick edits CSS file, or when I have a style tag in my HTML.

Simple explanation how it works: https://www.granneman.com/webdev/editors/brackets/quick-edit/
Add the functionality of this extension is the same as the QuickEdit but for directives, controllers and services on AngularJS in my JS or when one has a script tag in my HTML.

That would be a similar function with the Peek VSCode and File Peek extension, but for HTML.

QuickEdit like in Brackets would be awesome!

@aeschli not only css, javascript also. the first image is an example for CSS, and gif (second image) and an example of a for js directives. Also add "label js", please.

-- Sorry for the English, I used Google Translator --
@aeschli Even if it is few votes .. the idea is to do this function tando for CSS when for AngularJS (javascript).
The old gif on AngularJS does not seem to be loading correctly, so I'm putting a new one showing.

Create a new one to then track the AngularJS (javascript). But I believe the process can be the same or even similar.
Or can we change the title one more time?

@Tekbr Let's keep this issue to enable finding a css rule from a HTML element. That enables opening a peek view, which is similar to what your screenshot shows. That fits in with our current features.
For improved angular tooling, please file this against one of the Angular extensions. We don't plan to add Angular specific tooling to the HTML built-in support.

I mark this as duplicate of #27892 as that one has more votes.


Document @private underscore attribute behavior.

We already protect everything we wanted without harm to readability.

:tada: This issue has been resolved in version 1.0.1 :tada:
The release is available on:

1.0.1
GitHub release

Your semantic-release bot :package::rocket:


To array functions

In regard of issue #1616.
Some of the for..in loop were also changed to object methods, but there were situations that it was not clear if it was the best thing to do, since the object iterated, been an object variable referenced by "this", could have its value as undefined in some cases throwing an error when processed. So I have only changed a portion of them, I hope that's not a problem, but it's something to be aware of.

find() and findIndex() are not supported by IE and old browsers, and they are not polyfilled as Babel cannot determine the type at compile time. I apologize I forgot to mention it in the issue.

I can see there is still an error, I'm working on it

Since my first PR every time I send a push to my fork it seems it updates the PR for you, sorry for the noise

@VinVaz no worries.  You should be able to run yarn test locally which should help with identify some of the issues before pushing.

The local test only throws a Spawn Error and I have not been able to find its source.

My guess is that there's something wrong with your dev environment.  I'm guessing you're on Windows.  In order to narrow things down, I would try running each command separately that the test script from package.json runs and then Google for the failure in whichever one fails.  In the meantime, circleci has reported the following test failures:
Error ---------------------------------------------------------------------------------- src/environments/array.js:244:9

Cannot assign `outrow` to `body[r]` because:
 - an indexer property is missing in `span` [1].
 - an indexer property is missing in `span` [2].

   src/environments/array.js:244:9
   244|         body[r] = outrow;
                ^^^^^^^

References:
   src/buildCommon.js:348:4
   348| ): DomSpan {
           ^^^^^^^ [1]
   src/buildCommon.js:523:67
   523| const makeVList = function(params: VListParam, options: Options): DomSpan {
                                                                          ^^^^^^^ [2]

Also, something must not have worked with CRLF to LF since there's still 255 changes files according to GitHub.

The best way to fix these problems would be to save the work elsewhere, delete the whole project, and cloning a fresh copy. (https://xkcd.com/1597/ 😄)

Closing due to lack of activity.  @VinVaz feel free to reopen a fresh PR if you have time.


Escape literal asterisk

As it was treated as formatting, so it made the rest of the paragraph not legible

@jdom,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@jdom Thank you!


MUMUP-3148: Messages filtered by start and end dates

Adding a filter to weed out any messages which fall outside the bounds of the goLiveDate or expireDate
Contributor License Agreement adherence:

[x] This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

Filter is refactored as an array.filter using moment. Take another look and see if this'll work.


Upgrade Boost from 1.67.0 to 1.71.0 in CI/dev image

Related to #168

This was just a check pull request, no need to keep it open.

Still does not liking NVCC :/

Yeah, I expected that. In the boost upstream PR, I tried 1.72 with proposed patch and it did not work. I'm not sure that 1.73 is going to be any better.

If you can write a reproducer, we can submit it to the upstream thread to facilitate the fix.


change parallelism to 1 to avoid multi write to scheduler config in s…

Change open-local init-job: reduce parallelism to 1
This prevents kube-scheduler.yaml from being modified in parallel (which results in invalid scheduler configuration) when the cluster has only 1 node.

I have tested single-node mode several times on this branch, and no bad configuration of kube-scheduler occurred. So it is save to merge.


OCM-6992 | fix: docs for wait for std compute nodes

OCM-6992
Change type

[ ] New feature
[ ] Bug fix
[ ] Build
[ ] CI
[x] Documentation
[ ] Performance
[ ] Refactor
[ ] Style
[ ] Unit tests
[ ] Subsystem tests

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

/approve
/lgtm


The IdentityModel.OidcClient 2.0.0 is not compatible with UWP

Hello,
Is it possible to make it works with UWP? Up to the version 1.7.0 it's working fine.
I got this error:
System.Security.Cryptography.Csp 4.3.0 provides a compile-time reference assembly for System.Security.Cryptography.Csp on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-arm.
One or more packages are incompatible with UAP,Version=v10.0 (win10-arm).
System.Security.Cryptography.Csp 4.3.0 provides a compile-time reference assembly for System.Security.Cryptography.Csp on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-arm-aot.
One or more packages are incompatible with UAP,Version=v10.0 (win10-arm-aot).
System.Security.Cryptography.Csp 4.3.0 provides a compile-time reference assembly for System.Security.Cryptography.Csp on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x64.
One or more packages are incompatible with UAP,Version=v10.0 (win10-x64).
System.Security.Cryptography.Csp 4.3.0 provides a compile-time reference assembly for System.Security.Cryptography.Csp on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x64-aot.
One or more packages are incompatible with UAP,Version=v10.0 (win10-x64-aot).
System.Security.Cryptography.Csp 4.3.0 provides a compile-time reference assembly for System.Security.Cryptography.Csp on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x86.
One or more packages are incompatible with UAP,Version=v10.0 (win10-x86).
System.Security.Cryptography.Csp 4.3.0 provides a compile-time reference assembly for System.Security.Cryptography.Csp on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x86-aot.
One or more packages are incompatible with UAP,Version=v10.0 (win10-x86-aot).

Thanks.

There is currently a bug in Microsoft's JWT library which makes it incompatible with UWP. I've been told that they will release a bug fix very soon.
https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/559

Their "5.1.3-pre-402070922" release can be added to an UWP project. That's a good start ...
I'll wait the fix then.

28th Feb. I will update as soon as it is releaser.

@leastprivilege I see MS released System.IdentityModel.Tokens.Jwt 1.5.3, which takes the dependency on Microsoft.IdentityModel.Tokens 1.5.3, which in turns drop the dependency on System.Security.Cryptography.Csp.
Once you get a chance, can you please update your NuGet dependency on System.IdentityModel.Tokens.Jwt  to >= 5.1.3?
Thanks :)

updated. UWP sample is working now. thanks!

Awesome, thanks so much for your quick response on this one :)


Can no longer send functions between modules

After the changes in #241 , now you cannot send a function between two modules.
module.rhai:

fn test(action) {
    action();
}

main.rhai:

import "module" as module;
module::test(|| {print("test");});

Errors with Function not found: 'anon$ef32cb20fe8c79d5 ()'.
A similar error happens when using Fn("") syntax.
I assume this is because functions are resolved when they are called and not when they are created - maybe it's possible to change that?
Regarding expected behavior - I expect Fn("fn_in_main") to work only in main.rhai since that's where it's defined, but the result of that call to work anywhere it's passed

That's true...  the new default module system will run each function call in the module's private namespace.
The closure || { print(...); } is actually an anonymous function defined in the global namespace.  Fn(...) only captures the name of the function, and obviously it couldn't find it in the module's namespace.
It is possible to resolve, but at a significant speed penalty - we merge the global namespace with the module namespace before each function call.

It is possible to merge in anonymous functions (aka closures) before each call, and that seems to work fine (at a cost of cloning).
However, it doesn't work if the closure calls a function that's defined in main:
module.rhai:

fn test() { print("test!"); }

fn action(f) { f.call(); }

main.rhai:

fn foo() { print("foo!"); }

import "module" as m;
m::test(|| test());             // works
m::test(|| foo());             // 'foo' not found

This is quite counter-intuitive...

I feel like all of these behaviors would be much easier to implement and understand if rhai was designed in a way where functions weren't independent but could access their environment freely... But maybe that's too late to change at this point and you just gotta hack around it now.
The way I'd try to implement it is that when the AST is being compiled or eval_from_newed (I'm not sure about the difference) from the module's file, the function calls all get resolved at that point. Then, when the function gets passed somewhere, the function calls inside it still resolve to whatever they resolved to before. So I guess function names are not good enough for this - maybe all functions get unique ids that are visible everywhere? Or maybe you can do it with actual function pointers, although that might not work with closures...
Oh and gotta think what to do about imported functions from modules - if you're using that solution, now you gotta resolve those at compile-time as well which means compiling a module needs compiling its dependencies and that could get complex/slow... Hmm.
The system I'd love Rhai to mimic regarding visibility in modules is Python's module system - I think it just works really well.

I feel like all of these behaviors would be much easier to implement and understand if rhai was designed in a way where functions weren't independent but could access their environment freely... But maybe that's too late to change at this point and you just gotta hack around it now.

Yes.  Again, Rhai doesn't implement a scope-chain for performance reasons.  That is a deliberate design limit.

Then, when the function gets passed somewhere, the function calls inside it still resolve to whatever they resolved to before.

You need to copy the entire function definition around to do that.  Essentially, merging both namespaces (global and module) work in a similar manner.

The system I'd love Rhai to mimic regarding visibility in modules is Python's module system - I think it just works really well.

Well, Rhai has different design goals...  Otherwise, why not just write in Python?

Actually I have implemented the merging and it seems to work well...  So I may make it the default behavior...
So now you get:
module.rhai:

fn test() { print("test!"); }

fn action(f) { f.call(); }

main.rhai:

fn foo() { print("foo!"); }

import "module" as m;
m::test(|| test());             // works
m::test(|| foo());             // also works

Why not just write in Python?

Python is harder to tightly integrate with Rust like Rhai can (calling functions both ways, with custom types), at least from a surface-level looking around.

Seems to work well

Will this work for weird edge cases like a chain of 3+ modules with similar function names?

Will this work for weird edge cases like a chain of 3+ modules with similar function names?

Each module function overwrites a function with same name in parent modules.  The bottom layer is the global namespace.  So that should work... by theory...

You can pull from https://github.com/schungx/rhai to test out the new functionality...

The new PR lands on the official repo, so you can now pull on that.
Closing this issue for now.


css and js

Hi there,
I'm trying to run the html example, but js and css files get error 404

Hard to comment on the thing without a code example, make a minimal example that fails for you and explains what you wanna do and I am sure somebody will help you.

I was running your project's example. Then I've added a js tag on the header of the html file, but it gets 404 error, on any file. I know this must be something stupid.. it's just because i'm new to python. In php it could be solved by a "FILE" or "DIR" maybe.

If you are new to Python I would suggest you try some framework that provides static file serving capabilities like Sanic, Falcon or Flask. Japronto is targeted for particular use cases of speed enthusiasts. It is not yet a general purpose web framework I hope it becomes one day.

I see. I've actually started writting this -> https://github.com/jersobh/pydge
Solved the problem creating a route for the static files :+1:
Thanks

I'm trying to build a framework upon this, now I just simple use the code like this
from japronto import Application

async def hello(request):
    path = request.match_dict['static_file'].strip('/')

    with open(path) as html_file:
        return request.Response(text=html_file.read(), mime_type='text/html')

app = Application()

app.router.add_route('/static/{static_file}', hello)

app.run(debug=True, port=8765)

Because my static files were in a multi-tiered file tree i hacked something together, i'm not proud....
from japronto import Application

def content(request):
    with open(request.path[1:], 'rb') as static_file:
        return request.Response(body=static_file.read())

app = Application()

app.router.add_route('/static/{1}', static)
app.router.add_route('/static/{1}/{2}', static)
app.router.add_route('/static/{1}/{2}/{3}', static)

app.run(debug=True)

Performance for a 5kB file.
wrk -t 1 -c 100 -d 1m http://localhost:8080/static/1/2/3.file
Running 1m test @ http://localhost:8080/static/1/2/3.file
  1 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     6.32ms    2.95ms  28.84ms   77.73%
    Req/Sec    16.04k     3.97k   22.81k    54.50%
  958039 requests in 1.00m, 4.53GB read
Requests/sec:  15955.85
Transfer/sec:     77.18MB


Fire Berserker Battle Reward

The battle reward for the Fire Berserker fight doesn't work. The console throws an error, the reward (the fireball spell) is not rewarded, and the button to continue doesn't appear. This can be reproduced by just beating the Fire Berserker.

Fixed.


Disable context menu and allow right clicking

Previously when right click the context menu would appear and right clicks wouldn't be registered by the click event listener.
This change adds a handler to the contextMenu opening, redirects that mousePointEvent to the click handler and prevents the context menu from being opened.
Have evaluated this locally.

Nice, thanks for contributing!
I strongly agree with the need for right-click event support in the grid. And it's a good base for that.
I don't think it should be tunneled through the regular click even, though.
The onCellClick is meant to be an equivalent of the click event in js. Triggering it also on the contextmenu event might be confusing.
The current implementation also enables the right-button multi-cell-selection and other operations that were previously exclusive to the left mouse button. In those situations my rule of thumb is to see how do those operations work in existing grids (namely Excel, Excel Online and AG Grid) - to ensure predictable user experience. In those, the right button can only be used to select a cell and invoke a context menu of that cell (but no multi-cell selection nor column resizing).
Please also note that a blanket preventDefault and stopPropagation statements on the contextmenu event disables the context menu within the text boxes when editing values within the grid.
My suggestion for this feature would be:

Adding a new onCellContextMenu event (that is fired with the same properties as the onCellClick event)
Removing the blanked preventDefault and stopPropagation statements from the contextmenu event handling

In js, users can handle it themselves
In Dash, as users cannot code callbacks directly, we should introduce a separate prevent_default_cell_context_menu property that would be used when generating the callback for the underlying JS grid (for now it can be just a boolean value)

The onCellContextMenu should only be trigger in case of actual cell interactions (so not in case of text box interactions when editing grid values)

This would make the behavior more consistent with what web-dev users may expect and will also allow us to add a proper support for custom context menus in the futur (something that's also on the roadmap).

removed font styling changes into separate PR

Thanks for the review,

I've moved context menu to be it's own callback
Context menu callback is disabled if we're in editing mode
I didn't add the boolean for dash since users can generate their own js assets that will prevent update on the context menu
Right click dragging is not changing within this PR and should be fixed separately.


[rke2] updating an incorrect image name for a workload deploys a new pod instead of removing the old one. Removing the old pod manually fails, until the pod with the correct image goes to an active state

Rancher Server Setup

Rancher version:v2.6.4-rc1
Installation option (Docker install/Helm Chart):helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):rke1, 1.21.9

Proxy/Cert Details:valid certs

Information about the Cluster

Kubernetes version: 1.22.6+rke2r1
Cluster Type (Local/Downstream):Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):custom, with windows workers (version 2022)

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom):admin

Describe the bug

updating an incorrect image name for a workload deploys a new pod instead of removing the old one. Removing the old pod manually fails, until the pod with the correct image goes to an active state.
To Reproduce

deploy a workload with an incorrect image name. i.e. docker pull ranchertest/mytestcontainer
note that the deployment goes to a new error state
fix the image name
try to remove the old pod manually

Result

old pod with bad image is unable to remove until the new pod successfully deploys.

Expected Result

expecting the old pod to remove immediately.

Additional context
this is more prevalent in a workload with a large image, i.e. windows images.
https://user-images.githubusercontent.com/16691014/152889740-e0ff6582-dad0-42bc-9604-6905da700449.mov

I think this is the intended behavior, I think it has to do with the minimum availability, I don't think the old pod will be removed until either the new one succeeds, or the deployment is scaled down to 0.

ok, thanks Jake. Closing this as intended behavior


micalevisk/last-issue-action@v2 not found

As of 3 days ago, micalevisk/last-issue-action@v2 is returning "not found" for me in one of my GitHub workflows. I have tried changing this from v2 to v2.0.0 and v2.2.0 (which appears to not be in the marketplace), as well as direct harsh specifications of both of those releases, all of which return "not found." This error starting simultaneously with the v2.2.0 release makes me suspect something occurred in that process to break the action/rename it somehow. An example of the failure is here, where the run history shows the first failure date.

thank you for reporting!
I believe that this was a regression on v2.2
Can you please try v2.1.0 instead? I'll revert that ASAP

Confirmed, reverting to v2.1.0 (by specifying explicitly) has solved the issue for me.

@andrew-saydjari v2 should be working now
I was trying to support GH enterprise but it didn't worked

Can I use this goodwill to ask you to look at https://github.com/andrew-saydjari/andrew-saydjari.github.io/issues (this is my personal website, but I have several other applications I want to extend to if I can get this working) where #84 was created instead of appending to #83? I feel like my usage here is a perfect mirror to your example, but just isn't working for me.

it worked locally, at least :thinking:

https://github.com/andrew-saydjari/andrew-saydjari.github.io/actions/runs/6791129291/job/18461996780
it looks like issue-number is null, despite being found has-found being true?

(I am happy to split this off into a new issue if there really is something to track down, but my first assumption was that I had some silly typo)

oh you're using issue_number instead of issue-number

Yes.  Everything looks great now, I am a happy user, and will proliferate my usage! 👍🏽


Particle JS project

Particle.js JavaScript Project
I am Alik Kumar Ghosh. I would like to add a particle.js Javascript based project.
Could you please assign this to me as I am GSSOC'21 participant?

hey, I am a GSSOC'21 participant , I would love to take up this task, can you please assign it to me?

I have already completed, i am about to push my code now.

https://github.com/Vishal-raj-1/Awesome-JavaScript-Projects/pull/373/#issue-591691906
That's my PR link please have a look if possible.


⚠ Bofrost.at has degraded performance

In 917ae27, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1577 ms

Resolved: Bofrost.at performance has improved in 5c2bcf7 after 307 days, 9 hours, 39 minutes.


Status with new line

I want to post a twitter with new line.
How can I do it?

https://twittercommunity.com/t/is-it-possible-to-add-a-line-feed-to-a-status-update/7628
But I'm not sure about Twitter actually displaying the line break. See another post about it in another language, but that's not the point of the comment: http://stackoverflow.com/questions/15122284/post-tweet-with-new-line-inside-it

@pajoda
Thanks for your answer.
I have tried above link, but twitter can not display the line break.
Twitter::postTweet(array('This is first sentence'.'%0D%0A'.'This is second sentence', 'format' => 'json'));

I think the issue is in Twitter.php
line 244:
$this->log('PARAMETERS : '.http_build_query($parameters));
http_build_query()
will return the url encoded:

This+is+first+sentence+%250D%250A+This+is+second+sentence

Which when tweeted looks like:

This is first sentence %0D%0A This is second sentence

However, we want to pass to Twitter:

This+is+first+sentence+%0A+This+is+second+sentence

For proof of a solution you can edit the $parameters variable in the query method within Twitter.php to
        if($name !== "media/upload")
        {
            $parametersEncoded = http_build_query($parameters);
            $parametersEncoded = str_replace("%250A", "%0A", $parametersEncoded);
        }
        else
        {
            $parametersEncoded = http_build_query($parameters);
        }

	$this->log('METHOD : '.$requestMethod);
	$this->log('QUERY : '.$name);
	$this->log('URL : '.$url);
	$this->log('PARAMETERS : '.$parametersEncoded);
	$this->log('MULTIPART : '.($multipart ? 'true' : 'false'));

Try this:
      $string = 'Next 24h events: ';        $newLine = '             ';         $newLine = str_replace(' ', '', $newLine);         $string = $string.$newLine;
its work for me ($newLive has to broken )

I ended up adding urldecoded newline char
$status = 'First line'. urldecode('%0a').'Second line'.urldecode('%0a').'Third line';
I hope it will help others...

You can use "\n" for newline.
Example:
$status = "First line. \nSecond line. \nThird line";


Don't run CI on win-netlib-fix branch

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (d44f58b) 91.51% compared to head (0adbd34) 91.51%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #467   +/-   ##
=======================================
  Coverage   91.51%   91.51%
=======================================
  Files         162      162
  Lines       21717    21717
=======================================
  Hits        19875    19875
  Misses       1842     1842

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


HDDS-4147. Add OFS to FileSystem META-INF

What changes were proposed in this pull request?
With this change, fs.ofs.impl won't have to be explicitly set in core-site.xml when using OFS on a client.
This change is derived from https://github.com/apache/hadoop-ozone/pull/1088
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4147
How was this patch tested?
Existing OFS tests shall pass even with conf.set("fs.ofs.impl", ...) removed.

Thanks @adoroszlai for verifying the changes.
@elek Is there anything left to be desired for this PR?


resolve TODOs in docs

there are still some lingering TODOs in the docs which we should address before the 2.0 release. This should probably wait until the docs workshop prs are merged though, as its possible that content will address some of the TODOs.

closed in #6886


someting is wrong when i'm using the EarKindle

The content of the Deliver Logs are always shown with "send failed", So, what's happening to this?

The content of the Deliver Logs are always shown with "send failed", So, what's happening to this?

In page "Logs" of GAE BackEnd, you can find out what happened actually.

09:23:15.802
GET
200
127 B
92.5 s
AppEngine-Google; (+http://code.google.com/appengine)
/worker?u=admin&id=5066549580791808%2C5113123132407808%2C5634472569470976%2C5659313586569216
<IP_ADDRESS> - - [21/Mar/2017:09:23:15 +0800] "GET /worker?u=admin&id=5066549580791808%2C5113123132407808%2C5634472569470976%2C5659313586569216 HTTP/1.1" 200 127 http://devin-halward.appspot.com/deliver?u=admin "AppEngine-Google; (+http://code.google.com/appengine)" "worker.devin-halward.appspot.com" ms=92541 cpu_ms=62210 cpm_usd=0.000022601466 loading_request=0 instance=00c61b117c4237aba1ccd725c2ba2db7f0175b3b266a101c209b236b204652fe7a948bed87 app_engine_release=1.9.48 trace_id=fbeb4e0fd64bfbc6bf3a85671a66263c
{
protoPayload: {…}
insertId: "58d080e0000542765c5efa26"
httpRequest: {…}
resource: {…}
timestamp: "2017-03-21T01:23:15.802866Z"
severity: "WARNING"
labels: {…}
logName: "projects/devin-halward/logs/appengine.googleapis.com%2Frequest_log"
operation: {…}
}
09:24:32.707
fetch article failed(503):http://www.aisixiang.com/data/103576.html.
09:24:32.708
url [javascript:void();] failed [Invalid request URL: javascript:void();].
09:24:32.708
fetch article failed(535):http://www.aisixiang.com/data/103576.html.
09:24:32.931
fetch article failed(503):http://www.aisixiang.com/data/103617.html.
09:24:33.021
fetch article failed(503):http://www.aisixiang.com/data/103569.html.
09:24:33.112
fetch article failed(503):http://www.aisixiang.com/data/103570.html.
09:24:33.487
fetch article failed(503):http://www.aisixiang.com/data/103634.html.
09:24:33.578
fetch article failed(503):http://www.aisixiang.com/data/103634.html.
09:24:33.668
fetch article failed(503):http://www.aisixiang.com/data/103634.html.
09:24:33.757
fetch article failed(503):http://www.aisixiang.com/data/103634.html.
09:24:33.845
fetch article failed(503):http://www.aisixiang.com/data/103634.html.
09:24:34.005
fetch article failed(503):http://www.aisixiang.com/data/103634.html.
09:24:34.095
fetch article failed(503):http://www.aisixiang.com/data/103634.html.
09:24:34.244
url [javascript:void();] failed [Invalid request URL: javascript:void();].
09:24:34.245
fetch article failed(535):http://www.aisixiang.com/data/103634.html.
09:24:34.560
fetch article failed(503):http://www.aisixiang.com/data/103598.html.
09:24:34.650
fetch article failed(503):http://www.aisixiang.com/data/103568.html.
09:24:35.893
fetch article failed(503):http://www.aisixiang.com/data/103582.html.
09:24:35.975
fetch article failed(503):http://www.aisixiang.com/data/103582.html.
09:24:36.058
fetch article failed(503):http://www.aisixiang.com/data/103582.html.
展开  收起  全部显示
These are logs about "send failed ",Can anyone could explain what wrong with it? and there exist someting i have to say that all of the logs belong to "wanring" other than "error"

You need to expand the logs and paste it again.

I don't know what exactly logs should i send to show you.can you operate my computer with a telecontrol tool,such as TEAMVIEWER ,in order to figure out what exactly wrong@cdhigh

I don't know what exactly logs should i send to show you.can you operate my computer with a telecontrol tool,such as TEAMVIEWER ,in order to figure out what exactly wrong @cdhigh

@DevinHalward If you can give me your google account and password, may be I can update it for you。
After done that， you can modify your password. If you needed just mail me<EMAIL_ADDRESS>


groups/channels: rank level bans

This fixes #1593 on the backend and also displays messages on the frontend explaining that you can't join a group if they have banned you or your rank.
This should cover the joining from the frontend, but also anyone trying to be sneaky from the terminal whether they are trying to join a group or a channel since this also updates the can-read/can-write checks to include a check for banned status.

Pulled and played with this locally, so far everything LGTM. Asked @arthyn for a poke to set a rank ban so I can test the full flow.

Here's the poke for future reference:
:groups &group-action [[~zod %test] [now [%cordon [%open [%add-ranks (~(gas in *(set rank:title)) ~[%earl])]]]]]


Investigate Cilium CNI

Who What & Why
I'm as a developer wants to verify that our solution is able to be deployed with Cilium CNI because:

Cilium CNI is one of the most popular and promising CNI implementation
Cilium CNI is available in the most cloud providers

I'm as a customer wants to deploy on Cilium CNI by demand.
Additional info
Restrictions
Acceptance criteria
Definition of done

[x] Compare current (Calico) and Cilium CNI
[x] eUPF is tested together with Cilium CNI
[x] Defined whether it's possible to deploy with Cilium CNI

eUPF normally starting and working with Cilium

Cilium not support static IP assign to pod , this feature in developing https://github.com/cilium/cilium/issues/17026

for open5gs we need support SCTP protocol, Cilium support this feature in Beta https://docs.cilium.io/en/latest/configuration/sctp/


Create Spec Helper Modules

Unless you have a specific plan for what we want to do with spec helper modules, I'd recommend we hold off and start implementing this into a project or two before we decide what helper modules we'd like to have.

Cool.

First helpers desired:
assert_success Invites::InviteUserCommand.call(@invite_user_form, @inviter)
assert_failure Invites::InviteUserCommand.call(@invite_user_form, @inviter)

assert_success and assert_failure should also have the ability to optionally specify a status that they will validate also.
assert result.failure?
 assert_equal :redeemed, result.status

This is complete. The matchers themselves are tested.


Add a reference to ConfigureCryptoDefaults.ps1 script for E19 in the TLS section of HealthChecker

I have recently got an issue with incorrect TLS configuration set by Nartac IISCrypto tool.
I was not aware of the ConfigureCryptoDefaults.ps1 script (that is available with E19 in the $ExInstall\Bin folder) which can easily be used to setup a more secure or more relaxed cipher suites list and configure correctly the other TLS settings, as we recommend.

@gabymuntean  what is the ask here? To throw a warning if E19 isn't configured any longer out of the box from setup?

Not sure if a call out stating this as a note every time would be beneficial, even against a 2019 Exchange Server. Some customers might have a reason to not disable TLS 1.0/1.1 for home grown applications and they needed to remove what we set to be the most secure for a time.

@gabymuntean need to know what the other keys are related to TLS that we might want to include that we don't yet already.
I don't believe it is wise to include a reference to the script regarding how to configure TLS, just because of the mixed environments deal. We don't even run the ConfigureCryptoDefault.ps1 between CU build upgrades because of it messing with TLS that might have been there for a reason within the customer environment. Then depending on which CU they have installed, will depend on what all gets done and changed. So, if there was a mixed version of CUs, that could have different results which will not have the desired outcome.

@gabymuntean we discussed this internally and decided that we don’t want to reference the script yet. We’ve refactored the TLS documentation and replaced the more complex registry configuration steps with copy and paste PowerShell commands. The script itself was designed to run during setup and was not intended to run afterwards manually by customers. I will closely monitor the situation of TLS-related cases and we can re-open the discussion if we see a situation in which we should provide something for our customers.


update external submodule to noah-owp-modular

The surface module we're using has changed names to noah-owp-modular. This PR modifies the submodule path and URL along with other files as necessary to support running the main branch of noah-owp-modular.
Additions

extern/noah-owp-modular directory

Removals

extern/noah-mp-modular directory

Changes
Updated references to noah-owp-modular from noah-mp-modular:

Updated .gitmodules and ran git submodule add https://github.com/NOAA-OWP/noah-owp-modular extern/noah-owp-modular/noah-owp-modular with updated noah-owp-modular path and URL
.github/workflows/module_integration.yml
data/example_bmi_multi_realization_config.json
data/example_bmi_multi_realization_config_w_routing.json
data/bmi/fortran/noah-owp-modular-init-cat-27.namelist.input
extern/noah-owp-modular/CMakeLists.txt
extern/noah-owp-modular/README.md

Testing

Built noah-owp-modular and successfully ran Ngen tutorial example on cat-27

Todos

Update Ngen wiki to use noah-owp-modular
Note in the wiki that if you copy over namelist.input you need to specify the full relative path for the parameters table (../extern/noah-owp-modular/noah-owp-modular/parameters/)
The wiki says to copy over bondville.dat but I don't believe that is necessary

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows project standards (link if applicable)
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist (automated report can be put here)

Target Environment support

[ ] Linux
[ ] MacOS

Please let me know what needs to be changed or modified on the PR. Thanks

Has this commit been used to build a library and execute the model using the framework to ensure it works?

Yes. Just to be certain I did a clean ngen build from checking out the PR. Unit tests passed. If you follow my suggested changes to the Wiki, then you can build and run noah-owp-modular with the example config, namelist, and hydrofabric in cat-27.


Search with category endpoint

Changes proposed in this pull request:

Add endpoint for searching with a category
Bees.Venue.category/7

Categories:
https://developer.foursquare.com/docs/resources/categories
Screenshot:

Ready for review:
@DanToml

@DanToml Rebased. Thanks :star2: :dizzy:

@sic-f That's great - thanks! - I also just setup CI so it's easier to validate future changes too.

@DanToml No worries 🌟 Cool, easier now that we have CI 💯

🎉 Gonna cut a 0.3.0 release when I get home tonight.
Thanks for the great work


Week 4 ShinyWidgetsDemo error

I downloaded the ShinyWidgetDemo file, but there seems to be an error on rows 106-112.
code:
selectInput(
inputId='animal',
label='Select Animal',
choices=c("cat","dog","rat"),
selected="dog"
)
Error message:
Error in selectInput(inputId = "animal", label = "Select Animal", choices = c("cat",  :
could not find function "selectInput"

Whenever R can't find a function object that you expect to be found, it's likely you've not loaded the package with library().
At the beginning of your script, include library(shiny) and try again.  Do not include a call to function install.packages().
Let me know if this helps!

Thanks, that fixed it!

Sure thing!


[Event Request]  codeunit 8616 "Config. Management" OnTransferContentOnBeforeToCompanyFieldRefValue

Hello, Would it be possible to add OnTransferContentOnBeforeToCompanyFieldRefValue event to codeunit 8616 "Config. Management" like this?:
local procedure TransferContent(TableNumber: Integer; NewCompanyName: Text[30]; CopyTable: Boolean)
...
                  if not TempFieldRec.Get(TableNumber, FieldRec."No.") then begin
                        FromCompanyFieldRef := FromCompanyRecRef.Field(FieldRec."No.");
                        ToCompanyFieldRef := ToCompanyRecRef.Field(FieldRec."No.");
                        OnTransferContentOnBeforeToCompanyFieldRefValue(FieldRec, FromCompanyFieldRef); //NewEvent
                        ToCompanyFieldRef.Value(FromCompanyFieldRef.Value);
                    end;

[IntegrationEvent(false, false)]
local procedure OnTransferContentOnBeforeToCompanyFieldRefValue(FieldRec: Record "Field"; FromCompanyFieldRef: FieldRef) //NewEvent
begin
end;

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


Dev/quick shop

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (b5627ec) 83.63% compared to head (c089a8c) 83.49%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
- Coverage   83.63%   83.49%   -0.15%
==========================================
  Files          38       37       -1
  Lines        1497     1466      -31
  Branches       89       88       -1
==========================================
- Hits         1252     1224      -28
+ Misses        245      242       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


prepend Source Serif 4 to $font-family-serif

Fixes #1349.

"Source Serif Pro"  is retained after "Source Serif 4" because $font-family-serif may be used in other files which make use of the files inside the docs.rs project's /static, which still contain Source Serif Pro.

Another option might be to delete the override from our rustdoc.css
https://github.com/rust-lang/docs.rs/blob/f3a3740a8f60e000f041ebd05d973001cd2d4de4/templates/style/rustdoc.scss#L33
I'm not sure why we have this, it might be necessary for older rustdoc output, but checking some random docs from 2016 and 2018 deleting that line works fine.

It comes from the initial commit of the UI
https://github.com/rust-lang/docs.rs/commit/f59bc5f030ef9d5e220bd6503c9e5fa5efbb6264#diff-1ba7be47f68c69933566610bc4a27b54149989a893f733c0a233fd315ad2a19dR61
I think it's a good time to check whether it's needed by deleting it and seeing if we get any complaints :sweat_smile:

Should I change the PR to remove the override instead?

@tspiteri yep, I think it's worth trying out to simplify issues if rustdoc changes its fonts again.

Done.


create react app: pubsub does not work when served from HTTPS origins

Version:

     "libp2p": "^0.29.3",
    "libp2p-bootstrap": "^0.12.1",
    "libp2p-gossipsub": "^0.6.4",
    "libp2p-mplex": "^0.10.1",
    "libp2p-noise": "^2.0.1",
    "libp2p-webrtc-star": "^0.20.1",
    "libp2p-websockets": "^0.14.0",

Platform: macOS
Subsystem: Google Chrome 86.0.4240.183 (Official Build) (x86_64)

Type: Bug
Severity: High
Description:
In browser PubSub only works when one peer is running on localhost.
If both peers are running on pages hosted over https (like github pages), while the can discover eachothers peer ids, they cannot dial / listen for topics... but if 1 is localhost and the other is hosted on https origin, they can consume / produce events on the topics successfully.
Steps to reproduce the error:
https://github.com/OR13/webrtc-pub-sub-example
https://or13.github.io/webrtc-pub-sub-example/
^ open 2 tabs of this URL.
Copy the peer id of one of the tabs and set this URL: https://or13.github.io/webrtc-pub-sub-example/?peers=["QmTUQLwNFpMPA8eEmQaDJRrz3bHtQEbxJ2QQT5b2Ua1JvD"] and refresh.
(replacing peer id with the copied value)
see console for Error: "peer unavailable".
Run the project locally and use a local tab for 1 peer and a hosted tab for another peer... observe no error.
The same exact code works perfectly when run on local host, but fails when exposed over https (using ngrok).
It says that the test servers MUST NOT be used for production, is it possible that what is really meant is that they DO NOT SUPPORT https origins?

I was able to get this to work on Chrome and Brave on macOS using the url you gave. I didn't see the failure log and was able to verify the connection to the target peer in the libp2p.connections map via the console.
Can you turn on debugging for the webrtc-star transport to see if there is a clear error there? Setting localStorage.debug="libp2p:webrtc-star:*" in the browser console and refreshing should start logging.
My assumption is that the webrtc hole punch or ICE connections are failing for some reason.

@jacobheun I tried:
localStorage.debug="libp2p:webrtc-star:*";

but did not see any errors.

nvm, it just took a second to work... now I am seeing this:

downloaded and tested in brave, seeing the same error there.

hmm based on: https://github.com/libp2p/js-libp2p-webrtc-star/issues/258
I removed: '/dns4/wrtc-star2.sjc.dwebops.pub/tcp/443/wss/p2p-webrtc-star'
And that appears to have resolved the issue, will do a deployment to confirm.

confirmed its working now, this was the fix:

    const libp2p = await Libp2p.create({
        addresses: {
          listen: [
            '/dns4/wrtc-star1.par.dwebops.pub/tcp/443/wss/p2p-webrtc-star',
            // '/dns4/wrtc-star2.sjc.dwebops.pub/tcp/443/wss/p2p-webrtc-star'
          ]
        },
        modules: {
          transport: [Websockets, WebRTCStar],
          connEncryption: [NOISE],
          streamMuxer: [Mplex],
          peerDiscovery: [Bootstrap],
          pubsub: Gossipsub
        },
        config: {
          peerDiscovery: {
            [Bootstrap.tag]: {
              enabled: true,
              list: [
                '/dnsaddr/bootstrap.libp2p.io/p2p/QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN',
                '/dnsaddr/bootstrap.libp2p.io/p2p/QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb',
                '/dnsaddr/bootstrap.libp2p.io/p2p/QmZa1sAxajnQjVM8WjWXoMbmPd7NsWhfKsPkErzpm9wGkp',
                '/dnsaddr/bootstrap.libp2p.io/p2p/QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa',
                '/dnsaddr/bootstrap.libp2p.io/p2p/QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt'
              ]
            }
          }
        }
      })


use primal cdn for images

this uses the s (small) sized images from primal for contacts which should speed up loads. also because it's all from one origin I think the browser can batch these better.
question: is there a way to do the same with our own cache url?

search was the main place it was really hurting me, but yeah if you want to rewrite this in the background (or add a separate field?) that might be good. as long as it's not going to complicate sync too much


Fix fpgm

The current implementation calculates number of filters incorrectly, this PR fixes the problem.

@tanglang96 please help review


Geten no Hana with Yume Akari - Aizouban [PCSG00921]

App summary

App name: Geten no Hana with Yume Akari - Aizouban
App serial: PCSG00921
App version: 1.0

Vita3K summary

Version: v0.1.5
Build number: 2642
Commit hash: https://github.com/vita3k/vita3k/commit/4e1e255a
CPU backend: Dynamic

Test environment summary

Tested by: othmanead
OS: Windows 11
CPU: Intel i5-10300H
GPU: RTX 3060 mobile
RAM: 16 GB

Issue:

Game displays a black screen

Screenshots:

Log
vita3k.log
Recommended labels

Playable

Hi, it crashes for me before showing any content on screen with Vita3K v.0.1.6. Could anyone test it again to see if it is actually playable? Sorry I don't know how to find and upload my own log, but my environment is mostly the same as above. Thank you.

as of https://github.com/Vita3K/Vita3K/commit/fd92a28a1fccbc09a1458aa4d05563af56c5c3af, the game is in intro. crashes at around the 3rd screenshot.
Screenshots

Log
vita3k.log
Recommended Labels

Intro
crash


Create conda-forge package

The title basically says it all: create a conda-forge recipe and submit it to the package repo.

With https://github.com/wrenfold/wrenfold/pull/244 there is a full-source archive (including submodules) with every release.
With https://github.com/wrenfold/wrenfold/pull/251 there is now a recipe that can be built with conda-build.

Once the next release is created, I think the recipe can be submitted to conda-forge.

Submitted to conda-forge here: https://github.com/conda-forge/staged-recipes/pull/27501

The PR to conda-forge was accepted. The feedstock can be found here: https://github.com/conda-forge/wrenfold-feedstock
Link to the conda-forge package


[Framework] Using some widgets as compile time constants throw Evaluation of this constant expression throws an exception

Steps to Reproduce
Expected results:
I should be able to use NavigationBar as compile time constant as it has const constructor like this
const navigationBar = NavigationBar(
        destinations: const [
          NavigationDestination(
            icon: Icon(Icons.contacts),
            label: 'Contacts',
          ),
          NavigationDestination(
            icon: Icon(Icons.people),
            label: 'Players',
          ),
        ],
      );

Actual results:
The code above does not compile throwing
lib/domains/user/contacts.dart:55:29: Error: Constant evaluation error:
      const navigationBar = NavigationBar(
                            ^
/opt/flutter/packages/flutter/lib/src/material/navigation_bar.dart:76:53: Context: The property 'length' can't be accessed on '<Widget>[NavigationDestination {icon: Icon {icon: IconData {codePoint: 57743.0, fontFamily: "MaterialIcons", fontPackage: null, matchTextDirection: false}, size: null, color: null, semanticLabel: null, textDirection: null}, selectedIcon: null, label: "Contacts", tooltip: null}, NavigationDestination {icon: Icon {icon: IconData {codePoint: 58502.0, fontFamily: "MaterialIcons", fontPackage: null, matchTextDirection: false}, size: null, color: null, semanticLabel: null, textDirection: null}, selectedIcon: null, label: "Players", tooltip: null}]' in a constant expression.
 - 'Widget' is from 'package:flutter/src/widgets/framework.dart' ('/opt/flutter/packages/flutter/lib/src/widgets/framework.dart').
 - 'NavigationDestination' is from 'package:flutter/src/material/navigation_bar.dart' ('/opt/flutter/packages/flutter/lib/src/material/navigation_bar.dart').
 - 'Icon' is from 'package:flutter/src/widgets/icon.dart' ('/opt/flutter/packages/flutter/lib/src/widgets/icon.dart').
 - 'IconData' is from 'package:flutter/src/widgets/icon_data.dart' ('/opt/flutter/packages/flutter/lib/src/widgets/icon_data.dart').
  }) :  assert(destinations != null && destinations.length >= 2),
                                                    ^
lib/domains/user/contacts.dart:55:13: Context: While analyzing:
      const navigationBar = NavigationBar(
            ^
Failed to compile application.

Flutter --version output:
Flutter 2.10.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 5464c5bac7 (6 days ago) • 2022-04-18 09:55:37 -0700
Engine • revision 57d3bac3dd
Tools • Dart 2.16.2 • DevTools 2.9.2

Hi @dvoloshyn, please provide a complete minimal reproducible code sample so that we may verify this.
Thank you

Hi @danagbemava-nc,
Sure, here it is!
import 'package:flutter/material.dart';

void main() {
  const navigationBar = NavigationBar(
    destinations: const [
      NavigationDestination(
        icon: Icon(Icons.contacts),
        label: 'Contacts',
      ),
      NavigationDestination(
        icon: Icon(Icons.people),
        label: 'Players',
      ),
    ],
  );
}

Issue is reproducible on stable and master.
I discovered that the same thing happens with NavigationRail. There may be other widgets that are affected by this but at this time, I haven't discovered any other widgets. The result of flutter analyze -v is shared below. Leaving this for further input from the team.
SN: I noticed BottomNavigationBar doesn't have a const ctor, could this be the reason why?
@dvoloshyn in the interim, you can use final instead of const and it should work just fine.

code sample
import 'package:flutter/material.dart';

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

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
   return const MaterialApp(
     home:  MyHome(),
   );
  }
}

class MyHome extends StatefulWidget {
 const MyHome({Key? key}) : super(key: key);

  @override
  State<MyHome> createState() => _MyHomeState();
}

class _MyHomeState extends State<MyHome> {
  @override
  Widget build(BuildContext context) {
  const material = Material(
    color: Colors.blue,
    child: Text('Navigation Bar'),
  );

  const bottomAppBar = BottomAppBar(color: Colors.blue);

  const navigationBar = NavigationBar(
    destinations:  [
      NavigationDestination(icon: Icon(Icons.home), label: 'label'),
      NavigationDestination(icon: Icon(Icons.home), label: 'label'),
      NavigationDestination(icon: Icon(Icons.home), label: 'label'),
    ],
  );

  const navigationRail = NavigationRail(
    destinations: [
      NavigationRailDestination(icon: Icon(Icons.home), label: Text('label')),
      NavigationRailDestination(icon: Icon(Icons.home), label: Text('label')),
      NavigationRailDestination(icon: Icon(Icons.home), label: Text('label')),
    ],
    selectedIndex: 0,
  );

   return const Scaffold(
     body: Center(child: Text('Some text'),),
   );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 2.10.5, on macOS 12.3.1 21E258 darwin-arm, locale en-GB)
    • Flutter version 2.10.5 at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5464c5bac7 (8 days ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[☠] IntelliJ IDEA Community Edition (the doctor check crashed)
    ✗ Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at https://github.com/flutter/flutter/issues.
    ✗ FormatException: Unexpected extension byte (at offset 5)
    • #0      _Utf8Decoder.convertSingle (dart:convert-patch/convert_patch.dart:1789:7)
      #1      Utf8Decoder.convert (dart:convert/utf.dart:351:42)
      #2      InputStream.readString (package:archive/src/util/input_stream.dart:207:30)
      #3      new ZipDirectory.read (package:archive/src/zip/zip_directory.dart:40:30)
      #4      ZipDecoder.decodeBuffer (package:archive/src/zip_decoder.dart:19:30)
      #5      ZipDecoder.decodeBytes (package:archive/src/zip_decoder.dart:14:12)
      #6      IntelliJPlugins._findPluginXml (package:flutter_tools/src/intellij/intellij.dart:130:44)
      #7      IntelliJPlugins._readPackageVersion (package:flutter_tools/src/intellij/intellij.dart:141:40)
      #8      IntelliJPlugins.validatePackage (package:flutter_tools/src/intellij/intellij.dart:63:35)
      #9      IntelliJValidator.validate (package:flutter_tools/src/intellij/intellij_validator.dart:103:15)
      #10     asyncGuard.<anonymous closure> (package:flutter_tools/src/base/async_guard.dart:111:32)
      #11     asyncGuard.<anonymous closure> (package:flutter_tools/src/base/async_guard.dart:109:18)
      #12     _rootRun (dart:async/zone.dart:1426:13)
      #13     _CustomZone.run (dart:async/zone.dart:1328:19)
      #14     _runZoned (dart:async/zone.dart:1861:10)
      #15     runZonedGuarded (dart:async/zone.dart:1849:12)
      #16     runZoned (dart:async/zone.dart:1780:12)
      #17     asyncGuard (package:flutter_tools/src/base/async_guard.dart:109:3)
      #18     Doctor.startValidatorTasks (package:flutter_tools/src/doctor.dart:205:9)
      #19     Doctor.diagnose (package:flutter_tools/src/doctor.dart:309:47)
      #20     DoctorCommand.runCommand (package:flutter_tools/src/commands/doctor.dart:50:48)
      #21     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1320:12)
      <asynchronous suspension>
      #22     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
      <asynchronous suspension>
      #23     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
      <asynchronous suspension>
      #24     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
      <asynchronous suspension>
      #25     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
      <asynchronous suspension>
      #26     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
      <asynchronous suspension>
      #27     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
      <asynchronous suspension>
      #28     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
      <asynchronous suspension>
      #29     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
      <asynchronous suspension>
      #30     main (package:flutter_tools/executable.dart:94:3)
      <asynchronous suspension>

[✓] VS Code (version 1.66.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.38.1

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.3.1 21E258 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 100.0.4896.127

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 2.13.0-0.0.pre.733, on macOS 12.3.1 21E258 darwin-arm, locale en-GB)
    • Flutter version 2.13.0-0.0.pre.733 at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision de6689aaa3 (2 hours ago), 2022-04-26 01:02:38 -0400
    • Engine revision 79152137a9
    • Dart version 2.18.0 (build 2.18.0-57.0.dev)
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[✓] IntelliJ IDEA Community Edition (version 2021.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin version 213.5744.122

[✓] VS Code (version 1.66.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.38.1

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.3.1 21E258 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 100.0.4896.127

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

flutter analyze -v

At this point this is working as intended (see details in https://github.com/dart-lang/language/issues/1296)
Flutter framework should probably drop const constructor from this class to make it less surprising.
/cc @lrhn @eernstg

New kinds of constant expressions are always expensive, but it does seem doable to support length on certain constant collections as a constant expression.

Interesting. So, value.length is only allowed in a const expression if value is a String? Is that the only case?
I wonder if we could get a lint that would remind us to not declare these constructors as const (https://github.com/dart-lang/linter/issues/3367).
Also, currently, if we remove the const from this class, another lint wants the const back on it: https://github.com/dart-lang/linter/issues/3366.

@dvoloshyn, you may also be interested in the following issue: https://github.com/dart-lang/language/issues/2219.


attacks, brainsick

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[a,b]

/trunk merge


Add link to @paulrayner's attribution on homepage

@paulrayner is this the place you'd prefer to link to?

This is fine. Thanks.


Citador bug

https://yadi.sk/i/o_YIw8icBhfReQ
After click citate popup at text input is hided

i dont even support citador yet

https://yadi.sk/i/99spDcdRIQiH9w
In default theme is worked

Yes i know, I don't support citador on aurora.


ARTEMIS-2201 Added tests on DEFAULT_JOURNAL_FILE_OPEN_TIMEOUT value

Added 2 tests to cover changing variable DEFAULT_JOURNAL_FILE_OPEN_TIMEOUT:

I'm starting a server and then checking that I have default value
I'm setting my random value, then starting a server and then checking that server has my value not default

@mnovak1 @andytaylor could you please check this PR?

@michalxo Would it be possible to check that value was set to JournalFilesRepository.journalFileOpenTimeout attribute?

It is a question on @feuillemorte Oleg, not me. I am not an author  :-)

@michalxo Sorry, i got confused as you were asking to check this PR :-)
@feuillemorte @franz1981 Also byteman might do the trick. Byteman rule would be triggered after write to journalFileOpenTimeout variable. Rule would call byteman helper method in test case which would set some variable to given value. Then this value would be asserted in test. I think that there are already some tests like this in Arteims test suite.


Refactor the test driver

Some time ago I attempted to make the test suite work with the SVG back-end. I then found that the current testing code is really unmaintainable at some points and figured that it had to be corrected before we have a chance of adding new functionality (such as a back-end or WebGL switch).
This patch refactors the test driver by making it more class-like and removing quite some complexity from hacks and unneeded functions. Not only does this make the code much more readable, it also allows us to extend the code in a cleaner way because we got rid of the window.load dependency, innerHTML usages and many callbacks. Not all callbacks have been removed because the remaining ones are not too invasive and this patch can be seen as a major first step in cleaning up the test driver.
@Snuffleupagus Would you be up for reviewing this? It is not as daunting as it might look at first sight because a lot of it is just moving code around. The other changes are largely the same as the other refactoring PRs we have done. Reviewing with ?w=1 helps a bit, especially for the third commit.

Desarrolladores y líderes de Mozilla, que son travestis culo!
Alguien debe colgar ustedes para arriba en sus propias bolas y dejar que su perro muerda su caricatura de una polla!
Posteriormente deben ponerlo tiempo que sea necesario por la garganta hasta que traga a sí mismos en el suicidio!
Ustedes Mozilla está ... Estúpido de mierda coños!
Developers and leaders of Mozilla, which are shemales ass!

They should then put it long as needed by the throat until he swallows themselves in suicide!
You Mozilla is...

At this point it's still anecdotal evidence, but it appears that with these patches applied (and rebased to tip) the runtime of browsertest increased with approximately 1 minute for me.

/botio test

/botio-linux test

/botio test

/botio test

This last run was with one PDF file (specifically pdfkit_compress.pdf) changed to make sure that failures get detected. I have removed that commit now as it was only meant for a test.

/botio test

Review progress:

[ ] Refactor test slave
[ ] Clean up the test driver
[ ] Refactor test driver to be more class-like
[ ] Improve driver code structure
[ ] Implement an option to disable automatic scrolling

/botio test

@Snuffleupagus Thank you for the review! You made some good points and I have addressed all of them. I have also moved some changed from the fourth commit to the third commit, where they indeed belonged in the first place. I have run the tests locally and verified that the results are the same as before today's changes and I have run the tests here again too.

/botio test

/botio-windows test

Let's check that makeref-ing still works correctly before merging.
/botio makeref

/botio-windows makeref

Since everything still appears to work, both on the bots and locally, let's do this!
Thank you for the patch!


Fix action selector and action profile to apply the group/member tables only on base table hit

Action selector and action profile enables 2 or 3 table conditional lookup
Each table implementing action selector or action profile is split into 3 and 2 tables respectively. And the base table apply statement is converted into the new tables applied in sequence.

Prior to this PR,  group and member tables were unconditionally applied
table.apply()     --> table0.apply()
group_table.apply()
member_table.apply()
But this disallows any direct match on base table.
This PR add conditions for applying the group and member tables
The table apply can occur as independent MethodCallStatement, within IfStatement and SwitchStatement. Code comments explain how each of these cases are converted

Closing as upstreamed


Question: why still OS binaries?

If it is said to use protoc-jar, why still OS binaries e.g. in release notes updates?

Because protoc-jar is still OS specific. (It's a bundle of protoc binaries, not a pure Java impl)

OK, have not seen the note in README


push initial poc of single table strategy for event flagging

What does this pull request do?
Required.
What is the intent behind these changes?
Required.

After discussions internally, we've agreed that no additional data capture is required. Instead of making this intelligent and un-flagging per flag, we're going to un-flag per visit which for now will handle everything we need.
JIRA link for new approach: https://dsdmoj.atlassian.net/browse/VB-4349


chore: add Cilium images for v1.12.0

Add v1.12.0 images for cilium, cilium-operator, and cilium-operator-generic.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Add latest Cilium images.
Requirements:

[x] uses conventional commit messages

Special notes for your reviewer:
cilium/operator-generic is a new image that we started publishing recently.
Release note:
Add v1.12.0 images for cilium, cilium-operator, and cilium-operator-generic.

will re-open from a branch within the repo to avoid auth errors in build pipeline


fix(curriculum): added test using a tree that is not a binary search tree

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

The challenge description states that the value of a left child node in a binary search tree should be less than the parent node value. The current solution does not set isBST to false if the left.value === node.value. I fixed this.
To test that the solution fails if there is a left node value that is equal to its parent value, I added another test with a tree where one node's left value is equal to its parent node value.
This PR is not targeted to close a specific open issue.

Thank you for your contribution to the page! 👍
We are happy to accept these changes, and look forward to future contributions. 🎉


Fibonacci Series Without Recursion

I have created this method to print fibonacci series upto n numbers without recursion because recursion was very confusing to me. Hope You Like It ^_^

Thank you for your PR!
Unfortunately your solution is not in the scope of this repository :/
The goal is to find creative/abstract new solutions to FizzBuzz, not the Fibonacci series.
Please consult the readme for more information and see The top 5 samples here.
Thanks anyway! :)


More detail info needed

For this document it mentioned using dynamics 365 as a service to manage product source, but as I know dynamics 365 using dataverse as it's storage which is not listed in the picture.
So could you please add more detail design in this document about dynamics 365 to azure microservice without involving dataverse?

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

ID: 34ed51e6-265e-aae0-f552-0900a345b3be
Version Independent ID: 34ed51e6-265e-aae0-f552-0900a345b3be
Content: Scalable cloud applications and SRE - Azure Architecture Center
Content Source: docs/example-scenario/apps/scalable-apps-performance-modeling-site-reliability.yml
Service: architecture-center
Sub-service: example-scenario
GitHub Login: @martinekuan
Microsoft Alias: subhajch

@jarvan-jiang
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@Subhajit

@SubhajitChatterjee

@jarvan-jiang - You are correct in your understanding that Dynamics 365 Apps are built on top of Dataverse.
Microsoft has released the Common Data Model (Schema) that encompasses the majority of the entities required for your business apps.
https://microsoft.github.io/CDM/
It was not depicted in the diagram as the intent was to give a high-level view of the concept of Polyglot persistence using which you are able to bring in the best of all platforms for your solution architecture. Dynamics 365 offers a powerful suite of Apps that you can leverage out of the box for your business workflows.
Refer here on the public documentation on how to setup a product catalogue:
https://learn.microsoft.com/en-us/dynamics365/sales/set-up-product-catalog-walkthrough
Regarding your point on D365 without Dataverse, I believe you were referring to Power Platform. While it is possible to build standalone applications using the Power Platform, but having Dataverse in the mix gives you a lot of flexibility and extensibility that will be required in an enterprise context when building business applications. Refer below for the licensing differences.
https://learn.microsoft.com/en-us/power-platform/admin/pricing-billing-skus
Hope I was able to clarify your query.
Thanks
Subhajit

Thank you @Subhajit-Chatterjee-MS and @jarvan-jiang.  I've asked @Subhajit-Chatterjee-MS to consider some updates to the article to help clarify this for all readers.  @jarvan-jiang, please confirm the information provided by @Subhajit-Chatterjee-MS helps clarifies your query.
#please-close


chore: create plans directory under tests

Related to #98
As we know that monorepo is not working atm due to some shenanigans, this new style of creating plans is making sure we can continue sorting out new test plans under 1 repo

Tested locally - works as expected


[feat] Template ERC20 rewards deposit

Add the functionality to deposit the reward from the reward_token in the add_template function call. Make sure to revert if the deposit fails at any step.
References

Template add_template func
ERC20 deposit example

@b-j-roberts  may i be assigned to this issue?


Context propagation for query logging

Problem
Currently query logs can not relate to requests or a parent context from which they were invoked from. This means solutions like https://github.com/iamolegga/nestjs-pino or as well datadog tracing https://github.com/DataDog/dd-trace-js/issues/1244 are not able to work properly.
Suggested solution
Context propagation into query logging should work properly. Sadly I'm quite new to nodejs and therefore aren't able to further specify how this should happen. Also not sure if the architecture of prisma is a blocker here (separate query engine process, and whether this gets simpler once n-api is used)
Alternatives
I've looked at https://github.com/Jeff-Lewis/cls-hooked (which nestjs-pino uses under the hood) so not a real alternative, but tried to understand whats happening here.
Additional context
Slack convo: https://prisma.slack.com/archives/CA491RJH0/p1623345269439900

Duplicate of https://github.com/prisma/prisma/issues/6882

If you ignore the middleware aspect of this that you assumed @Sytten, this is essentially about e.g. creating a query id (or request id) and logging that with each query, so any external tooling can pick those out of the logs and correlate Prisma Client query to logged SQL query.

Possibly also duplicate of #6519 and #5956
Would assume it shouldn't really depend on which tracing solution is used, but the end result should be queries being traced which are as well correlated to the trigger on prisma client side (and furthermore the root of the prisma client call -> API Request, Background Job, etc).

same issue + 1
any solution?

Hi, having the same issue.
Is there any plan to create something like this?

Its already on the roadmap of prisma https://www.notion.so/Support-Tracing-in-Prisma-Client-c0afd7599022435da2b8fc05c30cd1c0

@tak1n this doesn't require tracing support in Prisma, per se. The issue is that since Prisma queries are sent to a rust engine, all of the context from the dd-trace library added with https://nodejs.org/api/async_hooks.html#async-hooks is lost in the $on() callback.

As I suspected, you can already trace today in Prisma:

prisma.$use(async (params, next) => {
  return await tracer.trace('prisma.query', async () => {
    // not logging params.args, which may contain personally identifying or confidential information
    logger.debug('Prisma query', {
      model: params.model,
      action: params.action,
      runInTransaction: params.runInTransaction,
    });
    const result = await next(params);
    return result;
  });
});

Tracing is entirely supported today, and the best way is w/ Prisma middlware, although you don't get raw SQL but that is tangential to tracing and a query can be replicated locally to debug the SQL if needed.

I tried this approach:
prisma.$use(async (params, next) => {
  return await tracer.trace('prisma.query', async (span) => {
    span?.setTag('model', params.model);
    span?.setTag('action', params.action);
    span?.setTag('runInTransaction', params.runInTransaction);
    logger.debug('Prisma query', {
      model: params.model,
      action: params.action,
      runInTransaction: params.runInTransaction,
    });
    const result = await next(params);
    return result;
  });
});

The spans are also taken out of context of the parent span from where I sent my Prisma query.
  try {
    throw new Error();
  } catch (e) {
    console.log(e);
  }

the above debug logging shows the stack trace lost the context that I called my prisma query from a particular GQL resolver / file:
Error:
    at /Users/jribakoff/groundwater/dist/apps/api/webpack:/groundwater/apps/api/src/app/db.ts:16:11
    at consumer (/Users/jribakoff/groundwater/node_modules/@prisma/client/runtime/index.js:49914:20)
    at /Users/jribakoff/groundwater/node_modules/@prisma/client/runtime/index.js:49920:76
    at runInChildSpan (/Users/jribakoff/groundwater/node_modules/@prisma/client/runtime/index.js:49133:12)
    at /Users/jribakoff/groundwater/node_modules/@prisma/client/runtime/index.js:49920:20
    at AsyncResource.runInAsyncScope (node:async_hooks:199:9)
    at PrismaClient._request (/Users/jribakoff/groundwater/node_modules/@prisma/client/runtime/index.js:49919:86)
    at /Users/jribakoff/groundwater/node_modules/@prisma/client/runtime/index.js:46474:25
    at _callback (/Users/jribakoff/groundwater/node_modules/@prisma/client/runtime/index.js:46233:52)
    at Proxy.then (/Users/jribakoff/groundwater/node_modules/@prisma/client/runtime/index.js:46240:14)

In my opinion the proposal from @matthewmueller  in https://github.com/prisma/prisma/issues/6882#issuecomment-1175427037 doesn't have anything to do with solving this issue. I do not want to manually get the parent span and pass it into every Prisma query. I just want the middleware to run from within the context where I called my Prisma query.

or production ready (errors will never be surfaced or logged).

Can you please make sure an issue with more information for this exists? Thanks.

i've discovered that if you use the binary query engine instead of the default Node-API based one, then the async context is not lost in the client.$on('query', handler) handler.  i don't know why this is, have been reading the LibraryEngine and BinaryEngine code to try to find a difference that might matter, but so far haven't figured it out.
it would be nice if the docs would talk a little more about the differences between those engines.  the only thing it really says is "The Node-API library approach is recommended since it reduces the communication overhead between the Prisma Client and the query engine."  but that makes me wonder why the binary engine is even an option at this point?

but that makes me wonder why the binary engine is even an option at this point?

Because sometimes the Node-API library gets something wrong, that works fine with the binary engine. Then it is a temporary workaround to use the binary engine. It is not recommended to use in other cases, and might be removed at any time.

@janpio would you consider this loss of async context an instance of the Node-API library getting something wrong?  if so, can it be fixed?  or is there some fundamental limitation with the Node-API approach that will never allow this to work?  i still don't really understand why the query event handler gets invoked in a different async context than that which initiated the prisma query (especially since it's only the case with the Node-API engine but not with the binary engine)

Right now we do not give any expectation that the async context would be kept - it is not part of our documented API -, which is why this feature request exists and tracks this expectation (or other solutions to achieve the same outcome). So right now this seems to be undefined to me. If you really need it, you can use the binary to work around that - but be aware that you are off the really recommended path then and might have other negative (or positive) effects that are not documented.

Right now we do not give any expectation that the async context would be kept - it is not part of our documented API -, which is why this feature request exists and tracks this expectation (or other solutions to achieve the same outcome). So right now this seems to be undefined to me. If you really need it, you can use the binary to work around that - but be aware that you are off the really recommended path then and might have other negative (or positive) effects that are not documented.

I tried to use the binary to work around that but it does not really work.
I use NestJS-CLS package, for saving information on the async context, but when I try to access it on query event.
    this.$on<any>('query', async (e) => {
      this.logger.debug({query: e.query, params: e.params});
      const info = this.clsService.get("info")
    });

The clsService return undefined.
My prisma engine was loaded with binary
✔ Generated Prisma Client (4.15.0 | binary) to ./node_modules/@prisma/client in 553ms
any idea?

Hi @janpio, I really want to contribute to that. I commented above and the solution you suggested has not worked, how can I contribute to the project, or have a solution for that

@janpio would you consider this loss of async context an instance of the Node-API library getting something wrong? if so, can it be fixed? or is there some fundamental limitation with the Node-API approach that will never allow this to work? i still don't really understand why the query event handler gets invoked in a different async context than that which initiated the prisma query (especially since it's only the case with the Node-API engine but not with the binary engine)

Have you managed to make it work?

Have you managed to make it work?

@EladIsraeli sorry i missed your question until now.  i've been away from this problem for long enough now that i don't recall the details, but i recall a few things that might help you here if you're still stuck and still wanting to work around it with the binary engine.
i was using the cls-hooked library, and it includes a bindEmitter function that i know i experimented with, but don't recall whether it was necessary to make my workaround work.  but i believe that function exists because EventEmitter handlers don't get fired with the proper async context by default, so that function somehow propagates the context to them.  if NestJS-CLS has some similar kind of helper, you might need to apply it to your prisma client.

The issue is that since Prisma queries are sent to a rust engine, all of the context ... added with https://nodejs.org/api/async_hooks.html#async-hooks is lost

This is a perfect summary by @joshribakoff-sm.
In short

The Prisma engine written in Rust loses access to the Node.js context from which a query was triggered, so these Prisma features can't help solve this problem:

$on()
$use() middlewares
$extends() extentensions

As a result, a request-specific context can't be shared when a database query is being executed. It doesn't work with

Native Node.js AsyncLocalStorage
cls-hooked
continuation-local-storage
and similar request-specific storage libraries that return undefined

One workaround I found is using the Prisma preview feature that allows the use of native Node.js database driver adapters to perform queries instead of the Prisma engine. Because these database adapters are executed in Node.js, async_hooks should just work fine.
You can find an example using https://github.com/brianc/node-postgres in @bemi-db/prisma that allows tracking all database changes and stitching them with request-specific context (user ID, API endpoint, etc.)

A useful workaround that helped me was to log the Prisma operation instead of the SQL using "query $allOperations":


Multiple paragraphs

Summary
Hey, It will be great if somehow I could add more than one para with a single command.
Motivation
Sometimes, I need to show multiple paras so I do not want to type the same command several times.
Instead, it will be great to add 4-5 paras with a single command.
Additional Context
This will be a good and simple addition to add multiple paras with a single command.
You could make insert multiples paras as an additional command to add multiple paras.
This would be easy if 5 random paras are taken from scriptPara in beeMovieScript.js and added to the workspace.

That's a great idea! This command could be named something like jazz.multiplepara and could ask the user how many paras to insert. Do you want to take this up?

Yes, I could work on this.
Assign this to me.


Multi Gpu support in keras gives error: Creating a partition for /device:CPU:3 which doesn't exist in the list of available devices

I am trying to build multigpu support into my model. The code is as follows :
with tf.device('/cpu:0'):
    # creating a model
multi_gpu_model = keras.utils.multi_gpu_model(model, gpus=2, )
multi_gpu_model.compile(loss='cosine_proximity', optimizer='nadam', metrics = ['accuracy'])
try:
    multi_gpu_model.fit_generator(
        sequential_generator('/home/jindal/notebooks/witter_dataset_sequences_20m', batch_size, total_lines),
        steps_per_epoch=steps_per_epoch, epochs=epochs,callbacks=[WeightsSaver(model, 200)]
    )
except Exception as e:
    print(e)

`
The error that I get is:
creating a partition for /device:CPU:3 which doesn't exist in the list of available devices. Available devices: /device:CPU:0,/device:XLA_CPU:0,/device:XLA_GPU:0,/device:GPU:0,/device:GPU:1,/device:GPU:2,/device:GPU:3
What is it that I did wrong?

The examples provided by in the documentation also result in the same error for me

I don't know if this will or will not help, but is there supposed to be a comma after gpus=2?  I have never used one.
try:     model=multi_gpu_model(model, gpus=2) except:      pass

@drsxr  Did not work.


clean integration & test of workspaces 'on top'

Jochen and I disagreed about how to represent that for ros-deb-builder, but I definitely want to see my approach with a separate parameter working as well before we decide in a pull-request. :)
I guess there's just some details I didn't figure out last time I tried.

Done. It works well as currently pushed in the test branch (ignoring the build failure due to my own stupidity):
      - uses: v4hn/ros-deb-builder-action/build@rosotest
        with:
          ROS_DISTRO: ${{ env.ROS_DISTRO }}
          DEB_DISTRO: ${{ env.DEB_DISTRO }}
          ROSDEP_SOURCE: |
            rosdep.yaml
            https://raw.githubusercontent.com/v4hn/ros-o-builder/jammy-one/local.yaml
          DEB_REPOSITORY: |
            deb [trusted=yes] https://raw.githubusercontent.com/v4hn/ros-o-builder/jammy-one/ ./

I don't particularly like the fact that we have to specify almost the same url twice for debs and rosdep although both come from the same source generator.
@jspricke Any opinion on adding a separate key (e.g. COMPACT_REPOSITORY, DEPDEB_REPOSITORY, ...) to pass https://raw.githubusercontent.com/v4hn/ros-o-builder/jammy-one/ to the action only once so that the action would fill in the other two fields respectively?
Alternatively I could imagine parsing either of them to generate the other (and validate whether the entries are valid of course), but it wouldn't be very clean.
Either way I clearly prefer a separate field for DEB_REPOSITORY over adding sbuild flags the way you proposed.

I don't particularly like the fact that we have to specify almost the same url twice for debs and rosdep although both come from the same source generator. @jspricke Any opinion on adding a separate key (e.g. COMPACT_REPOSITORY, DEPDEB_REPOSITORY, ...) to pass https://raw.githubusercontent.com/v4hn/ros-o-builder/jammy-one/ to the action only once so that the action would fill in the other two fields respectively?

You could define it as an variable and reuse inside the yaml.

Alternatively I could imagine parsing either of them to generate the other (and validate whether the entries are valid of course), but it wouldn't be very clean. Either way I clearly prefer a separate field for DEB_REPOSITORY over adding sbuild flags the way you proposed.

Can you give reason why you prefer it? Note that SBUILD_CONF will not go away as there are many more option and some, like EXTRA_REPOSITORY_KEYS can also consume the URL. So your proposal is mainly syntactic sugar leading to a less expressive interface. Given that the Action configuration is already rather short and will probably not edited a lot, I don't see much reason to diverge to a new interface.

You could define it as an variable and reuse inside the yaml.

True, that's probably enough.

Can you give reason why you prefer it? Note that SBUILD_CONF will not go away as there are many more option and some, like EXTRA_REPOSITORY_KEYS can also consume the URL

Paradigms of interface design. There's always a trade-off between concise statements, interface bloat, and customizability.
Adding another deb repository seems a
Yes, it probably makes sense to keep the parameter as it's an key customization point inside the action.
The three examples you gave for using it shouldn't be there in my opinion though:

make build verbose. verbose is the default now. If forcing quiet mode can still be done through that parameter that would be interesting use
custom syntax over everything

It probably makes sense to keep the SBUILD_CONF parameter as it is a key customization point inside the action. Even so, the three examples you gave for using it shouldn't be there in my opinion:

make build verbose. verbose is the default now. If forcing quiet mode can still be done through that parameter that would be interesting use of the argument
adding repositories (the argument I added), see above
adding keys for repositories. I didn't have that use-case yet, but I clearly prefer the same approach (e.g., a DEB_KEYS argument) for the same reasons.

see man sbuild.conf for a lot more options.

The one motivation you definitely not accept (and I see why, though I still think your proposed solution is not really good either) is that I currently reuse the deb repositories on the host to get access to setup_files and ros_environment and the syntax needed for SBUILD_CONF would just make that harder for no reason to extract it without redundant specification.

I see your problem but I think reusing the same variable for different things here is rather confusing and could lead to unforeseen consequences so I would rather have that as an extra option. I'm still undecided if we should allow adding custom repos to the host system or allow setting extra variables for bloom or even clean up the package.xml files. Most of the problems in that area seem to be where people missuse the package.xml to work around rosdep so maybe it is enough to provide proper rosdep keys. Would be great if you could open an issue with the action for this use case and add some samples.

see man sbuild.conf for a lot more options.

I explicitly asked you before what you think people will regularly use it for. These were the three use-cases you gave. ;)
I'm aware that there are many configuration options and as I said the argument should be kept to allow users to add them. But I'm also saying, that it shouldn't be necessary to specify this "advanced" argument for the envisioned regular workflows. People would just copy&paste more without understanding semantics.

I see your problem but I think reusing the same variable for different things here is rather confusing and could lead to unforeseen consequences so I would rather have that as an extra option.

I don't want to stress this point because it's still unclear whether this is relevant once everything is cleaned up, but it is not different. It's exactly the same and even simpler because I just dump regular sources.list contents into a regular sources.list file. sbuild just needs the lines wrapped in syntax to log and hand them to the build env. :-)

even clean up the package.xml files. Most of the problems in that area seem to be where people missuse the package.xml to work around rosdep so maybe it is enough to provide proper rosdep keys

The ROS-O approach I'm working on right now is to first of all use everything that is there and change only things that really need changing for newer debian systems.
Feel free to haunt OR to add correct python3 resolve values to map, e.g., python-yaml to python3-yaml on the correct target platforms. I have no idea why they didn't do it instead of providing separate keys.
But I will not run around and discuss with all the individual package maintainers that they should stop using the if attribute in their package.xmls (expect a low response rate anyway) and that it works with the debian rosdep package if you use the simpler entries. On the other side, I don't think it's helpful in any way to we fork all packages using it into ros-o to patch them there either.

I don't want to stress this point because it's still unclear whether this is relevant once everything is cleaned up, but it is not different. It's exactly the same and even simpler because I just dump regular sources.list contents into a regular sources.list file. sbuild just needs the lines wrapped in syntax to log and hand them to the build env. :-)

It is not different because in your case the VM and target system are both Ubuntu 22.04, that does not generalize.

The ROS-O approach I'm working on right now is to first of all use everything that is there and change only things that really need changing for newer debian systems. Feel free to haunt OR to add correct python3 resolve values to map, e.g., python-yaml to python3-yaml on the correct target platforms. I have no idea why they didn't do it instead of providing separate keys. But I will not run around and discuss with all the individual package maintainers that they should stop using the if attribute in their package.xmls (expect a low response rate anyway) and that it works with the debian rosdep package if you use the simpler entries. On the other side, I don't think it's helpful in any way to we fork all packages using it into ros-o to patch them there either.

As I said, I'm open to discuss different options. For using rosdep it is enough to override the keys for the build, I used the same approach before.

It is not different because in your case the VM and target system are both Ubuntu 22.04, that does not generalize.

Yes, and I concede that point. Though you conceded that it will likely work on any debian-based system we might build for. ;)
Staying with my current paradigm, the "proper" solution would be to setup an environment for the target system, ro mount the workspace and install setup_files and ros_environment in there just to sort the list of packages with catkin_topological_order... Which is a mess as well.

Yes, and I concede that point. Though you conceded that it will likely work on any debian-based system we might build for. ;)

That is for your special setup_files case.

It looks to me that one major point of disagreement is the "interface boundary" for the user. As I understand it, Jochen considers sbuild the public build interface, just as it is for regular Debian packaging, and the action is just a thin wrapper. Michael considers the action itself a public interface and sbuild an implementation detail.
From Jochen's perspective, adding more options just adds redundancy that complicates the interface and makes the wrapper needlessly "thick". From Michael's perspective, the action is too spartantic and requires to much "fiddling" with the inner details, i.e. the sbuild implementation.
Is that about right?

I believe Jochen and me were quite aware of our respective positions, as always. We have similar discussions every now and then. :grin: Thanks for spelling it out as this is a public issue!

ros-o-overlay now implements this sufficiently for my use-cases.


Bump azservicebus to v1.6.1

bump azservicebus to v1.6.1. this version includes a fix to the slow sending problem: https://github.com/Azure/azure-sdk-for-go/issues/21684

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.363%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
642

Relevant Lines:
761

💛  - Coveralls


Is time series saves my data for future retrieval ?

Right now I am planning to pump my data in to time series insights. but additionally do I need to store it in some cosmoDB for future retrieval. ? or time series can act as datastore?

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

ID: e98db64d-9617-991a-4145-3f5cc280d966
Version Independent ID: d6d4e34a-25ad-7152-85a9-a0576053f4ac
Content: How to add an IoT Hub event source to Azure Time Series Insights
Content Source: articles/time-series-insights/time-series-insights-how-to-add-an-event-source-iothub.md
Service: time-series-insights
GitHub Login: @ashannon7
Microsoft Alias: anshan

Can I query the data using c#? And get mean, aggregation calculations?


Add instances for :+: and :*:

Continuing #21.

Did I accidentally delete the branch on this?

@jhartzell42 I just couldn't push to it.

@phadej Please review this.

Amdended and merged in #48  and released https://hackage.haskell.org/package/some-1.0.4