Adjust IAM token refresh buffer to 5 minutes

IAM Tokens are refreshed at 5 minutes to expiry on the metadata server (i.e. the /computeMetadata/v1/instance/service-accounts/default/token endpoint).
Currently, we wait until 55 seconds before a token expires before refreshing it. It seems possible that we could bump this buffer up to 5 minutes, or just short of 5 minutes, and still get a fresh token, while leaving more room for retries.

We're already using 5 minutes as a buffer when IAM AuthN is enabled.
See https://github.com/GoogleCloudPlatform/cloud-sql-go-connector/blob/4f0e5ba1b64e641850252ae38d921cc3cef09a9d/internal/cloudsql/instance.go#L293-L294.

We should verify this works on GKE and Cloud Run.

Closing this as it's already done.


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use "bodyToString" instead of "toIterable" in client

Fixing https://github.com/softavis/flysystem-cloudflare-bundle/issues/1
Fix cloudfare error : Error parsing form fields

Thanks @johndodev 💯

Thanks @johndodev 💯


Add legacy plugin installation docs

Issue: #49

Can you put the plugins {}
In my opinion it's strictly better than the older version

Agree, done.

Merged, thank you!


Feature: added a function that gets subAccount deposit history from s…

…api/v1/broker/subAccount/depositHist
Signed-off-by: MartoMcfly<EMAIL_ADDRESS>Summary
Feature: added a function that gets subAccount deposit history from sapi/v1/broker/subAccount/depositHist
Additional Information
No breaking changes or dependencies added on this pull request

Response type different than the one described in api documentation. Which one is correct ?
https://binance-docs.github.io/Brokerage-API/Brokerage_Operation_Endpoints/#get-sub-account-deposit-history
@MartoMcfly

Can confirm typing were incorrect. Correct typings:
  getBrokerSubAccountDepositHistory(
    params?: GetBrokerSubAccountDepositHistoryParams
  ): Promise<BrokerSubAccountDepositHistory[]> {
    return this.getPrivate('sapi/v1/broker/subAccount/depositHist', params);
  }

export interface BrokerSubAccountDepositHistory {
    depositId: string,
    subAccountId: string,
    amount: string,
    coin: string,
    network: string,
    status: number,
    address: string,
    addressTag: string,
    txId: string,
    insertTime: number,
    sourceAddress: string,
    confirmTimes: string
}

@tiagosiebler @MartoMcfly

Hey @Xavier59 almost missed this - silly question at a glance, does this mean that the typing in this SDK needs an update for that interface?

Yes @tiagosiebler , this interface need an update with the model I gave above :)

Yes @tiagosiebler , this interface need an update with the model I gave above :)

Thanks @Xavier59 - fixed via #328 in v3.6.0. Should be on npm shortly. In future, if you comment somewhere like here and I potentially missed it, please feel free to open a new issue. I read your comments a while back but then totally forgot about it since it was hidden away in this thread. Thanks for sharing the corrected type too!


Modus side navigation item the tooltip is aligned to the center of the side nav item icon

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have read the contributing guidelines

Describe the issue
Modus side navigation item the tooltip is aligned to the center of the side nav item icon.
Expected : it should be aligned to whole item. so when focusing over the item tooltip should be displayed
Reduced test cases
No response
What operating system(s) are you seeing the problem on?
No response
What browser(s) are you seeing the problem on?
No response
What is the issue regarding ?
@trimble-oss/modus-web-components
What version of npm package are you using ?
0.4.1-react17
Priority
Medium
What product/project are you using Modus Components for ?
Trimble Construction Cloud
What is your team/division name ?
Industry Clouds
Are you willing to contribute ?
Yes
Are you using Modus Web Components in production ?
Yes

@VinoSakthiv This is fixed now. Can you verify in the latest package?


rework KMC alerting (pair)

Description
As KMC is used for billing users, it is essential that it exposes metrics usable to fire alerts whenever the billing would be impacted. To ensure this, the metrics exposed by KMC and the alerting rules using these new metrics need to be reworked.

Abbreviations

KMC sends the data needed for billings users to the Event Data Platform (EDP).
Kyma Environment Broker (KEB) is a component that allows provisioning Kyma as a runtime on clusters provided by third-party providers.

Helpful Links

Overview of current metrics in KMC
Example metrics in KMC
Golang Prometheus package
Prometheus Metrics Intro
Prometheus Naming Convention
Prometheus Alerting Best Practices

Acceptance

[ ] ensure all clusters (listed by KEB) which have to be considered active are scraped by KMC

in the KEB output: .status.state is set ot one of these values per SKR: succeeded , error , upgrading , updating
currently we rely on .status.provisioning.state == succeeded

[ ] check with KEB team for a metric which contains all active clusters which need to be scraped (all clusters with status is also fine). If they dont have any, then expose one in KMC
[ ] Metric per scraped instance for overall success / error.
[ ] Metric per subcomponent (keb, gardener, edp) for overall success / error.

extend kmc_skr_calls_total with labels for instanceID, shootID, subaccount, globalaccount

[ ] Metric for number of consecutive resends to edp per cluster
[ ] kmc_edp_request_total contains information about which clusters data was sent (label instanceID, shootID, subaccount, globalaccount)
[ ] Implement alerts in the helm chart which use the new metrics:

[ ] Individual clusters error rate increases spontaneously
[ ] Overall error rate increases spontaneously
[ ] Cluster which should be scraped do not get scraped

[ ] New alerts are tested
[ ] metrics are tested during unit test phase

Testing approach on DEV

deploy KMC on DEV (change the existing deployment, check with argo team)
create 1-n clusters on DEV
wait till KMC scraped them
check metrics / dashboards / alerts

Alerts

[ ]  Individual clusters error rate increases spontaneously when querying the SKR
[ ]  Overall http request to EDP failure rate increases spontaneously.
[ ]  Overall http request to EDP failure rate increases spontaneously.
[ ]  Cluster which should be scraped do not get scraped successfully.

New kcp chart will be automatically promoted to stage and next Monday to prod


pass in baseRouter for hooks

Codecov Report

Merging #75 into master will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff          @@
##           master   #75   +/-   ##
====================================
  Coverage      82%   82%
====================================
  Files           9     9
  Lines         339   339
====================================
  Hits          278   278
  Misses         59    59
  Partials        2     2

Continue to review full report at Codecov.

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


Add new parameter 'Birthday' & Update DG and UG & Update some test cases & Correct some styles

Have you tried running in the terminal gradlew clean headless allTests to see whether all test passed ?


Allow lines option to be configured when following app logs

Issue: #633

Thanks for the PR @alhafoudh 🙏
I've run the tests locally and I'm getting one error:
Failure:
CommandsAppTest#test_follow_logs [/Users/dmcbreen/Work/basecamp/kamal/test/commands/app_test.rb:147]:
Expected /docker\ ps\ \-\-quiet\ \-\-filter\ label=service=app\ \-\-filter\ label=role=web\ \-\-filter\ status=running\ \-\-filter\ status=restarting\ \-\-latest\ \|\ xargs\ docker\ logs\ \-\-timestamps\ \-\-tail\ 10\ \-\-follow\ 2>&1/ to match "ssh -t root@app-1 -p 22 'docker ps --quiet --filter label=service=app --filter label=role=web --filter status=running --filter status=restarting --latest | xargs docker logs --timestamps --follow 2>&1'".

bin/test Users/dmcbreen/Work/basecamp/kamal/test/commands/app_test.rb:146

Could you resolve that and then I'll get this merged.

@djmb Hi, I ran tests on my machine and I get no errors :( Do you have more error context you can share?

@djmb Nevermind, I reproduced the error.

@djmb You merged it before I fixed the tests. Sorry for confusion. Here is another PR for the assertion fix: https://github.com/basecamp/kamal/pull/712

Hey @alhafoudh - I wanted to get your changes in, so I merged and then committed a fix for the tests after. I'll close your other PR. Thanks again for this!


Add node js 84.bot authentication msgraph

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: stevkan sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I did a pass this morning and cleaned up a bit, we'll iterate with any needed changes.


Scale without tare

Hi,
I'm building a scale, with load cells, HX711 as a signal amplifier and Esp 32 as a microcontroller.
I chose Esp 32 because with sleep mode I can save much energy and therefore feed the system with a photovoltaic panel and a small lead-acid battery (the scale is in a remote site).
The problem I would like to solve concerns the  tare of the scale: I have to use the system continuously "sleeping down" (and "wakeing up") the controller every hour ... As you can imagine the system performs the tare at each wakeup so that already at the second weighing the object to be weighed is included in the tare and the weight shown on the display is zero.
Has anyone found themselves having to solve a similar problem?
Thank you for the answer...

So, on ESP8266 if I do not use LoadCell.start (stabilizingtime); at start, values are added and go up to -370 kg. I also need to ensure that at start there is no tare and the weight is shown with a load, and not be reset to zero at the start of the system.

If you want to be sure that tare is not executed at the start of the sketch, just leave out function LoadCell.start (stabilizingtime) in setup().
I don't quite understand what you mean by "values are added and go up to -370 kg"?
Note that the raw conversion value from HX711 is always a positive number, and the readout can only be negative if the tare offset is grater than the conversion value. So if you dont apply a tare offset I don't think it's possible to get a negative number readout.

negative is not a problem. Just changed the wires E +, E-. ))))
This is what I meant when I said values are added:
Starting...
Startup + tare is complete
Load_cell output val: 0.00
Load_cell output val: 23.72
Load_cell output val: 47.44
Load_cell output val: 94.89
Load_cell output val: 118.62
Load_cell output val: 142.34
Load_cell output val: 166.06
Load_cell output val: 189.78
Load_cell output val: 213.51
Load_cell output val: 237.23
Load_cell output val: 260.96
Load_cell output val: 284.68
Load_cell output val: 332.13
Load_cell output val: 355.85
Load_cell output val: 379.57
Load_cell output val: 379.58
Load_cell output val: 379.58
Load_cell output val: 379.57
Load_cell output val: 379.57
Load_cell output val: 379.57
Load_cell output val: 379.57
Load_cell output val: 379.57
`//-------------------------------------------------------------------------------------
// HX711_ADC.h
// Arduino master library for HX711 24-Bit Analog-to-Digital Converter for Weigh Scales
// Olav Kallhovd sept2017
// Tested with      : HX711 asian module on channel A and YZC-133 3kg load cell
// Tested with MCU  : Arduino Nano, ESP8266
//-------------------------------------------------------------------------------------
// This is an example sketch on how to use this library
// Settling time (number of samples) and data filtering can be adjusted in the config.h file
#include <HX711_ADC.h>
#include <EEPROM.h>
//HX711 constructor (dout pin, sck pin):
HX711_ADC LoadCell(12, 14);
const int eepromAdress = 0;
long t;
void setup() {
float calValue; // calibration value
calValue = 22325.24; // uncomment this if you want to set this value in the sketch
//22325,24;
#if defined(ESP8266)
//EEPROM.begin(512); // uncomment this if you use ESP8266 and want to fetch the value from eeprom
#endif
//EEPROM.get(eepromAdress, calValue); // uncomment this if you want to fetch the value from eeprom
Serial.begin(9600); delay(10);
Serial.println();
Serial.println("Starting...");
delay (5000);
LoadCell.begin();
long stabilisingtime = 2000; // tare preciscion can be improved by adding a few seconds of stabilising time
//LoadCell.start(stabilisingtime);
if(LoadCell.getTareTimeoutFlag()) {
Serial.println("Tare timeout, check MCU>HX711 wiring and pin designations");
}
else {
LoadCell.setCalFactor(calValue); // set calibration value (float)
Serial.println("Startup + tare is complete");
}
}
void loop() {
//update() should be called at least as often as HX711 sample rate; >10Hz@10SPS, >80Hz@80SPS
//use of delay in sketch will reduce effective sample rate (be carefull with use of delay() in the loop)
LoadCell.update();
//get smoothed value from data set
if (millis() > t + 100) {
float i = LoadCell.getData();
Serial.print("Load_cell output val: ");
Serial.println(i);
t = millis();
}
//receive from serial terminal
if (Serial.available() > 0) {
float i;
char inByte = Serial.read();
if (inByte == 't') LoadCell.tareNoDelay();
}
//check if last tare operation is complete
if (LoadCell.getTareStatus() == true) {
Serial.println("Tare complete");
}
}`

I took another new ESP8266, new HX711, and new 50 kg load cells. Connected on wires 5 cm to eliminate interference. The result is the same.
Starting...
Startup + tare is complete
Load_cell output val: 0.00
Load_cell output val: 0.00
Load_cell output val: 0.00
Load_cell output val: 0.00
Load_cell output val: 0.00
Load_cell output val: 0.00
Load_cell output val: 22.24
Load_cell output val: 44.49
Load_cell output val: 66.73
Load_cell output val: 88.97
Load_cell output val: 111.22
Load_cell output val: 133.46
Load_cell output val: 155.71
Load_cell output val: 177.95
Load_cell output val: 200.19
Load_cell output val: 222.44
Load_cell output val: 266.92
Load_cell output val: 289.17
Load_cell output val: 311.41
Load_cell output val: 333.66
Load_cell output val: 355.90
Load_cell output val: 355.90
Load_cell output val: 355.90
Load_cell output val: 355.90
Load_cell output val: 355.90
Load_cell output val: 355.90
Load_cell output val: 355.90

Hi
The function getData() returns an average of the library's rolling data set (default is 16+2 samples), but when you start, the  dataset is empty, thats why the first readout is 0 and then increasing until the dataset is filled up with data.
If you need to have the data correct from the very first call to getData() in loop() you must first fill up the data set with conversions so that the average value reflects the actual data from HX711.
You could try to put this code in the setup() part of your sketch to fill up the data set before the loop() is started (this code has not tested, hope it works... ):
int s = LoadCell.getSamplesInUse() + 2; // get number of samples in data set
while( s > 0 ) {
  if (digitalRead(12) == LOW) { // HX711 dout pin is pulled low when a new conversion is ready
       LoadCell.getData(); // add data to the set and start next conversion
       s--;
   }
}

no, it did not work. I even increased the request period. Data is filled in for 3 requests of 500ms.
So the calibration went wrong too? Why do the values eventually increase to 370 kg if there is nothing on the scale? I did the calibration according to the instructions: starting on an empty scale, set the weight to 90 kg, entered 90 kg into the port.

I forgot to include the update() function in the code snippet, that's why it didn't work. Updated and tested version below, put it at the bottom of the setup() part of your sketch.
///assuming that the dout pin is connected to D12:
  int s = LoadCell.getSamplesInUse() + 2; // get number of samples in data set
  while ( s > 0 ) {
    LoadCell.update();
    if (digitalRead(12) == LOW) { // HX711 dout pin is pulled low when a new conversion is ready
      LoadCell.getData(); // add data to the set and start next conversion
      s--;
    }
  }

The no-load value of 370 is probably because you didn't apply any tare offset. Similar; when I run your sketch (using my own calibration factor) on my 1kg loadcell without any mass, I get a no-load value of 12300gr. If I then send 't' in the terminal to perform tare offset, the no-load value is 0gr as it should be. If you don't want to use the library tare function, you will have to substract the zero value (370) in your sketch to get the actual mass. Or you can manipulate the library tare offset by using the functions described in post no. 2.
To check if calibration is correct, just add a known mass to the loadcell and observe if the value is increased by the correct number.
BTW; You probably know this, but the timing of 100ms (I assume this is what you changed to 500ms) in the example sketch does not affect the library data sampling at all, it's just the Serialprint interval.

Thanks. But this does not always work. WatchDog on the ESP8266 sometimes turns on.

Try to include yield(); or delay(1); at the end of the above while() loop.

Building a dual weight with individual HX711 sensors, but need a function for re-calibrating bouth sensors individually within a sketch.
When using the Calibration Sketch, I can get the raw number using getData(), but are not able to retreive this inside a sketch. Then I only get the calibrated number.. Tried getTareOffset(), but it's not the same as what I get using getData() in the calibration sketch.
How can I easily re-calibrate HX711 (not just setting a new setCalFactor()) using two individual sensors within the Read_2x_load_cell.ino sketch?

@msevland please don't post new and unrelated issues within existing threads! I have re-posted your question under #37


Simon/misc/1

Final PR before 0.1. I'll try to vacuum up all the parts I can get to quickly before merging.

I think most things are complete for a 0.1v now.


npm install fails with node v12

Describe the bug
npm i fails with node v12
You get a large list of errors like:
../src/fibers.cc:68:2: error: ‘Handle’ does not name a type
The suggested solution is to install g++ build essentials, which were already present.
To Reproduce

remove node_modules ( or get a fresh copy of this repo )
use node v12 ( tested with v12.17.0 and v12.18.4 )
npm i

Expected behavior
Expect everything to get installed :)
Desktop (please complete the following information):

OS: Ubuntu 2020.04

Additional context
Using Node v10 works fine, and after installing you can just switch to node v12 without any issue

Try deleting your package-lock and using 'npm ci'.

I assume you mean deleting your node_modules, and doing npm ci, as deleting your package-lock is not appreciated by npm ci.
Same error persists in this case.

@ReinoutStevens yeah

rm ./package-lock.json
git checkout package-lock.json
npm ci

Yeah thats what I did after npm ci complained that it requires a package-lock file :)
Fails both on master and 1.8.0

This should be fixed by https://github.com/prebid/prebid-universal-creative/pull/159


[Content block] enhancements to enable brand expression

User Story

As a [user role below]:
Carbon for ibm.com developer

I need to:
create/change the Content block brand expression enhancements

so that I can:
provide the ibm.com adopter developers components they can use to build ibm.com web pages

Updates

[ ] Update spacing logic in existing Content block
[ ] Adds optional sub heading and body copy to all Content block variations
[ ] Add knobs for larger type size for brand expression
[ ] Allows for additional CTA types

Additional information

Story within Storybook with corresponding knobs
Utilize Carbon
Create with Shadow DOM and Custom Elements standards
Design specs in Figma and PDF uploaded to Box
Functional specs remain the same
Web Components Visual QA testing issue (#?visualqa issue?)
Web Components Prod QA testing issue (#?prodqa issue?)

Acceptance criteria

[ ] Include README for the web component and corresponding styles
[ ] Create Web Components styles in styles package
[ ] Do not create knobs in Storybook that include JSON objects
[ ] Break out Storybook stories into multiple variation stories, if applicable
[ ] Add/update e2e test scripts
[ ] Confirm e2e test results have no major errors
[ ] Create codesandbox example under /packages/web-components/examples/codesandbox and include in README
[ ] Update the Carbon for ibm.com website component data file to be sure the web site Component Status and Storybook links are correct
[ ] Use the Visual QA checklist to verify design quality
[ ] If a design is provided, the Designer is included as a Reviewer in the Pull Request
[ ] Provide a direct link to the deploy preview for the designer in the Pull Request description
[ ] A comment is posted in the Prod QA issue (#?prodqa issue?)

HOLD updates to Content block until we determine the spacing logic.


Sample Snowfakery Recipe to Generate Permutations of Contacts, related Household Accounts, and Opps.

As a project developer, I need to be able to generate series of objects that are permutations of various record types and field values, and all required related objects for that base object.
When building out a membership portal, developers of the portal need to be able to test the interface with members who have all the different membership types and statuses.  To do this a data set must include all the permutations of the membership object (generally a custom object), the contacts that are required for each, accounts for those contacts, and potentially other required objects.

@mkolodner I feel like you would have specific ideas about this, given the complexity of the mentorship program data model that you've built.  I'm not sure what the next step is here, but I'm going through Issues to see what's actionable and I'd love your thoughts!

I modified the title here to be more specific and reflect the tooling that's been created since I first created this issue.  I still want to have a clear path to do this.  I know Forceea has a command in its instructions to do permutations of a list. I'm not sure if Snowfakery does currently.

@acrosman I think we're close to being able to do this, but not quite there yet.  Can you share your thoughts about where we are and the next step so that curious Sprinters can get involved?  So far, I know how to create all of the records in the requirements but I haven't succeeded at creating all of the permutations yet.

Permutations are a challenge still (see this issue), but working on some options would be good.
Starting with a simpler version with clear directions to get us started would be a great base line. Another helpful step would be helpful would be feedback to Paul and/or I about if there are other people that want this feature and if the proposed solutions for it make sense to others. That may help Paul determine priorities or other people work on pull requests.

@acrosman I like the membership example.  Maybe we can use the Membership Schema open source project as a use case?

We could refine/replace this issue with an ask to create a recipe for generating membership data that fits that schema.  Makes sense to me.

Moved this one out of Sprint Ready for 2/2021 Sprint in favor of the clearer sample recipe issues.


ssh based web login

Playing with new authentication idea described in this topic: https://discourse.asciinema.org/t/ssh-based-login-to-web-app/35

I don't think this is such a practical idea at this point. It was fun experiment though.

I don't think this is such a practical idea at this point. It was fun experiment though.

Do you mind sharing a bit about how you came to that conclusion? I've been thinking about implementing this in a separate project.

Do you mind sharing a bit about how you came to that conclusion? I've been thinking about implementing this in a separate project.


Add indent_match_arms option

Makes it optional whether to indent arms in match expressions. Setting
this to false may be desirable for people wishing to avoid
double-indents, in that if the match arm is a block, the block will
cause an extra indentation level, and if it isn't a block but just a
single line, it's still easy to see the logic at a glance.
This style is preferred in certain other languages with switch
statements, e.g. Linux style C and the most common Java style.

Fixed nit.

Thanks!


x.next() -> next(x) for python3 compat

.next() is renamed .__next__ in py3k, use next()

Thank you!


Add Bicep and update API versions

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

@mumian in bicep template, "dependsOn" property for function app should include hosting plan, storage account, application insight and VNET. "dependsOn" property for networkConfig should include function app and VNET.

@patelchandni - see "Implicit dependency" in https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/resource-dependencies. The azuredeploy.json file is built from main.bicep. You can see dependsOns are added in azuredeploy.json.


SagerNet.sing-box version 1.3.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/112443&drop=dogfoodAlpha

@microsoft-github-policy-service agree


Use JDK Docker bas image instead of JRE

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

Project coverage is 84.09%. Comparing base (e29dc4b) to head (0ae3720).

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #1018   +/-   ##
=========================================
  Coverage     84.09%   84.09%
  Complexity     3673     3673
=========================================
  Files           381      381
  Lines         12371    12371
  Branches       1064     1064
=========================================
  Hits          10404    10404
  Misses         1472     1472
  Partials        495      495

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


[kernel] Enable fusing i8 extsi into matmul/conv

I think this is already done?

Feel free to turn it into a tracking issue for what's left for other fusion issues. :)

Closing this issue. Ill file some issues that I see.


⚠ ClamAV has degraded performance

In ba5f14f, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 85 ms

Resolved: ClamAV performance has improved in be154c6.


Pass sandesh from opserver to discoverClient

Currently, when the opserver uses the discoverClient,
the logs are not captured. Specifically, in my case,
this caused the following helpful log messages:
default [SYS_INFO]: discClientLog: connection error or failed to publish
to never show up in my contrail-analytics logs.
A sendeesh object must be passed explicitly to the discoveryClient
in order for logging to work with its set_sandesh method.
This patch ensures that the global sendeesh object is passed
from the opserver to the discoveryClient so that its log messages
are captured.

Can you please raise a git review for this patch?

I think I'm waiting for my account to be added


Updated benchmarks

@sullivancolin I just ran the benchmarks from #18 on my computer. Interestingly, I see duckdb performing significantly better than polars on my machine. I ran this a couple times, and that result was consistent. I did update polars to 0.8.15 since 0.8.14 was yanked. Maybe that accounts for the perf difference? I also had to increase docker shared memory on machine to 10 GB. Modin continues to show poor performance.

Weird.  I just rain the main branch in Docker and got similar results to what I showed in the PR thread.  I also am using Intel core i7.  I have 12 cores with 32 GB of rame.


Title: Failed to Load Speech Detection Module

Description
We're currently experiencing an issue where the speech detection module fails to load properly. This is causing the voice activity detection (VAD) functionality to be unavailable, which significantly impacts the user experience of our application.
Steps to Reproduce

Launch the application
Attempt to use any feature that requires speech detection
Observe that the speech detection fails to initialize

Expected Behavior
The speech detection module should load successfully, allowing users to interact with voice-activated features.
Actual Behavior
The speech detection module fails to load, rendering voice-activated features unusable.
Impact
This issue is critical as it affects a core functionality of our application. Users are unable to use voice-activated features, which significantly degrades the user experience.
Please investigate and provide any insights or potential solutions. Let me know if you need any additional information or clarification.

Hi there - what OS and browser are you getting that error on?

Closing this - feel free to re-open if anyone can reproduce this with more information.


Migrate Ionic & Capacitor plugins + Refactor & Update

Summary of changes:

This PR re-introduce Ionic & Capacitor plugins into the repository
Refactor the capacitor and ionic-angular plugins

Drop the application generator in favor of a configuration generator that takes an existing app instead of generating a new one so we delegate application creation to the user and let him choose his configuration
Update generated Capacitor and Ionic versions

[!NOTE]
The ionic-react project was not touched in this PR, it still exposes an application generator that generates a new application and configures ionic for it. What do we want to do with this package?

TODO

Inference Plugin for Capacitor
Eventually an Inference Plugin for Ionic (would that be useful to cover the Ionic CLI through Nx tasks?)
Manual tests in an Nx repo

@edbzn I would drop the generator for the react app as well. If we want to keep the ionic-angular and ionic-react packages I would keep the layer they bring in as small as possible. What do you think?

Looks good so far :-) you need to rebase once, we updated the Nx version to 19.4. No changes except the version.
See the discussion here: #1101
We want to go the next updates with all plugins reintegrated first

I just realized the new configuration generator for Angular should do more than what it does actually if we want proper configuration setup, here's what I think is missing:

app.component.ts should be updated to include imports: [IonApp, IonRouterOutlet]
src/theme/variables.scss should be created
src/global.scss should be updated with proper ionic imports
index.html should be updated with proper meta tags
main.ts should be updated to include required ionic routing providers
src/app/app.component.html should be updated to include required ionic app component + router


Use polymorphic relationship

Could be useful for issuing tokens for organization accounts.

I think that a better idea would be the ability to change the Personal Access Token model like Passport: https://laravel.com/docs/5.8/passport#overriding-default-models
It is already in https://github.com/laravel/airlock/pull/18

@rennokki Correct me if I'm wrong, changing the personal access token model will allow you to issue token to another model than the user one but not several models, right?

Create a new model App\MyCustomTokenModel that extends the base model and replace the user() relation:
<?php

namespace App;

use Laravel\Airlock\PersonalAccessToken;

class MyCustomTokenModel extends PersonalAccessToken
{
    public function user()
    {
        // this will be your model
        return $this->morphTo();
    }
}

Make use of the function in boot():
use App\MyCustomTokenModel;
use Laravel\Airlock\Airlock;

Airlock::usePersonalAccessTokenModel(
    MyCustomTokenModel::class
);

Make sure you ignore the migrations in the register() in AppServiceProvider.php:
use Laravel\Airlock\Airlock;

Airlock::ignoreMigrations();

Publish the migrations or copy the migration file from the package in your database/migraitons/ folder and replace the user_id field with a morph field:
Schema::create('personal_access_tokens', function (Blueprint $table) {
    ...

    $table->morphs('model');

    ...
});

In your model (either it's User, Organisation or whatever) that uses the HasApiTokens trait in use, replace the tokens() method to make use of the morphMany:
use Laravel\Airlock\Airlock;

public function tokens()
{
    return $this->morphMany(Airlock::$personalAccessTokenModel, 'model');
}

Jobs done.

IMHO it would be simpler that Airlock handle this out of the box using a polymorphic relationship :) Your solution works but it's a bit of extra work for a common use case.

I took Passport's example on this case. I think stuff should be simple out-of-the-box. :male_shrug:

I agree to this, I was struggling to customize Laravel Passport to support polymorphic relationship. And I still resolve to use custom HTTP Header hack to get around it.
See laravel/passport#161

https://github.com/laravel/passport/issues/1006

@taylorotwell Would you accept a PR for this?


Bump version number in cmake.

PR Summary
@Yurlungur @rbberger creating a release version from the printf stuff.

PR Checklist

[x] Any changes to code are appropriately documented.
[x] Code is formatted.
[x] Install test passes.
[x] Docs build.
[x] If preparing for a new release, update the version in cmake.

@rbberger will this trigger Richard's Robots 🤖 ® ™ ?!

@rbberger will this trigger Richard's Robots 🤖 ® ™ ?!

:robot: Beep Beep Beep. No changes in spack-repo/packages found. Going back to sleep.

@dholladay00 right now this only happens after the release, since that's when you have the release commit to add for the spackage.

I will click the button and then trigger a new release. Be prepared for robots.


Commands not working

Hi!
I recently discovered your bot and wanted to set it up before the school year started. (I am self hosting it)
When I tried the commands, none of them work. I gave the bot the highest role with admin, and made sure the bot could read and send messages in all channels. Everything in Config is set up correctly, and I did not mess with any other files.
Could you help me fix this problem? Thank you.

Yeah sure! Can you describe what exactly is going wrong or any error messages?

The bot is not sending any output to my commands. It is not sending anything at all. I tried using multiple different bots, on different servers. I don't know if it's something with how I set up the bots or if I configured something wrong.

Did you use your actual Discord ID? The string of numbers you get by @'ing yourself and putting a backslash "" before the tag?
Atelier is designed to ignore every message that doesn't match that ID in the backend to comply with Canvas LMI ToS.

Thanks, that was the problem. I was using the bot's ID instead of mine. Thanks for the help!

Also, before this is closed, is there a way to get multiple users to be able to use the bot at once?

In the main directory, in index.js, on line 29, removing the check (msg.author.id != discordUserID) will allow anyone to interact with it.
Feel free to let me know about any new issues. I actually have been polishing up the bot a lot and fixing things here and there myself, so I'll try to release it before September when I'll be busy.

Thank you :)


Replace local web server setup for web editor with a Python-based solution

Follow-up to https://github.com/godotengine/godot/pull/56977.
This makes it easier to set up, as you always have Python installed when building Godot. On the other hand, you don't always have Node.js + npm installed (and you may not want to spend time running npm install).
I tested this locally and made sure it works.
Future improvements:

[x] Add a serve=yes SCons option that automatically extracts the generated ZIP and calls the serve script after building. (This would only work when using platform=javascript.)

Done in https://github.com/godotengine/godot/pull/67325

[x] Document building and usage instructions for all platforms (I'll do this in separate PRs, both for the main repository and godot-docs).

Done in https://github.com/godotengine/godot/pull/64889 and https://github.com/godotengine/godot/pull/64886.

I applied the suggestions and added help messages for command line options (visible with --help or -h).

@Calinou you seem to have deleted the whole package.json which is used for linting and docs.
Only the serve dependency should be removed (and the package.lock updated accordingly).

@Calinou you seem to have deleted the whole package.json which is used for linting and docs. Only the serve dependency should be removed (and the package.lock updated accordingly).

Fixed. I also renamed the .gitignore path so it ignores node_modules/ correctly.

Thanks!

Cherry-picked for 3.6.


Fix some Bulgarian translations

This change fixes some of the Bulgarian translations that still had
English in them and adds a few missing translations.

Looks great, thanks 👍


Implement Graph Memory in AI Assistant

Description
This pull request adds a new Jupyter notebook to the mem0 cookbook, demonstrating an AI companion application that utilizes mem0's graph memory capabilities. The notebook showcases how to create an interactive AI assistant that can remember and recall information from previous conversations using OpenAI's GPT-4 model and mem0's memory system.
Key features:

Integration of OpenAI's GPT-4 with mem0's memory management
Utilization of Qdrant for vector storage and Neo4j for graph storage
Interactive conversation loop with memory retention and retrieval

This addition aims to provide mem0 users with a practical example of building an AI companion system, highlighting the power of graph-based memory in conversational AI applications.
Fixes # (No specific issue number, as this is a new feature addition)
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] Documentation update

How Has This Been Tested?
The notebook has been tested in Google Colab environment. To reproduce:

Open the notebook in Google Colab
Set up the required environment variables using Google Colab's userdata
Run all cells sequentially
Test the interactive conversation loop with various inputs

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #xxxx (Not applicable for this new feature addition)
[ ] Made sure Checks passed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add Versioning support for API Products

Problem
When an API Product developer wants to change an operational behaviour of an already published API product as per their new business requirement, for such as authentication mechanism, resources, business plans, etc, currently WSO2 API-M does not have a proper mechanism at API product support, unless the change is made directly in to the deployed API product. But, this may directly affect the API product consumers’ functionalities in their applications and can have disastrous effects on end user’s downstream products and services.
Solution
The solution is to add versioning support for API products and  we plan to support the following sub-features to provide the proper versioning experience for API product developers.

Allow API developers to create a new api product version from an existing API product and allow to add version number during API Product creation.

Allow API developers to invoke the api product resources without specifying the version number by Introducing default version support

Allow API developers to select two options  during life cycle management of an API Product Deprecate old versions after publishing the API Products and Require re-subscription by when publishing API Products.

Product developer to receive notification of API Product version creation
Support context versioning for API Products in order to allow users to define the API Product  version as a parameter of its context by adding the {version} into the context.

Allow API developers to manage their API product versions with different environments through WSO2 API CTL.

Affected Component
APIM
Version
4.3.0
Implementation
Followings are the sub tasks to achieve the whole versioning support for API Product version

[x] Initial discussion to finalize the scope of versioning support for API Products feature
[x] Prepare an initial design documentation for the versioning support to API Products

Backend Changes to support api product versioning

[x] #2179 (Support new version create, update, delete flows)
[x] Support default version for API Products
[x] Support lifecycle checklist for API products (Show lifecycle checklist for new API Product versions,  add the capability to deprecate old versions or  copy subscription during APIProduct publish based on the  checklist status )
[x] Support context versioning for API Products
[x] Display correct published default version of API product at devportal
[x] Enable email notifications for subscribers to receive notification of creation of a new version of APIProduct

UI modification for api product versioning suppport
Publisher UI modifications

[x] Add version field into API Product creation form
[x] Display API Product Version at product overview page
[x] Add option to "create new version from existing API product" at overview page
[x] Add default version option at basic info in design configuration page
[x] Enable two options  Deprecate old versions after publishing the API Products and require re-subscription by when publishing API Products at life cycle management UI
[x]  version support at tryout console for API Products

####Other

[x] #2205

Tests and Documentation_

[x] Manual Testing all the use cases related to API product versioning support
[x] Unit tests for the backend code changes
[x] UI tests for API Product versioning support
[x] Integration tests for the API Products versioning
[ ] #2291

Related Issues
Similar issue: https://github.com/wso2/product-apim/issues/6971
Suggested Labels
No response

Progress Update
11th of Monday  2023 - 15th of Friday

Finalized the scope
Prepared initial design documentation [1]
Started REST API implementation

[1] https://docs.google.com/document/d/1cf-LazqdytaybVuHoiF8LUIiP8ENgwiaPCbWZGWF6Vo/edit?usp=sharing

Progress Update
18h of Monday  2023 - 22nd of Friday (5 days)
BackEnd Implemetation

Completed  Create/update/Delete  REST APIs for  New  API Products Version support
Completed the default version support for API Products

FrontEnd Implemetation

Made the UI changes to enable version field in the API Product creation form
Added UI changes to create new version from existing API product
Made changes in Product overview to show version
Enable default version option at API Product basic info

Ongoing

Testing the functionalities related to the above, completed task list (FrontEnd-BackEnd integration)

[1] https://docs.google.com/document/d/1cf-LazqdytaybVuHoiF8LUIiP8ENgwiaPCbWZGWF6Vo/edit?usp=sharing

Progress Update
25th of Sep  2023 - 27th of Sep 2023 (3 days)

Tested the end to end API Product versioning related  functionalities at publisher and fixed the issues.

Backend
I. Added changes to support context versioning for API Products
II. Modification on APIProduct listing Rest API to append context without version
III. Modification on API Product deployment flow (Bind version in to generated synapse API of API Products)
Front End
I. UI changes to display version at API tile during API Product listing and unified search
II. UI Changes on life cycle page to display life cycle check list for new API Product versions
Ongoing Testing as below.

Display multiple versions at devportal and verify their invocation.
Display default version at developer portal and invoke without version at url.

Progress Update
2nd of Oct  2023 - 6th of Oct 2023 (5 days)

Added backend changes to enable email notifications of new version creation of API Products

Added UI changes to API Products publisher tryout console to support versioning

Provided version support for API products in apictl

Identified testing scenarios and manually verified below
I. Create/update/deleted API products with mutiple versions
II Life Cycle support for API products based on the checklist to deprecate old versions or copy subscriptions  or both options
III Deploy revisions of new API product versions and invoke at publisher and devportal
IV Display multiple versions at devportal and verify their invocation.
V Display default version at developer portal and invoke without version at url.

Ongoing/ pending testing usecases.

Testing API product use cases on apictl tool and fixing issues.
Unit tests/integration tests/Documentation

PRs of the feature can be found at below.
[1] carbon-apimgt: https://github.com/wso2/carbon-apimgt/pull/12168
[2] apim-apps: https://github.com/wso2/apim-apps/pull/506
[3] product-apim-tooling: https://github.com/wso2/product-apim-tooling/pull/1022

Code Review of the feature is completed on last week and latest PRs are now available for the further review. The migration is handled from the codebase it self. We can port the available fixes to API-M 4.2.0 without any issue.
Only tests and documentation are pending to complete the feature.
@nandika please note.

We have noticed few issues for old API Products when porting the fixes into 4.2.0.
How do migrated API products work?

As @SavinduDimal worked on API Product Versioning support for API-M 4.2.0, we noticed some blockers during testing phase and introduced some changes to work migrated API Product as it is.  Following are some of key highlights.

By default, isDefaultVersion=true for all API products (Migrated and new API Products )
Migrated API products are identified by the value of the ContextTemplate which is stored at AM_API table in AM_DB
(It is null for old API Products since versioning didn't support for older APIM versions)
Migrated API Products should be able to identify with it's value of publishedDefaultVersion (If revision has been already deployed and ContextTemplate=null => IsPublishedDefaultVersion = true and publishedDefaultVersion=1.0.0)

Closing the issue since all tasks are completed


Update Overview.md

Mention that Orleans v2 does not support multi-cluster.

Docs Build status updates of commit fc1724b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

src/docs/deployment/multi-cluster_support/Overview.md
:bulb:Suggestion
View
Details

src/docs/deployment/multi-cluster_support/Overview.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 29, Column 1: [Suggestion: sensitive-language-ma - See documentation] Term 'master branch' is sensitive and should not be used in content or code. Usage: 'rs, and/or when it is written to storage frequently. Support for log-view grains is not part of the master branch yet. We have a prerelease including samples and a bit of documentation in the [geo-orleans branch]('

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Closed by https://github.com/dotnet/docs/pull/28582


[BUG] Issues with matching title when reference exists

Referring to 5. in https://github.com/Refemi/refemi_front/issues/88:
When you write a title that matches an existing reference but does not match the punctuation, it doesn't suggest it.
I think we should make the comparaison without punctuation.
Moreover, passed a certain number of characters the matching test does not work anymore

I open a PR about a issue I just created on the API to solve the problem you report.
I did some tests, especially with the research you left in the image, and it works normally now
I will also send the PR of the branch I just created to correct the index of the country selection

I open a PR about a issue I just created on the API to solve the problem you report. I did some tests, especially with the research you left in the image, and it works normally now
I will also send the PR of the branch I just created to correct the index of the country selection

Backend PR validated. I'm at work and don't have access to DB so, I'm unable to properly test it. The code looked good though.
Could you test different scenarios (title with space, with special character, with accent, with misspelling, very long, very short (when does the search start?), etc).
Also please comment on the criteria that the search uses. If you notice some stuff that could be improved, we can add a TODO for later!

To answer your comment @Laura, the selection of the search is rather simple, namely which search occurrence LIKE %search%' previously transformed with the lower` function.
I did as many searches as possible based on existing reference names, and the presence of special characters is not a problem to get a relevant result


Distribute engine as Flutter.xcframework

Xcode 11 (minimum required version in Flutter) introduced the .xcframework for distributing frameworks for multiple platforms and architectures. At build time, the correct version of the framework is linked on.  An XCFramework is already being used for add-to-app with the flutter build ios-framework --xcframework flag.
As Apple is increasing the number of architectures available for each platform (Catalyst as iOS apps on macOS, arm64 macOS) having one bundle containing all available architectures would reduce logic for the tool.  Particularly, no more re-copying the framework into the project when platforms architecture changes (still needs to be done per build mode), and no more lipo to remove unused architectures.
As an additional bonus, Flutter.xcframework can be distributed as a Swift Package as of Xcode 12.  See https://github.com/flutter/flutter/issues/33850#issuecomment-647758430
With https://github.com/flutter/flutter/pull/51453 iOS linking and embedding logic has moved into the tool, so there won't be migration needed for existing projects.

Update LUCI recipes to create a Flutter.xcframework instead of a Flutter.framework.  Still need them separated for Debug, Profile, and Release.
Flutter.podspec would need to change to s.vendored_frameworks = 'Flutter.xcframework'
Minimum required CocoaPods version in the tool would become 1.9 to handle that vendored xcframework.

See also https://github.com/flutter/flutter/issues/36204 for App.xcframework (not dependencies, this work can be done while still generating App.framework).
https://github.com/flutter/flutter/issues/56581 is a dependency to do the same trick for FlutterMacOS.xcframework

Just curious, why with Xcode 12 CocoaPods is still needed? What's missing to use only SPM?

What's missing to use only SPM?

See https://github.com/flutter/flutter/issues/33850

See https://github.com/jmagman/engine/blob/588d6a343bcb5423e89cab15556126416c490c6c/sky/tools/create_ios_framework.py#L71-L79


Handling LV_SIGNAL_PRESS_LOST

I had originally planned to be able to press a button to activate a motor, then upon release of that button deactivate the motor. As such I added callbacks for LV_BTN_ACTION_PR & LV_BTN_ACTION_CLICK.
However if I press a button and then slide my finger off of it, the button deactivates and the motor stays activated.
Is there something I can do to capture the button press being lost? I know in the input feedback function I have shoehorned in I can detect the LV_SIGNAL_PRESS_LOST, however that's without the context of the button, and not through the typical lv_btn_set_action() API.
I'd rather not depend upon the periodical signalling of a held button, nor would I prefer to hack together a solution that uses my input feedback function to catch the action.
Would it be possible to easily increase the action[] callback list to respond to the press being lost? or would the current architecture make that difficult/messy?

Hi,
You can extend the signal function of the button like this:

/*Global declarations*/
static lv_signal_func_t btn_signal;
static lv_res_t my_btn_signal(lv_obj_t * btn, lv_signal_t sign, void * param);

...

    lv_obj_t * btn = lv_btn_create(lv_scr_act(), NULL);
    btn_signal = lv_obj_get_signal_func(btn);            /*Save the original signal function*/
    lv_obj_set_signal_func(btn, my_btn_signal);        /*Set a new signal function*/

...

static lv_res_t my_btn_signal(lv_obj_t * btn, lv_signal_t sign, void * param)
{
    lv_res_t res;

    /* Call the original signal function */
    res = btn_signal(btn, sign, param);
    if(res != LV_RES_OK) return res;

    /*Proces the signals*/
    if(sign == LV_SIGNAL_PRESS_LOST || sign == LV_SIGNAL_RELEASED) {
        printf("Press lost\n");
    }

    return res;
}

Is it working?

I should hopefully find out today or tomorrow. I've been finishing up the back end code so the GUI actually has something to call. I'll let you know

It does in fact work! Thanks :-D

Your welcome!
As it's not supported directly right now this small "hack" should be applied. In v6.0 the actions will be modified the include the triggering event in the callback function. It will provide more flexibility and "PRESS_LOST" can be added as well.
More info here: https://github.com/littlevgl/lvgl/issues/316


Scroll markdown preview with editor scroll

VSCode Version: 1.10.2
OS Version: macOS 10.12.3

Steps to Reproduce:

Begin editing a markdown file
Open side by side markdown preview
Scroll editor window

There are two settings for scrolling under markdown:

markdown.preview.scrollPreviewWithEditorSelection
markdown.preview.scrollEditorWithPreview

It makes sense to also have a setting to scroll the preview window when the editor is scrolled. I always find myself scrolling the editor window expecting the preview to scroll with it.

Realized this is a duplicate of https://github.com/Microsoft/vscode/issues/19459.


Add hint

Associated Issue: #180
Summary of Changes

added hint for rebus 'hotkey'

Pull Request Test Coverage Report for Build 681

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

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


Questions related to configurations via CRDs.

Hello!
I got multiple questions if you let me, please. Using version 1.1.5 here. (Not connected to the WebUI console). Latest image.

Do countryCode based exceptions work if using k8s with CRDs? I've seen the issue resolved, not in my case unfortunatelly.

What is the order of the exceptions? E.g. I got a policy that works for all the ingresses defined in my cluster. Since the limitation I define countryCode based rules in separate exception CRD.

---
apiVersion: openappsec.io/v1beta1
kind: Policy
metadata:
    name: open-webapp-best-practice-policy
spec:
    default:
        mode: prevent
        practices:
            - webapp-best-practice
        triggers:
            - appsec-special-log-trigger
        custom-response: 403-forbidden
        exceptions:
            - appsec-exception-country-code # drop ES (Spain)
            - appsec-exception-general # accept "/wp-(.*)"
---
apiVersion: openappsec.io/v1beta1
kind: Exception
metadata:
  name: appsec-exception-general
spec:
  - action: accept
    comment: Allow wp
    url:
      - "/wp-(.*)"
---
apiVersion: openappsec.io/v1beta1
kind: Exception
metadata:
  name: appsec-exception-country-code
spec:
  - action: drop
    countryCode:
      - ES # Spain

What happens to one requesting https://example.com/wp-admin from Spain? Would he be dropped or accepted?
Didn't find the explanation for the CRD case on the website, sorry.

Today we faced DDoS attack and couldn't do anything with it since country based rules didn't work and there are no CRDs to define DDoS mitigations rules too. :< Tbh, my boss was mad -.-' Unfortunatelly, I cannot use your WebUI space because of the company security policies.

Hi @5hin0bi,

Yes, country code exceptions should be fixed.
Exception order is from strictest (Drop) to less strict (Accept), we're looking into recreating your set-up to check your-use case, could you please confirm those are the same exceptions you used in production?
My apologies, we're working on a new CRD version that will include rate limiting, and hope to publish it soon.

Best regards,
open-appsec team

Hi @orianelou,

Thanks for your answer, upgraded to 1.1.6 just in case, still no luck though.
Thank you, much clearer now. Yes, we used the same setup last time when faced ddos attack (I've seen most IPs were from Spain according to the MMDB). Now it's gone so I've yet excluded the country based exception from the policy exceptions array.
Thank you for your efforts!

Hi @5hin0bi, are you able to implement GeoIP blocking using CRDs alone?
We too are currently not in a position to use the WebUI for prod but for testing purpose we were able to make use of it. It worked when we made use of managed mode with the webui and the scripts. but using just plain CRDs creating exception in policy we are not able to achieve the same. Any help?


Do we actually need matplotlib and pandas in requirements.txt?

If not, please remove them.
To test if they are necessary, I suggest making a new virtualenv without installing matplotlib and pandas and seeing if you can install from the setup.py

Create a new virtual environment
python3 -m venv banditpam
cd banditpam
sorce bin/activate

Clone the BanditPAM repo
git clone https://github.com/ThrunGroup/BanditPAM.git

(banditpam) % pip list
Package    Version

pip        10.0.1
setuptools 39.0.1
You are using pip version 10.0.1, however version 21.2.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
(banditpam) dhavaldangaria@Dhavals-MacBook-Pro BanditPAM %

4)Removed Matplotlib and Pandas
(banditpam) dhavaldangaria@Dhavals-MacBook-Pro BanditPAM % cat requirements.txt
pybind11>=2.5.0
numpy>=1.16.2

Build the BanditPAM

/BanditPAM/: git submodule update --init --recursive
/BanditPAM/: cd headers/carma
/BanditPAM/: mkdir build && cd build && cmake .. && make && sudo make install
/BanditPAM/: cd ../../..
/BanditPAM/: pip install -r requirements.txt
/BanditPAM/: sudo pip install .

Installing collected packages: BanditPAM
Running setup.py install for BanditPAM ... done
Successfully installed BanditPAM-0.0.35

Though matplotlib and pandas are not necessary for the BanditPAM installation, they are used in test cases.


Read mails are marked as unread after downloading complete message

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.301
Where did you get the app from?
Google Play
Android version
12
Device model
Samsung Galaxy S10
Steps to reproduce

open unread email
click on "download complete message"
close email by using back button on your phone

Expected behavior
Email should be marked as read email.
Actual behavior
Email is still marked as unread email.
Only if i open the downloaded email again, then the email is finally marked as read.
Logs
k9mail-logs.txt

I just tested it on 6.303 and there it seems to work: S7 edge

No. Problem still exist on 6.302 an 6.303.

I can confirm this bug with 6.602 (F-Droid) and pop3.


Could you help me run ONNC 0.9.3 on the Ubuntu?

I already take follow this pages ( https://github.com/ONNC/onnc) from Basic instruction. but it is many errors.
This is errors

Can you help me step by step run it?
Thank you so much!

please follow the new document which might be helpful


pipe to proc

Does shelljs have something to simulate "command1 | command2"?
A possible usage:
echo(mylist.join('\n')).pipe('egrep "[0-9]"')

FWIW, I just cloned the repo with the same question in mind.  The following command
grep -ir "pipe" ./

the word pipe only showed up three times in src/test.js and once in the README.  My guess to this question then is "no"

Well, lets design it?
My pipe example method is not a good solution. This design asks the pipe parameter to be a shell command to be executes like exec does. How to use built-in sed and grep?
A solution may write pipe as a context object for other shelljs filter methods:
ls('/tmp').pipe().exec('grep "[0-9]"')  // system grep
ls('/tmp').pipe().grep('[0-9]')         // built-in grep

May pipe be configured? If not pipe can be implemented as a getter and the () is useless.
A simpler way:
All output by shelljs method must be a instance of Piped and that has sed, grep, cat, to, toEnd,  and pipe methods. This will result in a simpler jQuery like code:
ls('/tmp').pipe('grep "[0-9]"')  // filter first output by any system command
ls('/tmp').grep('[0-9]')         // filter first output by built-in filter methods
ls('/tmp').grep('[0-9]').sed('-r', 's/\.[^.]+$//').cat() // list numbered files without extension

@aurium - so from your experience, is there anyway to do something like this, as you were suggesting?
ls('/tmp').grep('[0-9]').sed('-r', 's/\.[^.]+$//').cat() // list numbered files without extension

Yes @bradparks!
That is pretty easy... Please see this gist with an implementation example:
https://gist.github.com/aurium/c913c85c45725814bf17

@aurium - sweet! thanks so much for taking the time to link to this... much appreciated!

:thumbsup:

I'd say this is a pretty major missing feature

:+1:

Any work on a PR for this? I'm personally interested in this feature, and would be willing to help develop a PR

@nfischer with 25 open PRs how likely is a PR to be merged? Perhaps the project owners need help?

@chrishiestand I agree it's a bit of an issue. It looks to me like the maintainer was in the process of setting this up to receive more help (making the shelljs organization), but it looks like he never finished. I think all we can do as a community is develop useful features in the mean time and try to resolve any issues we can.
Perhaps we could start a new thread discussing future maintenance of the project to assist @arturadib?

I wanted to ping this thread to say that it looks like we might be able to start merging some PRs in the next couple weeks. So if someone wanted to take this feature on, I'd be very interested in reviewing it and possibly merging.
I can also help develop the PR, but probably won't be able to start work on it for a little while. @aurium are you still interested in working on this?

Yeah, me and @nfischer can now merge PRs, so any new ones will be merged ASAP, and we'll try to to get through the backlog.

Also, I'll be opening a PR soon that will allow for pipes! So stay tuned (I just have some bugs to fix first).

So for my implementation, I opted to go with the syntax:
echo('foo'); // regular command
echo('foo').cat(); // echo foo | cat (which actually does the same thing)
echo('foo\nbar').grep('o').cat(); // echo -e 'foo\nbar' | grep 'o' | cat

The following commands can be on the right side of a pipe (almost anything can be on the left):

cat
grep
sed

Is this agreeable/intuitive to everyone? I still have some bugs to resolve, but after that I'll try to push the PR.

Can exec be on the right too?

Nice @nfischer! Can exec be on the right too? +1

I will look into this. Thanks for mentioning

exec would be really nice for portable ways of building e.g. uglified browserify bundles (if you want to opt out of gulp/grunt):
browserify entry.js | uglifyjs > bundle.js

It would be nice then to have access to the .to on the right-hand side as well. Either directly from exec or through cat:
const bundler = exec('browserify entry.js').exec('uglifyjs');
bundler.to('bundle.js');
// or
bundler.cat().to('bundle.js');

In the latter case you probably want cat to be silent (or at least mute it through options), as you really don't want the bundle.js content dumped to stdout. I'm not really sure about the details though. It's a usecase that I would believe would be quite common and really nice to have.

@myme thanks for providing a use case! I'll look into doing this.
This should be very easy to do for async exec(). I'll see if I can figure out a hack for synchronous exec() as well. If I can't get both, I'll do a PR for pipes for the utilities I've mentioned and ask for a contribution for exec() support.

Marking this as blocked by #360, since I think it's cleanest to get that dealt with first

I have an implementation of pipes out for review. If any of you all are interested in reviewing #370, please take a look. I even found a way to put exec() on the right-hand side of pipes, as requested.
Also, thanks to @aurium for the inspiration for how to design the pipes interface :+1:

:clap: :clap: :clap: :clap:


Fix python module runtime bootstrap

This is just the last iteration of an attempt to understand what's needed to bootstrap an sdk runtime. Pushing for sharing and passing context.
Added a few vars to error messages in core/module.go and core/schema/module.go to make it easier to debug.
\cc @sipsma

Fixed in #5900


Security issue with normalize-url package

What package(s) are you using?

[x] Cloud & Cognitive
[ ] Legacy/CDAI
[ ] Legacy/Security

Detailed description
The security scans has reported and issue that needs to be fixed for the upcoming release, the DCUT of which is by the end of this week.
Can someone look into this as a matter of priority?
Here's the screenshot showing where this pacakage is being used:

Describe in detail the issue you're having.

Is this issue related to a specific component?

What did you expect to happen? What happened instead? What would you like to
see changed?

What browser are you working in?

What version of the @carbon/ibm-cloud-cognitive packge are you using?

What offering/product do you work on? Any pressing ship or release dates we
should be aware of?

Steps to reproduce the issue

Step one
Step two
Step three
etc.

Please create a reduced test case in CodeSandbox
https://codesandbox.io/s/github/carbon-design-system/ibm-cloud-cognitive/tree/main/examples/codesandbox

Additional information

Screenshots or code
Notes

@murtdagi Thank you for bringing this to our attention.
You mention that a security scan has reported an issue, but you haven't actually told us what the issue is. I presume from the screen shot that you included that it is something about normalize-url v.4.5.0. Can you tell us what security scan you're referring to, and what it says about normalize-url? Does it give some kind of message? Is there a link to more information about the security issue?

@murtdagi PS I notice that cacheable-request v7.0.2 was published on June 9th, and this updates its dependency to<EMAIL_ADDRESS>If you remove your yarn.lock (or package-lock.json) file and run yarn install (or npm install) you should find that the dependency of got v11.8.2 now gets fulfilled by cacheable-request v7.0.2, and the dependency of that gets fulfilled by normalize-url v6.1.0, and this will hopefully resolve the security scan issue you're seeing.

Sorry for the delay @dcwarwick, we've been using this discussion as the focal point for these reports: https://github.com/carbon-design-system/carbon/discussions/8587
On our end, we'll make sure dependencies are up-to-date but most likely this will continue to pop up given the nature of static security analysis at the moment.

Thanks for the update


chore: min_lines required: false

PR-Codex overview
This PR updates the min_lines input in the action.yml file to be optional.
Detailed summary

Updated min_lines input in action.yml to be optional instead of required

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 3min)

@rultor release, tag is 0.0.15

@rultor release, tag is 0.0.15

@h1alexbel I'm sorry, I don't understand you :( Check this page and try again please

@rultor release, tag is 0.0.16

@rultor release, tag is 0.0.16

@h1alexbel Invalid release tag 0.0.16 specified. There is already a release 0.0.16 newer than the given release in this repository.

@rultor release, tag is 0.0.16

@h1alexbel I'm sorry, I don't understand you :( Check this page and try again please

@rultor release, tag is 0.0.17

@rultor release, tag is 0.0.17

@h1alexbel OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.17

@h1alexbel Done! FYI, the full log is here (took me 4min)


Testing validations on date picker

I am currently trying to test validations on a form where I am using react-bootstrap-date-picker however I am having a couple of issues.
In the view I can see that the validations are working correctly, but in the tests something isn't quite right.
I am using react-addons-test-utils Simulate like this:
Simulate.change(formFields[2], { target: { value: '04/01/2017' } }); in this instance formFields[2] is the date picker however unlike other input fields when I log the value out to the console it is still blank, I was wondering if anyone has a working test example for something like this that could point me in the right direction?

I'm not sure we'll be able to help without a lot more context. Feel free to open another issue if you're still running into this problem.


create dummy LLM to enable quick testing of modules

Add dummy LLM module, whichs mocks real LLM interface.
This enables testing for free in terms of time and money

fixed by #22


Create an image release pipeline

Create a Image release CI pipeline could make image release process easier.
For example:
every time we git push a release-vxxx.xxx.xxx the the build environment (e.g., a ec2 instance that already instealled all building tool like buildah, kubectl, jq, yq, helm) could detect a new release branch has been created, it will run the  ./scripts/release-controller.sh and publish the new version image

And also need to do some test in that CI pipeline for example:

make presubmit
do  kubectl apply -f examples/deploy-${NEW_VERSION}.yaml and then do make e2etest
do  helm install gateway-api-controller --version=${NEW_VERSION} and then do make e2etest


Populate ClientCAs field in Server TLS config

This PR achieves a gRPC Go echo client and server that uses an actual implementation of TransportCredentials interface to establish an mTLS connection, by populating ClientCAs locally, in the server config, in the tls config store library.
To elaborate on the TODO in the code, the crypto/tls ClientAuth field in the crypto/tls Config has several values:
(1) NoClientCert
(2) RequestClientCert
(3) RequireAnyClientCert
(4) VerifyClientCertIfGiven
(5) RequireAndVerifyClientCert
As per the documentation for VerifyPeerCertificate, if in the server config, ClientAuth is set to RequestClientCert or RequireAnyClientCert, crypto/tls skips normal verification. If ClientAuth is set to VerifyClientCertIfGiven or RequireAndVerifyClientCert, crypto/tls performs normal verification before calling the function given in VerifyPeerCertificate. The crypto/tls normal verification requires that ClientCAs be populated, if not, then normal verification failed, the VerifyPeerCertificate custom implementation never gets called, and the server tls handshake fails.
With our use of S2Av2 for the populating the server TLS config there are some things we can do;

Never populate ClientAuth with a value that triggers the crypto/tls normal verification process(always set it to RequestClientCert or RequireAnyClientCert). VerifyPeerCertificate will still be called in this case, but the verifiedchains parameters will be nil.
Add a field called ClientCAs to the ServerTLSConfiguration, and use it in the client libraries, whenever S2Av2 sets request_client_certificate to REQUEST_AND_VERIFY.

Go echo client / server using actual implementation of transport credentials to establish an mTLS connection:
bazel run fakes2av2_server

bazel run server

bazel run client


playRunHooks ClassNotFoundException re: sbt-yeoman GruntProcess

Play version: 2.3.8
Scala version: 2.11.1
sbt-yeoman: 0.7.1
using a build.sbt file
When using play-yeoman the addition of the GruntProcess to the playRunHooks setting causes a ClassNotFoundException during execution of the playRun task or show playRunHooks.
In order to add an additional PlayRunHook instances to playRunHooks it current requires setting playRunHooks := Seq() in the build.sbt file to remove the play-yeoman hook.
show playRunHooks output:
[trace] Stack trace suppressed: run last *:playRunHooks for the full output.
[error] (*:playRunHooks) java.lang.NoClassDefFoundError: play/PlayRunHook$class
[error] Total time: 0 s, completed Mar 28, 2015 4:48:14 PM

last *:playRunHooks output:
Caused by: java.lang.ClassNotFoundException: play.PlayRunHook$class
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at com.tuplejump.sbt.yeoman.Yeoman$Grunt$GruntProcess$2$.<init>(Yeoman.scala:160)
        at com.tuplejump.sbt.yeoman.Yeoman$Grunt$.GruntProcess$1$lzycompute(Yeoman.scala:160)
        at com.tuplejump.sbt.yeoman.Yeoman$Grunt$.GruntProcess$1(Yeoman.scala:160)
        at com.tuplejump.sbt.yeoman.Yeoman$Grunt$.apply(Yeoman.scala:174)
...
[error] (*:playRunHooks) java.lang.NoClassDefFoundError: play/PlayRunHook$class

Same happening with me. Any workaround to get it working?

Yea, I created my own grunt play run hook based on the one in play-yeoman as a temp solution. With this one you need to specify the grunt task to run. I did this since I use browserify with watchify and needed a custom task that runs browserify before watch.
https://gist.github.com/qberticus/232e821bc7ec6417fe69

Thanks for the reply. When I add the content from the gist to the build.sbt, I got the following error:
playRunHooks := Seq()
^
[error] Type error in expression

Do you have any idea what went wrong?

Found the import that was missing
import play.PlayImport.PlayKeys.playRunHooks
Thanks for your help on this :)

Thank you for your fix! I will try that as I had the same issue.
Would it be possible for you @qberticus to make a pull request with your playHook?


#798 - PackageReivsion deletionProposed sometimes deletes the packageRevision

resolves https://github.com/nephio-project/nephio/issues/798
This change sends a notification of packageRevision change before creating packageRev to avoid the race condition of an invalid ownerRef uid for packageRev, which causes k8s to add a deletionTimestamp to the packageRevs.

/retest

I may be wrong, but it seems to me that by deleting those lines from code you removed two functionality from porch:

OwnerReferences set to a PackageRevision object (e.g. by a PackageVariant) are no longer stored in the metadata store. That means if e.g. the porch server is restarted, those OwnerReferences are lost forever (preventing this is the reason why we have a metadata store in the first place)
The internal metadata store CR (kind: PackageRev) doesn't have an ownerReference to its parent PackageRevsision object any more. That ownerReference also existed for a reason, among others to let the garbage collector know that if the PackageRevision is deleted it can also delete the PackageRev.

Could you elaborate  on the reasons and implications of removing these functionalities?

I may be wrong, but it seems to me that by deleting those lines from the code you removed the following functionality from porch: The internal metadata store CR (kind: PackageRev) doesn't have an ownerReference to its parent PackageRevision object any more. That ownerReference exists mainly to let the garbage collector know that if the PackageRevision is deleted it can also delete the PackageRev.
Could you elaborate on the reasons and implications of removing this functionality?

Hey @kispaljr, thanks for your feedback.
The issue is that after an approve, when the 'main' twin gets created, intermittently, k8s adds the deletionTimestamp to it.
The suspect seemed to be the ownerRefs. Sometimes k8s sees the ownerRefs before the pkgrev is created and it looks at the pkgrev as an orphan. So upon a propose-delete, porch checks if the pkgRev has a deletionTimestamp and if it does, it removes the finalizer and calls for a delete of the pkgrev.

Thank you for the clarification. I think I understand it much better now.
Can we find a solution that keeps the ownerReference in the PackageRev pointing to the PackageRevision, but avoid the race condition at the same time?

In the latest commit, I've reverted the removal of the ownerRefs and changed the flow in repo.go to send a notification of the packagerevision change first before creation of the packageRev.

/approve

/approve

@kispaljr does the later changes address your concerns?

sorry, I haven't got the time to review the new version till now.
The current implementation is definitely an improvement, so I support merging it.
I still cannot see however, how this change guarantees that the parent PackageRevision exists in the porch server by the time the PackageRev is created in the etcd. Please note, that I am not saying that it doesn't guarantee it, I just don't see why, and I am afraid that it only decreases the probability of the race condition to happen by delaying the creation of PackageRevs with the time it takes to send out the notifications.
I guess all I am trying to say is that an explanation of how this solves the problem should be put in a comment in the code, so that developers would understand it easier.

Since as I stated there is no doubt that this is an improvement, and the solution was tested so we are sure that in practice it solves the original issue, please ignore my theoretical thoughts above and let's merge this.
/lgtm
/approve

Merge

Hey Istvan,
I tested this change with around 150-200 package revisions and couldn't reproduce the issue even once. When the cached repo is updated, it gives enough time for the pkgRev to use a valid uid I think.

Yeah, the race condition doesn't fully disappear. If the kube-controller-manager is processing through notifications from porch much slower than processing through notifiactions from kube-apiserver's pkgrev watch, the same issue can happen.
But this can happen between any 2 resources. I'll check whether there is a safeguard against this in the garbage collector.


Rework Rust runtime and builder

This PR reworks the builder and runtime to support the latest AWS lambda runtime which changed almost everything. Examples can be found in the examples folder.
Optimizations that will be considered in follow-up PRs:

Improve build caching by looking at https://github.com/Swatinem/rust-cache.
Merge handlers into one lambda. Build scripts might be a good solution for that.
CI setup

Just did a quick smoke test. Much better, good job, thanks!


Run your program

Hello @cirocosta,
I am struggling on how to launch your small program and perform the conversion of my classifier. I started recently node and I am not aware of how gulp works but I think it came from that.
I have copy-paste the 6-7 lines of your program in a new file index.js, changed the paths, installed the dependencies and then launch it with "node index.js" but it looks like the gulp default task it not launched. I am sure it is something stupid and straightforward and it would be nice to add it in the ReadMe for newbies with gulp like me :)

Hi @gilles-yvetot ! Thanks for reporting this.
That's true, it really lacks some documentation and non-gulp support (my bad). Using it along with gulp is actually a pretty easy thing:

install nodejs
install gulp globally (as you might want to use in other projects)
install the plugin (npm install --save-dev gulp-converter-tjs)
create a Gulpfile.js file and insert the example in the Readme (changing the src file and dest folder)
run the default gulp task ($ gulp in the terminal).

(gulp is a very cool thing to go with when developing with JS. Its somewhat like Make, Rake and other build tools but with a bunch of other cons - like its huge modularity, etc. This tutorial provides some guide!).

Maybe creating a converter-tjs repo with the proper CLI for it (and so, not requiring gulp) allowing piping stuff would be a great way (allow $ converter-tjs  claassifier.xml output.js and $ cat classifier.xml | converter-tjs > output.js). What do you think?
Thanks again!

Thanks again to you for the quick and clear answer!

Thats amazing @gilles-yvetot , you'll definetly enjoy! Also, feel free to contribute!


AWS OpenSearch Domain doesn't generate a unique physical resource name

What happened?
I’m deploying an AWS OpenSearch domain alongside my old AWS ElasticSearch domain, and there’s one very important difference in how the physical domain name is handled: for Elasticsearch, a unique suffix is appended to the logical resource name by Pulumi, which is great, and it follows the behavior of all other resources. For OpenSearch domain, however, this resource works differently:

the domainName (physical name) is now for some reason required (in other resources, it's always optional)

this essentially kills the ability to have the physical resource name be derived from the local name

The output of the 2 resources can be seen in this image. Elasticsearch clearly appends a unique ID, while Opensearch doesn't:

Steps to reproduce
The source code that will trigger the TS error is shown below:
import * as aws from "@pulumi/aws";

new aws.opensearch.Domain("example", {
    engineVersion: "OpenSearch_1.2",
    clusterConfig: {
        instanceType: "c5.xlarge.search"
    },
    ebsOptions: {
        ebsEnabled: true,
        volumeSize: 10,
        volumeType: "gp2"
    },
    advancedOptions: {
        "rest.action.multi.allow_explicit_index": "true"
    }
})

Expected Behavior
I expected the physical resource name to be optional, and auto-generated using the local resource name + unique ID, as in all other resources.
Actual Behavior
I see a TS error, which forces me to specify the physical resource name. I even tried disabling TS, but this check is also in the code, so it's not just a TS bug.
Versions used
CLI
Version      3.35.1
Go Version   go1.17.11
Go Compiler  gc

Plugins
NAME    VERSION
nodejs  unknown

Host
OS       darwin
Version  12.4
Arch     x86_64

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Ok, we need to support that autonaming happens on the domain_name parameter for this resource


General directive customization

Some directives are standalone, e.g.
# type STANDALONE
# fmt: off

Others come before the line (or statement) they affect
# type LEADING
# pyre-ignore: ...
import x

While others must happen at end of line
# type TRAILING_FIRST_LINE
from x import (  # isort:skip
  y,
  # type TRAILING
  z,  # noqa: F123
)  # hypothetical TRAILING_LAST_LINE

These basic types can be detected by prefix match and handled when ordering.  Right now leading comments (in a block) are special-cased in partition_leading_lines but ones that are of the LEADING type need to be excepted from that and kept with the statement.
These should be configurable, but with defaults for common tools.

Going to close this, as we just universally move comments preceding imports now. I think that's easier to explain than trying to magically decide what should or shouldn't move with the import. Reopen if you disagree?


Chaos Content Validation Issue for github.io website

Section link1:

Reason:
Link validation Issue: Wrong link: https://learn.microsoft.com/en-us/azure/azure-web-pubsub/howto-authorize-from-application - Service not match

Section link1:

Reason:
Link validation Issue: Broken links.

@rohit-ganguly, @lmazuel for notification.

Close this issue as we'll put it into a summarzied one.


How to calculate uptime using

Anyone knows how to convert the value received from "fortigate_last_reboot_seconds"
I tried
fortigate_last_reboot_seconds{job="fortigate_exporter"}/100
but I got 193 d 17:45:05 as result when on my Forti dashboard I have 23:07.mm.ss
Using v1.17.0 exporter and Forti 7.2.3 version.
Thanks in advance

I noted something weird, the normal thing with uptime is that as time pass the curve keep growing, like this

But instead with the fortigate exporter I got something like this

Any idea about what could be wrong or maybe this is a bug?

fortigate_last_reboot_seconds is the timestamp when the last reboot occurred. It is static unless a reboot happens. You can do something like fortigate_time_seconds - fortigate_last_reboot_seconds to get the current uptime (untested, but should work)

Thank you bluecmd! That clarify a lot, it works great now!


CoreFTP in ASP.NET Core MVC not working

Hi!
I'm trying to use your package CoreFTP but I get a error when it invoque the method LoginAsync():
"Value cannot be null. Parameter name: remoteEP".
The Code:
using (var ftpClient = new FtpClient(new FtpClientConfiguration
{
Host = "ftp://ftp.udc.es",
IgnoreCertificateErrors = true
}))
{
try
{
await ftpClient.LoginAsync();
}
catch (Exception ex)
{
return ex.Message; // ERROR: Value cannot be null. Parameter name: remoteEP
}
....
Any idea? Thanks.

omit the protocol in the host string

@josebarodriguez did that work?

Yes!. Thankyou!
But now I have another problem with folders... give me some days. I'm in spain holidays ;)

OK.
I am not able to navigate to the folder to get the list of files to use ListFilesAsync.
Is there any example or manual about it? Thank you.

I already discovered how to switch to a folder: ChangeWorkingDirectoryAsync
All is OK.
      if (ftpClient.IsAuthenticated)
            {
                await ftpClient.ChangeWorkingDirectoryAsync("folder/subfolder/...");
                var archivos = ftpClient.ListFilesAsync();
                foreach (var archivo in archivos.Result)
                {
                    using (var ftpReadStream = await ftpClient.OpenFileReadStreamAsync(archivo.Name))
                    {
                     ...

Thank you very much!

It would be nice if this was made more clear, or if an extra signature was added to have a filePath as a parameter in ListFilesAsync().


ci: build tests based on manifest change using tags

ci: test_plan: add tags based on manifest change
manifest: add mcuboot to bootloader group

Fixes #61716

This looks like it is doing the right thing. Presumably, we would want to have just the script changes without actually changing a module, but then again, that wouldn't get tested until other changes go in.

This looks like it is doing the right thing. Presumably, we would want to have just the script changes without actually changing a module, but then again, that wouldn't get tested until other changes go in.

unrelated test commits removed

Change looks okay but can't see this part: manifest: add mcuboot to bootloader group

I think this was the test commit that @nashif had initially to check it worked as expected, and then removed as per https://github.com/zephyrproject-rtos/zephyr/pull/61718#issuecomment-1687186488.


Update images in quickstarts

Ensure that quickstarts which show screenshots of "Show Taskpane" ribbon button display the correct icon for the button (blue blocks or black logo).

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/excel-quickstart-addin-2b.png
:white_check_mark:Succeeded

docs/images/powerpoint_quickstart_addin_1b.png
:white_check_mark:Succeeded

docs/images/powerpoint_quickstart_addin_2b.png
:white_check_mark:Succeeded

docs/images/powerpoint_quickstart_addin_3b.png
:white_check_mark:Succeeded

docs/includes/file-get-started-excel-jquery.md
:white_check_mark:Succeeded

docs/includes/file-get-started-excel-react.md
:white_check_mark:Succeeded

docs/includes/file-get-started-powerpoint.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Config color code not working.

For some reason the config's color code is not working.
https://i.imgur.com/4ZVOvsk.png
Anti-VPN: 5.11.37
WaterFall: 326

Fixed.

How did you manage to resolve this issue?

@egg82 I'll be flat out honest, I have no idea.
One moment it wasn't working, the next moment it was fine.
Perhaps something to do with those downloaded libraries?


Derivatives liquidity pool

options-pool page refactored & pulled from develop_perpetual.

Rounding issue mentioned in another pool request.
Otherwise, add / remove liquidity function verified.


[FEATURE] Provide aliases for commonly shortened commands

Affected project(s)

[ ] documentation
[ ] examples
[ ] wasmCloud host
[X] wasmCloud CLI (wash)
[ ] wasmCloud dashboard UI (washboard)
[ ] capability providers
[ ] provider bindgen
[ ] control interface client
[ ] other / not sure

Is your feature request related to a problem? Please describe.
wash link delete is a perfectly reasonable alternative to wash link del, and it stinks to error out at that point.
Describe the solution you'd like
For the common commands that have shortened names, we should provide these common aliases
Describe alternatives you've considered
No response
Additional context
No response

I believe I have a solution for this, can I have this issue assigned please ? Thank you!

@Aditya1404Sal go for it! Feel free to ask questions here or just open up the PR when you're ready 😄

https://github.com/wasmCloud/wasmCloud/blob/790cb148e088301656e8482a5a9b44fcf774f1c6/crates/wash-lib/src/cli/link.rs#L77-L90
#[clap(name = "del", alias = "delete")]
This should solve it, However I haven't written a test for it.
Sorry for the inconvenience but i have a question,
If I've made changes to the codebase locally and did the make build , is there any way to test out the cli changes in my terminal itself without writing tests? I looked through multiple READme's but couldn't find any clue to running a local copy of wash (if that's even possible) for development purposes.

@Aditya1404Sal yep! This is built right into the Rust tool cargo. Inside of the crates/wasi-cli directory you can run cargo run to build and run wash (the binary will be under target/debug/wash). Just put arguments after a -- in the CLI.
For example, to test the above you could try:
cargo run -- link del source ns package
cargo run -- link delete source ns package

It works! Thanks a lot!
Should I add a section to the README.me explaining cargo run for new contributors, so that they won't face the same problem as I did ?

@Aditya1404Sal That would be a great addition to the README!

@Aditya1404Sal That would be a great addition to the README!

I'll get started on it ASAP !

I think we've gotten great traction here and we can mark this completed 😄


feat(cli): support multi LICENSE

Hi!
This PR is related to #4.
With this change, the CLI gets supporting multi LICENSE.
$ ./target/debug/license-generator --help
license-generator 0.6.0
azu<EMAIL_ADDRESS>A Command line tool that generate `LICENSE` file.

USAGE:
    license-generator [OPTIONS] <INPUT>... --author <author>

FLAGS:
    -h, --help       Prints help information
    -V, --version    Prints version information

OPTIONS:
        --author <author>
        --output <output>
        --project <project>
        --year <year>

ARGS:
    <INPUT>...

$ ./target/debug/license-generator MIT Apache --author "thekuwayama"
$ ls LICENSE_MIT LICENSE_APACHE
LICENSE_APACHE LICENSE_MIT

Looks nice!
Thanks!

Release https://github.com/azu/license-generator/releases/tag/v0.7.0
I've added a bit change that uses - instead of _ as a separator in https://github.com/azu/license-generator/releases/tag/v0.7.1. (I missed it)
https://github.com/search?l=Text&q=filename%3A"LICENSE-MIT"&type=Code


Align custom kernel parameters with extensibility documentation

Problem
Currently the extensibility documentation lists that customizations to kernel parameters can be done by
custom_parameters:
  common:
    - { ... }

This is not the case as the code expects them grouped under the distribtuion_id.
Solution
This PR ensures that both common and distribution_id can be utilized to set kernel parameters.
If both common and distribution_id sets the same property, the distribution_id will take precedence.
See the following example:

Which results in parameters being set like the following on the os level

Thanks for the contribution. @SteffenBoThomsen


Made ICFolderDialogs ICEndpoint usage more obvious

Fixes #222

Pull Request Test Coverage Report for Build 906

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

Totals

Change from base Build 900:
0.0%

Covered Lines:
930

Relevant Lines:
1290

💛  - Coveralls

Pull Request Test Coverage Report for Build 906

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

Totals

Change from base Build 900:
0.0%

Covered Lines:
930

Relevant Lines:
1290

💛  - Coveralls


chore: upgrade all dependies to newest ones while ensuring everything works fine

Here are my changes:

Upgraded all packages to the newest version, altered the dev & build processes;
Migrated the Chrome extension version from Manifesto v2 to v3;
Installed new packages or changed the logic including using redux-toolkit syntax to make functionalities work normally.
Remove hot-reloader/react-dom and clean-webpack-plugin` due to failure of the build process, considering it will also affect the build process.

If you think what I've done is fine, I will try to deal with the issues you've listed before. Thank you!

@flynncao
Just found your blog post about chrome extension: https://www.flynncao.me/liu-lan-qi-cha-jian-kai-fa-jian-yi-zhi-nan-0
Are you interested in developing your own mojidict extension in plasmo? I did actually switch to Yomichan instead. So I might won't put more efforts on maintaining this project nor adding new features. You can fork or take whatever you want from the code base. I just realized I don't have passion for the maintenance of this project 🤣 .

@flynncao
Just found your blog post about chrome extension: https://www.flynncao.me/liu-lan-qi-cha-jian-kai-fa-jian-yi-zhi-nan-0

Are you interested in developing your own mojidict extension in plasmo? I did actually switch to Yomichan instead. So I might won't put more efforts on maintaining this project nor adding new features. You can fork or take whatever you want from the code base. I just realized I don't have passion for the maintenance of this project 🤣 .

Thank you for your review and hard work on this project, Yukaii! Yomichan is excellent to use in terms of abundant features.
The main reason for my switching to the official MojiDict extension is it allows me to collect unfamiliar words more or less and sync to other devices, which I am used to doing in the early phase of learning a new language, except the fact that it's pretty heavy and laggy sometimes compared to yours.
Before I have new ideas to differentiate these two referred to primary functionalities, I may not start a new project about MojiDict (Plasmo is a good choice at that time), or there are some firm reasons to use both.


Look for and pass proper command line arguments to vswhere

Fixes #2 and fixes #10

@timheuer take PR #9 then #11 before this. I can rebase anything if there's an issue or, if you prefer, just squash it all and submit a single PR. Originally I was just going to fix one issue and keep the PR focused, then I found another issue to fix, and another... 😊
Also, each of these uses semver since these are all bug fixes and shouldn't affect any public usage. I'm not sure how well that jives with GitHub actions. Seems it's concept of v1, v2, etc., is monotonic and independent of packages' semvers; but, I'm happy to make any adjustments as desired.

Ping

Any change to take a look at this? I even added tests and they all pass.

Would you like me to add even more tests to raise confidence in this change? There are significant bugs in how vswhere is used now that this fixes.

Please, merge this, otherwise this Action is absolutely useless. I'm using this fork instead of the official one and it works great.
Thanks for the contribution!

Thanks for the merge and great work. I hope my previous comment did not come off as disrespectful. :)

Maybe a bit :-) -- but it was enough of a nudge to compliment Heath's nudges as well.

I am sorry about that, I do appreciate all the work you put in though, and it's open source after all, so yeah... :) Thanks again and have a nice day!

No worries!