Upgrade brotli to 0.6.0

As a side effect, the bindings have become much simplified because they don't need to contain all the internal details of the decoder struct any more.
Some thoughts before merging

BrotliDecompressedSize is gone with no replacement. This means I've removed the decompressed_size method, which doesn't make me too sad since the comment seemed to basicaly say "this isn't reliable". On the other hand, it's backwards incompatible. If we really wanted to preserve this rather than bump version, we could ask the brotli project if they plan to add anything back.
I've removed some commented out methods using APIs that were deprecated and are now removed.
The API we're now making use of is deprecated (as revealed by ctest, which I've not come across before and is nifty), so I've disabled deprecated warnings for now. I've only done this on non-msvc because a look at ctest seems to indicate that this warning is disabled by default for msvc for some reason (been there since the initial commit)? (I've not actually tested msvc)
I've added a few TODOs for using the newer APIs (BrotliEncoderCompressStream function for compression, more compression parameters, human readable errors when decoding) that didn't seem particularly crucial for this upgrade.

Regarding "The API we're now making use of is deprecated" - this is the 'low level API' and was marked as deprecated with the recommended new route appearing to be the high level API.
Moving to use the higher-level API effectively brings the Compress struct in line with Decompress, i.e. no more copy_input and a change in signature of the compress function. This is (also) a breaking change so is probably worth considering as part of this PR.
If this was a pure rust project I'd be pretty gung-ho about all of this, but multiple versions of brotli can't be linked into the same application which makes it tricky. Any thoughts on best ways to do this?

Thanks for this! It looks like a number of breaking changes have happened at the actual library itself, so I'm totally fine just releasing new major versions of this and the sys crate. You're right that links may cause problems, but this isn't necessarily a hugely shared dep so it may not be that hard to upgrade?
Did you want to roll the updates into this PR or wait for a future one? I'm fine either way!

Yeah I guess better to make the breaking changes sooner rather than later when it becomes more widely used. I'll put the updates into this PR.

I think it's worth reviewing and considering this PR independently actually. Some benchmarking I did shows that this is noticeably slower, between 20 and 50%.
Here's a somewhat stripped version of the script I'm using to test:
extern crate brotli2;
extern crate rand;

use std::io::{Read, Write};
use brotli2::read;
use brotli2::write;
use brotli2::stream::{CompressParams, compress_buf, decompress_buf};
use rand::Rng;
use rand::SeedableRng;

// Used in functions as temporary storage space before producing a vec
const BIGBUF_SIZE: usize = 120*1024*1024;
static mut BIGBUF: [u8; BIGBUF_SIZE] = [0; BIGBUF_SIZE];

fn main() {
    let v1 = vec![1; 1024];
    let v2 = vec![44; 10*1024*1024];
    let mut params = CompressParams::new();
    params.mode(brotli2::stream::CompressMode::Text).quality(6);
    let params = &params;

    fn bufencode(data: &[u8], params: &CompressParams) -> Vec<u8> {
        let bufref = &mut unsafe { &mut BIGBUF[..] };
        let n = compress_buf(params, data, bufref).unwrap();
        assert!(n > 0 && n <= BIGBUF_SIZE && n == bufref.len());
        bufref.to_owned()
    }
    fn bufdecode(data: &[u8]) -> Vec<u8> {
        let bufref = &mut unsafe { &mut BIGBUF[..] };
        let s = decompress_buf(data, bufref).unwrap();
        assert!(s == brotli2::stream::Status::Finished);
        bufref.to_owned()
    }
    fn ioreadencode(data: &[u8], params: &CompressParams) -> Vec<u8> {
        let mut buf = vec![];
        read::BrotliEncoder::from_params(data, params).read_to_end(&mut buf).unwrap();
        assert!(buf.len() > 0);
        buf
    }
    fn ioreaddecode (data: &[u8]) -> Vec<u8> {
        let mut buf = vec![];
        read::BrotliDecoder::new(data).read_to_end(&mut buf).unwrap();
        buf
    }
    fn iowriteencode(data: &[u8], params: &CompressParams) -> Vec<u8> {
        let mut enc = write::BrotliEncoder::from_params(vec![], params);
        enc.write_all(data).unwrap();
        enc.finish().unwrap()
    }
    fn iowritedecode(data: &[u8]) -> Vec<u8> {
        let mut dec = write::BrotliDecoder::new(vec![]);
        dec.write_all(data).unwrap();
        dec.finish().unwrap()
    }

    let check = |data: &[u8]| {
        let c1 = &bufencode(data, params);
        let _ = &ioreadencode(data, params);
        let _ = &iowriteencode(data, params);
        assert!(data == &*bufdecode(c1));
        assert!(data == &*ioreaddecode(c1));
        assert!(data == &*iowritedecode(c1));
    };

    let mut rng = rand::XorShiftRng::from_seed([1, 4, 55, 98]);
    for _ in 0..5 {
        let rnum: usize = rng.gen_range(1, 100*1024*1024);
        let mut buf = vec![0; rnum];
        rng.fill_bytes(&mut buf);
        check(&buf)
    }
}

With 0.2.3:
real    0m17.171s
user    0m16.200s
sys     0m0.968s

With this PR:
real    0m21.711s
user    0m20.652s
sys     0m1.056s

I've not really changed anything other than doing the upgrade. Doing a very brief test with the bro tool doesn't show a similar slowdown.

So everything in this branch looks good to me, but the benchmark you posted seems worrisome! Is that an artifact of using the deprecated APIs? Does using the "right" apis in https://github.com/alexcrichton/brotli2-rs/pull/11 fix the speed loss?
If not, mind profiling to see where the time is spent? (e.g. in brotli vs in Rust)

Reported at google/brotli#550

Awesome, thanks for investigating! Does that mean we're still good for upgrading, maybe just with known caveats?

Turns out the delta between the last good version and v0.6.0 (where I was going to upgrade to) isn't that big (https://github.com/google/brotli/compare/cdca91b~1...v0.6.0), so I've just picked that last good commit.
Perf differences (measured by the example I added in the pre-upgrade commit, so that we can track over time) are about 10% slower for the new version, but it looks like there was a commit implementing better compression since the version we use so maybe that's expected.
Also, decompress_buf only returns true or false so there's no point in it returning a return status (it now returns a length, which is already available via .len I guess). I changed this in the pre-upgrade commit so the example can remain unchanged.

Oh, should I add the example to the .travis.yml since it's also sort of a test? It takes about 12s.

Ok changes sound great to me! I'm gonna go ahead and merge but yeah feel free to throw in running the example to travis, 12s isn't so bad!


ERROR [5/8] RUN chmod +x /opt/realsense/build-librealsense.sh && /opt/realsense/build-librealsense.sh

I was following the instruction on this page [(https://github.com/NVIDIA-ISAAC-ROS/.github/blob/main/profile/realsense-setup.md)]
At Step 5 ,I was trying to launch the docker.
But it keeps going wrong and i can not build base image.
Also,I see that script is trying to install realsense SDK 2.54, but realsense-ros 4.51 only support realsense SDK 2.51.
How to fix that?

This looks like a transient failure (unable to pull the appropriate build script) could you try running it again?


workflows/check-by-name: Better error when base branch also fails

Description of changes
Previously, even if the check also failed on the base branch, it would look like the PR introduced the failure (though I don't think this even happened).
We can have a better error message for such cases by also running the tool on the base branch, which is achievable with little extra effort.
However the main motivation really is that this paves the road towards https://github.com/NixOS/nixpkgs/issues/256788.
Note that due to using pull_request_target instead of pull_request, this PR itself does not trigger the new workflow.
Things done

[x] Tested all configurations of failing/succeeding base/PR:

[x] https://github.com/tweag/nixpkgs/pull/70
[x] https://github.com/tweag/nixpkgs/pull/69
[x] https://github.com/tweag/nixpkgs/pull/72
[x] https://github.com/tweag/nixpkgs/pull/71

[x] Verified that the CI check is not significantly slower

@roberth @RonnyPfannschmidt Now added a github workflow summary!

Ok -> Ok
Ok -> Fail
Fail -> Ok
Fail -> Fail


IGNITE-12781 Fixes security context propagation for cache events.

Thank you for submitting the pull request to the Apache Ignite.
In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:
The Contribution Checklist

[ ] There is a single JIRA ticket related to the pull request.
[ ] The web-link to the pull request is attached to the JIRA ticket.
[ ] The JIRA ticket has the Patch Available state.
[ ] The pull request body describes changes that have been made.
The description explains WHAT and WHY was made instead of HOW.
[ ] The pull request title is treated as the final commit message.
The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
[ ] A reviewer has been mentioned through the JIRA comments
(see the Maintainers list)
[ ] The pull request has been checked by the Teamcity Bot and
the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

How to Contribute
Coding abbreviation rules
Coding Guidelines
Apache Ignite Teamcity Bot

If you need any help, please email<EMAIL_ADDRESS>or ask anу advice on http://asf.slack.com #ignite channel.

Let's also add a test for rebalance events with security enabled.
Also, it's worth to check that client can evict or expire entries if it doesn't have right on REMOVE for this cache, and only perform PUT or GET operations.
RebalanceCacheEventSecurityContextTest test was added that tests EVT_CACHE_REBALANCE_OBJECT_LOADED, EVT_CACHE_REBALANCE_OBJECT_UNLOADED events in case of node joining and leaving.
ThinClientPermissionCheckTes#testCacheEntryExpiration and testCacheEntryEviction tests were added


Improved Rasa X shareable chat UI for mobile devices

Description of Problem:
The UI is poor for users who are testing a bot on their phone (iphone 6 in example)
The welcome text is taking a lot of space. There is a lot of padding around the UI elements. The 'send' button disappears because of some zoom-effect that happens when typing. Finally, the 'restart' button confuses new users.
chatting with keyboard closed

chatting with keyboard open

Overview of the Solution:
A more slim styling on narrow devices. Hide or explain the 'restart' button
Definition of Done:

Thanks for submitting this feature request 🚀@dakshvar22 will get back to you about it soon!✨

Hi @Krogsager. As you have pointed out, we have not optimised the share your bot feature in Rasa X for mobile devices. I like the idea though. Why is it important that your test users be able to use it on their phones?

When we share a bot URL for wider audience testing, the users are most likely to be using a mobile device, rather sitting at a desktop/laptop. And first impression is key - if they get frustrated by the UI I'm afraid that they will be less likely to try again later.

@Krogsager That is very true. What do you mean by wider audience testing?

The bot is meant as a citizen service and we don't have an existing chat channel. So to test if the bot is competent enough we will be publish it for testing to random people. (after internal testing of course)

Nice. So you publish it somewhere on the Internet and then random people test it?

We haven't decided how to target our users, but it could be a mix of random invitations by approaching people in public, a link on our website and banners/ads to invite people to test. It is for public library services.

Hey @Krogsager, the UI of the shareable chat on mobile devices has been improved in Rasa X @0.27, please feel free to create a new issue if you encounter any more issues with it.


Replace backlash when moving notebooks on windows

Replace backlash to forward slashes when moving notebooks.

Pull Request Test Coverage Report for Build 542282067

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.527%

Totals

Change from base Build 542240178:
0.0%

Covered Lines:
24936

Relevant Lines:
52481

💛  - Coveralls


Is the tags count correct?

I see @jason-vallet has added a list of stats as per #3 . However, I am worried that the number of tags may not be correct. I have my own script that returns a very different number: 3,915 annotations (not computed by the dashboard) with 867 codes (dashboard says 1,614).
There are also small differences in the numbers of comments (my script says 1,688, GraphRyders says 1,633) and users (my script says  posts (my script says 316, GraphRyders says 318) The number of posts is the same:  352.
My script for annotations:
import requests

checklistAnnotations = []
checklistCodes = []

response = requests.get('https://edgeryders.eu/opencare/annotations')
annotations = response.json()

## annotations = requests.get('https://edgeryders.eu/opencare/annotations').json()

latest = ''

for item in annotations['nodes']:
        if item ['node'] ['user_name'] == 'Amelia':
                created = item ['node']['date_standardized']
                if created > latest:
                        latest = created
                if item ['node']['annotation_id'] not in checklistAnnotations:
                        checklistAnnotations.append(item ['node']['annotation_id'])
                if item ['node']['tag_id'] not in checklistCodes:
                        checklistCodes.append(item ['node']['tag_id'])

print ('annotations: ' + str(len(checklistAnnotations)) )
print ('latest on: ' + latest)
print ('codes: ' + str(len(checklistCodes)) )

The logic is that MySQL returns a lot of duplicates, and even distinct does not always work. So I need to build these checklists of entities I already encountered, and for each entity returned by the view check that it is not already there.

I have used a simple (to not say dumb) request to get the number of tags (and users) and did not checked if they were used, so 1414 is actually the total number of tags existing within the db (as imported from ER), not just the ones used. I will correct this shortly.
I can explain the difference in the number of comments as some appears to not have existing parent (post or comment) when imported. Those elements are thus ignored to avoid discrepancy in the database.
Do you want to have the number of annotations available with the stats?

Re tags: OK, that explains it.
Re number of comments: can you make an example (need the number of comment id)?
Re annotations: yes please.

The comments all seem to be pretty old (~5years from what I can tell) so I am guessing their parents are not considered as elements of the Opencare project.
 So:

The sub-comments of these comments are legitimate. We reused some old (but relevant) content in order to seed the conversation.
They do have their own comment_ids and post_ids, but they also have parent_comment_ids that do not correspond to anything in the database.
This happened when we migrated the first Edgeryders website (Drupal 6) onto the present one (Drupal 7), in spring 2013. It does not happen anywhere else in the db: it's a one-off.
It COULD happen again in the future. Under Edgeryders TOCs, each user owns their content.  Drupal has a solution: it displays my comment (previously a comment to your comment) as a comment to the post that originated the thread. In terms of the social interaction network, the edge is redirected: used to be from me to you, but now it's from me to the author of the post.
Still, I think these comments should be counted. They have annotations, so they induce edges in the co-occurrences graph, etc.
They are 50 out of the 53 missing. The remaining 3 can be explained away with the time-delay between your harvesting into the graph db and the Drupal db I am looking into. Good!


Is it possible to use this for translatable models?

What's the issue you're running into?
I was wondering if it would be possible to use this plugin for translatable models. With something like
https://github.com/spatie/laravel-translatable or https://github.com/Astrotomic/laravel-translatable .
I know this is maybe out of scope of the plugin but was wondering if anyone has tried it before?
Thanks in advance!
Steps to reproduce
Fresh install of Statamic with this package and some translatable models.
Environment
Statamic 3.3.0-beta.2 Pro
Laravel 9.1.0
PHP 8.1.3
doublethreedigital/runway 2.3.0
statamic/eloquent-driver 0.2.0

Hey! Thanks for opening an issue.
Unfortunately, I don't know of anyone who's used that package alongside Runway. Maybe give it a go and see if it'll work?
As this is outside of the scope of this addon, I'm going to close this issue. Feel free to continue the discussion though.


hCaptcha broke pypi-cleanup automation

What's the problem this feature will solve?
I'm the maintainer of the https://github.com/arcivanov/pypi-cleanup project that is used to clean out project releases automatically from CLI using regex patterns.
A user just reported the added CAPTCHA breaking the functionality: https://github.com/arcivanov/pypi-cleanup/issues/27
Describe the solution you'd like
The lack of API providing for project maintenance capability (e.g. delete/yank releases) for the PyPI is a real bummer. By introducing hCaptcha you've basically killed the last hope for automating these maintenance procedures (hundreds of .dev releases can be generated by the CI for a project).
Please either provide an option for automation tools to function without hCaptcha or provide the maintenance API that allows such functionality to exist natively.

I encourage all folks with a 👍 on this to also check out #13409 and make sure that your use cases are reflected on that issue.

Thank you!


Webctrl - Blank/non-functioning control?

I'm using mIRC 7.75 and dcxdll-3.1-git469 on Windows 11 Pro (22H2, OS Build 22621.2428 with Experience Pack 1000.22674.1000.0)
I've been trying to use the web control to display a custom page, or any page really, and it's just blank.  Nothing renders even if I just set the url to https://google.com.  On top of that, trying to access the status text or any property seems to crash mIRC when done, but the regular commands don't seem to crash it(seem, as in I only tested -m).

Additionally, here is the simple code I used to try the webctrl control:
dialog WebControlTest {
  title "Web Control Test"
  size -1 -1 510 110
  option dbu close
}
alias webControlTestopen {
  clear
  if ($dialog(webcontroltest) == $null) {
    dialog -m webcontroltest WebControlTest
  }
  else {
    dialog -x webcontroltest
    dialog -m webcontroltest WebControlTest
  }
}
alias webctrltest.events {
  ; Nothing to do here
}
on *:DIALOG:webcontroltest:init:0:{
  dcx Mark $dname webctrltest.events

  xdialog -b $dname +tzy
  xdialog -T $dname +sp
  dcxml -d $dname web_test $qt($mircdirscripts\interface.xml)

  xdid -m $dname page +hwbf +b http://www.google.com
}

<dcxml>
    <dialogs>
        <dialog name="web_test" caption="Web Control Test" w="300" h="300" margin="5 5 5 5">
            <control type="webctrl" id="page" />
        </dialog>
    </dialogs>
</dcxml>

I also attempted to add the control manually with explicit height and width(values were 400 for both).  This didn't work either.
Browsers set as default that I tested:

Brave v1.60.118
Firefox v120.0 (64-bit)
Chrome v119.0.6045.160 (Official Build) (64-bit)
Edge v119.0.2151.72 (Official build) (64-bit)

I can't install IE 11 as it is discontinued at this point, but I tried the included registry keys never the less, with the same results as above.

Try to run CMD.exe as Administrator and: reg add "hkey_current_user\software\microsoft\internet explorer\main\featurecontrol\feature_browser_emulation" /d 11001 /f /t reg_dword /v mIRC.exe
Restart mIRC.exe. You can make yourself a .reg file and run it after installing windows.

I already said that I tried this.  But to be clear, I used regedit directly.  Added the dword of the correct value, quit regedit, and restarted mIRC.  Same result as above.  My uneducated opinion(I'm used to languages other than C), is that this is because I don't have Internet Explorer installed on my system, because like I said, the program is discontinued and I can't install it.  I'll update my post at least with the specific OS I'm running, since I apparently forgot to do that.

I don't have win11 so no if that matters.
The code you gave is missing the after init update of the cla, when i add that everything works fine.
dialog WebControlTest {
  title "Web Control Test"
  size -1 -1 510 110
  option dbu close
}
alias webControlTestopen {
  clear
  if ($dialog(webcontroltest) == $null) {
    dialog -m webcontroltest WebControlTest
  }
  else {
    dialog -x webcontroltest
    dialog -m webcontroltest WebControlTest
  }
}
alias webctrltest.events {
  ; Nothing to do here
}
alias -l _postinit {
  xdialog -l $1 update
  xdialog -j $1
}
on *:DIALOG:webcontroltest:init:0:{
  dcx Mark $dname webctrltest.events

  xdialog -b $dname +tzy
  xdialog -T $dname +sp
  dcxml -d $dname web_test $qt($mircdirinterface.xml)

  xdid -m $dname page +hwbf +b http://www.google.com

  .timer 1 0 _postinit $dname
}

Try the latest dll & web2ctrl, this should work fine on win7+

I can confirm the latest dll works in regards to the web2ctrl.
However, the performance of the dialog in general is significantly slower between versions 3.1-git952 and 3.1-git469, at least where a complex CLA is in use(for example, the minimal CLA I used to test the web is fast, but my primary use case results in it being slow.  Still investigating if it is something I can fix on my end).  I'll open a separate issue if it makes tracking things easier.


Need support for dynamic VHDs

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here:
curl
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here:
azure-cli (2.0.1)
acs (2.0.1)
appservice (0.1.1b6)
batch (0.1.1b5)
cloud (2.0.0)
component (2.0.0)
configure (2.0.1)
container (0.1.1b4)
core (2.0.1)
documentdb (0.1.1b2)
feedback (2.0.0)
find (0.0.1b1)
iot (0.1.1b3)
keyvault (0.1.1b6)
network (2.0.1)
nspkg (2.0.0)
profile (2.0.1)
redis (0.1.1b3)
resource (2.0.1)
role (2.0.0)
sql (0.1.1b6)
storage (2.0.1)
vm (2.0.1)
Python (Linux) 2.7.5 (default, Aug  2 2016, 04:20:16)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-4)]
OS Version: What OS and version are you using?
Answer here:
Red Hat Enterprise Linux Workstation release 7.3 (Maipo)
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here:
bash

Description
Would like to upload a 2 GB dynamic VHD and have it be converted to fixed, instead of  having to manually convert it to fixed first, which makes this particular VHD go from 2 GB dynamic to 32 GB fixed.
Error:
At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details. {
  "status": "Failed",
  "error": {
    "code": "ResourceDeploymentFailure",
    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
    "details": [
      {
        "code": "InvalidVhd",
        "message": "Disk 'osdisk_aIETG7Tyvv' with blob https://azrhelcli2stact.blob.core.windows.net/vhds/osdisk_aIETG7Tyvv.vhd is of Dynamic VHD type. Please retry with fixed VHD type."
      }
    ]
  }

Investigating options for supporting this

This feature will be nice! There is any new about this? Thanks!

Just bumping this since it would reduce our dependency on azure-vhd-utils if this was built into the CLI.

Cleaning up old issues from 2016 - 2018. Please let us know if this issue is still a concern.

@dctucker has this been resolved for you? I don't work in Azure anymore, but I remember this was a PITA. Looks like they just closed this with no resolution, but maybe a later version resolved this.


Add extension trait to output pretty table as JSON / yaml

In order to write better assertions on automated testing we should have the cli table output be serializable to serde. We can do this via the CSV export feature of prettytable (https://github.com/phsym/prettytable-rs#user-content-exporting) which we can serialize -> deserialize -> serialize as JSON or YAML.
This can be an extension trait on Table and we can control serialization output format with a top-level flag passed via the CLI.

Since there few types of table, some cells have non-trivial data (mostly strings), the most generic JSON format would be an array of arrays of strings and can be done with short code:
let v = serde_json::to_string(
    &table
        .row_iter()
        .map(|r| r.iter().map(|c| c.get_content()).collect::<Vec<_>>())
        .collect::<Vec<_>>(),
)
.unwrap();
println!("{}", &v);

For example:
[vagrant@adm ~]$ iml filesystem list
+------+-----------+------------------+---------+---------+------+------+
| Name | State     | Space            | Inodes  | Clients | MDTs | OSTs |
+------+-----------+------------------+---------+---------+------+------+
| fs   | available | 333 MiB / 46 GiB | 3K / 3M | 1       | 2    | 10   |
+------+-----------+------------------+---------+---------+------+------+
| fs2  | available | 332 MiB / 46 GiB | 3K / 3M | 1       | 1    | 10   |
+------+-----------+------------------+---------+---------+------+------+
[["Name","State","Space","Inodes","Clients","MDTs","OSTs"],["fs","available","333 MiB / 46 GiB","3K / 3M","1","2","10"],["fs2","available","332 MiB / 46 GiB","3K / 3M","1","1","10"]]

[vagrant@adm ~]$ iml filesystem show fs
+-------------------+---------------------------------------+
| Name              | fs                                    |
+-------------------+---------------------------------------+
| Space             | 333 MiB / 46 GiB                      |
+-------------------+---------------------------------------+
| Inodes            | 3K / 3M                               |
+-------------------+---------------------------------------+
| State             | available                             |
+-------------------+---------------------------------------+
| Management Server | mds1.local                            |
+-------------------+---------------------------------------+
| MDTs              | fs-MDT0000                            |
|                   | fs-MDT0001                            |
+-------------------+---------------------------------------+
| OSTs              | fs-OST0004                            |
|                   | fs-OST0000                            |
|                   | fs-OST0003                            |
|                   | fs-OST0001                            |
|                   | fs-OST0002                            |
|                   | fs-OST0005                            |
|                   | fs-OST0008                            |
|                   | fs-OST0007                            |
|                   | fs-OST0009                            |
|                   | fs-OST0006                            |
+-------------------+---------------------------------------+
| Clients           | 1                                     |
+-------------------+---------------------------------------+
| Mount Path        | <IP_ADDRESS>@tcp0:<IP_ADDRESS>@tcp0:/fs |
+-------------------+---------------------------------------+
[["Name","fs"],["Space","333 MiB / 46 GiB"],["Inodes","3K / 3M"],["State","available"],["Management Server","mds1.local"],["MDTs","fs-MDT0000\nfs-MDT0001"],["OSTs","fs-OST0004\nfs-OST0000\nfs-OST0003\nfs-OST0001\nfs-OST0002\nfs-OST0005\nfs-OST0008\nfs-OST0007\nfs-OST0009\nfs-OST0006"],["Clients","1"],["Mount Path","<IP_ADDRESS>@tcp0:<IP_ADDRESS>@tcp0:/fs"]]


Authorizer: combo roles issues

Developer + Operations role: If the user is a developer role first and then operations role was added, The menu icons next to the applications show edit grayed out but clicking them allows for editing if the developer role didnt own or share the application

Developer + Admin role: If the user is a developer role first and then admin role was added, user administration is not enabled.

Analyst + Operations role: if a user is an analyst role first and then operations role was added, the service pool and environments menu is not enabled.

@harshach This is related to UI, assigning it to myself.

Fixed in commit: https://github.com/hortonworks/streamline/commit/df6629bfeac7a3b82ab6947bfd83062c647c1810

verified with build 400 that these are resolved


Manual Marking views should be abstracted from specific class

The Manual Marking feature should be properly abstracted from the class views themselves.
Currently the views inject buttons, implement, and enable the feature.
The feature should be abstracted properly so that the Class implementations can extend it properly.

Fixed in the most recent refacotring


error: inlining failed in call to always_inline 'vfmaq_f32'

when I built the library with "Xilinx ARM v7 GNU Toolchain", I encountered some issues.
Following is the building log:
CMSIS-DSP_Library_Debug.build.ui.log
Can anyone help me to solve this issue, thanks.

Hi, I had the same issue with cortex-a9,could you please share the solution?


MODEL_NAME is giving such kind of error.

NOTE : I am using this code in GTA san andreas
Error in test_model.py

WARNING:tensorflow:From C:\python3\lib\site-packages\tflearn\initializations.py:119: UniformUnitScaling.init (from tensorflow.python.ops.init_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.initializers.variance_scaling instead with distribution=uniform to get equivalent behavior.
WARNING:tensorflow:From C:\python3\lib\site-packages\tflearn\objectives.py:66: calling reduce_sum (from tensorflow.python.ops.math_ops) with keep_dims is deprecated and will be removed in a future version.
Instructions for updating:
keep_dims is deprecated, use keepdims instead
Traceback (most recent call last):
File "D:\Projects\Artificial Intelligance\GTASDC\test_model.py", line 48, in
model.load(MODEL_NAME)
File "C:\python3\lib\site-packages\tflearn\models\dnn.py", line 308, in load
self.trainer.restore(model_file, weights_only, **optargs)
File "C:\python3\lib\site-packages\tflearn\helpers\trainer.py", line 490, in restore
self.restorer.restore(self.session, model_file)
File "C:\python3\lib\site-packages\tensorflow\python\training\saver.py", line 1538, in restore
+ compat.as_text(save_path))
ValueError: The passed save_path is not a valid checkpoint: D:\Projects\Artificial Intelligance\GTASDC\pygta5-car-fast-0.001-alexnetv2-10-epochs-300K-data.model

Same , i have a problem for using a pre trained model .. (The passed save_path is not a valid checkpoint+project location )


Expose full extra-files support, or at least GenericJson updater

TL;DR
The currently available generic updater for extra-files applies to many cases using the marker regexps.
However, applying it to JSON is quite awkward, and even more so when the JSON in question does not allow arbitrary extra properties beyond the expected schema. In some cases, such as the one I have at hand, it can be practically impossible.
Exposing the entire release-please extra files functionality, or at least the GenericJson updater would be good to have.
Detailed design
Backwards compatibility with the current extra-files content syntax might be problematic. But I suppose some kind of content sniffing would work, although it wouldn't be pretty -- the extra-files content could be parsed as JSON if it begins with ^\s*[, and the parsed payload passed onwards to support the full release-please extra files payload, including the generic JSON (and XML) updaters. There is a precedent for passing JSON content as string in changelog-types.
Additional information
No response

Indeed interested in that, and thanks for the info, will try it out sometime.
However, if the manifest driven way is highly recommended, I suggest addressing the following issues in README.md:

There's no mention that manifest driven is recommended, it's just documented as an alternative with easier bootstrapping.
There's no mention that manifest driven provides access to most (all) release-please features, the other way does not.
command is documented as "... either github-release, or release-pr, manifest, manifest-pr (defaults to running both)"; but what does "both" here mean -- which both of the four listed?

Also, a complete example of something using release-please-action with the manifest stuff would be most welcome.

Unfortunately, the manifest approach doesn't seem to work for me.
My case: I have a lot of Node repos that use a single shared workflow for ReleasePlease:
name: Release (Shared)
on:
  workflow_call:
jobs:
  manage-release:
    runs-on: ubuntu-latest
    steps:
      - name: Create/Update Release PR
        uses<EMAIL_ADDRESS>        id: release-pr
        with:
          release-type: node
          include-v-in-tag: false
          extra-files: |
            README.md
            version.js
            src/version.js
            config/version.js

And then in my projects I just use it like this:
name: Release
on:
  push:
    branches: main
jobs:
  default:
    uses: <public-github-url>/.github/workflows/default-release.yml

I came with the setup above so that all projects that use ReleasePlease use the same settings, which include extra-files. This been working really great so far, but in the current state, I'm unable to easily parse JSON files with the limited extra-files capability from this action.
👉 Creating manifest files for each repo would be highly counter-productive, as I'm aiming to simplify and reuse configuration across multiple repos, so the less files the better.
It would make more sense if extra-files wasn't a multiline string, but a real YAML array like:
extra-files:
- README.md
- version.js
- src/version.js
- config/version.js
- ...

which would then allow an object to be part of the array:
extra-files:
- README.md
- version.js
- src/version.js
- config/version.js
- type: json
  path: path/to/file.json
  jsonpath: "$.json.path.to.field"
- type: xml
  path: "path/to/file.xml"
  xpath: "//xpath/to/field"

Then the parser used by manifest files could be reused by this action as well. Hope it all makes sense!


Fluent condition predicate API

Replaces the predicate lambdas with an actual class.

Adds fluent API for predicate construction
Adds [de]serialization for predicates
Adds accessors to write predicates agains metrics & profiles

Can we have a test for using UDF in Predicate?

There are a few. See the tests with is_()

I'm running the Condition Validators example from mainline with the updated changes to test for backcompatibility.

Should be fixed now :)

Metric Constraints' conditons is a different concept than Condition Count Metrics' Condition: The first one is actually a Relation if I'm understanding correctly.

I think the MetricConstraint::condition may be closer to Predicate.

This is very confusing terminology. Do we want to do something about it? E.g. deprecating Metric Constraints condition in favor of a relation parameter?

"Condition," "relation," and "predicate" are all a bit muddled unfortunately. I'm not sure we can clean it up in a backward compatible way, but it's worth some thought :)


Release/2.9.0

Hey @chuwy - are you familiar with the release process for getting the JS Tracker rc into GTM? Is this something you can work with @mhadam on?


How to validate/decode a QR code with recovery or vaccination?

How to use DGC's service to validate/decode a QR code containing recovery or vaccination?

I came across https://www.npmjs.com/package/covid-certificate-parser with which we will be able to decode/parse a QR code with recovery/vaccination information offline.
What I am unable to understand is, how can I make use of DGC API/Service to validate/decode a QR code and check the authenticity of the QR code.
Is it possible? Does DGC provide some public APIs where a private company can connect to validate the authenticity of the QR code?

The DCC Gateway is not available directly to third parties, it only interacts with national backends. It's the national backends that provide the public keys needed for verification to the applications.
See https://github.com/eu-digital-green-certificates/dgc-participating-countries/issues/10 for a discussion on how to access the national backends


Why Facebook required?

If WorldScope has its own servers, why does it use Facebook login? I'm worried about using Facebook to log into any service if it may (even in principle) mean that the service gets any access to my Facebook account.
Anyway, really interesting project! Is there some other place to discuss and ask questions? For instance, have you considered enabling gitter chat?

Thank jluttine for your interests!
We were trying to make an open source clone of Periscope, which is integrated with Twitter; so we thought of using Facebook as an similar alternative that could support similar features such as sharing live streams, adding friends using Facebook friends list etc.
Login independent of Facebook should have been supported too. However we are doing this under the constraint of a semester university project and decided to implement higher priority requirements first i.e. social media integration.
Since this project has been concluded (for our university module), I suppose most existing developers will likely be inactive. Feel free to fork this repository if you plan to build any streaming service on top of this, or ask any question on this issue thread.

Ok, thanks for the explanation! Sorry to hear the project has been concluded, would love to see this project flourishing. I hope some interested people will continue working on this. Anyway, thanks for your work!

You're welcome and thanks for the kind words!


Removed unnecessary extra line break on images

Fixed #17

Any chance for a test? It can be simple assert below tests. That way we don't break it accidentally in the future. Great find otherwise. :+1:


Turbo 2 UI: Can't copy and hard to scroll

Verify canary release

[X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue
turbo dev
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
<EMAIL_ADDRESS>Describe the Bug
After installing the new Turbo Repo V2 there was a moment of exiting in seeying the new UI. Followed shortly by a bit disapointment and reverting back to the old UI.
I have 2 things that would be great to have improved.
1 - Scrolling is hard and slow.
Have you ever console.log a whole api response?
Well with this new UI forget it you will never reach the top.
IF you are not at the bottom. The application will continue to print things off screen and if you want to see the latest things.
It's going to take you a good 5 to 20 seconds to get to what's being run now.
Suggestions:

Add something to be able to go straight to Latest.
Scroll bar or some keybind to scroll up faster (not sure if it's possible)

2 - Can't copy anything.
Have you ever copied some long to look on google for a possible fix.
Well I can't copy anything apart from clicking on links that VS Code recognizes.
Expected Behavior
Be able to scroll quickly and be able to copy text from the terminal.
To Reproduce
turbo dev
Additional context
I tested it on canary.
I'm running on a MAC M2 Pro V14.2.1
Terminal running in VS Code.
Running on ZSH: zsh 5.9 (arm-apple-darwin22.6.0)
Running Oh-my-zsh:
ZSH_THEME="robbyrussell"

Up! Its a great V0 but not the best UX yet
My struggles are the same, so duplicating some ideas I support and adding new ones:

Scrollbar or go to latest. Also enhance scroll performance somehow.
Being able to copy, at least when interacting after entering with Enter
Enable terminal ctrl F search
Resize on window resize

Also had some issues debugging an error that was happening in a different task.
Used to having all the errors together I totally missed it for hours!
Having some kind of UX that points to tasks that have thrown an error, like coloring the name in red, or having some kind of notification would be great.
Ex: Youre running a nextjs app, and a server, the server throws an error and is not well catched in your nextjs app so you dont see the error as it is in the context of the server task

When you say "can't copy", are you meaning the same as https://github.com/vercel/turbo/issues/8306 or are you meaning "can't select at all"?

Yes that is what I mean

When you say "can't copy", are you meaning the same as #8306 or are you meaning "can't select at all"?

When you say "can't copy", are you meaning the same as #8306 or are you meaning "can't select at all"?

Kinda, It can't select at all.
I can't select not even to get dirty output.

Scrollbar or go to latest. Also enhance scroll performance somehow.

A scrollbar can solver the problem with going up or down.
a "go to latest" solves the problem of going down. In my opinon it would also need something extra to go up faster.

When you say "can't copy", are you meaning the same as #8306 or are you meaning "can't select at all"?

I can't select at all. Not even to get dirty output.

Same for me. In vscode and terminal is powershell 😅

Same here! Cannot select any text.

Yep, can't select anything at all from my VS Code terminal. This completely destroys UX because you cannot copy errors etc...

I reverted back to 1.0 because of the scroll issue. It does not behave like a normal terminal window when scrolling.

Setting env var TURBO_UI=false may help too until the new UI gets improved.

There is a config option in the turbo.json file to toggle back to the old output: https://turbo.build/repo/docs/reference/configuration#ui

Although this new UI is a great idea, it seems half baked.
Currently, if we can't scroll, select and copy data from the output, it's a productivity killer.
Going back to the old UI but can't wait to have a fully working version !
(it's awesome that turbo is open source but it's a real bummer that it doesn't rely more on the community to get feedback before launching and releasing new features)

@leonard-henriquez This feature was the first to go through the official RFC process: https://github.com/vercel/turbo/discussions/7802
Bugs are bugs and we are working hard at getting fixes.

I truly appreciate all the open-source work that has been put into Turbo.
It’s great that you implemented an RFC process! 💯
But wasn’t scrolling literally the very first feedback?
I just think it would have been worth waiting for a more stable version before officially releasing v2 and encouraging people to move to the new version.
Anyways, thank you very much for working on it!

The console ui is not very useful. It uses a lot of ressources, hangs, does not respond,...
When you launch multiple tasks the resource usage is out of control.

@mxn2020 Can you open an issue with a reproduction. This seems like a very different issue from the original one reported

The console ui is not very useful. It uses a lot of resources, hangs, does not respond,... When you launch multiple tasks the resource usage is out of control.

Same for me since i've updated turbo to v2 it consumes way more resources and my poor laptop gets too hot. Please add me in the issue you create.
Meanwhile, coming back to the main thread, is there an ETA for being able to copy the console contents? Is in the roadmap? This is the main issue we face with this new version and makes debugging really hard in several scenarios. And indeed the scroll speed is the second most painful regression :S

Btw I know its late for this kind of feedback, but,  why not just running N terminal sessions instead of a single one with this complicated feature? Just opening N terminals in the right order would do.  Since I've updated to turbo 2 thats what Im actually doing while these features are not there. I go one by one to the specific folders and run the dev commands. This way I have the 3-4 tasks running

I feel like building this full single multi-terminal from scratch could be a bit overkill righr?

Hey, folks, updating here:
We've disabled the terminal UI in 2.0.6 as the default until we can sort out this issue specifically. We're estimating around a week to get it fixed, and it's clear this isn't the experience we were looking for.
We're still focused on getting the fix for this and appreciate the kind feedback on this. We'll be back.
As a reminder, options to toggle the TUI on and off at your convenience:

The TURBO_UI=1 and TURBO_UI=0, respectively
Configuration in turbo.json as "ui": "tui" | "stream"

for the scrolling, this terminal ui is pretty decent for scrollbar handling inspiration
https://github.com/jesseduffield/lazygit

In the interest of ensuring we're keeping issues focused on one thing at a time, I've created an issue to focus on scrolling here: https://github.com/vercel/turbo/issues/8643
Those of us on the core team will be focusing on copying terminal outputs on this issue. For feedback on scrolling, please visit #8643.
We appreciate those of you contributing feedback on this Issue and appreciate you keeping up with our housekeeping. 🙏

This isn't entirely the same, but it's the same root cause—the border, which also breaks links. When in, i.e., vscode, you can ⌘-click links from eslint, etc, but this wraps them and breaks longer links.

@lishaduck You're correct that that wouldn't be in scope for this issue. If you'd like to report it in a new one, that would be great.

Fixed in #8713 and released in 2.0.10! We appreciate everyone's patience on this as we got this figured out.

how ca we disable this ?

@duard, you can control your UI preference using the ui config or the --ui flag (sorry for lack of link, looks like my redeploy of the docs didn't go through on Friday). 😄
@shawnmclean, we're tracking improving scrolling here if you'd like better visibility.

I agree with @lveillard, reimplementing tmux is the wrong direction. The DX will always be subpar compared to what the user is used to from their actual terminal.
Instead the user should just open N terminal sessions so they can get the full features of whatever environment they run their terminal sessions in (be it VSCode, tmux, Zellij, Zed, just their native terminal app, etc.) and the Turborepo daemon should deduplicate task runs across the multiple sessions behind the scenes.


HCA - Setup two-legged connectivity

Setup two-legged authentication and connectivity with HCA
cc: @jimduff-usds

On 1/20/22, HCA noted they are not able to make the supplied token work, and are receiving a 401 error:
Missing client_assertion parameter


removed api key and set write-gcm to true

This partially fixes #15. Since I am not using EC2, the support for JSON credentials upload is not present (It could be useful for GCE in case the Monitoring API is disabled on a previously created instance). There is also no check for authorization as discussed in #16.

Do you know when the PR submitted by bdesbiolles will be reviewed?

@poiuytrez  Unless somebody else steps up, I'll review these pull requests. Sorry, I can't make any promises about how quickly I'll be able to do that.
@bdesbiolles Thank you for the pull requests!

@rimey Great ! It's not urgent but I just wanted to make sure that someone was on it. Thank you !


Update multiimagechooser_strings_de.xml

Modified german translation

Thanks for the translations! Could you resolve the conflicts on this so we can merge it in? I possibly should have merged it in before #144, but didn't think to.


(WIP) Bootstrapable client

The pull request aim to make the Leshan Client bootstrapable.
The first step was to get the registration information from Lwm2m security/servers objects.
(This is a work in progress, do not merge it :p)

There is still some limitation in this version, but I think we are near to be able to integrate this in master. (after some review)
Here is a non exhaustive list of knowing issues :

we support only 1 device mangement server
we support only PSK (RPK and X509 need some modification in scandium to be implemented)
I think we're not really clean about threadsafeness :)
bootstrap sequence is not safe (we delete the bootstrap server if this is asked)
Ugly update strategy  (lifetime -1)
manage a client stop pending bootstrap session
we accept request of unknown server

:+1: for merging


Transaction output duplicated by 'fungible transfer'

I am using version 0.2.1 of RGB node to run a few basic tests to try and familiarize myself with the work that you guys are doing.
I was using the demo in /doc/demo-0.1 as a guide, and, after issuing the fungible transfer command, I noticed that the returned witness PSBT had what seemed to be a duplicate output: instead of two outputs paying 3.99789343 and 0.00030000 bitcoins respectively (as in the original PSBT passed to the fungible transfer command), it had two outputs paying the exact same amount of 3.99789343 bitcoins.
Here is the fungible transfer command that was issued:
rgb-cli fungible transfer 'rgb20:utxob1lr9rp8ygrvmq420yra6tsk6jyjkvvn5yry72dnz0wkvxl0mqe8vqu0u09n?asset=rgb1hq63xvdccglhn4mrqjvzx9gwgxfa35allc36dcz2zxcnxt75w3wqdqa6qd&amount=55' /var/lib/rgb/transf_tx.psbt /var/lib/rgb/consignment.rgb /var/lib/rgb/witness.psbt -i 536a2a6694490d1586a6bcf146e9a27a57b2665ee61fb18f9d7564f791361af5:0 -a 4945@215176c262d906f9e30c14692bdf4a9f284f6ed02ca51bca4f07592eb6301870:0

This is the contents of the transfer_tx.psbt file (base64 encoded):
cHNidP8BAHECAAAAAfUaNpH3ZHWdj7Ef5l5msld6oulG8bymhhUNSZRmKmpTAQAAAAD/////Ah9N1BcAAAAAFgAU/tnotNekXTer0RjOARcsopdnE+swdQAAAAAAABYAFHOHhjD4hd0I9Ssd9xDfvjANyfQkAAAAAAABAJACAAAAAXAYMLYuWQdPyhulLNBuTyifSt8raRQM4/kG2WLCdlEhAgAAAAD/////A0CcAAAAAAAAFgAUUBmwyRAdK+nlygxqsNdOJivGoO7cwtQXAAAAABYAFADzHLR73G3PsTxpYLOwxMwmU63mQJwAAAAAAAAWABTcp443bP2MZmFJryoi+9ST++VdXQAAAAABAR/cwtQXAAAAABYAFADzHLR73G3PsTxpYLOwxMwmU63mIgYDi4os0MxH+bn7DnOh11YLmuZYagbqbYDb9Vdt0tllgiMQpYtJpgAAAIABAACABQAAgAAiAgP6CaeE++8A2PeKxvCFrmadMjRR2zlNoIIOkjzeIYzaUxCli0mmAAAAgAEAAIALAACAACICAqnK9tKxYr3mo8BsXa8X7vvZkoShJuZUoWVEOLgmEUPuEKWLSaYAAACAAAAAgAgAAIAA

And here is its decoded (bitcoin-cli decodepsbt) contents:
{
  "tx": {
    "txid": "4b4d51df30dbfb7e70cd7de85818b4f5ff8194cf0aff63db564d78f514acc1a3",
    "hash": "4b4d51df30dbfb7e70cd7de85818b4f5ff8194cf0aff63db564d78f514acc1a3",
    "version": 2,
    "size": 113,
    "vsize": 113,
    "weight": 452,
    "locktime": 0,
    "vin": [
      {
        "txid": "536a2a6694490d1586a6bcf146e9a27a57b2665ee61fb18f9d7564f791361af5",
        "vout": 1,
        "scriptSig": {
          "asm": "",
          "hex": ""
        },
        "sequence":<PHONE_NUMBER>
      }
    ],
    "vout": [
      {
        "value": 3.99789343,
        "n": 0,
        "scriptPubKey": {
          "asm": "0 fed9e8b4d7a45d37abd118ce01172ca2976713eb",
          "hex": "0014fed9e8b4d7a45d37abd118ce01172ca2976713eb",
          "reqSigs": 1,
          "type": "witness_v0_keyhash",
          "addresses": [
            "tb1qlmv73dxh53wn0273rr8qz9ev52tkwylteuhdl5"
          ]
        }
      },
      {
        "value": 0.00030000,
        "n": 1,
        "scriptPubKey": {
          "asm": "0 73878630f885dd08f52b1df710dfbe300dc9f424",
          "hex": "001473878630f885dd08f52b1df710dfbe300dc9f424",
          "reqSigs": 1,
          "type": "witness_v0_keyhash",
          "addresses": [
            "tb1qwwrcvv8cshws3aftrhm3pha7xqxunapyzdh7jf"
          ]
        }
      }
    ]
  },
  "unknown": {
  },
  "inputs": [
    {
      "witness_utxo": {
        "amount": 3.99819484,
        "scriptPubKey": {
          "asm": "0 00f31cb47bdc6dcfb13c6960b3b0c4cc2653ade6",
          "hex": "001400f31cb47bdc6dcfb13c6960b3b0c4cc2653ade6",
          "type": "witness_v0_keyhash",
          "address": "tb1qqre3edrmm3kulvfud9st8vxyesn98t0xrd9h4x"
        }
      },
      "non_witness_utxo": {
        "txid": "536a2a6694490d1586a6bcf146e9a27a57b2665ee61fb18f9d7564f791361af5",
        "hash": "536a2a6694490d1586a6bcf146e9a27a57b2665ee61fb18f9d7564f791361af5",
        "version": 2,
        "size": 144,
        "vsize": 144,
        "weight": 576,
        "locktime": 0,
        "vin": [
          {
            "txid": "215176c262d906f9e30c14692bdf4a9f284f6ed02ca51bca4f07592eb6301870",
            "vout": 2,
            "scriptSig": {
              "asm": "",
              "hex": ""
            },
            "sequence":<PHONE_NUMBER>
          }
        ],
        "vout": [
          {
            "value": 0.00040000,
            "n": 0,
            "scriptPubKey": {
              "asm": "0 5019b0c9101d2be9e5ca0c6ab0d74e262bc6a0ee",
              "hex": "00145019b0c9101d2be9e5ca0c6ab0d74e262bc6a0ee",
              "reqSigs": 1,
              "type": "witness_v0_keyhash",
              "addresses": [
                "tb1q2qvmpjgsr547new2p34tp46wyc4udg8wugtpq5"
              ]
            }
          },
          {
            "value": 3.99819484,
            "n": 1,
            "scriptPubKey": {
              "asm": "0 00f31cb47bdc6dcfb13c6960b3b0c4cc2653ade6",
              "hex": "001400f31cb47bdc6dcfb13c6960b3b0c4cc2653ade6",
              "reqSigs": 1,
              "type": "witness_v0_keyhash",
              "addresses": [
                "tb1qqre3edrmm3kulvfud9st8vxyesn98t0xrd9h4x"
              ]
            }
          },
          {
            "value": 0.00040000,
            "n": 2,
            "scriptPubKey": {
              "asm": "0 dca78e376cfd8c666149af2a22fbd493fbe55d5d",
              "hex": "0014dca78e376cfd8c666149af2a22fbd493fbe55d5d",
              "reqSigs": 1,
              "type": "witness_v0_keyhash",
              "addresses": [
                "tb1qmjncudmvlkxxvc2f4u4z9775j0a72h2as5q6pz"
              ]
            }
          }
        ]
      },
      "bip32_derivs": [
        {
          "pubkey": "038b8a2cd0cc47f9b9fb0e73a1d7560b9ae6586a06ea6d80dbf5576dd2d9658223",
          "master_fingerprint": "a58b49a6",
          "path": "m/0'/1'/5'"
        }
      ]
    }
  ],
  "outputs": [
    {
      "bip32_derivs": [
        {
          "pubkey": "03fa09a784fbef00d8f78ac6f085ae669d323451db394da0820e923cde218cda53",
          "master_fingerprint": "a58b49a6",
          "path": "m/0'/1'/11'"
        }
      ]
    },
    {
      "bip32_derivs": [
        {
          "pubkey": "02a9caf6d2b162bde6a3c06c5daf17eefbd99284a126e654a1654438b8261143ee",
          "master_fingerprint": "a58b49a6",
          "path": "m/0'/0'/8'"
        }
      ]
    }
  ],
  "fee": 0.00000141
}

This is the contents of the resulting witness PSBT (base64 encoded):
cHNidP8BAHECAAAAAfUaNpH3ZHWdj7Ef5l5msld6oulG8bymhhUNSZRmKmpTAQAAAAD/////Ah9N1BcAAAAAFgAU/tnotNekXTer0RjOARcsopdnE+sfTdQXAAAAABYAFMZQDKWEyV7m2owN9qS0ENlwIVRLAAAAAAABAJACAAAAAXAYMLYuWQdPyhulLNBuTyifSt8raRQM4/kG2WLCdlEhAgAAAAD/////A0CcAAAAAAAAFgAUUBmwyRAdK+nlygxqsNdOJivGoO7cwtQXAAAAABYAFADzHLR73G3PsTxpYLOwxMwmU63mQJwAAAAAAAAWABTcp443bP2MZmFJryoi+9ST++VdXQAAAAABAR/cwtQXAAAAABYAFADzHLR73G3PsTxpYLOwxMwmU63mIgYDi4os0MxH+bn7DnOh11YLmuZYagbqbYDb9Vdt0tllgiMQpYtJpgAAAIABAACABQAAgAAiAgP6CaeE++8A2PeKxvCFrmadMjRR2zlNoIIOkjzeIYzaUxCli0mmAAAAgAEAAIALAACABv4DUkdCASED+gmnhPvvANj3isbwha5mnTI0Uds5TaCCDpI83iGM2lMAIgICqcr20rFiveajwGxdrxfu+9mShKEm5lShZUQ4uCYRQ+4QpYtJpgAAAIAAAACACAAAgAb+A1JHQgEhAqnK9tKxYr3mo8BsXa8X7vvZkoShJuZUoWVEOLgmEUPuBv4DUkdCAiDtMkT0uhzj8SwB+ee37chzV1aPiQ5/Idg0FOBYGrRidwA=

And here is its decoded (bitcoin-cli decodepsbt) contents:
{
  "tx": {
    "txid": "8344a0d070bb2fadeb9fa898493fcf144cff3d9a242e33a7bb25d33c84e8fe79",
    "hash": "8344a0d070bb2fadeb9fa898493fcf144cff3d9a242e33a7bb25d33c84e8fe79",
    "version": 2,
    "size": 113,
    "vsize": 113,
    "weight": 452,
    "locktime": 0,
    "vin": [
      {
        "txid": "536a2a6694490d1586a6bcf146e9a27a57b2665ee61fb18f9d7564f791361af5",
        "vout": 1,
        "scriptSig": {
          "asm": "",
          "hex": ""
        },
        "sequence":<PHONE_NUMBER>
      }
    ],
    "vout": [
      {
        "value": 3.99789343,
        "n": 0,
        "scriptPubKey": {
          "asm": "0 fed9e8b4d7a45d37abd118ce01172ca2976713eb",
          "hex": "0014fed9e8b4d7a45d37abd118ce01172ca2976713eb",
          "reqSigs": 1,
          "type": "witness_v0_keyhash",
          "addresses": [
            "tb1qlmv73dxh53wn0273rr8qz9ev52tkwylteuhdl5"
          ]
        }
      },
      {
        "value": 3.99789343,
        "n": 1,
        "scriptPubKey": {
          "asm": "0 c6500ca584c95ee6da8c0df6a4b410d97021544b",
          "hex": "0014c6500ca584c95ee6da8c0df6a4b410d97021544b",
          "reqSigs": 1,
          "type": "witness_v0_keyhash",
          "addresses": [
            "tb1qcegqefvye90wdk5vphm2fdqsm9czz4ztee2u0t"
          ]
        }
      }
    ]
  },
  "unknown": {
  },
  "inputs": [
    {
      "witness_utxo": {
        "amount": 3.99819484,
        "scriptPubKey": {
          "asm": "0 00f31cb47bdc6dcfb13c6960b3b0c4cc2653ade6",
          "hex": "001400f31cb47bdc6dcfb13c6960b3b0c4cc2653ade6",
          "type": "witness_v0_keyhash",
          "address": "tb1qqre3edrmm3kulvfud9st8vxyesn98t0xrd9h4x"
        }
      },
      "non_witness_utxo": {
        "txid": "536a2a6694490d1586a6bcf146e9a27a57b2665ee61fb18f9d7564f791361af5",
        "hash": "536a2a6694490d1586a6bcf146e9a27a57b2665ee61fb18f9d7564f791361af5",
        "version": 2,
        "size": 144,
        "vsize": 144,
        "weight": 576,
        "locktime": 0,
        "vin": [
          {
            "txid": "215176c262d906f9e30c14692bdf4a9f284f6ed02ca51bca4f07592eb6301870",
            "vout": 2,
            "scriptSig": {
              "asm": "",
              "hex": ""
            },
            "sequence":<PHONE_NUMBER>
          }
        ],
        "vout": [
          {
            "value": 0.00040000,
            "n": 0,
            "scriptPubKey": {
              "asm": "0 5019b0c9101d2be9e5ca0c6ab0d74e262bc6a0ee",
              "hex": "00145019b0c9101d2be9e5ca0c6ab0d74e262bc6a0ee",
              "reqSigs": 1,
              "type": "witness_v0_keyhash",
              "addresses": [
                "tb1q2qvmpjgsr547new2p34tp46wyc4udg8wugtpq5"
              ]
            }
          },
          {
            "value": 3.99819484,
            "n": 1,
            "scriptPubKey": {
              "asm": "0 00f31cb47bdc6dcfb13c6960b3b0c4cc2653ade6",
              "hex": "001400f31cb47bdc6dcfb13c6960b3b0c4cc2653ade6",
              "reqSigs": 1,
              "type": "witness_v0_keyhash",
              "addresses": [
                "tb1qqre3edrmm3kulvfud9st8vxyesn98t0xrd9h4x"
              ]
            }
          },
          {
            "value": 0.00040000,
            "n": 2,
            "scriptPubKey": {
              "asm": "0 dca78e376cfd8c666149af2a22fbd493fbe55d5d",
              "hex": "0014dca78e376cfd8c666149af2a22fbd493fbe55d5d",
              "reqSigs": 1,
              "type": "witness_v0_keyhash",
              "addresses": [
                "tb1qmjncudmvlkxxvc2f4u4z9775j0a72h2as5q6pz"
              ]
            }
          }
        ]
      },
      "bip32_derivs": [
        {
          "pubkey": "038b8a2cd0cc47f9b9fb0e73a1d7560b9ae6586a06ea6d80dbf5576dd2d9658223",
          "master_fingerprint": "a58b49a6",
          "path": "m/0'/1'/5'"
        }
      ]
    }
  ],
  "outputs": [
    {
      "bip32_derivs": [
        {
          "pubkey": "03fa09a784fbef00d8f78ac6f085ae669d323451db394da0820e923cde218cda53",
          "master_fingerprint": "a58b49a6",
          "path": "m/0'/1'/11'"
        }
      ],
      "unknown": {
        "fe0352474201": "03fa09a784fbef00d8f78ac6f085ae669d323451db394da0820e923cde218cda53"
      }
    },
    {
      "bip32_derivs": [
        {
          "pubkey": "02a9caf6d2b162bde6a3c06c5daf17eefbd99284a126e654a1654438b8261143ee",
          "master_fingerprint": "a58b49a6",
          "path": "m/0'/0'/8'"
        }
      ],
      "unknown": {
        "fe0352474201": "02a9caf6d2b162bde6a3c06c5daf17eefbd99284a126e654a1654438b8261143ee",
        "fe0352474202": "ed3244f4ba1ce3f12c01f9e7b7edc87357568f890e7f21d83414e0581ab46277"
      }
    }
  ],
  "fee": -3.99759202
}

I have done some investigation, and it seems that the root of this issue lies in the rust-lnpbp crate, more specifically in the commit() associated function of the Anchor structure.
The problem, for what I could see, is that the transaction output (vout) on which the tweak should be applied is being calculated in two different places using different methods.
The first place where the vout is calculated is inside the commit() associated function of the Anchor structure  (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L139-L154).
The second place where the vout is calculated is in the vout() method of the TxContainer structure (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/bp/dbc/tx.rs#L71-L77).
There, one can notice that the transaction fee is used in the calculation of the vout. And taking the fact that, in this particular case, the protocol_factor field of the TxContainer structure is set to the vout as calculated inside the commit() associated function of the Anchor structure (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L195-L211), one can conclude that, depending on the value of the transaction fee, the two vouts will point to distinct transaction outputs. And this is exactly what happens in this specific situation.
At some point in the processing of the commit() associated function of the Anchor structure, the embed_commit() associated function of the TxCommitment structure is called (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L221-L222).
Then, in the processing of the embed_commit() associated function of the TxCommitment structure, the tweaked transaction output is updated into the transaction itself. However, the transaction output that is being replaced is indexed by the vout as calculated by the vout() method of the TxContainer structure (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/bp/dbc/tx.rs#L147), while the whole processing of the tweak was done using the vout as calculated by the commit() associated function of the Anchor structure. And this is precisely what is causing the reported issue.

I have done some investigation, and it seems that the root of this issue lies in the rust-lnpbp crate, more specifically in the commit() associated function of the Anchor structure.
The problem, for what I could see, is that the transaction output (vout) on which the tweak should be applied is being calculated in two different places using different methods.
The first place where the vout is calculated is inside the commit() associated function of the Anchor structure  (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L139-L154).
The second place where the vout is calculated is in the vout() method of the TxContainer structure (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/bp/dbc/tx.rs#L71-L77).
There, one can notice that the transaction fee is used in the calculation of the vout. And taking the fact that, in this particular case, the protocol_factor field of the TxContainer structure is set to the vout as calculated inside the commit() associated function of the Anchor structure (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L195-L211), one can conclude that, depending on the value of the transaction fee, the two vouts will point to distinct transaction outputs. And this is exactly what happens in this specific situation.
At some point in the processing of the commit() associated function of the Anchor structure, the embed_commit() associated function of the TxCommitment structure is called (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L221-L222).
Then, in the processing of the embed_commit() associated function of the TxCommitment structure, the tweaked transaction output is updated into the transaction itself. However, the transaction output that is being replaced is indexed by the vout as calculated by the vout() method of the TxContainer structure (as can be seen here: https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/bp/dbc/tx.rs#L147), while the whole processing of the tweak was done using the vout as calculated by the commit() associated function of the Anchor structure. And this is precisely what is causing the reported issue.

Thank you very much for finding this issue and such a thorough investigation on it. @rajarshimaitra can you help me looking into possible fixes on it?

Thank you very much for finding this issue and such a thorough investigation on it. @rajarshimaitra can you help me looking into possible fixes on it?

Had a look and I have a few questions.

adding fee to id in https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L139-L154

This will then make vout calculation in anchor incompatible with vout calculation in TxContainer. For each ContractId this will then calculate different vouts. I think you meant "replace" instead of "add"?

Using 0 instead of fee in https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L197

This feels bandaid-y. Instead, how about we define protocol_factor properly somewhere(enum?) and use the appropriate protocol factor everywhere? We can set it to 0 for all the cases for now and the TxContainer constructor should then use the fee and protocol_factor as intended.
I will make the PR. looking for Approach ACK.

Had a look and I have a few questions.

adding fee to id in https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L139-L154

This will then make vout calculation in anchor incompatible with vout calculation in TxContainer. For each ContractId this will then calculate different vouts. I think you meant "replace" instead of "add"?

Using 0 instead of fee in https://github.com/LNP-BP/rust-lnpbp/blob/e35da7d534250ac7c52ebfae45c8bd772400a7ab/src/rgb/stash/anchor.rs#L197

This feels bandaid-y. Instead, how about we define protocol_factor properly somewhere(enum?) and use the appropriate protocol factor everywhere? We can set it to 0 for all the cases for now and the TxContainer constructor should then use the fee and protocol_factor as intended.
I will make the PR. looking for Approach ACK.

The problem here is the fact that at the level of transaction we do not have an access to the fee information. According to LNPBP-3 fee and protocol factor are just two additive numbers, which are modulo divided number of outputs; so
a) to fix the bug now we have to make them working correctly. If you'd like to rename them into factor1 and factor2 to remove the confusion that is totally ok
b) later in v0.3 I will do a refactoring of this part of the API, but for v0.2 branch we need a fix of this kind

The problem here is the fact that at the level of transaction we do not have an access to the fee information. According to LNPBP-3 fee and protocol factor are just two additive numbers, which are modulo divided number of outputs; so
a) to fix the bug now we have to make them working correctly. If you'd like to rename them into factor1 and factor2 to remove the confusion that is totally ok
b) later in v0.3 I will do a refactoring of this part of the API, but for v0.2 branch we need a fix of this kind

Understood. Going with the quick fix for now. So fix is as below:

Replace ContractId with fee + protocol_factor. Keep protocol_factor as 0 for now, so vout = fee % nouts. This will make the two derivation compatible.

Use correct fee and protocol_factor = 0 in TxContainer construction.

Sounds good?

Understood. Going with the quick fix for now. So fix is as below:

Replace ContractId with fee + protocol_factor. Keep protocol_factor as 0 for now, so vout = fee % nouts. This will make the two derivation compatible.

Use correct fee and protocol_factor = 0 in TxContainer construction.

Sounds good?

Solved with https://github.com/rgb-org/rgb-core/pull/4


realm sdk mongodb client support

I have application running in aws lambda serverless, the cold start takes a long time to setup connection pool, so using http requests to query data may be more suitable for serverless environments, and that can be done using realm sdk mongodb client.
can papr fully support this client in addition to the original mongodb connection?

Have you followed the best practices to manage connection with AWS Lambda (https://www.mongodb.com/docs/atlas/manage-connections-aws-lambda/)?
The first point is probably the most important one!

Yes sure, The problem is happening with cold start, these practices are good for warm requests.
and I want to add another point, managing number or connections of mongodb with serverless environment is hard and can reach the limit of connections easily, so moving that to data api is safer.

Have you followed the best practices to manage connection with AWS Lambda (https://www.mongodb.com/docs/atlas/manage-connections-aws-lambda/)?
The first point is probably the most important one!


feat(snapshots): add garbage collector to cleanup leaked snapshots unknown to control-plane

bors merge

bors try

bors merge


Code generator panics when bytes::Bytes are enabled

Using the following code generation snippet (from build.rs):
protobuf_codegen_pure::run(protobuf_codegen_pure::Args {
        out_dir: &out_dir.to_string_lossy(),
        input: &slices,
        includes: &[&proto_dir.to_string_lossy()],
        customize: protobuf_codegen_pure::Customize {
            carllerche_bytes_for_bytes: Some(true),
            ..Default::default()
        },
    })
    .expect("protoc");

Cargo.toml contains under [dependencies] section:
protobuf = { version = "2.2", features = ["with-bytes"] }
This code panics with:

thread 'main' panicked at 'unexpected field type: ::bytes::Bytes', /home/build/.cargo/registry/src/github.com-1ecc6299db9ec823/protobuf-codegen-2.2.0/src/field.rs:858

Is there anything missing?

oneof with bytes was not implemented. Fixed and published v2.2.1. Thank you for the bugreport!


CyclomaticComplexity still logs on IGNORE severity

The following message is printed (in purple/info level?):
Ignore: Function "apply" is too complex (score: 21).
After a number of "ignore" warnings the resulting output is :
No issues found.
The rules specify:
        {
            "type": "CyclomaticComplexity",
            "props": {
                "thresholds": [
                    {
                        "severity": "IGNORE",
                        "complexity": 20
                    },
                    {
                        "severity": "IGNORE",
                        "complexity": 30
                    }
                ]
            }
        },

From what I understand it - IGNORE is not supposed to log at all - and only logs in the case of CyclomaticComplexity (no other tests on IGNORE log info). My guess is a simple logging related bug that doesn't respect the IGNORE severity and just ignore it entirely. Unless there is a root severity I haven't configured that handles this?

(I can get around the logging with "complexity": 99 but obviously this isn't a solution :))


Fix pointer recursion problems

Undefined auto_create=True pointers to other PropertyClasses with auto_create=True pointers have infinite recursion problems on validate.

Also, validation accounts for objects that may point to each other, but serialization does not.

Regarding the auto_create=True infinite recursion, I think that is ok. HasProperties classes should just not be designed where auto_create properties can chain together infinitely.
Perhaps it's worth introducing a new attribute, something like create_on_get, where instead of being created as a default value (as is the case with auto_create), they are only created on getattr. That would mean you could access a chain of these values (something like BookPage().next_page.next_page.next_page, where each page is created on access), but on creation/validation/serialization, these are not auto-created and therefore don't face infinite recursion problems...

The validation/serialization are tackled in #121

Improved with #121. Tackling #128 will also help.


[pmdk] Update to 1.8

Update to the latest released version 1.8.
Related issue #9883.
Remove libvmem from solution Items. Please refer to these changes.
Note: No feature needs to test.

/azp run

/azp run

Cools, thanks @NancyLi1013 :)


Enhance csv version of output

💡 Summary
Enhance the csv output to include details such as the requirement text and result values. Basically, make it a csv version of the reports.
Motivation and context
While ScubaGear does output a csv version of the output, this functionality has not been updated in some time and does not include several enhancements that have been made. For example, it does not include the requirement text (#1015) or the "Result" value.
This would allow people to access their results in a machine-readable format or port their results to Excel spreadsheets.
Implementation notes
PR #970 created a json version of the output. The easiest way to implement the csv enhancement would probably be to convert the ScubaResults.json "Results" key into a csv.
Acceptance criteria

[ ] A csv version of the output is available

The easiest way to implement the csv enhancement would probably be to convert the ScubaResults.json "Results" key into a csv.

Almost.
The easiest way to implement the csv enhancement would probably be to allow any downstream system to convert the ScubaResults.json "Results" key into a csv.
FTFY.


Dispatch error event when shaders fail to compile

In #816 we added an error event when WebGL crashes. We should also dispatch an DOM error event when we detect that a shader failed to compile.

Dupe of #921


Avatar upload UI broken when blocking Gravatar

Hi!
Version:
Zulip Server
Version 4.3

I found an issue, which might hit many privacy aware users: When I block gravatar.com (for example using uBlock Origin), then the UI for setting my avatar looks as follows:

There is no element to click on to upload my avatar, because the gravatar image never gets loaded, because the request is blocked.
When gravatar is allowed to load (unblocked) the UI looks as follows:

The ability to upload a custom avatar should not be impacted by a third party tool (gravatar) being blocked at all. There should be a button to upload ones own avatar, regardless of what happens with the request to gravatar.com.

Thanks for the report!  I agree we should fix this.  I think the problem is that the element showing your current avatar with the click handler ends up with 0 size if the image doesn't load, which presumably can also happen in situations with network issues.
We probably should just have a grey background of the right size for that avatar region.
@priyank-p FYI, since I remember you looking into a similar issue elsewhere.
@ZelphirKaltstahl do other places (like the message feed) work OK with this setting? I'd like to make sure we fix this completely.

@timabbott I have not seen any other issue so far, while blocking gravatar.com requests. No guarantees though, I have only been using it for a short while. However, if I notice anything else, I will let you know. : )


HDDS-3384. Update SpringFramework to 5.1.14.

What changes were proposed in this pull request?
Upgraded spring-jdbc due to CVE.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3384
How was this patch tested?
Ran the relevant test with success.

@avijayanhwx / @vivekratnavel for review.

We also use the same dependency in hadoop-ozone/recon/pom.xml
Can we move spring.version to the root pom file and use it for both?

Ah, sorry missed that. we do not use spring anywhere outside of recon but yes, let me do that


Hover text support

Please provide hover text information for various icons as provided for the save.
FYI, I've tested app in the mac.

Closing this issue as fixed. This PR adds toolhints for the icons #2812.


Filtering and sorting of data quality tests & suites at Data Quality page

Is your feature request related to a problem? Please describe.
The data quality module (page) at OM does not allow sorting of filtering of data quality tests, suites

Describe the solution you'd like
Solution should be to have filter to filter out tests and test suites

by status i.e. Passed, Aborted or Failed
by resolution i.e. Ack, New or Resolved
by Last Run value may be sliding time window
by table name - search through table names

Also we should have sorting using same columns
Describe alternatives you've considered
Alternate way is to scroll through all tests which is not a good experience , specially if you have so many tests or suites
Additional context
Slack Thread

Merging related issue here
Filters that will be added:

Latest Status of test case execution
Resolution state -> will need to add latest state to TestCase (similar to testCaseResult)
Timestamp
Table name (i.e. entity link)
Test type (i.e. OpenMetadata, dbt, GX, or Other)

Note: domain filtering will be tracked in a separate issue https://github.com/open-metadata/OpenMetadata/issues/15594

Filters that will be implemented:

status
Last run value
table name
type [Column, Table]
~resolution~ -> This is already available in the incident manager

Re-opening as UI changes still left


unable to find packages

I am willing to install some packages but I can't find them by searching in install. I can't even find the script package then I find it through the StackOverflow link. please sort this issue.

I am willing to install some packages but I can't find them by searching in install. I can't even find the script package then I find it through the StackOverflow link. please sort this issue.

I'm having the same issue on my Windows computer, although I didn't have the issue on my Mac computer. My Windows is a company computer and is blocked from accessing GitHub and my Mac isn't. Could this be why?

Atom presently is the best editor , Intially Atom was owned by github as a product
But when Microsoft and Bill gates bought github, they also bought Atom too or more or less since atom was open source , they left it to die and marketed vscode, Siince then the atom project has been maintained by a team of contributors out of freewill
It is very likely the packages you want to add are deprecated at the moment, but in the moment I can be of help
What package(s) do you intend to install??
What link do you have for it??
Do you still see the package last release and compatibility with the latest version of Atom (1.60.0)
God bless the community for that release
then ask some other question and i will attend to you

But when Microsoft and Bill gates bought github, they also bought Atom too or more or less since atom was open source , they left it to die and marketed vscode

He left in March 2020


Use automatic superuser creation

starting with v1.15.0, https://github.com/sissbruecker/linkding/pull/323 allows us to automatically create a superuser via env variables.
Test this and update documentation.

Hey @fspoettel - Just raised #3 to solve this 🙂 - Hopefully you can review soon! 😄


[bug] Repetitive Transcription During Silence or White Noise Periods

Repetitive Transcription During Silence or White Noise Periods
Description
Running Version 0.5.6 (20241017.030846)
Apple M3 Max MacBook Pro
14-inch, Nov 2023
Memory: 128 GB
macOS Sequoia Version 15.1 Beta (24B5077a)
The Screenpipe app is experiencing an issue where the transcription feature generates repetitive text during periods of silence or white noise. This problem affects the accuracy of meeting summaries and may be related to how the app processes audio input when no distinct speech is detected.
The repetitive text appears as:
"The world is a great place to be able to get the world to be able to get the world..." or other disjointed phrases.
This redundancy prevents the app from providing meaningful summaries and indicates a potential bug in the transcription process or AI settings.

Current Settings

Audio Transcription Model: whisper-large-turbo
OCR Model: apple native
Monitors: 1 monitor(s) selected
Audio Devices: 2 device(s) selected

MacBook Pro Microphone (input) (default)
Display 1 (output) (default)

Languages: english
Restart Interval: 0 minutes (experimental feature)

Steps to Reproduce

Open the Screenpipe app with the current settings.
Start a recording where there are expected periods of silence or white noise.
Check the transcription output in the "meeting and conversation history" section.

Expected Behavior

The transcription should accurately reflect spoken content without inserting repetitive phrases during silent or white noise periods.
Summaries should be concise and relevant to the actual meeting content.

Actual Behavior

The transcription fills with repeated phrases like "the world is a great place to be able to get the world..." during silences or white noise.
This repetition disrupts the generation of meaningful summaries.

Suggested Fixes

Investigate and adjust the audio processing algorithm, particularly for the whisper-large-turbo model, to handle silence and white noise more effectively.
Implement filters to prevent repetitive text from affecting transcription outputs.
Consider adding a silence detection feature that skips transcription during prolonged quiet periods.
Explore options to fine-tune the AI model to better distinguish between speech and non-speech audio.

Additional Notes

The issue occurs despite using the whisper-large-turbo model, which is generally considered high-quality for transcription tasks.
The problem may be exacerbated by the experimental nature of some features, such as the restart interval setting.

Attachments

Screenshot of the affected transcript (attached)
Screenshot of current Screenpipe settings (attached)

Please address this issue to improve transcription accuracy and summary reliability in meetings with varying audio conditions.

#521 related

@cyberpapiii solved


Include an EventJobDataBinder that leverages an Axon Serializer

When using a QuartEventScheduler, you need an EventJobDataBinder, and (except for the legacy-aware one), out-of-the-box there's only the DirectEventJobDataBinder which uses Java serialization. That's not a great choice for several reasons:

It forces scheduled events to implement java.io.Serializable
It's not robust against refactoring

A natural alternative would be to take the Axon Serializer. The SerializedObject coming out of that can easily be mapped to jobData.  (Kotlin) example:
@Component
class AxonSerializerEventJobDataBinder(private val serializer: Serializer) : EventJobDataBinder {
    override fun toJobData(eventMessage: Any): JobDataMap {
        val serializedEvent = serializer.serialize(eventMessage, String::class.java)
        val jobData = JobDataMap()
        jobData["data"] = serializedEvent.data
        jobData["type.name"] = serializedEvent.type.name
        jobData["type.revision"] = serializedEvent.type.revision
        return jobData
    }

    override fun fromJobData(jobData: JobDataMap): Any {
        val type = SimpleSerializedType(jobData["type.name"] as String?, jobData["type.revision"] as String?)
        val serializedEvent = SimpleSerializedObject(jobData["data"] as String?, String::class.java, type)
        return serializer.deserialize(serializedEvent)
    }
}

Suggested improvement: add something like this to the framework so users can simply configure that bean, rather than having to write this from scratch. (And, in a next Axon 4 major release, make this the default.)

I just noticed this issue has already been resolved, and was additionally documented under #749.
The PR providing the fix can be found here.
The solution is slated for 3.4, which I assume we'll be releasing soon.


JoinQuery and partitioning

I'm trying to do a JoinQuery between 1 458 000 points and 104 polygons. It works but it's very long I think. Here is what I do :
First I load points in a dataframe,
val train = sqlContext.read.format("com.databricks.spark.csv").option("header", "true").option("inferSchema", "true").load("hdfs://namenode-0-node.hdfsnoha.autoip.dcos.thisdcos.directory:9001/train.csv")

train.cache
train.count

Then I load the shape file with all polygons
val  shapefileRDD = new ShapefileRDD(sc,"hdfs://namenode-0-node.hdfsnoha.autoip.dcos.thisdcos.directory:9001/nycbb");

val spatialRDD = new PolygonRDD(shapefileRDD.getPolygonRDD, StorageLevel.MEMORY_ONLY)

I create the PointRDD from my raw data (I repartition on purpose with the default processing unit of my spark context to be sure 😄 ),
val geometryFactory=new GeometryFactory()

val rawPointRDD = train.rdd.repartition(16).map( row => {

    	val point = geometryFactory.createPoint(new Coordinate(row.getDouble(row.fieldIndex("pickup_longitude")), row.getDouble(row.fieldIndex("pickup_latitude"))))
        point
    })

val nycPointRDD = new PointRDD(rawPointRDD, StorageLevel.MEMORY_ONLY)

I do a spatial partitioning of the points and apply that partitioning to the polygons (It's what I understood in the showcase or examples),

nycPointRDD.spatialPartitioning(GridType.QUADTREE)
spatialRDD.spatialPartitioning(nycPointRDD.partitionTree)

// nycPointRDD.buildIndex(IndexType.RTREE,true)

nycPointRDD.spatialPartitionedRDD.persist(StorageLevel.MEMORY_ONLY)
spatialRDD.spatialPartitionedRDD.persist(StorageLevel.MEMORY_ONLY)`

And finally I run the join,
val joinResult = JoinQuery.SpatialJoinQuery(nycPointRDD, spatialRDD, false,true)
joinResult.count

NB : I don't index yet all the points on purpose.
My question is : when I do that, I notice that only one worker was currently active. So, from what I understood, because I asked the same spatial partitioning for my points and my polygons, I should have all the workers processing the join at the same time.
All my polygons cached take 3.2Mo in memory and all my points take 92Mo in memory.
I do something wrong I think (I'm sure !) but I can't figure out what ...

@fmarchand My two cents:

Are you sure that nycPointRDD has more than one partition?
GeoSpark doesn't impact Spark cluster setting. Please check your cluster setting. Did you successfully connect to Spark master, e.g., explicitly specify Spark master IP address?


[BUG]: When trying to stop the model the CPU job doesn't go down

How are you running AnythingLLM?
Docker (local)
What happened?
When I write something to a model and then trying to stop, it works sometimes and sometimes the CPU is still 100% even after stopping, seems that the process hangs and I need to kill the process.
Can inform that I use docker container.
I use Ryzen 7 5800h 16GB ram
Are there known steps to reproduce?
Type anything to any model like llama3 or mistral.
Let the model write and then stop in the middle and write again and stop. Sometimes the process doesn't go idle and pushing the CPU 100% even after everything is stopped.

There is no detail on what LLM provider you are using here, so hard to help debug. Most LLM providers dont even support a halt method so once they start inferencing they cannot stop - all we can do client side is disconnect from the listener and hope the provider can see CONN_CLOSED and stop.
Again, most dont support this.

Oh okay, im using ollama api. But if ollama is the problem then they should
fix i hope.
Regards
Den tis 25 juni 2024 22:33Timothy Carambat @.***> skrev:

There is no detail on what LLM provider you are using here, so hard to
help debug. Most LLM providers dont even support a halt method so once
they start inferencing they cannot stop - all we can do client side is
disconnect from the listener and hope the provider can see CONN_CLOSED
and stop.
Again, most dont support this.
—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/1760#issuecomment-2189917849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW4TPNABUZY5O5W5HYLNPXLZJHHZZAVCNFSM6AAAAABJ4QDF3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBZHEYTOOBUHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yeah :/ I agree, believe me I have had this same issue myself and I have found just killing the process and rebooting worked when it was on a runaway inference

But strange part is I tried open webui and there it works when stopping but
the performance of answer from the model is slower than anythingllm.
Den tis 25 juni 2024 22:43Timothy Carambat @.***> skrev:

Yeah :/ I agree, believe me I have had this same issue myself and I have
found just killing the process and rebooting worked when it was on a
runaway inference
—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/1760#issuecomment-2189934834,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW4TPNBDPKDRJEOKIDHYENTZJHJA7AVCNFSM6AAAAABJ4QDF3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBZHEZTIOBTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


create css class error

Challenge http://freecodecamp.com/challenges/waypoint-use-a-css-class-to-style-an-element has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
if camper not delete h2 in style, i think they can't move to the next challenge.

Thanks for pointing this out!
The code that should fail:

CatPhotoApp


Fix: possible segfault on startup if duplicate ip+CIDR in ip match list

Thanks @mirkodziadzka-avi . The location of the first memset has been corrected via #2891


DMA Mode not working

This is a great little library/driver - thx for your great work!
I'm having trouble to get the DMA mode to work. It "hangs" in the Displ_Transmit() function on line 77.
while (!Displ_SpiAvailable) {};
It looks like there there is never a transfer-complete interrupt received - though both, the global SPI1 and DMA2 TX interrupts are enabled. I'v never worked with DMA before - do I need to configure something "special" except enabling the DMA TX ?
Btw: it works in "normal" Interrupt-Mode - just not in DMA mode....

Hi cider101,
yes, it seems that DMA doesn't signal transfer-complete.
Which uC are you using?
Have you enabled SPI interrupt? ("SPIx global interrupt" enabled, on "NVIC settings", in the SPIx "Configuration" page)
That has to be enabled together with the SPIx_TX settings.
Let me know.
Bye

Thx for your quick response.
I'm using an SMT32F401 Weact Blackpill and yes,  both, SPI1_TX and SPI1 global interrupt are enabled...
As mentioned before, I haven't used DMA yet - so please forgive my ignorance. From the HAL code I understood, that the DMATransferCompleted-IRQ/Event ist routed by HAL from the DMA-IRQ-Handle to the to the SPI-IRQ-Handler which then will finally call the function HAL_SPI_TxCpltCallback() from your library - right ?

Hi Cider101
3 more questions:

can you tell me the display you are using?
can you tell me the configuration in z_displ_ILI9XXX.h?  I mean the values enabled in STEP1 to STEP6
can you also show me lines in "main.c" between  /* USER CODE END SysInit / and    / USER CODE BEGIN 2 */
thet means the initialization sequence set by CubeMX?

Thank you

Good Morning Mauro
I'm using a ILI9488 Display with an FT6236  touch controller
this is my configuration for the display in the z_displ_ILI9XXX.h
0. //#define DISPLAY_USING_TOUCHGFX

1. #define ILI9488_V1 (this display seems only to work with rgb666)

2. #define DISPL_SPI_PORT 	hspi1
    #define DISPL_SPI 		SPI1

3. #define DISPL_PRESCALER SPI_BAUDRATEPRESCALER_2     //prescaler assigned to display SPI port
   #define TOUCH_PRESCALER SPI_BAUDRATEPRESCALER_256	//prescaler assigned to touch device SPI port

4. //#define DISPLAY_SPI_POLLING_MODE
   //#define DISPLAY_SPI_INTERRUPT_MODE
    #define DISPLAY_SPI_DMA_MODE // (mixed: polling/DMA, see below)

5. //#define DISPLAY_DIMMING_MODE

6. #define BUFLEVEL 12

and that's my main.c
MX_GPIO_Init();
MX_SPI1_Init();
MX_I2C1_Init();
MX_TIM2_Init();
MX_DMA_Init();

/* USER CODE BEGIN 2 */
Displ_Init(Displ_Orientat_0);
Displ_CLS(BLUE);
//Displ_BackLight('I');  			//currently hard-wired to 3v3
/* USER CODE END 2 */

/* Infinite loop */
/* USER CODE BEGIN WHILE */
while (1)
{
  /* USER CODE END WHILE */

  /* USER CODE BEGIN 3 */
    Displ_PerfTest();
}
/* USER CODE END 3 */

thx again for your help! have a nice weekend
Marco

Hi Cider101,
can you do these tests, changing the initialization order?
test 1:
MX_GPIO_Init();
MX_I2C1_Init();
MX_TIM2_Init();
MX_DMA_Init();
MX_SPI1_Init();
test 1:
MX_GPIO_Init();
MX_DMA_Init();
MX_I2C1_Init();
MX_TIM2_Init();
MX_SPI1_Init();
and let me know what happens?

It works!! thx a lot!  Seems this is a bug/issue with the Stm32CubeIDE since that code is generated by the IDE.
btw:did you ever figure out, what the difference between board version 1.0 and 2.0 is ? Maybe a different chip or firmware version/revision of the Ili9488 ?
thx again end enjoy the weekend
best regards
Marco

Yes,
it seems (to me) that when you create a new project, CubeMX sets the right initialization order. Anytime.
But, if you start to "play" with your configuration: enabling DMA (and saving configuration), then disabling it, then changing its setup, many time... CubeMX can fall into a wrong sequence and it is not able to set it back to the right one.
You could set the initialization sequence inyo CubeMX -> Project Manager -> Advanced Settings but some sequences (including DMA) are protected (against your mistakes but not against CubeMX mistakes).
About your project: from now on, if you make any changing in configuration, CubeMX will set back the wrong order. The only way (I found) avoiding it is to create a new project
Bye


Maccy's Clipboard not working

Before Submitting Your Bug Report

[X] I have verified that there isn't already an issue reporting the same bug to prevent duplication.
[X] I have seen the FAQ.

Maccy Version (see 'About' window)
0.31.0 (30)
macOS Version
Version 15.0 Beta (24A5264n)
Maccy Settings
{
    "KeyboardShortcuts_delete" = "{\\"carbonModifiers\\":2048,\\"carbonKeyCode\\":51}";
    "KeyboardShortcuts_pin" = "{\\"carbonModifiers\\":2048,\\"carbonKeyCode\\":35}";
    "KeyboardShortcuts_popup" = "{\\"carbonModifiers\\":2048,\\"carbonKeyCode\\":9}";
    "LaunchAtLogin__hasMigrated" = 1;
    "NSWindow Frame com.sindresorhus.Preferences.FrameAutosaveName" = "449 281 542 435 0 0 1440 875 ";
    "NSWindow Frame com.sindresorhus.Settings.FrameAutosaveName" = "499 445 442 322 0 0 1440 875 ";
    SUEnableAutomaticChecks = 1;
    SUHasLaunchedBefore = 1;
    SULastCheckTime = "2024-06-15 16:52:07 +0000";
    SUUpdateGroupIdentifier = 649720175;
    avoidTakingFocus = 1;
    clearOnQuit = 1;
    clearSystemClipboard = 0;
    enabledPasteboardTypes =     (
        "public.utf8-plain-text",
        "public.tiff",
        "public.html",
        "public.png",
        "public.file-url",
        "public.rtf"
    );
    historySize = 10;
    ignoreEvents = 0;
    ignoredPasteboardTypes =     (
        "com.agilebits.onepassword",
        "net.antelle.keeweb",
        "Pasteboard generator type",
        "de.petermaurer.TransientPasteboardType",
        "com.typeit4me.clipping"
    );
    menuIcon = clipboard;
    migrations =     {
        "2020-04-25-allow-custom-ignored-types" = 1;
        "2020-06-19-use-keyboardshortcuts" = 1;
        "2020-09-01-ignore-keeweb" = 1;
        "2021-02-20-allow-to-customize-supported-types" = 1;
        "2021-06-28-add-title-to-history-item" = 1;
        "2021-10-16-remove-dynamic-pasteboard-types" = 1;
        "2022-08-01-rename-suppress-clear-alert" = 1;
        "2022-11-14-add-html-rtf-to-supported-types" = 1;
        "2023-01-22-add-regexp-search-mode" = 1;
    };
    pasteByDefault = 1;
    suppressClearAlert = 1;
}

Description
I just updated to developer version of mac OS which is 15 and suddenly maccy's option + V has stopped working.
copied_txt
option + v --> ˇ
expected --> copied_txt
Steps to Reproduce
No response

What is "Option+V" doing? There is no such shortcut available in Maccy.

What is "Option+V" doing? There is no such shortcut available in Maccy.

This shortcut doesn't open up the clipboard.

Maybe on macOS 15 this shortcut is globally reserved, I haven't updated yet.

What is "Option+V" doing? There is no such shortcut available in Maccy.

This shortcut doesn't open up the clipboard.

I have the same exact issue with this new macOS Sequoia ...and couldn't find so far the reason anywhere

Let's continue under #791


What is the true usage of settings.big_num?

Shall i understand the settings.big_num in the training part as the batchsize that controls how many samples are feed until an optimization is executed?
and why in test_GRU.py, it is set by test_settings.big_num = 262 * 9.
I'm a little confused about why it is 262*9
Thank you

Yes, the settings.big_num refers to the number of entity pairs which are fed into the network while training/testing.
However during testing, the total number of the entity pairs you want to test should be divided by the big_num with no remainder. And that's why it is set as 262*9. You can also factor the number of the entity pairs you want test and set the big_num according to the results.
But you should note that when the big_num is small, the time of forward process will be a little bit long. However if the big_num is too big, the memory may be out of usage. So, you should try and find a balance.

Thanks a lot. It was really quick response. Now it's a lot clearer!