VS Extension: The SARIF viewer received one or more SARIF logs in which the analysis tool did not detect any results.

Hello,
Infer# worked without any issue on another project, but on this project, instead of a list of results, a banner shows up:

No errors appear in the error list.
The analysis seems to have run without issue:

I ran it on my MQTT project: https://github.com/signature-opensource/CK-MQTT/

Oh -- did you compile your binaries locally on your machine? The issue counts reported to the console were detected across the set of binaries that you provided to Infer#. However, we look at the filenames corresponding to each bug and create a new file which only consists of the files that exist locally on your machine, and open that file -- that file would be empty if all the bugs correspond to filenames not on your machine. It is possible that we didn't find bugs in your project persay, but they correspond to upstream library files (i.e. the FluentAssertions you demonstrate above).

Oh that would explain it, a lot of the issue reported in the excerpt are issues in my dependencies.
I'm still surprised it doesn't find anything on my 2k lines project :D

By reading the report.txt file, it looks like indeed no issues have been found for my files.

Ok, in \\wsl.localhost\infersharp1.4\root\infersharp\infer-staging I can see that none of my DLL are present.
That's explain why there is no issue found for my code.

I will say also that the Pulse framework fundamentally emphasizes precision, so I'm not too surprised if it doesn't find bugs necessarily. If you run the Linux binaries outside of the extension, you can provide the argument "-F" to enable "latent" issues (vs manifest issues, which is what it would report) -- these are issues which Pulse think can occur contextually but wouldn't necessarily occur, and there are usually many more of these.

Is it not because it didn't actually analyzed my DLLs (only some dependencies are in infer-staging ?

If you run the Linux binaries outside of the extension

Sadly I tried to enter the infer WSL distribution but it kinda don't want to:

PS C:\Users\Kuinox> wsl infersharp1.4
/bin/bash: infersharp1.4: command not found

My guess is you need a "-d" -- wsl -d infersharp1.4
Also, if it didn't even analyze the binaries corresponding to your project, then we certainly wouldn't expect any issues on it. Try isolating those binaries alone and rerunning the analysis. Keep in mind that for the analysis we de-dupe by filename for performance reasons, so for example if you have folder1/ConsoleApp1.dll and folder2/ConsoleApp1.dll we only analyze one of them.

If it didn't analysed my binaries, that would be a bug in the infersharp VS extension, no ?

No, it should have analyzed your binaries if they were present in the source directory and you used the expected debug build (you have DLL/PDB for each project). They should get copied to infer-staging, unless there is some issue with how the de-dupe logic that I described above works.

a) have the dlls/pdbs for your project in the initial directory,

Ran the tool on my solution through VS, everything has been compiled in debug mode.
I do have dll-pdbs

b) that they get copied into infer-staging?

But it's doesn't get copied in infer-staging

Do you have the corresponding PDBs as well? This is what I have as output by a debug build on my toy project:

Ah -- we don't yet support PDBs embedded in DLLs. That would be the root issue here. It's a simple fix on our end that I'll try to  address this week - will follow up here when I have that out. To mitigate it in the meantime, separating the embedding from the DLLs should work.

Thanks!
I tracked down why my project did not used the default pdb behavior.
It looks like it's because I'm using DotNet.ReproducibleBuilds and they set it explicitly to  embedded:
https://github.com/dotnet/reproducible-builds/blob/956ec68ee3572d3c29e62c7d37aaf076647ab8c8/src/DotNet.ReproducibleBuilds/DotNet.ReproducibleBuilds.props

@Kuinox Infer# should have no problem analyzing a .dll file with embedded pdb. The root cause here is that we tried optimizing the binary copying logic (IO between Windows file system and WSL is not great) by only copying .dlls with matching .pdbs without touching anything else.
PR https://github.com/microsoft/infersharp/pull/185 should address this.

Ok, thanks !

Hello! I have similar issue. I can see in report.txt that some of the issues are coming from my code, but I don't see any errors in VS UI. I have the flowing project structure:

App (set as analysis root)
Helper Lib (issues are reported here)


Update pandas version requirement in setup.py

This was already updated in the readme and the conda yamls but I forgot to update it in the most important place: setup.py.
We should really fix the code to not require filtering the SettingWithCopyWarning (now tracked in #39), but for now we have it and we need to require the right version of pandas.

Codecov Report

Merging #38 (0ccfe38) into main (2889d1f) will increase coverage by 0.27%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #38      +/-   ##
==========================================
+ Coverage   64.08%   64.36%   +0.27%
==========================================
  Files           9       10       +1
  Lines         465      477      +12
==========================================
+ Hits          298      307       +9
- Misses        167      170       +3

Impacted Files
Coverage Δ

sss/__init__.py
75.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

That sounds good!


How can i make SmartBreadcrumbs fixed on top

Hi,
Looking for some more functionality of SmarBreadcrumbs ;
wanted to know is it possible to make Smartbreadcumbs fixed on top below Navbar.

Hi,
Looking for some more functionality of SmarBreadcrumbs ;
wanted to know is it possible to make Smartbreadcumbs fixed on top below Navbar.

Somehow i am able to find and fixed this issue.
Freezing navbar hides breadcrum behind it.
just adding
body {
padding-top:60px
}

does the trick.
find more here https://stackoverflow.com/questions/18389307/breadcrumb-not-appearing-due-to-the-navbar-fixed-at-top


Bump v0.1.9 policy version.

Description
Updates the artifacthub file bumping the policy version to v0.1.9.
Related to https://github.com/kubewarden/kubewarden-controller/issues/479

As @viccuad needs this policy to next Monday (07/10/2023) and we have no one else available to review this. I'll merge it right now.


VLAZ: Watch SynoGut

VLAZ requests the watch of the watch_keyword SynoGut. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

SynoGut has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


programming compiling 8051Z-stack Home 1.2.2a

What are you using to program/compile 8051 soc for cc2531/cc2530 with Z-stack home 1.2.2a.  The new IAR doesn't support this anymore only Z-stack 3.0.  I think Z-stack Home 1.2.2a readme says you need IAR 9.03 to compile.  And they don't even offer a evaluation of this version anymore.
I have a cc2530 dev board that I want to program to control I/O to a 8ch relay and separate momentary switch.  It's in the supported devices under dnckatsw00x, but the hex is only given for a single relay.
It would also be good to program for simple sensor inputs, temperature etc.  Just manipulating the Z-stack home examples.
I think I already know the answer that you have to buy IAR software, but its a bit much to drop thousands on project, pretty frustrating, kind of kills dev for this board.

What errors do you get when compiling with the latest IAR?


Start ui-tests

Fixes https://github.com/jupyterlite/xeus-python-kernel/issues/29

[x] Add ui-tests top-level folder
[x] Test on chromium and firefox
[x] Snapshot test to check the kernel is correctly registered
[x] Test execute code
[x] Test access files
[x] ~Try webkit to investigate https://github.com/jupyterlite/xeus-python-kernel/issues/152~ -> will try in a separate PR
[x] Add workflow to update snapshots

Deferring the webkit investigation to a separate PR.


Realsense-viewer crashes while opening on MacOS sonoma

librealsense
2.54.2 RELEASE

OS
Mac OS

When I open the realsense-viewer without connecting the camera it's able to open but when I connect the camera the realsense-viewer crashes and it's not opening.
Can someone help me in resolving this issue?
Also is there any minimum system requirements for running realsense-viewer on MacOS?
The errors says it is segmentation fault.
I tried reinstalling but still it's not working.
Please do let me know if you have a solution for this issue.

Hi @Niranjini-Kathiravan  I note that you have posted a comment at the other case at https://github.com/IntelRealSense/librealsense/issues/12727 about problems with realsense-viewer on MacOS Sonoma.
Official support in the RealSense SDK for MacOS ended in 2018, though the SDK has continued to work with Mac in subsequent years and the community of RealSense MacOS users investigates problems and shares solutions with each other.
From MacOS Monterey onwards however problems became more common and there are unfortunately not clear solutions for Sonoma issues available at the time of writing this.  Discussions led by MacOS users such as https://github.com/IntelRealSense/librealsense/issues/12727 are the best chance of finding a resolution.
There are not stated minimum requirements for running realsense-viewer on MacOS.

Hi @Niranjini-Kathiravan  Bearing in mind the advice in the comment above, do you require further assistance with this case please?  Thanks!

Case closed due to no further comments received.


getAllTickers() is only returning a total of 14 tickers.

I can't find any way to set the parameters to expand the ticker list size. I expected to see ALL tickers, since that is the function's name, yet its only showing 14.

Are you calling the sandbox endpoint? I think the sandbox endpoint only returns a limited number of endpoints, but the main endpoint returns all the symbols: https://api.kucoin.com/api/v1/symbols

Since this issue has already been addressed and there have been no updates for a long time, we will now close it.
If you need any further assistance, feel free to ask!


Active cities not working in visits map

When there are selected visits, clicking on the map should present a dropdown asking to load all locations or just selected ones

This is not correct. The dropdown shows when there's pagination, not when there's selected visits.
It is working as intended


Convert drivechart to paper

Let's not checkin username/passwords (especially admin users) to source please. c#/ApiClient/Program.cs and node/app.js
Minor: Missed removing the "Drive Chart" comment from the top of the block that was removed from base.less.
Mobile view needs work (as reported by Josh--I have tested myself).

thank you gitignore... I'll fix this when I get to the mobile thing.


Shares service can be used for user enumeration

Context
oCIS version: v2.0.0-rc.1
Issue
A can enumerate usernames by sending delete share requests for shares which they don't have access to.
The impact is really small since the usernames can be listed through other endpoints but if we someday want to have an instance where listing usernames shouldn't be possible then this issue needs to be fixed.
The share was created by einstein and granted to admin.
Existing user:
curl -k -s -u richard:superfluidity -X DELETE 'https://localhost:9200/ocs/v1.php/apps/files_sharing/api/v1/shares/1284d238-aa92-42ce-bdc4-0b0000009157:4c510ada-c86b-4815-8820-42cdf82c3d51:e952af5d-cbaf-4aff-948e-978033572c03?shareWith=admin' | xmllint --format -
<?xml version="1.0" encoding="UTF-8"?>
<ocs>
  <meta>
    <status>error</status>
    <statuscode>998</statuscode>
    <message>error getting storage provider</message>
  </meta>
</ocs>

Non existent user:
curl -k -s -u richard:superfluidity -X DELETE 'https://localhost:9200/ocs/v1.php/apps/files_sharing/api/v1/shares/1284d238-aa92-42ce-bdc4-0b0000009157:4c510ada-c86b-4815-8820-42cdf82c3d51:e952af5d-cbaf-4aff-948e-978033572c03?shareWith=asdf' | xmllint --format -
<?xml version="1.0" encoding="UTF-8"?>
<ocs>
  <meta>
    <status>error</status>
    <statuscode>998</statuscode>
    <message>error getting grantee</message>
  </meta>
</ocs>

Note the share does not even need to exist. curling
curl -k -s -u richard:superfluidity -X DELETE 'https://localhost:9200/ocs/v1.php/apps/files_sharing/api/v1/shares/1?shareWith=admin' | xmllint --format -

will yield same results


RadioButtons: SelectionChanged event argument can contain null items as its selected/deselected items

Describe the bug
The RadioButtons.SelectionChanged event args contain null items as selected/deselected items. For example, when setting the initial RadioButtons selection (via code or click interaction), not only does the SelectionChangedEventArgs instance say that an item has been selected, but also that an item has been deselected (SelectionChangedEventArgs.RemovedItems.Count = 1). However, there is no such item being deselected (as none was selected before) and SelectionChangedEventArgs.RemovedItems[0] returns null. Thus this could lead to apps to crash if developers trust SelectionChangedEventArgs.RemovedItems to only contain non-null elements (and the expectation is just that).
Expected behavior
No null items should be listed. List count should be 0.
Version Info
Microsoft.UI.Xaml 2.4.0 (and earlier)
Microsoft.UI.Xaml 2.5 previews

This sounds like a bug but @StephenLPeters can confirm if there was a reason for this behavior.

Yup, does sound like a bug :/

Also hitting this via two way binding of SelectedItem.

The most common use case for me with RadioButtons would be basing Items or ItemsSource on an array of enums and then two-way binding SelectedItem to a property of that enum type on my view model. This bug prohibits that use case, because trying to cast null to an enum will throw an exception in the auto-generated code of x:bind. I've had to change all of these properties to MyEnum? (and add a bunch of null coalescing throughout my code) because of this issue.
Can we get a status update?

Still seeing this in 2.6.2.
The easiest way to compare why this is an issue is to do the following. This is what you can make with a ListView that works fine:
<ListView Header="Size" SelectedItem="{x:Bind MySize, Mode=TwoWay}">
    <x:Int32>3</x:Int32>
    <x:Int32>4</x:Int32>
    <x:Int32>5</x:Int32>
    <x:Int32>6</x:Int32>
</ListView>

If you then just directly swap to RadioButtons, it'll fail and throw a NullReferenceException:
<muxc:RadioButtons Header="Size" SelectedItem="{x:Bind MySize, Mode=TwoWay}">
    <x:Int32>3</x:Int32>
    <x:Int32>4</x:Int32>
    <x:Int32>5</x:Int32>
    <x:Int32>6</x:Int32>
</muxc:RadioButtons>

@Ranjeshj @StephenLPeters seems like @Felix-Dev had a PR opened last year? Is there a way to move this along?

Bad bot. Do not close.

Just a reminder that this issue still exists and is still forcing workarounds for the radio button case.

@ccarlo88 was that still with UWP and WinUI2 or also with WinUI 3?


New staking page

Dev tracking issue for new staking page (ClickUp)

Closing in favor of tracking on ClickUp


From-scratch augmentations proposal

As a direct successor to fine-tuning ConvNext the authors' way I propose we should drop their current approach and design our own from scratch.
A look at after-augmentations train batch preview from the authors' approach (code here):

The padding performed by scifAI's library (padding by per-image per-channel mean) varies greatly across images and channels.
Our images are very small. After padding to the nn's input size most of the image becomes just the padding. Perhaps we can do better.
We see weird, rectangular boxes around most cells (the original image's borders). Ideally I would like to do away with those.

Additional factors to consider:

The cells may vary slightly in size (biologically).
Authors use only horizontal and vertical flipping, no rotation during training (they oddly have it when calculating statistics...)
The microscope image quality is not great in the best scenario to very blurry in the worst one.

My proposal for our own take:

Use an algorithm to find the cell borders, considering all channels together. Once we find them, we crop the images to this size. Never used it, but maybe OpenCV can help us?
Apply mirror padding to the desired nn's input size. I'd like to maximize the cell information coverage in the picture, but simple resizing might distort the cells.
A chain of random transformations (50% each one will be applied):

Horizontal flip
Vertical flip
Rotation (180 degrees)
Random resized crop (small one, 80% of the picture always preserved) - to simulate biologically varying cell sizes

Simulate bad image quality (applied independently):

Random adjust sharpness (worsen by 30% at 70% probability) - frequent simulation of mild focus issue
Random Gaussian blur (kernel=3, std in the range=[0.15 - 0.25], probability of applying at 40%) - meant to simulate an occasional, stronger blur in the image.

Min max normalization

Above is a batch preview with no augmentations. As mentioned above, I originally thought that we'll have to find cell borders on our own since channels like brightfield (first one from the top) appeared to have no box around them. Because of this, I thought it was in a different shape than the rest of the channels. But as seen in the preview above it actually has a box, identical in size to the other channels - it was just masked by Gaussian in the original batch preview.
This simplifies things - we don't need to find the cell borders at all, they are already cut out for us. We can use the original images for our own augmentations.
Also, after internal discussion with @Griphu and @swiezew we have decided to not go with mirror padding. The reason for this is that padded, mirrored parts of an image would create duplicates of the original cell. Since the classification task involves a class called Multiplets, directly tied to the number of cells, mirror padding would likely confuse the model.

The agreed approach (for a first ConvNext run) is the following:

Pad original images with zeroes (for uniform background across channels, unlike the mean the authors were using).
50% for random vertical flip
50% for random horizontal flip
50% for rotation in 90 degree angle. Along with both of the flip this gives us a chance of any cell position fed to the model. The authors didn't use rotation and all, so it gives us many more possible inputs to the model compared to their approach.
50% for random resized crop, zoom up to 20%. It is meant to simulate differences in the cell sizes and be non-aggressive.

We also have two ideas we're not implementing from the get-go, but might in the next runs:

Use Gaussian noise or random adjust sharpness to simulate varying image quality. It's not that high to begin with, so we're not starting off with this.
Use SmallestMaxSize + CenterCrop to first resize the image while keeping the proportions of the picture and then take center crop to adjust the dimensions to the net's input. This is the approach used in the pretraining of the ConvNext we will be leveraging. I'm thinking that small cells on a field full of black may confuse the model, but we'll see.

Batch preview with our augments (train):

Batch preview with our augments (val/test), which includes only normalization:

Proposal set, closing for separate task for implementation.


three-part table names in Update/Insert leads to SQLCODE=-518

Node.js version: 12.16.2
idb-connector version: 1.2.9
IBM i version: 3 7
I connect to the *LOCAL database and try to update/insert a table on the remote system through DRDA access using three-part table name. It works well through JDBC or green screen but leads an error through idb-connector:
-518 THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT
To Reproduce

You need two i systems e.g. S1, S2
configure DRDA connection from S1 to S2 for user to be used.
create test table on S2
create table S2.testlib.sbjid (sbj int);
run test script on S1

let db = require('idb-connector');
let dbconn = new db.dbconn();
dbconn.conn("*LOCAL"); // connection to S1
dbconn.debug(true);
let sql =  'insert into S2.testlib.sbjid (sbj) values (1) with NC'; // leads an err
//let sql =  'update S2.testlib.sbjid set sbj=2 where sbj=1 with NC'; // leads an err
//let sql =  'select sbj from S2.testlib.sbjid limit 1'; // works well
let sqlStm = new db.dbstmt(dbconn);
sqlStm.execSync(sql, function (rs, errMsg) {
if (errMsg) {
console.log('errMsg: ' + errMsg);
} else {
console.log('rs: ' + JSON.stringify(rs));
}
});
sqlStm.close();

get error message
errMsg: Error: SQLSTATE=07003 SQLCODE=-518

Hello @SvKN0 , Would you tell me how to configure DRDA connection?
Generally I use the WRKRDBDIRE command to configure the remote database entries. And then connect to the remote database with the entry name --
let db = require('idb-connector');
let dbconn = new db.dbconn();
dbconn.conn("S2", "XUMENG", "PASSWORD"); // connection with the entry name
let sql = 'insert into testlib.sbjid (sbj) values (1) with NC';
let sqlStm = new db.dbstmt(dbconn);
sqlStm.execSync(sql, function (rs, errMsg) {

In this way, the record can be inserted to the remote database correctly.

Hi @dmabupt.
I am not a system administrator and I don't know about any specific system settings (DRDA).
For me it's just add a remote database and save credentials:
ADDRDBDIRE RDB(S2 S2) RMTLOCNAME(S2*IP)
ADDSVRAUTE USRPRF(USR) SERVER(S2) PASSWORD(PWD)
Yes I know that if make connection to remote DB it works. But this connection is very unstable. It crashs several times per day and to fix it needs to restart server.
I need to access multiple DB. Using three-part table name in my case is very useful and the topic of this issue exact "three-part name" =)
Can you, please, try to INSERT through strsql using three-part name. If you are able to do this then the DRDA are configured well.

Hello @SvKN0 , Thanks for the information. Seems we are using the same command the configure remote db access. I just did not know the ADDSVRAUTE trick.
I checked the manual here and started to suspect some commit related attributes. And then I found this one SQL_ATTR_COMMIT.
Would you try to set this connection attribute to SQL_TXN_NO_COMMIT?
let db = require('idb-connector');
let dbconn = new db.dbconn();
dbconn.setConnAttr(db.SQL_ATTR_COMMIT, db.SQL_TXN_NO_COMMIT); // <-- Add this
dbconn.conn("*LOCAL");

Thank you @dmabupt now it works!
I used WITH NC clause in the sql statement.
let sql = 'insert into S2.testlib.sbjid (sbj) values (1) WITH NC';
As I understand it's absolutely the same stuff as QL_TXN_NO_COMMIT attribute but it works only for *LOCAL DB request :[ . Very strange but it solved the problem =)
I very grateful for your time spent!


Storage Layer Discussion

Problem:
Input and output repos have different storage models. This essentially means there are two code paths for any of our operations that access PFS. This is not something we would like to maintain and we believe we can iterate on the output repo model to have it be applicable to input repos while also gaining performance improvements.
Potential Commit Model (input repos):
Commit is started:

Operations (put file, delete file, etc.) are stored with an in-memory hashtree and are associated with a particular chunk of data.
If this hashtree gets past a certain size threshold, we will serialize it to disk (sort, compute hashes, etc.) and create a new in-memory hashtree.
If the user lists/gets a file(s) in the open commit, the access will be treated as a merge of the in-memory and on-disk trees (we will leverage our indexing here).

Commit is finished:

The tree(s) for the current commit are merged with the parent commit, applying the operations to files in sequential order during the merge process.

Details:
The merge process applies the operations
The merge process operates on a sorted stream of hashtree nodes. Nodes that show up in multiple streams are merged together (content is concatenated and file hashes are updated). The merge process for each node would be changed such that it applies the operation(s) in the order of the node streams placement in the merge queue. Therefore, if the hashtrees are merged with the operation order being from oldest to newest, we would get the expected output (with the input repos, the main difference would be correct behavior of overwrites and deletes)
File node protos will need some notion of an operation
With this design, we will need to have some notion of operations stored in hashtrees rather than just state. It probably makes sense for these operations to be associated with the objects/blockRefs because that is the finest granularity operation on a file. Also, I think we will want to keep around objects in input repos and add them to output repos because they will serve as the deduplication layer in Pachyderm (deduplicated content could be stored through objects based on a certain size threshold, figuring out how to do that across Pachyderm is going to be a challenge in itself). The proto change would be as follows:
In hashtree.proto:
Old:
message FileNodeProto {
  repeated pfs.Object objects = 4;
  repeated pfs.BlockRef block_refs = 5;
  ...
}

New:
message FileNodeProto {
  repeated pfs.Data data = 7;
  ...
}

In pfs.proto:
New:
message Data {
  Op op = 1;
  Object object = 2;
  BlockRef blockRef = 3;
}
enum Op {
  APPEND = 0;
  OVERWRITE = 1;
  DELETE = 2;
}

Dump of internal discussions:
We decided to explore a storage model that will impact this change. This new model may provide the features and performance we are looking for with the new hash trees. This model is based on the idea of having two indexes into our sorted data, an index for objects and an index for file offsets. The index for objects is essentially multiple objects in object storage that the files are spread across in lexicographical order. This model also depends on the content based hashing mentioned in #3310 , which will determine the boundaries across which separate objects will exist. Having multiple indexes and content based hashing allows us to merge and batch content much more effectively than we currently do.
The basic idea is that the merge of content is actually just a merge of the new data into the objects that are impacted by the new content. Because there is a global ordering of content (order with respect to lexicographical ordering of files), we can index into the necessary objects based on the output files we are encountering during the merge. Here is a simple example of what this can look like:
Commit 0

Objects: 5c, a7, d3
Files: {a: 5c(0-5)}, {b: 5c(6), a7(0-2)}, {d: a7(3-8)}, {e: d3(0-4)}

Commit 1 (Middle insert of file c)

Objects: 5c, b4, 73, d3
Files: {a: 5c(0-5)}, {b: 5c(6), b4(0-2)}, {c: b4(3-5), {d: 73(0-5)}, {e: d3(0-4)}

Commit 2 (Removal of one byte from the middle of b)

Objects: 5c, 8f, 73, d3
Files: {a: 5c(0-5)}, {b: 5c(6), 8f(0-1)}, {c: 8f(2-4)}, {d: 73(0-5)}, {e: d3(0-4)}

This model provides several benefits: we get a consistent hash of a file regardless of the operations that led to its creation (hash is a combination of the hashes of the objects, plus the edges that don't take up a full object (beginning and end)), our data is stored in a format that lends itself well to batching, and we get an easy way to manage deduplication (at the level of an object that should be of some approximate size, tbd).
Something that is still on the table is whether we want to lazily merge the content. There are some mapreduce workloads where eagerly merging can mean re-storing a lot of data.

Another internal discussion dump:
We are continuing to explore the model discussed in the previous post. I started to prototype some of the new hash trees and encountered a pretty clear point of friction. Our metadata management (hashtree package) is not able to access or manipulate the actual data it is managing. This has one major problem, any place in Pachyderm where we read/write/modify data, we have to shuttle data through two abstractions (hashtree package and object storage api server). This has been okay up to this point, but is going to become more painful as we move towards the model previously discussed because of how much back and forth there will be between the metadata and data management layers. What seems to be a necessary change to effectively support the new storage model is to move both metadata and data management behind one abstraction that can manage hashtrees and the content the hashtrees reference (this layer would also be where we manage the caching of trees/data).

Approaches to implementing these changes:

Attempt to make small steps that can be integrated with the main codebase behind feature flags.

Pros:
Other developers can see the direction we are going at every step, which means they can proactively incorporate their changes
Cons:
Integration at every step, which could significantly slow down how fast we can iterate.

Build the system independently of the main codebase, and attempt to plug it in behind a feature flag when we are confident it is has a stable API.

Pros and cons are essentially the inverse of the first approach.

I am leaning a bit towards the second approach because I think we can still accomplish the main benefit of approach 1 by effectively communicating to engineers not involved with this project that changes they make to the way we read/write/modify files will also need to be implemented within the new storage layer and will need to pass our test suite which would be independent of the main test suite.

Potential model for hash tree creation in regards to memory/disk/object storage caching:
This model includes some notion of a memory/disk threshold that will determine when we need to fall back to a layer that can handle more data. Something we will need to take into consideration when determining this is the potential concurrency here (multiple hash trees being created at the same time on the same machine).
Model:

New hash tree is created:
Add file metadata and data to in-memory data structure.

If the process of adding data goes past the memory threshold:

Sort metadata (potentially includes file/chunk index), write to disk.
Write sorted data (may need to finish reading in the middle) to disk.

If the process of writing to disk goes past the disk threshold:

Select a subset of the on-disk data structures and merge their metadata/data then write to object storage.

Create new in-memory data structure.

The three tiered caching approach is an obvious choice, but a key distinction here is that we are also storing data in this in-memory data structure. The reason we need this is because we want to support workloads that have a high metadata to data ratio (database dumps where each file/datum is a record). This model will allow us to support both ends of the spectrum, a few big files and a lot of small files. This is also a simpler approach than what we had envisioned before because we no longer think about the size of metadata and data independently, we are instead operating on one unit of both metadata and data that can get up to a certain size based on where it is stored. The downside of this is that we would be storing more metadata, at least during tree construction, for the large file case. This downside is acceptable because the extra metadata will grow linearly with the size of the file(s) and will be a small fraction of the data being moved. This approach greatly simplifies how we need to handle moving metadata/data between the caching tiers.

Storage System
A system for storing and incrementally updating filesystems in object storage.
Goals:
Stable object storage format
Won't need to be migrated with every minor release.
Writes
We should be able to write a filesystem into O(fs data) objects. I.e.
it shouldn't be dependent on how many files we have, only their total
size. We should also be able to do this in O(fs data) time.
Reads
We should be able to read the content of a single file in O(Log(total data) + content data) time
We should be able to read the hash of the content of a file (including
directories) in O(Log(total data)) time
We should be able to read out the filesystem between two paths in
O(Log(total data) + fs data) time
Merges
We should be able to merge filesystems symbolically in O(num fs).
Note that this isn't dependant on the size of those filesystems, because
it's done symbolically.
Coalescing
We should be able to coalesce several filesystems that have been symbolically
merged into a single filesystem in O(total fs data)
Concepts:
Tree based hash
We want to compute hashes of files (including directories) because
filesystems (and individual files) can be very large, it's intractable to
compute the hash on a single machine (all the data would have to pass
through that one machine). Instead we do a tree-based-hash by hashing
chunks of content and then computing a hash of hashes for the final
result. To avoid overloading the term, I'm going to call these content
chunks "segments."
Content based segments
The above definition begs the question: how do we segment the data. The
obvious answer is to segment based on some fixed size. This won't work
because when you merge content into the middle of the filesystem it will
offset the segments and we'll need to rehash everything from scratch.
Instead we use content based segments, to do this we use a sliding
window fingerprint algorithm. The result is that segments can be added
in the middle and at most 2 chunks will be disrupted.
Segments will be the level at which we do compression and encrpytion.
The segment size is chosen based on the performance characteristics of
the underlying object storage. Because they're compressed, (and
encrypted if it's enabled) segments most be read in total. So they
should be tuned as the ideal size to read from the storage.
Data Layout
TAR
Our most basic data storage format is a tarball. Tarballs have a number of
appealing properties:
- They're designed for tape which has similar characteristics to object
storage. In particular it's efficient for sequential access.
- It's a well known format that we know includes all the information we
might want to record about files, such as permissions.
- It's designed to be split apart and concatenated.
Downsides:
- It doesn't include any notion of indexing, we'll have to build that
ourselves.
Tar streams have a very simple structure:
+---------+----------+---------+----------+
|f1 header|f1 content|f2 header|f2 content|...
+---------+----------+---------+----------+

The header looks like this:
type Header struct {
	// Typeflag is the type of header entry.
	// The zero value is automatically promoted to either TypeReg or TypeDir
	// depending on the presence of a trailing slash in Name.
	Typeflag byte

	Name     string // Name of file entry
	Linkname string // Target name of link (valid for TypeLink or TypeSymlink)

	Size  int64  // Logical file size in bytes
	Mode  int64  // Permission and mode bits
	Uid   int    // User ID of owner
	Gid   int    // Group ID of owner
	Uname string // User name of owner
	Gname string // Group name of owner

	// If the Format is unspecified, then Writer.WriteHeader rounds ModTime
	// to the nearest second and ignores the AccessTime and ChangeTime fields.
	//
	// To use AccessTime or ChangeTime, specify the Format as PAX or GNU.
	// To use sub-second resolution, specify the Format as PAX.
	ModTime    time.Time // Modification time
	AccessTime time.Time // Access time (requires either PAX or GNU support)
	ChangeTime time.Time // Change time (requires either PAX or GNU support)

	Devmajor int64 // Major device number (valid for TypeChar or TypeBlock)
	Devminor int64 // Minor device number (valid for TypeChar or TypeBlock)

	// Xattrs stores extended attributes as PAX records under the
	// "SCHILY.xattr." namespace.
	//
	// The following are semantically equivalent:
	//  h.Xattrs[key] = value
	//  h.PAXRecords["SCHILY.xattr."+key] = value
	//
	// When Writer.WriteHeader is called, the contents of Xattrs will take
	// precedence over those in PAXRecords.
	//
	// Deprecated: Use PAXRecords instead.
	Xattrs map[string]string // Go 1.3

	// PAXRecords is a map of PAX extended header records.
	//
	// User-defined records should have keys of the following form:
	//	VENDOR.keyword
	// Where VENDOR is some namespace in all uppercase, and keyword may
	// not contain the '=' character (e.g., "GOLANG.pkg.version").
	// The key and value should be non-empty UTF-8 strings.
	//
	// When Writer.WriteHeader is called, PAX records derived from the
	// other fields in Header take precedence over PAXRecords.
	PAXRecords map[string]string // Go 1.10

	// Format specifies the format of the tar header.
	//
	// This is set by Reader.Next as a best-effort guess at the format.
	// Since the Reader liberally reads some non-compliant files,
	// it is possible for this to be FormatUnknown.
	//
	// If the format is unspecified when Writer.WriteHeader is called,
	// then it uses the first format (in the order of USTAR, PAX, GNU)
	// capable of encoding this Header (see Format).
	Format Format // Go 1.10
}

TAR streams are not, according to the spec, required to be sorted, but
we will always store them in sorted order.
Linking
One of the standard types that can be recorded for TypeFlag is
TypeLink (or TypeSymLink). This gives us a natural way to do things
like copies and symlinking within pipelines (shuffling).
Merging
Merging is the most difficult and interesting aspect of what we're
doing, however I think the tar format gives us a fairly elegant way to
handle it. Similar to the TypeLink above we can add a TypeMerge flag
that Pachyderm recognizes. Just like linking tells you that when you're
looking up a file you should actually look up the linked file and return
it. Merging tells you that when you're trying to read from a filesystem
you should instead merge the referenced filesystem and read the result.
A Merge entry in a TAR stream will have Name equal to the first path
stored in the sub-filesystem, the Linkname field will be a path (in
object storage) to the sub-filesystem. The content will include extended
information to make merging more efficient. This should include:
- the last key in the underlying filesystem
- a bloom filter for the paths contained in the sub-filesystem
- the total size of the sub-filesystem
Coalescing
In this scheme every object we store can ultimately be rendered as
a TAR stream, so coalescing means turning it into a TAR stream
that can be rendered with fewer accesses. This basically amounts
to rendering the stream and then storing the rendered stream.
Object Storage
We will have 2 types of object stored in object storage. Semantically
addressed objects and content addressed objects. Semantically addressed
objects are named based on their meaning within pfs. I.e. the file
/pfs// represents the filesystem for  on .
Content addressed files are named based on a hash of their content.
This is what I have in mind for layout in object storage, with the
caveat that for some object stores the paths will need to be reversed to
prevent hot spotting.
/
├── pfs
│   ├── <repo1>
│   │   ├── <commit1>
│   │   └── <commit2>
│   └── <repo2>
│       ├── <commit1>
│       └── <commit2>
└── segment
    ├── <segment1>
    └── <segment2>

Distributed Merging (No shards):
Steps:

Workers process a datum group (actual name tbd) and merge the full results (metadata + data) and write to object storage (this includes chunking and indexing).
At the end of the job, the master merges the metadata from the datum groups and splits the metadata between the workers to perform the merge of the data from the datum group.

This process will need to resolve chunking across the splits of data (rolling hash window needs to resolve chunks at boundaries).
This process will also take advantage of chunks that do not change (big file with no merge insertions is just represented in the output metadata as it was in the datum group metadata, file data does not get read/changed in object storage).

Resulting metadata (that points to the correct chunks and has hashes) is sent back to the master to stitch together the final metadata and create indexes.

Things required to make going through one worker (master) for metadata merging work:

Merge log to avoid paying merge cost at every commit/job.
Merging smaller file sets together before larger ones.


config: Lead off with the purpose of the config

Instead of leading off with links to a bunch of other places, notes on the Go tags, etc., make things more inviting by leading off with a big-picture summary of what the configuration is about.
Also drop the config.json existence MUST because:

This section defines the configuration format, and doesn't need to be tied to a particular filename.

The bundle spec (in bundle.md) already has:

This REQUIRED file MUST reside in the root of the bundle directory and MUST be named config.json.

The config.md line may have been useful when it was added (77d44b10).  But since the bundle.md line landed in #210, I think it's been redundant.

LGTM

rebase plz

Rebased with 0952dd8 → ff071cc, working around the just-landed #756 which I'd spun off this PR earlier :p.

LGTM

LGTM


shortcut for block comment opens help menu?

I am using a mac...so instead of ctrl its actually command (which i had to find out). The line comments (//) work with command + /  but command-shift-/ doesn't do anything
so i experimented and its actually command + option + / to do block comments. Can we update wiki to show mac options?

@carinlynchin I updated the wiki page. As stated on that page, it's hard to keep wiki pages up-to-date with core code and it's impossible with extensions. You can install the Display Shortcuts extension to see the exact shortcuts defined on your system, and also converted to you OS.
Also, the shortcut is displayed next to the Edit > Toggle Block Comment menu item. It's Cmd-Alt-/.

Thank you so much. I didn't know there was an extension. Awesome


add support for RAM - Resource Access Management

MindSphere provides policies support to manage what user has access to what asset tree.
CLI should support creation and configuration of policies
more to be found here: https://documentation.mindsphere.io/MindSphere/apis/core-resourceaccessmanagement/api-resourceaccessmanagement-overview.html

the polciies client is there since few versions already.


How to access web view with Docker

Hi, I am trying to run the getting started examples from xviz and streetscape with two dockers. So far I have first run everything on my own pc to make sure that everything works. Then I have created docker container for xviz and ran it and visualize it with my local streetscape.gl web view through localhost:8080 (I have run "streetscape.gl/examples/get-started$ yarn start-streaming" and it works. However when I create a docker container for streetscape.gl as well and run the same code localhost:8080 says  "localhost didn’t send any data." I have published the port 8080 when running the docker with the code
"docker run -it -p 8080:8080 streetscapegl-master_streetscape /bin/bash"
then when docker started I have done
"/streetscape# cd examples/get-started/" and then
"yarn start-streaming"
When I do this it does not pop-up the localhost:8080 like it normally do and when I manually go to localhost:8080 on my browser it says  "localhost didn’t send any data."  (it does not say localhost:8080 refused to connect" so there is a connection but not any data)
I have tried --publish-all command as well as --network="host" command during the docker run command but none of them worked. Anybody have any idea what am I doing wrong?

@Orkunkizilirmak Do you solve this problem?


Add new FCU API support in Outscale EC2 driver

Add libcloud support for the following new APIs available in the Flexible Computing Unit (FCU)

DescribeInstanceTypes
DescribeProductTypes
GetProductType
DescribeQuota
ModifyInstanceKeypair

The patchset includes tests and fixtures for the new APIs.
Signed-off-by: Javier M. Mellid<EMAIL_ADDRESS>

Ok. I'm happy 👍

@tonybaloney thanks! :+1:


Migrate srf02 driver class member variable initialization to declarations, format whitespace and alphabetize/group/order var/method declarations

Describe problem solved by the proposed pull request
This PR migrates srf02 class member variable initialization to respective declarations, formats whitespace, and alphabetizes/organizes variable and method declarations in srf02.cpp.
This PR is copy/paste of the variable initialization values and method declarastion along with whitespace formatting.
Describe your preferred solution
Standardizing all of the distance sensor driver variable initialization, method ordering and general style will allow for future inheritance structure work to be performed on the distance sensor driver classes.
Describe possible alternatives
All of the distance sensor driver work could be accomplished in one massive PR, but breaking up work in each driver should minimize risk and reduce review effort.
Additional context
See #9279, #11853, #11857, #1858, #11859.
Please let me know if you have any questions on this PR. Thanks!
-Mark

@philipoe , would you be willing to review this PR for me?  I am trying to standardize the distance sensor drivers so that an inheritance hierarchy can be created.  Thank you!

Bench testing of this PR measuring a fixed distance object of approximately 25cm gives similar readings to PX4 master branch.
This PR:

PX4 master:

Hi @dagar, here are flight logs and plots of this PR and current master.  Performance is indistinguishable to me.
Flight log and plots running the SRF02 on current master in position mode varying altitude between approximately 20cm and 2.5m: https://review.px4.io/plot_app?log=246e025c-b744-4176-9bf0-cbf545d1a303

Flight log and plots running the SRF02 from this PR in position mode varying altitude between approximately 20cm and 3.5m: https://review.px4.io/plot_app?log=99cb01c3-62b6-4999-bdba-f7bde750b010

Please let me know if you'd like to see anything else in this PR.  Thanks!

@dagar , ping.

If anyone in the world can prove that this PR has issues, I would like to speak with them about my experience.s :) Is there anyone out there with hardware to test this beside me?

@philipoe , @okalachev @julianoes , please weigh in on this PR. Thank you!

@davids5 and @dagar , The PX4:master stack size is insufficient for this driver.  Here is output from current PX4:master stackcheck when starting the driver:

I have added a commit to increase the stack size, here it output from loading a stackcheck build with this PR:

@davids5  and @dagar, there wasn't enough time to get to this in the dev call today. Would you mind letting me know what else you'd like done? Thanks!


Ability to mark someone as Deceased/Dead

Describe the feature
Add ability to mark person as deceased to this page.

Additional Context
No response

Ems/fd is already able to do this, leo can have this functionality too?

Yes, please. Because sometimes FD/EMS are not available and we have some LEO they are Coroner/Medical Examiner sometimes


Fix system topic can not auto created

Fixes #9265
Motivation
If disabled the topic auto-creation, the system topic under the namespace also not able to be created automatically, this will result in the topic level policy not able to use.


Let user set a history folder for fzf action

With fzf.vim, user can set a history folder with g:fzf_history_dir, and each action will have its separate history files in that folder. That's because the base fzf plugin use this variable to set hisotry file. With this change, people (like me) can transfer from fzf.vim to fzf-lua more seamlessly. I also set the filenames the same as fzf's history files.
Currently I add the --history option at the last stage (in fzf_exec) as what fzf plugin does, since I'm not very familiar with the codebase. It can be better integrated.

@zyd2001, ty for the PR, merged manually as I had a few changes:

Removed the custom names to match fzf.vim's history files, IMHO it doesn't have to match fzf.vim's, these are scratch files that aren't that important
If someone cares enough to match the history filename they can set --history specifically to the providers where the names aren't matching
The name of the history file will now match that of resume map key, that makes it so all grep_xxx commands are stored under the same file in similar way the search/query is saved

Currently I add the --history option at the last stage (in fzf_exec) as what fzf plugin does, since I'm not very familiar with the codebase. It can be better integrated.

Moved to the correct places where all options are evaluated in config.normalize_opts
vim.fn.mkdir is now wrapped in a pcall  to prevent failures (e.g. when fzf_history_dir points to a file)

Other changes:

Removed debug prints vim.print


Add examples from ratatui repo to website

Right now we have an examples folder in the repo with the various examples. It might be more discoverable to be able to see these on the website.
Some ideas:

When doing a ratatui release we just copy and update the examples ratatui -> ratatui-website (this makes the website examples match the release version)
Each example should have a doc, a vhs tape, a gif, a small preview image for the index (like https://bevyengine.org/examples/)

https://ratatui.rs/examples/


feat: add profile and directory options for aws s3

Addresses #322 and #307.
Changes the AWS config option from a single value to a struct:
pub struct AwsConfig {
    pub bucket: String,
    pub profile: String,
    pub directory: String,
}

This allows the user to set a AWS credentials profile other than default to give them more flexibility. In addition, it allows specifying an optional folder name to store the assets in the S3 bucket. If no folder is provided they will be stored at the root level. This lets users store multiple collections in a single bucket.

Finally, this changes the file names to use the standard asset pair file names 0.json, 0.png, 1.json, 1.png etc. to make it easier to figure out what file is what.

Nice improvements!


Intero can't see types in Data.Functor.Foldable

I tried to load Data.Functor.Foldable from https://github.com/ekmett/recursion-schemes/ so I could understand the types. I had to add a stack.yaml file because the repo doesn't contain one. But whenever I press C-c C-t, I just get "Couldn't guess that module name. Does it exist?"

If I try C-c C-l I get:
Starting:
  stack ghci --with-ghc intero "--docker-run-args=--interactive=true --tty=false" --no-build --no-load --ghci-options -odir=/tmp/intero95102qs --ghci-options -hidir=/tmp/intero95102qs recursion-schemes
Intero 0.1.18 (GHC 7.10.3)
Type :intro and press enter for an introduction of the standard commands.

WARNING: /tmp is owned by someone else, IGNORING!
Prelude>
/tmp/intero9510cWg.hs:113:0:
     error: missing binary operator before token "("
     #if HAS_POLY_TYPEABLE

/tmp/intero9510cWg.hs:229:0:
     error: missing binary operator before token "("
     #if EXPLICIT_DICT_FUNCTOR_CLASSES

/tmp/intero9510cWg.hs:410:0:
     error: missing binary operator before token "("
     #if HAS_POLY_TYPEABLE

/tmp/intero9510cWg.hs:420:0:
     error: missing binary operator before token "("
     #if MIN_VERSION_base(4,4,0)

intero: phase `C pre-processor' failed (exitcode = 1)
>

@greenrd just an idea that might help or not (I wasn't able to reproduce your error): did you try to stack build your package from the command line before opening the files with intero?

Can you fix this?

WARNING: /tmp is owned by someone else, IGNORING!

Stack passes things to GHCi that are important via a temporary file.


[resign] Fix typo in resign.rb

Checklist

[ ] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[ ] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

Fixes a typo in the documentation.

Description

Add missing "g" to "provisioning"

Did not test at all.
Testing Steps

@googlebot I signed it!

@eduardopelitti Can you sign the CLA when you get a chance? 😊

@googlebot I signed it!
Just gave it another try @joshdholtz, I was waiting for my company representatives to complete the company form. Hope it works this time.

@eduardopelitti Looks like you are good now (the bot just isn't updating this). Thank you!!


[Feature Request] We would like to view the list of extensions enabled for a workspace and the list of globally enabled extensions on the sidebar, and sync extensions enabled and disabled for all the workspaces

Yes, we know that we can see the extension status description on an extension profile, but we want to see on the sidebar. On the sidebar, we would like to view the lists of:

extensions enabled for a workspace;
extensions disabled for a workspace;
globally enabled extensions;
globally disabled extensions.

We also would like to sync or back up disabled and enabled extensions for all the workspaces to Settings Sync, so we wouldn't have to enable and disable for a workspace. Only the globally enabled and disabled extensions are synced.

/duplicate
It is a duplicate of multiple feature requests

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Text is a little too dark in Black/Dark themes

I'll second this remark.
Font is grey when using dark theme, which makes is hardly visible. It should be much lighter grey, if not just white.
Please fix this :)

I have the same issue 👍

Yes I agree too, the text is too dark, contrast should be higher :)

Yeah, its pretty much unuseable in dark theme sadly.. :(

@klaussinani while waiting for this, is there a way to modify the theme manually, for example through a json or config file? Can you point us to the right direction?
Thanks!

Not just font color , icon color same problem:

I tried to modify https://github.com/klaussinani/ao/blob/master/src/style/dark-mode.css and run npm start but nothing seems to happen. Any clues ?


Displaying sumstats info (yes/no) for each study to facilitate data sorting for users

Following up from the feedback on OTG functionalities provided by BMS on 8-6-22.
As a user, I need to be able to select/sort studies with summary stats even before clicking on the "gene prioritisation" tab.
This will allow a better user experience with quicker navigation through the data. This should be a straightforward task.
Tasks

[] Add the sumstats info (yes/no) next to each study.

Specifications:

1) On the Target/gene page: add this next to each row in the L2G table and the coloc table (see example below)

On the Variant page: add this in the tables (see example below)

On the gene prioritisation page: add this in the ‘Association Summary’ section, under "study details" (see example below)

Acceptance tests
How do we know the task is complete?

When the pages/tables mentioned above display the "has sumstats - yes/no" field
Test

On the cloud and also in this link:  ftp://ftp.ebi.ac.uk/pub/databases/opentargets/genetics/latest/lut/study-index/
there are the annotations for each study. In this table there is also a column called "has_sumstats" which indicates whether a study has summary statistics or not

For use-case #3 above: Gene prioritisation page (evidence page) -add sumstats info in the Association Summary’ section, under "study details":
-this is possible as endpoint "hasSumstats" is queried
API query:
query StudyLocusHeaderQuery($studyId: String!, $variantId: String!) {
studyInfo(studyId: $studyId) {
studyId
traitReported
pubAuthor
pubDate
pubJournal
pmid
nInitial
nReplication
nCases
hasSumstats
__typename
}
variantInfo(variantId: $variantId) {
rsId
id
__typename
}
}
Example response:
{
"data": {
"studyInfo": {
"studyId": "GCST002222",
"traitReported": "LDL cholesterol",
"pubAuthor": "Willer CJ",
"pubDate": "2013-10-06",
"pubJournal": "Nat Genet",
"pmid": "PMID:24097068",
"nInitial": 94595,
"nReplication": 93982,
"nCases": null,
"hasSumstats": true,
"__typename": "Study"
},
"variantInfo": {
"rsId": "rs7254892",
"id": "19_44886339_G_A",
"__typename": "Variant"
}
}
}

Visualisation specs (for consistency with current style of table in Portal):
HEADER: Sumstats
VALUE: yes/no
N.B.: currently, the studies with sumstats are also visualised in blue in the searchbox dropdown when searching for a study. This visualisation will not be modified for now.

I can see the data (hasSumstats) is available - I'll start working on this


How should I use no-relative-imports

Hello!
I am amazed how productive became my work with vscode, typescript and this config.
Thank you for your great work with it.
I'm new with typescript and tslint, so I'm a bit confused how to use rule 'no-relative-imports'.
Suppose I have small frontend project with Webpack + Vue + ts-loader.
Main core written with typescript, other files with javascript.
In folder 'core' I have two files:

ElData.ts

...

export class AnimationElement {
  ...
}

...

SportData.ts

import * as ElData from './ElData';

...

The thing is, 'no-relative-imports' throws error:
[tslint] Imported module is being loaded from a relative path. Please use an absolute path: import * as ElData from './ElData'; (no-relative-imports)
Hmm, disable rule is not my way to resolve a problem!

First thing I try is just remove './' from my import like this:

SportData.ts

import * as ElData from 'ElData';

...

[tslint] Module 'ElData' is not listed as dependency in package.json (no-implicit-dependencies)
Well, lets try another way

Improve tsconfig.json

{
  ...
  "compilerOptions": {
    ...
    "baseUrl": "./src"
  }
}

And then

SportData.ts

import * as ElData from 'core/ElData';

...

[tslint] Module 'core' is not listed as dependency in package.json (no-implicit-dependencies)
[tslint] Submodule import paths from this package are disallowed; import from the root instead (no-submodule-imports)
Arrgh

Last hope

My webpack config a bit supercharged with aliases
{
  ....
  resolve: {
    alias: {
      '@': resolve('src'),
    }
  },
  ...
}

SportData.ts

import * as ElData from '@/core/ElData';

...

[tslint] Module '@/core' is not listed as dependency in package.json (no-implicit-dependencies)
[tslint] Submodule import paths from this package are disallowed; import from the root instead (no-submodule-imports)
[ts] Cannot find module '@/core/ElData'.
Jesus, all I achieved is just increase of errors.
How should I cook my imports?

I have the same question. I cannot figure out how to get no-relative-imports to work with the no-submodule-includes and the no-implicit-dependencies issues.
Just seems like too much hassle so I disabled the no-relative-imports rule.

Hi there - welcome to TS/TSLint/VSCode/etc.! Glad you're enjoying the new area 😊 it's great to have you!
I personally don't use this rule in my projects. The idea as I understand it is to encourage setting a baseUrl in your tsconfig.json, but that seems uncomfortable to me. Should we deprecate this rule @HamletDRC ? Do you have more context around it?

I've tried using the baseUrl method to get rid of the no relative paths issues, however when I do that I start violating two other rules: no-submodule-includes and no-implicit-dependencies.
no-submodule-includes is hit because I include components from subfolders in my solution.
no-implicit-dependencies is hit because the rule thinks that if I am not doing a relative include, then the code must be coming from a NPM package and wants me to include the package in my package.json file.
Can we drop the no-relative-imports rule from the microsoft tslint rule set? It might make sense for tiny projects or for npm packages but definitely does not work for website projects using tools such as webpack.

violating two other rules

Amusing. Yes, I'm in support of this. Let's leave this issue open for a few weeks, we can mark it as deprecated, then remove in a future major version.

@JoshuaKGoldberg Please don't remove this, I really like this rule. We don't use the no-submodule-includes and just wrapped the no-implicit-dependencies rule to ignore the files in the baseUrl path and it works really well!
Maybe we can just publish this as a standalone rule?

Interesting! @LukeSheard - could you please give a little more info on why you chose that way?

@JoshuaKGoldberg While I probably can't give amazingly detailed specifics.. Essentially we run a very large monorepo + single package.json at the root and so we run with the idea that our "top level" is a set of packages itself, meaning that imports look like
import { myThing } from "my/other/thing/over/here";

Since we other languages side by side with TypeScript we find that it gives nice consistency and also means if you move a file you can easily update imports by just searching for the module path.

That's a really interesting approach, thanks for posting it! Have you tried good-fences?
Also, would you mind also posting your tslint.json config here (or just the relevant rules around paths, importing, and/or modules)?

@JoshuaKGoldberg I haven't come across good-fences before, but it looks very useful for our code base!
Our tslint.json is a little bit up in the air right now as we begin to let the dust settle, but I'll get follow up in a couple of days.
I think that removing it from the default recommended configuration is the best solution, leaving it for users to bring it if it works for their use case.

In v6.0 allow-siblings option will be available which allows imports from same or nested folders so ./ElData from original post will be allowed.
Does this option solves other problems in this thread?

Tweaked @ford04's solution and it seems to work well with a default React project structure:
{
  "no-implicit-dependencies": [true, "dev", ["src"]],
  "no-submodule-imports": [true, "src"],
  "no-relative-imports": [true, "allow-siblings"]
}

Just ran across this project that may be relevant to some people in this discussion.
https://github.com/vladimiry/tslint-rules-bunch

☠  It's time! ☠
Per #876, this repository is no longer accepting feature pull requests. TSLint is being deprecated and we recommend you switch to https://typescript-eslint.io.
Thanks for open sourcing with us, everyone!


Integra 6MT ASPEC

Adds 6MT details which is not available in 2022 civic. Auto transmission states (D, N, P, R) are not present in the signals. XMISSION speed is also not present in the signals.
If adding the MT details to the 2022 civic DBC is a better path, please do that instead.
Here is the fingerprint:
#Integra 416955121 is Unknown & probably 6MT transmission
CAR.INTEGRA_6MT: {
(Ecu.eps, 0x18da30f1, None): [
b'39990-T38-A040\x00\x00',
],
(Ecu.gateway, 0x18daeff1, None): [
b'38897-3S5-A210\x00\x00',
],
(Ecu.srs, 0x18da53f1, None): [
b'77959-3S5-A920\x00\x00'
],
(Ecu.combinationMeter, 0x18da60f1, None): [
b'78108-3S5-AC20\x00\x00',
],
(Ecu.fwdRadar, 0x18dab0f1, None): [
b'36161-3S5-A060\x00\x00',
],
(Ecu.vsa, 0x18da28f1, None): [
b'57114-3S5-CA30\x00\x00',
],
(Ecu.unknown, 0x18da3af1, None): [
b'39390-3S5-A020\x00\x00',
],
(Ecu.hud, 0x18da61f1, None): [
b'78209-3S5-A030\x00\x00',
],
(Ecu.programmedFuelInjection, 0x18da10f1, None): [
b'37805-6LM-A020\x00\x00',
],
},
}

Hi Sunny - I figured I'd simplify and just get you the DBC. My efforts to try and integrate the changes on my own failed. I popped the fingerprint in to commit comments but, can submit a PR for the values.py if you want. Thanks!

Thanks for the PR @tapperoo42 . Can you please reopen the PR against the sunnypilot:master branch? It would be a whole lot easier to work on the port.

I'll move it wherever works best!


Run atom-beautify from command line

I'm interested in being able to leverage the abstraction atom-beautify offers to access multiple beautifiers/de-crufters from the command line so I could use the wonderful functionality via scripts.

I have been thinking of this as well and have been trying to implement the internal code in a way that should allow easier separation of Atom Beautify from its individual beautifiers.
The beautifiers and languages directories inside of the src/ directory could be separated from this Atom Beautify repository into a separate Node.js package.
Usage of this package would be similar to the following:
// Create a generalized Beautifier
Beautifiers = require("./beautifiers")
beautifier = new Beautifiers()
// Beautify
beautifier.beautify(text, allOptions, grammarName, editedFilePath, onSave : onSave)
    .then(beautifyCompleted)
    .catch(beautifyCompleted)

See https://github.com/Glavin001/atom-beautify/blob/master/src/beautify.coffee#L9-L10 and https://github.com/Glavin001/atom-beautify/blob/master/src/beautify.coffee#L181-L183
This package could then be turned into a command line interface that you could call from scripts.

I also want to look into support Sublime, along with CLI usage. The beautification core should be completely separate from Atom.

When you are ready to jump into CLI just let me know how I can help.  I have some experience integrating functionality to CLI via Node.

Thanks, @prettydiff !

@prettydiff : what do you think the core should be called? I'm currently thinking Unibeautify.
The name Atom-Beautify obviously will not work once we expand to support much more than just Atom.
My current plan for v1 is to support the following:

Atom
Sublime
CLI
Core (Node.js API)

Build tools like Grunt or Gulp can also have packages using the Core/Node.js API. The CLI will allow users to beautify their code immediately as other packages are developed.

Yeah, I am fine that name.  For the command line operation two work the beautifier will need to be either JavaScript or executable from the command line (using a Node child process).  Running the code is the easy part (provided we are beautifying only one file at a time).  The hard part is keeping everything uniform and making API decisions.  We can beautify multiple files (directory or directory tree) from the command line as well, but we should save that as a later enhancement.
I can write a preliminary CLI module next week in a pull request.  I should be able to take quite a bit from Pretty Diff and just reconfigure it.

This is possible as of moments ago: https://github.com/Unibeautify/unibeautify-cli
I have currently only implemented Pretty Diff beautifier: https://github.com/Unibeautify/beautifier-prettydiff
More to come! Please provide your feedback in Issues of the new repositories!


Probably can't import fixtures using ExUnit.TestCase and define them locally.

As documented here: https://github.com/obmarg/ex_unit_fixtures/commit/37cf4fb3024abc4a03aa551fb455f4df9f7f6e90 it's possible to use ExUnit.CaseTemplate to import some fixtures.  However, I'm pretty sure this won't play too well with defining fixtures locally to a test file.
It'd be good to test this to be sure, and then provide a way of making it work.

This is dealt with in #7 - it's no longer recommended to use ExUnit.CaseTemplate to import fixtures, and the new ExUnitFixtures.FixtureModule code handles this case.

Fixed in #7


FREERDP  via command line on android

is it posible to start freerdp with specific ip and port from command line in android ?

@ANANTHU-R-NATH not really. However you should be able to launch aFreeRDP by creating/downloading/.. a .rdp file and trying to open that.

@ANANTHU-R-NATH please also note that this is a issue tracker and not a help forum. For questions please try the mailing list or visit our irc channel.


[BUG]: [Child] Admin | Sync Logs - Missing Case Statement for "PowerAppPermissionEdited"

Describe the bug
The Filter array command is pulling 4 conditions,
@or(equals(item()?['Operation'], 'LaunchPowerApp'), equals(item()?['Operation'], 'DeletePowerApp'), equals(item()?['Operation'], 'DeleteFlow'), equals(item()?['Operation'], 'PowerAppPermissionEdited'))...
....but the switch/case statement is only logging 3. The logic doesn't appear to be doing anything with the PowerAppPermissionEdited data, there is no case statement and nothing in the default.
Component (please tell us which flow or app you are experiencing issues with):

Solution: Audit Log Components
Version: 1.36
App or Flow: [Child] Admin | Sync Logs

To Reproduce
Steps to reproduce the behavior:

Go to '[Child] Admin | Sync Logs'
Edit the flow
Review the conditions in the filter array. There are 4.
Review the conditions in the switch/case commands.  There are 3.

Expected behavior
All conditions should be logging. Are we not logging PowerAppPermissionEdited by design?
Screenshots

Additional context
Couldn't this be condensed into 1 flow? Not sure why there is a parent/child design with these 2 flows.

This is expected behaviour at the moment. Some of our customers wanted to be able to receive alerts for apps that are shared, but it wasn't broad enough feedback to implement this in the kit - we have therefore only prepared the flow to be able to act on this audit event. The CoE Starter Kit is a starting point for customers to implement their own admin and governance processes, and this is just one place where we provide a template only that can be modified.
The Parent Flow prepares time segments, and the Child Flow runs per time segment. The custom connector is limited in how many audit events it returns per call - for example, if you want to retrieve audit events on a daily basis, the parent flow prepares 1 hourly time segments (2021-03-21 09:00 to 2021-03-21 10:00) and calls the Child Flow 24 x for each time segment.

@manuelap-msft  - Understood, thank you for clarifying.
Regarding app sharing, we could actually use some tools or even some guidance on Flow sharing auditing/reporting. We'd like to have a "personal productivity" environment where sharing is not allowed. I started a discussion thread on this.
https://github.com/microsoft/powerapps-tools/discussions/853


Does CTest support setup and teardown functions per suite of tests (instead of per test)?

Hi,
Neat library!
As the tittle suggests, I was wondering if it's possible to have a setup/teardown function per each suite of tests instead of per each tests inside a suite?
Thanks!

Hi ,
Thx!
Do you mean you want a special setup and teardown function that's called
once per suite?
That is not supported at the moment..
The setup can be easily added in the normal setup in combination with a
global Boolean...
The teardown is nastier..
What use case do you have?
Bas
On Thu, 20 May 2021, 10:44 supersonicnumbers, @.***>
wrote:

Hi,
Neat library!
As the tittle suggests, I was wondering if it's possible to have a
setup/teardown function per each suite of tests instead of per each tests
inside a suite?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bvdberg/ctest/issues/47, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALLGWTN73UGIPWPJ3YKXLTOTDVNANCNFSM45GN4IWA
.

Hi,

Do you mean you want a special setup and teardown function that's called
once per suite?

Yes, I meant this.
My use case is ordinary testing (systems programming). I am currently looking for a test library and did found a couple of interesting ones (criterion, unity,...) but much prefer yours due to its small footprint, however the possibility of having a setup/teardown per suite would be quite important, as it makes it easier (and faster) to run large test files.
Have a nice day.

Hi,
i would not be hard to add i think, so maybe you could attempt that. The
macro code is quite dense however,
Best regards,
Bas
On Thu, May 20, 2021 at 1:09 PM supersonicnumbers @.***>
wrote:

Hi,
Do you mean you want a special setup and teardown function that's called
once per suite?
Yes, I meant this.
My use case is ordinary testing (systems programming). I am currently
looking for a test library and did found a couple of interesting ones
(criterion, unity,...) but much prefer yours due to its small footprint,
however the possibility of having a setup/teardown per suite would be quite
important, as it makes it easier (and faster) to run large test files.
Have a nice day.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bvdberg/ctest/issues/47#issuecomment-844988147, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALLGXQOWYDGORD3CKAZ5LTOTUU3ANCNFSM45GN4IWA
.

Thanks.
Is this something you would consider to eventually add yourself to the library (or accept a PR) ?
Curious to hear your thoughts.

Hoi Supersonic,
i have no other requests of people needing something like that, so i think
it's best if you modify it yourself.
Good luck,
Bas
On Fri, May 21, 2021 at 2:51 PM supersonicnumbers @.***>
wrote:

Thanks.
Is this something you would consider to eventually add yourself to the
library (or accept a PR) ?
Curious to hear your thoughts.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bvdberg/ctest/issues/47#issuecomment-845928047, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALLGWKZB2ZEMXWAGWUI63TOZJMZANCNFSM45GN4IWA
.

Thanks for the info!


Collect all known PowerShell Core installations for dynamic profiles

This pull request teaches the PowerShell Core generator about a bunch of different locations in which it might find a PowerShell.
These instances will be sorted, a leader will be elected, and that leader will be promoted and given the vaunted title of "PowerShell".
Names will be generated for the rest.
The sort order is documented in the comments, but that comment will be replicated here:
// <-- Less Valued .................................... More Valued -->
// |                 All instances of PS 6                 | All PS7  |
// |          Preview          |          Stable           | ~~~      |
// |  Non-Native | Native      |  Non-Native | Native      | ~~~      |
// | Trd  | Pack | Trd  | Pack | Trd  | Pack | Trd  | Pack | ~~~      |
// (where Pack is a stand-in for store, scoop, dotnet, though they have their own orders,
// and Trd is a stand-in for "Traditional" (Program Files))

Closes #2300

Maybe should add powershell core 7 stable profile now?

@bys1123 that’s the point, it is automatic.

@DHowett-MSFT Thanks for explains. But, powershell core 7 stable didn't show up on my Terminal list. Is Windows Terminal Preview v0.9.433.0 included this PR?

Yes. Can you share a copy of your profiles.json?

Here you are:
// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation

{
    "$schema": "https://aka.ms/terminal-profiles-schema",

    "defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",

    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles
        },
        "list":
        [
            {
                // Make changes here to the powershell.exe profile
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "Windows PowerShell",
                "commandline": "powershell.exe",
                "hidden": false
            },
            {
                // Make changes here to the cmd.exe profile
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "name": "cmd",
                "commandline": "cmd.exe",
                "hidden": false
            },
            {
                "guid": "{c6eaf9f4-32a7-5fdc-b5cf-066e8a4b1e40}",
                "hidden": false,
                "name": "Ubuntu-18.04",
                "source": "Windows.Terminal.Wsl"
            },
            {
                "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
                "hidden": false,
                "name": "Azure Cloud Shell",
                "source": "Windows.Terminal.Azure"
            }
        ]
    },

    // Add custom color schemes to this array
    "schemes": [],

    // Add any keybinding overrides to this array.
    // To unbind a default keybinding, set the command to "unbound"
    "keybindings": []
}

And where did you install powershell core 7?

E:\Program Files\PowerShell\7

Sorry, Terminal only checks normal places. It uses your system’s official “Program Files” directory to determine where to look.
Anybody installing autodetectable shells to weird locations will need to make their own profiles for them.

But vscode detect it automatically.

@bys1123 I have a workaround for this: make a symlink from where you installed PowerShell to C:\Program Files\PowerShell and let Windows Terminal regenerate the profile.


Migration guide for deprecations

It would be really helpful if the deprecation message shows which properties to use.
Currently, it only shows something like:
'menuAnimationFadeStrength' is deprecated: This property has been moved to the SideMenuPresentationStyle class.

and I couldn't guess which property to use using the autocomplete feature in Xcode.
I then headed to the README and got confused since the names of the properties were changed drastically.
I could finally find the solution by searching menuAnimationFadeStrength, using #500
It would have been nice if the message hinted me which properties to use, as I repeated the above for a few more settings!
EDIT: Now my app crashes if I try to open the side menu. My original code was like:
  func setupSideMenu() {
    let sideMenuManager = SideMenuManager.default
    // Fixes status bar getting blacked out
    sideMenuManager.menuFadeStatusBar = false
    sideMenuManager.menuPresentMode = .menuSlideIn
    sideMenuManager.menuAnimationFadeStrength = 0.6
    sideMenuManager.menuShadowOpacity = 0
  }

If I use the above code (with deprecation messages) it fails here:
    sideMenuManager.menuPresentMode = .menuSlideIn

So I migrated the code like:
    case "Present Side Menu Segue":
      let sideMenuNavCon = segue.destination as! UISideMenuNavigationController
      // Fixes status bar getting blacked out
      sideMenuNavCon.statusBarEndAlpha = 0
      sideMenuNavCon.settings.presentationStyle = .menuSlideIn
      sideMenuNavCon.presentationStyle.presentingEndAlpha = 0.6
      sideMenuNavCon.presentationStyle.onTopShadowOpacity = 0

in prepare(for:sender:) method, and none of them work; they produce Thread 1: signal SIGABRT error without any helpful outputs.
I tried to debug at let sideMenuNavCon = ... line, and did
(lldb) po sideMenuNavCon.presentationStyle
error: Couldn't lookup symbols:
  SideMenu.UISideMenuNavigationController.presentationStyle.getter : SideMenu.SideMenuPresentationStyle
(lldb) po sideMenuNavCon.presentationStyle.onTopShadowOpacity
error: Couldn't lookup symbols:
  SideMenu.UISideMenuNavigationController.presentationStyle.getter : SideMenu.SideMenuPresentationStyle

What am I doing wrong here?
PS: I tried to change the label to "bug", but I couldn't change it.

Rather than setting the style of the menu in prepare(for:sender:), do it in the menu's viewDidLoad so you don't have to set it all over the place.
As for what's causing your error -- I'm not sure. I have no problems with it in my projects. Perhaps your menu isn't probably subclassed in Storyboard. I'd search StackOverflow for clues.
Regarding the deprecations: I put my effort into the README. I'm sorry it took you time to understand it. If you'd like to update the deprecations I'm open to that. I need to move on to other code, unfortunately.

One more question: viewDidLoad of which view controller?
Should I subclass UISideMenuNavigationController and override viewDidLoad, or in the child view controller's viewDidLoad and use navigationController as? UISideMenuNavigationController?

The latter choice.
On Wed, Jul 24, 2019 at 1:09 AM Jay Lee<EMAIL_ADDRESS>wrote:

One more question: viewDidLoad of which view controller?
Should I subclass UISideMenuNavigationController and override viewDidLoad,
or in the child view controller's viewDidLoad and use navigationController
as? UISideMenuNavigationController?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/jonkykong/SideMenu/issues/512?email_source=notifications&email_token=ABLWL7ZJ7MMXQOILZPPGSFTQBAE4RA5CNFSM4IGMPRU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2VRCKY#issuecomment-514527531,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLWL7YNHXPUP7NMY5X3HTLQBAE4RANCNFSM4IGMPRUQ
.

--


Components

In this project, the Following tasks were completed:

Deleted all the boilerplate in the CRA.
Created a directory called components.
Created a calculator.js and calculator.css file that creates a UI.
Passed linter errors

Hi @TayyabKM,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Highlights

Correct GitFlow ✔
No linter errors ✔
Good implementations ✔

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

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


integration wont open and cant delete to attempt reinstall

here are my logs:
Logger: homeassistant.setup
Source: setup.py:221
First occurred: 11:27:10 AM (1 occurrences)
Last logged: 11:27:10 AM
Setup failed for custom integration 'kingspan_watchman_sensit': Requirements for kingspan_watchman_sensit not found: ['kingspan-connect-sensor==3.0.2'].
2024-01-04 11:26:17.966 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration kingspan_watchman_sensit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-01-04 11:27:10.435 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration 'kingspan_watchman_sensit': Requirements for kingspan_watchman_sensit not found: ['kingspan-connect-sensor==3.0.2'].
File "/config/custom_components/kingspan_watchman_sensit/init.py", line 17, in
from .api import APIError, SENSiTApiClient
File "/config/custom_components/kingspan_watchman_sensit/api.py", line 6, in
File "/config/custom_components/kingspan_watchman_sensit/init.py", line 17, in
from .api import APIError, SENSiTApiClient
File "/config/custom_components/kingspan_watchman_sensit/api.py", line 6, in
thanks
just updated to ha 2024.1 dont know if this was broken before or after

Issue is caused by 24.01.0. Reverting to 23.12.4 the integration loads and functions normally.

Can confirm I am also seeing this on 24.01.0:
Logger: homeassistant.setup
Source: setup.py:221
First occurred: 09:12:51 (1 occurrences)
Last logged: 09:12:51

Setup failed for custom integration 'kingspan_watchman_sensit': Requirements for kingspan_watchman_sensit not found: ['kingspan-connect-sensor==3.0.2'].

+1 from me - seems to have been induced by the latest release of HA 24.01.0

Python dependency hell again. Will look at it this weekend, but reverting to 2023.12 is the solution for now.

LOL - appreciate it @masaccio.  I bet you are regretting the day I reached out to you to develop this integration 😉

v1.6.4 has been released but breaks differently.

And now v1.6.5. Loads in my 2014.1.

Thanks @masaccio  - applying latest HA updates and your integration v1.6.5 now working a treat again!

Thankyou for fixing this so quickly.


Add integration for LocalAI

Feature request
Integration with LocalAI and with its extended endpoints to download models from the gallery.
Motivation
LocalAI is a self-hosted OpenAI drop-in replacement with support for multiple model families: https://github.com/go-skynet/LocalAI
Your contribution
Not a python guru, so might take few cycles away here.

Hey I would like to take upon this task and would be willing to contribute
can this be assigned to me
regards

I would highly appreciate this issue being picked up again!
The issue with the current state of affairs is that AzureChatOpenAI and ChatOpenAI both send requests to /v1/openai/deployments/MODEL_NAME/chat/completions but LocalAI expects completion requests to hit /v1/chat/completions.

I would highly appreciate this issue being picked up again!
The issue with the current state of affairs is that AzureChatOpenAI and ChatOpenAI both send requests to /v1/openai/deployments/MODEL_NAME/chat/completions but LocalAI expects completion requests to hit /v1/chat/completions.

We have the same issue... is there some workaround to point it at LocalAI w/o too many code changes?

I would highly appreciate this issue being picked up again!
The issue with the current state of affairs is that AzureChatOpenAI and ChatOpenAI both send requests to /v1/openai/deployments/MODEL_NAME/chat/completions but LocalAI expects completion requests to hit /v1/chat/completions.

We have the same issue... is there some workaround to point it at LocalAI w/o too many code changes?

use another backend :sweat_smile:

I would highly appreciate this issue being picked up again!
The issue with the current state of affairs is that AzureChatOpenAI and ChatOpenAI both send requests to /v1/openai/deployments/MODEL_NAME/chat/completions but LocalAI expects completion requests to hit /v1/chat/completions.

I'm wondering what openai client version are you using? /v1/chat/completions is actually what is used currently https://platform.openai.com/docs/api-reference/chat/create

both send requests to /v1/openai/deployments/MODEL_NAME/chat/completions but LocalAI expects completi

From my experience, when you have OPENAI_API_TYPE set to 'azure' latest Langchain (v0.0.354) ChatOpenAI goes to /v1/openai/deployments/MODEL_NAME/chat/completions, but if you switch OPEN_AI_TYPE to 'open_ai' it goes to /v1/engines/MODEL_NAME/chat/completions -- but LocalAI is not implementing this endpoint.


Convoy - Not able to scale up Services with convoy volume drivers since the instances fail to find suitable host.

Server Build - from master - Nov 18
Set up - 3 hosts
Host1 is not part of the convoy volume driver.
Host2 and Host3 are part of the convoy volume driver storage pool.
Deploy a service with scale 4 using convoy as volume driver.
4 instances of the services got deployed in host2 and host3 as expected.
Scale up service by 2.
The scaled up instances failed to get deployed because of not finding a suitable host for deployment.

Tested with build from latest.
Scaled up instances of a Services with convoy volume drivers get deployed in hosts which have access to convoy storage pools as expected.


Fixed Discord Link README.MD

Fixed Discord Link in
"Join our [Discord community] for support and discussions"  in README.MD

Description

Related Issues

Solution and Design

Test Plan

Type of change

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

Checklist

[ ] My pull request is atomic and focuses on a single change.
[ ] I have read the contributing guide and my code conforms to the guidelines.
[ ] I have documented my changes clearly and comprehensively.
[ ] I have added the required tests.

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


Update go-legs for data transfer IPLD based Vouchers

What
Update the voucher / voucher result types used in go-data-transfer to work with the proposed updates to the voucher system in https://github.com/filecoin-project/go-data-transfer/pull/305
The current voucher / voucher result types that need to be converted to bindnode are as follows:

https://github.com/filecoin-project/go-legs/blob/main/dtsync/voucher.go#L17
https://github.com/filecoin-project/go-legs/blob/main/dtsync/voucher.go#L27

The code that uses these vouchers is in the same file.

I believe this is done by https://github.com/filecoin-project/go-legs/pull/112

@masih unfortunately not; that's just the go-graphsync bit. The new API for go-data-transfer is being worked on @ https://github.com/filecoin-project/go-data-transfer/pull/325

Right you are thank you. Please ignore me


Upgrading Integration Server vrom 8.1.2 to 8.1.3 is failing

ECE Version Info
ESS production
Bug description:
The update from 8.1.2 to 8.1.3 updates Elasticsearch, Kibana but it does not update the Integrations server
Steps to reproduce:

Create a cluster running 8.1.2 with the Elastic terraform provider

terraform {
  required_version = ">= 0.12.29"

  required_providers {
    ec = {
      source  = "elastic/ec"
      version = "0.4.0"
    }
  }
}

provider "ec" {
  endpoint = "https://cloud.elastic.co"
  apikey = "<<REDACTED>>"

  verbose = false
}

# Create an Elastic Cloud deployment
resource "ec_deployment" "main" {
  name = "xyz"

  # Mandatory fields
  region                 = "gcp-us-west2"
  version                = "8.1.2"
  deployment_template_id = "gcp-io-optimized-v2"

  elasticsearch {
    autoscale = true
  }

  kibana {}

  integrations_server {
    topology {
      zone_count = 2
      size = "2g"
    }
  }
}

Update the Cluster to 8.1.3 using terraform too

terraform {
  required_version = ">= 0.12.29"

  required_providers {
    ec = {
      source  = "elastic/ec"
      version = "0.4.0"
    }
  }
}

provider "ec" {
  endpoint = "https://cloud.elastic.co"
  apikey = "<<REDACTED>>"

  verbose = false
}

# Create an Elastic Cloud deployment
resource "ec_deployment" "main" {
  name = "xyz"

  # Mandatory fields
  region                 = "gcp-us-west2"
  version                = "8.1.3"
  deployment_template_id = "gcp-io-optimized-v2"

  elasticsearch {
    autoscale = true
  }

  kibana {}

  integrations_server {
    topology {
      zone_count = 2
      size = "2g"
    }
  }
}

Check that the activities end successfully and the integration server is not updated

This is actually an elastic/cloud-sdk-go issue, transferring it there.


Use mouse click gesture to send a source location to Sourcetrail

e.g. crtl + right click

Whatever gesture you use, I'm interested in it being the same gesture that I use to switch from Sourcetrail to my IDE (Eclipse). I don't want to have to remember two different gestures depending on which direction I want to go. And the simpler the gesture, the better. Ctrl+rightClick is pretty simple.


Is it possible to animate the size of a bitmapdescriptor?

FEATURE REQUEST / SUGGESTION
Instead of swapping a custom small pin with a custom large pin, is there a way to animate the pin's bitmapdescriptor to increase and decrease in size?
which platform do you want?

[x] Android
[ x] iOS
[ ] UWP

PLATFORMS

[x] Android
[x] iOS
[ ] UWP

No we haven't.
You should implementing animations at yourself.


fetch data working (axios)

fetch data is now also working

@vip32 looks like we had the same idea! :) Take a look at PR #15.

I also changed this to async/await in PR #17.

Yes i was working on getting this template on the same level as the others starters last week. The fetch data component was still open. Seem like it is done now 😃

Do we want to close this one out and go with #17?

I think so since these are really the same changes as #15.

Ok sounds good, closing out!


[Want Help] It's possible to mount the content script in root dom instead of shadow dom?

What is the example you wish to see?
It's possible to mount the content script in root dom instead of shadow dom?
Is there any context that might help us understand?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

Yes, use the root container feature: https://docs.plasmo.com/framework/content-scripts-ui/life-cycle#custom-root-container


Added 1.20.3/4 Support

Added Translations and Item Icons for 1.20.3/4

thx. i took the translations and the changelog.
there were 32x32px images between the 16x16. so i rescaled, tinified the rescaled ones and added them via lfs


HDDS-6525. Add audit log for S3Gateway

What changes were proposed in this pull request?
Currently There is no audit log for S3gateway.
This ticket is to add audit log for S3gateway
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6525
How was this patch tested?
unit test.

@adoroszlai @ferhui Could you help to review this PR?

@adoroszlai Thank you for the detailed review.
Fixed with the comments except the default value one.
I was thinking to compare the value with defaultValue, but seems it's possible for users to use a value same as defaultValue.

Thanks @symious for updating the patch.
There is a compile error after conflict resolution:
Error:  /home/runner/work/ozone/ozone/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/endpoint/BucketEndpoint.java:[114,20] cannot find symbol
  symbol:   variable browser
  location: class org.apache.hadoop.ozone.s3.endpoint.BucketEndpoint

Updated, please have a look.

Thanks @symious for updating the patch.  LGTM.  Can you please resolve the conflict?

@adoroszlai Conflict solved, please have a look.

Thanks @symious for the contribution, @ferhui for the review.

@adoroszlai @ferhui Thanks for the review.


Fixing _sample_trunc_norm so that it works in both Scipy 1.4.0 and 1.5.1 (latest)

This follows the discussion in #107 and implements the backwards-compatible fix. Bumped version to 1.3.8.

Coverage remained the same at 100.0% when pulling 913d535627f80e49df7758a7a1bbd6c8a45fc39c on fix-for-107 into d96622fbfd16e73518b192eaee152af9718147a3 on master.

Tests are passing on travis: https://travis-ci.org/github/justinsalamon/scaper/builds/708983342
@pseeth LGTM, Squash & Merge!


API availability

Hi,
I don't see any documentation about an API to add a node, remove a node, change state, etc...
Thanks in advance

This is Vue so if you modify node structure treeview should be updated automatically


abstraction for storage

It should give you an easier way to implement other storage

the reason i want to entirely move from redis to badger: it's easy to make redis and the app crash (because of OOM), but this is good start tho


internal: remove proc macro management thread

Communication with the proc macro server process has always happened one request at a time, so the additional thread isn't really needed (it just forwarded each request, and sent back the response). This removes some indirection that was a bit hard to understand (a channel was allocated and sent over another channel to return the response).
Hope I'm not missing anything here

bors r+


Calculating route error

When calculating route (via: com.skobbler.ngx.routing.SKRouteManager.calculateRouteWithPoints() by passing a list SKPostion objects consisting of  latitude and longitude values along with SKRouteSettings object) error occures: GPX track navigation is available for commercial use with a enterprise license and JNI DETECTED ERROR IN APPLICATION: jmethodID was NULL..... In new build of Skobbler SDK is it fixed: http://forum.skobbler.com/showthread.php/7563-Latest-2-5-1-Android-build ... Is there any possibility to use this build?

Hi @DaveFCB, thanks for letting me know. Will update asap.

@DaveFCB pushed a fix to the develop branch. If you can confirm it works for you I'll merge it into master.

not working :-( the same error

@DaveFCB, I replaced the SKMaps.jar file and related documentation, so if it is still giving the same error it may not be related to that.

@DaveFCB, Ah, may have not changed the native libs. Hang on will try again.

@DaveFCB, Ok new native lib builds pushed. Let me know if that has solved it.

Problem solved. Thanks a lot!

@DaveFCB Execellent. Thanks for letting me know.


Treat JVM Error as server crash.

Treat detected JVM Error as server crash and start data restore procedure after server restart.

Fixed