Projects, notebook folders, packages, etc to highlight at OSM workshop?

Just linking in a few people on top of my head for now -- anyone please feel free to jump in, link more people in, provide comments, ask questions, etc
@briochemc  @navidcy  @ali-ramadan @glwagner @milankl @Alexander-Barth @jmbeckers @ctroupin @juliaclimate @juliageo
Please also take a look at the tentative list of 2' contributions in the repo's main README.md if you get a chance

Anyone around at OSM 20 tomorrow and available to come to the workshop? Please let me know via this thread or some other way if you will be able to help with this. Thanks

Le 2020-02-17 à 4:35 p.m., Gael Forget a écrit :

Anyone around at OSM 20 tomorrow and available to come to the
workshop? Please let me know via this thread or some other way if you
will be able to help with this. Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gaelforget/JuliaOceanSciencesMeeting2020/issues/1?email_source=notifications&email_token=AEWMLFQF327TW65HPJZJI3LRDKVENA5CNFSM4KU4QR4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL62OWQ#issuecomment-587048794,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEWMLFR7NSJPN2ZWDL6DZQLRDKVENANCNFSM4KU4QR4A.

Hi, Would like to join but we are all in Belgium for the moment
--
Prof. Jean-Marie Beckers

@meggart I am linking you here as I noted that this data help desk booth and that one where EarthCube is listed. Do you know if someone there will be able to e.g. showcase ESDL.jl ?
@zhenwu0728 and @suyashbire1 I just realized I forgot to link you in the above (sorry for the oversight ...)

Hi, Would like to join but we are all in Belgium for the moment

Thanks @jmbeckers
Is there anything specific you would like highlighted about GHER's packages etc? A couple plots or a picture of the group that I could link to in addition to your GitHub org maybe?

A few side notes:

I just emailed OSM to ask about the possibility to have a telecon setup (seems unlikely but who knows...)
I need to present a colleague's talk this PM so I probably won't do too much on this repo between now and tonight but will keep an eye out for e.g. PRs or issues if any

I'm unfortunately not in San Diego. If there's any way to participate virtually, let me know!!

I'll join the workshop and willing to help

It seems that we will be able to telecon after all.
@Ali-Ramadan @milankl and @jmbeckers would you be able to attend and say a few words about your respective packages at 1pm PST?
I will post detail / send link after I set up tomorrow AM.

Yes, should be possible (to be sure, tomorrow for you is Tuesday 17th ?)
though the connection might be slow (l will be at home).
Thanks in advance
Le 2020-02-18 à 6:49 a.m., Gael Forget a écrit :

It seems that we will be able to telecon after all.
@Ali-Ramadan https://github.com/Ali-Ramadan @milankl
https://github.com/milankl and @jmbeckers
https://github.com/jmbeckers would you be able to attend and say a
few words about your respective packages at 1pm PST?
I will post detail / send link after I set up tomorrow AM.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gaelforget/JuliaOceanSciencesMeeting2020/issues/1?email_source=notifications&email_token=AEWMLFW2N6XF6F56TFFALQLRDNZF5A5CNFSM4KU4QR4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMAVLIA#issuecomment-587290016,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEWMLFXINR5OVYFFDGTQLZLRDNZF5ANCNFSM4KU4QR4A.

--
Prof. Jean-Marie Beckers

No, we are not present there. That is a different project with a similar name ....

@Ali-Ramadan @milankl and @jmbeckers would you be able to attend and say a few words about your respective packages at 1pm PST?

Yes, from my side. Happy to prepare 2 slides, how do you want me to call in?

I will try to join a give a short presentation about some of our packages. (NCDatasets.jl, DIVAnd.jl, PhysOcean.jl) but I am not 100% sure that I can make it.

Plan is to have bluejeans for video & sound output + gotomeeting & mic so you can hear from audience. Meeting with the specialist to set it up in a bit.
Will post updates to this thread asap (by 11am PST most likely)

No, we are not present there. That is a different project with a similar name ....

@meggart would you be willing to pitch e.g. Zarr & esdl in a couple minutes maybe?

@Ali-Ramadan or @glwagner are you available to pitch e.g. Oceanigans & Clima ?

@navidcy or @glwagner are you available to pitch e.g. fourierflows ?

@briochemc @zhenwu0728 & @navidcy
could you maybe meet me in the room at say 12pm15?

@gaelforget, yes I'll meet you there at 12.15
Yes, either me or @glwagner can talk a bit for FourierFlows.jl / GeophysicalFlows.jl

@ali-ramadhan isn't here! I can give a short intro / pitch to Oceananigans.jl. I can also show the Clima repository.

Yes to confirm : this is happening today the 17th at 12pm45 PST
Slides: 1 or 2 would be great indeed -- please email them to me by 12pm30 if possible (just in case tech fails us ...)

@gaelforget  yes, I'll meet you there at 12:15

@balinus would you be available to pitch climatools in a 2' maybe today ?
(see above thread & repo for detail; sorry for late ping ...)

Currently in a meeting. (Where would be the link for the teleconference?)

Currently in a meeting. (Where would be the link for the teleconference?)

Should be https://bluejeans.com/675644738/2261
Plan is to start it up at 12pm15 once I am in the room

These will be my slides:
https://alexander-barth.github.io/OceanSciencesMeeting2020/#1

I am connected with my web-browser, but I don't see anybody ("You are the only one here")

Currently in a meeting. (Where would be the link for the teleconference?)

Should be https://bluejeans.com/675644738/2261
Plan is to start it up at 12pm15 once I am in the room

I can't install applications on my work laptop. Hope it's doing well!
Cheers!

It was a very nice overview of the julia climate/ocean/... ecosystem yesterday. Thanks a lot Gael for organizing this! I would be curious to know how many people where in the audience. At least it sounded more than just 3. :-)

At least it sounded more than just 3. :-)

Full house :smile:  https://twitter.com/gong_donglai/status/1229871926484467712

Thank you all so much for participating and making this work out so beautifully on such short notice. I feel that this was a resounding success and outstanding first step. Will follow up soon ...
Ps. A special thanks to @zhenwu0728 who saved the day by providing the crucial ethernet dongle just in time, and to @milankl @Alexander-Barth @briochemc & @glwagner for showcasing all of this great work

Dear all
I finally got around to reviewing the recording from the OSM event. As I did not notice anything that would requires being cut, I pushed to YouTube @ https://youtu.be/xOeB-uwoMI0
Might start advertising it early next week -- if you get a chance to watch it
I can probably cut some parts e.g. @Alexander-Barth @milankl @briochemc @glwagner were uncomfortable with this kind of advertising (please do asap or give this a +1 if you get a chance)
ps. Sorry we did not capture the audience's sound. I actually paid for it but the Moriots decided to show up with just a phone plug ... That's also why remote folks did not get to hear them. At some point I may try to add subtext to fill the blanks

Very fine with that!

I am fine with that too. Thanks for making the video available.


Disable the wiki tab?

It's currently not being used. Can we uncheck it from the repo settings to clean up the tab bar?

Done.

Thanks!


Fixed bugs parsing Categories in NUnit parser

Categories not retrieved in NUnit parser

Changed parser to look for a "Categories" element instead of a property named "Category" (to match NUnit 2.6.4)
Modified code to capture categories at the suite level for each test.  For example, a category of "SmokeTests" at the class level would not display at a category for the tests it contained
Modified code to capture categories for parameterized tests.  Parameterized tests are grouped under a test-suite node with type "ParameterizedTest" (example below), so those categories were not captured

  <test-suite type="ParameterizedTest" name="MyTestMethod" executed="True" result="Success" success="True" time="0.205" asserts="0">
 <categories>
   <category name="SmokeTest" />
 </categories>
 <results>
   <test-case name="MyTests.MyTestMethod(param1)" executed="True" result="Success" success="True" time="0.096" asserts="2" />
   <test-case name="MyTests.MyTestMethod(param2)" executed="True" result="Success" success="True" time="0.107" asserts="2" />
 </results>
  </test-suite>

Fixed CSS issue in File.cs template.  Large blank space was present between the suite list and suite detail (image below)

Changed .suite-list class to use percentage width instead of fixed width
Changed .suite-details to use percentage for left position instead of fixed number of pixels

I tested the styles, and this is what happens:

It won't be possible to do:
.suite-details {
    left: 21%;
 }

because the sidebar itself takes 260px of space.  Which is why the sidebar, suite-list and details are fixed width..

Thank you, Anshoo.  I'll test in a bit to make sure it was the same on my end.    I'll update accordingly or just remove the CSS changes altogether.  I should have submitted those in a separate request anyway.
Thanks again!

That's okay, the NUnit part looks good, so that will be merged.  You can send in 2 different pull-requests if you want, or I will manually merge the NUnit one.

And regarding the styles, if you think there is a better way to size the containers, please share - I am also struggling with a good ratio to display this content across different screens.  Maybe just make the container resizable?

Either way is fine with  me.  I certainly don't mind splitting them into two, so I can just go ahead and do that.  I'll take another look at the containers to see what I can come up with.  CSS is not my strong point, but if I have any ideas I'll let you know.


Can't use live PDF url

I am trying to use live url of PDF. it is showing file not found

Currently it only support local file.


add license

it's a very interesting project!
Would you consider adding a license to this repository to specify under which terms this code can be used?

yeah sure sorry i just got to you now :)

sure, not problem. can you add a license please?

Done buddy :)

Would be cool to see what you use it in.  I know it , but I think I could do it

oh dude thats awesome! good luck!


Size based rule is reversing result

I have a single node rule with default size 1x. I have refreshed the range and set it to a single integer property. I have added the property,"power" to the captions on the nodes.  The large numbers are appearing small and low values large. This is counter to the rule.
The Bloom version is 2.1.0

Andy

I have the same issue...also the color range rules don't work properly anymore.

Thanks for reporting, fixed with Bloom version 2.1.1

I will be closing this issue since the bug has been fixed. If you have any issues with Bloom, please feel free to raise a new issue here or on Canny https://neo4j-aura.canny.io/explore


Audio stopped playing after 17.5.1 IOS update

Describe the Bug
I have an audio reproduction app and the tracks suddently stoped playing on Ios after the last 17.5.1 update.
There are no immediate logs of error concerning the reproduction, but a long time after hitting the play button tho,
I get this log on the console: tcp_input [C69.1.1:3] flags=[R] seq=2659539961, ack=0, win=0 state=LAST_ACK rcv_nxt=2659539961, snd_una=2641334348
Is anyone experiencing anything like this? Android works fine.
Steps To Reproduce

Open the app
Reproduce any kind of audio

Environment Info:
"react-native-track-player": "^4.1.1",
Error occurs both on the real device and simulator, but sometimes the Iphone 15 Pro Max simulator works fine.
IOS 17.5.1

This is a real blocker for our project release. Bumping this up.

My workplace is experiencing similar issues with our audio app.

Audio stops after roughly an hour.
Only seems to affect iOS.
Doesn't seem to affect a colleague who's on iOS 17.4.1.

I am also experiencing this issue on iPhone SE iOS v17.5.1. Live stream audio automatically stops after roughly an hour. Doesn't seem to affect android or iOS versions less than 17.5.1.

Have any of you made sure this issue is specific to react-native-track-player?

I haven’t been able to confirm, I’m still in the process of narrowing it down. But in that process we saw this issue and considering my colleague is on iOS 17.4.1 and is unaffected by the issue we’re experiencing I thought I’d add weight to this theory.
On 28 Jun 2024, at 5:21 PM, Jonathan Puckey @.***> wrote:

Have any of you made sure this issue is specific to react-native-track-player?
—
Reply to this email directly, view it on GitHubhttps://github.com/doublesymmetry/react-native-track-player/issues/2334#issuecomment-2196299765, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJOJKOUMLKBRJF7V6SZFDILZJUFG7AVCNFSM6AAAAABJSAH66KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJWGI4TSNZWGU.
You are receiving this because you commented.Message ID: @.***>

Have any of you made sure this issue is specific to react-native-track-player?

Trust, me. I've done several hours of debbuging and recently I was able to actualy get an error message;

// {"error": {"code": "ios_track_unplayable", "message": "The track could not be played"}, "state": "error"}

Now, what i've noticed is that although it does works sometimes, the error always happens when the State of the player gets stuck on {"state": "loading"} or {"state": "buffering"} never being {"state": "ready"} unlikely what happens when running the android version of our app.

@Levi-Teixeira  Are you playing a HLS livestream ending in .m3u8 also?

@gmach No. Good old .mp3 tracks.

can u monitor network activity at when error happened? i mean if the audio stops ~1hr it sounds like a background problem? does ios 17.5.1 introduce some kind of background limitation or resource optimization patch in their logs?
or if a track consistently stops/errors can u post the link?
disclaimer tho i dont use mac/ios at all.


[FEATURE] Migration from AGS to Astal

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
This is a super-issue that's meant to include any and all To-Dos that entail migration to Aylur's Astal.
Additional context
Add any other context or screenshots about the feature request here.
https://github.com/Aylur/astal
Also see Aylur/ags#618. This means we'll have to rewrite the whole thing with Astal. There's a PKGBUILD by the AUR package maintainer themselves that will let us stick with v1 until we work on this.

@dianaw353, you HAVE TO see this! AGS just got updated to v2 and the current config we have, which is definitely incompatible with v2, WILL break your setup! Uninstall aylurs-gtk-shell-git and rebuild with the PKGBUILD linked in above comment RIGHT NOW!
I'll also open a separate PR to merge quickly and make a maintenance release out of it (<IP_ADDRESS>, anyone?).

There's a migration guide for a jumpstart as of now.
https://aylur.github.io/ags/guide/migrate.html

Tracked in PR: #61


[bug] wrong version

Describe the bug
tauri doesn't read the correct version which is in package.json

Reproduction

tauri.conf.json

{
  "package": {
    "version": "../package.json"
  }
}

package.json

{
  "version": "0.1.0"
}

yarn tauri build

Expected behavior
No response
Platform and versions
Environment
› OS: Windows 10.0.19044 X64
› Webview2: 104.0.1293.70
› MSVC:
- Visual Studio Community 2019
› Node.js: 14.16.0
› npm: 8.18.0
› pnpm: 6.25.0-3
› yarn: 1.22.19
› rustup: 1.25.1
› rustc: 1.63.0
› cargo: 1.63.0
› Rust toolchain: stable-x86_64-pc-windows-msvc
Packages
› @tauri-apps/cli [NPM]: 1.0.5
› @tauri-apps/api [NPM]: 1.0.2
› tauri [RUST]: 1.0.5,
› tauri-build [RUST]: 1.0.4,
› tao [RUST]: 0.12.2,
› wry [RUST]: 0.19.0,
App
› bundler: Webpack
App directory structure
├─ .git
├─ .vscode
├─ build
├─ dist
├─ dist-build
├─ node_modules
├─ public
├─ src
└─ src-tauri
Stack trace
No response
Additional context
No response

That version is from src-tauri/cargo.toml version field.

Yep it is from cargo.toml and it's just cargo's build log and we can't do anything about that. As long as the app itself (the bundle file names and what the getVersion api returns) is correct everything works as expected.

i see.


FEATURE - Link to Maintainer

Describe the feature you want the app to have that it currently doesn't

Create a new row in the SettingsView in the 1st section, right after the "GitHub Repo" and before the "Request a New Feature," link to Mikaela's GitHub Profile
Label the row: 🦄 Mikaela Caron - Maintainer
Link to: https://github.com/mikaelacaron

Describe alternatives you've considered

N/A

Additional context

This allows anyone to be able to contact Mikaela directly about the project if needed

Hi @mikaelacaron, can I work on this issue?

Hi @mikaelacaron, should the unicorn be part of the name or be an icon similar to the bug and GitHub icons?

@johnolwamba it should be part of the name, just the emoji


Error spam when trying to find the other end of ( or ), unsure if it affects [] or {}, needs more testing

Basicly this started happening out of nowhere, i was playing on a server and this weird error started spamming in "problems" tab
When trying to locate the other end of ( symbol, ")" it can't find it, it doesn't even mark the one i click in front of and spams an error message which causes lots of fps lag
Basicly to get get this error message i just clicked in front of ( symbol that does not have the other end
Clicking ( should mark it's other end if it exists, ")"

In text:
[github_wire] addons/github_wire/lua/wire/client/text_editor/texteditor.lua:194: bad argument #1 to 'ipairs' (table expected, got boolean)
1. ipairs - [C]:-1
2. GetCharIndexByPos - addons/github_wire/lua/wire/client/text_editor/texteditor.lua:194
3. CursorToCaret - addons/github_wire/lua/wire/client/text_editor/texteditor.lua:266
4. unknown - addons/github_wire/lua/wire/client/text_editor/texteditor.lua:915

Reproduced the lag, but I don't see the errors.

This can probably be closed since #2357 "fixed" it.


Releasing new versions of the spec

So far we have been updating the spec at https://github.com/sgkit-dev/vcf-zarr-spec/blob/main/vcf_zarr_spec.md and bumping the version number as we go. However, this won't work if we want to make a series of changes and then release those changes in one go.
The simplest way to do this would be to make the changes in a branch then merge into main when we want to release a new version.
Thoughts?

That SGTM. Keeping things lightweight is a good goal here.


[python] Provide pyproject.toml that supersedes setup.py

🤔 What's changed?

Provide pyproject.toml file that supersedes setup.py file
Use setuptools-scm to derive version-info from git-tags (in the future)
Remove outdated version info from
cucumber_tag_expressions/__init__.py, pytest.ini
README.rst: Update badges to be displayed in one line on pypi.org.

CLEANUP:

REMOVE: setup.py, setup.cfg
REMOVE: .bumversion.cfg (superseded-by: setuptools-scm mechanism)

⚡ What's your motivation?

development: Improvements to make the project better for the future

🏷 What kind of change is this?

:bug: Bug fix (non-breaking change which fixes a defect)

📋 Checklist:

[x] I agree to respect and uphold the Cucumber Community Code of Conduct
[ ] I've changed the behaviour of the code

[ ] I have added/updated tests to cover my changes.

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[x] Users should know about my change

[x] I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

Replace the core changes by:

Provide pyproject.toml that supersedes setup.py
Use setuptools-scm to derive version info from git-tag(s) (in the future)
Remove bumpversion support (superseded-by: setuptools-scm mechanism)

OTHERWISE:

Other cleanup changes are left out here.


Remove NNPACK integration

Description
NNPACK may be added back if someone is interested to implement the https://github.com/apache/incubator-mxnet/issues/9719 improvements (in particular switch to cmake) and/or if NNPACK has other advantages compared to oneDNN. Now oneDNN also supports ARM and I'd expect that it performs better than NNPACK given the continued investment of Intel. Note that oneDNN is also AL2 licensed.

@mxnet-bot run ci [centos-cpu]

@mxnet-bot run ci [centos-cpu]


Cannot download cards in list because too many checklists

Stemming from #74, this issue is to track the short-term solution.

See branch bug/issue-77

Please see v1.17.1 for the fix here.

Apparently this is still an issue.

I have completed coding for the selectable field downloads (#74).  That should resolve this issue completely.  I will perform some verification before publishing.

Please see Manatee.Trello v1.18.0


Use rails path helpers in specs instead of hard coding them

What problem does this pull request solve?
I spotted a few places where we were not using rails path helpers. I've checked a using find got  , post , put  & delete
Trello card:

Things to consider when reviewing

Ensure that you consider the wider context.
Does it work when run on your machine?
Is it clear what the code is doing?
Do the commit messages explain why the changes were made?
Are there all the unit tests needed?
Has all relevant documentation been updated?

Do we want to change https://github.com/alphagov/forms-api/blob/main/spec/requests/heartbeat_controller_spec.rb#L6 and https://github.com/alphagov/forms-api/blob/main/spec/requests/heartbeat_controller_spec.rb#L17 as well?


Add Game.backgroundDecoration property

Based on discussion in #1448, we would like to have the backgroundColor property of a Game to be dynamically changeable. One problem with that, however, is that right now backgroundColor is a method, not a property, and I don't think there is a way to convert a method into a property without making a breaking change.
So, instead of changing backgroundColor, I suggest to add a coexisting property backgroundDecoration, while deprecating backgroundColor method. The backgroundDecoration property will work like this:

by default it will return null;
if it returns an object, that object will be used as the decoration: property of the widget;
if it returns null, then we will call backgroundColor() and construct a decoration box out of that color;
the backgroundColor() method will be deprecated.

Note that backgroundDecoration allows more complicated backgrounds than simple color. For example, you can implement gradient colors through it.

How can it be dynamically changeable? Since both color and decoration are set on the widget and we can't refresh the widget?
I think if you'd want to change it mid-game it is better that the user does it at a widget level with state management than from inside of the game.

You can refresh the widget, since it's stateful.

I don't think we want to do that though, the state of the widget should lay on the Flutter side, not inside of the game.

The state of the widget belongs to the GameWidget class, and Game has a means of communicating with its widget. There is nothing new here, we're already doing that.

The game is a final property inside the GameWidget, which means it is impossible to "restart" it from within the GameWidget. Not that we wanted to.

Weird idea, but can we not just do a canvas.drawRect(Vector2.zero() & size, Paint()..color = backgroundColor()) (with some caching etc) at the start of our render pipeline? I mean even Flutter eventually uses some form of canvas drawing to draw the background color of a widget, why should we let a widget do that for us if we can provide it "easily" ourselves?

The state of the widget belongs to the GameWidget class, and Game has a means of communicating with its widget. There is nothing new here, we're already doing that.

You're right, saw that we are handling the mouseCursor in the same way as this would be done.
Then I think this is a better idea (if we'd want this feature) than to draw a rectangle on the canvas manually.

I mean even Flutter eventually uses some form of canvas drawing to draw the background color of a widget, why should we let a widget do that for us if we can provide it "easily" ourselves?

I think Flutter would cache the rendered background so that it wouldn't need to be re-drawn on every tick.


Updated Farm Dates and Index Token Emission

Pull Request Template
Type of Change
Select a category that relates to the content of your pull request (choose one).

[x] Bug fix
[ ] New feature
[ ] Documentation
[ ] Code Refactoring
[ ] Update of code styling

Does this request include a breaking change?
Is there any potential for this change to crash Index UI or make it unusable?

[ ] Yes
[x] No

Description
Provide a brief summary of the changes you made and their purpose as they relate to the Index UI.
If you are resolving an issue, please link the corresponding issue number.

Summary of Changes:
Fixes: Issue #309

Test Data or Screenshots
Include proof that your changes function properly and resolve the linked issue.

Checklist
Please review and confirm each of the following before creating your pull request.

[x] I have reviewed the Contribution Guidelines.
[x] I have performed a self-review of my own code.
[x] I have checked my code and corrected any errors.
[x] I have commented my code or used an effective naming scheme.
[x] I have updated my repository to match the master at SetProtocol/index-ui.
[x] I have included test data or screenshots that prove my fix is effective or that my feature works.

If all of the above are true, then you may mark your pull request as ready for review.

INDEX emissions:
https://gov.indexcoop.com/t/iip-53-dpi-liquidity-mining-july-2021/1842
https://gov.indexcoop.com/t/iip-52-mvi-liquidity-mining-july-2021/1841


spirv-val: Incorrect validation of NonWritable decoration

The OpenCL CTS includes a set of pre-assembled SPIR-V modules, as part of its "spirv_new" test component. Two of the binaries fail to validate, but it appears that this may be due to a bug in the validator. The failures are:
$ spirv-val test_conformance/spirv_new/spirv_bin/decorate_nonwritable.spv32
error: line 57: Target of NonWritable decoration is invalid: must point to a storage image, uniform block, or storage buffer
  %src = OpFunctionParameter %28
$ spirv-val test_conformance/spirv_new/spirv_bin/decorate_nonwritable.spv64
error: line 65: Target of NonWritable decoration is invalid: must point to a storage image, uniform block, or storage buffer
  %src = OpFunctionParameter %35

In each case, the decoration is applied to an OpFunctionParameter of type OpTypeImage %void 2D 0 0 0 0 Unknown ReadOnly (i.e. %28 and %35). Here, the sampler type of 0 indicates that "whether or not this image will be accessed in combination with a simpler" "is only known at run time, not at compile time". Changing this to 2 silences this validation failure, but replaces it with another one.
If the sampler type is changed to 2, then the subsequent use of OpSampledImage fails to validate. The OpSampledImage instruction in question takes a result type which is the result of OpTypeSampledImage, applied to the OpTypeImage type described above. The image operand in the previously described OpFunctionParameter result. The validation failures are then as follows:
$ spirv-val test_conformance/spirv_new/spirv_bin/decorate_nonwritable.spv32
error: line 70: Expected Image 'Sampled' parameter to be 0 or 1
  %TempSampledImage = OpSampledImage %32 %src %34
$ spirv-val test_conformance/spirv_new/spirv_bin/decorate_nonwritable.spv64
error: line 81: Expected Image 'Sampled' parameter to be 0 or 1
  %TempSampledImage = OpSampledImage %39 %src %41

The SPIR-V specification states that for OpSampledImage:

Image is an object whose type is an OpTypeImage, whose Sampled operand is 0 or 1, and whose Dim operand is not SubpassData.

Presumably, a Sampler type in OpTypeImage of 2 indicates that the image will never be used with a sampler, not even with OpSampledImage.
Is the validator therefore being too strict in disallowing use of NonWritable against images with runtime determination of sampling? It seems to me that the intent of the specification was to forbid use of NonWritable with sampled images, as these are inherently non-writable.
If so, the validator should accept use of the NonWritable decoration on images for which the image type has a Sampling operand of 0.

Note also, the decorate_volatile.spv{32,64} and decorate_coherent.spv{32,64} tests pass despite being almost identical to the decorate_nonwritable tests, and despite the Volatile and Coherent decorations having very similar requirements with regards to storage images. It seems plausible that there is a gap in validation coverage for the Volatile and Coherent decorations.

The spec for NonWritable says:

Must be applied only to memory object declarations or members of a structure type. Any such memory object declaration, or any memory object declaration that contains such a structure type, must be one of:

A storage image (see OpTypeImage).
...

And a storage image is defined in OpTypeImage as:

Sampled indicates whether or not this image will be accessed in combination with a sampler, and must be one of the following values:
0 indicates this is only known at run time, not at compile time
1 indicates will be used with sampler
2 indicates will be used without a sampler (a storage image)

So the spec seems to indicate the decoration should not be used with OpenCL images. I would suggest opening on internal SPIR-V issue about this.

Why does it follow that the decoration should not be used with OpenCL images? OpenCL images support samplers. What have I missed?

The NonWritable decoration can only be applied to storage images. That is images with a Sampled value of 2. OpenCL uses images with a Sampled value of 0. Those are not storage images according to the spec.


Design System > Element > Banner : Add new story for header banner [New Project Flow]

Design System > Element > Banner : Add new story for header banner
With heading [Dynamic Test]
Backgroundimae
sub title , sub heading [Dynamic Test]
along with 2 rds buttons
Hyperlink

Fixed on dev

Fixed on staging


Alternative syntax for lab mr create

The lab mr create would be much more helpful if the following options are available.

GitLab MR property
options

source_branch
-s <source-branch-name>

target_branch
-t <target-branch-name>

@jspreddy I'm just noticing the description of lab mr create is misleading

Currently only supports MRs into master
This is actually no longer true, as of 0.10 lab supports passing the target branch as a positional argument. Likewise the source branch is based on the currently checked out branch.

Usage:
  lab mr create [remote [branch]]

Do you specifically need them as flags or is this just the result of poor documentation? In either case I'll for sure make sure to improve the docs for lab mr create to detail setting source/target branch and title/description as part of this issue.

@zaquestion
Yes, I did notice that it supported the destination branch.
The issue is that I need to specifically check out the source_branch in order to create a merge request to destination_branch.
I want to be able to create merge requests from a branch that is not currently checked out locally.
I want to be able to specify both the source_branch and the destination_branch. So that I can create merge requests without having to check out the branch locally.

How would this syntax work for you?
lab mr create [remote[/source] [target]]

It seems like this would be the most git-like way to support this functionality, which is the goal.
Ex
lab mr create origin/source_branch target_branch

If that sounds good I can probably put it together this weekend and have it the next release

Updates to the lab mr create docs have been released in 0.10.1, planning to implement the above in 0.11.0

Sounds good. Can the remote be an optional param?
lab mr create source_branch target_branch

Or do you think that having remote in there is the better way to do this?

Okay after actually going to implement this, I realize that the below, makes no damn sense..
lab mr create [remote[/source] [target]]

The remote doesn't relate to the source branch at all, the only way the above would make sense is if you swapped the source and target. I'd argue thats not very intuitive, in addition its technically a breaking change.
After looking at the git push docs a bit, this seems like appropriate syntax, it also align to the new lab ci trace syntax so thats promising
lab mr create [remote [[source:] <target>]

Ex
lab mr create origin source_branch:target_branch

The remote kinda has to be there since its the first positional arg and I don't think changing its a good idea. Largely because git enforces the contraints on it's commands

Additional Thoughts, perhaps lab mr create just isn't well suited for this usecase. lab mr create is largely to make creating a merge request for the current branch as simple as possible. Its very context driven and it seems like the goal here is to have a better general purpose option thats still human friendly.
Implementing the above (lab mr create [remote [[source:] <target>]) should be pretty simple, but I don't think it'll "improve" that command and it doesn't seem like an ideal solution to the perceived usecase here. Particularly since there would still be no way to set the source remote/user.
So, my alternate proposal is a new command to support a new usecase: lab mr new (working title) to support general purpose mr creation. Syntax wise I'm thinking
lab mr new [[<remote>/] <source>] [[<remote>/] <target>]

This makes both remotes settable and optional by default.
lab mr new source_branch target_branch

or explicitly
lab mr new zaquestion/source_branch origin/target_branch

@jspreddy Any thoughts?

lab mr new zaquestion/source_branch origin/target_branch is this a cross repository merge request?
Is the origin a repository and zaquestion a repository?

I assume that the remotes would have to be the same for both source and target branches. Is that not the case? Can the remotes be different? How does that work?

The remotes can be different, consider the case where you fork a repo and want to create a merge request against the upstream.
In my example, I'm referring to origin as some repo that's been forked by my user and creating and Mr from my version to theirs

Ah ok, got it. I was unaware of this feature in gitlab. I thought forking was only available in github. Turns out I was blind while in gitlab. :p
Maybe because I have access to all my orgs' repos and could contribute directly to the repo, I was blind to the existence of fork.
https://docs.gitlab.com/ee/workflow/forking_workflow.html

lab merge-request can probably be deprecated as it does the same thing as lab mr create origin master

@jspreddy any thoughts on which approach to take?

lab mr new zaquestion/source_branch origin/target_branch
I like this approach but I am not sure about the new keyword. I think it is confusing especially since we have the create.
lab mr create
lab mr new

I think it might be good to figure out one common format which can accomplish all the requirements.
From what I understand from this conversation, I think the requirements are somewhat like this:
Considering the following variables:

remote: which repository is the branch on?
source_branch: the source branch name.
target_branch: The target branch name.

Requirements for the above variables:

Have a default source and target and remotes for each.

source: current <commit_hash> that is checked out in local repo
target: master
remote: origin

Be able to specify the source and target and remotes.
The remotes should be independently specifiable for both the source and target

Scenarios:
Scenario 1:
Consider a scenario where origin/master exists and feature is a local branch that has not been pushed up to origin yet. And it is currently checked out in the local repo in the scope of which the command is run. i.e. the pwd is the git repo.
lab mr create with no other parameters specified should try to create a MR from origin/feature to origin/master. It will fail, but that would be expected behaviour. Had the feature branch been pushed up to origin, the MR would have been created.
Scenario 2:
consider a scenario where origin/develop exists and origin/feature exists. And feature is checked out locally in the pwd git repo.
lab mr create origin/develop should create a MR from origin/<current_commit_hash> to origin/develop.
This will make sure that what we are trying to merge is actually available on origin. Because some one might have forgotten to push up their commit. And by defaulting to the <commit_hash> if the source is not specified, we also handle the scenario of mismatch between local/feature and origin/feature.
Scenario 3:
In the above scenario, if the user specified the source like lab mr create origin/feature origin/develop, then the MR should be created as requested even when the branches are mismatched.

Sorry if this is overwhelming. I am just trying to document the requirements so that we are on the same page. I want to help.

Thinking more and more that perhaps making lab mr create operate as proposed above is the right approach, if we can pin down the same level of comfort that the existing command has. We're still pre-1.0 so this is certainly the time to do it. Also I'm inclined to think most user are only using lab mr create with no arguments since the target branch was only added recently.
@bmess You're an opinionated guy :smile_cat:  Any thoughts on these proposed changes to lab mr create
Proposed
lab mr create [[<remote>/] <source>] [[<remote>/] <target>]

lab mr create source_remote/source_branch target_remote/target_branch

with the following shorthand
lab mr create target_remote/target_branch
lab mr create // as it works today

Existing
lab mr create [remote [branch]]

lab mr create target_remote target_branch

@jspreddy I'm taking this out of the 0.11.0 milestone to unblock the release. I'd like to collect more feedback from people currently using lab, but I largely think moving to the above proposal is the way to go.

Yea, that is good. Don't want to rush things. Expecially since this is going to be a major change in the API.

Got recently bit by this in #156 -- had an idea.
Change lab mr create to behave by attempting to create an MR with the most recently opened branch.
Use arguments from earlier proposal
lab mr create [[ <remote>] <source>]      [[<remote>] <target>]
lab mr create source_remote/source_branch target_remote/target_branch

This should largely maintain legacy behavior while providing a more extensible API.

+1 on this issue
The use-case I want is to create a standing 'staging->production' MR in my build via CI.  Then when I am ready for a prod deploy, I just merge it and wait for the next staging build to recreate it.
In order to do this, I need to:

Change the existing syntax to support arbitrary branches origin/staging origin/production works for me.
I don't think it should rely on working copy, since MRs don't (you would need to push first).
Update or delete an existing MR with the same name before recreating.

@gtrak Did my previous comment with suggested behavior/syntax work for your first bullet? I'm not sure lab should be so clever to support the 2nd bullet within 1 command but that seems doable if you scripted it with a combination of commands. Lets chat a bit about it.

I think your suggested syntax is fine for point 1.
Re #2, that might be too esoteric of a need across users, so I'm happy to script it with multiple commands.
I'm coming from phabricator/arcanist (which I actually dislike for a lot of reasons), but we did this with arc diff --update in CI to update a diff/PR/MR that we'd land manually when we are ready to deploy.

AFAICT this issue was solved in version 0.22.0 through 63c2db6414511, which added the --source flag to lab mr create command: now you can pass whatever --source <remote>:<branch> and the target remote/branch is passed through positional args, i.e. lab mr create --source remote:branch target_remote target_branch.
Would that cover the initial case of this issue?

This feature has been implemented for quite some time already and since we had no feedback for my last comment I'm going to close it as "solved".
But feel free to reopen it if needed.


Proposal: Include release name and chart name in value files

I think helm need to persist all state(release name, chart name, etc.) in the values file so I can simply do:
helm apply -f values.yaml

which is more friendly with GitOps flow.

@zzq889 Do you mind explaining what you mean by state? Are you looking for help do save this state to your values file? Also, what version of helm are you using?

I use both helm2 and helm3.
For kubernetes resources in a folder, I can simply do kubectl apply and everything will be updated.
// kubectl apply -f .
a.yaml
b.yaml
c.yaml

For helm command, I have to specify release-name and chart-name/path. When I do continuous deployment, it's hard to know the chart name in a mixed folder like this:
// helm upgrade -i [release-a] [chart-a] -f a-values.yaml
a-values.yaml -> chart-a
b-values.yaml -> chart-b
c-values.yaml -> chart-c

what I want to do is:
helm apply -f a-values.yaml

without any additional args

@hickeyma any update?

@zzq889 I am not sure we want to put the chart name and release name in the values file. helm get should be able to give the information that you need.

@hickeyma Based on infra as code principle, anything should be persisted in a repo. The values.yaml file has less info we need to reproduce the CD workflow. I think we need a mechanism to achieve this.

@zzq889 Maybe I am missing something here but I don't see a good reason for this proposal. What is the use case that is not already covered by Helm already?

@hickeyma for example, batch apply of apps: Multiple values with different chart deployed within a simple helm apply cmd which is capable in kustomize or kubectl apply.

@zzq889 Maybe your requirement could be related to #5276?

@zzq889 Thank you for your ideas to improve Helm. If you'd like, you can submit a Helm Improvement Proposal so as to work in the community to make your ideas a reality: https://github.com/helm/community/blob/master/hips/hip-0001.md - meanwhile, I will close this issue. Thanks!


How do I check every tag if contain specific commit

I use some way to check every tag which is contain specific commit.But the result not the same with "git tag -contain SHA".
Can go-git do this?

Is someone working on this ?


Remove unused Java classes

app/src/main/java/com/one4ll/xplayer/MyContentProvider.java
app/src/main/java/com/one4ll/xplayer/TaskContract.java
app/src/main/java/com/one4ll/xplayer/TaskDbHelper.java
These files are not used in the app. Deleting them from the repo will make the repo 100% Kotlin :)

https://github.com/gouri-panda/XPlayer/pull/16

@ardlank Nope thats not necessary.


TryVerify error while load a torrent which source file is large and torrent type is v1v2hybird

I created a 40gb file's torrent with default type, when I load the torrent,
this line would occur an error

but v1only torrent would be ok

I also encountered this problem, have you solved it? @ycy1164656

This should be solved in master, and also the latest beta release in NuGet. Thanks for reporting!

Specifically - this should have resolved the problem: https://github.com/alanmcgovern/monotorrent/commit/c766bc86d9fba1717ce9b86f6763e187c9987863


[RoadMap] development plan for Chinese inverse text normalization

Project Explanations:

Following NeMo's (1) classification + (2) verbalization two-stage method, we plan to adapt jiayu's ITN grammar to this two-stage pipeline (for more details, plz see this paper).

The reasons why we choose to separate Chinese ITN into two stages (each stage has its own WFST) rather than transduce input text using a single WFST:

WFSTs can only process input linearly, but the word order can change from spoken to written form (i.e. 三分之一 -> 1/3)
English ITN grammars, which has been carefully designed in NeMo, can be seamlessly integrated into this project

Road Map:

[ ] Design semiotic-class for Chinese
[ ] Update Chinese ITN grammars from single-stage to two-stage
[ ] Simplify ITN related code of Sparrowhawk(C++) and migrate it to WeNet runtime

危楼高百尺，手可摘星辰。不敢高声语，恐惊天上人。


[C++] ChunkedArrayResolver::Resolve is prematurely template-specialized

Describe the enhancement requested
ChunkedArrayResolver::Resolve<T> can be made more generic by always producing a ResolvedChunk<arrow::Array> instead of

ResolvedChunk<arrow::Int64Array>
ResolvedChunk<arrow::BoolArray>
ResolvedChunk<arrow::StringArray
and so on...

It's only ResolvedChunk::Value that needs to specialize on the sub-type of arrow::Array.
Other possible improvements that might end up with their own dedicated issues:

Make ChunkedArrayResolver constructable from std::vectors of other chunk array types (eg std::shared_ptr<Arrow>, std::shared_ptr<ArrayData> instead of just const Array
Make that construction step zero-copy

Component(s)
C++

Issue resolved by pull request 40281
https://github.com/apache/arrow/pull/40281


Fix protein mutation repex consistency tests

Description

This PR introduces the following changes:
For speed up:

Decrease the number of steps per iteration from 250 to 50
Set reassign_velocities to be False

For improved convergence:

Set n_iterations = 3000 for the neutral mutations and = 3000 for the charge changing mutations
Set n_replicas=36 for the charge changing test
Set minimisation_steps = 0, which means that the minimization will run until the energy is below a tolerance (instead of running for 100 steps, which is the default in HybridRepexSampler)
Change the convergence criteria to check if DDG < 6 * dDDG

Other:
~- Change the solvent padding to be 1.7 nm (which is necessary for the nightly dev builds of openmm). Note this may make the tests slower if we are testing against OpenMM <= 7.7~ EDIT: We are currently testing against openmm 7.7. We should not bump up the solvent padding until we switch the GPU tests to test against openmm => 7.8

Clean up unfinished comment and reporter file name

Motivation and context

This PR changes some of the parameters in the protein mutation repex consistency tests to ensure convergence (DDG < 6 * dDDG) and speed up the tests.

Resolves #1044
How has this been tested?

Tested on lilac.
Change log

Fix protein mutation repex internal consistency tests to ensure convergence and speed up the tests. So far only testing neutral transformations.

I think we'll want to skip the charge changing test for now -- @ijpulidos do you know how to do this?

Just wanted to say, that according to our latest GPU CI workflow, we are testing correctly just the neutral mutation. It is passing and taking ~5.5 hours.

This is odd. I was wondering why it took so long, so I ran the test on lilac on a GTX 1080 Ti, using
$ pytest -vvv --log-cli-level=DEBUG --log-cli-format="%(asctime)s %(levelname)s %(message)s" perses/tests/test_repex.py::test_RESTCapableHybridTopologyFactory_repex_neutral_mutation

to print a timestamp for each step.
It's been stuck at Generating unsampled endstates for a full hour!
00:11:03 WARNING Warning: The openmmtools.multistate API is experimental and may change in future releases
00:11:03 WARNING Warning: The openmmtools.multistate API is experimental and may change in future releases
00:11:05 INFO n_replicas not defined, setting to match n_states, 12
00:11:17 INFO Generating unsampled endstates.

@zhang-ivy : Is it possible this is actually taking an hour? Any idea why?

Hm---I think this is a red herring. If I disable the endstates in the test, it goes silent after the previous line:
01:24:42 WARNING Warning: The openmmtools.multistate API is experimental and may change in future releases
01:24:42 WARNING Warning: The openmmtools.multistate API is experimental and may change in future releases
01:24:43 INFO n_replicas not defined, setting to match n_states, 12

Some of our code must be disabling or changing the logging so I'm not getting any profess information even when requesting it via --log-cli-level=DEBUG. Any ideas why @ijpulidos or @mikemhenry?

For small molecules in solvent, I thought I had been seeing ~30 min
execution times before.
Instead of looking at the overall time (which is not very informative), I
really want to see the breakdown of where time is being spent once we get
past the first iteration.

@jchodera : I posted the logs (for the last 2 iterations) of a charge changing mutation (ALA->ARG) as well as a neutral mutation (THR->ALA) here

For small molecules in solvent, I thought I had been seeing ~30 min
execution times before.

Hmm, I don't think we've finished writing the tests for small molecule repex consistency yet, so I'm not sure where that would be from, but maybe @dominicrufa  knows which data you're referring to?

I had been referring to timings of small molecules in solvent from my own
previous experiments.
Two things worry me from the logs:

The energy matrix computation is way too long at over 3s. This should be
less than 1s. We need to look into why this is happening. Are long range
dispersion corrections slowing things down?
The replica propagation time is nearly 7s. This seems way too long for a
small solvent box. Do you have this calculation staged on disk somewhere?

@jchodera : For the neutral (THR->ALA) mutation, which uses n_replicas=12, propagating replicas takes ~2 seconds and computing energy matrix takes < 1 second. However, running 5000 iterations still takes ~3.5 hours, which you mentioned is much longer than expected. Is 2 seconds still much longer than you'd expect for the replica propagation time? If not, then I'm not sure what else would be making these so slow.
All the scripts/output files for this are located here: /data/chodera/zhangi/perses_benchmark/repex/38/38/with-perses-paper-test/, although I just accidentally deleted the log file :(
For the charge changing (ALA->ARG) mutation, which uses uses n_replicas=36, propagating replicas and computing the energy matrix take longer, as you mentioned above. I think the reason is because we are using so many more replicas.
All the scripts/output files are located here: /data/chodera/zhangi/perses_benchmark/repex/38/39/
Also since the solvation procedure has changed in openmm, i just want to double check that i'm using the appropriate amount of solvent. I'm using padding = 1.7 nm. Here is solvated capped ALA:

I spoke with @dominicrufa about implementing a LangevinMiddleIntegrator variant of LangevinDynamicsMove, which would give us better configuration-space accuracy. This uses BAOAB, and should be very easy to put into the upcoming openmmtools release that @mikemhenry will need to cut.
In general, I think we want to set reassign_velocities=False once we have fixed the velocity resume issue. This will reduce correlation times.
The other slowdowns---generating the htf in the same script, as well as the difference between hybrid propagation and repex---are things we might want to look into as well.

@jchodera :  A new LangevinDynamicsMove with LangevinMiddleIntegrator sounds great, and fixing the velocity resume issue would also be very helpful, but I'm wondering how essential it is for me to wait for these improvements to be able to start generating data for the barnase:barstar paper. I'll set up a time to chat about this (and other software roadblocks I've been experiencing) next week

We should use a BAOAB-based  integrator, which means you cannot use LangevinDynamicsMove since it is based on OBABO.
It may be easier just to modify LangevinDynamicsMove to use openmm.LangevinMiddleIntegrator, since there's no reason to specifically use openmm.LangevinIntetegrator. This is a one-line change here we should be able to get in right away.


refactor: replace deep-equal with dequal

Description

deep-equal contains up to 50 sub-dependencies.
https://npm.anvaka.com/#/view/2d/deep-equal
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

(Too long to post)


AllTable Function new features + Blog

This PR adds a couple of features that were inspired by the writing of this blog post on Diane allTable Function.

Added the ability to select a set of tables to describe. Before we could only execute the function on a whole table.
Added schema as a new column.
Fixed issue with the name column produced by the described table extended.

Once this PR is merged I will publish a new version of Diane so the allTable function can be used.

Blog post looks great.  Awesome work!


Implement unit test for withdrawing balance belonging to PTS address

Importing balance using PTS address needs to be tested.  Since it is migration related, assigning to @vikramrajkumar

This issue was moved to bitshares/bitshares-2#46


Support TEXMAP language extension

Add support for TEXMAP and make sure not to repeat mistakes of other renderers where adding TEXMAP to transparent elements also make the textures transparent.

Done when the texmap branch got merged.


Sharing a variable between jobs

Currently, the only way to interact between jobs is by creating a file (preferable .txt file).
That is like an overkill when it comes to sharing  a single variable.
Would be very good if there's a method way more simpler.

You can already do that: https://stackoverflow.com/a/61236803/11649486


Typechecking tsc , after running npm run build fails with Error TS2691: An import path cannot end with a '.d.ts' extension

What version of Remix are you using?
1.6.3
Steps to Reproduce

Run npm run build
Run npm run typescript-typecheck (which is essentially just running tsc command from typescript

Codesanbox of app (click + button to open new terminal tab session):

https://stackblitz.com/edit/node-uegzhy?file=package.json

Expected Behavior
tsc command should not fail.
Maybe there is another recommended way we can run the type check?
Actual Behavior
tsc command should not fail

Fixed by #3623


added terms and conditions

@Puskar-Roy
I have added the terms and conditions page and made it responsive for the mobile view as well
Sorry I have deleted the previous PR by mistake, that why I created this new PR
And also in the previous PR, you have added all the labels and considered it as level3, please dont forget to add the labels here
The issue number is #123
Kindly check it out
https://github.com/user-attachments/assets/82c5652e-ae83-4c63-a5aa-78d1b4b7f9a9

Hello @AswaniBolisetti, thank you for your pull request! We will review it shortly. 😇❣
Your contributions help us grow and improve our project. Please make sure you have read and followed our CONTRIBUTING GUIDELINES.
Your efforts are appreciated, and we value your participation in our community. Don't forget to ⭐ our repository!
Happy coding!✨


Add badge to the Activity Bar icon to show number of failing tests

just like GitLens with the number of changes.

It seems that the vscode extension api does not support such a feature for now: Microsoft/vscode#62783


Refactor encode_action_body

This code:
https://github.com/icerpc/icerpc-csharp/blob/b06a0d078a3d8e929873592d6159ac6326571308/tools/slicec-cs/src/encoding.rs#L349
should be simplified. It's confusing to compute value and then most of the time not use it but instead hardcode "value".
It would be nice to add some comments too. For example, explain why we create this strange helper variable:
let is_optional = type_ref.is_optional && !is_tagged;

This function got some simplification in #3916.
There is still more opportunity for simplification, but it would require untangling the other functions that call into it first.


vue-tsc versionning and vscode-vue-languageservice dependency

Currently vue-tsc specifies vscode-vue-languageservice as a dependency  with version^0.27.0.
As vscode-vue-languageservice gets released pretty often, you can have different behaviors in 2 projects that installed<EMAIL_ADDRESS>but at different times.
When vscode-vue-languageservice has a new interesting feature (or a regression), we can't easily install a specific version with NPM, as the one required by vue-tsc will be used (except in yarn projects where you can ask for a specific resolution).
Furthermore, tools like Renovate or Dependabot won't update vue-tsc until a new release is out, so you don't benefit from the new features of vscode-vue-languageservice until a new release of vue-tsc.
It could be interesting to either :

release vue-tsc with the same version number than vscode-vue-languageservice, and with a fixed version dependency. For example<EMAIL_ADDRESS>would have a dependency to<EMAIL_ADDRESS>move vscode-vue-languageservice to a peer dep, so it could be specified in the project package.json, and set to a specific version easily.

You can use resolutions  to roll back version, see: https://github.com/johnsoncodehk/volar/discussions/402

release vue-tsc with the same version number than vscode-vue-languageservice, and with a fixed version dependency. For example<EMAIL_ADDRESS>would have a dependency to<EMAIL_ADDRESS>

This is the most intuitive method, but it will cause github repos keep receive updates spam from vue-tsc.

move vscode-vue-languageservice to a peer dep, so it could be specified in the project package.json, and set to a specific version easily.

Maybe use this way in the future. The only disadvantage is that if the user does not explicitly add vscode-vue-languageservice to the dependency, the package manager tool will report a warning.

Thanks for your reply!
The problem is that you can't use resolutions if you use npm and not yarn.

This is the most intuitive method, but it will cause github repos keep receive updates spam from vue-tsc.

Agreed. But I wouldn't mind keeping up-to-date, and tools like Renovate can be configured to slow the update pace for some packages https://docs.renovatebot.com/noise-reduction/#selective-scheduling (this works very well).

Maybe use this way in the future. The only disadvantage is that if the user does not explicitly add vscode-vue-languageservice to the dependency, the package manager tool will report a warning.

I agree as well. But this would be of great help when you need to upgrade or downgrade to a specific version, and you can't use resolutions.
Anyway, thanks for your work and for considering these options.

This will process after refactored volar, because the dependency of vue-tsc may change from vscode-vue-languageservice to a smaller module.


Fix bug of update person

Bug fixed where updating person does not update groups or expense

Codecov Report

Merging #158 (393383c) into master (2b6ec03) will decrease coverage by 0.48%.
The diff coverage is 7.89%.

@@             Coverage Diff              @@
##             master     #158      +/-   ##
============================================
- Coverage     61.79%   61.31%   -0.49%
  Complexity      504      504
============================================
  Files           101      101
  Lines          1937     1962      +25
  Branches        224      230       +6
============================================
+ Hits           1197     1203       +6
- Misses          683      701      +18
- Partials         57       58       +1

Impacted Files
Coverage Δ

src/main/java/seedu/awe/model/expense/Expense.java
0.00% <0.00%> (ø)

src/main/java/seedu/awe/model/group/Group.java
41.25% <0.00%> (-19.87%)
:arrow_down:

src/main/java/seedu/awe/model/person/Person.java
75.92% <ø> (+3.51%)
:arrow_up:

...in/java/seedu/awe/model/group/UniqueGroupList.java
77.27% <28.57%> (-5.78%)
:arrow_down:

src/main/java/seedu/awe/model/AddressBook.java
80.76% <100.00%> (+0.37%)
:arrow_up:

src/main/java/seedu/awe/model/group/GroupName.java
78.57% <0.00%> (-14.29%)
:arrow_down:

...java/seedu/awe/logic/parser/ArgumentTokenizer.java
93.18% <0.00%> (-4.55%)
:arrow_down:

...java/seedu/awe/logic/parser/AddressBookParser.java
76.00% <0.00%> (ø)

...a/seedu/awe/logic/commands/CreateGroupCommand.java
83.78% <0.00%> (ø)

...edu/awe/logic/parser/CreateGroupCommandParser.java
67.50% <0.00%> (+5.37%)
:arrow_up:

... and 3 more

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 2b6ec03...393383c. Read the comment docs.


Adds snippet support

Description
Adds snippet support to the API
I wasn't sure how far away v2/v3 will land and my team would love to have Snippets supported in Terraform. If this is accepted, I can work on getting the Snippet rules next.
Adds:

GetSnippet
ListSnippets
DeleteSnippet
PutSnippet

I still have some further testing to do to make sure that these all behave as expected.
Types of changes
What sort of change does your code introduce/modify?

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

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[ ] This change is using publicly documented in cloudflare/api-schemas
and relies on stable APIs.

v2/v3 already has this support so unless you need something specifically in the v0 range, i would recommend using it instead of adding this.
we already support the newer library in the terraform provider as well.


Oregonator

Codecov Report
Patch coverage: 75.00% and project coverage change: -0.43% :warning:

Comparison is base (7021f00) 97.23% compared to head (4c0347f) 96.80%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #222      +/-   ##
==========================================
- Coverage   97.23%   96.80%   -0.43%
==========================================
  Files          32       32
  Lines        2564     2600      +36
==========================================
+ Hits         2493     2517      +24
- Misses         71       83      +12

Files Changed
Coverage Δ

include/micm/process/process.hpp
88.00% <0.00%> (-12.00%)
:arrow_down:

include/micm/solver/rosenbrock.hpp
100.00% <ø> (ø)

include/micm/solver/rosenbrock.inl
95.49% <100.00%> (-1.08%)
:arrow_down:

include/micm/system/system.hpp
95.55% <100.00%> (+0.96%)
:arrow_up:

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


e2e test cases and documentation for Aggregated TAD

This PR introduces:

e2e tests for Aggregated TAD
Documentation for Aggregated TAD

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e

/theia-test-e2e


conmon: 2.1.2 -> 2.1.3

https://github.com/containers/conmon/releases/tag/v2.1.3
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 182878 run on aarch64-linux 1

4 packages built:

buildah
conmon
cri-o
podman

Result of nixpkgs-review pr 182878 run on x86_64-linux 1

4 packages built:

buildah
conmon
cri-o
podman


[AC][SUPP-302] dynamic service name + cleanup

@barnesjake @nubz @pawelpanasewicz I've made a couple of changes after the comments above - do you mind looking at the PR again please? I've made a separate layout for the test-only stuff so that it's safer.
I've ignore a test for now but that it something that is currently being worked on in a separate ticket so it will be replaced with a proper implementation soon anyway.
I've also made the logs nicer to look at:

Same info, but new colours to help read it better.


this does not work on raspberry pi or at all for me

i updated everything after installing the requirements and it still says modules not found with useragent first it was fake useragent then i updated it. now when i am in root it says i must be root to run this. the same thing happened to be using nethunter kali this tool is broken

@Sheikh-Nightshader

the same thing happened to be using nethunter kali this tool is broken

If you have at least the reading ability of a third grader, you can see under the Prerequisites section of the README file that I mentioned Windows or Linux operating systems are required to run this script.
However, if you have at least beginner-level coding skills, you can see the "Check for root" condition in the script and remove it.
You can try these too:
sudo pip3 install --upgrade scapy aiohttp fake-useragent

sudo apt-get install python3-scapy

sudo python3 NetStrike.py

Yup removing the root permission did it thanks.  I really thought this was broke or my permissions where. But this is happening on both nethunter and my raspberry pi. Thanks again ill give it a run my friend said this is pretty kool and now i can tell him how i think

Ok yes Nice works great. Thanks again. Problem solved


use cobra

cobra is cool

Yeah it is, I think there is even an easier way to use subcommands.  Check out how Zarf does it.  https://github.com/defenseunicorns/zarf/tree/main/src/cmd

https://github.com/defenseunicorns/zarf/blob/main/src/cmd/prepare.go#L145-L149

https://github.com/defenseunicorns/zarf/blob/main/src/cmd/prepare.go#L145-L149

ya I wanna use flags not sub commands
. I did look into that though

I'm cool with it is the way it is.  It might make it easier to expand upon in the future.
For example:
kxd files list
kxd files current
kxd context list
kxd context switch
kxd context current

Then you can alias things like (or whatever you want)
kxd f ls
kxd f c
kxd ctx ls
kxd ctx s
kxd ctx c

... as so on...


how are alignment graph obtained for new datasets

Hi, in your coding,h5py.File features has keys like ['%d_features' % image_id] , ['%d_grids' % image_id], ['%d_boxes' % image_id], ['%d_size' % image_id], ['%d_mask' % image_id], If I have a new data set, can I just use align.py to get geometric alignment graph after I get grid features and region features using extract_region_feature.py and grid-feats-vqa.

Yes, all codes for generating geometric alignment graph are in align.ipynb with visualization function.


buildNpmPackage / prefetch-npm-deps doesn't support proxy

Describe the bug
prefetch-npm-deps doesn't support proxy. I have http_proxy and https_proxy environment variables defined, but it doesn't work which make it impossible to build something in closed corporate environments. Also I suspect that NIX_SSL_CERT_FILE environment (ca-certificates bundle) would not work also.
Steps To Reproduce
Steps to reproduce the behavior:

A PC without direct Internet access. Only proxy is available for Internet access.
http_proxy, https_proxy, NIX_SSL_CERT_FILE environment variables are defined for nix-daemon.service.
Build any buildNpmPackage package.

Expected behavior
Npm dependencies successfully fetched.
Screenshots
I've got an error "Network is unreachable (os error 101)". Example failed build log:
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/pgqsk8sdh6gg9kdqi8iijhw6sng6qwiv-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
@nix { "action": "setPhase", "phase": "configurePhase" }
configuring
no configure script, doing nothing
@nix { "action": "setPhase", "phase": "buildPhase" }
building
node_modules/@babel/cli
node_modules/is-boolean-object
node_modules/@babel/plugin-transform-destructuring
node_modules/babel-plugin-dynamic-import-node
node_modules/string-width
node_modules/path-parse
Error<EMAIL_ADDRESS>Connection Failed: Connect error: Network is unreachable (os error 101)

Caused by:
    Network is unreachable (os error 101)

Additional context
Most of the fetchers work via proxy which intercepted ssl. This one not. I think all fetchers should support it.
Notify maintainers
@winterqt
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.3.18-59.34-default, SLES, 15-SP3, nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.15.1`
 - channels(root): `"nixpkgs-22.05pre338599.f6e14b6ada8"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Thank you for this report! It's a known problem, but we did not yet have an open issue for it, so this will be good for tracking
I was hoping we can swap out ureq for isahc, which uses libcurl and should automatically handle that, but last I touched my branch for that, it was having TLS cert validation issues
I'll hopefully get to this sometime in the next few weeks, unless someone else wants to work from my isahc branch and get it working before me (my work-in-progress commit is at https://github.com/lilyinstarlight/nixpkgs/commit/3b524a7f485c0071240b166f5d4f5f10da1f5b5c)


Is this repo licensed under MIT?

Hello, I could not find a license file in this repository, and the license section in the readme seems to be copied from another repo so the link is dead. Was the package intended to be licensed under MIT?

Sorry, just added, https://github.com/yiwen-ai/xid-ts/blob/main/LICENSE

Thanks a lot!


"Add a field" feature in schema editor

Ability to add a field from the schema editor.
The selected field can be a descendant from either FieldDef or CardDef.
If the field is FieldDef, and "limit to one" is selected, the relationship will be contains, and containsMany when "allow multiple" is selected.
If the field is CardDef, we will assign linksTo or linksToMany.
Works like this:
https://github.com/cardstack/boxel/assets/273660/13ea5e78-63f0-43aa-84f1-c92a423f6a56

Was messing about. It seems adding a drafts card to a base card is a possibility. If we don't support this maybe the card catalog modal should not show the drafts card options when adding fields to a card in base workspace

It seems adding a drafts card to a base card is a possibility. If we don't support this ...

@tintinthong shouldn't drafts be treated as any other realm, while we do want cross realm linking? I'm wondering why that wouldn't be the case with drafts realm

It seems adding a drafts card to a base card is a possibility. If we don't support this ...

@tintinthong shouldn't drafts be treated as any other realm, while we do want cross realm linking? I'm wondering why that wouldn't be the case with drafts realm

Wud b great if it worked. Does the drafts/ import url resolve correctly within a base file?

It seems adding a drafts card to a base card is a possibility. If we don't support this ...

@tintinthong shouldn't drafts be treated as any other realm, while we do want cross realm linking? I'm wondering why that wouldn't be the case with drafts realm

Wud b great if it worked. I dont see any reason why we shud restrict base from importing only base fields or cards. But currently i dont think importing drafts to base works (Does the drafts/ import url resolve correctly within a base file?)

There should not be any restriction, currently, on which realm you can import a card from. Eventually there will probably be realm policy to control this—but let’s not speculatively add this.
In terms of the url resolution. The reason it looks funny is because we passed undefined in as the realm url in the ‘maybeRelativeURL()function. Perhaps the fix here is to thread the realm url of the field card thru as part of theincomingRelativeTo`

Also, can we confirm that the realm URL header for the base realm is “https://cardstack.com/base/“ and not “http://localhost…” we should be using the unresolved realm url in the header.

Or maybe that the outgoing relative url is the unresolved https://cardstack.com/base: and not “http://localhost…”

But currently i dont think importing drafts to base works (Does the drafts/ import url resolve correctly within a base file?)

I tried adding a drafts card to a base card (person card to number card in this case) and it looks like it works - is this what you had in mind?
Import (number.gts file after linking person card):

Schema editor (number.gts file after linking person card):

Also, can we confirm that the realm URL header for the base realm is “https://cardstack.com/base/“ and not “http://localhost…” we should be using the unresolved realm url in the header.

Confirmed, the header is unresolved:

But currently i dont think importing drafts to base works (Does the drafts/ import url resolve correctly within a base file?)

I tried adding a drafts card to a base card (person card to number card in this case) and it looks like it works - is this what you had in mind? Or should the import url be absolute in this case? I'm a little fuzzy on this.
Import (number.gts file after linking person card):

Schema editor (number.gts file after linking person card):

Also, can we confirm that the realm URL header for the base realm is “https://cardstack.com/base/“ and not “http://localhost…” we should be using the unresolved realm url in the header.

Confirmed, the header is unresolved so it should be ok:

What about the outgoingRelativeTo, is that also unresolved?

@habdelra so in that case (adding Person card to Number base card) the data is:
incomingRelativeTo is http://localhost:4201/drafts/CatalogEntry/1
outgoingRelativeTo  is http://localhost:4201/base/number.gts
relativeFieldModuleRef is /drafts/person (this is then used for importUtil.import)
Should outgoingRelativeTo be unresolved?

@habdelra so in that case (adding Person card to Number base card) the data is:
incomingRelativeTo is http://localhost:4201/drafts/CatalogEntry/1 outgoingRelativeTo  is http://localhost:4201/base/number.gts relativeFieldModuleRef is /drafts/person (this is then used for importUtil.import)
Should outgoingRelativeTo be unresolved?

AHA! that is the problem. the outgoingRelativeTo should be unresolved. that fixes this specific scenario. But there is another scenario where you have a module in published that has a field card and you want to add it to a module in drafts--you see the same problem there too. the way to fix that problem is to thread the realmURL of the incomingRelativeTo all the way to the maybeRelativeURL() function

@habdelra I think I'm having issues understanding how to recognize the anatomy of a correct import URL. I am unsure if these need to be relative, absolute, or cardstack prefixed (unresolved).
So for example, when I have a base card, let's say number, and I want to link add a Pet card to it, which URL is correct?
import { Pet as PetCard } from "http://localhost:4201/drafts/pet"; // This works

or

import { Pet as PetCard } from "/drafts/person"; // This also works

or

import { Pet as PetCard } from "https://cardstack.com/drafts/person"; // This doesn't work

@habdelra I think I'm having issues understanding how to recognize the anatomy of a correct import URL when linking different realms in our current setup. I am unsure if these need to be relative, absolute, or cardstack prefixed (unresolved).
So for example, when I have a base card, let's say number, and I want to link add a Pet card to it, which URL is correct?
import { Pet as PetCard } from "http://localhost:4201/drafts/pet"; // This works

or

import { Pet as PetCard } from "/drafts/person"; // This also works

or

import { Pet as PetCard } from "https://cardstack.com/drafts/person"; // This doesn't work

based on our pairing today, are you good now with this?

@habdelra yes, all clear about that! Will be pushing my updates shortly.

Ready for another round of reviews.

Ready for another round of reviews.

Based upon pairing, the updated code edits LGTM


Unable to open log device 'crash'

system: windows 10

Hello @zhang-longfei
Thanks for the report. Some words about your environment and target you're trying to access would be helpful.
rogcat by default runs add logcat -b main events crash kernel. Seem like your device doesn't have the crash buffer (which is Android standard). You can overwrite the rogcat default by applying the -b options to rogcat or configure the default behaviour in the config file (see Readme).

I don't know why, it is good now.


Add Search v1 + Misc Stuff

@pavitrabhalla @chrishaire
Changes

Added a search box to all pages + a search results page that the user is always redirected to when initiating a search.
After doing the Google Custom Search research I found some info on making sure our website is verified with Google for mobile search result ranking which is why I added "google4592d9aee6c0ac99.html" (more info at https://www.google.com/webmasters/tools/home?hl=en).
Since with github.io pages there's no .htaccess file that I can edit and I don't want /index.html to show up with people go back to our home page, I just updated all the links to be the home URL (franklyinc.github.io) instead.
This pull request unfortunately includes some commits that I made last night but including them here shouldn't be a problem at all since there have been no commits made in between. I'm sure this isn't good practice so if anybody is bothered by this, I'm happy to fix it but will need help.

:+1:


Automated way to create Arch Linux images on macOS

It takes a while to make an image, and it's especially on macOS, because you need to use a virtual machine. I think using software like Packer, this process could be automated. This is blocked until we use Dotman, see #325.

To present a contrary perspective, this is completely absurd.


ResponsiveValue.value should non-nullable

When you create a ResponsiveValue, you have to give it a default value, so why is ResponsiveValue.value nullable?

Good question! The default value can be null to support passing nulls.
An API improvement would be eliminating the required initial value perhaps?

Good question! The default value can be null to support passing nulls.
An API improvement would be eliminating the required initial value perhaps?

IMHO it would be better to remove the mandatory nullability of value. If you really do want it to be nullable you can still have that by using eg. ResponsiveValue<int?> instead of ResponsiveValue<int> , then value will also be nullable

Yes! This library actually predates null safety so <int?> wasn't an option.
That seems like a good implementation.

Really interesting API signature decisions.
https://github.com/Codelessly/ResponsiveFramework/pull/123#issuecomment-1592412698


Update firefox to 52.0

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

@neutric i believe we need to change appcast checkpoint

@gobinathm Indeed, forgot that! Thanks @vitorgalvao 🎈

Wow, over 24 hours and we're still waiting for travis-ci to get to this one! That's quite a backlog - https://www.traviscistatus.com/.

Forgetting to update the checkpoint certainly didn't make it better. ;)

@neutric Ah, right, that would've reset the clock. So it looks like https://github.com/caskroom/homebrew-cask/pull/30689 - 18 hrs old - is actually the oldest PR still awaiting CI review.

Verified this one locally.

@vitorgalvao You're the best, thanks. 👍  😄


v0.11 - when using --progress plain the stderr is outputted only at the end of the run.

What is the issue?
Hey there,
After upgrading to v0.11, I noticed that when using --progress plain, the stderr is outputted only at the end of the run. Why is this important? When running in CI, there will be no feedback given to the user (unless the go code explicitly writes to stdout/err) until the end of the run. This may take minutes.
That being said, the new plain output, once it has been outputted, is SOOOOO MUCH better in v0.11. 🙂
Expected: the dagger/container/services stderr is streamed as it generated like in <= 0.10
Actual Behaviour: the dagger/container/services stderr dumped at the end of the run.
I believe it is a regression from dagger v0.10.X. Using --progress tty "fixes" the issue, but the output is not suitable for a standard CI.
You can find an example here: https://github.com/j-martin/dagger-mysql/tree/f8fbe224264f7fc0bf48730dccb0a5e4a1039124
Dagger version
dagger v0.11.0 (registry.dagger.io/engine) darwin/arm64
Steps to reproduce

Checkout code in https://github.com/j-martin/dagger-mysql/tree/f8fbe224264f7fc0bf48730dccb0a5e4a1039124
Run dagger run --progress plain go run ./main.go

Log output
delayed logs, but the same logs

Duplicate of https://github.com/dagger/dagger/issues/7057


Refactor multiple counts in  and  root resolvers

Currently the count of records matching a search query is carried out multiple times. Once inside the resolver to determine the number of records to subtract from the current record limit and again inside the model layer when building the result object of limit-offset-based or cursor-based pagination. This is inefficient and should be refactored.
Refactor
Store the result of the count in the resolver layer in a variable and pass that variable to the respective model layer function(s).
Use default values for function arguments:
var count = function(searchArg) { return searchArg + 1 }
var readAllFancy = function(searchArg, countResult = count(searchArg) ) {
  console.log(`countResult is: ${countResult}`)
}

Check field resolvers and related model layer implementations of associations
Check whether this improvement will be automatically used by associations, too.

This blog post about named arguments and default values in Javascript maybe helps.

We will refactor readMany (readAllCursor, readAll) functions to not do a count. This will impact the implementations the respective functions as well as the reduction of the record limit, currently done in checkAndAdjustRecordLimit (resolver).
Sketch of the new design is maintained in hackMD document.


Fix method overwritten warning on julia master

The exact warning is as follows:
julia> using LibSndFile
INFO: Recompiling stale cache file /Users/ryuyamamoto/.julia/lib/v0.5/LibSndFile.ji for module LibSndFile.
WARNING: Method definition (::Type{LibSndFile.SndFileSink})(Any, Any) in
module LibSndFile at /Users/ryuyamamoto/.julia/v0.5/LibSndFile/src/LibSndFile.jl:91 overwritten at /Users/ryuyamamoto/.julia/v0.5/LibSndFile/src/LibSndFile.jl:95.

Current coverage is 97.27%

Merging #1 into master will increase coverage by +0.88% as of 7b73c56

@@            master      #1   diff @@
======================================
  Files            1       1
  Stmts          111     110     -1
  Branches         0       0
  Methods          0       0
======================================
  Hit            107     107
  Partial          0       0
+ Missed           4       3     -1

Review entire Coverage Diff as of 7b73c56

Powered by Codecov. Updated on successful CI builds.

Thanks for fixing!


svd2rust: 0.14.0 -> 0.17.0

Motivation for this change
Bring this up-to-date with the latest rust-embedded crates.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121102 at 742dcc62 run on aarch64-linux 1

1 package built successfully:

svd2rust

1 suggestion:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/build-support/rust/default.nix:144:3:
    |
144 |   meta = {
    |   ^

We just landed 0.18 in master.

I'm feeling like this package should actually be removed from nixpkgs, because 0.18 is useless until other codebases update to fix the breakage caused by that update.
The problem is that any codebase using svd2rust depends on a very specific version of it, and right now that's not even the latest 0.18, so... unless nixpkgs wants to carry all versions going forward (like svd2rust_17, etc), it's kind of pointless? tbh I'm not sure why it's even in nixpkgs, because it's pretty inappropriate to have without pinned versions of it.

unless nixpkgs wants to carry all versions going forward (like svd2rust_17, etc), it's kind of pointless?

I don't know. I never used the tool.

Does anyone agree that adding pinned version attrs would be appropriate?

I ping @astro about it


network interface precheck

Check the host network interface name is eth0 or not, if it's not the default interface name, return error and prompt user to set --interface parameter or set the interface name in Clusterfile.

I will try it.

https://github.com/alibaba/sealer/issues/182  we needn't precheck if we can auto detect network interface


Support overriding version mappings

As https://github.com/jetty-project/jetty-alpn/issues/22 shows, the OpenJDK patch version can't always reliably be used to determine which alpn boot version should be used, due to distributions backporting security fixes to patch versions rather than updating to the latest patch version. It's likely infeasible to correctly map every distributions possible version string correctly, so as an escape hatch, it would help if the agent supported an argument to override the detection, and force a particular alpn boot version to be used.

What's the point? If you need to use a specific version put it in the boot classpath.


[Enh]: Add support for DataFrame.write_parquet

We would like to learn about your use case. For example, if this feature is needed  to adopt Narwhals in an open source project, could you please enter the link to it below?
No response
Please describe the purpose of the new feature or describe the problem to solve.
I have a library which lets users ingest a pandas dataframe to a datalake. The dataframe provided to the lib by the user is converted to a parquet file (with pyarrow) before putting it in an ETL pipeline. I'd like to let users ingest polars dataframes as well via the same library and would like to use narwhals for the implementation, if possible.
Suggest a solution if possible.
For polars, nw.DataFrame.write_parquet would be the same as pl.DataFrame.write_parquet.
For pandas, nw.DataFrame.write_parquet would be pd.DataFrame.to_parquet.
If you have tried alternatives, please describe them below.
No response
Would you want to open a pull request?
no
Additional information that may help us understand your needs.
No response

hey @Priyansh121096 !
Seems like a good request to me! I think that reading data is probably out-of-scope for Narwhals - but writing, that should be in-scope

this should be available in the new version, pls let us know if it doesn't work for you, thanks!


Component: IconButton

Pre-check
This component proposal:

[x] Is not a duplicate of an existing issue
[x] Does not require 3rd party JS to implement
[x] Considers mobile-friendliness
[x] Does not cause accessibility problems

Describe the use case for this component
An icon button as a convenience component which wraps the button component but without rendering the button part. Possibly render a label next to the icon or as tooltip.
Similar to the Petal icon_button but shape could allow here to define the hover bg shape (options: rounded, square, circle) and the button's variant could be dropped for the icon_button interface.
This could be used for the theme-selector or other nav-bar items.
Demonstrate the component's API
<.icon_button icon_name="hero-cog-8-tooth-solid" tooltip="Settings" />

Yeah, I think I like this proposal. One thing to ensure is that it fully supports functioning as a link (see the source for the btn component) as well as a button. Were you interesting in putting together a PR for this?

Yes, I can work on that and put together a PR.


.tab('show') method is not properly documented

Bom

+1

Corrected description since Tabs don't have a hide method.


Add integration with Harvest.

Page tp create the access token
https://id.getharvest.com/developers


ncp: Fix handling of FCS for PROP_STREAM_RAW

The way the FCS was handled previously was based on assumptions (Like the mLength field of RadioPacket didn't include a CRC) that were incorrect. This change fixes that issue and also simplifies how the protocol handles the FCS bytes for PROP_STREAM_RAW.
This commit addresses #808.

Current coverage is 72.79% (diff: 0.00%)

Merging #809 into master will decrease coverage by 0.52%

@@             master       #809   diff @@
==========================================
  Files           107        107
  Lines         16065      17213   +1148
  Methods        2185       2390    +205
  Messages          0          0
  Branches       1916       2122    +206
==========================================
+ Hits          11778      12530    +752
- Misses         3653       4023    +370
- Partials        634        660     +26

Powered by Codecov. Last update 35ddd1a...a72db36

OS X builds on Travis are really backlogged.

In my experience, Travis OS X is really unstable and I removed OS X from the travis config a while back.  Pushing to a branch in your own fork will avoid doubling the Travis workload.

Pushing to a branch in your own fork will avoid doubling the Travis workload.

Oops. Didn't mean to do that. >_<

LGTM 👍


Update README.md

I changed the read me

And I changed the validation toml file. First I made an new version but then I realized that I just could change version2 and that the additions would be added (that prevents problems because of a new version).
However, I do not know if I have made the right pull request / changes because I see that my branch "lagerweijgr-patch-1" has conflicts.

The PR looks good. There is just one thing, since I merged my branch after you created this branch we have now a merge conflict. If you click on "Resolve conflicts" you will see that there are two versions for the _validation_schema_v2.toml.
Everything from <<<<<<< lagerweijgr-patch-1 till ======= is the content of your branch, the rest till >>>>>>> main contains the current version.
You can simple delete the rows and the markers in the browser to have a cleaned up version and then we merge.

All right. I have deleted the conflict markers, and I think it is fine.


test(hansbug): fix the problem of urlencoding in the 2021 versions

As the title said.
Related issues and merge requests

#6
#5

I think is okay, the latest version of plantuml server has been added to action's test workflow.
Thanks for the contribution of @cathiele , this version will be released as 0.0.4 soon afterwards.


Add REST API facility

Add rest api so that we can access it from other platform like Android or iOS apps

Well its somewhere in the future
But tbh that's a lot of work
Thankfully, my use of service classes would make this easier


Support for OpenVPN 2.4??

Would this script install OpenVPN 2.4, if not is it possible to add support for it?
It  is a major update with a large number of new features, improvements and fixes.

This script will install the version which is available in your repositories, including OpenVPN 2.4.
If your distro doesn't have OpenVPN officially available, you can add the official OpenVPN repos and the script will use them.


Button Issue

There is no such type of button available in materializecss like btn-success, btn-cancel, btn-info which is available in bootstrap.
To achive these we need to modify css each time.
or is there any alternate way to achive these...?

you can just give the class to button that you want
just need color of background and color of text

Success
Warn
Danger
Info

More info here http://materializecss.com/color.html

@205112067 Are you using sass? If so, you can easily extend the classes. Like so:
.btn-success {
@extend .blue, .white-text
}

Then you could use it in your html like so:
#

This would then create a blue button with white text, similar to the one that Bootstrap offers.