local-path-provisioner not working on any of my new 2.4.4 Rancher clusters

Hello, here's log from the local-path-provisioner startup:

kubectl -n local-path-storage logs -f -l app=local-path-provisioner
time="2020-07-02T11:04:46Z" level=debug msg="Applied config: {"nodePathMap":[{"node":"DEFAULT_PATH_FOR_NON_LISTED_NODES","paths":["/mnt/ocfs2/local-path-provisioner"]}]}"
time="2020-07-02T11:04:46Z" level=debug msg="Provisioner started"
I0702 11:04:46.139190       1 leaderelection.go:242] attempting to acquire leader lease  local-path-storage/rancher.io-local-path...
I0702 11:05:29.345216       1 leaderelection.go:252] successfully acquired lease local-path-storage/rancher.io-local-path
I0702 11:05:29.345423       1 event.go:281] Event(v1.ObjectReference{Kind:"Endpoints", Namespace:"local-path-storage", Name:"rancher.io-local-path", UID:"ce6452a4-d435-47de-a54c-76e30eeb32a6", APIVersion:"v1", ResourceVersion:"895442", FieldPath:""}): type: 'Normal' reason: 'LeaderElection' local-path-provisioner-54f4dd9777-vncwf_79257c3f-0586-4515-b92a-7fe04c93be6c became leader
I0702 11:05:29.345449       1 controller.go:773] Starting provisioner controller rancher.io/local-path_local-path-provisioner-54f4dd9777-vncwf_79257c3f-0586-4515-b92a-7fe04c93be6c!
I0702 11:05:29.445621       1 controller.go:822] Started provisioner controller rancher.io/local-path_local-path-provisioner-54f4dd9777-vncwf_79257c3f-0586-4515-b92a-7fe04c93be6c!

So it seems it has started well, but... nothing happens after that!
Example POD I'm trying to deploy:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: emqx-pvc
  namespace: rtm
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 8Gi
  storageClassName: local-path
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: emqx-rtm
  namespace: rtm
  labels:
    app: emqx-rtm
spec:
[...]
  template:
    spec:
      containers:
      [...]
        volumeMounts:
        - mountPath: "/opt/emqx/data/mnesia"
          name: emqx-data
      volumes:
      - name: emqx-data
        persistentVolumeClaim:
          claimName: emqx-pvc

No PV is created, so PODs will fail to start and enter LoopBack.
Since the installation manifest leaves the "local-path-provisioner" namespace unassigned to any Rancher project, I've also tried to move it to the "System' project, or to my own project, always restarting it afterwards, but nothing has changed in any of these tests.
Please advise: as I've got an Oracle OCFS2 Multi-Read/Write block volume already setup, mounted and shared between all of my nodes, local-pat-provision would provide me a perfect fit...

Sorry, I've got it working by looking closely at the provided sample pvc.yaml and pod.yaml.
Firstly, I tried them as downloaded, and they worked straight away!
Then I've tried to namespace them, since I was suspecting it was a namespace issue, but they've worked well also in the namespaced version!
Finally, I've made sure to really restart my failing PODs, deleting them in the first place and, as soon as they came back, the PVC was bounded!
In the end, I've realized my setup can be accomodated by a simpler hostPath approach: my issue with that was replicas >1 for my cluster; but I've just noticed each node in this application (emqx) kindly creates and mounts a subdirectory named after POD's IP! So I just need to relax & no worry about each POD writing to its own private storage, in the first place!


Machines in scaleset are stuck in init state

Information

Onefuzz version: 2.23.0
OS: Windows latest

Provide detailed reproduction steps (if any)
Submitted our integration test job but it appears to be stuck.
onefuzz jobs get 6d23b847-eefa-473c-a258-63c32f6afe64 --query 'task_info[].state'
[
    "waiting",
    "waiting",
    "scheduled"
]

Check relevant scalesets -- we use 1 machine from this one, which should be fine since 1 is free.
onefuzz scalesets get b14e93a1-8fd1-4400-9933-b02ad70b342e --query nodes
[
    {
        "instance_id": "5",
        "machine_id": "b6890749-f2b8-4833-8d12-e6c765e2f3e3",
        "state": "done"
    },
    {
        "instance_id": "6",
        "machine_id": "bd22631e-be2f-475a-9926-22737f2daeb2",
        "state": "free"
    }
]

But this one seems to be in a weird state:
onefuzz scalesets get 0efe1fc6-441f-4501-b9e1-5945b1528a56 --query nodes
[
    {
        "instance_id": "0",
        "machine_id": "51424bf9-4edf-43bc-92a4-e9546d61a93f",
        "state": "init"
    },
    {
        "instance_id": "1",
        "machine_id": "d9c25725-6bf0-4178-aabc-7ef1e200e348",
        "state": "init"
    }
]

I believe this instance was upgraded to 2.23.0 recently, so not sure if it's related to the upgrade or not.
Expected result
Machines to be in free state
Actual result
Machines appear to be stuck in init state. Checked traces logs and didn't see anything obvious. There's some scaleset issues in the exceptions logs, possibly related?

Ran onefuzz nodes reimage 51424bf9-4edf-43bc-92a4-e9546d61a93f but node is still showing as reimage not requested.
{
    "debug_keep_node": false,
    "delete_requested": false,
    "machine_id": "d9c25725-6bf0-4178-aabc-7ef1e200e348",
    "messages": [],
    "pool_name": "***",
    "reimage_requested": false,
    "scaleset_id": "0efe1fc6-441f-4501-b9e1-5945b1528a56",
    "state": "init",
    "tasks": [],
    "version": "2.23.0"
}

The scaleset exception logs are related.


Update Composer dependencies (2021-05-28-00-09)

Visual regression test passed!
View the visual regression test report


urljsf 0.1.1

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11872875385.

Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:

linter: passed
azure: failed

Thus the PR was not passing and not merged.

Blocked by https://github.com/conda-forge/admin-requests/pull/1165


Npm audit security vulnerabilitie

The problem
The dependency "dicer" has 2 high severity vulnerabilities
Environment

Firebase SDK version: 10.2.0
Firebase Product: firebase-admin
Node.js version: 16.14.2
NPM version: 8.5.0

Relevant Code:
npm audit report
dicer  *
Severity: high
Crash in HeaderParser in dicer - https://github.com/advisories/GHSA-wm7h-9275-46v2
fix available via npm audit fix --force
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/dicer
firebase-admin  >=7.1.0
Depends on vulnerable versions of dicer
node_modules/firebase-admin
2 high severity vulnerabilities

Sorry there is already an issue opened with this problem, i'll wait the response to that one.


Timeframe then switch for list of chosen themes.

enable a timeframe as below so it uses same theme for that time then switches.
Make it so you can select which themes,
Choose In Order or Random
set timeframe to change like once an hour, once a day, once a week, once a month
I am always manually switching themes, this would be great and not too hard to code.

Novel idea.
For the sake of UX, I think that there should only be a randomize switch, but instead of the randomize switch being truly random, it would kind of be like "shuffle" in iTunes in that every effect is eventually used, although which one goes first is random.
Reason why is because I'd use a checkmark in Effects to indicate that Random is on.
Then obviously when "random" is on then there's another picker view, that shows "Per swipe", "per X time period", etc.

I have asked others also and the important part  of the idea is that many people only use about 5-7 themes regular, not necessarily the entire 50+ included.  Being able to select ONLY those themes they prefer most, with the same way you select combination themes code wise to reuse existing code, then choose hour, day, or week to switch.
The random shuffle is a sub idea when you switch do you prefer it to be in order of your numbering or showing randomly and as you said with all themes eventually being used.
Just a random shuffle alone is a good add, but still would show all 50 themes and the above way makes everyone happy if it can be done.


Installation errors "go install"

Version
1.12.0
go version go1.17.5
What happened?
../vendor/github.com/pganalyze/pg_query_go/v2/parser/parser.go:6:10: fatal error: pg_query.h: No such file or directory
#include "pg_query.h"
^~~~~~~~~~~~
What operating system are you using?
macOS(darwin/amd64)
What database engines are you using?
PostgreSQL
What type of code are you generating?
 Building sqlc requires Go >= 1.16. Once you've upgraded to that version, let me know if you're still seeing this bug

Oops, after reading this again, 1.12 is the sqlc version.
What version of Go are you using?

same for me
go 1.17

I'm seeing the same problem after I tried to vendor my dependencies. Reason seems to be that the include sub-folder below parser does not make it into the vendor tree.
Are you vendor as well?
This issue explains it https://github.com/golang/go/issues/26366  .
Solution from the sqlcs end would be to move the .h files in the parser package instead of having them in the include folder which apparently gets dropped because there are no go files in it. Also putting a dummy go file in the include dir could work (don't know if that needs to get used to not be dropped by vendoring).

The instructions on the module with the vendoring issue resolved it for me.


Run build.cmd failed.

I checkout and run build.cmd. I got this message.
KoreBuild.ps1 Line 62
&dotnet restore "$toolsProject" --packages "$PSScriptRoot" -f https://www.myget.org/F/dnxtools/api/v3/index.json -v Minimal
Error Info:
The structure of init data has changed, do not know how to interpret it

I fixed this issue by reinstall dotnet.


press space to talk notificataion, so PTT without headset is disturbing!

Not only local but also the remote voice activates this notification.
We should disable it intelligently, or at least the user should be able to disable it!

I think letting user disable it is enough. Non IT users tend to get confused when to much things happen automatically, so they would not understand why sometimes they get the message and sometimes they don't. But b this is only my opinion.

This is only the case if your audio device has cross talking issue. Usually this is by echo-cancellation filters either from audio driver or because your browser runs aggressive echo-cancellation or (you have disable echo-cancellation AND your mic plugs up your speaker device). In each case I think user should see that this is happening.

I thought @misi was talking about background noise, causing the PPT to appear. I can confirm what @so010 says, that with properly working echo cancelling, even if you use mic and speakers (not a headset), the PPT appears only when needed, so when you talk. At least I have not noticed, that it was appearing in a annoying way. I use a Jabra speaker/mic 90% of the time.

It seems it was just my mistake and it is only behaves badly if there is something wrong with the user :)
or the user echo cancellation..


feat: emit an error log on potential memory leak scenario

Given that the scenario #838 is likely caused by context confusion on long-running requests, this warning should help us determine whether a memory leak is due to an intrinsic design detail to the agent, or context confusion. Emitting this warning is a clear sign of the latter (the remedy would be to identify the userspace queueing mechanism that breaks context, and patch it/request that it support async resources).

Guys the promotion of these logs from "warn" to "error" is causing problems.  Specifically line 241 in trace-api.ts.
Is an error required here?

@mikelueck this was a mistake. The issue is fixed in #882 and released as the latest version of the module.


Support PEP 484 type comments in function definitions.

This document defines some suggested way for type annotations to be added to functions in python 2.7.
https://www.python.org/dev/peps/pep-0484/#suggested-syntax-for-python-2-7-and-straddling-code
I tested against 269a8d51c3f159dfe40e974dc9820e988b9d081c and found that type:  comments only seem to work outside of a function definition.
This works as I expect:
def foo(a):
    b = a # type: int
    b.

This does not (no completions are shown)
def foo(a):
    # type: (int) -> None
    a.

And neither does this (no completions are shown):
def foo(
    a,  # type: int
):
    # type: (...) -> None
    a.

Since  #1073 was closed recently, this might be a feature you care about.

Due to upcoming end of life of 2.7 it is unlikely we will be investing significant time here.

It would be nice to have this, as there is a lot of 2.7 code still out there that would benefit from more type checking.


Install script does not work on docker-machine (Boot2Docker)

docker@manager1:~$ curl -sSL https://rexray.io/install | sh
sort: invalid option -- 'V'
BusyBox v1.27.2 (2017-10-30 14:58:40 UTC) multi-call binary.

Usage: sort [-nrugMcszbdfiokt] [-o FILE] [-k start[.offset][opts][,end[.offset][opts]] [-t CHAR] [FILE]...

Sort lines of text

	-o FILE	Output to FILE
	-c	Check whether input is sorted
	-b	Ignore leading blanks
	-f	Ignore case
	-i	Ignore unprintable characters
	-d	Dictionary order (blank or alphanumeric only)
	-g	General numerical sort
	-M	Sort month
	-n	Sort numbers
	-t CHAR	Field separator
	-k N[,M] Sort by Nth field
	-r	Reverse sort order
	-s	Stable (don't sort ties alphabetically)
	-u	Suppress duplicate lines
	-z	Lines are terminated by NUL, not newline
gzip: invalid magic
tar: Child returned status 1
tar: Error is not recoverable: exiting now

$ lsb_release -a
Boot2Docker 18.01.0-ce (TCL 8.2.1); HEAD : 0bb7bbd - Thu Jan 11 16:32:39 UTC 2018

This however does work:
$ curl -sSL https://rexray.io/install | sh -s -- stable 0.11.1
generating self-signed certificate...
  /etc/rexray/tls/rexray.crt
  /etc/rexray/tls/rexray.key

rexray has been installed to /usr/bin/rexray

REX-Ray
-------
Binary: /usr/bin/rexray
Flavor: client+agent+controller
SemVer: 0.11.1
OsArch: Linux-x86_64
Commit:<PHONE_NUMBER>ac4426b04941b4002fb33b9efd972e
Formed: Tue, 19 Dec 2017 22:26:34 UTC

Hello @zaventh and thanks for updating us on the solution for this.


fix space between operators

follow-up to #4239

:white_check_mark:

Why can't we just use dfmt to do this automatically and all in one PR?

Why can't we just use dfmt to do this automatically and all in one PR?

I think dfmt would even a lot more?
And just adding space already affects 3500 lines, s.t. it's impossible to review via the web interface (I tried).
In any case, I would love to put this style change into one PR ...

I mean have dfmt do everything that it normally does and all in one PR. Assuming there are no bugs in dfmt, this should not be a problem. And even if there were, the auto-tester would catch them.
We would then be able to diff any PR with the dfmt output to stop style deviations.

I mean have dfmt do everything that it normally does and all in one PR. Assuming there are no bugs in dfmt, this should not be a problem. And even if there were, the auto-tester would catch them.

169 files changed, 97926 insertions(+), 67498 deletions(-)

169 files changed, 97926 insertions(+), 67498 deletions(-)

Better that than hundreds of separate PRs, which is what it would take to enforce all of dfmt's rules. And like I said, the auto-tester will catch any errors.

I thought that aligning trailing comments was a requirement for using dfmt?

Better that than hundreds of separate PRs, which is what it would take to enforce all of dfmt's rules. And like I said, the auto-tester will catch any errors.

I just tried. dfmt destroys custom formatting and ddoc headers :/
-> Let's start simple & step by step? I will put all missing operator spaces in this pr.

I will put all missing operator spaces in this pr.

done.

If this was done automatically using sed, then LGTM

Auto-merge toggled on

@JackStouffer

the auto-tester will catch any errors.

That's very optimistic of you, for a ~100K line diff. It's not like we have 100% unit test coverage or anything...

Thanks :)

And now I wait for the yelling to start.

Yep you were quite brave - I didn't expect it to be merged that quickly, but it just touches single lines so I hope for the best!

You avoided the bikeshedding quite skillfully

I thought that aligning trailing comments was a requirement for using dfmt?

That's for DMD.  I'm not sure anyone's really evaluated it for phobos yet - and phobos is not really internally consistent.


add network connection information and refactor docs

this PR adds new connection information about DevNet and applies some refactoring across several pages of the docs including:

developer quickstart --> now 3 pages instead of 1
machine setup --> moved to developer section (from basics)
papers --> added to basics section to include all published papers listed on website

the following changes were made
new pages

https://docs-pr-261.onrender.com/docs/technical/papers

moved pages

Machine Setup was moved from basics to developer

refactored pages

Developer / Quickstart / Orientation was broken up into 2 pages: "Orientation" and "Building"
a new page called "Connecting" was created to identify the various deployments of the NEAR platform

note, all external links were preserved during this move (we should always keep the same folder and file structure in our docs and just edit sidebars.json when refactoring so external sources linking to our docs don't end up with broken links)


bug with "mass"

hi,
this config
_SYSTEM_CONFIG = """
bodies {
  name: "box_1"
  colliders {
    box {
      halfsize {
          x: 0.5
          y: 0.5
          z: 0.5
        }
    }
  }
  inertia {
    x: 1
    y: 1
    z: 1
  }
  mass: 0.03
}

bodies {
  name: "box_2"
  colliders {
    box {
      halfsize {
          x: 0.25
          y: 0.25
          z: 0.25
        }
    }
  }
  inertia {
    x: 1
    y: 1
    z: 1
  }
  mass: 0.03
}
bodies {
  name: "Ground"
  colliders {
    plane {
    }
  }
  frozen {
    all: true
  }
}
bodies {
  name: "target"
  colliders {
    sphere {
      radius: 0.009
    }
  }
  frozen { all: true }
}

joints {
  name: "joint0"
  angle_limit {
      min: -60
      max: 60
  }
  rotation {
    z: 90
  }

  parent_offset {
    y: -0.6
  }
  child_offset {
      z: 0.1
  }

  parent: "box_1"
  child: "box_2"
  stiffness: 5000.0
  angular_damping: 35
}

actuators {
  name: "joint0"
  joint: "joint0"
  strength: 300.0
  torque {
  }
}

friction: 0.6
gravity {
  z: -9.81
}
baumgarte_erp: 0.1
angular_damping: -0.05

collide_include {
  first: "box_1"
  second: "Ground"
}
collide_include {
  first: "box_2"
  second: "Ground"
}

dt: 0.02
substeps: 4
"""

you can see the two boxes with training.ipynb with html.render, but after training if you visualize a trajectory, there is only a grey image to see.
If you stop and reset the trajectory video, you see in the controls the x,y,z, etc. values which are going fastly into minus till NaN, if you play the video?
If you change the "mass" values of both boxes to 1.0 ,  everything looks ok ?

One sharp edge for our engine is that small masses typically need shorter simulation steps.  I'd bet everything would work if you upped the number of substeps (or, equivalently, decreased dt).

thanks for help,
it worked , i used dt: 0.015
substeps: 24
and then it shows up


Adding Headers To Static Serving

How to you add custom headers to static server?

https://sifrr.github.io/sifrr/#/./packages/server/sifrr-server/?id=sendfile static server options are same as sendFile with some extra options.

https://sifrr.github.io/sifrr/#/./packages/server/sifrr-server/?id=sendfile static server options are same as sendFile with some extra options.


Use webview_{darwin,linux,windows}.go

Hi! This looks really cool!
One idea, though.
Go will automatically compile the suitable files if you use the convention webview_{darwin,linux,windows}.go
Using this technique, you could eliminate the need for users to deal with #error "Define one of: WEBVIEW_GTK, WEBVIEW_COCOA or WEBVIEW_WINAPI"
The feature is documented in https://golang.org/pkg/go/build/#hdr-Build_Constraints

Thanks for the suggestion! However, I have to mention that webview is not only a Go library, but also a standalone C library. For C/C++ users compile-time definition is inevitable because the language provides no features to detect the build target automatically.
And for Go we actually use the same build constraints anyway, just inside the cgo section: https://github.com/zserge/webview/blob/master/webview.go#L4-L11
I don't see how splitting it into multiple files would be better.
So if you don't mind - I will close this issue.

I got to take a second look then, hit the above error when trying to run the example last night.
Feel free to close this one :-)

Ah, I was bitten by https://github.com/zserge/webview/commit/083a796c6aa511a3d5295fb934a30779c1068ca3 (goos name is darwin, not macos)


fix(helm): wrong webhooks indentation

What type of PR is this?
/kind bug
What this PR does / why we need it:
Without this commit anything under integrations.podOptions.namespaceSelector: just gets dropped by k8s api-server
Does this PR introduce a user-facing change?
NONE

/retest

/release-note-edit
HelmChart: Fix a bug that the `integrations.podOptions.namespaceSelector` is not propagated.

/release-note-edit
Helm: Fix a bug where the configuration for `integrations.podOptions.namespaceSelector` didn't have an effect  due to indentation issues.


[HOLD for payment 2024-01-26] [HOLD for payment 2024-01-25] Cancel payment - Expense report with payment cancellation system message is not entirely deleted

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.26-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Create a new workspace
Go to workspace chat
Create a manual request
Edit the amount, description etc of the request to invoke system message
Delete the request
Note that the details page together with the system message is deleted
Create another manual request
Pay elsewhere the report
Go to expense report > 3-dot menu > Cancel payment

Expected Result:
The report will be entirely deleted since there is no more request in the report
Actual Result:
The report is not entirely deleted as the system message for payment cancellation still remains
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

Uploading Bug6345737_1705521965443!bandicam_2024-01-18_00-51-03-204.mp4…
View all open jobs on GitHub

#wave7-collect-approvers

It looks like the video upload failed here. A reproduction video would be helpful for me to understand this better

It feels like the steps are missing last step saying: Delete the report

The offending PR was reverted.


[ENH] DevOps Kick-off

This PR works together with the main docker-compose set-up at https://github.com/brainlife/brainlife/pull/195
The main changes are regarding docker/config/api, which then does not affect the original service code.
However, in api/common.js, I have adapted the code for the Redis connection to accept an URL like redis://redis:6379.

Supplanted by current set-up.


A Facility to Share State Between Operators in a DAG instance (i.e. a specific run).

I have the following use-case. My DAG loads data for a few days (e.g. because of late-arriving data, my daily run actually can load data for late-arriving data for previous days). I would like to get a sense of how many data rows were added. To do this, I would like to query my database before the run starts and then again at the end of the run. I would then like to send the results in an email at the end of the run.
Since I can query the final row count before I send the email in a single PythonOperator, my challenge is to save the initial row count before the run starts in earnest, so that I can compute a diff at the end of the run.
Where can I store this state so that I can access it between operators in the flow? This would be a good general facility to support. There is another ticket #170 However, I don't need that capability.
The state will need to be cleared after the run completes, either in a successful or failed manner.
General Design Proposal :

A Flow State table that has (dag_id,ds) as the unique key and a text column to support storing serialized structured text (e.g. Avro, Json)
A util function to allow Python operators to store to and retrieve from this table
An ability in the framework to delete this row on flow completion : successful or failed. I understand that if people CTRL+C or SIGKILL a backfill command, that this state might not be cleaned up, through I would expect subsequent executions would replace this row.

I like this idea a lot (https://github.com/airbnb/airflow/issues/170#issuecomment-128401782).
I think Variable provides the basic infrastructure to achieve this and we could build on top of it. See https://github.com/airbnb/airflow/issues/220, #133 and #12.
However, I'm not sure exactly what Variables are being used for but they don't feel like the right place for this specific use -- first because they're publicly/globally visible and we'd end up horribly polluting that namespace, and second because they don't enforce the dag/task/datetime id that this would require.
But I think they light the path. So I'd propose the following:

based on the code that defines Variables here, create a new table called State (or something) keyed by (dag_id, task_id, ds, time*) [*in case there are multiple runs per day?]
add class functions similar to Variable.get() which store and retrieve States
add get_state() and set_state() methods to PythonOperator which handle json serialization/loading and creating the proper table key.

So users could do something like this:
def my_func(x, **kwargs):
    # get the calling task
    task = kwargs['task']

    # set_state handles json conversion and generating the
    # appropriate keys (task_id, dag_id) for storing the value
    task.set_state('my list', [1, 2, 3])

    # get_state retrieves the most recently saved state called 'my value',
    # optionally restricting the query to a certain task, dag, or date.
    #
    # in this case, we're only getting 'my value' if it was written by a task called
    # 'my_other_task'
    state = task.get_state('my value', task_id='my_other_task', dag_id=None, date=None)

Maybe with a little magic we can get rid of needing to access kwargs/pass context, but let's leave that for the future. In fact, I guess users could do that by calling State.set() directly, but then they'd have to pass the task_id and dag_id that the task method handles automatically.
@r39132 your point number 3 could be handled with some of the callback functions that I believe were recently handled.
Critically, all the plumbing to do this already exists thanks to Variable; just need to write the utility functions. If this is interesting I'll take a crack at it.

Maybe 'save'/'load' or 'store'/'retrieve' are the right semantics... open to suggestions!

For reference, we're in solution mode here:
https://github.com/airbnb/airflow/pull/232


cargo fmt and cargo fmt --check don't agree on bindgen

Will put concrete STR in a sec.

STR: Check out https://github.com/rust-lang/rust-bindgen/commit/dd21b210dd7c7b91a571ed83e9bbbb249f24aa8b
$ rustup run nightly cargo --version
cargo 1.39.0-nightly (9655d70af 2019-09-10)
$ rustup run nightly cargo fmt
$ git diff # empty
$ rustup run nightly cargo fmt -- --check
Diff in /home/emilio/src/moz/rust-bindgen/src/options.rs at line 1:
-use bindgen::{builder, Builder, CodegenConfig, EnumVariation, RustTarget, RUST_TARGET_STRINGS};
+use bindgen::{
+    builder, Builder, CodegenConfig, EnumVariation, RustTarget,
+    RUST_TARGET_STRINGS,
+};
 use clap::{App, Arg};
 use std::fs::File;
 use std::io::{self, stderr, Error, ErrorKind, Write};
Diff in /home/emilio/src/moz/rust-bindgen/src/options.rs at line 6:
 use std::str::FromStr;

 /// Construct a new [`Builder`](./struct.Builder.html) from command line flags.
-pub fn builder_from_flags<I>(args: I) -> Result<(Builder, Box<dyn io::Write>, bool), io::Error>
+pub fn builder_from_flags<I>(
+    args: I,
+) -> Result<(Builder, Box<dyn io::Write>, bool), io::Error>
 where

I can reproduce this one as well, though I've no idea what the cause is 🤔

When running with the list file names option -l, it looks like on the first pass that rustfmt is correctly identifying the diff in options.rs
$ cargo +nightly fmt -- -l
rust-bindgen/src/options.rs
rust-bindgen/tests/../src/options.rs

There is a rustfmt.toml file in the root of the project directory:
max_width = 80
binop_separator = "back"

but also one in the tests directory:
normalize_doc_attributes = true

Since rustfmt will run for each target, my guess is that it's doing one pass against options.rs with the root level config, and then doing another pass against options.rs since it is included via in tests.rs, but with the tsets config

@topecongiro @scampi  - is this indeed a bug in rustfmt? Personally I feel the issue is that the same file is being formatted twice, but with two different conflicting config files (one with max_width = 80 and the other with max_width = 100)
If it is a bug, is the expectation that rustfmt would somehow know while processing the options mod for the test target that it should use the other config file for just that one mod?

Yeah, that's a good point (sorry, I missed the replies before).
I think this can be closed as invalid if you want, though probably a warning or some sort of detection would be useful for this (probably lower priority? Idk).

I am not really familiar with that part of the code, but that said:

Is it intentional that rustfmt picks up a new config file tests/rustfmt.toml ? Maybe this behavior is documented and I never paid attention to that.
if that is intentional, maybe the logic should be that code in tests gets reformatted with a config that is a merge of rustfmt.toml at the root and tests/rustfmt.toml.

Sorry for the late reply. @calebcartwright @scampi This seems like a bug to me. IIRC, the rule to pick the correct rustfmt.toml should be something like the following:

If --config is passed, then always use it.
If not, then use the config file that is in the same directory as the input file.
If the config file is not present, then look for the parent directory recursively.
If there is no config file in any parents, then look for global config file

So with respect to this issue, the options.rs should be always formatted using the config file at the project's root directory.
Also we should not format the same file more than once. Looks like when a module has #[path = "..."] attribute the path to the module does not get canonicalized.

@scampi -

Is it intentional that rustfmt picks up a new config file tests/rustfmt.toml ? Maybe this behavior is documented

I actually hadn't noticed it before either, but I think the docs here accurately reflect the rules @topecongiro enumerated

IIRC, the rule to pick the correct rustfmt.toml should be something like the following:

That makes sense. IMO, rustfmt is locating and using the correct config files. For the bin target (which includes options.rs getting formatted), rustfmt is correctly using the rustfmt file in the root of the project directory because the main input file is src/main.rs, and then when rustfmt is invoked for the test target (main input file being tests/tests.rs) it is correctly using the rustfmt file in the tests directory

Also we should not format the same file more than once. Looks like when a module has #[path = "..."] attribute the path to the module does not get canonicalized.

Sounds like that's the actual bug here 🐞 So IIUC, because src/options.rs is formatted with the invocation of rustfmt for the bin target, rustfmt should not attempt to format src/options.rs again when it's invoked for the tests target? However, because the paths are not canonicalized, rustfmt thinks it is seeing two different files and erroneously formatting twice?
rust-bindgen/src/options.rs
rust-bindgen/tests/../src/options.rs

@scampi  - any chance your https://github.com/rust-lang/rustfmt/pull/3590 PR solves that (Asking based on the PR title)? 🤞

@calebcartwright that PR is to handle path attribute in windows. I doubt this would have an impact here ;o(


Adding more metadata in Brick Ontology

Hi guys, I just found this awesome ontology. I want to add it into LOV so that people can easily reuse it in the LOD space. However, I suggest adding more metadata in the ontology, such as the first issued date, modified date each time there is a new release, etc. Something along the following:

brick: a owl:Ontology ;
rdfs:label "Brick" ;
dcterms:description "A uniform metadata schema for buildings";
dcterms:creator ( [ a sdo:Person ;
sdo:email<EMAIL_ADDRESS>;
sdo:name "Gabe Fierro" ] [ a sdo:Person ;
sdo:email<EMAIL_ADDRESS>;
sdo:name "Jason Koh" ] ) ;
dcterms:license https://github.com/BrickSchema/brick/blob/master/LICENSE ;
dcterms:version "1.2.0" ;
dcterms:issued "2020-12-20" ; #first issued date
dcterms:modified "2021-02-21" ; # your last modified date
dcterms:publisher https://brickschema.org/consortium ;
rdfs:isDefinedBy https://brickschema.org/schema/1.2/Brick ;
rdfs:seeAlso https://brickschema.org .

Hello @gatemezing! Thanks for the suggestion to add more metadata to Brick . I've just filed #245 which adds the items that you mentioned. The PR will amend the ontology definition to the following:
<https://brickschema.org/schema/1.2/Brick> a owl:Ontology ;
    rdfs:label "Brick" ;
    dcterms:creator ( [ a sdo:Person ;
                sdo:email<EMAIL_ADDRESS>;
                sdo:name "Gabe Fierro" ] [ a sdo:Person ;
                sdo:email<EMAIL_ADDRESS>;
                sdo:name "Jason Koh" ] ) ;
    dcterms:issued "2016-11" ;
    dcterms:license <https://github.com/BrickSchema/brick/blob/master/LICENSE> ;
    dcterms:modified "2021-03-23" ;
    dcterms:publisher [ a sdo:Consortium ;
            sdo:legalName "Brick Consortium, Inc" ;
            sdo:sameAs <https://brickschema.org/consortium/> ] ;
    rdfs:isDefinedBy <https://brickschema.org/schema/1.2/Brick> ;
    rdfs:seeAlso <https://brickschema.org> ;
    owl:versionInfo "1.2.0" .

Can you verify that this matches what you would expect? Thanks!


host in swagger.json incorrect on Heroku after upgrading from 4.2.1 to 4.3.1

I have an application that uses hapi-swagger deployed to Heroku.
In version 4.2.1 my host was being correctly detected and set in the generated swagger.json. Upon upgrading to 4.3.1, the host is no longer correctly detected as the host that was used to make the request by the client, but instead it is the internal host of the heroku app, i.e. "258b8587-dddb-48c0-99ad-d9d75422f3fc:8625"
Any idea what could be causing this? I looked at the diff between the two versions and it is difficult to tell what could be causing it without really digging in.
I have pinned to v4.2.1 for now, and things are working as I expect.

Same here. v4.2.1 works, v4.3.1 - doesn't.

Hi this is next on my list to look at, hopefully I will get to it by Thu/Fri this week. There have been a few changes to get the plugin to work better with reverse proxies and azure which may have caused this. Need to go over the changes and test it in different live environments.

Thanks Glenn

Hi sorry its taken so long to sort this out.
There is now a fix in the latest npm release v5.0.0 The problem was created around changes to allow you to add hapi-swagger document on one hapi connection with the API been on another.
So unless you use the connectionLabel property in hapi-swagger options the host should be found correctly when deploying to Heroku.
Example app deployed Heroku: to http://pure-bastion-46398.herokuapp.com/documentation
Also if you do have future issue you can set the host within the hapi-swagger options. This will override any auto discovery that the plugin may perform.
const options = {
    host: 'pure-bastion-46398.herokuapp.com',
    info: {
            'title': 'Test API Documentation',
            'version': Pack.version,
        }
    };

server.register([
    Inert,
    Vision,
    {
        'register': HapiSwagger,
        'options': options
    }], (err) => {
        server.start( (err) => {
           if (err) {
                console.log(err);
            } else {
                console.log('Server running at:', server.info.uri);
            }
        });
    });

If you have any more problem please let me known

thanks @glennjones

thanks @glennjones . It Worked


Update front-end to work with code tables

Describe the Task
Update front-end to work with code tables
@anissa-agahchen to fill out specifics

The front-end shouldn't need any changes (assuming I'm not forgetting anything).  All of the code tables for the forms are populated into the spec before it it sent from the API.
The current code that populates those code tables is here: https://github.com/bcgov/lucy-web/blob/dev/api-mobile/src/utils/api-doc-security-filter.ts
Currently it uses a couple of tags that are in the spec to determine which code tables/values to pull in.
          "species_agency_code": {
            "type": "string",
            "title": "Agency",
            "x-enum-code": {
              "x-enum-code-set-name": "species_agency_code",
              "x-enum-code-value": "species_agency_code",
              "x-enum-code-name": "description"
            }
          },

That overall mechanism should still work, but the actual x-blah tags and the api-doc-security-filter.ts code will need updating to account for the new code-table model.

I think this has been taken care of with https://github.com/bcgov/invasivesbc/pull/187 right @NickPhura unless there are additional requirements


perf: speed up fsst decompression

before:

after:

to reproduce:
cargo run --release --example benchmark
in rust/lance-encoding/compression-algo/fsst
machine info:
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
Linux 192 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 GNU/Linux

Codecov Report
Attention: Patch coverage is 60.73620% with 64 lines in your changes missing coverage. Please review.

Project coverage is 79.27%. Comparing base (02294a1) to head (0ae9507).

Files
Patch %
Lines

...t/lance-encoding/compression-algo/fsst/src/fsst.rs
60.73%
60 Missing and 4 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2626      +/-   ##
==========================================
- Coverage   79.35%   79.27%   -0.08%
==========================================
  Files         213      213
  Lines       62520    62669     +149
  Branches    62520    62669     +149
==========================================
+ Hits        49610    49681      +71
- Misses       9996    10059      +63
- Partials     2914     2929      +15

Flag
Coverage Δ

unittests
79.27% <60.73%> (-0.08%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

end-to-end test:

to reproduce:

disable dictionary encoding
download dataset
wget https://huggingface.co/datasets/HuggingFaceFW/fineweb/resolve/main/data/CC-MAIN-2013-20/000_00000.parquet\?download\=true
run script(set LANCE_USE_FSST environmental variable to enable fsst and unset it to disable)

from lance.file import LanceFileReader, LanceFileWriter
import pyarrow.parquet as pq

parquet_file_path = "/home/x/data.parquet"
data = pq.read_table(parquet_file_path)
lance_file_path = '/home/x/lance-experiments/fineweb/output.lance'
with LanceFileWriter(lance_file_path) as writer:
  writer.write_batch(data)

import datetime
import pyarrow.parquet as pq
from lance.file import LanceFileReader

start = datetime.datetime.now()
tab = pq.read_table(parquet_file_path)
end = datetime.datetime.now()
elapsed = (end - start).total_seconds()
print(f"Parquet elapsed: {elapsed}s")

start = datetime.datetime.now()
tab2 = LanceFileReader(lance_file_path).read_all().to_table()
end = datetime.datetime.now()
elapsed = (end - start).total_seconds()

import os

lance_file_size = os.path.getsize(lance_file_path)
lance_file_size_mib = lance_file_size // 1048576
parquet_file_size = os.path.getsize(parquet_file_path)
parquet_file_size_mib = parquet_file_size // 1048576

if os.getenv("LANCE_USE_FSST") is not None:

  print(f"Parquet file size(fsst): {parquet_file_size_mib} Mbytes")
  print(f"Lance file size(fsst): {lance_file_size_mib} Mbytes")
  print(f"Lv2(fsst) elapsed: {elapsed}s")
else:
  print(f"Parquet file size(fsst): {parquet_file_size_mib} Mbytes")
  print(f"Lance file size(no fsst): {lance_file_size_mib} Mbytes")
  print(f"Lv2(no fsst) elapsed: {elapsed}s")

assert tab == tab2

print("Tables are equal")

ha, sorry that I didn't explain this PR, it is basically a rust translation from the original c++ implementation of decompression.
and uses rust's ptr::write_unaligned as a performant way to do store


Known Bugs and Wishlist

Bugs:

New existing suspect input has no error feedback
Homepage 3rd pannel positioning
Validation error carry over to next case on import
Search bar has no error handling (navigates to blank edit page)
Navbar page resize not responsive
DataTable error handling
DataTable latency issues
Batch input end early
Database security
Access tier privileges need implementation
New suspect forms keep data from original when duplicated (if original is filled out)

Wishlist:

Continuous integration
Implementing cookie authentication in addition to session storage for JWT
Increasing test coverage
Edit user
More flexible query and visualization
Map integration for visualizing crime address locations

My one wish: DRN validation should be done at the beginning of the entry process for a document to avoid wasting time entering an extant document.


Move to 'One' yaml semantic for Model deployments

/kind feature
Describe the solution you'd like
User needs to provide only "one" yaml file for model deployment. KFserving takes care of the rest. Possibly align with MLSpec

/assign @animeshsingh

Can you elaborate a little bit here? We already have a "one" yaml semantic. Do you mean for things like secrets, service accounts, and ingress? These will inevitably need to be driven outside the kfservice.yaml file.

Closing due to lack of response.
/close


New API method needed for Graph service

Feature Request
Graph service is missing latest service principal endpoints.
Go sdk file: https://github.com/Azure/azure-sdk-for-go/blob/master/services/graphrbac/1.6/graphrbac/serviceprincipals.go
API spec: https://github.com/Azure/azure-rest-api-specs/blob/e280b0a088439ed82a46e3b470d8da487de51037/specification/graphrbac/data-plane/Microsoft.GraphRbac/stable/1.6/graphrbac.json#L1287
Didn't find the method that implements this API in the SDK.

Based on the linked swagger the API can be found here.
https://github.com/Azure/azure-sdk-for-go/blob/master/services/graphrbac/1.6/graphrbac/applications.go#L363
Let me know if that works.

Thanks, @jhendrixMSFT ! I'll close the issue.


problem sending notification to two bots of telegram

Home Assistant release with the issue:

Home Assistant 0.101.3
Versione frontend: 20191025.1 - latest
Last working Home Assistant release (if known):
NA
Operating environment (Hass.io/Docker/Windows/etc.):

HASSIO on raspberry pi 3+
Integration:

https://www.home-assistant.io/integrations/telegram/
Description of problem:
I'm not able to integrate using two telegram bots...only first bot work fine
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

# connessione per notifica tramite telegram
telegram_bot:
  - platform: polling
    api_key: !secret api_key_telegram_daniele
    allowed_chat_ids:
      - !secret chat_ids_telegram_daniele
      - !secret chat_ids_telegram_barbara

# bot daniele telegram
notify:
 - name: telegram_daniele
   platform: telegram
   chat_id: !secret chat_ids_telegram_daniele
 - name: telegram_barbara
   platform: telegram
   chat_id: !secret chat_ids_telegram_barbara
 - name: famiglia
   platform: group
   services:
     - service: telegram_daniele
     - service: telegram_barbara

**Traceback (if applicable):**

telegram Error sending message: Chat not found. Args ....

**Additional information:**
I'm using unique token to access HTTP API, bot created with this telegram account work fine, but I'm not able to send notification to second bot created with another telegram account with a different token...

I leave here detailed logs:
2019-11-19 10:15:09 ERROR (SyncWorker_13) [homeassistant.components.telegram_bot] Error sending message: Chat not found. Args: (10333415xx, 'Home Assistant on Pi booted'), kwargs: {'parse_mode': 'Markdown', 'disable_notification': False, 'disable_web_page_preview': None, 'reply_to_message_id': None, 'reply_markup': None, 'timeout': None}


WSL does not start at all, all commands return blank

Version
10.0.19043.2006
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
I attempted to install the latest Ubuntu version (the first time I have tried installing Linux on this machine). I also tried using wsl --help and such commands
Expected Behavior
Ubuntu would install and the commands would do their required job.
Actual Behavior
I get the following error message from Ubuntu:
Please restart WSL with the following command and try again:
wsl --shutdown
wsl -- unregister DISTRO_NAME
however, whenever I try to use any wsl commands there is no output what so ever and the terminal is ready for another command
Diagnostic Logs
No response

/logs

I'm also dealing with this issue.


Add finer information on state of conda-store environment builds

I've had several env build failures recently (various reasons) that weren't caught by ci testing. On multiple occasions we've had to go into kubectl/k9s to see the failure or were it got hung up.
I like how everything is automated here, but when my gh action for deployment is showing "green" its misleading that the deployment is complete. I'd like some tooling (or documentation) to tell me how to set up kubectl to see what's going on after gh actions has done it's thing.
I know the pretense is that qhub is k8s for people who don't know k8s, but I need some additional monitoring capability.

I do not think that realtime logs will be possible. However I do think it would be easy to add further information with a progress bar for each environment.

solve
build
create lockfile
create conda pack
create conda docker image
And this should be reflected in a progress bar.

This is complete to my liking so I'm going to close.


Flyway multiple schemas support and search_path conflicts

Hello,
there's an issue when using multiple flyway instances to manage multiple schemas distinct as described here (second strategy):
http://flywaydb.org/documentation/faq.html#multiple-schemas
Example: I got 2 schemas: 'foo' and 'bar' and the search path is set to 'foo, bar'
I create a flyway instance to manage schema 'foo'
locations = /sql/foo
schemas = foo
table = schema_version
and a script containing the code
drop table if exists toDrop;
The table toDrop lives in schema 'bar' and not 'foo'. So the flyway instance will drop the table from schema 'bar'! But this instance was created to manage schema 'foo' and only this schema. So this behaviour is very dangerous.
I know why this is happening. It's because of this fix:
https://code.google.com/p/flyway/issues/detail?id=358
Flyway sets the search_path to something like that foo, foo, bar. So the scripts might also touch schema 'bar'.
I think it would be nice to have

a property to set the search_path on my own or
a pre-executing sql-script which is always executed before migrating begins (to set priviliges, search_paths, ...)
an additional boolean option for the setSchemas() to also set the search_path simultaneously

Thanks in advance!

There is a problem using method beforeMigrate for setting the search_path to a specific schema. My database setup is the following:
I use a PostgreSQL 9.1 database with 2 schemas foo and bar and the search path is set to foo, bar. Both schemas were migrated using flyway. Now I remove schema bar for example with
drop schema bar cascade;

and create a new flyway sql script for schema foo. This migration fails at flyway.migrate():
Caused by: org.flywaydb.core.api.FlywayException: Error setting current schema to "foo"
        at org.flywaydb.core.internal.dbsupport.DbSupport.setCurrentSchema(DbSupport.java:103)
        at org.flywaydb.core.Flyway$1.execute(Flyway.java:1052)
        at org.flywaydb.core.Flyway$1.execute(Flyway.java:1006)
        at org.flywaydb.core.Flyway.execute(Flyway.java:1418)
        at org.flywaydb.core.Flyway.migrate(Flyway.java:1006)
        ... 18 more
Caused by: org.postgresql.util.PSQLException: ERROR: invalid value for parameter "search_path": "foo, bar"
  Detail: schema "bar" does not exist
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:561)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:419)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:412)
        at org.flywaydb.core.internal.dbsupport.JdbcTemplate.execute(JdbcTemplate.java:219)
        at org.flywaydb.core.internal.dbsupport.postgresql.PostgreSQLDbSupport.doSetCurrentSchema(PostgreSQLDbSupport.java:67)
        at org.flywaydb.core.internal.dbsupport.DbSupport.setCurrentSchema(DbSupport.java:101)
        ... 23 more

I don't understand this behavior. I want to migrate schema foo so the "missing schema bar" is something irrelevant at this moment. That's exactly the reason I'm using method beforeMigrate. But this method seems to be called later?
Using Flyway 3.2.1


Feature: Disable cloud user list other user's namespaces.

What is the problem this feature will solve?
Currently, one cloud user can access its own namespace, but can list all other's namespaces.
Will leak user login/register informations.
If you have solution，please describe it
No response
What alternatives have you considered?
No response

Remove list here should fix it, but more tests are required.
https://github.com/labring/sealos/blob/5d5e8227a1f781d1c3e3058aff59ba595f803350/controllers/user/controllers/usergroupuserbinding_controller.go#L100


Trigger use-case tests for Events from a github worflow/action

Description
Building on the output of issue #166. This issue should focus on getting the tests to run scheduled with the help of github actions.
Additional Information
No response
Tasks

[ ] Define environment and environment variables for workflows running from Events
[ ] Create a slack hook that can be used to publis alerts to slack.
[ ] Define a workflow in github to run the use-case tests for Events
[ ] Trigger workflow from Azure DevOps to run once every 15 minutes
[ ] Clean up the use-case pipeline(s) to skip the Events tests
[ ] Find a way to highlight failing tests in the final summary of the test run.

Acceptance Criterias

[ ] Use-case tests are started once every 15 minutes.

Look into a github app for the triggering task as OAuth token is the only way to authenticate towards the workflow without using a PAT at the time.


docs,daemon: Added discouragement warnings for MetalLB to docs and agent

Added warnings explaining that development on the MetalLB based BGP feature has stopped. The feature will not be deprecated in 1.13, so noted that security updates and bugfixes will still be applied.
Even though we can't officially deprecate yet, we would like to highly discourage adoption of the old feature unless absolutely necessary.
Fixes: #22246
Signed-off-by: Dylan Reimerink<EMAIL_ADDRESS> Added discouragement warnings for MetalLB to docs and agent

Reading the description, you can probably remove the release-blocker label?

Reading the description, you can probably remove the release-blocker label?

I marked it as such since the original issue is also a release blocker and we would like this message to be there in the 1.13 docs.
CC @joestringer

/test

/test

Alright, its not getting better then this I guess. All reviews are in, CI green except for 2 tests which both hit flake #22019.
Marking as ready-to-merge


make it Dublin Core consistent

We should store the metadata as recommended by dublin core or equivalent as this is now common standard.

I feel the elements here https://guides.library.ucsc.edu/c.php?g=618773&p=4306386 should be stored in the meta object

This is to make reuse a bit easier, especially if we export to Zenodo. The following fields should be there:
Contributor – “An entity responsible for making contributions to the resource.”
Coverage – “The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.”
Creator – “An entity primarily responsible for making the resource.”
Date – “A point or period of time associated with an event in the lifecycle of the resource.”
Description – “An account of the resource.”
Format – “The file format, physical medium, or dimensions of the resource.”
Identifier – “An unambiguous reference to the resource within a given context.”
Language – “A language of the resource.”
Publisher – “An entity responsible for making the resource available.”
Relation – “A related resource.”
Rights – “Information about rights held in and over the resource.”
Source – “A related resource from which the described resource is derived.”
Subject – “The topic of the resource.”
Title – “A name given to the resource.”
Type – “The nature or genre of the resource.”

Something that one might at least add upon export is that the entry was recorded with the ELN (and the git commit hash or something like that)


Added a new Test case to 'Seek and Destroy challenge'

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #11201

Description

Added test which calls the function with at least 8 inputs.

LGTM 👍


Add natsort option

Allowing for the sorting of jobs by various parameters might be useful. For me, the most helpful case is applying a natural sort to the job name:
Unsorted:

Sorted:

I've added a key hint as with the other key-press actions.
No pressure to merge this, it's mainly for my own benefit, but it's here if you want it!

I think this is already possible with --sort. I'd maybe try --sort "i", see if that's what you want. FYI, Slurm's default for sort is P,t,-p.


Open source Cypress FX2 Firmware

This PR moves our Cypress FX2 over to open source firmware built with SDCC

This was actually merged in https://github.com/timvideos/HDMI2USB/commit/57085783e1f609c1162b9c077323dd555bec832b

The HDMI2USB-jahanzeb-firmware is no longer under development.
All active development is now on the HDMI2USB-misoc-firmware which supports both the Atlys and Opsis boards and has loads of other new features!


run_tests erroneously reports test-math as passing

@fritzo the screen printout of "make test" is showing test-math as passing but the test-math stderr file in the log directory shows the errors that I mentioned earlier in this thread.
Same issue for test-refactorCompilationSteps and presumably other tests.
Can you debug the run_tests output?

Sure I'll take a look. Note that "known failures" will probably log errors in the log files and still pass. If that's the case and is confusing, I'll add log messages for "BEGIN KNOWN FAILURE" and "END KNOWN FAILURE". I sure hope that's the case, and we're not silencing real errors.


How we can uno all the last 3 4 query’s were execute on database to undo the values change in tables

How we can uno all the last 3 4 query’s were execute on database to undo the values change in tables

Closing as duplicate of https://github.com/simolus3/drift/discussions/2524.


Error: Cannot resolve module 'react-addons-linked-state-mixin'

react-addons-linked-state-mixin looks to be missing from /client/package.json
ERROR in ./src/app/parts/auth/views/resetPassword.js
Module not found: Error: Cannot resolve module 'react-addons-linked-state-mixin' in
/Users/me/dev/react/starhack/client/src/app/parts/auth/views
 @ ./src/app/parts/auth/views/resetPassword.js 17:35-77

Thanks a lot for the report, should be fixed in https://github.com/FredericHeem/starhackit/commit/e5f66663286631dbd728538cf36934c593fbe0f9


add webphone events

to: https://github.com/ringcentral/ringcentral-js-integration-commons/pull/48


[Ethereum Payout Handler] Object reference not set to an instance of an object.

Hello, I added to his pool coin ELLE has made changes like EXP has launched the claymore miner so WALLET.RIG but do not go payments displays this error:
[2017-10-28 12:27:15.3457] [E] [ella1] [Ethereum Payout Handler] Object reference not set to an instance of an object.
What could be the problem?

Could you post the full stacktrace?

Здесь все изменения что я делал
https://github.com/SolarPool/miningcore_ella

The issue is relevant.
Could this be associated with the database,
[2017-10-28 19:30:17.0945] [E] [EXP1] [Ethereum Payout Handler] Object reference not set to an instance of an object.


Fix issues in Measurement_duration

This PR contains following changes :

Update the check for measurement_duration to be in the range of +- 5seconds
Update optional parameter validation failure for performance profile
Update delete API to get data from the API object

Merging this as the failing tests require test updates (cc @chandrams)


make the sdk available in maven central

Modern builds fetch dependencies from a central repo instead of adding jars to the lib folder.
More info on deploying to central here:
http://central.sonatype.org/pages/ossrh-guide.html

+1

Yup. Really needed for Gradle build.

+1

+1

+1

Maven og JCenter please :)

+1

for community, this is very important to be done...

If it's not on maven central it does not exist! It's as simple as that.

We cannot publish library either on Maven Central or jCenter as this is not open source library.
We need to investigate private maven repository.
On Fri, Mar 20, 2015 at 5:16 PM, Francis De Brabandere
<EMAIL_ADDRESS>wrote:

If it's not on maven central it does not exist! It's as simple as that.
Reply to this email directly or view it on GitHub:
https://github.com/Estimote/Android-SDK/issues/43#issuecomment-84058919

Ah, yes, that is true. Are there some specific reason for this not being open source? I haven't used much time on these BLE libraries, but aren't they mostly doing the same?

Our beacon configuration is our IP.
On Fri, Mar 20, 2015 at 5:24 PM, Kyrre Havik Eriksen
<EMAIL_ADDRESS>wrote:

Ah, yes, that is true. Are there some specific reason for this not being open source? I haven't used much time on these BLE libraries, but aren't they mostly doing the same?
Reply to this email directly or view it on GitHub:
https://github.com/Estimote/Android-SDK/issues/43#issuecomment-84060644

Forgot to answer this. I understand that it's your IP, and you are free to use it as you please. But that doesn't really answer why it can't be open sourced. And I'm not necessarily talking about free software, but open so we can see what is done, and help Estimote expand on it.

@Kyrremann +1

We are not open sourcing it as for now we do not want to reveal how we connect and configure our beacons.
On Mon, Mar 23, 2015 at 7:35 PM, Adrián Mouly<EMAIL_ADDRESS>wrote:

@Kyrremann +1
Reply to this email directly or view it on GitHub:
https://github.com/Estimote/Android-SDK/issues/43#issuecomment-85135921

Okay, that is understandable :)
Anyway, I think https://bintray.com/ allows for non OSS, it's just free if it's OSS.

Btw, we'll be adding private repo support to JitPack so you'd be able to easily publish closed-source libraries as maven artifacts. If that sounds interesting happy to notify you when its available

@jitpack-io Yes, please please do, :).

There is progress. From version 0.5 SDK is distributed as AAR.

cheers!

Awesome!!!

+1

Please add this to documentation about aar-distributed library:
http://tools.android.com/tech-docs/new-build-system/user-guide/manifest-merger#TOC-tools:overrideLibrary-marker
In case if your app uses minSdk lower that estimote's - the is needed to build successfully.
For me it worked even without specifying minSdk in Manifest (since it is present in my build.gradle file already) - just this line is enough: <uses-sdk tools:overrideLibrary="com.estimote.sdk" />

@Den-Rimus Thanks a lot, appreciated. Added to README.

@wiktor Got an update. JitPack now supports publishing a library that's built from a private repository. The library can be made public while the source code remains private.

@wiktor Any update on publishing this library via JitPack now that the feature is supported?

Good news. We have green light from Maven Central to be included in them.
Starting from version 0.8.7, Estimote SDK is available in Maven Central: com.estimote:sdk:0.8.7@aar.


Retraining an existing openface classifier

Context of the issue.
[Provide more detailed introduction to the issue itself and why it is relevant]
If we have a face authentication system to be implemented for an organization in which we want to grant access to the valid employees and reject individuals foreign to the organization.For achieving this we train the openface model with faces of all of the organizations'  employees.However now how can we modify the existing classifier(retrain)  to validate the newly joined employees.Also how can this be done for employees vacating the organization,such that access is no longer granted to them.
Expected behavior.
[Describe what you would expect to have resulted from this process.]
My question  is that, is  there a way to achieve this, with the Openface library,without training the whole new set of images again.In short can we "expand" the existing classifier to incorporate  employee changes.
Actual behavior.
[Describe what you currently experience from this process, and thereby explain the bug.]
Steps to reproduce.
[Present a minimal example and steps to produce the issue.]
OS and hardware information.

Operating system: [todo]
Torch version: [todo]
CPU architecture: [todo]
GPU type (if using): [todo]

This would be an extremely useful feature/documented process. It helps significantly with the expansion of services that might be built around this.


Helper to check against motor limits

For Hyperion, and in general across MX DAQ, we want to be able to easily check if a position is within motion limits. Specifically, we use optical edge detection to find a pin tip and then want to check if that's within the smargon limits or else stop the collection.
In ophyd we do something like:
class Smargon(Device):
    x: EpicsMotor = Component(EpicsMotor, "X")

    def get_x_in_limits(self, position: float):
        low = self.x.low_limit_travel.get()
        high = self.x.high_limit_travel.get()
        return low <= position <= high

def plan():
    if smargon.get_x_in_limits(100):
        yield from ...
    else:
        yield from ...

There are issues in doing this in ophyd-async:

The limit PVs are not in the Motor object (https://github.com/bluesky/ophyd-async/issues/42)
The above is a bad solution anyway as we're doing gets without going through the RE

My current work around is:

class XYZLimitsChecker(Device):
    """Checks that a position is within the XYZ limits of the motor.
    To use set the x, y, z vector to the device and read check `within_limits`
    """

    def __init__(self, prefix: str) -> None:
        self.within_limits = False

        axes = ["X", "Y", "Z"]
        self.limit_signals = {
            axis: (
                epics_signal_r(float, f"{prefix}{axis}.LLM"),
                epics_signal_r(float, f"{prefix}{axis}.HLM"),
            )
            for axis in axes
        }

    def children(self) -> Iterator[Tuple[str, Device]]:
        for attr, signals in self.limit_signals.items():
            yield attr + "low_lim", signals[0]
            yield attr + "high_lim", signals[1]
        return super().children()

    async def _check_limits(self, position: np.ndarray):
        check_within_limits = True
        for i, axis_limits in enumerate(self.limit_signals.values()):
            check_within_limits &= (
                (await axis_limits[0].get_value())
                < position[i]
                < (await axis_limits[1].get_value())
            )
        self.within_limits = check_within_limits

    def set(self, position: np.ndarray) -> AsyncStatus:
        return AsyncStatus(wait_for(self._check_limits(position), None))

def my_plan():
    yield from bps.set(limit_checker, [1, 2, 3])
    if limit_checker.within_limits:
        ...

Discussed offline and decided plan logic that gets limits from specific signals on the motor, then put the plan stub in ophyd-async next to the Motor class


I've become a god help me

Ever since I enabled the intrnlw theme I've transcended the simple plain of mind and matter. Now that wouldn't be a problem, but I can't seem to find a way to go back to my physical form. Please help me.
Sincerely,
Pretty much a god now.

just hit yourself really hard with a shovel


investigate why app doesn't respond on Sony when turned on riding mode and phone is not touched

already done as task null pointer exception.


Allow interaction with tooltip content

One of the requirements for the ClinVar track is showing a link to NCBI's website in a tooltip shown when hovering over a variant in the track.
Currently, tooltips are immediately removed when the mouse leaves the tooltip's anchor element. Thus, any link in a tooltip would be impossible to click because moving the mouse over the link would remove the tooltip and with it, the link.
This change keeps the tooltip visible while the mouse is over it. This allows putting interactive elements (such as links) in tooltips and allows users to select text shown in tooltips.

Rebased to resolve conflicts.


Use FromIterator for conversions

Several collection conversions expected the SymbolicByte  to be held in a Vec, but there was no real reason for this expectation. This changes the conversions from From<Vec<...>> to FromIterator<...>. The calling code that current holds a Vec then calls with into_iter().collect() instead of .into().
This opens up the code to being able to use different collections instead of being beholden to Vec due to the convenient conversion routines.

This also replaced a conversion from a Vec<u8> into an iterator of LittleEndian<u8>. This is a new type introduced to ensure that the caller using concrete bytes knows the data must be in little-endian format. This is to prevent mistakes like 100u64.to_be_bytes().into_iter().collect::<SymbolicBitVec>()


Move Public API behind labs flag

closes #5941

added UI to labs page
added method to determine if full authentication is required
updated public_api tests to enable public api first

Rebased & Updated.

:+1: Ember bits LGTM


Update unit-testing-with-nunit.md

Supported by https://github.com/dotnet/samples/pull/1690
Fixes #15623

@mairaw, Samples PR is merged. This is ready for review.

Ping, @mairaw

Thanks for the ping @Youssef1313.

Let me try rebuilding this. Want to confirm what I'm seeing is just outdated or bad references.

Humm, I find it a bit weird that now the sample looks incomplete because we're trying to hide the additional tests. @BillWagner what do you think?
https://review.docs.microsoft.com/en-us/dotnet/core/testing/unit-testing-with-nunit?branch=pr-en-us-15628#creating-the-first-test

@mairaw, Just to make sure, you're talking about adding the following comment under the test in the sample ?:
        /*
        More tests
        */

@mairaw @Youssef1313 I agree with Maira that the first sample looks confusing because it's not a complete class.  It's taken from this snippet.
I've started adding a new file with examples representing code that is between the starter code and final code so I can include snippets, but still have complete sample code. An example is here
Then, those examples are extended with more code before becoming part of the "final" example.
We can merge this, but I'd like to address the sample code promptly.

@mairaw, I missed this one. What exactly needs to be done to the sample ?

@Youssef1313 Sorry, I missed your question.  I'd update the sample as I mentioned in https://github.com/dotnet/docs/pull/15628#issuecomment-557139770


Covert &[i16] to &[u8]

I have audio data in &[i16], but process_bytes accepts only &[u8] (appeared after upgrading from 2.0.1 to 3.0.1)

Now I have replaced it to process_samples(data.to_vec()) but now it don't work

Sorry for the late reply, yes the process_samples method is what you need to use when you have the audio data already decoded as numbers.
If you are using int 16 samples you also need to set the config to:
  config.fmt.sample_rate = ...;
  config.fmt.sample_format = SampleFormat::I16;
  config.fmt.channels = ...;

And the size of the chunks provided to the process_samples method should be match the return of the rustpotter.get_samples_per_frame() if not they are ignored.
I think that is all you need to take into account.

Sorry for the late reply, yes the process_samples method is what you need to use when you have the audio data already decoded as numbers.
If you are using int 16 samples you also need to set the config to:
  config.fmt.sample_rate = ...;
  config.fmt.sample_format = SampleFormat::I16;
  config.fmt.channels = ...;

And the size of the chunks provided to the process_samples method should be match the return of the rustpotter.get_samples_per_frame() if not they are ignored.
I think that is all you need to take into account.

I have done as you wrote, but it still doesn't recognize anything

There is my config:

There is my buffer:

I have no clue what can be wrong. You can try to verify if you are correctly feeding it by using the "record" feature and setting a low threshold, like 0.01. Or trying to create a wav file using hound as rustpotter does.
Also I suggest you to disable the audio filter until you get it to work.
listener:: rustpotter:: get_samples();

That is not the library method.

I have no clue what can be wrong. You can try to verify if you are correctly feeding it by using the "record" feature and setting a low threshold, like 0.01. Or trying to create a wav file using hound as rustpotter does.
Also I suggest you to disable the audio filter until you get it to work.
listener:: rustpotter:: get_samples();

That is not the library method.

It is my function

And I can't see any files or even folder that i specified in record_path

The record folder need to exists and be writable.
But if you don get any detections after lowering the threshold it will no record, it just takes records on partial detections.

I got many short WAVs with strange flicking sound

My detections in rustpotter-cli:

Works correctly

I have taken source from another project and just upgraded rustpotter from 2.0.1 to 3.0.1, in the previous version all was working correctly

I have taken source from another project and just upgraded rustpotter from 2.0.1 to 3.0.1, in the previous version all was working correctly

If you want to send me the code diffs, maybe there is something I haven't got correctly.

I have taken source from another project and just upgraded rustpotter from 2.0.1 to 3.0.1, in the previous version all was working correctly

If you want to send me the code diffs, maybe there is something I haven't got correctly, until now I haven't found any problems migrating the things I was using to the v3, but maybe I'm missing something.

Ok, cargo.toml:
rustpotter = "2.0.0"

to
rustpotter = { git = "https://github.com/GiviMAD/rustpotter", features = ["record"] }

Rustpotter config:
pub const RUSTPOTTER_DEFAULT_CONFIG: Lazy<RustpotterConfig> = Lazy::new(|| {
    RustpotterConfig {
        fmt: WavFmt::default(),
        detector: DetectorConfig {
            avg_threshold: 0.,
            threshold: 0.5,
            min_scores: 15,
            score_mode: ScoreMode::Average,
            comparator_band_size: 5,
            comparator_ref: 0.22
        },
        filters: FiltersConfig {
            gain_normalizer: GainNormalizationConfig {
                enabled: true,
                gain_ref: None,
                min_gain: 0.7,
                max_gain: 1.0,
            },
            band_pass: BandPassConfig {
                enabled: true,
                low_cutoff: 80.,
                high_cutoff: 400.,
            }
        }
    }
});

to
pub const RUSTPOTTER_DEFAULT_CONFIG: Lazy<RustpotterConfig> = Lazy::new(|| {
    RustpotterConfig {
        fmt: AudioFmt::default(),
        detector: DetectorConfig {
            avg_threshold: 0.,
            threshold: 0.5,
            min_scores: 15,
            score_mode: ScoreMode::Average,
            eager: false,
            band_size: 5,
            score_ref: 0.22,
            vad_mode: None,
            record_path: Some(String::from("./recs")),
        },
        filters: FiltersConfig {
            gain_normalizer: GainNormalizationConfig {
                enabled: true,
                gain_ref: None,
                min_gain: 0.7,
                max_gain: 1.0,
            },
            band_pass: BandPassConfig {
                enabled: true,
                low_cutoff: 80.,
                high_cutoff: 400.,
            }
        }
    }
});

Rustpotter init:
pub fn init() -> Result<(), ()> {
    let rustpotter_config = config::RUSTPOTTER_DEFAULT_CONFIG;

    // create rustpotter instance
    match Rustpotter::new(&rustpotter_config) {
        Ok(mut rinstance) => {
            // success
            // wake word files list
            // @TODO. Make it configurable via GUI for custom user voice.
            let rustpotter_wake_word_files: [&str; 5] = [
                "rustpotter/jarvis-default.rpw",
                "rustpotter/jarvis-community-1.rpw",
                "rustpotter/jarvis-community-2.rpw",
                "rustpotter/jarvis-community-3.rpw",
                "rustpotter/jarvis-community-4.rpw",
                // "rustpotter/jarvis-community-5.rpw",
            ];

            // load wake word files
            for rpw in rustpotter_wake_word_files {
                rinstance.add_wakeword_from_file(rpw).unwrap();
            }

            // store
            RUSTPOTTER.set(Mutex::new(rinstance));
        },
        Err(msg) => {
            error!("Rustpotter failed to initialize.\nError details: {}", msg);

            return Err(());
        }
    }

    Ok(())
}

to
pub fn init() -> Result<(), ()> {
    let rustpotter_config = config::RUSTPOTTER_DEFAULT_CONFIG;

    // create rustpotter instance
    match Rustpotter::new(&rustpotter_config) {
        Ok(mut rinstance) => {
            // success
            // wake word files list
            rinstance.add_wakeword_from_file("first", "rustpotter/first.rpw").unwrap();
            rinstance.add_wakeword_from_file("second", "rustpotter/second.rpw").unwrap();
            rinstance.add_wakeword_from_file("third", "rustpotter/third.rpw").unwrap();

            // store
            RUSTPOTTER.set(Mutex::new(rinstance));
        },
        Err(msg) => {
            error!("Rustpotter failed to initialize.\nError details: {}", msg);

            return Err(());
        }
    }

    Ok(())
}

All the code took from this repo

Well I see several problems there, the audio format was not correctly configured.
At least it should be (this assumes you are using 16000hz, single channel audio).
        fmt: AudioFmt {
            ..Default::default(),
            sample_format: rustpotter::SampleFormat::I16,
        },

Also the frame size should be correctly initialized (but I assume you already fixed that as you got it to record), or you can use some buffering solution like the one implemented in the rustpotter-cli (because I encounter problems setting the clap buffer size to the required value in some platforms, maybe already fixed).

I was meaning this:
...
 buffer.extend_from_slice(data);
    while buffer.len() >= rustpotter_samples_per_frame {
        let detection = rustpotter.process_samples(
            buffer
                .drain(0..rustpotter_samples_per_frame)
                .as_slice()
                .into(),
        );
        print_detection(
            &*rustpotter,
            detection,
            partial_detection_counter,
            debug,
            debug_gain,
            get_time_string,
        );
    }
 ...

It's probably not the most efficient solution, there I'm pushing the audio data at end of a vector and then draining it until the data on it is less that the required chuck size, the buffer should be declared on a parent scope so it's reused between function calls as you do with the rustpotter instance. I think it can fit there so you don't need to change the general frame size.

Omg, I have recreated the project and just edited what I wrote above and it worked... I think I broke sth while editing code last time

Omg, I have recreated the project and just edited what I wrote above and it worked... I think I broke sth while editing code last time

Great to know you managed to make it work.
I encourage you to try to create a trained wakeword model to replace the v2 files you are currently used, it should provide a better functionality than the now called "wakeword references". I have one created with around 2000 samples (200 records of the wakeword + 1800 noise and silence records) and on my experience it work far better, over all in presence of small noises.
Best regards!


Support enabling concurrency

:wave:
This enables users to easily enable concurrency via their values.yaml.
(I literally just signed the CLA minutes ago, so it definitely hasn't been processed yet.)

Cool! Thanks @mmalecki for the contribution and welcome to the openwhisk community.

Thanks for the welcome, and the merge!


By default Ruby gem version is beta even when there is a stable release

Are you experiencing an issue with...
shields.io
🐞 Description
There is a gem: https://rubygems.org/gems/filewatcher
As you can see, it had a few beta-versions (of 2.0).
By default, gem (or Bundler) doesn't recognize them (until specific lock version).
But… there is 2.0.0 stable release. And it's newer, and it's stable.
But the badge still "dangerous" about beta-versions: https://img.shields.io/gem/v/filewatcher?include_prereleases&style=flat-square

Now I see there is include_prereleases param, but I believe it should count released versions.
🔗 Link to the badge
https://img.shields.io/gem/v/filewatcher?include_prereleases&style=flat-square
💡 Possible Solution
Reject any .beta, .rc, etc. versions if there is a stable version with the same digits.

This is happening because we're attempting to use semver sorting, which assumes the pre-release identifier is separated from the main part of the version number by a -, rather than a .. I've opened a PR to fix this at https://github.com/badges/shields/pull/8434

This is happening because we're attempting to use semver sorting, which assumes the pre-release identifier is separated from the main part of the version number by a -, rather than a .. I've opened a PR to fix this at #8434

Thank you, I didn't know about this Semver detail.
And yeah, as you have found, RubyGems suggest only dots. I guess, - will break them, but didn't check.


chore(master): release 1.12.1

:robot: I have created a release beep boop
1.12.1 (2024-06-08)
Bug Fixes

remove-signups: fix query on finding existing signup (#341) (a52e05f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ssilve1989/ulti-project/releases/tag/v1.12.1 :sunflower:


crypto:rand_uniform/2 is deprecated

crypto:rand_uniform/2 is deprecated and produces a warning. I think we should treat warning as errors. Is there some legitimate reason deprecated function has to be used?
Code warning introduced by @akorosmezey, please comment on that.
Build log:
apps/aecore/src/pow_sha256.erl:111: Warning: crypto:rand_uniform/2 is deprecated and will be removed in a future release; use rand:uniform/1

what is the new function? @cytadela8 @akorosmezey ? Please refactor to get rid of the warning and use the new approach

@sennui I think we should also add a check to travis.

From crypto 4.0 release notes:
Deprecate crypto:rand_uniform/2 as it is not cryptographically strong
We should change to rand:uniform. For future production ready code we will need a cryptographically strong randomness in pow, but for tests anything randomish is good.


strings package fails to install

I'm trying to install the strings package using scoop install strings on a freshly updated version of Scoop running on Windows 10. I get this error:
C:\Users\wgillela
λ  scoop install strings
Installing 'strings' (2.53) [64bit]
Loading Strings.zip from cache
Checking hash of Strings.zip... ok.
Extracting... Error moving directory:
 -------------------------------------------------------------------------------    ROBOCOPY     ::     Robust File Copy for Windows
-------------------------------------------------------------------------------    Started : Monday, April 30, 2018 8:58:12 AM    Source : C:\Users\wgillela\scoop\apps\strings\2.53\_tmp\strings\      Dest :
C:\Users\wgillela\scoop\apps\strings\2.53\      Files : *.*            Options : *.* /S /E /DCOPY:DA /COPY:DAT /MOVE /R:1000000 /W:30   ------------------------------------------------------------------------------  2018/04/30 08:58:12
ERROR 2 (0x00000002) Accessing Source Directory C:\Users\wgillela\scoop\apps\strings\2.53\_tmp\strings\ The system cannot find the file specified.
At C:\Users\wgillela\scoop\apps\scoop\current\lib\core.ps1:249 char:9
+         throw "Error moving directory: `n$out"
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Error moving di...ile specified. :String) [], RuntimeException
    + FullyQualifiedErrorId : Error moving directory:
     -------------------------------------------------------------------------------    ROBOCOPY     ::     Robust File Copy for Windows                               ---------------------------------------------------------------------
   ----------    Started : Monday, April 30, 2018 8:58:12 AM    Source : C:\Users\wgillela\scoop\apps\strings\2.53\_tmp\strings\      Dest : C:\Users\wgillela\scoop\apps\strings\2.53\      Files : *.*               Options : *.* /S /E /DCOPY
  :DA /COPY:DAT /MOVE /R:1000000 /W:30   ------------------------------------------------------------------------------  2018/04/30 08:58:12 ERROR 2 (0x00000002) Accessing Source Directory C:\Users\wgillela\scoop\apps\strings\2.53\_tm
 p\strings\ The system cannot find the file specified.

Here's the contents of the install directory it's trying to access.
C:\Users\wgillela
λ  ls C:\Users\wgillela\scoop\apps\strings\2.53\_tmp

    Directory: C:\Users\wgillela\scoop\apps\strings\2.53\_tmp

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----         3/3/2016   9:44 PM           7490 Eula.txt
-a----         7/5/2016   6:33 PM         149152 strings.exe
-a----         7/5/2016   6:30 PM         164008 strings64.exe

Looking at the JSON for the Strings package, the extract_dir is set to "strings". Not sure if this is the culprit or what. I know nothing about how Scoop works internally other than what I can tease out based on its behavior.
I should also mention that though it looks as if the contents of the Strings.zip file are successfully extracted, they haven't been registered for use as a command yet because of the error this issue is reporting. I'm assuming that Scoop does some further processing of files before registering them as a command?
If I had to guess (I don't really know how to test this), I'd say that removing the extract_dir property in the strings.json repository would fix it? Again, I know nothing about how Scoop works internally. I stumbled across this issue while at work so I don't have time to dig into it currently. If you could direct me to a resource describing how to debug this or tell me how, I can do so later this afternoon.
Thanks in advance!

Thanks for the quick fix!


Code review

I have created a new project on flutter. I don't have issues but I need someone to make code review to my project?
Can anyone help ??

Hi @areejmayadeh
This platform is not meant for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this, you may also get some help if you post it on Stack Overflow. Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you

@TahaTesser Thank you


Add Average Normalized Levenshtein Similarity (ANLS)

ANLS metric takes two inputs references and predictions. ANLS outputs the average score.

#321

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

This implements the same metric as #413. Maybe we merge the two PRs, what do you think @MedAhmedKrichen @QuadV? I think the features of this PR are nice, maybe we could adapt them in #413? If you make a code suggestion @MedAhmedKrichen then you become a code contributor. wdyt?

Great suggestion! Merging the two PRs would definitely ensure consistency in our metric and could certainly enhance #413.


add annotations for className, superClassname and interfaceNames

There is a corresponding pull request for Daikon: https://github.com/codespecs/daikon/pull/435


feat: basic filters options added to Discover and Reports

Ticket
#20rfmyr
Summary
Adding basic filter options for both Discover and Reports pages
Test Plan
How are you testing the work you're submitting?

Codecov Report

Merging #171 (074d23a) into develop (c42d5af) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #171   +/-   ##
========================================
  Coverage    79.46%   79.46%
========================================
  Files           31       31
  Lines          823      823
  Branches       273      273
========================================
  Hits           654      654
  Misses         166      166
  Partials         3        3

Flag
Coverage Δ

unittest
79.46% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.