Everybody understands that debugger and LS are not cheap to develop. However, the CLR wasn't either, and it's open. Making tooling closed (and free) won't bring much revenue, but it will drive many users away (esp. devs in other tech will be unlikely to switch). I can't explain why they might want to do this, except maybe to cripple VSCode experience to drive VS revenue. Or they want to somehow monetize VSCode.

, its look to me partly a technical misunderstanding and bad unforgiven history.  aslo thanks to whoever canceled the cancel culture idea of closing the thread .  thats lame.  BUT  The LSP server standard  looks to me like it would provide hooks so custom tooling like game Level Editors or cad tools that have data or entities  with  with interfaced plugin scritps that are c# or another language ( hopefully not just a  .net one, mabye even  Julia that has tooling which uses LSP btw( , that  can have breakponts , and buttons for  steppiing in, out , over, , codecompeton, inspection, toolips, and I wont  even have to attach a debbuger ,so i can have a custom one in my level design tool which happens to be WPF.      I would love to see an example like AvalonEdit or RosylinPad or Notepad ++ but with ability fo r  debugging  scripts, but  using LSP as the protocol not an ad hoc thing.  for c# at least.    Now i have to attach a separate debugger,  make my own pipe  server and insert a temporary line of  Debug.Break  in my plugin script tool on my level editor for a video game.   I dont want to use two tools Vs code, or VS studio or anything else,   so reading the top of the thread i actually dont see why this this is a not a GOOD IDEA..   its essential.. unless im completely missing some point. itsopening hte .NET  platfrom to more custom tooling , not closing it.
Here is an example in Julia, for an IDE..    https://github.com/julia-vscode/DebugAdapter.jl/blob/master/src/debugger_requests.jl

I dont except to refactor a ton of the code in a session where i visualize my simulation and tweak my own Ai and bot controller via script.   i dont want all the featuers in vs 2022 for that..  in fact hot reload barely works anymore on my Vs 2022..    Julia has jumped in this space, having the scripting power of python, and the performance on c++..  But how deployable is it?    im using MOnogame for visualization and right now whats misssing besides multiplatfrom level edtinng is DEBUGGING script and UI.    so if i need to go multiplatfrom with my level editor  i guess ill go to Avalonia with the old WPF code since i have no hopes on  Maui or anyother high level UI framework from MSFT frankly.  Btu a debugger is low level common intracture that can be generalized and standardized and should be.
snnce I read Don Boxes book compoent software decades ago, a mix of open and closed source, binary components and open or owned source is why i embraced COM and then .net..  I almost died betting on Winodows phone an Silverlight and windows only, .net.. so i understand teh fear and loathing, and mistrust,  but now im hopeful and i ported all my graphics code to MonoGame for visualization and have some hopes for Silk .Net  for visualizaton and GPGPU..

@damian-666 Maybe you could move some of these thoughts to a blog post and link it as opposed to putting it all here.  I don't understand what all this has to do with the roadmap for the VS Code C# extension, but you are free to have a blog and put your thoughts there.

  Look at the announcement.at.thr very top . They admit .Vs code is using an antiquated substandard debugger protocol so they are moving it to LTS.   If they or anyone else think they want to  add some closed cource advanced intellisense or advanced features worth cash  money they can, but  open sources or others closed sources that use .net core, can make custom debuggers with basic or special purpose featutes, on the same standard API.    This way you can possibly mix and match languages, if I understand correctly.
Otherwise languages like Julia will be better than .Net.  They already use LTS for their IDE s Omnisharp is moving to LTS already.. its a new start,  Adhering to open standards.   Otherwise, c# might start to die when  it's finally showing promise after 20years, tragically misunderstood and resented because of haters.  We don't want that,  ok agreed?   Like every game studio CEO  making innovative riggings I need to own my own custom ide and not owni  can't have debuggable scripting without using some weird hack solution or attaching a separate debugger.    So I am not triggered by the announcement.  So even if if vscode regressing a bit in the meantime, it's because they are rearchitecting for the common good.

After all these months and reading through all these comments, I feel that most people have no idea what they are actually complaining/commenting about.
Rereading the first post, it seems to me that nothing is being lost and the only thing that is happening is a restructuring. A tool HOST is being put in-between the LSP (which is and always will be open source) and this host will be the entry point for OTHER/NEW software which is closed source. That's it. That's all that they said.
Nothing is being lost really, but they need some place to call their closed source software from, probably a place for the security keys or whatever.
@timheuer maybe you guys should have shown this as a diagram instead - sometimes people understand those better..
Current:
graph LR;
    vsc((VS Code - open source))-->lsp((LSP - open source));

New:
graph LR;
    vsc((VS Code - open source))-.will become default.->th((LSP Tools Host - closed source));
    th-->lsp((LSP - open source));
    vsc-. can still choose to use  .->lsp;
    th-->nt((New tools - closed source))

@timheuer This is how I understand the main post, and if it's wrong maybe you guys could correct me with a diagram 😊

@mika76 so they can hook in their private intellisense that they use for visual studio and the open source one will be left to die. As MS does all the time killing off open source projects in favour of their own.

@phillip-haydon look I don't know how MS hurt you 😉 but yeah they want to add in other closed-source tools.
But so what? you'renot going to lose basic intelli sense (which is currently pretty damn basic and it is also part of the open source LSP) - but maybe we get some better stuff. I mean the alternative is they leave it all as is and we never get anything better. Plus they said they will give the choice of still using the old direct-to-lsp connection or the new tools host, I just don't understand the fear-mongering or the complaining.

I just don't understand the fear-mongering or the complaining.

...which shows that you didn't read some parts of the complaints.
A very similar situation happened with Python in VS Code in the past. This opens the roads to driving OmniSharp to slow extinction (or rather, lagging in features), and limiting the closed source LSP only to official VS Code builds (including Codespaces). Essentially it is driving competition (like GitPod) out of the market.
OmniSharp benefits from the huge user base and that's how it drives some people to contribute to it. This move would essentially cut the user base to nearly zero by changing the default. It was already speculated that there are internal policies discouraging MS DevDiv employees from contributing to OmniSharp. The move would essentially dry out the other source of contributions.

@mika76 there are two kind of people here, one want liberation and one want better C# experience on VS Code and don't care if it is closed source. I'm one of who want liberation. The main problem for me with this issue is it is ultimately killed Omnisharp. Why MS not just create a new C# extension without interfere with this one, which is open-sourced from the beginning?

@mika76 there are two kind of people here, one want liberation and one want better C# experience on VS Code and don't care if it is closed source. I'm one of who want liberation.

Believe it or not I want both and I don't think it's mutually exclusive. I am perfectly fine with having closed source extra features as long as it doesn't cripple the core functionality.
I was a pretty heavy VS and VS4Mac user in the past but the quality and inflexibility of the products forced me to switch over to VS Code. Back when MonoDevelop was still a thing I used to fix the performance issues directly by contributing, and eventually getting the fix shipped with VS4Mac some time later. Nowadays I make profiles of the closed-source code and report it back to the teams and wait for them to fix it. Not only this makes the turnaround much longer but I also need to invest way more time into understanding the internals without source code, comment, and code history. This is not a win for anyone.
If there was an open source LSP with core functionality and closed source one with some extra (eg. IntelliCode) built on the same code base that would be a good start. It would ensure that the core functionality evolves and does not break.

If there was an open source LSP with core functionality and closed source one with some extra (eg. IntelliCode) built on the same code base that would be a good start. It would ensure that the core functionality evolves and does not break.

It is fine as long as they create a new one without interfere with the open-sourced one. Otherwise they are going to kill the open-sourced one for sure.

@filipnavara

...which shows that you didn't read some parts of the complaints.

Oh I've read em all since June, but it just seems to me that people are complaining about things that have not being stated. I mean even what you said "...limiting the closed source LSP..." - they specifically stated that the LSP is not being closed-sourced (if that's a word) and that there will just be a tools host in between to call other closed-source tools.

OmniSharp benefits from the huge user base and that's how it drives some people to contribute to it...

The thing is that Omnisharp seems to have been stagnating till now anyway, so unless you get MS to help it forward then how is that better?
@ultimaweapon, @filipnavara

there are two kind of people here, one want liberation and one want better C# experience on VS Code and don't care if it is closed source.

If there was an open source LSP with core functionality and closed source one with some extra (eg. IntelliCode) built on the same code base that would be a good start. It would ensure that the core functionality evolves and does not break.

That's just the thing - from what @timheuer has written nothing is being closed really, they just need a branch off to be able to call closed-source tools - the existing stuff is still open source and continues as it currently is. I see this as a kind of proxy server between the current lsp, vscode and any new tools.
Of course this is my take on what was written so I might be wrong. It would probably help if someone from MS comments officially on this thread as I'm sure they've decided on a way forward since June...

We at F#, also did it that way for historical reasons, and let me tell you, that it introduced a lot more complexity and obviously performance penalities.

Citation needed.

I personally welcome this announcement.
C# development on VsCode is an absolute joke, the language server needs to be restarted multiple times per day and sometimes breaks entirely for no reason.
Yes I would I have preferred if it was open source but Omnisharp has proven to be very buggy and unreliable and I have not seen any significant improvement in the last years.
I suppose people who want to keep their entire workflow open source can keep using Omnisharp but I am more than willing to use a proprietary language server if it improves the development experience.
Is there any kind of ETA by the way?

I personally welcome this announcement. C# development on VsCode is an absolute joke, the language server needs to be restarted multiple times per day and sometimes breaks entirely for no reason. Yes I would have preferred if it was open source but Omnisharp has proven to be very buggy and unreliable and I have not seen any significant improvement in the last years. I suppose people who want to keep their entire workflow open source can keep using Omnisharp but I am more than willing to use a proprietary language server if it improves the development experience.
Is there any kind of ETA by the way?

https://github.com/muhammadsammy/free-omnisharp-vscode
There IS an open source debugger, and its maintained by Samsung.
Is it not surprising, that even niche languages get their VSCode support working and Microsoft struggles to do that - on their own platform 😅

The debugger is not the problem, at least not for me.
The one that ships with Omnisharp, although proprietary, works fine.
What does not is the intellisense part. Suggestions are often slow or broken, analyzers just don't work, etc...
This is what this proposal will hopefully fix.
I don't know why Omnisharp is so bad, maybe it's indeed because of a lack of contribution from Microsoft.
In any case it is close to unusable for anything but hobby projects so having the choice to use another,  hopefully better, language server, gives me hope that C# development on VSCode will be finally possible.
It would have been great if it were open source too but to me it's more important that the CLR and BLC remain open source, I can deal with a partially closed-source IDE.

#Offtopic a bit but towards thr general topic and problem at hand...
debugging c# and code completion judt mentio0ned. Im curious wnat not use
community editon 2022 ide anyways,.i found it faster. Because it caches
files here and there, and i needed a touch screen to target touchdevice,
and not too many options rhere.  Is this becasue its runing  linux?
Im looking into cusrom ide for domain specific reasons and soft debuggers,
so i try notepad plus plus and maybe rosylin pad..  and use scripting hosts
liie cs script and not sure which debug strategy inwan..i rather not block
the ui threat at all so im going with soft debugging, code waypoint
injection and custom visual inspection..its a pain in many.cases to stop
all the threads.  Also code completion andnall that im teating git copilot
with mixed results .. if this should branch to some.other area of
discussion im curius where because i have to make an ide for a specific
case, say CAD , i dont want two ide on my screen..
On Sun, Jan 15, 2023, 8:49 AM XorZy @.***> wrote:

The debugger is not the problem, at least not for me.
The one that ships with Omnisharp, although proprietary, works fine.
What does not is the intellisense part. Suggestions are often slow or
broken, analyzers just don't work, etc...
This is what this proposal will hopefully fix.
I don't know why Omnisharp is so bad, maybe it's indeed because of a lack
of contribution from Microsoft.
In any case it is close to unusable for anything but hobby projects so
having the choice to use another, hopefully better, language server, gives
me hope that C# development on VSCode will be finally possible.
It would have been great if it were open source too but to me it's more
important that the CLR and BLC remain open source, I can deal with a
partially closed-source IDE.
—
Reply to this email directly, view it on GitHub
https://github.com/OmniSharp/omnisharp-vscode/issues/5276#issuecomment-1383169665,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD74XGP6CEUOFU7RYD34RJLWSQFARANCNFSM5Y4EX2YQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Does anyone have any info on how progress is going? Has been 7 months since the original announcement

Agree, everybody is now waiting with new development based on omnisharp (eg SonarLint c# for vs code) because this posts makes the future very unclear. And to quote your first post:

Next Steps (these will ideally be issues that will be trackable, timelines of these may vary)

Where are the tracking issues?

Moving to JetBrains Fleet as of today on my Mac, VSCode is a great little editor but the C# support as it currently stands is simply hopeless.  I can't comprehend how people decide to actively contribute to this project whilst the core of it simply does not work, I definitely must be missing something.

Ha yes, just tried Fleet but the base functionality wasn't quite what I was expecting... Rider it is.  Shame as I like the simplicity of one IDE for all.

Rider is free for open source contributors.
https://www.jetbrains.com/community/opensource/#support
Much fun!

For Rider, it works well because of the plugins. I was able to run a project that had a React TypeScript SPA. The only missing piece out of the box was a CSS-for-JS / Styled-Component syntax. And a plugin was available to do that.

I mean if people are not satisfied on what Microsoft is doing, perhaps the best way to show them that maybe they should reconsider their stance on things, is to vote with their actions and use something else. They sure as hell don't seem to respond super well to this sort of thing. (I dont know, almost seems like entire VSCODE team really could care very little what users think)

Having heard in October that the team is actively working on this, but it's taking longer than expected, then the issue might be something else other than that the team does not care. Maybe we just need some high level update to know what to expect. How many official updates on this happened since the original announcement 9 months ago?

Yeah @timheuer it's ridiculous that this thread has been left here with no official comment...

Given that both C# and VSCode are developed by Microsoft I think it's reasonable to expect C# to have first-class support.

VS is making Microsoft a lot of money.
VSCode is not making a lot of money.
If they would just provide a first class support in the later, they would simply loose money.
This new extension is meant to "port" that money cow from VS to VSCode.
It's that easy.

VSCode is not making a lot of money.

Microsoft (Github) Codespaces uses VS Code primarily, and is seen as the future of IDEs by some.
Frankly, the one who likes VS Code more, is more likely to go to Rider than to go to VS.
I'd expect a lot of VS users to be MSDN subscribers, and continue to be regardless of VS, for things like Azure DevOps, and other software, etc.

VSCode is not making a lot of money.

Microsoft (Github) Codespaces uses VS Code primarily, and is seen as the future of IDEs by some.
Frankly, the one who likes VS Code more, is more likely to go to Rider than to go to VS.
I'd expect a lot of VS users to be MSDN subscribers, and continue to be regardless of VS, for things like Azure DevOps, and other software, etc.

is anything stopping you from going to rider?

VSCode is not making a lot of money.

Microsoft (Github) Codespaces uses VS Code primarily and is seen as the future of IDEs by some.
Frankly, the one who likes VS Code more, is more likely to go to Rider than to go to VS.
I'd expect a lot of VS users to be MSDN subscribers, and continue to be regardless of VS, for things like Azure DevOps, and other software, etc.

is anything stopping you from going to rider?

IMO VS Code has the best text editing experience out there. Rider has a VS Code keymap but it's not implemented properly.
Vim/NeoVim is probably superior but requires many more hours to learn it properly. Plus implementations like Azure Data Studio mean I can use the same keybindings for DBA work as I do for coding. And then Jupyter was added, and then Polyglot notebooks. And extensions like Dendron for Knowledge Management. Oh, and the PowerShell extension for all server/windows admin tasks.
If the C# extension is sorted I'll only ever need to use VS Code for ALL of the above work contexts. Would also make onboarding new users extremely simple

Vim/NeoVim is probably superior but requires many more hours to learn it properly.

See Helix

And yet nobody mentioned Window's Notepad being the best IDE.
It's best for:

simplicity
responsiveness
support dark mode natively and completely
100% free with Windows
100% free of garbage features
easier copy & paste of code

Except it’s not an IDE, it’s a text editor.
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: AraHaan @.>
Sent: Monday, March 27, 2023 9:54:57 AM
To: OmniSharp/omnisharp-vscode @.>
Cc: Russ Freeman @.>; Comment @.>
Subject: Re: [OmniSharp/omnisharp-vscode] Announcement: A roadmap update on the VS Code C# extension (Issue #5276)
And yet nobody mentioned Window's Notepad being the best IDE.
It's best for:

simplicity
responsiveness
support dark mode natively and completely
100% free with Windows
100% free of garbage features
easier copy & paste of code

—
Reply to this email directly, view it on GitHubhttps://github.com/OmniSharp/omnisharp-vscode/issues/5276#issuecomment-1484758265, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AACDWXM5RRIXJQWX6O36TOTW6FIWDANCNFSM5Y4EX2YQ.
You are receiving this because you commented.Message ID: @.***>

Of course it is - the plug-ins make it an IDE.

From: Giorgio Galante @.>
Sent: 27 March 2023 11:18
To: OmniSharp/omnisharp-vscode @.>
Cc: Russ Freeman @.>; Comment @.>
Subject: Re: [OmniSharp/omnisharp-vscode] Announcement: A roadmap update on the VS Code C# extension (Issue #5276)
Except it’s not an IDE, it’s a text editor.
…
VSCode is not an IDE either - it’s a text editor with plugins.
—
Reply to this email directly, view it on GitHubhttps://github.com/OmniSharp/omnisharp-vscode/issues/5276#issuecomment-1484885059, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AACDWXNZFCL5MFDZV3HRNBLW6FSOJANCNFSM5Y4EX2YQ.
You are receiving this because you commented.Message ID: @.***>

Of course there is always Notepad++ as well.

When are we going to get an official statement?
It's been almost a year and we still have no idea when (if ever) the new language server will be released.
Since the original announcement it appears development on Omnisharp has almost completely stopped, as nobody wants to contribute to a project that has been abandoned by Microsoft.
The extension is currently broken, there is no other way to describe it. It's not just the odd bug, it is simply unusable.
There has to be zero quality control before release since each one manages to be worse than the one that came before it. It is seriously unprofessional coming from such a big company as Microsoft.
I do not get why they made this announcement, which they knew was going to kill Omnisharp, and then delivered nothing.
In my opinion this situation is seriously tarnishing the image of Microsoft and C#, which is the least supported language in the most popular IDE.
If MS continues to keep silent on this issue, it is going to be difficult not to think their intent was to kill Omnisharp and to force people to go back to Visual Studio.


Fix select placeholder not showing

[X] Changes have been thoroughly tested to not break existing functionality.
[ ] New functionality has been documented or existing documentation has been updated to reflect changes.
[ ] Visual changes are explained in the PR description using a screenshot/recording of before and after.

This PR should fix issue #6736
It seems the problem lies in watch method. this.refreshPlaceholder() is called at the beginnging of the watch, but then this.select.clearStore() is called which removes the placeholder. Adding this.refreshPlaceholder() after this.select.clearStore() fixes this issue.
You can test this by just removing clearStore() and the placeholder will show. I'm sure clearStore is needed so the easiest option seems to be to refresh the placholder after calling clearStore().
Potentially we could get rid of the first refreshPlaceholder, but with the early return when the state is still being updated, maybe it needs to stay?

how can I upgrade this fonctionality?
composer update & php artisan filament:upgrade didn't change anything?
sorry I'm beginner with github and this community...

Wait for a new release to be made, this has not been released yet


Resolves orientechnologies/orientdb #3268

JS API library doesn't support empty passwords

I'm not sure if OrientDB supports empty password in the backend. Have you tried it?

OrientDB supports empty passwords, at least via the REST-API used by the JS API library.

It's ok for me, but please send it to "develop" branch, not master: we use master only for releasing.


Newstepper

Description
This is a tutorial for using the nodes called Stepper Motor driver Tic and Stepper Driver motor Tic Knob in order to control a motor with the Flojoy App
Inputs & Outputs
Input data : None
Output node : End (To stop the process)
Example APPS
This is the PR for the app repository:
https://github.com/flojoy-io/apps/pull/5
Integrating the Node
Only the node and the end node after that, just need to have a good hardware setup to control your motor.

Looks good.
Is the max current always 30? Or should it be a param with a default of 30?
Also can you add a short docstring to each function?

Hey @Angchau , is this ready now?

Hey @jackparmer, Yes it's ready for merge !!

Ready for merge with the new manifest files , @jackparmer

Now this PR should be ready with the last version of Manifest files with the good syntax, @jackparmer


Only output objects if something has changed

The install and update commands should only output objects if they change something: find a new version, install a new version, etc.

Fixed in 0.8.0.


merge from template-arlac77-github

package.json

chore(deps): add ^10.2.0 remove ^10.1.0 (devDependencies.npm-pkgbuild)

:tada: This PR is included in version 1.10.103 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.10.103
GitHub release

Your semantic-release bot :package::rocket:


Double quotes in value of prompt() can't be shown

If the "value" parameter of prompt() contains double quotes, the string is cut at the first double quote.
E.g. the code below only shows 'a'.
smalltalk.prompt('hello', 'world', 'a"b"c').then(function(value) {}, function() {});

It seems that double quotes aren't being escaped.

Thank you, fixed with f68cfec. Landed in v2.1.4.

Just updated to the newest version.
Thank you for the quick response   :)


Can't add integration with nabu-casa cloud instance of HA?

I get about as far as adding the integration, to configure it I get to the "URL you use to access Swatch (ie. http://ip.ad.dr.ess:4500/)" window.
I don't yet have a URL to access Swatch since I'm still adding it as an integration, so it's a little confusing.
I added my nabucasa URL and it errors out. What are we supposed to put there?
Additionally at the bottom of the read me it says "Please visit the main Swatch documentation for full installation instructions of this integration." but there is no installation instructions.

The integration is separate from the addon, which you need to install first.


feat: Piglets GRAPHITE-5346: #Health widget extension with donut graph

Closes #
Summary
Allow to display donut graph in valuecard
Change List (commits, features, bugs, etc)
src/components/Card/_card.scss
src/components/Dashboard/CardRenderer.jsx
src/components/Dashboard/Dashboard.story.jsx
src/components/Dashboard/snapshots/Dashboard.story.storyshot
src/components/ValueCard/Attribute.jsx
src/components/ValueCard/GraphRenderer.jsx
src/components/ValueCard/ValueCard.jsx
src/components/ValueCard/ValueCard.story.jsx
src/components/ValueCard/ValueRenderer.jsx
src/components/ValueCard/snapshots/ValueCard.story.storyshot
Acceptance Test (how to verify the PR)
Allow to show donut graph in side the valuecard by passing cardType,
The valuecard getting tow parameters ( value , thresholdRange) as attributes.
On the behalf of value and thresholdRange, card display as donut chart

tests here

FYI: This new PR will probably close this issue and PR https://github.com/IBM/carbon-addons-iot-react/pull/885

this has been superceded by the new PR


Upgrade crates

Upgrade dependency library versions. This includes upgrading to rpm-rs so that RPMv3 is no longer supported i.e., which is to close #106.

Cent OS 7 has reached its EOL. It's time to merge this pull request including RPMv3 drop.


For auto language

could you use
"System.Threading.Thread.CurrentThread.CurrentCulture.Name"
instead of  "CultureInfo.InstalledUICulture" for auto language detection?

The different between those ，already be discussed in this url：
https://stackoverflow.com/questions/329033/what-is-the-difference-between-currentculture-and-currentuiculture-properties-of

If you mean what is happening in LocalizationHelper.cs after clicking on Autodetected language in Language options, then we need to use CultureInfo.InstalledUICulture, because it's the only one that always provides specific cultures (such as pt-BR as opposed to just pt). We have defined our own language codes management, so sometimes specifics are needed, sometimes neutrals. But we always should start from specifics. When we have a specific culture and there is a resource file for that culture, then we are good to go. If there is no resource file for that culture, we can check for parent culture (which is always neutral culture, for example, pt is the parent of pt-BR) and check if we have a resource file for that. Again, if we have that's great, but otherwise (which means that language is unsupported) we switch to the English language, which is always present and ready to use.


Install problem with agular1.4.5

When I want to install ngFx for my project with angular 1.4, I face the following output:
$ bower install ngFx --save

bower ngFx#*                    cached git://github.com/Hendrixer/ngFx.git#1.1.0
bower ngFx#*                  validate 1.1.0 against git://github.com/Hendrixer/ngFx.git#*
bower angular#~1.3.0            cached git://github.com/angular/bower-angular.git#1.3.19
bower angular#~1.3.0          validate 1.3.19 against git://github.com/angular/bower-angular.git#~1.3.0
bower gsap#~1.11.6              cached git://github.com/greensock/GreenSock-JS.git#1.11.8
bower gsap#~1.11.6            validate 1.11.8 against git://github.com/greensock/GreenSock->JS.git#~1.11.6
bower angular-animate#~1.3.0    cached git://github.com/angular/bower-angular-animate.git#1.3.19
bower angular-animate#~1.3.0  validate 1.3.19 against git://github.com/angular/bower-angular-animate.git#~1.3.0
bower angular#1.4.5             cached git://github.com/angular/bower-angular.git#1.4.5
bower angular#1.4.5           validate 1.4.5 against git://github.com/angular/bower-angular.git#1.4.5
bower                        ECONFLICT Unable to find suitable version for angular

I tried to use resolutions to point to "angular": "~1.3.x", but nothing happened. Any idea?

+1. Same problem for me

sorry for the delay! I'm releasing ngFx v2 tonight, all will be solved!!

check out the latest version


Not working with nRF52

Presumably there is an assumption about the clock rate of the SoC and that's why.
Tested empirically (adjusting # of NOPs):
nRF51: 9,0,1,8
nRF52: 41,20, 20,41
This works ok for first LED on strip but cracks up after that. Not accurate enough.
On the 52 it may be possible to do this better with interrupts. Not tried yet.

Hello, Paultanner,
I am having some problems trying to work with nRF52, I change the # of NOPs but still not working,
Could you provide your sorce code ? ( I just need one LED)
Thanks,

I trying to use this on a nRF52840. Did you guys figure anything out?

Has anyone tried out the above code on the nRF52? I'm interested in an alternate method to the Adafruit library

The core of the nRF52840 is clocked at 64MHz. Referencing this document https://learn.adafruit.com/adafruit-neopixel-uberguide/advanced-coding describing the transmission protocol, I modified the number of NOPs to the following, which works for me. Don't forget that if you are using the radio, then softdevice interrupts could scupper your timings: there are a number of ways to solve this issue (timeslots, or temporarily disabling the softdevice).
Note, I didn't bother taking into account the loop/if cycles: at 64MHz they execute quick enough to be within the margin of error - so you could probably make this tighter, if you were inclined.

@pstids Could you include a simple but full sketch which works for you? Do you work with Arduino?

Hello
I would like to use this library in nrf52832.  Could you tell me about the NOP correction for 52832?
Thank you.

@schosdas: look here
https://github.com/Protonerd/nrf52-neopixel
This library is based on the nRF51 lib here, modified and fully debugged by myself and my friend Stefan with a logic analyser. Works great in our project.

@schosdas: look here
https://github.com/Protonerd/nrf52-neopixel
This library is based on the nRF51 lib here, modified and fully debugged by myself and my friend Stefan with a logic analyser. Works great in our project.

Kudos to lavallc and pstids for the hints, it did only take a bit of an effort to port it to nRF52

Kudos to lavallc and pstids for the hints, it did only take a bit of an effort to port it to nRF52


Fix ODR-672 and ODR-673 where poller fail to create on Platform-H

Changes include:

Not only looking on catalog source 'bmc' for ipmi IPs, but also
look at 'rmm', 'bmc-2', 'bmc-3', 'bmc-n'.
Print a debug message when no bmc ip found for creating default
poller.

This PR goes to release 1.2 branch.
@RackHD/corecommitters @yyscamper @anhou @iceiilin @WangWinson

*** BUILD #704 ***

test this please

*** BUILD #709 ***

test this please

*** BUILD #716 ***

I have tried Jenkins test multiple times. Build #704 and #709 fails with discovery timeout, build #716 seems fail with jinja2  download fail. The same piece of code pass on the master branch but fail on the 1.2 branch. I had also tested this code locally and it passed also.
I am more worried about #704 and #709 where discovery timedout. Does anybody know how can I get a copy of the on-taskgraph.log from the Jenkens builds? I am running out ideas on how to debug into this issue without digging into the RackHD log files.
Help! @RackHD/corecommitters @yyscamper @anhou @iceiilin @WangWinson

@cgx027 my PR https://github.com/RackHD/on-http/pull/273 fail Jenkin , too

I have seen the same error on https://github.com/RackHD/on-tasks/pull/197.
Looks like a common error.
@jlongever would you please help take a look?

Jenkin's isn't setup to smoke-test release branches, only master.

I had some comment in this PR: https://github.com/RackHD/on-tasks/pull/198
:+1: after the same comment is addressed.

@jlongever , if so , why the Jenkins fails this PR?

@jlongever : I think if Jenkins doesn't test this kind of PR, it's better to skip and mark it as passed, even better to give some clear message, so people will not confuse. How do you think?

@yyscamper it failed because it's running master functional tests against 1.2.  Jenkin's wasn't setup for release branches.
RackHD:release/1.2.0-branch from cgx027:bugfix/ODR-672/673_platform-H_empty_poller_1.2

@jlongever, yes, this is the cause, so we just ignore this jenkins failure?

@yyscamper yes,  at least until Jenkins jobs have been created to support release branches.

@jlongever , OK, since the PR (https://github.com/RackHD/on-tasks/pull/198) for master has passed the Jenkins, so it's safe to go ahead merge this PR as long as got enough approval.

Thanks @jlongever  and @yyscamper .

*** BUILD #725 ***

👍


file_field behaves unexpectely when used with table

file_field when used with table may result in zero records.
There may be problem fwith file_field when calculating cartisian product.
Either it does not seek file object or something else.
Here is implementation code for file_field.
class file_field(field):
    '''Creates field from file path'''
    def __init__(self, name:str, path, read_all=False):
        '''
        Creates file_field object

        ----------
        name: str
            Name of field
        path: str | bytes
            File path pointing to file with field items.
        read_all: bool
            True if should read all items to memory at once.
        '''
        self._path = path
        self._file = open(path)
        super().__init__(name, self._read_file_items, read_all)
        if read_all:
            # Close file handle as its content will be read at once.
            # It will never be used again.
            self._file.close()

    def _read_file_items(self):
        # Reads lines from file in path, returns generator.
        # This method may be called within __init__().
        for line in self._file:
            line_ = line.rstrip("\n")
            if line_:
                yield line_

    def _read_items(self):
        # Seeking may cause problems if file is used in multiple places.
        # This method may be called within __init__().
        self._file.seek(0)
        return super()._read_items()

    def close(self):
        self._file.close()

    def __enter__(self):
        return self

    def __exit__(self, exc_type, exc_val, exc_tb):
        self.close()

This is a bug since method _read_items(self) will in most cases be called once as implemented in field class.
_read_file_items(self) is the one that creates items and it end up reading file without seeking to the begining.
_read_items(self) is sometimes called when getting items but not always.
_read_items(self) gets items in their iterable form by calling any callable and the returning their items.
File handle/object should be seeked within _read_file_items(self) for better result or implement method to do it.

I tried to make changes and here the furthest I was able to go.
class file_field(field):
    '''Creates field from file path'''
    def __init__(self, name:str, path, read_all=False):
        '''
        Creates file_field object

        ----------
        name: str
            Name of field
        path: str | bytes
            File path pointing to file with field items.
        read_all: bool
            True if should read all items to memory at once.
        '''
        self._path = path
        self._file = open(path)

        def file_items_func():
            # Returns generator with items of files.
            # Every call will recreate generator by seeking file to pos 0.
            self._file.seek(0)
            return self._read_file_items(self._file)

        super().__init__(name, file_items_func, read_all)
        # Close file handle as its content will be read at once.
        if read_all:
            self._file.close()

    @classmethod
    def _read_file_items(cls, file):
        # Reads lines from file in path, returns generator.
        # This method may be called within __init__().
        for line in file:
            line_ = line.rstrip("\n")
            if line_:
                yield line_

    def close(self):
        self._file.close()

    def __enter__(self):
        return self

    def __exit__(self, exc_type, exc_val, exc_tb):
        self.close()

Now before _read_file_items(self) is called, file is first seeked.


UI: display unvaulting vaults in stakeholder home panel

unvaulting | unvaulted vaults should have a section in stakeholder home panel and a button "Cancel" to cancel the unvaulting

I think it's done?


[feat] SSR never option

This pull request aims to close #1650 by adding a never value to the ssr option, preventing svelte kit from importing the files on the server altogether.
Other alternatives: add spa option to config.
Todo list:

[x] Build simple approach
[x] Add tests
[x] Document feature
[x] Add changeset

Thanks for this! I rebased the PR against master so that the lint job would pass

Hey @benmccann, do you how can I create a new test app?

Do you think the docs are clear enough?

Is there any known workaround while this PR bakes? As far as I can tell, this issue completely blocks final building our SPA that uses web workers extensively.

Here are the current workarounds

Thanks for the PR. I'm -1 on this — this has been discussed in the maintainer's chatroom but not here, I think, so let me explain:
In general, we want to encourage the use of SSR as widely as possible. We therefore don't want people to solve the 'I can't SSR this particular page' problem by disabling SSR for the entire app. While there are situations where disabling SSR app-wide is the correct thing to do, in the many cases where that's not the case, the existence of this option would encourage bad practices.
I think something like the following is preferable:
export function handle({ request, resolve }) {
  return resolve(request, { ssr: false });
}

That way it can easily be scoped to specific parts of the app, for example, or even conditionally enabled for some UAs. It requires some discussion (not sure if adding options to resolve makes the sequence helper too complicated, for example) but I think that's the right direction to go in.

I might suggest resolve({ request, ssr: false }) while we can still sneak in breaking changes. We had opted for positional arguments at the time because there was only one and we only foresaw there ever being one, but once we have two, I think it makes sense to make them all named, not just the new options.

@Rich-Harris  - I'm working on a Native binding (kinda like Node-Gui & NativeScript Svelte) but mine connects using GTK from node.    Having a easy method to completely disable SSR would be a god send.    I've already had to start "rewriting" .svelte files after parsing into js to change any import x from "svelte" to import x from "svelte/internal" because the svelte package.json file is set to hand me the SSR.js file when you include svelte from node.  Which then of course break the events like onMount.      I don't believe this PR deals with this specific issue, but before you discount adding a method to completely disable it -- there are valid use-cases where SSR is completely unwanted and there needs to be some way to disable it either during compiling or via some setting which is the point I am wanting to bring up.   :grinning:

Rich's suggestion would allow you to completely disable SSR if you'd like. It'd be more powerful though - it would let you decide whether to disable on a per-page / per-request basis. If you really have a need to always set it to false you could do that still, but it would also give you far more power to do things like enable it only for GoogleBot, disable only for /admin route, or whatever else you'd like to do. I think making it more flexible in that manner is a good idea

I agree that Rich's suggestion is a more powerful option, but is it possible to have both options? I mean accepting "SSR never option" now (thinking on those cases where disabling SSR app-wide is the correct thing to do) and build the other better option in the future for more flexibility.
I think having the ssr never option in the short period will increase a lot Sveltekit (and Svelte) popularity among full SPA users, because they are going to have a framework with standard routing system, etc... I often see SPA users having problems with sveltekit and finally opting to use other alternatives (like routify).

No, we're not going to implement short-term solutions. I don't think it'd be terribly difficult to have the option passed from handle instead of svelte.config.js, so we should just do it right the first time around

I think having the ssr never option in the short term will increase a lot Sveltekit (and Svelte) popularity among full SPA users, because they are going to have a popular svelte framework with standard routing system, etc... I often see SPA users having problems with sveltekit and finally opting to use other alternatives (like routify or going back to Angular / React).

@fabiot21 This is exactly my current situation. I have been hopeful this PR would land in time for the next release. We have a total "local-first" PWA which does not communicate with a backend for anything except to synchronize an IndexedDB database from a  Worker . I get considerable trouble from SSR even thought its of no use to me for both Worker and IndexedDB objects, even with the static adapter. I much enjoy everything else about Sveltekit

I think something like the following is preferable:
export function handle({ request, resolve }) {
  return resolve(request, { ssr: false });
}

That way it can easily be scoped to specific parts of the app, for example, or even conditionally enabled for some UAs.

That's a great solution, but it doesn't solve one problem: the final app bundle. All sveltekit pages and their dependencies are bundled into app.js regardless of whether they actually need to be. Moving ssr evaluation to handle makes it too flexible, because we can't make it clear which pages will be SSRd at compile time, so every page will get bundled and that would result on the same x is not defined errors for side effect imports.

I don't understand why I'm am being marked as off topic for simply acknowledging that @Rich-Harris is right:

... While there are situations where disabling SSR app-wide is the correct thing to do ...

I understand that I disagree with some of the dev's poosition, but pretending that how I'm actively using SvelteKit is noise, is pretty toxic thing to do.
I honestly don't understand how disabling SSR app wide for a PWA that depends on browser specific API is bad practice. I also fail to see why that usecase is not important  enough to support just becuase some users could use a feature wrong.
Maybe (ikely) I just don't understand, but I don't see how handle replaces ssr: never in my case. I need SvelteKit to never run the final JS during the static build. For one example: loading data from IndexedDB in component load function. I don't have an API to fetch from, just IndexedDB to load from.

@abalmos the intention with Rich's suggestion was that you be able to set ssr: false on every page (i.e. app-wide), but also have finer-grained control. It seemed like that would solve your needs and so just saying again that you care about the feature wouldn't really change anything - we were already trying to provide a way to do what you want. The comments were hidden because they didn't add any technical details. We do know that there's a real need here - https://github.com/sveltejs/kit/issues/1650 has 49 thumbs up, which is how we track user demand for feature requests. We try to keep PRs purely focused to the implementation details. If all 49 people who wanted the feature were chiming in about it, we'd not be able to figure out how to get this out the door because the real discussion would get lost. Apologies in advance - I'm going to hide this comment and the last one as they don't relate to the PR. But I do understand the very real frustration in dealing with SSR errors when you're just trying to build a client-side app and we're not ignoring that - just trying to keep the discussion focused on how to solve it

But ssr: false isn't sufficient, unless your also going redefine that to mean what ssr: never means in this PR?

@JeanJPNM that's a great point.
I think there are two reasons things might get bundled right now

Kit sets inlineDynamicImports to true by default: https://github.com/sveltejs/kit/blob/d15e369bc80c7b521f1d86d6be9c6d547a0e6526/packages/kit/src/core/build/index.js#L445
The adapters run the Vite output through esbuild

If we can merge https://github.com/sveltejs/kit/pull/2580 then hopefully it would address both those points and allow Rich's suggestion on how to implement this to work still. I haven't tested to make certain, so maybe you'd like to take a peek at that branch and see if it would help here?

But ssr: false isn't sufficient, unless your also going redefine that to mean what ssr: never means in this PR?

Ah, I think you didn't quite understand @Rich-Harris's comment the same way I did. If ssr: false is passed in via handle then I interpreted that to mean that would be the final decision about whether the page was server-rendered. That means we'd not have to load the page to read the ssr config value embedded in the page and, by not loading the page on the server, we'd avoid all the pain that people experience. (Whether that means the ssr option still exists on the page or not I don't know. We'd have to discuss that. But I think it solves the issue either way as long as the handle value takes precedence)
That would provide a way to say "just shut this damn thing off", but you have an option to do it on a page or set of pages and don't have to go straight to disabling it for the whole app - which I think was the objection to having a global never flag with no finer-grained control.

@benmccann I appreciate the conversation. That is how I understood the proposal as well, but wouldn't that scheme still have problems when an import has something browser only, like in this comment: https://github.com/sveltejs/kit/issues/1650#issuecomment-886037938 ?
My concern boils down to (and currently is) that the module context has browser only imports because of code in load.
Or is SvelteKite somehow able import just the handle function without evaluating the module context's imports?

Or is SvelteKite somehow able import just the handle function without evaluating the module context's imports?

handle does not require the imports in your module to be evaluated. Today when handle calls resolve, resolve ends up loading the page on the server, but that would no longer happen with this new proposal.

I see. Hmm...  🤔 I'll have to dig back into the code. Clearly I have missed understood something. Thanks @benmccann, if it can work that way then it does indeed seem sufficient

@JeanJPNM I tested and the only thing we need is indeed to set inlineDynamicImports: false in the config. I sent a PR to do that by default: https://github.com/sveltejs/kit/pull/2753. In the meantime, you should be able to set it manually in the svelte.config.js to unblock development

With that problem out of the way, we can implement @Rich-Harris's solution without any drawbacks (though I think that option shold be renamed to something like loadPage)

I much prefer ssr to loadPage as a name

Closing in favor of #2804.


How to make this work on a Mac?

I tried to run it but I get this on my MacBook Pro:

Hi,
On OS X, you'll need an X11 environment, have a look at https://www.xquartz.org

Thanks for the prompt feedback!


record media local+ remote

Is it possible to record both remote and local video+audio at a time to node js folder

Just came across the same issue while using MRecordRTC.
the correct form for MRecordRTC is
recorder.videoRecorder.getInternalRecorder().addStreams([stream]);

For RecordRTC
recorder.getInternalRecorder().addStreams([stream]);

For MRecordRTC
recorder.videoRecorder.getInternalRecorder().addStreams([stream]);

Use RecordRTC function MultiStreamRecorder, this will be work.
let options = {
  type: 'audio',   mimeType: 'audio/webm',
};
let arrayOfStreams = [this.localStream.data, this.remoteStream.data];
this.recorder = new RecordRTC.MultiStreamRecorder(arrayOfStreams, options);
this.recorder.record();


Upgrade bpaf to 0.7 to remove some turbofishes

Plus various code improvements, feel free to drop some or all of them.

Do you want to update the code to use derive macro? This means compiling syn, but it's already being compiled...

Thanks! I'll take a look shortly.
Re: derive macro: I'm less concerned about compiling syn as I am about the macro being re-run on every compilation, increasing the incremental compilation times. I'm not very familiar with how derive macros work, so if that's not an issue, then using a derive macro to reduce the amount of code would be great.

https://github.com/rosetta-rs/argparse-rosetta-rs according to this other than initial cost to compile syn and related stuff - there's no difference to incremental compile time.

In that case using the derive API would be great!

Okay. Gimme a day or two.

Pushed, wording might change in some places but cli tests are passing as is so hopefully nothing breaks.
Also added a way for users to make cli parser output more colorful a-la clap3/clap4 if they want to. No extra dependencies by default.

It's a little strange to resolve color as a compilation feature. This is usually runtime configuration - and is disabled by default when writing to something other than a terminal, so that the plain text file doesn't end up littered with terminal escape sequences. See e.g. the behavior of grep --color= where it defaults to auto, but can be explicitly enabled or disabled.
Is there a way to do runtime resolution with bpaf? If not, I'd rather stick to plain/colorless output so that the output dumped to a text file would still be readable.

Runtime detection is present as well and will be used if you enable either colorscheme so redirect to file or running in CI would work as expected. Having it as a compile time helps people to decide if they want any colors at all - I would prefer no colors so won't be enabling this feature, but some people like it.

My apologies for the delay, I got caught up in RL stuff.  I'll try to review and merge this next week.

My apologies for the delay, I got caught up in RL stuff. I'll try to review and merge this next week.

No worries, take your time.

Any thoughts? Also do you want a pull request for cargo-auditable?  pico-args is simple but correctness is not quite there - see https://github.com/RazrFalcon/pico-args/issues/15 for example.

Thank you for the reminder, I'll try to take a look in the next few days now that I've shipped cargo audit 0.17.3.
cargo auditable doesn't need any help generation, and it only capture a subset of all arguments passed. Basically I'm intercepting only some of the arguments passed to rustc, for which pico-args is a great fit.
I am aware of the correctness issue you mentioned, but it only matters for invalid argument sequences, and rustc itself already does an argument validation pass so we don't have to.

I'm going to make the stylistic choice of bright colors, and drop the feature.

There's no downside to leaving the feature in even if you go with the bright colors by default, for example I would prefer not having color at all compared to the bright option. Visibility depends on only on background being dark or bright, but also on a palette.

https://github.com/clap-rs/clap/discussions/2906#discussioncomment-1646705

Also if you really want to drop the color selection - you need to update the docs.

Actually, I'll have to disable color for now because it pulls in atty, which has known UB and appears to be unmaintained: https://github.com/softprops/atty/issues/50

Bummer. I'm not using it directly but through owo-colors. Do you know of
any working/maintained alternative?
On Fri, Nov 4, 2022, 16:17 Shnatsel @.***> wrote:

Actually, I'll have to disable color for now because it pulls in atty,
which has known UB and appears to be unmaintained: softprops/atty#50
https://github.com/softprops/atty/issues/50
—
Reply to this email directly, view it on GitHub
https://github.com/rust-secure-code/cargo-supply-chain/pull/92#issuecomment-1304159608,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAQFI4FVEXKX3BPLYHOTBLWGVVN3ANCNFSM6AAAAAARCOA2OM
.
You are receiving this because you authored the thread.Message ID:
@.***>

No, but I haven't really looked.
You could always just fork it and we can encourage people to switch via the RustSec advisory for example: https://github.com/rustsec/advisory-db/issues/1457

I've shipped v0.3.2 - without color, but it does update to bpaf 0.7.x on crates.io.
I'd be happy to add color later because I think it meaningfully improves the readability of the help text.

I'll see what I can do about atty - I have some other changes planned first. Maybe a week or two.

I did this for now FWIW https://github.com/zkat/supports-color/issues/9

supports-color pull request got merged, hopefully a release soon.


[Communication Chat] Migrate communication-chat tests to the new recorder

As the title says, this PR migrates the Communication chat tests to the new recorder.
Follows the migration guide at https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/test-utils/recorder/MIGRATION.md
Note
The new recorder requires test-proxy to be run before running the tests.
For this, "docker" needs to be installed in your environment as suggested at https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/test-utils/recorder/MIGRATION.md#prerequisites.
Part of https://github.com/Azure/azure-sdk-for-js/issues/19859

/azp run js - communication-chat - tests

/azp run js - communication-chat - tests

/azp run js - aggregate-reports


[JSONRPC] add script_hash beside ScriptView

Also , change arg_auth_key_prefix to. "auth_key_prefix"

all fixed, PTAL

@bors-libra: r+

:pushpin: Commit 34c7e72 has been approved by phoenix-antigravity

:hourglass: Testing commit 34c7e7204179c1f2d070f60ed9a9d67751c62581 with merge ed006cb31fbe20e6c761304e4ca86cae31e693df...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra retry

:hourglass: Testing commit 34c7e7204179c1f2d070f60ed9a9d67751c62581 with merge 6435f1c03d22422f68d9ef9764595ade5586d290...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra retry

:hourglass: Testing commit 34c7e7204179c1f2d070f60ed9a9d67751c62581 with merge d4de5c531a58bd0009b53b9f765c32e9250dd3fd...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: phoenix-antigravity
Pushing d4de5c531a58bd0009b53b9f765c32e9250dd3fd to master...


Missing support for events?

I am currently looking at mostly-dom as an improved snabbdom with better typing and less polymorphism. I am wondering if events are/will be supported in mostly-dom similarly to how snabbdom implements them?

It's possible that the current snabbdom events module could be supported by mostly-dom. Ive originally skipped it because in motorcycle events are handled outside of the view code.
However, I've wanted to make a port, but I definitely want to have the typings be as exhaustive as the current types for properties etc. So for each given element, there should be corresponding event types specific to each element.
If be very willing to accept a PR for this if you're interested in doing the work, otherwise I can not give a timeline on when I'll get it done myself.
P.S. thanks for your issue and your interest in mostly-dom!

@asabil This is released in v3.4.0, try it out and let use know what you think!

Wow, awesome! Thanks. I will try it and report back


Matches containing / causes error

With the config suggested in the README, trying to run InlineFoldToggle on this file gives the following error:

    CSS

Error executing Lua callback: vim/_editor.lua:0: nvim_exec2(): Vim(syntax):E402: Garbage after pattern: /https://developer.mozilla.org/en-US/docs/Web/CSS/ co
nceal cchar=…
stack traceback:
        [C]: in function 'nvim_exec2'
        vim/_editor.lua: in function 'cmd'
        ...re/nvim/lazy/inline-fold.nvim/lua/inline-fold/module.lua:16: in function 'createConcealMatch'
        ...re/nvim/lazy/inline-fold.nvim/lua/inline-fold/module.lua:60: in function 'updateBuffer'
        ...re/nvim/lazy/inline-fold.nvim/lua/inline-fold/module.lua:82: in function 'toggleHide'
        ...cal/share/nvim/lazy/inline-fold.nvim/lua/inline-fold.lua:17: in function <...cal/share/nvim/lazy/inline-fold.nvim/lua/inline-fold.lua:15>

Hi this should be fixed with the latest commit. Special Characters now are getting escaped.


update README.md for recent dev server and API changes

I dropped the videos, they were badly out of date, but I'd like to add back new ones.
I didn't document the CosmosDB API, should we? Not sure how useful it is.
See the rendered README

do you manually add width on these? or does it happen automatically somehow.


Fixed DelaunayTriangulator failing on some inputs.

Use double in DelaunayTriangulator#circumCircle.
closes #7487

Can this be closed as duplicate? https://github.com/libgdx/libgdx/pull/7528


Scores with dot product differ with exact score versus approximate score for native engines

Description
For ANN search with filtering, we take a decision whether to just score all the docs or to run the ANN search. The problem with this approach is that we use Lucene distance function to score exact, while we use our own space type to score the results coming from the libraries ANN methods.
So, for a raw negative dot product score of -1,

ANN implementation will return 2: https://github.com/opensearch-project/k-NN/blob/main/src/main/java/org/opensearch/knn/index/SpaceType.java#L70-L75
Exact will return a score of 1: https://github.com/apache/lucene/blob/main/lucene/core/src/java/org/apache/lucene/index/VectorSimilarityFunction.java#L55

Desired solution
Scoring should be consistent. We should either use our own function to score or update to Lucene's MAX_IP distance function:
https://github.com/apache/lucene/blob/main/lucene/core/src/java/org/apache/lucene/index/VectorSimilarityFunction.java#L87-L96

I also faced this issue, and this issue is mainly happens for inner_product right?

L2 should not have this problem, given we use same translation.

can we move towards using the Lucene based scoring for our exact search too? Given that with newer JDK we will start to use vector APIs also.

The issue isnt related to script scoring. It is that we are using Lucene distance functions for the calculations when we switch to exact with filtering. That being said, this issue will be resolved via switching to MAX_INNER_PRODUCT score

@jmazanec15 can you provide more documentation on what MAX INNER PRODUCT is and how it's set? I couldn't find anything easily just from a straightforward Google search

Can we close this issue now as the feature is pushed and will be released in 2.13


Support popular fuzzers

Investigate the support for using a fuzzer like https://github.com/dvyukov/go-fuzz or https://github.com/google/gofuzz

I had checked both, these repos would help us to generate random input data, but we're already using gofakeit for this.


Proposal I -  - compatibilities extention in platform object

This proposal is born from proposal A to H.
The purpose of the proposal, based on the maintainers feedback, is to address the concern maintaining standalone artifact in OCI.

Definetely the idea of adding a new compatibilities field in the index that is a descriptor is interesting.
As mentioned in the comment, if we go that way we should create a new media type application/vnd.oci.image.compatibility.v1+json and provide its own properties (probably the one we wanted for artifact).
I also like the idea because compatibility would be under the image spec. If container runtimes want to support it they would not have a lot of additional API calls.


cannot upload heavy stemcell in AWS from pipeline

Need option to make an environment's deploy task privileged, such that it can mount the stemcell into the host namespace.

closing because this really comes down to an issue between containerization and the aws-cpi


breakup deployment of validator and helper

Motivation

Solution

Codecov Report
Patch coverage has no change and project coverage change: +7.62 :tada:

Comparison is base (821eaa2) 92.33% compared to head (b75fa6b) 99.95%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1224      +/-   ##
==========================================
+ Coverage   92.33%   99.95%   +7.62%
==========================================
  Files          46       47       +1
  Lines        2412     2415       +3
  Branches      394      354      -40
==========================================
+ Hits         2227     2414     +187
+ Misses        137        1     -136
+ Partials       48        0      -48

Flag
Coverage Δ

foundry
?

production
99.91% <ø> (?)

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 35 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


improvement index

improve main page, add file url support and remove status by direct scan number support. Disallow combined user inputs in the direct frontend. With this I mean making it impossible for the end user to enter both a file link and a file, layout like https://www.virustotal.com/gui/home/upload would work best for this imo
@sylus-squared this all good with you?

At some point soon (Like in the next few days) I am gonna completley redo the pages, ill do that then. If you have any thoughts on how the reports page should look, I will happily take them.

Current concept

@sylus-squared commit it when its stable <3 :D

I can write the credits and stats things btw

Ill create a new branch for the UI rework when its stable

The new index is live


update travis to more recent ghc version

Hmm seems cabal install --only-dependencies --enable-tests --enable-benchmarks --dry -v > installplan.txt no longer works with recent cabal-install


Client Allocation Request for: oydp

Client Allocation Questions
Core Information

Name: oydp
Website / Social Media: opydh, (oideu, oepydh)
Region: Africa
DataCap Requested: 160 GiB
Addresses to be Notarized: 1.4142135623730950488016887
Notary Requested: Sounghwan Park

This user’s identity has been verified through filplus.storage


allow for redirect_to to be specified in the /indieauth/auth POST param instead of constructor

now you have to specify the redirect_to in the constructor of the plugin instead of the form POST...

Fixed in f08d75eb80bed70c76893a0fb236b6e76d2fac1a


Message pane cannot be dragged down easily

Azure Data Studio Version: 1.0.0

Steps to Reproduce:

Run a query like SELECT * FROM sys.databases
When messages pane pops up below results grid, it cannot be dragged down to view more results.

This has been reported in a Azure SQL DW demo. I know they can set a hotkey like Ctrl+R to minimize entire pane, but having the ability to control size of messages pane may allow the user to see more results.
A mitigation is to drag the whole results pane down until messages is flat. This may be a limitation with our current grid implementation, so any feedback appreciated if this is truly a bug or a feature request given grid limitations.

I don't understand the ask here, dragging the results pane down is the same has affect has controlling the size of the message panes?


Chore: Link to datafusion in readme

Description
We're using lots of pieces from datafusion for query execution, and we've taken their sql planner and extended it to support features specific to glaredb.

What This Enables

Impacts

please do, actually, I felt way better about this product knowing it is based on datafusion, so at least you can focus at other areas, no one wants to start a DB from scratch.


complete folder path where artifacts should be uploaded

Description:
SAM package command only takes the bucket path today to upload artifacts. It should also take in the complete bucket/folder/folder/... path.
Why:
In CI/CD world, it is very common to test a build and use the same artifact to promote. If there was a way to control where artifacts went (e.g. bucketName/projectName/typeOfBuild/commitId/ it could still be used to promote to other environments.
I think this should be easily achievable.

@GarimaBathla You may not be aware of the --s3-prefix option in the SAM package command. This will probably provide you with what you need. Oddly enough, the --s3-prefix option does not seem to be included in any of the documentation for SAM CLI.
For more than a year, I've been directing teams with a build/package/deploy process that uses a package command like this:
s3Folder=${appName}/${branch}/${releaseVersion}
aws cloudformation package --template-file microservice.sam.yml --s3-bucket ${ARTIFACTS_BUCKET} --s3-prefix ${s3Folder}/lambda --output-template-file build/output/package.yml
aws s3 cp build/output/package.yml s3://${ARTIFACTS_BUCKET}/${s3Folder}/cfn/package.yml --no-progress

This supports a Build-Once-Deploy-Many approach to handling build artifacts, and sets up S3 to be a well-organized Artifact Repository.

Ah, I believe that the option is not documented in the sam package command, but it is available in the aws cloudformation package command.
Use aws cloudformation package help to see the options available.
sam package is intended to be an alias for aws cloudformation package, so generally I have my build system (e.g. CodeBuild) use the aws cloudformation command so that it doesn't have to install the SAM cli.

Thanks @michaelj-smith this worked. Yes it should have been documented.

Well, I will do the documentation for this use-case.


Add GETs in execution environments (size: small)

Acceptance Criteria

Add GET for

/v1/cloud-services/{id}/compute-resources/{crId}
/v1/compute-resources/{id}/cloud-service/{csId}
/v1/compute-resources/{id}/compute-resource-properties/{resourceID}
/v1/compute-resources/{id}/software-platforms/{spId}
/v1/software-platforms/{id}/cloud-services/{csId}
/v1/software-platforms/{id}/compute-resources/{crId}

Currently, we only need add/remove/change of the whole list


Add apt command to install dependencies

simply added everything needed for compiling on Ubuntu 18.04 to the readme.

Nice, thanks :3


Learning rate scheduler's epoch off by one when resuming from checkpoint

🐛 Bug
Currently lr_scheduler's state is updated after the checkpoint callback, so what is being saved here is last epoch's state.
Note: I think this has the same fix as #1464, but I'm posting it here because (1) I got rekt by this again, (2) in case it's not the same bug, and (3) #1464 is not fixed.
To Reproduce
Steps to reproduce the behavior:
Install using pip install git+https://github.com/PytorchLightning/pytorch-lightning.git@master --upgrade
import os
import torch
from torch.nn import functional as F
from torch.utils.data import DataLoader
from torchvision.datasets import MNIST
import torchvision.transforms as transforms

import pytorch_lightning as pl

class CoolSystem(pl.LightningModule):

    def __init__(self):
        super(CoolSystem, self).__init__()
        # not the best model...
        self.l1 = torch.nn.Linear(28 * 28, 10)

    def forward(self, x):
        return torch.relu(self.l1(x.view(x.size(0), -1)))

    def training_step(self, batch, batch_nb):
        # REQUIRED
        x, y = batch
        y_hat = self.forward(x)
        return {'loss': F.cross_entropy(y_hat, y)}

    def validation_step(self, batch, batch_nb):
        # OPTIONAL
        x, y = batch
        y_hat = self.forward(x)
        return {'val_loss': F.cross_entropy(y_hat, y)}

    def validation_epoch_end(self, outputs):
        # OPTIONAL
        avg_loss = torch.stack([x['val_loss'] for x in outputs]).mean()
        return {'val_loss': avg_loss}

    def configure_optimizers(self):
        # REQUIRED
        # can return multiple optimizers and learning_rate schedulers
        optimizer = torch.optim.Adam(self.parameters(), lr=0.02)
        return [optimizer], [torch.optim.lr_scheduler.MultiStepLR(optimizer, [100], gamma=0.1)]

    def train_dataloader(self):
        # REQUIRED
        return DataLoader(MNIST(os.getcwd(), train=True, download=True, transform=transforms.ToTensor()), batch_size=32)

    def val_dataloader(self):
        # OPTIONAL
        return DataLoader(MNIST(os.getcwd(), train=True, download=True, transform=transforms.ToTensor()), batch_size=32)

from pytorch_lightning import Trainer
from pytorch_lightning.callbacks import ModelCheckpoint, EarlyStopping

model = CoolSystem()

checkpoint_callback = ModelCheckpoint(
    filepath='./model_ckpt/whatever_the_name_is_gonna_be_auto_chosen',
    save_top_k=-1,
    verbose=True,
    monitor='val_loss',
    mode='auto'
)

early_stopping = EarlyStopping(
    monitor='val_loss',
    patience=5,
    verbose=True,
    mode='auto'
)

class PrintingCallback(pl.Callback):
    def on_epoch_start(self, trainer, pl_module):
        print('Scheduler epoch %d' % trainer.lr_schedulers[0]['scheduler'].last_epoch)
        print('Trainer epoch %d' % trainer.current_epoch)
        print('-'*80)

trainer = Trainer(max_nb_epochs=1000, train_percent_check=0.1,
                  checkpoint_callback=checkpoint_callback,
                  early_stop_callback=early_stopping,
                  callbacks=[PrintingCallback()])

trainer.fit(model)

Let the model train until convergence. And then reload a saved model and see how it continues:
trainer = Trainer(max_nb_epochs=1000, train_percent_check=0.1,
                  checkpoint_callback=None,
                  resume_from_checkpoint = 'model_ckpt/_ckpt_epoch_2.ckpt',
                  early_stop_callback=early_stopping,
                  callbacks=[PrintingCallback()])
trainer.fit(model)

The PrintingCallback would print:
Scheduler epoch 2
Trainer epoch 3
--------------------------------------------------------------------------------

Scheduler epoch 3
Trainer epoch 4
--------------------------------------------------------------------------------
...

and so on.
Expected behavior
The PrintingCallback should print:
Scheduler epoch 3
Trainer epoch 3
--------------------------------------------------------------------------------

Scheduler epoch 4
Trainer epoch 4
--------------------------------------------------------------------------------
...

Environment
This is ran on Google colab.
https://colab.research.google.com/drive/1pkCSMaApyjH40jwrdl4aQLVYjnGP3JzD?usp=sharing
Additional context
Related to #1463 and #1464.

@SkafteNicki mind have a look ^^

After looking a bit on this, I think it will automatically be solved by https://github.com/PyTorchLightning/pytorch-lightning/pull/1504, since it is the exact same problem as with early stopping.

Closing this, since the fix is tracked in  #1504.


[CLI] ops echoif not working properly

Hello,
It seems that the tool echoif is not working.
Infact:
❯ $(exit 1); ops -echoif "return code is 0" "return code is 1"
return code is 0

The bats tests seems to "jump over" the problem: in the file tests/echoif.bats the test should assert_line "b" or refute_line "a":

@test "-echoif echoes b with failed previous command" {
    run ops failing
    run ops -echoif "a" "b"
    refute_line "b" # here
}

Ops version:
❯ ops -v
0.1.0-2408111626.dev

As @msciabarra wrote on dev: "that was never used we could probably just get rid of it".


[Task]: Research ways to avoid sentry errors from Echarts widget when an incorrect chart data/configuration is passed to it

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
One of the goals of improving chart experience for the users is to reduce the sentry errors that we see. Although ECharts throws an exception when an incorrect chart data/configuration is passed to it, it still results in a sentry error. We need to research a way that

Avoid Echarts instance crashing
No sentry errors are generated.

Some possible solutions.

Have a validation function that validates that chart data/configuration that the user is passing.
Handle the validations at property pane/validations level. Relevant slack thread here : https://theappsmith.slack.com/archives/CGBPVEJ5C/p1686652610381169

A POC has been done for this and it works on all the requirements. A DP link for this POC is here : https://appsmith-rl2cnfsls-get-appsmith.vercel.app


Need to clarify explanation of last tableau in the example in tableaux/identity.tex

I think that the last paragraph (and possibly the tableau itself; see below) in the example within tableaux/identity.tex needs to be rewritten. That is the paragraph that explains the tableau for proving that equality is transitive.
The reason I find this paragraph confusing is because the terms t_1 and t_2 used in this tableau do not line up with the ones used in the =T inference rule. Namely, in this example, t_2 (resp. t_3) plays the role of t_1 (resp. t_2) in the rule. So when, reading the current text, it is not clear whether the terms in the text refer to those in the rule or those in the tableau. Rewriting the tableau with t' through t''' instead t_1 through t_3 would be one way to solve this issue.

fixed in ec6994c893e6c298997831741b217dea85a3ec1c


Feature request: aws provider

Would really love to see aws support.

This is currently being developed. It will most likely come in the 2.0 release with the driver refactor.

I'm going to close this out.  We don't have an internal use case for this.  If someone in the community wishes to implement it, that is great.  However, having an issue open for this doesn't make sense, since nobody on the molecule is slated to work on it.

hey @retr0h - I totally understand if this is something your team would like to farm out. This is something I'm really interested in adding (mostly for selfish reasons) - can you provide more guidance on where this can be added? Ideally I'd use the vagrant to save some time. I saw someone else was working on this at one point - but I also see your team is in the midst of a big refactor. Is my time better spent trying to target the refactored vagrant driver?

@msheiny your best bet would be adding this functionality to our v2 branch.  The v2 branch uses ansible to manage instances, therefore it would be a simple playbook to spin up an instance in Amazon, which Molecule would converge against.  v2 is a few months out, but makes most sense there.

@msheiny are you working on this ?

@Deepakkothandan @msheiny I'll likely implement it by EOW.  I'm refactoring v2's functional tests ATM, and want to test the ease of driver additions.  AWS seemed like a good candidate.

noopeee @Deepakkothandan / @retr0h -- sorry i got sidetracked in other projects :( but  I did essentially end up using ansible playbooks against ec2 for standup and teardown in the project in question that I needed this on.
Ill hold tight for your changes @retr0h and see if I can append to them. It would be great to switch my existing hobbled together bash scripts + ansible playbooks to utilize molecule instead.

@msheiny @Deepakkothandan just released ec2 support https://github.com/metacloud/molecule/pull/832.

@retr0h Awesome... I will take it up for a spin and update you.


Suggestion for get_midi_host

Hi rppicomidi,
i managed to build an extended version of midi2usb host (with 3 USB connections) and had to make some tweaks.
One was to change the code for get_midi_host to the following:
static midih_interface_t *get_midi_host(uint8_t dev_addr) {   TU_VERIFY(dev_addr >0 && dev_addr <= CFG_TUH_DEVICE_MAX);   //return (_midi_host + dev_addr - 1);   return &(_midi_host[dev_addr - 1]); }
This worked for me. Maybe this solves some reported problems with multiple devices.

Sorry, the code didn't look as i wanted  ...
static midih_interface_t *get_midi_host(uint8_t dev_addr)
{ TU_VERIFY(dev_addr >0 && dev_addr <= CFG_TUH_DEVICE_MAX);
//return (_midi_host + dev_addr - 1);  //seams to work only if dev_addr == 1
return &(_midi_host[dev_addr - 1]);
}

Thank you for this suggestion. I will investigate it.

@moseltronics I have tried the suggested code change because I was concerned there was something strange with the pico-sdk
C compiler. As I expected, whether I use the suggested code change or not, get_midi_host() returns the same value for the same value of dev_addr. This is the expected result.
May I suggest that now that your system is functioning, will you please revert the suggested change and see if it still works?
If you see a different result depending on whether you use your suggested change or the original code, I will need more
information about your build environment to help you figure out what is going on.
Please tell me whether you are using Arduino IDE or the pico-sdk. If the pico-sdk, please tell me the pico-sdk version and what version of gcc you are using to build the code. If the Arduino IDE, please tell me the version of the Arduino IDE and the version
of the Earle Philhower Raspberry Pi Pico board package you are using, and what version of all libraries you are using. Please
also tell me whether you are using a PC, Mac, or Linux computer to build your code. Finally, please tell me what target hardware
you use.

Hi rppicomidi,
your totally right.
I tried everything out and found that both versions work the same way. So sorry for bothering you ...
Changing the callback functions must have made the difference in my code.
Have a nice day ...

@moseltronics OK. It was no bother. If you discover there is a problem after all, please re-open this issue. Thank you for taking the time to file the issue in the first place.


Add a spatial and GIS glossary

Fixes #7910.
Summary of changes:

Add a new page, 'Glossary of Spatial and GIS Terms', designed to help
users get oriented to the rather confusing, TLA-laden GIS space.

To orient the above page "in space" and give it somewhere to live, we
add a new 'Spatial Features' section, with a semi-placeholder page to
be filled in more later, called 'Spatial Features', where we will
provide users with a reference of what, er, spatial features we
support.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3615b5622bfa41af58a298c96930723beb3e0471/
Edited pages:

v20.2/spatial-features.md
v20.2/spatial-glossary.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/cc7f5aec4d13eeb3b87f5630b578b3d72178ef40/
Edited pages:

v20.2/spatial-features.md
v20.2/spatial-glossary.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d0e12113a02fc587e7032bd75f2909cc24bbd2db/
Edited pages:

v20.2/spatial-features.md
v20.2/spatial-glossary.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/6bdd5e5923f14d36bda1b0ef901ee3ed284b1b9a/
Edited pages:

v20.2/spatial-features.md
v20.2/spatial-glossary.md


Correctly render boolean attributes

Problem
We currently guide our users to use true for boolean attributes.
E.g:
Primer::ButtonComponent.new("data-disable-with": true)

Since we use content_tag as our base, when passing true to an attribute, it will render it as the attribute value. In the example above, it will render:
<button data-disable-with="true">

Which is different from the expected:
<button data-disable-with>

Solution?
We could either guide users to use "" instead of true, which should render correctly. Otherwise, we could treat the trues ourselves in BaseComponent.

We could either guide users to use ""

I think a problem with this approach is if someone has some code like Component.new(hidden: user_can_see_component_helper?)

For the particular example you have above, I think that's expected behavior since data-disable-with should be set to a string.

We could either guide users to use ""

I think a problem with this approach is if someone has some code like Component.new(hidden: user_can_see_component_helper?)

I'm actually leaning towards only adding guidance to users. If an user has something like Component.new(data-attr: some_boolean_check?), we can't know if they are depending on having the "true" value or not. Changing how this works could be a massive breaking change.


AvoidAsyncVoid

Thanks very much for the pull request. I did some minor fixes on it (like showing method name instead of "{0}" and making it a warning).


Bug in parsing floats in Payloads that yields the failure of sending 5 Messages

Hello,
The messages NotifyChargingLimitRequest, NotifyMonitoringReportRequest, ReportChargingProfilesRequest, RequestStartTransactionRequest and SetChargingProfileRequest fail to be validated and hence to be sent. The bug happen when in all these messages payloads is present a float. Specifcally :

NotifyChargingLimitRequest is when you add the optional filed charging_schedule, that requires ChargingScheduleType, that requires ChargingSchedulePeriodType, that requires the field limit as a float.

NotifyMonitoringReportRequest is when you add the optional filed monitor, that requires MonitoringDataType, that requires VariableMonitoringType, that requires the field value as a float.

ReportChargingProfilesRequest is always present because of the field charging_profile that requires ChargingProfileType, that requires ChargingScheduleType, that requires ChargingSchedulePeriodType, that requires the field limit as a float.

RequestStartTransactionRequest is when you add the optional field charging_profile that requires ChargingProfileType, that requires ChargingScheduleType, that requires ChargingSchedulePeriodType, that requires the field limit as a float.

SetChargingProfileRequest is always present because of the field charging_profile that requires ChargingProfileType, that requires ChargingScheduleType, that requires ChargingSchedulePeriodType, that requires the field limit as a float.

Aftre reading the comment inside your code to my understanding the problem is due to the parser used to parse the floats in the payloads, that a default is float(). Indeed, you left a comment specifying that for some schemas should be used decimal.Decimal. However, as an user of your library I can only access your code up to the call method of your ChargePoint class and there is no possibility for me to sepcify the parser inside call - validate_payload - get_validator. Do you think that adding the possibility to specify the parse_float at the call method will fix the issue or is there another problem with the parsing of the floats?

Thanks for your elaborate report.
I'm curious why validation fails, though. The schemas for OCPP 1.6 limit the decimal points of a few number types to 1.  It does so using the JSON Schema keyword multipleOf. See for example the subschema for  ChargingSchedulePeriod.limit.
You noticed correctly that this library includes a custom encoder to serialize these numbers. See for example here and here.
The schemas of OCPP 2.0.1 don't use the multipleOf JSON keyword. Therefore, I don't understand how you run into validation issues. Can you provide a code example shows the validation issue?

To confirm the types highlighted in the issue are floats in the library - changing to question


Support type hinting

This pr does include the pr #374, because the pr was created with the master branch. So I would like that the "define-constants" pr will be merged first.

When fine, I'll create tests. But I'm unsure wether the code is okay like this.

@felixfbecker is this still working, would be great to have this merged?
should solve issue #350 right?

This is based on an old version of the langserver that used a different parser, see the merge conflicts. It's also missing some tests.

Okay, ehm, I will watch out when I got more time and then refile the pull request.


Dropdown cover by Bootstrap carousel, third level navigation not opening on a table/mobile

Hi,
When viewing on a screen biger than the 800px break point.The dropdown menu goes under a bootstrap carousel. The same happens with a video, the video effect can be seen here: http://jasonweaver.name/lab/flexiblenavigation/
when in chrome and the block above the video content has been deleted, as in attached example.
This happens on a desktop chrome, android and IOS. How do I keep the menu above a carousel? I have tried using z-index, but it does make any difference.
Many thanks.
Regards,
Kev

I forgot the attachment before.

Answer: add position: relative; to .flexnav {**position: relative;**z-index: 10;}
Sorry for the basic question before. I had failed to notice I had forgotten to add position: relative; as well to  z-index: 10; to .flexnav, so I answer it myself.
Kev


Add domain : vn - edu - nttu

nttu.edu.vn

@khanhnguyen234 You might miss my previous comment. Please react.

@khanhnguyen234 You might miss my previous comment. Please react.

Website: https://ntt.edu.vn/
Address: 300A – Nguyễn Tất Thành, Phường 13, Quận 4, TP. Hồ Chí Minh, Việt Nam
IT url: http://cntt.ntt.edu.vn/
Recognizes the domain: can see email at header on website (ex<EMAIL_ADDRESS>
@philipto Please help me check

@khanhnguyen234 Thank you for the details! You are quite right: this university has a domain ntt.edu.vn. However you requested to add a domain nttu.edu.vn (please notice extra "u" after "ntt").
If you need to add a domain ntt.edu.vn, I can do it immediately. Please confirm. Thank you!

Sorry I don't know why student e-mail in the format<EMAIL_ADDRESS>(http://phongdaotao2.ntt.edu.vn/NewsDetail.aspx?NewsID=1988). How can I do to get support?

@khanhnguyen234 Thank you for the clarification. Pull request merged. The page http://phongdaotao2.ntt.edu.vn/NewsDetail.aspx?NewsID=1988 was exactly what I needed. Thank you!


How to get swagger-ui is set to home page

if my website host is abc.com,then how can i see swagger by http://abc.com
now the url always need "/index" ,eg. abc.com/index. @ #

I use a redirect rule in the config file. Refer to the blog article I posted here - http://www.michaeltaylorp3.net/creating-a-rest-api-project-template/
Jump to the Setting a Default Document section.

@eightHundreds there are several ways to do it however.
To all who will come here from Google, go look here:
http://stackoverflow.com/questions/37724666/how-to-redirect-from-root-url-to-swagger-ui-index
and here:
http://stackoverflow.com/questions/30028736/how-to-use-swagger-as-welcome-page-of-iappbuilder-in-webapi
@domaindrivendev please include this topic in README.md because of so much frustration and common use-case.

I'm going to close this as there's several approaches described above. Adding a simple redirect to a web application is a pretty standard practice and is extremely well document. I don't think it's necessary to add specific documentation to Swashbuckle. But, if anyone here feels strongly about adding to the docs, feel free to submit a PR.

this worked for me:
app.Run(async context => {
    context.Response.Redirect("swagger/ui/index");
});


Fix: the dirty verification is system language dependent

My system runs on Brazilian Portuguese. So, git messages are not in English. This fix makes the dirty verification not language dependent.

Hi, @hugomaiavieira, I was 2 hours ahead ;)

@cybernetlab that was a good one! :smile:


Variant accordion_header is missing from Typography

Describe the bug

The initial fault was found in a Dialog, and seems to be reproduced anywhere as far as I can tell.
I did not try to render this inside an actual EDS Accordion, but I assume this is not related.
Steps to reproduce the bug
Use Typography component anywhere and send variant="accordion_header" as prop.
Expected behavior
Should output an accordion_header formatted text.
Specifications

Version: 0.18.0
Browser: Vivaldi 5.1 (Chromium 98)
OS: Linux

You need to add group="ui" and then it will work @ErlendAHall
I think our documentation might need an update to explain this!

Can confirm it works for me now :)


NonEmptyMap

Would nice to have convenience functions for this.

I think letting a separate library provide this is probably a good move, at least for now (especially now that one exists). Shall we close this?


I cannot add input devices.

I installed Interception Сore according to the instructions, but it doesn't work. I don't have a list of input devices displayed. Maybe I'm doing something wrong? Please help.
P.S. Sorry for the mistakes, my English is not good.

did you download the provider separately then find the exe file, and run an admin elevated command prompt to install it?

Reference https://github.com/Snoothy/UCR/wiki/Core-Providers, choose the input/output devices you would like, and click the links to find instructions on how to set them up.

I have the same issue, I had UCR working fine showing my input devices, after setup I noticed UCR wasn't blocking my keyboard inputs, so after some research I installed interception through the command line, and now after a UCR re-unzip all my input devices are gone.
I have a feeling interception didn't install correctly because after typing install-interception.exe /install I got no response (cmd went back to my directory) which usually means it worked, but the wiki says it should output "Interception successfully installed"

Not sure what fixed it but after uninstalling everything reinstalling rebooting I see my inputs now. I still can't get Interception to block my keyboard inputs, despite settings value set to "true"

I also am not getting input with interception

redownloading ucr worked

Missing input devices are usually due to blocked files or missing setup of specific providers. Try to run the unblocker in the UCR folder and follow the installation guide: https://github.com/Snoothy/UCR/wiki/Installation-and-Setup


mix.copy(); tries to minify JavaScript (includes reduced test case)

Laravel Mix Version: 2.1.11 (npm list --depth=0)
Node Version (node -v): 8.1.3
NPM Version (npm -v): 5.0.3
OS: macOS 10.13.4

Description:
When using mix.copy(); to copy a JavaScript file, Mix tries to minify the file if NODE_ENV=production. If it hits ES2015 syntax, Mix throws an error and recommends using mix.babel().
Steps To Reproduce:

Follow instructions for standalone install of Mix verbatim, including making an empty directory and copying the mix file and npm scripts.

Modify the mix file such that the only mix directive is:

mix.copy('src/app.js', 'dist/app.js');

Create a file, src/app.js, and put the following line of code in it:

var test = () => console.log('hello');

npm run production

@devcircus Correct me if I am wrong, but isn't mix.copy() intended to simply move files as is?

Specifically yes. At least that's how I've always understood it.
I was thinking in the context of copying a file that is then used in the build.


change types: struct Transaction.Timestamp string to int64

fixed test
--- FAIL: TestRetrieveTransactionInformation (0.05s)
    transactions_test.go:15:
                Error Trace:    transactions_test.go:15
                Error:          Expected nil, but got: &json.UnmarshalTypeError{Value:"number", Type:(*reflect.rtype)(0x6f2ec0), Offset:1826, Struct:"Transaction", Field:"timestamp"}
                Test:           TestRetrieveTransactionInformation

Breaking change:
raw-transaction response document:
https://docs-blockchain.line.biz/api-guide/Callback-Response?id=raw-transaction
timestamp | String | Confirmation time of the block immediately previous to the block including the given transaction with the format of “YYYY-MM-DDThh:mm:ssZ.” Note that it’s NOT confirmation time of the block including the given transaction.

The documentation states that this response will be returned as a string in a particular format, but it seems that it is actually returned as UNIXTIME (ms).

Thank you!


Proofread Deployment AWS

Proofread

Thanks for making the changes, Maria. Please verify how the doc looks when it builds to master in ~20 minutes.


logging: Fix missing logging

Previously we started using logging before it had been initialized.
Which resulted in leapp stopping to log for some logger names the debug
output. We did not know why this happened. It turns out that fileConfig
from the logging library has a parameter disable_existing_loggers which
is by default set to True and will set all loggers that have existed
before the call to fileConfig to disabled. Which in turn will make them
stop logging of course.
This patch will change this behaviour and set disable_existing_loggers
to False in order to have existing loggers be still enabled.
Signed-off-by: Vinzenz Feenstra<EMAIL_ADDRESS>

/rerun


Device emulator-5554 is not authorized, and I am not able to get any authorization dialog in my emulator

When I run flutter doctor in cmd I get a warning saying,
[√] Connected device (3 available)
       ! Device emulator-5554 is not authorized.
                  You might need to check your device for an authorization dialog.

Later when I run flutter devices I get the following,
[1] connected devices:
  Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22000.708]
  Chrome (web)      • chrome  • web-javascript • Google Chrome 102.0.5005.63
  Edge (web)        • edge    • web-javascript • Microsoft Edge 102.0.1245.30

 • Device emulator-5554 is not authorized.
 You might need to check your device for an authorization dialog.

I am not getting any authorization dialog in my emulator, my emulator is in developer mode, the USB debugging is ON and default
USB configuration is set to File Transfer

My emulator is not being detected and I am not able to run my flutter app in the emulator.

Hello @CM-Sharan. Have you tried re-creating the emulator by deleting it and creating it again or testing with another emulator?

I have tried re-creating the emulator but the same issue keeps coming up.

Can you check if this helps you?

Thank you @exaby73


add client id

Thank you for contributing to naz.
Every contribution to naz is important.
Contributor offers to license certain software (a “Contribution” or multiple
“Contributions”) to naz, and naz agrees to accept said Contributions,
under the terms of the MIT License.
Contributor understands and agrees that naz shall have the irrevocable and perpetual right to make
and distribute copies of any Contribution, as well as to create and distribute collective works and
derivative works of any Contribution, under the MIT License.
Now,
What(What have you changed?)
Why(Why did you change it?)

Codecov Report

Merging #45 into master will increase coverage by 0.17%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
+ Coverage   84.26%   84.44%   +0.17%
==========================================
  Files           9        9
  Lines         699      707       +8
==========================================
+ Hits          589      597       +8
  Misses        110      110

Impacted Files
Coverage Δ

naz/__version__.py
100% <ø> (ø)
:arrow_up:

naz/client.py
84.13% <100%> (+0.21%)
:arrow_up:

cli/cli.py
69.67% <100%> (+0.76%)
:arrow_up:

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 b001a3c...9f64951. Read the comment docs.


Support for JaCoCo on Java 9

For more information see #1006.

Relevant CI job.

The other thing I forgot to mention -- we should add something to the release notes about a default version change.

@big-guy Yeah, I was planning to add something to the release notes after merging.

@big-guy I addressed your comments for this PR. Can you please have another look?