Add/remove hunks and lines in "diff all files" view

Currently, this can only be done in the "diff file inline" view.

Hi @jipumarino - if you run git: diff, you are able to stage individual hunks from the resulting view (see here).  You can also remove hunks from the index using git: diff (cached).
I don't have plans to support staging individual lines from this view, mostly because of the complexity involved that was already solved with the inline-diff view.  However, if you're looking for more exact control over what is staged, I may add functionality to edit the diff before it is applied to the index (see #42).

Oh, sorry. I tried using the same shortcuts as in the file diff. Thanks!

No worries!


Make cards more responsive

Fixes: suggestions in #946
Make all cards more responsive to different screen sizes. Based on #1028
Before:
1. Snapshot detail

2. Disk edit

After:
1. Snapshot detail

2. Disk edit

@bond95 added my changes. Feel free to give any further feedback. Current view as approved by @lwrigh

@bond95 added my changes. Feel free to give any further feedback. Current view as approved by @lwrigh

Can you add a little more padding around the restore snapshot button? It seems a little too close to the rest of the snapshot info.

@bond95 added my changes. Feel free to give any further feedback. Current view as approved by @lwrigh

Can you add a little more padding around the restore snapshot button? It seems a little too close to the rest of the snapshot info.

Agree, I cannot see left border of popover.

@bond95 Does this look better?

@bond95 Does this look better?

Yes, thank you.

@thaorell - This PR addresses the popup dialogs for Snapshot details, Nic edit/create and Disk edit/create correct?  Please update the PR title/initial description to reflect what exactly the PR is targeting.

ci build please

Snapshot detail is showing to the left of the info icon instead of above it.

firefox-68.0-4.fc30.x86_64

@isaranova it will only popover for smaller screen size (<600px)

ci build please

@thaorell Sorry, you are right!
LGTM

@thaorell please, rebase

ci build please

LGTM


Move db.sql to another location

Currently, the db.sql file is placed in var/cache directory which makes clearing the cache tricky. Moving it to var/db location should fix this issue.

Related to #12.


Can't use multi-gpu (Colab example)

Hi, Thanks for your great work.
I just tried to run through provided Colab example using multi-gpu (0,1,2,3).
By changing use_multi_gpu from False to True, I got AssertionError: Invalid device id.
Does that mean Colab refuses to offer 4 GPUs or there are just some bugs?
By the way, I want to make sure whether my problem can be solved by the Informer model.
Let's say my custom dataset has 1 column of date and N columns of features and 1 target column that is numerical, and the goal is to predict the value of the target column using other columns in the same row.
Does this kind of problem called ''Multivariate predict Univariate'' so I choose 'MS' in args.features?
Thanks again.

Hi,

You need to check if the colab provide enough gpus and you can modify args.divices according to the devices you have. We have test multi-gpu running in our cluster and it works well.
Yes, you can use 'MS' to solve your problem, or use 'M' and select the last column of the result as your prediction.

Thanks for the quick response.
Does that mean the number of GPUs in the Colab would differ for different users even when they run the same provided Colab example for the first time?
Actually, I wonder how can I "check" how many GPUs can I use in Colab, and if it says that I can only use 2, how can I do to increase that number.
I had successfully used four GPUs once a time, the training process was very fast. However, whenever I trained afterward, I could use only two or even receive an error like "Invalid device id".

It seems that you can only use one GPU on google colab and that is the limit from Google.
The device id is related to the devices you can see and you need to set --devices as the ids of GPU you can use. For example, if you have 3 GPU, the device ids of them will be 0,1,2. And if the GPU 0 is used by other program, you can set --devices '1,2' to use GPU 1 and 2.
If you still recieve an error, you can provide us with the specific usage of the GPUs and more detailed error information.

Suppose there is no more discussion. I will close this issue now.


Removes forward slashes (/) from user agent in Peers tab UI.

user agent is prefixed and suffixed with forward slashes occupying two spaces and seem unnecessary for the Qt wallet UI. Example: /Dash Core:<IP_ADDRESS>/ --> Dash Core:<IP_ADDRESS>
Before:

After:

One good side effect the ellipsis is removed using the default window size.
This code is forked from my original pull for Dark Silk:  https://github.com/SCDeveloper/DarkSilk-Release-Candidate/pull/138

I do not agree. The user agent string IS "/Dash Core:<IP_ADDRESS>/" - removing the slashes from QT UI would falsify this fact for the sake of display convenience.

@crowning- any way to increase the default width of the User Agent row?

Is there a situation when the user agent prefix or suffix varies?  If not, I don't think it is useful to show in the UI.
Lets see if Bitcoin agrees.  I submitted a pull to them before Dash:  https://github.com/bitcoin/bitcoin/pull/7640

I agree with @schinzelh
More this issue is already fixed in 12.1 https://github.com/UdjinM6/dash/commit/fcad1c26ec704b7456dacc9c2ef1fcf4cd8ec57d

I'll close this for now.
Thanks for submitting it anyway, but "User Agent" column should display exactly that. I expect Bitcoin to share my view.

Okay.
According to BIP-0014, the prefix and suffix forward slashes are separators (a delimiter).
https://github.com/bitcoin/bips/blob/master/bip-0014.mediawiki#proposal

/ separates the code-stack

Displaying a separator or delimiter in the UI is unnecessary and goes against Jakob Nielsen heuristics: https://www.nngroup.com/articles/ten-usability-heuristics/:

Aesthetic and minimalist design Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

Remove it, simple. Stop arguing over something so trival and not only that.....CryptoDJ is correct.

@SCDeveloper It's not a matter if the change is trivial or not - it's simply not correct.
The User Agent string contains by specification (BIP-014) two slashes as delimiters. Therefore this column in the debug window works exactly as designed. Same applies to the CLI

I understand that you feel that it goes against good UI design practices, but the use case for the debug window is to display the information AS IS - not in a skewed way.
I see you have merged the changes into your code base, so no need to keep on pushing here.

I am sure the proposal is for the Qt UI only......


chips_input does not get focus when number of chips reaches maxChips

If I have maxChips=1 and I already selected a chip then the textController does not put the cursor even when we touch an empty space in the widget.
I understand that when number of chips is equal to maxChips, we can not add another chip. But still this does not mean we shouldn't be able to interact with the textController. Maybe the user wants to backspace an already selected chip instead of pressing X on the chip.

I would love that when maxChips number is reached, instead of preventing any input, user can still add a new chip, but is will then replace the last added chip.
So for instance with maxChips = 1 and one selected chip, you can still input and add a new one, but it wil delete the previous selected chip.


fix(log error): handle undefined target when websocket errors

Coverage remained the same at 86.704% when pulling a686b780f260cdbb489e4bd7eaf35fdca4071a41 on fix-websocket-log-error into 455ba4735bb526813c007591c569f153da5a95a3 on master.


How to specify custom residues to train Casanovo from scratch?

Since release of version 3.5.0,  "Specifying custom residues to retrain Casanovo is now possible."

I assume retrain means train Casanovo from scratch, it is still not possible to add extra residues to train Casanovo from a pretrained weights, am I right?
Are there any other actions I shall do apart from modifying the residues part in config.yaml? e.g., other than the residues specified in original config.yaml, I added "K+42.022":<PHONE_NUMBER>5  #Lysine Guandination<PHONE_NUMBER>50 + 42.02180. Is it all I need to do to specify custom residues?
Actually, I have been adding/removing residues to train Casanovo from scratch since version 3.1.0, it seems to work well. So, what has been changed between v3.5.0 and previous v3.x.0 regarding specifying custom residues?

Thanks!

Correct, when you change the residue alphabet, training from scratch is necessary.
No. (Besides having spectra for peptides with those modifications in your training data of course.)
Before version 3.5.0 modifications specified in the config would be ignored. This was fixed in version 3.5.0. For more details, see #229.


Freeze on start

On the latest version of canary, this plugin causes powercord to freeze on start. Doesn't cause a bootloop, but it does mean it freezes during the fade in so you can't use the app.
Info:
Canary 85548 (c81e78c)
Host 0.0.121
Linux 64-Bit (5.4.0-73-Generic)
Powercord v2 (111398d)

On the latest version of canary, this plugin causes powercord to freeze on start. Doesn't cause a bootloop, but it does mean it freezes during the fade in so you can't use the app.
Info:
Canary 85548 (c81e78c)
Host 0.0.121
Linux 64-Bit (5.4.0-73-Generic)
Powercord v2 (111398d)

Apologies for the late reply, but with the PR #6 it should help with performance issues if they're still present.


E185: Cannot find color scheme 'wal'

I get this error when opening vim documets:
E185: Cannot find color scheme 'wal'
and the color scheme doesn't change. Is there a way to set "wal" manually?

Did you follow the instructions from Plug?

here is my ~/.vimrc:
vimrc.txt
If I have understood the instruction correctly, so after putting the lines:
Plug 'dylanaraps/wal'
colorscheme wal
set background=dark

and run :PlugInstall, it should work at the next opening of vim.
but instead, I got the following:
➜  probability vi
Error detected while processing /Users/user/.vimrc:
line   25:
E185: Cannot find color scheme 'wal'
Press ENTER or type command to continue

@ducks4rule @nilnil47 @vikomen
What worked for me was the following procedure.
Insert Plug 'dylanaraps/wal.vim' into the list of plugins, then add colorscheme wal  after call plug#end().
Run :PlugInstall in vim.
Install pywall instead of wall using the procedure described in their installation and setup guide. Be sure to follow their guide to ensure persistence across terminals/reboots.
Run wal --theme base16-nord in terminal.
Run :PlugUpdate in vim.  After running this, you should have your theme working and lose the Cannot find color scheme 'wal' error message.
Finally, I would like to express my deep sadness upon finding out that Gilles passed away last year. I've emailed him in 2020 to thank him for his guide, and he took his time to thank me for making his day brighter.
I only wish that brightness could have lasted forever.

Check this out: https://stackoverflow.com/a/64178519/14176726


added twitter, facebook & linked-in to the menu

Uses https://github.com/plyfe/ember-social
Closes feedbackfruits/bepstore-ui#46, feedbackfruits/bepstore-ui#40 & feedbackfruits/bepstore-ui#54

@steffansluis @WouterKvG please review & hype!

[Current coverage][cc-pull] is 25.58%

Merging [#23][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #23   diff @@
==========================================
  Files             2          2
  Lines            43         43
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits             11         11
  Misses           32         32
  Partials          0          0

Powered by Codecov. Last updated by [cb0409d...dff07ff][cc-compare]
[cc-base-branch]: https://codecov.io/gh/feedbackfruits/bepstore-ui-goals/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/feedbackfruits/bepstore-ui-goals/compare/cb0409df3d02a6afdf2b8d29a7d71b190ac2c888...dff07ff5f2253586603612d808d432d8cdfe45c3
[cc-pull]: https://codecov.io/gh/feedbackfruits/bepstore-ui-goals/pull/23?src=pr


Fixing new pylint messages for actions

No review

Codecov Report

Merging #17 (0cf4be5) into main (c4b0da1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #17   +/-   ##
=======================================
  Coverage   80.51%   80.51%
=======================================
  Files           4        4
  Lines         308      308
=======================================
  Hits          248      248
  Misses         60       60

Impacted Files
Coverage Δ

generate_docker.py
0.00% <ø> (ø)

Continue to review full report at Codecov.

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


Mass accept applicants

Hi!
I work with Bitcamp, and we're looking into replacing our registration system with this. One important flow we have is bulk accepting applicants given a list of emails. See here.
Such a feature would be excellent for us, or at the very least it'd be great to have some API documentation right out of the box so we could put together a script to do it.
Thanks for the hard work on such a great application!

Hi, thanks for considering Dashboard!
This is a perfect example of a task that we do every year, but don't have specific code in our repo which covers every use case. One script (which is a Rails rake task) you can take a look at here: https://github.com/hackumass/dashboard/blob/master/lib/tasks/admissions.rake
You should be able to trivially modify this file to filter applicants as need-be.
Another future todo which isn't currently tracked in GitHub issues but is something that I'd like to see us add is a method of prioritizing applications; e.g., being able to set some students' application as priority level 1, some as level 2, and etc. And then when we decide on how many students we are able to accept, we can automatically pick as many as possible from group 1, flowing into group 2, until we hit our cap.
We can use this issue for tracking more extensive automation support to the admissions rake task. Thanks for the suggestion!


Use double quotes for shell expansion of ${script}

@bparees @jupierce I think this fixes the break.

@kargakis

Verified this fixes jobs manually

Thanks @smarterclayton


Storage dropdown is not selecting value when creating a new deployment

Setup

Rancher version:
v2.10-61d79963733364046c6fc8e9003bd9d6948a6db0-head
Dashboard | master 33b6680

Describe the bug
Found while testing https://github.com/rancher/dashboard/issues/11781
When creating a deployment, the dropdown displays the options as expected on both the pod and the container tab. However, for the container tab, as seen in the screen recording, the values the user selects from the dropdown are not actually being selected.
https://github.com/user-attachments/assets/b4c9c9ca-b433-426a-a1a1-e38576e59f21
And when trying to create the deployment, the following error occurs related to the volume (which might be related, otherwise, I'll file a new issue):

To Reproduce
Cluster Explorer --> Workloads --> Deployments --> Initial container tab --> Storage vertical tab
Expected Result
the values the user selects from the dropdown should be displayed in the UI and the deployment should be successfully created

e2e test coverage is sufficient. moving to done


Adding custom plugin to Kong enterprise edition

As Kong EE only have ljbc files how to add a custom plugin in Kong EE.
Steps To Reproduce

Create a "custom-auth.lua" file with content
local BasePlugin = require "kong.plugins.base_plugin"
local access = require "kong.plugins.request-transformer.access"
local RequestTransformerHandler = BasePlugin:extend()

function RequestTransformerHandler:new()
RequestTransformerHandler.super.new(self, "request-transformer")
end
function RequestTransformerHandler:access(conf)
RequestTransformerHandler.super.access(self)
access.execute(conf)
end
local ACLHandler = BasePlugin:extend()
function ACLHandler:new()
ACLHandler.super.new(self, "acl")
end
function ACLHandler:access(conf)
ACLHandler.super.access(self)
end

hit  curl -i -X POST --url http://localhost:8001/services/Service_req/plugins/ -F "name=pre-function" -F<EMAIL_ADDRESS>Getting the below error
{"config":"Error parsing pre-function #1: [string "local RequestTransformerHandler = BasePlugin:..."]:4: ')' expected near ''"}
The error we are getting bcz in Kong EE we do not have base_plugin.lua file, it have base_plugin.ljbc file
Do we need to compile the custom-auth.lua and add the ljbc file to Kong EE?
How to compile lua file.

You don’t need to compile down plugins for enterprise trials. They can be added as you would for any other plugin. See https://docs.konghq.com/1.0.x/plugin-development/distribution/#installing-the-plugin


[TechDocs] Update title and subtitle when location changes

Signed-off-by: Camila Belo<EMAIL_ADDRESS>Hey, I just made a Pull Request!
Always update the title and sub-title when the location changes on a TechDocs reader page.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@camilaibs this looks ready to go, just want to confirm with you first?


Immutable: update dependency

This is a simple keeping us current update that moves to the latest minor release version.

👍


LAB_04-Implement_Virtual_Networking.md

English:
Name server 1
Current Translation:
名稱伺服器 1
Suggested Translation:
Name server 1
Description:
It is code and should keep English

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Run the bugfix tool and waiting for result. ICMS QUERY

The issue has been fixed, so I close the PR.


How to set batch size in onnx model

hi, all
I hope that my yolov3 model is deployed on the tensorrt interence server. I downloaded tensorrt <IP_ADDRESS> and used tensorrt / samples / python / yolov3_onnx / yolov3_to_onnx.py to convert my darknet model to the onnx model and I configured tensorrt interence serve. When running with docker, he prompted me "Failed to load yolov3_onnx version 1: Invalid argument: unable to load model yolov3_onnx tensor 000_net shape expected by framework [1,3,416,416] doesnt match model configuration [3,416,416]" but I read the documentation The framework hopes that the model we input is [c, h, w] How can I modify yolov3_to_onnx.py. Hope someone can give me some suggestions. Thank you

this is my config.pbtxt
name: "yolov3_onnx"
platform: "onnxruntime_onnx"
max_batch_size: 0
input [
{
name: "000_net"
data_type: TYPE_FP32
format: FORMAT_NCHW
dims: [ 1,3, 416, 416 ]
}
]
output [
{
name: "082_convolutional"
data_type: TYPE_FP32
dims: [ 18, 13, 13 ]
},
{
name: "094_convolutional"
data_type: TYPE_FP32
dims: [ 18, 26, 26 ]
},
{
name: "106_convolutional"
data_type: TYPE_FP32
dims: [ 18, 52, 52 ]
label_filename:"coco_labels.txt"
}
]


Entity version missing in FLA

When generating the FLA, it only creates an Individual version, but not an Entity version.
Having an entity version also for the FLA would be preferable.
As an alternative, we might think about whether it makes sense to update the templates to cover both the individual contributor and entity version in the same text (what do you think @catharinamaracke ?) – might be tricky or actually prove to not be a good idea though.

As far as I understand this was deliberately taken out?

Also best to write Catharina a mail, not sure if she gets Github emails.

I think it was more the fact that we simply did get around to it. It has been requested by e-mail and in person enough times that we should have an Entity version for the FLA anyway.

Ah ok, thanks for the info. The template as such is basically already unified now. Things are taken out/added to get each version. Not sure atm how much work it would be for FLA, depends on how much would have to change. Just things that in the other CLA or more?

I think the goal would remain that the FLA and the other CLA templates would be very tightly intertwined. I.e. if you leave all options as defaults, you should obtain a CLA text which is identical to the FLA only without its preamble.
We made extra effort for this to be the case now, so I think we would continue to make the effort for this to continue in the future.

Ok, I think we are mixing some stuff up here.

one thing - entity for FLA, sure
other thing - all CLA options as default results in same as FLA minus preamble
last thing - as opposed to in beginning, agreement template is one file for all versions.
For all selections, the default selection seems to be the same as implied or selected by default for fla. (though I did not check text or code for this, just options chosen)
Adding entity version does not change that, no effort needed to keep it that way.

Just had a call with @catharinamaracke and we agreed that we should just generate the Entity version from the templates as they are for the FLA as well. We both recall that the fact it does not exist is a bug and that the templates should already be written in a way that this should be done easily.
As for my note about potentially rewriting the FLA/CLA templates so there would be no need for two documents, we might look into that next year during our 2021 revision of the FLA and CLA templates, but is outside the scope of this ticket.
Does that make sense and helps you in any way to enable the Entity FLA?

having generated 2 different examples and checking the code - individual vs entity only still matters in the name/subitle or if patent pledge, right? So in case of FLA, only the subtitle name would change, correct?

I thought there would have to be more changes, but apparently not...

Should be fixed in #31

Right now, the fla-entity is different in name only. Entity defintions are only included for patent pledge, so not included for FLA which does not have that, is that ok?
$('#review-text-fla #tmp-entity-definitions').hide();
           $('#review-text-fla-entity #tmp-entity-definitions').hide();
           if ( $( "#patent-type" ).val() == 'Patent-Pledge' ) {
               $('#review-text .tmp-entity-definitions').show();
               $('#review-text-entity .tmp-entity-definitions').show();
           }
           else {
               $('#review-text .tmp-entity-definitions').hide();
               $('#review-text-entity .tmp-entity-definitions').hide();

Right now, the fla-entity is different in name only. Entity defintions are only included for patent pledge, so not included for FLA which does not have that, is that ok?

Sounds about right, yes.
I diffed the MarkDown versions of the current FLA and the default entity CLA and it looks OK to me.

Ok cool. (the entity version added a lot of lines still, because two seperate texts are produced and I wanted to keep the way things are produced)

If you have an idea how to simplify these things, do let me know. If the diff is not really big, we should be able to simplify as much as possible.

Merged in #31. Please test if you like. Many repetitive things could be moved to functions or similar... but didn't want to do it as part of this feature.

Merged in #31. Please test if you like. Many repetitive things could be moved to functions or similar... but didn't want to do it as part of this feature.

I apologise for the late reply. Should this already work on the live instance of the chooser already?

I just tried it and apart from the name, I don’t even see any difference in the generated Individual vs Entity version even for a non-FLA choices.
Compare e.g.:
https://contributoragreements.org/ca-cla-chooser/?beneficiary-name=bla&project-name=&project-website=&project-email=&process-url=&project-jurisdiction=&agreement-exclusivity=exclusive&fsfe-compliance=&fsfe-fla=&outbound-option=fsfe&outboundlist=&outboundlist-custom=&medialist=____________________&patent-option=Traditional&your-date=&your-name=&your-title=&your-address=&your-patents=&pos=apply&action=

I just tried it and apart from the name, I don’t even see any difference in the generated Individual vs Entity version even for a non-FLA choices.
Compare e.g.:
https://contributoragreements.org/ca-cla-chooser/?beneficiary-name=bla&project-name=&project-website=&project-email=&process-url=&project-jurisdiction=&agreement-exclusivity=exclusive&fsfe-compliance=&fsfe-fla=&outbound-option=fsfe&outboundlist=&outboundlist-custom=&medialist=____________________&patent-option=Traditional&your-date=&your-name=&your-title=&your-address=&your-patents=&pos=apply&action=

As you can see from my comments above, that is apparently how it is supposed to be. Apart from name/subtitle and patent-pledge if chosen, there is no discernable difference. That is why I asked in above comment if that is correct. But I can only assume it must be, so unless you have different info or a future legal update concludes otherwise, this is how it is supposed to be.

Seems this popped up again – see #39 and #41

Re-closing in favour of https://github.com/contributoragreements/ca-cla-chooser/issues/45


sample.yaml not fount

Line 21 in run.sh should specify the correct name of the yaml file.
So instead of data/sample.yaml > "${OUTPUT_HTML_FILE}"
It should be data/bookmark.yaml > "${OUTPUT_HTML_FILE}"

Looks like a good catch!
If this is tested and has a works with the fix add a PR and I'll happily merge it.
(I am using the github action to build the html so I guess I missed it)

Yup, it's I consistent
https://github.com/georgettica/kubernetes-bookmark-bar/blob/d99cc25c8083dde88c9c9628b516d465ac94be9e/.github/workflows/upload-bookmark-html.yml#L32

@georgettica  It looks like I have no permissions to create a PR, therefore, the only thing need to be change to fix this issue is the last line in run.sh file.
It should be like this:
data/bookmark.yaml > "${OUTPUT_HTML_FILE}"

Was related to #9


Future Then callback that returns null and a when-resolved not null Future generates an exception

This only affects native dart (Flutter or the Dart CLI). dartpad does not generate this issue and executes correctly.
import 'dart:async';

void main() {
  Future.value(true).then<String?>((v) {
    if (v) {
      return Future.value('success');
    }
    return null;
  });
}

The above code when run generates this exception:
Unhandled exception:
type '(bool) => Future<String?>?' is not a subtype of type '(bool) => FutureOr<String?>'
#0      _FutureListener._onValue (dart:async/future_impl.dart:133:21)
<asynchronous suspension>

As I see it this should execute correctly, and indeed on the web (dartpad) it does.
Technically this is a FutureOr<String?>? I believe as this callback is not async and therefore is actually returning a null value.
However, if that's the case, why is the web version not generating this error?
Also, is the correct way to do something like this just make the callback async?

Dart SDK Version (dart --version)
Dart SDK version: 2.16.1 (stable) (Tue Feb 8 12:02:33 2022 +0100) on "macos_x64"

The problem does not reproduce for me in the tip-of-tree stand-alone VM either.
I can see that it does in the checked-in SDK we use for boot-strapping, so most likely the bug has already been fixed.

I would think that closure type actually comes from CFE, so it is probably a CFE issue which infers incorrect type for the closure.
@chloestefantsova @johnniwinther does this look like anything you have recently fixed in CFE?

This has been fixed by https://dart-review.googlesource.com/c/sdk/+/230240

@johnniwinther that CL just removed the cast. I think there indeed a VM issue. A simpler repro:
import 'dart:async';

Future<String?>? foo() {
  return null;
}

typedef F = FutureOr<String?> Function();

void main() {
  final F v = foo;
  print(v.runtimeType);
  print(v is F); // Returns false
  print((v as dynamic) as F); // Throws.
}

Seems like subtyping algorithm in the VM does not take into account that FutureOr<T?> is the same as FutureOr<T?>?

@sstrickl Could you look into this one?


Update User Guide

[x]  Fix Table of Content links
[x] Fix Ui.png
[x] Less wordy explanation

We have a lot of updates for User Guide.


dont clear names on missing oidc claims

Having these claim names hardcoded is still somewhat hacky. We'd need to change this with the OIDC rework.
Nextcloud for example only has the full name inside the name claim:
https://github.com/H2CK/oidc/wiki/User-Documentation#scopes

coverage: 88.644% (-0.04%) from 88.686% when pulling 5baa2998909aada31748e95301c6f8bf0d220de4 on fix-oidc-name-updating into af98f8aebde464c5122c762fea0b291d3d472225 on main.


Grafana: origin not allowed

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
After pulling today, I get "origin not allowed" on all panels. This is only under Ubuntu 20.04.3. Under Raspbian Bullseye all is fine, with identical setup.
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
No errors in grafana and teslamate logs.

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
1.27.0-dev

I perhaps important: grafana is running behind a reverse proxy with Apache.


DOC: add english doc 'access via rest api'

Signed-off-by: ZhangXiaozheng<EMAIL_ADDRESS>
Ⅰ. Describe what this PR does
Add english doc 'access via rest api' and fix typo in corresponding zh doc.
Ⅱ. Does this pull request fix one issue?

NONE

Thanks， @zhang-x-z . Great Translation!

/lgtm
/approve


#us5 ts95 loginpagelogic

#US5_ProjectManagement
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[Yes ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Description
This change hits the login authorization and pulls the Project API
Checklist:

[Yes ] My code follows the style guidelines of this project
[YEs ] I have performed a self-review of my own code
[ Yes] I have commented my code, particularly in hard-to-understand areas
[N/A ] I have made corresponding changes to the documentation
[Yes ] My changes generate no new warnings
[Yes ] I have added tests that prove my fix is effective or that my feature works
[ Yes] New and existing unit tests pass locally with my changes

Merging the branch after acceptance


[uint160] : Uint160DecodeStringBE does not produce the desired uint160

hashstring := "0xd2a4cff31913016155e38e474a2c06d08be276cf"
tokenHash, _ := neoutil.Uint160DecodeStringBE(strings.TrimPrefix(hashString, "0x"))
decimals, err := client().NEP17Decimals(tokenHash)

Produce: invocation failed: Called Contract Does Not Exist: 0xcf76e28bd0062c4a478ee35561011319f3cfa4d2
Am I doing it wrong?

Well, that's neo-project/neo#938 that is wrong here (but it can't be fixed now) and you've got a GAS contract hash that needs to be decoded with Uint160DecodeStringLE.

Seems to be solved to me.


Fix header indexes length

Replace logical incorrect check with "fool proofing" check.
Current check is logical incorrect because header length describes
length of data section withOUT index section itself
and we cannot statically check it at the point where this check is at the moment.

Excellent work, thank you. Upon revisiting this check, I see you are correct.

No problem, Ryan.
You've created great library, what I glad to work with.


Catch the exception 'TypeError' when parse_compile_commands_json fails

Exemple:
coercing to Unicode: need string or buffer, file found

Thanks for your contribution. It seems OK.


[3/x][checkpoint] Checkpoint Prologue transaction and Move function

Adds a system transaction that calls checkpoint_prologue -- a new move function in sui::sui_system.  This function does work at the beginning of each checkpoint (similar to the job of advance_epoch), which initially includes updating the clock, but may later be extended to support delegation.
Does not introduce the mechanism for injecting the CheckpointPrologue transaction at the start of each checkpoint.
Relaxes the previously added entry-point verifier to allow functions in sui::sui_system to accept mutable Clock parameters.
Test Plan
Test checking details of system transaction:
$ cargo nextest run -- test_checkpoint_prologue_transaction

Test checking that the transaction will not be signed if provided from an external source:
$ cargo nextest run -- test_refusal_to_sign_checkpoint_prologue

Test that the checkpoint_prologue updates the clock:
$ cargo nextest run -- checkpoint/clock.move

Stack

#7922
#8054

I suggest a name commit_prologue or consensus_commit_prologue rather then checkpoint_prologue. We would inject this transaction on every commit, but not necessarily on each checkpoint (since commit can be split into multiple checkpoints due to checkpoint size limit)


TOMEE-3931 fixed cucumber-jvm example and added deps/cucumber-openejb-shade module.

I am wondering about the re-generated BOM files. Adding a new shade dep shouldn't alter them? Perhaps an older (?) local state? Or did we alter the TomEE Jakarta API snapshot recently?

I wondered the same, I pull the latest master and after building without a test but with -Pno-examples, boms are updated. I opened a separate PR to double check that this was not related to adding a shade dep: https://github.com/apache/tomee/pull/876
If 876 is fine, we can merge and I'll rebase pr 875, or we can just go ahead with 875 and I would drop 876

I did merge #876, which led to https://github.com/apache/tomee/pull/877 by our automatic action, which should be the source of truth. If I am building master locally, I do not get any changed BOMs 🤔 Can you try with -U to update local SNAPSHOT artifacts?

Thank you for the review and help @rzo1 . You were right, updating snapshot by running locally mvn with -U removed the poms update from the PR. I rebase the PR now with only the changes for TomEE-3931

Hi @cesarhernandezgt ,
the PR looks good to me - I think we can proceed with it.
While testing it  locally, I noticed, that the README did not reflect the changes. Therefore, I went a head and updated it with the new versions / dependencies.

Nice, thank you!. Merging now...

Side note: can be worth doing it at cucumber directly instead of managing a fork ;)

@rmannibucau You are right - I was thinking the same. In the long run, it would be better to have it in cucumber. Therefore, I have opened an issue https://github.com/cucumber/cucumber-jvm/issues/2548, so we can discuss the possible ways of providing a Jakarta artifact at cucumber directly.


How to copy directory of *.tt files?

Hi!
Is it possible to copy a directory of *.tt files without executing template engine. I'd like to improve my rails templates and add custom scaffold templates (views, controllers and specs), but every time I use directory method
directory "lib/templates", force: true

I see an exception when thor tries to start template engine for those files. How to just copy my directory?

You can use FileUtils.cp. But I'm ok to add a new method that copies directory without using templates. Closing the issue since this is a feature request, but if you want to open a PR to add a new action, please do it.


New language agnostic, network compatible plugin framework

See also:

ZeroMQ plugin framework
MicroDrop Roadmap

We are planning to transition to a new plugin framework using a hub and spoke architecture (our current implementation is based on zeromq messaging). The goal is allow each plugin to operate as an independent process that registers with a central hub. Other goals of this framework are:

To be language agnostic (i.e., support plugins written in any language)
To allow plugins to run on a single computer or multiple computers connected over a network
Others?

Plugins can publish and subscribe to messages exposed through the hub. Some of this functionality is already implemented in MicroDrop 2.0 (e.g., the central hub, dmf_device_ui_plugin) but the intention is to migrate all existing plugins to using this framework and drop the PyUtilib-based system.
Some outstanding issues related to this process:
Legend - [x]: Done, [i]: In progress, [ ]: To do

[i] Language agnostic, network compatible plugin
communication

[x] Add zmq_hub_plugin as a core MicroDrop plugin
[i] Port existing **PyUtilib Component Architecture-based plugins to use the ZeroMQ plugin framework API.

[ ] New hook for launching v2.0 plugins: #197
[ ] Add support to specify plugin requirements as Conda packages (i.e., conda-requirements.txt) #199

This issue has been split into several sub-components: #197, #199, and #207.


Avoid relative imports in grpc code

Fixes #277

Would appreciate a review from either @MHDante or @Evgenus as well as they've contributed majorly to the GRPC stubs here.
My rationale is that this matches more closely to how the _grpc_pb2.py work, and obviates need for __init__.py files (at least matches more closely w/ how the .py works.

Looks good but what if generated files are not in root package?

I believe that you need to add your generated files directory to your PYTHONPATH or sys.path for things to work (see https://github.com/protocolbuffers/protobuf/issues/881). I think it's just a shortcoming of protobuf. Looks like the task was wont-fixed in 2017. I don't think that use case is well supported unfortunately.
mypy will find imports via this mechanism https://mypy.readthedocs.io/en/stable/running_mypy.html#finding-imports
For example, in our testsuite, the top of dummy_pb2_grpc.py looks like this
# Generated by the gRPC Python protocol compiler plugin. DO NOT EDIT!
"""Client and server classes corresponding to protobuf-defined services."""
import grpc

from testproto.grpc import dummy_pb2 as testproto_dot_grpc_dot_dummy__pb2

^ not using relative import.
With this diff, the dummy_pb2_grpc.pyi will match that - and thus work more similarly in cases like the one in #277


Questions about how to construt the initial <ml_network.csv> file for node classification task

Hi,
I would like to inquire about the structure of the <ml_network.csv> file, which appears to be formatted with '“u,i,ts,label,idx' style. From my understanding, the "label" field represents the label associated with the source node.
However, I am considering the scenario where the graph is a directed and homogeneous graph. In such a case, would it be possible to include labels for the target nodes as well in the <ml_network.csv> file? These target nodes are also significant entities in our analysis.
Thank you for your response.

Hello,
If I understand correctly, a simple solution for the mentioned case is to add a new column (maybe named as dst_label) to the <ml_network.csv> file, which stores the label of target nodes.
Then, when loading the dataset for node classification, you can add a line below here to read the target node labels, like dst_labels = graph_df.dst_label.values. Also, remember to add a new property of Data at here and below here, for example, self.dst_labels = dst_labels. Similarly, please get the target node labels here when using the target node labels to compute the loss.

Thank you very much! I think it is clear to me now.
I have another question regarding dynamic node classification. I have the edgelist csv file with three columns: source_id, target_id, and timestamp. the third column means that there are at least several interactions between the source node and the target node.

My question is that how to modify and condtruct the dataset and model trainig and test for supporting above scenario and dataset.

Firstly, for each line, you can split the interaction list into multiple lines, where each line stands for a single interaction. For example, split the first line u18839785, u266463103, "['2022-01-14 xxxx', '2021-11-30 xxxx']" into u18839785, u266463103, '2022-01-14 xxxx' and u18839785, u266463103, '2021-11-30 xxxx'.
Then, after splitting all the lines, you can sort the interactions in increasing order based on the timestamp.
The obtained data can be computed by our code.

Thanks a lot! I will check it ASAP.

Close this issue now. Feel free to reopen it when needed.

Hi,
I have a question regarding the dataset utilized in your code. Could you please specify if the dataset employed is an instance of a homogeneous graph within the context of dynamic node classification?

Hi,
Our work uses two datasets for dynamic node classification, including Wikipedia and Reddit. Compared with homogeneous graphs, these two datasets are bipartite with two types of nodes. You can refer to Section B.1 and Table 6 in our paper for more details.

Yes, I see.
However, I am uncertain as to how these models can be adapted to classify both source and target nodes in a single homogeneous graph.
Wikipedia and Reddit both contain source nodes that are labelled, but in a homogeneous graph, both source and target nodes must be labelled.
Could you please advise me on how to modify the code to accommodate this scenario? According to your previous suggestions https://github.com/yule-BUAA/DyGLib/issues/13#issuecomment-2080871203, it still does not work.
Thank you so much!

In my opinion, by adding a column to additionally denote the target node labels and loading them with slight code modifications, your case can be solved. Could you further explain why the previous suggestion cannot work?

Sure!

We obtain the original files like wikipedia.csv from previous work EdgeBank.
For the mentioned case, you can directly place the edge features as the original wikipedia.csv does. Then, for node features, if the node features change over time, you can append the features of source and target nodes after edge feature at each line. Moreover, you should also record the edge and node feature dimensions, so that you can split them like this. If the node features are consistent regardless of time, you can additionally save node features in a separate file with shape (num_nodes, node_feat_dim), and then load the node features by the node index in each line.


Max pool

What does this PR do?
Fixes #164.
We have restored thunder performance by having torchex running max_pool2d/3d via a single aten call, versus using the decomposed primitive operations using convolution.
A quick performance is demonstrated here:
This is before the PR:
jit_model elapsed time:  0.015625953674316406
torch eager elapsed time:  0.0018506050109863281

After the PR:
jit_model elapsed time:  0.0022668838500976562
torch eager elapsed time:  0.001873016357421875

Note this is only done for max_pool2d/3d. Because max_pool1d is implicitly differentiable in pytorch so there's no backward entry in aten.

I'm just changing the executor implementation. Hence I don't think I need to add extra tests apart from what's already in CI.


Extend JSON-schema with AppScope start message

This Pull Requests add start.msg info event:
Please see below overview of the changes:

Everything looks good here, but I'm not going to merge right away.
@abetones is doing some heavy lifting to add description fields in #812, and I don't want to add this in the middle of that activity.  I'd like a chance to coordinate this a little so we can finish that work, and then add descriptions for these new additions as easy as possible.

After talking with @abetones, I added "TBD " at the start of each new description field before merging.  The intent is to get this merged, but in a way that new description fields could be easily identified.
With this, we can merge whenever it's convenient.  The only reason I'm not doing it right now is that this change failed the "Build JSON schema reference" pipeline on the latest run.


#pragma once is more better than include guard

if we use modern c compiler, use #pragma once instead of old style #ifndef -- #endif .
macro names starting with one or two underscores, such as _HELLO_WORLD_H and __HELLO_WORLD_H, are reserved to the implementation and should not be used by the user.
#pragma once

void hello(char *buffer, const char *name);

#ifndef _HELLO_WORLD_H
#define _HELLO_WORLD_H

void hello(char *buffer, const char *name);

#endif

My only concern is that #pragma once isn't technically standard (because of issues that this repo will probably never encounter). If we're trying to showcase standard C practices, it may be best to stick with include guards.
I don't have strong feelings either way.

Good call, I didn't realize it wasn't standard. I figured it was part of a C standard newer than I'm used to in the embedded world.

but _HELLO_WORLD_H is not legal, you know. we have better use HELLO_WORLD_H if you want not to use pragma once.

Understood. We will use a legal include guard and avoid the non-standard #pragma once.

@fu7mu4 - Thanks for bringing these points up.


Styling enhanced

Fixes Issue🛠

[] New feature (styling has been updated,hover effect color, text and heading colors added )

Checklist✅

[] My code follows the style guidelines of this project
[] I have performed a self-review of my own code
[] I have commented my code, particularly in hard-to-understand areas
[] I have added demonstration in the form of GIF/video file
[] I am an Open Source Contributor

Screenshots/GIF📷
Hover color updated

Basic coloring updated:-

Please review and verify the above PR. Thank you

Update the issue number you have worked by adding #issuenumber. @YashBawa

@Rakesh9100 added the issue number.

Nice 👍, Merged !! @YashBawa


stages not working :((((((((

Describe your bug here.
lua stages on the week 7 build dont work, just black squares (they work on 0.5.2h)
https://imgur.com/a/Pgx5F2n
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
playstate, main menu state, but nothing related to lua

gonna do that tomorrow, kinda busy rn

https://drive.google.com/file/d/1MQnTTGAlD8e7usay1avh-Z5r-gpK4aFe/view?usp=drivesdk here it is, second song accessed by typing in "geddonbanjo" in the main menu.


Add simple tree navigation helper

Codecov Report

Merging #118 (f5de907) into main (08b33bc) will decrease coverage by 0.10%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##             main     #118      +/-   ##
==========================================
- Coverage   96.51%   96.41%   -0.11%
==========================================
  Files          13       15       +2
  Lines        1063     1087      +24
  Branches      132      133       +1
==========================================
+ Hits         1026     1048      +22
- Misses         18       19       +1
- Partials       19       20       +1

Impacted Files
Coverage Δ

xarray_sentinel/treenav.py
77.77% <77.77%> (ø)

tests/test_40_treenav.py
100.00% <100.00%> (ø)

xarray_sentinel/__init__.py
100.00% <100.00%> (ø)

xarray_sentinel/sentinel1.py
94.46% <100.00%> (+0.01%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us.


Hydration Error: UI Mismatch Between Server and Client

Describe the bug
The application throws a hydration error despite the server-rendered HTML and the client-rendered HTML being identical.
This issue occurs during the hydration process and causes the following problems:

Warning: Expected server HTML to contain a matching  in .
Hydration failed because the initial UI does not match what was rendered on the server.

Link to the Bolt URL that caused the error
https://github.com/stackblitz-labs/bolt.diy.git
Steps to reproduce
The server HTML is replaced with client content, leading to rendering inconsistencies.
This happens during tryToClaimNextHydratableInstance in the React reconciliation process.

Run the application in SSR mode (e.g., using remix-run).
Load the application in the browser.
Observe the console errors and warnings.

Expected behavior
No errors : The client-rendered UI should match the server-rendered HTML, allowing smooth hydration without errors.
Screen Recording / Screenshot
No response
Platform

OS: Windows 10
Browser: Chrome 131.0.6778.140 (Build officiel) (64 bits)
Framework: Remix (React)
Library: React (@remix-run/react, SSR enabled)
Error seen in: chunk-IXC3MVSS.js, hook.js, constants.ts

Provider Used
No response
Model Used
No response
Additional context
The server and client HTML outputs have been verified and are identical, but the hydration process still fails. This suggests a possible issue with how React processes the DOM during hydration.
localhost-1734463122848.log
Potential Causes:

React hydration misinterpreting the DOM structure.
Timing issues or hidden differences between the server-rendered and client-rendered DOM nodes.

try to clear your cache and if you have a value entered in the env for ollama delete it. Then just set the ollama baseurl in the settings

there is a mismatch on ModelList constant on server and UI hence the hydration error happens. we will look into this once we have fixed some of the bigger issues


Should we include the DIDComm and DIDAuthentication in this packages?

@OR13 Should we include the DIDComm and DIDAuthentication in this project? What's the best method for authentication e.g. DidAuth or Did Siop?

we don't support didcomm


Generate unicode ranges for ruby 2.5

Coverage remained the same at 100.0% when pulling aab42a329b2dc3d0a3f1dd4059e61b3a89ddee2c on ruby-2.5-update into 316cdc5354144a5c49787de407ea3664073829a9 on master.

Coverage remained the same at 100.0% when pulling d3dc6c9042af275b7130f349eea5d5feacc3e7bc on ruby-2.5-update into 316cdc5354144a5c49787de407ea3664073829a9 on master.


[Impeller] Filter graph should make an effort to re-use cmd buffers.

Command Buffers can encode multiple render or blit passes, provided that the previous render pass has completed before a new one is added. Since there is some overhead in creating and submitting a cmd buffer, we can slightly improve CPU performance on filter heavy scenes (backdrop blur benchmark) by utilizing the same cmd buffer in parts of the filter graph.
For example, the gaussian blur shader performs multiple render passes in sequential order, but uses a different cmd buffer for each one. These could be combined into a single cmd buffer.

FYI @bdero

Using the macrobenchmarks app backdrop perf example:
ToT: 427 Cmd buffers.
If we institute some basic reuse in the filter graph, we can reduce that to 250.

is that worth doing? uh question mark. Need to profile on iOS. In theory it shouldn't matter for Vulkan, and obvs not for GLES.

Nice to have, but ultra low priority?

This is done, sort of!


How to keep app running?

After starting my release app, how would I make sure that it will start automatically if the host got rebooted for any reason?

You would need to use upstart/systemd/etc. to manage that, exrm doesn't do anything in this regard itself.


[zh]Resync reference files after zh language renaming(reference-1)

related: https://github.com/kubernetes/website/issues/34221

content/zh-cn/docs/reference/labels-annotations-taints/_index.md

diff --git a/content/en/docs/reference/labels-annotations-taints/_index.md b/content/en/docs/reference/labels-annotations-taints/_index.md
index e68cb668d3..6622c63941 100644
--- a/content/en/docs/reference/labels-annotations-taints/_index.md
+++ b/content/en/docs/reference/labels-annotations-taints/_index.md
@@ -334,6 +334,24 @@ Used on: Service

 Kubernetes uses this label to differentiate multiple Services. Used currently for `ELB`(Elastic Load Balancer) only.

+### kubernetes.io/service-account.name
+
+Example: `kubernetes.io/service-account.name: "sa-name"`
+
+Used on: Secret
+
+This annotation records the {{< glossary_tooltip term_id="name" text="name">}} of the
+ServiceAccount that the token (stored in the Secret of type `kubernetes.io/service-account-token`) represents.
+
+### kubernetes.io/service-account.uid
+
+Example: `kubernetes.io/service-account.uid: da68f9c6-9d26-11e7-b84e-002dc52800da`
+
+Used on: Secret
+
+This annotation records the {{< glossary_tooltip term_id="uid" text="unique ID" >}} of the
+ServiceAccount that the token (stored in the Secret of type `kubernetes.io/service-account-token`) represents.
+
 ### endpointslice.kubernetes.io/managed-by {#endpointslicekubernetesiomanaged-by}

 Example: `endpointslice.kubernetes.io/managed-by="controller"`

content/zh-cn/docs/reference/kubectl/cheatsheet.md

diff --git a/content/en/docs/reference/kubectl/cheatsheet.md b/content/en/docs/reference/kubectl/cheatsheet.md
index e1711ea542..3412175285 100644
--- a/content/en/docs/reference/kubectl/cheatsheet.md
+++ b/content/en/docs/reference/kubectl/cheatsheet.md
@@ -280,7 +280,7 @@ kubectl patch deployment valid-deployment  --type json   -p='[{"op": "remove", "
 # Add a new element to a positional array
 kubectl patch sa default --type='json' -p='[{"op": "add", "path": "/secrets/1", "value": {"name": "whatever" } }]'

-# Update a deployment's replicas count by patching it's scale subresource
+# Update a deployment's replica count by patching its scale subresource
 kubectl patch deployment nginx-deployment --subresource='scale' --type='merge' -p '{"spec":{"replicas":2}}'

content/zh-cn/docs/reference/access-authn-authz/admission-controllers.md

diff --git a/content/en/docs/reference/access-authn-authz/admission-controllers.md b/content/en/docs/reference/access-authn-authz/admission-controllers.md
index 1e9f1a3298..f03b04f8e3 100644
--- a/content/en/docs/reference/access-authn-authz/admission-controllers.md
+++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md
@@ -139,7 +139,7 @@ requests with the `spec.signerName` requested on the CertificateSigningRequest r
 See [Certificate Signing Requests](/docs/reference/access-authn-authz/certificate-signing-requests/) for more
 information on the permissions required to perform different actions on CertificateSigningRequest resources.

-### CertificateSubjectRestrictions {#certificatesubjectrestrictions}
+### CertificateSubjectRestriction {#certificatesubjectrestriction}

 This admission controller observes creation of CertificateSigningRequest resources that have a `spec.signerName`
 of `kubernetes.io/kube-apiserver-client`. It rejects any request that specifies a 'group' (or 'organization attribute')

content/zh-cn/docs/reference/access-authn-authz/_index.md

diff --git a/content/en/docs/reference/access-authn-authz/_index.md b/content/en/docs/reference/access-authn-authz/_index.md
index 86d06488a8..3677f79c57 100644
--- a/content/en/docs/reference/access-authn-authz/_index.md
+++ b/content/en/docs/reference/access-authn-authz/_index.md
@@ -24,3 +24,5 @@ Reference documentation:
 - Service accounts
   - [Developer guide](/docs/tasks/configure-pod-container/configure-service-account/)
   - [Administration](/docs/reference/access-authn-authz/service-accounts-admin/)
+- [Kubelet Authentication & Authorization](/docs/reference/access-authn-authz/kubelet-authn-authz/)
+  - including kubelet [TLS bootstrapping](/docs/reference/access-authn-authz/kubelet-tls-bootstrapping/)

content/zh-cn/docs/reference/using-api/deprecation-guide.md

diff --git a/content/en/docs/reference/using-api/deprecation-guide.md b/content/en/docs/reference/using-api/deprecation-guide.md
index b72b60fb5a..d448344504 100644
--- a/content/en/docs/reference/using-api/deprecation-guide.md
+++ b/content/en/docs/reference/using-api/deprecation-guide.md
@@ -110,8 +110,10 @@ The **policy/v1beta1** API version of PodDisruptionBudget will no longer be serv

 PodSecurityPolicy in the **policy/v1beta1** API version will no longer be served in v1.25, and the PodSecurityPolicy admission controller will be removed.

-PodSecurityPolicy replacements are still under discussion, but current use can be migrated to
-[3rd-party admission webhooks](/docs/reference/access-authn-authz/extensible-admission-controllers/) now.
+Migrate to [Pod Security Admission](/docs/concepts/security/pod-security-admission/)
+or a [3rd party admission webhook](/docs/reference/access-authn-authz/extensible-admission-controllers/).
+For a migration guide, see [Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller](/docs/tasks/configure-pod-container/migrate-from-psp/).
+For more information on the deprecation, see [PodSecurityPolicy Deprecation: Past, Present, and Future](/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/).

 #### RuntimeClass {#runtimeclass-v125}

content/zh-cn/docs/reference/using-api/server-side-apply.md

diff --git a/content/en/docs/reference/using-api/server-side-apply.md b/content/en/docs/reference/using-api/server-side-apply.md
index 6b932278dc..e9f951a76a 100644
--- a/content/en/docs/reference/using-api/server-side-apply.md
+++ b/content/en/docs/reference/using-api/server-side-apply.md
@@ -125,7 +125,8 @@ this occurs, the applier has 3 options to resolve the conflicts:

 * **Overwrite value, become sole manager:** If overwriting the value was
   intentional (or if the applier is an automated process like a controller) the
-  applier should set the `force` query parameter to true and make the request
+  applier should set the `force` query parameter to true (in kubectl, it can be done by
+  using the `--force-conflicts` flag with the apply command) and make the request
   again. This forces the operation to succeed, changes the value of the field,
   and removes the field from all other managers' entries in managedFields.

Thanks.
/lgtm
/approve


Allow passing just the action if the route does not need any options

link "View Users", to: Users::Index

Duplicate of #66


Pendo: Track if users are coming from OSS or Ent and latest version

On OSS dashboard pass visitor metadata key as tier and value as OSS
On Enterprise dashboard pass visitor metadata key as tier and value as ent
For both OSS and Enterprise, latest version should be another key, with value as the latest version that was used.
https://support.pendo.io/hc/en-us/articles/360031832072-Visitor-and-Account-Metadata#what-key-values-are-supported-when-passing-metadata-through-the-snippet--0-13

@JamWils

For both OSS and Enterprise, latest version should be another key, with value as the latest version that was used.

What does the latest version mean in this context? Is it most recent browser version and name as in the doc you linked (which, I supposed, should be already logged by Pendo with the default visitor metadata by default) or is it the current dashboard version?

By latestVersion I am referring to the dashboard version they are using.  So we can target users based on "new features" we are trying to promote.

OK, thanks! Then I will submit whichever dashboard version I can get (I remember that before it was displayed with a commit hash if running from main, but now I see v0.12.0 without a commit, maybe smth. was changed).


undefined method `persistent?' for #Libvirt::StoragePool:0x007f15f546eeb8

maci@nb0815 ~/Desktop/libvirt % vagrant up --provider=libvirt
Bringing machine 'test_vm' up with 'libvirt' provider...
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.
An unexpected error ocurred when executing the action on the
'test_vm' machine. Please report this as a bug:
undefined method `persistent?' for #<Libvirt::StoragePool:0x007f15f546eeb8>

/home/maci/.vagrant.d/gems/gems/fog-1.15.0/lib/fog/libvirt/requests/compute/list_pools.rb:24:in `pool_to_attributes'
/home/maci/.vagrant.d/gems/gems/fog-1.15.0/lib/fog/libvirt/requests/compute/list_pools.rb:36:in `find_pool_by_name'
/home/maci/.vagrant.d/gems/gems/fog-1.15.0/lib/fog/libvirt/requests/compute/list_pools.rb:13:in `block in list_pools'
/home/maci/.vagrant.d/gems/gems/fog-1.15.0/lib/fog/libvirt/requests/compute/list_pools.rb:12:in `each'
/home/maci/.vagrant.d/gems/gems/fog-1.15.0/lib/fog/libvirt/requests/compute/list_pools.rb:12:in `list_pools'
/home/maci/.vagrant.d/gems/gems/fog-1.15.0/lib/fog/libvirt/models/compute/pools.rb:13:in `all'
/home/maci/.vagrant.d/gems/gems/vagrant-libvirt-0.0.11/lib/vagrant-libvirt/action/handle_storage_pool.rb:20:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/maci/.vagrant.d/gems/gems/vagrant-libvirt-0.0.11/lib/vagrant-libvirt/action/set_name_of_domain.rb:26:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/call.rb:51:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/home/maci/.vagrant.d/gems/gems/vagrant-libvirt-0.0.11/lib/vagrant-libvirt/action/connect_libvirt.rb:85:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/action/runner.rb:61:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/machine.rb:147:in `action'
/opt/vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'

1 maci@nb0815 ~/Desktop/libvirt % cat Vagrantfile                                                                                :(
Vagrant.configure("2") do |config|
If you are still using old centos box, you have to setup root username for
ssh access. Read more in section 'SSH Access To VM'.
config.ssh.username = "root"
config.vm.define :test_vm do |test_vm|
test_vm.vm.box = "lv-centos64"
test_vm.vm.network :private_network, :ip => '<IP_ADDRESS>'
end
config.vm.provider :libvirt do |libvirt|
libvirt.driver = "qemu"
libvirt.storage_pool_name = "default"
end
end

On my centos 7 install I get the same issue, but moving libcurl and the .pc file out of the way before installing the plugin doesn't work. I get the exact same error. Any other info I can provide?

Log for previous comment:
$ vagrant up --provider=libvirt
Bringing machine 'test_vm' up with 'libvirt' provider...
/home/bhundven/.vagrant.d/gems/gems/fog-1.27.0/lib/fog/libvirt/requests/compute/list_pools.rb:24:in `pool_to_attributes': undefined method `persistent?' for #<Libvirt::StoragePool:0x00000003691560> (NoMethodError)
        from /home/bhundven/.vagrant.d/gems/gems/fog-1.27.0/lib/fog/libvirt/requests/compute/list_pools.rb:36:in `find_pool_by_name'
        from /home/bhundven/.vagrant.d/gems/gems/fog-1.27.0/lib/fog/libvirt/requests/compute/list_pools.rb:13:in `block in list_pools'
        from /home/bhundven/.vagrant.d/gems/gems/fog-1.27.0/lib/fog/libvirt/requests/compute/list_pools.rb:12:in `each'
        from /home/bhundven/.vagrant.d/gems/gems/fog-1.27.0/lib/fog/libvirt/requests/compute/list_pools.rb:12:in `list_pools'
        from /home/bhundven/.vagrant.d/gems/gems/fog-1.27.0/lib/fog/libvirt/models/compute/pools.rb:11:in `all'
        from /home/bhundven/.vagrant.d/gems/gems/vagrant-libvirt-0.0.24/lib/vagrant-libvirt/action/handle_storage_pool.rb:20:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:34:in `call'
        from /home/bhundven/.vagrant.d/gems/gems/vagrant-libvirt-0.0.24/lib/vagrant-libvirt/action/set_name_of_domain.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/builtin/call.rb:53:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:34:in `call'
        from /home/bhundven/.vagrant.d/gems/gems/vagrant-libvirt-0.0.24/lib/vagrant-libvirt/action/connect_libvirt.rb:18:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:214:in `action_raw'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:191:in `block in action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/environment.rb:516:in `lock'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:178:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/machine.rb:178:in `action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

Same problem, also on ArchLinux !

I am having the same problem on Centos 7 with Vagrant 1.7.2 and libvirt 0.0.26. Any pointers to debugging/fixing would be appreciated.

try to update fog

Pronix - thanks for the suggestion - did a "gem install fog" but did not help.

try vagrant plugin install ... or vagrant plugin update ...

I worked around this issue by installing ruby-libvirt from the AUR and copying it over the version installed in ~/.vagrant.d. It sould keep things working at least for a while.

I'm flagging this as an upstream bug; if anyone could please report complete steps to replicate the issue under current vagrant (1.8.1+) and vagrant-libvirt (0.0.33) for any host OS, I will attempt to determine whether if we need to file a bug elsewhere.

I'm currently having that issue under vagrant 1.8.4 and vagrant-libvirt 0.0.33 on Arch Linux. None of the workarounds suggested above did help.
Steps to reproduce:

CFLAGS="-DHAVE_VIRDOMAINQEMUMONITORCOMMAND" vagrant plugin install vagrant-libvirt
(The additional CFLAGS is needed because a plain vagrant plugin install fails on Arch. An alternative is the install command mentioned in the Arch wiki which also worked to install the plugin).
vagrant init iknite/trusty64
vagrant up --provider libvirt

It fails with an error
Bringing machine 'default' up with 'libvirt' provider...
/home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:24:in `pool_to_attributes': undefined method `persistent?' for #<Libvirt::StoragePool:0x00032ca46c70e0> (NoMethodError)
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:36:in `find_pool_by_name'
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:13:in `block in list_pools'
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:12:in `each'
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:12:in `list_pools'
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/models/compute/pools.rb:11:in `all'
	from /home/me/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_storage_pool.rb:26:in `block in call'
	from /home/me/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_storage_pool.rb:23:in `synchronize'
	from /home/me/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_storage_pool.rb:23:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /home/me/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/builtin/call.rb:53:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/machine.rb:225:in `action_raw'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/machine.rb:200:in `block in action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/environment.rb:561:in `lock'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/machine.rb:186:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/machine.rb:186:in `action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

@katsel Using the CFLAGS option results in a broken native executable, instead better to switch the ld executable used for the duration of the plugin installation.
See https://github.com/vagrant-libvirt/vagrant-libvirt/issues/346#issuecomment-102145567
You'll need to completely uninstall vagrant-libvirt, then ensure that the ruby-libvirt plugin is completely removed. Switch the ld executable to the gold version, install vagrant-libvirt and then switch it back, and you should find that it is now able to correctly talk to libvirt through the ruby bindings.

@electrofelix Thanks for that hint!
I carefully followed the steps mentioned, and plugin install works without any issues, which is awesome. However, I'm still getting the same error when trying to bring the box up.
I also tried the CentOS box mentioned in the README of this project, same error.
Is there something else I am missing?
# remove old plugin
$ vagrant plugin uninstall vagrant-libvirt
Uninstalling the 'vagrant-libvirt' plugin...

# check that ruby-libvirt is removed
$ ls ~/.vagrant.d/gems/gems/
domain_name-0.5.20160615  ffi-1.9.12  vagrant-lxc-1.2.1

# use ld.gold
$ sudo ln -fs /usr/bin/ld.gold /usr/bin/ld

# re-install vagrant-libvirt
$ vagrant plugin install vagrant-libvirt
Installing the 'vagrant-libvirt' plugin. This can take a few minutes...
Installed the plugin 'vagrant-libvirt (0.0.33)'!

# attempt to start container
$ vagrant up --provider libvirt
Bringing machine 'default' up with 'libvirt' provider...
/home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:24:in `pool_to_attributes': undefined method `persistent?' for #<Libvirt::StoragePool:0x000329946c4bf0> (NoMethodError)
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:36:in `find_pool_by_name'
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:13:in `block in list_pools'
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:12:in `each'
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/requests/compute/list_pools.rb:12:in `list_pools'
	from /home/me/.vagrant.d/gems/gems/fog-libvirt-0.0.3/lib/fog/libvirt/models/compute/pools.rb:11:in `all'
	from /home/me/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_storage_pool.rb:26:in `block in call'
	from /home/me/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_storage_pool.rb:23:in `synchronize'
	from /home/me/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/handle_storage_pool.rb:23:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /home/me/.vagrant.d/gems/gems/vagrant-libvirt-0.0.33/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/builtin/call.rb:53:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/machine.rb:225:in `action_raw'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/machine.rb:200:in `block in action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/environment.rb:561:in `lock'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/machine.rb:186:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/machine.rb:186:in `action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.8.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

ping @infernix - I reported the steps to reproduce the issue above. Please let me know if there's anything else I can do.

@katsel i have installation testing for all distros except Arch I'm afraid. It's still on my list of distros to add.
As for the issue, I really am none the wiser after reviewing this, but it surely is an issue with how ruby-libvirt is being invoked/compiled. fog-libvirt just calls against ruby-libvirt and that interacts with libvirt itself.
If you look at ruby-libvirt, you can find:

#if HAVE_VIRSTORAGEPOOLISPERSISTENT
/*
 * call-seq:
 *   pool.persistent? -> [true|false]
 *
 * Call virStoragePoolIsPersistent[http://www.libvirt.org/html/libvirt-libvirt.html#virStoragePoolIsPersistent]
 * to determine if this storage pool is persistent.
 */
static VALUE libvirt_storage_pool_persistent_p(VALUE p)
{
    ruby_libvirt_generate_call_truefalse(virStoragePoolIsPersistent,
                                         ruby_libvirt_connect_get(p),
                                         pool_get(p));
}
#endif

Maybe you need to compile with that flag or otherwise determine why that flag isn't active during compilation? Is it in your extconf.h for the ruby-libvirt-built _libvirt.so?

@infernix: We found that one more step is required to reproduce the issue on Arch - it only happens when the ruby package has been installed via system package manager.
Meanwhile we got that problem fixed on my system. We did that by completely uninstalling all vagrant plugins, deleting the folder, emptying the gem cache, removing system ruby and re-installing the plugin according to the Arch wiki:
$ CONFIGURE_ARGS='with-ldflags=-L/opt/vagrant/embedded/lib \
with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib' \
GEM_HOME=~/.vagrant.d/gems \
GEM_PATH=$GEM_HOME:/opt/vagrant/embedded/gems \
PATH=/opt/vagrant/embedded/bin:$PATH \
  vagrant plugin install vagrant-libvirt

It seems like the issue stems from the fact that system ruby and vagrant's own ruby get mixed up in weird ways during plugin install.

I'm going to close this one for now since we've added the compilation option to the documentation and I'm about to add some CI to test for these types of issues across all popular distros.
If this pops up again feel free to comment/reopen!


Items without Swipe Menu

Can we disable menu for some items ? If how, please provide a solution. I have a list in which the default item should not have the swipe menu, rest need the menu. Is it possible ?

Same requirement. If possible provide solution ASAP.

Plz, same question, how can i disable swipe on header items?

Guys, solution is so easy and writen in README file =) just read it carefully! It's all about viewType


Make it work with .netrc

This way people do not need to expose a github token in the config.
https://gist.github.com/technoweenie/1072829

If we move off of using tarballs -> git, it would allow other services such as gitlab. See #10

https://github.com/jazzdev/node-netrc

I wasn't sure if this way would work with the deploy scripts.

It will, we made it work on semaphore. just place .netrc in the ~/
If CI cannot provide you isolated environment, it should not be used at all.

We are moving away from tarballs to using pure git. So this will be fixes in #19


Wire up MRT Core to Windows App SDK Insights

Not ready for review yet because:
Builds, but verification using build artifact is pending.

/azp run

/azp run

/azp run

/azp run

@rohanp-msft Hey just curious, were you going for a name-based v5 GUID or a random one? That new GUID you put in there is v5. (The commit comment wasn't clear which was desired.)

@rohanp-msft Hey just curious, were you going for a name-based v5 GUID or a random one? That new GUID you put in there is v5. (The commit comment wasn't clear which was desired.)

Yup, I was. I should have made the commit description clearer.

@rohanp-msft Cool, just double-checking. I'll go back into hiding!

/azp run

Do not move this file. The file is accessed from the build scripts. It was intentionally left in the root of WindowsAppSDK_Insights. Also, do not remove the reference to WindowsTelemetry-Internal. This is needed to replace the TraceloggingConfig with the correct version

Refers to: dev/WindowsAppSDK_Insights/WindowsAppSDKInsightsLib/nuget.config:2 in 3d8cb90. [](commit_id = 3d8cb9011362bdeabe05fa02c57cb94bf05f2b3c, deletion_comment = False)

Do not move this file. The file is accessed from the build scripts. It was intentionally left in the root of WindowsAppSDK_Insights. Also, do not remove the reference to WindowsTelemetry-Internal. This is needed to replace the TraceloggingConfig with the correct version
Refers to: dev/WindowsAppSDK_Insights/WindowsAppSDKInsightsLib/nuget.config:2 in 3d8cb90. [](commit_id = 3d8cb90, deletion_comment = False)

Done.

Not needed.

Refers to: dev/WindowsAppSDK_Insights/WindowsAppSDKInsightsLib.sln:38 in b4e16fe. [](commit_id = b4e16feb02c76a52ae41d51c8b9a2435bb684c8b, deletion_comment = False)

/azp run


Patch 1

Building off of #470 (closes #470).

I'm off on holiday so I got to this late. Looks awesome; I'm gonna add the dist file and get this merged! :+1:


README.rst: Change image URLs from blob to raw

so that they show up on PyPI.

There we are: https://pypi.python.org/pypi/ptpython :+1:
Thanks!
Merge in: https://github.com/jonathanslenders/ptpython/commit/cba050ca986e8928ba941d8d8cd6beaf0b1884a6

Nice!!!

Now I need to start playing with all the features of ptpython. It looks awesome!!!
https://twitter.com/MSAbramo/status/559384448832008192

Have fun!!
And feel free to create a GitHub issue when you feel something can be improved.


go: invalid go code for a module that only has static methods

:bug: Bug Report
Affected Languages

[x] Golang
[ ] TypeScript or Javascript
[ ] Python
[ ] Java
[ ] .NET (C#, F#, ...)

General Information

JSII Version: 1.22.0
Platform: any

What is the problem?
jsii modules that only have static methods will result in invalid go code since the _init_ module is not imported.
Verbose Log

cloudassemblyschema/cloudassemblyschema.go:1895:2: undefined: _init_

Root cause
The root cause is that the usesInitPackage of GoClass does not take static methods/properties into account.

This is a blocker for #2611

@MrArnoldPalmer since this is blocking the CDK, I don't think it's a P2...

Fixed by https://github.com/aws/jsii/pull/2622

Reopening until a test is added


FTDI connection does not charge the Device

The USB transfer happens between the phone and the FTDI chip. I want the phone to get charged simultaneously when it's transferring data.
FTDI chips provides 5V to the phone and the phone gets charged when it's not transferring data.
Is there any mode I should switch on for it to power the USB bus and also allow data transfer.

same. did u find any solution @mnive93 ?

@mnive93 Did you finally get around this?


VBA - create standard, add processing and create as element  - Not Working as Expected

When using the create_standard_vba function, the function is expected to create a new VBA representing a drilling with specific dimensions. Despite the function's apparent success in creating a VBA, subsequent attempts to set its parameters (such as section diameter and overall diameter) lead to errors, and the created VBA cannot be assigned to an element ID.
I am seeking assistance to:

Understand how to correctly set the parameters for the created VBA.
Correct the code or process to allow for the successful creation and manipulation of VBAs.

import cadwork
import connector_axis_controller

>>>connector_axis_controller.create_standard_connector("MyScrew", cadwork.point_3d(0.,0.,0.), cadwork.point_3d(0.,0.,100.)) # standard connector must exist in your 3d document
841935134
>>>connector_axis_controller.set_bolt_length(841935134, 400.0)
>>>connector_axis_controller.get_bolt_length(841935134)
400.0
>>>connector_axis_controller.update_axis_cutting_ability([841935134])
>>>connector_axis_controller.get_section_count(841935134)
4
>>>section : int = 2
>>>connector_axis_controller.set_section_diameter(841935134, section, 40.0)
>>>connector_axis_controller.get_section_diameter(841935134, section)
40.0


dimension mismatch in args to gemm (64,121)x(121,100)->(64,121)

I have a dataset of size 84000x121 (image patches) and I want to train a autoencoder with single hidden layer. My architecture is 121 -> 100 -> 121 and use the hidden layer as features to train a regression model (say SVR).
import h5py
import scipy.io as sio
import numpy as np

from keras.models import Sequential
from keras.layers import containers
from keras.layers.core import Dense, AutoEncoder
from keras.activations import sigmoid
from keras.utils import np_utils
from keras.optimizers import SGD, RMSprop

# layer dimension
h1_dim = 100
input_dim = 121

# training data
data = sio.loadmat('../data/GBLUR_Patches.mat')
X_train = data['all_patches']
X_train = np.transpose(X_train)
# X_train = X_train.reshape(84000,h1_dim)

print np.shape(X_train)

# define model
model = Sequential()
encoder = containers.Sequential([Dense(output_dim=h1_dim, input_dim=input_dim)])
decoder = containers.Sequential([Dense(output_dim=input_dim, input_dim=h1_dim)])
model.add(AutoEncoder(encoder=encoder, decoder=decoder, output_reconstruction=False))

# optimizer
rms = RMSprop(lr=0.001, rho=0.9, epsilon=1e-06)
model.compile(loss='mean_squared_error', optimizer=rms)

# fit model
model.fit(X_train, X_train, nb_epoch=10, batch_size=64, validation_data=None, verbose = 2, shuffle=True, show_accuracy = `False)

But when i train this model i'm getting the following error
Epoch 1/10
Traceback (most recent call last):
File "autoencoder_gblur.py", line 38, in
model.fit(X_train, X_train, nb_epoch=10, batch_size=64, validation_data=None, verbose = 2, shuffle=True, show_accuracy = False)
File "/usr/local/lib/python2.7/dist-packages/Keras-0.3.3-py2.7.egg/keras/models.py", line 701, in fit
shuffle=shuffle, metrics=metrics)
File "/usr/local/lib/python2.7/dist-packages/Keras-0.3.3-py2.7.egg/keras/models.py", line 317, in _fit
outs = f(ins_batch)
File "/usr/local/lib/python2.7/dist-packages/Keras-0.3.3-py2.7.egg/keras/backend/theano_backend.py", line 446, in call
return self.function(*inputs)
File "/usr/local/lib/python2.7/dist-packages/theano/compile/function_module.py", line 871, in call
storage_map=getattr(self.fn, 'storage_map', None))
File "/usr/local/lib/python2.7/dist-packages/theano/gof/link.py", line 314, in raise_with_op
reraise(exc_type, exc_value, exc_trace)
File "/usr/local/lib/python2.7/dist-packages/theano/compile/function_module.py", line 859, in call
outputs = self.fn()
ValueError: dimension mismatch in args to gemm (64,121)x(121,100)->(64,121)
Apply node that caused the error: GpuGemm{inplace}(GpuFromHost.0, TensorConstant{1.0}, GpuFromHost.0, dense_W, TensorConstant{-1.0})
Toposort index: 15
Inputs types: [CudaNdarrayType(float32, matrix), TensorType(float32, scalar), CudaNdarrayType(float32, matrix), CudaNdarrayType(float32, matrix), TensorType(float32, scalar)]
Inputs shapes: [(64, 121), (), (64, 121), (121, 100), ()]
Inputs strides: [(121, 1), (), (121, 1), (100, 1), ()]
Inputs values: ['not shown', array(1.0, dtype=float32), 'not shown', 'not shown', array(-1.0, dtype=float32)]
Outputs clients: [[GpuElemwise{Add}[(0, 1)](GpuDimShuffle{x,0}.0, GpuGemm{inplace}.0)]]
HINT: Re-running with most Theano optimization disabled could give you a back-trace of when this node was created. This can be done with by setting the Theano flag 'optimizer=fast_compile'. If that does not work, Theano optimizations can be disabled with 'optimizer=None'.
HINT: Use the Theano flag 'exception_verbosity=high' for a debugprint and storage map footprint of this apply node.
Please anyone can help me with this..

model.add(AutoEncoder(encoder=encoder, decoder=decoder, output_reconstruction=False))

output_reconstruction has to be True for training.


Support WebIDL getters and setters

https://heycam.github.io/webidl/#idl-special-operations
interface Dictionary {
  readonly attribute unsigned long propertyCount;

  getter double (DOMString propertyName);
  setter void (DOMString propertyName, double propertyValue);
};

These are the moral equivalent of Index and IndexMut traits in Rust, except that those must return references and we can't support that (especially with fallible getters and setters). Maybe just translate these into get and set functions?

From the link in the issue body:

Not all language bindings support all of the five kinds of special object behavior. When special operations are declared using operations with no identifier, then in language bindings that do not support the particular kind of special operations there simply will not be such functionality.

In some cases there are replacement operations:
interface SVGStringList {
  [Throws]
  DOMString getItem(unsigned long index);
  getter DOMString(unsigned long index);
  [Throws]
  DOMString replaceItem(DOMString newItem, unsigned long index);
  setter void (unsigned long index, DOMString newItem);
  ...
};

But in some cases there are no:
interface HTMLOptionsCollection : HTMLCollection {
  [CEReactions, SetterThrows]
  attribute unsigned long length;
  [CEReactions, Throws]
  setter void (unsigned long index, HTMLOptionElement? option);
  [CEReactions, Throws]
  void add((HTMLOptionElement or HTMLOptGroupElement) element, optional (HTMLElement or long)? before = null);
  [CEReactions, Throws]
  void remove(long index);
  [Throws]
  attribute long selectedIndex;
};

[OverrideBuiltins]
interface DOMStringMap {
  getter DOMString (DOMString name);
  [CEReactions, Throws]
  setter void (DOMString name, DOMString value);
  [CEReactions]
  deleter void (DOMString name);
};

So probably they should be always generated, despite the specification says otherwise?

@afdw hm I'm not sure I understand, but the spec may also be confusing me. The spec mentions five operations but only lists four in the table above, and additionally I don't think a replacement operation is one of the one it lists? (unless it's the elusive fifth)
How would we generate bindings though for missing operations?

The spec mentions five operations but only lists four in the table above

Yes, it also confuses me.
From my understanding, the spec says that for special operations with empty name no bindings should be generated if the target language does not support that kind of operation.
It means that these futures will be missing to the user of the bindings. And I think that the spec assumes that there are replacement operations, that such operations are only syntactic sugar, not essential functionality.
I have provided an example when it is the case. As you can see, getItem replaces the unnamed getter and replaceItem replaces the unnamed setter.
But, I have also shown 2 real examples when it is not the case, when there is no replacement regular operations for languages that do not support that kind of operations. So, if I have understood the spec correctly, it means that there will be no way to use this functionality in such languages at all.
So I think that we can ignore the spec here and always generate regular functions named get/set/delete in Rust.

Aha that makes sense! FWIW in the spec the "Example 15" makes me think that it's actually not possible for getters/setters to be named, but rather a named getter/setter is actually sugar for an unnamed getter/setter plus the actual function itself. In that sense I think we'll always have to deal with the getters/setters not having names!
I agree though that the best way to implement this for now is probably bare method names like get, set, and delete. We can double check that it doesn't conflict with an existing method, and otherwise I definitely agree it's best to provide the functionailty somehow rather than leaving it out because Rust doesn't have native getters/setters :)


TextIntroduction -- Functional Dot Notation

Closes #260
Changes

TextIntroduction is now more composable with subcomponents
TextIntroduction story is updated (click on See Code)

How to test this PR

View TextIntroduction Storybook story
Code Inspection
yarn test TextIntroduction

Screenshots

Also, if we decide to move forward with this, please update the unit tests.

I feel like there are more negatives than positives here:

280 more characters to achieve the same ouput
More tags to visually parse in order to understand what is being rendered
Requires dev to put elements in the correct order
Allows devs to implement the pattern incorrectly

A big part of building this library is to codify the DS patterns in order to keep visual outputs aligned.  We've definitely built other escape hatches into our components that would allow devs to stray from the prescribed design but I'm not convinced the level of freedom or responsibility that this PR provides is what we want.
Would be good to have a chat with @natalia-fitzgerald and @billhimmelsbach to explore the pros/cons.

Heyo! Sorry @shindigira and @meissadia for the sick delay here. 🤒 I might have missed some context here while I was out, but did you have a use case @shindigira where you needed to compose these pieces of TextIntroduction for something on a page you were working on or is it that you thought this would just be a helpful refactor?

To begin with there is an immediate use case from the Figma that breaks the component. One of said string props can no longer be a string prop; requires an actual component.

Could you point me to that Figma mockup?

@billhimmelsbach @shindigira
The "text introduction" is a specific component/pattern in the DS and should only be used in a limited number of ways. I did share some cf.gov outliers in last week's DSR meeting but these examples really no longer use the "text introduction" component (and decisions to break the component were specifically made by designers - not devs). For the sake of our component library we will want the component's design to push people to use it in the correct ways. So we should build in only the flexibility needed to accomplish the component's intent.

Heyo! Just to recap our discussion @meissadia and @shindigira: we'll add an export to TextIntroduction that composes these subcomponents into one that shares the same props as the original TextIntroduction: strings and ReactNodes for parts of the component that require links. That way we'll get the best of both worlds: a more rigid component to enforce design standards built upon flexible, forward thinking subcomponents that we can use/compose for future use cases.
@shindigira will make sure that this new composed component meets his needs for his use case. 👍

Great! Could you merge with main then I'll take a peek tomorrow. 👍


Access Violation in PascalCoinWallet.exe Build 1.5.6

I attempted to "Close" the wallet from the FileMenu because it said "NO BLOCKCHAIN" and "Obtaining valid blockchain". I had already restarted it once because it seemed to not be connecting to the network.
This time when I closed it I got an infinite loop of "Access violation at address 005608EE" messages and had to force quit from the task manager.

Restarted Computer and tried again:

Hi Aaron, I guess you are sending the message to a wrong mail address. We are Creativechain and our coin is Creativecoin (CREA) and not PascalCoin. You can get our wallet in: www.binaries.creativechain.net/latestBest regards,Creativechain Team
El 15 de junio de 2017 a las 16:58 Aaron Clymer<EMAIL_ADDRESS>escribió:I attempted to "Close" the wallet from the FileMenu because it said "NO BLOCKCHAIN" and "Obtaining valid blockchain". I had already restarted it once because it seemed to not be connecting to the network.
This time when I closed it I got an infinite loop of "Access violation at address 005608EE" messages and had to force quit from the task manager.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

Please upgrade to V2.
Many bugs fixed. Thanks


Array converted to string in array field

Describe the bug
Having a ArrayType field and using the create method from the repository convert the array to simple string, so it fails the DB constrain
Stack trace
DriverException: insert into `sms` (`affected_field`, `content`) values ('FirstValueOfMyArray', 'Example Message') - CONSTRAINT `sms.affected_field` failed for `myDB`.`sms`

To Reproduce
Steps to reproduce the behavior:

Having a array field with ArrayType type
Create a repository of that entity
Use the create method and use a normal array in the field

Expected behavior
The entity is inserted and created
Additional context
I tried to create a repro with stackblitz and sqlite but there it worked.... In my real project I use the mysql driver, maybe is only in that driver?
@Entity()
export class SMS {
  @PrimaryKey()
  id!: number;

  @Property()
  content!: string;

  @Property({ type: ArrayType })
  affectedField!: string[];
}

let repo = orm.em.getRepository(SMS);

let user = await repo.create({
  content: 'Ejemplo',
  affectedField: ['FirstValueOfMyArray'],
});

console.log(user);
expect(user.affectedField).toEqual(['FirstValueOfMyArray']);

Versions

Dependency
Version

node
16.17.0

typescript
4.8.3

mikro-orm
5.4.2

mikro-orm/mysql
5.4.2

Hmmm actualy, I think you should use JsonType here - mysql does not have native array type support like postgres does, so you will be in fact using a JSON column. Its still worth fixing (or automating) as the current behaviour is indeed confusing, ideally the array type should work out of box like in other drivers.

So the issue is only about em.create()? If you do user.affectedField = ['FirstValueOfMyArray'] it works?

Using the dev versions fails too.
With the JSONType is works! It generates the right array I don't know why.
Maybe is a bit confusing as you say, in mysql ArrayType and JSONType maybe can be the same under hood?

Oooh right, actually - this is working as expected. ArrayType produces comma separated string as a value - you have one item, so no commas. The serialized form looks like the first array item in this case.