typeToString discrepancy?

TypeScript Version:
1.8.9
Code
With the following function
function foo(a) {
  return a + 'hello';
}

I'd expect that typeChecker.typeToString of foo's type should yield (a: string) => string.
Instead, it returns (a: any) => string.
Is this an issue of typeToString, or is the underlying Type object really marks a as any?
If it's the former, how can I walk the Type object to generate the right signature? A quick glance shows that a procedure type is "anonymous", and holds an opaque reference of target and mapper, which doesn't shed light on how to traverse the type objects. Is there a guide somewhere about the types?
I'm trying to generate the type signature for run time contract checking, so I need an accurate representation of the resolved type info.

This is actually by design - a implicitly gets the type any at that position. We don't do inference based on how you end up using your parameters.

And even at runtime, a isn't implicitly a string, because lots of other values could easily be coerced into a a string and provide no runtime issue:
function foo(a) {
  return a + 'hello';
}

console.log(foo(true));
console.log(foo(5));
console.log(foo(undefined));
console.log(foo(null));
console.log(foo({}));
console.log(foo(/foo/));
console.log(foo(['foo', 'bar']));

All these produce valid results (a string) without throwing.

And even at runtime, a isn't implicitly a string

Indeed. It is implicitly an any. If you want such unsafe cases to be an error turn on --noImplicitAny as @DanielRosenwasser pointed out. Then you can see the error and either add :any (to tell the next dev that its okay, I want it to be an any) or annotate with :string (which is what you want) :rose:

@kitsonk - not sure what you mean. JS runtime isn't exactly type sound, which provides the motivation for creating TypeScript in the first place, no?
@DanielRosenwasser & @basarat - thanks will give --noImplicitAny a try. I originally thought TypeScript's type inference is like OCaml. Should I instead think of it as a local inference system (i.e. all functions should be annotated) - instead?

@yinso it is somewhat closer to that. We have the idea of inferential typing and contextual typing. There are certain contexts in which we can figure out the types that an expression will flow to.
For instance, with
[1,2,3,4].map(x => x)

TypeScript can figure out that the type of x is number because it knows that you're calling map on a number[]. That's called contextual typing.

@yinso of course it isn't type safe, but by omitting any type annotation TypeScript has to assume the worse.  Mostly TypeScript without type annotations is just JavaScript and the compiler was offering up what it could given the context.
To further Daniel's explanation even then, TypeScript doesn't do that without some indication of how to extract those types out of the context.  From lib.d.ts:
interface Array<T> {
    map<U>(callbackfn: (value: T, index: number, array: T[]) => U, thisArg?: any): U[];
}

So it infers the type of number[] which is then what it passes at number to value on the callback via the use of generics.  That means any callback function could have its types narrowed, depending on where and how it is used.  For example:
function cb1(value, index, array) { // no context, so `any` is assumed
    return value; // return considered `any` because no context
}

function cb2(value: string, index: number, array: string[]) { // everything typed
    return value; // return type inferred to be string;
}

[ 1, 2, 3 ].map(function (value, index, array) { // context, so value is number, etc...
    return value;
});

[ 1, 2, 3 ].map(cb1); // Works fine
[ 1, 2, 3 ].map(cb2); // Error, incompatible signatures

@DanielRosenwasser - thanks for the info on contextual typing. I will do more research on typescript's capability.
@kitsonk - thanks for the explanation and example. My take away is that typescript's design goal is to be compatible with Javascript (i.e. a proper superset), so it needs to be compatible with JS's runtime behavior when types are unspecified.

so it needs to be compatible with JS's runtime behavior when types are unspecified

Or can't be contextually deduced. 😄


Error mounting s3fs bucket

Summary
Unable to mount rexray/s3fs volume to docker container
Bug Reports
I am able to install the Docker plugin successfully and successfully create volumes. However, when I try to mount the volume to a container using docker run -it --volume-driver=rexray/s3fs -v myVol:/test busybox, I get the following error message:
C:\Program Files\Docker Toolbox\docker.exe: Error response from daemon: error while mounting volume '/mnt/sda1/var/lib/docker/plugins/72070f05ca2941b6ed377bfff1ab116acd4cfd7410a98a01510a47c841517e4f/rootfs': VolumeDriver.Mount: docker-legacy: Mount: myVol: failed: error mounting s3fs bucket.
time="2018-03-07T15:28:25-06:00" level=error msg="error waiting for container: context canceled"

Version
docker plugin: rexray/s3fs:0.11.2
$ docker info
Containers: 4
 Running: 1
 Paused: 0
 Stopped: 3
Images: 4
Server Version: 17.12.1-ce
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 17
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9b55aab90508bd389d7654c4baf173a981477d55
runc version: 9f9c96235cc97674e935002fc3d78361b696a69e
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.4.119-boot2docker
Operating System: Boot2Docker 17.12.1-ce (TCL 8.2.1); HEAD : 42357fc - Wed Feb 28 17:52:00 UTC 2018
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.65GiB
Name: default
ID: SKQJ:CIBW:25U2:SV2S:MIJG:IGM2:DXH3:5SVM:LPJO:UNC4:YSVE:MSVD
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 33
 Goroutines: 48
 System Time: 2018-03-07T21:31:23.029681921Z
 EventsListeners: 0
HTTP Proxy: (removed)
HTTPS Proxy: (removed)
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

$ docker plugin inspect rexray/s3fs
[
    {
        "Config": {
            "Args": {
                "Description": "",
                "Name": "",
                "Settable": null,
                "Value": null
            },
            "Description": "REX-Ray FUSE Driver for Amazon Simple Storage Service (S3FS)",
            "DockerVersion": "18.02.0-ce",
            "Documentation": "https://github.com/thecodeteam/rexray/.docker/plugins/s3fs",
            "Entrypoint": [
                "/rexray.sh",
                "rexray",
                "start",
                "-f",
                "--nopid"
            ],
            "Env": [
                {
                    "Description": "",
                    "Name": "REXRAY_LOGLEVEL",
                    "Settable": [
                        "value"
                    ],
                    "Value": "warn"
                },
                {
                    "Description": "",
                    "Name": "LIBSTORAGE_INTEGRATION_VOLUME_OPERATIONS_MOUNT_ROOTPATH",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "LINUX_VOLUME_ROOTPATH",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "LINUX_VOLUME_FILEMODE",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "HTTP_PROXY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_ENDPOINT",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_ACCESSKEY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_DISABLEPATHSTYLE",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_MAXRETRIES",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_OPTIONS",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_REGION",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "S3FS_SECRETKEY",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "",
                    "Name": "CSI_ENDPOINT",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "The name of the CSI plug-in used by the CSI module.",
                    "Name": "X_CSI_DRIVER",
                    "Settable": [
                        "value"
                    ],
                    "Value": ""
                },
                {
                    "Description": "A flag that disables the CSI to libStorage bridge.",
                    "Name": "X_CSI_NATIVE",
                    "Settable": [
                        "value"
                    ],
                    "Value": "false"
                }
            ],
            "Interface": {
                "Socket": "rexray.sock",
                "Types": [
                    "docker.volumedriver/1.0"
                ]
            },
            "IpcHost": false,
            "Linux": {
                "AllowAllDevices": true,
                "Capabilities": [
                    "CAP_SYS_ADMIN"
                ],
                "Devices": null
            },
            "Mounts": [
                {
                    "Description": "",
                    "Destination": "/dev",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/dev",
                    "Type": "bind"
                }
            ],
            "Network": {
                "Type": "host"
            },
            "PidHost": false,
            "PropagatedMount": "/var/lib/rexray",
            "User": {},
            "WorkDir": "",
            "rootfs": {
                "diff_ids": [
                    "sha256:eebe6ffed8f4c85b884ec7c227cff7ed9a9c189f8d28949aa20c395dd121869f"
                ],
                "type": "layers"
            }
        },
        "Enabled": true,
        "Id": "72070f05ca2941b6ed377bfff1ab116acd4cfd7410a98a01510a47c841517e4f",
        "Name": "rexray/s3fs:latest",
        "PluginReference": "docker.io/rexray/s3fs:latest",
        "Settings": {
            "Args": [],
            "Devices": [],
            "Env": [
                "REXRAY_LOGLEVEL=warn",
                "LIBSTORAGE_INTEGRATION_VOLUME_OPERATIONS_MOUNT_ROOTPATH=",
                "LINUX_VOLUME_ROOTPATH=",
                "LINUX_VOLUME_FILEMODE=",
                "HTTP_PROXY=",
                "S3FS_ENDPOINT=(removed)",
                "S3FS_ACCESSKEY=(removed)",
                "S3FS_DISABLEPATHSTYLE=",
                "S3FS_MAXRETRIES=",
                "S3FS_OPTIONS=url=(removed)",
                "S3FS_REGION=",
                "S3FS_SECRETKEY=(removed)",
                "CSI_ENDPOINT=",
                "X_CSI_DRIVER=",
                "X_CSI_NATIVE=false"
            ],
            "Mounts": [
                {
                    "Description": "",
                    "Destination": "/dev",
                    "Name": "",
                    "Options": [
                        "rbind"
                    ],
                    "Settable": null,
                    "Source": "/dev",
                    "Type": "bind"
                }
            ]
        }
    }
]

Expected Behavior
I should be able to mount a an s3fs volume to a Docker container.
Actual Behavior
I receive an error when trying to mount the volume.

Hello @elainaRenee,
Can you try the 0.11.1 s3fs plugin and let us know if that works? We have been tracking this as a possible problem in the 0.11.2 release.
Thank you

I just ran the same command again, and it seemed as though the mounting was successful. However, when I tried to write to the volume, I did not see the file appear in s3 storage. When I ran the command again a third time, I got the same error message as the original report (error mounting s3 bucket).

Yes, I think the OS is most likely the issue

@elainaRenee
I'm also having troubles with minio & docker plugin.
Can you provide the plugin install for minio if this is working for you / your coworkers?

@setiseta Check the following issue
https://github.com/kontena/kontena/issues/3083

Have tried running with 0.11.3 - no luck (same response as in title: VolumeDriver.Mount: docker-legacy: Mount failed: error mounting s3fs bucket.). But with 0.11.1 works. It really should be bug I guess.

Seems like I also have this issue
docker: Error response from daemon: error while mounting volume '': VolumeDriver.Mount: docker-legacy: Mount: swarmx-proxy-certs: failed: error mounting s3fs bucket.

While docker volume ls gives:
DRIVER               VOLUME NAME
rexray/s3fs:latest   swarmx-proxy-certs
rexray/s3fs:latest   swarmx-proxy-letsencrypt
...

And docker info output is:
Containers: 2
 Running: 1
 Paused: 0
 Stopped: 1
Images: 4
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: xfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: active
 NodeID: 4s9d7tpq6tv3pw4d5ppyoqggu
 Is Manager: true
 ClusterID: 8c6tv3smnm8kevt7nyf9uddco
 Managers: 3
 Nodes: 3
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 10
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Autolock Managers: false
 Root Rotation In Progress: false
 Node Address: <IP here>
 Manager Addresses:
   <Swarm IPs here>
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-862.14.4.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.796GiB
Name: <Name here>
ID: <ID here>
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

@kyberorg if you are using userdata like me to install it you cannot use IAM roles to mount it. You need to define access and secret keys

@shamsalmon,I am quite new to Amazon S3. Please explain what is userdata.

When you install s3fs in your bash script do this:
docker plugin install rexray/s3fs:latest S3FS_REGION=${aws_region} S3FS_OPTIONS="allow_other,iam_role=auto,umask=000" --grant-all-permissions

@shamsalmon I am second to @kyberorg question and a little confused
I do use IAM to install the plugin I use secret key defined there

I am getting the same error and downgrading to 0.11.1 fixes the issue.

I encountered this issue now. It was working yesterday. What can be the reason? I'm using the latest version.

After a ton of searching to resolve this same problem this worked for me as well.
docker plugin install rexray/s3fs:latest S3FS_REGION=${aws_region} S3FS_OPTIONS="allow_other,iam_role=auto,umask=000" --grant-all-permissions

For me work well with minio only this (combination on options)
docker plugin install rexray/s3fs \
    --grant-all-permissions \
    S3FS_ACCESSKEY=minioaccesskey \
    S3FS_SECRETKEY=miniosecretkey \
    S3FS_ENDPOINT=http://<IP_ADDRESS>:9000 \
    S3FS_OPTIONS="umask=000,allow_other,use_path_request_style,nonempty,url=http://<IP_ADDRESS>:9000"

is s3fs-fuse manidatory for rexray plugin?


Modalai v1.12.3 testing

Describe problem solved by this pull request
This MR adds the following features / options:

ModalAI SITL target
Params to reduce the number of arming checks (default behavior unchanged).
ModalAI ESC feedback logging

My preference is not to squash commits, to prevent future merge issues.

Codecov Report

:exclamation: No coverage uploaded for pull request base (modalai-1.12-dev@36460bb). Click here to learn what that means.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##             modalai-1.12-dev      #17   +/-   ##
===================================================
  Coverage                    ?   51.86%
===================================================
  Files                       ?      784
  Lines                       ?    60161
  Branches                    ?        0
===================================================
  Hits                        ?    31200
  Misses                      ?    28961
  Partials                    ?        0

Flag
Coverage Δ

mavsdk
37.24% <0.00%> (?)

unittests
32.51% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Delayed rendering

Hello.
Firstly, I would like to congratulate the team for their work.
I was able to solve my problem. In this case, context menu construction parameters are obtained from a database via AJAX calls. Once the information is available, I build a custom html (customHtml). After that, I make the attachment an id for each customHtml (this id is referring to some URLs that I should access after clicking on a context menu item). Through $ li access, I get the id of each element and identify the item that was selected.
I had to do something like:
Loop: {
For (let x of $ scope.menuOptions) {
If (x.link == parseInt ($ li [0] .firstChild.id)) {
$ Scope.srcPI = $ sce.trustAsResourceUrl (x.url);
Break loop;
}
}
}
However, I still have another problem that is related to context menu rendering.
As my data is obtained via AJAX the context-menu policy is invoked before the information is available. Investigating the source code of the library I noticed that it returns a function. I should be able to redo the policy from the instant my data was available.
I thought about using $ rootScope, $ broadcast, and $ scope. $ On to signal the arrival of the data. However, I still have no idea how to adapt the library code to do this.
Would you have any suggestions?
Thank you very much.

Is the context menu generated each time? If so you can just pre-load it instead of loading it when the user invokes the context menu. This way, when your context menu is invoked, it will already have the data.
Something like:
$scope.menuOptions = [];

$http.get(...).then(function(resp) {
  //... extract data from resp
  $scope.menuOptions = [
     //...AJAX data
   ];
});

Hello @josetaira . I'm trying to do something similar and even implemented a promisse:
$scope.rightClick = function (text, parent, index, idPanel){
$scope.buffer`` = angular.copy(text);
        let promisse = monitorService.getExternalLinks($scope.buffer.idVariavel).then(function (response) {
            return response.data;
        });
 $q.when(promisse).then(function (response) {
// $scope.menuOption = response.data --> others operations for mouting context menu
}
}

rightClick send info to the selected item to obtain the new data for $scope.menuOption.
However, the context-menu directive is invoked before the data is available in $scope.menuOption.
follow my html code:

...

I hope you can help me thank you.

Try this:
$scope.rightClick = function (text, parent, index, idPanel){
$scope.buffer = angular.copy(text);
var deferred = $q.defer();
// This is the important part
$scope.menuOption = deferred.promise;
let promisse = monitorService.getExternalLinks($scope.buffer.idVariavel).then(function (response) {
            return response.data;
        });
$q.when(promisse).then(function (response) {
// Do something with response data
// After doing something with response data
  deferred.resolve(<the array of objects>);
}
}

This should delay the context menu until the deferred.resolve is executed.
Your HTML code isn't available so I'm not sure how to help you completely.

I'm sorry, I think gitHub omitted a few lines from my comment...
This is my HTML (simplified):

    [...]

I'll try what you mentioned.

Hello @josetaira! I solve my problem! : D
I did not know the $q.defer( ), only $q.all( ) and $q.when( ).
Here's my code:

$scope.rightClick = function (text, parent, index, idPanel) {
    var deferred = $q.defer();
    $scope.menuOptions = deferred.promise;
    let promisse = monitorService.getExternalLinks($scope.buffer.idVariavel).then(function (response) {
        return response.data;
    });
    $q.when(promisse).then(function (response) {
        //in this step, the object modeling is performed as expected by the context menu
        deferred.resolve(buildMenuContent());
    })
    function buildMenuContent() {
        let itemArray = [];
        for (let item of response) {
            customHtml = "" + item.nomeLink + "";
            itemArray.push({
                html: customHtml,
                text: item.nomeLink,
                click: function ($itemScope, $event, modelValue, text, $li) {
                    loop: {
                        for (let x of $scope.menuOptions.$$state.value) {

                            if (x.link === parseInt($li[0].firstChild.id)) {
                                if (item.isModal == false) {
                                    $window.open(x.url, '_blank');
                                }
                                else {
                                    $rootScope.$broadcast('changeUrl');
                                    $('#openModal').modal('show');
                                    $scope.externalUrl = $sce.trustAsResourceUrl(x.url);
                                }

                                break loop;
                            }
                        }
                    }
                },
                link: item.idLink,
                url: item.caminhoLink = item.enviaIdPainel ? item.caminhoLink + panel.painelUsuario : item.caminhoLink
            });
        }
        return itemArray;
    }
}

This may be useful for other people who need to get the menu options via ajax calls.

Thank you very much.


Add encrypted streaming support for A/V files via Wowza

A ticket to pair with https://github.com/ucsdlib/encrypted-stream-name/issues/1

I've added PR as pair of https://github.com/ucsdlib/encrypted-stream-name/issues/1 to test the Wowza streaming support:
Enable Wowza streaming with JW Player:

config.wowza_enabled = true
Configure Wowza server url base:
config.wowza_baseurl = 'lib-streaming.ucsd.edu:1935/dams4-test/definst/'
Setting the environment key for encryption:
APPS_DHH_STREAMING_KEY


ci: use cachix auth token

Tokens are easier to rotate than signing keys

not using the nix-community cache


Let's use Yarn instead of NPM for installing dependencies

Lets us update to use Yarn package manager instead of Npm for installing electron dependencies while running prepare command

I've never heard about yarn, can you just describe whats the problem with npm and why you think yarn will work better?

https://yarnpkg.com/en/
This should answer your queries.
Let's just say, yarn is npm on steroids...

no reason to not support both.

I think so to, npm is the default package manager and I don't think there is the need to support yarn with this project


Cannot unsubscribe

I received this email and clicked on unsubscribe...

but it redirects me here

Just block it then

That email was quite a long time ago. I haven't been getting them anymore.

@icecream17, then maybe after clicking on the unsubscribe button, it got unsubscribed and redirected you to a page that didn't existed.


how to create incoming  webhooks programatically while integrating app to a channel

I have gone through incoming webhooks docs but still I am not able to understand on how to create incoming  webhooks programatically while integrating app to a channel.
The app is not distributed.
We need a solution on how to generate a webhook_url programatically when users integrates app to a channel and give it to user.
We need this programatically instead of app collabrators generating the webhooks from app settings as it is difficult  to generate webhooks for many channels manually.
Please help!

Hi @Mogadampalli-Jayanth, thanks fro asking the qusetion!

how to generate a webhook_url programatically when users integrates app to a channel

There is no way to generate an incoming webhook without any user actions. The only way to achieve your goal is to implement the Slack OAuth flow (=distributing app) with the incoming-webhook scope.
To learn how to implement the OAuth flow, please refer to https://slack.dev/bolt-js/concepts#authenticating-oauth for more details. Your app may want to post a message with link button as below. Check a Block Kit Builder example here

Also, if your goal is not generating an incoming webhook URL but enabling notifications to a specific channel, using chat.postMessage with bot token would be smoother. With this way, your app does not need to ask end-users to install the app again.
I hope this helps.

👋 Let us know if you need more help here! We will close this issue after waiting for your response for a while.

Thank you for the reply. Here, can you confirm few things:

If we implement OAuth flow, is it possible to generate incoming webhook everytime on adding the app to a new channel ?

Is OAuth flow called while adding an app to App Directory by org admins of a workspace  or is OAuth flow shown to every individual user when adding the app for their usage?

If OAuth flow is called for  every user while adding the app, then will the user be able to see the incoming webhook_urls in the json response after installation or are the urls received by app admins?

@Mogadampalli-Jayanth
Let me answer the follow-up questions as blow:

If we implement OAuth flow, is it possible to generate incoming webhook everytime on adding the app to a new channel ?

Just adding your app to a channel does not behave this way. Your app needs to ask an end-user to go through the OAuth flow.

Is OAuth flow called while adding an app to App Directory by org admins of a workspace or is OAuth flow shown to every individual user when adding the app for their usage?

As long as your org/workspace settings allow users to install apps, the OAuth flow can be available for all the users in the org/workspace. That being said, your app may need to send a message to inform how to complete the OAuth flow plus navigate them to /slack/install URL in web browser. Displaying a link button in modal / home tab may be useful too.

If OAuth flow is called for every user while adding the app, then will the user be able to see the incoming webhook_urls in the json response after installation or are the urls received by app admins?

The JSON response is not directly visible to the installing users. Your app is responsible to handle the JSON response and securely store the confidential URL information in database on behalf of the users.
If you've never implemented the bolt-js OAuth flow yet, I would recommend checking the behavior on your own first. Perhaps, it behaves a bit differently from the one that you currently expect. Refer to the following resources to learn how to implement it:

https://slack.dev/bolt-js/concepts#authenticating-oauth
https://github.com/slackapi/bolt-js/blob/%40slack/bolt%403.10.0/examples/oauth/app.js

I hope this helps! It seems that I don't have anything further that I can suggest for you at this moment. Would you mind closing this issue?

Thank you for the quick response. I will go through the suggested docs and find a solution.


Custom Dates panel

Hi Shahab,
May I ask that can I add other event on dates panel?
For example, click certain date, it will do something.

I recently released DatePanel as a plugin.
Do you just need onClickListenre? or you want more features?
Please just tell me , I will add that possibility for you.

I recently released DatePanel as a plugin.
Do you just need onClickListenre? or you want more features?
Please just tell me , I will add that possibility for you.

Because when I click date, it will direct to specific date.
Now I would like to click blue block of date and it will be removed.

Because when I click date, it will direct to specific date.
Now I would like to click blue block of date and it will be removed.

I will add a property called onClickDate to the DatePanel plugin, then you can define a listener for it, when you click on any of the dates that listener will run and give you the date clicked, then you can filter that specific date.

I will add a property called onClickDate to the DatePanel plugin, then you can define a listener for it, when you click on any of the dates that listener will run and give you the date clicked, then you can filter that specific date.

Thank you so much.

Thank you so much.

You're welcome, I'm working on it😉

You're welcome, I'm working on it😉

I think this is what you wanted.

I think this is what you wanted.

I think this is what you wanted.

Cool, it is, thank you.
But "x" still can remain there.

I think this is what you wanted.

Cool, it is, thank you.
But "x" still can remain there.

that is an optional feature.
You can easily return the x button by setting the removeButton prop to true , or you can delete that line.

that is an optional feature.
You can easily return the x button by setting the removeButton prop to true , or you can delete that line.

console.log(value)

It seems the array of dates didn't sorting.

console.log(value)

It seems the array of dates didn't sorting.

In early versions, datepicker sorted the selected dates by default. But I noticed that sorting dates confuses the amount of dates selected by the user.
For example, if you want to prioritize user-selected dates, sorting the dates will make it impossible for you.
That's why I eliminated this possibility. But if you want the dates to be displayed in order, you can easily sort them like this :
setValue(value.sort((a, b) => a - b))

I will update the previous codesandbox for you to see the result.

In early versions, datepicker sorted the selected dates by default. But I noticed that sorting dates confuses the amount of dates selected by the user.
For example, if you want to prioritize user-selected dates, sorting the dates will make it impossible for you.
That's why I eliminated this possibility. But if you want the dates to be displayed in order, you can easily sort them like this :
setValue(value.sort((a, b) => a - b))

I will update the previous codesandbox for you to see the result.

Ok, I added a prop for sorting selected dates.

Ok, I added a prop for sorting selected dates.


Create CODEOWNERS

As of now, it's individual aliases in the CODEOWNERS file.  I have taken liberty to take current approvers from core repo, along with @seemk and @TomRoSystems and make them default code owner. We can start adding component level owners once the repo grows.
Please raise a comment here if someone doesn't want to be in list, or would like to add someone here, or want to be owner of only specific component (currently nginx & httpd ) within repo ?
Once we all agree, we can raise request to create approver group accordingly.  Also whether we need to have separate approvers and maintainers, or let one of the default approvers be responsible to merge the changes once we have sufficient approvals.
I can't find @seemk from Reviewers search list ( not sure why )  - Requesting him to please review, or if someone can add him as reviewer.

Sure, one idea would be to separate owners by directories. 🙂

Good point.  This was how my initial commit to this PR looked like ( https://github.com/open-telemetry/opentelemetry-cpp-contrib/pull/12/commits/20f55591232ff007715a3d17c81b2da3a58c80d5 )
We can discuss and revert back to something similar if all agree.

Sure, one idea would be to separate owners by directories. 🙂

Good point. This was how my initial commit to this PR looked like ( 20f5559 )
We can discuss and revert back to something similar if all agree.

Have switched to directory level owners now.

Sure, one idea would be to separate owners by directories. slightly_smiling_face

Good point. This was how my initial commit to this PR looked like ( 20f5559 )
We can discuss and revert back to something similar if all agree.

Have switched to directory level owners now.

Thanks! Btw safe to ignore the failing test. Reworked the tests in #10 a bit (also so it won't trigger on unrelated changes anymore)


labels for LiDAR data

Good afternoon,
I was curious if there will be a label feature added to the LiDAR sensor.  I know several other people have posted about this in issue 1751 and issue 516, and that individual has a version of carla with labels for LiDAR.  Is this something that the developers are looking to do in the future?  I am using Carla, carla-ros-bridge, and SLAM to create point clouds for DL training.  Thank you!

Future versions of CARLA will provide ground truth for point clouds. We will visit this topic during next releases. If this has a high priority for you and you have some bandwidth, perhaps you could contribute a solution...? Contributions are very appreciated!

@tiger-bug good news. This feature has been recently developed and will be part of 0.9.10, expected in a few days.

Thank you!!! That is awesome!

Closing the issue since this has entered in master in #3131!

Is it possible to save lidar data as .pcap file using carla?


not able to train on a registered problem

Hi,
(not sure this is a bug or a mistake on my side)
I am trying to create some problems and to register them.
As long as I created only one problem, it works fine.
Now that I am adding another problem (registered with another name - in the same python file as the problem above), it works for t2t-datagen, but not for t2t-train.
The error is:
ValueError: merged_vocab_custom_data_problem not in the supported set of problems:
Interestingly, I also get the following with --registry_help:
Problems: ['algorithmic_addition_binary40', 'algorithmic_addition_decimal40', 'algorithmic_identity_binary40', 'algorithmic_identity_decimal40', 'algorithmic_multiplication_binary40', 'algorithmic_multiplication_decimal40', 'algorithmic_reverse_binary40', 'algorithmic_reverse_decimal40', 'algorithmic_reverse_nlplike32_k', 'algorithmic_reverse_nlplike8_k', 'algorithmic_shift_decimal40', 'custom_data_problem', 'image_cifar10', 'image_cifar10_plain', 'image_cifar10_tune', 'image_fsns', 'image_imagenet', 'image_imagenet32', 'image_mnist', 'image_mnist_tune', 'image_ms_coco_characters', 'image_ms_coco_tokens32k', 'image_ms_coco_tokens8k', 'lm_ptb_10k', 'lm_ptb_characters', 'merged_vocab_custom_data_problem', 'setimes_mken_tokens_32k', 'wmt_encs_characters', 'wmt_encs_tokens_32k', 'wmt_ende_characters', 'wmt_ende_tokens_32k', 'wmt_ende_tokens_8k', 'wmt_enfr_characters', 'wmt_enfr_tokens_32k', 'wmt_enfr_tokens_8k', 'wmt_zhen_tokens_32k', 'wmt_zhen_tokens_8k']
You can see in bold both the problems - the custom_data_problem, which is working, and the merged_vocab_custom_data_problem, which works only for t2t-datagen (not for t2t-train)
Any idea why this is happening?
Thanks,
Mirko

My bet is that there's something wrong with your problem's hparams method. It should mutate the defaults passed in and return None. The error is misleading because of a bad way of checking whether a problem was registered in the new supported way or the old legacy way by try/excepting a ValueError. Will fix in the next release. Sorry about that. And do let me know if my hunch is correct.

Hi Ryan,
thanks - that may be it.
I am not changing the hparam method though - just inheriting it:
https://github.com/tensorflow/tensor2tensor/blob/master/tensor2tensor/data_generators/problem.py#L408
It seems to me this method is already mutating the defaults the way I need it, and it is returning None.
So, it seems to me it is already fdoing what you suggest to do above.
Am I missing something here?
Thanks,
Mirko

Hi @rsepassi ,
the problem was actually in feature_encoders - there was a ValueError there, and I suppose this was preventing the code to load the models (thus the 'problem not found' error).
The ValueError was caught thus it required some time on my side to find it.
Now I can register/use more than one problem.
Thanks for your help,
Mirko

Makes sense. I'll fix the error-swallowing in the next release.
On Tue, Aug 8, 2017 at 8:35 AM Mirko Bronzi<EMAIL_ADDRESS>wrote:

Closed #208 https://github.com/tensorflow/tensor2tensor/issues/208.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensor2tensor/issues/208#event-1197467255,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABEGW3R8nax2pcX_VFGUOuzkU8Xhrk8fks5sWIAkgaJpZM4OuDS0
.

I'm encountering the same ValueError: languagemodel_test not in the supported set of problems: with a problem I defined. What was the solution to this?

Solved, it was a config issue

@ghego What was the config issue? I may be running into the same thing now.

Figured out the problem I was having: I need to be importing the class from my problem spec python file in __init__.py.


Allow ssh-audit init script to chsh root to use sudosh shell

Resolves #46

I believe this is not needed anymore because we are using usermod now


Move alpine package to community repos

@krallin this is just a reminder for me so i don't forget on the next release

Sure; thanks @danilobuerger. Does this mean Tini might move from the Alpine testing repo to another one? Let me know if I need to upgrade the README : ).
Cheers,

Yes exactly. The repository will change. However since the community repository is active by default, we will not have to specify it anymore. The command will then become:
apk add --update tini

The community repository was introduced with alpine 3.3, so on next release of tini we should leverage this.

Awesome; looking forward to it!
Cheers,


[BUG] @Accessors - breaks building object graph using reflection

Describe the bug
The new, experimental fluent API implemented using @Accessors breaks mapping tools that rely on reflection.
Dozer deep property mapping https://dozermapper.github.io/gitbook/documentation/deepmapping.html works as expected without @Accessors annotation. But adding @Accessors(chain = true) results in the following:
java.lang.NullPointerException: Cannot invoke "java.lang.reflect.Method.setAccessible(boolean)" because "method" is null
	at com.github.dozermapper.core.util.ReflectionUtils.invoke(ReflectionUtils.java:348)

To Reproduce
Classes
@Data
public class DummyA {
  private DummyB dumB;
}

@Data
public class DummyB {
  private String propB;
}

@Data
public class Dummy1 {
  private Dummy2 dum2;
}

@Data
@Accessors(chain = true)
public class Dummy2 {
  private String prop2;
}

Dozer mapping
<?xml version="1.0" encoding="UTF-8"?>
<mappings
	xmlns="http://dozermapper.github.io/schema/bean-mapping"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://dozermapper.github.io/schema/bean-mapping https://dozermapper.github.io/schema/bean-mapping.xsd">
	<mapping relationship-type="non-cumulative">
		<class-a>DummyA</class-a>
		<class-b>Dummy1</class-b>
    <field>
      dumB.propB
      dum2.prop2
    </field>

  </mapping>
</mappings>

Test
class DummyTest {
  @Test
  void test() {
    DummyB dummyB = new DummyB();
    dummyB.setPropB("B");
    DummyA dummyA = new DummyA();
    dummyA.setDumB(dummyB);
    Mapper mapper = DozerBeanMapperBuilder.create().withMappingFiles("dummyMapper.xml").build();
    Dummy1 dummy1 = mapper.map(dummyA, Dummy1.class);
  }
}

Expected behaviour
Deep property mapping using reflection is successful with chaining of getters and setters enabled using @Accessors(chain = true)
Version info (please complete the following information):

Lombok version - 1.18.18
Platform javac 15.0.1

Additional context
N/A

Can you please try that with a non-lombok example? Lombok does its job during compile time and it should not change runtime behaviour of reflection calls.

Without lombok, mapping with dozer(reflection) works ok.
With lombok, but without @Accessors(chain = true), mapping with dozer(reflection) works ok.
With lombok, with @Accessors(chain = true), I get the exception.


New UI idea

Hey all,
This is one night's worth of work (early days), but I thought I'd throw my hat in the ring and proffer a UI redesign that is less "Bootstrap-y". Let me know what you think; if interested, I can submit a PR for what I have so far.

# #

Nice! Looks great.
On 16 Nov 2017 08:19, "xFvl"<EMAIL_ADDRESS>wrote:

Hey all,
This is one night's worth of work (early days), but I thought I'd throw my
hat in the ring and proffer a UI redesign that is less "Bootstrap-y". Let
me know what you think; if wanted, I can submit a PR for what I have so far.
[image: screen shot 2017-11-16 at 00 13 14]
https://user-images.githubusercontent.com/29760774/32880763-a85d91d8-ca63-11e7-819d-073f908ac0fc.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nopara73/HiddenWallet/issues/91, or mute the thread
https://github.com/notifications/unsubscribe-auth/AYgLfZan_hsd0e9TIiNQcnIUcCuD5jEjks5s2_AugaJpZM4QgHI6
.

1. Dark vs Light Theme
This is great, I like it, and my girlfriend likes it a lot, too:) However I am uncomfortable with the dark colors and I deliberately chose the blue and white scheme, which is traditionally the colors of security companies for reason, since it represents calmness and serenity.
In contrast to dark colors, which gives the impression for the user he's doing something illegal, which is not the case, of course. Plus personally I would be more reassured if a light themed screenshot of HiddenWallet pops up on CNN, than a dark themed one. HiddenWallet is poised to become a widely used wallet and when that happens I don't want the dark theme to become a straw man, illustrating the point of regulators, politicians, bankers and other criminals.
As an idea: hello kitty themed wallet may be a smarter way to redesign it, not only, because it would be hilarious, but its joke aspect would offset the negative connotations and the feeling of guilt those are those are indoctrinated into us to come up every time when trying to preserve our privacy.
2. Bootstrap
Other than the notion that it is an npm package, where npm packages should generally be avoided by Bitcoin wallets to minimize security vulnerabilities, what's wrong with being "Bootstrap-y"?
3. Stability, Maintainability, Development Overhead
It'd like to also address the fundamental redesign of the front end. During the FOSS development, accepting a fundamental redesign from a new contributor is uncommon for reasons. Unfortunately most new contributors are not sticking around. Their reliability is impossible to judge at this point by the maintainer and when they fall out the work remains to the maintainer, and the problem is he's not familiar with the code base, therefore modifying it, fixing bugs would require magnitudes of more effort, than otherwise would. Furthermore, while I noted before the front end code does not use the best coding paradigms and concepts, I made sure the current GUI to be bulletproof, well tested and not result in surprises for the user. A redesign always opens a new can of worms (bugs).
4. How To Progress Further?
We could either start with smaller incremental improvements at first or you could maintain the GUI (a light themed one, please) in a new branch and see in a couple of months, if (1) it actually gets finished, (2) you are willing to maintain it.
Or as an alternative, if you wish, although it's not an easy job, you try to figure out a new feature, which will be needed for ZeroLink: a visualized transaction history with a visualized way of building Bitcoin transactions, something like this inserted illustration. This would incentivize the user to make well-educated decisions.

@xFvl if you would you like to come to slack, please send me your email and I'll send you an invite<EMAIL_ADDRESS>

All very good points, thank you.
I choose a dark theme partially because I think it looks cooler, but also because it's physically easier on the eyes, especially in low light (I really like, for example, the Jaxx wallet aesthetic). That said, a light theme is perfectly fine, too. The Hello Kitty idea is interesting...I think you could actually run with something playful like that but still keep it on the semi-professional side.
Bootstrap itself is perfectly fine as the framework, but it looks "canned" when not custom styled, which was my original issue. What I built in the screenshot still uses it, actually.
The maintainability makes perfect sense. I'm new to the whole FOSS game, so bear with me. I did add several npm packages -- gulp and associated packages for task running, CSS preprocessing, etc. -- and rearranged the frontend assets quite a bit for minifying/compilation purposes. This was mostly for future-proofing and readability, so as the app scales, it's easier to maintain. But, yes, not a conservative approach there, either.
Let me think about the visualized transaction history; I like that idea.

Let me think about the visualized transaction history; I like that idea.

Make sure you fully understand how Bitcoin transactions work. It's a really difficult mental shift, from addresses to scriptpubkeys to transactions to utxos. See Chapter 6 of Mastering Bitcoin.
In ZeroLink, the coin selection what covers this topic: https://github.com/nopara73/ZeroLink/#coin-selection
Also take a look at this issue: https://github.com/nopara73/ZeroLink/issues/40

There is a new version of the wallet, called Wallet Wasabi, that's a complete reimplementation of the wallet. GUI will be reimplemented in Avalonia (native .NET), not Electron (JavaScript).


[FLINK-24940] [docs] correct usage about how to create Hive catalog via Flink SQL CLI

What is the purpose of the change

As it's not supported to use yaml in SQL CLI, the documatation about how to create hive catalog in SQL CLI is out of date.
The pr is to correct the usage.

Brief change log

modify the hive_catalog.md

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving):  no
The serializers: no
The runtime per-record code paths (performance sensitive):no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper:  no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

@AHeise Please merge

@MartijnVisser Could you please help merge it ?

@luoyuxia Yes, let me rebase and squash commits to verify that it will still work and then I'll merge it. Apologies for the delay!

Build passed in https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=34343&view=results


Fix NPE: use ToolingAPI.SaveResult.class return type instead of null

Much appreciated! 👍
Mind if i ask a bit about your use case?


"Extract to method in class" in angular template not working correctly

Also see:
https://github.com/angular/vscode-ng-language-service/issues/533
https://github.com/microsoft/vscode-typescript-next/issues/18
Describe the bug
"Extract to method in class" ability doesn't seem to behave correctly on a inline template function call. In below
To Reproduce
see GIF for clear reproduction. the inline template is missing the function addChildElement and is listed correctly. Using the autosuggested 'extract method' call in context menu removes the whole template properly and swaps it with a templateURL one, with a weird function call.

Expected
A correctly named method in the class is generated and the template stays untouched.

Please include code to reproduce this in text format; we are not able to transcribe screenshots.


[FEATURE] : ADD hover animation for card component

Objective: Enhance the user experience of the card component by implementing a hover animation that provides visual feedback when users interact with the card.

Is your feature request related to a problem? Please describe.

The current card component lacks dynamic feedback, making it feel static and less engaging.
The hover animation should include subtle scaling or shadow effects to create a sense of depth.
The animation should be smooth and not distract from the overall usability of the component.

Describe the solution you'd like
Implementing this hover animation will improve the overall aesthetic of the card component and encourage user interaction.
Additional context
Hey @Vignesh025 Please assign me this Task with label "gssoc-ext", "hacktoberfest-accepted" and "level2"

can you assign me this issue?

Hey @samyak-aditya , someone else is currently assigned to the UI of the campgrounds page. I'll check if they're still working on it. If not, I'll assign it to you.

Hey @Vignesh025 Thanks for the update
Do let me know

Hey @samyak-aditya , sorry but someone else is already working on it. Feel free to explore the project and raise any other issues you'd like to work on!


Added handler for the nREPL 'info' message handler

This makes cider-doc and related functions work.

Hi, I'm very glad to be able to contribute!
As I told you on gitter, here's the PR that adds support for cider-doc in the embedded nREPL server. I tried not to mess up with the indentation style, but I see there's still a couple of whitespace-related changes. Please let me know if that is a problem!

This looks great!
Can you add a commit that adds your name to CONTRIBUTORS and acknowledge in the commit message that you've read and agreed to our Contributor's Licence Agreement? Instructions and details are in the README.

@nasser  Done!
I'll try to keep improving the nREPL support in my free time. Do you happen to know any documentation of the protocol API? So far I've been reverse engineering it by looking at the requests sent by cider but for anything more complicated than this it might be complicated.

@nasser Done!

Thanks!

I'll try to keep improving the nREPL support in my free time. Do you happen to know any documentation of the protocol API? So far I've been reverse engineering it by looking at the requests sent by cider but for anything more complicated than this it might be complicated.

The protocol is documented at nrepl.org but I used a lot of packet sniffing against cider to ensure that things were working correctly as well.


Fix: 🐛 scan large projects

Fix issues when scan large projects.

You've switched to Newtonsoft.Json but Snyk.Code.Library is still using System.Text.Json. Can we make a switch there too to be consistent and reduce our maintenance efforts in perspective?

Quick iteration, thank you and great job @aldanchenko 👍


Preserve generated assembly file on test errors

If a test case fails, I pretty much always end up re-running my compiler driver script to generate the assembly file. It would be helpful if test_compiler automatically stored the generated assembly file somewhere for the user to look at and debug after failed test cases.
I don't think having an option to generate the assembly file is part of the specification for the compiler driver in the book though. Maybe test_compiler needs a new argument to tell it what argument the compiler driver script uses to generate assembly?

The specification for the compiler driver suggests using -S to generate assembly but not assemble/link it. (This is a suggestion in Part I and a requirement in Part III.) I think it would be straightforward to add an option to test_compiler to have it just invoke the compiler again on any failed tests, this time with the -S option to preserve their assembly.

Added a --keep-asm-on-failure option that does this; let me know if you run into any issues with it!

This is great, thanks!


AVRO-2921: Type Fixes for avro.datafile

...and other small modules

Type hint and refactor avro.datafile
Type hint avro.test.mock_tether_parent
Type hint avro.timezones

Jira

[x] PR addresses and references AVRO-2921

Tests

[x] PR adds type checks

Commits

[x] Commits reference AVRO-2921
[x] Commits follow the guidelines from "How to write a good git commit message":

[x] Subject is separated from body by a blank line
[x] Subject is limited to 50 characters (not including Jira issue reference)
[x] Subject does not end with a period
[x] Subject uses the imperative mood ("add", not "adding")
[x] Body wraps at 72 characters
[x] Body explains "what" and "why", not "how"

Documentation
N/A

@RyanSkraba I appreciate someone looking at the work. If you want to read up, I think implementing __slots__ may be a potential game-changer for the Python implementation of avro.
They can massively reduce the memory footprint of objects and result in a speed-up, too. __slots__ are class property declarations that allow the interpreter to pre-allocate memory for the object. The trade-off is that classes with __slots__ can't have arbitrary properties and there are stricter inheritance rules.
I think implementing slots here makes sense because type hinting requires me to basically enumerate the properties anyway; however, let me know if you think the __slots__ thing is a bridge too far right now.


UX wise floating button is not needed on the HomeScreen

UX wise the floating button is not a good choice for going to templates.As according to guidelines the plus shaped floating button is not needed to add something in general.I would like to shift functionality of that button to navigation drawer (means shifting option of template to drawer itself) and remove that from home screen.(Remaining application and other floating buttons will be at their same location).
@batraabhishek please review my suggestions so that I can work on that.

FAB is used for primary action on a screen - which in our case is the to create a new template. I would suggest keeping it the way it is and not moving it to the navigation drawer and hiding the primary action.

As we are adding item to existing template not adding any template that's
why I suggested above thing. We are actually adding items inside template
not adding template itself so it would be good if we have FAB inside
template (which is already there).
Closed #4
https://github.com/BuildmLearn/BuildmLearn-Toolkit-Android/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/BuildmLearn/BuildmLearn-Toolkit-Android/issues/4#event-495847959
.

Hey @vjs3, on clicking FAB we are creating a new project based on existing template. Thus as @croozeus said, FAB is acting as primary action similar to creating a new mail fab in gmail app, and upload fab on youtube app.
Also moving it to Navigation Drawer, will make it less accessible to user. the aim is to create new project in one click.

Ok I got it.Thanks for your clarification :smile:


LevelX doesnot work-well

Dear Scott & Tiejun,
I am running LevelX & FileX with your demo API, demo_flilx_nand_flash.c.
Platform -> ARMR5 Comminication Processor
NAND   -> SPI NAND winbond 1G.
Driver   -> SPI NAND Driver is ported by myself.
The result looks like abnormal with LevelX.

Here is detailed information with your demo.

fx_media_format() is called firstly.

Because of no bad blocks, The routine is very simple.
Routine 1:
The Code Sample:

The log info:

Routine 2
The Code Sample:

The log info:

Routine3
The Code Sample:

The Log info:

SECTOR_WRITE -> lx_nand_flash_sector_wite()

Routine1:

The Log Info:

Routine2:

The log info:

As you seen, The Write Operation is failed. BUT I donot know the reason.
Pls give me some handle.
Thanks very much.
Best Regards
Joshua Wang

Hi Joshua, from your log info, we can see that the _lx_nand_flash_physical_page_allocate has failed to allocate a new page. You may check the value of nand_flash -> lx_nand_flash_free_pages when calling _lx_nand_flash_physical_page_allocate and see if it is zero. You may also check if your driver can read and write the spare bytes correctly.

Dear wencai,
It returned here with error.

If the rouitne is checked by yourself as my words, There is only reading spare area method, So I think The problem is have nothing with SPI ANND Drivers.
Thanks.
Best Regards
Joshua Wang

Hi Joshua, you may go through the lx_nand_flash_open function and see why lx_nand_flash_free_pages is zero. If lx_nand_flash_bad_blocks contains a large number, then check the driver_block_status_get function and verify if it returns correct block status. You may also check the values of lx_nand_flash_mapped_pages and lx_nand_flash_obsolete_pages. Checking variables lx_nand_flash_diagnostic_* in the LX_NAND_FLASH struct may also help you diagnosing the problem.

Dear wencai,
There is no bad block. As you seen, All return calue of river_block_status_get  is 0xFF.

Best Regards
Joshua Wang

Can you post all the variable values inside the nand_flash struct?

Dear wencai,

@ Ending of LX_NAND_FLASH_OPEN API
OR
@ Failure of WRITE BOOT Sector..

Pls help to confirm the scene, I will post all the information you mentioned.
Best Regards
Joshua Wang

Please post the variable states at the end of _lx_nand_flash_open function.

Best Regards
Joshua Wang

From your log, I see some abnormal values. For example, the lx_nand_flash_minimum_erase_count and lx_nand_flash_maximum_erase_count are quite large and the difference between min and max is large. It indicates that there may be issues in reading/writing the pages.
The lx_nand_flash_max_mapped_sector is quite large too. This indicates that invalid data may be returned by _extra_bytes_get. Please check your driver to see if it can access spare data correctly and make sure the extra data is stored in "user data" area of the spare area.
The non-zero values in lx_nand_flash_diagnostic_system_error(s), lx_nand_flash_diagnostic_erased_block, lx_nand_flash_diagnostic_re_erase_block and lx_nand_flash_diagnostic_mapping_invalid all show that there may be some data corruption in reading/writing the flash. My suggestion is to take the simulator as reference and check your driver and hardware, and make sure the written data can be read out correctly.

Dear wencai,
I will check it.
if some demo with real nand flash is ok, Pls  show us.
Thanks.
Best Regards
Joshua Wang

@wxp821217 we do not have demos using NAND flash available.

Hi @wxp821217 - any updates? Have you made any progress or have any questions?

I'll close this ticket for now but feel free to re-open.


refactor(api): increase calibration threshold value

Overview
Hardware testing found that the sensor threshold value actually needs to increase in order for the robot to accurately detect edges.

Closing in favor of https://github.com/Opentrons/opentrons/pull/12243


performCommand(), chat() methods

should be added within one of the next updates:
performCommand(String command)
chat(String message)
chat(MessageType type, String message)
MessageType (enum):
NORMAL,
WHISPHER,
SHOUT,
FRACTION,
ACTION

done


Move payload deserialisation out of handlers

This moves the deserialisation of payloads out of handlers and into the calling code (LspDispatcher).

I'm wondering whether BodyType should be called PayloadType. What do you reckon?

Ok - I'm going to change it then :grin:

Right, have renamed it and added a couple of tests :)
Providing CI checks pass, would you like me to add this work to your WIP branch?

Ok we're good to go :)


Blog for auto-instrumentation for java app

Blog for auto-instrumentation for java app

This looks pretty good to me. Any other comments @sunitakawane ?

Can you also put a screenshot with search traces screen.


[FEA] 0.4 Release ?

It's been awhile since dask-sql has done a release.  With the new committers on the team,  I was curious if you all would be interested in testing out dask-sql's release process
cc @rajagurunath @galipremsagar @charlesbluca
I suspect @rajagurunath would like to see #231 go in before any release

For sure, It's really a great idea, Lot of good work was added since the last release !!!. Please let me know if something needs to be done from my end. (And Apologies for being late).

I suspect @rajagurunath would like to see #231 go in before any release

For sure @quasiben, I have already started looking into this PR, Feeling somewhat less confident in the testing part, Happy to incorporate  Feedbacks/suggestions from @charlesbluca. May we will try to incorporate the rich/ textual features in upcoming releases.  (Actually planning to come up with UI Layer for dask-sql for different interfaces like browser (using streamlit), terminal (using rich), jupyter-lab plugins, a very small step towards that https://github.com/rajagurunath/dask-sql-workbench, happy to know everyone's thoughts on this :) ).

Something else I had been thinking about (but isn't pertinent with this release) is if we wanted to move to CalVer to match up with Dask/Distributed, since it seems like some of the work we're doing currently is bound to development in Dask.

I also like the CalVer idea !! 👍

With #231 merged in, I think we're in a pretty good place to do another release. @rajagurunath @quasiben how does a release in the next couple days sound?

Closing this now that 0.4.0 is out - note that we'll probably want to do a minor release once #294 or another solution for #297 is merged in


init

initialize all the stuff

The code itself looks fine. I am a bit worried that we are bringing too much stuff in; redux, thunks, and react router are great but maybe we should add them when they are needed. I'm worried this level of information overload will make it hard for those less familiar to know why these tools are useful.


Disable lazy loading of controllers

This branch is based on https://github.com/microsoft/vscode-jupyter/pull/11831
Review only the last comment

Codecov Report

Merging #11832 (688f461) into main (e93fd37) will decrease coverage by 0%.
The diff coverage is 64%.

:exclamation: Current head 688f461 differs from pull request most recent head 0086463. Consider uploading reports for the commit 0086463 to get more accurate results

@@          Coverage Diff           @@
##            main   #11832   +/-   ##
======================================
- Coverage     62%      62%   -1%
======================================
  Files        486      486
  Lines      34621    34667   +46
  Branches    5629     5638    +9
======================================
+ Hits       21774    21778    +4
- Misses     10782    10814   +32
- Partials    2065     2075   +10

Impacted Files
Coverage Δ

src/platform/interpreter/contracts.ts
100% <ø> (ø)

...rnels/raw/finder/localKernelSpecFinderBase.node.ts
78% <52%> (-5%)
:arrow_down:

.../raw/finder/localKnownPathKernelSpecFinder.node.ts
80% <66%> (-3%)
:arrow_down:

...lPythonAndRelatedNonPythonKernelSpecFinder.node.ts
75% <70%> (+<1%)
:arrow_up:

src/platform/api/pythonApi.ts
71% <77%> (+1%)
:arrow_up:

src/notebooks/controllers/controllerLoader.ts
92% <100%> (+<1%)
:arrow_up:

src/kernels/installer/productInstaller.node.ts
74% <0%> (-7%)
:arrow_down:

src/platform/common/cancellation.ts
62% <0%> (-6%)
:arrow_down:

.../standalone/survey/dataScienceSurveyBanner.node.ts
66% <0%> (-6%)
:arrow_down:

src/platform/common/process/baseDaemon.node.ts
50% <0%> (-4%)
:arrow_down:

... and 11 more

@DonJayamanne @IanMatthewHuff I have just merged the branch with main and retargeted it against main branch. The changes now are very minimal and considering we have already did a test run for this, IMHO we should merge it and have it released to Insiders users.


Add handling input events in web previewer

What does the pull request do?
Add handling input events in web previewer
What is the current behavior?
Server does not support input event handling
What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

The KeyEvent implementation seemed too hard to me
https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code/code_values

Also, I didn't understand how to do for text input

I added tests for the web previewer, now it probably need to add them to nuke

We now have tests for the web previewer


Fixed bug that failed to include certain abstract classes in schema

I'll add a reproducing test sometime tonight. Trying to change the schema for the autogenerated one right now.

Coverage decreased (-0.06%) to 84.394% when pulling bab0752eb70f1f69400f762c0697c1fe4f7df9fa on fix-bug-to-include-non-vertex-classes into 7042c3be086d1ee0d7a81f76a084a55d65d54984 on master.


Issue in home assistant logs - async_add_job

Home assistant log had the following error for smartrent
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:184
First occurred: 9:42:22 AM (10 occurrences)
Last logged: 9:42:36 AM
Detected that custom integration 'smartrent' calls async_add_job, which is deprecated and will be removed in Home Assistant 2025.4; Please review https://developers.home-assistant.io/blog/2024/03/13/deprecate_add_run_job for replacement options at custom_components/smartrent/init.py, line 54: hass.async_add_job(, please create a bug report at https://github.com/ZacheryThomas/homeassistant-smartrent/issues

Should be fixed when you download the latest release!
https://github.com/ZacheryThomas/homeassistant-smartrent/releases/tag/v0.4.6


definitions for angular-gettext v2.1.0

https://angular-gettext.rocketeer.be/

angular-gettext/angular-gettext.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/angular-gettext
http://bower.io/search/?q=angular-gettext
others?

[X] has a test file? (angular-gettext/angular-gettext-tests.ts or others)
[ ] pass the Travic-CI test?

Hi all, is this going to be merged soon? is it considered ready?

It is ready. At least I think so...

@dmandalidis @AkosLukacs oops, it merged. thanks mate!


k8s/reconciler: update/replace resources

Sometimes (for example in https://review.monogon.dev/c/monogon/+/2784) we need to update (or in cases of immutable fields) replace Monogon-managed resources to apply fixes. This issue is for non-version-critical fixes, separate from #272. The changes talked about in this issue can be applied at any time and are intended to just be applied as soon as the control plane node running the reconciler is upgraded.

Related to #280 as well


Error occurred when executing [ComfyUI-3D] Animate Anyone Sampler:  mat1 and mat2 shapes cannot be multiplied (2x1024 and 768x320)

File "/content/drive/MyDrive/ComfyUI/execution.py", line 152, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "/content/drive/MyDrive/ComfyUI/execution.py", line 82, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "/content/drive/MyDrive/ComfyUI/execution.py", line 75, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
File "/content/drive/MyDrive/ComfyUI/custom_nodes/ComfyUI-AnimateAnyone-Evolved/nodes.py", line 152, in animate_anyone
samples = diffuser(
File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/content/drive/MyDrive/ComfyUI/custom_nodes/ComfyUI-AnimateAnyone-Evolved/src/models/main_diffuser.py", line 440, in call
latents = self.denoise_loop(
File "/content/drive/MyDrive/ComfyUI/custom_nodes/ComfyUI-AnimateAnyone-Evolved/src/models/main_diffuser.py", line 315, in denoise_loop
self.reference_unet(
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1520, in _call_impl
return forward_call(*args, **kwargs)
File "/content/drive/MyDrive/ComfyUI/custom_nodes/ComfyUI-AnimateAnyone-Evolved/src/models/unet_2d_condition.py", line 1197, in forward
sample, res_samples = downsample_block(
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1520, in _call_impl
return forward_call(*args, **kwargs)
File "/content/drive/MyDrive/ComfyUI/custom_nodes/ComfyUI-AnimateAnyone-Evolved/src/models/unet_2d_blocks.py", line 657, in forward
hidden_states, ref_feature = attn(
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1520, in _call_impl
return forward_call(*args, **kwargs)
File "/content/drive/MyDrive/ComfyUI/custom_nodes/ComfyUI-AnimateAnyone-Evolved/src/models/transformer_2d.py", line 357, in forward
hidden_states = block(
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1520, in _call_impl
return forward_call(*args, **kwargs)
File "/content/drive/MyDrive/ComfyUI/custom_nodes/ComfyUI-AnimateAnyone-Evolved/src/models/mutual_self_attention.py", line 241, in hacked_basic_transformer_inner_forward
attn_output = self.attn2(
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1520, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/diffusers/models/attention_processor.py", line 527, in forward
return self.processor(
File "/usr/local/lib/python3.10/dist-packages/diffusers/models/attention_processor.py", line 1246, in call
key = attn.to_k(encoder_hidden_states, *args)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1520, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/diffusers/models/lora.py", line 430, in forward
out = super().forward(hidden_states)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/linear.py", line 116, in forward
return F.linear(input, self.weight, self.bias)

Use the right ClipVision

Use the right ClipVision #17

I followed the instruction linked, and placed the clip vision in the correct folder "ComfyUI\models\clip_vision\SD1.5" but still receive the same error message.


!): Fix "yfileswrap-obfuscated" version for gradle build.

In build.gradle file, "yfileswrap-obfuscated" version 6.0 is 404. Fix with the correct version 6.1.

I signed it!


Right Arrow, Up Arrow & Down Arrow Icons

Please add more arrow icons like right, up and down.

Thanks for pointing this out looks like I have missed out on these icons will update them

added in v2.0


Build failed : invalid source release: 17 (JVM)

I'm encountering this error when trying to build my app after upgrading Flutter:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':customer_io:compileReleaseJavaWithJavac'.
> error: invalid source release: 17

I suspect that it is caused by targeted jvm version specified in the build.gradle:
https://github.com/customerio/customerio-flutter/blob/e6862c9a6b145d7264cfea95e7977c6f805eff52/android/build.gradle#L38

JVM 17 is requirement for Gradle 8.
Does the answer here helps?

Ok my bad, I recently upgraded the whole project, and the build was successful locally but not on the CI pipeline. Turns out there's a pipeline action to set the Java version. I did and it solves the issue. I should've digged a little further before opening the issue, sorry for the inconvenience.


Fix Makefile errors that prevent builds on macOS

What's changed:
Remove unnecessary quotes from variable assignments, errant comments, and an unnecessary call to strip. I also inlined the variable detected_OS since it's only used in one place.
Why has this change been implemented:
Back in January 2023, some changes were made to Makefile to drop some flags that aren't available in macOS builds that were causing those builds to fail.
Unfortunately, these changes had a few small syntax issues that prevent the conditional checks for "Darwin" from ever being true. See commits 0e19696, d011eea, 0737d53.
Specifically, a trailing comment after a variable assignment with spaces before the comment character actually has the effect of adding those trailing spaces to the variable being assigned (detected_OS). The subsequent line attempts to strip these spaces, but inadvertently adds them back with another trailing comment. Further, the quotes around these assignments added in commit 0737d53 also end up verbatim in the variable's value. The consequence of this the comparison actually ends up comparing "Darwin"  with Darwin, so the check never succeeds and the wrong flags are used. You can confirm this by adding
echo .$(detected_OS).

to the all target and running make. You'll see the quotes and extra spaces between the dots when the echo command is written to the console (the quotes are eaten by the shell when echo is executed).
What (if any) actions must a user take after this change:
No user actions necessary. I tested these changes on macOS 14.4 and Ubuntu Linux 22.04.4 LTS

The quotes were added to facilitate WSL support, I'll give it a test on WSL and get back to you

I see. Maybe I was overzealous in my quote removal. I can revert those and limit the changes to just the Darwin test. - DavidOn Mar 15, 2024, at 6:48 AM, ReFil @.***> wrote:
The quotes were added to facilitate WSL support, I'll give it a test on WSL and get back to you
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Leave it as is for now and i will give it a test on wsl

Sorry it took me so long to test this! I can confirm it still builds on my WSL instance

Would you be able to tweak changelog.md to the PR title and link with the current date? Other than that it looks good to me :)

Sure thing. Thanks!

Thanks!


boto3 client with smart_open memory leak

Describe the bug
When use boto3 to read remote oss parquet file get memory leak.

Regression Issue

[ ] Select this option if this issue appears to be a regression.

Expected Behavior
No memory leak
Current Behavior
As the method be called many times, the memory leak happend.
Reproduction Steps
Run this script many times
self.client = boto3.client(
    "s3",
    aws_access_key_id=access_key_id,
    aws_secret_access_key=secret_access_key,
    endpoint_url=endpoint,
    config=Config(
        s3={"addressing_style": "virtual", "signature_version": "s3v4"}
        ),
)
with smart_open.open(
    f"s3://{bucket_name}/{file_path}",
    mode="rb",
    transport_params={"client": self.client},
) as f:
    parquet_file = pq.ParquetFile(f)
    ...

self.client.close()

Possible Solution
I guess may related to smart_open object not be closed
Additional Information/Context
no
SDK version used
boto3==1.34.54 botocore==1.34.54
Environment details (OS name and version, etc.)
centos

Thanks for reaching out. Can you please share your debug logs (with any sensitive info redacted) by adding boto3.set_stream_logger('') to your script to help with further investigation? And can you share any more details regarding the memory leak? If you're able to provide a memory profiling analysis that could be helpful as well. Otherwise if the issue here is with smart_open then you may want to consider opening an issue in that repository.

After added log(boto3.set_stream_logger("boto3", level=logging.DEBUG)), it shows nothing new log.
I have a class which will init new instance of boto3 client, and each call will raise the memory up.

def print_memory_used():
    import threading

    import psutil

    def monitor_memory():
        pid = os.getpid()
        process = psutil.Process(pid)

        while True:
            memory_info = process.memory_info()
            memory_usage_mb = memory_info.rss / (1024**2)  # MB
            logger.info(
                f"[Memory Monitor] Process ID: {pid}, Memory Usage: {memory_usage_mb:.2f} MB"  # noqa
            )
            time.sleep(1)

    memory_thread = threading.Thread(target=monitor_memory, daemon=True)
    memory_thread.start()


Add use of config-writing script to GCE envs

plus some other little bits I noticed along the way.
What is the problem that this PR is trying to fix?
The GCE and AWS infrastructures remain slightly inconsistent in how secret and non-secret configuration bits are ingested.
What approach did you choose and why?
I decided to use the same config writing script that the AWS infrastructures use, ported to rubby for arguably better UX and maintainability, since it is known to work.
How can you test this?
make plan in any GCE or AWS project to ensure stuff isn't busted.

Wow, I don't understand any of this, does anyone speak English on here, would really like to find people interested in my ideas......

Fyi I'm jay btw....


How to fix run time exception error

Hi,
I got RuntimeException error when trying to run php composer.phar install
Here's the complete log:
Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache handling the symfony-scripts event terminated with an exception

  [RuntimeException]
  An error occurred when executing the "'cache:clear --no-warmup'" command:
  Fatal error: Uncaught Symfony\Component\Config\Definition\Exception\Invalid
  ConfigurationException: The path "fos_user.from_email.address" cannot conta
  in an empty value, but got null. in /Users/raditaliem/Sites/tania/vendor/sy
  mfony/symfony/src/Symfony/Component/Config/Definition/VariableNode.php on l
  ine 88
  Symfony\Component\Config\Definition\Exception\InvalidConfigurationException
  : The path "fos_user.from_email.address" cannot contain an empty value, but
   got null. in /Users/raditaliem/Sites/tania/vendor/symfony/symfony/src/Symf
  ony/Component/Config/Definition/VariableNode.php on line 88
  Call Stack:
      0.9964   13970216   1. Symfony\Component\Debug\ErrorHandler->handleExce
  ption() /Users/raditaliem/Sites/tania/vendor/symfony/symfony/src/Symfony/Co
  mponent/Debug/ErrorHandler.php:0
  PHP Fatal error:  Uncaught Symfony\Component\Config\Definition\Exception\In
  validConfigurationException: The path "fos_user.from_email.address" cannot
  contain an empty value, but got null. in /Users/raditaliem/Sites/tania/vend
  or/symfony/symfony/src/Symfony/Component/Config/Definition/VariableNode.php
  :88
  Stack trace:
  #0 /Users/raditaliem/Sites/tania/vendor/symfony/symfony/src/Symfony/Compone
  nt/Config/Definition/BaseNode.php(303): Symfony\Component\Config\Definition
  \VariableNode->finalizeValue(NULL)
  #1 /Users/raditaliem/Sites/tania/vendor/symfony/symfony/src/Symfony/Compone
  nt/Config/Definition/ArrayNode.php(254): Symfony\Component\Config\Definitio
  n\BaseNode->finalize(NULL)
  #2 /Users/raditaliem/Sites/tania/vendor/symfony/symfony/src/Symfony/Compone
  nt/Config/Definition/BaseNode.php(303): Symfony\Component\Config\Definition
  \ArrayNode->finalizeValue(Array)
  #3 /Users/raditaliem/Sites/tania/vendor/symfony/symfony/src/Symfony/Compone
  nt/Config/Definition/ArrayNode.php(254): Symfony\Component\Config\Definitio
  n\BaseNode->finalize(Array)
  #4 in /Users/raditaliem/Sites/tania/vendor/symfony/symfony/src/Symfony/Comp
  onent/Config/Definition/VariableNode.php on line 88

Is it because of I didn't put anything in parameters.yml mailer? Please suggest some help

The path "fos_user.from_email.address" cannot contain an empty value, but got null.

It seems because the parameters.yml. You should fill it I guess.

Can you try using my parameters.yml?
parameters:
    database_host: yourdbhost
    database_port: null
    database_name: yourdbusername
    database_user: yourdbuser
    database_password: yourdbpassword
    mailer_transport: smtp
    mailer_host: <IP_ADDRESS>
    mailer_user: admin
    mailer_password: admin
    secret: yoursecretke

Try to put admin in the mailer settings.

was unsure how to fill that part, but hey it works!
also small suggestion to remind user to return to tania root folder before running curl and composer.phar install

Great to hear that it's work :)
Thanks for your suggestion. I'll update the documentation. We can close this issue for now.


Issues with revision and edition parsing

From #125
Last part parsed as an edition but not removed from document number:
✅ | NBS CIRC 74-1937e1937 | NBS CIRC 74e1937 | ✅ | NBS.CIRC.74-1937e1937 | NBS.CIRC.74-1937 | Circular of the Bureau of Standards C74: radio instruments and measurements
✅ | NBS HB 44-1988e1988 | NIST HB 44-1988 | ✅ | NBS.HB.44-1988e1988 | NBS.HB.44-1988 | Specifications, tolerances, and other technical requirements for weighing and measuring devices
✅ | NBS IR 84-2946e2946 | NIST IR 84-2946 | ✅ | NBS.IR.84-2946e2946 | NBS.IR.84-2946 | Polymers Division, technical activities 1984
✅ | NBS IR 89-4220e4220 | NIST IR 89-4220 | ✅ | NBS.IR.89-4220e4220 | NBS.IR.89-4220 | Electrical performance tests for storage oscilloscopes
✅ | NBS FIPS 100-1e1 | NIST FIPS 100-1 | ✅ | NBS.FIPS.100-1e1 | NBS.FIPS.100-1 | Federal Information Processing Standards Publication: interface between data terminal equipment (DTE) and
✅ | NBS FIPS 130-1988e1988 | NIST FIPS 130-1988 | ✅ | NBS.FIPS.130-1988e1988 | NBS.FIPS.130-1988 | Federal Information Processing Standards Publication: for information systems - intellig
✅ | NBS FIPS 131-1987e1987 | NIST FIPS 131-1987 | ✅ | NBS.FIPS.131-1987e1987 | NBS.FIPS.131-1987 | Federal Information Processing Standards Publication: small computer system interface (S
✅ | NBS FIPS 132-1987e1987 | NIST FIPS 132-1987 | ✅ | NBS.FIPS.132-1987e1987 | NBS.FIPS.132-1987 | Federal Information Processing Standards Publication: guideline for software verificatio
✅ | NBS FIPS 29-2e2 | NIST FIPS 29-2 | ✅ | NBS.FIPS.29-2e2 | NBS.FIPS.29-2 | Federal Information Processing Standards Publication: interpretation procedures for federal information proces
✅ | NBS FIPS 4-1e1 | NIST FIPS 4-1 | ✅ | NBS.FIPS.4-1e1 | NBS.FIPS.4-1 | Federal Information Processing Standards Publication: representation for calendar date and ordinal date for inform
✅ | NBS FIPS 5-2e2 | NIST FIPS 5-2 | ✅ | NBS.FIPS.5-2e2 | NBS.FIPS.5-2 | Federal Information Processing Standards Publication: codes for the identification of the States, the District of

Last part of NBS HB parsed as an edition and revision was added as merging result with DOI, result should have only revision:
✅ | NBS HB 105-1e1990r1990 | NIST HB 105-1-1990 | ✅ | NBS.HB.105-1e1990r1990 | NBS.HB.105-1r1990 | Specifications and tolerances for reference standards and field standard weights and mea

Edition parsed as edition and revision:
✅ | NIST HB 105-1e1990r1990 | NIST HB 105-1-1990 | ✅ | NIST.HB.105-1e1990r1990 | NIST.HB.105-1-1990 | Specifications and tolerances for reference standards and field standard weights and
✅ | NBS FIPS 100-1e1r1991 | NIST FIPS 100-1-1991 | ✅ | NBS.FIPS.100-1e1r1991 | NBS.FIPS.100-1-1991 | Federal Information Processing Standards Publication: interface between data terminal
✅ | NBS FIPS 11-1eSep1977rSep1977 | NBS FIPS 11-1-Sep1977 | ✅ | NBS.FIPS.11-1eSep1977rSep1977 | NBS.FIPS.11-1-Sep1977 | Federal Information Processing Standards Publication: American nati
✅ | NBS FIPS 14-1eDec1980rDec1980 | NBS FIPS 14-1-Dec1980 | ✅ | NBS.FIPS.14-1eDec1980rDec1980 | NBS.FIPS.14-1-Dec1980 | Federal Information Processing Standards Publication: Hollerith pun
✅ | NBS FIPS 14-1eMay1980rMay1980 | NBS FIPS 14-1-May1980 | ✅ | NBS.FIPS.14-1eMay1980rMay1980 | NBS.FIPS.14-1-May1980 | Federal Information Processing Standards Publication: Hollerith pun
✅ | NBS FIPS 16-1e1977r1977 | NBS FIPS 16-1-1977 | ✅ | NBS.FIPS.16-1e1977r1977 | NBS.FIPS.16-1-1977 | Federal Information Processing Standards Publication: bit sequencing of the code for
✅ | NBS FIPS 17-1e1977r1977 | NBS FIPS 17-1-1977 | ✅ | NBS.FIPS.17-1e1977r1977 | NBS.FIPS.17-1-1977 | Federal Information Processing Standards Publication: character structure and charact
✅ | NBS FIPS 18-1e1977r1977 | NBS FIPS 18-1-1977 | ✅ | NBS.FIPS.18-1e1977r1977 | NBS.FIPS.18-1-1977 | Federal Information Processing Standards Publication: character structure and charact
✅ | NBS FIPS 21-1e1975r1975 | NBS FIPS 21-1-1975 | ✅ | NBS.FIPS.21-1e1975r1975 | NBS.FIPS.21-1-1975 | Federal Information Processing Standards Publication: COBOL
✅ | NBS FIPS 22-1e1977r1977 | NBS FIPS 22-1-1977 | ✅ | NBS.FIPS.22-1e1977r1977 | NBS.FIPS.22-1-1977 | Federal Information Processing Standards Publication: synchronous signaling rates bet
✅ | NBS FIPS 32-1e1975r1975 | NBS FIPS 32-1-1975 | ✅ | NBS.FIPS.32-1e1975r1975 | NBS.FIPS.32-1-1975 | Federal Information Processing Standards Publication: character set for optical chara
✅ | NBS FIPS 32-1e1981r1981 | NBS FIPS 32-1-1981 | ✅ | NBS.FIPS.32-1e1981r1981 | NBS.FIPS.32-1-1981 | Federal Information Processing Standards Publication: character set for optical chara
✅ | NBS FIPS 32-1e1982r1982 | NBS FIPS 32-1-1982 | ✅ | NBS.FIPS.32-1e1982r1982 | NBS.FIPS.32-1-1982 | Federal Information Processing Standards Publication: character sets for optical char
✅ | NBS FIPS 33-1e1974r1974 | NBS FIPS 33-1-1974 | ✅ | NBS.FIPS.33-1e1974r1974 | NBS.FIPS.33-1-1974 | Federal Information Processing Standards Publication: character set for handprinting
✅ | NBS FIPS 68-2eAug1987rAug1987 | NBS FIPS 68-2-Aug1987 | ✅ | NBS.FIPS.68-2eAug1987rAug1987 | NBS.FIPS.68-2-Aug1987 | Federal Information Processing Standards Publication: BASIC
✅ | NBS FIPS 68-2eJan1987rJan1987 | NBS FIPS 68-2-Jan1987 | ✅ | NBS.FIPS.68-2eJan1987rJan1987 | NBS.FIPS.68-2-Jan1987 | Federal Information Processing Standards Publication: programming l
✅ | NBS FIPS 69-1e1985r1985 | NBS FIPS 69-1-1985 | ✅ | NBS.FIPS.69-1e1985r1985 | NBS.FIPS.69-1-1985 | Federal Information Processing Standards Publication: FORTRAN
✅ | NBS FIPS 70-1eJun1986rJun1986 | NBS FIPS 70-1-Jun1986 | ✅ | NBS.FIPS.70-1eJun1986rJun1986 | NBS.FIPS.70-1-Jun1986 | Federal Information Processing Standards Publication: representatio

Part of edition parsed as revision:
✅ | NBS FIPS 107-MAeMar1985r1985 | NBS FIPS 107-Mar1985 | ✅ | NBS.FIPS.107-MAeMar1985r1985 | NBS.FIPS.107-Mar1985 | Federal Information Processing Standards Publication: carrier sense mul
✅ | NBS FIPS 115-MAeMar1985r1985 | NBS FIPS 115-Mar1985 | ✅ | NBS.FIPS.115-MAeMar1985r1985 | NBS.FIPS.115-Mar1985 | Federal Information Processing Standards Publication: information proce

✅ | NBS HB 105-1e1990r1990 | NIST HB 105-1-1990 | ✅ | NBS.HB.105-1e1990r1990 | NBS.HB.105-1r1990 | Specifications and tolerances for reference standards and field standard weights and mea

https://nvlpubs.nist.gov/nistpubs/Legacy/hb/nisthandbook105-1-1990.pdf
PubID saying it's edition, but DOI saying it's revision.
Inside PDF:

@ronaldtse So is it revision or edition?

@mico great find here! And additionally, it is supposed to be "NIST Handbook" not "NBS Handbook" as per the screenshot! So this is also a data source issue.
In the content, the Abbrev PubID says "Rev. 1990".

So we need to clarify, and I suspect the correct resolution is "Rev. 1990".


Cleanup goreportcard warnings

https://goreportcard.com/report/github.com/constabulary/gb

Sure, removed changes pointed out.

Thanks.


Support smug - donate to Ukrainian Army 🇺🇦

Hello!
I'm the author of the smug, and I need your help. I’m fundraising money for a new car for the territorial defense forces, where my uncle is fighting from the first day of the war. I've already raised $3000 out of $5000.
I would appreciate any help (donate or repost), it would be the best way to support the project.
How to donate:
Paypal<EMAIL_ADDRESS>Wise<EMAIL_ADDRESS>BTC: bc1qmyphjt8ep4l2fvx4yppf9vmq0uhmcaefl03xe0
ETH: 0x0b96192951184a4b0df16ee947bbf0a60367bc85
USDT: 0x0b96192951184a4b0df16ee947bbf0a60367bc85
Thanks,
Ivan

The company is closed now, we have raised money and buying a car now :) Thanks to everyone who made a donation!


Add export formats

[x] DataCite v4 XML (search, OAI-PMH) (https://github.com/inveniosoftware/invenio-rdm-records/issues/1199)
[ ] DCAT-AP (https://github.com/inveniosoftware/invenio-rdm-records/issues/1202)
[x] MARC21 XML

[x] search (https://github.com/inveniosoftware/invenio-rdm-records/issues/1165)
[x] OAI-PMH (https://github.com/inveniosoftware/invenio-rdm-records/issues/1173)

[ ] BibTex (search)
[ ] DublinCore (search, OAI-PMH) (https://github.com/inveniosoftware/invenio-rdm-records/issues/1201)
[ ] JSON-LD (external contribution - do not take this one)
[x] https://github.com/inveniosoftware/invenio-rdm-records/issues/1154

Prerequisites

All metadata fields currently supported in Zenodo have to be part of the deposit form and metadata schema
Files indexing and serialization for search results

Next Steps

Review DataCite mapping
a. Migrate DCAT-AP using XSLT and custom logic for files serialization
Review DublinCore
Migrate MARC21 XML
Migrate BibTex
Migrate JSON-LD
Migrate GeoJSON
Allow instances to configure their own import/export types for REST API

One of the current issues is that a ResourceConfig is not easy to override/configure (we want to override request_body_parsers and response_handlers)
We should look into using something like the FromConfig utility that's used in services, e.g. for the permission_policy_cls

search accepts:

application/json
application/vnd.inveniordm.v1+json
application/vnd.citationstyles.csl+json
application/vnd.datacite.datacite+json
application/vnd.geo+json
application/vnd.datacite.datacite+xml
application/x-dc+xml
text/x-bibliography

These are defined in the APP_RDM_RECORD_EXPORTERS config variable by the content-type attribute. The ones that do not appear (MarcXML, DublinCore) is because they are not suitable for "list/search" serialization.
Action points:

Should we implement list on those above? To be added here https://github.com/inveniosoftware/invenio-rdm-records/blob/e4ced718577efaa78f8586339d4a5f19452c44ba/invenio_rdm_records/resources/config.py#L64
Should we add versioning to the serialization (e.g. datacite v4.3, v4.4, etc.)


Clean up extra trailing whitespace

This removes trailing whitespace and extra (>1) newlines from the code.

I'm going to close this for two reasons:

It conflicts with the repo now, so would need merging by hand
I'm not a fan of style commits as they mask git blame output and add confusion when debugging older commits.

My preference would be that we just try to be consistent with style and fix things around where we're working.

Could I do this only for blank lines, since that should not affect the blame output?
Since my text editor is configured to trim trailing whitespace, it will trim the extra newlines and whitespace from the files I edit. I figure that having the commit that fixes the whitespace being one specifically for that would be better than a commit that fixes something else, and cleans up the formatting.
Regarding the merge conflict, I am fine redoing this from master.


3 UAIs at once in the stack limit

Only the UAIs from the stack should be visible on the UI in one session.

It is resovled, discussed in the meeting.


Fix issue when using the ling command

When using the php artisan twig:lint command on our Gitlab CI (docker instance), I always had this output (wile having 97 templates, and errors) :
$ php artisan twig:lint --verbose
OK
1/1 valid files

I realized that an empty string was in STDIN, blocking the lint of all templates.
Checking if the template given in STDIN is empty fixed the issue.

Coverage remained the same at 25.926% when pulling 0360ef03c44a7af01606e53f65b63e6f9ae87f4d on kblais:linter-issue-in-ci into 6226d33331bbb1cdf64593a786f7efd1670200a7 on rcrowe:master.

Hi @barryvdh ! Any way this could me merged ? The fix is pretty basic, and really blocking me :/

Thanks :)


Update PatternFly packages

Update PatternFly packages to latest milestone
Fixes https://github.com/project-koku/koku-ui/issues/1151

Codecov Report

Merging #1153 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1153   +/-   ##
=======================================
  Coverage   75.24%   75.24%
=======================================
  Files         228      228
  Lines        4408     4408
  Branches      833      833
=======================================
  Hits         3317     3317
  Misses        973      973
  Partials      118      118

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 fbe7a7f...c4496f1. Read the comment docs.


Node run failed: error: operation not permitted

I followed the steps in FAQ.md and got the following error at step2, anyone else having the same problem?

When I run this test file alone, I get the following error

Please show your test.py ,
Before test your python script, please read the README.md

i just add “import numpy” before main function following the FAQ.md, The rest is unchanged.
Is that right? or i need to change my code?

Please show your test.py ,
Before test your python script, please read the README.md

Please show your test.py ,
Before test your python script, please read the README.md

i just add “import numpy” before main function following the FAQ.md, The rest is unchanged.
Is that right? or i need to change my code?

Is the user sandbox present on your platform?
uid=65537(sandbox) gid=59846(sandbox) group=59846(sandbox) — This system call execution is bound to the sandbox user.

Is the user sandbox present on your platform?
uid=65537(sandbox) gid=59846(sandbox) group=59846(sandbox) — This system call execution is bound to the sandbox user.

yes, currently the sandbox is on the platform.（目前正在服务器上配置sandbox的环境）
OS:Ubuntu20.04
CPU arch: amd64
Following the instructions:
1.Clone the repository using git clone https://github.com/langgenius/dify-sandbox and navigate to the project directory.
2.Run ./install.sh to install the necessary dependencies.
3.Run ./build/build_[amd64|arm64].sh to build the sandbox binary.
4.Run ./main to start the server.
while doing the "./main", the output is like this:

@athmey Please sure pip3 command is exists ？If not, please install it first

@athmey Please sure pip3 command is exists ？If not, please install it first

Thank you so much

@Hanfee  Why is the result of my operation like this?
Failed to run your python code, exit status 2
failed with exit status 2
uid=65537(sandbox) gid=1001(sandbox) groups=1001(sandbox)
I just add “import pandas” before main function following the FAQ.md
lib.DifySeccomp(65537, 1001, 1001)
import pandas
declare main function here
def main() -> dict:
return {"message": [1, 2, 3]}

I don't know where I went wrong, could you please clarify? Thank you very much


Array element - (dash) syntax support

I can't see any support or tests for the last paragraph of this section of RFC 6901:

o  If the currently referenced value is a JSON array, the reference
token MUST contain either:
*  characters comprised of digits (see ABNF below; note that
leading zeros are not allowed) that represent an unsigned
base-10 integer value, making the new referenced value the
array element with the zero-based index identified by the
token, or
*  exactly the single character "-", making the new referenced
value the (nonexistent) member after the last array element.

Should this be called out in the README as unsupported / always throwing an error?
I'm thinking specifically about this paragraph too:

For example, some applications might stop pointer processing upon an
error, while others may attempt to recover from missing values by
inserting default ones.

If you think supporting this is in scope, could you summarise your expectations for get, set and assign, and I could work up a PR?

That was an oversight, it should be supported.
No default values should be inserted. Attempting to access a - segment should result in the normal error Value at '${cursor}' does not have index '${segment}' except segment should be the computed index rather than -.
That means

- is only valid as the last element of a pointer.
get should error with the computed index
delete and unset should do nothing. Deleting something that doesn't exist is still a no-op, not an error.
set and assign should compute the index and assign the value to that index, but it will throw the normal does-not-have-index error if there are segments beyond -.

Thanks for finding this and for working on a fix. I'm hopeful that this should just be a fairly small change to the applySegment function.

Published as v0.7.0