Install additional/required dependencies while installing github-cli

SEMVER Update Type:

[ ] Major
[ ] Minor
[x] Patch

Description:

Adding --yes flag in install.sh command to install all required/additional dependencies while installing github-cli
I faced this issue while install github-cli in one of my job.

Downloading the GitHub CLI from "https://github.com/cli/cli/releases/download/v2.40.1/gh_2.40.1_linux_amd64.deb"...
Installing the GitHub CLI...
+ apt install ./gh-cli.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'gh' instead of './gh-cli.deb'
The following additional packages will be installed:
  git git-man less libcbor0 liberror-perl libfido2-1 openssh-client patch
Suggested packages:
  gettext-base git-daemon-run | git-daemon-sysvinit git-doc git-el git-email
  git-gui gitk gitweb git-cvs git-mediawiki git-svn keychain libpam-ssh
  monkeysphere ssh-askpass ed diffutils-doc
The following NEW packages will be installed:
  gh git git-man less libcbor0 liberror-perl libfido2-1 openssh-client patch
0 upgraded, 9 newly installed, 0 to remove and 25 not upgraded.
Need to get 8653 kB/20.0 MB of archives.
After this operation, 86.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] Abort.
+ set +x
Something went wrong installing the GH CLI. Please try again or open an issue.

Exited with code exit status 1

Motivation:

Closes Issues:

https://github.com/CircleCI-Public/github-cli-orb/issues/51

Checklist:

[x] All new jobs, commands, executors, parameters have descriptions.
[x] Usage Example version numbers have been updated.
[x] Changelog has been updated.

Your orb has been published to the CircleCI Orb Registry.
You can view your published orb on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/github-cli?version=2.5.0


Revert "Virtio: Use Publish indices according to spec"

This reverts commit b3fd592cf883cd7b9ae3024255ca057f17295639.
Currently the event suppression mechanism implementation is buggy and not
implemented correctly by us, that commit reveals these flaws. Currently
we'll revert this commit until the event suppression is fully fixed.

CI fails in NDISTest 6.0 - [2 Machine] - 2c_Mini6RSSSendRecv (Multi-Group Win8+)


pinning to a known good version

would help users for example https://github.com/ageron/handson-ml/issues/305

Thanks @lvnilesh


used istio1.5.1,but no mixer

run command:
istioctl manifest apply --set profile=demo
then use sidecar ，but in kiali，there are not Data of service traffic
how to enable mixer or how to do this ?

1.5.1 does not need or use mixer for grafana and kiali to work.
There must be something else wrong.

I feel like this issue is better handled in user forums or in slack. Closing this issue now.


Memory spikes killing Prometheus

What did you do?
Prometheus restart due to wal folder size increase

What did you expect to see?
Prometheus shoudl clear the wal folder over a period of time and getting crash
What did you see instead? Under which circumstances?
 when WAL folder reaches > 4gb , container will restart or crash

Environment
Production

System information:
insert output of uname -srm here

Prometheus version:
insert output of prometheus --version here
Prometheus 2.21

Alertmanager version:
insert output of alertmanager --version here (if relevant to the issue)

Prometheus configuration file:

insert configuration here

Alertmanager configuration file:

insert configuration here (if relevant to the issue)

Logs:

insert Prometheus and Alertmanager logs relevant to the issue here

To solve this issue I am using below sidecar container script
Prerequisite:
The wal folder location should be accessed by sidecar container
 package main

       import (
       	"fmt"
       	"log"
       	"net/http"
       	"os"
       	"os/exec"
       	"strconv"
       	"strings"
       	"time"
       )

       func clear() {
       	folder := []string{"/data/wal", "/data/chunks_head"}
       	for i := 0; i < len(folder); i++ {
       		e := os.RemoveAll(folder[i])
       		fmt.Println(" Removed ", e)
       	}
       	for i := 0; i < len(folder); i++ {
       		err1 := os.MkdirAll(folder[i], os.FileMode(0777))
       		err := os.Chown(folder[i], 65534, 65534)
       		if err != nil || err1 != nil {
       			log.Println(err, err1)
       		}
       	}
       }
       func main() {
       	for {
       		time.Sleep(1 * time.Second)
       		out, err := exec.Command("du", "-sk", "/data/wal").Output()
       		if err == nil {
       			d := strings.Fields(string(out))[0]
       			f := strings.Replace(d, "K", "", 1)
       			if f1, e := strconv.Atoi(f); f1 > 4194304 && e == nil {
       				clear()

       			} else {
       				fmt.Println("Size is less "+d+" ==>  %q", (time.Now()))
       			}

       			url := "http://localhost:9090/graph"

       			req, _ := http.NewRequest("GET", url, nil)

       			res, _ := http.DefaultClient.Do(req)

                                    if res == nil {
            				            clear()
            			         }

       		} else {
       			fmt.Printf("Folder %q is not exists  ==>  %q"+"\n", ("/data/wal"), (time.Now()))
       		}

       	}

       }

Note: The above script clear the logs if the size is more then 4gb or if the wal folder corrupt

@praveensams16 the WAL files are automatically cleaned up every 2 hours and corrupt files are repaired or removed on startup. What is the exact issue that you are facing? Can you share the logs around the crash?

PS: Manually deleting the WAL files is not a good idea, you might face data loss on any restart.

Hi @codesome
Please find the logs below
ts=2022-02-01T01:17:34.902Z caller=main.go:444 level=info msg="Starting Prometheus" version="(version=2.31.0, branch=HEAD, revision=d4c83da6d252d4edfdbd639fb817ebdb8e9ab2e4)" ts=2022-02-01T01:17:34.902Z caller=main.go:449 level=info build_context="(go=go1.17.2, user=root@395d507f537a, date=20211102-10:28:54)" ts=2022-02-01T01:17:34.902Z caller=main.go:450 level=info host_details="(Linux 4.14.243-185.433.amzn2.x86_64 #1 SMP Mon Aug 9 05:55:52 UTC 2021 x86_64 prometheus-server-8478db6d78-944g7 (none))" ts=2022-02-01T01:17:34.902Z caller=main.go:451 level=info fd_limits="(soft=1048576, hard=1048576)" ts=2022-02-01T01:17:34.902Z caller=main.go:452 level=info vm_limits="(soft=unlimited, hard=unlimited)" ts=2022-02-01T01:17:34.907Z caller=web.go:542 level=info component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090 ts=2022-02-01T01:17:34.907Z caller=main.go:839 level=info msg="Starting TSDB ..." ts=2022-02-01T01:17:34.909Z caller=tls_config.go:195 level=info component=web msg="TLS is disabled." http2=false ts=2022-02-01T01:17:34.917Z caller=head.go:479 level=info component=tsdb msg="Replaying on-disk memory mappable chunks if any" ts=2022-02-01T01:17:35.119Z caller=head.go:513 level=info component=tsdb msg="On-disk memory mappable chunks replay completed" duration=201.587779ms ts=2022-02-01T01:17:35.119Z caller=head.go:519 level=info component=tsdb msg="Replaying WAL, this may take a while" ts=2022-02-01T01:18:03.261Z caller=head_wal.go:360 level=warn component=tsdb msg="Unknown series references" samples=3774 exemplars=0 ts=2022-02-01T01:18:03.261Z caller=head.go:555 level=info component=tsdb msg="WAL checkpoint loaded" ts=2022-02-01T01:18:03.263Z caller=head.go:590 level=info component=tsdb msg="WAL segment loaded" segment=614 maxSegment=621 ts=2022-02-01T01:18:03.266Z caller=head.go:590 level=info component=tsdb msg="WAL segment loaded" segment=615 maxSegment=621 ts=2022-02-01T01:18:03.271Z caller=head.go:590 level=info component=tsdb msg="WAL segment loaded" segment=616 maxSegment=621 ts=2022-02-01T01:18:03.275Z caller=head.go:590 level=info component=tsdb msg="WAL segment loaded" segment=617 maxSegment=621 ts=2022-02-01T01:18:03.278Z caller=head.go:590 level=info component=tsdb msg="WAL segment loaded" segment=618 maxSegment=621 ts=2022-02-01T01:18:03.282Z caller=head.go:590 level=info component=tsdb msg="WAL segment loaded" segment=619 maxSegment=621 ts=2022-02-01T01:18:03.662Z caller=head.go:590 level=info component=tsdb msg="WAL segment loaded" segment=620 maxSegment=621 ts=2022-02-01T01:18:03.662Z caller=head.go:590 level=info component=tsdb msg="WAL segment loaded" segment=621 maxSegment=621 ts=2022-02-01T01:18:03.662Z caller=head.go:596 level=info component=tsdb msg="WAL replay completed" checkpoint_replay_duration=28.142507098s wal_replay_duration=400.604107ms total_replay_duration=28.744749931s ts=2022-02-01T01:18:11.811Z caller=main.go:866 level=info fs_type=EXT4_SUPER_MAGIC ts=2022-02-01T01:18:11.811Z caller=main.go:869 level=info msg="TSDB started" ts=2022-02-01T01:18:11.811Z caller=main.go:996 level=info msg="Loading configuration file" filename=/etc/config/prometheus.yml ts=2022-02-01T01:18:11.816Z caller=kubernetes.go:284 level=info component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config" ts=2022-02-01T01:18:11.836Z caller=kubernetes.go:284 level=info component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config" ts=2022-02-01T01:18:11.836Z caller=kubernetes.go:284 level=info component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config" ts=2022-02-01T01:18:11.837Z caller=kubernetes.go:284 level=info component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config" ts=2022-02-01T01:18:11.852Z caller=main.go:1033 level=info msg="Completed loading of configuration file" filename=/etc/config/prometheus.yml totalDuration=41.035182ms db_storage=1.048µs remote_storage=1.462µs web_handler=372ns query_engine=927ns scrape=2.080747ms scrape_sd=20.97451ms notify=26.125µs notify_sd=11.519µs rules=14.991234ms ts=2022-02-01T01:18:11.852Z caller=main.go:811 level=info msg="Server is ready to receive web requests." ts=2022-02-01T01:18:19.837Z caller=compact.go:518 level=info component=tsdb msg="write block" mint=1643666400107 maxt=1643673600000 ulid=01FTSDRQ9389EBTFAD7F91V4YD duration=6.554784618s ts=2022-02-01T01:18:19.855Z caller=db.go:1293 level=info component=tsdb msg="Deleting obsolete block" block=01FTSDRQ9389EBTFAD7F91V4YD ts=2022-02-01T01:18:20.411Z caller=head.go:803 level=info component=tsdb msg="Head GC completed" duration=556.056078ms ts=2022-02-01T01:18:20.411Z caller=checkpoint.go:97 level=info component=tsdb msg="Creating checkpoint" from_segment=614 to_segment=618 mint=1643673600000 ts=2022-02-01T01:18:41.380Z caller=head.go:972 level=info component=tsdb msg="WAL checkpoint complete" first=614 last=618 duration=20.968527514s
The pods getting restarts due to memory spike and eviction. we see the spike when the wal folder size reach 2 GB

we see the spike when the wal folder size reach 2 GB

restarts due to memory spike

Indicates that you need more memory provisioned to the Prometheus and has nothing to do with the WAL. WAL reaching 2GB during spike might just be the side effect of some background task that runs periodically that is taking a little more memory.
How bad is the spike? Do you have any dashboard to show the spike?

Hi Venkat ,
The node limitations are 16 gb , but you can see spike go beyond 19GB

[image: image.png]
On Wed, Feb 9, 2022 at 5:11 PM Ganesh Vernekar @.***>
wrote:

we see the spike when the wal folder size reach 2 GB
restarts due to memory spike
Indicates that you need more memory provisioned to the Prometheus and has
nothing to do with the WAL. WAL reaching 2GB during spike might just be the
side effect of some background task that runs periodically that is taking a
little more memory.
How bad is the spike? Do you have any dashboard to show the spike?
—
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/issues/10211#issuecomment-1033745839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADO6FZ2IKY7CWCMSTX4BY23U2JRYTANCNFSM5M2FSPFQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Thanks--
Praveen Sam

Please find the spike in the snap

Hello from the bug-scrub! More information was requested two years ago and not supplied, so we will close this issue.


crash when the mark all response is received whereas the user switches to another fragment

Steps to reproduce

Select "Mark all as read" on the home menu with many unread messages and on a slow network
Switch to another home tab
----> the app used to crash when the response was received

https://github.com/matrix-org/riot-android-rageshakes/issues/515
https://github.com/matrix-org/riot-android-rageshakes/issues/519

Fixed on develop.


Add raw dump to accelerate the save process

VizTracer can save json file directly from the C tracer now. There won't be any file_info, but all the trace data is there. This is helpful for cmdline usage to avoid duplicated load/dump procedure

Codecov Report

Merging #186 (7b89f1b) into master (e3baad3) will decrease coverage by 1.13%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##            master     #186      +/-   ##
===========================================
- Coverage   100.00%   98.86%   -1.14%
===========================================
  Files           22       22
  Lines         2361     2370       +9
===========================================
- Hits          2361     2343      -18
- Misses           0       27      +27

Impacted Files
Coverage Δ

src/viztracer/main.py
99.07% <100.00%> (-0.93%)
:arrow_down:

src/viztracer/report_builder.py
95.62% <100.00%> (-4.38%)
:arrow_down:

src/viztracer/tracer.py
100.00% <100.00%> (ø)

src/viztracer/viztracer.py
95.67% <100.00%> (-4.33%)
:arrow_down:

src/viztracer/patch.py
95.69% <0.00%> (-4.31%)
:arrow_down:

src/viztracer/simulator.py
96.77% <0.00%> (-3.23%)
:arrow_down:

src/viztracer/prog_snapshot.py
99.44% <0.00%> (-0.56%)
:arrow_down:

Continue to review full report at Codecov.

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


Enum type deduction fails when checked in condition

enum language {
    english,
    french,
    german
}

function getter(): language | undefined {
    return undefined;
}

let l: language | undefined;
while ((l = getter()) && l !== language.english) {
}

Link for live repro
Expected: Code compiles fine.
Actual: Error: 'Operator '===' cannot be applied to types 'language.english and language.french and language.german.'
Version: latest npm 2.5.3 and current playground

The issue is that language.english has the numeric value 0, which is falsy and therefore never makes it past the && operator. It works if you change your enum to:
enum language {
    english = 1,
    french,
    german
}


soc/intel_adsp: Update cavs-fw.py loader for cAVS 2.5 devices

Compatibility work (actually more or less a rewrite of large chunks)
to get this working on a Tiger Lake cAVS 2.5 device.
Signed-off-by: Andy Ross<EMAIL_ADDRESS>

FWIW: to I'm sure no one's surprise this has broken cavs15 loading somewhere.  That's not a huge deal as for that platform we have a working fallback in the older scripting (which I think Zephyr QA is still using) and it's no longer a focus platform for Zephyr development (we already made all the tests pass there and just need to fix regressions).  But it's surely fixable.

That's not a huge deal as for that platform we have a working fallback in the older scripting (which I think Zephyr QA is still using) and it's no longer a focus platform for Zephyr development (we already made all the tests pass there and just need to fix regressions). But it's surely fixable.

Can we please keep this working for 1.5 by either creating a different script for 2.5 and leaving 1.5 intact or by providing compatibility in the script itself?

That's not a huge deal as for that platform we have a working fallback in the older scripting (which I think Zephyr QA is still using) and it's no longer a focus platform for Zephyr development (we already made all the tests pass there and just need to fix regressions). But it's surely fixable.

Can we please keep this working for 1.5 by either creating a different script for 2.5 and leaving 1.5 intact or by providing compatibility in the script itself?

Ack, this needs to work for all as it's needed for the removal of xtos in SOF (alongside BYT and BDW SoC code)..

Yeah, agreed.  I've split the two scripts into separate files for now (again, there's no good reason we can't have one, I just don't have time and this stuff is really annoying to deal with -- changing one thing breaks stuff in weird ways).
Chased down the timer interrupt bug, that's included here, along with an SMP disable that unblocks testing while I sort out bringing the second CPU up (status: working as far as the ADSPCS and PWRSTS registers are concerned -- the cores seem to be alive and powered, but they aren't receiving the IDC interrupt to kick them out of the ROM and into our code, currently digging around in the IDC and interrupt masking layers and comparing to SOF trying to figure out what's broken).

Will update.  Unfortunately it's gone and broken on my board and I need to untangle what I did...

Close this.  All the changes got merged into the more recent MP pull request at #37647

Oops, actually close this.


core included modules not correct on node 6.9.0

It seems the algo for core is not working as expected on node 6.9.0:
test.js:
const core = require('resolve/lib/core.js');
console.log('Current version %s', process.versions.node);
console.log('path: %s', core['path']);
console.log('v8: %s', core['v8']);
console.log('process: %s', core['process']);

Output:
node test.js
Current version 6.9.0
path: true
v8: undefined
process: undefined

Which version of resolve do you have installed?

Good catch, closing. Issue is eslint isn't using the latest version: https://github.com/benmosher/eslint-plugin-import/blob/master/resolvers/node/package.json#L29


feat: delete organization and add user to organization

Description
delete organization and add user to organization
Related Issue (Link to issue ticket)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[] I have added tests to cover my changes.
[] All new and existing tests passed.

i have create another PR for each feature, you close this one


add log entry if proxies are being used

https://github.com/prebuild/prebuild-install/issues/51
@ralphtheninja Something like this?

Exactly like that! :)

2.4.1


short_description not being saved or returned in profile

When short_description is sent to POST profile, it is not returned by GET profile.

If I remember right I didn't return it there because it wasn't used on the user page. Only on store listings.

It needs to be returned so we can show it on the settings page, otherwise it's blank in the form.


Fix number of files

Fix number of files not batch size.

https://www.biostars.org/p/13270/

Using function to provide input files. Let's see how this plays out.

resolved by #2b920232


CloudFormation Stack Failure: Issues with CustomCopyImagesLambdaFunction and CloudFront Resources

I am currently facing an issue while trying to deploy the CloudFormation stack associated with the Retail Demo Store. The stack fails during the creation of the resource CustomCopyImagesLambdaFunction and CloudFront. Below are the details:
Issues Encountered:
CustomCopyImagesLambdaFunction:
The resource fails to create, and I am unable to locate any logs or details that explain the root cause of the failure.
I have checked CloudWatch logs, the IAM role associated with the function, and the permissions. However, I cannot find anything that points to the exact issue.
CloudFront:
The stack also fails during the CloudFront resource creation.
I have ensured that the IAM user has sufficient permissions, including cloudfront:CreateDistribution and cloudfront:UpdateDistribution, but the stack still fails.
Steps Taken:
I have reviewed the CloudFormation events and resources for detailed logs but could not locate the root cause.
Verified permissions for both the Lambda function and CloudFront distribution creation.
I attempted to redeploy the stack multiple times, but the same issue persists.
Could you please assist in identifying what might be causing these failures? I would appreciate any insights or guidance on resolving these issues so that the deployment can proceed successfully.
Thank you for your attention to this matter. I look forward to your response.

Hi,
Can you look at the cloudwatch logs of the Copy Images Lambda function?
Have you changed the parameter SourceImagesPackage to a specific URL?


Revert hive pre-upgrade script commits in PR #1886

What changes were proposed in this pull request?
Reverts commits made in PR #1886

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3345/
Test FAILed.
Test FAILured.


TypeError: unsupported operand type(s) for *: 'FieldInfo' and 'FieldInfo'

Update: See here for the stunning conclusion to the saga.
Cog Info:
$ cog --version
cog version 0.6.1 (built 2022-12-15T20:25:16Z)
Branch Info:
commit 38510524cf4f3dc679e5945ebb52feb40d52c1a9
Steps to Reproduce:

Clone the cog-stable-diffusion repo.
Download the models with the download-models script.
Run a build with cog build -t cog-stable-diffusion.
Hit the /prediction endpoint with a prompt and, optionally, a width. (See  below for sample.)

Sample requests:
requests.post(DIFFUSION_ENDPOINT, json={"prompt": "An oil painting of a sentient potato wearing brilliant silver armor, 4k, high quality, trending", "width": 512, "height": 512, "num_inference_steps": 10})

requests.post(DIFFUSION_ENDPOINT, headers={"content-type": "application/json"}, json={"prompt": "An oil painting of a sentient potato wearing brilliant silver armor, 4k, high quality, trending", "num_inference_steps": 10})

Expected Behavior:
The container will spin for a while and spit back an image based on the prompt.
Observed Behavior:
The endpoint returns an exception:
INFO:     <IP_ADDRESS>:63320 - "POST /predictions HTTP/1.1" 200 OK
Using seed: description='Random seed. Leave blank to randomize the seed' extra={'choices': None}
Traceback (most recent call last):
File "/root/.pyenv/versions/3.10.9/lib/python3.10/site-packages/cog/server/worker.py", line 209, in _predict
result = self._predictor.predict(**payload)
File "/root/.pyenv/versions/3.10.9/lib/python3.10/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/src/predict.py", line 104, in predict
if width * height > 786432:
TypeError: unsupported operand type(s) for *: 'FieldInfo' and 'FieldInfo'
INFO:     <IP_ADDRESS>:63392 - "POST /predictions HTTP/1.1" 200 OK

Reproducibility:
~50% of the time.
The line in the code:
https://github.com/replicate/cog-stable-diffusion/blob/main/predict.py#L99
        if width * height > 786432:
            raise ValueError(
                "Maximum size is 1024x768 or 768x1024 pixels, because of memory limits. Please select a lower width or height."
            )

This looks completely innocuous.  width and height are both integers and are assigned the value of 'Input', which is a subclass of FieldInfo, according to FastAPI/Pydantic.

I've attempted to cast the width and height to integers explicitly to see if there's perhaps some type coercion that's getting skipped before the multiply, but then I see, TypeError: int() argument must be a string, a bytes-like object or a real number, not 'FieldInfo'.

we should probably move this bug to replicate/cog with this feedback

Closing and moving to replicate/cog.


moment week number is not correct

I’m trying to calculate the week number from the epoch time. So the epoch time is this<PHONE_NUMBER>000(15th October 2019). Now when I change this epoch date to start of the week
using this code
moment(1571097600000.startOf("week").unix()*1000
what I get is this<PHONE_NUMBER>000(13th October 2019). But when I format this date the week number is incorrect. This is how I’m formatting
moment.(1570906800000).format("W, YYYY")
The value that I get is 41 but actually the week number is 42. Any idea what is going on over here
Here is the code that I'm using
console.log(moment(1571097600000).startOf("week").unix()*1000)
console.log(moment(1571097600000).startOf("week").format("W, YYYY"))

Desktop (please complete the following information):

OS: Max
Browser: Chrome
Version: 80.0.3

Moment-specific environment

The time zone setting of the machine the code is running on
The time and date at which the code was run
Other libraries in use (TypeScript, Immutable.js, etc)

Please run the following code in your environment and include the output:
1. "Mon Apr 13 2020 22:31:45 GMT+0500 (Pakistan Standard Time)"
2. "4/13/2020, 10:31:45 PM"
3. -300
4. "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.163 Safari/537.36"
5. "2.24.0"

I just found the issue. Rather than formatting the date to local time week number I was trying to format it to isoWeek. W is for isoWeek whereas w is for local.


1.3.9 not init table "ke_consumer_bscreen"

build master branch,and run. logs show "msg is Table 'ke.ke_consumer_bscreen' doesn't exist".
connect mysql

release kafka egale v1.3.9, and fixed it.


num_relation mismatches in message_and_aggregate()

I would like to use my custom data https://raw.githubusercontent.com/goga0001/graph/main/data.csv
I prepared the data as CSV file and followed the implementation of existing datasets:
import os
from torchdrug import data, utils
from torchdrug.core import Registry as R
from collections import defaultdict
from torch.utils import data as torch_data
from torchdrug import data
from torchdrug.utils import doc

@R.register("datasets.Flavonoid2")
@doc.copy_args(data.MoleculeDataset.load_csv, ignore=("smiles_field", "target_fields"))
class Flavonoid2(data.MoleculeDataset):
    """
    Subset of Flavonoid compound database for virtual screening.

    Statistics:
        - #Molecule:  4806
        - #Regression task: 2

    Parameters:
        path (str): path to store the dataset
        verbose (int, optional): output verbose level
        **kwargs
    """

    csv_file = "/content/torchdrug/torchdrug/datasets/data.csv"
    target_fields = ["logP","qed"]

    def __init__(self, path, verbose=1, **kwargs):
        self.load_csv(self.csv_file, smiles_field="smiles", target_fields=self.target_fields,
                      verbose=verbose, **kwargs)

Molecules were constructed from smiles but I get assertion error:
from torch import nn, optim
optimizer = optim.Adam(task.parameters(), lr = 1e-3)
solver = core.Engine(task, dataset, None, None, optimizer,
                     gpus=(0,), batch_size=128, log_interval=10)

solver.train(num_epoch=1)
solver.save("graphaf_flavonoid_1epoch.pkl")

AssertionError                            Traceback (most recent call last)
[<ipython-input-23-a6a027c50b11>](https://localhost:8080/#) in <module>
      4                      gpus=(0,), batch_size=128, log_interval=10)
      5
----> 6 solver.train(num_epoch=1)
      7 solver.save("graphaf_flavonoid_1epoch.pkl")

10 frames
[/content/torchdrug/torchdrug/layers/conv.py](https://localhost:8080/#) in message_and_aggregate(self, graph, input)
    414
    415     def message_and_aggregate(self, graph, input):
--> 416         assert graph.num_relation == self.num_relation
    417
    418         node_in, node_out, relation = graph.edge_list.t()

AssertionError:

Thank you! Looking forward to your reply!

Hi! Your code for custom dataset is right.
The problem is that you have different number of relations for your dataset and your model. This is typically caused by the kekulize option of the dataset. One safe way is to define the number of relations for your model based on dataset.num_bond_type. For GraphAF, I would recommend to use kekulize=True.

Hello, thank you for your quick reply!
I actually used kekulize=True in this line of code but it still gives the same Assertion Error:
dataset = Flavonoid3("/content/torchdrug/torchdrug/datasets/data.csv", kekulize=True,                             atom_feature="symbol")

dataset.num_bond_type
2
model.layers[0].num_relation
2
dataset[0].num_relation
AttributeError: 'dict' object has no attribute 'num_relation'
dataset[0]
{'graph': Molecule(num_atom=22, num_bond=50),  'logP': -0.8174,  'qed': 0.565067144}

Maybe I can give a minimal repro example that you can run?

Maybe I can give a minimal repro example that you can run?

Yes please. What about dataset[0]["graph"].num_relation?

Here is the link to minimal repro:
https://github.com/goga0001/graph/blob/main/minimal repro.ipynb
dataset[0]["graph"].num_relation
3
Thanks again!


Bugfix: Make setPoster work on mobile devices with native controls

This fixes #2418.
If an mobile device is used and mediaelement is configured to use native
controls in this case, t.container is not defined. Therefore the
setPoster() method threw an error.
In that case now the poster attribute is used, which is the native way
of showing the poster image.

Coverage remained the same at 73.832% when pulling 7d4781beb57e14980d459b528e2accb1cd3811f4 on lucash:fix-ios-native-controls-setposter into be2e7e8ebf228d105083b82a305b47cb76d1ea3a on mediaelement:master.

@rafa8626
This potentially conflicts with #2312. As I wasn't able to reproduce that issue I was not able to make sure that it is not a problem. Regarding the comment in code, removing the attribute helps if you need to support iOS 3.x - maybe it is needed to suppress setting the attribute for that iOS version? I think using a poster image should not be avoided at all if an iOS device is used with native controls as current iOS versions seem to support it.

@lucash Thanks for your PR. At this point, we only support iOS 8 and and above, so the comment for that is invalid

I'll review your PR as soon as I can, unless you are gonna modify it based on your comment above. Let me know if it's ready to review. Thanks

Please review. As I'm not able to reproduce above issue I won't change anything.

PR merged. Thanks and please star the project to support it


Make Instructions

Make Word Document that has instructions on how to use our site/tool.
Make it nice/fancy
Make it into an image, it will be replacing the current placeholder

made into a modal


Update README.md

@sunidhichaudhary please resolve the conflict then I'll merge it. By the way, you could have done the Readme related changes in a single PR :)

Sure @Prakriti-nith  :100:


How to set the date format so that it doesn't change when importing the csv file to the dbever database column

Description
I have a problem importing csv data into DBeaver DBMS, when importing data, the date column changes from 2022-09-30 to 2022-09-29, what should I do to prevent this problem from recurring in my dbever, thanks
DBeaver Version
Community Edition 22.1.3
Operating System
mac.OS.Monterey 12.2.1
Database and driver

Database Name MySQL

Steps to reproduce
I have a problem importing csv data into DBeaver DBMS, when importing data, the date column changes from 2022-09-30 to 2022-09-29, what should I do to prevent this problem from recurring in my dbever, thanks
Additional context
No response

Hi, it looks similar to https://github.com/dbeaver/dbeaver/issues/16624, can you look at it?

thanks for the report
closed as a duplicate of #16624

Thanks Sir and Mrs. That very help me

Thanks for the questions


Support integer/timestamp/numeric fields

This could be a generalisation of #4.
Documents may have associated numeric values, the most common of which would be timestamps (e.g. blog posts made on a certain date).
Morsels only indexes texts, but these can be mapped to integer values through some configuration (e.g. parsing a datetime string with a specific format into a 64bit unix timestamp).
On the API side, there could be support for:

less than, greater than, in between operations (1 < x < 1000)
sorting results by integer fields instead of BM25

On the UI side,

before/after dropdowns specifically for date times could be supported. (e.g. Any time vs After Dec 20 2005)
a sort-by dropdown could be supported. (e.g. by relevance, X field or Y field)

In terms of priority, timestamp fields should come first. The use case for generic numeric fields in static site search may be less common.

https://github.com/ang-zeyu/infisearch/commit/4ee3f81b9feb21f0bf275dbbd0257ba85facbfff


Start-Process: Provide the ability to append when redirecting stdout/stderr streams to file

Include an option/directive for the 'Start-Process' cmdlet that allows the user to specify that stream output should be *appended to an existing output file when redirecting the stdout/stderr streams to file.
Currently, when using either the '-RedirectStandardOutput' or '-RedirectStandardError' parameters to specify output file paths for redirection of the standard streams to file, the behavior of 'Start-Process' is to create/overwrite if a specified file exists. There is no means to have the output appended to an existing file. This forces the user to come up with additional and, IMHO, seemingly unnecessary work-arounds in order to implement the append logic. This seems like something that could be relatively easily implemented at a lower level, and, quite frankly, seems like basic functionality that the cmdlet should already support.
This could be as simple as adding some kind of append specifier to each parameter:
# stdout files gets overwritten (default behavior), stderr file gets appended to ('>>' specifier)
Start-Process -RedirectStandardOutput='logfile.txt' -RedirectStandardError='>>errlog.txt'

Of course, this could be setup in a variety of ways and/or as the powershell devs see fit.
Justification:
There are a variety of cases where it would be useful to be able to have a complete output history of a child process' output, even when the same child process is created multiple times, or across multiple executions of the parent script/command. Having the ability to append output files directly from 'Start-Process' would increase its usefulness in this respect.

PowerShell utilizes Process class which has not such feature. You could discuss this in .Net runtime repository to enhance the class.

This is definitely something that is implemented in PowerShell. .NET gives you the ability to redirect stdout/stderr and exposes that redirection through a StreamReader. To achieve this functionality we would have to change how the FileStream is opened here https://github.com/PowerShell/PowerShell/blob/4c40ab11401ff2ca19ee1206b7654ed299f373e6/src/Microsoft.PowerShell.Commands.Management/commands/management/Process.cs#L2263.
All that needs to be done to implement this functionality is to either change the mode to FileMode.Append or set to FileMode.Open and seek the FileStream to the end.

@jborean93 You referenced temporary code for Unix. PowerShell does many workarounds which is now in .Net and could be removed.
I'd say the redirection is OS feature and .Net utilizes this.

It looks like as if, to the caller, System.Diagnostics.Process.StandardOutput and StandardError are simply read-only properties through which automatically created Stream instances reflecting the redirected output  (that on Unix these streams are apparently backed by a file looks like an implementation detail that isn't visible to the caller); alternatively, the output can be read via events.
To put it differently: sending that captured output to a user-chosen file  must already be functionality overlaid by PowerShell, so offering an opt-in way to append to such a file should be possible.

As for how pressing the need for this feature is (I'm not saying it wouldn't be useful):
Note that there's generally little reason to combine Start-Process with console applications (terminal applications that use stdout and stderr).

For synchronous invocation, invoke such applications directly, in which case  you can use >>

someutil >> out.log 2>> err.log

For asynchronous invocation, you can use a background job, which also allows you to use >> -

$job = someutil >> out.log 2>> err.log &

As an aside: Unfortunately, the job-info object currently doesn't reflect $LASTEXITCODE after termination - see  #5422
Unnecessary - and often limiting - use of Start-Process is a common problem; I've added for guidance to be added to the documentation https://github.com/MicrosoftDocs/PowerShell-Docs/issues/6239, which has further details.

I don't like an cryptic things in PowerShell language - it is hard for users to discover them. It is more preferable to have an additional switch or two self described name(s) like -AppendToOutput/-AppendToError.

Or maybe even a mode like -RedirectOutputMode Create/Append (same for Error). This could have the benefit of adding Store/Var support where -RedirectStandardOutput is the name of a variable to redirect the value to.

Targeting variables could be achieved via paths that use namespace variable notation, such as -RedirectStandardOutput variable:out, which has been suggested before in #5184; the same idea had come up earlier in the context of >: #4332, which would make for a nice generalization.
That leaves the aspect of how to ask for appending, and in the case at hand -Append would then be enough.
Note that you may also want to append to variables (add to an existing collection stored there), which we already support in the context of common parameters such as -OutVariable - and there we do already have the kind of non-obvious "mini-DSL" that @iSazonov  is trying to avoid: prefixing the variable name with + requests append functionality:
$null = Get-Date -ov out
$null = Get-Date 1970-01-01 -ov +out  # appends to existing $out variable
$out # outputs both dates

In the case of something like 2>variable:errs, where adding parameters isn't an option, we'd have no other choice than to use a similar approach: 2>+variable:errs

Or maybe even a mode like -RedirectOutputMode Create/Append (same for Error). This could have the benefit of adding Store/Var support where -RedirectStandardOutput is the name of a variable to redirect the value to.

The mode would be useful if we knew there would be more modes.
As for output to variables, since we already have this with OutVariable parameter in some cmdlets we should follow this here too for consistency.

we already have this with OutVariable parameter in some cmdlets

The common -OutVariable parameter as well as -ErrorVariable, as a common parameters, are present on all cmdlets and designed to display uniform behavior across all cmdlets.
They are implemented in the engine itself, and we cannot overlay that with cmdlet-specific functionality.
As in all cmdlets, these parameters capture what the cmdlet itself outputs to PowerShell's success / error streams, which in the case of Start-Process does not apply to  the native output streams (stdout, stderr) of the external process being launched, because - of necessity, given the asynchronous-by-default Start-Process behavior - these native streams aren't mapped onto their PowerShell equivalents, unlike in direct invocation. This lack of stream integration is the primary reason not to use Start-Process with console applications.
These two common parameters therefore aren't terribly useful with Start-Process, but they do work as advertised:

-OutVariable out captures whatever Start-Process itself emits to the pipeline in variable $foo, which only applies when -PassThru is also specified in order to pass out the process-info object describing the newly launched process.

ErrorVariable err captures the errors that Start-Process itself emits in variable $err, which is in effect limited to the inability to even create the process (e.g., Start-Process nosuch -ErrorVariable err) - though I've just realized that appears to be broken on Unix-like platforms.


sched: add day of week check to getActiveAlarms()

See also discussion in #1780:
When having multiple alarms on a single day a successive alarm can display a previous alarm that should not fire because of its day of week configuration.
Example, today is Monday, alarm configurations are
Alarm 23:10, S_TWTFS, REPEAT YES
Alarm 23:11, SMTWTFS, REPEAT YES
Expected: Only one alarm at 23:11
Actual: Two alarms at 23:11 because sched things the first one was missed due to the check for day of week is missing.
This PR adds a check for day of week in getActiveAlarms()

Just not 100% sure if the dow check should happen in the function getActiveAlarms() or in the calling of the function in sched.js.

Great - thanks!


buildbot: 3.9.2 -> 3.10.0

Changelog: https://github.com/buildbot/buildbot/releases/tag/v3.10.0
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

What is still missing to undraft this?

Was waiting for ofborg to pass. I haven't done any testing apart from the nixos test.

Deployed on https://buildbot.thalheim.io/


Collisions work in Play In Editor mode but not when using Launch or Packaging project

OS: Win64
Engine: 4.16.2
Project link: https://mega.nz/#!zdxw2DDQ!uHxHgButoB3K0LE59eLAOy5DOIwxlRJhh2bFJa4Bq7w

Drag a Simple Cube Actor and my Actor_Blueprint into the scene.
Play in editor, notice how the collisions work.
Launch, notice how the collisions no longer work.

Will be happy to provide any more details if needed :)

@Reyitgex Hey man! I have the same problem as you but I have found solution. You need to remove usage of preprocessor string
#if WITH_RUNTIME_PHYSX_COOKING constant within
https://github.com/Koderz/RuntimeMeshComponent/blob/master/Source/RuntimeMeshComponent/Private/RuntimeMeshComponent.cpp, line 1781

Hello,
All existing issues for RMCv2 are being closed as RMCv2 is no longer being supported.  RMCv3 is in beta here : https://github.com/Koderz/RuntimeMeshComponent/tree/Version3Dev
If you encounter this or any new issues in v3 please feel free to open a new issue!
Thanks!
-Koderz


Update of set filter rule with SMT arrays

[ ] ~Tests added for any new code~
[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[ ] ~Documentation added for any new functionality~
[ ] ~Entries added to ./unreleased/ for any new functionality~

This PR removes a redundant membership check in the set filter rule, as suggested by @konnov a while back.

Codecov Report

Merging #2057 (6592b3f) into main (af68343) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2057      +/-   ##
==========================================
- Coverage   77.75%   77.73%   -0.02%
==========================================
  Files         425      425
  Lines       12998    12996       -2
  Branches      580      585       +5
==========================================
- Hits        10106    10103       -3
- Misses       2892     2893       +1

Impacted Files
Coverage Δ

...rsyte/apalache/tla/bmcmt/rules/SetFilterRule.scala
90.47% <100.00%> (-0.44%)
:arrow_down:

...a/at/forsyte/apalache/tla/lir/TlaLevelFinder.scala
97.36% <0.00%> (-2.64%)
:arrow_down:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


feat(scanner): Enable stand-alone E2E tests

Description

Update the E2E test description to match the expected results for Scanner V4 (diff from previous Scanner V2 results can still be inspected by diff -du scanner/e2etests/testdata/*.json).
Update e2e make rules to build and execute E2E tests in a cluster.
Create a GitHub workflow that runs the tests in a minikube instance after image builds are completed successfully.
Updated the E2E test cases not to fill in empty values to compare but to log when expected packages are not found.
Add a DEBUG flag to print the whole Matcher Vuln Report when the tests fail.

You will notice the images stored in registry.redhat.io are failing. The reason is credentials: We are missing a secret to registry.redhat.io. Other failures are legit.
Checklist

[x] Investigated and inspected CI test results
[x] Unit test and regression tests added
[x] Evaluated and added CHANGELOG entry if required
[x] Determined and documented upgrade steps
[x] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
CI results.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

Seems like we are missing us.gcr.io/stackrox-ci/qa/apache/server:latest creds, too. We should just move this to quay

Pulling in @BradLugo, as suggested. Please review this and see if there is anything worth improving. Please remember that I want a mechanism right now to reproduce the standalone E2E tests -- or functional tests; I feel there is a better name for this, but I can't seem to find one right now.
BTW, I would be happy to if there is a better, cheaper, and faster way to do this over OCI. I'm just trying to move against the clock.

Ping @BradLugo and @RTann

I appreciate the method this PR setups up the infrastructure for e2e tests; in fact, I wanted to pitch something along the lines of using minikube/k3s for all of stackrox testing. The problem is that we ultimately need to test on OpenShift.
In my opinion, scanner should have two types of e2e tests: one testing suite using OpenShift(/Kubernetes) and another for standalone mode. The idea is that if there are any dependencies on stackrox components (central, sensor, etc.) or Kubernetes APIs, those should live in the OpenShift test suite alongside the rest of the stackrox e2e tests, and the standalone test suite should not be tested in a Kubernetes environment.
That being said, we're racing against the clock a bit right now, so unless there are any objects from the automation team (cc @stackrox/infra), this all seems fine to me.


Implemented more functionality according to AHM TCP Protocol V1.4

I added the following functionality to the module:

Distinguish Type of Device (AHM-64/AHM-32/AHM-16) in order to reduce traffic when using device other than AHM-64
Action "Increment/Decrement Level of Input"
Action "Increment/Decrement Level of Zone"
Action "Playback Track"
Action "Set Level of Input"
Action "Set Level of Zone"
Variables for Levels of Inputs and Zones

Also I made some changes to the code structure:

cleaned up code a bit and
tried resolving terminology confusion on the terms "input", "zone", "channel"
added separate file for constants that are related to the whole module
added separate file for helper functions that are related more to Companion than the module itself

All functionality has been tested using a brand-new AHM-32.
What is still missing:

Up version of the module
Upgrade Scripts for existing Configurations (I do not know if this is required, maybe can update and test what is broken?)
Testing with AHM-16 and AHM-64 (I have no access)

Anybody got time to review this and merge this pull request?
@bryce-seifert
@JeffreyDavidsz
thanks in advance!

@JonasArnold I can take a look and will get back to you!

@JonasArnold Just looking at the code, not actually testing yet, to answer your Q we will need upgrade scripts anywhere an action's ID is changed. So from a glance, any action affected by the change of id: 'inputChannel', to id: 'mute_number' will need it. We'll also need an upgrade to handle the new ahm_type config option, just to set a default value for pre-existing installations.

hi, when can we expect this update to come through? We would like to use some of these features too. Thanks!

This PR is waiting for changes to be made in order to properly upgrade the actions that were changed, so they don't break existing setups

Ah okay, so @JonasArnold has to make these changes? Thanks

@JonasArnold Just looking at the code, not actually testing yet, to answer your Q we will need upgrade scripts anywhere an action option's ID is changed. So from a glance, any action affected by the change of id: 'inputChannel', to id: 'mute_number' will need it. We'll also need an upgrade to handle the new ahm_type config option, just to set a default value for pre-existing installations.

I had a look at it. I have checked in a first version of the update script  #d22dc02. unfortunately the update of the actions does not work yet.
Unfortunately I have no way to debug it and also the console.logs from the update script do not show in the Companion UI. Can anyone help me with this?

@JonasArnold How can we help? Do you need acces to an AHM32 for testing purposes? We have one available at the moment.

@JonasArnold How can we help? Do you need acces to an AHM32 for testing purposes? We have one available at the moment.

I do have access to an AHM32 aswell. The issue is that I cannot get the update script to run, so I need somebody with more experience with bitfocus companion module development to help me out with the code or debugging it.
Unfortunatly I think you will have to wait until the update script runs and the code is merged.

Hi, I will take a look and provide help later today

@JonasArnold I just tested this, and all seems to be working fine for me! In order to test, I used an old version of Companion to create a page of buttons with the actions to test. Then I exported that page, and imported the page on my dev version of Companion. I saw the logging for the upgrades, and verified all the action values weren't undefined.
So I think this should be good to go!

@JonasArnold I just tested this, and all seems to be working fine for me! In order to test, I used an old version of Companion to create a page of buttons with the actions to test. Then I exported that page, and imported the page on my dev version of Companion. I saw the logging for the upgrades, and verified all the action values weren't undefined.
So I think this should be good to go! Let me know if you have anything else you want to do before I merge

Thanks a lot for testing!
Using your method I was able to test the update script aswell and I even found a little bug :) If the action.options.inputChannel had the value of 0 it was not detected, which lead to it not being updated. I fixed this now and I think it would be ready to be merged now.
I already bumped the version to 2.1.0 in the last commit.
Thanks a lot for your support @bryce-seifert !
I'm happy to work on the module in the future if there are any more enhancements required.
By the way, this is how I was testing the update script: I disabled the development module => Companion took the original version of the module, added some actions and stuff, then re-enabled the development module => Companion takes the development module. I suspected it would use the update script in that case, but I'm probably wrong...

Re: upgrade script testing, yeah, there used to be a more explicit was to test the upgrade scripts, but I don't think that's existed since 3.0. It probably needs some work on the core end.
I'm going to go ahead and merge and release this!

@fenderwall These features form this PR should now be available for testing in the latest Companion beta

@JonasArnold Thanks very much for your work on this! Also, I would recommend joining the Slack if you're open to it for easier communication. I know there are some open requests for this module that I just haven't had time to get to, so if any interest / are of use to you I'm sure the users would be happy.

Hi!
I’ve discovered a bug in the AHM Companion module. I tested this both in the previous version and the updated one, and the issue persists in both.
I’m using the AHM Matrix as part of my GreenGo intercom setup, with multiple microphones connected to the inputs, and speakers and 4-wire interfaces connected to the outputs. I create various routes using zones. For example, Mic 1 is routed to a speaker on Output 6.
In Companion, I’ve created a button with two actions. First, I mute Input 1 (Mic 1) to Zone 6 using the “Mute input to Zone” function. In the second action, I unmute the same input to the same zone. For feedback, I use the “Change background when input to zone is muted” option, with Input 1 and Zone 6 selected. This works perfectly when using just one button.
However, when I add a second button with the same input (Input 1) but for a different zone (e.g., Zone 7), including mute, unmute, and feedback actions for this zone, this second button interferes with the feedback of the first button. The second button doesn’t change the mute functions of the first button on the AHM32, but it sets the feedback of the first button to “unmute.”
I hope you can assist me with this issue. I had done some testing and anticipated that the AHM32 would integrate smoothly. However, this bug is making it challenging to use the setup in our production environment.
Thank you in advance, and let me know if I can provide any assistance.


Fix issue with boolean string always resolving to true

THOW_ERROR_IF_VERSION_EXISTS will always be a string. So any conditionals on that field will always assert to true - even if the value of that env is false.
This copies the convention from the other booleans to wrap that in a JSON.parse

Thanks. When will the fix be pushed to the marketplace?

@amrastanov-nitka posted it just now. Sorry for not pushing it earlier, I haven't noticed that I needed to confirm some new github agreements.


Add HTTP 404 to /dataset/{id}

As there is a possibility that a requested dataset may never exist or may be deleted before the request is made, the endpoint should respond HTTP 404.

This should be submitted against develop.

@mcupak This PR is now for develop.

Wow, I had no idea the base branch can be changed after submitting a PR! Thanks @shiroyuki!

No problem :D


Upgraded raw_window_handle dependency to 0.6

Upgraded raw_window_handle dependency version to 0.6, possibly fixing #328.

Great! Thanks :)


Compability - PCF85063A

Arduino board:  ESP32 DEVKIT

Hey.
Been looking for a RTC module and found out the NPX PCF85063A. Found this lib that works with PCF8563.
Any chance those are compatible using this same library?
Thanks

Hi!
If you already bought the module, test it and tell us! Many modules use the same methods.
If you can use another module, try DS3231. It is very reliable and widely used (and also cheap).

The registers on the PCF85063A are different from the ones in the PCF8523 so the library won't work without modifications.

The registers on the PCF85063A are different from the ones in the PCF8523 so the library won't work without modifications.

@drak7 thanks for the reply. On that topic, any idea if that’s too complex to develop? Or how do I even begin? We had a spec for a project that uses this rtc and wishes to use it with a i2c bus linked on a esp32.
Thanks in advance!

@allexotecnologia: You have to read the datasheet, and pay special attention to the description of the internal registers. Then you can take inspiration from the implementation of the existing RTC_* classes.


Assignment 6 - Submission.

Learn more about the U-net library to train the deep learning model. Pretty intense assignment after several colors in black in the predicted mask.

113!


v0.29.0 released

Let me know if anyone notices any major issues with the release.
Release notes here. Please reply anything important I missed in the notes and I will update them.
Thank you to everyone for contributing, apologies it took so long to get a release out!

documentation no longer categorizes the functions (ie list, string, function, object), is this intended?

documentation no longer categorizes the functions (ie list, string, function, object), is this intended?

Thanks for your report. This is not intended, I've found what's wrong, and will make a PR to fix it.

Broken badge still exists on the top page of documentation.

It has already been removed with 243a0910ed49131682f623a5625a0f01a76852a8.

The function signatures are missing as well, the @sig in the block-comments

documentation no longer categorizes the functions (ie list, string, function, object), is this intended?

Thanks for your report. This is not intended, I've found what's wrong, and will make a PR (ramda/ramda.github.io#277) to fix it.

ty for the PR, merged and updated docs

The function signatures are missing as well, the @sig in the block-comments
Is this fixed now for you? Signatures seem to be there for me?

Looks like the repl is not using the latest version of ramda

@kedashoe I see the signatures again. Not sure why I didn't see them before, maybe something about that 277 MR made them work again

@kedashoe I see the signatures again. Not sure why I didn't see them before, maybe something about that 277 MR made them work again

Yes, the generating of sig, category and some other tags depend on R.propEq.

@kedashoe  The "Install" section has a variety of old semver versions

@kedashoe The "Install" section has a variety of old semver versions

I don't know much about deno and nest, seems those versions are correct in that they are the latest versions of ramda there? Looks like those CDNs are updated, not sure how quickly/often they update. I don't believe we traditionally handle releasing on anything but NPM, maybe we should just remove these links?

I'm not familiar with ramda's release process. Are releases to all delivery networks not automated?

Great stuff! Could you please consider using semver going forward? The parameter order for the propEq and pathEq have changed and it could have major implications on business logic. Many projects have automatic minor updates enabled.
I know this issue was raised in 2017 already, and you probably are all busy, yet it would be really great if such a widely used lib as ramda would adher to semantic versioning in the future.

@mvangent At least npm treats the 0.+ bump as breaking change

(Caret Ranges, e.g. ^1.0.0, ^0.1.0, ^0.0.1) allow changes that do not modify the left-most non-zero element in the [major, minor, patch] tuple. In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >=0.1.0, and no updates for versions 0.0.X.

So with ramda: "^0.28.0" in my package.json I'll have to npm install ramda@latest to get to v0.29. npm install will still install v0.28.
I don't know if that's Semver compliant, but the process works.
From the psychological point of view I think Ramda has long deserved a non-zero major version number, at least v1, if not even a jump to v29.0.0.

@semmel Yep, I get your point and if one is aware that minor version bumps can contain breaking api changes it is not a big deal and it can be managed with caret ranges.
But it would be nice to have breaking changes reflected in major version bumps to be in line with semantic versioning according to https://semver.org/. So if the minor version goes one step up it would mean that the api is still backward compatible which currently is not the case for ramda, however this semver standard is quite common across npm otherwise.

You're probably aware, but here is one issue for TypeScript users: @types/ramda is not yet in sync and therefore fixing instances of functions where the parameter order changed (e.g. propEq) will cause a type error when the compiler is checking for valid parameter names, where as not fixing it will obviously be a logic error.

Thank you @kedashoe!
I got downhearted by Mitre dragging me back into a vulnerability black hole after I'd spent so much effort on fighting Veracode on the same damned thing.  (BTW: I reached out to Mitre again last week, and still get no response.)  This left me too unenthused about getting back to Ramda (or really any other) FOSS work.
I promise I will be back.  Maybe not for another month or two, but reasonably soon.   It's good to see someone picking up the reins meanwhile.

In the meantime, if anyone has the energy to create an Upgrade Guide for this version, it would be useful.

In the meantime, if anyone has the energy to create an Upgrade Guide for this version, it would be useful.

Hey @CrossEye :)
I've included the upgrade notes on the release: https://github.com/ramda/ramda/releases/tag/v0.29.0

@CrossEye @kedashoe
I've just created an Upgrade Guide for this version, which includes more details.

Thanks, @kedashoe and @adispring!  These notes look great.


Enable initrd modules required by cryptsetup --kernel-crypto

See: https://github.com/NixOS/nixpkgs/pull/38382#discussion_r196077562

I've been using cryptsetup with an SSD and without kernel crypto to run my entire NixOS and didn't noted any performance issues, but I agree that my patch was a temporary workaround, so enabling the crypto module would be a better solution.

The disable-kernel-crypto option also breaks the feature of cryptsetup benchmark that can be used when installing nixos to reason about the speed of disk encryption

The installer.luksroot NixOS test works with and the kernel userapace crypto API enabled in cryptsetup on at least 19.03. cryptsetup was updated to 2.0.6 in the meantime, maybe the bug was fixed? Haven't noticed anything in cryptsetup release notes. This API shouldn't in fact be need for LUKS, only for tcrypt and the benchmark.
@cript0nauta Did you also run the test or did you just notice that on your local machine? Do you have any non-standard config concerning the initrd?

Hmm, even with cryptsetup-2.0.2 the installer.luksroot test succeeds. We need more information.

@fpletz I haven't ran any tests, I just tested it in my work laptop and in a VM used to isolate the issue. I used a non-standard initrd config only for debugging, but after finding the problem I used the standard one.
The only strange thing I did was to have a LUKS2 encrypted volume, which isn't very common (or at least it wasn't at the moment I experienced the issue).
In a few days I will try to boot my system both with and without kernel crypto to check whether it is necessary or not.

@fpletz: I can confirm that I still have problems booting my system when kernel crypto is enabled. I put this in my configuration.nix, in an updated unstable NixOS:
  nixpkgs.config.packageOverrides = super: {
    cryptsetup = (super.cryptsetup.overrideAttrs (old: rec {configureFlags = [
      "--enable-cryptsetup-reencrypt"
      "--with-crypto_backend=openssl"
      # "--disable-kernel_crypto"
    ];}));
  };

With this configuration, my system boots. If I uncomment the "--disable-kernel_crypto" line, it doesn't because it fails to unencrypt my root partition.
I'm using LVM inside a LUKS2 partition.

Here is the result of using --verbose --debug when mounting my LUKS2 volume with kernel crypto enabled. The last image is the most important. Sorry for pasting screenshots, I didn't have a flash drive to copy the logs.

Thank you very much for your detailed analysis. :+1:
Oh, LUKS2! Seems the userspace API is indeed needed for LUKS2 but not LUKS1. I'll try to adapt the installer.luksroot test and fix this issue. There are probably just some algif_* modules missing.


Switch Metadata to mapbinder and expose module to wrap install

I might be blocked on https://github.com/cashapp/misk/issues/2863, investigating further what the best path forward is on the import violation build failures.


Documentation 404 not found for "Suggest Edit" link in "API Reference" pages

What happened?
Concrete example: let's say I am currently reading the documentation of DataArray.resample. I would like to have a look at the internals and see the code directly on GitHub.

We can see a GitHub icon, with 3 links:

Repositry: leads to the home page of the repo: https://github.com/pydata/xarray
Suggest edit: leads to a 404 not found as it points to the generated documentation
Open issue (generic link to open an issue)

The [source] link does what is expected: it leads to the source code https://github.com/pydata/xarray/blob/main/xarray/core/dataset.py#L10471-L10565
What did you expect to happen?
The second link "Suggest edit" should actually lead to the source code, as the documentation is auto-generated from the docstrings themselves. Maybe it could be renamed like "View source"
Example of other repos having this feature:
Minimal Complete Verifiable Example
N/A

MVCE confirmation

[ ] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[ ] Complete example — the example is self-contained, including all data and the text of any traceback.
[ ] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[ ] New issue — a search of GitHub Issues suggests this is not a duplicate.
[ ] Recent environment — the issue occurs with the latest version of xarray and its dependencies.

Relevant log output
N/A

Anything else we need to know?
No response
Environment
N/A

Thanks @etienneschalk for reporting and sorry for the delay.
Although the "suggest edit" button should be disabled,
https://github.com/pydata/xarray/blob/b83aef65e711e490403a1e37c4e818d7b6c098bc/doc/conf.py#L388-L392
this obviously doesn't work anymore. I'm no Sphinx expert at all, leaving the debugging to someone else more knowledgeable.


🚨 NextAuth.js 2.0 - Release Candidate

I am considering next-auth@beta (the current version in master) as a release candidate for 2.0 and that it 2.0 will be released in the next few days, depending on feedback.
Latest beta release<EMAIL_ADDRESS>(includes fixes for issues reported)
Features
Authentication

Designed to work with any 0Auth service, it supports 0Auth 1.0, 1.0A and 2.0
Built-in support for many popular 0Auth sign-in services
Supports email / passwordless authentication
Supports both JSON Web Tokens and database sessions

Own your own data

An open source solution that allows you to keep control of your data
Supports Bring Your Own Database (BYOD) and can be used with any database
Built-in support for for MySQL, MariaDB, Postgres, MongoDB and SQLite
Works great with databases from popular hosting providers

Secure by default

Designed to be secure by default and promote best practice for safeguarding user data
Attempts to implement the latest guidance published by Open Web Application Security Project

Security focused features include CSRF protection, use of signed cookies, cookie prefixes, secure cookies, HTTP only, host only and secure only cookies and promoting passwordless sign-in.
Acknowledgement
NextAuth.js 2.0 is possible thanks to its contributors.
I would in particular like to thank the following people for their help with 2.0:

Lori Karikari
Nico Domino
Fredrik Pettersen
Gerald Nolan

I think this is fantastic feature set for a first release. We have so far smashed everything that was planned for 2.0 and gone beyond that by some margin.
I know there are many more people who have offered to help and I know there are features that many of you would like to see that didn't make the cut; unfortunately my time is limited and I feel it's important to cut a release so v1 can be finally be retired!
I'm am looking forward to working with more of you and figuring out the roadmap for 2.1 to build on this release and extend authentication mechanisms, adding features to JSON Web Token support, auditing / logging, database migration support and lots of other exciting stuff.
I'd ask if you would raise any bug reports or feature requests (including what you might see as incomplete features) as separate issues and just link back to this ticket mentioning this ID.
Please do ask questions in this thread! I'm sure you have a question someone else has it too.
Documentation
Please checkout the excellent documentation site (with link to live demo) that the folks in the team have worked on https://next-auth.js.org

I'm going to repost a question here from @emmenko asked in #167 as it is a very good question and I think people other may also be interested in it and may have feedback:

I have a question about using JWT. Does it mean that we don't need a DB anymore?
Thanks

That's a great question! The answer is "sort of" and that it will be improved.

If you want right now, you could use an SQLite in memory database in production when using JWT, so you don't need a hosted database anywhere if you are using an authentication provider that you trust (e.g. email sign in, the Google provider that verifies email addresses, or some other OAuth provider you trust).
The flip side is the User ID value in the JWT would be meaningless in this scenario (and should be ignored), but otherwise you could use this approach.
However how I would like it to be work is that I would like the option not to be able to provide a database at all and have everything still work.
I think to be useful, it would need to have an additional option, such as callback function which allowed you to evaluate a user on sign in and decide if they were valid and allowed to sign in (e.g. based on the service / account they were using, or the email address they were sign in with if used with an authentication provider you trust).
This function could potentially also return data (e.g. credentials, roles) to be added to the JWT.

This is not terribly complicated and could potentially be something that goes in before 2.0 is released, depending on feedback.

I've been a bit afk lately but I've read some pull requests and issues. I can help with the OAuth provider docs somewhere this week if you want. I saw that you wanted separate docs per provider like Passport does it I guess?  Also, I have to look into the Reddit profile stuff and had the same issue with some other providers that I haven't included yet.

I'm am looking forward to working with more of you and figuring out the roadmap for 2.1 to build on this release and extend authentication mechanisms, adding features to JSON Web Token support, auditing / logging, database migration support and lots of other exciting stuff.

Maybe we could have some place like Discord or whatever you like to discuss this stuff? It's easy to miss stuff being said in issues and pull requests and it's less clutter too.

I've been a bit afk lately but I've read some pull requests and issues. I can help with the OAuth provider docs somewhere this week if you want. I saw that you wanted separate docs per provider like Passport does it I guess? Also, I have to look into the Reddit profile stuff and had the same issue with some other providers that I haven't included yet.

+1 been super busy recently too, sorry about to anyone if I have missed anything.
Yeah, I think I've changed my mind from my original view of consolidating all the providers into one page and allowing them each to have a separate page.
I think the guide you wrote is wonderful and we should keep that exactly as is, as it works for most providers (and explains what is going on).
I think having dedicated pages for each authentication provider (ala Passport) is the way to go after all, especially for the special cases like Apple authentication provider that @geraldnolan put together are is super useful.
Even in simple cases like Facebook it's nice to have a place to confirm how straightforward it is, as well as list any caveats in detail.
I haven't really thought about the format of the page though, so if anyone has better ideas for a template for them would welcome that! (Appreciate there will always be exceptions like the Apple one too, which is more involved.)

I'm am looking forward to working with more of you and figuring out the roadmap for 2.1 to build on this release and extend authentication mechanisms, adding features to JSON Web Token support, auditing / logging, database migration support and lots of other exciting stuff.

Maybe we could have some place like Discord or whatever you like to discuss this stuff? It's easy to miss stuff being said in issues and pull requests and it's less clutter too.

I've been thinking this too!
I'd really like a dedicated place for us to chat about proposed stuff (myself, you, Nico and Gerald…) before I do it. I appreciate I've just been "doing stuff" as we don't really have a way to do that right now, beyond just writing stuff in PRs.
A better place where folks can self help would also be good I think.
I think Discord is a great suggestion and would fit really well!

@mathewtrivett Thank you, I would really welcome that.
I've been considering reaching out to people who are specialists in this area and who might be willing to conduct a review.

Right now we don't have an explicit disclosure policy, so that's probably a first action we can take. If you would like to reach out to me privately in the interim about anything sensitive (and that it might be sensible to have patch ready to install for before disclosing) you can also reach me on<EMAIL_ADDRESS>

After that, I would expect to drop a decent set of regression tests for all flows, which run against multiple databases (and none). That should at least ensure we maintain standards for issues we are already aware of.

JWT support might also be worth mentioning in this context, given it's very new:
When enabled, JSON Web Tokens are signed but not encrypted. When functions for people to add their own data to them that will change to encrypted then signed - as NextAuth.js is currently the only thing that sets data on them - there is no API for this - signed only is good enough as the JWT does not contain any sensitive data the user should not have access to, and it is not readable from client side JavaScript.
Of course, I'm also sure there are lots of things we don't know about and I would really welcome a review and recommendations.
I'd be happy to provide additional documentation related to this, to help clarify intended behaviour.

Hey @iaincollins, once again thank you for all of your work on this project. I know you have touched on this briefly but are you planning on this 2.0 release being ready for production use cases. Many of the docs mention the fact that this is still in beta but wanted to get some clarity on that if possible?

Hey @iaincollins, once again thank you for all of your work on this project. I know you have touched on this briefly but are you planning on this 2.0 release being ready for production use cases. Many of the docs mention the fact that this is still in beta but wanted to get some clarity on that if possible?

Sure! So the beta notices will be removed from the docs when it's cut for release.
Things will move much slower after release to ensure stability and to avoid breaking things once v2.0 i sout (with moving fast and breaking thing being something of a luxury of being pre-release), but there will be beta or canary releases at about the same pace.
Version 2.0 has been re-written, with a new approach and entirely new code, from the ground up in about a month. However, the next big update will probably take the same time again but will be a much more modest update - likely with a focus on testing - but there will likely be many bug fixes in the meantime as reports come in.
The feature set for 2.0 is pretty fixed at this point, but I one thing that might happen that is by nature relatively safe, is that database support may become optional when using JWT - for those that don't want or need to persist user accounts, because they are using an OAuth service they trust. I am still waiting to see what other issues come before I make a call on that though.
We've had some great bug reports and fixes since this post went up, but will see what the sort of rate of them in and will want to be confident it's suitable for mainstream use cases in a production environment, before making a call on moving out of beta.
(On that note, positive reports also welcome!)

@iaincollins Great, that is helpful thank you!

@iaincollins re: community discord/slack https://github.blog/2020-05-06-new-from-satellite-2020-github-codespaces-github-discussions-securing-code-in-private-repositories-and-more/#discussions looks like it'll be coming soon. I'd advise against creating another silo of information, only because searching is really important and keeping it in GitHub would make life much easier for noobies

I agree to wait for the GitHub Discussion feature to be available. That would be my preference as well.

Discord would be to discuss the roadmap and behind the scenes stuff for contributors. Discussions are to answer questions from the community. These are two separate things. I didn't mean to move the community to Discord. Just internal discussions.

Discord would be to discuss the roadmap and behind the scenes stuff for contributors. Discussions are to answer questions from the community. These are two separate things. I didn't mean to move the community to Discord. Just internal discussions.

This was my thinking too, although I was just looking at it and I think there might be some team discussion features on GitHub that might let us have private discussions?
We should probably move the discussion on this to dedicated ticket as some good options to be discussed there! Will do that over lunch and link back to it unless anyone beats me to it (please feel free! :-)

@iaincollins sorry for the delayed reply but yes will drop you a message next week to give you a bit more context to the project.
But essentially we will be using Google Auth.  I’m hoping to use JWT and avoid having a db if at all possible. So the docs you mentioned about JWT behaviour would be super useful.
As you suggested happy to flag anything we find privately via email. But also happy to work on fixes and improvements if we can.

I want to say I'm absolutely floored at how easy it was to set up authentication using this library. Huge kudos!
Quick question - is there a way to hook into the database so that there session can return Moore than just the username/email? I'm trying to figure out how to fetch the roles that a user belongs to without having to do a second db query.

I want to say I'm absolutely floored at how easy it was to set up authentication using this library. Huge kudos!

Thanks! I'm really happy to hear that!

Quick question - is there a way to hook into the database so that there session can return more than just the username/email? I'm trying to figure out how to fetch the roles that a user belongs to without having to do a second round trip.

No, but there should be. There is a @TODO to expose a callback function to allow you to customise what /api/auth/session returns.
I might add that over the weekend before we release, as it's a very simple / low risk change and quite a few folks have asked about it.

JWT sessions
We've been getting a few questions about JWT support, so thought I'd update folks on that and let them know to follow Encrypt JWT after signing which is planned to be wrapped up this weekend (hopefully later today) – the final implementation may differ from outline in the ticket.
As described in the ticket, it will be a minor breaking change to some of the options (to the jwt and session* options specifically) to rename things, but will make it possible to:

Read from the JWT more easily
There will be an explicit method for this you can use to access JWT sessions in API routes.

Inject additional data into JWT
i.e. on initial sign in and when re-signing, which is triggered when the client checks a session

Define custom signing / verification / encryption / decryption routines for JWT
This will allow you to any use mechanism you want for the JWT, so you can easily use an existing pragma, whether that is signed payload inside a signed JWT or signed then encrypt mode, or signed but not encrypted.
Note: By default the JWT will be both signed and encrypted and just as easy to use as it is now; but it will be possible to customise the handling if you want to.

Database sessions
It is likely the option to customise the contents of the session object that is returned when using database sessions will also be included in the same update, to allow for feature parity between the two approaches.
Things seem stable and could have launched without this, but this is a breaking change so it would be harder to release after v2 without breaking things for people, so I think it's worth holding on and releasing until after it's done as we are otherwise going to have to field a lot of tickets about it; but the impact on delay of v2 release should be fairly minimal.

Based on feedback and the sorts of issues that were coming, some features from 2.1 were brought forward and a large cumulative update has now been released to next-auth@beta as PR #223.
This introduces some breaking changes to the current options, including some small changes to the database schema, but I think the feature list will make a lot of people happy. All the changes are reflected in the updated documentation.
This is the last feature update I intended to work on personally before we release v2. It is a larger update than I had planned and probably pushes the release of v2 till later this week to allow time for wider testing and any bug fixing as required before we cut the release.
There is some great additional provider documentation that is in progress too.
Change log
NextAuth.js beta releases haven't normally included a change log, but as we are so close to release and it's such a big update I thought it was worth detailing the changes.
Database

[x] Databases are now optional - useful with OAuth + JWT if you only need access control
[x] Updated documentation and added example code for custom database adapters

JWT

[x] JWT option is now an object that groups JWT related options together (was a boolean)
[X] Refactored JWT lib and add AES encryption / decryption as well as signing / verification
[x] Allows JWT encode/decode methods to be overridden as options
[x] Contents of JWT can easily customised - without needing to use custom encode/decode
[x] Exported JWT methods so they can be called from custom API routes
[x] Updated documentation for new JWT options

Sessions

[x] All session options (eg. maxAge, updateAge) now grouped under single session option
[x] Using JWT for sessions is now enabled from session object (session.jwt: true)
[x] All options involving time now use seconds (instead of milliseconds) for consistency
[x] Added option to customise the Session object that is returned from /api/auth/session
[x] Update documentation for new Session options

Other improvements

[x] Added allowSignin() option to control what users / accounts are allowed to sign in
[x] Refactored callbackUrlHandler() - this option  is now called allowCallbackUrl()
[x] Minor improvements to NextAuth.js client API methods
[x] Minor to NextAuth.js API routes
[x] Minor improvements to built-in error pages
[x] Refactored database models
All tables now include a created column for each row which contains the datetime of when the row (e.g. User / Account / Session) was created.
Additionally, sessions now use the name 'expiry' for the expiry datetime value for consistency with other models.

@iaincollins any reason why you don't use the release notes on Github. I always tend to go look there for updates haha but you don't post them there.

@iaincollins any reason why you don't use the release notes on Github? I always tend to go look there for updates haha but you don't post them there.

I haven't been using releases yet to allow beta development to go faster, but that is not really sustainable with so many contributors (or post launch).
I'd like to automate things more and structure it better starting from the release of 2.0.
Have captured this in some related issues:

Team to decide what platform to use for internal discussions
Add GitHub hook to publish to NPM when a new release is created
Automate testing; add code coverage
Decide on roadmap for 2.1

Are the DB models supposed to be exported from the module? Right now, there's no way to integrate with the user models other than copying them from the source code.

Update: Scope creep has gotten to us 🧟♂
The good news is great new features have dropped, and more are on the way and, based on the feedback we've been getting, I think they are cohesive and relevant to a large number of people.
JWT and being able to use NextAuth.js without a database are already covered above, another feature that recently was released was that email addresses are now optional (but can still be required), to allow signing in with providers that don't provide them. The range of providers supported out of the box (and compatibility with custom providers) continues to grow too.
Currently in progress:

#245 - Update and document models, schemas and database structure
#247 - New Callback / Events system

The bad news is the previous release candidate is no longer a release candidate and obviously this pushes the release back another week.
We could have pushed back the changes in to a future release, but it would be a lot harder to do them in a responsible way after launch and would have taken many more weeks to get there if we had released; and I think a lot of folks would not have been very happy with the quality if we had released the current default database models in the current state.
I am trying to draw a line here though. You can track the milestones on GitHub to see how we are doing. There are new issue templates for features / bug reports / question too, to help with structure. Please do use those to report bugs, ask questions and request features.

Switched to JWT w/ database option, everything seems to be working!
Question: how does one access the JWT token from the client? I'm trying to set up Hasura ( https://hasura.io/docs/1.0/graphql/manual/auth/authentication/jwt.html ), and it requires the JWT token passed into it with some added fields. I was able to add fields (using jwt.get() ), and can even see the fields on the decoded JWT token, but I can't figure out how to get actual token so I can pass it on.
Thanks again for a fantastic library!

Your feedback on the data model is requested!
Request For Comments - Database Schema
Please leave comments or related on the PR linked to above and not here. Thanks!

You are probably all sick of updates at this point, but the last of the features for 2.0 are released!

PR #253 added new Models and Schemas
PR #260 added new Callbacks and Events

Both of these were critical breaking changes to the beta, and were made so that we don't have to make breaking changes after 2.0 is released (even as we add new features).
Included with both these updates are improved documentation and error handling.
If you are already using an earlier release of the beta be sure to checkout the new options documentation - and the Pull Requests above - to see how things have changed.

Extremely happy to announce that NextAuth.js v2.0 has been released. 🥳
Thanks everyone for the amazing contributions!
The release notes and web site contains all the information and documentation about this release, but if you interested in some of the work that's been going on, you can take a look at recent pull requests that have been merged.
If you want to see what's in store for the future you can keep an eye on the milestones.


Fixed drush sql-connect and sites aliases --print

So this isn't my favorite way to fix this, but it's the only way I found that will work. The SSH connection string is appropriately formatted every time, but sql-connect is the only command it won't work for.
terminus drush sql-connect executes:
ssh -T<EMAIL_ADDRESS>-p 2222 -o "AddressFamily inet" 'drush '\''sql-connect'\'' '
but blank line is returned. For a good comparison, terminus drush help works just fine:
ssh -T<EMAIL_ADDRESS>-p 2222 -o "AddressFamily inet" 'drush '\''help'\'' '
Since this is the only way I've got it working after coming back to it time and time again for a month now, I'm going to recommend it as the fix. If you know of a better option, I'd be excited to hear it.

Closes #454, although the original issue cleared up when the command was fixed in #589.

I changed the function name per your comment, and pointed terminus drush sql-connect to terminus site connection-info --site=<site> --env=<env> --field=mysql_command.

@TeslaDethray can we just remove that command action entirely? Perhaps just adding --env= and --connection-type=sql to the site connection-info action?

Per our discussion, I've changed it to catch unavailable commands and tell you to either run them in drush, or offer the Terminus equivalent, if available.

:racehorse: :+1:


Close left panel issue

Hi thanks for this nice library, its really helpful for n00b like me.
I try to close left panel from left panel view controller by using panel?.closeLeft()
What i expect is left panel will be closed with animation slide out, but what i get is only left panel closed without any slide out animation.
Is there any configuration that i do incorrectly?

@dfaizmaulana
You need to call openCentre function. Let me know if it works otherwise I will share some code example with you.
Thanks & regards

@fahidattique55
I tried to call panel?.openCenter(animated: true) as well, but still no animation happen.
I'm just wondering if panel?.closeLeft() should be call from center panel rather than on left panel, because when i try to call panel?.openLeft(animated: true) from center panel the animation is work.

@dfaizmaulana
I got the issue you are facing. There are two ways to hide the left panel.

Change the center panel animated
slideLeftPanelOut in the FAPanel+Animation.swift file

The second way is a function but internal for now. So I will push a new update to give the option you want. Otherwise if you will tap on centre panel the left panel will get close with animation. Or if you will change the center panel, the left panel will also get close with animation.
Thanks


Production Ready?

This package sounds very interesting, but I wonder if it is Production Ready and Battle Tested?
Are there any sitations where things could break because of using this package?

Hi @raayu83! We use it in a handful of projects. Since the "magic" is quite simple, I guess you could put it like this: Test it locally and if it works, I'll work in production as well.
Would be awesome to get some feedback from you when you're trying it out 🙂

We actually use it in production without problems! A local test is always advised of course!

Hi @raayu83! I hope the answers satisfy you. Please feel free to drop any questions here. Since I don't know if there are any left, I'll close this ticket.


roverrobotics_ros2: 0.1.1-2 in 'foxy/distribution.yaml' [bloom]

Increasing version of package(s) in repository roverrobotics_ros2 to 0.1.1-2:

upstream repository: https://github.com/RoverRobotics/roverrobotics_ros2.git
release repository: https://github.com/RoverRobotics-release/roverrobotics_ros2-release.git
distro file: foxy/distribution.yaml
bloom version: 0.10.0
previous version for package: 0.1.0-4

rover_bringup
* correct package dependency to allow for ros buildfarm passage

rover_description
* correct package dependency to allow for ros buildfarm passage

rover_driver
* Add pi contoller timeout to prevent run away
* correct package dependency to allow for ros buildfarm passage

rover_msgs

No changes

rover_navigation

No changes

rover_simulation
* formatting launch.py files and adding env-hooks

rover_teleop

No changes

roverrobotics_ros2
* Add pi contoller timeout to prevent run away
* formatting launch.py files and adding env-hooks
* correct package dependency to allow for ros buildfarm passage

Merging during hold period since this aims to fix a failing build.


MusicBot Stuttering

Ok so I havent checked for packet loss just yet, however, server performance cannot be the issue. I can get the bot working just fine but every song comes in laggy. I have tried the bot on my home computer and my $130 /month dedicated server. The server is i7 7700k 4.2ghz, 64GB DDR4 and 256GB SSD with 1GBPS port and my ping to the server is <20 ms. Any clue how I should proceed to diagnose this issue? Thank you for your time.

Note: I searched google endlessly for a fix for this but all of the replies just say: Oh you have bad connection, oh you have bad cpu/ram whichbis not helpful. The only thing I can think of is possibly lag to the discord server itself? My region is NYC area.

Have you tried changing the location of the discord server itself?

Try setting the process priority of the music bot to Realtime. This will allocate more CPU time to the musicbot and reduce stuttering.

Someone apparently fixed the problem by reinstalling Python and Git using the guide in Wiki (#661).

@SimonOrJ Yes! This was the fix. Thank you all for your replies! Have a blessed day!


Login Provider Migration Issue

There appears to be an issue with the user DisplayName not being added to the AspNetUsers table in the SqLite db. When I attempted to register, it was throwing an SqLite exception related to the DisplayName. When I opened up the table in a Db browser, there was no column for DisplayName in the AspNetUsers table.
I was using a Google provider.
Workaround: I manually added the DisplayName column with TEXT as the type, then was able to register an account and login successfully.

Yea... there's a larger problem with the Security EF context migrations not being applied.  I ran into this issue over the last week while deploying a new container and got stuck


[Bug] [Process definition] There is a problem with the location of the import process node.

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
The import process does not render the nodes in the workflow according to the coordinate position in the file.

What you expected to happen
The node position is not rendered based on coordinates.
How to reproduce
Upload the workflow file and click on the workflow details.
Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I will check this issue.

I will check this issue.

I assigned this issue to you @calvinjiang


Spike: Bytecoder JS backend

We once turned backend into JS, compilation of Maven was working and much faster then WASM.
Things to research:

Can we (easily) support both JS and WASM  together?
Test: with and without Exception handling
How easy is it to get JS backend to work?
Document alternative build structure

JS and WASM support both available in app now.
Refers to commit: https://github.com/squins/gdx-backend-bytecoder/commit/d9f523b8eab7f165f4f4666963dc0302ed282519


Some models are showing innet faces instead of outer faces

Some models (notably the skull of [Gait10dof]) have some faces flipped (you can see the inside of the mesh).
I've checked in Blender, and the normals are correctly set, so the problem must be on the Material side.

I think I have found the reason of this. In the gltf files, in the "materials" section, the alpha mode of the materials is "alphaMode": "BLEND". If you set it to "alphaMode": "OPAQUE", everything is shown correctly (including muscles). Here is the explanation.
@aymanhab, is there a way to export the gltf files  with alphaMode set to OPAQUE by default?


Create a restore point for to undo pose estimates

To avoid messing up the pose it would be helpful to revert changes done by sending initial poses. Either by keeping track of the poses or saving the current pose.

Maybe a 'commit' for a pose estimate? this would require tracking and rendering the current offset, maybe some visual feedback for uncommitted poses?


Skeletons and Zombies spawner Exploit

*Detailed description of the issue:
Basically if you place a zombie spawner underwater you bypass the spawner protection, as they transform in drowned
Same for the new snnow block in 1.17, place these near the skeleton spawner and it transforms skeletons into husk and they lose the antiexploit protection
Jobs version:
<IP_ADDRESS>
Server Type (Spigot/Paper/etc):
Paper
Server Version (using /ver):
1.17.1 - 249

ee4a323ddfb37b769a7563334ce2a49f71bb34e1


fix: remove duplicate path separator

For localisation in sub-namespaces. I was going to PR on https://github.com/ppy/osu a bump for in .config/dotnet-tools.json when I noticed this while comparing behaviour before and after bumping.
Despite not breaking anything on Windows, I haven't tested if it breaks on macOS or Linux. Better be safe than sorry.
This was probably an oversight during my testing for #57.
Will probably need more testing on other platforms to see if it behaves correctly.

Would prefer if you don't force push as it breaks the review flow, thanks.


English improvements

I don't think the checklist really applies.
I'm learning D and having done the D-tour (to which I made various English improvements), and some textbook reading and some simple programs, I'm now reading the manual. And since I'm reading it anyway, I might as well improve the English as I go.

That checklist applies more to code changes rather than documentation changes, so no need to worry. Thanks!


Suggestion: Nerf Fighter Marshal bonus to half PB rounded down

Alternatively compensate by allowing study enemy from stealth, since logically there should be no element in that action that should in any way give away a character's hiding spot :)

Moving to discussions, @dolenam317