Always full circle

For some reason, my circles are always at 100%. This used to work, but is broken since the latest release (0.1.5)

$('.circliful').circliful();
Am I missing something?

where is you're data-percent ? see options https://github.com/pguso/jquery-plugin-circliful#data-options-attributes

Isn't that optional, because based on the documentation, the data-total and data-part will be used to calculate a percentage:

If you want to display the percentage of a value for example you have 750MB Ram and at the moment are 350MB in use. You need to set data-total="750" and data-part="350" and the circle will show the percentage value 36,85%

Seems a bit odd that I have to manually calculate the percentage again then.

can you make a demo , because i've tested locally and it works just fine :)

Here's a demo: http://jsfiddle.net/sk8fxcqb/

@modbase  somehow the CDN you're using seems to be outdated , infact if you check the source of the CDN , it has no code that calculates data-part and data-total , use https://github.com/pguso/jquery-plugin-circliful/blob/master/js/jquery.circliful.js , its the latest and works fine, for your use case.
http://jsfiddle.net/sk8fxcqb/3/

Using the master version indeed fixes the issue. I used version 0.1.5.


Failed decoding short IPFix sets

Hi,
I am using your tool to verify an implementation of IPFix by decoding IPFix payloads.
It successfully decodes in most of the cases but I came upon the following case which failed.
I have a simple set, with 1 template, with 1 field, protocol field as you can see in the following picture:

Now, when we look at the data, it has 1 set, with 2 flows:

From what I know, according to RFC 7011, this is a valid IPFix packet. No padding is mandatory, we have only 1 set.
When I decode the data, I get the following JSON:
{"AgentID":"<IP_ADDRESS>","Header": {"Version":10,"Length":22,"ExportTime":0,"SequenceNo":305419896,"DomainID":7777},"DataSets":[]}
I looked a bit in the code, and the problem seems to be in the following line:
https://github.com/VerizonDigital/vflow/blob/b7cc5a3b5454b09ff915e07d36a225cf7588689a/ipfix/decoder.go#L183
This line demands that the length of the records (flows) be at least 4 (without the set header), hence the data set is not treated by the decoder. Why is this so?
I printed the values of the variables in this case for your convenience:
Set Header ID = 261
Set Header Length = 6
d.reader.ReadCount() = 20
d.reader.Len() = 2
startCount = 16

Let me know what you think, in case there is some point from the RFC that I am missing please point me to it.

Hi,
Please, let me know what you think about this.
Thanks


How to use WinAppDriver for IOS

I am using WinAppDriver to automate the windows app and I wanted to know is it possible to run the same code for IOS?
Is there any other option for it? Can any one help me on that?

No you cannot.

Can I use Appium to test my WinappDriver workflow on IOS?

can't understand what you mean?

There's some good reads online for crossplatform testing, e.g. this one.
You would have to make platform specific changes in your test case to account for UI variations and then use Appium to relay the test.
The Appium Issues board would be better suited for cross-platform test discussion, specifically with iOS.

I am using WinAppDriver to automate the windows app and I wanted to know is it possible to run the same code for IOS?
Is there any other option for it? Can any one help me on that?

I need solution as customer is asking for cross platform


[DO NOT MERGE] Backup Tests

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

@haroldrandom please help with this PR.

Hi, @sambitratha Could you explain the purpose of this PR?
Seems not related to any issue or feature. Can I close it?


Infinite query error when getNextPageParam is not after queryFn

Describe the bug
linksQueryOptions throw a type error when getNextPageParam is not after queryFn.

How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
N/A
Tanstack Query adapter
react-query
TanStack Query version
5.28.14
TypeScript version
5.2.2
Additional context
No response

On the spot, I'm not sure what getNextPageParam depends on - but I assume that it might depend on the return type of queryFn. In the reported situation the queryFn is context-sensitive (it has unannotated parameters). If we introduce that extra change to the simplified repro above we end up with an issue too:
https://www.typescriptlang.org/play?ts=5.4.4#code/C4TwDgpgBAsiDyAjAVhAxsAPAFQHxQF4oBvAWACgoowAnAewBMBXNCALigAoBDDgZ2A0AlgDsA5gEpC+bAG4KVNHRF8mAW3ZcG3YLyjYpBfADc6QhvPIBfSxSUrgUAGZ06hKDgA0uTnRQc4JFQMHFxDfDJKKHsBKFEwJkciP2QAOlpGFghOACIciUsqFNSY9Wz4xIKKGwoKFzpOSKoM5lYOHnCoAEYAJgBmTwVo5VUNdorgTonU4DoAMSEADwgGTglB6yryOtdGodKxrgmpkQTgGfmllbWN5vpWzQ7pbv6Nqy2gA

ah got it. I remember there was an open TS issue but I couldn't find it. I think we're fine having this as a known limitation.


Updates to handle node fallback.

Previously, ethrpc was doing hosted node fallback.  This code has been moved up to the UI instead, so everything else just operates on an array of possible nodes, the UI provides the list of possible nodes to connect to.
Also adds a launch configuration for debugging tests in VSCode and fixes a minor issue in building on Windows.

Note: This should not be merged until ethrpc, ethereumjs-connect, and agurjs PRs are merged.


React Native: snapshot/screengrab support

(Issue opened by request from https://github.com/fastlane/docs/issues/626)
New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description - (Only tested Screenshot (iOS), not Screengrab (Android))
Setting up RN build/release lanes with existing guides works fine out of the box! :) (standard guides)
Having huge issues with screenshot, which was the entire reason for looking at fastlane to begin with.
Would love it if there were to be a how-to on supporting this, without introducing invisible hacks that depends on libraries like redux and therefore also react navigation with redux (which seems to be a deprecated feature). Or removing accessible features within the app.
As stated elsewhere, i added the prop testID="<name or key>" to the elements, especially those where which i would interact with. I also tried decorating it with accessible={false}.
Sometimes it says "Timestamped event matching error failed to find matching element", other times it seems to capture an element, but instead of refering to the element by the testID, it seems to create its own identifier which just contains all the text.
I think this is more of a recording issue, but since it was asked to be created as an issue here by one of the contributors, i did so.
Workaround
Its mentioned elsewhere to create a nearly invisible "button" which gets tapped, and updates the redux navigation state. By doing so, you can just refer to the same element, and tap it on each screen to go to the appropriate screen afterwards.
This might work for redux users, but not all apps use redux. And i dont believe that adding the "complexity" of redux to the app, for the benefit of trying to use this feature.
React-Navigation will also stop supporting this behavior in the next version of React-Navigation:
https://reactnavigation.org/docs/en/redux-integration.html
Workaround 2 (Have not managed to get this to work myself - but suggested somewhere)
Set accessible={false} on elements which gives you a hard time.
Applications are actually required to be accessible in Norway (and from 1.1.2019 - The entire EU).
Hacking the app, and thereby making it less accessible is therefore not a wanted operation. Neither is making this change back and forth everytime a new screenshot is to be taken.
I can see that i would be a well invested effort in the later game of any application (adding and removing accessibilty for the sake of the screenshots) - But in the early stages of the app, screenshots might rapidly change - and therefore it would be very time consuming if we were to do this "dance" everytime.
Reason for using screenshot:
Localization of app and framing w/ localized text.
Environment
Issue is not directly related to anything fastlane, as i dont get far enough in the setup.

What exactly is the problem - taking the screenshots or getting the app into the state to take a screenshot of (running the UI test)?

Recording the UI test is the actual problem. Which is why i put a disclaimer here saying:

I think this is more of a recording issue, but since it was asked to be created as an issue here by one of the contributors, i did so.

My original request was for the docs to be updated with a how-to, as i, and others, seem to struggle setting this up. As there are none, and i might have missed something.

We are very interested in supporting all kinds of apps, which is why I am asking questions and trying to understand the problem. I have never touched a React Native app before, so I might not know things.
Are you trying to follow one of our normal screenshots guides?
https://docs.fastlane.tools/getting-started/ios/screenshots/
https://docs.fastlane.tools/getting-started/android/screenshots/
https://docs.fastlane.tools/actions/snapshot/
https://docs.fastlane.tools/actions/screengrab/
If so, at which step are you currently experiencing problem?
From your above description I understand you have integrated the respective tool just fine, but are now having problems to write the code that interact with your UI, correct? The elements you want to tap are not recognized, also correct? Can you share some of the code you have right now that is not working?

Ok, such problem I do know from working with Cordova/Ionic applications. There the recording function also is pretty useless, as it just doesn't properly recognize the elements in the UI, and what it recognizes doesn't work on replay later.
I "fixed" this by learning how to use XCUIApplication with Ionic apps: giving explicit id and/or id attributes to objects and using a forceTapElement, a function I got from StackOverflow: app.buttons["close add"].forceTapElement(). That works pretty often.
Googling for "react native XCUIApplication" gives some promising results, or is this what you are/were already doing?

Heres a repro for reproducing the error in its simplest form.
https://github.com/Cnordbo/RNFailedUITesting
I could always program the entire UI navigation myself using the ID buttons - BUT, they seem to appear in different subclasses / objects (as you demonstrate when using app.buttons["close add"],  so it might be hard navigating an unknown structure. Maybe google has a few more answers there. :)

Got it working, your tip using your own setup with ionic really helped! Thanks @janpio !
I updated the repository to, hopefully, explain how to do screenshots using react-native!
https://github.com/Cnordbo/React-Native-Fastlane-Screenshot

Awesome 💃


User idle mode: fullscreen app exclusion list and/or screen detection

Use case: If a game features prominent UI elements that can't be hidden, or if a video features a static panel (like a Twitch stream overlay), I try to avoid playing or watching it on my LGTV. Thus, I often have fullscreen applications on other displays that prevent user idle mode from activating, due to my having activated its fullscreen detection. I would still like the fullscreen detection to function, however, in cases where an application is running in fullscreen on the LGTV.
To that end, I'm wondering if it would be possible to create an exclusion list for user idle mode's fullscreen exception. It would be nice to be able to select specific apps and have user idle mode turn off the transmitters even if those applications are active and in fullscreen.
Alternatively, as it would solve the same issue more elegantly, it would be similarly useful if user idle mode could detect when applications are in fullscreen on the LGTV itself and only block user idle mode in those cases.

Hi @Sithishade,
Just so I understand.   But you want the LGTV to be active while you are at the PC.
if so, yes it would be possible to create an exclusion list. Not sure how easy it would be to discover which output device the game is running fullscreen on.
Let me know if I misunderstood something. otherwise I will add the suggestion to the feature requests list

This is correct, yep! I thought of it just recently since GDQ is airing
this week. I like to watch the marathon, but there’s a big overlay on the
video that remains the same for the majority of the event. As such, I’d
prefer not to put it on the TV.
A good chunk of the time, I’m just leaning back in my chair and watching
the livestream—technically idle, but still using a fullscreen app.  I figure I can accomplish
this by adding my browser to the exclusion list for these occasions,
removing it when it becomes unnecessary.
Same goes for gaming—if I step away from my desk while playing a game on a
regular monitor, no need to have the TV keep running either. I hope that
makes sense!
On Tue, Jan 10, 2023 at 6:09 AM JPersson77 @.***> wrote:

Hi @Sithishade https://github.com/Sithishade,
Just so I understand.  But you want the LGTV to be active
while you are at the PC.
if so, yes it would be possible to create an exclusion list. Not sure how
easy it would be to discover which output device the game is running
fullscreen on.
Let me know if I misunderstood something. otherwise I will add the
suggestion to the feature requests list
—
Reply to this email directly, view it on GitHub
https://github.com/JPersson77/LGTVCompanion/issues/96#issuecomment-1377164858,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS76375NNC5Y7KOZ2LL4MGLWRVGOJANCNFSM6AAAAAATWU4PYQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yeah it makes sense. I'll see what can be done!

Check out v2.2.0 published now with this feature added. Closing this issue


MM-15579: Updates styling/behaviour of disabled team setting.

Summary
Updates team setting in group-constrained case.
Ticket Link
https://mattermost.atlassian.net/browse/MM-15579
Screenshots

Thanks @skiplist for the pull request!
Per the CONTRIBUTING.md file displayed when you created this pull request, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
This is a standard procedure for many open source projects. Your form should be processed within 24 hours and reviewers for your pull request will be able to proceed.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

Apparently your username change means you need to re-sign the CLA :rofl:


test: add retries to container-registry tests

Fixes #7715

The polling which starts on line 275 failed. Maybe we should increase that or reevaluate the backoff before running multiple times.

I added one more attempt and changed the logic to an exponential backoff method. I didn't want to add many more attempts, given that the sleep will start getting really long. Please LMK if you have any other suggestions.


Question for providing odometry

Lidarslam_ros2 is working great for us, thank you for that!
But when moving outside, there are moments, when lidarslam looses its track and especially when returning to the same point the build map is wrong. (as in picture below)
Therefore, we wanted to add odometry. When doing that, is lidarslam then relying on the provided odometry for 100% or is it just complementary

?

Adding odometry will cause the initial position for scan matching to use the value estimated by odometry.
This improves the accuracy of scan matching and reduces the likelihood of estimation failure.


HeliosDeploymentResource ctor needs to be public

Since this class (from the testing library) is meant to be used by other
projects in their tests, the constructor really needs to not be
package-private.

@rohansingh @davidxia

@negz

Current coverage is 44.97%

Merging #811 into master will not affect coverage as of 676e15e

@@            master    #811   diff @@
======================================
  Files          261     261
  Stmts        10925   10925
  Branches      1521    1521
  Methods          0       0
======================================
- Hit           4914    4913     -1
+ Partial        443     442     -1
- Missed        5568    5570     +2

Review entire Coverage Diff as of 676e15e

Powered by Codecov. Updated on successful CI builds.

:+1:


Headers is not defined

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.
Fix error "headers is not defined".
Here is the diff that solved my problem:
diff --git a/node_modules/resend/build/src/resend.js b/node_modules/resend/build/src/resend.js
index 297f53b..a6bd654 100644
--- a/node_modules/resend/build/src/resend.js
+++ b/node_modules/resend/build/src/resend.js
@@ -10,6 +10,8 @@ var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, ge
 };
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.Resend = void 0;
+const fetch = require('node-fetch');
+const { Headers } = fetch;
 const render_1 = require("@react-email/render");
 const package_json_1 = require("../package.json");
 const api_keys_1 = require("./api-keys/api-keys");

This issue body was partially generated by patch-package.

Unfortunately, Node.js 16 has reached End-of-Life [1], and only Node 18 is supported by this package [2].
[1] https://nodejs.org/en/blog/announcements/nodejs16-eol
[2] https://github.com/resendlabs/resend-node/blob/main/package.json#L10-L12


26 pins socket pinout

Very good, but I want to direct use 26 pin socket interface.
Could you provide pinout for it?

Want to make it good, do it youself.

But I could not figure out A, B, C, D sensors.

But I could not figure out A, B, C, D sensors.

I did some tests, and I think it's (OUT1+OUT8)-(OUT2+OUT7)

I made experiments and it seems to be wrong pinout.
FES signal is violet, Green is differential RF, RED is head vertical position.
Compare with PHR-803t output here:
https://github.com/GaudiLabs/OpenLaserScanningMicroscope/issues/3

A,B,C,D are in in-phase and it is wrong.

Still have no idea. OUT1-4 are almost the same, OUT5-8 shifted by about 60 units from each other.
Phases are the same.

All eight signals + RF + Focus calculated as
OUT2 + OUT3 - OUT4 - OUT5;
Still no ideas

The only way to find out might be to point an OPU directly at the PDIC and see how the laser affects different quadrants.

@Kabron287
Thank you for your contribution!
I could not analyze the 26-pin terminal. Thank you very much.

I made experiments and it seems to be wrong pinout.
Did something go wrong with the documentation? If you can teach me the correct way to write it, I will apply it to the document.

All eight signals + RF + Focus calculated as OUT2 + OUT3 - OUT4 - OUT5; Still no ideas

Someone here: https://forum.hackteria.org/t/laser-optical-pickup-unit-hacking/771/58 had a very similar issue. They said that increasing the laser power seems to solve the problem, and they get a 500mv peak-to-peak output from the A-D pins.

there seems to be a laser driver circuit in the SF-HD65 datasheet:

It seems that the laser diode needs a reference voltage, not more power.

I increased the laser power to 50ma, and now the difference between the RF pins is ~500mv without any amplification just from focusing by hand. Seems promising. I can't measure the FES yet, as the peak-to-peak voltage of the A-D inputs are far higher than before, so my amplifier gain is too much.

Alright, I've finally got the FES

pins: (OUT7+OUT1)-(OUT8+OUT2)

Great!

The linked FFC conversion adapter (aliexpress) is not the right size.
This is the listing I got in Q1.24 that works (search by keyword if listings are gone):

10Pcs 0.5MM FPC FFC Flexible Flat Cable A/B Type 50/100/150/200/250/300mm 10P 12/15/16/18/20/26/28/30/32/36/38/40/45/50/54/60PIN (aliexpress link - I took one with length: 20mm, thickness: 0.5mm, 26 pin, A-type (same) - €3.03 with shipping to EU)
FPC FFC Adapter Board 0.5mm 1.0mm To 2.54mm Connector Straight Needle And Curved Pin 6 8 10 12 20 24 26 30 34 40 50 60 80 Pin (aliexpress link - I took 0.5MM-26P - €2.55 with shipping to EU )
New Slim Laser Lens Hop-150X Hop-15XX Replacement G2R2 DG-16D4S For Xbox 360 (aliexpress link - €5.70 for 2 pcs with shipping to EU)

I recommend "926 0.01mm Microscope Slides Reticle Calibrating Slide Ruler Cross Microscope Calibration Ruler Stage Micrometer" from alix as well, for testing.

The linked FFC conversion adapter (aliexpress) is not the right size. This is the listing I got in Q1.24 that works (search by keyword if listings are gone):
* 10Pcs 0.5MM FPC FFC Flexible Flat Cable A/B Type 50/100/150/200/250/300mm 10P 12/15/16/18/20/26/28/30/32/36/38/40/45/50/54/60PIN ([aliexpress link](https://www.aliexpress.com/item/1005004140412156.html) - I took one with length: 20mm, thickness: 0.5mm, 26 pin, A-type (same) - €3.03 with shipping to EU)

* FPC FFC Adapter Board 0.5mm 1.0mm To 2.54mm Connector Straight Needle And Curved Pin 6 8 10 12 20 24 26 30 34 40 50 60 80 Pin ([aliexpress link](https://www.aliexpress.com/item/1005005790776581.html) - I took 0.5MM-26P - €2.55 with shipping to EU )

* New Slim Laser Lens Hop-150X Hop-15XX Replacement G2R2 DG-16D4S For Xbox 360 ([aliexpress link](https://www.aliexpress.com/item/1005001298991688.html) - €5.70 for 2 pcs with shipping to EU)

I recommend "926 0.01mm Microscope Slides Reticle Calibrating Slide Ruler Cross Microscope Calibration Ruler Stage Micrometer" from alix as well, for testing.

I documented my schematics, code, etc for my LSM here: https://github.com/NilanEkanayake/LaserScanningMicroscope
It's not a full-featured solution yet though, lots of bugs and very basic software. I recommend looking through the schematics for parts used and ideas instead of directly following it. I do have a functioning version 3, but it has a noise issue on ADC5, caused by PWM X, which is on the opposite side of the PCB. Drove me nuts so I started a different project and forgot to finish it. Oops.

Version 1 works great, but has the wrong FFC connector on the PCB (had to manually replace) and a bunch of debug stuff. Refer to version 2's schematic for the right one. Can't remember if I updated V1 with the new FFC, so best to stay on the safe side.

Version 1 works great, but has the wrong FFC connector on the PCB (had to manually replace) and a bunch of debug stuff. Refer to version 2's schematic for the right one. Can't remember if I updated V1 with the new FPC connector, so best to stay on the safe side.

Fantastic, thanks for the effort and sharing! (to kototoibashi and others as well)
Might take me a while to get back on this but will try to iterate on it.

Version 1 works great, but has the wrong FFC connector on the PCB (had to manually replace) and a bunch of debug stuff. Refer to version 2's schematic for the right one. Can't remember if I updated V1 with the new FPC connector, so best to stay on the safe side.

Fantastic, thanks for the effort and sharing! (to kototoibashi and others as well) Might take me a while to get back on this but will try to iterate on it.

I have a huge amount of local documentation (mostly rambling) that has basically every detail of building the LSM, so if you have any questions, don't hesitate to ask, I should be able to answer them.


PKCE support, better handling of expired tokens and some minor improvements

This PR implements PKCE support, as discussed on the Google groups. It also improves the handling of expired access tokens. The new StateValidator interface is replaces by ValueRetriever and used for the PKCE implementation. As this PR implements several enhancements, it's best to review the commits one by one.

I did some minor cleanups and fixed the last remaining tests to make the build pass.

@papegaaij is the PR ready for review?

It looks good to me. Did you test it with and without PKCE and state?

@leleuj Our IdP supports PKCE and the current implementation does not allow disabling PKCE when the IdP supports it (null means autodetect). I can add a boolean flag to disable PKCE entirely if needed, but personally I would never disable PKCE when the IdP supports it, because it is highly recommended to use it. I did run quite a few tests with our test suite, with different configurations and different flows. That's how I found the NPE and noticed the state parameter with 'withState' set to false.

Yes, please add a flag enabled by default but which allows to disable PKCE. Thx

I've implemented it the other way around, rather then enabling PKCE, you can disable it. I think this makes more sense. Especially when the IdP does not support PKCE it would not have been clear what the behavior would have been if pkce was enabled.

Btw, I did test without PKCE, but didn't notice it :) My stub IdP does not support PKCE, so I can confirm this works as expected, the parameters were not added.
The nice think about PKCE is that the client only needs to add certain parameters. You can even add these parameters when the IdP does not support PKCE, they will simply be ignored. All validation is done on the side of the IdP. In fact, when using PKCE, both the nonce and state add very little value. PKCE is much stronger.

Excellent! Will merge. I'll make some tests today and release tomorrow or the day after tomorrow.


Roadmap: Specify scope of OTAR2-048

The OTAR2-048 project will provide data on protein function and how variants (potentially) affect protein function. Slides from the February 2019 project meeting can be found here.
Next steps:

[ ] Define fields in summary of normal protein function (meeting on Feb 05, 2019)
[ ] Correct info on slides 3 & 5 relating to data from IntAct and the Complex Portal (meeting on Feb 05, 2019)
[ ] Define summary for variants that (potentially) affect protein function
[ ] Define minimal information to specify a variant
[ ] Assess list of variants that can be provided by OTAR2-048 (How many of the proteins and how many of the variants are associated with diseases in Open Targets?)
[ ] Assess coverage of variant-disease and protein-disease associations that could be provided by OTAR2-048
[ ] Assess protein complex lists from Protein Portal, ChEMBL & PDBe (meeting on Feb 05, 2019)

The structure of the JSON documents is under development here.


Create project with components

This PR contains the Setup of the Bookstore web app.

Highlights:

Create React app
Setup gitflow
Add Books component
Add Categories component
Add Routing
ReadMe description
Linters
etc

Hi @roshan-bajgain, thanks for approving my PR. 🙏🏾


Revert "Make jenkins e2e runs reuse one SSH key."

Reverts GoogleCloudPlatform/kubernetes#7990

This broke things. Amazingly.


missing Microsoft.NET.CoreRuntime.1.1_1.1.25305.1

need to get sos.dll from this package because Windbg says versions of coreclr.dll and sos.dll does not match, so I need to find that sos.dll. and sos.dll does not exist in C:\Program Files\WindowsApps\Microsoft.NET.CoreRuntime.1.1_1.1.25305.1_x64__8wekyb3d8bbwe\ .

PTAL @lt72

@lt72 I need your help, Thanks.

@mikem8361 PTAL


[SILVerifier] NFC: Actually verify all BB predecessors/successors

This verifier has been broken since its inception four years ago.

@swift-ci please smoke test


download-artifact should only select major version

Codecov Report

Merging #526 (c2f7f79) into main (0d3fbf8) will decrease coverage by 54.35%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #526       +/-   ##
=============================================
- Coverage     68.96%   14.61%   -54.36%
- Complexity        0       32       +32
=============================================
  Files             9       40       +31
  Lines           261    13007    +12746
  Branches          0     2035     +2035
=============================================
+ Hits            180     1901     +1721
- Misses           67    10828    +10761
- Partials         14      278      +264

Impacted Files
Coverage Δ

go/okapi/didcomm.go

go/okapi/hashing.go

go/okapi/oberon.go

go/okapi/native_call_windows.go

go/okapi/ldproofs.go

go/okapi/didkey.go

go/okapi/metadata.go

go/okapi/native.go

go/okapi/native_call.go

...src/main/java/trinsic/okapi/metadata/Metadata.java
6.17% <0.00%> (ø)

... and 39 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Leverage GDScript 2.0 features to make scripting more robust

E.Run() implementation made its way into Popochiu to avoid the convolutions of yielding the execution of coroutines and processing the necessary signals.
Godot 4.0 will introduce a new version of GDScript with the very convenient await keyword. The syntax still involves starting a coroutine then await for the signal (see https://www.reddit.com/r/godot/comments/sbhvmh/godot_40_await_function/), but  Popochiu's API functions can serve some syntactic sugar to allow something like:
await C.Say("Player", "I guess the game will wait for me to finish this Nolan-inspired line of dialogue...")

Put like that, having blocking functions return the proper signal should suffice, but it may require a pervasive redesign of the public framework API. That's why this issue is marked as epic.

Finally... the release of v2.0-alpha1 handles this.


feat: random kademlia walks

Why

Resolves #73
What

add network_config.kad_walk_interval (defaulting to 300 seconds / 5 minutes)
add timer to trigger random kad walks in service.rs

Demo
(for the demo, lowered the delay to 1s just to grab a screenshot quickly)

Checklist

I have made corresponding changes to the tests
I have made corresponding changes to the documentation
[x] I have run the app using my feature and ensured that no functionality is broken

cc @mxinden continuing the conversation from https://github.com/fleek-network/ursa/pull/343#issuecomment-1406789107
https://github.com/fleek-network/ursa/blob/c4f3d832dc7737dceec5d3e8de227b98b329dab9/crates/ursa-network/src/service.rs#L949-L951
In this pr I used get closest peers to a random peer id, whereas you previously suggested to use bootstrap() at an interval. Depending on the implementation, I've seen both kinds used, I'm curious if there's any real difference or benefit from using bootstrap directly for the walk

Change looks good to me.

@mxinden continuing the conversation from #343 (comment). you suggested there to use bootstrap() at an interval, whereas in this pr I used get closest peers to a random peer id as seen here:
https://github.com/fleek-network/ursa/blob/c4f3d832dc7737dceec5d3e8de227b98b329dab9/crates/ursa-network/src/service.rs#L949-L951
Checking out several other implementations, I've seen both flows used interchangeably to keep the routing table fresh. I'm curious if there's any real difference or benefit from using bootstrap directly for the walk?
And of course, as always really appreciate the reviews and feedback! pray

A random walk does a single DHT lookup. A bootstrap call does one lookup per bucket.
Unfortunately I don't have any data on which of the two should happen periodically. Ultimately you are trading resource usage (periodic lookups) for low-latency (due to up-to-date routing table). Until we have more data, I suggest doing the cheaper operation, i.e. a random walk as you do in this pull request.


build-clients: add contracts.cargo-workspace shortcut

In our example environments.toml file, we say in development and testing environments, you can do this:
[development.contracts]
# Auto-build, -deploy, -bind, and -import all contracts in Cargo workspace
# Only supported in development & test environments
cargo-workspace = true

The initial implementation of the build-clients logic in #42 did not support this. You need to explicitly list each of the contracts.
Design questions
development.contracts currently specifies a vector of contracts. This would change one of them to be a special, reserved string, "cargo-workspace". This means you would not be able to have a contract named cargo-workspace, which—maybe that's fine? Seems an unlikely contract name. And also, the actual contracts specified here don't work if you use dashes. The generated wasm files use underscores, and you need to match those. But maybe that's a bug? We probably wouldn't want cargo-workspace to be the reserved word and cargo_workspace to refer to an actual contract.
All this to say: maybe we don't want the reserved word. Maybe instead we:

Just always assume you want to generate clients for all workspace contracts, if you have an environments.toml file.
Add a different key, like development.contracts-from-workspace = true.
A combination of the two. Make development.contracts-from-workspace default to true, but allow overriding to false. Is this unnecessary at this point?

I personally lean toward the first approach. We could add the contracts-from-workspace flag later, if we discover situations where it would be useful to have an environments.toml file and not build clients for all workspace contracts.

IMO I like the simplest option here which is to just auto build clients for all workspace contracts. Like you said, if there are use cases for not doing so we can add a flag later.


Export color coded Excel

Problem
when upgrading, I have been asked to go in and turn on & off the different modules to see what is broken / conflicting .... and Keeping track of that is a ... challenge when I have 85 active modules :-)
Solution
Would be great to have a way to keep track of the testing, makes notes etc ...
My suggestion would be to make it exportable to excel or google sheets ... with the colors in the list ... then I could add a column for status or make notes about errors etc
Alternatives
No response
Context
No response

You could just use the source Google Sheets document that this is pulling data from.


Update CI

Fixes #136
Changes made in this Pull Request:

Updates to miniforge/miniconda instead of mambaforge

PR Checklist

[ ] Tests?
[ ] Docs?
[ ] CHANGELOG.md updated?
[ ] AUTHORS.md updated?
[x] Issue raised/referenced?

Thanks for the review @IAlibay, once CI goes goes green (fingers crossed) I'll merge.


Support activating pipelines in an alternate namespace

There is a desire to have the collection-level resources (ie pipelines, tasks, etc) deployed in a separate namespace from the rest of Kabanero.  Consider the following proposed yaml:
apiVersion: kabanero.io/v1alpha1
kind: Kabanero
metadata:
  name: kabanero
spec:
  version: "0.3.0"
  targetNamespaces:
  - ns1
  - ns2
  pipelinesNamespace: kabanero-build

Note the new pipelinesNamespace attribute (name subject to change, and also cardinality, but lets go with this for now).  When activating the collections, the resources would get created in this alternate namespace.  If pipelinesNamespace were not specified, we would continue to activate in the current namespace (kabanero in this case).
It's not clear whether the collection itself should be activated in the current (kabanero) namespace or in the pipelines namespace.  For now lets assume activating in the current namespace.  If it's activated in the pipelines namespace, then the CLI services will need to change to watch/create kind: Collection instances in the pipelines namespace rather than the current namespace.  The kabanero-operator already sets up an environment variable to tell the CLI service what namespace to watch, and it may be as simple as just changing that to a new value, but that also may have un-intended side effects on the CLI, and also would probably require a new role / cluster role, to allow the CLI to search and create kind: Collection objects across namespaces.

@stephenkinder Can we get a clarification please - would you prefer:

Create the Collection instances in the kabanero namespace, and then create the pipelines/tasks/etc in pipelinesNamespace
Create both the Collection instances and the pipelines/tasks/etc in pipelinesNamespace

I don't know if there are long-term benefits from doing one over the other.

@dacleyra has been working thru some of the issues here, and I wanted to write some of this stuff down because it's going to affect other components (potentially).  First, there were some questions about the service accounts and roles now, which becomes complicated because you have namespaces where the pipelines are allowed to create applications, as well as namespaces where the pipelines are allowed to be in the first place.  Things to keep in mind:

kabanero-pipeline-role is currently a ClusterRole, established in the install script.  I think this can stay that way.  This role provides the permissions that a PipelineRun needs, to build and scan an application.  We could move the creation of this cluster role to the kabanero controller, but if we do this, we also need additional logic in the finalizer to remove it when the kabanero instance is deleted, since ClusterRole is a cluster scope object that can't be owned by a namespace-scoped object.
kabanero-pipeline service account is created in the install script, in the kabanero namespace.  The namespace should change to the pipelinesNamespace.  This means the service account must be created by the kabanero controller.  Since the service account is likely created in another namespace, it will require a finalizer change to clean it up when the kabanero CR instances is deleted.
kabanero-pipeline-cluster-role-binding is a ClusterRoleBinding established in the install script.  Since this is tied to the service account kabanero-pipeline, and since the namespace of that service account is now variable, the kabanero controller will need to create this, as well as a finalizer hit to clean it up.  Now, I don't see why this can't be just a RoleBinding but we'll need to find out from @kvijai82 if cluster scope is really necessary.  In either case a finalizer hit is required, because it can't be owned across namespaces.
kabanero-pipeline-deploy-role is currently a ClusterRole, established in the install script.  I think it can stay that way, but if not, see 1) for an explanation of what would need to be changed.
kabanero-pipeline-deploy-role-binding is currently a RoleBinding established in each of the targetNamespaces namespaces, and linked to the kabanero-pipeline service account in the kabanero namespace.  The namespace would now be variable, since the kabanero-pipeline service account is now established in the pipelinesNamespace namespace.  This should be a minor change to targetnamespaces.go to read the pipelinesNamespace from the Kabanero CR instance, and make the substitution in the template.  Since the object might now be created in a different namespace, we have another finalizer hit here.
kabanero-trigger-role is, I think, not relevant here since the stack controller uses it, and the stack-controller SA and namespace are not changing.

After these changes, someone using the tekton dashboard to establish a GitHub webhook would look to the pipelinesNamespace to select the pipeline.  the PipelineRun would now run in this namespace.  The following problems may occur:

The run will attempt to locate the Stack CR instance to determine the stack image name / tags.  Today, the Stack CR instance will always be in the kabanero namespace.  We'll need to look at these tasks and see if they are explicitly looking in the kabanero namespace, or are looking in the current namespace.  If the current namespace, we'll need to change to look in the kabanero namespace.  Long-term, when we support moving the Kabanero and Stack CR instances out of the kabanero namespace, we'll need to come up with a way to tell the PipelineRun what namespace it should use to look up the Stack CR instance.
The run will attempt to locate the Kabanero CR instance to determine the governance policy.  Again, today the Kabanero CR instance will always be in the kabanero namespace.  If it's hard-coded, great, but if not, we'll need to change that.  Long-term, we'll need to figure out how to tell the PipelineRun what namespace to use to look up the Kabanero CR instance.
I have no idea what impact this is going to have on kabanero-eventing.  This may be the show-stopper for us... we'd have to teach eventing how to find the pipelines in the pipelinesNamespace.

I don't like having a default pipelinesNamespace - I think we should use the control namespace kabanero for now, as we do today.  That way the short-term repercussions of this change are minimal to nil for users who don't choose to code a pipelinesNamespace in their Kabanero CR instance.
I think that the kabanero controller should be responsible for establishing all of the roles and bindings, since the Kabanero CR instance has the namespaces coded into it.  If we push the namespaces down to the Stack CR instances, that leaves the possibility that someone codes different pipelines namespaces into manually created Stack CR instances, and then we potentially end up with a mess (although it might be a convenient mess for someone who wants to do things in a very particular way).  I think having all of the permission/control information in the Kabanero CR instances is easier to understand.  I am open to other suggestions though.
Dan mentioned that as of right now, the kabanero operator is namespace-scoped, and so if we create pipelines and tasks in another namespace, we won't be able to watch these and re-create any that are deleted.  Once we change to be a cluster-scoped operator (see #284 ) this will be possible.  I mean, it's always possible that we can do some off-label thing like create a second client in the stack controller pod which is capable of watching another namespace, and then feed reconcile requests back into the reconciler somehow, but I don't think that's necessary.  For now, if someone codes pipelinesNamespace, we just acknowledge that we can't watch the resources, and that some day in the future we'll be able to do it.  Again I'm open to other suggestions here.
That's everything I can think of ATM.  It's likely that we can move this along to a point, and then have to stop to work thru more design issues (particularly with eventing), and that's fine.

Another approach worth considering is to support a matching pair of namespaces - myapp for deploying and myapp-build for pipelines.


Add "Blazor Page" template to VS templates for 'Add New' dialog in VS

Not an urgent requirement, but a "Blazor Page" template would be nice in the "Add New" dialog in VS.
At present I just copy existing pages and rename them.

You mean ItemTemplate

as of now i do Add New Item > Razor View in VS ... :)

Duplicate of #23


DOCK-2533: fix regex errors in Edit Info dialog

Description
This PR fixes the regex errors showing on Firefox when opening the "Edit Info" dialog in the My Tools page.
These errors show up on FireFox is because they use v mode - hence the trailing /v on the end of the regex patterns in the errors. This v flag is stricter than the u flag and required me to escape the characters.
Also edit the version with an invalid path to verify that the regex still works properly

Issue
https://ucsc-cgl.atlassian.net/browse/DOCK-2533
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that your code compiles by running npm run build
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[x] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[x] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[x] Do not use cookies, although this may change in the future
[x] Run npm audit and ensure you are not introducing new vulnerabilities
[x] Do due diligence on new 3rd party libraries, checking for CVEs
[x] Don't allow user-uploaded images to be served from the Dockstore domain
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.
[x] Check whether this PR disables tests. If it legitimately needs to disable a test, create a new ticket to re-enable it in a specific milestone.

Could you please add a brief summary why the changes were necessary to the PR "Description"?  If you have links to the appropriate docs, that would be great.

Could you please add a brief summary of why the changes were necessary to the PR "Description"? If you have links to the appropriate docs, that would be great.

Added some explanation in the description but please let me know if it is confusing.

Could you please add a brief summary of why the changes were necessary to the PR "Description"? If you have links to the appropriate docs, that would be great.

Added some explanation in the description but please let me know if it is confusing.

That explains it, thanks!
Some of the other regexps (repoNameWithSlashesImagePath and privateAmazonImagePath) look like they might include slashes in the character classes, do we need to modify them, too?
I wonder if we should add a test that attempts to use all of the regexps in v mode, so we can detect problems before we deploy...

Added some tests. Should I add more?

Maybe a test that checks that each value in validationDescriptorPatterns is valid in v mode?  Something like:
    for ([name, pattern] of Object.entries(validationDescriptorPatterns))
        new RegExp(pattern, 'v');
    }

(Note that the above might not be the best Typescript, and might be good to tweak so that if a pattern fails, we know which one.)
Curious what others think.


[MRG] support mle report <org/repo> command

closes: https://github.com/MLSysOps/MLE-agent/issues/164
checklists

[x] support mle report cli
[ ] add fetch github metadata api (move to another PR)

$ mle report MLSysOps/MLE-agent

@leeeizhang Please update readme accordingly


Combine data from Registration Info with data from other sources

When LTE data is missing in new APIs (e.g. Pixel 7 in NR NSA) a developer has to choose between LTE without frequencies (from cell location) or LTE without signal (from registration information).
I tried to overcome that, with two approaches:

Merge AllCellInfo and RegistrationInfo right after postprocessing. So data from registration info can be combined with LTE signal from Cell Location.
Get LTE Signal from Signal Strenght source and combine it with data from registration info (in NR NSA)

An alternative approach would be to merge  RegistrationInfo and AllCellInfo before Signal Strenght Postprocessor

After a some testing Signal Strength source didn't turn out to be so reliable, it seems to stop updating LTE after 5G connection. So I'll close this


Embedded links in obsidian is not exported

Describe the bug
Embedded links in obsidian is not exported, i'm using the feature below in obsidian. And I expect to export this feature in webview

Operating System
plugin version 1.7.3
obsidian version 1.4.14
To Reproduce
Steps to reproduce the behaviour:

write ![[source.md#heading1]] in main.md
write ![[source.md#^e69785]] in main.md
export to webpage via the plugin
nothing is exported in the html

Screenshots
If applicable, add screenshots here to help explain your problem (just copy paste)
here's the original form in markdown file in obsidian

here's the web view

IMPORTANT: Error Log

Please open the developer console using (Ctrl + Shift + I), and clear the console using the button at the top left corner.
Reproduce the bug
Take a screenshot orcopy the error from the console if it has any output and paste it here

Hi thanks, this is a duplicate of #207 so I will close this in favor of that issue. However, this problem will be fixed in the next update

Hello KosmosisDire,really glad to know that. Thanks for your reply.


sendToBridge invalid

I don't understand why sendToBridge is used in setTimeout, and onLoadingFinish onLoadingStart onLoadingError is not valid.
Do you have a detailed documentation?
componentDidMount() {
    this.refs.webviewbridge.sendToBridge('message');  //invalid
    this.refs.webviewbridge.onLoadingStart(()=>{});   //invalid
    this.refs.webviewbridge.onLoadingFinish(()=>{});  //invalid
    this.refs.webviewbridge.onLoadingError(()=>{});   //invalid
    setTimeout(() => {
        //Why use delay？
        //Delay time can not be determined
        //Can there be a callback function, tell me to be able to use the correct sendToBridge
        this.refs.webviewbridge.sendToBridge('message'); //effective
    }, 1000);
}

@alinz  i realy need help.

@TOP-Chao, one thing you should know is that, you can't send a message from react-native to webview at the beginning. The reason for that is we don't know when the page is loading on WebView. You might have a slow connection. So what you should do is sending a message from WebView to react-native first to tell native side that you program has already been loaded and executed successfully.
So don't try to send a message from componentDidMount to WebView.
It is a good practice to start the conversation from the WebView to Native side.

@TOP-Chao I have changed a couple of part of it, would you try it again with new version 0.20.0 and reopen this ticket if it happens again.


the player can't resume

hello, I working with your player a while, currently I got an issue, if streamer got a network problem in short time (such as switching from wifi to 4g or vise vera ) the player goes into the buffering state, after a while it goes to playing state or even ended state, in both cases the viewer is frozen.
If I implement a mechanism to retry, I got this error **com.amazonaws.ivs.player.PlayerException: Segment : ERROR_NETWORK : 404 : Segment download http error** until 1 minute later.

Hi,
Could you provide more details about your retry mechanism? If you restart the stream by calling load() and play() on the player once the broadcaster has resumed broadcasting the stream I would expect the stream to resume as normal.
We are also actively working on automatic network recovery in a number of situations and hope to deliver this in an upcoming release.

Hi,
Could you provide more details about your retry mechanism? If you restart the stream by calling load() and play() on the player once the broadcaster has resumed broadcasting the stream I would expect the stream to resume as normal.
We are also actively working on automatic network recovery in a number of situations and hope to deliver this in an upcoming release.

hi @iannparker thanks for you response.
I listen for the state Player.State.ENDED then I postpone in a short period of time before calling my own retry mechanism.
I tried a number of differences of delayed time (10s, 20s, 30s, 40s, 50s, 60s)
I tried both
player?.play()
and
player?.load(Uri.parse(url))
player?.play()

I realized that only the second one works after 60s of delayed time.

hi @iannparker thanks for you response.
I listen for the state Player.State.ENDED then I postpone in a short period of time before calling my own retry mechanism.
I tried a number of differences of delayed time (10s, 20s, 30s, 40s, 50s, 60s)
I tried both
player?.play()
and
player?.load(Uri.parse(url))
player?.play()

I realized that only the second one works after 60s of delayed time.

Hi @linhphan534 - it sounds like you got it working, but if you need further support on this topic, could you please file a ticket in the AWS Support Center so we can take a deeper look at your broadcasts? Thanks!

Hi @linhphan534 - it sounds like you got it working, but if you need further support on this topic, could you please file a ticket in the AWS Support Center so we can take a deeper look at your broadcasts? Thanks!

hi @maxstoller thank you so much for the response.
actually, my problem haven't solved yet, some time after host gets the connection disconnected then resume, the ivs player at viewer side change state from buffering ---> playing but the screen is still freezed.

hi @maxstoller thank you so much for the response.
actually, my problem haven't solved yet, some time after host gets the connection disconnected then resume, the ivs player at viewer side change state from buffering ---> playing but the screen is still freezed.


TDT23

Tracking

Bug Report Dump (Auto-generated)

Version 1.19.1<PHONE_NUMBER>)
Device: iPhone 7 (iOS 11.3)
TestFlight: false

🤔
Sent with GitHawk


License file is missing

You project misses a license file. Could you add one please? For guidance about how to choose an open-source license refer to e.g. here https://choosealicense.com/ (license overview).

Thanks for mentioning this, A MIT LICENSE is now added to the project.

The package.json is missing the license as well :wink:

Just added the license to the package.json as well.


Loading spinner never leaves

Loading spinner is not hiding after img loaded.
Also, spinner parameters is not working too

Could you please share your code with me so I can try to reproduce this? Also, what do you mean by "spinner parameters is not working" ? what parameters?

i mean the using of the attribute spinner="false" do not work and
imageLoaderConfig.enableSpinner(false); not working too;
i'll try to reproduce in a fresh project to share with u, i'll back soon.
tks

@cubissimo please try using the spinnerattribute like this in your markup:
<img-loader src="{{ speaker.headshot }}" useImg [spinner]="false"></img-loader>

@tabirkeland I can confirm now! It's work!
I end up handling a spinner outside img-loader, encapsulating in a custom element.
Is there a some kind of output OnLoad event to listen?
If not can i open a feature request?

@cubissimo not tested but you should be able to do something like so:
<img-loader src="{{ speaker.headshot }}" useImg [spinner]="false" (load)="imageLoaded()"></img-loader>

and then in your page controller:
export class MyExamplePage
{
    public imageLoaded() {
      // do something
   }
}

Perfect! i was checked the source code looking for this but missed! sry!
Tks! I'm closing this issue


React & Redux group project: set up your Kanban board

In this milestone We @Santosh-Konappanavar @ritikarawat220 ,

We have created a Kanban board for react capstone project and distributed the task to our team as below
Kanban board

Hi @Santosh-Konappanavar and @ritikarawat220,
Status: Approved ✅
Your project Kanban board is all set up!  There is nothing else to say other than... it's time to start implementing your project :shipit:
Congratulations! 🎉

Good Highlights✔

Tasks are well assigned
Kanban board well set up

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Add unit test for bitset

Signed-off-by: liliu-z<EMAIL_ADDRESS>Issue: #253
This PR did:

Add bitset unittest for DiskANN
Add a config for range search to allow user set the ratio of search list size and k. Before this change the default value is 1, much make recall too low.
Filter the -1 in range search result. (-1 is from KNN search, when the result is not enough, KNN search will fill the ids with -1).
Format the unittest for DiskANN

/lgtm


browserify errors if jquery.mousewheel is not in node_modules

When including dist/js/select2.js, browserify fails upon reaching line 5328 due to jquery.mousewheel not being present in node_modules/ for select2.

Still need to do some testing here to see if we can just change the word require (local variable) to something else, as it doesn't look like Browserify is looking at the syntax tree at all.

+1

+1
Why doesn't select2 just include jquery-mousewheel as a dependency in the package.json file??

Why doesn't select2 just include jquery-mousewheel as a dependency in the package.json file??

jquery-mousewheel is an optional dependency, which is surprisingly difficult to do with browserify. Unlike most module loaders, browserify does not allow modules to be loaded on the fly.

If it's optional because jquery-mousewheel is a shim, then it must be decided if Select2 wants to handle the shim or let the developer handle the shim. A package shouldn't have an optional dep. The way I see it, there are two options:

Let the developer add the jquery-mousewheel package to his project, and pass this off to Select2 under some kind of configuration. This option is basically saying that Select2 isn't concerning itself with shims/polyfills.
Require the jquery-mousewheel package as a dependency in Select2 package.json. This is saying that Select2 uses the jquery-mousewheel package as a shim/polyfill when it's needed, and so it is required to be bundled with it. Select2 can still be smart on when it uses the jquery-mousewheel plugin (using feature detection and whatnot).

The first one is better if you want to keep Select2 more lean and focused (unix-philosophy-like), but the second option is certainly easier on the developer.

I think it should be an explicit dependency too.
jquery.select2.js contains:
define([
  'jquery',
  'require',

  './select2/core',
  './select2/defaults'
], function ($, require, Select2, Defaults) {
  // Force jQuery.mousewheel to be loaded if it hasn't already
  require('jquery.mousewheel');

The requirejs docs explicitly state on http://requirejs.org/docs/errors.html#notloaded:

In particular, the following will not work:
//THIS WILL FAIL
define(['require'], function (require) {
var namedModule = require('name');
});
This fails because requirejs needs to be sure to load and execute all dependencies before calling the factory function above.

+1

+1
I hope it will be finally resolved soon...
Any plans to make library commonjs, amd compatible without the need of these hacks mentioned above?

+1

+1

+1

+1

+1

+1

+1

This should have been fixed by https://github.com/select2/select2/commit/8edf3c64082be59b9506f3ad6dd84073b6eb5841.


Building blinky sample program goes wrong

I have followed https://docs.zephyrproject.org/2.2.0/getting_started/index.html guide in order to
download zephyr.
On step 6.2 - west build -p auto -b  samples/basic/blinky
(I put esp32 although I do not have the hardware yet. just trying to build the program)
I was excepting the build to go right but instead, I'm getting this error message (screenshot ):

Environment:

OS: (Linux VM on windows host)
Toolchain (Zephyr SDK)
Zephyr version: 2.2.99

Zephyr SDK does not support building the ESP32, for that, you need to download the toolchain from espressif and setup the toolchain according to the board documentation.

@nonopx Here is some documentation with that info for the ESP32 board in Zephyr - https://docs.zephyrproject.org/latest/boards/xtensa/esp32/doc/index.html
Check out the https://docs.zephyrproject.org/latest/boards/xtensa/esp32/doc/index.html#system-requirements

Thank you very much


CID为负数，无法断开rtmp推流

get http://localhost:1985/api/v1/streams
结果：{"code":0,"server":49635,"streams":[{"id":49640,"name":"livestream","vhost":49636,"app":"HDxzzKjQGWT0TYKc9jsgiJNBhg41gzXuUVOtoR62yU0rl4pavDHwMQAGYhixSIJRajUBWaffDx3MDGq9wN8QQEtN19GCpUHjRSWrznSn4GPk5cm64jte6kNT8b4Ia0Zo/live","live_ms":1578883698442,"clients":1,"frames":25177,"send_bytes":3984,"recv_bytes":147834247,"kbps":{"recv_30s":1073,"send_30s":0},"publish":{"active":true,"cid":-38},"video":{"codec":"H264","profile":"High","level":"3.1","width":1296,"height":512},"audio":{"codec":"AAC","sample_rate":44100,"channel":2,"profile":"LC"}}]}
delete http://localhost:1985/api/v1/clients/-38
结果：{"code":2049}
单台电脑上测试

cid是负数的情况下好像就没办法断开，请问你后面有解决这个问题吗？

Check it.

Fixed, 4.0后CID为字符串。


\big/ \Big/ \bigg/ \Bigg/ don't work anymore in Firefox

I see this output:

But I think it used to work in Firefox (it never worked in Chrome though).
Firefox 131.0.3, Ubuntu 24.04

I agree that it has never worked in Chrome. Row184 in the Temml Wiki Test has always been a problem. Until recently, I was more concerned with rows 178 & 179, which also displayed Chromium errors. But that Chromium bug has been fixed and now is a good time to focus on row 184.
The source of the problem is that the MathML Core operator dictionary does not give any solidus-type character the stretchy attribute. I've spent the last 1/2 hour experimenting and I find that I can manually set a stretchy attribute on \ & /, Unicode characters U+002F & U+005C. Then I can set a minsize attribute to mimic LaTeX \big, \Big etc.
Results are mixed. The characters stretch properly in WebKit (Safari). Firefox stretches the solidus but not the reverse solidus. Chromium stretches both, but then inserts too much horizontal space between characters.
That's probably the best I'll be able to do. I'll work up a Temml revision later this week.

Fixed to the best of my ability in release v0.10.30.


Fixed animepahe

Fixed animepahe with the help of jsbeautifier, it's not necessary as you can try to deobfuscate the javascript with less LOC or just brute force all possible tokens (8-10), but this was the easiest and cleanest solution.

@Blatzar I just wanted to ask but is your kwik fix still working, I am not necessarily trying to use it but I am attempting to access kwik just by using requests or cfscrape and it seems to be blocking me out even when I put the referer.

@Blatzar I just wanted to ask but is your kwik fix still working, I am not necessarily trying to use it but I am attempting to access kwik just by using requests or cfscrape and it seems to be blocking me out even when I put the referer.

Kwik uses cloudflare which is currently broken

All right then, waiting game.

Outdated and doesn't work anymore


Update a project

Hi @francescou,
Great works on this compose-ui!!
Do you have planed for an Edit Button for either Yaml file, Reame file (logo also should be nice)
I plan to use compose-ui to allow several dev teams to interract with a docker swarm cluster, and theses features would be great.

Hi @allamand
thank you very much :)
actually...I'm not sure if it would be useful a file editor inside the Compose UI.
It seems more interesting to me to manage all the files in a git repository and let the UI  Load projects from a git repository
my team is using docker-compose-ui with gitlab to do so, this way we have version control and centralized authentication/authorization.
what do you think about this?

Thanks @francescou,
I'll give a try to the git workflow and let you know.
Do you activate create project from compose-ui in combination of git source for compose-projects ?
Sébastien

Le 9 nov. 2016 à 14:11, Francesco Uliana<EMAIL_ADDRESS>a écrit :
Hi @allamand
thank you very much :)
actually...I'm not sure if it would be useful a file editor inside the Compose UI.
It seems more interesting to me to manage all the files in a git repository and let the UI Load projects from a git repository
my team is using docker-compose-ui with gitlab to do so, this way we have version control and centralized authentication/authorization.
what do you think about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@francescou I tried with GIT url but got an error :
Stack Compose UI
Recreating docker-compose-ui
Attaching to docker-compose-ui
docker-compose-ui | INFO:root:git repo: git@gitlab.pic.s1.p.fti.net:dfyarchicloud/docker-compose-ui-projects.git
docker-compose-ui | INFO:root:git clone git@gitlab.pic.s1.p.fti.net:dfyarchicloud/docker-compose-ui-projects.git
docker-compose-ui | Traceback (most recent call last):
docker-compose-ui |   File "/app/main.py", line 14, in <module>
docker-compose-ui |     from scripts.git_repo import git_pull, git_repo, GIT_YML_PATH
docker-compose-ui |   File "/app/scripts/git_repo.py", line 31, in <module>
docker-compose-ui |     Repo.clone_from(git_repo, GIT_YML_PATH)
docker-compose-ui |   File "/env/lib/python2.7/site-packages/git/repo/base.py", line 885, in clone_from
docker-compose-ui |     return cls._clone(git, url, to_path, GitCmdObjectDB, progress, **kwargs)
docker-compose-ui |   File "/env/lib/python2.7/site-packages/git/repo/base.py", line 831, in _clone
docker-compose-ui |     finalize_process(proc)
docker-compose-ui |   File "/env/lib/python2.7/site-packages/git/util.py", line 155, in finalize_process
docker-compose-ui |     proc.wait()
docker-compose-ui |   File "/env/lib/python2.7/site-packages/git/cmd.py", line 319, in wait
docker-compose-ui |     raise GitCommandError(self.args, status, self.proc.stderr.read())
docker-compose-ui | ValueError: I/O operation on closed file
docker-compose-ui exited with code 1

similar error with https endpoint instead of ssh
docker-compose-ui | INFO:root:git repo: https://gitlab.pic.s1.p.fti.net/dfyarchicloud/docker-compose-ui-projects.git
docker-compose-ui | INFO:root:git clone https://gitlab.pic.s1.p.fti.net/dfyarchicloud/docker-compose-ui-projects.git
docker-compose-ui | Traceback (most recent call last):
docker-compose-ui |   File "/app/main.py", line 14, in <module>
docker-compose-ui |     from scripts.git_repo import git_pull, git_repo, GIT_YML_PATH
docker-compose-ui |   File "/app/scripts/git_repo.py", line 31, in <module>
docker-compose-ui |     Repo.clone_from(git_repo, GIT_YML_PATH)
docker-compose-ui |   File "/env/lib/python2.7/site-packages/git/repo/base.py", line 885, in clone_from
docker-compose-ui |     return cls._clone(git, url, to_path, GitCmdObjectDB, progress, **kwargs)
docker-compose-ui |   File "/env/lib/python2.7/site-packages/git/repo/base.py", line 831, in _clone
docker-compose-ui |     finalize_process(proc)
docker-compose-ui |   File "/env/lib/python2.7/site-packages/git/util.py", line 155, in finalize_process
docker-compose-ui |     proc.wait()
docker-compose-ui |   File "/env/lib/python2.7/site-packages/git/cmd.py", line 319, in wait
docker-compose-ui |     raise GitCommandError(self.args, status, self.proc.stderr.read())
docker-compose-ui | ValueError: I/O operation on closed file

Do you have any idea how to debug ? (can't exec in the container)

Hi,
my problem may be occur cause of self-signed certificates problem for my gitlab instance.
could we imagine allow to enable something like
git config --system http.sslverify false ?

OK I Fix this by adding the env var GIT_SSL_NO_VERIFY when starting the container :
      GIT_REPO: https://gitlab.net/cloud/docker-compose-ui-projects.git
      GIT_SSL_NO_VERIFY: 1

This works for me I close the issue!

Sorry I reopen the thread I've got additional question :
Even with a git workflow for compose-projects I would like to enable "ephemeral" project creation for users to quickly create/test live conf on compose-ui, and when they are satisfied they can submit properly using git workflow.
It seams that project creation don't works with gitlab wlows actually ? When pushing new project I've got an error

Hi,
In order to allow me to enable local update for testing purpose (letting know users that updates from UI is ephemeral and to backup thems they need to make a pull request in the compose-projects-repo) I update this in scripts/git_repo.py :
#GIT_YML_PATH = '/opt/docker-compose-projects-git/'
GIT_YML_PATH = '/opt/docker-compose-projects/'

This allow to have both git feature, and local update enabled.
What do you think about it ?

Hi @allamand and thanks for your contribution
if I understood correctly you don't want user to create ephemeral projects on the git repository, right?

Hi @francescou,
No in fact that the opposite, even with git repo I would like users to be able to create test project
Sébastien

Le 16 nov. 2016 à 21:13, Francesco Uliana<EMAIL_ADDRESS>a écrit :
Hi @allamand and thanks for your contribution
if I understood correctly you don't want user to create ephemeral projects on the git repository, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, the problem is that it can be a bit confusing, using git, to create new project on docker-compose-ui and then not be able to push the modifications (the git repo is read-only).
We usually let the users create new projects on gitlab and then they can use them on docker-compose-ui once they've clicked "Reload projects" (it performs a git pull)
We also have an automated deployment pipeline (from git push to docker container deployment), I can write you an email if you are interested.

I entirely agree with you!
But in my case I am promoting the use of docker swarm for many different teams with different working method, and as a first approach the use of gitlab and merge request may be overkill and I will loose to many people on the road.
I have change the path of directory in my fork so that both fit and local update are Woking with lot of WARNING in the réadme to remind users that if they want their project to persist they need to make pull request in gitlab.
Meanwhile they can easily play around using create button.
Yes please share your pipeline if you could ;)
Sébastien

Le 17 nov. 2016 à 07:43, Francesco Uliana<EMAIL_ADDRESS>a écrit :
Hi, the problem is that it can be a bit confusing, using git, to create new project on docker-compose-ui and then not be able to push the modifications (the git repo is read-only).
We usually let the users create new projects on gitlab and then they can use them on docker-compose-ui once they've clicked "Reload projects" (it performs a git pull)
We also have an automated deployment pipeline (from git push to docker container deployment), I can write you an email if you are interested.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


KOGITO-4542 - Grafana dashboards for cloud enviroment

JIRA: https://issues.redhat.com/browse/KOGITO-4542
For numeric decisions we will export the distribution anyway, but in the grafana dashboards we display only the average metric (see below)

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Your code is properly formatted according to this configuration
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

The Linux check is successful.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

Jenkins retest this please


serde_amqp::Value variants not following rust naming convention

Due to my negligence, the variant names didn't strictly follow the rust naming convention, for example, Value::UInt should be Value::Uint instead. Fixing this would be a breaking change and is probably not worth it.
This issue is opened just for record.

In UpperCamelCase, acronyms and contractions of compound words count as one word: use Uuid rather than UUID, Usize rather than USize or Stdin rather than StdIn.

https://rust-lang.github.io/api-guidelines/naming.html

Fixed in<PHONE_NUMBER>7dbe914d2d989b5520dc68f2785042


example of log transformation into pages

Acceptance criteria:

chunk of raw logs from pipeline and aggregator and the result

Gave two examples for aggregator, one for pipeline

It should be markdown, .md, not pdf.
Place all the information in the pdf to .md
https://github.com/cloudhubs/logscraper/blob/master/docs/Transformations.pdf
Delete the pdf after that.


ColorPicker SpinBox makes the cursor disappear on drag

Godot version
255e077
System information
Windows 10 x64
Issue description

Dragging the value is not possible. You need to press Escape or click somewhere away to make the cursor appear. Does not seem to happen with SpinBoxes in other places. Only happens in the editor, runtime ColorPickers are fine (related to popups?).
Steps to reproduce

Open any ColorPicker in the inspector (e.g. for modulate property)
Try dragging SpinBox arrows

Minimal reproduction project
No response

I was able to replicate this on Windows 10 and version c80540f9a20b45d107b9bed1e749571a83492337

Potentially related #60526 #62620 #58793
I remember this happening with the GraphEdit spinbox it has for changing zoom (can't find the issue), it was then fixed for spinbox at some point.


Having a functional tensorRT extension seems to mean not having access to the clip interogate feature?

See https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/13689 it seems like maybe people just gave up? Is there no way to have clip interrogate working at the same time tensorRT is installed?

As I'm not aware of this feature, could you elaborate on what exactly clip interrogate does (ideally from a technical perspective)?
Or can you provide instructions on how to set it up and reproduce this error?

"Interrogate clip" is a default feature for img2img in automatic1111webgui. As far as I know it's always been there and always been functional.
It's never not been set up, and I'm not sure what steps I might've taken to break it, other than getting tensorRT working properly. Both the timing, and the other issue I linked are my only evidence.
This is the error message.

I don't know much about how to install clip interrogate, because like I said, it's a default feature of automatic1111webgui that has always worked without me ever having had to do anything.
I tried setting if setting the sd_unet back to none

Was related or would fix clip interogate. It did not help. It did however trigger this bug: which is too vague to explain https://github.com/AUTOMATIC1111/stable-diffusion-webui-tensorrt/issues/69
In essence any time I do anything at all except using this extension properly, all/some of my profiles are set to invalid. So merely unselecting the sd_unet in the webgui means I'll have to rebuild all of my engine profiles. If I could use force rebuild to rebuild just the broken one(s) that wouldn't be so bad. But I have to rebuild them all. I think somehow force rebuild is not effecting models.json properly as I mentioned here https://github.com/AUTOMATIC1111/stable-diffusion-webui-tensorrt/issues/73

I created this thread to ask how someone as inept as me might update to the dev branch https://github.com/AUTOMATIC1111/stable-diffusion-webui/discussions/13760 if anyone reading this issue knows how.
I figured I didn't need to be on the dev branch because the instructions I first read about his extension telling me to go to the dev branch were two months old. So I figured the master branch, which update.bat is pulling it's git pull from, has probably caught up by now. But that's just a wild guess by me :)

Okay so my issues have nothing at all to do with dev branch or master branch, as it seems automatic1111's dev branch and master branch happen to be identical today?

I can replicate this issue. Simply rename models.py under this extension to models_trt.py,
and change line 12 of ui_trt.py from
from models_trt import make_OAIUNetXL, make_OAIUNet
to
from models import make_OAIUNetXL, make_OAIUNet
See #121

models_trt

Thank you so much, this fix absolutely works. And better yet, it helps me feel like I'm not losing my mind. I'm so new to this ai stuff I thought maybe it was 100% my own ineptness causing me to see imaginary problems everywhere :D
TLDR: I made your changes and it works. I can confirm rt rtensor and clip interrogate are working on my machine both.

models_trt

Thank you so much, this fix absolutely works. And better yet, it helps me feel like I'm not losing my mind. I'm so new to this ai stuff I thought maybe it was 100% my own ineptness causing me to see imaginary problems everywhere :D
TLDR: I made your changes and it works. I can confirm rt rtensor and clip interrogate are working on my machine both.

@left1000 I'm glad it works! I suggest keeping the issue open until the pull request is merged so the maintainer and others can see it. Have a great day!

I only know how to close or open an issue when inputting a new comment. So to follow up with your suggestion... I typed this sentence.


Adding promise aware tap function

Note:
> eslint ...
/home/travis/build/ramda/ramda/src/tapP.js
  24:19  error  Unexpected space before function parentheses            space-before-function-paren
  27:3   error  Expected indentation of 4 space characters but found 2  indent
  28:2   error  Newline required at end of file but not found           eol-last

But see https://github.com/ramda/ramda/issues/2074#issuecomment-277152148 before bothering to fix it.

Thanks for the review @CrossEye
I'm sort of lost between Promises and Ramda.
I published the request for the 'Q' library here:  https://github.com/kriskowal/q/pull/773
but got the response that it doesn't belong there.
I like ramda's composeP/pipeP, but without a tapP (promise aware), can't debug much and I guess vanilla ramda maybe does not want to work with promises anymore?
So, is this something that belongs in ramda fantasy given that promises are like tasks?

tap works fine with composeP and pipeP as pointed out here: https://github.com/ramda/ramda/issues/2074

That's the reason people have been down on Promises: they're similar to Tasks/Futures, but not lawful.  One can't reason about them or use them in ways consistent with other types.
But I'm glad the current tap already works for you.  That makes things much easier.


Pipewire, unable to set up filter chain via configuration.nix

Describe the bug
Unable to set filter chain via configuration.nix although it works if i put on ~/.config/pipewire/
Steps To Reproduce
Steps to reproduce the behavior:

add a libpipewire-module-filter-chain block inside context.modules via option services.pipewire.config.pipewire.

pipewireconfnix.txt
Expected behavior
Add a extra sound imput(Noise Canceling source).
Additional context
could be related to upgrade from pipewire 0.3.54 to 0.3.55 breaks rnnoise filter
× pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/etc/systemd/user/pipewire.service; linked-runtime; preset: enabled)
    Drop-In: /nix/store/khly40xfd1j3kdq3hj1s728sbxnx4xn1-user-units/pipewire.service.d
             └─overrides.conf
     Active: failed (Result: exit-code) since Tue 2022-09-27 09:58:18 -03; 15s ago
   Duration: 18ms
TriggeredBy: × pipewire.socket
    Process: 21658 ExecStart=/nix/store/85bkqah1kxikn0cqmxs3d0q4n527b9g5-pipewire-0.3.56/bin/pipewire (code=exited, status=161)
   Main PID: 21658 (code=exited, status=161)
        CPU: 18ms

set 27 09:58:18 inferno systemd[1142]: pipewire.service: Scheduled restart job, restart counter is at 5.
set 27 09:58:18 inferno systemd[1142]: Stopped PipeWire Multimedia Service.
set 27 09:58:18 inferno systemd[1142]: pipewire.service: Start request repeated too quickly.
set 27 09:58:18 inferno systemd[1142]: pipewire.service: Failed with result 'exit-code'.
set 27 09:58:18 inferno systemd[1142]: Failed to start PipeWire Multimedia Service.

[E][02881.509507] pw.core      | [          core.c:  382 core_new()] 0x557bbb8330e0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
[E][02881.509582] mod.filter-chain | [module-filter-ch: 2235 pipewire__module_init()] can't connect: Operation not supported
[E][02881.509791] pw.conf      | [          conf.c:  560 load_module()] 0x557bbb7cd710: could not load mandatory module "libpipewire-module-filter-chain": Operation not supported
[E][02881.509864] default      | [      pipewire.c:  125 main()] failed to create context: Operation not supported

Notify maintainers

Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.19.9, NixOS, 22.11 (Raccoon), 22.11pre411253.79d3ca08920`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.0`
 - channels(lucio): `""`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I have used this for quite a while without problems:
{ config, pkgs, ... }:
let
  json = pkgs.formats.json {};
  pw_rnnoise_config = {
    "context.properties" = {
      "log.level" = 0;
    };
    "context.spa-libs" = {
      "audio.convert.*" = "audioconvert/libspa-audioconvert";
      "support.*" = "support/libspa-support";
    };
    "context.modules" = [
      {
        name = "libpipewire-module-rtkit";
        args = {
          #"nice.level"   = -11;
          #"rt.prio"      = 88;
          #"rt.time.soft" = 2000000;
          #"rt.time.hard" = 2000000;
        };
        flags = [ "ifexists" "nofail" ];
      }
      { name = "libpipewire-module-protocol-native"; }
      { name = "libpipewire-module-client-node"; }
      { name = "libpipewire-module-adapter"; }

      {
        name = "libpipewire-module-filter-chain";
        args = {
          "node.name"        = "effect_input.rnnoise";
          "node.description" = "Noise Canceling source";
          "media.name"       = "Noise Canceling source";
          "filter.graph" = {
            nodes = [
              {
                type   = "ladspa";
                name   = "rnnoise";
                plugin = "librnnoise_ladspa";
                label  = "noise_suppressor_mono";
                control = {
                  "VAD Threshold (%)" = 50.0;
                 };
              }
            ];
          };
          "capture.props" = {
            "node.passive" = true;
	    "node.target" = "alsa_input.usb-M-Audio_Fast_Track-00.pro-input-0";
	    "audio.position" = [ "AUX0" ];
          };
          "playback.props" = {
	    "audio.position" = [ "MONO" ];
            "media.class" = "Audio/Source";
          };
        };
      }
    ];
  };
in
{
  environment.etc."pipewire/source-rnnoise.conf" = {
      source = json.generate "source-rnnoise.conf" pw_rnnoise_config;
  };
  systemd.user.services."pipewire-source-rnnoise" = {
    environment = { LADSPA_PATH = "${pkgs.rnnoise-plugin}/lib/ladspa"; };
    description = "Noise canceling source for pipewire";
    wantedBy = ["pipewire.service"];
    script = "${pkgs.pipewire}/bin/pipewire -c source-rnnoise.conf";
    enable = true;
    path = with pkgs; [pipewire rnnoise-plugin];
  };
}

You know if something like this would be enough? Since pipewire now can use split conf files I think it could work if there´s a way to generate the /etc/pipewire/pipewire.conf.d/99-input-denoising.conf without the leading and trailing brackets.
let
  json = pkgs.formats.json {};
  pw_rnnoise_config = {

  "context.modules"= [

###MICFILTER
    { "name" = "libpipewire-module-filter-chain";
        "args" = {
            "node.description" = "Noise Canceling source";
            "media.name"       = "Noise Canceling source";
            "filter.graph" = {
                "nodes" = [
                    {
                        "type"   = "ladspa";
                        "name"   = "rnnoise";
                        "plugin" = "${pkgs.rnnoise-plugin}/lib/ladspa/librnnoise_ladspa.so";
                        "label"  = "noise_suppressor_stereo";
                        "control" = {
                            "VAD Threshold (%)" = 50.0;
                        };
                    }
                ];
            };
            "audio.position" = [ "FL" "FR" ];
            "capture.props" = {
                "node.name" = "effect_input.rnnoise";
                "node.passive" = true;
            };
            "playback.props" = {
                "node.name" = "effect_output.rnnoise";
                "media.class" = "Audio/Source";
            };
        };
    }
];

  };
in
{
  environment.etc."pipewire/pipewire.conf.d/99-input-denoising.conf" = {
      source = json.generate "99-input-denoising.conf" pw_rnnoise_config;
  };
}

nvmd, its working this way, you you enlightened me, thnx.
{ config, pkgs, ... }:
{
  sound.enable = true;
  hardware.pulseaudio.enable = false;
  security.rtkit.enable = true;
  services.pipewire = {
    enable = true;
    alsa.enable = true;
    alsa.support32Bit = true;
    pulse.enable = true;
	};
}

{ config, pkgs, ... }:

let
  json = pkgs.formats.json {};
  pw_rnnoise_config = {
  "context.modules"= [
    { "name" = "libpipewire-module-filter-chain";
        "args" = {
            "node.description" = "Noise Canceling source";
            "media.name"       = "Noise Canceling source";
            "filter.graph" = {
                "nodes" = [
                    {
                        "type"   = "ladspa";
                        "name"   = "rnnoise";
                        "plugin" = "${pkgs.rnnoise-plugin}/lib/ladspa/librnnoise_ladspa.so";
                        "label"  = "noise_suppressor_stereo";
                        "control" = {
                            "VAD Threshold (%)" = 50.0;
                        };
                    }
                ];
            };
            "audio.position" = [ "FL" "FR" ];
            "capture.props" = {
                "node.name" = "effect_input.rnnoise";
                "node.passive" = true;
            };
            "playback.props" = {
                "node.name" = "effect_output.rnnoise";
                "media.class" = "Audio/Source";
            };
        };
    }
];
};
in
{
  environment.etc."pipewire/pipewire.conf.d/99-input-denoising.conf" = {
      source = json.generate "99-input-denoising.conf" pw_rnnoise_config;
		};
}

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/pipewire-unable-to-set-filter-chain-via-configuration-nix/21972/4

@wnxkiv85 That log fragment you posted says that it hasn't loaded libpipewire-module-protocol-native yet, and filter-chain depends on that. It used to be a very common issue that you had to have the modules listed in your config in a specific order but I got the impression that they had removed that limitation.
Maybe that is what the regression is about. The separate config fragments presumably get processed only after the main config file so the dependencies are already loaded.

error: The option `services.pipewire.extraConfig."pipewire/pipewire.conf.d/99-input-denoising.conf"' does not exist. Definition values:
       - In `/nix/store/318v6ykv94kgh9hwzgpc81zz0vmbds9a-source/modules/system/noisecancel.nix':
           {
             source = <derivation 99-input-denoising.conf>;
           }

:cry:

Nowadays you have to put it in services.pipewire.extraConfig.pipewire:
{ config, pkgs, ... }:
let
  pw_voice_dsp_config = {
    // <snip, this looks the same as before>
  };
in
{
  hardware.pulseaudio.enable = false;
  security.rtkit.enable = true;
  services.pipewire = {
    enable = true;
    # compatibility layers
    alsa.enable = true;
    alsa.support32Bit = true;
    pulse.enable = true;
    jack.enable = true;
    // if your filters depend on LV2 plugins you can list their nix packages here if you don't want to fiddle with global `*_PLUGIN_PATH` env variables. not sure if it works for other plugin formats though
    extraLv2Packages = with pkgs; [ lsp-plugins ];

    // Custom config files need to be listed here now:
    extraConfig.pipewire = {
      "99-voice-dsp-source" = pw_voice_dsp_config;
    };
  };
}

I've switched away from rnnoise/deepfilternet to a simple gate/compressor/eq setup, but the overall idea is similar.

got it working, thanks king!


Dependancies between modules that can support data sources and not outputs for secrets

Hello everyone.  Is there a way to pass data from one module to another?  For example I have a rds database that I am creating in one rds/terragrunt.hcl and then I would like to use a 1password module running in another terragrunt.hcl file.  When running the rds stack it would be nice to be able to read the datasource in the 1password via the dependency block without referring to outputs as they should not stored in state.  Is this possible?

Hi,
I was thinking to save sensitive data to a file and later reading it through file function
dependency "generator" {
  config_path = "../generator"
  mock_outputs = {
    sensitive_file = "file.txt"
  }
}
inputs = {
  pass = file("../generator/${dependency.m1.outputs.sensitive_file}")
}

Thanks for the suggestion @denis256.  In order to do that we would just need to play with the formatting of what is being stored in 1pasword to see if this is something that would work and then just we would need to make sure these files are in .gitignore.  Wish we could just use data resource between modules.


Implement P2P without external libs [48h]

start with 2 devices.
Make it as robust as possible (should recover automatically)

Currently back to research, since the first implementation was not good enough, and needed root to accept the connection dialog.


Sync param check for DiskANN and HNSW

This PR is to sync how HNSW&DiskANN will perform with empty config with Knowhere 1.x:
The rule is:

If ef exists, we need to ensure ef >= k.
If ef not exists, let ef = max(16, k).

/kind improvement

/lgtm


Test RabbitMQBundleBridge on PHP 8.0 again

https://github.com/php-amqplib/php-amqplib/releases/tag/v3.0.0 now supports PHP 8.0.
Maintenance of RabbitMQBundle has been continued so we no longer need to use the emag-tech-labs fork.

With ^2.5 it picks php-amqplib/php-amqplib (v2.6.0) and php-amqplib/rabbitmq-bundle (2.5.1) when installing lowest dependencies.
Switched to dev-master so that it uses https://github.com/php-amqplib/RabbitMqBundle/commit/27f6e461e9ef0753eaf33889d0e3f66349a7a2e0 and now it picks php-amqplib/php-amqplib (v2.12.0) and php-amqplib/rabbitmq-bundle (dev-master ef71c9b).
I believe that RabbitMqBundle should require ^2.12.2

Created a PR upstream to fix this https://github.com/php-amqplib/RabbitMqBundle/pull/627

They merged my PR and tagged 2.6. Finally it works 🎉


Match chat_invite_accepted to specs

Changes

Move invite up in depth for chat_invite_accepted and chat_invite_rejected as specified in specs

Description is unclear, please link to the spec for reference if possible in general.
“Up in depth” as in referring to the argument here I’m assuming based on the diff, not the call site of the events.

Description is unclear, please link to the spec for reference if possible in general.
“Up in depth” as in referring to the argument here I’m assuming based on the diff, not the call site of the events.

Yep, here are the specs, in the chat_invite_accepted event, invite is not buried in params.


Integrate an option for keyless signing

What would you like to be added:
Please evaluate and integrate a keyless signing process like cosign into ocm.
https://www.youtube.com/watch?v=d5vROySf1I8
Why is this needed:
Let's Encrypt has simplified the ease of consumption and life cyclemanagement for web certificates.
Similarly, sigstore.dev with the help of OpenSSF and the supply chain momentum will simplify the code signing process.
The value proposition is undeniable.
OCM should support and contribute to the emerging standard around Sigstore and offer a simple code signing experience.

https://eprint.iacr.org/2023/003.pdf (thanks @phoban01 and @mandelsoft)
This paper alleges that the cryptographic protocol behind sigstore has no merit.
sigstore.dev responded with https://blog.sigstore.dev/why-you-cant-use-sigstore-without-sigstore-de1ed745f6fc/
While the value/marketing proposition of integrating OCM with Sigstore still holds true, we can reduce the priority of this request until we have clear guidance.

I think there are still strong benefits in enabling these kinds of workflows for ocm.


Update sbt-paradox-akka to 0.18

Updates com.lightbend.akka:sbt-paradox-akka from 0.12 to 0.18.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a nice day!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "com.lightbend.akka", artifactId = "sbt-paradox-akka" }]

superseded by #72


add corresponding headers in source/common/stats/timespan_impl.*

Bug Template
Title: add common/common/assert.h to the timespan_impl lib files.
Description:
timespan_impl.cc is using macros from the common/common/assert.h, add the header files as it's breaking build.

/assign stevenzzzz


Running on MacOS

feature
Do you have any plans to support running this on an Apple M2 processor?
Thank you!

Hi, we are working on support running the model on Apple Silicon.  There is a contribution from the community that currently supports this: https://github.com/cameronbergh/LLaVA-MPS/tree/mps, and you may try it out. We'll update once we finish the integration.  Thanks!

Hello ! Have this fork been merged or work on an apple compatiblity been done?
Thank you !

Also interested, mostly to speed up development

You can start the worker jobs with --device mps and it will use the metal torch backend.
It's still a fairly inefficient code path, so you may be better off using the llama.cpp implementation: https://github.com/ggerganov/llama.cpp

@filipe-m-almeida how would one use llama.ccp instead of this this worker?
python -m llava.serve.model_worker --host <IP_ADDRESS> --controller http://localhost:10000 --port 40000 --worker http://localhost:40000 --model-path liuhaotian/llava-v1.5-13b --device mps

macOS support is updated with quantization coming later. You can try both llama.cpp or the support of macOS in this repo.


Fix loc with MultiIndex

What do these changes do?
Handles correctly the case where the index is a MultiIndex

Related issue number
Resolves #504

[x] passes flake8 modin
[x] passes black --check modin
[x] tests added and passing

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/627/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/629/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/630/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/631/
Test FAILed.


[bug]: Symlinked models cannot be deleted in Model Manager

Is there an existing issue for this problem?

[X] I have searched the existing issues

Operating system
Windows
GPU vendor
Nvidia (CUDA)
GPU model
GTX 1070
GPU VRAM
8GB
Version number
4.0.0rc5
Browser
Firefox 123.0.1
Python dependencies
No response
What happened
I had several models symlinked in InvokeAI and noticed that if I try to delete such a symlinked model using the delete button in the Model Manager beside the model, InvokeAI fails complaining not to be able to rmtree on a symbolic link.
To circumvent such complain, I shutdown the application, delete the symbolic links in IAI, then restart the app to refresh its database.
Here follow a screenshot of the console traceback errors:

What you expected to happen
In theory, it should delete the symbolic link.
How to reproduce the problem
In the specific, I symlinked the SD1.5 diffusers model inside C:\invokeai4\models\sd-1\main, then tried to delete it from MM.

Additional context
No response
Discord username
No response

Not a blocker for 4.0, but should be tracked and fixed as a lower priority bug.

Sure, that's fine.

I'm assuming that the source of the symlink is in the models directory?

The source of the symlinked models is in my second HDD


Update postAssetResponse to properly handle metadata.tags as an array…

When attempting to publish something with tags the response object needs to parse a json array of tags containing key value fields
Sample response with metadata... the current response expects string, which results in an error:
ERRO[2024-10-30T09:54:49-07:00] json: cannot unmarshal object into Go struct field Metadata.metadata.tags of type string
{
  "metadata": {
    "classifier": "raml",
    "tags": [
      {
        "value": "raml"
      },
      {
        "value": "rest"
      },
      {
        "value": "api"
      },
      {
        "key": "product-api-version",
        "value": "v1"
      },
      {
        "key": "original-format",
        "value": "raml"
      }
    ]
  }
}

@soufi please take a look when you can


[js] syntax highlight for 'var' and 'function' not working in Default VS theme

0.10.10 (Feburary build) has a regression is that the following JavaScript keywords are no longer highlighted in the Dark Visual Studio & Light Visual Studio themes:
var let const function get set class interface module namespace
This only affects JavaScript (not TypeScript).
The workaround if to switch to the Dark+ Default and Light+ theme.
Note that there are other colorizing issues open, not caused by this regression: e.g. 'import' and 'from'. See https://github.com/Microsoft/TypeScript-TmLanguage/issues/37

Not sure if intended but delete is not highlighted too

'delete' is also https://github.com/Microsoft/TypeScript-TmLanguage/issues/37

It also appears to get confused about var when it is part of another identifier (which throws off all styles beyond that point):

delete still not highlighted. Is it intended?

'delete' is Microsoft/TypeScript-TmLanguage#37 and will be fixed in the March release.

Yesterday, we created a new release that contains the fix for the coloring of var, let, const, function etc.
Please update...

yield is still not highlighted with version f291f4ad600767626b24a4b15816b04bee9a3049. Is that intended?

seem like import isn't highlighted


String: Find Longest Palindromic Substring in Javascript

https://leetcode.com/problems/longest-palindromic-substring/

assign this to me @akgmage