fix(yabloc_pose_initializer): disable downloading artifacts by default

Description

Other packages that use artifacts, have a DOWNLOAD_ARTIFACTS option, so that they can be built without access to the internet (e.g. when built with Debian's sbuild). This PR adds such option and defaults it to off.
See https://github.com/autowarefoundation/autoware-deb-packages/issues/18
Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@esteve Hi! I think this PR looks good.
However, I noticed that lidar_apollo_instance_segmentation also downloads files using CMake, but I'm curious why it doesn't result in any errors. If you don't mind, could you please provide an explanation? I would appreciate it.

@KYabuuchi thanks for the feedback. We're currently not building lidar_apollo_instance_segmentation as part of https://github.com/autowarefoundation/autoware-deb-packages, because it depends on TensorRT (https://github.com/autowarefoundation/autoware.universe/blob/main/perception/lidar_apollo_instance_segmentation/CMakeLists.txt#L15).
However, if we ever include it as part of the autoware-deb-packages repository, we'll have to disable automatic downloading of the artifacts. Moreover, we have https://github.com/autowarefoundation/autoware.universe/issues/3137 which does disable downloading artifacts in lidar_apollo_instance_segmentation and other packages.

I understand. It makes sense now. :+1:

@KYabuuchi thanks for approving this PR, I will merge it and add it to the list of PRs that disable downloading artifacts by default.


modify pattern restrictions to support properties

e.g. ${logLevel:-INFO} to use System.getProperty("logLevel") if it exists or INFO otherwise

Can you tell me where IF EXISTS is defined in the manual of logback?
I could only find the variable substitution
http://logback.qos.ch/manual/configuration.html#variableSubstitution

For documentation, default substitution has a very short blurb.
http://logback.qos.ch/manual/configuration.html#defaultValuesForVariables


dirPagination: No way to access paginate controller from "outer" controller.

I can't find a way to access the paginate controller from the controller handling the view I'm using pagination in.
For example, accessing the pagination controller and telling it to go to the last page is not possible as far as I can see. I can only access the __default__currentPage variable, but not the controller itself and its properties.
Version: most recent.

Changing __default__currentPage didn't work, but making the paginator use pagination.currentPage did. Weird.


After commit 'e645dfc0' I'm unable to load swagger service from url.

Actually adding description this time.
Receiving the following when invoking SwaggerService.FromUrl:
{
  "Message": "An error has occurred.",
  "ExceptionMessage": "Could not load type 'System.Net.WebClient' from assembly 'NSwag.Core, Version=2.10.5958.26958, Culture=neutral, PublicKeyToken=c2d88086e098d109'.",
  "ExceptionType": "System.TypeLoadException",
  "StackTrace": "   at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName)
at System.RuntimeType.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)
at System.Type.GetType(String typeName, Boolean throwOnError)
at NSwag.SwaggerService.FromUrl(String url)

..SNIPPED.."
}

Any guidance would be greatly appreciated.  This is in a WebAPI application, but is parsing Swagger contracts, not producing them.

On what platform are you calling the method? It is only supported on the full .NET 4.5+...

Target framework is 4.5.2 and this is not a portable assembly.
I will work on a sample application for you.

Reproducible here:
SwaggerRepro.zip

ok fixed in v2.11

Thanks so much for the quick turnaround.  Thanks for the project as well.

Thanks for using NSwag


Execute the "Mining now"

Execute the Allocator.allocate each the metrics when click the "Mining now" link.

Allocator.allocate API is here:  https://github.com/dev-protocol/dev-kit-js/blob/master/lib/allocator/allocate.ts


Defined plugins in 'custom.plugins' are not synced

The latest change introduced the option to use a seperate file for defining plugins ootb. At least on my machine, this does not seem to work as expected.
How to reproduce

check out kickstart.nvim in ~/.config/nvim
add file lua/costum/plugins.lua
copy relevant snippet from Readme
save and reopen neovim
run :PackerSync
no new plugins are added :(

Can anybody reproduce this, or is there something wrong with my setup?  Thx

can you show your exact custom/plugins file? And to be clear, you put it in custom/plugins not costom/plugins right?

Sorry for the late reply. Had the chance to try this on a different machine today... It works just fine!
I assume PEBKAC on my last attempt - sorry for the inconvinience!

Sorry for the late reply. Had the chance to try this on a different machine today... It works just fine!
I assume PEBKAC on my last attempt - sorry for the inconvinience!

No problem at all :)  have a good day

I'm seeing the exact same behaviour here.
My $HOME/.config/nvim/custom/plugins.lua:
return function(use)
  use({
	'nvim-tree/nvim-tree.lua'
	config = function()
		require("nvim-tree").setup()
	'nvim-tree/nvim-web-devicons'
	end
	})

I think the file needs to be located at
$HOME/.config/nvim/lua/custom/plugins.lua

Yes, sorry - my mistake... :(

However, it would seem that the custom/plugins.lua is only read for config of the plugin. Packer doesn't seem to see any plugins included in it...
I now have 3 plugins configured in it:
return function(use)
-- Configure nvim-tree
  use({
	'nvim-tree/nvim-tree.lua'
	config = function()
		require("nvim-tree").setup()
	'nvim-tree/nvim-web-devicons'
	end
-- Add friendly snippets
  use({
	'rafamadriz/friendly-snippets'
	config = function ()
		require("friendly-snippets").setup()
	end
	})
end

and it never installs 'friendly-snippets', and if I run PackerSync manually it always asks if it can remove the unused nvim-tree plugins... (which were installed when I had them in init.lua, which was when I had the wrong path to my custom/plugins.lua)
What am I doing wrong?

I'd guess it's these (rather than ~/.config/cache/nvim) that I should remove?

However a :PackerInstall does nothing...

I'm pretty sure though, that if I were to remove the above I would no longer have the nvim-tree plugin installed...

You can remove ~/.local/share/nvim, it will reset your config and reinstall everything (you may have to restart neovim a couple of time for everything to be set up).
I don't knwow if the custom/plugins.lua you showed is only a snippet or the entire file. If it is the entire file, a }) is missing, also nvim-web-devicons should be required. Here is the file with the corrections :
return function(use)
-- Configure nvim-tree
  use({
	{'nvim-tree/nvim-tree.lua', requires = 'nvim-tree/nvim-web-devicons'},
	config = function()
		require("nvim-tree").setup()
	'nvim-tree/nvim-web-devicons'
	end
	})
-- Add friendly snippets
  use({
	'rafamadriz/friendly-snippets'
	config = function ()
		require("luasnip.loaders.from_vscode").lazy_load()
	end
	})
end

Ok, thanks - but still - no install of the plugins in the custom file.
I did remove ~/.local/share/nvim and when I restarted it re-installed everything again - but not the plugins in the custom file:

Albeit it does look for it since I've configured it...
Error detected while processing /Users/jonasb/src/jby/nvim/after/plugin/defaults.lua:
E5113: Error while calling lua chunk: /Users/jonasb/src/jby/nvim/after/plugin/defaults.lua:4: module 'nvim-tree' not found:
        no field package.preload['nvim-tree']
        no file './nvim-tree.lua'
        no file '/usr/local/share/luajit-2.1.0-beta3/nvim-tree.lua'
        no file '/usr/local/share/lua/5.1/nvim-tree.lua'
        no file '/usr/local/share/lua/5.1/nvim-tree/init.lua'
        no file '/Users/jonasb/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/nvim-tree.lua'
        no file '/Users/jonasb/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/nvim-tree/init.lua'
        no file '/Users/jonasb/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/nvim-tree.lua'
        no file '/Users/jonasb/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/nvim-tree/init.lua'
        no file './nvim-tree.so'
        no file '/usr/local/lib/lua/5.1/nvim-tree.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
        no file '/Users/jonasb/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/lua/5.1/nvim-tree.so'
stack traceback:
        [C]: in function 'require'
        /Users/jonasb/src/jby/nvim/after/plugin/defaults.lua:4: in main chunk

Hmm, my ~/.config/nvim/lua/custom/plugins.lua doesn't even seem to be read even if I ignore the logic that's supposed to look for it and manually specify it in init.lua like this:
(require 'custom.plugins')

My ~/.config/nvim/lua/custom/plugins.lua now:
return function(use)
  -- Configure nvim-tree
  use({
    {'nvim-tree/nvim-tree.lua', requires = 'nvim-tree/nvim-web-devicons'},
    config = function()
      require("nvim-tree").setup()
      'nvim-tree/nvim-web-devicons'
    end
  })
  -- Add friendly snippets
  use({
    'rafamadriz/friendly-snippets',
    config = function ()
      require('luasnip.loader.from_vscode').lazy_load()
    end
  })
  -- // Comment.nvim
  use {
    'numToStr/Comment.nvim',
    config = function()
      require('Comment').setup()
    end
  }
end

The only way, so far I get the plugins I want to add to actually be installed and used is to add them to init.lua...
Doesn't that kind of make the custom.plugins rather useless?

Doesn't that kind of make the custom.plugins rather useless?

Sure but it seems that you are the only one with this problem, I'm sorry, I'm running out of ideas.

I kind of feel like I've hi-jacked someone else's, already closed, issue here. Maybe I should create my own instead?

Created #176 instead


How to cancel autocomplete-plus when running a line or cell in Hydrogen?

Not sure whether this question is best posted here, in the autocomplete-plus issues or on StackOverflow, but I figured I'd give it a shot.
When I hit cmd-enter to run a line in Hydrogen, the autocomplete-plus suggestion box stays open and I have to then hit escape to close it. How can I get cmd-enter to both run a line and cancel autocomplete-plus?
I can add this to my keymap:
'body atom-text-editor.autocomplete-active':
  'cmd-enter': 'autocomplete-plus:cancel'

but then cmd-enter overrides Hydrogen, so I have to hit it again to run the line.
Per this, I probably have to do a composed command but I don't know what code to put in there for either the Hydrogen or the autocomplete-plus command.
Would love any suggestions, thanks!

I believe that autocomplete-plus automatically removes the tooltip when the cursor moves. So I never have this problem because I always use Shift+Enter instead of Ctrl+Enter.
Regardless, for Ctrl+Enter we could probably tell the autocomplete tooltip to close, assuming that it wouldn't raise an exception if the tooltip is already closed.

That's right that there's no issue with shift-enter (which I never use).
Would be great to close the tooltip on cmd/ctrl-enter as well as cmd/ctrl-alt-enter (which runs the cell and also doesn't move the cursor and close the tooltip).

Put this in your init script. Kind of an edge case in my view, but you can make a pull request if you think this should be built in to hydrogen.
function cancelAutoComplete() {
  // `this` will be bound to the dom node that `hydrogen:run`
  // was called on https://atom.io/docs/api/v1.31.2/CommandRegistry#instance-add
  atom.commands.dispatch(this, "autocomplete-plus:cancel");
}
atom.commands.add("atom-text-editor.autocomplete-active", {
  "hydrogen:run": cancelAutoComplete,
  "hydrogen:run-cell": cancelAutoComplete
});

Thanks, love it! I would expect that I'm not the only person running hydrogen and autocomplete-plus (both at about 700k downloads) who would like this to be built in. I'd do a PR but I just took a spin through the code and am not sure where your addition would go.

I think I'd do this differently if I were building this into hydrogen, as opposed to an init script solution.
I would probably put this line in both run() and runCell() in lib/main.js right after the if (!editor) return; line:
// https://github.com/nteract/hydrogen/issues/1452
atom.commands.dispatch(editor.element, "autocomplete-plus:cancel");

@BenRussert 	I agree about how you would implement that if you put it into Hydrogen. Do you think it should be included rather than via init? It's something I've never come across because 1) I usually use run-and-move-down and 2) when using run I never call it while my cursor is in the middle of an autocomplete suggestion... I always would hit tab to complete first...

when using run I never call it while my cursor is in the middle of an autocomplete suggestion... I always would hit tab to complete first...

In my case, I rarely actually use autocomplete. 95% of the time my habit is just to finish typing the command. I only complete the suggestion when, e.g., a variable name is particularly long, or I'm using autocomplete to browse through an object's methods. Perhaps other users use it like this too.

I'll defer to @BenRussert

I'd be ok with a pull request, I'll leave it up for grabs.

Oh, and @kylebarron, there shouldn't be side effects as the dispatch will fail silently if auto complete isn't active.


Includes don't work for many to many relations

Hi guys! Now I'm creating my first project with adonisJS and in fact i enjoy it at all, but there is a problem with bumblebee transformer and i could not find any solution for that. When I use "include" method in transformer for many to many relations - it doesn't work and there is no kind of error, it just ignores relations. I'm doing all straight by docs, "include" works for belongsTo relations and doesn't work for "pivot table" to get all related entities for transforming model. Can you help me and describe why it does't it work properly with many to many relation, how could you miss that moment (i don't believe you could, but it seems to me that it's a pure fact) and which solution for many to many relations in transformer i can get out from box? Thank you!

Finally i have found the solution - just remove "static get" before include${relation}... damn...

I'm sorry. This might have been my fault. The documentation in the repository shows changes for the upcoming 2.0 release. I will fix this shortly.
Hope you enjoy adonis and my bumblebee addon.

Thank you! I really enjoy adonis and your addon and wish you good luck with it)

Thanks a lot, @TwoLiquid ... I spent hours trying to figure this out too. I think it would be great to mention this in the docs (removing the "static get" in front of defaultInclude() in transformer class,) in the case of Many to Many Relationships because the "static get" gives errors.


Add retries to Merritt ATOM feed

We're getting some 5xx errors back from Nuxeo when fetching metadata

Implemented by this commit: https://github.com/ucldc/nuxeo_merritt/commit/7e264c972bc4e713fdab266f45050100d1598da7
I bypassed the PR-to-merge requirement by accident...


Editing the prefix, breaks the prefix.

Hey,
I just found out this bug that if you edit the prefix or suffix in the web UI it changes it to the HTML code "&" instead of just leaving it as just "&".
Output:

This only happens if you select prefix node. If you don't touch it, it wont break.

@BrainStone any ideas?

I'll look into it.
@Golumpa if you can recreate it and paste the command here that you get when you click save would be nice. Like for example break one prefix but not the other.

@BrainStone Sure,
/lp applyedits 91462954c5b9c2d88f492c979889af6c/d47294a8a3386033d7365f575b47fee9165a2625
prefix.1, has been untouched
prefix.2, I clicked on it like I was going to edit it


Removed error message when file is broken symlink

Removed error message when attempting to make a hyperlink to a broken symlink. This shouldn't be an issue, since the user is already warned of a broken symlink.
TODO

[X] Use cargo fmt
[X] Add necessary tests
[X] Add changelog entry
[X] Update default config/theme in README (if applicable)
[X] Update man page at lsd/doc/lsd.md (if applicable)

Codecov Report

Merging #663 (9af080e) into master (dd2ef0a) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #663      +/-   ##
==========================================
- Coverage   86.55%   86.47%   -0.08%
==========================================
  Files          40       40
  Lines        4380     4384       +4
==========================================
  Hits         3791     3791
- Misses        589      593       +4

Impacted Files
Coverage Δ

src/meta/name.rs
89.21% <0.00%> (-1.35%)
:arrow_down:

Continue to review full report at Codecov.

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


Support variable-sized perf event array outputs

Currently Aya sets a generic type T for all PerfEventArray<T> objects, which requires T to have a fixed size known at compile time.
We have a use case where we want to transfer byte arrays/slices through a PerfEventArray (for data serialization & deserialization), but the size of these slices is not constant. It varies a lot depending on the data.
Currently, we can only do this with Aya's PerfEventArray::output()/PerfEventArray::output_at_index() functions by padding our data to a fixed size. This is not ideal. as the data size can vary a lot we may have to waste quite a few bytes.
As I understand the underlying helper function, bpf_perf_event_output() bpf-helper docs it actually supports variable sized data via a length parameter. This is set to a constant value by Aya.
What we would like is an additional output() function that accepts arbitrary data/bytes/slices with varying length. Of course the maximum length cannot exceed the total perf event array size, but sizes smaller than this should be accepted.

I think you're looking for this? https://docs.aya-rs.dev/bpf/aya_bpf/maps/struct.perfeventbytearray

I swear I looked through the code, but I must have been completly blind.  Thanks!


Empty page on Kitties Tutorial

What browsers are you seeing the problem on?
Firefox Developer Edition 95.0b8 (64-Bit), Ubuntu 20.04.3 LTS
Bug report for the website
Got an empty page when visiting https://docs.substrate.io/tutorials/v3/kitties/pt1/
with the following error in the console:
Uncaught TypeError: can't access property "map", n is undefined
    l DocsNav.tsx:78
    React 7
    unstable_runWithPriority scheduler.production.min.js:18
    React 6
    unlisten index.js:144
DocsNav.tsx:78:15

Steps to reproduce the problem
Goes away after hard reload (ctrl + shift + r).

@imadarai this is an ongoing issue systemic to our hosting: I need to use hard reload (ctrl + shift + r) very often because links just "don't work" on the site very often on firefox.
It's a massive pain :crying_cat_face: and not intuitive for others that I am sure must be running into this to use this method to rectify it.

@apopiak @NukeManDan
Thanks for pointing this out.
It seems like a cache issue, mainly stemming from PWA functionality.  I baked this in, because I thought people might want to add Substrate Docs as a PWA and utilize it on the go.  What I didn't anticipate was how frequently we'll be changing and updating core things like DocsNav etc.
I'll try a fix, and if the problem persists will just have to remove the PWA functionality all together.


Add missing user property

Purpose
Add missing property, left off from modm User.
Changes
Added property.
Side effects
None known of.
Ticket
Fixes https://travis-ci.org/CenterForOpenScience/osf.io/jobs/193915259#L1634 @icereval

👍


fix: segment track cleanup

fix: segment track cleanup
This PR:

Fixes genConfig to generate contribution points in package.json to only contain properties that vscode define.
Removes a redundant setupSegmentClient call
Removes properties in CommandEntry that were used to generate dendron.cheatsheet note from jinja template.
Corrects the when clause for displaying Dendron: Delete Node in explorer/context
Adds when clause to all views that are not functional when the user is not in a workspace that dendron recognizes.
Adds when clause to all commands that are not functional when the user is not in a workspace that dendron recognizes.

This is to reduce clutter in the command palette and also to avoid confusion to users that are new to Dendron and as yet to initialize a Dendron workspace.
This will also prevent a significant amount of error reporting since most of the non-functional commands will cause an engine not set error or similar.
The only commands that will be available in the command palette when in a non-dendron workspace will be the following:

Dendron: Launch Tutorial
Dendron: Initialize Workspace
Dendron: Change Workspace
Dendron: Enable Telemetry
Dendron: Disable Telemetry
Dendron: Sign Up
Dendron: Sign In
Dendron: Contribute
Dendron: Show Help
Dendron:Dev: Open Logs

Pull Request Checklist
If this is your first time submitting a pull request to Dendron, copy and paste the full Dendron Review Checklist into this request and check off each item as necessary.
This template contains the short checklist which is used by the Dendron core team.
Testing

[ ] Write Tests
[x] Confirm existing tests pass
[x] Confirm manual testing
[ ] If your tests changes an existing snapshot, make sure that snapshots are updated
[ ] If you are adding a new language feature (graphically visible in VS Code/preview/publishing), make sure that it is included in the test workspace

Docs

[ ] if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR

Analytics

[ ] if you are adding analytics related changes, make sure the Telemetry docs are updated

Just noticed that Dendron: Show Help links to dendron.cheatsheet in our wiki. now that we are not doing this anymore should we remove this command altogether? (and also remove the jinja template and the gen:cheatsheet task).
The when clauses have made the Show Help command much more visible to users when they are in a non-dendron workspace and I don't think opening a link to a note that has a #prune tag would be ideal

Just noticed that Dendron: Show Help links to dendron.cheatsheet in our wiki. now that we are not doing this anymore should we remove this command altogether? (and also remove the jinja template and the gen:cheatsheet task).
The when clauses have made the Show Help command much more visible to users when they are in a non-dendron workspace and I don't think opening a link to a note that has a #prune tag would be ideal

Maybe redirect to the FAQ? https://wiki.dendron.so/notes/683740e3-70ce-4a47-a1f4-1f140e80b558/

Just noticed that Dendron: Show Help links to dendron.cheatsheet in our wiki. now that we are not doing this anymore should we remove this command altogether? (and also remove the jinja template and the gen:cheatsheet task).
The when clauses have made the Show Help command much more visible to users when they are in a non-dendron workspace and I don't think opening a link to a note that has a #prune tag would be ideal

Maybe redirect to the FAQ? https://wiki.dendron.so/notes/683740e3-70ce-4a47-a1f4-1f140e80b558/

hmm I don't know.. Linking to a collection of random bits of knowledge would confuse a user even further I imagine. This is a command that is very rarely used, and probably something we want to improve in another PR anyways. Disregard my comment.

@hikchoi yeah, lets add show help in another section. instead of going to a page, we might even want to do something interactive

@hikchoi yeah, lets add show help in another section. instead of going to a page, we might even want to do something interactive

Yeah I was also considering a web view that can generate something like what the jinja template was originally doing that can interactively help the user.


[Autocomplete] multiple, filterSelectedOptions, autoHighlight stops working after "no options" state

Autocomplete with flags multiple, filterSelectedOptions, autoHighlight has an issue with autoHighlight stopping working after reaching state "No options" when entering text. Only after user explicitly selects an option from the list (either by mouse click or by arrow-down key), it starts working again.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
For Autocomplete multiple with autoHighlight and filterSelectedOptions, there are issues with auto-highlighting after a user enters text resulting in "No options" state. After reverting, by using Backspace key, the options again are shown, but auto-highlighting no longer works.
Expected Behavior 🤔
After reverting the text, so that "No options" state disappears and options are shown, the matched option should be highlighted again.
Steps to Reproduce 🕹

See code-sandbox - Autocomplete multiple with autoHighlight and filterSelectedOptions.
To reproduce:

Enter text "pulp"
the "Pulp Fiction" option gets highlighted
Add more text like "xxxx"
the "No options" message shows up
Use backspace key to revert and remove "xxxx", and leave the text "pulp" again
No option is highlighted (BUG)

Context 🔦

Your Environment 🌎

Tech
Version

Material-UI
v4.11.0

React
v16.13.1

Browser
Google Chrome 86

TypeScript
v3.8.2

etc.

Fixed in #23025, demo: https://codesandbox.io/s/material-demo-forked-tgf0z?file=/package.json


Psi update

This PR needs to be merged to have compatibility with the new master of PowerSystems.
Also solves the testing of PTDF by adding a new solver to substitute for Ipopt in overspecified LQ models.

Codecov Report

Merging #131 into master will decrease coverage by 1.73%.
The diff coverage is 39.13%.

@@            Coverage Diff             @@
##           master     #131      +/-   ##
==========================================
- Coverage   87.17%   85.44%   -1.74%
==========================================
  Files          44       44
  Lines         889      907      +18
==========================================
  Hits          775      775
- Misses        114      132      +18

Impacted Files
Coverage Δ

...rc/devices/device_constructors/load_constructor.jl
70.37% <ø> (-20.11%)
:arrow_down:

src/core/core_structs/operation_model.jl
100% <ø> (ø)
:arrow_up:

...rc/network/network_models/powermodels_interface.jl
99.09% <ø> (ø)
:arrow_up:

.../devices/device_constructors/branch_constructor.jl
100% <ø> (ø)
:arrow_up:

src/devices/device_models/common/cost_functions.jl
100% <ø> (ø)
:arrow_up:

src/core/core_structs/service_model.jl
100% <ø> (ø)
:arrow_up:

src/operation_models/economic_dispatch.jl
100% <ø> (ø)
:arrow_up:

src/network/network_constructor.jl
100% <ø> (ø)
:arrow_up:

src/devices/device_models/common/pm_translator.jl
88.88% <ø> (ø)
:arrow_up:

src/operation_models/opf.jl
100% <ø> (ø)
:arrow_up:

... and 11 more

Continue to review full report at Codecov.

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


Refactoring/1409/remove constructor

Description
removed constructor-page
Checklist

[ ] 🔽 My branch is up-to-date with "development" branch
[ ] ✅ All tests passed locally
[ ] ✨ My changes working with up-to-date front-end and back-end part locally, like charm
[ ] 🔗 Link pull request to issue

this PR was made to check if removen constructor-page still affects on app  and check if sonar cloud will pass
also there is a folder components/forms/constructor-form, and files in it were linked in constructor-page im going to check if it is a dead code or not


Add types and data containers for image processing

I've created some basic classes with attributes need to start working on image processing.
In color_format module I have also included two ready-made color formats (RGB3 and BGR3). For now this module can only define RGB-like formats - no YUV support. It should be noted, that YUV support will probably require creating child class expanded with information of every component's placement in one byte.
I thought also about leaving this for parsing utilities and only providing information as a PixelFormat (UYVY etc.) - good source.
image module consists of two classes - first is involved in file parsing and second will be directly used in image processing.
There is an import to numpy - BSD-3 license.
Closes #6
Closes #7

I've created simple unit tests for those two modules using unittest build-in framework.

Great, thanks! Please make sure to add a CI job that actually executes those tests


Update yq image

This PR fixes the yq image to match what Hive is using in their build scripts and updates the select to use the correct name.

/approve


A ichat update2

Ai test case removed

Codecov Report

Merging #22 (e0da381) into main (32d68dc) will decrease coverage by 11.47%.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@             Coverage Diff             @@
##             main      #22       +/-   ##
===========================================
- Coverage   48.14%   36.68%   -11.47%
===========================================
  Files          14       14
  Lines        1431     1431
===========================================
- Hits          689      525      -164
- Misses        742      906      +164

see 7 files with indirect coverage changes


runner.ts: Break into separate functions

PR checklist

[ ] Addresses an existing issue: #0000
[ ] New feature, bugfix, or enhancement

[ ] Includes tests

[ ] Documentation update

Overview of change:
Just a refactor. Breaks apart the class into smaller functions.
Converted it to return a Promise, but the implementation doesn't use Promises yet.

ping here, can you address @nchen63's comments?

According to https://github.com/palantir/tslint/issues/2446#issuecomment-290613113, anything not in index is not public.

fair enough; I assumed it was exported through index.
got a few merge conflicts left though

new conflicts with 2bc8982bfcc5b852c6288b3b231b63024e0e034a :(


Lots of ESENT Errors and stale DB.

I have troubles with the ESENT Database.
All Agents can register for some time, but after 3-5min lots of ESENT errors appears in the Eventlog and no client can't register any more nor get Reports from the pullserver.
The troubles are very similiar like this issue: https://github.com/PowerShell/xPSDesiredStateConfiguration/issues/296
Version of Microsoft.Powershell.DesiredStateConfiguration.Service.dll
10.0.14393.479
PS C:\Windows\system32> $PSVersionTable
Name                           Value

PSVersion                      5.1.14393.1532
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.1532
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
ImplementedAs   Name                      ModuleName                     Version    Properties

PowerShell      xDSCWebService            xPSDesiredStateConfiguration   <IP_ADDRESS>
Eventlogs Message:
w3wp (6392) PSDSCPullSever: The version store for this instance (0) has reached its maximum size of 15Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.
Possible long-running transaction:
SessionId: 0x156E6B00
Session-context: 0x00000000
Session-context ThreadId: 0x00000CBC
Cleanup: 1
Session-trace:
57573@11:50:31
and sometimes:
w3wp (4172) A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation.
See help link for complete details of possible causes.
Previous cache residency state: 100% (4143 out of 4143 buffers) (184 seconds ago)
Current cache residency state:  79% (39107 out of 48972 buffers)
Current cache size vs. target:  100% (191.773 / 191.773 MBs)
Physical Memory / RAM size:     4094.918 MBs
Is it possible, to increase the maximum size of the version store?
Thank you for any suggestion.

w3wp (3044) PSDSCPullSever: An attempt to open the file "D:\DscService\edb.log" for read only access failed with system error 32 (0x00000020): "The process cannot access the file because it is being used by another process. ".  The open file operation will fail with error -1032 (0xfffffbf8).
w3wp (3044) PSDSCPullSever: Error -1032 (0xfffffbf8) occurred while opening logfile D:\DscService\edb.log.

@Outek If this is still a problem I suggest you report this as a problem to Microsoft Support to see if you can get help trough there.

Following this release of Windows Pull Server, there are no additional plans to release new features to the pull service capability in Windows Server. Support for Windows Pull Server in production environments will continue following the Windows Server support lifecycle.
Windows Pull Server Planning Update – April 2018

Closing this as external since we can't resolve this in this resource module.


common

[ ] blog-posts
[ ] cell-channels
[ ] coalition-memberships
[ ] directories
[ ] discussion-channels
[ ] file-versions
[ ] files
[ ] locations
[ ] notes
[ ] org-chart-position-graph
[ ] org-chart-positions
[ ] organizations
[ ] people-graph
[ ] people-to-org-relationships
[ ] posts


Accumulo 1.9.3 RegexExample job failed because of Exception  org/apache/commons/configuration/CompositeConfiguration

I tried to run this example
bin/tool.sh lib/accumulo-examples-simple.jar org.apache.accumulo.examples.simple.mapreduce.RegexExample -u root -p 1 -i project -t rya_po --rowRegex 'Prot.*' --output output
but I got this Exception
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/configuration/CompositeConfiguration
I use this versions:
accumulo-1.9.3, hadoop-3.1.2, zookeeper-3.4.14
and I added the Hadoop class paths to accumulo-site.xml
any suggestions please?
I've to use those versions because I'm using Apache Rya with'em

Hi @metsy . Based on the exception, it seems you are missing commons-configuration on your class path. Without a full stack trace, it will be hard to determine which specific part of our code was looking for commons-configuration. However, if you put that on your class path, it should solve your problem. The tool.sh script was written to help add some things to your local class path, as well as the class path for the submitted MapReduce job. Perhaps it isn't picking up your commons-configuration jar? Or perhaps there's a conflict with the version that ships with Hadoop or ZooKeeper?
It looks like Accumulo 1.9.3 was built with commons-configuration 1.6, based on what we had in our pom.xml, but please note that 1.9.3 has been superseded by 1.10.0, and is no longer supported.
I hope this response helps answer your question. If you have any further questions, please consider subscribing to our user list and asking on that forum, as this issue tracker is primarily for tracking issues during development. Other users may have experienced similar issues, and solved them already, and may be able to help you further on the user list. See https://accumulo.apache.org/contact-us/ for more information about subscribing to our mailing lists.

Thanks @ctubbsii


Allow all admins to update results for all projects

Will rely on me finally getting this done!
https://github.com/Scifabric/pybossa/issues/1530

Not implementing with move to simple headless server


Add scripts compatible wtih smollm-corpus

This adds scripts for compatibility for the smollm-corpus:
https://huggingface.co/datasets/HuggingFaceTB/smollm-corpus

Looks good, I think the checks should work now that the typing extensions has been updated.

Tests actually aren't affected by any of the code changes, which look good, merging.


In some cases when xml syntax is invalid, NBi returns an object reference not set

Try with following xml and you'll receive an NullReferenceException on line 69 of XmlManager
<?xml version="1.0" encoding="utf-8" ?>
<testSuite name="My first test suite" xmlns="http://NBi/TestSuite">
 <test name="My first test">
  <system-under-test>
   <execution>
    <query connectionString="...">
     <![CDATA[
     SELECT
      {[Measure].[MyMeasure]} ON 0,
      {[MyDimension].[MyHierarchy].Members} ON 1
     FROM
      MyCube
     ]]>
   </execution>
  </system-under-test>
  <assert>
   <equalTo>
    <query connectionString="...">
     SELECT MyHierarchy, MyMeasure FROM MyTable
    </query>
   </equalTo>
  </assert>
 </test>
</testSuite>

Fixed, will be released in 1.10


Fix VM test flakes

Example failure:
https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/25294/integ-ipv6-k8s-tests_istio/1732
What happens is the pod startup just takes a while due to a fresh image
pull. We only wait 30s here - instead we should wait for the full
readiness timeout.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

/retest

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
38556552eaa8df5826d435920cd451d5cb0410e6
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


tests: fix OOM error when running tests in Flink ETL

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
(describe what this merge request does)
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[ ] add new test cases
[x] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting
[ ] streaming ingestion

[ ] with Redshift Serverless
[ ] with provisioned Redshift

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
5.10
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
8
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/18/2024, 09:17:12 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
5.10
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
8
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/18/2024, 09:39:46 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.80
< 80

Duplicated lines density
:white_check_mark: OK
5.10
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
8
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/18/2024, 09:42:58 (UTC+0)

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @amliuyong on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.80
< 80

Duplicated lines density
:white_check_mark: OK
5.10
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
8
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/18/2024, 09:44:34 (UTC+0)


Handling SSL authentication with the basic protocol

I'm working for Bearstech, a web hosting company. Using a mutualized carbon server can be messy with lots of users. For now, I add a stunnerl proxy for using authentication with a lightly patched statsd python clone. AMQP is too heavy, I wont to use simple client, post mortem log reader or statsd like tools.
This blog presents my hack :
http://blog.bearstech.com/2013/03/authenticate-everything-with-ssl.html
Is it possible to let carbon handling such security and authentication?
I would like to publish a pull request, but I had some troubles with Twisted voodoo.

:+1:  Would love to see this as well. Using stunnel in the meantime.


fix bad query in save_relationship_with_id

Description
Fixes the unbound variable error in the return statement of the cypher query in memgraph.save_relationship_with_id().
Pull request type
Bugfix
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Reviewer checklist (the reviewer checks this part)

[ ] Core feature implementation
[ ] Tests
[ ] Code documentation
[ ] Documentation on memgraph/docs

Hi @dadevel! Thank you for catching this and contributing 😄 Is this some feature you need before June 14th?
If not, we will merge this into the develop branch for the next release on June 14th.

Hi @katarinasupe, June 14th is fine by me, I'll use my fork till then, but you might want to release it earlier, because the bug impacts core functionality like Relationship.load().

@dadevel In the end, we will merge this to develop since it must be published on PyPi after the merge, and we think it's okay to have it there in 4 days 😄  Thank you again for your contribution, and let us know if anything else is wrong or create an issue for any new features or bug fixes.


[community] @AndrewZhaoLuo -> Committer

Please join us to welcome @AndrewZhaoLuo as a new committer to TVM.
Andrew has made great contributions, especially to automatic mixed precision (AMP) support and Relay frontends improvements. Andrew is also an easy-to-collaborate person. Specifically, when he files or reviews a PR, he is always open to discuss and accept comments from PR authors and reviewers, which results in a smooth discussion process and could efficiently push the discussion further. In addition, he has been actively participating the forum discussions to address related questions, provide his thought and experience. This greatly helps new community members and makes the community better.

Commits History
Code Review
Community Forum Summary

Hit the flaky segfault https://github.com/apache/tvm/issues/9895, need another run

Congrats!


Allow destroying an invitation

For after #215
Wires up the "X" button to destroy an invitation

@mixonic rebased after #215 and could use a look-over if you would like.
I didn't make a {{destroy-invitation}} component here like the {{resend-invitation}} component, opting to let the route's destroyInvitation action do the async and UI work, because unlike the resend-invitation, destroy-invitation isn't idempotent. By the time the invitation.destroyRecord() promise gets to its then, ember will have pulled that invitation from the controller's model and this row of the table (and the component) will have been removed. In particular, this makes a sendAction from within the component tricky because its targetObject has been nullified at that point.
I toyed with closing over the component's target object but it ended up feeling like too much ember inside baseball, and I let the route's action handle everything.
I don't love the side-by-side resentInvitation (past tense) and destroyInvitation (imperative) actions in the route, though.

dyin' to get new actions. Maybe we can implement them next week, it would need to be on top of Glimmer though.


404 component wip

WIP 404

Hello @justinwhall,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Add documentation about installing botogram on Windows

Based on feedback from an user, the installation of botogram on Windows is quite different than the Linux/OSX, and the documentation doesn't explain it.
It would be good to add a section about it.

Uhm, I'll probably hold off on this, let's see how that GNU/Windows thing goes.


Added String::dedent() to remove text indentation

This functions similarly to Python's textwrap.dedent()
It's also been applied to the built-in help to remove extra whitespace while parsing the XML.

We have strip_edges() is this different?
On Oct 11, 2017 9:46 AM, "Lee Zher Huei"<EMAIL_ADDRESS>wrote:

This functions similarly to Python's textwrap.dedent()
https://docs.python.org/3.1/library/textwrap.html#textwrap.dedent
It's also been applied to the built-in help to remove extra whitespace
while parsing the XML.
You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/12025
Commit Summary

Added String::dedent() to remove text indentation

File Changes

M core/ustring.cpp
https://github.com/godotengine/godot/pull/12025/files#diff-0 (42)
M core/ustring.h
https://github.com/godotengine/godot/pull/12025/files#diff-1 (1)
M core/variant_call.cpp
https://github.com/godotengine/godot/pull/12025/files#diff-2 (2)
M editor/doc/doc_data.cpp
https://github.com/godotengine/godot/pull/12025/files#diff-3 (6)

Patch Links:

https://github.com/godotengine/godot/pull/12025.patch
https://github.com/godotengine/godot/pull/12025.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/12025, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z27cjzRUAMhndZZw5sAndgEHjR8KYks5srLiqgaJpZM4P1adW
.

It is different. It's like split("\n") and then strip_edges() and then join(), but it also tries to preserve indentation levels deeper than the first line.

I'm not sure how well GitHub's markdown is going to handle my example, but text like this:
    line1
        line2
  line3

Would become
line1
    line2
line3

The problem I saw was that the descriptions in the class docs were indented to match the XML tags, and it was carried over when read by the built-in help. This function here helps get rid of that.

I'm fine with adding it if it's needed in the engine (though I wonder if that's the right fix, do you have example of docs that are not indented properly in the editor?), but I don't think it should be exposed to scripting languages.

I found it odd that the paragraph in the KinematicBody had a 1 char paragraph indent

But then the method description had a 3 char paragraph indent.

And that's when I realised it was actually because it wasn't properly cleaning up the XML doc indentation, which was the motivation behind writing this function.
The use case is very niche (probably only ever useful in HTML scraping), but I thought since it was there I might as well expose it to the scripts. If you don't think it should be there I'd be happy to take it out.

Well I guess it's fine as is - just needs a rebase after recent changes.

Done. While I was at it, I did a little extra to double the newlines of descriptions (not part of dedent function) so that it matches the formatting of docs.godotengine.org


CLI boolean options don't work as expected

The following throws an error
$ testacular start --single-run testacular.conf.js

but
$ testacular start --single-run --log-level error testacular.conf.js

and
$ testacular start testacular.conf.js --single-run

The reason is that optimist interprets testacular.conf.js as the value of the option single-run and so the config file isn't defined.
See also substack/node-optimist#42

Super old, please reopen if this is still important.


Cart: Updating qty. permanently disables the field until reload.

Summary
When you update the quantity field of items listed in the cart the fields become disabled and will not enable until the page is refreshed.
Steps to reproduce

Add items to the cart.
Update the quantity.

A link to a reproduction repository
No response
What OS are you using?
No response
Your next.config.js file
No response
Builds logs (or link to your logs)
No response
Function logs
No response

I believe it is related to this issue: https://github.com/apollographql/apollo-client/issues/9602
In order to fix that you need to update Apollo Client. Simply run pnpm i @apollo/client@next and you should be fine :)


Add docs for adWMG Analytics Adapter

According to email which we have received early

Hi, has your adapter code been merged yet?

Hi @MartianTribe ! Yes, it was merged some time ago


Add a mime type and separate modeInfo entry for edn

This allows findModeByName to work for edn and seems more consistent with how JSON is handled.
The mime type isn't official on IANA yet, but there seems to be widespread consensus in the Clojure community on "application/edn".

Note that JSON actually needs to be parsed differently, which isn't the case here, right? But still, people might want to show the language name to the user somehow, in which case having a separate entry makes sense. Merged as 8799d1d4fb325

Thanks!
In regard to parsing edn differently, afaik edn syntax is a strict subset of Clojure syntax, so the Clojure mode works as is. However, edn is stricter than Clojure in what it allows, so I could easily imagine adding an edn mode option to the Clojure parser at some point in the future.
By the way, the motivation behind this change (which I neglected to mention originally, but should have) was getting edn code block highlighting working in Markdown mode since it relies on findModeByName.


add a dark theme

It would be awesome if we could have a dark theme. I would like you to implement this by usng a media query like so:
@media (prefers-color-scheme: light | dark)
Update:
I have created a fork to add this https://github.com/pages-themes/cayman/pull/135 to try it out vist https://godalming123.github.io/cayman/ the dark theme is based on device theme so swith it up and go dark!

I am confused as to what information you need? I have provided a description.

if you aren't willing to this code it I am I will fork repo and start devolopment

@parkr  can you assign me to this issue

The fork works now just merge it already!


Please provide powershell/cli instructions for deleting data

You provide the portal + powershell for vault deletion, but only portal for computer/data deletion which is a prerequisite.
Please provide powershell or other CLI means of oing the prerequisite steps for discovering & deleting the computers protected by a vault.

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

ID: 728cc3f4-d5da-a270-a3c0-53f179147cc0
Version Independent ID: 32d276c0-0980-ff36-933b-5012a39f75c5
Content: Delete a Recovery Services vault in Azure '
Content Source: articles/backup/backup-azure-delete-vault.md
Service: backup
GitHub Login: @markgalioto
Microsoft Alias: markgal

@martinffoster Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

It seems that suggestign the use of armclient that is downloaded via chocolatey is not really the way we'd like to see our toolset going. It feels as though there is a gap in the powershell here, there are no commands around removing backup items, which is obviously helpful, nor is there  a way to force the delete of a vault via powershell's remove-azurermrecvoeryservicesvault. Mike, perhaps you can provide the feedback to the powershell team for recovery services, to finish their code so that we can actually do the work we need to without having to write code to wrap around, armclient.

what's the ETA ? I can't delete multiple backup items via powershell and it's a very annoying repetitive task

@Tajjun @jeffpatton1971 The best option here is to make a product recommendation on the User Voice forum. There were multiple requests for PowerShell functionality. Please look through any of the completed requests to see if there is a solution there. If not, please make a new request or up vote and comment on an exisitng entry that has not been completed.

We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

Document metadata has been updated with latest content owner details. Updated this issue with latest doc details to reflect changes.


Retrieving the parameter values that led to a derived parameter

Hi amosborne
First of all thank you for sharing this tool. I believe it has an enormous potential.
I was wondering if there is a possibility to retrieve the bondaries on the parameters that led to your derived parameter.
In your examble would be the specific values of R1 to R5 and VOS that led to the WC value of the VOUT_1A upper and lower bounds.
I've been trying to retrieve the eval_init dictionary created in the call to the function " extreme_value" but I believe there have to be cleaner ways of doing it.
Help here, or adding this feature would be highly appreciated.
Regards

Hello, I appreciate the compliment. I think you're on the right track by using the 'eval_init' dictionary. Let me see what I can do.
I'm curious to know what you may be using this software for?

I've updated the code such that when a parameter is derived using the byev method, the resulting parameter has a field called derivation. This field has subfields nom, lb, and ub, which are dictionaries of the parameters used to make the derivation and the exact value used. Please let me know if this addresses your request.
I've included the example outputs in the example python notebook (see cells 6 and 13).

Hey, thanks for the quick implementation, that is actually exactly what I meant.
Regarding the usage to give to it. I am also an electronic engineer working in aerospace :). I was about gonna start writing my own WC "calculator", (a very reduced version of your tool, mostly just for corner cases by brute force ) when I came across your code, so started digging around. Got a bit lost with the usage of the networkx library and your data structure, but I find the code is written in a pretty smart style. Finally for the type of circuitry I'm dealing with I think maybe is an overkill (not much complex analog stages), but I'll keep it around to see how much of the WCA process I can  automatize with it. I'll keep you posted

Great! Nice to hear. Best of luck.


13 add acceptance criteria task to include database persistance of articles comments

Apologies again for inconvenience by raising another pull request to origin repository by mistake


Test Improvements

I added new feature to hopefully make development of server tests a little easier and quicker: run make test-w from the /server folder to run tests with a watcher that will re-fire if any changes are made to the test files.
The example test file now loads sails before executing the tests (and lowers after).  This will be necessary when tests are developed to do things like add users or verify ORM validations.
Initially I planned to have subfolders inside tests/unit for models, controllers, policies, etc.  After some thought, I think it makes more sense to apply a "pods" type philosophy to grouping the tests, meaning all the tests for users will go in tests/unit/users.Test.js.  I believe this follows BDD strategy a little more closely.
Lastly, I threw together a few ideas of additional tests to be created later (once I figure out how).  Trying to just brainstorm what kinds of tests might be useful at this point.

thanks, that all seems great, I'll merge and they play with everything

I'm not a fan of the Makefile.  I think npm test is even easier to type.

In package.json:
  "scripts": {
    "test": "mocha -R spec --ui bdd ./tests/unit/**/*.Test.js"
  },

to run:
$ npm test
$ # or to run with watch
$ npm test -- --watch

stylistically, I would keep all file and folder names all lower-dashed.  user.Test.js -> user-test.js.

houghts so far - seems like using async mocha in the afterAllTestsFinish and sails .lower is breaking, i removed the done's and it stopped failing
using sinon and chai together may be best using this https://github.com/domenic/sinon-chai

Great comments and suggestions, thanks.
@kriswill do we lose anything by not using the runner.js?  Doesn't seem like it.  I agree it would be nicer without the Makefile, just couldn't figure out how.  Thanks.
@mgenev I was having problems with async until I modified the runner to remove process.on('exit', function()  When I took that out it would exit successfully.  Wonder if this is an apple / linux thing.  Sinon-chai looks cool.  Seems to also work correctly with proposed change to use command line mocha in the npm script.

@kriswill The only reason I went with capitals was to stay consistent with SANE (https://github.com/artificialio/sane/blob/master/tests/runner.js) which it looks like I failed at, since there's no preceeding dot in those tests.  I'm not tied to any particular naming.  Can change to whatever everyone agrees is best.

Yeah @IanVS I actually prefer the - naming scheme. Just kinda started with camelCase, so either had to rename all of them (which I might do eventually :P) or carry on being consistent.


ModuleNotFoundError: No module named 'mmdet'

I have download the master branch of swa_object_detection. Meanwhile i have mmdetection on my pc.
I have try to train mask rcnn r50fpn with the normal mmdetection code. But this error comes always. Appreciate for the help!

i use the same env for swa_mmdet and mmdetection, will that be a problem?

pip install -v -e . if these problem raised just run this cmd.


RELATED: FET-1201 update pkg

JIRA: FET-1201

Build failed (check pipeline).

https://checklist.intgdc.com/job/client-libs/job/gooddata-create-gooddata-react-app-unit-tests-zuul-docker/10/ : SUCCESS in 28s
https://checklist.intgdc.com/job/compliance/job/sonarcloud-scan-PR-check/9/ : FAILURE in 18s
https://checklist.intgdc.com/job/compliance/job/gooddata-create-gooddata-react-app-oss-check/347/ : SUCCESS in 6s

Build failed (check pipeline).

https://checklist.intgdc.com/job/client-libs/job/gooddata-create-gooddata-react-app-unit-tests-zuul-docker/11/ : SUCCESS in 31s
https://checklist.intgdc.com/job/compliance/job/sonarcloud-scan-PR-check/10/ : FAILURE in 16s
https://checklist.intgdc.com/job/compliance/job/gooddata-create-gooddata-react-app-oss-check/348/ : SUCCESS in 5s

ok to test

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/client-libs/job/gooddata-create-gooddata-react-app-unit-tests-zuul-docker/12/ : SUCCESS in 29s
https://checklist.intgdc.com/job/compliance/job/gooddata-create-gooddata-react-app-oss-check/349/ : SUCCESS in 5s

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-create-gooddata-react-app-merge-compliance-check/182/ : SUCCESS in 30s
https://checklist.intgdc.com/job/client-libs/job/gooddata-create-gooddata-react-app-unit-tests-zuul-docker/13/ : SUCCESS in 26s
https://checklist.intgdc.com/job/compliance/job/gooddata-create-gooddata-react-app-fossa-scanning-zuul/6/ : FAILURE in 1m 14s (non-voting)


Security FAQ (signed in)

⚠ IMPORTANT: Before deploying, remember to re-apply the kubernetes templates so that the FIU_EMAIL secret (see PR) is set by running ./manage.py app apply {test,prod}
Ticket: https://dsdmoj.atlassian.net/browse/MTP-1836

Thanks for the review @ushkarev 🌟


Introduced Parameter ExecutionSchedule to make the schedule configurable

This PR adds ExecutionSchedule with a default of 1 hour.

Closed since #29 already addresses this.

Closed since #29 already addresses this.


Fix Python 3 support

Hi, great code and documentation to get started with RL.
When trying to execute your code on Python 3.6, I ran into a number of errors. So I ported the code to Python 3, using the 2to3 Tool by Python. I also fixed a minor bug and added a requirements.txt, which can help with the installation.

I'm closing the PR as the repo seems to be no longer maintained. Feel free to re-open


DeepChem

I've found an interesting project named DeepChem that also seems interested in retrosynthesis. I think that some sort of collaboration could potentially be mutually beneficial.

Chiming in on this thread from DeepChem! DeepChem tries to offer an integrated suite of machine learning tools for molecules/materials/other scientific systems (See our docs at https://deepchem.readthedocs.io/en/latest/). We'd love to be able to use aizynthfinder to provide a good retrosynthesis tool to our users. If this would be of interest to you folks, would be glad to say more what this could look like technically :)

Hello @0x2b3bfa0 and @rbharath
Very interesting idea! I have responded to the issue in the deepchem repository, as I believe it is best to continue the discussion there. Hence I will close this issue.

Excellent!


Make staging repo description configurable

The description can now be customized on the extension or individual
tasks and now defaults to the GAV of the root project.
In addition, the User-Agent (which is shown in Nexus UI) is now
customized to gradle-nexus-publish-plugin/<version>.
Resolves #31.

@marcphilipp You have some style violations.


Grid without vertical indents

Hi!
Is it possible to make grid without vertical indents?

Sorry, I found solution a bit later


jax.debug.breakpoint(num_frames=1) crashes in colab

Description
import jax

@jax.jit
def f():
    jax.debug.breakpoint(num_frames=1)

f()
# IndexError: list index out of range

This must be run in a colab.
Setting num_frames=2 seems to work instead.
What jax/jaxlib version are you using?
HEAD

Hi @patrick-kidger, The IndexError: list index out of range issue encountered while using jax.debug.breakpoint() in a @jax.jit function will be resolved by updating to the most recent JAX version. Would you please try running the code again with the latest JAX version, it seems to be working fine. I've included a gist for your reference.
Thank you.


[ENH] Add uint blockfile key/val

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1854  👈
#1853
#1847
#1846
#1825
#1823
#1822
#1821
#1820
#1819
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @HammadB and the rest of your teammates on  Graphite


CSM serialization

Changes
The asdf schema of the CSM now uses the DiGraph schema. This change is incompatible with older WelDX files.
Related Issues
Closes #354
Checks

[x] updated CHANGELOG.md
[x] updated tests
[x] updated doc/
[x] update example/tutorial notebooks

ToDo

[x] consider spatial data
[x] consider sub systems
[ ] add legacy tags

I am still thinking about the best way to support the old 0.4 weldx files
My best idea is to include the legacy code in separate files and add a new converter for the old tag that can read old files and create CSM instances
Since we only need to read old files using the legacy code we can omit the to_yaml_tree section of the old code

I am still thinking about the best way to support the old 0.4 weldx files
My best idea is to include the legacy code in separate files and add a new converter for the old tag that can read old files and create CSM instances
Since we only need to read old files using the legacy code we can omit the to_yaml_tree section of the old code

I have implemented this approach here https://github.com/vhirtham/weldx/pull/3 and it seems to work for the IIW example 🎉
you can load the old file and create a new version file upon save

I am still thinking about the best way to support the old 0.4 weldx files
My best idea is to include the legacy code in separate files and add a new converter for the old tag that can read old files and create CSM instances
Since we only need to read old files using the legacy code we can omit the to_yaml_tree section of the old code

I have implemented this approach here vhirtham#3 and it seems to work for the IIW example 🎉
you can load the old file and create a new version file upon save

If it works we can just write a small script that reads all WelDX files in a directory and stores the updated WelDX files in a new one. We should then convert all important files and get rid of the legacy code ASAP.

I am still thinking about the best way to support the old 0.4 weldx files
My best idea is to include the legacy code in separate files and add a new converter for the old tag that can read old files and create CSM instances
Since we only need to read old files using the legacy code we can omit the to_yaml_tree section of the old code

I have implemented this approach here vhirtham#3 and it seems to work for the IIW example 🎉
you can load the old file and create a new version file upon save

If it works we can just write a small script that reads all WelDX files in a directory and stores the updated WelDX files in a new one. We should then convert all important files and get rid of the legacy code ASAP.

My idea would be to keep full legacy support for the 0.5 release and drop the legacy file/tag release in 0.6
This way we can still read files with the old tags and provide 'proper' backwards compatibility with the new API from 0.6 on

My idea would be to keep full legacy support for the 0.5 release and drop the legacy file/tag support in 0.6
This way we can still read (and convert) files with the old tags and provide 'proper' backwards compatibility with the new API from 0.6 on

Seems plausible. So just merge your updates into this branch. Are we good to go then (apart from this weird new k3d error?) or is there something missing?

Hello @vhirtham! Thanks for updating this PR.

In the file weldx/tags/core/transformations/_legacy/coordinate_system_hierarchy.py:

Line 67:89: E501 line too long (97 > 88 characters)
Line 373:26: E231 missing whitespace after ':'
Line 373:26: E999 SyntaxError: invalid syntax
Line 373:28: E251 unexpected spaces around keyword / parameter equals

In the file weldx/tags/core/transformations/coordinate_system_hierarchy.py:

Line 9:89: E501 line too long (95 > 88 characters)

Seems plausible. So just merge your updates into this branch. Are we good to go then (apart from this weird new k3d error?) or is there something missing?

I think everything should be ready
we should also prepare a PR on the IIW AA example repo that works with the current version imo (and update the example file to the new graph schema)


Master -> Live

Docs Build status updates of commit 0827b86:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.DS_Store
:white_check_mark:Succeeded

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-03.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-04.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-05.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-06.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-07.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-08.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/unreal-development-overview.md
:white_check_mark:Succeeded
View

mixed-reality-docs/unreal-winRT.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

.DS_Store
:white_check_mark:Succeeded

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-03.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-04.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-05.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-06.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-07.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/unreal-winrt-img-08.png
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/unreal-development-overview.md
:white_check_mark:Succeeded
View

mixed-reality-docs/unreal-winRT.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Refactor modalities - split names from rendering.

fixes: https://github.com/PolymerLabs/arcs/issues/2393

@lindner - thanks for the review, and sorry for making merge hard for you once again :)


New Exception Message

Addresses some concerns with ICR pull request.

To clarify, the concerns is just the clean up of the unused variable and adding of the adhoc exception message to SQLServerResource


Pretrained weights

Hi,
Thank you for sharing the code. Can you please share the pretrained weights for the models as well for direct inference? I have an old gpu and cannot train due to VRAM limitations.

Hi Shantanu,
I am deeply sorry for this. I haven't maintaining this project for almost 1 year and half.
The trained weight is missing somehow.
I suggest you may rent an online GPU service for training this model?

Hi @tomguluson92 ,
Thank you for your reply. I understand and I'll look into possible options for training it myself. I request you to not close this issue now, since I would like to share the training and test logs along with the pretrained weights here for others to use. Hope that is ok.


java 1.8 with ANT build error

I was facing class not found: javac1.8'. After a few googling I found the suggestion to force using -Dbuild.compiler=javac1.7' .I was able to run one of the clousure project using the following command:
cd /src/Defects4J_Experiment/Defects4J_projects_faysal/Closure_73 && ant -f /sbfl/defects4j/framework/projects/defects4j.build.xml -Dd4j.home=/sbfl/defects4j -Dd4j.dir.projects=/sbfl/defects4j/framework/projects -Dbuild.compiler=javac1.7 -Dbasedir=/src/Defects4J_Experiment/Defects4J_projects_faysal/Closure_73  compile 2>&1
But how to incorporate such force action into default defect4j? For example if I run `defect4j compile' how to add that force build command automatically?

I solved this problem by adding the force command (-Dbuild.compiler=javac1.7) to the ant file located in defects4j/major/bin


Sentiment analysis

How do I configure sentiment analysis for LUIS from settings in Composer?
I have enabled sentiment analysis when publishing from LUIS and I can see sentiment being returned when testing from the emulator. When I publish and use webchat there is no sentiment returned from LUIS. Both published bot and emulator should be using the same prediction endpoint.

I'm looking into if and how this can be done. I will post an update as soon as I know more.

Can you tell me, when you created your publishing profile in Composer, did you select "Create new Azure resources" or "Import existing Azure resources"? I suspect you selected the first option. If so, then I believe the issue is tied to the published LUIS service. Prior to publishing, you needed to supply your LUIS authoring key in order for you to be able to test your bot in Composer. However, during the publishing process, new LUIS authoring and endpoint keys are generated for use, exclusively, by the bot. The authoring key you supplied in Composer is discarded and replaced.
I'm guessing that, like you, I went to the LUIS.ai site and found the LUIS app that was created when testing. I made changes there and ran into the same issue you did. Once I noticed the new LUIS service(s) in the bot's resource group, I returned to LUIS.ai, clicked on my profile in the top right, and clicked the "Change authoring resource" link. The drop down revealed the new service. Changing to the new service displayed the correct LUIS app actually being used. I re-published the app selecting to use sentiment analysis and when I did, in Emulator for the published bot, I saw the below.

Did this help?

I suspect you are correct. I changed the "composer" LUIS app to use sentiment analysis, but I did not change the "publish" LUIS app. I was heading down this path of investigation but have been stymied because I can no longer published at all. Once I get that resolved I'll return to this issue and confirm. Thanks.

Hi @JohnRobertGreen : Curious if you have any updates here?  Thanks!

Hi @JohnRobertGreen : Closing due to inactivity, please reactivate if necessary..

@stevkan  - we are facing this issue, any suggestion?
we are using existing LUIS resource and using the preview composer pipelines to deploy. we are not getting the sentiment score even after changing the settings in luis portal.


using ui-grid with bower and angular 1.3.9

Hello,
I'm using AngularJS 1.3.9 and ui-grid as well, and using bower to install my project dependencies.
However, the ui-grid bower package is using angular ~1.2.16 which gives me hell lot of problems with the project deployment.
Is there a way to use latest ui-grid bower package with angular >=1.3.9?
Thanks,
Eyal.

In you're bower.json, add a resolutions section:
    "dependencies": {
        "angular": "~1.3.9",
        "angular-ui-grid": "~3.0.0-rc.16"
    },
    "resolutions": {
        "angular": "~1.3.9"
    },

https://github.com/bower/bower.json-spec#resolutions

Thanks. I have this in my bower.json and it doesn't work so good (actually, sometime it does and sometime it doesn't). from some reason, when I run "bower install angular", bower doesn't use the resolution and keep asking me about the angular version to use.
"dependencies": {
"angular": ">=1.3.9",
"angular-ui-grid": "3.0.0-RC.18"
},
"resolutions": {
"angular-ui-grid": "3.0.0-RC.18",
"angular": ">=1.3.9"
}
Isn't RC-18 better version to use? I encountered some issues with RC-16?

The resolutions is for when you call bower install (with no package specified).  When you have angular listed in your bower's dependencies section, there is no need to call bower install angular as that will try and re-download a particular version, prompting you for which version.
RC.18 is the latest, so sure that should be fine.

You may also want to be careful with capitalisation, refer #2324

@c0bra: is there something we need to change here to indicate that we're now compatible with 1.3?

Yea, we need to update bower.json here: https://github.com/angular-ui/bower-ui-grid/blob/master/bower.json
I think angular: 1.2.16 - 1.3.x should do it?

This should take effect with the next RC.

It appears this 1.3 compatibility fix got reverted in angular-ui/bower-ui-grid@4615685f3f7a4a4a15b1a4ee80b82da31d41d5ee
Same conflict issue here:-
% cat bower.json
{
  "name": "idap",
  "dependencies": {
    "angular": "~1.3.15"
  }
}

% bower install angular-ui-grid --save
bower angular-ui-grid#*         cached https://github.com/angular-ui/bower-ui-grid.git#3.0.0-rc.21
bower angular-ui-grid#*       validate 3.0.0-rc.21 against https://github.com/angular-ui/bower-ui-grid.git#*
bower angular#~1.2.16           cached https://github.com/angular/bower-angular.git#1.2.28
bower angular#~1.2.16         validate 1.2.28 against https://github.com/angular/bower-angular.git#~1.2.16
bower angular#1.3.15            cached https://github.com/angular/bower-angular.git#1.3.15
bower angular#1.3.15          validate 1.3.15 against https://github.com/angular/bower-angular.git#1.3.15
bower angular#>= 1.0.8          cached https://github.com/angular/bower-angular.git#1.3.15
bower angular#>= 1.0.8        validate 1.3.15 against https://github.com/angular/bower-angular.git#>= 1.0.8
bower angular#^1.2.9            cached https://github.com/angular/bower-angular.git#1.3.15
bower angular#^1.2.9          validate 1.3.15 against https://github.com/angular/bower-angular.git#^1.2.9
bower angular#>=1.0.8           cached https://github.com/angular/bower-angular.git#1.3.15
bower angular#>=1.0.8         validate 1.3.15 against https://github.com/angular/bower-angular.git#>=1.0.8
bower angular#>=1.3.0           cached https://github.com/angular/bower-angular.git#1.3.15
bower angular#>=1.3.0         validate 1.3.15 against https://github.com/angular/bower-angular.git#>=1.3.0
bower angular#*                 cached https://github.com/angular/bower-angular.git#1.3.15
bower angular#*               validate 1.3.15 against https://github.com/angular/bower-angular.git#*
bcower                        ECONFLICT Unable to find suitable version for angular

Any breakage reasons? Having issues with the resolutions block too.

Since it's closed and the problem is still present, here's the link to the "reopened" issue #3925


Regression: Not possible to import/export artifacts using different build architecture.

See original issue on GitLab
In GitLab by [Gitlab user @jjardon] on Feb 18, 2018, 13:56
Used to be possible to build something on arch (a), and then arch(b) could import that same thing
Now, because arch(a) and arch(b) differ, arch(b) cannot consume an artifact produced by arch(a).

In GitLab by [Gitlab user @jjardon] on Feb 18, 2018, 13:57
changed title from Not possible to import/export artifacts using different build architecture. to {+Regression: +}Not possible to import/export artifacts using different build architecture.

In GitLab by [Gitlab user @tristanvb] on Feb 19, 2018, 08:47

Used to be possible to build something on arch (a), and then arch(b) could import that same thing

It is quite accidental that this ever worked - and I find the expectation of this working to be unreasonable.
The remote artifact cache interactions is a productivity enhancing feature; not a requirement. This is to say it should always be possible to launch a BuildStream session and build a target, regardless of whether a remote artifact cache has been wiped clean or not; remote caches can disappear.
Doing this procedure without doing any export of the cross built artifacts produced on ${host} and another import of the same when later building on ${target} defeats reproducibility; because the build on ${target} then becomes reliant on some transient state to succeed (i.e. an artifact in a remote cache which is not guaranteed to exist).
We do intend to support cross-arch building in BuildStream proper by way of distributing the build processes to remote workers or virtual machines which provide the required build architecture and OS - but this is much further in our timeline and is a lot of work.
At this time, it looks like some external process has been designed around invalid assumptions; which means we need to do some damage control here and examine what avenue is least costly in the short term.
Export / Import
Readjusting the processes developed around this assumption to use a reliable export and then import is one way forward.
Preliminary bits of real support for cross building
Alternatively, it may be possible to implement the correct assertions and API layers of cross build support in advance of actually implementing cross capable sandboxes.
This would require:

A way for elements to dictate which architecture they expect to build on
A way for BuildStream to refuse to build if a sandbox cannot be provided for the required build arch

Until a complete implementation occurs, this would always abort if the requested arch is not the host arch

BuildStream to calculate cache keys based on the explicitly required build arch instead of the implied host arch

Probably there are a lot of details to analyze here to get the API right, but it's conceivable that if we went ahead with this path we could continue to "incidentally work", and in the case of a foreign arch build which expects a cross built base runtime artifact to exist; we would also gain the appropriate error instead of blindly attempting to run a build on an x86_64 runtime but aarch64 build host.

In GitLab by [Gitlab user @samthursfield] on Feb 19, 2018, 11:56
Note that for Baserock cross-bootstrap we solved this by pushing the results of the bootstrap to a separate OSTree repo (not a BuildStream artifact cache), then importing it with an 'import' element.
The process is documented here: https://gitlab.com/baserock/definitions/#bootstrap-sysroots

In GitLab by [Gitlab user @tristanvb] on Feb 19, 2018, 18:29
So in the above, I mentioned "Preliminary bits of real support for cross building" as a possible way forward, but I should note that even if we were to do that analysis now; I would still recommend that you follow [Gitlab user @samthursfield]'s better example of how to do it in Baserock. I.e. if we did iron out the preliminary bits of real support, using it in this way would still be creating a strangely non-reproducible project, or rather, a project that cannot be built without external artifact cache connectivity.
Also, I should note that while this needs to be fixed damn quickly on the freedesktop-sdk side, any premature commitments to API surrounding cross building would be severely dangerous to the project, that should really be ironed out whilst experimenting with implementations.
It is unfortunate that you hit this, and I'm still baffled that it ever worked at all.

In GitLab by [Gitlab user @tristanvb] on Mar 8, 2018, 11:40
This has been fixed by now in the downstream project, closing this as wontfix for reasons explained in comments above.

In GitLab by [Gitlab user @tristanvb] on Mar 8, 2018, 11:40
closed


module.eks.local_file.kubeconfig[0] will be created

I have issues
I'm submitting a...

[x] bug report
[ ] feature request
[x] support request - read the FAQ first!
[x] kudos, thank you, warm fuzzy

What is the current behavior?
It appears this always wants to be created. I'm not sure it's possible, but I'd like see no changes when nothing needs updating.
  # module.eks.local_file.kubeconfig[0] will be created
+ resource "local_file" "kubeconfig" {

If this is a bug, how to reproduce? Please include a code sample if relevant.
What's the expected behavior?
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details

Affected module version: v12.2.0
OS: ubuntu
Terraform version: 0.13.2

Any other relevant info

does you are running this in some CI process where this file is removed after job run?
Usually this happens on some CI runs where checkout from git is done and file is not existing, then usually is worth to disable it via variable: write_kubeconfig=false if it is not required.

ya, it's an ephemeral job, so git clone is literally done every time, and there's no state between runs. The kubeconfig file though is required if manage_aws_auth=true ?

nope, you can use following definition which is working on my code (omitted some code for clarity):
module eks_cluster {
  create_eks = var.eks_create
  # https://registry.terraform.io/modules/terraform-aws-modules/eks/aws/12.2.0
  source          = "terraform-aws-modules/eks/aws"
  version         = "12.2.0"
  cluster_name    = "eks-${var.environment}"
................
  vpc_id          = module.vpc.vpc_id
  manage_aws_auth = true
  enable_irsa                          = true
  write_kubeconfig                     = false
...............
}

data aws_eks_cluster cluster {
  count = var.eks_create ? 1 : 0
  name  = module.eks_cluster.cluster_id
}

data aws_eks_cluster_auth cluster {
  count = var.eks_create ? 1 : 0
  name  = module.eks_cluster.cluster_id
}

provider kubernetes {
  host                   = element(concat(data.aws_eks_cluster.cluster[*].endpoint, list("")), 0)
  cluster_ca_certificate = base64decode(element(concat(data.aws_eks_cluster.cluster[*].certificate_authority.0.data, list("")), 0))
  token                  = element(concat(data.aws_eks_cluster_auth.cluster[*].token, list("")), 0)
  load_config_file       = false
  version                = "1.13.1"
}

Score thanks!!

closing this, since it's the correct behavior. Please set write_kubeconfig=false if you don't need kubeconfig to be generated on your local disk.


Fixes to Transport

@krisread damn it you're right. You explained this earlier :man_facepalming:

Yeah I thought of using "pin" as well to make it more consistent but... seems like seneca is to blame in sabotaging this plan.
It might be possible to totally rewrite the transport somehow to not use tu.make_client at ALL and build the client custom in the transport layer.  I think that would be possible but more work!   In theory you can push a lot of logic into the transport if you try.


[shaderc port] automatically adds 'SPIRV-Tools.lib' but it has wrong path at all

Hello!
So for reducing reading time. (IDK, if it is a duplicate and known issue you can close it)
Two projects, A is exe and B is static library that uses shaderc and linking to A project.
(EXE) A <- B
(STATIC LIB) B <- shaderc
I just installed shaderc through vcpkg and followed to heuristic generated commands for cmake.
BUT adding
target_link_libraries(${PROJECT_NAME} PUBLIC unofficial::shaderc::shaderc) automatically adds 'SPIRV-Tools.lib' (yeah, it is only the name 'SPIRV-Tools.lib' without any path to it) in input section of linking and it is not correct, the solution can't be built because it wants to find the 'SPIRV-Tools.lib' but the location is unknown.
Okay, I tried to search SPIRV-Tools like a separated package through find_package (because when you install shaderc it also installs SPIRV-Tools too, it is right) and it doesn't remove SPIRV-Tools.lib it adds a 'new' path to lib's pathes for linking and I don't know how to fix, I tried many variants but it is some kind of a real bug for me.
For example, I added find_package(SPIRV-Tools-opt CONFIG REQUIRED) with target_link_libraries(${PROJECT_NAME} PUBLIC SPIRV-Tools-opt) and it replaced 'SPIRV-Tools-opt.lib' to right path. (yeah, shaderc::shaderc (or maybe it is not shaderc, IDK, but I explain things what I got) adds 'SPIRV-Tools.lib' and 'SPIRV-Tools-opt.lib')
As a proof I just put this screenshot of generated project's settings.

So the commands of target_link_libraries in cmake project are:
   ...
    find_package(glslang CONFIG REQUIRED)
    find_package(unofficial-shaderc_util CONFIG REQUIRED)
    find_package(SPIRV-Tools-opt CONFIG REQUIRED)
    find_package(SPIRV-Tools CONFIG REQUIRED)
    find_package(unofficial-shaderc CONFIG REQUIRED)
    find_package(unofficial-spirv-reflect CONFIG REQUIRED)
    ...

    target_link_libraries(${PROJECT_NAME} PUBLIC glslang::glslang)
    target_link_libraries(${PROJECT_NAME} PUBLIC SPIRV-Tools)
    target_link_libraries(${PROJECT_NAME} PUBLIC unofficial::shaderc::shaderc)
    target_link_libraries(${PROJECT_NAME} PUBLIC unofficial::shaderc_util::shaderc_util)
    target_link_libraries(${PROJECT_NAME} PUBLIC unofficial::spirv-reflect::spirv-reflect)
    target_link_libraries(${PROJECT_NAME} PUBLIC SPIRV-Tools-opt)

Hope you can repeat the steps and get the same situation what I reached, but it is really strange and I don't understand how it works. I investigated shaderc's project in vcpkg and got this interesting line in vcpkg/packages/shaderc_x64-windows/share/unofficial-shadercTargets.cmake
set_target_properties(unofficial::shaderc::shaderc PROPERTIES
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include/"
  INTERFACE_LINK_LIBRARIES "\$<LINK_ONLY:glslang::glslang>;\$<LINK_ONLY:glslang::OSDependent>;\$<LINK_ONLY:glslang::OGLCompiler>;\$<LINK_ONLY:glslang::glslang>;\$<LINK_ONLY:unofficial::shaderc_util::shaderc_util>;\$<LINK_ONLY:glslang::SPIRV>;\$<LINK_ONLY:SPIRV-Tools>"
)

Especially, I don't understand why adding SPIRV-Tools-opt as a additional package removes the invalid 'SPIRV-Tools-opt.lib' but doing the same for 'SPIRV-Tools' it doesn't affect at all.
Wasted some hours for fixing it and no results.
P.S. Platform is Windows 11 and it was generated for VS 2022, cmake is 3.25.0.
P.S.S. About SPIRV-Tools, heuristic suggests a wrong thing at all, you can't use -shared and -static at once.
See this pic:

P.S.S.S. Writing target_link_libraries(${PROJECT_NAME} PUBLIC SPIRV-Tools) instead of 'suggested' target_link_libraries(${PROJECT_NAME} PUBLIC SPIRV-Tools-static) still adds corrected path to SPIRV-Tools.lib (static version). It is not an error or something, just an observation.

P.S.S. About SPIRV-Tools, heuristic suggests a wrong thing at all, you can't use -shared and -static at once.

Welcome to #20190.

Fixed by https://github.com/microsoft/vcpkg-tool/pull/849.

I ended up doing this workaround, which solved my troubles:
find_package(SPIRV-Tools-opt CONFIG REQUIRED) find_package(SPIRV-Tools CONFIG REQUIRED) add_library(SPIRV-Tools ALIAS SPIRV-Tools-static) find_package(unofficial-shaderc_util CONFIG REQUIRED) find_package(unofficial-shaderc CONFIG REQUIRED)
The alias allows SPIRV-Tools-static to satisfy SPIRV-Tools' requirement in unofficial-shaderc .
I do not think this issue has been resolved. I understand the heuristic-based instructions have been modified, but they're still not helpful for this library in particular. Is there any reason not to remove SPIRV-Tools' inclusion?

Especially, I don't understand why adding SPIRV-Tools-opt as a additional package removes the invalid 'SPIRV-Tools-opt.lib' but doing the same for 'SPIRV-Tools' it doesn't affect at all.

In CMake link libraries specifications, SPIRV-Tools or SPIRV-Tools-opt initially don't have a special meaning, so they is passed as unqualifed lib name to the linker. This changes when CMake has a target with that name: Linking details are taken from target properties, including the actual location of the link library. And a call to find_package is a way to created "imported targets" for external packages.
Best practice is to never export targets (or created imported targets) without namespace: A prefix with the :: separator signals to CMake at configuration time that a name is a referring to a target. It will report early that probably a find_package call or alias is missing in the project. The linker cannot accidentally pick a release lib when a debug lib was meant.
Here, the names are defined upstream (in the SPIRV-Tools project), so we must use them.
But the problem was that the vcpkg port didn't properly care about setting up link libraries and doing in find_package in the exported CMake config packages.


eCarePlanner 3.2.0 - seems like it's not pulling very much from the SDS, many resources missing

Testing eCarePlanner functionality with Michelle, it appears that many resources in the SDS aren't being pulled into eCarePlanner.
Is this intentional?  We're missing MedicationResources, vitals, labs, care team - none seem to be getting queried for by eCarePlanner.
Here's the sum of queries being executed by eCarePlanner against the SDS:

It's only pulling:

QuestionnaireResponse
Goal
Condition

... that's it.
Shouldn't it be sharing a lot more?
Here's what we have in the SDS for this patient:

@mattStorer This is intentional. We started with Goal, Health Concerns, and QuestionnaireResponse for the first iteration. If the others are desired as a high priority, they will need to be addressed by Sean in his supporting contract after Oct 1, 2024.


[NFC] .github: Link out to Swift.org for release branch PR form

Summary
In an effort to centralize the release branch PR form and release process info in general, remove any instances of such content and link out to the dedicated section on Swift.org instead.
This move was agreed upon by the Contributor Experience Workgroup.
Concurrent PRs:

https://github.com/apple/sourcekit-lsp/pull/1433
https://github.com/apple/swift-org-website/pull/688
https://github.com/apple/swift-syntax/pull/2669
https://github.com/apple/swift/pull/74117

Checklist
This change is NFC.

I'd like to suggest we add a new .github repo on swiftlang and add PULL_REQUEST_TEMPLATE/CHERRY_PICK.md file on this repo.

Yep, that was the original idea — suboptimal for apple, but much better for swiftlang. We’re going to discuss this next meeting (I was the one to originally bring up this topic and nobody seemed to be anticipating swiftlang at the time).
@parispittman Do we have a rough estimate on the time frame of repository transfers to swiftlang?

I'd like to suggest we add a new .github repo on swiftlang and add PULL_REQUEST_TEMPLATE/CHERRY_PICK.md file on this repo.

Yep, that was the original idea — suboptimal for apple, but much better for swiftlang. We’re going to discuss this next meeting (I was the one to originally bring up this topic and nobody seemed to be anticipating swiftlang at the time).
@parispittman Do we have a rough estimate on the time frame of repository transfers to swiftlang?

I saw the transition has already began.
I suggest we just use "the original idea".
For those repo still hosted on apple currently (eg. swift-docc), we can continue use the old pattern.
When the migration is done for them, we can then just safely delete the duplicated .github/PULL_REQUEST_TEMPLATE/CHERRY_PICK.md file on those repo.

Turns out, folks have already added a .github repository to swiftlang, so I went ahead and added the org-wide pull request template. It works as a query parameter just fine. The template is called release.md — I think this neutral and simple if straightforward name will be easiest for us all to remember and type.  I will update this pull request accordingly as soon as the repo moves to swiftlang.
Thanks for weighing in!

Confirmed using my swift fork:

But it seems we will lose the template discovery after your PR.

Because this repository will no longer have its own template, you mean? I believe that is fine:

We still have a leading comment in the default template.
Folks that submit changes to release branches on a regular basis have the experience to catch on.
First-timers are in the majority of cases asked by code owners to cherry-pick something and receive appropriate guidance. One can also learn about the template and how to tap into it from the website: https://www.swift.org/contributing/#release-branch-pull-requests.

Confirmed with the swift repository, which no longer has a release template.

It seems I was wrong. I tried again with the Apple main branch vs. my fork as the base and now it only shows the default template. release.md is only shown when the repository has no PR templates at all, like swift-syntax. 😕