feat: add cosmosdb to available resources

Description
Cosmos DB - refactored in order to set up the resources config and dependencies in a central place, availableResourecs.
Work in progress for new azure provisioning service layer (this code is not live to customers yet).
Task Item
refs #7629

Coverage remained the same at 56.423% when pulling 56f83892ed69c5a0f5b663611974147ff825555b on natalgar/7629cosmosDb into 860e1e1d550eb73272b3052c3781cb51e5c73544 on main.

replacing this PR with #8321


Fix memory leaks

This PR fixes some memory leaks in bpftrace. I've only run the asan
build under some very basic programs so this doesn't prove that bpftrace
is totally leak free or anything.
This PR is also rebased on top of #1050. I'll rebase this PR onto master
once #1050 merges.
This fixes some of #1047.

@ajor I tried that initially (I mention it in one of the commit messages) but I didn't really like how that turned out. Here's the code: https://github.com/danobi/bpftrace/commit/511d1927ac60b5d05a3a8bb7fa3a954c7586f147
It seemed like a huge amount of churn in parser.yy. What are your thoughts?

So bison recently (see "C++: Support for move semantics (lalr1.cc)" in https://fossies.org/linux/bison/NEWS) added support for smart pointers. But unfortunately bison 3.2.1 (2018-11-09) isn't widely distributed yet. I'm running fedora 30 and still on bison-3.0.5.
I'm trying to do build time patching of parser.tab.hh but it's really heinous and fragile. I think the most maintainable solution is to do the regular old deletes for now.

Sorry, I meant to look into this to try and understand but didn't get round to it. Is it just that we have to explicitly type out std::move() or do move semantics not work at all with older Bisons? What's broken with them?

It's more than typing out std::move, it's that bison is missing an std::move in the generated code: http://www.comrite.com/wp/c11-stdunique_ptr-as-semantic-value-in-bison-c-mode/

There's also some issues with ownership in ast.h. For example, @a <<= 1 creates an ast::AssignMapStatment and an ast::Binop, both of which own pointers to the underlying ast::Map.
Even old style deletes get kind of nasty here b/c you can't always assume the AssignMapStatement holds ownership.
Could go with shared_ptr but that just kicks the ownership issues down the road.

I pushed some code that gets the job done. Not very pretty though.

Ah yeah we'd have to change the compound assignments. I think something like this should work to make a copy of one of the $1s to fix that problem:
$$ = make_unique<ast::AssignMapStatement>(
       $1,
       make_unique<ast::Binop>(std::make_unique<Map>(*$1),
                               token::LEFT,
                               $3,
                               @2),
       true);

Ok, I guess raw pointers are the way to go. We should also delete the default copy and move constructors to complete the "rule of 5".
I'd actually like to add copy constructors for these nodes at some point so we can do some AST manipulation, but that can wait. When we add copy constructors we'll be able to change the compound assignment node to have two separate copies of the map and simplify the ownership logic.
BTW, when I was talking about liking inline function definitions I only meant absolutely tiny ones (0/1 lines) ;)   I agree that bigger ones like this make it harder to read


fix($http): properly access request headers with mixed case

Fixes #10881

@petebacondarwin would you mind taking a quick look at this one?

Style discussions aside - Wouldn't it be more performance to simply lower case the header names when parsing them in the first place?

@petebacondarwin here we are talking about request headers so the ones provided by a user. In this sense we are not parsing anything.

@petebacondarwin I did the changes we've discussed during the hangout review. Mind taking another look?

LGTM


feat: saved api_key to keychain for user

This is a draft PR only for early feedback.  It does not have test yet and also depends on the exchange PR
What
When the api key environment variable does not exist,

it looks up the api key from keychain.  if it does not exist, then
the users are prompted to enter the api key and
the users are prompted whether they want to save the api key in the keychain

)

very cool! how would a user update the keychain with the same prompts (typo, rotation, etc)?
just had a thought! what do you think of a goose config (and maybe even a goose check)? that way we can use it as a catch all to do things

check latest version
check profiles
check api keys of each profile (both environment variables and keychain)?

cc @aat

cc @alecthomas

very cool! how would a user update the keychain with the same prompts (typo, rotation, etc)?
just had a thought! what do you think of a goose config (and maybe even a goose check)? that way we can use it as a catch all to do things

check latest version
check profiles
check api keys of each providers (both environment variables and keychain)?

Yes, that could be useful.

how would a user update the keychain with the same prompts (typo, rotation, etc)?
I think we can enhance this later.  When we load the api key from keychain, the console prints the message about the api_key source. If it is not correct, the user still can update by themselves.

This is awesome!


Lotka Volterra task

This PR solved #21 notebook

(not exactly the same because of noise)

Notebook

is this PR up to date, ready to merge?


collapsible elements remain active

Opening a collapseble element does not deactivate previous one. Both with Opera and firefox on Android.
See example here:
http://www.farmacia-dstf.unito.it/do/corsi.pl/ShowMobile?_id=133f
Any suggestion?
claudio

Seems to be related to JQuery Mobile and this:
'''clickEvent.forwardedTouchEvent = true;'''


Ping pong delay enters a feedback loop coming from the 404 page

Try not to blow out your speakers when testing this one...

Sevish — Yesterday at 10:13 PM

WOW - had to close the SW tab because it was sitting idle for 10 mins then started making a loud sound. might be an issue with my setup, but just mentioning in case useful
sounded as if oscillators had been running quietly in the background and then got faded in to left speaker first then right speaker at high level. maybe related to the amplitude envelope or the delay?
found it


fixed: next is not defined

if koa-router is used in other middleware like :
  return function* graceRouter(next){
    yield Router.routes();
    yield next;
  }

there catch an error in router.js : ‘next is not defined!’

koa-router requires the koa middleware signature of mw(ctx, next) (or mw(next) for versions 5.x). I don't think this change fits with the usage of koa very well.


Missing SEMI-AUTO source of annotation

My actions before raising this issue

[x] Read/searched the docs
Docs mentioning semi-auto
[x] Searched past issues

According to docs there are 3 sources of annotation

Source- source of creating of objects MANUAL, AUTO or SEMI-AUTO.

But case of SEMI-AUTO is not handled anywhere in CVAT UI (or in source code).
Steps to Reproduce (for bugs)

Create annotation with semi-auto source

either export annotations.xml with source

<track id="0" label="mbt" source="semi-auto">

Use cvat SDK

LabeledShapeRequest(type=ShapeType("mask"),

                                                  occluded=bool(int(obj["occluded"])),
                                                  source="semi-auto",
                                                  outside=False,
                                                  z_order=0,
                                                  rotation=0.0,
                                                  label_id=mappings_project_labels[obj["label"]],
                                                  points=obj["rle"] + [obj["xtl"], obj["ytl"], obj["xbr"] - 1, obj["ybr"] - 1],
                                                  frame=frame_id))

See it in CVAT ui

Expected Behaviour
Visible source should be SEMI-AUTO
Current Behaviour
It shows MANUAL
Possible Solution
Implement handling it.
Context

Your Environment
CVAT 2.4.5

@pktiuk
I think it is a documentation issue. We never have something like "semi-auto" in CVAT.

@bsekachev
But I think this semi-auto may be very useful. Especially in case of annotating with SAM

You are always welcome to implement that


Camera button pressed before session.isRunning becomes true results in NSInternalInconsistencyException

I added some Prints into capturePhotoAsyncronously(). Basically if the function is called before session.isRunning == true, then AVCaptureStillImageOutput will throw an NSInternalInconsistencyException.
DEBUG_USER_ACTION: CameraViewController.capturePressed()  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = capturePressed #line = 51
DEBUG_USER_ACTION: CameraViewController.captureTapped()  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = captureTapped #line = 56
self.session.isRunning: true
videoConnection.isEnable: true
videoConnection.isActive: true
DEBUG_USER_ACTION: didTakePhoto  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = swiftyCam(:didTake:) #line = 183
DEBUG_USER_ACTION: didTakePhoto  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = swiftyCam(:didTake:) #line = 183
2017-08-30 17:17:11.201236-0700 SomeFoodieApp[7915:3469642] Warning: Attempt to present <SomeFoodieApp.MarkupViewController: 0x1088cbb00> on <SomeFoodieApp.CameraViewController: 0x1022d4a00> whose view is not in the window hierarchy!
DEBUG_USER_ACTION: CameraViewController.exitPressed()  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = exitPressed #line = 61
DEBUG_USER_ACTION: CameraViewController.capturePressed()  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = capturePressed #line = 51
self.session.isRunning: false
videoConnection.isEnable: true
videoConnection.isActive: true
2017-08-30 17:17:23.451577-0700 SomeFoodieApp[7915:3469642] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '*** -[AVCaptureStillImageOutput captureStillImageAsynchronouslyFromConnection:completionHandler:] Inconsistent state'
*** First throw call stack:
(0x188802fe0 0x187264538 0x190252610 0x100dadaec 0x100da86f0 0x100db1508 0x100db153c 0x100db171c 0x100db16d8 0x100da1a88 0x100da1ad8 0x18ef068d0 0x18ef0a104 0x18eac40b4 0x18e965fc4 0x18eefa3a8 0x18eef9f78 0x18eef9224 0x18e964350 0x18e934f80 0x18f12ea20 0x18f12917c 0x18f12945c 0x18f12945c 0x18f12945c 0x1887b142c 0x1887b0d9c 0x1887ae9a8 0x1886deda4 0x18a149074 0x18e999c9c 0x10008f210 0x1876ed59c)
libc++abi.dylib: terminating with uncaught exception of type NSException

Working around this by disabling the camera button until .AVCaptureSessionDidStartRunning via NoficiationCenter observation. If this is a requirement please add this to the Readme documentation? Thanks!

I haven't run into this issue. I was hoping that checking for self.session.isRunning is true before calling captureStillImageAsynchronouslyFromConnection:completionHandler:, but it appears this exception is raised while self.session.isRunning is true. Can you confirm?

self.session.isRunning is only checked to stop the Preview Layer from appearing. I don't think there's anything within the framework preventing SwiftyCamButton.Tap from being executed?
Basically to reproduce the condition, one just have to keep hammering the camera button as the view is still loading. The odd is the camera session is going to take a while to get running, and SwityCamButton.Tap() will get triggered before isRunning == true

If you are running from source, can you try:
fileprivate func capturePhotoAsyncronously(completionHandler: @escaping(Bool) -> ()) {

    guard self.session.isRunning == true else {
        print("Cannot take photo while session isn't running")
        return
    }
    ...

Very strange...
DEBUG_USER_ACTION: CameraViewController.capturePressed()  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = capturePressed #line = 51
Cannot take photo while session isn't running
DEBUG_USER_ACTION: CameraViewController.captureTapped()  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = captureTapped #line = 56
DEBUG_USER_ACTION: CameraViewController.capturePressed()  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = capturePressed #line = 51
Cannot take photo while session isn't running
DEBUG_USER_ACTION: CameraViewController.captureTapped()  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = captureTapped #line = 56
DEBUG_USER_ACTION: CameraViewController.capturePressed()  #file = /Users/biscottigelato/Documents/Dev Space/EatellyApp/SomeFoodieApp/CameraViewController.swift #function = capturePressed #line = 51
self.session.isRunning: true
2017-08-30 19:22:04.014696-0700 SomeFoodieApp[7990:3506864] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '*** -[AVCaptureStillImageOutput captureStillImageAsynchronouslyFromConnection:completionHandler:] Inconsistent state'
*** First throw call stack:
(0x188802fe0 0x187264538 0x190252610 0x100e49a6c 0x100e44868 0x100e4d52c 0x100e4d560 0x100e4d740 0x100e4d6fc 0x100e3dc00 0x100e3dc50 0x18ef068d0 0x18ef0a104 0x18eac40b4 0x18e965fc4 0x18eefa3a8 0x18eef9f78 0x18eef9224 0x18e964350 0x18e934f80 0x18f12ea20 0x18f12917c 0x1887b142c 0x1887b0d9c 0x1887ae9a8 0x1886deda4 0x18a149074 0x18e999c9c 0x10012eac8 0x1876ed59c)
libc++abi.dylib: terminating with uncaught exception of type NSException

With my implementation, I was not able to make it crash. Not sure if it's just a pure timing thing...
// Listen to notification of when SwiftyCam's AVCaptureSession isRunning == true     NotificationCenter.default.addObserver(forName: .AVCaptureSessionDidStartRunning, object: nil, queue: OperationQueue.main) { _ in       self.captureButton?.isEnabled = true       NotificationCenter.default.removeObserver(self, name: .AVCaptureSessionDidStartRunning, object: nil)     }

And again, my test method is just basically hammering that capture button as quickly as i can after i pressed from a previous view to launch the camera view.

Can you try branch testFix

Will do, but very swamped at the moment. I'll try to give it a run Saturday.

I got this. I browsed through the new delegate and it doesn't seem there's one that indicates that capture session is ready/started?

🔷 User Action - CameraViewController.captureTapped() (CameraViewController.swift:70)
🔷 User Action - CameraViewController.capturePressed() (CameraViewController.swift:65)
🔷 User Action - CameraViewController.captureTapped() (CameraViewController.swift:70)
[SwiftyCam]: Cannot take photo. Capture session is not running
🔷 User Action - CameraViewController.capturePressed() (CameraViewController.swift:65)
[SwiftyCam]: Cannot take photo. Capture session is not running
🔷 User Action - CameraViewController.captureTapped() (CameraViewController.swift:70)
🔷 User Action - CameraViewController.capturePressed() (CameraViewController.swift:65)
🔷 User Action - CameraViewController.captureTapped() (CameraViewController.swift:70)
[SwiftyCam]: Cannot take photo. Capture session is not running

I have the same issue and I found the sessions starting place in the "SwiftyCamViewController" and I saw the sessions is starting on the "ViewDidAppear" and if you override the ViewDidAppear and the sessions is not running because the SwiftyCamViewController's ViewDidAppear is not called. Try this. if you use override ViewDidAppear remove and run again.


Json decode date time column

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Can't reference forward-slash operator functions

Description
I'm attempting to write DocC documentation for CasePaths, which uses a prefix / operator for defining a "case" path from an enum type to a particular case (similar to how \ is used for defining a key path). While I can document these operator functions, I cannot refer to them or organize them:

Xcode lists autocompletion for these functions, but autocompletes result in invalid DocC references, e.g. /(embed:) (/ doesn't seem to be a valid identifier, and the function is overloaded many times).

If I run the DocC server and manually navigate to these functions, I get URLs like http://localhost:8080/documentation/casepaths/(_:)-82yvm, but none of the following work when trying to reference the function in documentation:

(_:)-82yvm
/(_:)-82yvm
_(_:)-82yvm
\/(_:)-82yvm
%2F(_:)-82yvm
%2f(_:)-82yvm

Checklist

[ ] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior
I expect there to be a way to reference and organize these APIs.
Actual behavior
I cannot find a way to reference or organize these APIs.
Steps To Reproduce

Define a prefix operator / and function that uses it.
Attempt to reference the function in documentation.
Build documentation.

Swift-DocC Version Information
SwiftDocCPlugin 1.3.0
Swift Compiler Version Information
swift-driver version: 1.87.1 Apple Swift version 5.9 (swiftlang-<IP_ADDRESS>.108 clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx13.0

Additionally, the library defines a .. infix operator, and I can't figure out how to reference it, either.

The issue with the forwards slash characters is a recently discovered that's issue also tracked as rdar://112555102.

Additionally, the library defines a .. infix operator, and I can't figure out how to reference it, either.

I think that the .. infix operator would be linked to using ..(_:_:).
DocC inserts a leading ' to any path component that start with "..". That said, I would think '..(_:_:) would be close enough to ..(_:_:) for DocC to be able to diagnose and suggest a fixit for it. What diagnostic message are you getting for the '..(_:_:) link?

I think that the .. infix operator would be linked to using ..(_:_:).

That worked, thanks!

DocC inserts a leading ' to any path component that start with "..". That said, I would think '..(_:_:) would be close enough to ..(_:_:) for DocC to be able to diagnose and suggest a fixit for it. What diagnostic message are you getting for the '..(_:_:) link?

Unfortunately, Xcode autocompleted ..(lhs:rhs:) instead, and no suggestions were offered.

https://github.com/apple/swift-docc/pull/717 should resolve the issue with forward slash operators functions.

Unfortunately, Xcode autocompleted ..(lhs:rhs:) instead, and no suggestions were offered. When I manually tried '..(_:_:) no suggestions were offered, either. When I entered ..(_:_:) I was finally given suggestions since .. is overloaded a couple times.

The root cause of the autocompletion issue isn't in DocC's code so that'd have to be tracked with a Radar or Feedback.
..(lhs:rhs:) seems to be too different from ..(_:_:) to be offered as a suggestion but '..(_:_:) is close enough to be offered as a suggestion in Xcode 15.0 (15A240d)

The root cause of the autocompletion issue isn't in DocC's code so that'd have to be tracked with a Radar or Feedback.

@d-ronnqvist Thanks! Did you open a feedback?

The root cause of the autocompletion issue isn't in DocC's code so that'd have to be tracked with a Radar or Feedback.

@d-ronnqvist Thanks! Did you open a feedback?

I didn't but after searching I can say that rdar://78412414 is tracking this specific autocomplete issue.


Items selected from the patch library appear below the patch library

so they can't be seen

assuming that soon the same collapsible-select-control functionality may be used for assets library, i modified its dragAndDropMouseDownHandler()  so it checks in which library (id) element was clicked and hides it for one second to show that element was dropped under it.


Confusion about HubSpot's strategy wrt Tether based solutions

I have a questions for the maintainers here,
You have a bunch of projects ("Tooltip", "Shepherd" and "Select") which are all based off Tether's positioning system. But still you keep bundling the whole tether into each of these library's distributable builds. WHY?
If I am to use more than of your projects, there is no simple way to include the common code (tether) once, say using RequireJS, and then just have the tooltip's and shepherd's code separately, all pulled using Bower.
Right now, I only observed that Shepherd has the stand-alone build without the bundled tether code, but none of the other libraries have such organization.
Also, even with Shepherd, when I install it using bower, everything is pulled BUT NOT the standalone builds, which should make more sense than  :-(
Can I file this as a feature request? Have the AMD standalone builds of the libraries be distributable along with the bundled-up versions.

Has this been done? Looks like Kumar was going to start, but the issue is closed?

As part of the large upgrade path that occurred in the Tether based projects, this should be completely resolved. Each project now only include that projects source and dependencies need to be explicitly required separately. In addition, they should all be UMD.
That said, there have been requests to bring back the bundled, standalone versions, so one of the next upgrades coming (hopefully...) soon is to include a build step to include these are well.

+1 build step is good option.


Draft PR for future updates

Note: Pull requests which don't include the minimum details specified
in this template will probably be closed out-of-hand.
Issue link
Links to GitHub issues that this PR closes (if there's no issues, use "N/A").
Description
A detailed description of each change in the changeset.
How the changeset was tested
A detailed list of cases which the author verified before requesting review.

The ideal option here is a list of existing, updated, or newly-created UI
tests that cover the included functionality.
The next best option is probably a list of screenshots or videos.
The fallback option is a simple-but-detailed list of steps taken to verify changes.

Changes were verified on the following platforms:

[] Chrome desktop
[] Firefox desktop
[] Safari desktop
[] Chrome Android
[] MetaMask browser Android
[] Safari iOS
[] MetaMask browser iOS

Closing because this might be stale and there's no info in PR.


Removed Linux as Visual Studio is not supported on Linux.

Internal Review

We should get @danroth27 to approve this change, as I think he wrote that ....... and I don't like mess'in too much with what the boss gives me! 😆 lol

I think he was just saying "VS on Windows" ....... and also "on Linux" ... and also "on macOS" ... not VS on Win, Linux, and macOS. I think we could go with something like ...

Stay productive on Windows, Linux, and macOS with a development environment, such as [Visual Studio](https://visualstudio.microsoft.com) or [Visual Studio Code](https://code.visualstudio.com/).

Let's go ahead with this, and Dan may provide further guidance for a patch if needed.
Thanks @18-F-cali! :rocket:


Adding images and color code used in WireFrame

Description
 Landing Page image and some other images along with Color Coding used in making Wireframe is not present or specified in the concerned folder in master branch
Concerning Folder
https://github.com/houseofgeeks/hg/tree/master/WireFrame
Screenshots/testimonials

May I create a PR for adding those images/text file containing color codes used to the master branch - WireFrame folder ???. So that others dont have to look for images and color codes that are being used while making the designs.

You may include that in #19

naah, make another PR, that PR has already filled up !

closing against #24


Improve error message for clash between type name & field reference

Repro is with zq commit f8d7a87 and the Zeek NDJSON sample data.
When attempting certain additional Zed operations after applying the reference shaper for Zeek, we see failures with error messages that aren't too helpful.
$ zq -z -I ~/work/zed/zeek/shaper.zed '| head 1 | cut id.resp_h' weird.ndjson.gz
invalid expression on lhs of assignment

$ zq -z -I ~/work/zed/zeek/shaper.zed '| head 1 | put classnet=network_of(id.resp_h) | count() by classnet | sort classnet' weird.ndjson.gz
put: a referenced field is missing

The root cause turns out to be that there's currently a type definition called id within the shaper:
type id={orig_h:ip,orig_p:port,resp_h:ip,resp_p:port};

This clashes with these later attempts to treat id as a reference to a named field in the log data.
We discussed this as a group and there was consensus that the way to address in the short term is to use more descriptive names for the types in the shaper such that they would not conflict with named fields in the data, e.g. type socket in this case. However, even if we show best practices in our reference configs and docs, since certain data sources may have hundreds or thousands of fields of different names, we can't rule out that this might still happen in the wild. Therefore the error messages should be improved to indicate what actually happened, i.e. explicitly mention the clash.

This has been fixed as we now require type values to be wrapped in angle brackets...


#1 Add DHT22 room temperature sensor

Resolves #1
Add a DHT22 room temperature sensor so the accessory knows what the real temperature of the room is.
Testing

Note - adding it directly no longer builds on macOS
Needs to be run via root to access the DHT22 sensor: sudo /usr/local/go/bin/go run homekit-daikin-infrared.go -temperaturePin 4

Not sure this is the best approach.

I might keep this branch separate for now.


[utils] fix deepmerge issue with NextJS Edge runtime SSR

I made MUI work (more or less) with the new NextJS 12.2 edge runtime SSR. I found a bunch of issues on the emotion side and only this small but critical one on your side (or Next's side, tbh I am not sure).
Somewhy ({}).constructor === Object is false on the edge runtime and messes up pretty much everything with MUI via a deepmerge internal check.
Minimal repro is this NextJS page:
export default () => 'Testy'

const x = {}
console.log(x.constructor, Object, x.constructor === Object)

export const config = {
  runtime: 'experimental-edge'
}

It logs [Function: Object] [Function: Object] false
I suspect from the tests that part of the check was there to check against prototype pollution, I did not check yet. Please let me know if you are interested and I can put more work into this and maybe the emotion side of things too.

FYI: the other critical issue is with @emotion/cache. It loads the .browser file from the dist on the edge runtime (and loads the "normal one" on Node). The browser build fails as it relies on document being defined. A simple webpack alias solved it for me.
It seems like polyfilling is not on option with the Edge runtime, it still checks and complains about "unsupported APIs"

@solkimicreb It seems to me that it's an issue on NextJS Edge runtime. I'd suggest opening an issue in their repo. As far as I understand, the other issues you mentioned are also related to the implementation of the runtime. If you think any of them is a bug on Material UI's side, please open a new issue


0.9.0

What is new

Provides documentation on Android implementation
Releases Variants to Github Action Marketplace
Generates necessary configuration files for Fastlane Match
Ability to deploy application variants to different stores
Ability to specify destination of custom properties
Introduces custom properties on a global level
Introduces signing configuration on global and variant level
Provides Fastlane template for Android
Separates business logic from Variants CLI package to VariantsCore framework
Provides unit test coverage
Ability to deploy to TestFlight
Ability to automatically detect platform for all 3 commands
variants init for iOS automatically populates variants.yml
Replaces SwiftCLI with swift-argument-parser

Checklist:

[x] I ran make validation locally with success
[x] I have not introduced new bugs
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new errors

Warnings

:warning:
Pull request is relatively big. If this PR contains multiple changes,
consider splitting it into separate PRs for easier reviews.

  Generated by :no_entry_sign: Danger Swift against cbda4f9e719c01797ae186464744c44652c2c51e


Functional: allow explicit domain in field view

Adds the possibility to pass domain as argument in field view program, instead of relative to the output field. If all domains are explicit, the itir fencil will not get the extra size arguments. This needs cleanup and checks...
@program
def copy(
    dom: Domain[IDim, JDim, KDim],
    inp: Field[[IDim, JDim, KDim], float64],
    out: Field[[IDim, JDim, KDim], float64],
):
    copy_stencil(inp, out=out[dom])

This PR does actually 2 changes: allow domain as program argument, allow domain in getitem of out field. I am not sure if the former is a good idea...

Passing domain as program argument is not needed for now, creating an explicit domain is implemented in #940


Radiation Suit Chestpiece recipie inverted.

The radiation suit recipe is upside down, at least compared to most armor, the neck slot is at the bottom.

Fixed for next release


rclone mount: do not present files when in an errored state

I'm guessing the behavior is due to caching of files and their metadata but from what users have told me: should a service start returning errors (such as due to data transfer quota exhausted) then the files will continue to shown (readdir + stat) but open's and read's will fail.
MergerFS is following certain policies in order to select which file to open. If the file selected happens to be on the "broken" mount then the user will get that error. If however rclone decided to no longer present the files then mergerfs would pick the file which is still available to it. In effect a "failover".
Under a typical harddrive failure (at least in my experience) the drive will still be mounted but files won't be shown. This allows mergerfs to appear OK even though an underlying drive may have failed. (Say you have files mirrored across two or more drives.) I'm working to make mergerfs look at other drives should a certain command fail on the primary one selected but it may be easier to have rclone present failure states differently to the user. I don't know what the APIs from the services provide but perhaps a quota limit could result in rclone dropping all indication of files/dirs until the service is available again?

I was trying to do something similar with nginx through the use of the try_files module where I could make fault tolerance across multiple mounts and this was immediately brought as an issue.  It would be helpful if listing of files would break if the mount is in an error state.  The question I guess would be how to determine if it was in that state.  Perhaps some heart beat between the mount and the provider.

Hmm, it is quite difficult to determine that a mount is broken.  The providers aren't good at saying - this is broken now, go away, they just give errors on the transactions, which might be OK if you retry them.

No "you're over quota" errors? If not would perhaps some retry threshold be reasonable? After N tries the service is put into an errored state for some configurable amount of time?

Slippery slope.  If someone configured 60 transfer threads and quota is saying to allow 12 at that time then you'll get a lot of errors but the mount is working fine...
I've also had issue where threads are not doing any work but other than are fine.  In this case the mount is partially working.  My nginx server is hung on some threads but others are streaming.

That's a different kind of condition. If concurrency is also a limit then it should properly handle that and not report it as an OS error. Ideally there'd be a priority queue of calls so no thread starves or has to return back an error to the OS.
Very very little software expects filesystems to be intermittently available. Well written software will handle EINTR (which could help simplifying the implementation) but even that probably can't be relied on.


tilt: make backend able to send snapshots

this ended up being surprisingly annoying, mostly coming down to:

We had code in the TS that cleaned up the snapshot object before posting it. I wanted to move this into the backend, so that the backend could generate a snapshot.
This meant the backend needed to deserialize the object and know the snapshot structure. We have nothing enforcing that the view types in the backend and frontend match. It turns out the frontend had an extra endpoints field, and set some timestamp fields to empty string, which the default go serializer doesn't like.
The view had an error field, which is not roundtrip-serializable (it comes back as nil)
The alert handling is still entirely on the JS side, so now we need client-side types to accept them. NB: this means that snapshots created by the backend won't have alerts.

tbh i feel like we're eventually going to have to give up and make webview a protobuf

I don't even consider that giving up - the current situation is messy and bugprone and expensive


Incremental training not working on Huggingface Trans model

I trained a model from scratch using:
python3 train_joint_trans.py --train=data/custom/train --val=data/custom/valid --save=saved_models/joint_trans_model --epochs=3 --batch=64 --cache_dir=transformers_cache_dir  --trans=deepset/bert-large-uncased-whole-word-masking-squad2 --from_pt=true

and then attempted to incrementally train the model using:
#incremental training
python3 train_joint_trans.py --train=data/hp-custom/train --val=data/hp-custom/valid --save=saved_models/joint_trans_model2 --epochs=3 --batch=64 --cache_dir=transformers_cache_dir  --trans=deepset/bert-large-uncased-whole-word-masking-squad2 --from_pt=true --model=saved_models/joint_trans_model

This resulted in the following error:

File "train_joint_trans.py", line 107, in
epochs=epochs, batch_size=batch_size, id2label=id2label)
File "/Users/jv/dev/project/test/ai/tensorflow/BERT-Concierge/dialog-nlu/models/base_joint_trans.py", line 79, in fit
callbacks=callbacks)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/keras/engine/training.py", line 108, in _method_wrapper
return method(self, *args, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/keras/engine/training.py", line 1098, in fit
tmp_logs = train_function(iterator)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py", line 780, in call
result = self._call(*args, **kwds)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py", line 846, in _call
return self._concrete_stateful_fn._filtered_call(canon_args, canon_kwds)  # pylint: disable=protected-access
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 1848, in _filtered_call
cancellation_manager=cancellation_manager)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 1924, in _call_flat
ctx, args, cancellation_manager=cancellation_manager))
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 550, in call
ctx=ctx)
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/eager/execute.py", line 60, in quick_execute
inputs, attrs, num_outputs)
tensorflow.python.framework.errors_impl.InvalidArgumentError:  Received a label value of 40 which is outside the valid range of [0, 39).

Not sure why this is happening.

Hi @jvence did you add new label?
It seems to me that you added new labels and there is a bug in incremental training that doesn't use the saved tag/intents vectorizers.
But anyway adding new labels or tags should train the model from the beginning, since it is a different architecture.

Yes I did add new labels. Thank you for letting me know. BTW amazing job on the project. It's come such a long way. HF support is fantastic.

Thanks @jvence for your great encouraging words.
BTW you pointed me on a bug as described in my first comment. now it's fixed a886e6f4e1f840288eae195a7dea7b43997782a6
If you try the same experiment it will give you an exception in encoding tags or intents.

That was quick ;-)  Thanks for the amazing work.


fix: authentication flow for JWT tokens

there was an error in the isAuthenticated function which also sent the res.json(...) error response after calling next() without returning from the function
this will fix #3133

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 6 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 22.489%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app.ts
0
6
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3834

Relevant Lines:
18021

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 6 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+10.4%) to 32.938%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app.ts
0
6
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
10.4%

Covered Lines:
3834

Relevant Lines:
12177

💛  - Coveralls


fixed misc issues for web and codebase

Related Task : https://github.com/roots-id/roots-react-native/issues/7
Change Log:

Cleaned up code
Fixed typing issue on web
Fixed navigation architecture

https://user-images.githubusercontent.com/19255438/195727239-d9e60666-609b-469b-8bd1-6a899b29dbfc.mov

Excellent adjustments and additions that will set us up well for our future changes.  Confirmed in android, web, and iOS.  I will need to look into Responsively App :)


SubscaleImageView lib and Android Universal Image Loader lib

Hello,
How I can use Android Universal Image Loader to load image from web into SubscaleImageView
here is link of lib:
https://github.com/davemorrissey/subsampling-scale-image-view

If you can decorate SubsamplingScaleImageView with ImageAware interface then you can pass it into ImageLoader.displayImage(...)


Error

I have an error,
Missing argument 1 for Artisaninweb\SoapWrapper\Service::header(),
Thanks

Can you be more specific? Show us you code?

This happens when you run demo() in the SoapController example directly. In the service you're adding, just comment out the lines where you don't have any optional parameters to add :)

@artisaninweb @Sandldan
Yes comenting out the header is fine, but what if I wanna use header? I have put the params for header, but it say "Missing argument 2 for Artisaninweb/So....Service:header()"
please help, here is my header

$auth_params = new stdClass();
$auth_params->userid = $this->userid;
$auth_params->password = $this->password;
	$header_params = new SoapVar($auth_params, SOAP_ENC_OBJECT);
	$this->header = new SoapHeader($this->appName, 'UserCredentials', $header_params, false);


Add Blender Benchmark to Terra

Merged to: https://github.com/juno-fx/Terra-Official-Plugins/tree/pack-additional-software
Closing.


How to specify multiple file path patterns

This is not so much a bug as a request for documentation improvement.
I want to publish the results from "path//*.xml" and "path//*.junit".  I can do either one, but I have not figured out the magic incantation that will get me the results for both.
What
          files: "..."

do I need to use?

Are the double / in your path deliberately?
Try:
with:
  files: |
    path/*.xml
    path/*.junit

Section Configuration mention this multi-pattern syntax.

How did I miss that!?  Thank you so much!


Make dependent images configurable

Describe the feature you would like and why you want it
For closed corporate environments any images requested might need to go through an internal proxy, hence it would be good to be able configure the imagerepo/image required by kuberhealthy (like the gcr pause one).
The chart at https://github.com/helm/charts/tree/master/stable/kuberhealthy should take parameters to be able to point at these.
Additional context
See https://github.com/Comcast/kuberhealthy/issues/114 for background.

I've pushed an image tag for you to test with to  ds-image-override.
I've added this feature as an argument dsPauseContainerImageOverride - If you add this argument to your running kuberhealthy deployment at deployment.spec.template.spec.containers.args you should be able to specify the location of the pause container image that the daemon set checker deploys.
Ex:
spec:
  template:
    spec:
      containers:
        args:
        - "-dsPauseContainerImageOverride"
        - "your-docker-repo/pause:0.8.0"

Which image tag should I use?
Small typo, should be
"your-docker-repo/google_containers/pause:0.8.0"

doh -  found it - ds-image-override

Sorry to disappoint:
kubectl -n kuberhealthy logs kuberhealthy-7fdc478568-pq7v7
time="2019-02-25T23:02:04Z" level=info msg="Startup Arguments: [/app/kuberhealthy]"
time="2019-02-25T23:02:04Z" level=info msg="Starting web services on port :8080"
time="2019-02-25T23:07:24Z" level=info msg="I am now master. Starting checks."
time="2019-02-25T23:07:24Z" level=info msg="Became master. Starting checks."
time="2019-02-25T23:07:24Z" level=info msg="Running check: PodStatusChecker namespace kube-system"
time="2019-02-25T23:07:24Z" level=info msg="Running check: ComponentStatusChecker"
time="2019-02-25T23:07:24Z" level=info msg="Running check: DaemonSetChecker"
time="2019-02-25T23:07:24Z" level=info msg="Running check: PodRestartChecker namespace kube-system"
time="2019-02-25T23:07:24Z" level=info msg="Searching for unique taints on the cluster."
time="2019-02-25T23:07:24Z" level=info msg="Found taints to tolerate: [{dedicated  infra NoSchedule <nil>}]"
time="2019-02-25T23:07:24Z" level=info msg="Generating daemon set kubernetes spec."
time="2019-02-25T23:07:24Z" level=info msg="Deploying daemon set with tolerations:  [{dedicated  infra NoSchedule <nil>}]"
time="2019-02-25T23:07:24Z" level=info msg="Setting state of check ComponentStatusChecker to true []"
time="2019-02-25T23:07:24Z" level=error msg="Failed to create daemon set:Internal error occurred: admission webhook \"trust.hooks.securityenforcement.admission.cloud.ibm.com\" denied the request: \nDeny \"gcr.io/google_containers/pause:0.8.0\", no matching repositories in ClusterImagePolicy and no ImagePolicies in the \"kuberhealthy\" namespace"
time="2019-02-25T23:07:24Z" level=error msg="Something went wrong with daemonset deployment, cleaning things up..."
time="2019-02-25T23:07:24Z" level=info msg="DaemonSetChecker removing 0 daemonset pods"
time="2019-02-25T23:07:24Z" level=info msg="DaemonSetChecker removing daemonset"
time="2019-02-25T23:07:24Z" level=error msg="Failed to delete daemonset:daemonsets.extensions \"daemonset-test-kuberhealthy-7fdc478568-pq7v7-1551135724\" not found"
time="2019-02-25T23:07:24Z" level=info msg="Setting state of check PodRestartChecker namespace kube-system to true []"
time="2019-02-25T23:07:24Z" level=error msg="Error running check: DaemonSetChecker Internal error occurred: admission webhook \"trust.hooks.securityenforcement.admission.cloud.ibm.com\" denied the request: \nDeny \"gcr.io/google_containers/pause:0.8.0\", no matching repositories in ClusterImagePolicy and no ImagePolicies in the \"kuberhealthy\" namespace"
time="2019-02-25T23:07:24Z" level=info msg="Setting state of check PodStatusChecker namespace kube-system to true []"
time="2019-02-25T23:09:24Z" level=info msg="Running check: PodStatusChecker namespace kube-system"
time="2019-02-25T23:09:24Z" level=info msg="Running check: ComponentStatusChecker"
time="2019-02-25T23:09:24Z" level=info msg="Setting state of check ComponentStatusChecker to true []"
time="2019-02-25T23:09:24Z" level=info msg="Setting state of check PodStatusChecker namespace kube-system to true []"

pod:
...
containers:
  - args:
    - -dsPauseContainerImageOverride
    - fsnexus.evry.com:8085/google_containers/pause:0.8.0
    env:
    - name: POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    - name: POD_NAMESPACE
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.namespace
    image: fsnexus.evry.com:8085/comcast/kuberhealthy:ds-image-override
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 3
...

Ah, my mistake,  you'll also have to specify the command entry point - see below:
containers:
  - args:
    - -dsPauseContainerImageOverride
    - fsnexus.evry.com:8085/google_containers/pause:0.8.0
   command:
   - /app/kuberhealthy
    env:
    - name: POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    - name: POD_NAMESPACE
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.namespace
    image: fsnexus.evry.com:8085/comcast/kuberhealthy:ds-image-override
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 3
...```

Nice - that seems to work.
Next now is that the spawned DS should be a bit more configurable too, due to restrictive PSP:
vents:
  Type     Reason     Age                  From                   Message
  ----     ------     ----                 ----                   -------
  Normal   Scheduled  11m                  default-scheduler      Successfully assigned kuberhealthy/daemonset-test-kuberhealthy-6bf769c4d8-469rq-1551216695-8jsxz to <IP_ADDRESS>
  Normal   Pulling    11m                  kubelet, <IP_ADDRESS>  pulling image "fsnexus.evry.com:8085/google_containers/pause:0.8.0"
  Normal   Pulled     11m                  kubelet, <IP_ADDRESS>  Successfully pulled image "fsnexus.evry.com:8085/google_containers/pause:0.8.0"
  Warning  Failed     9m6s (x12 over 11m)  kubelet, <IP_ADDRESS>  Error: container has runAsNonRoot and image will run as root
  Normal   Pulled     74s (x48 over 11m)   kubelet, <IP_ADDRESS>  Container image "fsnexus.evry.com:8085/google_containers/pause:0.8.0" already present on machine

does it really require to run as root - and why?

Great, progress!
Is it reporting that the pause container is running as root?
The pause container doesn't do anything at all, it just sits and waits for an interrupt signal.  I'll work on configuring it to run as a non-root user by default since we should be doing that anyway.

I've updated the pause container to run as a non-root user in the daemon-set.  If you re-pull the image you should see that change.

We have a winner!
time="2019-02-27T13:42:30Z" level=info msg="Setting state of check DaemonSetChecker to true []"

Thanks a lot for all your fixes!
Will this be merged to master and a release made? I can make a PR for the chart when you have it out.

Awesome! Thanks for working through that with me.
I've cut v1.0.1 for these series of fixes and will be merging these changes into that release and master after tidying things up and adding documentation.
I'll reference this issue in the PR so you'll see it. I should have it merged in later today.

1.0.1? or 1.0.2? Since 1.0.1 already exists: https://quay.io/repository/comcast/kuberhealthy?tag=latest&tab=tags

You're correct, v1.0.2.

OK - I'm ready when you are: https://github.com/helm/charts/compare/master...davidkarlsen:fixKuberHealthy

Release cut, and we checked out your charts diff - looks good.

Closing issue since this is released.


Elasticache provider does not populate connection secret

What happened?
While creating a new resource of kind Cluster with apiVersion elasticache.aws.upbound.io/v1beta1, the provider does not populate the secret from the writeConnectionSecretToRef section. The secret is created but is empty.
How can we reproduce it?
apiVersion: elasticache.aws.upbound.io/v1beta1
kind: Cluster
metadata:
  annotations:
    meta.upbound.io/example-id: elasticache/v1beta1/cluster
    uptest.upbound.io/timeout: "3600"
  labels:
    testing.upbound.io/example-name: redis-cluster
  name: redis-cluster
spec:
  forProvider:
    engine: redis
    engineVersion: "7.1"
    maintenanceWindow: sun:05:00-sun:09:00
    nodeType: cache.t3.micro
    numCacheNodes: 1
    parameterGroupName: default.redis7
    port: 6379
    region: eu-west-1
    securityGroupIds:
      - "sg-XXXXXXXXXXXX"
    subnetGroupName: "vpc-elasticache-subnet-group"
  writeConnectionSecretToRef:
    name: redis-cluster-connection
    namespace: sandbox

kubectl describe secret redis-cluster-connection --namespace sandbox
Name:         redis-cluster-connection
Namespace:    sandbox
Labels:       <none>
Annotations:  <none>

Type:  connection.crossplane.io/v1alpha1

Data
====

NAME                       TYPE                              DATA   AGE
redis-cluster-connection   connection.crossplane.io/v1alpha1   0      19h

What environment did it happen in?
Crossplane version: 1.15.1

Cloud provider : AWS
Kubernetes version : 1.28
Kubernetes distribution : AWS EKS
ArgoCD version : v2.10.6+d504d2b

@lefredlebel did you solve the problem? I have the exactly same question.

@lefredlebel Same here, I am having this issue as well. How did it get solved?

@lefredlebel still seeing this same issue, was it resolved? If so how?


notmuch: 0.29.2 -> 0.29.3

Motivation for this change
Minor update according to https://notmuchmail.org/news/release-0.29.3/
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

/nix/store/7k3asg87azn9aa9d01qabca3kj49382r-notmuch-0.29.2	 417.8M
/nix/store/f9kbw5cy4x6mk51vaqy7sqh1w7j8a65s-notmuch-0.29.3	 417.8M
14 package built:
aerc afew alot astroid gmailieer muchsync neomutt notmuch notmuch-addrlookup notmuch-mutt python27Packages.notmuch python37Packages.notmuch python38Packages.alot python38Packages.notmuch
I "ran" all of them, except the pythons packages. By "running" I mean only with -h to see that they at least start.

thanks!


It's caching the extension

Summary
Vite is caching the extesion, how do I disable this?

What version of Vite are you using?
What directory is vite caching the build output to?


Code splitting

Is your feature request related to a problem? Please describe.
No, it's not a problem but it would be good to have as our codebase is increasing.
Describe the solution you'd like
Split the code based on router and lazy load other routes than "Home" so its performance can be a boost. It'll be great for low internet speed users.

I would like to get assigned this to me.

Please speak to @jeremyphilemon before you pick this up for development.

Routing scheme -

Demographics and Deep dive will have their own separate chunk.
The rest all will be in one main chunk.

Implementation -
The react Suspense and lazy will be used to achieve this.
@jeremyphilemon can I start working on this?


Upload Functionality added

Created form at <IP_ADDRESS>:8000/trial/, that stores the uploaded file at src/server/submissions

Merged manually. Thanks for the PR. Also, join the Telegram group at https://t.me/joinchat/AAAAAEH8f4dUqtP67SeMDQ


tractability data on QA 19.04 seems to be missing buckets for small molecules

LRRK2 has tractability data for both SM and Ab on production https://www.targetvalidation.org/target/ENSG00000188906
but only Ab (antibody) on QA
https://qa.targetvalidation.org/target/ENSG00000188906)
Missing "small molecules" data whenever tractability data is displayed in the Open Targets Platform i.e.

results of batch search
target profile page
prioritisation view in the disease association page

Should have been in Platform, not Genetics. Thanks @edm1 for catching this.


For translations, can you make the change on crowdin cf How to get started ~ Direct link crowdin protonmail ?
We auto pull translations from crowdin, so once the change is available there, we will be able to have it inside the next release, here the file inside src/i18n and *.po are only copy from crowdin.
Thx


python310Packages.recurring-ical-events: 2.0.1 -> 2.0.2

Description of changes
Diff: https://github.com/niccokunzmann/python-recurring-ical-events/compare/v2.0.1...v2.0.2
Changelog: https://github.com/niccokunzmann/python-recurring-ical-events/blob/v2.0.2/README.rst#changelog

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 217438 run on x86_64-linux 1

7 packages built:

calendar-cli
gtg
home-assistant-component-tests.caldav
python310Packages.caldav
python310Packages.recurring-ical-events
python311Packages.caldav
python311Packages.recurring-ical-events


More accurate device recognition

We should look into libs to more accurately get the users current device.

https://github.com/kaimallea/isMobile
http://hgoebl.github.io/mobile-detect.js/


BUG: onyo mving a dir into a nonexistent dir results in (odd) error

The source directory exists, but none of the destination directories exist. I do think that onyo should error here, as the parents do not exist. Onyo does error, but the message printed is incorrect/doesn't make sense.
(onyo) aqw@hrududu in /tmp/yope on git:master
❱ onyo mv dp/Alex\ Waite does/not/exist/
ERROR: Cannot rename /tmp/yope/dp/Alex Waite -> /tmp/yope/does/not/exist. Consider moving instead.

vs
❱ onyo mv dp/Alex\ Waite/ does/not/exist/Alex\ Waite/
ERROR: Destination is not an inventory directory: /tmp/yope/does/not/exist

Linking #420, since this is essentially the same problem


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_98b26753-3843-4476-898d-87bc2107f615/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_98b26753-3843-4476-898d-87bc2107f615.git

Docs Build status updates of commit 05eb606:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/opstest2/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Is there a upper limit for the No. of constraints or objective functions?

For my optimization problem, the NSGA-II worked very well when I have 2 objective functions and 3 constraints. However, when I enlarge the number of constraints to more than 10 or even over 20, I encountered a memory allocation error in multiprocessing, which I'm now trying to figure out.
In this issue, I want to ask if there is an upper limit for the No. of constraints. I believe that the answer may be algorithm dependent. From the documentation, I learned that there are multi-objective optimization algorithms and many-objective optimization algorithms, though I haven't found comparisons of them in the documentation.
Then, instead of testing all existing algorithms, is there any general rule to select certain algorithm according to this criteria, i.e., maximum No. of constraints? Or is it better to test through all algorithms? Thanks!

All algorithms in pymoo use the feasibility first principle for constraint handling. For very restrictive constraints, this can become an issue. There is quite a bit of research on how environmental survivals can be modified (eps-constraint, for instance) to allow some amount of feasibility.
Such modifications are not available yet in the current pymoo release, though. The memory error for constraints shall not be related to pymoo itself. For the algorithms the aggregated constraint violation is used, which is the sum of violated constraints for each solution.

All algorithms in pymoo use the feasibility first principle for constraint handling. For very restrictive constraints, this can become an issue. There is quite a bit of research on how environmental survivals can be modified (eps-constraint, for instance) to allow some amount of feasibility.
Such modifications are not available yet in the current pymoo release, though. The memory error for constraints shall not be related to pymoo itself. For the algorithms the aggregated constraint violation is used, which is the sum of violated constraints for each solution.

Thank you for the explanations! I have resolved the memory error by setting save_history=False and save the optimization history in Callback. Deep copies of optimization history turns out to accumulate to a large memory consumption.
I have noticed that pymoo tends to first find the feasible solutions that have zero CV and then optimize the objective functions. From your explanation,  I will take relatively less restrictive constraints.
Also, since the aggregated constraint violation is used, I found that solution with unbalanced but minimal CV could be chosen as the opt. While the solution with more even but larger CV was dropped. In this case, I'm trying to add penalty to the unbalanced solutions by defining constraints with squared errors instead of absolute errors. Appreciate it if you got more suggestions!


Can tab through notebook when it's in the background

Open a notebook
Switch to a text editor tab
Enable "tab moves focus mode"
Tab through the UI. After the status bar, the focus disappears. Check with devtools, see that focus is on notebook toolbars

@amunger not sure if this is the same issue, but the tabbing seems super random and does go into the notebook cell:
https://github.com/microsoft/vscode/assets/54879025/0bc49f4b-43d8-42a9-a38c-d8e8ac346188

It's separate, and I think that's the expected behavior: It's navigating among different toolbars, and once focused in a toolbar, you can use arrow keys to navigate. It jumps to that particular cell since that's where you were previously focused (I assume)

@amunger the focus still gets stuck in the notebook when I'm in tab moves focus mode.

@meganrogge - what do you mean it gets stuck? Do you have repro steps? That sounds different than what this issue was for.


When opening a settled bet with 0 shares, a red box with the error message "Data column(s) for axis #0 cannot be of type string" shows.

Fixed, but the Javascript code might still be in your browser cache.


Making memdisk.py python3 and python2 compatable

Archlinux by default users python 3+ this causes issues with the memdisk.py script i have modified the script slightly so that it is compatable with python 2.x and 3.x to hopefully resolve some make errors with less pain i have tested the change on an Archlinux and Centos server with positive results.
Before:
python -V ->
Python 3.5.2

python src/memdisk/memdisk.py ->
    print "Renaming " + osx_dmg + " => " + image
                    ^
SyntaxError: Missing parentheses in call to 'print'

python2.7 -V ->
Python 2.7.12

python2.7 src/memdisk/memdisk.py ->

After:
python src/memdisk/memdisk.py ->

Happy to answer any questions if needed :)
Thanks for the great work guys im just staring out in unikernels hope i have more pulls to come :D

ok to test

Hi @setkeh thanks! Let us know if there's anything we can help you with to get started :-)

Thanks @alfred-bratterud I'll surely post if I get stuck :D

ok to test

Im not entirely sure that the changes i made relate to Unit tests & Miscellaneous failing the Exact error is
+ cd test
+ python test.py -t miscellaneous
Test specified is not recognised, exiting
Build step 'Execute shell' marked build as failure

If im wrong im happy to investigate further :D

Hi @setkeh could you redirect this PR to our dev branch? This would likely make the missing test pass and we'll merge :-)

Sure thing @alfred-bratterud all done now :)


Some desc_short of materias still missing

Hi aEnigma,
Your last DM version holds most of the desc_short fields for materias, but there are still some missing.
The Astrals' Protection (504231800), Mark of the Glacian (504231812) are among them. Only a very few are still missing (at least among those having translations in all languages).
Can you have a look at them ?

Both entries (MST_MATERIA_SHORTDESCRIPTION_504231800 MST_MATERIA_SHORTDESCRIPTION_504231812) are simply missing from the F_TEXT_MATERIA_SHORTDESCRIPTION localization table.

All right, guess I'll update my code to fallback to the long description if short is missing. Thank you for the check.


ninja prefix header dependencies ignored

It seems that Ninja builds do not detect changes within files included from prefix headers.
The following report on http://www.cmake.org/Bug/view.php?id=1260#c31218 might be expressing the same thing concerning cotire: "...all the solutions mentioned above do not account for the fact that when using the ninja generator, the generated gch in the gcc builds doesn't have any dependency tracking, so if your pch includes some headers, and you alter one of them, the target won't get recompiled at all."
Here is a test case...
CMakeLists.txt is
cmake_minimum_required(VERSION 2.8)
project(test)
set(CMAKE_MODULE_PATH "${CMAKE_SOURCE_DIR}/CMake")
include(cotire)
set_directory_properties(PROPERTIES COTIRE_ADD_UNITY_BUILD FALSE)
add_executable(test stdafx.cpp main.cpp test1.cpp)
set_target_properties(test PROPERTIES COTIRE_CXX_PREFIX_HEADER_INIT "stdafx.h")
cotire(test)

h2.h is
#ifndef H2_H
#define H2_H
#define A 10
#endif

stdafx.h is
#ifndef STDAFX_H
#define STDAFX_H
#include "h2.h"
#define B A
#endif

stdafx.cpp is
#include "stdafx.h"

main.cpp is
#include "stdafx.h"
void test1();
int main() {
	test1();
	return B;
}

test1.cpp is
#include "stdafx.h"
#include <stdio.h>
void test1() { printf("T1: %d\n", B); }

Observe results where touching h2.h does not update the build (at least when using Ninja):
$ cmake -G NInja ..
-- The C compiler identification is GNU 4.8.1
-- The CXX compiler identification is GNU 4.8.1
-- Check for working C compiler using: Ninja
-- Check for working C compiler using: Ninja -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler using: Ninja
-- Check for working CXX compiler using: Ninja -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- cotire 1.5.1 loaded.
-- CXX target test cotired without unity build.

This was tested on Ubuntu 13.10, cmake <IP_ADDRESS>, ninja 1.3.4.  It seems to work fine though on make and MSVC generators.

I think there should be a note about this in the readme file. The readme just says that cotire supports ninja, but since dependency detection doesn't actually work you get some really strange compiler errors if you change a header which is precompiled.


Update createUiDefinition.json

Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

Hi @haneuvir,
Can you please fix the validation failures, and also, I could see that the folder structure we follow is somewhat different. Can you please confirm how you are packaging it and if possible, can you maintain this structure.
Thanks

Hi @haneuvir,
We can close this PR as you have raised a new PR with validation failure fix.
Thanks


Barmalini improvements

Barmalini is a local meme — an anonymous user that anyone (well, some) has access to.
This PR solidifies this in the codebase, adding some sensible restrictions:

Any user with full rights has access to barmalini.
There is no single barmalini password
Users can generate a temporary (1 hour) barmalini password
Any Barmalini session is capped at 1 hour
Barmalini rights are capped below first negative tier (10 minutes slow mode, no invites, no voting)
It's impossible to reset barmalini password

Mini demo:

@4vanger, thanks for the review. Addressed review comments, please take another look if you have time, otherwise I'll just merge it.


[Slider] Allow mobile VO users to interact with Sliders

[x] I have followed (at least) the PR section of the contributing guide.

Closes #23506
Preview: https://deploy-preview-23902--material-ui.netlify.app/components/slider/#vertical-sliders
a11y snapshot changes: https://github.com/eps1lon/mui-scripts-incubator/pull/1468/files

Also: Could you share how you verified that this approach works? A codesandbox and testing instructions would be ideal. If you don't know how to use this change in a codesandbox you should check out How can I use a change that wasn't released yet?

Could you clean up the changes to the test files so that it's obvious what is new and what changed. So far it looks like a pretty big breaking change.

Hi @eps1lon, Happy to try and clean up the test file a bit. The issue I ran into and discussed with @oliviertassinari (see here https://github.com/mui-org/material-ui/issues/23506#issuecomment-739254631) and why the test file ended up looking the way it does was because with this new approach the browser now handles all of the keyboard interactions. The browser swallows these keyboard events and updates the value accordingly. So triggering them in test or even through the console in browser has no effect.
The approach we decided on for the test file was to remove the tests that were testing keyboard interactions since that would be re-testing the actual browser, and ended up not being possible because of how the browser handles these interactions. In doing so we discovered that some of those tests were also testing other things, so I broke those out, moved them under their appropriate prop's describe section in the test, and then adjusted the tests to not rely on the keyboard since that no longer works.
Let me know if you have a suggestion on how to revise this. Thanks.

Also: Could you share how you verified that this approach works? A codesandbox and testing instructions would be ideal. If you don't know how to use this change in a codesandbox you should check out How can I use a change that wasn't released yet?

Here is the code sandbox with a very simple example https://codesandbox.io/s/material-ui-issue-forked-q7bh2, I can add a few different variations if you'd like but I tested it out on all of the slider examples present in the docs and it worked really nicely.

Visit the above sandbox on a mobile phone ( I only have an iphone X so that is what I used)
Enable VO in settings (you can enable triple tap to enable which I use to make it easier to enable)

Accessibility -> VoiceOver -> Enable

Travel to the slider by swiping right
once on the slider it will read "Swipe up or down with one finger to adjust the value"
you will see the slider move as you swipe up and down and hear feedback about the current value

It's a bit unfortunate that we have to change the internals now but that was something I should've pushed more during the initial review. Thanks for the work and fixture. I'll test this over the weekend to make sure we're not failing other screen readers.
Once that's done I'll prepare some migration instructions for tests. Last time we changed the public testing approach (on Select) we got quite a bit of issues so I want to make sure we're prepared for that.

Some results from our automated a11y tests:

NVDA still produces the same output on rudimentary keyboard navigation :+1:
changes to the produced AOM:

aria-disabled is now properly picked up. Was probably a bug in Chrome since role=slider does support aria-disabled
aria-orientation is ignored. Might be a bug in Chrome since role=slider does support aria-orientation and input[type="range"] maps to role="slider"

axe-core (these are old issues flagged under a different rule):

cannot deal with scientific notation in min and max (https://deploy-preview-23902--material-ui.netlify.app/components/slider/#small-steps) and flags these as invalid attributes
It probably reads the attributes not the properties since the AOM does convert them to numbers (hello, IEEE 754)

So we should check if the vertical slider is still supported. Could you add one to your fixture (https://codesandbox.io/s/material-ui-issue-forked-q7bh2) and test if VO is recognizing it as a vertical slider? Be sure to also check if it worked prior to this PR.

Re: slider orientation
It looks like there are a lot of conflicting options some of which are non-standard and some of which are deprecated. So I think that could be an entire pr of its own.
firefox has: orient={orientation}
webkit has: '-webkit-appearance': 'slider-vertical',
and then there is also 'writing-mode': 'bt-lr',
So I think it would be best to hold off if you are comfortable with that. It does seem to still work with VO and changing the value as expected for a non-visual users as is. https://codesandbox.io/s/material-ui-issue-forked-q7bh2
As for

But if you're using a slider and restrict the supported arrow keys to the orientation then the new implementation is misleading.

I'm not even sure you would be able to do that since the those interactions are currently highjacked by the browser, but I guess anything is possible, so some documentation couldn't hurt.

@CodySchaaf I have rebased on HEAD to fix the conflict with #23974

It looks like there are a lot of conflicting options some of which are non-standard and some of which are deprecated. So I think that could be an entire pr of its own.

Generally, no. If a PR regresses on certain behaviors then the PR should handle those. In this specific instance I would agree since we want to add some documentation around it and investigate how different browsers/screen readers work.

I'm not even sure you would be able to do that since the those interactions seem to be highjacked by the browser, but I guess anything is possible, so some documentation couldn't hurt.

I would hope that they just work like any other keyboard events in that the change is the default behavior and you can event.preventDefault() it. I don't know if we respect event.defaultPrevented in our key handler so that's definitely something I want to check first. Not that the new implementation blocks a possible feature that we do want to get in.
If you are on a deadline and don't care about vertical orientation then I would recommend you cherry-pick this change into a separate fork. We need to review it a bit more before we can merge it with confidence.

Oh no I didn't mean to try and rush this, I just thought that is what you were suggestion. Happy to keep trying to help.
I was not comfortable with the things I had tried to add to fix this. I ended up with similar results as to what you see here: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/range#Putting_it_all_together
On chrome it ends up reversing the arrow keys so right -> decrease / left -> increase which I don't think is desirable. As well as the console actually shows the property as -webkit-appearance: slider-vertical; with it striked through even though it still clearly has an effect when you toggle it on and off.
Sort of seems like they don't want us to use that since it is non-standard. Let me know if you have any additional ideas or if I should keep investigating. Thanks for all your testing!

I was not comfortable with the things I had tried to add to fix this. I ended up with similar results as to what you see here: developer.mozilla.org/en-US/docs/Web/HTML/Element/input/range#Putting_it_all_together

They even have a whole section. I didn't see that :+1: . And here I was thinking appearance: slider-vertical was clever :grin:

The bug on Chromium was confirmed 🙃. Is the next step to add more documentation under https://next.material-ui.com/components/slider/#accessibility?

Is the next step to add more documentation under next.material-ui.com/components/slider/#accessibility?

Here are the items I wanted to check:

Can we restrict the arrow keys to the ones matching the orientation and was this possible before?
Does VO announce the orientation?

I have resolved the conflict on HEAD.

@eps1lon react-aria has released a slider component: https://react-spectrum.adobe.com/react-aria/useSlider.html. They went in the same direction this PR is pushing. However, no specific care for the announcement seems to have been done.

However, no specific care for the announcement seems to have been done.

What makes you say that?

They seem to have used aria-orientation="vertical" as recommended by WAI-ARIA, I couldn't find more logic. I could have missed something.

They seem to have used aria-orientation="vertical" as recommended by WAI-ARIA, I couldn't find more logic. I could have missed something.

Would you agree that it's possible that they're not aware of this bug or worked around it in another form (e.g. appearance: vertical-slider;)?

@eps1lon Agree, I was merely trying to see if we could extra some information from this effort.

Announcement is now fixed on VoiceOver+(safari,chrome) and JAWS+chrome (jaws+(ie11,edge) was already working) by adding -webkit-appearance: slider-vertical.
On VoiceOver we still have the focus indicator on the hidden input instead of the thumb. Looking at that next.

Restored the old focus indicator behaviour mentioned in https://github.com/mui-org/material-ui/pull/23902#issuecomment-751698160.
I would consider these visuals problematic since the indicator does not updated its position when the value changes. The problem here is that VO assumes the role="slider" is the full widget like input[type="range"]. In that scenario it wouldn't need to update the position since the widget should not change position. Only the thumb changes position.
I had a fix locally:
I'm not applying it since that would change previous visuals and in this PR we just want to fix VO behaviour on iOS.

It also looks like we miss a test case, see the following regression. When we click on the rail, an error is thrown

On a discrete slider, yes.
So there are two issues to investigate:

Why does the demo not crash
Why does the discrete slider not work

Fixed https://github.com/mui-org/material-ui/pull/23902#pullrequestreview-559177627 in 42ba74b (#23902)

We need to update the Airbnb demo to forward the children deploy-preview-23902--material-ui.netlify.app/components/slider/#customized-sliders and we should be good, I can't find anything else .

I hope this is caused by a different change I ultimately didn't ship because I thought it wasn't necessary. Will take a look tomorrow.

We need to update the Airbnb demo to forward the children deploy-preview-23902--material-ui.netlify.app/components/slider/#customized-sliders and we should be good, I can't find anything else .

Fixed in 4f9c003 (#23902)
I don't like the new requirement since it's easy to get wrong. It should be impossible to remove the input i.e. effectively remove slider behavior.
I'll follow-up with a different approach with the goal of matching VoiceOver's focus indicator for input[type="range"] while making sure input[type="range"] will always be rendered. Probably going to ask the folks over at react-aria what their conclusion was regarding the focus indicator. I suspect they missed it because the (IMO currently broken indicator) only appears with certain values depending on the orientation.

Putting on hold because keyboard navigation is reversed for the vertical slider when using horizontal keyboard arrows (ArrowLeft and ArrowRight). See https://deploy-preview-23902--material-ui.netlify.app/components/slider/#vertical-sliders and https://github.com/eps1lon/mui-scripts-incubator/pull/1468/files#diff-e67a117eb1ef378927f4c4122e1409650751a063e7e7ea86cf575fee7ea19d17L206-R232

@eps1lon is this a bug in the implementation of -webkit-appearance?

Going to revert the appearance (adjusting the test accordingly) and add to the documentation possible workarounds with different tradeoffs for https://bugs.chromium.org/p/chromium/issues/detail?id=1162640&q=input range appearance&can=2 and https://bugs.chromium.org/p/chromium/issues/detail?id=1158217&hotlist_id=8815&sort= rank -ID

Going to revert the appearance (adjusting the test accordingly) and add to the documentation possible workarounds with different tradeoffs for https://bugs.chromium.org/p/chromium/issues/detail?id=1162640&q=input range appearance&can=2 and https://bugs.chromium.org/p/chromium/issues/detail?id=1158217&hotlist_id=8815&sort= rank -ID

@CodySchaaf Thanks for the work and explanation :+1: . Really glad we can use native elements and contribute some bugs to browser vendors.

@CodySchaaf Thanks for the work and explanation :+1: . Really glad we can use native elements and contribute some bugs to browser vendors.

Thanks so much @eps1lon for getting this across the finish line. It was great working with you all!

Thanks so much @eps1lon for getting this across the finish line. It was great working with you all!


Print all errors returned by the Percy API

This prevents api response errors from being hidden when looking for response[data] when it doesn't exist.  It catches the error earlier, and raises it.
This is perhaps an interim solution to getting all errors logged correctly.  Later we may want to add some retries for specific types of errors.
Thanks @criddyp for the original commit on this.

A good interim solution that exposes more info rather than just dying. Later on, we'd want to replicate the behavior of the other client libs to actually swallow the errors, log them out as warnings, and disable Percy internally without raising an exception so that CI suites aren't affected.


Please do not include binaries in repos, just provide build instructions. Use Releases for binaries.

Please do not include binaries in repos, just provide build instructions.

When checking out the repo, the binaries are wasting space being a binary-blob which cannot be diff'd by git. Please consider placing binaries in the GitHub's Releases.
The binary for amd64 linux for v1.0.4 has single finding of a "trojan" by a scanner I've not heard of. But when I build from source on Debian with Go 1.21 from backports, the build is clean.

NOTE: I would be worthwhile To clean up the previous check-ins so the future checkout will not be burdened with binary blobs through v1.0.4, you'll likely have to due some pruning and such. Then again, you could leave it as-is and just not include binaries, as the project's release page has just the source code.
Here's what I did on my Debian to make it:
git clone https://github.com/teacat/chaturbate-dvr  # and wait a while due to binary blobs
sudo apt install -t bookworm-backports golang-go    # due to default golang is currently 1.19, we need 1.21 in backports
apt policy golang                                   # to see our golang release
cd chaturbate-dvr
rm -rf bin                                          # remove existing binaries
                                                    # To set GOOS GOARCH, it's a quick 'uname' shell test for linux & macos
GOOS=linux GOARCH=amd64 go build -o chaturbrate-dvr # no need for me to put in the bin path.

For those looking to use this open source code, always read the source code. This go.mod uses well known Golang librarys directory from github.com and golang.org. If you get this code or binary elsewhere, you might get a little something undesirable. And always check a binary against virustotal.

The scanner result you've linked (with my build) shows it was passed, perhaps it's just a temporary false warning.

Though sometimes I use upx to compress the binaries which might be false positive, then I checked README_DEV.md and realized that I hadn't used it for chaturbate-dvr 💀
But- yea, I shall move binaries to Release in the next update.


[WIP] Fix formatting tests

For #9968

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[x] Has sufficient logging.
[ ] Has telemetry for enhancements.
[x] Unit tests & system/integration tests are added/updated.

Codecov Report

Merging #10801 into master will decrease coverage by 60.64%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #10801       +/-   ##
===========================================
- Coverage   60.64%    0.00%   -60.65%
===========================================
  Files         583       10      -573
  Lines       31558       32    -31526
  Branches     4488        4     -4484
===========================================
- Hits        19137        0    -19137
+ Misses      11449       32    -11417
+ Partials      972        0      -972

Impacted Files
Coverage Δ

src/client/constants.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

src/client/debugger/constants.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

src/client/common/process/constants.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

src/client/common/platform/constants.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

src/client/interpreter/locators/services/conda.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...t/datascience/jupyter/jupyterDataRateLimitError.ts
0.00% <0.00%> (-50.00%)
:arrow_down:

...er/jupyterInterpreterSubCommandExecutionService.ts

src/client/datascience/activation.ts

src/client/common/terminal/service.ts

...ent/common/application/webPanels/webPanelServer.ts

... and 569 more

Continue to review full report at Codecov.

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


LTA translation update.

Corrections made.

There are conflicts in PR, so I will upload jtlng_lta to master


Idea/proposal for router aliases

Aliases for routes are popular function of laravel routing, but current usage like a monster. As example:
// Without alias
Route::get('/home', 'HomeController@index');

// With alias
Route::get('/home', ['as' => 'home', 'uses' => 'HomeController@index']);

What you think about additional dsl-syntax for aliases? As example:
// Variant 1
Route::get('/home', 'home:HomeController@index');

// Variant 2
Route::get('/home', 'home#HomeController@index');

// Another....
// ?

//Variant 3
Route::get('/home', 'Home@index', 'home');

UPD: Laravel has method name:
Route::get('/home', 'HomeController@index')->name('home');

But this method has no in official documentation. I think this example must be added in http://laravel.com/docs/5.1/routing#named-routes

I'd just keep it like is, but add the example with ->name() to the documentation. Adding it to the dsl-syntax will only complicate stuff and it'd become less readable. However, if there were to be made any modifications in the dsl-syntax, I'd propose the route name to be added at the back somewhere, it makes more sense to me and is more readable.
// Variant 1
Route::get('/home', 'HomeController@index:home');

// Variant 2
Route::get('/home', 'HomeController@index#home');

:-1:
This way looks confusing, less intuitive and gives no real extra benefits.
What's wrong with Route::get('home', 'HomeController@index')->name('home');?

I agree this doesn't need to change.

@GrahamCampbell me agree too. I think need pull request in docs with description for this method. Create?

The docs repo is open to PRs.


Chose background color for editor tabs at Connection level

Hello
I'm using Version 7.2.0 and I would like to color my tab with different colors, in order to easily find which are for Dev and which are for Prod.

I found the Connection type option, but it seems to work only in the connection list, the resultsets and so on, but not on the editor tabs

In the prefernces there is a Color section, but I can't find the option to set them in a different way to a specific connection.

Is there any way to do it? If not by color, is there any other smart way to easily find the tab you are looking for, especially when you open 20 at the same time like I do? :smile:
Thanks

Add a connection type color to SQL Editor tabs sounds good. Thank you for the suggestion.

Add a connection type color to SQL Editor tabs sounds good. Thank you for the suggestion.

Found that the ticket duplicates https://github.com/dbeaver/dbeaver/issues/8052. Let only one remains opened

Found that the ticket duplicates https://github.com/dbeaver/dbeaver/issues/8052. Let only one remains opened


Added C#, NodeJS, and Phoenix/Elixir instructions

Added C# & NodeJS instructions

@gramian I have no idea how to use GitHub for things like this 😊.
However, I did my best and added C#, NodeJS, and Elixir instructions for at least something basic that works. It has taken me days to figure out these basic functions and could save other people the same time in the future with the generic HTTP/JSON API.
Feel free to update or add anything else. I may improve the code as I go further but for now at least these are all working simple illustrations. Thanks.

@lvca LGTM. I think it can be merged now. Thank @jonmdev
If the language examples grow in number, we may need make a HTTP/JSON Examples Section to not overcrowd the menu.

Approved


Fix nested section in documentation

Are you using v1 or v2? Because the existing syntax was correct for v2, and your edits are the syntax for v1.

@vlucas I’m not sure. I’m using the version that ships with Laravel 5.1.*.

I cam here with exactly the same issue as @martinbean, never thought to look at changes in phpdotenv versions, or that laravel might be using an older version.
Laravel Framework 5.1 is still using phpdotenv ~1.0.
It might be worth amending this PR to mention the version 1 syntax along side version 2 - I imagine a lot of developers discovering this project from lumen/laravel.

@vlucas I’m not sure. I’m using the version that ships with Laravel 5.1.*.

Laravel 5.1 uses phpdotenv 1, Laravel 5.2 uses phpdotenv 2.


Check host only ip when ssh_info is ready

Sometimes ssh is not ready then ssh_info is nil.
So, we need to check that.
And I fix a one indentation line.

I test openstack kolla by using vagrant-libvirt.
They use 3 ethernet interface.
( https://github.com/openstack/kolla/blob/master/dev/vagrant/Vagrantfile#L49-L50 )
But, they use same bridge for eth0 and eth2.
So, arp can not address eth0's mac address.
So, I think that is my real problem.


Add NFS Volume Plugin Info to Docs

Now that we have the NFS Volume Plugin committed, we need to edit the Volumes doc page to describe  how to configure and use it. While the Plugin was committed with a pod file example,the example is minorly confusing in that it uses "nfs" as both the volume name and type. I've clarified this by renaming the name as "myshare" in the example, hence the inclusion of the example file in this PR.
Incidentally, the Volumes page is going to become an unnecessarily large if we include the pod example in-line with every plugin description. The NFS description links to the example file instead. I plan to follow this approach for the up-coming docs for Gluster File and Ceph Block.

CLA signed as part of Red Hat

LGTM, thanks @wattsteve! Can we squash commits and we'll merge

@vmarmol commits squashed

Thanks! We'll merge tomorrow when merge hours re-open.


Copy client metadata explicitly

Hi @mwitkow, could you take a look at this? I'm not very familiar with grpc go, but this change seems to allow passing metadata to the backend service. Without it I only see user-agent and content-type.

FYI, metadata handling is also fixed in #16 .