Small optimizations to remove_duplicate_points.

Simplify _find_last_point helper function.
Use plain python array for to_be_reduced counters. Using numpy
array seems to cause some conversion overheads when incrementing
the contents and using in a zip iteration.

Current coverage is 100.00%

Merging #303 into master will not affect coverage as of 68b2d84

@@            master    #303   diff @@
======================================
  Files           41      41
  Stmts         1861    1861
  Branches         0       0
  Methods
======================================
  Hit           1861    1861
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 68b2d84

Powered by Codecov. Updated on successful CI builds.

I now realized that I had made changes in this function to make it faster but I forgot to do a pull request! @juanchopanza I  put here the code, in case you would like to use it. I use masks instead of resizing lists:
    @staticmethod
    def remove_duplicate_points(points, groups):
        ''' Removes the duplicate points from the beginning of a section,
        if they are present in points-groups representation.

        Returns:
            points, groups with unique points.

        '''

        def _find_last_point(group_id, groups):
            ''' Identifies and returns the id of the last point of a group'''
            group_initial_ids = np.sort(np.transpose(groups)[0])

            if group_id != len(group_initial_ids) - 1:
                return group_initial_ids[np.where(group_initial_ids ==
                                                  groups[group_id][0])[0][0] + 1] - 1

        to_be_reduced = np.zeros(len(groups))

        # mask of the points that will be returned. Starts as true, i.e. all points
        # will be returned and if a duplicate is found, the respective index will
        # become false
        p_mask = np.ones(len(points), dtype=np.bool)

        for ig, g in enumerate(groups):
            if g[2] != -1 and np.allclose(points[g[0]],
                                          points[_find_last_point(g[2], groups)]):
                # Set duplicate's index to False in order to remove
                # it from the resulting array
                p_mask[g[0]] = False
                # Reduce the id of the following sections
                # in groups structure by one
                to_be_reduced[ig + 1: len(groups)] += 1

        groups = np.array([np.subtract(i, [j, 0, 0])
                           for i, j in itertools.izip(groups, to_be_reduced)])

        return points[p_mask], groups

Is there a way to remove a commit? :P

@eleftherioszisis I tried it out and it didn't really change anything. Probably because it is a large array, because of the loop, and because most of the entries are true. There may be a better way of building the mask, or leveraging numpy to do the removal. But the "bottleneck" in unpacking is now find_group, responsible for about 1/4 of the time spent (so, not even a bottleneck, just one of the dominant components.)

For removing a commit, see here


use conda-package-streaming package

conda-package-streaming is a soon-to-be-released package providing our index/package_streaming and extra features

imported if available or we use our vendored version


Colorize background like in CoenraadS/Bracket-Pair-Colorizer-2

https://github.com/CoenraadS/Bracket-Pair-Colorizer-2:

Native VSCode:

"editorBracketPairGuide.backgroundX" / "editorBracketPairGuide.activeBackgroundX" change only guides color but not actual background color.

editorBracketPairGuide.* is just for the guides, there is a different color setting for the brackets. But you still cannot change the background.

Nice feature, but seems not many people see this

@hediet any way to highlight the bracket self background color same as to bracket color?


Run tests in<EMAIL_ADDRESS>and io.js

Вкусняшеча. Подпишусь

Fix mocks for<EMAIL_ADDRESS>https://github.com/tschaub/mock-fs/pull/18
Fix mocks for io.js: https://github.com/tschaub/mock-fs/pull/21


Fixed several bugs (including #4)

I have fixed several bugs in this Pull Request.
Firstly, I addressed issue #4. I fixed it by doing something similar to what @alex-laycalvert suggested there.
I changed if(focusedItem) to if(focusedItem != -1) in generateStateWithNewFolder and generateStateWithNewFolder (located in FileSystemHelpers.ts). In my opinion, this change is more accurate because item.index will either be -1 or a string. Using if(focusedItem >= 0) would work but is less clear.
Secondly, I addressed some bugs related to PR #22 regarding focusing a file. Since in that PR I changed the structure of the file system item (making the index and the object key the path of the file) it broke some stuff:

It broke dragging and dropping files. I fixed it by adapting the new changes in the helper functions (inside FileSystemHelpers.ts)
In addFile and addFolder functions (located in FileSystem.tsx), the check for the existence of an item was broken because the key is no longer the name but the path. I implemented a new function in FileSystemHelpers.tsx to make this check, now that the name is a property (data) and not the object key.

Important note: I have not yet adapted the handleRenameItem function (located in FileSystem.tsx) to the changes in PR #22. Therefore, renaming will likely be broken when it is implemented. I will make sure to fix it as soon as possible.
I believe these changes have resolved all known issues. However, if any further bugs are discovered, I will be sure to fix them as soon as possible.

I’ll Look into it.

I have fixed the two bugs that you mentioned. The first one was caused by a typo I made in the generateStateWithNewFolder function, where I mistakenly replaced newFolderName with newFileName.
The second bug was caused by the checkIfItemNameIsFolder function, which checked for the existence of files with a certain name throughout the system. I have now modified it to check for items by the provided name under a passed node (path) - in our use case, the focused item. Although I believe that this solution works well for now, we should consider passing the parent node when a folder is opened, not just when it is focused. If this indicator has already been implemented, please let me know.

@yonatanmgr I fixed the last bugs, and made some changes. The main change I did is that generateStateWithNewFile, generateStateWithNewFolder and itemExistsInParent (which is the new version of checkIfItemNameIsFolder, more about that below) now relate to the selectedFolder and not focusedItem. Other changes I made:

Recreated checkIfItemNameIsFolder as itemExistsInParent. It is pretty much doing the same, but now correct and more concise. Reference the comments in the function for more information.
Shortened generateStateWithNewFile and generateStateWithNewFolder. The first if check in those functions was redundant, since it was looking for the parent's path, which we don't need to look for now, as it is the key (or index).


#238 metrics grouping for report generation

Adding groups for metrics for report, idea #238.

@yegor256
I have completed work on the first version of the metrics grouping.
Currently, groups are defined within the metrics generators in the following format:
METRIC_NAME METRIC_NUMBER [GROUP_NAME] METRIC_DESCRIPTION

If a metric does not belong to any group, the [] must be omitted.
To implement grouping, I made changes to steps/report.sh:

It automatically finds all existing groups, including one labeled "Ungrouped Metrics."
It generates structured-list-of-metrics.tex using a predefined template.
It removes [GROUP_NAME] from the .tex file.
It overwrites the original list-of-metrics.tex.

Current metrics view from report

@Raleksan looks very good! Please, check the reports of our CI workflows. Also, see my comment above.

@yegor256
I think it's all for steps/report.sh.
Now it's worth thinking about tests, but I was unable to come up with something appropriate that wouldn't require me to implement similar logic from script but inside a test now. Any ideas?
p.s. Sorry for unclear commit history and several force push. I was a little in rage to shellcheck until I remembered that I have it in local Docker container.

@Raleksan in this PR, you didn't change the output of any metrics-generating scripts. Maybe it's worth doing that, in order to make sure your grouping works correctly?

@yegor256
I implemented a test for metrics grouping.
The process works as follows:

A script for testing metrics is created.
The steps/report.sh script is executed.
The report.pdf is converted to report.txt.
All test groups are verified for existence.
Each metric is checked to ensure it is placed within the correct group.

@Raleksan thanks!


Documentation on using a separate project for migrations not very clear and hard to follow

Please make the documentation a bit clearer and provide a full sample code.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b545eeff-6c33-3cc0-09ce-a3ad342d7438
Version Independent ID: 34bc1bac-7338-d8ab-390d-8c5e88a48c10
Content: Migrations with Multiple Projects - EF Core
Content Source: entity-framework/core/managing-schemas/migrations/projects.md
Product: entity-framework
GitHub Login: @bricelam
Microsoft Alias: bricelam

@whizkidwwe1217 Can you provide some details as to where it was unclear and/or hard to follow?

@ajcvickers I have a hard time understanding step 5. Does it mean I should reference the Migrations assembly to the Startup project?

@whizkidwwe1217 Yes.

Hi, step 5 really isn't very clear. When I read it I thought won't that create a circular ref, then read a little further and that is mentioned with a suggested fix.
However, that process always creates a circular ref which in vs community at least, isn't possible - an error dialog informs us of this.
Applying the fix seems to work, at least if you leave the model classes in the original project which defeats the object, but still a circular ref cannot be added which is confusing because the docs suggest this is required. If you move your model to the class library the need for that ref becomes apparent.
And there is no way round that, the project won't compile without the circular ref which can't be added.
Or did I not I miss something.
Either way it's confusing.
Thanks
Steve


Fix for double border card header + list-group

fixes the doubled up border when a card-header precedes a list-group
fixes #21609

.card-header + .list-group > li:first-child,
.card-header + .list-group > a:first-child {
  border: 0;
 }

This fixes the .list-groups with links too.

@royklutman added your suggestion 👍

Tweaked the CSS and selector just now. Demo at https://codepen.io/emdeoh/pen/KvoqxZ.


Add support for .NET 8

Changes
Adds build and test runs for .NET 8.
Merge requirement checklist

[ ] Unit tests added/updated
[x] CHANGELOG.md file updated for non-trivial changes
[ ] Changes in public API reviewed (if applicable)

Merging now, as 1.6.0-beta.3 upstream instrumentation libraries depend on using 8.0.0 libraries: https://www.nuget.org/packages/OpenTelemetry.Instrumentation.SqlClient/1.6.0-beta.3#dependencies-body-tab


Investigate why benchmarks became worse with RLST upgarde

as well as impact of threading control.

Superseded by explicit SIMD improvements.


tour: fmt.Println("Hello, foo.") causes 'process took too long'

Context: https://tour.golang.org/welcome/1
This specific code causes a process took too long error.
package main

import "fmt"

func main() {
	fmt.Println("Hello, foo.")
}

indent must be a tab, msg must be "Hello, foo."  I haven't bothered trying all other combinations, but altering the string or indenting with spaces does not cause the error.

Hi,
is the issue still seen ?
BR.


Execution stopped error

Hi, I was trying CSBB on my Mac today. When I tried running any module using the Sample_File I get the following error:
Running R in Background (please be patient).....
Excecution Stopped because of errors ... Please See Possible Errors Section of README or Contact CSBB for bugs and issues
perl version is 5.18.2
R is 2.5.0  GUI 1.19
pandoc and python 3.5.2 are installed
Any ideas?

An update on the error using the Sample_File.txt:
I updated R to the latest 3.3.1 and tried again.  Here is the error:
Running R in Background (please be patient).....
Error in file(file, "rt") : cannot open the connection
Calls: as.matrix -> read.table -> file
In addition: Warning message:
In file(file, "rt") :
cannot open file 'Sample_File.txt ': No such file or directory
Execution halted
Excecution Stopped because of errors ... Please See Possible Errors Section of README or Contact CSBB for bugs and issues
I dragged and dropped the file to insert the path as directed
Nick

Hi Nick,
Hope you are doing fine. when you dragged the file from finder window in Mac there is space that comes at the end. Can you try removing the space and run again. It will definitely run.
Sorry the slow response. I was out of town.
Thanks,
Cheers !!
SkyGenomics

Hi,  that did the trick.  Thanks for the info on the extra space.
Nick

Nicholas Webster, Ph.D., M.A.
Professor of Medicine
Chief, Division of Endocrinology and Metabolism
Associate Director for Shared Resources, Moores Cancer Center
University of California, San Diego
9500 Gilman Drive
La Jolla CA 92093
On Jul 11, 2016, at 10:06 AM, Sky Genomics <notifications<EMAIL_ADDRESS>wrote:
Hi Nick,
Hope you are doing fine. when you dragged the file from finder window in Mac there is space that comes at the end. Can you try removing the space and run again. It will definitely run.
Sorry the slow response. I was out of town.
Thanks,
Cheers !!
SkyGenomics
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/skygenomics/CSBB-v1.0/issues/1#issuecomment-231798582, or mute the threadhttps://github.com/notifications/unsubscribe/APYDXOPFxkpQPh0p7De323RaYRDQTRZjks5qUngbgaJpZM4JHcG-.

Hi Nick,
Awesome that CSBB is working now. Hope you like the tool and do suggest us with any ideas you have and which you want as a module in CSBB.
Thanks,
Cheers !!
Praneet Chaturvedi
Analyst Bioinformatics
CCHMC, Cincinnati, OH


Support for New relic

Graphs with metrics would be great, also system/app status could be updated automatically.

@andrefrcastro can you explain this a bit more please? :)

New relic provides metrics and important information on how the app is performing, such as response times (would be cool for graphs), error rates, alerts of downtime and other events, throughput, etc

Looks like Newrelic supports webhooks, is this something you can implement via that method?

I guess so. The API would also be helpful for the metrics such as response time: https://docs.newrelic.com/docs/apis/rest-api-v2/requirements/new-relic-rest-api-v2-getting-started
Some demos: http://data-api-demo.newrelic.com/

This isn't something that Cachet will be doing for now, because we'd have to build a whole provider system for the API.

Use web hooks to get some of the data out. I believe that you can set what data to send to the web hook, so this is your best bet.
Setup some kind of proxy to get the data out of Newrelic into Cachet.

Perhaps in the future we'll do this, but not right now as it should be possible to get enough out currently :)


feat: add curveusd actions and tests

big commit

@yippee-ki-yay pls add to addresses/mainnet.json


Failing with cryptic error in rspec test

      preview_circle = Circle.preview_circle
      expect(preview_circle).to be_a(Circle)
      ap preview_circle

The above succeeds without the ap line, and fails with it with error below. Note that the preview_circle method accesses an env var:
  def self.preview_circle
    @preview_circle ||= find_by(id: ENV.fetch('THREADABLE_PREVIEW_CIRCLE_ID', nil))
  end

Error:

Was on our end...


fix: moves auro library to dependencies in package.json #261

Alaska Airlines Pull Request
Moves Auro Library into dependencies from devDependencies to avoid installation issues, as originally reported in #573.
Resolves: #261
Summary:

Moved to dependencies within package.json
Regenerated package.lock
Verified build and test ran successfully

Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

 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.Chris Friedberg seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


What is the best practice to no-down-time upgrade OLM itself?

A.T.,
We are looking for a way to keep OLM itself updated, for example, we have 0.18.1 running and now we want to update OLM to 0.18.3,  how can we do this without turn down the services running on top of OLM?
let me know if any other context needed, thanks a lot!

Can you elaborate how the services depend on OLM and what makes the update of OLM itself noticeable? An OLM update is a fairly straight replacement of controllers with new images, the "down time" is really just time in which objects will not be reconciled and that should be rather short.

Can you elaborate how the services depend on OLM and what makes the update of OLM itself noticeable? An OLM update is a fairly straight replacement of controllers with new images, the "down time" is really just time in which objects will not be reconciled and that should be rather short.

Thanks for replying, one of examples is that we implemented a software self upgrade web UI based on InstallPlan, aka, a service is detecting the crd installPlan,  if there is an approved installPlan and  a installed CSV with same version, we show an entry to the UI that this version was installed. If there is an unapproved installplan, we show an entry to the UI that there is a newer version available, and then the UI can approve the install plan to install new version.
As you can see, the feature is based on CRD "installplans.operators.coreos.com" and "clusterserviceversions.operators.coreos.com" that are part of OLM, if we uninstall the OLM and re-install OLM, I think the resources will be deleted since the CRD was deleted and re-installed, let me know if I am missing anything.


No reading zone in logic factories and constructors

class CounterLogic {
  @prop value = 0;
  inc = () => (this.value += 1);

  constructor() {
    console.log(this.value);
  }
}

let n = 0;

const Counter = observe(() => {
  const { inc } = useLocal(CounterLogic);

  console.log("Render", n++);

  return <button onClick={inc}>+</button>;
});

export const App = () => <Counter />;

Edit on CodeSandbox
The component was subscribed to value and reacted the first time on It change, but not used inside.

https://github.com/betula/realar/blob/9168812ceb0195567945768161fd3c27ca23de3b/tests/use-local.test.tsx#L50


Style/TrivialAccessor allows predicate methods by default

This should cut down on the number of duplicate issues being raised on GitHub.

Just shoehorned a bugfix in here.

Apart from the failing build - both changes should have changelog entries.

Apart from the missing changelog entry or two, everything looks good. Rebase and we're good to merge.

Added missing changelog entry. Rebased.


created failing bazel run for js_image_docker e2e test

Slack link: hood.slack.com/archives/C02EFH1DJJK/p1691190028876829?thread_ts=1691093043.641909&cid=C02EFH1DJJK
This PR creates a failing test case in order to reproduce an issue where bazel/docker can't resolve symlinks in pnpm node_modules.
Type of change
Red PR
Test plan
Covered by existing test cases

 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.


Alphabetical Order XSLT

For the locations in the chapter I currently have:

This statement outputs at least 2/3 of the locations into alphabetical order with no repeats so I know the other functions are working correctly. The other 1/3 of the locations is definitely out of order at the end of the list because of the white spaces.
I have tried:

and it stops outputting after Chapter 1 heading in the table. The problem is that normalize-space cannot handle more than one string like the other functions. When written without an inputted string as normalize-space() it uses the string value of the context node, in this case 'heading'.

This outputs the entire heading tag where I want the list of locations.
Does anyone know how to use normalize-space in this context?

@alexvanwoert You’re on the right track here with identifying the problem. normalize-space() cannot take in a sequence of more than one. It needs to be run first, before the other functions, and it needs to run on just one node at a time. For this, use simple map ! rather than the arrow operator =>

Got it! Thanks.


Update chainercv in GCP chainer-latest-cu92-experimental image

Currently, in the Google Cloud Platform, in the deeplearning-platform-release project, the chainer-latest-cu92-experimental image has:
chainer - 5.3
chainercv - 0.11
What is the usual time-frame/method for updating those images to the latest version?
Edit: Here is a history of the updates on the images.

Thank you so much for pointing this out. We will check this out.


Directly access GPRMC NMEA data as retrieved from parser.

Codecov Report

Merging #17 into master will decrease coverage by 0.23%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage   94.20%   93.96%   -0.24%
==========================================
  Files           5        5
  Lines         207      199       -8
==========================================
- Hits          195      187       -8
  Misses         12       12

Impacted Files
Coverage Δ

src/ArduinoNmeaParser.h
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[Bug] 使用面具GitHub Copilot时，其模型会自动选择GPT-4，设置中的无效，且切换也无效。导致费用严重超预期。

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Deployment

[ ] Docker
[ ] Vercel
[ ] Server

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional Logs
Add any logs about the problem here.

you can changed it manually

or changed it by clicking this a icon bots

tested working fine:

感谢您的回复，按照您所说的操作步骤，是没有问题的。但在右侧总设置中切换模型版本，目前测试的，GitHub Copilot不会响应切换，而其他的面具则没有问题。如下：

谢谢！

bruh this not a bug or something that you thinking
look this when you disable a gpt-4 in env it will automated switch to other models which is available
https://github.com/Yidadaa/ChatGPT-Next-Web/assets/17626300/19a49e3c-59a1-4700-b317-08379068089c
also in setting are just add this (if don't want set gpt-4 disable in env, because it will disable for all gpt-4)


Improve UX when $IPFS_PATH/api exists and API is offline

The $IPFS_PATH/api file is used by a lot of developers to talk to remote nodes  (learning from ipfs-companion users). T
How to improve UX for "the API defined in $IPFS_PATH/api is offline" scenario?
Perhaps like this:

IF $IPFS_PATH/api file exists and is different from the one in the config file
AND IF multiaddr inside of api file points at remote API  which produces ECONNREFUSED error,
THEN ipfs-desktop should inform user about the problem with connection to remote node at {multiaddr} and display error window with built-in UI for dealing with it.

It could be a styled window similar to this mockup but with nice UI to:

(A) Change value in api file

open file with $EDITOR or provide built-in editor directly in the error window similar to what ipfs-webui does

(B) Run ipfs repo fsck

to remove api and potential lockfiles and try again (should be safe, technical user can always restore file by hand)

(C) Quit

Reminder to self: https://github.com/ipfs-shipyard/ipfs-desktop/pull/711#pullrequestreview-178054088.

(updated description to reflect what we learned during today's sync call)

I believe we can close this now as #722 was closed!

Just tested master @ 3b7c7812fa4ff717c4e16317ae6deefb5242c7e1  and having an empty $IPFS_PATH with api file alone produces this error:
Error: ENOENT: no such file or directory, open '/home/lidel/.ipfs/config'

@lidel that error might be caused by this line which will be removed as soon as the CORS PR (#738) is merged 😄 So it won't be a problem as we won't be testing the existence of any files.

That case is already solved. I'm closing this for now since we've already added the necessary logic for the scenarios here described.


Suggested path for JsonSchema.Net integration

This branch is my recommended approach for using JsonSchema.Net.  It will require a few paradigm shifts for the internals of OpenApi.Net, but these changes are necessary to take full advantage of what JsonSchema.Net has to offer.
Opening this as a draft as it's not nearly ready and so that we can discuss the changes.
I think with the approach I have here, we can completely remove the Readers library.

We using this deserialization pattern extensively in our SDK generation and are able to parse unrecognized properties into a dictionary without any problem. - @darrelmiller

My concern was less about unknown keywords and more about keywords defined in custom vocabularies, which, if you're supporting 2020-12, you will need to be able to support somehow, probably through some extension mechanism where people can define their own keyword implementations.


Dropdown for Foreign Key

I would like to manage a foreign key column with a dropdown and have the ID field hidden from the user.
Say the smart table shows invoices and an invoice has a column "CustomerId". Then I want to see  the customer name (not ID) in view mode as well as all customer names (not IDs) in the dropdown.
Sounds like a common scenario but can't see it done anywhere in smart table samples or blogs.

I have the same problem @stratdaz


(cask): change cask template url ' to " to allow string interpolation on version

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Summary
changed the line for url from single quote ' to double quote "
Fixed issues
with the current templeate i get a:
  url 'https://github.com/joshwcomeau/guppy/releases/download/v#{version}/Guppy-#{version}.dmg'

and this error:
Error: Cask 'guppy' definition is invalid: 'url' stanza failed with: bad URI(is not URI?):
https://github.com/joshwcomeau/guppy/releases/download/v#{version}/Guppy-#{version}.dmg

brew tests are failing here; can you try to fix the error? Thanks!

Thanks so much for your contribution!  You rock, @muescha!


imputing across conditions vs within conditions

Thank you so much for your creation of this wonderful tool. I am brand new to analyzing mass-spec data, and have trying to get my head around how to best analyze my data.
I’m performing analyses on phosphorylation data obtained from TimsTOF mass-spec. I have n = 5 for each condition.
I have 3 conditions that I expect to vary quite widely in their phosphorylation status between the 3 conditions.
When I do the imputation, I’m mostly curious about the calculation of the coefficient of variation and how the imputation is done on a condition wide basis.
If I upload my samples with all 3 conditions in one sheet and one sample, many more phospho-peptides are filtered out compared to if I input the samples as imputing on samples just from condition A, and then impute just from condition B, and then just C alone.
If I biologically expect that the peptides should vary quite a bit between conditions, would it make sense to impute each condition alone? Or does the tool work better if I impute with all samples.
I also sent an email asking the same question

Hi aleighbrown,
I think the situation you describe is normal. The reason that many more phospho-peptides are filtered out when you impute across 3 conditions may be caused by the parameters (i.e. NA ratio, CV threshold (raw scale)). As described in this tool, any protein/peptide with (NA ratio or CV) above the threshold will be removed. Therefore, for example, the CV of one protein/peptide from condition A or B is below the threshold, but above the threshold from condition C, this protein/peptide will be remained in the condition A or B, while it will be removed across 3 conditions.
So please check you data and adjust the parameters (Perhaps you could set NA ratio or CV a little larger for your data when you impute across 3 conditions). BTW, in my opinion, you could impute each condition alone or together. Both are reasonable.
Bests,
Shisheng
West China Hospital


Extend Support Matrix and Document Usecases

The project aims to extend KubeArmor support and document how KubeArmor is relevant for securing Kubernetes on Edge in addition to generic Kubernetes based Application deployments

Expected Outcome:

Try KubeArmor on Different Kubernetes Platforms

Microshift, k0s
Make fixes to deployments to make them work if needed

Document Usecases on these platforms
Document Usecases at a broader level for EDGE and Container Security
Produce Blogs about extended support and additional usecases

Ref #1325 #1318

This project is Lfx mentorship project  ?
I am interested in this project and i would like to work on this can @daemon1024  assign to me

Hi @daemon1024
lam planning to apply for this project for the LFX mentoring program. Are there any resource recommendations you have or approaches that the KubeAmor team follows so that I can learn more about the subject and help better?

Hi @daemon1024, I wanted to contribute to this project. Can u share the resources from where to learn?

Hello, my name is Ashutosh. I am a Google Summer of Code Mentee in Jenkins and I have experience with DevOps, Docker, Jenkins, Git, and Github. I am interested in contributing to this project. In the coming days, I will be developing a proposal. Thank you.

Hello, @daemon1024  I am interested in applying for this project under this LFX term
If you could clarify some of my doubts it could be great help
How will identified issues on Microshift and k0s be reported and tracked?
How will container security use cases be distinct from generic Kubernetes security use cases?
Will KubeArmor be compatible with all edge Kubernetes platforms?

Hello, @daemon1024 I am interested in applying for this project under this LFX term If you could clarify some of my doubts it could be great help
How will identified issues on Microshift and k0s be reported and tracked? How will container security use cases be distinct from generic Kubernetes security use cases? Will KubeArmor be compatible with all edge Kubernetes platforms?

Hello, @daemon1024 I am interested in applying for this project under this LFX term
If you could clarify some of my doubts it could be great help
How will identified issues on Microshift and k0s be reported and tracked?
How will container security use cases be distinct from generic Kubernetes security use cases?
Will KubeArmor be compatible with all edge Kubernetes platforms?

How will identified issues on Microshift and k0s be reported and tracked?

I don't understand the question? We want to test our compatibility with these platforms and make them work. Once it starts working, we just track issues on the KubeArmor repositoru.

How will container security use cases be distinct from generic Kubernetes security use cases?

KubeArmor is Container and VM Runtime Security Engine, I am not sure what this question means. You can check out our current documents to understand how it does it better https://github.com/kubearmor/KubeArmor#documentation-notebook

Will KubeArmor be compatible with all edge Kubernetes platforms?

KubeArmor support largely depends on availability of Linux Kernel Primitives available. We cannot gurantee compatibility with all platforms in general. But any supported Linux Kernel should mostly gurantee KubeArmor working.

Hello! I am Vishal Raj, a final year CSE student. The CNCF - KubeArmor project excites me as it aims to extend support and document use cases for securing Kubernetes on Edge and generic Kubernetes-based applications. I'm eager to contribute to this project and help try KubeArmor on different platforms like Microshift and k0s. Additionally, I'll work on fixing deployments if needed and documenting use cases at a broader level for EDGE and Container Security. As part of my contribution, I'll produce blogs about the extended support and additional use cases. Let's collaborate to enhance KubeArmor and make Kubernetes environments more secure!


version compatibility with almond-sh on windows when use spark

I'm facing a problem with version compatibility when use spark with almond-sh kernel on windows.  I tried many times with different version but not succeed (i also tried check compatibility table). What version i should choose for these

coursier (tried: 2.1.2, 2.1.5)
almond-sh (tried: 0.10.9, 0.13.0, 0.13.1, 0.13.14)
scala (tried: 2.12.10, 2.12.15 (wanted = scala build spark) )
spark = 3.2.2 build for hadoop 2.7.4 use scala 2.12.15
java = 1.8.0_121

CLI
bitsadmin /transfer downloadCoursierCli https://github.com/coursier/launchers/raw/master/coursier "%cd%\coursier"
bitsadmin /transfer downloadCoursierBat https://github.com/coursier/launchers/raw/master/coursier.bat "%cd%\coursier.bat"

coursier bootstrap --hybrid almond:**<version>** --scala **<version>** -o almond
almond --install --force
jupyter kernelspec list
jupyter-lab (to use kernel)

Thank you

@alexarchambault  can you help me bro, i still can't resolve this problem for 5 month :D


Pull Private Huggingface Model

Hi, so I believe it's now possible to pull huggingface models directly by prepending hf.co to the pull statement. I would just like to get clarity on how this works with private models? I have my huggingface token set as an environment variable, but I can't seem to pull a private model.

same problem.

Same problem here for private models!
pulling manifest
Error: pull model manifest: Get (...): unsupported protocol scheme ""


Load tests on background

Seems like tests library is being loaded directly in UI thread. Loading bigger test suite causes it to not responding to commands and eventually into not responding state.
I can imagine that tests list will be updated as data comes with some progress info if possible.

@ParanoikCZE It's a good point. Are you building from source or using the chocolatey package?
Also, do you notice the problem only when loading inprocess? This seems likely if we are interfering with the UI thread.

Used compiled version .. https://github.com/CharliePoole/nunit-gui/releases/download/0.4/NUnit-Gui-0.4.zip
I wasn't playing a lot as we are using mostly console runner, So I've loaded our suite (over 2500 tests) and ran few of them. Issue is related only to loading test dll.

The 0.4 release runs tests in a separate process by default, so it can't actually be loading on the gui thread but the notifications may be blocking for some reason.

Alternatively, we do some in-process examination of assemblies in order to decide how to load them. That could also be the source of the problem.

ok, I think this is more likely caused by generating test tree. Same UI lock happens when I switch to test list and then back to NUnit tree.

That's a good hint. I'm on vacation this week, but I'll check it out when I get a chance. There's no reloading going on in that situation, but the entire tree - not just the visible portion - is generated before anything is displayed. We probably need to be a bit smarter about it.

I'm having the same problem, using the 0.5 version. I'm loading over 50k tests and when loading the .dll the GUI freezes and eventually goes to Not Responding state


Wasm element offset to support global initexprs

Updating WASM elements implementation.
Adding support for offset to use globals as initexprs
Closed #1872

This change is

@dotnet-bot test Windows x86_debug please

@Cellule @MikeHolman please review.

Reviewed 15 of 15 files at r1.
Review status: all files reviewed at latest revision, 10 unresolved discussions, some commit checks failed.

lib/WasmReader/WasmElementSegment.cpp, line 27 at r1 (raw file):

    {
        Assert(m_numElem > 0);
        if (m_limit > module.GetTableSize())

m_limit is not calculated yet, this check doesn't make sense.

lib/WasmReader/WasmElementSegment.cpp, line 32 at r1 (raw file):

        }

        m_offset = module.GetOffsetFromInit(*m_offsetExpr); // i32 or global (i32)

This is done too soon. Globals can be imported, thus the offset must be resolved at linking time. ie: at the last possible moment before instantiating the table.

lib/WasmReader/WasmElementSegment.h, line 26 at r1 (raw file):

        const WasmNode* m_offsetExpr;
        UINT32 m_numElem;
        UINT32 m_offset;

Since Globals can be imported, you cannot calculate the offset and the limit at compile time. We should just hold on to the elements information and do the checks at linking time.

lib/WasmReader/WasmModule.cpp, line 25 at r1 (raw file):

    m_exportCount(0),
    m_datasegCount(0),
    m_elementsegCount(0),

please initialize the array to nullptr also since there are code path that won't initialize it

lib/WasmReader/WasmModule.cpp, line 334 at r1 (raw file):

    if (initExpr.op != wbI32Const && initExpr.op != wbGetGlobal)
    {
        throw WasmCompilationException(_u("Only int32.const supported for element offset"));

Change that message to Invalid init_expr for element offset

lib/WasmReader/WasmModule.cpp, line 348 at r1 (raw file):

        }
        WasmGlobal* global = this->globals.Item(initExpr.var.num);
        Assert(global->GetReferenceType() == WasmGlobal::Const);

Just in case, could you include that assert in the next check and throw an error if the value of the global is not resolved

lib/WasmReader/WasmModule.cpp, line 408 at r1 (raw file):

    if (index >= m_elementsegCount)
    {
        return nullptr;

Unless we have explicit checks for nullptr after calling this, I would prefer throwing an exception in this case

lib/WasmReader/WasmModule.h, line 1 at r1 (raw file):

//-------------------------------------------------------------------------------------------------------

Just a heads up, that file is disappearing in #1821 depending on which PR goes in first you might have to deal with it.

lib/WasmReader/WasmModule.h, line 77 at r1 (raw file):

        void AllocateElementSegs(uint32 count);
        void AddElementSeg(WasmElementSegment* seg, uint32 index);

nit: Since you give the index this would be more SetElementSegment

test/wasm/table.wast, line 10 at r1 (raw file):

  (type (func (result i32)))

  (global $a i32 (i32.const 6))

Could you add a test where the global is imported

Comments from Reviewable

lib/WasmReader/WasmModule.h, line 1 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> Just a heads up, that file is disappearing in #1821 depending on which PR goes in first you might have to deal with it.

Thanks for pointing this out. Will take care.

Comments from Reviewable

lib/WasmReader/WasmElementSegment.h, line 26 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> Since Globals can be imported, you cannot calculate the offset and the limit at compile time. We should just hold on to the elements information and do the checks at linking time.

This answers a lingering question I had. The new design was actually to address this if needed. Will make the necessary changes.
Thanks for pointing this out.

Comments from Reviewable

lib/WasmReader/WasmModule.cpp, line 25 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> please initialize the array to `nullptr` also since there are code path that won't initialize it

Missed that. Done.

Comments from Reviewable

lib/WasmReader/WasmModule.h, line 77 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> nit: Since you give the index this would be more `SetElementSegment`

Is there any reason for not using lists in WasmModule containers to get rid of the indices altogether?

Comments from Reviewable

@Cellule please have a look.

Review status: 7 of 16 files reviewed at latest revision, 10 unresolved discussions, some commit checks failed.

lib/WasmReader/WasmElementSegment.cpp, line 27 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> `m_limit` is not calculated yet, this check doesn't make sense.

Done.

lib/WasmReader/WasmElementSegment.cpp, line 32 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> This is done too soon. Globals can be imported, thus the offset must be resolved at linking time. ie: at the last possible moment before instantiating the table.

Done.

lib/WasmReader/WasmModule.cpp, line 334 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> Change that message to `Invalid init_expr for element offset`

Done.

lib/WasmReader/WasmModule.cpp, line 348 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> Just in case, could you include that assert in the next check and throw an error if the value of the global is not resolved

Done.

lib/WasmReader/WasmModule.cpp, line 408 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> Unless we have explicit checks for `nullptr` after calling this, I would prefer throwing an exception in this case

Done.

lib/WasmReader/WasmModule.h, line 77 at r1 (raw file):
Previously, arunetm (Arun Purushan) wrote…
> Is there any reason for not using lists in WasmModule containers to get rid of the indices altogether?

Done.

test/wasm/table.wast, line 10 at r1 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> Could you add a test where the global is imported

Done.

Comments from Reviewable

Reviewed 9 of 9 files at r2.
Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

lib/WasmReader/WasmElementSegment.cpp, line 60 at r2 (raw file):

    WasmElementSegment::GetElement(const UINT32 tableIndex) const
    {
        if (m_offset > tableIndex || tableIndex >= m_limit)

We should add a boolean that says if we resolved the offset and throw here if it isn't set

lib/WasmReader/WasmModule.h, line 77 at r1 (raw file):
Previously, arunetm (Arun Purushan) wrote…
> Done.

Lists have bigger overhead and we try to use them only if needed.

test/wasm/table.js, line 13 at r2 (raw file):

const blob1 = WScript.LoadBinaryFile('table.wasm');
const moduleBytesView1 = new Uint8Array(blob1);
var a1 = Wasm.instantiateModule(moduleBytesView1, {"m" : a}).exports;

I think it would be clearer in the context of this test to do
var a1 = Wasm.instantiateModule(moduleBytesView1, {"m" : {x : 10}}).exports;

and do not load global.wasm

test/wasm/table.js, line 27 at r2 (raw file):

print(a1.call(9));

//global offset

This is actually the imported global

Comments from Reviewable

@Cellule, incorporated the latest review changes.

Reviewed 4 of 4 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

lib/WasmReader/WasmElementSegment.cpp, line 60 at r3 (raw file):

    WasmElementSegment::IsOffsetResolved() const
    {
        return (m_offset == UINT_MAX || m_limit != UINT_MAX);

I don't think we can use UINT_MAX, if someone defines an empty segment at offset UINT_MAX,
We would have m_offset == UINT_MAX and m_limit == UINT_MAX and it would be valid.
Plus, the check above is erroneous it should be
m_offset != UINT_MAX && m_limit != UINT_MAX

lib/WasmReader/WasmElementSegment.cpp, line 66 at r3 (raw file):

    WasmElementSegment::GetElement(const UINT32 tableIndex) const
    {
        AssertMsg(IsOffsetResolved(), "Cannot access table elements before resolving their offsets.");

Make this a runtime check and throw exception if not true

Comments from Reviewable

lib/WasmReader/WasmElementSegment.cpp, line 60 at r3 (raw file):
Previously, Cellule (Michael Ferris) wrote…
> I don't think we can use UINT_MAX, if someone defines an empty segment at offset UINT_MAX,
> We would have `m_offset == UINT_MAX` and `m_limit == UINT_MAX` and it would be valid.
>
> Plus, the check above is erroneous it should be
> `m_offset != UINT_MAX && m_limit != UINT_MAX`

Fixed

Comments from Reviewable

Reviewed 2 of 2 files at r4.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


GL default backbuffer parameters aren't stored per-context

Description
Our game was developed with UE4 on Android platform. After creating three main GL contexts, the Engine will create other three GL contexts to precompile shaders during the boot process. Considering performance requirements, the contexts used for precompiling did not contain depth buffer and stencil buffer. Unfortunately, RenderDoc would overwrite the main GL context's init params with the one used for precompiling during the capture, which caused the depth test did not work in the replay.
Add depth bits validation counld avoid the main GL context's init params being overwritten.
// ===========================================
// FILE: gl_driver.h
// LINE: 125

// Declare a flag to check if init params has been set
bool m_InitParamHasSet = false;

// ===========================================
// FILE: gl_driver.cpp
// LINE: 937
// FUNC: void WrapperOpenGL::CreateContext(...)

// check DepthBits here to avoid the main context's init params being overwritten.
if (!m_InitParamHasSet ||  initParam.depthBits != 0)
{
    m_InitParams = initParams;
    m_InitParamHasSet = true;
}

But to solve this problem from roots, it may need multiple GL contexts support.
Environment

RenderDoc build: 2018-08-14 nightly build.
Operating System: Windows 10 and Android 8.0
API: OpenGL ES

This should now work correctly, I tested with a program that created two windows, one smaller and with no depth buffer, but the first window created still had the proper backbuffer properties and dimensions.


Stack Overflow

Greetings, I had a stack overflow exception occur with the IDE and reported here:
https://developercommunity.visualstudio.com/t/Visual-Studio-Fall-Down-Go-Boom-due-to-A/10702431
Visual Studio team is saying this is due to this extension, so I am reporting here for next steps.  Please let me know the best way to send the minidump to you and I will assist. 👍

Hi Mike,
Sorry to hear about the issues you encountered with AsyncApostle. You can either attach the minidump here or email it to<EMAIL_ADDRESS>with any additional information and we'll take a look at the issue.
Thanks!

Thank you for the quick reply @FXZFun!  I have sent you the file which turns out is a DMP and not a mini-DMP.  Please let me know if any further information is required and I will assist you.

Erm wait, maybe it is a mini-dmp after all 😅

I'm not getting much information out of the DMP file, do you know what you were doing at the time of the crash? I noticed that you are still using v2024.1.1, so you could try updating to v2024.2.1.

Unfortunately, I do not @FXZFun as it was 3 months ago.  I didn't learn that your extension was involved until today. 😬  Can you confirm that you do see a stack overflow as Visual Studio is reporting?  If you are unable to determine the issue that is OK and we can close this ticket.

I don't have much experience debugging DMP files, so I may not be loading it correctly, but I'm not finding any information about what caused the overflow in the trace. I do see what looks like an overflow but no information about it. I am happy to look into it, but if you haven't experienced the issue recently, I think we can close this for now.

Works for me @FXZFun 😃


Add web UI manual build note

Hi,
I am new to Kythe and I was following the documentation here and I faced some problems with web/ui and visualizing cross-references and found that it needs to be built manually (after some time).
I think it would be great if the documentation mentions that web/ui needs to be built from source first before visualizing.

@googlebot I signed it!

This is fine, but the reason web/ui was removed from the distribution is that it is unsupported and unmaintained.


Add "main" to package.json

First up, a HUGE thank you for putting this project out. I've just integrated it into a big project of mine and it worked perfectly on the first run. I had previously been using a hack with patch-package, and was stuck on Tailwind 3.1. I'm very impressed that you were able to figure this out, given the official way of running tw in the browser is not open source.
Without this small change to package.json I get errors running tests (with vitest) after adding jit-browser-tailwindcss to my project. I'm not a big expert on the insane world of JavaScript modules, so maybe you'll tell me there's a reason this "main" config should not be there. I honestly have no idea!

@mhsdesign thanks for the awesome package. Ran into the same issue, can you merge this in?

Thanks for all the nice feedback glad that it can be of some help ;) Will merge and tag a new release ;)


How can we load Certificate Signing Request using x509certificates?

How can we load Certificate Signing Request using x509certificates?
From a Certificate Signing Request as below:
Example:
-----BEGIN CERTIFICATE REQUEST-----
MIIClDCCAXwCAQAwTzELMAkGA1UEBhMCVk4xEDAOBgNVBAMMB2RldmljZTMxCjAI ...
-----BEGIN CERTIFICATE REQUEST-----
I am using system.security.cryptography.x509certificates, I would load it as a CertificateRequest/X509Certificate2 object to create new certificate from Certificate Signing Request.
Anyone who know how to do?
Detail
Input:

self signed certificate as a CA
certificate signing request
My code

string rootCA = ""; // root certificate
string scrString = ""; // certificate signing request
byte[] rootRawData = Convert.FromBase64String(rootCA);
X509Certificate2 rootCert = new X509Certificate2(rootRawData);
var generator = X509SignatureGenerator.CreateForRSA(rootCert.GetRSAPrivateKey(), RSASignaturePadding.Pkcs1);
byte[] scrRawData = Convert.FromBase64String(scrString);
X509Certificate2 scrDeviceCert = new X509Certificate2(scrRawData); ------> ERROR: : 'Cannot find the requested object.'
CertificateRequest scrDeviceReq = new CertificateRequest(scrDeviceCert.IssuerName, scrDeviceCert.PublicKey, HashAlgorithmName.SHA256);
var deviceCert = scrDeviceReq.Create(rootCert.IssuerName, generator, DateTimeOffset.UtcNow.AddDays(1), DateTimeOffset.UtcNow.AddDays(6), new byte[] { 1, 2, 3, 4 });

It's not currently possible, this is tracked as https://github.com/dotnet/runtime/issues/29547.
You could manually do it with the new System.Formats.Asn1 library, to manually interpret the CSR and recreate it as a CertificateRequest, just with all the caveats already called out in the feature tracking issue.


Add option to add identity block to an Automation Account

Overview/Summary
Replace this with a brief description of what this Pull Request fixes, changes, etc.
This PR fixes/adds/changes/removes

Fixes #398

Testing Evidence
 ARM_SUBSCRIPTION_ID="00000000-0000-0000-0000-000000000000" make TESTPREFIX='TestManagementAdvanced' terratest
==> Running Go test...
cd tests/terratest && go test $(go list ./... |grep -v 'vendor'|grep -v 'utils')  -run ^TestManagementAdvanced
ok  	github.com/Azure/terraform-azurerm-caf-enterprise-scale/tests/terratest/connectivity/advancedVnetPeeringName	0.190s [no tests to run]
ok  	github.com/Azure/terraform-azurerm-caf-enterprise-scale/tests/terratest/management/advancedAutomationAccountIdentity	10.888s

Note: identity block must be enclosed in a list [ ... ]
module "alz" {
  source  = "Azure/caf-enterprise-scale/azurerm"
  version = "2.x.x"
  # ... removed mandatory vars
  advanced = {
    custom_settings_by_resource_type = {
      azurerm_automation_account = {
        management = {
          identity = [
            {
              type = "SystemAssigned, UserAssigned"
              identity_ids = [
                "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/test/providers/Microsoft.ManagedIdentity/userAssignedIdentities/test-id"
              ]
            }
          ]
        }
      }
    }
  }
}

As part of this Pull Request I have

[x] Checked for duplicate Pull Requests
[x] Associated it with relevant issues, for tracking and closure.
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[x] Updated relevant and associated documentation.
[ ] Updated the "What's New?" wiki page (located in the Enterprise-Scale repo in the directory: /docs/wiki/whats-new.md)

/azp run unit

/azp run unit

Thanks @matt-FFFFFF for this feature, perfect timing for myself :). Maybe will be also good option to add System Managed Identity for Automation Account as default option for new automation accounts creation?

Hi @mlomat,
Thanks for the suggestion!
Doing this would modify existing deployments so will hold off for now and discuss with @krowlandson.
Matt

Sure, I understand that. From my perspective, I just tested it because I added SystemIdentity manually on Azure portal.
Framework wanted to remove it after reapply, because terraform find out that state of AA has changed. So I found out your change to version 2.1.2 and I added custom config:
 advanced = {
      custom_settings_by_resource_type = {
        azurerm_automation_account = {
          management = {
            identity = [
              {
              type = "SystemAssigned"
              }
            ]
          }
        }
      }
    }

After that, it doesn't want to remove it anymore. So I think no harm to add it as default.
Have a great weekend!
Best
Mateusz

@mlomat thanks!


Basic Companies created using the AR filing - need process for updating account info and payment options

Basic Companies created using the AR filing have tombstone information only and BCOL is raising tickets for those accounts to ITOPS
a.	Can a person who creates a basic account log in at any time to add their payment options and other company information?
b.	What happens if they cannot?

Regarding the below BAR email text, I understand that once a corp receives a link to file using the new BAR filing, and they create an account in BCROS, there is only tombstone info available and they have no options to update their account. This may/will create an issue when a user tries to update their new BCROS account (product selection, etc).
It sounds like we don’t want users to try to update their accounts until we are ready to migrate COLIN data to BCROS. I spoke with Omid, and he confirmed that work will have to be done on the Entities side before users will have the ability to update their accounts as their data is still in COLIN.
In the meantime, we will see if we can massage the wording in the BAR email so it is clear that users do not need to update their accounts yet. Will also look at the current key messages for BAR and provide some updates.

@sarahelz19 - see above, fyi


As an irresponsible student, I have to be scolded so that I can learn from my mistakes and be more responsible in the future.

[x] Add bot response to user's productivity in productivity panel

Integrated into ProductivityPanel


Save SRID custom settings

SRID settings are returned back to default after DBeaver reopening. We should keep user SRID settings saved.

Fixed. Please make sure column formatting still works.

SRID cannot be saved in spatial tab
SRID cannot be set in column formatting (3395 is used by default)

implemented.


Uneven distribution of IP address ownership

This is right after startup in a 3-node cluster:
# weave status ipam
76:a1:dd:6c:12:51(brya-0)               524288 IPs (50.0% of total) (1 active)
0e:e4:4e:dd:92:ca(brya-2)               393216 IPs (37.5% of total)
ba:23:5a:0c:f3:10(brya-1)               131072 IPs (12.5% of total)
# weave report
...
    "IPAM": {
        "Paxos": null,
        "Range": "<IP_ADDRESS>/12",
        "RangeNumIPs": 1048576,
        "ActiveIPs": 1,
        "DefaultSubnet": "<IP_ADDRESS>/12",
        "Entries": [
            {
                "Token": "<IP_ADDRESS>",
                "Size": 393216,
                "Peer": "0e:e4:4e:dd:92:ca",
                "Nickname": "brya-2",
                "IsKnownPeer": true,
                "Version": 5
            },
            {
                "Token": "<IP_ADDRESS>",
                "Size": 131072,
                "Peer": "ba:23:5a:0c:f3:10",
                "Nickname": "brya-1",
                "IsKnownPeer": true,
                "Version": 3
            },
            {
                "Token": "<IP_ADDRESS>",
                "Size": 524288,
                "Peer": "76:a1:dd:6c:12:51",
                "Nickname": "brya-0",
                "IsKnownPeer": true,
                "Version": 1
            }
        ],
        "PendingClaims": null,
        "PendingAllocates": null
    }
}

I would expect 50/25/25; the <IP_ADDRESS> token is bang in the middle but the <IP_ADDRESS> one is a quarter of the way between the two points.
(This particular distribution does not have any negative consequences, but I'm curious how it comes about)

As I commented on #3171:
We could have some modest background task where any peer can say at any time "I perceive that I have 1% of the address space and someone else has 90%; I will ask for some more" - that would help with "re-distribute" and also lessen the impact of a delay in reclaiming.
We also want to avoid gratuitously fragmenting the overall space. Although that may be ok as a consequence of existing heuristics.

Here's another example: newly-created kops cluster:
# weave status ipam
1a:14:77:48:b4:0d(ip-172-20-58-132.eu-central-1.compute.internal)  1048576 IPs (50.0% of total) (1 active)
8a:45:a2:e8:9a:f9(ip-172-20-70-4.eu-central-1.compute.internal)   524288 IPs (25.0% of total)
4a:b2:c6:50:52:f5(ip-172-20-35-59.eu-central-1.compute.internal)   393216 IPs (18.8% of total)
62:67:b2:a1:15:50(ip-172-20-127-112.eu-central-1.compute.internal)   131072 IPs (06.2% of total)


podman-remote volume inspect|ls

add the ability to list and inspect volumes using the remote
client and varlink
Signed-off-by: baude<EMAIL_ADDRESS>

the next volume based PR will enable tests and add API documentation to all volume related commands where applicable

LGTM
@jwhonce PTAL

fixed up per comments, ready for merge

/lgtm


City view crashes, "item with id ... already exists"

Steps to reproduce:

Go on https://cluster.covid19india.org/
Click the City icon in right sidebar

Observation:

Page is replaced by a single sentence : "An unexpected error has occurred."
Console log shows 2 errors:

Error: Cannot add item: item with id 7701c8e38a5d97b93a8ff527ff556ef31940bd5d already exists
    at t.value (e32c019e.a37cbf266f11b1830d7a.js:1)
    at t.value (e32c019e.a37cbf266f11b1830d7a.js:1)
    at t.value (index.js:1)
    at t.value (index.js:1)
    at wi (framework.1aca562006664c5eb2f5.js:1)
    at Va (framework.1aca562006664c5eb2f5.js:1)
    at ko (framework.1aca562006664c5eb2f5.js:1)
    at xu (framework.1aca562006664c5eb2f5.js:1)
    at wu (framework.1aca562006664c5eb2f5.js:1)
    at du (framework.1aca562006664c5eb2f5.js:1)

main-38f8a3fdb67c1679a368.js:1 Error: Cannot add item: item with id 7701c8e38a5d97b93a8ff527ff556ef31940bd5d already exists
    at t.value (e32c019e.a37cbf266f11b1830d7a.js:1)
    at t.value (e32c019e.a37cbf266f11b1830d7a.js:1)
    at t.value (index.js:1)
    at t.value (index.js:1)
    at wi (framework.1aca562006664c5eb2f5.js:1)
    at Va (framework.1aca562006664c5eb2f5.js:1)
    at ko (framework.1aca562006664c5eb2f5.js:1)
    at xu (framework.1aca562006664c5eb2f5.js:1)
    at wu (framework.1aca562006664c5eb2f5.js:1)
    at du (framework.1aca562006664c5eb2f5.js:1)

My surface guess is that id 7701c8e38a5d97b93a8ff527ff556ef31940bd5d is repeating in the data somewhere. If the data is coming from outside the scope of this repo, then this alert needs to be shared with the folks in charge of it.
Fix Proposal

In case this is a problem that can recur later on as well and it's beyond the scope of this repo to influence a fix, then we have to do on-the-fly adjustment to make the site still work.
Should run a data-cleaning function upon data fetch before passing it into the viz
Delete off or re-id dupes to make do and proceed; but also dump the dupe catch in the console log.
If possible, send out an api call to report this error. Matomo is a good OS solution - normally a hits tracker, but can be repurposed to capture specific messages.

Detailed error
Uncaught Error: Cannot add item: item with id 7ec65df9a6f2816d565962afff630ba8dd1fba261 already exists
    at t.value (vis-network.esm.min.js:25)
    at t.value (vis-network.esm.min.js:25)
    at Graph.patchNodes (index.js:178)
    at Graph.shouldComponentUpdate (index.js:86)
    at checkShouldComponentUpdate (react-dom.development.js:12716)
    at updateClassInstance (react-dom.development.js:13233)
    at updateClassComponent (react-dom.development.js:17131)
    at beginWork (react-dom.development.js:18653)
    at HTMLUnknownElement.callCallback (react-dom.development.js:188)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:237)
    at invokeGuardedCallback (react-dom.development.js:292)
    at beginWork$1 (react-dom.development.js:23234)
    at performUnitOfWork (react-dom.development.js:22185)
    at workLoopSync (react-dom.development.js:22161)
    at performSyncWorkOnRoot (react-dom.development.js:21787)
    at react-dom.development.js:11111
    at unstable_runWithPriority (scheduler.development.js:653)
    at runWithPriority$1 (react-dom.development.js:11061)
    at flushSyncCallbackQueueImpl (react-dom.development.js:11106)
    at flushSyncCallbackQueue (react-dom.development.js:11094)
    at discreteUpdates$1 (react-dom.development.js:21924)
    at discreteUpdates (react-dom.development.js:1071)
    at dispatchDiscreteEvent (react-dom.development.js:4168)

Looks like this hash belongs to Kerala state

Still trying to figure this one out.

fixed in https://github.com/someshkar/covid19india-network/pull/54


Best Practices & FAQ - Performance and Retention - Broken Link

Performance and Retention broken link in the Best Practices & FAQ document

Broken Link
Performance and Retention

This has been solved


Fix phone/email being published in logs

Seems like the current code doesn't fix it. Look into this.

Fixed. Issue was with not using fields: { property: false } in the projections.


why aws-data-wrangler-layer-py3-9 is deprecated?

Hi everybody, I would like to know why official lambda layer of this library is deprecated in AWS. Thank you!

https://serverlessrepo.aws.amazon.com/applications/us-east-1/336392948345/aws-data-wrangler-layer-py3-9

Hi @ijtarano, the library has recently gone through a rename from aws-data-wrangler to aws-sdk-pandas. The SAR app is still available but simply under a different name:

As result of that change we have deprecated the old versions to avoid confusion.

OMG, thank you so mucho @jaidisido!!