Files reverted and deleted by Git panel not in trash

VSCode Version: 1.36.0
OS Version: 4.19.56-1-MANJARO

Steps to Reproduce:

Have setting files.enableTrash enabled.
Create a new file in your workspace.
Use the Git panel revert changes icon to delete the new file.
File not found in trash.

Does this issue occur when all extensions are disabled?: Yes.
Why I think this is a bug:

The major facility for working with files, the Explorer panel, always moves files to the trash.
So, the user gets used to depending on the relative safety of using VSCode to deal with files.
Changing the behavior in another panel, even though the alert message says that the file will be "DELETED" in all caps, is very unexpected.
At the very least, the alert message should make this change of behavior more clear with more text IMO.

Thanks!

The git integration only uses git commands, which do not understand the concept of a trash. As the setting indicates, files.enableTrash, this is only related to file actions, not Git/SCM actions.

At the very least, the alert message should make this change of behavior more clear with more text IMO.

We can do more text, do you have any recommendations?

Thanks!
If you are not interested in making git commands follow the files.enableTrash setting then it would be nice to see another line appended to the original text, something like "Please note that these files will NOT be sent to Trash.".
However, since we know what GIT will do when we run the revert changes command on an untracked file, wouldn't it be really nice if VSCode just sent those files to trash for you? I am usually pretty careful about what I'm deleting but I have certainly regretted reverting changes in the past. As a matter of fact, I'd love to see VSCode send even tracked files with modifications to Trash before reverting them...
I suppose that I can do this with some sort of bash script that replaces my system git command but that sounds like a lot more work than what could be done from inside VSCode.

For now, since I've discovered this behavior, I think instead of reverting files, I'll try to get into the habit of using the VSCode Explorer panel to delete the files that I want to revert (to Trash) and then revert the deletions in the GIT panel. That is certainly the safest workflow.

I think DELETED already implies that they won't go to trash, but they will be deleted instead. Sorry about your missing files, but I'm glad you found a workflow which works for you.

I disagree because in many, many contexts DELETING something means you're sending it to the trash.
By far the most used OS (Windows) labels the context menu in Explorer as Delete, the command that actually sends things to the recycling bin.
So, I think it's a very bad idea to not differentiate what is actually happening in this scenario because people will continue to lose files.

Alright. We were already showing the following message when using the Discard All action:
This is IRREVERSIBLE!
Your current working set will be FOREVER LOST.

I've added the same disclaimer for the Discard action.


Update django classifiers

Add 1.11 and 2.0 to match with those tested in tox.ini
I just realized that https://github.com/arteria/django-hijack also tests on django 2.1, do we want to add that here too?

Coverage increased (+4.4%) to 100.0% when pulling 8529b638e9d03c6eae562a3554ce677ee32736dd on andyzickler:patch-1 into 934b2b94defe2986f66642bd60238cf752db8803 on arteria:master.

This change has been superseded by other PRs. Looks like the repo is abandoned though :(


Add as_x fns for layer types

Improves crate ergonomics. Most of the time when parsing you are only interested in one layer type at a time so it's much nicer to use layer.layer_type().as_tiles() than the whole match block. Specially nice for closures in filters:
// Old
let tile_layers = self
    .map
    .layers()
    .filter_map(|l|
        match l.layer_type() {
            tiled::LayerType::Tiles(tl) => Some((l, tl)),
            _ => None,
        }
    );

// New
let tile_layers = self
    .map
    .layers()
    .filter_map(|l| Some((l, l.layer_type().as_tiles()?)));

Crates like serde_json do this with some of their enums.

That seems useful indeed. One thing I'm wondering, since it seems that in all cases you'd need to call .layer_type() first, would it make sense to put the as_tiles, etc. functions on Layer instead of LayerType, similar to the functions that used to be in the tests? And maybe then using those names instead, so they match their return value?

Not 100% sure. For symmetry wouldn't that mean we should also have those methods in LayerType as well?

Not 100% sure. For symmetry wouldn't that mean we should also have those methods in LayerType as well?

As a pure convenience addition, I think that depends on whether it is a common scenario to have a LayerType instance without having access to the related Layer, but I have my doubts about that.
In my mind, the "LayerType" enum is a kind of workaround for the lack of inheritance in Rust, so I welcome these functions as a way to let this type fade a bit more into the background. We keep layer_type() for those cases where it is really more convenient to do a match, but I don't see a need to provide the as_x convenience functions also there.

I've only used this crate in one project, but IMO I don't see any use for having a LayerType without a Layer; I agree that it feels very much like an 'implementation detail'. So I'd just define the methods directly on Layer itself (as well as as_finite_tiles and as_infinite_tiles). If there does wind up being a need for putting it on the LayerType then you can just move the methods to LayerType and delegate.
In terms of naming, I like as_tile_layer, as_object_layer and so on. as_tiles makes me think it'll give me a Vec<Tile> or something.

Oops, this took so long to merge that the changelog ended up in the wrong place. Will need to fix that at some point.


Expand first-level of class hierarchy and file hierarchy by default

We have every class in our own namespace + directory, so the hierarchy looks something like this

Namespace X

Directory X

It would be very nice if there was a config for expanding the first level of the hierarchy by default, so that the user does not have to click it. We are using sphinx_rtd_theme, with "createTreeView": True.

Hi @apartridge,
So just to make sure I understand, you are wanting to have an option to expand stuff one level while using the sphinx_rtd_theme?  Right now there's a bootstrap version of that treeViewBootstrapLevels.
Easiest to just confirm with a picture, compare the current output online with the following screenshot made by setting it to two (git clone https://github.com/svenevs/exhale-companion.git -b bootstrap)
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -68,6 +68,7 @@ exhale_args = {
     # HTML Theme specific configurations.                                      #
     ############################################################################
     "treeViewIsBootstrap": True,
+    "treeViewBootstrapLevels": 2,
     # NOTE: there exist many other options for you to tweak.  See
     # http://exhale.readthedocs.io/en/latest/reference_exhale_configs.html#bootstrap-mods
     ############################################################################

The bootstrap stuff is all kind of legacy at this point, I'm not telling you to switch themes, just making sure this is what you are looking for only for the collapsibleLists version (the default, unless you set treeViewIsBootstrap to True).
I need to fix some broken CI but am hoping I can hack in a quick feature patch.  The javascript library is different, but the logic tracking levels is already in place so it may just be a matter of changing something small.  Let me know if this isn't what you are looking for, but I'll proceed assuming it is :slightly_smiling_face:

Hi @svenevs, yes that sounds correct.


POL-1365 Update Policy Permissions Automation - support for crossed-dagger symbol

Description

For policy permissions in the Readme which have more than two different footnotes, we must use another symbol to differentiate them.
Currently we are using and asterisk and a dagger, but now we have an example of a readme where the permissions have 3 different types of footnotes and therefore this is a change to add the crossed-dagger footnote symbol.
Also, this makes a change to the Dangerfile so that the Pull Request checks also support the new symbol (as well as the existing dagger symbol)
Issues Resolved

Link to Example Applied Policy

Contribution Check List

[x] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

Tested for a policy with AWS, Azure and Google Cloud permissions respectively
Tested for each symbol, and if the symbol exist for a permission, whether a footnote also exists
Example:

As per this page https://en.wikipedia.org/wiki/Note_(typography)#:~:text=Typographic characters%2C such as the,sign §%2C (v) the, I have added support for the following footnote symbols:
(i) the Asterisk [*]
(ii) the Dagger mark †
(iii) the Crossed dagger mark ‡
(iv) the Section sign §
(v) the Vertical bar ‖
(vi) the Pilcrow ¶
May move to a number system in future, but this gives us what we need for now


[DDW-794] Implement the Catalysts Fund7 screen

This PR implements the new design for catalysts fund7 screen
Todos

[x] Add translations

Screenshots

Default state

Non default date/number format

Register button enabled

Testing Checklist

Slack QA thread
[ ] Test

Review Checklist
Basics

[ ] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes
[ ] PR has default-sized Daedalus window screenshots or animated GIFs of important UI changes:

[ ] In English
[ ] In Japanese

[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance and unit tests are passing (yarn test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[ ] There are no flow errors or warnings (yarn flow:test)
[ ] There are no lint errors or warnings (yarn lint)
[ ] There are no prettier errors or warnings (yarn prettier:check)
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

@lucas-barros please replace any Fund5 and Fund6 in the voting wizard by Fund6 and Fund7, preferably by creating a CURRENT_CATALYST_FUND variable.

QRs lack left and right padding

proportions of those blocks should be 1:2

there is space to fit it 1 line :)

@lucas-barros @renanvalentin please make sure it works well in the window's minimum width, 905px.

@alexander-rukin i've created two versions. The first one has a fixed size and the other will scale accordingly.
Fixed size:

Liquid layout (this is the one used)

@renanvalentin the Learn More button is still breaking in the mim width. Maybe you could remove the padding and add a width. All the rest looks great ✨

@lucas-barros @renanvalentin Nice work! Just one minor issue:

In Japanese, when the date format is yy/mm/dd or yyyy/mm/dd, there is no space between date and time. Check this screenshot. Also applies to the snapshot date.

Hi @renanvalentin and @lucas-barros , On build 19568, I could still reproduce the issue that @gabriela-ponce found. Here is the screenshot

seems like min padding before button is lost -> it should be 20px

button text is too big, it should be:
size - 14px
line - 20px
top/bot paddings - 8px

to much space at the bottom

links should be sticked to the bottom (as they were before)

@renanvalentin @lucas-barros please make sure to only use lowercase letters in branch names. Thanks!

links should be sticked to the bottom (as they were before)
upd: "we always use flex to push to the bottom of the available area rather than making it sticky" (c) Michael

@alexander-rukin The PR was updated with the fixes.

secondary button missing hover/press/etc states

checkmark is moved to be bottom (left one is from dialog, right one is from voting screen)

I thought you would use local override for checkboxes in the voting screen... Because now other checkboxes are affected.
We can keep it as it is, if you link a ticket here to fix checkboxes 😅

this is 33px distance between checkboxes instead of 11px 😢

compare with design

this button should have top/bot paddings 8px (not 8.5px)

@daniloprates @lucas-barros @renanvalentin please add screenshots for the initial screen during different phases (e.g. the date based text copy). Thanks!

@lucas-barros @renanvalentin @daniloprates last thing we need to do before merging this one is to hide the "Voting registration" from the sidebar menu for all builds except Mainnet and Flight.
cc @input-output-hk/daedalus

@lucas-barros @renanvalentin @daniloprates last thing we need to do before merging this one is to hide the "Voting registration" from the sidebar menu for all builds except Mainnet and Flight. cc @input-output-hk/daedalus

I've tested this and I believe it is already current behaviour.
https://github.com/input-output-hk/daedalus/blob/8b2d51ff030276a79d0910719e805db8ec0100b3/source/renderer/app/stores/SidebarStore.js#L85

@lucas-barros @renanvalentin @daniloprates last thing we need to do before merging this one is to hide the "Voting registration" from the sidebar menu for all builds except Mainnet and Flight. cc @input-output-hk/daedalus

I've tested this and I believe it is already current behaviour.
https://github.com/input-output-hk/daedalus/blob/8b2d51ff030276a79d0910719e805db8ec0100b3/source/renderer/app/stores/SidebarStore.js#L85

Thanks for making sure! 💯


Video Support

This is the best open source library for an image carousel I've seen. Nice work! It doesn't however have support for videos. I created a fork which adds support for videos.
https://github.com/pm-dev/MediaSlideshow
Wanted to let you know in case you were interested in bringing it into this repo. It took a little bit of refactoring to the 'Core' repo (including renaming "ImageSlideshow" to "MediaSlideshow", then I added an "AV" sub-library to add AVFoundation support. It's not super customizable at the moment because I built it for my use case but works nicely.

Hey pm-dev,
I was using ImageSlideshow, and I'm implementing videos into my app now, so I've decided to give your MediaSlideshow fork a go in my project. I've spent the last few hours trying to get it to work, but the documentation appears out of date, and the example project uses slideshow.setMediaSource, which is private in the current version, doesn't appear to work if I set it to public. I might be doing something simple wrong, but I get the following error when I attempt to construct a 'ImageAndVideoSlideshowDataSource' from an AVSource:
let videoSource = AVSource(
                url: URL(string: "https://my-movie-url.mp4")!,
                autoplay: true)

let dataSource = ImageAndVideoSlideshowDataSource(sources: [videoSource])

Error:
Cannot convert value of type 'AVSource' to expected element type 'Array<ImageAndVideoSlideshowDataSource.Source>.ArrayLiteralElement' (aka 'ImageAndVideoSlideshowDataSource.Source')
I've included MediaSlideshow and MediaSlideshow/AV in my Podfile, and have imported MediaSlideshow to my swift file. Creating a dataSource with ImageMediaSlideshowDataSource works fine with images, but I need to get video content in there too (using ImageAndVideoSlideshowDataSource). I've tried all types of casting and coercion, all unsuccessfully.  Any help would be hugely appreciated for anyone who uses MediaSlideshow!
Many thanks,
-Tom

@primeviltom glad you found the fix. ImageAndVideoSlideshowDataSource.Source is an enum that needs to wrap the video or image source:
    public enum Source {
        case image(ImageSource)
        case av(AVSource)
    }

@pm-dev does your fork library still being maintained?
I add pod 'MediaSlideshow', '~> 2.1.1' to my podfile but it cocoapod could not find compatible version for it.

I'm using mediaslideshow and ı prefer to create a mixed slideshow contains videos and images. So ı tried this one but ı got this error message. how could i use it for a video array + image array?
`var kingFisherSources : [KingfisherSource] = []
var videoSource : [AVSource] = []
lazy var dataSource: ImageAndVideoSlideshowDataSource = {
    let avSources = videoSource.map { ImageAndVideoSlideshowDataSource.Source.av($0) }
    let imageSources = kingFisherSources.map { ImageAndVideoSlideshowDataSource.Source.image($0) }

    return ImageAndVideoSlideshowDataSource(sources: avSources + imageSources, onAVAppear: .paused)
}()

for mediaItem in mediaArray {
if  let mediaUrl = mediaItem["url"] as? String {
print("denemeUrl : (mediaUrl)")
let mediaType = mediaItem["mediaType"] as? String
if mediaType == "image" {
let imageKSource = KingfisherSource(urlString: mediaUrl)
self.kingFisherSources.append(imageKSource!)
} else {
let avSource = AVSource(url: URL(string: mediaUrl)!)
self.videoSource.append(avSource)
`


[vcpkg metrics] Users should be able to disable metrics after build

Users should be able to avoid metrics by setting the environment variable VCPKG_DISABLE_METRICS, or by passing the -disable-metrics flag to vcpkg.
Additionally, as a minor update, we should rewrite the metrics library to use the JSON library which is now built in, as opposed to using string interpolation

YEs please for the environment variable. Everytime I re-bootstrap vcpkg I forget to set the flag (or what it is spelled exactly) so I then immediately re-re-boostrap vcpkg with the right setting.
Btw.: I'd be much more willing to upload metrics if you'd share the aggregated statistics with the community.

Closed as completed in #11542 :)


Random incompleted measurements in loop mode

Hello after long time :) Its quarantine time and I finally found some time to come back to this :)
So I tried to make again server like last time. now everything works as last time and I tried to measure LTE in my SIM card. So I ran loop test every 30 minutes and 0 meters GPS range ( since I am nonstop in my flat).
Weird thing is that again like last time I posted in issue, there are some random not finnished tests, I thought it was because of my last setup, but now I dont have VPN like last time so I guess it wasnt that.
I will attach CSV generated from my database(as .txt because github doesnt support csv).
Any idea why there are random not finnished tests?
database.txt

Hi,
sometimes it's battery "optimizations" by smartphone manufacturers causing these problems. Did you turn these off for the app?
Otherwise that's a very strange behaviour. Did you notice when the tests failed (during start? during the test? during submission?)

Hi,
sometimes it's battery "optimizations" by smartphone manufacturers causing these problems. Did you turn these off for the app?

Well I did not turned it off, I will try that but just in mind the phone is constantly plugged in to PC via cable ( so basically it is charging) and I think the optimizations are off when charging, but I will check it :)

Otherwise that's a very strange behavior. Did you notice when the tests failed (during start? during the test? during submission?)

Well I haven't seen it yet because it is random and I wasn't watching at the time of failed measuring. Mmm maybe I will try to make as much tests per hour as possible and I will watch it closely if this error will appear and I will let you know. Since now I have now unlimited DATA I can do this without paying for it :)
I only saw on phone when there was written:  Previous test: error afterwards I checked database and saw that there was failed test. I waited and watch another test, if it also fails, but next test was successful. So far it make no sense because it looks like its very random.

Update: So I watched when it happens.
The test starts. Ping, download and upload are measerud succesfully but then it procceeds to QoS and (status bar in 75%) there is nothing happening, no small round circle indicating measuring QoS.
I recorded it and you can see the behaviour in this video. Especialy its weird in the end like 2s before end, when there appear positive tick at QoS. But it will write test error.
https://youtu.be/A6Y_-uIx7qM

OK so one more update and possible casue of problem.
I have genrealy low 4G signal in my home, one or two bars(out of 5 in phone) in more technical speach the RSRQ is around -17dB sometimes -19dB which is on the line to disconnection.
It looks like when this wrong measurement happens( the circle of QoS is not moving) my connection to 4G drops and phone is not connected for 20 or so seconds to LTE and wont send results to server resulting in error.

Hi,
thank you for debugging! That is a weird behaviour that should not happen... Seems as if the qos-test crashes and does not recover.
Do you see the same behaviour also in the new open-rmbt-android app? We're planning on switching to the new app in the coming weeks, focusing our testing there.


[cxx-interop] Fix class template instantiation.

Lazily instantiate class template members. This means we no longer reject some programs that clang accepts, such as the following:
template<class T> struct Foo {
  void fail(T value) { value.fail(); }
};
using Bar = Foo<int>;

The above program will not error so long as Bar::fail isn't called. (Previously, we'd fail to import Bar.)

This is an issue I was running into mainly around importing the standard library.
@hlopko no need to review this/reply. I just figured you might be interested because you worked on class template stuff.

This is an issue I was running into mainly around importing the standard library.
@hlopko no need to review this/reply. I just figured you might be interested because you worked on class template stuff.

Oh sneaky idea! Very cool :)

@swift-ci please smoke test.

@swift-ci please smoke test.

@swift-ci please smoke test.

Unless I hear an objection, I'm going to land this shortly.


Weights for yolov3-tiny and yolov3-tiny-prn aren't available on 'desktop' install

Hello!
If you try to change from yolov4 to any other mode, you get the next error:
Loading weights from yolov3-tiny.weights...Couldn't open file: yolov3-tiny.weights
Is there any way I can fix this?

Yes, they aren't included in the docker image.. I only included yolov4 for desktop : https://github.com/opendatacam/opendatacam/blob/master/docker/build/desktop/Dockerfile#L20
I need either to:

reflect this in the documentation
include them. which would cause a larger docker image..

I'm gonna document also how to use custom weights with the docker install of OpenDataCam... which would be a solution... you need to :

download the weights file and put it in the same folder as the docker-compose.yml
modify the docker-compose.yml to mount the weights at run time like this: (see the volumes part)

version: "2.3"
services:
  opendatacam:
    restart: always
    runtime: nvidia
    image: opendatacam/opendatacam:v3.0.0-beta.3-desktop
    privileged: true
    volumes:
      - './config.json:/var/local/opendatacam/config.json'
      - './yolov3-tiny.weights:/var/local/darknet/yolov3-tiny.weights'
    ports:
      - "8080:8080"
      - "8070:8070"
      - "8090:8090"
  mongo:
    image: mongo
    restart: always
    ports:
      - "27017:27017"
    volumes:
      - mongodb_data_container:/data/db
volumes:
  mongodb_data_container:

Documented now, and you have documentation on how to use other weights: https://github.com/opendatacam/opendatacam/blob/development/documentation/CONFIG.md#use-custom-neural-network-weights

Excellent, thank you!


snet: Ipv6 support

snet needs to support IPv6.

After @matzf's contributions, this is probably in.
We'll need enhance our end to end test to include IPv6 ASes to confirm that it works, and to protect against regressions.

As a first test for this, we should be checking that pure IPv4 ASes can interact with pure IPv6 ASes in the standard end to end test. The end to end test currently has 16 ASes; we should make 8 of them IPv6. They should be as spread out as possible throughout the network.

Now with #3593 we have a test that tests IPv6 ASes in CI. So we can be fairly confident that this works as it should.


Build web apps with expressjs solutions provided

Issue Description
The setup script below clones https://github.com/reddock/expressworks which provides the solutions to all of the problems. Was this the intended behavior? Should this be a different repo without the solutions?
As detailed here: https://www.freecodecamp.com/challenges/build-web-apps-with-expressjs
git clone https://github.com/FreeCodeCamp/fcc-expressworks.git && chmod 744 fcc-expressworks/setup.sh && fcc-expressworks/setup.sh && source ~/.profile

Screenshot

This is expected. These tutorials are purely for student benefit, so we're operating on the assumption that if someone wants to spend the time on them they won't just look at the answers. Thanks and happy coding!


3.4rc3 - Node selector on logs screen is always blank

Checklist

[x] Double-checked my configuration.
[x] Tested using the latest version.
[x] Used the Emissary executor.

Summary

With log archiving enabled, run a workflow.
When complete, choose a node, and click to view the logs.
As per the screenshot above, the node selector is always blank, even after clicking something.

This also happens for archived workflows.
This was not the case in 3.3.9
What version are you running? 3.4 - rc3

Message from the maintainers:
Impacted by this regression? Give it a 👍. We prioritise the issues with the most 👍.

Can you try rc2? If rc2 doesn't have this issue, then it might come from this change: https://github.com/argoproj/argo-workflows/pull/9464
If rc2 also has this problem, another change we can look into is this:  https://github.com/argoproj/argo-workflows/pull/8655

I was able to reproduce it, and it does seem like it was a side effect of my fix in rc3. Let me see about fixing it.

Oh, I see. There was a change in my PR that on its face looked like it was just the linter changing the formatting so I ignored it, but it looks like a real code change was accidentally made in there when I was playing around with things. If I set that line back to how it was, it works. I'll submit a PR.

This is confirmed resolved in rc4


example-concept-template page in concepts section index

This is a Bug Report
The example-concept-template page is showing up in the concepts section index.
Problem:
https://kubernetes.io/docs/concepts/
https://kubernetes.io/docs/concepts/example-concept-template/
Proposed Solution:
Investigate whether this page should be removed or if there is way to prevent (change page metadata) the page
from publishing. Looks like this page has a parameter called toc_hide.
Page to Update:
https://kubernetes.io/docs/concepts/example-concept-template/

Task template page too:
https://deploy-preview-22043--kubernetes-io-master-staging.netlify.app/docs/tasks/

/kind bug
Related to https://github.com/kubernetes/website/pull/20874

My gut feeling: replace these example pages with Hugo archetypes, and document using those.

/assign

/close


System.Drawing.Common.TestData version to 1.0.3.

@mellinoe,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


security_configuration.json generation is incorrect

When using the ST_NUM_SIGNATURES config option in st.config an incorrect security_configuration.json file is produced.
The generated json contains "minimal_signatures_match" instead of the correct "min_valid_sigs_required".
The following patch resolves the issue:
diff --git a/scripts/security_config.sh b/scripts/security_config.sh
index 45bfdddaaf2d..cb93efb197b7 100755
--- a/scripts/security_config.sh
+++ b/scripts/security_config.sh
@@ -44,7 +44,7 @@ use_ospkg_cache=${ST_USE_PKG_CACHE}
 cat >"${output}" <<EOL
 {
   "version":${version},
-  "minimal_signatures_match": ${num_signatures},
+  "min_valid_sigs_required": ${num_signatures},
   "boot_mode": "${boot_mode}",
   "use_ospkg_cache": ${use_ospkg_cache}
 }

Note that the README.md needs to be updated in the example security_configuration.json.

Hi @bjoto,
you're right. Looks like this config was renamed in https://github.com/system-transparency/stboot/commit/7514d930cf23cd4a3eabe81d30285aa560ab0b81 without adapting it here.
Moving to stricter parsing sound good to me :+1:

I've submitted a PR that resolves this issue: https://github.com/system-transparency/system-transparency/pull/137


Issue 32

Close issue #32.  Need for conditional compilation in uint128.hpp removed.

Resolved by ce0c3da.


Expose function to validate options

I wish module interface of luacheck has function to validate config options.
Without it I have to implement code like this:
local function validateCfg(options)
  local res,msg = pcall(luacheck.check_strings,{},options)
  if not res then
    msg = msg:match"#2 to 'luacheck.check_strings' %((.+)%)" or msg
    return nil,msg
  end
  return res
end

I'd like to avoid exposing validation functions because the planned new Lua interface that will support some CLI features like multithreading and config loading will have several methods with different sets of validated options (e.g. config option will be passed to some initial setup method but not to checking methods). Also, fully processing config option requires I/O operations so it's good to do it only once.
Would it work for your use case if instead of throwing a string, validation errors were instead returned as an object after nil? E.g. it could return nil, {type = "validation", option = "ignore", msg = "array of string expected, got string"} in some case. The error object would have __tostring method turning it into a single string again. Functions would still throw on type errors, like passing a number instead of option table. What do you think?

I'd like to avoid exposing validation functions because the planned new Lua interface

I suppose that cant harm anything as long as that function stay undocumented.

Also, fully processing config option requires I/O operations so it's good to do it only once.

Do you mean reading config file? In our environment (FAR manager) we cant use luacheck loading functions (including config.load_config), so in any case I have to reimplement config reading in my code..
And I definitely prefer separate validate function, e.g. for such tasks as validate after config editing.

What do you think?

Error object will be good, if you have planned it anyway.
As for my use case I can continue using pcall, that's not a problem.

The plan is to have something like this:
-- Here options include config: path to file or a table. If config is invalid, nil + error object is returned.
local checker = luacheck.new(options)
local report = checker:check(inputs)
-- Now can process report as a table or do something like `print(checker:format(report))`.

This way config validation is a step of creating the checker object. You could recreate the checker every time config is edited, thus validating it, and then use the object when something needs to be checked.

In our environment (FAR manager) we cant use luacheck loading functions (including config.load_config), so in any case I have to reimplement config reading in my code..

Why can't it be used, because some of I/O is forbidden or something more specific about how it is implemented?

You could recreate the checker every time config is edited

Yes, that will definitely work in my case, thanks.

Why can't it be used, because some of I/O is forbidden or something more specific about how it is implemented?

We have unicode-aware environment, e.g. function loadfile expects filename in utf8, etc.

See #107


Added $showSearchForm to ModelAdmin

Re-raise of #6237 to be merged into 3.5.0

Sorry - we can't change the return type of SearchForm in the 3 line :(


feat(cli): generate plugin specific schema for dynamic plugins

We need to generate a config schema for each dynamic plugin since they do not end up in the regular node_modules dependencies, therefore it's not crawled and discovered by the Backstage schema collect mechanism. This leads to visibility issues (frontend is unable to fetch values, backend can expose secrets in logs).
Config schema can also be stored in transitive dependencies, not within the plugin itself, so we need to collect schemas in similar way as Backstage does.
However, Backstage schema collection mechanism crawls all dependencies - which essentially gets all the way back to Bascktage core - that essentially means, each plugin specific schema would be a full Backstage instance schema. Therefore I had to do a heuristic filtering out the most common schema packages to hopefully reach plugin specific additions only and a reasonable schema size.
Schema is stored in dist-scalprum/configSchema.json and dist-dynamic/dist/configSchema.json.

@tumido
Approved, though maybe it would be great to just upgrade the dynamic-frontend-plugin @janus-idp/cli version to avoid the CI build error ?


Assign the AP/Trim Disconnect button to a physical button on your yoke

Not sure if/what is possible via a mod like this one but one thing that annoys me is how it's not possible to extinguish the AP Disconnect warning light on the FMA without pressing the AP/Trim Disconnect button on the yoke in the virtual cockpit. I would like being able to map that to a physical button on my own yoke.
I've already tried all AP Disconnect/OFF etc commands I could find in MSFS but they just disconnects the AP but leaves the red, visual warning blinking on the FMA on the PFD.
However as I started this post, I guess this is hard to fix in a mod but is rather something that needs to be fixed within MSFS itself, to add another command that has the same effect as pressing the AP/Trim Disconnect button on the virtual yoke.

This is simulator problem. I cant create command to use in Simulator

That's what I thought.
Thanks anyway!


openldap: Fix test

Fixing OpenLDAP test
The timings were just unfortunate, systemctl status returns 3, not 0, during service startup.

Success on aarch64-linux (full log)
Partial log (click to expand)
/nix/store/rlfjk9wlisxif6n9gp1k3x2yxhsil2ax-openldap-2.4.45

Success on x86_64-linux (full log)
Partial log (click to expand)
/nix/store/pgxzpf9y0qijgdya377ws4wq2wc81v51-openldap-2.4.45

Success on x86_64-darwin (full log)
Partial log (click to expand)
/nix/store/4dlszsb8f0l6zz338dd41r0l3gk2h6iv-openldap-2.4.45


Added Alcubierre Warp Metric & related docs

Fixes #532.

@shreyasbapat

Ah.

Hello @JeS24! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/einsteinpy/geodesic/geodesic.py:

Line 130:107: W291 trailing whitespace
Line 131:109: W291 trailing whitespace
Line 132:121: E501 line too long (127 > 120 characters)
Line 133:121: E501 line too long (122 > 120 characters)

In the file src/einsteinpy/geodesic/utils.py:

Line 41:9: W503 line break before binary operator
Line 42:9: W503 line break before binary operator
Line 43:9: W503 line break before binary operator
Line 45:13: W503 line break before binary operator
Line 46:13: W503 line break before binary operator
Line 47:13: W503 line break before binary operator
Line 49:17: W503 line break before binary operator
Line 50:17: W503 line break before binary operator
Line 53:9: W503 line break before binary operator
Line 54:9: W503 line break before binary operator
Line 55:9: W503 line break before binary operator
Line 57:13: W503 line break before binary operator
Line 58:13: W503 line break before binary operator
Line 60:17: W503 line break before binary operator
Line 63:9: W503 line break before binary operator
Line 64:9: W503 line break before binary operator
Line 66:13: W503 line break before binary operator
Line 70:9: W503 line break before binary operator
Line 149:9: W503 line break before binary operator
Line 150:9: W503 line break before binary operator
Line 151:9: W503 line break before binary operator

In the file src/einsteinpy/plotting/geodesic/static.py:

Line 40:75: W291 trailing whitespace
Line 264:47: W605 invalid escape sequence '\l'

In the file src/einsteinpy/symbolic/predefined/alcubierre_warp.py:

Line 13:121: E501 line too long (150 > 120 characters)

In the file src/einsteinpy/symbolic/tensor.py:

Line 309:121: E501 line too long (122 > 120 characters)

In the file tests/test_examples.py:

Line 7:1: E302 expected 2 blank lines, found 1
Line 10:11: E201 whitespace after '['
Line 10:27: E241 multiple spaces after ','
Line 10:44: E241 multiple spaces after ','
Line 10:77: E241 multiple spaces after ','
Line 10:94: E241 multiple spaces after ','
Line 11:9: E128 continuation line under-indented for visual indent
Line 11:10: E201 whitespace after '['
Line 11:43: E241 multiple spaces after ','
Line 11:93: E241 multiple spaces after ','
Line 12:9: E128 continuation line under-indented for visual indent
Line 12:10: E201 whitespace after '['
Line 12:43: E241 multiple spaces after ','
Line 12:93: E241 multiple spaces after ','
Line 13:9: E128 continuation line under-indented for visual indent
Line 13:43: E241 multiple spaces after ','
Line 13:94: E241 multiple spaces after ','
Line 14:9: E128 continuation line under-indented for visual indent
Line 14:43: E241 multiple spaces after ','
Line 14:94: E241 multiple spaces after ','
Line 15:9: E128 continuation line under-indented for visual indent
Line 15:43: E241 multiple spaces after ','
Line 15:94: E241 multiple spaces after ','
Line 20:1: E302 expected 2 blank lines, found 1

In the file tests/test_geodesic/test_mock_julia.py:

Line 14:11: E201 whitespace after '['
Line 14:27: E241 multiple spaces after ','
Line 14:44: E241 multiple spaces after ','
Line 14:77: E241 multiple spaces after ','
Line 14:94: E241 multiple spaces after ','
Line 15:9: E128 continuation line under-indented for visual indent
Line 15:10: E201 whitespace after '['
Line 15:43: E241 multiple spaces after ','
Line 15:93: E241 multiple spaces after ','
Line 16:9: E128 continuation line under-indented for visual indent
Line 16:10: E201 whitespace after '['
Line 16:43: E241 multiple spaces after ','
Line 16:93: E241 multiple spaces after ','
Line 17:9: E128 continuation line under-indented for visual indent
Line 17:43: E241 multiple spaces after ','
Line 17:94: E241 multiple spaces after ','
Line 18:9: E128 continuation line under-indented for visual indent
Line 18:43: E241 multiple spaces after ','
Line 18:94: E241 multiple spaces after ','
Line 19:9: E128 continuation line under-indented for visual indent
Line 19:43: E241 multiple spaces after ','
Line 19:94: E241 multiple spaces after ','
Line 24:1: E302 expected 2 blank lines, found 1

In the file tests/test_metric/test_kerr.py:

Line 82:25: E241 multiple spaces after ','
Line 82:42: E241 multiple spaces after ','
Line 82:59: E241 multiple spaces after ','
Line 82:93: E241 multiple spaces after ','
Line 82:121: E501 line too long (143 > 120 characters)

In the file tests/test_metric/test_kerrnewman.py:

Line 97:25: E241 multiple spaces after ','
Line 97:42: E241 multiple spaces after ','
Line 97:59: E241 multiple spaces after ','
Line 97:93: E241 multiple spaces after ','
Line 97:121: E501 line too long (143 > 120 characters)

In the file tests/test_metric/test_schwarzschild.py:

Line 21:10: E201 whitespace after '['
Line 21:26: E241 multiple spaces after ','
Line 21:43: E241 multiple spaces after ','
Line 21:60: E241 multiple spaces after ','
Line 22:9: E128 continuation line under-indented for visual indent
Line 22:25: E241 multiple spaces after ','
Line 32:54: W292 no newline at end of file

In the file tests/test_plotting/test_geodesic/test_interactive.py:

Line 93:33: E712 comparison to False should be 'if cond is False:' or 'if not cond:'

In the file tests/test_plotting/test_geodesic/test_static.py:

Line 37:1: E302 expected 2 blank lines, found 1
Line 87:33: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 153:1: E302 expected 2 blank lines, found 1

PEP issues are all fixed for this PR (except W503). Will make the final commit, after #527 is merged.


Can i achieve that effect

No, it's not meant for this kind of effect.
You'll probably be better off with one of these plugins:

https://github.com/lhandel/react-native-card-flip
https://github.com/moschan/react-native-flip-card

@bd-arc Sorry I want to achieve the effect of the lower left corner, it is a swipe effect

The plugin will allow you to do that, but you could also just use a regular ScrollView with a snapToOffsets prop.

this is my code now
<Carousel
    ref={c => {
      this._carousel = c;
    }}
    data={x.photo}
    renderItem={this._renderItem.bind(
      this
    )}
    sliderWidth={90}
    hasParallaxImages={true}
    useScrollView={true}
    snapToOffsets={2}
    activeSlideOffset={2}
    enableMomentum={true}
    containerCustomStyle={{
      marginTop: 5,width:90
    }}
    itemWidth={30}
  />

when I add useScrollView and snapToOffsets , This error has occurred:

Error while updating property 'snapToOffsets' of a view managed by: AndroidHorizontalScrollView Value for snapToOffsets cannot be cast from Double to ReadableArray

@bd-arc I want to let the active at the left of the view when it is the first. It is center now.

You're not supposed to use snapToOffsets with the carrousel. It will only mess things up.
Also make sure to read the doc, particularly regarding prop activeSlideAlignment.

You're not supposed to use snapToOffsets with the carrousel. It will only mess things up.
Also make sure to read the doc, particularly regarding prop activeSlideAlignment.
I had tried activeSlideAlignment, It can't achieve like the gif. I also make the active center except the first and the last


C++ compilation of rule ‘//tensorflow_serving/model_servers:http_rest_api_handler_test’ failed (Exit 1) tensorflow_serving/model_servers/http_rest_api_handler_test.cc:380:36: error: unterminated raw string

Hi,
I’m having a problem during Tensorflow Model Server compilation, seems i have a problem with my gcc version (4.5.8) and the TF version, i’m getting this error:
C++ compilation of rule ‘//tensorflow_serving/model_servers:http_rest_api_handler_test’ failed (Exit 1) tensorflow_serving/model_servers/http_rest_api_handler_test.cc:380:36: error: unterminated raw string
I have a conflict between my gcc version  but i’ve tried to update it but seems for my SUSE 12 SP2 is the highest version possible, also my bazel version is 0.21.0 because the 0.11.0 was giving me errors during TFMS compilation, these are tickets that i’ve checked related with the issue:
https://github.com/tensorflow/serving/issues/905
https://github.com/tensorflow/serving/issues/1001
Let me know if you need more details.
Thanks a lot.
Best Regards.

Hi,
I'm checking now the all installation tutorial steps to make sure I'm not missing something.
Can you confirm that you are using gcc version 4.5.8? This is a rather very old version which is pulled when you install SLES 12SP3. On my side with SP3, I got:
hxeadm@hxehost:/usr/sap/HXE/HDB90>gcc --version
gcc (SUSE Linux) 4.8.5
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I also realized that the documentation mentions that only TF 1.5 is supported, but the git clone command I reference will pull the latest release (1.12) which is probably why it requires bazel 0.21.0.
I'll check that as well.

Hi,
Sorry you're right i mistype the gcc version, the version i'm using is the same as you, maybe i should skip the unit testing files during compilation to avoid that error but seems is a bad idea( and i don't know how to do it from the bazel build command ) or also i should try to compile an older TF version, in any case i'll wait until your recommendation to solve/avoid the issue.
Thanks a lot for your time.
Best Regards.


AGENT-34: Set BOOTSTRAP_HOST_MAC in assisted-service environment

Setting the BOOTSTRAP_HOST_MAC environment variable notifies
assisted-service of a MAC address of Node Zero so that it will be set
as the bootstrap host.
We choose the MAC address of interface that the service IP is on, as
that is the most likely to be unique.
To pass the environment variable to assisted-service, we turn the node0
file used to trigger starting the service into an environment file.
/hold
Depends on openshift/assisted-service#3627

/hold cancel
This won't break anything, and the dependent PR appears on track to be accepted, so no need to keep holding.

I tested it with assisted-service PR.
/lgtm


Fixed issue #7

the issue of Sign-in form displays raw span html in input files. Added the words login and password to the en.yml file which is used for translation, and changed the placeholder text to match that

Well done! 👍
Fixes #7  <--- see what I did there?
Unfortunately the use of a symbol t(:login) is inconsistent with other forms in the codebase t('.login').


Add ruby version

I use asdf for both node and ruby, so I like .tool-versions but I'm guessing not everyone is.
We can either all move to asdf, which I don't expect everyone to do, or add the .ruby-version and the equal for node.

I think many will be already using .ruby-version and it should be easy to go with that for now.

@sanchez2210 Do you want to add it?

Sure.

@emerald-rubies/emeralds we'll be using -v 2.4.1 is that good for you?

Yep, 2.4.1 is the version we will be using. If anybody needs help setting up a version manager, I can help you out.


Feature/chairs meeting cleanup

This PR addresses some urgent things for chairs who will be using the app in Fall 2022:

#251 -- reduced number of input fields, reorganize a bit to use space better, also relabel a couple fields (and hack a solution to a problem this introduced)
#250 -- number of output fields has been reduced. Ordering has not been addressed yet (should be easy).

I'd love to have this approved prior to the chairs meeting tomorrow so that I can demo things with the revised interface and so people who give it a try have something that matches.  Is it possible to get to this today?

For urgent PR's, it might be helpful to @ the students or @kvlinden! I don't know enough about the context anymore to feel comfortable approving.

Thanks for taking a look.


Inspector component skeleton

This card should address:

component styling

Top level path in the component to show the tree path of the component visualised in the inspector

Depending on the type of the instance shown by the inspector, we will have to show different components, such as

Input text to change the name of the instance
read only input text for structures (neurons, synapses and contacts).
color picker to change color and transparency
button to hide/show the structure
download button (functionalities can differ depending on the type of instance shown, for structures we download the objs, for viewers we download svg/png images).
Text section to show whatever metadata the instance has available.
for neurons, we list the connections relevant to the neuron shown in the inspector.
for the viewers (morphology or cphate) we show the developmental stage slider
Only for the morphology viewers the strata section with buttons to add the worm body, pharynx and/or the nerve ring.
List of neurons when a cluster of the cphate is selected.

@ddelpiano  the developmental stage slider is here read-only, right?


GH Pages

Have you considered hosting this on Github pages? This looks like something that could really benefit from that. Should be fairly simple to have a script that consumes the json & creates a web page (possibly in react) with a clean searchable interface.
https://pages.github.com/

We already use Github Pages, right here:
https://dkhamsing.github.io/open-source-ios-apps/
The website is not under active development because I'm too busy lately, but it should still be functional. For more details see here:
https://github.com/dkhamsing/open-source-ios-apps/issues/400

Sick!


On pull request #400: >File>Close does not function in some windows

On #400
>File>Close does not function in some windows (midi monitor, midi calculator, log viewer) but causes no crashes. These windows are closing properly using the x-button on the right top.

I don't have any clue how tihs should be related to pull request #400 can someone confirm that this is working in any build?

can someone confirm that this is working in any build?

In  is NOT working in linux Version = 5.3.201, Build date = Tue Mar 29 13:56:34 CEST 2016, Branch = Nightly, Juce = 4.0.2, libusb = 1.0.19, liblo = 0.28,
Therefore it is not related to #400 . I've edited this issue accordingly.


Use proxy => Set proxy on electron or puppeteer?

I want to use proxy but I can't setting it.

did you tried commandline in electron.


error return :SHOW FULL TABLES FROM sharding_db LIKE 't_mail'

apache-shardingsphere-incubating-4.0.0-RC3-sharding-proxy-bin.tar.gz
query sql:SHOW FULL TABLES FROM sharding_db LIKE 't_mail'
return no record.
but mysql return 1 record.

but it work fine in sharding-jdbc 4.0.0-RC2

duplicate with #2904


Error while opening a .py file. Please read details

I have not seen this issue anywhere online.
I have followed the instructions carefully in the docs for the installation (dependencies + nvim + config / Packer plugins).
nvim --version:

Build type: Release
LuaJIT 2.1.0-beta3
Compiled by<EMAIL_ADDRESS>

Terminal: iTerm2 - Build 3.4.15
Operating system/version: MacOS Monterey - Version 12.2.1
Output of command set runtimepath:

runtimepath=~/.config/nvim,/opt/homebrew/etc/xdg/nvim,/etc/xdg/nvim,~/.local/share/nvim/sit
e,~/.local/share/nvim/site/pack/packer/opt/nvim-hlslens,~/.local/share/nvim/site/pack/packer/
opt/hop.nvim,~/.local/share/nvim/site/pack/packer/opt/vim-commentary,~/.local/share/nvim/site
/pack/packer/opt/cmp-emoji,~/.local/share/nvim/site/pack/packer/opt/cmp-buffer,~/.local/share
/nvim/site/pack/packer/opt/fidget.nvim,~/.local/share/nvim/site/pack/packer/opt/nvim-lspconfi
g,~/.local/share/nvim/site/pack/packer/opt/cmp-nvim-lsp,~/.local/share/nvim/site/pack/packer/
opt/cmp-path,~/.local/share/nvim/site/pack/packer/opt/cmp-omni,~/.local/share/nvim/site/pack/
packer/opt/nvim-cmp,~/.local/share/nvim/site/pack/packer/opt/lspkind-nvim,~/.local/share/nvim
/site/pack/packer/opt/bufferline.nvim,~/.local/share/nvim/site/pack/packer/opt/unicode.vim,~/
.local/share/nvim/site/pack/packer/opt/targets.vim,~/.local/share/nvim/site/pack/packer/opt/l
ualine.nvim,~/.local/share/nvim/site/pack/packer/opt/vim-repeat,~/.local/share/nvim/site/pack
/packer/opt/open-browser.vim,~/.local/share/nvim/site/pack/packer/opt/nvim-web-devicons,~/.lo
cal/share/nvim/site/pack/packer/opt/whitespace.nvim,~/.local/share/nvim/site/pack/packer/opt/
which-key.nvim,~/.local/share/nvim/site/pack/packer/opt/vim-yoink,~/.local/share/nvim/site/pa
ck/packer/opt/vim-swap,~/.local/share/nvim/site/pack/packer/opt/indent-blankline.nvim,~/.loca
l/share/nvim/site/pack/packer/opt/vim-sandwich,~/.local/share/nvim/site/pack/packer/opt/vim-m
atchup,~/.local/share/nvim/site/pack/packer/opt/vim-indent-object,~/.local/share/nvim/site/pa
ck/packer/opt/vim-highlighturl,~/.local/share/nvim/site/pack/packer/opt/dashboard-nvim,~/.loc
al/share/nvim/site/pack/packer/opt/vim-fugitive,~/.local/share/nvim/site/pack/packer/opt/gitl
inker.nvim,~/.local/share/nvim/site/pack/packer/opt/nvim-treesitter,~/.local/share/nvim/site/
pack/packer/opt/nvim-notify,~/.local/share/nvim/site/pack/*/start/*,~/.local/share/nvim/site/
pack/packer/opt/nord.nvim,~/.local/share/nvim/site/pack/packer/opt/wilder.nvim,~/.local/share
/nvim/site/pack/packer/opt/committia.vim,~/.local/share/nvim/site/pack/packer/opt/firenvim,~/
.local/share/nvim/site/pack/packer/opt/packer.nvim,/opt/homebrew/share/nvim/site,/usr/local/s
hare/nvim/site,/usr/share/nvim/site,/opt/homebrew/Cellar/neovim/0.8.0/share/nvim/runtime,/opt
/homebrew/Cellar/neovim/0.8.0/lib/nvim,~/.local/share/nvim/site/pack/packer/opt/cmp-emoji/aft
er,~/.local/share/nvim/site/pack/packer/opt/cmp-buffer/after,~/.local/share/nvim/site/pack/pa
cker/opt/cmp-nvim-lsp/after,~/.local/share/nvim/site/pack/packer/opt/cmp-path/after,~/.local/
share/nvim/site/pack/packer/opt/cmp-omni/after,~/.local/share/nvim/site/pack/packer/opt/vim-s
andwich/after,~/.local/share/nvim/site/pack/packer/opt/vim-matchup/after,/usr/share/nvim/site
/after,/usr/local/share/nvim/site/after,/opt/homebrew/share/nvim/site/after,~/.local/share/nv
im/site/after,/etc/xdg/nvim/after,/opt/homebrew/etc/xdg/nvim/after,~/.config/nvim/after

Describe the bug

Upon opening a python file, I get this error (occasionally and not with all python files). Unfortunately there is no deterministic way of reproducing it as it does not happen with all the py files that I have.
If it helps, the python file is part of a Flask project.

Error detected while processing BufReadPost Autocommands for "*":
Error executing lua callback: ...brew/Cellar/neovim/0.8.0/share/nvim/runtime/filetype.lua:22:
 Error executing lua: ...brew/Cellar/neovim/0.8.0/share/nvim/runtime/filetype.lua:23: Vim(let
):E119: Not enough arguments for function: everforest#get_palette
stack traceback:
        [C]: in function 'nvim_cmd'
        ...brew/Cellar/neovim/0.8.0/share/nvim/runtime/filetype.lua:23: in function <...brew/
Cellar/neovim/0.8.0/share/nvim/runtime/filetype.lua:22>
        [C]: in function 'nvim_buf_call'
        ...brew/Cellar/neovim/0.8.0/share/nvim/runtime/filetype.lua:22: in function <...brew/
Cellar/neovim/0.8.0/share/nvim/runtime/filetype.lua:11>
stack traceback:
        [C]: in function 'nvim_buf_call'
        ...brew/Cellar/neovim/0.8.0/share/nvim/runtime/filetype.lua:22: in function <...brew/
Cellar/neovim/0.8.0/share/nvim/runtime/filetype.lua:11>

When I perform checkhealth normally (i.e, when I do not get the above error), it does not give any error and everything is checked with "OK".
Only when I get the above error, if I press return, it continues to vim. Upon performing checkhealth in that case, I get this error:

tion <SNR>1_LoadFTPlugin[17]..script /opt/homebrew/Cellar/neovim/0.8.0/share/nvim/runtime/ftp
lugin/checkhealth.vim[9]../opt/homebrew/Cellar/neovim/0.8.0/share/nvim/runtime/ftplugin/markd
own.vim[10]../Users/hussein/.local/share/nvim/site/pack/packer/opt/sonokai/after/ftplugin/htm
l/sonokai.vim:
line   10:
E119: Not enough arguments for function: sonokai#get_palette
line   13:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   14:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   15:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   16:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   17:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   18:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   19:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   20:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   21:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   22:
E121: Undefined variable: s:palette
E116: Invalid arguments for function sonokai#highlight
line   23:...

finally, it seems like an issue with color schemes particularly, but I am not sure, maybe with term colors.
I spent 2 days trying to search for a solution without any luck.
Lastly, the config is untouched. It is in sync with the latest branch of this nvim config.

Maybe there is some problem with your nvim installation, I have never met this problem before. Try to uninstall your nvim completely (brew uninstall neovim), and then reinstall nvim (brew install neovim).
I do not think this is an issue of this config, maybe something wrong with everforest.


simplify BindableProperty creation

What do you think about this?
To me, all the many bindable properties are the most confusing and intimidating part of trying to modify this library. This approach means less redundant boilerplate and less casting. With this approach, when creating the lambda delegates for the events, the oldValue and newValue will have the appropriate type already. Which also makes it clearer what is happening.
It would cause a slight imperceptible performance degradation in terms of instantiating the data grid. And while it simplifies the code elsewhere, it is new code to maintain. On net, it adds code.
This kind of thing would ideally be incorporated into MAUI itself, and I made a feature suggestion there.
This approach also mandates naming conventions for each BindableProperty, as per the first guard clause in the new extension method. Since otherwise we would need to have the redundant nameof() parameter every time.

The other approach, which could be even more performant and even less code would be to use a source generator.
But that would add a lot of "magic" and would be awkward and unfamiliar to many, and more difficult to debug. And might potentially add a dependency to this project.
https://github.com/CommunityToolkit/Maui/discussions/1094


Change targets for diagnostics libraries

After the change:

Common: netstandard2.0
AspNet: net461
AspNetCore: netstandard2.0

Everything is tested under net461 and (except for AspNet) netcoreapp2.1.
Fixes #2959.

(Will assign after it's green...)


quiche_config_set_max_idle_timeout() - unit?

In the quiche.h header file, most function calls that involve a timeout seems to specify a unit in the comment describing it. Not for this.
Is it nanoseconds?

It's milliseconds. See https://tools.ietf.org/html/draft-ietf-quic-transport-32#section-18.2

Thanks. Maybe add that in a comment? It's not super obvious that it uses the same unit as the underlying protocol.

Maybe also mention what/if quiche sets some value by default? I would presume I'm not the only user who can't recall those specific details from the spec... =)


[Xai Sentry] Update service

Service Documentation
https://xai-foundation.gitbook.io/xai-network/about-xai/sentry-nodes-explained
Checklist
Initialized using:
ansible-galaxy role init [NAME] --init-path=depin/services/roles

Dependencies
If an Ansible Role is needed because of a dependency ensure it's also initialized in depin.libs
ansible-galaxy role init [NAME] --init-path=depin/libs/roles

Commands
Ensure all of the listed commands are implemented for the New Service.

[ ] Update service

'galaxy.yml'

[ ] updated version by one minor step (1.0.0 => 1.1.0)

New Services should never create breaking changes but adds new features

[ ] dependencies are updated for required collections

Reset -> uninstall install actions will be used as "Service update".


racket-minimal: build on darwin

Technically, racket compiles and packages too, but it doesn't pass all
tests yet, so the build fails.
gcc7Stdenv is GCC 7 with the MacOS-specific adaptations retained.
Building on MacOS with that works, but we should be using clang.
I'm hoping that the next person wanting to override the compiler
version in some other derivation sees that attribute and doesn't
inadvertently break a MacOS build again.
Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[✓] macOS
[✓] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[✓] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[✓] Tested execution of all binary files (usually in ./result/bin/)
[✓] Fits CONTRIBUTING.md.

@GrahamcOfBorg build racket-minimal

Success on x86_64-darwin (full log)
Partial log (click to expand)
cp "../COPYING-libscheme.txt" "../COPYING_LESSER.txt" "../COPYING.txt" "/nix/store/20jh9mdzw4ngyg6h2205lfpwhcjwj0ca-racket-minimal-6.12/share/racket"/
make[2]: Leaving directory '/private/tmp/nix-build-racket-minimal-6.12.drv-0/racket-6.12/src/build'
make[1]: Leaving directory '/private/tmp/nix-build-racket-minimal-6.12.drv-0/racket-6.12/src/build'
post-installation fixup
gzipping man pages under /nix/store/20jh9mdzw4ngyg6h2205lfpwhcjwj0ca-racket-minimal-6.12/share/man/
strip is /nix/store/v8ifq0hapblpr2z0hx4wvwg02w4aczqy-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/20jh9mdzw4ngyg6h2205lfpwhcjwj0ca-racket-minimal-6.12/lib  /nix/store/20jh9mdzw4ngyg6h2205lfpwhcjwj0ca-racket-minimal-6.12/bin
patching script interpreter paths in /nix/store/20jh9mdzw4ngyg6h2205lfpwhcjwj0ca-racket-minimal-6.12
/nix/store/20jh9mdzw4ngyg6h2205lfpwhcjwj0ca-racket-minimal-6.12/bin/.raco-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/19cc89zq5n68ibr53izy4zgcr5qg2rza-bash-4.4-p12/bin/sh"
/nix/store/20jh9mdzw4ngyg6h2205lfpwhcjwj0ca-racket-minimal-6.12

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/7v26yfzgjys8130jqprvnhcdxr5dd6n9-racket-minimal-6.12/lib/racket/mzdyn3m.o
wrong ELF type
gzipping man pages under /nix/store/7v26yfzgjys8130jqprvnhcdxr5dd6n9-racket-minimal-6.12/share/man/
strip is /nix/store/adidfx4pa7vmvby0gjqqmiwg2x49yr27-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/7v26yfzgjys8130jqprvnhcdxr5dd6n9-racket-minimal-6.12/lib  /nix/store/7v26yfzgjys8130jqprvnhcdxr5dd6n9-racket-minimal-6.12/bin
patching script interpreter paths in /nix/store/7v26yfzgjys8130jqprvnhcdxr5dd6n9-racket-minimal-6.12
/nix/store/7v26yfzgjys8130jqprvnhcdxr5dd6n9-racket-minimal-6.12/bin/.raco-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/sh"
checking for references to /tmp/nix-build-racket-minimal-6.12.drv-0 in /nix/store/7v26yfzgjys8130jqprvnhcdxr5dd6n9-racket-minimal-6.12...
wrong ELF type
/nix/store/7v26yfzgjys8130jqprvnhcdxr5dd6n9-racket-minimal-6.12

Success on aarch64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/yh3i5irfkpc6w41gjhcv4n3qr7lp6c41-racket-minimal-6.12/lib/racket/starter
shrinking /nix/store/yh3i5irfkpc6w41gjhcv4n3qr7lp6c41-racket-minimal-6.12/bin/.racket-wrapped
gzipping man pages under /nix/store/yh3i5irfkpc6w41gjhcv4n3qr7lp6c41-racket-minimal-6.12/share/man/
strip is /nix/store/skd6ix5ipkyhxzq7naylj4digawakl4j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/yh3i5irfkpc6w41gjhcv4n3qr7lp6c41-racket-minimal-6.12/lib  /nix/store/yh3i5irfkpc6w41gjhcv4n3qr7lp6c41-racket-minimal-6.12/bin
patching script interpreter paths in /nix/store/yh3i5irfkpc6w41gjhcv4n3qr7lp6c41-racket-minimal-6.12
/nix/store/yh3i5irfkpc6w41gjhcv4n3qr7lp6c41-racket-minimal-6.12/bin/.raco-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/sh"
checking for references to /build in /nix/store/yh3i5irfkpc6w41gjhcv4n3qr7lp6c41-racket-minimal-6.12...
wrong ELF type
/nix/store/yh3i5irfkpc6w41gjhcv4n3qr7lp6c41-racket-minimal-6.12


Bump Istio to 1.19.3

Open tasks:

[x] Cherry pick changes to release-1.1 branch
[x] Adapt zero downtime test documentation to review remarks

Description
Bump Istio libs and components to version 1.19.3
ACs:

[x] istio running on 1.19.3 version
[x] sidecars are running on 1.19.3 version
[x] verify zero downtime during istio upgrade
[x] update grafana dashboards if needed
[x] new image available in Kyma external repository
[ ] istio released and bumped in kyma
[x] gardener cluster can be hibernated
[x] run smoke test (expose httpbin with sidecar)
[x] run manual tests

Reasons
Keeping Istio up to date
DoD:
- [ ] Create a follow-up issue.

[ ] Provide unit tests.
[ ] Provide integration tests.
[ ] Provide documentation.
[ ] Test on a production-like environment.
[ ] Check the outcome of all related pipelines.
[ ] Verify resource limits.
[ ] As a PR reviewer, verify code coverage and evaluate if it is acceptable.
[ ] Create a release and bump in Kyma.
[ ] Add release notes and What's New notes for Kyma customers.

Attachments
https://istio.io/latest/news/releases/1.19.x/announcing-1.19.3/

Zero downtime upgrade test is in separate issue: https://github.com/kyma-project/istio/issues/429


Getting error The request signature we calculated does not match the signature you provided. Check your key and signing method.

Describe the bug
While trying to use s3 client put object method, it is returning this error message. The error comes with .net framework only, .net core works fine.
The request signature we calculated does not match the signature you provided. Check your key and signing method.
Expected Behavior
It used to work fine with .net framework and was able to put an object without any errors
Current Behavior
Getting above error probably since daylight savings changes!?
Reproduction Steps
var amazonS3Client = new AmazonS3Client();
var s3PutRequest = new PutObjectRequest
{
BucketName = param.bucketName,
Key = param.key,
ContentBody = param.data
};
var s3PutResponse = await amazonS3Client.PutObjectAsync(s3PutRequest);
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.Core: <IP_ADDRESS>
AWSSDK.S3: <IP_ADDRESS> and <IP_ADDRESS> (Error started on <IP_ADDRESS>)
Targeted .NET Platform
.NET Framework 4.8
Operating System and version
Windows 11

Same problem is happening when I run it on .net core 6. It only works when the project type is lambda.

Got the problem:
AWS used to be lenient earlier with bucket name and key name, but now it's being validated strictly. We used to pass
bucketName = bucketName + path
key = fileName
This is being rejected by now. Need to pass bucketName as name only and add the path to the key


[crypto][performance] Verify aggregated sig and fallback to individual sig verification in NW

A validator should aggregate the signed votes on its header and verify first, and only if there is a problem fallback to verifying each signature independently. See Vote::verify().

Closed by https://github.com/MystenLabs/sui/pull/9682/files


Stopping machine results in error

Docker version 1.9.1, build a34a1d5
docker-machine version 0.5.5, build 02c4254
installed on a Mac using:  DockerToolbox-1.9.1g.pkg
Trying to stop a machine after it was created results in error:
❯❯❯ docker-machine ls
NAME       ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER   ERRORS
default    *        virtualbox   Running   tcp://<IP_ADDRESS>:2376           v1.9.1
registry   -        virtualbox   Running   tcp://<IP_ADDRESS>:2376           v1.9.1
❯❯❯ docker-machine stop registry
/usr/local/bin/VBoxManage showvminfo registry --machinereadable failed:
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component ConsoleWrap, interface IConsole, callee nsISupports
VBoxManage: error: Context: "COMGETTER(VRDEServerInfo)(vrdeServerInfo.asOutParam())" at line 2340 of file VBoxManageInfo.cpp

Fixed with https://github.com/docker/machine/pull/2763


ibpanic after install in Ubuntu 20.04

I installed the azhpc-images on

Ubuntu 20.04
Standard ND96amsr A100 v4 machine

with the latest commit (c8db6de).
However, when I run
$ ibstat

, it raises an error as
ibpanic: [769778] main: stat of IB device 'mlx5_an0' failed: No such file or directory

It seems the machine has mlx5_ib0 to mlx5_ib7, why it tries to find mlx5_an0?

mlx5_an0 is the Accelerated Networking (AN) interface (for front-end network), not IB, and ibstat does not support AN interface.
Please exclude the AN interface for ibstat, and run ibstat directly on the IB interfaces. (eg: ibstat mlx5_ib0).
Also, note that ibstatus works for AN interface also.


Remove webdriver

--- Caused by: ---
# Webdrivers::NetworkError:
#   Net::HTTPClientException: 404 "Not Found" with https://chromedriver.storage.googleapis.com/LATEST_RELEASE_115.0.5790
https://github.com/titusfortner/webdrivers/issues/247

The webdrivers readme seems to suggest that selenium 4.11+ is needed in order to replace webdrivers entirely https://github.com/titusfortner/webdrivers#update-future-of-this-project
Do you think it's worth doing so in this PR too? (I have an ulterior motive for asking that: doing so seems to have broken Selenium on BOPS 😬)

You have caught me being lazy 😄
Can I do this in the next PR ?
Wanted to get this merged so I can rebase the docker fixes


Add foreign columns to tables

Hello!
Great package you made! Thanks
This PR has two new migrations that add foreign columns to tables for Thread and Message models.
It also adds a unique constraint in participants table so that a User can only participate once per Thread.
Hope it helps.

The only thing I would think about is to add onDelete('cascade')
https://laravel.com/docs/5.6/migrations#foreign-key-constraints

I tend to never use onDelete('cascade') so that I am forced to deal with related data, and not delete anything by mistake, but is more a personal preference than anything.
You want me to add it to the PR?

@jmfederico I just want it to add it to the discussion.
I tend to use it but I'm also not using soft deletes in most cases.

This is in conflict with the idea in #297 - so I won't prevent this from being merged but want to keep this in mind.

First, thank you for the PR @jmfederico! This package initially had foreign keys but it seemed like a bunch of users were having issues re-running or refreshing migrations in certain instances, so we dropped it. So for that reason, I'm not going to include this in the core package at this time, but I'll certainly reference this PR when needed. If it makes sense to include this in the future I'll be sure to pull your code in. Thanks again!


Nodemon

Nodemon will auto restart your bot whenever you make and save changes to a js file. Let me know if you want me to implement this into the start up script.

#25


Fixed navbar

Add top-nav and fixup bootstrap usage.
This change does the following:

Adds a top nav
Adds named links for major sections
Fixes "Resources" section groups with explicit grid divs (this puts each
section on a row at the same level)
Gives the text in the jumbotron a little color
Gives the body links colors that match the new logo
Adds a faviron

Note that this change builds upon the new logo changes.

You are the best!


Revision not supported...

Driver downloaded:
gchdm_204_981.dmg
Firmware:
[root@strix gchd]# pwd
/usr/lib/firmware/gchd
[root@strix gchd]# ls
mb86h57_h58_enc_h.bin  mb86h57_h58_idle.bin
[root@strix build]# ./Project -r 1080
FIFO: /tmp/gchd.ts has been created.
Waiting for user to open it.
This revision of the Elgato Game Capture HD is currently not supported.
Is this just a driver issue? Where to donwload the driver with the correct device.
If not?, well, when do we setup a vpn so you can access the hardware? or any advice to support it is welcome

Hi there,
I assume you have the Elgato Game Capture HD (not HD60 / HD60 Pro / HD60 S)? Please check with the command lsusb, which PID your device has. If it's 0x005d, then I'm sorry. There is currently no support for that revision. We have an issue tracker in #12.
Cheers,
Tolga

Yes, I have it. :(
On Thu, Sep 8, 2016 at 6:55 PM, Tolga Cakir<EMAIL_ADDRESS>wrote:

Hi there,
I assume you have the Elgato Game Capture HD (not HD60 / HD60 Pro / HD60
S)? Please check with the command lsusb, which PID your device has. If
it's 0x005d, then I'm sorry. There is currently no support for that
revision. We have an issue tracker in #12
https://github.com/tolga9009/elgato-gchd/issues/12.
Cheers,
Tolga
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tolga9009/elgato-gchd/issues/26#issuecomment-245778594,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEXMGbKyDM2llOwmM4uOYlroGKhjbvVfks5qoKCJgaJpZM4J4kDH
.

Okay, I'm marking this as a duplicate of #12 then. We can discuss details there.


Fixed #31742 -- Fixed makemigrations crash on ForeignKey to an app with mixed case label.

ticket-31742

buildbot, test on oracle.

Test failure on Oracle is not related, see #13113.


V 1.5.0 Stable: Error executing task LinkAssemblies: error XA2006: Could not resolve reference to CustomTabs

Hello again!
I'm have the same problem as #167, wrote some comments there but thought that I should probably open a new one after doing some research. When I use stable version of 1.5.0 I still get this:
Error: Error executing task LinkAssemblies: error XA2006: Could not resolve reference to 'Android.Support.CustomTabs.CustomTabsClient/ExtraCallbackDelegate'
(defined in assembly 'Xamarin.Auth, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null') with scope 'Xamarin.Android.Support.CustomTabs, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
When the scope is different from the defining assembly, it usually means that the type is forwarded. (MyApp.Droid)
when trying to build in release.
From #167 I got the information that version 1.5.0 is pinned to CustomTabs version 23.3.0. So I started testing alpha versions and noticed that building in Release worked from 1.5.0-alpha-03 up to 1.5.0-alpha-08. Then when I updated to 1.5.0-alpha-09 it stopped working and does give me the error for every version over 09 (including stable).
So I checked the commits and found this:
https://github.com/xamarin/Xamarin.Auth/commit/9e5117f6397bffd86ccfc9d7d9124f361e6d60fd#diff-f6026efe6e14c1b09646b2ba065b7706
So you upgraded the CustomTabs package right? Does this mean that we need to update to 25.3.1?
I'm currently running Xamarin.Forms <IP_ADDRESS> and CustomTabs 23.3.0.
Thanks in advance!
/Ferenczi

@DFerenczi
Package management became real problem since Xamarin.Forms support was added. Forms are pinned to 23.3.0.
Usually I encourage users to install with 23.3.0 and then update CustomTabs (and other Android support if that does not hurt badly). Minimal version is pinned to 23.3.0
I have similar setup and never hit similar problems.
Try bumping and provide us feedback here pls.

Alright, unfortunately updating other Android support does hurt badly and creates other conflicts in my project. Guess i'll have to use the alpha version for now until I have the time to resolve problems that appear when updating.
Will post here when I update!
/Ferenczi

+1 experiencing the same problem and will attempt the same work around. I will be watching for an update Thanks @DFerenczi

+1 get the same error, when "link assemblies" are checked in project options.
in debug builds the error doesn't show

My PCL project builds with Xamarin.Auth 1.5.0 by updating CustomTabs and dependencies to 25.3.1.
I'm using the latest prerelease of Xamarin.Forms, with Android 7.1 as compile version.

@kapslocker Thats interesting! I have not had the time to try updating my packages since updating the CustomTabs package requires updating all other Support packages to the same version (or at least bumping them to a higher version). The app I'm building is going live in a couple of days so for now the alpha version will be my option. But will try to update packages in the future!

@kapslocker
Thank you for the tip. Using Xamarin.Forms <IP_ADDRESS>-pre5 with updated support packages made my project build in release!

Upgrade to Xamarin.Auth <IP_ADDRESS> upgrade fixed it for me! Thanks!

I've the same problem and I blocked to release the apk.
The error is:
ion: error XA2006: Could not resolve reference to 'Android.Support.CustomTabs.CustomTabsClient/ExtraCallbackDelegate' (defined in assembly 'Xamarin.Auth, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null') with scope 'Xamarin.Android.Support.CustomTabs, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. When the scope is different from the defining assembly, it usually means that the type is forwarded. ---> Mono.Cecil.ResolutionException: Failed to resolve Android.Support.CustomTabs.CustomTabsClient/ExtraCallbackDelegate

@robintschroeder Which Xamarin Forms and Support libs version do you have?

@biapar update all your Xamarin.Android libraries to the latest v25.3.1 to match what is in the current Xamarin.Auth-master source.

I've now the v6.
Have you installed Xamarin.Auth.Forms or Xamarin.Auth?

@biapar
Microsoft Visual Studio Enterprise 2017
Version 15.2 (26430.14) Release
VisualStudio.15.Release/15.2.0+26430.14
Microsoft .NET Framework
Version 4.6.01586
Mono Debugging for Visual Studio   Mono.Debugging.VisualStudio
Support for debugging Mono processes with Visual Studio.
Xamarin   <IP_ADDRESS>6 (fec6f88)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android SDK   <IP_ADDRESS> (9dbc4c5)
Xamarin.Android Reference Assemblies and MSBuild support.
Xamarin.iOS and Xamarin.Mac SDK   <IP_ADDRESS> (ad35de4)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

@biapar
Xamarin.Forms v<IP_ADDRESS>
Xamarin.Auth v<IP_ADDRESS>
Xamarin.Build.Download v0.4.5

@robintschroeder Have you update the Android Support Libs to v25.3.1?

@biapar  not quite - I am running Xamarin.Android.Support... v25.1.0
hth

@biapar  @DFerenczi @robintschroeder @jenart @alexvitoriano Can you please try this with the latest version of Xamarin.Auth
Regards

no resonse after two weeks closing


Feature request: Sort clips by view count

Sorting by view count is the best way to find the most popular content and mostly corresponds with quality, it would be great to click on a channel and watch their most viewed clips. Also it would be nice to have sorting options from the channel clips tab immediately instead of having to use the advanced search.

View count isn't something we display on the frontend because videos don't update that frequently after being archived/uploaded; I can somewhat see a use case for all-time videos, but it'd be all over the place for new uploads.

Sure but even if you take the view count like 48 hours after a clip upload and update it as infrequently as you want, it would still be a pretty helpful sorting method in the long run, probably the most helpful, either per channel or per stream.


run mongodb --quiet with quiet => true

It would be great if I could configure this module to run the mongo daemon --quiet.
Is there a way to do that?
This currently does not work. Is there such a parameter?
  class { 'mongodb':
    enable_10gen => true,
    quiet => true,
    dbpath => "${::db_path}/mongodb",
    version => $mongo_version,
    replSet => $::replica_set_name,
    keyFile => $mongo_keyfile,
  }

I know verbose defaults to false, but this level of logging is still much more than when running mongod --quiet
Thanks!

cbcb251b09cdb4f7a1587d86999b21dbc4e5d765 added a quiet parameter


Line up dispatcher

This should also make decoder creation (unnoticeably) faster, but I have
no idea why you'd want to construct decoders in a loop.

nice tip

Thanks. At least it must be faster and looks natural in tightly optimized codes.


RandomObjectPopulator has inverted checkArguments

@Deamon5550 These lines should be the opposite.

@Deamon5550
Status update.


Timeout

Hello,
is there any chance that it is normal that my func are being stopped exactly after one hour ?
Thanks a lot.

cron starts your job in its own goroutine and does not interfere with it in any way. My only guess is if your func is scheduled to run every hour, and the second run interrupts the first due to some shared resource. Without seeing the code, I can't offer any other advice.

Actually, it is scheduled every 3 hours, but the function is dying after 1 hour exactly but I do not understand why, this is crazy, no error, nothing..

Sorry, I don't have the information to help you diagnose that, but there is no mechanism in the cron library that could cause it. Unless you have some other idea, I don't see the connection with this library. I hope you solve it!


docs: Generate examples for models dynamiclly

So we don't have to keep writing them in the docstrings.

This might not be relaistic, if anyone has any ideas, please comment


konfig apply fails on repeat runs when applying request-termination to a specific consumer

I'm attempting to set up a kongfig yml to apply the request termination plugin globally to enable OR-based multi-auth per the multi-auth docs.
Given this kongfig.yml:
plugins:
  - name: request-termination
    consumer_id: anon
    attributes:
      enabled: true

consumers:
  - username: anon
    custom_id: anon

The first run succeeds at creating both the consumer and globally applied plugin:

However, it doesn't apply it to the correct consumer:

In addition, I could be doing something wrong, but subsequent runs applying that kongfig break like this:

I'm not sure this is broken as I could be trying to apply the consumer_id incorrectly.

I've determined that the consumer_id needs to be the internal id. It can't be the consumer name or custom_id. Knowing that, I believe this means that I can't tie a plugin to a consumer using kongfig.

Seems like a dupe of https://github.com/mybuilder/kongfig/pull/80.


Removed CSS flavors API & Added DataArts configs

@vladimirhasko Will it work without sdk for dataarts?

please add also entry for catalog

@vladimirhasko Will it work without sdk for dataarts?

No it won't. @Polina-Gubina please have a look at this urgent request to deliver the data-arts SDK proxy asap

Hi @vladimirhasko @vladimirvshivkov i have created pull request for  dataarts proxy class.
https://github.com/opentelekomcloud/python-otcextensions/pull/372


Star Sports Channel Not work

Your Environment

Add-on name: [ Jiotv]
Add-on version: [2.0.0]
Kodi version: [Kodi 19.4]
Operating system version/name: [Fire Tv os 7]
Using from country: [India]

Describe the bug
Star Sports Channel not Playing
Star sports channel show subscription error and not playing the only star sports channel. Other star channel working but star sports not work.

Got to JioTV add-on settings > more and enable Disable Welcome Popup and Extra HD Channels
All Star channels will work.

Start Maa, start gold, star sports or any other star channels are not working even after enabling the extra HD channels and disable welcome pop-ups

install hotstar addon from botallen repository

Start Maa, start gold, star sports or any other star channels are not working even after enabling the extra HD channels and disable welcome pop-ups

install hotstar addon from botallen repository

Start Maa, start gold, star sports or any other star channels are not working even after enabling the extra HD channels and disable welcome pop-ups

install hotstar addon from botallen repository

Did but not able to play.. When I tried with mobile jio network I can play it but not with non jio network


Fill in license value as well as classifiers in flit init

When using flit init you are prompted for a license. This is used to set the "Classifiers" field in flit.ini. From what I've seen, many packages fill in both the classifiers and the license metadata field (even though "License" is documented as optional).
Would it be worth using the license choice to populate both Classifiers and License in flit.ini?

I've also seen many packages using it that way, but my understanding is that it's meant to be used as an alternative when the desired license is not available as a classifier:
https://www.python.org/dev/peps/pep-0345/#license-optional

OK. I was surprised that if you omit it, the metadata shows "License: UNKNOWN" even though the classifier is present - but that's just the way the metadata processing works. Scanning my system shows 64 with License set vs 9 without, and of the ones with it set, just under half are variations on what flit init offers (most of the rest are BSD).
So I'd say the advantage of adding it is that people doing naive scans of metadata don't see "License: UNKNOWN" and draw the wrong conclusion, plus a certain level of consistency (I see "License: MIT", "License: MIT License", "License: MIT license", "License: MIT License ", and "License: MIT license "!)
But it's certainly a minor point and if you prefer not to do this, I'm fine with that.

AFAICT, even with the license information in the pyproject.toml file, the classifiers are never filled into the generated setup.py file.  This results in a PyPI page that lacks the license metadata, and this can break downstreams (e.g. a corporate environment that checks for an acceptable license).
Here's my pyproject.toml file from importlib_resources - and its PyPI page:
[build-system]
requires = [
    "flit",
    "setuptools",
    "wheel",
    ]
build-backend = "flit.buildapi"

[tool.flit.metadata]
module = "importlib_resources"
author = "Barry Warsaw"
author-email =<EMAIL_ADDRESS>home-page = "http://importlib-resources.readthedocs.io/"
description-file = "README.rst"
classifiers = [
    "Development Status :: 3 - Alpha",
    "Intended Audience :: Developers",
    "License :: OSI Approved :: Apache Software License",
    "Topic :: Software Development :: Libraries",
    "Programming Language :: Python :: 3",
    ]
requires-python = '>=2.7,!=3.0,!=3.1,!=3.2,!=3.3'
requires = [
    "pathlib2; python_version < '3'",
    "typing; python_version < '3.5'",
    ]

and here's the generated setup.py file:
#!/usr/bin/env python
# setup.py generated by flit for tools that don't yet use PEP 517

from distutils.core import setup

packages = \
['importlib_resources',
 'importlib_resources.tests',
 'importlib_resources.tests.data01',
 'importlib_resources.tests.data01.subdirectory',
 'importlib_resources.tests.data02',
 'importlib_resources.tests.data02.one',
 'importlib_resources.tests.data02.two',
 'importlib_resources.tests.data03',
 'importlib_resources.tests.data03.namespace.portion1',
 'importlib_resources.tests.data03.namespace.portion2',
 'importlib_resources.tests.zipdata01',
 'importlib_resources.tests.zipdata02']

package_data = \
{'': ['*'],
 'importlib_resources': ['docs/*', 'docs/_static/*'],
 'importlib_resources.tests.data03': ['namespace/*']}

extras_require = \
{":python_version < '3'": ['pathlib2'], ":python_version < '3.5'": ['typing']}

setup(name='importlib_resources',
      version='0.5',
      description='Read resources contained within a package.',
      author='Barry Warsaw',
<EMAIL_ADDRESS>      url='http://importlib-resources.readthedocs.io/',
      packages=packages,
      package_data=package_data,
      extras_require=extras_require,
      python_requires='>=2.7,!=3.0,!=3.1,!=3.2,!=3.3',
     )

I've marked this as closed by #402. 'License' is not a required field according to the core metadata spec, and with that change, the License field will simply be omitted rather than indicating UNKNOWN. I hope that's clearer.
It looks like PEP 639 will give us some more structured way to record license metadata in the future.

Instead of LicenseRef-Public-Domain I would prefer PEP 639 to include more explicit way of copyright opt-out. Otherwise it looks like a hack to me.

You'll need to take that discussion up elsewhere - I'm not involved in PEP 639.


Fix typo in argument name

@DominikMe : Thanks for your contribution! The author(s) have been notified to review your proposed change.

This typo fix looks good to merge/approved. Publishing in this repository is suspended until Tuesday, March 2. Merging will resume Tuesday, and we will merge the pull request then. Thanks.


Add page on custodial head deployment model

The title says it all :) This could be useful as a reference when working on L2-based voting system
To check before merging:

[ ] CHANGELOG is up to date
[X] Up to date with master

Thanks for writing this up. Will have a look tomorrow. But one thing to think about: Although honest, naming this "custodial" is probably not going to serve us well in this ecosystem. Maybe we should go back to our original "Delegated Head" naming?


Add zero padding on embeddings column names for ordering purposes

Problem Description
This issue is not super important, but it would help to have it fixed.
The output of MinHashEncoder and GapEncoder is a dataframe whose columns are in the form <col>_1, <col>_2, ..., <col>_10, <col>_11. While intuitive, this is slightly confusing when columns get sorted, e.g. with the AggJoiner, because then the ordering becomes <col>_1, <col>_10, <col>_11, <col>_2
Feature Description
I suggest we add left zero padding by accounting for the number of columns:

between 1 and 9 columns, no padding: 1, ..., 9
between 10 and 99 columns, a single 0 padding: 01, ..., 99
and so on

Alternative Solutions
Keep it as it is.
Additional Context
No response

@Vincent-Maladiere
I would like to work upon this issue

Hello @Shree7676 thank you, go ahead 😊

@Vincent-Maladiere
I am going through the code of GapEncoder and I am bit confused between columns and labels.
can you provide some code through which i can reproduce.
below is something I explored and the column name here doesn't provide a good picture of above issue.
import pandas as pd from skrub import GapEncoder data = pd.DataFrame({     'category': ['apple', 'banana', 'apple', 'orange', 'banana', 'orange', 'banana'] }) encoder = GapEncoder(n_components=7, random_state=42) encoded_data = encoder.fit_transform(data['category']) encoded_df = pd.DataFrame(encoded_data) print(encoded_df.columns.tolist())
it provides output as
['category: apple, orange, banana', 'category: banana, apple, orange', 'category: orange, apple, banana', 'category: apple, orange, banana (3)', 'category: apple, orange, banana (4)', 'category: apple, orange, banana (5)', 'category: apple, orange, banana (6)']

Yes, indeed, I may have written this issue too fast. This issue was specific to the MinHashEncoder, so I don't think there is a need for the GapEncoder. Sorry for that.

Thanks @Vincent-Maladiere
For all the guidance :)

There are a lot of other issues, feel free to pick another one. If you're not sure which one to pick, we can discuss it on Discord :)


update to embedded-hal 1.0

Thank you for the beautifully documented and tested library. I am using this in a project, and would like to bring it up to the latest embedded-hal version, so that I can also use your other library embedded-hal-bus without hassle  :-D
Seems like these warnings from chrono will need a fix as well.

I found that reading from the device would sometimes cause a panic if it did not have a time or date set


Enable "Keep Me Signed In" MSAL

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.29.0
Wrapper Library
Not Applicable
Wrapper Library Version
None
Public or Confidential Client?
Public
Description
We use the MSAL library to access corporate resources.
The KMSI checkbox does not appear on login page.
AD FS server command: Set-AdfsProperties -EnableKmsi:$true
Are there any additional settings I need to add in order to show KMSI?
MSAL Configuration
//MSAL Config
const msalConfig = {
  auth: {
      clientId: APPID,
      authority: 'https://corporate.network/adfs/',
      knownAuthorities: ['https://corporate.network/adfs/'],
      redirectUri: REDIRECTURL,

  },
  cache: {
      cacheLocation: "localStorage",
      storeAuthStateInCookie: true,
  },
};

const msalInstance = new msal.PublicClientApplication(msalConfig);

function getWebAuth() {
  msalInstance
    .acquireTokenPopup(loginRequest)
    .then(handleResponse)
    .then(() => {

    })
    .catch((error) => {
      console.error(error);

    });
}

Relevant Code Snippets
No response
Identity Provider
ADFS
Source
Internal (Microsoft)

@alexseyrakov MSAL.js does not control the login UX on the server, you will need to reach out to your ADFS admin for any issues with the login page.


Package not published on constructs.dev

I'm trying to publish an initial version of a construct on constructs.dev. Here is its npmjs package.
I've read https://constructs.dev/contribute and added the correct tag, license + compiled with jsii.
I'm not sure why it's not available. Can you please help me out?

It will take some time until it's picked up https://constructs.dev/packages/cdk-cloudwatch-alarm-chatbot/v/1.0.3?lang=typescript

Ow sorry for my impatience!