[FR]: Is out_dirs and output_dir for webpack_cli supported?

What is the current behavior?
Minimal repro (but unsure if user error): https://github.com/aspect-build/rules_js/pull/661/files
Using rules_nodejs + yarn_install, typically, we can build all bundles for webpack.config.js via output_dir = True
I see that the equivalent rules_js bin.webpack_cli has an output_dir option, but it seems to not emit any bundles.
# note: rules_nodejs yarn_install'd output_dir = True is sufficient for outputting
#
# `bazel build //examples/webpack_cli:bundle_dir`
bin.webpack_cli(
    name = "bundle_dir",
    srcs = [
        "webpack.config.js",
        ":lib",
    ],

    # Emits an `ls bazel-bin/examples/webpack_cli/bundle_dir`, but contents empty
    output_dir = True,

    # Emits an `ls bazel-bin/examples/webpack_cli/raytest`, but contents empty
    out_dirs = ["raytest"],
    args = [
        "--config webpack.config.js",
    ],
    chdir = package_name(),
    log_level = "debug",
)

Describe the feature
If my minimal repro isn't user error, should there be parity between webpack_cli in rules_js and rules_nodejs?
Fund our work

[ ] Sponsor our open source work by donating a feature bounty

The issue here was a mismatch between the output directory configured in the BUILD file and the output directory configured in the webpack config in the minimal repro.
See https://github.com/aspect-build/rules_js/pull/661#issuecomment-1341910713 and https://github.com/aspect-build/rules_js/pull/661#issuecomment-1381422371


Migration script for ALD

Why

For devop, they would be using this script
For registering all essential contracts for PaymentTx V1. We would also need to audit the script in my opinion since we are using some dependency inject in between contracts. If wrong dependency is put, the system would not work as expected.

Successful Criteria

Implement migration script for ALD that would be do for this round of audit
Update README

close this as #298 is merged


4th feedback session

All:

[x] Make the dashboard more interactive
[x] Add filters to dashboard

Gone over required changes as per feedback.


feat: avoid OS page cache on macOS

This adds F_NOCACHE to all the FDs on mac.
It's not clear whether this is a good idea as it doesn't seem to actually be more performant. But it'll give us more consistency with any app-level caching we implement cross-platform.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#376
#375  👈
#374
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rphmeier and the rest of your teammates on  Graphite

Merge activity

Sep 2, 11:01 AM EDT: @rphmeier started a stack merge that includes this pull request via Graphite.


Add init(light:dark:) to NSColor and UIColor

This extension allows to create an NSColor or UIColor with different colors for light mode and dark mode. I created separate NSColorExtensions.swift and UIColorExtensions.swift files, because NSColor and UIColor use different APIs for this problem and can't be unified.
I couldn't figure out how to create a test for macOS, because it uses NSAppearance instead of UITraitCollection. Any suggestions?
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 5.0.
[x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[x] I have added a changelog entry describing my changes.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 589 tests, with 0 failures (0 unexpected) in 11.991 (13.953) seconds

:book:
tvOS: Executed 564 tests, with 0 failures (0 unexpected) in 3.316 (5.104) seconds

:book:
macOS: Executed 422 tests, with 0 failures (0 unexpected) in 1.125 (1.468) seconds

  Generated by :no_entry_sign: Danger

I'd like to add a test for NSColor, but I don't know how to set an NSAppearance without having a view hierarchy. Any suggestions?

@MaxHaertwig I don't think there's any way around the view hierarchy. I ran this in Playgrounds and it works:
let color = NSColor(light: .red, dark: .blue)
let view = NSView()
view.wantsLayer = true

NSAppearance.current = NSAppearance(named: .aqua)
view.layer?.backgroundColor = color.cgColor
view.layer?.backgroundColor == NSColor.red.cgColor

NSAppearance.current = NSAppearance(named: .darkAqua)
view.layer?.backgroundColor = color.cgColor
view.layer?.backgroundColor == NSColor.blue.cgColor

Thanks @guykogus, I added a test.

@guykogus, @LucianoPAlmeida do you know why the travis build failes?

Seems something on Danger, I'll take a look  as soon as possible :))

@MaxHaertwig check that NSColorExtensions.swift was added to the SwifterSwift-macOS target?

It belongs to SwifterSwift-macOS .

I fixed the error. However, I don't know why codecov is complaining. Any ideas?

@MaxHaertwig codecov can be a bit strange sometimes. I wouldn't worry about it. It's complaining about a decrease in code coverage from a recent UIImage extension.

Is it possible to run the Travis build on a macOS 10.15 machine?

@MaxHaertwig not yet https://docs.travis-ci.com/user/reference/osx/

@LucianoPAlmeida @guykogus
I think this method should be changed to the following to be more compatible.
convenience init?(light: UIColor?, dark: UIColor?) {
    guard let light = light, let dark = dark else {
      return nil
    }

    if #available(iOS 13.0, *) {
      self.init(dynamicProvider: { $0.userInterfaceStyle == .dark ? dark : light })
    } else {
      self.init(cgColor: light.cgColor)
    }
  }

Otherwise you will encounter such errors in projects with a minimum deployment version lower than iOS 13.

The reason for using optional variables is to be compatible with the colors loaded from the bundle.

What does your code look like that the colours would be optional?
The main issue with changing this to be a nullable initialiser is that it's a breaking change. You could just make dark optional, which may help and still keeps things simple.
convenience init(light: UIColor, dark: UIColor?) {
    if #available(iOS 13.0, tvOS 13.0, *),
        let dark = dark {
        self.init(dynamicProvider: { $0.userInterfaceStyle == .dark ? dark : light })
    } else {
        self.init(cgColor: light.cgColor)
    }
}

@guykogus
Because I use R.swift, loading the color from the bundle (via init(named:)) will return an optional value. Your suggestion is great, I did not expect it to cause a breaking change.

My suggestions are usually great 😏 (that's a lie, never listen to me)
Feel free to create a PR 🙂

😆 Thank you, will do it shortly.


[FEAT] Support for "Desktop Virtualization User" role assignment

Community Note

Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
Unless there are reasons not to, it would be good if the module takes user(s) or group(s) as (optional) input variable and assigns the roles in scope of the application group.
From https://learn.microsoft.com/en-us/azure/developer/terraform/configure-avd-rbac
data "azurerm_role_definition" "role" { # access an existing built-in role
  name = "Desktop Virtualization User"
}

resource "azurerm_role_assignment" "role" {
  scope              = azurerm_virtual_desktop_application_group.dag.id
  role_definition_id = data.azurerm_role_definition.role.id
  principal_id       = azuread_group.aad_group.id
}

which was also suggested in https://github.com/hashicorp/terraform-provider-azurerm/issues/14146#issuecomment-971444726
It would allow to complete the AVD configuration using the module.
New or Affected Resource(s)/Data Source(s)
azurerm_role_assignment
Potential Terraform Configuration
No response
References
No response

Hello @mloskot ,
Thank you for opening this issue. We will look into it.

Hello @mloskot ,
Apologies for the delay.
Your suggestion is available in https://github.com/claranet/terraform-azurerm-avd/tree/v7.3.0. Thanks for the idea.

Hi @zfiel That's awesome, thank you very much! I will test it out soon.
I'm closing this issue as completed then.


enable per-equation discretiation

depends on #128
dict of {variable: discretisation} passed as input to base discretisation class.
The discretiation class passed in the dict handles things like gradient/divergence discretisation + broadcasting

Should compute_diffusivity which finds the value of the diffusion coefficient at the locations between nodes be specific to the 'FiniteVolume' method? If we were to implement a FiniteDifference method, we could still call the same compute_diffusivity function to find the the values at the locations between nodes (even though the nodes are now shifted). Not sure of the requirements for FiniteElement

@tinosulzer suggested that instead of providing spatial methods per equation, we give a spatial_method to each variable.
With the per equation method we encounter a problem when we try discretise the dict of variables which is of the form:
model.variables = {"c", c, "N", N}

There is no eqn key id to determine which spatial method we should use.

I would also suggest giving spatial_method the variable names as keys, e.g. if we define
c = Variable("concentration", domain=whole_cell)

then the spatial method could have keys
spatial_method = {"concentration": ..., ...}

We could even make more specific variable classes like Concentration , Potential, etc that are subclasses of Variable but give the right name

that sounds reasonable. I guess when you pick a certain set of basis functions, you are picking them to represent a certain variable, rather than an equation, so I think it makes sense.

then the spatial method could have keys
spatial_method = {"concentration": ..., ...}

This seems inconsistent with what we are doing for model.rhs and model.algebraic? We have used the variable object as the key for these, why not spatial_method as well?

Yes, good point, better to keep it consistent.


Add thymeleaf dialect

We now use a Thymeleaf dialect. This makes the use of layouts a bit more intuitive and we can now include JS files only on specific pages.
It is not necessary to make a thorough review here. On all HTML pages I had to change the header section.
We now have a new dependency and groovy is now also on the classpath for the productive code (previously only for testing).

 Include JavaScript and CSS files only on the pages where they are actually needed.


rebase code in workflow CI

Signed-off-by: Di Xu<EMAIL_ADDRESS>
What type of PR is this?
kind/workflow
What this PR does / why we need it:
Rebasing codes with origin/main during CI
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Codecov Report

Merging #231 (7fd47dc) into main (a9950f0) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #231      +/-   ##
==========================================
- Coverage   10.26%   10.19%   -0.08%
==========================================
  Files          39       39
  Lines        4237     4237
==========================================
- Hits          435      432       -3
- Misses       3771     3773       +2
- Partials       31       32       +1

Impacted Files
Coverage Δ

...ernet/clusternet/pkg/hub/apiserver/shadow/utils.go
89.28% <0.00%> (-10.72%)
:arrow_down:

Continue to review full report at Codecov.

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


L1 layout

Preliminary layout for L1 page which includes:

L1 page template
Featured cards in stack layout
Single column text only list

Fix #272, #219
Test URLs:

Before: https://main--hlx-test--urfuwo.hlx.page/draft/rootpea/219-l1-sample-page
After: https://272-featured-articles--hlx-test--urfuwo.hlx.page/draft/rootpea/219-l1-sample-page

General question: how much overlapping of l1 and l2 styles is there? If the overlapping is high, maybe we can refactor the CSS

I would say for now still a high degree but L1 is just in infancy so I expect L1 template to diverge from L2 and we anyways don't want to send extra bytes for L2 styles to L1 page. But yes, I agree we should revisit later point in time if we can merge common styles.

we should revisit later point in time

Let's do the opposite, unify now. Lets not add stuff we "maybe need later". YANGI & KISS are our friends.

we should revisit later point in time

Let's do the opposite, unify now. Lets not add stuff we "maybe need later". YANGI & KISS are our friends.

Looking at the L1 design we might be adding more L1 specific styles in same template which will maintain both styles so we'll be sending extra bytes for styles not required on the page but sure we can separate the template later. But that will also require changing the page metadata to change the template if required.
For now I'll merge the templates.

For now I'll merge the templates

+1 if we later see a case we can carve out thinks. Also changing metadata for one or 2 pages is not an issue


Bump version & add icon updating via constructor

@aretecode can you remove the "version bump" part? We're going 0.6.x now.


whereILike and orWhereILike don't work with sqlite3

When using whereILike in query building, Knex generates a query that contains the word "ilike" not recognized by sqlite3, thus provoking an error. whereILike should generate a regular "like", already case insensitive in sqlite3.
Error example:
select * from `video` where `location` ilike '%airon%' limit 200 - near "ilike": syntax error
It should have been
select * from `video` where `location` like '%airon%' limit 200
Thanks

I was working on this, but I'm not sure where to add the tests, any guidance on that would be appreciated


Add bounds on number of elements in api/v1/log/entries/retrieve.

The API definition for retrieve does not specify an upper bound for number of entries in the request. It is trivial to construct a request that takes O(many seconds) to return with a response size O(MB). Adding upper bounds on number of entries per request will let us offer an achievable SLO for this endpoint.

This is the search index. I think we'll also need to add pagination if we do this, we'll need a way to handle retrieving everything.

I think there are different concerns for api/v1/index/retrieve vs api/v1/log/entries/retrieve:
For api/v1/log/entries/retrieve: the number of input elements is unbounded, but the number of responses appears to be <= the number of elements requested. Each successful lookup requires a one more more fan out calls to Trillian so clients can currently generate significant load with a small number of requests. If this is all accurate, for GA would could just put a limit on the number of entries requested and let clients handle pagination.
For /api/v1/index/retrieve: the concern here is that a single search could potentially return a large number of requests. This API doesn't seem to involve a back end call to Trillian for each result so there aren't the same concerns on fanout on backends. The main concern here would be memory usage while the request is being handled. I suspect this is largely theoretical (?) given the number of entries in the log at the moment but a misbehaving user could eventually trigger this as well. Pagination sounds like the right approach but I guess we could spin up a read replica for search if we just want to isolate it from the core read/write path. Not sure either are GA worthy.
CC @bobcallaway and @priyawadhwa to keep me honest here.

Yah, that sounds correct to me.
Gathered some data for the api/v1/log/entries/retrieve endpoint (averaged across 3 runs):
10 entries: 331 ms
20 entries: 231 ms
50 entries: 480 ms
100 entries: 884 ms
200 entries: 1947ms (averaged across two runs, errored out on third run with a `504 Gateway Time-out` from nginx

I think capping api/v1/log/entries/retrieve at 50 entries would be good to get in before GA.
Pagination could be post-GA work. I checked to see if Trillian has any kind of support for it, but all I could find was this function which could be useful when we get to it.
https://github.com/google/trillian/blob/0a389c4bb8d97fb3be8f55d7e5b428cf4304986f/trillian_log_api_grpc.pb.go#L66-L68

Behavior under load is also important. I was able to observe 100% error rate (and cause other problems) sending sustained traffic with 50 entries per request for a short amount of time. What are the primary use cases for this API? What would be the consequences of reducing this limit to 5 or 10? I may be worth adding a metric to measure distribution of request size.

I think lowering the limit should be fine. Not sure if anyone is using it tho, I think you mentioned parsing logs in Slack to find out and that might be a good place to start.

Thanks for clarifying, I had the wrong endpoint. I didn't actually even know this API supported multiple. Dropping sounds fine to me.

+1 to limiting entry length to 50


Update _index.md

Updated def for 'contract address'

@tesla809 new contributor, @KenMan79 is recruiting.

@tesla809 new contributor, @KenMan79 is recruiting.


How to add optgroups from json data??

it would be nice to add optgroups to selectize like this
<selectize config='myConfig' options='myOptions' optgroups='myOptgroups' ng-model="myModel"></selectize>

I tried to add them trough config manualy like this and it works but

$scope.optLis= [
            {id: 1, title: 'Game of Thrones'},
            {id: 2, title: 'Bird'},
            {id: 3, title: 'Reptile'}
        ];

$scope.myConfig = {
            optgroupField: 'parent_id',
            optgroupLabelField: 'title',
            optgroupValueField: 'id',
            optgroups: $scope.optList,
            valueField: 'id',
            labelField: 'title',
            searchField: 'title',
            placeholder: 'Select Parent Category',
            maxItems: 1,
            preload: true
        };

when I try to load optgroups in myConfig from database with json request by adding  optgroups: $scope.roots it doesnt work
 $scope.roots = function(){
            return {
                get : function() {
                    return $http.get('/roots');
                }
            }
};

I guess problem with this is preloading of roots inside angularjs becouse when i add myOptions to selectize tag from json they get loaded but optgroups didnt load inside angular so there is nothing

The suggestion is OK, I suppose.
As a workaround, you can try and use the Optgroups API to add them later.
(Haven't tried.)

@PhiLhoSoft thanks for sugestion I just added functionality only problem I have is implementing id becouse addOptionGroup needs that id Can u help me with this I just created gist with code that should work --- https://gist.github.com/atheleron/03afae07a5b180c6c265.js

Can you please set up a Plunker (or Fiddle or whatever) with your code, corresponding HTML and client code, showing it in action?

I just created a plunk I head bit trouble with 2 angular-selectize scripts on same page so I did some changes to suppot both directives selectize and optselect but now its ok check the preview on plank http://plnkr.co/edit/2JG0EEKbLQnpVbXjWpLg?p=info

OK, thanks. At first, I was a bit confused, wondering why you have so much files.
I finally made sense out of that... :-D
Note: I would have used a CDN for Selectize itself, using the standalone version, avoiding to explicitly add the two dependencies. I used <script src="//cdnjs.cloudflare.com/ajax/libs/selectize.js/0.12.1/js/standalone/selectize.js"></script> in a Plunk. The non-minified version eases debugging... :-)
Now, I find your Plunk well made, informative and illustrative. Well done.
I haven't fully analyzed the issue yet, but by glancing at the code, I think the main problem is that optgroup isn't available from the start of the controller in the atheleron version, while it is in the machineboy one.
angular-selectize binds its options but actually needs them a init (link() call) time, so they cannot be loaded in a delayed way. I suppose it is a similar issue with optgroup, but it is just an intuition right now. It needs a more thorough investigation.

It fails when calling addOptionGroup which is defined as function(id, data), but you call it as selectize.addOptionGroup(scope.optgroups);, ie. only one parameter.
Moreover, it is called in onInitialize(), so scope.optgroups isn't set yet.

Some errors in your code: the atheleron version doesn't define an option group, like the machineboy version. I added it. As I pointed out, you treat addOptionGroup like addOption, hoping it will process an array, but it is here only a call for one group. So I changed your calls with a map over the array.
http://plnkr.co/edit/TRpM8N3WceevLAAZE1Ri
Seems it works. Again, it is a quick hack / fix, perhaps I overlooked some things.

wooohooooo it woooorks :) :) :)
@PhiLhoSoft First I would like to thank you so much for your effort and support you give me.
I did at first used selectize standalone version I dont know why but select input didnt show up so I used one that required microplugin and sifter
In theory options and optgroups are basicly the same so I said ok lets clone this options and lets try to implement addOptionGroup but since I was cloned generateOptions to generateGroups function witch returns an array I was like why do I need id I mean there is optgroupField witch tells you what id to use to connect options and optgroupValueField that is id of optgroup so why do I realy need that id. then I just added json string to it in hope it will resolve but it didnt. So I was thinking I shoudld make better array and somehow tell addOptionGroup to use id of scope.options but how to get it ?? this is where I stuck. I didnt realise I should make reversable array man that is genious you can call it a hack or fix whatever you call it maybe is not the best solution but it works exactly as it should be its perfect.
Maybe in future we can create some function instead call an array on it each time. I was searching inside of brianreavis/selectize.js to find how he did optgroups but that is to much complex code and requires lots of reading hehe I did find some callbacks that are not inside of documentation like onOptionGroupAdd onOptionGroupRemove and onOptionGroupClear and some other stuff just by searching "optionGroup" maybe it can help if we need to make optgroup function that will also beautify more code and after we can send a machineboy pull request as optgroups feature functionality but what a heck important is that it works now!! :) :)

I notice there is a bug with onChange function when you select "Game of Thrones" and then
open selectize input list again instead optgroup name there is an id number instead of label but if I commentout onChange function that isn't happening but when I try to submit form without onChange function in my case value is not submitted because value is empty.. So why value changes optgroupLabelField to optgroupValueField it should just change current value of select box not the title??

I updated the pliunk to include an onChange function, and I can reproduce the issue. Actually, the first issue, visible without onChange, is that the Game of Thrones option should be under the group of same name. Not sure why it is not, yet.

I cleaned up a bit the code, removing ngModel from the optgroup generation, or automatic generation of optgroups from a string, as these don't make sense (or we should generate the id in the latter case).
Opt groups are broken, I am debugging it, but gotta go, Will code back to it later.

hahaha this is crazy or what ok I solved it!!! previous code works fine don't need to remove anything the only problem was naming of id value i just changed optgroupValueField: id to oid so its diferent from valueField and somehow inside root json  there is oid with same value as id hahaha and it works optgroupValueField can be named as you wish it will just clone id number of json and it will appended to it here is plunk check Json Response in preview you will see oid http://plnkr.co/edit/gW8gqojbFYaxwgu7vAms?p=preview

I am sorry, but I don't understand your last plunk.
Apparently, you use the same data to define the options and the option groups, which doesn't make much sense for me.
I still think the opt group data should be separate, as I shown in my plunk. Although perhaps they can be loaded asynchronously too.
But you made me take a second look. Actually, I found out that the values defined in the optgroupValueField property must match the values in the optgroupField defined in the options.
In other words, in my plunk, ogid's values in the optgroup definitions must match values of parent_id in the option definitions. In short, there was no need for a parent_id field in the optgroup definition.
I think that null parent_id isn't a valid value, though.
Note: my previous version was calling selectize.addOptionGroup(g.id, g); which is incorrect, supposing an id field was defined. Now it uses selectize.addOptionGroup(g[config.optgroupValueField], g);.
And I still think the code I removed isn't useful: you will rarely refer to a group by its full name in the options, I think. And you won't define optgroups from the model, too (unlike selected options).

OK, if you want to load groups dynamically as well, you can.
I updated the plunk, using modified Json data, separating group definitions from options (and changing null parent_id to 11).
Changed the machineboy code as well. Both work fine, now.
Still at http://plnkr.co/edit/TRpM8N3WceevLAAZE1Ri?p=preview

Last note: I mentioned that the wrapper should call registerOption instead of addOption, to distinguish user tags from initial tags. Likewise, we should call registerOptionGroup instead of addOptionGroup, because it frees us from having to specify an id (which is stored back to the data anyway) and doesn't trigger an event (not useful initially).

Thanks a lot PhiLhoSoft !
You save us some long hours (dev) with your modified version for optgroups !

I've added an example of optgroups to the plnkr demo. But the directive still does not support dynamic optgroups. This might be a good feature to add in the future.

is dynamic optgroups supported now?


Lack of transparency

Hey :wave:,
I'm one of the collaborators of https://github.com/neoclide/coc-tabnine and I really like the concept of TabNine but I do find it somewhat iffy that it is closed source but even more that the project lacks transparency. The project is all of a sudden owned by Codota and there is no mention of it anywhere.
What is going on and how is this going to impact the future of this project?

#229

Hi @sQVe @NilsIrl
The acquisition of TabNine by Codota has been published in many tech-business related news sites. We'll soon publish blog posts with some additional views and plans for the future.
TabNine is a commercial product, which is currently closed-source, as it has been since day one.
Our team at Codota is working hard to maintain and improve TabNine, and with the increased bandwidth, you'll see faster progress. We're committed to maintaining the project, including a valuable free plan and giving great service to this terrific community.

@sQVe Thank you for your patience. You can find the note from Jacob Jackson here, and my note here. As more developers are now working on TabNine, we have been able to address many of the long-standing issues (notably CPU and memory consumption), and working in full force on the next round of improvements.
Thank you for supporting TabNine!
Dror (CEO @Codota)


Custom command with a language other than English

I am trying to create a custom command application selecting Spanish language. I add some commands and use the keyword recognition to improve accuracy. Everything seems to work fine from the portal, since I use the test option and I am capable of interacting with the custom command app. Also, the app is deployed correctly. However, when I say the keyword from my app to start listening voice commands, an error is thrown: "The server returned status code '404' when status code '101' was expected".
I have another custom command application with English language, and it works perfectly fine. Is there any issue using another language rather than English?
Thanks in advance.
Expected behavior
A custom command application running correctly using a language other than English.
Version of the Cognitive Services Speech SDK
1.14.0
Platform, Operating System, and Programming Language

OS: Windows
Hardware - x64
Programming language: C#

Thanks for contacting us!
How are you configuring the language to Spanish in the C# application? If you could share the code snippet of how you're connecting, that'd be a huge help in diagnosing further -- as would a client log collected per these instructions: https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/how-to-use-logging

Hi @trrwilson,
Thank you for your prompt reply.
As you pointed out, I used logging to know what was going on. The problem was I didn't set the Language in the configuration. I thought that the speech sdk implicitly knew that passing the key of the suscription and the id of the application.
The service works so well. Congrats for the job well done.
Cheers, - Cristian.


Gauri/static initialization problem r08

You'll need to change the target branch for the PR to r0.8.


Bar width, datetime, data overlap

Hello.
I programing chart with real time data.
Data arrives at different intervals.
https://codesandbox.io/s/vue-basic-example-hmxov?file=/src/components/Chart.component.vue
Look at the picturie:

1 - how make width 100%?
2 - date in the wrong place
1588661399 = 2020-05-05T06:49:59+00:00 almost 06:50:00
1588661452 = 2020-05-05T06:50:52+00:00 much further 06:50:00
3 - data overlap.
4 - where date? (date sometimes appears in wrong place)
The difference in data between 2 charts is only 1 value at<PHONE_NUMBER>000
Can i set interval manualy (1sec, 5min, 1day) for prevent nr3 - data overlap?

If the bars are overlapping, one thing that might be causing is the dates not being sorted in ascending order. Make sure that the dates you provide are coming in ascending order.
Also, upgrade apexcharts to 3.19.0 to fix the width issue.

Many thanks!
Sorting in ascending order has solved many problems.
But one problem remained.
Incorrect date position.
https://codesandbox.io/s/vue-basic-example-vw0m4?file=/src/components/Chart.component.vue:3107-3117


Use type aliases

Currently uint256 is used for timeouts, chain_id, token amounts, channel identifiers, nonces, block_numbers, and expirations. On most cases these are completely incompatible and mixing the values is a bug, and on some cases care is required to convert from one type to another (timeouts -> expirations).
To avoid errors and have a type with semantic meaning I propose the use of the following pattern to alias types:
struct ChannelId { uint256 id; }
map(ChannelId => Channel) public channels;

instead of using the value type directly as it's currently done:
map(uint256 => Channel) public channels;

I checked the bytecode generated for code similar to the one above with 0.4.24+commit.e67f0147.Emscripten.clang and there is no negative impact on the generated code (without optimizations)

and there is no negative impact on the generated code

Do you mean it looks identical? iow has no extra opcodes?

Do you mean it looks identical? iow has no extra opcodes?

yes

We do similar stuff (structs with a single member) to get compiler time type-checking in C.

Yep, same idea

Did you only check for the code above or did you also check with code that actually uses the ChannelId? I expect additional gas (probably minimal) from computing the pointer to the actual id value.
Do you know if web3.py already supports struct as input? I know there were some problems implementing this at some point.

Did you only check for the code above or did you also check with code that actually uses the ChannelId?

I did not check with our current code.

I expect additional gas (probably minimal) from computing the pointer to the actual id value.

I had some guesses written here, but instead of guessing we should just do a test and see if it's the same.

Do you know if web3.py already supports struct as input? I know there were some problems implementing this at some point.

I don't know for sure, the only issue open on the web3.py repo is about improving the current return value. I believe that structs as input is part of the new ABI, which still experimental, so I would not expect inputs to work right now.
That is something that we can fix (contributing code or reporting issues). If there are issues we could either wait until everything is working or use more descriptive types for the internal data structures with explicit casting for the inputs. I think the type safety is worth the additional lines of code/trouble.

@hackaugusto , please provide the entire code of what you have tested. For me, it does not compile and  solidity/issues/599 does not seem closed.
map is not correct code, so I assume the above was pseudocode.
Otherwise, we can test later and see if this has benefits for the contracts.

I see why
struct ChannelId { uint256 id; }
struct Channel {ChannelId id;}

is useful and can protect from unintended operations on two different types (e.g. channel_identifier + settlement_timeout).
Implementing this at the moment would also mean changing the contracts structure, because - as seen earlier, mappings cannot have struct as keys - at least not yet.
So, what do you propose? Wait? Restructure?


Adds docker as a prerequisite

## What
Updates ReadMe doc to include docker as a prerequisite
Why
It may be an obvious thing to do but should be explicitly stated so users are not confused.

(Welcome back 👋 )

As I understand this isn't needed because the Brewfile installs docker: https://github.com/alphagov/govuk-docker/blob/ff55aa1698eccc8ab0ad926c50dae2c6b9516b71/Brewfile#L8 and by changing this we create an inconsistency between some dependencies listed here and others in the Brewfile.

As I understand this isn't needed because the Brewfile installs docker:
https://github.com/alphagov/govuk-docker/blob/ff55aa1698eccc8ab0ad926c50dae2c6b9516b71/Brewfile#L8
and by changing this we create an inconsistency between some dependencies listed here and others in the Brewfile.

This is a good point, I'll close the PR


when apply SCSwipeableFilterView in SCPlayer then display white screen some time

self.player = SCPlayer()
        self.player.delegate = self
        self.player.setItemByStringPath(self.strFilePath)

        let scplayerView = SCVideoPlayerView(player: self.player)
        scplayerView.playerLayer?.videoGravity = AVLayerVideoGravityResizeAspectFill
        scplayerView.frame = self.playerView.frame
        scplayerView.autoresizingMask = self.filterSwitcherView.autoresizingMask
        self.playerView.addSubview(scplayerView)

        self.filterSwitcherView.refreshAutomaticallyWhenScrolling = false
        self.filterSwitcherView.contentMode = .scaleAspectFill

        let emptyFilter = SCFilter.empty()
        emptyFilter.name = "#nofilter"
        self.filterSwitcherView.filters = [emptyFilter,
                                           SCFilter(ciFilterName: "CIPhotoEffectNoir"),
                                           SCFilter(ciFilterName: "CIPhotoEffectChrome"),
                                           SCFilter(ciFilterName: "CIPhotoEffectInstant"),
                                           SCFilter(ciFilterName: "CIPhotoEffectTonal"),
                                           SCFilter(ciFilterName: "CIPhotoEffectFade"),
                                           SCFilter(contentsOf: Bundle.main.url(forResource: "a_filter", withExtension: "cisf"))]

        self.filterSwitcherView.isHidden = false
        self.filterSwitcherView.backgroundColor = UIColor.clear

        self.player.ciImageRenderer = self.filterSwitcherView
        self.player.loopEnabled = true

i apply SCSwipeableFilterView in SCPlayer using above code. some time its display white screen.

hello am also facing same issue, you found any issue ?


Migrate backend to Azure Functions

Fixes

Deploy backend (Az function, Az VM, Az Container?)

in #39

We need to change this to programming version model V1, V2 refuses to deploy


Provide motivation for bind modifiers

Per @lonix1 on original issue #28245 ...
In this section it says:

For two-way data binding in ASP.NET Core 7.0 or later, we recommend using @bind:get/@bind:set modifiers. For more information, see the @bind:get/@bind:set in the opening section of this article.

But it doesn't say why? I assume that the new v7 syntax allows one to perform a "set" with an async method, which cannot be done using a regular c# (sync) property setter. That is useful, for e.g., when doing autocomplete. Maybe there are other reasons?
Cross-references:

https://github.com/dotnet/aspnetcore/issues/39815
https://github.com/dotnet/aspnetcore/issues/39837
https://github.com/dotnet/razor-compiler/pull/70
Blog post (Release): "Run async logic after data binding and independently control how data binding gets and sets the data."
Blog post: (Preview 7): "now easier to setup binding" and "now make it trivial to create a component parameters that binds to an underlying UI element"

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

ID: b211df59-e1c9-86c0-c904-31fa3c361e6d
Version Independent ID: 3f912dfc-5ba5-6c6c-ba93-1ae78508a5cc
Content: ASP.NET Core Blazor data binding
Content Source: aspnetcore/blazor/components/data-binding.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

@lonix1 ... It looks like from Javier's remarks that only one specific reason ... well, that's obvious anyway because dev issues that were opened for the PU aren't listed in the design issue ... the one specific reason that applies to the remark is ...

Or, if you @bind to a property with a get/set pair, you have to discard the Task returned by ValueChanged.InvokeAsync.

Cross-ref: https://github.com/dotnet/aspnetcore/issues/39837
... noting that the example in THIS article's section doesn't bind to a property ... we do it down in the Bind across more than two components section ... which actually has a whole different approach with @bind:get/@bind:set commented out that nobody can see due to problems with the feature at the time of .NET 7's release that were partially fixed by a framework patch and will be completely fixed in VS for the February VS release. The update to that doc section is tracked by a separate issue, which I'll work as soon as the new VS drops and the PU confirms that VS is cool ... the problem in VS btw AFAIK was just that IntelliSense is tripping up on the syntax. I think the runtime is cool ... I think it's just a UI problem in VS.
I think that I should say in the NOTE the one reason that we do have ☝. Let's do that. I'm not convinced that we should cross-link the whole design issue at this point. I'll take more feedback on that. If more devs ask about the motivations for the change and want to read further, I'll give them the link to that PU issue at first ... and if folks keep asking, I'll cross-link that PU issue into the document in the earlier section that introduces the main concepts.


Dark Frame question

So this is more of a question on the dark frame option.  Currently on the pi there is dark images from -13 to 31. the number go from -13 to 31 in one step settings i have the dark frame option select in the config.sh.
# Set to "true" if you want to enable dark frame subtraction on your night-time images.
# You must first create dark frames - see the README.md file for instructions./

DARK_FRAME_SUBTRACTION="true"

I read the README.md but still a confused but it.
So since I have 46 dark images the software will try all 46 and see which one is the best are removing hot pixels.
Mike

@maserowik No, the software will get the current sensor temperature from the temperature.txt file then find the closes file in darks/* to that temperature.  For example, current temp in temperature.txt is 21.  You have 3 darks:  17.jpg, 20.jpg, and 23.jpg.  The software will first look for an exact match with 21.jpg, but since it's not found it will pick 20.jpg because it's only 1 degree off from the current temp of 21.
It never looks in the files - it simply looks at the names of the files.  Unless something is really weird with the camera, or your darks are pretty old, the closest dark frame will give the best results.  Assuming the dark and the light have the same settings, like exposure time, binning, gain, etc.
Does this answer your question?
FYI, the Pi you're letting me use has the fixed version of darkCapture.sh and darkSubtract.sh that correctly implements this.

Here are examples of the files I'm comparing, when I open them both up in Photoshop and create layers and compare the two I do see some of the hot pixels being removed but not all.
![43](https://user-images.githubusercontent.com/92370510/136946861-f118cd0c-29ee-4b61-bd03-076b6dd978ec.jpg

)

@maserowik No, the software will get the current sensor temperature from the temperature.txt file then find the closes file in darks/* to that temperature. For example, current temp in temperature.txt is 21. You have 3 darks: 17.jpg, 20.jpg, and 23.jpg. The software will first look for an exact match with 21.jpg, but since it's not found it will pick 20.jpg because it's only 1 degree off from the current temp of 21. It never looks in the files - it simply looks at the names of the files. Unless something is really weird with the camera, or your darks are pretty old, the closest dark frame will give the best results. Assuming the dark and the light have the same settings, like exposure time, binning, gain, etc.
Does this answer your question?
FYI, the Pi you're letting me use has the fixed version of darkCapture.sh and darkSubtract.sh that correctly implements this.

Thanks  I have a better understanding on how the darks work with the program.
Mike

I know the issues I was having have been resolved.


maybe use a model VPN  like wireguard ?

https://www.wireguard.com/
Its open and in c and golang

If we make a driver architecture IMHO it could be a driver if somebody has capacity to write it. For some environments wireguard is still not accepted, specially since it's a young project, and the kernel modules aren't upstream yet. But it's promising.

Wireguard support is in progress. Please see https://github.com/submariner-io/submariner/issues/394


porter build should always create secure bundles

Hold off on this for a bit while CNAB/duffle redoes how it handles signing.

This seems to still be unsettled in CNAB/duffle..maybe we flip install to assume unsigned for now? Experience will be a little easier until it's all settled.

Yeah I hate always having to use --insecure when it's the only thing that works right now. EXECUTE! 👍

Closing as the security spec is not complete.


Provide mechasnism to opt-out of DotNetCoreCLIV2 deprecation warnings

Required Information
Question, Bug, or Feature?
Type: Feature
Enter Task Name: DotNetCoreCLIV2
Environment

Server - Azure Pipelines

Agent - Hosted

Issue Description
Every time the DotNetCoreCLIV2 task is used it now outputs this warning:
##[warning].NET Core SDK/runtime 2.2 and 3.0 are now End of Line(EOL) and have been removed from all agents. If you're using these SDK/runtimes, kindly upgrade to newer versions which are not EOL, or else use UseDotNet task to install the requied version.

This warning is displayed even if you aren't using 2.2 or 3.0, and there doesn't seem to be any way to opt out of this message.  We are using:
- task: UseDotNet@2
  inputs:
    version: 3.1.300

This task needs to either:

Ideally, detect the version of .NET Core in use and not display this warning
Allow us to set an environment variable (or something) to not display the warning

This message spams our logs and hides warnings that may be actual problems:

@tejasd1990

Detecting the version being used isn't going to work across the board. Some commands don't have a version specified. For example, I have the following in my pipeline and it still emits that warning:
      - task: DotNetCoreCLI@2
        displayName: 'Install gitversion'
        inputs:
          command: 'custom'
          custom: 'tool'
          arguments: 'install -g gitversion.tool --version 5.3.7'

Related thread https://developercommunity.visualstudio.com/content/problem/1108547/irrelevant-build-warning-about-eol-net-core-sdks-b.html

It would be nice if the task detected the runtime version in the global.json and didnt show the warning if you are on a supported runtime

Detection is going to be difficult and may well be wrong at times. Hence we will not do that.
We are moving this message from warning to be an Info. It will still be printed in all cases, but will not show up in pipeline warnings.

Would it be worth emitting the warning for UseDotNet@2 if an unsupported version is specified?

@mconnew UseDotNet task will use whichever version is specified(eol or not), for subsequent tasks. The deprecation message is for DotNetCoreCLI task on hosted agents, not UseDotNet. Not sure I got the question.

The deprecation message is for DotNetCoreCLI task on hosted agents

The message should only be shown on hosted agents? That's not the case, I also get it on a self-hosted agent.

@tejasd1990, if the idea is to warn people when they are using an older EOL version of .NET Core, then I was suggesting adding the warning message to the UseDotNet task instead where you do know exactly which version has been specified.

@mconnew If I am understanding correctly, it seems like this warning (not info) message is really warning the user that .NET Core 2.2 and 3.0 are no long installed by default on hosted agents, which happens to be because they are EoL'ed, not that you are using an EoL'ed version of .NET Core. I do think that the latter (warning if you are using an EoL'ed version of .NET Core) would be more meaningful however. For example, how long are you going to display the info message? For the rest of time? Will there be additional messages added later when another version is EoL'ed? It seems like there should be a warning if, and only if, you are actually using an EoL'ed version of the framework.

@ChristopherHaws I misunderstood the purpose of the message. I would think that the build output is the wrong place to communicate about a change in the hosts configuration which is why I didn't connect the dots correctly. Re-reading the message I can see that the intention was about the host configuration.

Yes the intention is to communicate about hosted agents. The intention was necessiated due to a lot of folks not able to understand why their pipeline started failing after we removed EOL version from hosted agent.
I agree that this is not a very elegant solution as it shows up even if you use a current version. But detecting the version which is in use for a command is not really straightforward, and we chose not to venture into that complexity as it could potentially result into unexpected behaviour.
We however are looking into how to bubble hosted agent changes in a more discoverable and pleasant manner. Post that we can definitely think about removing this message from task log.

We should however clearly call out 'hosted agent' in the message. @vineetmimrot can you please change this?

We should however clearly call out 'hosted agent' in the message. @vineetmimrot can you please change this?
.NET Core SDK/runtime 2.2 and 3.0 are now End of Line(EOL) and have been removed from all agents

I see that this has already been fixed by @tejasd1990


SAK-46957 - Lessons: Collapsible section not keyboard accessible

A few things to note with this revised commit:

For some reason, most of the aria attributes have been applied to the h3 element, so I retained that practice except for applying an aria-label to the icon span.
The 'needIcon' boolean present in ShowPageProducer doesn't make sense to me; it would remove the collapse/expand icon if the default state of the collapsible section is closed. However, even if it was closed, a user should be able to know that the section is collapsible by the presence of that icon (and now button), so I've revised that logic.


error: Found argument '--ok' which wasn't expected, or isn't valid in this context

I am using this config:
      - name: Install Spectral
        uses: spectralops/spectral-github-action@v2
        with:
          spectral-dsn: ${{ env.SPECTRAL_DSN }}
          spectral-args: --ok
      - name: Run Spectral
        run: spectral scan --github-format

Unfortunately my action fails with error message:

error: Found argument '--ok' which wasn't expected, or isn't valid in this context

Am I holding it wrong? The spectral-args with --ok is documented here: https://github.com/SpectralOps/spectral-github-action/tree/v2#configuration

Hi,
please look at the example here
I will update the docs
Thanks!

@guylev008 thanks! I opened a PR fixing the docs: https://github.com/SpectralOps/spectral-github-action/pull/6


⚠ Bofrost.gr has degraded performance

In 43307d8, Bofrost.gr (https://www.bofrost.gr) experienced degraded performance:

HTTP code: 200
Response time: 2379 ms

Resolved: Bofrost.gr performance has improved in 6319ee5 after 6 minutes.


Build API that accepts yaml file instead of yaml string

Is your feature request related to a problem? Please describe.
Right now someone has to write the yaml file reading logic to create agents. If there were ways to directly pass the yaml file, it would have been easier
Describe the solution you'd like
The build API directly accepting yaml as a file path

Make a change to the Flo.build API to accept an optional parameter named yaml_path= which can take in yaml file path and use it. (inside core.py)
Flo.build(session, yaml_path="<path to yaml>")

Fix in https://github.com/rootflo/flo-ai/pull/73

Closed in #73


[medInria 3.0] binary crash xcb Qt5

A colleague tried the medInria 3.0 binary for Ubuntu 16 on a Ubuntu 18. He switched his OS to Qt5 with sudo apt install qt5-default, run the medInria script and crash:
This application failed to start because it could not find or load the Qt platform plugin "xcb".

Reinstalling the application may fix this problem.
Abandon (core dumped)

It's maybe solved on the master, or it's a pre-requisites problem, i don't have the crash.

It sounds like you are missing Qt5 dependencies on the system. Something we need to document by the way. On the slaves for build, I think we have explicitly installed :

for ubuntu : qt5-default qttools5 qtdeclarative5 libqt5x11extras5 libqt5svg5
for fedora : qt5

That's one point in favor to go back to a rpm or deb packaging, this could solve those problems

Pre-requisites for running medInria added in https://github.com/medInria/medInria-public/wiki/A-Quick-Dev-Guide


R24.08 BDRS - TRG Checklist

QG checks
Please open and fill in this issue in your product repository to document the compliance with our Tractus-X Release Guideline (TRGs)
Show compliance with TRGs by referencing to a tagged link in the respective repository where possible, example: TRG 1.01 (see github.com/eclipse-tractusx/example-repo/tree/1.0.0/README.md)
Close this issue once the compliance with the TRGs has been documented
Committer(s): @jimmarino @paullatzelsperger @wolf4ood @ndr-brt
Helm Chart Version: 0.5.1
App Version: 0.5.1
Release Management Reference Issue:
Check of Tractus-X Release Guidelines

Currently implemented automatic checks can be found under your product on our Release Guidelines Checks Board
This QG Check is depending on the mandatory information from our current Release Guidelines

TRG 1 Documentation

[x] TRG 1.01 appropriate README.md
[x] TRG 1.02 appropriate install instructions either INSTALL.md or in README.md
[x] TRG 1.03 appropriate CHANGELOG.md
[x] TRG 1.04 editable static files
[ ] TRG 1.06 Administrator's Guide
[ ] TRG 1.07 End User Manual
[ ] TRG 1.08 Interface documentation (APIs)

TRG 2 Git

[x] TRG 2.01 default branch is named main
[x] TRG 2.03 repository structure
[x] TRG 2.04 leading product repository
[x] TRG 2.05 .tractusx metafile in a proper format
[x] TRG 2.06 Dependabot

TRG 3 Kubernetes

[x] TRG 3.02 persistent volume and persistent volume claim or database dependency (subchart) are in place when needed

TRG 4 Container

[x] TRG 4.01 semantic versioning and tagging
[x] TRG 4.02 base image is agreed
[x] TRG 4.03 image has USER command and Non Root Container
[x] TRG 4.05 released image must be placed in DockerHub, remove GHCR references
[x] TRG 4.06 separate notice file for DockerHub has all necessary information
[x] [TRG 4.07] (https://eclipse-tractusx.github.io/docs/release/trg-4/trg-4-07) root file system is set to read access by default, but can be overwritten by the user

TRG 5 Helm

[x] TRG 5.01 Helm chart requirements
[x] TRG 5.02 Helm chart location in /charts directory and correct structure
[x] TRG 5.03 proper version strategy
[x] TRG 5.04 CPU / MEM resource requests and limits and are properly set
[x] TRG 5.06 Application must be configurable through the Helm chart
[x] TRG 5.07 Dependencies are present and properly configured in the Chart.yaml
[x] TRG 5.08 Product has a single deployable helm chart that contains all components
[x] TRG 5.09 Helm Test running properly
[x] TRG 5.10 Products need to support 3 versions at a time
[x] TRG 5.11 Upgradeability

TRG 6 Released Helm Chart

[x] TRG 6.01 Released Helm Chart

TRG 7 Open Source Governance

[x] TRG 7.01 Legal Documentation
[x] TRG 7.02 License and copyright header
[x] TRG 7.03 IP checks for project content
[x] TRG 7.04 IP checks for 3rd party content
[x] TRG 7.05 Legal information for distributions
[x] TRG 7.06 Legal information for end user content
[x] TRG 7.07 Legal notice for documentation
[x] TRG 7.08 Legal notice for KIT documentation

TRG 8 Security

[x] TRG 8.01 Mitigate high and above findings in CodeQL
[x] TRG 8.02 Mitigate high and above findings in KICS
[x] TRG 8.04 Mitigate high and above findings in Trivy
[x] TRG 8.03 No secret findings by GitGuardian or TruffleHog

TRG 9 UX/UI Styleguide

[ ] TRG 9.01 UX consistency / Styleguide for UI

Hints
Information Sharing

@paullatzelsperger:  Can you have a look at TRG points 1.06-1.08 and 9.01, they were added but not in the template and I was not aware of that, thanks!

there is no end user manual, since it is not an end-user application. likewise there is no UX styleguide, because there is no UX.
the interface documentation is published to GH Pages (lacking a consolidated approach as of now) and the "Administrators guide" is in the repo.


Default date_time skill version 0.2.2 does not work correclty in Italian

The skill does not load even if it is well installed. It works fine with version
ovos-skill-date-time              0.2.3a5

ovos-docker pre-build images are based on alpha releases which is why 0.2.2 version will not work and which is the reason why ovos-skill-data-time  Docker image is based on alpha release as well.
https://github.com/OpenVoiceOS/ovos-docker/blob/dev/skills/skill-date-time/Dockerfile#L20


ModuleNotFoundError: OCRDetectionPipeline:

I get the following error message:
ModuleNotFoundError: OCRDetectionPipeline: No module named 'tf_keras.legacy_tf_layers'
Any ideas how to fix this?
Thank you.

This is due to versions of Tensorflow and keras. The OCR model is from modelscope. Using the latest versions of Tensorflow and keras results in incompatibility with the OCR model. Try installing versions of Tensorflow and keras in requirements.txt. If this still reports error, you can continue to write error reports here.

I'm also having this issue. Which version of TensorFlow and Keras are compatible with the OCR model from modelscope and can be installed on a MacBook with an Apple M1/M2/M3 chip with ARM-based architecture?

I'm also having this issue. Which version of TensorFlow and Keras are compatible with the OCR model from modelscope and can be installed on a MacBook with an Apple M1/M2/M3 chip with ARM-based architecture?

You can try the following two methods on MAC:

Modify the requirements.txt: from "TensorFlow==2.9.1" to "tensorflow-macos==2.9"
conda create -n mobileagent python=3.9.11
Modify the requirements.txt:
TensorFlow==2.13.0
keras==2.13.1

I also having the same problem. How was the issue finally resolved? If I use the author's version, it prompts that it cannot find the appropriate version of the required environment. The screenshots is:

I also having the same problem. How was the issue finally resolved? If I use the author's version, it prompts that it cannot find the appropriate version of the required environment. The screenshots is:

Hello, what operating system are you using?

I also having the same problem. How was the issue finally resolved? If I use the author's version, it prompts that it cannot find the appropriate version of the required environment. The screenshots is:

Hello, what operating system are you using?

The operating system of my computer is Windows 10. I have already solved this problem in another discussion. I adjusted the version of Python with the command: conda create -n mobileagent python=3.10.6
TensorFlow==2.9.1
keras==2.9.0
Thanks a lot!


Adds character limits for chat

Fixes #1301
This is my first contribution ever to an open source project.
For now, it works like this :

There's a client-side check that prevents sending a message over the character limit
If it doesn't work or the client is modded, there is a server-side check that prevents that also
The max message length is sent by the server in every MsgChatMessage. I don't know if it's the best way, I thought the server could send the max message length once to the client during the handshake but I wasn't sure. If it needs to be changed I will gladly

Thank you for your PR! As a tip, it'd be best if you titled your PRs with descriptive names. For example, "Adds character limits for chat".

Thank you for your PR! As a tip, it'd be best if you titled your PRs with descriptive names. For example, "Adds character limits for chat".

Thanks for the tip, I just corrected it

All suggestions have been added to the PR

You're going to want to remove all the .csproj changes, especially since some of them only work on your system.

Those changes were made automatically by Visual Studio apparently. I think I removed every changes (I reset all the .csproj files to their states before my first commit)

So I mades changes to remove any .csproj modifications. I don't know why they were made, I think it's an auto thing from VS. Anyways, long story short I created my local branch from the SS14 repo instead of my own fork to be updated and for that reason I cannot push the finished stuff on this PR.
That's why I'll close this one and re-open a new one


Correction for raw affiliation Department of Medical Physics Tom Baker Cancer Centre  Calgary AB; Department of Physics and Astronomy University of Calgary  Calgary AB

Correction needed for raw affiliation Department of Medical Physics Tom Baker Cancer Centre  Calgary AB; Department of Physics and Astronomy University of Calgary  Calgary AB
raw_affiliation_name: Department of Medical Physics Tom Baker Cancer Centre  Calgary AB; Department of Physics and Astronomy University of Calgary  Calgary AB
new_rors: 03yjb2x39
previous_rors:
works_examples: W2107172893;W2032653063
contact: ba7d23630aaae29ab5f4abc7eae42459:6257e10e @ ourresearch.org

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


Fixed nil pointer issue causing errors to not be passed through

https://github.com/jak103/powerplay/issues/80


add onramp.money

What is the purpose of the change
adds another option to buy tokens from (onramp.money)
ClickUp Task
ClickUp Task URL
Brief Changelog

when click on buy button, it add 1 more option called onramp.money.
opens onramp.money on a iframe.
users sees how much they are going to pay & how much coins are they coin to get.
user address is prefilled
user needs to pay & received token in their wallet

Testing and Verifying

Documentation and Release Note

Looks like we might have some build failures due to type errors.

Looks like we might have some build failures due to type errors. Can you run yarn build locally and get it to pass?

m using yarn run generate command to generate the sprite-ids.ts but its not working..
looks like sprite-ids.ts is build using public/icons/sprite.svg file - mentioned in generate-sprite-ids.ts file
how to i update public/icons/sprite.svg file ?

Looks like we might have some build failures due to type errors. Can you run yarn build locally and get it to pass?

m using yarn run generate command to generate the sprite-ids.ts but its not working..
looks like sprite-ids.ts is build using public/icons/sprite.svg file - mentioned in generate-sprite-ids.ts file
how to i update public/icons/sprite.svg file ?

Sent you a slack

Looks like we might have some build failures due to type errors. Can you run yarn build locally and get it to pass?

m using yarn run generate command to generate the sprite-ids.ts but its not working..
looks like sprite-ids.ts is build using public/icons/sprite.svg file - mentioned in generate-sprite-ids.ts file
how to i update public/icons/sprite.svg file ?

Sent you a slack

fixed build issues

in logo ON text is only visible when you hover the mouse.

Says both Osmo and USDC supported but only Osmo is available currently. Shouldn't be a blocker if USDC is coming soon.

Couldn't link TG bot for a Portugal phone number.
Din't get OTP for an Indian phone number

in logo ON text is only visible when you hover the mouse.

logo updated

Osmo logo does not look good, it looks pixelated and unaligned.

Couldn't link TG bot for a Portugal phone number. Din't get OTP for an Indian phone number

Here is a dummy phone number you can use
Phone Number: +91<PHONE_NUMBER>
OTP :  123456

There should be limit for integers so things dont overlap.

@sajwanAshish I tried with dummy number and scanned QR to pay with googlepay/phonepe with 200Rs.  dint went through. Is it because of dummy number or payments aren't open yet?
We would like to test full version end to end with real phone numbers (EU, US, IND etc) and Tg accounts to make sure full integrations works well.

There should be limit for integers so things dont overlap.

this is sorted

in logo ON text is only visible when you hover the mouse.

sorted

i see there are conflicts in localizations files... shall i go ahead & fix conflicts or your team will take care of it

i see there are conflicts in localizations files... shall i go ahead & fix conflicts or your team will take care of it
@DavideSegullo @kamal-sutra

You can fix them

Osmo logo does not look good, it looks pixelated and unaligned.

fixed

@sajwanAshish looks like you just need to rebase against stage to resolve conflicts

Tried with Indian mobile number- KYC done in 5min.
Purchase with QR done in 5min
Sending osmo to my addy +5min
In 15min all done end to end.

@sajwanAshish only inr fiat available for now? eur or usd?

@sajwanAshish any update on this?

123456

This test number has changed,
this is for Germany (EU)
+49<PHONE_NUMBER> | 123456
for india plz use real numbers..
-- | --

@sajwanAshish it is not giving EUR option

1122334455

EUR option shows now, just couldn't test with dummy number, as it sends otp to that number

Pls try entering 123456 as otp
On Tue, 9 Jan 2024, 11:17 pm kamal-sutra, @.***> wrote:

1122334455
EUR option shows now, just couldn't test with dummy number, as it sends
otp to that number
—
Reply to this email directly, view it on GitHub
https://github.com/osmosis-labs/osmosis-frontend/pull/2538#issuecomment-1883515287,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APTIZJ4WAUZDMXMEBGNA5ADYNV7EVAVCNFSM6AAAAABAQ25SA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBTGUYTKMRYG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

1122334455

1122334455

plz try now

1122334455

plz try now

got Fetching bank details for 5min and then this

1122334455

plz try now

got Fetching bank details for 5min and then this

Please try it again..

1122334455

plz try now

got Fetching bank details for 5min and then this

Please try it again..

@sajwanAshish it is now giving me bank details. But i gave a dummy name as Recipient and i don't get the option to change to real name even after clearing cache. For now i will try with another wallet address

@sajwanAshish Even from another wallet it is not giving me option to write new Recipient name. I guess it is already linked to the dummy german number. Can u provide option to edit Recipient name please. Else bank transfer might get declined/lost.

@sajwanAshish Even from another wallet it is not giving me option to write new Recipient name. I guess it is already linked to the dummy german number. Can u provide option to edit Recipient name please. Else bank transfer might get declined/lost.

can we get on a call & sort out this out
as you guys might want to test it for multiple countries before approving this change

@sajwanAshish Even from another wallet it is not giving me option to write new Recipient name. I guess it is already linked to the dummy german number. Can u provide option to edit Recipient name please. Else bank transfer might get declined/lost.

can we get on a call & sort out this out
as you guys might want to test it for multiple countries before approving this change

Sure. can u send invite link to<EMAIL_ADDRESS>(but for tomorrow if possible, it's late night for me now)
cc @MaxMillington @CryptoAssassin1  if you wanna get on call

Purchase with EUR is successful.
Suggestions-
Allow 'space' in Recipient name field;
A check box would be helpful for the user to make sure the Name, Phone number etc are provided correctly.
Good to merge

@sajwanAshish IMP
i just tried another transfer. i think there is a payment method network issue.
This din't happened during QA few days ago. Alternative option to transfer by bank is also not available. Bank depsoit details are not given.

@sajwanAshish IMP i just tried another transfer. i think there is a payment method network issue. This din't happened during QA few days ago. Alternative option to transfer by bank is also not available. Bank depsoit details are not given.

should be working now..

@sajwanAshish IMP i just tried another transfer. i think there is a payment method network issue. This din't happened during QA few days ago. Alternative option to transfer by bank is also not available. Bank depsoit details are not given.

should be working now..

Taking long time. Please check status


Hotspots Overview Infobox improvements

move scale/sync status to top
add 24h earnings, make it above 30d earnings. or if we can add a toggle and use the same widget, even better.
add recent activity table. show the 5 most recent activities for the hotspot including timestamp
move checklist to below the table

For the recent activity table, continue to use "time ago".
Under Hotspots/Activity, add timestamp when a user expands on the details. Keep time ago.

Per Marc, remove 7D aug witnesses and replace with total witnesses.

Move the gain/elevation numbers from widget to next to Hotspot name/details.


Unable to Run Sampo

Hi,
I have been unable to run Sampo.
I was able to clone the tweaks branch and start the following command in one machine (after tweaking some minor code errors in "sampo.sh", esp. the lines with < <):
while true; do {echo -e  'HTTP/1.1 200 OK \r\n'; bash ./sampo.sh;} | nc -l 1042; done
From another machine, I ran the following command:
curl -i http://IPofmachine:1042/
Output:
HTTP/1.1 200 OK
But, I'm not receiving functionalities. Similarly, running with different endpoints does not yield any results.
Is there a more recent version/release of this tool?
Can you please help troubleshoot this issue? Please let me know if I have to make any changes or specific configurations on my side.
Thanks for the support!

Apologies for the slow response here.  The k8s deployment is really the only one that works ATM.  The infinite loop and just the docker container need more tweaks.  I have some changes upcoming that will support all three.  Until then, YMMV

@ramgiteng Could you please try the latest release (v1.0.0) and let me know how that works for you?
The while loop will not actually work, but give the other methods a try that I show on the README

Have you tried the newest version @ramgiteng?  Now v1.0.2?

Have you tried the newest version @ramgiteng?  Now v1.0.2?

Hi Jacob, apologies for not following up. It's been a while since I last attempted using this. Will try it out and get back sometime next week.


More split of multimodal tests

Issue #, if available:
Description of changes:

Tests split according to run time

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@zhiqiangdon We can consider to submit a follow-up PR to restructure the test-cases based on their functionality.

Doc building failure looks unrelated and the unit tests has passed. Will merge


Fix build problem on Solaris x64.

Remove the duplicated label.
Fixes #5440

Assuming this fix is good, I'm unable to merge in a timely fashion.

Oh! Typo! Failed to check that path :-( But I've spotted another problem with it, Windows-specific. So I'd like to suggest to close this in favour of combined fix...

Closing in favour of #5447.


VQModel1d

Hi,
I found that your code includes VQModel1d method. I want to ask whether you try to use VQModel1d to compress the mel-spectrogram? If you did it, can you share the training config and the training code?

Yes, i have tried and the reconstruction was bad (blurred, not detailed). I don’t think i have code which could help you.


ui can't create a new project

Version
3.0.0-beta.13
Reproduction link
http://www.example.com/not-necessary
Steps to reproduce

run vue ui
Create a new project

What is expected?
A new project is created
What is actually happening?
Displays error: Failed to resolve plugin: @vue/cli-service
Error is chrome console is:
ProjectCreate.vue:528 Error: GraphQL error: Cannot return null for non-nullable field Mutation.projectCreate.

Also getting error when trying to import an existing vue project.
Error is: es6.promise.js:110 Unhandled promise rejection Error: GraphQL error: Cannot read property 'lastIndexOf' of undefined
Perhaps its related.

I believe this should be fixed in beta.15

I experienced this in beta.15, but the issue reported didn't have beta.15 as an option. I'll test again though.


which ACLs are needed for peering?

the default behavior only lets people peer up if there is a Network ACL allowing it. Those are managed via the admin API, but you can set a default allow-all rule at bootstrap with --bootstrap.default-network-policy=accept.

Originally posted by @tinyzimmer in https://github.com/webmeshproj/webmesh/issues/5#issuecomment-1669269793
Which ACLs do I need for peering? Is it like 8443, 9443?

Nah. This is getting in to the stuff that has near zero documentation and very little testing. Once the networking fundamentals are stabilized I really need to give the whole RBAC system some love.
The cidr/port filters are not fully fleshed out - you should be able to get by with the node filters. So, for example, to allow a node node-2 to peer to node-1:
wmctl put networkacl acl-name --src-node node-1 --dst-node node-2

And (if my memory serves) you'll need a reverse of the rule as well. You can also collect nodes into groups and create ACLs using the group:<group-name> format for the node arguments.

Since you are actively playing with this functionality - I'd love to incorporate any feedback you might have. So feel free to call out any areas where you think things might work better.

This is just a lot of uncharted territory. CIDR/Port filtering is not yet implemented. The reason being the implementation will have to be specific for each platform and will take time (and hopefully more developers). The node itself is not inspecting traffic - it is only setting up the interfaces. So to do IP/Port filtering - nodes need to evaluate the ACLs locally and apply to their firewalls what they should allow/block.
That being said - what should be working right now is that if there is no rule that at least allows two nodes by their IDs to communicate with one another - the connection should not be established. Beyond that - once the connection is established, all traffic between the peers is being allowed. If that is not working as intended, it's definitely the first thing that needs to be addressed.


Mirror Filecoin Actors Improvements

Issue summary

[ ] Containerized Deployment
[ ] Add black as a formatter, and pylance as a type checker.

Other information and links

It works fine, let's not overengineer.


[ListView] removeClippedSubviews={true} and overflow:"hidden"

Hi,
The document of ListView says the removeClippedSubviews={true} property only works when the list items have overflow:"hidden" style set.
I'm wordering whether this is just an interface design or an impmentation must.
In my case I want to display a badge on the upper-left corner of each of the list item, in order to avoid clipping the badge by the item margin, I set overflow to "visible" but after that the list is just to lag to be used.
Is it possible to make removeClippedSubviews work with overflow:"visible"?

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/listview-removeclippedsubviewstrue-and-overflowhidden
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.


RolemasterUnified Official: RR and misc fixes.

Stats are now right aligned.
Fix update for specialised skills.
RRs:

now have a box.  Make them standout more.
Use the pretty name. not the attribute name.
Number now rolls with modifier.

Fix an issue causing some characters to have problems levelling up.
Fixed specialisations show the skill name when rolling.
Handle knacks for Alchemists.

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Character Sheet Info Roll20 Internal Use only.


Added Huffman Coding Algorithm

📥 Pull Request
Description
Added Huffman Coding to greedy algorithms
Fixes #280
Type of change

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

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@ajay-dhangar Please look into it


recommended title is different in instructions and code

The git repo name in step one of "Publish your application to GitHub" is jekyll-azure-static. The name of the repo in the code block of Step 2 is jekyll-static-app. Please change so they match.

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

ID: d1532547-d8ef-bdea-4164-4f617a249eb5
Version Independent ID: f8a21eb1-662f-13f3-dd9d-9ed2962e740d
Content: Tutorial: Publish a Jekyll site to Azure Static Web Apps
Content Source: articles/static-web-apps/publish-jekyll.md
Service: static-web-apps
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@PSGruss Thanks for the feedback! We are currently investigating and will update you shortly.

@PSGruss Thanks again for the feedback! I have created PR it will be visible soon


Feature Request: Support semver build artifacts

Currently shep's build artifacts are keyed by build sha, which is great for uniqueness.  For human consumption it'd be nice to also optionally support semver for artifacts, based on the version in package.json.  Something like:
$ jq -r .version package.json
1.0.0
$ shep deploy --semver-artifacts --overwrite

Would create foo-1.0.0.zip artifacts, and overwrite them if they exist already.  If --overwrite was omitted and the key existed, an error would be thrown.
It likely also makes sense to tag the semver-key'ed object with the build sha to provide an immutable link to a git commit.

How would doing this break/change the existing s3 behavior? Or is that not happening because it is opt in with a flag?

I had guessed the least surprising thing was to only push the semver artifact if the flag was passed.  I'm open to it being supplemental and not binary if you think that has advantages.

If that's the case we should fix it. We're not dog fooding tha :/. Let me recap:

The idea behind hash keys is we could not deploy code we already deployed to another version. In practice its an extra layer of complexity and we've never gotten it working 100%.
The hash key is designed to match up with the hash that lambda calculates. I'm not sure if this is beneficial to shep at all. The idea was long term it prob would be.
The fact that we don't use any of this in at Bustle in prod is bad.

I'm 100% cool with adding this as a flag. In that case, is it on the dev to increment the version? Or can we make that part of the process? They get prompted to specify major, minor, patch?
I'm not sure what to do about the existing hash/s3 setup. We should either fix it or remove it entirely and do a major release. I'm 50/50

PS: Would also be nice to store this config in package.json#shep too

Would also be nice to store this config in package.json#shep too

I like that idea, but I think its slightly at odds with iterating rapidly during dev vs making a production release.
E.g. during rapid dev, I might deploy a dev version 10x without a version bump, and I'd like to just run shep deploy --env development.  When I'm done and ready to call this 1.1.0, I expect that I'll:

Bump version in package.json, commit it.
Tag the repo.
Run a deploy.

Maybe it makes sense to roll that up into a --release flag on deployment, as @reconbot mentions, and have that trigger the artifact build + upload?
Maybe that's an argument for a release key in the package.json, e.g something like:
{
  "name": "my-package",
...
  "shep": {
    "region": "us-east-1",
    "accountId": "XXX",
    "release": {
      "semver_artifacts": true,
      "s3_bucket": "..."
     }
  },
}


Added OpenSearch 1.1 manifest.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
This is a working 1.1 manifest that also builds with --snapshot.
./bundle-workflow/build.sh manifests/opensearch-1.1.0.yml --snapshot

It will need to be updated as fixes into https://github.com/opensearch-project/opensearch-build/issues/179 roll in.
Issues Resolved
Mostly addresses https://github.com/opensearch-project/opensearch-build/issues/196.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This is ready to review. It's a working 1.1 manifest, even though it uses forks/branches for a couple of projects and doesn't include performance-analyzer and performance-analyzer-rca. We can add those later.

Closing in favor of https://github.com/opensearch-project/opensearch-build/pull/274.


Slow processing of JSON

Can I do anything to optimize the performance of highlighting JSON in my app, or is this working as designed?
class JelloStyle(Style):
    styles = {
        Name.Tag: 'bold ansiblue',     # key names
        Keyword: 'ansibrightblack',    # true, false, null
        Number: 'ansimagenta',         # int, float
        String: 'ansigreen'            # string
    }

print(highlight(output, JsonLexer(), Terminal256Formatter(style=JelloStyle))[0:-1])

(I remove the last character because it seems for some reason highlight adds a newline character, but that doesn't seem to affect performance)
When I use the highlight function on a relatively large (6MB) JSON file, it adds 13 seconds to the output time:
time cat ls-R.out | jc --ls | jello -m
real    0m3.101s
user    0m1.727s
sys 0m0.537s

vs.
time cat ls-R.out | jc --ls | jello
real    0m16.916s
user    0m14.624s
sys 0m0.721s

Using the plain TerminalFormatter didn't seem to improve performance.

Could there be any performance gains by compiling some of the core functionality via Cython or perhaps with mypyc when/if it is ready?

It might, although I suspect that most time is spent matching the regexes anyway, and of course the regex engine is already C code.
So either we optimize the regexes, or we switch to a faster regex engine...

@kellyjonbrazil could you link to the file you're using, or suggest a way to locally produce a representative file?
For example, if it's a very very very nested structure, perhaps there are some opportunities to improve the internal stack processing of the JSON lexer. Or perhaps the formatter is doing some calls/lookups/whatever that, at scale, are adding some time. Or perhaps the lexer's regular expressions are truly the issue and it would be worthwhile to explore a faster regex engine like @birkenfeld suggested.
Whatever the root cause actually is, it will be helpful to have a representative (if not identical) sample file.
By the way, is your app exclusively writing 6MB of JSON to console? Are there any other use cases (other languages, other output formats, etc) that should be accounted for while investigating?

Hi @kurtmckee,
My application is called jc (https://github.com/kellyjonbrazil/jc) and it JSONifies the output of many commands. The performance issue would probably not be noticed in most situations since you would not normally want to see hundreds of megabytes worth of pretty-printed JSON text in the terminal, but I did notice it in testing.
To reproduce, you can redirect the output of a large ls job to a file:
ls -alR / > lsfile.out

Then you can run the following jc command to convert it to JSON in the terminal. When jc outputs to the terminal, Pygments will color the output by default. If the -m option is used, Pygments is disabled:
cat lsfile.out | jc --ls      # this is slow
cat lsfile.out | jc --ls -m     # this is faster

The JSON that Pygments is working on looks like this (it's relatively flat):
[
  {
    "filename": "CHANGELOG",
    "flags": "-rw-r--r--",
    "links": 1,
    "owner": "kbrazil",
    "group": "staff",
    "size": 336,
    "date": "Sep 25 10:52"
  },
  {
    "filename": "Procfile",
    "flags": "-rw-r--r--@",
    "links": 1,
    "owner": "kbrazil",
    "group": "staff",
    "size": 21,
    "date": "Aug 26 14:09"
  },
  {
    "filename": "README.md",
    "flags": "-rw-r--r--@",
    "links": 1,
    "owner": "kbrazil",
    "group": "staff",
    "size": 104,
    "date": "Sep 25 10:52"
  },

...

@kellyjonbrazil thanks for describing how to generate a representative file. I created a 118MB input file using jc, timed it, and then rewrote the JSON lexer and timed the new code.
118MB input file with current regex code
real    2m57.441s
user    2m41.297s
sys     0m10.030s

118MB input file with new code
real    1m42.079s
user    1m31.906s
sys     0m6.530s

This is a promising improvement but it isn't sufficient.
First, get_tokens_unprocessed() only takes 22 seconds to lex the 118MB file (compared with 63 seconds for the current regex lexer). That means 80+ seconds are spent elsewhere in Pygments.
Second, memory consumption explodes to over 3GB with both implementations. I haven't found where this is happening yet. A cursory tour of the lexer-to-formatter-to-output pipeline suggests that everything is handled through iteration, but it's definitely happening somewhere.
There are also other issues to resolve. The JSON lexer lacks meaningful unit tests. The JSON bare-object and JSON-LD lexers are dependent on the existing JSON regex lexer. And there's an opportunity to tokenize in-string escape sequences like \n or \u1234, which is missing from the current implementation. However, I don't want to tackle this until the runaway memory consumption is addressed.
I'll update again when I've addressed some or all of these issues.

I've submitted a patch to help improve your processing times. The JSON lexer is three times faster now, and unrelated to this ticket, the HTML formatter consumes 33% less memory that it did before.
There may be other improvement opportunities but this is a good place to stop either for feedback or for merging.


[Enhancement] support iceberg column stats

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[FE Incremental Coverage Report]
:disappointed: fail : 32 / 71 (45.07%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/iceberg/cost/IcebergFileStats.java
0
6
00.00%
[129, 133, 137, 141, 145, 146]

:large_blue_circle:
com/starrocks/catalog/IcebergTable.java
0
4
00.00%
[83, 117, 119, 124]

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/StatisticsCalculator.java
0
2
00.00%
[291, 294]

:large_blue_circle:
com/starrocks/sql/optimizer/operator/logical/LogicalIcebergScanOperator.java
0
2
00.00%
[63, 66]

:large_blue_circle:
com/starrocks/connector/iceberg/cost/IcebergStatisticProvider.java
18
42
42.86%
[87, 97, 98, 99, 104, 106, 107, 109, 110, 112, 114, 118, 122, 123, 126, 160, 161, 163, 164, 171, 173, 174, 175, 194]

:large_blue_circle:
com/starrocks/connector/iceberg/IcebergMetadata.java
1
2
50.00%
[286]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/sql/optimizer/statistics/ColumnStatistic.java
9
9
100.00%
[]

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)


Link fails on Node 8

I sometimes switch between different node versions and I noticed yalc link fails with node 8 today.
(node:94815) UnhandledPromiseRejectionWarning: TypeError: Symbol.asyncIterator is not defined.
    at __asyncValues (/Users/USER/.npm/_npx/94815/lib/node_modules/yalc/src/sync-dir.js:38:38)
    at Object.<anonymous> (/Users/USER/.npm/_npx/94815/lib/node_modules/yalc/src/sync-dir.js:99:33)
    at step (/Users/USER/.npm/_npx/94815/lib/node_modules/yalc/src/sync-dir.js:32:23)
    at Object.next (/Users/USER/.npm/_npx/94815/lib/node_modules/yalc/src/sync-dir.js:13:53)
    at fulfilled (/Users/USER/.npm/_npx/94815/lib/node_modules/yalc/src/sync-dir.js:4:58)
    at <anonymous>
(node:94815) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)

I reckon it's caused by this line here: https://github.com/whitecolor/yalc/blob/master/src/sync-dir.ts#L56.
Adding ESNext.AsyncIterable to the tsconfig might do the trick 👍

can you test and make PR for this?

You bet

Fixed in PR #86


[otp_ctrl] DAI interface write sw partitions digest error

Hi Michael,
Here is a corner case when writing SW partitions digests via DAI interface.
For example to write OwnerSwCfg Partition's digest, the DAI address is 1528, hex format is h5F8. Because the digest has a granularity of 64 bits. I think issuing any address between h5F8 to h5FF for DAI interface should work. The DAI interface works fine when I input direct_access_address between h5F8 to h5FB. But it has error if I input address between h5FC to h5FF.
Sequence is:

Write digest through DAI interface with address h5fc with wdata_0 h5985_54ea and wdata_1 with data he139_6c70
Read out digest through DAI interface with address h5fc, get rdata_0 h5985_54ea and rdata_1 0.
Read out digest through DAI interface with address h5f8, get rdata_0 0 and rdata_1 h5985_54ea.

So from the observation. The digest value writes to DAI address h5FC(wdata0)  instead of h5F8(wdata0).
Looking at the waveform, when writing data from DAI interface to OTP, I think the otp_addr_o has some issue. For digest with 64 bits granularity, the output address from DAI to OTP is 2fe. This treats the digest address as normal secret partition address. But I think RTL should treat it as secret and the OTP address should be 2fa.

Thanks,
Cindy

Thanks @cindychip. Yeah this was not entirely correct. PR with the fix is up.

Thanks @cindychip. Yeah this was not entirely correct. PR with the fix is up.


[feature] Revise Breeze's prompt template

Why are these changes needed?

Related issue number (if applicable)

Checks

[ ] I've run format.sh to lint the changes in this PR.
[ ] I've included any doc changes needed.
[ ] I've made sure the relevant tests are passing (if applicable).

As our discussion offline, this takes no effect on the arena.twllm.com where I serve open-access models by vllm openai server. Pls let me know if breeze uploads the chat template on hf


📦 Improve packaging export

This addresses many of the challenges in importing into a ESM native environment.
Improvements

Bundled and unbundled support for esm/cjs
Includes minified and unminified packages
Allows the build process to run in parallel
Puts types in their own directory
Includes source maps and the source folder so that debugging in vscode is easier for downstream packages
adds a clean function and a test:watch
Imports JSON #7
Adds the comment in the index.html demo to be correct for now (#9 should improve this)

Downstream implementations

https://github.com/executablebooks/markdown-it-docutils/pull/26
https://github.com/executablebooks/markdown-it-myst-extras/pull/1
https://github.com/executablebooks/markdown-it-amsmath/pull/7
https://github.com/executablebooks/markdown-it-dollarmath/pull/3

Closed issues:

#7

🚀


App freezes sometimes when create new window

Describe the bug
Sometimes, when create new window, the new window is totally empty without titlebar and app is frozen

I cannot interact directly in the UI anymore, but when I close the window by click "x" button in menu-bar, it can jump into my break point in close function (don't understand because if app is frozen, UI thread should not be occupied anymore?).
Call Stack when I break all while app is freezing (I used c#):

Steps to reproduce the bug
Sometimes happened when create new windows
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.3.2: 1.3.230602002
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

It looks like InProcessClient64.dll might be part of a product called "SentinelOne", do you have that installed?  It looks like it causes problems with some applications, for example: https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/InProcessClient64-dll-is-blocking-your-Autodesk-product-s-from-launching.html
If you are using SentinelOne, does this issue still happen when you disable it?

Closing for now, please reply if this is still an issue for you.


Search issues

It would be nice to be able to search issues. Maybe there is some Github API that could be reused for that?

:D

But GitHub is one click away from cddaiv ;)
Also to be perfectly honest cddaiv is rather hand-rolled in terms of the whole app structure. Would do it differently now (see e.g. cartographer). Given that I'm not very much for adding more features to cddaiv as it is.
Also CopperTube on IRC can search github issues :)

I was relaying this comment from reddit. He was looking to vote on something but he could not find it.


Docs improvement: add check of CVE feed

Update the release process documentation to add a final step:

Set a calendar reminder for yourself to check the CVE feed ( https://kubernetes.io/docs/reference/issues-security/official-cve-feed/ ) next day and ensure the automated process added the new CVE

The update should usually happen within a few hours.


isWritable Changes

Dear Ege, I have tested the changes, but don't merge the changes. Lets sit together and discuss the changes and push it

I have indented the code in Tester.ts file, still shows differently in git diff. But it is ok, when you check it in a editor


snipe-it: 5.4.3 -> 6.0.1

Description of changes
https://github.com/snipe/snipe-it/releases/tag/v6.0.1

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

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

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

[x] Fits CONTRIBUTING.md.

This major version bump defaults to PHP 8 from now on.
I will mark this as ready for review once I have built and tested the MR on one of my systems.

is this upgrade breaking enough that it deserves a mention in the release notes ?

I don't think so. It hasn't broken anything in my manual testing so far and therefore won't require any intervention by the user.


 Corrects a bug with the parsed set quantifier for bag operators. Previously when a set quantifier was unspecified, the default was ALL. Changed to be DISTINCT.
Other changes from this PR

BREAKING: partiql-ast: rename of SetExpr to BagOpExpr and SetOp to BagOp

Affects the AST and visitor

BREAKING: partiql-parser: Parsed struct's ast field is now an ast::AstNode<ast::TopLevelQuery>
BREAKING: partiql-eval: Evaluable trait's update_input fn now also takes in an EvalContext
Closes #237. branch_num is now used for bag operators. Removed the comment for add_flow_with_branch_num fn.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I proposed some clean-up via commit that I pushed. Everything else LGTM.

Thanks, clean-up changes in https://github.com/partiql/partiql-lang-rust/pull/400/commits/10745d318fd7ab3a0e952bc2c10a3fdc441e5e74 (e.g. using itertools, iterating over ValueIntoIterator rather than Bag, and multiplicity cleanup) look good to me.


refactor(eslint): top-level eslint

references #723
Removes eslint-config-custom package and implements top-level flat ESLint configuration, serving as the the primary linter configuration for all packages. package specific .eslintrc.cjs files are instructed to use the configuration defined in the top-level, and it more explicitly specifies the package's tsconfig.json for TypeScript-related linting.

Curious, do you think this solves a problem we have? The current config we have seems to be a turborepo standard thing. Moving it to the top level seems to be a net-neutral effect.

I think by removing dedicated configuration packages and leveraging inheritance, it has the nice property of reducing potential duplication. Since it extends the top-level configuration, it's also clearer when there are package-specific overrides, which can make it easier to read. This applies to the tsconfig.json as well.
I was sequentially going down the NPM publishing tracking issue to reduce our backlog.

I suppose my observation is that it doesn't remove the need for dedicated configs, it was using inheritance before, and there does not seem to be any de-duplication. At best, it seems like a net-neutral change. And in that case, I think it's best to stick with the default turborepo recommendation.