Adding settlement APIs and balances API

The sample app doesn't have the APIs for fetching the settlements list and settlement detail. Also the payments API list doesn't have the fetch Balance endpoint.
Adding the above mentioned API to the sample application
Do Not Merge until the API has been added.

Makes sense, but settlements can be queried by both merchants and marketplaces. Depending on the case, the user needs to specify different parameters. See: https://github.com/circlefin/payment-processor/blob/89fb1ca3a8f000e094af431ad8945aff210e25d8/payment-processor/src/main/java/com/circle/paymentprocessor/resources/v1/SettlementsResource.java#L73-L78

Can you please also update: http://localhost:3011/debug/


DateTime.Date() returns different results if only the seconds field differs in UTC times

DateTime.Date() returns different results if the seconds field differs
Steps To Reproduce
https://deck.net/93a9d3ed52d8a5949d7216fc697f7c8c
Source of the error is here:
https://github.com/bridgedotnet/Bridge/blob/master/Bridge/Resources/Date.js#L1148-L1164
$clearTime: function (d, isUTC) {
    var dt = new Date(d.getTime());

    if (isUTC === true) {
        dt.setUTCHours(0);
        dt.setUTCMinutes(0);
        dt.setUTCMinutes(0);
        dt.setUTCMilliseconds(0);
    } else {
        dt.setHours(0);
        dt.setMinutes(0);
        dt.setSeconds(0);
        dt.setMilliseconds(0);
    }

    return dt;
},

Thanks for pointing out this defect. Looks like the first dt.setUTCMinutes(0); should have been dt.setUTCSeconds(0);.

Fixed! The issue's fix has just been merged upstream and will make it next Bridge release! See issue's milestone for the version it will be in; at the time of the writing of this response, 17.2.0.


Camera Integration with Azure IoT

Hi,I have done camera integration with Azure IoT using raspberry pi. While receiving message from azure IoT, motion service which is setup in the raspberry pi is connected.The changes made by me in the code are command to start and stop the motion service.Please have a look at the below code:
`if message_buffer =="on":
os.system('sudo /etc/init.d/motion start 2>&1')
command to turn on camera
print("camera on")
else:
os.system('sudo /etc/init.d/motion stop 2>&1')
command to turn off camera
print("camera off")
But, I got some errors as:
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_amqp_common.c Func:on_amqp_connection_state_changed Line:759 Transport received an ERROR from the amqp_connection (state changed AMQP_CONNECTION_STATE_OPENED -> AMQP_CONNECTION_STATE_ERROR); it will be flagged for connection retry.
Info: Preparing transport for re-connection
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransportamqp_methods.c Func:iothubtransportamqp_methods_unsubscribe Line:892 unsubscribe called while not subscribed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/message_sender.c Func:messagesender_close Line:814 Detaching link failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/message_receiver.c Func:messagereceiver_close Line:401 link detach failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_amqp_telemetry_messenger.c Func:destroy_message_receiver Line:515 Failed closing the AMQP message receiver (this failure will be ignored).
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/message_sender.c Func:messagesender_close Line:814 Detaching link failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/message_receiver.c Func:messagereceiver_close Line:401 link detach failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_amqp_messenger.c Func:destroy_message_receiver Line:701 Failed closing the AMQP message receiver (this failure will be ignored).
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/message_sender.c Func:messagesender_close Line:814 Detaching link failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_amqp_connection.c Func:on_cbs_error Line:160 CBS Error occured
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/amqp_management.c Func:amqp_management_close Line:1041 messagesender_close failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/message_receiver.c Func:messagereceiver_close Line:401 link detach failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/amqp_management.c Func:amqp_management_close Line:1048 messagereceiver_close failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:send_detach Line:235 Sending detach frame failed in session send
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/link.c Func:link_detach Line:1256 Sending detach frame failed
Error: Time:Tue Nov 27 12:36:29 2018 File:/usr/sdk/src/c/uamqp/src/connection.c Func:connection_encode_frame Line:2048 Connection not open

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

ID: 617cf9c4-6f85-d240-d8e5-6010cd0b7839
Version Independent ID: a3c4e9da-c539-2f51-c245-57b5e43eca42
Content: Cloud-to-device messages with Azure IoT Hub (Python)
Content Source: articles/iot-hub/iot-hub-python-python-c2d.md
Service: iot-hub
GitHub Login: @kgremban
Microsoft Alias: kgremban

@naznaaa Please help with the document on which this feedback is related. Thanks.

Hello @naznaaa . Because you developed custom code this is not supported on the documentation issues. Please can you ask this question on the Azure IoT Python SDK repo ?
Let us know the link so others can follow-up there as well :).
Thank you so much!

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Did something change with default arguments?

TypeScript Version:  2.0.3 / nightly (2.1.0-dev.201xxxxx)
I work on the Node version of the popular BotBuilder library and I have numerous people complaining that my latest release has broken them. I've isolated the issue down to a default argument not being filled in but I can't figure out if it's because of a change to the TS compiler or just a misunderstanding on my part around how default arguments work.  My issue is that this code:
    constructor(root: lib.Library, defaultLocale = 'en') {
        this.defaultLocale(defaultLocale);

Is generating this code:
    function DefaultLocalizer(root, defaultLocale) {
        if (defaultLocale === void 0) { defaultLocale = 'en'; }
        this.localePaths = [];
        this.locales = {};
        this.defaultLocale(defaultLocale);

That means that defaultLocale will ONLY ever be assigned a value when the argument literally isn't passed.  In my situation null is being passed and isn't being converted to 'es'. I can understand why that might be the case but that's not how I thought default arguments worked and now I need to go through and re-evaluate all of my code because default arguments aren't really ensure that I always have a value.
IMHO Default arguments are pretty much worthless without the added protection against null. You want to be able to reliable assume that you're going to have a value. If I'm going to have to add a second check in my code to protect against someone passing in null then what's the point?

This is the same as always and the same as the ES spec. You need to pass undefined for default parameters.

Ok... Like I said. I wasn't sure if it just wasn't a misunderstanding on my part. My statement about them being of limited use without the added null protection still stands. The problem is code wise it makes you think that you can just assume that a value will always be provided for an argument and that really isn't the case. But I guess you can make that statement about all parameters.


Connection Lines are not using the starting position of their Handles

Describe the Bug
Hello,
i'm trying to create multiple handles on one node.
It looks like expected, but if i try to drag one of the handles, the line always begins at the first handle.
I think it has something to do with the handle-id.. so i tried to generate an id for every handle.
I tried to use "useUpdateNodeInternals" but i'm not really sure where i should put it and if it solves my problem.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
This component renders the dynamic amount of handles
export default function CustomHandles({ data }) {
    const handles = data;
    const handleArray = [];
    const handleAmount = Object.keys(handles).length;

    Object.entries(handles).forEach(handle => {
        handleArray.push(handle);
    });

    const handleList = handleArray.map((handle, index) =>
        <CustomHandle data={handle} amount={handleAmount} positionId={index + 1} />
    );

    return (
        <>
            {handleList}
        </>

    );
}

This is my CustomHandle Component which sets the position and color for now..
export default function CustomHandle({ data, amount, positionId }) {
    const handleData = data[1];
    let handleType = '';
    let handlePosition = '';

    // Calculates the top position depending on the amount of handles
    const handleGap = 100 / (amount + 1);
    const handleStyles = {
        backgroundColor: '',
        top: (handleGap * positionId) + '%',
    }

    // Set Handle Color
    switch (handleData.media) {
        case 'audio':
            handleStyles.backgroundColor = 'yellow'
            break;
        case 'video':
            handleStyles.backgroundColor = 'red'
            break;
        case 'control':
            handleStyles.backgroundColor = 'blue'
            break;
        default:
            break;
    }

    // Set Input or Source Handle
    if (handleData.type == 'input') {
        handleType = 'target';
        handlePosition = Position.Left;

    } else if (handleData.type == 'output') {
        handleType = 'source';
        handlePosition = Position.Right;
    }

    return (
        <Handle id={nanoid} style={handleStyles} type={handleType} position={handlePosition} />
    );
}

Expected behavior
Thank you very much for any help!
Screenshots or Videos

Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

I gave every handle a string as ID. Like 'audio', 'video', 'control'.
Now its working!


[fix]: file extension "tanis" to "tanis.md"

The file extension of the tanis (frames/find-starknet-frens/tanis) was not specified. Therefore, I changed it from tanis to tanis.md. However, I suggest changing it to README.md because it will not be readable when people want to check the project.
Also, I have added my Farcaster account to the builder_follow_builder.md file.

are there any active contributors here?


Check number wrong

Check 7.87 does not match with the check id (extra792):
prowler -l
[...]
7.87 [extra792] Check if Elastic Load Balancers have insecure SSL ciphers (Not Scored) (Not part of CIS benchmark)
[...]

Thanks for the heads up @mfuellbieaws


spec: bump version to 0.10.0

Ready for review.
Bumps iOS deployment target to 9.0, since some changes were made for iOS 9.0 in #14 (now merged).
Don't forget to tag the merge commit on master with 0.10.0 after merging.

You should be able to test this commit works by installing this Pod in a Bean SDK project.
Try using the following line in your Podfile:
pod 'Bean-iOS-OSX-SDK', :git => 'https://github.com/PunchThrough/Bean-iOS-OSX-SDK/pull/18', :commit => '600ce84354ebef65ae7c3a86a9c7189dbca998c4', :branch => 'ios-9-release', :submodules => true

Verified by @zeeeke. Thanks!


Feature Request: ospf over nebula

What version of nebula are you using?
1.6.1
What operating system are you using?
Linux
Describe the Bug
Hello, first I would like to congratulate everyone for the excellent work on nebula. You guys are defining the future of mesh network.
My question is: is it possible to use routing protocols like ospf over nebula?
I came across a scenario where in some clients I have 2 internet links configured in failover and i add in firewall rules to forward each instance of a node to a link and I would like the nodes to switch in case of a link failure. I tried ospf on top of nebula1 and nebula2 interfaces in both sites, but no success.
Any tips? Or am I really trying something not yet supported? If so, is there any possibility that nebula will support this scenario in some future?
To better understand my need, I made a small diagram:
                    node_A                                                                  node_B
                |interface_nebula1|----|wan1    |                       |wan1    |----|interface_nebula1|
 |network A|----|      ospf       |    |firewall|---internet_multiwan---|firewall|    |      ospf       |----|network B|
                |interface_nebula2|----|wan2    |                       |wan2    |----|interface_nebula2|
Logs from affected hosts
No response
Config files from affected hosts
No response

After making some tests, I discovered that it is not possible to change the routes manually or by some dynamic routing system in the nebula interface. So I think the solution for this case would be to have an option in the configuration file to allow changing the routes externally. Perhaps also make this statement explicit in the node's certificate.

I would wonder if something like wireguard would be a better transport layer for something like OSPF - far less complexity, and a tool better suited for the job.

I know I am late to the game but this might work in ptp or point to point mode in bird. I am going to try it when I have a chance.

Yes, it works in ptmp mode (or ptp). But it would be nice if nebula would work in simple ospf broadcast mode where one does not need to specify neighbors manually...

I don't believe that's really possible, broadcasting to an entire nebula network seems inadvisable, given it's designed to be very scalable.

@benyanke Well, maybe it's possible to create an opt-in flag for that for people with smaller networks like me. I am using Wireguard now too, but it's more hassle to set up a bit and it's currently being blocked in Russia by govt (i'm having a VPN for my parents there).


Create a simple way for Front End devs to work on the codebase.

There are quite a few hoops to jump through to for a front end dev to contribute to the project. We need to reduce the friction.
1- Create better documentation
2- Spin up a dev buttress instance

Whether it's easy is up for grabs, but the Buttress Dev instance lives and the Getting Started document is up on the Wiki,


"SIGILL: illegal instruction" causing "error reading from server: EOF"

My CPU only supports AVX,but not AVX2 or AVX512.  This is causing issues I can't seem to workaround even when rebuidling with proper CPU Flags.  See my .env
## Set number of threads.
## Note: prefer the number of physical cores. Overbooking the CPU degrades performance notably.
THREADS=2

## Specify a different bind address (defaults to ":8080")
# ADDRESS=<IP_ADDRESS>:8080

## Define galleries.
## models will to install will be visible in `/models/available`
GALLERIES=[{"name":"model-gallery", "url":"github:go-skynet/model-gallery/index.yaml"}, {"url": "github:go-skynet/model-gallery/huggingface.yaml","name":"huggingface"}]

## Default path for models
MODELS_PATH=/models

## Enable debug mode
DEBUG=true

## Disables COMPEL (Lets Stable Diffuser work, uncomment if you plan on using it)
# COMPEL=0

## Enable/Disable single backend (useful if only one GPU is available)
# SINGLE_ACTIVE_BACKEND=true

## Specify a build type. Available: cublas, openblas, clblas.
BUILD_TYPE=openblas

## Uncomment and set to true to enable rebuilding from source
REBUILD=true

## Removing CPU FLAGS
CMAKE_ARGS="-DLLAMA_F16C=OFF -DLLAMA_AVX512=OFF -DLLAMA_AVX2=OFF -DLLAMA_AVX=OFF -DLLAMA_FMA=OFF -DLLAMA_F16C=OFF"

## Enable go tags, available: stablediffusion, tts
## stablediffusion: image generation with stablediffusion
## tts: enables text-to-speech with go-piper
## (requires REBUILD=true)
#
#GO_TAGS=tts

## Path where to store generated images
# IMAGE_PATH=/tmp

## Specify a default upload limit in MB (whisper)
# UPLOAD_LIMIT

# HUGGINGFACEHUB_API_TOKEN=Token here

LocalAI version:
Latest
Environment, CPU architecture, OS, and Version:

Supermicro 2U X9DRI-LN4F Board
2x Intel Xeon E5-2670 2.6ghz 16-Cores
64gb mem
Latest Unraid OS 6.12.6
Using Docker Compose

Describe the bug
To Reproduce
Issue HTTP Request:
curl http://localhost:9000/v1/chat/completions -H "Content-Type: application/json" -d '{
     "model": "lunademo",
     "messages": [{"role": "user", "content": "How are you?"}],
     "temperature": 0.9
   }'

Receive HTTP 500 Error Response:
{"error":{"code":500,"message":"could not load model: rpc error: code = Unavailable desc = error reading from server: EOF","type":""}}

Expected behavior
HTTP 200 response
Logs
See Attached File
[Boot & Error Logs.txt](https://github.com/mudler/LocalAI/files/13695032/Boot.Error.Logs.txt)

Additional context
Using following model and configs:

Lunademo.yaml:
backend: llama
context_size: 4096
name: lunademo
parameters:
  model: luna-ai-llama2-uncensored.Q4_K_M.gguf
  temperature: 0.2
template:
  chat: luna-chat-message
threads: 10

Same here... Compiling from source with latest commit seeing if it is fixed...

Glad to hear I'm not alone.  Let me know if you have a breakthrough. :)

Great News! Got it working! Building from source with this modified Dockerfile worked! Here are the steps I used:

Clone the Repo

git clone https://github.com/mudler/LocalAI.git
cd LocalAI

Download the attached Dockerfile

wget https://github.com/mudler/LocalAI/files/13705244/Dockerfile.txt -O Dockerfile

Build

docker build -t localai .

Dockerfile

@justaCasualCoder thanks for digging in and sharing your findings!  When I manually ran a diff between the Dockerfile you found and the one in the main repo I noticed all your Dockerfile was doing was adding the same CPU flags.
Ultimately, I just pulled down the new 2.0.1 Dockerfile and everything worked.   I guess I was just experience an edge case scenario related to 2.0.0.


Update Package Name

This PR updates the cli to be registered for the codacy-reporter command name, and also updates the package to be published on npm with the name codacy-reporter instead of codacy. Accompanying this are also updates to the README for the new name and updates to the package.json to point to the new home of the repository.

@DavidTPate
The current status is:

renamed the package to codacy-coverage
deprecated codacy (at least I think I did)
updated your pull request
released initial version of codacy-coverage

The status of your PR is ready to release new version 1.0.2-1 with some link fixes
Can you take a look and see if I messed up something?

Looks good! The old package is properly deprecated and the updates look good. The only thing I changed is the version number. NPM uses semver and based on that metadata in the version number such as -2 is considered to be a pre-release. So instead we would just update the revision number in this case.


Generating slabs for mp-14928 takes too long

Generating slabs for MnSc2Se4 (mp-14928) is very slow.  The HTTP request times out on the demo, and takes 1min 27s ± 523 ms when done manually using ocdata:
from ocdata.core import Bulk, Slab

bulk = Bulk(bulk_src_id_from_db="mp-14928")
slabs = Slab.from_bulk_get_all_slabs(bulk)

Is there anything we can do to speed this up?

Looks like majority of time is spent in this get_primitive_structure call:

Not much we can do on our end. One solution is to precompute these so we dont have to create them from scratch all the time. Closing for now.


Unreal 2 !

Man, the wrapper IS WORKING! It's awesome!
Unreal 2 can use EAX only through OpenAL "native" interface and NOT DirectSound like UT 2004, so you've solved a 18 years old problem :D (DSOAL has no use here!)
Still there are some little issues! Can you test personally Unreal 2 and hear them by yourself (->footsteps and water sounds in the Severnaya level when you load a savegame on the dam)? The Unreal Anthology package release is already patched (and Steam release too, maybe) to the lastest version!
No issue with an old and glorious Audigy 2 ZS!
But man, you did finally free us from Creative! (X-Fi cards, Titanium apart, do not work correctly with old OpenAL games and the Audigy 2 can't be installed on modern systems).

Here's a video of the (sound) problem: https://www.mediafire.com/file/ar7wg2n6ff9ofdh/Unreal2+2021+04+19+02+36+55+821-1.mkv/file


Fixed various issues found in development

Fixed performance issues close to image boundaries.
Fixed undefined behaviour when processing an image where cols == 35.
Fixed correctness issues where rogue keypoints can be found by reading out of bounds.

Owens-MBP:KFAST owen$ ./KFAST

------------- KFAST ------------
Warming up...
Testing...
------------ OpenCV ------------
Warming up...
Testing...
---------- Dr. Rosten ----------
Warming up...
Testing...
--------------------------------

Verifying results...

All keypoints agree! Test valid.

KFAST      took 717.865 us to find 8361 keypoints.
OpenCV     took 2918.54 us to find 8361 keypoints (4.066x slower than KFAST).
Dr. Rosten took 13099.9 us to find 8361 keypoints (18.25x slower than KFAST).


SAK-28184 new account tool should email users a link to activate their accounts

https://jira.sakaiproject.org/browse/SAK-28184
To ensure that users are creating accounts using their real email addresses, the New Account tool should be configurable to send an email with a link to activate their account.
Also, when we add unofficial participants through Site Info, the user eids match their email addresses. For consistency, the New Account tool should have configuration to similarly force the eid to match the user's email address.
Finally, it would be handy to display instructions in the tool. But note that institutions may have multiple instances of this tool to serve different purposes (eg. to create users with different account types), so the instructions should be configurable in the tool properties.

I'm not sure why the Travis CI build is reporting as failed on this, I downloaded the log and it clearly states that the build succeeded.

I've tested this locally with success. OOTB, the tool behaves as it always did. The introduced tool properties alter the behaviour to allow validation via email, forcing eid to match the email address, and providing customizable instructions on a per tool instance.
When configured to validate via email, the requester is given a link in the email to fill out a form to provide name and password.

I think this looks good, I think it would be nice to have some place we need some good place to document these tool properties. Could you maybe add a README.md in the top level of reset-pass in the meantime so we can build up some simple instructions?

No problem. I'm going to add the README.md to the top level of the users tool rather than reset-pass though, as the tool properties pertain to the New Account tool of users rather than reset-pass.

So I just noticed these README.md files contain a lot of markup. Is there a nice/easy way to create one of these files that you know of Matt?

Yeah, I like to use https://stackedit.io/ . This was something Earle had wanted to put in every top level we just didn't have time. Though here's the start of a README.md for the user directory. https://stackedit.io/editor#!provider=couchdb&id=V1QlahYI9i6nvRK7F7IRi1Ph

Cool, thanks for that Matt. I also did a bit of reading, and it seems that you don't actually have to create all the markup if you don't want to. So I just added a very simple README.md with some basic markdown.
So if you're good with this, I'll squash the commits down and merge.

Yeah, I don't think github supports all of the markup either. I'd just use the simplest stuff tags.
Are you going to create a new jira to cleanup generatePassword?

Ya I'll do a new Jira/PR for moving genereatePassword into kernel


Audio player style update

What
Update audio player - see design resources
Note: This ticket is for the default version which doesn't include skip ahead function, see #11032
Why
Improve style, features, and resolve accessibility issue #10231
Background
Re-designed as part of the Exhibition Guide improvement work.
Done when

Audio player primarily appears in two places on the site:

Exhibition guides
On works pages eg https://wellcomecollection.org/works/a3v24ekj

We have discussed possibility of having a  "light mode" version for works pages, however if make decision to move the audio player off works pages and into the viewer #5763 then we should be able to keep one version.


pass user session information when opening the electron app from web platform

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/15651
PROPOSAL: https://github.com/Expensify/App/issues/15651#issuecomment-1467954112
Tests

Login with account A in the desktop app.
Login with account B in the web app.
Navigate to the user profile page in the web app.
Refresh the browser.
A prompt should appear asking to 'Open the app in Electron'.
Click on it and wait for the desktop app to open.
Verify the user profile page for account B is displayed in the desktop app.

[x] Verify that no errors appear in the JS console

Offline tests

Login with account A in the desktop app.
Login with account B in the web app.
Navigate to the user profile page in the web app.
Refresh the browser.
A prompt should appear asking to 'Open the app in Electron'.
Turn off the network.
Click on 'Open the app in Electron' and wait for the desktop app to open.
Verify the login page is displayed in the desktop app.

QA Steps

Login with account A in the desktop app.
Login with account B in the web app.
Navigate to the user profile page in the web app.
Refresh the browser.
A prompt should appear asking to 'Open the app in Electron'.
Click on it and wait for the desktop app to open.
Verify the user profile page for account B is displayed in the desktop app.

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://user-images.githubusercontent.com/8579651/225961641-73dadfd3-71a4-431a-ba76-8d0bd191820e.mp4

Mobile Web - Chrome
N/A

Mobile Web - Safari
N/A

Desktop
N/A

iOS
N/A

Android
N/A

@ntdiary I'm looking at your questions right now. I'll get back to you after I get insights into these.

@ntdiary FYI the desktop deeplink is not working on main currently.

@hayata-suenaga @thesahindia One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

I'm looking at your comment now I have to be offline now and I'm OOO today, but if I can find a time tonight, I'll get back to you.

@ntdiary thank you for checking on auth token lifespan.

I temporarily let the app jump to the home page instead of getting stuck on the /transition page.

Is it possible for us to intercept the event of clicking on Open Electron button and navigate the user back to the home page?

@ntdiary does the user have to sign in again? not just refreshing the screen?

I'll wait @shawnborton's response but shouldn't we display "Please refresh again" instead?
And @ntdiary how do you suggest we trigger the change of the screen when the token expires?

there is a suggestion that we should implement a new screen for expired session and deprecate DeeplinkWrapper. @ntdiary please let me know if you're up to this 👀
https://expensify.slack.com/archives/C049HHMV9SM/p1679504172500439?thread_ts=1678823496.930569&cid=C049HHMV9SM
https://expensify.slack.com/archives/C049HHMV9SM/p1679505364500279?thread_ts=1678823496.930569&cid=C049HHMV9SM

LogInWithShortLivedAuthTokenPage (not yet committed)

@ntdiary I'll wait for your commit in the expired session screen.

@ntdiary I'm waiting for @thesahindia's review.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/pecanoro in version: 1.2.94-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 1.2.94-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@tgolen thank you very much for the comments. we should have done more thorough review.
Some of the fixes suggested changed are being implemented in this PR
@ntdiary are you up for a followup PR for fixing the original one?

Great, thank you so much for addressing these! It's gonna make this code a lot cleaner. 👍

I think this PR caused a regression https://github.com/Expensify/App/issues/17391 (details here). This PR adds the transition prefix to all deeplinks and I think we should not do that because the transition prefix is only for OLDDOT -> NEWDOT and not WEB -> DESKTOP.


Issue #29 Adding travis CI and make test

Fixes #29
Signed-off-by: Lalatendu Mohanty<EMAIL_ADDRESS>

@LalatenduMohanty This also needs rebase!

Closing this now, updated to #71


Fix up kOS KSP versioning snafu

Ok, I found an issue, now it's gotten itself in a loop.

1:<IP_ADDRESS> tests fine locally


Turn by Turn

### Tasks
- [ ] Integrate work from Demo (811 branch)
- [ ] Making work generic to any plan, demo uses hardcoded plans rn for demo

Closing since the demo is now stale


"TS2304: Cannot find name 'Storage'" error when compiling a web worker written in TypeScript

I am trying to write a web worker in TypeScript that uses Dexie, but I'm running into a compilation error from dexie's use of the Storage type (which may not be available in web worker context).
To reproduce the issue:
npm init
npm install --save dexie
npm install --save-dev typescript

Note I'm using the following package versions:
npm ls
+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>
Then create a worker using TypeScript that imports dexie:
worker.ts:
import Dexie from 'dexie';
console.log('Hello from worker land!');

Now try to compile it using TypeScript, using the proper context for web workers:
tsc --lib es6,webworker worker.ts

Note this results in a compilation error:
node_modules/dexie/dist/dexie.d.ts(57,24): error TS2304: Cannot find name 'Storage'.

As far as I can tell, the Storage type refers to the Web Storage API (session storage and local storage), which are not accessible from a web worker context, so it makes sense that it can't compile.
Short of dropping down to vanilla JavaScript for web workers, is there a workaround for this?

If I remember correctly dexie does work in webworkers and this is just a compiler error. Since typescript can emit javascript even when there are compiler errors you could just ignore the error.
You could also just define Storage as a type to avoid the error or try to extend --lib es6,webworker to contain whatever d.ts file contains Storage (probably dom).

You could also try dexie@next (version 2.0-beta.10) with no dependence of localStorage

I appreciate the help!

Since typescript can emit javascript even when there are compiler errors you could just ignore the error.

Sure, that works, but obviously it's less than ideal. The build system for the project I'm hoping to use this for actually halts the build in case of compilation errors, though it's something I could disable (or just use pure JS for web workers instead, which I think I'll be going with for the time being).

You could also just define Storage as a type to avoid the error

I'm still a bit new to TypeScript, but how do I do that? In my example, I tried putting this as the first line of worker.ts (before importing dexie), but it still gave me a compilation error:
declare var Storage: any;

Also tried:
interface Storage {}

But I was still getting the error in both cases. I'm wondering if I won't actually be able to fix this from my worker.ts file (short of messing with dexie.d.ts inside the module).

or try to extend --lib es6,webworker to contain whatever d.ts file contains Storage (probably dom).

Well, if I add dom, then it complains about a bunch of duplicate declarations - I don't think you can use dom together with webworker, since they share a lot of types.
If I replace webworker with dom, then I run into other issues since there are global functions that have different call signatures between the DOM version and the web worker version. For example, postMessage can be called with a single parameter when called from a web worker, but not in DOM. So if I have this in my web worker:
postMessage("This is a message from a web worker");

Trying to compile it with the dom lib results in:
error TS2346: Supplied parameters do not match any signature of call target.

You could also try dexie@next (version 2.0-beta.10) with no dependence of localStorage

I tried it, but I'm running into the same compilation error (Cannot find name 'Storage'). Looking at the dist/dexie.d.ts file that ships with both dexie 1.5.1 and 2.0.0-beta.10, looks like they both have this block in there:
    static dependencies: {
        indexedDB: IDBFactory,
        IDBKeyRange: IDBKeyRange,
        localStorage?: Storage
    };

By the way, is there separate API documentation for Dexie 2, or is it pretty much identical to Dexie 1.5 so I can use the same docs?

@sergkr Sorry for late answer. I see. It's wrong that localStorage is part of dependencies in 2.0. Will remove it. Thanks for reporting.
To answer your question, the API docs are the same. Where there is a difference, the docs will tell point out the difference. Deprecated parts of the 1.x API is listed under http://dexie.org/docs/Deprecations.

Thanks @dfahlander!


Enforce conditional validation of augmented data

Resolves #57

All tests are now running, except the EGA known issue,


Scene transitions don't fade properly or never fade in

Describe the bug
When transitioning from one scene to another the fade is sometimes very choppy (feels almost instantaneous, especially when fading to black) and there are occasions where it doesn't fade in at all. I wasn't able to isolate the problem properly, but my best guess is that it has to do with the recent changes to which events make the fade in wait.
One example: the Wait event now also delays the fade in when used at the start of a scene, which isn't what I would expect.
To Reproduce
I've attached a test project, which highlights some of the issues.
TestLab.zip
Expected behavior
If my guess is correct, I would only include events that don't execute over more than one frame in the list of events that delay the fade in.
Screenshots
https://user-images.githubusercontent.com/9643886/149205615-e87dbf4c-8e00-447f-a925-776940f2b7e8.mp4
Platform (please complete the following information):

OS: Windows 10
App version 3.0.2 (develop branch)

Additional context
Another possible culprit could be the engine field edit of the transition color, as I often change it right before changing the scene.

This works now by setting the Fade In manually (instead of using the new auto Fade In).


Create a Security page

On this page, provide the following information:

Zowe security principles (being worked on)
How to report security issues. Use the same information on the doc site: https://docs.zowe.org/stable/contribute/roadmap-contribute/#report-security-issues

Both is now part of the zowe.org/security


set non-zero rc when help2man fails to generate file

make sure check fails if any man pages can't be generated

Message on line 76 is missing the text "--version." . Since it needs editing anyway, would matching the format of the message on line 70 be consistent...?

The messages are different because there are different problems - it could be missing one of --version, --help, or both.


Change CODEOWNERS to be 1.10 release managers

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

@jacob-delgado: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jacob-delgado: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.10
7f3fc324c0f5b0fffefae8be00aeb718a25e48c2
link
/test test-tsan_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.10
7f3fc324c0f5b0fffefae8be00aeb718a25e48c2
link
/test test-tsan_envoy_release-1.10

test-asan_envoy_release-1.10
7f3fc324c0f5b0fffefae8be00aeb718a25e48c2
link
/test test-asan_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[stable/verdaccio] failed to download?

$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "jetstack" chart repository
Update Complete. ⎈ Happy Helming!⎈

$ helm install --namespace=npm-verdaccio npm-registery-verdaccio stable/verdaccio
Error: failed to download "stable/verdaccio" (hint: running `helm repo update` may help)

Version of Helm and Kubernetes:
helm version
version.BuildInfo{Version:"v3.0.2", GitCommit:"19e47ee3283ae98139d98460de796c1be1e3975f", GitTreeState:"clean", GoVersion:"go1.13.5"}
kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"archive", BuildDate:"1970-01-01T00:00:01Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

Same here.
I am using Helm on Docker.
My helm alias looks like:
alias helm='docker run -e KUBECONFIG="/root/.kube/config:/root/.kube/digitalocean-tutorial-kubeconfig.yaml:/root/.kube/helm-drupal-issue-kubeconfig.yaml" -ti --rm -v $(pwd):/apps -v ~/.kube:/root/.kube -v ~/.config/helm:/root/.config/helm -v ~/.helm:/root/.helm alpine/helm'

I cannot install a chart from here though:
$ helm version
version.BuildInfo{Version:"v3.1.1", GitCommit:"afe70585407b420d0097d07b21c47dc511525ac8", GitTreeState:"clean", GoVersion:"go1.13.8"}
$ helm repo add stable https://kubernetes-charts.storage.googleapis.com
"stable" has been added to your repositories
$ helm install my-first-vanilla-drupal stable/drupal
Error: failed to download "stable/drupal" (hint: running `helm repo update` may help)
$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈
$ helm install my-first-vanilla-drupal stable/drupal
Error: failed to download "stable/drupal" (hint: running `helm repo update` may help)

So in my case I was using Helm on Docker and had to fix which volumes I was sharing between my host and my container. For helm charts in repos to work correctly, ~/.cache/helm and ~/.config/helm need to be shared.
Here are the changes to how I'm using helm on Docker:

https://github.com/alpine-docker/helm/pull/17/files
https://github.com/alpine-docker/helm/pull/18/files

This is required from what I understand starting in Helm 3.
@chrissound can you please confirm that you are using helm on docker and that your helm command is an alias (not locally installed), possibly in your ~/.bash_profile file. If so you might want to add:
-v ~/.config/helm:/root/.config/helm -v ~/.cache/helm:/root/.cache/helm

If not, then your problem is not related to mine.


How to properly extends types using declarations file

Hello! I'm currently using declaration files to add missing types or correct some of existing ones. This works fairly well, but I couldn't properly add 'root-level' api (like browser.tabGroups) using this approach. Do you maybe know how to do it properly? This is how I tried to do it, but it didn't work:
import 'webextension-polyfill';

declare module 'webextension-polyfill' {
    // Extending existing APIs works fine
    namespace Tabs {
        interface Static {
            group: (options: {createProperties?: {windowId?: number}, groupId?: number, tabIds?: number | number[]}) => Promise<number>
        }
    }

    // Adding new API doesn't work :(
    namespace Browser {
        type TabGroupColor = "grey" | "blue" | "red" | "yellow" | "green" | "pink" | "purple" | "cyan" | "orange";
        interface TabGroup {
            collapsed: boolean,
            color: TabGroupColor,
            id: number,
            windowId: number,
            title?: string,
        }

        interface TabGroupsStatic {
            update: (groupId: number, updateProperties: {collapsed?: boolean, color?: TabGroupColor, title?: string}, ) => Promise<TabGroup | undefined>
        }

        const tabGroups: TabGroupsStatic;

        interface Browser {
            tabGroups: TabGroupsStatic
        }
    }
}

Hi,
Not sure why this does not work on root level.. possibly because of the namespace & interface combination.
Since you are using a chrome-only API, maybe it would be an option make it chrome-specific?
Let's say you start with the following:
type TabGroupColor = "grey" | "blue" | "red" | "yellow" | "green" | "pink" | "purple" | "cyan" | "orange";
interface TabGroup {
    collapsed: boolean;
    color: TabGroupColor;
    id: number;
    windowId: number;
    title?: string;
}

interface ChromeTabGroupsStatic {
    update: (
        groupId: number,
        updateProperties: { collapsed?: boolean; color?: TabGroupColor; title?: string }
    ) => Promise<TabGroup | undefined>;
}

interface ChromeTabsStatic {
    group: (options: {
        createProperties?: { windowId?: number };
        groupId?: number;
        tabIds?: number | number[];
    }) => Promise<number>;
}

type ChromeBrowserAdditions = {
    tabGroups: ChromeTabGroupsStatic;
    tabs: ChromeTabsStatic;
};

You now  have 3 possibilities to chose from:
Option 1:  isChromeBrowser check (if you want to stay cross-browser compatible):
function isChromeBrowser<T extends Browser>(browser: T): browser is T & ChromeBrowserAdditions {
    return "tabGroups" in browser;
}

if (isChromeBrowser(browser)) {
    browser.tabGroups.update(0, {});
}

Now everywhere you use chrome-specific code, you can easily do so by first checking for chrome.
Option 2: A new constant (if you want to use the polyfill export, but no browser check is wanted):
const chrome = browser as Browser & ChromeBrowserAdditions;
chrome.tabGroups.update(0, {});

Option 3: declaring global (if you only care about the types from this package)
declare global {
    const chrome: Browser & ChromeBrowserAdditions;
}

chrome.tabGroups.update(0, {});

Hope this helps

First option will be the best, thanks you very much!


Running xs in a Dev Container doesn't work

Running xs in Dev Container caused a  Permission denied
node ➜ /workspaces/vscode-sap-hana-dev-env-for-running-hana-cli-2 (main ✗) $ xs
bash: /workspaces/vscode-sap-hana-dev-env-for-running-hana-cli-2/XS_CLIENT00P_134-70001320/bin/xs: Permission denied
Dev Container:  - running xs doesn't works!*
node ➜ /workspaces/vscode-sap-hana-dev-env-for-running-hana-cli-2/XS_CLIENT00P_134-70001320/bin (main ✗) $ ls -lt
total 4
-rw-r--r-- 1 node node 1696 Jun  7 13:49 xs

node ➜ /workspaces/vscode-sap-hana-dev-env-for-running-hana-cli-2/XS_CLIENT00P_134-70001320 (main ✗) $ ls -lt
total 52
drwxr-xr-x 5 node node  4096 Aug  2 13:01 sapjvm_8_jre
drwxr-xr-x 3 node node  4096 Aug  2 13:01 jars
drwxr-xr-x 2 node node  4096 Aug  2 13:01 bin
-rw-r--r-- 1 node node 37245 Jun 17 11:08 SIGNATURE.SMF

WSL locally: - running xs works!
➜  bin git:(main) ✗ ls -lt
total 4
-rw-r--r-- 1 diraschk diraschk 1696 Jun  7 15:49 xs

➜  XS_CLIENT00P_134-70001320 git:(main) ✗ ls -lt
total 52
drwxr-xr-x 5 diraschk diraschk  4096 Aug  2 15:01 sapjvm_8_jre
drwxr-xr-x 3 diraschk diraschk  4096 Aug  2 15:01 jars
drwxr-xr-x 2 diraschk diraschk  4096 Aug  2 15:01 bin

Before you start your Dev Container, you need to set the -x permission to the XS_CLIENT00P_134-70001320/bin/xs file with root
chmod -R +x xs
before setting permission
-rw-r--r-- 1 diraschk diraschk 1696 Aug  3 09:12 xs
after setting permission
-rwxr-xr-x 1 diraschk diraschk 1696 Aug  3 09:12 xs

And before you start your Dev Container, you need to set the -x permission within the XS_CLIENT00P_134-70001320/sapjvm_8_jre/bin folder with root
chmod -R +x bin

I tried it again:  chmod -R +x xs
Changed at first the permission in WSL Ubuntu
(You can see the result for before and after changing the permission within the two /bin folders.)

After the changes I was able to use the XS-Client for XSA connection.

If someone has a solution for doing this inside of the dockerfile I would appreciate it to let me know how this works!


Merge branch 'master' of https://github.com/Code-and-Response/Promete…

…o-Mobile-App
Conflicts:
app/src/main/AndroidManifest.xml
app/src/main/java/com/prometeo/BluetoothLeService.java
app/src/main/java/com/prometeo/DeviceControlActivity.java
app/src/main/java/com/prometeo/DeviceScanActivity.java
app/src/main/java/com/prometeo/ScanDevice_old.java
app/src/main/java/com/prometeo/ui/home/HomeFragment.java
app/src/main/res/values/strings.xml

Change look & feel


Add rpath tests for macho

Expected to fail
Tests for https://github.com/microsoft/vcpkg/pull/39889
This mimics the situation of libssl/libcrypto of the openssl port.
A lot of boilerplate code is copied from the existing rpath tests, interesting addition is here https://github.com/microsoft/vcpkg/compare/master...m-kuhn:vcpkg:rpath-macho-test?expand=1#diff-df76c3210c8286fde1e58d91e8aec9b40df0dc0d76a238e918c8533971c3e4f7R33-R59

Thanks! It would've taken me a while to figure out myself.

Closing in favor of https://github.com/microsoft/vcpkg/pull/39889
The proof that this fails with the current state of code is provided.


Upload web-assets for packages.grpc.io

Store authoritative copy of the non-image contents of gs://packages.grpc.io/web-assets in the git repo.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,976,372      Total (=)      1,976,372

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,770,425      Total (>)     10,770,420

 No significant differences in binary sizes

[microbenchmarks] No significant performance differences


Add fix for bug with hyperindices

Summary
Updated contract_hyper_indices function to address bug
Implementation Details
Updated logic contract_hyper_indices function to address bug and added test to ensure test case is working.

Check before merging:

[x] All discussions are resolved
[x] New code is covered by appropriate tests
[ ] Tests are passing locally and on CI
[x] The documentation is consistent with changes
[x] Any code that was copied from other sources has the paper/url in a comment and is compatible with the MIT licence
[x] Notebooks/examples not covered by unittests have been tested and updated as required
[x] The feature branch is up-to-date with the master branch (rebase if behind)
[x] Incremented the version string in Project.toml file

Codecov Report

Merging #8 (bb2ed3a) into master (225482d) will decrease coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
- Coverage   81.65%   81.56%   -0.10%
==========================================
  Files           7        6       -1
  Lines         398      396       -2
==========================================
- Hits          325      323       -2
  Misses         73       73

Impacted Files
Coverage Δ

src/utils.jl
98.52% <ø> (ø)

src/tensor.jl
98.52% <100.00%> (-0.03%)
:arrow_down:

src/tensor_network.jl
70.50% <100.00%> (ø)

Continue to review full report at Codecov.

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


Merge sandbox UI into production

enhance preview build and align with Antora 2.3
general style changes
update header and header styles
add templates, CSS, and JavaScript to support listing page and individual pages for connectors

One thing we should do before merging is updating the dependencies. It's always a good idea to do this when making a major update so the code is as current as possible.


Fix: add missing types exports

Codecov Report

Merging #482 (6a47a7b) into main (19d7592) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #482   +/-   ##
=======================================
  Coverage   98.27%   98.27%
=======================================
  Files          73       73
  Lines         811      811
  Branches      128      128
=======================================
  Hits          797      797
  Misses         12       12
  Partials        2        2

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


captured stdout output is garbled

Running git --version directly returns correct result, but if I assign it to a variable then it will be garbled: $x = git --version; $x.

Whoa! I was able to repro; that is a weird bug. Thanks for the report, I will hopefully have a minute to look into it soon.

Fixed in 7cf3747681eeb6ac320e0e638b753c18612edfcb (you can read the commit message for more details).
Thank you for the report @wangzq!


防止多次点击刷屏操作

多次点击发表评论，系统提示请勿刷屏
By
张欢欣
黄文心
梁怡萱
刘庐庐

@1500h
Could you show that your changes work when the software is running.
-Hui

@1500h
Could you show that your changes work when the software is running.
-Hui

------------------ 原始邮件 ------------------
发件人:                                                                                "lanlab-org/OAPS-TreeLib"<EMAIL_ADDRESS>发送时间: 2021年1月5日(星期二) 下午2:35
收件人<EMAIL_ADDRESS>抄送: "1020193782"<1020193782<EMAIL_ADDRESS>主题: Re: [lanlab-org/OAPS-TreeLib] 防止多次点击刷屏操作 (#52)
@1500h
Could you show that your changes work when the software is running.
-Hui
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

------------------ 原始邮件 ------------------
发件人:                                                                                "lanlab-org/OAPS-TreeLib"<EMAIL_ADDRESS>发送时间: 2021年1月5日(星期二) 下午2:35
收件人<EMAIL_ADDRESS>抄送: "1020193782"<1020193782<EMAIL_ADDRESS>主题: Re: [lanlab-org/OAPS-TreeLib] 防止多次点击刷屏操作 (#52)
@1500h
Could you show that your changes work when the software is running.
-Hui
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I was going to write a function of prevent (). Later, I found that I just need to add an ID instead of onclick = "prevent ()", and I forgot to delete it
------------------ 原始邮件 ------------------
发件人:                                                                                "lanlab-org/OAPS-TreeLib"<EMAIL_ADDRESS>发送时间: 2021年1月5日(星期二) 下午2:27
收件人<EMAIL_ADDRESS>抄送: "1020193782"<1020193782<EMAIL_ADDRESS>主题: Re: [lanlab-org/OAPS-TreeLib] 防止多次点击刷屏操作 (#52)
@spm2020spring commented on this pull request.
In templates/article.html:
> @@ -130,8 +131,21 @@
{{ article.title }}
            <textarea class="form-control" rows="3" name="body" placeholder="write something here..." required="required"></textarea>
   -        <button class="btn btn-primary" type="submit" style="float:right">comment</button> +        <button id="btn" class="btn btn-primary" type="submit" style="float:right"  onClick="prevent()">comment</button>
@1500h
Why do you have the prevent() method, which is not defined anywhere?
-Hui
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I was going to write a function of prevent (). Later, I found that I just need to add an ID instead of onclick = "prevent ()", and I forgot to delete it
------------------ 原始邮件 ------------------
发件人:                                                                                "lanlab-org/OAPS-TreeLib"<EMAIL_ADDRESS>发送时间: 2021年1月5日(星期二) 下午2:27
收件人<EMAIL_ADDRESS>抄送: "1020193782"<1020193782<EMAIL_ADDRESS>主题: Re: [lanlab-org/OAPS-TreeLib] 防止多次点击刷屏操作 (#52)
@spm2020spring commented on this pull request.
In templates/article.html:
> @@ -130,8 +131,21 @@
{{ article.title }}
            <textarea class="form-control" rows="3" name="body" placeholder="write something here..." required="required"></textarea>
   -        <button class="btn btn-primary" type="submit" style="float:right">comment</button> +        <button id="btn" class="btn btn-primary" type="submit" style="float:right"  onClick="prevent()">comment</button>
@1500h
Why do you have the prevent() method, which is not defined anywhere?
-Hui
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

It can be set to one minute，change 5000 to 5000*60
------------------ 原始邮件 ------------------
发件人:                                                                                "lanlab-org/OAPS-TreeLib"<EMAIL_ADDRESS>发送时间: 2021年1月5日(星期二) 下午2:30
收件人<EMAIL_ADDRESS>抄送: "1020193782"<1020193782<EMAIL_ADDRESS>主题: Re: [lanlab-org/OAPS-TreeLib] 防止多次点击刷屏操作 (#52)
@spm2020spring commented on this pull request.
In templates/article.html:
>      </form> +


fixed reading mode

Deployed to: http://staging.quran.com:32832

Deployed to: http://staging.quran.com:32833


tgcf forwards all pictures inspite of using a whitelist filter

Describe the bug
When using a whitelist filter, it will still forward all pictures
To Reproduce
Use a whitelist text filter, and try sending a photo
Expected behavior
It shouldn't forward the picture unless it includes a tag with the keyword
System information:
Running on Heroku

@RebbePod Please provide a screenshot

I can try, it's pretty self explanatory and would be hard to bring out in a screenshot.

i have solved this problem @RebbePod
make sure you have installed the latest version of tgcf 0.1.26 or above, to test it out.

hi @RebbePod help tgcf grow!
please share with your friends and different telegram groups and channels and social media.
thank you

Thank you so much, what's the easiest way to update? (Using heroku)

what's the easiest way to update? (Using heroku)

create a fresh new deploy

Thanks. Confirmed it's working.


what about skipping to a new line?

So far I like the functionality, but it would also be nice if there was a combo for adding a semicolon and starting a new line. Maybe ctrl-shift-; and ctrl-shift-,?

There is ctrl-enter (by default in Atom) that allows you to start a new line wherever you are in the current line. Would that suit your need despite needing another key press ?
If it doesn't, I think your request would be easy to implement (although I would be reluctant to add yet another key mapping by default).

Yeah, that works too. There's also just going to the end of the line.
It would definitely be worth adding the functionality without default keybindings.
Also, ctrl-shift-; is a horrible idea, ctrl-alt-; is way easier to use.

I updated the package, there are two new commands named trailing-semicolon:semicolon-newline and trailing-semicolon:comma-newline to start a new line after adding the semicolon/comma. It behaves exactly like ctrl-enter.
There is also a new setting that allows you to enable this behavior for the default commands.


Revert "KAFKA-9705 part 1: add KIP-590 request header fields (#9144)"

This reverts commit 21dc5231ce9c7398c7ede4dbefa2f2202e06b2d4. As we no longer use initial principals, it makes sense to revert on trunk and 2.7 as well.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

retest this please

retest this please

test this

retest this


Ancestry: support other country domains beyond .com

United Kingdom: .co.uk
Canada: .ca
Australia: .com.au
Germany: .de
Italy: .it
France: .fr
Sweden: .se
Mexico: .mx
Or perhaps just the English ones for now because the Ancestry parser only works with English labels.

Be sure to update the Agent info to match the source domain

I've fixed this issue and created a pull request, #85. How do you assign yourself to an issue?

#85 added support for 3 additional domains.


Refactor webpack config

See conversation in #29 issue

@nugaon this issue has been open for quite a while, and we didn't identify any notable issues with webpack.
The only thing I can think of is removing BundleAnalyzerPlugin.
Should I proceed with that, so we can close this issue?

yeah, we can close it.


Aarch64 compile inline asm error: unexpected token in argument list

I'm running Debian GNU/Linux 8 on a Qualcomm/Arrow Dragonboard 410C and am having trouble compiling libobjc2.
I'm using commit 2ea11117a392646d960f1e861494e2f27873b15b, and Clang 3.7 was apt-gotten.
linaro@linaro-alip:~/libobjc2/build$ uname -a
Linux linaro-alip 4.2.4-linaro-lt-qcom #1 SMP PREEMPT Fri Dec 4 12:42:30 UTC 2015 aarch64 GNU/Linux

Here is the output of make.
Scanning dependencies of target objc
[  1%] Building C object CMakeFiles/objc.dir/abi_version.c.o
[  2%] Building C object CMakeFiles/objc.dir/alias_table.c.o
[  3%] Building C object CMakeFiles/objc.dir/block_to_imp.c.o
[  4%] Building C object CMakeFiles/objc.dir/caps.c.o
[  5%] Building C object CMakeFiles/objc.dir/category_loader.c.o
[  6%] Building C object CMakeFiles/objc.dir/class_table.c.o
[  7%] Building C object CMakeFiles/objc.dir/dtable.c.o
[  8%] Building C object CMakeFiles/objc.dir/eh_personality.c.o
[  9%] Building C object CMakeFiles/objc.dir/encoding2.c.o
[ 10%] Building C object CMakeFiles/objc.dir/hash_table.c.o
[ 11%] Building C object CMakeFiles/objc.dir/hooks.c.o
[ 12%] Building C object CMakeFiles/objc.dir/ivar.c.o
[ 13%] Building C object CMakeFiles/objc.dir/legacy_malloc.c.o
[ 14%] Building C object CMakeFiles/objc.dir/loader.c.o
[ 15%] Building CXX object CMakeFiles/objc.dir/mutation.m.o
[ 16%] Building C object CMakeFiles/objc.dir/protocol.c.o
[ 17%] Building C object CMakeFiles/objc.dir/runtime.c.o
[ 18%] Building C object CMakeFiles/objc.dir/sarray2.c.o
[ 19%] Building C object CMakeFiles/objc.dir/selector_table.c.o
[ 20%] Building C object CMakeFiles/objc.dir/sendmsg2.c.o
[ 21%] Building C object CMakeFiles/objc.dir/statics_loader.c.o
[ 22%] Building C object CMakeFiles/objc.dir/toydispatch.c.o
[ 23%] Building ASM object CMakeFiles/objc.dir/block_trampolines.S.o
[ 25%] Building ASM object CMakeFiles/objc.dir/objc_msgSend.S.o
[ 26%] Building C object CMakeFiles/objc.dir/NSBlocks.m.o
[ 27%] Building C object CMakeFiles/objc.dir/Protocol2.m.o
[ 28%] Building C object CMakeFiles/objc.dir/arc.m.o
[ 29%] Building C object CMakeFiles/objc.dir/associate.m.o
[ 30%] Building C object CMakeFiles/objc.dir/blocks_runtime.m.o
[ 31%] Building C object CMakeFiles/objc.dir/properties.m.o
[ 32%] Building C object CMakeFiles/objc.dir/gc_none.c.o
Linking C shared library libobjc.so
[ 32%] Built target objc
Scanning dependencies of target objcxx
[ 33%] Building CXX object CMakeFiles/objcxx.dir/objcxx_eh.cc.o
Linking C shared library libobjcxx.so
[ 33%] Built target objcxx
Scanning dependencies of target AllocatePair
[ 34%] Building CXX object Test/CMakeFiles/AllocatePair.dir/AllocatePair.m.o
Linking C executable AllocatePair
[ 34%] Built target AllocatePair
Scanning dependencies of target AllocatePair_optimised
[ 35%] Building CXX object Test/CMakeFiles/AllocatePair_optimised.dir/AllocatePair.m.o
Linking C executable AllocatePair_optimised
[ 35%] Built target AllocatePair_optimised
Scanning dependencies of target AssociatedObject
[ 36%] Building CXX object Test/CMakeFiles/AssociatedObject.dir/AssociatedObject.m.o
Linking C executable AssociatedObject
[ 36%] Built target AssociatedObject
Scanning dependencies of target AssociatedObject2
[ 37%] Building CXX object Test/CMakeFiles/AssociatedObject2.dir/AssociatedObject2.m.o
Linking C executable AssociatedObject2
[ 37%] Built target AssociatedObject2
Scanning dependencies of target AssociatedObject2_optimised
[ 38%] Building CXX object Test/CMakeFiles/AssociatedObject2_optimised.dir/AssociatedObject2.m.o
Linking C executable AssociatedObject2_optimised
[ 38%] Built target AssociatedObject2_optimised
Scanning dependencies of target AssociatedObject_optimised
[ 39%] Building CXX object Test/CMakeFiles/AssociatedObject_optimised.dir/AssociatedObject.m.o
Linking C executable AssociatedObject_optimised
[ 39%] Built target AssociatedObject_optimised
Scanning dependencies of target BlockImpTest
[ 40%] Building CXX object Test/CMakeFiles/BlockImpTest.dir/BlockImpTest.m.o
Linking C executable BlockImpTest
[ 40%] Built target BlockImpTest
Scanning dependencies of target BlockImpTest_optimised
[ 41%] Building CXX object Test/CMakeFiles/BlockImpTest_optimised.dir/BlockImpTest.m.o
Linking C executable BlockImpTest_optimised
[ 41%] Built target BlockImpTest_optimised
Scanning dependencies of target BlockTest_arc
[ 42%] Building CXX object Test/CMakeFiles/BlockTest_arc.dir/BlockTest_arc.m.o
[ 43%] Building CXX object Test/CMakeFiles/BlockTest_arc.dir/Test.m.o
Linking C executable BlockTest_arc
[ 43%] Built target BlockTest_arc
Scanning dependencies of target BlockTest_arc_optimised
[ 44%] Building CXX object Test/CMakeFiles/BlockTest_arc_optimised.dir/BlockTest_arc.m.o
[ 45%] Building CXX object Test/CMakeFiles/BlockTest_arc_optimised.dir/Test.m.o
Linking C executable BlockTest_arc_optimised
[ 45%] Built target BlockTest_arc_optimised
Scanning dependencies of target BoxedForeignException
[ 46%] Building CXX object Test/CMakeFiles/BoxedForeignException.dir/BoxedForeignException.m.o
Linking C executable BoxedForeignException
[ 46%] Built target BoxedForeignException
Scanning dependencies of target BoxedForeignException_optimised
[ 47%] Building CXX object Test/CMakeFiles/BoxedForeignException_optimised.dir/BoxedForeignException.m.o
Linking C executable BoxedForeignException_optimised
[ 47%] Built target BoxedForeignException_optimised
Scanning dependencies of target CXXExceptions
[ 48%] Building CXX object Test/CMakeFiles/CXXExceptions.dir/CXXException.m.o
[ 50%] Building CXX object Test/CMakeFiles/CXXExceptions.dir/CXXException.cc.o
Linking C executable CXXExceptions
[ 50%] Built target CXXExceptions
Scanning dependencies of target CXXExceptions_optimised
[ 51%] Building CXX object Test/CMakeFiles/CXXExceptions_optimised.dir/CXXException.m.o
[ 52%] Building CXX object Test/CMakeFiles/CXXExceptions_optimised.dir/CXXException.cc.o
Linking C executable CXXExceptions_optimised
[ 52%] Built target CXXExceptions_optimised
Scanning dependencies of target ExceptionTest
[ 53%] Building CXX object Test/CMakeFiles/ExceptionTest.dir/ExceptionTest.m.o
Linking C executable ExceptionTest
[ 53%] Built target ExceptionTest
Scanning dependencies of target ExceptionTest_optimised
[ 54%] Building CXX object Test/CMakeFiles/ExceptionTest_optimised.dir/ExceptionTest.m.o
Linking C executable ExceptionTest_optimised
[ 54%] Built target ExceptionTest_optimised
Scanning dependencies of target ForeignException
[ 55%] Building CXX object Test/CMakeFiles/ForeignException.dir/ForeignException.m.o
Linking C executable ForeignException
[ 55%] Built target ForeignException
Scanning dependencies of target ForeignException_optimised
[ 56%] Building CXX object Test/CMakeFiles/ForeignException_optimised.dir/ForeignException.m.o
Linking C executable ForeignException_optimised
[ 56%] Built target ForeignException_optimised
Scanning dependencies of target Forward
[ 57%] Building CXX object Test/CMakeFiles/Forward.dir/Forward.m.o
Linking C executable Forward
[ 57%] Built target Forward
Scanning dependencies of target Forward_optimised
[ 58%] Building CXX object Test/CMakeFiles/Forward_optimised.dir/Forward.m.o
Linking C executable Forward_optimised
[ 58%] Built target Forward_optimised
Scanning dependencies of target ManyManySelectors
[ 59%] Building CXX object Test/CMakeFiles/ManyManySelectors.dir/ManyManySelectors.m.o
Linking C executable ManyManySelectors
[ 59%] Built target ManyManySelectors
Scanning dependencies of target ManyManySelectors_optimised
[ 60%] Building CXX object Test/CMakeFiles/ManyManySelectors_optimised.dir/ManyManySelectors.m.o
Linking C executable ManyManySelectors_optimised
[ 60%] Built target ManyManySelectors_optimised
Scanning dependencies of target MethodArguments
[ 61%] Building CXX object Test/CMakeFiles/MethodArguments.dir/MethodArguments.m.o
Linking C executable MethodArguments
[ 61%] Built target MethodArguments
Scanning dependencies of target MethodArguments_optimised
[ 62%] Building CXX object Test/CMakeFiles/MethodArguments_optimised.dir/MethodArguments.m.o
Linking C executable MethodArguments_optimised
[ 62%] Built target MethodArguments_optimised
Scanning dependencies of target NestedExceptions
[ 63%] Building CXX object Test/CMakeFiles/NestedExceptions.dir/NestedExceptions.m.o
Linking C executable NestedExceptions
[ 63%] Built target NestedExceptions
Scanning dependencies of target NestedExceptions_optimised
[ 64%] Building CXX object Test/CMakeFiles/NestedExceptions_optimised.dir/NestedExceptions.m.o
Linking C executable NestedExceptions_optimised
[ 64%] Built target NestedExceptions_optimised
Scanning dependencies of target NilException
[ 65%] Building CXX object Test/CMakeFiles/NilException.dir/NilException.m.o
Linking C executable NilException
[ 65%] Built target NilException
Scanning dependencies of target NilException_optimised
[ 66%] Building CXX object Test/CMakeFiles/NilException_optimised.dir/NilException.m.o
Linking C executable NilException_optimised
[ 66%] Built target NilException_optimised
Scanning dependencies of target PropertyAttributeTest
[ 67%] Building CXX object Test/CMakeFiles/PropertyAttributeTest.dir/PropertyAttributeTest.m.o
Linking C executable PropertyAttributeTest
[ 67%] Built target PropertyAttributeTest
Scanning dependencies of target PropertyAttributeTest_optimised
[ 68%] Building CXX object Test/CMakeFiles/PropertyAttributeTest_optimised.dir/PropertyAttributeTest.m.o
Linking C executable PropertyAttributeTest_optimised
[ 68%] Built target PropertyAttributeTest_optimised
Scanning dependencies of target PropertyIntrospectionTest
[ 69%] Building CXX object Test/CMakeFiles/PropertyIntrospectionTest.dir/PropertyIntrospectionTest.m.o
Linking C executable PropertyIntrospectionTest
[ 69%] Built target PropertyIntrospectionTest
Scanning dependencies of target PropertyIntrospectionTest2_arc
[ 70%] Building CXX object Test/CMakeFiles/PropertyIntrospectionTest2_arc.dir/PropertyIntrospectionTest2_arc.m.o
<inline asm>:1:27: error: unexpected token in argument list
        mov     fp, fp          ; marker for objc_retainAutoreleaseReturnValue
                                             ^
<inline asm>:1:27: error: unexpected token in argument list
        mov     fp, fp          ; marker for objc_retainAutoreleaseReturnValue
                                             ^
<inline asm>:1:27: error: unexpected token in argument list
        mov     fp, fp          ; marker for objc_retainAutoreleaseReturnValue
                                             ^
<inline asm>:1:27: error: unexpected token in argument list
        mov     fp, fp          ; marker for objc_retainAutoreleaseReturnValue
                                             ^
<inline asm>:1:27: error: unexpected token in argument list
        mov     fp, fp          ; marker for objc_retainAutoreleaseReturnValue
                                             ^
5 errors generated.
Test/CMakeFiles/PropertyIntrospectionTest2_arc.dir/build.make:54: recipe for target 'Test/CMakeFiles/PropertyIntrospectionTest2_arc.dir/PropertyIntrospectionTest2_arc.m.o' failed
make[2]: *** [Test/CMakeFiles/PropertyIntrospectionTest2_arc.dir/PropertyIntrospectionTest2_arc.m.o] Error 1
CMakeFiles/Makefile2:1359: recipe for target 'Test/CMakeFiles/PropertyIntrospectionTest2_arc.dir/all' failed
make[1]: *** [Test/CMakeFiles/PropertyIntrospectionTest2_arc.dir/all] Error 2
Makefile:147: recipe for target 'all' failed
make: *** [all] Error 2

As of version 3.9 (trunk from 03/15/2016) the issue is still there.

Any idea what line in what file in the CLANG source I have to patch to make this work at least for myself?

Look in clang/lib/CodeGen/TargetInfo.cpp.  There's a method AArch64TargetCodeGenInfo::getARCRetainAutoreleasedReturnValueMarker().  This should probably be conditional on targeting a Mac runtime, but if you just want something that works for now then simply making it return nullptr should work.

Found it!  Awesome!  Thank you!!!!!
--
Galen Rhodes
<EMAIL_ADDRESS>
On Mar 30, 2016, at 2:13 PM, davidchisnall<EMAIL_ADDRESS>wrote:
Look in clang/lib/CodeGen/TargetInfo.cpp. There's a method AArch64TargetCodeGenInfo::getARCRetainAutoreleasedReturnValueMarker(). This should probably be conditional on targeting a Mac runtime, but if you just want something that works for now then simply making it return nullptr should work.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub https://github.com/gnustep/libobjc2/issues/14#issuecomment-203561251

I believe that this is now fixed in clang.


Move code into folder, delete enviroment2 and add pyspark to the new enviroment

I've already modified the Docker


Unable to run update-schema.ps1

When attempting to add the custom action (https://docs.microsoft.com/en-us/composer/how-to-create-custom-actions). The final step of merging the two schema files is failing.
if I update the script and change "!**/generated" to "!../generated" I am able to remove some errors.  Doing this will remove the first block of errors.

I also have removed a orphaned dialog that seems to resolve other issues but still have issues remaining. With the AcsSMSAdapter

I also attempted to copy from the sample custom action project from here https://github.com/microsoft/BotBuilder-Samples/tree/main/composer-samples/csharp_dotnetcore/projects/CustomAction/MultiplyDialog This still had the exact same issues with the PowerShell script for merging the custom schema.

Hi @piechk -- Thanks, looking into it.

Hi @piechk,

What is your BF Command Line Interface (CLI) version?

type bf -v in termal to find bf version

I created "Core Bot with Language" in composer(v2.1.1) and followed the Create custom actions docs here and I was able to repro this issue. Though, my stack trace error was similar this issue-> #8501

I found a work around here and was able to merge schema successfully.

In your bot directory, find the schemas folder, and open update-schema.ps1
Line 11, change "!**/generated" to "!../generated" and add "!../dialogs/imported"

Example
bf dialog:merge "*.schema" "!**/sdk-backup.schema" "*.uischema" "!**/sdk-backup.uischema" "!**/sdk.override.uischema" "!../generated" "../*.csproj" "../package.json" "!../dialogs/imported" -o $SCHEMA_FILE

Try these steps and let me know if this quick work around works for you.

I will give this a try. My version is @microsoft/botframework-cli/4.14.1 win32-x64 node-v14.17.5.

After attempting PowerShell fix. The error message I received was as follows:

Closing this issue as similar one is posted here. https://github.com/microsoft/BotFramework-Composer/issues/8501

@piechk, let's continue this discussion in the issue link above. Also, please list the steps to reproduce the behavior.


Create Windows Installer Script

There should be an installation script for Windows users, that installs the following. If these are already in the correct version, skip the install. Otherwise, if older version is installed, uninstall and reinstall the correct version.

[ ] Virtualbox 5.0.20 (latest)
[ ] Virtualbox extension pack for latest VBox
[ ] Vagrant 1.8.1
[ ] Git Bash latest

Once all these are installed, run vagrant up from inside powershell (where the script is being executed) or Git Bash.
And finally open Git Bash and clearly print out that the user needs to run vagrant ssh from inside Git Bash (this command won't work from inside Windows cmd or powershell).

@waliahimanshu want to take this up?

okay I will sort this out.

Couple of questions

Power-shell 3.0/Chocolatey need .Net 4 or higher, do we assume this is already installed ?
Is it okay to assume above dependencies are only installed at c:\program files ? They could be installed anywhere else as well ?

For starters we cannot assume those, however depending upon the packaging/licencing restrictions we 1) We may trigger installations prompts for .NET
2) These could be any where depending upon the user's config, so we should check the %PATH% environment variable if we can get hold of the dependencies.

How is the progress so far on this issue?

I have the basic script to detect packages and install if required.
I am working on uninstalling the older version if installed, as i am testing this it sometimes triggers restart of user machine, also it gets tricky because any of the packages could be installed as msi or exe.

How about try to make the code with functions and then test each function separately so as to separate causation. For each function, it should do one thing very well but very limited so it is stable. Try to hard code for all the installed application for now. We make a more general one later. Just focus on the three or four installations.

I would suggest using chocolatey installed via an elevated batch file and then running the other package installs through chocolatey as it can already detect if packages are installed anywhere in the path and resolve conflicts. I could write an example if you are interested as I'm going to be doing something similar for my dotfiles repo.

@dragon788 sure, we could try that way. If you can write one, please discuss with @waliahimanshu and raise a PR. Thanks!

@dragon788  yes thanks i am using choclatey, will raise a PR soon.

@dragon788 would you like to join our slack channel to chat with existing collaborators in real time? We have more resources there stored.

You guys should check out Boxstarter, it can do all this in a single URL, its amazing.

@dragon788 great tip! That might just do our job.


SendMessage function should be renamed

Looking at https://github.com/RogueException/Discord.Net/blob/cf3aa40c8ab110ba8d425b1e2dbd53007cf79dba/src/Discord.Net/Models/Channel.cs#L356 and the helpful guys on the discord api channel. I was running into the issue where a message would not be sent properly before disconnecting. The reason being, this should be renamed to EnqueueMessage as that's what it does. It does not actually fully send and complete the message with this implementation. Only enqueues it.

0.9 isn't being worked on atm.

0.9 won't be ever updated due RC of 1.0. There it is SendMessageAsync and waits until the message has been sent.

Alright, good to know. Closing this now =]

This will not be changed for 1.0, for the record. This is a frivolous change. When you send anything that doesn't go directly from you to something else, it will almost always go in a queue, whether that's a mailbox in an office/outside your house, or anywhere else. It's still being sent.
The only reason for it to sit in the queue would be ratelimits. Ergo, not worth the clarification.


Add query support to object storage.

[ ] Direct object query.
[ ] Simple mechanics of constructing queries.

Queries in object-storage are a subset of mongodb queries.

not relevant


Migration of lambdas to provided.al2 runtime

Problem
The aws lambdas are configured to use the go1.x runtime, which will be deprecated on 2023-12-31.
Proposed solution
Migrate to the provided.al2 runtime. See details here.

Hi @kislerdm!
Thanks for raising this, on the back of this I have raised PR #89 to resolve this issue. Thanks!


Bug: Incorrect sampling from a multivariate Gaussian

Summary:
There is a small bug in the Cholesky sampling routine in stan/src/stan/mcmc/hmc/hamiltonians/dense_e_metric.hpp.
Bug noticed by user fehiepsi on the discourse
Description:
Line 61 of the above file reads
  z.p = z.inv_e_metric_.llt().matrixL().solve(u);

It should say
z.p = z.inv_e_metric_.llt().matrixU().solve(u);

If we write z.inv_e_metric as the matrix A, then z.inv_e_metric.llt() performs the Cholesky decomposition A = LL^T. The next part of the call constructs z.p = L^{-1}u, where u~N(0,I). The covariance matrix of z.p is E(z.p z.p^T) = L^{-1}E(uu^T)L^{-T} = (L^TL)^{-1}. This is not A^{-1}, so the code is wrong.
In Eigen, the matrixU() routine returns the upper triangular matrix L^T.
Current Version:
v2.18.0

Fixed long ago.


use lombok at android studio 3.0 stable and gradle 3.0.0

i config these:
dependencies{
    compile 'org.projectlombok:lombok:1.16.18'
    annotationProcessor "org.projectlombok:lombok:1.16.18"
}

IDE: android studio 3.0 stable
Gradle version: 3.0.0
JDK8, Windows10 pro
so I can use debug ,but can't release apk.
`
Warning: lombok.ConfigurationKeys$1: can't find superclass or interface lombok.core.configuration.ConfigurationKey
Warning: lombok.delombok.ant.Tasks$Delombok: can't find superclass or interface org.apache.tools.ant.Task
Warning: lombok.javac.apt.Processor: can't find superclass or interface javax.annotation.processing.AbstractProcessor
Warning: lombok.launch.AnnotationProcessorHider$AnnotationProcessor: can't find superclass or interface javax.annotation.processing.AbstractProcessor
Warning: lombok.launch.AnnotationProcessorHider$AstModificationNotifier: can't find superclass or interface org.mapstruct.ap.spi.AstModifyingAnnotationProcessor
Warning: lombok.launch.AnnotationProcessorHider$ClaimingProcessor: can't find superclass or interface javax.annotation.processing.AbstractProcessor
Warning: lombok.launch.PatchFixesHider$ExtensionMethod: can't find referenced class org.eclipse.jdt.internal.compiler.lookup.TypeBinding
`
more than 700+ this warning
and i have a  question: I use android studio, why need eclipse jars?
Warning: lombok.launch.PatchFixesHider$ExtensionMethod: can't find referenced class org.eclipse.jdt.internal.compiler.lookup.TypeBinding

First of all, you don't need eclipse jars, nor the ant task.
Do you have any ideas what generates these warnings? A am not a Gradle export, but possibly, using compileOnly instead of compile helps?

@rspilker thanks,let me try today.

Did you try?

I'm also receiving this error with Android Studio 3.0 and gradle 3.0
Error:Execution failed for task ':app:javaPreCompileDebug'.
> Annotation processors must be explicitly declared now.  The following dependencies on the compile classpath are found to contain annotation processor.  Please add them to the annotationProcessor configuration.
    - lombok-1.16.18.jar (org.projectlombok:lombok:1.16.18)
  Alternatively, set android.defaultConfig.javaCompileOptions.annotationProcessorOptions.includeCompileClasspath = true to continue with previous behavior.  Note that this option is deprecated and will be removed in the future.
  See https://developer.android.com/r/tools/annotation-processor-error-message.html for more details.

Any feedback?

I can confirm that using compileOnly instead of
compile fixed the build for me.


Resumable jobs

During the course of running a job intermediate output is written to Zarr files. If a job is interrupted it could be resumed by continuing from the point at which it was stopped.
Cubed Array objects can be pickled, so it is already possible to reload them (and the underlying Plan object containing the DAG) as long as they have been saved first.
To detect where in the DAG the resume from, we can skip any intermediate Zarr files that have all of their chunks written. The check we need to do is nchunks_initialized == nchunks. (Since we specify that write_empty_chunks is True we know that every chunk will be written out, even if it composed of empty fill values.)
In the future it might be possible to resume at the level of individual chunks, but for now starting at the level of a Zarr array (and rewriting any chunks that have already been written) is sufficient.
This depends on #10 for testing - we can use it to see how many tasks actually ran, to check that earlier arrays were not re-written after resuming a partially completed job.

Fixed in c66edff38748542ce69623088ff0bee8231a0a3f


fix(api, controller): deprecate invalid capacity request

Signed-off-by: Akhil Mohan<EMAIL_ADDRESS>Why is this PR required? What issue does it fix?:
The InvalidCapacityRequest phase was a wrong addititon into status.phase of BlockDeviceClaim. But invalid capacity can only be a reason for the BDC to remain in Pending state. This also guarantees that, even if invalid capacity is given after editing the capacity to a correct value, the BDC can get Bound.
What this PR does?:
Deprecate the InvalidCapacityRequest phase from block device claim. The phase will be moved to Pending and invalid capacity can only be a reason for BDC remaining in Pending state. Exisiting BDCs with the phase will be changed to Pending.
Does this PR require any upgrade changes?:
No
If the changes in this PR are manually verified, list down the scenarios covered::

Create NDM Operator with 0.6.0 image. Create a BDC with invalid capacity request. The BDC will be in InvalidCapacity phase. Update the image with changes in this PR. The BDC phase will change to Pending. Editing the capacity to a correct value, gets the BDC to a Bound state.

Any additional information for your reviewer? :
This is actually part of cleanup of BDC api.
Checklist:

[ ] Fixes #
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[x] Has the change log section been updated?
[x] Commit has unit tests
[ ] Commit has integration tests
[x] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #443 into master will decrease coverage by 0.04%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #443      +/-   ##
==========================================
- Coverage   43.63%   43.59%   -0.05%
==========================================
  Files          61       61
  Lines        2947     2952       +5
==========================================
+ Hits         1286     1287       +1
- Misses       1559     1563       +4
  Partials      102      102

Impacted Files
Coverage Δ

...er/blockdeviceclaim/blockdeviceclaim_controller.go
40.11% <33.33%> (-0.61%)
: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 0cb8eb0...0ea4d84. Read the comment docs.


feat: include formatted sql on DatabaseError for improved debugging

What?
Adds an optional sql field to the DatabaseError which gets populated with the formatted sql statement in execute() if a database error is encountered (not errors rising from the postJSON function).
Why?
Today while writing an application using this driver, I ran into syntax error at position XXXX on a pretty big generated SQL query with user provided values (?). Debugging this in my code editor alone was quite tough, so I decided to open up DataGrip and pasted my generated query into its console for help. No luck. Syntax errors everywhere due to all the placeholder question marks. As a last resort, I dug into my node_modules folder and added console.log(sql) into execute() and got the full query that way. Pasted it into DataGrip, and bingo, it showed me exactly where the error was.
Point is, that was way more difficult than it needed to be. In that situation it would have been really awesome to just console.log(error.sql), or just a more general debug log option (future PR perhaps?)
Added a test for it as well so should be ready to merge if maintainers feel it's an appropriate addition.

Thanks for the pull request with all of these details!
Including replacement argument values in error messages can leak personally identifiable info, passwords, tokens, etc. into logs. They can also appear in the user-facing app itself if the error message received from the server is displayed without modification.
Another way to do this for debugging is to wrap the format function with logging behavior.
import { connect, format } from '@planetscale/database'

function debugFormat(query, values)
  const sql = format(query, values)
  console.log(sql)
  return sql
}

const config = {
  format: debugFormat,
  host: '<host>',
  username: '<user>',
  password: '<password>'
}

const conn = connect(config)
const results = await conn.execute('select 1 from dual where 1=?', [1])
console.log(results)


RequestHandler bug

I found a bug setting a Collector.RequestHandler func after a collector is initialized.
Setting Collector.RequestHandler, requires to execute c.backend.Client.CheckRedirect=c.checkRedirectFunc(). As c.backend is not accessible outside colly package, i will suggest to introduce a breaking change (might require version update according to golang/mod best practices) by renaming Collector.RedirectHandler to Collector.redirectHandler.
// SetRedirectHandler instructs the Collector to allow multiple downloads of the same URL
func (c *Collector) SetRedirectHandler(f func(req *http.Request, via []*http.Request) error) {
	c.redirectHandler = f
	c.backend.Client.CheckRedirect = c.checkRedirectFunc()
}

I can make a PR to address the issue. @asciimoo any thoughts?

I'm not sure if I understand the problem. c.backend.Client.CheckRedirect doesn't need to be reassigned if the c.RedirectHandlerchanges because c.RedirectHandler is executed in the function returned by c.checkRedirectFunc() (https://github.com/gocolly/colly/blob/master/colly.go#L1133).
Could you provide a testcase which reproduces the bug?

Here @asciimoo!

@llonchj you're right again, my pointer magic doesn't work here. Your solution seems to be our best option. Could you send me a PR with the changes?

Ready @asciimoo


Unify session backups and save files

Users have found the different concepts of session backups and save files difficult to understand. We should unify and simplify this. One option is to have the backup be a dot or tilde file alongside the normal file. This would be similar to emacs, Word, Netbeans, IPython, etc. We should do a comparison of how these other editors work before settling on a spec.

ipython has a good system:

auto save every minute to the regular file name.
when user issues save command, save an extra copy into a checkpoint file.

location of checkpoint could be a dot file, added .bak suffix, or (like ipython) a subdir named "checkpoints".

davide convinced me that ipython's is not expected behavior, tabled it.

I actually lost work with ipython when I accidentally deleted large amounts of code, and then the result was auto-saved and auto-checkpointed. I would gladly dedicate a gigabyte or two to be able to autosave without overwriting.
Variation: have a special git repository in ./beaker and auto-commit there every 30 seconds.