WIP: validity client for multiblock proofs

This PR creates a validity-client crate that will enable multiblock proofs, for full ZK validity proofs.

Creates a new validity-client/driver.rs to replace the default kona-client driver implementation.

It adds the l2_claim_block to the struct, since the default impl assumes it's unneeded since it'll always be one block after the safe head.
Rather than calling step on the pipeline once, it loops calling step and saving the attributes for each L2 block until we've reached the l2_claim_block.
When attributes are returned, we move the cursor forward to begin searching for inputs to a new L2 block.
When an L1 block is exhausted, the L1 origin is incremented by one, so we search continuously until all data has been found.
When we've received the data for the l2_claim_block, we exit and return the full vector of results.

Updates main.rs to incorporate these changes.

Uses the new derivation driver type, and expects a vector of attributes back instead of just one.
Executes each of the block attributes in a loop to get all the way through to the final l2_claim_block's state.
Performs validation within these loops to ensure that payloads are executed sequentially (with some extra safety checks).

Closing in favor of https://github.com/moongate-forks/kona-sp1/pull/27


brownout: new package at 0.4

Description of package
A scriptable, minimal f.lux/redshift alternative which only depends on libX11
Installed manifest of package
/var/db/kiss/installed/brownout/version
/var/db/kiss/installed/brownout/sources
/var/db/kiss/installed/brownout/manifest
/var/db/kiss/installed/brownout/depends
/var/db/kiss/installed/brownout/dependencies
/var/db/kiss/installed/brownout/build
/var/db/kiss/installed/brownout/
/var/db/kiss/installed/
/var/db/kiss/
/var/db/
/var/
/usr/share/man/man1/brownout.1
/usr/share/man/man1/
/usr/share/man/
/usr/share/
/usr/bin/is-day
/usr/bin/brownout
/usr/bin/
/usr/

New package

[X] Latest upstream version.
[X] I agree to maintain this package.
[X] I agree to notify the @kiss-community maintainers if I can no longer maintain this package.

The dependencies file should be renamed to depends, the package manager only reads depends.

Whoops! Thank you!

Also you should use the tarball source instead of git for this package since the tarball is up to date already (Last commit was made on the same day as the last release)

Looks good with the tar source :)

This PR also includes your berry commit. Can you rebase onto remote/main and force push your changes?

Did that do it? Sorry, I seem to be forever getting to grips with GitHub!

That did do it!
git is a complicated beast. Only reason I knew how to solve it is I've had to do it before...


Implement the SETSTATE API command

The SETSTATE API command sets the state of an event.  It takes two arguments: A case-id and a state value.
Example of a Zino 1 interactive session:
GETATTRS 134127
303 simple attributes follow, terminated with '.'
state: waiting
router: example-gw5
type: bgp
opened:<PHONE_NUMBER>
remote-addr: <IP_ADDRESS>
id: 134127
peer-uptime: 477
updated:<PHONE_NUMBER>
polladdr: <IP_ADDRESS>
priority: 200
bgpOS: down
bgpAS: running
remote-AS: 65333
lastevent: peer is down
.

SETSTATE 134127 ignored
200 ok

GETATTRS 134127
303 simple attributes follow, terminated with '.'
state: ignored
router: example-gw5
type: bgp
opened:<PHONE_NUMBER>
remote-addr: <IP_ADDRESS>
id: 134127
peer-uptime: 477
updated:<PHONE_NUMBER>
polladdr: <IP_ADDRESS>
priority: 200
bgpOS: down
bgpAS: running
remote-AS: 65333
lastevent: peer is down
.

GETLOG 134127
301 history follows, terminated with '.'
1673538471 state change embryonic -> open (monitor)
1673598401 somebody
 We did something - RT#123456

1673598403 state change open -> waiting (somebody)
1697799421 state change waiting -> ignored (mvold)
.

Changing an event state should trigger at least three actions:

The state attribute of the event must be changed accordingly.
A history entry must be added to the event to document which change took place, and who did it.
A change notification must be triggered.  Currently, we have not yet implemented notification channels in Zino 2.0, so this will have to come later.

Regarding valid/invalid state values: Zino 1 allows arbitrary state values, so I could easily issue a SETSTATE 42 foobar and Zino would happily change the state of event 42 to foobar.  Zino 2 doesn't allow arbitrary values in this field, so if the user tries to set a state not in the valid enum of EventState, Zino 2.0 should respond with a 500 error explaining what went wrong.

What happens when SETSTATE is used to close an event?
The only way to close an event in Zino is for an operator to issue the SETSTATE command.  Closing an event in Zino 1 triggers the following additional actions (from the setEventState function):

The closed event is persisted to disk in a separate file by the saveEvent function, in preparation for removal from the in-memory state data.
The event is marked for expiration or somehow flagged so that it can no longer be updated.  A new event must be created if the state changes again.

Zino 2 has not yet implemented event expiration (or scavenging, as it is termed in Zino 1), since we haven't yet had the mechanism to close events. Scavenging runs about every 30 minutes.  This is a job that removes closed events from the in-memory state models, but only after a configured event expiry period has passed.

What happens if SETSTATE tries to change the state of a closed event
It should not be allowed to.  Closed events cannot be reopened.

What happens to archived events?
As far as we know: Nothing.  They are just archived and never touched by Zino again. Presumably, the archived events are only perused by a Zino operator as a form of detailed logs of the past.

Event "commits"
It turns out we may need something event "commit" mechanism described in #52 to fully implement this.  That is, we do not necessarily need a "commit" operation to ensure internal consistency, since no threads are used in Zino, but we at least need some way to signal various procedures to take place when an event is updated.
For example, the SETSTATE command doesn't just change the state of an event.  Once the server requests a state change for an event, Zino 1 executes multiple actions:

The state change is logged to the event, and the log message must include the username of the user who changed the state.
The event changes are "committed".
A state dump is scheduled to take place within 10 seconds (regardless of the current schedule for state dumps) to ensure state remains persistent.
A notification is scheduled to be sent to all listening NTIE socket clients.

It turns out we may need something like the event "commit" mechanism described in #52 to fully implement this. That is, we do not necessarily need a "commit" operation to ensure internal consistency, since no threads are used in Zino, but we at least need some way to signal various procedures to take place when an event is updated.

#136 has been added to address this need.


Fix: Hidden tooltip from table and out of screen tooltip (Home) page

Description of PR

fixed hidden tooltip from table
fixed getting out of screen tooltip

Type of PR

[x] Bugfix

Relevant Issues
Fixes #1442, Fixes #1380
Checklist

[x] Compiles and passes lint tests
[x] Properly formatted
[x] Tested on desktop
[x] Tested on phone

Screenshots

Thanks for the PR! Patched by #1465


GUI features request & misc

Would be great if the GUI would include some controls to turn features on/off, some of which are only available through the command line.

timestamps to include/exclude the milliseconds (or do this by default when they are all just 0's ?)
allow to change the visible window span (--buffer option)
allow to change the COM/serial port in the GUI - and show CONNECTED / DISCONNECTED status - for instance if serial port connection is lost for whatever reason

Would be nice to remove any dependencies to python and just have a standalone executable.
Any chance the program could be compiled into an executable? I tried it with pyinstaller but I ran into all sorts of issues.
BUG: I noticed if the USB is disconnected the SPS starts decreasing instead of going to 0.

Check out version 1.0.4:

timestamps now change to second or millisecond depending on the range in view. This now also works when you zoom in.
SPS rate now calculated differently (red if <100, yellow if <500, white otherwise) and automatically sets to 0 when there is no data.
UI also shows connectivity state:

Pause/resume buttons now change state correctly.

The rest of the suggestions/asks will have to wait for the next rev of the UI, as matplotlib is not exactly friendly to drawing UI features like this.


vds-radio-check rendering the dot off-center by default

Sorry for the nit-pick here folks, I am a little "nuts" as they would say, but I love what you all have done with the Player and I hope I am just helping out to make it incrementally more awesome.
Current Behavior:
The class vds-radio-check on the Player currently has the width and height properties set to:
var(--media-menu-radio-check-size, 9px);
I realize that I can set the --media-menu-radio-check-size value to correct any sizing issues (which I have done), but I believe this means that by default, the "dot" is off-center due to the math, e.g. 9px is a pixel too small.

Expected Behavior:
By default, I would expect the CSS to "just work". I believe to get it to just work the fallback number for the width and height properties needs to be 10px, not 9px.
Steps To Reproduce:
Just take a look at the "Speed" settings in the Player.

Environment:

Framework: React
Meta Framework: Next.js
Node: 18.17.0
Device: Chrome
Browser: Version 119.0.6045.105

Thanks for the report! Hm unless I'm missing something I can't repro this. The sizing by default seems to be correct and centered?


Update New-CsTeamsMeetingPolicy.md

Adding new meetingPolicy setting AllowNetworkConfigurationSettingsLookup to help determines whether network configuration setting lookup can be made for not enterprise voice enabled users. It will be used for enabling network roaming policy

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

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

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

@JohanFreelancer9

@vini-gupta kindly implement the suggested changes. Thanks

@dariomws @tseward @get-itips

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

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

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

Docs Build status updates of commit 40d051f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

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

@tseward

@tseward please review

@tiburd Please merge this PR. Thanks

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

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

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


Authentication failed : Invalid Application

I always get the above error no matter if I use my production or sandbox keys. I also tried to add devId and certId.
Code:
inspect = require('eyespect').inspector({maxLength: null})
chalk = require('chalk')

ebay = require('ebay-api')

ebayConfig = require('../config/ebay.config.js')
appId = ebayConfig.getAppKey('AppID')
console.log appId

exports.getItems = (appUser, searchTerm, callback)->
  options = {}
  options.appId = ebayConfig.getAppKey('appId')
  options.devId = ebayConfig.getAppKey('devId')
  options.certId = ebayConfig.getAppKey('certId')

  options.serviceName = "Finding"
  options.opType = "findItemsAdvanced"

  params = {
    keywords: ["Canon", "Powershot"],

    #add additional fields
    outputSelector: ['AspectHistogram'],

    paginationInput: {
      entriesPerPage: 10
    },

    itemFilter: [
      {name: 'FreeShippingOnly', value: true},
      {name: 'MaxPrice', value: '150'}
    ],

    domainFilter: [
      {name: 'domainName', value: 'Digital_Cameras'}
    ]
  }
  options.params = params

  inspect options #the appId, devId and certId are displayed correctly
  ebay.xmlRequest(options, callback)

Error Msg:
{"err":{"name":"EbayClientError","message":"Bad response status code 500 <?xml version='1.0' encoding='UTF-8'?><errorMessage xmlns=\"http://www.ebay.com/marketplace/search/v1/services\"><error><errorId>11002</errorId><domain>Security</domain><severity>Error</severity><category>System</category><message>Authentication failed : Invalid Application: MYAPPID</message><subdomain>Authentication</subdomain><parameter name=\"Param1\">Invalid Application: MYAPPID</parameter></error></errorMessage>"}}

Is there a string "MYAPPID" in your Ebay.config.js file?
On Tuesday, January 5, 2016, 360disrupt<EMAIL_ADDRESS>wrote:

I always get the above error no matter if I use my production or sandbox
keys. I also tried to add devId and certId.
Code:
inspect = require('eyespect').inspector({maxLength: null})
chalk = require('chalk')
ebay = require('ebay-api')
ebayConfig = require('../config/ebay.config.js')
appId = ebayConfig.getAppKey('AppID')
console.log appId
exports.getItems = (appUser, searchTerm, callback)->
options = {}
options.appId = ebayConfig.getAppKey('appId')
options.devId = ebayConfig.getAppKey('devId')
options.certId = ebayConfig.getAppKey('certId')
options.serviceName = "Finding"
options.opType = "findItemsAdvanced"
params = {
keywords: ["Canon", "Powershot"],
#add additional fields
outputSelector: ['AspectHistogram'],

paginationInput: {
  entriesPerPage: 10
},

itemFilter: [
  {name: 'FreeShippingOnly', value: true},
  {name: 'MaxPrice', value: '150'}
],

domainFilter: [
  {name: 'domainName', value: 'Digital_Cameras'}
]

}
options.params = params
inspect options #the appId, devId and certId are displayed correctly
ebay.xmlRequest(options, callback)
Error Msg:
{"err":{"name":"EbayClientError","message":"Bad response status code 500 <errorMessage xmlns="http://www.ebay.com/marketplace/search/v1/services\">11002SecurityErrorSystemAuthentication failed : Invalid Application: MYAPPIDAuthentication<parameter name="Param1">Invalid Application: MYAPPID"}}
—
Reply to this email directly or view it on GitHub
https://github.com/benbuckman/nodejs-ebay-api/issues/28.

Nope, but it magically works now. maybe s.th. with ebay maybe I changed s.th. can't reconstruct anymore.

Sorry to comment on closed issue, but I ran into the same exact thing and this is the 1st result. For me, it was due to the fact that appId & appName is used interchangeably in their docs.
I used to have this, which worked for all api calls except for finding
{
            serviceName: serviceName,
            opType: opType,
            devId: credentials.devId,
            certId: credentials.certId,
            appName: credentials.appId,
            sandbox: config.isSandBox,
            authToken: currentSeller.token,
            params: params,
        };

changed to this, with finding working as well now
{
            serviceName: serviceName,
            opType: opType,
            devId: credentials.devId,
            certId: credentials.certId,
            appId: credentials.appId, //<--
            sandbox: config.isSandBox,
            authToken: currentSeller.token,
            params: params,
        };

For me I had to use production appId. Sandbox doesn't work.

Like @chovy, the Finding servicename only works with production apps for me, not with sandbox. There is this in the code of xml-request.js of this module:
if (options.serviceName === 'Finding') {
  root.push({'_attr': {'xmlns': 'http://www.ebay.com/marketplace/search/v1/services'}});
}
else {
  root.push({'_attr': {'xmlns': 'urn:ebay:apis:eBLBaseComponents'}});
}

XML APIs are a foreign country to me, but if eBay is using xmlns to determine whether a call belongs in production or sandbox sites, then this code is going to tell eBay to perform the request against the production site (based on the URI passed in), while all the credentials are for the sandbox site.

Yup.
Looks like a hack to get Finding working but only for production.
Feel free to fix and submit a pull request. :)
On Thu, Aug 31, 2017 at 3:59 PM rhclayto<EMAIL_ADDRESS>wrote:

Like @chovy https://github.com/chovy, the Finding servicename only
works with production apps for me, not with sandbox. There is this in the
code of xml-request.js of this module:
if (options.serviceName === 'Finding') {
root.push({'_attr': {'xmlns': 'http://www.ebay.com/marketplace/search/v1/services'}});
}else {
root.push({'_attr': {'xmlns': 'urn:ebay:apis:eBLBaseComponents'}});
}
XML APIs are a foreign country to me, but if eBay is using xmlns to
determine whether a call belongs in production or sandbox sites, then this
code is going to tell eBay to perform the request against the production
site (based on the URI passed in), while all the credentials are for the
sandbox site.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/benbuckman/nodejs-ebay-api/issues/28#issuecomment-326442636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWSY9Qx77UeJ-GGaoRquCg_DCOLdWhuks5sdzragaJpZM4G-q1t
.


Request for Comments: Clarify location of robot-specific manually added files?

Historically, the robots-configuration has been used to host two kind of files:

The "official" (with a lot of quotes : ) ) configuration files for a given robot, that are typically maintained by the iCub Tech, and that routinely need to be massively updated for several reason (bugs found, change in the software that requires update in the configuration files). This files are not exactly the same for two different (even if identical) robots, due to calibration settings and similar robot specific parameters, but at least their structure is (or should be) consistent  across robot of the same version.
Robot-specific configuration and material: this includes robot-specific material that is maintained by specific Research Lines that used the robot (in IIT) or robot groups. While one school of thought is that this material should be in repositories that are maintained by the groups that are responsible for them, in practice for configuration files that are part of the "robot setup" it is quite convenient to be able to managed them with the rest of the robot configuration files.

This is de-facto situation. However, I think that a possible improvement (especially to simplify the possibility of doing automatic changes to the "official" configuration files) is to dedicate a given directory in the robot directory for robot-specific files, something called extra or similar (bikeshedding on the name is welcome), in which all the robot-specific files can be placed. In this way, it would be easy to separate between "official" iCub configuration files and robot-specific ones.

Comments on this proposal are welcome: @Nicogene @pattacini @marcoaccame @S-Dafarra @violadelbono @davidetome @triccyx (feel free to tag more people that could be interesting).

Good suggestion @traversaro 👍🏻
Also, extra sounds good.

Also, extra sounds good.

I must confessed that I borrowed the concept from the FMI3 standard, see Section <IP_ADDRESS>. Directory Extra.

Sounds good. Among the files that could go in that directory there would be also the yarpmanager application files for example (since those are usually modified to consider the specific machines in the network for example). Hence this repo would store the configuration files in a broader sense, not just related to the robot itself, but to the entire setup.

I like the idea, the extra folder could contain all the "extern" configuration files stored with the contexts hierarchy

@Nicogene if you mean the .ini files, that's not the case!
.ini files shall be in the robot root directory to make all the resource-finder pipeline work as intended.

So, go ahead @S-Dafarra as agreed!


Update website.js, use specific pattern to handle the function parameters

use specific pattern to handle the function parameters

I cannot grant the pull request because the pattern is for one character.

OK then, I'll grant the request


understanding readable stream and writeable stream

hi, I can not understand the code
req.pipe(request.get('http://some/url')).pipe(res);
```

`req` is readable stream, `res` is writeable stream
does the above code means `request.get` is writeable and readable?

thanks~

Yep, it's a duplex stream.

@simov thanks!


Replace "Enhanced by Google" search function

The current Search function on apache.org is a 3rd-party tie in that provides lackluster results on searches. It needs to be replaced with a more useful function/tool that is Apache-hosted.
This ties into #52 as well, since 3rd-party fonts are being used as well.

Speaking just as someone who makes infrequent updates to the ASF web content, I'd prefer to deal with a tool like Pagefind than with Google.
<= $.02
Craig

Yeah, something like Pagefind would be much more helpful. I have zero skin in the Google game. Discussing with my team tomorrow.


"Null check operator used on a null value" in _CupertinoScrollbarState::handleThumbPressStart

I started observing massive "Null check operator used on a null value" errors in Crashlytics since I've deployed the app built with flutter 2.0.2 (after upgrading from 1.22.6)
Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Null check operator used on a null value. Error thrown Instance of 'ErrorDescription'.
       at _CupertinoScrollbarState.handleThumbPressStart(_CupertinoScrollbarState.java:162)
       at RawScrollbarState.<fn>(RawScrollbarState.java:1086)
       at LongPressGestureRecognizer.<fn>(LongPressGestureRecognizer.java:420)
       at GestureRecognizer.invokeCallback(GestureRecognizer.java:182)
       at LongPressGestureRecognizer._checkLongPressStart(LongPressGestureRecognizer.java:420)
       at LongPressGestureRecognizer.didExceedDeadline(LongPressGestureRecognizer.java:372)
       at PrimaryPointerGestureRecognizer.didExceedDeadlineWithEvent(PrimaryPointerGestureRecognizer.java:501)
       at PrimaryPointerGestureRecognizer.<fn>(PrimaryPointerGestureRecognizer.java:454)
       at _CustomZone.<fn>(_CustomZone.java)
       at TickerFuture.thunk(TickerFuture.java:407)

Unfortunately I can't reproduce it, but it's reported from many users and from many devices for Android.
P.S. I apologize for .java in stacktraces. I've already added a comment about it in  https://github.com/FirebaseExtended/flutterfire/issues/80

Hi @SimeonZV
Can you please provide your flutter doctor -v, your flutter run --release --verbose and a minimal complete reproducible code sample? You can start by looking where you are using a widget similar to CupertinoScrollbar.
There is nothing we can do without a reproducible code sample as this may be caused either by the framework or your implementation!
Thank you

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.2, on Linux, locale en_US.UTF-8)
    • Flutter version 2.0.2 at /home/simeon/apps/flutter
    • Framework revision 8962f6dc68 (7 days ago), 2021-03-11 13:22:20 -0800
    • Engine revision 5d8bf811b3
    • Dart version 2.12.1

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /home/simeon/apps/android-sdk
    • Platform android-30, build-tools 29.0.2
    • ANDROID_SDK_ROOT = /home/simeon/apps/android-sdk
    • Java binary at: /home/simeon/apps/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Android Studio (version 3.5)
    • Android Studio at /home/simeon/apps/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)

[✓] IntelliJ IDEA Community Edition (version 2020.3)
    • IntelliJ at /home/simeon/apps/idea-IC-202.7660.26
    • Flutter plugin version 53.1.5
    • Dart plugin version 203.7759

[✓] VS Code (version 1.52.1)
    • VS Code at /usr/share/code
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • SM G900F (mobile)                  • 15b0d3a4      • android-arm    •
      Android 6.0.1 (API 23)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    •
      Android Q (API 28) (emulator)
    • Chrome (web)                       • chrome        • web-javascript •
      Google Chrome 87.0.4280.141

• No issues found!

I fully understand that it's difficult to fix an issue without being able to reproduce it. But I really tried hard and didn't manage it. I do use CupertinoScrollbar widget, but no issues when I test on emulators or on my local devices.
The only place where I see exceptions is Crashlytics. And I can say that it started happening only in the latest release of my app that I deployed just 2 days ago built with flutter 2.0.2. I had no changes in my code where I use CupertinoScrollbar.
Anyway thanks for looking at it.

And I've just got the first error from an iOS device reported in Crashlytics
Non-fatal Exception: FlutterError
0  ???                            0x0 handleThumbPressStart + 162 (scrollbar.dart:162)
1  ???                            0x0 <fn> + 1086 (scrollbar.dart:1086)
2  ???                            0x0 <fn> + 420 (long_press.dart:420)
3  ???                            0x0 invokeCallback + 182 (recognizer.dart:182)
4  ???                            0x0 _checkLongPressStart + 420 (long_press.dart:420)
5  ???                            0x0 didExceedDeadline + 372 (long_press.dart:372)
6  ???                            0x0 didExceedDeadlineWithEvent + 501 (recognizer.dart:501)
7  ???                            0x0 <fn> + 454 (recognizer.dart:454)

I'm experimenting the same issue

With the hint from https://github.com/flutter/flutter/issues/78487#issuecomment-805323013, I've finally managed to reproduce this issue. By now I strongly believe that these two issues are related although reported by Crashlytics independently at different times.

/cc @Piinks

With the hint from #78487 (comment), I've finally managed to reproduce this issue. By now I strongly believe that these two issues are related although reported by Crashlytics independently at different times.

Can you share the reproduction?

Also mentioned in https://github.com/flutter/flutter/issues/78487, https://github.com/flutter/flutter/pull/77107 may provide better insight into what is occurring here.

Sure, below is the minimal code. As advised here https://github.com/flutter/flutter/issues/78487#issuecomment-805323013, you would need to tap directly at the scroll bar and drag.
I've also just noticed that without injecting "controller: ScrollController()", this issue is not reproducible.
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Cupertino Scroll Bar Issue',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Cupertino Scroll Bar Issue'),
    );
  }
}

class MyHomePage extends StatelessWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(title),
      ),
      body: CupertinoScrollbar(
        child: ListView.builder(
            controller: ScrollController(),
            padding: const EdgeInsets.all(8),
            itemCount: 100,
            itemBuilder: (BuildContext context, int index) {
              return Container(
                height: 50,
                child: Center(child: Text('$index')),
              );
            }),
      ),
    );
  }
}

Ah! Thank you! I can see what is happening now.
#77107 does add more guidance about this and better error messaging. If you assign a scroll controller to your list view, you have to provide it to the scrollbar.
This should resolve your issue:
final ScrollController controller = ScrollController();

CupertinoScrollbar(
  controller: controller, // here
  child: ListView.builder(
    controller: controller, // and here
    padding: const EdgeInsets.all(8),
    itemCount: 100,
    itemBuilder: (BuildContext context, int index) {
      return Container(
        height: 50,
        child: Center(child: Text('$index')),
      );
    }),
  ),

Being able to interact with the scrollbar relies on being able to access the ScrollController. When you remove the ScrollController from your reproduction, there is no issue because by default, your ListView uses the inherited PrimaryScrollController. The Scrollbar knows about the PrimaryScrollController, so when the Scrollbar is not provided a ScrollController, it looks up the PrimaryScrollController instead - so everything works as expected.
When the ListView is provided a ScrollController, but the Scrollbar does not receive it (like in your reproduction), it cannot access your ListView, and since it has not received a controller, it looks up the PrimaryScrollController and tries to use that. In your reproduction, the PrimaryScrollController is not attached to anything since the ListView has its own controller, so it throws an exception.

Thanks for the detailed explanation and improving the docs! I'll fix my code accordingly.


Vector3.Magnitude is incorrect

Sorry if the Vector3 object is out of this repo's scope; didn't feel like writing an email to submit the bug report.
You can easily replicate this by comparing a by a lua magnitude calculation vs Vector3.Magnitude
function getMag(vec)
    return math.sqrt(vec.X ^ 2 + vec.Y ^ 2 + vec.Z ^ 2)
end

local testVec = Vector3.new(15,70,25)

print(testVec.Magnitude)
print(getMag(testVec))

>> 75.828758239746
>> 75.828754440516

I triple checked my getMag function with some calculators to ensure math.sqrt was accurate; and it is.

It is out of scope, you'd post this one on the dev forums.
Either way, nobody really needs this degree of accuracy on Roblox, but if you do you can just use your own custom function. It is a bug, but not really one that matters too much.

Not a dev forum member. Lost quite a bit of time hunting down seemingly causeless math bugs during unit testing; turns out the bugs weren't mine. Thankfully spotted the issue but it required a print() on pretty much every single variable until I noticed it was the Vector3.magnitude call.
Noticed that Color3.toHSV() does this as well:
My toHSV function; final decimal point correctly rounds:
0.16666666666667 0.58823525905609 1
Color3.toHSV, very odd that it rounds earlier and fills in digits after the round with seemingly random numbers:
0.16666667163372 0.58823525905609 1
Roblox's object's methods should cut off the return value at 8 decimal places if a solution to return the correct number is not possible.

@ZachCurtis all of the object methods, such as Instance and Vector3 are part of the C/C++ engine, not the CoreScripts. Report it via email here, or report it on the devforum (or get someone to do it for you)

@stillunt1tled Dev forum members can not post on behalf of other users, including non-members.

@Kampfkarren I don't get it why Roblox makes bug reporting for the engine such a pain.

This is an artifact of IEEE floating point numbers and slightly differing implementations. It doesn't really matter and isn't a bug.
You shouldn't try to compare floating point values directly, that's almost never what you want.


fix: quantity controls in horizontal product on category page

Description
Fix quantity selector and add to cart on product card horizontal component to send proper values.
Important: to make it work we need to update storefront-ui version cause there is fix for quantity selector component input updating. Without that it won't work properly.
Related Issue
Closes #128
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Awesome work @AdamPawlinski!
Would you be able to update the version as well? Just go to packages/theme and update the existing version of Storefront UI to the one that contains this fix :)

I think the best would be to update to the newest version, because there is a plan to release 0.11.3 today.


Validation doesn't work with JSON:API mime type

If we have mimetype of JSON:API(application/vnd.api+json), validations don't work.

Hi @harshveers! openapi-backend currently only compiles requestBody validators for schemas listed under application/json content https://github.com/anttiviljami/openapi-backend/blob/master/src/validation.ts#L556
PRs are accepted if you feel like application/vnd.api+json should also be handled


Formatting the caption

Hi Guys,
It seems I'm unable to format the caption text not by html or ASS tags.
Am I missing something?

Hi @noamleib , what caption text are you referring to, as there is no caption field defined? do you mean the whole text in the ballon?

Hi @souly1
Yes, I'm referring to the main-caption directive (main-caption="This is some text"). Since the documentation mentions the text is formidable (

main-caption (optional) - Any walkthrough type. This is the text that will be displayed in the walk-through. Text can be formatted

).
In my case, it's not a balloon since I'm using the transparency  walkthrough-type.

Oops, your totally right, I forgot the attribute is called "main-caption", so you try through CSS to format text and it doesn't work?

Tried to embed in the caption some html tags (h, p etc). Didn't work :-(

Could you perhaps add a plunker demo or cut n' paste code of what's not working?
Thanks

Lets say in JS I'm Doing:
$rootScope.captionSchedule = "Lets Start! \n To start a scheduling process click this button to tell Pepper who you would like to meet with."
HTML:

The only Tag I was able to incorporate is the \n.
I was wondering if i could do somthing like this:
$rootScope.captionSchedule = "Lets Start!  To start a scheduling process click this button to tell Pepper who you would like to meet with."

You should be able use html as you see fit with the transclude option, and if you want to change style to whole text you can use the css element .walkthrough-text

Sorry, long hours... Don't know how I missed it. Thanks man!

No problem


fix: fixes -o for onnx-mllir-opt

-o never created a file when used. In the old cold the file is deleted when the scope is left. Now the file remains.

@ljfitz should this be upstreamed?

@ljfitz should this be upstreamed?

Yes. I see that the problem still exists upstream. I'll arrange for upstreaming once this PR is merged.


elon.se

@adguard-bot commented on Thu Oct 11 2018
Issue URL (Incorrect Blocking)
https://www.elon.se/
Comment
Username: @Xophile

Works perfectly fine when I disable AG.

Screenshots

Screenshot 1

System configuration

Information
value

Platform:
And 8.1.0

AdGuard version:
2.12.234η

Browser:
Firefox

AdGuard mode:
VPN

Filtering quality:
High-quality

HTTPS filtering:
disabled

DNS requests blocking:
disabled

Filters:
AdGuard Mobile Ads,AdGuard Annoyances,AdGuard Base,Fanboy's Swedish,AdGuard Spyware,AdGuard Social Media

@Xophile
Can you try to clear the cache in FF and try again?
Seems to me it can be reproduced but without clearing the cache.

Hi!
Clearing the cache does not help. The issue is still there.

Can't reproduce. Can you please say what is inside "Show details"?

I cannot reproduce it on the latest AG for Mac alpha build as well. I guess some of the other changes helped with this bug :)


basic-audio-system

Adds a basic sound system to the engine, with a usage example in the pong.
Closing #11

Bug found: Compile on linux does not work due to the static constexpr vector of supported extensions.


Enhance User Authentication and Data Security

Hi @Vin205 ,
I'm interested in contributing to this project by improving/adding user authentication and data security.
I propose implementing:
Sign up a user (Email/Password)
Sign in a user
Sign out a user
Form Validation and Handle Errors
Handle User Authentication State
Email Verification
Forgot/Reset Password
Google Sign in
Facebook Sign in
Add, Get & Update Logged In User Data
Upload, Get & Update Logged In User Profile Picture.

I'm ready to discuss this further and contribute a pull request.

@Nayanpatel48 Your contribution proposal sounds fantastic! Improving user authentication and data security is crucial for the project. Feel free to proceed, and we can discuss the details further. Once you're ready, submit your pull request, and we'll review it. Let me know if you need any assistance along the way!

Sure 😊

Here is my linked in keep in touch 😙
https://www.linkedin.com/in/patel-nayan-047317248?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=android_app


Color select v2

What this PR does
Adds ColorSelect2 component which is a new version that eventually will replace ColorSelect.
The biggest change is in the spectrum and hue implementation to use react-colorful package that has better functionality and tests.
Currently is ColorSelect there's a critical bug where users cannot select colors from the edges, so black/white cannot be reached - ColorSelect2 is fixing it.
This PR merge is blocked by merging #235, after that merge the only changes between this PR and master will be under ColorSelect2 folder.
Important Changes
2 Tests are failing for ColorSelect2.
I've commented them out for now, I don't think it's a blocker because it's v2 and most teams can move the v2 without these props.
required was used to add an attribute to a div, to be honest I'm not sure why we would want to add required to a div.

name was also added to the same div, also not sure why we would do it.

Screenshots & Recordings
https://user-images.githubusercontent.com/9106375/224244137-0c880ec0-3741-4b98-bfc7-533d5415bbb7.mp4
How it does that

Remove all ...props usage so we actually know which props are used.
Remove ColorSelectSpectrum and all not-needed state props.
Add react-colorful and change a bit the css to fit the props ColorSelect is providing

Testing
Unit tests from original ColorSelect are used.
All stories have been copied to have both ColorSelect and ColorSelect2

Gonna tag @tylerthegrove for a second pair of eyes since this will be the first time we'll be including a third party dependency since they were first removed. 👀


IE/Edge: prevent autoclose on option click

Hi again,
IE/Edge does not support event.composedPath. The function eventPath will always return false clicking on an option.
I did a workaround using a check on whether or not you are "hovering" the MultiSelect when the handleDocumentClick is fired. Works for me :)

..git issues;)

fix was released


DCS-1846: ✨Add expected arrivalId for temporary absence and transfer

Also, debated whether to pass through the arrivalId to the confirmation screens for monitoring purposes. Suppose we can always use 200 responses from the API /confirm endpoint with arrivalId to monitor these scenarios instead. Thoughts?


Build site WARN fix, submodule bump

Description
This pull request focused on resolving WARNs in the Build Site substep in the buildAndDeploy job. It also includes updates to the theme submodule.
Changes

Relocated editpost, assets and cover parameters in config.yml file.

Error: WARN Unknown kind "editpost" in outputs configuration.

Fixed an issue that caused an error when using the ShowFullTextinRSS parameter for updated version of RSS.xml.

Error: namespace prefix content on encoded is not defined rss

Index_profile.html and post_meta.html files are synchronized with theme updates.

post_meta.html update also contains a fix for an issue that caused meta information (day, author and etc.) to be displayed incorrectly.

Updated implemented_features.html and planned_features.html files.

Error: WARN  calling IsSet with unsupported type "invalid" (<nil>) will always return false.

Off Topic
By the way, all my best wishes for coming happy new year

Happy new year and thanks for continuously maintaining our website!!


[Bug] Row selection selects row number not incident

When checking a row it appears to leave the check on the row number and doesn't move with the incident when a new incident comes in and the selected incident gets moved to a different row.
e.x.
incident a
x incident b
incident c
If I select the row that incident b is currently on, and we get a new incident in, incident a will be selected instead
incident d
x incident a
incident b
incident c

On initial triage, it looks like this is due to the fact that we are using react-window for virtualisation.
Will need to further investigate solutions to this, potentially additional hooks to ensure the correct rows keep selection.


kogito 1.11.x to take rhba artifacts from main repo

Thank you for submitting this pull request

How to retest a PR or trigger a specific build:

* a pull request please add comment: Jenkins retest this

shouldn't be there instead of NEXT CURRENT_* variable?


Tekton Pipelines v0.30.0 requires k8s 1.20 as its minimum version

Expected Behavior
Tekton pipelines should be able to run on k8s 1.19, per the current installation guidance.
Actual Behavior
The pipelines controller reports an error that it does not support k8s 1.19.
Steps to Reproduce the Problem

Install Tekton Pipelines on a k8s 1.19 cluster
View the logs of the pipelines controller

Additional Info

Kubernetes version: 1.19.x

Tekton Pipeline version: 0.30.0

It appears that the knative dependency update to v1.0 is the root cause of this issue. See https://github.com/tektoncd/pipeline/pull/4354

Note that k8s 1.19 is no longer supported by the upstream Kubernetes community - updating relevant documentation to require k8s 1.20 would make the most sense in my opinion.
FYI @nikhil-thomas this perhaps will have an impact on the Tekton operator as well.

@adambkaplan thank you for the issue report!
updated both the release notes and documentation

release: https://github.com/tektoncd/pipeline/releases/tag/v0.30.0
documentation: https://github.com/tektoncd/pipeline/pull/4414


Update dependencies: RN 0.63.4, TS 4.1.3, etc.

And do:

the typing to silence tsc
proper indentation

Signed-off-by: Jérôme Benoit<EMAIL_ADDRESS>

@jerome-benoit Stop mixing formatting and upgrading of modules!!!
The formatting is wrong here and I cannot merge the PR!
Always doing the same mistake!!!!

@jerome-benoit Stop mixing formatting and upgrading of modules!!!
The formatting is wrong here and I cannot merge the PR!
Always doing the same mistake!!!!

It's just a mix of non functional changes like import cleanups, typing, indentation, etc. with dependencies upgrade which is the only functional change made that need more testing. It's just a convenient way to coin them in the code flow without multiplying PRs and make them easy to review: two files only for dependencies upgrade, the rest can only be non functional changes and that way they are not mixed in PRs with important functional changes. So if there's issue, it can only be because of the dependency upgrade.
That PR still have issue regarding connectors status showed but I'm not sure about the root cause yet. I put then that PR in the 'In Progress' pipeline.
And the indentation is correct in that PR like explained in another comment.

@jerome-benoit Stop mixing formatting and upgrading of modules!!!
The formatting is wrong here and I cannot merge the PR!
Always doing the same mistake!!!!

That PR still have issue regarding connectors status showed but I'm not sure about the root cause yet. I put then that PR in the 'In Progress' pipeline.

I do not understand why on offline charging station, the connector status is incorrect. The re-indentation and incorrect switch case construct fix could trigger that issue .

And the indentation is correct in that PR like explained in another comment ;).

Automatic indentation should now work properly with separating arguments in the call.

That PR still have issue regarding connectors status showed but I'm not sure about the root cause yet. I put then that PR in the 'In Progress' pipeline.

I do not understand why on offline charging stations, the connector status is incorrect. The re-indentation and incorrect switch case construct fix in getConnectorStyles() should not trigger that issue .

The ev-mobile application just displays the connector status the REST API return. On the dashboard, the connector status is forced to 'Unavailable' if the charging station is considered as offline.
We can:

do the same on the mobile app;
ensure the connectors status are set to 'Unavailable' when a charging station is flagged as offline server side.
I prefer the later.

That issue is then unrelated to that PR.

@jerome-benoit Stop mixing formatting and upgrading of modules!!!
The formatting is wrong here and I cannot merge the PR!
Always doing the same mistake!!!!

It's just a mix of non functional changes like import cleanups, typing, indentation, etc. with dependencies upgrade which is the only functional change made that need more testing. It's just a convenient way to coin them in the code flow without multiplying PRs and make them easy to review: two files only for dependencies upgrade, the rest can only be non functional changes and that way they are not mixed in PRs with important functional changes. So if there's issue, it can only be because of the dependencies upgrade.
That PR still have issue regarding connectors status showed but I'm not sure about the root cause yet. I put then that PR in the 'In Progress' pipeline.
And the indentation is correct in that PR like explained in another comment ;).

Same comment :-)
I cannot read your updates as there are too many changes.
Next time create a new PR for this purpose or I'll close it.

The ev-mobile application just displays the connector status the REST API return. On the dashboard, the connector status is forced to 'Unavailable' if the charging station is considered as offline.

We have to do it at UI level to avoid processing time at backend level.
Moreover, you may want also to know the latest status of the connectors before it went offline.

The ev-mobile application just displays the connector status the REST API return. On the dashboard, the connector status is forced to 'Unavailable' if the charging station is considered as offline.

We have to do it at UI level to avoid processing time at backend level.
Moreover, you may want also to know the latest status of the connectors before it went offline.

I just did it in V1.3.33

@jerome-benoit Stop mixing formatting and upgrading of modules!!!
The formatting is wrong here and I cannot merge the PR!
Always doing the same mistake!!!!

It's just a mix of non functional changes like import cleanups, typing, indentation, etc. with dependencies upgrade which is the only functional change made that need more testing. It's just a convenient way to coin them in the code flow without multiplying PRs and make them easy to review: two files only for dependencies upgrade, the rest can only be non functional changes and that way they are not mixed in PRs with important functional changes. So if there's issue, it can only be because of the dependencies upgrade.
That PR still have issue regarding connectors status showed but I'm not sure about the root cause yet. I put then that PR in the 'In Progress' pipeline.
And the indentation is correct in that PR like explained in another comment ;).

Same comment :-)
I cannot read your updates as there are too many changes.
Next time create a new PR for this purpose or I'll close it.

And then you will complain about having too much PRs not attached to an issue:

one for typing
one for code style
one for dependencies update
one for logic misconstruct
...

;)
Sometimes rules need some small violation to fit in.
Usually there's less non functional unrelated changes to review but that PR is opened for more than a month: more important changes were expected to go in before its merge. So the size of the unrelated changes have increased over time during the wait.
In any case, I've addressed the comments done in the review, tested it (need npm run android:clean, npm run pod:install, etc.). It contains some genuine fixes related to the RN style typing, logic misconstruct or security.

And then you will complain about having too much PRs not attached to an issue:

You almost never do that anyway!

one for typing
one for code style
one for dependencies update
one for logic misconstruct
...

You can group some of these topics together

Sometimes rules need some small violation to fit in.

It's more a rule than an exception with you ;-)

Usually there's less non functional unrelated changes to review but that PR is opened for more than a month: more
important changes were expected to go in before its merge. So the size of the unrelated changes have increased over time
during the wait.

That's normal, I do not merge when you update RN version that can impact current dev before an imminent prod release you are not aware of. But I can merge code style changes...

In any case, I've addressed the comments done in the review, tested it (needs npm run android:clean, npm run pod:install, etc.). It contains some genuine fixes related to the RN style typing and composition, logic misconstruct or security.

Conflicts resolved (again).
The dependencies upgrade are either against the correction or patch in their SemVer, except for one for security reason. So it's a safe upgrade path and the update that might contains breaking changes have been tested to work as intended.


Cache: Build info file does not contain storage layout

Hi, thanks for the repository, it helps a lot to setup upgrades with foundry.
There is a problem with foundry output storageLayout after the first successful run which requires us to yarn clean all the time before testing. I'm not sure it's an issue with this or foundry itself.
Step to reproduce:

Done everything documented in README and have your first successful test with yarn test --ffi -vvv
Change anything in the test files to invalidate the output artifacts
Run yarn test --ffi -vvv again. It should fail now because of missing storage layout.
yarn clean && yarn test --ffi -vvv again. It runs successfully.
Now every time I want to test, I need to yarn clean =(

Thanks @ericglau for the tech explanation. The --force works for the CI.

I'm running into this problem when executing forge scripts, even after forge clean or when using --force.
Both fixes do work for us when running forge test --ffi --force, but not when running forge script script/DeployContracts.s.sol:DeployContracts \   --fork-url ${RPC_URL} \   --broadcast \   -vvvv \   --private-key ${DEPLOYER_PRIVATE_KEY} \   --ffi \   --force

In both cases, I have manually verified and can see that out/build-info does contain a file which seems to have storageLayouts.

2024-01-14T12:11:55.161932Z ERROR cheatcodes: non-empty stderr input=["npx", "<EMAIL_ADDRESS>"validate", "out/build-info", "--contract", "src/TimePiecePassport.sol:TimePiecePassport"] stderr="/Users/rick/.npm/_npx/db46e24580d42758/node_modules/@openzeppelin/upgrades-core/dist/cli/validate/build-info-file.js:101\n                throw new error_1.ValidateCommandError(`Build info file ${buildInfoFilePath} does not contain storage layout.`, () => STORAGE_LAYOUT_HELP);\n                      ^\n\nValidateCommandError: Build info file out/build-info/61112cbfc9266bc57d70b1becfbe095a.json does not contain storage layout.\n\nIf using Hardhat, include the 'storageLayout' output selection in your Hardhat config:\n  module.exports = {\n    solidity: {\n      settings: {\n        outputSelection: {\n          '*': {\n            '*': ['storageLayout'],\n          },\n        },\n      },\n    },\n  };\nThen recompile your contracts with 'npx hardhat clean && npx hardhat compile' and try again.\n\nIf using Foundry, include the \"storageLayout\" extra output in foundry.toml:\n  [profile.default]\n  build_info = true\n  extra_output = [\"storageLayout\"]\nThen recompile your contracts with 'forge clean && forge build' and try again.\n    at readBuildInfo (/Users/rick/.npm/_npx/db46e24580d42758/node_modules/@openzeppelin/upgrades-core/dist/cli/validate/build-info-file.js:101:23)\n    at async getBuildInfoFiles (/Users/rick/.npm/_npx/db46e24580d42758/node_modules/@openzeppelin/upgrades-core/dist/cli/validate/build-info-file.js:41:12)\n    at async validateUpgradeSafety (/Users/rick/.npm/_npx/db46e24580d42758/node_modules/@openzeppelin/upgrades-core/dist/cli/validate/validate-upgrade-safety.js:22:28)\n    at async main (/Users/rick/.npm/_npx/db46e24580d42758/node_modules/@openzeppelin/upgrades-core/dist/cli/validate.js:30:24)\n    at async run (/Users/rick/.npm/_npx/db46e24580d42758/node_modules/@openzeppelin/upgrades-core/dist/cli/cli.js:6:5)\n\nNode.js v18.17.0\n"

@RickVM Thanks for reporting, I see this as well and am working on a fix.  This happens due to a recent change in Foundry that affects the output format for scripts.  As a workaround for now, you can forge clean, forge test, then forge script in that order without modifying anything in between those steps.

The issue with forge script above is fixed in the linked PRs.  You can get the fix by either updating your submodule for this repository, or by updating your installed npm package of @openzeppelin/upgrades-core.
Note that the limitation mentioned in my earlier comment still exists -- that is, you still need to either run forge clean before running scripts or tests, or use --force with forge script or forge test to do a full compilation in order for upgrade safety validations to work.
Otherwise, you will get an error like Build info file is not from a full compilation.


Make compatible with TYPO3 v12.0

It would be great to have a version until the release of TYPO3 12.0

Code is currently not compatible so we can't just raise the version but also have to make the implementation compatible.

Has been resolved in #82


Pure functions

Adds pure functions. Pure functions are normal functions with additional constraints.
An example of a pure function is the following.
pure_fn :: pu x ->
  x * 2
end

The constraints in a pure function are the following:

You cannot make assignments.
You cannot declare mutable variables.
You cannot read mutable variables (in global scope).

To do:

[ ] Tests
[ ] Somehow restrict access to const blobs and list, since they are not actually immutable. Either adding more constraints or in a separate issue.
[ ] Fix function calls in impure functions that are not assigned.

Design decision time!
These two tests should fail, but for what reason?
https://github.com/sylt-lang/sylt-lang/blob/pure-functions/tests/pure/impure_access_list.sy
https://github.com/sylt-lang/sylt-lang/blob/pure-functions/tests/pure/impure_access_blob.sy
The two options are:

Disallow reading lists, blobs, etc. that are in scope of the definition because they can be mutated.
Disallow mutation of lists, blobs, etc. that are not declared as mutable.

When it comes to blobs and lists in pure functions, I'd say we allow it now and change how constant works so nothing inside a constant list is mutable and nothing inside a constant blob is mutable. In my opinion this is a better understanding structure.
But the change to constants actually being constants is a little bit to big for what I think this PR should be. It's usually better to merge smaller PRs since they're easier to review. I'd say merge this and fix the mutability as a next PR. How does that feel?

When it comes to blobs and lists in pure functions, I'd say we allow it now and change how constant works so nothing inside a constant list is mutable and nothing inside a constant blob is mutable. In my opinion this is a better understanding structure.

This sounds good.

But the change to constants actually being constants is a little bit to big for what I think this PR should be. It's usually better to merge smaller PRs since they're easier to review. I'd say merge this and fix the mutability as a next PR. How does that feel?

I agree, my thinking was just that if we wanted to restrict access to blobs, lists, etc. it might be smaller and fit inside this pr.


[WIP] Improve reference widget

with https://github.com/plone/plone.restapi/pull/539 plone.restapi request, we have the widget property for relation widget
with that property we can select the right widget in plone-react
the widget allow to navigate through folders like gdrive widget

missing tasks

[ ] tests for new components
[ ] clearing the navigator component
[ ] review the interface with an ux designer
[ ] retrieve the title of current selected folder in the navigation component
[x] default query when open the widget

Coverage decreased (-0.2%) to 54.341% when pulling 83da4ca5059602afe7f20c5eb46479f11444395e on improve-reference-widget into c50acd6fe17557c3cfb0ef7327f3c70847545e7d on master.

There is a basic reference widget and another more sophisticated it's on its way, being taking cared by the RT folks.


Button text when removing Yalu

When removing Yalu (to update it to the latest beta version) the two buttons indicates "None".

You don't even need to remove yalu to install a new version. Anyway looks like some tweak side effect


UCE using multi-gpu

Hi @Yanay1
Do you know why UCE repotred the following error When I setted multi-gpu True. I had launched hugging face on command line:
huggingface-cli login
(scanpy) root@iZ1pp06g2kc1mpkdbn2uzzZ:/home/jinfang/backup/jinfang/songmf/007-uce/UCE# python eval_single_anndata.py --adata_path /home/jinfang/backup/jinfang/songmf/000-Data/HCC_snRNA/HCC_MET_KM.h5ad --dir /home/jinfang/backup/jinfang/songmf/007-uce/UCE/HCC_MET_KM --species human --model_loc /home/jinfang/backup/jinfang/songmf/007-uce/UCE/model_files/4layer_model.torch --batch_size 100 --multi_gpu True Proccessing HCC_MET_KM 8222.0 HCC_MET_KM (43574, 15502) Wrote Shapes Dict 15502 Max Code: 613 Loaded model: /home/jinfang/backup/jinfang/songmf/007-uce/UCE/model_files/4layer_model.torch   0%|                                                                                | 0/436 [00:02<?, ?it/s] Traceback (most recent call last):   File "/mnt/array3/jinfang/songmf/007-uce/UCE/eval_single_anndata.py", line 155, in <module>     main(args, accelerator)   File "/mnt/array3/jinfang/songmf/007-uce/UCE/eval_single_anndata.py", line 85, in main     processor.run_evaluation()   File "/mnt/array3/jinfang/songmf/007-uce/UCE/evaluate.py", line 145, in run_evaluation     run_eval(self.adata, self.name, self.pe_idx_path, self.chroms_path,   File "/mnt/array3/jinfang/songmf/007-uce/UCE/evaluate.py", line 239, in run_eval     batch_sentences = model.module.pe_embedding(batch_sentences.long())                       ^^^^^^^^^^^^   File "/bio/anaconda3/envs/scanpy/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1614, in __getattr__     raise AttributeError("'{}' object has no attribute '{}'".format( AttributeError: 'TransformerModel' object has no attribute 'module'. Did you mean: 'modules'?

When you use multi-gpu it has to be with hugging face accelerator. So it needs to be launched with accelerate rather than just python (see: https://huggingface.co/docs/accelerate/en/index)


UI - Verifying permissions prior to checking Remote Process Group transmission status

NIFI-3023:

Verifying permissions prior to checking Remote Process Group transmission status.

Reviewing....

The proposed changes look good and prevent the app from throwing an error when the user does not have permissions to read the remote process group. However, I noticed that the 'transmitting' and 'not-transmitting' classes are being applied even when the remote process group is 'invalid'. This is causing the warning icon fill color to be overridden to #728e9b instead of the #cf9f5d. Could you please add a check for invalid state when applying the 'transmitting' and 'not-transmitting' class?

Will do. Thanks!

Thanks @mcgilman this has been merged to master.


Throw error when esnext found in JSCS config file

So, it turns out that putting "esnext": true in .jscsrc unfortunately does nothing; that option has to be specified at a higher level (e.g. Grunt). Given that, perhaps an error could be thrown when esnext is found in the config file, explicitly stating that it cannot be set via the config file? Makes it easier for the user to discover their mistake.

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

It does nothing? http://jscs.info/overview.html#esnext
/cc @mikesherov

@cvrebert, what version of JSCS are you using? Specifying in jscsrc should work...
What happens when you have esnext in your .jscsrc and run jscs from the command line and not via the grunt plugin?

Looks like I was on crack when filing this, as I couldn't repro when trying to put together a nice testcase. My apologies for the trouble!


Create gh-redoc

What/Why/How?
Reference
Testing
Screenshots (optional)
Check yourself

[ ] Code is linted
[ ] Tested
[ ] All new/updated code is covered with tests

Security

[ ] Security impact of change has been considered
[ ] Code follows company security practices and guidelines

created gh-redoc


grouped.filter with axis=1 gave filtered rows

using pandas 0.16.2
minimum example here:
import numpy as np
import pandas as pd

index = pd.MultiIndex.from_product([range(10), [0, 1]])
data = pd.DataFrame(np.arange(100).reshape(-1, 20), columns=index)
data.groupby(level=0, axis=1).filter(lambda x: x.iloc[0, 0] > 10)

expected: get all filtered (grouped) columns as a DataFrame
result: IndexError
when change np.arange(100) to np.arange(1000) (more rows than columns)
results data frame with missing rows.

This is a bug here
self.axis needs to be passed to .take
want to do a pull-request?

I'll submit a PR soon. But how to create this expected DataFrame in unit test?
In [5]: data.groupby(level=0, axis=1).filter(lambda x: x.iloc[0, 0] > 10)
Out[5]:
    6       7       8       9
    0   1   0   1   0   1   0   1
0  12  13  14  15  16  17  18  19
1  32  33  34  35  36  37  38  39
2  52  53  54  55  56  57  58  59
3  72  73  74  75  76  77  78  79
4  92  93  94  95  96  97  98  99

So in R, there's this dput() method that we can use to get the declaration of a data frame. Is there a similar method in pandas that we can use to make the data frame reproducible?

@terrytangyuan That's fast! :-P

@tdihp  thanks. Hope this could solve your problem.

closed by #11055


Creating internet-monitoring_promethus_1 Failed

After about 30 mins from running ansible-playbook main.yml on the Pi get the below error. I have tried with the inventory.ini file pointing to the IP as apposed to local but i get a different error referenced in Issue #277
TASK [Copy templated internet-monitoring files into place.] ********************
ok: [<IP_ADDRESS>] => (item={'src': 'grafana-config.monitoring.j2', 'dest': 'grafana/config.monitoring'})
ok: [<IP_ADDRESS>] => (item={'src': 'prometheus.yml.j2', 'dest': 'prometheus/prometheus.yml'})
ok: [<IP_ADDRESS>] => (item={'src': 'prometheus-pinghosts.yaml.j2', 'dest': 'prometheus/pinghosts.yaml'})
TASK [Ensure internet-monitoring environment is running.] **********************
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": false, "errors": [], "module_stderr": "Creating internet-monitoring_prometheus_1 ... \n", "module_stdout": "", "msg": "Error starting project UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"}
PLAY RECAP *********************************************************************
<IP_ADDRESS>                  : ok=12   changed=0    unreachable=0    failed=1    skipped=7    rescued=0    ignored=0
Inventory.ini
[internet_pi]
#<IP_ADDRESS> ansible_user=pi
Comment out the previous line and uncomment this to run inside Raspberry Pi.
<IP_ADDRESS> ansible_connection=local ansible_user=pi
config.xml
Location where configuration files will be stored.
config_dir: '~'
Pi-hole configuration.
pihole_enable: true
pihole_hostname: pihole
pihole_timezone: America/Chicago
pihole_password: "Pass1234!"
Internet monitoring configuration.
monitoring_enable: true
monitoring_grafana_admin_password: "Pass1234!"
monitoring_speedtest_interval: 60m
monitoring_ping_interval: 5s
monitoring_ping_hosts:  # [URL];[HUMAN_READABLE_NAME]

http://www.google.com/;google.com
https://github.com/;github.com
https://www.apple.com/;apple.com

Shelly Plug configuration. (Also requires monitoring_enable)
shelly_plug_enable: false
shelly_plug_hostname: <IP_ADDRESS>
shelly_plug_http_username: pi
shelly_plug_http_password: "Pass1234!"
AirGradient configuration. (Also requires monitoring_enable)
airgradient_enable: false
airgradient_sensors:
ID Should be limited to no more than 38 characters, in the set a-z.

id: raspberrypi
ip: "<IP_ADDRESS>"

Starlink configuration. (Also requires monitoring_enable)
starlink_enable: false

I'm experiencing exactly the same issue - clean current install of Raspberry Pi OS Lite 32 bit, ansible running remotely. IP address changed in inventory.ini, passwords in config.yml otherwise default.
Playbook task that fails:
TASK [Ensure internet-monitoring environment is running.] ***************************************************************************
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": false, "errors": [], "module_stderr": "Starting internet-monitoring_prometheus_1 ... \n", "module_stdout": "", "msg": "Error starting project UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"}

Interestingly, I went away, came back with a fresh head, and a fresh 32GB SD card (previously it was onlya 16GB card), and the exact same ansible config installed. It might be the extra resource aloowed some of the downloads to work?


Expand test suite and implement benchmarking suite

This crate needs additional unit testing and, more importantly, integration testing.
The proposed test suite will involve miri to help detect UB, and the addition of a few more dev-dependencies to make it easier to write high-quality, meaningful tests.
In addition to this, I would like to add a basic benchmarking suite to start, and then it can be expanded upon from there. The most important functions to benchmark are those that involve reading data into slices vs. arrays (Bytes / Chunk<N> types).
Ideally, this will make it into v0.3.0 to give end-users a better picture of what the crate's capabilities are. There are not many crates in this particular area (zero copy direct reading/writing from byte slices aka "safe transmute"), so it is crucial that abio is able to compete with these crates.

This did not make it into the initial public release, but should be rolled into v0.3.1 instead.

Due to the massive amount of changes and refactoring, it is unlikely that a patched or minor version can be released without introducing breaking changes. Thus, the focus is currently on releasing a stable, ergonomic 0.4.0 that will fix many of the severe flaws in the current code base.
I will be closing this issue for now since the test suite and benchmarking suite will both be added as soon as possible.
If you would like to help, I would absolutely love that and I will gladly re-open this issue (or crate a new one) to encapsulate the work required to complete this feature.


Add "file" field to PackageArtifactInfo

This change adds the file field to the PackageArtifactInfo provider.  This
allows consuming rules to directly access the named artifact file, as opposed to
having to search the artifact target's DefaultInfo for it.
PackageArtifactInfo.file_name is now deprecated.  The same information can be
acquired from PackageArtifactInfo.file.
Basic tests for the validity of this field have been added to pkg_rpm.  I can look into adding tests for the others if desired.
This doesn't solve all the problems with PackageArtifactInfo, but it's a step in the right direction.
Fixes #433.

'workspace_stanza': workspace_stanza,
--
  | UnicodeEncodeError: 'ascii' codec can't encode character '\u2026' in position 1420: ordinal not in range(128)

Cool. Unicode problems. I hope this is because I just added the non latin1 filenames to the test data

I'm merging even though the integration tests are failing. That is clearly the non-ASCII in the changelog.


Add CosmicNvim and Cosmic-ui

Checklist:

[x] The plugin is specifically built for Neovim.
[ ] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] It's not already on the list.
[ ] It supports treesitter syntax if it's a colorscheme.

The lines end with a .. This is to conform to awesome-list linting and requirements.

Not sure about this one. My descriptions have an "!" at the end of lines like some of the other descriptions. Can change if needed.

Thanks for the PR!


build: Updated lara-interactive-api to 1.9.4 [PT-185396456]

Looks good 👍
It's definitely nice to have, as lara-interactve-api 1.9.4 added a check that tests if only one copy of lara-interactve-api is imported. But as I mentioned on Slack - no bug fixes, features, or PT stories depend on that. So, I don't think we need to release QI v1.15.1 or anything like that.


Installed Packages Checker - spawn error

Type: Bug

Behaviour
Expected vs. Actual
Launching VS Code from a virtualenv (virtualenvwrapper) environment located under ~/.virtualenvs folder, with python. defaultInterpreterPath properly set, the Python extension produces error: [error] Error while getting installed packages check result:
Steps to reproduce:

Launch VS Code from the root directory of an activated virtualenv (virtualenvwrapper) environment using code .
Click on requirements.txt file in the Explorer

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.10.10
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): virtualenv
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

2024-02-23 23:08:47.592 [info] Telemetry is disabled
2024-02-23 23:08:47.592 [info] Experiments are disabled, only manually opted experiments are active.
2024-02-23 23:08:47.593 [info] Default formatter is set to ms-python.black-formatter for workspace /Users/mac.user/code/python_workspace/llamaindex_test
2024-02-23 23:08:47.593 [info] VS Code was launched from an activated environment: 'llamaindex_test', selecting it as the interpreter for workspace.
2024-02-23 23:08:47.593 [info] Test server listening.
2024-02-23 23:08:47.593 [info] Python interpreter path: ~/.virtualenvs/llamaindex_test/bin/python
2024-02-23 23:08:51.722 [info] Starting Pylance language server.
2024-02-23 23:09:12.574 [info] Running installed packages checker:  /Users/mac.user/.virtualenvs/llamaindex_test /Users/mac.user/.vscode/extensions/ms-python.python-2024.0.1/pythonFiles/installed_check.py /Users/mac.user/code/python_workspace/llamaindex_test/requirements-dev-tools.txt
2024-02-23 23:09:12.574 [info] > ~/.virtualenvs/llamaindex_test ~/.vscode/extensions/ms-python.python-2024.0.1/pythonFiles/installed_check.py ./requirements-dev-tools.txt
2024-02-23 23:09:12.575 [error] Error while getting installed packages check result:
Error: spawn /Users/mac.user/.virtualenvs/llamaindex_test EACCES
at Process.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -13,
code: 'EACCES',
syscall: 'spawn /Users/mac.user/.virtualenvs/llamaindex_test',
path: '/Users/mac.user/.virtualenvs/llamaindex_test',
spawnargs: [
'/Users/mac.user/.vscode/extensions/ms-python.python-2024.0.1/pythonFiles/installed_check.py',
'/Users/mac.user/code/python_workspace/llamaindex_test/requirements-dev-tools.txt'
]
}

User Settings

languageServer: "Pylance"

testing
• unittestArgs: "<placeholder>"
• unittestEnabled: true

Extension version: 2024.0.1
VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:42:13.651Z)
OS version: Darwin x64 21.6.0
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2500)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (3.09GB free)

Process Argv
.

Screen Reader
no

VM
0%

It appears that that the the command to launch installed package checker is truncated, containing only the root virtualenv folder and not the complete path to Python interpreter:
~/.virtualenvs/llamaindex_test ~/.vscode/extensions/ms-python.python-2024.0.1/pythonFiles/installed_check.py ./requirements-dev-tools.txt
When I run the above command with the path to the interpreter included on a terminal, it works fine:
> ~/.virtualenvs/llamaindex_test/bin/python ~/.vscode/extensions/ms-python.python-2024.0.1/pythonFiles/installed_check.py ./requirements-dev-tools.txt
[{"line": 10, "character": 0, "endLine": 10, "endCharacter": 13, "package": "flake8-bandit", "code": "not-installed", "severity": 3}]

@karrtikr Do we need to use a different API to get the executable?
https://github.com/microsoft/vscode-python/blob/e6c859dc03b32a4b5f6bc83a8fa4df2798734c19/src/client/pythonEnvironments/creation/common/installCheckUtils.ts#L62

Yes, it should be using IInterpreterService instead.

Hi @umairishaq are you able to verify if this fix is working? It is out on vscode- insiders with the python pre-release of the extension so you can try it there if you are able. Thanks!

@karthiknadig are there verification steps here if they don't get back to us in time?


operator pelorus-operator (0.0.3)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description of the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@mpryc please review :smile:

/merge possible

/ok-to-test

/retest

/merge possible

/test 4.9-deploy-operator-on-openshift

/merge possible


Add Dockerfile

Hi all,
I think it's better if we have a Dockerfile for Fossor ;) Thanks.
Best Regards,

Could you go into more detail? Is your intention to run an isolated instance of Fossor inside of its own docker container?

Ya, if we have docker image of Fossor, we don't need to install dependency (using yum or apt), just run "docker run ..."
Best Regards,

That sounds helpful. I'm open to a pull request if you (or someone else) is up for adding that.


rclcpp design

Link to https://github.com/esteve/ros2_java/pull/8

@Theosakamg @elehuitouze thanks for your contributions, they are great!
As I told @Theosakamg on his ros2_java pull request (https://github.com/esteve/ros2_java/pull/8#issuecomment-257613110 and https://github.com/esteve/ros2_java/pull/8#issuecomment-260190111), I would really prefer if you created separate pull requests for each improvement, I can't merge this pull request as is.
One particular thing is that this pull request replaces the Gradle plugin with your own. It'd be great if you submitted any improvements to the Gradle plugin I created (https://github.com/esteve/ament_gradle_plugin), otherwise it's going to confuse users as to which Gradle plugin to use. Moreover, what features were missing in my Gradle plugin? I had a quick look at yours and it does not work with Android, and the support for Eclipse in your plugin is broken. If you want to add support for Eclipse, you only need to modify the build.gradle file in a Gradle project to add apply plugin: 'eclipse' (https://docs.gradle.org/current/userguide/eclipse_plugin.html#sec:eclipse_usage), so I don't fully understand why you built that into your Gradle plugin.

@Theosakamg @elehuitouze so, any update? No response from you guys since I ask you to split it into concrete pull requests, so I'm thinking of closing this pull request in the following days if I don't heard from you.

@esteve Sorry for delay. the PR is WIP.


Update extsprintf dependency

My build system is presently stuck behind a firewall, the misconfiguration of which is making it hard to get to github.  We have a caching NPM proxy, which works well, and all of the modules we use during the build are presently cached.  However, when node-jsprim pulls in a relatively old version of extsprintf (1.0.2), the git submodules initialization fails for git://github.com/... URIs.  Those git submodules were removed from extsprintf in commit 76e9d14be8d6a jsPrintf dicey use of arguments.  So updating the dependency would help us out in this (admittedly fringe) case.
I'm filing this issue and will followup with a PR to resolve it along with #21.
Happy to take guidance on other solutions, but this seemed to me to make sense.

Sure!
This repo uses a different contribution process now, but that was never updated in the README or a contributing file.  I'll put together a change for this issue, #21, and to update the contribution guidelines.

Proposed change: https://cr.joyent.us/#/c/2317/1
This is make prepush clean.

Published in v1.4.1.


Feature request: set_dictionary in pure Rust backend

I'd like to use the mentioned functionality in a project that is built to WASM, so only using native Rust stuff is preferred.
Based on https://github.com/rust-lang/flate2-rs/pull/74#issuecomment-372338710, adding this "should be relatively simple".

Actually, for this purpose, if any of the available zlib backends supports seamless compiling to WASM from source, that would also work... :no_mouth:

Thanks for posting. After taking a closer look, I believe this feature request should first be posted over at the miniz_oxide which is the implementation used here when the Rust backend is chosen.
Once available, it should be trivial to make set_dictionary available here.
WASM support is available in this crate as well, even though it does seem to default to miniz_oxide when that happens. Thus the way forward truly seems to be to get the desired feature implemented in miniz_oxide.
For that reason, I am closing the issue here as I trust you will open a new one once the pre-requisites are fulfilled. Thanks for your understanding.


fixed #1068 drush need mysql-client installed

I completed the 3 steps below:

[Y] I've read the Contribution Guide.
[Y] I've updated the documentation. (refer to this for how to do so).
[Y] I enjoyed my time contributing and making developer's life easier :)

Any idea on failed travis test?
I just install a mysql client.

@terryzwt It's filing for some reason before you PR. If you have some time to fix it would be great, but it's not caused by this PR.


HiKey: make linux sd boot entry look for BOOTAA64.EFI

Better to use the generic EFI firmware name when producing images that can be loaded via external devices, such as sdcard and usb. With this change, any distro can be easily supported as long they provide a MBR SD card setup with 2 partitions, and the first (fat) providing one compatible EFI bootloader as BOOTAA64.EFI.
Tested with https://builds.96boards.org/snapshots/reference-platform/debian/latest/hikey/hikey-debian-jessie-alip-20160503-84.img.gz flashed in a sdcard.
Since LeMaker is not yet using this firmware for factory, we can work with them to convert their image to be compatible with this new path/scheme.

@hzhuang1  any update here?


Stack recursive deletion

Describe changes
I implemented/fixed _ to achieve _.
Pre-requisites
Please ensure you have done the following:

[x ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ x] I have added tests to cover my changes.

Types of changes

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

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: safoinme:x: KenmogneThimoteeYou have signed the CLA already but the status is still pending? Let us recheck it.

Hi @KenmogneThimotee. Thanks for this PR. It actually needs to be based off the develop branch and not main (see our contribution guidelines for more info). Thanks!