Podman, Buildah, and Skopeo support

Support for Podman, Buildah, and Skopeo
The current fn init and subsequent containers exclusively use Docker, and require the Docker daemon to be running. The open-source leaner alternatives Podman, Buildah, and Skopeo are intended to replace Docker, and provide a daemon-less container experience. The can also compliment and augment to the feature set of Fn CLI.

Interfaces similar to the below can be practically re-used to implement support any OCI-compliant container tools.
https://github.com/fnproject/fn/blob/88635fcf086b80dbe809257951beb08727979cfb/api/agent/drivers/docker/image_puller.go#L25-L28

At this point, I might have to agree that Fn is tightly coupled with Docker. Not sure if this can be implemented as a feature, or a standalone fork.

Hello, we have the driver interface https://github.com/fnproject/fn/blob/master/api/agent/drivers/driver.go which seems to be what you're looking for, this enables swapping out container drivers. Of course, it has become very docker specific over time, it's possible to stub out certain things to get something working to ignore certain feature sets we currently offer via the docker driver, and the basic create container / run container ought to be sufficient. it would be possible to implement such a driver separately and configure fn to start with it, no fork needed. it would be nice to run containers without the docker daemon!

Is someone looking to work on this? Hope I can self-assign and start working?

Looking forward to have them support, especially now that docker desktop has its license changed.

您好，您的邮件已收到，谢谢。——熊宇飞


Syntastic fails to parse the tilda character (user home dir) in custom include paths

With syntastic configured so it knows where to search for "custom" includes through creating a configuration file that looks something like this:
.config/vim/foo_includes.syntastic
-I/var/foo_sdk/include
-I/var/bar_sdk/include
-I~/.local/include

And in the .vimrc file:
let g:syntastic_cpp_config_file='~/.config/vim/foo_includes.syntastic'

You will run into this type of error: "fatal error: custom.h: No such file or directory".
Re-running this with some extra debug to find out what's going on:
SyntasticMake: called with options: {'postprocess': [], errorformat': '%-G%f:%s:,%f:%l:%c: %trror: %m,%f:%l:%c: %tarning: %m,%f:%l:%c: %m,%f:%l: %trror: %m,%f:%l: %tarning: %m,%f:%l: %m', 'makeprg': '''g++'' -x c++ -fsyntax-only  -I. -I.. -Iinclude -Iincludes -I../include -I../includes ''-I/home/[username]/.vim/~/.local/include'' -I/var/foo/include -I/var/bar/include some_file.cc'}
Clearly shows that the issue is in the expansion of the '~' character which should be "path to users home directory" - it seems syntastic does not handle this, because the line in the configuration file:
-I~/.local/include
Should equate to:
-I/home/[username]/.local/include
But looking at the debug, it is actually becoming:
-I/home/[username]/.vim/~/.local/include

"Doctor, it hurts when I do X." :smile:
Config files are deliberately dumb.  They have a single feature, expansion of relative paths with -I.  They have no concept of quoting.  Expanding ~ would require extending the format for config files to understand quoting, because otherwise you wouldn't be able to pass unexpanded ~.
This is Vim.  How about :s!^-I\zs\~!/home/user!.


Added university applications page for students

closes #41
Added page for students to add the universities applications.
Added form validation for the same page.
Code cleanup.

LGTM


button design

Question
How do the design of the buttons for photo come out since it only opens the camera
What I tried
No response
VisionCamera Version
2.13.2
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Hey sorry I don't understand the question.

Could you maybe show screenshots?


Fix Webhook Parsing

TL;DR you forgot to .find() it.

check git history
https://github.com/mewna/catnip/commit/6e05ddc51a968ef122bd3d852dd86834c0bc3507#diff-da7559634f1160f94a6cfe01bafc7d6f
authored by me

Guess I don't get to pass the blame this time, rip
ty for fix


Add: "auto-label" GitHub Workflow for Automated Labeling

Objective: Implement an "auto-label" GitHub workflow to automatically assign the "gssoc-ext" and "hacktoberfest-accepted" labels to relevant pull requests and issues.
Details:

This workflow will streamline the labeling process by automatically applying the "gssoc-ext" and the "hacktoberfest-accepted" label to Issues.
By automating these labels, we can ensure consistent tracking and visibility of contributions tied to these significant events.

Implementing this "auto-label" workflow will enhance project organization
hey @Devanik21 Please Assign it to me with label "gssoc-ext" , "hacktoberfest-accepted" and "level2"

Objective: Implement an "auto-label" GitHub workflow to automatically assign the "gssoc-ext" and "hacktoberfest-accepted" labels to relevant pull requests and issues.
Details:

This workflow will streamline the labeling process by automatically applying the "gssoc-ext" and the "hacktoberfest-accepted" label to Issues.
By automating these labels, we can ensure consistent tracking and visibility of contributions tied to these significant events.

Implementing this "auto-label" workflow will enhance project organization
hey @Devanik21 Please Assign it to me with label "gssoc-ext" , "hacktoberfest-accepted" and "level2"

plz add for level1,level2 and level3 also

@samyak-aditya , are u working ?, plz edit .github/workflows/auto-label.yml
and raise a PR

Hey @Devanik21 yes I am Working on it

Hey @Devanik21 I have raised the PR

@samyak-aditya

Hey @Devanik21


Disable linter error check when configuration is not found.

How to disable linter in ale (in my case eslint), if there was no eslint configuration found.
I sometimes edit standalone file scripts, where linter is not configured, and I don't have eslint globally configured.

I recommend disabling ESLint for particular files. Consult the documentation for :help g:ale_linters and :help g:ale_pattern_options.

@w0rp thank for the answer. I know this option, but it will be extremely annoying to configure pattern for every file you want to edit. Moreover, the same file can appear twice in different projects and you want linter for one of it.

You can use regular expressions, so you can configure many things in one go.

@krhubert
You can use this in your vimrc to get that functionality:
autocmd FileType javascript let g:ale_linters = findfile('.eslintrc', '.;') != '' ? {'javascript': ['eslint']} : {'javascript': ['']}

I have added an option, which can be configured per buffer, for disabling specifically this error. See :help g:ale_javascript_eslint_suppress_missing_config. Be warned that turning this option on will mean that you won't be told when you're missing a configuration file for your project.

BTW, here is some code which takes a glob pattern (e.g. .eslintrc.*) instead of just a string (findfile does not support globs):
" Only lint if .eslintrc is present
autocmd FileType javascript let g:ale_linters = FindGlob('.eslintrc.*', expand('%:p:h')) ? {'javascript': ['eslint']} : {'javascript': ['']}

function! g:FindGlob(pattern, path)
  let fullpattern = a:path . "/" . a:pattern
  if strlen(glob(fullpattern))
    return 1
  else
    let parts = split(a:path, "/")
    if len(parts)
      let newpath = "/" . join(parts[0:-2], "/")
      return FindGlob(a:pattern, newpath)
    else
      return 0
    endif
  endif
endfunction

Probably atrocious vimscript because I don't have much experience with the language, but hey, it works.


Update hide-logs-using-regex.md

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b864cf6a1a57840d19f32a--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b865205ced5086837883dc--harness-developer.netlify.app


Reconsider bug fixing description

In the description of this crate there is a mention of bugs in std being avoided by using this crate but after the news in https://github.com/rust-lang/rust/issues/100650 the validity of this statement should be reconsidered

I believe the MIPS one is fixed in LLVM, but the fix should not yet be available in rustc. The arm one is not yet fixed as far as I know (LLVM isssue is still open). The powerpc one is supposedly fixed in LLVM, but when I tested it before with the version that was supposed to contain the fix, the problem was not actually fixed. (I'm aware of other bugs besides this regarding powerpc, and I should minimize and report them, but enough minimizing the repro is not easy...)
This problem is already tracked in #2, where there is a description of the conditions under which the problem occurs, but note that this is a bug that can be hidden by other factors, especially the presence or absence of optimization, since it is UB. So random "I can't reproduce this" comments are not necessarily reliable.
Eventually, when all of these are fixed, I would close #2 and change the description to something like "LLVM bugs affecting rustc 1.N and earlier", but at least that is not something that can be done right now.
I'm going to close this in favor of a #2 that tracks the problem more exhaustively.

The MIPS issue also does not appear to be actually fixed. https://github.com/rust-lang/rust/issues/123772


Crawler stats

Would be great to have some simple way how to access statistics from crawler run similarly as on Apify.com (pages crawled, outputted, retried, in queue, failed, number of results, etc.)

@mnmkng This is mostly done with the small stats object at the end. Maybe add simple documentation for it and close this?

#716


There is no unit for the usage value size against one file share

Storage Explorer Version: 1.22.0-dev
Build Number: 20211109.2
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 18.04/MacOS Monterey 12.0.1
Architecture: ia32/x64
How Found: From running test cases
Regression From: Previous release (1.21.3)
Steps to Reproduce

Expand one storage account -> File Shares.
Select one file share -> Check its 'Properties' panel.
Observe the value of the 'Usage' property -> Check whether there is a unit for the value size.

Expected Experience
There is a unit for the value size.

Actual Experience
There is no unit for the value size.

Verified on the build 20211110.1. Fixed.


Inefficient storage space usage.

Moving containers between projects causes filesystem clones to be created.
Original filesystems are being moved to storage-filesystem/deleted/containers.
It is not possible to delete these filesystems because of the clones not being promoted.
Filesystem list grows with each container move.
Storage backend space usage grows with snapshots taking more space when old data is being overwritten.

What storage backend (sounds like ZFS)?
What commands did you run and how does zfs list -t all -o name,origin look before and after?


Question: Does component Main need prop named router?

Hi!
I am looking at the code for the client-side. Does the Main component need a prop named router? How is it used? See lines 14 and 27 in src/client/index.jsx

Hi!
No. Thanks for noticing! Fix has been pushed:
https://github.com/sysgears/apollo-fullstack-starter-kit/commit/20afa3dfe31368c1f2fa90c95e9dc8479f3fbbbf


Math/extent conversion

This PR converts all the math/extent code in RapiD to consume the id-sdk.
I have started with just the math/extent library, but can open additional PRs / extend this PR to do a total conversion if folks want!
Screenshot of working tests:

Screenshot of (ruh roh) OSM Ways not displaying. Need to drill down into why this is happening:

Awesome!  Yeah Extent is one that's used everywhere - this is a ton of work!
I'm not sure offhand what made the ways disappear, but will take a quick scan of the diff..

Unfortunately it looks like ways are still broken after I made the changes @bhousel suggested. Something else is going on here- no way data is making it into the OSM Layer data. I suspect some wonky extent logic is masking the data from making it to the rendering pipeline.

Merging after our sync discussion on friday.

merging as per our sync meeting friday!


lit-element-mixin: add formatter func support

In some cases you don't want to render the value directly.
You might need:

Formatting
Conditionals
etc

An ability to add a value formatter/converter to the binder is needed.

Currently used this way:
<span>${$objarr.length${(length) => length > 1 ? '+' : ''}}</span>


This model is amazing!

Hi! This model is amazing. I am wondering if you plan on further developing it. You could add more maps, eg .albedo etc. further fine tune the model etc.
I would definitely be willing to sponsor this project!

There was one point where I really wanted to develop this further and train a single model that could produce a ton of maps, but that ended up being really difficult and I kinda gave up. I currently spend most my time working on chaiNNer now, so I probably won't work on any successor to this for a while.
Though, since we already have normal map generation in chaiNNer, I do think it would be cool to add generators for other maps there. Maybe I'll look into that.

I see. Unfortunately, I have absolutely no idea how any of this works so I cannot contribute myself. I built something pretty cool that uses your model. Do you have Twitter or something? I would love to show it to you and maybe pay you a coffee or something

I don't have a Twitter but I do have a ko-fi if you really wanna donate, but you really don't have to. https://ko-fi.com/jballentine
Glad you were able to use this for something useful 👍

chaiNNer looks interesting, thanks!
More generators would be cool indeed.

chaiNNer looks interesting, thanks! More generators would be cool indeed.

Yes,it's simple and useful.As same as you,looking forward to the more generators.


Minor fix to README for service/#quick-start

Previous link to https://github.com/clearlydefined/service/readme.md
gives a 404.
Signed-off-by: Tom Marble<EMAIL_ADDRESS>

🎊 Thanks for your first PR, @tmarble!


Initialization of behaviors and events

I've been thinking about how best to initialize behaviors and events.
Goals:

Initialization should only be allowed to happen once
It should be easy to find where in the view a thing is being initialized

This is what we currently have. Initialization can be found by searching for "name.def".
{click: btnClick.def} = button("Click me")

This one looks very non-magical. One would have to find initialization locations by searching for ": name".
button("Click me", {on: {click: btnClick})

This one also has no magic. The def function (or whatever it should be called) extracts events from the component.
def({click: btnClick}, button("Click me")

In this one the events list specifies which events to create. But it doesn't work, because the result of the expression whould not be the component but instead the array.
[btnClick.def] = button("Click me", {events: ["click"]})

I like the idea of it being non-magical and prefer:
button("Click me", {on: {click: btnClick})

this would work well if we want to implement a HyperScript-like functions where you describe all the properties and settings in an object.
button("click me", {
  on:{
    click: btnClick
  },
  style: {
    paddingLeft: "5px"
  },
  attributes: {
    disabled
  }
}

Good point. It will also work smoothly with JSX which none of the others will. I think we'll pick that one then.
Also, to ensure that a behavior/event can only be hooked into one component, I we could do this: Instead of having a push method, the behaviors returned by declareBehaviors could have a getPush method that returns a push function and throws an error if it is called more than once.


AMBARI-23164 Config dependencies alert bar not displayed properly while scrolling down the page

How was this patch tested?
21523 passing (31s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1018/
Test PASSed.


[Extension] Create port service and control service worker lifetime

Create a service that is dedicated to storing port information and controlling service worker lifetime. The service worker should remain alive while any port is still active, otherwise it may be shut down.

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

Project coverage is 78.53%. Comparing base (d3309ca) to head (6865950).

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #89       +/-   ##
===========================================
+ Coverage   65.32%   78.53%   +13.20%
===========================================
  Files          31        4       -27
  Lines         822      177      -645
  Branches       60       21       -39
===========================================
- Hits          537      139      -398
+ Misses        281       38      -243
+ Partials        4        0        -4

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


Tidy up building docs a bit, add arch dependencies

Why are arch dependencies being added? I thought only Fedora and Debian/Ubuntu were being supported.

Works just fine for me, have built on Manjaro and stock Arch. Why not make the info more accessible if it works anyways?

Packaging is a non-issue for Arch-based stuff at this point, Mado is currently maintaining a PKGBUILD for the AUR. I imagine no effort will be needed on your part. Unfortunate debian-based distros don't have something similar though.


build error with<EMAIL_ADDRESS>

../../go/pkg/mod/github.com/iovisor/gobpf@v0.2.0/bcc/module.go:230:132: not enough arguments in call to (_C2func_bcc_func_load)
have (unsafe.Pointer, _Ctype_int, *_Ctype_char, *_Ctype_struct_bpf_insn, _Ctype_int, *_Ctype_char, _Ctype_uint, _Ctype_int, *_Ctype_char, _Ctype_uint, nil)
want (unsafe.Pointer, _Ctype_int, *_Ctype_char, *_Ctype_struct_bpf_insn, _Ctype_int, *_Ctype_char, _Ctype_uint, _Ctype_int, *_Ctype_char, _Ctype_uint, *_Ctype_char, _Ctype_int)
make: *** [Makefile:6: netcap] Error 1

just use<EMAIL_ADDRESS>


GEOMESA-2522 Specify id or user data field in converter error messages

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

Needs to be rebased.

Is this ready to be rebased?


Bumps GH actions to pre-releases

Package manage/ecosystem
github_actions
Manifest contents prior to update

Updated dependency

What you expected to see, versus what you actually saw

Images of the diff or a link to the PR, issue or logs

This has been already reported in https://github.com/dependabot/dependabot-core/issues/1461#issuecomment-638181262, but I felt like an separate issue makes sense for both tracking the state and finding it easier.
dependabot currently updates GitHub actions to pre-releases, which seems counter-intuitive. Having that behavior hidden behind a configuration flag might be useful, but I think the default should be to only update to full releases.
Example PR: https://github.com/theforeman/forklift/pull/1181

cc @ekohl

From https://github.com/dependabot/dependabot-core/issues/1461#issuecomment-638181262
It will be nice to detect pre-release or beta tag and do not bump it.
Check a GitHub release type
The<EMAIL_ADDRESS>is a beta version (pre-release). We need a useful filter for not bumping it.
Check a tag format
Semantic Versioning 2.0.0 has a format for a beta release like 1.0.0-beta, 2.0.0-rc.2, and v3.7.0-1.
It is useful:

Not to create a pull-request for those releases OR
User can set up with their .github/dependabot.yml wether accepting beta release it, or not.

Adding 1 Debit: https://github.zendesk.com/agent/tickets/1912286

Question from the ticket I pates above. I was told, and shared with the customer, that ignoring "minor" versions would also ignore pre-release. They don't want to implement this.
Is there a way they can continue to use Dependabot without getting pre-release version updates and without ignoring "minor" versions?

While I love the Releases UI and use it routinely in my open source projects, I'm much more a fan of communicating the non-stable versions directly in the version number / tag, and not indirectly through a metadata API like the releases API. For example, we recently added support to Dependabot for fetching/updating actions hosted at custom locations not necessarily GitHub... so the releases API wouldn't work then...
FWIW, Actions recommends a versioning scheme that embeds indications of beta / pre-release into the tag itself:

Major versions can be initially released with a beta tag to indicate their status, for example, v2-beta. The -beta tag can then be removed when ready.

We may want to sync internally with the Actions team to ask them to tighten that recommendation to not only major versions, but also any versions with alpha/beta in the suffix treat as pre-release. I don't think it can be just any suffix as suffixes may sometimes be useful to communicate other information such as OS / hardware platform compatibility, etc.
If we don't already, we probably should have a UT in dependabot-core checking that we honor the -beta tag: ... this would be an easy thing for us to treat as non-stable vs stable when upgrading.

Similar discussion:

https://github.com/dependabot/dependabot-core/issues/5284#issuecomment-1408032292

Hey,
I'm facing the same problem with a pre-release package we have in python using pip. In our case, we are using the format X.X.X.devX.
Does anyone has achieve to add an ignore setting for this case? We are publishing a pre-release, so we do dogfooding of our own CLI before realizing to the our customers and this is a real pain as our customers are getting notified by the Dependbot about a new pre-release version.

It would be nice to follow a similar concept to NPM and be able to release a new (major) version as stable, without marking it as latest and so not triggering the dependabot update.
The default setting from semantic-release cover exactly this use case with the next and next-major branches...
Something similar could be achieved without switching to the release API though, simply by adding a latest tag the same way we add the major version tags.
This way, workflows could be updated manually to newer stable versions and wouldn't need to be updated again, once the version is marked as latest. And workflows would be updated automatically as soon as the latest tag is set and it is safe to upgrade.


apt-get update / install with -y causes setup hang

https://github.com/shivammathur/php-ubuntu/blob/d752c0e323638e3fa5ae13654ab4935d7432657d/scripts/install.sh#L31
I'm trying to run shivammathur/setup-php@v2 through act, however it hangs up indefinitely.
So I connected a term session to the container, checked where it is stuck and manually checked through the running scripts:
root        19     0  0 19:15 pts/1    00:00:00 node<EMAIL_ADDRESS>root        35    19  0 19:15 pts/1    00:00:00  \_ /usr/bin/bash<EMAIL_ADDRESS>root        49    35  0 19:15 pts/1    00:00:00      \_ bash /tmp/install.sh 7.4 release
root       117    49  0 19:15 pts/1    00:00:00          \_ sudo apt --fix-broken install
root       118   117  0 19:15 pts/2    00:00:00              \_ sudo apt --fix-broken install
root       119   118  0 19:15 pts/2    00:00:00                  \_ apt --fix-broken install

Running the command manually (after manually deleting the apt lock), it asks me for confirmation; which I suppose is the root problem.
After some detective work, it seems that the code of install.sh is coming from this repository (I'm guessing is the script I linked at the top).

@uuf6429
What is the command you are using to run act.

Just "act", and selecting the "medium" image, since it actually has node 16.

Please try with images we maintain for setup-php.
https://github.com/shivammathur/setup-php#local-testing-setup

Thanks that seems to work well!

@shivammathur actually, I still have one final problem - apparently that image does not contain docker itself, so I cannot start further services. Any suggestions?
(also, couldn't it make sense to just fix the original problem with php-ubuntu?)

I added the -y option in https://github.com/shivammathur/php-ubuntu/commit/33b904aabddbe7ed9c02174587485866c14949cc as it is harmless, but scripts in this repo are only meant to run on GitHub hosted runners which do not need this.
I will add a check in setup-php to make sure these scripts are not run when using act in the next release of the action.
Also, I have added docker to the shivammathur/node images, so please use those for running act.


emybon player search issues with special characters

Would it be possible to edit the embycon player so it can find titles with '(' or ')' in the name please? I currently get no video found on anything with either type of bracket in the title. I've very little coding knowledge but looking at the json there's something written in to deal with other special characters such as ;:&. Thanks

Sure, have at it. I don't think anyone that has been or is currently involved in this project uses Emby or Embycon, so it's pretty unlikely to get fixed unless you do it.


Added the capture option so that theme authors can better customize keyword in Rust

This PR fixes #138280

Please see the header of the grammar file:
		"This file has been converted from https://github.com/dustypomerleau/rust-syntax/blob/master/syntaxes/rust.tmLanguage.json",
		"If you want to provide a fix or improvement, please create a pull request against the original repository.",
		"Once accepted there, we are happy to receive an update request."

So if you can create the PR against  https://github.com/dustypomerleau/rust-syntax, that would be fantastic.


Provide flag to only allow free (as in speech) packages

VSCode Version: 1.9.1
OS Version: Fedora 26

Steps to Reproduce:

Look through packages available
Observe that many of the top ones – in particular, those by Microsoft – are proprietary software.

This is a feature request to allow rejecting packages whose license does not indicate they are free and open source software.

Hi -
Thanks again for the suggestion. As with https://github.com/Microsoft/vscode/issues/27154 I do not believe we should be the gate keeper for licenses. Users can make an educated decision by looking at the readme in the product before deciding to install the extension.


Server Error On Join

[20:11:39] [Netty Server IO #3/ERROR] [minecraft/NettyPacketEncoder]: java.lang.NullPointerException
[20:11:39] [Netty Server IO #3/ERROR] [minecraft/ArgumentTypes]: Could not serialize net.minecraftforge.server.command.ModIdArgument@280a0090 (class net.minecraftforge.server.command.ModIdArgument) - will not be sent to client!
[20:11:39] [Netty Server IO #3/ERROR] [minecraft/ArgumentTypes]: Could not serialize net.minecraftforge.server.command.EnumArgument@453c9950 (class net.minecraftforge.server.command.EnumArgument) - will not be sent to client!

Figured out source of issue

Fixed in this commit.
Replacing vanilla recipe factories breaks Minecraft servers I guess.


Type assertions using Exact, Subset, Superset

I have suffered several times with the limitations of casting like so:
res.json(<Foo>{foo:'bar'});

the above cast/assertion will work even if the anonymous object does not have all the fields in type Foo.
For example, this question I had: https://stackoverflow.com/questions/53328459/prevent-compilation-unless-all-fields-exist
This feature request is for something like this:
res.json(Exact<Foo>{foo:'bar'});
res.json(Subset<Foo>{foo:'bar'});
res.json(Superset<Foo>{foo:'bar'});

note this is similar to the existing construct Partial, as in Partial<T>, hopefully the above are self-explanatory. I am not sure if both Subset<> and Superset<> make sense, but one of them should.

Exact types #12936

Also #26064

Does this work?
type Subset<L, R extends L> = L

type Superset<L extends R, R> = L

interface T {
    foo: 'foo';
    bar: 'bar';
}

const v: { foo: 'foo' } = {
    foo: 'foo'
};

const v2: { foo: 'foo'; bar: 'bar', baz: 'baz' } = {
    foo: 'foo', bar: 'bar', baz: 'baz'
};

const vprime1: Subset<typeof v, T> = v; // ok
const vprime2: Superset<typeof v, T> = v; // notok

const vprime2_1: Subset<typeof v2, T> = v2; // notok
const vprime2_2: Superset<typeof v2, T> = v2; // nok

@jack-williams  probably, except I am looking to use it with an anonymous object, like so:
type T = ...

doMyThang((err, val) => {
    res.json(<T>val.x);
});

it needs to be an assertion like that...aka doing this kinda takes all my joy away:
type T = ...
doMyThang((err, val) => {
   const x : T = val.x;
    res.json(x);
});


Errors in our build pipeline..

Everything has been working just fine for a year with our build pipeline, but this error just appeared today:
Serverless plugin "serverless-plugin-warmup" initialization errored: Unexpected token {

Same here, started after last update. Freezing module version to 4.8.0 did fix the issue for us.

So it's an error specific to version 4.9.0, right?
Do you get the error when deploying or when the warmup lambda is executed?
Any more info that you can provide?

Hi @juanjoDiaz, its during deployment, attaching the logs below:
$ serverless deploy -s vdtdev

  Syntax Error -------------------------------------------

  /home/circleci/project/serverlessImplementation/node_modules/serverless-plugin-warmup/node_modules/fs-extra/lib/mkdirs/make-dir.js:86
        } catch {
                ^

  SyntaxError: Unexpected token {
      at createScript (vm.js:80:10)
      at Object.runInThisContext (vm.js:139:10)
      at Module._compile (module.js:617:28)
      at Object.Module._extensions..js (module.js:664:10)
      at Module.load (module.js:566:32)
      at tryModuleLoad (module.js:506:12)
      at Function.Module._load (module.js:498:3)
      at Module.require (module.js:597:17)
      at require (internal/module.js:11:18)
      at Object.<anonymous> (/home/circleci/project/serverlessImplementation/node_modules/serverless-plugin-warmup/node_modules/fs-extra/lib/mkdirs/index.js:3:44)
      at Module._compile (module.js:653:30)
      at Object.Module._extensions..js (module.js:664:10)
      at Module.load (module.js:566:32)
      at tryModuleLoad (module.js:506:12)
      at Function.Module._load (module.js:498:3)
      at Module.require (module.js:597:17)
      at require (internal/module.js:11:18)
      at Object.<anonymous> (/home/circleci/project/serverlessImplementation/node_modules/serverless-plugin-warmup/node_modules/fs-extra/lib/copy-sync/copy-sync.js:5:20)
      at Module._compile (module.js:653:30)
      at Object.Module._extensions..js (module.js:664:10)
      at Module.load (module.js:566:32)
      at tryModuleLoad (module.js:506:12)
      at Function.Module._load (module.js:498:3)
      at Module.require (module.js:597:17)
      at require (internal/module.js:11:18)
      at Object.<anonymous> (/home/circleci/project/serverlessImplementation/node_modules/serverless-plugin-warmup/node_modules/fs-extra/lib/copy-sync/index.js:4:13)
      at Module._compile (module.js:653:30)
      at Object.Module._extensions..js (module.js:664:10)
      at Module.load (module.js:566:32)
      at tryModuleLoad (module.js:506:12)
      at Function.Module._load (module.js:498:3)
      at Module.require (module.js:597:17)
      at require (internal/module.js:11:18)
      at Object.<anonymous> (/home/circleci/project/serverlessImplementation/node_modules/serverless-plugin-warmup/node_modules/fs-extra/lib/index.js:7:6)
      at Module._compile (module.js:653:30)
      at Object.Module._extensions..js (module.js:664:10)
      at Module.load (module.js:566:32)
      at tryModuleLoad (module.js:506:12)
      at Function.Module._load (module.js:498:3)
      at Module.require (module.js:597:17)
      at require (internal/module.js:11:18)
      at Object.<anonymous> (/home/circleci/project/serverlessImplementation/node_modules/serverless-plugin-warmup/src/index.js:9:12)
      at Module._compile (module.js:653:30)
      at Object.Module._extensions..js (module.js:664:10)
      at Module.load (module.js:566:32)
      at tryModuleLoad (module.js:506:12)
      at Function.Module._load (module.js:498:3)
      at Module.require (module.js:597:17)
      at require (internal/module.js:11:18)
      at requireServicePlugin (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:26:10)
      at pluginsObject.modules.filter.map.name (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:127:20)
      at Array.map (<anonymous>)
      at PluginManager.resolveServicePlugins (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:124:8)
      at PluginManager.loadAllPlugins (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:111:15)
      at pluginManager.loadConfigFile.then.then (/usr/local/lib/node_modules/serverless/lib/Serverless.js:96:35)
      at tryCatcher (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/util.js:16:23)
      at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:547:31)
      at Promise._settlePromise (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:729:18)
      at Promise._fulfill (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:673:18)
      at Promise._resolveCallback (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:466:57)
      at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:559:17)
      at Promise._settlePromise (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:729:18)
      at Promise._fulfill (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:673:18)
      at PromiseArray._resolve (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise_array.js:127:19)
      at PromiseArray._promiseFulfilled (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise_array.js:145:14)
      at Promise._settlePromise (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:609:26)
      at Promise._settlePromise0 (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:729:18)
      at Promise._fulfill (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:673:18)
      at Promise._resolveCallback (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:466:57)
      at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:559:17)
      at Promise._settlePromise (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:729:18)
      at Promise._fulfill (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:673:18)
      at PropertiesPromiseArray.PromiseArray._resolve (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise_array.js:127:19)
      at PropertiesPromiseArray._promiseFulfilled (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/props.js:78:14)
      at Promise._settlePromise (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:609:26)
      at Promise._settlePromise0 (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:729:18)
      at Promise._fulfill (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:673:18)
      at Promise._resolveCallback (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:466:57)
      at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:559:17)
      at Promise._settlePromise (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:725:18)
      at _drainQueueStep (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:93:12)
      at _drainQueue (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:86:9)
      at Async._drainQueues (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:102:5)
      at Immediate.Async.drainQueues (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:15:14)
      at runCallback (timers.js:810:20)
      at tryOnImmediate (timers.js:768:5)
      at processImmediate [as _immediateCallback] (timers.js:745:5)

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com

  Your Environment Information ---------------------------
     Operating System:          linux
     Node Version:              8.17.0
     Framework Version:         1.67.1
     Plugin Version:            3.6.5
     SDK Version:               2.3.0
     Components Version:        2.28.0

Exited with code exit status 1

Thanks for the details!
So the problem is that you are using Node 8 which was EOLed in December 2019.
fs-extra uses optional catch which is only supported from Node 10.3.
The solution is simply to use Node 10 in your circle ci build.
Would that work?

@juanjoDiaz Yes, that was indeed the case, thanks!

I'll close the issue. Fell free to reopen if needed.


feat: report builder outputs report v2 natively

I'm actually gonna split this up. Give me a sec to push a new change.

Ok, good to review 👍


please add Dartford Grammar School to jetbrains

file.zip
dartfordgrammarschool.txt

@cyber-railgun Your support request which you have made by email was successfully resolved, and I close this pull request as a duplicate. It was not correct anyway, thus it's good that you have contacted JetBrains support when found difficult to submit a request here. Thank you.


Set Visibility

When we set property set Visibility GONE to SwipeRevealLayout. It's Display blank view in row. It's Didn't hide. can you please look in this.

I'm having this same issue. When you're showing a couple of items on swipe and then you set the visibility of all those items to View.GONE then empty space shows. Would appreciate it if anybody could help fix this.


Minor tweaks to the service invocation quickstart

Minor tweaks to the service invocation quickstart

run the consumer before the sender, otherwise things will fail
be clear about where to run the 'cd' cmd from
in the golang sender sample code I removed the extra "if" statement
because it wasn't relevant to the point being made... adding a header
remove quotes from sender's json output to go along with
https://github.com/dapr/quickstarts/pull/621
remove "Step" from the "###" headers
reordered the pub-sub sample too so we start-up the receiver first

Signed-off-by: Doug Davis<EMAIL_ADDRESS>

@paulyuk please review.

It pains me a little to reorder because we have total consistency between these and pub-sub. Maybe you'd donate that change too? :)

Oh geez, now you did it - my OCD kicked in... while doing the re-order for pub-sub I noticed the use of the "###" headers were inconsistent.  In service-invocation only one of the headers at that level started with "Step ", the rest didn't. In pub-sub, there was more than 1 "Step" prefixed header, but then there were other headers at the "###" level w/o a "Step" prefix. Since everything at that level appears to be actions for the user I opted for the consistency of removing the "Step X" prefix from both samples since I'm not sure numbering them adds any real value.

@duglin - Looked at this again and actually I disagree with removing the steps in the headings. Why did you want to do this?
Although I see these are inconsistent in Service Invocation here https://v1-7.docs.dapr.io/getting-started/quickstarts/serviceinvocation-quickstart/
Also this PR now clashes with the one to make all the quickstarts into Capitals and needs resolving.

I looked at this again and actually I do not fully agree with removing the steps in the headings, since this helps follow along. Why did you want to do this? (Although I see these are inconsistent in Service Invocation here https://v1-7.docs.dapr.io/getting-started/quickstarts/serviceinvocation-quickstart/)

I noticed it was inconsistent so I picked a direction that made it easier to manage in the future because if we ever needed to reorder thing (like I did here) or add new steps we wouldn't need to remember to update the other step numbers. I can go back and add the "Step x" headers if people find value in that.
Done

@duglin - Did you confirm that the changes you are introducing here (ordering of running services) are reflected in the quickstart repo readmes?

@greenie-msft I think I got them all in https://github.com/dapr/quickstarts/pull/637 - let me know if you think I missed something

Thanks @duglin. This PR is waiting on the QuickStart repo PR to be merged: https://github.com/dapr/quickstarts/pull/637


HNC: use a later version of controller-tools

We're on a very recent version of controller-runtime and are about to upgrade to the latest version (#1270) but we're using a fairly old version of controller-tools and should probably upgrade those as well. It may even be necessary but I'm not certain.
@GinnyJI - ideally you can fix #1270 and this separate PRs, but if that doesn't work, maybe consider doing them together.
/assign @GinnyJI

/assign @adrianludwin

/assign @adrianludwin


Revert "Fix RelBase indexing with composite types"

This crashes with typealiases referenced across files. I will resubmit with a fix. See also https://github.com/apple/swift/pull/65545
This reverts commit 7a5e9dcf194df9c1c2c655cf29842408f5a7e4b2.

@swift-ci please test


Integrate with GitHub Actions

Hi,
I am trying to use versioningit to bump my pkg version while deploying with GitHub Actions.
The first push successfully created version 0.0.0 at PyPI: https://test.pypi.org/project/geotils/0.0.0/
However, version is not being incremented in subsequent pushes. What did I miss in the following configuration?
pyproject.toml:
[build-system]
requires = ["setuptools >= 61.0"]
build-backend = "setuptools.build_meta"
[project]
name = "geotils"
dynamic = ["version"]
dependencies = [
                ...,
		'versioningit',
]
requires-python = ">=3.10"
description = "geotils by GEOAI group"
readme = "README.md"
license = {text = "MIT License"}
keywords = ["geotils", "geospatial", "earth observation"]
classifiers = [
  "Development Status :: 3 - Alpha",
  "Intended Audience :: Developers",
  "Topic :: Software Development :: Build Tools",
  "License :: OSI Approved :: MIT License",
  "Programming Language :: Python",
]

[tool.versioningit.format]
distance = "{base_version}.post{distance}+{vcs}{rev}"
dirty = "{base_version}+d{build_date:%Y%m%d}"
distance-dirty = "{base_version}.post{distance}+{vcs}{rev}.d{build_date:%Y%m%d}"

[project.urls]
Homepage = "https://geogroup.ai/"
Documentation = "https://readthedocs.org/geotils"
Repository = "https://github.com/geoaigroup/geotils"
"Bug Tracker" = "https://github.com/geoaigroup/geotils/issues"
Changelog = "https://github.com/geoaigroup/geotils/blob/master/CHANGELOG.md"
[project.scripts]
geotils = "geotils.module:function"

GitHub CI/CD workflow code: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#the-whole-ci-cd-workflow

versioningit needs to be listed in requires under [build-system] in order for it to be present & active when the package version is calculated.  Putting it in [project]dependencies as you've done is only correct if your package is a plugin for versioningit.
Also, I only skimmed the linked workflow, but I don't see where you're creating a new Git tag for each release; creating a tag is necessary in order to bump the version for a versioningit-using package.

Thanks @jwodder for the quick feedback.

I added versioningit  to the requires list
got the following build error versioningit could not find a version for the project in /home/runner/work/geotils/geotils!
Finally, the workflow is not creating a tag for each release on purpose. For releases to be pushed to test-pypi, there should be no attached tag while for releases to be pushed to main PyPi, a tag should be attached. This is the logic used by the workflow to decided where to publish (either test-pypi or regular pypi).
given the workflow logic, any luck to use versioningit  without a tag?

What exactly are you expecting or wanting to happen in the absence of tags?
In the absence of a tag, it would be more than enough to increment the patch release version to be able to push changes to TestPyPI.

Would this be feasible with versioningit or do you recommend other version-bumping tools?

@aghand0ur versioningit has no knowledge of any version information if there are no tags available, so it wouldn't have anything to increment if there are no tags.
The following may work for you instead:

Change the uses: actions/checkout@v4 step at the start of the build job to:
- uses: actions/checkout@v4
  with:
    fetch-depth: 0

This will cause the checkout action to perform a full checkout of all of your repository's history, including tags.  Without the with: {fetch-depth: 0}, it would just check out the commit that triggered the workflow, and there would be no tags available for versioningit to query.
With this change, when you build the package, versioningit will take the latest tag (as identified by git describe); if there have been any commits since that tag, you'll get a version formatted as described in your tool.versioningit.format.distance config option.

It is my understanding that both PyPI and Test PyPI reject uploads of packages whose versions end with +stuff.  Thus, you'll need to change your "distance" format to not contain a plus sign.

A straightforward and uncomplicated solution...
I'm at a loss for words to express my gratitude, @jwodder.


Display a editor gizmo icon for Listener

3.x version of https://github.com/godotengine/godot/pull/49284.
The icon was present in editor/icons/, but it was never implemented in the editor gizmos code. This gizmo's visibility can be toggled in the 3D viewport's View menu as usual.
This also removes some unused gizmo drawing code (overridden methods that are no longer called anywhere).
Preview

Thanks!


Proper error recovery in the bridge

The bridge now handles errors and panics better. This occurs in two layers:

If one of the bridge's methods (e.g. createContainer) panics, this will now be turned into an error by the method. From the bridge loop's point of view the behavior hasn't changed, but the methods have to do a bit of extra work to turn the panic into an error.
If the bridge loop panics or errors, it will return the error up to CommandLoop. CommandLoop will then retry on errors until Kill() is called on the bridge. This allows the bridge to listen for the next message, even if it hasn't properly responded to the last one. This allows for things like opening up a shell into the UVM even after a bridge error occurs (assuming the container isn't in an invalid state on the HCS end).

Addresses issues #101 and #103

@beweedon,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

I don't agree with the principle of this change. We should not be trying to recover panics. If there is a panic, it means there is a bug and we have to fix it. Recovering often means leaving the process in an indeterminate state.

From: Ben Weedon<EMAIL_ADDRESS>Sent: Wednesday, August 9, 2017 8:47:12 PM
To: Microsoft/opengcs
Cc: John Starks; Mention
Subject: Re: [Microsoft/opengcs] Proper error recovery in the bridge (#107)
@beweedonhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbeweedon&data=02|01|John.Starks%40microsoft.com|18ee89e0a02a4cde740f08d4dfa27c9d|72f988bf86f141af91ab2d7cd011db47|1|0|636379336354021016&sdata=QJXpRTeGwvWMpJi9KSJ6Odcn3mVS2PsXpoXZvuISxPI%3D&reserved=0 requested your review on: Microsoft/opengcs#107https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fopengcs%2Fpull%2F107&data=02|01|John.Starks%40microsoft.com|18ee89e0a02a4cde740f08d4dfa27c9d|72f988bf86f141af91ab2d7cd011db47|1|0|636379336354021016&sdata=rlgUgf9bLPl9Ql5AwXv1Sq%2B%2F%2FHp44siZiM0mno%2Bt%2F1w%3D&reserved=0 Proper error recovery in the bridge.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fopengcs%2Fpull%2F107%23event-1200231299&data=02|01|John.Starks%40microsoft.com|18ee89e0a02a4cde740f08d4dfa27c9d|72f988bf86f141af91ab2d7cd011db47|1|0|636379336354021016&sdata=JwsWB%2B50oj2Y8Eo3pbJwZwQG1Q%2ForbsUvgKy6grunlY%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJGyQhnl_YpO4UbDNHsy1JBMRaxS3Ww3ks5sWn1AgaJpZM4Oy6Nv&data=02|01|John.Starks%40microsoft.com|18ee89e0a02a4cde740f08d4dfa27c9d|72f988bf86f141af91ab2d7cd011db47|1|0|636379336354021016&sdata=Vo2IABrU9cNwLy6bSJXOiBaEgzAWMMIOggwZZlu3ptw%3D&reserved=0.

John and Justin, I agree with you both that panics are indicative of a bug in the GCS that needs to be fixed.  This can make it more difficult to root cause the problem, especially without easy access to something like porthole. Panics, like some error values we might encounter, are indicative of bugs in the GCS. But I think there's still value to handling these bugs gracefully.
As for leaving the process in an indeterminate state, correct me if I'm wrong, but because panics still call all the defers in the stack until they recover, cleanup operations (which we still in general need to be better at handling on error, but that's another issue) can still be run.

There is no way to know whether recovering is going to keep the process in a good state. Some code uses defer to undo things on failure, some code manually cleans up resources after checking err values, and some code is not possible to undo in the case of a panic. There is no concept of panic safety in Go like there is a concept of exception safety in C++.
In everything we do, we must follow the fail fast philosophy -- if there is a logic bug or fatal error, we must terminate the process. Doing otherwise hides security bugs, data loss bugs, and a variety of weird and unpredictable behavior.
If the problem is that it's too hard to determine what went wrong when there is a panic, then we need to find another way to ensure that the GCS logs and panic output make it back to the host. For example, maybe we need to have GCS try to open a well-known hvsocket on startup to use for stderr. Then we can provide a small tool on the host that binds to that socket that can be used to make debugging easier.

How I've been debugging GCS panic is redirecting gcs stdout/stderr to a persistent file on disk (using VHD boot). I imagine something similar could be to hook up the GCS's stdout/err to well known hvsockets.
Another option is to get the serial console stuff working and then just read from them. This would also help with debugging kernel panics, which can't really be debugged at the moment.

Yeah, the serial console is probably the most straightforward path. We could have two serial ports, one for the Linux console and interactive shell, and a second one for the GCS log (and possibly service VM tool logs).

That's fair. We can explore other avenues for getting panic information back. If we want to go for fail fast, then I should probably also remove the retry logic for the bridge loop, since any errors in the loop itself are likely to either be major errors in the GCS code or malformed data sent from the HCS, both of which are difficult to figure out how to properly recover from.
If this seems cool, I can just redo the commits to only contain the error handling tests.

Sounds good.

bump

Bump

Bump. It would be helpful to merge this or the async bridge request so we can rebase and include the set of changes.

Given this is a test only change and its passing. I am going to merge so I can make the updates to async bridge PR.


codechecker_false_positive does not change the Review status column to False positive

codechecker_false_positive does not change the Review status column to False positive
To Reproduce
Steps to reproduce the behaviour:
https://codechecker.readthedocs.io/en/v6.9.0/user_guide/#source-code-comments-for-review-status
Expected behaviour
Review status column should change to False positive

@gyorb created a patch which may solve your problem: #3078. Could you please try it out?
By the way how is you CodeChecker store command looks like? Do you use the --trim-path-prefix option?
How the source code comment looks like in your source code? Maybe there is a typo. Could you share with us the comment and the line below it?

I think the #3078 patch solved this problem, because I can not reproduce this problem anymore. Please try it again with the master branch.
I will close this ticket for now, but if you still experience this problem we can reopen it.


[HIP] -15: Validator Governance Participation Indicator

https://talk.harmony.one/t/hip-15-validator-governance-participation-indicator/1836/8
Description
A new Governance Participation indicator will be available on the validators staking page with the number of votes submitted versus the number of governance proposals created since validator creation.
Context
The network benefits from active validators who participate in governance. Delegators may want to factor this in when choosing a validator to stake with.
Motivation : To increase validator participation in governance, and allow delegates to easily identify validators who are actively participating in network governance.
Specification : A new Governance Participation indicator will be available on the validators staking page with the number of votes submitted versus the number of governance proposals created since validator creation.
e.g. Governance Participation: 5 / 5
Acceptance Criteria

[ ] Start the count from the date of implementation
[ ] Find the number of votes since implementation that the validator has been active fo.
[ ] Check which votes the valdator participated in.
[ ] Display this value on the staking website.

Reward
TBD by core team after review of scope

Moved to Bounties
https://github.com/harmony-one/bounties/issues/103(url)


P0: Tests (Unit and E2E) for ToDo Skill

Need to add unit and E2E test for ToDo Skill

UT was done. Track E2E task in another item for Va.


problem with breakpoints props

I'm trying to pass breakpoints props to vue-glide  without success. On small screens the number of slides doesn't change.

 <vue-glide

	:autoplay="2000"
	:breakpoints="{'800px':{perView:1},'1200px':{perView:4}}">
	<vue-glide-slide  v-for="index in 10" :key="index">
		Test slide {{index}}
	</vue-glide-slide>

</vue-glide>

According to code comments from @glidejs/glide/dist/glide.js  it should be such object :
  /**
     * Collection of options applied at specified media breakpoints.
     * For example: display two slides per view under 800px.
     * `{
     *   '800px': {
     *     perView: 2
     *   }
     * }`
     */

Version without px units as in official docs didn't help.
https://glidejs.com/docs/components/breakpoints/

 <vue-glide

	:autoplay="2000"
	:breakpoints="{800:{perView:1},1200px:{perView:4}}">
	<vue-glide-slide  v-for="index in 10" :key="index">
		Test slide {{index}}
	</vue-glide-slide>

</vue-glide>

Hello, vue-glide is still in WIP state. Things may not work as expected as it is not a stable code. Sorry.


compile error on ubuntu16.04

accesshttp compile success，
accessws compile error

../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_version':
openssl.c:(.text+0xe67): undefined reference to `SSLeay'
../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_set_engine_default':
openssl.c:(.text+0x11c0): undefined reference to `ENGINE_set_default'
../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_seed.part.5':
openssl.c:(.text+0x13d9): undefined reference to `RAND_file_name'
openssl.c:(.text+0x13ef): undefined reference to `RAND_load_file'
../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_seed':
openssl.c:(.text+0x1498): undefined reference to `RAND_load_file'
../libs/libcurl.a(libcurl_la-openssl.o): In function `ossl_connect_step1':
openssl.c:(.text+0x23f0): undefined reference to `BIO_f_ssl'
../libs/libcurl.a(libcurl_la-openssl.o): In function `Curl_ossl_init':
openssl.c:(.text+0x3447): undefined reference to `OPENSSL_load_builtin_modules'
../libs/libcurl.a(libcurl_la-openssl.o): In function `servercert':
openssl.c:(.text+0x3caa): undefined reference to `OCSP_response_status'
openssl.c:(.text+0x3cbd): undefined reference to `OCSP_response_status_str'
openssl.c:(.text+0x4b24): undefined reference to `OCSP_response_get1_basic'
openssl.c:(.text+0x4b5c): undefined reference to `OCSP_basic_verify'
openssl.c:(.text+0x4ba8): undefined reference to `OCSP_resp_count'
openssl.c:(.text+0x4bbe): undefined reference to `OCSP_resp_get0'
openssl.c:(.text+0x4be3): undefined reference to `OCSP_single_get0_status'
openssl.c:(.text+0x4c07): undefined reference to `OCSP_check_validity'
openssl.c:(.text+0x4c17): undefined reference to `OCSP_cert_status_str'
openssl.c:(.text+0x4e12): undefined reference to `OCSP_crl_reason_str'

Can you please share step-by-step how to reproduce this error?

@Junbin-Hao See installation setup here in Readme: http://github.com/testnet-exchange/python-viab…

@ohld thanks.

@ohld @Junbin-Hao
我的编译方法，请看README最后面
https://github.com/Bringer-of-Light/viabtc_exchange_server

在ubuntu 14.04x64上全部编译成功，修改了accessws的makefile，调整了-lcurl的顺序，把它放到-lssl之前
在ubuntu 16.04x64上matchengine及readhistory编译失败，其他的可以编译成功，错误原因看起来跟libmysqlclient及gcc有关，找不到new，delete等大量的符号，libmysqlclient是c++的项目，而viabtc是c项目，暂时未找到解决方法

Here is my solution, scroll down to the page end: Build on Ubuntu14.04x64
https://github.com/Bringer-of-Light/viabtc_exchange_server

all success on ubuntu14.04x64, I have to modify the makefile of accessws, place -lcurl in front of -lssl solve the link error.
on ubuntu16.04x64, matchengine and readhistory compile failed while all other is success. many link erros occured when compiling matchengine, such as undefined reference to opreator new, undefined reference to opreator new  and etc. looks like libmysqlclient is involved since it is a c++ project while viabtc is c project. gcc may need something more to link to a c++ lib, but I haven't found a solution.

@Bringer-of-Light Can you please avoid using Chinese because, if you do so, you are increasing the chance that the developers across all GitHub can not only use your code, but even fix bugs.
My second question is why you have not used any dockerisation in your solution? This is very useful way to test and deploy the exchange on any environment. Please check the way I've done it here:
https://github.com/testnet-exchange/viabtc_exchange_server/tree/master/docker

@ohld
OK, I will try not to use Chinese anymore.
I'm not using docker, because it looks like that all docker repo of viabtc I found is written for test purpose, all viabtc subunit (include matchengine, accesshttp, etc.) running on the same machine, which should be avoid in production environment.
we really want to modify these docker projects to adapt into our needs, but we are not familiar with docker, and we don't have much time to learn it right now.

@Bringer-of-Light
I was able to compile all on ubuntu 16.04x64 version, do you have MySQL installed?

@Bringer-of-Light You can take a look at docker-compose.yml file in my repo. There is a way to launch this set of dockers on a cluster (search for docker swarm).
By default all dockers in docker-compose are run on the single node inside a virtual local net, that helps in their communication (you can see the ip-addresses in docker-compose.yml file).

@Bringer-of-Light
I don't quite sure that you can easily duplicate services (two accesshttp in your case) with docker swarm. You need some load balancer and I don't know it docker swarm has it out-of-the-box. I know that nginx is very popular load balancer, may be you need some of this.
But anyway. You definitely should check Dockerfile's of every service and than docker-compose.ymlwhich combines them. All that stuff allows be to launch the exchange server with only three commands:
``git clone https://github.com/testnet-exchange/viabtc_exchange_server
cd viabtc_exchange_server/docker
sudo docker-compose up```

@ohld
OK, I'm using load balancer.
"docker-compose up" will make everything online, but on one single machine, which is not the best for production.
what I'm really want to do is: I have multi machine, each one has it's own purpose. such as one for matchengine, one for marketprice, two for accesshttp, etc. after I have install docker and run "git clone" on every machine, I can not run "docker-compose up" on every machine, because "matchengine" should have only one instance.
 But how can these two knowing each other and work together?
I'm doing docker stuff right now, will keep you update If I can put all this together and deploy it into production.
Thanks!

@Bringer-of-Light
Take a look at docker swarm: https://docs.docker.com/engine/swarm/
You can join all your machines in a swarm (read the tutorial on the docker site). There is a way to deploy all dockers from  your docker-compose to your swarm so different containers will be on a different machines of a swarm:  https://docs.docker.com/engine/swarm/stack-deploy/#create-the-example-application
All your swarm machines will be united into a single virtual local network so your containers could communicate with each other in a private network.

@ohld
I got these error on my ubuntu18 machine when using docker-compose up
 sudo docker-compose up

exchange_kafka is up-to-date
Starting exchange_mysql ...
Starting exchange_mysql        ... error
exchange_cli is up-to-date

ERROR: for exchange_mysql  Cannot start service mysql: OCI runtime create failed: container_linux.go:348: starting container proces
Starting exchange_redis_master ... error

ERROR: for exchange_redis_master  Cannot start service redis-master: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/docker-entrypoint.sh\": permission denied": unknown

ERROR: for mysql  Cannot start service mysql: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/docker-entrypoint.sh\": permission denied": unknown

ERROR: for redis-master  Cannot start service redis-master: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/docker-entrypoint.sh\": permission denied": unknown
ERROR: Encountered errors while bringing up the project.
root@marketprice:/opt/bilala/viabtc_exchange_server/docker#

I don't know this error. Do you use the latest docker and docker-compose? Try this tutorial to reinstall docker: https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-18-04

@ohld
do you know why this error is happening?

Actually I've had the same error on Centos. But on Ubuntu / Debian all is fine.

Install it on Centos: https://github.com/lealife/viabtc_exchange_server/issues/1


Steps for Upgrading from 3.4.0 to 3.6.2

Hi,
September 2016 I cloned team-and-enterprise branch (22df21a) on a Virtual Machine and 70 users has used Mattermost since then. We have 19 061 posts and 26 channels.
We would like to do git pull and rebuild Docker images to latest version of this branch, in order to upgrade to latest Mattermost version v3.6.2.
What are the upgrading steps, in order to not loose any existing data? Is it as easy as just to do git pull, rebuild docker images and do docker-compose up?

You should be able to rebuild the docker image and run it. The image will take care of the upgrade. Though I would make sure data is backed up and possibly do a snapshot on the VM in case there is something wrong with the upgrade.

Thanks @xcompass!
Here are the steps i performed:

Stop mattermost docker container
Backup complete folder (mattermost-docker), even I only had changes in volumes folder and docker-compose.yml file
Run git pull
Run docker-compose build
Run docker-compose up -d

Would it be possible to extend README with these details. I assume more people might be interested?


python312Packages.wyoming: 1.5.4 -> 1.6.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.wyoming is: Protocol for Rhasspy Voice Assistant
meta.homepage for python312Packages.wyoming is: https://github.com/rhasspy/wyoming
meta.changelog for python312Packages.wyoming is: https://github.com/rhasspy/wyoming/releases/tag/1.6.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.6.0 with grep in /nix/store/f34sdqkdpgsald4z4xf4ykb64izwvc67-python3.12-wyoming-1.6.0
found 1.6.0 in filename of file in /nix/store/f34sdqkdpgsald4z4xf4ykb64izwvc67-python3.12-wyoming-1.6.0

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.wyoming
python311Packages.wyoming
python312Packages.wyoming
wyoming-faster-whisper
wyoming-piper
wyoming-satellite

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/f34sdqkdpgsald4z4xf4ykb64izwvc67-python3.12-wyoming-1.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.wyoming https://github.com/r-ryantm/nixpkgs/archive/9a8ea814de5f35a977db69eac88616d3516526f7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9a8ea814de5f35a977db69eac88616d3516526f7#python312Packages.wyoming

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/f34sdqkdpgsald4z4xf4ykb64izwvc67-python3.12-wyoming-1.6.0
ls -la /nix/store/f34sdqkdpgsald4z4xf4ykb64izwvc67-python3.12-wyoming-1.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

wyoming-satellite
wyoming-satellite.dist

9 packages built:

home-assistant-component-tests.wyoming
python311Packages.wyoming
python311Packages.wyoming.dist
python312Packages.wyoming
python312Packages.wyoming.dist
wyoming-faster-whisper
wyoming-faster-whisper.dist
wyoming-piper
wyoming-piper.dist

Maintainer pings
cc @mweinelt for testing.

Add a :+1: reaction to pull requests you find important.

This broke wyoming-satellite.


Refresh all valid views when connected to a new system

Changes
Fixes a bug where profiles were not being refreshed after disconnect and connecting to a new system, which was resulting in the incorrect - fixing #1239.
This may also fix #1221, but I am unsure as I can't test that.
Checklist

[x] have tested my change
[ ] updated relevant documentation
[ ] Remove any/all console.logs I added
[ ] eslint is not complaining
[ ] have added myself to the contributors' list in CONTRIBUTING.md
[ ] for feature PRs: PR only includes one feature enhancement.

@worksofliam Sure, I will give it a shot tomorrow.

This is odd as that was already done for the Object/IFS browsers and the LibraryListView:

Those may be removed now, maybe?

@sebjulliand Yes, they should probably be removed. I wonder if we remove them, the issue will come back?


Numeric Pattern 324

any problem?

Hi, so basically the SWOC scoring policy is as follows:
10 patterns beginner tag 10 points
20 patterns easy tag 20 points
and so on...
I will be able to merge this PR once you have minimum 10 patterns eligible for beginner tag. If you are first time contributor please join the organization too so that we are able to keep a record of contributors.

I have assigned your 4 pending issues and will merge the pr on completion of 10 patterns


fix(handler): company name would overlap business id (HL-1201)

Description :sparkles:
This is originally unresponsive but 🤷  at least it's not broken anymore.
Before

After

API branch is deployed to platta: https://helsinkilisa-pr2929.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://helsinkilisa-ui-handler-pr2929.dev.hel.ninja :rocket::rocket::rocket:

APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr2929.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://helsinkilisa-ui-handler-pr2929.dev.hel.ninja :laughing::tada::tada::tada:


Remove python 3.7 support

Summary:

Test plan:

Fixes #{issue number}

Codecov Report
Base: 63.52% // Head: 63.53% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (c9dcb20) compared to base (f1fb48c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #399   +/-   ##
=======================================
  Coverage   63.52%   63.53%
=======================================
  Files         143      143
  Lines        9605     9604    -1
=======================================
  Hits         6102     6102
+ Misses       3503     3502    -1

Impacted Files
Coverage Δ

examples/flava/native/train.py
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Updates analysis

[ ] Add option to make analysis public such that it can be shared via the URL. Let's add a button on the frontend, similar to step5.

[x] @olehkorkh-planeks is there a way to fix the order of the scalar values on the analysis dashboard. It is not ideal that it is always a different order in the scalarplot. Could we add indices to the scalars and sort by indices? Eg, 0_gait_speed, 1_cadence, etc? Or something like that?

@antoinefalisse A partial update with fixing scalar plot ordering:
https://github.com/stanfordnmbl/opencap-viewer/pull/325

Thanks @olehkorkh-planeks, the second task is tested and merged.

Hi @antoinefalisse, There are the pull-requests for sharing public analysis:
Backend - https://github.com/stanfordnmbl/opencap-api/pull/187/files
Frontend - https://github.com/stanfordnmbl/opencap-viewer/pull/336/files

@olehkorkh-planeks thanks it works as expected. However, we cannot have the analyses from all public sessions available to the person who receives the link. Here is a use case. A doctor sends a link to a patient with their analyses (different trials from a session). To do that, the doctor has to make the session public, which is fine. However, we do not want the patient to have access to analyses from another patients, which would be possible with the current implementation. I understand that it is tricky given how the analysis dashboard page is implemented. Do you have any ideas about how sharing could be limited to only the analyses from the shared session?
Another piece of feedback, which might not be relevant depending on how you solve the above. When you click on share analysis publicly, you get a link. But this will only work if the session is public. We should add some logic there. If the session is not yet public, then add a box that says: "Make session public" with a ? that says "To make your analysis public, you need to make your session public". We should then also add a ? on the session side next to Make session public that says "Making your session public will make your analysis public too".
Let me know for questions.

Hi @antoinefalisse

Here is a use case. A doctor sends a link to a patient with their analyses (different trials from a session). To do that, the doctor has to make the session public, which is fine. However, we do not want the patient to have access to analyses from another patients, which would be possible with the current implementation. I understand that it is tricky given how the analysis dashboard page is implemented. Do you have any ideas about how sharing could be limited to only the analyses from the shared session?

OK. I see that we need to generate and use some additional URL parameter for specifying which exact data we want to make accessible. How do you think, can we generate a unique URL for the subject level. In that case, the user will be able to open the link and see only public sessions and trials related to the particular subject. In that case, the Subject select will have only single option. Or maybe we need to generate unique URL for the session? Or for the trial?
Let me know your thoughts.

Another piece of feedback, which might not be relevant depending on how you solve the above. When you click on share analysis publicly, you get a link. But this will only work if the session is public. We should add some logic there. If the session is not yet public, then add a box that says: "Make session public" with a ? that says "To make your analysis public, you need to make your session public". We should then also add a ? on the session side next to Make session public that says "Making your session public will make your analysis public too".

Yes, it will be more clear for user. I'll add that feature.

@olehkorkh-planeks if you generate a URL for the subject, then when you share it from an analysis, will it point to that analysis specifically and then the user can select another public session/trial from the dropdown menu? I think it is important that the URL points to exactly what the sender wants the user to see. So in other words, how would the URL differentiate between an analysis made on 2024-04-30 and 2024-05-25 for instance? If that's possible, then yes I think it is what we want: a URL that points to the analysis, and then the option for the receiver to open the other public sessions from that subject only (and all private sessions if the receiver is signed in and the subject belongs to them).
Also, another piece of feedback. Currently, if you open an analysis through the dashboard list, then it does not retain the id, which is a problem for sharing:

@antoinefalisse

if you generate a URL for the subject, then when you share it from an analysis, will it point to that analysis specifically and then the user can select another public session/trial from the dropdown menu?

Yes. I can add the proper trialId parameter for the currently selected trial.

So in other words, how would the URL differentiate between an analysis made on 2024-04-30 and 2024-05-25 for instance?

As I understand, ther will be two separate trials. Correct? So, we'll be able to generate URLs that will point diretly to the analysis for the proper trials.

Also, another piece of feedback. Currently, if you open an analysis through the dashboard list, then it does not retain the id, which is a problem for sharing

You're right. We can use history.pushState for adding the proper trialId paramater when trial selects.
I also improve the sharing with adding extra parameters, like subject id and a some generated token. The backend will verify the token and returns the data for the proper subject.


Chat icon appears in sidebar but content remains blank

Happens to me a few times when a new window opens. It seems the windows usually have history, so it might be a race condition when past state is loaded.
After startup, I open the secondary sidebar. Chat remains blank until I click the icon. Then the previous history is loaded and shown as expected.

No errors in output or devtools.

This is the view being restored, but not visible. I have seen this from time to time with the output view in my own secondary sidebar

Still happening for me every time a window is being restored with right sidebar open.


Restore ability to explicitly configure field name that differs from property name

We made the decision that during EF Core 3.0 we would re-enable configuration like this, after breaking it in preview 4. From the breaking change documentation:

Mitigations
Field-only properties must be named the same as the field they are mapped to. In a later preview of EF Core 3.0, we plan to re-enable explicitly configuring a field name that is different from the property name:
modelBuilder
   .Entity<Blog>()
   .Property("Id")
   .HasField("_id");

Unfortunately it seems we missed doing this before GA.
@AndriySvyryd I did a quick search to see if we already had a duplicate for this and I didn't find it, but maybe you know where it is.

https://github.com/aspnet/EntityFrameworkCore/issues/15307

Closed as duplicate of #15307.


load proxy account register upon enclave start up

Upon start up, the stateless enclave does not know of previously registered proxy accounts. Because the proxies are stored onchain with the proxy pallet, it would be reasonable to get the accounts from the chain when the enclave chain relay is first initialised.
Suggested approach: Upon worker start up, the worker calls into the chain storage via the substrate-api-client (rpc interface) to get all registered proxy accounts. The enclave is called via ecall (e.g. init_proxy_register(...) and are stored in memory with an atomic pointer
(see https://github.com/scs/substraTEE-worker/blob/master/enclave/src/rpc/worker_api_direct.rs#L85-L107 for an atomic pointer handling example within the enclave)
When designing the enclave in memory storage the following interactions should be possible (maybe it makes sense to provide interface functions? Up to you):

Check if the given AccountID (proxy) is registered
Check if the given AccountID (proxy) and AccountID (main) are assosciated
add proxy account to list
remove proxy account from list

as all direct calls will provide the main account, I guess our proxy registry should be of the form:
map AccountId (main) -> Vec<AccountId (proxy)>

This way, we can lookup the beneficiary account and get ll permissioned proxies so we can check if the signer of the call is in the set.

@ksr30 please check our docs on accessing onchain storage
There is also an example of a storage map in encointer you may want to look at:
https://github.com/encointer/encointer-worker/blob/3be977ba4d8de76ac724f69c7928e67f9dd375d3/stf/src/sgx.rs#L352

Thanks @haerdib @brenzi ... i will look into it

open question:

We can only get read proofs for single storage keys, not for an entire storage_map. This means we somehow need to know all the main accounts that have ever deposited using the ocex pallet. Then we could fetch proxies per main account with read proof

@brenzi , We can define three storage items on-chain
pub struct PolkadexLinkedAccount{
      prev: AccountID,
      next: Option<AccountID>,
      proxies: Vec<AccountID>

}

// Inside the on-chain ocex storage
// We define three storage as given below
decl_storage!{
...
     FirstAccount: T::AcountID
     LastAccount: T::AccountID
     pub mainAccounts get(fn get_main_accounts): map hasher(blake2_128_concat) T::AccountId => PolkadexLinkedAccount;
...
}

The first transaction that adds the registers the first account will set the storage of "FirstAccount" also and subsequent add_account calls will check if FirstAccount is set or not, if it is set, then we just read the struct stored corresponding to the "LastAccount" key from mainAccounts storage map and modify the PolkadexLinkedAccount's prev, proxies, and next fields.
Also we update "LastAccount" storage to the current accountID in question.
Thanks to @ksr30  for the linked list idea!

For the off-chain worker, it can read the "FirstAccount" storage's value and use that to continuously read all the remaining accounts using the next field of the PolkadexLinkedAccount.

An example, where the enclave uses the read_proof with an ocall to the worker:
The enclave calls into the worker to get onchain information (ocall wrapper):
https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/master/enclave/src/lib.rs#L933
actual ocall:
https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/master/enclave/src/lib.rs#L1070
in edl file:
https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/master/enclave/Enclave.edl#L116-L119
ocall on worker side:
https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/master/worker/src/main.rs#L744
in this function, the worker gets the storage by key, including the proof and returns both to the enclave.
The enclave verifies the proof:
https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/master/enclave/src/lib.rs#L983
The StorageProof functions are defined in the chain relay:
https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/master/enclave/chain_relay/src/storage_proof.rs

Issue: If we do an ocall from the enclave to get the account registry, we need to predefine the returned size of the linked list.
Solution proposal: After initialising chain relay, the worker knows of the latest header of the enclave and can get the state & storage proof at this header and do an ecall into the enclave which verifies the storage proof at the latest header.

Possible vulnerability
Mitigation

Worker tampers with account data
storage proof  of linked list

Worker omits ecall init_account_registry
enclave will omit an error without initialised registry when syncing chain relay

Worker ecalls init_account_registry before initialising chain relay, no validator set
enclave fails unsealing a validator and returns an error

Worker ecalls init_account_registry and afterwrads reinitialisises the chain relay. The worker includes a linked list of accounts with a matching storage proof. The enclave will deem the proof and the list correct and initialise the registry. Afterwards the worker inits the chain relay to a different genesis hash, resulting in a mismatch of the registered accounts and the actual chain
When initialising the chain relay, by default the enclave could remove the contents of the linked account registry.

Have I missed anything?

I wonder if we're overengineering here: As we have a single instance of the GW running, that instance will sync the chain from genesis and catch all proxy registrations from then on. Couldn't we just maintain proxies as we do with balances (where we sync all deposit/withdrwaw extrinsics besides direct invoc)?


[stable/postgresql] Add namespace variable to metadata to honor spinnaker helm deployments

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #3988

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @tompizmor

@mruepp can you try this using the namespaceOverride here ? spinnaker/clouddriver#3678


Not working on different clip_model

Thank you for this good open-source repo.
I have tried to change clip_model from ViT-B/32 to ViT-B/16 in demo.
But, with ViT-B/16, zero-shot classification with custom vocab seems not working.
Did you check this clip model before?
Dose detic has a dependency to clip_model?
If not, do you have any idea please?

I found a flag, USE_ZEROSHOT_CLS, which is used in roi_heads and Detic are using pre-computed clip embedding (probably it was from ViT-B/32).
I carefully wonder if zero-shot weights (classifier) are incorporated in Detic training (Probably it is just for prediction after training)
I have not completed reviewing this big repo yet, so my doubt would be wrong.

Hi,
I believe we used ViT-B/32. Did you retrain the model when switching the clip models? It shouldn't work without retraining as different CLIP models give different semantic spaces.
Best,
Xingyi


Check router & vault address against 2 different midgard instances

Overview
Check router & vault address against 2 different midgard instances to be sure one of them isnt compromised
References and additional details
Check router & vault address against 2 different midgard instances to be sure one of them isnt compromised
Acceptance Criteria
Check router & vault address against 2 different midgard instances to be sure one of them isnt compromised
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

blocked. needs for further discussion with @elmutt  @0xdef1cafe @kaladinlight @con5cience

invalid as @kaladinlight  is spinning up our own node soon


Argument parser suggestions function is always called with a terminal command sender context

When registering a custom argument parser. the CommandContext.getSender() always returns the console sender, even when a player is typing the commands.
On paper, this is:
com.destroystokyo.paper.console.TerminalConsoleCommandSender
This is currently rendering personalized suggestions ('suggestions based on what the player can see') impossible.

This seems to work as expected for me:
.withSuggestionsProvider((context, input) -> {
    if (context.getSender() instanceof Player) {
        Player player = (Player) context.getSender();
        ...
    }
    ...
})

https://github.com/Incendo/cloud/blob/a264605cf0d3c6e9a93a83ee4a70a856eb9daa68/cloud-minecraft/cloud-brigadier/src/main/java/cloud/commandframework/brigadier/CloudBrigadierManager.java#L443
this method uses a dummy provider, which is probably where this would be happening then

Yup I am using the brigadier manager, so that would check out

The issue is probably due to this:
https://github.com/Incendo/cloud/blob/e25940b64b2af4b4b116059bda5a06dccd5b5bc5/cloud-minecraft/cloud-bukkit/src/main/java/cloud/commandframework/bukkit/CloudCommodoreManager.java#L58
https://github.com/Incendo/cloud/blob/e25940b64b2af4b4b116059bda5a06dccd5b5bc5/cloud-minecraft/cloud-paper/src/main/java/cloud/commandframework/paper/PaperBrigadierListener.java#L53
https://github.com/Incendo/cloud/blob/fdeaa7d8cc35dd0bee0ab06e3b67915cdbbb11c6/cloud-minecraft/cloud-velocity/src/main/java/cloud/commandframework/velocity/VelocityPluginRegistrationHandler.java#L51
The weird thing is, I was using the brigaider manager in my tests as well. I printout the result of
context.getSender().getClass().toGenericString() in my suggestions provider (ArgumentParser#suggestions), and get
public class org.bukkit.craftbukkit.v1_16_R3.entity.CraftPlayer

I am using the 1.2.0 development branch, maybe this is a bug that was later introduced? Sorry, forgot to mention this

I can confirm this only happens when using the brigadier manager.


Change to radiation storms

Removed the Radiation pulse overlay, made the radiation storms spawn entities that will radiate things near them if they are in range unoccluded. You can spawn radiation pulses from the menu now.
Stopped using pointlightcomponents resyncs to simulate the intensity, changed it to client animations that won't resync.
This is an update of #2948

It seems there is not a easy way to spawn just a shader in an empty sprite at the moment. I asked something related and was told to just add a transparent 32x32 texture.

It seems there is not a easy way to spawn just a shader in an empty sprite at the moment. I asked something related and was told to just add a transparent 32x32 texture.

No progress after 19 days. Closing.


land_detector initiate cycle immediately

fixes #12190

This did not work for me, same error message.

How about now? With uORB::Subscription we no longer have to worry about subscribing in the thread of execution, so some of the awkward startup dance goes away.

Not sure what make of this :smile::
Thread 62 "px4" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffbaffd700 (LWP 32129)]
0x00007ffff7a81eb5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: dnf debuginfo-install libgcc-9.1.1-1.fc30.x86_64 libstdc++-9.1.1-1.fc30.x86_64
(gdb) bt
#0  0x00007ffff7a81eb5 in raise () from /lib64/libc.so.6
#1  0x00007ffff7a6c895 in abort () from /lib64/libc.so.6
#2  0x00007ffff7e0f6da in ?? () from /lib64/libstdc++.so.6
#3  0x00007ffff7e1b61c in ?? () from /lib64/libstdc++.so.6
#4  0x00007ffff7e1b677 in std::terminate() () from /lib64/libstdc++.so.6
#5  0x00007ffff7e1c415 in __cxa_pure_virtual () from /lib64/libstdc++.so.6
#6  0x0000000000469137 in land_detector::LandDetector::_check_params (this=0x7fffac001a10, force=<optimized out>)
    at /home/julianoes/src/Firmware/src/modules/land_detector/LandDetector.cpp:156
#7  0x000000000046a2e9 in land_detector::MulticopterLandDetector::MulticopterLandDetector (this=0x7fffac001a10)
    at /home/julianoes/src/Firmware/src/modules/land_detector/MulticopterLandDetector.cpp:73
#8  0x0000000000468d0e in land_detector::LandDetector::task_spawn (argc=argc@entry=2, argv=argv@entry=0x7fffbaffcba8)
    at /home/julianoes/src/Firmware/src/modules/land_detector/land_detector_main.cpp:74
#9  0x0000000000419816 in ModuleBase<land_detector::LandDetector>::start_command_base (argv=0x7fffbaffcba8, argc=2)
    at /home/julianoes/src/Firmware/src/platforms/px4_module.h:317
#10 ModuleBase<land_detector::LandDetector>::main (argc=3, argv=0x7fffbaffcba0) at /home/julianoes/src/Firmware/src/platforms/px4_module.h:140
#11 0x00000000005af402 in px4_daemon::Pxh::process_line (line="land_detector start multicopter", silently_fail=silently_fail@entry=true)
    at /usr/include/c++/9/bits/basic_string.h:401
#12 0x00000000005af810 in px4_daemon::Pxh::process_line (line="land_detector start multicopter", silently_fail=silently_fail@entry=true)
    at /usr/include/c++/9/bits/basic_string.h:1031
#13 0x00000000005b07f2 in px4_daemon::Server::_handle_client (arg=0x7ffff0000b40) at /home/julianoes/src/Firmware/platforms/posix/src/px4_daemon/server.cpp:278
#14 0x00007ffff7f835a2 in start_thread () from /lib64/libpthread.so.0
#15 0x00007ffff7b45163 in clone () from /lib64/libc.so.6

Hi @dagar, I flight tested this PR and it's working quite right, it doesn't detect properly:
https://review.px4.io/plot_app?log=b5b3bc76-c1d3-445c-a29a-484a254a70ae

The problem was the _check_params(true) call in the constructor of LandDetector() (the base class). LandDetector::_update_params() is pure virtual.


Configurable editor should auto fill the data

Description:

When there is a  Config.toml  with the required values. It should populate the configurable form with the given values.
Describe your problem(s)
Describe your solution(s)
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Closing since we have disabled the config editor


Output CA certificate for Cassandra service

What is currently missing?
Exported/Read-only value for the CA certificate that is created with the Cassandra service. This would be good to easier access it in automation scripts.
If applicable to other services I think it would be a good addition to them as well.
How could this be improved?
Export the certificate so it can be an output.
Is this a feature you would work on yourself?

[ ] I plan to open a pull request for this feature.

@mdanielolsson Cassandra service CA certificate can be found in the aiven_project resource https://registry.terraform.io/providers/aiven/aiven/latest/docs/resources/project#ca_cert. It is unique for all the services in the project.


Offline support

Amazing work.
If I may suggest something -
the current solution embeds the bundle from unpkg. This is great for using the latest when internet connectivity is available, but when it is not, ideally I think there should be a local dist (even if it ends up a bit outdated, it is better than nothing)
https://github.com/bipinkrish/vscode-pose/blob/main/src/poseViewerProvider.ts#L51

Good idea, i will try to implement it as soon as possible

done in v0.0.3


how to make bg transparent

the title says it all

I think you can set these highlight group
highlight link NotifyERRORBody Normal
highlight link NotifyWARNBody Normal
highlight link NotifyINFOBody Normal
highlight link NotifyDEBUGBody Normal
highlight link NotifyTRACEBody Normal

There is a background_colour setting which you have to set to a colour value if you want a transparent background. This colour is used to calculate the highlight when changing opacity. The colour should be whatever your terminal background is

so how to make it transparent? :/

Your terminal must be transparent. Your Normal highlight must not have a background highlight set i.e. termbg=none

hmm i set normal=none

What do you mean you set normal=none? As in you've set the guibg for the Normal highlight to none? If so then you have a transparent background, you need to make your terminal emulator transparent as well if you want a transparent effect over other windows/the desktop

    hl(0, "Normal", { bg = "none", sp = "none" })

this is what i use

So then your neovim background is transparent, your terminal is what is not transparent. Configure your terminal to use transparency


Function 20 Causes Abrupt Exit

When run on a Tacoma (which does not have the motherboard D-Bus Object)
Function Number20
sd_bus_call: org.freedesktop.DBus.Error.UnknownProperty: Unknown interface xyz.openbmc_project.Inventory.Decorator.Asset or property SerialNumber.sd_bus_call: org.freedesktop.DBus.Error.UnknownObject: Unknown object '/xyz/openbmc_project/inventory/system/chassis/motherboard'.Segmentation fault (core dumped)

This should be handled gracefully and FF should be shown to indicate failure.

Need to check Tacoma for latest sdbusplus patch.


Update CDN link

Description
Updates the README.md with the newest version of the CDN link to the browser version.

There are some issues with your commit and our naming convention

Commit: 2db64074fe4450a861bc67201fcdabef71452dad
Don't use more than 72 characters per line in the body of your commit. If you reach this limit at the same line, just break and continue at next line. To separate paragraphs, leave a blank line between them.
Commits must be in the following format: %{context}: %{description}

The complete commit style guide is available at https://github.com/pagarme/git-style-guide

This message was auto-generated by https://gitcop.com

There are some issues with your commit and our naming convention

Commit: 2db64074fe4450a861bc67201fcdabef71452dad
Don't use more than 72 characters per line in the body of your commit. If you reach this limit at the same line, just break and continue at next line. To separate paragraphs, leave a blank line between them.
Commits must be in the following format: %{context}: %{description}

The complete commit style guide is available at https://github.com/pagarme/git-style-guide

This message was auto-generated by https://gitcop.com

There are some issues with your commit and our naming convention

Commit: f519abd9a2e69144beff9ca4bdb902f3441cc7a2
Don't use more than 72 characters per line in the body of your commit. If you reach this limit at the same line, just break and continue at next line. To separate paragraphs, leave a blank line between them.

The complete commit style guide is available at https://github.com/pagarme/git-style-guide

This message was auto-generated by https://gitcop.com

There are some issues with your commit and our naming convention

Commit: f519abd9a2e69144beff9ca4bdb902f3441cc7a2
Don't use more than 72 characters per line in the body of your commit. If you reach this limit at the same line, just break and continue at next line. To separate paragraphs, leave a blank line between them.

The complete commit style guide is available at https://github.com/pagarme/git-style-guide

This message was auto-generated by https://gitcop.com


chore(client): tweaks

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
685

Relevant Lines:
1677

💛  - Coveralls