TypeScript Error in /my-awesome-project/src/components/profile/profileCard/profileFormNav/nav/PersonalInfo/PhoneItem/PhoneItem.tsx(34,27)

This is the first time I'm trying to deploy the demo locally, I didn't have a problem with deploying npmfixed branch. Now I'm going to use default branch and after fixing all requirements as described by Altence team,  I get this error after using yarn start command :
Compiled with warnings.

my-awesome-project/src/components/profile/profileCard/profileFormNav/nav/PersonalInfo/PhoneItem/PhoneItem.tsx
TypeScript error in /my-awesome-project/src/components/profile/profileCard/profileFormNav/nav/PersonalInfo/PhoneItem/PhoneItem.tsx(34,27):
No overload matches this call.
  Overload 1 of 2, '(props: { onChange: (value?: E164Number | undefined) => void; value?: E164Number | undefined; country?: CountryCode | undefined; international?: boolean | undefined; ... 4 more ...; smartCaret?: boolean | undefined; } & { ...; } & { ...; }): ReactElement<...>', gave the following error.
    Type '{ disabled: boolean | undefined; className: string; onClick: (() => void) | undefined; }' is not assignable to type 'IntrinsicAttributes & { onChange: (value?: E164Number | undefined) => void; value?: E164Number | undefined; country?: CountryCode | undefined; ... 5 more ...; smartCaret?: boolean | undefined; } & { ...; } & { ...; }'.
      Property 'disabled' does not exist on type 'IntrinsicAttributes & { onChange: (value?: E164Number | undefined) => void; value?: E164Number | undefined; country?: CountryCode | undefined; ... 5 more ...; smartCaret?: boolean | undefined; } & { ...; } & { ...; }'.
  Overload 2 of 2, '(props: StyledComponentPropsWithAs<PhoneInputComponentType, any, {}, never, PhoneInputComponentType, PhoneInputComponentType>): ReactElement<...>', gave the following error.
    Type '{ disabled: boolean | undefined; className: string; onClick: (() => void) | undefined; }' is not assignable to type 'IntrinsicAttributes & { onChange: (value?: E164Number | undefined) => void; value?: E164Number | undefined; country?: CountryCode | undefined; ... 5 more ...; smartCaret?: boolean | undefined; } & { ...; } & { ...; }'.
      Property 'disabled' does not exist on type 'IntrinsicAttributes & { onChange: (value?: E164Number | undefined) => void; value?: E164Number | undefined; country?: CountryCode | undefined; ... 5 more ...; smartCaret?: boolean | undefined; } & { ...; } & { ...; }'.  TS2769

    32 |       ]}
    33 |     >
  > 34 |       <S.PhoneNumberInput disabled={verified} className="ant-input" onClick={onClick} />
       |                           ^
    35 |     </BaseButtonsForm.Item>
    36 |   );
    37 | };

Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.

I would appreciate your attention and response. Thank you.

Hello @kian-ara,
Is it possible that you have deleted original yarn.lock that comes from the repository? If you clone new project looks like there is no error

@kian-ara
fixed this error in #256
soon will be merged to main
closing


ruby runtime improvements

made functions easier to define - now you just need to define the
function like with Python and don't need to wrap it in a class
handler function name is respected and the runtime will now run your
function with that name instead of relying on the harcoded
Kubelessfunction.run to exist
$stdout.sync is set to true so that stdout output is not buffered and
printed straight away
idiomatic improves to the Ruby runtime
add tests for Ruby runtime

NOTE: This is a breaking change to the Ruby runtime, functions will need to be updated. e.g.
class Kubelessruntime
  def self.run(request)
    ...
  end
end

would need to be updated to:
def run(request)
  ...
end

A manual test is required here, since due to #277 we can't test against the controller changes here (specifically the runtime image update).

Thanks @Angelmmiguel! Yeah the failing tests are due to #277, but the kubeless-ruby image needs to be updated before landing


Amend Http2 metrics

Add http2ResponseFlushTime on server side.
Add pendingTasks metric for client and server

@cgtz @jsjtzyy   Addressed your comments:

getNumberOfPendingTasks is moved to Utils.java to make the dependency easier. (RestServer can call it directly)
Gauge registrations are moved to Http2ClientMetrics and NettyMetrics
Server's boss/worker registrations are moved NettyServer, both frontend and storage node can have these metrics.

Codecov Report

Merging #1783 (07ab80d) into master (c64e875) will decrease coverage by 11.68%.
The diff coverage is 17.70%.

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


Breakout for JLink Base Compact

Requirements:

20 pins (2x10) header for connecting with JLink Base Compact (bonus points for Notch)
6 pins REDFIT connector (see SKEDD-jtag+uart)
UART breakout 4 pins 2.54 pitch with pinout: GND - TX - RX - VCC
Optional picoblade connector (see SKEDD-jtag+uart)

Steps:

[ ]  Figure out pinout for Jlink
[ ] Find connectors and foorprints
[ ] Make schematic
[ ] Make layout

Similar to https://www.digikey.co.uk/en/products/detail/olimex-ltd/ARM-JTAG-20-10/3471401 but with a different pin mapping

pins for 6 pins REDFIT connector: SWDIO, SWCLK, RX, TX, GND, VCC


Add text that indicates that you see code by clicking graph

It is not obvious the first time you visit the page that you see the code by clicking the graph

done in #19


[Question] How do I get information back from CMake after configuring a library?

I have a CMake library that conditionally adds link time dependencies based on the output of a check_cxx_source_compiles command.  That's all fine when building a CMake project, but when building a Cargo library I need to add a line like this into build.rs:
println!("cargo:rustc-link-lib=framework=XXX");

To mimic the behaviour of the CMake library, I will need to somehow retrieve the value of the variable that is set by the check_cxx_source_compiles command.  That might not be possible directly, but it should be possible determine the value by reading (in build.rs) the output of the CMake configure command.
Is there a way to go about doing that?  Or more generally, does cmake-rs have a good way to get information back from CMake after the CMake library is configured?

Looks like this is the same problem I ran into here:
https://stackoverflow.com/questions/74851275/rust-cargo-cmake-integration-with-c-library-dependencies
As far as I can tell, this crate is currently only driving the configuration/building process, so it does not have access to any information like that.
I guess in the future, one can imagine parsing the cmake install-config (e.g., https://gitlab.kitware.com/cmake/community/-/wikis/doc/tutorials/How-to-create-a-ProjectConfig.cmake-file) but that is probably a massive undertaking


Support binary quantization

It would be great to support binary quantization in arroy. The main principle is to convert the dimensions values x <= 0 to 0 and x > 0 to 1. This way, we can represent the quantized vector with 32x less space and compute the distances in a much faster and CPU-friendly way. We are currently limited to something like 15M (float 32bit, 768dims) on a 63GiB machine, but with binary quantization, we can go up to 480M vectors on the same machine.
Here is an example of implementing the Euclidean distance with binary data. Here is the formula: $\sqrt{(p1-q1)^2+(p2-q2)^2}$.
This means that computing the difference at the power of two is equivalent to a xor:
$(0-1)^2 = (-1)^2 = 1$
$(1-0)^2 = 1^2 = 1$
$(0-0)^2 = 0$
$(1-1)^2 = 0$
Ultimately, the Euclidean operation is the sum of the XORed dimensions of both vectors squared: $\sqrt{(p1 \bigoplus q1)+(p2 \bigoplus q2)}$. All the necessary operations can be SIMD-optimized or maybe using the u8::BitXor and u8::count_ones methods will be SIMD-optimized by itself 🤔

I would love to see this!
Here is mixedbread.ai talking about the benefits: https://www.mixedbread.ai/blog/binary-mrl


Visualizing components of a vector

I could visualize the magnitude of a vector on Paraview-Visuailzer, but I am wondering how can I see the components of the vector.

The UI is currently behind and prevents you from picking the component otherwise the feature is supported.

Hi Sebastien,
Thank you for your reply. Do you have a time estimate for when this feature
becomes available?
Best regards,
Mehrzad
On Fri, Oct 18, 2019 at 7:41 AM Sebastien Jourdain<EMAIL_ADDRESS>wrote:

The UI is currently behind and prevents you from picking the component
otherwise the feature is supported.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/visualizer/issues/84?email_source=notifications&email_token=AMACZTQQSCFE4EVR7PRDIHDQPHDKTA5CNFSM4JCCYRXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBUWMFY#issuecomment-543778327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMACZTSE3HEVGHDDQJGOEI3QPHDKTANCNFSM4JCCYRXA
.

Unless someone funds us to add that feature, I don't see that feature added any time soon even if it is only a couple of hours worth of work.

Could you please give me an estimate of how much funding you will need to
add this feature to this tool? It is a nice tool and there is a way around
it. However, if the budget is reasonable, I might be able to convince one
of my collaborators to pay for it.
Thank you,
Mehrzad
On Fri, Oct 18, 2019 at 10:06 AM Sebastien Jourdain <
<EMAIL_ADDRESS>wrote:

Unless someone funds us to add that feature, I don't see that feature
added any time soon even if it is only a couple of hours worth of work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/visualizer/issues/84?email_source=notifications&email_token=AMACZTTWTQ3OAHOLH7ZJ3BTQPHUI7A5CNFSM4JCCYRXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBVFFUQ#issuecomment-543838930,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMACZTSB23WMLAVPHSECKOLQPHUI7ANCNFSM4JCCYRXA
.

Our Support entry point is at $2500 which should be enough to add back that feature while maybe have some leftover for other small edits.

Good to know! I will start working on it.
On Fri, Oct 18, 2019 at 10:38 AM Sebastien Jourdain <
<EMAIL_ADDRESS>wrote:

Our Support https://www.paraview.org/services/ entry point is at $2500
which should be enough to add back that feature while maybe have some
leftover for other small edits.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/visualizer/issues/84?email_source=notifications&email_token=AMACZTXMKNQOPLXAOPPHX2LQPHYCRA5CNFSM4JCCYRXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBVI72A#issuecomment-543854568,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMACZTQD2VCKKDVDUBFYOEDQPHYCRANCNFSM4JCCYRXA
.


STOR-858: Bump github.com/openshift/* and k8s.io/*

Bump OpenShift and Kubernetes libraries. @openshift/storage

I don't think this bump can cause the failure but following failure looks kinda genuine:
{  fail [k8s.io/kubernetes@v1.24.0/test/e2e/storage/testsuites/fsgroupchangepolicy.go:134]: while cleanup resource
Unexpected error:
    <errors.aggregate | len:1, cap:1>: [
        [
            {
                msg: "persistent Volume pvc-1421a6ff-62c5-43f5-951a-c0789fa981b5 not deleted by dynamic provisioner: PersistentVolume pvc-1421a6ff-62c5-43f5-951a-c0789fa981b5 still exists within 5m0s",
                err: {
                    s: "PersistentVolume pvc-1421a6ff-62c5-43f5-951a-c0789fa981b5 still exists within 5m0s",
                },
            },
        ],
    ]
    persistent Volume pvc-1421a6ff-62c5-43f5-951a-c0789fa981b5 not deleted by dynamic provisioner: PersistentVolume pvc-1421a6ff-62c5-43f5-951a-c0789fa981b5 still exists within 5m0s
occurred
Ginkgo exit error 1: exit with code 1}

/retest

/retest

/label docs-approved
/label px-approved
This is not user-facing change

Regression test cases passed for Azure-Disk CSI Driver, and do some check on the CSI Driver operator.
/label qe-approved


Execution failed in run-android

Bug description:
I am run:
$ yarn add react-native-webview
$ react-native link react-native-webview
$ react-native run-android
To Reproduce:
In run-android returns this:

Configure project :react-native-webview
:react-native-webview:reactNativeAndroidRoot /home/handover/Documents/handover/tests/paypalRN/node_modules/react-native/android

Task :react-native-webview:compileDebugJavaWithJavac FAILED
/home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewFileProvider.java:3: error: package androidx.core.content does not exist
import androidx.core.content.FileProvider;
^
/home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewFileProvider.java:10: error: cannot find symbol
public class RNCWebViewFileProvider extends FileProvider {
^
symbol: class FileProvider
/home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewModule.java:14: error: cannot find symbol
import androidx.annotation.RequiresApi;
^
symbol:   class RequiresApi
location: package androidx.annotation
/home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewModule.java:15: error: package androidx.core.content does not exist
import androidx.core.content.ContextCompat;
^
/home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewModule.java:16: error: package androidx.core.content does not exist
import androidx.core.content.FileProvider;
^
/home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewModule.java:178: error: cannot find symbol
@RequiresApi(api = Build.VERSION_CODES.LOLLIPOP)
^
symbol:   class RequiresApi
location: class RNCWebViewModule
/home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewModule.java:224: error: cannot find symbol
if (ContextCompat.checkSelfPermission(getCurrentActivity(), Manifest.permission.WRITE_EXTERNAL_STORAGE) != PackageManager.PERMISSION_GRANTED) {
^
symbol:   variable ContextCompat
location: class RNCWebViewModule
/home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewModule.java:352: error: cannot find symbol
return FileProvider.getUriForFile(getReactApplicationContext(), packageName + ".fileprovider", capturedFile);
^
symbol:   variable FileProvider
location: class RNCWebViewModule
Note: /home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /home/handover/Documents/handover/tests/paypalRN/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
8 errors

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':react-native-webview:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s
Environment:

OS: Ubuntu
OS version: 18.4
react-native version: 16.8.3
react-native-webview version: 6.0.1

Duplicate of #580

Hello I fixed 6.0.2 and also released 5.9.1 if you don't want to upgrade!

Here's my solution : https://github.com/react-native-community/react-native-webview/issues/581#issuecomment-509534033

Thanks a lot!!!!, been stuck wit this error for days.

Hi, I'm facing the same pb but on 6.8.0  :confused:
@gentle-shao thanks for your contributions, but creating a new project is NOT a Solution

@BlackCod3  If you have found any solution please share it.

Hello i fixed my solution for rnwebview
you can install  "react-native-webview": "^7.5.2",
this will solve your solution in webview

Hello i fixed my solution for rnwebview
you can install "react-native-webview": "^7.5.2",
this will solve your solution in webview

This worked for me. Thanks Winplaybox


Update table of contents to add the new configuration dialog page

The push of the commit that added the new configuration dialog page to the table of contents failed due to a command line typeo.
This change adds in the missing contents link

/azp run mrtk_docs


Protection Table Refactor

#1165

lets discuss. do not push yet.

few things:
1.

when filtering only "fully protected" i should only see rows that are fully protected

longer symbols break the lines. consider displaying the data in the table in a trimmed down format.
example:
current: 0.000146 renBTC
trim down version: 0.000146 r...
and mouse over shows the full information (or you can create a cool animation on mouse over https://stackoverflow.com/questions/33888214/css-animation-to-extend-button-text-on-hover)

https://streamable.com/hq3d7a

select data range:

when selected the size of the indication is wider than when it is not defined.
x to clear the range is outside the box and is not intuitive that it is connected to the range selection

@Ran73Cohen lets go over this one tomorrow morning. @ashachaf do you want to join as well? I have a few ideas about design improvements.

"my protected positions" font size has changed.
filter box is larger (in height) than search box.
date selector font is smaller than other filters and is not centered in height of the box.

text change:
current: full protection reached
updated: Fully protected

@Meytal2021


Run flutter test on appveyor (Windows)

Should be possible now that https://github.com/flutter/flutter/issues/8516 is closed.
/cc @bkonyi

Closing in favor of @bkonyi's PR.

Isn't this still relevant?  dev/bots/test.dart still disables running unit tests on Windows...

Scratch that - just saw the Right PR 😄

I talked to @bkonyi offline and he wanted to enable all the tests in his PR, so I am dropping this one for now.


Initialize repository files

The new repository split out of cdss-app-statecu-fortran needs to have standard repository files added and top-level folder added similar to other documentation repositories.

Re-initialized repository files after splitting out of cdss-app-statecu-fortran.  Close this issue.


UI crash resulting on a white screen

Version: 1.0.0-alpha.54 (since 53)
Platform: win32 10.0.17134
Since the introduction of re-arranging tabs the UI started to crash constantly resulting on a complete white screen and all terminal connections loss.

Potentially fixed 18c0a585a2fe24be6dcba30df4c963f6f1802e90

@juanpazup have you by any chance enabled vibrancy in the settings? It could cause problems with Windows 7

Version: 1.0.0-alpha.55
Platform: win32 6.1.7601
@Eugeny No, vibrancy is not enable. And it always crash when I try to open the "Terminal" settings.


Add subcommand kv:bucket delete

This command should take as an argument the path to a directory of static assets to be deleted from Workers KV, keyed on path relative to the root of same directory.

closed by #514


format() and unformat() could return Any instead of AnyObject

If ValueFormatter's functions format() and unformat() would return Any instead of AnyObject I could write a ValueFormatter that transforms a dictionary of latitude and longitude to a CLLocationCoordinate2D  struct. Now I am forced to convert it to CLLocation object which means unnecessary overhead.
I'm sure there are more advantages to this.

That would be a nice update to the current system. Unfortunately Spine currently uses KVC to get and set values on resource objects. This means that we can only use it with reference types afaik.


v2 - reduce window white space for bigger model display

When working with bigger models, the model working area is too small, and it also replicates in the generated PDF. It even shows when zooming in. I include an example:

Describe the solution you'd like:

More space to work, and less blank space.
(Optional) zoom controls just for the model.

Working on Fedora Linux 33, using RPM version from the repo.

With version 2.0 of Threat Dragon we see the same problem, screenshot attached. We need the 'Properties' and 'Threats' Panes to be docked with the lower edge of the window, so that the drawing area and 'Entities' panes can expand to fill the gap.
Note that this also happens with the web app version, just zoom out to see the effect.

@taoyiyang1 - the tutorials/documentation for the drawing package is here : https://x6.antv.vision/en/docs/tutorial/about
Is this issue something you could help with?

With version 2.0 of Threat Dragon we see the same problem, screenshot attached. We need the 'Properties' and 'Threats' Panes to be docked with the lower edge of the window, so that the drawing area and 'Entities' panes can expand to fill the gap.

I'm hoping we can do better with the placement of these panes as well! As it is, it's not looking so great on smaller screens. :(
If memory serves me, the height for the graph is currently hard-coded in pixels.  This could even be as simple as changing it to use view-height as the unit with a min-size property?

Hello @lreading - absolutely agree, and you are best placed to do this one
My thought here was that @taoyiyang1 could help out with the actual tutorials and documentation for antv? As 陶一阳 does not have the language barrier here

It turns out the graph area isn't super responsive by default.  This means we might need to watch for window resizing events (or zoom events, if such a thing exists?) and redraw.  That might have some performance implications... We could debounce the events to help mitigate that a bit.
I'm going to try to think of a better solution for this before committing anything. If anyone has ideas, please do share! :smile:

你好@lreading - 绝对同意，你最适合做这个 我的想法是@taoyiyang1可以帮助提供antv 的实际教程和文档？因为陶一阳在这里没有语言障碍
我们可以把这个问题分配给你们两个吗？

@jgadsden Of course, @lreading you can consult me if you have difficulty reading a certain part of the document

The diagram area is now working as required in version 2.0 : https://www.threatdragon.com/
So this can now be closed


[gcov plugin] Branch exclusion markers not working?

I'm using the gcov plugin to generate reports of test coverage.
I managed to mark areas of my code that won't be tested with the LCOV_EXCL_START and LCOV_EXCL_STOP succesfully (although the output of the command line doesn't show them as covered, the html report reports the correct number

I'm trying to add the exclude branch markers to mark some "we won't get here" areas of the code (like the default case on a switch) but for the life of me I can't get it working. Is there something in gcov / lcov, or the gcov plugin that makes it ignore the branch exclusion markers?Could it be a versioning issue? Or am I using them wrong?

Thanks!

I'm afraid I haven't used any of these features in gcov yet and don't know the answer. @dpostorivo or @tobyjwebb -- do you know the answer?

haha, thanks for the honesty 😆
It's my first for me too, so not a 100% sure that I'm using them correctly, that's why I am asking

I'd need to do more investigation on this. I've never done exclude branches like this before. It should be noted that gcovr is external coverage report generation you can find here:
https://github.com/gcovr/gcovr
Ceedling's gcov plugin should just run gcov or lcov so if those comments work if your coverage executable, it should be fine.
What coverage executable are you using and what version? If possible I'd also analyse the raw .gcda  or .gcno  or whatever is generated in build/gcov/out.

Sorry, I haven't used these features yet, either...
TW

$ gcov --version
gcov (Rev2, Built by MSYS2 project) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.

$ gcovr --version
gcovr 4.1

Copyright 2013-2018 the gcovr authors
Copyright 2013 Sandia Corporation
Under the terms of Contract DE-AC04-94AL85000 with Sandia Corporation,
the U.S. Government retains certain rights in this software.

It appears that gcovr added the basic markers (LINE, START and STOP) in v3.8, but there's a ticket open for the BR set of markers.
https://github.com/gcovr/gcovr/issues/121
So I might be wrong, but it seems that is a gcovr issue.
Regarding my first screenshot, which piece of code is responsible for showing the console output? Any ideas on why the coverage % is different than the one in the HTML report (which is the "correct" one)

Hi!
Just a heads up. Gcovr has closed the ticket for the BR* markers (https://github.com/gcovr/gcovr/issues/121#event-7116069817) so I assume a new version with support for them will be released soon.

The branch exclusion markers are introduced into gcovr with https://github.com/gcovr/gcovr/pull/644. You can close this issue.


IOS build and deploy

Hi,
I need help.
I installed and develop a test app. Now I should do the package and install everything on IOS devices.
I have generated various certificates and provisioning.
But now I do not know how to proceed using the cordova commands (without Xcode).
Can you help me?
Can you tell me a step by step procedure to deploy on device?
Please.
Thanks and regards.

Oh... ok. Thanks a lot,
but I do not have an xcode project: I installed everything following your instructions with the command
"cordova create <project_create_dir> [com.example.projectname] [ProjectClassName] --template cordova-template-framework7-vue-webpack".
is it ok anyway?

Ok,
after several attempts I managed to build ipa with xcode and I installed everything on ipad. it works!

Awesome work @Bek81 !


[FedEx] Fix ArgumentError on parse tracking response.

This fixes an ArgumentError on ResponseContentError initialization when trying to parse tracking response from FedEx.
The existent code for FedEx's parse_tracking_response raising ResponseContentError error when tracking details notification is an ERROR with code different from 9040. But it provides only one argument for initialization when two expected.
Backtrace:
ArgumentError: wrong number of arguments (1 for 2)
/active_shipping-1.3.0/lib/active_shipping/errors.rb:19:in `initialize'
/active_shipping-1.3.0/lib/active_shipping/carriers/fedex.rb:578:in `exception'
/active_shipping-1.3.0/lib/active_shipping/carriers/fedex.rb:578:in `raise'
/active_shipping-1.3.0/lib/active_shipping/carriers/fedex.rb:578:in `parse_tracking_response'
/active_shipping-1.3.0/lib/active_shipping/carriers/fedex.rb:161:in `find_tracking_info'

With this PR second argument for ResponseContentError initialization becomes optional and parse_tracking_response raises error with correct arguments.

:+1:


fheroes2: include desktop entry

Description of changes
Currently fheroes2 in nixpkgs doesn't set up a desktop entry, even though an icon and desktop entry is included in the upstream repository. This fixes that.
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
[x] 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 224465 run on x86_64-linux 1

1 package built:

fheroes2


Increment versions for maps/azure-maps-route releases

Increment package versions for maps/azure-maps-route releases

API change check
API changes are not detected in this pull request.


universal poker half-pot abstraction: half-pot action is always considered legal even when it shouldn't be?

>>>  game = pyspiel.load_game('universal_poker', {'bettingAbstraction': 'fchpa'})
>>> s = game.new_initial_state().child(3).child(7).child(2).child(2)
>>> print(s)
BettingAbstration: FCPHA
P0 Cards: 2s
P1 Cards: 3s
BoardCards
Node type?: Player node for player 0
]
Round: 0
ACPC State: STATE:0:r300r900:2s|3s
Spent: [P0: 300  P1: 900  ]

Action Sequence: ddpp
>>> s.legal_actions()
[0, 1, 3, 4]
>>> s.child(4)
SpielError: open_spiel/open_spiel/games/universal_poker/acpc_cpp/acpc_game.cc:225 CHECK_TRUE(project_acpc_server::isValidAction(game_->MutableGame(), &acpcState_, false, &a))

In universal_poker.cc, the "half-pot bet" action (action 4) is always added, without checking to see if it's legal (and even in a terminal state). In contrast, the "pot bet" action (action 2) is added only when it is legal: this is determined by the possibleActions_ attribute, which is set in _CalculateActionsAndNodeType.
I guess the fix here would be to add the half-pot action to possibleActions_, and to set it in _CalculateActionsAndNodeType if using the FCPHA abstraction and the half-pot action should be legal.

Thanks, just tagging @jhtschultz @jblespiau for a heads up.

Another good catch. That does sound like a sensible fix. If you get to implementing it before we do it would be a welcome contribution :)

@VitamintK did you ever fix this ?
With the outstanding bugs in universal_poker.. I am wondering if we should consider removing the game unless we can fix these issues. It might be more prudent than leaving buggy games in the code base.

Actually, I think I have a better solution for games in this category: https://github.com/google-deepmind/open_spiel/pull/1163  (and https://github.com/google-deepmind/open_spiel/pull/1162)


Signatures don't validate

There's still something wrong with the output certificate files, when validating them the computed hash doesn't match the remote hash.

It looks like if the batch only contains a single cert we always end up with e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 as the hash, which if I had to guess is probably the hash of an empty cert (or whatever minimal values get subbed in when the unsigned cert is empty). Haven't found why that would happen yet...

As I suspected:
──┤stuart@varan:pts/3├┤venv├─────────────────┤/home/stuart/src/gt-blockcerts-issuer├┤master├──
──┤1423:Thu,21 Nov 19:✓├── echo -n '' |sha256sum
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855  -

Looks like the problem is we're passing a batch of certs to the issuer like:
[
  {"cert1": {<cert data>}},
  {"cert2": {<cert data>}},
  {"cert3": {<cert data>}}
]

But it should actually be:
 {
  "cert1": {<cert data>},
  "cert2": {<cert data>},
  "cert3": {<cert data>}
}

Well, testing that I'm finding it gives me errors about the urn keys not being valid urls. @divyegala pointed out that the docs at https://github.com/blockchain-certificates/cert-issuer/blob/master/docs/web_resources.md say to do it the way we were, but the tests at https://github.com/blockchain-certificates/cert-issuer/blob/master/tests/test_certificate_handler.py#L79 are what made me think that was wrong...

I think I've finally got this figured out, the actual format is:
[
    {<cert data>},
    {<cert data>},
    {<cert data>}
]

So there's no uuid keys.


v2ray: 5.11.0 -> 5.13.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for v2ray is: A platform for building proxies to bypass network restrictions
meta.homepage for v2ray is: https://www.v2fly.org/en_US/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.12.1 with grep in /nix/store/9plxlsiw96xg4q9nwaycn4d1nirx57cw-v2ray-core-5.12.1
found 5.12.1 in filename of file in /nix/store/9plxlsiw96xg4q9nwaycn4d1nirx57cw-v2ray-core-5.12.1

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
qv2ray
v2ray
v2raya

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9plxlsiw96xg4q9nwaycn4d1nirx57cw-v2ray-core-5.12.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/741db21b6b5287d68b5782c8d8f86a33748b4c1e#v2ray

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9plxlsiw96xg4q9nwaycn4d1nirx57cw-v2ray-core-5.12.1
ls -la /nix/store/9plxlsiw96xg4q9nwaycn4d1nirx57cw-v2ray-core-5.12.1/bin

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

3 packages built:

qv2ray
v2ray
v2raya

Maintainer pings
cc @servalcatty for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for v2ray is: A platform for building proxies to bypass network restrictions
meta.homepage for v2ray is: https://www.v2fly.org/en_US/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.13.0 with grep in /nix/store/80vrwsvkaaql9b7wkgylbgbym5nh1wj9-v2ray-core-5.13.0
found 5.13.0 in filename of file in /nix/store/80vrwsvkaaql9b7wkgylbgbym5nh1wj9-v2ray-core-5.13.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
qv2ray
v2ray
v2raya

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/80vrwsvkaaql9b7wkgylbgbym5nh1wj9-v2ray-core-5.13.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/5044c8f5f821a0d8eb61d8e9d6ebcc7ade39e546#v2ray

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/80vrwsvkaaql9b7wkgylbgbym5nh1wj9-v2ray-core-5.13.0
ls -la /nix/store/80vrwsvkaaql9b7wkgylbgbym5nh1wj9-v2ray-core-5.13.0/bin

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

3 packages built:

qv2ray
v2ray
v2raya

Maintainer pings
cc @servalcatty for testing.


Base stuff

Per @pmrv's suggestion, adding from pyiron_base:

ImportAlarm
Deprecator
retry

@pmrv, catching warnings in the tests can be janky -- e.g. because some dependency introduces some deprecation error of its own or whatever -- so I made a private flag to convert the deprecator warnings into hard errors and then test explicitly for that. User facing stuff remains totally unchanged.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.2%) to 91.741%

Totals

Change from base Build<PHONE_NUMBER>:
2.2%

Covered Lines:
411

Relevant Lines:
448

💛  - Coveralls


blockbench: 4.10.4 -> 4.11.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/JannisX11/blockbench/releases.
meta.description for blockbench is: Low-poly 3D modeling and animation software
meta.homepage for blockbench is: https://blockbench.net/
meta.changelog for blockbench is: https://github.com/JannisX11/blockbench/releases/tag/v4.11.0
Updates performed

NPM version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.11.0 with grep in /nix/store/gc7l6id8sw62q78izxbdsyj2p7x0qdkn-blockbench-4.11.0
found 4.11.0 in filename of file in /nix/store/gc7l6id8sw62q78izxbdsyj2p7x0qdkn-blockbench-4.11.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

blockbench

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/089817100165a606256570a87feb1401ee7d0f4b#blockbench

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gc7l6id8sw62q78izxbdsyj2p7x0qdkn-blockbench-4.11.0
ls -la /nix/store/gc7l6id8sw62q78izxbdsyj2p7x0qdkn-blockbench-4.11.0/bin

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

1 package built:

blockbench

Maintainer pings
cc @TomaSajt for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Builds and runs fine
@NixOS/nixpkgs-merge-bot merge


feat(risectl): add meta pause/resume

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
A useful feature for debugging.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)
#3697
#3471
Close #4003

Would you please add docstring to Pause and Resume enum, so that ./risedev ctl meta --help can be presented correctly?


2nd attempt at: Merge pull request #2781 from SwiftPackageIndex/dependabot/npm_and_ya…

…rn/dependencies-7337d43281
NPM: Bump the dependencies group with 6 updates

Seems to be working now: https://gitlab.com/finestructure/swiftpackageindex/-/jobs/5759980412


Introducing passive_intertransport_auth to facilitate communication b…

…etween nodes with adv sec enabled and nodes without adv sec enabled.
Changes to ssl_dual_mode_enabled to support the same.
Signed-off-by: Dhiresh Jain<EMAIL_ADDRESS>opendistro-for-elasticsearch/security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly
NOTE: This commit has been moved from opendistro repo to opensearch. The manual test was done using docker in opendistro. Docker testing is currently unavailable in opensearch so did not perform a manual test here yet.

Category: New feature

Github Issue # or road-map entry, if available:

Description of changes: Introducing opendistro security dynamic config feature flag "passive_intertransport_auth".
Additionally, making changes to ssl_dual_node behaviour.
The changes allow transport communication between nodes with advanced security enabled and nodes without advanced security enabled (ssl only or plugin disabled).
The feature flag should be used transiently to facilitate migration of cluster to using advanced security.

Why these changes are required?
Currently, migrating to advanced security requires a full cluster restart as any other kind of migration process causes transport communication to break between old and newer nodes. These changes will allow a cluster to be migrated to use advanced security without any downtime, by allowing old and new nodes to successfully communicate at the transport layer.
NOTE: There is an existing feature disable_intertransport_auth that if enabled will cause transport level authorization to be skipped. However, the side affect of this is that any non-super admin user will be able to update opendistro_security during migration.
passive_intertransport_auth does not skip authorization, instead it injects a default user, which you can map to the permissions you want to give during this transient phase of migration.

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)
Old Behaviour: Transport communication from old node to a new node fails at the new nodes with the error: No user found for...
New Behaviour: Transport communication from old node to a new node succeeds. When a user is not found and this feature flag is set to true, we inject a default user. Note that this user should have all index and cluster permissions.

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)
Extensive UTs to cover all cases.

__With passive_intertransport_auth disabled:__
dhireshj@f45c899db61b ~/w/d/dhi_security (transport_passive_mode)> curl "https://localhost:9200/_cat/nodes" -k
<IP_ADDRESS> 18 22 44 2.01 1.88 1.04 dimr * elasticsearch1
<IP_ADDRESS> 55 20 49 2.01 1.88 1.04 dir  - elasticsearch2
dhireshj@f45c899db61b ~/w/d/dhi_security (transport_passive_mode)> curl -X PUT "https://localhost:9200/test5?pretty" -H 'Content-Type: application/json' -d'
                                                                   {
                                                                       "settings": {
                                                                           "index": {
                                                                             "number_of_shards": 1,
                                                                             "auto_expand_replicas": "0-all",
                                                                             "routing.allocation.exclude._name": "elasticsearch1"
                                                                           }
                                                                       }
                                                                   }' -k
{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "index" : "test5"
}
dhireshj@f45c899db61b ~/w/d/dhi_security (transport_passive_mode)> curl -XPOST "https://localhost:9200/test5/_doc/1" -k -H 'Content-Type: application/json' -d'{}' -k
{"error":{"root_cause":[{"type":"security_exception","reason":"No user found for indices:admin/mapping/auto_put"}],"type":"security_exception","reason":"No user found for indices:admin/mapping/auto_put"},"status":500}⏎

__With passive_intertransport_auth enabled:__

dhireshj@f45c899db61b ~/w/d/dhi_security (transport_passive_mode) [60]> curl "https://localhost:9200/_cat/nodes" -k
<IP_ADDRESS> 17 21 48 2.84 1.97 0.95 dimr * elasticsearch1
<IP_ADDRESS> 26 21 49 2.84 1.97 0.95 dir  - elasticsearch2
dhireshj@f45c899db61b ~/w/d/dhi_security (transport_passive_mode)> curl -X PUT "https://localhost:9200/test4?pretty" -H 'Content-Type: application/json' -d'
                                                                   {
                                                                       "settings": {
                                                                           "index": {
                                                                             "number_of_shards": 1,
                                                                             "auto_expand_replicas": "0-all",
                                                                             "routing.allocation.exclude._name": "elasticsearch1"
                                                                           }
                                                                       }
                                                                   }' -k
{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "index" : "test4"
}
dhireshj@f45c899db61b ~/w/d/dhi_security (transport_passive_mode) [52]> curl -XPOST "https://localhost:9200/test4/_doc/1" -k -H 'Content-Type: application/json' -d'{}' -k
{"_index":"test4","_type":"_doc","_id":"1","_version":1,"result":"created","_shards":{"total":1,"successful":1,"failed":0},"_seq_no":0,"_primary_term":1}⏎

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1156 (c7853af) into main (f1a2f45) will increase coverage by 0.03%.
The diff coverage is 75.00%.

:exclamation: Current head c7853af differs from pull request most recent head 974087a. Consider uploading reports for the commit 974087a to get more accurate results

@@             Coverage Diff              @@
##               main    #1156      +/-   ##
============================================
+ Coverage     64.65%   64.68%   +0.03%
- Complexity     3183     3192       +9
============================================
  Files           245      247       +2
  Lines         17147    17197      +50
  Branches       3038     3046       +8
============================================
+ Hits          11086    11124      +38
- Misses         4516     4522       +6
- Partials       1545     1551       +6

Impacted Files
Coverage Δ

...arch/security/ssl/OpenSearchSecuritySSLPlugin.java
83.97% <0.00%> (ø)

...ssl/transport/SecuritySSLTransportInterceptor.java
0.00% <0.00%> (ø)

...g/opensearch/security/support/ConfigConstants.java
94.44% <ø> (ø)

...rch/security/setting/OpensearchDynamicSetting.java
60.00% <60.00%> (ø)

...pensearch/security/configuration/CompatConfig.java
41.66% <66.66%> (+12.63%)
:arrow_up:

.../security/setting/TransportPassiveAuthSetting.java
75.00% <75.00%> (ø)

...rch/security/transport/SecurityRequestHandler.java
75.71% <83.33%> (+0.52%)
:arrow_up:

...org/opensearch/security/filter/SecurityFilter.java
78.03% <87.50%> (+2.43%)
:arrow_up:

.../opensearch/security/OpenSearchSecurityPlugin.java
81.34% <100.00%> (+0.11%)
:arrow_up:

...g/opensearch/security/ssl/transport/SSLConfig.java
100.00% <100.00%> (+10.00%)
:arrow_up:

... and 10 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 6a86ae2...974087a. Read the comment docs.

@vengadanathan-s when merging PR please make sure to delete all unnecessary details from the commit message.


[ENH] Modifying Points in Line Chart

Adding a feature to modify points in V2. similar to http://jsfiddle.net/3tok57dL/2/
Ability to change Radius, Colors, Size, Visibility for individual points in Line Chart

@taqimustafa you can do this in multiple ways. I think the best way is to set pointRadius as an array of values and set it to 0 for the points you don't want to see.


Fix various persistence bugs

[x] Closes #517, closes #518, closes #528, closes #524.
[x] I am familiar with the contributing guidelines.
[x] Tests added.
[ ] Updates entries to docs/source/api.rst for API changes.
[ ] Adds descriptions to appropriate "what's new" file in docs/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[x] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

Two questions: should day ahead persistence keep NaNs in the forecast or fail to make one? Should probabilistic forecast return empty series when there is no data or raise some error?

adding what's new soon


contentType bug fix

request.contentType bug fix

The second comparison should probably be changed to == "" instead of !=.

you are right.
https://github.com/openfl/openfl/pull/1030

You can make changes, and the pull request will update with those changes automatically. You don't have to make a new pull :)

sorry, i change code in the fellow url now.it is right ?
https://github.com/hpgood/openfl/blob/patch-3/openfl/display/Loader.hx


Can't type help in the input box

I can't type Help in the input box because it seems I can only type one of the mathematical expressions - And doing is_prime help raises an error as well

Lol yeah I accidentally removed help as a command after rewriting the input system 🤦♂


⚠ ClamAV has degraded performance

In 72bd9bc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 84 ms

Resolved: ClamAV performance has improved in 204d561.


README: Ho ho ho!

Merry Christmas and happy holidays! :monkey: :cloud: :santa: :christmas_tree:
/cc alphabetically-ish @andrijapanic @anuragaw @borisstoyanov @bwsw @chiradeep @csquire @DaanHoogland @DagSonsteboSB @dhlaluku @fmaximus @GabrielBrascher @gsirett @glennwagner @harikrishna-patnala @jayapalu @K0zka @karuturi @kiwiflyer @khos2ow @PaulAngus @marcaurele @mike-tutkowski @milamberspace @msinhore @nitin-maharana @NuxRo @nvazquez @pdion891 @pyr @rafaelweingartner @RPDiep @resmo @steveroles @sureshanaparti @svenvogel @swill @syed @ustcweizhou @wido and so many others!

merry xmas and happy new year!

@rhtyd Thank you! Merry Christmas as well)

Can we have some LGTMs, I checked the Travis test failures were not caused by this PR ;)

LGTM! Merry Christmas and Happy new year everyone!

LGTM. Merry Christmas and Happy New Year guys! :tada:

LGTM and merry Christmas everyone!
I do have a small comment though, why the name of branch is xmas-2019? :wink:

LGTM , Merry Christmas everyone, Happy new year

+1
Merry Christmas and Happy New year to all :)

Fill your bellies and be merry! Ho ho ho :)

+1  Merry Christmas everyone!

LGTM, Happy holidays and have a wonderful 2019!

I do have a small comment though, why the name of branch is xmas-2019?
@khos2ow well it's about Christmas time and 2019 new year!

For me xmas is on 7th January 2019 - so "works on my machine" 🕺

I do have a small comment though, why the name of branch is xmas-2019?
@khos2ow well it's about Christmas time and 2019 new year!

For me xmas is on 7th January 2019 - so "works on my machine" 🕺

Best PR ever,  +1
Enjoy holidays ! :-)

LGTM
Thanks and Happy new year!

We're in violent agreement, let's merge!


Greater/less than + other relational operators too strict on union types

master branch as of 10/12/2016
let lhs: 10 | 20 = <any>10;
let rhs: 15 | 25 = <any>15;
if (lhs > rhs) { // Error, can't compare 10|20 to 15|25

}

Actual behavior:Error, can't compare 10 | 20 to 15 | 25
Expected: No error

Duplicate #10119


Update README.md

add the oepnsds design focus description.
add the 'OpenSDS Controller Work Group' sections.
add the 'License' sections.

@wisererik Thanks for updating the document, but I'm a bit confused about this sentence:
If you are a developer want to be part of the PoC development that is happening now, please refer to the Contribute sections below.
Can you please update the word Poc development to something like code development so that others would not get misunderstood?

@leonwanghui Thanks for your suggestion, I have resolved it, please review again.

Thanks Eric, it looks better, now I will merge it until all build work is done.


chore: allow custom java repository to work with bazel 6.x

Wait, this probably won't fix our downstream, because the nightly Bazel binary doesn't have a version number.

Yeah, I figured best to adapt the future to accommodate the now :-)

Thanks!


YLabels are cut

I'm trying to replicate this design, but when I reach high values on Y axis, they are cut (I don't want to decrease the font of the text but reduce the right part of the graph to give more space to the Y labels):

This is how it looks in app:

I'm also trying to create the blue box only on X label that is selected, any suggestions?

Hi @steq28
To increase the Y-axis label width, you can use the yAxisLabelWidth prop.
To create a blue box for the selected X-axis label, you can use the labelComponent property inside the data array objects.
Here's a sample code for your use case-
export const HighlightXaxis = () => {
  const [selectedIndex, setSelectedIndex] = useState(-1);

  const MyComponent = (labelText, index) => {
    const isSelected = selectedIndex === index;
    return (
      <View
        style={{
          backgroundColor: isSelected ? '#344F6C' : 'transparent',
          width: 20,
          height: 24,
          paddingTop: 2,
          alignSelf: 'center',
          borderRadius: 4,
        }}>
        <Text
          style={{textAlign: 'center', color: isSelected ? 'white' : 'gray'}}>
          {labelText}
        </Text>
      </View>
    );
  };

  const data: barDataItem[] = [
    {value: 49.5, labelComponent: () => MyComponent('M', 0)},
    {value: 64.2, labelComponent: () => MyComponent('T', 1)},
    {value: 52.2, labelComponent: () => MyComponent('W', 2)},
    {value: 76.5, labelComponent: () => MyComponent('T', 3)},
  ];
  return (
    <BarChart
      data={data}
      roundedTop
      frontColor="lightgray"
      barWidth={20}
      spacing={40}
      showReferenceLine1
      referenceLine1Position={60}
      referenceLine1Config={{
        color:'#6DBDBD',
        thickness: 5
      }}
      referenceLinesOverChartContent={false}
      rulesType={ruleTypes.SOLID}
      showFractionalValues
      roundToDigits={3}
      noOfSections={5}
      yAxisLabelWidth={60}
      yAxisTextStyle={{color: 'gray'}}
      yAxisColor={'lightgray'}
      xAxisColor={'lightgray'}
      focusBarOnPress
      focusedBarConfig={{color: '#344F6C'}}
      onPress={(item, index) => {
        setSelectedIndex(index);
      }}
    />
  );
};

https://github.com/Abhinandan-Kushwaha/react-native-gifted-charts/assets/20596944/e36710df-9ad7-4c14-8223-a8aa75e8ec7f

Thanks!

is it possible to display Y-axis label with metric prefix?

Yes @leolo784
Try the props yAxisLabelPrefix, yAxisLabelSuffix or formatYLabel
You can also use the yAxisLabelTexts prop for custom label texts. See https://github.com/Abhinandan-Kushwaha/react-native-gifted-charts/issues/22


Move Vector implementation to Vector2 file

This is to disambiguate between Vector2 and Vector3 (see #974). Vector.h can be repurposed to be include delegates for both until downstream projects update their includes:
Vector.h
#include "Vector2.h"
#include "Vector3.h"

Vector2.h
//Original contents of Vector.h

I think I desire to not split Vector into 2D and 3D versions.

See my last comment on #974, this isn't really the direction I want to go with NAS2D.


Don't scroll map away when scrolling through layers [ 6 hours ]

I want to say it'll take closer to 2 hours, but I seem to recall trying this before and giving up after quite a bit of work. 6 seems a decent middle ground - by 4 hours if it's not fixed at least I'll know why and know how much further there is to go.

Fixed: cb71ee78b976ba7c49f3b72ae29aa64bbc5158ba


Install env get wrong

I try to install in my new project virtual enviroment for python, and it gives me error.
[Window Title]
devenv.exe
[Main Instruction]
An unexpected error occurred
[Content]
Your packages may not have been installed.
Please press Ctrl+C to copy the contents of this dialog and report this error to our issue tracker.
[^] Hide details  [Закрыть]
[Expanded Information]
System.ArgumentException: Параметр задан неверно. (Исключение из HRESULT: 0x80070057 (E_INVALIDARG))
в EnvDTE.Commands.Raise(String Guid, Int32 ID, Object& CustomIn, Object& CustomOut)
в Microsoft.PythonTools.ProjectWizards.InstallRequirementsWizard.ProjectFinishedGenerating(Project project)

At this point, your project should still have been created, even though it doesn't have a virtual environment in it. If you create one through Solution Explorer, do you get an error? Unfortunately, there isn't enough information here for me to figure out what went wrong.

Seems to be specific to Russian? It's really not clear how that could be the case though.

Possibly specific to non-English?

Which version of VS is this? I could try to repro.

VS 2015, I believe. The earlier report was from January, so VS 2017 wasn't out yet.

If i create env from explorer, it's been ok. It's created and worked. Maybe it's really specific to Russian system language and language in programm. I try soon on English, and write here results. VS version 2015.

Yea problem is in Russian language in programm. I install English version of it, and it will be work perfectly.

We're closing old issues with no recent activity. If this is still important, please open a new issue.


[HxInputDate] dark mode broken in Edge

Only happens in Edge so far as I can tell.
Video:
https://github.com/havit/Havit.Blazor/assets/10275357/3640c98f-ec38-42e2-bade-13f485a34190

@crdo I'm able to reproduce the reported issue.
The issue disappears when I force :hover on the select element:

@hakenr to me this feels more like a browser bug rather than issue in our library.

Although I still believe this is a browser bug and I cannot reproduce it as it works on all browsers across macOS I rewrote the CSS to get rid of that silly :not(:hover) selector.
@hakenr please let me know if it helped or make a pre-release so @hrocha1 or @resignationinfinite can test it.

Might be an issue with some Windows native UI elements. I haven't been able to reproduce it on macOS or Linux either.

release 4.6.11-pre2, make sure you clear your browser cache (previous version of CSS bundle)

After a quick testing with @alexax578 I think it is fixed.

@crdo Can confirm it works on my side, thanks 👍

Closing as fixed.
Will be part of the 4.6.11 release.


Fix warning missing terminating character

warning: missing terminating ' character [enabled by default]

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
337

Relevant Lines:
337

💛  - Coveralls


Supermium still enforces a choice on me on downloads, that it considers to be "unsafe"

Supermium 122.0.6261.85 Hotfix (R2) 32bit https://github.com/win32ss/supermium/releases/tag/v122-hf
on Windows XPSP3 32bit
A continuation of a ticket that I created earlier: https://github.com/win32ss/supermium/issues/247
test file is the same as which is used in https://github.com/win32ss/supermium/issues/415
http://<IP_ADDRESS>:8090/download/developer/vs/vs2008proedition90daytrialenux1435622.iso
I do have the following configured on Supermium:
1.) Chrome flag #insecure-download-warnings is set to disabled.  It just shall start to download without nagging me.
2.) Chrome flag #disable-download-upload set to enabled, for the same reason: It shall just download without nagging me
3.) Chrome flag #download-bubble set to disabled, because I do prefer the download shelf over the bubble
4.) furthermore in the settings -> security I do have safeBrowsing feature turned off, because I don't want to be nagged, and I don't want my downloads to be sent to google neither:

5.) I do use the cmd-line param --safebrowsing-disable-download-protection (hoping to make it stop whimpering)
Expected result:
I don't want to be nagged with foolish questions like:

It should just start to download!
I am ok with setting yet another cmdline param, or chrome-flag for that purpose (or fixing the existing #insecure-download-warnings to cover that case as well).
No need to change the browsers default behavior. Let our grandmas be safe!
Observed result:
Supermium still nags me with that foolish question for the case of the link above being http (which is not https):

That nonsense is inherited from the Google Chrome guys ofc.

I was working on the --ungoogled-supermium switch and I decided to target safe browsing (although it doesn't seem to be even part of safe browsing!). It seems to work with some other flagged binaries like progwrp.dll but I will have to verify a little more. The downloading part of that switch can be integrated into --insecure-download-warnings as well.

The downloading part of that switch can be integrated into --insecure-download-warnings as well.

Sounds great!

https://github.com/win32ss/supermium/commit/fae39619269dfe9467da7fc741bfe44c0f37383a might be related and was committed after "Supermium 122.0.6261.85 Hotfix (R2)" was released already, so I would expect it to be integrated in its successor.

I tried to retest this ticket with "Supermium 122.0.6261.152 (R4)", but the website has changed meanwhile and now queries for user credentials (on all browsers) and I don't have the credentials.
I therefore assume that the ticket was properly fixed by https://github.com/win32ss/supermium/commit/fae39619269dfe9467da7fc741bfe44c0f37383a and I would open a fresh issue if I ever would see that message again.


Update Netty beyond 4.1.45 (per CVE-2020-11612)

There is a security vulnerability, CVE-2020-11612 in netty, before 4.1.46. (This is flagged by build-time tools, such as the commonly used OWASSP dependency-checker.)
It particularly affects any use of netty code in a server situation, where untrusted clients data is able to reach the server directly and be decoded:
The ZlibDecoders in Netty 4.1.x before 4.1.46 allow for unbounded memory allocation while decoding a ZlibEncoded byte stream. An attacker could send a large ZlibEncoded byte stream to the Netty server, forcing the server to allocate all of its free memory to a single decoder.
Update shaded netty version to at least 4.1.48 should fix the issue.

We're using 4.1.77.Final currently.
I think this can be closed @avelanarius.


fix(offset): avoid NaN when mainAxis or crossAxis is undefined

The coords become NaN when we use offset middleware and pass undefined to option.mainAxis or option.crossAxis. This behavior can cause problem when the option was optional value, like offset({ mainAxis: offsetOrUndefined }).

Thank you


Few ideas to add

Hi,
I think that add influxdb, telegraf and varken should be a very good idea because permit see a much more datas.
May be another optionaly adds are https://github.com/metalmatze/alertmanager-bot or https://github.com/MikeSafonov/prometheus-telegram-alert and https://github.com/prymitive/karma

There's nothing stopping users from adding Varken to their stacks, the intent specifically around dockprom is to provide users with some basic dashboards and a stack to provide monitoring/alerting.
Since Varken is quite specifically centered around specific applications and the applications other than karma are centered around telegram we wouldn't add them to the stack because it's not so much a one size fits all.
We look to cater to the lowest common denominator to ensure that the stack is lean and maintainable and so that elements that are introduced are likely to be utilised by many rather than the few.


AND,OR,NOT logic in the API

@elipapa commented on Fri Sep 15 2017
Description

[x] WHY - What is the problem this feature would answer?

filtering targets expressed in one tissue but NOT in another one and other similar queries. Basically it will enable an expressive query language for search.

[ ] HOW are we going to solve the problem?

Describe technical design of the solution.
Paste here google doc link or link to markdown file, if already written somewhere else

[ ] WHAT would this look like?

Screenshots and mock-ups are great

Progress Tracker
Get to a prototype at branch.targetvalidation.org:

Write code + tests + docs. Isolate the work in feature branches.
Use as many PRs as you need.
Write tests in the same or different PRs, as is convenient for you.
As each PR is merged, add a comment to this issue referencing the PRs.

[ ] Feature tag Code should have a feature tag to be disabled by default.
[ ] Minimal functional testing
[ ] Minimal docs
[ ] if on webapp, test a deployment on netlify

Push to staging

[ ] merged code and pushed to staging.targetvalidation.org
PULL request should be reviewed by 1-2 people at least
[ ] at least 1 week internal testing?
[ ] received some feedback/input from users (eg. pharma scientist)

Released

[ ] in the release notes?
[ ] documentation updated?
[ ] blog post?
[ ] users that requested it originally informed?

Make sure you can measure impact

As dev team we want to know if a new feature are succesful.
To do that we need to define metrics to assess the impact of each new feature we introduce to the platform

[ ] metric identified
[ ] identify the one metric that matters (OMTM)

@elipapa commented on Fri May 04 2018
slack does this well:

@Need to confirm priority and value of this advanced search/ filtering over other requirements.


Update to work with kettle@2.

If run with<EMAIL_ADDRESS>the tests fail with:
14:49:39.476:  Sending a GET request to: http://<IP_ADDRESS>:6533/http://localhost:6533/hcf
14:49:39.482:  FATAL ERROR: Uncaught exception: Unexpected token T in JSON at position 0
SyntaxError: Unexpected token T in JSON at position 0
    at JSON.parse (<anonymous>)
    at fluid.test.express.helpers.verifyJSONContent (/Users/duhrer/Source/rtf/fluid-express/tests/js/lib/test-helpers.js:43:24)
    at togo (/Users/duhrer/Source/rtf/fluid-express/node_modules/infusion/tests/test-core/utils/js/IoCTestUtils.js:232:33)
    at wrapped (/Users/duhrer/Source/rtf/fluid-express/node_modules/infusion/tests/test-core/utils/js/IoCTestUtils.js:350:26)
    at fire (/Users/duhrer/Source/rtf/fluid-express/node_modules/infusion/src/framework/core/js/Fluid.js:1732:40)
    at IncomingMessage.<anonymous> (/Users/duhrer/Source/rtf/fluid-express/node_modules/kettle/lib/test/KettleTestUtils.http.js:162:13)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1244:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

The request payload was previously JSON as a string.  Now it's a string.
The notes for the 2.0.0 release claim backward compatibility, but something seems to have changed.
cc: @amb26

The request payload was previously JSON as a string.  Now it's a string.
The notes for the 2.0.0 release claim backward compatibility, but something seems to have changed.
cc: @amb26

As discussed with Antranig, the errors were down to a change in the handling of the path and url fields that was addressed by the 2.1.0 release of kettle.

As discussed with Antranig, the errors were down to a change in the handling of the path and url fields that was addressed by the 2.1.0 release of kettle.


Connectivity loss | Limitation not added to the Create and configure Route Server page

Connectivity loss | Limitation not added to the Create and configure Route Server page
Customer reported as the limitations causing the connectivity loss is not added to the Create and configure Route Server page. Please get this added as customer knows this to be implemented during approved downtime window.
This limitation is included to the troubleshooting document:-
https://learn.microsoft.com/en-us/azure/route-server/troubleshoot-route-server#why-do-i-lose-connectivity-to-my-on-premises-network-over-expressroute-andor-azure-vpn-when-im-deploying-azure-route-server-to-a-virtual-network-that-already-has-expressroute-gateway-andor-azure-vpn-gateway
But not in the configuration document:-
https://learn.microsoft.com/en-us/azure/route-server/quickstart-configure-route-server-portal
Please get this included.

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

ID: c771bcd2-f7be-662f-f9a8-225a45714e08
Version Independent ID: b2ecbc58-7f13-44b7-38bd-ffc773570e87
Content: Quickstart: Create and configure Route Server - Azure portal
Content Source: articles/route-server/quickstart-configure-route-server-portal.md
Service: route-server
GitHub Login: @halkazwini
Microsoft Alias: halkazwini

@amkarmak
Thanks for your feedback! We will investigate and update as appropriate.

@amkarmak
Thank you for your feedback!
I've added the same warning that exists on: https://learn.microsoft.com/en-us/azure/route-server/expressroute-vpn-support article. Expect to see the change reflected in the public doc in the next few hours.
#please-close


Vue 2.0 and vue-touch#next: no $event property?!

I'm trying vue-touch#next under Vue 2.0 with...
v-touch:swipe="eventListItemSwiped({ itemId: item.id, direction: $event.direction })"
v-touch-options:swipe="{ direction: 'horizontal', threshold: 100 }"

...but it seems the special $event property does not exist for vue-touch events. I always just get a Vue warning: Property or method "$event" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option. (found in root instance).
I know I could do...
v-touch:swipe="eventListItemSwiped"
v-touch-options:swipe="{ direction: 'horizontal', threshold: 100 }"

...and receive the Hammer event as the single argument and then assemble the data structure in the callback as { itemId: $(ev.target).attr("data-id"), direction: event.direction }. But could you please add back the $event property for vue-touch? It would align vue-touch again to the regular Vue event handling where $event is available. Without this the Hammer events have to be handled differently than other types of events.
Or did I missed something and hence $event is not working for me?

One more issue with the "next" variant of Vue-Touch: the old "v-touch-options" is no longer available. Just the global options. Can you re-add "v-touch-options" please, too?

Disclaimer: I wrote the update for 2.0 but did not write the initial implementation
Are you sure $event was accessible in the 1.0 version? directives are not events, thefore there's never any $event available afaik.
About v-touch-options: That is unfortunately not as easy as it may sound. Due to the changes to custom directives (in this case: the deprecation of the priority option for custom directives) v-touch-options can't be implemented in the way that it was.

The current workaround is to create a custom Event instead.
I was already thinking about allowing to pass an object to v-touch, which would contain options and the callback function - but that would require some thorough testing and may take a while.

No, I'm not sure that $event existed in the 1.0 version. I'm just trying to convert a Vue 2.0 + HammerJS app to Vue 2.0 + vue-touch#next and recognized that the current vue-touch#next does not look sophisticated enough. Independent whether $event is available or not, we have to make the HammerJS event object available to the callback, because only this way one can check things like "direction", etc. Passing it through to the callback via $event would be just the most obvious solution for Vue users as they are used to this from the similar "looking" v-on:xxx, too.

, we have to make the HammerJS event object available to the callback, because only this way one can check things like "direction", etc.

The callback function that you pass to v-touch will receive the Hammer Event Object as its (only) argument.
If you want to curry the callback function, you can do something like this:

methods: {
  curry(fn, ...initialArgs) {
    const newFn = fn.bind(this, ...initialArgs)
    return (...newArgs) => newFn(...newArgs)
   },
  myCallback(a, b, event) {

  }
}

curry utilities are available via many util libs, e.g. lodash has _.partial()

Thanks for the hint. Could you perhaps do the following: just always append the event object to the argument list of the callback. So, v-touch="foo" invokes foo(<event>) and v-touch="foo(42, 'bar')" invokes foo(42, 'bar', <event>). Because it is nasty having to provide the curry helper function as a method all the time just to be able to get certain parameters and the event.

Could you perhaps do the following: just always append the event object to the argument list of the callback. So, v-touch="foo" invokes foo(<event>) and v-touch="foo(42, 'bar')" invokes foo(42, 'bar', <event>).

This is not possible with a directive, as I already explained above when I talked about $event: The expression is already executed when the code of the directive receives it, that means that foo(42, 'bar') would have already *called the foo() function with the arguments 42 and 'bar' by the time the directive code runs.

Oh, finally got it! Then vue-touch#next is really stuck, of course. Instead Vue 2.0 would have to be first enhanced to support more flexible implementations of custom directives where the argument is evaluated at the time an event happens instead of at render-time...

Please don't be bothered by me, but just one more crazy idea: if a custom Vue 2.0 directive never can have the power of v-on, we perhaps should change the implementation strategy: instead of implementing an own v-touch, how about implementing custom DOM events triggered by HammerJS events, i.e., how about using v-on:swipe="..."and find a way to emulate the custom DOM eventswipewith the help of HammerJS? Do you see a chance this could be achieved? If it would be possible, it would have both the advantage of the full power ofv-on` and let the touch gestures no longer be special cases, too ;-)


Expecting $NULL but got a Value errors - These seem to be wrong checks

First time running dbachecks so these may be me not understanding the output but they seem like errors
Upon running -AllChecks upon a new build server
Failsafe Operator, is specified but it is wanting a NULL, this should be expecting a value
Context Testing failsafe operator exists on <Server>\<Instance>
      [-] failsafe operator on <Server>\<Instance> exists 1.62s
        Expected $null, because The failsafe operator will ensure that any job failures will be notifed to someone if not set explicitly, but got 'SQLLog'.
        52:                     (Connect-DbaInstance -SqlInstance $psitem).JobServer.AlertSystem.FailSafeOperator | Should -Be $failsafeoperator -Because 'The failsafe operator will ensure that any job failures will be notifed to someone if not set explici
tly'
        at <ScriptBlock>, C:\Program Files\WindowsPowerShell\Modules\dbachecks\1.1.138\checks\Agent.Tests.ps1: line 52

DBMail profile, is specified but it is wanting a NULL, this should be expecting a value
Context Testing database mail profile is set on <Server>\<Instance>
      [-] database mail profile on <Server>\<Instance> is  1.23s
        Expected $null, because The database mail profile is required to send emails, but got 'SQLLog'.
        65:                     (Connect-DbaInstance -SqlInstance $psitem).JobServer.DatabaseMailProfile | Should -Be $databasemailprofile -Because 'The database mail profile is required to send emails'
        at <ScriptBlock>, C:\Program Files\WindowsPowerShell\Modules\dbachecks\1.1.138\checks\Agent.Tests.ps1: line 65

Active Directory Domain, computer is joined to the domain, but is wanting a NULL, this should be wanting a values
Context Testing Active Directory Domain Name on <Server>
      [-] <Server> Should Be on the Domain  448ms
        Expected $null, because The machine needs to be on the domain, but got 'domain.rootdomain.com'.
        8:                 (Get-DbaCmObject -Class Win32_ComputerSystem -ComputerName $psitem -Credential $credential).Domain | Should -Be $domain -Because 'The machine needs to be on the domain'
        at <ScriptBlock>, C:\Program Files\WindowsPowerShell\Modules\dbachecks\1.1.138\checks\Domain.Tests.ps1: line 8

Hi @AntG1985
Because those configurations do not have a default value the check will evaluate against a NULL value and fail.
If you run
Get-DbcCheck | Out-GridView

You can see the configuration items that are required for each check. So the failsafe operator for example requires the config agent.failsafeoperator

You can set this with
Set-DbcConfig -Name agent.failsafeoperator -Value "The OperatorName I require"
and see all of the configured values using
Get-DbcConfig | Out-GridView

I hope that helps to enable you to work out how to configure the other values that you need also. Feel free to join the SQL Community Slack at sqlps.io/slack and ask for help in the #dbachecks channel as well

Any value that you wish set or change needs to be done with Set-DbcConfig.
Only SqlInstance, ComputerName and SqlCredential can be set at when you call Invoke-DbcCheck
Best Regards
Rob Sewell
Cloud and Datacenter MVP
https://robsewell.info
https://sqldbawithabeard.com
@sqldbawithbeardhttps://twitter.com/sqldbawithbeard
https://uk.linkedin.com/in/robsewellsqldba
mrrobsewell<EMAIL_ADDRESS>From: AntG1985<EMAIL_ADDRESS>Sent: 14 June 2018 11:24
To: sqlcollaborative/dbachecks<EMAIL_ADDRESS>Cc: Rob Sewell<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [sqlcollaborative/dbachecks] Expecting $NULL but got a Value errors - These seem to be wrong checks (#497)
Ah, thanks Rob, that’s great. Thought it would be my lack of understanding.
So essentially anything with a blank value in Get-DbcConfig needs to either be set via Set-DbcConfig or the correct value passed in at invoke time.
Thanks
Ant
From: Rob Sewell <notifications<EMAIL_ADDRESS>Sent: 14 June 2018 10:39
To: sqlcollaborative/dbachecks <dbachecks<EMAIL_ADDRESS>Cc: AntG1985 <antg1985<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [sqlcollaborative/dbachecks] Expecting $NULL but got a Value errors - These seem to be wrong checks (#497)
Hi @AntG1985https://github.com/AntG1985
Because those configurations do not have a default value the check will evaluate against a NULL value and fail.
If you run
Get-DbcCheck | Out-GridView
You can see the configuration items that are required for each check. So the failsafe operator for example requires the config agent.failsafeoperator
[Image removed by sender. image]https://user-images.githubusercontent.com/6729780/41404139-52e7e95a-6fbe-11e8-87bd-299e98418d74.png
You can set this with
Set-DbcConfig -Name agent.failsafeoperator -Value "The OperatorName I require"
and see all of the configured values using
Get-DbcConfig | Out-GridView
[Image removed by sender. image]https://user-images.githubusercontent.com/6729780/41404287-b6664288-6fbe-11e8-8a4b-a35051073c6d.png
I hope that helps to enable you to work out how to configure the other values that you need also. Feel free to join the SQL Community Slack at sqlps.io/slack and ask for help in the #dbachecks channel as well
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/sqlcollaborative/dbachecks/issues/497#issuecomment-397234909, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AmXguTjyDKbbSQVZUJ8A57uIUb4fx3b3ks5t8i8cgaJpZM4Ul0rX.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsqlcollaborative%2Fdbachecks%2Fissues%2F497%23issuecomment-397247154&data=02|01||5b022d2bc6a54414669408d5d1e0eb0d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636645686300316398&sdata=aqqBpZhb6dtTUf4zVeJJVpszfWFde0Uz76PLeZQdzvw%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGawNLvoGVIDkAvcQhXH3-quDJs5VAuvks5t8jm0gaJpZM4Ul0rX&data=02|01||5b022d2bc6a54414669408d5d1e0eb0d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636645686300316398&sdata=AdoxmIeRIp2KQcPhbjFCC6YMosY2rATsPilD9IUvS5k%3D&reserved=0.


Adding definition for MagLev 1.0.0

Any chance someone could test this & get it pulled in? Thanks!

:+1:

What happened to the rake build:maglev? Is that necessary?

@jeremy no, it's not necessary anymore. The install script takes care of generating the extent.

Whoa, this looks like it could stand some improvement. An explanation: There are two shell scripts. Install.sh only needs to be run one time ever, it checks for and adjusts memory parameters and adds a line to /etc services. Then it calls update.sh, which will download a GemStone server file if necessary and then call rake build:maglev and start the stone process running. Since install.sh needs sudo privs, I'd skip it if it's already been run. e.g.
Be smart about whether MagLev has already been installed.
unset MAGLEV_HOME
if [ grep -sc "^gs64ldi" /etc/services -eq 0 ]; then
bash ./install.sh
else
bash ./update.sh
fi

Thanks @Monty. I had asked @timfel about this and after looking at the script it seems running install.sh muiltiple times won't hurt. With that in mind, do you think it's necessary to do this check?

More is explained at http://maglev.github.com/docs/download.html

So this is truly a global install.
Adding a definition for MagLev 1.1 means a 1.0 install would be upgraded; they wouldn't live side by side.
This will break rbenv's expectations.
Perhaps the definition shouldn't be versioned, then.

Not sure exactly what you mean by "truly a global install" but no, I don't think an install of 1.1 would upgrade 1.0.
A 1.1 tarball would be downloaded & if necessary, a different Gemstone VM tarball. Both would be unpacked to ~/.rbenv/versions/ & the 1.1 install script executed. 1.0 would still be there, right?
The only thing global is the shared page cache memory settings but they shouldn't need to change between 2 versions of MagLev.

It doesn't have to be global, you can install and run any number of
stones and VMs. What you might run into problems with is trying to run
the Squeak based Gemtools on two different terminals at once, but I
don't imagine many Rubyists would want to do that ;)
-----Original Message-----
From: Jeremy Kemper
Sent: 09/11/2011 20:07
To: Tim Felgentreff
Subject: Re: [ruby-build] Adding definition for MagLev 1.0.0 (#85)

@jc00ke It doesn't hurt to run install script again instead of checking if only update needs running.
Primary diff is that install requires sudo, so you'll have to enter a password -- which annoys some people.


Prevent stale timeouts from being sent to connection handlers

Fix tcp_server_handler.rs to only send timeouts for recent messages. This means we need to remove the request timer from the timer wheel when we receive an envelope with a correlation id. Since we don't track timer slots for request_ids, and ferris doesn't require this tracking we should probably switch to use ferris for the wheel so we can accomplish this easily.

A temporary workaround is for the connection handler themselves to check the request count on the timeout correlation id to ensure it's still valid.

There are no more connection handlers in 0.5-dev


Removed internal types from OpenTelemetry API surface; removed default parameters from OpenTelemetry API surface.

Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[X] C++ Guidelines
[X] Doxygen docs
[X] Unit tests
[X] No unwanted commits/changes
[X] Descriptive title/description

[X] PR is single purpose
[X] Related issue listed

[X] Comments in source
[X] No typos
[X] Update changelog
[X] Not work-in-progress
[ ] External references or docs updated
[ ] Self review of PR done
[ ] Any breaking changes?

Ping.

Partial review, will continue shortly.
Are there any readme/docs we'd want to update to highlight the coding pattern change?

To my knowledge, there is no coding pattern change. All I've done is hidden a ton of implementation details.
None of the public code changed, neither did the service implementation.


wget gn through https

google is not supporting http any more.   without reverting this change, my ci job will fail to wget.
if wget https is failed during owt-server build, 90% of the root cause is LD_LIBRARY_PATH contains build/libdeps/.../libssl*.so .  and ubuntu ssl/cert lib is ignored.

@taste1981

@taste1981


[Feature]: Support node during build step for building static frontends

Describe the feature
Support Node 18 & 20 lts for building static HTML/CSS/JS which is served by a rust process, example being Astrox where node is needed in the build step with Astro to produce static files which are then served by an axum backend which also provides the backend API. This would be extremely useful as Node based tooling still makes up the bulk of modern UI development and with static site generators like astro becoming more and more popular this could allow shuttle to fit the niche in web hosting that currently Vercel & Netlify completely miss
Suggestion or Example of how the feature would be used
shuttle.toml supporting some additional build steps that may call on in this case node to build out static files which are then served by a rust binary, example project given above
Duplicate declaration

[X] I have searched the issues and this feature has not been requested before.

Great suggestion! We will try supporting it in the new builder #1547

@jonaro00 Since the build containers are linux based maybe integrating just some wrapping over nvm and default enabling corepack to allow simple tooling like below
[tools]
node = { version = "20.11.1", script = "npm install && npm run build" }
node = { version = "20", flags = ["lts", "corepack"], script = "pnpm i && pnpm build" }

or automatically check for build script and automatically install deps based off given lock file and default to npm like vercel does

@versecafe Installing and running node should now be possible with hook scripts on shuttle.dev: https://docs.shuttle.dev/docs/builds#experimental-hook-scripts
Would you like to give it a try?


[Azure.Monitor.Query] Release Query

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


proto: Update generated Go protobuf files.

I don't know why this has changed. But we must update the generated code to keep the Travis check happy.
@pivanof @enisoc @alainjobart
If Travis does not pass here, it's an issue with my local machine.

This change is

LGTM I have the same issue, but travis passed without this earlier today for me...

@pivanof suggested that the different output is caused by different Go versions.
It looks like this is the case. Go 1.7 has changes to the compression library: https://tip.golang.org/doc/go1.7
Given that, I'm considering to do the following changes:

exclude the binary literals for the file descriptors from the proto travis test
stop generating protobufs on every make build because this will create different protobuf files for people who are not using Go 1.7

Can we use a go 1.7 image in Travis?
On Mon, Jul 25, 2016 at 3:01 PM, Michael Berlin<EMAIL_ADDRESS>wrote:

@pivanof https://github.com/pivanof suggested that the different output
is caused by different Go versions.
It looks like this is the case. Go 1.7 has changes to the compression
library: https://tip.golang.org/doc/go1.7
Given that, I'm considering to do the following changes:

exclude the binary literals for the file descriptors from the proto
travis test
stop generating protobufs on every make build because this will
create different protobuf files for people who are not using Go 1.7

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/youtube/vitess/pull/1891#issuecomment-235099735, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEaVMt7qJ5tzwt4z0dYK_gQto8c4CFd8ks5qZTJSgaJpZM4JUjUd
.

Can we use a go 1.7 image in Travis?

We can also do that.
But we deliberately want to run the same Go version which we require as minimum and that's currently 1.6.

The fixes are in place now. Can somebody please review the the changes? :)

So with just the 'ignore gzip diff' commit, why do we need the Makefile change as well?

To avoid confusion for users who don't run Go 1.7:
They would run make build and the protobuf files would get generated with a different content. This will clutter their git status. In the worst case, they'll send us pull requests where the changed protobuf files are included.

LGTM then, makes sense.


add GitHub Integration workflow

Adds integration testing for 6.7 and 7.0 VMWare + VSphere configurations, deploying a minimal cluster on Equinix Metal for each of the two versions.
TODO:

[x] I need to add a secret for S3_URL before this can work. Other variables have already been added. (ideally the bucket is in the same facility or region as the EM deployment)
[x] Push the necessary vmware iso images into the bucket
[x] I think SSH keys are going to be needed in this test (rather than root pass auth) for the SSH provisioners. I intend to resolve https://github.com/displague/metal-project-action/issues/3 so that a dynamically generated project will be created with a SSH key that the workflow can use in subsequent steps.

Fixes #9

The most recent tests failed with:
null_resource.download_vcenter_iso: Creating...
null_resource.run_pre_reqs: Creating...
null_resource.download_vcenter_iso: Provisioning with 'file'...
metal_device_network_type.router: Creating...
null_resource.run_pre_reqs: Provisioning with 'remote-exec'...
null_resource.run_pre_reqs (remote-exec): Connecting to remote host via SSH...
null_resource.run_pre_reqs (remote-exec):   Host: <IP_ADDRESS>
null_resource.run_pre_reqs (remote-exec):   User: root
null_resource.run_pre_reqs (remote-exec):   Password: false
null_resource.run_pre_reqs (remote-exec):   Private key: true
null_resource.run_pre_reqs (remote-exec):   Certificate: false
null_resource.run_pre_reqs (remote-exec):   SSH Agent: false
null_resource.run_pre_reqs (remote-exec):   Checking Host Key: false
null_resource.run_pre_reqs (remote-exec): Connected!
null_resource.download_vcenter_iso: Provisioning with 'file'...
null_resource.run_pre_reqs (remote-exec): mkdir: cannot create directory ‘/root/bootstrap/’: File exists

null_resource.download_vcenter_iso: Provisioning with 'remote-exec'...
null_resource.download_vcenter_iso (remote-exec): Connecting to remote host via SSH...
null_resource.download_vcenter_iso (remote-exec):   Host: <IP_ADDRESS>
null_resource.download_vcenter_iso (remote-exec):   User: root
null_resource.download_vcenter_iso (remote-exec):   Password: false
null_resource.download_vcenter_iso (remote-exec):   Private key: true
null_resource.download_vcenter_iso (remote-exec):   Certificate: false
null_resource.download_vcenter_iso (remote-exec):   SSH Agent: false
null_resource.download_vcenter_iso (remote-exec):   Checking Host Key: false
null_resource.download_vcenter_iso (remote-exec): Connected!
null_resource.download_vcenter_iso (remote-exec): bash: /root/bootstrap/download_vcenter.sh: Not a directory

ea1a07b should fix #13

Merging this now for the added benefits. Any remaining integration issues can be resolved in a follow-up.


Is there any interest in having GH Actions run clippy, rustfmt and tests on PRs?

I can make a PR that will introduce these (at least on Linux, but can also run a matrix for MacOS and Windows)... For public projects like this one there is no fee for running these workflows...

I think currently we use travis to run these commands. I personally think that Github actions would be better, because we wouldn't need another service.
Other than that, I can't say which one is better because I haven't worked with either of them. Maybe someone else can comment on that topic.

Yeah, I haven't used travis in years, but don't know where to look to see if the run passed. I can also just clone that travis workflow into a GH workflow...

Hmm. npm being flaky?
https://travis-ci.org/github/riker-rs/riker/jobs/745630770

I just ran pre-commit run -a against current master and everything passed...

Could be. We had some CI problems before. Maybe @olexiyb can check what went wrong. He worked on the CI stuff.
I think we should work towards a more stable CI. And if Github Actions helps, then i'm all for it. Could you make a test branch in your fork so that we can have a look at it?

Sure, will do.

Here is a PR to my forked master branch that uses cargo audit, clippy, rustfmt (nightly), builds and tests on macOS, Linux, Windows. I also updated the badge on the readme to point at the test results. Will modify this to point at the riker org if you accept this and want a PR.
Note here, that the clippy warnings are exceptionally useful and highly readable:
https://github.com/nothingismagick/riker/pull/3/checks?check_run_id=1452948120

Also if you scroll down to the end, here: https://github.com/nothingismagick/riker/pull/3/files
You will see the clippy comments. If they are found in the current PR's files, they will be inlined there.

Another nice thing with GH Actions is that you can protect a branch and prevent even administrators from merging if any workflows fail... I love that feature.

We could also run all the examples to make sure that they still work too...

I have added pre-commit and changed existing Travis to run pre-commit checks those include clippy, check, fmt and prettier (to enforce default spacing styles)
I would highly recommend keeping pre-commit support as it allows to enforce to run all checks during commit unless Github has a way to run these checks from the command line without PR.

I think you use the latest rust version and Clippy, that's why you may see new errors.

Sure - I didn't add precommit because I just wanted to show the approach, but don't think it would be a big problem to add if there is consensus that this project wants to start using GH Actions.

I have created a pull request https://github.com/nothingismagick/riker/pull/4 to use pre-commit GH action.

I'm currently reviewing GH Actions. Precommit has been an issue on and off since we introduced it, but as @olexiyb mentions it serves as an important step to ensure the integrity of code upfront. Part of the problem has been the integration between GH and Travis changing over time, such as webhooks.
@nothingismagick I'll look at your fork for GH Actions, thanks.


Resolve unlicensed dependencies issues

There are 3 unlicensed dependencies in the project. Some have licenses now, but had not with the package version used. Maybe upgrading these packages can fix this.
We should try to see if we can really resolve these dependencies before ignoring them.

PR #473 fixes some issues.
For buffer, we use jszip instead of unzipper. We already depend on jszip anyway.
For cycle, we use inquirer instead of prompt. Almost all tasks use inquirer. Only create-user used prompt, so it's not necessary.
Unfortunately, for @mapbox/jsonlint-lines-primitives, there is no way to not use it as long as we use mapbox-gl-js, which won't be dropped in a foreseeable future (or will it?...)

We know we want to drop mapbox, so we at least know the path to fixing that one. We could mark it as "fine" in fossa for the time being.

The last issue was marked as ignored in fossa