Resizing terminal

curses doesn't seem to detect any change in getmaxyx after a resize.  I've gone so far as to implement my own signal handler for SIGWINCH and reinitialize the screen if there is a resize, but still no changes.  Have no idea what's going on.

os.get_terminal_size() from the os module does seem to give correct terminal dimensions even with the keyboard listener, but naive implementations have run into key errors -- I may pursue this further though.

For ref : 3c2804207a25c41f04262649f8ccdd3a234e63d0
So, no problems with os.get_terminal_size() ?

os.get_terminal_size works for me with the Listener threads on Ubuntu at least.


Replace images under the #SILKLIFE

Hello everyone.
SILK Life encompasses a range of activities that align with our SILK website's values and mission to empower people through cooperation, culture, and social interaction. Choose the images that add a clear vision of the services and activities we offer. The new images should showcase our services and events, and represent the core values of Strength, Intelligence, Love, and Kindness.
Here are the specifications for the new images:

File format: JPEG or PNG
Right-click on the image, check "Inspects" to know the dimension (length and width) of the image, and choose a new image according to that dimension.

Thank you.

You can use a template like this for your issues:
Issue Template
Hello GitHub People,
We're in the process of completing the SILK Corp website, and we've noticed that the image on the homepage needs to be updated. Could someone please update the image to reflect our current mission and values?
Here are the specifications for the new content/image:

Dimensions: 1200px x 800px
File format: JPEG or PNG
Content: (Write a description for your image for example the image should reflect our mission of providing a peaceful community of people while empowering their mental, physical, and emotional well-being. Please choose an image that is visually appealing and relevant to our brand.)

Thanks for your help!

Provide enough info so issues make more sense to everyone.

I've updated this issue.

@Remy-Reveltek, I am going to work on adding an image in the Art section of #SILKLIFE.

@duafatimaa Can we hop on a call for 10 minutes?

Request to Close
This issue is solved, please close it.


Extend event framework to support a standard serializable payload

As this is essentially opening up a new data type that can be put 'on the wire', (including the scope to have pubsub sinks in a similar fashion to the existing package publishers) does it make sense to have a defined expectation on what constitutes an 'event'?.

I think that the definition of an event can remain quite flexible, the exact reasoning behind a new event can be discussed during the implementation and review of specific event additions. As for how verbose this becomes, we can review this at a later date but the sinks can dispatch events in a filterable manner e.g. to specific type topics for a kafka sink (for example).

The event introduced here exercises all of the methods provided by the interface (component, type, message) when generating the logrus output. Could DispatchEvent() potentially pass a struct (validated with a schema for expected fields, format etc as with packages) constructed from the interface methods to the event handlers AddEvent() instead of the event itself?

Yeah I think this might need some tweaking to have an easily method of encoding data for transmission. We might want some form of standardised event payload which the individual Event implementations can populate. The current method of having the sink switch based on the event type isn't very extendable for many sinks and many events.
Originally posted by @Qinusty in https://github.com/ossf/package-feeds/pull/89#issuecomment-827558722

Just so it's not lost, logging this comment as an example of a usecase for transmitting additional/optional data which could be supported by events supporting a payload that allows for extensibility.
https://github.com/ossf/package-feeds/pull/89#discussion_r621221950


Not recognizing Python v3.9.5

windows-build-tool does not seem to be properly recognizing my Python v3.9.5 installation as it re-downloads Python v.2.7.15 (python-2.7.15.amd64). Furthermore, according to recent commits, I was under the assumption windows-build-tools now uses Python 3 instead of Python 2, so why is it still downloading Python 2? I have tried this many times even on a prior version of Windows 10. I also tried without installing Python and it still defaulted to 2.7.15 and downloaded it. I've cleared cache and verified. Remove all traces of Python and VS Build Tools. No luck.
According to https://github.com/felixrieseberg/windows-build-tools/blob/master/src/utils/get-is-python-installed.ts I'd reckon any Python 3 version is supported. Not really sure why this is happening.
OS: Windows 10 Pro - Version 20H2 Build 19042.964
Node: v16.1.0
windows-build-tools: v5.2.2 (latest according to npm)
Command: npm install -g windows-build-tools

There has not been a release of windows-build-tools with those commits yet.
(Apparently, there are no core maintainers here with access to publish releases, or those that have access also have low bandwidth or availability to work on this project. So it is almost/practically unmaintained, in a way.)


Export passwords and secrets to yaml and json files

We can export saved passwords from the gateway using restman by modifying the restman URL and parameters:

Add encryptSecrets=true as a URL parameter
Add L7-key-passphrase as a header, with an encryption passphrase as value

With that in place, the bundle comes from the gateway with the passwords.
Provide a way to decrypt them.
Change the stored passwords and jdbc connections exporter to write the decrypted password to the yaml file.
Verify that's working by building a bundle using the developer plugin and loading into the gateway

This will not be done due to the implementation required to decrypt passwords coming from the gateway would be exposed to public in this git repo, which is a security issue.


Warning: componentWillReceiveProps is deprecated

Hello,
I am using the component and I got a warning when using a decrepit component.
My installation has the following versions of react
    "react": "16.8.6",     "react-native": "0.60.4",     "react-native-animatable": "^1.3.2",
And the message is as follows
ReactNativeJS ▶ Warning: componentWillReceiveProps is deprecated and will be removed in the next major version. Use static getDerivedStateFromProps instead.
│
│ Please update the following components: withAnimatable(View)
│
│ Learn more about this warning here:
└ https://fb.me/react-async-component-lifecycle-hooks

same here

I had the same issue and eventually rewrote the library. Maybe this is also a solution for others, see https://github.com/rodw1995/react-native-pincode-input-component

@VasquezLab
Thanks for reporting and you can also use better implementation with better maintainability:  https://github.com/retyui/react-native-confirmation-code-field


Add FreeBSD Support

Running FreeBSD 13.0-RELEASE with current versions of go, rust and gmake installed:
build-rust-release works and finishes without errors (only requires a modification of SHARED_LIB_EXT = "so" for FreeBSD OS detection in the Makefile).
build-go doesn't work. Here is the output:
$ gmake build-go
go build ./...
go: downloading github.com/stretchr/testify v1.7.0
go: downloading github.com/syndtr/goleveldb v1.0.1-0.20200815110645-5c35d600f0ca
go: downloading gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c
# github.com/CosmWasm/wasmvm/api
ld: error: undefined symbol: analyze_code
>>> referenced by cgo-gcc-prolog:56
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_analyze_code)
>>> referenced by cgo-gcc-prolog:609
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_analyze_code)

ld: error: undefined symbol: execute
>>> referenced by cgo-gcc-prolog:90
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_execute)
>>> referenced by cgo-gcc-prolog:639
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_execute)

ld: error: undefined symbol: get_metrics
>>> referenced by cgo-gcc-prolog:113
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_get_metrics)
>>> referenced by cgo-gcc-prolog:658
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_get_metrics)

ld: error: undefined symbol: ibc_channel_close
>>> referenced by cgo-gcc-prolog:146
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_ibc_channel_close)
>>> referenced by cgo-gcc-prolog:687
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_ibc_channel_close)

ld: error: undefined symbol: ibc_channel_connect
>>> referenced by cgo-gcc-prolog:179
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_ibc_channel_connect)
>>> referenced by cgo-gcc-prolog:716
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_ibc_channel_connect)

ld: error: undefined symbol: ibc_channel_open
>>> referenced by cgo-gcc-prolog:212
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_ibc_channel_open)
>>> referenced by cgo-gcc-prolog:745
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_ibc_channel_open)

ld: error: undefined symbol: ibc_packet_ack
>>> referenced by cgo-gcc-prolog:245
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_ibc_packet_ack)
>>> referenced by cgo-gcc-prolog:774
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_ibc_packet_ack)

ld: error: undefined symbol: ibc_packet_receive
>>> referenced by cgo-gcc-prolog:278
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_ibc_packet_receive)
>>> referenced by cgo-gcc-prolog:803
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_ibc_packet_receive)

ld: error: undefined symbol: ibc_packet_timeout
>>> referenced by cgo-gcc-prolog:311
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_ibc_packet_timeout)
>>> referenced by cgo-gcc-prolog:832
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_ibc_packet_timeout)

ld: error: undefined symbol: init_cache
>>> referenced by cgo-gcc-prolog:337
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_init_cache)
>>> referenced by cgo-gcc-prolog:854
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_init_cache)

ld: error: undefined symbol: instantiate
>>> referenced by cgo-gcc-prolog:371
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_instantiate)
>>> referenced by cgo-gcc-prolog:884
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_instantiate)

ld: error: undefined symbol: load_wasm
>>> referenced by cgo-gcc-prolog:395
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_load_wasm)
>>> referenced by cgo-gcc-prolog:904
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_load_wasm)

ld: error: undefined symbol: migrate
>>> referenced by cgo-gcc-prolog:428
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_migrate)
>>> referenced by cgo-gcc-prolog:933
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_migrate)

ld: error: undefined symbol: pin
>>> referenced by cgo-gcc-prolog:449
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_pin)
>>> referenced by cgo-gcc-prolog:950
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_pin)

ld: error: undefined symbol: query
>>> referenced by cgo-gcc-prolog:479
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_query)
>>> referenced by cgo-gcc-prolog:976
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_query)

ld: error: undefined symbol: reply
>>> referenced by cgo-gcc-prolog:512
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_reply)
>>> referenced by cgo-gcc-prolog:1017
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_reply)

ld: error: undefined symbol: save_wasm
>>> referenced by cgo-gcc-prolog:536
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_save_wasm)
>>> referenced by cgo-gcc-prolog:1037
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_save_wasm)

ld: error: undefined symbol: sudo
>>> referenced by cgo-gcc-prolog:569
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_sudo)
>>> referenced by cgo-gcc-prolog:1066
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_sudo)

ld: error: undefined symbol: unpin
>>> referenced by cgo-gcc-prolog:590
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_C2func_unpin)
>>> referenced by cgo-gcc-prolog:1083
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_unpin)

ld: error: undefined symbol: release_cache
>>> referenced by cgo-gcc-prolog:991
>>>               $WORK/b047/_x004.o:(_cgo_d3f6466c8ed4_Cfunc_release_cache)

ld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
cc: error: linker command failed with exit code 1 (use -v to see invocation)
gmake: *** [Makefile:37: build-go] Error 2

Have a look at api/link_*.go. There you see a build condition and different link commands depending on the system. I guess linux in both cases makes that both link_*.go are excluded and the linkage lines
// #cgo LDFLAGS: -Wl,-rpath,${SRCDIR} -L${SRCDIR} -lwasmvm
import "C"

is missing.

@webmaster128 And clue on how to resolve this?
I should have mentioned that I'm not a developer/programmer and that I have no experience with go.

@Moonshine-cc if that is the case I see very little chance for FreeBSD support any time soon. We have to build the library for each target system individually which is quite hard for Linux/Mac/Windows on x86/ARM already and this is the first time I hear about the desire for building for FreeBSD.
What's your motivation for targetting this system?

@webmaster128 With FreeBSD it's possible to use Linux binaries and libraries natively thanks to its Linux Binary Compatibility Layer, which makes use of CentOS 7 (if interested in the details, see Chapter 10. Linux Binary Compatibility of the FreeBSD handbook.
I'm running a set of validators on a server powered by FreeBSD, which is an extremely pleasant experience so far (way better then with the usual Linux distributions).
Thanks to the Linux Binary Compatibilty Layer and all the needed components (like go and rust) available natively, I could make almost all validator projects that I have tried run without problems so far, except the latest one that made use of CosmWasm.

Oh, that's interesting. Our .so is built on a CentOS 7 system. So it might just work with this diff: https://github.com/CosmWasm/wasmvm/pull/313

@webmaster128 Seems to have worked:
$ go build ./...
go: downloading github.com/tendermint/tm-db v0.6.7
go: downloading github.com/stretchr/testify v1.7.0
go: downloading github.com/google/btree v1.0.0
go: downloading github.com/syndtr/goleveldb v1.0.1-0.20200815110645-5c35d600f0ca
go: downloading gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c
go: downloading github.com/davecgh/go-spew v1.1.1
go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading github.com/golang/snappy v0.0.1

No errors, but now I'm puzzled, what's the result?
(I've just cloned the repo, applied the diff and only ran go build ./... to check what's going to happen)

Glad to hear that.
Now the question is how you want this deployed. The Linux .so is built by the CI and checked into git for every change. See https://github.com/CosmWasm/wasmvm/tree/main/api for the .so and .dylib. I would like to do that for FreeBSD too because it comsumes a lot of space in git and I don't know if I found a FreeBSD CI system. If you don't want to build everything manually and patch the chain for every upgrade using a local version of wasmvm, it's probably better to use the Linux build.

@webmaster128 Sorry, not really sure what you mean. The already present Linux libwasmvm.so can not be used on FreeBSD, so that library has to be built natively on a FreeBSD system, which is what I just did. I don't know if this can be solved in any better way, but as long as I'm able to build libwasmvm.so locally, just having the mentioned changes do the trick.

But didn't you say it can be used via CentOS 7 compatibility mode on FreeBSD?

That's what I thought as well, but it didn't work. This is what it looks like with the Linux libwasmvm.so:
$ ldd craftd
craftd:
        libthr.so.3 => /lib/libthr.so.3 (0x803d3e000)
        libwasmvm.so =><EMAIL_ADDRESS>(0x803e00000)
        libc.so.7 => /lib/libc.so.7 (0x8043c4000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x803d6b000)
        librt.so.1 => /usr/lib/librt.so.1 (0x803d84000)
        libpthread.so.0 => not found (0)
        libm.so.6 => not found (0)
        libdl.so.2 => not found (0)
        libc.so.6 => not found (0)
        ld-linux-x86-64.so.2 (0)

I'm not able to explain what the problem is with this (looks like the Linux binary can't find the needed libraries in the right place, and even with some manual symlinking, it then said something about a wrong glibc version).
This is what it looks like with the FreeBSD libwasmvm.so:
$ ldd craftd
craftd:
        libthr.so.3 => /lib/libthr.so.3 (0x803d3e000)
        libwasmvm.so =><EMAIL_ADDRESS>(0x803d6b000)
        libc.so.7 => /lib/libc.so.7 (0x804076000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x804487000)
        libm.so.5 => /lib/libm.so.5 (0x8044a0000)

So the only way to go is to build libwasmvm.so natively for FreeBSD.

@webmaster128 So it's working, but I'm not sure how you could implement the required patches to make it universally usable. The diff for the two api/link_*.go files is OK, but oddly the OS detection for determining the library extension isn't.
I have GNU Make installed on FreeBSD, so I'm compiling the project with gmake build and although it supposedly should work that way, I'm getting "Need an operator" errors on the used ifeq / elseif / endif in lines 12, 14 and 22, which is why I simply have commented the whole checks out and made "so" the default:
SHARED_LIB_EXT = "so" # File extension of the shared library
#ifeq ($(OS),Windows_NT)
#       SHARED_LIB_EXT = dll
#else
#       UNAME_S := $(shell uname -s)
#       ifeq ($(UNAME_S),Linux)
#               SHARED_LIB_EXT = so
#       endif
#       ifeq ($(UNAME_S),Darwin)
#               SHARED_LIB_EXT = dylib
#       endif
#endif

Any ideas?

I think it should not be too hard to convert the main Makefile into a set of shell scripts. We hardly use any make feature there anyways. If you want to roll out make build, you can just do:
(cd libwasmvm && cargo build --release)
cp libwasmvm/target/release/libwasmvm.so api

cp libwasmvm/bindings.h api

go build ./...


Container app stopped logging to Azure Monitor

This issue is a: (mark with an x)

[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
An ACA environment in West Europe stopped logging to Azure Monitor log destinations on 11th November at 01:02 UTC. No logs are emitted to either ContainerAppSystemLogs or ContainerAppConsoleLogs. The last logs received were for container k8se-localproxy with Log detail logger of LocalProxyClient.
Until 01:01 UTC the following logs repeated:
Failed to receive from stream.
Getting latest ServiceRedirectInfos.
Initialized
Start listening services redirect info updates

After which the following logs repeated about 500 times:
Failed to receive from stream.
Getting latest ServiceRedirectInfos.
Failed to call GetServiceRedirectInfos
Getting latest ServiceRedirectInfos.
Failed to call GetServiceRedirectInfos
Getting latest ServiceRedirectInfos.
Failed to call GetServiceRedirectInfos

Following which all logging stopped. There have not been any logs for several days.

Hi @maskati
Is the issue still happening? If so, can you please send an email with your subscription id and environment name to acasupport at microsoft dot com and we will investigate ASAP.

It was a bug and fix already deployed, close the issue

Getting the same bug with container app job

I can confirm that we are also getting this issue...
{"level":"error","ts":"2023-12-05T11:06:36.712622994Z","logger":"LocalProxyClient","msg":"Failed to call GetServiceRedirectInfos","error":"rpc error: code = Canceled desc = context canceled","stacktrace":"main.run\n\t/__w/k4apps/k4apps/cmd/proxy/main.go:139\nmain.main\n\t/__w/k4apps/k4apps/cmd/proxy/main.go:103\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}


Switch atsign bug

- What I did 1. Replace isEncrypted metadata with checking if key contains public: to decrypt the value.
2. Fix switch atsign bug.
- How I did it
- How to verify it
- Description for the changelog

LGTM


fix rss icon link error

The RSS icon link can not be prepended site.url，because site.url mostly is "http://localhost:4000/XXX" for testing, it's better to not prepend site.url

@huster-zhangpeng
thanks for your PR! currently, site.url and site.baseurl represent each domain and path. but site.baseurl and site.url are used at the same time almost always :sweat_smile: so I think it's a nice idea to integrate site.url and site.baseurl TOTALLY. i'm doing that by myself on #11, thanks a lot :wink:


MultiFileSelector: path argument is not taken into account in default constructor

I'm trying to use MultiFileSelector as presented in panel 0.12.6 doc on Debian/Testing with python 3.9
Description of expected behavior and the observed behavior
multiple_files          = param.MultiFileSelector(path='../../*/*.py?', precedence=0.5)

I expect the multifile selector to list only the requested files. In fact it only displays file in os.getcwd()
Looking at the __init__.py code for MultiFileSelector we can see that path argument is not used in the default constructor...
Complete, minimal, self-contained example code that reproduces the issue
import param
class MRecordData(param.Parameterized):
    fvariable  = param.MultiFileSelector(path='./data')

As far as I can tell, Param is working as designed here:
import param
class F(param.Parameterized):
    fs = param.MultiFileSelector(path='/usr/share/*')

f = F()
f.fs

I.e., it's checking that the default or subsequently defined values are included in the list of files specified by path. Is this maybe a bug report for Panel, indicating that Panel isn't giving the expected options? Feel free to re-open this if I've misunderstood what the bug report is meant to be.


Allow set custom authentication errors.

This patch allow send custom authentication errors, for example, when overriding default 'authenticate' listener.

@PSyton  you have conflict to fix.

@PSyton you removed lot of "socket.disconnect();"


endpoint

[Enter feedback here]

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

ID: dd333ae2-34f6-4afd-cdb1-db72303a5736
Version Independent ID: 5fc52fe8-dade-b8b7-7126-c4e7dd902e62
Content: Office 365 IP Address and URL web service - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/microsoft-365-ip-web-service.md
Service: microsoft-365-enterprise
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@keonglee1978 We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if you see an improvement is required in the specific area of this documentation. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


GEODE-6779: Create disk store command should only return when the MBeans are available

Co-authored-by: Sarah Abbey<EMAIL_ADDRESS>Co-authored-by: Jens Deppe<EMAIL_ADDRESS>Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[x] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@Petahhh @jmelchio @jackw26 @sabbeyPivotal

I made a change so that the disk store creation gfsh commands now also check that the command doesNotContainOutput("Did not complete waiting"). I think this effectively serves the same purpose that you were suggesting.


Unit testing, how can we perform process testing using async and await keywords.

Following #21,
The example you provided works for the promise chaining processing style.
This is not the writing you recommanded to me, I have this two process that require unit test:
Global logic of logout, will be present on every pages:
export const getLogoutLogic = createLogic({
  type: SUBMIT_LOGOUT_REQUEST, // trigger on this action
  latest: true, // use response for the latest request when multiple
  async process({ pages, authService, forwardTo }, dispatch, done) {
    try {
      const success = await authService.logout();
      dispatch(sendingLogoutRequest(false));
      forwardTo(pages.pageLogin.path);
      dispatch(onSuccessLogoutRequest(success));
    } catch (err) {
      dispatch(sendingLogoutRequest(false));
      forwardTo(pages.pageLogin.path);
      dispatch(onErrorLoginRequest(err));
    }
    done();
  },
});

Login logic, will be present on LoginPage:
export const getAuthorizeLogic = createLogic({
  type: SUBMIT_LOGIN_REQUEST, // trigger on this action
  cancelType: LOCATION_CHANGE, // cancel if route changes
  latest: true, // use response for the latest request when multiple
  async process({ authService, forwardTo, pages, action }, dispatch, done) {
    const { username, password } = action.data;
    try {
      const jwt = await performLogin(authService, username, password);
      dispatch(onSuccessLoginRequest());
      dispatch(jwtLoaded(jwt));
      forwardTo(pages.pageDashboard.path); // Go to dashboard page
    } catch (err) {
      dispatch(onErrorLoginRequest(err));
      forwardTo(pages.pageLogin.path); // Go to dashboard page
    }
    done();
  },
});

async function performLogin(authService, username, password) {
  await authService.preLogin();
  await authService.login(username, password);
  const codeRes = await authService.code(oauthClient.clientId, oauthClient.redirectUri);
  const code = getParameter('code', codeRes.url);
  const jwt = await authService.token(oauthClient.clientId, oauthClient.clientSecret, code,
  return jwt;
}

In your example:
const resultPromise = getAuthorizeLogic.process({
    pages,
    authService,
    action,
    forwardTo,
    getState,
    requestUtil
}, dispatch, done);

Even with a mock for my test, this doesn't return a promise, but instead undefined because I don't do any return in my process.
I am also surprise there is no otherway to test the code "line by line", for example, for await return value checking.
I also need a way to test when errors happen, so my app doesn't get unsynced with it's store.
Thanks in advance.

The way I think about it is that it is great to develop nice testable API's for our own code that don't depend on any specific framework thus they can be independently tested and reused in many interesting ways. Then I use code like redux-logic to tie that API to the redux API (mapping things from actions and dispatching results).
Breaking things out keeps things smaller and more focussed and usually makes testing easier. It is great to be able to test API code without having to deal with actions and dispatching. It is still good to have tests at different levels (unit, integration, system) to make sure all that works right, but we look for different things at the various levels.
So with our example above, you can test your API performLogin as a whole to make sure it does everything properly in order, and you can test each individual step (authService.preLogin, authService.login, ...) to make sure they all do the right thing and return errors appropriately.
Then when you get to testing logic code, you are primarily testing a few happy and failure paths just to make sure that everything is being mapped properly (inputs from actions, invoking the API's, and dispatching data as actions, and that errors are being dispatched as well).
In that way we are covering things at multiple levels where it makes sense but not getting bogged down in trying to reproduce every combination when working at the higher levels.
As mentioned in #21 (and for anyone coming to this conversation here) I usually do some testing of the various hooks from createLogic (the object shape returned by createLogic is basically the same as is passed in with some defaults applied), so you can test the fooLogic.process (or fooLogic.validate, fooLogic.tranform) hook by passing in the deps you use like getState, action. I have usually passed in an expect.createSpy for dispatch so I can check directly what is dispatched.
After that low level logic unit testing, I also do some integration testing at the middleware or store level so that I can verify that everything is configured and declared properly.
However I am thinking we would benefit from a helper lib that makes that a little easier to setup. It is a bit of busywork to set those things up, so I think that could be streamlined a bit. I'll put together a gist of what it could look like to see what you and others think. I'll link to it here shortly.

Take a look at this redux-logic-test gist for the test helper API and let me know what you think

I created a request for comment RFC issue for discussing the API of the new test helper #25

Any update on the release that ? I really need this, as all our code coverage get reduced because of that. It's not very nice. :!

@kopax Sorry for the delay, I just wanted to make sure I allowed some time for input from people, but it seems that this will be a good start. I should be able to work on this soon.

@jeffbski Sorry for the delay myself, I started to get to go with redux-logic, I had to teach my team how to use it and we had some other topic. I'll close as soon as it is confirmed that we know how to test every logic, which is not the case yet.

Thanks! I know how it is. We get backed up on things and have to prioritize. I deal with this daily.


HDD Wake during Sleep

Running mdf.1m.sh . The app periodically querys HDD's and therefore wakes up my external HDD about once a minute. I woke up to it spinning up and down repeatedly. Any way to configure script refresh rate individually? And not allow scripts to run when sleeping?

Change the 1m to 30m or 2h or 1d (see here)

Oh. Well that was easy.
Would still be nice to not have it run when OSX is sleeping. It does for some reason which is peculiar.

Maybe have a look at the Energy Saver settings - could it be that Power Nap is preventing your laptop from "real" sleeping?

I can't be sure if my computer is still waking from sleep. I set the script to run bi-hourly. Thats 4 times a night at most so I'm okay with that.
PS: It wasn't power nap. Thanks guys for the help!


[master] Bump Mesos to nightly master 751ef19

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/84749967a1c1384f75c3c017bda45a85eea67787...751ef19270ca2a9d82cff5946e1820d28e8e508f

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

Closed in lieu of https://github.com/dcos/dcos/pull/3318


Login fails when password contains a non-ASCII character

I was trying to set-up the Home Assistant Litter-Robot integration when I was unable to log in to my litter-robot account.
Digging through the logs I found out that the issue stems from this library.
The error I got is the following:
UnicodeEncodeError: 'ascii' codec can't encode character '\xa3' in position 15: ordinal not in range(128)
A work-around was to remove the pound symbol (£) from my password.

2022.8.0b0 should fix this as well as add support for the Litter-Robot 4
https://github.com/home-assistant/core/pull/75790

Resolved in 2022.8.0


Added parameter dumps_default to JsonObjectSerializer.init

Autobahn-python current implementation does not allow to serialize to JSON non standard types of value in WAMP message kwargs/args (eg. kwargs={'amount': decimal.Decimal('10.25')}).
I added parameter dumps_default to JsonObjectSerializer.__init__ in order to allow customize JSON dumping of non-standard types.
Thanks to this change we will be able to do the following:
def dumps_default(obj):
    if isinstance(obj, decimal.Decimal):
        return str(obj)
    raise TypeError('Unable to convert object of {} to JSON'.format(type(obj)))

serializers = [JsonSerializer(dumps_default=dumps_default)]
server = WampRawSocketServerFactory(factory, serializers)

Codecov Report

Merging #1080 into master will decrease coverage by <.01%.
The diff coverage is 62.5%.

@@            Coverage Diff             @@
##           master    #1080      +/-   ##
==========================================
- Coverage   41.84%   41.83%   -0.01%
==========================================
  Files          69       69
  Lines       13207    13215       +8
  Branches     2204     2205       +1
==========================================
+ Hits         5526     5529       +3
- Misses       7257     7261       +4
- Partials      424      425       +1

Impacted Files
Coverage Δ

autobahn/wamp/serializer.py
79.45% <62.5%> (-1.35%)
:arrow_down:

Continue to review full report at Codecov.

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

WAMP does not support non-standard, serializer specific types, because those cannot be transparently converted between serializers.

one more note: Autobahn/Crossbar support a feature called "WAMP payload transparency". using that you can use any custom types: https://github.com/crossbario/crossbar-examples/tree/master/payloadcodec
this feature is not yet in the official WAMP spec ..


doesn't show

Any thoughts on why it doesn't show up? I know that showWithStatus is getting invoked, but it just doesn't show up. 6 or 7 doesn't matter, using the simulator.

Call this in didFinishLaunchingWithOptions:
SVProgressHUD.setContainerView(UIApplication.shared.keyWindow)


Cleanups to JPetLogger

Display thread id only when multi threading is enabled, reorder displayed information

I removed JPetManager dependency. Beside of that I refactored JPetLogger to reduce usage of getInstance() and hide it in static function.
Example log message:
1:  the option '--file' is required but missing [JPetManager.cpp:parseCmdLine@94]
2:  While parsing command line arguments [JPetManager.cpp:run@45]
3:  ======== Starting processing all tasks: 17.02.2019 20:11 ========
[JPetManager.cpp:run@54]
4:  No local database file found. [JPetParamManager.cpp:generateParamManager@37]


Password Protect PDF

Hello,
I want to open password protected file, but unable to do that, a normal pdf file is working fine,
Can you please work on that, it will be better if password will be pass through function before it load, so security will increase for pdf to download from temp directory.
Hope you understand my requirement, No one can download pdf or we can protect them via password.
Thanks in advance

I'm not shure if I fully understand your requirement.

You would like to open password protected pdfs with the plugin
Password should be somehow passed to viewDocument as plain text

Is that correct?
Which platforms are you playing with?

I am looking for both iOS and Android.
My requirement is I have pdf and do not want anyhow it will be copied, so I though about I will create a pdf with a password and then the password would be saved in database. Now when we open pdf through document viewer, then I will pick that password from database and pass it to pdf so it will be open. if any one available to get password then they did not have password. By this way we can put a security layer over pdf. Hope you will understand what I am looking for.
Thanks

I understand. But:
The plugin is designed to view pdfs embedded in the app. I you don't provide a link to the user, where he can download or send the pdf, he won't be able to obtain a copy of the file.
so why do you need password protection?

Thanks for your reply,
Here my requirement is little bit more, I have pdf for books, and they can be increase, I am creating app where user can pick from list of pdfs from server for whom they have authentication.
In future number of pdfs can be increased, even the size of pdfs are too big, so putting them inside app means it will make app size too big. and for new pdf I have to build again and published in App store.
Hope you will understand my requirement, waiting for your reply or suggestion so can finish my app.
Thanks in advance

whenever a user wants to view a pdf:

download pdf from server to a temp file on device
view temp file in viewer
delete temp file(s) via onClose handler or when app is started/stopped

to increase performance and avoid duplicate donwloads during a session you should delete temp files only when the app is stopped or started.
temp files are protected against external access on android and iOS. On windows the user may access them via windows explorer (if  knows how to do that).


Add PermissionOffer and PermissionOfferResponse

Add RLMSyncPermissionOffer and RLMSyncPermissionOfferResponse.
Move RLMSyncManagementObjectStatus and function to RLMSyncUtil.
Unit tests are split another PR because tests don't work until new ROS will be released.
CC @mrackwitz @jpsim

@kishikawakatsumi now that Realm Object Server beta 4.8 is out, can you update this PR to include the tests you mentioned? Also needs a rebase.

@jpsim PermissionOffer and PermissionOfferResponse have not worked yet even beta 4.8.
https://github.com/realm/realm-sync-services/blob/master/src/node/services/permission/service.js#L27-L30
https://github.com/realm/realm-sync-services/pull/504

@jpsim @mrackwitz @bigfish24 Add unit tests for PermissionOffer and PermissionOfferResponse

@kishikawakatsumi could you share steps that could help reviewers actually test this? Which version(s) of upstream dependencies should be built to try this out?

@jpsim This PR needs a new release of ROS that includes https://github.com/realm/realm-sync-services/pull/504. I've changed the state to "in progress" for now.

@kishikawakatsumi can you please update this to use ROS v1.0.0-BETA-4.14 that was just released? Hopefully your tests will pass with that.
Also there's a merge conflict in the changelog now.

@jpsim @mrackwitz This PR gets ready for review again. Could you review this?
This PR adds RLMSyncPermissionOffer, RLMSyncPermissionOfferResponse, SyncPermissionOffer and SyncPermissionOfferResponse to ObjC and Swift.
These model classes should be same as realm-sync-services.
The test confirms that a token can be obtained through PermissionOffer, and then PermissionOfferResponse works correctly using the token.
Also if PermissionOffer expires, the offer cannot be used.
PermissionOfferResponse doesn't work with invalid tokens.

@mrackwitz I agreed that id properties should be a primary key. But on current ROS implementation, it will abort if there is a difference between ROS models and client models. To be strict, RLMSyncPermissionChange and RLMSyncPermissionOffer work fine despite changing id to a primary key. But if I change RLMSyncPermissionOfferResponse's id to a primary key, ROS aborted.
2016-12-20T10:15:33.702Z - detail: client: Using already open Realm file: ./realm-object-server/listener/realms/c62d2e0d8ba14342b6ca2a9bb7c8edc1.realm
2016-12-20T10:15:33.703Z - debug: permission: Realm at path /4aa9ef105fff5dd6c96cc68323a6d3aa/__management has changes
2016-12-20T10:15:33.703Z - debug: permission: Opening /4aa9ef105fff5dd6c96cc68323a6d3aa/__management
2016-12-20T10:15:33.704Z - detail: permission: management-Realm of user 4aa9ef105fff5dd6c96cc68323a6d3aa has changes
2016-12-20T10:15:33.704Z - debug: permission: Found 0 unprocessed objects of PermissionChange
2016-12-20T10:15:33.715Z - debug: permission: Found 0 unprocessed objects of PermissionOffer
2016-12-20T10:15:33.716Z - debug: permission: Found 1 unprocessed objects of PermissionOfferResponse
2016-12-20T10:15:33.716Z - detail: permission: Process PermissionOfferResponse(id='E6AC8E42-0...')
2016-12-20T10:15:33.722Z - debug: permission: Opening management-Realm /e8df750a29a035504a707da71df7204d/__management
2016-12-20T10:15:33.754Z - error: permission: Error when processing PermissionOfferResponse(id='E6AC8E42-0...'): The following changes cannot be made in additive-only schema mode:
- Primary Key for class 'PermissionChange has been removed.
- Primary Key for class 'PermissionOffer has been removed.
- Primary Key for class 'PermissionOfferResponse has been removed.
2016-12-20T10:15:33.757Z - debug: permission: Closing /4aa9ef105fff5dd6c96cc68323a6d3aa/__management
libc++abi.dylib: terminating with uncaught exception of type realm::js::Exception<realm::node::Types>: Error: The following changes cannot be made in additive-only schema mode:
- Primary Key for class 'PermissionChange has been removed.
- Primary Key for class 'PermissionOffer has been removed.
- Primary Key for class 'PermissionOfferResponse has been removed.
make: *** [serve] Abort trap: 6

Can't set status; build failed.

From the discussion on our Slack, we decided to accept breaking changes. Make id property as a primary key. eae4fdb

Marking as "in-progress" until @kishikawakatsumi can resolve the test failures.

@jpsim This PR now ready for review again.

I confirmed the tests passed with REALM_SYNC_VERSION=1.0.0-BETA-6.5 and REALM_OBJECT_SERVER_VERSION=1.0.0-BETA-5.1-pre.

It seems rebasing a wrong branch. I'll fix soon.

Can't set status; build failed.


Inconsistent calibration matrix in TUM-RGBD dataset

After downloading fr1_desk dataset, its calibration_matrix.txt file shows that the calibration matrix is the one from the freiburg3 dataset of TUM-RGBD benchmark dataset (see here).
Shouldn't it be the calibration matrix from the freiburg1 dataset?

Paste the issue wrongly. Shifted it to EVOLIN dataset page and create a new commit here.


custome buildpack error

Hi
I use custome buildpack Scalingo and when push app error accured! i push app with default buildpack and every thing is ok. I trace code
https://github.com/Scalingo/php-buildpack
-----> Fetching custom buildpack
remote: + exit_code=1
remote: + set -e
remote: + [[ 1 -eq 10 ]]
remote: + implemented=1
remote: + [[ 1 -ne 0 ]]
remote: + exit 1
remote: + exit_code=1
remote: + set -e
remote: + [[ 1 -eq 10 ]]
remote: + implemented=1
remote: + [[ 1 -ne 0 ]]
remote: + exit 1
remote: + exit_code=1
remote: + set -e
remote: + [[ 1 -eq 10 ]]
remote: + implemented=1
remote: + [[ 1 -ne 0 ]]
remote: + exit 1
remote: + exit_code=1
remote: + set -e
remote: + [[ 1 -eq 10 ]]
remote: + implemented=1
remote: + [[ 1 -ne 0 ]]
remote: + exit 1

exit_code=0
set -e
[[ 0 -eq 10 ]]
implemented=1
[[ 0 -ne 0 ]]
for script in '$PLUGIN_PATH/*/commands'
set +e
/var/lib/dokku/plugins/mariadb/commands git-receive-pack ''''sample''''
exit_code=0
set -e
[[ 0 -eq 10 ]]
implemented=1
[[ 0 -ne 0 ]]
for script in '$PLUGIN_PATH/*/commands'
set +e
/var/lib/dokku/plugins/nginx-vhosts/commands git-receive-pack ''''sample''''
++ dirname /var/lib/dokku/plugins/nginx-vhosts/commands
source /var/lib/dokku/plugins/nginx-vhosts/../common/functions
++ set -eo pipefail
++ [[ -n 1 ]]
++ set -x
case "$1" in
exit 10
exit_code=10
set -e
[[ 10 -eq 10 ]]
continue
for script in '$PLUGIN_PATH/*/commands'
set +e
/var/lib/dokku/plugins/ps/commands git-receive-pack ''''sample''''
++ dirname /var/lib/dokku/plugins/ps/commands
source /var/lib/dokku/plugins/ps/../common/functions
++ set -eo pipefail
++ [[ -n 1 ]]
++ set -x
++ dirname /var/lib/dokku/plugins/ps/commands
source /var/lib/dokku/plugins/ps/functions
++ set -eo pipefail
++ [[ -n 1 ]]
++ set -x
+++ dirname /var/lib/dokku/plugins/ps/commands
++ source /var/lib/dokku/plugins/ps/../common/functions
+++ set -eo pipefail
+++ [[ -n 1 ]]
+++ set -x
case "$1" in
exit 10
exit_code=10
set -e
[[ 10 -eq 10 ]]
continue
for script in '$PLUGIN_PATH/*/commands'
set +e
/var/lib/dokku/plugins/redirects-plugin/commands git-receive-pack ''''sample''''
[[ git-receive-pack == redirects ]]
[[ git-receive-pack == redirects:* ]]
case "$1" in
exit_code=0
set -e
[[ 0 -eq 10 ]]
implemented=1
[[ 0 -ne 0 ]]
for script in '$PLUGIN_PATH/*/commands'
set +e
/var/lib/dokku/plugins/secure-apps/commands git-receive-pack ''''sample''''
[[ git-receive-pack == secure:* ]]
case "$1" in
exit 10
exit_code=10
set -e
[[ 10 -eq 10 ]]
continue
for script in '$PLUGIN_PATH/*/commands'
set +e
/var/lib/dokku/plugins/shell/commands git-receive-pack ''''sample''''
case "$1" in
exit 10
exit_code=10
set -e
[[ 10 -eq 10 ]]
continue
[[ 1 -eq 0 ]]
exit 0
To dokku@serverha.tk:sample
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'dokku@serverha.tk:sample'

sorry my composer file was wrong!
Thanks


Compiler warnings regarding some CFE_SB API calls

The CFE_SB_GetMsgId(), CFE_SB_GetUserDataLength(), and CFE_SB_GetTotalMsgLength() API calls trigger compiler warnings if they are called with a buffer that is qualified as const.
As these 3 functions are read-only (they do not modify the buffer) the input should be qualified as const, which fixes the warning.

Imported from trac issue 250.  Created by jphickey on 2018-09-20T11:06:49, last modified: 2019-07-03T13:15:28

Trac comment by jphickey on 2018-09-20 11:07:22:
This is a fairly straightforward patch.

Trac comment by jphickey on 2018-09-20 11:27:43:
Commit [changeset:4bd7b9b] is ready for CCB review

Trac comment by jphickey on 2018-10-02 15:11:41:
Reviewed at 2018-10-02 CCB and merged into ic-ccb-20181002

Trac comment by jphickey on 2018-10-02 16:33:45:
Confirmed that 32bit + 64bit builds are successful and all unit tests pass

Trac comment by jphickey on 2018-10-10 09:03:10:
Fix is now included in development branch

Trac comment by jhageman on 2019-07-03 13:15:28:
Moved closed tickets targeting 6.6.1 to 6.7.0 end of summer release.


Hide Microsoft Edge password reveal control

Description
Follow-up to https://github.com/filamentphp/filament/pull/10956. Hides the native Microsoft Edge password reveal control when Filament's password reveal actions are used.

[x] Visual changes (if any) are shown using screenshots/recordings of before and after.

Code style

[x] composer cs command has been run.

Testing

[x] Changes have been tested.

Documentation

[x] Documentation is up-to-date.

Handled this here for you, @andrewdwallo.

@zepfietje Awesome! Glad you found the solution regarding the affix issue. I tried that using CSS but the result wasn't perfect.

Also I didn't know the & in [&::-ms-reveal] is supported in this context.. does that not require postcss nesting plugin?

Also I didn't know the & in [&::-ms-reveal] is supported in this context.. does that not require postcss nesting plugin?

The & here targets the current element. It's a Tailwind CSS feature of arbitrary selectors. I've checked the compiled CSS and it looks ok. Let me know once you've been able to test this in a real Edge browser on Windows though.

Oh okay, sounds good 👌🏻


Update changelog.md

A customer couldn't tell if Postgres deprecation note was because 9.4 goes out of support or because some enhancement for 10 comes in August. Clarified if users should be upgrading now.

@wiersgallak friendly reminder :)


Cleanup File

@sundar-sap: Can you check the file in the root of the repository:
https://github.com/SAP-samples/cloud-alm-api-examples/blob/main/cloud-alm-api.http
I think that was checked in due to an error, could you please check and remove?

Done :-)


Unauthorized response when following quick start guide and don't know how to fix

I'm following the quick start guide to using the Spell Check API with the C# SDK.
The link to Bing Spell Check resource does not resolve presumably because of the warning at the top of the guide that we must use Bing Search Services.
I've provisioned a Bing Search resource and grabbed a key from the "Keys and Endpoints" tab. When I use the exact code from the guide and paste my key in, I get an Unauthorized exception. Was this the correct resource to provision? What key should I be using? How can I diagnose the problem?

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

ID: e6793619-efc3-eb91-793c-b5d38369a5a1
Version Independent ID: 388a2155-2661-bed0-bffc-416eb290ebd8
Content: Quickstart: Check spelling with the Bing Spell Check SDK for C# - Azure Cognitive Services
Content Source: articles/cognitive-services/Bing-Spell-Check/sdk-quickstart-spell-check.md
Service: cognitive-services
Sub-service: bing-spell-check
GitHub Login: @aahill
Microsoft Alias: aahi

@Blackbaud-ChristiSchneider you should be using the Bing Search V7 resource keys and endpoint. Endpoint should be "https://api.bing.microsoft.com/v7.0/SpellCheck/".


Remove truncate instruction - Fix issue #457

As title. Closes #457

From today's meeting, it was decided to leave the code as it is. Numba has the same behavior.


Caddyfile validation

Makes sure that we don't break Caddy! Breaking Caddy is bad

What's wrong (or could go wrong) with formatting the whole thing in contrast to just the change?

Idk if something is messed up in another section it could overwrite it

If there's a syntax error then the validate before the format will catch it, everything should be formatted anyways

Alr


Option to Not Output TOC Heading

This would prevent the program from outputting:
Table of Contents
=================

Fixed by #11


Cocoon Stackdriver logs do not properly handle UTF16 characters

GCP Stackdriver only currently supports UTF8. Devicelab logs lose the fancy formatting from the Flutter logs.
There is currently no timeline for UTF16 support on Stackdriver.

Triage: stackdriver shows logs from other tasks, which is confusing. We might consider removing stackdriver.

@digiter can you close this when devicelab tasks are moved to LUCI?


feat(library): allow setting workflow env values from within workflow builder

Misinterpreted the need to set env on workflow dynamically.
If you think it would still make sense, please reopen.


Rename Create-Next-App. to Create-Next-App.txt

If that file is supposed to be there feel free to delete this pull request, but through my testing on my fork I was only able to clone the repo after removing this file or changing it to a text file.


Add travis CI

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7d272b7). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #12   +/-   ##
=========================================
  Coverage          ?   23.12%
=========================================
  Files             ?        1
  Lines             ?      160
  Branches          ?        0
=========================================
  Hits              ?       37
  Misses            ?      123
  Partials          ?        0

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 7d272b7...b8a89df. Read the comment docs.

@yunhailuo some possible improvements:

We can put all the scripts inside a folder called xena-GDC-ETL, so that it is easier to write tests for them and check coverage. This will also ease the process of releasing to pypi a lot.
So, in my opinion it would be better if the directory structure is something like:

xena-GDC-ETL
|- tests
|- docs
|- xena-GDC-ETL
|- .travis.yml
|- setup.py
|- ...

Overall, suggestions all look good. I would prefer doing this step by step (commit) so it's clear where we should debug if anything goes wrong. I won't do coverage for now since this project is not big for now. A overall structure change and adding tests are must and they are clearly big flaws I made. So as mentioned above, I'd say separate structure change and travis. And since travis may need quite some changes after structure changes, I would do structure change in another PR first. Then come back to fix tests and/or adding more tests in this PR or new PRs.

OK. I create a PR #13 for structural changes. It should work as far as I know for now. But I want to give myself more time for reviewing and testing before merging. Feel free to check it out and play with it though.

Ok, I will separate out the commits.

I have removed codecov and separated out into two commits. Will rebase this PR once #13 is merged.

I have removed codecov and separated out into two commits. Will rebase this PR once #13 is merged.

@yunhailuo , I have added some more tests. Please review. gdc module api is up to date with upstream.

Will squash the commits once this PR is approved.

@ayan-b I just merged #13 Could you please resolve the conflict and make sure Travis test can pass?

PR should be good to go now. :tada:

@yunhailuo, once this PR is merged, I will send PR on code cleanup.

@yunhailuo, please review and let me know if some modifications are required. :smile:


repository using packagr to create a release, rxjs and other improvements

version 3.1.0 using packagr to create a release under dist which you can simple install with npm and release in npm repository. I think this could be a good start point to support 3rd part integrations

Thanks @mburger81 !!


More flexibility for templating output component

I'd love to use this module but would like to do some different things with the output component. I'm not sure what the best way to approach this would be — whether providing a slew of new options, or a templating system that would allow custom, or something else.
Here are things that I would like to do:

Check propTypes to ensure that the user has provided style.width and style.height, which are often necessary for IE.
Add focusable="false" to the every svg element.
Add an aria-labelled attribute to the svg element whose value is a generated id that is used by a <title> element that is the first child of the svg, which receives this.props.title.

Another possibility would be to publish the core of the Babel plugin separately — that is, the code that fixes up SVG attributes so everything works as JSX. Then people who want more flexibility can wrap this with their own code, but we benefit from collaborating on the core problem.

As I think about this more, it seems to me that working with a template (instead of creating the JSX with Babel, then stringifying that) might be a good way to provide lots of flexibility. Are you interested in such a significant change? Or would you rather keep things as they are, and I'll work on making a loader with a different approach?

Hi. Thanks for the great ideas. I've considered moving the babel plugin into a separate package. But haven't got enough time to spend on this loader. I'd keep the loader as it is for version 2 instead of splitting it into packages. But definitely something that I'd do in the next major version.
And regarding the other points -

Check propTypes to ensure that the user has provided style.width and style.height, which are often necessary for IE

Is there a more generic requirement - like adding any prop-types?

Add focusable="false" to the every svg element

This will be too specific for one case. Isn't it?

Add an aria-labelled attribute to the svg element whose value is a generated id that is used by a <title> element that is the first child of the svg, which receives this.props.title

Similar #171. Definitely something we can add for 2.x.
And for these items, PR definitely welcome.

As I think about this more, it seems to me that working with a template (instead of creating the JSX with Babel, then stringifying that) might be a good way to provide lots of flexibility. Are you interested in such a significant change?

I don't want to change the babel generation phase to a template because templates can cause syntax errors if we miss calculate something. On the other hand, working with the AST through babel gives some level of guarantee that the generated code(if it generates without errors) will contain less bugs - at least doesn't throw a syntax error. I consider this shifting of (some possibilities mistakes) errors from runtime to compile time is important.
Thanks again for the great ideas.

It's now split into 3 packages - babel-plugin, loader and cli - https://github.com/boopathi/react-svg-loader/releases/tag/v2.0.0-alpha.4

For anybody who might be looking at this and wonder how to add focusable="false" on every SVG element:
The following is a way to do this in your webpack config, provided you are on<EMAIL_ADDRESS>      {
        test: /\.svg$/,
        use: [
          {
            loader: "babel-loader"
          },
          {
            loader: "react-svg-loader",
            options: {
              svgo: {
                plugins: [
                  { addAttributesToSVGElement: { attributes: [ 'focusable="false"' ] } }
                ]
              }
            }
          }
        ]
      }

You could do this for any attribute. For example, we needed aria-hidden="true" on every SVG element

@sleexyz Thank you for sharing how to add focusable='false' to all SVG elements. Your configuration worked for my webpack setup.


mysql package is old

mysql package version is 0.95 ，but mainline of mysql is  2.1.x.   2.1.x fix more bugs like auto reconnect etc. Do you have plan update mysql package

Ripped out in v2


Vue supporting

Hello. Does this plugin work with vue and with alias paths as '@/сomponents/example'?
Thanks.

I don't think Vue is supported, never tried it. Alias paths doesn't work by default, you can set something up with this https://github.com/kristijanhusak/vim-js-file-import/blob/master/doc/vim-js-file-import.txt#L209

I added support for Vue, but it is not working 100% ok like for regular js.

It doesn't handle alias paths
If there aren't any imports in the file, and when you try to import the first thing, it will import it at 1st line. It is not aware of the <script> tag
Probably more issues, wasn't able to catch it.

So it's more-less working, but nothing fancy.

I added support for Vue, but it is not working 100% ok like for regular js.

It doesn't handle alias paths
If there aren't any imports in the file, and when you try to import the first thing, it will import it at 1st line. It is not aware of the <script> tag
Probably more issues, wasn't able to catch it.

So it's more-less working, but nothing fancy.

Thanks for fast response.
Is it any way to fix this issues?

Yeah, 2. should be fairly easy. For 1, where does configuration for this lives? Is that a webpack thing or?

@timsofteng I added some better support for Vue, but I wasn't able to test it in the real life project, since I don't develop in vue. I used this https://github.com/gothinkster/vue-realworld-example-app for testing.
Check this part of readme https://github.com/kristijanhusak/vim-js-file-import#vue-support , and give it a test to see how it works.

@timsofteng I added some better support for Vue, but I wasn't able to test it in the real life project, since I don't develop in vue. I used this https://github.com/gothinkster/vue-realworld-example-app for testing.
Check this part of readme https://github.com/kristijanhusak/vim-js-file-import#vue-support , and give it a test to see how it works.

Thanks. I'll test it tomorrow.
By the way could I use go to file feature (gf) with this plugin?

You can use jump to definition via <Plug>(JsGotoDefinition), if that's what you are talking about.


question for the posterior

Hi, I read your code and paper carefully. I am a little confused about the posterior calculation, Why do you use gp.F in the  file np_ode_fg.m to calculate the posterior ? It seems that you calculate the posterior with non-whitened vector field, but get the corresponding gradient with whitened vector field. When I prune away the gp.L' in front of dF in function grad_Fw, the result seems wrong. Can you point out my misunderstanding? thank you very much!

That's just a notation issue. We indeed optimize the Fw variable. While computing the integral, you need F, which is defined as F=LFw. You can just replace gp.F with Lgp.Fw, the result would be the same.


Cant run scan on openshift - Job creation fail

What happened:
Scanner job cant be created
What you expected to happen:
Scanner job run sucessfully
How to reproduce it (as minimally and precisely as possible):
Just run a scan on the whole cluster
Are there any error messages in KubeClarity logs?
(e.g. kubectl logs -n kubeclarity --selector=app=kubeclarity)
time="2023-10-05T23:25:43Z" level=error msg="failed to run job: failed to create job: openshift-kube-storage-version-migrator/scanner-okd-content-b4ecf268-0035-4162-9494-71bfcdb1d489. Job.batch "scanner-okd-content-b4ecf268-0035-4162-9494-71bfcdb1d489" is invalid: [spec.template.spec.volumes[1].name: Invalid value: "image-pull-secret-kube-storage-version-migrator-sa-dockercfg-7s9xz": must be no more than 63 characters, spec.template.spec.containers[0].volumeMounts[1].name: Not found: "image-pull-secret-kube-storage-version-migrator-sa-dockercfg-7s9xz"]" func="github.com/openclarity/kubeclarity/runtime_scan/pkg/scanner.(*Scanner).worker" file="/build/runtime_scan/pkg/scanner/job_managment.go:120" scanner id=77a2c019-3665-49f2-a6ff-8f1503b71adb
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version --short):

Kubernetes Version: v1.23.5-rc.0.2071+3afdacbd018325-dirty

Helm version (use helm version):

version.BuildInfo{Version:"v3.10.3", GitCommit:"835b7334cfe2e5e27870ab3ed4135f136eecc704", GitTreeState:"clean", GoVersion:"go1.18.9“
}

KubeClarity version (use kubectl -n kubeclarity exec deploy/kubeclarity -- ./backend version)

Version: v2.21.1
Commit: 5d942857b75fe255056e84a237bb4eb7453cb0e2
Build Time: 2023-09-28T11:43:45Z

KubeClarity Helm Chart version (use helm -n kubeclarity list)

NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
kubeclarity     kubeclarity     1               2023-10-05 18:30:59.893142169 -0400 EDT deployed        kubeclarity-v2.21.1     v2.21.1

Cloud provider or hardware configuration:
Others:

Scan log has a lot of errors like this:
Failed to scan image "velero/velero-plugin-for-aws:v1.5.3". Effected pods: velero-667d7768d8-l9jh7/velero. Reasons: job has timed out. imageID=docker.io/velero/velero-plugin-for-aws@sha256:42e85af860e5250047a8dbeebae03d2363833eb89203759734a19ece9f2b3855.

Jobs cant create pods because of runAsRoot setting:
error:%20container%20has%20runAsNonRoot%20and%20image%20will%20run%20as%20root%20(pod%3A%20%22scanner-okd-content-75475810-1a6a-478e-bf03-ba111b28bacf-qzf5h_openshift-multus(f287d93e-b764-475a-9a7d-2cb7f4406eb5)%22,%20container%3A%20vulnerability-scanner)

Hi @uselessidbr, thanks a l lot for opening the issue.
Looks like there are several problems here.
Regarding:
time="2023-10-05T23:25:43Z" level=error msg="failed to run job: failed to create job: openshift-kube-storage-version-migrator/scanner-okd-content-b4ecf268-0035-4162-9494-71bfcdb1d489. Job.batch "scanner-okd-content-b4ecf268-0035-4162-9494-71bfcdb1d489" is invalid: [spec.template.spec.volumes[1].name: Invalid value: "image-pull-secret-kube-storage-version-migrator-sa-dockercfg-7s9xz": must be no more than 63 characters, spec.template.spec.containers[0].volumeMounts[1].name: Not found: "image-pull-secret-kube-storage-version-migrator-sa-dockercfg-7s9xz"]" func="github.com/openclarity/kubeclarity/runtime_scan/pkg/scanner.(*Scanner).worker" file="/build/runtime_scan/pkg/scanner/job_managment.go:120" scanner id=77a2c019-3665-49f2-a6ff-8f1503b71adb

Looks like we don't validate and trim the length in addJobImagePullSecretVolume(): https://github.com/openclarity/kubeclarity/blob/217c5fc8c9f1f1ad936765b2f2b1fea6575180f9/runtime_scan/pkg/scanner/job_managment.go#L342
Regarding
error: container has runAsNonRoot and image will run as root (pod: “scanner-okd-content-75475810-1a6a-478e-bf03-ba111b28bacf-qzf5h_openshift-multus(f287d93e-b764-475a-9a7d-2cb7f4406eb5),container: vulnerability-scanner)

We set runAsNonRoot: true in the vulnerability-scanner container: https://github.com/openclarity/kubeclarity/blob/217c5fc8c9f1f1ad936765b2f2b1fea6575180f9/charts/kubeclarity/templates/scanner-template-configmap.yaml#L137
Is there something on your side, like a webhook that might change this? Can you please verify that the created Job has runAsNonRoot: true as the value in the job template in the config map?

Hello!
I Will take a look regarding the job template. Thanks!

Hi @uselessidbr, thanks a l lot for opening the issue. Looks like there are several problems here. Regarding:
time="2023-10-05T23:25:43Z" level=error msg="failed to run job: failed to create job: openshift-kube-storage-version-migrator/scanner-okd-content-b4ecf268-0035-4162-9494-71bfcdb1d489. Job.batch "scanner-okd-content-b4ecf268-0035-4162-9494-71bfcdb1d489" is invalid: [spec.template.spec.volumes[1].name: Invalid value: "image-pull-secret-kube-storage-version-migrator-sa-dockercfg-7s9xz": must be no more than 63 characters, spec.template.spec.containers[0].volumeMounts[1].name: Not found: "image-pull-secret-kube-storage-version-migrator-sa-dockercfg-7s9xz"]" func="github.com/openclarity/kubeclarity/runtime_scan/pkg/scanner.(*Scanner).worker" file="/build/runtime_scan/pkg/scanner/job_managment.go:120" scanner id=77a2c019-3665-49f2-a6ff-8f1503b71adb

Looks like we don't validate and trim the length in addJobImagePullSecretVolume():
https://github.com/openclarity/kubeclarity/blob/217c5fc8c9f1f1ad936765b2f2b1fea6575180f9/runtime_scan/pkg/scanner/job_managment.go#L342
Regarding
error: container has runAsNonRoot and image will run as root (pod: “scanner-okd-content-75475810-1a6a-478e-bf03-ba111b28bacf-qzf5h_openshift-multus(f287d93e-b764-475a-9a7d-2cb7f4406eb5),container: vulnerability-scanner)

We set runAsNonRoot: true in the vulnerability-scanner container:
https://github.com/openclarity/kubeclarity/blob/217c5fc8c9f1f1ad936765b2f2b1fea6575180f9/charts/kubeclarity/templates/scanner-template-configmap.yaml#L137
Is there something on your side, like a webhook that might change this? Can you please verify that the created Job has runAsNonRoot: true as the value in the job template in the config map?

Hello!
Well, i‘ve fixed the scanner template and it took some hours to run the scanner. I noticed that the scanners sucessfully started. Unfortunatelly the result is the same, only a few applications scanned.
Same errors with images:
Failed to scan image "quay.io/openshift/okd-content@sha256:32387b4368115abe975671057b1cff23701175771ce899d5b792fd66a0621026". Effected pods: vmware-vsphere-csi-driver-controller-67f7f5d97c-4mg5z/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-controller-67f7f5d97c-8vcgw/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-2dgtq/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-2jft5/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-2ww2n/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-9ptzj/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-dzrr7/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-k9p25/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-l85bf/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-qth45/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-qzslb/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-rzpzq/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-vcl4w/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-whxdp/openshift-cluster-csi-drivers, vmware-vsphere-csi-driver-node-xdz92/openshift-cluster-csi-drivers. Reasons: failed to create job: openshift-cluster-csi-drivers/scanner-okd-content-e7ad44b7-24c8-42d6-a671-1d7bc8399fe9. Job.batch "scanner-okd-content-e7ad44b7-24c8-42d6-a671-1d7bc8399fe9" is invalid: [spec.template.spec.volumes[1].name: Invalid value: "image-pull-secret-vmware-vsphere-csi-driver-controller-sa-dockercfg-r8f98": must be no more than 63 characters, spec.template.spec.containers[0].volumeMounts[1].name: Not found: "image-pull-secret-vmware-vsphere-csi-driver-controller-sa-dockercfg-r8f98"].


Remove postinstall

postinstall should not be needed as no other ng2-module / library whatsoever uses it and it is creating problems where the whole application can not be deployed to Heroku, maybe other PaaS services too...
Also see #10

Hey @vinaygopinath and thanks for merging. Could you also please publish to npm 2.0.3 with that merge? Would be great 👍

Done! Thanks for the postInstall PR (again)


SagePay discounts do not appear in Basket

It appear that if you include discounts in Basket XML , in the SagePay account control panel you are not able to see the discounts in the section Additional information

Some background to this: https://github.com/academe/SagePay/issues/27
Discounts are not supported by omnipay-sagepay at all. I'm not sure if this issue was posted here on purpose or by accident, but it is worth noting as a feature that it would be great to support. More generically, if the basket or cart can be made extendable for OmiPay 3.0, instead of hard-coded into omnipay-common as it is now, making it very difficult to extend, then we may have the possibility that each driver could extend the cart with its own specific features. This would be a great example of how traits could be used, so the application can extend the cart from multiple drivers (but also a great example of how traits can clash if we are not careful).

It was posted by accident, apologies

No problem - keep it here for now as it raises an interesting point. I really want to get a better cart implemented for 3.0, with much more flexibility for extending with new features when needed. I'll close this ticket when I get an issue more generic (for sagepay-common) written up.

If the basket contains negative item values, then it will now be listed in the basket as discount items. This is specific to omnipay-sagepay, and not a general OmniPay feature. Luckily no additional fields were needed to support this. This was implemented under PR #50 & #51. It needs a specific test to show the discounts working, so I'll leave this ticket open until the tests are done, and the XML Basket goes into an official release (2.3.0, I think).

It is a good idea. Thank you a lot.

We need to test multiple discounts. I have a hunch that may be an issue, as it looks like a new <discounts> element will be created for each discount added. I'll raise a new ticket if it fails during investigation.

Hi Jason,
you are right this what is producing with multi discounts
My item110.000.0010.001010</fi
xed>Discount5Discount
$discounts = $xml->addChild('discounts') should be outside the foreach loop.
if there is no negative prices with will not create the discounts Child.
here is the test with $discounts = $xml->addChild('discounts') outside of the loop
10Discount5DiscountMy item110.00</u
nitNetAmount>0.0010.0010
and with no negative value and $discounts = $xml->addChild('discounts') outside of the loop and new loop for discountItems
My item110.000.0010.001010</fi
xed>Discount5Discount
I will make a new pull request at the sagepay omnipay to fix this bug and will add a test for creating the basketXML with discount as well.

Cool, thanks for checking that. I'll help to get it into a release ASAP.
If the tests tested for 0, 1 and 2 discount items, that would make an awsome unit test. When there are no discount items, I suspect the discount XML element should be left out completely, rather than provided as an empty element.
The Sage Pay documentation states that the elements MUST be in the same order as documented, which to me strikes of an XML parser that does things in an odd way, e.g. string matching rather than proper XML parsing, so we need to give it an easy a time as we can ;-)

Since I am already set up for this, I'm happy to make these changes if it's a hassle at your end. Just say.

Thank you so much, but It is a good experience for me and I would love to do it. I am almost ready, I just need to clear a bit the messy code and put some comments.
Thank you once again sincerely.
Cheers,

Hi Jason,
I made a new pull request and added code which allow zero value item to be included in the basket, fixed the discount child creation, add tests for no discounts , one and many discounts, added fix for special characters in item name as addChild() does not escape & and triggers an error when is trying to create xml basket, added test for items with names including special characters. Please review it, and when you are happy with the investigation ad the changes.
Thank you in advance

That's awesome - I'll have a play.

Check out the first answer to this SO question:
http://stackoverflow.com/questions/552957/rationale-behind-simplexmlelements-handling-of-text-values-in-addchild-and-adda
The escaping is done for you if you assign a text value rather than add a child.

True, but the way BasketXML should be build , requires addChild and we gone need escaping function for odd names

We did tested the BasketXML and it generated error when trying to build the basket with nonescaped & that's why we decided that the best is that the driver should handle the escaping and the application just pass the information.

I agree it needs to be escaped, but implemented this way, < and > in the description would be escaped twice.
This example from SO should work and provide full escaping (though not tried it):
$discount->addChild('description')->{0} = $discountItems->getName();

Yes, I just tried it and yes this is the solution. Shall I make the changes?
Thanks a lot again.

Yep - go ahead :-) The PR will automatically update when you push your change. Probably worth putting a test in with < > & and " in the description too.
This is something I've never tested: what character encoding does the XML basket accept? I would assume it is just ISO8859 and not UTF-8. But curious.

I did try description like  this -> Denise's Strange & Wierd Name? and only the & was not accepted.
It says pm the documentation that description accepts ;  Aa 0-9 \ / & {}
but it is not quite correct as it errors when & is present
And one strange situation with travic my phpunit test passes and travic has a failure on testBasket and testBasketWithTwoDiscount. it is adding and extra <0></0> tag around description. Can you suggest solution, I am a bit confused?
Thank you

Hi Jason,
I found another solution. I am just waiting for travic to finish
$item->description = $basketItem->getName()
Thank you so much.

Hi Jason,
It passed travis and it escapes very nicely the name of the item. I hope you will accept it and merged it.
Thank you so much.
Cheers.

Just for reference, this is all in PR #53

Can we close this because the PR is now merged?

Here is a discount showing up in a Sage Pay test account:

So yes, it is now working to this point at least. Whether Sage Pay take that value further into the back-end control panel, or not, is another thing altogether and out of scope here.

However, noticing just now that discounts don't have a quantity, and from memory that is something this driver handles for discounts, I thing we possibly need some more checks in place.

Well, this driver does multiply the discount by the quantiry of that discount.  The quantity is not sent to Sage Pay, so it's an internal thing. I don't think it is going to cause any harm, but I also don't think this is the place to do that calculation. I think we can leave it for now, but recommend that a discount always has a quantity of one.

Hi @judgej,
I've been trying to use the discount functionality and been getting the (ever so helpful) 3021 : INVALID : The Basket format is invalid. error code.
I can't see any actual issues with the transaction or the Basket XML. If I remove the discounts from the basket, the transaction can proceed as normal... This is all in the testing environments of course.
For an example, I have a cart with the Amount being 17.99 and I want the final Amount to be 11.99. The following basket XML is generated to achieve this:
 <basket>
	 <item>
	 	<description>Item 1</description>
	 	<quantity>1</quantity>
	 	<unitNetAmount>11.99</unitNetAmount>
	 	<unitTaxAmount>0.00</unitTaxAmount>
	 	<unitGrossAmount>11.99</unitGrossAmount>
	 	<totalGrossAmount>11.99</totalGrossAmount>
	 </item>
	 <discounts>
		 <discount>
		 <fixed>6.00</fixed>
		 <description>Voucher code (FREEDEL)</description>
		 </discount>
	 </discounts>
 </basket>

I'm wondering if you/anyone has seen similar problems? Or is there something i'm really missing here?

I haven't checked the docs to confirm this yet, but my first thought is that the amount is not correct. The discounts are subtracted just like any other line is added to get the final amount, so your basket contains 11.99 minus 6.00 or 5.99, and that will not match your total amount.
Try it with the net unit cost (17.99) before any basket discounts are applied.
Unlike some gateways, the basket is not just information for logging. All items in it must correctly add up to the order total.

I'll give it a go and get back to you on that.
Also, it's funny that you mention adding up items. In my experience so far with SagePay, it has never once complained about Basket items not matching the transaction Amount. In our use case, we don't actually include the shipping as an item, so these two values are always mismatching :smile:
I don't think there is currently support in this package for shipping parameters either. The SagePay integrations docs do say it is possible via a Basket deliveryNetAmount node though.

It may have been the old style basket that did this, rather than the XML basket, so I may be wrong. It was just something to try anyway. I'll have a look at the XML when I get ten minutes and see if there is anything in there that looks wrong to me.

Given it another go. Tried using:

Amount = 11.99, basket.item.unitNetAmount = 17.99 with basket.discounts.discount.fixed = 6.00
Amount = 11.99, basket.item.unitNetAmount = 9.99 with basket.discounts.discount.fixed = 6.00
Amount =17.99, basket.item.unitNetAmount = 17.99 with basket.discounts.discount.fixed = 6.00

Note I originally got the basket.item.unitNetAmount wrong as this is supposed to be 9.99 (SagePay automatically adds on the actual tax amount if you check the completed transaction).
I am tempted to think this is a problem on their side really, as it's not clear to me why it shouldn't work.

The XML looks good to me (correct names and order, and all the mandatory fields). The spec lists TotalGrossAmount with a capital T though, but I suspect that is a documentation error. Edit: a later spec has this corrected, so the lower-case t is correct.
There is a changelog in the spec:

27/08/2015 Remove totals validation from BasketXML

So I wasn't going mad thinking the totals had to add up correctly.

Just to check, is this basketXML sample you have supplied here generated by this OmniPay driver? The formatting is something you have done for readability?

That just makes it even more baffling that it's complaining about the Basket format being invalid then, no?
And yes, this was XML generated by the Omnipay driver and I adjusted the formatting just for readability purposes.

Unlike some gateways, the basket is not just information for logging. All items in it must correctly add up to the order total.

PayPal and PaymentWall also require that the items correctly add up to the order total.


Need to update docs to include AzDO pipeline permissions for repositories

AzDO Build pipeline agents don't have permission by default to contribute to a repo, create a branch or update a pr.
You need to grant that permission, This might be something good to add to docs.

I think this also applies to the github implementation. I had to set the security settings to allow Workflows to have write permissions.

Done! Please check the updated site


Replace rm alias in source code and added -force to removing aliases

Replaced rm with Remove-Item to allow assigning another command to rm
Add -force option to removing aliases (Remove-Item "alias:\$_" -force) to allow assigning custom aliases to default global/constant ones (e.g. to gl)

Cool, sounds good. Thanks.


debug cluster - unusable state

Hi,
I´m trying to debug my cluster with command :  aztk spark cluster debug --id sparkcluster --output logsAztk/
It creates the file in the specific folder but it´s not able to write anything in the "debug-output.txt" file. ( i already tried with sudo command)
I´m using 0.8.1 Aztk version.
This is the error:

Thanks.

Just to be clear -- every node in the cluster is in an unusable state when this error occurs?

Yes, all the nodes are unusable.
Thank you.


Liascript Basec Editable Container

Hello, working with Lia has so far been a challenging experience.
While the availability and usability which are present are great, I am personally lacking a... let's call it... "div" that I can throw script-based elements/interactions/ ... in and have them been cleaned up on the leaving / return of the page.
I am currently toying around with a project, in which I am attempting to dynamically generate a task for a user. Said task I am currently having, along with an input field and an image in a div, that I have placed onto the page as a placeholder.
Upon reaching the part where the script gets activated, it fills the div with the necessary layout of button, text, and image to have a user work on...
So far so good... in theory... at least for me... a good idea...
Though when I switch to a page where I no longer employ my... "div" or... "place holder"... I suddenly find it displayed on the page...
After some... problem analysis... it was suspected, that this might be the case as the background process might not "clean up" a seemingly empty div... as... well... it's empty and therefore doesn't bother anyone... and nobody realizes that it's no longer empty.
Maybe I am using everything wrong... but... the idea of having an empty placeholder to be replaced dynamically with a script... sounds like an idea worth considering.
So... maybe just have an lia HTML-based element which is an empty div, and gets handled like any other object on the page (therefore removed upon switching to the next page) would be a great addition for this project.

I thought about it ... At the moment it might be necessary to clean-up custom dom-insertions manually. One method might be to add a certain class and probably a data-field with a certain section number, this way it should be possible to search for all elements with  your class and to delete them, if they do not have the same section number as defined by the current "slide".
By the way, maybe this is also not required and you can stay within the LiaScript-world. I created an example/stub, which creates dynamical content and also makes use of the text-analysis template for user inputs. It does not allow to inject certain slides, but maybe this is also not required. The macros allow to use your functions multiple times in different places within a course.
https://github.com/LiaPlayground/ImageDescriber
Storing user-inputs permanently within the browser is only possible if the "code-block" is not generated dynamically and the course version is larger than equal to "1.0.0" otherwise you will have to define your own functionality to store the inputs in localStorage or indexeddb ...


HTML5 Canvas Animation added

Description 📜
HTML5 Canvas Animation added using HTML5 Canvas API
Fixes #621

Type of change 📝
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] Add a new project
[ ] Modified or enhanced the existing projects
[ ] Improve the readme of any project

Domain of Contribution 📊
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Optional) 📸
Add the screenshot of the changes you have made

@khushi-purwar Kindly explain why you have removed level3 and given level2


link_attributes for autolink

It seems the :link_attributes option is not working for autolinks. It would be very useful to add a "nofollow" tag to those links to prevent link building.
i use :link_attributes=> {:rel=>"nofollow"} and :autolink => true with no luck :(

Is it possible to make it optional, like the following?
def markdown_format(text, nofollow = false)
    renderer = Redcarpet::Render::HTML.new(
      filter_html: true,
      no_links: false
    )
    renderer[:link_attributes] = { rel: 'nofollow' } if nofollow


--insecure vs --skip-verify and options inside gNMIclient

greetings! I am trying to use pygnmi for connecting to a cisco Nexus 9000 series switch. and with the gnmic tool for command line i can get my commands to work as long as i use "--skip-verify" in my command string. I am trying to accomplish the same thing in a python script and am running into errors. In the client in the library, there doesn't appear to be an equivalent to "--skip-verify" as an arg in the client function.
and that brings me to my question. in the case of this. Does "insecure=True" act the same as "--skip-verify" in the gnmic tool?
i guess what i am really looking for is how, in the python client, do i also do untrusted TLS command as an arg?
i.e. working command for cisco 9k switch:
gnmic -a <IP_ADDRESS>:6030 -u admin -p admin --skip-verify get --path /lldp/state/enabled
i.e. NOT working command for cisco 9k switch:
gnmic -a <IP_ADDRESS>:6030 -u admin -p admin --insecure get --path /lldp/state/enabled
and here is my python snippet:
with gNMIclient(target=host, username='admin', password='admin',insecure=True, gnmi_timeout=2) as gc:
also this library is truly amazing, it was a no brainer to start using this as my automation go to for my growing presence of grpc stuff
keep up the great work!!!

this helped a lot
https://karneliuk.com/2021/03/pygnmi-8-securing-the-gnmi-connectivity-with-self-signed-certificates/

Hello @soap1337 ,
thanks for a kind feedback. Has the blogpost answered your question? Is there anything else needed?
Best,
Anton

Yep, basically I need to test cert based auth. I'll post here with some examples when I get it done. My environment has totally different vendors+hardware than you test this library on in the video examples. Thanks for responding!

just figured i would update this for anyone who might come across this. I ran this tooling against cisco and arista.
for the cisco 9k appliances, each device needs a specific cert with the whole chain the the CA.
took me a few days to really get this detail worked out.
also @akarneliuk if you ever circle to OpenConfig+pygnmi on the Cisco nexus 9k platform. i can post the information i have gathered on it. CIsco documentation is not easily searchable or deciphered.


issue resolved(#237)

Description
issue resolved by adding anchor tag to link the microsoft learn student ambassador website.
Fixes #237
link added
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
tested using live server.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My changes generate no new warnings

From next time, we will not entertain any PRs made to master branch
It is clearly mentioned @Kp779 that to send PR to development branch.
Your PR is disqualified due to not reading the project readme properly and making code-based PRs on master branch.


Add Football as Item for Ducks

Hi, I would like to work on this request.

hey @github4maninder, I'm moving all of the duck stuff into a repository here. If you could add your pull request there, it would be great!

The issue is here.


"docker volume create" accepts no argument(s)"

Problem description
When following https://docs.docker.com/engine/tutorials/dockervolumes/, section Mount a shared-storage volume as a data volume, specifically issuing this command there:
$ docker volume create -d flocker -o size=20GB my-named-volume

After issuing the command, this was the docker's full output:
"docker volume create" accepts no argument(s).
See 'docker volume create --help'.

Usage:  docker volume create [OPTIONS]

Create a volume

Problem location

I saw a problem on the following URL: https://docs.docker.com/engine/tutorials/dockervolumes/

Project version(s) affected
Running on macOS with:
$ docker --version
Docker version 1.12.2, build bb80604, experimental

Hi!
I also following this guide. This is error in guide, see right syntax here https://docs.docker.com/engine/reference/commandline/volume_create/
$ docker volume create --name=my-named-volume1 --opt o=size=100m

But i don't use flocker.

Why is this closed if the tutorial is still broke?

@mstanleyjones looks like these changes were cherry-picked into the 1.12.x branch, but were supposed to be for 1.13.x (where name could also be passed as a positional argument); https://github.com/docker/docker/pull/26343 https://github.com/docker/docker/commit/5e4e13e31c71f27e62825b55beedc096c27e3554


What is prev_output_tokens in TransformerModelBase?

❓ Questions and Help
I have searched the issues and have searched the docs.
What is your question?
I'm training a custom model which inherits from fairseq.models.transformer.TransformerModel. I have replaced the encoder and decoder with my own custom encoders/decoders, and now am training the new obtained model with pytorch lightning. It seems I have to provide three arguments to the forward method: src_tokens, src_lengths, prev_output_tokens. Can you please clarify what the third argument is?
It seems to me that we've to train this like an RNN (word by word). But that cannot be the case because the whole premise of transformers was to remove the recurrence equation from RNNs that had made optimizations basically impossible.
So please clarify what that argument means. Link to the specific line number in the specific file (TransformerModelBase) that I am concerned with.
Code
    # TorchScript doesn't support optional arguments with variable length (**kwargs).
    # Current workaround is to add union of all arguments in child classes.
    def forward(
        self,
        src_tokens,
        src_lengths,
        prev_output_tokens,
        return_all_hiddens: bool = True,
        features_only: bool = False,
        alignment_layer: Optional[int] = None,
        alignment_heads: Optional[int] = None,
    ):
        """
        Run the forward pass for an encoder-decoder model.
        Copied from the base class, but without ``**kwargs``,
        which are not supported by TorchScript.
        """
        ...

What have you tried?
Ctrl-F on several places but couldn't find anything.

The prev_output_tokens function functions as the target sequence. The naming conventions of prev_output_tokens is only used to match auto-regressive models that also exist in fairseq (RNN/LSTM as you mentioned). This also makes more sense during iterative decoding (at inference time).


Update package.json to make prettier formatting of HTML as LWC

Critical Changes
Changes
Issues Closed

Prettier changes were incorporated into .prettierrc (instead of package.json) in Pull Request #23.


fix issue where game could be paused when the game ended

also i changed the pausedelay because i realized that with the previous code, the pause screen message would be drawn twice. idek why there is a pause delay but if its important then change it back
btw i didnt test my code but it should work... probably

Made changes to the main branch, thanks for finding this xD.
Closing!


GITHUB-5 [driver][windows] new driver (untested)

sounds cool! could you put everything in example/windows/driver please?

can you make a build script please?

great progress!!!!! could you continue so that I could implement the connector please?


Supports for cocoapods 1.0.0.beta

Since cocoapods 1.0.0.beta1 has been released on Dec 31, 2015, motion-cocoapods should also follow up. Any progress?

Uploaded motion-cocoapods v1.8.0.beta.1.
You can install it with gem i motion-cocoapods --pre.
Thanks.


Outdated Instructions?

I have two tenants, both using the updated PIM experience.  I have not enabled or consented to PIM in the past.  When I try to follow the direction for Start Using PIM, there is no Consent to PIM option.  It looks like consent was given, but no users assigned to the Privileged Role Administrator role.  This is the same for both tenants.
When I go to Azure AD Roles, there is no sign-up option under quick start and some of the menu options seem different.  Is this listing the instructions for the previous user experienced?  If so, where are the instruction for the updated experience?  Otherwise, what is the proper way to start using this without the consent and sign up wizard?

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

ID: f720f767-871a-b92b-0efa-e0e35d3ccca8
Version Independent ID: ee84f58e-7791-40cf-9b38-1d5b416303af
Content: Start using PIM - Azure Active Directory
Content Source: articles/active-directory/privileged-identity-management/pim-getting-started.md
Service: active-directory
Sub-service: pim
GitHub Login: @curtand
Microsoft Alias: curtand

Having the same issue as tsrob50 (#50216 ). I see that there is single account assigned to the PIM role but cannot find out which account is holding the right.

I was able to get it working by manually adding the user following the instructions  to grant access to others to manage PIM located here https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pim-how-to-give-access-to-pim

+1 for outdated documentation.  In a tenant set up recently via CDX, there is no facility to "sign up", however the Privileged Role Administrator has no assignments.

I encountered with the same issue. The initial account used to manage PIM for others does not automatically gets assigned Privilege Role Administrator or Security Administrator roles. And when eligible Global Administrator activates his account he can change everything in PIM; assign more roles to self, change settings and even remove other accounts from PIM. That is absurd. Previously it worked well. Please look into this asap.

Hi @tsrob50
The PIM UI and documentation for Azure AD roles has been updated on 4/23. I hope this helps your experience.
#please-close